|
This chapter describes the commands related to trunks. The contents in this chapter are as follows:
After you configure the node, the trunks need configuration. Trunks are inter-node links in a network. A trunk can connect any combination of IPX, IGX 8400 series, or BPX 8620 nodes. (the trunk connecting the MGX 8220 with the BPX 8620 is described in the MGX 8220 documentation.) Trunk characteristics are:
· Physical line type: | T1 (including fractional), E1 (including fractional), Subrate, E3, T3, OC12 (STM4), or OC3 (STM1). |
· Communication technology: | Asynchronous Transfer Mode (ATM) or FastPackets. |
Table 5-1 shows the card combinations and line types for each type of node.
Node Type | Front Card | Back Card | Line Types | Technology |
---|---|---|---|---|
IPX | NTC | BC-T1 | T1, T1 Fractional | FastPacket |
IGX 8400 series | NTM | BC-T1 | T1, T1 Fractional | FastPacket |
IPX | NTC | BC-E1 | E1, E1 Fractional | FastPacket |
IGX 8400 series | NTM | BC-E1 | E1, E1 Fractional | FastPacket |
IPX | NTC | BC-SR | Subrate | FastPacket |
IGX 8400 series | NTM | BC-SR | Subrate | FastPacket |
IPX | NTM | BC-Y1 | Y1 | FastPacket |
IGX 8400 series | NTM | BC-Y1 | Y1 | FastPacket |
IPX | AIT | BC-T3, BC-E3 | T3, E3 | ATM |
IGX 8400 series | ALM/B | BC-UAI-1T3, BC-UAI-1E3 | T3, E3 | ATM |
IGX 8400 series | BTM | BC-T3, BC-E3 | T3, E3 | ATM |
BPX 8620 | BNI | LM-3T3, LM-3E3 | T3, E3 | ATM |
BPX 8620 | BNI-155, | 2OC3-SMF or | OC3 (STM1) | ATM |
BPX 8620 | BXM-155-8 | MMF-155-8 | OC3 (STM1) | ATM |
BPX 8620 | BXM-155-4 | MMF-155-4 | OC3 (STM1) | ATM |
BPX 8620 | BXM-622-2 | SMF-622-2 | OC12 (STM4) | ATM |
BPX 8620 | BXM-622 | SMF-622 | OC12 (STM4) | ATM |
Before you execute the commands in this chapter, node setup must be complete (see the chapter titled "Setting Up Network Nodes"). Also, be sure the front and back cards that support the proposed trunk type and communication technology reside in the slot you want for the trunk. You can do this visually or by executing the dspcds command.
1. Use uptrk to activate ("up") a trunk. The uptrk command activates the card set and starts frame generation. If the front card is a BXM, executing uptrk indicates to the BXM that it is supporting a trunk. The uptrk command also determines whether the trunk is physical-only or a virtual trunk. To identify a virtual trunk, add a third-place digit (see uptrk description).
2. Use the cnftrk command to override trunk default values. The cnftrk command is mandatory for virtual trunks but optional for physical trunks. For virtual trunks, the VPI must be changed to a non-zero value before execution of addtrk.
3. Use addtrk to add the trunk. Adding the trunk makes the trunk a usable resource, so connections can be added (addcon) for carrying traffic. Add a trunk at only one end of the trunk.
This section describes how to set up a virtual trunk using a BPX 8620 cloud. Virtual trunking is a purchased feature, so Cisco must enable it on each node you intend to use virtual trunking. Also, firmware levels on ASI and BNI cards must be current. For more information on virtual trunking, see the Cisco WAN Switching System Overview.
Step 2 For each ASI port connected to a BNI virtual trunk, use the following command sequence:
upln slot.port
upport slot.port
cnfport slot.port, and set the shift parameter to "N" for no shift.
Step 3 Execute addcon. In the cloud network, add a virtual path ASI connection for each end of the virtual trunk that is to be routed through the cloud. An example of the syntax for this is:
addcon joker 5.1.1.* swstorm 6.2.10.*
where 5.1 and 6.2 are ASI ports hooked up and configured for virtual trunking. DACS connections are acceptable. Note that the third number is the VPI, which must correspond to the virtual trunk VPI configured with cnftrk in step 4. The CBR/VBR parameter must also correspond to the Virtual Trunk Type of the virtual trunk. For T3, set PCR to 96000 and CDTV to 24000 for the connection so that the ASI does not drop cells. Cisco recommends these values based on testing.
Step 4 Configure BNI trunks. Take this step if the ATM cloud provider has assigned the VPC. On BNIs that connect to the cloud's ASI ports, configure the virtual trunks, as follows:
When you use cnftrk, make sure the virtual trunk type and VPI correspond to the existing ASI Virtual Path connections.
The parameters slot.port.vtrk on a BNI card can have the following values:
The values for slot.port.vtrk on an AIT, BTM, or ALM/B card can be:
This section describes how to change trunk parameters after the trunk has been added. After a trunk has been added, you can reconfigure some parameters without first deleting the trunk (deltrk). (See the list that follows.) All other changes to trunk parameters must follow trunk deletion. The parameters that are changeable without first deleting the trunk are:
To display the current trunk parameters, use dsptrkcnf. If you can make all the needed parameter changes without deleting the trunk, execute just cnftrk. Use cnftrk at both ends of the trunk.
To change parameters that first require trunk deletion:
Step 2 Execute cnftrk to reconfigure parameters. Use cnftrk at both ends of the trunk.
Step 3 Execute addtrk to add the trunk. Use addtrk at only one end of the trunk.
To remove a trunk:
Step 2 Use the dntrk command to down the trunk. Execute dntrk at both ends of the trunk.
The network trunk configuration can be displayed on the screen or printed on the printer in a one step process by using any one of the following commands.
ATM trunk redundancy is the T3 and E3 trunk redundancy supported by the AIT, ALM/B, and BTM cards. Redundancy can exist between either an AIT card and BNI (BPX 8620), a ALM/B and BNI, or a BTM and a BNI. Trunk redundancy cannot exist between IPXs and IGX 8400 series switches. Also, virtual trunking and trunk redundancy are incompatible. Trunk redundancy uses the standard trunk cables rather than a Y-cable. (For all service card sets other than trunk cards, redundancy is managed through the Y-cable redundancy commands addyred, delyred, prtyred, and dspyred).
Trunk redundancy depends on the applicable commands, the trunk card in the adjacent slot, and the standard trunk cable. Trunk redundancy commands execute only on the IPX or IGX 8400 series switches. The BPX 8620 does not require information regarding this feature. The following commands manage trunk redundancy:
Subrate trunks use an Interface Control Template that specifies the configuration of an output control lead. The template defines which output lead is to be configured and whether the lead is asserted, inhibited, or follows a specified input source. A template for a subrate trunk can be configured individually or copied from the template of another subrate trunk.
Subrate trunk interface control templates are managed through the following commands.
The following list shows the full name and starting page for the description of each trunk command.
Mnemonic | Description | Page |
---|---|---|
addtrk | Add trunk | |
addtrkred | Add trunk redundancy | |
cnftrk | Configure trunk | |
cnftrkalm | Configure trunk alarm | |
cnftrkict | Configure trunk interface control template | |
cpytrkict | Copy trunk interface control template | |
deltrk | Delete trunk | |
deltrkred | Delete trunk redundancy | |
dntrk | Down trunk | |
dspnw | Display network | |
dsptrkbob | Display trunk breakout box | |
dsptrkcnf | Display trunk configuration | |
dsptrkict | Display trunk interface control template | |
dsptrkred | Display trunk redundancy | |
dsptrks | Display trunks | |
dsptrkstats | Display trunk statistics | |
prtnw | Print network | |
prttrkict | Print trunk interface control template | |
prttrks | Print trunks | |
uptrk | Up trunk |
Adds a trunk between nodes. A trunk must be added to the network before it can carry traffic. Executing addtrk is necessary at only one of the nodes terminating the trunk. Before you add a trunk to the network, you must have activated (or "upped") the trunk at both ends by using uptrk.
A trunk must be free of major alarms before you can add it. If you use addtrk to join two networks that were previously separate, the local node verifies that all node names in both networks are unique before it adds the trunk.
A trunk cannot be added while any of the following conditions are true:
When using the addtrk command, exercise caution when you add a new node to a network or one network to another network. With these particular operations, the user IDs and passwords may be replaced by those in the other network, so consult Cisco Customer Service first.
Add trunk
addtrk <slot.port>[.vtrk]
deltrk, dsptrks, uptrk
Privilege | 1 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | Yes |
addtrk 7
Add trunk between node beta, slot 7 and node alpha, slot 10.
beta TRM YourID:1 IPX 32 8.4 Mar. 3 1996 15:04 MST
PLN Type Current Line Alarm Status Other End
7 E1/32 Clear - Line OK alpha.10
9 T1/24 Clear - Line OK gamma.10
13 T1/24 Clear - Line OK alpha.14
15 T1/24 Clear - Line OK gamma.15
20 T3/3 Major - AIT Missing -
Last Command: addtrk 7
Next Command:
Parameter | Description |
---|---|
slot.port | Specifies the slot and port number of the trunk to add. |
Parameter | Description |
---|---|
vtrk | Specifies the virtual trunk number. The maximum on a node is 32. The maximum on a T3 or E3 line is 32. The maximum on an OC3/STM1 line is 11. |
Configures trunk redundancy on an ATM trunk. The addtrkred command specifies a backup trunk to the primary trunk. Applicable line types are T3 and E3. This redundancy scheme requires two sets of ATM trunk cards and two T3 or E3 cables. Note the following characteristics of trunk redundancy:
Trunk redundancy is not compatible with virtual trunking.
Add trunk redundancy
addtrkred <primary trunk> <secondary trunk>
deltrkred, dsptrkred
Privilege | 1-4 |
Jobs | No |
Log | Yes |
Node | IPX, IGX 8400 series |
Lock | Yes |
addtrkred 4 5
Add bandwidth redundancy for the primary ATM trunk in slot 4 with backup from the ATM trunk in slot 5.
beta TRM YourID:1 IPX 32 8.4 Mar. 3 1996 15:15 MST
ATM Line Backup ATM Line
4 5
Last Command: addtrkred 4 5
Next Command:
Parameter | Description |
---|---|
primary trunk | Specifies the slot number of the primary trunk card set. |
secondary trunk | Specifies the slot number of the secondary trunk card set as backup. |
Configures trunk parameters. A trunk has a default configuration after you activate (or "up") the trunk with the uptrk command. Beyond this default configuration, cnftrk lets you configure trunk parameters. Normally, you use cnftrk after you have upped the trunk (uptrk) but before you have added it to the network with addtrk. You must execute cnftrk at both ends of a trunk.
The section "cnftrk-Parameters" in this description shows required cnftrk parameters. Virtual trunk parameters are in the section titled "cnftrk-Optional Parameters." You can reconfigure some parameters after adding a trunk with addtrk. See the section "Reconfiguring a Trunk ."
In the cnftrk display, the current value for each parameter appears on screen. At the command line prompt for each parameter, the current or default value appears in parentheses and stays the same if you press Return without typing any characters. Configurable parameters depend on the trunk type. For example, an NTM and BNI support different parameters. If a parameter is not available for the current interface, its name appears at half-intensity, and the value field contains dashes. (Note that Clock Rate is a required parameter for only HSSI. The Clock Rate range is 4 Mbps-50.84 Mbps. The actual clock limits depend on the front card.)
The parameters RCV Trunk Rate and Transmit Trunk Rate apply to physical ATM trunks on an IPX or IGX 8400 series node. On a BPX 8620 node, only Transmit Trunk Rate is available. These parameters let you configure lower rates than the maximum line rate for the trunk type. If you adjust a rate, do so at both ends of the trunk. For example, if RCV Trunk Rate on an IGX is 40,000 packets per second (pps), Transmit Trunk Rate on the far end must be 20,000 cells per second (cps).
For ATM trunks terminating on an AIT (IPX) or a BTM (IGX 8400 series), make sure the receive rate is below the maximum of the T3 or E3 line rate. For these cards, the rate should be no more than 40,000 packets per second. (On an IPX, the reason for reducing the rate is to prevent the MUXBUS from becoming overloaded. Furthermore, the rate should be even less if large numbers of T1 or E1 trunks exist on the same IPX.) Increments for RCV Trunk Rate and Transmit Trunk Rate can be as small as 1 cell or packet per second. (Note that the node may round up or round down the value you enter.)
The default value for Transmit Trunk Rate is the maximum rate for the back card type. You can reduce this rate to any number of cells per second that is less than or equal to the physical port rate. If E3 or T2 is selected, the bandwidth is reduced from the T3 rate.
The implementation of Transmit Trunk Rate on a virtual trunk differs from the implementation on a physical trunk. On a physical trunk, Transmit Trunk Rate limits the rate at which the back card physically generates cells. For a virtual trunk, Transmit Trunk Rate does not limit the rate at which the back card generates cells: the line rate stays at the maximum for the line type. However, Transmit Trunk Rate is the maximum transmission rate allowed on a virtual trunk.
The provider of the virtual trunk service assigns the value for Transmit Trunk Rate. You must have this provider-assigned value for Transmit Trunk Rate and enter it when you use cnftrk.
For FastPacket trunks, which the NTC and NTM front cards support, the Subrate interface and Subrate data rate fields are configurable only if the back card is a BC-SR. The interface types for a subrate trunk are V.11, X.21, V.35, and RS449. Set the data rate to match the subrate facility within the range 64 Kbps-1.920 Mbps.
The DS-0 map is used to define fractional E1 and T1 trunks. It consists of a repeating set of specifications in the form <x[-y[a]]>, where "x" and the optional "y" are DS-0 numbers 0-23, and the optional "a" indicates alternating. The value of "y" must be greater than the value of "x." The values of both "x" and "y" cannot be less than 0 or greater than the maximum number of DS-0s for the line type. In the DS-0 map for unframed E1, use 0-31. For framed E1, use 1-31. For 30 DS-0 E1, use 1-15, 17-31.
Configure trunk
cnftrk <slot.port>[.vtrk] <options for E1 | T1 | E3 | T3 | OC3 | OC12 | E2 | HSSI | SR >
addtrk, dsptrkcnf
Privilege | 1 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | Yes |
cnftrk 11
Configure trunk 11. The trunk in slot 11 is an ATM T3 trunk on an ALM/B. (If you want to verify the card is the trunk version of the ALM, use either dspcd or dspcds and check the front card "Rev." An ALM/B shows a
the first character in the Rev column.)
IGX16 TN SuperUser IGX 16 8.4 Dec. 5 1996 16:38 PST
PLN 11 Config T3/576 [192000pps] ALM slot: 11
Clock Rate: -- Idle code: 7F hex
Transmit Trunk Rate: 96000 cps Restrict PCC traffic: No
Rcv Trunk Rate: 192000 pps Link type: Terrestrial
Subrate interface: -- Line framing: --
Subrate data rate: -- coding: --
Line DS-0 map: -- CRC: --
Pass sync: Yes recv impedance: --
Loop clock: No cable type:
Statistical Reserve: 992 pps length: 0-225 ft.
Header Type: STI HCS Masking: Yes
Gateway Type: BAM Payload Scramble: No
VPI Address: 0 End supp BData: Yes
VCI Address: 0 End supp FST: Yes
Last Command: cnftrk 11
Next Command:
cnftrk 1.1
Configure trunk 1.1. This trunk is an ATM T3 trunk on a BPX 8620.
batman TN SuperUser BPX 15 8.4 Date/Time Not Set
TRK 1.1 Config T3 [96000 cps] BNI-T3 slot: 1
Restrict CC traffic: No
Transmit Rate: 96000 Link type: Terrestrial
Subrate interface: -- Line framing: --
Subrate data rate: -- coding: --
Line DS-0 map: -- CRC: --
Pass sync: Yes recv impedance: --
Loop clock: No cable type:
Statistical Reserve: 992 cps length: 0-225 ft.
Idle code: 7F hex HCS Masking: Yes
Connection Channels: 1771 Payload Scramble: No
Valid Traffic Classes: Frame Scramble: --
V,TS,NTS,FR,FST,CBR,VBR,ABR Virtual Trunk Type: --
SVC Channels: 0 Virtual Trunk VPI: --
SVC Bandwidth: 0 cps Virtual Trunk Service: --
This Command: cnftrk 1.1
Transmit Rate [T2=14490, E3=80000, T3=96000, OC3 = 353208](96000):
cnftrk 13.1.1
Configure trunk 13.1.1 (a virtual trunk on an ATM T3).
sw97 TN SuperUser BPX 15 8.4 July 30 1996 11:45 GMT
TRK 13.1.1 Config T3 [2867 cps] BNI-T3 slot: 13
Restrict CC traffic: No
Transmit Rate: 3000 Link type: Terrestrial
Subrate interface: -- Line framing: --
Subrate data rate: -- coding: --
Line DS-0 map: -- CRC: --
Pass sync: No recv impedance: --
Loop clock: No cable type:
Statistical Reserve: 992 cps length: 0-225 ft.
Idle code: 7F hex HCS Masking: Yes
Connection Channels: 55 Payload Scramble: No
Valid Traffic Classes: Frame Scramble: --
V,TS,NTS,FR,FST,CBR,VBR,ABR Virtual Trunk Type: CBR
Virtual Trunk VPI: 0
Virtual Trunk Service: 4
Last Command: cnftrk 13.1.1 3000 N N 992 7F 55 V,TS,NTS,FR,FST,CBR,VBR,ABR N TER
RESTRIAL 0 Y N CBR 0
Next Command:
Trunk Option | Type | Description | Possible Entries | Default |
---|---|---|---|---|
slot.port | All | The number of the trunk to configure. | Any valid slot and port. For cards with one port, use slot. | N/A |
Trunk Identification (display onlynot configurable) | All | Displays trunk number, trunk type and bandwidth supplied, and the card type and slot number of the unit supporting the trunk. | T3, E3, T1, E1, fractional T1, fractional E1 subrate, ATM, NTC, NTM, OC3, STM1, OC12, STM4. | none |
Clock Rate | ATM | Clock rate applies to only HSSI. | 4 Mbps-50.84Mbps |
|
Receive Trunk Rate | ATM | CELLBUS or MUXBUS bandwidth in packets per second (pps) for a BTM, ALM/B, or AIT. Not used on BPX 8620. | 0-192,000 pps for ALM/B 0-80,000 pps for BTM (IGX 8400 series) or AIT (IPX) cards | 1000
|
Transmit Trunk Rate | ATM | Maximum transmit rate in cells per second (cps) over a trunk. Note that defaults for virtual trunks are 1/32 | 0-96000 cps for T3 | 96000 for T3 |
Subrate interface | PKT | Subrate physical interface type | X.21 | V.35 | X.21 |
Subrate data rate | PKT | Subrate data rate (Kbps) | 64-1920 | 1920 |
DS-0 map | PKT | DS-0s to use for a fractional T1 bundle. Optional "a" = "use alternating channels." | x - y[a] | 0-31 (E1) 0-23 (T1) |
Pass sync | All | Enables the trunk to pass a clock for network synchronization. | Yes | No | Yes for standard, no for virtual trunks |
Loop Clock | All | Loop the receive clock back to transmit. | Yes | No | No |
Statistical | All | This trunk bandwidth is reserved for non-standard traffic, such as internode controller messages or user-traffic diverted because of a failure. | 0-10666 FastPackets 0-353298 for OC3 | 600 for FastPackets |
Header Type | ATM | Specifies the cell header type: UNI, NNI, or STI. See Cisco WAN Switching System Overview for a description. | UNI | NNI | STI A UXM trunk uses NNI only. | NNI for UXM, STI for all others |
Gateway Type | ATM | Specifies the addressing mode. See the Cisco WAN Switching System Overview for a description. | BPX 8620 - BPX 8620 (BAM) | BAM |
VPI Address | ATM | Virtual path address in ATM cell. Must be non-0 for a virtual trunk. | 0-255 | 0 |
VCI Address | ATM | Virtual circuit address in ATM cell. | 0-65,535 | 0 |
Idle code | All | HEX code either in the payload space of an ATM idle cell or on an idle FastPacket trunk (idle packets do not exist) | 0-ff (hex) | 54 (E1) |
SVC Channels | ATM | The number of channels reserved for SVCs. | T3: 0-1771 E3: 0-1771 OC3: 0-16199 | 0 |
SVC Bandwidth | ATM | The bandwidth reserved for SVCs. | T3: 96000 cps E3: 80000 cps OC3: 353208 cps | 0 |
Restrict CC traffic (requires super user privilege) | All | Restrict node controller messages from | Y | N | No |
Link type | All | Terrestrial or Satellite link.Link Type applies to configuring a route so it can "avoid satellite." | T | S | T |
Line framing | PKT | T1 line framing | D4 | ESF | D4 |
Line coding | PKT | E1 line coding | HDB3 | AMI | HDB3 |
Line CRC | PKT | E1 CRC-4 | Yes | No | No |
Recv impedance | PKT | E1 receive impedance | 1 = 75W unbalanced | 1 |
Cable type and | PKT | Length and type of cable for a trunk. Designates the software configurable line build-out to match the cable length from the IPX or IGX 8400 series to the DSX cross-connect. | 1 = 0-220' MAT | 4 |
HCS Masking | ATM | Mask the ATM cell header checksum to disable error checking. HCS Masking applies to E3, OC3, OC12. | Yes | No | Yes |
Payload Scramble | ATM | Scramble the cell payload. | Yes | No | Yes for BNI-E3 |
End supp BData | All | Indicates whether the far end of a trunk supports bursty, frame relay data. | Yes | No | No |
End supp FST | All | Indicates whether the far end of the trunk supports ForeSight for frame relay. | Yes | No | No |
Gateway | ATM | How many FastPackets to put into an ATM cell. Does not apply to BNI. | 1 | 2 | 3 | 2 |
Virtual Trunk Parameter | Type | Description | Possible Entries | Default |
---|---|---|---|---|
Connection Channels | BNI | The maximum number of connection channels per trunk. All virtual trunks on the port share this total. The number of connections added to the port cannot exceed the number of connection channels configured for the port. | BNI-T3/E3: max 1771 BNI-OC3: max 15867 | BNI-T3/E3: 1771 BNI-OC3: 15867
For Virtual Trunks: BNI-T3/E3: 55 BNI-OC3: 1442 |
Valid Traffic Classes | BNI | The valid types of traffic for a virtual trunk. The recommended traffic classes for each virtual trunk types: | Vvoice |
|
Virtual Trunk Type | BNI | This choice usually comes from the carrier that provides the ATM cloud. | CBR, VBR, ABR | CBR |
Virtual Trunk VPI | BNI | Virtual Trunks must be configured to have a greater-than-0 VPI before connections are added by addcon. This value usually comes from the carrier that provides the ATM cloud. | 1-255 for T3/E3 1-63 for OC3 (STM1) |
|
Configures alarm reporting for a trunk. When a trunk is upped and added to the network, alarm reporting is enabled, but cnftrkalm lets you disable alarms on upped trunks. Disabling alarms can be useful when a trunk is connected to a node but not yet in service or when a trunk has occasional bursts of errors but still functions.
Configure trunk alarms
cnftrkalm <slot.port>[.vtrk] <e | d>
dspalms, dsptrks
Privilege | 1-5 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | Yes |
cnftrkalm 7 d
Disable trunk alarms on trunk 7
beta TRM YourID:1 IPX 32 8.4 Mar. 3 1996 15:21 MST
PLN Type Current Line Alarm Status Other End
7 E1/32 Clear - Line OK alpha.10
9 T1/24 Clear - Line OK gamma.10
13 T1/24 Clear - Line OK alpha.14
15 T1/24 Clear - Line OK gamma.15
20 T3/3 Major - AIT Missing -
Last Command: cnftrkalm 7 d
Next Command:
Parameter | Description |
---|---|
slot.port | Specifies the trunk number. |
e | Enables the alarm. |
d | Disables the alarm. |
Parameter | Description |
---|---|
vtrk | Specifies the virtual trunk number. |
Configures the output lines of an interface control template for a subrate trunk. Table 5-10 lists the configurable signals:
Interface Type | Output Signal | Inputs |
---|---|---|
X.21 | C, I |
|
V.35 | RTS, DTR | CTS, DSR |
MIL-188 | IS, LL, RL, RS, SF, SS, TR | DM, CS |
Configure trunk interface control template
cnftrkict <line> <output> <source>
dsptrkict, prttrkict
Privilege | 1-2 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX 8400 series |
Lock | Yes |
cnftrkict 9 c on
Configure output lead "c" as "on" in the interface control template for subrate trunk 9.
beta TRM YourID:1 IPX 32 8.4 Mar. 3 1996 15:15 MST
Packet Line: 9
Interface: X.21 DTE
Interface Control Template for Trunk Line
Lead Output Value Lead Output Value
C/DTR ON
Last Command: cnftrkict 9 c on
Next Command:
Parameter | Description | |
---|---|---|
line | Specifies the trunk whose interface control template is to be configured. | |
output | Specifies the output lead to be configured. Configurable output leads vary depending on the type of data interface (X.21, V.35, or MIL-188) used. | |
source | Specifies how the specified output lead is to be configured. The options are as follows:
Input leads vary depending on the type of data interface (X.21, V.35, or MIL-188) supported. |
Copies the interface control template of one trunk to another trunk. Once copied, the control information can be edited with the cnftrkict command. See the cnftrkict description for more information on configuring the trunk interface control templates.
Copy trunk interface control template
cpytrkict <source_trunk> <destination_trunk>
cnftrkict, dsptrkict
Privilege | 1-2 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX 8400 series |
Lock | Yes |
cpytrkict 9 11
Copy the interface control template for trunk 9 to trunk 11.
beta TRM YourID:1 IPX 32 8.4 Mar. 3 1996 15:15 MST
Packet Line: 9
Interface: X.21 DTE
Interface Control Template for Trunk Line
Lead Output Value Lead Output Value
C/DTR ON
Last Command: cpytrkict 9 11
Enter destination line number:
Parameter | Description |
---|---|
source trunk | Specifies the trunk number of the interface control template information to be copied. |
destination trunk | Specifies the trunk number to which the interface control template information will be copied. |
Deletes a trunk. Because deleting a trunk removes the communication path between two nodes, using deltrk may split a network into two separate networks. If deltrk execution splits the network, deletion of the connections that were using the deleted trunk also occurs.
If both nodes on the trunk are reachable, executing deltrk is necessary on only one node. If a trunk is deleted on a node while the node at the other end is unreachable, the unreachable node does not detect the deletion, so be sure to delete the trunk at both nodes in this case.
After you delete a trunk, it still carries framing signals but no traffic. Also, the trunk can generate alarms for counting. To remove a trunk completely, use dntrk after the deltrk command.
In the following situations, the node does not allow deltrk to execute:
Delete trunk from a network
deltrk <slot.port>[.vtrk]
addtrk, dntrk, dspnw, dsptrks uptrk
Privilege | 1 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | Yes |
deltrk 7
Delete trunk 7 from the network.
beta TRM YourID:1 IPX 32 8.4 Mar. 15 1996 15:02 MST
PLN Type Current Line Alarm Status Other End
7 E1/32 Clear - Line OK -
9 T1/24 Clear - Line OK gamma.10
13 T1/24 Clear - Line OK alpha.14
15 T1/24 Clear - Line OK gamma.15
20 T3/3 AIT - AIT Missing -
Last Command: deltrk 7
Next Command:
Parameter | Description |
---|---|
slot.port | Specifies the physical trunk number. |
Parameter | Description |
---|---|
vtrk | Specifies the virtual trunk portion of the trunk identifier. |
Removes redundancy from an ALM/B, BTM, or AIT trunk. After you execute deltrkrd, you can remove the backup card without causing an alarm.
Delete ATM trunk redundancy
deltrkred <backup ATM trunk number>
addtrkred, dsptrkred
Privilege | 1-4 |
Jobs | No |
Log | Yes |
Node | IPX, IGX 8400 series |
Lock | Yes |
deltrkred 5
Remove ATM trunk redundancy for the card set in slot 5.
beta TRM YourID:1 IPX 32 8.4 Mar. 15 1996 15:15 MST
ATM Line Backup ATM Line
7 8
Last Command: deltrkred 5
Next Command:
Parameter | Description |
---|---|
Backup trunk number | Specifies of the ATM card set assigned as the backup. |
Downs a trunk, after which it no longer carries framing or statistics. Before you can down a trunk with dntrk, you must remove it must from the network with deltrk (or delshelf in a tiered network).
Down trunk
dntrk <slot.port>[.vtrk]
addtrk, deltrk, uptrk, dsptrks
Privilege | 1-2 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | Yes |
dntrk 9
Deactivate trunk 9.
beta TRM YourID:1 IPX 32 8.4 Mar. 3 1996 10:53 MST
From Type Current Line Alarm Status Other End
13 T1/24 Clear - Line OK alpha.14
15 T1/24 Clear - Line OK gamma.15
20 T3/3 Major - AIT Missing -
Last Command: dntrk 9
Next Command:
Parameter | Description |
---|---|
slot.port | Specifies the physical trunk. |
Parameter | Description |
---|---|
vtrk | Specifies a virtual trunk number (applies to BNI only). T3/E3 range is 1-32. OC3 range is 1-11. |
Displays the network topology in tabular form. Alarms appear in a column, and added trunks (by addtrk) appear to the right to the node name. Each trunk entry shows the local back card slot number and the node name and back card slot number on the other end of the line. Note the following conventions:
If the network has more nodes and trunk connections than are currently on the screen, a "Continue?" prompt appears. Press the Return key to display other parameters, or enter "n" to exit the command.
Display network
dspnw [+b | -b] [+z | -z]
dspnds, prtnw
Privilege | 1-6 |
Jobs | No |
Log | No |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | No |
dspnw
Display the network topology in tabular form.
sw91 TN SuperUser IPX 8 8.4 Nov. 13 1996 16:06 GMT
NodeName Alarm Packet Line
sw92 UNRCH
8-7/sw91
sw200 UNRCH
14-14/sw201 15-15/sw201 16-16/sw201
sw201 UNRCH
14-14/sw200 15-15/sw200 16-16/sw200
12.1-4.5/sw26
sw12 MAJOR
3.1.2-4.7/sw26 3.1.3-6.3/sw91
sw91 MAJOR
7-8/sw92 6.3-3.1.3/sw12 6.4-3.1.4/sw68
sw68 Minor
3.1.4-6.4/sw91
This Command: dspnw
Continue?
The display shows a network containing the nodes alpha, beta, and gamma. The word "Major" on the right of "gamma" and "beta" (see Alarm column) indicates the existence of alarm conditions such as loss of signal.
The "10-9/beta" listed to the right of node gamma indicates that trunk 10 on node gamma connects to node beta as trunk 9. The "7-10/alpha" listed to the right of node beta indicates that trunk 7 on node beta connects to node alpha as trunk 10. If the two trunk numbers are separated by an tilde (~) in place of a dash (-), the display is indicating a satellite. The following illustrates a map of this network.
Parameter | Description |
---|---|
+b | Display only the lines that support bursty data. |
-b | Display only the lines that do no support bursty data. |
+z | Display only the lines that use ZCS encoding. |
-z | Display only the lines that do not use ZCS encoding. |
Displays the state of all inputs from subrate line equipment to an IPX or IGX 8400 series and the state of all outputs from the node to the subrate line equipment. Display updates can occur at an optional, user-specified interval. Otherwise, the display remains on-screen until Delete is pressed or the display times out. The default interval for updating the display is every 5 seconds. If a trunk is disabled, its number appears in dim, reverse video. See cnftrkict for configuration details.
Display trunk breakout box
dsptrkbob <line> [interval]
cnftrkict, dsptrkict
Privilege | 1-6 |
Jobs | No |
Log | No |
Node | IPX, IGX 8400 series |
Lock | Yes |
dsptrkbob 9
Display the breakout for subrate trunk 9.
beta TRM YourID:1 IPX 32 8.4 April 15 1996 15:15 MST
Packet Line: 9
Interfaces: X.21 DTE
Inputs from Line Equipment Outputs to Line Equipment
Lead Pin State Lead Pin State Lead Pin State Lead Pin State
RxD 4/11 Idle TxD 2/9 Active
I/DSR 5/12 On C/DTR 3/10 On
S/RxC 6/13 Active
Last Command: dsptrkbob 9
Hit DEL key to quit:
Parameter | Description |
---|---|
trunk | Specifies the subrate trunk. |
Parameter | Description |
---|---|
interval | The number of seconds between updates of the breakout box display. The range is 1-60. |
Displays trunk configuration. The parameter values that dsptrkcnf displays have been set with cnftrk or are default values.
Display trunk configuration
dsptrkcnf <slot.port>[.vtrk]
cnftrk
Privilege | 1-6 |
Jobs | No |
Log | No |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | No |
dsptrkcnf 3.1
Display the configuration for trunk 3.2.
svcbpx1 TN SuperUser BPX 15 8.4.0F June 19 1997 15:30 GMT
TRK 3.1 Config OC3 [304301cps] BXM slot: 3
Transmit Rate: 353208 Line framing: STS-3C
Subrate interface: -- coding: --
Subrate data rate: -- CRC: --
Line DS-0 map: -- recv impedance: --
Statistical Reserve: 1000 cps cable type: --
Idle code: 7F hex length: --
Max Channels/Port: 256 Pass sync: Yes
Connection Channels: 256 Loop clock: No
Valid Traffic Classes: HCS Masking: Yes
V,TS,NTS,FR,FST,CBR,VBR,ABR Payload Scramble: Yes
SVC Channels: 1000 Frame Scramble: Yes
SVC Bandwidth: 300000 cps Virtual Trunk Type: --
Restrict CC traffic: No Virtual Trunk VPI: --
Link type: Terrestrial Deroute delay time: 0 seconds
Last Command: dspport
Next Command:
dsptrkcnf 11
Display the configuration for the E3 trunk in slot 11 (an ALM/B trunk).
IGX16 TN SuperUser IGX 16 8.4 Jan. 23 1997 02:08 GMT
PLN 11 Config E3/480 [160000pps] ALM slot: 11
Clock Rate: -- Idle code: 7F hex
Transmit Trunk Rate: 80000 cps Restrict PCC traffic: No
Rcv Trunk Rate: 160000 pps Link type: Terrestrial
Subrate interface: -- Line framing: --
Subrate data rate: -- coding: --
Line DS-0 map: -- CRC: --
Pass sync: Yes recv impedance: --
Loop clock: No cable type:
Statistical Reserve: 992 pps length: 0-225 ft.
Header Type: STI HCS Masking: Yes
Gateway Type: BAM Payload Scramble: No
VPI Address: 0 End supp BData: Yes
VCI Address: 0 End supp FST: Yes
Last Command: dsptrkcnf 11
Next Command:
dsptrkcnf 13.3.1
Display the configuration for virtual trunk 13.3.1. The trunk is on a BNI-T3 card set in a BPX 8620.
sw97 TN SuperUser BPX 15 8.4 June 22 1996 07:34 GMT
TRK 13.3.1 Config T3 [2867 cps] BNI-T3 slot: 13
Restrict CC traffic: No
Transmit Rate: 3000 Link type: Terrestrial
Subrate interface: -- Line framing: --
Subrate data rate: -- coding: --
Line DS-0 map: -- CRC: --
Pass sync: No recv impedance: --
Loop clock: No cable type:
Statistical Reserve: 992 cps length: 0-225 ft.
Idle code: 7F hex HCS Masking: Yes
Connection Channels: 55 Payload Scramble: No
Valid Traffic Classes: Frame Scramble: --
V,TS,NTS,FR,FST,CBR,VBR,ABR Virtual Trunk Type: CBR
Virtual Trunk VPI: 1
Virtual Trunk Service: 3
Last Command: dsptrkcnf 13.3.1
Next Command:
Parameter | Description |
---|---|
slot.port | Specifies the physical slot and port number of the trunk. |
Parameter | Description |
---|---|
vtrk | Specifies the virtual trunk number. The maximum value on a node is 32. The maximum on a T3 or E3 line is 32. The maximum for user traffic on an OC3/STM1 trunk is 11. (See also the section called "Setting Up a Virtual Trunk " at the front of this chapter.) |
Displays interface control information for the subrate trunks. The displayed information includes:
To see a list of configurable outputs, and information on how to configure an output, see the cnftrkict command. Disabled trunks have their trunk number displayed in dim, reverse video on the screen.
Display trunk interface control templates
dsptrkict <line>
cnftrkict, prttrkict
Privilege | 1-2 |
Jobs | No |
Log | No |
Node | IPX, IGX 8400 series |
Lock | No |
dsptrkict 9
Display subrate for the trunk 9 interface control template.
beta TRM YourID:1 IPX 32 8.4 Mar. 15 1996 15:15 MST
Packet Line: 9
Interface: X.21 DTE
Interface Control Template for Trunk Line
Lead Output Value Lead Output Value
C/DTR ON
Last Command: dsptrkict 9
Next Command:
Displays the backup and primary cards for a trunk.
Display ATM trunk redundancy
dsptrkred [trunk]
addtrkred, deltrkred
Privilege | 1-4 |
Jobs | No |
Log | No |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | No |
dsptrkred
Display all ATM trunks with redundancy.
beta TRM YourID:1 IPX 32 8.4 Mar. 15 1996 15:15 MST
ATM Line Backup ATM Line
4 5
7 8
Last Command: dsptrkred
Next Command:
Parameter | Description |
---|---|
ATM trunk number | Specifies the slot number of the primary or backup ATM card set to display. Without this optional entry, the screen displays all primary and backup ATM trunks. |
Displays basic trunk information for all trunks on a node. This command applies to both physical only and virtual trunks. The displayed information consists of:
In addition, for trunks that have been added to the network with the addtrk command, the information includes the node name and trunk number at the other end. Trunks that have a "-" in the Other End column have been upped with uptrk but not yet added on both ends with addtrk. For disabled trunks, the trunk numbers appear in reverse video on the screen.
Display trunks
dsptrks
addtrk, deltrk, dntrk, dsptrks, uptrk
Privilege | 1-6 |
Jobs | No |
Log | No |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | No |
dsptrks
Display information on the trunk configuration and alarm status for the trunks at a node. The trunk numbers with three places represent virtual trunks.
sw53 TN SuperUser BPX 15 8.4 April 24 1996 23:03 GMT
TRK Type Current Line Alarm Status Other End
1.1 T3 Clear - OK sw89(IPX/AF)
1.2 T3 Clear - OK -
1.3 T3 Clear - OK -
2.1.1 OC3 Clear - OK -
3.1 T3 Clear - OK sw92(IPX/AF)
3.2 T3 Clear - OK sw91(IPX/AF)
3.3 T3 Clear - OK sw90(IPX/AF)
4.1 T3 Clear - OK sw24(IPX/AF)
4.2 T3 Clear - OK swstorm/1.1
4.3 T3 Clear - OK sw25(IPX/AF)
13.1 T3(E3) Clear - OK -
13.2.1 T3 Clear - OK -
13.2.2 T3 Clear - OK -
13.2.3 T3 Clear - OK -
Last Command: dsptrks
Next Command:
Displays the trunk port status, ATM cell loss counts, cell payload errors, and cell header errors for the specified trunk port. Table 5-24 lists the other statistics. By including the optional clear parameter, dsptrkstats execution clears these statistics.
Statistic | Description |
---|---|
Cells dropped due to BFrame parity error. | A parity error was detected in one or more of the P bits in the BFrame header or in the BIP-16 parity check for the header, which caused the cell to be dropped. |
Cell header mismatch error count. | A count of cells arrived on this trunk with an incorrect header address for the card. |
First mismatch cell header VPI/VCI. | This displays the VPI/VCI address of the first header mismatch to be received by the card in this slot.port. |
BFrame cell data payload error. | A separate BIP-16 parity check is used for the payload data. This number represents the number of errors detected by this parity check. This does not necessarily cause a cell to be dropped. |
BFrame cell loss due to admin access. | Internal to the BNI card is an administrative processor. This statistic is a count of the cells that were lost in an internal administrative shuffle. |
Display trunks statistics
dsptrkstats <slot.port> [clear]
cnftrkstats, dsptrkerrs
Privilege | 1-6 |
Jobs | No |
Log | No |
Node | BPX 8620 |
Lock | Yes |
dsptrkstats 1.1
Display cell statistics for the trunk at 1.1.
sw53 TN SuperUser BPX 15 8.4 April 24 1996 23:07 GMT
Trunk 1.1 Status: Clear - OK Cleared: 04/24/96 17:31:16
Type Count
Cells dropped due to BFrame parity err 0
Cell header mismatch error count 0
BFrame cell data payload error 0
BFrame cell loss due to disabled chan 0
BFrame cell count(TX) 8316 non-hipri cells - 52
BFrame cell count(RX) 12452
First mismatch cell masked VPI/VCI 0
First mismatch cell full VPI/VCI 0
Last Command: dsptrkstats 1.1
Next Command:
Parameter | Description |
---|---|
slot.port | Specifies the physical part of the logical trunk number. |
Parameter | Description |
---|---|
clear | Directs the system to clear the statistics counters. |
Prints the network topology table. Alarms print in a column, and added trunks (by addtrk) appear to the right to the node name. Each trunk entry shows the local back card slot number and the node name and back card slot number on the other end of the line. Note the following conventions:
Parameters set Zero Coded Suppression (ZCS) display characteristics. ZCS writes a 1 over the least significant bit of any byte that contains 0s. The purpose is to ensure a minimum occurrence of 1s so that the receiving node can extract timing information. Command uses the same syntax, and prints the same information as is displayed using the dspnw command.
Print network
prtnw [+b | -b] [+z | -z]
dspnw
Privilege | 1-6 |
Jobs | Yes |
Log | No |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | Yes |
prtnw
Print the network topology.
(No screen display, just a printout.)
Parameter | Description |
---|---|
+b | Display only the lines that support bursty data. |
-b | Display only the lines that do no support bursty data. |
+z | Display only the lines that use ZCS encoding. |
-z | Display only the lines that do not use ZCS encoding. |
Prints the interface control template of a subrate trunk. For a list of configurable outputs and configuration steps, see the cnftrkict description. The printed information includes:
Print trunk interface control template
prttrkict <line>
dsptrkict
Privilege | 1-2 |
Jobs | Yes |
Log | No |
Node | IPX, IGX 8400 series |
Lock | Yes |
prttrkict
Print network topology.
(No screen display, just a printout.)
Parameter | Description |
---|---|
line | Specifies the trunk interface control template. |
Prints the trunk configuration for the node. This command uses the same syntax and prints the same information as the dsptrks command. Configuration information for trunks includes the trunk number and the type of line (T3, E3, and so on). For trunks that have been added to the network with the addtrk command, the configuration information also includes the node name and trunk number at the other end of the line.
Note the following printout characteristics:
Print trunks
prttrks
dsptrks
Privilege | 1-6 |
Jobs | Yes |
Log | No |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | Yes |
prttrks
Print trunk configuration for the node.
(No screen display, just a printout.)
Activates (or "ups") a trunk. If you include the optional vtrk parameter, uptrk activates the trunk as a virtual trunk. If the front card is a BXM (in a BPX 8620), uptrk indicates to the BXM that it is supporting a trunk rather than a UNI port. (See the upln description for the BXM in port mode.)
After you have upped the trunk but not yet added it, the trunk carries line signalling but does not yet carry live traffic. Before you add the trunk with addtrk, the node can monitor the trunk for reliability. Once a trunk has shown reliability and is ready to go into service, add the trunk to the network. If you need to take an active trunk out of service, use dntrk. The dntrk command causes the node to reroute any existing traffic if sufficient bandwidth is available.
You cannot mix physical and virtual trunk specifications. For example, after you up a trunk as a standard trunk, you cannot add it as a virtual trunk when you execute addtrk. Furthermore, if you want to change trunk types between standard and virtual, you must first down the trunk with dntrk then up it as the new trunk type.
You cannot up a trunk if the required card is not available. Furthermore, if a trunk is executing self-test, a "card in test" message may appear on-screen. If this message appears, re-enter uptrk.
Up trunk
uptrk <slot.port>[.vtrk]
addtrk, dntrk
Privilege | 1-2 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX 8400 series, BPX 8620 |
Lock | Yes |
uptrk 21
Activate (up) trunk 21a single-port card, in this case, so only the slot is necessary.
Example 2
Activate (up) trunk 6.1.1a virtual trunk, in this case, which the third digit indicates.
Parameter | Description |
---|---|
slot.port | Specifies the slot and port of the trunk to activate. If the card has only one port, the port parameter is not necessary. An NTM, for example, has one port. |
Parameter | Description |
---|---|
vtrk | Specifies the virtual trunk number. The maximum on a node is 32. The maximum on a T3 or E3 line is 32. The maximum for user traffic on an OC3/STM1 trunk is 11 (so more than one OC3/STM1 may be necessary). Refer also to the section titled "Setting Up a Virtual Trunk " at the front of this chapter. |
Posted: Thu Jan 18 13:02:37 PST 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.