Feedback
Table Of Contents
Configuring the 8-Port Channelized T1/E1 SPA
Specifying the Interface Address on a SPA
Verifying the Interface Configuration
Verifying Per-Port Interface Status
Framing and Encapsulation Configuration Example
Facility Data Link Configuration Example
Invert Data on the T1/E1 Interface Example
Configuring the 8-Port Channelized T1/E1 SPA
This chapter provides information about configuring the 8-Port Channelized T1/E1 SPA on the Cisco 7600 series router. It includes the following sections:
•
Verifying the Interface Configuration
For information about managing your system images and configuration files, refer to the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2 and Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 publications.
For more information about the commands used in this chapter, see Chapter 40, "SIP, SSC, and SPA Commands," which documents new and modified commands, and then any related Cisco 7600 Series Router Command Reference publication for your release. Also refer to the related Cisco IOS Release 12.2 software command reference and master index publications. For more information about accessing these publications, see the "Related Documentation" section on page xlviii .
Configuration Tasks
This section describes how to configure the 8-Port Channelized T1/E1 SPA for the Cisco 7600 series router and includes information about verifying the configuration.
It includes the following topics:
•
•
Required Configuration Tasks
This section lists the required configuration steps to configure the 8-Port Channelized T1/E1 SPA. Some of the required configuration commands implement default values that might be appropriate for your network. If the default value is correct for your network, then you do not need to configure the command.
•
•
•
Note
Setting the Card Type
The SPA is not functional until the card type is set. Information about the SPA is not indicated in the output of any show commands until the card type has been set. There is no default card type.
Note
To set the card type for the 8-Port Channelized T1/E1 SPA, complete these steps:
Step 1
Router# configure terminal
Enters global configuration mode.
Step 2
Router(config)# card type {e1 | t1} slot subslot
Sets the serial mode for the SPA:
•
•
•
Step 3
Router(config)# exit
Exits configuration mode and returns to the EXEC command interpreter prompt.
Enabling the Interfaces on the Controller
To create the interfaces for the 8-Port Channelized T1/E1 SPA, complete these steps:
Step 1
Router(config)# controller {t1 | e1} slot/subslot/port
Select the controller to configure and enter controller configuration mode.
•
•
•
Step 2
Router(config-controller)# clock source {internal | line}
Sets the clock source.
Note
•
•
Step 3
Router(config-controller)# linecode {ami | b8zs | hdb3}
Selects the linecode type.
•
•
•
Step 4
For T1 controllers
Router(config-controller)# framing {sf | esf}
For E1 controllers
Router(config-controller)# framing {crc4 | no-crc4}
Selects the framing type.
•
•
•
•
Step 5
Router(config-controller)# channel-group t1 t1-number {timeslots range | unframed} [speed {56 | 64}]
Define the time slots that belong to each T1 or E1 circuit.
•
•
•
•
–
–
Note
Note
Note
Step 6
Router(config)# exit
Exits configuration mode and returns to the EXEC command interpreter prompt.
Verifying Controller Configuration
Use the show controllers command to verify the controller configuration:
Router(config)# show controllers t1T1 6/0/1 is up.Applique type is Channelized T1Cablelength is long gain36 0dbNo alarms detected.alarm-trigger is not setFraming is ESF, Line Code is B8ZS, Clock Source is Line.Data in current interval (395 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsTotal Data (last 24 hours)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 SecsSetting the IP Address
To set the IP address for the 8-Port Channelized T1/E1 SPA, complete these steps:
Step 1
Router(config)# interface serial slot/subslot/port:channel-group
Selects the interface to configure from global configuration mode.
•
Step 2
Router(config-if)# ip address address mask
Sets the IP address and subnet mask.
•
•
Step 3
Router(config)# exit
Exits configuration mode and returns to the EXEC command interpreter prompt.
Verifying Interface Configuration
Use the show interfaces command to verify the interface configuration:
Router(config)# show interfaces...Serial6/0/1:0 is up, line protocol is upHardware is SPA-T1E1MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation PPP, crc 16, loopback not setKeepalive set (10 sec)LCP Open, multilink OpenLast input 00:00:03, output 00:00:03, output hang neverLast clearing of "show interface" counters 5d17hInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 3194905708Queueing strategy: fifoOutput queue: 0/40 (size/max)30 second input rate 0 bits/sec, 0 packets/sec30 second output rate 0 bits/sec, 0 packets/sec74223 packets input, 1187584 bytes, 0 no bufferReceived 0 broadcasts (0 IP multicast)0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort74227 packets output, 1187751 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets0 output buffer failures, 0 output buffers swapped out4 carrier transitions no alarm presentTimeslot(s) Used:1-24, subrate: 64Kb/s, transmit delay is 0 flags..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:
•
•
•
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/0This 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.
For the 8-Port Channelized T1/E1 SPA, the interface address format is slot/subslot/port:channel-group, where:
•
For more information about identifying slots and subslots, see the "Identifying Slots and Subslots for SIPs, SSCs, and SPAs" section on page 4-2.
Optional Configurations
There are several standard, but optional, configurations that might be necessary to complete the configuration of your serial SPA.
Note
•
•
•
•
•
•
•
•
Configuring Framing
Framing is used to synchronize data transmission on the line. Framing allows the hardware to determine when each packet starts and ends. To configure framing, use the following commands.
Router# configure terminal
Enters global configuration mode.
Router(config)# controller {t1 | e1} slot/subslot/port
Selects the controller to configure.
•
•
•
For T1 controllers
Router(config-controller)# framing {sf | esf}
For E1 controllers
Router(config-controller)# framing {crc4 | no-crc4}
Set the framing on the interface.
•
•
•
•
Verifying Framing Configuration
Use the show controllers command to verify the framing configuration:
Router# show controllers t1T1 6/0/0 is down.Applique type is Channelized T1Cablelength is long gain36 0dbReceiver has loss of frame.alarm-trigger is not setFraming is ESF, Line Code is B8ZS, Clock Source is Line.Data in current interval (717 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 717 Unavail SecsTotal Data (last 24 hours)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, 86400 Unavail SecsConfiguring Encapsulation
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:
Router# configure terminal
Enters global configuration mode.
Router(config)# interface serial slot/subslot/port:channel-group
Selects the interface to configure.
•
Router(config-if)# encapsulation encapsulation-type {hdlc | ppp | frame-relay}
Set the encapsulation method on the interface.
•
•
•
Verifying Encapsulation
Use the show interfaces serial command to verify encapsulation on the interface:
Router# show interfaces serial 6/0/0:0Serial6/0/0:0 is down, line protocol is downHardware is SPA-T1E1MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation PPP, crc 32, loopback not setKeepalive set (10 sec)LCP Closed, multilink ClosedLast input 1w0d, output 1w0d, output hang neverLast clearing of "show interface" counters 6d23hInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: weighted fairOutput queue: 0/1000/64/0 (size/max total/threshold/drops)Conversations 0/0/256 (active/max active/max total)Reserved Conversations 0/0 (allocated/max allocated)Available Bandwidth 1152 kilobits/sec30 second input rate 0 bits/sec, 0 packets/sec30 second output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts (0 IP multicast)0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitions alarm presentTimeslot(s) Used:1-24, subrate: 64Kb/s, transmit delay is 0 flagsConfiguring the CRC Size for T1
All 8-Port Channelized T1/E1 SPA interfaces use a 16-bit cyclic redundancy check (CRC) by default, but also support a 32-bit CRC. CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. 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.
CRC-16, the most widely used CRC throughout the United States and Europe, is used extensively with WANs. CRC-32 is specified by IEEE 802 and as an option by some point-to-point transmission standards. It is often used on Switched Multimegabit Data Service (SMDS) networks and LANs.
To set the length of the cyclic redundancy check (CRC) on a T1 interface, use these commands:
Router# configure terminal
Enters global configuration mode.
Router(config)# interface serial slot/subslot/port:channel-group
Selects the interface to configure.
•
Router(config-if)# crc {16 | 32}
Selects the CRC size in bits.
•
•
Verifying the CRC Size
Use the show interfaces serial command to verify the CRC size set on the interface:
Router# show interfaces serial 6/0/0:0Serial6/0/0:0 is up, line protocol is upHardware is SPA-T1E1MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation PPP, crc 32, loopback not setKeepalive set (10 sec)LCP Open, multilink OpenLast input 00:00:38, output 00:00:00, output hang neverLast clearing of "show interface" counters 01:46:16Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)30 second input rate 0 bits/sec, 0 packets/sec30 second output rate 0 bits/sec, 0 packets/sec1272 packets input, 20396 bytes, 0 no bufferReceived 0 broadcasts (0 IP multicast)0 runts, 0 giants, 0 throttles6 input errors, 3 CRC, 0 frame, 0 overrun, 0 ignored, 3 abort1276 packets output, 20460 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitions no alarm presentTimeslot(s) Used:1-24, subrate: 64Kb/s, transmit delay is 0 flagsConfiguring FDL
Facility Data Link (FDL) is a 4-kbps channel provided by the Extended Super Frame (ESF) T1 framing format. The FDL performs outside the payload capacity and allows you to check error statistics on terminating equipment without intrusion.
Router# configure terminal
Enters global configuration mode.
Router(config)# controller t1 slot/subslot/port
Selects the controller to configure.
•
Router(config-controller)# fdl [ansi | att | both]
If the framing format was configured for esf, configures the format used for Facility Data Link (FDL).
•
•
•
Verifying FDL
Use the show controllers t1 command to verify the fdl setting:
Router# show controllers t1
T1 6/0/1 is up.Applique type is Channelized T1Cablelength is long gain36 0dbNo alarms detected.alarm-trigger is not setFraming is ESF, FDL is ansi, Line Code is B8ZS, Clock Source is Line.Data in current interval (742 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsTotal Data (last 73 15 minute intervals):1278491 Line Code Violations, 3 Path Code Violations,0 Slip Secs, 1 Fr Loss Secs, 177 Line Err Secs, 0 Degraded Mins,3 Errored Secs, 0 Bursty Err Secs, 1 Severely Err Secs, 227 Unavail Secs...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:
•
•
•
Note
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. (For example, 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 command indicates the MLPPP type and the fragmentation size:
Router# show ppp multilink
Multilink1, bundle name is Patriot2
Bundle up for 00:00:13
Bundle is Distributed
0 lost fragments, 0 reordered, 0 unassigned
0 discarded, 0 lost received, 206/255 load
0x0 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 rcvd
Se4/2/0/2:0, since 00:00:10, no frags rcvd
Distributed 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:
Assign an interface to a Multilink Bundle
To assign an interface to a multilink bundle, use the following commands:
Router# configure terminal
Enters global configuration mode.
Router(config)# interface serial slot/subslot/port/t1-number:channel-group
Selects the interface to configure and enters interface configuration mode. See the "Specifying the Interface Address on a SPA" section.
•
Router(config-if)# encapsulation ppp
Enables PPP encapsulation.
Router(config-if)# multilink-group group-number
Assigns the interface to a multilink bundle.
•
Router(config-if)# ppp multilink
Enables multilink PPP on the interface.
Repeat these commands for each interface you want to assign to the multilink bundle.
Configuring fragmentation size on an MLPPP Bundle (optional)
To configure the fragmentation size on a multilink PPP bundle, use the following commands:
Disabling the fragmentation on an MLPPP Bundle (optional)
To assign an interface to a multilink bundle, use the following commands:
Verifying Multilink PPP
Use the show ppp multilink command to verify the PPP multilinks:
Router# show ppp multilinkMultilink1, bundle name is mybundleBundle up for 01:40:50Bundle is Distributed0 lost fragments, 0 reordered, 0 unassigned0 discarded, 0 lost received, 1/255 load0x0 received sequence, 0x0 sent sequenceMember links: 5 active, 0 inactive (max not set, min not set)Se6/0/0/1:0, since 01:40:50, no frags rcvdSe6/0/1/1:0, since 01:40:09, no frags rcvdSe6/0/3/1:0, since 01:15:44, no frags rcvdSe6/0/4/1:0, since 01:03:17, no frags rcvdSe6/0/6/1:0, since 01:01:06, no frags rcvdSe6/0/6:0, since 01:01:06, no frags rcvdConfiguring 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:
•
•
•
Create a Multilink Bundle
To create a multilink bundle, use the following commands:
Assign an Interface to a Multilink Bundle
To assign an interface to a multilink bundle, use the following commands:
Router# configure terminal
Enters global configuration mode.
Router(config)# interface serial slot/subslot/port:channel-group
Selects the interface to assign.
•
Router(config-if)# encapsulation frame-relay mfr number [name]
Creates a multilink Frame Relay bundle link and associates the link with a bundle.
•
•
Router(config-if)# frame-relay multilink lid name
(Optional) Assigns a bundle link identification name with a multilink Frame Relay bundle link.
•
Note
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.
•
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.
•
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.
•
Verifying Multilink Frame Relay
Use the show frame-relay multilink detailed command to verify the Frame Relay multilinks:
router# show frame-relay multilink detailedBundle: MFR49, State = down, class = A, fragmentation disabledBID = MFR49No. of bundle links = 1, Peer's bundle-id =Bundle links:Serial6/0/0:0, HW state = up, link state = Add_sent, LID = testCause code = none, Ack timer = 4, Hello timer = 10,Max retry count = 2, Current count = 0,Peer LID = , RTT = 0 msStatistics: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 = 0Invert Data on the T1/E1 Interface
If the interface on the 8-Port Channelized T1/E1 SPA is used to drive a dedicated T1 line that does not have B8ZS encoding, you must invert the data stream on the connecting CSU/DSU or on the interface. Be careful not to invert data on both the CSU/DSU and the interface, as two data inversions will cancel each other out. To invert data on a T1/E1 interface, use the following commands:
Use the show running configuration command to verify that invert data has been set:Router# show running configuration...interface Serial6/0/0:0no ip addressencapsulation ppplogging event link-statusload-interval 30invert datano cdp enableppp chap hostname group1ppp multilinkmultilink-group 1!...Changing a Channel Group Configuration
To alter the configuration of an existing channel group, the channel group needs to be removed first. To remove an existing channel group, use the following commands:
Router# configure terminal
Enters global configuration mode.
Router(config)# controller {t1 | e1} slot/subslot/port
Select the controller to configure and enter controller configuration mode.
•
Router(config-controller)# no channel-group t1 t1-number
Select the channel group you want to remove.
•
Follow the steps in the section: Enabling the Interfaces on the Controller.
Create a new channel group with the new configuration.
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.
For MPB configuration guidelines and restrictions and feature compatibility tables, see the "Configuring Multipoint Bridging" section on page 4-23.
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.
For BCP configuration guidelines and restrictions and feature compatibility tables, see the "Configuring PPP Bridging Control Protocol Support" section on page 4-35.
Configuring BCP on MLPPP
BCP on MLPPP Configuration Guidelines
•
•
•
•
Note
Configuring BCP on MLPPP Trunk Mode
To configure BCP on MLPPP trunk mode, perform these steps:
Verifying BCP on MLPPP Trunk Mode
To display information about Multilink PPP, use the show ppp multilink command in EXEC mode.
The following shows an example of show ppp multilink:
Router# show ppp multilinkMultilink1, bundle name is group 1Bundle is Distributed0 lost fragments, 0 reordered, 0 unassigned, sequence 0x0/0x0 rcvd/sent0 discarded, 0 lost received, 1/255 loadMember links: 4 active, 0 inactive (max no set, min not set)Serial1/0/0/:1Serial1/0/0/:2Serial1/0/0/:3Serial1/0/0/:4FRF.12 Guidelines
FRF.12 functions in hardware. Note the following:
•
•
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.
HW 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:
•
•
•
•
•
FRF.12 LFI Guidelines
LFI using FRF.12 is always done is hardware. Note the following:
•
•
•
Configuring QoS Features on Serial SPAs
The SIPs and SPAs support many QoS features using modular QoS CLI (MQC) configuration. For information about the QoS features supported by the serial SPAs, see the "Configuring QoS Features on a SIP" section on page 4-61.
Network Clocking for the Cisco 7600/SIP-200
You can use the Network Clocking for the Cisco 7600/SIP-2000 feature to select and configure a clock and distribute it across the chassis to be used as the Transmit reference on all SPA ports.
The Network Clocking for the Cisco 7600/SIP-2000 feature is supported on Cisco IOS Release 12.2SRB on the SPA-8XT1/E1, SPA-1XCHSTM1/OC3, SPA-4XOC3/STM1POS, SPA-4XOC3-ATM.
The linecard operates in three different modes, depends on the config and the configured source state.
•
Note
•
Note
•
Note
Note
Guidelines
•
•
•
•
•
•
Configuration Tasks
To configure Network Clocking for the SIP-200 on a 8-Port Channelized T1/E1 SPA, use the following commands:
Verifying
Use the show platform hardware network-clocks command to verify.
SIP-400-4# show plat hardware network-clocksSONET Clock Register = 0x20CA8000SONET Clock Interrupt Enable Register = 0x0SONET Clock Interrupt Status Register = 0x0MT90401 Reference : Primary Free RunningPrimary : SPA 0Secondary : SPA 0Backplane ReferencePrimary DISABLED : SPA 0Secondary DISABLED : SPA 0Status :Lock : 0 HoldOver : 0 SecOOR : 1 PriOOR : 1CLK_2M_OK : 1Config :PCCI : 0 FLOCK : 0 ModeSel : 2SI5321 CAL Signal : 0 SI5321 LOS Signal : 0SI5321 HoldOver : 0SIP-200-4#use the show network-clock command to verify output on RPPE1#sh network-clocksActive source = SONET 1/3/0Active source backplane reference line = Primary Backplane ClockAll Network Clock Configuration---------------------------------Priority Clock Source State Reason1 SONET 1/3/0 ValidCurrent operating mode is RevertiveCurrent OOR Switchover mode is SwitchoverThere are no slots disabled from participating in network clockingPE1#Saving the Configuration
To save your running configuration to nonvolatile random-access memory (NVRAM), use the following command in privileged EXEC configuration mode:
For more information about managing configuration files, refer to the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2 and Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 publications.
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 8-Port Channelized T1/E1 SPA.
Verifying Per-Port Interface Status
To find detailed interface information on a per-port basis for the 8-Port Channelized T1/E1 SPA, use the show interfaces serial command. For a description of the command output, see Chapter 40, "SIP, SSC, and SPA Commands."
The following example provides sample output for interface port 0 on the SPA located in the first subslot of the SIP installed in slot 6 of a Cisco 7609 router:
Router# show interface serial 6/0/0:0Serial6/0/0:0 is up, line protocol is upHardware is SPA-T1E1MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation PPP, crc 32, loopback not setKeepalive set (10 sec)LCP Open, multilink OpenLast input 00:00:38, output 00:00:00, output hang neverLast clearing of "show interface" counters 01:46:16Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)30 second input rate 0 bits/sec, 0 packets/sec30 second output rate 0 bits/sec, 0 packets/sec1272 packets input, 20396 bytes, 0 no bufferReceived 0 broadcasts (0 IP multicast)0 runts, 0 giants, 0 throttles6 input errors, 3 CRC, 0 frame, 0 overrun, 0 ignored, 3 abort1276 packets output, 20460 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitions no alarm presentTimeslot(s) Used:1-24, subrate: 64Kb/s, transmit delay is 0 flagsConfiguration Examples
This section includes the following configuration examples:
•
•
•
Framing and Encapsulation Configuration Example
The following example sets the framing and encapsulation for the controller and interface:
! Specify the controller and enter controller configuration mode!Router(config)# controller t1 6/0/0!! Specify the framing method!Router(config-controller)# framing esf!! Exit controller configuration mode and return to global configuration mode!Router(config-controller)# exit!! Specify the interface and enter interface configuration mode!Router(config)# interface serial 6/0/0:0!! Specify the encapsulation protocol!Router(config-if)# encapsulation ppp!! Exit interface configuratin mode!Router(config-if)# exit!! Exit global configuration mode!Router(config)# exitCRC Configuration Example
The following example sets the CRC size for the interface:
! Specify the interface and enter interface configuration mode!Router(config)# interface serial 6/0/0:0!! Specify the CRC size!Router(config-if)# crc 32!! Exit interface configuration mode and return to global configuration mode!Router(config-if)# exit!! Exit global configuration mode!Router(config)# exitFacility Data Link Configuration Example
The following example configures Facility Data Link:
! Specify the controller and enter controller configuration mode!Router(config)# controller t1 6/0/0!! Specify the FDL specification!Router(config-controller)# fdl ansi!! Exit controller configuration mode and return to global configuration mode!Router(config-controller)# exit!! Exit global configuration mode!Router(config)# exitMLPPP Configuration Example
The following example creates a PPP Multilink bundle:
! Enter global configuration mode!Router# configure terminal!! Create a multilink bundle and assign a group number to the bundle!Router(config)# interface multilink 1!! Specify an IP address for the multilink group!Router(config-if)# ip addres 123.456.789.111 255.255.255.0!! Enable Multilink PPP!Router(config-if)# ppp multilink!! Leave interface multilink configuration mode!Router(config-if)# exit!! Specify the interface to assign to the multilink bundle!Router(config)# interface serial 3/1//0:1!! Enable PPP encapsulation on the interface!Router(config-if)# encapsulation PPP!! Assign the interface to a multilink bundle!Router(config-if)# multilink-group 1!! Enable Multilink PPP!Router(config-if)# ppp multilink!! Exit interface configuration mode!Router(config-if)# exit!! Exit global configuration mode!Router(config)# exitMFR Configuration Example
The following example configures Multilink Frame Relay (MFR):
! Create a MFR interface and enter interface configuration mode!Router(config)# interface mfr 49!! Assign the bundle identification (BID) name `test' to a multilink bundle.!Router(config-if)# frame-relay multilink bid test!! Exit interface configuration mode and return to global configuration mode!Router(config-if)# exit!! Specify the serial interface to assign to a multilink bundle!Router(config)# interface serial 5/1/3:0!! Creates a multilink Frame Relay bundle link and associates the link with a multilink bundle!Router(config-if)# encapsulation frame-relay mfr 49!! Assigns a bundle link identification (LID) name with a multilink bundle link!Router(config-if)# frame-relay multilink lid test!! Configures the interval at which the interface will send out hello messages!Router(config-if)# frame-relay multilink hello 15!! Configures the number of seconds the interface will wait for a hello message acknowledgement before resending the hello message!Router(config-if)# frame-relay multilink ack 6!! Configures the maximum number of times the interface will resend a hello message while waiting for an acknowledgement!Router(config-if)# frame-relay multilink retry 5!! Exit interface configuration mode and return to global configuration mode!Router(config-if)# exit!! Exit global configuration mode!Router(config)# exitInvert Data on the T1/E1 Interface Example
The following example inverts the data on the serial interface:
! Enter global configuration mode!Router# configure terminal!! Specify the serial interface and enter interface configuration mode!Router(config)# interface serial 5/1/3:0!! Configure invert data!Router(config-if)# invert data!! Exit interface configuration mode and return to global configuration mode!Router(config-if)# exit!! Exit global configuration mode!Router(config)# exit
