|
|
This chapter describes the procedures for configuring a Cisco 10000 ESR channelized T3 (CT3) line card (Figure 5-1). The chapter includes a table of default values and a detailed interface configuration example. This information is followed by sections that describe the principal commands:
Table 5-1 lists default values for the CT3 line card and indicates which values apply to which line speeds. The commands marked with an asterisk are described in the Cisco IOS Command Reference. The other commands are among those described in this chapter.
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.
| Command Name | Default Setting | Command Syntax | Remote Side Setting | DS 0 | T1 | Ch T3 | Unch T3 |
|---|---|---|---|---|---|---|---|
| Controller Configuration Mode | |||||||
249 | cablength feet | — |
|
| x | x | |
[no] channelized | — |
|
| x | x | ||
internal | _(_IREFOBJ:1041871_) _clock source [line | internal] | At least one side set to internal |
|
| x | x | |
internal | t1 t1-number _(_IREFOBJ:1041873_) _clock source [line | internal] | At least one side set to internal |
| x |
|
| |
auto-detect | _(_IREFOBJ:1041875_) _framing [c-bit | m23 | auto-detect] | Same |
|
| x |
| |
esf | t1 t1-number
_(_IREFOBJ:1041877_)
_framing [esf | sf
[hdlc-idle {0x7E |
0xFF}]]
| Same |
| x |
|
| |
0X7e (flags) | _(_IREFOBJ:1041879_) _idle pattern [0x0 to 0xFF] | Same |
|
| x |
| |
| Interface Configuration Mode | |||||||
16 | [no] _(_IREFOBJ:1041881_) _crc [16 | 32] | Same | x |
|
| x | |
44,210 | dsu bandwidth bandwidth | Same |
|
|
| x | |
cisco | _(_IREFOBJ:1041883_) _dsu mode mode | Same |
|
|
| x | |
HDLC | _(_IREFOBJ:1041885_) _encapsulation [hdlc | ppp | frame-relay] | Same | x |
|
| x | |
c-bit | _(_IREFOBJ:1043834_) _framing [c-bit | m13] | Same |
|
|
| x | |
flags (0x7e) | _(_IREFOBJ:1041887_) _idle character | Same |
|
|
| x | |
keepalive | Same | x |
|
| x | ||
4470 | _(_IREFOBJ:1041893_) _mtu size | Same | x |
|
| x | |
No scrambling | [no] _(_IREFOBJ:1041895_) _scramble | Same |
|
|
| x | |
To specify an interface number in a configuration command, use the syntax in Table 5-2 to identify interfaces on the CT3 line card.
Type of Interface | Slot | Subslot | Port (T3 Number) | T1 Number | Channel Group Number |
|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
Examples:
Router(config)# controller t3 2/0/0 Router(config-controller)# t1 6 command
Router(config)# interface serial 2/0/0/6:8 Router(config-if)
Full-Rate T3 Interface
a. Enter controller configuration mode.
Router(config)# controller t3 2/0/0 Router(config-controller)#
b. To create a full-rate T3 interface, you must eliminate the T1 interfaces by entering the no channelized command.
Router(config-controller)# no channelized Router(config-controller)# exit Router(config)#
c. Go to interface configuration mode:
Router(config)# interface serial 2/0/0
d. You can now continue to Step 2.
Subrate T3 Interface
a. Enter controller configuration mode.
Router(config)# controller t3 2/0/1 Router(config-controller)#
b. To create a subrate T3 interface, first create a full-rate one.
Router(config-controller)# no channelized Router(config-controller)# exit Router(config)#
c. Then go into interface configuration mode, where you can use the dsu bandwidth command to create a subrate T3 interface. In this example, a subrate T3 interface is created that has a bandwidth of 16,000 kbps.
Router(config)# interface serial 2/0/1 Router(config-if)# dsu bandwidth 16000
d. You can now continue to Step 2.
Full T1 Interface
a. Enter controller configuration mode.
Router(config)# controller t3 2/0/2 Router(config-controller)#
b. Use the t1 channel group command to create a T1 interface. In the following example, T1 interface 1 (of 28) is defined as being made up of a single channel group, number 20 (any number between 0 and 23). This channel group consists of all 24 DS0 timeslots.
Router(config-controller)# t1 1 channel-group 20 timeslots 1-24
c. Go to interface configuration mode for the channel group you just created.
Router(config)# interface serial 2/0/2/1:20
d. You can now continue to Step 2.
Fractional T1 Interface
a. Enter controller configuration mode.
Router(config)# controller t3 2/0/3 Router(config-controller)#
b. Use the t1 channel group command to create fractional T1 interfaces. In the following example, T1 interface 3 (of 28) is defined as being made up of three channel groups, numbers 19, 20, and 21. (numbers between 0 and 23 are allowed.) The channel groups consist of a total of 24 DS0 timeslots. Each channel group represents a separate interface.
Router(config-controller) t1 3 channel-group 19 timeslots 1-6, 10 Router(config-controller) t1 3 channel-group 20 timeslots 7,8,9 Router(config-controller) t1 3 channel-group 21 timeslots 11-24
c. Go to interface configuration mode for one of the channel groups. For example:
Router(config)# interface serial 2/0/3/3:19
d. You can now continue to Step 2.
Step 2 Enter the encapsulation method. This example shows the command for using Frame Relay encapsulation. You can also choose PPP or HDLC.
Router(config-if)# encapsulation frame relay
Step 3 If IP routing is enabled on the system, assign an IP address and subnet mask. For example:
Router(config-if)# ip address 172.16.32.49 255.255.0.0
Step 4 Add any configuration subcommands required to enable routing protocols and set the interface line characteristics.
Step 5 Change the shutdown state to up, which enables the interface.
Router(config-if)# no shutdown
Step 6 When you have entered all of the configuration subcommands to complete the configuration, press Ctrl-Z to exit configuration mode.
Step 7 To write the new configuration to NVRAM, type
Router# copy running-config startup-config
After you create an interface configuration, you can modify it at any time by using the appropriate Cisco IOS configuration commands.
By default, a T3 interface on a CT3 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:
You can also use the following commands, described in the "Channelized T3 Commands" section, when you are configuring an unchannelized T3: cablelength, clock source, mdl, equipment, and loopback.
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/port
The following example shows how to enter controller configuration mode:
Router(config)# controller T3 1/0/0 Router(config-controller)#
You can configure the T3 interface as unchannelized (clear channel) by entering the no channelized command.
[no]channelized channelized
 |
Caution The no channelized command removes all channel groups from a channelized T3 interface. If you have already configured channel groups, use this command with caution. |
Use the channelized command to return the interface to its default. The default value for a T3 interface is channelized.
In the following example, an unchannelized T3 interface is created:
Router(config)# controller T3 1/0/0 Router(config-controller)# no channelized
You can implement subrate T3 by specifying the bandwidth for an unchannelized T3 interface. To do so, use the command dsu bandwidth bandwidth from interface configuration mode.
dsu bandwidth bandwidth[no]bandwidth bandwidth
Where 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 timeslot size for the current DSU mode.
In order for you to use this command, the remote side of the connection must have a Cisco 7200 or Cisco 7500 with a PA-T3 or PA-2T3 port adapter or a T3 DSU supported by the dsu mode command.
In the following example, a bandwidth of 16000 kbps is specified:
Router(config)# interface serial 1/0/0 Router(config-if)# dsu bandwidth 16000
 |
Tips "Configuring Multilink Point-to-Point Connections," describes an alternative approach for reducing the bandwidth of a T3 channel. |
To specify a framing type for the unchannelized T3 controller, use the framing command.
framing [c-bit | m13][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/0 Router(config-if)# framing m13
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.
dsu mode [Adtran | cisco | Digital-link | Kentrox | Larscom | verilink-highbit | verilink-lowbit][no]dsu mode
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/0 Router(config-if)# dsu mode cisco
To enable scrambling on an unchannelized T3 interface, use the scramble command from interface configuration mode.
scramble[no]scramble
The 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/0 Router(config-if)# scramble
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.
idle-character [flags | marks][no]idle-character [flags | marks]
Where:
The default idle character is 0x7e.
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/0 Router(config-if)# idle-character flags
 |
Note Some systems interpret marks, 0xff, as an abort signal. Therefore, flags, 0x7e, is preferred. |
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:
bert [errors number | pattern pattern] interval time[no]bert
Where:
You can terminate a BER test at any time using the no bert command.
For more information, refer to the online Cisco 10000 ESR Troubleshooting Guide.
Examples:
Router(config)# interface serial 1/0/0 Router(config-if)# bert pattern 2^20 interval 5
Router(config)# interface serial 1/0/0 Router(config-if)# bert pattern 1s interval 1440
By default, a T3 interface on a CT3 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 discusses
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 Timeslots and T1s" section.
Figure 5-2 shows the levels of configurable interface bandwidth that channelization offers.
You may need to enter controller configuration mode for actions involving the T3 interface. For example, enter this mode to change an unchannelized T3 interface back to a channelized one or to set MDL messages.
controller T3 slot/sub-slot/port
The following example shows how to enter controller configuration mode:
Router(config)# controller T3 1/0/0 Router(config-controller)#
A 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 channelized
|
Caution The no channelized command removes all channel groups from a channelized T3 interface. If you have already configured channel groups, use this command with caution. |
The following example shows the creation of a channelized T3 interface:
Router(config)# controller T3 1/0/0 Router(config-controller)# channelized
To specify the cable length for the T3 controller, use the cablelength command.
cablelength feet[no]cablelength feet
Where 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 cablelength value is set to 40 feet.
Router(config)# controller T3 1/0/0 Router(config-controller)# cablelength 40
|
Note This command causes the system to use one of two settings for impedance matching and pulse shaping, one setting for any cable length between 0 and 249 feet and another setting for any cable length greater than 250 feet. The exact value you enter is stored in the configuration file. |
To specify a framing type for the channelized T3 controller, use the framing command.
framing [c-bit | m23 | auto-detect][no]framing [c-bit | m23 | auto-detect]
The default is auto-detect.
Use the no form of the command to return the framing type to its default.
You can instruct the CT3 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/0 Router(config-controller)# framing auto-detect
You can configure maintenance data link (MDL) messages (as defined in the ANSI T1.107a-1990 specification) on the channelized T3 interface.
|
Note MDL messages are supported only when the T3 framing is set for C-bit parity. (See the "Setting the Framing Type" section.) |
To configure MDL messages, use the mdl command.
mdl {transmit {path | idle-signal | test-signal} |
string {eic | lic | fic | unit | pfi | port | generator} id_string}
[no] mdl {transmit {path | idle-signal |
test-signal} | string {eic | lic | fic | unit | pfi | port | generator}
id_string}
Where:
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/0 Router(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 string
You can set a specific pattern to be transmitted between HDLC packets on all unconfigured timeslots that belong to a channelized T3 interface. To do so, use the idle pattern command.
idle pattern patterns[no]idle pattern patterns
Where 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 Some systems interpret marks, 0xff, as an abort signal. Therefore, flags, 0x7e, is preferred. |
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/0 Router(config-controller)# idle pattern 0x10
Router(config)# controller T3 1/0/0 Router(config-controller)# idle pattern 23
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/0 Router(config-controller)# clock source line
You can configure the T3 controller for a loopback mode using the loopback command.
loopback [local | network | remote][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 ESR Troubleshooting Guide.
Examples:
Router(config)# controller T3 1/0/0 Router(config-controller)# loopback local
Router(config)# controller T3 1/0/0 Router(config-controller)# loopback remote
Use the equipment loopback command to run loopbacks in conjunction with remote equipment.
equipment [customer | network] loopback[no]equipment [customer | network] loopback
Where:
Use the no form of the command to terminate the loopback.
For more information on the loopback command, refer to the online Cisco 10000 ESR Troubleshooting Guide.
In the following example, an equipment network loopback is configured:
Router(config)# controller T3 1/0/0 Router(config-controller)# equipment network loopback
Each channelized T3 consists of 28 T1s, each of which is divided into 24 timeslots (or DS0s). To create an interface that supports subscriber traffic, you must combine the timeslots into channel groups. Use the t1 channel-group command to create a channel group.
Channel groups have these characteristics:
Figure 5-2 illustrates channelization possibilities on the CT3 line card.
You create a logical channel group using the following command:
t1 t1-number channel-group channel-group-number timeslots
list-of-timeslots [speed {56 | 64}]
[no] t1 t1-number channel-group channel-group-number
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/0 Router(config-controller)# t1 3 channel-group 20 timeslots 1-8, 10
Router(config)# interface serial 1/0/0/3:20
Router(config)# controller t3 1/0/0 Router(config-controller)# t1 4 channel-group 18 timeslots 1-24
Router(config)# interface serial 1/0/0/4:18
Router(config)# controller t3 1/0/0 Router(config-controller)# t1 5 channel-group 19 timeslots 1-6 Router(config-controller)# t1 5 channel-group 20 timeslots 10 Router(config-controller)# t1 5 channel-group 21 timeslots 7-9, 24
Router(config)# controller T3 1/0/0 Router(config-controller)# no t1 1 channel-group 20
From controller configuration mode for a T3 interface, you can enter commands to modify aspects of a T1 interface. This section describes the commands for
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:18
You can specify the T1 interface framing format using the following command:
t1 t1-number framing {esf | sf [hdlc-idle {0x7E | 0xFF}]}
[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.
Examples:
Router(config)# controller T3 1/0/0 Router(config-controller)# t1 6 framing sf
Router(config)# controller T3 1/0/0 Router(config-controller)# t1 16 framing esf
Use the t1 yellow command to turn the detection or generation of a yellow alarm on or off.
t1 t1-number yellow {detection | generation}
[no] t1 t1-number yellow {detection | generation}
Where:
When you select SF framing for a full T1 interface (24 timeslots) 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/0 Router(config-controller)# t1 1 yellow detection
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/0 Router(config-controller)# t1 1 clock source line
You can enable 1-second transmissions of performance reports through the facility data link (FDL) according to the specification ANSI T1.403, on both ends of the T1 connection. To do so, use the following command:
t1 t1-number fdl ansi [no] t1 t1-number fdl ansi
Where t1-number is T1 interface 1 to 28.
Use the no form of the command to disable this feature.
|
Note You can use this command only when the T1 framing is ESF. |
In the following example, FDL is enabled:
Router(config)# controller t3 1/0/0 Router(config-controller)# t1 2 fdl ansi
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:
t1 t1-number bert pattern pattern interval time [unframed] [no] t1 t1-number bert
Where:
|
Note For each T3, you can run only one BER test at a time. |
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 ESR Troubleshooting Guide.
Examples:
Router(config)# controller T3 1/0/0 Router(config-controller)# t1 10 bert pattern 2^20 interval 5 unframed
Router(config)# controller T3 1/0/0 Router(config-controller)# t1 10 bert pattern 1s interval 14400 unframed
If problems occur when you configure a T1 interface, you can troubleshoot the line card by using the following command from controller configuration mode:
t1 t1-number loopback [local | network {line | payload} | remote [line
[fdl {ansi | bellcore} | inband] | payload [fdl | ansi]]]
[no] t1 t1-number loopback
Where:
Use the no form of the command to terminate a loopback.
For more information on this command, refer to the online Cisco 10000 ESR Troubleshooting Guide.
Examples:
Router(config)# controller t3 1/0/0 Router(config-controller)# t1 1 loopback local
Router(config)# controller t3 1/0/0 Router(config-controller)# t1 1 loopback remote line fdl ansi
Posted: Tue Oct 3 09:43:07 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.