The command outputs in the following section are examples only; actual displays may differ depending on supported functionality and user configuration.
This command displays set debug points.
This command displays active subscriber information and only applies to the 7450 ESS and 7750 SR.
Displays mirror services.
If no optional parameters are specified, all services defined on the system are displayed.
Label | Description |
Service Id | The service identifier. |
Type | Specifies the service type configured for the service ID. |
Adm | The desired state of the service. |
Opr | The operating state of the service. |
CustomerID | The ID of the customer who owns this service. |
Last Mgmt Change | The date and time of the most recent management-initiated change to this service. |
Displays Lawful Intercept (LI) information.
Displays Lawful Intercept mirror configuration and operation information.
Displays Lawful Intercept mirror IPv4 or IPv6 address filter configuration and operation information.
Displays Lawful Intercept event log information.
Displays information for specified log.
Displays Lawful Intercept status information.
Displays Lawful Intercept mirror configuration and operation information.
This command displays mirror configuration and operation information.
Table 4 lists and describes the mirroring output fields:
Label | Description |
Service Id | The service ID associated with this mirror destination. |
Type | Entries in this table have an implied storage type of “volatile”. The configured mirror source information is not persistent. |
Admin State | Up — The mirror destination is administratively enabled. |
Down — The mirror destination is administratively disabled. | |
Oper State | Up — The mirror destination is operationally enabled. |
Down — The mirror destination is operationally disabled. | |
Forwarding Class | The forwarding class for all packets transmitted to the mirror destination. |
Remote Sources | Yes — A remote source is configured. |
No — A remote source is not configured. | |
Enable Port Id | Yes — PPP Port ID Mirroring is enabled. |
No — PPP Port ID Mirroring is disabled. | |
Slice | The value of the slice-size, the maximum portion of the mirrored frame that will be transmitted to the mirror destination. Any frame larger than the slice-size will be truncated to this value before transmission to the mirror destination. A value of 0 indicates that mirrored packet truncation based on slice size is disabled. |
Destination SAP | The ID of the access port where the Service Access Point (SAP) associated with this mirror destination service is defined. |
Egr QoS Policy | This value indicates the egress QoS policy ID. A value of 0 indicates that no QoS policy is specified. |
This command configures mirror source parameters for a mirrored service.
The mirror-source command is used to enable mirroring of packets specified by the association of the mirror-source to sources of packets defined within the context of the mirror-dest-service-id. The mirror destination service must already exist within the system.
A mirrored packet cannot be mirrored to multiple destinations. If a mirrored packet is properly referenced by multiple mirror sources (for example, a SAP on one mirror-source and a port on another mirror-source), then the packet is mirrored to a single mirror-dest-service-id based on the following hierarchy:
Filter entry
The hierarchy is structured so the most specific match criteria has precedence over a less specific match. For example, if a mirror-source defines a port and a SAP on that port, then the SAP mirror-source is accepted and the mirror-source for the port is ignored because of the hierarchical order of precedence.
The mirror-source configuration is not saved when a configuration is saved. A mirror-source manually configured within an ASCII configuration file will not be preserved if that file is overwritten by a save command. Define the mirror-source within a file associated with a config exec command to make a mirror-source persistent between system reboots.
By default, all mirror-dest service IDs have a mirror-source associated with them. The mirror-source is not technically created with this command. Instead the service ID provides a contextual node for storing the current mirroring sources for the associated mirror-dest service ID. The mirror-source is created for the mirror service when the operator enters the debug>mirror-source svcId for the first time. If the operator enters li>li-source svcId for the first time, an LI source is created for the mirror service. The mirror-source is also automatically removed when the mirror-dest service ID is deleted from the system.
The no form of the command deletes all related source commands within the context of the mirror-source service-id. The command does not remove the service ID from the system.
No mirror source match criteria is defined for the mirror destination service.
This command configures mirroring of ingress MPLS frames with a specific MPLS label to a mirror destination.
This command enables mirroring of packets that match specific entries in an existing IP filter.
The ip-filter command directs packets which match the defined list of entry IDs to be mirrored to the mirror destination referenced by the mirror-dest-service-id of the mirror-source.
The IP filter must already exist in order for the command to execute. Filters are configured in the config>filter context. If the IP filter does not exist, an error will occur. If the filter exists but has not been associated with a SAP or IP interface, an error is not generated but mirroring will not be enabled (there are no packets to mirror). Once the IP filter is defined to a SAP or IP interface, mirroring is enabled.
If the IP filter is defined as ingress, only ingress packets are mirrored. Ingress mirrored packets are mirrored to the mirror destination prior to any ingress packet modifications.
If the IP filter is defined as egress, only egress packets are mirrored. Egress mirrored packets are mirrored to the mirror destination after all egress packet modifications.
An entry-id within an IP filter can only be mirrored to a single mirror destination. If the same entry-id is defined multiple times, an error occurs and only the first mirror-source definition is in effect.
By default, no packets matching any IP filters are mirrored. Mirroring of IP filter entries must be explicitly defined.
The no ip-filter command, without the entry keyword, removes mirroring on all entry-id’s within the ip-filter-id.
When the no command is executed with the entry keyword and one or more entry-id’s, mirroring of that list of entry-id’s is terminated within the ip-filter-id. If an entry-id is listed that does not exist, an error will occur and the command will not execute. If an entry-id is listed that is not currently being mirrored, no error will occur for that entry-id and the command will execute normally.
IP filter mirroring is not defined.
If an entry-id does not exist within the IP filter, an error occurs and the command will not execute.
If the filter’s entry-id is renumbered within the IP filter definition, the old entry-id is removed but the new entry-id must be manually added to the configuration to include the new (renumbered) entry’s criteria.
This command configures AA ISAgroup as a mirror source for this mirror service. Traffic is mirrored after AA processing takes place on AA ISAs of the group, therefore, any packets dropped as part of that AA processing are not mirrored.
This command enables mirroring of packets that match specific entries in an existing MAC filter.
The mac-filter command directs packets which match the defined list of entry IDs to be mirrored to the mirror destination referenced by the mirror-dest-service-id of the mirror-source.
The MAC filter must already exist in order for the command to execute. Filters are configured in the config>filter context. If the MAC filter does not exist, an error will occur. If the filter exists but has not been associated with a SAP or IP interface, an error is not be generated but mirroring will not be enabled (there are no packets to mirror). Once the filter is defined to a SAP or MAC interface, mirroring is enabled.
If the MAC filter is defined as ingress, only ingress packets are mirrored. Ingress mirrored packets are mirrored to the mirror destination prior to any ingress packet modifications.
If the MAC filter is defined as egress, only egress packets are mirrored. Egress mirrored packets are mirrored to the mirror destination after all egress packet modifications.
An entry-id within a MAC filter can only be mirrored to a single mirror destination. If the same entry-id is defined multiple times, an error occurs and only the first mirror-source definition is in effect.
By default, no packets matching any MAC filters are mirrored. Mirroring of MAC filter entries must be explicitly defined.
The no mac-filter command, without the entry keyword, removes mirroring on all entry-id’s within the mac-filter-id.
When the no command is executed with the entry keyword and one or more entry-id’s, mirroring of that list of entry-id’s is terminated within the mac-filter-id. If an entry-id is listed that does not exist, an error will occur and the command will not execute. If an entry-id is listed that is not currently being mirrored, no error will occur for that entry-id and the command will execute normally.
No MAC filter mirroring defined.
Each entry-id must exist within the mac-filter-id. If the entry-id is renumbered within the MAC filter definition, the old entry-id is removed from the list and the new entry-id will need to be manually added to the list if mirroring is still desired.
If no entry-id entries are specified in the command, mirroring will not occur for that MAC filter ID. The command will have no effect.
This command enables mirroring of traffic ingressing or egressing a port (Ethernet port, SONET/SDH channel, TDM channel, or Link Aggregation Group (LAG)).
The port command associates a port or LAG to a mirror source. The port is identified by the port-id. The defined port may be Ethernet, Access or network, SONET/SDH, or TDM channel access. A network port may be a single port or a Link Aggregation Group (LAG) ID. When a LAG ID is given as the port-id, mirroring is enabled on all ports making up the LAG. If the port is a SONET/SDH interface, the channel-id must be specified to identify which channel is being mirrored (applies to the 7450 ESS and 7750 SR). Either a LAG port member or the LAG port can be mirrored.
The port is only referenced in the mirror source for mirroring purposes. The mirror source association does not need to be removed before deleting the card to which the port belongs. If the port is removed from the system, the mirroring association will be removed from the mirror source.
The same port may not be associated with multiple mirror source definitions with the ingress parameter defined. The same port may not be associated with multiple mirror source definitions with the egress parameter defined.
If a SAP is mirrored on an access port, the SAP mirroring will have precedence over the access port mirroring when a packet matches the SAP mirroring criteria. Filter and label mirroring destinations will also precedence over a port-mirroring destination.
If the port is not associated with a mirror-source, packets on that port will not be mirrored. Mirroring may still be defined for a SAP, label or filter entry, which will mirror based on a more specific criteria.
The encapsulation type on an access port or channel cannot be changed to Frame Relay if it is being mirrored (applies to the 7750 SR and 7450 ESS).
The no port command disables port mirroring for the specified port. Mirroring of packets on the port may continue due to more specific mirror criteria. If the egress or ingress parameter keywords are specified in the no command, only the ingress or egress mirroring condition will be removed.
No ports are defined.
The following syntax applies to the 7750 SR:
port-id | slot/mda/port [.channel] | ||
eth-sat-id | esat-id/slot/port | ||
esat | keyword | ||
id | 1 to 20 | ||
pxc-id | pxc-id.sub-port | ||
pxc | keyword | ||
id | 1 to 64 | ||
sub-port | a, b | ||
aps-id | aps-group-id[.channel] | ||
aps | keyword | ||
group-id | 1 to 64 | ||
bundle ID | bundle-type-slot/mda.bundle-num | ||
bundle | keyword | ||
type | ima, ppp | ||
bundle-num | 1 to 336 | ||
bgrp-id | bpgrp-type-bpgrp-num | ||
bgrp | keyword | ||
type | ima, ppp | ||
bgrp-num | 1 to 2000 | ||
ccag-id | ccag-id.path-id cc-type:cc-id | ||
ccag | keyword | ||
id | 1 to 8 | ||
path-id | a,b | ||
cc-type | sap-net, .net-sap | ||
cc-id | 0 to 4094 |
The following syntax applies to the 7950 XRS:
port-id | slot/mda/port [.channel] | ||
eth-sat-id | esat-id/slot/port | ||
esat | keyword | ||
id | 1 to 20 | ||
pxc-id | pxc-id.sub-port | ||
pxc | keyword | ||
id | 1 to 64 | ||
sub-port | a, b |
![]() | Note:
On the 7950 XRS, the XMA ID takes the place of the MDA. |
This command enables mirroring of traffic ingressing or egressing a service access port (SAP). A SAP that is defined within a mirror destination cannot be used in a mirror source. The mirror source SAP referenced by the sap-id is owned by the service ID of the service in which it was created. The SAP is only referenced in the mirror source name for mirroring purposes. The mirror source association does not need to be removed before deleting the SAP from its service ID. If the SAP is deleted from its service ID, the mirror association is removed from the mirror source.
More than one SAP can be associated within a single mirror-source. Each SAP has its own ingress and egress parameter keywords to define which packets are mirrored to the mirror destination.
The SAP must be valid and properly configured. If the associated SAP does not exist, an error occurs and the command will not execute.
The same SAP cannot be associated with multiple mirror source definitions for ingress packets. The same SAP cannot be associated with multiple mirror source definitions for egress packets.
If a particular SAP is not associated with a mirror source name, then that SAP will not have mirroring enabled for that mirror source.
Note that the ingress and egress options cannot be supported at the same time on a CEM encap-type SAP. The options must be configured in either the ingress or egress contexts (applies to the 7750 SR and 7950 XRS).
The no form of the command disables mirroring for the specified SAP. All mirroring for that SAP on ingress and egress is terminated. Mirroring of packets on the SAP can continue if more specific mirror criteria is configured. If the egress or ingress parameter keywords are specified in the no command, only the ingress or egress mirroring condition is removed.
No SAPs are defined by default.
This command adds hosts of a subscriber to mirroring service and only applies to the 7450 ESS and 7750 SR.
This command enables ingress MPLS frame mirroring based on the top-of-stack MPLS label. Multiple labels can be defined simultaneously.
The ingress-label command is used to mirror ingressing MPLS frames with specific MPLS labels to a specific mirror destination. The ingress label must be at the top of the label stack and can only be mirrored to a single mirror destination. If the same label is defined with multiple mirror destinations, an error is generated and the original mirror destination remains.
The ingress-label mirror source overrides all other mirror source definitions. The MPLS frame is mirrored to the mirror destination as it is received on the ingress network port. The router MPLS label space is global for the system. A specific label is mirrored to the mirror destination regardless of the ingress interface.
By default, no ingress MPLS frames are mirrored. The ingress-label command must be executed to start mirroring on a specific MPLS label.
The no ingress-label command removes all label mirroring for the mirror source. To stop mirroring on specific labels, use the no ingress-label label form of the command. Multiple labels may be given in a single no ingress-label command.
No ingress MPLS labels for mirroring are defined.
If the label does not exist on any ingress network ports, no packets are mirrored for that label. An error will not occur. Once the label exists on a network port, ingress mirroring commences for that label.