-
Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide
-
Using Cisco IOS Software
-
SIP, SSC, and SPA Product Overview
-
Overview of the SIPs and SSC
-
Configuring the SIPs and SSC
-
Troubleshooting the SIPs and SSC
-
Overview of the ATM SPAs
-
Configuring the ATM SPAs
-
Troubleshooting the ATM SPAs
-
Overview of the CEoP and Channelized ATM SPAs
-
Configuring the CEoP and Channelized ATM SPAs
-
Overview of the Ethernet SPAs
-
Configuring the Fast Ethernet and Gigabit Ethernet SPAs
-
Troubleshooting the Fast Ethernet and Gigabit Ethernet SPAs
-
Overview of the POS SPAs
-
Configuring the POS SPAs
-
Overview of the Serial SPAs
-
Configuring the 8-Port Channelized T1/E1 SPA
-
Configuring the 2-Port and 4-Port Clear Channel T3/E3 SPAs
-
Configuring the 2-Port and 4-Port Channelized T3 SPAs
-
Configuring the 1-Port Channelized OC-3/STM-1 SPA
-
Configuring the 4-Port Serial Interface SPA
-
Troubleshooting the Serial SPAs
-
Overview of the IPSec VPN SPA
-
Configuring VPNs on the IPSec VPN SPA
-
Configuring VPNs in VRF Mode
-
Configuring IPSec VPN Fragmentation and MTU
-
Configuring IKE Features Using the IPSec VPN SPA
-
Configuring Enhanced IPSec Features Using the IPSec VPN SPA
-
Configuring PKI Using the IPSec VPN SPA
-
Configuring Advanced VPNs Using the IPSec VPN SPA
-
Configuring Duplicate Hardware Configurations and IPSec Failover Using the IPSec VPN SPA
-
Configuring Monitoring and Accounting for the IPSec VPN SPA
-
Troubleshooting the IPSec VPN SPA
-
Upgrading Field-Programmable Devices
-
Table Of Contents
Configuring the CEoP and Channelized ATM SPAs
Specifying the Interface Address on a SPA
Configuring Port Usage (Overview)
Configuring the 24-Port Channelized T1/E1 ATM CEoP SPA
Configuring the 2-Port Channelized T3/E3 ATM CEoP SPA
Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SONET VT1.5
Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-4 C-12
Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-3 C-11
Configuration Guidelines and Restrictions
Configuring a CEM Class (Optional)
Configuring TDM Local Switching
Configuring Pseudowire Redundancy (Optional)
Configuring the SPA for Clear-Channel ATM
SONET Controller Configuration
SDH Configuration for AU-4 C-12
SDH Configuration for AU-3 C-11
Configuring Inverse Multiplexing over ATM
IMA Link Bundle Configuration Overview
Configuring an IMA Link Bundle
Configuring IMA Group Parameters
Verifying the IMA Configuration
BITS Clock Support—Receive and Distribute—CEoP SPA on SIP-400
Configuring Out-of-Band Clocking
Creating and Configuring the Master Clock Interface
Configuring the Slave Clock Interface
Verifying Out-of-Band Clocking
Removing the Out-of-Band Clocking Configuration
Out-of-Band Clocking Configuration Example
Configuring CEM Circuits for Out-of-Band Clocking Example
Configuring Payload Size (Optional)
Setting the Dejitter Buffer Size
Setting the Idle Pattern (Optional)
Configuring AIS and RAI Alarm Forwarding in CESoPSN Mode on CEoP SPAs
Verifying the Interface Configuration
Configuring the CEoP and Channelized ATM SPAs
This chapter provides information about configuring the Circuit Emulation over Packet (CEoP) shared port adapters (SPAs) on the Cisco 7600 series router. It contains the following sections:
•
Configuring Circuit Emulation
•
•
•
•
For information about managing your system images and configuration files, see the Cisco IOS Configuration Fundamentals Configuration Guide and Cisco IOS Configuration Fundamentals Command Reference publications for your Cisco IOS software release.
For more information about the commands used in this chapter, refer to the Cisco IOS Software Releases 12.2SR Command References and to the Cisco IOS Software Releases 12.2SX Command References. Also refer to the related Cisco IOS Release 12.2 software command reference and master index publications. For more information, see the "Related Documentation" section on page li.
Configuration Tasks
This section describes the most common configurations for the CEoP SPAs on a Cisco 7600 series router. It contains procedures for the following:
•
•
Specifying the Interface Address on a SPA
Four CEoP SPAs can be installed in a SPA interface processor (SIP). Ports are numbered from left to right, beginning with 0. Single-port SPAs use only the port number 0. To configure or monitor SPA interfaces, you need to specify the physical location of the SIP, SPA, and interface in the command-line-interface (CLI). The interface address format is slot/subslot/port, where:
•
•
•
The following example shows how to specify the first interface (0) on a SPA installed in subslot 1 of the SIP in chassis slot 3:
Router(config)# interface cem 3/1/0For more information about how to identify slots and subslots, see the "Identifying Slots and Subslots for SIPs, SSCs, and SPAs" section on page 4-2.
Configuring Port Usage (Overview)
The 24-Port Channelized T1/E1 ATM CEoP SPA and 1-Port Channelized OC-3 STM1 ATM CEoP SPA can be configured to run in the following modes:
•
•
•
The 2-Port Channelized T3/E3 ATM CEoP SPA, introduced in Cisco IOS Release 12.2(33)SRC, can be configured to run in ATM mode. The SPA does not currently support CEM or IMA mode.
The following tables show the commands to configure each of the SPAs for CEM or ATM. Detailed configuration instructions are provided in the sections that follow.
Configuring the 24-Port Channelized T1/E1 ATM CEoP SPA
To configure the 24-Port Channelized T1/E1 ATM CEoP SPA, perform the following steps:
Configuring the 2-Port Channelized T3/E3 ATM CEoP SPA
To configure the 2-Port Channelized T3/E3 ATM CEoP SPA, perform the following steps:
Note
Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SONET VT1.5
To configure the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SONET VT 1.5, perform the following steps:
Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-4 C-12
To configure the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-4 C-12, perform the following steps:
Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-3 C-11
To configure the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-3 C-11, perform the following steps:
Configuring Circuit Emulation
This section provides information about how to configure circuit emulation on a CEoP SPA. Circuit emulation provides a bridge between a time division multiplexed (TDM) network and a packet network (such as Multiprotocol Label Switching [MPLS]). The router encapsulates TDM data in MPLS packets and sends the data over a CEM pseudowire to the remote provider edge (PE) router. Thus, circuit emulation acts like a physical communication link across the packet network.
To configure circuit emulation on a CEoP SPA port, you must do the following:
1.
2.
Figure 10-1 shows the following sample configuration for a CEoP SPA:
•
•
•
–
–
Figure 10-1 TDM Time Slots to Pseudowire Mappings
Configuration Guidelines and Restrictions
Not all combinations of payload-size and dejitter-buffer size are supported. Payload size, or dejitter configurations are rejected at the CLI level in CEM circuit mode on the SPA if they are not compatible. Any incompatible parameter modifications will be rejected and the configuration will fall back to the old dejitter and payload parameters if the parameters are being applied through the cem class template.
For relation between the payload size and the dejitter buffer size on CeoPSN and SaToP T1/E1 frames see Table 9-1, CESoPSN DS0 Lines: Payload and Jitter Limits, Table 9-2, SAToP T1 Frame: Payload and Jitter Limits and Table 9-3, SAToP E1 Frame: Payload and Jitter Limits.
Configuring a CEM Group
To configure a CEM group to represent a CEM circuit on a SPA port, use the following procedure.
Note
•
Configuring a CEM Class (Optional)
To assign CEM parameters to one or more CEM interfaces, you can create a CEM class (template) that defines the parameters and then apply the class to the interfaces.
CEM class parameters can be configured directly on the CEM circuit. The inheritance is as follows:
•
•
•
If the same parameter is configured on the CEM interface and CEM circuit, the value on the CEM circuit takes precedence.
To configure a CEM class, use the following procedure:
Step 1
Router(config)# class cem name
Creates a CEM class to help in configuring parameters in a template and applying parameters at the CEM interface level.
•
Step 2
Router(config-cem-class)# command
Configure CEM parameters by issuing the appropriate commands. See the "Configuring CEM Parameters" section for commands.
In the following example, a CEM class (TDM-Class-A) is configured to set the payload-size and dejitter-buffer parameters:
class cem TDM-Class-Apayload-size 512dejitter-buffer 80exitIn the next example, the CEM parameter settings from TDM-Class-A are applied to CEM interface 2/1/0. Any CEM circuits created under this interface inherit these parameter settings.
int cem 2/1/0class int TDM-Class-Acem 6xconnect 10.10.10.10 2 encap mplsexitConfiguring a CEM Pseudowire
To configure a pseudowire to transport a CEM circuit across the MPLS network, follow this procedure.
Step 1
Router(config)# interface cemslot/subslot/port
Selects the CEM interface where the CEM circuit (group) is located (where slot/subslot is the SPA slot and subslot and port is the SPA port where the interface exists).
Step 2
Router(config-if)# cem group-number
Selects the CEM circuit (group) to configure a pseudowire for.
Step 3
Router(config-if-cem)# command
(Optional) Defines the operating characteristics for the CEM circuit. For command details, see the "Configuring CEM Parameters" section.
Step 4
Router(config-if)# xconnect peer-router-id vcid {encapsulation mpls | pseudowire-class name}
Configures a pseudowire to transport TDM data from the CEM circuit across the MPLS network.
•
•
•
•
Note
Step 5
Router(config-if)# exit
Exits interface configuration mode.
The following sample configuration shows a T1 port on which two CEM circuits (groups) are configured. Each CEM circuit carries data from time slots of the TDM circuit attached to the port.
The two xconnect commands create pseudowires to carry the TDM data across the MPLS network. Pseudowire 2 carries the data from time slots 1, 2, 3, 4, 9, and 10 to the remote PE router at 10.10.10.10. Pseudowire 5 carries the data in time slots 5, 6, 7, 8, and 11 to the remote PE router at 10.10.10.11.
controller t1 2/1/0cem-group 6 timeslots 1-4,9,10cem-group 7 timeslots 5-8,11framing esflinecode b8zsclock source adaptive 6cablelength long -15dbcrc-threshold 512description T1 line to 3rd floor PBXloopback networkno shutdownint cem2/1/0cem 6xconnect 10.10.10.10 2 encap mplscem 7xconnect 10.10.10.11 5 encap mplsConfiguring TDM Local Switching
TDM Local Switching allows switching of Layer 2 data between two CEM interfaces on the same router. The two CEM groups can be on the same physical interface or different physical interfaces; they can be on the same SPA, the same line card, or different line cards.
Note
Use the following guidelines for CEoP Phase 2 TDM Local Switching:
•
•
•
•
•
•
•
Use the following procedure to configure CEoPS Phase 2 TDM Local Switching:
Configuration Example
The following is an example:
Router(config)# interface CEM4/3/0Router(config)# connect cem cem2/1/0 1 cem4/2/0 2Verifying
Use the show connection, show connection all, show connection id conn id, and show connection conn name commands to verify.
Local Switching Redundancy
Local Switching Redundancy provides a backup attachment circuit (AC) when the primary attachment circuit fails. All the ACs must be on same Cisco 7600 series router.
Note
The following combinations of CEM ACs are supported:
•
•
•
Guidelines
Local Switching Redundancy guidelines are as follows:
•
•
•
•
•
•
•
Configuration
Configuration Example
The following is a configuration example for Local Switching Redundancy:
Router(config)# connect cem cem2/1/0 1 cem4/2/0 2Router(config)# backup interface cem 3/0/0 3Verifying
Use the show xconnect all command to check the status of the backup and primary circuits.
Configuring ATM
In addition to CEM mode, CEoP SPAs support ATM. When configured to operate in ATM mode, CEoP SPAs support the ATM features listed in Chapter 9, "Overview of the CEoP and Channelized ATM SPAs."
CEoP SPAs also support inverse multiplexing over ATM (IMA), which allows you to combine multiple ATM links into a single high-bandwidth logical link. For more information on IMA, see the "Configuring Inverse Multiplexing over ATM" section.
CEoP SPAs support ATM operation in clear-channel or channelized mode:
•
•
Note
ATM Connections Per SPA
Use the following guidelines:
•
•
–
–
•
ATM Configuration Overview
To configure a port on a CEoP SPA for ATM operation, you must:
1.
2.
3.
ATM and IMA Interfaces
IMA interfaces may consist of groups of T1s or E1s. IMA is not supported on the 2-Port Channelized T3/E3 ATM CEoP SPA.
The router creates an ATM interface for each T3 or E3 port (or channelized T1 or E1) that is configured for ATM mode. The interface has the format atmslot/subslot/port (where slot/subslot identifies the SPA slot and subslot and /port identifies the port [for example, atm2/1/0]).
If you configure IMA, the router creates an interface to represent each IMA group (link bundle). The interface has the format atmslot/subslot/imagroup-id (where slot/subslot identifies the SPA slot and subslot and group-id identifies the IMA group number [for example, atm2/1/ima0]).
Configuring an ATM Pseudowire
To configure a pseudowire for an ATM connection or an IMA link bundle, perform these steps. The pseudowire is used to carry the ATM data across the MPLS network.
Step 1
Router(config)# interface atmslot/subslot/port
or
Router(config)# interface atmslot/subslot/imagroup-id
Selects the ATM interface to configure the pseudowire for (where slot/subslot is the SPA slot and subslot, and /port is the SPA port where the interface exists).
For IMA, the format is atmslot/subslot/imagroup-id (where slot/subslot/ identifies the SPA slot and subslot and group-id is the IMA group number).
Step 2
Router(config-if)# pvc vpi/vci
Creates a permanent virtual circuit for the ATM or IMA interface and assigns the PVC a VPI and VCI:
•
•
Note
Step 3
Router(config-if-atm-vc)# encapsulation {aal0 | aal5 | aal5snap}
Specifies the ATM adaptation layer (AAL) for the PVC:
•
•
•
Step 4
Router(config-if-atm-vc)# command
Configures the ATM operating characteristics of the PVC. CEoP SPAs support the ATM features in Chapter 9.
Step 5
Router(config-if-atm-vc)# exit
Returns you to interface configuration mode.
Step 6
Router(config-if)# xconnect peer-router-id vcid {encapsulation mpls | pseudowire-class name}
Configures a pseudowire to transport data from the ATM or IMA interface across the MPLS network.
•
•
•
•
Note
Step 7
Router(config-if)# exit
Exits interface configuration mode.
Configuring Pseudowire Redundancy (Optional)
CEoP SPAs support the L2VPN Pseudowire Redundancy feature, which provides backup service for ATM and circuit emulation (CEM) pseudowires. The L2VPN Pseudowire Redundancy feature enables the network to detect a failure and reroute the Layer 2 (L2) service to another endpoint that can continue to provide service. This feature provides the ability to recover from a failure either of the remote PE router or of the link between the PE and CE routers.
You configure pseudowire redundancy by configuring two pseudowires for an ATM or CEM interface: a primary pseudowire and a backup (standby) pseudowire. If the primary pseudowire goes down, the router uses the backup pseudowire in its place. When the primary pseudowire comes back up, the backup pseudowire is brought down and the router resumes using the primary.
For detailed information about pseudowire redundancy, see its feature description at:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/products_feature_guide09186a0080606811.html
Figure 10-2 shows an example of pseudowire redundancy.
Figure 10-2 Pseudowire Redundancy
Following is a summary of the steps to perform to configure pseudowire redundancy on a CEoP SPA. Although an ATM interface is shown, the configuration is the same for CEM.
Note
1.
2.
3.
4.
5.
6.
The following example shows pseudowire redundancy configured for a CEM circuit (group). In the example, the xconnect command configures a primary pseudowire for CEM group 0. The backup peer command creates a redundant pseudowire for the group.
int cem8/1/1no ip addresscem 0xconnect 10.10.10.1 1 encap mplsbackup peer 10.10.10.2 200exitConfiguring T1
To configure T1 on a 24-Port Channelized T1/E1 ATM CEoP SPA, use the following procedure and observe these guidelines:
•
•
•
•
•
Configuring E1
To configure E1 on a 24-Port Channelized T1/E1 ATM CEoP SPA, use the following procedure:
Configuring T3
This section describes how to configure the 2-Port Channelized T3/E3 ATM CEoP SPA. The SPA can be configured to operate in the following modes:
•
•
•
In clear-channel mode, each SPA port provides a single high-speed data channel. In channelized mode, each port provides multiple T1/E1 or DS0 channels.
The router creates a logical interface to represent the mode that the SPA port is configured to run in. An ATM interface is created for each T3 port (or channelized T1/E1) that is configured for ATM mode. The interface has the format atmslot/subslot/port (where slot/subslot identifies the SPA slot and subslot and /port identifies the port). An example is atm2/1/0.
The following sections provide instructions for configuring the SPA:
•
T3 Configuration Guidelines
This section lists the guidelines for configuring the 2-Port Channelized T3/E3 ATM CEoP SPA. For information about supported features, see Chapter 9, "Overview of the CEoP and Channelized ATM SPAs."
Note
T3 Mode
When configured for T3, the SPA can be configured for CEM or ATM clear-channel or channelized mode:
•
•
ATM Mode
For ATM, note the following guidelines:
•
Configuring Port Usage
Perform the following steps to configure a SPA port for T3:
Note
Step 1
Router(config)# controller {t3 | e3} slot/subslot/port
Selects the T3 controller for the port you are configuring (where slot/subslot identifies the SPA slot and subslot and /port identifies the port).
Step 2
Router(config-controller)# [no] framing {c-bit | m13}
(Optional) Specifies the framing type. The default is C-bit for both clear-channel and channelized modes.
For clear-channel mode, configure framing as:
•
•
Router(config-controller)# [no] framing {auto-detect | c-bit | m23}
For channelized mode, configure framing as:
•
•
•
Step 3
Router(config-controller)# clock source {internal | line}
(Optional) Specifies the clock source.
•
•
Step 4
Router(config-controller)# cablelength feet
(Optional) Specifies the length of the cable attached to the port (in feet). Valid values are 0 to 450 ft. The default is 224 ft.
Step 5
Router(config-controller)# [no] loopback {local | network | remote {line | payload}}
(Optional) Runs a loopback test, which is useful for troubleshooting problems. The no form of the command stops the test. The default is no loopback.
•
•
•
Step 6
Router(config-controller)# [no] bert pattern
[2^11 | 2^15 | 2^20 O.153 | 2^20 QRSS | 2^23 | 0s | 1s | alt-0-1] interval [1-1440](Optional) Configures bit-error-rate (BER) testing.
Step 7
Router(config-controller)# mdl {string {eic | fic | generator | lic | pfi | port | unit} string} | {transmit {idle-signal | path | test-signal}}
Example
Router(config-controller)# mdl string eic ID
Router(config-controller)# mdl string fic Building B
Router(config-controller)# mdl string unit ABC
Router(config-controller)# mdl string pfi Facility Z
Router(config-controller)# mdl string port Port 7Router(config-controller)# mdl transmit path
Router(config-controller)# mdl transmit idle-signal
(Optional) Configures maintenance data link (MDL) messages, which communicate information between local and remote ports. Valid only with C-bit framing.
•
–
–
–
–
–
–
–
•
–
–
–
Step 8
Router(config-controller)# exit
Returns you to global configuration mode.
If you specified channelized T3 mode in Step 2, see the next section for instructions on how to configure the logical T1/E1 channels on the port. Then, configure the port for CEM or ATM mode ("Configuring Circuit Emulation" or "Configuring the SPA for Clear-Channel ATM").
Configuring the SPA for Clear-Channel ATM
To configure a T3/E3 SPA port for clear-channel ATM, follow these steps:
Step 1
Router(config)# controller {t3 | e3} slot/subslot/port
Selects the T3 controller for the port you are configuring (where slot/subslot identifies the SPA location and /port identifies the port).
Step 2
Router(config-controller)# atm
Configures the port (interface) for clear-channel ATM. The router creates an ATM interface whose format is atm/slot/subslot/port (where slot/subslot identifies the SPA slot and subslot and /port is the SPA port).
Step 3
Router(config-controller)# exit
Returns you to global configuration mode.
Step 4
Router(config)# interface atmslot/subslot/port
Selects the ATM interface for the SPA port in Step 1.
Step 5
Router(config-if)# pvc vpi/vci
Configures a PVC for the interface and assigns the PVC a VPI and VCI. Do not specify 0 for both the VPI and VCI. See the "Configuring an ATM Pseudowire" section for details on this command and the next.
Step 6
Router(config-if)# xconnect peer-router-id vcid {encapsulation mpls | pseudowire-class name}
Configures a pseudowire to carry data from the clear-channel ATM interface over the MPLS network.
Step 7
Router(config-if)# end
Exits configuration mode.
Configuring SONET (OC-3)
To configure SONET (OC-3) on the1-Port Channelized OC-3 STM1 ATM CEoP SPA, use the following procedure and observe these guidelines:
•
•
•
•
•
•
•
•
SONET Controller Configuration
To configure the SONET controller, perform this task:
SDH Configuration for AU-4 C-12
This section describes how to enable an interface under SDH framing with AU-4 mapping after configuring the SONET controller.
SDH Configuration for AU-3 C-11
This section describes how to enable an interface under SDH framing with AU-3 mapping after configuring the SONET controller.
Configuring Inverse Multiplexing over ATM
Inverse multiplexing over ATM (IMA) allows multiple T1 or E1 links to be bundled together into a high-bandwidth logical link. The rate of the logical IMA link is approximately the sum of the rate of the physical links in the IMA group, although some overhead is required for ATM header and control cells.
Note
The inverse multiplexing operation is transparent to the ATM layer protocols, and therefore the ATM layer can operate normally, as if only a single physical interface is being used. In the transmit direction, IMA takes cells from the ATM layer and sends them in round-robin manner over the individual T1 or E1 links in the IMA group. At the receiving end, the cells are recombined to form the original cell stream and are passed up the ATM layer. An IMA device always sends a continuous stream. If no ATM layer cells are being sent, an IMA filler cell is transmitted to provide a constant stream at the physical layer.
IMA Control Protocol (ICP) cells are periodically transmitted between IMA interfaces. ICP cells control the inverse multiplexing function, provide sequencing for the ATM cell stream, and define the IMA frame. Using an IMA frame length of 128 cells, one out of every 128 cells on each link is an ICP cell.
Figure 10-3 shows how IMA works. In the figure, IMA performs inverse multiplexing and demultiplexing with four bundled links, providing 5.52 Mbps of bandwidth for T1s for packet traffic, after subtracting the overhead of ATM cell headers and ICP cells. The transmitting side, from which cells are distributed across the links, is referred to as Tx, and the receiving side, where cells are recombined, is called Rx.
Figure 10-3 IMA Operation
IMA Configuration Guidelines
Observe these guidelines as you configure the CEoP SPA for inverse multiplexing ATM:
•
–
–
•
•
•
•
•
•
•
•
To ensure that IMA groups synchronize correctly after a restart, observe the following guidelines as you configure IMA links. For information about restarts, see the description of ima autorestart in the "Configuring IMA Group Parameters" section.
•
•
IMA Link Bundle Configuration Overview
You bundle T1 or E1 links together by assigning the links to the same IMA group and configuring a PVC for the links in the group to use.
To assign a T1 or E1 link to an IMA group, issue the ima group group-number command under the T1 or E1 controller for the port that the link is attached to. Bundle a set of links together by issuing ima group under the controller for each of the links that you want to add to the bundle, and specify the same group number for each.
The router creates an IMA interface to represent the IMA group (link bundle). The interface has the same slot/subslot information as the SPA, followed by the IMA group ID, as shown here (for example, atm2/1/ima0):
interface atmslot/subslot/imagroup-id
The IMA interface has all of the characteristics of an ATM interface and supports any currently supported ATM features.
When all of the T1/E1 interfaces are removed from an IMA group, the IMA interface that represents the group is removed.
To configure the IMA group for operation, you must:
•
•
Configuration Example
The following steps provide an example of the steps to configure an IMA link bundle on the 24-Port Channelized T1/E1 ATM CEoP SPA. Detailed steps are provided in the section that follows.
1.
controller t1 2/1/0ima-group 0exitcontroller t1 2/1/1ima-group 0exitcontroller t1 2/1/2ima-group 0exitcontroller e1 5/1/0ima-group 1exitcontroller e1 5/1/1ima-group 1exit2.
interface atm2/1/ima0pvc 0/100 l2transportxconnect 10.2.0.1 10 encapsulation mplsexitinterface atm5/1/ima1pvc 0/101 l2transportxconnect 10.20.0.4 11 encapsulation mplsexit3.
interface atm2/1/ima0ima active-links-minimum 2ima clock-mode independentima frame-length 256exitConfiguring an IMA Link Bundle
To configure an IMA link bundle on a 24-Port Channelized T1/E1 ATM CEoP SPA, perform the following steps from global configuration mode:
Step 1
Router(config)# controller {t1 | e1} slot/subslot/port
Selects the controller for the link you want to add to an IMA link bundle (an IMA group).
•
Step 2
Router(config-controller)# [no] ima-group group-number
Creates an IMA group and adds the link to the group. Use the no form of the command remove the link from the IMA group.
•
Note
Step 3
Router(config-controller)# exit
Returns to global configuration mode.
Repeat steps 1 through 3 to add additional links to the IMA link bundle.Note
Step 4
Router(config)# interface atmslot/subslotimagroup-number
Selects the IMA interface for the link bundle you just created and enters interface configuration mode.
•
•
Step 5
Router(config-if)# pvc vpi/vci
Configures a PVC for the IMA group and assigns the PVC a VPI and VCI.
•
•
Note
Step 6
Router(config-if)# xconnect peer-router-id vcid {encapsulation mpls | pseudowire-class name}
Configures a pseudowire to carry data from the IMA link bundle over the MPLS network. See the "Configuring an ATM Pseudowire" section for details on the command.
Step 7
Router(config-if)# ima command
Configures parameters for the IMA interface. See Table 10-1 for the configuration commands.
Step 8
Router(config-if)# end
Returns you to privileged EXEC mode.
Configuring IMA Group Parameters
Use the commands in Table 10-1 to configure parameters for an IMA group. Issue the commands in interface configuration mode under the IMA interface of the IMA group being configured. Use the no form of each command to turn off a feature or to revert to its default setting.
Note
Table 10-1 IMA Interface Parameters
[no] ima version {1.0 | 1.1}
Selects which version of IMA to use. The default is version 1.1.
[no] ima active-links-minimum number
Specifies the minimum number of IMA links that must be active for the IMA group to be active, where:
•
The IMA group is active as long as the specified number of links is active; otherwise, the group is brought down and remains out of service until the minimum number of links becomes active again. To determine an appropriate value, consider your application needs and performance requirements, and the number of links in the group.
[no] ima clock-mode {common | independent}
Sets the transmit clock mode for the links in the IMA group. The default is common.
•
•
[no] ima frame-length {32 | 64 | 128 | 256}
Specifies the number of cells in an IMA frame. The default is 128.
Because each IMA frame contains an ICP cell, this parameter also controls how often ICP cells are sent over the links in the IMA group. For example, with a frame length of 64, 1 out of every 64 cells on the link is an ICP cell.
The smaller the IMA frame length, the more often ICP cells are sent, which reduces the amount of link bandwidth that is available for data.
[no] ima test [link link number] pattern pattern-id
Sends a continuous test pattern over an IMA link to verify that the link is operational. The pattern is looped back at the receiving end, which is useful for troubleshooting the physical link or configuration problems at the remote end. Use the no form of the command to stop the test.
•
•
Note
[no] ima differential-delay-maximum milliseconds
Specifies the maximum allowable differential delay (in milliseconds) among links in the IMA group. If the delay on any link exceeds this value, that link is dropped from the IMA group.
IMA sends cells round-robin over the T1 or E1 links in an IMA group, and every link adds some delay. To enable the router to correctly reconstruct the original data stream, IMA adjusts for differences in link delay. However, if a link's delay is greater than the specified maximum, the data stream cannot be reconstructed correctly.
Valid values for milliseconds are:
•
•
A shorter delay allows less adjustment among link delay variations. However, a longer delay can affect overall group performance by adding more latency to traffic or causing retransmission.
[no] ima autorestart {near-end-id near-end-group-id [far-end-id far-end-group-id]}
Enables the auto restart feature, which controls how IMA groups sync up after a restart. The no form of the command disables auto restart if it is enabled. See "IMA Auto Restart Examples" for examples.
When an IMA group stops operating correctly (for example, due to a failure with the CEoP SPA, an IMA link, or the router), the group must be restarted. When a restart occurs, the local IMA group must sync up with an IMA group at the remote end:
•
•
The near-end-id and far-end-id keywords identify the IMA groups. Valid values for near-end-id is 0-41. Valid values for far-end-id are 0-255 .
•
•
If you specify near-end-id only, the local IMA group learns the ID of the remote group to sync up with (which will be the first remote IMA group to become active). This learned remote group ID remains active until the SPA is reloaded.
If you specify both near-end-id and far-end-id, the local IMA group will only synchronize with this remote IMA group. Both the near-end and far-end IDs must be the same.
ima restart
Manually restarts an IMA group. When an IMA group stops operating correctly (for example, due to a link failure), you can use this command to restart the group after the problem has been corrected.
Verifying the IMA Configuration
To display information about all configured IMA groups, or a specific group, use the show ima interface command in privileged EXEC mode:
show ima interface atmslot/subslot/imagroup-number [detail]
In the following example, information is displayed for IMA group 1 (on the SPA in slot 5, subslot 0):
Router# show ima interface atm5/0/ima1ATM5/0/ima1 is up, ACTIVATION COMPLETESlot 5 Slot Unit 0 unit 257, CTRL VC 257, Vir 0, VC -1IMA Configured BW 12186, Active BW 3046IMA version 1.0, Frame length 128Link Test: DisabledAuto-Restart: DisabledImaGroupState: NearEnd = operational, FarEnd = operationalImaGroupFailureStatus = noFailureIMA Group Current Configuration:ImaGroupMinNumTxLinks = 1 ImaGroupMinNumRxLinks = 1ImaGroupDiffDelayMax = 25 ImaGroupNeTxClkMode = common(ctc)ImaGroupFrameLength = 128 ImaTestProcStatus = disabledImaGroupTestLink = None ImaGroupTestPattern = 0x0ImaGroupConfLink = 8 ImaGroupActiveLink = 2IMA Link Information:ID Link Link Status Test Status---- -------------- ------------------------------ ---------------0 T1 5/0/0 Up - controller Up disabled1 T1 5/0/1 Up - controller Up disabled2 T1 5/0/2 Down - controller Up disabled3 T1 5/0/3 Down - controller Up disabled4 T1 5/0/4 Down - controller Up disabled5 T1 5/0/5 Down - controller Up disabled6 T1 5/0/6 Down - controller Up disabled7 T1 5/0/7 Down - controller Up disabledIMA Auto Restart Examples
IMA auto restart is disabled by default, which means that IMA learns the ID of the remote IMA group each time a restart occurs. To see the current settings for auto restart, issue the show ima interface command and view the Auto-Restart section of the command output.
Following are several examples of different ways to enable auto restart:
•
ima autorestart near-end-id near-end-group-id•
ima autorestart near-end-id near-end-group-id far-end-id far-end-group-id•
no ima autorestartConfiguring Clocking
This section provides information about how to configure clocking on the 24-Port Channelized T1/E1 ATM CEoP SPA and the 1-Port Channelized OC-3 STM1 ATM CEoP SPA. It describes the following topics:
•
•
BITS Clock Support—Receive and Distribute—CEoP SPA on SIP-400
You can use the BITS Clock Support—Receive and Distribute—CEoP SPA on SIP-400 feature to select and configure a clock and distribute it across the chassis to be used as the Transmit reference on all SPA ports.
The BITS Clock support - Receive and Distribute - CEoP SPA on SIP-400 feature is supported on Cisco IOS Release 12.2SRB on the SPA-24CHT1-CE-ATM and the SPA-1CHOC3-CE-ATM, SPA-4XOC3 ATM, SPA-1xOC12/STM4 POS SPAs.
The line card operates in three different modes, dependiing on the configuration and the configured source state.
•
Note
•
Note
•
Note
Note
Guidelines
Use the following guidelines:
•
•
•
•
•
•
Configuration Tasks
To configure Network Clocking for the Cisco 7600/SIP-400, use the following commands:
Verifying
Use the show platform hardware network-clocks command to verify.
SIP-400-4# show plat hardware network-clocksSONET Clock Register = 0x20CA8000SONET Clock Interrupt Enable Register = 0x0SONET Clock Interrupt Status Register = 0x0MT90401 Reference : Primary Free RunningPrimary : SPA 0Secondary : SPA 0Backplane ReferencePrimary DISABLED : SPA 0Secondary DISABLED : SPA 0Status :Lock : 0 HoldOver : 0 SecOOR : 1 PriOOR : 1CLK_2M_OK : 1Config :PCCI : 0 FLOCK : 0 ModeSel : 2SI5321 CAL Signal : 0 SI5321 LOS Signal : 0SI5321 HoldOver : 0SIP-400-4#use the show network-clock command to verify output on RPRouter# show network-clocksActive source = SONET 1/3/0Active source backplane reference line = Primary Backplane ClockAll Network Clock Configuration---------------------------------Priority Clock Source State Reason1 SONET 1/3/0 ValidCurrent operating mode is RevertiveCurrent OOR Switchover mode is SwitchoverThere are no slots disabled from participating in network clockingConfiguring Clock Recovery
When configuring clock recovery, consider the following guidelines:
Adaptive Clock Recovery
•
–
–
•
–
–
•
•
•
Differential Clocking
•
•
•
To configure clock recovery on a 24-Port Channelized T1/E1 ATM CEoP SPA, use the following procedure:
To apply the recovered clock to the controller, use the following procedure:
Verifying Clock Recovery
To verify clock recovery, use the show recovered-clock command. In Cisco IOS Release 12.2SRB1 and later, command output has been expanded to include the port number and CEM group number.
Router# show recovered-clockRecovered clock status for subslot 3/0----------------------------------------Clock Mode Port CEM Status Frequency Offset(ppb)1 ADAPTIVE 0 1 HOLDOVER 0Router# show recovered-clockRecovered clock status for subslot 3/0----------------------------------------Clock Mode Port CEM Status Frequency Offset(ppb)1 ADAPTIVE 0 1 ACQUIRING -694Use the show platform network-clock command to display the contents of network clocking registers.
Router# show platform network-clockSONET Clock Register = 0x20EB80C8SONET Clock Interrupt Enable Register = 0x0SONET Clock Interrupt Status Register = 0x2MT90401 Reference : Primary ReservedPrimary : SPA 0Secondary : SPA 0Backplane ReferencePrimary ENABLE : SPA 0Secondary ENABLE : MT90401Status :Lock : 0 HoldOver : 1 SecOOR : 1 PriOOR : 1CLK_2M_OK : 1Config :PCCI : 0 FLOCK : 0 ModeSel : 3SI5321 CAL Signal : 0 SI5321 LOS Signal : 0SI5321 HoldOver : 0Configuring Out-of-Band Clocking
A TDM network requires a synchronized clock at each end of the connection (the source and destination). This means that the source and destination clock signals must be synchronized to each other in order to maintain data integrity on the communication link.
On the other hand, a packet-switched network (PSN) does not use a clocking strategy, which means that the PSN does not provide frequency synchronization between source and destination routers. Therefore, to transmit TDM data across a PSN (such as an MPLS network), we need a way to deliver the clocking signal between the source and destination routers.
Out-of-band clocking provides a way to deliver a clock signal between two CEoP SPAs, which allows TDM devices connected to the SPAs to communicate with each other. Dedicated pseudowires (called out-of-band clock channels) carry the timing signal between the sending and receiving SPAs. When a TDM device sends data to a destination TDM device, the receiving SPA uses the out-of-band clock channel to recover the clock signal that was used to send the data.
By keeping the timing packets separate from data packets, out-of-band clocking delivers an extremely accurate timing signal. This timing accuracy is important for mobile wireless applications and other specialized applications that have very low tolerances for such things as packet delay variation (PDV), jitter, and latency in the network. In-band clocking (where timing information is derived from the data stream) does not provide a clock that is accurate enough for these applications.
To set up out-of-band clock channels, you must configure a master clock interface and a slave clock interface on the SPAs and configure pseudowires to connect the master and slave clocks. Instructions for performing these steps are provided later in this section.
Benefits
Out-of-band clocking provides the following benefits:
•
•
•
•
•
•
•
Configuration Guidelines
The following guidelines apply to out-of-band clocking on CEoP SPAs:
•
•
•
•
When no network clock is available, the virtual CEM interface goes down and the pseudowire is disabled. This process is reversed when a valid network clock becomes available again. Normal CEM interfaces never go down, even if the associated physical link is down.•
Router Sending Clock (Master Clock)
•
•
•
•
Router Recovering Clock (Slave Clock)
•
•
•
Configuration Overview
The following steps provide a high-level overview of the procedure for configuring out-of-band clocking between two CEoP SPAs. Detailed steps are provided in the sections that follow.
Before you begin, determine which CEoP SPAs have TDM devices connected to them. You must configure an out-of-band clock channel to deliver the clock signal from each SPA that sends TDM data to every destination SPA that receives the data.
1.
2.
a.
b.
Note
3.
–
–
Note
4.
a.
b.
Creating and Configuring the Master Clock Interface
To create the master clock interface for out-of-band clocking, perform the following steps:
To configure the out-of-band channel to use for the master clock signal, perform the following steps:
Step 1
Router(config)# int virtual-cem slot/subslot/port
Selects the virtual CEM interface for the master clock and enters interface configuration mode. The interface has the same slot and subslot as the SPA from which the master clock was recovered (Step 1 in the preceding task), and the port number is always 24.
Step 2
Router(config-if)# cem circuit-id
Creates a CEM attachment circuit for the master clock signal. Valid values for circuit-id are 0 to 63.
Note
Step 3
Router(config-if-cem)# xconnect peer-router-id vcid encapsulation mpls
Configures an out-of-band channel (pseudowire) to carry the master clock signal.
•
•
•
Note
Step 4
Router(config-if-cem-xconn)# end
Exits CEM interface configuration mode and returns you to privileged EXEC mode.
Note
Configuring the Slave Clock Interface
To configure the slave clock interface and out-of-band channel to use for out-of-band clocking, perform the following steps. Configure a slave clock interface on every CEoP SPA that receives TDM data from the SPA configured as the master clock in the preceding section.
Step 1
Router(config)# recovered-clock slot/subslot
Specifies the slot and subslot of the CEoP SPA from which the master clock is recovered.
Step 2
Router(config)# clock slave
Creates a virtual CEM interface to represent the clock slave for out-of-band clocking.
Step 3
Router(config)# int virtual-cem slot/subslot/port
Enters configuration mode for the virtual CEM interface that represents the clock slave.
•
•
Step 4
Router(config-if)# cem circuit-id
Creates a CEM attachment circuit for the clock slave. The circuit-id value can be:
•
•
Note
Step 5
Router(config-if-cem)# xconnect peer-router-id vcid encapsulation mpls
Configures an out-of-band channel (pseudowire) to carry the clock signal.
•
•
•
Note
Step 6
Router(config-if-cem-xconn)# end
Exits CEM interface configuration mode and returns you to privileged EXEC mode.
Verifying Out-of-Band Clocking
This section lists the show commands that you can use to verify the out-of-band clocking configuration.
•
Router# show ip int brief. . .Virtual-cem8/1/24 unassigned YES unset up up. . .•
Router# show cem circuitCEM Int. ID Line Admin Circuit AC--------------------------------------------------------------CEM8/1/1 1 DOWN DOWN Active --/--Virtual-cem8/1/1 DOWN UP Active UP•
Router# show cem interface virtual-cem 8/1/24(Virtual-cem8/1/24) State: CONFIG COMPLETEVirtual CEM Slave Clock InterfaceSlot 8, Slot Unit 88, VC -1Total cem circuits: 1Cem circuits up : 1Cem circuits down : 0•
Router# show run int virtual-cem 8/1/24Building configuration...Current configuration : 117 bytes!interface Virtual-cem8/1/24no ip addresscem 1rtp-presentxconnect 20.0.0.1 300 encapsulation mpls!end•
Router# show run | begin recoveredrecovered-clock 8 1clock master•
Router# show recovered-clockRecovered clock status for subslot 3/0----------------------------------------Clock Mode Port CEM Status Frequency Offset(ppb)ENHANCED PRIMARY 0 HOLDOVER 0Removing the Out-of-Band Clocking Configuration
Use the following commands to delete the various components used for out-of-band clocking:
•
Router# conf tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# int virtual-cem 8/1/24Router(config-if)# no cem 1Router(config-if)# end•
Router# conf tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# recovered-clock 8 1Router(config-clock)# no clock masterRouter(config-clock)# endRouter#In the following example, the no clock slave command deletes the slave clock interface for the recovered clock (which is 8/1):
Router# conf tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# recovered-clock 8 1Router(config-clock)# no clock slaveRouter(config-clock)# endRouter#Out-of-Band Clocking Configuration Example
This section provides an example of how to configure out-of-band clocking between two CEoP SPAs. It is divided into several different configuration sections.
Configuring the Master Clock Interface
The following example shows how to configure a CEoP SPA as a master clock and verify the configuration:
Router# conf tEnter configuration commands, one per line. End with CNTL/Z.Router (config)# recovered-clock ?<0-14> Slot numberRouter (config)# recovered-clock 8 1Router(config-clock)# clock ?master Configure clock master on the cardrecovered Configure recovered clock on the cardreference Configure reference clock on the cardslave Configure clock slave on the cardRouter(config-clock)# clock masterRouter(config-clock)# endRouter# show run | begin recoveredrecovered-clock 8 1clock masterConfiguring the Slave Clock Interface
Router# conf tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# recovered-clock 8 1Router(config-clock)# clock slaveRouter(config-clock)# endRouter#Router# show run | begin recovered-clockrecovered-clock 8 1clock slaveVerifying the Virtual CEM Interface Configuration
The router creates a virtual CEM interface when you configure either the master or slave clock interface. You can view the interface using the show ip interface brief command:
Router# show ip int br...Virtual-cem8/1/24 unassigned YES unset up up...Router# sh run int Virtual-cem 8/1/24Building configuration...Current configuration : 50 bytes!interface Virtual-cem8/1/24no ip addressendConfiguring CEM Circuits for Out-of-Band Clocking Example
This section provides an example of how to configure CEM circuits and pseudowires for out-of-band clocking. The sample configuration shows the circuits and pseudowires configured on a CEoP SPA in PE1, which sends TDM data to another CEoP SPA in PE2.
You configure CEM circuits for the master and slave clocks under the virtual CEM interface that represents the recovered clock that is being used for out-of-band clocking. This differs from normal CEM circuits, which are configured under the SPA controller through the cem-group command.
Issuing the xconnect command under the master and slave CEM circuits configures an out-of-band clock channel to use to send the clock signal from the sending SPA to the receiving SPA. Note that normal CEM pseudowires are configured under the SPA controller interface.
Out-of-Band Clocking (PE1)
PE1# conf tPE1(config)# int virtual-cem 8/1/24PE1(config-if)# cem 1PE1(config-if-cem)# xconnect 20.0.0.1 200 encap mplsPE1(cfg-if-cem-xconn)# endPE1# show run int Virtual-CEM 8/1/24Building configuration...Current configuration : 117 bytes!interface Virtual-cem8/1/24no ip addresscem 1rtp-presentxconnect 20.0.0.1 200 encapsulation mpls!endOut-of-Band Clocking (PE2)
PE2# conf tPE2(config)# int virtual-cem 8/1/24PE2(config-if)# cem 1PE2(config-if-cem)# xconnect 10.0.0.1 200 encap mplsPE2(cfg-if-cem-xconn)# endPE2# show run int Virtual-CEM 8/1/24Building configuration...Current configuration : 117 bytes!interface Virtual-cem8/1/24no ip addresscem 1rtp-presentxconnect 10.0.0.1 200 encapsulation mpls!endConfiguring CEM Parameters
The following sections describe the parameters you can configure for CEM circuits.
Note
Configuring Payload Size (Optional)
To specify the number of bytes encapsulated into a single IP packet, use the pay-load size command. The size argument specifies the number of bytes in the payload of each packet. The range is from 32 to 1313 bytes.
Default payload sizes for an unstructured CEM channel are as follows:
•
•
•
Default payload sizes for a structured CEM channel depend on the number of time slots that constitute the channel. Payload size (L in bytes), number of time slots (N), and packetization delay (D in milliseconds) have the following relationship: L = 8*N*D. The default payload size is selected in such a way that the packetization delay is always 1 millisecond. For example, a structured CEM channel of 16xDS0 has a default payload size of 128 bytes.
The payload size must be an integer of the multiple of the number of time slots for structured CEM channels.
Setting the Dejitter Buffer Size
To specify the size of the dejitter buffer used to compensate for the network filter, use the dejitter-buffer size command. The configured dejitter buffer size is converted from milliseconds to packets and rounded up to the next integral number of packets. Use the size argument to specify the size of the buffer, in milliseconds. The range is from 1 to 500 ms; the default is 5 ms.
Setting the Idle Pattern (Optional)
To specify the idle pattern, use the [no] idle-pattern pattern1 command. The payload of each lost CESoPSN data packet must be replaced with the equivalent amount of the replacement data. The range for pattern is from 0x0 to 0xFF; the default idle pattern is 0xFF.
Enabling Dummy Mode
Dummy mode enables a bit pattern for filling in for lost or corrupted frames. To enable dummy mode, use the dummy-mode [last-frame | user-defined] command. The default is last-frame. The following is an example:
Router(config-cem)# dummy-mode last-frameSetting the Dummy Pattern
If dummy mode is set to user defined, you must use the dummy-pattern pattern command to configure the dummy pattern. The range for pattern is from 0x0 to 0xFF. The default dummy pattern is 0xFF. The following is an example:
Router(config-cem)# dummy-pattern 0x55Shutting Down a CEM Channel
To shut down a CEM channel, use the shutdown command in CEM configuration mode. The shutdown command is supported only under CEM mode and not under the CEM class.
Configuring AIS and RAI Alarm Forwarding in CESoPSN Mode on CEoP SPAs
Cisco IOS Release 12.2(33)SRD3 introduces the ability to configure on a per-T1/E1 basis the forwarding of AIS and RAI alarms towards peer CE devices via the TDM attachment circuit.
This feature allows grooming of traffic from several different cell-site fractional T1/E1s via CEM, through an MPLS cloud, onto a single aggregate T1/E1 going to the BSC.
This feature provides the following functionality:
•
•
•
Configuring SONET Mode
Use the following commands to enable AIS/RAI forwarding on the CEoP SPAs on the SIP-400 line card interface for SONET mode:
Configuring SDH AU-4 Mode
Use the following commands to enable AIS/RAI forwarding on the CEoP SPAs on the SIP-400 line card interface for SDH AU-4 Mode:
Configuring SDH AU-3 Mode
Use the following commands to enable AIS/RAI forwarding on the CEoP SPAs on the SIP-400 line card interface for SDH AU-3 Mode
:
Configuring T1 Mode
Use the following commands to enable AIS/RAI forwarding on the CEoP SPAs on the SIP-400 line card interface for T1 mode
:
Configuring E1 Mode
Use the following commands to enable AIS/RAI forwarding on the CEoP SPAs on the SIP-400 line card interface for E1 mode
:
Note
Configuration Restrictions
The following restrictions apply while configuring AIS/alarm RAI forwarding:
•
•
•
Verifying the Interface Configuration
The show cem circuit command shows information about the circuit state, administrative state, the CEM ID of the circuit, and the interface on which it is configured. If xconnect is configured under the circuit, the command output also includes information about the attached circuit.
Router# show cem circuit ?<0-504> CEM IDdetail Detailed information of cem ckt(s)interface CEM Interfacesummary Display summary of CEM ckts| Output modifiersRouter# show cem circuitCEM Int. ID Line Admin Circuit AC--------------------------------------------------------------CEM1/1/0 1 UP UP ACTIVE --/--CEM1/1/0 2 UP UP ACTIVE --/--CEM1/1/0 3 UP UP ACTIVE --/--CEM1/1/0 4 UP UP ACTIVE --/--CEM1/1/0 5 UP UP ACTIVE --/--The show cem circuit 0-504 command displays the detailed information about that particular circuit.
Router# show cem circuit 1CEM1/1/0, ID: 1, Line State: UP, Admin State: UP, Ckt State: ACTIVEIdle Pattern: 0xFF, Idle cas: 0x8, Dummy Pattern: 0xFFDejitter: 5, Payload Size: 40Framing: Framed, (DS0 channels: 1-5)Channel speed: 56CEM Defects SetExcessive Pkt Loss RatePacket LossSignalling: No CASRTP: No RTPIngress Pkts: 25929 Dropped: 0Egress Pkts: 0 Dropped: 0CEM Counter DetailsInput Errors: 0 Output Errors: 0Pkts Missing: 25927 Pkts Reordered: 0Misorder Drops: 0 JitterBuf Underrun: 1Error Sec: 26 Severly Errored Sec: 26Unavailable Sec: 5 Failure Counts: 1Pkts Malformed: 0The show cem circuit summary command displays the number of circuits which are up or down per interface basis.
Router# show cem circuit summaryCEM Int. Total Active Inactive--------------------------------------CEM1/1/0 5 5 0The show running module command shows detail on each CEM group:
Router# show running module 1Building configuration...Current configuration : 1542 bytescard type t1 1 1!Controller T1 1/1/0framing esflinecode b8zscem-group 1 timeslots 1-5 speed 56cem-group 2 timeslots 6-10 speed 56cem-group 3 timeslots 11-15 speed 56cem-group 4 timeslots 16-20 speed 56cem-group 5 timeslots 21-24 speed 56!Controller T1 1/1/1framing esflinecode b8zs!Controller T1 1/1/2framing esflinecode b8zs!Controller T1 1/1/3framing esf!Controller T1 1/1/4framing esflinecode b8zs!Controller T1 1/1/5framing esffdl bothlinecode b8zs!Controller T1 1/1/6framing esflinecode b8zs!Controller T1 1/1/7framing esflinecode b8zs!Controller T1 1/1/8framing esflinecode b8zs!Controller T1 1/1/9framing esfclock source internallinecode b8zs!Controller T1 1/1/10framing esflinecode b8zs!Controller T1 1/1/11framing esflinecode b8zs!Controller T1 1/1/12framing esflinecode b8zs!Controller T1 1/1/13framing esflinecode b8zs!Controller T1 1/1/14framing esflinecode b8zs!Controller T1 1/1/15framing esflinecode b8zs!Controller T1 1/1/16framing esflinecode b8zs!Controller T1 1/1/17framing esflinecode b8zs!Controller T1 1/1/18framing esflinecode b8zs!Controller T1 1/1/19framing esflinecode b8zs!Controller T1 1/1/20framing esflinecode b8zs!Controller T1 1/1/21framing esflinecode b8zs!Controller T1 1/1/22framing esflinecode b8zs!Controller T1 1/1/23framing esflinecode b8zs!interface CEM1/1/0no ip addresscem 1!cem 2!cem 3!cem 4!cem 5!endRouter# show int cem 2/1/3CEM2/1/3 is up, line protocol is upHardware is Circuit Emulation InterfaceMTU 1500 bytes, BW 10000000 Kbit, DLY 0 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation CEM, loopback not setKeepalive set (10 sec)Last input never, output never, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/0 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts (0 IP multicasts)0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outRouter# show class cem class1Class: class1Idle Pattern: 0x9, Idle cas: 0xFDejitter: 5, Payload Size: 100RTP: No RTPRouter# show class cem allClass: abcdefghijklmnIdle Pattern: 0xF, Idle cas: 0x8Dejitter: 200, Payload Size: 200RTP: Configured, RTP-HDR Compression: DisabledClass: class1Idle Pattern: 0x9, Idle cas: 0xFDejitter: 5, Payload Size: 100RTP: No RTPClass: 1234Idle Pattern: 0xF, Idle cas: 0x8Dejitter: 5, Payload Size: 32RTP: No RTPRouter# show class cem detailClass: abcdefghijklmnIdle Pattern: 0xF, Idle cas: 0x8Dejitter: 200, Payload Size: 200RTP: Configured, RTP-HDR Compression: DisabledCircuits inheriting this Class:NoneInterfaces inheriting this Class:NoneClass: class1Idle Pattern: 0x9, Idle cas: 0xFDejitter: 5, Payload Size: 100RTP: No RTPCircuits inheriting this Class:NoneInterfaces inheriting this Class:NoneClass: 1234Idle Pattern: 0xF, Idle cas: 0x8Dejitter: 5, Payload Size: 32RTP: No RTPCircuits inheriting this Class:NoneRouter# show class cem class1Class: class1Idle Pattern: 0x9, Idle cas: 0xFDejitter: 5, Payload Size: 100RTP: No RTP
