Table of Contents

Introduction
Setting Up a Trunk
Setting Up a Virtual Trunk

Some Notes on Virtual Trunking in Release 9.1

Reconfiguring a Trunk
Removing a Trunk
Displaying or Printing Trunk Configurations
Setting Up ATM Trunk Redundancy
Using Subrate Trunk Interface Control Templates
Summary of Commands
addtrk
addtrkred
cnfrsrc
cnftrk

Subrate and Fractional Trunks
Receive and Transmit Rates on Physical Trunks
Receive and Transmit Rates on Virtual Trunks
Virtual Trunk Traffic Classes
Adding a Single Virtual Trunk

cnftrkalm
cnftrkict
cpytrkict
deltrk
deltrkred
dntrk
dspnw
dsppphyslns
dspphyslnstathist
dsptrkbob
dsptrkcnf
dsptrkict
dsptrkred
dsptrks
dsptrkstats
prtnw
prttrkict
prttrks
uptrk

Setting Up Trunks

This chapter describes the commands related to trunks. The contents in this chapter are as follows:

• Introduction
  
  
• A table showing the supported combinations of nodes, card sets, and line types
  
  
• Descriptions of trunk-related procedures:
  
  
• Setting up a trunk
  
  
• Setting up a virtual trunk
  
  
• Reconfiguring a trunk
  
  
• Removing a trunk
  
  
• Displaying or printing a trunk configuration
  
  
• Specifying trunk redundancy
  
  
• Using subrate trunk interface control templates
  
  
• 
  
  
• A list of commands in this chapter with beginning page number
  
  
• Descriptions of the trunk commands
  
  

Introduction

After nodes are configured, the trunks have to be activated. Trunks are intra-node communication links in a network. A trunk can connect any combination of IPX, IGX, or BPX nodes. Trunk characteristics are:

Table 4-1 shows the communication technology for each node type, card combination, and line type.

Setting Up a Trunk

Prior to executing the commands in this section, node setup must be complete (see the chapter titled "Setting Up Nodes"). Also, the front and back cards that support the proposed line type and communication technology must reside in the slot intended for the trunk.

1. Use the uptrk command to activate the trunk. This command activates the port so it can begin generating framing. It also determines whether the trunk is physical-only or a virtual trunk. The third place digit signals that the trunk is virtual. Virtual trunking is only supported on the BPX.

  Each node can have a combined maximum of 32 virtual and physical trunks. The BNI-T3 or E3 can support up to 32 virtual trunks on 1 or both physical ports. A BNI-OC3 line can support up to 11 virtual trunks. Note that, like regular trunks, virtual trunks can carry high-priority traffic.

  Use uptrk at each end of the trunk. When the trunk is up at only one end, the node detects the trunk as being in an alarm state (see dsptrks). Upping the trunk at both ends clears the alarm.

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-0 value before execution of addtrk.

  If cnftrk is used, identical changes must take place at both ends of the trunk. To display existing trunk parameters, use the dsptrkcnf command. The configurable parameters are listed for each card type in the following table. (The possibilities are PKT for FastPackets, ATM cells, BNI if the trunk is a BNI card, or All.) Not all of these parameters apply to the BPX node. The BPX parameters are in a list that follows the table.

  Once the trunk is configured and after the trunk is added (addtrk), certain parameters can be re-specified. For example, a period of trunk usage may reveal a need to change parameters to optimize trunk usage. Refer to the forthcoming section titled "Reconfiguring a Trunk " for details.

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.

  (To add an interface shelf in a tiered network, use addshelf. See the chapter "Setting Up Nodes.")

Setting Up a Virtual Trunk

This section describes how to set up a virtual trunk using a BPX 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 1   Set up cables as follows: in the cloud network, physically connect an ASI port to each BNI port that is likely to carry virtual trunks.

Step 2   For each ASI port connected to a BNI virtual trunk port, use the following configuration 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:

  uptrk slot.port.vtrk (If the cloud is already configured, the alarm on the virtual trunk should clear.)

   cnftrk slot.port.vtrk

When you use cnftrk, make sure the virtual trunk type and VPI correspond to the existing ASI Virtual Path connections.

  addtrk slot.port.vtrk

The parameters slot.port.vtrk on a BNI card can have the following values:

• Slot can be 1-6, 9-14.
  
  
• Port is the physical port number, which can be 1-3 for T3/E3 or 1-2 for OC3/STM1.
  
  
• Vtrk is the virtual trunk number, which can be 1-32 for T3/E3 or 1-11 for OC3/STM1.
  
  

Some Notes on Virtual Trunking in Release 9.1

To use virtual trunking on a BXM card in release 9.1.03, you must use the wraparound workaround solution. Contact the Cisco TAC (Technical Assistance Center) for this information.

When you configure a trunk, you can set the maximum number of user VCs that can traverse the trunk. The BXM will add 270 virtual circuits for controller card (CC) traffic, etc.

There is no concept of a maximum number of VCIs supported on a VPC (virtual path connection). All VCI addresses matching the specified VPI value will be transported if you specify the connection with an "addcon VPI.* format" command.

BNI cards support virtual trunking in release 8.2 and later switch software..

Reconfiguring a Trunk

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:

• Restrict Control Card traffic ("PCC restrict")
  
  
• Pass sync
  
  
• Loop clock
  
  
• Statistical reserve
  
  
• Bursty data peak speed
  
  
• Bursty data peak average frame
  
  
• Idle Code
  
  
• User traffic
  
  
• Connection channels
  
  

To display the current trunk parameters, use dsptrkcnf. If you can make all the needed parameter changes without deleting the trunk, execute cnftrk. Use cnftrk at both ends of the trunk.

To change parameters that first require trunk deletion:

Step 1   Delete the trunk by executing deltrk. Use deltrk at one end of the trunk.

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.

Removing a Trunk

To remove a trunk:

Step 1   Use the deltrk command to delete the trunk. If both ends of the trunk are reachable, perform this command at one end of the trunk only. Otherwise, this command must be performed at both ends. Connections using the deleted trunk that cannot be rerouted are automatically deleted.

Step 2   Use the dntrk command to down the trunk. Execute dntrk at both ends of the trunk.

Displaying or Printing Trunk Configurations

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.

• dsptrks—Displays the current trunk configuration and alarm status at a node.
  
  
• prttrks—Prints the current trunk configuration and alarm status at a node.
  
  
• dspnw—Displays all trunks for each node in a domain.
  
  
• prtnw—Prints all trunks for each node in a domain.
  
  

Setting Up ATM Trunk Redundancy

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), a ALM/B and BNI, or a BTM and a BNI. Trunk redundancy cannot exist between IPX and IGX nodes. 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 node. The BPX node does not require information regarding this feature. The following commands manage trunk redundancy:

• addtrkred—Sets up redundancy for a pair of AIT, BTM, or ALM/B cards.
  
  
• deltrkred—Deletes redundancy for a current redundant pair.
  
  
• dsptrkred—Displays all redundant ATM trunk pairs
  
  

Using Subrate Trunk Interface Control Templates

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.

• cnftrkict—Configures an interface control template for a subrate trunk.
  
  
• cpytrkict—Copies the template from one subrate trunk and applies to another trunk.
  
  
• dsptrkict—Displays the interface control template for a specifies line.
  
  
• prttrkict—Prints the interface control template for a specifies line.
  
  

Summary of Commands

Table 4-2 shows the full name and starting page for the description of each trunk command.

addtrk

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 and node numbers in both networks are unique before it adds the trunk.

You cannot add a trunk while any of the following conditions are true:

• Another node is attempting to change the network topology by adding or deleting a trunk.
  
  
• Another node is notifying all nodes that it has been renamed.
  
  
• Another node is currently adding or deleting a connection in the network with the addcon or delcon command.
  
  
• An unreachable node exists in the network.
  
  
• Connections are rerouting.
  
  
• The node names or the node numbers across the two networks are not unique. Use the command and optional parameter dspnds +n to see the node numbers.
  
  

When using the addtrk command, exercise caution when adding 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. Consult Customer Service before performing these operations.

Full Name

Add trunk to the network

Syntax

addtrk <slot.port>[.vtrk]

Related Commands

deltrk, dsptrks, uptrk

Attributes

Example 1

addtrk 7

Description

Add trunk between node beta slot 7 and node alpha slot 10.

System Response

addtrkred

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. The redundancy scheme requires two sets of ATM trunk cards and two standard T3 or E3 cables (not Y-cables). Note the following characteristics of trunk redundancy:

• Applicable card sets are the AIT, BTM, and ALM/B connected to a BNI card set on a BPX node. (Trunk redundancy between an AIT, BTM, and ALM/B is not allowed.)
  
  
• Execute addtrkred on an IPX or IGX but not on the BPX side.
  
  
• Primary and backup card sets must be in adjacent slots.
  
  
• After a primary trunk failure clears, the traffic automatically returns to the primary card set.
  
  
• Trunk redundancy is not compatible with virtual trunking.
  
  

Full Name

Add trunk redundancy

Syntax

addtrkred <primary trunk> <secondary trunk>

Related Commands

deltrkred, dsptrkred

Attributes

Example 1

addtrkred 4 5

Description

Add bandwidth redundancy for the primary ATM trunk in slot 4 with backup from the ATM trunk in slot 5.

System Response

cnfrsrc

Use the cnfrsrc command to partition resources for AutoRoute PVCs and VSI-Tag Switching.

Full Name

Configure resource

Syntax

cnfrsrc <slot>.<port> <maxpvclcns> <maxpvcbw> <partition> <e/d> <minvsilcns> <maxvsilcns> <vsistartvpi> <vsiendvpi><vsiminbw> <vsimaxbw>

Related Commands

dsprsrc

Attributes

Example

cnfrsrc 4.1 256 26000 1 e 512 16384 2 15 26000 100000

Description

Configure the VSI partition for port 4.1.

System Response

cnftrk

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. Typically, you use uptrk to first up the trunk, then use cnftrk to configure trunk parameters, then use addtrk to add it to the network. You must execute cnftrk at both ends of a trunk.

The section "cnftrk-Parameters" in this description shows required cnftrk parameters. The section titled "cnftrk-Optional Parameters" shows virtual trunk parameters. You can reconfigure some parameters after adding a trunk with addtrk. See the section "Reconfiguring a Trunk ."

In the display for cnftrk, 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 displayed 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.)

In Release 9.1, you can configure cost-based routing from either end of the trunk. You can change the cost before or after the trunk has been added to the network. You can also change the cost after connections have been routed over the trunk. Any cost change is updated network-wide. Every node in the network stores the cost of every trunk in the network.

Subrate and Fractional Trunks

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 EIA/TIA-449. 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.

Receive and Transmit Rates on Physical Trunks

The parameters RCV Trunk Rate and Transmit Trunk Rate apply to physical ATM trunks on an IPX or IGX node. On a BPX 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, you need to do this 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). The typical relationship between pps and cps is two FastPackets for each cell.

For ATM trunks terminating on an AIT (IPX) or a BTM (IGX), 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 node, 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 node.) 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.

Receive and Transmit Rates on Virtual Trunks

The implementation of XMT Trunk Rate on a virtual trunk differs from the implementation on a physical trunk. On a physical trunk, XMT Trunk Rate limits the rate at which the back card physically generates cells. For a virtual trunk, XMT 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, XMT Trunk Rate is the maximum transmission rate allowed on a virtual trunk.

The provider of the virtual trunk service assigns the value for XMT Trunk Rate. You must have this provider-assigned value for XMT Trunk Rate and enter it when you use cnftrk.

The total bandwidth of all the virtual trunks in one port cannot exceed the maximum bandwidth of the port. The trunk loading (load units) is maintained per virtual trunk., but the cumulative loading of all virtual trunks on a port is restricted by the transmit and receive rates for the port.

Virtual Trunk Traffic Classes

All types of Cisco traffic are supported through an ATM cloud. Every trunk is defaulted to carry every type of traffic. The CBR, VBR, and ABR virtual trunks within the cloud should be configured to carry the correct type of traffic. The CBR trunk is suited to carry all types of traffic. The VBR trunk is best suited to carry IPX frame relay and BPX VBR traffic, as well as ForeSight and ABR traffic. The ABR trunk is best suited to carry ForeSight and ABR traffic. You can change the type of traffic each trunk carries. However, to avoid unpredictable results, it is best to stick to the recommended traffic types for a given VPC type.

Adding a Single Virtual Trunk

Following example describes a typical scenario of adding one virtual trunk across an ATM network. One one side of the cloud is a BPX with a BXM trunk in slot 4. On the other side of the cloud is an IGX with a UXM trunk card in slot 10. A virtual trunk is added between port 3 on the BXM and port 2 of the UXM.

1. On BPX_A, up virtual trunk #1 on BXM trunk port 4.3.1.

  uptrk 4.3.1

2. On BPX_A, configure the VPI, VPC type, traffic classes, number of connection channels, and header type.

  cnftrk 4.3.1

3. On IGX_A, up the virtual trunk #1 on the UXM trunk port 10.

  uptrk 10.2.1

4. On IGX_A, configure the VPI, VPC type, traffic classes, number of connection channels, and header type.

  cnftrk 10.2.1

5. On BPX_A, add a virtual trunk between the two nodes. (Executing addtrk 10.2.1 at IGX_A would also add a virtual trunk between the two nodes.)

  addtrk 4.3.1

The VPI values you chose during cnftrk must match those used by the cloud VPC. Also, both ends of the virtual trunk must match on Transmit Rate, VPC type, traffic classes supported, and number of connection channels supported. The addtrk command checks for matching values before allowing the trunk to be added to the network topology.

The network topology from BPX_A's perspective after you add the trunk be:

  BPX_A 4.3.1-10.2.1/IGX_A

Full Name

Configure trunk

Syntax

cnftrk <slot.port>[.vtrk] <options for E1 | T1 | E3 | T3 | OC3 | OC12 | E2 | HSSI | SR >

Related Commands

addtrk, dsptrkcnf

Attributes

Example 1

cnftrk 11

Description

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." The Rev column contains a B for the first character for an ALM/B.)

System Response

Example 2

cnftrk 1.1

Description

Configure trunk 1.1. This trunk is an ATM T3 trunk on a BPX node.

System Response

Example 3

cnftrk 13.1.1

Description

Configure trunk 13.1.1 (a virtual trunk on an ATM T3).

System Response

Example 4

cnftrk 6.3

Description

Configure trunk 6.3 (an OC3 trunk on a UXM).

System Response

Example 5

cnftrk 8.1

Description

Configure trunk 8.1 (a T3 trunk on a UXM).

System Response

Example 6

cnftrk 10.1

Description

Configure trunk 10.1 (an E3 trunk on a UXM).

System Response

Example 7

cnftrk 5.2

Description

Configure trunk 5.2 (an E1 trunk on a UXM).

System Response

Example 8

cnftrk 10.1

Description

Configure trunk 10.1 (a T1 trunk on a UXM).

System Response

cnftrkalm

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.

In an IPX or IGX node, enabled alarms cause an output from the ARC or ARM card or an indication to StrataView Plus.

Full Name

Configure trunk alarms

Syntax

cnftrkalm <slot.port>[.vtrk] <e | d>

Related Commands

dspalms, dsptrks

Attributes

Example 1

cnftrkalm 7 d

Description

Disable trunk alarms on trunk 7.

System Response

cnftrkict

Configures the output lines of an interface control template for a subrate trunk. Table 4-11 shows the configurable signals:

cpytrkict

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.

Full Name

Copy trunk interface control template

Syntax

cpytrkict <source_trunk> <destination_trunk>

Related Commands

cnftrkict, dsptrkict

Attributes

Example 1

cpytrkict 9 11

Description

Copy the interface control template for trunk 9 to trunk 11.

System Response

deltrk

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:

• Another node is attempting to change the network topology by adding or deleting a trunk.
  
  
• Another node is notifying all other nodes that it has a new node name.
  
  
• Another node is adding or deleting a channel connection in the network with the addcon or delcon command.
  
  

Full Name

Delete trunk from a network

Syntax

deltrk <slot.port>[.vtrk]

Related Commands

addtrk, dntrk, dspnw, dsptrks, uptrk

Attributes

Example 1

deltrk 7

Description

Delete trunk 7 from the network.

System Response

deltrkred

Removes redundancy from a UXM, ALM/B, BTM, or AIT trunk. After you execute deltrkrd, you can remove the backup card without causing an alarm.

Full Name

Delete ATM trunk redundancy

Syntax

deltrkred <backup ATM trunk number>

Related Commands

addtrkred, dsptrkred

Attributes

Example 1

deltrkred 5

Description

Remove ATM trunk redundancy for the card set in slot 5.

System Response

dntrk

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).

Full Name

Down trunk

Syntax

dntrk <slot.port>[.vtrk]

Related Commands

addtrk, deltrk, uptrk, dsptrks

Attributes

Example 1

dntrk 9

Description

Deactivate trunk 9.

System Response

dspnw

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:

• ~ indicates that the trunk is a satellite line.
  
  
• Flashing entry indicates a failed line.
  
  
• Blinking node name indicates a node executing downloader software.
  
  

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.

Full Name

Display network

Syntax

dspnw [+b | -b] [+z | -z]

Related Commands

dspnds, prtnw

Attributes

Example 1

dspnw

Description

Display the network topology in tabular form.

System Response

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.

dsppphyslns

Displays a summary of line alarm status for the ATM port specified. These include the cell count in the transmit and receive directions, and error counts associated with the port. The display indicates the date and time that the statistics were cleared and the statistics collection time since the last clearance. Cells transmitted indicates the amount of data transmitted out the port to the user device. Cells received indicates the amount of data received from the user device at the port. Corrupted statistics result from channel/port loopbacks or port tests. A yes in this field indicates that such loopback or port test have occurred since the statistics were last cleared.

Full Name

Display the status of the UXM trunk and its physical line (or lines if IMA).

Syntax

dspphyslns [slot]

Related Commands

dspphyslnstathist

Attributes

Example 1

dspphyslns

Description

Display the physical line of all the UXM cards on the node.

System Response

Example 2

dspphyslns 11

Description

Display the physical lines of the UXM card in slot 11.

System Response

dspphyslnstathist

Displays a summary of physical statistics for the specified individual line within an IMA trunk. These include the cell count in the transmit and receive directions, and error counts associated with the port. The display indicates the date and time that the statistics were cleared and the statistics collection time since the last clearance. Cells transmitted indicates the amount of data transmitted out the port to the user device. Cells received indicates the amount of data received from the user device at the port. Corrupted statistics result from channel/port loopbacks or port tests. A yes in this field indicates that such loopback or port test have occurred since the statistics were last cleared.

Full Name

Display individual physical line statistics

Syntax

dsphyslnstathist

Related Commands

dspphyslns, dspportstats

Attributes

Example 1

dspphyslnstathist 4.1

Description

Display the statistics for line on the IMA trunk on port 4.1.

System Response

dsptrkbob

Displays the state of all inputs from subrate line equipment to an IPX or IGX node 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.

Full Name

Display trunk breakout box

Syntax

dsptrkbob <line> [interval]

Related Commands

cnftrkict, dsptrkict

Attributes

Example 1

dsptrkbob 9

Description

Display the breakout for subrate trunk 9.

System Response

dsptrkcnf

Displays trunk configuration. The parameter values that dsptrkcnf displays have been set with cnftrk or are default values.

As of Release 9.1, dsptrkcnf displays the cost of a trunk if cost-based routing is configured. You configure the administrative cost of a trunk with cnftrk.

Full Name

Display trunk configuration

Syntax

dsptrkcnf <slot.port>[.vtrk]

Related Commands

cnftrk

Attributes

Example 1

dsptrkcnf 6.8

Description

Display the configuration for trunk 6.8

System Response

Example 2

dsptrkcnf 6

Description

Display the configuration for trunk 6. Trunk 6 is an AIT trunk on an IPX node.

System Response

Example 3

dsptrkcnf 11

Description

Display the configuration for the E3 trunk in slot 11 (an ALM/B trunk).

System Response

Example 4

dsptrkcnf 13.3.1

Description

Display the configuration for virtual trunk 13.3.1. The trunk is on a BNI-T3 card set in a BPX node.

System Response

Example 5

dsptrkcnf 6.3

Description

Display the configuration for trunk 6.3. The trunk is on a UXM-OC3 card set in an IGX node.

System Response

Example 6

dsptrkcnf 5.2

Description

Display the configuration for trunk 5.2. The trunk is on a UXM-E1 card set in an IGX node.

System Response

Example 7

dsptrkcnf 10.1

Description

Display the configuration for trunk 10.1. The trunk is on a UXM-T1 card set in an IGX node.

System Response

dsptrkict

Displays interface control information for the subrate trunks. The displayed information includes:

• Specified line.
  
  
• Associated leads and their status (i.e., on or off)
  
  
• Whether output follows a local input.
  
  
• Name of the local or remote input lead that the output lead follows.
  
  

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.

Full Name

Display trunk interface control templates

Syntax

dsptrkict <line>

Related Commands

cnftrkict, prttrkict

Attributes

Example 1

dsptrkict 9

Description

Display subrate for the trunk 9 interface control template.

System Response

dsptrkred

Displays the backup and primary cards for a trunk.

Full Name

Display ATM trunk redundancy

Syntax

dsptrkred [trunk]

Related Commands

addtrkred, deltrkred

Attributes

Example 1

dsptrkred

Description

Display all ATM trunks with redundancy.

System Response

dsptrks

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:

• Trunk number, including the virtual trunk number if applicable
  
  
• Line type (E1, T3, or OC3, for example)
  
  
• Alarm status
  
  

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.

Full Name

Display trunks

Syntax

dsptrks

Related Commands

addtrk, deltrk, dntrk, dsptrk, uptrk

Attributes

Example 1

dsptrks

Description

Display information on the trunk configuration and alarm status for the trunks at a node. The trunk numbers with three places represent virtual trunks.

System Response

dsptrkstats

Displays the trunk port status, ATM cell loss counts, cell payload errors, and cell header errors for the specified trunk. Table 4-28 lists the other statistics. If you include the optional clear parameter, dsptrkstats execution clears the statistics.

prtnw

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:

• ~ indicates the trunk is a satellite line.
  
  
• Flashing entry indicates a failed line.
  
  
• Blinking node indicates a node is executing downloader software.
  
  

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. The prtnw command uses the same syntax and prints the same information as the dspnw command.

Full Name

Print network

Syntax

prtnw [+b | -b] [+z | -z]

Related Commands

dspnw

Attributes

Example 1

prtnw

Description

Print the network topology.

System Response

(No screen display appears—just a printout.)

prttrkict

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:

• Specified line.
  
  
• Associated leads and their status
  
  
• Whether output follows a local input
  
  
• Name of the local or remote input lead that the output lead follows
  
  

Full Name

Print trunk interface control template

Syntax

prttrkict <line>

Related Commands

dsptrkict

Attributes

Example 1

prttrkict

Description

Print network topology.

System Response

(No screen display—just a printout.)

prttrks

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:

• Those trunks that show a "-" in the "Other End" column, have been upped with the uptrk command but not yet added with the addtrk command.
  
  
• The Other End column shows the node name and slot number of the other end of the trunk.
  
  
• Names of disabled trunk appear as light text in the printout.
  
  

Full Name

Print trunks

Syntax

prttrks

Related Commands

dsptrks

Attributes

Example 1

prttrks

Description

Print trunk configuration for the node.

System Response

(No screen display appears—just a printout.)

uptrk

Activates (or "ups") a trunk and, if you include the optional vtrk parameter for applicable cards, activates the trunk as a virtual trunk.

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 addtrunk. 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.

If, after upping a BXM trunk, you get a message telling you to use cnfrsrc to configure PVCs, make sure that when configuring resource partitions with cnfrsrc, you specify values greater than 0 for the Maximum PVC Channels, Maximum PVC Bandwidth, and Maximum VSI LCNs. Otherwise, you will be unable to create any PVCs on a BXM card. Also, you will not be able to change the Connection Channels amount with cnftrk if you do not first use cnfrsrc to configure PVCs.

Full Name

Up trunk

Syntax

uptrk <slot.port>[.vtrk]

uptrk <slot.start-port-end-port> for IMA

Related Commands

addtrk, dntrk, cnfrsrc

Attributes

Example 1

uptrk 21

Description

Activate (up) trunk 21—a single-port card, in this case, so only the slot is necessary.

Example 2

uptrk 6.1.1

Description

Activate (up) trunk 6.1.1—in this case, a virtual trunk, as indicated by the third digit.

Posted: Thu Aug 22 09:32:38 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.