- Cisco 10000 Series Router Line Card Configuration Guide
Feedback
Table Of Contents
4-Port Channelized T3 Half-Height Line Card Configuration
Checking Hardware and Software Compatibility
Interface Configuration Sample
Configuring a T3 Interface as Unchannelized
Specifying Subrate T3 Bandwidth
Configuring a T3 Interface as Channelized
Channel-Group Command for DS0 Time Slots and T1s
High Availability Using Line Card Redundancy
Prerequisites for Line Card Redundancy
Restrictions for Line Card Redundancy
Configuring Line Card Redundancy
Verifying and Monitoring Line Card Redundancy
Performing a Manual Line Card Switchover
show controllers t3 bert Command
linecard-group y-cable Command
4-Port Channelized T3 Half-Height Line Card Configuration
This chapter describes the Cisco 10000 series 4-Port Channelized T3 Half-Height line card, hereafter known as the 4-Port Channelized T3 Half-Height line card.
The 4-Port Channelized T3 Half-Height line card provides the Cisco 10000 router with four DS3 ports of high-density T3 service (eight T3 ports per slot).
This chapter contains the following sections:
•
Interface Configuration Sample
•
•
Software Support
Table 4-1 shows the minimum Cisco IOS release on each release train that supports the 4-Port OC-3/STM-1 ATM line card.
Table 4-1 4-Port OC-3/STM-1 ATM Line Card Software Support
PRE2
Cisco IOS Release 12.2(28)SB and later releases of Cisco IOS 12.2SB
Checking Hardware and Software Compatibility
The PRE installed in the Cisco 10000 series router chassis must support the Cisco IOS software running on the router. Use the show version command to check the PRE version installed.
To see if a feature is supported by a Cisco IOS release, to locate the software document for that feature, or to check the minimum software requirements of Cisco IOS software with the hardware installed on your router, Cisco maintains the Software Advisor tool on Cisco.com at http://www.cisco.com/pcgi-bin/Support/CompNav/Index.pl
This tool does not verify whether line cards within a system are compatible, but does provide the minimum Cisco IOS requirements for individual hardware line cards, modules, or options.
You must be a registered user on Cisco.com to access this tool.
Feature Overview
The 4-Port Channelized T3 Half-Height line card is very similar in function to the 6-Port Channelized T3 line card. The differences are summarized in the following features list for the 4-Port Channelized T3 Half-Height line card:
•
•
•
•
–
–
–
–
Note
•
•
•
•
Note
Default Values
Table 4-2 lists default values for the 4-Port Channelized T3 Half-Height line card and indicates which values apply to which line speeds. The table includes the command used for modifying a default value and indicates whether a value needs to be the same (or opposite) on the remote end of the connection.
Interface Syntax
To specify an interface number in a configuration command, use the syntax in Table 4-3 to identify interfaces on the 4-Port Channelized T3 Half-Height line card.
Examples:
•
Router(config)# controller t3 2/0/0Router(config-controller)# t1 6•
Router(config)# interface serial 2/0/0/6:8Router(config-if)#Interface Configuration Sample
Each T3 controller can be configured as a single T3 interface (full or subrate), as 28 T1 interfaces, or as an even larger number of fractional T1s. The following procedure walks you through the basic steps for creating full-rate and subrate T3 interfaces, as well as T1 and fractional T1 interfaces:
Step 1
Full-Rate T3 Interface
a.
Router(config)# controller t3 2/0/0Router(config-controller)#b.
Router(config-controller)# no channelizedRouter(config-controller)# exitRouter(config)#c.
Router(config)# interface serial 2/0/0d.
Subrate T3 Interface
a.
Router(config)# controller t3 2/0/1Router(config-controller)#b.
Router(config-controller)# no channelizedRouter(config-controller)# exitRouter(config)#c.
Router(config)# interface serial 2/0/1Router(config-if)# dsu mode digital-linkRouter(config-if)# dsu bandwidth 16000d.
Full T1 Interface
a.
Router(config)# controller t3 2/0/2Router(config-controller)#b.
Router(config-controller)# t1 1 channel-group 20 timeslots 1-24c.
Router(config)# interface serial 2/0/2/1:20d.
Fractional T1 Interface
a.
Router(config)# controller t3 2/0/3Router(config-controller)#b.
Router(config-controller) t1 3 channel-group 19 timeslots 1-6, 10Router(config-controller) t1 3 channel-group 20 timeslots 7,8,9Router(config-controller) t1 3 channel-group 21 timeslots 11-24c.
Router(config)# interface serial 2/0/3/3:19d.
Step 2
Router(config-if)# encapsulation frame relayStep 3
Router(config-if)# ip address 172.16.32.49 255.255.0.0Step 4
Step 5
Router(config-if)# no shutdownStep 6
Step 7
Router# copy running-config startup-configAfter you create an interface configuration, you can modify it at any time by using the appropriate Cisco IOS configuration commands.
Unchannelized T3 Commands
By default, a T3 interface on a 4-Port Channelized T3 Half-Height line card is channelized into 28 T1 interfaces. You must unchannelize the T3 interface in order to create a full-rate or subrate T3 interface. This section describes the commands you use to create, customize, and test full-rate and subrate T3 interfaces. This section describes the following:
•
•
Note
Configuring a T3 Interface as Unchannelized
The default value for a T3 interface is channelized. To create an unchannelized T3 interface, you must first enter controller configuration mode for the T3 controller you want to configure.
controller T3 slot/sub-slot/portAfter entering controller configuration mode, you can configure the T3 interface as unchannelized (clear channel) by entering the no channelized command. Use the channelized command to return the interface to its default (channelized).
[no] channelized
Caution
In the following example, an unchannelized T3 interface is created:
Router(config)# controller T3 1/0/0Router(config-controller)# no channelizedSpecifying the DSU Mode
To specify a DSU mode for a selected T3 interface, use the dsu mode command from interface configuration mode. This command configures the line card to emulate a manufacturer's proprietary multiplexing scheme.
[no] dsu mode [Adtran | cisco | Digital-link | Kentrox | Larscom | verilink-highbit | verilink-lowbit]The default DSU mode is cisco.
Use the no form of the command to return the DSU mode to its default.
In the following example, the DSU mode is set to cisco:
Router(config)# interface serial 1/0/0Router(config-if)# dsu mode ciscoSpecifying Subrate T3 Bandwidth
To specify subrate T3 bandwidth, use the dsu bandwidth bandwidth command from interface configuration mode.
[no] dsu bandwidth bandwidthWhere bandwidth is a numeric value between 0 and 44210 kbps.
The default bandwidth is 44210 kbps.
To return to the default bandwidth, use the no form of this command.
When you specify a value, the software sets the bandwidth to the closest acceptable bandwidth, based on the time slot size for the current DSU mode.
To use the dsu bandwidth command, the remote side of the connection must also support the same DSU modes.
In the following example, a bandwidth of 16000 kbps is specified:
Router(config)# interface serial 1/0/0Router(config-if)# dsu bandwidth 16000Setting the Framing Type
To specify a framing type for the unchannelized T3 controller, use the framing command.
[no] framing [c-bit | m13]The default framing type is C-bit.
Use the no form of this command to restore the default framing type.
In the following example, framing is set to m13:
Router(config)# interface serial 1/0/0Router(config-if)# framing m13Enabling Scrambling
To enable scrambling on an unchannelized T3 interface, use the scramble command from interface configuration mode.
[no] scrambleThe default setting for this command is no scramble (scrambling disabled).
Both sides of the link should have the same scrambling setting.
In the following example, scrambling is enabled on the specified T3 interface:
Router(config)# interface serial 1/0/0Router(config-if)# scrambleSpecifying an Idle Character
To set a specific character on the unchannelized T3 interface to be transmitted between HDLC packets, use the idle character command from interface configuration mode.
[no] idle-character [flags | marks]Where:
•
•
The default idle character is 0x7e.
Note
Use the no form of the command to return the idle character to its default.
In the following example, the idle character is set to flags:
Router(config)# interface serial 1/0/0Router(config-if)# idle-character flags
Note
Configuring a BER Test
You can configure an unchannelized T3 interface to run a bit error rate (BER) test. The test can be used in checking cables and solving signal problems in the field. To send a BER test pattern on an unchannelized T3 interface, use the following interface configuration command:
[no] bert [errors number | pattern pattern] interval timeWhere:
•
•
–
–
–
–
–
–
–
•
You can terminate a BER test at any time using the no bert command.
For more information, refer to the online Cisco 10000 Series Internet Router Troubleshooting Guide.
The following are example of configuring a BER test:
•
Router(config)# interface serial 1/0/0Router(config-if)# bert pattern 2^20 interval 5•
Router(config)# interface serial 1/0/0Router(config-if)# bert pattern 1s interval 1440To show BER test statistics, use the show controllers t3 slot/subslot/port bert command in EXEC or privileged EXEC mode:
Router# show controllers t3 6/1/0 bert T3 6/1/0 is up. BERT test result (done) Test Pattern : 2^15, Status : Not Sync, Sync Detected : 1 Interval : 5 minute(s), Time Remain : 0 minute(s) Bit Errors (since BERT started): 0 bits, Bits Received (since BERT started): 13025 Mbits Bit Errors (since last sync): 0 bits Bits Received (since last sync): 13025 MbitsSpecifying the Cable Length
To specify the cable length for the T3 controller, use the cablelength command.
[no] cablelength feetWhere feet is a number from 0 to 450.
The default value is 249 feet.
Use the no form of this command to restore the default cable length.
In the following example, the cable length value is set to 40 feet.
Router(config)# interface serial 1/0/0Router(config-if)# cablelength 40
Note
Entering MDL Messages
You can configure maintenance data link (MDL) messages (as defined in the ANSI T1.107a-1990 specification) on the unchannelized T3 interface.
Note
To configure MDL messages, use the mdl command.
[no] mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port | generator} id_string}Where:
•
•
•
•
•
•
•
(up to 38 characters).•
•
The default is that no MDL message is configured.
Use the no form of the command to remove an MDL message.
Examples of configuring MDL messages follow:
•
Router(config)# interface serial 1/0/0Router(config-if)# mdl transmit path•
Router(config-if)# mdl transmit idle-signal•
Router(config-if)# mdl transmit test-signal•
Router(config-if)# mdl string eic router A•
Router(config-if)# mdl string lic test network•
Router(config-if)# mdl string fic building b•
Router(config-if)# mdl string unit abc•
Router(config-if)# mdl string pfi string•
Router(config-if)# mdl string port string•
Router(config-if)# mdl string generator stringSetting the Clock Source
At the prompt, set the internal or line clock source for the selected T3 controller using the clock source command. This command is set in controller configuration mode.
clock source {internal | line}Where:
•
•
The default is clock source internal.
In this example, a T3 controller is instructed to use a line clock source.
Router(config)# interface serial 1/0/0Router(config-if)# clock source line
Note
Configuring Loopback Mode
You can configure the T3 controller for loopback mode using the loopback command.
[no] loopback [local | network | remote]Local and network loopbacks are the same.
To cancel a loopback, use the no form of the command.
For more information on the loopback command, refer to the online Cisco 10000 Series Internet Router Troubleshooting Guide.
Examples:
•
Router(config)# interface serial 1/0/0Router(config-if)# loopback local•
Router(config)# interface serial 1/0/0Router(config-if)# framing c-bitRouter(config-if)# loopback remote
Note
Running Equipment Loopbacks
Use the equipment loopback command to run loopbacks in conjunction with remote equipment.
[no] equipment [customer | network] loopbackWhere:
•
•
Use the no form of the command to terminate the loopback.
For more information on the loopback command, refer to the online Cisco 10000 Series Internet Router Troubleshooting Guide.
In the following example, an equipment network loopback is configured:
Router(config)# interface serial 1/0/0Router(config-if)# equipment network loopbackChannelized T3 Commands
By default, a T3 interface on a 4-Port Channelized T3 Half-Height line card is channelized into 28 T1 interfaces. This section describes the commands you use to customize and test a channelized T3 interface. This section describes:
•
To use the channels for subscriber traffic, you must configure the T1 and DS0 components. For more information, see the "Channel-Group Command for DS0 Time Slots and T1s" section.
Figure 4-1 shows the levels of configurable interface bandwidth that channelization offers.
Figure 4-1 Channelization of T3s
Configuring a T3 Interface as Channelized
All configuration of a T3 channelized interface must occur in controller configuration mode.
controller T3 slot/sub-slot/portA T3 interface is channelized by default. Use the channelized command if you had previously made the interface unchannelized and want to change the setting.
[no] channelized
Caution
The following example shows the creation of a channelized T3 interface:
Router(config)# controller T3 1/0/0Router(config-controller)# channelizedSpecifying the Cable Length
To specify the cable length for the T3 controller, use the cablelength command.
[no] cablelength feetWhere feet is a number from 0 to 450.
The default value is 249 feet.
Use the no form of this command to restore the default cable length.
In the following example, the cable length value is set to 40 feet.
Router(config)# controller T3 1/0/0Router(config-controller)# cablelength 40
Note
Setting the Framing Type
To specify a framing type for the channelized T3 controller, use the framing command.
[no] framing [c-bit | m23 | f]The default is auto-detect.
Use the no form of the command to return the framing type to its default.
You can instruct the 4-Port Channelized T3 Half-Height line card to detect the framing type from the far end and transmit that same framing type as follows:
Router(config)# controller T3 1/0/0Router(config-controller)# framing auto-detectEntering MDL Messages
You can configure maintenance data link (MDL) messages (as defined in the ANSI T1.107a-1990 specification) on the channelized T3 interface.
Note
To configure MDL messages, use the mdl command.
[no] mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port | generator} id_string}Where:
•
•
•
•
•
•
•
(up to 38 characters).•
•
The default is that no MDL message is configured.
Use the no form of the command to remove an MDL message.
Examples of configuring MDL messages follow:
•
Router(config)# controller T3 1/0/0Router(config-controller)# mdl transmit path•
Router(config-controller)# mdl transmit idle-signal•
Router(config-controller)# mdl transmit test-signal•
Router(config-controller)# mdl string eic router A•
Router(config-controller)# mdl string lic test network•
Router(config-controller)# mdl string fic building b•
Router(config-controller)# mdl string unit abc•
Router(config-controller)# mdl string pfi string•
Router(config-controller)# mdl string port string•
Router(config-controller)# mdl string generator stringSpecifying the Idle Pattern
You can set a specific pattern to be transmitted between HDLC packets on all unconfigured time slots that belong to a channelized T3 interface. To do so, use the idle pattern command.
[no] idle pattern patternsWhere patterns is a number in the range of 0x0 to 0xff (hexadecimal) or 0 to 255 (decimal). You can enter this value in either hexadecimal or decimal form. Values of 0 to 254 set the idle pattern to HDLC flags (0x7e); a value of 255 sets the pattern to 0xff (all ones).
Note
The default idle pattern is 0x7e.
Use the no form of the command to return the idle pattern to its default value.
Examples:
•
Router(config)# controller T3 1/0/0Router(config-controller)# idle pattern 0x10•
Router(config)# controller T3 1/0/0Router(config-controller)# idle pattern 23Setting the Clock Source
At the prompt, set the internal or line clock source for the selected T3 controller using the clock source command. This command is set in controller configuration mode.
clock source {internal | line}Where:
•
•
The default is clock source internal.
In this example, a T3 controller is instructed to use a line clock source.
Router(config)# controller T3 1/0/0Router(config-controller)# clock source line
Note
Configuring Loopback Mode
You can configure the T3 controller for loopback mode using the loopback command.
[no] loopback [local | network | remote]Local and network loopbacks are the same.
To cancel a loopback, use the no form of the command.
Note
For more information on the loopback command, refer to the online Cisco 10000 Series Internet Router Troubleshooting Guide.
Examples:
•
Router(config)# controller T3 1/0/0Router(config-controller)# loopback local•
Router(config)# controller T3 1/0/0Router(config-controller)# framing c-bitRouter(config-controller)# loopback remote
Note
Running Equipment Loopbacks
Use the equipment loopback command to run loopbacks in conjunction with remote equipment.
[no] equipment [customer | network] loopbackWhere:
•
•
Use the no form of the command to terminate the loopback.
For more information on the loopback command, refer to the online Cisco 10000 Series Internet Router Troubleshooting Guide.
In the following example, an equipment network loopback is configured:
Router(config)# controller T3 1/0/0Router(config-controller)# equipment network loopbackChannel-Group Command for DS0 Time Slots and T1s
Each channelized T3 consists of 28 T1s, each of which is divided into 24 time slots (or DS0s). To create an interface that supports subscriber traffic, you must combine the time slots into channel groups. Use the t1 channel-group command to create a channel group.
Channel groups have these characteristics:
•
•
–
–
•
•
Figure 4-1 illustrates channelization possibilities on the 4-Port Channelized T3 Half-Height line card.
You create a logical channel group using the following command:
[no] t1 t1-number channel-group channel-group-number timeslots list-of-timeslots [speed {56 | 64}]Where:
•
•
•
•
Use the no form of the command to remove a logical channel group.
The following examples show how to use the t1 channel-group command:
•
Router(config)# controller t3 1/0/0Router(config-controller)# t1 3 channel-group 20 timeslots 1-8, 10To enter interface configuration mode for this channel group, enter the following:
Router(config)# interface serial 1/0/0/3:20•
Router(config)# controller t3 1/0/0Router(config-controller)# t1 4 channel-group 18 timeslots 1-24To enter interface configuration mode for this channel group, you enter the following:
Router(config)# interface serial 1/0/0/4:18•
Router(config)# controller t3 1/0/0Router(config-controller)# t1 5 channel-group 19 timeslots 1-6Router(config-controller)# t1 5 channel-group 20 timeslots 10Router(config-controller)# t1 5 channel-group 21 timeslots 7-9, 24•
Router(config)# controller T3 1/0/0Router(config-controller)# no t1 1 channel-group 20Channelized T1 Commands
From controller configuration mode for a T3 interface, you can enter commands to modify aspects of a T1 interface. This section describes the following:
After you configure a T1 interface, you can add encapsulation, routing, and other instructions by entering interface configuration mode; for example:
Router(config)# interface serial 1/0/0/4:18Setting the Framing Format
You can specify the T1 interface framing format using the following command:
[no] t1 t1-number framing {esf | sf [hdlc-idle {0x7e | 0xff}]}Where:
•
•
•
The default framing format is extended super frame (ESF).
Use the no form of the command to return framing to its default value.
The following are examples of setting the framing format:
•
Router(config)# controller T3 1/0/0Router(config-controller)# t1 6 framing sf•
Router(config)# controller T3 1/0/0Router(config-controller)# t1 16 framing esfControlling Yellow Alarms
Use the t1 yellow command to turn the detection or generation of a yellow alarm on or off.
[no] t1 t1-number yellow {detection | generation}Where:
•
•
•
When you select SF framing for a full T1 interface (24 time slots) that uses the default speed of 64, consider using the no t1-number yellow detection command to turn off yellow alarm detection, because the yellow alarm can be incorrectly detected with SF framing.
In the following example, T1 interface 1 is set to yellow detection:
Router(config)# controller t3 1/0/0Router(config-controller)# t1 1 yellow detectionSetting the Clock Source
You can set the internal or line (network) clock source for a T1 interface using the controller command.
t1 t1-number clock source {internal | line}Where:
•
•
•
The default is clock source internal.
In the following example, the interface is instructed to get its clock source from the line:
Router(config)# controller T3 1/0/0Router(config-controller)# t1 1 clock source lineConfiguring FDL
You can enable 1-second transmissions of performance reports through the facility data link (FDL) according to the ANSI T1.403 specification, on both ends of the T1 connection. To do so, use the following command:
[no] t1 t1-number fdl ansiWhere t1-number is T1 interface 1 to 28.
Use the no form of the command to disable this feature.
Note
In the following example, FDL is enabled:
Router(config)# controller t3 1/0/0Router(config-controller)# t1 2 fdl ansiConfiguring a BER Test
You can configure an individual T1 interface to run an independent BER test. The test is used to check cables and solve signal problems in the field. To send a BER test pattern on a T1 interface, use the following command in controller configuration mode:
[no] t1 t1-number bert pattern pattern interval time [unframed]Where:
•
•
•
–
–
–
–
–
–
–
–
–
–
–
•
Note
You can terminate a BER test at any time using the no form of the command.
For more information, refer to the online Cisco 10000 Series Internet Router Troubleshooting Guide.
The following are examples of configuring a BER test:
•
Router(config)# controller T3 1/0/0Router(config-controller)# t1 10 bert pattern 2^20 interval 5 unframed•
Router(config)# controller T3 1/0/0Router(config-controller)# t1 10 bert pattern 1s interval 14400 unframedTo show BER test statistics, use the show controllers t3 slot/subslot/port t1-number bert command in EXEC or privileged EXEC mode:
Router# show controllers t3 6/1/1/1 bert T3 6/1/1/1 is up. Hardware is C10K Half Height CT3 line card T1 1 BERT test result (running) Test Pattern : 2^15, Status : Sync, Sync Detected : 1 Interval : 5 minute(s), Time Remain : 5 minute(s) Bit Errors (since BERT started): 0 bits, Bits Received (since BERT started): 36 Mbits Bit Errors (since last sync): 0 bits Bits Received (since last sync): 36 MbitsThe 4-Port Channelized T3 Half-Height line card supports any combination of six T1 BER tests simultaneously for each set of two ports. That is, six T1 BER tests for ports 0 and 1, and six T1 BER tests for ports 2 and 3. Table 4-4 shows a sample BER test distribution for the four ports of the 4-Port Channelized T3 Half-Height line card.
Table 4-4 Sample BER Test Distribution
Port 0
6 T1 BER tests
Port 1
1 T3 BER test
Port 2
3 T1 BER tests
Port 3
3 T1 BER tests
Configuring T1 Loopback Mode
If problems occur when you configure a T1 interface, you can troubleshoot the line card by using the following command from controller configuration mode:
[no] t1 t1-number loopback [local | network {line | payload} | remote [line [fdl {ansi | bellcore} | inband [maintenance]] | payload [fdl | ansi]]]Where:
•
•
•
•
Note
The 4-Port Channelized T3 Half-Height line card sends the following code for remote line FDL ANSI loopback:
–
–
The 4-Port Channelized T3 Half-Height line card sends the following code for remote line FDL Bellcore (SmartJack) loopback:
–
–
•
The maintenance keyword is new in 12.2(28)SB. The maintenance keyword sends loopback codes to an interface on the remote end of the connection. This sets loopback on the remote end interface. (Note that the 4-Port Channelized T3 Half-Height line card does not respond to inband maintenance codes.)
–
–
–
–
•
Note
The 4-Port Channelized T3 Half-Height line card sends the following code for remote payload FDL ANSI loopback:
–
–
Use the no form of the command to terminate a loopback.
For more information on this command, refer to the online Cisco 10000 Series Internet Router Troubleshooting Guide.
The following are examples of configuring loopback mode:
•
Router(config)# controller t3 1/0/0Router(config-controller)# t1 1 loopback local•
Router(config)# controller t3 1/0/0Router(config-controller)# t1 1 loopback remote line fdl ansiHigh Availability Using Line Card Redundancy
You can configure one-to-one line card redundancy using the optional Y-cables and configuring 4-Port Channelized T3 Half-Height line cards for redundancy. This redundancy provides automatic failover protection at the line card level for the 4-Port Channelized T3 Half-Height line card. Because the redundancy is at the line card level, all ports are switched over during a failover.
The redundant line cards occupy the two subslots within the same chassis line card slot. There is one Y-cable for receive and one for transmit for each of the four ports for the two redundant line cards. For information about installing redundant 4-Port Channelized T3 Half-Height line cards and the Y-cables, see the Cisco 10000 Series Router Line Card Hardware Installation Guide.
This section contains the following topics:
•
•
•
•
•
•
Prerequisites for Line Card Redundancy
Before configuring line card redundancy, the Y-cables must be installed; before deconfiguring redundancy the Y-cables must be removed.
Restrictions for Line Card Redundancy
The following restrictions apply to line card redundancy:
•
•
•
Configuring Line Card Redundancy
After verifying that the Y-cables are installed, you are ready to configure one-to-one redundancy between two 4-Port Channelized T3 Half-Height line cards. To configure line card redundancy, enter the following commands beginning in global configuration mode:
Example 4-1 configures two 4-Port Channelized T3 Half-Height line cards that are installed in line card slot 2 for one-to-one redundancy.
Example 4-1 Configuring Line Card Redundancy
Router(config)# redundancyRouter(config-red)# linecard-group 1 y-cableRouter(config-red-lc)# member subslot 2/1 primaryRouter(config-red-lc)# member subslot 2/0 secondaryVerifying and Monitoring Line Card Redundancy
To verify line card redundancy and to display information about a line card or a line card group, use the show redundancy linecard command. The following table describes the type of information provided by some of the command options.
The output examples in this section use the following configuration:
!redundancylinecard-group 0 y-cablemember subslot 8/1 primarymember subslot 8/0 secondarymode sso!controller T3-RED 8/1/0controller T3-RED 8/1/1controller T3-RED 8/1/2controller T3-RED 8/1/3!Example 4-2 shows output from the show redundancy linecard all command. It shows the redundancy state of all line card slots. The line card group is indicated as "None" if the slot is empty, or if it contains a line card that has not been configured for redundancy.
For a redundant line card, the mode can be primary or secondary and is established when redundancy is configured. The mode of a line card does not change. For the 4-Port Channelized T3 Half-Height line card, the line card in subslot 0 is always secondary, and the line card in subslot 1 is always primary.
The line card role indicates which line card in a redundant configuration is sending and receiving traffic. The line card with the active role is sending and receiving traffic. The other line card in a redundant configuration has the role of standby. Unlike the line card mode, the role of a line card can change.
In Example 4-2 you can see there has been a switchover at some point, because the line card in slot 8, subslot 0 has the active role, even though its mode is secondary.
Example 4-2 show redundancy linecard all Command Output
Router# show redundancy linecard allLC My Peer Peer PeerSlot Subslot Group State State Slot Subslot Role Mode-----------------------------------------------------------------------------1 0 None Init - None None None None1 1 None Init - None None None None2 0 None Init - None None None None2 1 None Init - None None None None3 0 None Init - None None None None3 1 None Init - None None None None4 0 None Init - None None None None4 1 None Init - None None None None5 0 None Init - None None None None5 1 None Init - None None None None6 0 None Init - None None None None6 1 None Init - None None None None7 0 None Init - None None None None7 1 None Init - None None None None8 0 0 Active Stdby Hot 8 1 Active Secondary8 1 0 Stdby Hot - 8 0 Standby PrimaryExample 4-3 shows output from the show redundancy linecard subslot command. It displays information for a particular line card.
Example 4-3 show redundancy linecard subslot Command Output
Router# show redundancy linecard subslot 8/1Redundant LC Group Number: 0LC Slot: 8LC Subslot: 1Redundant LC Name: 8/1Redundant LC Mode: PrimaryRedundant LC Role: StandbyRedundant LC My State: Stdby HotRedundant LC Peer State: -Router# show redundancy linecard subslot 8/0Redundant LC Group Number: 0LC Slot: 8LC Subslot: 0Redundant LC Name: 8/0Redundant LC Mode: SecondaryRedundant LC Role: ActiveRedundant LC My State: ActiveRedundant LC Peer State: Stdby HotExample 4-4 shows output from the show redundancy linecard group command. It shows line card information for a specific line card group, which in this example is group 0. Note that the show redundancy linecard group command displays only the static line card configuration information. For example, it shows the line card mode (primary or secondary) but not the line card role, which changes in a switchover. The line card in slot 8, subslot 1, is primary even though it currently has the standby role.
Because there is only one line card group in the sample configuration, the show redundancy linecard group all command would display the same output as shown in Example 4-4.
Example 4-4 show redundancy linecard group Command Output
Router# show redundancy linecard group 0Group Identifier: 0NON-revertiveGroup Redundancy Type: Y_CABLEGroup Redundancy Class: 1:1Group Redundancy Configuration Type: LINECARD GROUPPrimary: Slot 8Subslot 1Secondary: Slot 8Subslot 0The show redundancy linecard history command and the show redundancy linecard sub-block command provide information that can be helpful to Cisco technical support personnel when they are assisting you in troubleshooting a redundancy problem. The output in Example 4-5 was collected after a line card switchover.
Note
Example 4-5 show redundancy linecard history Command Output
Router# show redundancy linecard historyAug 29 2005 06:03:16 46400671 - Slot(17): MY State Change, (Stdby Wait) -> (Stdby Hot)Aug 29 2005 06:03:16 46400671 - Slot(16): PEER State Change, (Stdby Wait) -> (Stdby Hot)Aug 29 2005 06:03:16 46400671 - Slot(16): PEER FSM Execution , Active:Stdby Wait:State NtfyAug 29 2005 06:03:16 46400671 - Slot(17): MY State Change, (Stdby LC Feat Sync) -> (Stdby Wait)Aug 29 2005 06:03:16 46400671 - Slot(16): PEER State Change, (Stdby LC Feat Sync) -> (Stdby Wait)Aug 29 2005 06:03:16 46400671 - Slot(16): PEER FSM Execution , Active:Stdby LC Feat Sync:Feat Sync DoneAug 29 2005 06:03:16 46400671 - Slot(17): MY State Change, (Stdby FIB Dnld) -> (Stdby LC Feat Sync)Aug 29 2005 06:03:16 46400671 - Slot(16): PEER State Change, (Stdby FIB Dnld) -> (Stdby LC Feat Sync)Aug 29 2005 06:03:16 46400671 - Slot(16): PEER FSM Execution , Active:Stdby FIB Dnld:Feat Sync ReqAug 29 2005 06:03:16 46400671 - Slot(17): MY State Change, (Stdby LC Cfg Dnld) -> (Stdby FIB Dnld)Aug 29 2005 06:03:16 46400671 - Slot(16): PEER State Change, (Stdby LC Cfg Dnld) -> (Stdby FIB Dnld)Aug 29 2005 06:03:16 46400671 - Slot(16): PEER FSM Execution , Active:Stdby LC Cfg Dnld:Cfg Dnld DoneAug 29 2005 06:03:16 46400671 - Slot(17): MY State Change, (Stdby Cold) -> (Stdby LC Cfg Dnld)Aug 29 2005 06:03:16 46400671 - Slot(16): PEER State Change, (Stdby Cold) -> (Stdby LC Cfg Dnld)Aug 29 2005 06:03:16 46400644 - Slot(16): PEER FSM Execution , Active:Stdby Cold:Cfg DnldAug 29 2005 06:03:16 46400644 - Slot(17): MY State Change, (Init) -> (Stdby Cold)Aug 29 2005 06:03:16 46400644 - Slot(16): PEER State Change, (Init) -> (Stdby Cold)Aug 29 2005 06:03:16 46400644 - Slot(16): PEER FSM Execution , Active:Init:UpAug 23 2005 21:18:03 49333 - Slot(16:-1): Checkpoint State Update, (Active:Init)Aug 23 2005 21:18:03 49333 - Slot(17:-1): Checkpoint State Update, (Init:Init)Aug 23 2005 21:18:03 49332 - Slot(16:-1): Checkpoint State Update, (Active Cold:Init)Aug 23 2005 21:18:03 49332 - Slot(17:16): Checkpoint State Update, (Active:Active Cold)Aug 23 2005 21:11:07 7881 - Slot(17:-1): Checkpoint State Update, (Active:Stdby Hot)Aug 23 2005 21:11:07 7881 - Slot(16:-1): Checkpoint State Update, (Stdby Hot:Init)Aug 23 2005 21:10:42 6393 - Slot(16): MY FSM execution, Init:Init:ResetExample 4-6 show redundancy linecard sub-block Command Output
Router# show redundancy linecard sub-block allSlotIndex Port H-IDB M-HW A-HW Type Role Flag----------------------------------------------------------16 0 5 21 13 Physical None 0x1516 1 7 22 15 Physical None 0x1516 2 9 23 17 Physical None 0x1516 3 11 24 19 Physical None 0x1517 0 21 13 5 Virtual - 0x317 0 13 21 5 Physical None 0x517 1 22 15 7 Virtual - 0x317 1 15 22 7 Physical None 0x517 2 23 17 9 Virtual - 0x317 2 17 23 9 Physical None 0x517 3 24 19 11 Virtual - 0x317 3 19 24 11 Physical None 0x5Performing a Manual Line Card Switchover
To initiate a manual switchover of the active 4-Port Channelized T3 Half-Height line card to the standby 4-Port Channelized T3 Half-Height line card, enter the following command in privileged Exec mode:
Example 4-7 shows how you can force the switchover of the active line card in slot 2, subslot 1, to the standby line card in slot 2, subslot 0.
Example 4-7 Manual Line Card Switchover
Router# redundancy linecard-group switchover from subslot 2/1Removing Line Card Redundancy
After verifying that the Y-cables are removed, you are ready to remove one-to-one redundancy between two 4-Port Channelized T3 Half-Height line cards. To remove line card redundancy, enter the following commands beginning in global configuration mode:
Example 4-8 removes one-to-one redundancy between two 4-Port Channelized T3 Half-Height line cards that are installed in slot 2 for one-to-one redundancy.
Example 4-8 Removing Line Card Redundancy
Router(config)# redundancyRouter(config-red)# linecard-group 1 y-cableRouter(config-red-lc)# no member subslot 2/0 secondaryRouter(config-red-lc)# no member subslot 2/1 primaryRouter(config-red-lc)# exitRouter(config-red)# no linecard-group 1 y-cableFailover Conditions
The following describes the conditions under which the primary line card will fail over to the secondary line card when line card redundancy is configured.
•
•
•
•
Command Reference
The following commands are new in Cisco IOS Release 12.2(28)SB:
•
•
•
show controllers t3 bert Command
To display BER test statistics, use the show controllers t3 bert command in EXEC or privileged EXEC mode.
show controllers t3 {slot/subslot/port} [/t1-number] bert
Syntax Description
Command Modes
EXEC
Privileged EXEC
Command History
Examples
The following example shows BER test statistics for an unchannelized T3 interface:
Router# show controllers t3 6/1/0 bert T3 6/1/0 is up. BERT test result (done) Test Pattern : 2^15, Status : Not Sync, Sync Detected : 1 Interval : 5 minute(s), Time Remain : 0 minute(s) Bit Errors (since BERT started): 0 bits, Bits Received (since BERT started): 13025 Mbits Bit Errors (since last sync): 0 bits Bits Received (since last sync): 13025 MbitsThe following example shows BER test statistics for a channelized T3 interface:
Router# show controllers t3 6/1/0 bert T3 6/1/0 is up. BERT test result (running) Test Pattern : 2^15, Status : Sync, Sync Detected : 1 Interval : 3 minute(s), Time Remain : 1 minute(s) Bit Errors (since BERT started): 0 bits, Bits Received (since BERT started): 5493 Mbits Bit Errors (since last sync): 0 bits Bits Received (since last sync): 5493 MbitsThe following example shows BER test statistics for a T1 interface:
Router# show controllers t3 6/1/1/1 bert T3 6/1/1/1 is up. Hardware is C10K Half Height CT3 line card T1 1 BERT test result (running) Test Pattern : 2^15, Status : Sync, Sync Detected : 1 Interval : 5 minute(s), Time Remain : 5 minute(s) Bit Errors (since BERT started): 0 bits, Bits Received (since BERT started): 36 Mbits Bit Errors (since last sync): 0 bits Bits Received (since last sync): 36 MbitsRelated Commands
bert
Configures a BER test for an unchannelized or channelized T3 interface.
t1 bert pattern
Configures a BER test for a T1 interface.
linecard-group y-cable Command
To create a line card group for one-to-one line card redundancy, use the linecard-group y-cable command in redundancy mode. To remove the line card redundancy group, use the no form of this command.
linecard-group linecard-groupId y-cable
no linecard-group linecard-groupId y-cable
Syntax Description
linecard-groupId
An unsigned integer in the range 0 to the (maximum number of chassis line card subslots/2) -1.
y-cable
The link protection type for the line card group.
Defaults
No default behavior or values.
Command Modes
Redundancy
Command History
Usage Guidelines
The no linecard-group y-cable command removes the line card redundancy group and frees the linecard-groupId for reuse. The no linecard-group y-cable command succeeds only if there are no subslot members in the line card redundancy group.
Examples
The following example creates line card group number 1 for one-to-one line card redundancy:
Router(config)# redundancyRouter(config-red)# linecard-group 1 y-cableRelated Commands
member subslot Command
To configure the redundancy role of a line card, use the member subslot command in line card redundancy group mode. To remove the redundancy role of a line card, use the no form of this command.
member subslot slot/subslot {primary | secondary}
no member subslot slot/subslot {primary | secondary}
Syntax Description
Defaults
No default behavior or values
Command Modes
Line card redundancy group
Command History
Usage Guidelines
The primary line card must be the first line card configured and must occupy subslot 1. The secondary line card must be the second line card configured and must occupy subslot 0. Only one primary line card and one secondary line card can be configured.
Examples
The following creates line card group number 1 for one-to-one line card redundancy. It also specifies the line card in subslot 1 as the primary (active) line card, and the line card in subslot 0 as the secondary (standby) line card:
Router(config)# redundancyRouter(config-red)# linecard-group 1 y-cableRouter(config-red-lc)# member subslot 2/1 primaryRouter(config-red-lc)# member subslot 2/0 secondaryRelated Commands
