Required Configuration Tasks

This section lists the required configuration steps to configure the 2-Port and 4-Port Channelized T3 SPA. Some of the required configuration commands implement default values that might be appropriate for your network.

channel-number—Specifies a channel-group mapping(0–23) under the designated T1.

range—List of timeslots under the channel-group. Timeslots assigned to this T1 can be 1–24 or a combination of subranges within 1– 24. You can indicate a range using a hyphen, commas, or a combination of both. One timeslot equals one DS0.

speed 56 or 64— Specifies the speed of a timeslot as either 56 or 64 kbps. The default speed of 64 kbps is not mentioned in the config.

internal—Specifies that the internal clock source is used. This is the default.

line—Specifies that the network clock source is used.

Step 6

Configure the serial interfaces.

Note After a T1 channel is configured, it appears to the Cisco IOS software as a serial interface; therefore, all the configuration commands for a serial interface are available. However, not all commands are applicable to the T1 interface. All the encapsulation formats, such as PPP, HDLC, and Frame Relay are applicable to the configured T1. Encapsulation can be set via the serial interface configuration commands.

Verifying T3 Controller Configuration

Use the show controllers command to verify the controller configuration:

Router# show controllers t3

T3 3/1/0 is administratively down.

T3 3/1/1 is administratively down.

T3 3/1/2 is up. Hardware is 4 ports CT3 SPA

ATLAS FPGA version: 0, FREEDM336 version: 0

TEMUX84(1) version: 0, TEMUX84(1) version: 0

SUBRATE FPGA version: 0

Applique type is Channelized T3

No alarms detected.

Framing is M23, Line Code is B3ZS, Clock Source is Internal

Equipment customer loopback

Data in current interval (746 seconds elapsed):

0 Line Code Violations, 0 P-bit Coding Violation

0 C-bit Coding Violation, 0 P-bit Err Secs

0 P-bit Severely Err Secs, 0 Severely Err Framing Secs

0 Unavailable Secs, 0 Line Errored Secs

0 C-bit Errored Secs, 0 C-bit Severely Errored Secs

0 Severely Errored Line Secs

0 Far-End Errored Secs, 0 Far-End Severely Errored Secs

0 CP-bit Far-end Unavailable Secs

0 Near-end path failures, 0 Far-end path failures

0 Far-end code violations, 0 FERF Defect Secs

0 AIS Defect Secs, 0 LOS Defect Secs

T1 1 is up

timeslots: 1-24

FDL per AT&T 54016 spec.

No alarms detected.

Framing is ESF, Clock Source is Internal

Data in current interval (177 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

0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs

Total Data (last 2 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

0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs

T1 2

Not configured.

T1 3

Not configured.

.

.

.

T3 3/1/3 is up. Hardware is 4 ports CT3 SPA

ATLAS FPGA version: 0, FREEDM336 version: 0

TEMUX84(1) version: 0, TEMUX84(1) version: 0

SUBRATE FPGA version: 0

Applique type is Subrate T3

No alarms detected.

MDL transmission is disabled

FEAC code received: No code is being received

Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Line

Equipment customer loopback

Data in current interval (657 seconds elapsed):

0 Line Code Violations, 0 P-bit Coding Violation

0 C-bit Coding Violation, 0 P-bit Err Secs

0 P-bit Severely Err Secs, 0 Severely Err Framing Secs

0 Unavailable Secs, 0 Line Errored Secs

0 C-bit Errored Secs, 0 C-bit Severely Errored Secs

0 Severely Errored Line Secs

0 Far-End Errored Secs, 0 Far-End Severely Errored Secs

0 CP-bit Far-end Unavailable Secs

0 Near-end path failures, 0 Far-end path failures

0 Far-end code violations, 0 FERF Defect Secs

0 AIS Defect Secs, 0 LOS Defect Secs

Verifying Interface Configuration

Use the show interface serial command to verify the interface configuration. The following example shows the ouput for the serial interface for an un-channelized T3:

Router# show interface serial3/0/0

Serial3/0/0 is down, line protocol is down

Hardware is Channelized/ClearChannel CT3 SPA

MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec,

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

Encapsulation HDLC, crc 16, loopback not set

Keepalive set (10 sec)

Last input never, output never, 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

0 packets input, 0 bytes, 0 no buffer

Received 0 broadcasts (0 IP multicast)

0 runts, 0 giants, 0 throttles

0 parity

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

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 applique, 2 interface resets

0 output buffer failures, 0 output buffers swapped out

1 carrier transitions alarm present

DSU mode 0, bandwidth 44210 Kbit, scramble 0, VC 0

The following example shows the output for a serial interface for the first T1 on a channelized T3:

Router# show interface serial3/0/1/1:0

Serial3/0/1/1:0 is administratively down, line protocol is down

Hardware is Channelized/ClearChannel CT3 SPA

MTU 1500 bytes, BW 832 Kbit, 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 never, output never, 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

0 packets input, 0 bytes, 0 no buffer

Received 0 broadcasts (0 IP multicast)

0 runts, 0 giants, 0 throttles

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

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 collisions, 1 interface resets

0 output buffer failures, 0 output buffers swapped out

0 carrier transitions alarm present

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

Specifying the Interface Address on a SPA

SPA interface ports begin numbering with “0” from left to right. Single-port SPAs use only the port number 0. To configure or monitor SPA interfaces, you need to specify the physical location of the SIP, SPA, and interface in the CLI. The interface address format is slot / subslot / port , where:

slot —Specifies the chassis slot number in the Cisco 7600 series router where the SIP is installed.

subslot —Specifies the secondary slot of the SIP where the SPA is installed.

port —Specifies the number of the individual interface port on a SPA.

The following example shows how to specify the first interface (0) on a SPA installed in the first subslot of a SIP (0) installed in chassis slot 3:

Router(config)# interface serial 3/0/0

This command shows a serial SPA as a representative example, however the same slot / subslot / port format is similarly used for other SPAs (such as ATM and POS) and other non-channelized SPAs.

Configuring the Data Service Unit Mode

Configure the SPA to connect with customer premise Data Service Units (DSUs) by setting the DSU mode. Subrating a T3 or E3 interface reduces the peak access rate by limiting the data transfer rate. To configure the Data Service Unit (DSU) mode, use the following commands.

z

Command

Purpose

Step 1

Router# configure terminal

Enters global configuration mode.

Step 2

Router(config)# interface serial slot/subslot/port

Selects the controller to configure and enters controller configuration mode.

Configuring FDL

Facility Data Link (FDL) is a far-end performance reporting tool. In ansi mode, you can enable 1-second transmissions of performance reports on both ends of the T1 connection. To configure FDL, use the following commands:

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# controller t3 slot/subslot/port

Selects the controller to configure and enters controller configuration mode.

Configuring Scramble

T3 scrambling is used to assist clock recovery on the receiving end. Scrambling is designed to randomize the pattern of 1s and 0s carried in the physical layer frame. Randomizing the digital bits can prevent continuous, nonvariable bit patterns—in other words, long strings of all 1s or all 0s. Several physical layer protocols rely on transitions between 1s and 0s to maintain clocking.

Scrambling can prevent some bit patterns from being mistakenly interpreted as alarms by switches placed between the Data Service Units (DSUs).

To configure scrambling, use the following commands:

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface serial slot/subslot/port

Selects the interface to configure and enters interface configuration mode.

Verifying Scrambling

Use the show interface serial command to display the scramble setting:

Router# show interface serial3/0/0

Serial3/0/0 is down, line protocol is down

Hardware is Channelized/ClearChannel CT3 SPA

MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec,

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

Encapsulation HDLC, crc 16, loopback not set

Keepalive set (10 sec)

Last input never, output never, 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

0 packets input, 0 bytes, 0 no buffer

Received 0 broadcasts (0 IP multicast)

0 runts, 0 giants, 0 throttles

0 parity

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

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 applique, 4 interface resets

0 output buffer failures, 0 output buffers swapped out

1 carrier transitions alarm present

DSU mode 0, bandwidth 44210 Kbit, scramble 1, VC 0

Configuring Multilink Point-to-Point Protocol (Hardware-based)

Multilink Point to Point Protocol (MLPPP) allows you to combine T1 or E1 lines into a bundle that has the combined bandwidth of multiple T1/E1 lines. You choose the number of bundles and the number of T1 or E1 lines in each bundle.

MLPPP for T1/E1 Configuration Guidelines

The required conditions are:

Only T1 or E1 links in a bundle

All links on the same SPA

Maximum of 12 links in a bundle.

NoteSome notes about hardware-based MLPPP:

Only 3 fragmentation sizes are possible 128, 256 and 512 bytes

Fragmentation is enabled by default, default size is 512 bytes

Fragmentation size is configured using the ppp multilink fragment-delay command after using the interface multilink command. The least of the fragmentation sizes (among the 3 sizes possible) satisfying the delay criteria is configured. (e.g., a 192 byte packet causes a delay of 1 millisecond on a T1 link, so the nearest fragmentation size is 128 bytes.

The show ppp multilink commandwill indicate the mlppp type and the fragmentation size:Router# show ppp multilinkMultilink1, bundle name is Patriot2Bundle up for 00:00:13Bundle is Distributed0 lost fragments, 0 reordered, 0 unassigned0 discarded, 0 lost received, 206/255 load0x0 received sequence, 0x0 sent sequence Member links: 2 active, 0 inactive (max not set, min not set)Se4/2/0/1:0, since 00:00:13, no frags rcvdSe4/2/0/2:0, since 00:00:10, no frags rcvdDistributed fragmentation on. Fragment size 512. Multilink in Hardware.

Fragmentation is disabled explicitly by using the no ppp multilink fragmentation command after using the interface multilink command.

Create a Multilink Bundle

To create a multilink bundle, use the following commands:

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface multilink group-number

Creates a multilink interface and enter multilink interface mode.

group-number—The group number for the multilink bundle.

Router(config-if)# ip address address mask

Sets the IP address for the multilink group.

address—The IP address.

mask—The IP netmask.

Assign an interface to a Multilink Bundle

To assign an interface to a multilink bundle, use the following commands:

group-number—The group number for the multilink bundle. Range 1-2147483647

Router(config-if)# ppp multilink fragment-delay delay

Sets the fragmentation size satisfying the configured delay on the multilink bundle.

delay—delay in milliseconds

Disabling the fragmentation on an MLPPP Bundle (optional)

To assign an interface to a multilink bundle, use the following commands:

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface multilink group-number

Creates a multilink interface and enters multilink interface mode.

group-number—The group number for the multilink bundle. Range 1-2147483647

Router(config-if)# no ppp multilink fragmentation

Disables the fragmentation on the multilink bundle.

Verifying Multilink PPP

Use the show ppp multilink command to verify the PPP multilinks:

router# show ppp multilink

Multilink1, bundle name is mybundle

Bundle up for 01:40:50

Bundle is Distributed

0 lost fragments, 0 reordered, 0 unassigned

0 discarded, 0 lost received, 1/255 load

0x0 received sequence, 0x0 sent sequence

Member links: 5 active, 0 inactive (max not set, min not set)

Se6/0/0/1:0, since 01:40:50, no frags rcvd

Se6/0/1/1:0, since 01:40:09, no frags rcvd

Se6/0/3/1:0, since 01:15:44, no frags rcvd

Se6/0/4/1:0, since 01:03:17, no frags rcvd

Se6/0/6/1:0, since 01:01:06, no frags rcvd

Se6/0/6:0, since 01:01:06, no frags rcvd

.Configuring MLFR for T1/E1

Multilink Frame Relay (MLFR) allows you to combine T1/E1 lines into a bundle that has the combined bandwidth of multiple T1/E1 lines. You choose the number of bundles and the number of T1/E1 lines in each bundle. This allows you to increase the bandwidth of your network links beyond that of a single T1/E1 line.

MLFR for T1/E1 Configuration Guidelines

MLFR will function in hardware if all of the following conditions are met:

Only T1 or E1 member links

All links are on the same SPA

Maximum of 12 links in a bundle

Create a Multilink Bundle

To create a multilink bundle, use the following commands:

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface mfr number

Configures a multilink Frame Relay bundle interface.

number—The number for the Frame Relay bundle.

Router(config-if)# frame-relay multilink bid name

(Optional) Assigns a bundle identification name to a multilink Frame Relay bundle.

name—The name for the Frame Relay bundle.

Note The bundle identification (BID) will not go into effect until the interface has gone from the down state to the up state. One way to bring the interface down and back up again is by using the shut and no shut commands in interface configuration mode.

Assign an Interface to a Multilink Bundle

To assign an interface to a multilink bundle, use the following commands:

Note The bundle link identification (LID) will not go into effect until the interface has gone from the down state to the up state. One way to bring the interface down and back up again is by using the shut and no shut commands in interface configuration mode.

Router(config-if)# frame-relay multilink hello seconds

(Optional) Configures the interval at which a bundle link will send out hello messages. The default value is 10 seconds.

seconds—Number of seconds between hello messages sent out over the multilink bundle.

Router(config-if)# frame-relay multilink ack seconds

(Optional) Configures the number of seconds that a bundle link will wait for a hello message acknowledgment before resending the hello message. The default value is 4 seconds.

seconds—Number of seconds a bundle link will wait for a hello message acknowledgment before resending the hello message.

Router(config-if)# frame-relay multilink retry number

(Optional) Configures the maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment. The default value is 2 tries.

number—Maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment.

Verifying Multilink Frame Relay

Use the show frame-relay multilink detailed command to verify the Frame Relay multilinks:

Router# show frame-relay multilink detailed

Bundle: MFR49, State = down, class = A, fragmentation disabled

BID = MFR49

No. of bundle links = 1, Peer's bundle-id =

Bundle links:

Serial6/0/0:0, HW state = up, link state = Add_sent, LID = test

Cause code = none, Ack timer = 4, Hello timer = 10,

Max retry count = 2, Current count = 0,

Peer LID = , RTT = 0 ms

Statistics:

Add_link sent = 21, Add_link rcv'd = 0,

Add_link ack sent = 0, Add_link ack rcv'd = 0,

Add_link rej sent = 0, Add_link rej rcv'd = 0,

Remove_link sent = 0, Remove_link rcv'd = 0,

Remove_link_ack sent = 0, Remove_link_ack rcv'd = 0,

Hello sent = 0, Hello rcv'd = 0,

Hello_ack sent = 0, Hello_ack rcv'd = 0,

outgoing pak dropped = 0, incoming pak dropped = 0

Configuring Multipoint Bridging

Multipoint bridging (MPB) enables the connection of multiple ATM PVCs, Frame Relay PVCs, BCP ports, and WAN Gigabit Ethernet subinterfaces into a single broadcast domain (virtual LAN), together with the LAN ports on that VLAN. This enables service providers to add support for Ethernet-based Layer 2 services to the proven technology of their existing ATM and Frame Relay legacy networks. Customers can then use their current VLAN-based networks over the ATM or Frame Relay cloud. This also allows service providers to gradually update their core networks to the latest Gigabit Ethernet optical technologies, while still supporting their existing customer base.

Configuring Bridging Control Protocol Support

The Bridging Control Protocol (BCP) enables forwarding of Ethernet frames over SONET networks and provides a high-speed extension of enterprise LAN backbone traffic through a metropolitan area. The implementation of BCP on the SPAs includes support for IEEE 802.1D, IEEE 802.1Q Virtual LAN (VLAN), and high-speed switched LANs.

Configuring BCP on MLPPP

Only channelized interfaces allowed, and member links must be from the same controller card

Only trunk port BCP is supported on MLPPP

Bridging can be configured only on the bundle interface

NoteBCP on MLPPP operates only in trunk mode.

NoteWhen you manually configure the MTU and MRRU values on the bundle interface with BCP on dMLPPP, you should set the MRRU value to atleast 20 bytes more than the MTU value. This configuration ensures that the packets wth size up to the configured MTU value on the multilink interface are not dropped because of the MRRU restrictions.

Configuring BCP on MLPPP Trunk Mode

To configure BCP on MLPPP trunk mode, perform these steps:

Command

Purpose

Step 1

Router(config)# interface multilink

Selects the multilink interface.

Step 2

Router(config-if)# switchport

Puts an interface that is in Layer 3 mode into Layer 2 mode for Layer 2 configuration.

Step 3

Router(config-if)# switchport trunk allowed vlan 100

By default, no VLANs are allowed. Use this command to explicitly allow VLANs; valid values for vlan-list are from 1 to 4094.

Step 4

Router(config-if)# switchport mode trunk

Configures the router port connected to the switch as a VLAN trunk port.

Step 5

Router(config-if)# switchport nonegotiate

Puts the LAN port into permanent trunking mode but prevents the port from generating DTP frames

Step 6

Router(config-if)# no ip address

Step 7

Router(config-if)# ppp multilink

Enables this interface to support MLP.

Step 8

Router(config-if)# multilink-group 1

Assigns this interface to the multilink group.

Step 9

Router(config-if)# interface Serial1/0/0.1/1/1/1:0

Designates a serial interface as a multilink bundle.

Step 10

Router(config-if)# no ip address

Unassigns the IP address.

Step 11

Router(config-if)# encapsulation ppp

Enables PPP encapsulation.

Step 12

Router(config-if)# ppp multilink

Enables this interface to support MLP.

Step 13

Router(config-if)# multilink-group 1

Assigns this interface to the multilink group 1.

Step 14

Router(config-if)# interface Serial1/0/0.1/1/1/2:0

Designates a serial interface as a multilink bundle.

Step 15

Router(config-if)# no ip address

Unassigns the IP address.

Step 16

Router(config-if)# encapsulation ppp

Enables PPP encapsulation.

Step 17

Router(config-if)# ppp multilink

Enables this interface to support MLP.

Step 18

Router(config-if)# multilink-group 1

Assigns this interface to the multilink group 2.

Step 19

Router(config-if)# shutdown

Shuts down an interface.

Step 20

Router(config-if)# no shutdown

Reopens an interface.

Step 21

Router(config-if)# switchport trunk allowed vlan vlan-list

By default, no VLANs are allowed. Use this command to explicitly allow VLANs; valid values for vlan-list are from 1 to 4094.

Verifying BCP on MLPPP Trunk Mode

To display information about Multilink PPP, use the show ppp multilink command in EXEC mode.

FRF.12 Guidelines

Only 3 fragmentation sizes are available - 128 bytes, 256 bytes, and 512 bytes. The supported fragment sizes - 128, 256 and 512 - include the FRF and NLPID headers in addition to the payload.

If you have a configuration where a C7600 router acts as a Provider Edge(PE) router between Customer Edge(CE) routers, you can configure C7600 in plain Frame Relay or Frame Relay Fragmentation mode. If you enable Frame Relay Fragmentation only at the CE routers and C7600 acts as a plain Frame Relay interface, the configuration works fine. In a configuration of C7600 with any of the three SPAs(8-Port Channelized T1/E1 SPA,1-Port Channelized OC-3/STM-1 SPA or 2 or 4-Port CT3 SPA), where Frame Relay is configured on the serial interface and Frame Relay Fragmentation is enabled in any of the sub interfaces, the fragmented packets may be dropped in the transparant DLCIs. If you want such a configuration to work, you should set the fragment size value on the main interface larger than any CE router fragmentation size usingthe command frame-relay fragment x end-to-end , where x is the fragmentation size on the main interface.

LFI Guidelines

LFI can function two ways - using FRF.12 or MLPPP. MLPPP LFI can be done in both hardware and software while FRF.12 LFI is done only in hardware.

Hardware MLPPP LFI Guidelines

LFI using MLPPP will function only in hardware if there is just one member link in the MLPPP bundle. The link can be a fractional T1 or full T1. Note the following:

The ppp multilink interleave command needs to be configured to enable interleaving.

Verifying the Interface Configuration

Besides using the show running-configuration command to display your Cisco 7600 series router configuration settings, you can use the show interfaces serial and the show controllers serial commands to get detailed information on a per-port basis for your 2-Port and 4-Port Clear Channel T3/E3 SPA.

Verifying Per-Port Interface Status

To find detailed interface information on a per-port basis for the 2-Port and 4-Port Channelized T3 SPA, use the show interfaces serial command.

The following example provides sample output for the serial interface on an un-channelized T3:

Router# show interface serial3/0/0

Serial3/0/0 is down, line protocol is down

Hardware is Channelized/ClearChannel CT3 SPA

MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec,

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

Encapsulation HDLC, crc 16, loopback not set

Keepalive set (10 sec)

Last input never, output never, 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

0 packets input, 0 bytes, 0 no buffer

Received 0 broadcasts (0 IP multicast)

0 runts, 0 giants, 0 throttles

0 parity

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

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 applique, 4 interface resets

0 output buffer failures, 0 output buffers swapped out

1 carrier transitions alarm present

DSU mode 0, bandwidth 44210 Kbit, scramble 1, VC 0

The following example provides sample output for the serial interface on a channelized T3:

Router# show interface serial3/0/1/1:0

Serial3/0/1/1:0 is down, line protocol is down

Hardware is Channelized/ClearChannel CT3 SPA

MTU 1500 bytes, BW 832 Kbit, 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 never, output never, 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

0 packets input, 0 bytes, 0 no buffer

Received 0 broadcasts (0 IP multicast)

0 runts, 0 giants, 0 throttles

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

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 output buffer failures, 0 output buffers swapped out

0 carrier transitions alarm present

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

To find detailed status and statistical information on a per-port basis for the 2-Port and 4-Port Clear Channel T3/E3 SPA, use the show controllers serial command.

The following example provides sample controller statistics for the third port on the SPA located in the first subslot of the SIP-200 that is installed in slot 5 of a Cisco 7609 router: