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
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)
Remote Node Alarms: 1 Minor
Remote Domain Alarms: None
Routing Network Alarms: None
FastPAD Node Alarms: None
Last Command: delalmslot 11
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
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
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
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
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
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
Controller deleted successfully!
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
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
Last Execution Results: None Status: Locked
Next Execution Time: Interval:
- Failure Reaction: Abort Exec. Results: None
- Failure Reaction: Repeat 12 Times and Abort Exec. Results: None
- Failure Reaction: Repeat 12 Times and Continue Exec. Results: None
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
Trigger 1 - PLN 2 FAILURE
3 test3 09/02/97 11:11:11 Idle 1 days SuperUser
This Command: deljobtrig 1
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
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
Last Command: delshelf A241
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 -
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
Last Command: deltrkred 5
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
Last Command: deluser John
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
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
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
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
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
Line Type Current Line Alarm Status
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
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%
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
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
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
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
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)
Remote Node Alarms: 1 Minor
Interface Shelf Alarms: 1 Minor
Example
Display APS alarms.
dspalms
alexa TRM genre BPX 8620 9.3 Apr. 13 2000 16:35 PDT
Alarm summary (Configured alarm slots: None)
Remote Node Alarms: 1 Minor
Interface Shelf Alarms: None
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)
Circuit Line Alarms: None
Physical Line Alarms: None
Remote Node Alarms: 1 Unreachable, 2 Majors, 5 Minors
Interface Shelf Alarms: None
FastPAD/Access Dev Alms: None
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)
Circuit Line Alarms: None
Physical Line Alarms: None
IOS Unavailable in 1 slot
Interface Shelf Alarms: None
FastPAD/Access Dev Alms: None
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
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
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
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
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
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
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
Example
Display the parameters for configuration class 1.
dspatmcls 1
night TN SuperUser BPX 8620 9.3 Apr. 13 2000 13:22 GMT
PCR(0+1) %Util CDVT(0+1) AAL5 FBTC SCR
2000/2000 100/100 10000/10000 n 2000/2000
Description: "Default rt-VBR 2000"
_____________________________________________
PCR(0+1) %Util CDVT(0+1) AAL5 FBTC SCR
8000/8000 100/100 10000/10000 n 8000/8000
Description: "Default nrt-VBR 8000"
Last Command: dspatmcls 1
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:
Priority Bumping Active on this node [ YES]
Number of Priority Bumping Bands [ 7] (D)
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:
Priority Bumping Active on this node [ NO]
Number of Priority Bumping Bands [ 0] (D)
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
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
Clocking: Normal (255999 Baud)
Inputs from User Equipment Outputs to User Equipment
Lead Pin State Lead Pin State Lead Pin State Lead Pin State
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
Inputs from User Equipment Outputs to User Equipment
Lead Pin State Lead Pin State Lead Pin State Lead Pin State
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
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
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
Minimum Reqd Bandwidth: 0 0 0
Average Used Bandwidth: 0 0 0
Peak Used Bandwidth: 0 0 0
Maximum Port Bandwidth: - 10866 3
(Fpkts / 2 + Cells) <= 32000
Reserved Bandwidth: - 4000 1
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
Minimum Reqd Bandwidth: 0 0 0
Average Used Bandwidth: 0 0 0
Peak Used Bandwidth: 0 0 0
Maximum Port Bandwidth: - 10866 3
(Fpkts / 2 + Cells) <= 32000
Reserved Bandwidth: - 4000 1
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 A (slot 7): Active - OK
Bus B (slot 8): Standby - OK
Example (IGX)
dspbuses
sw197 TN SuperUser IGX 8420 9.3 Apr. 13 2000 04:10 GMT
Bus Bandwidth usage in Fastpackets/second (Snapshot)
Available = 1082000 (92%)
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
Available MUXBUS bandwidth (snapshot)
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
Collection Time: 1 day(s) 03:15:51 Clrd: Date/Time Not Set
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
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 Blocks allocated = 63 CBA Blocks used = 16
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
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
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
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
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
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
Detailed Card Display for BXM-155 in slot 13
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
Support: LMIv 1,ILMIv 1,NbrDisc,XL
Support: OAMLp, TrfcGen, PPDPolic
#Ch:32768,PG[1]:32736,PG[2]:32736
#Sched_Ch:61440 #Total_Ch:61376
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
Hardware Error Total Events: 0 Threshold Counter: 0
Last Command: dspcderrs 11
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
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
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
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
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
7 BCC BWF LMBCC AC Active 15 ASM ACA LMASM AC Active
8 Empty reserved for Card
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
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
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
Onhk B 3 Signaling TSP MODE
This Command: dspchan 7.1
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
SIG RATE 0 iec tone dsbl 1
Last Command: dspchan 7.1
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
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
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
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
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
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
Last Command: dspchstathist 6.1 7 1 AUTO
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
From Network: 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
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
VC Q : 0 Tx OAM : 29608 NonCompliant: 0
Rx EFCI : 0 Rx AIS : 14710
Tx EFCI : 0 Rx FERF: 0 ForeSight Cells
AAL-5 Frames: 0 Adj Fdn: 0
This Command: dspchstats 4.1.50.1
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
This Command: dspchstats 13.1.100
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
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
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
Last Command: dspchstats 2.1.1.1 1
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
|
|