mirror-dest service-id [type encap-type] [mirror-source-type mirror-source-type] [create]
no mirror-dest
config>mirror
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command sets up a service that is intended for packet mirroring. It is configured as a service to allow mirrored packets to be directed locally (within the same device), over the core of the network and have a far end device decode the mirror encapsulation.
The mirror-dest service comprises destination parameters that define where the mirrored packets are to be sent. It also specifies whether the defined service-id receives mirrored packets from far end devices over the network core.
The mirror-dest service IDs are persistent between boots of the router and are included in the configuration backups. The local sources of mirrored packets for the service ID are defined within the debug mirror mirror-source command that references the same service-id.
The mirror-dest command is used to create or edit a service ID for mirroring purposes. If the service-id does not exist within the context of all defined services, the mirror-dest service is created and the context of the CLI is changed to that service ID. If the service-id exists within the context of defined mirror-dest services, the CLI context is changed for editing parameters on that service ID. If the service-id exists within the context of another service type, an error message is returned and CLI context is not changed from the current context.
The no form of this command removes a mirror destination from the system. The mirror-source associations with the mirror-dest service-id do not need to be removed or shutdown first. The mirror-dest service-id must be shutdown before the service ID can be removed. When the service ID is removed, all mirror-source commands that have the service ID defined are also removed from the system.
Specifies the service ID that identifies the service in the service domain. This ID is unique to this service and cannot be used by any other service, regardless of service type. The same service ID must be configured on every device that this particular service is defined on.
If a particular service ID already exists for a service, the same value cannot be used to create a mirror destination service ID with the same value.
For example:
If an Epipe service-ID 11 exists, a mirror destination service-ID 11 cannot be created. If a VPLS service-ID 12 exists, a mirror destination service-ID 12 cannot be created.
If an IES service-ID 13 exists, a mirror destination service-ID 13 cannot be created.
Specifies the type describes the encapsulation supported by the mirror service.
Allows scaling of mirror services that can be used only with remote mirror sources, while limiting the mirror services that can be used by local mirror sources or by both local and remote mirror sources. For more information, see Table: Combinations of SAPs, spoke-SDPs, and remote sources allowed in a mirror service. This parameter is not supported in the access-uplink operating mode.
Indicates that the mirror service can only be used by local mirror sources.
Indicates that the mirror service can only be used by remote mirror sources.
Indicates that the mirror service can be used by both local and remote mirror sources.
fc fc-name
no fc
config>mirror>mirror-dest
7210 SAS-T (network and access-uplink), 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-Sx 10/100GE
This command specifies a forwarding class for all mirrored copies of the packets transmitted to the destination SAP overriding the default (be) forwarding class. All packets are sent with the same class of service to minimize out-of-sequence issues. The mirrored copy of the packet does not inherit the forwarding class of the original packet.
When the destination is on a SAP, it pulls buffers from the queue associated with the FC name and the shaping and scheduling treatment given to the packet is as per the user configuration for that queue.
The FC can be assigned only when the mirror source is local. When the mirror source is remote, the network QoS ingress policies that are applied to all the traffic received on the network port and network IP interface are also applied to mirror traffic.
On the 7210 SAS-T, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-Sx 10/100GE, all SAPs configured on a port use the port-based egress queues. If the mirror destination SAP (that is, dot1q SAP or a Q1.* SAP) is configured to share an uplink with service traffic, the mirrored copy of the traffic sent out of the Dot1q or Q1.* SAP shares the port-based egress queues with the other service traffic. The user is provided an option to assign the profile mirrored copy to the packet, so that during congestion, the mirrored copy of the packets marked as out-of-profile is dropped before in-profile service traffic (and possibly in-profile mirrored traffic, if the user has configured mirrored traffic to be in-profile). The profile is used to determine the slope policy to use for the packet and determines the packet drop precedence. Additionally, if marking is enabled, it determines the marking value to be used in the packet header.
On the 7210 SAS-Mxp, 7210 SAS-R6 and 7210 SAS-R12, SAP-based egress queue QoS policy is used when the port-based egress queuing is disabled on the mirrored destination SAP, allowing users to control the amount of bandwidth allocated for mirrored traffic. If port-based queuing is enabled, all SAPs configured on a port use the port-based egress queues.
The no form of this command returns the mirror-dest service ID forwarding class to the default forwarding class.
The best effort (be) forwarding class is associated with the mirror-dest service ID and profile is out.
Specifies the name of the forwarding class with which to associate mirrored service traffic. The forwarding class name must already be defined within the system. If the FC name does not exist, an error is returned and the fc command has no effect. If the FC name does exist, the forwarding class associated with fc-name overrides the default forwarding class.
Specifies the profile to assign to the mirrored copy of the service traffic. The profile is used to determine the slope policy to use for the packet and determines the packet's drop precedence. Additionally, if marking is enabled, it determines the marking value to be used in the packet header. A value of in marks the traffic as in-profile traffic and results in the use of high slope parameters. A value of out marks the traffic as out-of-profile and results in the use of low slope parameters.
far-end ip-address [vc-id vc-id] [ing-svc-label ing-vc-label | tldp]
no far-end ip-addr
config>mirror>mirror-dest>remote-source
Supported on all 7210 SAS platforms as described in this document
This command defines the remote device and configures parameters for mirror destination services on other devices allowed to mirror to the mirror destination service ID.
The far-end command is used within the context of the remote-source node. It allows the definition of accepted remote sources for mirrored packets to this mirror-dest-service-id. If a far end router has not been specified, packets sent to the router are discarded.
The far-end command is used to define a remote source that may send mirrored packets to this 7210 SAS for handling by this mirror-dest service-id.
The ing-svc-label keyword must be entered to manually define the expected ingress service label. This ingress label must also be manually defined on the far-end address through the mirror-dest SDP binding keyword egr-svc-label.
The no form of this command deletes a far-end address from the allowed remote senders to this mirror-dest service. All far-end addresses are removed when no remote-source is executed. All signaled ingress service labels are withdrawn from the far-end address affected. All manually defined ing-svc-label configurations are removed.
Specifies the service IP address (system IP address) of the remote device sending mirrored traffic to this mirror destination service. If 0.0.0.0 is specified, any remote is allowed to send to this service.
Specifies the virtual circuit identifier.
Specifies the ingress service label for mirrored service traffic on the far-end device for manually configured mirror service labels.
The defined ing-svc-label is entered into the ingress service label table which causes ingress packet with that service label to be handled by this mirror-dest service.
The specified ing-svc-label must not have been used for any other service ID and must match the far end expected specific egr-svc-label for this 7210 SAS. It must be within the range specified for manually configured service labels defined on this 7210 SAS. It may be reused for other far end addresses on this mirror-dest-service-id.
Specifies that the label is obtained through signaling via the LDP.
[no] remote-source
config>mirror>mirror-dest
Supported on all 7210 SAS platforms as described in this document
This command configures remote devices to mirror traffic to this device for mirror service egress. Optionally, this command deletes all previously defined remote mirror ingress devices.
The remote-source context allows the creation of a ‛sniffer farm’ to consolidate expensive packet capture and diagnostic tools to a central location. Remote areas of the access network can be monitored via normal service provisioning techniques.
Specific far-end routers can be specified with the far-end command allowing them to use this router as the destination for the same mirror-dest-service-id.
The remote-source node allows the source of mirrored packets to be on remote 7210 SAS devices. The local 7210 SAS configures its network ports to forward packets associated with the service-id to the destination SAP. When remote-source far-end addresses are configured, an SDP is not allowed as a destination.
By default, the remote-source context contains no far-end addresses. When no far-end addresses have been specified, network remote devices are not allowed to mirror packets to the local 7210 SAS as a mirror destination. Packets received from unspecified far-end addresses are discarded at network ingress.
The no form of this command restores the service-id to the default condition to not allow a remote 7210 SAS access to the mirror destination. The far-end addresses are removed without warning.
sap sap-id [create]
no sap
config>mirror>mirror-dest
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command creates a service access point (SAP) within a mirror destination service. The SAP is owned by the mirror destination service ID.
The SAP is defined with port and encapsulation parameters to uniquely identify the (mirror) SAP on the interface and within the box. The specified SAP must define an Ethernet port with a null SAP or a Dot1q SAP or a Q1.* SAP.
Only one SAP can be created within a mirror-dest service ID. If the defined SAP has not been created on any service within the system, the SAP is created and the context of the CLI changes to the newly created SAP. In addition, the port cannot be a member of a multi-link bundle, LAG, APS group or IMA bundle.
If the defined SAP exists in the context of another service ID, mirror-dest or any other type, an error is generated.
Mirror destination SAPs can be created on Ethernet interfaces that have been defined as an access port or access-uplink port. If the interface is defined as network, the SAP creation returns an error.
When using a dot1q SAP or a Q1.* SAP as a mirror destination, users must allocated resources of another port for use by this features. Refer the mirror configuration notes preceding Configuration notes.
The no form of this command used on a SAP created by a mirror destination service ID, deletes the SAP with the specified port and encapsulation parameters.
Specifies the physical port identifier portion of the SAP definition. See Common CLI command descriptions for command syntax.
service-name service-name
no service-name
config>mirror>mirror-dest
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures an optional service name, up to 64 characters, which adds a name identifier to a specific service to use that service name in configuration references as well as display and use service names in show commands throughout the system. This helps the service provider/administrator to identify and manage services within the 7210 SAS platforms.
All services are required to assign a service ID to initially create a service. However, either the service ID or the service name can be used to identify and reference a specific service when it is initially created.
Specifies a unique service name to identify the service. Service names may not begin with an integer (0-9).
spoke-sdp sdp-id:vc-id [create] [no-endpoint]
spoke-sdp sdp-id:vc-id [create] endpoint name
no sdp sdp-id:vc-id
config>mirror>mirror-dest
Supported on all 7210 SAS platforms as described in this document
This command binds an existing (mirror) service distribution path (SDP) to the mirror destination service ID.
The operational state of the SDP dictates the operational state of the SDP binding to the mirror destination. If the SDP is shutdown or operationally down, SDP binding is down. When the binding is defined and the service and SDP are operational, the far-end router defined in the config service sdp sdp-id far-end parameter is considered part of the service ID.
Only one SDP can be associated with a mirror destination service ID. If a second sdp command is executed after a successful SDP binding, an error occurs and the command has no effect on the existing configuration. A no sdp command must be issued before a new SDP binding can be attempted.
An SDP is a logical mechanism that ties a far end router to a specific service without having to define the far-end SAP. Each SDP represents a method to reach a router.
The other method is Multi-Protocol Label Switching (MPLS) encapsulation. Routers support both signaled and non-signaled LSPs (Label Switched Path) though the network. Non-signaled paths are defined at each hop through the network. Signaled paths are protocol communicated from end to end using RSVP. Paths may be manually defined or a constraint based routing protocol (OSPF-TE or CSPF) can be used to determine the best path with specific constraints.
SDPs are created and then bound to services. Many services can be bound to a single SDP. The operational and administrative state of the SDP controls the state of the SDP binding to the service.
An egress service label (Martini VC-Label), used by the SDP to differentiate each service bound to the SDP to the far-end router, must be obtained manually or though signaling with the far end. If manually configured, it must match the ing-svc-label defined for the local router.
No default SDP ID is bound to a mirror destination service ID. If no SDP is bound to the service, the mirror destination is local and cannot be to another router over the core network.
When using remote mirroring with spoke-SDP configured as a mirror destination, users must allocated resources of another port for use by this features. Refer the mirror configuration notes preceding Configuration notes.
The no form of this command removes the SDP binding from the mirror destination service. When removed, no packets are forwarded to the far-end (destination) router from that mirror destination service ID.
Specifies a locally unique SDP identification (ID) number. The SDP ID must exist. If the SDP ID does not exist, an error occurs and the command does not execute.
For mirror services, the vc-id defaults to the service-id. However, there are scenarios where the vc-id is being used by another service. In this case, the SDP binding cannot be created. So, to avoid this, the mirror service SDP bindings now accepts vc-ids.
Specifies the virtual circuit identifier.
Specifies the name of the endpoint associated with the SAP.
Removes the association of a SAP or a SDP with an explicit endpoint name.
egress
config>mirror>mirror-dest>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure spoke SDP egress parameters.
vc-label egress-vc-label
no vc-label [egress-vc-label]
config>mirror>mirror-dest>spoke-sdp>egress
Supported on all 7210 SAS platforms as described in this document
This command configures the spoke-SDP egress VC label.
Specifies a VC egress value that indicates a specific connection.
egress
config>mirror>sap
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
Commands in this context configure QoS egress policies for this SAP.
[no] qos policy-id
config>mirror>sap>egress
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command configures the QoS policy for the mirror destination SAP egress. The SAP egress QoS policy to use is specified using the policy ID and must have been configured before associating this policy with the SAP. The SAP egress policy can be configured using the commands under the context config>qos>sap-egress.
When a SAP egress policy is associated with the SAP configured as a mirror destination, the queue associated with FC specified with the CLI command config>mirror>mirror-dest>fc is used for traffic sent out of the mirror destination SAP. The policy allows the user to specify the amount of buffers, the WRED policy, the shaping rate and the marking values to use for the mirrored copy.
On the 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12, this command is available only when SAP-based egress queuing is configured. The command is not available when port-based egress queuing is configured.
The no form of this command associates the default SAP egress QoS policy with the SAP.
no qos
Specifies the QoS policy to be associated with SAP egress. The QoS policy referred to by the policy-id is configured using the commands under config>qos>sap-egress.