Table of Contents

Setting Up an ATM Connection
Managing Bandwidth
Other Commands
Summary of Commands
addcon

Network and Service Interworking

clrchstats
cnfatmcls
cnfcls
cnfcon
cnfport

Feature Mismatching to Verify LMI/ILMI Support
Traffic Shaping on the UXM Card in Release 9.2
Configuring Traffic Shaping

Redundancy Architecture
Firmware Functionality (BXM)
Performance of Traffic Shaping
Errors and Alarm Handling

cnfportq

Configuring Port Queues used by rt-VBR and nrt-VBR Connections

delcon
dnport
dspatmcls
dspchstats

Functional Description
Segmentation, Assembly, and Reassembly (SAR) Statistics for BXM Card

dspcls
dspcon
dspconcnf
dspcons
dsplmistats

Functional Description of LMI Statistics for BXM Card

dspport
dspportq
dspportstats

Statistics Supported for BPX ATM Ports (ASI or BXM Front Card)

dsprtcache
upport

ATM Connections

This chapter describes the ATM commands that let you activate and configure ATM connections as well as statistical reporting for these connections at an ATM UNI in a BPX or IGX node. You can add ATM connections to an ASI or BXM in a BPX node, or to an ALM/A or UXM in an IGX node. Table 9-1 lists the ATM UNI card combinations for BPX and IGX nodes. For details on ATM commands and other support on an MGX 8220 shelf, refer to the MGX 8220 documentation. For details on ATM commands on an MGX 8550 shelf, refer to the MGX 8550 documentation.

Setting Up an ATM Connection

To set up an ATM connection, perform the following steps:

Step 1   Activate a line with the upln command. Activating a line makes it available so you can configure it. Also, it starts statistics collection. Subsequently, you can begin to add connections with addcon. You can verify that the line has been activated by using the dsplns command. (See the chapter titled "Setting Up Lines" for descriptions of upln and dsplns.)

Step 2   Activate the ATM port with the upport X.X command, where X.X is the slot and port of the ATM card set.

Step 3   Use the cnfport command to establish the characteristics for the ATM port.

Step 4   If a suitable class is already configured, note its number and use this class when adding the ATM connection with the addcon command. (The dspcls command displays the parameters for each connection class. The cnfcls command allows you to modify an individual class.)

Step 5   Use the vt command to log in to the node at the remote end of the proposed ATM connection.

Step 6   At the remote node, use the upln, upport, and cnfport commands, as listed in steps 1 and 2, to activate and configure the remote port.

Step 7   Use the addcon command at one end of the connection to activate the ATM connection.

Managing Bandwidth

There are several commands that assist you in managing bandwidth to achieve satisfactory traffic patterns.

Other Commands

The following commands are useful in establishing connections.

Summary of Commands

Table 9-2 shows the name of each ATM connection command and the page the command description starts on.

addcon

Establishes an ATM connection between the current node and one or more nodes in the network. You can add ATM connections at a UNI port on either an ASI or a BXM in a BPX node, or an ALM/A or a UXM in an IGX node. When used with the syntax in this chapter, addcon adds either a standard ATM connection or an ATM-Frame Relay interworking connection. You can also use addcon to add a virtual path connection (or VP tunnelling DAX connection) between a line port on an IGX-UXM as the VP side, and the line port at the ATM cloud entry point as the VCC side. For a description of the addcon command as it applies to Frame Relay connections, voice connections, or serial data connections, refer to the chapter in this manual that describes the applicable traffic type. For descriptions of the ATM commands that operate on an MGX 8220 shelf, see the MGX 8220 documentation. For descriptions of the ATM commands that operate on an MGX 8850 shelf, see the MGX 8850 documentation.

Note that in this release, on BXM and UXM cards, you can configure port and trunk (routing and feeder trunk) interfaces on the same card slot. For example, you can have port 1 on a BXM slot upped as a trunk interface while having port 2 on the same card slot upped as a line interface. For more information on the Port and Trunks feature, refer to the "Setting Up Trunks" chapter.

In Release 9.2.10, you can add VP tunnelling DAX connections. This type of connection has a VP connection as one end of the connection, and the other end as a VC connection. This VP tunnelling DAX connection can be between different port interfaces on the same UXM card, or on different UXM cards. See Example 2.

In Release 9.2.20, you can add both rt-VBR and nrt-VBR connections. The parameter prompts are the same for both rt-VBR and nrt-VBR, except for Trunk Cell Routing Restrict, which displays for all ATM connections except real-time VBR connections. (This is because rt-VBR connections should only be routed over ATM trunks such as BXM, UXM, and ASI trunks; rt-VBR connections should not be routed over FastPacket trunks such as BTM or ALM/B trunks.)

Note   In Release 9.2.20, the rt-VBR class of service is supported on the IGX UXM and BPX BXM, ASI, and BNI cards only. It is not supported for BTM or ALM-A/B connection endpoints. The rt-VBR class of service is not supported on FastPacket trunks, nor is it supported on MGX 8850 or MGX 8220 (AXIS) interface shelves.

Note that for segment connections, all 2- and 3-segment connections must be the same, that is, all rt-VBR or all nrt-VBR. The CLI will not block you from adding any combination of rt-VBR or nrt-VBR segment connections.

The CLI will block you from adding rt-VBR connections in a network of nodes running releases previous to Release 9.2. All nodes in the network must be first upgraded to Release 9.2.10. In a mixed network of Release 9.1 and 9.2.20, or Release 9.2.10 and 9.2.20, the rt-VBR class of service is not supported—in this scenario, all VBR connections will function as nrt-VBR connections. To support rt-VBR, all nodes in the network must be running switch software 9.2.20. See the Cisco WAN Switching 9.2 Release Notes for more information.

In Release 9.2.0, the switch software supports a minimum Peak Cell Rate (PCR) of 6 cps without policing enabled on both the BXM and UXM. In Release 9.3.0, the switch software supports a minimum PCR of 6 cps with policing enabled (with certain card limitations). Use the dspcd command to determine if this feature is supported on a given slot. Use the addcon command to set the minimum PCR values. If these values are less than the minimum values supported on a given card, the command line interface will not allow you to set them until you have disabled policing. (A prompt will let you know about this limitation, and allow you to disable policing.) Note the following when adding a card:

1. If this new feature is enabled on a card, but is replaced by a card with older firmware (not supporting this feature) the dspcd screen parameter "card status" will display "Mismatch," and indicate the reason for the mismatch.

2. If two cards are loaded with new firmware supporting this feature and configured for Y-redundancy, and one replaced with a card with old firmware, the result is a "mismatch."

For ABRSTD, a policing prompt is now added for VSVD=OFF connections.

Please refer to Table 9-5 for a list of cards that are supported by this feature and their performance specifications.

The addcon command for ATM adds any one of the following types of ATM connections:

• Constant Bit Rate (CBR)
  
  
• Variable Bit Rate (VBR)—rt-VBR and nrt-VBR
  
  
• Frame Relay-to-ATM interworking connection (ATFR)
  
  
• Frame Relay-to-ATM interworking with ForeSight (ATFST) connection
  
  
• Available Bit Rate according to ATM Forum standards (ABRSTD)
  
  
• Available Bit Rate with ForeSight (ABRFST)
  
  
• Frame Relay to ATM transparent Service Interworking (ATFT)
  
  
• Frame Relay to ATM transparent Service Interworking (ATFTFST)
  
  
• Frame Relay to ATM translational Service Interworking (ATFX)
  
  
• Frame Relay to ATM translational Service Interworking (ATFXFST)
  
  
• Unspecified Bit Rate (UBR)
  
  

Detailed connection sequences can be found in the Cisco BPX Series Installation and Configuration. This description has the following information:

• A table that names each type of policing
  
  
• A table showing each connection parameter, possible values, and defaults
  
  
• A table with a brief definition of each connection parameter
  
  
• Example screens from the command line interface
  
  

For detailed descriptions of the connection types, traffic classes, policing, and ATM-related topics, refer to the Cisco BPX 8600 Series Installation and Configuration guide or the ATM Forum specifications.

The node on which addcon executes is the "owner" of the connection. Connection ownership is important because automatic rerouting and preferred routing information is entered on the node that owns the connection. See the cnfpref and cnfcos descriptions for details on automatic rerouting.

The parameter prompts depend on the connection type. The figures on this and the following pages are flow diagrams showing the sequence of possible parameter prompts according to the connection type. The flow diagrams begin at the point after you have entered the remote node name and VPI and VCI (which are common parameters). The subsequent tables define the parameters and list the defaults and ranges for each parameter.

A form of notation appears for some parameters that may need explanation. The notation is either (0), (1), or (0+1). This refers to the state of the Cell Loss Priority (CLP) bit. The usage of the CLP bit is in the traffic policing schemes. (0+1) means cells with CLP=0 or 1. (0) means cells with CLP=0. (1) means cells with CLP=1. The CLP bit is used in different contexts. For example, CDVT (0+1) refers to Cell Delay Variation Tolerance (CDVT) for cells with CLP=0 or 1.

Before a connection is added, the proposed connection appears on the screen prompting you to confirm. After addcon executes, the system software automatically routes the connection.

Instead of entering a class of service, the user can instead enter a class number to select a pre-configured template, for example, class 4 for NTR-VBR, and class 3 for RT-VBR. The class of service templates can be modified as required using the cnfcls/cnfatmcls command and displayed using the dspcls/dspatmcls command.

Note   An IGX switch running NPM-64/4M BRAM, now has increased VC Bandwidth Parameter entries. This provides support for more connections with different bandwidths. When adding or modifying a connection, the input bandwidth parameters are checked against the existing VC Bandwidth Parameters array. If there is a match against an existing parameter in the array, then that particular parameter entry will be used for the connection issued. If there is no match, a new VC Bandwidth Parameter is assigned to the connection. The maximum number of VC Bandwidth Parameters for the NPM-64/4M BRAM was 700. With Release 9.3.0 switch software and higher, the maximum number is 1999.

Note   For a new node running 9.2.20 or later, the rt-VBR connection class number is 3. An upgraded node will retain existing connection classes. Therefore, it won't have the rt-VBR connection class 3. However, the user can configure the connection classes to whatever service and parameters they want using the cnfcls/cnfatmcls command.

Network and Service Interworking

Frame Relay to ATM Interworking enables Frame Relay traffic to be connected across high-speed ATM trunks using ATM standard Network and Service Interworking.

Two types of Frame Relay to ATM interworking are supported, Network Interworking and Service Interworking. The Network Interworking function is performed by the BTM card on the IGX switch. The FRSM card on the MGX 8220 supports both Network and Service Interworking.

clrchstats

Clears the gathered statistics for either a specific channel or all channels. When you enter a specific channel number, the current channel statistics display appears, asking if you want to clear the display. If you enter "*" (all channels) for the channel specification, the display prompts you to confirm whether you want to clear all channel statistics. This is sometimes referred to as a summary statistics command.

The Multilevel Channel Statistics lets you configure and display additional levels of statistics beyond level 1 statistics (for example, levels 2 and 3), as supported by the multilevel channels statistics feature. You use the cnfcdparm command to configure the channels statistics level on the BXM or UXM cards. For example, if you configure slot 5 to support level 3 channel statistics, all connections on that particular card are set to provide level 3 statistics. Switch software collects, displays, and propagates to Cisco WAN Manager the various statistics types. The channel statistic type vary in number and type based on the level of support provided by the BXM and UXM cards. You use the dspchstats and clrchstats to display and clear the statistics.

Full Name

Clear channel statistics

Syntax

clrchstats <channel | *>

Related Commands

dspchstats

Attributes

Example 1

clrchstats 3.1.1

Description

Clear channel statistics for 3.1.1.

System Response

cnfatmcls

The cnfatmcls command allows the ten Cisco-supplied class templates for ATM connection configuration to be modified. (The addcon command can take a class as an input.)

When you enter the number of the class to configure, the display shows the current value of each parameter in the class. For each item in the class, a prompt appears for changing or keeping the current value.

In Release 9.2.20, you can use cnfatmcls and cnfcls to configure the rt-VBR ATM connection class. You can use dspatmcls and dspcls to display the connection parameters for the rt-VBR and nrt-VBR connection classes.

The rt-VBR connections are configured per class 3 service parameters, and nrt-VBR connections are configured per class 2 service parameters. You can change these class parameters by using the cnfcls/cnfatmcls command, or you can enter the parameters individually for each connection by specifying yes to the extended parameters prompt of the addcon command.

Note   For a new node running software Release 9.2.20 or later, the rt-VBR connection class number is 3. An upgraded node will retain existing connection classes. Therefore, it won't have the rt-VBR connection class 3. However, the user can configure the connection classes to whatever service and parameters they want using the cnfcls/cnfatmcls command. For nrt-VBR connections in a new node, running 9.2.20, a number of connection classes are pre-configured, including 2, 4, 5, and 6.

Full Name

Configure class

Syntax

cnfatmcls <class number> [optional parameters]

Related Commands

addcon, cnfatmcls, dspatmcls, cnfcls, dspcls

Attributes

Example 1

cnfatmcls 10

Description

Configure ATM connection class 10. The command line interface (CLI) displays the current settings and requests the class type (see System Response 1). After you enter a class type, the CLI prompts you to specify each parameter for the selected class type (ABRSTD as System Response 2 shows).

System Response 1

System Response 2

Example 2

cnfatmcls 3

Description

Configure ATM connection class 3 for rt-VBR class type connection parameters. The command line interface (CLI) displays the current settings and requests the class type.

System Response 3

cnfcls

The cnfcls command allows the ten Cisco-supplied class templates for connection configuration to be modified. (The addcon command can take a class as an input.)

When you enter the number of the class to configure, the display shows the current value of each parameter in the class. For each item in the class, a prompt appears for changing or keeping the current value.

In Release 9.2.20, you can use cnfatmcls and cnfcls to configure the rt-VBR ATM connection class. You can use dspatmcls and dspcls to display the connection parameters for the rt-VBR and nrt-VBR connection classes.

The rt-VBR connections are configured per class 3 service parameters, and nrt-VBR connections are configured per class 2 service parameters. These class parameters can be changed using the cnfcls/cnfatmcls command, or the parameters can be entered individually for each connection by specifying yes to the extended parameters prompt of the addcon command.

Note   For a new node running software Release 9.2.20 or later, the rt-VBR connection class number is 3. An upgraded node will retain existing connection classes. Therefore, it won't have the rt-VBR connection class 3. However, the user can configure the connection classes to whatever service and parameters they want using the cnfcls/cnfatmcls command. For nrt-VBR connections in a new node, running 9.2.20, a number of connection classes are pre-configured, including 2, 4, 5, and 6.

Full Name

Configure class

Syntax

cnfcls <class number> [optional parameters]

Related Commands

addcon, dspcls, cnfatmcls, dspatmcls

Attributes

Example 1

cnfcls 10

Description

Configure connection class 10. The command line interface (CLI) displays the current settings and requests the class type (see System Response 1). After you enter a class type, the CLI prompts you to specify each parameter for the selected class type (ABRSTD as System Response 2 shows).

System Response 1

System Response 2

An example of a cnfcls/cnfatmcls command and response is shown in the following example:

System Response 3

cnfcon

Configures the ATM bandwidth parameters for a specified connection. The initial cell rate (ICR) normally is set to the port speed. It may be lower if other constraints exist on the data-generation rate. If ICR is too low, cells are dropped. If it is too high, bandwidth may be wasted unless ForeSight is used. Statistical reports are the best source of information for deciding what to adjust.

If the connection type includes ForeSight (abr enabled), the results of the last test round-trip delay command (tstdelay) appear. Note that this is not the current RTD but the result of the last test that ran. Connection priority—high or low—is displayed for standard Frame Relay connections and ForeSight connections. Several checks are done on the parameters that specify bandwidth to assist users in efficient use of network bandwidth. The following messages describe the performance evaluation:

Warning messages are informational only, so the related operation continues. If an error message appears, the operation does not continue.

Full Name

Configure connection

Syntax

cnfcon <slot.port.vpi.vci> [bandwidth parameters]

Related Commands

addcon, dspcon

Attributes

Example 1

cnfcon 12.1.1.6

Description

Configure ASI port 12.1.1.6.

System Response

cnfport

Configures the parameters of an ATM port on an ASI or BXM card on the BPX or a UXM card on the IGX. Press Return to keep the current value of a parameter. See the parameter table for important information.

Previous to Release 9.2, on the BXM card, only ABR VSVD connections are subject to VC scheduling policies on the egress and that is only when the FCES (external segment) option is enabled. With the introduction of traffic shaping, you can choose whether to perform VC scheduling on CBR, VBR, and UBR traffic streams.

In this release, the Ports and Trunks feature lets you configure multiple trunk lines and circuit lines on a single BXM or UXM card simultaneously. In previous releases, when you upped a single port as a trunk (by using the uptrk command), all the remaining ports on that card were treated as a trunk. Similarly, when you up a single port as a circuit line (by using the upln command), all the remaining ports on the card are treated as circuit line ports. This feature allows BXM and UXM cards to be trunk line cards as well as circuit line cards at the same time. This allows trunks as well as circuit lines to coexist on these interface cards.

Feature Mismatching to Verify LMI/ILMI Support

The cnfport commands, in addition to other configuration commands, perform mismatch verification on the BXM and UXM cards. For example, the cnfport command will verify whether the cards both have LMI/ILMI configured.

The command cnfport will prevent disabling ILMI protocol on a port interface if a VSI ILMI session is active on a VSI partition of the port interface. Configure ILMI protocol running on a port interface to run on the BCC instead of the BXM.

Refer to "Feature Mismatching" in the BPX 8600 Series Installation and Configuration. The Feature Mismatching capability will not mismatch cards unless the actual feature has been enabled on the card. This allows for a graceful card migration from an older release.

Traffic Shaping on the UXM Card in Release 9.2

Traffic shaping lets you choose whether to have VC scheduling performed to your CBR, VBR, and UBR traffic streams. You can configure the traffic shaping (which involves weighted fair queuing) option on each BXM interface. A cnfport parameter will prompt you to enable/disable traffic shaping. (The default is for traffic shaping to be disabled.)

Traffic shaping is performed on a per-port basis. When traffic shaping is enabled, all traffic exiting the port is subject to the VC scheduling based on the appropriate service parameters you provision. When a particular port is configured to perform traffic shaping, all ATM cells, regardless of class of service, pass through the VC queues before leaving the card. Where a port is not configured for traffic shaping, the CBR, VBR, and UBR PVCs circumvent the VC queues and are scheduled by the QBins.

No connections should exist on the port before changing the port traffic shaping parameter. If there are existing connections when the port traffic shaping parameter is toggled, then these connections will not be updated unless the card is reset, connections are rerouted, a switchcc occurs, or you modify the connection parameters. Also, traffic shaping is not enabled on a VSVC endpoint if an external segment has been enabled.

Redundant cards must both support traffic shaping, or neither support traffic shaping. In the non-redundant case, traffic shaping is configurable regardless of whether the BXM card in the target slot supports traffic shaping. If the card does not support traffic shaping, then a BXM card that does support traffic shaping can be inserted later and the traffic shaping configuration will take effect. System software will not perform mismatch checking on the traffic shaping capabilities of the BXM.

The traffic shaping rate parameters are in Table 9-15. The MCR is the minimum cell rate for the connection. This is the lowest rate that the connection will be scheduled from the VC queue into the QBin. The PCR is the peak cell rate, or the highest rate at which the connection will be scheduled from the VC queue into the QBin.

Configuring Traffic Shaping

Traffic shaping involves passing ATM traffic through the ATM interface at a VC queue, scheduled rate. Currently, in the BXM-only ABR VSVD connections are subject to VC scheduling policies. With the introduction of traffic shaping, the customer will have the option to perform VC scheduling to his/her CBR, VBR, and UBR traffic streams. Traffic shaping is performed by the BXM hardware.

Traffic shaping will be performed on a per-port basis. When enabled, all traffic exiting the port will be subject to the VC scheduling based on the appropriate service parameters provisioned by the user. Note that all ATM cells, regardless of class of service, pass through the VC queues before leaving the card.

No connections should exist on the port before you change the port traffic shaping parameter. If there are existing connections when you toggle the port traffic shaping parameter, then these connections will not be updated unless you reset the card (by using the resetcd command), connections are rerouted, a switchcc occurs, or you modify the connection parameters. Also, it should be noted that traffic shaping is not enabled on a VSVD endpoint if external segment has been enabled.

Redundancy Architecture

Software requires that redundant cards either both support the feature or neither supports the feature. In the non-redundant case, the feature is configurable regardless of whether the BXM card in the target slot supports traffic shaping. If the card does not support the feature, then a BXM card that does support traffic shaping can be inserted later and the traffic shaping configuration will take effect. Switch software will not perform mismatch checking on the traffic-shaping capabilities of the BXM.

Cisco WAN Manager in Release 9.2 has no changes to support traffic shaping. Switch software functionality is limited to enabling the traffic shaping option (involving weighted fair queuing) on a per-BXM interface case. The cnfport command has a new parameter, which will prompt you to enable or disable traffic shaping. The parameter default is to disable the feature.

Refer to the WAN Switch Software Release 9.2 release notes for additional information on traffic shaping. No connections should be on the port before changing the port traffic shaping parameter. If there are existing connections when the port traffic shaping parameter is toggled, then these connections will not be updated unless the card is reset, connections are rerouted, a switchcc occurs, or you modify the connection parameters*. Also, it should be noted that traffic shaping is not enabled on a VSVD endpoint if an external segment has been enabled. In this case, the scheduling policies are based upon the ATMF 4.0 ABR rules.

The MCR is the minimum cell rate for the connection. This is the lowest rate that the connection will be scheduled from the VC queue into the Qbin. The PCR is the peak cell rate, or the highest rate at which the connection will be scheduled from the VC queue into the Qbin.

Firmware Functionality (BXM)

The BXM firmware supports a new Commbus parameter to enable/disable traffic shaping. When you add a connection, the BXM firmware checks its database to see if traffic shaping is enabled for the port that the connection is to be mapped to. If traffic shaping is enabled, the BXM firmware sets up the ASIC hardware to perform the weighted fair queuing. In the background, the BXM firmware runs a rate-based algorithm.

Existing functionality, such as VC queuing, is used by the traffic shaping feature.

In this release, the BXM firmware supports a new CommBus (CBUS) parameter to enable/disable traffic shaping. When a connection is added, the BXM firmware checks its database to see if traffic shaping is enabled for the port that the connection is to be mapped to. If traffic shaping is enabled, the BXM firmware sets up the ASIC hardware to perform the weighted fair queuing. In the background, the BXM firmware runs a rate-based algorithm similar to what is done today for ERS (explicit rate stamping). The only other interface change includes an egress SCR parameter in the channel (0x52) message.

The algorithm executed by the firmware involves the BXM firmware polling the cell arrival and transmit counters of the Qbins approximately every 15 msec. During this time, the firmware determines the congestion ratio:

• rc = rp * out/in
  
  

where rp is the previous value of rc, "out" is the number of cells leaving the Qbin, and "in" is the number of cells arriving into the QBIN. Note that if the ratio of out/in is less than 1, then the Qbin is experiencing congestion. The BXM firmware takes the resulting "rc" and divides this value into the sum of all of the PCRs for the Qbin and uses this result as the congestion factor to be programmed into the hardware (SABRE).

Performance of Traffic Shaping

The weighted-fair queuing (WFQ) algorithm for traffic shaping runs the same algorithm as the explicit rate stamping (ERS). Today, this processing consumes 12 percent. Because the algorithm runs once (even if both ERS and WFQ are enabled), traffic shaping will not increase the worst-case demand for BXM processor time.

Errors and Alarm Handling

No alarms will be generated regarding the Traffic Shaping feature. As previously mentioned, there is no mismatch checking for BXMs that do not support the feature, so if you insert a BXM with firmware that does not support the feature, then the traffic shaping functionality will not be supported on that card.

It should be noted that cells can be momentarily received out of order when connections are reconfigured between traffic shaping and non-traffic shaping. This is a limitation of the hardware for which there is no work-around.

Full Name

Configure port

Syntax

cnfport <port> [<params>]

Related Commands

upport, dnport, dspport, dspports

Attributes

Example 1

cnfport 12.1 N N N H N N

Description

Configure port 12.1 to have a UNI cell header format; not to be an MGX 8220 shelf; not to have a Metro Cell Header format; shift on HCF; use no protocol; and not to apply %util.

System Response

Example 2

cnfport 5.1 N N N N

Description

Configure port, when used with an IMA line, displays the IMA Port Group. It does not prompt for any new IMA configuration.

System Response

cnfportq

Configures queue parameters for a port on an ASI or BXM card on the BPX or a UXM card on the IGX. Pressing the Return key keeps the current value for the parameter.

In Release 9.2.20, the VBR class of service type can be either rt-VBR or nrt-VBR, depending on the way the corresponding port (service) queues (both ingress and egress) are configured. For the nrt-VBR class of service type in this release, the corresponding service queues are larger than in previous releases to provide more efficient bandwidth sharing with other non-real time service types. The service queues for both rt-VBR and nrt-VBR service types can be configured on a node-by-node basis.

You can use cnfportq to configure Qbin values separately for rt-VBR and nrt-VBR connection types on ports. (To configure the qbin values for rt-VBR and nrt-VBR classes of service on trunks, use cnftrkparm.) The rt-VBR and nrt-VBR connections use different queues on a port: these are the rt-VBR and nrt-VBR queues, respectively. (See Example 3 for a cnfportq screen showing the configuration parameters available for a port queue.)

For information on configuring trunk queues used by rt-VBR and nrt-VBR connections, see the cnftrkparm command.

Configuring Port Queues used by rt-VBR and nrt-VBR Connections

The rt-VBR and nrt-VBR connections use different queues on a port, these are the rt-VBR and nrt-VBR queues, respectively. You can configure these separately, using the cnfportq command.

See Example 2 for a sample cnfportq screen showing configuration parameters available for a port queue.

Full Name

Configure port queue parameters

Syntax

cnfportq <port> [<params>]

Related Commands

upport, dnport, dspportq

Attributes

Example 1

cnfportq 4.2 200 80 60 80 1000 80 60 80 9800 80 60 80

Description

Configure port 4.2 to the parameters indicated.

System Response

Example 2

cnfportq 2.2

Description

Configure the port queue parameters on port 2.2.

System Response

Note   The total queue size of the UXM card is 97250 cells.

delcon

Removes connections from the network. The same command with differing syntax may be used to delete voice connections, data connections, Frame Relay connections, or ATM connections. The syntax in this section deletes an ATM connection. You can verify connection deletions by using the dspcons command.

In Release 9.2.20, you can use delcon to delete data or FRP connections that are terminated on UXM/UXM-E cards for IGX 8400 interface shelves, and terminated on routing network feeder trunks for IGX 8400 routing nodes.

Full Name

Delete connections

Syntax

delcon <channel(s)>

Related Commands

addcon, dspcon, dspcons

Attributes

Example 1

delcon 4.1.1.4

Description

Delete connection 4.1.1.4. The connections to delete are highlighted, and a prompt appears asking you to confirm the deletion. Respond with "y", for yes, and connection 4.1.1.4 is deleted.

System Response

dnport

Deactivates (or "downs") the specified ATM port. Before downing a port, you must remove all connections from the port.

Full Name

Down port

Syntax

dnport <port>

Related Commands

cnfport, dspport, upport

Attributes

Example 1

dnport 4.2

Description

Down port 4.2.

System Response

dspatmcls

Displays the current parameters for an ATM connection class template. The number of classes is ten. The parameters and the values for each varies with the type of connection (CBR, VBR, ABR, and ATFR).

In Release 9.2.20, both the dspatmcls and dspcls commands display

Full Name

Display ATM connection class

Syntax

dspatmcls <class number>

Related Commands

addcon, cnfatmcls, dspcls, cnfcls, dspcon, dspcons

Attributes

Example 1

dspatmcls 1

Description

Display the parameters for configuration class 1.

System Response

Example 2

dspatmcls 1

Description

Display the parameters for configuration class 1.

System Response

dspchstats

Displays statistics for a channel. You can specify an optional parameter interval, and the statistics display will be refreshed by the number of seconds you specify. (You can press the Delete key to stop the screen refresh.) If you do not specify the interval parameter, the screen refresh interval defaults to 10 seconds.

In this release, the multilevel channels statistics feature provides additional levels of channel statistics configuration for the BXM/UXM cards. You can use the cnfcdparm command to configure the channel statistic level on the BXM and UXM cards. For more information see the cnfcdparm command description in the Cisco WAN Switching SuperUser Command Reference.

The system responses that follow display the following statistics categories:

• From the port (something coming into a port, typically from an external device/box)
  
  
• To the network (something going out of the switch; typically trunks)
  
  
• Discarded (received from the attached device but not transmitted to the network)
  
  
• From the network (received in; typically, into the trunk)
  
  
• To the port (transmitted out of the port, to an external device or cloud)
  
  
• Discarded (received from the network but not transmitted to the attached device)
  
  

Full Name

Display channel statistics

Syntax

dspchstats <channel> [interval]

Related Commands

clrchstats

Attributes

Example 1

dspchstats 4.1.50.1

Description

Display the channel statistics for connection 4.1.50.1.

System Response

Example 2

dspchstats 13.1.100 10

Description

Display statistics for connection 13.1.100 with a 10-second interval between screen updates. The card in slot 13 is an ALM/A.

System Response

Example 3

dspchstats 9.2.1.100

Description

Display statistics for connection 9.2.1.100. The card in slot 9 is a UXM.

System Response

Example 4

dspchstats 2.1.1.1 1

Description

Display statistics for connection 2.1.1.1 (with a VPI of 1, and VCI of 1), and an interval of 1.

System Response

Example 5

dspchstats 10.1.205.101

Description

Display statistics for connection 10.1.205.101 (with a VPI of 205 and VCI of 101).

System Response

Functional Description

The table provides some statistics information regarding the BXM SAR. The switch software collects miscellaneous statistics regarding the Monarch SAR (Segmentation, Assembly, and Reassembly).

Segmentation, Assembly, and Reassembly (SAR) Statistics for BXM Card

Table 9-24 provides some statistics information for SAR on the BXM card. Note that the object name typically maps to the screen field name on the dspchstats screen.

dspcls

Displays the current parameters for a connection class template. The number of classes is ten. The parameters and the values for each varies with the type of connection (CBR, rt-VBR, nrt-VBR, ABR, and ATFR). (Note that connection parameters for the rt-VBR and nrt-VBR connection classes display separately.)

Full Name

Display connection class

Syntax

dspcls <class number>

Related Commands

addcon, cnfcls, dspcon, dspcons

Attributes

Example 1

dspcls 1

Description

Display the parameters for configuration class 1.

System Response

Example 2

dspcls 1

Description

Display the parameters for configuration class 1.

System Response

dspcon

Displays connection information for a specified channel. The information displayed includes:

• The channel numbers for both the local and remote ends of the connection.
  
  
• The node names at both ends of the connection.
  
  
• The type or data rate of the connection.
  
  
• The routing restriction.
  
  
• Trunk cell routing restriction.
  
  
• The Class of Service (COS) of the connection.
  
  
• The connection route, listing the end nodes and any intermediate nodes.
  
  
• If cost-based AutoRoute is configured, displays maximum and current costs for a connection route.
  
  
• The preferred route for the connection (if configured).
  
  
• The status of the cards associated with the connection.
  
  
• Any Y-cable conflicts.
  
  
• The compression status.
  
  
• The connection bandwidth parameter values.
  
  
• The connection/type descriptor (if configured). (If the connection is a VP tunnelling DAX connection, the type is displayed as cbrvp, abrstvp, abrfsvp, etc.)
  
  
• The circuit round-trip delay (if ForeSight is enabled).
  
  

Any failures that affect the connection flash on the screen. For Frame Relay NNI ports, the NNI value indicates the A-bit value received across the NNI from the remote network. The status that may be displayed includes:

In release 9.2 switch software for an IGX 8400 routing hub, dspcon does the following:

• dspcon—Shows the new connection segment. Because the connection type is based on the master end of the connection (either voice, data, Frame Relay or ATM connections), the dspcon command displays that and shows the feeder trunk endpoint as the slave end and the incoming A-bit status.
  
  
• dspcon—Indicates connection failures at feeder endpoints.
  
  

In Release 9.2.20, rt-VBR and nrt-VBR connection service types display separately.

Full Name

Display connections

Syntax

dspcon <channel>

Related Commands

addcon, cnfcon, cnfpref, cnfrtcost

Attributes

Example 1

dspcon 12.1.1.5

Description

Display connection information for channel 12.1.1.5 (a VBR connection).

System Response

Example 2

dspcon 12.1.1.4

Description

Display connection information for channel 12.1.1.4 (CBR).

System Response

Example 3

dspcon 12.1.1.100

Description

Display connection information for channel 12.1.1.100 (an ABR connection.)

System Response

Example 4

dspcon 4.1.2.1

Description

Display connection information for channel 4.1.2.1 (an ATFST connection.)

System Response

Example 5

dspcon 12.1.1.*

Description

Display connection information for channel 12.1.1.* (a CBR VP tunnelling DAX connection.)

System Response

dspconcnf

Displays the following information for a connection's configuration:

• The channel numbers for both the local and remote ends of the connection.
  
  
• The node names at both ends of the connection.
  
  
• The preferred route for the connection (if configured).
  
  
• The bandwidth parameter values for ATM connections.
  
  
• VC queue depth.
  
  
• The connection type (if configured).
  
  
• Other values (see example screen).
  
  

The rt-VBR and nrt-VBR connection service types will display separately.

Full Name

Display connection configuration

Syntax

dspconcnf <channel>

Related Commands

addcon, dspcon, dspcons, delcon

Attributes

Example 1

dspconcnf 3.1.1.1

Description

Display the configuration for 3.1.1.1.

System Response

Example 2

dspconcnf 2.1.1.101

Description

Display the configuration for 2.1.1.101.

System Response

dspcons

Displays information about the connections on an IGX or BPX node. (For information about dspcons for an MGX 8220 card, refer to the MGX 8220 Command Reference.)

Table 9-28 lists all possible information headings that appear in the display. The actual headings that appear depend on the choice of selected optional parameters—including no parameters. The screen examples reflect various optional parameters.

Note   This description contains all parameters that are displayed even though some parameters are meaningless on a BPX.

You can also use dspcons to display those connections that have failed the OAM loopback test.

In Release 9.2.20, dspcons will display the rt-VBR and nrt-VBR service types separately.

As you configure VP tunnelling connections on a node, you can display all the VP tunnelling connections on a particular node by using the dspcons -tun command. VP tunnelling connections are indicated by a connection type of "cbrvp", for example, in the Type column of the dspcons screen. For more information on VP tunnelling on UXM cards, see the IGX Installation and Configuration manual.

Full Name

Display connections

Syntax

dspcons [start_channel] [nodename] [-f] [-v] [-d] [-atfr] [-abit] [-fabit] [-fail] [-down]

where

start_channel	The starting channel to display.
nodename	specifies that connections for only the named node appear in the display.
-f	specifies that the display show Frame Relay connections only.
-v	specifies that the display show only voice connections.
-d	specifies that the display show only data connections (in Kbps).
-atfr	specifies that the display show Frame Relay to ATM interworking connections (as well as atfr with ForeSight).
-abit	specifies that the display show status of the A-bit.
-fabit	specifies that the display show only connections with failed A-bits.
-down	specifies that the display show only downed connections.

---

Note   Some parameters may cause other parameters not to appear. Therefore, if you specify all parameters, some do not appear.

---

Related Commands

addcon, delcon

Attributes

Privilege	Jobs	Log	Node	Lock
1-6	No	No	IGX, BPX	No

Example 1

dspcons 4.1.1.4

Description

Displays all connections starting with 4.1.1.4.

System Response

ca19 VT SuperUser BPX 15 9.2 Aug. 23 1997 19:44 GMT Local Remote Remote Route Channel NodeName Channel State Type Avoid COS O 4.1.1.4 ca20 12.1.1.4 Ok CBR 0 R 4.1.1.5 ca20 12.1.1.5 Ok rt-VBR 0 R 4.1.1.6 ca20 12.1.1.6 Ok ABR 0 R 4.1.1.7 ca20 12.1.1.7 Ok nrt-VBR 0 R Last Command: dspcons Next Command:

Example 2

dspcons -abit

Description

Display the Abit status for all connections starting with 1.1.3.66.

System Response

sw81 TN SuperUser BPX 15 9.2 Aug. 14 1997 10:32 PST Local Remote Remote Local Remote Channel NodeName Channel State Abit Abit 1.1.3.66 sw81 1.1.3.66 Ok OK OK 1.1.3.67 sw81 1.1.3.67 Ok OK OK 1.1.3.68 sw81 1.1.3.68 Ok OK OK 1.1.3.69 sw81 1.1.3.69 Ok OK OK 1.1.3.70 sw81 1.1.3.70 Ok OK OK 1.1.3.71 sw81 1.1.3.71 Ok OK OK 1.1.3.72 sw81 1.1.3.72 Ok OK OK 1.1.3.73 sw81 1.1.3.73 Ok OK OK 1.1.3.74 sw81 1.1.3.74 Ok OK OK 1.1.3.75 sw81 1.1.3.75 Ok OK OK 1.1.3.76 sw81 1.1.3.76 Ok OK OK 1.1.3.77 sw81 1.1.3.77 Ok OK OK 1.1.3.78 sw81 1.1.3.78 Ok OK OK This Command: dspcons -abit Continue?

Example 3

dspcons

Description

Display connections

System Response

sw99 TN StrataCom BPX 8620 9.2.10 Aug. 27 1998 08:59 GMT Local Remote Remote Route Channel NodeName Channel State Type Avoid COS O ------- -------- ------- ----- ---- ----- --- -- 3.2.6.16 sw14 10.1.6.16 Ok rt-vbr 0 L 3.2.6.17 sw14 10.1.6.17 Ok rt-vbr 0 L 3.2.6.18 sw14 10.1.6.18 Ok rt-vbr 0 L 3.2.6.19 sw14 10.1.6.19 Ok rt-vbr 0 L 3.2.6.20 sw4 10.1.6.20 Ok rt-vbr 0 L 3.2.6.21 sw14 10.1.6.21 Ok nrt-vbr 0 L 3.2.6.22 sw14 10.1.6.22 Ok atfr 0 L 3.2.6.16 sw157 16.1.6 Failed atfr 0 L 3.2.6.17 sw157 16.1.7 Failed atfr 0 L 3.2.8.18 sw157 16.1.8 OAM-F atfr 0 L 3.2.8.19 sw157 16.1.9 OAM-F atfr 0 L Last Command: dspcons

Example 4

dspcons -oam

Description

Display connections that have failed the OAM loopback test.

System Response

sw99 TN StrataCom BPX 8620 9.2.10 Aug. 27 1998 08:59 GMT Local Remote Remote Route Channel NodeName Channel State Type Avoid COS O ------- -------- ------- ----- ---- ----- --- -- 3.2.6.16 sw157 16.1.6 OAM-F atfr 0 L 3.2.6.17 sw157 16.1.7 OAM-F atfr 0 L 3.2.8.18 sw157 16.1.8 OAM-F atfr 0 L 3.2.8.19 sw157 16.1.9 OAM-F atfr 0 L Last Command: dspcons -oam Next Command:

Table 9-29: dspcons—Optional Parameters

Parameter	Description
start channel	Specifies the beginning channel to display. The start channel format is: slot.port.vpi.vci If no starting channel is specified, the display begins with the first connected channel.
node name	Specifies that connections to a specific remote node are displayed.
-atfr	Frame Relay to ATM interworking connections
-abit	A-bit status
-fabit	Connections with A-bit errors
-fail	Failed connections
-down	Downed connections

Example 5

dspcons -tun

Description

Display only VP tunnelling connections on that node.

System Response

sw224 TRM StrataCom IGX 8420 9.2.a5 Mar. 5 1999 11:10 PST Local Remote Remote Channel NodeName Channel State Type Compress Code COS 12.1.1.100 sw224 12.2.1.* Ok cbrvp 12.2.1.* sw224 12.1.1.100 Ok cbr Last Command: dspcons

dsplmistats

Displays LMI statistics for a specified channel.

Full Name

Display LMI/ILMI statistics

Syntax

dsplmistats <port> [clear]

Note   On an access shelf, the dsplmistats command takes no arguments. On an IPX or IGX node, dsplmistats requires a trunk number. On a BPX node, dsplmistats requires the slot and port number.

Related Commands

none

Attributes

Example 1

dsplmistats 1.1

Description

Display LMI statistics for channel 1.1.1.1.

System Response

Functional Description of LMI Statistics for BXM Card

An internal firmware command provides the capability for the controller card to fetch ILMI/LMI statistics on ILMI/LMI sessions on the BXM card. The BXM must be firmware-capable. Refer to LMI Statistics and Descriptions for dsplmistats (ATM) for BXM Card

dspport

Displays detailed status on a single specified ATM port. The more specific the port address in the command, the more detail is provided. A full description of these parameters is provided in the cnfport command.

Full Name

Display port

Syntax

dspport <slot.port>

Related Commands

cnfport, upport, dnport

Attributes

Example 1

dspport 4.1

Description

Display the status of ASI port 4.1.

System Response

Example 2

dspport 7.2

Description

Display the status of the primary link on port 2, slot 7, of an IMA line.

System Response

dspportq

Displays the port queue configuration for an ASI or BXM card on a BPX or a UXM card on an IGX. After you enter this command with the required slot and port number parameter, the display shows the detailed port queue configuration information shown in the example figure.

Full Name

Display port queue configuration.

Syntax

dspportq <slot.port>

Related Commands

cnfportq

Attributes

Example 1

dspportq 4.2

Description

Display the port queue configuration for 4.2.

System Response

Example 2

dspportq 2.1

Description

Display the port queue configuration for 2.1

System Response

dspportstats

Displays a summary of port statistics 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 they were last cleared. 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 tests have occurred since the statistics were last cleared.

Full Name

Display port statistics

Syntax

dspportstats <port> [interval]

Related Commands

clrportstats

Attributes

Example 1

dspportstats 11.1

Description

Display the statistics for ASI port 11.1.

System Response

Statistics Supported for BPX ATM Ports (ASI or BXM Front Card)

The following 45 statistics are available for each BPX ATM port, with an ASI or BXM front card type, and T3, E3, or OC-3 back card type. (Note that the statistics names listed below are what displays in Cisco WAN Manager; the field name that appears on the dspportstats screen may vary slightly from the Cisco WAN Manager parameter/field name.)

1) Cell Buffer Overflow

2) Cells Rx w/CLP discarded

3) Cells Rx w/CLP=0

4) Cells Rx w/CLP=0 discarded

5) Cells Tx w/CLP=0

6) Egress OAM Cell Count

7) Egress RM Cell Count

8) Get Request Rx

9) Get Request Tx

10) Get Response Rx

11) Get Response Tx

12) GetNext Request Rx

13) GetNext Request Tx

14) Ingress RM Cell Count

15) Invalid LMI IE Rx

16) Invalid LMI Rx

17) Invalid LMI length Rx

18) Invalid Transaction IDs

19) Non-zero GFC Count

20) Number of BCM Cell Rx

21) Number of Cells Rx

22) Number of Cells Rx w/CLP set

23) Number of Cells Rx w/EFCI set

24) Number of Cells Tx

25) Number of Cells Tx w/CLP set

26) Number of Cells Tx w/EFCI set

27) OAM Cells Rx Count

28) Rx AIS Cell

29) Rx FERF Cell

30) SetRequest Rx

31) Status Ack Rx

32) Status Ack Tx

33) Status Enq Rx

34) Status Enq Tx

35) Status Rx

36) Status Tx

37) Trap Rx

38) Trap Tx

39) Tx Header Err Discard

40) Tx Payload Err Due to BIP-16 Err

41) Unknown LMI Rx

42) Unknown LMI Tx

43) Unknown VPI/VCI

44) Update Status Rx

45) Update Status Tx

dsprtcache

This command displays the cache of all cost-based routing connections. The optional index parameter lets you specify a cache entry index. The optional c parameter clears the cache.

Full Name

Display cost-based route cache

Syntax

dsprtcache [index] [c]

[index] specifies the cache entry index

[c] specifies to clear the entire cache or a single entry

Related Commands

dspcon, cnfrtcost, cnfpref

Attributes

Example 1

dsprtcache

Description

Display route cache contents, and let you monitor and manually clear the cache.

System Response

upport

Activates a single port on an ASI or BXM card on a BPX or a UXM card on an IGX. If the port has not been configured, the default configuration values are used to configure the port.

Full Name

Up port

Syntax

upport <slot.port>

Related Commands

dnport, cnfport, upln

Attributes

Example 1

upport 4.2

Description

Activate port 2 on the ASI in slot 4.

System Response

Example 2

upport 5.1

Description

Activate port 1, in slot 5, the primary link for the IMA.

System Response

Posted: Mon Aug 19 21:30:52 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.