Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide, Release 15.3(3)S


Command	Purpose
Switch(config)# card type oc3 slot bay	Configures the OC-3 Ports: •slot bay—Specifies the location of the port. Note The slot number is always 1 and the bay number is always 0 on the Cisco ME 3600X 24CX Series Switch.

Note On doing no card type T1/E1 0 1, the peer box controller will not go down untill the device is reloaded as prompted.

Configuring the Controller

Use the following command to configure the controller for SDH framing:


Command	Purpose
Switch(config)# controller sonet slot/bay/port	Selects the controller to configure and enters controller configuration mode, where: •slot/bay/port—Specifies the location of the interface. Note The slot number is always 1 and the bay number is always 0 on the Cisco ME 3600X 24CX Series Switch.

Configuring SDH

The following sections describe how to configure SDH on the OC3 port:

•Configuring SDH Mode

Configuring SDH Mode

To configure SDH mode, complete the following steps:


	Command	Purpose
Step 1	Switch(config-controller)# framing sdh	Specifies SDH as the frame type.
Step 2	Switch(config-controller)# aug mapping {au-3 \| au-4}	Configures AUG mapping for SDH framing. If the AUG mapping is configured to be AU-4, then the following muxing, alignment, and mapping will be used: TUG-3 <--> VC-4 <--> AU-4 <--> AUG If the mapping is configured to be AU-3, then the following muxing, alignment, and mapping will be used: VC-3 <--> AU-3 <--> AUG The default setting is au-3.
Step 3	Switch(config-controller)# clock source {internal \| line}	Sets the clock source, where: •internal—Specifies that the internal clock source is used. •line—Specifies that the network clock source is used. This is the default for T1 and E1.
Step 4	Switch(config-controller)# au-4 au-4# tug-3 tug-3# or Switch(config-controller)# au-3 au-3#	Configures AU-3, AU-4, and tributary unit groups, type 3 (TUG-3) for AU-4 and enters specific configuration mode. In SDH framing mode, each AU-3, TUG-3, and AU-4 can be configured with one of these commands. Depending on currently configured AUG mapping setting, this command further specifies TUG-3, AU-3 or AU-4 muxing. The CLI command parser enters into config-ctrlr-tug3 (SDH mode) or config-ctrlr-au3 (SDH mode), which makes only relevant commands visible. •au-4#—Range is from 1 to 4. For OC-3 mode, the value is 1. •tug-3#—Range is from 1 to 3. •au-3# —Range is from 1 to 12. For OC-3 mode, the value is 1-3. Note T1 can only be configured in au-3 mode, E1 can only be configured in the au-4 mode.
Step 5	Creates a CEM group, or channel-group for the AU-3 or AU-4. Valid values are: •e1— 1-3 •t1—1-4 •tug-2—1-7	SAToP CEM Group Switch(config-ctrlr-tug3)# tug-2 1 e1 1 cem-group 1 unframed CESoPSN CEM Group Switch(config-ctrlr-tug3)# tug-2 1 e1 1 cem-group 1 timeslots 1-31 Channel Group Switch(config-ctrlr-tug3)# tug-2 1 e1 1 [[channel-group channel-group-number] [timeslots list-of-timeslots]] Note DS0 level channelization is not supported for serial interfaces, however it is supported for CEM groups.

Optional Configurations

There are several standard, but optional, configurations that might be necessary to complete the configuration of your port.

•Configuring the Encapsulation Method

•Configuring the CRC Size for T1

•Configuring Keepalive Value

•Configuring MTU Value

Configuring the Encapsulation Method

When traffic crosses a WAN link, the connection needs a Layer 2 protocol to encapsulate traffic. To set the encapsulation method, use the following commands:


	Command	Purpose
Step 1	Switch(config)# interface serial slot/bay/port.au-3/tug-2/t1:channel-group	Selects the interface to configure and enters interface configuration mode. •slot/bay/port.au-3/tug-2/t1:channel-group—Specifies the location of the interface.
Step 2	Switch(config-if)# encapsulation encapsulation-type {hdlc \| ppp}	Sets the encapsulation method on the interface, where: •hdlc—Sets the High-Level Data Link Control (HDLC) protocol for serial interface. This encapsulation method provides the synchronous framing and error detection functions of HDLC without windowing or retransmission. This is the default for synchronous serial interfaces. •ppp—Sets point-to-point protocol (PPP) for serial interface. Note Frame relay encapsulation is not supported.

Configuring the CRC Size for T1

CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. The 4-Port Channelized OC-3/STM-1 IM uses a 16-bit cyclic redundancy check (CRC) by default, but also supports a 32-bit CRC. The designators 16 and 32 indicate the length (in bits) of the frame check sequence (FCS). A CRC of 32 bits provides more powerful error detection, but adds overhead. Both the sender and receiver must use the same setting.

To set the length of the cyclic redundancy check (CRC) on a T1 interface, use these commands:


	Command	Purpose
Step 1	Switch(config)# interface serial slot/bay/port.au-3/tug-2/t1:channel-group	Selects the interface to configure and enters interface configuration mode. •slot/bay/port.au-3/tug-2/t1:channel-group—Specifies the location of the interface.
Step 2	Switch(config-if)# crc {16 \| 32}	Selects the CRC size in bits, where: •16—16-bit CRC. This is the default. •32—32-bit CRC.

Configuring Keepalive Value


keepalive [period [retries]]	Specifies the frequency at which the Cisco IOS software sends messages to the other end of the line to ensure that a network interface is alive, where: •period—Specifies the time interval in seconds for sending keepalive packets. The default is 10 seconds. •retries—Specifies the number of times that the device continues to send keepalive packets without response before bringing the interface down. The default is 3 retries.

Configuring MTU Value


mtu bytes	Configures the maximum packet size for an interface in bytes. The packet size range is 64 - 7673. The default packet size is 4470 bytes.

Managing Interface Naming

The following sections describe how to manage interface naming on the Cisco ME 3600X 24CX Series Switch optical interface module.

Identifying Slots and Subslot

To specify the physical address for controller or interface configuration, use the interface and controller sonet commands, where:

•slot—Specifies the chassis slot number where the interface module is installed; the slot number is always 1 for interface modules on the Cisco ME 3600X 24CX Series Switch.

•bay—Specifies the subslot where the interface module is installed, the bay number is always 0 for interface modules on the Cisco ME 3600X 24CX Series Switch.

•port—Specifies the OC-3 port number.

For example, if the optical interface module is installed in slot 0 of the chassis, the controller configuration address is specified as controller sonet 1/0/0.

For channelized configuration, the interface address format for t1 is: slot/bay/port.au-3/tug-2/t1:channel-group, the interface address format for E1 is slot/bay/port.au-4/tug-3/tug-2/e1:channel-group where:

•channel-group—Specifies the logical channel group assigned to the time slots within the T1 link.

Naming Interfaces

Interface names are automatically generated, and the format varies based on the line card operating mode.

The listing below shows the formats of the serial interface for each interface type as well as interface formats for HDLC and CEM formats.

Note For HDLC framing, use the serial interface format.

If SDH-AUG mapping is au-3:

•interface serial slot/bay/port.au-3/tug-2/t1:channel-group

Configuring BERT

BERT (Bit-Error Rate Testing) is used for analyzing quality and for problem resolution of digital transmission equipment. BERT tests the quality of an interface by directly comparing a pseudorandom or repetitive test pattern with an identical locally generated test pattern.

The BERT operation is data-intensive. Regular data cannot flow on the path while the test is in progress. The path is reported to be in alarm state when BERT is in progress and restored to a normal state after BERT has been terminated.

Running Bit Error Rate Testing

Bit error rate testing (BERT) is supported on optical interfaces. The BERT testing is done only over a framed E1 or T1 signal and can be run only on one port at a time.

The interface modules contain onboard BERT circuitry. With this, the interface module software can send and detect a programmable pattern that is compliant with CCITT/ITU O.151, O.152, and O.153 pseudo-random and repetitive test patterns. BERTs allow you to test cables and signal problems in the field.

When running a BER test, your system expects to receive the same pattern that it is transmitting. To help ensure this, two common options are available:

•Use a loopback somewhere in the link or network

•Configure remote testing equipment to transmit the same BER test pattern at the same time

To run a BERT on an interface, perform the following optional tasks beginning in global configuration mode


	Command	Purpose
Step 1	Switch# configure terminal	Enters global configuration mode.
Step 2	Switch(config)# controller sonet slot/bay/port	Selects the controller to configure and enters controller configuration mode, where: •slot/bay/port—Specifies the location of the interface. The slot number is always 1 and the bay number is always 0 on the Cisco ME 3600X 24CX Series Switch
Step 3	Switch(config-controller)# au-4 au-4# tug-3 tug-3# or Switch(config-controller)# au-3 au-3#	Configures AU-3, AU-4, and tributary unit groups, type 3 (TUG-3) for AU-4 and enters specific configuration mode. In SDH framing mode, each AU-3, TUG-3, and AU-4 can be configured with one of these commands. Depending on currently configured AUG mapping setting, this command further specifies TUG-3, AU-3 or AU-4 muxing. The CLI command parser enters into config-ctrlr-tug3 (SDH mode) or config-ctrlr-au3 (SDH mode), which makes only relevant commands visible. •au-4#—Range is from 1 to 4. For OC-3 mode, the value is 1. •tug-3#—Range is from 1 to 3. •au-3# —Range is from 1 to 12. For OC-3 mode, the value is 1-3. Note T1 can only be configured in au-3 mode, E1 can only be configured in the au-4 mode.
Step 4	Switch(config-ctrlr-tug3)# tug-2 1 e1 1 [[channel-group channel-group-number] [timeslots list-of-timeslots]]	Creates a channel-group for the AU-3
Step 5	Switch(config-ctrlr-au3)#bert pattern {0s \| 1s \| 2^15 \| 2^23 } interval minutes	Specify the BERT pattern for the port and the duration of the test in minutes (1 to 1440 minutes). Note 0s, 1s, 2^15 and 2^23 patterns are supported.
Step 6	Switch(config-ctrlr-au3)#end	Exits confguration mode.
Step 7	Switch#show controllers sonet slot/bay/port	Displays the BERT test results.

The following keywords list different BERT keywords and their descriptions.

Caution

0s, 1s, 2^15 and 2^23 patterns are supported.

Table 3-1 BERT Pattern Descriptions
Keyword	Description
0s	Repeating pattern of zeros (...000...).
1s	Repeating pattern of ones (...111...).
2^15	Pseudo-random O.151 test pattern that is 32,768 bits in length.
2^23	Pseudo-ramdom 0.151 test pattern that is 1,048,575 bits in length.

Both the total number of error bits received and the total number of bits received are available for analysis. You can select the testing period from 1 minute to 24 hours, and you can also retrieve the error statistics anytime during the BER test.

Note To terminate a BER test during the specified test period, use the no bert command.

You can view the results of a BER test at the following times:

•After you terminate the test using the no bert command

•After the test runs completely

•Anytime during the test (in real time)

Example:

Switch#config terminal

Switch(config)#controller sonet 1/0/0

Switch(config-controller)#au-3 1

Switch(config-ctrlr-au3)#tug-2 1 t1 1 bert 2^15 interval 2

Switch(config-ctrlr-au3)#end

Switch#config terminal

*Jul  9 06:00:35.639: %SYS-5-CONFIG_I: Configured from console by consolet

Enter configuration commands, one per line.  End with CNTL/Z.

Switch(config)#controll sonet 1/0/0

Switch(config-controller)#au-3 1

Switch(config-ctrlr-au3)#tug-2 1 t1 1 bert pattern 2^15 interval 2

*Jul  9 06:02:50.231: %LINK-6-BERTSTATUS: Interface T1 1/0/0.1/1/1, BERT is not in sync

*Jul  9 06:02:50.231: %CONTROLLER-5-UPDOWN: Controller SONET 1/0/0 STM1.AU3/TU11/T1 1/1/1, 
changed state to bert down

*Jul  9 06:02:52.231: %LINK-3-UPDOWN: Interface Serial1/0/0.1/1/1:0, changed state to down

*Jul  9 06:02:53.231: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0/0.1/1/1:0, 
changed state to down

*Jul  9 06:03:00.231: %LINK-6-BERTSTATUS: Interface T1 1/0/0.1/1/1, BERT is sync

*Jul  9 06:04:50.267: %LINK-6-BERTSTATUS: Interface T1 1/0/0.1/1/1, BERT is done

*Jul  9 06:04:50.267: %CONTROLLER-5-UPDOWN: Controller SONET 1/0/0 STM1.AU3/TU11/T1 1/1/1, 
changed state to bert up

*Jul  9 06:04:52.267: %LINK-3-UPDOWN: Interface Serial1/0/0.1/1/1:0, changed state to up

*Jul  9 06:04:53.267: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0/0.1/1/1:0, 
changed state to up

Switch#end

To display BERT Results use the show controllers sonet command:

Switch#show controllers sonet 1/0/0.1/1/1

SONET 1/0/0 is up.

 Path mode C11

 AU-3 1, TUG-2 1, T1 1 (C-11 1/1/1) is down

 VT Receiver has no alarm.

  timeslots: 1-24

  FDL per AT&T 54016 spec.

  No alarms detected.

  Framing is ESF, Clock Source is Internal

  BERT test result (running)

     Test Pattern : 2^15, Status : Sync, Sync Detected : 1

     Interval : 2 minute(s), Time Remain : 1 minute(s)

     Bit Errors (since BERT started): 0 bits,

     Bits Received (since BERT started): 0 Kbits

     Bit Errors (since last sync): 0 bits

     Bits Received (since last sync): 0 Kbits

  Data in current interval (90 seconds elapsed):

     0 Line Code Violations, 0 Path Code Violations

     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs

     0 Unavail Secs, 0 Stuffed Secs

  Data in Interval 1:

     0 Line Code Violations, 0 Path Code Violations

     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs

     0 Unavail Secs, 0 Stuffed Secs

  Total Data (last 1 15 minute intervals):

     0 Line Code Violations,0 Path Code Violations,

     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,

     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs

     0 Unavail Secs, 0 Stuffed Secs

Note Bit Errors and Bits Received are always 0. The driver cannot detect the number of bits/error bits. The show controller <>/<>/<> bert command can only give information about SYNC state.

Configuring Circuit Emulation

This section provides information about how to configure CEM. CEM provides a bridge between a time-division multiplexing (TDM) network and a packet network, such as Multiprotocol Label Switching (MPLS). The router encapsulates the TDM data in the MPLS packets and sends the data over a CEM pseudowire to the remote provider edge (PE) router. Thus, function as a physical communication link across the packet network.

Note Only 512 pseudowires are supported on the Cisco ME3600X-24CX switch.

The following sections describe how to configure CEM:

•Configuring a CEM Group

•Using CEM Classes

•Configuring CEM Parameters

Note CEM is used as an element in configuring pseudowires including Structure-Agnostic TDM over Packet (SAToP) and Circuit Emulation Service over Packet-Switched Network (CESoPSN). For more information about configuring pseudowires, see Chapter 7 "Configuring Pseudowire."

Configuring a CEM Group

The following section describes how to configure a CEM group on the Cisco ME 3600X 24CX Series Switch.

Note You cannot configure the same cem group ID on different controllers.

SUMMARY STEPS

1. enable

2. configure terminal

3. controller sonet slot/bay/port

4. au-4 au-4# tug-3 tug-3#

au-3 au3

5. tug-2 tug-2 t1 t1

6. cem-group group-number {unframed | timeslots timeslot}

7. end


	Command	Purpose
Step 1	enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal	Enters global configuration mode.
Step 3	controller sonet slot/bay/port	Selects the controller to configure and enters controller configuration mode, where: •slot/bay/port—Specifies the location of the interface. The slot number is always 1 and the bay number is always 0 on the Cisco ME 3600X 24CX Series Switch
Step 4	au-4 au-4# tug-3 tug-3# or au-3 au-3#	Configures AU-3, AU-4, and tributary unit groups, type 3 (TUG-3) for AU-4 and enters specific configuration mode. Depending on the framing mode of SONET or SDH, each STS-1, AU-3, TUG-3, and AU-4 can be configured with one of these commands. Depending on currently configured AUG mapping setting, this command further specifies TUG-3, AU-3, AU-4 or STS-1 muxing. The CLI command parser enters into config-ctrlr-tug3 (SDH mode), config-ctrlr-au3 (SDH mode), or config-ctrlr-sts1 parser mode (SONET mode), which makes only relevant commands visible. •au-4#—Range is from 1 to 4. For OC-3 mode, the value is 1. •tug-3#—Range is from 1 to 3. •au-3# —Range is from 1 to 12. For OC-3 mode, the value is 1-3. T1 can only be configured in au-3 mode, E1 can only be configured in the au-4 mode.
Step 5	Creates a CEM group, or channel-group for the AU-3 or AU-4. Valid values are: •e1— 1-3 •t1—1-4 •tug-2—1-7	SAToP CEM Group Switch(config-ctrlr-tug3)# tug-2 1 e1 1 cem-group 1 unframed CESoPSN CEM Group Switch(config-ctrlr-tug3)# tug-2 1 e1 1 cem-group 1 timeslots 1-31 Channel Group Switch(config-ctrlr-tug3)# tug-2 1 e1 1 [[channel-group channel-group-number] [timeslots list-of-timeslots]] DS0 level channelization is not supported for serial interfaces, however it is supported for CEM groups.
Step 6	cem-group group-number {unframed \| timeslots timeslot}	Creates a circuit emulation channel from one or more time slots of a T1 or E1 line. •The group-number keyword identifies the cem dircuit number to be used for this cem circuit. This number must be unique across all cem-circuits. The range is 0 to 2015. •Use the unframed keyword to specify that a single CEM channel is being created including all time slots and the framing structure of the line.This unframed keyword is used to create an SAToP circuit. •Use the timeslots keyword and the timeslot argument to specify the time slots to be included in the CEM channel. The list of time slots may include commas and hyphens with no spaces between the numbers. The range for T1 is 1 to 24. The range for E1 is 1 to 31.
Step 7	end	Exits controller configuration mode and returns to privileged EXEC mode.

Using CEM Classes

A CEM class allows you to create a single configuration template for multiple CEM pseudowires. Follow these steps to configure a CEM class:

Note The CEM parameters at the local and remote ends of a CEM circuit must match; otherwise, the pseudowire between the local and remote PE routers will not come up.

Note You cannot apply a CEM class to other pseudowire types such as ATM over MPLS.

SUMMARY STEPS

1. enable

2. configure terminal

3. class cem classname

4. payload-size size

5. dejitter-buffer size

6. exit

7. interface cem 1/0/number

8. cem group-number

9. cem class cem-class-name

10. xconnect peer-ip-address vc-id {encapsulation {mpls}

11. exit

12. exit


	Command	Purpose
Step 1	enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal	Enters global configuration mode.
Step 3	Switch(config)# class cem mycemclass	Creates a new CEM class.
Step 4	payload-size size dejitter-buffer size	Enter the configuration commands common to the CEM class. This example specifies a sample rate, payload size, and dejitter buffer.
Step 5	Switch(config-cem-class)# exit	Returns to the config prompt.
Step 6	Switch(config)# interface cem 1/0/1 Switch(config-if)#cem class cem-class-name Switch(config-if-cem)# xconnect 192.0.2.1 200 encapsulation mpls	Configure the CEM interface that you want to use for the new CEM class. Note The use of the xconnect command can vary depending on the type of pseudowire you are configuring.
Step 7	Switch(config-if-cem)# exit Switch(config-if)#	Exits the CEM interface.
Step 8	exit	Exits configuration mode.

Configuration Examples for CEM:

The following examples show how to configure a CESoP CEM circuit:

Switch(config)#controller sonet 1/0/0

Switch(config-controller)#au-3 1

Switch(config-ctrlr-au3)#tug-2 1 t1 2 cem-group 3 timeslots 1-24

Switch(config)#int cem 1/0/0

Switch(config-if)#cem 3

Switch(config-if-cem)#xconnect 12.12.12.12 3 encapsulation mpls

Switch(cfg-if-cem-xconn)#end

The following example shows how to configure a SAToP CEM circuit:

Switch(config-controller)#controller sonet 1/0/2

Switch(config-controller)#au-3 1

Switch(config-ctrlr-au3)#tug-2 1 t1 1 cem-group 4 unframed

Switch(config-if)#int cem 1/0/2

Switch(config-if)#cem 4

Switch(config-if-cem)#xconnect 12.12.12.12 4 encapsulation mpls

Switch(cfg-if-cem-xconn)#end

Configuring CEM Parameters

The following sections describe the parameters you can configure for CEM circuits.

•Configuring Payload Size (Optional)

•Setting the Dejitter Buffer Size

•Shutting Down a CEM Channel

Note The CEM parameters at the local and remote ends of a CEM circuit must match; otherwise, the pseudowire between the local and remote PE routers will not come up.

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 192 to 256 bytes.

Default payload sizes for an unstructured CEM channel are as follows:

•E1 = 256 bytes

•T1 = 192 bytes

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.

Shutting 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 Loopbacks

The following sections describe how to set loopbacks:

•Setting a Loopback on the Controller

•Setting a Loopback at the PDH Level

Note Only one loopback can be configured at conroller level or PDH level across all OC3 ports and PDHs.

Setting a Loopback on the Controller

To set a loopback on the controller, perform the following task:


Command	Purpose
Switch# configure terminal	Enters global configuration mode.
Switch(config)#controller sonet slot/bay/port	Selects the controller to configure and enters controller configuration mode, where: •slot/bay/port—Specifies the location of the interface. Note The slot number is always 1 and the bay number is always 0 on the Cisco ME 3600X 24CX Series Switch
Switch(config-controller)#loopback {local \| network}	Sets a loopback to test the OC3 port.

Setting a Loopback at the PDH Level

You can use the following loopback commands on the controller in global configuration mode:


Task	Command
Switch(config)#controller sonet slot/bay/port	Selects the controller to configure and enters controller configuration mode, where: •slot/bay/port—Specifies the location of the interface. Note The slot number is always 1 and the bay number is always 0 on the Cisco ME 3600X 24CX Series Switch
Switch(config-controller)# au-4 au-4# tug-3 tug-3# or Switch(config-controller)# au-3 au-3#	Configures AU-3, AU-4, and tributary unit groups, type 3 (TUG-3) for AU-4 and enters specific configuration mode. In SDH framing mode, each AU-3, TUG-3, and AU-4 can be configured with one of these commands. Depending on currently configured AUG mapping setting, this command further specifies TUG-3, AU-3 or AU-4 muxing. The CLI command parser enters into config-ctrlr-tug3 (SDH mode) or config-ctrlr-au3 (SDH mode), which makes only relevant commands visible. •au-4#—Range is from 1 to 4. For OC-3 mode, the value is 1. •tug-3#—Range is from 1 to 3. •au-3# —Range is from 1 to 12. For OC-3 mode, the value is 1-3. Note T1 can only be configured in au-3 mode, E1 can only be configured in the au-4 mode.
Switch(config-ctrlr-au3)#tug-2 tug-2 t1 t1 loopback[local \| network {line \| payload} \| remote {line {fdl \| inband} \| payload]	When framing in SDH with AU-3 AUG mapping, set a loopback to test a T1 link. Note The remote {line {fdl \| inband} \| payload keywords are displayed on the switch however they are not supported.

Note To remove a loopback, use the no loopback command.

Table 3-2 Loopback Descriptions
Loopback	Description
loopback local	Loops the incoming receive signal back out to the transmitter. You can specify whether to use the line or payload.
local line	The incoming signal is looped back in the interface module using the framer's line loopback mode. The framer does not reclock or reframe the incoming data. All incoming data is received by the interface module driver.
local payload	Loops the incoming signal back in the interface module using the payload loopback mode of the framer. The framer reclocks and reframes the incoming data before sending it back out to the network. When in payload loopback mode, an all 1s data pattern is received by the local HDLC receiver and the clock source is automatically set to line (overriding the clock source command). When the payload loopback is ended, the clock source returns to the last setting selected by the clock source command.
loopback remote iboc	Attempts to set the far-end T1 interface into line loopback. This command sends an in-band bit-oriented code to the far-end to cause it to go into line loopback. This command is available when using ESF or SF framing mode.
network line	Loops the incoming signal back in the interface module using the line loopback mode of the framer. The framer does not reclock or reframe the incoming data. All incoming data is received by the interface module driver.
network payload	Loops the incoming signal back using the payload loopback mode of the framer. The framer reclocks and reframes the incoming data before sending it back out to the network. When in payload loopback mode, an all 1s data pattern is received by the local HDLC receiver, and the clock source is automatically set to line (overriding the clock source command). When the payload loopback is ended, the clock source returns to the last setting selected by the clock source command.

Configuration Examples

Controller level Loopbacks:

Switch#configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Switch(config)#controll

Switch(config)#controller sonet 1/0/0

Switch(config-controller)#loopback local

PDH level loopbacks:

Switch#configure terminal

Switch(config)#controller sonet 1/0/0

Switch(config-controller)#au-3 1

Switch(config-ctrlr-au3)#tug-2 1 t1 4 loopback network line

Verifying Interface Configuration

Besides using the show running-configuration command to display your Cisco ME 3600X 24CX Series Switch configuration settings, you can use the show interface serial and the show controllers sonet commands to get detailed information on a per-port basis.

Verifying Per-Port Interface Status

To find detailed interface information on a per-port basis on an optical interface module, use the show interface serial and show controllers sonet commands.

Output of the show interface serial command:

Switch#show interface Serial 1/0/0.1/1/1:0

Serial1/0/0.1/1/1:0 is up, line protocol is up

  Hardware is SPA_TYPE_WHALES2_OCX

  Internet address is 1.1.1.1/24

  MTU 1500 bytes, BW 1536 Kbit/sec, DLY 20000 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation HDLC, crc 16, loopback not set

  Keepalive set (10 sec)

  Last input 00:00:03, output 00:00:06, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     85 packets input, 7154 bytes, 0 no buffer

     Received 72 broadcasts (0 IP multicasts)

     0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     98 packets output, 8558 bytes, 0 underruns

     0 output errors, 0 collisions, 4 interface resets

     0 unknown protocol drops

     0 output buffer failures, 0 output buffers swapped out

     3 carrier transitions no alarm present

  VC 0: timeslot(s): 1-24, Transmitter delay 0, non-inverted data

Output of the show controller sonet command:

Switch#show controllers sonet

SONET 1/0/0 is up.

  Hardware is SPA_TYPE_WHALES2_OCX

 Applique type is Channelized Sonet/SDH

 Clock Source is Line, AUG mapping is AU3.

Medium info:

  Type: SDH, Line Coding: NRZ,

 Regenerator Section:

  LOS = 0          LOF = 0                           BIP(B1) = 0

SONET/SDH Section Tables

  INTERVAL       CV    ES   SES  SEFS

  05:46-05:55     0     0     0     0

Multiplex Section:

  AIS = 0          RDI = 0          REI = 0          BIP(B2) = 0

Active Defects: None

Detected Alarms: None

Asserted/Active Alarms: None

Alarm reporting enabled for: SLOS SLOF SF B1-TCA B2-TCA

BER thresholds:  SF = 10e-3  SD = 10e-6

TCA thresholds:  B1 = 10e-6  B2 = 10e-6

Rx: S1S0 = 00

    K1 = 00,   K2 = 00

    J0 = 01

    RX S1 = 00

Tx: S1S0 = 00

    K1 = 00,   K2 = 00

    J0 = 01

SONET/SDH Line Tables

  INTERVAL       CV    ES   SES   UAS

  05:46-05:55     0     0     0     0

High Order Path:

PATH 1:

  AIS = 0          RDI = 0          REI = 0          BIP(B3) = 0

  LOP = 0          PSE = 0          NSE = 0          NEWPTR = 0

  LOM = 0          PLM = 0          UNEQ = 0

Active Defects: None

Detected Alarms: None

Asserted/Active Alarms: None

Alarm reporting enabled for: PLOP LOM B3-TCA

TCA threshold:  B3 = 10e-6

Rx: C2 = 02

Tx: C2 = 02

PATH TRACE BUFFER : STABLE

  C9 45 31 20 31 2F 30 2E 31 20 20 20 20 20 20 00     .E1 1/0.1      .

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

SONET/SDH Path Tables

  INTERVAL       CV    ES   SES   UAS

  05:46-05:55     0     0     0     0

PATH 2:

  AIS = 1          RDI = 0          REI = 0          BIP(B3) = 0

  LOP = 0          PSE = 0          NSE = 0          NEWPTR = 0

  LOM = 0          PLM = 0          UNEQ = 0

Active Defects: None

Detected Alarms: PAIS PPLM

Asserted/Active Alarms: PAIS

Alarm reporting enabled for: PLOP LOM B3-TCA

TCA threshold:  B3 = 10e-6

Rx: C2 = FF

Tx: C2 = 02

PATH TRACE BUFFER : STABLE

  A7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

SONET/SDH Path Tables

  INTERVAL       CV    ES   SES   UAS

  05:46-05:55     0     0     0     0

PATH 3:

  AIS = 1          RDI = 0          REI = 0          BIP(B3) = 0

  LOP = 0          PSE = 0          NSE = 0          NEWPTR = 0

  LOM = 0          PLM = 0          UNEQ = 0

Active Defects: None

Detected Alarms: PAIS PPLM

Asserted/Active Alarms: PAIS

Alarm reporting enabled for: PLOP LOM B3-TCA

TCA threshold:  B3 = 10e-6

Rx: C2 = FF

Tx: C2 = 02

PATH TRACE BUFFER : STABLE

  A7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

SONET/SDH Path Tables

  INTERVAL       CV    ES   SES   UAS

  05:46-05:55     0     0     0     0

STM1.AU3 1/0/0.1 is up.

  Hardware is SPA_TYPE_WHALES2_OCX

 Applique type is C11

 AU-3 1, TUG-2 1, T1 1 (C-11 1/1/1) is up

 VT Receiver has no alarm.

  timeslots: 1-24

  FDL per AT&T 54016 spec.

  No alarms detected.

  Framing is ESF, Clock Source is Internal

  Data in current interval (540 seconds elapsed):

     0 Line Code Violations, 0 Path Code Violations

     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs

     0 Unavail Secs, 0 Stuffed Secs

 AU-3 1, TUG-2 1, T1 2 (C-11 1/1/2)

    Not configured.

 AU-3 1, TUG-2 1, T1 3 (C-11 1/1/3)

    Not configured.

 AU-3 1, TUG-2 1, T1 4 (C-11 1/1/4)

    Not configured.

 AU-3 1, TUG-2 2, T1 1 (C-11 1/2/1)

    Not configured.

 AU-3 1, TUG-2 2, T1 2 (C-11 1/2/2)

    Not configured.

 AU-3 1, TUG-2 2, T1 3 (C-11 1/2/3)

    Not configured.

 AU-3 1, TUG-2 2, T1 4 (C-11 1/2/4)

    Not configured.

 AU-3 1, TUG-2 3, T1 1 (C-11 1/3/1)

    Not configured.

 AU-3 1, TUG-2 3, T1 1 (C-11 1/3/1)

    Not configured.

 AU-3 1, TUG-2 3, T1 2 (C-11 1/3/2)

    Not configured.

 AU-3 1, TUG-2 3, T1 3 (C-11 1/3/3)

    Not configured.

 AU-3 1, TUG-2 3, T1 4 (C-11 1/3/4)

    Not configured.

 AU-3 1, TUG-2 4, T1 1 (C-11 1/4/1)

    Not configured.

 AU-3 1, TUG-2 4, T1 2 (C-11 1/4/2)

    Not configured.

 AU-3 1, TUG-2 4, T1 3 (C-11 1/4/3)

    Not configured.

 AU-3 1, TUG-2 4, T1 4 (C-11 1/4/4)

    Not configured.

 AU-3 1, TUG-2 5, T1 1 (C-11 1/5/1)

    Not configured.

 AU-3 1, TUG-2 5, T1 2 (C-11 1/5/2)

    Not configured.

 AU-3 1, TUG-2 5, T1 3 (C-11 1/5/3)

    Not configured.

 AU-3 1, TUG-2 5, T1 4 (C-11 1/5/4)

    Not configured.

 AU-3 1, TUG-2 6, T1 1 (C-11 1/6/1)

    Not configured.

 AU-3 1, TUG-2 6, T1 2 (C-11 1/6/2)

    Not configured.

 AU-3 1, TUG-2 6, T1 3 (C-11 1/6/3)

    Not configured.

 AU-3 1, TUG-2 6, T1 4 (C-11 1/6/4)

    Not configured.

 AU-3 1, TUG-2 7, T1 1 (C-11 1/7/1)

    Not configured.

 AU-3 1, TUG-2 7, T1 2 (C-11 1/7/2)

    Not configured.

 AU-3 1, TUG-2 7, T1 3 (C-11 1/7/3)

    Not configured.

 AU-3 1, TUG-2 7, T1 4 (C-11 1/7/4)

    Not configured.

STM1.AU3 1/0/0.2 is down.

  Hardware is SPA_TYPE_WHALES2_OCX

 Applique type is C11

 AU-3 2, TUG-2 1, T1 1 (C-11 2/1/1)

    Not configured.

 AU-3 2, TUG-2 1, T1 2 (C-11 2/1/2)

    Not configured.

 AU-3 2, TUG-2 1, T1 3 (C-11 2/1/3)

    Not configured.

 AU-3 2, TUG-2 1, T1 4 (C-11 2/1/4)

    Not configured.

 AU-3 2, TUG-2 2, T1 1 (C-11 2/2/1)

    Not configured.

 AU-3 2, TUG-2 2, T1 2 (C-11 2/2/2)

    Not configured.

 AU-3 2, TUG-2 2, T1 3 (C-11 2/2/3)

    Not configured.

 AU-3 2, TUG-2 2, T1 4 (C-11 2/2/4)

    Not configured.

 AU-3 2, TUG-2 3, T1 1 (C-11 2/3/1)

    Not configured.

 AU-3 2, TUG-2 3, T1 2 (C-11 2/3/2)

    Not configured.

 AU-3 2, TUG-2 3, T1 3 (C-11 2/3/3)

    Not configured.

 AU-3 2, TUG-2 3, T1 4 (C-11 2/3/4)

    Not configured.

 AU-3 2, TUG-2 4, T1 1 (C-11 2/4/1)

    Not configured.

 AU-3 2, TUG-2 4, T1 2 (C-11 2/4/2)

    Not configured.

 AU-3 2, TUG-2 4, T1 3 (C-11 2/4/3)

    Not configured.

 AU-3 2, TUG-2 4, T1 4 (C-11 2/4/4)

    Not configured.

 AU-3 2, TUG-2 5, T1 1 (C-11 2/5/1)

    Not configured.

 AU-3 2, TUG-2 5, T1 2 (C-11 2/5/2)

    Not configured.

 AU-3 2, TUG-2 5, T1 3 (C-11 2/5/3)

    Not configured.

 AU-3 2, TUG-2 5, T1 4 (C-11 2/5/4)

    Not configured.

 AU-3 2, TUG-2 6, T1 1 (C-11 2/6/1)

    Not configured.

 AU-3 2, TUG-2 6, T1 2 (C-11 2/6/2)

    Not configured.

 AU-3 2, TUG-2 6, T1 3 (C-11 2/6/3)

    Not configured.

 AU-3 2, TUG-2 6, T1 4 (C-11 2/6/4)

    Not configured.

 AU-3 2, TUG-2 7, T1 1 (C-11 2/7/1)

    Not configured.

 AU-3 2, TUG-2 7, T1 2 (C-11 2/7/2)

    Not configured.

 AU-3 2, TUG-2 7, T1 3 (C-11 2/7/3)

    Not configured.

 AU-3 2, TUG-2 7, T1 4 (C-11 2/7/4)

    Not configured.

STM1.AU3 1/0/0.3 is down.

  Hardware is SPA_TYPE_WHALES2_OCX

 Applique type is C11

 AU-3 3, TUG-2 1, T1 1 (C-11 3/1/1)

    Not configured.

 AU-3 3, TUG-2 1, T1 2 (C-11 3/1/2)

    Not configured.

 AU-3 3, TUG-2 1, T1 3 (C-11 3/1/3)

    Not configured.

 AU-3 3, TUG-2 1, T1 4 (C-11 3/1/4)

    Not configured.

 AU-3 3, TUG-2 2, T1 1 (C-11 3/2/1)

    Not configured.

 AU-3 3, TUG-2 2, T1 2 (C-11 3/2/2)

    Not configured.

 AU-3 3, TUG-2 2, T1 3 (C-11 3/2/3)

    Not configured.

 AU-3 3, TUG-2 2, T1 4 (C-11 3/2/4)

    Not configured.

 AU-3 3, TUG-2 3, T1 1 (C-11 3/3/1)

    Not configured.

 AU-3 3, TUG-2 3, T1 2 (C-11 3/3/2)

    Not configured.

 AU-3 3, TUG-2 3, T1 3 (C-11 3/3/3)

    Not configured.

 AU-3 3, TUG-2 3, T1 4 (C-11 3/3/4)

    Not configured.

 AU-3 3, TUG-2 4, T1 1 (C-11 3/4/1)

    Not configured.

 AU-3 3, TUG-2 4, T1 2 (C-11 3/4/2)

    Not configured.

 AU-3 3, TUG-2 4, T1 3 (C-11 3/4/3)

    Not configured.

 AU-3 3, TUG-2 4, T1 4 (C-11 3/4/4)

    Not configured.

 AU-3 3, TUG-2 5, T1 1 (C-11 3/5/1)

    Not configured.

 AU-3 3, TUG-2 5, T1 2 (C-11 3/5/2)

    Not configured.

 AU-3 3, TUG-2 5, T1 3 (C-11 3/5/3)

    Not configured.

 AU-3 3, TUG-2 5, T1 4 (C-11 3/5/4)

    Not configured.

 AU-3 3, TUG-2 6, T1 1 (C-11 3/6/1)

    Not configured.

 AU-3 3, TUG-2 6, T1 2 (C-11 3/6/2)

    Not configured.

 AU-3 3, TUG-2 6, T1 3 (C-11 3/6/3)

    Not configured.

 AU-3 3, TUG-2 6, T1 4 (C-11 3/6/4)

    Not configured.

 AU-3 3, TUG-2 7, T1 1 (C-11 3/7/1)

    Not configured.

 AU-3 3, TUG-2 7, T1 2 (C-11 3/7/2)

    Not configured.

 AU-3 3, TUG-2 7, T1 3 (C-11 3/7/3)

    Not configured.

 AU-3 3, TUG-2 7, T1 4 (C-11 3/7/4)

    Not configured.

For additional examples of the show commands here, see the Cisco IOS Interface and Hardware Component Command Reference.

Troubleshooting

You can use the following commands to verify your configuration:

•show cem circuit—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.

•show cem circuit summary—Displays the number of circuits which are up or down per interface basis.

•show controller sonet slot/bay/port transceiver [status | idprom [brief | detail]]—Displays information about the optical transceiver

•show mpls l2transport vc—Displays the state of local and peer access circuits

•show running configuration—Shows detail on each CEM group

•show xconnect all—Displays the state of the pseudowire and local and peer access circuits

To provide information about system processes, the Cisco IOS software includes an extensive list of EXEC commands that begin with the word show, which, when executed, display detailed tables of system information. .

Configuration Examples

This section includes the following configuration examples:

•Example of Cyclic Redundancy Check Configuration

Example of Cyclic Redundancy Check Configuration

The following example configures CRC on a T1 interface:

! Specify the interface to configure and enter interface configuration mode.

Switch(config)# interface serial 2/0/0.1

! Specify the CRC type.

Switch(config-if)# crc 32

Example of Show Commands Output

The following example show output from show controller sonet port/bay/slot tranceiver status command:

Switch#show controllers sonet 1/0/0 transceiver status

The Transceiver in slot 1 subslot 0 port 0 is enabled.

  Module temperature                        = +43.550 C

  Transceiver Tx supply voltage             = 3304.8 mVolts

  Transceiver Tx bias current               = 5630 uAmps

  Transceiver Tx power                      = -11.8 dBm

  Transceiver Rx optical power              = -23.0 dBm

The following example show output from show controller sonet port/bay/slot tranceiver idprom command:

Switch#show controllers sonet 1/0/0 transceiver idprom brief

IDPROM for transceiver CHOCX_W2_0/0:

  Description                               = SFP or SFP+ optics (type 3)

  Transceiver Type:                         = OC3 IR-1/STM1 S-1.1 (3)

  Product Identifier (PID)                  = SFP-OC3-IR1

  Vendor Revision                           = A

  Serial Number (SN)                        = SPC144905RT

  Vendor Name                               = CISCO-SUMITOMO

  Vendor OUI (IEEE company ID)              = 00.00.5F (95)

  CLEI code                                 = IPUIAC0RAA

  Cisco part number                         = 10-1966-01

  Device State                              = Enabled.

  Date code (yy/mm/dd)                      = 10/12/03

  Connector type                            = LC.

  Encoding                                  = 8B10B

NRZ

                                              Manchester

  Nominal bitrate                           = OC3/STM1 (200 Mbits/s)

  Minimum bit rate as % of nominal bit rate = not specified

  Maximum bit rate as % of nominal bit rate = not specified

Switch#show controllers sonet 1/0/0 transceiver idprom detail

IDPROM for transceiver CHOCX_W2_0/0:

  Description                               = SFP or SFP+ optics (type 3)

  Transceiver Type:                         = OC3 IR-1/STM1 S-1.1 (3)

  Product Identifier (PID)                  = SFP-OC3-IR1

  Vendor Revision                           = A

  Serial Number (SN)                        = SPC144905RT

  Vendor Name                               = CISCO-SUMITOMO

  Vendor OUI (IEEE company ID)              = 00.00.5F (95)

  CLEI code                                 = IPUIAC0RAA

  Cisco part number                         = 10-1966-01

  Device State                              = Enabled.

  Date code (yy/mm/dd)                      = 10/12/03

  Connector type                            = LC.

  Encoding                                  = 8B10B

NRZ

                                              Manchester

  Nominal bitrate                           = OC3/STM1 (200 Mbits/s)

  Minimum bit rate as % of nominal bit rate = not specified

  Maximum bit rate as % of nominal bit rate = not specified

  The transceiver type is 3

  Link reach for 9u fiber (km)              = IR-1(15km) (15)

  Link reach for 50u fiber (m)              = SR(2km) (0)

                                              IR-1(15km) (0)

                                              IR-2(40km) (0)

                                              LR-1(40km) (0)

                                              LR-2(80km) (0)

                                              LR-3(80km) (0)

                                              DX(40KM) (0)

                                              HX(40km) (0)

                                              ZX(80km) (0)

                                              VX(100km) (0)

                                              1xFC, 2xFC-SM(10km) (0)

                                              ESCON-SM(20km) (0)

  Link reach for 62.5u fiber (m)            = SR(2km) (0)

                                              IR-1(15km) (0)

                                              IR-2(40km) (0)

                                              LR-1(40km) (0)

                                              LR-2(80km) (0)

                                              LR-3(80km) (0)

                                              DX(40KM) (0)

                                              HX(40km) (0)

                                              ZX(80km) (0)

                                              VX(100km) (0)

                                              1xFC, 2xFC-SM(10km) (0)

                                              ESCON-SM(20km) (0)

  Nominal laser wavelength                  = 1310 nm.

  DWDM wavelength fraction                  = 1310.0  nm.

  Supported options                         = Tx disable

                                              Tx fault signal

                                              Loss of signal (standard implementation)

  Supported enhanced options                = Alarms for monitored parameters

                                              Software Tx disable

                                              Software Tx fault monitoring

                                              Software Rx LOS monitoring

  Diagnostic monitoring                     = Digital diagnostics supported

                                              Diagnostics are externally calibrated

                                              Rx power measured is "Average power"

  Transceiver temperature operating range   = -5 C to 85 C (extended)

  Minimum operating temperature             = -5 C

  Maximum operating temperature             = 85 C

  High temperature alarm threshold          = +103.000 C

  High temperature warning threshold        = +95.000 C

  Low temperature warning threshold         =  -43.000 C

  Low temperature alarm threshold           =  -43.000 C

  High voltage alarm threshold              = 4000.0 mVolts

  High voltage warning threshold            = 3600.0 mVolts

  Low voltage warning threshold             = 3000.0 mVolts

  Low voltage alarm threshold               = 0.0 mVolts

  High laser bias current alarm threshold   = 70.000 mAmps

  High laser bias current warning threshold = 60.000 mAmps

  Low laser bias current warning threshold  = 0.000 mAmps

  Low laser bias current alarm threshold    = 0.000 mAmps

  High transmit power alarm threshold       = -5.0 dBm

  High transmit power warning threshold     = -7.0 dBm

  Low transmit power warning threshold      = -16.0 dBm

  Low transmit power alarm threshold        = -18.0 dBm

  High receive power alarm threshold        =  8.0 dBm

  High receive power warning threshold      =  8.0 dBm

  Low receive power warning threshold       = -40.0 dBm

  Low receive power alarm threshold         = -40.0 dBm

  External Calibration: bias current slope  = 1.000

  External Calibration: bias current offset = 0

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)

Results

Chapter: Configuring OC3 Ports

Configuring OC3 Ports

Limitations and Restrictions

Configuring the OC-3 Ports

Configuring the Controller

Configuring SDH

Configuring SDH Mode

Optional Configurations

Configuring the Encapsulation Method

Configuring the CRC Size for T1

Configuring Keepalive Value

Configuring MTU Value

Managing Interface Naming

Identifying Slots and Subslot

Naming Interfaces

Configuring BERT

Running Bit Error Rate Testing

Example:

Configuring Circuit Emulation

Configuring a CEM Group

SUMMARY STEPS

Using CEM Classes

SUMMARY STEPS

Configuration Examples for CEM:

Configuring CEM Parameters

Configuring Payload Size (Optional)

Setting the Dejitter Buffer Size

Shutting Down a CEM Channel

Configuring Loopbacks

Setting a Loopback on the Controller

Setting a Loopback at the PDH Level

Configuration Examples

Verifying Interface Configuration

Verifying Per-Port Interface Status

Troubleshooting

Configuration Examples

Example of Cyclic Redundancy Check Configuration

Example of Show Commands Output

Was this Document Helpful?

Contact Cisco

Related Support Community Discussions

Share