Alphabetical List of Commands dchst through window

Table Of Contents

Alphabetical List of Commands dchst through window

dchst (display channel status)

delalmslot (delete alarm slot)

delapsln (delete a SONET APS line)

delcon (delete connection)

delctrlr (delete MPLS controller from an IGX)

delctrlr (delete VSI capabilities from an AAL5 feeder interface)

delfrport (delete Frame Relay port using T1 or E1 lines)

deljob (delete a job)

deljobtrig (delete a job trigger)

dellp (delete loopback from connections or a port)

delport (delete port)

delshelf (delete an interface shelf)

deltrk (delete a trunk from the network)

deltrkred (delete ATM trunk redundancy)

deluser (delete a user)

delyred (delete Y-cable redundancy)

diagbus (diagnose failed IGX bus)

dncd (down a card)

dncon (down connection)

dnln (down line)

dnport (down port)

dntrk (down trunk)

dport (display port)

drtop (display route op table)

dspabortlog (display abort log)

dspalms (display current node alarms)

dspapsln (display APS lines)

dspasich (display ASI channel routing entry)

dspasm (display ASM card)

dspatmcls (display ATM connection class)

dspbmpparm (display priority bumping parameters)

dspbmpstats (display priority bumping statistics)

dspbob (display breakout box)

dspbpnv (display backplane NOVRAM)

dspbusbw (display cell bus bandwidth for UXM cards)

dspbuses (display bus status)

dspcdstats (display UXM card statistics)

dspcbause (display CBA block usage)

dspcd (display card)

dspcderrs (display card errors)

dspcdred (display redundant cards)

dspcds (display cards)

dspcftst (display communication fail test pattern)

dspchan (display channel configuration)

dspchcnf (display channel configuration)

dspchdlcnf (display channel dial type configurations)

dspchec (display channel echo canceller configuration)

dspchstatcnf (display statistics enabled for a channel)

dspchstathist (display statistics history for a channel)

dspchstats (display summary statistics for a channel)

dspchuse (display channel usage)

dspclksrcs (display network clock sources)

dspclnerrs (display circuit line errors)

dspclnstatcnf (display circuit line statistics configuration)

dspclnstathist (display statistics history for a circuit line)

dspcls (display connection class)

dspcnf (display configuration save/restore status)

dspcntrstats (display counter status statistics)

dspcon (display connection)

dspcon (display data connections)

dspcon (display Frame Relay connections)

dspcon (display ATM connections)

dspconcnf (display connection configuration)

dspcond (display conditioning criteria)

dspcons (display connections)

dspconst (display connection state for line connections)

dspctrlrs (display all controllers on a BPX node)

dspcurclk (display current clock sources)

dspdnld (display download)

dspdutl (display data channel utilization)

dspecparm (display echo canceller parameters)

dspeventq (display event queue)

dspfrcbob (display FRC/FRM breakout box)

dspfrcls (display Frame Relay classes)

dspfrcport (display FRC-2/FRM-2 port configuration)

dspfwrev (display firmware revision)

dsphitless (display statistical history of hitless rebuilds)

dspict (display interface control template)

dspjob (display job)

dspjobs (display jobs)

dsplancnf (display LAN interface connection)

dsplanip (display LAN IP addresses)

dsplm (display load model table)

dsplmistats (display Annex G LMI statistics)

Functional Description of LMI Statistics for BXM Card

dsplnalmcnf (display line alarm configuration)

dsplncnf (display line configuration)

dsplnerrs (display line errors)

dsplns (display lines)

dsplnstathist (display statistics data for a line)

dspload (display connection loading)

dsplog (display event log)

Degraded Mode Conditions

dspmode (display mode)

dspmodes (display modes)

dspnds (display all nodes)

dspnebdisc (display neighbor discovery)

dspnode (display node)

dspnw (display network)

dspnwip (display network IP interface)

dspoamseg (display connection OAM segment status)

dspospace (display open space for a route)

dsppcs (display port concentrator shelf)

dspphyslnerrs (display physical line errors)

dspphyslns (display physical line status)

Display Fields

dspphyslnstatcnf (display statistics enabled for a physical line)

dspphyslnstathist (display statistics data for a physical line)

dspport (display port)

dspportids (display port IDs)

dspportq (display ARM port queue configuration)

dspports (display ports)

dspportstatcnf (display statistics enabled for FR port)

dspportstathist (display statistics history for an FR port)

dspportstats (display Frame Relay port statistics)

dspportstats (display ATM port statistics)

dspprtcnf (display print configuration)

dsppwd (display password)

dsppwr (display power supply status)

dspqbin (display Qbin)

dspqbinstats (display Qbin statistics)

dspqbint (display Qbin templates)

dsprevs (display revisions)

dsprobst (display robust statistics)

dsprrst (display reroute statistics)

dsprsrc (display resources)

dsprtcache (display cost-based route cache)

dsprtr (display router)

dsprtrcnfdnld (display status of router configuration file)

dsprtrslot (display router slot)

dsprtrslots (display router slots)

dsprts (display connection routing)

dspsct (display Service Class Template)

dspsig (display signaling)

dspsigqual (display signaling qualifiers)

dspslot (display slot)

dspslotalmcnf (display slot alarm configuration)

dspslotalms (display slot alarms)

dspsloterrs (display slot errors)

dspslotstatcnf (display statistics enabled for a BXM card slot)

dspslotstathist (display statistics history for a BXM card)

dspsnmp (display SNMP parameters)

dspsnmpstats (display SNMP statistics)

dspstatfiles (display TFTP statistics file information)

dspstatmem (display statistics memory use)

dspsv3 (display WAN manager L3 link control blocks)

dspsvcst (display the voice SVC statistics)

dspswlog (display software error log)

dsptcpparm (display TCP parameters)

dsptermcnf (display terminal port configurations)

dsptermfunc (display terminal port functions)

dsptrkbob (display trunk breakout box)

dsptrkcnf (display trunk configuration)

dsptrkcons (display trunk connection counts)

dsptrkerrs (display trunk errors)

dsptrkict (display trunk interface control templates)

dsptrkmcons (display trunk connection counts by master node)

dsptrkred (display ATM trunk redundancy)

dsptrks (display trunks)

dsptrkstatcnf (display statistics enabled for a trunk)

dsptrkstathist (display statistics history for a trunk)

dsptrkstats (display trunk statistics)

dsptrkutl (display trunk utilization)

dsptsmap (display the channel-to-timeslot mapping usage)

dsptsmap (display SNMP parameters)

dspusers (display users)

dspusertask (display user task)

dspusertasks (display user tasks)

dsputl (display utilization)

dspvsiif (display a Service Class Template assigned to an interface)

dspvsipartcnf (display VSI partition characteristics)

dspvsipartinfo (display VSI statistics per partition)

dspyred (display Y-cable redundancy)

editjob (edit a job)

getfwrev (get firmware revision)

help or ? (help command)

killuser (log out a user)

loadcnf (load configuration)

loadrev (load revision)

prtapsln (print APS line status)

prtcderrs (print card errors)

prtchcnf (print channel configuration)

prtchdlcnf (print channel dial type configuration)

prtclnerrs (print circuit line errors)

prtcons (print connections)

prtict (print interface control template)

prtjob (print job)

prtjobs (print jobs)

prtlnerrs (print physical line errors)

prtlns (print line configuration)

prtlog (print event log)

prtnw (print network topology)

prtrts (print connection routes)

prtscrn (print terminal screen)

prttrkerrs (print trunk errors)

prttrkict (print trunk interface control template)

prttrks (print trunks)

prtyred (print Y-cable redundancy)

redscrn (redraw the terminal screen)

resetcd (reset card)

resetpc (reset port concentrator)

rrtcon (reroute connection)

rstrtr (reset router)

rststats (reset statistics collection time)

runcnf (run configuration)

runjob (run a job)

runrev (run revision)

savecnf (save configuration)

TFTP Configuration Save and Restore

stopjob (stop job)

upggrp (upgrade groups)

switchapsln (control APS switching interface)

switchcc (switch control card)

switchyred (switch Y-redundancy cards)

tstbadubus (test NTM corruption problem)

tstcon (test connections)

tstconseg (test connection segment)

tstdelay (test connection round-trip delay)

tstpcs (test port concentrator shelf)

tstport (test port)

tststats (test statistics)

upcd (up card)

upcon (up a connection)

upgdlogcd (upgrade logical card database)

upgdvsilcn (expand VSI LCN to 60K for BXM-E)

upln (up a line)

upport (up port)

uptrk (up trunk)

vt (make a virtual connection)

window (window to external device)

Alphabetical List of Commands dchst through window

dchst (display channel status)

Displays CDP or CVM card parameters.

This command displays state information for a CDP or CVM channel used for a specific connection.

The Transmit and Receive dBm0 for both CDP or CVM indicate the input (toward the circuit line) and output power (from the circuit line) levels for the channel. Modem state indicates whether modem-detect is on or off.

Syntax

dchst <channel> [interval]

Parameters

Parameter

Description

<channel(s)>

Specifies the voice channel numbers to configure.

<interval>

Specifies the refresh time for the data.
Range: 1-60 seconds
Default: 5 seconds

Display Fields: Channel Status Parameters for CDP or CVM

Register

Byte

Parameter

Description

0

high
low

zcr total
signal state mem

Zero Crossing Total
Signal State Memory

1

high
low

hpf z1 hi-hi
hpf z1 hi-lo

High-Pass Filter
High-Pass Filter

2

high
low

sam - hi
sam - lo

Encoded Voice Sample
Encoded Voice Sample

3

high
low

vad state-hi
vad state-lo

Voice Activity Detector state
Voice Activity Detector state

4

high
low

sil cnt
mad signal state

Silent Count
Modem Activity Detector Signal State

5

high
low

mad wnd cnt
mad fail cnt

Modem Activity Detector Wnd. Count
Modem Activity Detector Fail Count

6

high
low

mad state-hi
mad state-lo

Modem Activity Detector state
Modem Activity Detector state

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

Yes

Related Commands

cnfcdpparm

Example

dchst 11.1

alpha TRM SuperUser Rev: 9.3 Apr. 13 2000 16:30 PST

CDP state display for channel 11.1 Snapshot

Transmit dBm0:
Receive dBm0:

Register 0 =
Register 1 =
Register 2 =
Register 3 =
Register 4 =
Register 5 =
Register 6 =

Last Command: dchst 11.1

Next Command:

delalmslot (delete alarm slot)

Disables the ARC (IPX) or ARM (IGX) alarm indicators and ARI external alarms. See the addalmslot description for more information on ARC/ARM alarm relays and adding alarm slots.

Upon receiving the command, the system places the alarm card set in the standby state and displays the current alarm status.

Syntax

delalm <slot number>

Parameters

Parameter

Description

slot number

Specifies the slot number of the alarm card set to activate.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-4

No

Yes

IGX

Yes

Related Commands

addalmslot, dspalms

Example

Disable the alarm indicators on the ARM card set in slot 11. (The system subsequently displays alarm status.)

delalmslot 11

pubsigx1 TN SuperUser IGX 8430 9.3 Apr. 13 2000 02:09 GMT

Alarm summary (Configured alarm slots: None)
Connections Failed: None
Groups Failed: None
TRK Alarms: None
Line Alarms: None
Cards Failed: None
Missing Cards: None
Remote Node Alarms: 1 Minor
Remote Domain Alarms: None

Routing Network Alarms: None

Cabinet Fan(s) Failed

FastPAD Node Alarms: None

Last Command: delalmslot 11
Next Command:

delapsln (delete a SONET APS line)

The delapsln command deletes SONET Automatic Protection Switching (APS) for the lines. You must enter the working slot.port pair. When you execute the delapsln command, the dspapsln display appears, showing you that the line you deleted is gone. (The delapsln display will be empty, or show only the remaining APS lines.)

SONET APS is a standard that describes the switching of SONET lines from the active line to a standby line to provide hardware line redundancy. The SONET APS feature applies only to BXM OC-3 and OC-12 cards in this release.

For background information on how SONET APS for BXM cards works, refer to "APS Command Summary" in this chapter.

When you execute the delapsln command, the switch software does verifies that the slot.port arguments support APS.

Syntax

delapsln <slot.port1> < slot.port2> <protocol>

Parameters

Parameter

Description

slot.port1

The desired working line number.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

No

Yes

BPX

Yes

Related Commands

addapsln, cnfapsln, cnfcdaps, dspapsln, dsplog, dspalms

Example

delapsln 11.1

sw119 TRM StrataCom BPX 8620 9.3.10 Date/Time Not Set

Work/Protect Actv Active Line Standby Line Current APS Last User
(Work1/Work2)Line Alarm Status Alarm Status Alarm Status Switch Req

Last Command: delapsln 11.1

delcon (delete connection)

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.

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.

You can use delcon to remove one or more voice connections from a network. You can delete connections at either end of the connection. After entry of the channel or range of channels to delete, a prompt requests confirmation of the selection.

Do not delete a connection when the node at the other end of the connection is unreachable. The unreachable node does not recognize the deletion. You must not delete a connection to an unreachable node then connect that deleted channel to another node.

To verify connection deletions, use the dspcons command. To add channel connections to the network, use the addcon command.

Syntax

delcon <channels>

Parameters

Parameter

Description

channels

Specifies a channel or range of channels to delete.

The format for channel on a CDP or CVM is slot.channel.

The format for channel on a UVM is slot.line.channel.

The format for an ATM channel is slot.port.vpi.vci.

For a range of channels, separate the first and last channel with a hyphen (-).

Range (FRP port): 1-24

Range (FRM port): 1-31

Range (UFM-C port): 1-250 (For connections on a UFM-C, line is not necessary because of the port-to-line mapping through addfrport.)

Range (UFM-U port for V.35 or X.21): 1-12

Range (UFM-U port for HSSI): 1-4 (unless Y-cable redundancy exists on the HSSI, in which case port can be only "1").

Range (DLCI): 16-1007

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

BPX, IGX

Yes

Related Commands

addcon, dspcon, dspcons

Example

Delete connection 10.1.1. The proposed deletions are highlighted, and a prompt requests confirmation of the deletion. Enter a "y" to delete the highlighted connections or an "n" to keep the highlighted connections. The example shows the screen before deletion of 10.1.1.

delcon 10.1.1

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 12:24 PST

From Remote Remote
10.1.1 NodeName Channel State Type Compress Code COS
10.1.1 igxr02 20.1.1 Ok p 0
10.1.3-4 igxr02 20.1.3-4 Ok v VAD 2
10.1.5-6 igxr02 20.1.5-6 Ok t 0
10.1.9-10 igxr02 20.1.9-10 Ok a24 ADPCM 2
10.1.11-12 igxr02 20.1.11-12 Ok c24 VAD/ADPCM 2
10.1.13-14 igxr02 20.1.13-14 Ok a32 ADPCM 2
10.1.15-16 igxr02 20.1.15-16 Ok c32 VAD/ADPCM 2
10.1.19-20 igxr02 20.1.19-20 Ok l16v VAD/LDCELP 2
10.2.1 igxr02 20.2.1 Ok p 0
10.2.3-4 igxr02 20.2.3-4 Ok a24 ADPCM 2
10.2.5-6 igxr02 20.2.5-6 Ok a32 ADPCM 2
10.2.7 igxr02 20.2.7 Ok l16 LDCELP 2
10.2.9 igxr02 20.2.9 Ok l16v VAD/LDCELP 2

This Command: delcon 10.1.1

Delete these connections (y/n)?
Example

Delete connection 6.4.

delcon 6.4

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 12:38 PST

From Remote Remote
6.4 NodeName Channel State Type Compress Code COS
6.4 igxr02 18.4 Ok 128 DFM 7/8 0
10.1.1 igxr02 20.1.1 Ok p 0
10.1.3-4 igxr02 20.1.3-4 Ok v VAD 2
10.1.5-6 igxr02 20.1.5-6 Ok t 0
10.1.9-10 igxr02 20.1.9-10 Ok a24 ADPCM 2
10.1.11-12 igxr02 20.1.11-12 Ok c24 VAD/ADPCM 2
10.1.13-14 igxr02 20.1.13-14 Ok a32 ADPCM 2
10.1.15-16 igxr02 20.1.15-16 Ok c32 VAD/ADPCM 2
10.1.19-20 igxr02 20.1.19-20 Ok l16v VAD/LDCELP 2
10.2.1 igxr02 20.2.1 Ok p 0
10.2.3-4 igxr02 20.2.3-4 Ok a24 ADPCM 2
10.2.5-6 igxr02 20.2.5-6 Ok a32 ADPCM 2
10.2.7 igxr02 20.2.7 Ok l16 LDCELP 2

This Command: delcon 6.4

Delete these connections (y/n)?
Example

Delete connection 14.3.4. The connections to delete are highlighted. A prompt asks you to confirm the deletion. Respond with "y" for yes.

delcon 14.3.4

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 12:56 PST

From Remote Remote
14.3.4 NodeName Channel State Type Compress Code COS
14.3.4 igxr02 27.3.4 Ok fr 0
14.3.5 igxr02 27.3.5 Ok fr 0
14.3.6 igxr02 27.3.6 Ok fr 0
14.3.7 igxr02 27.3.7 Ok fr 0
14.3.8 igxr02 27.3.8 Ok fr 0
14.3.9 igxr02 27.3.9 Ok fr 0
14.3.10 igxr02 27.3.10 Ok fr 0
14.3.11 igxr02 27.3.11 Ok fr 0
14.3.12 igxr02 27.3.12 Ok fr 0
14.3.13 igxr02 27.3.13 Ok fr 0
14.3.14 igxr02 27.3.14 Ok fr 0
14.3.15 igxr02 27.3.15 Ok fr 0
14.3.16 igxr02 27.3.16 Ok fr 0

This Command: delcon 14.3.4

Delete these connections (y/n)?
Example

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

delcon 11.1.180.150

sw53 VT Cisco BPX 8620 9.3.m0 Dec. 19 2000 09:57 GMT

From Remote Remote Route
11.1.180.150 NodeName Channel State Type Avoid COS O
11.1.180.150 sw180 15.1.11.100 Ok ubr 0 R
11.1.180.530 sw180 5.3.53.530 Ok ubr 0 L
11.1.180.1000 sw180 15.1.53.1000 Ok nrt-vbr 0 L
11.1.180.1001 sw180 15.1.53.1001 Ok abrstd 0 L

This Command: delcon 11.1.180.150

Delete these connections (y/n)?

delctrlr (delete MPLS controller from an IGX)

Deletes an MPLS controller attached to a line on a UXM card.

When the controller is deleted, the VSI control channels used to communicate between the VSI master on the MPLS controller and the VSI slaves on the UXM cards are also deleted. The control VCs associated with other controllers attached to the node will not be affected.

Syntax

delctrlr <controller id>

Parameters

Parameter

Description

controller id

Controller ID number corresponding to the MPLS controller you are deleting. ID numbers should correspond to an active MPLS controller.

Range: 1-16

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

No

Yes

BPX, IGX

Yes

Yes

Yes

No

Related Commands

addctrlr, dspctrlrs

Example

Delete an MPLS controller.

delctrlr 3

arnold TN Cisco IGX 8430 9.3.1p Aug. 16 2000 17:12 PST

VSI Controller Information

CtrlrId PartId ControlVC Intfc Type CtrlrIP
VPI VCIRange

Last Command: delctrlr 3

Controller deleted successfully!
Next Command:

delctrlr (delete VSI capabilities from an AAL5 feeder interface)

Deletes VSI capabilities on a trunk interface to which a feeder of type AAL5 is attached. Use this command to delete a controller, such as a PNNI SES controller, from a BPX node. It deletes the VSI control channels used to communicate between the VSI master on the PNNI controller and the VSI slaves on the BXM cards.

Run this command as the first step in deleting a PNNI controller from a BPX node. The second step is to run the command to delete the AAL5 feeder.

Note Do not use delctrlr to delete a VSI Label Switching controller from a BPX node; you must use delshelf to delete a VSI Label Switching controller from a BPX node.

PNNI runs on the Service Expansion Shelf (SES) hardware.

To add VSI controller capabilities onto the newly created AAL5 interface, you use the addctrlr command. You are prompted to enter the controller ID and partition ID. This creates an interface through which a PNNI controller can use the VSI protocol to control the node resources that were previously specified by using the cnfrsrc command.

Remove a PNNI controller from a node by using the delctrlr command. For example, this might be a VSI controller such as a PNNI controller configured with VSI capabilities as an AAL5 interface shelf to a BPX. When you delete one of the controllers by using the delctrlr command, the master-slave connections associated with this controller are deleted. The control VCs associated with other controllers managing the same partition will not be affected.

Note To add a VSI Label Switch Controller, use addshelf and delshelf commands.

Syntax

delctrlr <slot.port> <controller id>

Parameters

Parameter

Description

slot.port

Slot and port numbers corresponding to the feeder trunk.

controller id

Controller ID number corresponding to the PNNI controller you are deleting. ID numbers should correspond to an active PNNI controller.

Range: 1-32

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

No

Yes

BPX, IGX

Yes

Yes

Yes

No

Related Commands

addctrlr, dspctrlrs, dspnode

Example

Delete VSI controller with interface shelf (feeder) type of AAL5 connected on trunk 10.3 from the list of controllers connected to BPX node named "night."

delctrlr 10.3

night TN StrataCom BPX 8600 9.3.10   Apr. 11 2000 14:31 GMT

BPX Controllers Information

Trunk Name Type Part Id Ctrl Id Ctrl IP State
10.3 PAR VSI 1 2 192.0.0.0 Enabled
11.1 VSI VSI 2 2 192.0.0.0 Disabled

Last Command: delctrlr 10.3

Example

Deletes controller from port 3 on slot 10, with controller name E, and controller ID of 1.

delctrlr <slot.port><controller_id>

night TN StrataCom BPX 8600 9.3.10   Apr. 11 2000 14:31 GMT

BPX Controllers Information

Trunk Name Type Part Id Ctrl Id Ctrl IP State
10.3 PAR VSI 1 1 192.0.0.0 Enabled
11.1 VSI VSI 2 2 192.0.0.0 Disabled

Last Command: delctrlr 10.3

delfrport (delete Frame Relay port using T1 or E1 lines)

Deletes logical ports on FRP, FRM, or UFM-C cards and "unassigns" associated DS0/timeslots. The information in this definition applies only to Frame Relay ports using a T1 or E1 line.

The deleted DS0/timeslots are available for you to assign to new logical ports by using the addport (alias addfrport) command. The port display (normally visible through dspport [alias dspfrport] command) appears regardless of whether the port has been successfully deleted. The screen displays the defined port numbers for the specified line. Table 4-1 lists the error and warning messages for this command.

Table 4-1 delfrport—Warnings and Error Messages

Messages

Reason for Message

"Slot is out of range"

Line number is not correct for FRP T1/E1.

"Port does not exist"

Logical port number does not exist.

"You must first down the port"

Logical port is up.

"You must first down the port"

Specified port is not first DS0/timeslot of logical port.

Syntax

For FRM or FRP:
delfrport <slot.port>

For UFM:
delfrport <slot.port> <line.ds0_range>

Parameters

Parameter

Description

slot

Specifies logical port numbers for the physical FRP or FRM T1 or E1 line.
Range for T1 lines: 1-24
Range or E1 lines: 1-31

port

Specifies the logical port number of the port to delete.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

Yes

Yes

IGX

Yes

Related Commands

addfrport, dspfrport

Example

Delete Frame Relay port 14.1.

delfrport 14.1

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 13:04 PST

Port configuration for UFM 14

Port Line Chan Speed Interface State Protocol
1 1 1-24 1536 Kbps T1D ACTIVE None
2 2 1-24 1536 Kbps T1D ACTIVE None
3 3 1-24 1536 Kbps T1D ACTIVE None
4 4 1-24 1536 Kbps T1D ACTIVE None

This Command: delfrport 14.1

You must first down the port
Enter port:

deljob (delete a job)

Deletes a job. To delete a job, you must have a privilege level at least as high as the job itself. A job that is currently running cannot be deleted. If necessary, use stopjob to stop the job so that you can delete it.

Syntax

deljob <job_number>

Parameters

Parameter

Description

job number

Specifies the number of the job.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

Yes

BPX, IGX

Yes

Related Commands

addjob, dspjob, dspjobs

Example

Delete job 4.

deljob 4

pubsigx1 TN SuperUser IGX 32 9.3 Apr. 13 2000 19:54 GMT

Job 4
Last Execution Results: None Status: Locked
Next Execution Time: Interval:

1: prtlog
- Failure Reaction: Abort Exec. Results: None
2: dncd 6
- Failure Reaction: Repeat 12 Times and Abort Exec. Results: None
3: dncd 6
- Failure Reaction: Repeat 12 Times and Continue Exec. Results: None

This Command: deljob 4

Delete this job (y/n)?

deljobtrig (delete a job trigger)

Deletes a job trigger. The deljobtrig command deletes one trigger at a time. If you delete a job by using the deljob command, all associated job triggers are deleted.

Syntax

deljobtrig <job_number> <trig_num>

Parameters

Parameter

Description

<job_number>

Specifies the number of the job.

<trig_num>

Specifies the number of the trigger to delete.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

Yes

BPX, IGX

Yes

Related Commands

addjobtrig, dspjobs

Example

Delete job trigger 1 for job 1.

deljobtrig 1 1

pubsigx1 TN SuperUser IGX 32 9.3 Apr. 13 2000 18:19 GMT

Job Description Next Execution Status Interval Access Group
1 test1 Idle SuperUser
Trigger 1 - PLN 2 FAILURE
2 Idle SuperUser
3 test3 09/02/97 11:11:11 Idle 1 days SuperUser
4 Idle SuperUser
5 Idle SuperUser
6 Idle SuperUser

This Command: deljobtrig 1

Enter trigger number:

dellp (delete loopback from connections or a port)

Deletes an external, local, remote, or local-remote (tiered nets) loopback from the designated channel, set of channels, or port. After the loopback is deleted, any conditioning applied during the loopback process is removed and service is restored.

•Add local loopbacks by using the addloclp command.

•Add remote loopbacks by using the addrmtlp command.

•Add external loopbacks by using the addextlp command.

A local loop can be deleted only from the node that added it. However, a remote loop can be deleted from the node at either end of the connection.

Add local-remote loopbacks by using the addlocrmtlp command. Note that with local-remote loopbacks, execution of dellp is mandatory after testing is complete, otherwise continuity errors will result.

The addloclp and addlocrmtlp commands support the two-segment connection at the hub node port endpoint in a network of IGX routing hubs and SES interface shelves. The addloclp and addlocrmtlp commands are blocked at the interface shelf trunk endpoint. The addrmtlp command is not supported at either endpoint of the connection. You can use the dellp command to remove the local (or local remote) loopbacks that have been added; however, you cannot use the dellp command at the trunk endpoint of the connection—it will be blocked. Loops of any kind are not supported for the middle segment of a three-segment connection.

Syntax

dellp <channel>

Parameters

Parameter

Description

channel

Specifies the channel or set of channels whose loopback is to be deleted. The format for channel depends on the type of connection is:

Voice connection: slot.channel
Data connection: slot.port
Frame Relay connection: slot.port.DLCI
ATM connections: slot.port.vpi.vci

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

BPX, IGX

Yes

Related Commands

addextlp, addloclp, addlocrmtlp, addrmtlp

Example

Delete the loopback on channel 5.1.121. The connections screen appears with connection 5.1.121 highlighted. (The highlighting is not visible in the screen example, but the loop symbols indicates loopback.) The display prompts you to confirm deletion of the loopback. To confirm, enter "y."

dellp 5.1.121

pubsipx1 TN SuperUser IGX 8420 9.3 Apr. 13 2000 19:16 PDT

Local Remote Remote
Channel NodeName Channel State Type Compress Code COS
5.1.121 )pubsipx1 8.33.133 Ok atfr
5.1.122 pubsipx1 8.34.134 Ok atfr
5.2.111 pubsipx1 8.45.155 Ok atfr
5.2.112 pubsipx1 8.45.156 Ok atfr
8.33.133 pubsipx1 (5.1.121 Ok atfr
8.34.134 pubsipx1 5.1.122 Ok atfr
8.45.155 pubsipx1 5.2.111 Ok atfr
8.45.156 pubsipx1 5.2.112 Ok atfr

This Command: dellp 5.1.121

Delete these loopbacks (y/n)?

delport (delete port)

This command is required to delete ports from the IGX and BPX. Use this command to:

•delete an ATM port from the BPX (for example, ASI, BXM, physical, or virtual port).

•delete the internal ATM port from the embedded UXM in the Universal Router Module (URM) (introduced in Release 9.3.20 on the IGX 8400).

•delete a Frame Relay port from the IGX (for example FRM, UFM, physical).

The dnport command is required before the ports can be deleted.

Syntax

delport <slot.port>[.<vport>]

Parameters

Parameter

Description

<slot.port>

Specifies the slot number of the card, the physical port, and optional virtual port (BXM card only).

[.<vport>]

The optional vport identifier. Range: 1-31

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

BPX, IGX

Yes

Related Commands

addport, upport cnfport, dnport

Example

Delete the internal ATM port 11.1 on the Universal Router Module (URM) in an IGX node.

delport 11.1

sw190 TRM Cisco IGX 8420 9.3.e9 Oct. 6 2000 05:23 GMT

Port configuration for ATM 11

Port Chan Speed Interface State Protocol Type

Last Command:delport 11.1
Example (BPX)

Delete port 3 on the BXM card in slot 11.

delport 11.3

sw53 TN Cisco BPX 8620 9.3.m0 Dec. 19 2000 12:45 GMT

Port configuration for ATM 11

From VPI Min/Max Bandwidth Interface State Protocol Type

Last Command: delport 11.3

delshelf (delete an interface shelf)

Deletes an interface shelf from a tiered network. The identifier for an interface shelf is either the trunk number or the name of the shelf. Normally, you do not execute delshelf only at the hub node or the BPX core switch shelf, but on the IGX/AF itself.

The delshelf command has the single function of letting you turn off LMI if the trunk is not allowing communication. In contrast to the deltrk command, you can execute delshelf at any time if no connections terminate at the trunk.

In Release 9.2 and above, when you use delshelf to remove an MGX 8850 interface shelf trunk from a BPX routing hub, or an SES interface shelf (or feeder) trunk from an IGX 8400 routing node, the Annex G signaling channel and IP relay programming for the MGX 8850 or SES interface shelf is removed.

Deleting a Controller

You remove a controller from the node by using the delshelf command. When one of the controllers is deleted by using the delshelf command, the master-slave connections associated with this controller is deleted. The control VCs associated with other controllers managing the same partition are not affected.

The deletion of the controller triggers a new VSI configuration CommBus (internal BPX protocol) message that includes the list of the controllers attached to the node and is sent to all active slaves in the shelf. The controller deleted is removed from the list. In cluster configurations, deleting a controller is communicated to the remote slaves by the slave directly attached through the interslave protocol.

While there is at least one controller attached to the node controlling a given partition, the resources in use on this partition should not be affected by the deletion of a controller. The slaves release all the VSI resources used on a partition only when that partition is disabled.

Syntax

delshelf <trunk> | <shelf-name>

Parameters

Parameter

Description

trunk or shelf name

Specifies the slot and port number of the trunk or the name of the interface shelf.

Related Commands

addshelf, dspnode

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

Yes

Yes

BPX, IGX

Yes

Yes

Yes

No

Example

Delete shelf trunk A241 from a BPX node.

delshelf 4.1

nmsbpx23 TN SuperUser BPX 8600 9.3.10     July 16 2000 13:26 PST

BPX Interface Shelf Information

Trunk Name Type Alarm
1.3 AXIS240 AXIS OK
11.2 A242 AXIS OK

Last Command: delshelf A241

Shelf has been deleted
Next Command:

deltrk (delete a trunk from the network)

Deletes a trunk. Because deleting a trunk removes the communication path between two nodes, using deltrk may split a network into two separate networks. If executing deltrk splits the network, then the connections that are using the deleted trunk are also deleted.

If both nodes on the trunk are reachable, you need only to execute deltrk on one node. If you delete a trunk on a node while the node at the other end is unreachable, the unreachable node does not detect that the trunk to the other node has been deleted; therefore, be sure to delete the trunk at both nodes in such a case.

After you delete a trunk, it still carries framing signals but no traffic. Also, the trunk can generate alarms for counting. To remove a trunk completely, use dntrk after executing the deltrk command.

In these situations, the node does not allow deltrk to execute:

•Another node is attempting to change the network topology by adding or deleting a trunk.

•Another node is notifying all other nodes that it has a new node name.

•Another node is adding or deleting a channel connection in the network with the addcon or delcon command.

In Release 9.1.07, when the A-bit Notifications on LMI/ILMI Interface feature is enabled (by using cnfnodeparm), after deleting the trunk, the master node will deroute all the connections on the trunk. The slave end will receive the A7 (CMUP_DEROUTE) message before the reroute message from the master node.

Regarding the A-bit Notifications feature, each pass in the Connection Management routing state machine involves two activities: deroute and then followed by routing connections. However, connections can be derouted without going through the reroute state machine (for example, deltrk). There are several ways to kick off the routing state machine resulting in slightly different deroute and reroute behavior. See the deltrk, dncd, and cnfcmparm (SuperUser) commands.

Syntax

deltrk <slot.port>[.vtrk]

Parameters

Parameter

Description

<slot.port>

Specifies the physical trunk number.

[.vtrk]

Optionally specifies the virtual trunk portion of the trunk identifier.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

Yes

Yes

BPX, IGX

Yes

Related Commands

addtrk, dntrk, dspnw, dsptrks, uptrk

Example

Delete trunk 7 from the network.

deltrk 7

beta TRM YourID:1 IGX 8430 9.3 Apr. 13 2000 15:02 MST

PLN Type Current Line Alarm Status Other End
7 E1/32 Clear - Line OK -
9 T1/24 Clear - Line OK gamma.10
13 T1/24 Clear - Line OK alpha.14
15 T1/24 Clear - Line OK gamma.15
20 T3/3 AIT - AIT Missing -

Last Command: deltrk 7

Next Command:

deltrkred (delete ATM trunk redundancy)

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

The trunk redundancy feature (not the Automatic Protection Switching redundancy feature) is supported on the IGX platforms. This is different from the Automatic Protection Switching redundancy feature. APS is supported only on BXM SONET trunks, and can be used with virtual trunks. That is, the trunk port supporting virtual trunks can have APS line redundancy configured in the same way it would be configured for a physical trunk. The APS commands addapsln, delapsln, switchapsln, and cnfaplsn are all supported on virtual trunk ports.

Note that the trunk redundancy feature is not supported for virtual trunks. The addtrkred, deltrkred, and dsptrkred commands are rejected for virtual trunks.

Note that Y-cable redundancy is supported for both the UXM and BXM trunk cards at the edge of the ATM cloud.

Syntax

deltrkred <backup ATM trunk number>

Parameters

Parameter

Description

<backup ATM trunk number>

Specifies of the ATM card set assigned as the backup.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-4

No

Yes

IGX

Yes

Related Commands

addtrkred, dsptrkred

Example

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

deltrkred 5

beta TRM YourID:1 IGX 8430 9.3 Apr. 13 2000 15:15 MST

ATM Line Backup ATM Line
5 8

Last Command: deltrkred 5

Next Command:

deluser (delete a user)

Deletes a user from the network. You can delete users at any lower privilege level.

Syntax

deluser <user_id>

Parameters

Parameter

Description

<user_id>

Specifies the name of the user to delete from the network.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-5

No

Yes

BPX, IGX

Yes

Related Commands

adduser, dspusers

Example

deluser john

Delete the user named "john."

alpha TRM YourID:1 IGX 8410 9.3 Apr. 13 2000 13:52 PST

YourID 1
Sarah 5

\

Last Command: deluser John

Next Command:

delyred (delete Y-cable redundancy)

This command disables Y-cable redundancy for the card set in the specified primary slot number. If the secondary card slot is in use as the active slot at the time you use the delyred command, the system attempts to switch back to the primary slot. The substitution takes place only if the primary slot has a complete set of cards and the cards are in a Standby or a Standby-F state (not if they are Failed).

See the dspcds description for information on card states. See the addyred and dspyred commands for more information on Y-cable redundancy.

When you issue the delyred command, it always completes. If the primary card is incomplete, control is given to the primary card.

If the secondary card slot is being used as the active slot at the time you use the delvred command, the system attempts to switch back to the primary slot. The substitution takes place only if the primary slot has a complete set of cards and the cards are in a Standby or a Standby-F state (not if they are Failed). See the dspcds description for information on card states.

Because YRED (Y redundancy) could be considered a misnomer for the SONET APS two-slot case, these alias commands support card redundancy:

•addcdred—same functionality as addyred

•dspcdred—same functionality was dspyred

•delcdred—same functionality as delyred

•prtcdred—same functionality as prtyred

•switchcdred—same functionality as switchyred

Syntax

delyred <primary slot>

Parameters

Parameter

Description

<primary slot>

Specifies the number of the primary slot for which you are deleting Y-cable redundancy.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-4

No

Yes

BPX, IGX

Yes

Yes

Yes

No

Related Commands

addyred, dspyred, prtyred

Example (IGX)

Disable Y-cable redundancy at slot 12.

delyred 12

arnold TN Cisco IGX 8430 9.3.1p Aug. 16 2000 17:31 PST

Slot Other Front Back Channel Configuration
Slot Type Slot Card Card 1 2 3 4 5 6 7 8

Last Command: delyred 12

Next Command:
Example (BPX)

Disable Y-cable redundancy at slot 2.

delyred 2

sw53 VT Cisco BPX 8620 9.3.2o Dec. 6 2000 10:48 GMT

Slot Other Front Back
Slot Type Slot Card Card

Last Command: delyred 2

diagbus (diagnose failed IGX bus)

Diagnose a failed IGX Muxbus or IGX cell bus. This command runs detailed diagnostics to isolate Muxbus problems to a failed card or bus. It is used when a minor alarm is indicated and displaying the alarm (dspalms) screen indicates the message "bus needs diagnosis."

This command can be run only locally with a terminal connected directly to the Control port or remotely from a modem connection. It can not be executed through a virtual terminal (VT) command or when the node's Control port is configured for Cisco WAN Manager mode.

Caution This command can cause a major disruption in service on all lines and connections and should be run only at a time when disruption can be tolerated. It should not be performed except as a last resort.

To fully isolate the failure might require manual removal of cards, including controller cards and so forth. For this reason, the command may not be executed over a Virtual Terminal connection.

If the test is successful, and no problems found, the system displays:

Both buses are OK

Otherwise, the system displays various messages to the operator for additional steps to perform in isolating the problem. These messages depend on the results of the diagnostics testing.

Syntax

diagbus

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

IGX

Yes

dncd (down a card)

Downs (deactivates) a card. When you down a card, it is no longer available as a node resource. You should down a card before you remove it from a card cage. Before it actually downs an active card, the node determines if a standby card is available. If no standby card is present, the node gives you an opportunity to abort the command. If a standby card of the same type is available and you execute dncd, the standby card is activated. If no standby card is available and you execute the command, a major alarm results. To activate a downed card, use the upcd command.

Note If you remove a card from a card cage without first executing dncd, no warning appears.

You cannot down a control card (NPM or BCC). Use switchcc for control cards.

If the A-bit Notifications on LMI/ILMI Interface feature is enabled (with cnfnodeparm), after downing the trunk, the master node deroutes the connections or condition the connections due to path fail.

Syntax

dncd <slot number>

Parameters

Parameter

Description

slot number

Specifies the slot number of the card to be downed.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-3

Yes

Yes

BPX, IGX

Yes

Related Commands

dspcds, resetcd, upcd

Example

Down the card in slot 9.

dncd 9

sw180 TN Cisco IGX 8420 9.3.g0 Oct. 20 2000 09:14 GMT

FrontCard BackCard FrontCard BackCard
Type Rev Type Rev Status Type Rev Type Rev Status
1 NPM BVS Standby 9 FRM KSB FRI-T1 AL Down
2 NPM BWS Active 10 Empty universal backplane
3 Empty universal backplane 11 Empty universal backplane
4 UXM CD23 T3 AA Active 12 URM AA11 2FE2V EW Active
5 UXM CA23 OC3 AD Active 13 LDM CK03 232-8 AJ Standby-T
6 FRM DHZ FRI-V35 BD Standby 14 URM AA13 2FE2V P03 Active
7 Empty universal backplane 15 URM AA12 2FE2V EW Active
8 Empty 16 NTM FHF T1 AL Active

Last Command: dncd 9

dncon (down connection)

Deactivates (downs) a connection, bundle of connections, a connection group or all connection in a COS or COS range. The dncon command temporarily removes one or more connections from the network. This command is useful for temporarily removing voice connections when additional bandwidth is necessary for other types of connections.

Connections can be downed immediately or with courtesy. Even with immediate downing, a prompt appears that requests confirmation. With courtesy downing, the system waits until the connection is on-hook before downing the connection.

Courtesy downing is possible only if the on-hook status has been configured by using the cnfvchtp command. The upcon command reactivates the voice connections. The up/down status of the voice connections appears in the "State" field of the dspcons screen.

Syntax

dncon {<group | local_chan(s)> | COS <cos_range>} {i | c}

Parameters

Parameter

Description

<group | local_chan(s)>

Specifies a group, or a channel, or a range of channels to down.

COS <cos_range>

Specifies the COS or COS range. Range: 0-15

i | c

Specifies immediate downing (i) of the specified connections or courtesy downing (c) of the specified connections.

Display Fields

State

Description

"OK" (routed)

Connection is activated and able to carry traffic.

"Down"

Connection has been added to the network database but is not activated and is not able to carry traffic.

"OK(Dn)"

Waiting for on-hook to occur to allow courtesy down to take place for connection(s) that have been courtesy downed using the dncon command.

"Failed"

Unrouted, but trying to reroute.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

IGX

Yes

Related Commands

upcon

Example

Down connection 14.1 with courtesy.

dncon 14.1 c

Example

Down connection 14.1 immediately.

dncon 14.1 i

Example

Courtesy down on-hook connections network-wide with COS 4 through 8. This command marks all connections that may be courtesy downed at one time and does not monitor new connections or those that later fit the COS.

dncon cos 4-8 c

Example

Immediately down connection 3.1.100.

dncon 3.1.100 i

pubsigx1 TN SuperUser IGX 32 9.3 Apr. 13 2000 16:51 GMT

Local Remote Remote
Channel NodeName Channel State Type Compress Code COS
3.1.100 pubsigx1 3.2.200 Ok fr
3.2.200 pubsigx1 3.1.100 Ok fr

This Command: dncon 3.1.100 i

Down these connections (y/n)?
Example

Immediately down all connections network-wide with COS 4 through 8. This command executes once, so if individual connections are subsequently upped or new connections added in this COS range, they remain up.

dncon cos 4-8 i

dnln (down line)

Deactivates ("downs") a line. After dnln executes, the line no longer generates framing, and no statistics are gathered. (Alias: the dncln command is identical.)

Before you deactivate a line, use delcon to remove all connections on the line and use dnport to deactivate the port associated with the line.

The dnln command is also used to deactivate an IMA line on the IGX only. As with the other lines, you must remove all connections on the IMA line (delcon or delcongrp), then deactivate the port by using the dnport command. You then can deactivate the line by using dnln.

For the BPX: before you can down a line, all ports must be detected by using the delport command. Downing will not remove the port.

Syntax

dnln <[slot.] [line number]>

Parameters

Parameter

Description

[slot.]

Specifies the slot number, if the back card (such as a UXM card) has one line.

[line number]

Specifies the line. If the card has more than one line, include a line number.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

BPX, IGX, IPX

Yes

Related Commands

upcln, dsplns, dsptsmap

Example

Deactivate line 5.1 (the primary link for an IMA line). After this command executes, the system displays the status of the line using the same information as dsplns displays.

dnln 5.1

sw225 TRM StrataCom IGX 8420 9.3.a6 Mar. 10 2000 05:54
GMT

Line Type Current Line Alarm Status
8.1 T1/24 Clear - OK
9 E1/30 Clear - OK

Last Command: dnln 5.1

dnport (down port)

Deactivates (or downs) the specified port (Frame Relay, ASI, BXM, virtual, or physical port). Before downing a port, you must remove all connections from the port (see delcon definition).

Syntax

dnport <slot.port>[.<vport>]

For UFM-U, FRM, or FRP:
dnport <slot.port>

For UFM-C:
dnport <slot.port> <line.ds0_range>

Parameters

Parameter

Description

slot

Specifies the slot number of the Frame Relay card with the port to down.

port

Specifies the port number to deactivate on the card specified by slot.
Range (FRP or FRM): 1-24 or 1-31
Range (UFM-C): 1-250
Range (UFM-U with a V.35 or X.21 interface): 1-12
Range (UFM-U with a HSSI interface): 1-4

[.vport]

The optional vport identifier on the BXM card only. Range: 1-31

line

The physical line on UFM-C card sets (not used for UFM-U cards).

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

BPX, IGX

Yes

Related Commands

cnfport, dspport, upport, addport, delport, cnffrport, dspfrport, upfrport

Example

Down port 3 on the BXM card in slot 11.

dnport 11.3

sw53 TN Cisco BPX 8620 9.3.m0 Dec. 19 2000 13:04 GMT

Port: 11.3 [INACTIVE] Bandwidth/AR BW: 353208/353208
Interface: LM-BXM CAC Override: Enabled
VPI Range: 0 - 255 CAC Reserve: 0
Type: UNI %Util Use: Disabled
Shift: SHIFT ON HCF (Normal Operation)
SIG Queue Depth: 640 Port Load: 0 %

Protocol: NONE Protocol by Card: No

Last Command: dnport 11.3
Example

Down Frame Relay port 9.2.

dnport 9.2

sw108 VT Cisco IGX 8420 9.3.q2 Dec. 20 2000 12:56 GMT

Port: 9.2 [INACTIVE]
Interface: V35 DCE Configured Clock: 256 Kbps
Clocking: Normal Measured Rx Clock: 0 Kbps

Port ID 0 Min Flags / Frames 1
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec
DE Threshold 100 % N391 Full Status Poll 6 cyl
Signalling Protocol None EFCI Mapping Enabled No
Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Interface Control Template
N393 Monitored Events Count 4 Lead CTS DSR DCD
Communicate Priority No State ON ON ON
Upper/Lower RNR Thresh 75%/ 25%

Last Command: dnport 9.2

dntrk (down trunk)

Downs a trunk, after which it no longer carries framing or statistics. Before you can down a trunk by using dntrk, you must remove it from the network by using deltrk (or delshelf in a tiered network).

Syntax

dntrk <slot.port>[.vtrk]

(No space exists between the port number and the "." for the virtual trunk specification.)

Parameters

Parameter

Description

slot.port

Specifies the physical trunk.

vtrk

Specifies a virtual trunk number (applies to BNI only).
Range (T3/E3): 1-32
Range (OC-3) 1-11

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

BPX, IGX

Yes

Related Commands

addtrk, deltrk, uptrk, dsptrks

Example (IGX)

Deactivate trunk 3.4.

dntrk 3.4

sw108 VT Cisco IGX 8420 9.3.q2 Dec. 19 2000 12:17 GMT

TRK Type Current Line Alarm Status Other End
4.2 OC3 Clear - OK sw180/5.1
4.4 OC3 Clear - OK sw53/11.2
14 T1/24 Clear - OK sw180/8

Last Command: dntrk 3.4

dport (display port)

Display port Qbin information.

Syntax

dport <slot.port>[.<vport>] qbn | *

Parameters

Parameter

Description

<slot.port>

Specifies the slot number of the card and the physical port.

[.<vport>]

Optionally specifies a virtual port number. BXM card only.
Range: 1-31

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

BPX, IGX

Yes

Related Commands

addport, dspportq, cnfportq

Example

Display Qbin 1 database information for port 11 on BXM card 1.

dport 11.1 1

sw53 VT Cisco BPX 8620 9.3.m0 Dec. 19 2000 11:05 GMT

Qbin Database 11.1 on BXM qbin 1

algorithm 3
depth 20000
clp hi 80
clp lo 60
efci 20
vc shaping Disabled
BW INC Cells 200
BW INC Pages 1

Last Command: dport 11.1 1
Example

Display Qbin summary information for port 11.1 on a BXM card.

dport 11.1 *

sw53 VT Cisco BPX 8620 9.3.m0 Dec. 19 2000 11:06 GMT

Qbin Bandwidth Database 11.1 on BXM

Qbin Bandwidth Increment Qbin Bandwidth Increment
0 50 1 8 0 0
1 200 1 9 0 0
2 50 1 10 0 0
3 0 0 11 0 0
4 0 0 12 0 0
5 0 0 13 0 0
6 0 0 14 0 0
7 0 0 15 0 0

Last Command: dport 11.1 *

drtop (display route op table)

Displays the routing table from the local node to each connected remote node.

The drtop command displays the routing table from the local node to each remote node to which it connects. It shows how NPM/B.C. traffic is routed to other nodes in the network. Use drtop to find which trunks are used to send control cells or packets to other nodes.

The display includes remote node name, number of hops to the remote node, the trunks used, and number of satellite hops if any, and the number of unused DS0s (open space), if any, on the route.

Syntax

drtop

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

dsptrkcons

Example

drtop

pubsipx2 VT SuperUser IGX 8430 9.3 Apr. 13 2000 02:27 GMT

Node Number Node Name Hops To Via Trk SAT Hops No HP Hops Open Space
1 npubsbpx1 2 6 0 0 3
2 npubsigx1 3 6 0 0 3
3 npubsigx2 0 0 0 0 0
5 npubsigx1 1 6 0 0 24
7 npubsigx3 2 6 0 0 24

Last Command: drtop

Next Command:

dspabortlog (display abort log)

Displays the abort errors log. The log contains up to six entries. When the log is full, additional aborts overwrite the oldest entries.

Log contains only fatal entries. The log for software errors (dspswlog command) contains only non-fatal entries.

A lighted icon "AB" at the bottom of the command line interface indicates that a software abort has been logged. Not related to the command, but also displayed at the bottom of the command line interface, the "CD" icon indicates a card or hardware error, and the "SW" icon indicates a software error.

Syntax

dspabortlog [<d> | <number> | <c> ]

Parameters

Parameter

Description

<d>

Displays the detailed version of the log, including stack dumps. Page through the detailed version of the log by using the arrow keys or the Return key.

<number>

When an entry number is entered (found under the No. column), displays the detailed version of a specific entry in the log.

<c>

Clears the log. Optionally, you can use the clrabortlog command.

Display Fields

Field

Description

No.

Abort entries in the table, numbered from 1-12.

Type Error

The entry identifier. For the dspabortlog command, the identifier is "abort." Occasionally, the identifier "BadType," is displayed, indicating a problem within the table itself.

Number

The number that identifies a specific abort problem.

Data (Hex)

A 4-byte field containing information that may be useful in solving a problem. It is different for every abort number.

PC (Hex)

Program Counter. The address of the place in memory where the software was running when the abort was logged; this identifies where the problem was detected.

PROC

Process or Task. This field indicates which process was running when the problem occurred. In the above example, TN_2 is the second Telnet user task. Use the dspprf command to display all of the tasks.

SwRev

Switch software version operating on this node.

Date

Date of the abort.

Time

Time of the abort.

Related Commands

clrswlog, dspswlog, clrabortlog

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Example

Displays a detailed log for abort number 1.

dspabortlog 1

sw150 TRM StrataCom IGX 8420 9.3.0L Feb. 2 2000 12:35 GMT

Active Control Card's Software Log
No. Type Number Data(Hex) PC(Hex) PROC SwRev Date Time
1. Abort 1000001 00000000 301EAED2 TN_2 9.3.0L 02/02/00 11:09:12

SSP 306B1310 10 00 30 28 F8 C2 70 08 30 6B 06 40 00 81 00 81 ..0(..p.0k.@....
SSP 306B1320 00 01 00 81 30 53 55 E8 30 6B 06 6C 00 00 00 0C ....0SU.0k.l....
USP 306B066C 00 00 00 00 00 00 00 01 00 00 00 04 31 5A B7 7C ............1Z.|
USP 306B067C 30 53 D6 F8 31 5A DE 28 00 00 02 40 30 53 D6 F8 0S..1Z.(...@0S..
USP 306B068C 00 00 00 4F 30 52 1A 56 00 00 00 01 00 00 00 01 ...O0R.V........
USP 306B069C 30 6B 07 34 30 52 46 50 00 00 00 01 31 5A D1 64 0k.40RFP....1Z.d
USP 306B06AC 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
USP 306B06BC 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
USP 306B06CC 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
USP 306B06DC 00 0D 00 00 00 00 00 00 31 5A B7 7C 00 00 00 01 ........1Z.|....

Last Command: dspabortlog 1

dspalms (display current node alarms)

Displays major and minor alarms throughout the network and specific alarms at the local node. The dspalms command displays:

•The number of failed connections on the node.

•The number of sources failed.

•The number of major and minor circuit line alarms on the node.

•The number of major and minor trunk alarms on the node. Trunk alarms are differentiated between those trunks that are disabled and trunks that are not disabled.

•The number of failed cards on the node.

•The number of missing cards on the node.

•The number of alarms on other nodes in the network.

•The number of APS lines in alarm.

•The number of junction node alarms when the Cisco WAN Manager terminal is at a junction (physically, or vt).

•The number of unreachable nodes in the network.

•The power supply and power monitor failures on the node.

•Bus failures (either "Failed" or "Needs Diagnostics").

•FR/ATM Port Communication Failed (OAM Packet Threshold exceeded).

•FR/ATM NNI A-bit Alarms (connections with A-bits=0).

•Slot alarms on IGX due to insufficient bus bandwidth allocation on a slot containing a UXM card.

•ASM card alarms on BPX nodes.

•The number of APS lines that are in alarm. Statistical alarms are not cleared on an APS switch. This is consistent with the way card redundancy works (sometimes referred to as "YRED"). Statistical alarms are not cleared on a YRED switch.

•IOS-status alarms on the Universal Router Module (URM) embedded router.

The URM is supported on the IGX 8400 with Release 9.3.20. The URM provides IOS-based voice support and basic routing functions. It consists of an embedded UXM with one internal ATM port and an embedded IOS-based router. The internal ATM port is the communication bridge between the embedded router and switch software.

When the router is not operational (in other words, it cannot route packets among its interfaces, including the internal ATM interface), switch software generates a minor alarm and fails all connections that terminate on the internal port. When an embedded router is not operational, dspalms shows the URM slot number and reports the router status as unavailable (IOS field). A "Minor Alarm" is also displayed in the bottom right corner of the dspalms screen.

For more details on each type of alarm, use the "display" command associated with each failed item. Table 4-2 shows the display commands that show error information.

Table 4-2 Commands that Display Error Information

Command

Description

dspcds

Displays cards in the node, with F for failures.

dsplns

Displays circuit lines.

dspcons

Displays connections.

dsplog

Displays events affecting the node.

dspnds

Displays unreachable nodes within a network.

dspnw

Displays the network topology and includes alarm status of each node in the network.

dsptrks

Displays trunks.

dsppwr

Displays power supply status and internal temperature.

dsprtrslot

Displays operational information and alarm status for a specified URM embedded router.

dsprtrslots

Displays operational information and alarm status for all URM embedded routers in a node.

Syntax

dspalms

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

dspcds, dsplns, dspcons, dsplog, dspnw, dsptrks, dsppwr, dsprtrslot, dsprtrslots

Example (BPX)

Display a summary of all alarms affecting the BPX node.

dspalms

sw167 TN Cisco BPX 8620 9.3.2Q Dec. 13 2000 14:17 PST

Alarm summary (Configured alarm slots: None)
Connections Failed: None
TRK Alarms: None
Line Alarms: None
Cards Failed: None
Slots Alarmed: None
Missing Cards: None
Remote Node Alarms: 1 Minor
APS Alarms: None

Interface Shelf Alarms: 1 Minor
ASM Alarms: None

Last Command: dspalms
Example

Display APS alarms.

dspalms

alexa TRM genre BPX 8620 9.3 Apr. 13 2000 16:35 PDT

Alarm summary (Configured alarm slots: None)
Connections Failed: None
TRK Alarms: None
Line Alarms: None
Cards Failed: None
Slots Alarmed: 1 Major
Missing Cards: 1
Remote Node Alarms: 1 Minor
APS Alarms: 1 Minor

Interface Shelf Alarms: None
ASM Alarms: None

Last Command: dspalms
Example (IGX)

Display the current alarms on an IGX node.

dspalms

sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 09:23 PST

Alarm summary (Configured alarm slots: None)
Connections Failed: None
TRK Alarms: None
Circuit Line Alarms: None
Physical Line Alarms: None
Cards Failed: 2
Missing Cards: None
Remote Node Alarms: 1 Unreachable, 2 Majors, 5 Minors

Interface Shelf Alarms: None

FastPAD/Access Dev Alms: None

Last Command: dspalms

Next Command:

MAJOR ALARM
Example

Display the current alarms on an IGX node with a Universal Routing Module (URM). Check the operational status of the embedded IOS-based router. When the router is not operational, the IOS field shows the router as unavailable and reports the URM slot number. A "Minor Alarm" is also displayed when the router is not operational.

dspalms

sw190 TRM Cisco IGX 8420 9.3.e8 Oct. 4 2000 10:38 GMT

Alarm summary (Configured alarm slots:None)
Connections Failed: None
TRK Alarms: None
Circuit Line Alarms: None
Physical Line Alarms: None
Cards Failed: None
Missing Cards: None
Remote Node Alarms: None

IOS Unavailable in 1 slot
Interface Shelf Alarms: None

FastPAD/Access Dev Alms: None

Last Command:dspalms

Next Command:

Minor Alarm

dspapsln (display APS lines)

The dspapsln command displays the currently configured APS lines and their status.

Syntax

dspapsln

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

No

No

BPX

No

Related Commands

addapsln, delapsln, cnfapsln, cnfapsln, dspapsln, dsplog, dspalms

Example

Display all the currently configured APS lines and their status.

dspapsln

alexa TRM genre BPX 8600 9.3 Apr. 13 2000 16:25 PDT

Actv Active Line Standby Line Current APS Last User
Work/Protect Line Alarm Status Alarm Status Alarm Status Switch Req

2.1 3.1 PROT OK OK Loss of Sig(RED) Clear
5.1 5.2 WORK OK LOS LOS Lockout
6.3 6.4 NONE Deactivated APS Deactivated
10.1 11.1 PROT OK OK Standard Mismatch Clear

Command: dspapsln

Example

Display currently configured APS lines and their status.

dspapsln

sw117 TRM genre BPX 8620 9.3 Apr. 13 2000 16:25 PDT

Work/Protect Actv Active Line Standby Line Current APS Last User
(Work 1/Work 2) Line Alarm Status Alarm Status Alarm Status Switch Req
2.2 3.2 WORK Loss of Sig (RED) Remote (YEL) Remote (YEL) Clear

Command: dspapsln

dspasich (display ASI channel routing entry)

Displays the ATM channel routing entries for an ASI card.

Syntax

dspasich <line> <channel>

Parameters

Parameter

Description

<line>

Specifies the line in the format slot.port.

<channel>

Specifies the channel in the format vpi.vci.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

Yes

No

BPX

Yes

Example: ASI Channel Routing Entry

dspasich 5.1 1 N

pubsbpx1 VT SuperUser BPX 15 9.3 Apr. 13 2000 21:09 GMT
ASI Channel Configuration Query & Display

Slot.port.lcn:5.1.1
Status: Added BF hdr: 4145 9002 8012 0501 8640 0000 2DEB
[00] BF tp: 4 [11] VCI: 00000064 [22] UPC CDV: 0 [33] FST up: 0
[01] Pri SDA: 5 [12] Con tp: VC [23] UPC CIR: 500 [34] FST dn: 0
[02] Dst Prt: 1 [13] Rmt tp: ASI [24] UPC CBS: 1000 [35] FST fdn: 0
[03] Dst lcn: 2 [14] Srv tp: VBR [25] UPC IBS: 0 [36] FST rmx: 0
[04] BCF tp: 0 [15] Gen AIS: N [26] UPC MFS: 200 [37] Q max:64000
[05] Qbin#: 12 [16] Mcst: 0 [27] CLP enb: Y [38] EFCI: 100
[06] BF VPI: 64 [17] Mc grp: 1 [28] FST enb: N [39] CLP hi: 100
[07] BF VCI: 0 [18] & msk: 0000000F [29] FST MIR: 500 [40] CLP lo: 100
[08] Pl Cls: 0 [19] | msk: 06400640 [30] FST PIR: 500 [41] BCM: N
[09] Rmt lp: N [20] Prt QBN: 2 [31] FST QIR: 500 [42] Inhibit:N
[10] VPI: 00000064 [21] UPC GCR: 0 [32] QIR TO: 0 [43] UPC enb:Y

Last Command: dspasich 5.1 1 N

Next Command:

dspasm (display ASM card)

Displays BPX node alarms that, when active, produce an external alarm output (relay closure). These alarms are associated with powering and cooling the node as well as a statistics count.

For example, a minor alarm is generated when a fan speed drops below 2000 rpm. Because the single ASM card is always located in slot 15, you do not need to enter a card slot for this command. To configure the ASM alarms, use cnfasm (a SuperUser command).

Syntax

dspasm

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

No

No

BPX

Yes

Related Commands

cnfasm

Example

Display the ASM card parameters.

dspasm

D1.jea TRM SuperUser BPX 8620 9.3 Apr. 13 2000 12:24 GMT

ASM Status: Active ASM Alarms
Statistics count: 7 Fan #1 RPM out of range
Statistics timeouts: 0 Fan #2 RPM out of range
Cabinet temperature: 21 C Fan #3 RPM out of range
Power voltage A/B: 0.0 / 0.0 V

PSU Ins Type Rev SerNum Failure
A N N/A N/A N/A N/A
B N N/A N/A N/A N/A

FAN 1 2 3
0000 0000 0000 RPM

Last Command: dspasm

Next Command:

dspatmcls (display ATM connection class)

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

Syntax

dspatmcls <class number>

Parameters

Parameter

Description

class number

Specifies the class whose current parameters you want to see.
Range: 1-10

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

BPX, IGX

No

Related Commands

addcon, cnfatmcls, dspcls, cnfcls, dspcon, dspcons

Example

Display the parameters for configuration class 1.

dspatmcls 1

night TN SuperUser BPX 8620 9.3 Apr. 13 2000 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:
Example

Display the parameters for configuration class 1.

dspatmcls 1

night TN SuperUser BPX 8620 9.3 Apr. 13 2000 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:

dspbmpparm (display priority bumping parameters)

Displays the priority bumping parameters.

Syntax

dspbmpparm

Parameters

Parameter

Values

Description

Priority Bumping Enabled

ON or OFF

Default: OFF

This flag specifies whether the priority bumping feature is activated on the node.

Priority Bumping Bundle

1-50
Default: 10

The number of connections that can be selected in a priority bumping routing request when PB is enabled.

Bumping Band 1

1-15

Default: 2

The lowest value in the second most important COS band. Connections with a COS value below Bumping Band 1 are implicitly grouped as the most important band, Band0.

Connections in Band 0 can bump those in other bands, but cannot be bumped.

Connections in Band 1 can bump those in bands 2-7, and can only be bumped by those in Band 0.

Bumping Band 2

1-15

Default: 4

The lowest value in the third most important COS band. Connections in this band can bump those in bands 3-7, and can be bumped by those in bands 0-1.

Bumping Band 2 cannot be less than Bumping Band 1.

Bumping Band 3

1-15

Default: 6

The lowest value in the fourth most important COS band. Connections in this band can bump those in bands 4-7, and can be bumped by those in bands 0-2.

Bumping Band 3 cannot be less than Bumping Band 2.

Bumping Band 4

1-15

Default: 8

The lowest value in the fifth most important COS band. Connections in this band can bump those in bands 5-7, and can be bumped by those in bands 0-3.

Bumping Band 4 cannot be less than Bumping Band 3.

Bumping Band 5

1-15

Default: 10

The lowest value in the sixth most important COS band. Connections in this band can bump those in bands 6-7, and can be bumped by those in bands 0-4.

Bumping Band 5 cannot be less than Bumping Band 4.

Bumping Band 6

1-15

Default: 12

The lowest value in the seventh most important COS band. Connections in this band can only bump those in Band7, and can be bumped by those in bands 0-5.

Bumping Band 6 cannot be less than Bumping Band 5.

Bumping Band 7

1-15

Default: 14

The lowest value in the least important COS band. Connections in this band cannot bump, but can be bumped by those in bands 1-6.

Bumping Band 7 cannot be less than Bumping Band 6.

Priority Bumping Active on this node?

YES or NO

Default: NO

Indicates whether priority bumping is enabled or disabled on a particular node.

Number of Priority Bumping Bands

0-7

Indicates the number of priority bands enabled. If priority bumping is not enabled, this value is 0.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

Yes

Yes

BPX, IGX

Yes

Related Commands

cnfbmpparm

Example

Use dspbmpparm to view the priority bumping parameters. Priority bumping for the whole network is shown at the top of the display, and then at the bottom for a specific node.

igxr2 TN StrataCom IGX 8420 9.3.0K Jan. 26 2000 15:19 PDT

1 Priority Bumping Enabled [ YES]
2 Priority Bumping Bundle [ 10] (D)
3 Priority Bumping Bands:
Bumping Band 1 [ 2] (D)
Bumping Band 2 [ 4] (D)
Bumping Band 3 [ 6] (D)
Bumping Band 4 [ 8] (D)
Bumping Band 5 [ 10] (D)
Bumping Band 6 [ 12] (D)
Bumping Band 7 [ 14] (D)

Priority Bumping Active on this node [ YES]
Number of Priority Bumping Bands [ 7] (D)

Last Command: dspbmpparm

bpx1 TN StrataCom BPX 8620 9.3.0K Jan. 26 2000 14:20 PST

1 Priority Bumping Enabled [ YES]
2 Priority Bumping Bundle [ 10] (D)
3 Priority Bumping Bands:
Bumping Band 1 [ 2] (D)
Bumping Band 2 [ 4] (D)
Bumping Band 3 [ 6] (D)
Bumping Band 4 [ 8] (D)
Bumping Band 5 [ 10] (D)
Bumping Band 6 [ 12] (D)
Bumping Band 7 [ 14] (D)

Priority Bumping Active on this node [ NO]
Number of Priority Bumping Bands [ 0] (D)

Last Command: dspbmpparm

dspbmpstats (display priority bumping statistics)

Displays priority bumping operational statistics for the priority bumping feature.

Syntax

dspbmpstats

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

Yes

Yes

BPX, IGX

Yes

Related Commands

dspbmpparm, cnfbmpparm, dsprrst s, rrtinf

Display Fields

Statistics Object

Description

Latest bumping band

The band value of the latest reroute connection that originates from this node.

Latest bumped band

The band value of the latest connection that is bumped from this node. The bumped connection can be mastered or slaved on this node. It can even be simply traversing this node. The bumping connection also can be mastered on, slaved on, or simply that originates from this node.

Hvm bumping band

The high water mark, since the last resetting of statistics, of the band value of any reroute connection that traverses this node

Lwm bumped band

The low water mark, since the last resetting of statistics, of the band value of any connection that has been bumped from this node.

Latest # bumping conns/req

The number of reroute candidate connections in the most recent reroute request. If there are many similar connections to be routed to the same destination, this value usually represents the bundle size of the Priority Bumping reroute request.

Latest # bumped conns/req

The number of connections selected to be bumped from this node in the most recent reroute request.

Hwm # bumping conns/req

The high water mark, since the last resetting of statistics, of the number of reroute candidate connections in any reroute request.

Hwm # bumped conns/req

The high water mark, since the last resetting of statistics, of the number of connections selected to be bumped from this node in any reroute request.

Accum # bumping conns

The total number, since the last resetting of statistics, of successfully routed connections.

Accum # bumped Lcons

The total number, since the last resetting of statistics, of master or slave connections bumped from this node.

Avg # bumping conns/req

The average number, since the last resetting of statistics, of successfully routed connections in a reroute request.

Accum # bumped VLcons

The total number, since the last resetting of statistics, of via connections bumped from this node.

Example (BPX)

dspbmpstats

sw67 TN StrataCom BPX 8620 9.3.0L Jan. 28 2000 18:57 PST

PB Routing Statistic

Latest bumping band - Latest bumped band -
Hwm bumping band - Lwm bumped band -

Latest # bumping conns/req 0 Latest # bumped conns/req 0
Hwm # bumping conns/req 0 Hwm # bumped conns/req 0

Accum # bumping conns 0 Accum # bumped Lcons 0
Avg # bumping conns/req 0.00 Accum # bumped VLcons 0

Last Command: dspbmpstats

dspbob (display breakout box)

Shows the current state of all inputs from user equipment to the node the state of all outputs from the node to the user equipment. The display is real-time and updated at a user-specified interval. The display refreshes at the designated interval until the Delete key is pressed or until it times out.

See the cnfict description for information on configuring data interfaces. When used with Frame Relay T1/E1 applications, dspbob displays the message "This FRP does not support V.35 ports."

Displaying Signal Status for Port Concentrator Ports

If an FRM-2 or FRP-2 card connects to a Port Concentrator Shelf (PCS), you can specify up to 44 ports by using the port parameter. In this case, dspbob displays the signal status for ports on the PCS. The PCS relays any changes in signal states to the FRM-2 or FRP-2, so a slight delay occurs when signals are updated.

When used for PCS ports, dspbob has an optional parameter measuring port clock speed. Selection of this parameter temporarily interrupts all traffic on the logical port. The events that take place upon input of this parameter are:

1. The port is disabled.

2. Two invalid frames are timed as they go out the port.

3. The port is reactivated.

Syntax

dspbob <slot><port> [interval] [(measure clock speed) y | n ]

Parameters

Parameter

Description

<slot>

Specifies the slot number of the card containing the port whose input and output pins are to be displayed.

<port>

Specifies the data port or Frame Relay port whose input and output pins are to be displayed.

[interval]

Optionally specifies the time in seconds, between updates of the breakout box display. If no interval is specified, the display is updated at five second intervals. Do not use an interval of "1" second in a busy network.
Range: 1 to 60 seconds

[(measure clock speed) y | n ]

For Port Concentrator Shelf (PCS) only, optionally directs the system to measure the clock speed.

If a Port Concentrator port is selected, the last measured clock speed is displayed on the Clocking line. When Measure Clock Speed is entered as an optional parameter, the clock is measured first, and the results are displayed. Clock speed measurement for PCS ports is described in the Cisco WAN Switching System Overview information for the PCS.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

Yes

Related Commands

cnfict, dspcon, dspict

Example

See the breakout box display for channel 5.1.

dspbob 5.1

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 11:29 PST

Port: 5.1
Interface: V35 DCE
Clocking: Normal (255999 Baud)

Inputs from User Equipment Outputs to User Equipment
Lead Pin State Lead Pin State Lead Pin State Lead Pin State
RTS C Off CTS D On
DTR H Off DSR E On
TxD P/S Idle DCD F Off
TT U/W Unused RI J Off
TM K Off
RxD R/T Idle
RxC V/X Active
TxC Y/a Active

This Command: dspbob 5.1

Hit DEL key to quit:
Example

See the breakout box display for Frame Relay connections.

dspbob 9.1

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 11:29 PST

Port: 9.1
Interface: FRI-V35 DTE
Clocking: Normal

Inputs from User Equipment Outputs to User Equipment
Lead Pin State Lead Pin State Lead Pin State Lead Pin State
CTS D Off RTS C On
DSR E Off DTR H On
DCD F Off LT L Off
(TM) n Off (RLB) N Off

This Command: dspbob 9.1

Hit DEL key to quit:

dspbpnv (display backplane NOVRAM)

Issue the dspbpnv command to see the NOVRAM setting for the backplane. For some operations, you must verify if the node has the new backplane or the old backplane. For example, in order for the BPX 8600 to operate at 19.2 Gbps with the BCC-4V, it must have the NOVRAM Word #2 set to 0001 (which indicates that the backplane version is new). If it instead has the NOVRAM Word# set to 0000 (indicating that the backplane version is old) the switch cannot run with a 19.2 Gbps peak throughput. If you visually verify that the backplane is a 19.2 Gbps backplane (see note below), but the backplane NOVRAM Word #2 has not been set to 0001, then issue the cnfbpnv command to program the NOVRAM.

Note You can visually identify the 19.2 backplane by the small white card slot fuses at the bottom rear of the backplane. These fuses are approximately 1/4 inch high and1/8 inch wide. The 9.6 Gbps backplane does not have these fuses. If your BPX switch is a late model, then a 19.2 Gbps backplane is installed.

The following table details the bit fields for the BCC Backplane NOVRAM format. The display in the field Word 2 describes the backplane type.

16 Bit Word

Byte # (hex)

Contents

0

0,1

Hardware revision

1

2,3

Backplane Type (usually 0x65=101 decimal)

2

4,5

Backplane version (0x0000old 0x0001new)

3

6,7

Backplane serial number in ASCII - MSB

4

8,9

Backplane serial number in ASCII - MSB

5

A,B

Backplane serial number in LSB

6

C,D

Board FAB number, in ASCII - MSB

7

E,F

Board FAB number, in ASCII - LSB

8

10,11

Board FAB number, in ASCII - LSB

9

12,13

Board FAB number, in ASCII - LSB

A

14,15

Board FAB number, in ASCII - LSB

B

16,17

Board FAB number, in LSB

C

18,19

Unused

D

1A,1B

Unused

E

1C,1D

Unused

F

1E,1F

Checksum bytes - NOT SUPPORTED

Syntax

dspbpnv

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

Any user

No

No

BPX

No

OK

Yes

No

Related Commands

cnfbpnv

Example (BPX)

View the NOVRAM settings on a BPX 8620.

dspbpnv

sw217 TN Cisco BPX 8620 9.3.x5 June 11 2001 14:34 GMT

BackPlane NOVRAM
----------------
WORD 0: 0x0096 WORD 1: 0x0065
WORD 2: 0x0000 WORD 3: 0x3232
WORD 4: 0x3037 WORD 5: 0x3632
WORD 6: 0x0000 WORD 7: 0x0000
WORD 8: 0x0000 WORD 9: 0x0000
WORD 10: 0x0000 WORD 11: 0x0000
WORD 12: 0x0000 WORD 13: 0x0000
WORD 14: 0x0000 WORD 15: 0x9997

Last Command: dspbpnv

dspbusbw (display cell bus bandwidth for UXM cards)

Displays the amount of bandwidth allocated on the cell bus on an IGX node. By default, the system allocates enough bus bandwidth for one OC-3 when the first line is upped by using the upln command. If there is not enough allocated cell bus bandwidth, the line is not upped. Cell bus bandwidth must be allocated before adding connections on the UXM card.

Syntax

dspbusbw <slot> [u]

Parameters

Parameter

Description

<slot>

Specifies the slot number of the card containing the universal bus bandwidth information to display.

[u]

Optionally specifies that the card should update the information with the latest information calculated in firmware. If not provided, the system will prompt you.

Display Fields

Display

Description

Minimum Required Bandwidth

Minimum bandwidth in FastPackets per second and cells per second required for all connections currently configured on this card.

This is calculated by UXM firmware as connections are added.

Maximum Port Bandwidth

Total bandwidth of all active trunks/ports on this card in FastPackets per second, cells per second, and UBUs.

Average Bandwidth and Peak Used Bandwidth

Statistics counters maintained by UXM firmware. These statistic counters display FastPackets per second, cells per second, and UBUs. Use this information when calculating the amount of bus bandwidth to be allocated.

These counters are cleared when the UXM card is reset.

Last Updated time

Shows the time when the counters were last updated. This is the current time if you answered yes to the Get updated bandwidth info from card (Y/N)? prompt or entered the command with the u parameter.

Allocated Bandwidth

The bandwidth allocated for this card using the cnfbusbw command. Refer to the Cisco WAN Switching SuperUser Commands manual for more information. Allocated bandwidth is specified in FastPackets per second, cells per second and converted to UBU units by the system.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX (with UXM)

Yes

Related Commands

cnfbusbw

Example

Display the amount of bandwidth allocated on the cell bus on the UXM card in slot 6 of the IGX node.

dspbusbw 6

Get updated bandwidth info from card (Y/N)? n

sw199 TN StrataCom IGX 16 9.3 Apr. 13 2000 17:52 GMT

1\NBus Bandwidth Usage for UXM card in slot 6 Last Updated on 04/07/98 12:03:0
0
FPkts/sec Cells/sec UBUs
Minimum Reqd Bandwidth: 0 0 0
Average Used Bandwidth: 0 0 0
Peak Used Bandwidth: 0 0 0
Maximum Port Bandwidth: - 10866 3

Allocated Bandwidth: 8
(Cell Only): - 32000
(Cell+Fpkt): 16000 24000
(Fpkts / 2 + Cells) <= 32000

Reserved Bandwidth: - 4000 1

Last Command: dspbusbw 6

Next Command: dspbusbw 6

Get updated bandwidth info from card (Y/N)? y

sw199 TN StrataCom IGX 16 9.3 Apr. 13 2000 17:53 GMT

1\NBus Bandwidth Usage for UXM card in slot 6 Last Updated on 04/09/98 17:53:2
2
FPkts/sec Cells/sec UBUs
Minimum Reqd Bandwidth: 0 0 0
Average Used Bandwidth: 0 0 0
Peak Used Bandwidth: 0 0 0
Maximum Port Bandwidth: - 10866 3

Allocated Bandwidth: 8
(Cell Only): - 32000
(Cell+Fpkt): 16000 24000
(Fpkts / 2 + Cells) <= 32000

Reserved Bandwidth: - 4000 1

Last Command: dspbusbw 6

dspbuses (display bus status)

Displays the available Muxbus or cell bus bandwidth. The display does not dynamically receive updates and is therefore a snapshot. The dspbuses command lists the dedicated and pooled bandwidth units as well as the status of the available Muxbus.

As a safeguard against bus failure, each node is equipped with redundant System Buses: Bus A and Bus B. Either bus can be configured as the active bus with the other bus as standby. Use the cnfbus command to switch the active bus.

Each System Bus contains these buses:

•Control Bus

•Time Division Multiplex (TDM) bus

•clock bus

•power bus

In addition to showing which System Bus is active and which is standby, the dspbuses command also shows which sub-bus needs diagnostics or has failed. Bus status is displayed at the bottom of the screen. Table 4-3 shows the possible status displays and their meaning.

Table 4-3 Possible Bus Status Displays

Status

Description

OK

Bus operation satisfactory

Failed TDM

A failed TDM Bus

Failed CNTL

A failed Control Bus

Needs Diagnostics TDM

The TDM bus needs diagnostics

Needs Diagnostics CNTL

The Control Bus needs diagnostics

The remaining cell bus bandwidth available to assign to cards and circuits is displayed. This is primarily used when configuring the AIT card on the IGX node. You can assign CELLBUS bandwidth for the IGX node.

Available bandwidth falls into two categories:

•Dedicated
Dedicated bandwidth is reserved by the system for specific purposes, such as Statistical Reserve for PCC traffic.

•Pooled
Pooled bandwidth can be assigned to any use but primarily is used for an ATM trunk.

Cell bus bandwidth is assigned in quantities of "switches," "slices," and "circuits" and the available bandwidth is displayed in three rows accordingly. A single DS0 circuit occupies 333 packets per second (pps) of cell bus bandwidth, a "slice" of bandwidth is equivalent to three DS0 circuits for a total of 1000 pps. A switch is eight slices for a total of 8000 packets/second of bus bandwidth.

In a newly installed node with no cards and no circuits installed, the total bus bandwidth that is available to be assigned is listed in the right column of the following table, which is the sum of the dedicated and pooled bandwidth. As cards and circuits are added to the node, the available bandwidth decreases accordingly.

Table 4-4 Bandwidth Units and Capacity

Unit of BW

Quantity

Cell Bus Capacity

switch

8 slices or 8000 pps

20

slice

3 DS0s or 1000 pps

160

DS0

333 pps

480

Syntax

dspbuses

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

cnfbus

Example (BPX)

dspbuses

bpx1 TN SuperUser BPX 15 9.3 Apr. 13 2000 13:22 GMT

Bus Status

Bus A (slot 7): Active - OK

Bus B (slot 8): Standby - OK

Last Command: dspbuses

Next Command:
Example (IGX)

dspbuses

sw197 TN SuperUser IGX 8420 9.3 Apr. 13 2000 04:10 GMT

Bus Info

Bus Bandwidth usage in Fastpackets/second (Snapshot)

Allocated = 86000 ( 8%)
Available = 1082000 (92%)

-----------
Bus A: Active - OK
Bus B: Standby - OK

Last Command: dspbuses
Example (IGX)

Display status and bandwidth available. The status of Bus A and Bus B is displayed. In this example, both buses are OK and B is the active control bus (normal operation is for bus A to be the active bus).

dspbuses

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 13:34 PST

Bus Info

Available MUXBUS bandwidth (snapshot)

Dedicated Pooled Units
--------- ------ -----
0 13 8000 pkts/sec
5 104 1000 pkts/sec
22 312 ds0 circuits

Bus Status
-----------
Bus A: Standby - OK
Bus B: Active - OK

Last Command: dspbuses

Next Command:

dspcdstats (display UXM card statistics)

The dspcdstats command displays the collected UXM card statistics for the selected node slot.

Syntax

dspcdstats <slot number>

Parameters

Parameter

Description

<slot number>

Specifies the shelf and slot.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

Yes

Yes

BPX

Yes

Related Commands

cnfslotstats, dspsloterrs (for BXM)

Example (IGX)

Display UXM Card Statistics

dspcdstats 9

bolger TN Cisco IGX 8430 9.3.3q May 25 2001 12:23 PST

Slot 9
Collection Time: 1 day(s) 03:15:51 Clrd: Date/Time Not Set
Type Count
QBIN: Ingress Cells Rcv from ln 22
QBIN: Ingress Cells Tx to net 22
QBIN: Ingress Cells discarded 0
QBIN: Ingress FPs Rcv from ln 68013
QBIN: Ingress FPs Tx to net 68013
QBIN: Ingress FPs discarded 0

This Command: dspcdstats 9
Example (IGX) Field Descriptions

Table 4-5 Display Fields for Example UXM

Field

Description

Ingress Cells Rcv from ln

Ingress Cells received from the line (cells into the UXM from it's node).

Ingress Cells Tx to net

Ingress Cells transmitted to the network (cells out of the UXM to the network).

Ingress Cells discarded

Ingress Cells discarded by the UXM.

Ingress FPs Rcv from ln

Ingress fast packets received from the line (fast packets into the UXM from it's node).

Ingress FPs Tx to net

Ingress fast packets transmitted to the network (fast packets out of the UXM to the network).

Ingress FPs discarded

Ingress fast packets discarded by the UXM.

dspcbause (display CBA block usage)

Queries the specified slot and displays information about the CBA blocks. While running this command, it periodically queries the card and the display continuously updates the CBA parameters, showing block usage among AutoRoute and VSI.

To display a summary of CBA usage on all active UXMs on the node, enter dspcbause with no parameters.

To display CBA usage on a specific active UXM card, enter dspcbause with the slot number parameter.

Syntax

dspcbause [slot_no] [interval]

Parameters

Parameter

Description

[slot_no]

Optionally specifies the slot number of a particular UXM card.

[interval]

Optionally specifies the interval in seconds. Default: 10 seconds.

Display Fields

Parameter

Description

CBABlocksAllocated

The number of CBA blocks allocated. 32 CBAs are equal to one block.

CBABlocksUsed

Number of CBA blocks used by the slot for connections.

CBAsUsed

Number of CBAs used by the slot for connections.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

No

No

IGX

Yes

Yes

Yes

No

Example

dspcbause

Display CBA and CBA block use of Automatic Routing Management and VSI (on a node).

sw188 TRM Cisco IGX 8420 9.3.1c Aug. 17 2000 11:10 PST

VSI CBA allocation summary for all slots :

Slot VSI LCNs CBA Blks Actual CBA Blks
to be alloced alloced
4 200 7 7
5 2000 63 63
Last Command: dspcbause

Next Command:
Example

Display CBA and CBA block use among AutoRoute and VSI (on a slot).

dspcbause 5

sw188 TRM Cisco IGX 8420 9.3.1c Aug. 17 2000 11:11 PST

CBA Usage for slot 5

CBA Blocks allocated = 63 CBA Blocks used = 16

CBA Block Bitmap:
80 : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
140 : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
200 : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2C0 : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
380 : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
440 : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
500 : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
5C0 : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
680 : 0 0 F8 FF 7 0 0 0 0 0 0 0

This Command: dspcbause 5

Hit DEL key to quit:

dspcd (display card)

Displays the status, revision, serial number, and top assembly number of a card. If a back card is present, its type, revision, and serial number appear. The displayed information can vary with different card types and appears on a single-page display.

Syntax

dspcd <slot number>

Parameters

Parameter

Description

<slot number>

Specifies the slot number of the card for which you wish to see status and identifying information.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

Yes

Yes

No

Yes

Related Commands

dncd, dspcds, resetcd, upcd

Example (BPX) BXM-155

Display features supported (Support fields) on the BXM card in slot 2. The front card supports the Neighbor Discovery feature (NbrDisc) and the XLMI protocol (XL). Both the LMI Neighbor Discovery feature and XLMI protocol are required for AR-PNNI links in a hybrid network.

dspcd 1

BPX02 TN Cisco BPX 8620 9.3.3W Aug. 13 2001 11:24 PDT

Detailed Card Display for BXM-155 in slot 1
Status: Active
Revision: FA21 Backcard Installed
Serial Number: A66165 Type: LM-BXM
Top Asm Number: 80033333 Revision: BB
Queue Size: 524280 Serial Number: 770491
Supp:8 Pts, OC3, FST, VcShp Top Asm Number:
Supp: VT,ChStLv 1,VSI(Lv 3,ITSM) Supp: 8 Pts,OC3,MMF,RedSlot:NO
Supp: APS(FW), F4F5
Support: LMIv 1,ILMIv 1,NbrDisc,XL
Supp: OAMLp,TrfcGen,PPDPolic,OAM-E
#Ch:32768,PG[1]:32736,PG[2]:32736
PG[1]:1,2,3,4,PG[2]:5,6,7,8,
#Sched_Ch:61440 #Total_Ch:61376
Type: BXME, revision DX

Last Command: dspcd 1

Table 4-6 Display Fields for Example (BPX) BXM-155

Field

Value

Description

BXM Front Card Fields

Status

Displays the status of a card.

Active

Card in use, no failure detected.

Active—F

Card in use, failure detected.

Active—T

Card active, test in progress.

Active—F-T

Card active, minor failure detected, test in progress.

Standby

Card idle, no failure.

Standby—F

Card idle, failure detected.

Standby—T

Card idle, test in progress.

Standby—F-T

Card idle, failure detected, test in progress.

Failed

Card failed.

Down

Card downed by user.

Down—F

Card downed, failure detected.

Down—T

Card downed, failure detected, test in progress.

Mismatch

Mismatch between front card and back card.

Update *

Configuration RAM being updated from active control card.

Locked*

Old software version is being maintained in case it is needed.

Dnlding*

Downloading new system software from the active PCC adjacent node from WAN Manager.

Dnldr*

Looking to adjacent nodes or WAN Manager for either software to load or other software needs you have not specifically requested.

Program

Occurs when new firmware is being burned on the card.

Revision

The firmware/hardware version ID.

Serial Number

The serial number of the card.

Top Asm Number

The card's 800-level part number.

Queue Size

The sum of the sizes of the ATM cell queues in one direction. Queue size = size of HP+TS+BDATA+BDATB+CBR+VBR +SIG+ABR queues.

Support or Supp

The features that the card's firmware and hardware supports.

Pts

The number of physical ports supported by card hardware: OC3 | OC12 |T3 | E3

The card type supported

Indicates firmware supports Foresight.

VcShp

Indicates firmware supports VCshaping.

VT

Indicates firmware supports virtual trunks

ChStLv

The multilevel channel statistics level currently programmed 0-3. The statistics level is configured using the command cnfcdparm. Refer to cnfcdparm (configure card parameters), page 3-143 for more information about multilevel channel statistics.

VSI

The VSI attributes supported. Values are:

lv-VSI level supported by firmware. The level is 0, 1, 2, or 3; the level represents the resources supported, i.e. LCNs, VPI, etc.

ITSM-VSI level supported by firmware.

I = ILMI support.

T = topology support.

S = signalling, QBIN support.

M = multiple partition support.

V = VC merge support.

APS

The APS attributes supported. Values are:

APS(FW)-APS is supported by card firmware.

APS(HW1+1)-APS 1+1 is supported by card hardware.

APS(ChHlv)-The number of channels supported by card is halved in order to support APS 1:1.

F4F5

F4 AIS detection on trunks and F4 AIS to F5 AIS mapping on ports is supported by card firmware.

LMIv

LMI version supported by card firmware.

ILMIv

ILMI version supported by card firmware.

NbrDisc

ILMI neighbor discovery is supported by card firmware.

OAMLp

OAM loopback testing is supported by card firmware.

XL

XLMI protocol supported by card firmware.

TrfcGen

Traffic Generation testing is supported by card firmware.

PPDPolic

OAM-E

OAM Ping feature supported by card firmware.

#Ch

The total number of channels supported by all port groups.

PG[1]:8160 PG[2]:8160

The number of channels contained in each port group.

PG[1]:1,2,3,4,

PG[2]:5,6,7,8

The card physical ports.

#Sched_Ch

The number of scheduler channels supported by card.

#Total_Ch

The total number of channels reported by the BXM cards.

BXM Back Card Fields

Type

The type of backcard: LM-BXM, T3-3, E3-3, T3-2, E3-2, SMF, MMF, SMFLR, LMASM, STM1, UTP, STP.

Revision

The hardware version ID.

Serial Number

The serial number of the card.

Top Asm Number

(TAN) The 800-level part number of the card.

Supp

The resources and features this card supports. For example:

8 Pts,OC3,SMF,APS,RedSlot:2

Pts

The number of ports on the backcard

OC3

Supports SONET OC3 with SMF

Supp (cont.)

APS

Supports APS 1:1

RedSlot:<slot number>

If APS 1+1 supported by the backcard, and configured, this field shows the redundant card's slot number. Values are:

??- If APS 1+1 supported by the backcard, but not configured.

NO- If APS 1+1 is not supported by the backcard.

Example (IGX) UXM

Detailed Card Display for UXM card in slot 9.

dspcd 9

sbolger TN Cisco IGX 8430 9.3.3o May 17 2001 17:43 PST

Detailed Card Display for UXM in slot 9

Status: Active Front Card Supports:
Revision: CD02 Vtrunks, OAMLpbk & TrfcGen, ILMI ver 1,
Serial Number: 284344 Neighbor Discovery, SIW, CGW, CellFwd,
Top Asm Number: 28216402 Hot Standby, Trfc Shaping, IMA,
Backplane Installed ChnStatLvl 1, NumChans = 8000,
Backcard Installed NumRCMP = 8191, VSI ver 2, VSI Ctrlr
Type: OC3
Revision: AD
Serial Number: 258051
Top Asm Number: 28226303
Ports: 4
Line Mode: SMF

Last Command: dspcd 9

Next Command:

Table 4-7 Display Fields for Example (IGX) UXM

Field

Value

Description

BXM Front Card Fields

Status

Displays the status of a card.

Active

Card in use, no failure detected.

Active—F

Card in use, failure detected.

Active—T

Card active, test in progress.

Active—F-T

Card active, minor failure detected, test in progress.

Standby

Card idle, no failure.

Standby—F

Card idle, failure detected.

Standby—T

Card idle, test in progress.

Standby—F-T

Card idle, failure detected, test in progress.

Failed

Card failed.

Down

Card downed by user.

Down—F

Card downed, failure detected.

Down—T

Card downed, failure detected, test in progress.

Mismatch

Mismatch between front card and back card.

Update *

Configuration RAM being updated from active control card.

Locked*

Old software version is being maintained in case it is needed.

Dnlding*

Downloading new system software from the active PCC adjacent node from WAN Manager.

Dnldr*

Looking to adjacent nodes or WAN Manager for either software to load or other software needs you have not specifically requested.

Program

Occurs when new firmware is being burned on the card.

Revision

The firmware/hardware version ID.

Serial Number

The serial number of the card.

Top Asm Number

The card's 800-level part number.

Backplane Installed

Indicates if a backplane is installed. It either shows a Single slot Universal backplane in installed or that no backplane, meaning a backplane other than a single slot Universal backplane.is installed.

Backcard Installed, No Backcard Installed

Shows whether there is a backcard installed.

Front Card Supports

The features that the card's firmware and hardware supports.

Vtrunks

Indicates firmware supports virtual trunks.

OAMLpbk

OAM loopback testing is supported by card firmware.

TrfcGen

Traffic Generation testing is supported by card firmware.

ILMI ver

ILMI version supported by card firmware.

Neighbor Discovery

ILMI neighbor discovery is supported by card firmware.

SIW

Service Interworking supported by card firmware.

CGW

Complex gateway supported by card firmware.

CellFwd

Cell forwarding supported by card firmware.

Hot Standby

Redundant card hot standby supported by card firmware.

Trfc Shaping

Traffic shaping supported by card firmware.

IMA

Inverse Multiplexing for ATM supported by card firmware.

ChnStatLvl

The channel statistics level programmed

NumChans

The total number of channels supported by card.

NumRCMP

The number channels reserved for routing control monitoring and policing.

VSI ver

VSI version level supported by card firmware.

VSI Ctrlr

VSI controller supported by card firmware.

UXM Back Card Fields

Type

The type of backcard: E1 | E1-IMA | T1 | T1-IMA | T3 | E3 | OC3 | Missing.

Revision

The hardware version ID.

Serial Number

The serial number of the card.

Top Asm Number

(TAN) The 800-level part number of the card.

Ports

The number of physical port the backcard supports.

Line Mode

Backcard fiber modes, present only if this is a SONET card. For Example: [SMF | MMF | SMFLR | STM1 | UTP |STP]

SMF

Single mode fiber.

MMF

Multi mode fiber.

SMFLR

SMF long reach.

SNM

Mixed SMF and MMF card.

STM1

STM-1 back card.

XLR

XLR back card.

UTP

OC3 UTP back card.

STP

OC3 STP back card.

Example (BPX)

Displays Neighbor Discovery support under the Front Card Supports field for a BXM card in slot 13, and VC Merge support, designated by V in:

Supp: VT,ChStLv 1,VSI(Lv 3,ITSMV)

dspcd 13

ssw177 TN Cisco BPX 8620 9.3.c3 May 4 2001
23:39 GMT

Detailed Card Display for BXM-155 in slot 13
Status: Active
Revision: FAL Backcard Installed
Serial Number: A66604 Type: LM-BXM
Top Asm Number: 8000309303 Revision: BB
Queue Size: 260090 Serial Number: A84438
Support: 4 Pts, OC3, FST, VcShp Top Asm Number:
Supp: VT,ChStLv 1,VSI(Lv 3,ITSMV) Supp:8 Pts,OC3,MMF,RedSlot:NO
Supp: APS(FW)
Support: LMIv 1,ILMIv 1,NbrDisc,XL
Support: OAMLp, TrfcGen, PPDPolic
#Ch:32768,PG[1]:32736,PG[2]:32736
PG[1]:1,2,PG[2]:3,4,
#Sched_Ch:61440 #Total_Ch:61376
Type: BXME, revision DX

dspcderrs (display card errors)

Displays detailed card failure information resulting from card diagnostics testing at the local node.

This command displays a history of card failures associated with a specified slot. If no argument is specified, a summary is displayed, indicating which slots have failures recorded against them. The command displays the results of the self-tests and background tests as well as the total hardware errors.

To clear the card error counters, use the clrcderrs command. To obtain a hard copy of the report, use the prtcderrs command.

Syntax

dspcderrs [<slot>]

Parameters

Parameter

Description

[<slot>]

Specifies the shelf slot in the local node.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

clrcderrs, prtcderrs

Example

Display card errors on the card in slot 11.

dspcderrs 11

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 17:56 PST

AIT in Slot 11 : 176767 Rev AEF Failures Cleared: Apr. 13 2000 11:25:29 PST
----------------------------------- Records Cleared: Apr. 13 2000 13:14:03 PST
Self Test Threshold Counter: 0 Threshold Limit: 300
Total Pass: 0 Total Fail: 0 Total Abort: 0
First Pass: Last Pass:
First Fail: Last Fail:

Hardware Error Total Events: 0 Threshold Counter: 0
First Event: Last Event:

Last Command: dspcderrs 11

Next Command:

dspcdred (display redundant cards)

The command dspcdred has the same functionality as the command dspyred; therefore, please use the command dspyred. For information about dspyred command usage, refer to dspyred (display Y-cable redundancy).

dspcds (display cards)

Displays the cards in a shelf, front and back, with their type, revision, and status. For front and back card sets, the status field applies to the cards as a set. A "T" opposite a card indicates that it is running a self-test or a background test. An "F" opposite a card indicates that it has failed a test.

If lines or connections have been configured for a slot, but no suitable card is present, the display lists the missing cards at the top of the screen.

If a special backplane is installed or if a card was previously installed, empty slots are identified as "reserved."

For a two-shelf node, the screen initially displays only the upper shelf with a "Continue?" prompt. Typing "y" to the prompt displays the cards in the lower shelf. For an IGX 8410 node, the card information appears in only the left column.

Syntax

dspcds [l]

Parameters

Parameter

Description

l

Directs the system to display status of the cards on just the lower shelf of an IGX 32 node.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

dncd, dspcd, resetcd, upcd

Display Cards Update and Status Display Fields

•Active

Card in use, no failure detected.

•Active—F

Card in use, failure detected.

•Active—T

Card active, test in progress.

•Active—F-T

Card active, minor failure detected, test in progress.

•Standby

Card idle, no failure.

•Standby—F

Card idle, failure detected.

•Standby—T

Card idle, test in progress.

•Standby—F-T

Card idle, failure detected, test in progress.

•Failed

Card failed.

•Down

Card downed by user.

•Down—F

Card downed, failure detected.

•Down—T

Card downed, failure detected, test in progress.

•Mismatch

Mismatch between front card and back card.

•Update *

Configuration RAM being updated from active control card.

•Locked*

Old software version is being maintained in case it is needed.

•Dnlding*

Downloading new system software from the active PCC adjacent node from WAN Manager.

•Dnldr*

Looking to adjacent nodes or WAN Manager for either software to load or other software needs you have not specifically requested.

•Program

Occurs when new firmware is being burned on the card.

In the preceding messages, an asterisk (*) means an additional status designation for BCC or NPM cards. An "F" flag in the card status indicates that a non-terminal failure was detected. Cards with an "F" status are activated only when necessary (for example, when no other card of that type is available). Cards with a "Failed" status are never activated.

The "reserved for" logic in Release 9.2 reserves the slot for a BXM if SONET APS (Automatic Protection Switching) has been configured on the slot.

To support the Hitless Rebuild feature in Release 9.2, after a switchover has occurred and the standby updates are about to begin, the dspcds command shows the standby processor card as missing temporarily. This is a result of the delay in performing the full rebuild on the standby processor, which is necessary as part of the hitless rebuild sequence.

Following any processor card switchover, the new standby rebuilds, preserving the critical databases needed for a hitless rebuild. When database updates can start, the standby rebuilds again doing a normal standby rebuild. If there is a failure on the new active card that causes it to switch back before updates can start, the card taking over performs a hitless rebuild. Under most conditions, the second switchover is not necessary, and a full rebuild is done on the standby processor. As this process begins, the standby card briefly appears to be missing.

Example (URM on IGX)

Display the status of cards in an IGX node with Universal Router Module (URM) cards.

dspcds

sw175 TN Cisco IGX 8420 9.3.q6 Mar. 9 2000 05:21 GMT

Missing Cards: 1 NPM

FrontCard BackCard FrontCard BackCard
Type Rev Type Rev Status Type Rev Type Rev Status
1 NPM FMR Active 9 FRM ESX FRI-T1 AL Standby
2 Empty reserved for NPM 10 URM BA03 2FE P03 Standby
3 Empty 11 URM BA04 2FE P03 Standby-T
4 Empty 12 NTM EKJ Empty Standby
5 UXM CAA Empty Standby 13 Empty
6 URM BA04 Empty Standby 14 Empty
7 UXM BDJ E1-IMA AC Standby-T 15 Empty
8 Empty 16 URM BA03 2FE P03 Standby

Last Command:dspcds
Example (OC-12 on BPX)

Display status of cards on a BPX node. The two-port BME card with OC-12 interface is in slot 11.

dspcds

sw60 TN SuperUser BPX 15 9.3 Apr. 13 2000 11:36 GMT
Missing Cards: 1 BCC

FrontCard BackCard FrontCard BackCard
Type Rev Type Rev Status Type Rev Type Rev Status
1 BNI-T3 CCF T3-3 BE Active 9 BNI-155 BDK MMF-2 CM Standby
2 Empty 10 Empty
3 ASI-T3 BJF T3-2 AA Standby 11 BME-622 K08 11LM-BXM P02AB Active
4 ASI-E3 BMJ E3-2 BE Standby 12 ASI-155 BDK MMF-2 AB Standby
5 BNI-E3 CMF E3-3 EY Standby 13 Empty
6 Empty 14 Empty
7 BCC BWF LMBCC AC Active 15 ASM ACA LMASM AC Active
8 Empty reserved for Card

Last Command: dspcds

dspcftst (display communication fail test pattern)

Displays the test pattern used for the communications fail test.

This test pattern is used to test the controller communication path to a node that does not respond to normal controller traffic. The test pattern defaults to an alternating 8-byte sequence of 00 and FF. Refer to cnfcftst command for other patterns and how to reconfigure this pattern.

Syntax

dspcftst

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

cnfcftst

Example

dspcftst

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 17:57 PST

Comm Fail Test Pattern.

Byte 0: FF Byte 12: 00 Byte 24: FF Byte 36: 00 Byte 48: FF
Byte 1: FF Byte 13: 00 Byte 25: FF Byte 37: 00 Byte 49: FF
Byte 2: FF Byte 14: 00 Byte 26: FF Byte 38: 00 Byte 50: FF
Byte 3: FF Byte 15: 00 Byte 27: FF Byte 39: 00 Byte 51: FF
Byte 4: 00 Byte 16: FF Byte 28: 00 Byte 40: FF Byte 52: 00
Byte 5: 00 Byte 17: FF Byte 29: 00 Byte 41: FF Byte 53: 00
Byte 6: 00 Byte 18: FF Byte 30: 00 Byte 42: FF Byte 54: 00
Byte 7: 00 Byte 19: FF Byte 31: 00 Byte 43: FF Byte 55: 00
Byte 8: FF Byte 20: 00 Byte 32: FF Byte 44: 00 Byte 56: FF
Byte 9: FF Byte 21: 00 Byte 33: FF Byte 45: 00 Byte 57: FF
Byte 10: FF Byte 22: 00 Byte 34: FF Byte 46: 00 Byte 58: FF
Byte 11: FF Byte 23: 00 Byte 35: FF Byte 47: 00 Byte 59: FF

Last Command: dspcftst

Next Command:

dspchan (display channel configuration)

Displays the configuration of IGX voice channels. This is primarily a debug command that allows you to inspect the data structure defining a channel. Parameters for voice and signaling processing on a CVM voice channel are displayed by this command. Table 4-8 lists the displayed CVM parameters. Many of these parameters are also displayed elsewhere.

Syntax

dspchan <channel>

Parameters

Parameter

Description

<channel>

Specifies the voice channel connection to display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

IGX

No

Related Commands

cnfcdpparm

CVM Voice Channel Parameters

Table 4-8 Parameters Configurable on a CVM Voice Channel

Parameter

Parameter

Parameter

Parameter

VC Index

Dial Type

TX Sig

iec converge.

In Loss

TX A-D bit

RX Sig

Hi Pass F

Out Loss

RX A-D bit

Clr Chn

es loss

Chan Type

Signaling

Sig Rate

Fmodem

Sig. Intg

Echo supr

PLY MSBhx

ADV

Xmt. dlay

Wink Puls

PLY LSBhx

Cond ID

Smpl dlay

TX A-D Qual

In use

iec erl lvl

Bk noise

RX A-D Qual

DPU

iec Hregs.

DSI smple

TX Code

iec cancel

iec tone dsbl

Chan Util

RX Code

iec nlp

adpcm flag

Onhk A-D

Example (IGX)

dspchan 7.1

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:06 PST

Channel Data Base for CDP card 7 chan. 000000 at address 30BF29EC

VC Index -1 Onhk C 4
In Loss 0 Onhk D 4
Out Loss 0 Dial Type 0
Chan Type 1 TX A bit 1
Sig. Intg 96 TX B bit 1
Xmt. dlay 5 TX C bit 0
Smpl dlay 1 TX D bit 1
Bk noise 67 RX A bit 1
DSI smple 168 RX B bit 1
Chan Util 40 RX C bit 0
Onhk A 3 RX D bit 1
Onhk B 3 Signaling TSP MODE

This Command: dspchan 7.1

Continue?

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:07 PST

Channel Data Base for CDP card 7 chan. 000000 at address 30BF29EC

TX CODE 3 iec cancel 0
RX CODE 3 iec nlp 1
TX SIG 0 iec converg. 1
RX SIG 0 iec erl lvl 1
CLR CHN 0 iec Hregs. 1
SIG RATE 0 iec tone dsbl 1
PLY MSBhx 1 adpcm flag 0
PLY LSBhx 90
In use 0
DPU -

Last Command: dspchan 7.1

Next Command:
Example (BPX)

dspchan 11.1

sw53 TN Cisco BPX 8620 9.3.m0 Dec. 12 2000 12:16 GMT

Channel Data Base for 11.1 on BXM at address 0x325C48DA

pcnfg_nm_chans 0 apc_metro 0
pcnfg_bandwidth 353208 pcnfg_basis 0
pcnfg_frst_indx 0 apc_t1_basis 0
pcnfg_chan_cnt 5 apc_nni_port 0
pcnfg_loop 0
pcnfg_state 1
pcnfg_cnfg 1
pcnfg_hipri 0
pcnfg_com_fail 0
pcnfg_ptp_conn 0

Last Command: dspchan 11.1

dspchcnf (display channel configuration)

Displays configuration details for voice, data, ATM, or Frame Relay channels.

Voice Channels

When you specify a voice channel with dspchcnf, the display shows configuration details for all channels on the specified circuit line starting with the specified channel:

•Percent of channel utilization

•Adaptive voice enable status

•Fax enable status

•Gain in both directions (in decibels)

•Dial Type

•Interface type (such as 2w E&M)

•Onhook and conditioning specifications

Data Channels

The data cards that support this command are the HDM, LDM, UVM, and CVM/CVP cards on the IGX node.

For data connections on the specified card and starting with the specified channel, the dspchcnf command displays configuration details for all channels on the specified data card (CDP, SDP, or LDP) starting with the specified channel:

•Maximum EIA update rate

•Percentage of channel utilization

•DFM pattern length

•DFM status (enabled or disabled)

•Idle code suppression (enabled or disabled)

•PreAge (in microseconds)

Frame Relay Channels

The display includes configuration details for all channels on the specified FRP port starting with the specified channel. If you specify a Frame Relay port only with no DLCI, the display includes configuration details for all channels on the Frame Relay port specified. The display also indicates either Cisco parameters or standard Frame Relay parameters where appropriate.

When you specify a Frame Relay channel with dspchcnf, the display shows:

•Minimum Information Rate

•VC Queue Buffer Size or Bc

•Peak Information Rate or Be

•Maximum Credits

•ECN Queue Buffer Size

•Quiescent Information Rate

•ForeSight enabled or not

•Percentage Utilization

Syntax

dspchcnf <start_channel>

Parameters

Parameter

Description

<start_channel>

Specifies the channel to begin the display.

The format for a CDP or CVM is slot.channel.

The format for a UVM is slot.line.channel.

The format for an IMA-compliant line is slot.line.start_channel—end_channel.

The format for Frame Relay is slot.port.DLCI. The DLCI parameter is optional.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

cnfdch, cnfchadv, cnfchdfm, cnfchdl, cnfcheia, cnfchgn, cnfchtp, cnfchutl, cnffrcon, cnfchpri

Example (UVM on IGX)

Display the channel configuration of line 7.1.1-24. The card in slot 7 is a UVM.

dpchcnf 7.1.1

sw109 VT cisco IGX 8420 9.3 Apr. 13 2000 18:59 PST

% Adaptive Gain (dB) Dial Interface OnHk Cond
Channels Util Voice Fax In Out Type Type A B C D Crit
7.1.1-24 40 Enabled Disabled 0 0 Inband 2W E&M 0 X - - a
7.2.1-24 40 Enabled Disabled 0 0 Inband Unconfig ? ? - - a

Last Command: dspchcnf 7.1.1

Next Command:
Example (CVM on IGX)

Show channel configuration of line 13. The card in slot 13 is a CVM.

dspchcnf 13.1

sw150 TN Cisco IGX 8420 9.3.2T Dec. 19 2000 23:32 PST

% Adaptive Gain (dB) Dial Interface OnHk Cond
Channels Util Voice Fax In Out Type Type A B C D Crit
13.1-24 60 Enabled - 0 0 Inband Unconfig ? ? - - a

Last Command: dspchcnf 13.1
Example (Data Channels on IGX)

Show data channels starting at 13.1.

dspchcnf 13.1

sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 12:15 GMT

Maximum EIA % DFM Pattern DFM Idle Code PreAge
Channels Update Rate Util Length Status Suppr (usec)
13.1-8 2 100 8 Enabled - 0

Last Command: dspchcnf 13.1
Example (Frame Relay on IGX)

Show data channels starting at 13.1.

dspchcnf 9.1

sw108 VT Cisco IGX 8420 9.3.q2 Dec. 20 2000 12:29 GMT

Frame Relay Channel Configuration Port: 9.1

From MIR CIR VCQ Dep PIR Cmax ECNQ Th QIR FST %Utl
9.1.918 59.5 59.5 61440 59.5 10 21504 59.5 n 100
9.1.919 19.2 19.2 61440 19.2 10 21504 19.2 n 100
9.1.920 19.2 19.2 61440 19.2 10 21504 19.2 n 100

Last Command: dspchcnf 9.1

dspchdlcnf (display channel dial type configurations)

Displays dial type configurations for all channels on a circuit line:

Syntax

dspchdlcnf <start_channel>

Parameters

Parameter

Description

<start_channel>

Specifies the channel at which the display begins.

For a CDP or CVM, the format is slot.channel.

For a UVM, the format is slot.line.channel.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

cnfchdl

Display Fields

Channel Type

Dial Type

Description

All

Dial Type

Inband, pulse, or user-configured.

User-configured

signaling delay

The signaling delay on a channel.
Range: 12 ms-96 ms

minimum wink

The minimum wink on the channel. Minimum wink does not apply to a CDP or CVM channel.
Range: 3 ms-765 ms

interdigit time

The interdigit times on a channel. Interdigit time does not apply to a CDP or CVM channel.
Range: 3 ms-765 ms

playout delay

The playout delay on a channel. Range: 12 ms-96 ms

Example

Display the dial type configuration for all channels beginning with 14.1.

dspchdlcnf 14.1

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 09:45 PST

Channels Type Sig Delay Min Wink IntDigit Time Playout Delay
14.1-24 Inband 12 141 300 -

Last Command: dspchdlcnf 14.1

Next Command:

dspchec (display channel echo canceller configuration)

Displays the integrated echo canceller (IEC) parameters for one or more voice channels. The dspchec command does not apply to CAS or data channels. The specified channels must be on a CDP, CVM, or UVM. See Table 4-4 for what dspchec displays.

Table 4-9 Information in the dspchec Display

Category

Possible Value

Echo cancellation

Enabled or Disabled

Echo Return Loss (.1 dBs)

High/low (loss is in units are 0.1 dBs)

Tone Disabler

Enabled or Disabled

Convergence

Enabled or Disabled

Nonlinear Processing

Enabled or Disabled

Voice Template

USA, other

Syntax

dspchec <channel>

Parameters

Parameter

Description

<channel>

Specifies the channel or channels to display.

For a CVM or CDP, the format is slot.channel(s).

For a UVM, the format is slot.line.channel(s).

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

cnfchec

Display Fields

Category

Possible Value

Echo cancellation

Enabled or Disabled

Echo Return Loss (.1 dBs)

High/low (loss is in units are 0.1 dBs)

Tone Disabler

Enabled or Disabled

Convergence

Enabled or Disabled

Nonlinear Processing

Enabled or Disabled

Voice Template

USA, other

Example

Display the echo canceller configuration for channel 7.1.

dspchec 7.1

pubsipx1 TN cisco IGX 8420 9.3 Apr. 13 2000 06:10 PDT

Echo Echo Return Tone Conver- Non-Linear Voice
Channels Cancel Loss (.1 dBs) Disabler gence Processing Tmplt
7.1 Enabled High 60 Enabled Enabled Enabled USA
7.2-31 Disabled High 60 Enabled Enabled Enabled USA

Last Command: dspchec 7.1

Next Command:

dspchstatcnf (display statistics enabled for a channel)

Displays the configuration of enabled statistics for a channel to help debug problems with statistics gathering.

Use the cnfcdparm command to configure the channel statistics level (level 1, 2, or 3) on BXM and UXM cards.

The command output is a list of the connection statistics as set by the cnfchstats command, by Cisco WAN Manager, or by IGX features.

The Owner column identifies who or what set the statistic. If the Owner column shows "Automatic," the node's features set the statistic. If the node name appears under Owner, Cisco WAN Manager set the statistic. If the user name appears under Owner, the cnfchstats command executed from the command line interface set the statistic.

Syntax

dspchstatcnf <channel>

Parameters

Parameter

Description

<channel>

Specifies the channel whose statistics configuration you want to display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

IGX

Yes

Related Commands

cnfchstats, dspchstathist, cnfcdparm

Example (FR channel)

dspchstatcnf 5.1.100.100

pubsbpx1 VT SuperUser BPX 15 9.3 Apr. 13 2000 23:13 GMT
Statistics Enabled on Channel 5.1.100.100

Statistic Samples Interval Size Peaks Owner
------------------------------------ ------- -------- ---- ----- ----------
41) AAL5 Cells Discarded for VCQ Full 1 30 4 NONE TFTP
42) Average VCq Depth in Cells 1 30 4 NONE TFTP
43) Cells lost due to Rsrc Overflow 1 30 4 NONE TFTP
44) Cells discarded for SBIN full 1 30 4 NONE TFTP
45) Cells Transmitted with EFCI(Port) 1 30 4 NONE TFTP
46) Cells Transmitted(Port) 1 30 4 NONE TFTP
47) Cells Received from Network 1 30 4 NONE TFTP
48) Cells discarded for QBIN full 1 30 4 NONE TFTP
49) Cells discarded when QBIN>CLP 1 30 4 NONE TFTP
50) Cells Transmitted with CLP (Port) 1 30 4 NONE TFTP
51) BCM Cells Received(Port) 1 30 4 NONE TFTP

This Command: dspchstatcnf 5.1.100.100

Continue?

dspchstathist (display statistics history for a channel)

Displays a history of statistics configured as enabled for a selected channel. This command is intended for debugging problems with statistics gathering. It displays the data for the number of samples specified in the configuration of the channel statistic. You select a statistic from the list in the dspchstathist display. Specify only an enabled statistic.

You can use the cnfdparm command to configure the channel statistics level on the BXM and UXM cards. Make a note of the statistics types enabled, the collection interval, and owner; you will need this information to obtain the statistics history. Use cnfchstats to enable a statistic if it is not already enabled.

Syntax

dspchstathist <channel> <stat> <owner> <interval>

Parameters

Parameter

Description

<channel>

Specifies the channel.

<stat>

Specifies the number of the statistic to view.

<owner>

Specifies the source of the selected statistics's original configuration (the choices are "auto," "user," and "tftp"). You might need to enter "AUTO" in all capital letters.

<interval>

Specifies the time period of statistics collection to display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX

Yes

Related Commands

cnfchstats, cnfchlevel, dspchstatcnf

Example

A display for channel 6.1 packets transmitted (1 second interval) history.
dspchstathist 6.1 7 1 AUTO

gamma TRM SuperUser Rev: 9.3 Apr. 13 2000 13:53 PDT

Packets Transmitted on Channel 6.1
Interval: 1 Minute(s), Data Size: 4 Byte(s), NO Peaks, Owner: Automatic

0 - 1699
-1 - 1698
-2 - 1698
-3 - 1699
-4 - 1698
-5 - 1698
-6 - 1698
-7 - 1699
-8 - 1697
-9 - 1699

Last Command: dspchstathist 6.1 7 1 AUTO

Next Command:

dspchstats (display summary statistics for a channel)

Displays summary statistics. This command is intended for debugging problems with statistics gathering. It displays the data for the last five occurrences of the channel statistic.

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 examples show these statistics categories:

•From the port (something coming into a port, typically from an external device/box)

•To the network (something going out of the switch; typically trunks)

•Discarded (received from the attached device but not transmitted to the network)

•From the network (received in; typically, into the trunk)

•To the port (transmitted out of the port, to an external device or cloud)

•Discarded (received from the network but not transmitted to the attached device)

Syntax

dspchstats <channel> [interval]

Parameters

Parameter

Description

<channel>

Specifies the channel defined according to the channel type.

ATM format: slot.port.vpi.vci

Frame Relay format: slot.port.DLCI

Voice or data format: slot.port

<interval>

Specifies the refresh interval for displaying data.
Range:1-60 seconds
Default: 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.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX

Yes

Related Commands

cnfchstats, dspchstatcnf

Display Fields (Frame Relay Channel Statistics)

Table 4-10 displays 35 statistics are available for each Frame Relay PVC channel. Note that the statistic field name listed may be slightly different from the field name on the dspchstats screen.

Table 4-10 Frame Relay Channel Statistics in IGX

Statistic

Description

Frames Received (Ingress)

This statistic provides a count of the number of frames received from the attached equipment. This statistic is incremented even when the received frame is invalid or discarded for any reason. (See possible reasons below.)

Receive Frames Discarded (Ingress)

This statistic provides a count of the number of frames received from the attached equipment that were discarded before being sent into the network or aborted after some portion had been already sent into the network. Possible reasons for discard are:

•Invalid CRC—that is, the CRC calculated by the IGX does not match the CRC provided by the attached equipment in the last two octets of the frame. (Frames received with an invalid CRC are also included in the port Receive Frame CRCs Errors statistic.)

•Invalid Frame Length—that is, the length of the received frame, including the header and frame check sequence (FCS, or CRC) octets, is either too short (less than five octets) or too long (more than 4510 octets). (Frames received with an invalid frame length are also included in the port Illegal Length Receive Frames statistic.)

•Invalid Alignment—that is, the length of the received frame is not an integral number of octets. (Frames received with an invalid alignment are also included in the port Receive Frame Alignment Errors statistic.)

Frame received with DE = 1 and the PVC's ingress queue is filled at least to the DE threshold and the global DE feature is enabled (using the cnfsysparm command). Frames discarded for this reason are specifically counted in the PVC DE Frames Dropped statistic (below).

•PVC failed (due to endpoint hardware failure/absence or inability to find a route through the network) or downed (intentionally out of service due to operator action). Frames discarded for this reason are specifically counted in the PVC Rx Frames Discarded - Deroute/Down statistic (below).

•PVC ingress queue full. The queue may fill (and overflow) due to sustained transmission above the PVC's MIR or as a result of MUXBUS oversubscription. Frames discarded for this reason are specifically counted in the PVC Rx Frames Discarded - VC Q Overflow statistic (below).

This statistic is a subset of the PVC Frames Received statistic.

Frames Transmitted (Egress)

This statistic provides a count of the number of frames transmitted to the attached equipment.

Transmit Frames Discarded

This statistic provides a count of the number of frames that were not able to be transmitted to the attached equipment. Possible reasons for discard are:

Port Transmit Queue Overflow—that is, the frame traversed the network successfully but encountered a full egress port queue. Frames discarded for this reason are specifically counted in the PVC Tx Frames Discarded - Q Overflow statistic (below) and the port Tx Frames Discarded - Queue Overflow statistic (above).

Incomplete Frame at Egress—that is, no end-of-frame (EOF) packet received for any reason. The most common cause is a CRC error detected at ingress; that is, the beginning of the frame traversed the network successfully but the end of the frame was never sent because a CRC error was detected at the end of the frame at ingress. Frames discarded due to a missing EOF packet (because of ingress CRC error or EOF packets dropped in a trunk) are specifically counted in the PVC Tx Frames Discarded - Ingress CRC statistic (below). Ingress CRC errors are also counted in the ingress port Receive Frame CRC Errors statistic (above).

Incorrect Frame Length—that is, the expected frame length (recorded in the end-of-frame packet) is different from the total payload of all the packets that arrive. Such a frame length error could be caused by:

•one or more packets being missing due to discard(s) on a trunk, or

•a transmission bit error on the frame length field in the end-of-frame packet. Frames discarded for this reason are counted in the PVC Tx Frames Discarded - Trunk Discard statistic (below).

Invalid Frame Length—that is, the frame is longer than 4510 octets long. This could occur if the end-of-frame packet from one frame and the start-of-frame packet of the next frame are both missing due to discards on a trunk, resulting in a concatenated frame. Frames discarded for this reason are counted in the PVC Tx Frames Discarded - Trunk Discard statistic (below).

Frame CRC error—that is, the calculated CRC at the destination does not match the original frame's CRC (contained within the received packets). This situation can occur as a result of transmission bit errors on payload bits on one or more packets of the frame. Frames discarded for this reason are specifically counted in the PVC Tx Frames Discarded - Trunk Discard statistic (below).

Packets Received

This statistic provides a count of the number of packets received across the network. These are the packets that are used to recreate all the frames which are counted in the PVC Frames Transmitted and Transmit Frames Discarded statistics (above).

Receive Packets Discarded

This statistic provides a count of the number of packets received across the network but whose payload was ultimately discarded because they contained portions of the frames which are discarded and counted in the Transmit Frames Discarded statistic (above).

Packets Transmitted

This statistic provides a count of the number of packets submitted to the network. These packets are all the packets that were generated from the non-errored received frames (Frames Received minus Receive Frames Discarded) as well as some of the packets from the errored-received frames (Receive Frames Discarded). Some packets from errored receive frames may be submitted to the network because the IGX does not wait to receive the entire frame before starting to packetize the frame and send it through the network. Consequently, if an error is detected at the end of the frame (for example, CRC error, alignment error, length error), the frame is aborted only after some packets may have been sent.

Bytes Received

This statistic provides a count of the number of octets in the frames counted in the Frames Received statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

Receive Bytes Discarded

This statistic provides a count of the number of octets in the frames counted in the Receive Frames Discarded statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

Bytes Transmitted

This statistic provides a count of the number of octets in the frames counted in the Frames Transmitted statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

Transmit Bytes Discarded

This statistic provides a count of the number of octets in the frames counted in the Transmit Frames Discarded statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

Seconds in Service

This statistic provides a count of the number of seconds during which the PVC was in service. The PVC is considered in service any time the PVC is not failed (due to endpoint hardware failure/absence or inability to find a route through the network) or downed (intentionally out of service due to operator action).

Frames Transmitted with FECN

This statistic provides a count of the number of frames transmitted to the attached equipment with the Forward Explicit Congestion Notification (FECN) bit set, regardless of where in the network the congestion was experienced.

This statistic is a subset of the PVC Frames Transmitted statistic.

This statistic is also a subset of the port Frames Transmitted with FECN statistic.

Frames Transmitted with BECN

This statistic provides a count of the number of frames transmitted to the attached equipment with the Backward Explicit Congestion Notification (BECN) bit set, regardless of where in the network the congestion was experienced.

This statistic is a subset of the PVC Frames Transmitted statistic.

This statistic is also a subset of the port Frames Transmitted with BECN statistic.

Minutes Congested

This statistic provides a count of the number of minutes during which 50 percent or more of the frames transmitted to the attached equipment have the Forward Explicit Congestion Notification (FECN) bit set.

The threshold (default: 50 percent) that defines congestion is configurable (by a SuperUser) using the cnffstparm command.

DE Frames Received

This statistic provides a count of the number of frames received from the attached equipment with the Discard Eligible (DE) bit already set.

This statistic is a subset of the PVC Frames Received statistic

DE Frames Transmitted

This statistic provides a count of the number of frames transmitted to the attached equipment with the Discard Eligible (DE) bit set, regardless of why or where the DE bit was set.

If IDE-to-DE mapping is enabled on the port, this statistic includes those frames that have their DE bit set by the IDE-to-DE mapping function.

This statistic is a subset of the PVC Frames Transmitted statistic.

DE Frames Dropped

This statistic provides a count of the number of frames received from the attached device which were discarded because the frame's DE bit is set and the PVC's ingress buffer has reached the DE threshold. The DE threshold is configured as part of the port configuration (cnfport command).

This statistic is a subset of the PVC Frames Received statistic.

This statistic is a subset of the PVC Receive Frames Discarded statistic.

This statistic is a subset of the PVC DE Frames Received statistic.

DE Bytes Received

This statistic provides a count of the number of octets in the frames counted in the DE Frames Received statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

This statistic is a subset of the PVC Bytes Received statistic.

Frames Received in Excess of CIR

This statistic provides a count of the number of frames received from the attached equipment which exceed the configured Committed Information Rate (CIR) for the PVC. Whether a frame is considered "in excess of CIR" depends on whether the DE feature is enabled (using the cnfsysparm command).

•If the DE feature is enabled, only frames with DE=0 are counted against Bc. Thus, this statistic only counts those frames which exceeded Bc and had DE=0. (If a frame is received with DE=1, only the DE Frames Received statistic is incremented and the frame is not counted against Bc.)

•If the DE feature is not enabled, all frames are counted against Bc. If the frame exceeds Bc, it is included in this statistic.

This statistic is a subset of the PVC Frames Received statistic

Bytes Received in Excess of CIR

This statistic provides a count of the number of octets in the frames counted in the Frames Received in Excess of CIR statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

This statistic is a subset of the PVC Bytes Received statistic.

Frames Transmitted in Excess of CIR

This statistic provides a count of the number of frames transmitted to the attached equipment which:

•were determined at ingress to exceed the configured Committed Information Rate (CIR) for the PVC, or

•were received at ingress with DE=1 and the DE feature is enabled, or

•were received at ingress when the VC_Q exceeded the configured DE threshold and the DE feature is enabled.

All of these conditions have in common that the packets carrying these frames all have CLP=1. It is actually the status of the CLP bits in the arriving packets that is monitored at egress.

This statistic is a subset of the PVC Frames Transmitted statistic.

Bytes Transmitted in Excess of CIR

This statistic provides a count of the number of octets in the frames counted in the Frames Transmitted in Excess of CIR statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

This statistic is a subset of the PVC Bytes Transmitted statistic.

Rx Frames Discarded—Deroute/Down

This statistic provides a count of the number of frames received from the attached equipment which are discarded because the PVC is routed (due to endpoint hardware failure/absence or inability to find a route through the network) or "downed" (intentionally out of service due to operator action).

This statistic is a subset of the PVC Frames Received statistic.

Rx Bytes Discarded—Deroute/Down

This statistic provides a count of the number of octets in the frames counted in the Rx Frames Discarded - Deroute/Down statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

This statistic is a subset of the PVC Bytes Received statistic.

This statistic is also a subset of the PVC Receive Bytes Discarded statistic.

Rx Frames Discarded—VC Q Overflow

This statistic provides a count of the number of frames received from the attached equipment which are discarded because the PVC ingress buffer (VC Q) is full.

This statistic is a subset of the PVC Frames Received statistic.

Rx Bytes Discarded—VC Q Overflow

This statistic provides a count of the number of octets in the frames counted in the Rx Frames Discarded - VC Q Overflow statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

This statistic is a subset of the PVC Bytes Received statistic.

This statistic is also a subset of the PVC Receive Bytes Discarded statistic.

Tx Frames Discarded—Q Overflow

This statistic provides a count of the number of frames which were not able to be transmitted to the attached equipment because the port's egress buffer is full. The port's egress buffer may fill (and overflow) due to oversubscription.

This statistic is a subset of the PVC Transmit Frames Discarded statistic.

This statistic is a subset of the port Tx Frames Discarded - Q Overflow statistic.

Tx Bytes Discarded—Q Overflow

This statistic provides a count of the number of octets in the frames counted in the Tx Frames Discarded - Q Overflow statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

This statistic is a subset of the PVC Transmit Bytes Discarded statistic.

This statistic is a subset of the port Tx Bytes Discarded - Q Overflow statistic.

Tx Frames Discarded—Ingress CRC

This statistic provides a count of the number of frames which were not able to be transmitted to the attached equipment because the frame is incomplete. Specifically, this statistic is incremented any time an end-of-frame (EOF) packet is missing. In other words:

•a start-of-frame packet is followed by another start-of-frame packet, or start-of-frame packet is followed by an encapsulated-frame packet, or

•a middle-of-frame packet is followed by a start-of-frame packet, or

•middle-of-frame packet is followed by an encapsulated-frame packet

The most likely cause of any of these conditions is a CRC error detected at ingress causing the end of the frame (including at least the end-of-frame packet and maybe one or more middle-of-frame packets) to not be sent.

A less likely cause for the missing EOF packet is that the packet was dropped due to a transmission bit error in the packet header that is detected by a trunk along the PVC's path. Such conditions are included in this statistic.

This statistic is a subset of the PVC Transmit Frames Discarded statistic.

Tx Bytes Discarded—Ingress CRC

This statistic provides a count of the number of octets in the frames counted in the Tx Bytes Discarded - Ingress CRC statistic (above). The octets counted include the Frame Relay header octets as well as any octets which arrived successfully.

This statistic is a subset of the PVC Transmit Bytes Discarded statistic.

Tx Frames Discarded—Trunk Discard

This statistic provides a count of the number of frames that were not able to transmitted to the attached equipment because the frame: has an incorrect length, that is, the expected frame length (recorded in the end-of-frame packet) is different than the total payload of all the packets which arrive. Such a frame length error could be caused by:

•one or more packets being missing due to discard(s) on a trunk, or

•a transmission bit error on the frame length field in the end-of-frame packet.

•has an invalid length, that is, the frame is longer than 4510 octets long. This could occur if the end-of-frame packet from one frame and the start-of-frame packet of the next frame are both missing due to discards on a trunk, resulting in a concatenated frame.

In any of the cases above, a packet could be discarded on a network trunk either due to extreme trunk congestion or a detected transmission bit error on the packet header.

This statistic is a subset of the PVC Transmit Frames Discarded statistic.

Tx Bytes Discarded—Trunk Discard

This statistic provides a count of the number of octets in the frames counted in the Tx Bytes Discarded - Trunk Discard statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

This statistic is a subset of the PVC Transmit Bytes Discarded statistic.

Tx Frames During Ingress LMI Failure

This statistic provides a count of the number of frames that were transmitted to the attached equipment while the signaling protocol on the local port was failed (that is, when the port was in a Port Communication Failure state).

This statistic is a subset of the PVC Frames Transmitted statistic

Tx Bytes During Ingress LMI Failure

This statistic provides a count of the number of octets in the frames counted in the Tx Frames During Ingress LMI Failure statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets.

Table 4-11 At Ingress (before FRP Firmware Release FDS/FES)

DE Feature
Enabled

DE = 1

> CIR

VC_Q > DE Threshold

Action

No

Don't care

No

Don't care

Send

No

Don't care

Yes

Don't care

Set CLP=E1 in all packets

Yes

No

No

No

Send

Yes

No

No

Yes

Set CLP=E1 in all packets

Yes

No

Yes

No

Set CLP=E1 in all packets

Yes

No

Yes

Yes

Set CLP=E1 in all packets
Set IDE=1 in last packet

Yes

Yes

Don't care

No

Set CLP=E1 in all packets

Yes

Yes

Don't care

Yes

Discard frame

Table 4-12 At Ingress (FRP Firmware Release FDS/FES and later)

DE Feature
Enabled

DE=1

> CIR

VC_Q > DE Thresh

Action

No

Don't care

No

Don't care

Send

No

Don't care

Yes

Don't care

Set CLP=1 in all packets

Don't care

No

No

No

Send

Don't care

No

No

Yes

Set CLP=1 in all packets

Don't care

No

Yes

No

Set CLP=1 in all packets

Don't care

No

Yes

Yes

Set CLP=1 in all packets
Set IDE=1 in last packet

Yes

Yes

Don't care

No

Set CLP=1 in all packets

Yes

Yes

Don't care

Yes

Discard frame

Table 4-13 At Ingress (FRP firmware Release FDV/FEV and later)

DE Feature
Enabled

DE=1

> CIR

Action

No

Don't care

No

Send

No

Don't care

Yes

Set CLP=1 in all packets

Don't care

No

No

Send

Don't care

No

Yes

Set CLP=1 in all packets
Set IDE=1 in last packet

Yes

Yes

Don't care

Set CLP=1 in all packets

Table 4-14 At Egress (DE bit setting)

IDE = 1

IDE = 1

IDE to DE Mapping Enabled

Action

Yes

Don't care

Don't care

DE=1 (No change to DE bit) --> Tx_Q

No

No

Don't care

DE=1 (No change to DE bit) --> Tx_Q

No

Yes

No

DE=1 (No change to DE bit) --> Tx_Q

No

Yes

Yes

DE=1 (Change DE bit) --> Tx_Q

Table 4-15 At Egress (Transmit queue behavior)

DE Feature
Enabled

DE=1

Tx_Q > DE Threshold

Action

No

Don't care

Don't care

If space available, put frame into Tx_Q

Yes

No

Don't care

If space available, put frame into Tx_Q

Yes

Yes

No

If space available, put frame into Tx_Q

Yes

Yes

Yes

Discard frame

Example (IGX)

Display the channel statistics for connection 14.1.1.

The system response shows these statistics categories:

•From the port (something coming into a port, typically from an external device/box)

•To the network (something going out of the switch; typically trunks)

•Discarded (received from the attached device but not transmitted to the network)

•From the network (received in; typically, into the trunk)

•To the port (transmitted out of the port, to an external device or cloud)

•Discarded (received from the network but not transmitted to the attached device)

dspchstats 14.1.1

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 13:07 PST

Channel Statistics: 14.1.1 Cleared: Jan. 15 2001 09:06 (|)
MIR: 64/64 kbps Collection Time: 3 day(s) 04:09:55 Corrupted: NO
Frames Avg Size Avg Util Packets Avg
(bytes) (fps) (%) (pps)
From Port: 0 0 0 0
To Network: 0 0 0 0 0 0
Discarded: 0 0 0 0
From Network: 0 0 0 0 0 0
To Port: 0 0 0 0
Discarded: 0 0 0 0 0 0
ECN Stats: Avg Rx VC Q: 0 ForeSight RTD --
Min-Pk bytes rcvd: -- FECN Frames: 0 FECN Ratio (%) 0
Minutes Congested: -- BECN Frames: 0 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: dspchstats 14.1.1

Hit DEL key to quit:
Example (BPX)

Display the channel statistics for connection 4.1.50.1.

dspchstats 4.1.50.1

night TN SuperUser BPX 15 9.3 Apr. 13 2000 02:46 GMT

Channel Statistics for 4.1.50.1 Cleared: Apr. 13 2000 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:
Example (IGX)

Display statistics for connection 13.1.100 with a 10-second interval between screen updates.

dspchstats 13.1.100 10

sw142 TN SuperUser IGX 16 9.3 Apr. 13 2000 14:38 PDT

Channel Statistics: 13.1.100 Cleared: Apr. 13 2000 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:
Example (UXM on IGX)

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

dspchstats 9.2.1.100

sw199 TN SuperUser IGX 16 9.3 Apr. 13 2000 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
Example (BPX)

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

dspchstats 2.1.1.1 1

sw57 TRM StrataCom BPX 8620 9.3 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
Example (IGX)

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

dspchstats 10.1.205.101

m2a TN StrataCom IGX 8420 9.3 Apr. 13 2000 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

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

Table 4-16 provides some statistics information for SAR on the BXM card. The switch software collects miscellaneous statistics regarding the Monarch SAR (Segmentation, Assembly, and Reassembly). Note that the object name typically maps to the screen field name on the dspchstats screen.

Table 4-16 SAR Statistics 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 CommBus 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.

dspchuse (display channel usage)

Displays a summary of the channel distribution in a given slot of a BPX or IGX switch. It shows the distribution of channels between the following:

•Automatic Routing Management PVCs

•Networking channels

•VSI management channels

•Channels allocated to the VSI slave

•Channels used for F4-F5 mapping

If you do not enter a slot number, a summary of channels allocated for all the BXM or UXM cards that are active will be displayed. You are then prompted to enter a slot number.

Syntax

dspchuse <slot>

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

No

No

BPX, IGX

Yes

Yes

Yes

No

Display Fields

Parameter

Description

Max

Maximum number of channels supported on the card.

Used

Number of channels currently used; this includes all types of channels: networking channels, PVCs, VSI master-slave VCs, and channels allocated to VSI partitions

Avail

Number or channels still available for use.

Netw

Number of network channels used. For each trunk interface (feeder trunk, physical trunk, or virtual trunk) that is up, 270 channels are reserved for networking. For an enhanced UXM card, 270 channels are allocated for networking when the first trunk is upped. For all the subsequent trunks, networking channels are allocated from the RCMP reserve.

PVC cnfg

Number of channels configured for PVCs (AR connections).

F4-F5

Number of channels used to support F4-F5 mapping.

VSI mgmt

Number of channels used for VSI master-slave VCs.

VSI cnfg

VSI channels reserved for use by the slave to set up connections requested via the VSI interface.

PVC used

Channels currently used by Automatic Routing Management connections.

vsi min

VSI min channels configured for a partition via the cnfrsrc command.

vsi max

VSI max channels configured for a partition via the cnfrsrc command.

Example (BPX)

Display channel management summary for slot 11.

dspchuse 13

BPX02 TN Cisco BPX 8620 9.3.3 0 Aug. 13 2001 12:43 PDT

Channel Management Summary for Slot 13

max used avail netw pvc cnfg f4-f5 vsi mgmt vsi cnf

card 13: 61376 61277 99 542 332 0 3 60400
port grp 1: 32736 30066 2670 0 66 0 0 30000
port grp 2: 32736 31209 1527 542 266 0 1 30400

pvc cnfg pvc used nw used f4-f5 vsi mgmt vsi min vsi max

phy if 1: 20 0 0 0 0 --- ---
phy port: 20 0 0 0
phy if 2: 26 0 0 0 0 --- ---
phy port: 26 0 0 0
part 3: 0 30000
Last Command: dspchuse 13
Continue? y

BPX02 TN Cisco BPX 8620 9.3.3 0 Aug. 13 2001 12:46 PDT

Channel Management Summary for Slot 13

pvc cnfg pvc used nw used f4-f5 vsi mgmt vsi min vsi max

phy if 3: 0 0 0 0 0 --- ---
phy if 4: 20 1 0 0 0 --- ---
phy port: 20 1 0 0
phy if 5: 10 1 0 0 0 --- ---
phy port: 10 1 0 0
phy if 6: 256 0 271 0 0 --- ---
vtrk 1: 256 0 ---
phy if 7: 0 0 0 0 0 --- ---
phy if 8: 0 0 271 0 1 --- ---
phy trk: 0 0 ---
part 3: 0 30400

Last Command: dspchuse 13

dspclksrcs (display network clock sources)

Displays all clock sources for the network. The display for unreachable or failed clock sources flashes on and off.

Syntax

dspclksrcs

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnfclksrc, dspcurclk

Example

Display the network clock sources.

dspclksrcs

bootzilla TRM YourID: Numba 1 IGX 8430 9.3 Apr. 13 2000 15:32 MST

Network Clock Sources

Primary
bootzilla CLN 15

Secondary
None

Tertiary
None

Last Command: dspclksrcs

Next Command:

dspclnerrs (display circuit line errors)

Displays the accumulated error count since the last time errors were reset. Table 4-17 lists the types of circuit line errors. The clrclnerrs command clears the error counters for circuit lines.

The dsplnerrs and dspclnerrs commands are the same.

Table 4-17 Errors Displayed by the dsplnerrs Command

Type

Explanation

Bipolar errors

Number of times that two consecutive pulses had the same polarity (applies to AMI coding only).

Frame slips

Number of times a frame was discarded to re-establish synchronization.

Out of frames

Number of times a loss-of-frame synchronism was detected on this circuit line.

Loss of signal

Number of times the signal level at the circuit line input went below the minimum acceptable level.

Frame bit errors

Number of times the frame bit failed to alternate (frame error).

CRC errors

Number of times the generated CRC character did not match the received CRC character (applies only if CRC checking is enabled).

Out of MFrames

Number of times a multiframe synch error was detected (E1 lines only).

AIS - 16

Number of times the Alarm Information Signal (Blue signal) was received.

Syntax

dspclnerrs [slot | slot.line]

Parameters

Parameter

Description

slot or
slot.line

For most circuit lines, the slot number is the line number. To use this optional parameter on a UFM, enter one of the line numbers. With no optional parameter specification, a summary screen for all line errors appears.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

clrclnerrs, prtclnerrs

Example

Display a summary of all circuit line errors.

dspclnerrs

sw151 TN SuperUser IGX 16 9.3 Apr. 13 2000 12:45 GMT

Total Errors

Code Frame Out of Loss of Frame CRC Out of
CLN Errors Slips Frames Signal BitErrs Errors MFrames AIS-16
9 0 - 0 0 - 0 - -
5.1 0 - 0 0 - 0 - -
12 0 0 0 0 - 0 - -
5.2 0 - 0 0 - 0 - -

Last Command: dspclnerrs

Next Command:
Example

Display the circuit line errors for line 5.1 on the UFM card in slot 5.

dspclnerrs 5.1

sw151 TN SuperUser IGX 16 9.3 Apr. 13 2000 12:38 GMT

Circuit Line 5.1 Status:Major - Out of Frm (RED) Clrd: 06/20/96 12:08:38
Type Count ETS Status Type Count ETS Status
Bipolar Err 0 0 Loss of Sig (RED) 0 -
Frame Slips - - AIS (BLU) 0 -
Out of Frms 0 0 Out of Frms (RED) 2 -
Loss of Sig 0 0 Frm Err Rate(RED) - -
Frame BitErrs - - AIS-16 (RED) - -
CRC Err 0 0 Rmt Oof (YEL) 0 -
AIS-16 - - Out of MFms (RED) -
Out of MFms - - Rmt Oom (YEL) - -
Local CGA (RED) - -
Remote CGA (YEL) - -

Last Command: dspclnerrs 5.1

Next Command:

SW MAJOR ALAR

dspclnstatcnf (display circuit line statistics configuration)

Displays statistics configured for a selected circuit line as enabled by the cnflnstats (or alias cnfclnstats) command, by Cisco WAN Manager, or by IGX features. (Note that the dsplnstatcnf command is an older alias for dspclnstatcnf.)

The Owner column identifies who or what set the statistic. If the Owner column shows "Automatic," the node's features set the statistic. If the node name appears under Owner, Cisco WAN Manager set the statistic. If the user name appears under Owner, the cnfchstats command executed from the command line interface set the statistic.

Syntax

dspclnstatcnf <line>

Parameters

Parameter

Description

<line>

Specifies the circuit line in the format slot or slot.line. If the card has only one line, you can enter just the slot.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX

Yes

Related Commands

cnfclnstats

Example (IGX)

dspclnstatcnf 4.1

sw180 VT Cisco IGX 8420 9.3.p7 Dec. 12 2000 12:57 GMT

Statistics Enabled on Circuit Line 4.1

Statistic Samples Interval Size Peaks Owner
----------------------------------- ------- -------- ---- ----- ----------
1) Bipolar Violations 60 0 4 NONE AUTO
3) Out of Frames 60 0 4 NONE AUTO
4) Losses of Signal 60 0 4 NONE AUTO
5) Frames Bit Errors 60 0 4 NONE AUTO
6) CRC Errors 60 0 4 NONE AUTO
29) Line Code Violations 60 0 4 NONE AUTO
32) Line Parity Errors 60 0 4 NONE AUTO
35) Path Parity Errors 60 0 4 NONE AUTO
41) BIP-8 Code Violations 60 0 4 NONE AUTO
98) Frame Sync Errors 60 0 4 NONE AUTO
Last Command: dspclnstatcnf 4.1
1

dspclnstathist (display statistics history for a circuit line)

Displays a history of statistics enabled for a circuit line, including the last five occurrences of the circuit line statistic. When you first enter dspclnstathist, you select the circuit line statistic from the displayed list.

Use the dspclnstatcnf to display the statistics enabled for the selected channel. Use cnfclnstats to enable a statistic.

Syntax

dspclnstathist <line> <statistic number> <interval> <owner>

Parameters

Parameter

Description

<line>

Specifies the circuit line in the format slot.line. If the card set supports only one line, you can enter just the slot number.

<statistic number>

Specifies the type of statistic to enable/disable.

<interval>

Specifies the time interval of each sample. Range: 1-255 minutes

<owner>

Specifies the source of the configuration ("auto," "user," or "tftp"). You might have to enter owner "AUTO" in all capital letters.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

IGX

Yes

Related Commands

cnfclnstats, dspclnstatcnf

Example

A display for T1 circuit line 14 bipolar violations (60-second interval) history.

dspclnstathist 14 1 60 AUTO

gamma TRM SuperUser Rev: 9.3 Apr. 13 2000 14:00 PDT

Bipolar Violations on Circuit Line 14
Interval: 60 Minute(s), Data Size: 4 Byte(s), 10 S Peaks, Owner: Automatic

0 - 0(0)
-1 - 0(0)
-2 - 0(0)
-3 - 0(0)
-4 - 0(0)
Last Command: dspclnstathist 14 1 60 AUTO
Next Command:

dspcls (display connection class)

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

dspcls - Display ATM or Frame Relay Connection Classes
Cannot be included in Jobs.
Usage: dspcls atm | fr

Syntax

dspcls <atm | fr>

Parameters

Parameter

Description

<atm | fr>

Specifies either ATM or Frame Relay

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

BPX, IGX

No

Related Commands

addcon, cnfcls, dspcon, dspcons

Example (IGX)

Display the parameters for ATM on IGX.

dspcls atm

-----------------------------------SCREEN 1------------------------------------
sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 13:01 GMT

ATM Connection Classes
Class: 1 Type: ABRSTD
PCR(0+1) % Util MCR CDVT(0+1) AAL5 FBTC VSVD
96000/96000 100/100 96000/96000 10000/10000 n n

Policing
4

Description: "Default ABR 96000"

This Command: dspcls atm

Continue? y

-----------------------------------SCREEN 2------------------------------------
sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 13:06 GMT

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 VC Qdepth CLP Hi CLP Lo
1000/1000 3 1280/1280 80/80 35/35

Description: "Default nrt-VBR 1000 "

This Command: dspcls atm

Continue? y

-----------------------------------SCREEN 3------------------------------------
sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 13:06 GMT

ATM Connection Classes
Class: 3 Type: rt-VBR
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
4000/4000 100/100 10000/10000 n 4000/4000

MBS Policing VC Qdepth CLP Hi CLP Lo
1000/1000 3 1280/1280 80/80 35/35

Description: "Default rt-VBR 4000 "

This Command: dspcls atm

Continue? y

-----------------------------------SCREEN 4------------------------------------
sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 13:03 GMT

ATM Connection Classes
Class: 4 Type: nrt-VBR
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
8000/8000 100/100 10000/10000 n 8000/8000

MBS Policing VC Qdepth CLP Hi CLP Lo
1000/1000 3 1280/1280 80/80 35/35

Description: "Default VBR nrt-8000 "

This Command: dspcls atm

Continue? y

-----------------------------------SCREEN 5------------------------------------
sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 13:04 GMT

ATM Connection Classes
Class: 5 Type: nrt-VBR
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
16000/16000 100/100 10000/10000 n 16000/16000

MBS Policing VC Qdepth CLP Hi CLP Lo
1000/1000 3 1280/1280 80/80 35/35

Description: "Default nrt-VBR 16000 "

This Command: dspcls atm

Continue? y

-----------------------------------SCREEN 6------------------------------------
sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 13:07 GMT

ATM Connection Classes
Class: 6 Type: nrt-VBR
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
32000/32000 100/100 10000/10000 n 32000/32000

MBS Policing VC Qdepth CLP Hi CLP Lo
1000/1000 3 1280/1280 80/80 35/35

Description: "Default nrt-VBR 32000 "

This Command: dspcls atm

Continue? y

-----------------------------------SCREEN 7------------------------------------
sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 13:08 GMT

ATM Connection Classes
Class: 7 Type: nrt-VBR
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
96000/96000 100/100 10000/10000 n 96000/96000

MBS Policing VC Qdepth CLP Hi CLP Lo
1000/1000 3 1280/1280 80/80 35/35

Description: "Default nrt-VBR 96000 "

This Command: dspcls atm

Continue? y

-----------------------------------SCREEN 8------------------------------------
sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 13:09 GMT

ATM Connection Classes
Class: 8 Type: CBR
PCR(0+1) % Util CDVT(0+1) Policing VC Qdepth CLP Hi
500/500 100/100 10000/10000 4 160/160 80/80

CLP Lo
35/35

Description: "Default CBR 500 "

This Command: dspcls atm

Continue? y

-----------------------------------SCREEN 9------------------------------------
sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 13:09 GMT

ATM Connection Classes
Class: 9 Type: CBR
PCR(0+1) % Util CDVT(0+1) Policing VC Qdepth CLP Hi
1000/1000 100/100 10000/10000 4 160/160 80/80

CLP Lo
35/35

Description: "Default CBR 1000 "

This Command: dspcls atm

Continue? y

-----------------------------------SCREEN 10-----------------------------------
sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 13:09 GMT

ATM Connection Classes
Class: 10 Type: CBR
PCR(0+1) % Util CDVT(0+1) Policing VC Qdepth CLP Hi
4000/4000 100/100 10000/10000 4 160/160 80/80

CLP Lo
35/35

Description: "Default CBR 4000"

Last Command: dspcls atm

dspcnf (display configuration save/restore status)

Displays the status for the configuration save and restore processes on all nodes in the network.

The display lists the various nodes, the backup ID name of the saved configuration, the time and date saved, and the Cisco WAN Manager terminal it is saved on.

If the status displays "Reserved for Firmware," a firmware image is maintained in memory after it is loaded. Use the getfwrev 0.0 command to clear the firmware image.

If a configuration image is displayed, clear the old configuration image by using savecnf clear or loadcnf clear.

If an IGX node status displays "Reserved for Router Configuration," an IOS configuration file for the URM embedded router is stored in NPM memory. Starting with Release 9.3.30, the Universal Router Module (URM) Remote Router Configuration feature enables the transfer of an IOS configuration file from a TFTP server to the NPM. Use the clrrtrcnf command to clear the IOS configuration file from NPM memory. For additional information on the URM Remote Router Configuration feature, see the cnfrtr command description.

Caution Do not use clrcnf without first discussing the action with TAC.

Syntax

dspcnf

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

savecnf, loadcnf, runcnf

Fields Displayed

Field

Description

nodename

Specifies the name of the node that had its configuration saved. The wildcard option, specified by an asterisk (*), is used in place of nodename to indicate all nodes are to have their configuration saved.

This also can be a CWM nodename, specifies the name of the node that has the CWM attached.

backup ID

Specifies the name of the configuration file to be saved. The name must be 1-8 alphanumeric characters, and the first character must be alphabetic. Configuration names are case-sensitive.

When the directory and files are on CWM, the backup is on /usr/users/svplus directory. The directory containing the configuration files will be named <backup_id>_Cfgdir.

Revision

The firmware/hardware version ID.

Date/Time (GMT)

The timestamp of the action listed under "status."

Status

Current status of the configuration save and restore process. In 9.3.30 and higher, the IP address of the CWM or the TFTP server is displayed for proprietary or TFTP download, respectively. For releases earlier than 9.3.30, the SV+ node nbame is displayed. Another possible status is that the NPM RAM buffer is occupied with IOS config file.

Example

dspcnf

bpx1 TN Cisco BPX 8620 9.3.h1 Mar. 9 2001 15:16 GMT

Node Backup ID Revision Date/Time (GMT) Status
-------- --------- -------- ----------------- ---------------------------------
bpx1 cisco111 9.3.h1 03/08/01 23:32:16 Save on 172.29.10.72 complete
sw200 Reserved for firmware image
sw76 cisco111 9.3.j3 03/08/01 23:32:16 Save on 172.29.10.72 complete
magneto cisco111 9.3.h1 03/08/01 23:32:16 Save on 172.29.10.72 complete

Last Command: dspcnf
Example

dspcnf

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:21 PST

Node Backup ID Revision Date/Time (GMT) Status
-------- --------- -------- ----------------- ---------------------------------
sw78 mark 9.2.00 02/22/97 16:36:26 Unreachable
sw81 mark 9.2.00 02/22/97 16:36:26 Unreachable
sw84 mark 9.2.00 02/22/97 16:36:26 Save on Cisco WAN Manager at sw78 complete
sw79 mark 9.2.00 02/22/97 16:36:26 Save on Cisco WAN Manager at sw78 complete
sw86 mark 9.2.00 02/22/97 16:36:26 Unreachable
sw83 mark 9.2.00 02/22/97 16:36:26 Save on Cisco WAN Manager at sw78 complete

Last Command: dspcnf

dspcntrstats (display counter status statistics)

Displays counter status statistics for both BPX and IGX (such as Connection, Port, Trunk, and so on) for a given statistics object.

Syntax

dspcntrstats <stat_object_type><oid>

Parameters

Parameter

Description

<stat_object_type>

Specifies the object type for statistics display.

<oid>

Object ID. Identifies the object for statistics display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

Yes

BPX, IGX

Yes

Related Commands

cnfcntrstats

Example (BPX)

Display Counter Statistics for Virtual Port 6 on card 3 in slot 4 of the BPX.

dspcntrstats 4 3.6

Counter Stats for Port 3.6

RTC STATS Value RTC STATS Value
Inv LMI PDU Rx : 0 Inv LMI len Rx : 0
Unk LMI PDU Rx : 0 Inv LMI IE Rx : 0
Inv Trans IDs : 0 Rx Clp 0 Cells : 0
Rx Clp 0 Dscd : 0 Rx Clp 1 Dscd : 0
Tx Clp 0 Cells : 0 Tx OAM Cells : 0
Rx RM Count : 0 Tx RM Count : 0
Lst Unk VpiVci : 0 Qbin 0 CTXL : 0
Tx Q0 CDscd : 0 Egr QBIN0 CRx : 0
Qbin 1 CTXL : 0 Tx Q1 CDscd : 0
Egr QBIN1 CRx : 0 Qbin 2 CTXL : 0
Tx Q2 CDscd : 0 Egr QBIN2 CRx : 0
Qbin 3 CTXL : 0 Tx Q3 CDscd : 0

This Command: dspcntrstats 4 3.6

Next/previous page? (+/-/DEL key to quit):
NODENAME TRM Cisco BPX 8620 9.3.10 Date/Time Not Set

Counter Stats for Port 3.6

RTC STATS Value RTC STATS Value
Egr QBIN3 CRx : 0 Qbin 9 CTXL : 0
Tx Q9 CDscd : 0 Egr QBIN9 CRx : 0
Qbin 10 CTXL : 0 Tx Q10 CDscd : 0
Egr QBIN10 CRx : 0 Qbin 11 CTXL : 0
Tx Q11 CDscd : 0 Egr QBIN11 CRx : 0
Qbin 12 CTXL : 0 Tx Q12 CDscd : 0
Egr QBIN12 CRx : 0 Qbin 13 CTXL : 0
Tx Q13 CDscd : 0 Egr QBIN13 CRx : 0
Qbin 14 CTXL : 0 Tx Q14 CDscd : 0
Egr QBIN14 CRx : 0 Qbin 15 CTXL : 0
Tx Q15 CDscd : 0 Egr QBIN15 CRx : 0

This Command: dspcntrstats 4 3.6

Previous page? (-/DEL key to quit):
Example (IGX)

Display Counter Statistics for Trunk 5.2 of the IGX.

dspcntrstats 5.2

Enter Object Type:

neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:48 GMT

Counter Stats for Trunk 5.2 (ltrk = 1)

RTC STATS Value RTC STATS Value
Txntscdscd : 0 Txhpcdscd : 0
Txvcdscd : 0 Txtscdscd : 0
Txbdacdscd : 0 Txbdbcdscd : 0
Txcbrcdscd : 0 Txabrcdscd : 0
Txvbrcdscd : 0 VI: Cells transmitted : 0
VI: Cells received : 0 TxQ10cdscd : 0
TxQ11cdscd : 0 TxQ12cdscd : 0
TxQ13cdscd : 0 TxQ14cdscd : 0
TxQ15cdscd : 0

Example (IGX)

Display Counter Statistics for Port 5.1 on card 4 of the IGX.

dspcntrstats 4.5.1

neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:48 GMT

Counter Stats for Port 5.1

RTC STATS Value RTC STATS Value
PORT: Unknwn VPI/VCI cnt: 0 VI: Cells rcvd w/CLP=1 : 0
VI: OAM cells received : 0 VI: Cells tx w/CLP=1 : 0
VI: Cells transmitted : 0 VI: Cells received : 0
ILMI: Get Req PDUs rcvd : 0 ILMI: GetNxt Req PDUS rx: 0
ILMI: GetNxt Req PDUS xmt:0 ILMI: Set Req PDUs rcvd : 0
ILMI: Trap PDUs rcvd : 0 ILMI: Get Rsp PDUs rcvd : 0
ILMI: Get Req PDUs xmt : 0 ILMI: Get Rsp PDUs xmt : 0
ILMI: Trap PDUs xmt : 0 ILMI: Unknwn PDUs rcvd : 0
LMI: Status messages xmt: 0 LMI: Updt Status msgs xmt:0
LMI: Status Ack msgs xmt: 0 LMI: Status Enq msgs rcvd:0
LMI: Status Enq msgs xmt: 0 LMI: Status msgs rcvd : 0
LMI: Updt Status msg rcvd:0 LMI: Status Ack msg rcvd: 0

This Command: dspcntrstats 4 5.1

Next page? (+/DEL key to quit):
Example (IGX)

Display Counter Statistics for Physical Line 5.2 of the IGX.

dspcntrstats 5.2

neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:49 GMT

Counter Stats for Physical Line 5.2 (l_physln = 1)

RTC STATS Value RTC STATS Value
Bpv : 0 Oof : 1
Los : 1 Fer : 0
CRC : 0 Lcv : 262140
Pcvl : 2 Pcvp : 2
Bcv : 3 Total Cells Tx to line : 0
Total Cells Rx from line: 0 FSyncErr : 1

This Command: dspcntrstats 5.2

Hit DEL key to quit:

dspcon (display connection)

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

•The channel numbers for both the local and remote ends of the connection.

•The routing restriction.

•The class of service (CoS) of the connection (see cnfcos description for details).

•The connection route listing the end nodes and any intermediate nodes.

•The preferred route for the connection (if configured).

•If cost-based routing is configured, displays maximum and current costs for a connection route.

•The status of the cards associated with the connection.

•Any Y-cable conflicts (LDI, CDP for example).

•The type of the compression, if applicable (VAD, ADPCM, LDCELP, CACELP for voice; repetitive pattern suppression (RPS) applies to data connections).

•The type or data rate of the connection.

•The connection priority (low or high).

•The status of the front and back cards and access devices associated with the connection.

•If one endpoint is a CDP or CVM, the compression status (VAD on or off, ADPCM on or off).

•The bandwidth parameters for the connection.

•The ForeSight enable status.

•The percent of utilization.

•The connection descriptor (if configured).

•The circuit round-trip delay (RTD) if ForeSight is enabled.

The status that may be displayed includes:

OK

Connection good

FAILED

Connection failed

Syntax

dspcon <channel>

Parameters

Parameter

Description

<channel>

Specifies the channel for the connection details display. The command displays connection information for one channel at a time.

The format for channel on a CDP or CVM is slot.channel.

The format for a channel on a UVM is slot.line.channel.

slot.port.connection_ID.
Range for connection_ID : 1-252

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

Yes

IGX

No

Related Commands

addcon, cnfcos, cnfpref, cnfrtcost, dspcons

Example

Display connection information for voice channel 10.1.1.

dspcon 10.1.1

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 12:26 PST

Conn: 10.1.1 igxr02 20.1.1 p Status:OK

Owner: LOCAL Restriction: NONE COS: 0 Compression: NONE
Path: igxr03 19.1--12.3igxr02
Pref: Not Configured

igxr03 UVM: OK igxr02 UVM: OK
Line 10.1 : OK OFFHK Line 20.1 : OK

Last Command: dspcon 10.1.1

dspcon (display data connections)

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

•The channel numbers for both the local and remote ends of the connection

•The node names at both ends of the connection

•The routing restriction

•The class of service (CoS) of the connection

•The connection route listing the end nodes and any intermediate nodes

•The preferred route for the connection (if configured)

•If cost-based AutoRoute is configured, displays maximum and current costs for a connection route

•The status of the cards associated with the connection

•Any Y-cable conflicts

•The compression status (VAD on or off, ADPCM on or off, DFM on or off, Frame Relay
compression on or off)

•The connection descriptor (if configured)

The status that may be displayed includes:

OK

Connection OK

FAILED

Connection failed

Syntax

dspcon <channel>

Parameters

Parameter

Description

channel

Specifies the channel. The command displays connection information for one channel at a time. The format for channel specification is slot.channel.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

cnfchec, cnfrtcost

Example

Display information for data channel 6.4.

dspcon 6.4

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 12:36 PST

Conn: 6.4 igxr02 18.4 128 7/8 Status:OK

Owner: REMOTE Restriction: NONE COS: 0 Compression: DFM
Path: igxr03 19.2--12.4igxr02
Pref: Not Configured

igxr03 HDM: OK igxr02 HDM: OK
SDI: OK SDI: OK
Clock: OK Clock: OK

Last Command: dspcon 6.4

dspcon (display Frame Relay connections)

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

•The channel number at both the local and remote ends of the connection

•The node name at both ends of the connection

•The type or data rate of the connection

•The routing restriction

•The class of service (CoS) of the connection

•The connection route, which lists the end nodes and any intermediate nodes

•The preferred route for the connection (if configured)

•If cost-based AutoRoute is configured, displays maximum and current costs for a connection route

•The status of the cards associated with the connection

•Any Y-cable conflicts (LDI, CDP for example)

•The compression status (VAD on or off, ADPCM on or off, DFM on or off, Frame Relay compression on or off)

•The connection bandwidth parameter values for Frame Relay

•The circuit round trip delay (RTD) if ForeSight is enabled

A failure that affects the connection flashes on the screen. For Frame Relay NNI ports, the NNI value indicates the A-bit value was received over the NNI from the remote network. The possible status messages are:

•OK

Connection OK.

•FAILED

Connection failed.

•MISSING

DLCI was deleted in other network at NNI. A previous status report indicated a valid DLCI was present but an updated report did not.

•UNUSED

Indicates the UNI port does not support reporting of NNI A-bit status.

Syntax

dspcon <slot.port.DLCI>

Parameters

Parameter

Description

channel

Specifies the Frame Relay channel in the format slot.port.DLCI. The dspcon command displays information for one connection at a time.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

addcon, cnfcos, cnfpref, cnfrtcost, dspcons

Example

Display connection information for Frame Relay channel 14.1.1.

dspcon 14.1.1

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 13:09 PST

Conn: 14.1.1 igxr02 27.1.1 fr Status:OK
MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR
64/64 64/64 65535/65535 64/64 100/100 65535/65535 64/64

Owner: LOCAL Restriction: NONE COS: 0 FST: n % Util: 25/25
Pri: L Test-RTD: 0 msec
Path: igxr03 19.2--12.4igxr02
Pref: Not Configured

igxr03 UFM: OK igxr02 UFM: OK
Line 14.1 : OK Line 27.1 : OK

Last Command: dspcon 14.1.1

dspcon (display ATM connections)

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

•The channel numbers for both the local and remote ends of the connection, including, for an Extended PVC (XPVC) that spans over a hybrid AutoRoute (AR)-PNNI, or AR-PNNI-AR, network, connection details for an XPVC segment linking the Automatic Routing Management and PNNI endpoints (the connection segment status). The node names at both ends of the connection.

•The node names at both ends of the connection.

•The type or data rate of the connection.

•The routing restriction.

•Trunk cell routing restriction.

•The Class of Service (CoS) of the connection.

•The connection route, listing the end nodes and any intermediate nodes.

•The maximum and current costs for a connection route when cost-based Automatic Routing Management is configured.

•The preferred route for the connection (if configured).

•The status of the cards associated with the connection.

•Any Y-cable conflicts.

•The compression status.

•The connection bandwidth parameter values.

•The connection/type descriptor (if configured). (If the connection is a VP tunnelling DAX connection, the type is displayed as cbrvp, abrstvp, abrfsvp, and so on.)

•The circuit round-trip delay (if ForeSight is enabled).

•Any failures that affect the connection flash on the screen.

For Frame Relay NNI ports, the NNI value indicates the A-bit value received across the NNI from the remote network. The status that may be displayed includes:

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:

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

•Indicates connection failures at feeder endpoints.

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

With Release 9.3.20, dspcon supports the Universal Router Module (URM) introduced on the IGX 8400. The URM provides IOS-based voice support and basic routing functions. It consists of an embedded UXM with one internal ATM port and an embedded IOS-based router. The URM embedded UXM has no physical line interfaces. Therefore, dspcon does not display line status information for the URM endpoints. For example, if a connection has one endpoint on the URM internal ATM port and the other on a UXM port, dspcon displays the line status information for the UXM endpoint but not for the URM endpoint. For the URM end point, dspcon displays port status information instead. This information includes port communication failure and IOS unavailable (if the router connected to the internal port is not able to provide services because IOS is not up and running).

Syntax

dspcon <channel>

Parameters

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

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

addcon, cnfcon, cnfpref, cnfrtcost

Example (VBR on BPX)

Display connection information for channel 11.1.180.1000 (an nrt-VBR connection).

dspcon 11.1.180.1000

------------------------------------SCREEN 1-----------------------------------
sw53 VT Cisco BPX 8620 9.3.2o Nov. 30 2000 11:23 GMT

Conn: 11.1.180.1000 sw180 15.1.53.1000 nrt-vbr Status:OK
PCR(0+1) % Util CDVT(0+1) FBTC SCR MBS PLC
50/50 100/100 250000/250000 n 50/50 1000/1000 3
Owner: LOCAL Restriction: NONE COS: 0
TestRTD: 0 msec Trunk Cell Routing Restrict: Y
Path: sw53 11.2-- 4.4sw108 4.2-- 5.1sw180
Pref: Not Configured

sw53 BXM : OK sw180 URM : OK
Line 11.1 : OK Port 15.1 : OK
OAM Cell RX: Clear NNI : OK
NNI : OK

This Command: dspcon 11.1.180.1000

Continue? y

------------------------------------SCREEN 2-----------------------------------
sw53 VT Cisco BPX 8620 9.3.2o Nov. 30 2000 11:24 GMT

Conn: 11.1.180.1000 sw180 15.1.53.1000 nrt-vbr Status:OK
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
50/50 100/100 250000/250000 n 50/50

MBS Policing VC Qdepth CLP Hi CLP Lo
1000/1000 3 1280/1280 80/80 35/35

Trunk Cell Routing Restrict: Y

Last Command: dspcon 11.1.180.1000
Example (CBR on BPX)

Display connection information for channel 11.1.108.61 (CBR).

dspcon 11.1.108.61

------------------------------------SCREEN 1-----------------------------------
sw53 VT Cisco BPX 8620 9.3.2o Nov. 30 2000 11:29 GMT

Conn: 11.1.108.61 sw108 6.1.53.111 cbr Status:OK
PCR(0+1) % Util CDVT(0+1) Policing
50/50 100/100 10000/10000 4/4
Owner: LOCAL Restriction: NONE COS: 0
TestRTD: 0 msec Trunk Cell Routing Restrict: Y
Path: sw53 11.2-- 4.4sw108
Pref: Not Configured

sw53 BXM : OK sw108 URM : OK
Line 11.1 : OK Port 6.1 : OK
OAM Cell RX: Clear NNI : OK
NNI : OK

This Command: DSPCON 11.1.108.61

Continue? y

------------------------------------SCREEN 2-----------------------------------
sw53 VT Cisco BPX 8620 9.3.2o Nov. 30 2000 11:29 GMT

Conn: 11.1.108.61 sw108 6.1.53.111 cbr Status:OK
PCR(0+1) % Util CDVT(0+1) Policing VC Qdepth CLP Hi
50/50 100/100 10000/10000 4 160/160 80/80

CLP Lo
35/35

Trunk Cell Routing Restrict: Y

Last Command: DSPCON 11.1.108.61
Example (ABR on BPX)

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

dspcon 12.1.1.100

ca20 LAN SuperUser BPX 15 9.3 Apr. 13 2000 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
Example (ABRSTD on BPX)

Display connection information for channel 11.1.0.1023 (an ABRSTD connection).

dspcon 12.1.1.100

------------------------------------SCREEN 1-----------------------------------
sw53 VT Cisco BPX 8620 9.3.2o Nov. 30 2000 11:32 GMT

Conn: 11.1.0.1023 sw180 5.3.0.1023 abrstd Status:OK
PCR(0+1) % Util MCR CDVT(0+1) FBTC FST VSVD FCES
50/50 100/100 50/50 250000/250000 y n n n
Owner: LOCAL Restriction: NONE COS: 0
TestRTD: 0 msec Trunk Cell Routing Restrict: Y
Path: sw53 11.2-- 4.4sw108 4.2-- 5.1sw180
Pref: Not Configured

sw53 BXM : OK sw180 UXM : OK
Line 11.1 : OK Line 5.3 : OK
OAM Cell RX: Clear NNI : OK
NNI : OK

This Command: dspcon 11.1.0.1023

Continue? y

------------------------------------SCREEN 2-----------------------------------
sw53 VT Cisco BPX 8620 9.3.2o Nov. 30 2000 11:32 GMT

Conn: 11.1.0.1023 sw180 5.3.0.1023 abrstd Status:OK
PCR(0+1) % Util MCR CDVT(0+1) AAL5 FBTC VSVD
50/50 100/100 50/50 250000/250000 y n

Policing
4

Trunk Cell Routing Restrict: Y

Last Command: dspcon 11.1.0.1023

Example (ATFST on BPX)

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

dspcon 4.1.2.1

sw53 TN SuperUser BPX 8620 9.3 Apr. 13 2000 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
Example (CBR on IGX)

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

dspcon 12.1.1.*

sw224 TRM IGX 8420 9.3 Apr. 13 2000 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.*
Example (URM on IGX)

Display connection information for channel 11.1.1.100 on the internal ATM port in the Universal Router Module (URM).

dspcon 11.1.1.100

sw190 TRM Cisco IGX 8420 9.3.e9 Oct. 6 2000 05:31 GMT

Conn: 11.1.1.100 sw190 10.1.1.100 nrt-vbr Status:OK
PCR(0+1) % Util CDVT(0+1) FBTC SCR MBS PLC
1000/1000 100/100 10000/10000 n 1000/1000 1000/1000 3

Pri:L Test-RTD:0 msec
Path: Route information not applicable for local connections

sw190 URM: OK sw190 URM: OK
Port 11.1 :OK Port 10.1 :OK
OAM Cell RX:Clear NNI: OK
NNI: OK

This Command:dspcon 11.1.1.100

Continue?

--------- Screen 2 ----------
sw190 TRM Cisco IGX 8420 9.3.e9 Oct. 6 2000 05:31 GMT

Conn: 11.1.1.100 sw190 10.1.1.100 nrt-vbr Status:OK

PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
1000/1000 100/100 10000/10000 n 1000/1000

MBS Policing VC Qdepth CLP Hi CLP Lo
1000/1000 3 1280/1280 80/80 35/35

Last Command:dspcon 11.1.1.100

dspconcnf (display connection configuration)

Displays information for a connection's configuration:

•The channel numbers for both the local and remote ends of the connection

•The node names at both ends of the connection

•The preferred route for the connection, if configured

•The bandwidth parameter values for ATM connections

•VC queue depth

•The connection type, if configured

•Other values (see examples)

The rt-VBR and nrt-VBR connection service types are displayed separately

Syntax

dspconcnf <channel>

Parameters

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

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX

No

Related Commands

addcon, dspcon, dspcons, delcon

Example (ABRSTD on BPX)

Display the configuration for 11.1.108.60 (for ABRSTD).

dspconcnf 11.1.108.60

sw53 VT Cisco BPX 8620 9.3.2o Nov. 30 2000 10:57 GMT

Conn: 11.1.108.60 sw108 6.1.53.110 abrstd Status:OK
PCR(0+1) % Util MCR CDVT(0+1) AAL5 FBTC VSVD
50/50 100/100 50/50 250000/250000 y n

Policing
4

Trunk Cell Routing Restrict: Y

Last Command: dspconcnf 11.1.108.60
Example (RT-VBR on BPX)

Display the configuration for 11.1.108.60 (for RT-VBR).

dspconcnf 11.1.108.112

sw53 VT Cisco BPX 8620 9.3.2o Nov. 30 2000 11:02 GMT

Conn: 11.1.108.112 sw108 6.1.53.112 rt-vbr Status:OK
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
50/50 100/100 250000/250000 n 50/50

MBS Policing VC Qdepth CLP Hi CLP Lo
1000/1000 3 1280/1280 80/80 35/35

Trunk Cell Routing Restrict: Y

Last Command: dspconcnf 11.1.108.112

dspcond (display conditioning criteria)

Displays the signaling bit patterns from the specified template. Refer to the description of the cnfcond command for the purpose of the conditioning template.

Syntax

dspcond <identifier>

Parameters

Parameter

Description

<identifier>

Specifies the identifier of the template.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

cnfchtp, cnfcond

Example

Display the conditioning template identified as "a."

dspcond a

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 09:56 PST

Conditioning criterion a:

Data Pattern
01010100 - E1
01111111 - T1

Signalling Pattern
A 0(40)/1
B 1
C 1
D 1

Last Command: dspcond a

Next Command:

dspcons (display connections)

Displays information about the connections on an IGX or BPX node. The Display Fields table 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. Entering the command with no parameters displays all connections.

All parameters are displayed even though some parameters are meaningless on a BPX.

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

You can 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.

Syntax

dspcons [start_channel] [nodename] [state] [type]
[-g | +d | -v | -d | -f | -abit | -fabit | -atfr | -siw | -fail | -down | -tun | -siw ]]

Parameters

Parameter

Description

start_channel

Specifies the channel to begin the display. Specify start channel in one of these formats:

Frame Relay channel (IGX): slot.port.DLCI

Frame Relay Group Connection (IGX): remote node.group_name

ATM channel (IGX, BPX): slot.port.vpi.vci

CDP or CVM channel (IGX): slot.channel

UVM channel (IGX): slot.line.channel

If you do not specify a starting channel, the display begins at the first connection.

nodename

Specifies that only connections to this remote node from the local note be displayed. If no nodename is designated, connections from the local node to all other nodes are displayed.

-a

-f

Display Frame Relay connection only.

-v

Display only voice connections.

-d

Display only data connections and do so in Kbps.

-atfr

Display Frame Relay to ATM interworking connections (also displays atfr with ForeSight).

-abit

Show status of the A-bit. In Release 9.3.30 and higher, use the dspcons -abit command to display the connection status of an XPVC segment linking the AR and PNNI endpoints. The local and remote A-bit status values are interpreted as follows:

•Status "OK" (A-bit equals 1): The connection exists in the PNNI network. The operational status of the connection at the PNNI network may be active, failed, or downed.

•Status "FAILED" (A-bit equals 0): The connection is deleted from the PNNI network.

Note Only the local AR node information is displayed for XPVC segments. The Remote Node Name and Remote Channel fields remain blank. You must use the CWM or MGX CLI to display the remote PNNI node connection details.

-fabit

Show only connections with failed A-bits.

-fail

Show only failed connections.

-down

Show only downed connections.

-tun

Shows VP tunneled connections (IGX only).

-siw

Shows service interworking connections (IGX only).

-oam

Displays only connections that have failed the OAM loopback Test (IGX only).

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

dspcon, addcon

Owner: from 3rd table

ABRSTD=OFF: from 3rd table

Display Fields

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 possible connections states are:

State

Description

OK

Routed, A-bit = 1

Down

Downed.

Failed

Unrouted, but trying; A-bit = 0

Unused

The UNI port does not support reporting of NNI A-bit status.

OAM

Connections that have failed the OAM Loopback test, but are otherwise OK.

OAM-F

Indicates OAM Loopback failure

Type

The type of connection. For example, this can be Frame Relay, Frame Relay with interworking, voice, data, and so on.

Only __

If one parameter preempts another, this heading appears with the accepted parameter type. To name two examples:
If the parameter is -d for data, this heading either "Only d"
If the parameter is -fail for failed connections only, this heading becomes "Only fail"

Code

The encoding used for data connections (7/8 = data byte is 7 bits of user data plus a "1" in the last bit position, 8/8 = data byte is 8 bits of user data, 8/8I = data byte is 8 bits of inverted user data).

Route Avoid

The type of lines to avoid when routing (satellite lines, terrestrial lines, lines with zero code suppression).

Compression

The type of compression applied to the connection (PCM, PCM and VAD, ADPCM, VAD and ADPCM for voice connections), (DFM for data connections).

COS

The Class of Service.

Local/Remote A-bit

A bit status on the local and remote nodes if -abit option selected. Note that -abit is incompatible with -v, -d, and +d.

Loopback

This is not a heading but rather the standard loopback symbols indicating the presence of a test loop.

Owner

The end of the connection in control of rerouting.

ABRSTD=OFF

The policing value for the connection.

Example (BPX)

Display a summary of all connections on a BPX.

dspcons

sw53 VT Cisco BPX 8620 9.3.2o Nov. 30 2000 10:17 GMT

Local Remote Remote Route
Channel NodeName Channel State Type Avoid COS O
11.1.0.1023 sw180 5.3.0.1023 Ok abrstd 0 L
11.1.108.60 sw108 6.1.53.110 Ok abrstd 0 L
11.1.108.61 sw108 6.1.53.111 Ok cbr 0 L
11.1.108.112 sw108 6.1.53.112 Ok rt-vbr 0 R
11.1.108.113 sw108 6.1.53.113 Ok nrt-vbr 0 R
11.1.108.200 sw108 6.1.53.200 Ok cbr 0 R
11.1.180.150 sw180 15.1.11.100 Ok ubr 0 R
11.1.180.530 sw180 5.3.53.530 Ok ubr 0 L
11.1.180.1000 sw180 15.1.53.1000 Ok nrt-vbr 0 L
11.1.180.1001 sw180 15.1.53.1001 Ok abrstd 0 L

Last Command: dspcons
Example (BPX)

Show a summary of connections starting with 11.1.180.1.

dspcons 11.1.180.1

sw53 VT Cisco BPX 8620 9.3.2o Nov. 30 2000 10:37 GMT

From Remote Remote Route
11.1.180.1 NodeName Channel State Type Avoid COS O
11.1.180.150 sw180 15.1.11.100 Ok ubr 0 R
11.1.180.530 sw180 5.3.53.530 Ok ubr 0 L
11.1.180.1000 sw180 15.1.53.1000 Ok nrt-vbr 0 L
11.1.180.1001 sw180 15.1.53.1001 Ok abrstd 0 L

Last Command: dspcons 11.1.180.1
Example (IGX)

Display a summary of all connections on an IGX.

dspcons

sw108 VT Cisco IGX 8420 9.3.2o Nov. 30 2000 08:46 GMT

Local Remote Remote
Channel NodeName Channel State Type Compress Code COS
6.1.20.3 sw180 4.1.20.3 Ok rt-vbr 0
6.1.53.110 sw53 11.1.108.60 Failed abrstd 0
6.1.53.111 sw53 11.1.108.61 Failed cbr 0
6.1.53.112 sw53 11.1.108.112 Failed rt-vbr 0
6.1.53.113 sw53 11.1.108.113 Ok nrt-vbr 0
6.1.53.200 sw53 11.1.108.200 Ok cbr 0
9.1.918 sw180 15.1.9.18 Ok atfx 0
9.1.919 sw180 15.1.9.19 Ok atft 0
9.1.920 sw180 15.1.9.20 Ok atfr 0

This Command: dspcons

Continue direction - Previous/Quit? (p/q)
Example (BPX)

Display connections and A-bit status.

dspcons -abit

sw53 VT Cisco BPX 8620 9.3.2o Nov. 30 2000 10:42 GMT

Local Remote Remote Local Remote
Channel NodeName Channel State A-bit A-bit
11.1.0.1023 sw180 5.3.0.1023 Ok OK OK
11.1.108.60 sw108 6.1.53.110 Ok OK OK
11.1.108.61 sw108 6.1.53.111 Ok OK OK
11.1.108.112 sw108 6.1.53.112 Ok OK OK
11.1.108.113 sw108 6.1.53.113 Ok OK OK
11.1.108.200 sw108 6.1.53.200 Ok OK OK
11.1.180.150 sw180 15.1.11.100 Ok OK OK
11.1.180.530 sw180 5.3.53.530 Ok OK OK
11.1.180.1000 sw180 15.1.53.1000 Ok OK OK
11.1.180.1001 sw180 15.1.53.1001 Ok OK OK

Last Command: dspcons -abit
Example (IGX)

Display connections and A-bit status.

dspcons -abit

sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 09:04 GMT

Local Remote Remote Local Remote
Channel NodeName Channel State A-bit A-bit
4.1.2.2 sw108 4.3.1.2 Ok OK OK
4.1.10.1 sw108 4.1.10.1 Ok OK OK
4.1.20.1 sw108 6.1.20.1 Ok OK OK
4.1.20.2 sw108 6.1.20.2 Ok OK OK
4.1.20.3 sw108 6.1.20.3 Ok OK OK
4.2.10.1 sw108 4.3.10.1 Ok OK OK
5.3.0.11 sw180 5.3.0.50 Ok OK OK
5.3.0.50 sw180 5.3.0.11 Ok OK OK
5.3.0.1023 sw53 11.1.0.1023 Ok OK OK
5.3.1.1 sw180 5.3.1.1 Ok OK OK
5.3.10.1 sw108 3.3.10.1 Ok OK OK
5.3.53.530 sw53 11.1.180.530 Ok OK OK
14.1.10.1 sw108 3.1.10.1 Ok OK OK

This Command: dspcons -abit

Continue direction - Next/Quit? (n/q)
Example (IGX)

Display voice connections.

dspcons -f

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 12:20 PST

Local Remote Remote Only
Channel NodeName Channel State v Compress Code COS
10.1.1 igxr02 20.1.1 Ok p 0
10.1.3-4 igxr02 20.1.3-4 Ok v VAD 2
10.1.5-6 igxr02 20.1.5-6 Ok t 0
10.1.9-10 igxr02 20.1.9-10 Ok a24 ADPCM 2
10.1.11-12 igxr02 20.1.11-12 Ok c24 VAD/ADPCM 2
10.1.13-14 igxr02 20.1.13-14 Ok a32 ADPCM 2
10.1.15-16 igxr02 20.1.15-16 Ok c32 VAD/ADPCM 2
10.1.19-20 igxr02 20.1.19-20 Ok l16v VAD/LDCELP 2
10.2.1 igxr02 20.2.1 Ok p 0
10.2.3-4 igxr02 20.2.3-4 Ok a24 ADPCM 2
10.2.5-6 igxr02 20.2.5-6 Ok a32 ADPCM 2
10.2.7 igxr02 20.2.7 Ok l16 LDCELP 2
10.2.9 igxr02 20.2.9 Ok l16v VAD/LDCELP 2

Last Command: dspcons -v
Example (IGX)

Display data connections.

dspcons -d

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 12:30 PST

Local Remote Remote Only
Channel NodeName Channel State d Compress Code COS
6.1 igxr02 18.1 Ok 1024 7/8 0
6.2 igxr02 18.2 Ok 256 7/8 0
6.3 igxr02 18.3 Ok 256 7/8 0
6.4 igxr02 18.4 Ok 128 DFM 7/8 0
10.1.5-6 igxr02 20.1.5-6 Ok t 0
11.17-24 igxr02 21.17-24 Ok t 0
15.3 igxr01 12.4 Ok 128 DFM 7/8 0
15.4 igxr01 12.3 Ok 128 DFM 7/8 0
22.1 igxr02 19.1 Ok 16 DFM 7/8 0
22.2-8 igxr02 19.2-8 Ok 19.2 DFM 7/8 0

Last Command: dspcons -d
Example (IGX)

Display the connection with descriptors.

dspcons

sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 09:38 GMT

Local Remote Remote
Channel NodeName Channel State Type Descriptor
4.1.2.2 sw108 4.3.1.2 Ok cbr
4.1.10.1 sw108 4.1.10.1 Ok cbr
4.1.20.1 sw108 6.1.20.1 Ok nrt-vbr
4.1.20.2 sw108 6.1.20.2 Ok nrt-vbr
4.1.20.3 sw108 6.1.20.3 Ok rt-vbr
4.2.10.1 sw108 4.3.10.1 Ok cbr
5.3.0.11 sw180 5.3.0.50 Ok cbr
5.3.0.50 sw180 5.3.0.11 Ok cbr
5.3.0.1023 sw53 11.1.0.1023 Ok abrstd
5.3.1.1 sw180 5.3.1.1 Ok cbr
5.3.10.1 sw108 3.3.10.1 Ok cbr
5.3.53.530 sw53 11.1.180.530 Ok ubr
14.1.10.1 sw108 3.1.10.1 Ok rt-vbr

This Command: dspcons +d

Continue direction - Next/Quit? (n/q)
Example (IGX)

Display a summary of connections starting with 5.3.

dspcons 5.3

sw180 TN Cisco IGX 8420 9.3.o1 Nov. 30 2000 09:50 GMT

Local Remote Remote
Channel NodeName Channel State Type Compress Code COS
5.3.0.11 sw180 5.3.0.50 Ok cbr
5.3.0.50 sw180 5.3.0.11 Ok cbr
5.3.0.1023 sw53 11.1.0.1023 Ok abrstd 0
5.3.1.1 sw180 5.3.1.1 Ok cbr
5.3.10.1 sw108 3.3.10.1 Ok cbr 10
5.3.53.530 sw53 11.1.180.530 Ok ubr 0
14.1.10.1 sw108 3.1.10.1 Ok rt-vbr 0
14.1.15.5 sw108 3.1.15.5 Ok cbr 0
14.1.15.6 sw108 3.1.15.6 Ok cbr 0
14.1.15.7 sw108 3.1.15.7 Ok cbr 0
14.1.15.8 sw108 3.1.15.8 Ok cbr 0
14.1.15.9 sw108 3.1.15.9 Ok cbr 0
14.1.15.10 sw108 3.1.15.10 Ok cbr 0

This Command: dspcons 5.3

Continue direction - Next/Quit? (n/q)
Example (IGX)

Display Frame Relay connections only.

dspcons -f

igxr01 TN Cisco IGX 8420 9.3.2V Jan. 18 2001 10:59 PST

Local Remote Remote Only
Channel NodeName Channel State f Compress Code COS
9.1.1 igxr03 26.1.1 Ok fr 0
9.1.2 igxr03 26.1.2 Ok fr 0
9.1.3 igxr03 26.1.3 Ok fr 0
9.1.4 igxr03 26.1.4 Ok fr 0
9.1.5 igxr03 26.1.5 Ok fr 0
9.1.6 igxr03 26.1.6 Ok fr 0
9.1.7 igxr03 26.1.7 Ok fr 0
9.1.8 igxr03 26.1.8 Ok fr 0
9.1.9 igxr03 26.1.9 Ok fr 0
9.1.10 igxr03 26.1.10 Ok fr 0
9.1.11 igxr03 26.1.11 Ok fr 0
9.1.12 igxr03 26.1.12 Ok fr 0
9.1.13 igxr03 26.1.13 Ok fr 0

Last Command: dspcons -f
Example (BPX)

Displays all connections starting with 4.1.1.4.

dspcons 4.1.1.4

ca19 VT SuperUser BPX 15 9.3 Apr. 13 2000 19:44 GMT

Local Remote Remote Route
Channel NodeName Channel State Type Avoid COS O
4.1.1.4 ca20 12.1.1.4 Ok CBR 0 R
4.1.1.5 ca20 12.1.1.5 Ok rt-VBR 0 R
4.1.1.6 ca20 12.1.1.6 Ok ABR 0 R
4.1.1.7 ca20 12.1.1.7 Ok nrt-VBR 0 R

Last Command: dspcons

Next Command:
Example (IGX)

Display only VP tunnelling connections on that node.

dspcons -tun

sw224 TRM StrataCom IGX 8420 9.3 Apr. 13 2000 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

dspconst (display connection state for line connections)

Displays the status of the circuit line(s) and continues to display the status until you press the Delete key. While the display is on the screen, the status is automatically updated. The update frequency is one second for each circuit line being displayed. (For example, if only one line is displayed, the update frequency is once per second, if three circuit lines are displayed, the update frequency is once per three seconds.) Table 4-18 shows the connection type. The cnfchtp command must be correctly configured.

Table 4-18 Types of Connection Status

Symbol

Description

+

off-hook

-

on-hook

m

slow modem

M

fast modem

F

FAX

blank

channel not connected

Syntax

dspconst [circuit line]

Parameters

Parameter

Description

[circuit line]

Specifies the number of the line for the channel state display. If you do not specify a line, all upped circuit lines (up to a maximum of eight at once) are displayed.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

cnfchtp

Example

Display the condition state for the voice channels on the node.

dspconst

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 09:55 PST

Connection status display

+ offhook, - onhook, m slow modem, M fast modem, F FAX
1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
CLN 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

14 +

This Command: dspconst

Hit DEL key to quit:

dspctrlrs (display all controllers on a BPX node)

Displays the controllers, such as an PNNI SES controller on a BPX node or an MPLS controller on the IGX.

Displays all the VSI controllers on a BPX node. You can also the dspnode command to display the VSI controllers on a BPX node. To add and delete a VSI controller such as a Label Switch Controller to a BPX node, use addshelf and delshelf.

The dspctrlrs command lists:

•controller ID

•partition the controller uses

•trunk or interface to which a controller is attached

•controller type (always an MPLS controller)

•interface type (AAL5, VSI Label Switching) or MGX 8220 interface shelf

•the name of the controller/entity that the controller exists on (that is, node name, equipment name)

•VPI used for the control channel

•VCI range used for the control channel

•IP address of the controller

Syntax

dspctrlrs <slot.port><controller name string><partition_id><controller_id>

Parameters

Parameter

Description

<slot.port>

<controller name string>

<partition_id>

<controller_id>

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

No

Yes

BPX, IGX

Yes

Yes

No

No

Related Commands

addctrlr, cnfctrlr, delctrlr, dspnode, addshelf

Example (IGX)

Display all the VSI Controllers attached to an IGX node.

dspctrlrs

arnold TN Cisco IGX 8430 9.3.1p Aug. 16 2000 17:09 PST

VSI Controller Information

CtrlrId PartId ControlVC Intfc Type CtrlrIP
VPI VCIRange
2 1 0 75-105 12.1 MPLS 0.0.0.0
3 2 0 40-70 12.1 MPLS 0.0.0.0

Last Command: addctrlr 12.1 2 1 0 75

Controller added successfully!
Next Command:
Example (BPX)

Display VSI controllers on a BPX node.

dspctrlrs

sw174 TRM StrataCom BPX 8620 9.3.10   Sep 20 2000 14:31 GMT

BPX 8620 VSI controller information

Ctrl Id Part Id Trunk Ctrlr Type Intfc Type Name
1 1 2.1 VSI AAL5 SIMFDR0

Last Command: dspctrlrs

dspcurclk (display current clock sources)

Displays the current clock source. The display for dspcurclk contains:

•Source Node: the node in the network where the clock source originates.

•Source Line: the type of line used as the clock source and its back slot number (for example, "CLN 15", TRK 22, "EXTERNAL 2", or "INTERNAL").

•Clock Type: the clock type configured for the source clock (primary, secondary, or tertiary). If the source clock for the node is an internal oscillator, no clock type is given.

•Clock Frequency: the received clock frequency as measured by the local BCC.

•Path to Source: the path from the current node to the node of the originating clock source. This includes all intermediate nodes and trunks.

Syntax

dspcurclk

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnfclksrc, dspclksrcs

Example

Display the current clock source.

dspcurclk

bootzilla TRM YourID:1 IGX 8430 9.3 Apr. 13 2000 15:33 MST

Current Clock Source

Source Node: gamma
Source Line: Internal
Clock Type:
Clock Frequency: 1544015

Path to Source:
bootzilla 9--10gamma

Last Command: dspcurclk

Next Command:

dspdnld (display download)

Displays the status of a download to a nodes.

This command displays the status of any software or firmware download operation from Cisco WAN Manager to the node controller card. You should be connected to the node being downloaded either directly or via a virtual terminal connection. The display download command shows:

•download destination—Node currently being downloaded.

•download type—Destination of the downloaded image, standby RAM or active or standby ROM, or firmware.

•download source—Where the image to be downloaded is currently stored, Cisco WAN Manager, an active or standby controller, or a remote node.

•download image—Where the image is located, ROM or RAM.

This command can be used to check how far along the download has progressed. Blocks of data already downloaded appear highlighted; the remaining blocks appear dim. If there was no download initiated when this command was entered, the blocks of data appear as all zeros.

Syntax

dspdnld

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

loadrev, getfwrev

Example (IGX)

dspdnld

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:23 PST

dl_dest: Active CC dl_source: Active CC
dl_type: None dl_image: ROM

30010800 30020800 30030800 30040800 30050800 30060800 30070800 30080800
30090800 300A0800 300B0800 300C0800 300D0800 300E0800 300F0800 30100800
30110800 30120800 30130800 30140800 30150800 30160800 30170800 30180800
30190800 301A0800 301B0800 301C0800 301D0800 301E0800 301F0800 30200800
30210800 30220800 30230800 30240800 30250800 30260800 30270800 30280800
30290800 302A0800 302B0800 302C0800 302D0800 302E0800 302E3E7C

Last Command: dspdnld

Next Command:

dspdutl (display data channel utilization)

Displays the percentage of channel utilization of data connections.

This command displays the percentage utilization for the data connections starting at the back slot (bslot) number you specify. All data connections for the node are displayed (maximum of 32).

The percentage is calculated by dividing the number of packets transmitted over the total number of packets allocated to the specified channel. Only transmit packet rates are used. If percentage use exceeds the use configured, the channel appears in reverse video.

Use the clear option to clear all slots. Use dsputl to display utilization for voice channels.

Syntax

dspdutl <start bslot> [clear]

Parameters

Parameter

Description

<start bslot>

Specifies the slot where the data card is located.

[clear]

Specifies that all data channel utilization buffers should be cleared after the display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

IGX

No

Related Commands

dsputl

Example

dspdutl 13

sw150 TN SuperUser IGX 8420 9.3 Apr. 13 2000 20:07 GMT

Percentage utilization Last Cleared: Date/Time Not Set Snapshot
From
Slot 1 2 3 4 5 6 7 8 Slot 1 2 3 4 5 6 7 8
13 6 99 99

Last Command: dspdutl 13

Next Command:

dspecparm (display echo canceller parameters)

Displays statistics configured as enabled for a selected CDP echo canceller. This command displays the Integrated Echo Canceller card parameters associated with the specified circuit line. Set these parameters by using the cnfecparm command.

Syntax

dspecparm <line>

Parameters

Parameter

Description

<line>

Specifies the circuit line to display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

IGX

No

Related Commands

cnfecparm

Display Fields

Number

Parameter

Description

1

Echo Return Loss High

Maximum ERL required for echo canceller to be enabled.

2

Echo Return Loss Low

Minimum ERL required for echo canceller to be enabled.

3

Tone Disabler Type

Selection of protocol to enable tone disabler.

4

Non-Linear Processing

Selects type of post-canceller signal.

5

NLP Threshold

Threshold to enable non-linear processing.

6

Noise Injection

Determines if noise will be injected when NLP is active.

7

Voice Template

Selection of echo canceller template to use.

Examples

dspecparm 7

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:34 PST

IEC Line 7 Parameters
1 CDP IEC Echo Return Loss High (.1 dBs) [ 60] (D)
2 CDP IEC Echo Return Loss Low (.1 dBs) [ 30] (D)
3 CDP IEC Tone Disabler Type [ G.164]
4 CDP IEC Non-Linear Processing [Center Clipper]
5 CDP IEC Non-Linear Processing Threshold [ 18] (D)
6 CDP IEC Noise Injection [ Enabled]
7 CDP IEC Voice Template [ USA]

Last Command: dspecparm 7

Next Command:

dspeventq (display event queue)

Display information about any configured event queues from the fail event handler.

Syntax

dspeventq

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

clreventq

Example

Display the contents of the fail event handler on the current node.

dspeventq

swstorm TN SuperUser BPX 8620 9.3 Apr. 13 2000 11:00 GMT

QUEUE LENGTH THROTTLING
NUM NAMES MAX HIGH CURRENT POINT
1 Fail_Xid 4 1 14000
2 Fail_ Q 4 0

Last Command: dspeventq

Next Command:

dspfrcbob (display FRC/FRM breakout box)

Displays the current state of the signals on the FRM-2 or FRP-2 physical port. The display is real-time and updated according to the interval parameter. The display refreshes at a user-specified interval until either the Delete key is pressed or until a timeout occurs.

This command does not show inputs from the user equipment. It shows inputs from the Port Concentrator module to the FRI-2.

For the Inputs from the User Equipment, the display shows the signals as either On, Off, Active, or Inactive.

For the Outputs to User Equipment, the display shows the signals as either On, Off, Active, or Inactive.

X.21 State Names and Leads for DTC and DCE interfaces are also displayed as ON or OFF.

Syntax

dspfrcbob <slot.port> <interval>

Parameters

Parameter

Description

<slot.port>

Specifies the slot and port of an FRM-2/FRC-2 physical port.
Range: 1-4

<interval>

Specifies the screen update interval in seconds.
Default: five seconds

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-3

No

No

IGX

Yes

Related Commands

dspbob, dspfrcport

Example

Display the signals states for port 2 in slot 5.

dspfrcbob 5.2

bootzilla LAN SuperUser IGX 8430 9.3 Apr. 13 2000 15:09 GMT

Physical Port: 5.2
Interface: FTI-X21 DCE
Clocking: Normal (512224 bps)

Inputs from User Equipment Outputs to User Equipment
Lead Pin State Lead Pin State Lead Pin State Lead Pin State
C 3/10 On I 5/12 On
T 2/9 Active R 4/11 Active

X.21 State Name DTE Lead T C DCE Lead R I
1 Ready 1 OFF 1 OFF
13 S Send Data D ON 1 OFF
13 R Receive Data 1 OFF D ON
13 Data Transfer D ON D ON

This Command: dspfrcbob 6.2 1

Hit DEL key to quit:

dspfrcls (display Frame Relay classes)

Displays the configuration of a Frame Relay class. Network-wide classes are available to provide a shortcut for adding Frame Relay connections.

The */* in the PIR (Peak Information Rate) column means that if a connection is added using this Frame Relay class, the PIR for this connection will be equal to that of the port speed on which the connection was added. For example, if the port speed for port 6.1 = 64 Kbps, and if a connection 6.1.100 is adding using the Frame Relay class, it will have a value of 64 Kbps for the PIR parameter.

Syntax

dspfrcls

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

IGX

No

Related Commands

addcon, cnffrcls

Example

Display the Frame Relay class configurations. The screen display is the same as that for the cnffrcls command.

dspfrcls

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 13:43 GMT

Frame Relay Connection Classes

# MIR CIR VC Q Depth PIR Cmax ECN QThresh
1 9.6/9.6 9.6/9.6 65535/65535 */* 10/10 65535/65535
QIR: 9.6/9.6 FST: n % Util: 100/100 Description: "Default 9.6"
2 19.2/19.2 19.2/19.2 65535/65535 */* 10/10 65535/65535
QIR: 19.2/19.2 FST: n % Util: 100/100 Description: "Default 19.2"
3 16/16 16/16 65535/65535 */* 10/10 65535/65535
QIR: 16/16 FST: n % Util: 100/100 Description: "Default 16"
4 32/32 32/32 65535/65535 */* 10/10 65535/65535
QIR: 32/32 FST: n % Util: 100/100 Description: "Default 32"
5 56/56 56/56 65535/65535 */* 10/10 65535/65535
QIR: 56/56 FST: n % Util: 100/100 Description: "Default 56"

This Command: dspfrcls

Continue?

dspfrcport (display FRC-2/FRM-2 port configuration)

Displays physical port configuration for FRM-2 or FRP-2 ports connected to a Port Concentrator.

The screen displayed with this command includes fields for standard Frame Relay ports on the FRM card. Only the fields in the following table have meaning for a Port Concentrator.

Syntax

dspfrcport <slot.port> <interval>

Parameters

Parameter

Description

slot.port

Specifies the physical slot and port of the Frame Relay card set.
Range: 1-4

interval

Specifies the screen update interval in seconds.
Default: five seconds

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

BPX, IGX

No

Related Commands

dspfrcport, dspbob

Display Fields

Field

Meaning

Interface

Always FRI-X.21 DCE for PCS ports.

Clocking

Always Normal for PCS ports.

Port Type

Specifies port type, always FR (Frame Relay) for PCS ports.

Port ID

Specifies the DLCI for the port, always 1022 for PCS ports.

Port Queue Depth

Specifies the maximum bytes queued for transmission from the FRM-2 or FRP-2 port.
Range: 0-65535
Default: 65535

DE Threshold

Specifies the port depth queue above which frames with the Discard Eligibility bit set will be discarded.
Range: 0-100 percent,
Default: 100 percent
100 percent effectively disables DE for the port.

Signaling Protocol

For Frame Relay ports, specifies LMI operation mode. For PCS ports, this is set to None.

Measured Rx Clock

The actual speed of received data as clocked by the FRM-2 or FRP-2. Under normal operation, this should always display the fixed concentrated link speed of 512 Kbps. Clock speed is measured by the FRM-2 or FRP-2 once per minute.

Concentrated Link Util

Current utilization percentage of the concentrated link. Utilization is defined as the percentage of the fixed link speed (512K) used for data. Because the maximum allowable aggregate for each link's 11 ports is 448 Kbps, 88 percent is the maximum value for this field.

Min Flags / Frames

Specifies the minimum number of flags per frame. All values greater than zero are valid. Default: 1

OAM Pkt Threshold

Specifies the OAM FastPackets used within the local node to transmit the NNI status from the remote network.
Range: 0-15 packets.
Default: 3
A 0 disables this function.

Example

Display the configuration of port 3.1.

dspfrcport 3.1

tecate LAN SuperUser IGX 8420 9.2 Apr. 13 2000 10:25 PST
Physical Port: 3.1 [ACTIVE]
Interface: FRI-X.21 DCE Configured Clock: 512 Kbps
Clocking: Normal Measured Rx Clock: 512 Kbps
Port Type FR Min Flags / Frames 1
Port ID 1022
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 6 sec
DE Threshold 100 % N391 Full Status Poll 10 cyl
Signalling Protocol None ForeSight (CLLM) No
Asynchronous Status No CLLM Status Tx Timer 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Interface Control Template
N393 Monitored Events Count 4 Lead I
Communicate Priority No State ON
Upper/Lower RNR Thresh 75%/ 25% Concentrated Link Util 88%

Last Command: dspfrcport 3.1

Next Command:

dspfwrev (display firmware revision)

Displays the status of card firmware revision image loaded in the controller card's RAM.

This command displays the revision level and an indication of the length of the firmware in the controller card. It might require two screens to display all the parameters (see example).

You can use this command while firmware is downloading to a node to get an idea of how far along the downloading process has progressed. The blocks already downloaded appear normal. Blocks that are yet to be downloaded appear shaded.

If no getfwrev command was issued, nothing displays. If "Configuration image present" displays, use the loadcnf clear command to clear this status.

Syntax

dspfwrev

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

getfwrev, burnfwrev

Example

dspfwrev

gamma TRM SuperUser Rev: 9.3 Apr. 13 2000 14:28 PDT

Firmware Size Status
F.D.A 256 K Complete

File Address Length CRC Burn Address
File Address Length CRC Burn Address
1 800800 410 22996DDA
1 800800 410 22996DDA
3 805E60 480 85CB29EA
4 80A630 70 57A938AE
4 80A630 70 57A938AE
6 810000 10000 338E45F6
7 820000 4400 95990113
8 835000 1810 875771B2
9 8368A0 15D0 4C597B97

This Command: dspfwrev

Continue?

_________________________________________________

gamma TRM SuperUser Rev: 9.3 Apr. 13 2000 14:29 PDT

Firmware Size Status
F.D.A 256 K Complete

File Address Length CRC Burn Address
10 838000 20F0 0F4898D2
11 83A100 1E20 175F4B39
12 83C000 2FC0 F39B0302
13 83F000 1B0 E755FE4E
14 83FFFE 2 A1F4726D

Last Command: dspfwrev

Next Command:

dsphitless (display statistical history of hitless rebuilds)

Displays the statistical history of hitless rebuilds that may have occurred within the configured thresholding period. (This thresholding period is described in the cnfnodeparm command definition, under Index #42, Maximum Hitless Rebuild Count, and Index #43, Hitless Counter Reset Time parameters.)

Hitless rebuild is a modified control software restart on the processor card that prevents a full configuration rebuild of the node.

Normally, if it is necessary to restart the control software, and a switchover is not possible, then the node does a full rebuild. A node with many connections may take two hours to restore itself fully to the network. In the meantime, communications are broken with some nodes and some network connections are not routed or are not on their preferred routes.

The Hitless Rebuild feature provides the ability for a node to effectively rebuild without affecting user traffic. Hitless rebuild avoids resetting the line or trunk cards, or interfering with user traffic in any way during the control software restart. During most software restarts, the interface cards are not reset to preserve their configurations. Even if the standby processor card is failed or absent and the active card must abort, a full rebuild is avoided. This substantially decreases the time it takes for the BPX software to settle into its normal operating state after a rebuild.

Certain databases containing configuration data (such as current and preferred routes) are stored in BRAM (battery-backed RAM) so that they survive system initializations and power outages. A statistical history of hitless rebuilds is also stored in BRAM so that this history survives a full rebuild. Two records of hitless rebuilds are maintained: one contains information within the current thresholding window. When a full rebuild occurs, the hitless rebuild statistics from the current window are moved to a saved area, and a new current window begins. Optional parameters allow you to display either a summary screen or a detailed screen giving the history of hitless rebuilds. There are two versions of each screen, one for the current window and one for the saved previous window.

The Hitless Rebuild feature is internal to the switch software on a node. If there is a problem with the node, switch software takes care of it; no user intervention is needed.

As part of the Hitless Rebuild feature, the Autobus diagnostic feature on the node is disabled because it requires the node to undergo a series of full rebuilds causing the node to be out of the network for a long duration of time.

Syntax

dsphitless [-d] [-p] [-c] [-s]

Parameters

Parameter

Description

-d

Detailed screen. Default: summary screen

-p

Previous window. Default: Active window

-c

Clear statistics for current window

-s

Standby statistics

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

No

No

BPX, IGX

No

Related Commands

cnfnodeparm, resetcd, switchcc, dspcds, dsplog

Example

dsphitless

sw99 TN SuperUser BPX 8620 9.3 Apr. 13 2000 14:59 GMT

current hitless rebuild count: 7
high water mark: 9
cnf max before full rebuild: 10
cnf reset timer: 24 hours
most recent hitless rebuild: 08/27/98 14:27:09
oldest hitless still in count: 08/27/98 11:42:18
Hitless stats cleared: 07/29/98 12:00:05
Action when cnf max is exceeded: full rebuild

Last Command: dsphitless

Next Command:
Example

dsphitless d p

sw99 TN SuperUser BPX 15 9.3 Apr. 13 2000 14:59 GMT

1 04/07/98 14:27:09 software abort 1000003
2 04/07/98 13:58:46 software abort 1000003
3 04/07/98 13:32:24 software abort 1000003
4 04/07/98 12:57:36 software abort 1000003
5 04/07/98 12:28:29 software abort 1000003
6 04/07/98 12:07:16 software abort 1000003
7 04/07/98 11:42:18 software abort 1000003

Last Command: dsphitless d p

Next Command:
Software Revisions and Interoperability

The Hitless Rebuild feature requires Release 9.2 or later switch software, and works on both the BPX and IGX platforms. This feature is local to a node. Hitless rebuild functions correctly on nodes running software that contains the feature, even in a network with mixed software releases, some of which do not have the feature.

Hitless rebuild will operate during upgrades, but will not operate during a downgrade. If a failure occurs that would normally result in a controller card switchover, but the switchover needs to be suppressed due to the different software releases running on the two processors, then a hitless rebuild will be done instead.

If a backoff must be done from an upgrade, then a full rebuild will occur. A backoff refers to the state where the new switch software revision has been loaded as the secondary image, and the decision is made to go back to the original revision.

There are no operational problems if, during an upgrade, the new release of software has the Hitless Rebuild feature and the older release does not. Hitless Rebuild will just operate on the processor card with the newer release.

Most aspects of a full rebuild and a hitless rebuild function the same way. For example, initial synchronization between the switch and Cisco WAN Manager and the loss of statistics information will remain the same.

Safe Switchover

Sometimes shortly after a switchover, the new active processor card will run some diagnostics and detect a failure, causing it to switch back to the original active card. The Hitless Rebuild feature improves this situation under most conditions. Following any processor card switchover, the new standby will rebuild, preserving the key databases needed for a hitless rebuild (11 seconds). When database updates can start, the standby will rebuild again doing a normal standby rebuild (11 seconds). If there is a failure on the new active card that causes it to switch back before updates can start, the card taking over will do a hitless rebuild. If the active processor card fails while still updating its standby, it will perform a hitless rebuild.

Action Taken If the Control Card Fails

During any active control card failure, a decision must be made about the type of initialization to undertake. Table 4-19 shows the possible conditions, and the corresponding actions.

Table 4-19 What Happens when a Control Card Restarts or Aborts

Reason

Standby

Ready

Standby

Updating

Standby

Not Ready,

Not Updating

Standby

State Unknown

Standby Does Not Exist

Standby

in Upgrade

Standby State Not Applicable

Aborts

(examples include:

•bad logical ptr

•bad nib DB

•bad topology

•memory allocs

•out of buffers

•bad primary revision

Switch

Hitless

Hitless

Hitless

Hitless

Hitless

N/A

Abort

(CC mastership error. Active now is standby card)

N/A

N/A

N/A

N/A

N/A

N/A

Full standby rebuild

(DBs are corrupted)

Exceptions

•Write Protect

•Address Error

•Trap Error

•Bus Unknown

Switch

Hitless

Hitless

Hitless

Hitless

Hitless

N/A

Exceptions

•Parity Error

Switch

Hitless

Hitless

Hitless

Hitless

Hitless

N/A

Exceptions

•Spurious Int

Switch

Hitless

Hitless

Hitless

Hitless

Hitless

N/A

Bad Image CRC

Switch

Hitless

Hitless

Hitless

Hitless

Hitless

N/A

WatchDog

Time-out

Switch

Hitless

Hitless

Hitless

Hitless

Hitless

N/A

User Command

•clrallcnf

•clrcnf

•resetcd H

N/A

N/A

N/A

N/A

N/A

N/A

Full rebuild

Bad CommBus

N/A

N/A

N/A

N/A

N/A

N/A

Degrade

Mode

Bus Diagnostics

(destructive)

N/A

N/A

N/A

N/A

N/A

N/A

Full rebuild

configuration Changes

•runcnf

N/A

N/A

N/A

N/A

N/A

N/A

Full rebuild

Bad BCC card

Switch

Ignore

Ignore

Ignore

Ignore

Ignore

N/A

Bad CrossPoint

Ignore

Ignore

Ignore

Ignore

Ignore

Ignore

Ignore

Preparation for revision change

(happens only on the standby card)

N/A

N/A

N/A

N/A

N/A

N/A

Full standby rebuild

Revision Switch

Switch

N/A

N/A

N/A

N/A

N/A

Hitless rebuild on standby

Primary Revision Change

N/A

N/A

N/A

N/A

N/A

N/A

Full rebuild on either card

Starting the updates to the standby card—message is sent by the active card

N/A

N/A

N/A

N/A

N/A

N/A

Full rebuild on the standby card

User switchcc

(hitless on standby card)

Switch

Switch

•Full rebuild on newly active

•Hitless rebuild on standby

Switch

•Hitless rebuild on standby

•Active rebuild depends on rebuild flag state

N/A

N/A

N/A

Hitless rebuild on the standby card

When a controller card switchover to the new card occurs, the new standby card (unless shown differently in Table 4-19) performs a hitless rebuild. These databases are maintained, allowing the card to take over without affecting traffic until the updates are started. After the updates have started, the new standby card does a full rebuild to get ready to receive the updates.

When the threshold is exceeded and the node is to enter degraded mode, a hitless rebuild occurs first. After the hitless rebuild completes the node enters degraded mode.

How Memory is Managed During Hitless Rebuilds

Full rebuilds result in the complete initialization of all RAM memory regions. Before the Hitless Rebuild feature, there was no need to save any databases in RAM through an initialization. All databases were rebuilt from configuration stored in BRAM. For a rebuild to be hitless, databases containing certain types of critical information related to trunks, connections, and so on, must survive intact in RAM.

Configuration data that must survive a hitless rebuild is moved to regions where it remains intact. These "hitless regions" regions are managed by a memory management algorithm.

When logged into a node, you can see the changes by using the Profiler. The commands dspprf and dspprfhist show some statistics related to memory usage. Refer to the service commands for descriptions of dspprf and dspprfhist commands. You must have service-level privileges to use the debug, or service-level commands.

Errors and Alarm Handling

The Hitless Rebuild feature does not cause many changes to errors or alarms. However, most of the conditions that cause a hitless rebuild will themselves generate errors or alarms. There are no changes to these.

The Hitless Rebuild feature introduces two new events, indicating the end of a hitless rebuild or a full rebuild. These will be logged into the local event log on the node (which you can view with dsplog).

Corresponding Robust Card Alarm messages are sent from the node to Cisco WAN Manager, and these generate traps that are sent to Cisco WAN Manager's RTM proxy. The traps make the information available to external network management systems that register for traps on Cisco WAN Manager.

As always, the Robust Alarm mechanism does not guarantee that all alarm state transitions will result in messages being sent to Cisco WAN Manager. The mechanism guarantees that "current state" information is sent; however, when multiple transitions occur close together, only the last one is guaranteed. During a rebuild, a few changes may occur quickly.

The Robust Card Alarm messages sent to Cisco WAN Manager have the following values:

•Trap Type: The current state of the card. (Fail, Active, Down, and so on)

•Alarm Class: (1) Info

•Reason: (3107) BCC Completed hitless rebuild.

•(3108) BCC Completed full rebuild. This Robust Card Alarm messages will result in Cisco WAN Manager traps of the following type:

•TrapType: (20004) Card Alarm

•TrapReason: (3107) BCC Completed hitless rebuild

•(3108) BCC Completed full rebuild

Consistency Checking

When a hitless rebuild is completed, the node goes through consistency checks to verify the databases. Some of these include topology checking, and verification of LCONS and VIA LCONS to have valid end points.

During normal switch operation, or during normal switchovers into hot standby processor cards, the Hitless Rebuild feature should have no impact on the performance of switch software.

Normal switchcc

The following chart shows the steps for a normal switchcc. The standby is ready (in Standby state). Up to step 4 the new standby (card 7) can do a hitless rebuild if necessary. A standby card rebuild is not the same as an active card rebuild. This is the same for both normal and hitless rebuilds.

The normal abort case is almost identical to this case. In step 1, the abort causes an automatic switch. The remaining steps are the same.

Card 7

Card 8

Step 1

Active BCC.

Standby BCC—Ready

Step 2

User issues switchcc.

Step 3

Does Standby Hitless Rebuild, not ready to receive updates, can do Hitless Rebuild.

Activates itself.

Step 4

Kicks off standby updates. Can now do a Hitless Rebuild.

Step 5

Does normal standby rebuild.

Waits for standby.

Step 6

Enters normal standby mode, ready to receive updates, cannot do Hitless Rebuild.

Step 7

Starts standby updates and network updates.

Abort—Standby not Ready

All the action is on the part of the active card (see Table 4-20).

Table 4-20 What Happens During an Abort, and Standby Card is Not Ready

Card 7

Card 8

0

Active BCC.

Standby BCC—Not Ready

1

Abort occurs.
For example, the card ran out of memory.

2

Does active hitless rebuild.

3

Tries to start standby updates.

4

Starts network updates.

CommBus Failure

In the case of a CommBus failure, the active card is no longer certain of the state of any other card. In particular, it can make no assumptions about the state of the standby BCC.

Card 7

Card 8

0

Active BCC

Standby BCC—Any

1

Commbus failure detected.

2

Enter Degraded Mode if feature is enabled; otherwise, a full rebuild will occur

dspict (display interface control template)

Displays interface control template information for data channels and Frame Relay ports:

•The specified channel.

•The type of template: a, c, l, n, or f.

•The associated output leads and their status:

ON.
OFF.
Following a local input.
Following a remote input.

For Frame Relay ports, the entire port configuration screen is displayed (see dspfrport command). Any RTS to CTS delay is also shown.

Syntax

dspict <port> <template>

Parameters

Parameter

Description

<port>

Specifies the physical slot and port of the Frame Relay card set.

<template>

Specifies which control template to display for the channel. Three templates are available for data channels and one (a) for Frame Relay ports. You also specify which end of the circuit.

a = Active control template (normal operation). The only choice for a Frame Relay port.

c = Conditioned control template (when connection fails).

l = Looped control template (with local or remote loopback).

n = Near.

f = Far.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

IGX

No

Related Commands

cnfict, cpyict

Example

Display the active interface control template for channel 25.1.

dspict 25.1 a

beta TRM YourID:1 IGX32 9.3 Apr. 13 2000 17:33 MST

Data Channel: 25.1
Interface: RS232 DCE
Clocking: Normal

Interface Control Template for Connection while ACTIVE

Lead Output Value Lead Output Value
RI OFF DSR ON
CTS ON SRxD ON
DCR OFF DCD ON
SCTS ON SDCD ON
SQ ON

Last Command: dspict 25.1 a

Next Command:
Example

Display the Frame Relay data channel 9.1 interface control template.

dspict 9.1 a

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 10:26 PST

Port: 9.1 [ACTIVE ]
Interface: FRI-V35 DTE Configured Clock: 256 Kbps
Clocking: Normal Measured Rx Clock: 0 Kbps
Port ID 7
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 6 sec
DE Threshold 100 % N391 Full Status Poll 10 cyl
Signalling Protocol None ForeSight (CLLM) No
Asynchronous Status No CLLM Status Tx Timer 0 msec
T392 Polling Verif Timer 15 Interface Control Template
N392 Error Threshold 3 Lead State
N393 Monitored Events Count 4 RTS ON
Communicate Priority No DTR ON
Upper/Lower RNR Thresh 75%/ 25%
Min Flags / Frames 1

Last Command: dspict 9.1 a

Next Command:

dspjob (display job)

Displays information about a job:

•Job number and description

•Next execution date and time

•Status

•The time interval between successive executions of the job

•The results of the last execution of the job

This command requires at least the same privilege level as the person who created the job.

Syntax

dspjob <job_number>

Parameters

Parameter

Description

job number

Specifies the the number of the job to display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

addjob, deljob, dspjob

Example (IGX)

Display job number 2.

dspjob 2

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 14:17 PST

Job 1 test
Last Execution Results: None Status: Idle
Next Execution Time: 08/17/97 20:20:30 Interval: 1 days

1: prtlog
- Failure Reaction: Repeat 2 Times and Abort Exec. Results: None

Last Command: dspjob 1

Next Command:

dspjobs (display jobs)

Displays information on each job:

•Job number

•Job description

•Next execution date and time

•Execution interval between jobs

•Access Group: The privilege level required to run or display the job

To see details of an individual job, use the dspjob command.

Syntax

dspjobs

Related Commands

addjob, deljob, dspjob

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Example (IGX)

Display a summary of all jobs stored at the node.

dspjobs

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 14:16 PST

Job Description Next Execution Status Interval Access Group
1 test 08/17/97 20:20:30 Idle 1 days Group 1

Last Command: dspjobs

Next Command:

dsplancnf (display LAN interface connection)

Displays the addresses and configuration for the LAN Ethernet. The dsplancnf screen displays configuration fields showing the type of network capability and if it is ready or unavailable.

Syntax

dsplancnf

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-5

No

No

BPX, IGX

No

Related Commands

cnflan (SuperUser)

Display Fields

Field

Description

<IPAdd>

Specifies the Internet address of the node used in the TCP/IP protocol.

<IP subnet mask>

Specifies a 32-bit mask that contains information about the bit lengths of the subnet ID and host ID address fields. The format of this field uses 1s for the subnet ID field and 0s for the host ID address field as defined in the TCP/IP protocol. This mask denotes both subnet ID and host ID fields as 8-bit fields.
Default (decimal notation): 255 255 255.0

<Max. LAN Transmit Unit>

BPX only: typical amount is 1500 bytes.

<TCPServicePort>

Specifies the node's service point used by the transmission control protocol (TCP).

<GatewayIPAddr>

Specifies the Internet gateway address.

Type

List of socket types (for example, TCP, UDP, and SNMP) that are open (in READY state) for communication between the node and the LAN. In the system response shown, the TCP socket is no longer used by switch software, indicated by the UNAVAIL state.

The TimeHndlr (or Daytime) socket is related to TFTP. It lets an external node retrieve the day and time from the switch.

The Tunneling socket is used for communication between a BPX and an INS (Intelligent Network Server).

State

State of communication socket between the node and the LAN. READY indicates that the socket is open for communication between the node and the LAN. UNAVAIL indicates that the socket is not available for communication between the node and the LAN.

Example (BPX)

Display the LAN configuration for the current node.

dsplancnf

pubsbpx1 TN SuperUser BPX 8620 9.3 Apr. 13 2000 13:23 GMT

Active IP Address: 204.179.31.104
IP Subnet Mask: 255.255.255.0
IP Service Port: 5120
Default Gateway IP Address: None
Maximum LAN Transmit Unit: 1500
Ethernet Address: 00.C0.43.00.21.F0

Type State Type State
LAN READY TUNL READY
TCP UNAVAIL
UDP READY
Telnet READY
TFTP READY
TimeHdlr READY
SNMP READY

Last Command: dsplancnf

dsplanip (display LAN IP addresses)

Displays the LAN IP address and subnet mask of the local node and the LAN IP address of all other nodes reachable from a given node in the network, including feeder nodes. Feeder nodes are displayed with a blank node name, and they appear immediately beneath the hub node to which they are attached.

Similar to the dspnwip command, the dsplanip command supports Out-of-Band network management which enables management traffic to be sent over IP to the switches' LAN Ethernet interface, thereby reducing the load on trunk bandwidth and node processor times.

Service-Affecting Alarms and Out-of-Band Network Management Features

The service-affecting alarms feature enhances reporting of switch alarm conditions to Cisco WAN Manager, and to a customer network management system (NMS) through the Cisco WAN Manager RTM Proxy. Robust Alarm messages are generated from existing switch events that could affect service.

Out-of-Band network management enables management traffic to be sent over IP to switches' LAN Ethernet interface to Cisco WAN Manager, thereby reducing the load on trunk bandwidth and node processor times. For WAN Manager to be able to manage a switch out of band, these things must be done:

•To support out-of-band management feature and service-affecting alarms, SV+ must be running Release 9.2 or higher.

•The LAN IP address of the switch must be configured.

•LAN Ethernet access must be provided from the Cisco WAN Manager workstation to the switches' LAN port.

•You may use only the "lanip" option for Cisco WAN Manager, which enables out-of-band management, if all switch nodes in the network are running switch software Release 9.2 or higher.

•For an MGX 8220 (AXIS) interface shelf to send LAN IP address changes to a routing node, it must be running MGX 8220 release 4.0.20 or higher.

To change the LAN IP address of a routing node, use the cnflan command. The Out-of-Band Network Management software detects a change to the LAN IP address on a routing or feeder note and forwards an update message to Cisco WAN Manager.

The service-affecting alarms and out-of-band network management features in Release 9.2 can interoperate in mixed networks of one or more nodes running switch software Release 9.1 or 8.5.

Syntax

dsplanip

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

dspphyslns, dsptrks

Example (BPX)

Display the LAN IP address of local node, and all other reachable nodes in network.

dsplanip

sw248 TN StrataCom BPX 15 9.3 Apr. 13 2000 18:28 GMT

Active LAN IP Address: 172.29.9.155
Active LAN IP Subnet Mask: 255.255.255.0

NodeName LAN IP Address
sw252 172.29.9.159
172.29.9.175
sw263 172.29.9.167
172.29.9.163
sw8 172.29.9.124
sw248 172.29.9.155
172.29.9.134
172.29.9.173

Last Command: dsplanip

dsplm (display load model table)

Verify target node load models by issuing the chklm and dsplm commands. These commands compare sections of the current node's database with all other nodes in the network. These commands are useful before a software upgrade since ideally, the network should be alarm free at the time of the software upgrade. If this is not possible, at least the reason for all major alarms should be identified and noted, and then suitable reconfiguration should be made in order to remove the alarm.

Issue the chklm command on every node in the network sequentially. When complete, return to the first node and run the dsplm command. The P in the output stands for pass, which indicates that everything is in order. Any failures are indicated by an F in the dsplm command output screen.

Note For software Releases above 8.4, the dsplm command will give incorrect results if the network topology has recently changed.

Syntax

dsplm

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

Super group

Yes

No

BPX, IGX

No

Yes

No

No

Related Commands

chklm

Display Fields

Field

Description

Nd

Node numbers of the nodes in the network.

T

Trunk database.

L

Load model.

C

Connection identifier database.

LC

Logical Connection database.

V

Virtual path connection database.

GL

Gateway logical connection database

PB

Priority bumping band load database. PB displays the following values:

P = Pass

F = Fail

"-" = priority bumping feature not enabled

Example (BPX)

Display the load mode; table.

dsplm

sw217 TN Cisco BPX 8620 9.3.x3 June 8 2001 07:49 GMT

Nd T L C LC V GL PB
1 P P P P P P -
3 P P P P P P -

Last Command: dsplm

dsplmistats (display Annex G LMI statistics)

Displays Annex G LMI statistics for the trunk that connects an IGX/AF interface shelf to the BPX core switch shelf. To execute this command from the access shelf itself, you must Telnet to the IGX/AF. The dsplmistats command provides information to help you analyze problems that might arise while you set up a tiered network.

Syntax

On an access shelf:
dsplmistats

On an IGX node:
dsplmistats <trunk_number>

On a BPX node:
dsplmistats <slot.port>[.vport] [clear]

Parameters

Parameter

Description

slot.port[.vport]

Specifies the card slot, physical, and optional virtual port number (BXM only). Virtual ports are not available for ASI or UXM cards.

clear

On a BPX node only, the optional clear argument clears the current statistics after dsplmistats executes.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX/AF, BPX

No

Example (IGX/AF)

Display the LMI statistics for the trunk attached to the hub.

dsplmistats

batman SuperUser IGX/AF 9.3 Apr. 13 2000 18:04 PST

Annex G LMI Statistics for slot:1 port:1
VPI.VCI: 0.0 Lmi enabled Lmi polling enabled
Invalid Pdu Rx: 0 Status Polling Timer (T396) : 10
Invalid Pdu Len Rx: 0 Status Enquiry Timer (T393) : 10
Unknown Pdu Type Rx: 0 Max Status Enquiry Retry (N394): 5
Unknown IE Type Rx: 0 Update Status Timer (T394) : 10
Bad Transaction Rx: 0 Max Update Status Retry (N395) : 5
Status Rx: 1384 Spc Polling Timer : 3
Status Enq Tx: 1384 Spc Retry Timer : 0
Status Enq Rx: 1384 Spc Retry Counter : 1
Status Tx: 1384 Node Status Retry Timer : 0
Status Ack Rx: 8 Node Status Retry Counter : 0
Update Status Tx: 8 Node Status Polling Timer : 2
Update Status Rx: 8
Status Ack Tx: 8

Last Command: dsplmistats

Next Command:
Example (BXM on BPX)

Display LMI statistics for port 6 on the BXM card in slot 3.

dsplmistats 3.6

Functional Description of LMI Statistics for BXM Card

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

Table 4-21 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 CommBus 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.

dsplnalmcnf (display line alarm configuration)

Displays alarm configuration by alarm type. Each alarm type includes:

•The minor alarm threshold

•The minor alarm time

•The minor alarm clear time

•The major alarm threshold

•The major alarm time

•The major alarm clear time

The alarm threshold, alarm time, and alarm are set by using the cnflnalm command.

Syntax

dsplnalmcnf

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

cnflnalm, dspclnerrs, dsptrkerrs

Example

View the line alarm threshold configured for a node.

dsplnalmcnf

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 10:51 PST

Line Alarm Configuration

Minor Major

Violation Rate Alarm Time Clear Rate Alarm Time Clear
1) Bpv 10E-7 10 min 3 min 10E-3 10 sec 10 sec
2) Fs .01% 10 min 3 min .1% 10 sec 10 sec
3) Oof .0001% 10 min 3 min .01% 10 sec 10 sec
4) Vpd 2% 5 min 3 min 5% 60 sec 10 sec
5) Tsdp .01% 5 min 3 min .1% 60 sec 10 sec
6) Ntsdp .01% 5 min 3 min .1% 60 sec 10 sec
7) Pkterr .01% 10 min 3 min .1% 125 sec 10 sec
8) Los .0001% 10 min 3 min .01% 10 sec 10 sec

This Command: dsplnalmcnf

Continue?

---------------

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 10:51 PST

Line Alarm Configuration

Minor Major

Violation Rate Alarm Time Clear Rate Alarm Time Clear
9) Fer .01% 10 min 3 min .1% 200 sec 10 sec
10) CRC .01% 10 min 3 min .1% 200 sec 10 sec
11) Pkoof .01% 10 min 3 min .1% 200 sec 10 sec
12) Oom .001% 10 min 3 min .1% 10 sec 10 sec
13) Ais16 .0001% 10 min 3 min .01% 10 sec 10 sec
14) Bdapd .001% 5 min 3 min .1% 60 sec 10 sec
15) Bdbpd .001% 5 min 3 min .1% 60 sec 10 sec
16) Badclk .1% 10 min 3 min 1% 50 sec 10 sec

This Command: dsplnalmcnf

Continue?

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 10:52 PST

Line Alarm Configuration

Minor Major

Violation Rate Alarm Time Clear Rate Alarm Time Clear
17) Pccpd .001% 5 min 3 min .1% 60 sec 10 sec
18) Lcv 10E-6 10 min 3 min 10E-2 10 sec 10 sec
19) Pcvl 10E-6 10 min 3 min 10E-2 10 sec 10 sec
20) Pcvp 10E-6 10 min 3 min 10E-2 10 sec 10 sec
21) Bcv 10E-6 10 min 3 min 10E-2 10 sec 10 sec
22) Rxvpd 1% 5 min 3 min 4% 60 sec 10 sec
23) Rxtspd .01% 5 min 3 min .1% 60 sec 10 sec
24) Rxntspd .01% 5 min 3 min .1% 60 sec 10 sec

This Command: dsplnalmcnf

Continue?

----------------

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 10:52 PST

Line Alarm Configuration

Minor Major

Violation Rate Alarm Time Clear Rate Alarm Time Clear
25) Rxbdapd .001% 5 min 3 min .1% 60 sec 10 sec
26) Rxbdbpd .001% 5 min 3 min .1% 60 sec 10 sec
27) Rxhppd .001% 4 min 3 min .1% 60 sec 10 sec
28) Atmhec .1% 10 min 3 min 1% 120 sec 10 sec
29) Plcpoof .01% 10 min 3 min .1% 200 sec 10 sec
30) Rxspdm .01% 4 min 2 min .001% 10 sec 5 sec

Last Command: dsplnalmcnf
Next Command:

dsplncnf (display line configuration)

Displays the configuration of a line. The display fields that actually contain data depend on the type of line.

Syntax

dsplncnf <line number>

Parameters

Parameter

Description

<line number>

Identifies the line in the format slot or slot.line. If the back card has one line connector and cable, enter the slot number. If the card has more than one physical line, such as a UXM, enter a slot and line number. In the case of a UVM, however, enter just the slot number.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnfln (obsolete name: cnfcln)

Display Fields

Screen Item

Description

Options

LN configuration

Line type and the number of channels.

T1
E1

Loop clock

Specifies whether the receive clock is looped back to the transmit clock.

Y
N

Line framing

Identifies the type of line framing used by the circuit line.

DS4 for T1
ESF for T1
PLCP for T3/E3
HEC for T3/E3
STS-SC for OC-3
STM-1 for OC-3

Line coding

Identifies the line coding used by the circuit line.

E1: HDB3, AMI
T1: ZCS, B8ZS, AMI

CRC

Specifies the CRC checking on E1 lines.

Y
N

recv impedance

Nominal impedance for the receive line.

75 ohms balanced or unbalanced
120 ohms balanced

E1 signaling

Identifies the signaling type used for E1.

CCS or ABCD with CAS

encoding

Specifies the voice encoding scheme.

micro-law
A-law

T1 signaling

Identifies the signaling type used for T1.

ABCD or ABAB (with ESF line framing) or AB (with D4 line framing); CCS is available in timeslot 24 if applicable PBXs need it.

56 Kbps Bit Pos:

Position in word for bit stuffing on 56 Kbps data channels.

MSB or LSB

Pct fast modem

Cable type

Specifies the T1 or E1 cable type (used for equalization).

MAT
ABAM

Cable length

Specifies the T1 or E1 cable length in feet to the CSU or digital cross-connect.

0-220 220-440 440-655
0-133 133-262 262-393
393-524 524-655
T3/E3 = 0-255 ft.|greater than 255 ft.

Cnfg

Applies to the UVM: cnfg shows the mode of an individual UVM port. The slot.line identifies the line.

External, Passing, Blocked, or Inserting

See the UVM documentation in the Cisco IGX 8400 Series Reference for a description of these modes.

Transmit Line Rate

Applies to ATM line cards: the display shows the transmit line rate (the direction is away from the node).

The value is always the maximum for the line and is in cells per second (cps): 96000 cps for T3
80000 cps for E3
353208 cps for OC-3.

Receive Line Rate

Applies to ATM line cards: the display shows the user-configured receive line rate (the direction is towards the node).

The value is in cells per second (cps). Range for T3: 150-9600 cps
Range for E3: 150-80000 cps
Range for OC-3: 353208 cps

Header Type

Applies to ATM cards: the display shows the user-specified header type.

The header type is VCC or VPC.

Payload Scramble

Applies to ATM cards: the display shows whether payload scramble is on.

The display shows Yes or No.

Example (IGX)

Displays the configuration for an IMA line in slot 5. The dsplncnf shows the same screen as cnfln without prompting for configuration.

dsplncnf 5.1

sw225 TRM StrataCom IGX 8420 9.3.a6 Mar. 10 2000 05:55
GMT

LN 5.1(4) Config E1/119 UXM slot:5
Line DS-0 map: 1-15,17-31
IMA Group Member(s): 1-4
Retained links: 4
IMA Protocol Option: Enabled
IMA Max. Diff. Dly: 200 msec.
IMA Clock Mode: CTC
Loop clock: No
Line coding: HDB3
Line CRC: Yes
Line recv impedance: 75 ohm
Idle code: 54 hex
HCS Masking: Yes
Payload Scramble: Yes
VC Shaping: No

Last Command: dsplncnf 5.1
Example (IGX)

Displays configuration for line 1 of the UVM in slot 20. The "cnfg" field shows "External," so all DS0s terminate on line 1. Also, CAS switching is off, and SVC caching is on.

dsplncnf 20.1

igxr02 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 13:51 PST

LN 20.1 Config T1/24 UVM slot:20
Loop clock: No
Line framing: D4
Line coding: ZCS
Line encoding: u-LAW
Line T1 signalling: AB
Line cable type: ABAM
Line length: 0-133 ft.
Line 56KBS Bit Pos: msb
Line pct fast modem: 20
Line cnfg: External
Line cnf slot.line: --
Line CAS-Switching: Off
Line SVC-Caching: Off

Last Command: dsplncnf 20.1
Example (IGX)

Display configuration for line 12 of the CVM in slot 12.

dsplncnf 12

sw150 TN Cisco IGX 8420 9.3.2T Dec. 19 2000 23:09 PST

LN 12 Config T1/24 CVM slot:12
Loop clock: No
Line framing: D4
Line coding: ZCS
Line encoding: u-LAW
Line T1 signalling: AB
Line cable type: ABAM
Line length: 0-133 ft.
Line 56KBS Bit Pos: msb
Line pct fast modem: 20
Line SVC-Caching: Off

Last Command: dsplncnf 12
Example (BPX)

Show card in slot 11 as a BXM in a BPX node.

dsplncnf 11.2

sw53 VT Cisco BPX 8620 9.3.2o Dec. 5 2000 09:47 GMT

LN 11.1 Config OC3 [353208cps] BXM slot: 11
Loop clock: 0 Idle code: 7F hex

Line framing: --
coding: --

recv impedance: --
E1 signalling: --
encoding: -- cable type: --
T1 signalling: -- length: --
HCS Masking: Yes
Payload Scramble: Yes
56KBS Bit Pos: -- Frame Scramble: Yes
pct fast modem: -- Cell Framing: STS-3C

This Command: dsplncnf 11.2
Example (IGX)

Show the UXM OC-3 card in slot 5 of an IGX node.

dsplncnf 5.3

sw180 TN Cisco IGX 8420 9.3.o1 Dec. 5 2000 09:42 GMT

LN 5.3 Config OC3 UXM slot:5
Loop clock: No
Line framing: STS-3C
Idle code: 7F hex
HCS Masking: Yes
Payload Scramble: Yes
Frame Scramble: Yes

Last Command: dsplncnf 5.3

dsplnerrs (display line errors)

Displays the accumulated error count since the last time errors were reset. The clrlnerrs command clears the error counters for circuit lines by resetting all error counts to 0.

Syntax

dsplnerrs [line_number]

Parameters

Parameter

Description

line number

Specifies the circuit for the error count display. Otherwise, a summary screen for all lines appears.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

clrclnerrs, prtclnerrs

Display Fields: Line Error Types

Type

Explanation

Bipolar errors

Number of times two consecutive pulses have the same polarity (occurs only when the line uses AMI coding).

Frame slips

Number of times a frame is discarded to re-establish synchronization.

Out of frames

Number of times a loss-of-frame synchronism is detected on this line.

Loss of signal

Number of times the signal level at the circuit line input went below the minimum acceptable level.

Frame bit errors

Number of times the frame bit failed to alternate (frame error).

CRC errors

Number of times the generated CRC character did not match the received CRC character (applies only if CRC checking is enabled).

Out of MFrames

Number of times a multiframe synch error was detected (E1 lines only).

AIS - 16

Number of times the Alarm Information Signal (Blue signal) was received.

Example

dsplnerrs

sw108 VT Cisco IGX 8420 9.3.2o Dec. 5 2000 10:12 GMT

Total Statistical Errors

Code Frame Out of LossOf Frame CRC Out of
CLN Errors Slips Frames Signal BitErs Errors MFrms AIS-16
3.1 0 - 0 0 0 0 - -
3.2 0 - 0 0 0 0 - -
3.3 0 - 0 0 0 0 - -
4.1 0 - 0 0 0 0 - -
4.3 0 - 0 0 0 0 - -

Last Command: dsplnerrs

dsplns (display lines)

Displays basic configuration and status information for all the lines on the node. The dsplns command is the same as the dspclns command.

The dsplns information includes the line number, the type of line, and the line alarm status. The line type shows whether the line is J1, T3, E3, T1, E1, or OC-3 and shows the number of configured DS0s. This command also shows the primary line in an IMA line configuration and the line alarm status. Line alarm status categories include:

•Clear—Line OK

Alarm Information Signal

•Loss of Signal

Remote Out of Frame

•Out of Frame

Remote Out of Packet Frame

•Minor—Bad clock source

Loss of Multiframe

With Release 9.3.20, the dsplns command supports the Universal Router Module (URM) introduced on the IGX 8400 to provide IOS-based voice support and basic router functions. It consists of an embedded UXM with one internal ATM port and an embedded IOS-based router. The internal ATM port has no physical line interfaces. However, switch software resource management uses one entry from the line database for each active URM port. Consequently, the number of physical lines available in the node is reduced by the number of active URM ports.

The dsplns command accounts for the active URM ports. The dsplns command displays:

•The default display is a detailed display of lines used and includes a prompt for display of a line summary screen. The line summary screen reports the number of lines available in the node. The number of lines available is reduced by the number of active URM ports. The line summary screen can also be displayed by using the dsplns s command.

•The detailed display of lines used in the node. This is the same display provided by the dsplns command. However, it does not include a prompt for display of the line summary screen.

•The line summary calculates the number of lines available in the node. The number of lines available is the total IGX node lines minus the number of activated lines and the number of activated URM ports. The number of activated URM ports is reported in the "Active Router Ports" field.

Syntax

dsplns [s | d]

Parameters

Parameter

Description

s

Displays the line summary for an IGX node. The summary includes the number of active lines, the number of active router ports, and the number of available lines.

d

Displays detailed information for each line in an IGX node.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

dnln, dsptrks, upln, dspphyslns

Example (BPX)

Display circuit lines on the node.

dsplns

sw53 VT Cisco BPX 8620 9.3.2o Dec. 5 2000 09:29 GMT

Line Type Current Line Alarm Status
11.1 OC3 Clear - OK
11.8 OC3 Clear - OK

Last Command: dsplns
Example (IGX)

Display the lines within an IMA configuration. Line 5.1 designates the primary line (the line first added to the configuration) and (8) designates that eight lines are grouped together to form this IMA line. The overall IMA group alarm status is shown in the dsplns display. The dspphyslns command shows the alarm status on each of the 8 physical lines within the IMA group.

dsplns

sw225 TN StrataCom IGX 8420 9.3.l3 Feb. 2 2000 10:15 GMT

Line Type Current Line Alarm Status
5.1(8) E1/238 Clear - OK

Last Command: dsplns

Example (URM on IGX)

Display the line detail and summary information for an IGX node with two active Universal Router Module (URM) ports. The summary screen is displayed by answering "yes" (y) to the prompt. The number of "Available Lines" is the "Total Lines" minus the "Active Lines" and the "Active Router Ports".

dsplns

sw180 TN Cisco IGX 8420 9.3.2a July 20 2000 15:33 GMT

Line Type Current Line Alarm Status
4.1 T3/636 Clear - OK
4.2 T3/636 Clear - OK
5.3 OC3 Clear - OK
5.4 OC3 Clear - OK
7.1 E1/30 Clear - OK

This Command:dsplns

Display the summary lines output?
--------------------- Screen 2 --------------------

sw180 TN Cisco IGX 8420 9.3.2a July 20 2000 15:34 GMT

Line Summary:

Active Lines 5
Active Router Ports 2
Available Lines 57

Total Lines 64

Last Command:dsplns
Example (URM on IGX)

Display the detail for the activated lines on an IGX node with active URM ports.

dsplns d

sw180 TN Cisco IGX 8420 9.3.2a July 20 2000 15:33 GMT

Line Type Current Line Alarm Status
4.1 T3/636 Clear - OK
4.2 T3/636 Clear - OK
5.3 OC3 Clear - OK
5.4 OC3 Clear - OK
7.1 E1/30 Clear - OK

Last Command:dsplns d
Example (URM on IGX)

Display the line summary for an IGX node with active URM ports.

dsplns s

sw180 TN Cisco IGX 8420 9.3.2a July 20 2000 15:33 GMT

Line Summary:
Active Lines 5
Active Router Ports 2
Available Lines 57

Total Lines 64

Last Command:dsplns s

dsplnstathist (display statistics data for a line)

Displays a history of statistics configured as enabled for a selected line. This command displays the last five occurrences of the line statistic. You select the line statistic from the list displayed when you enter the command. Use the dsplnstatcnf to display the statistics enabled on the selected channel. Use cnflnstats to enable a statistic. (Note that dspclnstathist is the same as dsplnstathist.)

Syntax

dsplnstathist <line> <statistic number> <interval> <owner>

Parameters

Parameter

Description

<line>

Specifies the circuit line in the format slot.line. If the card set supports only one line, you can enter just the slot number.

<statistic number>

Specifies the type of statistic to enable/disable.

<interval>

Specifies the time interval of each sample. Range: 1-255 minutes

<owner>

Specifies the source of the configuration ("auto," "user", or "tftp").
You might need to enter "AUTO" in all capital letters.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX

Yes

Related Commands

cnflnstats, dsplnstatcnf

Example (BPX)

dsplnstathist 11.8

-------------------------------------SCREEN 1-----------------------------------
sw53 TN Cisco BPX 8620 9.3.m0 Dec. 12 2000 12:27 GMT

Line Statistic Types

1) Loss of Frames 39) Path FEBE
2) Loss of Signal 40) Section BIP8 Err. Secs.
19) HCS Errors 41) Line BIP24 Err. Secs.
28) YEL Transitions 42) Line FEBE Err. Secs.
30) Alarm Indication Signal 43) Path BIP8 Err. Secs.
31) Loss of Cell Delineation 44) Path FEBE Err. Secs.
32) Loss of Pointer 45) Section BIP8 Severely Err. Secs.
33) OC3 Path AIS 46) Section Sev. Err. Framing Secs.
34) OC3 Path YEL 47) Line BIP24 Severely Err. Secs.
35) Section BIP8 48) Line FEBE Severely Err. Secs.
36) Line BIP24 49) Path BIP8 Severely Err. Secs.
37) Line FEBE
38) Path BIP8

This Command: dsplnstathist 11.8

Continue? y

-------------------------------------SCREEN 2-----------------------------------
sw53 TN Cisco BPX 8620 9.3.m0 Dec. 12 2000 12:27 GMT

Line Statistic Types

50) Path FEBE Severely Err. Secs.
51) Line Unavailable Secs.
52) Line Farend Unavailable Secs.
53) Path Unavailable Secs.
54) Path Farend Unavailable Secs.
55) HCS Correctable Error
56) HCS Correctable Error Err. Secs

This Command: dsplnstathist 11.8

Statistic Type:

dspload (display connection loading)

Displays both the used and available bandwidth (both in the transmit and receive directions) for each trunk at the specified node. The "transmit" direction is from the node specified and to the node at the other end of the trunk. In the screen display, the numbers of disabled trunks appear in dim, reverse video on the screen.

The dspload display reflects the static load model stored by the node and used to determine the bandwidth available for new connections and reroutes. The display does not represent changes due to the dynamic utilization of the trunks. Some types of connections, such as voice connections using adaptive voice and data connections using Data Frame Multiplexing (DFM), suppress packets. In contrast, Frame Relay connections may generate additional packets when bandwidth permits.

When this command is executed at a local node in structured networks, the information displayed is for any node on the intra-domain lines belonging to the same domain. The node uses the terminating and through routed connections' calculated load to calculate the trunk load. The connection type (v, c, a, or d) or baud rate (9.6 Kbps, 56 56 Kbps, and so on) and other factors determine its basic load. The calculated trunk load may also be modified by using the cnfchutl command for connections that use VAD, DFM, or Frame Relay.

A certain amount of bandwidth is reserved for each trunk (when using cnftrk). The reserved bandwidth is available only for high priority packets (for example, PCC traffic). The node cannot route connections using this reserved bandwidth. The following loading, in packets per second, is calculated for each trunk in each direction:

total trunk capacity = current load + open space + statistical reserve

Syntax

dspload [nodename] [line number] [-cos]

Parameters

Parameter

Description

nodename

Specifies the local node.

line number

Specifies the physical line whose loading information is displayed.

-cos

Displays loading based on all cos band values.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

dsptrkutl, cnfcmparm

Example (IGX)

Display the load for all trunks that terminate on the current node.

dspload

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 11:54 PST

Trunk loads for node 'alpha'

Units Used Available Reserved Cmax In Use Cmax In Use
PLN Xmt Rcv Xmt Rcv Xmt Rcv Xmt Rcv XmtA RcvA XmtB RcvB
10 Pkts Pkts 1760 1744 8304 8320 600 600 0 0 0 0
14 Pkts Pkts 504 504 6896 6896 600 600 20 20 0 0

Last Command: dspload

Next Command:
Example (IGX)

Display the load for the trunk in slot 10 of the current node. If the dspload arguments include a trunk number, detailed information for each of the packet types on that line appears. Additional categories of information for Frame Relay loads on the trunk include Cmax In Use, Cmax Available, and Cmax Capacity.

dspload 10

sw151 TN SuperUser IGX 16 9.3 Apr. 13 2000 17:05 GMT

Configured Trunk Loading: TRK sw151 10--10 sw150

Load Type Xmt-p Rcv-p lcl
NTS 2016 2016 Conid In Use 11
TS 432 432 Conid Available 1760
Voice 208 208 Total Capacity 1771
BData A 0 0
BData B 0 0 Line type is Terrestrial
CBR 0 0 Line supports BData Load
rt-VBR 0 0 Line does not use ZCS
nrt-VBR 50 50
ABR 0 0 Traffic class:
Total In Use 2656 2656 V TS NTS FR FST CBR nrt-VBR ABR rt-VBR
Reserved 992 992
Available 76352 76352
Total Capacity 80000 80000

Last Command: dspload 10

Next Command:
Example (BPX)

Displays the load for trunk 1 in slot 1 of the current node based on load type (CBR, ABR, etc.). The trunk queue delay is also displayed if routing with delay is enabled. The dspload screen displays the bandwidth used by rt-VBR and nrt-VBR connections on a trunk.

dspload 1.1

sw203 TN SuperUser BPX 8620 9.3 Apr. 13 2000 17:05 GMT

Configured Trunk Loading: TRK sw203 1.1-- 1.1 sw242

Load Type Xmt-c Rcv-c lcl
NTS 0 0 Conid In Use 1068
TS 0 0 Conid Available 703
Voice 0 0 Total Capacity 1771
BData A 0 0
BData B 0 0 Trunk cost: 26
CBR 23100 23100 Trunk V Qdelay: 2.5 msec
rt-VBR 14300 14300 Trunk NTS Qdelay: 31.9 msec
nrt-VBR 14300 14300 Trunk end doesn't support complex gateway
ABR 18901 18901 Trunk is Terrestrial
Total In Use 56301 56301 Trunk does not use ZCS
Reserved 1000 1000 Trunk end doesn't support complex gateway
Available 38699 38690 Traffic class: V TS NTS FR FST CBR nrt-VBR ABR
Total Capacity 96000 96000 rt-VBR

Last Command: dspload 1.1

Next Command:
Example (BPX)

Displays the "cos based" load for trunk 1 in slot 1 of the current node. The -cos option displays the load categorized by bands. This is applicable and meaningful only when the Priority Bumping option is enabled.

dspload 1.1 -cos

sw67 TRM StrataCom BPX 8620 9.3.a7 Mar. 2 2000
13:52 GMT

Configured Trunk Loading: TRK sw67 1.1--13.1 sw66
Band: CoS Xmt-c Rcv-c
B0 : 0- 1 50 50 Conid In Use+Avail: 1+
1770= 1771
B1 : 2- 3 0 0 VPC conids: 0/256
B2 : 4- 5 0 0
B3 : 6- 7 0 0 Trunk is Terrestrial
B4 : 8- 9 0 0 Trunk supports cell routing
B5 :10-11 0 0 Trunk does not use ZCS
B6 :12-13 0 0 Trunk end doesn't support complex
gateway
B7 :14-15 0 0 Traffic: V TS NTS FR FST CBR
NRT-VBR ABR
Total In Use 50 50 RT-VBR
Reserved 5000 5000 Lcn/GwLcn bmap, oe: 00/00,00/00
Available 90950 90950
Total Capacity 96000 96000

Last Command: dspload 1.1 -cos

dsplog (display event log)

Displays the event log for a node. Events affecting the node are displayed in chronological order with the most recent events at the top of the log. The display includes a description of the event, the date and time of the event, and the alarm class of the event. A Continue? prompt is displayed if more than one screen is required to display all the log entries. Events generating alarms are marked Major or Minor, and events clearing alarms are marked Clear.

When you enter parameters with the dsplog command, they may all be used and entered in any order (except the <i> parameter, which cannot be used with <p>).

The dsplog entries show the virtual trunk number of a trunk, for example, slot.port.vtrk.

For UXM cards with ATM Forum IMA compliant trunks, a trunk is displayed in dsptrks as:

<slot>.<primary_port>x<num ports>

For example, an IMA trunk would display in the TRK column in the dsptrks display as:

5.1x4

In this case, 5.1x4 indicates an ATM Forum-compliant IMA trunk 5.4 which consists of four physical lines. To see all physical lines belonging to this IMA trunk, you can enter the dspphyslns command.

For IMA trunks, you can configure nonconsecutive physical lines.

To support ATM Forum compliant IMA trunks, the UXM card must have Model B firmware. (Model A firmware supports Cisco proprietary IMA protocol trunks, but not the ATM Forum-compliant trunks.)

The dsplog displays an SES interface shelf (feeder) when it is added to or removed from an IGX 8400 routing hub.

When you execute the dsplog command a message tells you when a Hitless Rebuild of the node occurred. See Example 2, which shows even log entries indicating that a hitless rebuild has occurred.

When a hitless rebuild occurs, event log entries indicating the occurrence of the rebuild will be logged. You view these event log entries by using dsplog.

Whenever the polling type changes, this event is logged in the event log (displayed by using dsplog command) on the switch.

Degraded Mode Conditions

Related to degraded mode conditions, which may occur when a node has exhausted its internal resources due to excessive messaging (among other possible causes) which leads the node to abort, the node either switches to the standby CC if it is available, or else it goes to into the degraded mode, assuming that this mode has been enabled. A node indicates that it is in degraded mode by: displaying degraded on the console screen; remote nodes generating degraded mode alarms; remote nodes showing the degraded mode as unreachable/degraded (UNDeg). The abort that put the node into degraded mode is logged in the switch software log, which you can display by using the dsplog command.

After a node enters the degraded mode, communication is halted with the rest of the network. All the network nodes immediately transition to communication break with the node in degraded mode.

The communication break generates a Minor Alarm for the network nodes. Each node inserts a special communication break message into the local event log (dsplog). For a locally attached Cisco WAN Manager, the message is also inserted into the Cisco WAN Manager event log. This message indicates the communication break was caused by a degraded mode at the remote node.

In addition to the log entries, a Communication Break Robust Alarm trap is generated to Cisco WAN Manager. This trap contains a new alarm type (code 997), which indicates the communication break was caused by a degraded mode at the remote node.

After a node exits the degraded mode, communication resumes with the rest of the network. All the network nodes clear communication break with the node.

The clearing of the communication break clears the Minor Alarm for the network nodes. Communication break clear messages are inserted into the local and Cisco WAN Manager event logs. A Communication break Robust Alarm trap is generated with the clear alarm type (code 998). The log messages and the robust trap for the communication break clear do not indicate that the communication break was caused by the node being in a degraded mode.

Display Fields: APS Alarms

The dsplog command displays SONET APS (Automatic Protection Switching) events and alarms shown in Table 4-22. APS alarms are also propagated to Cisco WAN Manager. APS events are indicated in the table by "Info" class type.

Table 4-22 APS Alarms Displayed with dsplog Command

Class

dsplog Text

Description

Minor

APS standard mismatch

In a two-card APS 1+1 configuration, one card is programmed for GR-253 and the other card is programmed for ITUT.

Minor

APS card missing

Indicates that either a BXM front card or back card supporting this APS line is detected as missing by a BXM.

Clear

APS OK

APS line is up with no alarms

Clear

APS deactivated

APS line is down

Minor

APS lines looped

APS line is looped

Minor

APS remote signal failure

A remote signal indicates that there is a problem with the far end signaling information in the K1K2 bytes.

Minor

APS channel mismatch

Can happen only in bidirectional mode and indicates that there is a problem with the underlying APS channel protocol. The receive K2 channel number does not equal the transmit K1 channel number.

Minor

APS protection switch byte failure

Protection switch byte failure or PSB. In bidirectional mode, indicates that there is an invalid K1 byte. The receive K1 request does not match the reverse request and is less than the transmit K1 request. In all modes, a PSB alarm indicates that K1/K2 protocol is not stable.

Minor

APS far end protection failure

Far end protection failure indicates that the far end's protection line is failing. When there is signal failure on the protection channel, the remote end sees Far End Protection Fail.

Minor

APS architecture mismatch¹

Architecture mismatch means that the APS configuration on one end of the line does not match the APS configuration at the other side of the line. Specifically, GR-253 at one end and ITUT at the other or 1+1 at one end and 1:1 at the other.

Info

APS Init/Clear/Revert

A BXM APS event indicating that the BXM APS has been initialized or a clear switch has occurred or a revert switch has occurred.

Info

Cannot perform a Clear/Revert switch

A BXM APS event indicating that the BXM APS was unable to perform a clear/revert switch.

Info

APS manual switch

A BXM APS event indicating that the BXM APS has performed a user requested manual switch.

Info

Cannot perform a manual switch

A BXM APS event indicating that the BXM APS was unable to perform a user requested manual switch.

Info

APS signal degrade LoPri switch

A BXM APS event indicating that the BXM APS performed a switch due to a low-priority signal degrade condition. An automatically initiated switch due to a "soft failure" condition resulting from the line BER exceeding a preselected threshold (cnfapsln).

Info

Cannot perform a signal degrade LoPri switch

A BXM APS event indicating that the BXM APS was unable to perform a switch due to a low-priority signal degrade condition.

Info

APS signal degrade HiPri switch

A BXM APS event indicating that the BXM APS performed a switch due to a high-priority signal degrade condition. An automatically initiated switch due to a "soft failure" condition resulting from the line BER exceeding a preselected threshold (cnfapsln).

Info

Cannot perform a signal degrade HiPri switch

A BXM APS event indicating that the BXM APS was unable to perform a switch due to a high-priority signal degrade condition.

Info

APS signal failure LoPri switch

A BXM APS event indicating that the BXM APS performed a switch due to a low-priority signal failure condition. An automatically initiated switch due to a signal failure condition on the incoming OC-N line including loss of signal, loss of frame, AIS-L defects, and a line BER exceeding 10-3.

Info

Cannot perform a signal failure LoPri switch

A BXM APS event indicating that the BXM APS was unable to perform a switch due to a low-priority signal failure condition.

Info

APS signal failure HiPri switch

A BXM APS event indicating that the BXM APS performed a switch due to a high-priority signal failure condition. An automatically initiated switch due to a signal failure condition on the incoming OC-N line including loss of signal, loss of frame, AIS-L defects, and a line BER exceeding 10-3.

Info

Cannot perform a signal failure HiPri switch

A BXM APS event indicating that the BXM APS was unable to perform a switch due to a high-priority signal failure condition.

Info

APS forced switch

A BXM APS event indicating that the BXM APS has performed a user requested forced switch.

Info

Cannot perform a forced switch.

A BXM APS event indicating that the BXM APS was unable to perform a user requested forced switch.

Info

APS lockout switch

A BXM APS event indicating that the BXM APS has performed a user requested switch that prevents switching from working line to protection line from taking place.

Info

Cannot perform a lockout switch

A BXM APS event indicating that the BXM APS was unable to perform a user requested lockout of protection switch.

Info

WTR switch

A BXM APS event indicating that the BXM APS performed a switch due to a Wait to Restore time-out. A state request switch due to the revertive switch back to the working line because the wait-to-restore timer has expired.

Info

Cannot perform a WTR switch

A BXM APS event indicating that the BXM APS was unable to perform a switch due to a WTR condition.

Info

Exercise switch

Not supported.

Info

Cannot perform an exercise switch

Not supported.

Info

Reverse switch

A BXM APS event indicating that the BXM APS performed a switch due to a reverse request. A state request switch due to the other end of an APS bidirectional line performing an APS switch.

Info

Cannot perform a reverse switch

A BXM APS event indicating that the BXM APS was unable to perform a switch due to a reverse switch request.

Info

No Revert switch

A BXM APS event indicating that the BXM APS performed a switch due to a Do Not Revert. A state request due to the external user request being cleared (such as a forced switch) while using non-revertive switching.

Info

Cannot perform a No Revert switch

A BXM APS event indicating that the BXM APS was unable to perform a switch due to a Do Not Revert switch request.

Minor

Standby line section trace

APS standby line alarm

Minor

Standby line path trace

APS standby line alarm

Minor

Standby line path yellow alarm

APS standby line alarm

Minor

Standby line path AIS

APS standby line alarm

Minor

Standby line loss of pointer

APS standby line alarm

Minor

Standby line loss of cell

APS standby line alarm

Minor

Standby line pclp yellow alarm

APS standby line alarm

Minor

Standby line plcp out of frame alarm

APS standby line alarm

Minor

Standby line yellow alarm

APS standby line alarm

Minor

Standby line alarm indication signal (AIS)

APS standby line alarm

Minor

Standby line out of frame alarm (LOF)

APS standby line alarm

Minor

Standby line loss of signal alarm (LOS)

APS standby line alarm

¹Architecture mismatch indicates that one side supports APS 1+1, and the other end of line is configured for 1:1, or the directional or revertive parameter does not match. Firmware cannot bring the two ends into compliance on the fly—the user must correct the configuration error.

¹There is no APS power supply alarm.

Syntax

dsplog <r> <p> <t> <i>

Parameters

Parameter

Description

<r>

Reverses the entry order in the log. Normally, the log displays the most recent entries at the top (newest to oldest. When you use the <r> parameter, entries are displayed oldest to newest.

<p>

Allows you to page through the log. Use "n" to go to the next page, "p" to go to the previous page, and "q" to quit the log.

<t>

Searches the log for an exact or closest timestamp.

The syntax is:
[p|i] [r] [t yyyy mm dd hh mm ss]

For example:
2000 3 16 8 46 58

For fields that you do not search, insert a zero. For example:
2000 3 16 0 0 0

<i>

This parameter is available only for service level privilege and above.

Displays all log entries, software error entries (dspswlog), and aborts (dspabortlog). Software error and abort entries are integrated by timestamp. This parameter can be used with either the <r> or <t> parameter.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

dspabortlog, dspswlog, clrogs, dspphyslns, dsptrks

Example (BPX)

Displays the log in reverse order, oldest entries first.

dsplog r

sw215 TRM Cisco BPX 8620 9.3.r7 Mar. 16 2000 08:49 PST

Least recent log entries (most recent at bottom)
Class Description Date Time
Info Log Cleared Date/Time Not Set
Info BCC 8 Restarted due to a Primary Revision Change Date/Time Not Set
Info CC 8 Starting rebuild due to Primary Revision Change Date/Time Not Set
Info Full Rebuild Occurred Date/Time Not Set
Info Invalid Login Attempt via Control Port (Local) Date/Time Not Set
Info BCC 8 downloading Flash with Revision 9.3.r7 Date/Time Not Set
Info ASM Inserted Date/Time Not Set
Info ASM 15 Activated Date/Time Not Set
Info Polling type changed to 2 Date/Time Not Set
Clear LMASM 15 Inserted - Activated Date/Time Not Set
Minor Fan #1 RPM out of range Date/Time Not Set
Minor Fan #2 RPM out of range Date/Time Not Set
Minor Fan #3 RPM out of range Date/Time Not Set

This Command: dsplog r
Example (BPX)

Displays the log in pages. Use "n" for next, "p" for previous, and "q" to quit out of the log.

dsplog p

sw215 TRM Cisco BPX 8620 9.3.r7 Mar. 16 2000 08:50 PST

Snapshot of log entries (most recent at top)
Class Description Date Time
Info AXIS shelf on TRK 2.1: Added 03/16/00 08:48:07
Info BCC 8 downloaded Flash with Revision 9.3.r7 03/16/00 08:47:58
Clear TRK 2.1 OK 03/16/00 08:47:51
Clear TRK 2.1 Activated 03/16/00 08:47:51
Info BNI-T3 2 Activated 03/16/00 08:47:51
Info BCC 8 downloading Flash with Revision 9.3.r7 03/16/00 08:47:25
Info Port 3.1 Activated 03/16/00 08:47:25
Info BCC 8 Restarted due to a Primary Revision Change 03/16/00 08:47:21
Clear LN 3.1 OK 03/16/00 08:47:21
Clear LN 3.1 Activated 03/16/00 08:47:21
Info ASI-T3 3 Activated 03/16/00 08:47:21
Clear Fan #3 RPM out of range 03/16/00 08:46:58
Clear Fan #2 RPM out of range 03/16/00 08:46:58

This Command: dsplog p
Continue direction - Next/Previous/Quit? (n/p/q)
Example (BPX)

Displays the log by timestamp.

dsplog t 2000 3 16 8 46 58

sw215 TRM Cisco BPX 8620 9.3.r7 Mar. 16 2000 08:52 PST

Snapshot of log entries (most recent at top)
Class Description Date Time
Clear Fan #3 RPM out of range 03/16/00 08:46:58
Clear Fan #2 RPM out of range 03/16/00 08:46:58
Clear Fan #1 RPM out of range 03/16/00 08:46:58
Info T3-2 3 Inserted 03/16/00 08:46:55
Info ASI-T3 3 Inserted 03/16/00 08:46:55
Info MMF-2 14 Inserted 03/16/00 08:46:53
Info BNI-155 14 Inserted 03/16/00 08:46:53
Info Time changed from: Date/Time Not Set 03/16/00 08:46:52
Info SMF-2 6 Inserted Date/Time Not Set
Info BNI-155 6 Inserted Date/Time Not Set
Info Name change from NODENAME to sw215 Date/Time Not Set
Info LM-BXM 11 Inserted Date/Time Not Set
Info BXM 11 Inserted Date/Time Not Set

This Command: dsplog t 2000 3 16 8 46 58
Example (BPX)

For service level privilege and above. Displays log entries, software error entries, and aborts. This example shows a dsplog screen where notification is given when high-priority mode is in use by the High Priority! string on the screen. The local event log indicates when the high-priority mode is entered and exited.

These strings are logged:

•Info User StrataCom logged in (Local High Priority)

•Info User StrataCom logged out (Local High Priority)

When in local high-priority mode, using the vt command to execute commands on another node provides a high-priority virtual terminal session. If you log into a control port at high priority, and then use the vt command to remotely log into another node with high priority VT, then both nodes will be at a high priority. The local node operates at the control port high priority, while the remote node serves you at a priority just below the network handler. When using the high-priority vt command, the screen shows High Priority VT and the local event log shows these strings.

•Info User StrataCom logged in (Virtual Terminal High Pri)

•Info User StrataCom logged out (Virtual Terminal High Pri)

Similar to the console screen, the Cisco WAN Manager and maintenance log show only the normal VT strings.

dsplog i

sw215 TRM Cisco BPX 8620 9.3.r7 Mar. 16 2000 09:00 PST

Most recent log entries (most recent at top)
Class Description Date Time
Info BCC 8 Restarted due to a Software Abort 03/16/00 08:59:38
Info Abort 9000000 Data:00000001 PC:30200A30/USR1 9.3.r7 03/16/00 08:59:19
Info User Cisco logged in (Local) 03/16/00 08:59:03
Info Hitless Rebuild Occurred 03/16/00 08:59:01
Info CC 8 Starting rebuild due to Software Abort 03/16/00 08:59:00
Info User Cisco logged in (Local) 03/16/00 08:59:02
Info User Service logged out (Local) 03/16/00 08:58:51
Info User Service logged in (Local) 03/16/00 08:58:34
Info User SuperUser logged out (Local) 03/16/00 08:58:29
Info User SuperUser logged in (Local) 03/16/00 08:57:22
Info Invalid Login Attempt via Control Port (Local) 03/16/00 08:57:03
Info User Cisco logged out (Local) 03/16/00 08:56:57
Info Error 1015 Data:DEADBEEF PC:302B74A6/USR1 9.3.r7 03/16/00 08:56:53

Last Command: dsplog i

dspmode (display mode)

Displays the mode of the card. The mode applies only to a UFM-U back card. The UFM-U back cards are the UFI-12V.35, UFI-12X.21, and UFI-4HSSI. A card mode is a combination of maximum port speeds and for specific port numbers. For a description of the UFM-U modes, see the UFM-U description in the Cisco IGX 8400 Series Reference.

Syntax

dspmode <slot>

Parameters

Parameter

Description

slot

Specifies the slot of the UFM-U card.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

Yes

IGX

Yes

Related Commands

cnffrport, cnfmode, dspmodes

Display Fields

Table 4-23 lists the maximum port speeds and active ports for each card mode.

Table 4-23 Card Modes for Unchannelized Back Cards

V.35 and X.21 Ports

HSSI Ports

Group A

Group B

Group C

Mode

1 2 3 4

5 6 7 8

9 10 11 12

1 2 3 4

1

3 3 3 3

3 3 3 3

3 3 3 3

8 8 8 8

2

8 - 8 -

8 - 8 -

8 - 8 -

16 - 16 -

3

10 - - -

10 - - -

10 - - -

16 - - -

4

8 - 8 -

3 3 3 3

3 3 3 3

5

10 - - -

3 3 3 3

3 3 3 3

6

8 - 8 -

8 - 8 -

3 3 3 3

7

10 - - -

8 - 8 -

3 3 3 3

8

10 - - -

10 - - -

3 3 3 3

9

10 - - -

8 - 8 -

8 - 8 -

10

10 - - -

10 - - -

8 - 8 -

11

3 3 3 3

8 - 8 -

3 3 3 3

12

3 3 3 3

3 3 3 3

8 - 8 -

13

3 3 3 3

10 - - -

3 3 3 3

14

3 3 3 3

3 3 3 3

10 - - -

15

8 - 8 -

3 3 3 3

8 - 8 -

16

3 3 3 3

8 - 8 -

8 - 8 -

17

8 - 8 -

10 - - -

3 3 3 3

18

8 - 8 -

3 3 3 3

10 - - -

19

3 3 3 3

8 - 8 -

10 - - -

20

3 3 3 3

10 - - -

8 - 8 -

21

10 - - -

3 3 3 3

8 - 8 -

22

10 - - -

3 3 3 3

10 - - -

23

3 3 3 3

10 - - -

10 - - -

24

8 - 8 -

10 - - -

8 - 8 -

25

8 - 8 -

8 - 8 -

10 - - -

26

10 - - -

8 - 8 -

10 - - -

27

8 - 8 -

10 - - -

10 - - -

Example (UFM-U on IGX)

Display the mode of the UFM-U in slot 13.

dspmode 13

sw180 TN SuperUser IGX 16 9.3 Apr. 13 2000 01:39 GMT

UFMU Card Mode Configuration

Slot Number Configured Mode Available Ports Currently Activated Ports

13 1 [111111111111] [100000000000]

Last Command: dspmode 13

Next Command:

dspmodes (display modes)

Displays the ports that are active with each mode of an unchannelized UFM. The mode applies only to a UFM-U back card. The UFM-U back cards are the UFI-12V.35, UFI-12X.21, and UFI-4HSSI.

A card mode is a combination of maximum port speeds and specific port numbers. Refer to the dspmode definition for the table that lists the maximum port speeds and active ports for each mode. For a description of the UFM-U modes, see the UFM-U description in the Cisco IGX documentation.

The dspmodes command takes no parameters. Also, note that only the first three modes apply to a UFI-4HSSI.

Syntax

dspmode

Related Commands

cnffrport, cnfmode, dspmode

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

Yes

BPX, IGX

Yes

Example (IGX)

Display the possible modes.

dspmodes

sw180 TN SuperUser IGX 16 9.3 Apr. 13 2000 01:39 GMT

UFMU Card Mode Configuration

Slot Number Configured Mode Available Ports Currently Activated Ports

13 1 [111111111111] [100000000000]

Last Command: dspmode 13

Next Command:

dspnds (display all nodes)

Displays the name, type, and alarm status of all nodes within the network of the node executing the command. The remote node alarm is provided. You can use the vt command to reach the remote node and obtain the alarm information.

If a node is in alarm, its name is highlighted and the alarm type (major/minor), is displayed. A major alarm will be a flashing word. A junction node is identified with "Yes" printed under the Jct column.

Syntax

dspnds [+n | -p | -d | domain]

Parameters

Parameter

Description

+n

Specifies the node number. Assigning a node number requires SuperUser privilege.

-p

Specifies that the display include the type of controller card in the node. The types are BCC, NPM, and so on.

-d

Specifies that the display include the type of node for each named node. The type is either "IGX" or "BPX."

Related Commands

dspnw

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Example

Display the alarm status of all nodes within the network.

dspnds

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 09:42 PST

NodeName Alarm
alpha MAJOR
beta MAJOR
gamma MAJOR

Last Command: dspnds

Next Command:

dspnebdisc (display neighbor discovery)

Displays the Neighbor Device's topology information. You can display the neighbor information for all ports on an interface card in a specified slot or for all ports on all interface cards in the switch.

Syntax

dspnebdisc <slot number>

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

BPX, IGX

No

Example (BPX)

Display the neighbor information for all ports in the BPX. The protocol field displays the protocol running on the BXM port.

sw52 TN Cisco BPX 8620 9.3.30 Jan. 30 2001 20:05 GMT
Node Neighbor Discovery
Port Enable State NbrIpAddress Protocol NbrIfName
2.2 No FAILED N/A X-LMI N/A
2.3 Yes FAILED 10.1.1.50 X-LMI atmVirtual.01.1.1.01

Last Command: dspnebdisc

Example (IGX)

Use the dspnebdisc command to display all the neighbor's information discovered by the IGX via the ELMI Neighbor Discovery procedure.

dspnebdisc

top TN Cisco IGX 8420 9.3.10 July 25 2000 09:31 GMT

Port Neighbor Discovery
Port Enable State IpAddress IfIndex/IfName
5.1 Yes ACTIVE 2.2.2.2 11
7.1 Yes INACTIVE 0.0.0.0 0
7.2 No ACTIVE 2.2.2.2 2
7.3 Yes ACTIVE 0.0.0.0 0
7.4 No INACTIVE 0.0.0.0 0
7.5 Yes ACTIVE 1.1.1.1 5
7.6 No INACTIVE 0.0.0.0 0
7.7 No INACTIVE 0.0.0.0 0
7.8 No INACTIVE 0.0.0.0 0
7.9 No ACTIVE 0.0.0.0 0
7.10 No INACTIVE 0.0.0.0 0
7.11 No ACTIVE 0.0.0.0 0

This Command: dspnebdisc
Example (UXM on IGX)

Display the neighbor information for all ports on all UXM cards in the IGX.

•Port 4.2 is failed, so the IpAddress is N/A and IfName is N/A even the ILMI is run on the card and Neighbor Discovery is configured to Yes.

•Port 4.3 is showing Neighbor's IpAddress 172.29.200.154 and IfName "ATM3/IMA0."

•Port 9.1 has the same situation as port 4.2.

•Port 9.4 does not configure ILMI to be run on the card. Slot 5 and 10 are not UXM cards.

dspnebdisc

igxf1 VT Cisco IGX 8420 9.3.10 July 26 2000 23:32 PST

Port Neighbor Discovery
Port Enable State IpAddress IfIndex/IfName
4.2 Yes FAILED N/A N/A
4.3 Yes ACTIVE 172.29.200.154 ATM3/IMA0
5.1 Yes INACTIVE 0.0.0.0 0
5.5 Yes INACTIVE 0.0.0.0 0
6.1 No ACTIVE 0.0.0.0 0
6.2 Yes INACTIVE 0.0.0.0 0
6.4 Yes INACTIVE 0.0.0.0 0
9.1 Yes FAILED N/A N/A
9.4 No ACTIVE N/A N/A
10.1 Yes INACTIVE 0.0.0.0 0
10.2 No ACTIVE 0.0.0.0 0
10.3 No INACTIVE 0.0.0.0 0

This Command: dspnebdisc

dspnode (display node)

Displays a summary of the interface shelves.

The dspnode command can isolate the shelf where an alarm has originated. For example, when you execute dspalms, the display indicates the number of shelves with alarms but does not identify the shelves. Therefore, execute dspnode on the IPX/BPX core switch shelf to determine which interface shelf generated the alarm.

To execute a command from an IGX/AF itself, you must either Telnet to the shelf or use a control terminal attached to the shelf.

Use the dspnode command to display the VSI controllers on a BPX node. You can display the control_VPI and control_VCI_start of the particular controller.

If the BPX cannot communicate LMI messages to its feeders, then the LMI status at the feeders must be maintained to keep the connections "active" to their external devices. If the BPX hub is flooded with network messages, then LMI/ILMI communication with its feeders may be interrupted. LMI normally runs a keep-alive between the hub and feeder. If the keep-alive fails, then the other end changes the status of all connections to "failed." If the outage is due to a network message flood, then it is desirable to override this mechanism to keep the connection status as "active."

Syntax

dspnode

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX, IGX/AF, BPX

Yes

Related Commands

addshelf, delshelf, dsptrks

Example (BPX)

Display information about the loopbacks on feeders to the BPX node.

dspnode

sazu TN StrataCom BPX 8620 9.3 Apr. 13 2000 11:11 GMT

BPX Interface Shelf Information

Trunk Name Type Alarm
10.2 sw157 IPX/AF MAJ (L)

Last Command: dspnode
Example (BPX)

dspnode

sw167 TN Cisco BPX 8620 9.3.2T Dec. 18 2000 21:47 PST

BPX 8620 Interface Shelf Information

Trunk Name Type Part Id Ctrl Id Control_VC Alarm
VPI VCIRange
1.1 sw250 AXIS - - - - MIN
12.1 sw156 IGX 8400/ - - - - OK

Last Command: dspnode

Example (BPX)

dspnode

bpx03 VT Cisco BPX 8620 9.3.2V Jan. 19 2001 08:37 PST

BPX 8620 Interface Shelf Information

Trunk Name Type Part Id Ctrl Id Control_VC Alarm
VPI VCIRange
5.1 SES1 AAL/5 2 2 0 40-54 OK
5.3 VSI VSI 1 1 0 40-54 OK

Last Command: dspnode
Example (IGX)

dspnode

sw150 TN Cisco IGX 8420 9.3.2Q Dec. 13 2000 08:01 PST

IGX Interface Shelf Information

Trunk Name Type Alarm
3.1 sw134 IGX 8400/AF OK

Last Command: dspnode

dspnw (display network)

Displays the network topology in tabular form. Alarms appear in a column, and added trunks (by addtrk) appear to the right to the node name. Each trunk entry shows the local back card slot number and the node name and back card slot number on the other end of the line.

Conventions:

•~ indicates that the trunk is a satellite line.

•Flashing entry indicates a failed line.

•Blinking node name indicates a node executing downloader software.

If the network has more nodes and trunk connections than are currently on the screen, a "Continue?" prompt appears. Press the Return key to display other parameters, or enter "n" to exit the command.

Syntax

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

Parameters

Parameter

Description

+b

Display only the lines that support bursty data.

-b

Display only the lines that do not support bursty data.

+z

Display only the lines that use ZCS encoding.

-z

Display only the lines that do not use ZCS encoding.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

dspnds, prtnw

Example (IGX)

dspnw

------------------------------------SCREEN 1-----------------------------------
sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 09:18 PST

NodeName Alarm Packet Line
sw197
6.1-4.1/sw94
sw290
13.1-4.2/sw69
sw167 Minor
4.2-4.2/sw147 9.1-9.1/sw69
4.1-4.1/sw147 3.1-2.1/sw69
2.1-2.1/sw58 2.2-2.2/sw58
2.3-2.3/sw58 14.1-11.1/sw64
11.2-12.2/sw69

This Command: dspnw

Continue? y

------------------------------------SCREEN 2-----------------------------------
sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 09:18 PST

NodeName Alarm Packet Line
sw64
11.1-14.1/sw167 2.1-6.1/sw147
2.3-6.3/sw147 2.5-6.5/sw147
1.2-1.2/sw94 5.1-14.5/sw94
5.2-14.6/sw94

This Command: dspnw

Continue? y

------------------------------------SCREEN 3-----------------------------------
sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 09:19 PST

NodeName Alarm Packet Line
sw147 Minor
4.1-4.1/sw167 2.1-3.1/sw94
6.1-2.1/sw64 6.3-2.3/sw64
6.5-2.5/sw64 1.3-3.1/sw69
4.2-4.2/sw167 10.2-11.2/sw94
9.2-11.2/sw69 2.2.1-2.2.1/sw94
2.2.2-2.2.2/sw94 2.2.3-2.2.3/sw94
2.2.4-2.2.4/sw94 5.2-14.3/sw94
2.2.23-2.2.23/sw94 2.2.5-2.2.5/sw94
2.2.6-2.2.6/sw94 2.2.12-2.2.12/sw94
2.2.24-2.2.24/sw94 2.2.7-2.2.7/sw94
2.2.8-2.2.8/sw94 2.2.9-2.2.9/sw94
2.2.10-2.2.10/sw94 2.2.11-2.2.11/sw94

This Command: dspnw

Continue? y

------------------------------------SCREEN 4-----------------------------------
sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 09:19 PST

NodeName Alarm Packet Line
sw147 Minor
2.2.13-2.2.13/sw94 2.2.14-2.2.14/sw94
2.2.15-2.2.15/sw94 2.2.16-2.2.16/sw94
2.2.17-2.2.17/sw94 2.2.18-2.2.18/sw94
2.2.19-2.2.19/sw94 2.2.20-2.2.20/sw94
2.2.21-2.2.21/sw94 2.2.22-2.2.22/sw94
2.2.30-2.2.30/sw94 2.2.25-2.2.25/sw94
2.2.26-2.2.26/sw94 2.2.27-2.2.27/sw94
2.2.28-2.2.28/sw94 2.2.29-2.2.29/sw94
2.2.31-2.2.31/sw94 2.2.32-2.2.32/sw94

This Command: dspnw

Continue? y

------------------------------------SCREEN 5-----------------------------------
sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 09:19 PST

NodeName Alarm Packet Line
sw58
1.3-1.3/sw69 10.1-9.1/sw94
3.1-2.1/sw94 9.1-11.1/sw69
2.1-2.1/sw167 2.2-2.2/sw167
2.3-2.3/sw167 12.1-11.1/sw94
5.1-3.3/sw150 1.2.1-1.2.1/sw69
1.2.2-1.2.2/sw69 1.2.3-1.2.3/sw69
1.2.4-1.2.4/sw69 1.2.5-1.2.5/sw69
1.2.6-1.2.6/sw69

This Command: dspnw

Continue? y

------------------------------------SCREEN 6-----------------------------------
sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 09:20 PST

NodeName Alarm Packet Line
sw150
5.3-4.1/sw69 14.2.6-4.6.6/sw69
8.1-5.2/sw94 14.2.3-4.6.3/sw69
14.2.1-4.6.1/sw69 14.3-4.8/sw69
14.2.2-4.6.2/sw69 14.2.7-4.6.7/sw69
14.2.4-4.6.4/sw69 14.2.5-4.6.5/sw69
3.3-5.1/sw58 14.2.13-4.6.13/sw69
14.2.8-4.6.8/sw69 14.2.9-4.6.9/sw69
14.2.10-4.6.10/sw69 14.2.11-4.6.11/sw69
14.2.12-4.6.12/sw69 14.2.14-4.6.14/sw69
9.1-14.1/sw94

This Command: dspnw

Continue? y

------------------------------------SCREEN 7-----------------------------------
sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 09:20 PST

NodeName Alarm Packet Line
sw94
3.1-2.1/sw147 1.2-1.2/sw64
4.1-6.1/sw197 2.1-3.1/sw58
9.1-10.1/sw58 14.3-5.2/sw147
14.5-5.1/sw64 2.2.23-2.2.23/sw147
11.1-12.1/sw58 1.1-2.3/sw69
2.2.1-2.2.1/sw147 2.2.2-2.2.2/sw147
2.2.3-2.2.3/sw147 2.2.4-2.2.4/sw147
11.2-10.2/sw147 5.2-8.1/sw150
14.6-5.2/sw64 2.2.12-2.2.12/sw147
2.2.9-2.2.9/sw147 2.2.5-2.2.5/sw147
2.2.6-2.2.6/sw147 2.2.7-2.2.7/sw147
2.2.8-2.2.8/sw147 14.1-9.1/sw150

This Command: dspnw

Continue? y

------------------------------------SCREEN 8-----------------------------------
sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 09:20 PST

NodeName Alarm Packet Line
sw94
3.1-2.1/sw147 1.2-1.2/sw64
4.1-6.1/sw197 2.1-3.1/sw58
9.1-10.1/sw58 14.3-5.2/sw147
14.5-5.1/sw64 2.2.23-2.2.23/sw147
11.1-12.1/sw58 1.1-2.3/sw69
2.2.1-2.2.1/sw147 2.2.2-2.2.2/sw147
2.2.3-2.2.3/sw147 2.2.4-2.2.4/sw147
11.2-10.2/sw147 5.2-8.1/sw150
14.6-5.2/sw64 2.2.12-2.2.12/sw147
2.2.9-2.2.9/sw147 2.2.5-2.2.5/sw147
2.2.6-2.2.6/sw147 2.2.7-2.2.7/sw147
2.2.8-2.2.8/sw147 14.1-9.1/sw150

Last Command: dspnw

dspnwip (display network IP interface)

Displays the IP address for each node in the network. The IP address is used to route TFTP messages transferring bulk statistics between the node and the WAN Manager Statistics Master.

Syntax

dspnwip

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnfwip

Example

Display network IP addresses.

dspnwip

axiom1 TN bootzilla IGX 32 9.3 Apr. 13 2000 18:18 GMT

Active Network IP Address: 169.134.90.106
Active Network IP Subnet Mask: 255.255.255.0

NodeName IP Address
axiom1 169.134.90.111
169.134.90.105
169.134.90.101
axiom2 169.134.90.102
axiom3 169.134.90.103
axiom1 169.134.90.106

Last Command: dspnwip

Next Command:

dspoamseg (display connection OAM segment status)

Displays the segment status of an Extended PVC (XPVC) segment in a hybrid AutoRoute (AR)-PNNI network.

The BPX 8600 supports an XPVC that spans over an AR-PNNI, or AR-PNNI-AR, hybrid network. The Cisco WAN Manager (CWM) is used to add, modify, and delete XPVCs. The CWM is also used to display XPVC connection details and monitor XPVC status.

The AR BXM and PNNI AXSM interface cards allow Enhanced UNI (EUNI) and Enhanced NNI (ENNI) port types that support XPVC segments. XPVC segments terminating on EUNI/ENNI ports are automatically programmed as "non-segment" endpoints. Non-segment endpoints do not loop back OAM segment loopback cells. With non-segment endpoints, OAM loopback cells are passed through to the adjacent network. Consequently, the CWM test procedures, such as test delay, cannot identify a faulty XPVC segment. When end-to-end XPVC testing fails, the faulty Automatic Routing Management or PNNI network and faulty XPVC segment must be identified.

You use the cnfoamseg command to change the segment status of an XPVC segment from "non-segment" to "segment". When the XPVC segment status is "segment", OAM segment loopback cells are looped back at the terminating EUNI/ENNI endpoint. This allows CWM test procedures to be executed on each XPVC segment to isolate a fault. You use the dspoamseg command to display the current segment status of an XPVC segment.

Syntax

dspoamseg <connection_channel>

Parameters

Parameter

Description

connection channel

Specifies the XPVC segment channel to be configured. Channel is specified in the following format:

slot.port.vpi.vci

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

Super Group

No

No

BPX

Yes

Yes

No

No

Related Commands

cnfoamseg

Example

Display the segment status for the XPVC segment channel 9.1.10.500.

dspoamseg 9.1.10.500

bpx1 TN Cisco BPX 8620 9.3.2X Feb. 7 2001 16:40 GMT

Connection segment status

The Connection is : Non-Segment

Last Command: dspoamseg 9.1.10.500

dspospace (display open space for a route)

Displays the open space for a connection route.

Syntax

dspospace <connection | group>

Parameters

Parameter

Description

<connection | group>

Specifies the connection.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

Yes

BPX, IGX

Yes

Example

Display the open space for the ATM Frame Relay connection 4.1.1. The line interface card is a UFM-8C.

dspospace 4.1.1

sw110 TN SuperUser IGX 16 9.3 Apr. 13 2000 19:11 GMT

Open Space for 4.1.1 Snapshot

Domain
Local: sw110 8--10.3sw86 6.2-- 6.1sw81
ms_cur_pkts: 524272 ms_cur_cells: 12576
sm_cur_pkts: 4368 sm_cur_cells: 11296

Last Command: dspospace 4.1.1

Next Command:

dsppcs (display port concentrator shelf)

Displays status and level information for either a specific Port Concentrator Shelf or all Port Concentrators attached to the node. When the command has a specific slot number for an argument, information appears for each concentrated link. The information for each concentrated link is:

•Status, where OK means the FRM-2 or FRP-2 is communicating with the PCS, and "Failed" means the FRM-2 or FRP-2 is not communicating with the PCS on the concentrated link.

–No Test means no test (tstpcs command) has occurred since last reset.

–Passed means the last PCS test (tstpcs command) detected no errors in the PCS hardware.

–Failed means the last PCS test (tstpcs command) detected errors in the PCS hardware.

–Testing means a test (tstpcs command) is in progress.

•FW Revision is the firmware revision of the PCS module.

•Boot PROM Date is the boot firmware date of PCS module.

•Boot PROM Revision is the boot firmware revision of PCS module.

The first example shows the results when a slot number is specified. When the command executes without a specified slot, a general status statement and the firmware revision for each port appear as shown in the second example.

Syntax

dsppcs [slot]

Parameters

Parameter

Description

slot

Specifies slot associated with the ports you want to display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-3

No

No

BPX, IGX

No

Related Commands

cnffrport, dspfrcport, dspfrcbob, dspportstats

Example

Display PCS information for port 6.

dsppcs 6

singha TN SuperUser IGX32 9.2 July 7 1997 14:04 GMT

Detailed Port Concentrator Display For FRP in slot 6

Link Number: 1 Link Number: 3
Status: Failed Status: OK
Test Status: No Test Test Status: Passed
FW Revision: FW Revision: P3
Boot PROM Date: Boot PROM Date: 11/9/95
Boot PROM Revision: Boot PROM Revision: P3

Link Number: 2 Link Number: 4
Status: Failed Status: OK
Test Status: No Test Test Status: Passed
FW Revision: FW Revision: P3
Boot PROM Date: Boot PROM Date: 11/9/95
Boot PROM Revision: Boot PROM Revision: P3

Last Command: dsppcs 6

Next Command:

Example

Display information for all Port Concentrator Shelves.

dsppcs

singha TN SuperUser IGX32 9.2 July 7 1997 14:02 GMT

Port Concentrator Status

Slot.Port Status FW Revision
6.1 Failed
6.2 Failed
6.3 OK P3
6.4 OK P3

Last Command: dsppcs

Next Command:

dspphyslnerrs (display physical line errors)

Displays the accumulated line error counts, by failure type, for the specified physical lines. If no slot number is entered with the command, a one-line summary of errors for al physical lines at the local node is displayed. If a slot number is entered with the command, a detailed analysis is displayed.

The summary for physical lines 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 a loopback or port test has occurred since the statistics were last cleared.

The clrphyslnerrs command resets all error counts to 0. Table 4-24 contains a brief description of each error.

Physical line statistics are displayed on the dspphyslnstats, dspphyslnstathist, and dspphyslnerrs screens. These commands accept only physical line numbers (that is, slot.port).

Table 4-24 Errors in the dspphyslnerrs Display

Line Type

Error

Explanation

All except ATM

Bipolar errors

Number of times two consecutive pulses have the same polarity (AMI coding only).

Frame slips

Number of times a frame is discarded to re-establish synchronization.

Out of frames

Number of times a loss-of-frame synchronism is detected on this circuit line.

Loss of signal

Number of times the signal level at the circuit line input went below the minimum acceptable level.

Frame bit errors

Number of times the frame bit failed to alternate (frame error).

CRC errors

Number of times the generated CRC character did not match the received CRC character (applies only if CRC checking is enabled).

Out of MFrames

Number of times a multiframe synch error was detected (E1 lines only).

AIS - 16

Number of times the Alarm Information Signal (Blue signal) was received.

Only ATM

Out of Frames

Number of times a momentary loss of-DS3 frame alignment was detected.

Loss of sync (XX)

Number of times a loss of DS3 frame alignment lasting more than XX seconds was detected.

Packet Error

Number of CRC errors for a packet address.

Line Code Errors

Number of B3ZS code errors detected.

P-bit Parity Errors

Number of parity errors for the DS3 parity bit (P-bit) sequence.

C-bit Parity Errors

Number of parity errors for the DS3 control bit (C-bit) sequence.

Comm Fails

Number of BCC failed to communicate to the other node.

Loss of signal

Number of times the signal level at the trunk line input went below the minimum acceptable level.

Only ATM

AIS (BLU)

Number of times the Alarm Information Signal (Blue signal) was received.

Out of MFrames

Number of times a loss-of-frame synchronism in the DS3 multiframe alignment was detected.

Remote Oof

Number of times the DS3 remote alarm (indicating remote end was out of frame alignment) was received.

Syntax

dspphyslnerrs [slot | slot.port]
or
dspphyslnerrs <slot.port> (for virtual physical lines)

Parameters

Parameter

Description

[slot | slot.port]

Specifies a physical line for the error display.
For a specific single physical line: slot
For multi-physical line cards: slot.port

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

clrphyslnerrs, prtphyslnerrs

Example

Display a summary of all physical line errors at the local IGX node.

dspphyslnerrs

sw150 VT Cisco IGX 8420 9.3.2T Dec. 18 2000 22:28 PST

Total Statistical Errors

Code Out of LossOf Frame CRC
PHYSLN Errors Frames Signal BitErs Errors
3.1 - 0 0 0 0
3.3 - 0 0 0 0
5.3 0 0 0 0 0
8.1 0 0 0 0 0
9.1 0 0 0 0 0
14.2 0 0 0 0 0
14.3 0 0 0 0 0

Last Command: dspphyslnerrs
Example

Display a detailed description of the errors for physical line 4.2 (an OC-3 trunk).

dspphyslnerrs 4.2

sw108 VT Cisco IGX 8420 9.3.2o Dec. 5 2000 10:25 GMT

PHYSLN 4.2 Clear - OK Clrd:12/04/00 17:26:01
Statistical Alarm Count ETS Status Integrated Alarm Count ETS Status
Bipolar Err 0 0 Loss of Sig (RED) 0 -
Out of Frms 0 0 AIS (BLU) 0 -
Loss of Sig 0 0 Out of Frms (RED) 0 -
Frame BitErrs 0 0 Remote (YEL) 0 -
CRC Err 0 0 Loss of Cell 0 -
Line Code Errs 0 0 Loss of Pointer 0 -
P-bit Parity Errs 0 0 Path AIS 0 -
C-bit Parity Errs 0 0 Path Yellow 0 -
BIP-8 Code Errs 0 0 Frame Sync 0 -
Frame Sync Errs 0 0 Remote Framing 0 -
Rmt Path Trace 0 -
Rmt Section Trace 0 -

Last Command: dspphyslnerrs 4.2
Example

Display a detailed description of the errors for physical line 3.1 (an E3/T3 trunk).

dspphyslnerrs 3.1

sw150 VT Cisco IGX 8420 9.3.2T Dec. 18 2000 22:29 PST

PHYSLN 3.1 Clear - OK Clrd:12/18/00 20:52:07
Statistical Alarm Count ETS Status Integrated Alarm Count ETS Status
Out of Frms 0 0 Loss of Sig (RED) 0 -
Loss of Sig 0 0 AIS (BLU) 0 -
Frame BitErrs 0 0 Out of Frms (RED) 0 -
CRC Err 0 0 Remote (YEL) 0 -
Line Code Errs 0 0 Loss of Cell 0 -
P-bit Parity Errs 0 0 Loss of Pointer 0 -
BIP-8 Code Errs 0 0 Frame Sync 0 -
Frame Sync Errs 0 0 Remote Framing 0 -
Rmt Path Trace 0 -

Last Command: dspphyslnerrs 3.1
Example

Display a detailed description of the errors for physical line 11.3 (an E1 trunk).

dspphyslnerrs 11.3

sw228 TN SuperUser IGX 16 9.3 Apr. 13 2000 17:59 PST

PHYSLN 11.3 Status:Clear - OK
Clrd: 08/27/97 13:33:15
Type Count ETS Status Type Count ETS Status
Out of Frms 0 0 Loss of Sig (RED) 0 -
Loss of Sig 0 0 AIS (BLU) 0 -
Frame BitErrs 0 0 Out of Frms (RED) 0 -
CRC Err 0 0 Frm Err Rate(RED) 0 -
AIS-16 (RED) 0 -
Rmt Oof (YEL) 0 -
Loss of Cell 1 -

Last Command: dphyslnerrs 11.3
Example

Display a detailed description of the errors for physical line 7.1 (a T1 IMA trunk).

dspphyslnerrs 7.1

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 14:44 PST

PHYSLN 7.1 Clear - OK Clrd:01/14/01 17:50:01
Statistical Alarm Count ETS Status Integrated Alarm Count ETS Status
Bipolar Err 0 0 Loss of Sig (RED) 0 -
Out of Frms 0 0 AIS (BLU) 0 -
Loss of Sig 0 0 Out of Frms (RED) 0 -
Frame BitErrs 0 0 Rmt Oof (YEL) 0 -
CRC Err 0 0 Loss of Cell 0 -
Line Code Errs 0 0 IMA Line Failures 0 -
P-bit Parity Errs 0 0 IMA Failures 0 -
C-bit Parity Errs 0 0
BIP-8 Code Errs 0 0
Frame Sync Errs 0 0

Last Command: dspphyslnerrs 7.1

dspphyslns (display physical line status)

Displays a list of physical lines and their current alarm status. at the local IGX node. If no slot number is entered, a one-line summary for all physical lines at the local node is displayed. If a specific slot number is entered with the command, all physical lines on that slot only are displayed.

You can configure nonconsecutive physical lines on the same IMA trunk or line. Use dspphyslns to display all physical lines belonging to a particular IMA trunk.

IMA physical line alarms are maintained differently than other types of logical (physical and virtual) trunks. Each IMA trunk has a configurable number of retained links. If the number of non-alarmed lines is less than the number of retained links, the logical (physical and virtual) trunks on the IMA trunk or line are placed into major alarm.

To illustrate this, a line has the current configuration: IMA trunks 4.5-8, with the number of retained links set at 2. If 4.5 and 4.6 go into LOS (loss of signal), physical line alarms are generated for these two physical lines. The logical trunks 4.5-8 do not go into alarm because the two retained links are still healthy. In this situation, the bandwidth on the logical trunk is adjusted downward to prevent cell drops, and the connections on those trunks are rerouted. If a third line goes into alarm, the logical trunk is then failed.

Syntax

dspphyslns [slot]

Parameters

Parameter

Description

[slot]

Specifies the slot number.

Display Fields

Parameter

Description

PHYSLN

The physical line number.

Type

Physical line type.

Current Line Alarm Status

The alarm status is one of the following values:

•Clear—OK (Alarm Information Signal)

•LOS (Loss of Signal)

•Out of Frame (Remote Out-of-Packet Frames)

•Minor—Bad clock source (Loss of Multiframe)

Trk/Line

Shows the primary line or trunk number. The primary line or trunk is the first line or trunk added to an IMA configuration using the upln or uptrk command.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

dspphyslnstathist, clrphyslnerrs, prtphyslnerrs

Example

Display a summary of physical lines.

dspphyslns

sw150 VT Cisco IGX 8420 9.3.2T Dec. 18 2000 22:12 PST

PHYSLN Type Current Line Alarm Status Trk/Line
3.1 E3/530 Clear - OK 3.1-T
3.3 E3/530 Clear - OK 3.3-T
5.3 OC3 Clear - OK 5.3-T
8.1 T3/636 Clear - OK 8.1-T
9.1 OC3 Clear - OK 9.1-T
14.2 OC3 Clear - OK 14.2.1(14)
14.3 OC3 Clear - OK 14.3-T

Last Command: dspphyslns
Example

Display the physical lines on card 4.

dspphyslns 4

sw108 VT Cisco IGX 8420 9.3.2J Oct. 31 2000 13:35 GMT

PHYSLN Type Current Line Alarm Status Trk/Line
4.2 OC3 Clear - OK 4.2-T
4.4 OC3 Clear - OK 4.4-T

Last Command: dspphyslns 4
Example

Display a detailed description of the type and current alarm status for the physical lines in slot 7 (a T1 IMA trunk).

dspphyslns 7

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 14:16 PST

PHYSLN Type Current Line Alarm Status Trk/Line
7.1 T1/24 Clear - OK 7.1(8)-T
7.2 T1/24 Clear - OK 7.1(8)-T
7.3 T1/24 Clear - OK 7.1(8)-T
7.4 T1/24 Clear - OK 7.1(8)-T
7.5 T1/24 Clear - OK 7.1(8)-T
7.6 T1/24 Clear - OK 7.1(8)-T
7.7 T1/24 Clear - OK 7.1(8)-T
7.8 T1/24 Clear - OK 7.1(8)-T

Last Command: dspphyslns 7
Example

Display a detailed description of the type and current alarm status for the physical lines in slot 5.

dspphyslns 5

sw225 TN StrataCom IGX 8420 9.3.l3 Feb. 2 2000 10:11 GMT

PHYSLN Type Current Line Alarm Status Trk/Line
5.1 E1/30 Clear - OK 5.1(8)-L
5.2 E1/30 Clear - OK 5.1(8)-L
5.3 E1/30 Clear - OK 5.1(8)-L
5.4 E1/30 Clear - OK 5.1(8)-L
5.5 E1/30 Clear - OK 5.1(8)-L
5.6 E1/30 Clear - OK 5.1(8)-L
5.7 E1/30 Clear - OK 5.1(8)-L
5.8 E1/30 Clear - OK 5.1(8)-L

Last Command: dspphyslns 5

dspphyslnstatcnf (display statistics enabled for a physical line)

Displays statistics (see Table 4-25)configured as enabled for a selected line on a UXM card by the cnfphyslnstats command, by Cisco WAN Manager, or by node features. (The older command dsplnstatcnf is an alias for the IGX only.)

The Owner column identifies who or what set the statistic. If the Owner column shows "Automatic," the node's features set the statistic. If the node name appears under Owner, Cisco WAN Manager set the statistic. If the user name appears under Owner, the cnfchstats command executed from the command line interface set the statistic.

Table 4-25 Physical Line Statistics

Statistic Object

Stat Type

Card Type

Definition

Total Cells Received

Logical

UXM/BXM

All

Total Cells Transmitted

Logical

UXM/BXM

All

LOS Transitions

Physical

UXM/BXM

All

LOF Transitions

Physical

UXM/BXM

All

Line AIS Transitions

Physical

UXM/BXM

T3/E3/SONET

Line RDI (Yellow) Transitions

Physical

UXM/BXM

T3/E3/SONET

Uncorrectable HCS Errors

Physical

UXM

T3/E3/SONET

Correctable HCS Errors

Physical

UXM

T3/E3/SONET

HCS Errors

Physical

BXM

T3/E3/SONET

Line Code Violations, ES, and SES

Physical

BXM

T3/E3

Line Parity (P-bit]) Errors, ES, and SES

Physical

BXM

T3

Path Parity (C-bit) Errors, ES, and SES

Physical

BXM

T3

Far End Block Errors

Physical

BXM

T3

Framing Errors and SES

Physical

BXM

T3/E3

Unavailable Seconds

Physical

BXM

T3/E3

PLCP LOF and SES

Physical

BXM

T3

PLCP YEL

Physical

BXM

T3

PLCP BIP-8, ES, SES

Physical

BXM

T3

PLCP FEBE, ES, SES

Physical

BXM

T3

PLCP FOE, ES, SES

Physical

BXM

T3

PLCP UAS

Physical

BXM

T3

LOC Errors

Physical

UXM/BXM

E3/SONET

LOP Errors

Physical

UXM/BXM

SONET

Path AIS Errors

Physical

UXM/BXM

SONET

Path RDI Errors

Physical

UXM/BXM

SONET

Section BIP-8 Counts, ES, and SES

Physical

UXM/BXM

SONET

Line BIP-24 Counts, ES, and SES

Physical

UXM/BXM

SONET

Line FEBE Counts, ES, and SES

Physical

UXM/BXM

SONET

Section SEFS

Physical

UXM/BXM

SONET

Line UAS and FarEnd UAS

Physical

UXM/BXM

SONET

Clock Loss Transitions

Physical

UXM

T1/E1

Frame Loss Transitions

Physical

UXM

T1/E1

Multiframe Loss

Physical

UXM

T1/E1

CRC Errors

Physical

UXM

T1/E1

BPV

Physical

UXM

T1

Frame Bit Errors

Physical

UXM

E1

Unknown VPI/VCI Count

Physical

UXM/BXM

All

Errored LPC Cell Count

Physical

UXM

All

Non-zero GFC Cell Count

Physical

UXM/BXM

Max Differential Delay

Physical

UXM

T1/E1

Uncorrectable HEC errors

Physical

UXM

All

Cell Hunt Count

Physical

UXM

T1/E1

Bandwidth Changed Count

Physical

UXM

T1/E1

Receive CLP=0 Cell Count

Logical

UXM/BXM

All

Receive CLP=1 Cell Count

Logical

UXM/BXM

All

Receive CLP=0 Cell Discard

Logical

UXM/BXM

All

Receive CLP=1 Cell Discard

Logical

UXM/BXM

All

Transmit CLP=0 Cell Count

Logical

UXM/BXM

All

Transmit CLP=1 Cell Count

Logical

UXM/BXM

All

Receive OAM Cell Count

Logical

UXM/BXM

All

Transmit OAM Cell Count

Logical

UXM/BXM

All

Receive RM Cell Count

Logical

UXM/BXM

All

Transmit RM Cell Count

Logical

UXM/BXM

All

For Each Traffic Type:

(V,TS,NTS, ABR, rt-VBR,
nrt-VBR, CBR, BdatB, BdatA, HP)

Cells Served

Logical

UXM/BXM

All

Maximum Qbin Depth

Logical

UXM/BXM

All

Cells Discarded Count

Logical

UXM/BXM

All

The dspphyslnstatcnf command also provides additional physical line statistics (which support the ATM Forum-compliant IMA protocol. See these the IMA physical line statistics under the command cnfphyslnstats in Table 3-28 on page 3-306.

Syntax

dspphyslnstatcnf <line>

Parameters

Parameter

Description

<line>

Specifies the line.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX

Yes

Related Commands

cnfphyslnstats

Example

Display statistics enabled for a physical line on an IGX.

dspphyslnstatcnf 5.1

sw180 VT Cisco IGX 8420 9.3.p7 Dec. 12 2000 12:38 GMT

Statistics Enabled on Physical Line 5.1

Statistic Samples Interval Size Peaks Owner
----------------------------------- ------- -------- ---- ----- ----------
1) Bipolar Violations 60 0 4 NONE AUTO
3) Out of Frames 60 0 4 NONE AUTO
4) Losses of Signal 60 0 4 NONE AUTO
5) Frames Bit Errors 60 0 4 NONE AUTO
6) CRC Errors 60 0 4 NONE AUTO
29) Line Code Violations 60 0 4 NONE AUTO
32) Line Parity Errors 60 0 4 NONE AUTO
35) Path Parity Errors 60 0 4 NONE AUTO
41) BIP-8 Code Violations 60 0 4 NONE AUTO
98) Frame Sync Errors 60 0 4 NONE AUTO

Last Command: dspphyslnstatcnf 5.1

dspphyslnstathist (display statistics data for a physical line)

Displays a history of statistics configured as enabled for a selected physical line on an active IMA trunk or line on a UXM card.

This command displays the last five occurrences of the line statistic for a physical line on an active IMA trunk on a UXM card. Select the line statistic from the list displayed when you first enter this command. Use the dspphyslnstatcnf to display the statistics enabled on the selected channel. Use cnfphyslnstats to enable a statistic.

Syntax

dspphyslnstathist <line> <statistic number> <interval> <owner>

Parameters

Parameter

Description

<line>

Specifies the circuit line in the format slot.line. If the card set supports only one line, you can enter just the slot number.

<statistic number>

Specifies the type of statistic to enable/disable.

<interval>

Specifies the time interval of each sample. Range: 1-255 minutes

<owner>

Specifies the source of the configuration ("auto," "user", or "tftp"). You might need to enter "AUTO" in capital letters.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

IGX

Yes

Related Commands

cnfphyslnstats, dspphyslnstatcnf

Example

Display statistics for a physical line on an IGX.

dspphyslnstathist 5.1

------------------------------------SCREEN 1----------------------------------
sw180 VT Cisco IGX 8420 9.3.p7 Dec. 12 2000 13:04 GMT

Line Statistic Types

1) Bipolar Violations 37) Severely Err Secs - Path
3) Out of Frames 38) Severely Err Frame Secs
4) Losses of Signal 40) Unavail. Seconds
5) Frames Bit Errors 41) BIP-8 Code Violations
6) CRC Errors 42) Cell Framing Errored Seconds
29) Line Code Violations 43) Cell Framing Sev. Err Secs.
30) Line Errored Seconds 44) Cell Framing Sec. Err Frame Secs
31) Line Severely Err Secs 45) Cell Framing Unavail. Secs.
32) Line Parity Errors 62) Total Cells Tx to line
33) Errored Seconds - Line 69) Total Cells Rx from line
34) Severely Err Secs - Line 98) Frame Sync Errors
35) Path Parity Errors 141) FEBE Counts
36) Errored Secs - Path 143) Cell Framing FEBE Err Secs

This Command: dspphyslnstathist 5.1

Continue? y

------------------------------------SCREEN 2----------------------------------
sw180 VT Cisco IGX 8420 9.3.p7 Dec. 12 2000 13:06 GMT

Line Statistic Types

144) Cell Framing FEBE Sev. Err. Secs. 202) Section BIP8 Err. Secs.
151) Yellow Alarm Transition Count 203) Line BIP24 Err. Secs.
152) Cell Framing Yel Transitions 204) Line FEBE Err. Secs.
153) AIS Transition Count 205) Path BIP8 Err. Secs.
193) Loss of Cell Delineation 206) Path FEBE Err. Secs.
194) Loss of Pointer 207) Section BIP8 Severely Err. Secs.
195) OC3 Path AIS 208) Section Sev. Err. Framing Secs.
196) OC3 Path YEL 209) Line BIP24 Severely Err. Secs.
197) Section BIP8 210) Line FEBE Severely Err. Secs.
198) Line BIP24 211) Path BIP8 Severely Err. Secs.
199) Line FEBE 212) Path FEBE Severely Err. Secs.
200) Path BIP8 213) Line Unavailable Secs.
201) Path FEBE 214) Line Farend Unavailable Secs.

This Command: dspphyslnstathist 5.1

Continue? y

------------------------------------SCREEN 3----------------------------------
sw180 VT Cisco IGX 8420 9.3.p7 Dec. 12 2000 13:06 GMT

Line Statistic Types

215) Path Unavailable Secs. 228) INVMUX: Tx Failure Count
216) Path Farend Unavailable Secs. 229) INVMUX: Rx Failure Count
217) HCS Uncorrectable Error
218) HCS Correctable Error
219) INVMUX: line violations
220) INVMUX: Severely Err. Secs.
221) INVMUX: Farend Sev. Err. Secs.
222) INVMUX: Unavailable Secs.
223) INVMUX: Farend Unavail Secs.
224) INVMUX: Tx Unusable Seconds
225) INVMUX: Rx Unusable Seconds
226) INVMUX: Farend Tx Unusable Secs.
227) INVMUX: Farend Rx Unusable Secs.

This Command: dspphyslnstathist 5.1

Statistic Type:

dspport (display port)

Displays the status of all ports in a node, all ports on a specified interface card, or the detailed information for a single specified port. The more specific the port address in the command, the more detail is provided. For a full description of the port configuration parameters, see the cnfport command. (The dspport command is the same as the alias command dspfrport).

Sample commands:

dspport
Display the states of all ports in the node.

dspport 8
Display the port states for interface card in slot 8.

dspport 8.1
Display the configuration for port 1 of the interface card in slot 8.

dspport 2.1.1
Display the configuration for virtual port 1.1 of the BXM card in slot 2.

Syntax

dspport <slot.port> [.vport]

Parameters

Parameter

Description

slot.port

Specifies the physical slot and port of the Frame Relay or ATM card set.
Range: 1-4

[.vport]

Optional virtual port number (BXM only).

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

BPX, IGX

Yes

Related Commands

cnfport, upport, dnport, addport, delport

Example (BPX)

Display port 13.1 of a BXM.

dspport 13.1

BPX02 TN Cisco BPX 8620 9.3.3W Aug. 13 2001 12:35 PDT

Port: 13.1 [ACTIVE ] Bandwidth/AR BW: 353208/353208
Interface: LM-BXM CAC Override: Enabled
VPI Range: 0 - 255 CAC Reserve: 0
Type: UNI %Util Use: Disabled
Shift: SHIFT ON HCF (Normal Operation)
SIG Queue Depth: 640 Port Load: 0 %
F4-F5 Mapping: Yes F4-F5 Used Chans: 0
Protocol: NONE Protocol by Card: No

Last Command: dspport 13.1

Next Command:
Example (IGX)

Display port 9.3 of a UXM.

cnfport 9.3 N i 10 16 y y 30 3 4 N y 200 0 y y y

bolger TN Cisco IGX 8430 9.3.3o May 16 2001 09:33 PST

Port: 9.3 [ACTIVE ]
Interface: OC3 CAC Override: Disabled
Type: UNI %Util Use: Disabled
Speed: 353208 (cps) GW LCNs: 200
SIG Queue Depth: 640 Reserved BW: 0 (cps)
Alloc Bandwidth: 353208 (cps) VC Shaping: Enabled
Protocol: ILMI Protocol run on the card: Yes
VPI.VCI: 10.16 Advertise Intf Info: Yes
ILMI Polling Enabled Y
Trap Enabled Y
T491 Polling Interval 30
N491 Error Threshold 3
N492 Event Threshold 4

Last Command: cnfport 9.3 N i 10 16 y y 30 3 4 N y 200 0 y y y

Example (IGX)

Display port for IMA port 8.1 of a UXM.

dspport8.1

bolger TN Cisco IGX 8430 9.3.3o May 15 2001 18:42 PST

Port: 8.1 [FAILED ]
IMA Port Grp: 1-2
Interface: E1-IMA CAC Override: Disabled
Type: NNI %Util Use: Enabled
Speed: 8905 (cps) GW LCNs: 200
SIG Queue Depth: 640 Reserved BW: 0 (cps)
Alloc Bandwidth: 8905 (cps) VC Shaping: Enabled
Protocol: ILMI Protocol run on the card: Yes
VPI.VCI: 10.16 Advertise Intf Info: Yes
ILMI Polling Enabled Y
Trap Enabled Y
T491 Polling Interval 30
N491 Error Threshold 3
N492 Event Threshold 4

Last Command: dspport 8.1
Example (IGX)

Display port for UFM-C port 8.1

dspport 8.1

sw176 TN Cisco IGX 8420 9.3.a5 Apr. 27 2001 09:54 PDT

Port: 8.1 [FAILED]
Interface: T1D Configured Clock: 320 Kbps
Clocking: None Measured Rx Clock: None

Port ID - Min Flags / Frames 1
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec
DE Threshold 100 % N391 Full Status Poll 6 cyl
Signalling Protocol Cisco LMI EFCI Mapping Enabled No
Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Channel Speed 64
N393 Monitored Events Count 4 Line Number 1
Communicate Priority No Channel Range 1-5
Upper/Lower RNR Thresh 75%/ 25%

Last Command: dspport 8.1
Example (IGX)

Display port 9 for UXM card; shows all ports on slot 9.

dspport 9

bolger TN Cisco IGX 8430 9.3.3m Apr. 27 2001 09:09 PST

Port configuration for ATM 9

Port Chan Speed Interface State Protocol Type
2 2 353208 (cps) OC3 INACTIVE NONE UNI
3 3 353208 (cps) OC3 ACTIVE ILMI UNI

Last Command: dspport 9
Example (IGX)

Display port 25.1 of a URM.

dspport 25.1

bolger TN Cisco IGX 8430 9.3.3o May 16 2001 09:37 PST

Port: 25.1 [ACTIVE ]
Interface: INTERNAL CAC Override: Disabled
Type: UNI %Util Use: Enabled
Speed: 353208 (cps) GW LCNs: 200
SIG Queue Depth: 640 Reserved BW: 0 (cps)
Alloc Bandwidth: 353208 (cps) VC Shaping: Enabled
Protocol: ILMI Protocol run on the card: Yes
VPI.VCI: 10.16 Advertise Intf Info: Yes
ILMI Polling Enabled Y
Trap Enabled Y
T491 Polling Interval 30
N491 Error Threshold 3
N492 Event Threshold 4

Last Command: dspport 25.1
Example (IGX)

Display port 9.1 on a UFM-U card.

dspport 9.1

sw108 TN Cisco IGX 8420 9.3.c2 May 16 2001 16:38 GMTPort 9.1 [ACTIVE ]
Interface V35 DCE Configured Clock 256 Kbps
Clocking Normal Measured Rx Clock 256 Kbps

Port ID 0 Min Flags / Frames 1
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec
DE Threshold 100 % N391 Full Status Poll 6 cyl
Signalling Protocol None EFCI Mapping Enabled No
Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Interface Control Template
N393 Monitored Events Count 4 Lead CTS DSR DCD
Communicate Priority No State ON ON ON
Last Command: dspport 9.1

dspportids (display port IDs)

Displays port IDs. The port ID is a user-specified identifier for a particular Frame Relay port where several virtual circuits share the same physical interface. The port ID can be any numeric value in the range 1-1024.

The command for specifying a port ID is cnffrport. Note that a Port Concentrator does not use port IDs.

Syntax

dspport IDs

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

BPX, IGX

No

Related Commands

cnffrport

Example

Display the port IDs throughout the network.

dspportids

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 15:55 PST

Frame Relay Port IDs
ID Node
7 alpha |
9 alpha |

Last Command: dspportids

Next Command:

dspportq (display ARM port queue configuration)

Displays the Automatic Routing Management 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.

Syntax

dspportq <slot.port>[<.vport>]

Parameters

Parameter

Description

slot.port[.vport]

Specifies the card slot, physical, and optional virtual port number (BXM only).

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

BPX, IGX

No

Related Commands

cnfportq

Display Parameters (ASI)

Parameter

Description

nni/uni

Specifies whether the cell header format is NNI or UNI. Default: UNI

cbr queue parms

Specifies the CBR queue parameters of depth, cbr-hi, cbr-lo, and efci.
Range for depth: 0 to 24000
Range for all others: 0 to 100%

nrt-vbr queue parms

Specifies the nrt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci.
Range for depth: 0 to 24000
Range for all others: 0 to 100%

rt-vbr queue parms

Specifies the rt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci.
Range for depth: 0 to 24000
Range for all others: 0 to 100%

ubr/abr queue parms

Specifies the ABR queue parameters of depth, abr-hi, abr-low, and efci.
Range for depth: 0 to 24000
Range for all others: 0 to 100%

Display Parameters (UXM)

Parameter

Description

nni/uni

Specifies whether the cell header format is NNI or UNI. Default: UNI

cbr queue parms

Specifies the CBR queue parameters of depth, cbr-hi, cbr-lo, and efci.
Range for depth: 0 to 97250
Range for all others: 0 to 100%

nrt-vbr queue parms

Specifies the nrt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci.
Range for depth: 0 to 97250
Range for all others: 0 to 100%

rt-vbr queue parms

Specifies the rt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci.
Range for depth: 0 to 97250
Range for all others: 0 to 100%

ubr/abr queue parms

Specifies the ABR queue parameters of depth, abr-hi, abr-low, and efci. UBR traffic shares this queue with the ABR traffic.
Range for depth: 0 to 97250
Range for all others: 0 to 100%

Display Parameters (BXM)

Parameter

Description

nni/uni

Specifies whether the cell header format is NNI or UNI. Default: UNI

cbr queue parms

Specifies the CBR queue parameters of depth, cbr-hi, cbr-lo, and efci.
Range for depth: 0 to 97250
Range for all others: 0 to 100%

nrt-vbr queue parms

Specifies the nrt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci.
Range for depth: 0 to 97250
Range for all others: 0 to 100%

rt-vbr queue parms

Specifies the rt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci.
Range for depth: 0 to 97250
Range for all others: 0 to 100%

ubr/abr queue parms

Specifies the ABR queue parameters of depth, abr-hi, abr-low, and efci. UBR traffic shares this queue with the ABR traffic.
Range for depth: 0 to 97250
Range for all others: 0 to 100%

Example (IGX)

Display the port queue configuration for IGX port 5.3.

dspportq 5.3

sw180 TN Cisco IGX 8420 9.3.o9 Dec. 5 2000 14:05 GMT

Port: 5.3 [ACTIVE ]
Interface: OC3
Type: UNI
Speed: 353208 (cps) Alloc Bandwidth: 353208 (cps)

CBR Queue Depth: 600 rt-VBR Queue Depth: 5000
CBR Queue CLP High Threshold: 80% rt-VBR Queue CLP High Threshold: 80%
CBR Queue CLP Low Threshold: 60% rt-VBR Queue CLP Low Threshold: 60%
CBR Queue EFCI Threshold: 60% rt-VBR Queue EFCI Threshold: 60%
nrt-VBR Queue Depth: 5000 ABR Queue Depth: 20000
nrt-VBR Queue CLP High Threshold: 80% ABR Queue CLP High Threshold: 80%
nrt-VBR Queue CLP Low Threshold: 60% ABR Queue CLP Low Threshold: 60%
nrt-VBR Queue EFCI Threshold: 60% ABR Queue EFCI Threshold: 20%

Last Command: dspportq 5.3
Example (BPX)

Display the port queue configuration for BPX port 11.1.

dspportq 11.1

sw53 VT Cisco BPX 8620 9.3.2o Dec. 5 2000 14:07 GMT

Port: 11.1 [ACTIVE ]
Interface: LM-BXM
Type: UNI
AR Bandwidth: 353208 (cps)
SVC Queue Pool Size: 0
QUEUE DEPTH CLP HI CLP LO EFCI VC SHAPE
/EPD
CBR 600 80% 60% 60% DISABLED
rt-VBR 5000 80% 60% 60% DISABLED
nrt-VBR 5000 80% 60% 60% DISABLED
UBR/ABR 20000 80% 60% 20% DISABLED

Last Command: dspportq 11.1

dspports (display ports)

Displays either all of the ports on the node, or if a slot is specified, all of the ports on the specified slot.

Syntax

dspports [<slot>]

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

BPX, IGX

No

Related Commands

dspport, addport, upport, dnport, delport

Example (BPX)

Display the status of all the ports on the BXM card.

dspports

sw167 TN Cisco BPX 8620 9.3.2T Dec. 19 2000 21:19 PST

Port States
Port State
5.1 ACTIVE
5.2 ACTIVE
6.3 ACTIVE
6.4 ACTIVE
6.5 ACTIVE
6.6 ACTIVE
6.7 ACTIVE
6.8 ACTIVE

Last Command: dspports
Example (BPX)

Display the status of BXM card slot 6.

dspports 3

sw167 TN Cisco BPX 8620 9.3.2T Dec. 19 2000 21:22 PST

Port configuration for ATM 64

Port VPI Min/Max Bandwidth Interface State Protocol Type
6.3 0 / 255 353208 (cps) LM-BXM ACTIVE NONE UNI
6.4 0 / 255 353208 (cps) LM-BXM ACTIVE NONE UNI
6.5 0 / 255 353208 (cps) LM-BXM ACTIVE NONE UNI
6.6 0 / 255 353208 (cps) LM-BXM ACTIVE NONE UNI
6.7 0 / 255 353208 (cps) LM-BXM ACTIVE NONE UNI
6.8 0 / 255 353208 (cps) LM-BXM ACTIVE NONE UNI
Last Command: dspports 6

dspportstatcnf (display statistics enabled for FR port)

Displays statistics configured as enabled for a selected Frame Relay port.

These are the statistics set by the cnfportstats command, by Cisco WAN Manager, or by node features. The owner column shows what set the statistic. If the Owner column is Automatic, it was set by feature; if it is node name, it was set by Cisco WAN Manager; if it is user, it was set with the cnfportstats command.

Syntax

dspportstatcnf <line>

Parameters

Parameter

Description

<line>

Specifies the port in the form slot.port: do NOT enter the DLCI.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

IGX

Yes

Related Commands

cnfportstats

Example

Display port statistics enabled.

dspportstatcnf 8.1

gamma Cisco WAN Manager YourID Rev: 9.3 Apr. 13 2000 13:47 PDT

Statistics Enabled on Port 8.1

Statistic Samples Interval Size Peaks Owner
------------------------------------ ------- -------- ---- ----- ----------
Frames Received 5 60 4 1 M beta
Frames Received 5 60 4 1 M beta
Bytes Received 5 60 4 1 M beta

Last Command: dspportstatcnf 8.1

dspportstathist (display statistics history for an FR port)

Displays a history of statistics configured as enabled for a selected Frame Relay port. This command displays the data for the last five occurrences of the port statistic.You select the port statistic from the list displayed when you first enter the command. Use cnfportstats to enable a statistic.

Syntax

dspportstathist <line> <statistic number> <interval> <owner>
Parameters

Parameter

Description

<line>

Specifies the circuit line in the format slot.line. If the card set supports only one line, you can enter just the slot number.

<statistic number>

Specifies the type of statistic to enable/disable.

<interval>

Specifies the time interval of each sample. Range: 1-255 minutes

<owner>

Specifies the source of the configuration ("auto," "user", or "tftp"). You might have to enter owner "AUTO" or "USER" in all capital letters.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

IGX

Yes

Related Commands

cnfportstats, dspportstatcnf

Example (UXM on IGX)

dspportstathist 4.1

sw144 TN Cisco IGX 8420 9.3.10 Date/Time Not Set

Port Statistic Types

34) PORT: Unknwn VPI/VCI cnt 48) PORT: # of cells rcvd
35) VI: Cells rcvd w/CLP=1 49) PORT: # of cells xmt
36) VI: OAM cells received 51) INVMUX: HEC cell errors
37) VI: Cells tx w/CLP=1 52) INVMUX: LCP cell errors
39) VI: Cells received w/CLP=0 53) INVMUX: Cell Hunt Count
40) VI: Cells discarded w/CLP=0 54) INVMUX: Bandwidth Change Count
41) VI: Cells discarded w/CLP=1 55) ILMI: Get Req PDUs rcvd
42) VI: Cells transmitted w/CLP=0 56) ILMI: GetNxt Req PDUS rx
43) VI: OAM cells transmitted 57) ILMI: GetNxt Req PDUS xmt
44) VI: RM cells received 58) ILMI: Set Req PDUs rcvd
45) VI: RM cells transmitted 59) ILMI: Trap PDUs rcvd
46) VI: Cells transmitted 60) ILMI: Get Rsp PDUs rcvd
47) VI: Cells received 61) ILMI: Get Req PDUs xmt

This Command: dspportstathist 4.1

Continue?

sw144 TN Cisco IGX 8420 9.3.10 Date/Time Not Set

Port Statistic Types

62) ILMI: Get Rsp PDUs xmt 75) LMI: Invalid LMI PDU length rcvd
63) ILMI: Set Req PDUs xmt 76) LMI: Unknown LMI PDUs rcvd
64) ILMI: Trap PDUs xmt 77) LMI: Invalid LMI IE rcvd
65) ILMI: Unknwn PDUs rcvd 78) LMI: Invalid Transaction IDs
66) LMI: Status messages xmt 79) INVMUX: Unavailable Seconds
67) LMI: Updt Status msgs xmt 80) INVMUX: Near End Fail Count
68) LMI: Status Ack msgs xmt 81) INVMUX: Last Proto Fail Code
69) LMI: Status Enq msgs rcvd 82) INVMUX: Slowest Link
70) LMI: Status Enq msgs xmt 86) Q2 Cells Tx
71) LMI: Status msgs rcvd 87) Tx Q2 CDscd
72) LMI: Updt Status msg rcvd 88) Egr CRx Q2
73) LMI: Status Ack msg rcvd 89) Q3 Cells Tx
74) LMI: Invalid LMI PDUs rcvd 90) Tx Q3 CDscd

This Command: dspportstathist 4.1

Continue?

sw144 TN Cisco IGX 8420 9.3.10 Date/Time Not Set

Port Statistic Types

91) Egr CRx Q3 113) Q11 Cells Tx
101) Q7 Cells Tx 114) Tx Q11 CDscd
102) Tx Q7 CDscd 115) Egr CRx Q11
103) Egr CRx Q7 116) Q12 Cells Tx
104) Q8 Cells Tx 117) Tx Q12 CDscd
105) Tx Q8 CDscd 118) Egr CRx Q12
106) Egr CRx Q8 119) Q13 Cells Tx
107) Q9 Cells Tx 120) Tx Q13 CDscd
108) Tx Q9 CDscd 121) Egr CRx Q13
109) Egr CRx Q9 122) Q14 Cells Tx
110) Q10 Cells Tx 123) Tx Q14 CDscd
111) Tx Q10 CDscd 124) Egr CRx Q14
112) Egr CRx Q10 125) Q15 Cells Tx

This Command: dspportstathist 4.1

Continue?

sw144 TN Cisco IGX 8420 9.3.10 Date/Time Not Set

Port Statistic Types

126) Tx Q15 CDscd
127) Egr CRx Q15

This Command: dspportstathist 4.1

Statistic Type:
Example (BXM on BPX)

dspportstathist 12.3

rogue TN Cisco BPX 8620 9.3.10 July 14 2000 11:43
GMT

Port Statistic Types

1) Unknown VPI/VCI count 24) Get Request PDUs transmitted
8) Number of cells received 25) Get Response PDUs transmitted
9) Number of cells rcvd w/CLP set 26) Trap PDUs transmitted
12) Number of cells xmitted 27) Unknown ILMI PDUs Received
13) OAM cells received count 28) Status messages transmitted
15) Number of cells xmitted w/CLP set 29) Update Status messages
transmitted
18) Get Request PDUs received 30) Status Acknowledge msgs
transmitted
19) Get Next Request PDUS received 31) Status Enquiry messages received
20) Get Next Request PDUS transmitted 32) Status Enquiry mesgs transmitted
21) Set Request PDUs received 33) Status messages received
22) Trap PDUs received 34) Update Status messages received
23) Get Response PDUs received 35) Status Acknowledge messages
received

This Command: dspportstathist 12.3

Continue?

rogue TN Cisco BPX 8620 9.3.10 July 14 2000 11:44
GMT

Port Statistic Types

36) Invalid LMI PDUs received received 48) Last unknown VPI/VCI pair
37) Invalid LMI PDU length received 49) Tx Cells Served on Qbin 0
38) Unknown LMI PDUs received 50) Tx Cells Discarded on Qbin 0
39) Invalid LMI IE received 51) Tx Cells Received on Qbin 0
40) Invalid Transaction IDs 52) Tx Cells Served on Qbin 1
41) Number of cells rcvd w/clp 0 53) Tx Cells Discarded on Qbin 1
42) Number of cells dscd w/clp 0 54) Tx Cells Received on Qbin 1
43) Number of cells dscd w/clp set 55) Tx Cells Served on Qbin 2
44) Number of cells tx w/clp 0 56) Tx Cells Discarded on Qbin 2
45) Tx OAM cell count 57) Tx Cells Received on Qbin 2
46) Rx RM cell count 58) Tx Cells Served on Qbin 3
47) Tx RM cell count 59) Tx Cells Discarded on Qbin 3

This Command: dspportstathist 12.3

Continue?

rogue TN Cisco BPX 8620 9.3.10 July 14 2000 11:44
GMT

Port Statistic Types

60) Tx Cells Received on Qbin 3 87) Tx Cells Received on Qbin 12
76) Tx Cells Served on Qbin 9 88) Tx Cells Served on Qbin 13
77) Tx Cells Discarded on Qbin 9 89) Tx Cells Discarded on Qbin 13
78) Tx Cells Received on Qbin 9 90) Tx Cells Received on Qbin 13
79) Tx Cells Served on Qbin 10 91) Tx Cells Served on Qbin 14
80) Tx Cells Discarded on Qbin 10 92) Tx Cells Discarded on Qbin 14
81) Tx Cells Received on Qbin 10 93) Tx Cells Received on Qbin 14
82) Tx Cells Served on Qbin 11 94) Tx Cells Served on Qbin 15
83) Tx Cells Discarded on Qbin 11 95) Tx Cells Discarded on Qbin 15
84) Tx Cells Received on Qbin 11 96) Tx Cells Received on Qbin 15
85) Tx Cells Served on Qbin 12
86) Tx Cells Discarded on Qbin 12

This Command: dspportstathist 12.3

Statistic Type:
Example (BXM on BPX)

dspportstathist 12.3

rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:43 GMT

Port Statistic Types

1) Unknown VPI/VCI count 24) Get Request PDUs transmitted
8) Number of cells received 25) Get Response PDUs transmitted
9) Number of cells rcvd w/CLP set 26) Trap PDUs transmitted
12) Number of cells xmitted 27) Unknown ILMI PDUs Received
13) OAM cells received count 28) Status messages transmitted
15) Number of cells xmitted w/CLP set 29) Update Status messages transmitted
18) Get Request PDUs received 30) Status Acknowledge msgs transmitted
19) Get Next Request PDUS received 31) Status Enquiry messages received
20) Get Next Request PDUS transmitted 32) Status Enquiry mesgs transmitted
21) Set Request PDUs received 33) Status messages received
22) Trap PDUs received 34) Update Status messages received
23) Get Response PDUs received 35) Status Acknowledge messages received

This Command: dspportstathist 12.3

Continue?

rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:44 GMT

Port Statistic Types

36) Invalid LMI PDUs received received 48) Last unknown VPI/VCI pair
37) Invalid LMI PDU length received 49) Tx Cells Served on Qbin 0
38) Unknown LMI PDUs received 50) Tx Cells Discarded on Qbin 0
39) Invalid LMI IE received 51) Tx Cells Received on Qbin 0
40) Invalid Transaction IDs 52) Tx Cells Served on Qbin 1
41) Number of cells rcvd w/clp 0 53) Tx Cells Discarded on Qbin 1
42) Number of cells dscd w/clp 0 54) Tx Cells Received on Qbin 1
43) Number of cells dscd w/clp set 55) Tx Cells Served on Qbin 2
44) Number of cells tx w/clp 0 56) Tx Cells Discarded on Qbin 2
45) Tx OAM cell count 57) Tx Cells Received on Qbin 2
46) Rx RM cell count 58) Tx Cells Served on Qbin 3
47) Tx RM cell count 59) Tx Cells Discarded on Qbin 3

This Command: dspportstathist 12.3

Continue?

rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:44 GMT
Port Statistic Types

60) Tx Cells Received on Qbin 3 87) Tx Cells Received on Qbin 12
76) Tx Cells Served on Qbin 9 88) Tx Cells Served on Qbin 13
77) Tx Cells Discarded on Qbin 9 89) Tx Cells Discarded on Qbin 13
78) Tx Cells Received on Qbin 9 90) Tx Cells Received on Qbin 13
79) Tx Cells Served on Qbin 10 91) Tx Cells Served on Qbin 14
80) Tx Cells Discarded on Qbin 10 92) Tx Cells Discarded on Qbin 14
81) Tx Cells Received on Qbin 10 93) Tx Cells Received on Qbin 14
82) Tx Cells Served on Qbin 11 94) Tx Cells Served on Qbin 15
83) Tx Cells Discarded on Qbin 11 95) Tx Cells Discarded on Qbin 15
84) Tx Cells Received on Qbin 11 96) Tx Cells Received on Qbin 15
85) Tx Cells Served on Qbin 12
86) Tx Cells Discarded on Qbin 12

This Command: dspportstathist 12.3
Statistic Type:

dspportstats (display Frame Relay port statistics)

Displays a summary of port statistics for a Frame Relay port. Statistics include the data byte count in the transmit and receive directions and error counts associated with the port. The display indicates the date and time the statistics were cleared and the amount of time since the node last cleared the statistics. Bytes transmitted indicates the amount of data transmitted from the port to the user device. Bytes received indicates the amount of data received at the port from the user device.

Corrupted statistics result from channel/port loopbacks or port tests. A "yes" in this field indicates that loopback or port tests have occurred since the statistics were last cleared. The statistics for User-to-Network Interface (UNI) ports (connections to user devices) are displayed with one screen.

Syntax

dspportstats <slot.port> [interval]

Parameters

Parameter

Description

slot

Specifies the Frame Relay card set slot.

port

Specifies the port on the back card.
Range (FRI-V.35 or FRI-X.21 back cards): 1-4
Range (channelized ports FRI-T1): 1-24
Range (channelized ports FRI-E1): 1-31
Range (UFI back card): 1-250

[interval]

Specifies the refresh interval time for data.
Range: 1-60 seconds
Default: 1 second

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

Yes

Related Commands

clrportstats

The dspportstats command also displays the statistics as shown in Table 4-26:

Table 4-26 UNI Port Statistics for Frame Relay

Frame Errors

LMI Statistics

Miscellaneous Statistics

Invalid CRC

Status Enquiries Received

Average TX Port Q

Invalid Alignment

Status Transmitted

FECN Frames

Invalid Frame Length

Update Transmit

FECN Ratio (%)

Invalid Frame Format

Invalid Requests

BECN Frames

Unknown DLCIs

Sequence # Mismatches

BECN Ratio (%)

Last Unknown DLCI

Timeouts

Resource Overflow

Signaling Protocol

DE Frames Dropped (Egress)

Network to Network (NNI) ports require two screens to display all the parameters. The first screen is the same as described previously for UNI ports—you display the second screen by responding with a "y" for yes to the Continue? prompt. The second screen compares receive LMI statistics (see Table 4-27) with transmit LMI statistics. The LMI receive statistics are repeated from the middle column of the first screen and displayed again so you can compare them. This table lists the usage statistics in screen 2.

Table 4-27 LMI Statistics for Frame Relay

LMI Receive Protocol Stats

LMI Transmit Protocol Statistics

Status Enquiries Received

Status Inquiries Transmitted

Status Enquiries Transmitted

Status Received

Asynchronous Status Transmitted

Asynchronous Status Received

Sequence # Mismatches

Sequence # Mismatches

Timeouts

Timeouts

Invalid Frames

Signaling Protocol

The command displays frame error (see Table 4-28), LMI (see Table 4-29), miscellaneous statistics (see Table 4-30), and CCLM statistics (see Table 4-31).

Table 4-28 Frame Error Statistics

Statistics

Description

CRC Errors

Based on a CRC CCITT 16-bit frame check sequence, which is a cyclic redundancy check. If the frame received at a port has an incorrect CRC, it is flagged as a CRC error, and the frame is discarded.

Receive Frame CRC Errors (Ingress). Provides a count of the number of frames received from the attached equipment in which the CRC calculated by the IGX does not match the CRC provided by the attached equipment in the last two octets of the frame.

Any frame received with an incorrect CRC is discard by the network.

However, the IGX does not wait to receive the entire frame before starting to packetize the frame and send it through the network. As long as the frame header format is valid (see Invalid Format Receive Frames statistic) and the DLCI field in the frame header is recognized (see Receive Frames Undefined DLCI Count statistic below), packets containing the beginning of the frame are created—(one start-of-frame (SOF) packet and subsequent middle-of-frame (MOF) packets)—and sent as soon as possible.

If the frame is short and if there are other packets already waiting to be sent, the detection of the CRC error will cause all the packets of the frame to be discarded. However, if the frame is long and there is no congestion in the ingress VC queue, some packets are sent through the network before the CRC error is detected. As soon as the CRC error is detected, any portion of the frame that has not yet been sent is discarded. In particular, no end of frame (EOF) packet is ever sent. At the far end, when an SOF packet arrives that does not immediately follow an EOF packet, the incomplete frame is discard and counted in the PVC statistic of Transmit Frames Discarded. If the CRC is incorrect because of a bit error in the DLCI field in the frame header, then the error will also be recorded as a Receive Frame with Undefined DLCI unless the errored DLCI is also configured on the port. This statistic is a subset of the Frames Received statistic.

Alignment error

Frame was not an integral number of bytes.

Receive Frame Alignment Errors (Ingress). This statistic provides a count of the number of frames received from the attached equipment in which the total frame length is not an integral number of octets. Any frame received with an incorrect alignment is discarded by the network.

However, the IGX does not wait to receive the entire frame before starting the packetize the frame and send it to the network. As long as the frame header format is valid (See Invalid Format Receive Frames statistic), and the DLCI field in the frame header is recognized (see Receive Frames Undefined DLCI Count statistic), packets containing the beginning of the frame are created—(one start-of-frame (SOF) packet and subsequent middle-of-frame (MOF) packets)—and sent as soon as possible.

If the frame is short or if there are other packets already waiting to be sent, the detection of the alignment error will cause all the packets of the frame to be discarded. However, if the frame is long and there is no congestion in the ingress VC queue, some packets are sent through the network before the alignment error is detected. As soon as the alignment error is detected, any portion of the frame that has not yet been sent is discarded. In particular, no end-of-frame (EOF) packet is ever sent.

When the next frame arrives, a new SOF packet is sent, etc. At the far end, when an SOF packet arrives that does not immediately follow an EOF packet, the incomplete frame is discarded and counted in the PVC statistic of Transmit Frames Discarded. This statistic is a subset of the Frames Received statistic.

Frame length errors

Frames <5 bytes or> 4096 bytes.

Illegal Length Receive Frames (Ingress). Provides a count of the number of frames received from the attached equipment in which the total frame length is either too short or too long. To be accepted, a frame must be at least five octets, but no more than 4510 octets long, including the header and frame check sequence (FCS, or CRC) octets. Any frame received with an invalid length is discard by the network. A frame that is too short is immediately detected and discarded. For a frame that is too long, the IGX does not wait to receive the entire frame before starting to packetize the frame and send it through the network.

As long as the frame header format is valid (see Invalid Format Receives Frames statistic), and the DLCI field in the frame header is recognized (see Receive Frames Undefined DLCI Count statistic below), packets containing the beginning of the frame are created—(one start of frame (SOF) packet, and sent as soon as possible. Since the frame is very long, it is very likely that some packets are sent through the network before the length error is detected. As soon as the length error is detected, any portion of the frame that has not yet been sent is discarded. In particular, no end-frame (EOF) packet is ever sent. When the next frame arrives, a new SOF packet arrives that does not immediately follow an EOF packet, the incomplete frame is discarded and counted in the PVC statistic of Transmit Frames Discarded. This statistic is a subset of the Frames Received statistic.

Frame format errors

Occurs when either of the least significant bits in the first two bytes of the Frame Relay header are set incorrectly. These two bytes are the frame's address field. The first byte's least significant bit is defined to be a zero, meaning that there is a second byte to the address. The second byte's least significant bit is defined to be a one, meaning this is the last byte of the address because it's a two byte address field.

Invalid Format Receive Frames (Ingress). Provides a count of the number of frames received from the attached equipment in which the Extended Address (EA) bits (the least significant bit in each of the two Frame Relay header octets) is incorrect. The IGXIGX must see a r0s as the least significant bit of the first octet and a r1s as the least significant bit of the second octet. Any frame received with incorrect EA bits is discarded immediately. This statistic is a subset of the Frames Received statistic.

Unknown DLCIs

Occurs when a frame arrives at a Frame Relay port and the DLCI has not been mapped and the frame is discarded.

Received Frames Undefined DLCI Count (Ingress). Provides a count of the number of frames received with a DLCI for which no PVC is provisioned on this port. This count includes any signaling protocol frames received while no signaling protocol is enabled or the wrong signaling protocol is enabled (such as by enabling the Strata LMI signaling protocol while the attached equipment is generating Annex A or Annex D signaling protocol frames, or vice versa). Any frame received with an undefined DLCI is discarded immediately. This statistic is a subset of the Frames Received statistic.

Last unknown DLCI

Displayed so that the user can see the unknown DLCI.

Table 4-29 LMI Statistics

Statistics

Description

Status inquiries transmitted/received

Provides a count of the number of status enquiry frames received from the attached equipment as part of the selected signaling protocol. This statistic is valid for any UIN signaling protocol chosen (Strata LMI, ANSI Annex D, or CCITT Annex A). This statistic is a subset of the Frames Received statistic.

LMI UNI Status Enquiries (Ingress). Provides a count of the number of status enquiry frames received from the attached equipment as part of the selected signaling protocol. This statistic is valid for any UNI signaling protocol chosen (Strata LMI, ANSI Annex D, or CCITT Annex A). This statistic is also valid for any NNI signaling protocol chosen (ANSI Annex D, or CCITT Annex A). This statistic is a subset of the Frames Received statistic.

LMI NNI Status Enquiries (Egress). Provides a count of the number of status enquiry frames transmitted to the attached equipment as part of the selected signaling protocol. This statistic is valid for any NNI signaling protocol chosen (ANSI Annex D or CCITT Annex A). This statistic is a subset of the Frames Transmitted statistic.

Status transmit/received

The number of Status messages sent to the user device.

LMI UNI Status Transmit Count (Egress). Provides a count of the number of status frames transmitted to the attached equipment as part of the selected signaling protocol. This statistic is valid for any UNI signaling protocol. This statistic is valid for any UNI signaling protocol chosen (Strata LMI, ANSI Annex D, or CCITT Annex A). This statistic is a subset of the Frames Transmitted statistic.

Async status Xmit

The number of asynchronous status messages sent to the user device.

Provides a count of the number of asynchronous status update frames transmitted to the attached equipment as part of the selected signaling protocol. This statistic is valid for any UNI signaling protocol chosen (Strata LMI, ANSI Annex D, or CCITT Annex A). This statistic is also valid for any NNI signaling protocol chosen (ANSI Annex D, or CCITT Annex A). If enabled as part of the port configuration (cnfport command), an asynchronous status update frame is generated any time a PVC is failed or downed and again any time a PVC is repaired or upped. This statistic is a subset of the Frames Transmitted statistic.

Invalid requests

The number of invalid requests received from the user device.

LMI Invalid Status Enquiries (Ingress). Provides a count of the number of status enquiry frames with an invalid format received from the attached equipment as part of the selected signaling protocol. This statistic is valid for any UNI signaling protocol chosen (Strata LMI, ANSI Annex D, or CCITT Annex A). This statistic is also valid for any NNI signaling protocol chosen (ANSI Annex D, or CCITT Annex A). This statistic is a subset of the Frames Received statistic.

Timeouts

The number of LMI protocol timeouts.

LMI UNI Link Timeout Errors. Provides a count of the number of times that the rT392 Polling Verification Timers times out without a Status Enquiry frame having been received. This statistic is valid for any UNI signaling protocol chosen (Strata LMI, ANSI Annex D, or CCITT Annex A). The rT392 Polling Verification Timers is configured as part of the port configuration (cnfport command).

Sequence number mismatches

The number of LMI protocol sequence number mismatches.

LMI UNI Keepalive Sequence Errors. Provides a count of the number of times that there was a discontinuity in the (normally consecutive) sequence numbers contained the Status Enquiry frames received from the attached equipment. This statistic is valid for any UNI signaling protocol chosen (Strata LMI, ANSI Annex D, or CCITT Annex A).

Signaling protocol

The protocol selected for this Frame Relay port interface: Cisco LMI, Annex A UNI, Annex D UNI, Annex A NNI, or Annex D NNI.

Table 4-30 Miscellaneous Frame Relay Use Statistics

Miscellaneous Statistics

Statistics

Description

Average queue depth

The average fill of the VC queue at the input of the FRP or FRM.

Transmit Frames Discarded—Queue Overflow (Egress). Provides a count of the number of frames that were discarded because the port's transmit queue (egress queue) was full. The size of the port's transmit queue is configured as part of the port configuration (cnfport) command.

Transmit Bytes Discarded—Queue Overflow (Egress). Provides a count of the number of octets in the Transmit Frames Discarded—Queue Overflow statistic. The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS or CRC) octets.

BECN frames

Number Explicit Congestion Notification frames transmitted to the receiving router.

Number of Explicit Congestion Notification frames transmitted to the transmitting router.

Percentage of BECN frames sent to the total number of frames sent.

Frames Transmitted with BECN (Egress). Provides a count of the number of frames transmitted to the attached equipment with the Backward Explicit Congestion Notification (BECN) bit set, regardless of where in the network the congestion was observed.

FECN frames

The percentage of FECN frames sent to the total number of frames sent.

Frames Transmitted with FECN (Egress). Provides a count of the number of frames transmitted to the attached equipment with the Forward Explicit Congestion Notification (FECN) bit set, regardless of the where in the network the congestion was experienced.

This statistic is a subset of the Frames Transmitted statistic.

Rsrc overflow

Resource overflow indicates the number of times the port shut down due to receive frame buffer overflow or receive queue entries.

DE Frames Dropped (Egress)

The total number of frames with Discard Eligibility that were discarded.

Provides a count of the number of frames to be transmitted to the attached device that were discarded because the frame's DE bit is set and the port's egress buffer has reached the DE threshold. The DE threshold is configured as part of the port configuration (cnfport command). This statistic is a subset of the corresponding PVCs Transmit Frames Discarded statistic.

Table 4-31 CLLM (ForeSight) Statistics

Statistics

Description

CLLM Frames Received

Provides a count of the number of Consolidated Link Layer Management (CLLM) frames received from the attached equipment. CLLM frames are used to exchange PVC congestion information over an NNI port to allow the ForeSight algorithm to regulate the flow of traffic on each PVC based on congestion in the local network as well as congestion in the attached network. This is not intended to be a full implementation of the CLLM suite. The CLLM mechanism is enabled as part of the port configuration (cnfport command). This statistic is a subset of the Frames Received statistic.

CLLM Bytes Received (Ingress)

Provides a count of the number of octets in the frames counted in the CLLM Frames Received statistic. The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. This statistic is a subset of the Bytes Received statistic.

CLLM Frames Transmitted (Egress)

Provides a count of the number of Consolidated Link Layer Management (CLLM) frames transmitted to the attached equipment. CLLM frames are used to exchange PVC congestion information over an NNI port to allow the ForeSight algorithm to regulate the flow of traffic on each PVC based on congestion in the local network as well as congestion in the attached network. This is not intended to be a full implementation of the CLLM suite. The CLLM mechanism is enabled as part of the port configuration (cnfport command). This statistic is a subset of the Frames Transmitted statistic.

CLLM Bytes Transmitted (Egress)

Provides a count of the number of Consolidated Link Layer Management (CLLM) frames transmitted to the attached equipment. CLLLM frames are used to exchange PVC congestion information over an NNI port to allow the ForeSight algorithm to regulate the flow of traffic on each PVC based on congestion in an attached network. This is not intended to be a full implementation of the CLLM suite. The CLLM mechanism is enabled as part of the port configuration (cnfport command). This statistic is a subset of the Frames Transmitted statistic.

CLLM Failures

Provides a count of the number of times that no CLLM frame was received within one second (not configurable), or a CLLM frame was received with any invalid internal format. An invalid CLLM frame that is discarded is included in the statistic of Frames Received.

Example (IGX)

Display the port statistics for Frame Relay port 9.1.

dspportstats 9.1

-----------------------------------SCREEN 1------------------------------------
sw108 VT Cisco IGX 8420 9.3.2o Dec. 5 2000 14:45 GMT

Port Statistics for 9.1 Cleared: Dec. 4 2000 17:26
Port Speed: 256 kbps Collection Time: 0 day(s) 00:00:00 Corrupted: NO
Sig Protocol: None
Bytes Average (kbps) Util (%) Frames
From Port: 0 0 0 0
To Port: 0 0 0 0
Frame Errors LMI Receive Protocol Stats Misc Statistics
Invalid CRC 0 Status Enq Rcvd 0 Avg Tx Port Q 0
Invalid Alignment 0 Status Xmit 0 FECN Frames 0
Invalid Frm Length 0 Asynch Xmit 0 Ratio (%) 0
Invalid Frm Format 0 Seq # Mismatches 0 BECN Frames 0
Unknown DLCIs 0 Timeouts 0 Ratio (%) 0
Last Unknown DLCI 0 Invalid Req 0 Rsrc Overflow 0
DE Frms Dropd 0

This Command: dspportstats 9.1

Next page? (+/-/DEL key to quit)

-----------------------------------SCREEN 2------------------------------------
sw108 VT Cisco IGX 8420 9.3.2o Dec. 5 2000 14:51 GMT

Port Statistics for 9.1 Cleared: Dec. 4 2000 17:26
Port Speed: 256 kbps Collection Time: 0 day(s) 00:00:00 Corrupted: NO
Sig Protocol: None
Bytes Average (kbps) Util (%) Frames
From Port: 0 0 0 0
To Port: 0 0 0 0
LMI Receive Protocol Stats LMI Transmit Protocol Stats CLLM (ForeSight) Stats
Status Enq Rcvd 0 Status Enq Xmit -- Frames Rcvd --
Status Xmt 0 Status Rcd -- Bytes Rcvd --
Asynch Xmit 0 Asynch Rcvd -- Frames Xmt --
Seq # Mismatches 0 Seq # Mismatches -- Bytes Xmt --
Timeouts 0 Timeouts -- CLLM Failures --
Invalid Frames 0
Elmi Ver Req 0 Elmi Ver Rsp 0
Elmi QOS Req 0 Elmi QOS Rsp 0

Last Command: dspportstats 9.1

dspportstats (display ATM port statistics)

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.

Syntax

dspportstats <slot.port>[.<vport>] [interval]

Parameters

Parameter

Description

<slot.port>[.<vport>]

Specifies the slot number of the card, the physical port and optional virtual port (BXM card only). Range (optional vport identifier): 1-31

[interval]

Specifies the refresh interval time for data.
Range: 1 and 60 seconds
Default: 1 second

For BPX only: 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.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

clrportstats

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

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

Table 4-32 BPX Port Statistics Supported for ASI and BXM Front Cards

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

Example (BPX)

Display the statistics for BXM port 11.1.

dspportstats 11.1

sw53 VT Cisco BPX 8620 9.3.2o Dec. 5 2000 14:26 GMT

Port Statistics for 11.1 Cleared: Dec. 5 2000 14:00
Port Speed: 353208 cps Collection Time: 0 day(s) 00:25:38 Corrupted: NO

Cells CLP (EFCI)
Rx Port: 0 0 --
Tx Port: 263 0 --

Unkn Addr (UA): 266 Rx OAM Cells : 0 Rx Clp 0 Cells: 0
Rx Clp 0 Dscd : 0 Rx Clp 1 Dscd : 0 Tx Clp 0 Cells: 263
Tx OAM Cells : 263 Rx RM Count : 0 Tx RM Count : 0
Lst Unk VpiVci: 0.0

UA sums across ports in port group.

This Command: dspportstats 11.1
Example (IGX)

Display the statistics for UXM port 11.1.

dspportstats 11.1

-----------------------------------SCREEN 1------------------------------------
sw180 TN Cisco IGX 8420 9.3.o9 Dec. 5 2000 14:31 GMT

Port 4.1
Collection Time: day(s) 02:29:24 Clrd: 12/05/00 11:51:28
Type Count
VI: Cells received 0
VI: Cells transmitted 0
VI: Cells rcvd w/CLP=1 0
VI: Cells tx w/CLP=1 0
VI: Cells received w/CLP=0 0
VI: Cells transmitted w/CLP=0 0
VI: Cells discarded w/CLP=1 0
VI: Cells discarded w/CLP=0 0
VI: OAM cells received 0
VI: OAM cells transmitted 0
VI: RM cells received 0
VI: RM cells transmitted 0

This Command: dspportstats 4.1

Next page? (+/-/DEL key to quit)

-----------------------------------SCREEN 2------------------------------------
sw180 TN Cisco IGX 8420 9.3.o9 Dec. 5 2000 14:33 GMT

Port 4.1
Collection Time: 0 day(s) 02:30:40 Clrd: 12/05/00 11:51:28
Type Count
PORT: Unknwn VPI/VCI cnt 40
PORT: Last unknown VPI/VCI pair 0.16
PORT: # of cells rcvd 0
PORT: # of cells xmt 0
INVMUX: maximum diff delay 0
INVMUX: HEC cell errors 0
INVMUX: LCP cell errors 0
INVMUX: Cell Hunt Count 0
INVMUX: Bandwidth Change Count 0
INVMUX: Unavailable Seconds 0
INVMUX: Near End Fail Count 0
INVMUX: Last Proto Fail Code 0

This Command: dspportstats 4.1

Next page? (+/-/DEL key to quit)

-----------------------------------SCREEN 3------------------------------------
sw180 TN Cisco IGX 8420 9.3.o9 Dec. 5 2000 14:33 GMT

Port 4.1
Collection Time: (s) 02:31:06 Clrd: 12/05/00 11:51:28
Type Count
INVMUX: Slowest Link 0
ILMI: Get Req PDUs rcvd 0
ILMI: Get Rsp PDUs rcvd 0
ILMI: GetNxt Req PDUS rx 0
ILMI: Trap PDUs rcvd 0
ILMI: Set Req PDUs rcvd 0
ILMI: Unknwn PDUs rcvd 0
ILMI: Get Req PDUs xmt 0
ILMI: Get Rsp PDUs xmt 0
ILMI: GetNxt Req PDUS xmt 0
ILMI: Trap PDUs xmt 0
ILMI: Set Req PDUs xmt 0

This Command: dspportstats 4.1

Next page? (+/-/DEL key to quit)

-----------------------------------SCREEN 4------------------------------------
sw180 TN Cisco IGX 8420 9.3.o9 Dec. 5 2000 14:33 GMT

Port 4.1
Collection Time: 0 day(s) 02:31:31 Clrd: 12/05/00 11:51:28
Type Count
LMI: Status msgs rcvd 0
LMI: Updt Status msg rcvd 0
LMI: Status Enq msgs rcvd 0
LMI: Status Ack msg rcvd 0
LMI: Status messages xmt 0
LMI: Updt Status msgs xmt 0
LMI: Status Enq msgs xmt 0
LMI: Status Ack msgs xmt 0
LMI: Invalid LMI PDUs rcvd 0
LMI: Invalid LMI PDU length rcvd 0
LMI: Unknown LMI PDUs rcvd 0
LMI: Invalid LMI IE rcvd 0

This Command: dspportstats 4.1

Next page? (+/-/DEL key to quit)

-----------------------------------SCREEN 5------------------------------------
sw180 TN Cisco IGX 8420 9.3.o9 Dec. 5 2000 14:34 GMT

Port 4.1
Collection Time: 0 day(s) 02:31:57 Clrd: 12/05/00 11:51:28
Type Count
LMI: Invalid Transaction IDs 0

This Command: dspportstats 4.1

dspprtcnf (display print configuration)

Displays the current print configuration for the network where the command is entered. The three printing modes, "remote," "local," and "no" are listed and the currently selected mode is highlighted. If remote printing is selected, the node name where the remote printer is located also appears. If the name of the node is flashing, the node is unreachable.

Remote mode indicates that the log for the node prints on the printer at the listed remote node.

Local mode indicates that the log for the node prints on the node's printer.

No printing mode indicates that the log for the node does not print.

Syntax

dspprtcnf

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnfprt

Example

Display the print configuration. The example does not show the highlighted field.

dspprtcnf

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 16:02 PST

Printing Mode

Remote Printing
Local Printing
No Printing

Last Command: dspprtcnf

Next Command:

dsppwd (display password)

Displays the password of the current user or any user at any lower privilege level.

Syntax

dsppwd <user_id>

Parameters

Parameter

Description

userid

Specifies the user whose password is displayed.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Example

Display the password for user YourID.

dsppwd yourid

alpha TRM YourID:1 IGX 8410 9.3 Apr. 13 2000 13:56 PST

The password for YourID is liftoff

This Command: dsppwd YourID

This screen will self-destruct in ten seconds
Next Command: dsppwd YourID

dsppwr (display power supply status)

Displays the current status of the power supply monitor, the current power supply configuration (which may consist of one to four power supplies depending on node requirements), and the current cabinet temperature.

On the right side of the screen is displayed the internal cabinet temperature in degrees Centigrade and Fahrenheit. The temperature is displayed as a thermometer and the exact temperature appears at the top of the thermometer.

Syntax

dsppwr

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

dspcd, dspcds

Example (IGX)

Display the power status and temperature inside the current IGX node.

dsppwr

sw151 TN SuperUser IGX 16 9.3 Apr. 13 2000 11:50 GMT

Power Supply Status Cabinet Temperature

Monitor Rev AK, Ser # 247582 - Status: Active 30 86

AC Supply Status C 60 | | 140 F
A 1 875W OK e | | a
B 1 875W OK n 50 |--| 122 h
C 1 Empty t | | r
D 2 Empty i 40 | | 104 e
E 2 Empty g | | n
F 2 Empty r 30 | | 86 h
a | | e
d 20 | | 68 i
e `--' t

Last Command: dsppwr

Next Command:
Example (BPX)

Display the power status and temperature inside the current BPX node.

dsppwr

bootzilla TN SuperUser BPX 8620 9.3 Apr. 13 2000 11:06 GMT

Power Status Cabinet Temperature

ASM Status: Active 21 69

Power voltage A/B: 0 / 49 V C 60 | | 140 F
e | | a
PSU Ins Type Rev SerNum Failure n 50 |--| 122 h
A N N/A N/A N/A N/A t | | r
B Y ???? 00 ...... None i 40 | | 104 e
g | | n
Fan Status r 30 | | 86 h
a | | e
FAN 1 2 3 d 20 | | 68 i
0000 3300 3240 RPM e `--' t

Last Command: dsppwr

Next Command:

dspqbin (display Qbin)

Displays the Qbin resources on a selected trunk, port, or virtual trunk:

•the Qbin parameters currently configured for an interface

•whether the Qbin resources have been configured by the user or by a template

•whether the Qbin has EPD enabled/disabled

Only Qbins (Class of Service Buffers) 10 to 15 are used for VSI connections.

To display all VSI Qbins on an interface, pass the wildcard character (the asterisk *) as the Qbin ID to the command.

Syntax

dspqbin <slot.port.vtrk>[qbin-id]

Parameters

Parameter

Description

<slot.port.vtrk>

Specifies the UXM card slot number, port number, and virtual trunk number. For VSI, specifies the ID number of the Qbin available for use by the LSC (MPLS Controller).

[qbin-id]

Specifies the ID number of the Qbin available for use by the LSC (MPLS controller) for VSI. Range: 10-15

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

Yes

BPX, IGX

Yes

Yes

Yes

No

Related Commands

cnfqbin, dspqbint

Display Parameters

Object (Parameter) Name

Range/Values

Default

Description

Qbin Number

10-15

R

Identifies the target Qbin to modify.

Discard Selection

1: CLP Hysteresis (EPD Disabled)

2: Frame Discard (EPD Enabled)

EPD: Early Packet Discard

R

Indicates whether Qbin should perform the CLP Hysteresis or the Frame Discard option. The Qbin can be configured to do only one or the other.

Discard Threshold

0-? cells

R

The Qbin depth: Determines the amount of cell memory dedicated to this Qbin.

CLP High Threshold

0-100%

R

Parameter determines at which level in the Qbin CLP-tagged cells are discarded. Discard continues until the Qbin depth drops below the Qbin CLP Low Threshold.

CLP Low Threshold

0-100%

R

Parameter determines at which level in the Qbin CLP-tagged cells are admitted.

EFCI Threshold

0- 100%

R

Parameter determines at which level in the Qbin EFCI bits are tagged in the departing cells.

EPD Threshold

0-100%

R

Parameter determines at which level the QBIN Frame Discard is activated.

Example (OC-3 on IGX)

Display the current Qbin configuration on Qbin 10 of the OC-3 trunk 13.2.

dspqbin 9.1 10

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 13:56 PST

Qbin Database 13.2 on UXM qbin 10 (Configured by MPLS1 Template)
(EPD Enabled on this qbin)

Qbin State: Enabled
Discard Threshold: 65536 cells
EPD Threshold: 95%
High CLP Threshold: 100%
EFCI Threshold: 100%

Last Command: dspqbin 13.2 10

Next Command:
Example (UXM on IGX)

Display the current Qbin configuration on slot 13, port 2, Qbin 15.

dspqbin 13.2 15

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 13:57 PST

Qbin Database 13.2 on UXM qbin 15 (Configured by MPLS1 Template)
(EPD Enabled on this qbin)

Qbin State: Enabled
Discard Threshold: 65536 cells
EPD Threshold: 95%
High CLP Threshold: 100%
EFCI Threshold: 100%

Last Command: dspqbin 13.2 15

Next Command:
Example (VSI on IGX)

Display all VSI Qbins on virtual trunk 3.2.1. Answer yes when prompted to display the next Qbin.

dspqbin 3.2.1 *

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 13:58 PST

Qbin Database 3.2.1 on UXM qbin 10 (Configured by MPLS1 Template)
(EPD Enabled on this qbin)

Qbin State: Enabled
Discard Threshold: 900 cells
EPD Threshold: 95%
High CLP Threshold: 100%
EFCI Threshold: 100%

This Command: dspqbin 3.2.1 *

Continue?
Example (OC-3 on BPX)

Display the current Qbin configuration on Qbin 10 of the OC-3 trunk 4.2

dspqbin 4.2 10

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 19:45 GMT

Qbin Database 4.2 on BXM qbin 10 (Configured by MPLS1 Template)
(EPD Enabled on this qbin)

Qbin State: Enabled
Discard Threshold: 105920 cells
EPD Threshold: 95%
High CLP Threshold: 100%
EFCI Threshold: 100%

Last Command: dspqbin 4.2 10

Next Command:
Example (BXM on BPX)

Display the current Qbin configuration on slot 10, port 2, Qbin 15.

dspqbin 10.2 15

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 19:48 GMT

Qbin Database 10.2 on BXM qbin 15 (Configured by ATMF1 Template)
(EPD Enabled on this qbin)

Qbin State: Enabled
Discard Threshold: 131072 cells
EPD Threshold: 60%
High CLP Threshold: 80%
EFCI Threshold: 100%

Last Command: dspqbin 10.2 15

Next Command:
Example (VSI on BPX)

Display all VSI Qbins on virtual trunk 10.1.1. Answer yes when prompted to display the next Qbin.

dspqbin 10.1.1 *

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 19:51 GMT

Qbin Database 10.1.1 on BXM qbin 10 (Configured by MPLS1 Template)
(EPD Enabled on this qbin)

Qbin State: Enabled
Discard Threshold: 900 cells
EPD Threshold: 95%
High CLP Threshold: 100%
EFCI Threshold: 100%

This Command: dspqbin 10.1.1 *

Continue?
Class of Service Buffer Descriptor Template Configuration

Table 4-33 below lists parameters included in the Class of Service (CoS) Buffer (Qbin) portion of the Service Class Templates. A Qbin is a platform-specific instance, such as BXM, of the more general Class of Service Buffer. A firmware command sends a command (message) to switch software to initialize the CoS Buffer Descriptors in the Service Class Templates. This command may contain multiple instances of Qbin number, each indicating a new Qbin configuration.

Table 4-33 Class of Service Buffer Parameters That Display on dspqbin Screen

Object (Parameter) Name

Range/Values

Default

Description

Qbin Number

10-15

R

Identifies the target Qbin to modify.

Discard Selection

1: CLP Hysteresis (EPD Disabled)

2: Frame Discard (EPD Enabled)

EPD: Early Packet Discard

R

Indicates whether Qbin should perform the CLP Hysteresis or the Frame Discard option. You can configure the Qbin to do only one or the other.

Discard Threshold

0-? cells

R

The Qbin depth: Determines the amount of cell memory dedicated to this Qbin.

CLP High Threshold

0-100%

R

Parameter determines at which level in the Qbin CLP-tagged cells are discarded. Discard continues until the Qbin depth drops below the Qbin CLP Low Threshold.

CLP Low Threshold

0-100%

R

Parameter determines at which level in the Qbin CLP-tagged cells are admitted.

EFCI Threshold

0-100%

R

Parameter determines at which level in the Qbin EFCI bits are tagged in the departing cells.

EPD Threshold

0-100%

R

Parameter determines at which level the QBIN Frame Discard is activated.

dspqbinstats (display Qbin statistics)

Displays Qbin summary statistics associated with a trunk or port.

Syntax

dspqbinstats <trunk | port> [interval]

Parameters

Parameter

Description

trunk

Specifies the trunk for statistics display. Format is slot.port[.vtrk]

port

Specifies the port for statistics display.
Format is slot.port[.vport]
Range (optional vport identifier): 1-31

[interval]

Specifies the interval (in seconds) between updates of the statistics display.
Range 1-30 seconds
Default: 10 seconds

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

No

Yes

BPX, IGX

Yes

Related Commands

dspstatparms, dsptrkerrshist

Example (BXM on IGX)

Display Qbin statistics for port 3.6 on a BXM (BPX) card.

dspqbinstats 3.6

NODENAME TRM Cisco BPX 8620 9.3.10 Date/Time Not Set

QBIN Stats for Port 3.6 Cleared: Date/Time Not Set
Prt TX Rate: 96000 cps Collection Time: 0 day(s) 00:08:00

STATS Cells STATS Cells STATS Cells
Qbin 0 CTXL :0 Egr QBIN0 CRx :0 Tx Q0 CDscd :0
Qbin 1 CTXL :0 Egr QBIN1 CRx :0 Tx Q1 CDscd :0
Qbin 2 CTXL :0 Egr QBIN2 CRx :0 Tx Q2 CDscd :0
Qbin 3 CTXL :0 Egr QBIN3 CRx :0 Tx Q3 CDscd :0
Qbin 9 CTXL :0 Egr QBIN9 CRx :0 Tx Q9 CDscd :0
Qbin 10 CTXL :0 Egr QBIN10 CRx:0 Tx Q10 CDscd :0
Qbin 11 CTXL :0 Egr QBIN11 CRx:0 Tx Q11 CDscd :0
Qbin 12 CTXL :0 Egr QBIN12 CRx:0 Tx Q12 CDscd :0
Qbin 13 CTXL :0 Egr QBIN13 CRx:0 Tx Q13 CDscd :0
Qbin 14 CTXL :0 Egr QBIN14 CRx:0 Tx Q14 CDscd :0

This Command: dspqbinstats 3.6

Next page? (+/DEL key to quit):

NODENAME TRM Cisco BPX 8620 9.3.10 Date/Time Not Set

QBIN Stats for Port 3.6 Cleared: Date/Time Not Set
Prt TX Rate: 96000 cps Collection Time: 0 day(s) 00:08:00

STATS Cells STATS Cells STATS Cells
Qbin 15 CTXL :0 Egr QBIN15 CRx:0 Tx Q15 CDscd :0

This Command: dspqbinstats 3.6
Example (UXM on IGX)

Display Qbin statistics for port 5.1 on a UXM (IGX) card.

dspqbinstats 5.1

neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:45 GMT

QBIN Stats for Port 5.1 Cleared: May 31 2000 01:26
Prt TX Rate: 96000 cps Collection Time: 0 day(s) 00:15:00

STATS Cells STATS Cells STATS Cells
Q2 Cells Tx :0 Egr CRx Q2 :0 Tx Q2 CDscd :0
Q3 Cells Tx :0 Egr CRx Q3 :0 Tx Q3 CDscd :0
Q7 Cells Tx :0 Egr CRx Q7 :0 Tx Q7 CDscd :0
Q8 Cells Tx :0 Egr CRx Q8 :0 Tx Q8 CDscd :0
Q9 Cells Tx :0 Egr CRx Q9 :0 Tx Q9 CDscd :0
Q10 Cells Tx :0 Egr CRx Q10 :0 Tx Q10 CDscd :0
Q11 Cells Tx :0 Egr CRx Q11 :0 Tx Q11 CDscd :0
Q12 Cells Tx :0 Egr CRx Q12 :0 Tx Q12 CDscd :0
Q13 Cells Tx :0 Egr CRx Q13 :0 Tx Q13 CDscd :0
Q14 Cells Tx :0 Egr CRx Q14 :0 Tx Q14 CDscd :0

This Command: dspqbinstats 5.1

Next page? (+/DEL key to quit):

neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:46 GMT

QBIN Stats for Port 5.1 Cleared: May 31 2000 01:26
Prt TX Rate: 96000 cps Collection Time: 0 day(s) 00:17:41

STATS Cells STATS Cells STATS Cells
Q15 Cells Tx :0 Egr CRx Q15 :0 Tx Q15 CDscd :0

This Command: dspqbinstats 5.1

dspqbint (display Qbin templates)

Displays the default Qbin parameters for a VSI Qbin in a Qbin template. The Qbin template is associated with the Service Class Template. There are nine Service Class Templates so there are nine corresponding Qbin templates. Each Qbin template contains entries for all VSI Qbins (10-15).

For more detailed information on service class templates and Qbin templates, please read the section on VSI in the Cisco IGX Series Reference Guide and the Cisco BPX Installation and Configuration Guide.

Syntax

dspqbint <Service_Class_Template #><qbin ID #>

Parameters

Parameter

Description

Service_Class_Template

Specifies the Service Class Template associated with the Qbin.

Qbin ID #

Specifies the ID number of the Qbin available for use by the LSC (MPLS Controller) for VSI.
Range: 10-15

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

Yes

Yes

No

No

Related Commands

dspsct, dspqbin, cnfrsrc, dsprsrc, cnfvsiif, dspvsiif

Example (IGX)

Display the Qbin parameters in Qbin 10 of Service Class Template 1.

dspqbint 1 10

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 14:05 PST

Service Template: 1 Qbin: 10

Discard Threshold: 300000 (micro secs)
CLP Low/EPD Threshold: 95 (% of Discard Threshold)
CLP High Threshold: 100 (% of Discard Threshold)
EFCI Threshold: 100 (% of Discard Threshold)
EPD: Enabled
Vc Shaping: Enabled

Last Command: dspqbint 1 10

Next Command:
Example (BPX)

Display the Qbin parameters in Qbin 10 of Service Class Template 1.

dspqbint 1 10

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:08 GMT

Service Template: 1 Qbin: 10

Discard Threshold: 300000 (micro secs)
CLP Low/EPD Threshold: 95 (% of Discard Threshold)
CLP High Threshold: 100 (% of Discard Threshold)
EFCI Threshold: 100 (% of Discard Threshold)
EPD: Enabled
Vc Shaping: Enabled

Last Command: dspqbint 1 10

Next Command:

dsprevs (display revisions)

Displays the system configuration and status of the primary and secondary software revisions running on all nodes in the network. The primary revision is the software that is running on the node. The secondary revision is the software that is available in memory but not being run.

Syntax

dsprevs

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

runrev, loadrev

Display Fields: Software Revision Status Messages

Status

Description

unavailable

The revision is currently unavailable for the node displayed. The revision has not propagated to the node yet.

available

The node has located the specified revision but has not yet downloaded it.

partial

The revision was only partially downloaded. Indicates the download was temporarily interrupted.

downloading

The revision is in the process of being downloaded. Blocks of data are transferring.

loaded

The revision has completed downloading but is not ready for running.

upgrading

The controller card is being upgraded by the current revision. This process generally occurs immediately following the download.

upgraded

The upgrade procedure has been completed.

running

The primary revision is currently used to run the node.

Example (IGX)

dsprevs

sw171 TN SuperUser IGX 8420 9.3 Apr. 13 2000 14:52 GMT
------ Primary ------ ----- Secondary -----
NodeName Status Revision Status Revision
sw29 Running 9.2.h3
sw43 Running 9.2.h5
sw44 Running 9.2.h3
sw171 Running 9.2.h0 Loaded 9.2.h9
sw177 Running
sw106 Running 9.2.h3
sw181 Running 9.2.h3

Lowest revision running in net: 9.2.h0

Last Command: dsprevs

Next Command:

dsprobst (display robust statistics)

Displays the statistics associated with the Robust Alarms messages between the node and Cisco WAN Manager NMS. The optional "clear" argument clears the statistics buffers.

Syntax

dsprobst [clear]

Parameters

Parameter

Description

[clear]

Specifies that the statistics buffers should be cleared after the display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

cnfrobparm

Example (IGX)

dsprobst

sw197 TN SuperUser IGX 8420 9.3 Apr. 13 2000 05:43 GMT

Robust Communications Statistics since : Date/Time Not Set

Updts msg xmit: 0
Updts msg ackd: 0
Updts ack tout: 0
LCBs freed: 0
Updts ack reset: 0

Last Command: dsprobst

Next Command:

dsprrst (display reroute statistics)

Displays the network statistics for connection rerouting resulting from failed trunks. These statistics are useful in determining the performance of the reroute algorithm. Use the "clear" option to clear the counters before accumulating the statistics.

Syntax

dsprrst [s] [t] [clear]

Parameters

Parameter

Description

[s]

Optional parameter that displays connection routing summary and settling information.

[t]

Optional parameter that displays node settling time measurement history. The following statistics are reported:

•Start Time: the time that the route measurement started.

•Stop Time: the time when the route measurement stopped. If "In Progress" is displayed, routing is still ongoing.

•Conns: the number of connections routed during measurement.

•Bndls: the number of route bundles routed during measurement.

•Avg Bndl: the average bundle size during measurement.

•Elapsed(s): the elapsed nodal settling time in seconds during measurement.

•E: the efficiency factor. The total real time spent processing routing threads divided by the node settling time.

The last ten settling time measurements, including the active measurement, if any, are displayed. Node settling time history is cleared whenever reroute statistics are cleared.

For each route initiated, a separate table entry is added. The most recent route initiated is at the top of the table.

[clear]

Specifies that the reroute statistics buffers should be cleared after the display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

rrtcon

Display Fields: Reroute Statistics

Statistic

Description

Number of Completed Routes

The total number of connections routed since the activities were last cleared.

Number of Failed Routes

The number of attempted reroutes that failed for any reason.

Number of Collisions

During a route, the initiating node locks all nodes on the route until routing is done. If another node attempts to reroute through a locked node, a collision occurs, so the second node must wait then retry.

Max. # of Consec. Collisions

The count of consecutive collisions as defined above.

Max/Avg Secs To Select Route

Time taken within the initiating node to select a new route.

Max/Avg Secs To Perform Route

Time taken to contact and lock the nodes on the new route and perform the routing process.

Avg Secs to Route a Conn:

Time to perform a reroute divided by the average number of connections in a bundle.

% of Collisions/Rrt Attempt

Another statistic derived from the number of collisions and the number of route attempts.

Max Secs To NOT find Route

Similar to "max secs to select a route" except that the algorithm finished and no route was found.

Number of Routes not found

Number of routes not found in the rerouting process. This parameter updates periodically as a heartbeat to check for activity.

# of Rrts with rrt req_bit set

Number connections awaiting reroute. If rrt_req bit is set, a reroute was not successful; or trunk deletions or loading additions mean connections must be rerouted. Rerouting clears the rrt_req bit.

Address of Forced Rrt Counts

Memory address for database information.

Max routes checked in search

Maximum number of paths examined in a search for a new route.

Max good rts checked in search

Maximum number of possible routes found before the search ended. The value should be 1.

# our lns rmvd from under us

The number of changes to topology and loading that occurred while rerouting was in progress. This is the number of times we detect, while "cleaning up" a derouted connection, that the involved trunk for the said connection has *just* been deleted.

This counter can be incremented more than once even if derouting only one single connection.

If the value for this statistic and the statistic # lines rmvd out from under us (see below) is zero, the connection is fine. If one of the values is non-zero, (at least once) this indicates that a trunk has been deleted before affected connections have been properly "cleaned."

# lines rmvd out from under us

This counter is incremented as a continuation of the cleanup process. During the course of cleanup of a single connection, if this condition is detected, the process still proceeds to cleanup all sorts of related resources.

This counter can be incremented more than once even if derouting only one single connection.

If the value for this statistic and the statistic # our lns rmvd from under us (see above) is zero, the connection is fine. If one of the values is non-zero, (at least once) this indicates that a trunk has been deleted before affected connections have been properly "cleaned."

Concurrent RR_CB HWM

Maximum number of reroute control blocks simultaneously allocated. Note the following definitions:

•RR_CB: ReRoute Control Block. This is the data structure used to maintain status of a routing thread.

•HWM: High-Water Mark.

Concurrent master RR_CB HWM

Maximum number of reroute control blocks simultaneously allocated for master routes.

# Path block saturation

Number of times candidate selection was aborted due to too many path-blocked candidates.

# Slv rejected by path blk

Number of times a candidate was rejected because the slave node was path blocked.

# Rts rejected by path blk

Number of times a route was rejected because a node on the path was path blocked.

# Slv rejected by backoff

Number of times a candidate was rejected because the salve node is in collision backoff.

# Mstr CPU throttle trans

Number of times CPU-based throttling for master routes has transitioned from off to on.

# Via CPU throttle trans

Number of times CPU-based throttling for via routes has transitioned from off to on.

# Slv CPU throttle trans

Number of times CPU-based throttling for slave routes has transitioned from off to on.

# M Rts rej by CPU throttle

Number of times master routing has been deferred due to CPU throttling.

# V Rts rej by CPU throttle

Number of times a via route request was rejected due to CPU throttling.

# S Rts rej by CPU throttle

Number of times a slave route request was rejected due to CPU throttling.

Example

dsprrst

sws5 TN Cisco IGX 8420 9.3.a4 Mar. 18 2001 02:03 PST

Conn. Routing Statistics LOC_DOMAIN
Number of Completed Routes: 0 Blocked by other st machines: 1
Number of Failed Routes: 0 Timeouts waiting for ACK/NACK: 0
Number of Collisions: 0 Timeouts in LOCKED state: 0
Max # of Consec Collisions: 0 Number of Routes Not found: 0
Max Secs To Select Route: 0.000 # of Rrts with rrt_req bit set: 0
Max Secs To Perform Route: 0.000 Address of Forced Rrt Counts: 3147FDB6
Max Bundle Size Routed: 0 Max routes checked in search: 0
Avg Secs To Select Route: 0.000 Max good rts checked in search: 0
Avg Secs To Perform Route 0.000 # nibs rmvd out from under us: 0
Avg Secs To Route a Conn: 0.000 # our lns rmvd from under us: 0
Avg Bundle Size Routed: 0 # lns rmvd from under us: 0
% of Collisions/Rrt Attempt: 0% Number of conid conflicts: 0
Max Secs To NOT find Route: 0.011 Number of LCON deroutes: 0
Times conns deletd while rtng: 0 Number of VLCON deroutes: 0

This Command: dsprrst
Continue?

sws5 TN Cisco IGX 8420 9.3.a4 Mar. 18 2001 02:04 PST

Conn. Routing Statistics LOC_DOMAIN
# conns added to Rrt waitlist: 0 # no destination trunk: 0
# conns unroutable: 0 # lowest cost route found: 0
# Reroute_Line_Debug: 4000610 # lowest cost route not found: 0
# Reroute_Debug: FFFFFFFF # lowest cost route recovered: 0
# Upd_via_info: 0 # cost exceeded hop recovery: 0
# diff rrt cons number: 0 # unsuccessful cache usage: 0
# hop count exceeded: 0 # successful cache usage: 0
# cost exceeded: 0 # successful on-demand: 0
# delay exceeded: 0 # quit msgs sent from mstr: 6
# open cell space too low: 0 # nodal endpt collisions 0
# open packet space too low: 0 # nodal via collisions 0
# open conid space too low: 0
# open GW LCN space too low: 0
# lowest cost path replaced: 0

This Command: dsprrst
Continue?

sws5 TN Cisco IGX 8420 9.3.a4 Mar. 18 2001 02:04 PST

Conn. Routing Statistics LOC_DOMAIN
Concurrent RR_CB HWM: 1
Concurrent master RR_CB HWM: 1
# Path block saturation: 0
# Slv rejected by path blk: 0
# Rts rejected by path blk: 0
# Slv rejected by backoff: 0
# Mstr CPU throttle trans: 0
# Via CPU throttle trans: 0
# Slv CPU throttle trans: 0
# M Rts rej by CPU throttle: 0
# V Rts rej by CPU throttle: 0
# S Rts rej by CPU throttle: 0

Last Command: dsprrst
Example

Display the connection routing summary and settling information for the IGX node.

dsprrst s

sws5 TN Cisco IGX 8420 9.3.a4 Mar. 18 2001 06:06 PST

Connection Routing Summary and Settling Info

Number of Completed Routes: 0 Reroute Repeat Count = 0
Number of Failed Routes: 0

Max Secs To Select Route: 0.000
Max Secs To Perform Route: 0.000

Avg Secs To Select Route: 0.000
Avg Secs To Perform Route: 0.000
Avg Secs To Route a Conn: 0.000

Reroute Duration has never been measured
Settling Time has never been measured

Last Command: dsprrst s
Example

Display the settling time measurement history for a BPX node.

dsprrst t

sw217 TN Cisco BPX 8620 9.3.u4 May 10 2001 1223 PST

Node Settling Time Measurements Current Measurement State ACTIVE

Start Time Stop Time Conns Bndls Avg Bndl Elapsed(s) E
05/10/01 122301 In Progress 0 0 0.00 7.73 ---
05/10/01 122247 05/10/01 122248 2 2 1.00 0.64 1.23
05/10/01 122241 05/10/01 122241 1 1 1.00 0.35 0.92
05/10/01 000942 05/10/01 004418 1000 1000 1.00 1955.16 0.22

Last Command dsprrst t

dsprsrc (display resources)

Displays the partition of all the resources on the specified trunk or port. It also displays virtual trunks for a specified trunk or port. Resources not applicable to virtual trunks are not displayed.

To display all active interfaces with or without partitions on the node, enter the command with no parameters.

To display all active interfaces with or without partitions on a particular slot, enter the command with the slot number.

To display detailed information about all the partitions enabled on an active interface, enter:

dsprsrc slot.port or dsprsrc slot.port.vtrk

Syntax

dsprsrc <slot>.<port>.<vtrk> [partition_id]

Parameters

Parameter

Description

<slot>

Specifies the card slot.

<port>

Specifies the card port number.

<vtrk>

Specifies the virtual trunk number.

[partition_id]

Specifies the ID number of the partition available for use by the LSC (MPLS Controller) for VSI.

Optional.
Range: 0-255
Default: 0
Valid partitions: 1, 2, and 3

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

Yes

BPX, IGX

Yes

Yes

No

No

Related Commands

cnfrsrc, cnfqbin, dspqbin

Example (IGX)

Display partition resources on the IGX node.

dsprsrc

sw188 TRM Cisco IGX 8420 9.3.1c Aug. 17 2000 11:19 PST

VSI Partitions on this node

Interface (slot.port) Part 1 Part 2 Part 3
Line 4.1 E D D
Trunk 5.1 D E D
Trunk 5.2 D D D
Trunk 5.3 D D D
VTrunk 5.4.1 D D E
Line 5.5 E E D

Last Command: dsprsrc
Example (IGX)

Display partition resources on slot 5 of the IGX node.

dsprsrc 5

sw188 TRM Cisco IGX 8420 9.3.1c Aug. 17 2000 11:20 PST

VSI Partitions on this node

Interface (slot.port) Part 1 Part 2 Part 3
Trunk 5.1 D E D
Trunk 5.2 D D D
Trunk 5.3 D D D
VTrunk 5.4.1 D D E
Line 5.5 E E D

Last Command: dsprsrc 5
Example (IGX)

Display partition resources on port 5 of the UXM card in slot 5 of the IGX node.

dsprsrc 5.5

sw188 TRM Cisco IGX 8420 9.3.1c Aug. 17 2000 12:05 PST

Line : 5.5
Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 3000
(Reserved Port Bandwidth: 150)

State MinLCN MaxLCN StartVPI EndVPI MinBW MaxBW
Partition 1: E 200 500 100 200 100 500
Partition 2: E 200 500 255 255 250 500
Partition 3: D

Last Command: dsprsrc 5.5
Example (OC-3 on BPX)

Display partition resources on the OC-3 trunk on card slot 3, port 2, and virtual trunk 1 on the BPX node.

dsprsrc 3.2.1

sw57 TN SuperUser BPX 8620 9.3.10     Mar. 10 2000 10:41 GMT

Virtual Trunk: 3.2.1
Full Port Bandwidth: 3000
Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 1867
(Statistical Reserve: 1000)

PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1
PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1

Partition : 1 2 3
Partition State : Disabled Disabled Disabled
VSI LCNS (min/max): 0 /0 0 /0 0 /0
VSI VPI (start/end): 0 /0 0 /0 0 /0
VSI BW (min/max): 0 /0 0 /0 0 /0
VSI ILMI Config: CLR CLR CLR
Example (OC-3 on BPX)

Display partition resources on the OC-3 trunk on port 1 of slot 13 on the BPX to support MPLS.

dsprsrc 13.1

sw57 TN SuperUser BPX 8620 9.3.10    Mar. 10 2000 10:41 GMT

Trunk : 13.1
Full Port Bandwidth: 353208
Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 352207
(Statistical Reserve: 1000)

PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1
PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1

Partition : 1 2 3
Partition State : Enabled Disabled Disabled
VSI LCNS (min/max): 0 /6323 0 /0 0 /0
VSI VPI (start/end): 60 /70 0 /0 0 /0
VSI BW (min/max): 0 /0 0 /0 0 /0
VSI ILMI Config: CLR CLR CLR

Last Command: dsprsrc 13.1

dsprtcache (display cost-based route cache)

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.

Syntax

dsprtcache [index] [c]

Parameters

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.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX, BPX

No

Related Commands

dspcon, cnfrtcost, cnfpref

Example

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

dsprtcache

pissaro TN StrataCom BPX 15 9.3 Apr. 13 2000 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:

dsprtr (display router)

Displays the configuration of the Universal Router Module (URM) embedded router on a specified router slot. The configurable router parameters include the IOS configuration file source and the router serial port function. A full description of these parameters is provided in the cnfrtr command definition.

Syntax

dsprtr <router_slot>

Parameters

Parameter

Description

router slot

Specifies the virtual shelf slot to support the URM embedded router.
Range: 1-32

Switch software manages the embedded router in the URM as if the router resides on a slot in a virtual shelf (of routers). Each slot in the IGX shelf has a corresponding router slot in the virtual shelf. A router slot is considered empty when the equivalent IGX slot is empty or contains an IGX card without an embedded router. If the IGX slot contains a URM card, the router slot is reported as hosting an IOS router.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

Yes

Yes

No

No

Related Commands

cnfrtrparm, cnfrtr, dsprtrslot, dsprtrslots, dspalms, rstrtr

Example

Display the configuration for the URM embedded router in router slot 10. In this example, the IOS configuration file source is configured as the NPM Admin flash.

dsprtr 10

sw175 TN Cisco IGX 8420 9.3.q6 Mar. 9 2000 05:44 GMT

Configuration for Router Slot 10: Snapshot
IOS Configuration: from card's Admin Flash
Router Serial Port: CON

Last Command: dsprtr 10

dsprtrcnfdnld (display status of router configuration file)

Displays the status of the IOS configuration file transfer. The display is updated dynamically. Status is reported for two-step file transfer process:

•IOS configuration file transfer from the TFTP server to the NPM RAM buffer.

•IOS configuration file copy (burn) to the URM Admin flash.

The dsprtrcnfdnld screen displays the following fields of information.

•The name of the IOS configuration file.

•The size, in bytes, of the IOS configuration file.

•The number of IOS configuration file bytes transferred.

•The status of the file transfer to the NPM RAM buffer or copy to the URM Admin flash.

The file transfer status reports include:

•Complete

•Corrupted

•Unavailable

•File too large

•Abort (shows reason for abort)

•Space occupied (identifies application occupying the space)

•Getting from TFTP server (shows server IP address)

•Burning into slot (shows slot number)

For further information about the URM Remote Router Configuration feature, refer to URM Remote Router Configuration Feature on the IGX, page 2-3.

Syntax

dsprtrcnfdnld

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

Yes

Yes

No

No

Related Commands

burnrtrcnf, clrrtrcnf, cnfrtr, cnfrtrcnfmastip, dspcnf, dsprtr, dsprtrslot

Example

Display the transfer status of the IOS configuration file named 1234.c.

dsprtrcnfdnld

sw175 TN Cisco IGX 8420 9.3.q6 Mar. 9 2000 05:18 GMT

Router Config filename Status
1234.c Complete

Router Config fileSize Bytes Dnld
256050

Last Command: dsprtrcnfdnld

dsprtrslot (display router slot)

The display now also includes the IOS configuration file, Admin flash configuration file information, detailed operational information, and alarm status for the Universal Router Module (URM) embedded router on a specified router slot. The display is dynamically updated by IGX switch software.

The IOS configuration file source information includes the name and size of the file stored in URM Admin flash. For a full description of the parameter used to specify the IOS configuration file source, see the cnfrtr command.

The URM dynamically reports router operational information to the NPM. The information reported is described in Table 4-34.

Table 4-34 URM Embedded Router Operational Information

Information Type

Description

Router State

The router operational status. Router states include:

•Inactive

•Rommon

•Rommon-CLI

•Network-Download-Setup

•BootHelp-Setup

•IOS-Setup

•Network-Download

•BootHelper

•IOS

•Failed

IOS SW Image

The IOS image name and revision (up to 32 characters).

VIC Type

The Voice Interface Card (VIC) type. VIC types include:

•E1

•T1

•none

The URM dynamically reports router alarm conditions to the NPM. The alarm conditions for the embedded router are described in Table 4-35.

Table 4-35 URM Embedded Router Alarm Conditions

Alarm Condition

Description

Standby

Indicates the router state is Inactive on a standby URM slot.

Clear

Indicates that the router state is IOS on an active URM logical slot.

Service

Indicates the router state is either BootHelper or Network-Download on an active URM logical slot. When the router is in this condition, all connections on the internal port remain operational. Traffic on these connections, in both ingress and egress directions, is NOT discarded.

Non-Operational

Indicates that the router state on an active logical URM slot is either Inactive, Rommon, Rommon-CLI, Network-Download-Setup, Boothelper-Setup, IOS-Setup, or Failed. When the router is in this condition, all connections on the internal port are FAILED. Traffic on these connections, in both ingress and egress directions, is discarded.

Missing-Card

Indicates that the active logical URM card is either mismatched, down, failed, programming, or missing. When the router is in this condition, all connections on the internal port are FAILED.

Syntax

dsprtrslot <router_slot>

Parameters

Parameter

Description

router slot

Specifies the virtual shelf slot to support the URM embedded router.
Range:1-32

Switch software manages the embedded router in the URM as if the router resides on a slot in a virtual shelf (of routers). Each slot in the IGX shelf has a corresponding router slot in the virtual shelf. A router slot is considered empty when the equivalent IGX slot is empty or contains an IGX card without an embedded router. If the IGX slot contains a URM card, the router slot is reported as hosting an IOS router.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

cnfrtrparm, cnfrtr, dsprtr, dsprtrslots, dspalms, rstrtr

Example

Display IOS configuration file source information, operational information, and alarm status for the URM embedded router on router slot 10.

dsprtrslot 10

sw175 TN Cisco IGX 8420 9.3.q6 Mar. 9 2000 05:39 GMT

Router Slot 10 Operational Info

Card Type : URM
Router State : Inactive
IOS Status Alrm : Standby
IOS SW Image : --
VIC Type : --
Router config name : --
Router config size : --

Last Command: dsprtrslot 10

dsprtrslots (display router slots)

Displays a summary of the operational information and alarm status for all URM embedded routers in the IGX node. The operational information includes router slot number, card type, and Voice Interface Card (VIC) type. The display is dynamically updated by switch software.

Use the dsprtrslots command in conjunction with the dsprtrslot command. The dsprtrslot command displays detailed operational information for the router on a specific router slot. The router states and router alarm conditions reported by the URM are described in the dsprtrslot command.

Syntax

dsprtrslots [l | u]

Parameters

Parameter

Description

l | u

Specifies the virtual shelf in a 32-slot IGX for display.

•l = lower shelf

•u = upper shelf

Switch software manages the embedded router in the URM as if the router resides on a slot in a virtual shelf (of routers). Each slot in the IGX shelf has a corresponding router slot in the virtual shelf. A router slot is considered empty when the equivalent IGX slot is empty or contains a legacy IGX card. If the IGX slot contains a URM card, the router slot is reported as hosting an IOS router.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

cnfrtrparm, cnfrtr, dsprtr, dsprtrslot, dspalms, rstrtr

Example

Display the operational information for all URM embedded routers in the IGX node.

dsprtrslots

sw108 TN Cisco IGX 8420 9.3.2E Sep. 5 2000 08:51 GMT

R O U T E R S L O T S

Card VIC Router Card VIC Router
Type Type Status Type Type Status
1 No router in NPM 9 -- -- --
2 No router in NPM 10 -- -- --
3 -- -- -- 11 -- -- --
4 -- -- -- 12 -- -- --
5 -- -- -- 13 -- -- --
6 URM VIC-2E1 Ok 14 -- -- --
7 -- -- -- 15 -- -- --
8 -- -- -- 16 -- -- --

Last Command:dsprtrslots

dsprts (display connection routing)

Displays the routes used by all connections at a node. The display shows the trunk numbers and names of all nodes in the path.

Use dsprts to see the current cost for all connection routes. A derouted connection shows no current cost. A connection route optimized with trunk delay shows the current total delay. A highlighted connection on the display has exceeded the maximum route cost.

Syntax

dsprts [start group | chan] [nodename]

Parameters

Parameter

Description

start group or channel

Specifies the starting group or channel with which to begin the display. Channel displays are in numeric order. If no starting channel is specified, the display begins with the first connected channel. Start channel is specified in one of the following formats:

Voice connection: slot.channel

Data connection: slot.port

Frame relay connection: slot.port.DLCI

Frame relay connection group: remote node.groupname

Access device connection: slot.port.device_ID

node name

Specifies that connections from only the local node to the current node are displayed. If no nodename is entered, connections from the local node to all other nodes are displayed.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

Yes

Yes

BPX, IGX

Yes

Related Commands

cnfpref

Example (BPX)

Display the connection routes.

dsprts

sw203 TN SuperUser BPX 8620 9.3 Apr. 13 2000 17:47 GMT

Conn Route
9.1.1.* (Cost = 5)
sw203 1.1-- 1.1sw242
Pref: Not Configured
9.2.5.100 (Cost = 1)
sw203 3.1.1-- 2.1.1sw242
Pref: Not Configured
9.2.5.101 (Cost = 1)
sw203 3.1.1-- 2.1.1sw242
Pref: Not Configured
9.2.5.102 (Cost = 5)
sw203 1.1-- 1.1sw242
Pref: Not Configured

This Command: dsprts

Continue?

dspsct (display Service Class Template)

Displays a list of nine Service Class Templates (SCT). There are three levels of operations for this command:

•dspsct
With no arguments, lists all Service Class Templates resident in the node.

•dspsct <tmplt_id>
Lists all the Service Classes (or service types) in the template

•dspsct <tmplt_id> <Service Type>
Lists all the parameters of that Service Class.

Syntax

dspsct [template #][service_type]

Parameters

Parameter

Description

[template #]

Template ID number; lists all the Service Classes (service types) in this template.

[service_type]

Lists the parameters of the specified Service Class

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

Yes

Yes

No

No

Related Commands

dspqbint, cnfvsiif, dspvsiif

Extended Services Types Support

The service-type parameter for a connection is specified in the connection bandwidth information parameter group. The service-type and service-category parameters determine the Service Class to be used from the Service Template.

Connection Admission Control (CAC)

When a connection request is received by the VSI slave, it is first subjected to a Connection Admission Control process before being forwarded to the firmware layer responsible for actually programming the connection. The granting of the connection is based on these criteria:

LCNs available in the VSI partition

•Qbin

•Service Class

QoS guarantees

•max CLR

•max CTD

•max CDV

When the VSI slave accepts (that is, after CAC) a connection setup command from the VSI master in the Label Switch Controller, it receives information about the connection including service type, bandwidth parameters, and QoS parameters. This information is used to determine an index into the VI's selected Service Template's VC Descriptor table thereby establishing access to the associated extended parameter set stored in the table.

Supported Service Types

The service type identifier is a 32-bit number. However, the service type identifier is represented as a string (service type) on the dspsct screen. For example, to specify a Service Class Template number and service type:

dspsct 1 Tag0

A list of supported service templates and associated Qbins, and service types is shown in Table 4-36.

Table 4-36 Service Template and Associated Qbin Selection

Template Type

Service Type ID

Service Type

Parameters

Associated Qbin

VSI Special Types

0x0001

0x0002

Default

Signaling

See dspsct command for sample parameters for various service types.

13 for templates MPLS1, ATMF1, and ATMF2.

10 for the rest of the templates.

10 for template MPLS1

ATMF1 and

ATMF2 templates

(for PNNI controllers)

0x0100

0x0101

0x0102

0x0103

0x0104

0x0105

0x0106

0x0107

0x0108

0x0109

0x010A

0x010B

cbr.1

vbr.rt1

vbr.rt2

vbr.rt3

vbr.nrt1

vbr.nrt2

vbr.nrt3

ubr.1

ubr.2

abr

cbr.2

cbr.3

See dspsct command for sample parameters for various service types.

10

11

11

11

12

12

12

13

13

14

10

10

MPLS Types

(for MPLS controllers)

0x0001

0x0002

0x0200

0x0201

0x0202

0x0203

0x0204

0x0205

0x0206

0x0207

0x0210

Default

Signaling

Tag0

Tag1

Tag2

Tag3

Tag4

Tag5

Tag6

Tag7

TagABR

See dspsct command for sample parameters for various service types.

13

10

10

11

12

13

10

11

12

13

14

ATMF_tagcos_1

ATMF_tagcos_2

0x0001

0x0100

0x0101

0x0102

0x0103

0x0104

0x0105

0x0106

0x0107

0x0108

0x0109

0x010A

0x010B

0x0200

0x0201

0x0202

0x0203

0x0204

0x0205

0x0206

0x0207

0x0210

Default

cbr.1

vbr.rt1

vbr.rt2

vbr.rt3

vbr.nrt1

vbr.nrt2

vbr.nrt3

ubr.1

ubr.2

abr

cbr.2

cbr.3

Tag0

Tag1

Tag2

Tag3

Tag4

Tag5

Tag6

Tag7

TagAbr

See dspsct command for sample parameters for various service types.

10

15

11

11

11

12

12

12

10

10

14

15

15

10

10

13

13

10

10

13

13

14

ATMF_TAGABR_1

ATMF_TAGABR_2

0x0001

0x0100

0x0101

0x0102

0x0103

0x0104

0x0105

0x0106

0x0107

0x0108

0x0109

0x010A

0x010B

0x0200

0x0201

0x0202

0x0203

0x0204

0x0205

0x0206

0x0207

0x0210

Default

cbr.1

vbr.rt1

vbr.rt2

vbr.rt3

vbr.nrt1

vbr.nrt2

vbr.nrt3

ubr.1

ubr.2

abr

cbr.2

cbr.3

Tag0

Tag1

Tag2

Tag3

Tag4

Tag5

Tag6

Tag7

TagAbr

See dspsct command for sample parameters for various service types.

10

15

11

11

11

12

12

12

10

10

14

15

15

10

10

10

10

10

10

10

10

13

atmf_TAGCoS_TAGABR_1

atmf_TAGCoS_TAGABR_2

0x0001

0x0100

0x0101

0x0102

0x0103

0x0104

0x0105

0x0106

0x0107

0x0108

0x0109

0x010A

0x010B

0x0200

0x0201

0x0202

0x0203

0x0204

0x0205

0x0206

0x0207

0x0210

Default

cbr.1

vbr.rt1

vbr.rt2

vbr.rt3

vbr.nrt1

vbr.nrt2

vbr.nrt3

ubr.1

ubr.2

abr

cbr.2

cbr.3

Tag0

Tag1

Tag2

Tag3

Tag4

Tag5

Tag6

Tag7

TagAbr

See dspsct command for sample parameters for various service types.

10

10

10

10

10

11

11

11

12

12

11

10

10

12

13

14

15

12

13

14

15

13

Details of Connection (VC) Parameters Used in Service Class Templates

Listed below is detailed information on connection (VC) parameters used in Service Class Templates. Some of these parameters may appear on the dspsct display.

Qbin #

Description CoS Buffer (Qbin) to use for this CoS
Range/Values: 10 - 15
Units: enumeration

UPC Enable

Description: Enable/Disable Policing function. The first 2 values are consistent with the definition for the older cards. Option #2 and #3 are new and provide the ability to turn on policing on just GCRA #1 (PCR policing) or #2 (SCR policing).

Range/Values: 0 -3
0: Disable both GCRAs
1: Enable both GCRAs
2: Enable GCRA #1 only (PCR policing)
3: Enable GCRA #2 only (SCR policing)

Units: enumeration

UPC CLP Selection

Description: Selects processing of policing Buckets based on the CLP bit.

Range/Values: 0 -2
0 - Bk 1: CLP (0+1), Bk 2: CLP (0)
1 - Bk 1: CLP (0+1), Bk 2: CLP (0+1)
2 - Bk 1: CLP (0+1), Bk 2: Disabled

Units: enumeration

Policing Action (GCRA #1)

Description: Indicates how cells that fail the second bucket (SCR bucket) of the policer should be handled, if policing is enabled.

Range/Values: 0 - Discard
1 - Set CLP bit
2 - Set CLP of untagged cells, disc. tag'd cells

Units: enumeration

Policing Action (GCRA #2)

Description: Indicates how cells that fail the second bucket (SCR bucket) of the policer should be handled, if policing is enabled.

Range/Values: 0 - Discard
1 - Set CLP bit
2 - Set CLP of untagged cells, disc. tag'd cells

Units: enumeration

PCR

Description: Peak Cell Rate; used as default value if not supplied in VSI connection request.

Range/Values: 0 - 100

Units: cells/sec

MCR

Description: Minimum Cell Rate; used as default value if not supplied in VSI connection request.

Range/Values: 0 - 100

Units: cells/sec

SCR

Description: Sustained Cell Rate; used as default value if not supplied in VSI connection request.

Range/Values: 0 - 100

Units: cells/sec

ICR

Description: Initial Cell Rate . Used only for ABR VCs to set initial ACR value after idle traffic period.

Range/Values: 0 - 100

Units: cells/sec

MBS

Description: Maximum Burst Size - used to set bucket depth in policer function.

Range/Values: 1 - 5M

Units: cell count

CoS Min BW

Description: Bandwidth reserved for this Class of Service; used to initialize the CoS Buffer (Qbin) Minimum Service Rate (HW param. = ICG), and for CAC purposes (subject to CAC treatment type).

Range/Values: 0% - 100%

Units: % of Partition Min BW.

CoS Max BW

Description: Maximum value allowed for the sum of VC Min. BW's for this CoS; used by CAC (subject to CAC treatment type).

Range/Values: 0% - 100%

Units: % of Partition Max BW

Scaling Class

Description: Scaling table used for modifying per-VC thresholds under VI or Global cell-memory congestion.

Range/Values: choices are 0 - 3,

0: CBR
1: VBR
2: ABR
3: UBR

Units: enumeration

CAC Treatment

Description: Connection Admission Control algorithm used by this CoS

Range/Values: 0 - 256

0: No CAC performed; all connections admitted.

1: LCN_CAC; check for LCN availability only; no BW consideration.

2: MINBW_CAC; LCN + simple min. BW test (sum_of_VC_min_BW <= CoS_max_BW)

3: CAC_2 w/ overbooking allowed

4: ECR_CAC; LCN + ECR calculation (from table) & BW test (sum_of VC_ECR <= Cos_max_BW).

5: CAC_4 w/ overbooking allowed

6: MEASURED_CAC; LCN + ECR calculation (from dynamic measurement) & BW test (sum_of VC_ECR <= Cos_max_BW).

Units: enumeration

VC Max

Description: Maximum VC-cell-count threshold; all cells are discarded on a VC when this threshold has been exceeded.

Range/Values: 0 - VI_max_cell_count

Units: cell count

VC CLPhi

Description: VC cell count above which CLP=1 cells are discarded

Range/Values: 0 - 100

Units: % of VC Max threshold

VC CLPlo

Description: VC cell count below which CLP=1 cells are no longer discarded (discards having begun when CLPhi was exceeded).

Range/Values: 0 - 100

Units: % of VC Max threshold

VC EPD

Description: VC cell count above which AAL-5 frames are discarded

Range/Values: 0 - 100

Units: % of VC Max threshold

VC EFCI

Description: VC cell count above which congestion notification is activated

Range/Values: 0 - 100

Units: % of VC Max threshold

VC Discard Selection

Description: Choice of frame-based discard (EPD) or CLP-hysteresis

Range/Values: 0 - 1
0: CLP Hysteresis
1: EPD

Units: enumeration

VSVD/FCES

Description: For ABR VC's, enable/disable Virtual Source/Virtual Destination (VSVD) and/or Flow Control on External Segments (FCES) functionality

Range/Values: 0 -2
0: None
1: VSVD
2: VSVD w/ FCES

Units: enumeration

ADTF ABR only parameter

Description: ACR decrease time factor; idle time before ACR -> ICR

Range/Values: 10 - 1023

Units: milliseconds

RDF ABR only parameter

Description: Rate Decrease Factor
ACR = ACR - (ACR * RDF)

Range/Values: 2 - 512, in powers of 2

Units: Inverse decrease factor

RIF ABR only parameter

Description: Rate Increase Factor
ACR = ACR + (PCR * RDF)

Range/Values: 2 - 512, in powers of 2

Units: Inverse decrease factor

NRM ABR only parameter

Description: Number of data cells between FRM cells

Range/Values: 2 - 512, in powers of 2

Units: cells

TRM ABR only parameter

Description:

Range/Values:

Units:

CDF ABR only parameter

Description:

Range/Values:

Units:

TBE ABR only parameter

Description:

Range/Values:

Units:

FRTT ABR only parameter

Description:

Range/Values:

Units:

Example (IGX)

Displays all the templates in the IGX node.

dspsct

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 14:10 PST

Service Class Templates

Template Name

1 MPLS1
2 ATMF1
3 ATMF2
4 ATMF_tagcos_1
5 ATMF_tagcos_2
6 ATMF_TAGABR_1
7 ATMF_TAGABR_2
8 atmf_TAGCoS_TAGABR_1
9 atmf_TAGCoS_TAGABR_2

Last Command: dspsct

Next Command:
Example (IGX)

Display all service classes of the MPLS1 template in the IGX node.

dspsct 1

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 14:11 PST

Service Class Map for MPLS1 Template

Service Class Qbin Service Class Qbin Service Class Qbin

Default 13
Signaling 10
Tag0 10
Tag1 11
Tag2 12
Tag3 13
Tag4 10
Tag5 11
Tag6 12
Tag7 13
TagAbr 14

Last Command: dspsct 1

Next Command:
Example (IGX)

Display service type Default in template 1.

dspsct 1 default

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 14:12 PST

Service Template: MPLS1 (1) Service Type: Default (1)

Service Category Default (1)
Qbin 13
UPC Enable NONE
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 61440 (cells)
VC Dscd Selection EPD
VC CLP High 100 (% of Vc MAX Threshold)
VC EPD 40 (% of Vc MAX Threshold)
Cell Delay Variation Tolerance 250000

Last Command: dspsct 1 Default

Next Command:
Example (IGX)

Display service type Signaling in Template 1.

dspsct 1 Signaling

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 14:14 PST

Service Template: MPLS1 (1) Service Type: Signaling (2)

Service Category Signaling (2)
Qbin 10
UPC Enable NONE
Sustained Cell Rate 0 (% of PCR)
Maximum Burst Size 0 (cells)
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 0 (cells)
VC Dscd Selection Hystersis
VC CLP High 75 (% of Vc MAX Threshold)
VC CLP Low 30 (% of Vc MAX Threshold)
Cell Delay Variation Tolerance 250000

Last Command: dspsct 1 Signaling

Next Command:
Example (IGX)

Display service type Tag0 in Template 1.

dspsct 1 Tag0

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 14:15 PST

Service Template: MPLS1 (1) Service Type: Tag0 (200)

Service Category Tag0 (200)
Qbin 10
UPC Enable NONE
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 61440 (cells)
VC Dscd Selection EPD
VC CLP High 100 (% of Vc MAX Threshold)
VC EPD 40 (% of Vc MAX Threshold)

Last Command: dspsct 1 Tag0

Next Command:
Example (IGX)

Display service type TagAbr in Template 1.

dspsct 1 TagAbr

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 14:15 PST

Service Template: MPLS1 (1) Service Type: TagAbr (210)

Service Category TagAbr (210)
Qbin 14
UPC Enable NONE
Minimum Cell Rate 0 (% of PCR)
Sustained Cell Rate 0 (% of PCR)
Initial Cell Rate 100 (% of PCR)
Maximum Burst Size 1024 (cells)
Scaling Class Scaled 2nd
CAC Treatment LCN
VC Max Threshold 61440 (cells)
VC Dscd Selection EPD
VC CLP High 100 (% of Vc MAX Threshold)
VC EPD 40 (% of Vc MAX Threshold)

This Command: dspsct 1 TagAbr

Continue? Y

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 14:16 PST

Service Template: MPLS1 (1) Service Type: TagAbr (210)

VC EFCI 20 (% of Vc MAX Threshold)
VSVD NONE
Decrease Time Factor 500 (milli seconds)
Rate Decrease Factor 16 (Inverse Decrease Factor)
Rate Increase Factor 16 (Inverse Decrease Factor)
data cells b/w Fwd RM Cells 32 (Cells)
Time b/w Fwd RM Cells 0
Cut-Off Decrease Factor 16
Transient Buffer Exposure 16777215
Fixed Round Trip Time 0

Last Command: dspsct 1 TagAbr

Next Command:
Example (BPX)

Displays all the templates in the BPX node.

dspsct

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:23 GMT

Service Class Templates

Template Name

1 MPLS1
2 ATMF1
3 ATMF2
4 ATMF_tagcos_1
5 ATMF_tagcos_2
6 ATMF_TAGABR_1
7 ATMF_TAGABR_2
8 atmf_TAGCoS_TAGABR_1
9 atmf_TAGCoS_TAGABR_2

Last Command: dspsct

Next Command:
Example (BPX)

Display Service Class Template 2, which displays Service Classes (also referred to as service categories or service sub-categories) for the ATMF1 template, along with designated Qbins.

dspsct 2

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:26 GMT

Service Class Map for ATMF1 Template

Service Class Qbin Service Class Qbin Service Class Qbin

Default 13 Cbr1 10
Signaling 12 Cbr2 10
VbrRt1 11 Cbr3 10
VbrRt2 11
VbrRt3 11
VbrNRt1 12
VbrNRt2 12
VbrNRt3 12
Ubr1 13
Ubr2 13
Abr 14

Last Command: dspsct 2
Example (BPX)

Display Service Class Template 3, which displays service classes for the ATMF2 template, along with designated Qbins.

dspsct 3

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:39 GMT

Service Class Map for ATMF2 Template

Service Class Qbin Service Class Qbin Service Class Qbin

Default 13 Cbr1 10
Signaling 12 Cbr2 10
VbrRt1 11 Cbr3 10
VbrRt2 11
VbrRt3 11
VbrNRt1 12
VbrNRt2 12
VbrNRt3 12
Ubr1 13
Ubr2 13
Abr 14

Last Command: dspsct 3

Next Command:
Example (BPX)

Display service type VbrRt1 in Template 2.

dspsct 2 VbrRt1

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:41 GMT

Service Template: ATMF1 (2) Service Type: VbrRt1 (101)

Service Category VbrRt (101)
Qbin 11
UPC Enable GCRA_1_2
UPC CLP Selection CLP01_CLP01
Policing Action 1 DISCARD
Policing Action 2 DISCARD
Sustained Cell Rate 100 (% of PCR)
Maximum Burst Size 1024 (cells)
Scaling Class Scaled 3rd
CAC Treatment CAC4
VC Max Threshold 1280 (cells)
VC Dscd Selection Hystersis
VC CLP High 80 (% of Vc MAX Threshold)

This Command: dspsct 2 VbrRt1

Continue? Y
sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:42 GMT

Service Template: ATMF1 (2) Service Type: VbrRt1 (101)

VC CLP Low 35 (% of Vc MAX Threshold)
Cell Delay Variation Tolerance 250000

Last Command: dspsct 2 VbrRt1

Next Command:
Example (BPX)

Display service type Abr in Template 2.

dspsct 2 Abr

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:43 GMT

Service Template: ATMF1 (2) Service Type: Abr (109)

Service Category Abr (104)
Qbin 14
UPC Enable GCRA_1
UPC CLP Selection CLP01
Policing Action 1 DISCARD
Minimum Cell Rate 0 (% of PCR)
Sustained Cell Rate 0 (% of PCR)
Initial Cell Rate 0 (% of PCR)
Maximum Burst Size 1024 (cells)
Scaling Class Scaled 2nd
CAC Treatment MIN BW
VC Max Threshold 8000 (cells)
VC Dscd Selection Hystersis

This Command: dspsct 2 Abr

Continue? Y

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:44 GMT

Service Template: ATMF1 (2) Service Type: Abr (109)

VC CLP High 80 (% of Vc MAX Threshold)
VC CLP Low 35 (% of Vc MAX Threshold)
VC EFCI 20 (% of Vc MAX Threshold)
VSVD NONE
Decrease Time Factor 500 (milli seconds)
Rate Decrease Factor 16 (Inverse Decrease Factor)
Rate Increase Factor 16 (Inverse Decrease Factor)
data cells b/w Fwd RM Cells 32 (Cells)
Time b/w Fwd RM Cells 0
Cut-Off Decrease Factor 16
Transient Buffer Exposure 16777215
Fixed Round Trip Time 0
Cell Delay Variation Tolerance 250000

Last Command: dspsct 2 Abr

Next Command:
Example (BPX)

Display service type Default in Template 1 (MPLS1).

dspsct 1 Default

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:44 GMT

Service Template: MPLS1 (1) Service Type: Default (1)

Service Category Default (1)
Qbin 13
UPC Enable NONE
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 61440 (cells)
VC Dscd Selection EPD
VC CLP High 100 (% of Vc MAX Threshold)
VC EPD 40 (% of Vc MAX Threshold)
Cell Delay Variation Tolerance 250000

Last Command: dspsct 1 Default
Example (BPX)

Display the signaling service type in Template 1 (MPLS1).

dspsct 1 Signaling

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:46 GMT

Service Template: MPLS1 (1) Service Type: Signaling (2)

Service Category Signaling (2)
Qbin 10
UPC Enable NONE
Sustained Cell Rate 0 (% of PCR)
Maximum Burst Size 0 (cells)
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 0 (cells)
VC Dscd Selection Hystersis
VC CLP High 75 (% of Vc MAX Threshold)
VC CLP Low 30 (% of Vc MAX Threshold)
Cell Delay Variation Tolerance 250000

Last Command: dspsct 1 Signaling

Next Command:
Example (BPX)

Display the service type Tag0 in Template 1 (MPLS1).

dspsct 1 Tag0

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:48 GMT

Service Template: MPLS1 (1) Service Type: Tag0 (200)

Service Category Tag0 (200)
Qbin 10
UPC Enable NONE
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 61440 (cells)
VC Dscd Selection EPD
VC CLP High 100 (% of Vc MAX Threshold)
VC EPD 40 (% of Vc MAX Threshold)

Last Command: dspsct 1 Tag0

Next Command:
Example (BPX)

Display the service type Cbr1 in Template 9.

dspsct 9 Cbr1

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:50 GMT

Service Template: atmf_TAGCoS_TAGABR_2 (9) Service Type: Cbr1 (100)

Service Category Cbr (100)
Qbin 10
UPC Enable NONE
Scaling Class Scaled 4th
CAC Treatment CAC4
VC Max Threshold 160 (cells)
VC Dscd Selection Hystersis
VC CLP High 80 (% of Vc MAX Threshold)
VC CLP Low 35 (% of Vc MAX Threshold)
Cell Delay Variation Tolerance 250000

Last Command: dspsct 9 Cbr1

Next Command:

dspsig (display signaling)

Displays the current signaling state received at the node from the specified voice channel.

This command displays the current signaling state received at the node from the specified voice channel. The status of the transmit and receive A and B signaling bits (for DS1 trunks) or A, B, C and D signaling bits (for E1 trunks) are displayed as a 0 or 1. The status of the bits (0 or 1) depends on the signaling type utilized on the connection displayed. The transmit direction of transmission is toward the remote node; the receive direction is toward the local circuit line.

The dspsig command can be used to verify the connection signaling type. If you compare the A/B bit states on-hook and off-hook with those shown in the dspchcnf command, you will note that the node passes signaling straight through. The signaling definition is only important for monitoring the on-hook/off-hook state and setting conditioning patterns.

Syntax

dspsig <start_channel>

Parameters

Parameter

Description

<start_channel>

First voice channel in the format slot.port.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

IGX

No

Related Commands

cnfclnsigparm, cnfrcvsig, dspclnsigparm

Example

dspsig 7.1

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 19:25 PST

Signalling Information
From 7.1 TXA-bit TXBbit TXCbit TXDbit RXA-bit RXBbit RXCbit RXDbit no_serv
7.1-15 1 1 0 1 1 1 0 1
7.17-31 1 1 0 1 1 1 0 1

Last Command: dspsig 7.1

Next Command:

dspsigqual (display signaling qualifiers)

Displays the configuration for the A, B, C, and D bit signaling qualifiers for all channels. The only parameter is the starting channel. You set the values for these signaling bits by using the cnfrcvsig and cnfxmtsig commands. Note that these signaling bit states are different from the states during circuit alarm (signaling conditioning).

During normal operation of the voice circuit, the A, B, C, and D signaling bits may be held at a fixed value (0 or 1), inverted (I), or passed through transparently (T).

Signal direction:

•Transmit direction is toward the PBX or channel bank.

•Receive direction is from the external equipment.

Syntax

dspsigqual <start channel>

Parameters

Parameter

Description

start channel

Specifies the starting channel.

On a CDP or CVM, the format is slot.channel.

On a UVM, the format is slot.line.channel.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Related Commands

cnfxmtsig, cnfrcvsig

Example

Display the channel signaling bit qualifiers for channel 13.1.

dspsigqual 13.1

sw150 TN Cisco IGX 8420 9.3.2T Dec. 19 2000 23:58 PST

Signalling Qualifiers
From 13.1 TXAbit TXBbit TXCbit TXDbit RXAbit RXBbit RXCbit RXDbit
13.1-24 T T T T T T T T

Last Command: dspsigqual 13.1

dspslot (display slot)

Displays system information associated with a specific card in the node.

This command displays system information associated with a specific card in the node. The information can help you debug card failures. When a card failure is reported to the Cisco TAC, the TAC engineer records the parameters for the associated card displayed by using dspslot.

The information displayed by the dspslot command is unique to the card and is used primarily by the controller card to supervise background system tasks lists the card parameters.

Use this command to add information on a failed card when you return it. Print the screen or otherwise record the information and return it with the faulty card to Cisco.

Syntax

dspslot <slot number>

Parameters

Parameter

Description

<slot number>

Specifies the shelf slot number.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Example (IGX)

dspslot 6

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 19:27 PST

Card Data Base for FRP card in slot 6 at address 30BD820C

Logical Card 6 Test in Prog 0
Verify DB Flag 0 Slft Res Abort 0
Info Ptr 30B88C2C Slft Abort 0
Last Event TEST_FREE Last Test BKGD_TEST
Fail Inter 0 FRP Test Fail 0
Selftest Fail 0 FRP Test Fail I 0
Selftest Inter 0 FRP Port Test Fail 0
Selftest Timeout 0 FRP Port Capacity 31
Con Test Fail 0 FRP Line Capable 1
Red LED Flag 0 FRP V35 Capable 0
Restart Reason Not maintained FRP X21 Capable 0
Selftest Results FRP NNI/CLLM Cap 1
FRP CGW/ATFR Cap 1

Last Command: dspslot 6

Next Command:
Slot Parameters You Can Display on Node

Item

Parameter

Description

1

Logical Card

This number represents the type of card.

2

Verify DB Flag

Verify database flag. Concerned with database and memory.

3

Info Ptr

Information pointer. Concerned with database and memory.

4

Last Event

This is the previous state of the card.

5

Fail Inter

Indicates intermittent card failure.

6

Selftest Fail

Indicates self-test fail condition.

7

Selftest Inter

Indicates intermittent self-test failure.

8

Selftest Timeout

Self-test routine timed out before completion.

9

Con Test Fail

Indicates failure of the test con command.

10

Red LED Flag

Indicates front panel FAIL LED on.

11

Restart Reason

Reason for last card reset.

12

Selftest Results

Results of last self-test for card.

13

Test in Prog

Indicates card test is in progress.

14

Slft Res Abort

Not used.

15

Slft Abort

Not used.

16

Card Stats Up

A "1" indicates statistics are being collected on this card.

17

Sib Pointer

Pointer to database concerning statistics.

18

Summary stats

Pointer to database concerning statistics.

19

Detailed stats

Pointer to database concerning statistics.

20

Bus Mastership

For BCC, this indicates whether this is the slave BCC. For other cards, this is not used.

21

Last Test

Last test performed on card in this slot.

dspslotalmcnf (display slot alarm configuration)

Displays the slot alarm configuration for the BPX node.

Syntax

dspslotalmcnf [slot]

Parameters

Parameter

Description

slot number

Specifies the slot number of the card to be displayed.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

dspslotalms

Example (BPX)

Display the slot alarm configuration for the BPX.

dspslotalmcnf 7

D1.jea TRM SuperUser BPX 8620 9.3 Apr. 13 2000 12:04 GMT

Slot Alarm Configuration

Minor Major

Violation Rate Alarm Time Clear Rate Alarm Time Clear
1) SBus .01% 10 min 3 min .1% 10 sec 10 sec
2) InvP .01% 10 min 3 min .1% 10 sec 10 sec
3) PollA .01% 10 min 3 min .1% 10 sec 10 sec
4) PollB .01% 10 min 3 min .1% 10 sec 10 sec
5) BGE .01% 10 min 3 min .1% 10 sec 10 sec
6) TBip .01% 10 min 3 min .1% 10 sec 10 sec
7) RBip .01% 10 min 3 min .1% 10 sec 10 sec
8) Bfrm .01% 10 min 3 min .1% 10 sec 10 sec
9) SIU .01% 10 min 3 min .1% 10 sec 10 sec

Last Command: dspslotalmcnf 7

Next Command:

dspslotalms (display slot alarms)

Displays statistical alarms associated with the SIU on each BPX card. The display provides a single line for each slot in a local BPX node occupied by a card. Both the card type and the current card alarm status appears. If a card is operating normally, the display shows "Clear - Slot OK." If fault conditions continue to cause the slot errors to exceed a preset threshold, the column labeled Current Card Alarm Status reflects this fact. If the alarm condition has disappeared, use the clrslotalms command to clear these alarm messages. For a list of slot errors, see the dspsloterrs description.

Syntax

dspslotalms <slot>

Parameters

Parameter

Description

slot

Specifies the slot number of the card to display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX

No

Related Commands

dspsloterrs

Example

Display the status of the card in slot 1.

dspslotalms 1

D1.jea TRM SuperUser BPX 8620 9.3 Apr. 13 2000 12:00 GMT

Slot Type Current Slot Alarm Status
7 BCC Clear - Slot OK
11 BNI-T3 Clear - Slot OK

Last Command: dspslotalms

Next Command:

dspsloterrs (display slot errors)

Displays statistical alarms associated with the SIU on each BPX card. The dspsloterrs command takes a slot number as an optional parameter: if you enter dspsloterrs without a slot number, the display shows a single line for each slot with statistics that have accumulated for all slots.

Both the card type and current status are displayed. If a card is operating normally, the status is "Clear - Slot OK." If fault conditions persistently cause the slot errors (described in the Display Slot Errors command) to exceed a preset threshold, this fact is displayed under the column labeled Current Card Alarm Status. The clrslotalm command clears the alarm messages if the alarm condition has been cleared. The chart below describes the errors is the display.

Display Fields: Statistical Alarms

Error

Description

Standby Bus Errors

Indicates a background test over the standby bus produced an error.

Invalid Port Errors

Indicates port number was out of the range 1-3.

Polling Bus A Errors

Parity error occurred on this polling bus.

Polling Bus B Errors

Parity error occurred on this polling bus.

Bad Grant Errors

Error indicates arbiter did not issue a grant to send data before a timeout.

Tx BIP-16 Errors

Data frame transmitted had a checksum error.

Rx BIP-16 Errors

Data frame received with a checksum error.

SIU Phase Errors

Serial Interface Unit on the card did not detect the frame synch properly.

Bframe Errors

Errors detected in the BPX frame on the StrataBus or in a memory operation.

Rx FIFO Sync Errs

Rx FIFO (first-in-first-out) sync errors indicate that the receive FIFOs used by the BIF-RX circuit either got out of sync with the start of frames or with each other.

These errors mean that two frames have been discarded; however, those frames may not have contained any user data (they could just be filler known as Null BFrames). When these occur infrequently, they are simply counted. If they happen too often, a hardware error will be generated because a circuit failure could cause them. Make sure you are using the latest firmware (the BIF-RX has had fixes for this). If the errors continue, replace the card.

Poll Clk Errs

Poll Clock Errors are detected when the POLLCLK, which is distributed by the active BCC to each of the other cards, stops. The count is of 100 millisecond periods in which this happened. Without POLLCLK, the card is unable to transmit data across the backplane.

CK 192 Errs

Errors in a clock distributed by the BCC. The CK-192 is used to synchronize the transmit signal on some cards. If it is not present, the transmit signal is off frequency, in turn generating line and trunk errors.

BXM Errs

BXM errors are BXM card specific errors.

Syntax

dspsloterrs [slot]

Parameters

Parameter

Description

slot

Specifies the slot number of a card for the display.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX

No

Related Commands

dspslotalms

Example (BPX)

Display the alarm statistics for the card in slot 4.

dspsloterrs 4

sw217 TN Cisco BPX 8620 9.3.3q May 25 2001 12:22 PST

BXM 4 Status: Clear - Slot OK Clrd: Date/Time Not Set
Type Count ETS Status Type Count ETS Status
Stby PRBS Errs 0 0
Rx Invld Prt Errs 0 0
Poll Bus A Parity 0 0
Poll Bus B Parity 0 0
Bad Grant Errs 0 0
Tx BIP-16 Errs 0 0
Rx BIP-16 Errs 0 0
SIU Phase Errs 0 0
Bfrm. Par. Errs 0 0
Rx FIFO Sync Errs 0 0
Poll Clk Errs 0 0
CK 192 Errs 0 0
BXM Errs 0 0

Last Command: dspsloterrs 4

dspslotstatcnf (display statistics enabled for a BXM card slot)

Displays enabled statistics for where a BXM card resides. These statistics are set by the cnfslotstats command, by Cisco WAN Manager, or by node features.

The Owner column shows what set the statistic:

•If the column shows Automatic, it was set by features.

•If the column shows the node name, it was is set by Cisco WAN Manager.

•If the column shows the name of the user, it was set with the cnfslotstats command.

Syntax

dspslotstatcnf <slot>

Parameters

Parameter

Description

<slot>

Specifies the slot where the BXM resides.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX

Yes

Related Commands

cnfslotstats

Example

dspslotstatcnf 2

sw59 TN SuperUser BPX 15 9.3 Apr. 13 2000 14:02 GMT

Statistics Enabled on Slot 2

Statistic Samples Interval Size Peaks Owner
------------------------------------ ------- -------- ---- ----- ----------
1) Standby PRBS Errors 60 0 4 NONE AUTO
2) Rx Invalid Port Errs 60 0 4 NONE AUTO
3) PollA Parity Errors 60 0 4 NONE AUTO
4) PollB Parity Errors 60 0 4 NONE AUTO
5) Bad Grant Errors 60 0 4 NONE AUTO
6) Tx Bip 16 Errors 60 0 4 NONE AUTO
7) Rx Bip 16 Errors 60 0 4 NONE AUTO
8) Bframe parity Errors 60 0 4 NONE AUTO
9) SIU phase Errors 60 0 4 NONE AUTO
10) Rx FIFO Sync Errors 60 0 4 NONE AUTO
11) Poll Clk Errors 60 0 4 NONE AUTO
12) CK 192 Errors 60 0 4 NONE AUTO
13) Monarch Specific Errors 60 0 4 NONE AUTO

This Command: dspslotstatcnf 2

Continue?
Example

Display thresholds for slot 7.

dspslotstatcnf 7

D1.jea TRM SuperUser BPX 8620 9.3 Apr. 13 2000 12:03 GMT

Statistics Enabled on Slot 7

Statistic Samples Interval Size Peaks Owner
----------------------------------- ------- -------- ---- ----- ----------
Standby PRBS Errors 60 0 4 NONE Automatic
Rx Invalid Port Errors 60 0 4 NONE Automatic
Polling Bus A Parity Errors 60 0 4 NONE Automatic
Polling Bus B Parity Errors 60 0 4 NONE Automatic
Bad Grant Errors 60 0 4 NONE Automatic
Transmit Bip 16 Errors 60 0 4 NONE Automatic
Receive Bip 16 Errors 60 0 4 NONE Automatic
Bframe parity Errors 60 0 4 NONE Automatic
SIU phase Errors 60 0 4 NONE Automatic

Last Command: dspslotstatcnf 7

Next Command:

dspslotstathist (display statistics history for a BXM card)

Displays a history the last five occurrences of the slot statistic enabled for a BXM card slot.

You select the statistic from the list displayed when you first enter this command. Use the dspslotstatcnf to display the statistics enabled on the selected slot. Use cnfslotstats to enable a statistic.

Syntax

dspslotstathist <port>

Parameters

Parameter

Description

<slot>

Specifies the slot.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX

Yes

Related Commands

cnfslotstats, dspslotstatcnf

dspsnmp (display SNMP parameters)

Display the following SNMP parameters for the current node:

•Get Community String

•Set Community String

•Trap Community String

•SNMP Set Request Queue Size

•SNMP Queued Request Timeout, in seconds

•SNMP Trap Event Queue Size

Syntax

dspsnmp

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnfsnmp, dspsnmpstats

Example (IGX)

Display the SNMP parameters for the current node.

dspsnmp

sw180 TN Cisco IGX 8420 9.3.p0 Dec. 6 2000 09:03 GMT

Get Community String: audit
Set Community String: private
Trap Community String: private

SNMP Set Request Queue Size: 110
SNMP Queued Request Timeout (secs): 21600
SNMP Trap Event Queue Size: 100

Last Command: dspsnmp

dspsnmpstats (display SNMP statistics)

Displays the following SNMP statistics for the current node:

•SVC Requests Received, the number of SVC requests received.

•SVC Current Queue Length, the number of outstanding SVC requests in the queue.

•SVC Maximum Queue Length, the high watermark of the number of outstanding SVC requests in the queue.

•SVC Requests Timed Out, the number of SVC requests that have timed out.

•Current Trap Managers, the number of managers (up to 10) that are currently registered, their IP addresses and UDP ports.

•Traps Transmitted, the number of traps transmitted.

•TRAP Current Queue Length, the number of outstanding traps in the queue.

•TRAP Maximum Queue Length, the high watermark of the number of outstanding traps in the queue.

•TRAP Queue Events Discarded, the number of traps discarded due to queue overflow.

•Overflow Traps Transmitted, the number of overflow traps transmitted due to queue overflow.

Syntax

dspsnmpstats

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnfsnmp, dspsnmp

Example (IGX)

Display SNMP statistics for the current node.

dspsnmpstats

sw180 TN Cisco IGX 8420 9.3.p0 Dec. 6 2000 09:05 GMT

SVC Requests Received: 0 Traps Transmitted: 0

SVC Current Queue Length: 0 TRAP Current Queue Length: 0
SVC Maximum Queue Length: 0 TRAP Maximum Queue Length: 0
SVC Requests Timed Out: 0 TRAP Queue Events Discarded: 0
Overflow Traps Transmitted: 0

Current Trap Managers: 0/10 Snmp_Trap_Db Ptr: 315687BE

Last Command: dspsnmpstats

dspstatfiles (display TFTP statistics file information)

The dspstatfiles command displays TFTP statistics file information for the current node.

These files contain statistics for switch objects (such as connections, lines, trunks, ports, and so forth) that are reported to the Cisco WAN Manager (CWM) by means of the Trivial File Transport Protocol (TFTP).

Syntax

dspstatfiles [d]
Parameters

Parameter

Description

[d]

Optional. Specifies a detailed display for command output.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX and IGX

No

OK

No

No

Related Commands

dspstatparms, cnfstatparms, cnfnodeparm, dspstatmem

Example

Display TFTP statistics file information for the current node.

Default display example:

dspstatfiles
sw62 TN StrataCom BPX 8620 9.2.36 Jan. 24 2001 01:24 GMT

KEY:A = Active File, S = Switchover occured, R = Stats Reset, K = Stats Skewed
E = Stats just enabled, W = Write Failure, M = Made while standby
FILE NAME FLAGS FILE NAME FLAGS
sw62.0124010030 M
sw62.0124010030 M
sw62.0124010045 M
sw62.0124010100 SE
sw62.0124010115 R
sw62.0000000000 A

Last Command:dspstatfiles

Next Command:

SW CD MAJOR ALARM

Field definitions for default display:
A = Active File - The active file.
S = Switchover occured - A CC switch over occurred while the file was active.
R = Stats Reset - While the file was active a user executed the
"rststats" command, or a there was a time change
large enough to invalidate the current collection.
K = Stats Skewed - Due to cbus message throttling some statistics
polls may have been skipped. The stats were picked
up by a later poll, but due to a file rollover the
stats were skewed into the new active file.
E = Stats just enabled - New statistics were enabled while the file was
active.
W = Write Failure - The file could not be written because the file
size exceeded the remaining memory allocated for
TFTP files. This is an error condition. The
software error 2051 is logged to provide information
about the error condition.
M = Made while standby - The stats in the file were collected by the active
CC while the current CC was standby.

Display detailed TFTP statistics file information for the current node:

dspstatfiles d

sw62 TN StrataCom BPX 8620 9.2.36 Jan. 24 2001 01:10 GMT

File: sw62.0124010030 File: sw62.0124010030

Next File Ptr: 0x307C0EB0 Next File Ptr: 0x307C0A30
Data Block Ptr: 0x307C10F0 Data Block Ptr: 0x307C0C70

File Length: 53 File Length: 53
File Memory: 1152 File Memory: 1152
Data Length: 512 Data Length: 512
Tftp_File_Size Tftp_File_Size
at creation: 573 at creation: 573

Enter Long Fails:0 Enter Long Fails:0
Enter Fails: 0 Enter Fails: 0

This Command:dspstatfiles d

Continue?

SW CD MAJOR ALARM

dspstatmem (display statistics memory use)

Displays memory usage for statistics collection.

This command displays memory usage for statistics collection. It is intended for debugging statistics collection problems, not everyday use. The command shows the amount of controller card memory allocated by the user to statistics display (defaults to 650 Kbytes).

The memory occupied by USER is used for user-enabled statistics. The memory occupied by USER figure is that used by the Cisco WAN Manager user. Memory occupied by AUTO is that used by node features.

Syntax

dspstatmem

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX

No

Example (IGX)

dspstatmem

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 19:29 PST

User Configured Statistics Memory (In bytes) = 624640

Memory Occupied by USER (In bytes) = 0

Memory Occupied by AUTO (In bytes) = 21584

Last Command: dspstatmem

Next Command:

dspsv3 (display WAN manager L3 link control blocks)

Displays the Cisco WAN Manager L3 (Layer 3) Link Control Blocks (LCBs). The dspsv3 command supports the Out-of-Band network management feature, which enables management traffic to be sent over IP to a switch LAN Ethernet interface. This feature reduces the load on trunk bandwidth and node processor times. The dspsv3 command provides a summary of all LCBs in a node and a detailed display of information for a specified LCB.

The dspsv3 command displays the LCBs used by a switch to communicate with one or more SV+ workstations. The display shows whether the out-of-band (lanip) option is being used. The dspsv3 screen distinguishes between the three modes:

•nwip_off

•nwip_on

•lanip

The dspsv3 command displays counts of pending alarms for SONET APS (Automatic Protection Switching) and robust object types that have updated status.

The dspsv3 command supports the Universal Router Module (URM) on the IGX 8400, providing IOS-based voice support and basic routing functions. It consists of an embedded UXM with one internal ATM port and an embedded IOS-based router. The dspsv3 display includes the URM embedded router object and reports router alarm link information.

Syntax

dspsv3 <LCB number>

Parameters

Parameter

Description

LCB number

Number of the Link Control Block for display of detailed information.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

Yes

Related Commands

dsplanip

The chart below provides a description of the fields in the dspsv3 LCB summary display.

Display Fields: Summary

Field

Explanation

Serial Admin

Serial link admin window

LAN Admin

LAN Admin window

LCB

Link Control Block number (0 is the gateway link)

Node

SV+ gateway node number (0 is local IO)

IP

IP address (* indicates nwip is enabled)

Display Fields: Detail

The table below provides a description of the fields in the detailed display for one LCB.

Field

Explanation

LCB

LCB number

Alloc

LCB allocated (1) or no (0)

sv3_lcb_ptr

Address of LCB in memory

IP Address

SV+ IP Address

Response Timer

SV+ Link Response Timer

Idle Timer

Display SV+ Link Idle Timer

Retry Count

SV+ Link Retry Count

Current Protocol State

Link state (idle, reset, transfer, poll)

No. of buffers in the data_q

Messages in the data queue

No. of buffers in the xmit_q

Messages in the transmit queue

No. of buffers in the nflow_q

Messages in the non-flow-controlled queue

Subscribed applications

Applications to which SV+ has subscribed

Update

Robust object types that have updated object(s) status

Pending

Robust object types that have been updated to SV+, and are waiting for an acknowledgment from SV+.

Robust Database Updates data

Robust database update bitmap addresses

Example (IGX)

Display Cisco WAN Manager L3 Link Control Blocks summary.

dspsv3

nsaigx2 TN StrataCom IGX 8420 9.3 Apr. 13 2000 06:11 GMT

Number of Active SV3 Links: 2 Serial Admin: None LAN Admin: None
LCB: 0 Node: 0 IP:*172.16.64.20
LCB: 1 Node: 3 IP:*172.16.64.20

>Last Command: dspsv3
Example (BPX)

Display Cisco WAN Manager L3 Link Control Blocks summary. The summary display shows three Link 1 LCBs, which connect to three different SV+ workstations. The "N" next to the first IP address indicates the nwip_on option. The "L" next to the second address indicates the lanip option. The absence of a symbol on the third line indicates the nwip_off option.

dspsv3

sw248 TN StrataCom BPX 15 9.3 Apr. 13 2000 18:05 GMT

Number of Active SV3 Links: 2 Serial Admin: None LAN Admin: None
LCB: 0 Node: 128 IP:N172.29.9.29
LCB: 1 Node: 128 IP:L172.29.9.53
LCB: 2 Node: 128 IP: 172.29.9.115

Last Command: dspsv3
Example (BPX)

Display Cisco WAN Manager L3 Link Control Block 1. The detailed display shows the state on an individual link control block. The display indicates the use of the lanip option.

dspsv3 1

sw248 TN StrataCom BPX 15 9.3 Apr. 13 2000 18:11 GMT

LCB: 1 Alloc: 1 sv3_lcb_ptr: 31514034
IP Address: 172.29.9.53 (lanip)
Response Timer: 0
Idle Timer: 393
Retry Count: 120
Current Protocol State: SV3_TRANSFER
No. of Buffers in the data_q: 0
No. of Buffers in the xmit_q: 0
No. of Buffers in the nflow_q: 0
Comm Break Alarm: Update: 0, Pending: 0
Comm Break Alarm Bitmaps: Update: 314741FC, Pending: 3147449C

Last Command: dspsv3 1
Example (IGX)

Display Cisco WAN Manager L3 Link Control Block 0 in an IGX node with a Universal Router Module (URM). Note the "Router Object" and "Router Alarm" fields in the second screen display.

dspsv3 0

sw190 TRM Cisco IGX 8420 9.3.2l Oct. 10 2000 04:28 GMT

LCB:0 Alloc:1 sv3_lcb_ptr:314F501A
IP Address:172.29.10.43 (nwip on)
Response Timer:0
Idle Timer:600
Retry Count:3
Current Protocol State:SV3_TRANSFER
No. of Buffers in the data_q:0
No. of Buffers in the xmit_q:0
No. of Buffers in the nflow_q:0
Comm Break Alarm: Update:0, Pending:0
Comm Break Alarm Bitmaps: Update:3149446E, Pending:314941CE

This Command:dspsv3 0

Continue?
--------- Screen 2 ----------

sw190 TRM Cisco IGX 8420 9.3.2l Oct. 10 2000 04:28 GMT

LCB:0 Alloc:1 sv3_lcb_ptr:314F501A
Subscribed Applications:Topology MaintLog
314F504E
Update Pending
Revision: 0 0
Rebuild: 0 0
Subscription: 0 0
Card Obj: 0 314F5FA7 0 314F5FA2 Card Alarm: 0 314F6F24 0 314F6F29
Feeder Obj: 0 314F5FA0 0 314F5FA1 Feeder Alarm: 0 314F6F22 0 314F6F23
Port Obj: 0 314F5750 0 314F5B58 Port Alarm: 0 314F66D2 0 314F6ADA
Conn Obj: 0 314F505E 0 314F53C9 Conn Alarm: 0 314F5FE0 0 314F634B
Cline Obj: 0 314F5734 0 314F573D Cline Alarm: 0 314F66B6 0 314F66BF
Trunk Obj: 0 314F5746 0 314F574B Trunk Alarm: 0 314F66C8 0 314F66CD
Periph. Obj: 0 314F5FAF 0 314F5FAC Periph. Alarm:0 314F6F2E 0 314F6F31
Router Obj: 0 314F5FD6 0 314F5FDB Router Alarm: 0 314F6F5C 0 314F6F61

This Command:dspsv3 0
--------- Screen 3 ----------

sw190 TRM Cisco IGX 8420 9.3.2l Oct. 10 2000 04:28 GMT

LCB:0 Alloc:1 sv3_lcb_ptr:314F501A
Robust Database Updates data:
db_update_flags: 30EBA470 db_pending_flags: 30EBA930
flag_offset_table: 30EBAE30
1:0 2:0 3:0 4:0 5:0 6:0 7:0 8:0 9:0
10:1 11:0 12:36C 13:36D 14:0 15:0 16:372 17:0 18:0
19:372 20:46C 21:0 22:471 23:0 24:0 25:0 26:476 27:0
28:477 29:0 30:478 31:47D 32:48F 33:0 34:0 35:0 36:498
37:0 38:0 39:499 40:0 41:0 42:0 43:0 44:0 45:0
46:49A 47:0 48:0 49:0 50:0 51:0 52:0 53:0 54:0
55:0 56:0 57:0 58:0 59:0 60:4A0 61:0 62:0 63:0
64:0 65:0 66:4A1 67:0 68:0 69:0 70:0 71:0 72:0
73:0 74:0 75:0 76:0 77:0 78:4A2 79:4A3 80:0 81:0
82:0 83:4BF 84:0 85:0 86:0 87:0 88:0 89:0 90:0
91:0 92:0 93:0 94:0 95:0 96:0 97:0 98:0 99:0

This Command:dspsv3 0

--------- Screen 4 ----------

sw190 TRM Cisco IGX 8420 9.3.2l Oct. 10 2000 04:28 GMT

LCB:0 Alloc:1 sv3_lcb_ptr:314F501A
Robust Database Updates data (continued):
flag_offset_table (continued): 30EBAE30
100:0 101:0 102:0 103:0 104:0 105:0 106:0 107:0 108:0
109:0 110:0 111:0 112:0 113:0
VSI Controller:314F6F5A 314F6F58

Last Command:dspsv3 0

dspsvcst (display the voice SVC statistics)

Displays the voice SVC statistics.

Syntax

dspsvcst

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

No

Example

Display the voice SVC statistics for the current node.

dspsvcst

sw91 TN cisco IGX 8410 9.3 Apr. 13 2000 14:11 GMT

Number of Active SVC : 0
Number of SVC Requests : 0
Number of Failed Requests : 0
Last Reason for request failure : 0
Number of Completed SVC Routes : 0
Number of Failed SVC Routes : 0
Number of Deleted SVC(s) : 0
Number of Failed SVC : 0
Max Secs To Perform SVC Route : 0.000
Avg Secs To Perform SVC Route : 0.000

Last Command: dspsvcst

Next Command:

dspswlog (display software error log)

Displays the software errors log. The log contains 12 entries, and when the log is full, additional errors overwrite the oldest entries. The dspswlog command displays contains non-fatal entries. Use the dspabortlog command to display a new log containing abort entries.

A lighted icon "SW" at the bottom of the command line interface indicates that a software error has been logged. Unrelated to this feature, but also at the bottom of the command line interface, the "CD" icon indicates a card or hardware error, while the "AB" icon indicates an abort error:

SW

AB

CD

Job 1

Syntax

dspswlog [<d> | <number> | <c> ]

Parameters

Parameter

Description

<d>

Displays the detailed version of the log, including stack dumps. Page through the detailed version of the log using the arrow keys or the Return key.

<number>

When an entry number is entered (found under the No. column), displays the detailed version of a specific entry in the log.

<c>

Clears the log. Optionally, you can use the clrabortlog command.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

clrswlog, dspabortlog, clrabortlog

Display Fields

Field

Description

No.

Error entries in the table numbered from 1-12.

Type Error

The entry identifier. For dspswlog, the identifier is "error." Occasionally, the identifier "BadType," is displayed, indicating a problem within the table itself.

Number

The number that identifies a specific error problem.

Data (Hex)

A 4-byte field containing information that may be useful in solving a problem. It is different for every error number.

PC (Hex)

Program Counter. The address of the place in memory where the software was running when the error was logged; this identifies where the problem was detected.

PROC

Process or Task. This field indicates which process was running when the problem occurred. Use the dspprf command to display all of the tasks.

SwRev

Switch software version operating on this node.

Date

Date of the error.

Time

Time of the error.

Example

Display the software error log.

dspswlog

igxr02 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 13:31 PST

Active Control Card's Software Log
No. Type Number Data(Hex) PC(Hex) PROC SwRev Date Time
1. Error 509 00000000 303AE716 CBUS 9.3.2V 01/16/01 14:36:26
2. Error 101 07000000 301EECCC CBUS 9.3.2V 01/16/01 14:36:26
3. Error 509 00000000 303AE716 CBUS 9.3.2V 01/16/01 14:36:27
4. Error 101 07000000 301EECCC CBUS 9.3.2V 01/16/01 14:36:27
5. Error 3018 00000012 30229F02 TRNS 9.3.2V 01/16/01 15:30:26
6. Error 3018 00000012 301F57B0 TRNS 9.3.2V 01/16/01 15:30:26
7. Error 254 000000CE 303CE002 RSRC 9.3.2V 01/16/01 15:37:53
8. Error 254 000000CE 303CE002 RSRC 9.3.2V 01/16/01 15:37:53
9. Error 254 000000CE 303CE002 RSRC 9.3.2V 01/16/01 15:37:53
10. Error 254 000000CE 303CE002 RSRC 9.3.2V 01/16/01 15:37:53
11. Error 254 000000CE 303CE002 RSRC 9.3.2V 01/16/01 15:37:53
12. Error 9000 14030098 30546430 TRNS 9.3.2V 01/18/01 13:19:41

Last Command: dspswlog

dsptcpparm (display TCP parameters)

The dspftcpparm command displays the TCP bandwidth throttle parameter.

Syntax

dsptcpparm

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

cnftcpparm

Example (IGX)

cc2 LAN SuperUser IGX 8430 9.3 Apr. 13 2000 11:42 PST

NWIP Bandwidth Throttle (Kbytes/sec): 32

Last Command: dsptcpparm

Next Command:

dsptermcnf (display terminal port configurations)

Displays the configuration for the control port and auxiliary port at a node. It includes all the asynchronous communications parameters that are specified by the cnfterm command.

Syntax

dsptermcnf

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnfterm, cnftermfunc (a SuperUser command), dsptermfunc

Example (BPX)

Display the terminal port configuration data.

dsptermcnf

batman TN SuperUser BPX 8620 9.3 Apr. 13 2000 02:55 PST

Control port Auxiliary port

Baud Rate: 9600 Baud Rate: 9600

Parity: None Parity: None
Number of Data Bits: 8 Number of Data Bits: 8
Number of Stop Bits: 1 Number of Stop Bits: 1
Output flow control: XON/XOFF Output flow control: XON/XOFF
Input flow control: XON/XOFF Input flow control: XON/XOFF
CTS flow control: No CTS flow control: Yes
Use DTR signal: Yes Use DTR signal: Yes

Last Command: dsptermcnf

Next Command:

dsptermfunc (display terminal port functions)

Displays the port functions configured by the cnftermfunc command.

Syntax

dsptermfunc

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnfterm, cnftermfunc, dsptermcnf

Example (BPX)

Display the terminal port configuration data. The highlighted or reverse video items are the currently selected options.

dsptermfunc

swstorm TN SuperUser BPX 8620 9.3 Apr. 13 2000 09:42 PST

Control port Auxiliary port

1. VT100/StrataView 1. Okidata 182 Printer
2. VT100 2. Okidata 182 Printer with LOG
3. VT100
4. Alarm Message Collector
5. External Device Window
6. Autodial Modem

Last Command: dsptermfunc

Next Command:

dsptrkbob (display trunk breakout box)

Displays the state of all inputs from subrate line equipment to an IGX node and the state of all outputs from the node to the subrate line equipment. Display updates can occur at an optional, user-specified interval. Otherwise, the display remains on-screen until Delete is pressed or the display times out. The default interval for updating the display is every 5 seconds. If a trunk is disabled, its number appears in dim, reverse video. See cnftrkict for configuration details.

Syntax

dsptrkbob <line> [interval]

Parameters

Parameter

Description

<line>

Specifies the subrate trunk.

[interval]

The number of seconds between updates of the breakout box display.
Range: 1-60

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

IGX

Yes

Related Commands

cnftrkict, dsptrkict

Example

Display the breakout for subrate trunk 9.

dsptrkbob 9

beta TRM YourID:1 IGX 8430 9.3 Apr. 13 2000 15:15 MST

Packet Line: 9
Interfaces: X.21 DTE

Inputs from Line Equipment Outputs to Line Equipment
Lead Pin State Lead Pin State Lead Pin State Lead Pin State RxD 4/11 Idle TxD 2/9 Active I/DSR 5/12 On C/DTR 3/10 On S/RxC 6/13 Active

Last Command: dsptrkbob 9

Hit DEL key to quit:

dsptrkcnf (display trunk configuration)

Displays trunk configuration. The parameter values that dsptrkcnf displays have been set by using cnftrk or are default values. See Table 4-37 for default physical trunk statistics and Table 4-38 for default virtual trunk statistics.

The default values for statistical reserves can accommodate sufficient bandwidth for control traffic. The statistical reserve can be changed. However, if you modify the reserve below recommended values, a warning message is displayed. For example, if the statistical reserve is modified below 1000 cps for "upped" T1/E1/T3/OC-3/OC-12 physical trunks and 300 for T1/E1 virtual trunks, this warning message is displayed:

"WARNING: Changing stats reserve < {1000 | 300 } may cause a drop in CC traffic"

If cost-based routing is configured, dsptrkcnf displays the cost of a trunk. Configure the administrative cost of a trunk by using cnftrk.

Table 4-37 Default Statistical Reserves for Physical Trunks

BNI

BXM

UXM

ALM

NTM

IMA-T1/E1

N/A

N/A

5000 cps > T2, E2

1000 cps < T2, E2

N/A

N/A

T1/E1

N/A

N/A

1000 cps

N/A

1000 cps

T3/E3

5000 cps

5000 cps

5000 cps

5000 cps

N/A

OC3

5000 cps

5000 cps

5000 cps

N/A

N/A

OC12

N/A

5000 cps

N/A

N/A

N/A

T2 = 14490 cps (96 DS0s)

E2 = 19900 cps

N/A = not available

Table 4-38 Default Statistical Reserves for Virtual Trunks

BNI

BXM

UXM

T1/E1

N/A

N/A

300 cps

T3/E3

1000 cps

1000 cps

1000 cps

OC3

1000 cps

1000 cps

1000 cps

OC12

N/A

1000 cps

N/A

N/A = not available

Syntax

dsptrkcnf <slot.port>[.vtrk]

Parameters

Parameter

Description

<slot.port>

Specifies the physical slot and port number of the trunk.

[.vtrk]

Specifies the virtual trunk number. The maximum value on a node is 32. The maximum on a T3 or E3 line is 32. The maximum for user traffic on an OC-3/STM1 trunk is 11.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnftrk

Example (BPX)

Display the configuration for trunk 13.6.1.

dsptrkcnf 13.6.1

BPX02 TN Cisco BPX 8620 9.3.3W Aug. 13 2001 11:40 PDT

TRK 13.6.1 Config OC3 [4528 cps] BXM slot: 13
Transmit Rate: 4528 VPC Conns disabled: --
Protocol By The Card: -- Line framing: STS-3C
VC Shaping: No coding: --
Hdr Type NNI: No recv impedance: --
Statistical Reserve: 1000 cps cable type: --
Idle code: 7F hex length: --
Connection Channels: 256 Pass sync: No
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No
Restrict CC traffic: No HCS Masking: Yes
Link type: Terrestrial Payload Scramble: Yes
Routing Cost: 10 Frame Scramble: Yes
F4 AIS Detection: Yes Vtrk Type / VPI: CBR / 1
Incremental CDV: 0
Deroute delay time: 0 seconds

Last Command: dsptrkcnf 13.6.1

Next Command:

Example (BPX)

Display the configuration for BXM 11.2 trunk.

dsptrkcnf 11.2

sw53 TN Cisco BPX 8620 9.3.2J Oct. 31 2000 13:41 GMT

TRK 11.2 Config OC3 [353207cps] BXM slot: 11
Transmit Rate: 353208 VPC Conns disabled: No
Protocol By The Card: No Line framing: STS-3C
VC Shaping: No coding: --
Hdr Type NNI: Yes recv impedance: --
Statistical Reserve: 5000 cps cable type: --
Idle code: 7F hex length: --
Connection Channels: 256 Pass sync: No
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No
SVC Vpi Min: 0 HCS Masking: Yes
SVC Channels: 0 Payload Scramble: Yes
SVC Bandwidth: 0 cps Frame Scramble: Yes
Restrict CC traffic: No Virtual Trunk Type: --
Link type: Terrestrial Virtual Trunk VPI: --
Routing Cost: 10 Deroute delay time: 0 seconds

Last Command: dsptrkcnf 11.2
Example (BPX)

Display the configuration for BXM T3 virtual trunk.

dsptrkcnf 3.2.3

bpx04 VT Cisco BPX 8620 9.3.2V Jan. 19 2001 08:14 PST

TRK 3.2.3 Config T3 [2867 cps] BXM slot: 3
Transmit Rate: 3000 VPC Conns disabled: --
Protocol By The Card: -- Line framing: PLCP
VC Shaping: No coding: --
Hdr Type NNI: No recv impedance: --
Statistical Reserve: 250 cps cable type: --
Idle code: 7F hex length: 0-225 ft.
Connection Channels: 256 Pass sync: No
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No
Restrict CC traffic: No HCS Masking: Yes
Link type: Terrestrial Payload Scramble: No
Routing Cost: 21 Frame Scramble: --
Virtual Trunk Type: CBR
Virtual Trunk VPI: 3
Deroute delay time: 0 seconds

Last Command: dsptrkcnf 3.2.3
Example (IGX)

Display the configuration for trunk 5.1. The trunk is on a UXM OC-3 card set in an IGX node.

dsptrkcnf 5.1

sw180 TN Cisco IGX 8420 9.3.g0 Oct. 20 2000 11:41 GMT

TRK 5.1 Config OC3 [353207cps] UXM slot:5
Transmit Trunk Rate: 353208 cps Connection Channels: 256
Rcv Trunk Rate: 353207 cps Gateway Channels: 200
Pass sync: Yes Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Loop clock: No Frame Scramble: Yes
Statistical Reserve: 5000 cps Deroute delay time: 0 seconds
Header Type: NNI VC Shaping: No
VPI Address: 1 VPC Conns disabled: No
Routing Cost: 10
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Line framing: STS-3C
HCS Masking: Yes
Payload Scramble: Yes

Last Command: dsptrkcnf 5.1
Example (IGX)

Display the configuration for trunk 14.2 on a UXM card.

dsptrkcnf 14.2

sw176 TN Cisco IGX 8420 9.3.a1 Aug. 13 2001 13:08 PDT

TRK 14.2 Config T3/636 [96000 cps] UXM slot:14
Transmit Trunk Rate: 96000 cps Payload Scramble: No
Rcv Trunk Rate: 96000 cps Connection Channels: 256
Pass sync: Yes Gateway Channels: 200
Loop clock: No Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Statistical Reserve: 5000 cps Incremental CDV: 0
Header Type: NNI Deroute delay time: 0 seconds
VPI Address: 1 VC Shaping: No
Routing Cost: 10 VPC Conns disabled: No
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Line framing: PLCP
Line cable length: 0-225 ft.
HCS Masking: Yes

Last Command: dsptrkcnf 14.2

Next Command:
Example (IGX)

Display the configuration for virtual trunk 4.3.1. The ILMI protocol is running on the UXM interface card.

dsptrkcnf 4.3.1

igxf3 VT Cisco IGX 8420 9.3.10 July 26 2000 23:40 PST

TRK 4.3.1 Config OC3 [2867 cps] UXM slot:4
Transmit Trunk Rate: 3000 cps Gateway Channels: 200
Rcv Trunk Rate: 2867 cps Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Pass sync: No Virtual Trunk Type: CBR
Loop clock: No Virtual Trunk VPI: 10
Statistical Reserve: 1000 cps Frame Scramble: Yes
Header Type: UNI Deroute delay time: 0 seconds
Routing Cost: 10 VC Shaping: No
Idle code: 7F hex ILMI run on the card: Yes
Restrict PCC traffic: No
Link type: Terrestrial
Line framing: STS-3C
HCS Masking: Yes
Payload Scramble: Yes
Connection Channels: 256

Last Command: dsptrkcnf 4.3.1

Example (IGX)

Display the T1 NTM configuration for trunk 14.

dsptrkcnf 14

sw108 VT Cisco IGX 8420 9.3.2J Oct. 31 2000 13:20 GMT

TRK 14 Config T1/24 [8000 pps] NTM slot:14
Line DS-0 map: 0-23
Pass sync: Yes
Loop clock: No
Statistical Reserve: 1000 pps
Routing Cost: 10
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Line framing: D4
Line coding: B8ZS
Line cable type: ABAM
Line cable length: 0-133 ft.
Traffic: V,TS,NTS,FR,FST
Deroute delay time: 0 seconds

Last Command: dsptrkcnf 14

dsptrkcons (display trunk connection counts)

Displays the number of connections routed over the specified trunk. This command applies to physical and virtual trunks. It displays the total number of connections being carried by the specified trunk. The connections are summed for each terminating node in the network and lists the connection count for the transmit direction (out of the node).

This command is useful in determining the source of dropped packets in cases where the specified trunk is oversubscribed:

Step 1 Use the dsptrks command to list the trunks that originate at each node.

Step 2 Next, use the dsptrkcons to determine the number of connections (the more connections per trunk the greater the possibility of over-subscription).

Step 3 Then use the dsprts command to identify any through nodes (where the trunk is not terminated).

Step 4 Finally, look at the utilization factor for each of these lines using the dsputl and dspdutl commands.

Syntax

dsptrkcons <line number>

Parameters

Parameter

Description

<line number>

Trunk number.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

dsptrkmcons, dspplnmcons

Example (BPX)

dsptrkcons 5.1

batman TN SuperUser BPX 15 9.3 Apr. 13 2000 15:57 GMT

Connection Counts For TRK 5.1

Src Node Conns Src Node Conns Src Node Conns Src Node Conns
batman 1765

Last Command: dsptrkcons 5.1
Next Command:

dsptrkerrs (display trunk errors)

Displays the accumulated line error counts, by failure type, for the specified trunk(s). If you do not enter a trunk number, a one-line summary of errors for all trunks at the local node is displayed. If you enter a specific trunk number with the command, a detailed analysis, including error threshold (ETH), is displayed. Disabled trunks have their trunk number displayed in dim, reverse video on the screen.

Error rates to be concerned about are any that are incrementing. For example, a Y-red switchover may cause some statistical errors. These are expected. But if there are errors happening in a stable situation, then they indicate a problem.

The clrtrkerrs command resets all error counts to 0.

Syntax

dsptrkerrs
or

dsptrkerrs [slot | slot.port]
or
dsptrkerrs <slot.port.vtrk>

Parameters

Parameter

Description

trunk number

Specifies a trunk for the error display. Without a trunk number, a summary for all physical trunks appears. To display error statistics for virtual trunks, however, you must specify a trunk number in the form slot.port.vtrk. For all physical trunk types, the trunk number is optional: entering dsptrkerrs without a trunk number lists all trunks with errors. For standard trunks, the form of a specific trunk is slot for single-trunk cards or slot.port for multitrunk cards.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

clrtrkerrs, prttrkerrs

Display Fields

Line Type

Error

Explanation

All except ATM

Bipolar errors

Number of times two consecutive pulses have the same polarity (AMI coding only).

Frame slips

Number of times a frame is discarded to re-establish synchronization.

Out of frames

Number of times a loss-of-frame synchronism is detected on this circuit line.

Loss of signal

Number of times the signal level at the circuit line input went below the minimum acceptable level.

Frame bit errors

Number of times the frame bit failed to alternate (frame error).

CRC errors

Number of times the generated CRC character did not match the received CRC character (applies only if CRC checking is enabled).

Out of MFrames

Number of times a multiframe synch error was detected (E1 lines only).

AIS - 16

Number of times the Alarm Information Signal (Blue signal) was received.

Only ATM

Out of Frames

Number of times a momentary loss of DS3 frame alignment was detected.

Loss of sync (XX)

Number of times a loss of DS3 frame alignment lasting more than XX seconds was detected.

Packet Error

Number of CRC errors for a packet address.

Line Code Errors

Number of B3ZS code errors detected.

P-bit Parity Errors

Number of parity errors for the DS3 parity bit (P-bit) sequence.

C-bit Parity Errors

Number of parity errors for the DS3 control bit (C-bit) sequence.

Comm Fails

Number of BCC failed to communicate to the other node.

Loss of signal

Number of times the signal level at the trunk line input went below the minimum acceptable level.

Only ATM

AIS (BLU)

Number of times the Alarm Information Signal (Blue signal) was received.

Out of MFrames

Number of times a loss-of-frame synchronism in the DS3 multiframe alignment was detected.

Remote Oof

Number of times the DS3 remote alarm (indicating remote end was out of frame alignment) was received.

Example (BPX)

Display a summary of all trunk errors at the local node.

dsptrkerrs

sw53 VT Cisco BPX 8620 9.3.2o Dec. 6 2000 09:13 GMT

Total Errors

Code Out of Loss of HCS Unavail Ln Unav Path Un Tx Cell
TRK Errors Frames Signal Errors Seconds Seconds Seconds Dropped
11.2 - 0 0 0 - 0 0 0

Last Command: dsptrkerrs
Example (BPX)

Display a detailed description of the errors for trunk 11.2.

dsptrkerrs 11.2

------------------------------------SCREEN 1----------------------------------
sw53 VT Cisco BPX 8620 9.3.2o Dec. 6 2000 09:20 GMT

Trunk 11.2 Status: Clear - OK Clrd: 12/06/00 06:00:38
Type Count ETS Status Type Count ETS Status
Out of Frms 0 0 Comm Fails 0 -
Loss of Sig 0 0 Loss of Sig (RED) 0 -
AIS (BLU) 0 -
Out of Frms (RED) 0 -
Rmt Oof (YEL) 0 -

This Command: dsptrkerrs 11.2

Continue? y

------------------------------------SCREEN 2----------------------------------
sw53 VT Cisco BPX 8620 9.3.2o Dec. 6 2000 09:22 GMT

Trunk 11.2 Status: Clear - OK Clrd: 12/06/00 06:00:38
Type Count ETS Status Type Count ETS Status
HCS Errors 0 0
BXM:Tx NTS CDs 0 0
BXM:Tx HP CDs 0 0
BXM:Tx V CDs 0 0
BXM:Tx TS CDs 0 0
BXM:Tx BDA CDs 0 0
BXM:Tx BDB CDs 0 0
BXM:Tx CBR CDs 0 0
BXM:Tx ABR CDs 0 0
BXM:Tx VBR CDs 0 0
Line Unavail Secs 0 0
Path Unavail Secs 0 0

Last Command: dsptrkerrs 11.2
Example (IGX)

Display a summary description of the errors for trunk 16.

dsptrkerrs 16

sw108 VT Cisco IGX 8420 9.3.2o Dec. 6 2000 09:10 GMT

Total Statistical Errors
TxPkts
Code RxPkts Out of LossOf Frame CRC /Cells Packet Packet
PLN Errors Droppd Frames Signal BitErs Errors Droppd Errors Oofs
4.2 - - - - - - 0 - -
4.4 - - - - - - 0 - -
14 0 - 0 0 0 0 0 0 0

Last Command: dsptrkerrs
Example (IGX)

Display a detailed description of the errors for trunk 14.

dsptrkerrs 14

sw108 VT Cisco IGX 8420 9.3.2o Dec. 6 2000 09:16 GMT

TRK 14 Clear - OK Clrd:12/04/00 17:26:00
Statistical Alarm Count ETS Status Integrated Alarm Count ETS Status
Bipolar Err 0 0 Comm Fails 3 -
Out of Frms 0 0 Loss of Sig (RED) 3 -
Loss of Sig 0 0 AIS (BLUE) 0 -
Frame BitErrs 0 0 Out of Frms (RED) 1 -
CRC Err 0 0 Rmt OOF (YEL) 0 -
Tx Voice Pkt Drp 0 0 Packet Oofs (RED) 1 -
Tx TS Pkt Drp 0 0 Rmt Alarms (YEL) 0 -
Tx Non-TS Pkt Drp 0 0 VTRK Path Fails 0 -
Tx CC Pkt Drp 0 0
Tx BData A Pkt Drp 0 0
Tx BData B Pkt Drp 0 0
Packet Err 0 0
Packet Oofs 0 0 Last failure time: 12/05/00 15:19:34

Last Command: dsptrkerrs 14

dsptrkict (display trunk interface control templates)

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

•Specified line.

•Associated leads and their status (that is, on or off)

•Whether output follows a local input.

•Name of the local or remote input lead that the output lead follows.

To see a list of configurable outputs, and information on how to configure an output, see the cnftrkict command. The numbers of disabled trunks are displayed in dim, reverse video on the screen.

Syntax

dsptrkict <line>

Parameters

Parameter

Description

<line>

Trunk number.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

No

No

IGX

No

Related Commands

cnftrkict, prttrkict

Example

Display subrate for the trunk 9 interface control template.

dsptrkict 9

beta TRM YourID:1 IGX 8430 9.3 Apr. 13 2000 15:15 MST

Trunk: 9
Interface: X.21 DTE

Interface Control Template for Trunk Line

Lead Output Value Lead Output Value
C/DTR ON

Last Command: dsptrkict 9

Next Command:

dsptrkmcons (display trunk connection counts by master node)

Displays the number of connections routed over the specified trunk (BNI) by the master node. Rather than showing the remote end of the connection, the display lists the connection and the node that owns that connections.

This command is useful in determining the source of dropped packets in cases where the specified trunk is oversubscribed.

Step 1 First use the dsptrkmcons command to list the trunks that originate at each node (the more connections per trunk, the greater the possibility of over-subscription).

Step 2 Next, use the dsprts command to identify any through-nodes (on which the trunk is not terminated).

Step 3 Finally, look at the utilization for each of these lines by using the dsputl and dspdutl commands.

Syntax

dsptrkmcons <line number>

Parameters

Parameter

Description

<line number>

Specified trunk number. Note that in a BPX, the line number must include a port number.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

dsptrkcons

Example (BPX)

dsptrkmcons 6.1

sw81 TN SuperUser BPX 15 9.3 Apr. 13 2000 13:16 PST

Connection Counts For TRK 6.1

Mst Node Conns Mst Node Conns Mst Node Conns Mst Node Conns
sw86 26

Last Command: dsptrkmcons 6.1

Next Command:

dsptrkred (display ATM trunk redundancy)

Displays the backup and primary cards for a trunk.

Syntax

dsptrkred [trunk]

Parameters

Parameter

Description

ATM trunk number

Specifies the slot number of the primary or backup ATM card set to display. Without this optional entry, the screen displays all primary and backup ATM trunks.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-4

No

No

BPX, IGX

No

Related Commands

addtrkred, deltrkred

Example (IGX)

Display all ATM trunks with redundancy.

dsptrkred

beta TRM YourID:1 IGX 8430 9.3 Apr. 13 2000 15:15 MST

ATM Line Backup ATM Line 4 5 7 8

Last Command: dsptrkred

Next Command:

dsptrks (display trunks)

Displays basic trunk information for all trunks on a node. This command applies to both physical and virtual trunks. The displayed information consists of:

•Trunk number, including the virtual trunk number, if applicable

•Line type (E1, T3, or OC-3, for example)

•Alarm status

In addition, for trunks that have been added to the network by using the addtrk command, the information includes the node name and trunk number at the other end. Trunks that have a "-" in the Other End column have been upped by using uptrk but not yet added on both ends by using addtrk. For disabled trunks, the trunk numbers appear in reverse video on the screen.

For UXM trunks with ATM Forum IMA-compliant trunks, a trunk is displayed in dsptrks as:

<slot>.<primary_port>x<num ports>

For example, an IMA trunk would display in the TRK column in the dsptrks screen as the following:

5.1x4

In this case, 5.1x4 indicates an ATM Forum-compliant IMA trunk 5.4, which consists of four physical lines. To see all physical lines belonging to this IMA trunk, you can enter the dspphyslns command.

The dsptrks commands displays all interface shelves attached to a BPX or an IGX routing hub that use the AAL5 protocol.

For IMA trunks, you can configure non-consecutive physical lines. Non-consecutive physical lines are supported.

For VSI "dedicated" virtual trunks, dsptrks will indicate this.

Syntax

dsptrks

Related Commands

addtrk, deltrk, dntrk, uptrk

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Example (BPX)

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

dsptrks

sw288 TN SuperUser BPX 8620 9.3 Apr. 13 2000 15:39 GMT

TRK Type Current Line Alarm Status Other End
4.1 OC-12 Clear - OK SIMFDR(AAL5)
11.2 T3 Clear - OK redhook/14
11.3 T3 Clear - OK sw113/16

Last Command: dsptrks

Next Command:
Example (BPX)

Display information on the trunk configuration and alarm status for the trunks at a node. The trunk numbers with three places (slot.port.vrtk) represent virtual trunks; for example—trunk 13, port 3, virtual trunk 12. Also, on trunk 4, slot 8, is a simulated interface shelf "SIMFDR0", with interface shelf type of AAL5.

dsptrks

sw288 TN SuperUser BPX 8620 9.3 Apr. 13 2000 23:03 GMT

TRK Type Current Line Alarm Status Other End
2.1 T3 Clear - OK pswbpx1/1.2
4.8 T3 Clear - OK SIMFDR0 (AAL5)
13.3.12 OC-3 Clear - OK rita/4.2.10

Last Command: dsptrks

Next Command:
Example (BPX)

Display information on the trunk configuration and alarm status for the trunks at a node. The trunk numbers with three places (slot.port.vrtk) represent virtual trunks. An ATM Forum-compliant trunk is configured on slot 11, which has a primary port of 1 and 4 physical lines.

dsptrks

sw53 TN SuperUser BPX 8620 9.3 Apr. 13 2000 23:03 GMT

TRK Type Current Line Alarm Status Other End
2.1 T3 Clear - OK pswbpx1/1.2
4.8 T3 Clear - OK SIMFDR0 (AAL5)
11.1x4 T1/92 Clear - OK a1c/3.5x4
15.1 OC-3 Clear - OK alc/3.5x4

Last Command: dsptrks

Next Command:
Example (IGX)

Display information on the trunk configuration and alarm status for the trunks at an IGX node showing IMA-compliant links on slot 11.

dsptrks

oo1 TN SuperUser IGX 8430 9.3 Apr. 13 2000 23:03 GMT

TRK Type Current Line Alarm Status Other End
6.1 OC-3 Clear - OK oo1p(AAL5)
8.5 T3 Clear - OK n4b/4.5
8.6 E3/530 Clear - OK alc/15
10 T3/240 Clear - OK alc/3.5x4
11.1x4 T1/92 Clear - OK alc/3.5x4
15.1 OC-3 Clear - OK n1a/11.3
15.2 OC-3 Clear - OK n2b/5.3

Last Command: dsptrks
Next Command:
Example (IGX)

Display information on the feeders attached to an IGX 8400 routing hub. (The SES feeder uses the AAL5 protocol to communicate with the routing network.) Feeder names appear in the Other End field on the dsptrks screen on an IGX routing hub.

dsptrks

oo1 TN SuperUser IGX 8430 9.3 Apr. 13 2000 23:03 GMT

TRK Type Current Line Alarm Status Other End
13 E1 Clear - OK igx1/12
14.1 OC-3 Clear - OK ases1 (AAL5)

Last Command: dsptrks

Next Command:
Example

Display trunks including virtual trunks. A VSI trunk is on trunk 2.1.1; dsptrks indicates this with "VSI trunk."

dsptrks

TRK Type Current Line Alarm Status Other End
1.1 E3 Clear - OK sw58/1.1
1.2 E3 Clear - OK sw183(AXIS)
2.1.1 OC-3 Clear - OK VSI trunk
Example (BPX)

The dsptrks screen shows VSI trunks 4.1, 4.2, and 4.3 with the "Other End" of 4.1 reading "VSI (VSI)". A typical dsptrks screen example showing some VSI trunks configured follows:

dsptrks

n4 TN SuperUser BPX 15 9.3 Apr. 13 2000 16:45 PST

TRK Type Current Line Alarm Status Other End
2.1 OC-3 Clear - OK j4a/2.1
3.1 E3 Clear - OK j6c(AXIS)
5.1 E3 Clear - OK j6a/5.2
5.2 E3 Clear - OK j3b/3
5.3 E3 Clear - OK j5c(IPX/AF)
6.1 T3 Clear - OK j4a/4.1
6.2 T3 Clear - OK j3b/4
4.1 OC-3 Clear - OK VSI(VSI)
4.2 OC-3 Clear - OK VSI(VSI)
4.3 OC-3 Clear - OK VSI(VSI)

Last Command: dsptrks

dsptrkstatcnf (display statistics enabled for a trunk)

Displays the enabled statistics a physical or virtual trunk.

This command is intended for debugging statistics collection problems. It displays the trunk statistics set by the cnftrkstats command, by Cisco WAN Manager, or by node features. The Owner column shows the source of the specification. If the Owner column shows AUTO, the node's features determined the statistics. If the Owner column shows the name of the node, Cisco WAN Manager determined the statistics. If the Owner column shows USER, the cnftrkstats command was used to configure the statistics. The display may take up to four screens to display completely depending on statistics displayed.

Syntax

dsptrkstatcnf <line>

Parameters

Parameter

Description

<line>

Specifies the trunk: line can have the form slot, slot.port or slot.port.vtrk. The format depends on whether the trunk card has one or more physical ports and whether the trunk is a virtual trunk.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX

Yes

Related Commands

cnftrkstats

Example (BPX)

dsptrkstatcnf 11.2

sw53 TN Cisco BPX 8620 9.3.m0 Dec. 12 2000 13:25 GMT

Statistics Enabled on Trunk 11.2

Statistic Samples Interval Size Peaks Owner
------------------------------------ ------- -------- ---- ----- ----------
28) Tx NTS Cells Discarded 60 0 4 NONE AUTO
29) Tx Hi-Pri Cells Discarded 60 0 4 NONE AUTO
30) Tx Voice Cells Discarded 60 0 4 NONE AUTO
31) Tx TS Cells Discarded 60 0 4 NONE AUTO
32) Tx BData A Cells Discarded 60 0 4 NONE AUTO
33) Tx BData B Cells Discarded 60 0 4 NONE AUTO
34) Tx CBR Cells Discarded 60 0 4 NONE AUTO
35) Tx ABR Cells Discarded 60 0 4 NONE AUTO
36) Tx VBR Cells Discarded 60 0 4 NONE AUTO

Last Command: dsptrkstatcnf 11.2

dsptrkstathist (display statistics history for a trunk)

Displays a history of configured statistics for a physical or virtual trunk. The command is used for statistics debugging. It displays the data for the last five occurrences of the selected statistic. The available trunk statistics appear on screen upon entry of the dsptrkstathist command. (The cnftrkstats command enables individual statistics. The dsptrkstatcnf command displays the enabled statistics for a trunk.)

Syntax

dsptrkstathist <trunk>

Parameters

Parameter

Description

<trunk>

Specifies the trunk in one of the following formats:
slot for a trunk card with one line
slot.port for a trunk card with more than one line
slot.port.vtrk for a virtual trunk

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX

Yes

Related Commands

cnftrkstats, dsptrkstatcnf

Example (BPX)

dsptrkstathist 11.2

------------------------------------SCREEN 1----------------------------------
sw53 TN Cisco BPX 8620 9.3.m0 Dec. 12 2000 13:42 GMT

Virtual Interface Statistic Types

7) Tx Voice Cells Served 32) Tx BData A Cells Discarded
8) Tx TS Cells Served 33) Tx BData B Cells Discarded
9) Tx NTS Cells Served 34) Tx CBR Cells Discarded
10) Tx Hi-Pri Cells Served 35) Tx ABR Cells Discarded
11) Tx BData A Cells Served 36) Tx VBR Cells Discarded
12) Tx BData B Cells Served 37) Egress NTS Cells Rx
19) Tx CBR Cells Served 38) Egress Hi-Pri Cells Rx
20) Tx VBR Cells Served 39) Egress Voice Cells Rx
21) Tx ABR Cells Served 40) Egress TS Cells Rx
28) Tx NTS Cells Discarded 41) Egress BData A Cells Rx
29) Tx Hi-Pri Cells Discarded 42) Egress BData B Cells Rx
30) Tx Voice Cells Discarded 43) Egress CBR Cells Rx
31) Tx TS Cells Discarded 44) Egress ABR Cells Rx

This Command: dsptrkstathist 11.2

Continue? y

------------------------------------SCREEN 2----------------------------------
sw53 TN Cisco BPX 8620 9.3.m0 Dec. 12 2000 13:42 GMT

Virtual Interface Statistic Types

45) Egress VBR Cells Rx 58) Tx Q10 Cells Served
46) Total Cells Tx from port 59) Tx Q10 Cells Discarded
47) Cells RX with CLP0 60) Egress Q10 Cells Rx
48) Cells Rx with CLP1 61) Tx Q11 Cells Served
49) Cells RX Discard with CLP0 62) Tx Q11 Cells Discarded
50) Cells RX Discard with CLP1 63) Egress Q11 Cells Rx
51) Cells TX with CLP0 64) Tx Q12 Cells Served
52) Cells TX with CLP1 65) Tx Q12 Cells Discarded
53) BXM: Total Cells RX 66) Egress Q12 Cells Rx
54) Ingress OAM Cell Count 67) Tx Q13 Cells Served
55) Egress OAM Cell Count 68) Tx Q13 Cells Discarded
56) Ingress RM cell count 69) Egress Q13 Cells Rx
57) Egress RM cell count 70) Tx Q14 Cells Served

This Command: dsptrkstathist 11.2

Continue? y

------------------------------------SCREEN 3----------------------------------
sw53 TN Cisco BPX 8620 9.3.m0 Dec. 12 2000 13:42 GMT

Virtual Interface Statistic Types

71) Tx Q14 Cells Discarded
72) Egress Q14 Cells Rx
73) Tx Q15 Cells Served
74) Tx Q15 Cells Discarded
75) Egress Q15 Cells Rx

This Command: dsptrkstathist 11.2
Example (IGX)

dsptrkstathist 5.1

------------------------------------SCREEN 1----------------------------------
sw180 TN Cisco IGX 8420 9.3.p7 Dec. 12 2000 14:07 GMT

Virtual Interface Statistic Types

1) QBIN: Voice Cells Tx to line 14) QBIN: Tx BData A Cells Discarded
2) QBIN: TimeStamped Cells Tx to ln 15) QBIN: Tx BData B Cells Discarded
3) QBIN: NTS Cells Tx to line 16) QBIN: Tx CBR Cells Discarded
4) QBIN: Hi-Pri Cells Tx to line 17) QBIN: Tx ABR Cells Discarded
5) QBIN: BData A Cells Tx to line 18) QBIN: Tx nrt-VBR Cells Discarded
6) QBIN: BData B Cells Tx to line 19) QBIN: Tx NTS Cells Received
7) QBIN: Tx CBR Cells Served 20) QBIN: Tx Hi-Pri Cells Received
8) QBIN: Tx nrt-VBR Cells Served 21) QBIN: Tx Voice Cells Received
9) QBIN: Tx ABR Cells Served 22) QBIN: Tx TS Cells Received
10) QBIN: Tx NTS Cells Discarded 23) QBIN: Tx BData A Cells Received
11) QBIN: Tx Hi-Pri Cells Discarded 24) QBIN: Tx BData B Cells Received
12) QBIN: Tx Voice Cells Discarded 25) QBIN: Tx CBR Cells Received
13) QBIN: Tx TS Cells Discarded 26) QBIN: Tx ABR Cells Received

This Command: dsptrkstathist 5.1

Continue? y

------------------------------------SCREEN 2----------------------------------
sw180 TN Cisco IGX 8420 9.3.p7 Dec. 12 2000 14:08 GMT

Virtual Interface Statistic Types

27) QBIN: Tx nrt-VBR Cells Received 40) CGW: Packets Rx From Network
28) VI: Cells rcvd w/CLP=1 41) CGW: Cells Tx to Line
29) VI: OAM cells received 42) CGW: NIW Frms Relayed to Line
30) VI: Cells tx w/CLP=1 43) CGW: SIW Frms Relayed to Line
31) VI: Cells received w/CLP=0 44) CGW: Aborted Frames Tx to Line
32) VI: Cells discarded w/CLP=0 45) CGW: Dscd Pkts
33) VI: Cells discarded w/CLP=1 46) CGW: 0-Length Frms Rx from Network
34) VI: Cells transmitted w/CLP=0 47) CGW: Bd CRC16 Frms Rx from Network
35) VI: OAM cells transmitted 48) CGW: Bd Lngth Frms Rx from Network
36) VI: RM cells received 49) CGW: OAM RTD Cells Tx
37) VI: RM cells transmitted 54) CGW: Packets Tx to Network
38) VI: Cells transmitted 55) CGW: Cells Rx from Line
39) VI: Cells received 56) CGW: NIW Frms Relayed from Line

This Command: dsptrkstathist 5.1

Continue? y

------------------------------------SCREEN 3----------------------------------
sw180 TN Cisco IGX 8420 9.3.p7 Dec. 12 2000 14:08 GMT

Virtual Interface Statistic Types

57) CGW: SIW Frms Relayed from Line 78) QBIN: Tx Q11 Cells Received
58) CGW: Abrt Frms 79) QBIN: Tx Q12 Cells Served
59) CGW: Dscd Cells 80) QBIN: Tx Q12 Cells Discarded
60) CGW: 0-Lngth Frms Rx from Line 81) QBIN: Tx Q12 Cells Received
61) CGW: Bd CRC32 Frms Rx from Line 82) QBIN: Tx Q13 Cells Served
62) CGW: Bd Lngth Frms Rx from Line 83) QBIN: Tx Q13 Cells Discarded
63) CGW: OAM RTD Cells Rx 84) QBIN: Tx Q13 Cells Received
64) CGW: OAM Invalid OAM Cells Rx 85) QBIN: Tx Q14 Cells Served
73) QBIN: Tx Q10 Cells Served 86) QBIN: Tx Q14 Cells Discarded
74) QBIN: Tx Q10 Cells Discarded 87) QBIN: Tx Q14 Cells Received
75) QBIN: Tx Q10 Cells Received 88) QBIN: Tx Q15 Cells Served
76) QBIN: Tx Q11 Cells Served 89) QBIN: Tx Q15 Cells Discarded
77) QBIN: Tx Q11 Cells Discarded 90) QBIN: Tx Q15 Cells Received

This Command: dsptrkstathist 5.1

Statistic Type:

dsptrkstats (display trunk statistics)

Displays the trunk port status, ATM cell loss counts, cell payload errors, and cell header errors for the specified trunk. The chart below lists the other statistics.

To clear the statistics, include the optional clear parameter.

Logical trunk statistics refer to counts on trunks that are visible as routing entities. This includes physical and virtual trunks (all logical trunks). Logical trunk statistics are displayed on the dsptrkstats, dsptrkstathist, and screens. These commands accept only logical trunk numbers and display only logical trunk statistics. Virtual interface (VI) statistics and queue statistics are both subsets of the logical trunk statistics.

Syntax

dsptrkstats <trunk number>

Parameters

Parameter

Description

slot.port

Specifies the physical part of the logical trunk number.

clear

Directs the system to clear the statistics counters.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnftrkstats

Display Fields: Additional

Statistics

Description

Cells dropped due to BFrame parity err.

A parity error was detected in one or more of the P bits in the BFrame header or in the BIP-16 parity check for the header causing the cell to be dropped.

Cell header mismatch error count.

A count of cells received by a BNI in this slot.port with an incorrect header address for that card.

First mismatch cell header VPI/VCI.

This displays the VPI/VCI address of the first header mismatch to be received by the card in this slot.port.

BFrame cell data payload error.

A separate BIP-16 parity check is used for the payload data. This number represents the number of errors detected by this parity check. This does not necessarily cause a cell to be dropped.

BFrame cell loss due to admin access.

Internal to the BNI card is an administrative processor. This statistic is a count of the cells that were lost in an internal administrative shuffle.

Trunk Statistics

Statistics are collected on trunks at several different levels.

•Physical line statistics apply to each physical port. In the case of IMA trunks, the physical line statistics are tallied separately for each T1 port.

On both the BPX and the IGX, physical line statistics are displayed on the dspphyslnstats, dspphyslnstathist, and dspphyslnerrs screens. These commands accept only physical line numbers (that is, slot.port). These commands are new to the BPX in this release.

•Logical trunk statistics refer to counts on trunks that are visible to users as routing entities. This includes physical trunks and virtual trunks.

Logical trunk statistics are displayed on the dsptrkstats, dsptrkstahist, and dsptrkerrs screens. These commands accept only logical trunk numbers and display only logical trunk statistics.

•VI statistics are a subset of the logical trunk statistics.

•Queue statistics are a subset of the logical trunk statistics.

•Channel statistics are not polled by software on trunks. However, they are available if the debug command dspchstats is used.

Table 4-39 lists trunk statistics including statistics type, card type, and line type, as applicable.

Table 4-39 Trunk Statistics

Statistic

Stat Type

Card Type

Line Type

Total Cells Received

Logical

UXM/BXM

All

Total Cells Transmitted

Logical

UXM/BXM

All

LOS transitions

Physical

UXM/BXM

All

LOF transitions

Physical

UXM/BXM

All

Line AIS transitions

Physical

UXM/BXM

T3/E3/SONET

Line RDI (Yellow) transitions

Physical

UXM/BXM

T3/E3/SONET

Uncorrectable HCS errors

Physical

UXM

T3/E3/SONET

Correctable HCS errors

Physical

UXM

T3/E3/SONET

HCS errors

Physical

BXM

T3/E3/SONET

Line Code Violations, ES, and SES

Physical

BXM

T3/E3

Line Parity(P-bit]) errors, ES, and SES

Physical

BXM

T3

Path Parity(C-bit) errors, ES, and SES

Physical

BXM

T3

Far End Block Errors

Physical

BXM

T3

Framing Errors and SES

Physical

BXM

T3/E3

Unavailable Seconds

Physical

BXM

T3/E3

PLCP LOF and SES

Physical

BXM

T3

PLCP YEL

Physical

BXM

T3

PLCP BIP-8, ES, SES

Physical

BXM

T3

PLCP FEBE, ES, SES

Physical

BXM

T3

PLCP FOE, ES, SES

Physical

BXM

T3

PLCP UAS

Physical

BXM

T3

LOC errors

Physical

UXM/BXM

E3/SONET

LOP errors

Physical

UXM/BXM

SONET

Path AIS errors

Physical

UXM/BXM

SONET

Path RDI errors

Physical

UXM/BXM

SONET

Section BIP-8 counts, ES, and SES

Physical

UXM/BXM

SONET

Line BIP-24 counts, ES, and SES

Physical

UXM/BXM

SONET

Line FEBE counts, ES, and SES

Physical

UXM/BXM

SONET

Section SEFS

Physical

UXM/BXM

SONET

Line UAS and FarEnd UAS

Physical

UXM/BXM

SONET

Clock Loss Transitions

Physical

UXM

T1/E1

Frame Loss Transitions

Physical

UXM

T1/E1

Multiframe Loss

Physical

UXM

T1/E1

CRC errors

Physical

UXM

T1/E1

BPV

Physical

UXM

T1

Frame bit errors

Physical

UXM

E1

Unknown VPI/VCI count

Physical

UXM/BXM

All

Errored LPC cell count

Physical

UXM

All

Non-zero GFC cell count

Physical

UXM/BXM

Max Differential Delay

Physical

UXM

T1/E1

Uncorrectable HEC errors

Physical

UXM

All

Cell Hunt count

Physical

UXM

T1/E1

Bandwidth Changed count

Physical

UXM

T1/E1

Receive CLP=0 cell count

Logical

UXM/BXM

All

Receive CLP=1 cell count

Logical

UXM/BXM

All

Receive CLP=0 cell discard

Logical

UXM/BXM

All

Receive CLP=1 cell discard

Logical

UXM/BXM

All

Transmit CLP=0 cell count

Logical

UXM/BXM

All

Transmit CLP=1 cell count

Logical

UXM/BXM

All

Receive OAM cell count

Logical

UXM/BXM

All

Transmit OAM cell count

Logical

UXM/BXM

All

Receive RM cell count

Logical

UXM/BXM

All

Transmit RM cell count

Logical

UXM/BXM

All

For Each Traffic Type:

(V,TS,NTS,ABR,rt-VBR,
nrt-VBR,CBR, BdatB, BdatA,HP)

Cells served

Logical

UXM/BXM

All

Maximum Qbin depth

Logical

UXM/BXM

All

Cells discarded count

Logical

UXM/BXM

All

Example (BPX)

Display cell statistics for trunk 11.2.

dsptrkstats 11.2

sw53 TN Cisco BPX 8620 9.3.2J Oct. 31 2000 13:58 GMT

Trunk Statistics for 11.2 Cleared: Oct. 24 2000 06:39 Snapshot
Trunk Speed: 353208 cps Collection Time: 6 day(s) 20:39:41 Corrupted: NO

Cells CLP (EFCI)
Rx Trunk: 227028 0 --
Tx Trunk: 155079 0 --

Unkn Addr (UA): 0 Rx OAM Cells : 0 Rx Clp 0 Cells: 227028
Rx Clp 0 Dscd : 0 Rx Clp 1 Dscd : 0 Tx Clp 0 Cells: 155079
Tx OAM Cells : 0 Rx RM Count : 0 Tx RM Count : 0
Lst Unk VpiVci: Percent load TX 0.0% Percent load RX 0.0%

UA sums across ports in port group.

Last Command: dsptrkstats 11.2
Example (IGX)

Display cell statistics for ATM trunk 5.2 on a UXM card.

dsptrkstats 5.2

neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:50 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:23:49 Clrd: 05/31/00 01:26:37
Type Count
QBIN: NTS Cells Tx to line 0
QBIN: Tx NTS Cells Received 0
QBIN: Tx NTS Cells Discarded 0
QBIN: Hi-Pri Cells Tx to line 0
QBIN: Tx Hi-Pri Cells Received 0
QBIN: Tx Hi-Pri Cells Discarded 0
QBIN: Voice Cells Tx to line 0
QBIN: Tx Voice Cells Received 0
QBIN: Tx Voice Cells Discarded 0
QBIN: TimeStamped Cells Tx to ln 0
QBIN: Tx TS Cells Received 0
QBIN: Tx TS Cells Discarded 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)
neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:50 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:23:49 Clrd: 05/31/00 01:26:37
Type Count
QBIN: BData A Cells Tx to line 0
QBIN: Tx BData A Cells Received 0
QBIN: Tx BData A Cells Discarded 0
QBIN: BData B Cells Tx to line 0
QBIN: Tx BData B Cells Received 0
QBIN: Tx BData B Cells Discarded 0
QBIN: Tx CBR Cells Served 0
QBIN: Tx CBR Cells Received 0
QBIN: Tx CBR Cells Discarded 0
QBIN: Tx nrt-VBR Cells Served 0
QBIN: Tx nrt-VBR Cells Received 0
QBIN: Tx nrt-VBR Cells Discarded 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)
neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:50 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:00 Clrd: 05/31/00 01:26:37
Type Count
QBIN: Tx ABR Cells Served 0
QBIN: Tx ABR Cells Received 0
QBIN: Tx ABR Cells Discarded 0
QBIN: Tx Q10 Cells Served 0
QBIN: Tx Q10 Cells Received 0
QBIN: Tx Q10 Cells Discarded 0
QBIN: Tx Q11 Cells Served 0
QBIN: Tx Q11 Cells Received 0
QBIN: Tx Q11 Cells Discarded 0
QBIN: Tx Q12 Cells Served 0
QBIN: Tx Q12 Cells Received 0
QBIN: Tx Q12 Cells Discarded 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)
neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:50 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:09 Clrd: 05/31/00 01:26:37
Type Count
QBIN: Tx Q13 Cells Served 0
QBIN: Tx Q13 Cells Received 0
QBIN: Tx Q13 Cells Discarded 0
QBIN: Tx Q14 Cells Served 0
QBIN: Tx Q14 Cells Received 0
QBIN: Tx Q14 Cells Discarded 0
QBIN: Tx Q15 Cells Served 0
QBIN: Tx Q15 Cells Received 0
QBIN: Tx Q15 Cells Discarded 0
VI: Cells received 0
VI: Cells transmitted 0
VI: Cells rcvd w/CLP=1 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)

neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:50 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:12 Clrd: 05/31/00 01:26:37
Type Count
VI: Cells tx w/CLP=1 0
VI: Cells rcvd w/CLP=1 0
VI: Cells tx w/CLP=1 0
VI: Cells discarded w/CLP=1 0
VI: Cells discarded w/CLP=0 0
VI: OAM cells received 0
VI: OAM cells transmitted 0
VI: RM cells received 0
VI: RM cells transmitted 0
CGW: Packets Rx From Network 0
CGW: Cells Tx to Line 0
CGW: NIW Frms Relayed to Line 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)

neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:51 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:19 Clrd: 05/31/00 01:26:37
Type Count
CGW: SIW Frms Relayed to Line 0
CGW: Aborted Frames Tx to Line 0
CGW: Dscd Pkts 0
CGW: 0-Length Frms Rx from Network 0
CGW: Bd CRC16 Frms Rx from Network 0
CGW: Bd Lngth Frms Rx from Network 0
CGW: OAM RTD Cells Tx 0
CGW: Packets Tx to Network 0
CGW: Cells Rx from Line 0
CGW: NIW Frms Relayed from Line 0
CGW: SIW Frms Relayed from Line 0
CGW: Abrt Frms 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)
neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:51 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:29 Clrd: 05/31/00 01:26:37
Type Count
CGW: Dscd Cells 0
CGW: 0-Lngth Frms Rx from Line 0
CGW: Bd CRC32 Frms Rx from Line 0
CGW: Bd Lngth Frms Rx from Line 0
CGW: OAM RTD Cells Rx 0
CGW: OAM Invalid OAM Cells Rx 0
CF: Egress Packet Sequence Errs 0
CF: Egress Bad HEC from cellbus 0
CF: Egress Packets from cellbus 0
CF: Egress Cells Tx to Line 0
CF: Ingress Packets to cellbus 0
CF: Ingress Cells from Line 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)
neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:51 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:39 Clrd: 05/31/00 01:26:37
Type Count
IE: Egress Packets to Extract Buf 0
IE: Egress Cells injected 0
IE: Egress Packets Extract Buf full 0
IE: Ingress Cells to Extract Buf 0
IE: Ingress Packets injected 0
IE: Ingress Cells Extract Buf full 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)

Next page? (+/-/DEL key to quit)
neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:50 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:23:49 Clrd: 05/31/00 01:26:37
Type Count
QBIN: BData A Cells Tx to line 0
QBIN: Tx BData A Cells Received 0
QBIN: Tx BData A Cells Discarded 0
QBIN: BData B Cells Tx to line 0
QBIN: Tx BData B Cells Received 0
QBIN: Tx BData B Cells Discarded 0
QBIN: Tx CBR Cells Served 0
QBIN: Tx CBR Cells Received 0
QBIN: Tx CBR Cells Discarded 0
QBIN: Tx nrt-VBR Cells Served 0
QBIN: Tx nrt-VBR Cells Received 0
QBIN: Tx nrt-VBR Cells Discarded 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)
neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:50 GMT
Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:00 Clrd: 05/31/00 01:26:37
Type Count
QBIN: Tx ABR Cells Served 0
QBIN: Tx ABR Cells Received 0
QBIN: Tx ABR Cells Discarded 0
QBIN: Tx Q10 Cells Served 0
QBIN: Tx Q10 Cells Received 0
QBIN: Tx Q10 Cells Discarded 0
QBIN: Tx Q11 Cells Served 0
QBIN: Tx Q11 Cells Received 0
QBIN: Tx Q11 Cells Discarded 0
QBIN: Tx Q12 Cells Served 0
QBIN: Tx Q12 Cells Received 0
QBIN: Tx Q12 Cells Discarded 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)
neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:50 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:09 Clrd: 05/31/00 01:26:37
Type Count
QBIN: Tx Q13 Cells Served 0
QBIN: Tx Q13 Cells Received 0
QBIN: Tx Q13 Cells Discarded 0
QBIN: Tx Q14 Cells Served 0
QBIN: Tx Q14 Cells Received 0
QBIN: Tx Q14 Cells Discarded 0
QBIN: Tx Q15 Cells Served 0
QBIN: Tx Q15 Cells Received 0
QBIN: Tx Q15 Cells Discarded 0
VI: Cells received 0
VI: Cells transmitted 0
VI: Cells rcvd w/CLP=1 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)

neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:50 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:12 Clrd: 05/31/00 01:26:37
Type Count
VI: Cells tx w/CLP=1 0
VI: Cells rcvd w/CLP=1 0
VI: Cells tx w/CLP=1 0
VI: Cells discarded w/CLP=1 0
VI: Cells discarded w/CLP=0 0
VI: OAM cells received 0
VI: OAM cells transmitted 0
VI: RM cells received 0
VI: RM cells transmitted 0
CGW: Packets Rx From Network 0
CGW: Cells Tx to Line 0
CGW: NIW Frms Relayed to Line 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)

neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:51 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:19 Clrd: 05/31/00 01:26:37
Type Count
CGW: SIW Frms Relayed to Line 0
CGW: Aborted Frames Tx to Line 0
CGW: Dscd Pkts 0
CGW: 0-Length Frms Rx from Network 0
CGW: Bd CRC16 Frms Rx from Network 0
CGW: Bd Lngth Frms Rx from Network 0
CGW: OAM RTD Cells Tx 0
CGW: Packets Tx to Network 0
CGW: Cells Rx from Line 0
CGW: NIW Frms Relayed from Line 0
CGW: SIW Frms Relayed from Line 0
CGW: Abrt Frms 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)
neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:51 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:29 Clrd: 05/31/00 01:26:37
Type Count
CGW: Dscd Cells 0
CGW: 0-Lngth Frms Rx from Line 0
CGW: Bd CRC32 Frms Rx from Line 0
CGW: Bd Lngth Frms Rx from Line 0
CGW: OAM RTD Cells Rx 0
CGW: OAM Invalid OAM Cells Rx 0
CF: Egress Packet Sequence Errs 0
CF: Egress Bad HEC from cellbus 0
CF: Egress Packets from cellbus 0
CF: Egress Cells Tx to Line 0
CF: Ingress Packets to cellbus 0
CF: Ingress Cells from Line 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)
neelix TRM Cisco IGX 8420 9.3.10 May 31 2000 01:51 GMT

Trunk 5.2 Clear - OK
Collection Time: 0 day(s) 00:24:39 Clrd: 05/31/00 01:26:37
Type Count
IE: Egress Packets to Extract Buf 0
IE: Egress Cells injected 0
IE: Egress Packets Extract Buf full 0
IE: Ingress Cells to Extract Buf 0
IE: Ingress Packets injected 0
IE: Ingress Cells Extract Buf full 0

This Command: dsptrkstats 5.2

Next page? (+/-/DEL key to quit)

dsptrkutl (display trunk utilization)

Displays dynamic utilization information for a specified trunk. The trunk must be upped and added to use this command. The following tables list the trunk utilization and terminated connection parameters included in the display. The parameter values are updated according to the specified or default interval and the screen remains displayed until the DEL key is depressed. Disabled trunks have their trunk number displayed in dim, reverse video on the screen.

If you notice that data traffic has slowed or stopped due to the very high trunk utilization due to network traffic, it may be because a node is receiving excessive volumes of network traffic (CC). In this case, the node may start dropping messages, which will result in communication breaks with other nodes as well as possible communication failures on some of its trunks.

You can detect the excessive traffic by displaying various statistics such as network statistics (nwstats), SAR statistics (srstats), and check utilization of the node's trunks by using the dsptrkutl command. In the event of excessive traffic, these command displays will show values that are increasing at a high rate. See the cnfnodeparm parameters Enable Degraded Mode, Auto Switch on Degrade, and Max Degraded Aborts for descriptions of how to set parameters so that if a node has exhausted its internal resources due to excessive messaging (among other possible causes), which leads the node to abort, the node will either switch to the standby CC if available, or it will enter degraded mode (if the cnfnodeparm Enable Degraded Mode parameter is enabled). See Table 4-40 for trunk utilization parameters and statistics, and Table 4-41 for the terminated connection statistics.

Table 4-40 Trunk Utilization Parameters and Statistics

Trunk Utilization Parameters and Statistics

Description

Elapsed time (seconds)

Elapsed time in seconds since the command was started.

Total packets transmitted

Number of packets transmitted during the elapsed time.

Overall packet rate

Number of packets transmitted per second (pps) during the elapsed time.

Overall utilization

Bandwidth used, expressed as a percentage of the available bandwidth during the elapsed time. This is 100 x total packets transmitted/elapsed time x bandwidth (pps).

Peak interval utilization

Bandwidth used, expressed as a percentage of the available bandwidth during the peak interval. This is 100 x total packets transmitted/peak interval x bandwidth (pps).

Last Interval (seconds)

Elapsed time, in seconds, for the last screen update interval.

Interval packets generated

Number of packets transmitted during the last interval.

Interval packet rate (pkts/sec)

Number of packets transmitted per second during the last interval.

Interval utilization

The used bandwidth expressed as a percentage of the available bandwidth during the last interval. The derivation of interval utilization is 100 x interval packets transmitted/last interval x bandwidth (pps).

Total Connections

Total number of connections routed over the trunk.

Terminated/Via

Terminated: Number of connections routed over the trunk that terminate at this node.

Via: Number of connections routed over the trunk that do not terminate at this node.

Table 4-41 Terminated Connection Statistics

Terminated Connection Statistics

Description

Voice terminated

Number of voice connections terminated at this node that are routed over his trunk.

Data terminated

Number of data connections terminated at this node that are routed over this trunk.

Frame Relay terminated

Number of Frame Relay connections terminated at this node that are routed over this trunk.

Num voice off-hook

Number of voice connections off-hook that are terminated at this node and routed over this trunk.

Connection type

Voice connection types: c, a, v, p or t.

Connection num

Number of terminated voice connections of each type:

c, a, v, p and t.

Modem on

Number of terminated connections with modem detected.

Modem V.25

Number of terminated connections with V.25 modem detected.

VAD enabled

Number of terminated connections with VAD enabled.

Syntax

dsptrkutl <trunk number> [interval]

Parameters

Parameter

Description

trunk number

Specifies the number of the trunk in the format slot.trunk. If the card has only one trunk, you can enter just the slot.

interval

Specifies the number of seconds between screen updates.
Range: 1-60
Default: 5

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

Yes

Related Commands

dspload, dspchhist, dsptrkhist

Example (BPX)

Display OC-3 trunk utilization for port 2 of the BXM card in slot 11.

dsptrkutl 11.2

sw53 VT Cisco BPX 8620 9.3.2o Dec. 6 2000 10:09 GMT

TRK 11.2 Utilization Display Snapshot

Elapsed time (seconds) 44.8 Terminated Connection Statistics
Total cells transmitted 362 Voice terminated 0
Overall cell rate (cells/sec) 8 Data terminated 0
Overall utilization 1% Frame Relay terminated 0
Peak interval utilization 1% Num voice OffHook 0
Last interval (seconds) 7.6 ATM terminated 5
Interval cells generated 58 Connection Modem Modem VAD
Interval cell rate (cells/sec) 7 Type Num On V.25 Enabled
Interval utilization 1% c 0 0 0 0
a 0 0 0 -
Terminated Connections 5 v 0 0 0 0
Via Connections and Groups 0 p/t 0 0 0 -

Last Command: dsptrkutl 11.2

dsptsmap (display the channel-to-timeslot mapping usage)

Display the channel-to-timeslot mapping usage information on a UVM card on an IGX node. The dsptsmap command is for use with the SVC caching feature, which speeds up call setup for most VNS controlled calls. The SVC caching feature avoids some of the call setup/tear-down operations associated with addcon and delcon as a call originates or terminates. The SVC caching feature reduces the connect time for many switch calls over a busy network.

To use the dsptsmap command, the line must have SVC caching enabled on it. You can find out if a channel is disabled by using the dsptsmap command.

•The cnfln command is used to configure the SVC caching parameter setting.

•The dspcons command is used to view disabled connections provided the SVC has not been deleted.

•The dsplncnf command will show the value (On/Off) of the SVC caching mode feature.

Refer to the VNS Installation and Configuration Manual for more information on SVC caching.

The dspclns command is an identical alias for the dsplns command.

Syntax

dsptsmap <line_number>[update_interval]

Parameters

Parameter

Description

line_number

The slot.line for UVM or line for CVM/CDP.

interval_number

Interval in seconds between screen updates. The default value is controlled by "Screen Update Time" in the cnfuiparm command.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnfuiparm, cnfln, cnfupcln, dncln, dsptrks, dspln, dsplncnf

Example

Enabled channels are shown on the screen underlined and in reverse video. Disabled (cached) channels are shown with the channel number underlined and in reverse video, while the timeslot is shown in normal video. Channels that have no connection are shown in normal video for both channel number and timeslot.

For example:

•Channel 1 does not have a connection.

•Channel 2 is an enabled connection carrying traffic.

•Channel 3 is a disabled connection.

Specify the line_number parameter in slot.line format for UVM, and line format for CDP/CVM.

Use the optional update_interval parameter to control how often the screen gets updated. If you do not enter any value through the CLI, the value of the Screen Update Time parameter set using in the cnfuiparm command is used.

dsptsmap 7.2

sw176 TRM StrataCom IGX 16 9.3 Apr. 13 2000 11:00 PST

Line 7.2 Channel to Timeslot Map

Chan TS Chan TS Chan TS Chan TS
-------- -------- -------- --------
1 1 9 14 17 17
2 2 10 12 18 5
3 22 11 18 19 19
4 5 12 10 20 20
5 11 13 13 21 21
6 6 14 9 22 3
7 7 15 15 23 23
8 8 16 9 24 24

This Command: dsptsmap 7.2

Hit DEL key to quit:

dsptsmap (display SNMP parameters)

Displays the following SNMP statistics for the node:

•SVC Requests Received, the number of SVC requests received.

•SVC Current Queue Length, the number of outstanding SVC requests in the queue.

•SVC Maximum Queue Length, the high-water mark of the number of outstanding SVC requests in the queue.

•SVC Requests Timed Out, the number of SVC requests that have timed out.

•Current Trap Managers, the number of managers (up to 10) that are currently registered, their IP addresses and UDP ports.

•Traps Transmitted, the number of traps transmitted.

•TRAP Current Queue Length, the number of outstanding traps in the queue.

•TRAP Maximum Queue Length, the high watermark of the number of outstanding traps in the queue.

•TRAP Queue Events Discarded, the number of traps discarded due to queue overflow.

•Overflow Traps Transmitted, the number of overflow traps transmitted due to queue overflow.

Syntax

dspsnmpstats

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

cnfsnmp, dspsnmp

Example (IGX)

Display SNMP statistics for the current node.

dspsnmpstats

sw180 TN Cisco IGX 8420 9.3.p0 Dec. 6 2000 09:05 GMT

SVC Requests Received: 0 Traps Transmitted: 0

SVC Current Queue Length: 0 TRAP Current Queue Length: 0
SVC Maximum Queue Length: 0 TRAP Maximum Queue Length: 0
SVC Requests Timed Out: 0 TRAP Queue Events Discarded: 0
Overflow Traps Transmitted: 0

Current Trap Managers: 0/10 Snmp_Trap_Db Ptr: 315687BE

Last Command: dspsnmpstats

dspusers (display users)

Displays users. The privilege levels in the display are restricted to those of the current user and any privileges below the current user.

Syntax

dspusers

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

adduser, deluser, dspusers

dspusertask (display user task)

Displays information about the current user task. The displayed information varies with the user task. For example, information about a vt session slightly differs from a Telnet session. The command takes a user task number as an argument. If the user task number is unknown, enter the command without a number to see a list of possible user tasks and the current user task.

The types of user tasks are:

•User, which can be the control terminal user, auxiliary port user, or StrataView

•A Telnet session

•A virtual terminal session (vt)

•An SNMP agent

•A job

Syntax

dspusertask [user task number]

Parameters

Parameter

Description

user task number

Specifies the number of the user task whose information is displayed.

Related Commands

adduser, cnfpwd, deluser, dspusers, dsppwd

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Example (BPX)

Display user task information—without specifying a task in this case. This example shows a case in which the user has started a vt session on a node. See also step 2 of this example.

dspusertask

sw78 VT SuperUser BPX 15 9.3 Apr. 13 2000 15:52 PST

# TASK PURPOSE USER ID # TASK PURPOSE USER ID
-- ---- ------------ ------- -- ---- ------------ -------
1 USR1 control port none 13 VT-5 VT none
2 USR2 auxilry port none 14 VT-6 VT none
3 USR3 lan port(SV) none 15 SNMP agent n/a
4 TN-1 lan (telnet) none 16 JOBS runs jobs n/a
5 TN-2 lan (telnet) none
6 TN-3 lan (telnet) none
7 TN-4 lan (telnet) none
8 TN-5 lan (telnet) none
9 VT-1 VT: sw81 SuperUser < You
10 VT-2 VT none
11 VT-3 VT none
12 VT-4 VT none

This Command: dspusertask

Please Enter User Number:9
Example (BPX)

This example shows the screen after the you enter a 9 at the prompt in the previous screen, a case in which you already started a vt session on a node. Note that the display shows the status as a vt slave, and the node on which the vt session originated is sw81.

9

sw78 VT SuperUser BPX 15 9.3 Apr. 13 2000 15:53 PST

Task: VT-1
Logged in as: SuperUser
VT master: no
VT slave: yes Master node is: sw81
VT pending: no

Public lock: no
Private lock: none

No command is currently running.
Previous command: dspusertask 9

Last Command: dspusertask 9

Next Command:

dspusertasks (display user tasks)

Displays general information about all current user tasks. The types of user tasks are as follows:

•User, which can be the control terminal user, auxiliary port user, or Cisco WAN Manager

•A Telnet session

•A virtual terminal session (vt)

•An SNMP agent

•A job

Syntax

dspusertasks

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

adduser, cnfpwd, deluser, dspusers, dsppwd, dspusertask

Example (IGX)

Display user task information.

dspusertasks

sw151 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:02 GMT

# TASK PURPOSE USER ID # TASK PURPOSE USER ID
-- ---- ------------ ------- -- ---- ------------ -------
1 USR1 control port SuperUser 13 VT-5 VT none
2 USR2 auxilry port none 14 VT-6 VT none
3 USR3 lan port(SV) none 15 SNMP agent n/a
4 TN-1 lan (telnet) none 16 JOBS runs jobs n/a
5 TN-2 lan (telnet) SuperUser < You
6 TN-3 lan (telnet) none
7 TN-4 lan (telnet) none
8 TN-5 lan (telnet) none
9 VT-1 VT none
10 VT-2 VT none
11 VT-3 VT none
12 VT-4 VT none

Last Command: dspusertasks

Next Command:

dsputl (display utilization)

The dsputl command displays the utilization factor for all voice connections or data channels on a circuit line.

This command displays the actual percentage utilization for all voice connections on a single circuit line specified by the back slot (bslot) number. The percentage is calculated by dividing the number of packets transmitted by the total number of packets allocated to the specified channel. Only transmit packet rates are used. If the percentage of actual utilization exceeds the configured utilization the channel appears in reverse video.

Syntax

dsputl <bslot> [clear]

Parameters

Parameter

Description

<bslot>

Specifies the shelf back slot number of the circuit line.

[clear]

Directs the controller card to clear the utilization counters after being displayed.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

IGX

Yes

Related Commands

dspdutl

Example

This is a typical display. In this example, the connections from 11.1 to 11.11 use VAD and the connections from 11.12 to 11.17 do not. The connections using VAD do not use any network bandwidth (0 utilization) until the connection is used. The other connections utilize the full bandwidth (100% utilization) even though they may be idle.

dsputl 11

gamma TRM SuperUser Rev: 9.3 Apr. 13 2000 16:36 PDT

Percentage utilization Last Cleared: Date/Time Not Set Snapshot

CLN 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

11 0 0 0 0 0 0 0 0 0 0 0 0 99 99 99

CLN 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

11 99

Last Command: dsputl 11
Next Command:

dspvsiif (display a Service Class Template assigned to an interface)

Display a Service Class Template assigned to an interface (VI). You can also display a summary of the resources allocated to the VSI partition on a given interface. Multiple users may use the dspvsiif at one time.

After using cnfvsiif command to assign a selected Service Class Template to an interface, you can use the dspvsiif command to display the type of Service Class Template assigned to an interface (VI).

Syntax

dspvsiif <slot.port.vtrk>

Parameters

Parameter

Description

slot.port.[vtrk]

Slot, port (and virtual trunk number if applicable) of the interface.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

Yes

Yes

No

No

Related Commands

cnfrsrc, dsprsrc, cnfqbin, dspqbin

Example (IGX)

Display the service class template assigned to interface 3.1.

dspvsiif 3.1

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 14:17 PST

Port: 3.1

Service Class Template ID: 2

State MinLCN MaxLCN StartVPI EndVPI MinBW MaxBW
Partition 1: D
Partition 2: D
Partition 3: E 100 200 100 200 10000 10000

Last Command: dspvsiif 3.1

Next Command:
Example (BPX)

Display the Service Class Template assigned to BXM port interface 11.1.

dspvsiif 11.1

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 20:56 GMT

Port: 4.1

Service Class Template ID: 2

VSI Partitions :
channels bw vpi
Part E/D min max min max start end ilmi
1 D 0 0 0 0 0 0 D
2 D 0 0 0 0 0 0 D
3 D 0 0 0 0 0 0 D

Last Command: dspvsiif 4.1 4

Next Command: dspvsiif 4.1

dspvsipartcnf (display VSI partition characteristics)

Display VSI ILMI functionality:

•whether VSI ILMI is enabled for a given partition

•the LCN used for the sessions (only for trunk interfaces)

If no partition is specified, dspvsipartcnf displays the above information about all the VSI partitions and also the Sys_Id downloaded to the BXM card for ILMI functionality.

Syntax

dspvsipartcnf <slot.port.[vtrk]> [partition_id]

Parameters

Parameter

Description

slot.port.[vtrk]

Slot, port (and virtual trunk number if applicable) of the interface.

partition_id

Partition ID corresponding to the VSI partition. This parameter is optional and, if not specified, this command will display information about all VSI partitions.

Related Commands

cnfrsrc, cnfvsipart, cnfport, cnftrk

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

No

BPX

Yes

dspvsipartinfo (display VSI statistics per partition)

Display VSI statistics for a particular active partition on an interface. You can use the dspvsipartinfo command on only one partition at a time, to get VSI statistics on an interface (can be a port or virtual trunk).

You can optionally specify an interval in seconds, which will display VSI statistics for the specified active partition every x seconds. The command shows you some of the same parameters that display on the cnfrsrc screen, such as Min LCNs and Max LCNs, Used LCNs and Available LCNs, and Min BW, Max BW, and Used BW.

The command also displays a line that provides slave redundancy status. It tells you whether the standby card is in sync with the active card. You must have cards in Y-redundancy configuration for this line to display.

Multiple users may use the dspvsipartinfo command at the same time.

The switch software polls the card for the information at the specified interval and displays the information from the card.

Syntax

dspvsipartinfo <interface>.<partition>[<interval>]

Parameters

Parameter

Description

interface

The slot.port.[vtrk] of the interface being monitored

partition

Partition ID for which information is to be displayed.

interval

Refresh interval for displaying data.
Range: 1-60 seconds
Default: 10 seconds

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

Yes

Yes

Yes

No

Related Commands

cnfrsrc, dsprsrc

Display Fields

Parameter

Description

Min BW

Configured minimum bandwidth for this partition (for reference only).

Max BW

Configured maximum bandwidth for this partition (for reference only).

Used BW

Bandwidth currently used by connections on this partition.

Available BW

Bandwidth currently available to connections on this partition. This is determined based on the minimum and maximum bandwidth configured for the partition and the bandwidth currently available in the common pool.

Min Lcns

Configured minimum LCNs for this partition (for reference only).

Max Lcns

Configured maximum LCNs for this partition (for reference only).

Used Lcns

Number of LCNs currently used by connections in this partition.

Available Lcns

Number of LCNs available to this partition. This is determined based on the minimum and maximum LCNs configured for the partition and the number of connections on the partition.

Example (IGX)

Display the VSI statistics for partition 2 on trunk 5.1.

dspvsipartinfo 5.1 2

sw188 TRM Cisco IGX 8420 9.3.1c Aug. 17 2000 12:11 PST

VSI Resources Status for trunk 5.1 Partition 2

Minimum Lcns : 500 Minimum BW (cps) : 1000
Maximum Lcns : 2000 Maximum BW (cps) : 2000
Used Lcns : 0 Used BW (cps) : 0
Available Lcns : 1100 Available BW (cps) : 2000
Start VPI : 55 End VPI : 60

This Command: dspvsipartinfo 5.1 2

Hit DEL key to quit:
Example (BPX)

Display VSI statistics on interface 3.1, partition 1, at an interval of every 10 seconds.

dspvsipartinfo 3.1 1 10

sw237 TN StrataCom BPX 8620 9.3.10    June 9 2000 17:32 PST

VSI Resources Status for trunk 3.1 Partition 1

Min Lcns : 0 Min BW (cps)    : 0
Max Lcns : 20 Max BW (cps)   : 0
Used Lcns : Used BW (cps)    :
Available Lcns : Available BW(cps):

Next Command: dspvsipartinfo 3.1 1
Example (BPX)

Display VSI statistics for interface 11.1, partition 2, at an interval of every 10 seconds.

dspvsipartinfo 11.1 2 10

sw53   TN   StrataCom     BPX 8600 9.3.10   Jan. 10 2000   14:31 GMT

VSI Resource Status for port 11.1 Partition 2

Min Lcns         1000         Min BW (cps)       20000
Max Lcns         4000         Max BW (cps)      40000
Used Lcns        500          Used BW (cps)      20000
Available Lcns: : 1000         Available BW(cps)   10000

This Command: dspvsipartinfo 11.1 2 10

Hit DEL key to quit:
Example (BPX)

Display VSI statistics for interface 4.1, partition 1.

dspvsipartinfo 4.1 1

sw237 TN StrataCom BPX 8620 9.3.10    May 10 2000 14:58 PST

VSI Resources Status for trunk 4.1 Partition 1 Snapshot

Min Lcns :20 Min BW (cps)    :2000
Max Lcns :30 Max BW (cps)    :3000
Used Lcns : Used BW (cps)    :
Available Lcns : Available BW(cps):

Last Command:dspvsipartinfo 4.1 1
Example (BPX)

Display VSI statistics for interface 6.3, partitions 1, 2 and 3.

dspvsipartinfo 6.3

sw167 TN Cisco BPX 8620 9.3.2R Dec. 14 2000 11:04 PST

Port: 6.3 Partn: 1 -- VSI partition DISABLED
Port: 6.3 Partn: 2 -- VSI partition DISABLED
Port: 6.3 Partn: 3 -- VSI partition DISABLED

Sys_Id generation failed!! Using default value = 0.0.0.0.0.1

Last Command: dspvsipartcnf 6.3

dspyred (display Y-cable redundancy)

Displays information for Y-cable pairings. You can specify a single slot or you can display all pairings by specifying no slot.

Slot numbers appearing in high intensity indicate active card status. Front card, back card, and channel configuration conflicts appear in reverse video. A conflict occurs when the port interfaces are different for corresponding ports in a redundant slot pair.

The output display shows:

•First column (Slot): the slot of the displayed card.

•Second column (Slot Type): its status, Pri (primary) or Sec (secondary).

•Third column (Other Slot): the slot number of the associated Y-redundant card.

•Fourth column (Front Card): the type of card in the front slot.

•Fifth column (Back Card): the type of card in the back slot.

Remaining columns (Channel Configuration) describe the channel configurations when appropriate.

Syntax

dspyred [slot]

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-4

No

Yes

BPX, IGX

Yes

Yes

No

No

Related Commands

addyred, delyred, prtyred, switchyred

Example (BPX)

Display Y-redundancy for all cards.

dspyred

sw11 TN Cisco BPX 8620 9.3.c0 May 9 2001 1329 GMT

Slot Other Front Back
Slot Type Slot Card Card
2 Pri 3 BXM LM-BXM
3 Sec 2 BXM LM-BXM

Last Command dspyred

editjob (edit a job)

Edits a job. You can change any of these items in a job:

•The job description

•Execution time

•Execution interval

•Individual commands in the job

•Failure reactions for each command

After you enter the editjob command, the system displays the template for the job. You can edit, delete, or add a command. Each item in the template is successively displayed on the command line so that you can confirm or change the item.

You cannot change the privilege level of a job.

Use editjob to:

•To change an item in the job template, enter or type over the existing information on the command line and press the Return key.

•Use any of the control keys to change information on the command line. To keep the same value of an item, press the Return key at the prompt.

•To add a new command between existing commands in a job, hold down the Control key while you press the ^ key. A new line appears above the command that is highlighted. Enter the new command after the "Enter Cmd:" prompt and press Return.

•To add a new command to the end of a job, press the Return key after the last command in the job template.

•To delete a command from a job, either backspace over the command when it appears on the command line and press the Return key, or hold down the Control key while you press the
"x" key.

•To end the editing session, press the Return key when prompted for a new command or press the Del key.

When commands are added to or deleted from a job, the system renumbers the commands. To test an edited job, run it with the runjob command.

Syntax

editjob <job_number>

Parameters

Parameter

Description

<job_number>

Specifies the number of the job to edit.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

Yes

BPX, IGX

Yes

Related Commands

addjob, deljob, dspjob, dspjobs, runjob

Example

Edit job 1. The template for job 1 appears on the screen. The system displays the existing job description, which you can change or keep. To keep it, press Return. The system then displays the execution time. To change it to August 17, 1998 at 11:00:, for example, enter:

1998 8 17 11 00

If no other items require changing, press the Return key.

editjob 1

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 14:19 PST

Job 1 prtlog
Last Execution Results: None Status: Editing
Next Execution Time: 08/17/97 11:00:00 Interval: 1 days

1: prtlog
- Failure Reaction: Repeat 2 Times and Abort Exec. Results: None
2:

Last Command: editjob 1

Next Command:

getfwrev (get firmware revision)

The getfwrev command gets and loads a firmware image:

•From Cisco WAN Manager, or a remote node.

•To the specified card on the specified node, or on all reachable nodes.

This firmware image can then be downloaded to specific interface cards within the node with the burnfwrev command. The firmware image must be already loaded into the Cisco WAN Manager or Cisco WAN Manager terminal before using this command.

When the command is first entered, the status is temporarily "Unavailable" while the node attempts to locate the source of the firmware image. Once the download begins, a list of all of the files that make up the image is displayed and as the downloading progresses, the address of the file is updated.

•getfwrev a.b.cd *—Loads firmware revision a.b.cd at all reachable nodes

•getfwrev BNI-E3 a.b.cd nodename—Loads firmware revision a.b.cd on the BNI-E3 card at one node only (nodename specifies the node).

•getfwrev 0.0—Clears a firmware revision image from memory. Should be issued after every firmware download to clear the memory.

•getfwrev BNI-E3 0.0 nodename—Clears a firmware revision image from the BNI-E3 card at one node only (nodename specifies the node).

Caution This command is not to be confused with loadrev. The loadrev command loads system software, not firmware.

Syntax

getfwrev <card type> <image name> <nodename>

Parameters

Parameter

Description

<card type>

Specifies the card on which to load the revision.

<image name>

Specifies the name assigned to the firmware revision. Image names are generally in all capital letters and are case-sensitive when being entered.

<nodename>

Specifies the node on which to load the revision.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

Yes

Yes

BPX, IGX

Yes

Related Commands

burnfwrev, dspfwrev, dspdnld

help or ? (help command)

Displays a help menu. This command accesses the help routine in the system software, providing:

•A short description of the command

•An indication of whether the command can be used in a job

•The command syntax

A more extensive, menu-driven, on-line help function exists within the WAN Manager NMS. Consult the Cisco WAN Manager Operations Guide for a complete description of the online help.

The ways to request help on commands are:

•Entering help or ? without an argument lists the command categories. Selecting one of these categories (using arrow keys and Return) displays all the commands in that category. You can select commands in this list by using arrow keys then the Return key.

•Entering a command name displays help for that particular command.

•Entering a partial command name lists all commands that contain that character string. For example, fr indicates all commands (such as cnffrport) that contain "fr." You select a command in the list by using arrow keys to scroll to the command then press Return.

Syntax

? or help

[command name | character string]

Parameters

Parameter

Description

command

Specifies a command.

string

Specifies a character string as a search argument.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Example (IGX)

Display the help menu. (Without an argument, the help command shows the command categories.)

help

sw180 TN Cisco IGX 8420 9.3.g0 Oct. 20 2000 06:14 GMT

All commands fall into one (or more) of the following categories:

Control Terminal
Configuration
Lines
Network
Connections
Cards
Alarms and Failures
Diagnostics
Debug

This Command: ?

Use cursor keys to select category and then hit <RETURN> key:
Example (BPX)

Display the help menu. (Without an argument, the help command shows the command categories.)

help

sw53 TN Cisco BPX 8620 9.3.2J Oct. 25 2000 06:19 GMT

All commands fall into one (or more) of the following categories:

Control Terminal
Configuration
Lines
Network
Connections
Cards
Alarms and Failures
Diagnostics
Debug

This Command: help

Use cursor keys to select category and then hit <RETURN> key:

Example (BPX)

Display the syntax and other information for Display BXM Slot Errors (dspbxmsloterrs).

help dspbxmsloterrs

sw53 TN Cisco BPX 8620 9.3.2J Oct. 25 2000 06:20 GMT

dspbxmsloterrs - Display BXM Slot Errors
Cannot be included in Jobs.
Usage: dspbxmsloterrs [slot]

Last Command: help dspbxmsloterrs
Example (IGX)

help fr

Display all commands that contain the string "fr." (These are the Frame Relay commands.) A list of all commands containing the letters "fr" appears on screen. Scroll to a command then press Return to display the related help screen.

sw180 TN Cisco IGX 8420 9.3.g0 Oct. 20 2000 06:47 GMT

Commands that contain the string "fr"

addfrcons - Add Multiple Frame Relay Connections
addfrport - Add Frame Relay Port
clrfrcportstats - Clear Port Concentrator Link Statistics
cnffrcls - Configure Frame Relay Connection Classes
cnffrcon - Configure (modify) Frame Relay Connection Parameters
cnffrport - Configure Frame Relay Port Parameters
cnffrcport - Configure Port Concentrator Link Parameters
cnfrcvsig - Configure Received Signalling
cnfrobparm - Configure Robust Parameter Values
cnfrsrc - Configure VSI Resource Partition
cnfrtcost - Configure Maximum Route Cost for a Connection
cnfrtr - Configure Router Configuration Parameters
cnfrtrparm - Configure Router Service Parameters

This Command: help fr

Use cursor keys to select command, then hit <RETURN> key for detailed help:

killuser (log out a user)

Logs out a user. The command displays a numbered list of users. The number is the argument that killuser takes. The display indicates your user number so that you do not log out yourself.

Syntax

killuser <user number>

Parameters

Parameter

Description

<user number>

Specifies the number of the user to log out.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX

Yes

Example (IGX)

killuser

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 00:11 PST

# TASK PURPOSE USER ID # TASK PURPOSE USER ID
-- ---- ------------ ------- -- ---- ------------ -------
1 USR1 control port none 13 VT_5 VT none
2 USR2 auxilry port none 14 VT_6 VT none
3 USR3 lan port(SV) none 15 SNMP agent n/a
4 TN_1 lan (telnet) SuperUser < You 16 JOBS runs jobs n/a
5 TN_2 lan (telnet) none
6 TN_3 lan (telnet) none
7 TN_4 lan (telnet) none
8 TN_5 lan (telnet) none
9 VT_1 VT none
10 VT_2 VT none
11 VT_3 VT none
12 VT_4 VT none

This Command: killuser

Please Enter User Number:

loadcnf (load configuration)

Loads a configuration image from the Cisco WAN Manager (CWM) or a TFTP network server to a node, where the file is stored in the RAM buffer.

Note Starting with Release 9.3.30, the TFTP Configuration Save and Restore feature enables use of the standard TFTP protocol for network configuration backup to a server other than CWM. For detailed information on this feature, see the savecnf command description.

This command causes a saved network configuration file to be downloaded to one node or all nodes. (See savecnf.) To illustrate this:

loadcnf r93nov17 nodeA * 172.29.9.25 T /usr/users/svplus

–Loads the configuration of one node connected to the TFTP server.

loadcnf r93nov17 * * 172.29.9.25 T /usr/users/svplus

–Loads the configuration of all nodes through one node connected to the TFTP server.

The configuration image downloaded is temporarily stored in a buffer area in a node's controller card memory. The process runs in the background and may take several minutes if the configuration file is large. Although loaded, the configuration is not yet restored. You restore the configuration to the controller card's BRAM memory by using the runcnf command.

After loading and restoring a network configuration, you should clear the control card buffer area used for this purpose so it will be available for other downloading processes, such as that of firmware.

To clear the buffer area, execute loadcnf with the clear parameter specified instead of backup_id. Specify the buffer of an individual node with nodename or all nodes with *.

To execute this command on an IGX/AF interface shelf, Telnet to the shelf or use a control terminal attached to the shelf.

Syntax

loadcnf <backup_id | clear> <nodename | *> <CWM_nodename | *> [<destination_IP>] [<T>] [<pathname>]

Parameters

Parameter

Description

backup ID

Specifies the name of the configuration file to be restored. To identify file names on CWM, look in the /usr/users/svplus directory. The directory containing the configuration files is named <backup_id>_Cfgdir.

clear

An optional parameter that clears the buffer space in RAM of any old configuration files before the new configuration is copied back to the node. You must explicitly clear the buffer before it can be loaded with a new file.

nodename

Specifies the name of the node that is to have its configuration restored. The wildcard option, specified by an asterisk (*), is used in place of nodename to indicate all nodes are to have their configurations restored.

CWM nodename

Specifies the name of the node that has the CWM attached. The node name identifies the gateway node of the CWM that is the source for the configuration restore. As an option, an asterisk (*) can be entered to indicate that the CWM IP address is to be used to identify the source CWM.

destination IP

An optional parameter that specifies the IP address of the CWM or TFTP network server that is the source for the configuration restore. You can only enter this parameter when an asterisk (*) is entered for CWM Nodename.

T

An optional parameter that specifies TFTP is used for data transfer instead of the CWM proprietary protocol.

pathname

A new optional parameter that can be configured when TFTP is being used for data transfer. It indicates the directory path name where the backup files are stored.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

Yes

Yes

BPX, IGX, IGX/AF

Yes

Related Commands

clrcnf, dspcnf, runcnf, savecnf

loadrev (load revision)

Loads a secondary system software revision image from Cisco WAN Manager into the specified nodes.

The secondary revision system software is the code that is loaded onto a controller card but is not currently running. Use the runrev command (after you have loaded a revision with loadrev) to make the secondary revision the primary revision. The primary revision then becomes the secondary.

Examples of this command:

•loadrev a.b.cd *—Loads revision a.b.cd at all reachable nodes.

•loadrev a.b.cd nodename—Loads revision a.b.cd at nodename only

•loadrev 0.0.—Clears a software revision image from controller memory. You should issue this command after every software download to clear the controller memory.

After entering the command, the system responds with this prompt:

Enter Rev Number:
A prompt is issued if you run the loadrev command during a time when statistics collection is enabled. If you select "yes," statistics collection is disabled before the loadrev command is executed.

Use the dsprevs command to view the software revisions that are currently loaded in the controller memory. Use the dspdnld command to display a running picture of the download procedure status once it has begun. The runrev command also displays the lowest revision running in the network.

Caution Do not confuse loadrev with getfwrev. The getfwrev command loads firmware, not system software.

Syntax

loadrev <revision> <node_name | group_name | *>

Parameters

Parameter

Description

<revision>

Specifies the revision level of the system software file to be loaded.

<node_name>

Specifies the target node where the secondary revision is to be loaded.

<group_name>

Specifies a subset of nodes in the network.

<*>

Specifies all nodes in the network.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX, IGX/AF

Yes

Related Commands

runrev, dsprevs, cnfdlparm, upggrp

prtapsln (print APS line status)

Prints the dspapsln screen, that is, the currently configured APS lines and their status.

Syntax

printapsln

Related Commands

addapsln, delapsln, cnfapsln, cnfcdaps, dspapsln, dsplog, dspalms

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

No

No

BPX

No

prtcderrs (print card errors)

The prtcderrs command prints out detailed card failure information.

Prints a history of card failures associated with a specified slot on the network printer. If no argument is specified, a summary is printed, indicating the slots that have failures recorded against them. Refer to the dspcderrs command definition for an example of a typical card error record that might be printed.

Syntax

prtcderrs [<slot>]

Parameters

Parameter

Description

<slot >

Specifies the shelf slot where the selected card is installed.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

Yes

No

BPX, IGX

Yes

Related Commands

clrcderrs, dspcderrs

prtchcnf (print channel configuration)

Prints the configuration details for voice channels or data channels. This command uses the same syntax, and prints the same information as is displayed by using the dspchcnf command. See the dspchcnf command definition for syntax and output information.

Syntax

prtchcnf [start_channel]

Parameters

Parameter

Description

[start_channel]

Specifies the starting channel for the print output.
On a CDP or CVM, the format is slot.channel.
On a UVM, the format is slot.line.channel.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

IGX

Yes

Related Commands

dspchcnf

Example

Print the configuration values of circuit line 14.1.

prtchcnf 14.1

This command produces hardcopy.

prtchdlcnf (print channel dial type configuration)

Prints the dial type configurations for channels on a circuit line.

Syntax

prtchdlcnf <start_channel>

Parameters

Parameter

Description

start channel

Specifies the starting channel for the print output.
On a CDP or CVM, the format is slot.channel.
On a UVM, the format is slot.line.channel.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

IGX

Yes

Related Commands

cnfchdl, dspchcnf

Example

Print the dial type configuration for all channels beginning with 14.1.

prtchcnf 14.1

This command produces hardcopy

prtclnerrs (print circuit line errors)

Prints the accumulated error count since the last time errors were reset. This command uses the same syntax and prints the same information as is displayed by using the dspclnerrs command. The clrclnerrs command clears the error counters for circuit lines by resetting all error counts to 0.

Syntax

prtclnerrs

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

Yes

IGX

Yes

Related Commands

clrtrkerrs, prttrkerrs

prtcons (print connections)

Prints a summary of connections terminated at the IGX node. This command uses the same syntax and prints the same information as is displayed using the dspcons command. See the dspcons command for syntax and output information.

Syntax

prtcons [start_channel] [nodename] [type]

Parameters

Parameter

Description

[start_channel]

Optionally specifies the starting channel.
On a CDP or CVM, the format is slot.channel.
On a UVM, the format is slot.line.channel.

[nodename]

Optionally specifies that only connections to this remote node from the local note be displayed. If no "nodename" is designated, connections from the local node to all other nodes are displayed.

[type]

Optionally specifies that only connections of the specified type appear. If you do not include a connection-type argument, all connections appear. Connection types require a hyphen (-). Valid connection type entries are:

-v = Display only voice connections.
-d = Display only data connections.
-atfr = Display Interworking connections.
-g = Display grouped connections.
-abit = Display A-bit Status.
-fabit = Display A-bit Errors.
-fail = Display failed connections.
-down = Display downed connections.
-f = Display Frame Relay connections.
-nni = Displays Frame Relay network to network connections for failed
connections only.

The state that may be displayed for Frame Relay and NNI connection types includes:

OK: Connection OK, A-bit = 1.

FAILED: Connection failed, A-bit = 0.

MISSING: DLCI was deleted in other network NNI. A previous status report indicated a valid DLCI present but an updated report did not.

UNUSED: The UNI port does not support reporting of NNI A-bit status.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

IGX

Yes

Related Commands

dspcons

prtict (print interface control template)

Prints the configuration details for voice channels or data channels. This command uses the same syntax, and prints the same information as is displayed by using the dspchcnf command. See the dspchcnf command for syntax and output information.

Syntax

prtict <port> <template>

Parameters

Parameter

Description

<port>

Specifies the channel containing the data card. The start channel has the format slot.port.

<template>

Specifies which control template to display for the channel. Three templates are available for data channels. One template (option "a") is available for Frame Relay ports. You can also specify the near or far end of the connection.

a = Active control template (normal operation). The only choice for a Frame Relay port.

c = Conditioned control template (when connection fails).

l = Looped control template (with local or remote loopback).

n = Near.

f = Far.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

No

IGX

Yes

Related Commands

cnfict, cpyict

Example

Print the active interface control template for 25.1.

prtict 25.1

The command produces hardcopy.

prtjob (print job)

Prints this information about a specific job:

•Job number

•Job description

•Next execution date and time

•Status

•Interval. The time interval between successive executions of the job

•Execution. The results of the last execution of the job

To print a job, you must have at least the same (or higher) privilege level as the person who wrote the job). See the addjob command definition for more information. The prtjob command uses the same syntax and prints the same information the dspjob command.

Syntax

prtjob <job_number>

Parameters

Parameter

Description

<job_number>

Specifies the number of the job to be printed.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

BPX, IGX

Yes

Related Commands

dspjob

prtjobs (print jobs)

Prints this information about all existing jobs:

•Job number

•Job description

•Next execution date and time

•Status

•Execution interval between jobs

•Access Group: The privilege level required to run or display the job

For a printout on a single job, use the prtjob command. This command uses the same syntax, and prints the same information as is displayed by using the dspjobs command. See the dspjobs command definition for syntax and output information.

Syntax

prtjobs

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

Yes

BPX, IGX

Yes

Related Commands

dspjobs

prtlnerrs (print physical line errors)

Prints the accumulated error count since the last time errors were reset. This command uses the same syntax and prints the same information as the dsplnerrs command. The clrlnerrs command clears the error counters for circuit lines by resetting all error counts to 0.

Syntax

prtlnerrs

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

BPX, IGX

Yes

Related Commands

dsplnerrs

prtlns (print line configuration)

Prints the current line configuration and line alarm status for a node. This command uses the same syntax, and prints the same information as the dsplns command. See the dspclns command definition for syntax and output information.

Syntax

prtlns

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

BPX, IGX

Yes

Related Commands

dsplns

prtlog (print event log)

Prints the event log for a node. Events affecting the node are displayed in chronological order with the most recent events at the top of the log. The printout includes a description of the event, the date and time of the event, and the alarm class of the event.

This command uses the same syntax and prints the same information as the dsplog command. See the dsplog command definition for output information.

Syntax

prtlog

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

BPX, IGX

Yes

Related Commands

dsplog

prtnw (print network topology)

Prints the network topology table. Alarms print in a column, and added trunks (by addtrk) appear to the right to the node name. Each trunk entry shows the local back card slot number and the node name and back card slot number on the other end of the line.

These conventions apply:

•An ~ indicates the trunk is a satellite line.

•Flashing entry indicates a failed line.

•Blinking node indicates a node is executing downloader software.

Parameters set Zero Coded Suppression (ZCS) display characteristics. ZCS writes a 1 over the least significant bit of any byte that contains 0s. The purpose is to ensure a minimum occurrence of 1s so that the receiving node can extract timing information. The prtnw command uses the same syntax and prints the same information as the dspnw command.

Syntax

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

Parameters

Parameter

Description

+b

Display only the lines that support bursty data.

-b

Display only the lines that do no support bursty data.

+z

Display only the lines that use ZCS encoding.

-z

Display only the lines that do not use ZCS encoding.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

BPX, IGX

Yes

Related Commands

dspnw

prtrts (print connection routes)

Prints the connection routes for channels on the IGX node. This command uses the same syntax and prints the same information as the dsprts command. See the dsprts definition for output information.

Syntax

prtrts [start_channel] [dest_nodename]

Parameters

Parameter

Description

[start_channel]

Specifies the channel with which to print. Channels are printed in numeric order. If no starting channel is specified, the display begins with the first connected channel. Start channel is specified in one of these formats:

slot.channel voice connection.

slot.port data connection.

slot.port.DLCI Frame Relay connection.

remote node.groupname Frame Relay connection group.

[dest_nodename]

Specifies the printing of connection routes from only the local node to the current node (destination node). Without a specified node name, the printout shows connections from the local node to all other nodes.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

IGX

Yes

Related Commands

dsprts

prtscrn (print terminal screen)

Prints the information on the screen at the time the command is entered. All information on the terminal screen is printed. If printing is successful, no status message appears. If the printer is unavailable, an appropriate status message appears.

Syntax

prtscrn

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

BPX, IGX

Yes

Related Commands

clrscrn, redscrn

prttrkerrs (print trunk errors)

Prints a summary of the trunk error counts for both physical and virtual trunks on the local node. This is the same information that displays when you use the dsptrkerrs command. See the dsptrkerrs command definition for output information.

Syntax

prttrkerrs

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

BPX, IGX

Yes

Related Commands

dsptrkerrs

prttrkict (print trunk interface control template)

Prints the interface control template of a subrate trunk. For a list of configurable outputs and configuration steps, see the cnftrkict description. The printed information includes:

•Specified line

•Associated leads and their status

•Whether output follows a local input

•Name of the local or remote input lead that the output lead follows

Syntax

prttrkict <line>

Parameters

Parameter

Description

line

Specifies the trunk interface control template.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

No

IGX

Yes

Related Commands

dsptrkict

prttrks (print trunks)

Prints the trunk configuration for the node. This command uses the same syntax and prints the same information as the dsptrks command.

Configuration information for trunks includes the trunk number and the type of line (T3, E3, and so on). For trunks that have been added to the network with the addtrk command, the configuration information also includes the node name and trunk number at the other end of the line.

Note these printout characteristics:

•Those trunks that show a "-" in the "Other End" column, have been upped with the uptrk command but not yet added with the addtrk command.

•The Other End column shows the node name and slot number of the other end of the trunk.

•Names of disabled trunk appear as light text in the printout.

Syntax

prttrks

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

BPX, IGX

Yes

Related Commands

dsptrks

prtyred (print Y-cable redundancy)

Prints the Y-cable redundancy configuration for an SDP, LDP, CDP, FRP, FTC, or NTC.

The command prtcdred is an alias for prtyred.

On an IGX node, the cards are the HDM, LDM, CVM, FRM, NTM, UXM, UFM, and UVM.

On a BPX node, the applicable cards are the BCC, ASI, and BNI.

This command uses the same syntax and prints the same information as the dspyred command. See the dspyred command definition for details on the format of the command output.

Syntax

prtyred <start slot>

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

Yes

Related Commands

dspyred, addyred, delyred

Example (IGX)

Print Y-redundancy for all cards (no starting slot entered)

prtyred

Prints the card redundancy configuration for a BXM card with an OC-3 or OC-3 interface. This command uses the same syntax and prints the same information as the dspyred command. See the dspcdred command definition for details on the format of the command output.

redscrn (redraw the terminal screen)

Redraws the screen. This command can be useful for communication that involves a modem. If data has become corrupted and caused erroneous characters on the terminal screen, redscrn clears them.

Syntax

redscrn

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

BPX, IGX

No

Related Commands

clrscrn, prtscrn

Example (IGX)

redscrn

sw180 TN Cisco IGX 8420 9.3.2J Oct. 25 2000 06:39 GMT

FrontCard BackCard FrontCard BackCard
Type Rev Type Rev Status Type Rev Type Rev Status
1 NPM BVS Standby 9 FRM KSB FRI-T1 AL Standby
2 NPM BWS Active 10 Empty universal backplane
3 Empty universal backplane 11 Empty universal backplane
4 UXM CD23 T3 AA Active 12 URM AA11 2FE2V EW Standby
5 UXM CA23 OC3 AD Active 13 LDM CK03 232-8 AJ Standby-T
6 FRM DHZ FRI-V35 BD Standby 14 URM AA13 2FE2V P03 Standby
7 Empty universal backplane 15 URM AA12 2FE2V EW Active
8 NTM FHF T1 AL Active 16 Empty universal backplane

Last Command: redscrn

resetcd (reset card)

Resets the hardware and software for a card. Use the resetcd command to switch between a primary and redundant service card that has been configured for Y-cable redundancy. Normally, a failure would cause a switch between Y-cabled cards, but you might want to cause the switch to remove the active card to upgrade its hardware, for example.)

Do not use resetcd on an active NPM or BCC because resetting an active controller card interrupts traffic while it boots. (Resetting a controller card does not destroy configuration information.) If a redundant controller card is present and you want to switch between controllers, use the switchcc command to switch the active controller card to standby and the standby controller card to active. You can subsequently reset the standby controller without bringing it to the active state (and therefore not disrupt service).

You might use the resetcd r command is if you ran out of memory and had no standby card. If there were a memory leak problem somewhere in the system, you might execute a resetcd r command before you run the switchcc command (if you do not have a standby card, or you are not sure of the health of the standby card if there is one), then you might execute it locally on the active processor card (BCC or NPM). You do not need to enter the minus symbol before the "r" in the resetcd r command (just resetcd r) is acceptable.

The resetcd command takes an argument to indicate a hardware or failure reset. A hardware reset (resetcd h) is equivalent to physically removing and reinserting the front card and causes the card's logic to be reset. When you reset the hardware of an active card other than a controller card (an NPM or BCC), a standby card takes over if one is available. A failure reset (resetcd f) clears the card failures associated with the specified slot. If a slot contains a front card and back card, resetcd resets both cards. A resetcd r performs a card reset on processor cards (such as an NPM or BCC). Note when the node is in degraded mode, the "r" option is disabled.

You can use the resetcd command to initiate a hitless rebuild manually. The Hitless Rebuild feature provides the ability to effectively rebuild without affecting user traffic. It substantially decreases the time it takes for the BPX to settle into its normal operating state after a rebuild.

The option "r" lets you manually initiate a hitless rebuild on processor cards only. The "r" option becomes disabled when the node is in degraded mode.

Syntax

resetcd <slot_num> <reset_type>

Parameters

Parameter

Description

<slot_num>

Specifies the card number to be reset.

h | f

Specifies whether the hardware or failure history for the card is to be reset.

h-specifies hardware; performs a hardware test

f-specifies failure history; performs a failure reset

b

Specifies to use hardware to reset the card, not the CBUS message. This option is also known as the "arbiter" option. You can use the b option only on BPX nodes.

r

Specifies that a hitless rebuild is performed only on processor cards.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-3

Yes

Yes

BPX, IGX

Yes

Related Commands

resetcd

resetpc (reset port concentrator)

Resets a PCS attached to a specified FRM-2 or FRP-2 physical port on the IGX. Concentrated links, logical ports, and all connections are temporarily suspended while the PCS hardware performs a warm boot.

Once the PCS re-establishes communication with the FRM-2 or FRP-2, logical ports are reconfigured and connections repaired. A series of messages describing each of the concentrated links failing and being re-established is generated.

Syntax

resetpc <slot.port>

Parameters

Parameter

Description

slot.port

Specifies the card and port number to reset.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-3

Yes

Yes

BPX, IGX

Yes

Related Commands

tstpcs, dsppcs

rrtcon (reroute connection)

Manually reroute one or more connections.

This command forces a group, channel, or range of channels to be rerouted. If a free-routing connection is rerouted by the system for whatever reason, it will not automatically return to its original route when the trouble clears. This might leave the connection on a path that is not the most direct or cost effective.

You can use rrtcon to force a reroute that will likely put the connection back to its original route if that route is available. Over time, many routes may need to be rerouted back to their original paths. In this case, use the "*" parameter with rrtcon on the node where you originally executed it to reroute all connections.

To use this command you must first vt to the node that owns the connection (local node). If not at the local node, the system displays "This node is not owner of the connection(s)."

There is no provision for specifying a route. The node determines the connection route according to the same rules that are used when adding a new connection. If no network bandwidth is available for rerouting the connection, the node marks the connection as failed.

Caution Using this command on a connection that is in service should be done with some discretion because the reroute interrupts service for as long as it takes to reroute the connection.

Syntax

rrtcon <group | channel | *>

Parameters

Parameter

Description

<group | channel | *>:

Specifies a group, a channel, or a range of channels to be rerouted.
A * specifies all locally owned groups and connections.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

Yes

Yes

BPX, IGX

Yes

Related Commands

drtop

rstrtr (reset router)

Resets the Universal Router Module (URM) on a specified router slot. The URM is functionally equivalent to a UXM card with one ATM port and an IOS router. The rstrtr command does not reset or restart the embedded UXM on the URM.

In normal operation, verify the source of the IOS configuration file before using the rstrtr command. The source of the IOS configuration file can be either the router BRAM, which stores the running IOS configuration file, or the NPM, which stores a blank default configuration file. Upon reset, the IOS processor reloads the configuration file from the source specified in the IOS-config-file parameter. When the router BRAM is specified as the IOS configuration file source, the router resumes normal operation upon reset.

Use the dsprtr command to display the specified source of the IOS configuration file. Use the cnfrtr command to change the source of the IOS configuration file.

Syntax

rstrtr <router-slot>

Parameters

Parameter

Description

router-slot

Specifies the virtual shelf slot to support the URM embedded router.
Range: 1-32

Switch software manages the embedded router in the URM as if the router resides on a slot in a virtual shelf (of routers). Each slot in the IGX shelf has a corresponding router slot in the virtual shelf. A router slot is considered empty when the equivalent IGX slot is empty or contains an IGX card without an embedded router. If the IGX slot contains a URM card, the router slot is reported as hosting an IOS router.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

IGX

Yes

Related Commands

cnfrtrparm, cnfrtr, dsprtr, dsprtrslot, dsprtrslots, dspalms

Example

Reset the URM embedded router on router slot 6.

rstrtr 6

sw108 TN Cisco IGX 8420 9.3.2E Sep. 5 2000 09:05 GMT

This Command:rstrtr 6

Reset router with above configuration ? (y|n) y

rststats (reset statistics collection time)

The rststats command resets the statistics collection time for the tststats command. Executing rststats clears all statistics. When you enter it, a prompt warns you that the command clears all statistics and asks if you want to proceed.

The tststats command displays a test statistics summary. Before there will be any meaningful statistics, the tstcon command must be performed on one or more network connections.

Syntax

rststats

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

Yes

No

BPX, IGX

Yes

Related Commands

tststats

Example (IGX)

rststats

alpha32 LAN SuperUser IGX 8430 9.3 Apr. 13 2000 13:35 PST

This Command: rststats

Warning: This command clears all statistics
Continue?

runcnf (run configuration)

Restores a network configuration image at one or all nodes. This command restores the specified configuration to the controller card's BRAM memory and overwrites the current configuration. Once restored, the specified node (or all nodes) rebuilds with the restored configuration image.

To execute this command on an IGX/AF interface shelf, Telnet to the shelf or use a control terminal attached to the shelf.

This command is usually run after a previous configuration has been lost. If doubts exist about the state of the configuration at other nodes in the network, load the configuration into all nodes by specifying "*" for the node name. The new configuration must have previously been loaded into the controller buffer area by using the loadcnf command.

Caution All network nodes must be run with the same configuration.

The system may display two warnings in response to the runcnf command:

1. When single node specified:

–Warning—node_name not reachable. Continue? Y/N.

–Warning—node_name does not have the specified configuration. Continue? Y/N.

2. When all nodes specified:

–Warning—all nodes not reachable. Continue? Y/N.

–Warning—all nodes do not have the specified configuration. Continue? Y/N.

If a single node is not reachable, responding with a "Y" does not affect the operation of the network. If nodes do not all have the specified configuration or all are unreachable, it is not recommended that you continue until after the problem is resolved.

Syntax

runcnf <backup_id> <node_name>

Parameters

Parameter

Description

<backup_id>

Specifies the name of the configuration image loaded from Cisco WAN Manager. Configuration names are case-sensitive.

<node_name>

Specifies the node name to receive the configuration. An asterisk (*) specifies all nodes.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX

Yes

Related Commands

savecnf, loadcnf, clrcnf

runjob (run a job)

Runs a job. The runjob command runs a job regardless of its execution time. The runjob command does not change a job's assigned execution time.

When you enter runjob, the system displays the job template and prompts, "Run this job (y/n)?" Enter "y" to start the job. Enter "n" to exit runjob.

After you enter y, four seconds pass before a job begins running. Press any key briefly to suspend a job. Four seconds of no keyboard activity must pass before the jobs resume. While a job is running, the system highlights the current command and updates command results.

You can include the runjob command in a job. Therefore, running one job can cause another job to run. The only limitation is that a job cannot cause itself to run. For example, Job 1 cannot include the command "runjob 1." Also, Job 1 cannot include the command "runjob 2" if Job 2 contains the command "runjob 1."

Syntax

runjob <job_number>

Parameters

Parameter

Description

<job_number>

Specifies the number of the job to run.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

Yes

BPX, IGX

Yes

Related Commands

addjob, dspjobs, editjob, stopjob

Example (IGX)

Run job 1.

runjob 1

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 14:23 PST

Job 1 test
Last Execution Results: None Status: Idle
Next Execution Time: 03/17/96 11:00:00 Interval: 1 days

1: prtlog
- Failure Reaction: Repeat 2 Times and Abort Exec. Results: None

This Command: runjob 1
Run this job (y/n)?

runrev (run revision)

Runs a specific revision of the system software at a node. This command sets the primary revision for the specified nodes. The primary software revision is the one that is actively controlling node operation. You can also load a non-active secondary revision that differs from the primary revision running in the controller. To set the primary software revision, enter one of the following:

•runrev a.b.cd *—To run revision a.b.cd at all reachable nodes.

•runrev a.b.cd nodename—To run revision a.b.cd at a single node (nodename) only.

After entering the command, the system responds with "Enter Rev Number." Use the dsprevs command to determine which revision(s)—primary and secondary—are available on the node. The runrev command also displays the lowest revision running in the network. The runrev command will be ignored if the required revision is not present on the node.

You might need to load the new revision onto the Cisco WAN Manager terminal and then use loadrev command to download the new software image into the standby controller before you issue the runrev command. If you enter a revision number that does not exist at the node, the system displays:

"Warning—the node does not have the specified revision. Continue? Y/N"

If statistics collection is enabled at the time the runrev command is issued, a prompt is displayed, allowing the user to disable collection. If the user selects "yes," statistics collection is disabled.

Caution All network nodes typically should be run with the same software revision to ensure normal network operation.

Syntax

runrev <revision> <node_name | group_name | *>

Parameters

Parameter

Description

<revision>

Identifies the revision you want to run.

<node_name>

Specifies the node name to rebuild with a new configuration.

<group_name>

Specifies a subset of nodes in the network.

*

Specifies all nodes in the network.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

Yes

BPX, IGX

Yes

Related Commands

dsprevs, loadrev, cnfdlparm, upggrp

savecnf (save configuration)

Takes a snapshot of the existing node configuration, saves it in RAM buffer files, then uploads the files to a Cisco WAN Manager (CWM) or TFTP network server, where they are stored on disk.

Note Starting with Release 9.3.30, the TFTP Configuration Save and Restore feature enables use of the standard TFTP protocol for network configuration backup to a server other than CWM. For detailed information on this feature, see the "TFTP Configuration Save and Restore" section.

The savecnf command has two possible applications. It saves:

•the configuration of one node or all the configurations for all the nodes in a routing network, or

•it saves the configuration of one IGX/AF interface shelf.

Once saved, you can restore the configuration to the controller card's BRAM by using the loadcnf and runcnf commands. You should execute savecnf in these situations:

•After making any configuration changes in a network

•Before upgrading to a new system software release

Execution on a Routing Node

In a routing network, savecnf saves a configuration image for one node or all routing nodes (nodename = *) on the Cisco WAN Manager workstation specified by CWM_nodename or on a TFTP network server specified by destination_IP.

From the CLI, the following example saves the configuration of one node connected to a TFTP server.:

savecnf r93nov17 nodeA * 172.29.9.25 T /usr/users/svplus

The next example from the CLI saves the configuration of all the nodes through one node connected to a TFTP server.

savecnf r93nov17 * * 172.29.9.25 T /usr/users/svplus

Execution on an IGX/AF Interface Shelf

To execute savecnf on an IGX/AF, either Telnet to the shelf or use a control terminal attached to it: savecnf saves a configuration image of only the current shelf. The image is stored on the workstation with the IP address in the parameter CWM_nodename. (In a routing network, CWM_nodename is not necessary.) Note that nodename and CWM_nodename must both be the name of the shelf. The IP address of the destination Cisco WAN Manager workstation uniquely identifies where to store the configuration image.

Syntax

savecnf <backup_id | clear> <nodename | *> <CWM_nodename | *> [<destination IP>] [<T>] [<pathname>]

Parameters

Parameter

Description

backup ID

Specifies the name of the configuration file to be saved. The name must be 1-8 alphanumeric characters, and the first character must be alphabetic. Configuration names are case-sensitive.

clear

An optional parameter that clears the buffer space in RAM of any old configuration files before the new configuration snapshot is taken. You must explicitly clear the buffer before it can be loaded with a new file.

nodename

Specifies the name of the node that is to have its configuration saved. The wildcard option, specified by an asterisk (*), is used in place of nodename to indicate all nodes are to have their configuration saved.

CWM nodename

Specifies the name of the node that has the CWM attached. The node name identifies the gateway node of the destination CWM for the configuration save. As an option, an asterisk (*) can be entered to indicate that the CWM IP address is to be used to identify the destination CWM.

destination IP

An optional parameter that specifies the IP address of the CWM or TFTP network server that is the source for the configuration restore. You can only enter this parameter when an asterisk (*) is entered for CWM Nodename.

T

An optional parameter that specifies TFTP is used for data transfer instead of the CWM proprietary protocol.

pathname

A new optional parameter that can be configured when TFTP is being used for data transfer. It indicates the directory path name where the backup files are stored.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

Yes

Yes

BPX, IGX, IGX/AF

Yes

Related Commands

loadcnf, runcnf, clrcnf, dspcnf

TFTP Configuration Save and Restore

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, standard TFTP protocol can be used to backup the BPX/IGX node configuration 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 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.

The TFTP Configuration Save and Restore facility also includes a TFTP Start file interface for initiating a configuration save and restore request. The TFTP Start file follows the same format used for a firmware download request. The name of the Start file indicates whether a Save or Restore is being requested. A TFTP Put of the start file is sent to the node for a Configuration Save request and a Configuration Restore request. 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 TFTP Configuration Save and Restore process using CLI commands includes the following steps:

•Use the cnfswfunc command to enable the configuration save and restore facility. (The cnfswfunc command is a Cisco service command.)

•Use the cnfsysparm command to specify the parameter "Num of Nodes Doing Simultaneous TFTP Cnfg Save/Restore." This value for the parameter must be the same on all nodes.

•Use the cnfnodeparm command to specify the IP Relay Gateway node. This parameter must be configured separately on each node. However, this step is only necessary if the node has no LAN connection to the TFTP server, and therefore, needs to use IP Relay to transfer TFTP data to the server. If the LAN connection to the server exists, it is preferable to use it. Leaving the "IP Relay gateway node" parameter set at the default value of 0 will allow the node to use the LAN connection.

•Use the cnffwswinit command to specify the IP address of the network server authorized to initiate the configuration save and restore operation using the TFTP Start file or SNMP interface.

•Use the dspcnf command to display the configuration save/restore status for all network nodes.

•Clear the buffer in RAM. The RAM buffer stores files and images from three separate facilities. It is not required to clear the buffer if it currently contains the old configuration files from the previous Save/Restore operation. In fact, a new Save/Restore request can interrupt one that is in process. The RAM buffer only needs to be cleared if it currently contains files from other features; for example firmware or software downloads or a URM Remote Router Configuration download. In such instances, use the savecnf clear command to clear old configuration files stored by the configuration save and restore facility. Use the getfwrev command to clear firmware images stored by the Firmware Download facility. Use the clrrtrcnf command to clear IOS configuration files stored by the URM Remote Router Configuration facility.

•Create a directory and files on the target network server. This step is performed automatically by CWM when proprietary protocol is used. The Configuration Save process stores the files on CWM disk in a newly created directory with the following pathname:

/usr/users/svplus/<backup_id>_Cfgdir

When TFTP is used, you must create the directory and files manually or create a script that automatically generates the files. Make sure the directory and files have read and writer permissions enabled for everyone to have access; otherwise, the node will not be able to write (save) or read (restore) from the server. Also, the directory and file formats must follow the same conventions as the proprietary protocol. The following is a list of conventions.

–The backup_id is the name given by the user to the saved configuration. For each node, the configuration consists of three files. If a backup of the entire network is made through a single request, then there will be a single backup_id, and files for all nodes are stored in the same directory. The files have names in the following format, based upon the domain number (currently always 1) and the name of the node:

•D1.<nodename>.000. A small file containing the basic boot configuration.

•D1.<nodename>.001. A large file containing online configuration.

•D1.<nodename>.cfg. A small Image Descriptor file, containing information about the other two files (CRCs, addresses, etc.).

•There is currently a set of user interface commands that is used to create the files indicated above, and to drive the Configuration Save and Restore process. These are described in the next few sections.

•Use the savecnf command to start the upload process to CWM or other network server.

•Use the loadcnf command to start the download process from CWM or other network server.

•Use the runcnf command to restore the node configuration.

stopjob (stop job)

Stops all running and all waiting jobs. When you enter the stopjob command, the system prompts, "Stop all running and waiting jobs (y/n)?" Enter a "y" to stop running jobs and prevent all waiting jobs from beginning. Enter an "n" to exit stopjob. Because the stopjob command can leave a task partially executed, use stopjob with caution. You must have at least the same or higher privilege level of the creator of the jobs you want to stop.

Syntax

stopjob

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

No

No

BPX, IGX

No

Related Commands

runjob

Example (IGX)

Stop all jobs currently running or queued to run on the node. Confirm by entering y.

stopjob

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 14:24 PST

Job 1 test
Last Execution Results: None Status: Idle
Next Execution Time: 03/17/96 11:00:00 Interval: 1 days

1: prtlog
- Failure Reaction: Repeat 2 Times and Abort Exec. Results: None

This Command: stopjob

Stop all running and waiting jobs (y/n)?

upggrp (upgrade groups)

The loadrev and runrev commands take "upgrade group" names as arguments, allowing you to upgrade any subset of nodes at the same time.

Previous to Release 9.1, you could specify either a single node name, or an `*' (asterisk) to specify all nodes in the network, as an argument to runrev or loadrev. An upgrade group is a list of nodes, which could be all nodes in the network. Instead of running runrev for each node to be upgraded, upgrading an entire group of nodes at one time leads to a synchronized upgrade process (which the "staggered update mechanism" relies on). The staggered mechanism prevents a situation where many nodes send messages to a single node at the same time.

After an upgrade, each node requests information from every node about its topology and connection database to compensate for any errors or race conditions that may occur during the upgrade. Every node sends its messages to only one node during a given interval. If all nodes start sending these updates at the same time (and the interval is configured the same on all nodes), then all nodes will send messages to different nodes as everyone has a different node number. Whenever the interval ends, they start sending to a node with the next node number. If they would not start at the same time, there would be overlaps as one node could be in its first interval, whereas others are already in the second or third interval.

If all nodes start at the same time, it is guaranteed that one node will exchange updates with only one other node during a given interval, reducing the amount of stress that would occur when multiple nodes send updates to one node at the same time.

This command creates a group of nodes to be upgraded by the loadrev and runrev commands. To create an upgrade group type

upggrp -c <group name>

You can create up to 20 upgrade groups. Naming the upgrade groups follows the same convention as for node names; that is, choose group names that are different from the node names in the network. If loadrev or runrev encounter a name conflict, the commands chose the node name interpretation.

Note Upgrade groups are only known on the node where they are created. They are neither sent to the Standby, nor saved in BRAM. It is assumed they are needed for a short time only. Once the upgrade is done, you can delete the groups.

To delete an upgrade group that is no longer needed, freeing up resources, enter:

upggrp -d <group name>

To show (list) the currently defined upgrade groups, enter:

upggrp -s

To list all the member nodes of a group, enter:

upggrp -s <group name>

To remove a node or several nodes from an upgrade group, enter:

upggrp -r <group name> <node 1> <node 2>...

To add several nodes to an upgrade group, enter:

upggrp -a <group name> <node 1> <node 2>...

After the command is executed, the members of the group are listed. You can add nodes to an upgrade group in multiple iterations.

Syntax

upggrp [-c | -d | -s ] <group_name>

upggrp [-a | -r ] <group_name> <node_list>

Parameters

Parameter

Description

-c

Create a user group.

-d

Delete a user group.

-s

Show the defined upgrades groups.

-a

Add nodes to the group.

-r

Remove list of nodes from group.

<group name>

Name of group of nodes to be upgraded.

<node_list>

The length of the node list can be as long as the command line allows. If an entry is invalid, that is, it is not a valid node name or not a name of a node in the network, an error message prints, and the remainder of the node list is not processed. The nodes before the invalid node are added to the group.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

dsprevs, cnfdlparm, loadrev, runrev

switchapsln (control APS switching interface)

Control the APS switching interface. You use the switchapsln command, along with other APS commands such as addapsln, delapsln, dspapsln, switchapsln, and cnfapsln to configure and control a SONET APS (Automatic Protection Switching) line for a BXM OC-3 or OC-12 card. SONET APS is a standard that describes the switching of SONET lines from the active line to a standby line to provide hardware line redundancy.

Several options are available that determine the type of switch operation:

•Clear—clear user switch request. This option clears the last user switch request and sets the switching state machine to fully automatic hardware control.

•Forced Switch (Working to Protection or Protection to Working)—the forced switch forces hardware to switch to the standby line even if it is in alarm.

•Manual Switch (Working to Protection or Protection to Working)—the manual switch is lower priority than a forced switch and will cause a switch only if certain conditions are met.

Note It is recommended that you not use the Manual Switch option with Annex B configured when the BPX is connected to a third-party vendor's switch.

•Lockout—prevents switching from the working line to the protection line from taking place. A lockout request is cleared by a subsequent Clear request.

•Service—the service switch for the two-slot solution only. This request causes all lines to be forcibly switched to one back card so that the other card of the pair can be removed for service.

Be sure that the associated front card is active for the back card that is to remain in the rack. You might have to perform a switchyred (alias switchcdred) so that the back card to which the service switch switches has its associated front card active.

Note When Annex B is configured, switchapsln options are not blocked at the command line interface.

Syntax

switchapsln <slot.port> <switchoption> [S]

Parameters

Parameter

Description

<slot.port>

The working APS line to be switched

<switchoption>

Switch options:

1. Clear clears the last user request, returns state back to working line, resets to all defaults, and sets BXM to fully automatic line control.

2. Lockout of Protection—Prevents specified APS pair from being switched to protection line. If protection line is already active, switch is made back to the working line. (For Annex B, the working line is termed the "primary line," and the Protection line is termed the "secondary line.")

3. Forced Working to Protection Line Switch—If working line is active, switch is made to protection line unless the protection line is locked out or in the SF condition or Forced Switch is already in effect. Forces hardware to switch to the protection line even if it is in alarm.

4. Forced Protection to Working Line Switch—If protection is active, switch is made to working unless a request of equal or higher priority is in effect. P-->W switch applies only in the 1+1 architecture. If protection line is active, switch is made to working line unless a request of equal or higher priority is in effect.

5. Manual Switch (Working to Protection Line)—Switch from working to protection line unless a request of equal or higher priority is in effect. Will not switch if other line is in alarm.

6. Manual Switch (Protection to Working Line). Not applicable to 1+1, Annex B.

[S]

If you enter S as an additional parameter, a service switch is performed for all ports on the card such that all lines are forcibly switched to one back card so that the other back card of the pair can be removed for service. Be sure that the associated front card is active for the back card that is to remain in the rack. You may have to perform a switchcdred command so that the back card that the service switch changes to has its associated front card active.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1

Yes

Yes

BPX

Yes

Related Commands

cnfcdaps, addapsln, delapsln, dspapsln, switchapsln, cnfapsln

switchcc (switch control card)

Switches the standby BCC or NPM card to active and the active card to standby. If a standby BCC card is not available, the command is not executed. If a standby BCC is available but is not ready to go active, a prompt asks you to confirm or abort the switch of the control card. Executing switchcc (previously called switchpcc) has this effect:

•Control is transferred to the standby controller card.

•Any job currently running is aborted.

•The user is logged off.

Immediately after the switch, the controller card that was previously active reverts to a download mode. This is indicated by the flashing front panel FAIL lamp. The system software image that is always stored in ROM is downloaded to RAM in the event that the system software was corrupted.

After this is completed, the configuration database is downloaded from the newly active controller card to complete the download. This process takes a number of minutes so this controller card is not available for standby operation until this download process is completed.

The switchcc command results in a very brief interruption of all traffic. Consequently, you should use switchcc only when the network can tolerate a brief interruption.

If the Hitless Rebuild feature is enabled (by using cnfnodeparm command), the databases needed for a hitless rebuild will be preserved during the subsequent standby rebuild. This allows for a hitless rebuild if the new standby processor encounters a fatal hardware error shortly after the switchover.

Syntax

switchcc [f]

Parameters

Parameter

Description

[f]

Forces a cc switchover even if there are pending updates. If you don't specify the [f] option, the system warns you about pending updates before the switch and gives you a choice to not switch over.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-3

Yes

No

BPX, IGX

Yes

Related Commands

dspcd, dspcds

switchyred (switch Y-redundancy cards)

Switches active and redundant cards used for SONET APS (Automatic Protection Switching). The switchyred command is the same as the switchcdred command, and you can use it on any Y-cable redundancy card pair. You typically would use this command only when you need to perform diagnostics or maintenance, and you need to remove and service the active card.

Note When implementing two-card APS 1+1, it must be implemented with card redundancy. This implementation may also be referred to as "Y-redundancy," because the new card redundancy commands used to configure APS 1+1 are based on Y-redundancy commands used in releases previous to Release 9.2.

When there is a front card failure, front card downed, or the front card fails a self-test, the card switchover should happen automatically (that is, you should not need to execute the switchyred command for the card switchover to happen). An automatic switchover typically occurs when the switch software determines that the card is in a worse condition than the redundant pair (that is, a card is in a failed state due to a condition such as self-test, background test, fatal errors). If a standby card is not available, the switchyred command will not be executed.

Typically, when APS and card redundancy are implemented together, the term Y-redundancy actually refers to card redundancy because there is no Y-cable connecting two back cards to one line. With SONET APS card redundancy, there is a primary and a secondary front card/back card pair. The redundant front card must be in Hot Standby state before a switchover can occur. When a front card failure is detected, the switchover should happen automatically (when card redundancy has been implemented). However, for the APS application, the active line is not switched if the line status is good. If the line has Loss of Signal (or other defects), it will be switched to the redundant line. (The line refers to the physical cable attached to the output of the back card.)

For APS 1+1, a front card can switch and become the standby card while its associated back card still has the active lines. The APS line will not switch during a card redundancy switch, unless the APS firmware detects that an APS switch is needed.

Following a switchyred, or active card reset, the BXM card is sent a message from switch software to have it perform an APS switch to align itself with the last user switchapsln switch request. If the last user request is "clear," full automatic APS switching is in effect with the working line in the active state by default. When there is no last user request to switch to any particular line (that is, protection line), the working line becomes active.

Note In the APS 1+1 configuration, if the protection line is active and the last user request is "clear," a switchyred will cause the working line to be active if there is no line condition on the working line. When APS 1+1 comes up, it will come up on the working line if the working line is clear. When a switchyred is issued, the active card also comes up on the working line if the working line is clear and there is no user request. In cases where the working line is in alarm or there is a user request to switch to the protection line, the card will first come up on the working line, then the card will detect the alarm or the user request and switch to the protection line.

In the APS 1+1 configuration, if the last user request was a W->P switch, then dsplog will log a W->P switching event when a switchyred is issued. On a switchyred, the newly active card comes up on working line first. Then it responds to a user request to switch from working to protection by switching to the protection line and sending an event notification to that effect. You can see the event notification in the event log by using the dsplog command.

It may be necessary to perform a switchyred command after performing a service switch with the switchapsln command so that the back card that the service switch selects has its associated front card active.

The switchyred command is sometimes referred to as soft y-red switching (also known as the "graceful switching" feature). Use it to access the Y-redundancy switching feature already in the system. Executing the switchyred command performs a graceful Y-redundancy switch in that no cards need to be reset in the process of switching from the current active card to the current standby card. Thus, all the existing channel programming on both cards remain intact, and is ready to use in the case of a fault condition (where the newly active card is found to be faulty).

To implement similar preventative maintenance procedures, this command lets you switch active and standby cards, without resetting either card. If you intend to execute the switch once every two weeks, and if the standby card is faulty, in the current scheme, during reprogramming of the reset card, an outage is experienced. To do away with the outage period, the standby card should not go through a rebuild forced by the resetting of the card. With this feature, neither card is reset, and programming is continued on both cards. This type of reprogramming ensures that all channels are programmed again on the same card. It is transparent to the user, since all the channels were never deleted; they are being reprogrammed as is typical today in the case of a regular Y-redundancy switch.

The switchyred command operates on these BXM cards:

•Y-redundancy trunk cards

•BXM Y-redundancy port cards

•BXM Y-redundancy feeder cards

In addition, you can use the switchyred command on ASI cards and BNI cards. In any case where these cards are not supported, you will be blocked from executing the command at the command line interface. The switchyred command initiates the Y-redundancy switch. It can also be initiated through a job. The switchyred command is available through the same access login as the addyred command.

The switchred command lets you switch between cards of a Y-redundancy pair, avoiding any card resets or failures. The feature is needed to allow the customer fast failure recovery in the cases where the previously standby card is found to be at fault. The feature allows for the previously active card to maintain its configuration and availability, allowing you to switch to it, either through another soft Y-redundancy switch request, or through the automated Y-red switching (which executes upon card failure).

The graceful switching command (switchyred) is applicable to BXM, ASI cards, and BNI cards.

This command requires Release 9.1 software and beyond. The cards in question have to be programmed to be Y-redundant. The states of the cards have to be Active (for the Primary card) and Standby (for the Secondary card) OR Standby (for the Primary card) and Active (for the Secondary card).

The purpose of a graceful switch is to switch from the current active card of a Y-cable pair, to the current standby card of the pair, without deactivating, resetting, or reprogramming either of the cards.

You initiate a graceful switch by issuing a switchyred command at the command line interface or through an SNMP script. The input to the command is the primary card's slot number. You can obtain this information by means of the dspyred command, which lists the Primary card of a Y-redundancy pair, and the secondary card of the Y-red pair (see Table 4-42).

Table 4-42 switchyred-Example

Slot

Card Type

Other Slot

Front Card

Back Card

3

Pri

4

BXM

LM-BXM

4

Sec

3

BXM

LM-BXM

In the above example, a Y-red has been configured using slots 3 and 4, where slot 3 is identified as the Primary card (Pri) of the pair. Using the example shown in Table 4-42, the command line would look like this:

Next Command: switchyred 3

The switchyred command displays errors on the screen for the slot used in the command line if the following conditions exist:

•if the card slot is not configured for Y-redundancy

•if the state of both cards is not valid

The command line issues a warning and prompts you to continue in case any channel programming is in progress. (Continuing at this stage introduces the risk of encountering continuity problems for a short period of time until all remaining channels are programmed.)

After you issue the command, the switch software starts the process of the graceful switch.

First, turn off the laser of the current active card (by sending it an Ox05 cbus message). In effect, stop running traffic on that card.

Next, activate and start running traffic on the current standby card, forcing it to be the new active card of the pair. This process also starts the channel reprogramming of the cards, and allows for the new standby card to be reprogrammed.

All the steps required to complete the graceful Y-redundancy switch are in Release 9.2 with the only possible difference being that neither card is reset.

There are no backward compatibility issues related to the switchyred command in Release 9.1.

The switchyred feature introduces the concept of deactivating a card without a failed state being present, or deactivating the card, or the need to reprogram all the channels on the card.

The switchyred command kicks off the graceful switch process. After you issue the command, the switch software checks for and reports the following error conditions:

•If the input slot number is invalid (the valid ranges for the slot is 1-6 and 9-15).

•If the slot is empty, an error is displayed onto the screen indicating that the slot is empty.

•If the slot is not occupied by a BXM card, an error is displayed on the screen.

•If the card in the slot specified is not configured for Y-redundancy, an error specifies that the graceful switch command is executed for the y-redundancy feature. If no Y-red is configured on the card, graceful switching cannot be performed.

If the Y-redundancy pair (specified through the primary slot) contains cards in the incorrect state, a message is displayed onto the screen indicated the incorrect state of the cards. Valid states for the cards are:

•The primary card is in active state and the secondary is in standby state.

•The primary card is in standby state, and the secondary card is in active state. No other state combination is valid.

You are prompted to continue if the following is true:

•The switch software determines that channel programming is in progress for either of the cards in the Y-redundancy pair.

To choose to continue in this state implies that channels (connections) in the process of being programmed might not exist on the standby card after the graceful switching has completed, that is, the programming must be completed on both cards.

A message displays listing the cards being switched from, and the card being switched to, just before the graceful switching process begins.

After the switching process has been kicked off, the switch software does the following:

•Turns off the laser on the active card (stopping traffic).

•Puts the current active card into the standby state.

•Activates the current standby card to be the active one of the pair.

Event logging does not distinguish between a Y-redundancy switch due to a failure (beyond logging the indication of the failure), and a Y-redundancy switch due to the execution of the switchyred command.

Syntax

switchyred

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-3

Yes

No

BPX

Yes

Related Commands

addyred, delyred, dspyred, prtyred,

tstbadubus (test NTM corruption problem)

Tests the NTM-UXM/NPM UBU corruption problem. You can use this any time you encounter a possible cell drop problem to make sure the problem is not caused by the UBU allocation. The tstbadubus command checks every allocated UBU to see if the above problem exists. If an allocation problem is detected, the falsely allocated UBUs will be displayed.

The NTM card has been known to corrupt Lane 1 of its previous UBU. But it affects only the cells, not FastPackets. Thus it may corrupt data for the UXM card (cells) and NPM (AAL5 cells) if their UBUs are located in front of the one for the NTM card.

For example, if UBU 2 is used by the NTM, the cells (not FastPackets) in Lane 1 of UBU 1 will be corrupted. Because the UXM and NPM are the only cards using the cells in the bus, the UBU immediately before the one used by NTM cannot be allocated to the UXM or NPM.

The UBU allocation software will not assign UBUs for a UXM and an NPM card, if it is next to the one for NTM (to avoid the problem mentioned above).

Workaround

If the tstbadubus screen shows something similar to the screen in Example 1, then reallocating the UBU to slot 8 might cure the problem.

Issue the dspbusbw <8> command to see how may UBUs are currently allocated to slot 8. If the allocated UBU is 10, then always add one more UBU to the card. Use cnfbusbw <8> <11> to allocate 11 UBUs to slot 8. Most of the time, this change can remove the corruption condition.

If the problem persists, then add two more UBUs to the card. The idea is that by adding one or two more UBUs to the card, the UBU locations to be allocated change, which may cure the problem. Reallocating one or two fewer UBUs may also work.

Syntax

tstbadubus

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

Yes

Yes

IGX

Yes

Related Commands

dspbusbw, cnfbusbw

Example

The twenty-fourth UBU in page 3 was "badly" allocated (causing corruption). It is allocated to the NTM located at slot 4. This UBU corrupts the UBU allocated to the UXM located at slot 8. A cell drop will be expected for slot 8 due to the corruption.

tstbadubus

sw152 TRM SuperUser IGX 8420 9.3 Apr. 13 2000 15:13 GMT

NTM-UXM UBU Corruption Test

Page UBU NTM UXM Page UBU NTM UXM Page UBU NTM UXM Page UBU NTM UXM

3 24 4 8

Total 1 Corrupted UBUs detected

Last Command: tstbadubus

tstcon (test connections)

Tests the integrity of an IGX data path by inserting node-generated test data. The connection service is affected for only a few seconds during the test. You can test only existing connections. One channel at a time is tested to minimize disruption. Because service is disrupted for a short time, no conditioning is applied during the test. If a failure is detected, the fault is isolated to a replaceable IGX node, and the standby card (if available) automatically goes into service. During fault isolation, conditioning is applied to both ends of the connection.

After testing is complete, you must use dellp to remove the loopback established by using addlocrmtlp.

The Automatic Management Routing tstcon procedure is not modified in Release 9.3.30. When tstcon is executed, the OAM loopback cells pass through the XPVC segment linking the AR-PNNI networks. When the tstcon command is executed on an XPVC segment, however, only the local Automatic Routing node information is displayed. The information for the remote PNNI node is not displayed, and the Remote Node Name and Remote Channel fields are blank. You must use the CWM or MGX Command Line Interface to display the remote PNNI node connection details.

Table 4-43 describes the results of executing tstcon.

Table 4-43 Results of tstcon Execution

Result

Description

Completed

Total number of tests that were run.

Aborted

Number of tests that did not run because the connection was not testable because of loopbacks or missing or failed hardware.

Failures

Number of tests that failed.

Repaired

Number of connections that failed a previous test and have passed the current test.

If you enter a range of channels (some with connections and some without), the unconnected channels are skipped. You can enter the tstcon command on the node at either end of the connection. Unlike the addloclp and addrmtlp commands, tstcon does not require external test equipment. You cannot test connections with the tstcon command if they are currently looped back with either the addloclp or addrmtlp commands.

Table 4-44 describes examples of the tstcon command with various arguments.

Table 4-44 Examples of tstcon Specification

Command

Description

tstcon *

Test all connections.

tstcon * f

Test all Frame Relay connections.

tstcon * v x

Test all voice connections, abort on first failure.

tstcon 1.3

Test connection on channel 1.3.

tstcon 4.2.200

Test connection on channel 4.2.200.

tstcon 1.13-16

Test connections on channels 1.13-16.

tstcon 3.21-24 x

Test connections on channels 3.21-24, abort on first failure.

tstcon 3.11-20 v

Test voice connections only on channels 3.11-20.

tstcon 3.11-20 v x

Test voice connections only on channels 3.11-20, abort on first failure.

tstcon 3.21-22 v 5

Test voice connections only on channels 3.21-22 and repeat the test five times.

tstcon 3.14-15 d x 5

Test data connections on channels 3.14-15 and repeat test five times. Abort on failure.

For V.35 ports configured for DTE, these three conditions apply:

•Model D FRP, along with software Release 8.1 or higher, supports ForeSight dynamic congestion avoidance feature. The Model D FRP is required for the AIP application in system software Release 7.1. The enhanced V.35 loopback test is available with this card when using Firmware Revision F and system software 7.1.

•A loopback test pattern signal (Test Mode) is transmitted to a modem or NTU to initiate a
loopback. Some modems and NTUs recognize this code but do not return the TM signal even though a loop has been set up. The FRPs, with the exception of the Model D Firmware Rev. F, wait to receive the TM signal from the external equipment before the data test is performed. If the FRP Model D Firmware Rev. F receives the TM signal return, it responds. If FRP Model D Firmware Rev. F does not receive the TM signal, it waits 10 seconds and then sends the test pattern. If the external equipment is inoperative or disconnected, the test fails. After the test is completed, transmission of the codes is terminated and the circuit returns to normal operation. The test result is displayed on the node's terminal tstport screen.

•Some external equipment supports loopback testing but does not recognize the loop test pattern signal (Test Mode) in the data stream. The FRP/FRI toggles the V.35 LLB (local loopback) or the LRB (remote loopback) leads and then sends the test pattern after the time-out period (10 seconds). If the external equipment is inoperative or disconnected, the test fails. The IGX control terminal displays the result of tstport execution.

Syntax

testcon <channel(s)> [-nolp] [type] [failure abort] [repeat count]

Parameters

Parameter

Description

channels

Specifies the specifies the channel or set of channels whose connections are to be tested. An "*" specifies all connections. Formats:

slot.channel-voice connection
slot.port-data connection
slot.port.DLCI-Frame Relay connection
slot.port.vpi.vci-ATM connection

-nolp

No automatic loopback. This parameter applies only to local-remote loopbacks and is mandatory for testing a multisegment connection in a tiered network.

type

Restricts the test to the designated connection type. If no connection type is designated, all connections are tested.

v-Tests only voice connections.
d-Tests only data connections.
f-Tests only Frame Relay connections

x

Aborts the test as soon as a failure is detected. If an "x" is not entered, all specified connections are tested regardless of the test results for each individual connection.

repeat count

Specifies the number of times the test is to be repeated. If no test count is specified, the test is run once.
Range: 1-50

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

BPX, IGX

OK

OK

Yes

No

Related Commands

dspcons, dspcons

Example (IGX)

Test connection 9.1.100. The connections screen appears with the connection for channel 9.1.100 highlighted. The system prompts to confirm the test. A "T" after channel under test indicates that the test is currently running on that channel.

When the first test is completed, a message appears indicating the results of the tests. As each test is completed, the T moves to the next channel to be tested and the message is updated to include the cumulative results of the tests. When the test is completed for all the specified connections, the "T" disappears and the message indicates the total number of tests and the cumulative results of the test.

tstcon 9.1.100

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 11:04 PST

Local Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
5.1 T beta )25.1 Ok 256 7/8 0 L
9.1.100 gamma 8.1.200 Ok fr 0 L
9.1.200 gamma 8.1.300 Ok fr 0 L
9.2.400 beta 19.2.302 Ok fr(Grp) 0 L
14.1 gamma 15.1 Ok v 0 L

Last Command: tstcon 9.1.100

Tests: Completed = 1, Aborted = 0, Failed = 1, Connections Repaired = 0
Next Command:

tstconseg (test connection segment)

Externally tests the integrity of a connection by sending OAM segment loopback cells over the specified channel for the specified number of times.

With Release 9.3.30, the BPX 8600 supports an Extended PVC (XPVC) that spans over an Automatic Routing Management (AR)-PNNI, or AR-PNNI-AR, hybrid network. However, the AR tstconseg procedure is not modified. When tstconseg is executed, the OAM loopback cells pass through the XPVC segment linking the AR-PNNI networks. When the tstconseg command is executed on an XPVC segment, however, only the local AR node information is displayed. The information for the remote PNNI node is not displayed, and the Remote Node Name and Remote Channel fields are blank. You must use CWM or MGX CLI to display the remote PNNI node connection details.

Table 4-45 describes the reported results of executing tstconseg.

Table 4-45 Results of Executing tstconseg

Result

Description

Completed

Total number of tests that were run.

Aborted

Number of tests that did not run because the connection was not testable because of loopbacks or missing or failed hardware.

Failures

Number of tests that failed.

Repaired

Number of connections that failed a previous test and have passed the current test.

Syntax

tstconseg <channel> <iteration count> [A | a]

Parameters

Parameter

Description

<channel>

Specifies the slot.port.vpi.vci of the channel to be tested.

<iteration count>

Number of times to repeat the test.

[A | a]

Specifies that the test be aborted if an error occurs (not case-sensitive).

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-5

Yes

Yes

BPX, IGX

OK

OK

Yes

No

Related Commands

dspcons

Example (BPX)

Test connection segment 11.2.10.17. The connections screen appears with the connection for channel 11.2.10.17 highlighted. The system prompts to confirm that the test should begin. A "T" after the channel under test indicates the test is currently running on that channel. When the first test is complete, a message appears indicating the results of the tests. As each test is completed, the T moves to the next channel to be tested and the message is updated to include the cumulative results of the tests. When the test is completed for all the specified connections, the T disappears and the message indicates the total number of tests and the cumulative results of the test.

tstconseg 11.2.10.17

nmsbpx23 TN SuperUser BPX 8620 9.3 Apr. 13 2000 12:37 PST

Local Remote Remote Route
Channel NodeName Channel State Type Avoid COS O
11.2.10.17 nmsbpx23 11.1.11.17 Ok atfst

This Command: tstconseg 11.2.10.17 1

Perform a tstconseg on this connection (y/n)?

----------------

nmsbpx23 TN SuperUser BPX 8620 9.3 Apr. 13 2000 12:38 PST

External Connection Segment Test

Status: Test Complete

Connection ID Test Count Failure Count Success Count
11.2.10.17 1 1 0

Last Command: tstconseg 11.2.10.17 1

Next Command:

tstdelay (test connection round-trip delay)

Puts the remote end of the connection into a loopback state, requests the FRP (Frame Relay) or ASI (ATM) to generate a test packet, calculates and displays the round-trip delay (RTD). This delay includes the FRP or ASI and trunk queuing and processing delays throughout the network. The measured delay using tstdelay differs from the ForeSight RTD, which uses a high-priority packet and does not include processing and queuing delays.

Using the tstdelay command requires that the FRP is at least a Model D. This test interrupts transmission on the connection during the test. Test results appear at the bottom of the screen (this may include a timeout message, as in Example 1).

Testing an IGX node that has been configured as an interface shelf requires execution of addlocrmtlp prior to tstdelay and a tstdelay parameter that applies only to tiered networks (see optional parameter table). After testing is complete, the loopback established with addlocrmtlp must be removed by dellp.

Cisco BPX 8600 series switches now support an Extended PVC (XPVC) that spans over an Automatic Routing Management (AR)-PNNI, or AR-PNNI-AR, hybrid network. Both the AR BXM and PNNI AXSM interface cards support Enhanced UNI (EUNI) and Enhanced NNI (ENNI) port types. With the EUNI/ENNI port types, all new XPVC segment connections are programmed as "non-segment". This non-segment status allows OAM segment loopback cells to flow through a multi-segment XPVC in the hybrid AR-PNNI network. Note that the tstdelay command cannot be executed at a ENNI endpoint if the XPVC segment connection remains programmed as "non-segment".

The AR test delay procedure is slightly modified in Release 9.3.30. When tstdelay is executed, the OAM loopback cells pass through the XPVC segment linking the AR-PNNI networks. When the tstdelay command is executed on an XPVC segment, however, only the local AR node information is displayed. The information for the remote PNNI node is not displayed, and the Remote Node Name and Remote Channel fields are blank. You must use the CWM or MGX CLI to display the remote PNNI node connection details.

Syntax

tstdelay <slot.port.DLCI> [count] | tstdelay <slot.port.vpi.vci> [-nolp] [count] [y | n]

Parameters

Parameter

Description

<slot.port.DLCI>

Specifies the Frame Relay channel of the connection to be tested.

[count]

Specifies the number of times the test is to be repeated. If you do not specify a count, the test runs once.
Range: 1-50

tstdelay

<Reviewers, we need a parm desc.>

<slot.port.vpi.vci>

Specifies the ATM channel of connection to be tested

[-nolp]

No automatic loopback. This parameter applies to only local-remote loopbacks and is mandatory for testing a multisegment connection in a tiered network.

[y | n]

Specifies that the ForeSight RTD is included and applies to ATM connections only.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-5

Yes

Yes

BPX, IGX

OK

OK

Yes

No

Related Commands

addlocrmtlp, dellp, dspcons, dspcons

Example (IGX)

Test the delay on Frame Relay channel 9.1.100.

tstdelay 9.1.100

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 11:05 PST

Conn: 9.1.100 gamma 8.1.200 fr
MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR FST
9.6/9.6 9.6/9.6 5/5 256/256 10/10 65535/65535 9.6/9.6 n
% Util: 100/100
Owner: LOCAL Restriction: NONE COS: 0 Status: Failed Test
Group: NONE Priority: H TestRTD: 0 msec

Path: alpha 14--13beta 15--15gamma
Pref: alpha 14--13beta 15--15gamma

alpha 9.1.100 gamma 8.1.200
FRP: OK FRP: OK
FRI: OK FRI: OK

Last Command: tstdelay 9.1.100

Test delay timed out
Next Command:
Example (BPX)

Test the delay on ATM connection 9.1.1.1. The first prompt that follows initial command entry is for whether the ForeSight RTD should be included. The second prompt is for confirming that the test should proceed.

tstdelay 9.1.1.1

bpx1 TN SuperUser BPX 8620 9.3 Apr. 13 2000 13:45 PST

Conn: 9.1.1.1 ]bpx6 11.1.1.1 abr Status: OK
SCR MBS MCR ABR PCR UPC FST CLP % util
4000/4000 1000/1000 4000/4000 4000/4000 y y y 100/100
Owner: REMOTE Restriction: NONE COS: 0
Group: NONE ForeSightRTD: 40 msec TestRTD: 10 msec

Path: bpx1 1.3-- 3.3bpx6
Pref: Not Configured

bpx1 ASI-T3 : OK bpx6 ASI-T3 : OK
Line 9.1 : OK Line 11.1 : OK
OAM Cell RX: Clear

Last Command: tstdelay 9.1.1.1 n

Round trip delay is 10 msec.
Next Command:

tstpcs (test port concentrator shelf)

Tests the data path for PCS ports for a selected module. The port parameter specifies the particular PCS module: an FRM-2 or FRP-2 physical port to which one of the PCS modules connects.

Upon command entry, each of the 11 ports for the PCS goes into a loop state. In this state, data goes to each port and loops back to the PCS module. Test frames go to a port and are checked for integrity when they return. The test frames also go out on the port.

During this test, any Frame Relay connection data received by the FRM-2 or FRP-2 destined for one of the ports is discarded. The other three Port Concentrator modules are unaffected. After the test, the port is returned to its previous configuration.

The PCS tests available RAM, and sets each of the 11 ports into a loop mode. Ten frames of data are sent to each port and checked to make sure the same frames are received in entirety and in order.

During a test, the dsppcs screen shows "Testing" then either "Passed" or "Failed." The test takes about 15 seconds.

Syntax

tstpcs <slot.port>

Parameters

Parameter

Description

slot.port

Slot is the location of an FRM-2 or FRP-2 card. Port selects the physical port to which a PCS module connects.
Range: 1-4

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

IGX

Yes

Related Commands

dsppcs, resetpc

tstport (test port)

Executes a port loopback test on the specified data port. Using tstport without the optional parameter performs an internal test. The loopback for the internal test is performed on the IGX back card and is used to test just the IGX front and back cards. The test disables the communications for that port and the back card is placed into a loopback mode. The applicable card sets for the tstport command are the FRP, FRM, SDP, HDM, LDP, and LDM. The card under test sends several frames of data to the port on the interface card, loops them back, and checks their integrity.

If connections exist on the port being tested, the dspcons screen appears. If no connections are present, the dspport screen appears. A flashing T in the connections screen indicates those connections affected by the test. Either a "(" character or a ")" character indicates the loopback in the dspfrport. If a local or remote test fails, the port itself is automatically tested (internal) to determine if the IGX node caused the failure.

For a Frame Relay port or an LDP or LDM port, an external loopback may be placed at the near (local) or far (remote) modem during the test. For a DDS port, the external loopback is a CSU or DSU loopback at the remote DSU device. If an external port loopback test fails, the internal port loopback test is executed to determine if the IGX node caused the failure. The cnfict command can be used to specify the interface control lead template used to condition the output control leads during loopback.

The local and remote modem tests that test the near end and far end modems or NTUs require the IGX back card to operate as a DTE, so the modem acts as a DCE in this case. The back card asserts the local or remote loopback pin of the V.35 port. For X.21 ports, which do not have a loopback pin defined, the back card sends a loopback command in the data stream to cause the NTU to go into loopback mode. The test then begins.

The loopback test operation sends several frames of test data, receives them back, compares them, and verifies their integrity. The loopback pin subsequently returns to the inactive state, and the modems return to normal operation. The local or remote test works with only those modems that recognize a local and remote loopback command.

Before starting a test, you must be sure the cabling is correct for the specific equipment. The test conventions are described in CCITT V.54 and X.21 specifications. Only the near (n) and far (f) options are available for the Model C SDP. If the near or far tests fail, no internal test is executed on the SDP to isolate the problem. The SDP is not failed due to a tstport failure.

Syntax

tstport <slot.port> [n | f]

Parameters

Parameter

Description

slot.port

Slot is the location of a card. Port selects the physical port to which a module connects.

[n | f]

n = near external port loopback test

f = far external port loopback test

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

IGX

Yes

Related Commands

cnfict, dspcons,

Example

Perform an internal port test on a Frame Relay port.

tstport 9.1

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 11:27 PST

Conn: 9.1.100 gamma 8.1.200 fr
MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR FST
9.6/9.6 9.6/9.6 5/5 256/256 10/10 65535/65535 9.6/9.6 n
% Util: 100/100
Owner: LOCAL Restriction: NONE COS: 0 Status: Failed Test
Group: NONE Priority: H TestRTD: 0 msec

Path: alpha 14--13beta 15--15gamma
Pref: alpha 14--13beta 15--15gamma

alpha 9.1.100 gamma 8.1.200
FRP: OK FRP: OK
FRI: OK FRI: OK

Last Command: tstport 9.1

No external clock is detected for DTE
Next Command:
Example

Perform a local (near end) loopback test on port 32.1 (requires port to be configured as DTE).

tstport 32.1 n

Example

Perform a remote (far end) loopback test on port 32.1 (requires port to be configured
as DTE).

tstport 32.1 f

Example

Perform a test of an FRP port.

tstport 9.1

tststats (test statistics)

Displays a summary of the test statistics that result from performing a tstcon command on various network connections.

Before tststats displays any meaningful statistics, the tstcon command must run on one or more network connections. The statistics are displayed for voice, data, and Frame Relay connections.

•Tests Completed, Passed, Failed, and Aborted.

•Failure data per failed connection (applies only to voice connections).

•Slot.channel—Indicates which connection has failed.

•Good reads—Indicates number of good reads on the test failure.

•Bad reads—Indicates number of bad reads on the test failure.

Note The tstcon command should have run before you enter tststats.

Syntax

tststats [clear]

Parameters

Parameter

Description

[clear]

Specifies that the test statistics buffers be cleared.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX, IGX

No

Related Commands

tstcon

Example (IGX)

tststats

sw150 TN SuperUser IGX 8420 9.3 Apr. 13 2000 21:54 GMT

Connection Test results since: Date/Time Not Set

Type Total Passed Failed Aborted
Voice 0 0 0 0
Data 0 0 0 0
Fr Relay 0 0 0 0
Last Command: tststats
Next Command:

upcd (up card)

Activates a card you have downed with the dncd command. If a slot contains a complete card set, both the front and back card are upped. After a card set is upped, it is available as a node resource.

When you activate a card, it comes up in either the standby or active state. The initial state depends on whether the network is ready to use the card immediately.

Syntax

upcd <slot>

Parameters

Parameter

Description

slot

Specifies the card slot number of the card

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-3

Yes

No

BPX, IGX

Yes

Related Commands

dncd, dspcds

Example (IGX)

Activate the FRM in slot 9.

upcd 9

sw180 TN Cisco IGX 8420 9.3.g0 Oct. 20 2000 09:16 GMT

FrontCard BackCard FrontCard BackCard
Type Rev Type Rev Status Type Rev Type Rev Status
1 NPM BVS Standby 9 FRM KSB FRI-T1 AL Standby
2 NPM BWS Active 10 Empty universal backplane
3 Empty universal backplane 11 Empty universal backplane
4 UXM CD23 T3 AA Active 12 URM AA11 2FE2V EW Active
5 UXM CA23 OC3 AD Active 13 LDM CK03 232-8 AJ Standby
6 FRM DHZ FRI-V35 BD Standby-T 14 URM AA13 2FE2V P03 Active
7 Empty universal backplane 15 URM AA12 2FE2V EW Active
8 Empty 16 NTM FHF T1 AL Active

Last Command: upcd 9

upcon (up a connection)

Ups (activates) a connection, bundle of connections, group of connections, or all connections with a COS or COS range. When a connection is upped, the system tries to route. If the connection cannot immediately be routed, the connection is failed and generates a major alarm. The State display column in an upcon or dspcons screen has these meanings:

•"OK" means routed.

•"Down" means downed.

•"OK(Dn)" means waiting for on-hook to occur to allow courtesy down to take place for connections that have been courtesy downed by using the dncon command.

•"Failed" means not routed, but trying.

Syntax

upcon {<group | local_chan(s)> | COS <cos_range>}

Parameters

Parameter

Description

<group | local_chan(s)>

Specifies a group, a channel, or a range of channels to activate.

COS <cos_range>

Specifies the COS or COS range. Range: 0-15

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

IGX

Yes

Related Commands

dncon, dspcon, dspcons

Example

Activate connections 5.1.

upcon 5.1

alpha TRM YourID:1 IGX 8420 9.3 Apr. 13 2000 11:33 PST

Local Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
5.1 beta )25.1 Ok 256 7/8 0 L
9.1.100 gamma 8.1.200 Ok fr 0 L
9.1.200 gamma 8.1.300 Ok fr 0 L
9.2.400 beta 19.2.302 Ok fr(Grp) 0 L
14.1 )gamma 15.1 Ok v 0 L

Last Command: upcon 5.1
Next Command:
Example

Activate a range of connections 9.1-4.

upcon 9.1-4

Example

Activate a Frame Relay group connection.

upcon alpha

Example

Activate all downed connections with a COS of 9.

upcon 9

Example

Activate all downed connections with a COS of 9-12.

upcon cos 9-12

upgdlogcd (upgrade logical card database)

Manually upgrade the logical card database when upgrading from a BXM card to a BXM-E card. This command should be used in conjunction with the cnfnodeparm command.

1. Use the cnfnodeparm command and set the auto BXM upgrade parameter to N, specifying that you do not want the logical card database to be upgraded automatically when the new BXM-E card replaces the BXM card. The default value for the parameter auto BXM upgrade is N.

2. Replace the BXM card with the BXM-E card.

3. Use the upgdlogcd command to manually upgrade the logical card database on the active slot.

Upgrading the logical card database manually instead of automatically allows you to easily switch back to the legacy card before the upgdlogcd command is executed. By default, the cnfnodeparm parameter auto BXM upgrade is set to Y. Using this default setting, the logical card database is automatically upgraded.

Refer to the BPX 8600 Installation and Configuration Guide for a list of upgrade options and procedures.

Syntax

upgdlogcd <log_card_num>

Parameters

Parameter

Description

<log_card_num>

Specifies the logical card number; for example, upgdlogcd 6 upgrades the logical card database on the active BXM-E in slot 6.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX

Yes

Related Commands

cnfnodeparm, cnfcdparm

Example

Set the auto BXM upgrade parameter to N, specifying that you do not want the logical card database to be upgraded automatically when the new BXM-E card replaces the BXM card.

cnfnodeparm 54 n

Example

Set the Auto BXM Upgrade Parameter to N.

w116 TN StrataCom BPX 8620 9.3.0S Feb. 29 2000 16:37 GMT

1 Update Initial Delay [ 5000] (D) 16 Stats Memory (x 100KB) [ 132] (D)
2 Update Per-Node Delay [30000] (D) 17 Standby Update Timer [ 10] (D)
3 Comm-Break Test Delay [30000] (D) 18 Stby Updts Per Pass [ 50] (D)
4 Comm-Break Test Offset [ 10] (D) 19 Gateway ID Timer [ 30] (D)
5 Network Timeout Period [ 1700] (D) 20 GLCON Alloc Timer [ 30] (D)
6 Network Inter-p Period [ 4000] (D) 21 Comm Fail Delay [ 60] (D)
7 NW Sliding Window Size [ 1] (D) 22 Nw Hdlr Timer (msec) [ 50] (D)
8 Num Normal Timeouts [ 7] (D) 23 SAR CC Transmit Rate [ 560] (D)
9 Num Inter-p Timeouts [ 3] (D) 24 SAR High Transmit Rate [ 280] (D)
10 Num Satellite Timeouts [ 6] (D) 25 SAR Low Transmit Rate [ 56] (D)
11 Num Blind Timeouts [ 4] (D) 26 SAR VRAM Cngestn Limit [ 7680] (D)
12 Num CB Msg Timeouts [ 5] (D) 27 SAR VRAM Cell Discard [ 256] (D)
13 Comm Fail Interval [10000] (D) 28 ASM Card Cnfged [ Y] (Y/N)
14 Comm Fail Multiplier [ 3] (D) 29 TFTP Grant Delay (sec) [ 1] (D)
15 CC Redundancy Cnfged [ Y] (Y/N) 30 TFTP ACK Timeout (sec) [ 10] (D)

This Command: cnfnodeparm

sw116 TN StrataCom BPX 8620 9.3.0S Feb. 29 2000 16:37 GMT

1 Update Initial Delay [ 5000] (D) 16 Stats Memory (x 100KB) [ 132] (D)
2 Update Per-Node Delay [30000] (D) 17 Standby Update Timer [ 10] (D)
3 Comm-Break Test Delay [30000] (D) 18 Stby Updts Per Pass [ 50] (D)
4 Comm-Break Test Offset [ 10] (D) 19 Gateway ID Timer [ 30] (D)
5 Network Timeout Period [ 1700] (D) 20 GLCON Alloc Timer [ 30] (D)
6 Network Inter-p Period [ 4000] (D) 21 Comm Fail Delay [ 60] (D)
7 NW Sliding Window Size [ 1] (D) 22 Nw Hdlr Timer (msec) [ 50] (D)
8 Num Normal Timeouts [ 7] (D) 23 SAR CC Transmit Rate [ 560] (D)
9 Num Inter-p Timeouts [ 3] (D) 24 SAR High Transmit Rate [ 280] (D)
10 Num Satellite Timeouts [ 6] (D) 25 SAR Low Transmit Rate [ 56] (D)
11 Num Blind Timeouts [ 4] (D) 26 SAR VRAM Cngestn Limit [ 7680] (D)
12 Num CB Msg Timeouts [ 5] (D) 27 SAR VRAM Cell Discard [ 256] (D)
13 Comm Fail Interval [10000] (D) 28 ASM Card Cnfged [ Y] (Y/N)
14 Comm Fail Multiplier [ 3] (D) 29 TFTP Grant Delay (sec) [ 1] (D)
15 CC Redundancy Cnfged [ Y] (Y/N) 30 TFTP ACK Timeout (sec) [ 10] (D)

This Command: cnfnodeparm

Continue? y
sw116 TN StrataCom BPX 8620 9.3.0S Feb. 29 2000 16:38 GMT

31 TFTP Write Retries [ 3] (D) 46 Max Htls Rebuild Count [ 100] (D)
32 SNMP Event logging [ Y] (Y/N) 47 Htls Counter Reset Time[ 1000] (D)
33 Job Lock Timeout [ 60] (D) 48 Send A-bit early [ N] (Y/N)
34 Max Via LCONs [50000] (D) 49 A-bit Tmr Multiplier M [ 0] (D)
35 Max Blind Segment Size [ 3570] (D) 50 A-bit Tmr Granularity N [ 3] (D)
36 Max XmtMemBlks per NIB [ 3000] (D) 51 FBTC with PPDPolicing [ N] (Y/N)
37 Max Mem on Stby Q (%) [ 33] (D) 52 CommBrk Hop Weight [ 25] (D)
38 Stat Config Proc Cnt [ 1000] (D) 53 CB Fail Penalty Hops [ 2] (D)
39 Stat Config Proc Delay [ 2000] (D) 54 Auto BXM upgrade [ Y] (Y/N)
40 Enable Degraded Mode [ Y] (Y/N)
41 Trk Cell Rtng Restrict [ Y] (Y/N)
42 Enable Feeder Alert [ N] (Y/N)
43 Reroute on Comm Fail [ N] (Y/N)
44 Auto Switch on Degrade [ Y] (Y/N)
45 Max Degraded Aborts [ 100] (D)

This Command: cnfnodeparm

Enter parameter index: 54
Enter 'Yes' or 'No': n

sw116 TN StrataCom BPX 8620 9.3.0S Feb. 29 2000 16:39 GMT

31 TFTP Write Retries [ 3] (D) 46 Max Htls Rebuild Count [ 100] (D)
32 SNMP Event logging [ Y] (Y/N) 47 Htls Counter Reset Time[ 1000] (D)
33 Job Lock Timeout [ 60] (D) 48 Send A-bit early [ N] (Y/N)
34 Max Via LCONs [50000] (D) 49 A-bit Tmr Multiplier M [ 0] (D)
35 Max Blind Segment Size [ 3570] (D) 50 A-bit Tmr Granularity N [ 3] (D)
36 Max XmtMemBlks per NIB [ 3000] (D) 51 FBTC with PPDPolicing [ N] (Y/N)
37 Max Mem on Stby Q (%) [ 33] (D) 52 CommBrk Hop Weight [ 25] (D)
38 Stat Config Proc Cnt [ 1000] (D) 53 CB Fail Penalty Hops [ 2] (D)
39 Stat Config Proc Delay [ 2000] (D) 54 Auto BXM upgrade [ N] (Y/N)
40 Enable Degraded Mode [ Y] (Y/N)
41 Trk Cell Rtng Restrict [ Y] (Y/N)
42 Enable Feeder Alert [ N] (Y/N)
43 Reroute on Comm Fail [ N] (Y/N)
44 Auto Switch on Degrade [ Y] (Y/N)
45 Max Degraded Aborts [ 100] (D)

Last Command: cnfnodeparm 54 n
Example

Manually upgrade the logical card database on the BXM-E3 in slot 6.

upgdlogcd 6

sw116 TN StrataCom BPX 8620 9.3.0S Feb. 29 2000 16:24 GMT

Missing Cards: 1 BCC

FrontCard BackCard FrontCard BackCard
Type Rev Type Rev Status Type Rev Type Rev Status
1 BNI-T3 CHM T3-3 BE Standby 9 BNI-155 BDM Empty Standby
2 Empty 10 Empty
3 Empty 11 Empty
4 ASI-T3 CXF T3-2 BE Standby-T 12 BNI-T3 CFM T3-3 BE Active
5 BNI-T3 CEM T3-3 FL Active 13 BNI-T3 CFM T3-3 BE Active
6 BXM-E3 FB01 TE3-12BA Active 14 ASI-155 HDC MMF-2 AB Active
7 BCC-3 DRM LM-2 AC Active 15 ASM ABA LMASM EV Active
8 Empty reserved for Card

Last Command: dspcds

Next Command: upgdlogcd 6

upgdvsilcn (expand VSI LCN to 60K for BXM-E)

Configures a BXM-E card slot to support 60K LCN for VSI. Only BXM-E card models DX and EX support this configuration.Theupgdvsilcn command hitlessly upgrade the active BXM-E card slot to support 60K LCN for VSI. For additional information on this feature, see the 60K Channel Support for VSI on the BPX, page 2-10.

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.

Switch software logs an event when the upgdvsilcn command is executed. Use the dsplog command to review the event log.

Syntax

upgdvsilcn <slot>

Parameters

Parameter

Description

slot

Specifies the slot number of the BXM-E model DX or EX card.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

SuperUser

No

No

BPX

No

Yes

Yes

No

Related Commands

none

Example

Expand BXM-E card slot 12.

upgdvsilcn 12

rogue TN Cisco BPX 8620 9.3.41 Mar. 2 2001 14:50 GMT

Detailed Card Display for BXM-155 in slot 12
Status: Active
Revision: FAH Backcard Installed
Serial Number: A34332 Type: LM-BXM
Top Asm Number: 8000309102 Revision: BA
Queue Size: 524280 Serial Number: 111111
Support: 8 Pts, OC3, FST, VcShp Top Asm Number:
Supp: VT,ChStLv 1,VSI(Lv 3,ITSM) Supp: 8 Pts,OC3,MMF,RedSlot:NO
Supp: APS(FW)
Support: LMIv 1,ILMIv 1,NbrDisc
Support: OAMLp, TrfcGen, PPDPolic
#Ch:32768,PG[1]:32736,PG[2]:32736
PG[1]:1,2,3,4,PG[2]:5,6,7,8,
#Sched_Ch:61440 #Total_Ch:61376
Type: BXME, revision DX

Last Command: upgdvsilcn 12

upln (up a line)

Activates (ups) a line. Use the upln command to make the line available for configuring and to start statistics gathering.

Configure the line's signal characteristics for the data you intend for the line using the cnfln command.Once both ends of the line are active, you must activate ports at both ends of the line by executing the upport command. Once completed, add connections with the addcon command.

A line consists of a cable for transmitting data and the interface circuitry for the line. The cable can be a coaxial wire, fiber optic, or a twisted pair.

As of Release 9.3, you can configure an IMA line for ports as well as trunks. Use the upln command to create an IMA group. As of Release 9.3.0, upln does not automatically configure a port (for BPX only).

The BXM or UXM card can be a trunk card and a line (port) card at the same time. For example, a BXM slot can up port 1 as a trunk interface while upping port 2 as a line interface.

The first connection in the string becomes the primary link (how the IMA group is recognized in other screens), such as dspport, dspports, and cnfln.

upln 10.1,3,6,8 adds the primary link 10.1 and the non-consecutive physical lines 10.3, 10.6, and 10.8. When you use other commands, such as dnln or cnfln, this IMA group is known by the primary link, 10.1.

upln 10.5-7,2-3 adds the primary link 10.5 and the physical lines 10.5, 10.6, 10.7, 10.2, and 10.3. When you use other commands, such as dnln or cnfln, this IMA group is known by the primary link, 10.5.

Syntax

upln <line_number>

Parameters

Parameter

Description

<line_number>

For a BPX ATM line: slot.line

For IGX only: slot.line<,line,line,...>

If the line is not an IMA line, use slot.line, otherwise line in slot.line indicates the first (primary) IMA line that comprises the IMA group, and other line parameters denote other lines on the interface as part of the IMA group.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

BPX, IGX

upport (up port)

Activates a single port on Frame Relay (FRP, FRM, or UFM) card or 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).

With a Port Concentrator Shelf (PCS), upping (activating) the first port causes the FRP-2 or FRM-2 to begin communicating with the four PCS modules and to download code to them if necessary.

As of Release 9.3.0, upln does not automatically configure a port. You can verify that the line has been activated by using the dsplns command.

Syntax

For ASI, BXM, or UXM:
upport <slot.port>[.<vport>]

For UFM-U, FRM, or FRP:
upport <slot.port>

For UFM-C:
upport <slot.port> <line>

Parameters

Parameter

Description

<slot >

Specifies slot number of the card containing the port.

<port>

Specifies the port.
Range on UFM-C: 1-250
Range on UFM-U with a UFI-12V.35 or UFI-12X.21: 1-12
Range on UFM-U with a UFI-4HSS: 1-4
Range on an FRP or FRM: 1-4
Range on an FRP-2 or FRM-2: 1-44

<vport>

The optional vport identifier (BXM card only). Range: 1-31

<line>

Applies to UFM-C only. The line is the physical connector.
Range (T1 or E1): 1-8

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

BPX, IGX

Yes

Related Commands

dnport, cnfport, cnffrport, upln, addport, delport

Example (BPX)

Activate port 3 on the BXM card in slot 11.

upport 11.3

sw53 TN Cisco BPX 8620 9.3.m0 Dec. 19 2000 13:00 GMT

Port: 11.3 [FAILED ] Bandwidth/AR BW: 353208/353208
Interface: LM-BXM CAC Override: Enabled
VPI Range: 0 - 255 CAC Reserve: 0
Type: UNI %Util Use: Disabled
Shift: SHIFT ON HCF (Normal Operation)
SIG Queue Depth: 640 Port Load: 0 %

Protocol: NONE Protocol by Card: No

Last Command: upport 11.3
Example (IGX)

Activate port 2 on the card in slot 9 of the IGX.

upport 9.2

sw108 VT Cisco IGX 8420 9.3.q2 Dec. 20 2000 12:37 GMT

Port: 9.2 [FAILED] CABLE MISMATCH
Interface: V35 DCE Configured Clock: 256 Kbps
Clocking: Normal Measured Rx Clock: 0 Kbps

Port ID 0 Min Flags / Frames 1
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec
DE Threshold 100 % N391 Full Status Poll 6 cyl
Signalling Protocol None EFCI Mapping Enabled No
Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Interface Control Template
N393 Monitored Events Count 4 Lead CTS DSR DCD
Communicate Priority No State ON ON ON
Upper/Lower RNR Thresh 75%/ 25%

Last Command: upport 9.2

Activates a port on a Frame Relay card. The applicable cards are all versions of the FRP, FRM, and UFM series of cards. If the port has not been configured through the cnffrport command, a set of default configuration values apply.

With a Port Concentrator Shelf (PCS), upping the first port causes the FRP-2 or FRM-2 to begin communicating with the four PCS modules and to download code to them if necessary.

uptrk (up trunk)

Activates (or ups) a trunk. If you include the optional vtrk parameter for applicable cards, uptrk also activates the trunk as a virtual trunk. You also use uptrk to enable a feeder trunk on a port.

After you have upped the trunk but not yet added it, the trunk carries line signaling but does not yet carry live traffic. Before you add the trunk by using addtrk, the node can monitor the trunk for reliability. Once a trunk has shown reliability and is ready to go into service, add the trunk to the network. If you need to take an active trunk out of service, use dntrk. The dntrk command causes the node to reroute any existing traffic if sufficient bandwidth is available.

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 a single port is upped as a trunk (by using the uptrk command), all the remaining ports on that card are 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.

As of Release 9.3.0, upln no longer automatically configures a port. After you add a port (addport), you can begin to add connections by using addcon. You can verify that the line has been activated by using the dsplns command.

This feature allows the BXM and UXM trunks to be trunk line cards as well as circuit line cards, and to allow trunks and circuit lines to coexist on these cards.

For example, assuming that a four-port BXM card is plugged into slot 11, you could do the following:

1. uptrk 11.1
Up a trunk at port 1 on slot 11

2. upln 11.2
Up a line at port 2 of slot 11

3. upln 11.3
Up a line at port 3 of card slot 11

4. uptrk 11.4
Up a trunk at port 4 of card slot 11

You can now mix physical and virtual trunk specifications. For example, after you up a trunk as a standard trunk, you can then add it as a virtual trunk when you execute addtrunk. Furthermore, if you want to change trunk types between standard and virtual, you must first down the trunk with dntrk, then up it as the new trunk type.

You cannot up a trunk if the required card is not available. Furthermore, if a trunk is executing a self-test, a "card in test" message may appear on-screen. If this message appears, re-enter uptrk.

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

In this release, to support the Multilevel Channels Statistics feature, you will be prompted when you attempt to up the line with upln or up the trunk with uptrk, warning you to initialize the channel statistics level before activating the card. This warning only applies when upping the first trunk or first line on the card:

"Channel Statistic Level must be initialized prior to card activation"

Configuring IMA Physical Lines

Release 9.1 supported a Cisco proprietary IMA (Inverse Multiplexing ATM) protocol on UXM trunks, which was able to interoperate only with Cisco products, for example, MGX-8220 IMATM. Release 9.2 supports the ATM Forum-compliant IMA protocol, which allows UXM trunks to interoperate with other vendors' equipment. IMA provides inverse multiplexing of ATM cells across multiple physical lines. The ATM Forum-compliant IMA protocol is supported only on UXM trunks.

The IMA protocol feature requires you to upgrade the UXM firmware to Model B. When you load Model B firmware onto a UXM card, all IMA trunks invoked on that card automatically perform ATM Forum-compliant IMA protocol. You do not need to use any switch software commands to enable the IMA protocol. Note that switch software Release 9.2 is not set up to work with UXM Release 9.1 firmware, so it is advised that you not downgrade to Model A firmware, as the software will not work. (The UXM firmware code space is not large enough to hold both versions of the protocol in a single firmware image.)

Note also that the ATM Forum-compliant IMA feature is not compatible with the Cisco proprietary IMA protocol supported in Release 9.1 (which uses UXM firmware Model A). Both ends of the UXM IMA trunk requires UXM firmware Model B. If the UXM trunk is connected to another device, that device must support the ATM Forum-compliant IMA protocol.

A subset of the ATM Forum compliant IMA protocol:

•You can add and delete physical links while the IMA group is active.

•You can up an IMA group with a minimum number of retained links.

•New configurable link (cnftrk) parameters:

–IMA Max. Differential Delay

–IMA Protocol Option

–IMA Clock Mode (this parameter is fixed and not configurable)

•Additional IMA group and individual physical link state and statistics can be collected.

•Allows non-consecutive physical links on the same card to be in the same IMA group. This is specific to the UXM card and is not specified as part of the ATM Forum-compliant IMA standard.

Release 9.2 supports virtual trunking on both the BPX and IGX. IMA trunk ports are referenced by the first physical line of the trunk port after uptrk has been executed. For example, you can uptrk 1.5-8.9. You can then up a second trunk (which, in this case, is a virtual trunk on slot.port 1.5) on the same trunk port using uptrk 1.5.11.

You can use a UXM IMA trunk to connect an IGX feeder node to a routing node, either an IGX or a BPX using IMATM. UXM IMA provides redundancy in case one of the physical lines on an IMA trunk should fail. This reduces the chance of a single point of failure when a single feeder trunk is out of service. Also, you may configure the services on a feeder node rather than on a router node; this indirectly allows the network to scale better with respect to the limit of 223 network nodes.

Specifying an IMA Group Member

You can define an IMA trunk consisting of non-consecutive physical lines. In addition, you can change the group member by deleting a physical line from an existing IMA trunk.

Use this syntax to specify an IMA group on a UXM trunk:

•uptrk slot.group_member.vtrk

where:

slot is the slot number

group_member is a set of physical lines composing an IMA group. You can specify the member in an expression consisting of the primary link followed by a, or - and additional physical links.

vtrk is the optional virtual trunk number. If at least one virtual trunk already exists on this port, you only have to specify the primary link as the group_member. In the case of adding a UXM IMA feeder trunk from an IGX routing node to an IGX feeder node, you will not know whether the trunk is a regular trunk or feeder trunk. There is no virtual trunk for the feeder.

For example, 9.1-4 defines trunk 9.1 to consist of four physical links, that is, 1, 2, 3, and 4 where physical link 1 is the primary link. (This example is compatible with Release 9.1.)

For example, 9.1-3,5 defines trunk 9.1 to consist of four physical links, that is, 1, 2, 3, and 5 where physical link 1 is the primary link.

For example, 9.5-7,2-3 defines trunk 9.5 to consist of five physical links, that is, 2, 3, 5, 6, and 7 where physical link 5 is the primary link.

Similarly, 9.8,2,4,6 defines trunk 9.8 to consist of all even number of physical links where physical link 8 is the primary link.

The cnftrk is used to specify the primary link on the IMA trunk.

Primary Link—In an IMA group, you must select one of the physical links to be a primary link. This primary link number is used to refer to this IMA group or trunk. You can use cnftrk to add additional links to the group or delete existing links. When deleting existing links from an IMA group, you cannot delete the primary link. You must deactivate the trunk using deltrk followed by dntrk to remove the primary link. The cnftrk will be blocked after the trunk has been added as a feeder trunk.

Feature Mismatching on Virtual Trunks

The uptrk command, in addition to other configuration commands, will perform mismatch verification on the BXM and UXM cards. For example, the uptrk command will verify whether the card has virtual trunk support. For more information about Feature Mismatching, refer to the BPX 8600 Series Installation and Configuration Manual.

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.

Syntax

uptrk <slot.port>[.vtrk]

uptrk <slot.group_member.[<vtrk]> for IMA

uptrk <slot>.<group-member(s)>

Parameters

Parameter

Description

<slot.port>

Specifies the slot and port of the trunk to activate. If the card has only one port, the port parameter is not necessary. An NTM card, for example, has one port.

<slot.group_
member>

Specifies the slot and a set of physical lines composing an IMA group on an IMA trunk to activate. You can specify the group_member in an expression consisting of the primary link followed by a, or - and additional physical links. (When specifying an IMA group, you must select one of the physical links to be a primary link. This primary link number is used to refer to this IMA group or trunk. You can use cntrk to add additional links to the group of delete existing links. When deleting existing links from an IMA group, you cannot delete the primary link. You must deactivate the trunk using deltrk, followed by dntrk to remove the primary link.

[<vtrk>]

Specifies the virtual trunk number. The maximum on a node is 32. The maximum on a T3 or E3 line is 32. The maximum for user traffic on an OC-3/STM1 trunk is 11 (so more than one OC-3/STM1 may be necessary).

When specifying an IMA group, if at least one virtual trunk already exists on this port, then you only have to specify the primary link as the group_member.

Related Commands

addtrk, dntrk, cnfrsrc

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-2

Yes

Yes

BPX, IGX

Yes

Example

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

uptrk 21 1

Example

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

uptrk 6.1.1

Example (BPX)

Show BXM trunk 11.3. The "Other End" has not been configured ("upped"). Note the message to "use confreres" to configure PVCs. Note the major alarm status.

putrid 11.3

sw53 TN Cisco BPX 8620 9.3.2J Oct. 31 2000 12:32 GMT

TRK Type Current Line Alarm Status Other End
11.2 OC3 Clear - OK sw108/4.4
11.3 OC3 Major - Loss of Sig (RED) -

Last Command: uptrk 11.3

256 PVCs allocated. Use 'cnfrsrc' to configure PVCs
Next Command:
Example (IGX)

Show UXM virtual port 5.2.1. Note that "Other End" has not been configured ("upped"). Note the message to "use confreres" to configure LCNs. Note the major alarm status.

putrid 5.2.1

------------------------------------SCREEN 1------------------------------------
sw180 VT Cisco IGX 8420 9.3.2J Oct. 31 2000 12:59 GMT

TRK Type Current Line Alarm Status Other End
5.1 OC3 Clear - OK sw108/4.2
8 T1/24 Clear - OK sw108/14

This Command: uptrk 5.2.1

256 LCNs allocated. Use 'cnfrsrc' to configure LCNs
Press any key to continue..
------------------------------------SCREEN 2------------------------------------
sw180 VT Cisco IGX 8420 9.3.2J Oct. 31 2000 13:00 GMT

TRK Type Current Line Alarm Status Other End
5.2.1 OC3 Major - Loss of Sig (RED) -
8 T1/24 Clear - OK sw108/14

Last Command: uptrk 5.2.1

vt (make a virtual connection)

Establishes a virtual terminal connection to a remote node. A virtual terminal connection has these properties:

•On the remote node, any command except the vt command can be executed.

•Multiple vt sessions is a purchasable option. With it, more than one user can vt to a node.

•During a virtual terminal session, jobs can be executed at any time.

During a vt session, the remote node name and date flash on the local terminal screen, and "Virtual Terminal" appears in the lower left corner. The bye command terminates a virtual terminal session and returns the terminal to local usage. After a default timeout of four minutes of inactivity, a vt connection automatically reverts to a local connection. This timeout is the equivalent of using the bye command.

Syntax

vt <nodename>

Parameters

Parameter

Description

node name

Specifies the name of the remote node for the virtual terminal connection. If the specified node name is not valid, the returned message states that the "Node is unknown" and prompts for the correct node name. Also, the main area of the screen names the recognized nodes in the network to help determine the correct name.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-6

Yes

No

BPX, IGX

No

Related Commands

bye

Example

Establish a virtual terminal connection to the switch named "sw53."

vt sw53

-----------------------------------SCREEN 1--------------------------------------
sw53 VT Cisco BPX 8620 9.3.2J Oct. 25 2000 06:28 GMT

Last Command:

Next Command:

Virtual Terminal CD

-----------------------------------SCREEN 2--------------------------------------
sw180 TN Cisco IGX 8420 9.3.2J Oct. 25 2000 06:31 GMT

Last Command: vt sw53

Virtual Terminal connection broken
Next Command:

window (window to external device)

Provides an interface to an external device.

To establish a session with an external device, first use the cnftermfunc command to designate the auxiliary port to serve as the external device window. To begin the session, enter the window command and specify the port. The control terminal screen subsequently clears, after which characters entered at the control terminal go to the external device and vice versa.

Because the IGX and BPX nodes "bundle" characters together before transmitting them, a slight transfer delay occurs. Transfers are delayed until the transfer buffer is filled or the keyboard is inactive for over 50 milliseconds. To end the session, enter the escape sequence designated with the cnftermfunc command. The default for the escape sequence is ^^ (SHIFT 66).

The window command can be executed over a virtual terminal connection. This makes it possible to control external devices from a single point in the network. Devices such as Channel Service Units (CSUs), routers, channel banks and other devices with RS-232 console ports can be accessed remotely with this feature.

Syntax

window <a | c>

Parameters

Parameter

Description

a

Specifies a window into external equipment attached to the node's auxiliary port. This is the default connection.

c

Specifies a window into external equipment attached to the node's control port.

Attributes

Privilege

Jobs

Log

Node

Help

History

Lock

Hipri

1-4

No

No

BPX, IGX

Yes

Related Commands

cnfterm, cnftermfunc

Example

Connect to a local router attached to the auxiliary port. The following dialogue shows the prompts and example responses.

window a

Protocol [ip]:

Target IP address: 192.9.202.1

Repeat count [5]:
Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]::

Type escape sequence to abort. ^^

Sending 5, 100-byte ICMP Echoes to 192.9.202.1, timeout is 2 seconds:

.......

Success rate is 100 percent

left #

Register	Byte	Parameter	Description
0	high low	zcr total signal state mem	Zero Crossing Total Signal State Memory
1	high low	hpf z1 hi-hi hpf z1 hi-lo	High-Pass Filter High-Pass Filter
2	high low	sam - hi sam - lo	Encoded Voice Sample Encoded Voice Sample
3	high low	vad state-hi vad state-lo	Voice Activity Detector state Voice Activity Detector state
4	high low	sil cnt mad signal state	Silent Count Modem Activity Detector Signal State
5	high low	mad wnd cnt mad fail cnt	Modem Activity Detector Wnd. Count Modem Activity Detector Fail Count
6	high low	mad state-hi mad state-lo	Modem Activity Detector state Modem Activity Detector state

Parameter	Description
<channel(s)>	Specifies the voice channel numbers to configure.
<interval>	Specifies the refresh time for the data. Range: 1-60 seconds Default: 5 seconds

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
SuperUser	No	No	BPX, IGX			Yes

Parameter	Description
slot.port	Slot and port numbers corresponding to the feeder trunk.
controller id	Controller ID number corresponding to the PNNI controller you are deleting. ID numbers should correspond to an active PNNI controller. Range: 1-32

Messages	Reason for Message
"Slot is out of range"	Line number is not correct for FRP T1/E1.
"Port does not exist"	Logical port number does not exist.
"You must first down the port"	Logical port is up.
"You must first down the port"	Specified port is not first DS0/timeslot of logical port.

Parameter	Description
slot	Specifies logical port numbers for the physical FRP or FRM T1 or E1 line. Range for T1 lines: 1-24 Range or E1 lines: 1-31
port	Specifies the logical port number of the port to delete.

Parameter	Description
<job_number>	Specifies the number of the job.
<trig_num>	Specifies the number of the trigger to delete.

Parameter	Description
<slot.port>	Specifies the slot number of the card, the physical port, and optional virtual port (BXM card only).
[.<vport>]	The optional vport identifier. Range: 1-31

Parameter	Description
<slot.port>	Specifies the physical trunk number.
[.vtrk]	Optionally specifies the virtual trunk portion of the trunk identifier.

Parameter	Description
<group \| local_chan(s)>	Specifies a group, or a channel, or a range of channels to down.
COS <cos_range>	Specifies the COS or COS range. Range: 0-15
i \| c	Specifies immediate downing (i) of the specified connections or courtesy downing (c) of the specified connections.

State	Description
"OK" (routed)	Connection is activated and able to carry traffic.
"Down"	Connection has been added to the network database but is not activated and is not able to carry traffic.
"OK(Dn)"	Waiting for on-hook to occur to allow courtesy down to take place for connection(s) that have been courtesy downed using the dncon command.
"Failed"	Unrouted, but trying to reroute.

Parameter	Description
[slot.]	Specifies the slot number, if the back card (such as a UXM card) has one line.
[line number]	Specifies the line. If the card has more than one line, include a line number.

Parameter	Description
slot	Specifies the slot number of the Frame Relay card with the port to down.
port	Specifies the port number to deactivate on the card specified by slot. Range (FRP or FRM): 1-24 or 1-31 Range (UFM-C): 1-250 Range (UFM-U with a V.35 or X.21 interface): 1-12 Range (UFM-U with a HSSI interface): 1-4
[.vport]	The optional vport identifier on the BXM card only. Range: 1-31
line	The physical line on UFM-C card sets (not used for UFM-U cards).

Parameter	Description
slot.port	Specifies the physical trunk.
vtrk	Specifies a virtual trunk number (applies to BNI only). Range (T3/E3): 1-32 Range (OC-3) 1-11

Parameter	Description
<slot.port>	Specifies the slot number of the card and the physical port.
[.<vport>]	Optionally specifies a virtual port number. BXM card only. Range: 1-31

Parameter	Description
<d>	Displays the detailed version of the log, including stack dumps. Page through the detailed version of the log by using the arrow keys or the Return key.
<number>	When an entry number is entered (found under the No. column), displays the detailed version of a specific entry in the log.
<c>	Clears the log. Optionally, you can use the clrabortlog command.

Field	Description
No.	Abort entries in the table, numbered from 1-12.
Type Error	The entry identifier. For the dspabortlog command, the identifier is "abort." Occasionally, the identifier "BadType," is displayed, indicating a problem within the table itself.
Number	The number that identifies a specific abort problem.
Data (Hex)	A 4-byte field containing information that may be useful in solving a problem. It is different for every abort number.
PC (Hex)	Program Counter. The address of the place in memory where the software was running when the abort was logged; this identifies where the problem was detected.
PROC	Process or Task. This field indicates which process was running when the problem occurred. In the above example, TN_2 is the second Telnet user task. Use the dspprf command to display all of the tasks.
SwRev	Switch software version operating on this node.
Date	Date of the abort.
Time	Time of the abort.

Command	Description
dspcds	Displays cards in the node, with F for failures.
dsplns	Displays circuit lines.
dspcons	Displays connections.
dsplog	Displays events affecting the node.
dspnds	Displays unreachable nodes within a network.
dspnw	Displays the network topology and includes alarm status of each node in the network.
dsptrks	Displays trunks.
dsppwr	Displays power supply status and internal temperature.
dsprtrslot	Displays operational information and alarm status for a specified URM embedded router.
dsprtrslots	Displays operational information and alarm status for all URM embedded routers in a node.

Parameter	Description
<line>	Specifies the line in the format slot.port.
<channel>	Specifies the channel in the format vpi.vci.

Parameter	Values	Description
Priority Bumping Enabled	ON or OFF Default: OFF	This flag specifies whether the priority bumping feature is activated on the node.
Priority Bumping Bundle	1-50 Default: 10	The number of connections that can be selected in a priority bumping routing request when PB is enabled.
Bumping Band 1	1-15 Default: 2	The lowest value in the second most important COS band. Connections with a COS value below Bumping Band 1 are implicitly grouped as the most important band, Band0. Connections in Band 0 can bump those in other bands, but cannot be bumped. Connections in Band 1 can bump those in bands 2-7, and can only be bumped by those in Band 0.
Bumping Band 2	1-15 Default: 4	The lowest value in the third most important COS band. Connections in this band can bump those in bands 3-7, and can be bumped by those in bands 0-1. Bumping Band 2 cannot be less than Bumping Band 1.
Bumping Band 3	1-15 Default: 6	The lowest value in the fourth most important COS band. Connections in this band can bump those in bands 4-7, and can be bumped by those in bands 0-2. Bumping Band 3 cannot be less than Bumping Band 2.
Bumping Band 4	1-15 Default: 8	The lowest value in the fifth most important COS band. Connections in this band can bump those in bands 5-7, and can be bumped by those in bands 0-3. Bumping Band 4 cannot be less than Bumping Band 3.
Bumping Band 5	1-15 Default: 10	The lowest value in the sixth most important COS band. Connections in this band can bump those in bands 6-7, and can be bumped by those in bands 0-4. Bumping Band 5 cannot be less than Bumping Band 4.
Bumping Band 6	1-15 Default: 12	The lowest value in the seventh most important COS band. Connections in this band can only bump those in Band7, and can be bumped by those in bands 0-5. Bumping Band 6 cannot be less than Bumping Band 5.
Bumping Band 7	1-15 Default: 14	The lowest value in the least important COS band. Connections in this band cannot bump, but can be bumped by those in bands 1-6. Bumping Band 7 cannot be less than Bumping Band 6.
Priority Bumping Active on this node?	YES or NO Default: NO	Indicates whether priority bumping is enabled or disabled on a particular node.
Number of Priority Bumping Bands	0-7	Indicates the number of priority bands enabled. If priority bumping is not enabled, this value is 0.

Statistics Object	Description
Latest bumping band	The band value of the latest reroute connection that originates from this node.
Latest bumped band	The band value of the latest connection that is bumped from this node. The bumped connection can be mastered or slaved on this node. It can even be simply traversing this node. The bumping connection also can be mastered on, slaved on, or simply that originates from this node.
Hvm bumping band	The high water mark, since the last resetting of statistics, of the band value of any reroute connection that traverses this node
Lwm bumped band	The low water mark, since the last resetting of statistics, of the band value of any connection that has been bumped from this node.
Latest # bumping conns/req	The number of reroute candidate connections in the most recent reroute request. If there are many similar connections to be routed to the same destination, this value usually represents the bundle size of the Priority Bumping reroute request.
Latest # bumped conns/req	The number of connections selected to be bumped from this node in the most recent reroute request.
Hwm # bumping conns/req	The high water mark, since the last resetting of statistics, of the number of reroute candidate connections in any reroute request.
Hwm # bumped conns/req	The high water mark, since the last resetting of statistics, of the number of connections selected to be bumped from this node in any reroute request.
Accum # bumping conns	The total number, since the last resetting of statistics, of successfully routed connections.
Accum # bumped Lcons	The total number, since the last resetting of statistics, of master or slave connections bumped from this node.
Avg # bumping conns/req	The average number, since the last resetting of statistics, of successfully routed connections in a reroute request.
Accum # bumped VLcons	The total number, since the last resetting of statistics, of via connections bumped from this node.

Parameter	Description
<slot>	Specifies the slot number of the card containing the port whose input and output pins are to be displayed.
<port>	Specifies the data port or Frame Relay port whose input and output pins are to be displayed.
[interval]	Optionally specifies the time in seconds, between updates of the breakout box display. If no interval is specified, the display is updated at five second intervals. Do not use an interval of "1" second in a busy network. Range: 1 to 60 seconds
[(measure clock speed) y \| n ]	For Port Concentrator Shelf (PCS) only, optionally directs the system to measure the clock speed. If a Port Concentrator port is selected, the last measured clock speed is displayed on the Clocking line. When Measure Clock Speed is entered as an optional parameter, the clock is measured first, and the results are displayed. Clock speed measurement for PCS ports is described in the Cisco WAN Switching System Overview information for the PCS.

16 Bit Word	Byte # (hex)	Contents
0	0,1	Hardware revision
1	2,3	Backplane Type (usually 0x65=101 decimal)
2	4,5	Backplane version (0x0000old 0x0001new)
3	6,7	Backplane serial number in ASCII - MSB
4	8,9	Backplane serial number in ASCII - MSB
5	A,B	Backplane serial number in LSB
6	C,D	Board FAB number, in ASCII - MSB
7	E,F	Board FAB number, in ASCII - LSB
8	10,11	Board FAB number, in ASCII - LSB
9	12,13	Board FAB number, in ASCII - LSB
A	14,15	Board FAB number, in ASCII - LSB
B	16,17	Board FAB number, in LSB
C	18,19	Unused
D	1A,1B	Unused
E	1C,1D	Unused
F	1E,1F	Checksum bytes - NOT SUPPORTED

Parameter	Description
<slot>	Specifies the slot number of the card containing the universal bus bandwidth information to display.
[u]	Optionally specifies that the card should update the information with the latest information calculated in firmware. If not provided, the system will prompt you.

Display	Description
Minimum Required Bandwidth	Minimum bandwidth in FastPackets per second and cells per second required for all connections currently configured on this card. This is calculated by UXM firmware as connections are added.
Maximum Port Bandwidth	Total bandwidth of all active trunks/ports on this card in FastPackets per second, cells per second, and UBUs.
Average Bandwidth and Peak Used Bandwidth	Statistics counters maintained by UXM firmware. These statistic counters display FastPackets per second, cells per second, and UBUs. Use this information when calculating the amount of bus bandwidth to be allocated. These counters are cleared when the UXM card is reset.
Last Updated time	Shows the time when the counters were last updated. This is the current time if you answered yes to the Get updated bandwidth info from card (Y/N)? prompt or entered the command with the u parameter.
Allocated Bandwidth	The bandwidth allocated for this card using the cnfbusbw command. Refer to the Cisco WAN Switching SuperUser Commands manual for more information. Allocated bandwidth is specified in FastPackets per second, cells per second and converted to UBU units by the system.

Status	Description
OK	Bus operation satisfactory
Failed TDM	A failed TDM Bus
Failed CNTL	A failed Control Bus
Needs Diagnostics TDM	The TDM bus needs diagnostics
Needs Diagnostics CNTL	The Control Bus needs diagnostics

Unit of BW	Quantity	Cell Bus Capacity
switch	8 slices or 8000 pps	20
slice	3 DS0s or 1000 pps	160
DS0	333 pps	480

Field	Description
Ingress Cells Rcv from ln	Ingress Cells received from the line (cells into the UXM from it's node).
Ingress Cells Tx to net	Ingress Cells transmitted to the network (cells out of the UXM to the network).
Ingress Cells discarded	Ingress Cells discarded by the UXM.
Ingress FPs Rcv from ln	Ingress fast packets received from the line (fast packets into the UXM from it's node).
Ingress FPs Tx to net	Ingress fast packets transmitted to the network (fast packets out of the UXM to the network).
Ingress FPs discarded	Ingress fast packets discarded by the UXM.

Parameter	Description
[slot_no]	Optionally specifies the slot number of a particular UXM card.
[interval]	Optionally specifies the interval in seconds. Default: 10 seconds.

Parameter	Description
CBABlocksAllocated	The number of CBA blocks allocated. 32 CBAs are equal to one block.
CBABlocksUsed	Number of CBA blocks used by the slot for connections.
CBAsUsed	Number of CBAs used by the slot for connections.

Field	Value	Description
BXM Front Card Fields
Status Displays the status of a card.	Active	Card in use, no failure detected.
	Active—F	Card in use, failure detected.
	Active—T	Card active, test in progress.
	Active—F-T	Card active, minor failure detected, test in progress.
	Standby	Card idle, no failure.
	Standby—F	Card idle, failure detected.
	Standby—T	Card idle, test in progress.
	Standby—F-T	Card idle, failure detected, test in progress.
	Failed	Card failed.
	Down	Card downed by user.
	Down—F	Card downed, failure detected.
	Down—T	Card downed, failure detected, test in progress.
	Mismatch	Mismatch between front card and back card.
	Update *	Configuration RAM being updated from active control card.
	Locked*	Old software version is being maintained in case it is needed.
	Dnlding*	Downloading new system software from the active PCC adjacent node from WAN Manager.
	Dnldr*	Looking to adjacent nodes or WAN Manager for either software to load or other software needs you have not specifically requested.
	Program	Occurs when new firmware is being burned on the card.
Revision		The firmware/hardware version ID.
Serial Number		The serial number of the card.
Top Asm Number		The card's 800-level part number.
Queue Size		The sum of the sizes of the ATM cell queues in one direction. Queue size = size of HP+TS+BDATA+BDATB+CBR+VBR +SIG+ABR queues.
Support or Supp		The features that the card's firmware and hardware supports.
	Pts	The number of physical ports supported by card hardware: OC3 \| OC12 \|T3 \| E3
	The card type supported	Indicates firmware supports Foresight.
	VcShp	Indicates firmware supports VCshaping.
	VT	Indicates firmware supports virtual trunks
	ChStLv	The multilevel channel statistics level currently programmed 0-3. The statistics level is configured using the command cnfcdparm. Refer to cnfcdparm (configure card parameters), page 3-143 for more information about multilevel channel statistics.
	VSI	The VSI attributes supported. Values are: lv-VSI level supported by firmware. The level is 0, 1, 2, or 3; the level represents the resources supported, i.e. LCNs, VPI, etc. ITSM-VSI level supported by firmware. I = ILMI support. T = topology support. S = signalling, QBIN support. M = multiple partition support. V = VC merge support.
	APS	The APS attributes supported. Values are: APS(FW)-APS is supported by card firmware. APS(HW1+1)-APS 1+1 is supported by card hardware. APS(ChHlv)-The number of channels supported by card is halved in order to support APS 1:1.
	F4F5	F4 AIS detection on trunks and F4 AIS to F5 AIS mapping on ports is supported by card firmware.
	LMIv	LMI version supported by card firmware.
	ILMIv	ILMI version supported by card firmware.
	NbrDisc	ILMI neighbor discovery is supported by card firmware.
	OAMLp	OAM loopback testing is supported by card firmware.
	XL	XLMI protocol supported by card firmware.
	TrfcGen	Traffic Generation testing is supported by card firmware.
	PPDPolic
	OAM-E	OAM Ping feature supported by card firmware.
#Ch		The total number of channels supported by all port groups.
	PG[1]:8160 PG[2]:8160	The number of channels contained in each port group.
	PG[1]:1,2,3,4, PG[2]:5,6,7,8	The card physical ports.
#Sched_Ch		The number of scheduler channels supported by card.
#Total_Ch		The total number of channels reported by the BXM cards.
BXM Back Card Fields
Type		The type of backcard: LM-BXM, T3-3, E3-3, T3-2, E3-2, SMF, MMF, SMFLR, LMASM, STM1, UTP, STP.
Revision		The hardware version ID.
Serial Number		The serial number of the card.
Top Asm Number		(TAN) The 800-level part number of the card.
Supp		The resources and features this card supports. For example: 8 Pts,OC3,SMF,APS,RedSlot:2
	Pts	The number of ports on the backcard
	OC3	Supports SONET OC3 with SMF
Supp (cont.)	APS	Supports APS 1:1
	RedSlot:<slot number>	If APS 1+1 supported by the backcard, and configured, this field shows the redundant card's slot number. Values are: ??- If APS 1+1 supported by the backcard, but not configured. NO- If APS 1+1 is not supported by the backcard.