Table Of Contents
Functional Organization
New with Release 9.3.30
URM BC-2FE Back Card on the IGX
URM VSI Support on the IGX
URM Remote Router Configuration Feature on the IGX
TFTP Configuration Save and Restore Feature on the BPX and IGX
Trunk Incremental CDV Feature on BPX and IGX
Virtual Circuit (VC) Merge
CRC-4 Protection Feature on the IGX
AIS OAM Recognition Feature on BPX and IGX
Virtual Trunk Clock Source Synchronization Feature on BPX and IGX
800 Part Number Support for Back Card Feature on BPX and IGX
Virtual Port ILMI Enhancement on the BPX
Concurrent Routing on the BPX and IGX
60K Channel Support for VSI on the BPX
F4 to F5 Mapping Feature on the BPX
Automatic Routing Management to PNNI Migration
Network to Endpoint Connectivity Verification and Round Trip Delay Measurement
Basic User Interface
Setting Up Nodes
Setting Up Lines
Setting Up Trunks
Voice Connections
Data Connections
Frame Relay Connections
ATM Connections
Universal Router Module
Optimizing Traffic Routing and Bandwidth
Synchronizing Network Clocks
Managing Jobs
Managing the Network
Statistics
Troubleshooting
Error Information
VSI Commands
Summary of IGX VSI Commands
Summary of BPX VSI Commands
SuperUser Commands
Command Aliases
Functional Organization
This chapter provides an overview of the features introduced in Release 9.3.30 for the BPX and IGX. The chapter also groups related commands according to general functional usage. These functional groupings are listed below.
•
Basic User Interface
• Setting Up Nodes
• Setting Up Lines
• Setting Up Trunks
• Voice Connections
• Universal Router Module
• Data Connections
• Frame Relay Connections
• ATM Connections
• Universal Router Module
• Synchronizing Network Clocks
• Managing Jobs
• Managing the Network
• Statistics
• Troubleshooting
• Error Information
• VSI Commands
• VSI Commands
• SuperUser Commands
• Command Aliases
The Type column of the command tables shows whether the command is for the BPX or IGX switches, and whether it is a SuperUser (SU) command.
New with Release 9.3.30
With Release 9.3.30, the BPX and IGX switch software supports several new features. On overview of each feature is presented in the following sections.
URM BC-2FE Back Card on the IGX
Release 9.3.30 provides support for the new BC-2FE back card for the IGX Universal Router Module (URM). The BC-2FE back card provides two Fast Ethernet (FE) ports that support 100 Mbps Ethernet. The URM front card and BC-2FE back card combination supports IOS-routing functions only. The URM front card and BC-2FE2V back card combination introduced in Release 9.3.20 continues to support both IOS-based voice and routing functions.
There are a couple precautions regarding the use of the BC-2FE back card.
•The BC-2FE back card is not swappable.
•The BC-2FE back card should be inserted first into the chassis, then the URM front card. (This sequence also applies to the BC2FE2V back card. Insert the back card, then the URM front card.)
For more information about BC-2FE card, refer to the Cisco IGX 8400 Series Provisioning Guide.
The CLI commands modified to support the new URM BC-2FE back card are listed below.
dspcd (display card)
|
In addition to other card information, now displays detailed information about the new URM BC-2FE back card.
|
dspcds (display cards)
|
In addition to other card information, now displays the new URM BC-2FE back card.
|
URM VSI Support on the IGX
Release 9.3.30 introduces support for the Virtual Switch Interface (VSI) feature on the IGX URM. The VSI feature and usage on the URM is the same as for VSI on the UXM interface card, except that the URM does not support trunks, or IMA lines and trunks. An NPM with 4M BRAM and 64M RAM is required to support this feature. Existing CLI commands are used to configure VSI on the URM embedded UXM ATM port. These commands configure the VSI controller, VSI slave, VSI partition, service class template (SCT), and VSI Qbin statistics. For a complete list of these VSI commands, see the "VSI Commands" section. The IOS CLI VSI xtag commands are used to configure the URM embedded router.
URM Remote Router Configuration Feature on the IGX
The Release 9.3.30 Remote Router Configuration feature allows you to start up the URM embedded IOS router with an IOS configuration file that is downloaded from a TFTP server and stored in the URM Admin flash. This feature eliminates the need to have console access to the embedded router to perform initial configuration. Once the IOS configuration file is stored in the URM, it can be used repeatedly upon router reset or restart. The IOS configuration file can have a configuration to enable access to the router from standard TCP-based applications, such as telnet, FTP, and TFTP.
The new and modified CLI commands used to support the URM Remote Router Configuration feature are listed below. For detailed information on the URM Remote Router Configuration feature, see cnfrtr (configure router configuration parameters), page 3-405.
TFTP Configuration Save and Restore Feature on the BPX and IGX
In releases prior to 9.3.30, the configuration save and restore facility used a proprietary protocol for communication between the nodes and CWM only. With the Release 9.3.30 TFTP Configuration Save and Restore facility, the standard TFTP protocol can be used to backup configuration files to a network server other than CWM. The network server can be any machine that is connected to a LAN attached to the network, has a TFTP server and disk, and is used to store configuration files. Configuration files that are saved using the TFTP method can be restored using the proprietary method, and vice versa, as long as the files are stored in the correct directory with the correct file names assumed by the proprietary protocol.
The TFTP Configuration Save and Restore facility includes a TFTP Start file interface for initiating a configuration save and restore request. The TFTP Start file naming convention is:
dnld.savecnf
|
for the Save operation
|
dnld.loadcnf
|
for the Restore operation.
|
Upon receipt of the TFTP Start file, the node drives the save and restore process in the same manner as it does with a CLI or SNMP request.
The default number of simultaneous sessions is 4, but the feature allows for up to 15 simultaneous TFTP Save/Restore operations. Use the default, then slowly increase the number of sessions to guard against any traffic congestion problems in your network(s).
The new and modified CLI commands used to support the TFTP Configuration Save and Restore facility are listed below. For detailed information on the feature, see the savecnf command description on page 4-446.
Note The TFTP Configuration Save and Restore facility also includes an SNMP interface for initiating configuration save and restore requests and reporting errors and status. This new interface allows the use of other network management platforms running SNMP managers for driving network management functionality in the WAN.
cnffwswinit (configure FW/SW download initiator IP address)
|
Specifies the IP address of the machine used to initiate a firmware or software download. This command now allows you to specify the IP address of the network server used to initiate the configuration save and restore operation using the TFTP Start file or SNMP interface.
|
cnfsysparm (configure system parameters)
|
Configures system-wide parameters. A new parameter is added to indicate the total number of nodes that can perform TFTP configuration data transfers simultaneously.
|
cnfnodeparm (configure node parameter)
|
Configures node-level parameters. A new parameter, IP Relay Gateway Node Number, is added to specify the number of the node that is to serve as the IP Relay Gateway to the TFTP target network server. The target network server must be reachable through the LAN from the configured IP Relay Gateway. The gateway can be the same on all nodes if a single target network server is used for all TFTP configuration backups. Multiple gateways and multiple target network servers can be used to decrease bottlenecks and the time required to back up the entire network.
|
savecnf (save configuration)
|
Takes a snapshot of the existing node configuration, saves it in RAM buffer files, then uploads the files to a network server, where they are stored on disk. Parameters are now expanded to allow configuration of the IP address of a network server other than CWM and specify TFTP for data transfer.
|
loadcnf (load configuration)
|
Downloads node configuration files from a network server to the node, where they are stored in the RAM buffer. Parameters are now expanded to allow configuration of the IP address of a network server other than CWM and specify TFTP for data transfer.
|
dspcnf (display configuration save/restore status)
|
Displays the save and restore status on each node in the network. The format of some node status messages are modified to support this feature. Specifically, the message substring "SV+ at <nodename>" is replaced with substring "IP address".
|
Trunk Incremental CDV Feature on BPX and IGX
The trunk cell delay variance (CDV) is particularly important for voice and non-time-stamped (NTS) connections, for which voice quality and bit datastream transparency must be maintained. The delay for a physical trunk is easily estimated as a function of the transmit queue size and transmit rate. However, the delay for a virtual trunk connected to a public ATM network is not easily estimated by the BPX/IGX network. Consequently, the CDV for virtual trunks is frequently over estimated, resulting in excessive latency for the connections.
The Release 9.3.30 Trunk Incremental CDV feature reduces the transmission latency introduced at the egress port of a voice or NTS connection, when the connection traverses over one or more trunks. With this feature, the BPX/IGX system estimates the CDV (estimated CDV) for voice and NTS virtual trunk connections as if they were physical trunk connections. The feature also allows you to configure an incremental CDV on both physical and virtual trunks.
When configured, the incremental CDV is added to the estimated CDV to derive the effective CDV. The effective CDV is used during connection routing to assure that the CDV tolerance specified for the connection is not exceeded. The effective CDV is also used to derive the jitter buffer size at the egress ports.
The CLI commands modified to support the Incremental CDV on Virtual Trunk feature are listed below. For additional information on this feature, see the cnftrk command description on 3-444.
Virtual Circuit (VC) Merge
VC merge improves the scalability of MPLS networks and allows multiple incoming VCs to be merged into a single outgoing VC, which is called merged VC. VC Merge is responsible for processing any incoming VSI messages from the MPLS controller and identifies the merging request. In the BPX 8600 series switch, VC Merge is implemented as part of the output buffering for ATM interfaces. The VC Merge feature requires the enhanced BXM (BXM-E) cards. Tag switching is supported.
Only frame-based connections are implemented.The key to VC Merge is to switch cells from the merging Label Virtual Circuit (LVC) to the merged LVC that points to the destination, while preserving AAL5 framing. Several AAL5 frames can arrive on different VCs and are merged onto a single VC without interleaving the frames.
If VC Merge is not supported on the card, N/A is displayed from the command cndcdparm.
cnfcdparm (configure card parameters)
|
Configures card parameters. The new index value 2 specifies VC merge. Enter either "E" to enable or "D" to disable the VC Merge feature.
|
cnfrsrc (configure resource)
|
Configures card resources. If the VC Merge feature is enabled under the command cnfcdparm, the feature is enabled by filling at least 1023 VSI channels on any interface on the card.
|
dspcd (display card)
|
Displays card information. VC merge support is indicated under VSI attributes supported with a "V."
|
CRC-4 Protection Feature on the IGX
ITU-T Recommendation G.704 provides for the optional use of a 4-bit CRC to protect the E1 framing structure. The Release 9.3.30 CRC-4 Protection feature allows you to enable/disable the CRC check on multiframed UXM E1 trunks and lines.
The CLI commands modified to support the CRC-4 Protection feature are listed below.
AIS OAM Recognition Feature on BPX and IGX
With the Release 9.3.30 AIS OAM Recognition feature, virtual trunks recognize receipt of end-to-end F4 OAM AIS alarms from the ATM service provider. Prior to Release 9.3.30,virtual trunks recognized ILMI traps/responses as a source of Virtual trunk path failure.
The AIS OAM Recognition feature is provided on BPX BXM and IGX UXM cards only. Virtual trunks in a VP-tunnelling configuration (IGX) are not supported.
The absence or presence of ILMI support from the ATM service provider does not affect the functionality of detecting F4 OAM AIS. Similarly, absence or presence of AIS indication from the ATM cloud does not affect the functionality of ILMI.
The Virtual Trunk Path Fail states have been expanded to distinguish between failures due to ILMI and AIS. The trunk states now include:
•Clear state
•Virtual Trunk Path Fail state due to ILMI trap
•Virtual Trunk Path Fail state due to AIS
•Virtual Trunk Path Fail state due to both ILMI and AIS
This feature provides a new entry point into the Virtual Trunk Path Failure alarm. Consequently, more connection rerouting may occur. You can use the cnftrk Trunk Deroute Delay timer to avoid excessive rerouting during brief outages.
The CLI commands modified to support the AIS OAM Recognition feature are listed below.
cnftrk (configure trunk)
|
Configures trunk parameters. A new parameter, F4 AIS Detection, is added to enable the AIS OAM Recognition feature.
|
dsptrkcnf (display trunk configuration)
|
Displays the parameter configuration for a trunk. The display now includes the new F4 AIS Detection parameter
|
dspcd (display card)
|
Displays support for the AIS OAM Recognition feature on the BXM ("F4F5" field) and UXM ("F4 AIS Recognition" field) cards.
|
dsptrks (display trunks)
|
Displays all trunks on a node. The Virtual Trunk Path Fail state alarms are expanded to distinguish between failures due to ILMI and AIS.
|
Virtual Trunk Clock Source Synchronization Feature on BPX and IGX
With the increased use of virtual trunks in Wide Area Networks, it is required that the clock source be derived from the ATM service provider for network synchronization. The Virtual Trunk Clock Source Synchronization feature associates the network clock source with the physical interface, rather than the virtual interface. This enables the use of all configurable virtual interfaces available on a physical trunk port as clock sources. When a virtual trunk fails, the clock source is not switched to another physical interface or internal clock source if there is another active, clock configurable virtual interface on the physical interface. This means that if at least one virtual trunk interface is up without any failure, the physical interface remains a sustainable clock source. This feature has no effect on regular, non-virtual trunks.
When a virtual trunk port is configured for clock source, the first virtual trunk interface on the trunk port is internally marked as the clock source. If the first virtual trunk interface on the trunk port fails, or becomes unusable as the clock source, the node searches for the next active virtual trunk interface that is usable as a clock source and marks that interface as the clock source. This virtual trunk search mechanism allows the clock source of the node to be associated with the physical trunk port rather than the physical interface. The clock selection mechanism within the same trunk port is transparent to the other nodes in the network, including the highest numbered node.
The CLI commands modified to support the F4 AIS Detection feature are listed below.
cnfclksrc (configure network clock source)
|
Configures a network-wide clock source. The prompts and error messages now support the Virtual Trunk Clock Source Synchronization feature.
|
dsplog (display event log)
|
Displays the event log for a node. The clock switch event log for local and remote node is modified for clock switches between physical interfaces. The virtual interface number is no longer included in the trunk address.
|
800 Part Number Support for Back Card Feature on BPX and IGX
This Release 9.3.30 feature enables display of the 800-level part number (also referred to as the Top Assembly Number, or TAN) for selected back cards. The 800 part number provides information about the back card that can assist with trouble shooting. Only the following back cards provide 800 part number support:
•BXM on the BPX
•URM, UXM, UFM, and UVM on the IGX
The 800 Part Number Support feature is not provided on controller back cards. Additionally, this feature does not provide the capability of writing the back card 800 part number.
The CLI commands modified to support the 800 Part Number Support for Back Card feature are listed below.
Virtual Port ILMI Enhancement on the BPX
The Virtual Port ILMI enhancement enables selection of the ILMI link management protocol on a BXM physical interface configured with virtual ports. Prior to Release 9.3.30, the ILMI protocol applied only to physical ports. LMI continues to be supported on BXM physical ports only.
Although ILMI can be enabled on the virtual ports, there is only one ILMI session per physical interface; meaning, an ILMI session only runs between the BXM physical interface and the ATM device to which it is directly connected. Similar to the existing ILMI implementation on the physical ports, the ILMI session on the BXM interface with virtual ports does not process incoming connection status traps.
ILMI configuration performed on one virtual port applies to all virtual ports on the same physical interface. When the protocol is enabled on a virtual port, ILMI processing is done only on the BXM card. You cannot configure the protocol to run on the controller card (BCC) with virtual ports.
The ILMI Neighbor Discovery feature on the BXM interfaces with virtual ports is only supported at the BPX switch level. There is currently no Cisco Wan Manager support for this feature. The cnfport CLI has been modified to allow users to configure ILMI on a virtual port.
The following parameters were applicable to physical ports only, they are now also applicable to virtual ports.
•Protocol (the only valid protocol for virtual ports is ILMI).
•VPI for ILMI connection
•VCI for ILMI connection
•ILMI Address Registration Enable
•ILMI Polling Enable
•ILMI Trap Enable
•ILMI T491 Polling Interval
•ILMI N491 Error Threshold
•ILMI N492 Event Threshold
•Protocol by the Card
•Advertise Interface Information (in previous releases, this parameter was known as Neighbor Discovery)
Concurrent Routing on the BPX and IGX
The Release 9.3.30 Concurrent Routing feature allows multiple route requests to be concurrently active on a node. This feature shortens network settling time (the time required for all connections in the network to reroute) by allowing multiple route requests to be accepted and serviced without blocking.
The maximum total number of concurrent routes is eight, and the maximum number of master routes is two. The second instance of the master route has to be path orthogonal to the first master route (i.e. with non-overlapping path). If the master node fails to find the second eligible route after a number of tries, it gives up the second route attempt—the second route is path blocked.
Concurrent routing also supports CPU throttling, a mechanism used to temporarily reduce routing concurrency when CPU utilization exceeds a defined threshold. The threshold is set by the cnfrrcpu command.
CLI commands modified to support the Concurrent Routing feature are listed below.
60K Channel Support for VSI on the BPX
The Release 9.3.30 60K channel support for VSI feature provides the capability to support up to 60K channels for VSI connections on trunk side, port side, or a combination of trunks and ports. The enhanced BXM-E card models DX and EX support up to 60K channels per card slot. In contrast, pre-release 9.3.30 switch software specifies that the total number of channels used by AutoRoute and VSI connections cannot exceed 32K. The maximum supported AutoRoute channels remains at 32K.
To upgrade a BXM-E card slot with 32K channel configuration, you can execute the new upgdvsilcn command. If you have a BXM card slot, and want to configure that slot to use the 60K channels feature, you have to follow the procedure for "Hitless Upgrade of BXM to BXM-E" documented in Release 9.3.00, then execute the new upgdvsilcn command.
Channel statistics level 0 or 1 is required for feature operation. If you execute upgdvsilcn with channel statistics levels 2 or 3, you receive the following error message: "Logical card does not support 60K LCN for VSI." Use the cnfcdparm command to specify the channel statistics level.
The new and modified CLI commands used to support the 60 channel support for VSI feature are listed below.
dspcd (display card)
|
Displays card detail. The command now displays the total channel number the physical BXM-E card can support.
|
dspcmi (service level command, not documented in this reference manual.)
|
Display the Total LCN for the Physical and Logical card.
|
dsplog (display event log)
|
Displays the event log for a node. Events are added to log configuration of 60K VSI LCN.
|
dsplogcd (service level command, not documented in this reference manual.)
|
Display the Maximum channel number used for the Autoroute Connection and VSI Connection. They are max_ar_lcn and max_vsi_lcn respectively.
|
upgdvsilcn (expand VSI LCN to 60K for BXM-E)
|
Configures the BXM-E card slot to support 60K VSI LCN. This is a new CLI command.
|
F4 to F5 Mapping Feature on the BPX
The F4 to F5 Mapping feature allows end-to-end OAM cell flow on a multi-segment PVC to enhance end-to-end connection management. The feature allows the path level OAM (F4 AIS) cells arriving at the VCC/VPC interface to be mapped to channel level OAM (F5 AIS) cells for all the VCC segments at the interface with the same VPI value. The VPC is provisioned by the ATM service provider. The VCCs are terminated at the BXM line port, which is the VPC/VCC interface. When the F4 to F5 Mapping feature is enabled on a BXM port, the BXM is programmed to detect F4 AIS for all the VPIs for which VCCs exist on that port. Consequently, F4 to F5 mapping is configured on a logical port basis. Mapping is not configured for VPIs on a logical port.
The modified CLI commands used to support the F4 to F5 Mapping feature are listed below.
addcon (add an ATM connection)
|
Adds connections. This command now displays error messages to support this feature.
|
cnfport (configure ATM port)
|
Configures port parameters. A new parameter, F4 to F5 Mapping, is added to enable/disable this feature. In addition, the number of F4-F5 channels on the port is displayed.
|
dspport (display port)
|
Displays port configuration. The command now displays the state of the F4 to F5 Mapping feature. In addition, the number of F4-F5 channels on the port is displayed.
|
dspcd (display card)
|
Displays support for the feature on the BXM card ("F4F5" field).
|
dspchuse (display channel usage)
|
Displays the channel distribution in a specified slot. This command now shows the number of channels used for F4-F5 mapping.
|
Automatic Routing Management to PNNI Migration
Release 9.3.30 supports the first phase of the Automatic Routing Management (AR) to Private Network-to-Network Interface (PNNI) migration. This release enables the introduction of PNNI networking software and MGX 8800 series routing switches into existing networks comprising BPX 8600 series routing switches running AR networking software.
The BPX 8600 supports both an Extended Permanent Virtual Connection (XPVC) and an Extended Permanent Virtual Path (XPVP) that spans over an AR-PNNI, or AR-PNNI-AR, hybrid network. This document concentrates on Extended Permanent Virtual Connections (XPVCs). Each XPVC can contain up to five segments that support various combination pairs of FR, ATM, and RPM endpoints. Each XPVC may contain feeder nodes such as MGX 8220, MGX 8230, MGX 8250, and Release 1 MGX 8850.
The UNI or NNI interface on each XPVC segment is enhanced and called Enhanced User-to-Network Interface (EUNI) or Enhanced Network-to-Network Interface (ENNI). The EUNI/ENNI allows segment OAM loopback cells to start from an edge of the hybrid AR-PNNI network and traverse through the multiple XPVC segments. When a fault is identified, CLI commands described in this document can be used at each EUNI/ENNI point to loopback OAM cells. Cisco recommends you use the Cisco WAN Manager (CWM) application to set up multi-segment OAM loopback. This OAM segmentation capability supports fault isolation in the AR-PNNI network.
With Release 9.3.30, the BXM card supports an Extended Local Management Interface (XLMI) protocol. The XLMI protocol, in conjunction with the LMI Neighbor Discovery feature, enables the exchange of connection status and topology information between the BPX and MGX switches in the AR-PNNI hybrid network.XLMI supports D bit, meaning that if a segment is automatically deleted, an AIS is sent to the Customer Premises Equipment (CPE). Abit operational status is not exchanged.
The Cisco WAN Manager (CWM) is required with Release 9.3.30. The CWM combines the XPVC segments into a single connection for simplified management. CWM must be used to add, modify, or delete a multi-segment XPVC (using the SNMP Service Agent proxy along with provided CWM-XPVC-CLI scripting capability). CWM must also be used to display the XPVC connection details. The CWM initiates test delay procedures and monitors the connection endpoints at the edge of the AR-PNNI network. CWM receives connection information from each network segment and reports the XPVC connection status.
The Release 9.3.30 AR-PNNI networking feature is compatible with the following network components:
•BPX software release 9.3.30 and above
•BXM firmware version MFH and above
•MGX release 2.1.60 and above
•AXSM with MGX2 release
•CWM release 10.5 and above
The following PVC endpoints are eligible on the AR network edge:
•BXM/ASI port
•BXM/BNI feeder to AXIS/MGX 8850 Release 1 with AUSM, FRSM, RPM, and PXM1 as endpoints
All connections supported on BPX software Release 9.3 with the above endpoints are supported in the AR-PNNI hybrid network. All feeders supported on BPX software Release 9.3 are supported in the AR-PNNI hybrid network.
The following network components are not supported:
•BXM/BNI feeder to AXIS/MGX 8850 Release 1 with VISM and CESM as endpoints
•BPX-SES in the PNNI network
With Release 9.3.30, the LMI Neighbor Discovery feature is only supported on BXM physical ports over the AR-PNNI link. LMI Neighbor Discovery is allowed only when the XLMI protocol runs on the BXM card. The XLMI protocol only runs on the BXM card and is only supported over the AR-PNNI link.
A maximum of 12 ports can be configured with the XLMI protocol per BXM card. The maximum number of ports that can have XLMI enabled on the BPX is 144 (12 BXM cards/BPX times 12 physical ports/BXM card).
The following features are not supported in Release 9.3.30:
•IP relay is not supported over the AR-PNNI link.
•VSI partition is not supported on EUNI/ENNI port types.
•BPX virtual ports cannot be configured as EUNI/ENNI port types.
The modified CLI commands used to support the AR-PNNI migration feature are listed below.
addyred (add Y-cable redundancy)
|
Performs XLMI Neighbor Discovery feature mismatch verification on a Y-cabled redundant BXM pair.
|
cnflan (configure LAN)
|
Sends the LAN IP address to the BXM when the XLMI protocol is enabled and the Management IP address is the LAN IP address.
|
cnfnodeparm (configure node parameter)
|
Configures the XLMI Management IP address as LAN IP address or Network IP address.
|
cnfnwip (configure network IP address)
|
Sends the Network IP address to the BXM when the XLMI protocol is enabled and the Management IP address is the Network IP address.
|
cnfoamseg (configure connection OAM segment status)
|
Configures the segment status of an XPVC segment in a hybrid AR-PNNI network. This is a new CLI command.
|
cnfport (configure ATM port)
|
Configures the BXM port type as EUNI/ENNI and enables both the XLMI protocol and LMI Neighbor Discovery feature. The command also performs LMI Neighbor Discovery feature mismatch verification on replacement BXM cards.
|
dspcd (display card)
|
Displays the BXM card's capability to support the XLMI protocol and LMI Neighbor Discovery feature.
|
dspcon (display connection)
|
Displays the local AR node connection details for an XPVC segment.
|
dspcons (display connections)
|
With the -abit parameter, displays the connection status of an XPVC segment at the AR-PNNI interfaces. "Abit" is not exchanged through XLMI between a BPX switch and an MGX Release 2 switch. The Abit display interpretation on MGX Release 2 and the BPX gateway node is changed. The abit display on the gateway BPX and the MGX Release 2 nodes means connection is missing on the neighbor network.
|
dspnebdisc (display neighbor discovery)
|
Displays the neighbor AXSM's topology information when the XLMI protocol and LMI Neighbor Discovery feature are enabled. The command also displays the protocol running on the BXM port, for example, ILMI or XLMI.
|
dspoamseg (display connection OAM segment status)
|
Displays the segment status of an XPVC segment in a hybrid AR-PNNI network. This is a new CLI command.
|
dspport (display port)
|
Displays the status and configuration of a BXM port terminating an XPVC segment.
|
tstcon (test connections)
|
Tests a multi-segment XPVC in the AR-PNNI hybrid network.
|
tstconseg (test connection segment)
|
Tests a multi-segment XPVC in the AR-PNNI hybrid network.
|
tstdelay (test connection round-trip delay)
|
Tests a multi-segment XPVC in the AR-PNNI hybrid network. The tstdelay command provides data continuity as well as delay measurement between the 2 edges of our network.
|
Network to Endpoint Connectivity Verification and Round Trip Delay Measurement
The network to endpoint loopback connectivity verification feature tests the data path for a connection from a BPX switch by generating and detecting end-to-end OAM loopback cells. You can verify the connectivity from the network to a PVC endpoint or a PVP endpoint, depending upon the type of connection on which the test is issued from the BPX switch. Unlike the command tstdelay, which tests connectivity "inside" the network, the new command tstpingoam tests connectivity going "out" of the network.
The tstpingoam command is useful for troubleshooting in a multi-provider network, as shown in Figure 2-1.
Figure 2-1 Multi-Provider Network
When an end user experiences connectivity or delay problems with a connection to an ATM network, there are multiple places where connectivity problems can occur. It is difficult to determine where the problem is located, and therefore, who has the responsibility to fix the problem. By giving each service provider the ability to establish connectivity with the CPE and measure delay, they can quickly narrow down which network has the problem, then work within that network to fix the problem.
The new or modified CLI commands used to support the network to endpoint loopback connectivity verification feature are listed below.
tstpingoam (network to endpoint loopback test)
|
Performs a network to endpoint loopback test of the data path for a connection from a BPX switch by generating and detecting end-to-end OAM loopback cells.
|
cnfcdparm (configure card parameters)
|
Provides for selection of O.151 OAM cell format (a non-standard format still used by some service providers) instead of the standard I.610 OAM cell format. Refer to this command if you need to change the OAM cell format used in the test.
|
tstconseg (test connection segment)
|
Used to test segment connectivity "outside" the network. The round trip delay measurement is added to this command display.
|
tstdelay (test connection round-trip delay)
|
Used to test connectivity "inside" the network. The round trip delay measurement is added to this command display.
|
Basic User Interface
The user interface commands:
•Provide help on how to use the commands
•Display the twelve most recent commands entered into the system
•Connect to another node
•Sign on and off
•Clear, print, or redraw the screen
These commands are all simple to use and have no command parameters except the virtual terminal command (vt), in which you must specify the node name, and the help commands, in which you must enter a command character string.
Command
|
Description
|
Type
|
Page
|
.
|
Display command history
|
BPX, IGX
|
3-1
|
bye
|
End user session
|
BPX, IGX
|
3-90
|
clrscrn
|
Clear screen
|
BPX, IGX
|
3-112
|
help or ?
|
Help
|
BPX, IGX
|
4-406
|
prtscrn
|
Print screen
|
BPX, IGX
|
4-429
|
redscrn
|
Redraw screen
|
BPX, IGX
|
4-434
|
vt
|
Make a virtual terminal connection
|
BPX, IGX
|
4-490
|
Setting Up Nodes
This group of commands are used to set up an IGX or BPX node. (You must set up each node before you build the network.) This group also contains commands to:
•Configure a node name and time zone.
•Add and remove a network node.
•Add and remove an interface shelf in a tiered network.
•View a node's configuration.
•Specify Y-cable redundancy for cards in the node.
•Start a window session to an external device or specify an interface to an attached terminal.
•Sending A-bit Notification on ILMI/LMI Using Configurable Timer
Command
|
Description
|
Type
|
Page
|
addalmslot
|
Add an alarm slot
|
BPX, IGX
|
3-3
|
addshelf
|
Add a trunk between an IGX or BPX core switch shelf and an interface shelf
|
BPX, IGX, MGX, SES
|
3-70
|
addyred
|
Add Y-cable redundancy
|
BPX, IGX
|
3-83
|
cnfasm
|
Configure ASM card
|
BPX, IGX
|
3-126
|
cnfdate
|
Configure date
|
BPX, IGX
|
3-198
|
cnffunc
|
Configure system function
|
BPX, IGX
|
3-228
|
cnfname
|
Configure node name
|
BPX, IGX
|
3-278
|
cnfprt
|
Configure printing functions
|
BPX, IGX
|
3-360
|
cnfterm
|
Configure terminal port
|
BPX, IGX
|
3-434
|
cnftime
|
Configure time
|
BPX, IGX
|
3-439
|
cnftmzn
|
Configure time zone
|
BPX, IGX
|
3-442
|
delalmslot
|
Delete alarm slot
|
IGX
|
4-3
|
delshelf
|
Delete a trunk between a IGX/BPX core switch shelf and interface shelf
|
BPX, IGX
|
4-19
|
delyred
|
Delete Y-cable redundancy
|
BPX, IGX
|
4-25
|
dspasm
|
Display ASM card configuration
|
BPX
|
4-47
|
dspcd
|
Display card
|
BPX, IGX
|
4-69
|
dspcdred
|
Display Y-cable redundancy (displays card redundancy for SONET Automatic Protection Switching). Alias for dspyred
|
BPX, IGX
|
4-77
|
dspcds
|
Display cards
|
BPX, IGX
|
4-78
|
dspctrlrs
|
Display all PNNI VSI controllers on a BPX node
|
BPX, IGX
|
4-153
|
dsplancnf
|
Display LAN configuration
|
BPX, IGX
|
4-179
|
dsplmistats
|
Display LMI Statistics
|
BPX, IGX/AF
|
4-185
|
dspnds
|
Display nodes
|
BPX, IGX
|
4-216
|
dspnode
|
Display summary information about interface shelves
|
BPX, IGX/AF
|
4-219
|
dspprtcnf
|
Display print configuration
|
BPX, IGX
|
4-273
|
dsppwr
|
Display power
|
BPX, IGX
|
4-275
|
dsptermcnf
|
Display terminal configuration
|
BPX, IGX
|
4-351
|
dsptermfunc
|
Display terminal port configuration
|
BPX, IGX
|
4-352
|
dspyred
|
Display Y-cable redundancy
|
BPX, IGX
|
4-402
|
prtyred
|
Print Y-cable redundancy
|
BPX, IGX
|
4-433
|
upcd
|
Up card
|
BPX, IGX
|
4-474
|
window
|
Window to external device
|
BPX, IGX
|
4-492
|
Setting Up Lines
A circuit line is the physical line that carries data, voice, Frame Relay, or ATM traffic between an IGX or BPX node and customer premises equipment (CPE). Each piece of customer premises equipment is attached to a node through a circuit line. After a card has been "upped" with the upcd command, a circuit line on that card can be "upped" and configured.
Line commands are the same as circuit line commands. However, the cnfcln command is no longer used; use cnfln instead. The switch software prompts for the parameters appropriate for the card type it detects.
Command
|
Description
|
Type
|
Page
|
cnfcassw
|
Configure CAS switching
|
IGX
|
3-141
|
cnfln
|
Configure line (alias for cnfcln)
|
BPX, IGX
|
3-242
|
cnfphylnstats
|
Configure physical line statistics
|
BPX, IGX, SU
|
3-306
|
cnfport
|
Configure a port
|
BPX, IGX
|
3-330
|
cnfrsrc
|
Configure resources
|
BPX, IGX
|
3-376
|
dnln
|
Down line (alias for dncln)
|
BPX, IGX
|
4-32
|
dsplncnf
|
Display line configuration (alias for dspclncnf)
|
BPX, IGX
|
4-191
|
dsplns
|
Display lines (alias for dspclns)
|
BPX, IGX
|
4-197
|
dspphylnstatcnf
|
Display physical line statistics configuration
|
BPX, IGX, SU
|
4-238
|
dspphylnstathist
|
Displays the physical line statistics history
|
BPX, IGX, SU
|
4-242
|
dspport
|
Displays information about a specific port.
|
BPX, IGX
|
4-244
|
dsptsmap
|
Display time slot map
|
BPX, IGX
|
4-390
|
prtlns
|
Print circuit lines (alias for prtclns)
|
BPX, IGX
|
4-425
|
upln
|
Up line (alias for upcln)
|
BPX, IGX
|
4-482
|
Setting Up Trunks
After you have configured the nodes, you must activate the trunks. Trunks are intra-node communication links in a network. A trunk can connect any combination of IGX or BPX nodes.
Before executing the commands in this section, you must have finished setting up the nodes. Also, the front and back cards that support the proposed line type and communication technology must reside in the slot intended for the trunk.
You cannot use a virtual trunk as an interface shelf (feeder) trunk; similarly, you cannot configure an interface shelf trunk to act as a virtual trunk, nor can you terminate interface shelf (feeder) connections on a virtual trunk.
Command
|
Description
|
Type
|
Page
|
addapsln
|
Add SONET APS line redundancy to a BXM OC-3 or OC-12 card
|
BPX
|
3-4
|
addtrk
|
Add trunk
|
BPX, IGX
|
3-79
|
addtrkred
|
Add trunk redundancy
|
BPX, IGX
|
3-81
|
cnfapsln
|
Configure APS parameters on a working line of redundant pair
|
BPX
|
3-123
|
cnfrsrc
|
Configure resources
|
BPX, IGX
|
3-376
|
cnftrk
|
Configure trunk
|
BPX, IGX
|
3-444
|
cnftrkalm
|
Configure trunk alarm
|
BPX, IGX
|
3-460
|
cnftrkict
|
Configure trunk interface control template
|
IGX
|
3-464
|
cpytrkict
|
Copy trunk interface control template
|
IGX
|
3-506
|
delapsln
|
Delete SONET APS line from a BXM OC-3 or OC-12 card
|
BPX
|
4-4
|
deltrk
|
Delete trunk
|
BPX, IGX
|
4-21
|
deltrkred
|
Delete trunk redundancy
|
IGX
|
4-23
|
dntrk
|
Down trunk
|
BPX, IGX
|
4-35
|
dspapsln
|
Display currently configured APS lines and their status
|
BPX
|
4-45
|
dspcntrstats
|
Display counter statistics for a given statistics object
|
BPX, IGX
|
4-124
|
dspnw
|
Display network
|
BPX, IGX
|
4-221
|
dspphyslns
|
Display lines in an IMA trunk
|
IGX
|
4-235
|
dspphyslnstathist
|
Display statistics gathered for lines in an IMA trunk
|
IGX
|
4-242
|
dsptrkbob
|
Display trunk breakout box
|
IGX
|
4-353
|
dsptrkcnf
|
Display trunk configuration
|
BPX, IGX
|
4-354
|
dsptrkict
|
Display trunk interface control template
|
IGX
|
4-364
|
dsptrkred
|
Display trunk redundancy
|
BPX, IGX
|
4-366
|
dsptrks
|
Display trunks
|
BPX, IGX
|
4-367
|
dsptrkstats
|
Display trunk statistics
|
BPX, IGX
|
4-376
|
prtapsln
|
Print the APS line redundancy switching interface
|
BPX
|
4-414
|
prtnw
|
Print network
|
BPX, IGX
|
4-427
|
prttrkict
|
Print trunk interface control template
|
IGX
|
4-431
|
prttrks
|
Print trunks
|
BPX, IGX
|
4-432
|
switchapsln
|
Control the APS line redundancy switching interface
|
BPX
|
4-453
|
uptrk
|
Up trunk
|
BPX, IGX
|
4-485
|
Voice Connections
The voice commands apply to setting up, configuring, and statistical reporting for voice connections (including FAX). You use these commands to add a voice connection, configure card redundancy, and optimize the use of voice activity detection (VAD).
Voice connections exist as ports on circuit lines supported by a Channelized Voice Module (CVM) or Universal Voice Module (UVM) in an IGX node. The back card for the CDP or CVM is either a BC-T1, BC-E1, or BC-J1. For the UVM, the back card is either a BC-UVI-2T1EC, a BC-UVI-2J1EC, or BC-UVI-2E1EC.
Command
|
Description
|
Type
|
Page
|
addcon
|
Add channel voice connection
|
IGX
|
3-96
|
cnfchadv
|
Configure channel adaptive voice
|
IGX
|
3-151
|
cnfchdl
|
Configure channel dial type
|
IGX
|
3-153
|
cnfchec
|
Configure channel echo canceller
|
IGX
|
3-155
|
cnfchfax
|
Configure fax modem detection for channels (UVM)
|
IGX
|
3-158
|
cnfchgn
|
Configure channel gain insertion
|
IGX
|
3-159
|
cnfcond
|
Configure conditioning template
|
IGX
|
3-192
|
cnfdch
|
Configure data connection to have idle code suppression enabled/disabled
|
IGX
|
3-200
|
cnflnpass
|
Configure line pass
|
IGX
|
3-260
|
cnfrcvsig
|
Configure receive signaling
|
IGX
|
3-370
|
cnfvchtp
|
Configure voice channel interface type
|
IGX
|
3-495
|
cnfxmtsig
|
Configure transmit signaling
|
IGX
|
3-501
|
delcon
|
Delete connection
|
BPX, IGX
|
4-5
|
dspchcnf
|
Display channel configuration
|
IGX
|
4-84
|
dspchdlcnf
|
Display channel dial type configuration
|
IGX
|
4-87
|
dspchec
|
Display channel echo canceller
|
IGX
|
4-89
|
dspcon
|
Display connection
|
IGX
|
4-127
|
dspcond
|
Display conditioning template
|
IGX
|
4-142
|
dspcons
|
Display connections
|
BPX, IGX
|
4-143
|
dspconst
|
Display connection state
|
IGX
|
4-151
|
dspsigqual
|
Display signal qualifiers
|
IGX
|
4-298
|
dspsvcst
|
Display voice SVC statistics
|
IGX
|
4-347
|
prtchcnf
|
Print channel configuration
|
IGX
|
4-416
|
prtchdlcnf
|
Print channel dial type configuration
|
IGX
|
4-417
|
prtcons
|
Print connections
|
IGX
|
4-419
|
Data Connections
These commands apply to setting up, configuring, and statistical reporting on data connections:
•Setting up a circuit line and a data connection
•Configuring data channel redundancy
•Using interface control templates
•Enabling DFM and data channel utilization
•Enabling Embedded EIA operation
•Configuring idle code suppression on a per-connection basis
Command
|
Description
|
Type
|
Page
|
addcon
|
Add a data channel connection
|
IGX
|
3-6
|
cnfchdfm
|
Configure Data Frame Multiplexing (DFM)
|
IGX
|
3-152
|
cnfcheia
|
Configure EIA
|
IGX
|
3-157
|
cnfcldir
|
Configure control lead direction
|
IGX
|
3-171
|
cnfdch
|
Configure data connection to have ICS (Idle Code Suppression)
|
IGX
|
3-200
|
cnfdchtp
|
Configure data channel interface type
|
IGX
|
3-205
|
cnfdclk
|
Configure data clock
|
IGX
|
3-207
|
cnfict
|
Configure interface control template
|
IGX
|
3-232
|
cpyict
|
Copy interface control template
|
IGX
|
3-504
|
delcon
|
Delete connection
|
BPX, IGX
|
4-6
|
dspchcnf
|
Display channel configuration
|
IGX
|
4-84
|
dspcons
|
Display connections
|
BPX, IGX
|
4-143
|
dspict
|
Display interface control template
|
IGX
|
4-175
|
prtchcnf
|
Print channel configuration
|
IGX
|
4-417
|
prtcons
|
Print connections
|
IGX
|
4-419
|
prtict
|
Print interface control template
|
IGX
|
4-421
|
Frame Relay Connections
The Frame Relay commands let you add, configure, delete, and specify statistical reporting for Frame Relay connections:
•Set up a Frame Relay connection
•Use Frame Relay classes
•Use interface control templates
•Configure channel utilization
•Set channel priorities
•Display statistics
In an IGX node, the Frame Relay commands operate on an FRM or UFM card set. For the Frame Relay commands that operate on an FRSM in an MGX 8220 shelf, refer to the Cisco MGX 8220 Command Reference.
Command
|
Name
|
Type
|
Page
|
addcon
|
Add Frame Relay connection
|
BPX, IGX
|
3-21
|
addport
|
Add Frame Relay port T1/E1. (The command addfrport is an older alias.)
|
IGX
|
3-61
|
clrchstats
|
Clear Frame Relay channel statistics
|
IGX
|
3-94
|
clrfrcportstats
|
Clear FRC/FRM Port Concentrator link statistics
|
BPX, IGX
|
3-99
|
cnfchpri
|
Configure Frame Relay channel priority
|
IGX
|
3-160
|
cnffrcls
|
Configure Frame Relay class
|
IGX
|
3-219
|
cnffrcon
|
Configure Frame Relay connection
|
IGX
|
3-222
|
cnffrcport
|
Configure Frame Relay port on a Port Concentrator Shelf
|
IGX
|
3-224
|
cnfict
|
Configure interface control template
|
IGX
|
3-236
|
cnfmode
|
Configure mode
|
IGX
|
3-273
|
cpyict
|
Copy interface control template
|
IGX
|
3-504
|
delcon
|
Delete connection
|
BPX, IGX
|
4-7
|
delfrport
|
Delete Frame Relay port using T1 or E1 Lines
|
IGX
|
4-11
|
dnfrport
|
Down Frame Relay port. An alias for dnport.
|
BPX, IGX
|
4-32
|
dspchcnf
|
Display channel configuration
|
IGX
|
4-86
|
dspchstats
|
Display channel statistics
|
BPX, IGX
|
4-95
|
dspcon
|
Display connection
|
IGX
|
4-131
|
dspcons
|
Display connections
|
BPX, IGX
|
4-143
|
dspfrcls
|
Display Frame Relay class
|
IGX
|
4-163
|
dspfrport
|
Display Frame Relay port. An alias for dspport
|
BPX, IGX
|
4-166
|
dspict
|
Display interface control template
|
IGX
|
4-175
|
dspmode
|
Display mode
|
IGX
|
4-213
|
dspmodes
|
Display modes
|
BPX, IGX
|
4-215
|
dsppcs
|
Display Port Concentrator Shelf
|
IGX
|
4-229
|
dspportids
|
Display port IDs
|
BPX, IGX
|
4-248
|
dspportstats
|
Display port statistics
|
BPX, IGX
|
4-259
|
prtchcnf
|
Print channel configuration
|
IGX
|
4-416
|
prtcons
|
Print connections
|
IGX
|
4-421
|
prtict
|
Print interface control template
|
IGX
|
4-422
|
upfrport
|
Up Frame Relay port. An alias for upport
|
BPX, IGX
|
4-477
|
ATM Connections
These commands 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, and to a UXM or URM in an IGX node. 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.
Command
|
Description
|
Type
|
Page
|
addcon
|
Add ATM connection
|
BPX, IGX
|
3-30
|
addport
|
Add ATM or Frame Relay port
|
BPX, IGX
|
3-61
|
clrchstats
|
Clear channel statistics
|
BPX, IGX
|
3-94
|
cnfatmcls
|
Configure ATM class template
|
BPX, IGX
|
3-128
|
cnfcls
|
Configure class template
|
BPX, IGX
|
3-179
|
cnfcon
|
Configure connection
|
BPX, IGX
|
3-222
|
cnfport
|
Configure ATM or Frame Relay port. (Use instead of older cnffrport alias.)
|
BPX, IGX
|
3-226
|
cnfportq
|
Configure port queue parameters
|
BPX, IGX
|
3-350
|
cnfrtr
|
Configure Universal Router Module embedded router
|
IGX
|
3-405
|
delcon
|
Delete connection
|
BPX, IGX
|
4-7
|
delport
|
Delete ATM port
|
BPX, IGX
|
4-17
|
dnport
|
Down port
|
BPX, IGX
|
4-33
|
dspatmcls
|
Display ATM connection class
|
BPX, IGX
|
4-48
|
dspchstats
|
Display all embedded statistics for a channel
|
BPX, IGX
|
4-95
|
dspcls
|
Display connection class
|
BPX, IGX
|
4-118
|
dspcntrstats
|
Display counter status statistics
|
BPX, IGX
|
4-124
|
dspcon
|
Display ATM connections
|
BPX, IGX
|
4-133
|
dspconcnf
|
Display connection configuration
|
BPX
|
4-140
|
dspcons
|
Display connections
|
BPX, IGX
|
4-143
|
dsplmistats
|
Display Annex G LMI statistics
|
BPX, IGX/AF
|
4-185
|
dspnebdisc
|
Display Neighbor Discovery
|
BPX, IGX
|
4-217
|
dspport
|
Display port
|
BPX, IGX
|
4-244
|
dspportq
|
Display ARM port Qbin information
|
BPX, IGX
|
4-249
|
dspports
|
Display all ports that exist on the node
|
BPX, IGX
|
4-252
|
dspportstats
|
Display Frame Relay port statistics
|
BPX, IGX
|
4-259
|
dspqbinstats
|
Display Qbin summary statistics
|
BPX, IGX
|
4-282
|
dsprtcache
|
Display cost-based route cache
|
BPX, IGX
|
4-298
|
dsprtr
|
Display Universal Router Module embedded router configuration
|
IGX
|
4-299
|
dsprtrslot
|
Display operational information for a specified Universal Router Module embedded router
|
IGX
|
4-302
|
dsprtrslots
|
Display summary of operational information for all Universal Router Module embedded routers
|
IGX
|
4-305
|
rstrtr
|
Reset Universal Router Module embedded router
|
IGX
|
4-439
|
upport
|
Up port
|
BPX, IGX
|
4-483
|
Universal Router Module
The Universal Router Module (URM) was introduced with Release 9.3.20 on the IGX 8400. The URM is functionally equivalent to a UXM card with one ATM port and an IOS router.
Management of the URM is different from other IGX cards. The IGX CLI is used to manage the embedded UXM and internal ATM port. The IOS CLI and IOS management applications are used to manage the embedded router. The IGX CLI, however, does provide features that facilitate configuration, serviceability, and monitoring of the URM embedded router. These commands are described in the following table.
The URM supports the Virtual Switch Interface (VSI) feature. The VSI feature and usage on the URM is the same as for VSI on the UXM interface card, except that the URM does not support trunks, or IMA lines and trunks. Existing CLI commands are used to configure VSI on the URMs embedded UXM ATM port. See "VSI Commands" section for the list of IGX VSI commands.
Command
|
Description
|
Type
|
Page
|
burnrtrcnf
|
Copies, or burns, the IOS configuration file from the NPM RAM buffer to the Admin flash of the URM card.
|
IGX
|
3-89
|
clrrtrcnf
|
Clears the NPM RAM buffer used to store the IOS configuration file downloaded from the TFTP server.
|
IGX
|
3-111
|
cnfrtr
|
Configures certain router parameters on a specific router slot. Parameters include IOS configuration file source and serial port function.
|
IGX
|
3-405
|
cnfrtrcnfmastip
|
Configures the IP address of the authorized TFTP server from which the IOS configuration file is to be transferred.
|
IGX
|
3-409
|
cnfrtrparm
|
SuperUser. Configures certain router parameters on a specific router slot. Parameters include common action, router reset, and write to bootflash.
|
IGX
|
3-410
|
dspalms
|
Displays major and minor alarms throughout the network and specific alarms at the local node.
|
IGX
|
4-41
|
dspcnf
|
Displays the nodes reserved for the IOS configuration file stored in the NPM RAM buffer. The save and restore facility is not allowed on these reserved nodes.
|
IGX
|
4-122
|
dsprtr
|
Reports the router configuration on a specific router slot.
|
IGX
|
4-299
|
dsprtrcnfdnld
|
Displays the progress of the transfer of the IOS configuration file from the TFTP server to the NPM RAM buffer and the copy (burn) of the configuration file to the URM Admin flash.
|
IGX
|
4-300
|
dsprtrslot
|
Reports router operational information on a specific router slot. Operational information includes: card type, VIC type, IOS software image name, router operational state, and router alarm status. Command also displays information on the IOS configuration file stored in the URM Admin flash
|
IGX
|
4-302
|
dsprtrslots
|
Reports router operational information for all router slots in the IGX. Operational information includes: card type, VIC type, and router alarm status.
|
IGX
|
4-305
|
rstrtr
|
Resets the router on a specified router slot.
|
IGX
|
4-439
|
Optimizing Traffic Routing and Bandwidth
To achieve peak network performance, the routing of traffic and the use of available bandwidth is configurable. The information used in configuring traffic routing and bandwidth is gathered from historical network trends. These commands are used to complete those tasks required to optimize the network: specifying channel utilization, specifying the class of service (including the use of the priority bumping feature), and managing bandwidth.
Command
|
Description
|
Type
|
Page
|
cnfbmpparm
|
Configure priority bumping
|
BPX, IGX
|
3-130
|
cnfchutl
|
Configure channel utilization
|
IGX
|
3-168
|
cnfcmb
|
Configure combined timeout parameters
|
IGX
|
3-181
|
cnfcon
|
Configure a connection
|
BPX, IGX
|
3-190
|
cnfcos
|
Configure class of service
|
IGX
|
3-194
|
cnfpref
|
Configure preferred route for connections
|
BPX, IGX
|
3-358
|
cnfrtcost
|
Configure cost based routing
|
BPX, IGX
|
3-403
|
dncon
|
Down connections
|
IGX
|
4-30
|
dspbmpparm
|
Display priority bumping parameters
|
BPX, IGX
|
4-50
|
dspload
|
Display connection loading
|
BPX, IGX
|
4-50
|
dspospace
|
Display open space for routes
|
BPX, IGX
|
4-228
|
dsprts
|
Display connection routing
|
BPX, IGX
|
4-299
|
dsptrkutl
|
Display trunk utilization
|
BPX, IGX
|
4-385
|
prtrts
|
Print connection routes
|
BPX, IGX
|
4-428
|
upcon
|
Up connections
|
IGX
|
4-475
|
Synchronizing Network Clocks
These commands are used to synchronize a network.
The designation of the clock source depends on the stratum (or stability) of the clock source. Each node in the network synchronizes to the nearest (fewest number of hops) primary clock source. If no primary source is available, the nearest secondary clock source is used, and so on. If no other source is available, the network synchronizes to the internal oscillator of one of the nodes in the network.
Command
|
Description
|
Type
|
Page
|
clrclkalm
|
Clears an alarm associated with a clock source. The cause of an alarm usually clock source that fails or is outside of the frequency limits. You must clear a clock alarm before the corresponding clock source is usable.
|
BPX, IGX
|
3-96
|
cnfclksrc
|
Configure network clock source. Specifies a primary, secondary, or tertiary clock source in a network
|
BPX, IGX
|
3-173
|
dspclksrcs
|
Displays all the currently defined network clock sources.
|
BPX, IGX
|
4-113
|
dspcurclk
|
Displays the clock source that the network is currently using.
|
BPX, IGX
|
4-155
|
Managing Jobs
A job is a user-specified string of commands. A job can automatically execute on a prearranged schedule or upon an event trigger. Use these commands to:
•Create a job
•Run a job
•Stop a job
•Display one or more jobs
•Edit a job
•Delete a job
•Create a job trigger
The system assigns a number to a new job. This job number identifies the job and is a required parameter for most job control commands. When you create a new job, the current privilege level is automatically saved as the privilege level of the job. Only commands that are available at your privilege level can be in your job specification. For example, a user whose highest privilege level is 3 cannot include the addtrk command in a job because addtrk requires a level 1 privilege. This privilege requirement also applies to other job functions, such as running, editing, or stopping a job.
Not all Cisco WAN Switching commands can execute as a part of a job. For this reason, the Attributes section of each command description in this manual states whether the command can function in a job.
Command
|
Description
|
Type
|
Page
|
addjob
|
Add a job
|
BPX, IGX
|
3-45
|
addjobtrig
|
Add a job trigger
|
BPX, IGX
|
3-48
|
deljob
|
Delete a job
|
BPX, IGX
|
4-13
|
deljobtrig
|
Delete job trigger
|
BPX, IGX
|
4-155
|
dspjob
|
Display a job
|
BPX, IGX
|
4-177
|
dspjobs
|
Display jobs
|
BPX, IGX
|
4-178
|
editjob
|
Edit a job
|
BPX, IGX
|
4-403
|
prtjob
|
Print a job
|
BPX, IGX
|
4-422
|
prtjobs
|
Print jobs
|
BPX, IGX
|
4-423
|
runjob
|
Run a job
|
BPX, IGX
|
4-444
|
stopjob
|
Stop a job
|
BPX, IGX
|
4-450
|
Managing the Network
These commands are used for network administration. They are also used to manage system user access, passwords, and tasks.
Command
|
Description
|
Type
|
Page
|
adduser
|
Add user(s)
|
BPX, IGX
|
3-82
|
cnffwswinit
|
Configure Cisco WAN Manager node IP address for the firmware and software initiator
|
BPX, IGX
|
3-231
|
cnfpwd
|
Configure password
|
BPX, IGX
|
3-362
|
cnfsnmp
|
Configure SNMP parameters
|
BPX, IGX
|
3-416
|
cnfstatmast
|
Configure statistics master SV+ address
|
BPX, IGX
|
3-417
|
cnfsysparm
|
Configure system parameters
|
BPX, IGX
|
3-428
|
deluser
|
Delete user
|
BPX, IGX
|
4-24
|
dsplanip
|
Display LAN IP address of all nodes in network
|
IGX
|
4-181
|
dspnwip
|
Display network IP interface
|
BPX, IGX
|
4-225
|
dsppwd
|
Display password
|
BPX, IGX
|
4-274
|
dspsnmp
|
Display SNMP parameters
|
BPX, IGX
|
4-337
|
dspsnmpstats
|
Display SNMP statistics
|
BPX, IGX
|
4-338
|
dspstatfiles
|
Display TFTP statistics file information
|
BPX, IGX
|
4-339
|
dspsv3
|
Display WAN manager Layer 3 link control blocks
|
BPX, IGX
|
4-342
|
dsptsmap
|
Display SNMP parameters
|
BPX, IGX
|
4-390
|
dspusers
|
Display users
|
BPX, IGX
|
4-391
|
dspusertask
|
Display user task
|
BPX, IGX
|
4-392
|
dspusertasks
|
Display all user tasks
|
BPX, IGX
|
4-394
|
Statistics
Command
|
Full Name
|
Type
|
Page
|
clrchstats
|
Clear channel statistics
|
IGX
|
3-94
|
cnflnstats
|
Configure line statistics collection
|
BPX, IGX, SU
|
3-265
|
cnfphyslnstats
|
Configure physical line statistics collection (OC-3)
|
IGX, SU
|
3-306
|
cnfportstats
|
Configure port statistics collection
|
BPX, IGX, SU
|
3-353
|
cnfrobparm
|
Configure robust alarms parameters
|
BPX, IGX, SU
|
3-372
|
cnfrtrparm
|
Configure universal router module (URM) embedded router parameters
|
IGX, URM, SU
|
3-410
|
cnfslotstats
|
Configure slot statistics collection
|
BPX, SU
|
3-414
|
cnfstatparms
|
Configure statistics parameters
|
BPX, IGX, SU
|
3-418
|
cnftrkstats
|
Configure trunk statistics collection
|
BPX, IGX, SU
|
3-477
|
dspchstatcnf
|
Display statistics enabled for a channel
|
IGX, SU
|
4-91
|
dspchstathist
|
Display statistics data for a channel
|
IGX, SU
|
4-93
|
dspclnstatcnf
|
Display statistics enabled for a circuit line (Note older alias: dsplnstatcnf)
|
BPX, IGX, SU
|
4-116
|
dspclnstathist
|
Display statistics history for a circuit line
|
BPX, IGX, SU
|
4-117
|
dspcntrstats
|
Display counter status statistics
|
BPX, IGX
|
4-124
|
dsplnstathist
|
Display statistics data for a line
|
BPX, IGX, SU
|
4-200
|
dspphyslnstatcnf
|
Display statistics enabled for a physical line on a UXM. The alias dsplnstatcnf is used for IGX only.
|
BPX, IGX, SU
|
4-238
|
dspphyslnstathist
|
Display statistics history for a physical line on a UXM
|
IGX, SU
|
4-242
|
dspportstatcnf
|
Display statistics enabled for an FR port
|
IGX, SU
|
4-253
|
dspportstathist
|
Display statistics history for an FR port
|
IGX, SU
|
4-254
|
dspportstats
|
Display ATM port statistics
|
BPX, IGX
|
4-268
|
dsprobst
|
Display robust statistics
|
BPX, IGX, SU
|
4-288
|
dsprrst
|
Display reroute statistics
|
BPX, IGX, SU
|
4-289
|
dspslotstatcnf
|
Display statistics enabled for a slot
|
BPX, IGX, SU
|
4-334
|
dspslotstathist
|
Display statistics history for a slot
|
BPX, IGX, SU
|
4-336
|
dspstatmem
|
Display statistics memory use
|
BPX, IGX, SU
|
4-341
|
dsptrkcons
|
Display trunk connection counts
|
BPX, IGX, SU
|
4-359
|
dsptrkmcons
|
Display trunk connection counts by master node
|
BPX, IGX, SU
|
4-365
|
dsptrkstatcnf
|
Display statistics enabled for a trunk
|
BPX, IGX, SU
|
4-371
|
dsptrkstathist
|
Display statistics history for a trunk
|
BPX, IGX, SU
|
4-373
|
rststats
|
Reset statistics collection time
|
BPX, IGX, SU
|
4-441
|
tststats
|
Test statistics
|
BPX, IGX, SU
|
4-473
|
Troubleshooting
Command
|
Full Name
|
Type
|
Page
|
addalmslot
|
Add alarm slot
|
BPX, IGX
|
3-3
|
addextlp
|
Add external loopback
|
IGX
|
3-44
|
addloclp
|
Add local loopback to connections on a port
|
BPX, IGX
|
3-54
|
addlocrmtlp
|
Add local-remote loopback in a tiered network
|
BPX, IGX
|
3-59
|
addrmtlp
|
Add remote loopback to connections
|
BPX, IGX
|
3-65
|
clrchstats
|
Clear channel statistics
|
BPX, IGX
|
3-95
|
clrclkalm
|
Clear clock alarm
|
BPX, IGX
|
3-96
|
clreventq
|
Clear the events queues from the fail handler
|
IGX
|
3-98
|
clrlnalm
|
Clear circuit line alarm
|
IGX
|
3-100
|
clrlnerrs
|
Clear circuit line errors
|
IGX
|
3-102
|
clrlog
|
Clear log
|
IGX
|
3-103
|
clrmsgalm
|
Clear message alarm
|
BPX, IGX
|
3-104
|
clrphyslnalm
|
Clear physical line alarms
|
IGX
|
3-105
|
clrphyslnerrs
|
Clear physical line errors
|
IGX
|
3-108
|
clrportstats
|
Clear port statistics
|
IGX
|
3-109
|
clrslotalms
|
Clear slot alarms
|
BPX
|
3-113
|
clrsloterrs
|
Clear slot errors
|
BPX, IGX
|
3-114
|
clrtrkalm
|
Clear trunk alarm
|
BPX, IGX
|
3-115
|
clrtrkerrs
|
Clear trunk errors
|
BPX, IGX
|
3-119
|
clrtrkstats
|
Clear trunk statistics
|
BPX, IGX
|
3-120
|
cnfbus
|
Configure active bus
|
IGX
|
3-137
|
cnfleadmon
|
Monitor LDM/HDM data port control leads
|
IGX
|
3-240
|
cnflnalm
|
Configure line alarm
|
IGX
|
3-258
|
cnfslotalm
|
Configure slot alarm parameters
|
BPX
|
3-330
|
cnftrkalm
|
Configure trunk alarm
|
BPX, IGX
|
3-463
|
dellp
|
Delete loopbacks from a connection or port
|
BPX, IGX
|
4-15
|
dncd
|
Down card
|
BPX, IGX
|
4-28
|
dspalms
|
Display alarms
|
BPX, IGX
|
4-41
|
dspbob
|
Display Breakout Box
|
BPX, IGX
|
4-55
|
dspbusbw
|
Display cell bus allocated bandwidth
|
IGX/UXM
|
4-59
|
dspbuses
|
Display bus status
|
BPX, IGX
|
4-64
|
dspclnerrs
|
Display circuit line errors
|
IGX
|
4-114
|
dspeventq
|
Display the event queue names and the data in each.
|
BPX, IGX
|
4-160
|
dspfrcbob
|
Display FRC-2/FRM-2 breakout box
|
IGX
|
4-161
|
dsplnalmcnf
|
Display line alarm configuration
|
IGX
|
4-189
|
dsplnerrs
|
Display line errors
|
IGX
|
4-195
|
dsplog
|
Display event log
|
BPX, IGX
|
4-205
|
dsppwr
|
Display power supply status
|
BPX, IGX
|
4-275
|
dspslotalms
|
Display slot alarms
|
BPX
|
4-331
|
dspsloterrs
|
Display slot errors
|
BPX
|
4-332
|
dspslotstatcnf
|
Display slot statistics configuration
|
BPX
|
4-335
|
dspsv3
|
Display Cisco WAN Manager L3 (layer 3) Link Control Blocks
|
BPX, IGX
|
4-342
|
dsptrkerrs
|
Display individual or all trunk errors
|
BPX, IGX
|
4-360
|
prtclnerrs
|
Print circuit line errors
|
IGX
|
4-418
|
prtlnerrs
|
Print line errors
|
BPX, IGX
|
4-424
|
prtlog
|
Print log
|
BPX, IGX
|
4-426
|
prttrkerrs
|
Print trunk errors
|
BPX, IGX
|
4-430
|
resetcd
|
Reset card
|
BPX, IGX
|
4-435
|
resetpc
|
Reset Port Concentrator
|
BPX, IGX
|
4-437
|
switchcc
|
Switch controller card
|
BPX, IGX
|
4-455
|
tstcon
|
Test connection
|
BPX, IGX
|
4-462
|
tstconseg
|
Test connection segment
|
BPX, IGX
|
4-465
|
tstdelay
|
Test Frame Relay connection delay
|
BPX, IGX
|
4-467
|
tstpcs
|
Test Port Concentrator Shelf
|
IGX
|
4-470
|
tstport
|
Test port
|
IGX
|
4-471
|
Error Information
Command
|
Description
|
Type
|
Page
|
dspcds
|
Displays front and back cards in the node, with type, revision, and status
|
BPX, IGX
|
4-78
|
dspcons
|
Displays a summary of connections.
|
BPX, IGX
|
4-143
|
dsplns
|
Displays status and configuration of circuit lines.
|
BPX, IGX
|
4-197
|
dsplog
|
Displays events affecting the node.
|
BPX, IGX
|
4-205
|
dspnds
|
Displays name, type, and alarm status of nodes within the local network.
|
BPX, IGX
|
4-216
|
dspnw
|
Displays the network topology in tabular form, including alarm status of each node in the network.
|
BPX, IGX
|
4-221
|
dsppwr
|
Displays power supply status and internal temperature.
|
BPX, IGX
|
4-275
|
dsprtrslot
|
Displays operational information and alarm status for a specified URM embedded router.
|
IGX
|
4-302
|
dsprtrslots
|
Displays operational information and alarm status for all URM embedded routers in a node.
|
IGX
|
4-305
|
dsptrks
|
Displays basic information for all trunks.
|
BPX, IGX
|
4-367
|
VSI Commands
Virtual Switch Interface (VSI) is a common control interface for Cisco switches such as the MGX 8850, the BPX 8650 and the IGX 8400. It provides a resource management scheme that allocates the switch resources needed for setting up connections, such as system bandwidth and channel space, to a number of external connection-management entities (controllers) which manage calls or connections with PNNI or MPLS or other protocols.
The switch resources are partitioned between Automatic Routing Management and the MPLS or PNNI Controllers.
While BPX supports both SES PNNI and MPLS controllers, IGX supports only MPLS controllers.
VSI on the BPX and IGX provides these facilities:
•multiple VSI partitions
•Service Class templates
•virtual trunk support for VSI
•Cisco WAN Manager support for VSI
VSI is supported on:
•UXM and URM cards on the IGX
•BXM cards on the BPX
For more overview information and specific information on how to configure a BPX 8650 switch, refer to the Cisco BPX Series Installation and Configuration Guide. For information about configuring a router for MPLS operation, refer to the MPLS Software Configuration Guide. For information on the IGX 8400 switch, see the IGX Installation and Configuration Guide.
Summary of IGX VSI Commands
Mnemonic
|
Description
|
Page
|
addctrlr
|
Attach a VSI controller to the IGX node.
|
3-39
|
addyred
|
Enables card redundancy for IGX cards.
|
3-83
|
compactrsrc
|
Compact the Automatic Routing Management CBAs on a particular slot.
|
3-503
|
cnfctrlr
|
Reconfigure the VPI and start_VCI of the control channels for an MPLS Controller.
|
3-196
|
cnfqbin
|
Configure Qbin parameters on a selected port, physical or virtual trunk.
|
3-363
|
cnfrsrc
|
Configure resources, for example, for Automatic Routing Management PVCs and MPLS (Multiprotocol Label Switching) Controller (LSC).
|
3-383
|
cnfvsiif
|
Assign a different Service Class Template to an interface.
|
3-498
|
delctrlr
|
Delete an MPLS controller from an IGX node.
|
4-8
|
dspcbause
|
Query the specified slot and display information about the CBA block usage.
|
4-67
|
dspchuse
|
Display a summary of channel usage in a given slot.
|
4-111
|
dspctrlrs
|
Display the MPLS controllers attached to an IGX node.
|
4-153
|
dspqbin
|
Display Qbin parameters on the specified port, physical or virtual trunk.
|
4-277
|
dspqbinstats
|
Display Qbin summary statistics
|
4-282
|
dspqbint
|
Display the default Qbin parameters for a VSI Qbin in a Qbin template.
|
4-284
|
dsprsrc
|
Display the resource partitioning for a port or trunk.
|
4-295
|
dspsct
|
Display a list of nine Service Class Templates and the Class of Service.
|
4-309
|
dspvsiif
|
Display Service Class Template assigned to an interface.
|
4-396
|
dspvsipartinfo
|
Display VSI resource information for a partition.
|
4-399
|
dspyred
|
Display information for Y-cable pairings
|
4-403
|
Summary of BPX VSI Commands
Mnemonic
|
Description
|
Page
|
addctrlr
|
Attach a PNNI VSI controller to a BPX node through an AAL5 interface shelf. For controllers that require Annex G capabilities in the controller interface.
|
3-41
|
addshelf
|
Add a trunk between the hub node and interface shelf, VSI-MPLS controller or an SES PNNI controller.
|
3-70
|
addyred
|
Enables card redundancy for BPX cards.
|
3-83
|
cnfqbin
|
Configure Qbin parameters on a selected port, physical or virtual trunk.
|
3-363
|
cnfrsrc
|
Configure resources, for example, for Automatic Routing Management PVCs and MPLS controller (LSC).
|
3-390
|
cnfvsiif
|
Configure VSI or a different template to an interface.
|
3-498
|
cnfvsipart
|
Configure VSI partition characteristics for VSI.
|
3-500
|
delctrlr
|
Delete a controller, such as a PNNI ESP (Extended Services Processor) 4.0 controller, from a BPX node.
|
4-9
|
delshelf
|
Delete a trunk between a hub node and access shelf.
|
4-19
|
dspchuse
|
Display a summary of channel distribution in a given slot.
|
4-111
|
dspctrlrs
|
Display the VSI controllers attached to a BPX node.
|
4-153
|
dspqbin
|
Display Qbin parameters.
|
4-277
|
dspqbinstats
|
Display Qbin summary statistics.
|
4-282
|
dspqbint
|
Display Qbin template.
|
4-284
|
dsprsrc
|
Display the resource partitioning for a port or trunk.
|
4-295
|
dspsct
|
Display Service Class Templates and the Class of Service.
|
4-309
|
dspvsiif
|
Display VSI.
|
4-396
|
dspvsipartcnf
|
Display information about VSI ILMI functionality.
|
4-398
|
dspvsipartinfo
|
Display VSI resource information for a partition.
|
4-399
|
dspyred
|
Display information for Y-cable pairings
|
4-402
|
upgdvsilcn
|
Expand VSI LCN to 60K for BXM-E
|
4-480
|
SuperUser Commands
The Cisco WAN switch software SuperUser commands require user privilege level 0 (zero). SuperUser commands (privilege level 0) require a different login and password than commands with privilege levels 1-6. Because the privilege level for all SuperUser commands is 0, the privilege level does not appear in the command definition.
Once you log into a node as SuperUser (user privilege level 0), you will have access to all the SuperUser commands throughout the entire session until you log off that node.
Caution These commands are intended to be restricted to Cisco personnel and other qualified users, such as system administrators. Do not distribute this information to casual users because improper use of SuperUser commands could lead to system malfunction or complete failure.
To access these commands, type in SuperUser at the login prompt. Enter the SuperUser password and the password prompt. To exit a command at any point, press the Delete key.
The definitions of potentially dangerous SuperUser commands contain an advisory for you to call the Cisco Technical Assistance Center (TAC) before you proceed. The number in the United States is 800-553-2447. For international access, use 1-408-526-4000.
This section briefly describes the statistics command line interface (CLI) definitions that are provided for various statistics commands (for example, cnfchstats, cnflnstats, cnfportstats, and so on.) Each statistics command displays field names on the CLI.
The descriptions provided in the various statistics description tables may vary from the actual definitions of the field name as it appears on the switch software command line interface statistics screens.
Only BXM card statistics descriptions are provided; however, note that many of the UXM card statistics are similar or identical to those used for the BXM card. This means that in many cases, the description may also apply to the UXM card.
The statistics descriptions provided in the various tables may not always map directly to the CLI field names, but in many cases, they provide a description of the statistic that is sent from the card firmware to the switch software CLI (through CommBus messages from the firmware to switch software).
Note The BXM CommBus interface is similar in many places to the CommBus interface for previously-released cards (ASI and BNI cards). Note that there are small differences in the CommBus definition for other cards. In some cases the object ID for the BXM card statistic differs from its ASI or BNI counterpart.
Several tables contain CommBus messages, along with descriptions of how each message is used by the switch software. Note that in many cases, the CommBus message description provides a description of the statistics field name on the CLI screen display, on dspchstats, dspchstathist, and so on.
Explanation of table columns:
•ID—Indicates the object ID number.
•Object Name—Provides a description of the object.
•Range/Values—Indicates the legal values that the object can take.
•Default—Indicates the default value used by the firmware if this object is not sent. Special defaults:
–R—Indicates that there is no default and the object must be supplied each time.
–RI—Indicates that the object is required only at initial setup time.
–NA—Not Applicable; Indicates that the object is "get-only" so a default value does not apply in this case.
–NC—No Change.
–LR—Line Rate (E3, DS3, OC-3, OC-12).
•Description—Indicates the use of the object.
Functional Description of Channel Statistics
This operation provides a way for the software to collect channel statistics. The number of channel statistics that can be collected is limited and configurable by software. Note that all of these statistics are not available on the Monarch firmware at one time. For the statistics that are not configured, a value of zero will be returned during the "get" operation.
In the description column of the screen display, the numbers in brackets indicate how many stats-per-connection need to be configured on the card for the specific statistic to be available over the CommBus interface. [ALL] indicates the statistic is available regardless of the number of configured stats-per-connection. If the number inside the [ ]s is preceded by "A:", that means that the statistic is available when primary statistics are requested for the connection. If the number inside the [ ]s is preceded by "B:", that means the statistic is available when secondary statistics are requested for the connection.
Command
|
Description
|
Type
|
Page
|
burnfwrev
|
Burn firmware image into a specific card's memory.
|
BPX, IGX, SU
|
3-87
|
clrcderrs
|
Clear detailed card errors log
|
BPX, IGX, SU
|
3-92
|
clrcnf
|
Clear configuration memory of the current node
|
BPX, IGX, SU
|
3-97
|
cnfabrparm
|
Configure parameters for ABR queue on all ports of UXM card
|
IGX, SU
|
3-122
|
cnfbusbw
|
Configure UXM card bus bandwidth parameters
|
IGX, SU
|
3-139
|
cnfcdparm
|
Configure channel statistics level on BXM or UXM cards
|
BPX, IGX, SU
|
3-143
|
cnfcdpparm
|
Configure CVM card parameters
|
BPX, IGX, SU
|
3-148
|
cnfcftst
|
Configure communications fail test pattern
|
BPX, IGX, SU
|
3-150
|
cnfchstats
|
Configure channel statistics collection
|
BPX, IGX, SU
|
3-162
|
cnfchts
|
Configure channel timestamp, a pre-aging parameter
|
BPX, IGX, SU
|
3-166
|
cnfcmparm
|
Configure connection management parameters
|
BPX, IGX, SU
|
3-183
|
cnfdiagparm
|
Configure diagnostic test parameters
|
BPX, IGX, SU
|
3-211
|
cnfdlparm
|
Configure software and firmware download parameters. Primarily a debug command.
|
BPX, IGX, SU
|
3-213
|
cnfecparm
|
Configure CDP or CVM echo canceller parameters for a specified voice circuit line.
|
IGX, SU
|
3-217
|
cnffstparm
|
Configure Frame Relay Optimized Bandwidth Management node parameters
|
BPX, IGX, SU
|
3-226
|
cnflan
|
Configure Ethernet LAN between node and Cisco WAN Manager terminal.
|
BPX, IGX, SU
|
3-238
|
cnflnparm
|
Configure ATM line parameters
|
IGX UXM, SU
|
3-259
|
cnflnsigparm
|
Configure line signaling parameters for voice cards
|
IGX, SU
|
3-262
|
cnflnstats
|
Configure line statistics collection. Primarily a debug tool.
|
BPX, IGX, SU
|
3-265
|
cnfmxbutil
|
Configure Muxbus utilization
|
IGX, SU
|
3-276
|
cnfnodeparm
|
Configure miscellaneous node parameters
|
BPX, IGX, SU
|
3-279
|
cnfnwip
|
Configure network IP address and subnet mask for the node
|
BPX, IGX, SU
|
3-303
|
cnfphyslnstats
|
Configure physical line statistics collection on UXM
|
IGX UXM, SU
|
3-306
|
cnfportstats
|
Configure FR port statistics collection. Primarily a debug command.
|
IGX, SU
|
3-353
|
cnfrobparm
|
Configure Robust Alarms parameters (a protocol for node-to-network management systems)
|
BPX, IGX, SU
|
3-372
|
cnfrtrparm
|
Configure Universal Router Module (URM) embedded router parameters
|
IGX URM, SU
|
3-410
|
cnfslotstats
|
Configure slot statistics collection for troubleshooting
|
BPX, SU
|
3-414
|
cnfstatparms
|
Configure port statistics parameters
|
BPX, IGX, SU
|
3-418
|
cnftcpparm
|
Configure TCP parameters. Specifies the number of times the BCC checks the IP addresses for attention requests.
|
BPX, IGX, SU
|
3-433
|
cnftermfunc
|
Configure terminal port parameters
|
BPX, IGX, SU
|
3-436
|
cnftlparm
|
Configure trunk-based loading parameters
|
BPX, IGX, SU
|
3-440
|
cnftrkparm
|
Configure trunk parameters to optimize traffic mixes
|
BPX, IGX, SU
|
3-466
|
cnftrkstats
|
Configure collection of Qbin statistics on specified trunk
|
BPX, IGX, SU
|
3-477
|
cnftstparm
|
Configure card self-test parameters
|
BPX, IGX, SU
|
3-485
|
cnfuiparm
|
Configure control terminal user interface parameters
|
BPX, IGX, SU
|
3-488
|
cnfuvmchparm
|
Configure UVM channel parameters
|
IGX, SU
|
3-490
|
cnfvchparm
|
Configure CVM or CVM voice channel parameters
|
IGX, SU
|
3-492
|
dchst
|
Display CDP or CVM channel status
|
IGX, SU
|
4-1
|
diagbus
|
Diagnose failed MuxBus or cell bus
|
IGX, SU
|
4-27
|
drtop
|
Display Route Op Table. Displays network statistics for connection rerouting resulting from failed trunks.
|
BPX, IGX, SU
|
4-38
|
dspabortlog
|
Display abort log
|
BPX, IGX, SU
|
4-39
|
dspasich
|
Display ASI channel routing entry
|
BPX, SU
|
4-46
|
dspbuses
|
Display available MuxBux or cell bus bandwidth
|
BPX, IGX, SU
|
4-62
|
dspcderrs
|
Display card failure information from diagnostics at local node
|
BPX, IGX, SU
|
4-76
|
dspcftst
|
Display communications fail test pattern
|
BPX, IGX, SU
|
4-81
|
dspchan
|
Display voice channel configuration
|
IGX, SU
|
4-82
|
dspchstatcnf
|
Display statistics enabled for a channel to help debug statistics
|
IGX, SU
|
4-91
|
dspchstathist
|
Display history of statistics enabled for a channel
|
IGX, SU
|
4-93
|
dspclnstatcnf
|
Display statistics enabled for a circuit line by cnflnstats
|
IGX, SU
|
4-116
|
dspclnstathist
|
Display statistics history for a circuit line
|
BPX, IGX, SU
|
4-117
|
dspcnf
|
Display configuration save and restore status
|
BPX, IGX, SU
|
4-122
|
dspdnld
|
Display status of a download to a node
|
BPX, IGX, SU
|
4-156
|
dspdutl
|
Display percentage of data channel utilization
|
IGX, SU
|
4-157
|
dspecparm
|
Display CDP echo canceller parameters
|
IGX, SU
|
4-158
|
dspfwrev
|
Display status of card firmware revision image loaded in controller card's RAM
|
BPX, IGX, SU
|
4-166
|
dsplnstathist
|
Display statistics data for a line
|
BPX, IGX, SU
|
4-200
|
dspphyslnstatcnf
|
Display statistics enabled for a physical line on a UXM by cnfphyslnstats
|
IGX, SU
|
4-238
|
dspphyslnstathist
|
Display statistics history for a physical line on a UXM
|
IGX, SU
|
4-242
|
dspportstatcnf
|
Display statistics enabled for an FR port
|
IGX, SU
|
4-253
|
dspportstathist
|
Display statistics history for an FR port
|
IGX, SU
|
4-254
|
dsprevs
|
Display system configuration and status of primary and secondary revisions running all nodes
|
BPX, IGX, SU
|
4-286
|
dsprobst
|
Display statistics associated with Robust Alarms
|
BPX, IGX, SU
|
4-288
|
dsprrst
|
Display statistics on reroutes resulting from failed trunks
|
BPX, IGX, SU
|
4-289
|
dspsig
|
Display current signaling rate from specified voice channel
|
IGX, SU
|
4-326
|
dspslot
|
Display system information associated with a slot
|
BPX, IGX, SU
|
4-328
|
dspslotstatcnf
|
Display statistics enabled for a BXM card
|
BPX, IGX, SU
|
4-334
|
dspslotstathist
|
Display statistics history for a BXM card
|
BPX, IGX, SU
|
4-336
|
dspstatmem
|
Display memory usage for statistics collection
|
BPX, IGX, SU
|
4-341
|
dspswlog
|
Display software errors log
|
BPX, IGX, SU
|
4-348
|
dsptcpparm
|
Display TCP bandwidth throttle parameter
|
BPX, IGX, SU
|
4-350
|
dsptrkcons
|
Display number of connections routed over specific trunk
|
BPX, IGX, SU
|
4-359
|
dsptrkmcons
|
Display number of connections routed over specific trunk (BNI) by master node
|
BPX, IGX, SU
|
4-365
|
dsptrkstatcnf
|
Display statistics enabled for a physical or virtual trunk
|
BPX, IGX, SU
|
4-371
|
dsptrkstathist
|
Display statistics history for a physical or virtual trunk
|
BPX, IGX, SU
|
4-373
|
dsputl
|
Display utilization for voice and data connections
|
IGX, SU
|
4-395
|
getfwrev
|
Get firmware revision image
|
BPX, IGX, SU
|
4-405
|
killuser
|
Log out a user
|
BPX, IGX, SU
|
4-409
|
loadcnf
|
Load configuration image from WAN Manager
|
BPX, IGX, SU
|
4-410
|
loadrev
|
Load secondary software revision from WAN Manager
|
BPX, IGX, SU
|
4-412
|
prtcderrs
|
Print card error information
|
BPX, IGX, SU
|
4-415
|
rrtcon
|
Manually reroute connection
|
BPX, IGX, SU
|
4-438
|
rststats
|
Reset statistics collection time for the tststats command
|
BPX, IGX, SU
|
4-441
|
runcnf
|
Restores network configuration image to one or all nodes
|
BPX, IGX, SU
|
4-442
|
runrev
|
Run a specific revision of system software at a node
|
BPX, IGX, SU
|
4-445
|
savecnf
|
Save system configuration image on WAN Manager workstation disk
|
IGX, SU
|
4-446
|
tststats
|
Display a summary of test statistics resulting from use of tstcon
|
BPX, IGX, SU
|
4-473
|
upgdlogcd
|
For BXM to BXM-E card, manually upgrade the logical card database
|
BPX, SU
|
4-477
|
upgdvsilcn
|
Expand VSI LCN to 60K for BXM-E
|
BPX, SU
|
4-480
|
Command Aliases
These commands are functionally identical. The first command name is an alias; see the command definition for the second, preferred name:
•addcdred—same functionality as addyred
•addfrport—same functionality as addport
•cnfclnstats—same functionality as cnflnstats
•cnffrport—same functionality as cnfport
•delcdred—same functionality as delyred
•delfrport—same functionality as delport
•dnfrport—same functionality as dnport
•dspcdred—same functionality was dspyred
•dspfrport—same functionality as dspport
•dsplnstatcnf—same functionality as dspphyslnstatcnf
•dsplnstats—same functionality as dspphyslnstats
•prtcdred—same functionality as prtyred
•switchcdred—same functionality as switchyred
•upfrport—same functionality as upport
