The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
TAP and Split TAP Support for Protected Interfaces
Cisco IOS XE Cupertino 17.7.1
TAP and split TAP support for the following protected interfaces on both receive and transmit direction:
Automatic Protection Switching (APS)
Unidirectional Path Switching Ring (UPSR)
Card Protection Group (CPG)
With this feature support, you can perform monitoring and debugging on these virtual protection interfaces.
Test Access Port (TAP) or Test Access Digroup (TAD)
Cisco IOS XE Bengaluru 17.6.1
Support for Test access port or digroup (TAP/TAD) in the following aspects:
Non-intrusive monitoring for both receive and transmit directions.
Split and terminate cross connection for intrusive testing in both directions. The TAP feature helps in monitoring and debugging
purpose.
RSP-based Non-Intrusive Monitor Ports
Cisco IOS XE Bengaluru 17.5.1
This feature allows you to transmit data to multiple connections from a single source using the RSP-based non-intrusive monitor
port TAP port. It establishes a one-way cross-connect listen connection that listens to either the source or destination
of an existing cross-connect or a local connect connection. This feature is only supported on Cisco RSP3 module.
This feature is supported on NCS 4206/4216 routers.
This feature is supported on the following CEM interface modules:
48-port T1/E1 CEM interface module
48-port T3/E3 CEM interface module
1-port OC48/ STM-16 or 4-port OC-12/OC-3 / STM-1/STM-4 + 12-Port T1/E1 + 4-Port T3/E3 CEM interface module
Prior to Cisco IOS XE Bengaluru Release 17.5.1, it was not possible to transmit data to
multiple connections from a single CEM source.
With Cisco IOS XE Bengaluru Release 17.5.1, you can transmit data to multiple connections from a single source using the RSP-based
non-intrusive monitor port or Terminal Access Point (TAP) port. The destination port at which the traffic is monitored is
a listen-only port. This port can only receive traffic but cannot transmit. It establishes a one-way cross-connect listen
connection that listens to either the source or destination of an existing cross-connect or a local connect connection. The
listen connection takes a standard cross-connect and sends the traffic to multiple 'listen only' destinations. Thus, the data
can be transmitted to multiple connections from a single source. This feature is supported on Cisco RSP3 module.
This feature is supported on the following CEM interface modules:
48-port T1/E1 CEM interface module
48-port T3/E3 CEM interface module
1-port OC48/ STM-16 or 4-port OC-12/OC-3 / STM-1/STM-4 + 12-Port T1/E1 + 4-Port T3/E3 CEM interface module
Starting with Cisco IOS XE Bengaluru 17.6.1, you can enable TAP or TAD point to monitor the traffic as listen-only connections
in the following directions for local connect and/or cross-connect scenarios:
Receive direction (Rx)
Transmit direction (Tx)
The default TAP configuration is Tx and the Tx direction support is available from Cisco IOS XE Bengaluru 17.5.1.
In addition, you can split the TAP or TAD session and monitor for intrusive testing. The original traffic is affected unlike
the Tx and Rx where the traffic is replicated.
The split TAP and monitor session supports in the following directions:
Split Receive direction (Split-Rx)
Split Transmit direction (Split-Tx)
The directions Tx or Rx is considered with respect to the core interface in the network.
Source and destination ports can be in the same or different router.
TAP Support for Protected Interfaces
Starting with Cisco IOS XE Cupertino 17.7.1, you can enable TAP or split TAP for the following protected interfaces on both
receive and transmit direction:
Automatic Protection Switching (APS)
Unidirectional Path Switching Ring (UPSR)
Card Protection Group (CPG)
UPSR Protection
SONET local connect and cross connect are supported at VT-15 CEP, STS-1c, STS-3c, STS-12c, and STS-48c levels. UPSR is also
supported on TDM endpoints that are mapped to a pseudowire. T1 SAToP, T3 SAToP, and CT3 are supported on an UPSR ring only
with local connect mode.
Starting with Cisco IOS XE Fuji 16.9.x, the cross connect of T1, T3, and CT3 circuits to UPSR is supported.
Single TAP Destination
In the figure below, the ingress traffic at port A is tapped at port C. Port C is a
listen-only port, which can only receive the traffic but cannot transmit. Thus, the
traffic is transmitted from port A to port B and from port A to port C. Port C can be
present on the same IM or on different IMs of the same router as that of port A. Port C
can be present on different routers (remote nodes) connected via a pseudowire.
Multiple TAP Destinations
In the figure below, the ingress traffic at port A is tapped at the listen-only ports C, D, E, and F. Thus, the traffic is
transmitted from port A to ports B, C, D, E, and F. Ports C, D, E, and F can be present on the same IM or on different IMs
of the same router as that of port A. Port C, D, E, and F can be present on different routers (remote nodes) connected via
a pseudowire to port A.
Restrictions
SSO is not supported.
High availability is not supported.
For releases prior to Cisco IOS XE Bengaluru 17.6.1, to configure TAP on an original xconnect or to create a TAP xconnect
connection with more than 12 circuits, use the following command:
no cef table output-chain build indirection
You must configure the above-mentioned command before configuring TAP for L2VPN. This command increases the convergence on
all existing circuits in the router on core flaps.
The range of monitor session ID for CEM interfaces is from 16 to 1015.
This feature is not supported on 1-port OC-192 Interface module or 8-port Low Rate Interface Module.
This feature is not supported on circuits with protected core, FRR core, tunnel core, or with ECMP.
TAP xconnects are not supported on protected core, FRR core, tunnel core, or with ECMP.
When you first configure TAP on a circuit, there is a negligible traffic drop on the original circuit.
Configuration under monitor is applied only after you exit the privilege mode. Hence, to apply any changes to the existing
source or direction, ensure that you first unconfigure the existing source or direction before reconfiguring the feature.
The split-Rx configuration is not supported on source interface for local connection.
In SAToP, the loop code detection is disabled by default. Both ESF/FDL loop code and IBOC loop code are transparently sent
to CPE.
In CESoP, the loop code detection is not disabled by default. Under controller configuration, use the rem-loop-detect-disable command to disable loop code detection.
If you are not using STE with unidirectional TAP (Tx/Rx), then the design consideration should be taken to handle control
packets that are replicated through TAP session configuration.
In local connect, only Tx and split-Tx configurations are supported.
A maximum of 20 tap destinations from a single source is supported. You can tap a maximum of 50 sources. Thus, the total tap
scale is 50X20=1000.
The maximum number of split Tx or split-Rx monitor session that you can configure on a source interface is one.
TAP is not supported when the iMSG VLAN handoff feature is enabled on the same node.
TAP feature is supported only on RSP3 for protected interfaces. In UPSR, some of the configurations are not supported for
the protected interfaces.
The N-bits or P-bits of CEM counter keeps increasing in CEP mode of STS-1E, SONET, or SDH frame. The N-bits or P-bits adjust
the placement of CEP payload in the SONET or SDH frame, but these bits do not correct the clock. The increment of these bits
do not stop until CE and PE clocks are synced with proper clock configuration. This is applicable for all CEM interface modules
except T1 or E1 interface module.
How to configure RSP-based Non-Intrusive Monitor Ports
Scenarios for RSP-based Non-Intrusive Monitoring or TAP Port Configuration
The following scenarios show the different configurations of RSP-based non-intrusive monitoring or TAP ports.
The following table shows the TAP monitor session direction for local and cross connections:
Table 2. TAP/TAD Support Direction for Local and Cross Connections
Pseudowire Type
Monitor Session Direction
Support on Monitor Session Direction
Local Connection
Tx (Passive monitor for traffic transmitted into the pseudowire)
Yes
Rx (Passive monitor for traffic received from the pseudowire)
No
Split-Tx (Intrusive test for TDM traffic transmitted into the pseudowire)
Yes
Split-Rx (Intrusive test for TDM traffic received from the pseudowire)
No
Cross Connection
Tx (Passive monitor for traffic transmitted into the pseudowire)
Yes
Rx (Passive monitor for traffic received from the pseudowire)
Yes
Split-Tx (Intrusive test for TDM traffic transmitted into the pseudowire)
Yes
Split-Rx (Intrusive test for TDM traffic received from the pseudowire)
Yes
Note
If TAP configured with multiple modes, and to verify the correct mirror count details at ingress and egress sides, we recommend
that you use the show cem circuit interface cem<bay/slot/port> <cem-group-no> command. For example, show cem circuit interface cem 0/7/0 0.
Scenario 1: Configure Source, Destination, and TAP Port - Local Node
Consider a scenario, where the traffic originating from the CEM interface A on router R1 is transmitted to the CEM interface
B via the local connect on router R1. Use the feature to tap or transmit this traffic from CEM interface A to the CEM interface
C on the router R1.
The following example shows the configuration of the tap source and destination on the local node:
Verifiy the Port Source and Destination Configuration on Local Node :
Use the show monitor session all command to verify the
configuration:
Router#show monitor session all
Session 20
----------
Type : Remote Source Session
Status : Admin Enabled
Source Ports :
TX Only : CE0/5/16 10
Destination Ports : CE0/3/16 30
Scenario 2: Configure Source and Destination - Local Node and TAP Port - Remote Node
Consider a scenario where CEM interfaces A and B are on the local node (router R1). The traffic is mirrored or tapped from
CEM interface A to the CEM interface C of the remote node (router R2).
The following example shows the configuration of the source and destination on local node and TAP port on remote node:
Use the show monitor session all command to verify the
configuration:
Router#show monitor session all
Session 20
----------
Type : Remote Source Session
Status : Admin Enabled
Source Ports :
TX Only : CE0/5/16 10
Destination Ports : Pseudowire 100
Scenario 3: Configure Source and TAP Port - Local Node and Destination - Remote Node
Consider a scenario, where the traffic originating from the CEM interface A on the local node (router R1) is transmitted to
the CEM interface B via the MPLS core interface on the remote node (router R2). Use the feature to tap or transmit this traffic
from CEM interface A of the local node (router R1) to CEM interface C of the local node (router R1).
The following example shows the configuration of source and TAP port on the local node, and destination on the remote node:
Use the show monitor session all command to verify the configuration:
Router#show monitor session all
Session 20
----------
Type : Remote Source Session
Status : Admin Enabled
Source Ports :
TX Only : CE0/5/16 10
Destination Ports : CE0/5/16 20
Scenario 4: Configure Source - Local Node and TAP Port and Destination - Remote Node
Consider the scenario below, where the traffic originating from the CEM interface A on local node (router R1) is transmitted
to the CEM interface B via the MPLS core interface on the remode node (router R2). Use the feature to tap or transmit this
traffic from CEM interface A of the local node (router R1) to the CEM interface C of the remote node (router R2).
The following example shows the configuration of source on the local node, and TAP port and destination on the remote node:
Use the show monitor session all command to verify the configuration:
Router#show monitor session all
Session 20
----------
Type : Remote Source Session
Status : Admin Enabled
Source Ports :
TX Only : CE0/5/16 10
Destination Ports : Pseudowire 200
Scenario 5: Configure Source - Local Node and Destination and TAP Port - Different Remote Nodes
Consider a scenario where all the source, destination, and tap interfaces are on different routers. In this scenario, the
CEM interface A on the local node (router R1) and the CEM interface B on the remote node (router R2) are cross-connected.
The traffic is tapped from the CEM interface A on the local node (router R1) to the CEM interface C on the different remote
node (router R3).
The following example shows the configuration of source on local node, and destination and TAP port on different remote nodes:
Use the show monitor session all command to verify the
configuration:
Router#show monitor session all
Session 20
----------
Type : Remote Source Session
Status : Admin Enabled
Source Ports :
TX Only : CE0/5/16 10
Destination Ports : Pseudowire 200
Scenario 6 - Configure Monitor Rx
Consider a scenario, where the traffic originating from the CEM interface B on the local node (router R2) is transmitted to
the CEM interface A via the MPLS core interface on the remote node (router R1). Create a TAP C on R1 to monitor the Rx traffic.
The following example shows the configuration of monitor Rx session:
Verify if the L2VPN cross connect is up on Router R1
router#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri mpls 10.2.2.2:100 UP ac CE0/5/16:0(CESoPSN Basic) UP
Verify if both the cross connections are up and running on Router R1
PE1#sh xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri mpls 10.2.2.2:100 UP ac CE0/5/16:0(CESoPSN Basic) UP
UP pri ac MONITOR:20(CESoPSN Basic) UP ac CE0/5/16:20(CESoPSN Basic) UP
Verify CEM counters on Router R1
Use the show cem circuit detail command to verify the CEM counters configuration:
Router#show cem circuit detail
CEM0/5/16, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 1, VTG: 1, T1: 1, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 4)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 3000 Dropped: 0
Egress Pkts: 3000 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
CEM0/5/16, ID: 20, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 2, VTG: 1, T1: 1, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 4)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 3000 Dropped: 0
Egress Pkts: 3000 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
Verify TAP Port Configuration on Router R1
Use the show monitor session all to verify the configuration:
Router#show monitor session all
Session 20
----------
Type : Remote Source Session
Status : Admin Enabled
Source Ports :
RX Only : CE0/5/16 0
Destination Ports : CE0/5/16 20
Scenario 7 - Configure Monitor Split-Rx
Consider a scenario, where the traffic originating from the CEM interface B on the local node (router R2) is transmitted to
the CEM interface A via the MPLS core interface on the remote node (router R1). The traffic flows from interface B to interface
A. Configure split-Rx on interface C. The traffic from interface B to interface A is affected. The traffic flows from interface
B to interface C.
The following example shows the configuration of monitor Split Rx session:
Verify that the L2VPN cross connect is Up on Router R1
router#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri mpls 10.2.2.2:100 UP ac CE0/5/16:0(CESoPSN Basic) UP
Verify if both the cross connections are Up on Router R1
router#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri mpls 10.2.2.2:100 UP ac CE0/5/16:0(CESoPSN Basic) UP
UP pri ac MONITOR:20(CESoPSN Basic) UP ac CE0/5/16:20(CESoPSN Basic) UP
Verify CEM counters on Router R1
Use the show cem circuit detail command to verify the CEM counters configuration:
Router#show cem circuit detail
CEM0/5/16, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 1, VTG: 1, T1: 1, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 0)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 3000 Dropped: 0
Egress Pkts: 0 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 3000 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 3000
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 186
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 3000 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
CEM0/5/16, ID: 20, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 2, VTG: 1, T1: 1, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 3)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 3000 Dropped: 0
Egress Pkts: 3000 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
Verify TAP Port Configuration on Router R1
Use the show monitor session<session-id> or show monitor session all to verify the configuration:
Router#show monitor session 20
Session 20
----------
Type : Remote Source Session [SPLIT]
Status : Admin Enabled
Source Ports :
RX Only : CE0/5/16 0
Destination Ports : CE0/5/16 20
Scenario 8 - Configure Monitor Split-Tx
Consider a scenario, where the traffic originating from the CEM interface A on the local node (router R1) is transmitted to
the CEM interface B via the MPLS core interface on the remote node (router R2). The traffic flows from interface A to interface
B. Configure split-Tx on interface C. The traffic from interface A to interface B is affected. The traffic flows from interface
A to interface C.
The following example shows the configuration of monitor Split Tx session:
Verify that the L2VPN cross connect is Up on Router R1
router#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri mpls 10.2.2.2:100 UP ac CE0/5/16:0(CESoPSN Basic) UP
Verify if both the cross connections are Up on Router R1
router#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri mpls 10.2.2.2:100 UP ac CE0/5/16:0(CESoPSN Basic) UP
UP pri ac MONITOR:20(CESoPSN Basic) UP ac CE0/5/16:20(CESoPSN Basic) UP
Verify CEM counters on R1
Use the show cem circuit detail command to verify the CEM counters configuration:
Router#show cem circuit detail
CEM0/5/16, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 1, VTG: 1, T1: 1, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 4)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 3000 Dropped: 0
Egress Pkts: 3000 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
CEM0/5/16, ID: 20, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 2, VTG: 1, T1: 1, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 3)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 3000 Dropped: 0
Egress Pkts: 3000 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
Verify CEM counters on Router R2
Use the show cem circuit detail command to verify the CEM counters configuration:
Router#show cem circuit detail
CEM0/2/19, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 1, VTG: 1, T1: 1, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 0)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 5000 Dropped: 0
Egress Pkts: 0 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 5000 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 5000
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 312
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 5000 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
Verify TAP Port Configuration on Router R1
Use the show monitor session<session-id> orshow monitor session all to verify the configuration:
Router#show monitor session 20
Session 20
----------
Type : Remote Source Session [SPLIT]
Status : Admin Enabled
Source Ports :
TX Only : CE0/5/16 0
Destination Ports : CE0/5/16 20
Scenario 9 - Configure TAP for APS Protection
Consider a scenario, where the interface A is configured with APS group on router R1 and interface B is configured without
APS group on router R2. The traffic originating from the CEM interface B on the local node (router R2) is transmitted to the
CEM interface A via the MPLS core interface on the remote node (router R1). Create a TAP C on R1 to monitor the Rx traffic.
The following example shows the configuration of TAP for APS:
Create an APS Group (Working Controller) on Router R1
If there is no back to back connection on work or protected interfaces and to avoid alarms, we recommend that you configure
loopback local on the work and protected interaces using the following command:
loopback local
Create an APS Group (Protect Controller) on Router R1
If there is no back to back connection on work or protected interfaces and to avoid alarms, we recommend that you configure
loopback local on the work and protected interaces using the following command:
Verify if the L2VPN cross connect is up on Router R1
router#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri mpls 10.2.2.2:100 UP ac CE2:0(CESoPSN Basic) UP
Verify if both the cross connections are up and running on Router R1
PE1#sh xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri mpls 10.2.2.2:100 UP ac CE2:0(CESoPSN Basic) UP
UP pri ac MONITOR:20(CESoPSN Basic) UP ac CE0/5/16:20(CESoPSN Basic) UP
Verify CEM counters on Router R1
Use the show cem circuit detail command to verify the CEM counters configuration:
Router#show cem circuit detail
CEM-ACR 2, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 1, VTG: 1, T1: 1, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 4)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 3000 Dropped: 0
Egress Pkts: 3000 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
CEM0/5/16, ID: 20, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 1, VTG: 1, T1: 1, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 4)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 3000 Dropped: 0
Egress Pkts: 3000 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
Verify CEM counters on Router R2
Use the show cem circuit detail command to verify the CEM counters configuration:
Router#show cem circuit detail
CEM0/13/19, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 1, VTG: 1, T1: 1, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 4)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 3000 Dropped: 0
Egress Pkts: 3000 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
Verify TAP Port Configuration on Router R1
Use the show monitor session all to verify the configuration:
Router#show monitor session all
Session 20
----------
Type : Remote Source Session
Status : Admin Enabled
Source Ports :
RX Only : CEM-ACR 2 0
Destination Ports : CE0/5/16 20
Scenario 10 - Configure TAP for CPG Protection
Consider a scenario, where the CPG controller is configured on router R1 with CEM, and non-CPG controller is configured on
the same router R1 with CEM group. Create a TAP C on R1 to monitor the Tx traffic.
Configure Card Protection Group
enableconfigure terminal card-protection4primary slot 0 bay 0backup slot 0 bay 5end
Note
(Optional) By default the card protection is non-revertive, if necessary you can change to revertive.
card-protection 4revertive time [30-720]end
Configures CEM on T1 Controller—Source Node (Router 1)
Use the show cem circuit detail command to verify the CEM counters configuration:
Router#show cem circuit detail
CEM8/3/0, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE
Mode :Unchannelized, CEM Mode: T1-SAToP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 3)
Payload Size: 1024
Framing: Unframed
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 8102584 Dropped: 0
Egress Pkts: 8105758 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 6400
Generated Lbits: 8102584 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
CEM0/3/0, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE
Mode :Unchannelized, CEM Mode: T1-SAToP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 3)
Payload Size: 1024
Framing: Unframed
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 8102584 Dropped: 0
Egress Pkts: 8105758 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 6400
Generated Lbits: 8102584 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
Verify TAP Port Configuration
Use the show monitor session all to verify the configuration:
Router#show monitor session all
Session 20
----------
Type : Remote Source Session
Status : Admin Enabled
Source Ports :
TX Only : CE8/3/0 0
Destination Ports : CE0/3/0 0
Scenario 11 - Configure TAP for UPSR Protection
Consider a scenario, where the UPSR work and protect paths are created on router R1, and original destination is created on
router R2. The traffic originating from the CEM interface B on the router R2 is transmitted to the CEM interface A via the
MPLS core interface on the remote node (router R1). Create a TAP C on R1 to monitor the Rx traffic.
The following example shows the configuration of TAP for UPSR:
Create UPSR on Router R1
protection-group 2 type vt1.5controller protection-group 2type vt1.5cem-group 16002 unframed
Verify if the L2VPN cross connect is up on Router R1
router#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri mpls 10.2.2.2:100 UP ac CEM-PG 2:16002(CESoPSN Basic) UP
Verify if both the cross connections are up and running on Router R1
PE1#sh xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri mpls 10.2.2.2:100 UP ac CEM-PG 2:16002(CESoPSN Basic) UP
UP pri ac MONITOR:20(CESoPSN Basic) UP ac CE0/5/16:20(CESoPSN Basic) UP
Verify CEM counters on Router R1
Use the show cem circuit detail command to verify the CEM counters configuration:
Router#show cem circuit detail
CEM-PG 2, ID: 16002, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 1, VTG: 1, T1: 2, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 4)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 3000 Dropped: 0
Egress Pkts: 3000 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
CEM0/5/16, ID: 20, Line: UP, Admin: UP, Ckt: ACTIVE
Path Mode : VT15, STS: 1, VTG: 1, T1: 2, CEM Mode: T1-CESoP
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8 0x8
Dejitter: 6 (In use: 4)
Payload Size: 192
Framing: Framed (DS0 channels: 1-24)
CEM Defects Set
None
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 3000 Dropped: 0
Egress Pkts: 3000 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
Generated Lbits: 0 Received Lbits: 0
Generated Rbits: 0 Received Rbits: 0
Generated Mbits: 0 Received Mbits: 0
Verify TAP Port Configuration on Router R1
Use the show monitor session all to verify the configuration:
Router#show monitor session all
Session 20
----------
Type : Remote Source Session
Status : Admin Enabled
Source Ports :
RX Only : CEM-PG 2 16002
Destination Ports : CE0/5/16 20