|
|
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 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.
| Front Card | Back Card |
|---|---|
ASI-T3 | LM-2T3 (Two ports) |
ASI-E3 | LM-2E3 (Two ports) |
ASI-155 | MMF-2-BC, SMF-2-BC, or SMF LR-2-BC |
UXM | UAI-4OC3MMF, UAI-4OC3SMF, UAI-2OC3SMF, UAI-8T1-IMA DB15, UAI-8E1-IMA DB15, UAI-8E1-IMA BNC |
BXM-T3-8 or BXM-T3-12 | BPX-T3/E3-8/12 (a universal back card for BXM-T3 or E3) |
BXM-E3-8 or BXM-E3-12 | BPX-T3/E3-8/12 (a universal back card for BXM-T3 or E3) |
BXM-155-4, BXM-155-4D | MMF-155-4, SMF-155-4, or SMFLR-155-4 |
BXM-155-8 | MMF-155-8, SMF-155-8, or SMFLR-155-8 |
BXM-622 | SMF-622 or SMFLR-622 |
BXM-622-2 | SMF-622-2 or SMFLR-622-2 |
To set up an ATM connection, perform the following steps:
 |
Note As of Release 9.3.0, for BPX ports: upln no longer automatically configures a port (the UXM does not require an addport). You can verify that the line has been activated by using the dsplns command. (SeChapter 5, "Setting Up Lines," for descriptions of upln and dsplns.) |
Step 2 For BPX ATM, add an ATM port with the addport X.X[.X] command, where X.X[.X] is the slot, physical port, and optional virtual port number (the UXM does not require an addport). At this time, virtual ports are only available on BXM cards.
Step 3 Use the cnfport command to establish the characteristics for the ATM port.
Step 4 Activate the ATM port with the upport X.X[.X] command, where X.X[.X] is the slot, physical port, and optional BXM card virtual port of the ATM card set.
Step 5 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 6 Use the vt command to log in to the node at the remote end of the proposed ATM connection.
Step 7 At the remote node, use the upln, addport, upport, and cnfport commands, as listed in Steps 1 through 4, to activate and configure the remote port.
|
Note Use the addcon command at one end of the connection to activate the ATM connection. |
|
Note In Release 9.3.0, if a slot-port combination for a BXM card has been brought up as a physical port (upport X.X), that slot-port cannot have virtual ports activated unless the physical port is first deleted (delport X.X). The opposite also applies; once a virtual port is configured, it cannot be used as a physical port until all virtual ports are deleted (delport X.X). Deleting the port completely removes the port from the interface. |
There are several commands that assist you in managing bandwidth to achieve satisfactory traffic patterns.
| Use the configure preference command to specify preferred routing for intra-domain connections. You can use this command to assist in balancing the load on the network's trunks. |
| Use the display and print routes commands in conjunction with the cnfpref command to display the current connection routing information. |
| Use the up and down connection commands to temporarily down connections, thus releasing bandwidth for other services. Frequently, to provide more bandwidth for data, Frame Relay, or ATM traffic, you can down some voice connections. |
The following commands are useful in establishing connections.
| Delete a connection from an ATM line. |
| Delete an ATM port. |
| Down a line. |
| Down a port. |
| Display the connections on a specified ATM line. |
Table 9-2 shows the name of each ATM connection command and the page the command description starts on.
| Mnemonic | Description | Page |
|---|---|---|
addcon | Add connection | |
addport | Add ATM port | |
clrchstats | Clear channel statistics | |
cnfatmcls | Configure ATM class | |
cnfcls | Configure class | |
cnfcon | Configure connection | |
cnfport | Configure port | |
cnfportq | Configure AutoRoute port queue | |
delcon | Delete connection | |
delport | Delete ATM port | |
dnport | Down port | |
dspportq | Display port Qbin information | |
dspatmcls | Display ATM class | |
dspchstats | Display channel statistics | |
dspcls | Display class | |
dspcon | Display connection | |
dspconcnf | Display connection configuration | |
dspcons | Display connections | |
dsplmistats | Display LMI statistics | |
dspport | Display port | |
dspportq | Display AutoRoute port queue | |
dspports | Display all ports that exist on the node | |
dspportstats | Display port statistics | |
dsprtcache | Display cache | |
upport | Up port |
Establishes an ATM connection between the current node and one or more nodes in the network. You can add ATM connections at a port (UNI or NNI) on either an ASI or a BXM in a BPX node, 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 to add a 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, see the chapter in this manual that describes the applicable traffic type. For descriptions of the ATM commands that operate on an MGX 8220 shelf, refer to the MGX 8220 documentation. For descriptions of the ATM commands that operate on an MGX 8850 shelf, refer to the MGX 8850 documentation.
Note that in Release 9.2, 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 Chapter 5, "Setting Up Trunks."
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 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 on page 9-16.
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.)
|
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. 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 is replaced with a card with old firmware, the result is a "mismatch."
For ABRSTD, a policing prompt is now added for VSVD=OFF connections.
See 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:
Detailed connection sequences can be found in the <CellCommandItalic>Cisco BPX Series Installation and Configuration. This description has the following information:
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 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 preconfigured 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 commands.
|
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. |
With Release 9.3.0, you can add connections to a virtual port on a BXM card. At this time, virtual ports are only available on BXM cards. When adding a connection to a virtual port, the virtual port number is not required. The slot, port, and VPI will map to the supporting virtual port. In addition, Vc QDepth is now configurable for all connection types.
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 FRSM card on the MGX 8220 supports both Network and Service Interworking.
| Parameter/Prompt | Description | ||||
|---|---|---|---|---|---|
local channel | Specifies the local slot, port, virtual path identifier (VPI), and virtual connection identifier (VCI) for the connection. The format is slot.port.vpi.vci. You do not need to specify the virtual port (if one has been activated for this channel). The slot, port, and VPI will automatically map to the correct virtual port. The VPI range for a UNI connection is 1-255. The VPI range for an NNI connection is 1-4095. When adding an MGX 8850 interface shelf with a UNI interface to a BPX routing node, the VPI range is 1-255. The VCI range is 1-65535. When adding an MGX 8850 interface shelf with an NNI interface to a BPX routing node, the VPI range is 1-255. The VCI range is 1-65535. When adding an SES (Service Expansion Shelf) to an IGX 8400 routing node, for VCC addressing, the VPI range is 1-255. The VCI range is 1-65535. For VPC addressing, when adding an SES interface shelf to an IGX 8400 routing hub with a UNI interface, the VPI range is 1-255. The VCI range is 1-65535. For VPC addressing, when adding an SES shelf to an IGX 8400 routing with an NNI interface, the VPI range is 1-4095. The VCI range is 1-65535. Note that when adding an SES to an IGX 8400 routing node, the VPI/VCI configured on the IGX 8400 routing hub should match the VPI/VCI configured on the SES interface shelf endpoint address. When adding a VP tunnelling DAX connection to an IGX UXM card, either end of the connection can be the VPI or VCI side. This connection type can be any of the ATM connection types supported by UXM virtual trunks, for example, ABR, CBR, UBR, and VBR. The VCI range is 1-65535. The VCI can be an asterisk (*) to indicate the connection is a virtual path connection (so the VCI has no meaning within the network). | ||||
remote node name | Specifies the name of the node at the other (or remote) end of the connection. | ||||
remote channel | Specifies the remote node's slot, port, VPI, and VCI for this connection. The format is slot.port.vpi.vci. The VPI and VCI ranges are: The VPI range for a UNI connection is 1-255. The VPI range for an NNI connection is 1-4095. The range for a VCI is 1-65535. The VCI can be an asterisk (*) to indicate the connection is a virtual path (the VCI does not provide a distinction within the network). You do not need to specify the virtual port (if one has been activated for this channel). The slot, port, and VPI will automatically map to the correct virtual port. | ||||
connection class/ | Specifies one of the following traffic types—VBR (rt-VBR or nrt-VBR), UBR, CBR, ATFST, ATFR, ABRSTD, ABRFST, ATFT, ATFX, ATFTFST, or ATFXFST; or connection classes—for example, for rt-VBR, connection class 3 for a new node running Release 9.2.20. The subsequent displayed parameters depend on the connection type you choose. To see the parameters associated with each connection type, refer to the appropriate flow diagrams in the refer to the <CellCommandItalic>Cisco BPX Series Installation and Configuration. The option for choosing a class number is also available. The class is a template for a connection type. The class serves as an alternative to specifying each parameter for a connection type. To specify a connection class, enter a digit in the range 1-10. To see the parameter values for a class, use the dspcls commands. To customize any class template, use cnfcls.
| ||||
PCR | Peak Cell Rate: the cell rate that the source cannot exceed. | ||||
%Util | Specifies the percentage of bandwidth utilization. | ||||
MCR | Minimum Cell Rate: the committed, minimum cell rate for a connection in a network. | ||||
CDVT | Cell Delay Variation Tolerance: controls time scale over which the PCR is policed. | ||||
FBTC (AAL5 Frame-based Traffic Control) | To enable the possibility of discarding the whole frame, not just one non-compliant cell. This is used to set the Early Packet Discard bit at every node along a connection. With the ASI, FBTC means packet discard on both policing and queueing. With the BXM, FBTC means packet discard on queueing only. | ||||
VSVD | Virtual Source Virtual Destination. | ||||
Flow Control External Segments | Enables Cisco WAN switches to perform flow control on external segments (on the CPE, for example) in addition to the Cisco WAN Switching segments. | ||||
SCR | Sustainable Cell Rate: the long-term limit on the rate that a connection can sustain. | ||||
MBS | Maximum Burst Size: the maximum number of cells that can burst at the PCR and still be compliant. MBS is used to determine the Burst Tolerance (BT), which controls the time period over which the SCR is policed. | ||||
Policing | With the ASI, FBTC means packet discard on both policing (see Table 9-5) and queueing. With the BXM, FBTC means packet discard on queueing only. | ||||
VC QDepth | The depth of the queue VC QDepth. As of Release 9.3, VC QDepth can be configured for all connections, not just ABR connections. | ||||
CLP Hi | Cell Loss Priority Hi threshold (% of VC QDepth). When the high threshold is exceeded, the node discards cells with CLP=1 until the number of cells in the queue drops below the level specified by CLP Lo/EPD. As of Release 9.3, CLP Hi can now be configured for all connections, not just ABR connections. | ||||
CLP Lo/EPD | Cell Loss Priority Low threshold (% of VC QDepth)/Early Packet Discard. When the number of cells in the queue drops below the level specified by CLP Lo/EPD, the node stops discarding cells with CLP=1. If the card is a BXM and AAL5 FBTC=yes, the percent of VC QMax equals the value of EPD. Frame-based Traffic Control (FBTC) is FGCRA for AAL5. The BXM does not support Frame-based Policing. For an ASI card, the percent of VC QMax is CLP Lo regardless of the FBTC setting. As of Release 9.3, CLP Lo/EPD can now be configured for all connections, not just ABR connections. | ||||
EFCI | Explicit Forward Congestion Indication threshold (% of VC QDepth). | ||||
ICR | Initial Cell Rate: the rate at which a source initially transmits after an idle period. | ||||
IBR | Initial Burst Size: the maximum burst size a source can initially transmit after an idle period. IBR applies to only BXM cards. | ||||
ADTF (ATM Forum TM 4.0 term) | The Allowed-Cell-Rate Decrease Factor. Time permitted between sending RM cells before the rate is decreased to ICR. (In previous software releases, ADTF was ICR TO—Initial Cell Rate Time Out.) | ||||
Trm (ATM Forum TM 4.0 term) | An upper bound on the time between forward RM-cells for an active source: an RM cell must be sent at least every Trm milliseconds. (In previous software releases, Trm was Min. Adjust.) | ||||
RIF (ATM Forum TM 4.0 term) | Rate Increase Factor: controls the amount by which the cell transmission rate may increase upon receipt of an RM cell. (In previous software releases, RIF was Rate Up.) | ||||
RDF (ATM Forum TM 4.0 term) | Rate Decrease Factor: controls the amount decrease in cell transmission rate when an RM cell arrives. (In previous software releases, RDF was Rate Down.) | ||||
Nrm (ATM Forum TM 4.0 term) | Nrm. Maximum number of cells a source may send for each forward RM cell: an RM cell must be sent for every Nrm-1 data cells. | ||||
FRTT (ATM Forum TM 4.0 term) | Fixed Round Trip Time: the sum of the fixed and propagation delays from the source to a destination and back. | ||||
TBE (ATM Forum TM 4.0 term) | Transient Buffer Exposure The negotiated number of cells that the network would like to limit the source to sending during start-up periods, before the first RM-cell returns. | ||||
PCR | Peak cell rate: the cell rate that the source may never exceed. |
| Parameter with Default Settings | UXM and BXM T1/E1, T3/E3, OC-3, and OC-12 RANGE | ASI Range |
|---|---|---|
PCR(0+1)[50/50] | 50-max. T1/E1 cells/sec 50-max. T3/E3 cells/sec 50-max. OC-3 cells/sec 50-max. OC-12 cells/sec | T3: MCR-96000 E3: MCR-80000 OC-3 (STM1): 0-353200 Limited to MCR-5333 cells/sec for ATFR connections. |
%Util [100/100] for UBR [1/1] | 0-100% | 1-100% |
MCR [50/50] | cells/sec 6-max. of T3/E3/OC-3/OC-12 | T3: 0-96000 cells/sec E3: 0-80000 cells/sec |
AAL5 Frame-Based Traffic Control: for rt/nrt-VBR [disable] for ABR/UBR [enable] for Path connection [disable] | enable/disable With the BXM card, FBTC means packet discard on both policing and queueing. | enable/disable With the ASI card, FBTC means packet discard on both policing and queueing. |
CDVT(0+1): for CBR [10000/10000], others [250000/250000] | 0-5,000,000 microsecs. | T3/E3 1-250,000 usecs. OC-3/STM1: 0-10000 usecs. |
ForeSight [disable] | 0 = disable 1 = enable | 0 = disable 1 = enable |
VSVD [disable] | enable/disable | enable/disable |
Flow Control External Segment [disable] | enable/disable | enable/disable |
Default Extended Parameters [enable] | enable/disable | enable/disable |
CLP Setting [enable] | enable/disable | enable/disable |
SCR [50/50] | c50-max. T1/E1 cells/sec 50-max. T3/E3 cells/sec 50-max. OC-3 cells/sec 50-max. OC-12 cells/sec
| T3: MCR-96000:T3 E3: MCR-80000: E3 OC-3/STM1: 0-353200 Limited to MCR-5333 cells/sec for ATFR connections. |
MBS [1000/1000] | 1--5,000,000 cells | T3/E3: 1-24000 cells OC-3 (STM1): 10-1000 cells |
Policing [3] For CBR: [4] | 1 = VBR.1 2 = VBR.2 3 = VBR.3 4 = PCR policing only 5 = off | 1 = VBR.1 2 = VBR.2 3 = VBR.3 4 = PCR policing only 5 = off |
ICR: max [MCR, PCR/10] | MCR - PCR cells/sec | MCR - PCR cells/sec |
ADTF [1000] | 62-8000 msecs. | 1000-255000 msecs. |
Trm [100] | ABRSTD: 1-100 msecs. | 20-250 msecs. |
VC QDepth [16000/16000] For ATFR/ATFST [1366/1366] | 0-61440 cells | Applies to T3/E3 only |
CLP Hi [80/80] | 1-100% | 1-100% |
CLP Lo/EPD [35/35] | 1-100% | 1-100% |
EFCI [30/30] For ATFR/ATFST [100/100] | 1-100% | 1-100% |
RIF:
For ForeSight: = max [PCR/128, 10]
For ABRSTD [128] | If ForeSight, then in absolute (0-PCR)
If ABR, then 2n (1-32768) | If ForeSight, then in absolute (0-PCR)
If ABR, then 2n (1-32768) |
RDF: For ForeSight [93]
For ABRSTD [16] | IF ForeSight, then % (0%-100%)
If ABR, then 2n (1-32768) | IF ForeSight, then % (0%-100%)
If ABR, then 2n (1-32768) |
Nrm[32]-BXM only | 2-256 cells | not applicable |
FRTT[0]-BXM only | 0-16700 msec | not applicable |
TBE[1,048,320]-BXM only | 0-1,048,320 cells (different maximum range from TM spec. but limited by firmware for CRM (4095 only) where CRM=TBE/Nrm | not applicable |
IBS [0/0] | 0-24000 cells | T3/E3 ABR: 0-24000 cells ATFR: 1-107 cells OC-3: 0-999 cells |
Trunk Cell Routing Restriction (y/n) [y] | yes or no For rt-VBR connections, this prompt will not display. (This is because rt-VBR connections should only be routed over ATM trunks such as BXM, UXM, and ASI.) Trunk Cell Routing Restriction will display for all other connections. | yes or no For rt-VBR connections, this prompt will not display. (This is because rt-VBR connections should only be routed over ATM trunks such as BXM, UXM, and ASI.) Trunk Cell Routing Restriction will display for all other connections. |
.
| Card Name | Card Types | Minimum PCR Values with Policing | ||
IGX-UXM | T1/E1 | 6 cps | ||
IGX-UXM | IMA | 6 cps | ||
IGX-IUX | T3/E3 | 12 cps | ||
IGX-UXM | OC-3/STM-1 | 50 cps | ||
BPX-BXM | T3/E3 | 12 cps | ||
BPX-BXM | OC-3/STM-1 | 50 cps | ||
BPX-BXM | OC-12/STM-4 | 50 cps | ||
| ||||
| Connection Type | ATM Forum TM spec. 4.0 conformance definition | PCR Flow (1st leaky bucket) | CLP tagging (for PCR flow) | SCR Flow (2nd leaky bucket) | CLP tagging (for SCR flow) |
|---|---|---|---|---|---|
CBR | CBR.1 when policing set to 4 (PCR policing only) | CLP(0+1) | no | off | n/a |
CBR | when policing set to 5 (off) | off | n/a | off | n/a |
UBR | UBR.1 when CLP setting = no | CLP(0+1) | no | off | n/a |
UBR | UBR.2 when CLP setting = yes | CLP(0+1) | no | CLP(0) | yes |
rt/nrt-VBR, ABR, ATFR, ATFST | VBR.1 when policing set to 1 | CLP(0+1) | no | CLP(0+1) | no |
rt/nrt-VBR, ABR, ATFR, ATFST | VBR.2 when policing set to 2 | CLP(0+1) | no | CLP(0) | no |
rt/nrt-VBR, ABR, ATFR, ATFST | VBR.3 when policing set to 3 | CLP(0+1) | no | CLP(0) | yes |
rt/nrt-VBR, ABR, ATFR, ATFST | when policing set to 4 | CLP(0+1) | no | off | n/a |
rt/nrt-VBR, ABR, ATFR, ATFST | when policing set to 5 (off) | off | n/a | off | n/a |
Note 1: - For UBR.2, SCR = 0
Note 2:
CLP = Cell Lost Priority
CLP(0) means cells that have CLP = 0
CLP(1) means cells that have CLP = 1
CLP(0+1) means both types of cells: CLP = 0 & CLP = 1
CLP(0) has higher priority than CLP(1)
CLP tagging means to change CLP = 0 to CLP = 1, where CLP= 1 cells have lower priority
| Connection Type | ATM Forum TM spec. 4.0 conformance definition | PCR Flow (1st leaky bucket) | CLP tagging (for PCR flow) | SCR Flow (2nd leaky bucket) | CLP tagging (for SCR flow) |
|---|---|---|---|---|---|
rt/nrt-VBR, ABR, ATFR, ATFST, ATFT, ATFTST, ATFX, ATFXFST | VBR.1 when policing set to 1 | CLP(0+1) | no | CLP(0+1) | no |
rt/nrt-VBR, ABR, ATFR, ATFST, ATFT, ATFTST, ATFX, ATFXFST | VBR.2 when policing set to 2 | CLP(0+1) | no | CLP(0) | no |
rt/nrt-VBR, ABR, ATFR, ATFST, ATFT, ATFTST, ATFX, ATFXFST | VBR.3 when policing set to 3 | CLP(0+1) | no | CLP(0) | yes |
rt/nrt-VBR, ABR, ATFR, ATFST, ATFT, ATFTST, ATFX, ATFXFST | when policing set to 4 | CLP(0+1) | no | off | n/a |
rt/nrt-VBR, ABR, ATFR, ATFS, ATFT, ATFTST, ATFX, ATFXFST | when policing set to 5 for off | off | n/a | off | n/a |
Add Connection
addcon parameters (see preceding tables)
delcon, dspcons
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
addcon 9.1.100.100 pubsbpx2 9.1.102.102
Add a standard ABR connection with VSVD and no Default Extended Parameters (which then require user input for SCR, MBS, and so on).
pubsbpx1 TN SuperUser BPX 15 9.2 Oct. 27 1997 05:22 GMT
From Remote Remote Route
9.1.100.100 NodeName Channel State Type Avoid COS O
9.1.100.100 pubsbpx2 9.1.102.102 Ok abrstd
9.1.102.102 pubsbpx2 9.1.100.100 Ok abrstd
This Command: addcon 9.1.100.100 pubsbpx2 9.1.102.102 abr * * * * e e * d * * 1
* * * * * * * * *
Add these connections (y/n)?
addcon 5.2.10.* pubsigx1p 5.1.1.100 CBR ...
Add a virtual path connection (VPC) to virtual circuit connection (VCC) between ports 1 and 2. (This is called a VP tunnelling connection.)
pubsigx1 TN SuperUser IGX 8400 9.2 Oct. 27 1998 05:22 GMT
From Remote Remote Route
NodeName Channel State Type Avoid COS O
5.2.10.* pubsigx2 5.1.1.100 Ok abrstvp
5.1.1.100 pubsigx2 5.2.10.* s Ok abrstvp
This Command: addcon 5.2.10.* pubsigx1p 5.1.1.100 CBR ...
Add these connections (y/n)?
|
Note For BPX only, as of Release 9.3.0, upln no longer automatically configures a port. You must use the addport command to add the port before you can use the addcon command. 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.) |
Add ATM or FRAME RELAY port
addport <slot.port>[.<vport>]
delport, upport, dnport, dspports, dspport, cnfport
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
addport 5.2 2.1-20
Add port 2 for the IGX card in slot 5.
addport 16.1-15
Add port 1 for the IGX card in slot 16.
addport 3.2.15
Add port 2 for BPX card in slot 3.
| Parameter | Description |
|---|---|
slot.port[.vport] | Specifies the slot number of the card, the physical port, and the optional virtual port (BXM card only). The optional vport identifier must be between 1-31 inclusive. |
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.
Clear Channel Statistics
clrchstats <channel | *>
dspchstats
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
clrchstats 3.1.1
Clear channel statistics for 3.1.1 (BPX).
clrchstats 3.1.1
Clear channel statistics for 3.1.1.
sw83 TN SuperUser IGX 8420 9.2 Aug. 23 1997 19:24 PST
Channel Statistics: 3.1.1 Cleared: Aug. 17 1997 08:10
MIR: 3.8 kbps Collection Time: 6 day(s) 10:04:58 Corrupted: NO
Frames Avg Size Avg Util Packets Avg
(bytes) (fps) (%) (pps)
From Port: 1516586 198 2 35
To Network: 1516215 198 2 35 16678365 30
Discarded: 371 198 0 0
From Network: 1518665 197 2 35 16705146 30
To Port: 1518629 198 2 35
Discarded: 36 120 0 0 238 0
ECN Stats: Avg Rx VC Q: 0 ForeSight RTD 40
Min-Pk bytes rcvd: 52470 FECN Frames: 0 FECN Ratio (%) 0
Minutes Congested: 0 BECN Frames: 16 BECN Ratio (%) 0
Frames rcvd in excess of CIR: 0 Bytes rcvd in excess of CIR: 0
Frames xmtd in excess of CIR: 0 Bytes xmtd in excess of CIR: 0
This Command: clrchstats 3.1.1
OK to clear (y/n)?
| Parameter | Description |
|---|---|
channel | Specifies the channel whose statistics are cleared. |
* | Specifies all channel statistics. |
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 commands, 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 desired service and parameters using the cnfcls/cnfatmcls commands. For nrt-VBR connections in a new node, running Release 9.2.20, a number of connection classes are preconfigured, including 2, 4, 5, and 6. |
Configure Class
cnfatmcls <class number> [optional parameters]
addcon, cnfatmcls, dspatmcls, cnfcls, dspcls
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
cnfatmcls 10
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).
sw60 TN SuperUser BPX 8620 9.2 Date/Time Not Set
ATM Connection Classes
Class: 10 Type: CBR
PCR(0+1) % Util CDVT(0+1) Policing
4000/4000 100/100 10000/10000 4
Description: "Default CBR 4000"
This Command: cnfatmcls 10
Enter class type (rt-VBR, nrt-VBR, UBR, CBR, ATFST, ATFR, ABRSTD, ABRFST, ATFT, ATFX,
ATFTFST, ATFXFST):
sw60 TN SuperUser BPX 8620 9.2 Date/Time Not Set
ATM Connection Classes
Class: 10 Type: ABRSTD
PCR(0+1) % Util MCR CDVT(0+1) AAL5 FBTC
4000/4000 100/100 4000/4000 10000/10000 n
Description: "Default CBR 4000"
This Command: cnfatmcls 10 abrstd * * * * *
Do you want this change (y/n)?
cnfatmcls 3
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.
sw60 TN SuperUser BPX 8620 9.2 Date/Time Not Set
ATM Connection Classes
Class: 3 Type: rt-VBR
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
2000/2000 100/100 10000/10000 n 2000/2000
MBS Policing
1000/1000 3
Description: "Default rt-VBR 2000"
This Command: cnfatmcls 3
Enter class type (rt-VBR, nrt-VBR, UBR, CBR, ATFST, ATFR, ABRSTD, ABRFST, ATFT, ATFX,
ATFTFST, ATFXFST):
| Parameter | Description |
|---|---|
class | Specifies the class to configure. The class numbers are 1-10. |
| Parameter | Description |
|---|---|
optional parameters | Individual parameters are specific to the type of connection (rt-VBR, nrt-VBR, CBR, UBR, ATFST, ATFR, ABRSTD, ABRFST, ATFT, ATFX, ATFTFST, ATFXFST). Each is prompted one at a time. Refer to the dspcls command to see the parameters in each of the classes. |
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 commands, 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 desired service and parameters using the cnfcls/cnfatmcls commands. For nrt-VBR connections in a new node, running Release 9.2.20, a number of connection classes are pre-configured, including 2, 4, 5, and 6. |
Configure Class
cnfcls <class number> [optional parameters]
addcon, dspcls, cnfatmcls, dspatmcls
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
cnfcls 10
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).
sw60 TN SuperUser BPX 8620 9.2 Date/Time Not Set
ATM Connection Classes
Class: 10 Type: CBR
PCR(0+1) % Util CDVT(0+1) Policing
4000/4000 100/100 10000/10000 4
Description: "Default CBR 4000"
This Command: cnfcls 10
Enter class type (VBR, CBR, UBR, ABRSTD, ABRFST, ATFR):
sw60 TN SuperUser BPX 8620 9.2 Date/Time Not Set
ATM Connection Classes
Class: 10 Type: ABRSTD
PCR(0+1) % Util MCR CDVT(0+1) AAL5 FBTC
4000/4000 100/100 4000/4000 10000/10000 n
Description: "Default CBR 4000"
This Command: cnfcls 10 abrstd * * * * *
Do you want this change (y/n)?
An example of a cnfcls/cnfatmcls command and response is shown in the following example:
pubsbpx1 TN silves:1 BPX 8620 9.2.2G July 16 1999 10:42 PDT
ATM Connection Classes
Class: 2 Type: nrt-VBR
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
1000/1000 100/100 10000/10000 n 1000/1000
MBS Policing
1000/1000 3
Description: "Default nrt-VBR 1000 "
This Command: cnfcls atm 2
Enter class type (rt-VBR, nrt-VBR, CBR, UBR, ABRSTD, ABRFST, ATFR, ATFST, ATFT,
ATFTFST, ATFX, ATFXFST):
| Parameter | Description |
|---|---|
class | Specifies the class to configure. The class numbers are 1-10. |
| Parameter | Description |
|---|---|
optional parameters | Individual parameters are specific to the type of connection (CBR, rt-VBR, nrt-VBR, ABR, ATFR). Each is prompted one at a time. Refer to the dspcls command to see the parameters in each of the classes. |
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:
| Min cannot exceed peak. |
| Min exceeds this port's speed. |
| Sum of mins exceeds port's speed. |
| Peak exceeds this port's speed. |
Warning messages are informational only, so the related operation continues. If an error message appears, the operation does not continue.
Configure Connection
cnfcon <channel> [bandwidth parameters]
addcon, dspcon
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
cnfcon 12.1.1.6
Configure ASI connection 12.1.1.6.
a20 LAN SuperUser BPX 15 9.2 Aug. 29 1997 11:43 PST
Conn: 12.1.1.6 ca19 4.1.1.6 ABR
Description:
SCR IBS MBS ABR MCR PCR ICR
100/100 10/10 10/10 y 10/10 96000/96000 10/10
ICR TO Rate Up Rate Dn Rate FastDn Max Adjust VC Qdepth EFCI % Util
10 100 100 100 100 64000/64000 100/100 100/100
CLP CLP Hi CLP Lo
y 100/100 90/90
This Command: cnfcon 12.1.1.6
MBS (10) must exceed IBS (10)
Enter the MBS [10/10]:
| Parameter | Description |
|---|---|
channel | Specifies the connection to configure. This command configures one connection at a time. The channel specification has the following format: slot.port.vpi.vci You do not need to specify the virtual port (if one has been activated for this channel). The slot, port, and VPI will automatically map to the correct virtual port. |
| Parameter | Description |
|---|---|
bandwidth parameters | Refer to the addcon command in this chapter for descriptions and connection types. |
Configures the parameters of an ATM or FRAME RELAY port on an ASI or BXM card on the BPX, or a UXM card on the IGX. On the IGX this command works on the UXM, FRM, and UFM cards. Press Return to keep the current value of a parameter. See the parameter table for important information (Table 9-19).
In Release 9.2, 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.
In Release 9.3.0, changing the line framing for BXM-T3 cards from PLCP to HEC no longer automatically changes the port's bandwidth to the new maximum. It merely raises the upper limit for the port's bandwidth. After changing the framing, you must use cnfport to increase the port's bandwidth, and cnfrsrc to increase the port's Auto Route bandwidth (PVC Max Bandwidth).
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 lets you choose whether to have VC scheduling performed to your CBR, VBR, UBR, or ABRSTD with VSVD and without FCES traffic streams. You can configure the traffic shaping (which involves weighted fair queuing) option on each BXM interface. In release 9.3.05 onward, traffic shaping is enabled/disabled per QoS using the cnfportq command.
Traffic shaping, and all traffic pertaining to the QoS for this release, is performed on a per-port basis, . When a particular QoS 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. When a traffic class is not configured for traffic shaping, its connections 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 VSVD endpoint if an external segment has been enabled.
Redundant cards must either 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-16. 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.
| Service Type | MCR | PCR |
|---|---|---|
CBR | PCR | PCR |
VBR | SCR1%Util | PCR |
UBR | 0 | PCR |
ABR | MCR %Util | PCR |
| 1Indicates that the system software issues a warning that traffic shaping is not supported on that specific BXM. |
|
Note Traffic shaping does not generate any alarms. There is no mismatch checking for BXMs that support traffic shaping, so if you insert a BXM card with firmware that does not support it, then the traffic shaping functionality will not exist. |
|
Note Cells can be momentarily received out of order when you reconfigure connections between traffic shaping and non-traffic shaping. This is a limitation of the hardware for which there is no workaround. |
Traffic shaping involves passing ATM traffic through the ATM interface at a VC queue, scheduled rate. With the introduction of traffic shaping, the customer will have the option to perform VC scheduling to his/her ABR, CBR, VBR, and UBR traffic streams. Traffic shaping is performed by the BXM hardware.
Traffic shaping will be performed on a per-port, per-COS basis.
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.
Use cnfportq to configure traffic shaping parameters.
Software requires that redundant cards either both support the feature or neither support 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.
Refer to the Cisco 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 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 for the traffic class on the port, 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 explicit rate stamping (ERS). 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:
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).
The weighted fair queuing (WFQ) algorithm for traffic shaping runs the same algorithm as the explicit rate stamping (ERS). This processing consumes 12 percent of the bandwidth. 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.
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 workaround.
Virtual Ports are available for the BPX switches for the purpose of supporting hierarchical traffic shaping. Hierarchical traffic shaping is traffic shaping at more than one level, and provides a combination of Virtual Port traffic shaping and connection traffic shaping. Currently, there is traffic shaping on Physical Ports and on connections. This feature will allow one or more Virtual Ports per Physical Port interface. Traffic shaping, which was previously offered only on Physical Ports, will be available on Virtual Ports. Connection-level traffic shaping will also be available within Virtual Ports.
Virtual Ports is a chargeable feature. Cisco Customer Service must enable this feature per node by using the cnfswfunc command. The cnfswfunc command has a privilege level of Service or higher.
Virtual Ports on the BPX (node) will connect the node to CPEs, either directly or indirectly through an ATM network. Although Virtual Ports can connect directly to CPEs, they will generally be used to connect indirectly, because direct connections to CPEs can be done with currently available Physical Ports.
Virtual Ports will be a chargeable feature on the BPX and must be configured on the BPX for operation. A Virtual Port may carry multiple PVCs or PVPs. VI traffic shaping capability will be provided per Virtual Port. Additionally, connection traffic shaping will also be available on a QOS basis. While Virtual Port shaping is always ON, connection traffic shaping can be turned ON or OFF using the cnfportq command.
A maximum of 31 logical entities are available on a BXM card. A logical entity is a Virtual or Physical trunk or a virtual or physical port. Each port will support all AutoRoute traffic types that are currently supported by Physical Ports.
With Release 9.3, all ports have a cnfport Bandwidth parameter specifying the maximum bandwidth available for use on that port (see Figure 9-2). This parameter is similar to the Bandwidth parameter in Physical Ports. The Bandwidth parameter will be configurable on the Virtual Port. On Physical Ports, this parameter is not configurable, it is automatically set to the line speed. Traffic throughput on a Virtual Port cannot exceed the Bandwidth.
The cnfport CAC Reserve parameter specifies a portion of the bandwidth that is not available for booking by connections if CAC Override is disabled. This feature reserves some bandwidth to handle bursts of traffic. The CAC reserve specifies a port in the Auto Route Bandwidth (the total port's bandwidth can be provisioned into AR and VSI using the cnftsrsc command, and the CAC reserve is relevant to the AR portion).
The cnfport VPI range parameter specifies the range for Virtual Ports. The VPI range cannot be configured for Physical Ports. The range must be contiguous (for example, VPI 100 to 100, or VPI 151 to 160). The default value for the VPI range is 0, meaning no VPIs are assigned.
If the cnfport CAC Override flag is disabled, the Port cannot be overbooked by the connections terminating on that Port. If CAC Override flag is enabled, overbooking is allowed. Overbooking means allocating bandwidth to connections on a Port, where their total bandwidth allocation is greater than bandwidth minus CAC Reserve. Booking can exceed bandwidth and also the bandwidth of the port. But traffic throughput can never exceed bandwidth.
Figure 9-3 shows the types of bandwidth that make up the port's total bandwidth as configured by cnfport.
The total port bandwidth is the bandwidth of the port. It is configured by the cnfport command. Its units are cells per second. If there are multiple ports on a line (physical interface), then the sum of the "Total Port Bandwidths" on that line is limited to be less than or equal to the line speed.
For BXM T3 lines the line speed is based on the framing, PLCP or HEC, and can be reconfigured using the cnfln command.
The AutoRoute Bandwidth is the bandwidth that can be used by AutoRoute connections. It is user configured via the cnfrsrc command. Its units are cells per second. It can never be larger than the total port bandwidth.
The VSI bandwidth is the bandwidth that is currently used by the VSI partitions. It is a calculated value based on the VSI min- BW and max- BW values. Its units are in cells per second. It is "configurable by the user" when the min- BW and max- BW values are modified via the cnfrsrc command. When being configured, the min- BW and max- BW parameters cannot be set so that they would consume more than Total Port Bandwidth - AutoRoute Bandwidth.
The unused bandwidth is whatever is left over. This occurs if some of the nonAutoRoute bandwidth is unused by VSI.
The BXM card has 31 Virtual Interfaces (VIs). These VIs can be used for Virtual Ports, Virtual Trunks, Physical Ports or Physical Trunks.
1. The maximum number of interfaces (Virtual/Physical Port/Trunk) per BXM is equal to the maximum number of VIs. Therefore, a maximum of 31 (BXM) Virtual Ports are supported per card. The maximum number of Virtual Ports is 31 (BXM), but the number of available Virtual Ports can be lower based on the number of other interface types in use.
2. A maximum of 254 ports (physical or virtual), are supported on the BPX node with the BCC 4-128 controller. A maximum of 144 Virtual Ports will be supported on a BPX node running the BCC 3-64 controller. Virtual Ports are not supported on controllers lower than BCC 3-64 (BPX). The maximum Virtual Ports available will be reduced by the number of Physical Ports on the system.
3. Some port parameters are physical, and therefore when they are changed on one Virtual Port, they will change the same parameter on all other Virtual Ports that reside on the same Physical Port. Others apply only to the Virtual Port. A description of all the parameters is listed in Table 9-17.
4. The total number of connection channels per card is shared by all interfaces on the card. The number of channels used by all the interfaces on a card cannot exceed the total number of channels on the card. The number of channels on a given interface is further limited by the port group to which it belongs.
5. The number of port groups limits the number of channels that may be used on an interface. For example, consider an 8-port BXM card with two port groups and a total of n channels. Each port group may access a pool of n/2 channels. Each port may only access the channels in its port group, so each interface is limited to a maximum of n/2 channels.
6. The total bandwidth per Physical Port is shared by all the Virtual Ports on that Physical Port. The bandwidth sum of all the Virtual Ports on the Physical Port cannot exceed the bandwidth of the Physical Port.
7. Queue depth per port is shared by all the logical (Physical/Virtual Port/Trunk) interfaces on the card. The queues are dynamic, which allows oversubscription of the available queue space. The sum of all the configured queue depths may be larger than the available queue space on the card.
a. T1 (UXM card only) 3,622 cells/second
b. T3 (PLCP mode) (BXM) 96,000 cells/second
c. T3 (HEC/Direct mapping mode) (BXM) 104,000 cells/second
d. E3 (BXM) 80,000 cells/second
e. OC3 (BXM) 353,208 cells/second
f. OC12 (BXM) 1,412,830 cells/second
8. Virtual Port traffic shaping is always ON, connection shaping is configurable per QOS.
Virtual ports are available on the BXM card for the BPX. This feature is included in BPX Switch Software 9.3.0. and is independent of firmware. Virtual ports are not supported on ASI card connections.
On the BPX, this feature requires:
1. BCC 3-64 or BCC 4-128 controller card
2. BXM card
Virtual Ports (Figure 9-4) are virtual interfaces like Virtual Trunks, Physical Trunks, and Physical Ports. A Virtual Port will connect to CPE devices, directly or through an ATM cloud. A Virtual Port's bandwidth can be configured to the full Physical Port bandwidth or a subset thereof. However, the bandwidth sum of all Virtual Ports on a Physical Port cannot exceed the Physical Port's total bandwidth.
Virtual Ports have traffic shaping at the Virtual Port level as well as at the connection level. Currently, only connection traffic shaping is available. The purpose of this feature is to provide the second level of traffic shaping, Virtual Port traffic shaping.
This section describes two of the many possible examples of virtual port configurations.
Type I Virtual Ports can have PVP or PVC connections terminating on it. All traffic through this Virtual Port is constrained to the Virtual Port's configured bandwidth (Virtual Port shaping). Moreover, if connection shaping is enabled (per QOS), each connection will be constrained to its PCR and be given a fair chance to transmit by using WFQ (Weighted Fair Queuing).
Type II Virtual Ports have PVC connections all with the same VPI terminating on it. As with the type I Virtual Port above, all traffic through this port is constrained to the Virtual Port's configured bandwidth. If connection shaping is enabled, each connection will be constrained to its PCR and undergo WFQ.
Software does not distinguish between the two types of Virtual Ports.
Depending on the interface type, UNI or NNI, the maximum number of PVPs will be 255 or 4095 respectively. The maximum number of PVCs is 65535.
Configure Port
cnfport <slot.port>[.<vport>] [<params>]
upport, dnport, dspport, dspports, delport, addport
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
cnfport 3.2.1 11393 N H N 0 N 100 100
Configure port 2 (and virtual port 1) on the BPX card in slot 3.
cnfport 3.6 353208 N H i 0 16 N N N 30 3 4 Y N 0 N N
Configure port 6 on the BPX card in slot 3.
cnfport 3.6 353208 N H L0 31 N 10 10 10 5 5 N 0 N N
Configure port 6 on the BPX card in slot 3.
cnfport 3.6 353208 N H N N 0 N
Configure port 6 on the BPX card in slot 3.
cnfport 5.1 N N N N
Configure port, when used with an IMA line, displays the IMA Port Group. It does not prompt for any new IMA configuration.
sw225 TRM StrataCom IGX 8420 9.3.a6 Mar. 10 2000 05:56 GMT Port: 5.1 [ACTIVE ] IMA Port Grp: 1-4 Interface: E1-IMA CAC Override: Enabled Type: UNI %Util Use: Disabled Speed: 17962 (cps) SIG Queue Depth: 640 Protocol: NONE This Command: cnfport 5.1 NNI Cell Header Format? [N]: Protocol [N]: Apply Percent Utilization? [N]: CAC Override Disable? [N]:
| Parameter | Description | ||
|---|---|---|---|
slot.port[.vport] | Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI or UXM cards. | ||
nni/uni | Specifies whether the cell header format is NNI or UNI. UNI is the default. | ||
metro data cell header | Specifies whether the metro data cell header type is used (ASI-T3 cards only). | ||
VPI Range | BPX only: VPI Range is configurable on Virtual Ports and defaults to 0-255/4095 for Physical Ports (based on UNI/NNI type). The VPI Range cannot overlap with any other VPI Range on the physical interface. | ||
Bandwidth | BPX only: Bandwidth is configurable on all ports. For Virtual Ports, this parameter specifies the maximum bandwidth available for a Virtual Port. Each port has this parameter configurable. Connections within the Virtual Port may overbook the bandwidth if CAC Override is enabled, but the actual throughput will never be allowed to exceed the Virtual Port bandwidth. | ||
CAC Reserve | BPX only: CAC Reserve is configurable on all ports, but only valid if CAC Override is disabled. This parameter specifies the amount of AutoRoute Port Bandwidth not available for booking by connections if CAC Override is disabled. If CAC Override is enabled, overbooking is permitted. The purpose of this parameter is to reserve some bandwidth to handle bursts of traffic without cell discards. All ports have this parameter configurable. | ||
shift h | n | Specifies whether a one-byte shift on the HCF field of the cell header occurs. Changing the HCF field for a physical port will affect all virtual ports supported on the physical port. The choice of H (shift) or N (no shift) depends on whether the ATM cloud includes non-Cisco WAN Switching nodes and whether virtual trunking is in operation:
For BPX or IGX ports performing virtual trunking within an ATM cloud to external Cisco equipment, ports should be configured to shift on (that is, shift H) for BNI cards; BXM ports should typically be configured to shift off (shift N).
For example, if the public ATM cloud consists of BPX nodes, the access points to the cloud might be ASI ATM UNI ports. Because the cells transmitted to the ASI trunk interface are coming from a Cisco device, for example, a BNI card, the 16 VCI bits have already been left-shifted by four (4) bits and contain 12 bits of VCI information and four (4) bits of ForeSight information. Therefore, the ASI cards at either end of the cloud should be configured to not shift (that is, shift off). In this case, you would configure shift N on the ASI port. If the ATM cloud consists of non-Cisco nodes, then the 12 VCI bits + 4 ForeSight bits in the cells coming from the BNI card in the BPX are then passed through untouched as 16 VCI bits. Because it is a non-Cisco network, the ForeSight bits are ignored. Make sure that you set the HCF field correctly for your network configuration before you add connections. For example, if you are acting as a service provider, and one of your customers wants to configure virtual trunking through the network, if your ports have been previously configured with the incorrect HCF shift field setting, you may need to go back and delete all the connections from each port, configure the port, and add the connections again. Below are guidelines on how to set the Shift parameter when using BNI virtual trunking through a cloud of Cisco equipment using BXMs, and a cloud using ASIs and BNIs. Also shown is how to set the Shift parameter when using either BXM or UXM virtual trunking through a cloud of Cisco equipment (BXM cards), and a cloud of ASIs and BNIs. | ||
| | ||
protocol | Specifies the use of either an LMI protocol, an ILMI protocol, or no specified protocol. No specified protocol is the default. This parameter is not configurable for virtual ports. By default, this setting is No for virtual ports. Values for protocol are one of the following: N-(NONE) L-(LMI) I-(ILMI) Note: An IMA configuration will display the same protocol values as shown above. | ||
%util | Enables/disables percent utilization. This parameter supports ATM VBR/ABR fairness for ASI terminated connections and applies to only VBR and ABR connections. To change the %util status of a port, no connections can be currently terminating on the port. Therefore, if connections terminate on the port, they must be deleted before cnfport execution then re-added after execution of cnfport. When this feature is disabled, the port queue bandwidth is calculated using the sum of the MCRs or PCRs for the connections terminating on the port. This is identical to the port queue bandwidth calculation prior to the implementation of the %util feature. The port queue bandwidth with %util feature disabled is:
When the %util feature is enabled, the port queue bandwidth is calculated for ABR and VBR connections as follows: for ABR connections, the port queue bandwidth is the sum of a percentage of the MCRs for the connections terminating on the port; for VBR connections, the port queue bandwidth is the sum of a percentage of the PCRs for connections terminating on the port. The feature is not applied to CBR connections. In summary, the port queue bandwidth with feature %util enabled is:
For virtual ports, parameter can be set to Enable or Disable and is only pertinent to the specific virtual port. | ||
CAC Override | This can be set to Enable or Disable for the specific port. | ||
Protocol by Card | This indicates whether the Protocol (LMI, ILMI) selected is to be run on the BXM card.. |
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.
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.
In Release 9.3.0 , you can enable connection shaping for BXM queues. (Refer to the Hierarchical. Traffic Shaping on the BXM Card.)
Configure Port Queue Parameters
cnfportq <slot.port>[<.vport>] [<params>]
upport, dnport, dspportq
| Privilege | Jobs | Log | Node | Lock |
2 | Yes | Yes | IGX, BPX | Yes |
cnfportq 9.1 0 800 80 60 60 D 10000 80 60 60 D 10000 80 60 60 D 20
000 80 60 20 D
Configure port 9.1 to the parameters indicated for a BXM card.
sw215 TN Cisco BPX 8620 9.3.f9 May 31 2000 09:35 GMT
Port: 9.1 [ACTIVE ]
Interface: LM-BXM
Type: NNI
AR Bandwidth: 96000 (cps)
SVC Queue Pool Size: 0
QUEUE DEPTH CLP HI CLP LO EFCI VC SHAPE
/EPD
CBR 800 80% 60% 60% DISABLED
rt-VBR 10000 80% 60% 60% DISABLED
nrt-VBR 10000 80% 60% 60% DISABLED
UBR/ABR 20000 80% 60% 20% DISABLED
Last Command: cnfportq 9.1 0 800 80 60 60 D 10000 80 60 60 D 10000 80 60 60 D 20
000 80 60 20 D
Next Command:
cnfportq 3.2.15 0 600 80 60 60 D 5000 80 60 60 D 5000 80 60 60 D 000 80 60 20 D
Configure a port queue for a virtual port on the BPX card in slot 3.
| Parameter | Description |
|---|---|
slot.port[.vport] | Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI or UXM cards. |
nni/uni | Specifies whether the cell header format is NNI or UNI. UNI is the default. |
cbr queue parms | Specifies the CBR queue parameters of depth, cbr-hi, cbr-lo, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others. |
nrt-vbr queue parms | Specifies the nrt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others. |
rt-vbr queue parms | Specifies the rt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others. |
ubr/abr queue parms | Specifies the ABR queue parameters of depth, abr-hi, abr-low, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others. |
| Parameter | Description |
|---|---|
slot.port[.vport] | Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI or UXM cards. |
nni/uni | Specifies whether the cell header format is NNI or UNI. UNI is the default. |
cbr queue parms | Specifies the CBR queue parameters of depth, cbr-hi, cbr-lo, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. |
nrt-vbr queue parms | Specifies the nrt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. |
rt-vbr queue parms | Specifies the rt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. |
ubr/abr queue parms | Specifies the ABR queue parameters of depth, abr-hi, abr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. UBR traffic shares this queue with the ABR traffic. |
| Parameter | Description |
|---|---|
slot.port[.vport] | Specifies the card slot, physical port, and optional virtual port (BXM card only). The optional vport identifier must be between 1-31 inclusive. |
VC traffic shaping, connection shaping | Weighted fair queuing (WFQ) can be enabled on a per QOS/Qbin basis. This field is only configurable for BXM cards that support VC shaping. As of Release 9.3.0, VC shaping for BXM cards is no longer enabled on a per line bases. It is now done on a per QBIN/QoS basis. Enable/disable connection shaping within a virtual port. This feature is based on QOS. For example, all CBR connections can have traffic shaping, but all ABR connections may have traffic shaping disabled. The default setting is disabled. |
|
Note The total queue size of the UXM card is 97250 cells. |
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.
Delete Connections
delcon <channel(s)>
addcon, dspcon, dspcons
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
delcon 4.1.1.4
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.
ca19 VT SuperUser BPX 15 9.2 Aug. 23 1997 20:36 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 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 VBR 0 R 4.2.1.1 ca20 12.2.1.1 Ok CBR 0 L 4.2.1.2 ca20 12.2.1.2 Ok VBR 0 L 4.2.1.3 ca20 12.2.1.3 Ok ABR 0 L Last Command: delcon 4.1.1.4 Delete connections? (y) Next Command:
| Parameter | Description |
|---|---|
channel | Specifies the channel or set of channels for deleting connections, <channel> is specified in the following format: slot.port.vpi.vci |
Deletes a port (ASI, BXM, virtual, or physical port). Before deleting a port it must first be downed (dnport).
Delete Port.
delport <slot.port>[.<vport>]
addport, upport cnfport, dnport
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
Delete port 4 on the BXM card in slot 3.
delport 3.4
| Parameter | Description |
|---|---|
slot.port[.vport] | Specifies the slot number of the card, the physical port, and optional virtual ports (BXM card only). The optional vport identifier must be between 1-31 inclusive. |
Deactivates (or downs) the specified port (ASI, BXM, virtual, or physical port). Before downing a port, you must remove all connections from the port.
Down Port
dnport <slot.port>[.<vport>]
cnfport, dspport, upport, addport, delport
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
dnport 4.2
Down port 2 on the BXM card in slot 4.
ca19 VT SuperUser BPX 15 9.2 Aug. 23 1997 19:49 GMT ASI Port States Port State 4.1 ACTIVE 4.2 INACTIVE Last Command: dspports Next Command: dnport 4.2
dnport 3.5.1
Down port 5 (virtual port 1) on the BXM card in slot 3.
| Parameter | Description |
|---|---|
slot.port[.vport] | Specifies the slot number of the card, the physical port, and optional virtual port (BXM card only). The optional vport identifier must be between 1-31 inclusive. |
Display port Qbin information.
Display Port.
dport <slot.port>[.<vport>] qbn | *
addport, dspportq, cnfportq
| Privilege | Jobs | Log | Node | Lock |
1-2 | No | No | IGX, BPX | Yes |
Display Qbin database information for port 5 on BXM card 3.
dport 3.5.30 1
Display Qbin bandwidth database information for port 5 on BXM card 3.
dport 3.5.30 *
| Parameter | Description |
|---|---|
slot.port[.vport] | Specifies the slot number of the card, the physical port, and optional virtual port (BXM card only). The optional vport identifier must be between 1-31 inclusive. |
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.
Display ATM Connection Class
dspatmcls <class number>
addcon, cnfatmcls, dspcls, cnfcls, dspcon, dspcons
| Privilege | Jobs | Log | Node | Lock |
1-2 | No | No | IGX, BPX | No |
dspatmcls 1
Display the parameters for configuration class 1.
night TN SuperUser BPX 8620 9.2 July 28 1997 13:22 GMT
ATM Connection Classes
Class: 1
Type: VBR
UPC SCR IBS MBS ABR PCR ABR PCR
y 500/500 10/10 1000/1000 - 500/500 -/-
ICR ICR TO Rate Up Rate Dn Rate FastDn Max Adjust CDVT[in cells]
-/- - - - - - 64000/64000
EFCI % Util FGCRA MFS CLP CLP Hi CLP Lo BCM
100/100 100/100 n/n -/- y 100/100 100/100 n/n
Description: "Default VBR 500"
Last Command: dspatmcls 1
Next Command:
dspatmcls 1
Display the parameters for configuration class 1.
night TN SuperUser BPX 8620 9.2 July 28 1997 13:22 GMT
ATM Connection Classes
Class: 3 Type: rt-VBR
PCR(0+1) %Util CDVT(0+1) AAL5 FBTC SCR
2000/2000 100/100 10000/10000 n 2000/2000
MBS Policing
1000/1000 3
Description: "Default rt-VBR 2000"
Class: 4 Type: rt-VBR
PCR(0+1) %Util CDVT(0+1) AAL5 FBTC SCR
8000/8000 100/100 10000/10000 n 8000/8000
MBS Policing
1000/1000 3
Description: "Default nrt-VBR 8000"
Last Command: dspatmcls 1
Next Command:
| Parameter | Description |
|---|---|
class number | Specifies the class whose current parameters you want to see. Values are 1-10. |
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.
The system responses that follow display the following statistics categories:
Display Channel Statistics
dspchstats <channel> [interval]
clrchstats
| Privilege | Jobs | Log | Node | Lock |
5 | No | No | IGX, BPX | No |
dspchstats 4.1.50.1
Display the channel statistics for connection 4.1.50.1.
night TN SuperUser BPX 15 9.2 July 17 1997 02:46 GMT
Channel Statistics for 4.1.50.1 Cleared: July 13 1997 02:53 (|)
MCR: 0 cps Collection Time: 0 day(s) 18:10:22 Corrupted: NO
Traffic Cells CLP Avg CPS %util Discards: Cells
From Port : 14710 0 0 0 VcQ > CLP: 0
To Network : 14710 --- 0 0 VcQ Full : 0
From Network: 14710 --- 0 0 Qbin Full: 0
To Port : 14710 14710 0 0 Qbin> CLP: 0
Failed : 14710
OAM Cells RsrcOVL : 0
VC Q : 0 Tx OAM : 29608 NonCompliant: 0
Rx EFCI : 0 Rx AIS : 14710
Tx EFCI : 0 Rx FERF: 0 ForeSight Cells
Rx BCM : 0 Adj Up : 0
Tx BCM : 0 Adj Dn : 0
AAL-5 Frames: 0 Adj Fdn: 0
This Command: dspchstats 4.1.50.1
Hit DEL key to quit:
dspchstats 13.1.100 10
Display statistics for connection 13.1.100 with a 10-second interval between screen updates.
sw142 TN SuperUser IGX 16 9.2 July 31 1997 14:38 PDT
Channel Statistics: 13.1.100 Cleared: July 31 1997 11:50 (/)
MCR: 150 cps Collection Time: 0 day(s) 00:00:00 Corrupted: NO
Cells Avg Util
(cps) (%)
From Port: 0 0 0
To Network: 0 0 0
Discarded: 0 0 0
From Network: 0 0 0
To Port: 0 0 0
Discarded: 0 0 0
This Command: dspchstats 13.1.100
Hit DEL key to quit:
dspchstats 9.2.1.100
Display statistics for connection 9.2.1.100. The card in slot 9 is a UXM.
sw199 TN SuperUser IGX 16 9.0.s6 Aug. 28 1997 09:25 PDT
Channel Statistics: 9.2.1.100 Snapshot
Collection Time: 0 day(s) 13:28:47 Clrd: 08/27/97 19:47:24
Type Count
Cells Received from Port 0
Cells Transmitted to Network 0
Cells Received from Network 0
Cells Transmitted to Port 0
EOF Cells Received from Port 0
Cells Received with CLP=1 0
Cells Received with CLP=0 0
Non-Compliant Cells Received 0
Average Rx VCq Depth in Cells 0
Average Tx Vcq Depth in Cells 0
Cells Transmitted with EFCI=1 0
Cells Transmitted with EFCI=0 0
Ingress Vsvd Allowed Cell Rate 0
Egress Vsvd Allowed Cell Rate 0
OAM state (0:OK,1:FERF,2:AIS) 0
Good Pdu's Received by the Sar 0
Good Pdu's Transmitted by the Sar 0
Rx pdu's discarded by the Sar 0
Tx pdu's discarded by the Sar 0
Invalid CRC32 pdu rx by the sar 0
Invalid Length pdu rx by the sar 0
Shrt-Lgth Fail detected by the sar 0
Lng-Lgth Fail detected by the sar 0
Last Command: dspchstats 9.2.1.100
dspchstats 2.1.1.1 1
Display statistics for connection 2.1.1.1 (with a VPI of 1, and VCI of 1), and an interval of 1.
sw57 TRM StrataCom BPX 8620 9.2.zR Date/Time Not Set
Channel Statistics for 2.1.1.1 Cleared: Date/Time Not Set (\) Snapshot
MCR: 96000/96000 cps Collection Time: 0 day(s) 00:01:45 Corrupted: NO
Traffic Cells CLP Avg CPS %util Chan Stat Addr: 30EBB36C
From Port : 0 0 0 0
To Network : 0 --- 0 0
From Network: 0 0 0 0
To Port : 0 --- 0 0
NonCmplnt Dscd: 0 Rx Q Depth : 0 Tx Q Depth : 0
Rx Vsvd ACR : 0 Tx Vsvd ACR : 0 Bkwd SECB : 0
Bkwd Lost Cell: 0 Bkwd Msin Cell: 0 Bkwd BIPV : 0
Fwd SECB : 0 Fwd Lost Cell : 0 Fwd Msin Cell : 0
Fwd BIPV : 0
Last Command: dspchstats 2.1.1.1 1
Next Command:
CD Minor Alarm
dspchstats 10.1.205.101
Display statistics for connection 10.1.205.101 (with a VPI of 205 and VCI of 101).
m2a TN StrataCom IGX 8420 9.2.zR May 14 1998 14:19 GMT Channel Statistics: 10.1.205.101 Collection Time: 0 day(s) 23:02:58 Clrd: 05/13/98 14:33:00 Type Count Traffic Rate (cps) Cells Received from Port 82978 From port 0 Cells Transmitted to Network 82978 To network 0 Cells Received from Network 82978 From network 0 Cells Transmitted to Port 82978 To port 0 EOF Cells Received from Port 0 Cells Received with CLP=1 0 Cells Received with CLP=0 82978 Non-Compliant Cells Received 0 Average Rx VCq Depth in Cells 0 Average Tx Vcq Depth in Cells 0 Cells Transmitted with EFCI=1 0 Cells Transmitted with EFCI=0 82978 This Command: dspchstats 10.1.205.101
| Parameter | Description |
|---|---|
channel | Specifies the channel for statistics display, with format of slot.port.vpi.vci. |
| Parameter | Description |
|---|---|
interval | Specifies the interval (in seconds) between updates of the statistics display. If you specify an interval, you can either press Delete to terminate the command or wait until the command times out. The default is 10 seconds. If the Rx Q depth and the Tx Q depth fields remain "0", make sure that a value other than "0" is specified for the interval parameter. |
The table provides some statistics information regarding the BXM SAR. The switch software collects miscellaneous statistics regarding the Monarch SAR (Segmentation, Assembly, and Reassembly).
The following table 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.
| Object ID | Object Name | Range/Values | Default | Description |
|---|---|---|---|---|
01 | Message Tag | Byte 0-3 : Tag ID Byte 4-7 : IP Address | 0 | Identifier and source IP address sent with ComBus message. Both will be copied into the response, if any is to be sent. |
02 | Ingress Unknown AAL5 Discards | 0 - 232-1 | N/A | Number of unknown AAL5 PDUs discarded in the ingress. |
03 | Egress Unknown ALL5 Discards | 0 - 232-1 | N/A | Number of unknown AAL5 PDUs discarded in the egress. |
04 | Ingress Frame Ready FIFO Overruns | 0 - 232-1 | N/A | Number of ingress frame-ready FIFO overruns. |
05 | Egress Frame Ready FIFO Overruns | 0 - 232-1 | N/A | Number of egress frame-ready FIFO overruns. |
06 | Ingress Frame Ready FIFO Fulls | 0 - 232-1 | N/A | Number of ingress frame-ready FIFO fulls. |
07 | Egress Frame Ready FIFO Fulls | 0 - 232-1 | N/A | Number of egress frame-ready FIFO fulls. |
08 | Ingress Frame Ready FIFO Half-Fulls | 0 - 232-1 | N/A | Number of ingress frame-ready half-fulls. |
09 | Egress Frame Ready FIFO Half-Fulls | 0 - 232-1 | N/A | Number of egress frame-ready half-fulls. |
0A | Inverse ARP Requests Rcv | 0 - 232-1 | N/A | Number of inverse ARP requests received. |
0B | Inverse ARP Replies Rcv | 0 - 232-1 | N/A | Number of inverse ARP replies received. |
0C | Bad /errored ARP packets rcv | 0 - 232-1
| N/A | Number of invalid or unknown type ARP packets received. |
0D | Inverse ARP Requests Xmt | 0 - 232-1 | N/A | Number of inverse ARP requests transmitted. |
0E | Inverse ARP Replies Xmt | 0 - 232-1 | N/A | Number of inverse ARP replies transmitted. |
0F | Errored ARP packet Xmt | 0 - 232-1 | N/A | Number of invalid or unknown type ARP packets transmitted. |
10 | Bad LLC/NSAP PDUs Rcv | 0 - 232-1 | N/A | Number of illegal LLC/NSAP packets received. |
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.)
Display Connection Class
dspcls <class number>
addcon, cnfcls, dspcon, dspcons
| Privilege | Jobs | Log | Node | Lock |
1-2 | No | No | IGX, BPX | No |
dspcls 1
Display the parameters for configuration class 1.
night TN SuperUser BPX 8620 9.2 July 28 1997 13:22 GMT
ATM Connection Classes
Class: 3 Type: rt-VBR
PCR(0+1) %Util CDVT(0+1) AAL5 FBTC SCR
2000/2000 100/100 10000/10000 n 2000/2000
MBS Policing
1000/1000 3
Description: "Default rt-VBR 2000"
Class: 4 Type: rt-VBR
PCR(0+1) %Util CDVT(0+1) AAL5 FBTC SCR
8000/8000 100/100 10000/10000 n 8000/8000
MBS Policing
1000/1000 3
Description: "Default nrt-VBR 8000"
Last Command: dspatmcls 1
Next Command:
dspcls 1
Display the parameters for configuration class 1.
night TN SuperUser BPX 15 9.2 July 28 1998 13:22 GMT
ATM Connection Classes
Class: 1
Type: VBR
UPC SCR IBS MBS ABR PCR ABR PCR
y 500/500 10/10 1000/1000 - 500/500 -/-
ICR ICR TO Rate Up Rate Dn Rate FastDn Max Adjust CDVT[in cells]
-/- - - - - - 64000/64000
EFCI % Util FGCRA MFS CLP CLP Hi CLP Lo BCM
100/100 100/100 n/n -/- y 100/100 100/100 n/n
Description: "Default VBR 500"
Last Command: dspcls 1
Next Command:
| Parameter | Description |
|---|---|
class number | Specifies the class whose current parameters you want to see. Values are 1-10. |
Displays connection information for a specified channel. The information displayed includes:
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:
OK | Connection OK |
FAILED | Connection failed |
MISSING | VPI.VCI was deleted in other network at NNI. A previous status report indicated a valid VPI.VCI was present but an updated report did not. |
UNUSED | Indicates the UNI port does not support reporting of NNI A-bit status |
In Release 9.2 switch software for an IGX 8400 routing hub, dspcon does the following:
In Release 9.2.20, rt-VBR and nrt-VBR connection service types display separately.
Display Connections
dspcon <channel>
addcon, cnfcon, cnfpref, cnfrtcost
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | No |
dspcon 12.1.1.5
Display connection information for channel 12.1.1.5 (a VBR connection).
ca20 LAN SuperUser BPX 15 9.2 Aug. 29 1997 10:44 PST
Conn: 12.1.1.5 ca19 4.1.1.5 VBR Status: Down
SCR MBS PCR ABR PCR UPC FST CLP % util
1000/1000 10/10 500/500 --/-- y n y 100/100
Owner: LOCAL Restriction: NONE COS: 0
Group: NONE TestRTD: 16705 msec
Path: Downed by user
Pref: Not Configured
ca20 ASI-T3 : OK ca19 ASI-T3 : OK
Line 12.1 : OK Line 4.1 : OK
Last Command: dspcon 12.1.1.5
Next Command:
dspcon 12.1.1.4
Display connection information for channel 12.1.1.4 (CBR).
ca20 LAN StrataCom BPX 15 9.2 Aug. 29 1997 10:42 PST
Conn: 12.1.1.4 ca19 4.1.1.4 CBR Status: Down
PCR CDVT MCR ABR PCR UPC FST CLP % util
100/100 10/10 --/-- --/-- y n y 100/100
Owner: LOCAL Restriction: NONE COS: 0
Group: NONE TestRTD: 0 msec Trunk Cell Routing Restrict: Y Max Cost: 100 Route Cost:
36
Path: Downed by user
Pref: Not Configured
ca20 ASI-T3 : OK ca19 ASI-T3 : OK
Line 12.1 : OK Line 4.1 : OK
Last Command: dspcon 12.1.1.4
Next Command:
dspcon 12.1.1.100
Display connection information for channel 12.1.1.100 (an ABR connection).
ca20 LAN SuperUser BPX 15 9.2 Aug. 29 1997 10:31 PST
Conn: 12.1.1.100 ca20
SCR MBS MCR ABR PCR UPC FST CLP % util
20000/20000 50/50 20000/20000 96000/96000 y y y 100/100
ForeSight RTD: 0 msec
Path: Route information not applicable for local connections
ca20 ASI-T3 : OK ca20 ASI-T3 : OK
Line 12.1 : OK Line 12.2 : OK
Last Command: dspcon 12.1.1.100
Next Command:
dspcon 4.1.2.1
Display connection information for channel 4.1.2.1 (an ATFST connection).
sw53 TN SuperUser BPX 8620 9.2 July 26 1997 13:40 GMT
Conn: 4.1.2.1 sw53 4.3.2.1 atfst Status: OK
SCR MBS MCR ABR PCR UPC FST CLP % util
25/25 1000/1000 25/25 25/25 y y y 100/100
ForeSightRTD: 0 msec
Path: Route information not applicable for local connections
sw53 BNI-T3 : OK sw53 BNI-T3 : OK
Line 4.1 : OK Line 4.3 : OK
OAM Cell RX: Clear NNI : OK
NNI : OK
Last Command: dspcon 4.1.2.1
Next Command:
dspcon 12.1.1.*
Display connection information for channel 12.1.1.* (a CBR VP tunnelling DAX connection).
sw224 TRM IGX 8420 9.2.a5 Mar. 5 1999 11:10 PST
Conn: 12.2.1.* sw224 12.1.1.100 cbrvp Status:OK
PCR(0+1) % Util CDVT(0+1) Policing
1000/1000 100/100 10000/10000 4/4
Pri: L Test-RTD: 0 msec
Path: Route information not applicable for local connections
sw224 UXM: OK sw224 UXM: OK
Line 12.2 : OK Line 12.1 : OK
OAM Cell RX: Clear NNI: OK
NNI: OK
This Command: dspcon 12.2.1.*
| Parameter | Description |
|---|---|
channel | Specifies the channel for which to display connection details. The command displays connection information for one channel at a time. You cannot specify a set of channels. Channel is specified in the following format: slot.port.vpi.vci |
Displays the following information for a connection's configuration:
The rt-VBR and nrt-VBR connection service types will display separately.
Display Connection Configuration
dspconcnf <channel>
addcon, dspcon, dspcons, delcon
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | BPX | No |
dspconcnf 3.1.1.1
Display the configuration for 3.1.1.1.
sw60 TN SuperUser BPX 8620 9.2 Date/Time Not Set
Conn: 3.1.1.1 sw60 3.1.1.1 abrstd
Description:
PCR(0+1) % Util MCR CDVT(0+1) AAL5 FBTC
96000/96000 100/100 96000/96000 10000/10000 n
Last Command: dspconcnf 3.1.1.1
Next Command:
dspconcnf 2.1.1.101
Display the configuration for 2.1.1.101.
sw60 TN SuperUser BPX 8620 9.2 Date/Time Not Set
Conn: 3.1.1.1 sw60 3.1.1.1 rt-vbr
Description:
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
---------- ------ --------- --------- -----
50/50 100/100 250000/250000 n 50/50
MBS Policing
---- ---------
500/500 3
Trunk Cell Routing Restrict: Y
Last Command: dspconcnf 3.1.1.1
Next Command:
| Parameter | Description |
|---|---|
channel | Specifies the channel for which to display connection configuration. The command displays connection information for one channel at a time. You cannot specify a set of channels. Channel is specified in the following format: slot.port.vpi.vci |
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-32 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. See the cnfoamlpbk and dspoamlpbk commands for more information.
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.
| Fields | Description |
|---|---|
Local Channel | The connection's channel at this node. |
Remote Node Name | The name of the node at the other end of the connection. |
Remote Channel | The connection's channel at the remote node. |
State | The state of the connection(s) are as follows. OK—routed Down—downed Failed—unrouted, but trying |
Type | The type of connection (nrt-vbr, cbr, abr, atfr, or atfst). |
Route Avoid | The type of lines to avoid when routing (satellite lines, terrestrial lines, lines with zero code suppression). |
COS | The Class of Service. |
Owner | The end of the connection in control of rerouting. |
ABRSTD=OFF | The policing value for the connection. |
Display Connections
dspcons [start_channel] [nodename] [-f] [-v] [-d] [-atfr] [-abit] [-fabit] [-fail] [-down]
where
start_channel | is the starting channel to display. |
nodename | specifies that connections for only the named node appear in the display. |
-f | specifies that the display shows Frame Relay connections only. |
-v | specifies that the display shows only voice connections. |
-d | specifies that the display shows only data connections (in Kbps). |
-atfr | specifies that the display shows Frame Relay-to-ATM interworking connections (as well as atfr with ForeSight). |
-abit | specifies that the display shows status of the A-bit. |
-fabit | specifies that the display shows only connections with failed A-bits. |
-down | specifies that the display shows only downed connections. |
|
Note Some parameters may cause other parameters not to appear. Therefore, if you specify all parameters, some do not appear. |
addcon, delcon
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | No |
dspcons 4.1.1.4
Displays all connections starting with 4.1.1.4.
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:
dspcons -abit
Display the A-bit status for all connections starting with 1.1.3.66.
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?
dspcons
Display connections.
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
dspcons -oam
Display connections that have failed the OAM loopback test.
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:
| 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 |
dspcons -tun
Display only VP tunnelling connections on that node.
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
Displays LMI statistics for a specified port.
Display LMI/ILMI Statistics
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. If available on the IGX or BPX node, the virtual port number can be used. |
none
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | No |
dsplmistats 3.6
Display LMI statistics for port 6 on the BXM card in slot 3.
| Parameter | Description |
|---|---|
slot.port[.vport] | Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI or UXM cards. |
| Parameter | Description |
|---|---|
clear | On a BPX node only, the optional clear argument clears the current statistics after dsplmistats executes. |
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
| Object ID | Object Name | Range/Values | Default | Description |
|---|---|---|---|---|
01 | Message Tag | Byte 0-3 : Tag ID Byte 4-7 : IP Address | 0 | Identifier and source IP address sent with ComBus message. Both will be copied into the response, if any is to be sent. |
02 | Port Number | 1 - 12 | R | Identifies the target port. If multiple port numbers are sent during the operation, then each port number object terminates the configuration for the string of objects for the previous port number. |
03 | Virtual Port # | 1 - 255 | R | Identifies the target virtual port. |
04 | Status Sync | 0 - Clear 1 - Get Status | R | Sync up ingress status information to bcc. |
05 | Session Status | 0 - Okay 1 - Failed | 0 | Indicates whether or not the ILMI/LMI session on this logical interface is failed. |
06 | BPX/Feeder IP Address | 0 - 232-1 | 0 | Valid for feeder connections. Indicates the IP address of the feeder. |
07 | BPX/Feeder Name | Byte 0..8 : String | N/A | Valid for feeder connections. Indicates the name of the feeder. |
08 | BPX/Feeder Serial Number | Byte 0..8 : String | N/A | Valid for feeder connections. Indicates the serial number of the feeder. |
09 | BPX/Feeder Alarm Status | 0 : Clear 1 : Minor 2 : Major | N/A | Valid for feeder connections. Indicates the alarm status of the feeder. |
0A | BPX/Feeder Line Rate | 0 - 232-1 | N/A | Valid for feeder connections. Indicates the line receive rate of the feeder. |
0B | BPX/Feeder LAN IP Address | 0 - 232-1 | 0 | Valid for feeder connections. Indications the LAN IP address of the feeder. |
0C-0F | RESERVED |
|
|
|
10 | ILMI Number of Get Req Rx'd | 0 - 232-1 | N/A | ILMI number of Get Requests received. |
11 | ILMI No. of Get Next Req Rx'd | 0 - 232-1 | N/A | ILMI number of Get Next Requests received. |
12 | ILMI No. of Get Next Req Tx'd | 0 - 232-1 | N/A | ILMI number of Get Next Requests transmitted. |
13 | ILMI No. of Set Req Rx'd | 0 - 232-1 | N/A | ILMI number of Set Requests received. |
14 | ILMI No. of Traps Rx'd | 0 - 232-1 | N/A | ILMI number of traps received. |
15 | ILMI No. of Get Resp. Rx'd | 0 - 232-1 | N/A | ILMI number of Get Responses received. |
16 | ILMI No. of Get Req. Tx'd | 0 - 232-1 | N/A | ILMI number of Get Requests transmitted. |
17 | ILMI No. of Get Resp. Tx'd | 0 - 232-1 | N/A | ILMI number of Get Responses transmitted. |
18 | ILMI No. of Traps Tx'd | 0 - 232-1 | N/A | ILMI number of traps transmitted. |
19 | ILMI Unknown PDUs Rx'd | 0 - 232-1 | N/A | ILMI number of unknown PDUs received. |
1A-1F | RESERVED |
|
|
|
20 | LMI No. of Status Tx'd | 0 - 232-1 | N/A | LMI number of Status transmitted. |
21 | LMI No. Update Status Tx'd | 0 - 232-1 | N/A | LMI number of Update Status transmitted. |
22 | LMI No. of Status Ack. Tx'd | 0 - 232-1 | N/A | LMI number of StatusAck. transmitted. |
23 | LMI No. of Status Enq. Rx'd | 0 - 232-1 | N/A | LMI number of Status Enquiries received. |
24 | LMI No. of Status Enq. Tx'd | 0 - 232-1 | N/A | LMI number of Status Enquiries transmitted. |
25 | LMI No. of Status Rx'd | 0 - 232-1 | N/A | LMI number of Status received. |
26 | LMI No. Update Status Rx'd | 0 - 232-1 | N/A | LMI number of Update Status received. |
27 | LMI No. of Status Ack. Rx'd | 0 - 232-1 | N/A | LMI number of StatusAck. received. |
28 | LMI No. of Invalid PDU Rx'd | 0 - 232-1 | N/A | LMI number of invalid PDUs received. |
29 | LMI No. of Invalid PDU Len. Rx'd | 0 - 232-1 | N/A | LMI number of invalid PDU lengths received. |
2A | LMI No. Unknown PDUs Rx'd | 0 - 232-1 | N/A | LMI number of unknown PDUs received. |
2B | LMI No. of Invalid IEs Rx'd | 0 - 232-1 | N/A | LMI number of Information Elements received. |
2C | LMI No. of Invalid T.ID Rx'd | 0 - 232-1 | N/A | LMI number of invalid Transaction IDs received. |
Displays detailed status on a single specified ATM port. A full description of these parameters is provided in the cnfport command.
Display Port
dspport <slot.port>
cnfport, upport, dnport, addport, delport
| Privilege | Jobs | Log | Node | Lock |
1-2 | No | No | IGX, BPX | No |
dspport 3.2.1
Display the status of BXM port 3.2.1.
dspport 3.4
Display the status of BXM port 3.4.
dspport 3.6
Display the status of BXM port 3.6.
dspport 7.2
Display the status of the primary link on port 2, slot 7, of an IMA line.
sw225 TN StrataCom IGX 16 9.3.00 Jun 19 1999 13:39 PST Port: 7.2 [ACTIVE ] IMA Port Group: 2-5 Interface: E1-IMA CAC Override: Enabled Type: UNI %Util Use: Disabled Speed: 13433 (cps) SIG Queue Depth: 640 Protocol: NONE Last Command: dspport 7.2
| Parameter | Description | ||
|---|---|---|---|
slot.port[.vport] | Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI or UXM cards. | ||
<??> | Display usable VPIs on a virtual port. | ||
VPI Range | BPX Only. VPI Range is configurable on virtual ports and defaults to 0-255/4095 for physical ports (based on UNI/NNI type). The VPI Range cannot overlap with any other VPI Range on the physical interface. | ||
Bandwidth | BPX Only: For Virtual Ports, this parameter specifies the maximum bandwidth available for a Virtual Port. Each port has this parameter configurable. Connections within the Virtual Port may overbook the bandwidth if CAC Override is enabled, but the actual throughput will never be allowed to exceed the Virtual Port bandwidth. | ||
CAC Reserve | BPX only: CAC Reserve is configurable on all ports, but only valid if CAC Override is disabled. This parameter specifies the amount of AutoRoute Port Bandwidth not available for booking by connections if CAC Override is disabled. If CAC Override is enabled, overbooking is permitted. The purpose of this parameter is to reserve some bandwidth to handle bursts of traffic without cell discards.All ports have this parameter configurable. | ||
shift h | n | Specifies whether a one-byte shift on the HCF field of the cell header occurs. Changing the HCF field for a physical port will affect all virtual ports supported on the physical port. The choiceof H (shift) or N (no shift) depends on whether the ATM cloud includes non-Cisco WAN Switching nodes and whether virtual trunking is in operation:
For BPX or IGX ports performing virtual trunking within an ATM cloud to external Cisco equipment, port should be configured to shift on (that is, Shift H) for BNI cards; BXM ports should typically be configured to shift off (shift N).
For example, if the public ATM cloud consists of BPX nodes, the access points to the cloud might be ASI ATM UNI ports. Because the cells transmitted to the ASI trunk interface are coming from a Cisco device, for example, a BNI card, the 16 VCI bits have already been left-shifted by four (4) bits and contain 12 bits of VCI information and four (4) bits of ForeSight information. Therefore, the ASI cards at either end of the cloud should be configured to not shift (that is, shift off). In this case, you would configure shift N on the ASI port. If the ATM cloud consists of non-Cisco nodes, then the 12 VCI bits + 4 ForeSight bits in the cells coming from the BNI card in the BPX are then passed through untouched as 16 VCI bits. Because it is a non-Cisco network, the ForeSight bits are ignored. Make sure that you set the HCF field correctly for your network configuration before you add connections. For example, if you are acting as a service provider, and one of your customers wants to configure virtual trunking through the network, if your ports have been previously configured with the incorrect HCF shift field setting, you may need to go back and delete all the connections from each port, configure the port, and add the connections again. Below shows some guidelines on how to set the Shift parameter when using BNI virtual trunking through a cloud of Cisco equipment using BXMs, and a cloud using ASIs and BNIs. Also shown is how to set the Shift parameter when using either BXM or UXM virtual trunking through a cloud of Cisco equipment (BXM cards), and a cloud of ASIs and BNIs. | ||
| | ||
protocol | Specifies the use of either an LMI protocol, an ILMI protocol, or no specified protocol. No specified protocol is the default. This parameter is not configurable for virtual ports. By default, this setting is No for virtual ports. Values for protocol are one of the following: N-(NONE) L-(LMI) I-(ILMI) Note: An IMA configuration will display the same protocol values as shown above. |
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 physical port number parameters, the display shows the detailed port queue configuration information.
Display AutoRoute Port Queue Configuration.
dspportq <slot.port>[<.vport>]
cnfportq
| Privilege | Jobs | Log | Node | Lock |
1-2 | No | No | IGX, BPX | No |
dspportq 13.2
Display the port queue configuration for IGX port 13.2.
dspportq 13.2
Display the port queue configuration for BPX virtual port 3.2.1.
| Parameter | Description |
|---|---|
slot.port[.vport] | Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI or UXM cards. |
ASI Parameters nni/uni | Specifies whether the cell header format is NNI or UNI. UNI is the default. |
cbr queue parms | Specifies the CBR queue parameters of depth, cbr-hi, cbr-lo, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others. |
nrt-vbr queue parms | Specifies the nrt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others. |
rt-vbr queue parms | Specifies the rt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others. |
ubr/abr queue parms | Specifies the ABR queue parameters of depth, abr-hi, abr-low, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others. |
UXM Parameters slot.port[.vport] | Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI or UXM cards. |
nni/uni | Specifies whether the cell header format is NNI or UNI. UNI is the default. |
cbr queue parms | Specifies the CBR queue parameters of depth, cbr-hi, cbr-lo, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. |
nrt-vbr queue parms | Specifies the nrt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. |
rt-vbr queue parms | Specifies the rt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. |
ubr/abr queue parms | Specifies the ABR queue parameters of depth, abr-hi, abr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. UBR traffic shares this queue with the ABR traffic. |
BXM Parameters slot.port[.vport] | Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI or UXM cards. |
nni/uni | Specifies whether the cell header format is NNI or UNI. UNI is the default. |
cbr queue parms | Specifies the CBR queue parameters of depth, cbr-hi, cbr-lo, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. |
nrt-vbr queue parms | Specifies the nrt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. |
rt-vbr queue parms | Specifies the rt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. |
ubr/abr queue parms | Specifies the ABR queue parameters of depth, abr-hi, abr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. UBR traffic shares this queue with the ABR traffic. |
Displays either all of the ports on the node, or if a slot is specified, all of the ports on the specified slot.
Display Ports
dspports [<slot>]
dspport, addport, upport, dnport, delport
| Privilege | Jobs | Log | Node | Lock |
1-2 | No | No | IGX, BPX | No |
dspports
Display the status of all the ports on the BXM card.
dspports 3
Display the status of BXM card slot 3.
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.
Display Port Statistics
dspportstats <slot.port>[.<vport>] [interval]
clrportstats
| Parameter | Description | ||
|---|---|---|---|
slot.port[.vport] | Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI or UXM cards. | ||
shift h | n | Specifies whether a one-byte shift on the HCF field of the cell header occurs. Changing the HCF field for a physical port will affect all virtual ports supported on the physical port. The choiceof H (shift) or N (no shift) depends on whether the ATM cloud includes non-Cisco WAN Switching nodes and whether virtual trunking is in operation:
For BPX or IGX ports performing virtual trunking within an ATM cloud to external Cisco equipment, port should be configured to shift on (that is, Shift H) for BNI cards; BXM ports should typically be configured to shift off (shift N).
For example, if the public ATM cloud consists of BPX nodes, the access points to the cloud might be ASI ATM UNI ports. Because the cells transmitted to the ASI trunk interface are coming from a Cisco device, for example, a BNI card, the 16 VCI bits have already been left-shifted by four (4) bits and contain 12 bits of VCI information and four (4) bits of ForeSight information. Therefore, the ASI cards at either end of the cloud should be configured to not shift (that is, shift off). In this case, you would configure shift N on the ASI port. If the ATM cloud consists of non-Cisco nodes, then the 12 VCI bits + 4 ForeSight bits in the cells coming from the BNI card in the BPX are then passed through untouched as 16 VCI bits. Because it is a non-Cisco network, the ForeSight bits are ignored. Make sure that you set the HCF field correctly for your network configuration before you add connections. For example, if you are acting as a service provider, and one of your customers wants to configure virtual trunking through the network, if your ports have been previously configured with the incorrect HCF shift field setting, you may need to go back and delete all the connections from each port, configure the port, and add the connections again. Below are guidelines on how to set the Shift parameter when using BNI virtual trunking through a cloud of Cisco equipment using BXMs, and a cloud using ASIs and BNIs. Also shown is how to set the Shift parameter when using either BXM or UXM virtual trunking through a cloud of Cisco equipment (BXM cards), and a cloud of ASIs and BNIs. | ||
| |
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IPX, IGX | No |
dspportstats 9.1
Display the statistics for ASI port 9.1.
sw215 TN Cisco BPX 8620 9.3.f9 May 31 2000 15:50 GMT
Port Statistics for 9.1 Cleared: May 26 2000 09:39
Port Speed: 96000 cps Collection Time: 5 day(s) 06:06:32 Corrupted: NO
Cells CLP (EFCI)
Rx Port: 454053 0 --
Tx Port: 454053 0 --
Unknown Addr : 3175 Rx OAM Cells : 454053 Rx Clp 0 Cells: 454053
Rx Clp 0 Dscd : 0 Rx Clp 1 Dscd : 0 Tx Clp 0 Cells: 454053
Tx OAM Cells : 454053 Rx RM Count : 0 Tx RM Count : 0
Lst Unk VpiVci: 0.0
This Command: dspportstats 9.1
Hit DEL key to quit:
dspportstats 3.2.1
Display the statistics for BXM port 3.2.1.
| Parameter | Description |
|---|---|
slot.port[.vport] | Specifies the slot number of the card, the physical port and optional virtual port (BXM card only). The optional vport identifier must be between 1-31 inclusive. |
| Parameter | Description |
|---|---|
interval | Specifies the refresh interval time for data. It can be specified between 1 and 60 seconds. The default interval is 1 second. For BPX only: Note that you must specify a value other than 0 for the "interval" parameter. Otherwise, the screen displayed for UXM and BXM cards will be just a snapshot—it will not be updated periodically. If the Rx Q depth and the Tx Q depth on the BXM and UXM cards remain "0", specify a value for the interval parameter other than 0. |
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.)
| Statistics Name in Cisco WAN Manager | Statistics ID |
|---|---|
Cell Buffer Overflow | 1 |
Cells Rx w/CLP discarded | 42 |
Cells Rx w/CLP=0 | 40 |
Cells Rx w/CLP=0 discarded | 41 |
Cells Tx w/CLP=0 | 43 |
Egress OAM Cell Count | 44 |
Egress RM Cell Count | 46 |
Get Request Rx | 17 |
Get Request Tx | 23 |
Get Response Rx | 22 |
Get Response Tx | 24 |
GetNext Request Rx | 18 |
GetNext Request Tx | 19 |
Ingress RM Cell Count | 45 |
Invalid LMI IE Rx | 38 |
Invalid LMI Rx | 35 |
Invalid LMI length Rx | 36 |
Invalid Transaction IDs | 39 |
Non-zero GFC Count | 2 |
Number of BCM Cell Rx | 10 |
Number of Cells Rx | 7 |
Number of Cells Rx w/CLP set | 8 |
Number of Cells Rx w/EFCI set | 9 |
Number of Cells Tx | 11 |
Number of Cells Tx w/CLP set | 14 |
Number of Cells Tx w/EFCI set | 15 |
OAM Cells Rx Count | 12 |
Rx AIS Cell | 5 |
Rx FERF Cell | 6 |
SetRequest Rx | 20 |
Status Ack Rx | 34 |
Status Ack Tx | 29 |
Status Enq Rx | 30 |
Status Enq Tx | 31 |
Status Rx | 32 |
Status Tx | 27 |
Trap Rx | 21 |
Trap Tx | 25 |
Tx Header Err Discard | 16 |
Tx Payload Err Due to BIP-16 Err | 13 |
Unknown LMI Rx | 37 |
Unknown LMI Tx | 26 |
Unknown VPI/VCI | 0 |
Update Status Rx | 33 |
Update Status Tx | 28 |
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.
Display Cost-based Route Cache
dsprtcache [index] [c]
[index] specifies the cache entry index
[c] specifies to clear the entire cache or a single entry
dspcon, cnfrtcost, cnfpref
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | No |
dsprtcache
Display route cache contents, and let you monitor and manually clear the cache.
pissaro TN StrataCom BPX 15 9.1 Jun. 18 1997 11:11 GMT Route Cache (Summary) Index Use No. Cost Delay Restrict Load VPC Hops RemoteNode
0 Yes ...1.......Yes No None VBR No 2 lautrec 1 Yes 6 Yes No *s BDB No 3 vangogh 2 Yes 9 Yes No None BDA No 3 matisse 3 Yes 3 Yes No *t BDB No 3 rousseau 4 Yes 1 Yes No None CBR No 3 seurat <- current
5 No 0 No No None --- No 0 ---
6 No 0 No No None --- No 0 ---
7 No 0 No No None --- No 0 ---
8 No 0 No No None --- No 0 ---
9 No 0 No No None --- No 0 ---
10 No 0 No No None --- No 0 ---
11 No 0 No No None --- No 0 ---
Last Command: dsprtcache Next Command:
| Parameter | Description |
|---|---|
index | Specifies a particular route entry within the cache. When used with the c parameter, the route is either displayed or cleared from the cache. |
c | Clears the cache, or if you also enter the index parameter, clears the route cache specified by the index number. |
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. Upport cannot be used on a virtual port unless the virtual port's VPI Range is configured (cnfport).
|
Note As of Release 9.3.0, upln no longer automatically configures a port. You can verify that the line has been activated by using the dsplns command. (See Chapter 5, "Setting Up Lines," for descriptions of upln and dsplns.) |
Up Port
upport <slot.port>[.<vport>]
dnport, cnfport, upln, addport, delport
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
upport 2.1
Activate port 1 on the BXM card in slot 2.
upport 10.4.2
Activate port 4 (virtual port 2) on the BXM card in slot 10.
| Parameter | Description |
|---|---|
slot.port[.vport] | Specifies the card's slot, physical port and optional virtual port (BXM card only) number to activate. The optional vport identifier must be between 1-31 inclusive. |
Posted: Fri Sep 29 13:30:38 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.