Table Of Contents
Prerequisites for Circuit Emulation over IP
Restrictions for Circuit Emulation over IP
Information About Circuit Emulation over IP
Benefits of Circuit Emulation over IP
Adaptive Clocking for Circuit Emulation over IP
Data Protection (Sample Repetition)
Payload Compression for Circuit Emulation over IP
Signaling for Circuit Emulation over IP
TDM Clock Network Participation
How to Configure Circuit Emulation over IP
Configuring the NM-CEM-4TE1 Card Type
Creating CEM Channels on the T1/E1 Line
Configuring the Connection Using the xconnect Command
Configuring Port Muxing on a CEM Serial Channel
Configuration Examples for Circuit Emulation over IP
Configuring a T1 CEM Network Module: Example
Configuring a Serial CEM Network Module: Example
Verifying a CEM Network Module Example
Circuit Emulation over IP
Circuit Emulation over IP (CEoIP) provides a protocol-independent transport over IP networks. It enables proprietary or legacy applications to be carried transparently to the destination, similar to a leased line. Two network modules—NM-CEM-4TE1 and NM-CEM-4SER—are introduced to provide the CEoIP support.
History for the Circuit Emulation over IP Feature
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for Circuit Emulation over IP
•
Restrictions for Circuit Emulation over IP
•
Information About Circuit Emulation over IP
•
How to Configure Circuit Emulation over IP
•
Configuration Examples for Circuit Emulation over IP
Prerequisites for Circuit Emulation over IP
•
The CEoIP feature requires a circuit emulation (CEM) network module (NM) on each end of the connection, either the NM-CEM-4TE1 or the NM-CEM-4SER. You do not need to use the same type of CEM NM on both ends of the connection.
•
The CEoIP feature requires 300 KB of flash memory and 1 MB of DRAM in addition to your Cisco IOS software requirements.
Restrictions for Circuit Emulation over IP
•
The NM-CEM-4TE1 supports only B8ZS (T1) and HDB3 (E1) line codes.
•
E1 lines do not support 56-kbps connections.
•
CEoIP software cannot run payload compression for more than 3.088 Mbps per network module.
•
If you configure four T1, E1, or serial cables (over 1.544 MB) at the same time on Cisco 2600XM series routers, you cannot turn on the data protection and payload compression features. Also, in framed mode (channelized), you can use up to 60 channels without the data protection and payload compression features on Cisco 2600XM series routers. However, you can turn on the data protection and payload compression feature on one T1/E1.
•
There is a limitation on the data protection and payload compression features on Cisco 3660 routers. If you configure four T1, E1, or serial cables on Cisco 3660 routers, you can turn on data protection for up to two T1/E1s. In framed mode, you can use 88 channels.
Information About Circuit Emulation over IP
To configure Circuit Emulation over IP, you should understand the following concepts:
•
Benefits of Circuit Emulation over IP
•
Adaptive Clocking for Circuit Emulation over IP
•
Data Protection (Sample Repetition)
•
Payload Compression for Circuit Emulation over IP
•
Signaling for Circuit Emulation over IP
•
TDM Clock Network Participation
Circuit Emulation over IP
Circuit emulation over IP is an end-to-end service that allows Layer 1 data to be transported transparently through an IP network. Applications that require circuit emulation need the network to provide a constant-rate bit stream. Enterprise customers can use CEoIP with the enhanced adaptive clock to provide a leased-line emulation service to connect a central PBX to one or more remote PBXs. In Figure 1 an existing PBX system with leased T1 or E1 lines is shown in the diagram on the left, and CEoIP is introduced in the diagram on the right. CEoIP introduces the ability to provide an emulation of T1 or E1 leased lines through an IP infrastructure that is transparent to the PBXs.
Figure 1 PBX Application of CEoIP
CEoIP can use adaptive clocking as a means of synchronizing the clock frequencies at the two endpoints. Channel-associated signaling (CAS) transport is provided as an optional feature to allow channelized voice applications. Payload compression is provided as an optional feature to improve bandwidth efficiency, and data protection is provided to reduce the probability of data loss.
CEoIP software supports the following network modules:
•
NM-CEM-4SER—A network module with four serial ports. To configure CEoIP software for the NM-CEM-4SER, you must configure the options of the ports. Options include dejitter buffer, payload compression, and payload size.
•
NM-CEM-4TE1—A network module with four ports that you can configure as T1 or E1 (where all four ports support the same interface type). To configure CEoIP software for the NM-CEM-4TE1, you must define the card type and then configure the options of the port.
CEoIP can be used by mobile wireless service providers to configure existing IP infrastructure to carry compressed or noncompressed time-division multiplexing (TDM) voice traffic between geographically distributed cell sites and centralized equipment. CEoIP can be used at cell sites to provide asynchronous control of devices at cell sites. Another application can be for Metro Ethernet where CEoIP can provide a T1/E1 leased-line emulation over a packet infrastructure.
Benefits of Circuit Emulation over IP
CEoIP emulates a TDM circuit over a pipe through the IP network so that TDM Circuit-based networks can be migrated to a packet-based network. CEoIP provides a simple migration path to IP-only networks. Examples of solutions that CEoIP integrates with IP include the following:
•
Legacy data services
•
Legacy video applications
•
Satellite data streams
•
Radar data streams
•
Telemetry for automated industrial environments (for example, power distribution)
•
Crypto tunneling for multilevel security
Adaptive Clocking for Circuit Emulation over IP
The adaptive clocking option of CEoIP allows the egress clock to vary by expanding or contracting the clock period from the nominal clock. After you have implemented the clocking feature, the adaptive clocking circuits continuously adjust the selected clock on the basis of the data buffer level. You can implement adaptive clocking on each port independently.
In Cisco IOS Release 12.4(2)T and later releases, the adaptive clocking algorithm is enhanced to provide better adaptive clock accuracy. The clock source command allows one of three adaptive modes to be selected:
•
coarse—Specifies the coarse mode. The coarse mode uses the original adaptive clock algorithm and is used when the stability of the master clock derived from the CPE is not guaranteed. This mode is compatible with previous Cisco IOS releases.
•
closed-loop—Specifies the closed loop mode. Taking advantage of the fact that a T1 or E1 link uses the same clock in both directions, the adaptive clock algorithm enhancements are used to improve the adaptive clock accuracy. The same clock must be used in both directions for the closed loop mode, and both ends of the CEM must be running a Cisco IOS release that supports the enhanced adaptive clock algorithm. Use the closed loop mode when clock accuracy is required, the master clock from the customer premises equipment (CPE) is of good quality, and the clocks are the same in both directions of the T1 or E1 link.
Note
Do not use the closed loop mode in applications where the clocks are different for the two directions of the T1 or E1 link.
•
open-loop—Specifies the open loop mode. Some of the adaptive clock algorithm is used, but this mode does not require the clocks to be the same in both directions. This mode is compatible with previous Cisco IOS releases and is the default mode if no keyword is specified. Use the open loop mode when the master clock from the CPE is of good quality, but the clocks are not the same in both directions of the T1 or E1 link.
Note
The NM-CEM-4SER does not support the enhanced adaptive clock accuracy feature introduced in Cisco IOS Release 12.4(2)T.
Control Lead Configurations
CEoIP software supports the monitoring and transport of serial interface control leads.
CRC Error Check
CRC error checking can be disabled on specific serial modules so that the CEM payload is passed on in spite of bit errors. CEM can tolerate a low error rate without losing its synchronization. The ability to disable CRC error checking makes CEM more robust on lossy IP networks.
Modules that support disabling of CRC error checking include the NM-4T, WIC-2T, VWIC-2MFT-DI, WIC-1DSU-56K4, VWIC-1MFT-T1, VWIC-1MFT-E1, VWIC-2MFT-T1, VWIC-2MFT-E1, VWIC-2MFT-T1-DI, and the HWIC-4T.
Data Protection (Sample Repetition)
The data protection option, also known as sample repetition, reduces the probability of errors due to packet loss by sending each sample twice, in two different IP packets. Data protection consumes more bandwidth than standard transmission, but you can minimize the amount of traffic with payload compression. This feature is disabled by default.
Dejitter
The dejitter buffer size determines the ability of the emulated circuit to tolerate network jitter. The dejitter buffer in CEoIP software is configurable up to 500 milliseconds; the maximum amount of network jitter that CEoIP can tolerate is plus or minus 250 milliseconds.
Idle Pattern
The idle pattern option specifies the idle pattern to transmit when the circuit goes down. You can specify a maximum of 64 bits with two 32-bit patterns for the NM-CEM-4SER and eight 8-bit patterns for the NM-CEM-4TE1.
Interface MIB
The Interface MIB (IF-MIB) is available for CEM channels for monitoring link status with the linkDown and linkUp MIB objects. The IF-MIB is supported only on serial CEM network modules.
Payload Compression for Circuit Emulation over IP
The payload compression option minimizes the amount of bandwidth that traffic consumes. It compresses the transmission of any repetitive data pattern (idle code, HDLC flags, and so on) to increase the efficiency of the solution across the network.
With CEoIP software, you can adjust the size (in bytes) of the payload for the IP packet to configure efficiency as opposed to packetization. Larger payloads provide more efficiency but increase the delay. With smaller packets, the overhead of the header increases. Payload compression is disabled by default.
Payload Size
Payload size is the number of bytes put into each IP packet. This parameter impacts packetization delay and efficiency. Configure a high payload size to increase packetization delay and efficiency. A smaller payload size reduces packetization delay and efficiency.
Port Muxing
The port muxing capability allows data directed to the same destination from different serial ports to be multiplexed into a single CEM channel. Port muxing reduces operating overhead because only one port requires management.
All ports in a muxed group must be of the same type, such as all RS232 ports, or all RS530 ports; they must be of the same "polarity" (DCE or DTE); and they must all belong to the same clock domain.
When ports are participating in a muxed group, compression/data protection will not be supported.
Signaling for Circuit Emulation over IP
CEoIP software supports the transport of channel-associated signaling (CAS) bits in channelized T1/E1 mode. This option extracts incremental signaling information and sends that information in separate packets.
TDM Clock Network Participation
Allows the CEM channel to participate in a TDM clock network and to function both as a clock slave and a clock master. The adaptive clock recovered from the CEM channel can be passed to other network clock-capable modules, such as the VWIC. The clock coming in from other T1/E1 lines can be used to start the clocks on the CEM. The CEM, likewise, can trigger clocks on T1/E1 links.
Note
The Cisco 2600XM platform requires the AIM-VOICE-30, AIM-ATM, or AIM-ATM-VOICE-30; and the Cisco 3660 platform, requires the MIX-3660-64 for this feature.
How to Configure Circuit Emulation over IP
This section documents the tasks for configuring the two network modules introduced to support CEoIP: NM-CEM-4TE1 and NM-CEM-4SER.
•
Configuring the NM-CEM-4TE1 Card Type
•
Creating CEM Channels on the T1/E1 Line
•
Configuring the Connection Using the xconnect Command
•
Configuring Port Muxing on a CEM Serial Channel
To configure an NM-CEM-4TE1, start with the "Configuring the NM-CEM-4TE1 Card Type" section.
To configure an NM-CEM-4SER, go directly to the "Configuring the Connection Using the xconnect Command" section.
Configuring the NM-CEM-4TE1 Card Type
Perform this task to configure the card type for the four-port T1 or E1 network module that supports CEoIP (NM-CEM-4TE1). All the ports must be set to the same transmission mode, either T1 or E1.
This task does not apply to the NM-CEM-4SER.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
card type {t1 | e1} slot
4.
end
DETAILED STEPS
What to Do Next
Go to the "Configuring the T1/E1 Line" section to continue configuring CEoIP on an NM-CEM-4TE1.
Configuring the T1/E1 Line
Perform this task to configure the T1 or E1 line.
This task does not apply to the NM-CEM-4SER.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
controller {t1 | e1} slot/port
4.
framing {esf | sf | unframed}
or
framing {crc4 | no-crc4 | unframed}5.
clock source {internal | line | adaptive channel-number [closed-loop | open-loop | coarse]}
6.
cablelength {long attenuation | short length}
7.
crc-threshold value
8.
description text
9.
loopback{local {line | payload} | network}
10.
end
DETAILED STEPS
What to Do Next
Go to the "Creating CEM Channels on the T1/E1 Line" section to continue configuring CEoIP on an NM-CEM-4TE1.
Creating CEM Channels on the T1/E1 Line
Perform this task to create CEM channels on the T1 or E1 line.
This task does not apply to the NM-CEM-4SER.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
controller {t1 | e1} slot/port
4.
cem-group group-number {unframed | timeslots timeslot [speed {56 | 64}]}
5.
end
DETAILED STEPS
What to Do Next
Go to the "Configuring the Connection Using the xconnect Command" section to continue configuring CEoIP on an NM-CEM-4TE1.
Configuring the Connection Using the xconnect Command
Perform this task to create a connection using the xconnect command.
This task applies to configuring CEoIP on both the NM-CEM-4TE1 and the NM-CEM-4SER.
Note
To properly configure the CEoIP feature, two CEoIP network modules must use the same UDP port number to communicate.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
cem slot/port/channel
4.
xconnect remote-ip-address virtual-connect-ID encapsulation encapsulation-type
5.
local ip address ip-address
6.
local udp port port
7.
remote udp port port
8.
end
DETAILED STEPS
Command or Action PurposeStep 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
cem slot/port/channel
Example:Router(config)# cem 3/1/0
Enters CEM configuration mode to configure CEM channels.
•
Use the slot argument to specify the slot number in which the network module is installed.
•
Use the port argument to specify the port number of the CEM channel to be configured.
•
Use the channel argument to specify the CEM channel number to be configured. For a serial channel, enter zero. For a T1 or E1 channel, enter the channel number defined in the cem-group command (see the "Creating CEM Channels on the T1/E1 Line" section).
Step 4
xconnect remote-ip-address virtual-connect-ID encapsulation encapsulation-type
Example:Router(config-cem)# xconnect 10.2.0.1 0 encapsulation udp
Creates one end of a connection between two CEM network modules and enters xconnect configuration mode.
•
Use the remote-ip-address argument to specify the IP address of an interface (regular or loopback) on the destination router.
•
Set the virtual-connect-ID argument to zero.
Note
Currently the only supported encapsulation type is UDP.
Step 5
local ip address ip-address
Example:Router(config-cem-xconnect)# local ip address 10.2.0.2
Configures the IP address of an interface (regular or loopback) on the source router.
Note
The local IP address must be the same as the remote IP address (at the other side) configured in the xconnect command.
Step 6
local udp port port
Example:Router(config-cem-xconnect)# local udp port 15901
Specifies the User Datagram Protocol (UDP) port number of the local CEM channel.
Note
The number of the local UDP port of a CEM channel must be the same as the number of the remote UDP port of the CEM channel at the other end of the connection.
Step 7
remote udp port port
Example:Router(config-cem-xconnect)# remote udp port 15902
Specifies the UDP port number of the remote CEM channel.
Note
The number of the remote UDP port of a CEM channel must be the same as the number of the local UDP port of the CEM channel at the other end of the connection.
Step 8
end
Example:Router(config-cem-xconnect)# end
Exits xconnect configuration mode and returns to privileged EXEC mode.
What to Do Next
This task must be repeated on the other CEM network module. Each end of the CEM connection must be configured identically to allow traffic to pass between the network modules. When both network modules have been configured, go to the "Configuring the CEM Channel" section.
Configuring the CEM Channel
Perform this task to configure the CEM T1/E1 or serial channel.
This task applies to both the NM-CEM-4TE1 and the NM-CEM-4SER.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
cem slot/port/channel
4.
clock rate rate
5.
clock mode {normal | split}
6.
clock source {internal | loop | adaptive}
7.
payload-size size
8.
dejitter-buffer size
9.
control-lead sampling-rate rate
10.
control-lead state {active | fail} output-lead {on | off | follow} [{local | remote} input-lead]
11.
data-strobe input-lead {on | off}
12.
idle-pattern {pattern | length pattern1 [pattern2]
13.
failure {activation | deactivation} msec
14.
signaling [on-hook-pattern] [off-hook-pattern] [msec]
15.
payload-compression
16.
data-protection
17.
ip dscp [dscp-value]
18.
ip tos tos
19.
ip precedence precedence
20.
loopback {local | network}
21.
end
22.
show cem {slot/port/channel | summary}
DETAILED STEPS
Command or Action PurposeStep 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
cem slot/port/channel
Example:Router(config)# cem 3/1/0
Enters CEM configuration mode to configure CEM channels.
•
Use the slot argument to specify the slot number in which the network module is installed.
•
Use the port argument to specify the port number of the CEM channel to be configured.
•
Use the channel argument to specify the CEM channel number to be configured. For a serial channel, enter zero. For a T1 or E1 channel, enter the channel number defined in the cem-group command (see the "Creating CEM Channels on the T1/E1 Line" section).
Step 4
clock rate rate
Example:Router(config-cem)# clock rate 38400
(Optional) For serial channels only. Specifies the nominal bit rate of a serial CEM channel.
•
Use the rate argument to specify the data rate of the channel, in bps. Default is 64000.
Step 5
clock mode {normal | split}
Example:Router(config-cem)# clock mode split
(Optional) For serial channels only. Specifies the clock mode of a serial CEM channel.
•
Use the normal keyword to specify that the DCE provides both the Receive Clock (RxC) and the Transmit clock (TxC) to the attached DTE.
•
Use the split keyword to specify that the DCE provides the Receive Clock (RxC) to the attached DTE and that the DTE provides the external Transmit Clock (XTC or TT) to the DCE.
Note
Depending on the serial cable attached to the port, the port is automatically configured as either a DCE or a DTE.
Step 6
clock source {internal | loop | adaptive}
Example:Router(config-cem)# clock source loop
(Optional) Configures the clock source for a serial CEM channel.
•
This step applies only to configuring serial channels. For information about configuring the clock source for T1 or E1 ports, see the "Configuring the T1/E1 Line" section.
•
Use the internal keyword to specify that the clock(s) provided by the network module to the CPE is derived from the TDM bus backplane clock, if one exists in the router, or from the onboard oscillator on the network module.
•
Use the loop keyword to specify that the clock provided by the network module to the attached CPE is derived from the clock received on the same port from the attached CPE.
•
Use the adaptive keyword to specify that the clock(s) provided by the network module to the CPE is locally synthesized based on the average data content of the local dejitter buffer.
Note
The loop keyword is valid only when the clock mode split command is configured.
Step 7
payload-size size
Example:Router(config-cem)# payload-size 512
(Optional) Specifies the number of bytes encapsulated into a single IP packet.
•
Use the size argument to specify the number of bytes included in the payload of each packet. Default is 32 for a serial CEM channel.
•
For more information about T1 and E1 default values, see the payload-size command in the Cisco IOS Interface and Hardware Component Command Reference, Release 12.4.
Step 8
dejitter-buffer size
Example:Router(config-cem)# dejitter-buffer 80
(Optional) Specifies the size of the dejitter buffer used to compensate for the network filter.
•
Use the size argument to specify the size of the buffer, in milliseconds. Default is 60.
Step 9
control-lead sampling-rate rate
Example:Router(config-cem)# control-lead sampling-rate 10
(Optional) For serial channels only. Specifies the sampling rate of input control leads on a serial CEM channel.
•
Use the rate argument to specify the frequency with which the control leads are sampled, in samples per second. Default is 0.
Note
Control lead update packets are independent of the data packets from the same channel.
Step 10
control-lead state {active | fail} output-lead {on | off | follow} [{local | remote} input-lead]
Example:Router(config-cem)# control-lead state active rts follow remote cts
(Optional) For serial channels only. Specifies the state of each output control lead on a serial CEM channel.
•
Use the active keyword to specify the state of the control lead when the connection is active.
•
Use the fail keyword to specify the state of the control lead when the connection has failed.
•
Use the output-lead argument to specify the name of the control lead.
•
Use the on keyword to specify that the control lead is permanently asserted.
•
Use the off keyword to specify that the control lead is permanently not asserted.
•
Use the follow keyword to specify that the control lead is to follow any changes in the state of an input control lead specified by the local or remote keywords and the input-lead argument.
•
Use the input-lead argument to specify the name of the local or remote control lead to follow.
Note
Control lead update packets are independent of the data packets for the same channel.
Note
The control-lead sampling-rate parameter must be set to nonzero in order for this feature to operate.
Step 11
data-strobe input-lead {on | off}
Example:Router(config-cem)# data-strobe dtr on
(Optional) For serial channels only. Specifies that an input control lead is to be monitored and data is packetized and sent only when the specified control lead is in the specified state.
•
Use the input-lead argument to specify the input control lead to be monitored to determine whether input data is to be packetized.
•
Use the on keyword to specify that data packets are to be sent from this CEM channel only when the specified input lead is asserted.
•
Use the off keyword to specify that data packets are to be sent from this CEM channel only when the specified input lead is not asserted.
•
Use this command to save bandwidth when the attached CPE is inactive.
Note
Control lead update packets are still sent even if data packets are withheld.
Step 12
Cisco NM-CEM-4SER
idle-pattern length pattern1 [pattern2]
Cisco NM-CEM-4TE1
idle-pattern pattern1
Example:Cisco NM-CEM-4SER
Router(config-cem)# idle-pattern 53 0x12345678 0x87654321
Cisco NM-CEM-4TE1
Router(config-cem)# idle-pattern 0x66
(Optional) Defines the idle data pattern to send to the attached CPE when packets are lost or the dejitter buffer experiences an under-run condition.
For serial CEM channels:
•
A bit pattern up to 64 bits long may be specified.
•
Use the length argument to specify the total length of the repeating bit pattern. Default is 8 bits.
•
Use the pattern1 argument to specify up to 32 bits of the least significant bits of the idle data pattern, in hex notation. Default is 0xFF.
•
Use the pattern2 argument to specify the most significant bits of the idle data pattern, in hex notation. If the length argument is 32 bits or less, this argument is not permitted.
For T1 or E1 CEM channels:
•
An eight 8-bit idle data pattern is specified.
Step 13
failure {activation | deactivation} msec
Example:Router(config-cem)# failure activation 1000
(Optional) Specifies a time period before a circuit emulation (CEM) connection enters, or recovers from, a failed state.
•
Use the activation keyword to specifiy how long the software will wait for the detection of a failure of a CEM connection until the CEM channel enters the failed state.
•
Use the deactivation kewyord to specifify how long the software will wait from the detection of a repair to the CEM connection until the CEM channel is returned to an active (up) state.
•
Use the time argument to specify the failure activation or deactivation time in milliseconds. The valid range is 50 to 60000. Default is 2000. Any value entered is rounded up to the next multiple of 50 milliseconds.
Step 14
signaling [on-hook-pattern] [off-hook-pattern] [msec]
Example:Router(config-cem)# signaling
(Optional) For framed T1 or E1 data channels only. Enables the transport of channel-associated signaling (CAS) bits.
Step 15
payload-compression
Example:Router(config-cem)# payload-compression
(Optional) Enables payload compression on a CEM channel.
Note
Enabling payload compression adds a delay equal to one packet time.
Step 16
data-protection
Example:Router(config-cem)# data-protection
(Optional) Enables data protection by transmitting each data bit twice, once in each of two consecutive data packets.
•
Use the data-protection command to protect transmissions from the effects of lost IP packets.
CautionUse this command carefully because it increases the network bandwidth used by the CEM connection.
Step 17
ip dscp [dscp-value]
Example:Router(config-cem)# ip dscp 36
(Optional) Configures the IP differentiated services code point (DSCP) for packets originating from this CEM channel.
•
Use the optional dscp argument to specify the value placed in the DSCP field of IP packets originating from this channel. Default is 46.
Note
If DSCP is configured, the ip tos and ip precedence commands are not available because they are mutually exclusive.
Step 18
ip tos tos
Example:Router(config-cem)# ip tos 11
(Optional) Configures the IP type of service (ToS) bits for the CEM channel.
•
Use the tos argument to specify the value placed in the ToS field of IP packets originating from this channel. Default is 5.
Note
If DSCP is configured using the ip dscp command, the ip tos command is not available because these commands are mutually exclusive.
Step 19
ip precedence precedence
Example:Router(config-cem)# ip precedence 7
(Optional) Configures the IP precedence bits for the CEM channel.
•
Use the precedence argument to specify the value placed in the precedence field of IP packets originating from this channel. Default is 0.
Note
If DSCP is configured using the ip dscp command, the ip precedence command is not available because these commands are mutually exclusive.
Step 20
loopback {local | network}
Example:Router(config-cem)# loopback network
(Optional) Creates a loopback from a CEM serial channel.
•
Use the local keyword to create a loopback where the information from a locally-attached CPE is transmitted back to the locally-attached CPE.
•
Use the network keyword to create a loopback where the data received over the network from a remotely-attached CPE is transmitted back to the remotely-attached CPE.
Note
For configuring a loopback on a T1 or E1 port, see the "Configuring the T1/E1 Line" section.
Step 21
end
Example:Router(config-cem)# end
Exits CEM configuration mode and returns to privileged EXEC mode.
Step 22
show cem {slot/port/channel | summary}
Example:Router# show cem summary
Displays CEM statistics.
Examples
The following example shows partial output from the show cem command using the summary keyword:
Router# show cem summarycem summaryCSTATE: CEM stateLSTATE: line stateOSTATE: operational statePSIZE: payload-sizePCOMP: payload-compressionDPROT: data-protectionCEM CSTATE LSTATE OSTATE PSIZE PCOMP DPROT----------------------------------------------------------------------2/0/0 shutdown up config-incomplete 256 disabled disabled2/1/0 shutdown up config-incomplete 256 disabled disabled2/2/0 shutdown up config-incomplete 256 disabled disabled2/3/0 shutdown up config-incomplete 256 disabled disabled4/0/1 up up active 96 enabled disabled4/0/2 up up active 96 enabled disabled4/0/3 up up active 96 enabled disabled4/0/4 up up active 96 enabled disabled4/0/5 up up active 96 enabled disabled4/0/6 up up active 96 enabled disabled4/0/7 up up active 96 disabled disabled4/0/8 up up active 96 disabled disabled4/0/9 up up active 96 disabled disabled4/0/10 up up active 96 disabled disabledConfiguring Port Muxing on a CEM Serial Channel
Perform this task to configure port muxing on a CEM serial channel, routing data from multiple ports through a single channel. Port Muxing reduces operating overhead, requiring management of a single port rather than several.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
cem slot/port/channel
4.
attach port
5.
end
Detailed Steps
Command or Action PurposeStep 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
cem slot/port/channel
Example:Router(config)# cem 3/1/0
Enters CEM configuration mode to configure CEM channels.
•
Use the slot argument to specify the slot number in which the network module is installed.
•
Use the port argument to specify the port number of the CEM channel to be configured.
•
Use the channel argument to specify the CEM channel number to be configured. For a serial channel, enter zero. For a T1 or E1 channel, enter the channel number defined in the cem-group command (see the "Creating CEM Channels on the T1/E1 Line" section).
Step 4
attach port
Example:Router(config-cem)# attach 1
Attaches slave ports to a master port for port muxing.
Step 5
end
Example:Router(config-cem)# end
Exits CEM configuration mode and returns to privileged EXEC mode.
Step 6
show cem {slot/port/channel | summary}
Example:Router# show cem summary
Displays CEM statistics.
Configuration Examples for Circuit Emulation over IP
This section provides the following configuration examples:
•
Configuring a T1 CEM Network Module: Example
•
Configuring a Serial CEM Network Module: Example
•
Verifying a CEM Network Module Example
Configuring a T1 CEM Network Module: Example
The following example shows a basic configuration of a T1 network module to configure the CEoIP feature.
card type t1 0controller t1 4/0cem-group 6 timeslots 1-4,9,10 speed 64framing esflinecode b8zsclock source adaptive 6cablelength long -15dbcrc-threshold 512description T1 line to 3rd floor PBXloopback networkno shutdownexitcem 2/1/6xconnect 10.2.0.1 0 encapsulation udplocal ip address 10.2.0.9local udp port 15901remote udp port 15902payload-size 512dejitter-buffer 80signalingexitConfiguring a Serial CEM Network Module: Example
The following example shows a basic configuration of a CEM serial channel to configure the CEoIP feature. Each end of the CEM connection must be configured before the CEM channel is configured.
Serial CEM Network Module 1
cem 2/0/0xconnect 10.3.0.1 0 encapsulation udplocal ip address 10.3.0.9local udp port 15901remote udp port 15902endSerial CEM Network Module 2
cem 2/1/0xconnect 10.3.0.9 0 encapsulation udplocal ip address 10.3.0.1local udp port 15902remote udp port 15901endSerial Channel Configuration
cem 2/0/0clock rate 38400clock mode splitclock source looppayload-size 512dejitter-buffer 80control-lead sampling-rate 10control-lead state active rts follow remote ctsdata-strobe dtr onidle-pattern 53 0x12345678 0x87654321payload-compressiondata-protectionip dscp 36loopback networkendVerifying a CEM Network Module Example
The folowing example displays the status of a configured CEM network module. This exmaple uses the show cem command to monitor the configuration, status and performance of a particular CEM channel.
Router# show cem 4/1/0cem infocem 4/1/0 is upLine state is upOperational state is activeNear end ip address: 172.31.28.2, udp port: 15901Far end ip address: 172.31.28.10, udp port: 15901IP payload size: 512IP dscp : 0x28Idle pattern length: 8 , Idle Pattern: 0xFFPayload compression is disabledData protection is disabledDejitter buffer size is 60 msChannel clock rate is 2048000 bpsPhysical interface is E1 unframedIngress packets: 32505156, dropped: 0, overruns: 0Egress packets: 32505158, dropped: 637, lost pkts: 0Egress out of sequence pkts: 0Egress overruns: 16, underruns: 244Egress corrupt pkts rcvd: 030 second ingress rate 2050321 bits/sec, 500 packets/sec30 second egress rate 2050184 bits/sec, 500 packets/secTx interrupts: 32504249Reorder queue flush: 0, visited: 0, max wait window: 0Network jitter max: 8 ms, average: 1 ms, min: 0 msAdaptive clock ppm correction is 2 trackingEvent history: 0x00230058Pkts dropped by burst limit: 0Global stats for slot 4************************Egr free buf: 255Egr host overruns: 0Egr unknown dest count: 0Last unknown dest ip : 0.0.0.0, port: 0Last unknown dest src ip : 0.0.0.0, port: 0Egr process switched: 0Egr oos: 0Egr unknown src count: 0, last unknown src ip: 0.0.0.0, port: 0Ingr overruns: 0NM cpu: 53.56 53.51 53.45 53.54Table 1provides a listing and description of all of the fields displayed by the show cem command. For each line of the display, the middle column of the table indicates whether that line of the display applies to a serial CEM (S), a T1/E1 CEM (TE), or both.
Table 1 show cem Command Output Display
You can clear all of the CEM channel statistics and restart statistics collection using the clear cem command. The following examples shows counters being cleared with the clear cem command.
Router# clear cem 1/3/1Cleared counters for cem 1/3/1.Router# clear cem allCleared counters for cem 1/1/0. Cleared counters for cem 1/3/1. Cleared counters for cem 2/0/0. Cleared counters for cem 2/1/0. Cleared counters for cem 2/2/0. Cleared counters for cem 2/3/0.Additional References
For additional information related to the CEoIP feature, see the following references.
Related Documents
Related Topic Document TitleCEoIP network modules
Release Notes for Cisco NM-CEM-4TE1 and NM-CEM-4SER Network Module Software
Standards
MIBs
RFCs
Technical Assistance
Command Reference
This section documents new commands (for Cisco IOS Release 12.3(7)T) and modified commands (for Cisco IOS Release 12.4(2)T).
•
cem
attach (CEM)
To enable port muxing to mux data from the slave port to the master port of a serial CEM channel, use the attach command in CEM configuration mode. To remove the slave port from the master port, use the no form of the command.
attach port
no attach port
Syntax Description
Defaults
Port muxing is not active.
Command Modes
CEM
Command History
Usage Guidelines
CEM serial ports can have a maximum of two master ports with any unique permutation of slave port. The attach command must follow the cem port command in a configuration. To remove the slave port from the master port use the no form of the command. If all the slave ports from the master port are removed, the master port will behave as a normal serial port (that is, no mux or demux operations will be preformed.).
Mux to Single Master Port
In this example, three slave ports are muxed to a single master port 0.
cem port 1/0/0attach 1attach 2attach 3Mux to Multiple Master Ports
In this example, two master ports 0,1 have been created. Here, slave port 2 is muxed to master port 0 and slave port 3 is muxed to master port 1.
cem port 1/0/0attach 2cem port 1/1/0attach 3Related Commands
Command Descriptionport
Specifies the CEM channel, or master port, to which slaves ports will be muxed.
cem
To enter circuit emulation (CEM) configuration mode, use the cem command in global configuration mode.
cem slot/port/channel
Syntax Description
Command Default
CEM configuration mode is not available.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enter CEM configuration mode to allow the configuration of all CEM options.
Examples
The following example shows how to enter CEM configuration mode:
Router(config)# cem 1/2/0
Router(config-cem)#Related Commands
cem-group
To create a circuit emulation (CEM) channel from one or more time slots of a T1 or E1 line of an NM-CEM-4TE1 network module, use the cem-group command in controller configuration mode. To remove a CEM group and release the associated time slots, use the no form of this command.
cem-group group-number {unframed | timeslots time-slot-range [speed kbps]}
no cem-group group-number
Syntax Description
Command Default
No CEM groups are defined.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to create CEM channels on the T1 or E1 network module, NM-CEM-4TE1. A maximum of 64 channels may be created on an NM-CEM-4TE1.
Examples
The following example shows how to create circuit emulation group number 0 with a single CEM channel including all time slots and the framing structure of the line on an NM-CEM-4TE1.
Router(config-controller)# cem-group 0 unframedThe following example shows how to create circuit emulation channel number 6 with T1 channel time slots one through four, nine, and ten using all eight bits of each time slot on an NM-CEM-4TE1.
Router(config-controller)# cem-group 6 timeslots 1-4,9,10 speed 64Related Commands
clear cem
To clear circuit emulation (CEM) statistics, use the clear cem command in privileged EXEC mode.
clear cem {slot | slot/port/channel | all}
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to clear CEM statistics for CEM channel number 10 on the card installed in slot 1, port 1.
Router# clear cem 1/1/10
Related Commands
clock mode
To configure the clock mode of a serial circuit emulation (CEM) channel, use the clock mode command in CEM configuration mode. To reset the clock mode to its default, use the no form of this command.
clock mode {normal | split}
no clock mode
Syntax Description
Command Default
The serial CEM channel clock defaults to normal mode.
Command Modes
CEM configuration
Command History
Usage Guidelines
This command applies only to serial ports.
Examples
The following example shows how to configure the CEM clock for normal mode.
Router(config-cem)# clock mode normal
Related Commands
clock rate
To configure the clock rate for the hardware connections on serial interfaces, such as network interface modules (NIMs) and interface processors, to an acceptable bit rate, use the clock rate command in interface configuration mode or Circuit Emulation Module (CEM) configuration mode. To remove the clock rate if you change the interface from a DCE to a DTE device, use the no form of this command. Using the no form of this command on a DCE interface sets the clock rate to the hardware-specific default value.
clock rate {line | rate}
no clock rate
Syntax Description
Defaults
No clock rate is configured.
Command Modes
Interface configuration
CEM configuration in Circuit Emulation Module (CEM)Command History
Usage Guidelines
Using the no form of this command on a DCE interface sets the clock rate to the hardware-dependent default value.
Cable Length
Be aware that the fastest speeds might not work if your cable is too long and that speeds faster than 148,000 bits per second are too fast for EIA/TIA-232 signaling. It is recommended that you use the synchronous serial EIA/TIA-232 signal at speeds up to 64,000 bits per second only. To permit a faster speed, use EIA/TIA-449 or V.35.
Synchronous Serial Port Adapters
For the synchronous serial port adapters (PA-8T-V35, PA-8T-X21, PA-8T-232, and PA-4T+) on Cisco 7200 series routers and on second-generation Versatile Interface Processors (VIP2s) in Cisco 7500 series routers, the clock rate that you enter is rounded (if needed) to the nearest value that your hardware can support. To display the clock rate value for the port adapter, use the show running-config command.
If you plan to boot from a network (TFTP) server over a synchronous serial port adapter interface and have a boot image prior to Cisco IOS Release 11.1(9)CA that does not support nonstandard (rounded) clock rates for the port adapters, you must use one of the following standard clock rates:
1200, 2400, 4800, 9600, 19200, 38400, 56000, 64000
CEM Network Modules
The following clock rates are supported on CEM Network Modules:
200, 300, 400, 600, 800, 1200, 1800, 2400, 3200, 3600, 4800, 6400, 7200, 8000, 9600, 12000, 12800, 14400, 16000, 16800, 19200, 24000, 28800, 32000, 38400, 48000, 56000, 57600, 64000, 76800, 84000, 96000, 112000, 115200, 128000, 144000, 168000, 192000, 224000, 230400, 256000, 288000, 336000, 384000, 448000, 512000, 672000, 768000, 772000, 896000, 1024000, 1152000, 1344000, 1536000, 1544000, 1792000, 1920000, 2048000
Examples
Network as Clock Source Example
The following example shows how to set the clock rate to use the network as the clock source:
Router(config)# interface serial 0Router(config-if)# clock rate lineClock Rate on Synchronous Serial Port Example
The following example shows how to set the clock rate on a synchronous serial port adapter in slot 5, port 0 to 1,234,567 bps. In this example, the clock rate is adjusted to 1,151,526 bps.
Router(config)# interface serial 5/0Router(config-if)# clock rate 1234567%Clockrate rounded to nearest value that your hardware can support.Clock Rate Rounded on Serial Enterface Example
The following example shows how to determine the exact clock rate that the serial interface was rounded to by using the show running-config command.
Router# show running-configBuilding configuration......!interface Serial5/0no ip addressclockrate 1151526!CEM Channel Example
This example shows the statistics for the current CEM configuration.
Router# show cem 4/1/0cem infocem 4/1/0 is upLine state is upOperational state is activeNear end ip address: 172.31.28.2, udp port: 15901Far end ip address: 172.31.28.10, udp port: 15901IP payload size: 512IP dscp : 0x28Idle pattern length: 8 , Idle Pattern: 0xFFPayload compression is disabledData protection is disabledDejitter buffer size is 60 msChannel clock rate is 2048000 bpsPhysical interface is E1 unframedIngress packets: 32505156, dropped: 0, overruns: 0Egress packets: 32505158, dropped: 637, lost pkts: 0Egress out of sequence pkts: 0Egress overruns: 16, underruns: 244Egress corrupt pkts rcvd: 030 second ingress rate 2050321 bits/sec, 500 packets/sec30 second egress rate 2050184 bits/sec, 500 packets/secTx interrupts: 32504249Reorder queue flush: 0, visited: 0, max wait window: 0Network jitter max: 8 ms, average: 1 ms, min: 0 msAdaptive clock ppm correction is 2 trackingEvent history: 0x00230058Pkts dropped by burst limit: 0Global stats for slot 4************************Egr free buf: 255Egr host overruns: 0Egr unknown dest count: 0Last unknown dest ip : 0.0.0.0, port: 0Last unknown dest src ip : 0.0.0.0, port: 0Egr process switched: 0Egr oos: 0Egr unknown src count: 0, last unknown src ip: 0.0.0.0, port: 0Ingr overruns: 0NM cpu: 53.56 53.51 53.45 53.54Related Commands
Command Descriptionshow running-config
Displays the current configuration.
show cem
Displays circuit emulation statistics.
clock source (CEM)
To configure the clock source of a circuit emulation (CEM) network module port, use the clock source command in CEM configuration mode or controller configuration mode. To return to the default clock source, use the no form of this command.
Cisco NM-CEM-4SER
clock source {internal | loop | adaptive}
no clock source {internal | loop | adaptive}
Cisco NM-CEM-4TE1
clock source {internal | line | adaptive channel-number [closed-loop | open-loop | coarse]}
no clock source {internal | line | adaptive channel-number [closed-loop | open-loop | coarse]}
Syntax Description
Command Default
Cisco NM-CEM-4SER
The clock source defaults to internal.
Cisco NM-CEM-4TE1
The clock source defaults to line.
Command Modes
Cisco NM-CEM-4SER
CEM configuration
Cisco NM-CEM-4TE1
Controller configuration
Command History
Release Modification12.3(7)T
This command was introduced.
12.4(2)T
The closed-loop, open-loop, and coarse keywords were added.
Usage Guidelines
When clock source internal is specified, the clocks provided by the network module are derived from either of the following source:
•
The router's backplane TDM clock frequency (in any router equipped with a TDM backplane bus)
•
The master oscillator on the network module (in any router not equipped with a TDM backplane bus)
When the adaptive keyword is specified, the clocks provided by the network module are derived from the same source as in the clock source internal case. However, the derived frequency is further adjusted up or down on the basis of the measured average fill of the egress dejitter buffer of the connection. If the dejitter buffer is perceived to be slowly filling, the frequency is adjusted slightly upward. If the dejitter buffer is perceived to be slowly depleting, the frequency is adjusted slightly downward.
Cisco NM-CEM-4SER
When the loop keyword is specified, the clock provided by the NM-CEM-4SER is the same as the clock provided to the NM-CEM-4SER from the attached CPE. The specification of clock source loop is only valid when the clock mode split command is specified. The clock mode command is used only during configuration of the NM-CEM-4SER.
Cisco NM-CEM-4TE1
In Cisco IOS Release 12.4(2)T, the adaptive clocking algorithm is enhanced to provide better adaptive clock accuracy. Three new keywords are used to specify the preferred mode:
•
closed-loop—Specifies the closed loop mode. Taking advantage of the fact that a T1 or E1 link uses the same clock in both directions, the adaptive clock algorithm enhancements are used to improve the adaptive clock accuracy. The same clock must be used in both directions for the closed loop mode, and both ends of the CEM must be running a Cisco IOS release that supports the enhanced adaptive clock algorithm. Use the closed loop mode when clock accuracy is required, the master clock from the customer premises equipment (CPE) is of good quality, and the clocks are the same in both directions of the T1 or E1 link.
Note
Do not use the closed loop mode in applications where the clocks are different for the two directions of the T1 or E1 link.
•
open-loop—Specifies the open loop mode. Some of the adaptive clock algorithm is used, but this mode does not require the clocks to be the same in both directions. This mode is compatible with previous Cisco IOS releases and is the default mode if no keyword is specified. Use the open loop mode when the master clock from the CPE is of good quality, but the clocks are not the same in both directions of the T1 or E1 link.
•
coarse—Specifies the coarse mode. The coarse mode uses the original adaptive clock algorithm and is used when the stability of the master clock derived from the CPE is not guaranteed. This mode is compatible with previous Cisco IOS releases.
Examples
The following example shows how to configure the clock source for the serial CEM network module, NM-CEM-4SER:
Router(config-cem)# clock source loopThe following example shows how to configure the clock source for the T1/E1 CEM network module, NM-CEM-4TE1:
Router(config-controller)# clock source adaptive 6The following example shows how to configure the clock source for an NM-CEM-4TE1 using the closed-loop mode to improve the adaptive clock accuracy:
Router(config-controller)# clock source adaptive 5 closed-loopRelated Commands
Command Descriptioncem
Enters circuit emulation configuration mode.
clock mode
Configures the clock mode on an NM-CEM-4SER network module.
show cem
Displays CEM channel statistics.
control-lead sampling-rate
To configure the sampling rate of input control leads, use the control-lead sampling-rate command in CEM configuration mode.
control-lead sampling-rate rate
Syntax Description
Command Default
The input control lead sampling rate defaults to 0 (no sampling).
Command Modes
CEM configuration
Command History
Usage Guidelines
This command applies only to serial channels. This command does not have a no form; to disable control-lead sampling, set the rate argument to 0.
Examples
The following example shows how to configure the ingress control-lead sampling rate to 20 samples per second on a serial CEM port.
Router(config-cem)# control-lead sampling-rate 20
Related Commands
control-lead state
To specify the state of an output control lead, use the control-lead state command in CEM configuration mode. The choice of output lead depends on whether the port is DCE or DTE.
control-lead state {active | fail} output-lead {on | off | follow} [{local | remote} follow-lead] [and|or]
Syntax Description
Command Default
The default Active template that is activated depends on whether the port is DCE or DTE. The default Fail template deactivates all signals. Table 2 shows the various control-lead default states.
Table 2 Control-Lead Default States
Lead Number DCE Name DTE Name Active Default Fail Default1
CTS
RTS
On
Off
2
DSR
DTR
On
Off
3
DCD
—
On
Off
4
—
LL
Off
—
5
TM
—
On
Off
6
RI
RL
Off
Off
Command Modes
CEM configuration
Command History
Release Modification12.3(7)T
This command was introduced.
12.4(2)T
The and and or keywords were added to support port muxing.
Usage Guidelines
This command applies only to serial ports. This command does not have a no form; to disable the control lead, specify the off keyword.
Output Control Lead States
The state of each output control lead may be specified to assume a constant level (on or off) or to change on the basis of the state of any input control lead, either at the local data port or at the remote data port.
EIA Pin Maps
Local EIA pin of the muxed ports map to a single EIA pin on the remote side, such that a state change in any of the muxed EIA pins are reflected on the mapped EIA pin on the remote side
Examples
The following example shows how to specify the state of an output control lead.
Router(config-cem)# control-lead state active cts on
Related Commands
Command Descriptioncem
Enters circuit emulation configuration mode.
control-lead sampling-rate
Configures the sampling rate of input control leads.
show cem
Displays CEM channel statistics.
crc-threshold
To define a severely errored second (SES) by specifying the number of cyclic redundancy check (CRC) errors that occur in one second, use the crc-threshold command in controller configuration mode. To return to the default value, use the no form of this command.
crc-threshold value
no crc-threshold
Syntax Description
value
Number of CRC errors in one second that results in the second being declared a severely errored second (SES). Range is from 0 to 3000. Default is 320.
Command Default
A default SES is defined by a value of 320 CRC errors per second.
Command Modes
Controller configuration
Command History
Usage Guidelines
On a T1 port, this command applies only if extended super frame (ESF) framing is used because the super frame (SF) (also known as D4) frame structure does not include any CRC protection.
This command does not apply to an E1 port.
Examples
The following example shows how to set the CRC threshold at 512 CRC errors in one second.
Router(config-controller)# crc-threshold 512data-protection
To enable data protection for a circuit emulation (CEM) channel, use the data-protection command in CEM configuration mode. To disable data protection, use the no form of this command.
data-protection
no data-protection
Syntax Description
This command has no arguments or keywords.
Command Default
Data protection is disabled for a CEM channel.
Command Modes
CEM configuration
Command History
Examples
The following example demonstrates how to enable data protection.
Router(config-cem)# data-protectionRelated Commands
Command Descriptioncem
Enters circuit emulation configuration mode.
clear cem
Clears CEM channel statistics.
show cem
Displays CEM channel statistics.
data-strobe
To specify an input control lead to be monitored as an indicator of valid data, use the data-strobe command in CEM configuration mode. To disable the monitoring of an input control lead, use the no form of this command.
data-strobe input-lead {on | off}
no data-strobe
Syntax Description
Command Default
No input control lead is monitored.
Command Modes
CEM configuration
Command History
Usage Guidelines
Any input control signal on a serial data port may be configured as a "data strobe" to indicate to the NM-CEM-4SER network module whether ingress data on the port should be encapsulated for transmission or ignored. If the data-strobe command is specified with the on keyword, data packets are created and sent when the input lead is asserted. If the data strobe is off (either intentionally or as a result of the failure of the customer premises equipment [CPE]), no data packets are created, and this results in preservation of bandwidth in the IP network.
This command applies only to serial ports.
Examples
The following example demonstrates how to specify that packets are to be created and sent to the far end only when the DTR input control lead is asserted.
Router(config-cem)# data-strobe dtr on
Related Commands
dejitter-buffer
To configure the size of the dejitter buffer, use the dejitter-buffer command in CEM configuration mode. To restore the dejitter buffer to its default size, use the no form of this command.
dejitter-buffer size
no dejitter-buffer
Syntax Description
Command Default
The dejitter buffer defaults to 60 milliseconds.
Command Modes
CEM configuration
Command History
Examples
The following example shows how to set the dejitter buffer to 200 milliseconds.
Router(config-cem)# dejitter-buffer 200
Related Commands
Command Descriptioncem
Enters circuit emulation configuration mode.
clear cem
Clears CEM channel statistics.
show cem
Displays CEM channel statistics.
failure
To specify a time period before a circuit emulation (CEM) connection enters, or recovers from, a failed state, use the failure command in CEM configuration mode. To remove the time period, use the no form of this command.
failure {activation | deactivation} msec
no failure {activation | deactivation}
Syntax Description
Command Default
CEM channels enter or recover from a failed state immediately.
Command Modes
CEM configuration
Command History
Usage Guidelines
The detection of the failure of a CEM connection is determined by an underflow of the egress dejitter buffer. The failed state for a serial channel (on an NM-CEM-4SER) is defined by the control-lead state command, where the failed state for each egress control lead is specified. The failed state for a T1/E1 channel (on an NM-CEM-4TE1) is defined by the signaling command.
The detection of the repair of a CEM connection is determined by the egress dejitter buffer returning to its intended half-full state. The active state for a serial channel (on an NM-CEM-4SER) is defined by the control-lead state command where the active state for each egress control lead is specified. The active state for a T1/E1 channel (on an NM-CEM-4TE1) is defined using the signaling command that can be configured to carry the ABCD signaling bits transparently from end to end.
Examples
The following example shows that after a CEM connection (on an NM-CEM-4SER) failure is detected, the software will wait for 200 milliseconds before the CEM channel enters the failed state:
Router(config)# cem 2/0/0Router(config-cem)# control-lead state fail cts onRouter(config-cem)# failure activation 200The following example shows that after a CEM connection repair (on an NM_CEM-4TE1) is detected, the software will wait for 5000 milliseconds before the CEM channel enters the active (up) state:
Router(config)# cem 1/0/0Router(config-cem)# signaling state active cts onRouter(config-cem)# failure deactivation 5000Related Commands
framing (CEM)
To specify the framing format of a circuit emulation (CEM) T1 or E1 port, use the framing command in controller configuration mode. To reset the framing format of the port to its default value, use the no form of this command.
T1 Port
framing {sf | esf | unframed}
no framing
E1 Port
framing {crc4 | no-crc4 | unframed}
no framing
Syntax Description
Command Default
The framing format of a T1 line defaults to esf.
The framing format of an E1 line defaults to crc4.
If an unframed CEM channel is created on the port using the cem-group command, no framing structure is sought or imposed.Command Modes
Controller configuration
Command History
Usage Guidelines
Framing must be configured to match the framing format used by the attached equipment.
In order to change a line between unframed and any framed mode, you must first delete the CEM channels defined in the line.
Examples
The following example shows how to set the framing format of a CEM T1 port to be super frame format.
Router(config-controller)# framing sfThe following example shows how to set the framing format of a CEM E1 port to the G.704 standard with the optional CRC4 mechanism defined in time slot 0 disabled.
Router(config-controller)# framing no-crc4Related Commands
idle-pattern
To define the idle pattern that a circuit emulation (CEM) channel transmits when the channel experiences an underrun condition or to replace any missing packets, use the idle-pattern command in CEM configuration mode. To stop sending idle pattern data, use the no form of this command.
idle-pattern {pattern | length pattern1 [pattern2]}
no idle-pattern
Syntax Description
Command Default
For T1 or E1 channels, the default idle pattern is 0xFF.
For serial channels, the default idle pattern is 0xFF and 8 bits in length.Command Modes
CEM configuration
Command History
Usage Guidelines
Idle pattern data is always sent in multiples of one entire packet payload. If a single packet is missing from the arriving data stream it is replaced by an idle packet of the same payload size and composed of repetitions of the specified idle pattern. If the CEM channel outbound (egress) buffer experiences an underrun condition, identical idle packets are transmitted until the dejitter buffer is filled to at least half its total depth.
Examples
The following example shows how to configure a 32-bit idle pattern for a serial CEM channel.
Router(config-cem)# idle-pattern 32 0x12345678
Related Commands
Command Descriptioncem
Enters circuit emulation configuration mode.
clear cem
Clears CEM channel statistics.
show cem
Displays CEM channel statistics.
ip dscp
To enable the use of IP differentiated services code point (DSCP) for packets that originate from a circuit emulation (CEM) channel, use the ip dscp command in CEM configuration mode. To disable the use of IP DSCP, use the no form of this command.
ip dscp [dscp-value]
no ip dscp
Syntax Description
dscp-value
(Optional) Value placed in the DSCP field of IP packets that originate from a CEM channel. Range is from 0 to 63. Default is 46.
Command Default
IP DSCP is enabled for packets that originate from a CEM channel.
Command Modes
CEM configuration
Command History
Usage Guidelines
DSCP is mutually exclusive from both IP type of service (ToS) and IP precedence. Thus, if DSCP is configured, the ip tos command and the ip precedence command are both unavailable at the command-line interface (CLI).
Examples
The following example shows how to set the IP DSCP field value to 36.
Router(config-cem)# ip dscp 36Related Commands
Command Descriptionip precedence
Configures the IP precedence bits for the CEM channel.
ip tos
Configures the IP ToS bits for the CEM channel.
local ip address
To define an IP address to identify a local circuit emulation (CEM) channel, use the local ip address command in CEM xconnect configuration mode.
local ip address ip-address
Syntax Description
Command Default
The default local IP address is 0.0.0.0 for a CEM channel.
Command Modes
CEM xconnect configuration
Command History
Usage Guidelines
This command does not have a no form. To remove a local IP address, either configure a new local IP address or enter the no xconnect command to disable the connection and all its parameters.
The local IP address used to identify the local end of a CEM connection must be the same as the IP address defined by the remote-ip-address argument used in the xconnect command to identify the CEM channel at the other end of the CEM connection.
Note
If there are multiple CEM connections that originate from the same router, they may share the same
local IP address provided that each local IP address defines a unique UDP port number using the
local udp port command.Examples
The following example demonstrates how to configure the IP address of the local endpoint of the CEM over IP (CEoIP) connection.
Router(config-cem-xconnect)# local ip address 10.0.5.1
Related Commands
local udp port
To define the User Datagram Protocol (UDP) port of the local endpoint of a circuit emulation (CEM) connection, use the local udp port command in CEM xconnect configuration mode.
local udp port port
Syntax Description
port
Number of the CEM local UDP port. Possible values are 0, 2141, and 15872 through 16383. The default is 0.
Command Default
The default local UDP port number is 0 for the local endpoint of a CEM connection.
Command Modes
CEM xconnect configuration
Command History
Usage Guidelines
This command does not have a no form. To remove a local UPD port number, either configure a new UPD port number or enter the no xconnect command to disable the connection and all its parameters.
Examples
The following example demonstrates how to configure the UDP port of the local endpoint of the CEM over IP (CEoIP) connection.
Router(config-cem-xconnect)# local udp port 2141
Related Commands
loopback (CEM)
To set the loopback method for testing a T1, E1, or serial CEM interface, use the loopback command in controller configuration or CEM configuration mode. To remove any existing loopback, use the no form of this command.
Cisco NM-CEM-4SER
loopback {local | network}
no loopback
Cisco NM-CEM-4TE1
loopback {local {payload | line} | network}
no loopback
Syntax Description
Command Default
No loopback is configured for a CEM interface.
Command Modes
Cisco NM-CEM-4SER
CEM configuration
Cisco NM-CEM-4TE1
Controller configuration
Command History
Usage Guidelines
Use this command to create a loopback for a CEM interface. You can use a loopback to test for equipment malfunction caused by the interface.
The NM-CEM-4TE1 does not respond to loopback requests initiated by the CPE, locally attached or remote, using the extended super frame (ESF) Facility Data Link (FDL) mechanism or by any other mechanism.
The NM-CEM-4SER does not respond to any form of loopback request initiated by the locally attached or remote CPE on the Local Loop (LL) or Remote Loop (RL) control leads. Nor does the NM-CEM-4SER respond to any form of loopback request initiated by the locally attached or remote CPE using in-band loopback codes.
Examples
The following example shows how to create a loopback on a CEM T1/E1 interface so that data received from a remote CPE is transmitted back to the remote CPE on the network.
Router(config-controller)# loopback networkThe following example shows how to create a loopback of data in individual time slots on a CEM T1/E1 interface. Data received from a locally attached CPE will be sent back to the locally attached CPE.
Router(config-controller)# loopback local payloadThe following example shows how to create a loopback on a serial CEM channel so that data received from a remote CPE is transmitted back to the remote CPE on the network.
Router(config-cem)# loopback networkRelated Commands
Command Descriptioncem
Enters circuit emulation configuration mode.
controller
Enters controller configuration mode.
payload-compression
To enable payload compression, use the payload-compression command in CEM configuration mode. To disable payload compression, use the no form of this command.
payload-compression
no payload-compression
Syntax Description
This command has no arguments or keywords.
Command Default
Payload compression is disabled by default.
Command Modes
CEM configuration
Command History
Usage Guidelines
Payload compression can be enabled only for a maximum of 3 Mbps per network module.
Examples
The following example demonstrates how to enable payload compression.
Router(config-cem)# payload-compression
Related Commands
Command Descriptioncem
Enters circuit emulation configuration mode.
payload-size
Configures payload size.
show cem
Displays CEM statistics.
payload-size
To configure the payload size of a circuit emulation (CEM) over IP (CEoIP) packet, use the payload-size command in CEM configuration mode. To restore the default payload size, use the no form of this command.
payload-size size
no payload-size
Syntax Description
Command Default
The default payload size for a serial channel is 32 bytes. Defaults for T1 and E1 channels are shown in Table 3 and Table 4.
Table 3 Default Payload Size for N*64-kbps T1/E1 Channels
Table 4 Default Payload Size for N*56-kbps T1 Channels
Command Modes
CEM configuration
Command History
Usage Guidelines
Use this command to configure the size of each CEoIP packet. Smaller sizes reduce delay but diminish efficiency.
Note
The payload size must be a multiple of the number of time slots and 16. The payload size entered
by the user will be automatically changed to match the above requirement, and a console message
will inform the user of this change.Examples
The following example demonstrates how to configure a payload size of 224.
Router(config-cem)# payload-size 224Related Commands
Command Descriptioncem
Enters circuit emulation configuration mode.
payload-compression
Enables payload compression.
show cem
Displays CEM channel statistics.
remote udp port
To define the User Datagram Protocol (UDP) port of the remote endpoint of a circuit emulation (CEM) connection, use the remote udp port command in CEM xconnect configuration mode.
remote udp port port
Syntax Description
port
Number of the circuit emulation (CEM) remote UDP port. Possible values are 0, 2142, and 15872 through 16383. The default is 0.
Command Default
The default UDP port number is 0 for the remote endpoint of a CEM connection.
Command Modes
CEM xconnect configuration
Command History
Usage Guidelines
This command does not have a no form. To remove a remote UPD port number, either configure a new UPD port number or enter the no xconnect command to disable the connection and all its parameters.
Examples
The following example demonstrates how to configure the UDP port of the remote endpoint of the CEM over IP (CEoIP) connection.
Router(config-cem-xconn)# remote udp port 2142
Related Commands
show cem
To display circuit emulation (CEM) statistics, use the show cem command in privileged EXEC mode.
show cem {slot/port/channel | summary}
Syntax Description
Command Modes
Privileged EXEC
Command History
Release Modification12.3(7)T
This command was introduced.
12.4(2)T
Output was modified to support enhanced adaptive clocking.
Examples
show cem summary Example
The following example shows a summary of some of the configuration parameters of the CEM channels.
Router# show cem summarycem summaryCSTATE: CEM stateLSTATE: line stateOSTATE: operational statePSIZE: payload-sizePCOMP: payload-compressionDPROT: data-protectionCEM CSTATE LSTATE OSTATE PSIZE PCOMP DPROT----------------------------------------------------------------------2/0/0 shutdown up config-incomplete 256 disabled disabled2/1/0 shutdown up config-incomplete 256 disabled disabled2/2/0 shutdown up config-incomplete 256 disabled disabled2/3/0 shutdown up config-incomplete 256 disabled disabled4/0/1 up up active 96 enabled disabled4/0/2 up up active 96 enabled disabled4/0/3 up up active 96 enabled disabled4/0/4 up up active 96 enabled disabled4/0/5 up up active 96 enabled disabled4/0/6 up up active 96 enabled disabled4/0/7 up up active 96 disabled disabled4/0/8 up up active 96 disabled disabled4/0/9 up up active 96 disabled disabled4/0/10 up up active 96 disabled disabled4/0/11 up up active 96 disabled disabled4/0/12 up up active 96 disabled disabled4/0/13 up up active 96 disabled disabled4/0/14 up up active 96 disabled disabled4/1/1 down down config-incomplete 96 enabled disabled4/1/2 down down config-incomplete 96 enabled disabled4/1/3 down down config-incomplete 96 enabled disabled4/1/4 down down config-incomplete 96 enabled disabled4/1/5 down down config-incomplete 96 enabled disabled4/1/6 down down config-incomplete 96 enabled disabled4/1/7 down down config-incomplete 96 disabled disabled4/1/8 down down config-incomplete 96 disabled disabled4/1/9 down down config-incomplete 96 disabled disabled4/1/10 down down config-incomplete 96 disabled disabled4/1/11 down down config-incomplete 96 disabled disabled4/1/12 down down config-incomplete 96 disabled disabled4/1/13 down down config-incomplete 96 disabled disabled4/1/14 down down config-incomplete 96 disabled disabledTable 5 describes the significant fields shown in the display.
Verifying a CEM Network Module Example
The following example displays the status of a configured CEM network module. This example uses the show cem command to monitor the configuration, status and performance of a particular CEM channel.
Router# show cem 4/1/0cem infocem 4/1/0 is upLine state is upOperational state is activeNear end ip address: 172.31.28.2, udp port: 15901Far end ip address: 172.31.28.10, udp port: 15901IP payload size: 512IP dscp : 0x28Idle pattern length: 8 , Idle Pattern: 0xFFPayload compression is disabledData protection is disabledDejitter buffer size is 60 msChannel clock rate is 2048000 bpsPhysical interface is E1 unframedIngress packets: 32505156, dropped: 0, overruns: 0Egress packets: 32505158, dropped: 637, lost pkts: 0Egress out of sequence pkts: 0Egress overruns: 16, underruns: 244Egress corrupt pkts rcvd: 030 second ingress rate 2050321 bits/sec, 500 packets/sec30 second egress rate 2050184 bits/sec, 500 packets/secTx interrupts: 32504249Reorder queue flush: 0, visited: 0, max wait window: 0Network jitter max: 8 ms, average: 1 ms, min: 0 msAdaptive clock ppm correction is 2 trackingEvent history: 0x00230058Pkts dropped by burst limit: 0Global stats for slot 4************************Egr free buf: 255Egr host overruns: 0Egr unknown dest count: 0Last unknown dest ip : 0.0.0.0, port: 0Last unknown dest src ip : 0.0.0.0, port: 0Egr process switched: 0Egr oos: 0Egr unknown src count: 0, last unknown src ip: 0.0.0.0, port: 0Ingr overruns: 0NM cpu: 53.56 53.51 53.45 53.54Table 1provides a listing and description of all of the fields displayed by the show cem command. For each line of the display, the middle column of the table indicates whether that line of the display applies to a serial CEM (S), a T1/E1 CEM (TE), or both.
Table 6 show cem Command Output Display
You can clear all of the CEM channel statistics and restart statistics collection using the clear cem command. The following examples shows counters being cleared with the clear cem command.
Router# clear cem 1/3/1Cleared counters for cem 1/3/1.Router# clear cem allCleared counters for cem 1/1/0. Cleared counters for cem 1/3/1. Cleared counters for cem 2/0/0. Cleared counters for cem 2/1/0. Cleared counters for cem 2/2/0. Cleared counters for cem 2/3/0.Related Commands
Commands Descriptioncem
Enters circuit emulation configuration mode.
clear cem
Clears CEM statistics.
signaling
To enable channel-associated signaling (CAS), use the signaling command in CEM configuration mode. To disable signaling, use the no form of this command.
signaling [on-hook-pattern] [off-hook-pattern] [msec]
no signaling [on-hook-pattern] [off-hook-pattern] [msec]
Syntax Description
Command Default
CAS is disabled.
Command Modes
CEM configuration
Command History
Release Modification12.3(7)T
This command was introduced.
12.3(7)T1
The on-hook-pattern, off-hook-pattern, and msec arguments were added.
Usage Guidelines
When a T1/E1 channel with signaling enabled is placed in the failed state, the on-hook pattern is sent to the attached device for a duration specified by the msec attribute. After the time specified by the msec attribute, the off-hook pattern is sent to the attached device for as long as the CEM connection remains failed.
The on-hook pattern parameter specifies, as a single hexadecimal character, the ABCD signaling bits sent to the attached device (typically a PBX) to simulate the remote PBX sending notification that any call in progress has been terminated or is on-hook. This provides a forced disconnect of any calls when the CEM connection fails.
The off-hook pattern parameter specifies, as a single hexadecimal character, the ABCD signaling bits sent to the attached device (typically a PBX) to simulate the remote PBX sending notification that a channel is already in use, or is off-hook. This prevents the attached PBX from trying to use the failed channel to place a new call while the CEM connection remains failed.
Examples
The following example shows how to enable signaling.
Router(config-cem)# signaling
The following example shows how to enable signaling with onhook and offhook parameters:
Router(config-cem)# signalling 0x0 0x1 101Delay will be set to 150 msRelated Commands
xconnect (CEM)
To build one end of a circuit emulation (CEM) connection and to enter CEM xconnect configuration mode, use the xconnect command in CEM configuration mode. To remove any existing CEM connections from this CEM channel, use the no form of this command.
xconnect remote-ip-address virtual-connect-ID encapsulation encapsulation-type
no xconnect
Syntax Description
Command Default
No CEM connections are built.
Command Modes
CEM configuration
Command History
Examples
The following example shows how to build one end of a CEoIP connection and to enter CEM xconnect configuration mode.
Router(config-cem)# xconnect 10.0.5.1 0 encapsulation udpRouter(config-cem-xconnect)#Related Commands
Copyright © 2004-2006 Cisco Systems, Inc. All rights reserved.




