Feedback
Table Of Contents
Position-Dependent and Keyword-Driven Parameters
Identifying Physical and Logical Elements
Troubleshooting Commands
This chapter describes commands that directly or indirectly facilitate troubleshooting. They include commands for viewing and clearing alarms and statistics. The chapter begins descriptions of the CLI, various elements of the AXSM, and the PNNI port identifier.
Position-Dependent and Keyword-Driven Parameters
A command can include parameters that are keyword-driven or position-dependent.
For position-dependent parameters, you must type parameters in the order they appear in the syntax description or on-line help. To create a logical port, for example, the position-dependent syntax is:
addport <ifNum> <bay.line> <guaranteedRate> <maxrate> <sctID> <ifType> [vpi]
For a keyword-driven parameter, a keyword must precede the value. The keyword is preceded by a dash and followed by the parameter (-timeout <secs>, for example). The order you enter keyword-driven parameters does not matter—although any preceding or succeeding, position-dependent parameters must appear as they do in the command syntax description.
In the following syntax example, the command is to delete more than one connection at a time. The mandatory, position-dependent connection identifier consist of a logical port (ifNum) and the VPI and VCI of the first connection to delete. After the connection identifier, the line shows two optional, keyword-driven parameters. These keyword-driven parameters let you enter the number of connections to delete and specify verbose mode:
delcons <ifNum> <vpi> <vci> [-num <num.conns to del>] [-verbose < 1 | 0 >]
Command Entry
When you enter a command with the current version of the product, you must type all intended arguments before you press the Return key or Enter key.
If you press the Return key or Enter key with incorrect parameters or no parameters (if the command requires parameters), a message displays the syntax and parameter ranges. The returned message may also suggest what the problem is. For example, the message may warn of too few parameters. No error messages or warnings appear until you complete the command.
Identifying the AXSM Models
The model number of an AXSM identifies the line speed, line count, and number of bays (see Table 9-1.) Note that the number of lines applies to an individual back card, so the total number of lines supported by the front card equals the highest line number times the number of bays. The OC-48 card AXSM-1-2488 has the lowest number of lines—one. The highest number of lines exist on the AXSM-16-155 and AXSM-16-T3E3—16, as the name indicates.
An MGX 8850 or MGX 8950 node uses the concept of a bay. The bay refers to the upper or lower location of a single-height card. (The switch has a double-height card cage, so a single-height back card necessarily occupies either an upper or lower position.)
The T3/E3, OC-3, and OC-12 versions of the AXSM can have two back cards, one in bay 1 (upper location of the back slot) and the second in bay 2 (lower slot). The MGX-AXSM-1-2488 (OC-48 AXSM) can have a back card in bay 1 only. For further descriptions and illustrations of the card sets, refer to Cisco MGX 8850 Routing Switch Hardware Installation, Release 2.1 or Cisco MGX 8950 Routing Switch Hardware Installation, Release 1.
Identifying Physical and Logical Elements
The Private Network-to-Network Interface (PNNI) control protocol and the AXSM use different formats to identify the same elements. This section describes the format of these elements in the PNNI and AXSM contexts and how they correspond to each other. When you configure or view items on the CLIs of different cards, you often need to specify it in PNNI as well as the AXSM. For example, when you configure a PNNI port on the CLI of the PXM45, you also need to configure a port on the CLI of the AXSM. Furthermore, when you display a connection on the AXSM, you identify that same connection using a different format on the PXM45 CLI. For specific examples of these parallel actions, see the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1.
Note
Apart from the way PNNI and the lower levels of logic identify the same element, the issue of configuration sequence needs explanation. When you configure logical ports—as just one example—you must complete certain tasks on the AXSM CLI before and after related PNNI tasks. This manual describes prerequisites for certain commands, but refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1, for more details of this sequence.
AXSM Format
The AXSM items that you identify for addressing purposes are:
•
•
•
•
A logical port on an AXSM (and its CLI) always uses the label ifNum. For a UNI and NNI interface, a one-to-one correspondence exists between a logical port and a physical line. For virtual trunks, you can configure multiple ports for a line.
The range of logical ports (ifNum) is 1-60 for the AXSM and 1-32 for the AXSM-E regardless of whether the interface type is UNI, NNI, or VNNI (virtual network-to-network interface).
PNNI Format
The PNNI controller requires the following format to identify a physical port:
[shelf.]slot:subslot.port:subport
The PNNI physical port identifier (physical port ID) consists of a series of mandatory elements. Note the period or colon associated with each element inside the square brackets. The elements of the physical port ID are as follows:
•
•
•
•
•
For each physical port number, PNNI also generates a logical port number as an encrypted form of the physical port number. The logical port number appears as an unformatted numerical string. For example, a PNNI physical port ID may have the form 1:1.2:2, so the PNNI logical port number would be 16848898. Where needed, the descriptions in the PNNI command chapter define the need for this logical port number. (This section does not define a PNNI logical port number, nor does it describe the correspondence between an AXSM port and a PNNI logical port number.) For the correspondence between a PNNI physical port and the port identifier on an AXSM, see Table 9-2.
Table 9-2 Mapping PNNI Port ID to AXSM Elements
Shelf
N/A
Slot
Slot
Subslot
Bay (for upper or lower back card)
Port
Line
Subport
Logical interface (or port)
As the table shows, a port from the PNNI side is a line on the AXSM, and a subport from the PNNI side is a logical interface (or logical port) on an AXSM. An example of a PNNI physical port identifier is 1:2.1:1. This portid corresponds to an AXSM, with the following particulars:
Slot 1
Bay 2
Line 1
Logical interface 1 (or logical port 1)
abortofflinediag
Abort Offline Diagnostics
Aborts the currently running offline diagnostics.
Note
Syntax
abortofflinediag <slot>
Syntax Description
Cards on Which This Command Runs
PXM45
Related Commands
cnfdiag, cnfdiagall, dspdiagcnf
Attributes
Caution
Example
abortofflinediag 1addchanloop
Add Channel Loopback—add a loopback to a specific channel in a network test configuration.
The channel loopback tests the integrity of the connection (channel) at the local UNI or across the network. The system returns an error message if the connection is broken or incorrect data arrives at the end of the loopback. The maximum number of connection loopbacks that can exist on an AXSM is 256.
The addchanloop command applies to a network that is not carrying live traffic because the test is very intrusive. The test requires a testing device to generate a cell stream. The parameters for such a stream are the number of cells transmitted through the loop, the cell transfer rate, and so on. (To test connection integrity in a non-destructive way while the connection carries user data, use tstdelay on the ingress or tstconseg on the egress. These commands generate one OAM cell for each command execution.)
A connection can have only one loopback at a time. Therefore, you cannot add a loopback for both directions at the same time. The loopback remains until you delete it by executing delchanloop. To see the presence of connection loopbacks on a per-port basis, use dspchanloop.
The addchanloop command lets you specify the direction of cell flow within the loop (see Figure 9-1):
•
•
The maximum number of loopbacks that can exist on an AXSM is 256.
Figure 9-1 Connection (Channel) Loopbacks on the Ingress and Egress
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
addchanloop <ifNumber> <vpi> <vci> <loopback mode>
Syntax Description
Related Commands
delchanloop, dspchanloop
Tabulates
Example
Add a loopback on the connection with VPI/VCI of 1 50 on logical port 4. No message is returned unless an error occurs in command execution (such as an attempt to add a channel loopback to a connection that already has a loopback).
pop20two.1.AXSM.a > addchanloop 4 1 50Check for the presence of the loopback by displaying all channel loopbacks on port 4.
pop20two.1.AXSM.a > dspchanloop 4Port Type lVPI lVCI rVPI rVCI4 igrLpbk 1 50 0 35addlnloop
Add Line Loop
Specifies a loopback state for a line on the current service module.
Note
Cards on Which This Command Runs
AXSM, AXSM-E
AXSM Syntax
addlnloop <-ds3 | -sonet bay.line> <-lpb loopback type>
Note
AXSM Syntax Description
AXSM-E Syntax
addlnloop < -ds3 | -e3 | -sonet | -ds1 | -e1 bay.line> <-lpb loopback type>
AXSM-E Syntax Description
Related Commands
dellnloop
Attributes
Example
Adding a DS3 line in a loopback state.
MGX8850.1.11.AXSME.a > addlnloop -ds3 1.1 -lpb 2clradjlnalmcnt
Clear Adjacent Card Alarm Count
The clradjlnalmcnt command lets you clear the statistical alarms and alarm counters for the adjacent back card in an automatic protection system (APS) configuration.
Note
Cards on Which This Command Runs
AXSM-E
Syntax
clradjlnalmcnt <bay.line>
Syntax Description
bay.line
Identifies the bay (1 or 2) and the number of the line. The line number can be 1 to the highest numbered line on the back card.
Related Commands
dspadjlnalm, dspadjlnalmcnt
Attributes
Example
On the card in slot 3, clear the alarm count for the card adjacent to bay 1, line 1. Check the alarm status for the same adjacent bay and line.
MGX8850.3.AXSME.a > clradjlnalmcnt 1.1MGX8850.3.AXSME.a > dspadjlnalm 1.1Line Number : 1.1Section Alarm State : ClearLine Alarm State : ClearPath Alarm State : ClearSection Stat Alarm State: ClearLine Stat Alarm State : ClearPath Stat Alarm State : ClearLOCD Alarm State : Clearclrallcnf
Clear All Configurations
Clear all configuration for all the cards in the node. After you enter the command, the system prompts you to confirm the action.
Caution
Cards on Which This Command Runs
PXM45
Syntax
clrallcnf
Related Commands
restoreallcnf, clrcnf
Attributes
Example
Clear all the configuration elements for all the cards in the node.
node1.7.PXM.a > clrallcnfAll SM's config will be deleted, andthe shelf will be reset.Do you want to proceed (Yes/No)?clralmcnt
Clear Alarm Counters
Clear all the alarm counters and statistics on the specified line on the current card. All counters are reset to 0. All statistical alarms that are displayed by dspalms and dspalmcnt are cleared. The system does not display a response unless it detects a syntax error.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
clralmcnt <bay.line>
Syntax Description
bay.line
Identifies the bay (1 or 2) and the number of the line. The line number can be 1 to the highest numbered line on the back card.
Related Commands
dspalmcnt
Attributes
Example
Clear the alarms on line 1 or the lower back card.
node1.1.2.AXSM.a > clralmcnt 2.1
clrbecnt
Clear Bit Error Count
The clrbecnt command lets you clear the APS-related bit error counters for a working line. To see the contents of the error counters, use the dspbecnt command.
Cards on Which This Command Runs
AXSM
Syntax
clrbecnt <working-bay.line>
Syntax Description
working-bay.line
Identifies the bay (1 or 2) and the number of the line. The line number is from 1 to the highest numbered line on the back card. For the range of line numbers on specific AXSM models, see Table 9-1.
Related Commands
addapsln, cnfapsln, delapsln, dspapsln, dspapslns, switchapsln, dspbecnt
Attributes
clrcdcnt
Clear Card Counters
Clears the counters for received and transmitted cells on the current card. See dspcdcnt for examples of the counter contents. The information that clrcdcnt clears and that dspcdcnt displays primarily applies to debugging.
Cards on Which This Command Runs
AXSM
Syntax
clrcdcnt
Syntax Description
This command takes no parameters.
Related Commands
dspcdcnt, dspchancnt
Attributes
clrchancnt
Clear Channel Counters
Clear all counters for ATM cells on a connection (channel). The command applies to an SVC or an SPVC. For a list of displayed counters, see the example of dspchancnt. Once you execute clrchancnt, the previous counter contents are unrecoverable.
Note
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
clrchancnt <ifNum> <vpi> <vci>
Syntax Description
ifNum
The logical port number. The range for AXSM is 1-60. The range for AXSM-E is 1-32.
vpi
The VPI has the range 0-255 for a UNI or 0-4095 for a UNI or VNNI.
vci
The VCI in the range 1-65535.
Related Commands
dspchancnt
Attributes
Example
Clear all the connection counters on AXSM for connection 100.1000 on logical port 3.
node1.1.AXSM.a > clrchancnt 3 100 1000clrchancnts
Clear Channel Counters
Clears the statistics counters on all connections.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
clrchancnts
Syntax Description
Related Commands
dspchancnt, clrchancnt
Attributes
Example
SunnyVale.13.AXSME.a > clrchancnts
clrdiagerr
Clear Diagnostics Errors
Clears all diagnostics error messages that are currently in memory.
Note
Syntax
clrdiagerr <slot>
Syntax Description
Cards on Which This Command Runs
PXM45
Related Commands
dspdiagerr
Attributes
Example
clrdiagerr 7clrdiagstat
Clear Diagnostics Statistics
Clears all the diagnostics statistics currently in memory. The diagnostics statistics program keeps count of how many times diagnostics has run.
Note
Cards on Which This Command Runs
PXM45
Syntax
clrdiagstat <slot>
Syntax Description
Related Commands
dspdiagstat
Attributes
Example
clrdiagstat 7clrerr
Clear Error
Clear all error log files. After you execute clrerr, the information is unrecoverable. The cleared information consists of system-level or internal errors and so applies more to developers and individuals capable of internal troubleshooting. To see the information that clrerr removes, see dsperr.
After you enter clrerr, the system prompts you to confirm that you want to clear all error log files.
Cards on Which This Command Runs
PXM45
Syntax
clrerr <-s1 slot>
Syntax Description
Related Commands
dsperr
Attributes
Example
Clear all error log files on the PXM45.
pinnacle.7.PXM.a > clrerrDo you want to clear error log file (Yes/No)?clrerrhist
Clear Error History—clear the history of errors for a card.
The clrerrhist commands resets the contents of the error history file for a particular card. Although you execute this command on the CLI of the PXM45, you can specify the error history of any slot. For a list of the information fields in an error history file, see the description of dsperrhist.
Cards on Which This Command Runs
PXM45
Syntax
clrerrhist [slot]
Syntax Description
slot
Number of the slot—any slot in the switch. If you do not enter a slot number, the system clears the error history on the current PXM45.
Related Commands
dsperrhist
Attributes
Example
Clear the error history for the current PXM45. The system returns a message indicating whether the operation succeeded.
pop20one.7.PXM.a > clrerrhist 7Log of Errors and Failures for slot# 7 is cleared.clrilmicnt
Clear ILMI Counters
Clears the ILMI statistics for a partition and logical port on a service module.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
clrilmicnt <ifNum> <partId>
Syntax Description
ifNum
The ranges for logical interface (or AXSM port) number are as follows:
•
•
partId
The ranges for partition identifier are as follows:
•
•
Related Commands
dspilmicnt, dspilmi, dspilmis
Attributes
Example
Clear the ILMI statistics for logical interface 1, resource partition 1. Before doing so, confirm the existence of these entities by executing dspparts.
pop20two.1.AXSM.a > dsppartsif part Ctlr egr egr ingr ingr min max min max min maxNum ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn(.0001%)(.0001%)(.0001%)(.0001%)-----------------------------------------------------------------------------1 1 2 10000 10000 10000 10000 10 100 100 1000 0 10pop20two.1.AXSM.a > clrilmicnt 1 1ilmi stats for ifNum 1, partId 1 clearedclrlncnt
Clear Line Counters—clear cell and connection-related counters for a line.
See dsplncnt for descriptions of the counters. The system returns a response only if an error occurs.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
clrlncnt <bay.line>
Syntax Description
bay.line
Identifies the bay (1 or 2) and the number of the line. The range for line can be 1 to the highest numbered line on the back card.
Related Commands
dsplncnt
Attributes
Example
Clear the line counters for line 1 in bay 1 on the current AXSM.
wilco.1.AXSM.a > clrlncnt 1.1clrlog
Clear Log
Use the clrlog command to clear either a specific log file or all log files. The log resumes accumulating event messages after the command executes.
Cards on Which This Command Runs
PXM45
Syntax
clrlog [-log <log>]
Syntax Description
-log
Specifies the type of log file (log) to clear. See dsplog for a list of the types of logs files.
Related Commands
dsplog, dsplogs
Attributes
Example
Clear all event log files on the PXM45 card.
wilco.7.PXM.a > clrlogclrportcnt
Clear Port Counter
Clear counter values on a specific logical port.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
clrportcnt <ifNum>
Syntax Description
Related Commands
clrportcnts, dspportcnt
Attributes
Example
Display the counters for logical interface 1, then clear the counters on port 1. Re-check the port counters.
M8850_NY.1.AXSM.a > dspportcnt 1Cleared at : 10/26/2001 00:00:44Current time : 12/02/2001 21:44:41Elapsed time : 37 day(s) 21:43:21 [hh:mm:ss]Total Running Avg (cps) Peak--------------------------------------------------------------------Arrival CLP0 Ing: 0000000000000007326214 2 21Arrival CLP1 Ing: 0000000000000000000000 0 0Ar CLP0 discard Ing: 0000000000000000000056 0 3Ar CLP1 discard Ing: 0000000000000000000000 0 0Departure CLP0 Ing: 0000000000000007326211 2 21Departure CLP1 Ing: 0000000000000000000000 0 0Arrival CLP0 Egr: 0000000000000007326217 2 21Arrival CLP1 Egr: 0000000000000000000000 0 0Ar CLP0 discard Egr: 0000000000000000000000 0 0Ar CLP1 discard Egr: 0000000000000000000000 0 0Departure CLP0 Egr: 0000000000000007326218 2 21Departure CLP1 Egr: 0000000000000000000000 0 0M8850_NY.1.AXSM.a > clrportcnt 1M8850_NY.1.AXSM.a > dspportcnt 1Cleared at : 12/02/2001 21:44:56Current time : 12/02/2001 21:45:19Elapsed time : 0 day(s) 0:0:22 [hh:mm:ss]Total Running Avg (cps) Peak--------------------------------------------------------------------Arrival CLP0 Ing: 0000000000000000000054 2 2Arrival CLP1 Ing: 0000000000000000000000 0 0Ar CLP0 discard Ing: 0000000000000000000000 0 0Ar CLP1 discard Ing: 0000000000000000000000 0 0Departure CLP0 Ing: 0000000000000000000054 2 2Departure CLP1 Ing: 0000000000000000000000 0 0Arrival CLP0 Egr: 0000000000000000000051 2 2Arrival CLP1 Egr: 0000000000000000000000 0 0Ar CLP0 discard Egr: 0000000000000000000000 0 0Ar CLP1 discard Egr: 0000000000000000000000 0 0Departure CLP0 Egr: 0000000000000000000051 2 2Departure CLP1 Egr: 0000000000000000000000 0 0M8850_NY.1.AXSM.a >clrportcnts
Clear Port Counters
Clear all port counters on the current AXSM. The system does not return a message unless a syntax error occurs (such as a spurious character following the command on the CLI).
Cards on Which This Command Runs
AXSM
Syntax
clrportcnts
Syntax Description
This command takes no parameters.
Related Commands
clrportcnt, dspportcnt
Attributes
Example
Display the counters for logical interface 2, then clear all the port counters on the current AXSM. Again display the counters for logical interface 2.
M8850_NY.1.AXSM.a > dspportcnt 2Cleared at : 10/26/2001 00:00:44Current time : 12/02/2001 21:46:42Elapsed time : 37 day(s) 21:45:22 [hh:mm:ss]Total Running Avg (cps) Peak--------------------------------------------------------------------Arrival CLP0 Ing: 0000000000000000655030 0 0Arrival CLP1 Ing: 0000000000000000000000 0 0Ar CLP0 discard Ing: 0000000000000000000000 0 0Ar CLP1 discard Ing: 0000000000000000000000 0 0Departure CLP0 Ing: 0000000000000000655030 0 0Departure CLP1 Ing: 0000000000000000000000 0 0Arrival CLP0 Egr: 0000000000000000655030 0 0Arrival CLP1 Egr: 0000000000000000000000 0 0Ar CLP0 discard Egr: 0000000000000000000000 0 0Ar CLP1 discard Egr: 0000000000000000000000 0 0Departure CLP0 Egr: 0000000000000000655030 0 0Departure CLP1 Egr: 0000000000000000000000 0 0M8850_NY.1.AXSM.a > clrportcntsM8850_NY.1.AXSM.a > dspportcnt 2Cleared at : 12/02/2001 21:46:57Current time : 12/02/2001 21:47:02Elapsed time : 0 day(s) 0:0:5 [hh:mm:ss]Total Running Avg (cps) Peak--------------------------------------------------------------------Arrival CLP0 Ing: 0000000000000000000000 0 0Arrival CLP1 Ing: 0000000000000000000000 0 0Ar CLP0 discard Ing: 0000000000000000000000 0 0Ar CLP1 discard Ing: 0000000000000000000000 0 0Departure CLP0 Ing: 0000000000000000000000 0 0Departure CLP1 Ing: 0000000000000000000000 0 0Arrival CLP0 Egr: 0000000000000000000000 0 0Arrival CLP1 Egr: 0000000000000000000000 0 0Ar CLP0 discard Egr: 0000000000000000000000 0 0Ar CLP1 discard Egr: 0000000000000000000000 0 0Departure CLP0 Egr: 0000000000000000000000 0 0Departure CLP1 Egr: 0000000000000000000000 0 0M8850_NY.1.AXSM.a >clrxbaralm
Clear Crossbar Alarm—clear the crossbar alarms.
The clrxbaralm command clears the alarms for either a specific switch plane or for all the switch planes on the switching card. In an MGX 8850 node, the slot is the physical slot number of the PXM45. In an MGX 8950 node, the slot is the number of the slot where an XM60 resides. To see the alarms that clrxbaralm clears, use dspdevalms or dspswalms.
Cards on Which This Command Runs
PXM45
Syntax
clrxbaralm <slot> <plane>
clrxbaralm *
Syntax Description
Related Commands
dspdevalms, dspswalms
Attributes
Example
Clear the alarms for switch plane 0 in slot 7. The system returns no messages unless an error exists in the command syntax. To see the results, execute dspdevalms.
pop20two.7.PXM.a > clrxbaralm 7 0clrxbarerrcnt
Clear Crossbar Error Count—clear the counters for crossbar errors.
The clrxbarerrcnt command clears the errors for either a specific switch plane or all the switch planes on the active switching card. In an MGX 8850 node, the slot is the physical slot number of the PXM45. In an MGX 8950 node, the slot is the number of the slot where an XM60 resides. To see the errors that clrxbarerrcnt clears, execute dspdeverrhist.
Cards on Which This Command Runs
PXM45
Syntax
clrxbarerrcnt < * | [ slot plane ]>
Syntax Description
Related Commands
dspdeverrhist, cnfxbarerrthresh, dspxbarerrthresh, dspswalms
Attributes
Example
Clear the errors for switch plane 0 in slot 7. The system returns no messages unless an error exists in the command syntax. To see the results, execute dspdeverrhist.
M8850_NY.7.PXM.a > clrxbarerrcnt 7 0M8850_NY.7.PXM.a >Clear all crossbar alarms on the current PXM45.
M8850_NY.7.PXM.a > clrxbarerrcnt *XBAR errors of slot 7 are clearedcnfalm
Configure Alarm
Configures statistical alarm thresholds for a line. The configurable items for SONET and PLCP are defined in RFC 2258. The configurable items for DS3 and E3 are defined in RFC 2496. The items that constitute a configuration are:
•
•
•
•
•
•
A keyword identifies the alarm criteria. Each keyword identifies the tested layer (line, and so on), the type of threshold (errored seconds, and so on), and the test period of 15 minutes or 24 hours. For example, -lnes15 indicates the number of errored seconds on the line layer during any 15 minute period. See the Syntax Description for a list and definitions of all keywords.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
The required parameters are the line type the line identifier in the format bay.line, and the severity of the alarm (minor or major). All other parameters are optional and must be preceded by the keyword that identifies the type of parameter.
Generic Syntax Description
The generic syntax is.
cnfalm <line type> <bay.line> <alarm severity> <thresholds>
The meaning of the generic syntax appears in the following list. Refer to subsequent lists for the descriptions of alarm severities and thresholds for each line type.
Thresholds for SONET Section
Thresholds for SONET Line
Thresholds for SONET Path
Thresholds for DS3
Thresholds for E3
Thresholds for PLCP
Related Commands
dspalmcnf
Attributes
Example
Configure the following thresholds for triggering a major line-level alarm on line 2 in bay 1:
•
•
•
•
•
•
•
node4.1.AXSM.a > cnfalm -sonetline 1.2 -lnsev 2 -lnes15 60 -lnes24 600 -lnses15 3 -lnses24 7 -lncv15 75 -lncv24 750 -lnuas15 10 -lnuas24 10Check the configuration by executing dspalmcnf for the line number and line type in this example.
node4.1.AXSM.a > dspalmcnf -sonetline 1.2LineNum: 1.2Line Stat Alarm Severity: No Alarm15min Threshold 24hr ThresholdLine ESs : 60 600Line SESs: 3 7Line CVs : 75 750Line UASs: 10 10cnfautolndiag
Configure Auto Line Diagnostics
Enables or disables auto line diagnostic on the card.
Cards on Which This Command Runs
AXSM-E
Syntax
cnfautolndiag <enable | disable>
Syntax Description
Attributes
Example
MGX8850.10.AXSME.a > cnfautolndiag 1cnfbert
Configure Bit Error Rate Test
Configures the bit error rate test patterns for the given line. The new configuration will not take effect if a BERT test is already running on the given line. It will, however, take effect when the currently running BERT test is stopped and started again.
Cards on Which This Command Runs
AXSM-E
Syntax
cnfbert -ln <bay.line> -tp <test pattern> -tpi <transmit pattern inverse>
-rpi <receive pattern inverse> -eir <error insertion rate 1 - 8 >Syntax Description
Related Commands
stopbert, startbert
Attributes
cnfconsegep
Configure Connection Segment Endpoint
The cnfconsegep command lets you configure a segment endpoint for an SVC or SVP on a via node. Its purpose is part of a troubleshooting scheme. After you create an endpoint, you can use the tstdelay command and specify the endpoint created with the cnfconsegep command. The Example section shows how to use tstdelay and conntrace in conjunction with the cnfconsegep command.
You can specify more than one endpoint as long as each one complies with the requirements of the cnfconsegep command, as follows:
•
•
•
In Figure 9-2, an SPVC has endpoints at UNI1 and UNI2. You can use cnfconsegep to configure segment endpoints at NNI2, NNI3, NNI4, and NNI5. You cannot configure segment endpoints at UNI1, UNI2, NNI1, and NNI6. After you configure any of these endpoints, you could verify the electrical integrity by using the tstdelay command from UNI1 or UNI2 to each of NNI2, NNI3, NNI4, or NNI5. After you finish troubleshooting, remove all segment endpoints by using delconsegep for each endpoint.
Figure 9-2 Configurable Endpoints for the cnfconsegep Command
Command(s) on Which Command Executes
PXM45
Syntax
cnfconsegep <portid> <vpi> [vci]
Syntax Description
portid
Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.
vpi
VPI of the connection.
vci
VCI of the connection.
Related Commands
cnfoamsegep, dspoamsegep, delconsegep, dspconsegep
Attributes
Example
This example shows how the cnfconsegep, conntrace, and tstdelay commands can work to show a point of failure. In Figure 9-3, the following are the NNIs:
•
•
•
•
•
•
In this network, the following have also been established:
•
•
•
Figure 9-3 Sample Network for Testing Segment Integrity
Check the connection path by using the conntrace command. As expected, it traverses the direct link (PhysPortId=9:1.2:2), as follows:
tokyo.8.PXM.a > conntrace 9:1.8:8 -vpi 66 -vci 66Result:SUCCESS Reason: N/InterfaceId:9:1.8:8Originating Interface VPI : 66Originating Interface VCI : 66Originating Interface Call Ref : 1NodeId EgressPort VPI VCI CallRef56:160:47.00918100000000107b65f448.00107b65f448.01 17373186 0 35 1 PhysPortId=9:1.2:256:160:47.00918100000000309409f3bb.00309409f3bb.01 0Terminating Interface VPI : 66Terminating Interface VCI : 66Terminating Interface Call Ref : 1To continue this example, the following tasks are performed:
1.
2.
3.
tokyo.8.PXM.a > dnpnport 9:1.2:2tokyo.8.PXM.a > conntrace 9:1.8:8 -vpi 66 -vci 66Result:SUCCESS Reason: N/AInterfaceId:9:1.8:8Originating Interface VPI : 66Originating Interface VCI : 66Originating Interface Call Ref : 2NodeId EgressPort VPI VCI CallRef56:160:47.00918100000000107b65f448.00107b65f448.01 17373185 0 36 2 PhysPortId=9:1.1:156:160:47.00918100000000309409f3b8.00309409f3b8.01 17373187 0 41 1 PhysPortId=9:1.3:356:160:47.00918100000000309409f3bb.00309409f3bb.01 0Terminating Interface VPI : 66Terminating Interface VCI : 66Terminating Interface Call Ref : 2tokyo.8.PXM.a > uppnport 9:1.2:2Configure a connection segment endpoint by using the following values on node "fiorano":
•
•
fiorano.7.PXM.a > cnfconsegep 9:1.1:1 0 36PortId: 0.9:1.1:1 Vpi: 0 Vci: 36The connection is configured as a segment end point.
cnfdiag
Configure Diagnostics
Enables the online or offline diagnostics. The cnfdiag command also configures the time settings for the start time and coverage for running the offline diagnostics. When you enter cnfdiag with no parameters, it displays the current configuration and status of the diagnostics.
The cnfdiagall command is the same as cnfdiag except that it configures all slots on the card at once.
Note
The Purpose of the MGX 8850 Diagnostics
MGX 8850 diagnostics were implemented to test and validate the communication paths on the controller (PXM45) and the service modules (AXSM) to ensure reliability before and during operation. The diagnostics are always scheduled from the PXM45 controller card whether or not they run on the PXM45 card or the AXSM card.
For backward compatibility, the MGX 8850 Release 2.1 switch has two buses on its backplane:
•
•
Because of the difference in bus speeds on the backplane, the Reliability Availability Serviceability (RAS) requirements demand that diagnostics be run periodically on the communications paths.
Consequently, diagnostics should be running periodically on both active and standby cards, but especially on standby cards. It is important that standby cards are tested using diagnostics periodically and frequently so that when an active card fails, the standby card has been tested and is ready to assume the active card state immediately.
Online Diagnostics
Online diagnostics are nondestructive tests (that do not interfere with active traffic) and run on either active and standby cards. The MGX 8850 switch supports seven online diagnostics tests. Three tests run on the PXM45 card, and four tests run on the AXSM card.
PXM45 Online Diagnostics
Active State
When you enable online diagnostics on an active PXM45 card, the following test runs:
•
Standby State
When you enable online diagnostics on a standby PXM45 card, the following tests run:
•
•
AXSM Online Diagnostics
Active State
When you enable online diagnostics on an active AXSM card, the following test runs:
•
Standby State
When you enable online diagnostics on a standby AXSM card, the following tests run:
•
•
•
Offline Diagnostics
Offline diagnostics are destructive tests (that interfere with active traffic) and therefore run only on standby cards.
Offline diagnostics must be scheduled using the offline start (offStart) and offline day-of-week (offDow) parameters. The coverage (offCover) parameter specifies the length of time that the offline diagnostics will run.
Note
When offline diagnostics is enable and scheduled, numerous tests may be run depending on the implementation. The possible tests that may be run on the PXM45 and AXSM cards are listed in the following sections.
PXM45 Offline Diagnostics
1.
•
•
•
•
2.
•
•
•
•
•
•
3.
•
•
•
•
•
•
4.
•
5.
•
•
•
AXSM Offline Diagnostics
1.
2.
3.
4.
5.
6.
7.
8.
Syntax
cnfdiag <slot> <onEnb> <offEnb> [<offCover> <offStart> <offDow>]
Syntax Description
Cards on Which This Command Runs
PXM45
Related Commands
cnfdiagall, dspdiagcnf
Attributes
Example
cnfdiag 7 enable disable light 22:30 -M-W-F-cnfdiagall
Configure Diagnostics All
This command enables and configures online or offline diagnostics for all card slots. (This command is the same as cnfdiag except that it effects all slots instead of just one.)
When you enter this command with no parameters, it displays the current configuration and status of the diagnostics.
Note
Note
Cards on Which This Command Runs
PXM45
Syntax
cnfdiagall <onEnb> <offEnb> [<offCover> <offStart> <offDow>]
Syntax Description
Related Commands
cnfdiag, dspdiagcnf
Attributes
Example
cnfdiagall enable disable light 22:30 -M-W-F-cnfpnportloscallrel
Configure PNNI Port Loss of Signal Call Release
The cnfpnportloscallrel command lets you shut off the standard delay for rerouting calls on a port when the system detects loss of signal (LOS) on a port.
When the system detects LOS on an NNI link, the switch does not immediately tear down the calls on the link—in case the break is momentary. By default, the system waits for the SSCOP "no-response" and T309 timers to time out before it releases calls on the broken link. The default values for these timers are 30 seconds and 10 seconds, respectively. The system-level assumption (and therefore the default for cnfpnportloscallrel) is to retain all the calls for a temporary loss of connectivity, but this can also have the effect of delaying the rerouting of connections. The cnfpnportloscallrel command lets you direct the system to reroute calls without delay on a particular port.
Cards on Which This Command Runs
PXM45
Syntax
cnfpnportloscallrel <portid> <yes | no>
Syntax Description
portid
Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.
yes | no
Specifies whether immediate call release is enabled upon LOS. To enable this feature—to remove the standard reroute delay—type "yes."
Default: no
Related Commands
dsppnportloscallrel
Attributes
Example
Enable call release upon LOS for port 3:1.1:1, then confirm its status.
8850_NY.8.PXM.a > cnfpnportloscallrel 3:1.1:1 yes
8850_NY.8.PXM.a > dsppnportloscallrel 3:1.1:1
Call release on Los :enabledcnfxbaradmin
Configure Crossbar Administration—turn a switch plane on or off.
The cnfxbaradmin command lets you turn off the switch planes on a switch card. The purpose for turning off switch planes is a graceful removal of the standby PXM45 in an MGX 8850 switch or an XM60 in an MGX 8950 switch. The circumstance for removing the card is a bad switch plane.
Graceful removal reduces lost traffic due to card removal. Removing a switching card normally causes very little cell loss, and using the cnfxbaradmin command further reduces the loss. The actual impact of the command is relatively small. (For most plane-centric failures, the switching ASIC can continue to switch cells but at a lower rate.)
Note
Cards on Which This Command Runs
PXM45
Syntax
cnfxbaradmin <xbarSlot> <adminStatus>
Syntax Description
Related Commands
cnfxbarerrthresh, cnfxbarmgmt, dspxbar, dspdevalms, dspdeverrhist, dspxbarstatus
Attributes
Examples
Do the following:
1.
2.
3.
4.
M8850_NY.7.PXM.a > cnfxbaradmin 8 offShut-down of switch could be service affecting!cnfxbaradmin: Do you want to proceed (Yes/No)? yM8850_NY.7.PXM.a > dspxbarstatus 8 0M8850_NY System Rev: 02.01 Nov. 28, 2001 15:42:22 PSTMGX8850 Node Alarm: CRITICALSwitch CD No: 8 Switch ASIC No: 0Operational Status Bitmap : 0x0Error Status Bitmap:Slot 1: 0x0Slot 2: 0x0Slot 3: 0x0Slot 4: 0x0Slot 5: 0x0Slot 6: 0x0Slot 7: 0x0Slot 8: 0x0Slot 9: 0x0Slot 10: 0x0Slot 11: 0x0Slot 12: 0x0Slot 13: 0x0Slot 14: 0x0Slot 15: 0x0Slot 16: 0x0Misc Error Bitmap: 0x0Fabric Available Bandwidth: 3000 MbpsSwitch Card Available Bandwidth: 0 MbpsHighest Bandwidth Needed: 2488 MbpsM8850_NY.7.PXM.a > cnfxbaradmin 8 onM8850_NY.7.PXM.a > dspxbarstatus 8 0M8850_NY System Rev: 02.01 Nov. 28, 2001 15:42:46 PSTMGX8850 Node Alarm: CRITICALSwitch CD No: 8 Switch ASIC No: 0Operational Status Bitmap : 0x3FFFError Status Bitmap:Slot 1: 0x0Slot 2: 0x0Slot 3: 0x0Slot 4: 0x0Slot 5: 0x0Slot 6: 0x0Slot 7: 0x0Slot 8: 0x0Slot 9: 0x0Slot 10: 0x0Slot 11: 0x0Slot 12: 0x0Slot 13: 0x0Slot 14: 0x0Slot 15: 0x0Slot 16: 0x0Misc Error Bitmap: 0x0Fabric Available Bandwidth: 6000 MbpsSwitch Card Available Bandwidth: 3000 MbpsHighest Bandwidth Needed: 2488 MbpsM8850_NY.7.PXM.a >Do the following on an MGX 8950 switch:
1.
2.
3.
4.
M8950_DC.7.PXM.a > cnfxbaradmin 9 offShut-down of switch could be service affecting!cnfxbaradmin: Do you want to proceed (Yes/No)? yM8950_DC.7.PXM.a > dspxbarstatus 9 0M8950_DC System Rev: 02.01 Nov. 28, 2001 14:45:35 PSTMGX8950 (JBP-2) Node Alarm: MAJORSwitch CD No: 9 Switch ASIC No: 0Operational Status Bitmap : 0x0Error Status Bitmap:Slot 1: 0x0Slot 2: 0x0Slot 3: 0x0Slot 4: 0x0Slot 5: 0x0Slot 6: 0x0Slot 7: 0x0Slot 8: 0x0Slot 9: 0x0Slot 10: 0x0Slot 11: 0x0Slot 12: 0x0Slot 13: 0x0Slot 14: 0x0Slot 15: 0x0Slot 16: 0x0Misc Error Bitmap: 0x0Fabric Available Bandwidth: 5000 MbpsSwitch Card Available Bandwidth: 0 MbpsHighest Bandwidth Needed: 2488 MbpsM8950_DC.7.PXM.a > cnfxbaradmin 9 onM8950_DC.7.PXM.a > dspxbarstatus 9 0M8950_DC System Rev: 02.01 Nov. 28, 2001 14:58:47 PSTMGX8950 (JBP-2) Node Alarm: MAJORSwitch CD No: 9 Switch ASIC No: 0Operational Status Bitmap : 0xFCFFError Status Bitmap:Slot 1: 0x0Slot 2: 0x0Slot 3: 0x0Slot 4: 0x0Slot 5: 0x0Slot 6: 0x0Slot 7: 0x0Slot 8: 0x0Slot 9: 0x0Slot 10: 0x0Slot 11: 0x0Slot 12: 0x0Slot 13: 0x0Slot 14: 0x0Slot 15: 0x0Slot 16: 0x0Misc Error Bitmap: 0x0Fabric Available Bandwidth: 7000 MbpsSwitch Card Available Bandwidth: 2000 MbpsHighest Bandwidth Needed: 2488 Mbpscnfxbarerrthresh
Configure Crossbar Error Threshold—specify a threshold for a particular crossbar alarm severity.
The Syntax Description contains a list of possible errors. A crossbar error threshold consists of:
•
•
•
Usage Guidelines for cnfxbarerrthresh
Note the following details about this command:
•
•
Note
Cards on Which This Command Runs
PXM45Syntax
cnfxbarerrthresh <errtype> <threshtime> <severity> <clrcount> <almcount>
Syntax Description
Related Commands
dspxbarerrthresh
Attributes
Example
For Loss of Sync, set the clear count for critical alarms to 200.
pop20two.7.PXM.a > cnfxbarerrthresh 1 2000 2 200 301In the sequence of command and arguments, the only value that differs from the existing threshold is the clear count of 200. If the operation is successful, the system displays the error threshold for the type of error you specified—Loss of Sync in this example.
pop20two System Rev: 02.01 Dec. 05, 2000 02:29:17 GMTMGX8850 Node Alarm: MAJORCROSSBAR ERROR CONFIGURATIONThresh -- MINOR -- -- MAJOR -- -- CRITICAL --Device Error Time Clear Alarm Clear Alarm Clear AlarmType (msec) Count Count Count Count Count Count-------------------- ------ ----- ----- ----- ----- ----- -----LossOfSync 2000 0 3 4 15 200 301cnfxbarmgmt
Configure Crossbar Management—configure load sharing.
The purpose of load sharing is to a provide backup for the switch planes on the active PXM45. The backup is provided by the switch planes on the standby PXM45. The hardware on which cnfxbarmgmt focuses is a redundant pair of PXM45s in an MGX 8850 switch. (In an MGX 8950 switch, load sharing is always enabled.) If a switch plane fails on the active PXM45, a switch plane on the standby PXM45 takes over the switching tasks of the failed ASIC.
Note
Regardless of whether the node has redundant PXM45s or a load-sharing configuration, you can still investigate alarms and errors through a hierarchy of shelf-management and crossbar-related commands:
1.
2.
3.
4.
Cards on Which This Command Runs
PXM45Syntax
cnfxbarmgmt <loadSharing> <autoShutdown> <planeAlarmThresh>
Syntax Description
Related Commands
dspxbarmgmt, dspxbarerrthresh, dspdeverrhist
Attributes
Example
Specify an error threshold of five links to declare a bad switch plane and enable auto-shutdown. The system returns a message only if an error occurs. Use dspxbarmgmt to check the new configuration.
pop20two.7.PXM.a > cnfxbarmgmt 1 1 5pop20two.7.PXM.a > dspxbarmgmtpop20two System Rev: 02.01 Dec. 06, 2000 00:44:20 GMTMGX8850 Node Alarm: MAJORLoad Sharing: EnableAuto Shutdown: EnablePlane Alarm Threshold: 5conntrace
Connection Trace
The conntrace command lets you start a trace on an established connection and display the result. The required parameter is the PNNI physical port identifier. To identify the connection, you can specify the call reference or the VPI and VCI.
Cards on Which This Command Runs
PXM45
Syntax
conntrace <portid> [-callRef callRef [-endptRef endptRef]] [-vpi vpi [-vci vci]]
Syntax Description
portid
Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.
-callRef
You can provide a call reference by itself to trace the connection. A call reference by itself identifies a point-to-point call.
Range for callRef: 1-16777215
-endptRef
If you provide a call reference, you can also provide an endpoint reference for a point-to-multipoint (P2MP) call.
Note
Range for endptRef:1-32767
-vpi
The VPI has a range that depends on whether the connection is a virtual path connection or a virtual channel connection, as follows:
•
•
-vci
The VCI has a range of 0-65355.
Related Commands
pathtraceport, pathracenode, pathtraceie
Attributes
Example
Do a connection trace on by using a known VPI and VCI. The port ID is 9:1.8:8, and the VPI and VCI are both 66.
tokyo.8.PXM.a > conntrace 9:1.8:8 -vpi 66 -vci 66Result:SUCCESS Reason: N/InterfaceId:9:1.8:8Originating Interface VPI : 66Originating Interface VCI : 66Originating Interface Call Ref : 1NodeId EgressPort VPI VCI CallRef56:160:47.00918100000000107b65f448.00107b65f448.01 17373186 0 35 1 PhysPortId=9:1.2:256:160:47.00918100000000309409f3bb.00309409f3bb.01 0Terminating Interface VPI : 66Terminating Interface VCI : 66Terminating Interface Call Ref : 1
copycons
Copy Connections
The purpose of the copycons command is debugging. It copies one or more endpoints from a specified endpoint.
This debugging command works by incrementing the VCI for a VCC endpoints and the VPI for a VPC endpoints.
The following steps are recommended when using this command:
1.
2.
3.
Caution
Improper use of this command can result in dangling (unpaired) endpoints in the network.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
copycons <source> <destn> [-rem <remote Conn Id>] [-num <num. conns to add>]
[-verbose <1 | 0>]Syntax Description
Related Commands
addcon, delcon
Attributes
Example
MGX8850.1.11.AXSME.a > copycons 3.10.50 3.10.60 -num 10core
Core Memory Dump
The core command applies to core memory dumps that can occur when a card is reset. (Whether a specific reset type leads to a core dump is configurable.) You can copy zipped files to a workstation.
The core task has the following functional areas (further described in the Syntax Description sections):
•
–
–
–
–
•
•
Certain functions are complex enough to warrant a detailed description. These functions are noted in the Syntax Description tables and have details in the Usage Guidelines section.
The processor card and AXSM modules support a different number of command parameters. The parameters are described by card type in subsequent sections. Furthermore, the processing of the captured memory contents differs for the processor card and the service modules, as follows:
•
specified_name.zip
•
core_slotslot_num.zip, where slot_num is the number of the slot where the AXSM resides
The node logs messages for a service module core dump. The log shows when the core dump started, finished, and aborted as well as any exceptions. To see these logs, use dsplog -mod CRDMP.
Ftp files to a work station. You can send files to the Cisco TAC to be unzipped and debugged.
Cards on Which This Command Runs
PXM45, AXSM, AXSM-E
Syntax
core (optional parameters—see Syntax Description for AXSM or PXM45)
Syntax Description (AXSMs)
The first entry in the following list is the core command itself because it produces a unique output when no parameters follow it. The list entries after the core command are the parameters. Each of these parameters must follow the core command even though each parameter description does not show core.
core
The core command without parameters indicates whether core dumps are enabled for the current slot and that files reside on the C drive.
?
The core command with a question mark lists the optional parameters.
mask
Enter core mask to display the following:
•
•
•
The default mask is 0x262ee. To modify the mask, use mask hex-mask. See also the section, "Usage Guidelines," for the core mask details.
mask default
Enter mask default to return the mask to the default value (0x262ee).
mask hex-mask
Type core mask followed by a hexadecimal value to modify the mask. You can specify a mask regardless of whether core dumping is enabled for the card. See the section, "Usage Guidelines,," for the core mask details. See also Examples.
enable
Enter core enable to enable automatic core dumping for the current slot.
disable
Enter core disable to disable automatic core dumping for the current slot.
Syntax Description (PXM45)
The first entry in the following list is the core command itself because it produces a unique output when no parameters follow it. The list entries after the core command are the parameters. Each of these parameters must follow the core command even though each parameter description does not show core.
core
The core command without parameters shows the priority of core dumping at the switch level, whether images exist and the number of the image (0 or 1), the reason for the reset that caused the core dump, and a time stamp.
?
The core command followed by a question mark lists the optional parameters.
mask
Enter core mask to display the following:
•
•
•
The default mask is 0x262ee. To modify the mask, use mask hex-mask. For details, see the paragraphs on the core mask in the section, "Usage Guidelines."
mask default
Enter mask default to return the mask to the default value (0x262ee).
mask hex-mask
Type core mask followed by a hex value to modify the mask. You can specify a mask whether or not core dumping is enabled on the card. For details, see the paragraphs on core masks in the section, "Usage Guidelines." See also Examples.
enable
Type core enable to enable automatic core dumping for the current slot.
disable
Type core disable to disable automatic core dumping for the current slot.
hot-dump
The hot dump option directs the system to save memory but not to reset the card. The memory-read occurs during normal operation, so RAM is frequently changing, and the accuracy is not high. This parameter targets only the PXM. The hot dump is the only dump during which traffic continues to flow.
dump-and-reset
This parameter causes a core dump then a reset (the reverse of the usual order). It applies to only the PXM. This parameter is infrequently used. It could apply to a situation where you must reset the PXM and want the memory contents before the reset. The same results result from a hot dump followed by a manual reset.
save bin-num file-name
To save a raw data image residing in the unmarked part of the disk to a zip file, type save followed by the bin number (0 or 1) then the file name in the format filename.zip. For example: save 0 new_york010202.zip
clear
Enter core clear to delete the raw core data. These files are the PXM core dumps in the unmarked region of disk. The service module files remain on the C drive.
red-policy
Enter core red-policy to show the core dump policy for non-redundant service modules (not PXMs). See redundancy policy in "Usage Guidelines."
red-policy enable
At the switch-level, enable core dumps for non-redundant service modules.
red-policy disable
At the switch-level, disable core dumps for non-redundant service modules.
dump-status
This parameter lets you see the progress of core dumps.
abort-dump
To abort a core dump in progress, core abort-dump followed by the slot number. See the abort paragraph in the section, "Usage Guidelines."
time-out
Display the maximum number of seconds a core dump can take before the system terminates the process.
time-out
timeInSecsYou can specify the number of seconds allowed for a core dump to complete.
Range: 240-7200 seconds
Default: 360 seconds
priority
Enter core priority to see if core dumping is a high-priority task or a low-priority task. The default is high priority. For some purposes, you may not want core dumping to be a high-priority task. Priority is node-level and not configurable by slot. See the section, "Usage Guidelines," for more information on the priority.
priority high
Enter core priority high to make core-dumping a high-priority task at the node level. High priority is the default for the switch to ensure that no cores are lost, so this command is necessary only if the priority is low and needs to change.
priority low
Enter core priority low to make core-dumping a low-priority at the node level.
Usage Guidelines
A description of usage considerations for the more complex parameters follows.
Disabling Core Dumps, Timeout, and Priority
You may want to disable core dumps for a slot due to the time to write core memory to disk. For example:
•
•
As the processor gets busier, core dumps require more time. In addition to disabling core dumps for a slot, you can set the priority of core dumps to low at the switch level or specify a timeout period for core dumps. See priority and timeout explanations in the section, "Syntax Description (PXM45)."
Specifying the Core Mask
The core mask is the sum of the hexadecimal numbers associated with reset reasons that are enabled to trigger a core dump. Most reasons for a card reset can be enabled to trigger a core dump. (The reasons that cannot trigger a core dump are indicated as such.) Each reset reason has an associated hexadecimal number—regardless of whether it can trigger a core dump. If the reset reason is ON, the associated hex number is an element of the mask.
To create a core mask, add the hexadecimal values for the reset reasons that you want to be in the mask. The list that follows shows the reset reasons and the default enables. For a simplified example, enter core mask c to specify that only a resource overflow or watchdog timeout can cause a core dump for the slot where you enter this command. The default mask as displayed by core mask follows:
OFF 00001 not used (cannot be turned ON)
ON 00002 DRAM Parity Error
ON 00004 WatchDog Timeout Reset
ON 00008 Resource Overflow
OFF 00010 Clear All Configuration (cannot be turned ON)
ON 00020 Missing Task
ON 00040 Reset because of PXM Low Voltage
ON 00080 Reset By Event Log Task
OFF 00100 Reset from Shell—a reset issued from a low-level debugging shell used by Cisco engineers
ON 00200 Unknown
OFF 00400 Reset from PXM—of the reasons PXM causes reset, some (e.g., resetcd) can cause a dump
OFF 00800 Reset System (cannot be turned ON)—the system reset triggered by the resetsys command
OFF 01000 Switch Core Card—the reset caused by the switchcc command (core card switch-over)
ON 02000 Secondary Cache Error
ON 04000 Software Error Reset
OFF 08000 S/W reset due to upgrade (cannot be turned ON)
OFF 10000 Restore All Configuration (cannot be turned ON)
ON 20000 Device Driver Error
If you add all the reset reasons that are ON in the default mask, the sum is the hexadecimal number 262ee. A reason that cannot trigger a core dump is indicated in the preceding list with "cannot be turned ON." A reset reason that cannot trigger a core dump removes pertinent information from memory.
Redundancy Policy
After a redundant pair of service modules switches over, the former active card is rebooting, so a core dump is possible. Because the activated card is carrying the traffic, the time to write RAM contents from the reset card to disk normally is not an issue. For non-redundant service modules, however, the dump time may be a concern. The parameters for redundancy policy let you determine whether core dumps can occur in non-redundant service modules.
The redundancy policy is a node-level configuration. You can override the configuration on a per slot basis by enabling or disabling core dumps at the CLI of the individual card.
Aborting a Core Dump
In some circumstances, you would want to abort a service module core dump. Example situations follow:
•
•
Related Commands
ftp, ll, cd, dsplog (use the dsplog command with the following parameter: -mod CRDMP)
Attributes
Examples (PXM45)
First, check the current status for PXM files. Next, clear the raw core dumps then re-check the status.
M8850_LA.8.PXM.a > coreSaved PXM core images:Bin Reset Reason Type Slot Dump Time--------------------------------------------------------------------------------0 Manual dump POPEYE 2 8 WED JAN 30 19:28:13 20021 Software Error Reset POPEYE 2 8 TUE FEB 27 17:48:24 2001The current core bin is 1.Automatic core dumping is ** disabled ** for this slot.Current Task Priority for CoreDump is [High].Saved SM core images can be found in C:/.M8850_LA.8.PXM.a > core clearAll the raw core dump images will be erased.core: Do you want to proceed (Yes/No)? yCheck the mask and observe it has returned to the default.
M8850_LA.8.PXM.a > coreSaved PXM core images:Bin Reset Reason Type Slot Dump Time--------------------------------------------------------------------------------The current core bin is 0.Automatic core dumping is ** disabled ** for this slot.Current Task Priority for CoreDump is [High].Saved SM core images can be found in C:/.M8850_LA.8.PXM.a >Get a snapshot of core memory on the PXM45. The dots crossing the screen shows the progress of the dump. Check the status by entering core without parameters. The display shows that a snapshot occurred ("Manual dump"). Save the dump to the file called test_1.zip and confirm that it resides on the C drive.
M8850_LA.8.PXM.a > core hot-dumpcore: Do you want to proceed (Yes/No)? yDumping PXM Core Image[0]:................................................................................Done.M8850_LA.8.PXM.a > coreSaved PXM core images:Bin Reset Reason Type Slot Dump Time--------------------------------------------------------------------------------0 Manual dump POPEYE 2 8 WED JAN 30 19:28:13 20021 Software Error Reset POPEYE 2 8 TUE FEB 27 17:48:24 2001The current core bin is 1.Automatic core dumping is ** disabled ** for this slot.Current Task Priority for CoreDump is [High].Saved SM core images can be found in C:/.Enter ll C: to check for the test_1.zip file. The example display is truncated to show just the zip file.
M8850_LA.8.PXM.a > ll C:size date time name-------- ------ ------ --------19517299 JAN-31-2002 22:42:22 test_1.zipIn the file system :total space : 819200 K bytesfree space : 689221 K bytesThis example shows three actions in relation to the mask: showing the current mask, specifying a mask, and restoring the default mask. Show the current core mask for the PXM45 by entering core mask.
M8850_LA.8.PXM.a > core maskAutomatic core dumping is ** disabled ** for this slot.The current core mask is 0x64e0.OFF 00001 not used (can't be turned ON)OFF 00002 DRAM Parity ErrorOFF 00004 WatchDog Timeout ResetOFF 00008 Resource OverflowOFF 00010 Clear All Configuration (can't be turned ON)ON 00020 Missing TaskON 00040 Reset because of PXM Low VoltageON 00080 Reset By Event Log TaskOFF 00100 Reset from ShellOFF 00200 UnknownON 00400 Reset from PXMOFF 00800 Reset System (can't be turned ON)OFF 01000 Switch Core CardON 02000 Secondary Cache ErrorON 04000 Software Error ResetOFF 08000 S/W reset due to upgrade (can't be turned ON)OFF 10000 Restore All Configuration (can't be turned ON)OFF 20000 Device Driver ErrorSet the mask to 0xc and observe the results in the display. Most reasons are off (some are always off).
M8850_LA.8.PXM.a > core mask cAutomatic core dumping is ** disabled ** for this slot.The current core mask is 0xc.OFF 00001 not used (can't be turned ON)OFF 00002 DRAM Parity ErrorON 00004 WatchDog Timeout ResetON 00008 Resource OverflowOFF 00010 Clear All Configuration (can't be turned ON)OFF 00020 Missing TaskOFF 00040 Reset because of PXM Low VoltageOFF 00080 Reset By Event Log TaskOFF 00100 Reset from ShellOFF 00200 UnknownOFF 00400 Reset from PXMOFF 00800 Reset System (can't be turned ON)OFF 01000 Switch Core CardOFF 02000 Secondary Cache ErrorOFF 04000 Software Error ResetOFF 08000 S/W reset due to upgrade (can't be turned ON)OFF 10000 Restore All Configuration (can't be turned ON)OFF 20000 Device Driver ErrorReset the mask to the default by entering core mask default. Note that core dumping remains disabled regardless of the mask.M8850_LA.8.PXM.a > core mask defaultAutomatic core dumping is ** disabled ** for this slot.The current core mask is 0x262ee.OFF 00001 not used (can't be turned ON)ON 00002 DRAM Parity ErrorON 00004 WatchDog Timeout ResetON 00008 Resource OverflowOFF 00010 Clear All Configuration (can't be turned ON)ON 00020 Missing TaskON 00040 Reset because of PXM Low VoltageON 00080 Reset By Event Log TaskOFF 00100 Reset from ShellON 00200 UnknownOFF 00400 Reset from PXMOFF 00800 Reset System (can't be turned ON)OFF 01000 Switch Core CardON 02000 Secondary Cache ErrorON 04000 Software Error ResetOFF 08000 S/W reset due to upgrade (can't be turned ON)OFF 10000 Restore All Configuration (can't be turned ON)ON 20000 Device Driver ErrorM8850_LA.8.PXM.a >Display the redundancy policy.
M8850_LA.8.PXM.a > core red-policyNon-redundant SMs are allowed to dump core.Examples (AXSM)
Check the core mask on the current AXSM.
M8850_LA.1.AXSM.s > core maskAutomatic core dumping is enabled for this slot.The current core mask is 0x262ee.OFF 00001 not used (can't be turned ON)ON 00002 DRAM Parity ErrorON 00004 WatchDog Timeout ResetON 00008 Resource OverflowOFF 00010 Clear All Configuration (can't be turned ON)ON 00020 Missing TaskON 00040 Reset because of PXM Low VoltageON 00080 Reset By Event Log TaskOFF 00100 Reset from ShellON 00200 UnknownOFF 00400 Reset from PXMOFF 00800 Reset System (can't be turned ON)OFF 01000 Switch Core CardON 02000 Secondary Cache ErrorON 04000 Software Error ResetOFF 08000 S/W reset due to upgrade (can't be turned ON)OFF 10000 Restore All Configuration (can't be turned ON)ON 20000 Device Driver ErrorSet the core mask to 0xc and note the result in the display.
M8850_LA.1.AXSM.s > core mask cAutomatic core dumping is enabled for this slot.The current core mask is 0xc.OFF 00001 not used (can't be turned ON)OFF 00002 DRAM Parity ErrorON 00004 WatchDog Timeout ResetON 00008 Resource OverflowOFF 00010 Clear All Configuration (can't be turned ON)OFF 00020 Missing TaskOFF 00040 Reset because of PXM Low VoltageOFF 00080 Reset By Event Log TaskOFF 00100 Reset from ShellOFF 00200 UnknownOFF 00400 Reset from PXMOFF 00800 Reset System (can't be turned ON)OFF 01000 Switch Core CardOFF 02000 Secondary Cache ErrorOFF 04000 Software Error ResetOFF 08000 S/W reset due to upgrade (can't be turned ON)OFF 10000 Restore All Configuration (can't be turned ON)OFF 20000 Device Driver ErrorDetermine if core dump is enabled for the current slot.
M8850_NY.1.AXSM.s > coreAutomatic core dumping is enabled for this slot.Saved core images are on PXM's hard disk (C:/).M8850_NY.1.AXSM.s >dclk
Display Clock Measured by System Clock Test
Display the Digital to Analog Converter (DAC) value and the deviation, in parts-per-million, of the output frequency of the current clock source. This is the nominal frequency value for the local oscillator on the PXM45 UIS3 card.
The local oscillator of the UIS3 is an Over-Controlled Crystal Oscillator (OCXO) with a nominal frequency of 19.44Mhz. The control voltage applied to the OCXO by the hardware circuitry on the board adjusts the output frequency range of the clock between +/- 7 PPM (136Hz) to +/- 14PPM (272Hz).
The DAC value is used to convert the digital voltage value, from the DSP FPGA, to the analog voltage, which controls the OCXO. The range of the input DAC value is from 0x0000 to 0xffff with a nominal value of 0x8000.
The dclk output displays the DAC value field, which is the difference between the current measured DAC value and the nominal DAC value of 0x8000, and the PPM values for the last 100 current clock samples that have been taken at the rate of one every second.
Cards on Which This Command Runs
PXM45
Syntax
dclk
Syntax Description
Related Commands
None
Attributes
Example
M8850_NY.7.PXM.a > dclkSample DAC Dev ppm.1 -900 -0.192 -915 -0.193 -915 -0.194 -915 -0.195 -900 -0.196 -900 -0.197 -916 -0.198 -916 -0.199 -916 -0.1910 -916 -0.1911 -916 -0.1912 -916 -0.1913 -900 -0.1914 -900 -0.1915 -899 -0.1916 -899 -0.1917 -899 -0.1918 -900 -0.1919 -900 -0.1920 -900 -0.1921 -899 -0.1922 -899 -0.19Type <CR> to continue, Q<CR> to stop:23 -900 -0.1924 -916 -0.1925 -899 -0.1926 -915 -0.1927 -915 -0.1928 -916 -0.1929 -900 -0.1930 -916 -0.1931 -916 -0.1932 -915 -0.1933 -915 -0.1934 -916 -0.1935 -916 -0.1936 -916 -0.1937 -900 -0.1938 -899 -0.1939 -900 -0.1940 -900 -0.1941 -900 -0.1942 -900 -0.1943 -915 -0.1944 -915 -0.1945 -916 -0.19Type <CR> to continue, Q<CR> to stop:46 -916 -0.1947 -915 -0.1948 -916 -0.19dbgcon
Debug Connection—enables or disables logging of SPVC or SPVP-related errors.
Enable or disable the SPVC log at the switch level or for an individual SPVC or SPVP. To see whether the SPVC log is enabled, use the dspcons-dbg command.
Cards on Which This Command Runs
PXM45
Syntax
dbgcon <enable | disable> [-port <portid> -vpi <vpi> -vci <vci>]
Syntax Description
Related Commands
dspcons-dbg
Attributes
Example
Enable the SPVC log. Specify PNNI port 9:1.8:8 and a VPI/VCI of 100/100.
ja8850.8.PXM.a > dbgcon enable -port 9:1.8:8 -vpi 100 -vci 100Enable the log for the whole switch then check the status by using the dspcons-dbg command.
M8850_NY.7.PXM.a > dbgcon enableWARNING: This could significantly increase CPUload and severely degrade performance.Do you want to proceed (Yes/No) ? yM8850_NY.7.PXM.a > dspcons-dbgGlobal SPVC/SPVP Event Log Status: EnableM8850_NY.7.PXM.a >delchanloop
Delete Channel Loopback
Delete a loopback from a connection (channel). For an understanding of the purpose of channel loopbacks, see the description of addchanloop.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
delchanloop <ifNumber> <vpi> <vci>
Syntax Description
ifNumber
The logical port number. The range for AXSM is 1-60. The range for AXSM-E is 1-32.
vpi
The VPI of the connection. The range is 0-4095.
vci
The VCI of the connection. The range is 1-65535.
Related Commands
addchanloop, dspchanloop
Attributes
Example
Remove the loopback from VPI/VCI 1 50 on logical port 4.
pop20two.1.AXSM.a > delchanloop 4 1 50
dellnloop
Delete Line Loop
Remove the line loopback state from a line.
Cards on Which This Command Runs
AXSM, AXSM-E
AXSM Syntax
dellnloop <-ds3 | -sonet> <bay.line>
Note
AXSM Syntax Description
AXSM-E Syntax
dellnloop < -ds3 | -e3 | -sonet | -ds1 | -e1 bay.line>
AXSM-E Syntax Description
Related Commands
addlnloop
Attributes
Example
Deleting a DS3 loopback line.
MGX8850.1.11.AXSME.a > dellnloop -ds3 1.6 -lpb 3Line loop-back status will be changed.Do you want to proceed (Yes/No) ?dncon
Down Connection
Temporarily deactivates (or downs) a connection so you can modify or troubleshoot it. The dncon command applies to only an SPVC. Execute at the master endpoint of a connection. Subsequently, when you view commands with dspconinfo or dspcon at the master endpoint, the display shows the connection state as down. If you execute either of these commands at the slave endpoint, the state appears as failed.
To reactivate the connection, use upcon.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dncon <ifNum> <vpi> <vci>
Syntax Description
Related Commands
upcon
Attributes
dnln
Down Line
Use dnln to de-activate a line on the current card. Before you can de-activate a line, you must:
Step 1
Step 2
Step 3
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dnln <bay.line>
Syntax Description
Related Commands
dspln, dsplns, cnfln, upln
Attributes
Example
De-activate line 1 in bay 1.
MGX8850.1.AXSM.a > dnln 1.1dnport
Down Port
The dnport command disables (or downs) a logical port and thereby halts all traffic on the logical port. The usual purpose for using dnport is troubleshooting. The configuration for the port remains intact whether the logical port is a UNI or an NNI. The command for enabling a downed port is upport.
For an NNI, the PXM45 de-routes the failed connections then re-routes them through other trunks. After you re-enable an NNI port through upport, you cannot return the re-routed connections to the upped port. The PXM45 routes connections over the trunk as needed.
On a UNI, the connections continue to exist, but remain in the failed state until you enable the port by executing upport.
Caution
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dnport <ifNum>
Syntax Description
Related Commands
dspport, dspports, upport
Attributes
Example
Disable port 1 on the current card.
MGX8850.1.AXSM.a > dnport 1dspadjlnalm
Display Adjacent Line Alarms
The dspadjlnalm command lets you display the alarm status line for the adjacent back card. To acquire the status, enter the bay and line number for the active back card.
Note
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspadjlnalm <bay.line>
Syntax Description
Related Commands
dspadjlnalmcnt, clradjlnalmcnt
Attributes
Example
MGX8850.3.AXSME.a > dspadjlnalm 1.1Line Number : 1.1Section Alarm State : ClearLine Alarm State : ClearPath Alarm State : ClearSection Stat Alarm State: ClearLine Stat Alarm State : ClearPath Stat Alarm State : ClearLOCD Alarm State : Cleardspadjlnalmcnt
Display Adjacent Line Alarm Counters
You give the active card bay.line number and this command displays the alarm status line for the adjacent back card at the given time interval (intvl).
Note
Cards on Which This Command Runs
AXSM-E
Syntax
dspadjlnalmcnt <bay.line> <intvl>
Syntax Description
Related Commands
dspadjlnalm, clradjlnalmcnt
Attributes
Example
MGX88503.AXSME.a> dspadjlnalmcnt 1.1 1Line Number : 1.1Interval Number : 1Section PM:-----------Num of LOSs : 0Num of LOFs : 0ESs : 0SESs : 0SEFSs : 0CVs : 0Line PM:-----------Num of AISs : 0Num of RFIs : 0Near End Far EndESs : 0 0SESs : 0 0CVs : 0 0UASs : 0 0Path PM:-----------Num of AISs : 0Num of RFIs : 0Near End Far EndESs : 0 0SESs : 0 0CVs : 0 0UASs : 0 0dspalm
Display Alarm—displays the alarms from among the configured alarm types for a line.
Use the dspalm command to view the alarms associated with a specified line. See cnfalm for a description of the types of alarms you can see. In addition to the configurable alarm types, the output also shows instances of loss of cell delineation (LOCD).
Cards on Which This Command Runs
AXSM, AXSM-E
AXSM Syntax
dspalm <-ds3|-e3|-sonet|-ds1|-e1> <bay.Line>
Syntax Description
Related Commands
cnfalm, clralm, dspalms, dspalmcnt
Attributes
Example
Display alarms on OC-12 line 1.1. In this example, the components of a SONET line (section, line, and path) are clear. Also, no instances of loss of cell delineation (LOCD) have occurred.
MGX8850.1.AXSM.a > dspalm -sonet 1.1Line Number : 1.1Section Alarm State : LOSLine Alarm State : ClearPath Alarm State : ClearSection Stat Alarm State: TotalESs,TotalSESs,TotalSEFSs,CurrentESs,CurrentSESssLine Stat Alarm State : TotalUASs,CurrentUASsPath Stat Alarm State : TotalUASs,CurrentUASsLOCD Alarm State : ClearAPS Alarm State : N/AOn another node, the same bay.line shows some of the possible errors: loss of signal (LOS), errored seconds and severely errored seconds, unavailable seconds.
MGX8850.1.AXSM.a > dspalm -sonet 1.1Line Number : 1.1Section Alarm State : LOSLine Alarm State : ClearPath Alarm State : ClearSection Stat Alarm State: CurrentESs,CurrentSESs,CurrentSEFSsLine Stat Alarm State : CurrentSESs,CurrentUASsPath Stat Alarm State : CurrentSESs,CurrentUASsLOCD Alarm State : ClearDisplay examples for AXSM-E.
MGX8850.11.AXSME.a > dspalm -sonet 1.1Line Number : 1.1Section Alarm State : LOS,LOFLine Alarm State : AISPath Alarm State : ClearSection Stat Alarm State: TotalESs,TotalSESs,TotalSEFSs,CurrentESs,CurrentSESs,CurrentSEFSsLine Stat Alarm State : TotalUASs,CurrentUASsPath Stat Alarm State : TotalUASs,CurrentUASsLOCD Alarm State : LOCDMGX8850.5.AXSME.a > dspalm -ds3 1.1Line Number : 1.1Alarm State : XmtRAI,RcvLOF,RcvLOS,RcvOtherFailureStatistical Alarm State: SEFS15minAlarm,SEFS24hrAlarm,UAS15minAlarm,UAS24hrAlarmPLCP Alarm State : ClearLOCD Alarm State : LOCDMGX8850.9.AXSME.a > dspalm -ds1 1.1Line Number : 1.1Alarm State : XmtFarEndLOF,LOF,LOSLOCD Alarm State : LOCDdspalmcnf
Display Alarm Configuration
Display the threshold information about the alarm statistics being collected. Refer to the cnfalm description for details regarding alarm threshold configuration.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspalmcnf <-sonetsec | -sonetline |-sonetpath | -ds3 | -e3 | -plcp> <bay.line>
Syntax Description
Related Commands
cnfalm, dspalm, dspalms
Attributes
Examples
Display alarm configuration for AXSM cards.
MGX8850.1.AXSM.a > dspalmcnf -sonetline 1.2LineNum: 1.2Line Stat Alarm Severity: No Alarm15min Threshold 24hr ThresholdLine ESs : 60 600Line SESs: 3 7Line CVs : 75 750Line UASs: 10 10MGX8850.1.AXSM.a > dspalmcnf -sonetsec 1.1LineNum: 1.1Section Stat Alarm Severity: No Alarm15min Threshold 24hr ThresholdSection ESs : 60 600Section SESs : 3 7Section SEFSs: 3 7Section CVs : 75 750Display alarm configuration for AXSM-E cards.
MGX8850.1.11.AXSME.a > dspalmcnf -ds3 1.1LineNum: 1.1Stat Alarm Severity: Minor15min Threshold 24hr ThresholdLCV : 20 20LES : 20 20PCV : 25 25PES : 20 20PSES : 3 3SEFS : 20 20UAS : 10 10MGX8850.1.6.AXSME.a > dspalmcnf -sonetsec 1.1LineNum: 1.1Section Stat Alarm Severity: Minor15min Threshold 24hr ThresholdSection ESs : 20 20Section SESs : 3 3Section SEFSs: 3 3Section CVs : 25 25MGX8850.1.6.AXSME.a > dspalmcnf -sonetline 1.1LineNum: 1.1Line Stat Alarm Severity: Minor15min Threshold 24hr ThresholdLine ESs : 20 20Line SESs: 3 3Line CVs : 25 25Line UASs: 10 10MGX8850.1.6.AXSME.a > dspalmcnf -sonetpath 1.1LineNum: 1.1Path Stat Alarm Severity: Minor15min Threshold 24hr ThresholdPath ESs : 20 20Path SESs: 3 3Path CVs : 25 25Path UASs: 10 10dspalmcnt
Display Alarm Counters
Displays the performance monitoring alarm counters for either a SONET or DS3 line.
Cards on Which This Command Runs
AXSM, AXSM-E
AXSM Syntax
dspalmcnf -ds3 | -e3 | -plcp | -sonet | -ds1 | -e1 <bay.line>
Syntax Description
Related Commands
clralmcnt
Attributes
Examples
Display the alarm count for T3 line 1 in bay 1.
MGX8850.11.AXSM.a > dspalmcnt -ds3 1.1Line Num: 2.1CurrentLCV : 9109365CurrentLES : 13CurrentPCV : 1CurrentPES : 1CurrentPSES: 0CurrentSEFS: 11CurrentUAS : 0Num of LOS : 1Num of OOF : 1Num of RAI : 0Num of CCV : 0Num of FE : 0Display SONET line 1 in bay 1.
MGX8850.6.AXSM.a > dspalmcnt -sonet 1.1Line Num: 1.1Elapsed Time (in sec): 1634Section PM:-----------Num of LOSs: 1Num of LOFs: 1CurrentESs: 0CurrentSESs: 0CurrentSEFSs: 1CurrentCVs: 1Line PM:--------Num of AISs: 0Num of RFIs: 0Near End Far EndCurrentESs : 1 CurrentESs : 1CurrentSESs: 0 CurrentSESs: 0CurrentCVs : 1 CurrentCVs : 1CurrentUASs: 0 CurrentUASs: 0Path PM:--------Num of AISs: 1Num of RFIs: 1Near End Far EndCurrentESs : 0 CurrentESs : 0CurrentSESs: 0 CurrentSESs: 0CurrentCVs : 0 CurrentCVs: 0CurrentUASs: 0 CurrentUASs: 0For AXSM-E, examples show the performance monitoring alarm counters of a DS3, SONET, and DS1 line for current 15 minute interval. Counters with description "Num of . . ." are counters for the current 15 minute interval.
MGX8850.5.AXSME.a > dspalmcnt -ds3 1.1Line Number: 1.1Elapsed Time(in sec): 188Num of LOS : 0Num of OOF : 0Num of RAI : 0Near End Far EndCurrentCCVs : 0 CurrentCCVs : 0CurrentCESs : 0 CurrentCESs : 0CurrentCSESs : 0 CurrentCSESs : 0CurrentUASs : 189 CurrentUASs : 0CurrentLCV : 0CurrentLES : 0CurrentPCV : 0CurrentPES : 0CurrentPSES : 0CurrentSEFS : 189CurrentLSES : 0Current24HrLCV : 0Current24HrLES : 0Current24HrPCV : 0Current24HrPES : 0Current24HrPSES: 0Current24HrSEFS: 29700Current24HrUAS : 29700Current24HrCCV : 0Current24HrCES : 0Current24HrCSES: 0Current24HrLSES: 0MGX8850.11.AXSME.a > dspalmcnt -sonet 1.1Line Number : 1.1Elapsed Time(in sec): 298Section PM:-----------Num of LOSs : 0Num of LOFs : 0CurrentESs : 299CurrentSESs : 299CurrentSEFSs : 299CurrentCVs : 0Current24HrESs : 64795Current24HrSESs : 64795Current24HrSEFSs: 64795Current24HrCVs : 0Line PM:--------Num of AISs: 0Num of RFIs: 0Near End Far EndCurrentESs : 0 CurrentESs : 0CurrentSESs : 0 CurrentSESs : 0CurrentCVs : 0 CurrentCVs : 0CurrentUASs : 299 CurrentUASs : 0Current24HrESs : 0 Current24HrESs : 0Current24HrSESs: 0 Current24HrSESs: 0Current24HrCVs : 0 Current24HrCVs : 0Current24HrUASs: 64795 Current24HrUASs: 0Path PM:--------Num of AISs: 0Num of RFIs: 0Near End Far EndCurrentESs : 0 CurrentESs : 0CurrentSESs : 0 CurrentSESs : 0CurrentCVs : 0 CurrentCVs : 0CurrentUASs : 299 CurrentUASs : 0Current24HrESs : 0 Current24HrESs : 0Current24HrSESs: 0 Current24HrSESs: 0Current24HrCVs : 0 Current24HrCVs : 0Current24HrUASs: 64795 Current24HrUASs: 0MGX8850.5.AXSME.a > dspalmcnt -ds1 1.1Line Number: 1.1Elapsed Time(in sec): 520Near End Far EndCurrentUASs : 0 CurrentUASs : 0CurrentLESs : 0 CurrentLESs : 0CurrentESs : 0 CurrentESs : 0CurrentSESs : 0 CurrentSESs : 0CurrentSEFSs : 0 CurrentSEFSs : 0CurrentPCVs : 0 CurrentPCVs : 0CurrentLCVs : 0dspalms
Display Alarms
Display all line-related alarms on the card. RFC 2258 describes the alarm categories. The display can easily scroll for many pages if more than one line is active. See cnfalm for a description of types of alarms you might see. In addition to the alarms from cnfalm, the dspalms command also displays instances of loss of cell delineation (LOCD).
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspalms
Syntax Description
This command takes no parameters.
Related Commands
dspalm, clralm
Attributes
Example
Display alarms for the lines on the current AXSM card.
MGX8850.1.AXSM.a > dspalmsLine Number: 1.1Alarm StateSection : LOSLine : ClearPath : ClearStatistical Alarm StateSection : TotalESs,TotalSESs,TotalSEFSs,CurrentESs,CurrentSESs,CurrentSEFSsLine : TotalSESs,TotalUASs,CurrentUASsPath : TotalSESs,TotalUASs,CurrentUASsLOCD Alarm : ClearLine Number: 1.2Alarm StateSection : LOSLine : ClearPath : ClearStatistical Alarm StateSection : TotalSESs,TotalSEFSs,CurrentESs,CurrentSESs,CurrentSEFSsLine : TotalSESs,TotalUASs,CurrentUASsPath : TotalSESs,TotalUASs,CurrentUASsLOCD Alarm : ClearLine Number: 2.1Alarm StateSection : ClearLine : ClearPath : ClearStatistical Alarm StateSection : ClearLine : ClearPath : ClearLOCD Alarm : ClearLine Number: 2.2Alarm StateSection : ClearLine : ClearPath : ClearStatistical Alarm StateSection : ClearLine : ClearPath : ClearLOCD Alarm : ClearDisplay alarms for the lines on the current AXSM-E card.
MGX8850.11.AXSME.a > dspalms---------------------------------------------Line Number: 1.1Alarm StateSection : LOS,LOFLine : AISPath : ClearLOCD : LOCDStatistical Alarm StateSection : TotalESs,TotalSESs,TotalSEFSs,CurrentESs,CurrentSESs,CurrentSEFSsLine : TotalUASs,CurrentUASsPath : TotalUASs,CurrentUASsLine Number: 1.2Alarm StateSection : LOS,LOFLine : AISPath : ClearLOCD : LOCDStatistical Alarm StateSection : TotalESs,TotalSESs,TotalSEFSs,CurrentESs,CurrentSESs,CurrentSEFSsLine : TotalUASs,CurrentUASsPath : TotalUASs,CurrentUASsLine Number: 1.3Alarm StateSection : ClearLine : ClearPath : ClearLOCD : ClearStatistical Alarm StateSection : ClearLine : ClearPath : ClearLine Number: 1.4Alarm StateSection : ClearLine : ClearPath : ClearLOCD : ClearStatistical Alarm StateSection : ClearLine : ClearPath : Cleardspautolndiag
Display Auto Line Diagnostics
Displays the status of auto line diagnostic feature on card.
Cards on Which This Command Runs
AXSM-E
Syntax
dspautolndiag
Syntax Description
Related Commands
cnfautolndiag
Attributes
Example
MGX8850.5.AXSME.a > dspautolndiagAuto Line Diagnostics : DisabledM8850_NY.5.AXSME.a >dspbecnt
Display Bit Error Count
The dspbecnt command lets you display the APS-related bit error counters.
Cards on Which This Command Runs
AXSM
Syntax
dspbecnt <working-bay.line>
Syntax Description
working-bay.line
Identifies the bay (1 or 2) and the number of the line. The line number is from 1 to the highest numbered line on the back card. For the range of line numbers on specific AXSM models, see Table 9-1.
Related Commands
addapsln, cnfapsln, delapsln, dspapsln, dspapslns, switchapsln, dspapsbkplane, dspbecnt
Attributes
dspbert
Display Bit Error Rate Test
Displays the status of the bit error rate test.
Cards on Which This Command Runs
AXSM-E
Syntax
dspbert <bay.line>
Syntax Description
Related Commands
dspbertstats
Attributes
Example
MGX8850.10.AXSME.a > dspbert 1.1Bert Admin Operational BERT StartLine Status Status Pattern Date---- ------ ------------- ---------------------- --------------------1.1 Down OutOfSync AltOneZerodspbertstats
Display Bit Error Rate Test Statistics
Displays the bit error rate test statistics.
Cards on Which This Command Runs
AXSM-E
Syntax
dspbertstats <bay.line>
Syntax Description
Related Commands
dspbert
Attributes
Example
MGX8850.5.AXSME.a > dspbertstats 1.1Bert Bits Bit Errors ErrorsLine Received Received Injected---- ---------- ---------- --------1.1 0 0 0dspcd
Display Card
Display the following information about a card:
•
•
•
•
Note
•
Use the maximum number of supported connections to help you configure resource partitions. If a particular resource partition has close to the maximum supported by hardware on a line, few or no connections would be possible in another partition on the same line.Some of the information that dspcd shows is common to the version command, but version shows the boot code version in bold.
Cards on Which This Command Runs
PXM45, AXSM, AXSM-E
Syntax
dspcd
Syntax Description
This command does not take parameters.
Related Commands
dspcds, version
Attributes
Examples
Display card details for the current PXM45.
Note
M8850_NY.7.PXM.a > dspcdM8850_NY System Rev: 02.01 Dec. 22, 2001 22:38:43 PSTMGX8850 Node Alarm: MAJORSlot Number 7 Redundant Slot: 8Front Card Upper Card Lower Card---------- ---------- ----------Inserted Card: PXM45 UI Stratum3 PXM HardDiskDriveReserved Card: PXM45 UI Stratum3 PXM HardDiskDriveState: Active Active ActiveSerial Number: SBK050302AF SBK045203PJ SBK044602HJPrim SW Rev: 2.1(70.131)A --- ---Sec SW Rev: 2.1(70.131)A --- ---Cur SW Rev: 2.1(70.131)A --- ---Boot FW Rev: 2.1(70.131)A --- ---800-level Rev: A0 A0 A0800-level Part#: 800-06147-08 800-05787-02 800-05052-04CLEI Code: BAA670YCAA BA7IBCLAAA BA7IADNAAAReset Reason: On Reset From ShellCard Alarm: NONEFailed Reason: NoneMiscellaneous Information:M8850_NY System Rev: 02.01 Dec. 22, 2001 22:38:43 PSTMGX8850 Node Alarm: MAJORCrossbar Slot Status: PresentAlarm Causes------------NO ALARMSM8850_NY.7.PXM.a >Display card details for the current AXSM-1-2488.
MGX8850.1.AXSM.a > dspcdFront Card Upper Card Lower Card---------- ---------- ------------Card Type: AXSM-1-2488 SMFSR-1-2488 ---State: Active Present UndefinedSerial Number: SAK04010033 SAK040400F9 ---Boot FW Rev: 2.0(233)A1 --- ---SW Rev: 2.0(22)D --- ---800-level Rev: 09 05 ---Orderable Part#: 800-5795-1 800-5490-2 ---PCA Part#: 73-4363-1 73-4040-2 ---Reset Reason:On Power upCard SCT Id: 2#Lines #Ports #Partitions #SPVC #SVC------ ------ ----------- ------- -------1 1 1 2 1Port Group[1]:#Chans supported:32512 Lines:1.1Port Group[2]:#Chans supported:32512 Lines:1.2Port Group[3]:#Chans supported:32512 Lines:2.1Port Group[4]:#Chans supported:32512 Lines:2.2dspcdalms
Display Card Alarms
Use dspcdalms on the PXM45 to display alarms that have been reported by a service module. If dspcdalms shows an alarm for one of the following parts of a card, you can cc to that card and execute one of the applicable commands:
•
•
•
•
In addition to the preceding, on the AXSM you can also execute dspalm and dspalms.
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
•
•
•
The dspcdalms command is part of a hierarchy of troubleshooting commands you can execute on the PXM45 or a service module. Frequently, dspcdalms follows the higher-level command dspndalms.
Cards on Which This Command Runs
PXM45
Syntax
dspcdalms [slot]
Syntax Description
slot identifies a particular slot. For the current PXM45, slot is unnecessary. For any other card, you must include slot.
Related Commands
PXM45: dspndalms, dspswalms, dspclkalms,
AXSM: dspalm, dspalms
Attributes
Examples
Display card-level alarms for the card in slot 8.
node19.8.PXM.a > dspcdalms 8Node Card Alarm SummaryLine Alarm Slot 8 Critical 0 Major 0 Minor 0Port Alarm Slot 8 Critical 0 Major 0 Minor 0Connect Alarm Slot 8 Critical 0 Major 0 Minor 0Display card alarms without specifying a slot.
MGX8850.7.PXM.a > dspcdalmsNode Card Alarm SummaryLine Alarm Slot 1 Critical 0 Major 0 Minor 0Port Alarm Slot 1 Critical 0 Major 0 Minor 0Feeder Alarm Slot 1 Critical 0 Major 0 Minor 0Channel Alarm Slot 1 Critical 0 Major 0 Minor 0Line Alarm Slot 2 Critical 0 Major 0 Minor 0Port Alarm Slot 2 Critical 0 Major 0 Minor 0Feeder Alarm Slot 2 Critical 0 Major 0 Minor 0Channel Alarm Slot 2 Critical 0 Major 0 Minor 0Line Alarm Slot 3 Critical 0 Major 0 Minor 0Port Alarm Slot 3 Critical 0 Major 0 Minor 0Feeder Alarm Slot 3 Critical 0 Major 0 Minor 0Channel Alarm Slot 3 Critical 0 Major 2 Minor 0Line Alarm Slot 5 Critical 0 Major 0 Minor 0Port Alarm Slot 5 Critical 0 Major 0 Minor 0Feeder Alarm Slot 5 Critical 0 Major 0 Minor 0Channel Alarm Slot 5 Critical 0 Major 0 Minor 0Line Alarm Slot 6 Critical 0 Major 0 Minor 0Port Alarm Slot 6 Critical 0 Major 0 Minor 0Feeder Alarm Slot 6 Critical 0 Major 0 Minor 0Channel Alarm Slot 6 Critical 0 Major 0 Minor 0Line Alarm Slot 9 Critical 1 Major 0 Minor 0Port Alarm Slot 9 Critical 0 Major 0 Minor 0Feeder Alarm Slot 9 Critical 0 Major 0 Minor 0Channel Alarm Slot 9 Critical 0 Major 0 Minor 0Line Alarm Slot 10 Critical 2 Major 0 Minor 1Port Alarm Slot 10 Critical 0 Major 0 Minor 0Feeder Alarm Slot 10 Critical 0 Major 0 Minor 0Channel Alarm Slot 10 Critical 0 Major 0 Minor 0Line Alarm Slot 12 Critical 0 Major 0 Minor 0Port Alarm Slot 12 Critical 0 Major 0 Minor 0Feeder Alarm Slot 12 Critical 0 Major 0 Minor 0Channel Alarm Slot 12 Critical 0 Major 0 Minor 0MGX8850.7.PXM.a > dspcdalmsCard Alarm SummarySlot 1 Crit 0 Maj 0 Min 0 || Slot 17 Crit 0 Maj 0 Min 0Slot 2 Crit 0 Maj 0 Min 0 || Slot 18 Crit 0 Maj 0 Min 0Slot 3 Crit 0 Maj 0 Min 0 || Slot 19 Crit 0 Maj 0 Min 0Slot 4 Crit 0 Maj 0 Min 0 || Slot 20 Crit 0 Maj 0 Min 0Slot 5 Crit 0 Maj 0 Min 0 || Slot 21 Crit 0 Maj 0 Min 0Slot 6 Crit 12 Maj 15 Min 19 || Slot 22 Crit 0 Maj 0 Min 0Slot 7 Crit 0 Maj 0 Min 1 || Slot 23 Crit 0 Maj 0 Min 0Slot 8 Crit 0 Maj 2 Min 0 || Slot 24 Crit 0 Maj 0 Min 0Slot 9 Crit 0 Maj 0 Min 0 || Slot 25 Crit 0 Maj 0 Min 0Slot 10 Crit 0 Maj 0 Min 0 || Slot 26 Crit 0 Maj 0 Min 0Slot 11 Crit 0 Maj 0 Min 0 || Slot 27 Crit 0 Maj 0 Min 0Slot 12 Crit 0 Maj 0 Min 0 || Slot 28 Crit 0 Maj 0 Min 0Slot 13 Crit 0 Maj 0 Min 0 || Slot 29 Crit 0 Maj 0 Min 0Slot 14 Crit 0 Maj 0 Min 0 || Slot 30 Crit 0 Maj 0 Min 0Slot 15 Crit 0 Maj 0 Min 0 || Slot 31 Crit 0 Maj 0 Min 0Slot 16 Crit 0 Maj 0 Min 0 || Slot 32 Crit 0 Maj 0 Min 0Use dspcdalms <slot> to see more detail.MGX8850.7.PXM.a > dspcdalms 6Card Alarm SummaryHardware Alarm Critical 0 Major 0 Minor 0Card State Alarm Critical 0 Major 0 Minor 0Disk Alarm Critical 0 Major 0 Minor 0Line Alarm Critical 3 Major 4 Minor 5Port Alarm Critical 4 Major 5 Minor 6Feeder Alarm Critical 0 Major 0 Minor 0Channel Alarm Critical 5 Major 6 Minor 7MGX8850.7.PXM.a > dspndalmsNode Alarm SummaryAlarm Type Critical Major MinorClock Alarms 0 0 0Switching Alarms 0 0 2Environment Alarms 0 0 0Card Alarms 12 17 18dspcdbucketcnt
Display Cell Counts for the Card
The dspcdbucketcnt command shows the following cell-related counts:
•
•
•
•
•
In addition to the other bucket command on the AXSM (dsplnbucketcnt), the display commands for the switch planes on the PXM45 may help you analyze cell flows. (See the dspxbar-type commands.)
Cards on Which This Command Runs
AXSM
Syntax
dspcdbucketcnt
Syntax Description
This command takes no parameters.
Related Commands
dsplnbucketcnt, all the dspxbar-type of commands except dspxbarstatus
Attributes
Example
Display the bucket counters for the current AXSM.
MGX8850.12.AXSM.a > dspcdbucketcntcells to backplane(QLSI) : 0cells from QE 48 : 5347cells from backplane(QLSI) : 6917CLP0 cells dropped : 0CLP1 cells dropped : 0undefined cells from port : 0errored OAM from port : 0invalid OAM from port : 0unsupported OAM from port : 0errored RM cells from port :0dspcdcnt
Display Card Counters
Displays the number of cells transferred between the service module and the switching planes. (Synonyms for switching plane are crossbar, xbar, and switch fabric.) One switch fabric is implemented in hardware by one ASIC. The dspcdcnt command primarily applies to debugging.
The type of information consists of:
•
•
•
•
•
•
•
•
•
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspcdcnt
Related Commands
clrcdcnt (on the AXSM), dspxbar, dspdevalms, dspdeverrhist, dspxbarerrthresh
Attributes
AXSM Example
Display the cell transfers between the current AXSM and the switch planes (crossbar planes).
U1.11.AXSM.a > dspcdcntIngress cells to xbar Egress cells from xbar--------------------- ----------------------plane 1 : 0000000000000000326416 0000000000000000325869plane 2 : 0000000000000000326415 0000000000000000325890plane 3 : 0000000000000000217610 0000000000000000217413plane 4 : 0000000000000000000000 0000000000000000000000plane 5 : 0000000000000000217611 0000000000000000217433plane 6 : 0000000000000000326417 0000000000000000325996plane 7 : 0000000000000000326417 0000000000000000325996plane 8 : 0000000000000000000000 0000000000000000000000Ingress cells to destination slot----------------------------------------------------------------slot 01: 0000000000000000000000 slot 02: 0000000000000000000000slot 03: 0000000000000000000000 slot 04: 0000000000000000000000slot 05: 0000000000000000000000 slot 06: 0000000000000000000000slot 07: 0000000000000000004036 slot 08: 0000000000000000000000slot 09: 0000000000000000000000 slot 10: 0000000000000000000000slot 11: 0000000000000001736851 slot 12: 0000000000000000000000slot 13: 0000000000000000000000 slot 14: 0000000000000000000000Ingress cells Egress cells------------------------------------ ---------------------------To backplane: 0000000000000001740886 From backplane:0000000000000001738597From QE : 0000000000000001740888 To QE:0000000000000001738599QE Total (Ingress + Egress)-----------------------------------------------------Undefined cell type : 0000000000000000000000Err OAM (bad CRC) cells : 0000000000000000000000Invalid OAM type or function: 0000000000000000000000Unsupported OAM cells : 0000000000000000000000Err RM (bad CRC) cells : 0000000000000000000000QE congestion discard CLP0 : 0000000000000000000000QE congestion discard CLP1 : 0000000000000000000000Display cell transfers between the current AXSM and the switching planes (crossbars) on the XM60 cards.
NODE_U4.3.AXSM.a > dspcdcntIngress Count Egress Count------------- ------------Cells to xbar plane[1]: 8702 Cells from xbar plane[1]: 8733Cells to xbar plane[2]: 8702 Cells from xbar plane[2]: 8627Cells to xbar plane[3]: 10443 Cells from xbar plane[3]: 10503Cells to xbar plane[4]: 0 Cells from xbar plane[4]: 0Cells to xbar plane[5]: 0 Cells from xbar plane[5]: 0Cells to xbar plane[6]: 0 Cells from xbar plane[6]: 0Cells to xbar plane[7]: 0 Cells from xbar plane[7]: 0Cells to xbar plane[8]: 0 Cells from xbar plane[8]: 0Total cells to backplane: 27847 Total cells from backplane:27863Cells from QE48 : 27847 Cells to QE48: 27863Undefined cells : 0 CLP0 cells discard: 0Errored OAM cells : 0 CLP1 cells discard: 0Invalid OAM cells : 0Unsupported OAM cells : 0Errored RM cells : 0Cells to dest slot[01]: 0 Cells to dest slot[02]: 0Cells to dest slot[03]: 0 Cells to dest slot[04]: 0Cells to dest slot[05]: 0 Cells to dest slot[06]: 0Cells to dest slot[07]: 27847 Cells to dest slot[08]: 0Cells to dest slot[11]: 0 Cells to dest slot[12]: 0Cells to dest slot[13]: 0 Cells to dest slot[14]: 0Cells to dest slot[15]: 0 Cells to dest slot[16]: 0AXSM-E Example
Display card count on AXSM-E.
MGX8850.6.AXSME.a > dspcdcntAll cell counters are cleared upon read!Ingress cells to xbar Egress cells from xbar--------------------- ----------------------plane 1 : 0000000000000000219156 0000000000000000219204plane 2 : 0000000000000000219201 0000000000000000219027plane 3 : 0000000000000000263077 0000000000000000263335plane 4 : 0000000000000000000000 0000000000000000000000plane 5 : 0000000000000000000000 0000000000000000000000plane 6 : 0000000000000000000000 0000000000000000000000plane 7 : 0000000000000000000000 0000000000000000000000plane 8 : 0000000000000000000000 0000000000000000000000Ingress cells to destination slot----------------------------------------------------------------slot 01 : 0000000000000000000000 slot 02: 0000000000000000000000slot 03 : 0000000000000000000000 slot 04: 0000000000000000000000slot 05 : 0000000000000000000000 slot 06: 0000000000000000688036slot 07 : 0000000000000000013398 slot 08: 0000000000000000000000slot 09 : 0000000000000000000000 slot 10: 0000000000000000000000slot 11 : 0000000000000000000000 slot 12: 0000000000000000000000slot 13 : 0000000000000000000000 slot 14: 0000000000000000000000dspcderrs
Display Card Errors
Display information about card errors.
Cards on Which This Command Runs
PXM45
Syntax
dspcderrs
Related Commands
clrerr
Attributes
Example
Display all card errors.
wilco.7.PXM.a > dspcderrsdspcderrs08/05/95-18:53:05 tRootTask 3 Task failed : scm09/05/95-09:14:08 tRootTask 3 Task failed : scmvalue = 0 = 0x0wilco.7.PXM.a >dspcds
Display Cards
Displays high-level information for all the cards in the node. For more detailed information about a card, execute dspcd on the CLI of that card. The information that dspcds provides is the:
•
•
•
•
•
•
•
•
Cards on Which This Command Runs
PXM45
Syntax
dspcds
Related Commands
dspcd, version
Attributes
Example
Display information for all cards in the MGX 8850 switch.
M8850_NY.7.PXM.a > dspcdsM8850_NY System Rev: 02.01 Dec. 22, 2001 22:40:51 PSTChassis Serial No: SAA03211181 Chassis Rev: B0 GMT Offset: -8Node Alarm: MAJORCard Front/Back Card Alarm Redundant RedundancySlot Card State Type Status Slot Type--- ---------- -------- -------- ------- -----01 Active/Active AXSM_4OC12 NONE 02 PRIMARY SLOT02 Standby/Active AXSM_4OC12 NONE 01 SECONDARY SLOT03 Active-U/Active AXSM_4OC12 NONE NA NO REDUNDANCY04 Empty --- --- --- ---05 Active/Empty Resv AXSME_2OC12 MAJOR NA NO REDUNDANCY06 Active/Mismatch AXSM_16OC3_B MINOR NA NO REDUNDANCY07 Active/Active PXM45 NONE 08 PRIMARY SLOT08 Standby/Active PXM45 NONE 07 SECONDARY SLOT09 Active/Active RPM_PR NONE NA NO REDUNDANCY10 Empty --- --- --- ---11 Empty --- --- --- ---12 Empty --- --- --- ---13 Empty --- --- --- ---14 Empty --- --- --- ---M8850_NY.7.PXM.a >Display information for all cards in the current MGX 8950 switch.
M8950_DC.7.PXM.a > dspcdsM8950_DC System Rev: 02.01 Dec. 22, 2001 22:40:53 PSTChassis Serial No: SCA0504043H Chassis Rev: A0 GMT Offset: -8Node Alarm: CRITICALCard Front/Back Card Alarm Redundant RedundancySlot Card State Type Status Slot Type--- ---------- -------- -------- ------- -----01 Active/Active AXSM_4OC12 NONE NA NO REDUNDANCY02 Empty --- --- --- ---03 Empty --- --- --- ---04 Empty --- --- --- ---05 Active/Active AXSM_1OC48_B NONE NA NO REDUNDANCY06 Empty --- --- --- ---07 Active/Active PXM45B NONE 08 PRIMARY SLOT08 Empty Resvd/Empty --- MAJOR 07 SECONDARY SLOT09 Active/Empty XM_60 NONE NA NO REDUNDANCY10 Active/Empty XM_60 NONE NA NO REDUNDANCY11 Active/Active RPM_PR NONE NA NO REDUNDANCY12 Empty --- --- --- ---13 Empty --- --- --- ---14 Empty --- --- --- ---15 Empty --- --- --- ---Type <CR> to continue, Q<CR> to stop:M8950_DC System Rev: 02.01 Dec. 22, 2001 22:40:53 PSTChassis Serial No: SCA0504043H Chassis Rev: A0 GMT Offset: -8Node Alarm: CRITICALCard Front/Back Card Alarm Redundant RedundancySlot Card State Type Status Slot Type--- ---------- -------- -------- ------- -----16 Empty --- --- --- ---25 Active/Empty XM_60 NONE NA NO REDUNDANCY26 Active/Empty XM_60 NONE NA NO REDUNDANCYM8950_DC.7.PXM.a >dspcdstatus
Display Card Status
Displays the most serious alarms reported by a service module. The alarm information pertains to:
•
•
•
•
•
You can use this command to isolate the alarm source if, for example, you see that a Critical Alarm LED is lit or just want to check the node for alarms. You can subsequently use other alarm commands to locate the problem. Some alarm commands run on only the PXM45, and other commands run on service modules. The commands other than dspcdstatus on the PXM45 are:
•
•
•
•
•
The alarm monitoring function on the PXM45 uses two criteria to determine which alarm to display. One criterion is alarm severity, and the other is hierarchy.
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
•
•
•
Two hierarchies of alarm types exist. They are card alarms and node alarms. See Figure 9-4 for a list of alarm categories. Note that, although the card alarms appear to apply to only service modules, this category can also apply to the PXM45.
Figure 9-4 Alarm Type Hierarchy
The alarm monitoring function reports the highest status alarm after it sorts the current alarms first by severity then by hierarchy. If alarms of equal severity exit in both hierarchies, the system reports the node alarm as the highest status alarm. For example, if a major alarm exists on a line and a major power alarm exists, the dspcdstatus command displays the power alarm as the highest status alarm.
Cards on Which This Command Runs
PXM45
Syntax
dspcdstatus
Syntax Description
This command requires a slot number.
Related Commands
dspndalms, dspcdalms, dspenvalms, dspclkalms, dspswalms, dspalm (AXSM), dspalms (AXSM)
Attributes
Examples
Display status of slot 11. The display shows a critical line alarm for slot 11. Next, cc to slot 11.
Golden_U2.8.PXM.a > dspcdstatus 11Logical Slot 11 Physical Slot 11Card Alarm Status - Type LINE Severity CRITICALThe display for dspalms shows that line 1 in bay 1 has LOS. (This example shows only the alarmed line. A complete display shows the status of all lines)
Golden_U2.11.AXSM.a > dspalmsLine Number: 1.1Alarm StateSection : LOS,LOFLine : AISPath : RDIdspchancnt
Display Channel Counters
Display the statistical counters for a connection (channel). See the cnfdiag command for a detailed description of MGX 8850 diagnostics.
Note
Cards on Which This Command Runs
AXSM, AXSM-E
AXSM Syntax
dspchancnt <ifNum> <vpi> <vci> <isPVC>
AXSM Syntax Description
AXSM-E Syntax
dspchancnt <ifNum> <vpi> <vci> -r <dsp interval> -max <max dsp time>
AXSM-E Syntax Description
Related Commands
dspchstats, clrchancnt, dspcdcnt
Attributes
Example
Display channel counters on AXSM for 1 10 100.
Golden_U2.11.AXSM.a > dspchancnt 1 10 100Ingress EgressInstantaneous Qdepth: 0 0Arrival CLP0 cells: 0 492305Arrival CLP1 cells: 0 0Dscd CLP0 cells: 0 -Dscd CLP0+1 cells: 0 -Noncompliant cells: 0 -Arrival EFCI cells: 0 0Arrival EOF cells: 0 0Display channel counters on AXSM-E for 1 10 100.
MGX8850.6.AXSME.a > dspchancnt 1 10 100 -r 1 -max 1Ingress chan stat Egress chan stat-------------------------------------- --------------------------------------All non-compliant cells : 0CLP1 non-compliant : 0CLP0 non-compliant : 0CLP0 -> CLP1 : 0Cells from port(Before policing) : 0 Cells to port : 0CLP0 from port : 0 CLP0 to port : 0CLP1 from port : 0 CLP1 to port : 0EOF from port : 0 EOF to port : 0EFCI1 from port : 0 EFCI1 to port : 0RM to port : 0Cells to network : 0 Cells from network : 0CLP0 to network : 0 CLP0 from network : 0CLP1 to network : 0 CLP1 from network : 0EFCI1 to network : 0 EFCI1 from network : 0Cells discarded in qe : 0 Cells discarded in qe : 0CLP0 discarded in qe : 0 CLP0 discarded in qe : 0CLP1 discarded in qe : 0 CLP1 discarded in qe : 0EOF discarded in qe : 0EFCI1 discarded in qe : 0VC queue depth : 0 VC queue depth : 0ACR (Valid for WFQ conns) : 1 ACR (Valid for WFQ conns) : 1OAM from port : 0 OAM to port : 0RM from port : 0RM to network : 0 RM from network : 0OAM to network : 0 OAM from network : 0OAM discarded in qe : 0 OAM discarded in qe : 0EFCI1 discarded in qe : 0RM discarded in qe : 0 RM discarded in qe : 0Type <Ctrl>C to quit----------------------------------------------------------------------------------Ingress chan stat Egress chan stat-------------------------------------- --------------------------------------All non-compliant cells : 0CLP1 non-compliant : 0CLP0 non-compliant : 0CLP0 -> CLP1 : 0Cells from port(Before policing) : 999 Cells to port : 1000CLP0 from port : 999 CLP0 to port : 1000CLP1 from port : 0 CLP1 to port : 0EOF from port : 0 EOF to port : 0EFCI1 from port : 0 EFCI1 to port : 0RM to port : 0Cells to network : 1000 Cells from network : 1000CLP0 to network : 1000 CLP0 from network : 1000CLP1 to network : 0 CLP1 from network : 0EFCI1 to network : 0 EFCI1 from network : 0Cells discarded in qe : 0 Cells discarded in qe : 0CLP0 discarded in qe : 0 CLP0 discarded in qe : 0CLP1 discarded in qe : 0 CLP1 discarded in qe : 0EOF discarded in qe : 0EFCI1 discarded in qe : 0VC queue depth : 0 VC queue depth : 0ACR (Valid for WFQ conns) : 1 ACR (Valid for WFQ conns) : 1OAM from port : 0 OAM to port : 0RM from port : 0RM to network : 0 RM from network : 0OAM to network : 0 OAM from network : 0OAM discarded in qe : 0 OAM discarded in qe : 0EFCI1 discarded in qe : 0RM discarded in qe : 0 RM discarded in qe : 0dspchanloop
Display Channel Loopbacks
Show channel (connection) loopbacks on a logical port.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspchanloop <ifNumber>
Syntax Description
Related Commands
addchanloop, delchanloop
Attributes
Example
Display any channel loopbacks on logical port 4. The display shows one connection with a loopback in the ingress direction.
pop20two.1.AXSM.a > dspchanloop 4Port Type lVPI lVCI rVPI rVCI4 igrLpbk 1 50 0 35dspchantests
Display Channel Tests—display results of tstdelay or tstconseg commands.
The tstdelay or tstconseg commands test the integrity of the path of a connection in the ingress and egress directions, respectively. After you successfully start a test through tstdelay or tstconseg, the returned message directs you to use dspchantests or dspcon to see the results. The same test results presented by dspchantests appears in the dspcon display, but dspchantests shows only the test results.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspchantests <ifNum> <vpi> <vci> [-num <count>]
Syntax Description
Related Commands
tstdelay, tstconseg, dspcon
Attributes
Examples
Run tstdelay on connection 1 10 100 then display the results.
Step 1
node19.1.AXSM.a > tstdelay 1 10 100Test started; Use dspcon/dspchantests to see test resultsStep 2
node19.1.AXSM.a > dspchantests 1 10 100Connection Id Test Type Direction Result Round Trip Delay============= ========= ========= ======= ================01.0010.00100: OAM Lpbk ingress Success 40000Run tstconseg for 1 10 100 then display the results.
Step 1
node19.1.AXSM.a > tstconseg 1 10 100Test started; Use dspcon/dspchantests to see test resultsStep 2
node19.1.AXSM.a > dspchantests 1 10 100Connection Id Test Type Direction Result Round Trip Delay============= ========= ========= ======= ================01.0010.00100: OAM Lpbk egress TimeOut 0
dspclkalms
Display Clock Alarms
Displays alarms associated with the primary or secondary clock source.
The switch constantly monitors the state of the clocks. On the local node, the clock monitor declares an alarm if the clock becomes undetectable or goes out of specification for any reason. The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
•
•
•
The dspclkalms command is part of a hierarchy of troubleshooting commands you can execute on the PXM45 or a service module. Frequently, dspclkalms follows the higher-level command dspndalms. The dspndalms command shows a variety of alarms within the switch and helps isolate the problem.
The dspndalms and dspclkalms commands run on the PXM45. If the errored clock source appears to be on a service module, you can cc to the CLI of that card and execute a variety of alarm commands and other troubleshooting commands.
Cards on Which This Command Runs
PXM45
Syntax
dspclkalms
Syntax Description
This command takes no parameters.
Related Commands
dspcdstatus, dspndalms, dspalm, dspalms, dspclksrcs, cnfclksrc
Attributes
Example
Display clock alarms.
M8850_NY.7.PXM.a > dspclkalmsM8850_NY System Rev: 02.01 Dec. 22, 2001 22:44:28 PSTMGX8850 Node Alarm: MAJORClock Manager Alarm Summary----------------------------NETWORK CLOCK ALARM : LOST PRIMARY REFERENCE : MINORNETWORK CLOCK ALARM : STANDBY LOST PRIMARY REFERENCE : MINORCritical Major Minor000 000 002dspclksrcs
Display Clock Sources
Displays the configuration and status of the clock sources on the node. (For details about network synchronization, see the description of cnfclksrc.) The dspclksrcs output consists of:
•
•
•
•
Note
Cards on Which This Command Runs
PXM45
Type of Clock Source
The type is either BITS or generic. Currently, generic applies to only an AXSM-sourced clock. If a user-specified priority of clock is not configured, the source is null. For the current release, the null source is presumed to be the internal oscillator.
Possible Sources
The source of the clock has the format [shelf.]slot:subslot.port:subport. More typically, the source has the two-part, short-hand form slot.line or slot.port. If the source is an AXSM, the format is slot.line.
For a BITS clock, the format is slot.port. The slot for a BITS clock is 7. The logical port is always 35 or 36. Port 35 refers to the upper external clock connector, and port 36 refers to the lower connector.
Clock Status
The status of a particular clock source can be one of the following:
•
(If the status is "ok," then the Reason field shows "okay." If the status is "ok," the reason for the status change described in the section, "Reason for Status Change," is not important.)•
•
•
Reason for Status Change
The reasons that clock status can change are numerous. The dspclksrcs command displays a Reason field for both the primary and the secondary clock source. The reason can include the first-time, user-specification of the clock source. The reason strings and their meaning appear in Table 9-3. Additional information about "okay" and the locking process follows.
When you configure a new clock source or the current clock source changes due to any reason, the software goes through the process of validating the new, current clock source again. (For example, the reasons other than direct user-configuration can be: the previous clock source goes out of lock or a resync of the clock sources takes place due to a switch-over or a rebuild.) This validation process takes the current clock source through the following states:
•
•
•
During these states, the node is already using the new clock source as the synchronizing source.
You might also see these states—in the sequence previously listed—if the current clock source was momentarily lost because it drifted out of the lockable range for either the frequency or the phase. In such a case, the software goes through one more round of trying to confirm that the current clock source is lockable before it declares a clock source to be unlockable. If the software finds that, even after this repeated attempt, that the clock source is not coming back within the lockable range, it declares the clock source as unlockable and proceeds to use the next clock in the hierarchy (of primary, secondary, internal oscillator) as the current clock source. The exception to this final validation scenario occurs if the current clock source is the internal oscillator in either the free running mode or the hold-over mode: in this case, the software omits this final validation attempt because no other clocks sources within a clock hierarchy are available.
Revertive Behavior
For information on revertive behavior, see the cnfclksrc description.
Syntax
dspclksrcs
Related Commands
cnfclksrc, delclksrc, dspclkalms
Attributes
Example
Display the clocks. The display shows that both the primary and secondary clocks are good. They are sourced at lines 2 and 3 of the AXSM in slot 6. Also, the primary source is providing the active clock, and the system is configured for revertive behavior. The primary and secondary clock reasons are okay.
pinnacle.7.PXM.a> dspclksrcsPrimary clock type: genericPrimary clock source: 6.2Primary clock status: goodPrimary clock reason: okaySecondary clock type: genericSecondary clock source: 6.3Secondary clock status: goodSecondary clock reason: okayActive clock: primarysource switchover mode: revertiveDisplay information about the clock sources. This example shows a BITS clock for the primary source with revertive mode enabled.
pop20one.7.PXM.a > dspclksrcsPrimary clock type: bits t1Primary clock source: 7.35Primary clock status: okPrimary clock reason: okaySecondary clock type: genericSecondary clock source: 9:1.1:1Secondary clock status: okSecondary clock reason: okayActive clock: primarysource switchover mode: revertivedspcon
Display Connection
Display information about an SPVC. The contents of the display on the AXSM and the PXM45 differ slightly. On both cards, the dspcon output appears in sections to make the information easier to sort.
Most of the information in the dspcon output comes from addcon execution. See the addcon description for more information. Also, executing cnfpnni-intf can affect the dspcon output.
Cards on Which This Command Runs
AXSM, AXSM-E, PXM45
Display Connection on the PXM45
On the PXM45, dspcon shows the following connection identifiers:
•
The provisioning parameters in the display consist of the following:
•
•
•
•
•
•
•
The default cost-per-link is 5040, so if a particular service type uses the default and a route consists of 4 links, the Routing Cost is 20160. If the dspspvc display shows that Max Cost is -1, no limit was specified through cnfpnni-intf, and the resulting Routing Cost is 0.•
The Traffic Parameters section shows the standard parameters PCR, SCR, and CDV in the receive and transmit directions.
Display Connection on the AXSM
On the AXSM, dspcon shows the following connection identifiers:
•
The provisioning parameters in the display show:
•
•
•
•
•
The traffic management parameters consist of:
•
These other fields also pertain to connection integrity:
•
•
•
The dspcon command requires a unique connection identifier. If you do not have the information to identify a connection, execute dspcons. On the AXSM, dspcons identifies all the connections on the AXSM. On the PXM45, dspcons identifies all the connections on the node. (See dspcons description).
Display Connection on the AXSM-E
The display output on the AXSM-E also displays RDI (Remote Defect Indication) information at the ATM Layer through the OAM mechanism in Ingress and Egress directions.
AXSM and AXSM-E Syntax
dspcon <ifNum> <vpi> <vci>
PXM45 Syntax
dspcon <portid> <vpi> <vci>
Syntax Description
Related Commands
addcon, dspcons, cnfcon
PXM45 Attributes
AXSM and AXSM-E Attributes
Examples
Display connection 5 31 63000 on the current AXSM.
MGX8850.1.AXSM.a > dspcon 5 31 63000--------------------------------------------------------------------------Local : NSAP Address port vpi vci(M) 4700918100000000107BE92F3F00000101180500 1.01.05 31 63000Remote : NSAP Address port vpi vci(S) 4700918100000000107BE92F3F00000101180500 1.01.05 3201 100--------------------------------------------------------------------------Conn. Type : VCC Admn Status : ADMN-UPService Type : cbr1 Oper Status : FAILController : 2--------------------------------------------------------------------------Local PCR : 10000 Remote PCR : 1000Local SCR : N/A Remote SCR : N/ALocal CDV : -1 Remote CDV : -1Local CTD : -1 Remote CTD : -1Local MBS : N/A Remote MBS : N/ALocal CDVT : -1 Remote CDVT : -1Admin weight : -1 Frame discard: N--------------------------------------------------------------------------OAM CC Config :DISABLED Statistics : DISABLED--------------------------------------------------------------------------Loopback Type :No Lpbk | Dir:N/A | Status: No Lpbk | RTD: 0 usOn the CLI of the PXM45, display connection 20 100 on 11:1.1:2.
Unknown.7.PXM.a > dspcon 11:1.1:2 20 100Port Vpi Vci Owner State-------------------------------------------------------------------------Local 11:1.1:2 20.100 MASTER FAILAddress: 47.00918100000000107b65f33d.0000010b1802.00Remote 11:1.1:2 10.100 SLAVE FAILAddress: 47.00918100000000107b65f33d.0000010b1802.00-------------------- Provisioning Parameters --------------------Connection Type: VCC Cast Type: Point-to-PointService Category: CBR Conformance: CBR.1Bearer Class: BCOB-XLast Fail Cause: SPVC Established Attempts: 0Continuity Check: Disabled Frame Discard: DisabledL-Utils: 100 R-Utils: 100 Max Cost: -1 Routing Cost: 0---------- Traffic Parameters ----------Tx PCR: 50 Rx PCR: 50Tx CDV: N/A Rx CDV: N/ATx CTD: N/A Rx CTD: N/ADisplay information for vpi/vci 10 100 on port ID 1:1.1:1. In this case, port ID and remote and local NSAP addresses are the same, so the connection is a DAXCON. Also, the Max Cost is -1. The Max Cost of -1 means no cost-per-link was specified for UBR service, and therefore the Routing Cost is 0.
node19.8.PXM.a > dspcon 1:1.1:1 10 100Port Vpi Vci Owner State-------------------------------------------------------------------------Local 1:1.1:1 10.100 SLAVE OKAddress: 47.00918100000000001a53c82d.000001011801.00Remote 1:1.1:1 11.101 MASTER OKAddress: 47.00918100000000001a53c82d.000001011801.00-------------------- Provisioning Parameters --------------------Connection Type: VCC Cast Type: Point-to-PointService Category: UBR Conformance: UBR.1Bearer Class: BCOB-XLast Fail Cause: SPVC Established Attempts: 0Continuity Check: Disabled Frame Discard: DisabledL-Utils: 100 R-Utils: 100 Max Cost: -1 Routing Cost: 0---------- Traffic Parameters ----------Tx PCR: 14 Rx PCR: 14Tx SCR: 3 Rx SCR: 3Tx MBS: 1 Rx MBS: 1Tx CDVT: -1 Rx CDVT: -1Tx CDV: N/A Rx CDV: N/ATx CTD: N/A Rx CTD: N/ADisplay output for AXSM-E, port 1, vpi 10, vci 100.
MGX8850.6.AXSME.a > dspcon 1 10 100--------------------------------------------------------------------------Local : NSAP Address vpi vci(S) 47009181000000002A231F3C4A00000106180100 10 100Remote : NSAP Address vpi vci(M) 47009181000000002A231F3C4A00000106180200 10 100--------------------------------------------------------------------------Conn. Type : VCC Admn Status : ADMN-UPService Type : cbr1 Oper Status : OKController : 2 Record # : 0--------------------------------------------------------------------------Local PCR : 1000 Remote PCR : 1000Local SCR : N/A Remote SCR : N/ALocal CDV : N/A Remote CDV : N/ALocal CTD : N/A Remote CTD : N/ALocal MBS : N/A Remote MBS : N/AMax Cost : N/A Frame discard: NLocal CDVT : 250000 OAM segment : ENABLED--------------------------------------------------------------------------OAM CC Config : DISABLED Statistics : DISABLED--------------------------------------------------------------------------Loopback Type : No Lpbk | Dir: N/A | Status: No Lpbk | RTD: 0us----------------------------------------------------------------------------------------------------------------------------------------------------Port side Tx : normal Swth side Tx : AISPort side Rx : normal Swth side Rx : normal--------------------------------------------------------------------------Ing-E2E-AIS ING-SEG-AIS Ing-E2E-RDI Ing-SEG-RDINO NO NO NO--------------------------------------------------------------------------Egr-E2E-AIS Egr-SEG-AIS Egr-E2E-RDI Egr-SEG-RDIYES NO NO NO--------------------------------------------------------------------------Ing-E2E-CCFAIL Ing-SEG-CCFAIL Egr-E2E-CCFail Egr-SEG-CCFail--- --- --- -----------------------------------------------------------------------------CONDITIONED IfFail Mismatch LMI-ABITNO YES NO NO--------------------------------------------------------------------------dspconalmcnts
Display Connection Alarm Counts—display connection alarms on interfaces by alarm cause.
The dspconalmcnts command lists errored connections on the logical interfaces on the card. It lists by alarm cause. The causes are:
•
•
•
•
•
•
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspconalmcnts
Syntax Description
This command takes no parameters.
Related Commands
dspconalms
Attributes
Example
Display the connection alarms by alarm cause.
M8850_SF.1.AXSM.a > dspconalmcnts************************************************************************************** CONNECTIONS IN ALARM PER INTERFACE (BY ALM CAUSE)**************************************************************************************IF# IfState #Condn #IngAlm #EgrAlm #CCFail #ifFail #mismatch #Abit-- ------- ------ ------- ------- ------- ------- --------- -----01 ACTV 00000 00000 00000 00000 00000 00000 0000002 ACTV 00000 00000 00000 00000 00000 00000 0000003 ACTV 00000 00000 00000 00000 00000 00000 00000******************** SUMMARY ALARM COUNT FOR THE CARD *******************#Condn #IngAlm #EgrAlm #CCFail #ifFail #mismatch #abit000000 000000 000000 000000 000000 000000 000000dspconalms
Display Connection Alarms—display connection alarms on interfaces by alarm severity.
Use the dspconalms command to display connection alarms. The command lists alarms by port and shows instances by the severities of critical, major, and minor alarms. The display also shows which types of failures constitute each of these severities.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspconalms
Syntax Description
This command takes no parameters.
Related Commands
dspconalmcnts
Attributes
Example
Display connection alarms. This card has three logical interfaces but no connection alarms.
M8850_SF.1.AXSM.a > dspconalms*********************************************************************** CONNECTIONS IN ALARM PER INTERFACE (BY SEVERITY) ***********************************************************************IF# IfState #Critical #Major #Minor-- ------- --------- ------ ------01 ACTV 00000 00000 0000002 ACTV 00000 00000 0000003 ACTV 00000 00000 00000****************************************************************************** PRESENT ALARM SEVERITY CONFIGURATION **************************************************************************CRITICAL: MismatchMAJOR : Condn CCFailMINOR : IngAlm EgrAlm IfFail AbitM8850_SF.1.AXSM.a >dspconinfo
Display Summaries of Connection Information—display general information about SPVCs.
The dspconinfo runs on the PXM45 and lists the total number SPVCs on each PNNI port on the switch. The default operation of the command is to show all SPVCs or SPVPs, With the optional parameters, you can specify one or more types of information to display.
The display shows:
•
•
•
•
•
Note that dspconinfo checks for the down state at the master end of the connection (status at the slave endpoint is failed). See also the descriptions for dncon and dspcon.
Cards on Which This Command Runs
PXM45
Syntax
dspconinfo
[-port portid] [-detail {true | false}] [-owner {master | slav] -sc {cbr | rtvbr | nrtvbr | abr | ubr}Syntax Description
-port
Identifies a PNNI physical port. The format for portid is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.
-detail
Determines whether the display contains information for all interfaces and slots or just slots. Type "true" after the keyword for all interfaces and slots. Type "false" for just slots.
Default: true
-owner
Lets you specify the endpoint of the connection. Type "master" or "slave."
-sc
Directs the command to display connections of a particular service type. Type one of the following after the keyword: cbr, nrtvbr, rtvbr, abr, or ubr.
Default: no default
Related Commands
None
Attributes
Examples
Display the SPVC summaries on the switch with the following conditions:
•
•
•
•
•
atlanta.7.PXM.a > dspconinfoLocal Port #Active #Failed #Down #Total-----------------------------------------------------------5:1.2:2 13 0 0 13atlanta.7.PXM.a > dspconinfo -sc ubrLocal Port #Active #Failed #Down #Total-----------------------------------------------------------5:1.2:2 2 0 0 2atlanta.7.PXM.a > dspconinfo -port 5:1.2:2Local Port #Active #Failed #Down #Total-----------------------------------------------------------5:1.2:2 13 0 0 13atlanta.7.PXM.a > dspconinfo -detail falseLocal Slot #Active #Failed #Down #Total-----------------------------------------------------------5 13 0 0 13atlanta.7.PXM.a > dspconinfo -owner slaveLocal Port #Active #Failed #Down #Total-----------------------------------------------------------5:1.2:2 0 0 0 0dspconload
Display Connection Load—display the number of cells actually traversing the ingress and egress.
The dspconload command lets you see the current load on a connection. With the statistics provided by dspconload, you can determine whether the current load on the connection suggests a modification to the connection or possible troubleshooting.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspconload <ifNum> <vpi> <vci>
Related Commands
dspcons, dspcon, dspload
Attributes
AXSM Example
Display the load on the connection with a VPI and VCI of 101 and 101, respectively, on logical port 3. In this case, no traffic currently exists on the connection.
MGX8850.10.AXSM.a > dspconload 3 101 101Getting the stats. Please wait ...Ingress EgressCell rate (cps) : 0 0AXSM-E Example
Display the load on the connection with a VPI and VCI of 10 and 100, respectively, on logical port 1.
MGX8850.6.AXSME.a > dspconload 1 10 100Ingress Egress-------------------------------------- --------------------------------------All non-compliant cells : 0CLP1 non-compliant : 0CLP0 non-compliant : 0CLP0 -> CLP1 : 0Cells from port(Before policing) : 999 Cells to port : 999CLP0 from port : 999 CLP0 to port : 999CLP1 from port : 0 CLP1 to port : 0EOF from port : 0 EOF to port : 0EFCI1 from port : 0 EFCI1 to port : 0RM to port : 0Cells to network : 999 Cells from network : 999CLP0 to network : 999 CLP0 from network : 999CLP1 to network : 0 CLP1 from network : 0EFCI1 to network : 0 EFCI1 from network : 0Cells discarded in qe : 0 Cells discarded in qe : 0CLP0 discarded in qe : 0 CLP0 discarded in qe : 0CLP1 discarded in qe : 0 CLP1 discarded in qe : 0EOF discarded in qe : 0EFCI1 discarded in qe : 0VC queue depth : 0 VC queue depth : 0ACR (Valid for WFQ conns) : 1 ACR (Valid for WFQ conns) : 1OAM from port : 0 OAM to port : 0RM from port : 0RM to network : 0 RM from network : 0OAM to network : 0 OAM from network : 0OAM discarded in qe : 0 OAM discarded in qe : 0EFCI1 discarded in qe : 0RM discarded in qe : 0 RM discarded in qe :dspcons
Display Connections—display basic information for all connections.
The default usage of dspcons uses no parameters and causes all available information for the connections to appear. To narrow the scope of the output, use one or more optional parameters.
The dspcons command runs on the CLI of either the AXSM or the PXM45. The set of optional parameters and the output are different on these cards. (See Syntax Description for the card-specific parameters.) On the AXSM, the columns at the head of the information fields are:
When you execute dspcons on the CLI of the PXM45, the output shows:
Cards on Which This Command Runs
PXM45, AXSM, AXSM-E
PXM45 Syntax
dspcons [-port portid] [-vpi starting-vpi] [-vci starting vci] [-state {fail | ais | abit | ok | down}]
[-owner {master | slave}]PXM45 Syntax Description
-port
Identifies a PNNI physical port. The format for portid is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.
-vpi
The VPI of the connection that you would like to serve as the starting connection in the display.
-vci
The VPI of the connection that you would like to serve as the starting connection in the display.
-state
A specific connection state. The display shows only the connections with the state you specify. Note that on the PXM45, you must spell out the entire state keyword. The keywords for specifying a state are
failed—only failed connections
ais—connections with alarm indication signal (AIS) set
abit—connections on which an A-bit error has occurred
ok—connections with no problems
down—connections that are administratively down because a user has executed dncon to down the connection
-owner
Specifies connections where the local endpoint is either master or slave.
AXSM Syntax
dspcons [-conn <conn id>] [-filt <filter options>] [-if <intf no>] [-vpi <vpi filter>] [-vci <vci filter>]
AXSM Syntax Description
AXSM-E Syntax
dspcons [-conn <conn id>] [-filt <filter options>]
AXSM-E Syntax Description
Related Commands
dspcon, addcon, cnfcon, delcon, dncon, upcon
Attributes
PXM45 Example
Display all connections by entering dspcons on the CLI of the PXM45.
MGX8850.7.PXM.a > dspconsLocal Port Vpi.Vci Remote Port Vpi.Vci State Owner----------------------------+-----------------------------+-------+------3:1.1:1 20 0 6:1.1:1 20 0 OK MASTERLocal Addr: 47.00918100000000107b65f33d.000001031801.00Remote Addr: 47.00918100000000107b65f33d.000001061801.005:1.1:1 100 100 5:1.1:1 100 200 OK SLAVELocal Addr: 47.00918100000000107b65f33d.000001051801.00Remote Addr: 47.00918100000000107b65f33d.000001051801.005:1.1:1 100 200 5:1.1:1 100 100 OK MASTERLocal Addr: 47.00918100000000107b65f33d.000001051801.00Remote Addr: 47.00918100000000107b65f33d.000001051801.006:1.1:1 20 0 3:1.1:1 20 0 OK SLAVELocal Addr: 47.00918100000000107b65f33d.000001061801.00Remote Addr: 47.00918100000000107b65f33d.000001031801.006:1.1:1 100 100 6:1.1:1 100 200 OK SLAVELocal Addr: 47.00918100000000107b65f33d.000001061801.00Remote Addr: 47.00918100000000107b65f33d.000001061801.006:1.1:1 100 200 6:1.1:1 100 100 OK MASTERLocal Addr: 47.00918100000000107b65f33d.000001061801.00Remote Addr: 47.00918100000000107b65f33d.000001061801.006:1.1:1 200 100 6:2.1:3 200 200 OK SLAVE6:1.1:1 100 200 6:1.1:1 100 100 OK MASTERLocal Addr: 47.00918100000000107b65f33d.000001061801.00Remote Addr: 47.00918100000000107b65f33d.000001061801.006:1.1:1 200 100 6:2.1:3 200 200 OK SLAVELocal Addr: 47.00918100000000107b65f33d.000001061801.00Remote Addr: 47.00918100000000107b65f33d.000001061803.006:2.1:3 200 200 6:1.1:1 200 100 OK MASTERLocal Addr: 47.00918100000000107b65f33d.000001061803.00Remote Addr: 47.00918100000000107b65f33d.000001061801.009:1.3:3 10 100 Routed 0 0 FAIL SLAVELocal Addr: 47.00918100000000107b65f33d.000001091803.00Remote Addr: 00.000000000000000000000000.000000000000.0011:1.1:2 10 100 11:1.1:2 20 100 OK SLAVELocal Addr: 47.00918100000000107b65f33d.0000010b1802.00Remote Addr: 47.00918100000000107b65f33d.0000010b1802.00Local Port Vpi.Vci Remote Port Vpi.Vci State Owner----------------------------+-----------------------------+-------+------11:1.1:2 20 100 11:1.1:2 10 100 OK MASTERLocal Addr: 47.00918100000000107b65f33d.0000010b1802.00Remote Addr: 47.00918100000000107b65f33d.0000010b1802.00AXSM Example
Display all connections on the current AXSM. In this example, only one connection exists. Master and slave endpoints are shown.
GN.6.AXSM.a > dspconsrecord Identifier Type SrvcType M/S Upld Admn Alarm------ ---------- ---- -------- --- ---- ---- -----0 01.0010.00100 VCC cbr1 S 010c7953 UP none1 04.0020.00100 VCC cbr1 M 010c7964 UP noneAXSM-E Example
Display all connections on the current AXSM-E.
MGX8850.6.AXSME.a > dspconsrecord Identifier Type SrvcType M/S Upld Admn Alarm------ ---------- ---- -------- --- ---- ---- -----0 01 0010 00100 VCC cbr1 S 01b945d2 UP multiple1 02 0010 00100 VCC cbr1 M 01b945f2 UP E-AisRdidspcons-dbg
Display Connections-Debug—shows whether the SPVC log is enabled or disabled.
The dspcons-dbg command shows whether the SPVC log is enabled. The dbgcon command lets you enable or disable this log.
Cards on Which This Command Runs
PXM45
Syntax
dspcons-dbg
Syntax Description
This command takes no parameters.
Related Commands
dbgcon
Attributes
Examples
Determine whether SPVC logging is enabled. The output shows that the log is disabled.
MGX8850.8.PXM.a > dspcons-dbgGlobal SPVC Event Log Status: Disabledspcontrollers
Display Controllers
Displays all controllers that have been added through the addcontroller command.
Cards on Which This Command Runs
PXM45
Syntax
dspcontrollers
Syntax Description
This command takes no parameters.
Related Commands
addcontroller, delcontroller
Attributes
Example
Display all controller. In this example, the switch has only one controller—PNNI. The display also shows that the controller is internal (slot 7) and has the optional, user-specified name PNNITWO. Apart from controller information, the display shows that no shelf alarms exist.
M8850_NY.7.PXM.a > dspcontrollersM8850_NY System Rev: 02.01 Dec. 22, 2001 22:46:53 PSTMGX8850 Node Alarm: MAJORNumber of Controllers: 1Controller Name: PNNI ControllerController Id: 2Controller Location: InternalController Type: PNNIController Logical Slot: 7Controller Bay Number: 0Controller Line Number: 0Controller VPI: 0Controller VCI: 0Controller In Alarm: NOController Error:M8850_NY.7.PXM.a >dspdevalms
Display Device Alarms—display severity of crossbar alarms.
The dspdevalms command shows whether a crossbar alarm is minor, major, or critical. The display shows status on both the active and standby PXM45 or all the XM60s.
For fault isolation after you execute dspdevalms, you can check the possible errors (illustrated in the example). The following is a top-down sequence of commands related to switch planes (or ASICs):
1.
2.
3.
4.
5.
Cards on Which This Command Runs
PXM45
Syntax
dspdevalms <device name> [-pslot <slot no>]
dspdevalms <device name> [-xslot <xbar slot>] [-pl <plane No>]
Syntax Description
Related Commands
dspswalms, dspdeverr, dspdeverrhist, dspxbarerrthresh, clrxbaralms
Attributes
Example (8850)
Display switching device alarms for physical slot 7 and switch ASIC 0. Thereafter, display switching device alarms for crossbar slot 7, switch ASIC 0.
M8850_NY.7.PXM.a > dspdevalms XBARCORE -pslot 7 -pl 0M8850_NY System Rev: 02.01 Dec. 09, 2001 23:31:46 PSTMGX8850 Node Alarm: CRITICALXBAR CORE ERROR ALARM INFO FOR SLOT: 7FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par----- ---- ---- ---- ---- ---- ---- ---- ---- ---7/0 -- -- -- -- -- -- -- -- --7/1 -- -- -- -- -- -- -- -- --7/2 -- -- -- -- -- -- -- -- --8/0 -- -- -- -- -- -- -- -- --8/1 -- -- -- -- -- -- -- -- --8/2 -- -- -- -- -- -- -- -- --XBAR CORE ERROR ALARM INFO FOR SLOT: 7FabricSlot/ SFrame SFrame ACP SevPlane Tick Lock Addr Summ.----- ---- ---- --- ----7/0 -- -- -- --7/1 -- -- -- --7/2 -- -- -- --8/0 -- -- -- --8/1 -- -- -- --8/2 -- -- -- --M8850_NY.7.PXM.a > dspdevalms XBARCORE -xslot 7 -pl 0M8850_NY System Rev: 02.01 Dec. 10, 2001 15:23:29 PSTMGX8850 Node Alarm: MAJORXBAR CORE ERROR ALARM INFO:Fabric Slot No: 7 Xbar Plane No: 0Loss Rx Rx Xmit Hdr Pload Slot Slot BPSlot Sync Cv Disp Par CRC CRC Remap Recur Par----- ---- ---- ---- ---- ---- ---- ---- ---- ---1 -- -- -- -- -- -- -- -- --2 -- -- -- -- -- -- -- -- --3 -- -- -- -- -- -- -- -- --4 -- -- -- -- -- -- -- -- --5 -- -- -- -- -- -- -- -- --6 -- -- -- -- -- -- -- -- --7 -- -- -- -- -- -- -- -- --8 -- -- -- -- -- -- -- -- --9 -- -- -- -- -- -- -- -- --10 -- -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- -- --M8850_NY System Rev: 02.01 Dec. 10, 2001 15:23:29 PSTMGX8850 Node Alarm: MAJORXBAR CORE ERROR ALARM INFO:Fabric Slot No: 7 Xbar Plane No: 0SFrame SFrame ACP SevSlot Tick Lock Addr Summ.----- ---- ---- ---- ----1 -- -- -- --2 -- -- -- --3 -- -- -- --4 -- -- -- --5 -- -- -- --6 -- -- -- --7 -- -- -- --8 -- -- -- --9 -- -- -- --10 -- -- -- --11 -- -- -- --12 -- -- -- --13 -- -- -- --14 -- -- -- --M8850_NY.7.PXM.a >Example (8950)
Display switch device alarms for physical slot 1. At the end of the display, critical alarms are indicated for the XM60 is slot 26. Use the command with the -xbar parameter to investigate these alarms. For this second action, the command entry is as follows:
dspdevalms XBARCORE -xslot 26 -pl 3
Thereafter, use dspdeverr for the physical slot and the crossbar slot. The displays show a bad link between slot 1 only and switch ASIC 3 on the XM60 in slot 26.
M8950_DC.7.PXM.a > dspdevalms XBARCORE -pslot 1M8950_DC System Rev: 02.01 Dec. 15, 2001 18:39:30 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE ERROR ALARM INFO FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par----- ---- ---- ---- ---- ---- ---- ---- ---- ---9/0 -- -- -- -- -- -- -- -- --9/1 -- -- -- -- -- -- -- -- --9/2 -- -- -- -- -- -- -- -- --9/3 -- -- -- -- -- -- -- -- --10/0 -- -- -- -- -- -- -- -- --10/1 -- -- -- -- -- -- -- -- --10/2 -- -- -- -- -- -- -- -- --10/3 -- -- -- -- -- -- -- -- --M8950_DC System Rev: 02.01 Dec. 15, 2001 18:39:30 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE ERROR ALARM INFO FOR SLOT: 1FabricSlot/ SFrame SFrame ACP SevPlane Tick Lock Addr Summ.----- ---- ---- --- ----9/0 -- -- -- --9/1 -- -- -- --9/2 -- -- -- --9/3 -- -- -- --10/0 -- -- -- --10/1 -- -- -- --10/2 -- -- -- --10/3 -- -- -- --25/0 -- -- -- -- -- -- -- -- --25/1 -- -- -- -- -- -- -- -- --25/2 -- -- -- -- -- -- -- -- --25/3 -- -- -- -- -- -- -- -- --26/0 -- -- -- -- -- -- -- -- --26/1 -- -- -- -- -- -- -- -- --26/2 -- -- -- -- -- -- -- -- --26/3 Maj Crit Crit -- Crit Crit -- -- --M8950_DC System Rev: 02.01 Dec. 15, 2001 18:39:30 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE ERROR ALARM INFO FOR SLOT: 1FabricSlot/ SFrame SFrame ACP SevPlane Tick Lock Addr Summ.----- ---- ---- --- ----25/0 -- -- -- --25/1 -- -- -- --25/2 -- -- -- --25/3 -- -- -- --26/0 -- -- -- --26/1 -- -- -- --26/2 -- -- -- --26/3 -- -- -- CritM8950_DC.7.PXM.a > dspdevalms XBARCORE -xslot 26 -pl 3M8950_DC System Rev: 02.01 Dec. 15, 2001 18:43:51 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE ERROR ALARM INFO:Fabric Slot No: 26 Xbar Plane No: 3Loss Rx Rx Xmit Hdr Pload Slot Slot BPSlot Sync Cv Disp Par CRC CRC Remap Recur Par----- ---- ---- ---- ---- ---- ---- ---- ---- ---1 Maj Crit Crit -- Crit Crit -- -- --2 -- -- -- -- -- -- -- -- --3 -- -- -- -- -- -- -- -- --4 -- -- -- -- -- -- -- -- --5 -- -- -- -- -- -- -- -- --6 -- -- -- -- -- -- -- -- --7 -- -- -- -- -- -- -- -- --8 -- -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- -- --15 -- -- -- -- -- -- -- -- --16 -- -- -- -- -- -- -- -- --XBAR CORE ERROR ALARM INFO:Fabric Slot No: 26 Xbar Plane No: 3SFrame SFrame ACP SevSlot Tick Lock Addr Summ.----- ---- ---- ---- ----1 -- -- -- Crit2 -- -- -- --3 -- -- -- --4 -- -- -- --5 -- -- -- --6 -- -- -- --7 -- -- -- --8 -- -- -- --11 -- -- -- --12 -- -- -- --13 -- -- -- --14 -- -- -- --15 -- -- -- --16 -- -- -- --M8950_DC.7.PXM.a > dspdeverr XBARCORE -pslot 1M8950_DC System Rev: 02.01 Dec. 15, 2001 18:38:56 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------9/0 0 0 0 0 0 0 0 0 09/1 0 0 0 0 0 0 0 0 09/2 0 0 0 0 0 0 0 0 09/3 0 0 0 0 0 0 0 0 010/0 0 0 0 0 0 0 0 0 010/1 0 0 0 0 0 0 0 0 010/2 0 0 0 0 0 0 0 0 010/3 0 0 0 0 0 0 0 0 0XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----9/0 0 0 09/1 0 0 09/2 0 0 09/3 0 0 010/0 0 0 010/1 0 0 010/2 0 0 010/3 0 0 0MGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------25/0 0 0 0 0 0 0 0 0 025/1 0 0 0 0 0 0 0 0 025/2 0 0 0 0 0 0 0 0 025/3 0 0 0 0 0 0 0 0 026/0 0 0 0 0 0 0 0 0 026/1 0 0 0 0 0 0 0 0 026/2 0 0 0 0 0 0 0 0 026/3 220 3300 3300 0 3300 3300 0 0 0M8950_DC System Rev: 02.01 Dec. 15, 2001 18:38:56 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----25/0 0 0 025/1 0 0 025/2 0 0 025/3 0 0 026/0 0 0 026/1 0 0 026/2 0 0 026/3 0 0 0M8950_DC.7.PXM.a > dspdeverr XBARCORE -xslot 26 -pl 3M8950_DC System Rev: 02.01 Dec. 15, 2001 18:45:43 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT :Fabric Slot No: 26 Xbar Plane No: 3Loss Rx Rx Xmit Hdr Pload Slot Slot BPSlot Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------1 220 3300 3300 0 3300 3300 0 0 02 -- -- -- -- -- -- -- -- --3 -- -- -- -- -- -- -- -- --4 -- -- -- -- -- -- -- -- --5 0 0 0 0 0 0 0 0 06 -- -- -- -- -- -- -- -- --7 0 0 0 0 0 0 0 0 08 -- -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- -- --15 -- -- -- -- -- -- -- -- --16 -- -- -- -- -- -- -- -- --XBAR CORE CURRENT ERROR COUNT :Fabric Slot No: 26 Xbar Plane No: 3Slot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----1 0 0 02 -- -- --3 -- -- --4 -- -- --5 0 0 06 -- -- --7 0 0 08 -- -- --11 -- -- --12 -- -- --13 -- -- --14 -- -- --15 -- -- --16 -- -- --M8950_DC.7.PXM.a >dspdeverr
Display Device Errors—display current errors related to the switching fabric.
The dspdeverr command shows current alarms for the switch planes. The errors can be isolated to a specific link or the entire switch plane. (A link is the hardware path between the switch plane and the recipient card's bus transceiver.) Most errors result in the shutdown of only a link. Two of the three plane-based errors shut down the entire switch plane. Also, the error r types can be
Note
Cards on Which This Command Runs
PXM45
Syntax
dspdeverr <device name> [-pslot <slot no>]
dspdeverr <device name> [-xslot <xbar slot>] [-pl <plane No>]
Syntax Description
Related Commands
dspdevalms, dspdeverrhist, cnfxbarerrthresh, dspxbarerrthresh
Attributes
Example
Do the following sequence of tasks:
1.
2.
3.
M8850_NY.7.PXM.a > dspdeverr XBARCORE -pslot *M8850_NY System Rev: 02.01 Dec. 25, 2001 21:17:06 PSTMGX8850 Node Alarm: MAJORXBAR CORE CURRENT ERROR COUNTERS SUMMARYFabric Slot / PlaneSlot 7/0 7/1 7/2 8/0 8/1 8/2----- ------ ------ ------ ------ ------ ------01 0 0 0 0 0 002 0 0 0 0 0 003 0 0 0 76 68 7604 -- -- -- -- -- --05 0 0 0 0 0 006 0 0 0 0 0 007 0 0 0 0 0 008 0 0 0 0 0 009 -- -- -- -- -- --10 -- -- -- -- -- --11 -- -- -- -- -- --12 -- -- -- -- -- --13 -- -- -- -- -- --14 -- -- -- -- -- --M8850_NY.7.PXM.a > dspdeverr XBARCORE -pslot 3M8850_NY System Rev: 02.01 Dec. 24, 2001 22:49:24 PSTMGX8850 Node Alarm: MAJORXBAR CORE CURRENT ERROR COUNT FOR SLOT: 3FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------7/0 0 0 0 0 0 0 0 0 07/1 0 0 0 0 0 0 0 0 07/2 0 0 0 0 0 0 0 0 08/0 1 15 15 0 15 15 0 0 158/1 1 15 15 0 15 15 0 0 78/2 1 15 15 0 15 15 0 0 15Type <CR> to continue, Q<CR> to stop:M8850_NY System Rev: 02.01 Dec. 24, 2001 22:49:24 PSTMGX8850 Node Alarm: MAJORXBAR CORE CURRENT ERROR COUNT FOR SLOT: 3FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----7/0 0 0 07/1 0 0 07/2 0 0 08/0 0 0 08/1 0 0 08/2 0 0 0M8850_NY.7.PXM.a > dspdeverr XBARCORE -xslot 8 -pl 2M8850_NY System Rev: 02.01 Dec. 25, 2001 21:40:39 PSTMGX8850 Node Alarm: MAJORXBAR CORE CURRENT ERROR COUNT :Fabric Slot No: 8 Xbar Plane No: 2Loss Rx Rx Xmit Hdr Pload Slot Slot BPSlot Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------1 0 0 0 0 0 0 0 0 02 0 0 0 0 0 0 0 0 03 1 15 15 0 15 15 0 0 154 -- -- -- -- -- -- -- -- --5 0 0 0 0 0 0 0 0 06 0 0 0 0 0 0 0 0 07 0 0 0 0 0 0 0 0 08 0 0 0 0 0 0 0 0 09 -- -- -- -- -- -- -- -- --10 -- -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- -- --Type <CR> to continue, Q<CR> to stop:M8850_NY System Rev: 02.01 Dec. 25, 2001 21:40:39 PSTMGX8850 Node Alarm: MAJORXBAR CORE CURRENT ERROR COUNT :Fabric Slot No: 8 Xbar Plane No: 2Slot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----1 0 0 02 0 0 03 0 0 04 -- -- --5 0 0 06 0 0 07 0 0 08 0 0 09 -- -- --10 -- -- --11 -- -- --12 -- -- --13 -- -- --14 -- -- --M8850_NY.7.PXM.a > dspdeverr XBARCORE -xslot 8M8850_NY System Rev: 02.01 Dec. 24, 2001 22:14:02 PSTMGX8850 Node Alarm: MAJORXBAR CORE CURRENT ERROR COUNT :Fabric Slot No: 8 Xbar Plane No: 0Loss Rx Rx Xmit Hdr Pload Slot Slot BPSlot Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------1 0 0 0 0 0 0 0 0 02 0 0 0 0 0 0 0 0 03 1 15 15 0 15 15 0 0 154 -- -- -- -- -- -- -- -- --5 0 0 0 0 0 0 0 0 06 0 0 0 0 0 0 0 0 07 0 0 0 0 0 0 0 0 08 0 0 0 0 0 0 0 0 09 -- -- -- -- -- -- -- -- --10 -- -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- -- --Type <CR> to continue, Q<CR> to stop:M8850_NY System Rev: 02.01 Dec. 24, 2001 22:14:02 PSTMGX8850 Node Alarm: MAJORXBAR CORE CURRENT ERROR COUNT :Fabric Slot No: 8 Xbar Plane No: 0Slot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----1 0 0 02 0 0 03 0 0 04 -- -- --5 0 0 06 0 0 07 0 0 08 0 0 09 -- -- --10 -- -- --11 -- -- --12 -- -- --13 -- -- --14 -- -- --dspdeverrhist
Display Device Error History—display specific crossbar errors since last reset of a switch card.
The dspdeverrhist command shows numbers of various types of errors on each slot-link. Note that the error can occur anywhere along the path of the ASIC and the hardware on the service module. The types of errors apply to the 60-byte switch frames.
Note
You can see the thresholds for triggering the alarms by using dspxbarerrthresh.
The following types and instances of errors appear by slot number (see example screen):
•
•
•
•
•
•
•
•
Note
A top-down sequence of troubleshooting commands for isolating faults in the switching fabric are:
1.
2.
3.
4.
Cards on Which This Command Runs
PXM45
Syntax
dspdeverrhist <device name> [-pslot <slot no>]
dspdeverrhist <device name> [-xslot <xbar slot>] [-pl <plane no>]
Syntax Description
Related Commands
dspxbar, dspdevalms, dspxbarerrthresh, cnfxbarerrthresh, dspndalms, dspswalms
Attributes
Example
Two screens are necessary to display all error types. Note that the screen display can accommodate only a finite number of errors without being distorted. Therefore, a K for 1000 or an M for 1000000 multiplier may be necessary—not the case in the first example.
Display the physical slot error history for slot 1. The command parameters are XBARCORE -pslot 1. The view of this display is from the card in slot 1 to all the switch planes. The display shows a small number of errors on the switch planes on the backup PXM45. The errors are not the plane-based errors that would shut down the planes entirely (Sframe tick and SFrame lock). That the same variety of errors appear for all three switch planes suggests that the problem is not in the ASICs themselves.
M8850_NY.7.PXM.a > dspdeverrhist XBARCORE -pslot 1M8850_NY System Rev: 02.01 Dec. 21, 2001 23:07:37 PSTMGX8850 Node Alarm: MAJORXBAR CORE HISTORY ERROR COUNT FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------7/0 0 0 0 0 0 0 0 0 07/1 0 0 0 0 0 0 0 0 07/2 0 0 0 0 0 0 0 0 08/0 2 30 30 0 30 30 0 0 218/1 2 30 30 0 30 30 0 0 218/2 2 30 30 0 30 30 0 0 19XBAR CORE HISTORY ERROR COUNT FOR SLOT: 1FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----7/0 0 0 07/1 0 0 07/2 0 0 08/0 0 0 08/1 0 0 08/2 0 0 0Display errors for each card slot addressed by the switch planes in slot 8.
M8850_NY.7.PXM.a > dspdeverrhist XBARCORE -xslot 8M8850_NY System Rev: 02.01 Dec. 21, 2001 23:11:39 PSTMGX8850 Node Alarm: MAJORXBAR CORE HISTORY ERROR COUNT :Fabric Slot No: 8 Xbar Plane No: 0Loss Rx Rx Xmit Hdr Pload Slot Slot BPSlot Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------1 2 30 30 0 30 30 0 0 212 3 45 45 0 45 45 0 0 303 1 15 15 0 15 15 0 0 154 -- -- -- -- -- -- -- -- --5 1 15 15 0 15 15 0 0 156 0 0 0 0 0 0 0 0 07 0 0 0 0 0 0 0 0 08 0 0 0 0 0 0 0 0 09 -- -- -- -- -- -- -- -- --10 -- -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- -- --Type <CR> to continue, Q<CR> to stop:M8850_NY System Rev: 02.01 Dec. 21, 2001 23:11:39 PSTMGX8850 Node Alarm: MAJORXBAR CORE HISTORY ERROR COUNT :Fabric Slot No: 8 Xbar Plane No: 0Slot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----1 0 0 02 0 0 03 0 0 04 -- -- --5 0 0 06 0 0 07 0 0 08 0 0 09 -- -- --10 -- -- --11 -- -- --12 -- -- --13 -- -- --14 -- -- --M8850_NY.7.PXM.a >The dspswalms display shows a critical crossbar core alarm related to slot 1. Run the dspdeverrhist command for physical slot then crossbar slot (see Syntax Description as needed). The alarm type is critical because the number of errors has exceeded the threshold for critical alarms. Note that plane 3 in slot 26 has not shut down because the errors are nether SFrame Tick nor SFrame lock errors—the critical failures that cause the whole plane to be unusable.
M8950_DC.7.PXM.a > dspswalmsXBAR SWITCHING FABRIC ALARMS SUMMARYXbar Core Alarm Xbar Port Alarm Xbar Slot B/W alarmSlot No. Critical Major Minor Critical Major Minor Critical Major Minor------- -------- ----- ----- -------- ----- ----- -------- ----- -----01 1 0 0 0 0 0 0 1 002 -- -- -- -- -- -- -- -- --03 -- -- -- -- -- -- -- -- --04 -- -- -- -- -- -- -- -- --05 0 0 0 0 0 0 0 0 006 -- -- -- -- -- -- -- -- --07 0 0 0 0 0 0 0 0 008 -- -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- -- --15 -- -- -- -- -- -- -- -- --16 -- -- -- -- -- -- -- -- --M8950_DC.7.PXM.a >Note that the screen display can accommodate only a finite number of errors without being distorted. Therefore, a K (for 1000) and M (for 1000000) multiplier may be necessary, as this example shows.M8950_DC.7.PXM.a > dspdeverrhist XBARCORE -pslot 1M8950_DC System Rev: 02.01 Dec. 21, 2001 22:34:30 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE HISTORY ERROR COUNT FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------9/0 0 0 0 0 0 0 0 0 09/1 0 0 0 0 0 0 0 0 09/2 0 0 0 0 0 0 0 0 09/3 0 0 0 0 0 0 0 0 010/0 0 0 0 0 0 0 0 0 010/1 0 0 0 0 0 0 0 0 010/2 0 0 0 0 0 0 0 0 010/3 0 0 0 0 0 0 0 0 0XBAR CORE HISTORY ERROR COUNT FOR SLOT: 1FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----9/0 0 0 09/1 0 0 09/2 0 0 09/3 0 0 010/0 0 0 010/1 0 0 010/2 0 0 010/3 0 0 0Type <CR> to continue, Q<CR> to stop:M8950_DC System Rev: 02.01 Dec. 21, 2001 22:34:30 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE HISTORY ERROR COUNT FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------25/0 0 0 0 0 0 0 0 0 025/1 0 0 0 0 0 0 0 0 025/2 0 0 0 0 0 0 0 0 025/3 0 0 0 0 0 0 0 0 026/0 0 0 0 0 0 0 0 0 026/1 0 0 0 0 0 0 0 0 026/2 0 0 0 0 0 0 0 0 026/3 10275K 154132K 154132K 0 154132K 154132K 0 0 0Type <CR> to continue, Q<CR> to stop:M8950_DC System Rev: 02.01 Dec. 21, 2001 22:34:30 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE HISTORY ERROR COUNT FOR SLOT: 1FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----25/0 0 0 025/1 0 0 025/2 0 0 025/3 0 0 026/0 0 0 026/1 0 0 026/2 0 0 026/3 0 0 0M8950_DC.7.PXM.a > dspdeverrhist XBARCORE -xslot 26 -pl 3M8950_DC System Rev: 02.01 Dec. 21, 2001 22:36:56 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE HISTORY ERROR COUNT :Fabric Slot No: 26 Xbar Plane No: 3Loss Rx Rx Xmit Hdr Pload Slot Slot BPSlot Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------1 10276K 154154K 154154K 0 154154K 154154K 0 0 02 -- -- -- -- -- -- -- -- --3 -- -- -- -- -- -- -- -- --4 -- -- -- -- -- -- -- -- --5 0 0 0 0 0 0 0 0 06 -- -- -- -- -- -- -- -- --7 0 0 0 0 0 0 0 0 08 -- -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- -- --15 -- -- -- -- -- -- -- -- --16 -- -- -- -- -- -- -- -- --XBAR CORE HISTORY ERROR COUNT :Fabric Slot No: 26 Xbar Plane No: 3Slot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----1 0 0 02 -- -- --3 -- -- --4 -- -- --5 0 0 06 -- -- --7 0 0 08 -- -- --11 -- -- --12 -- -- --13 -- -- --14 -- -- --15 -- -- --16 -- -- --M8950_DC.7.PXM.a >dspdiagcnf
Display Diagnostics Configuration
Displays the current diagnostics configuration, such as whether online or offline is enabled, the coverage time, starting time, and the days of the week (SMTWTFS) that the offline diagnostics runs.
Coverage indicates the length of time that the diagnostics will run as follows:
•
•
•
Note
Syntax
dspdiagcnf
Syntax Description
This command takes no parameters.
Cards on Which This Command Runs
PXM45
Related Commands
cnfdiag, cnfdiagall
Attributes
Example
pop20one.7.PXM.a > dspdiagcnfOnline -------------- Offline -------------Slot Enable Enable Coverage StartTime SMTWTFS1 enable enable full 10:30 -M-W-F-2 disable enable full 22:00 -M-W-F-3 enable disable medium 11:15 -M-W-F-4 enable disable light 03:20 -M-W-F-5 enable disable light 14:30 ------S6 disable enable full 12:00 -M-W-F-7 disable enable light 18:00 ------S8 enable enable medium 05:00 -M-W-F-9 enable disable light 04:30 -M-W-F-10 enable disable full 22:00 ------S11 enable disable light 24:15 -M-W-F-12 disable enable full 11:00 ------S13 enable enable light 13:15 -M-W-F-14 enable enable medium 01:00 -M-W-F-15 enable enable full 02:30 -M-W-F-16 disable disable light 00:00 SMTWTFS17 disable disable light 00:00 SMTWTFS18 disable disable light 00:00 SMTWTFS19 disable disable light 00:00 SMTWTFS20 disable disable light 00:00 SMTWTFS21 disable disable light 00:00 SMTWTFS22 disable disable light 00:00 SMTWTFS23 disable disable light 00:00 SMTWTFS24 disable disable light 00:00 SMTWTFS25 disable disable light 00:00 SMTWTFS26 disable disable light 00:00 SMTWTFS27 disable disable light 00:00 SMTWTFS28 disable disable light 00:00 SMTWTFS29 disable disable light 00:00 SMTWTFS30 disable disable light 00:00 SMTWTFS31 disable disable light 00:00 SMTWTFS32 disable disable light 00:00 SMTWTFSdspdiagerr
Display Diagnostics Errors
Displays the current offline or online diagnostics errors.
Cards on Which This Command Runs
PXM45
Syntax
dspdiagerr <online/offline>
Syntax Description
Related Commands
clrdiagerr
Attributes
Example
MGX8850.7.PXM.a > dspdiagerr offlineSlot Date Time Message---- ---- ---- -------1 -- --2 24-Aug 13:35 SAR send failed3 -- --4 -- --5 -- --6 -- --7 -- --8 -- --9 -- --10 -- --11 -- --12 -- --13 18-Aug 03:24 HUMVEE IRQ test failed14 -- --15 -- --16 -- --17 -- --18 -- --19 -- --20 -- --21 -- --22 -- --23 -- --24 -- --25 -- --26 -- --27 -- --28 -- --29 -- --30 -- --31 -- --32 -- --dspdiagstat
Display Diagnostics Statistics
Displays the number of times that the diagnostics has run. The output shows the number of attempts and the number of failures for both offline and online diagnostics.
Note
Syntax
dspdiagstat <slot>
Syntax Description
Cards on Which This Command Runs
PXM45
Related Commands
clrdiagstat
Attributes
Example
pop20two.7.PXM.a > dspdiagstat 7Slot 7 diagnostics statistics:online diag attempted = 0x00000000online diag failed = 0x00000000offline diag attempted = 0x00000000offline diag failed = 0x00000000dspdiagstatus
Display Diagnostics Status
Displays the diagnostics status for each card on the switch. The diagnostics statuses are:
•
•
•
•
Note
Syntax
dspdiagstatus
Syntax Description
This command takes no parameters.
Cards on Which This Command Runs
PXM45
Related Commands
cnfdiag, cnfdiagall
Attributes
Example
pop20one.7.PXM.a > dspdiagstatusSlot State Role1 Ready ACTIVE CARD ROLE2 Ready ACTIVE CARD ROLE3 Offline STANDBY CARD ROLE4 Online ACTIVE CARD ROLE5 Ready ACTIVE CARD ROLE6 Offline STANDBY CARD ROLE7 Ready ACTIVE CARD ROLE8 Online ACTIVE CARD ROLE9 Idle ACTIVE CARD ROLE10 Ready ACTIVE CARD ROLE11 Online ACTIVE CARD ROLE12 Idle ACTIVE CARD ROLE13 Ready ACTIVE CARD ROLE14 Offline STANDBY CARD ROLE15 Idle ACTIVE CARD ROLE16 Idle ACTIVE CARD ROLE17 Idle ACTIVE CARD ROLE18 Idle ACTIVE CARD ROLE19 Idle ACTIVE CARD ROLE20 Idle ACTIVE CARD ROLE21 Idle ACTIVE CARD ROLE22 Idle ACTIVE CARD ROLE23 Idle ACTIVE CARD ROLE24 Idle ACTIVE CARD ROLE25 Idle ACTIVE CARD ROLE26 Idle ACTIVE CARD ROLE27 Idle ACTIVE CARD ROLE28 Idle ACTIVE CARD ROLE29 Idle ACTIVE CARD ROLE30 Idle ACTIVE CARD ROLE31 Idle ACTIVE CARD ROLE32 Idle ACTIVE CARD ROLEdspegrbucketcnt
Display Alarm Counters
Displays selected statistical counters for the specified 15 minute interval (intvl) for all lines and virtual interfaces on the card.
Cards on Which This Command Runs
AXSM-E
Syntax
dspegrbucketcnt <intvl>
Syntax Description
Related Commands
dspingbucketcnt
Attributes
Example
MGX8850.1.10.AXSME.a > dspegrbucketcnt 0Line Total CellsReceived------- ---------------1.1 01.2 01.3 01.4 01.5 01.6 01.7 01.8 02.1 02.2 02.3 02.4 0IfNum Total Cells Total CellsReceived Discarded----- --------------- ---------------1 0 02 0 0dspenvalms
Display Environment Alarms
Display alarms related to the environment of the node. The monitored categories are:
•
•
•
•
•
•
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
•
•
•
The dspenvalms command is part of a hierarchy of troubleshooting commands you can execute on the PXM45. Frequently, dspenvalms follows the higher-level command dspndalms. The dspndalms command shows a variety of alarm types within the switch and helps isolate the problem.
Cards on Which This Command Runs
PXM45
Syntax
dspenvalms [temp] [psu] [fan] [vmon]
Syntax Description
Related Commands
dspndalms, dspcdstatus
Attributes
Examples
Check the temperature.
MGX8850.7.PXM.a > dspenvalms tempMGX8850 System Rev: 02.00 Aug. 06, 2000 18:28:33 GMTMGX8850 Node Alarm: CRITICALENVIRONMENTAL ALARM STATE INFO ^Notification DisabledAlarm Type Unit Threshold DataType Value State---------------- ---- -------------- -------- ---------- -------------Temperature <= 50 Celsius 33 NormalCheck the fans for alarms. The display shows minimal and actual RPMs for each fan. The display shows that the bottom fan tray is missing.
MGX8850.7.PXM.a > dspenvalms fanMGX8850 System Rev: 02.00 Aug. 06, 2000 22:33:08 GMTMGX8850 Node Alarm: CRITICALENVIRONMENTAL ALARM STATE INFO ^Notification DisabledAlarm Type Unit Threshold DataType Value State---------------- ---- -------------- -------- ---------- -------------Top Fan Tray 1 >= 2000 RPM 3504 NormalTop Fan Tray 2 >= 2000 RPM 3498 NormalTop Fan Tray 3 >= 2000 RPM 3576 NormalTop Fan Tray 4 >= 2000 RPM 3492 NormalTop Fan Tray 5 >= 2000 RPM 3474 NormalTop Fan Tray 6 >= 2000 RPM 3564 NormalTop Fan Tray 7 >= 2000 RPM 3462 NormalTop Fan Tray 8 >= 2000 RPM 3366 NormalTop Fan Tray 9 >= 2000 RPM 3444 NormalBottom Fan Tray 1 >= 2000 RPM 0 MissingBottom Fan Tray 2 >= 2000 RPM 0 MissingBottom Fan Tray 3 >= 2000 RPM 0 MissingBottom Fan Tray 4 >= 2000 RPM 0 MissingBottom Fan Tray 5 >= 2000 RPM 0 MissingBottom Fan Tray 6 >= 2000 RPM 0 MissingBottom Fan Tray 7 >= 2000 RPM 0 MissingDisplay all environment alarms for the enclosure by entering dspenvalms with no optional parameters.
MGX8850.7.PXM.a > dspenvalmsMGX8850 System Rev: 02.00 Aug. 06, 2000 18:20:35 GMTMGX8850 Node Alarm: CRITICALENVIRONMENTAL ALARM STATE INFO ^Notification DisabledAlarm Type Unit Threshold DataType Value State---------------- ---- -------------- -------- ---------- -------------Temperature <= 50 Celsius 33 NormalPower Supply A1 none None none NormalPower Supply A2 none None none NormalPower Supply A3 none None none NormalDC Voltage A 42 to 54 VoltsDC 49 NormalPower Supply B1 none None none MissingPower Supply B2 none None none MissingPower Supply B3 none None none MissingDC Voltage B 42 to 54 VoltsDC 0 NormalTop Fan Tray 1 >= 2000 RPM 3504 NormalTop Fan Tray 2 >= 2000 RPM 3498 NormalTop Fan Tray 3 >= 2000 RPM 3576 NormalTop Fan Tray 4 >= 2000 RPM 3498 NormalTop Fan Tray 5 >= 2000 RPM 3480 NormalTop Fan Tray 6 >= 2000 RPM 3570 NormalTop Fan Tray 7 >= 2000 RPM 3468 NormalTop Fan Tray 8 >= 2000 RPM 3366 NormalTop Fan Tray 9 >= 2000 RPM 3444 NormalBottom Fan Tray 1 >= 2000 RPM 0 MissingBottom Fan Tray 2 >= 2000 RPM 0 MissingBottom Fan Tray 3 >= 2000 RPM 0 MissingBottom Fan Tray 4 >= 2000 RPM 0 MissingBottom Fan Tray 5 >= 2000 RPM 0 MissingBottom Fan Tray 6 >= 2000 RPM 0 MissingBottom Fan Tray 7 >= 2000 RPM 0 MissingBottom Fan Tray 8 >= 2000 RPM 0 MissingBottom Fan Tray 9 >= 2000 RPM 0 Missing+5V Input 4.850^ to 5.150^ VoltsDC 5.017 Informational+3.3V Input 3.200^ to 3.400^ VoltsDC 3.259 Informational+2.5V Input 2.425^ to 2.575^ VoltsDC 2.440 InformationalCalibration VDC 0x7e^ to 0x82^ Other 0x80 InformationalDisplay the state of the fans. The display shows that upper and lower fan trays exist in the system—a requirement of the MGX 8950 node.
Jupiter_Lower.7.PXM.a > dspenvalms fanJupiter_Lower System Rev: 02.00 Aug. 06, 2000 22:36:35 GMTJUPITER Node Alarm: NONEENVIRONMENTAL ALARM STATE INFO ^Notification DisabledAlarm Type Unit Threshold DataType Value State---------------- ---- -------------- -------- ---------- -------------Top Fan Tray 1 >= 2000 RPM 3432 NormalTop Fan Tray 2 >= 2000 RPM 3516 NormalTop Fan Tray 3 >= 2000 RPM 3552 NormalTop Fan Tray 4 >= 2000 RPM 3402 NormalTop Fan Tray 5 >= 2000 RPM 3558 NormalTop Fan Tray 6 >= 2000 RPM 3564 NormalTop Fan Tray 7 >= 2000 RPM 3618 NormalTop Fan Tray 8 >= 2000 RPM 3522 NormalTop Fan Tray 9 >= 2000 RPM 3516 NormalBottom Fan Tray 1 >= 2000 RPM 3576 NormalBottom Fan Tray 2 >= 2000 RPM 3558 NormalBottom Fan Tray 3 >= 2000 RPM 3594 NormalBottom Fan Tray 4 >= 2000 RPM 3570 NormalBottom Fan Tray 5 >= 2000 RPM 3492 NormalBottom Fan Tray 6 >= 2000 RPM 3600 NormalBottom Fan Tray 7 >= 2000 RPM 3504 NormalType <CR> to continue, Q<CR> to stop:dsperr
Display Error
Display error message files. The dsperr command is primarily a debug command. Because it displays tasks and system calls, the information is more suitable to developers or others who can use information that is internal to the switch rather than applicable to the network. The information may also be useful to Cisco support personnel.
Cards on Which This Command Runs
PXM45
Syntax
dsperr <-s1 slot> [-en <Error#>] [ -tr {P | L | N}]
Syntax Description
Related Commands
clrerr
Attributes
Example
Display one screen of internal error messages for slot 1. The Error Num is 4849.
pop20two.8.PXM.a > dsperr -sl 1Error Log for Slot 01: Error Num 4849Firmware version: Product Id: 8850Timestamp: 02/20/2001-14:04:42 Node name: pop20twoSection Number 0:Event Logged:01-00266 02/20/2001-14:04:38 SHMA-7-API_BC_REPORTE:04849 tEmFaultMg 0x801d2fc0shmBackCardInsertReport: AppId 0x10005, tId 0x1003d, tName tEmFaultMgr , BayType 1, callerPc 0x80237ff0Section Number 1:Stack Trace:0x80694668 vxTaskEntry +00c: sysTaskSetup+0()0x80159068 sysTaskSetup +0a4: emFaultMgrTaskEntry+0()0x80237950 emFaultMgrTaskEntry +114: ssiIpcComEpWait+0()0x8016313c ssiIpcComEpWait +070: ssi_ipc_mhdlr_receive_loop+0()0x80165e34 ssi_ipc_mhdlr_receive_loop+100: ssi_ipc_mhdlr_msg_receive+0()0x801666a8 ssi_ipc_mhdlr_msg_receive+054: fmFaultMgrTaskHandler+0()0x80237434 fmFaultMgrTaskHandler +0b0: cemaFmPhyProc+0()0x8023bb68 cemaFmPhyProc +068: emHandleHwStatusRpt+0()0x80238e28 emHandleHwStatusRpt +460: cemaFmReportBCInsert+0()0x80237ff0 cemaFmReportBCInsert +440: shmBackCardInsertReport+0()0x801d2fc0 shmBackCardInsertReport +07c: ssiEvent+0()0x80142454 ssiEvent +284: ssiEventMsgReport+0()0x80142840 ssiEventMsgReport +0e4: ssiBramMsgReport+0()0x80142be0 ssiBramMsgReport +0f8: ssiStackTrace+0()--------------dsperrhist
Display Error History—displays a list of errors for a card slot.
The display consists of the following for each record in the history file:
•
•
•
•
The maximum number of entries in the history for a slot is 10. When the 11th error is logged, the switch deletes the oldest entry. Alternatively, you can clear the error history by executing clrerrhist.
If no entries exist in the history, the system returns the message, Nothing is logged.
Cards on Which This Command Runs
PXM45
Syntax
dsperrhist [slot]
Syntax Description
slot
Number of the slot—any slot in the switch. If you do not enter a slot number, the system displays the error history on the active PXM45.
Related Commands
clrerrhist
Attributes
Examples
Display the error history for the current PXM45. This PXM45 resides in slot 8.
jdlenoir.8.PXM.a > dsperrhistLog of Errors and Failures (Slot 8):Entry#--Event#---EventName-------------------------------TimeStamp-----------General:01 0x5006 CBC(Slave) Non-Fatal Minor 11/21/2000-17:55:4902 0x5006 CBC(Slave) Non-Fatal Minor 11/21/2000-17:57:3603 0x5006 CBC(Slave) Non-Fatal Minor 11/21/2000-18:22:47-----------------------------------------------------------------------------Display the error history for the AXSM in slot 6.
jbscott.8.PXM.a > dsperrhist 6Log of Errors and Failures (Slot 6):Entry#--Event#---EventName-------------------------------TimeStamp-----------General:01 0x0005 SHM_CDF_DISCOVER_TMR_POP 11/21/2000-13:49:47-----------------------------------------------------------------------------Display the error history for the AXSM in slot 1.
pop20two.7.PXM.a > dsperrhist 1Log of Errors and Failures (Slot 1):Entry#--Event#---EventName-------------------------------TimeStamp-----------General:01 0x0005 SHM_CDF_DISCOVER_TMR_POP 11/29/2000-16:45:1802 0x0001 SHM_CDF_INVALID_SW_ID 11/29/2000-16:45:4803 0x0002 SHM_CDF_SW_DNLD_FAILED 11/29/2000-16:51:1704 0x0005 SHM_CDF_DISCOVER_TMR_POP 12/26/2000-16:23:19Hardware Alarm:01 0x5000 Humvee Non-Fatal Minor 12/18/2000-16:48:3602 0x5000 Humvee Non-Fatal Minor 12/18/2000-16:49:1103 0x5000 Humvee Non-Fatal Minor 12/18/2000-16:49:3804 0x5000 Humvee Non-Fatal Minor 12/18/2000-16:54:3105 0x5000 Humvee Non-Fatal Minor 12/26/2000-16:16:34-----------------------------------------------------------------------------dspilmicnt
Display ILMI Counters
Displays the ILMI counters for a particular resource partition on a particular logical port.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspilmicnt <ifNum> <partId>
Syntax Description
ifNum
The ranges for logical interface (or AXSM port) number are as follows:
•
•
partId
The ranges for partition identifier are as follows:
•
•
Related Commands
cnfilmi, dspilmi, dspilmis, clrilmicnt, dnilmi, upilmi
Attributes
Example
Display the ILMI counters for logical port 1 on the current AXSM card.
pinnacle3.1.2.AXSM.a > dspilmicnt 1Port Num: 1SNMPPDUsReceived: 0Get RequestsReceived: 0GetNextRequestsReceived: 0SetRequestsReceived: 0TrapReceived: 0GetResponseReceived 0GetResponseTransmitted: 0GetRequestTransmitted: 0TrapsTransmitted: 0InvalidPDUReceived: 0Asn1ParseError: 0NoSuchNameError: 0TooBigError: 0dspln
Display Line
Display the configuration of a physical line.
Note
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspln <-ds3 | -sonet> <bay.line>
Syntax Description
Related Commands
upln, cnfln, delln
Attributes
Examples
Display T3 line 1 on the current AXSM.
pinnacle.2.AXSM.a > dspln -ds3 1.2LineNum: 1.2LineEnable: DownLineType: ds3cbitadmLineCoding: ds3B3ZSLineLength(meters): 0LineOOFCriteria: fBits3Of8LineAIScBitsCheck: CheckLineLoopback: NoLoopXmt. Clock source: localTimingLineRcvFEACValidation: 4 out of 5 FEAC codesDisplay OC-48 line on the current OC-12 AXSM.
pop20two.1.AXSM.a > dspln -sonet 2.1Line Number : 2.1Admin Status : Up Alarm Status : ClearLoopback : NoLoop APS enabled : DisableFrame Scrambling : Enable Number of ports : 1Xmt Clock source : localTiming Number of partitions: 1Line Type : sonetSts12c Number of SPVC : 0Medium Type(SONET/SDH) : SONET Number of SVC : 4Medium Time Elapsed : 506223Medium Valid Intervals : 96Medium Line Type : ShortSMFdsplncnt
Display Line Counters—display the contents of counters for various cell-related statistics on a line.
The dsplncnt command displays counters for the following:
•
•
•
•
•
•
•
•
•
An asterisk (*) indicates the displayed field does not apply to the AXSM-1-2488.
Note
Cards on Which This Command Runs
AXSM, AXSM-E
AXSM Syntax
dsplncnt <bay.line>
AXSM-E Syntax
dsplncnt <bay.line> <intvl>
Syntax Description
Related Commands
clrlncnt
Attributes
Example
Display example for AXSM-E.
MGX8850.5.AXSME.a > dsplncnt 1.1 1Line : 1.1Interval : 1Ingress EgressRcv CLP0 Cells : 180 180Rcv CLP1 Cells : 0 0Valid OAM Cells : 0 0Err OAM Cells : 0 0Rcv Valid RM Cells : 0 0VpiVciErr Cells : 0Rcv Idle Cells : 317903602Ing Gfc Cells : 0Ing LastUnknVpi : 0Ing LastUnknVci : 0Discard HecErr Cells : 0Corrected HecErr Cells : 0Example
Display the cell counters for line 1 in bay 1.
MGX8850.11.AXSM.a > dsplncnt 1.1Line Number : 1.1Ingress EgressCLP0 Cells : 0 0CLP1 Cells* : 0 0Valid OAM Cells* : 0 0Err OAM Cells* : 0 0Invalid VPI/VCI/PTI Cells*: 0 0Non-zero GFC Cells* : 0Last Unknown VPI* : 0Last Unknown VCI* : 0Discard HecErr Cells : 115Corrected HecErr Cells : 0NOTE: Counters with '*' do NOT apply to AXSM-1-2488 (OC48)dsplnpmbucketcnt
Display Line Performance Bucket Counters
Displays the line specific performance monitoring interval counters.
Cards on Which This Command Runs
AXSM-E
Syntax
dsplnpmbucketcnt <bay.line> <intvl>
Syntax Description
Related Commands
dspalmcnt
Attributes
Example
MGX8850.1.10.AXSME.a > dsplnpmbucketcnt 2.1 96Line Number : 2.1Interval Number : 96Section PM:-----------ESs : 1125SESs : 1125SEFSs : 1125CVs : 43199586Line PM:--------Near End Far EndESs : 1125 1125SESs : 1125 1125CVs : 43199586 165598436UASs : 1125 1125Path PM:--------Near End Far EndESs : 1125 1125SESs : 1125 1125CVs : 14399862 0UASs : 1125 1125dsplns
Display Lines
Displays the configuration for all lines on a card. For each line, the output information consists of the:
•
•
•
•
•
•
•
•
•
•
•
For information on an individual line, use dspln. Also, the dspln command shows the transmit clock configuration if one exists.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dsplns
Related Commands
cnfln, delln, dspcds, dspln, upln
Attributes
Example
Display the configuration of the lines on an AXSM-4-622.
pop20two.1.AXSM.a > dsplnsMedium MediumSonet Line Line Line Frame Line Line AlarmLine State Type Lpbk Scramble Coding Type State----- ----- ------------ ------ -------- ------ ------- ------1.1 Down sonetSts12c NoLoop Enable Other Other Clear1.2 Down sonetSts12c NoLoop Enable Other Other Clear2.1 Up sonetSts12c NoLoop Enable Other ShortSMF Clear2.2 Up sonetSts12c NoLoop Enable Other ShortSMF CriticalExamples
Display line configuration on the current AXSM-1-2488.
pinnacle.1.AXSM.a > dsplnsMedium MediumSonet Line Line Line Frame Line LineLine Status Type Lpbk Scramble Coding Type----- ----- ------------ ------ -------- -------- -------1.1 Down sonetSts48c NoLoop Enable Other ShortSingleModeDisplay the configuration of each T3 line on the current AXSM-16-T3E3.
jdlenoir.11.AXSM.a > dsplnsLine Line Line Line Length OOF AIS AlarmNum State Type Lpbk (meters) Criteria cBitsCheck State---- ------- ----------- ----------- ------ -------- ---------- -----1.1 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear1.2 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear1.3 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear1.4 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear1.5 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear1.6 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear1.7 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear1.8 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear2.1 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear2.2 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear2.3 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear2.4 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear2.5 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear2.6 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear2.7 Down ds3cbitadm NoLoop 0 3Of8Bits Check Clear2.8 Down ds3cbitadm NoLoop 0 3Of8Bits Check Cleardsplog
Display Log
Display log file contents. The dsplog command is a debugging command and requires in-depth knowledge of the internal workings of the system. For example, the display may show points where the switch software steps into and out of functions or tracks tasks that it is spawning.
The PXM45 supports multiple log files: if the space allocation for one file becomes exhausted, the system starts filling a new, sequentially numbered file. The log files contain a substantial variety of information. With no parameters, the output contains all the contents of all the log files, so dsplog provides optional parameters for filtering the output. For example, you could specify only severe errors and only for a particular slot. The Syntax Description describes each parameter. Briefly, their functions are to:
•
•
•
•
•
Cards on Which This Command Runs
PXM45
Syntax
dsplog [-log <filename>] [-sl <slot #>] [-task <task name>] [-mod <module name>] [-sev <severity>]
[-tle <time same or earlier than>] [-tge <time same or greater than>]Syntax Description
Related Commands
clrlog, dsplogs
Attributes
Example
Display the contents of log file number 1. This example shows the first of multiple screens.
jdlenoir.7.PXM.a > dsplog -log 107-00236 11/16/2000-15:21:26 CLI-7-CMDLOGtTnInTsk01 0x8037558ccliCmdLog: cisco@telnet.01: (cc 7).11-00017 11/16/2000-15:21:26 CLI-7-CMDLOGtSmInTsk03 0x801ef16ccliCmdLog: cisco@smterm.03: (logout). - 1 dropped07-00235 11/16/2000-15:18:26 CLI-7-CMDLOGtTnInTsk01 0x8037558ccliCmdLog: cisco@telnet.01: (cc 11).11-00016 11/16/2000-15:18:25 CLI-7-CMDLOGtSmInTsk02 0x801ef16ccliCmdLog: cisco@smterm.02: (logout).11-00015 11/16/2000-15:18:24 CLI-7-CMDLOGtSmInTsk02 0x801ef16ccliCmdLog: cisco@smterm.02: (cc 11).07-00234 11/16/2000-15:18:18 CLI-7-CMDLOGtTnInTsk01 0x8037558ccliCmdLog: cisco@telnet.01: (cc 7).07-00233 11/16/2000-15:18:17 CLI-7-CMDLOGtTnInTsk01 0x8037558ccliCmdLog: cisco@telnet.01: (login).07-00232 11/16/2000-15:18:12 CLI-7-CLITNLOGDisplay all logged events for slot 11. Note that the number 11 appears at the beginning of each log entry. This example shows the first of multiple screens.
jbscott.7.PXM.a > dsplog -sl 1111-00032 11/16/2000-16:35:34 CLI-7-CMDLOGtSmInTsk03 0x801ef16ccliCmdLog: superuser@smterm.03: (logout). - 1 dropped11-00031 11/16/2000-16:34:44 CLI-7-CMDLOGtSmInTsk02 0x801ef16ccliCmdLog: superuser@smterm.02: (logout).11-00030 11/16/2000-16:34:44 CLI-7-CMDLOGtSmInTsk02 0x801ef16ccliCmdLog: superuser@smterm.02: (cc 11).11-00029 11/16/2000-16:33:59 CLI-7-CMDLOGtSmInTsk03 0x801ef16ccliCmdLog: superuser@smterm.03: (logout). - 1 dropped11-00028 11/16/2000-16:32:01 CLI-7-CMDLOGtSmInTsk02 0x801ef16ccliCmdLog: superuser@smterm.02: (logout).11-00027 11/16/2000-16:32:00 CLI-7-CMDLOGtSmInTsk02 0x801ef16ccliCmdLog: superuser@smterm.02: (cc 11).11-00026 11/16/2000-16:15:10 CLI-7-CMDLOGtSmInTsk03 0x801ef16ccliCmdLog: superuser@smterm.03: (logout). - 1 dropped11-00025 11/16/2000-16:12:46 CLI-7-CMDLOGdsplogs
Display Logs—display a list of all existing log files.
The dsplogs shows the existing log files (but not the file contents). The dsplogs command lets you see which files exist and thus determine specific contents to view when you execute dsplog.
Cards on Which This Command Runs
PXM45
Syntax
dsplogs
Syntax Description
This command takes no parameters.
Related Commands
dsplog
Attributes
Example
The output shows that many log files exist. To view the contents of log file 41, for example, you would enter dsplog -log error041.log. See also the description of the dsplog command.
M8850_SF.7.PXM.a > dsplogsCurrent Event log number: 47Event log 47: C:/LOG/event47.logstarting timestamp: 11/19/2001-18:24:39Event log 46: C:/LOG/event46.logstarting timestamp: 11/17/2001-02:26:33Event log 45: C:/LOG/event45.logstarting timestamp: 11/15/2001-02:25:48Event log 44: C:/LOG/event44.logstarting timestamp: 11/12/2001-18:35:01Event log 43: C:/LOG/event43.logstarting timestamp: 11/10/2001-02:30:37Event log 42: C:/LOG/event42.logstarting timestamp: 11/07/2001-16:44:35Event log 41: C:/LOG/event41.logstarting timestamp: 11/06/2001-20:05:54Event log 40: C:/LOG/event40.logstarting timestamp: 11/05/2001-13:05:23Event log 39: C:/LOG/event39.logstarting timestamp: 11/04/2001-03:37:16Event log 38: C:/LOG/event38.logstarting timestamp: 11/02/2001-16:47:52Event log 37: C:/LOG/event37.logdspndalms
Display Node Alarms
Displays various types of alarms on the node from a high-level perspective. With the information in the dspndalms display, you can select one of the following commands to investigate the alarm:
•
•
•
•
The preceding commands execute on the PXM45. If the results of the preceding commands seem to warrant it, you can cc to another card and execute alarm-specific or other troubleshooting commands. Use the help (or ?) on the CLI of the other card to see available alarm commands (? alm, for example).
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
•
•
•
Cards on Which This Command Runs
PXM45
Syntax
dspndalms [slot]
Syntax Description
Related Commands
dspalm, dspalms
Attributes
Examples
Display node alarms. The output shows two major, card-level alarms. Use the dspcdalms command to determine which card or cards have the alarms.
ITNODE3.7.PXM.a > dspndalmsNode Alarm SummaryAlarm Type Critical Major Minor---------- -------- ------- -------Clock Alarms 0 0 0Switching Alarms 0 0 0Environment Alarms 0 0 0Card Alarms 0 2 0The output of dspcdalms shows that both card alarms are on the card in slot 8—the standby PXM45. the last line of the output recommends using dspcdalms with a specific slot to see more details.
ITNODE3.7.PXM.a > dspcdalmsCard Alarm SummarySlot Critical Major Minor---- -------- ------- -------1 0 0 02 0 0 03 0 0 04 0 0 05 0 0 06 0 0 07 0 0 08 0 2 09 0 0 010 0 0 011 0 0 012 0 0 013 0 0 014 0 0 0Use dspcdalms <slot> to see more detail.Executing dspcdalms for slot 8 shows that a disk alarm and card state alarm exist.
ITNODE3.7.PXM.a > dspcdalms 8Card Alarm SummaryAlarm Type Critical Major Minor---------- -------- ------- -------Hardware Alarm 0 0 0Card State Alarm 0 1 0Disk Alarm 0 1 0Line Alarm 0 0 0Port Alarm 0 0 0Feeder Alarm 0 0 0Channel Alarm 0 0 0Run dspcds to see general information about the cards, then use dspcd to acquire details on the state of a particular card.
M8850_NY.7.PXM.a > dspcdsM8850_NY System Rev: 02.01 Dec. 22, 2001 22:50:20 PSTChassis Serial No: SAA03211181 Chassis Rev: B0 GMT Offset: -8Node Alarm: MAJORCard Front/Back Card Alarm Redundant RedundancySlot Card State Type Status Slot Type--- ---------- -------- -------- ------- -----01 Active/Active AXSM_4OC12 NONE 02 PRIMARY SLOT02 Standby/Active AXSM_4OC12 NONE 01 SECONDARY SLOT03 Active-U/Active AXSM_4OC12 NONE NA NO REDUNDANCY04 Empty --- --- --- ---05 Active/Empty Resv AXSME_2OC12 MAJOR NA NO REDUNDANCY06 Active/Mismatch AXSM_16OC3_B MINOR NA NO REDUNDANCY07 Active/Active PXM45 NONE 08 PRIMARY SLOT08 Standby/Active PXM45 NONE 07 SECONDARY SLOT09 Active/Active RPM_PR NONE NA NO REDUNDANCY10 Empty --- --- --- ---11 Empty --- --- --- ---12 Empty --- --- --- ---13 Empty --- --- --- ---14 Empty --- --- --- ---M8850_NY.7.PXM.a >dspingbucketcnt
Display Alarm Counters
Displays selected statistical counters for the specified 15 minute interval (intvl) for all the lines on card.
Cards on Which This Command Runs
AXSM-E
Syntax
dspingbucketcnt <intvl>
Syntax Description
Related Commands
dspegrbucketcnt
Attributes
Example
MGX8850.1.10.AXSME.a > dspingbucketcntLine Total Cells Total CellsReceived Discarded------- --------------- ---------------1.1 0 01.2 0 01.3 0 01.4 0 01.5 0 01.6 0 01.7 0 01.8 0 02.1 0 02.2 0 02.3 0 02.4 0 0dsplnbucketcnt
Display Line Bucket Counters—display the contents of cell counters.
The dsplnbucketcnt command lets you display counters for various cell-related statistics on a line for the current bucket interval. For bucket statistics, line statistics are collected for a period of 15 minutes (bucket interval), then a statistics file is generated at the end of this bucket interval. This file is then uploaded to CWM. The bucket counters are cleared at the start of the next bucket interval.
The dsplnbucketcnt command displays counters for the following:
•
•
•
•
•
•
•
•
•
Note
Cards on Which This Command Runs
AXSM
Syntax
dsplnbucketcnt <bay.line>
Syntax Description
Related Commands
dsplncnt
Attributes
Example
Display the bucket cell counters for line 1 in bay 1.
U2Golden.9.AXSM.a > dsplnbucketcnt 1.1Ingress EgressRcv CLP0 Cells :0 216Rcv CLP1 Cells :0 0Valid OAM Cells :0 180Err OAM Cells :0 0VpiVciErr Cells :0 0Ing Gfc Cells :0Ing LastUnknVpi :0Ing LastUnknVci :0Discard HecErr Cells :0Corrected HecErr Cells :0Discard Upc CLP0 Cells :0Discard Upc Total Cells:0Total Upc NonComp Cells:0dsppnportloscallrel
Display PNNI Port Loss of Signal Call Release
This command displays the enable status of the LOS call release feature. See cnfpnportloscallrel for a description of this feature.
Cards on Which This Command Runs
PXM45
Syntax
dsppnportloscallrel <portid>
Syntax Description
portid
Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.
Related Commands
cnfpnportloscallrel
Attributes
Example
First, confirm that LOS call release is disabled on port 3:1.1:1. Enable it, then confirm that it's enabled.
8850_NY.8.PXM.a > dsppnportloscallrel 3:1.1:1
Call release on Los :disabled
8850_NY.8.PXM.a > cnfpnportloscallrel 3:1.1:1 yes
8850_NY.8.PXM.a > dsppnportloscallrel 3:1.1:1
Call release on Los :enableddspportbucketcnt
Display Port Bucket Counters—display the contents of cell counters.
The dspportbucketcnt command lets you display counters for various cell-related statistics on a port for the current bucket interval. For bucket statistics, port statistics are collected for a period of 15 minutes (bucket interval), then a statistics file is generated at the end of this bucket interval. This file is then uploaded to CWM. The bucket counters are cleared at the start of the next bucket interval and continue to accumulate values until the end of this interval. The dspportbucketcnt command shows the (Ingress & Egress) counters for the following:
•
•
•
•
•
•
Cards on Which This Command Runs
AXSM
Syntax
dspportbucketcnt <ifNum>
Syntax Description
Related Commands
dspportcnt
Attributes
Examples
Display port bucket counters on logical port (ifNum) 1 of the current AXSM.
U2Golden.9.AXSM.a > dspportbucketcnt 11Ingress EgressRcv Clp0 Cells :0 216Rcv Clp1 Cells :0 0Clp0 Disc Cells :0 0Clp1 Disc Cells:0 0Xmt Clp0 Cells :0 216Xmt Clp1 Cells :0 0dspportcnt
Display Port Counters
Displays ATM cell counters for a logical port. Refer to the example for contents.
Cards on Which This Command Runs
AXSM, AXSM-E
AXSM Syntax
dspportcnt <ifNum>
AXSM-E Syntax
dspportcnt <ifNum> <intvl>
Syntax Description
Related Commands
dspports, dspport, cnfport, dspcds
Attributes
Examples
Display port counters on logical port (ifNum) 1 of the current AXSM.
MGX8850.1.AXSM.a > dspportcnt 1Cleared at : 06/27/2001 17:43:13Current time : 06/27/2001 17:44:43Elapsed time : 0 day(s) 0:1:30 [hh:mm:ss]Total Running Avg (cps) Peak--------------------------------------------------------------------Arrival CLP0 Ing: 0000000000000000000000 0 0Arrival CLP1 Ing: 0000000000000000000000 0 0Ar CLP0 discard Ing: 0000000000000000000000 0 0Ar CLP1 discard Ing: 0000000000000000000000 0 0Departure CLP0 Ing: 0000000000000000000000 0 0Departure CLP1 Ing: 0000000000000000000000 0 0Arrival CLP0 Egr: 0000000000000000000000 0 0Arrival CLP1 Egr: 0000000000000000000000 0 0Ar CLP0 discard Egr: 0000000000000000000000 0 0Ar CLP1 discard Egr: 0000000000000000000000 0 0Departure CLP0 Egr: 0000000000000000000000 0 0Departure CLP1 Egr: 0000000000000000000000 0 0Display port counters on logical port (ifNum) 1 of the current AXSM.
MGX8850.1.10.AXSME.a > dspportcnt 1 1Interface Num : 1Interval Num : 1Egr Rcv Clp0 Cells : 0Egr Rcv Clp1 Cells : 0Egr Clp0 Disc Cells : 0Egr Clp1 Disc Cells : 0Egr Xmt Clp0 Cells : 0Egr Xmt Clp1 Cells : 0Egr Rcv OAM Cells : 0Egr Rcv RM Cells : 0Egr Xmt EFCI Cells : 0Egr Rcv EFCI Cells : 0Egr Xmt OAM Cells : 0dspprfhist
Display Performance History
The dspprfhist command shows the percentage of activity of tasks. Refer to the Example section for the type of displayed information. The command applies primarily to internal Cisco developers.
Cards on Which This Command Runs
PXM45, AXSM, AXSM-E
Syntax
dspprfhist
Syntax Description
This command takes no parameters.
Attributes
Example
Display the performance history on the current AXSM. The example display shows a completely idle system.
pop20two.1.AXSM.a > dspprfhistCURRENT TIME 0:45:4Sample # 00:44:27(From)-0:44:47(To)TASK TaskId %---------------------------------------INTERRUPT - 0.0000KERNEL - 0.0000IDLE - 100.0000UNKOWN - 0.0000Sample # -10:44:7(From)-0:44:27(To)TASK TaskId %---------------------------------------INTERRUPT - 0.0000KERNEL - 0.0000IDLE - 100.0000UNKOWN - 0.0000Sample # -20:43:47(From)-0:44:7(To)TASK TaskId %dspswalms
Display Switching Alarms—displays alarms for the switching fabrics.
The dspswalms command helps you isolate the cause of switch fabric alarms. The display shows whether the alarm severity is critical, major, or minor. It also lists information by slot and by alarm type. (See Example section.)
The three alarm types are:
•
•
•
Note
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
•
•
•
Usage Guidelines for dspswalms
After determining the error type and the related slot, you can use the crossbar troubleshooting commands to isolate the problem further.
The following is a top-down sequence of alarm-related commands that lead to isolating possible faults in the switch fabric:
1.
2.
3.
4.
An alarm can originate in any of the following:
•
•
•
The dspswalms display shows how many errors have occurred and generally where the errors have occurred. For purposes of troubleshooting the switch, you can decide which card to replace by using the dspdeverr, dspdevalms, dspxbarplanealms, and dspxbarslotbwalms commands. These commands can help you isolate the problem to a particular switch ASIC, the receiving card, or the link between them. (In the context of the switch ASICs, the hardware path between the switch card and the recipient card's bus transceiver is called a link.) The crossbar troubleshooting commands can be either plane-centric or slot-centric. Plane-centric is from the switch ASICs outwards. Slot-centric is from a slot toward a switch ASIC. The reference point in relation to card slots is important for fault isolation. For example, a plane-centric command sequence is:
1.
2.
3.
4.
Cards on Which This Command Runs
PXM45
Syntax
dspswalms
Syntax Description
This command takes no parameters.
Related Commands
dspndalms, dspdeverr, dspdeverrhist, dspdevalms
Attributes
Examples
Display switching alarms. Where no card resides, the display shows dashes. No errors have occurred.
M8850_NY.7.PXM.a > dspswalmsXBAR SWITCHING FABRIC ALARMS SUMMARYXbar Core Alarm Xbar Port Alarm Xbar Slot B/W alarmSlot No. Critical Major Minor Critical Major Minor Critical Major Minor------- -------- ----- ----- -------- ----- ----- -------- ----- -----01 0 0 0 0 0 0 0 0 002 0 0 0 0 0 0 0 0 003 0 0 0 0 0 0 0 0 004 -- -- -- -- -- -- -- -- --05 0 0 0 0 0 0 0 0 006 0 0 0 0 0 0 0 0 007 0 0 0 0 0 0 0 0 008 0 0 0 0 0 0 0 0 009 -- -- -- -- -- -- -- -- --10 -- -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- -- --M8850_NY.7.PXM.a >M8950_DC.7.PXM.a > dspndalmsNode Alarm SummaryAlarm Type Critical Major Minor---------- -------- ------- -------Clock Alarms 0 1 0Switching Alarms 1 1 0Environment Alarms 0 0 0Card Alarms 0 2 0M8950_DC.7.PXM.a >M8950_DC.7.PXM.a > dspswalmsXBAR SWITCHING FABRIC ALARMS SUMMARYXbar Core Alarm Xbar Port Alarm Xbar Slot B/W alarmSlot No. Critical Major Minor Critical Major Minor Critical Major Minor------- -------- ----- ----- -------- ----- ----- -------- ----- -----01 1 0 0 0 0 0 0 1 002 -- -- -- -- -- -- -- -- --03 -- -- -- -- -- -- -- -- --04 -- -- -- -- -- -- -- -- --05 0 0 0 0 0 0 0 0 006 -- -- -- -- -- -- -- -- --07 0 0 0 0 0 0 0 0 008 -- -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- -- --15 -- -- -- -- -- -- -- -- --16 -- -- -- -- -- -- -- -- --M8950_DC.7.PXM.a >M8950_DC.7.PXM.a > dspxbarplanealmsM8950_DC System Rev: 02.01 Dec. 15, 2001 17:55:13 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR PLANE ALARM INFOXbarSlot Xbar Core Xbar Plane/plane Alarm Based Alarm------ ----- -----------9/0 -- --9/1 -- --9/2 -- --9/3 -- --10/0 -- --10/1 -- --10/2 -- --10/3 -- --25/0 -- --25/1 -- --25/2 -- --25/3 -- --26/0 -- --26/1 -- --26/2 -- --26/3 Critical --M8950_DC.7.PXM.a > dspxbarslotbwalmsM8950_DC System Rev: 02.01 Dec. 15, 2001 17:55:26 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR SLOT BANDWIDTH ALARM INFO SUMMARYLoadSharing < Enabled > AutoShutDown < Enabled >Slot Xbar Slot Required no. Available no. Operational no.No. Bw Alarm of Planes of Planes of Planes---- --------- ----------- ------------ --------------01 Major 3 8 702 -- -- -- --03 -- -- -- --04 -- -- -- --05 None 3 8 806 -- -- -- --07 None 1 4 408 -- -- -- --12 -- -- -- --13 -- -- -- --14 -- -- -- --15 -- -- -- --16 -- -- -- --M8950_DC.7.PXM.a >M8950_DC.7.PXM.a > dspdeverr XBARCORE -pslot *M8950_DC System Rev: 02.01 Dec. 15, 2001 18:02:14 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNTERS SUMMARYFabric Slot / PlaneSlot 9/0 9/1 9/2 9/3 10/0 10/1 10/2 10/3----- ------ ------ ------ ------ ------ ------ ------ ------01 0 0 0 0 0 0 0 002 -- -- -- -- -- -- -- --03 -- -- -- -- -- -- -- --04 -- -- -- -- -- -- -- --05 0 0 0 0 0 0 0 006 -- -- -- -- -- -- -- --07 0 0 0 0 0 0 0 008 -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- --15 -- -- -- -- -- -- -- --16 -- -- -- -- -- -- -- --M8950_DC System Rev: 02.01 Dec. 15, 2001 18:02:14 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNTERS SUMMARYFabric Slot / PlaneSlot 25/0 25/1 25/2 25/3 26/0 26/1 26/2 26/3----- ------ ------ ------ ------ ------ ------ ------ ------01 0 0 0 0 0 0 0 1342002 -- -- -- -- -- -- -- --03 -- -- -- -- -- -- -- --04 -- -- -- -- -- -- -- --05 0 0 0 0 0 0 0 006 -- -- -- -- -- -- -- --07 0 0 0 0 0 0 0 008 -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- --15 -- -- -- -- -- -- -- --16 -- -- -- -- -- -- -- --M8950_DC.7.PXM.a > dspdeverr XBARCORE -pslot 1M8950_DC System Rev: 02.01 Dec. 15, 2001 18:06:02 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------9/0 0 0 0 0 0 0 0 0 09/1 0 0 0 0 0 0 0 0 09/2 0 0 0 0 0 0 0 0 09/3 0 0 0 0 0 0 0 0 010/0 0 0 0 0 0 0 0 0 010/1 0 0 0 0 0 0 0 0 010/2 0 0 0 0 0 0 0 0 010/3 0 0 0 0 0 0 0 0 0M8950_DC System Rev: 02.01 Dec. 15, 2001 18:06:02 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----9/0 0 0 09/1 0 0 09/2 0 0 09/3 0 0 010/0 0 0 010/1 0 0 010/2 0 0 010/3 0 0 0M8950_DC System Rev: 02.01 Dec. 15, 2001 18:06:02 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------25/0 0 0 0 0 0 0 0 0 025/1 0 0 0 0 0 0 0 0 025/2 0 0 0 0 0 0 0 0 025/3 0 0 0 0 0 0 0 0 026/0 0 0 0 0 0 0 0 0 026/1 0 0 0 0 0 0 0 0 026/2 0 0 0 0 0 0 0 0 026/3 220 3300 3300 0 3300 3300 0 0 0Type <CR> to continue, Q<CR> to stop:M8950_DC System Rev: 02.01 Dec. 15, 2001 18:06:02 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----25/0 0 0 025/1 0 0 025/2 0 0 025/3 0 0 026/0 0 0 026/1 0 0 026/2 0 0 026/3 0 0 0M8950_DC.7.PXM.a >Display switch fabric alarms on the current MGX 8950 switch.
M8950_DC.7.PXM.a > dspswalmsXBAR SWITCHING FABRIC ALARMS SUMMARYXbar Core Alarm Xbar Port Alarm Xbar Slot B/W alarmSlot No. Critical Major Minor Critical Major Minor Critical Major Minor------- -------- ----- ----- -------- ----- ----- -------- ----- -----01 1 0 0 0 0 0 0 1 002 -- -- -- -- -- -- -- -- --03 -- -- -- -- -- -- -- -- --04 -- -- -- -- -- -- -- -- --05 0 0 0 0 0 0 0 0 006 -- -- -- -- -- -- -- -- --07 0 0 0 0 0 0 0 0 008 -- -- -- -- -- -- -- -- --11 -- -- -- -- -- -- -- -- --12 -- -- -- -- -- -- -- -- --13 -- -- -- -- -- -- -- -- --14 -- -- -- -- -- -- -- -- --15 -- -- -- -- -- -- -- -- --16 -- -- -- -- -- -- -- -- --M8950_DC.7.PXM.a > dspdevalms XBARCORE -pslot 1M8950_DC System Rev: 02.01 Dec. 21, 2001 18:06:42 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE ERROR ALARM INFO FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par----- ---- ---- ---- ---- ---- ---- ---- ---- ---9/0 -- -- -- -- -- -- -- -- --9/1 -- -- -- -- -- -- -- -- --9/2 -- -- -- -- -- -- -- -- --9/3 -- -- -- -- -- -- -- -- --10/0 -- -- -- -- -- -- -- -- --10/1 -- -- -- -- -- -- -- -- --10/2 -- -- -- -- -- -- -- -- --10/3 -- -- -- -- -- -- -- -- --M8950_DC System Rev: 02.01 Dec. 21, 2001 18:06:42 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE ERROR ALARM INFO FOR SLOT: 1FabricSlot/ SFrame SFrame ACP SevPlane Tick Lock Addr Summ.----- ---- ---- --- ----9/0 -- -- -- --9/1 -- -- -- --9/2 -- -- -- --9/3 -- -- -- --10/0 -- -- -- --10/1 -- -- -- --10/2 -- -- -- --10/3 -- -- -- --M8950_DC System Rev: 02.01 Dec. 21, 2001 18:06:42 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE ERROR ALARM INFO FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par----- ---- ---- ---- ---- ---- ---- ---- ---- ---25/0 -- -- -- -- -- -- -- -- --25/1 -- -- -- -- -- -- -- -- --25/2 -- -- -- -- -- -- -- -- --25/3 -- -- -- -- -- -- -- -- --26/0 -- -- -- -- -- -- -- -- --26/1 -- -- -- -- -- -- -- -- --26/2 -- -- -- -- -- -- -- -- --26/3 Maj Crit Crit -- Crit Crit -- -- --M8950_DC System Rev: 02.01 Dec. 21, 2001 18:06:42 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE ERROR ALARM INFO FOR SLOT: 1FabricSlot/ SFrame SFrame ACP SevPlane Tick Lock Addr Summ.----- ---- ---- --- ----25/0 -- -- -- --25/1 -- -- -- --25/2 -- -- -- --25/3 -- -- -- --26/0 -- -- -- --26/1 -- -- -- --26/2 -- -- -- --26/3 -- -- -- CritM8950_DC.7.PXM.a > dspdeverr XBARCORE -pslot 1M8950_DC System Rev: 02.01 Dec. 21, 2001 18:10:23 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------9/0 0 0 0 0 0 0 0 0 09/1 0 0 0 0 0 0 0 0 09/2 0 0 0 0 0 0 0 0 09/3 0 0 0 0 0 0 0 0 010/0 0 0 0 0 0 0 0 0 010/1 0 0 0 0 0 0 0 0 010/2 0 0 0 0 0 0 0 0 010/3 0 0 0 0 0 0 0 0 0M8950_DC System Rev: 02.01 Dec. 21, 2001 18:10:23 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----9/0 0 0 09/1 0 0 09/2 0 0 09/3 0 0 010/0 0 0 010/1 0 0 010/2 0 0 010/3 0 0 0M8950_DC System Rev: 02.01 Dec. 21, 2001 18:10:23 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------25/0 0 0 0 0 0 0 0 0 025/1 0 0 0 0 0 0 0 0 025/2 0 0 0 0 0 0 0 0 025/3 0 0 0 0 0 0 0 0 026/0 0 0 0 0 0 0 0 0 026/1 0 0 0 0 0 0 0 0 026/2 0 0 0 0 0 0 0 0 026/3 220 3300 3300 0 3300 3300 0 0 0M8950_DC System Rev: 02.01 Dec. 21, 2001 18:10:23 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE CURRENT ERROR COUNT FOR SLOT: 1FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----25/0 0 0 025/1 0 0 025/2 0 0 025/3 0 0 026/0 0 0 026/1 0 0 026/2 0 0 026/3 0 0 0M8950_DC.7.PXM.a > dspdeverrhist XBARCORE -pslot 1M8950_DC System Rev: 02.01 Dec. 21, 2001 18:11:21 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE HISTORY ERROR COUNT FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------9/0 0 0 0 0 0 0 0 0 09/1 0 0 0 0 0 0 0 0 09/2 0 0 0 0 0 0 0 0 09/3 0 0 0 0 0 0 0 0 010/0 0 0 0 0 0 0 0 0 010/1 0 0 0 0 0 0 0 0 010/2 0 0 0 0 0 0 0 0 010/3 0 0 0 0 0 0 0 0 0M8950_DC System Rev: 02.01 Dec. 21, 2001 18:11:21 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE HISTORY ERROR COUNT FOR SLOT: 1FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----9/0 0 0 09/1 0 0 09/2 0 0 09/3 0 0 010/0 0 0 010/1 0 0 010/2 0 0 010/3 0 0 0XBAR CORE HISTORY ERROR COUNT FOR SLOT: 1FabricSlot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BPPlane Sync Cv Disp Par CRC CRC Remap Recur Par------ ------ ------ ------ ------ ------ ------ ------ ------ ------25/0 0 0 0 0 0 0 0 0 025/1 0 0 0 0 0 0 0 0 025/2 0 0 0 0 0 0 0 0 025/3 0 0 0 0 0 0 0 0 026/0 0 0 0 0 0 0 0 0 026/1 0 0 0 0 0 0 0 0 026/2 0 0 0 0 0 0 0 0 026/3 10117K 151764K 151764K 0 151764K 151764K 0 0 0M8950_DC System Rev: 02.01 Dec. 21, 2001 18:11:21 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR CORE HISTORY ERROR COUNT FOR SLOT: 1FabricSlot/ SFrame SFrame ACPPlane Tick Lock Addr----- ------ ------ ----25/0 0 0 025/1 0 0 025/2 0 0 025/3 0 0 026/0 0 0 026/1 0 0 026/2 0 0 026/3 0 0 0M8950_DC.7.PXM.a >dsptrapmgr
Display Trap Manager
Display details about all existing trap managers. The dsptrapmgr output shows:
•
•
•
•
•
Of these elements, the IP address and port number result from addtrapmgr.
Cards on Which This Command Runs
PXM45
Syntax
dsptrapmgr
Syntax Description
This command takes no parameters.
Related Commands
addtrapmgr, deltrapmgr
Attributes
Example
Display trap managers.
node19.8.PXM.a > dsptrapmgripAddress PortNum RowStatus ReadTrapFlag NextTrapSeqNum--------------- ------- ---------- ------------ --------------171.71.55.21 2500 Add Off 0172.29.65.87 2500 Add Off 348172.71.59.21 2500 Add Off 0LastTrapSeqNum: 385NumOfValidEntries: 3
dspxbar
Display Crossbar—display the configuration of the crossbars.
The dspxbar command displays general information about the configuration of a switch plane (or switching fabric or crossbar, also synonymous with switch ASIC).
The crossbar-related commands are special debug commands with infrequent use. The configuration normally has fixed, default values and is not configurable.
The low-level dspxbar command normally applies to software or hardware development and therefore is not useful for troubleshooting at the network or node level. To isolate a switching problem to determine whether to replace a card, use the crossbar troubleshooting commands: dspswalms, dspdeverr, dspdevalms, dspdeverr, dspdeverrhist, dspxbarerrthresh.
An engineer that needs to alter certain error thresholds for hardware or software development can use the cnfxbarerrthresh command.
Connectivity Between the Switching Fabric and Card Slots
Before attempting to interpret the contents of the dspxbar output, some perspective on the crossbar information is appropriate. The switch fabric consists of all the switch ASICs in total. This total includes the switch planes in use The connectivity between the cards and the switch fabric forms a mesh: each switch ASIC communicates with each card, and each card can use any ASIC.
If one switch ASIC becomes inoperative, the switching fabric continues to support new or existing connections within the switch, but the throughput falls far short of the maximum. Of less drastic effect would be a condition where one link can no longer carry data between an individual ASIC pin and a particular card slot.
The Contents of the dspxbar Output
Refer to the examples to see the location of each of the following fields. The general information that dspxbar displays is as follows:
•
•
•
•
•
•
•
The crossbar configuration consists of four categories of information for each slot:
•
•
•
•
The Slot column for Redundancy Configuration shows whether card redundancy exists, as follows: if the slot number under Redundancy Configuration differs from the number in the Slot Number column (far left in the example screen), a card redundancy configuration exists for that slot pair.
Note
Cards on Which This Command Runs
PXM45
Syntax
dspxbar <plane>
dspxbar <xbarSlot> <plane> for XM60Syntax Description
Related Commands
dspswalms, dspdevalms, dspdeverr, dspdeverrhist, dspxbarerrthresh, clrxbaralm, clrxbarerrcnt
Attributes
Example
Display switch ASIC (or switch plane or crossbar) 0.
M8850_NY.7.PXM.a > dspxbar 0M8850_NY System Rev: 02.01 Dec. 17, 2001 23:00:48 PSTMGX8850 Node Alarm: MAJORPXM45 CROSSBAR CONFIGURATIONCrossbar Slot No: 7 Switch Asic No: 0 Status: OKCell Grant Mode: Multicast Pref Resync Sframe Tic: Rising-Edge DetectAsic Revision: 1Slot BACK PRESSURE DISABLE REQUEST DISABLE DATA REDUNDANCY CONFIGNo Grant Mode Dest Src Dest Src Mode Slot---- ------------- --------------- ------------ ------------------1 Valid InBand No No No No Remap 12 Valid InBand No No No No Remap 23 Valid InBand No No No No Remap 34 Valid InBand No No No No Remap 45 Valid InBand No No No No Remap 56 Valid InBand No No No No Remap 67 Valid InBand No No No No Remap 78 Valid InBand No No No No Remap 89 Valid InBand No No No No Remap 910 Valid InBand No No No No Remap 1011 Valid InBand No No No No Remap 1112 Valid InBand No No No No Remap 1213 Valid InBand No No No No Remap 1314 Valid InBand No No No No Remap 14M8850_NY.7.PXM.a >Display switch ASIC 1 in slot 25. Note that the Redundancy Column reflects the PXM45 redundancy (with slot 7 mapping to slot 8 and slot 8 mapping to slot 7).
JBP2_Lower.8.PXM.a > dspxbar 25 1JBP2_Lower System Rev: 02.01 Nov. 28, 2000 21:35:39 GMTMGX8950 (JBP-2) Node Alarm: MAJORPXM45 CROSSBAR CONFIGURATIONCrossbar Slot No: 25 Switch Asic No: 1 Status: OKCell Grant Mode: Multicast Pref Resync Sframe Tic: Rising-Edge DetectAsic Revision: 1Slot BACK PRESSURE DISABLE REQUEST DISABLE DATA REDUNDANCY CONFIGNo Grant Mode Dest Src Dest Src Mode Slot---- ------------- --------------- ------------ ------------------1 Valid InBand No No No No Remap 12 Valid InBand No No No No Remap 23 Valid InBand No No No No Remap 34 Valid InBand No No No No Remap 45 Valid InBand No No No No Remap 56 Valid InBand No No No No Remap 67 Valid InBand Yes Yes No No Remap 88 Valid InBand Yes Yes No No Remap 711 Valid InBand No No No No Remap 1112 Valid InBand No No No No Remap 1213 Valid InBand No No No No Remap 1314 Valid InBand No No No No Remap 1415 Valid InBand No No No No Remap 1516 Valid InBand No No No No Remap 16dspxbarerrthresh
Display Crossbar Error Threshold—display the thresholds for alarms of different severities.
A crossbar can have nine types of errors, and each error has a threshold. The errors are loss of synchronization, a variety of parity and CRC errors, and so on (see Definitions of Crossbar Errors).
The items that make up a threshold are the:
•
•
•
Note
The two types of alarm counts for each of these severities. (Refer to the example.) The higher count is the Alarm Count and is the highest number of errors that triggers an alarm of a particular severity. The lower count is the Release Count: when the number of errors drops below the Release Count, the alarm severity drops to the next lower severity. For example (using the defaults shown in the example display), if the number of transceiver errors drops below 40 (a major alarm), the alarm turns into a minor alarm. The higher count for a minor, major, and critical alarm is the number of errors that trigger that alarm. The lower count is number of errors that causes the severity to drop to the next lower severity.
The types of errors whose thresholds are displayed are:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Cards on Which This Command Runs
PXM45
Syntax
dspxbarerrthresh
Syntax Description
This command takes no parameters.
Related Commands
dspxbar, dspdevalms, dspdeverrhist
Attributes
Example
Display the current crossbar error thresholds.
M8850_NY.7.PXM.a > dspxbarerrthreshM8850_NY System Rev: 02.01 Nov. 15, 2001 14:24:30 PSTMGX8850 Node Alarm: CRITICALCROSSBAR ERROR CONFIGURATIONThresh -- MINOR -- -- MAJOR -- -- CRITICAL --Device Error Time Clear Alarm Clear Alarm Clear AlarmType (msec) Count Count Count Count Count Count-------------------- ------ ----- ----- ----- ----- ----- -----LossOfSync 20000 0 3 4 15 300 301TranscieverErr 20000 0 31 40 150 300 301DisparityErr 20000 0 31 40 150 300 301ParityErr 20000 300 301 300 301 300 301HeaderCRCErr 20000 0 31 40 150 300 301PayloadCRCErr 20000 0 31 40 150 300 301RemapTwiceErr 20000 0 1 0 1 300 301RemapRecurrErr 20000 300 301 300 301 300 301B.P.ParityErr 20000 0 31 40 150 300 301M8850_NY.7.PXM.a >On an MGX 8950, the display appears as follows:
JBP2_Lower.8.PXM.a > dspxbarerrthreshJBP2_Lower System Rev: 02.01 Nov. 28, 2000 21:39:29 GMTMGX8950 (JBP-2) Node Alarm: MAJORCROSSBAR ERROR CONFIGURATIONThresh -- MINOR -- -- MAJOR -- -- CRITICAL --Device Error Time Clear Alarm Clear Alarm Clear AlarmType (msec) Count Count Count Count Count Count-------------------- ------ ----- ----- ----- ----- ----- -----LossOfSync 20000 0 3 4 15 300 301TranscieverErr 20000 0 31 40 150 300 301DisparityErr 20000 0 31 40 150 300 301ParityErr 20000 300 301 300 301 300 301HeaderCRCErr 20000 0 31 40 150 300 301PayloadCRCErr 20000 0 31 40 150 300 301RemapTwiceErr 20000 0 1 0 1 300 301RemapRecurrErr 20000 300 301 300 301 300 301B.P.ParityErr 20000 0 31 40 150 300 301dspxbarmgmt
Display Crossbar Management—display the load sharing configuration.
The dspxbarmgmt command shows details about the load sharing configuration for the node. See the cnfxbarmgmt description for an explanation.
Cards on Which This Command Runs
PXM45
Syntax
dspxbarmgmt
Syntax Description
This command takes no parameters.
Related Commands
cnfxbarmgmt
Attributes
Example
Display the crossbar management state for the current node. The settings are the defaults.
pop20two.7.PXM.a > dspxbarmgmtpop20two System Rev: 02.01 Dec. 05, 2000 20:43:43 GMTMGX8850 Node Alarm: MAJORLoad Sharing: EnableAuto Shutdown: DisablePlane Alarm Threshold: 3dspxbarplanealms
The dspxbarplanealms command displays the alarm status for each switch plane.
Cards on Which on This Command
PXM45
Syntax
dspxbarplanealms
Syntax Description
This command takes no parameters.
Related Commands
dspxbarslotbwalms
Attributes
Example
M8850_NY.7.PXM.a > dspxbarplanealmsM8850_NY System Rev: 02.01 Dec. 10, 2001 16:35:21 PSTMGX8850 Node Alarm: MAJORXBAR PLANE ALARM INFOXbarSlot Xbar Core Xbar Plane/plane Alarm Based Alarm------ ----- -----------7/0 -- --7/1 -- --7/2 -- --8/0 -- --8/1 -- --8/2 -- --M8850_NY.7.PXM.a > dspxbarslotbwalmsM8850_NY System Rev: 02.01 Dec. 10, 2001 16:36:09 PSTMGX8850 Node Alarm: MAJORXBAR SLOT BANDWIDTH ALARM INFO SUMMARYLoadSharing < Enabled > AutoShutDown < Enabled >Slot Xbar Slot Required no. Available no. Operational no.No. Bw Alarm of Planes of Planes of Planes---- --------- ----------- ------------ --------------01 None 3 6 602 None 3 6 603 None 3 6 604 -- -- -- --05 None 2 6 606 None 3 6 607 None 1 6 608 None 1 6 610 -- -- -- --11 -- -- -- --12 -- -- -- --13 -- -- -- --14 -- -- -- --M8850_NY.7.PXM.a >M8950_DC.7.PXM.a > dspxbarplanealmsM8950_DC System Rev: 02.01 Dec. 15, 2001 17:21:50 PSTMGX8950 (JBP-2) Node Alarm: CRITICALXBAR PLANE ALARM INFOXbarSlot Xbar Core Xbar Plane/plane Alarm Based Alarm------ ----- -----------9/0 -- --9/1 -- --9/2 -- --9/3 -- --10/0 -- --10/1 -- --10/2 -- --10/3 -- --25/0 -- --25/1 -- --25/2 -- --25/3 -- --26/0 -- --26/1 -- --
