9 Troubleshooting Commands C H A P T E R

9 Troubleshooting Commands C H A P T E R
C H A P T E R
9
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 with a description 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.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-1
Chapter 9
Troubleshooting Commands
Identifying the AXSM Models
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.
The MGX 8850 node use 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 Hardware Installation, Release 2.1.
Table 9-1
Valid Line Numbers and Number of Bays for AXSM Card Types
Front Card
Speed
Lines
Bays
AXSM-1-2488
OC-48
1
1
AXSM-4-622
OC-12
1–4
1–2
AXSM-16-155
OC-3
1–8
1–2
AXSM-16-T3E3
T3, E3
1–8
1–2
AXSM-2-622-E
OC12
1
1–2
AXSM-8-155-E
OC3
1–4
1–2
1–8
1–2
AXSM-16-T3E3-E T3, E3
Identifying Physical and Logical Elements
The Private Network-to-Network Interface (PNNI) control protocol and the service modules use
different formats to identify the same entity. For example, the format of a logical port that you enter on
an AXSM is different from the format you would enter on the PXM45. This section describes these
formats in the PNNI and AXSM contexts and how they correspond to each other. The parallel actions of
configuring or displaying logical elements on different cards is broadly illustrated in the Cisco
MGX 8850 Routing Switch Software Configuration Guide, Release 2.0.
Apart from the way PNNI and the lower levels of logic identify the same element, the sequence of
commands also needs explanation. When you configure logical ports—for just one example—you must
complete certain tasks on the AXSM CLI before or after related PNNI tasks. For certain commands, this
manual lists prerequisite commands or tasks. For more details on the sequence of tasks, refer to the Cisco
MGX 8850 Routing Switch Software Configuration Guide, Release 2.0, for more details of this sequence.
AXSM Format
On a service module, you identify the follow when you provision the capabilities of the card:
•
Slot
•
Bay
Cisco MGX 8850 Routing Switch Command Reference
9-2
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
Identifying Physical and Logical Elements
•
Line
•
Logical port
•
Port group
•
Resource partition
Not all of these elements correspond to elements you specify on the PXM45. Subsequent paragraphs
describe only the common elements that are visible on the CLI of the PXM and the service module. The
preceding elements are further defined in the Cisco MGX 8850 Routing Switch Software Configuration
Guide, Release 2.0.
For a UNI or NNI, one logical interface (or logical port) exists per physical line. For virtual network to
network interfaces (VNNIs), you can configure multiple ports on a line. The maximum number of logical
ports on an AXSM is 60 regardless of the AXSM model or the number of lines on the back cards. The
range of logical port numbers is 1–60 for an AXSM regardless of whether the interface type is UNI, NNI,
or VNNI.
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:
•
The shelf is always 1 for the current product and so is usually omitted.
•
The slot number of the front card.
•
Subslot is the number of the bay where the back card resides. This number is 1 or 2.
•
Port is the physical line.
•
Subport corresponds to the resource partition on the AXSM. For a UNI or NNI, this resource
partition is the same number as the logical port number (ifNum) on the AXSM. For a virtual
network-to-network interface (VNNI), the number does not directly correspond to the
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
PNNI port
AXSM
Shelf
N/A
Slot
Slot
Subslot
Bay (for upper or lower back card)
Port
Line
Subport
Logical interface (or port)
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-3
Chapter 9
Troubleshooting Commands
Identifying Physical and Logical Elements
As Table 9-2 shows, a port to PNNI is a line on the AXSM, and a subport to PNNI 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)
Cisco MGX 8850 Routing Switch Command Reference
9-4
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
abortofflinediag
abortofflinediag
Abort Offline Diagnostics
Aborts the currently running offline diagnostics.
Note
See the cnfdiag command for a detailed description of MGX 8850 diagnostics.
Syntax
abortofflinediag
<slot>
Syntax Description
slot
The slot of the card for which to abort the offline diagnostics.
Cards on Which This Command Runs
PXM45
Related Commands
cnfdiag, cnfdiagall, dspdiagcnf
Attributes
Log: no
Caution
State: active, standby
Privilege: SERVICE_GP
If offline diagnostic is running on the AXSM, the AXSM must be in the standby state.
Example
abortofflinediag 1
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-5
Chapter 9
Troubleshooting Commands
addchanloop
addchanloop
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 totally
intrusive. The test requires some form of 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):
•
In the ingress direction, the cells travel from the tester to the queueing engine on the AXSM; then
back to the tester.
•
In the egress direction, the cells travel from the tester to the local AXSM; then across the network
to the remote AXSM. At the far end, the cells go to the queueing engine then return back across the
network to the tester.
The maximum number of loopbacks that can exist on an AXSM is 256.
Figure 9-1
Connection (Channel) Loopbacks on the Ingress and Egress
Tester
AXSM
Ingress: mode 1
AXSM
AXSM
Tester
Egress: mode 2
Rx
49469
Tx
ATM
cloud
Cards on Which This Command Runs
AXSM
Syntax
addchanloop <ifNumber> <vpi> <vci> <loopback mode>
Syntax Description
ifNumber
The logical port number. The range for AXSM is 1–60.
vpi
The VPI of the connection. The range is 0–4095.
Cisco MGX 8850 Routing Switch Command Reference
9-6
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
addchanloop
vci
The VCI of the connection. The range is 32–65535.
loopback
mode
The mode of the loopback is the direction.
•
1 = the ingress direction.
•
2 = the egress direction.
Related Commands
delchanloop, dspchanloop
Tabulates
Log: log
State: active, standby
Privilege: SERVICE_GP
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 50
Check for the presence of the loopback by displaying all channel loopbacks on port 4.
pop20two.1.AXSM.a > dspchanloop 4
Port
Type
lVPI
lVCI
4
igrLpbk
1
50
rVPI
0
rVCI
35
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-7
Chapter 9
Troubleshooting Commands
addlnloop
addlnloop
Add Line Loop
Specifies a loopback state for a line on the current service module.
Note
Before you can change the loopback type for an existing loopback, you must first delete the loopback
by executing dellnloop or just addlnloop with the No loopback mode.
Cards on Which This Command Runs
AXSM
AXSM Syntax
addlnloop <-ds3 | -sonet bay.line> <-lpb loopback type>
Note
For AXSM cards, the keyword ds3 applies to both T3 and E3 line types.
AXSM Syntax Description
-ds3
Specifies a DS3 line (E3 or T3) or a SONET line (OC-3c, OC-12c, OC-48c).
-sonet
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.
-lpb
Specifies the loopback type for the line type. The entry for no loopback (1) removes
any existing loopback.
1 = No loopback
2 = Local loopback
3 = Remote loopback
Related Commands
dellnloop
Attributes
Log: log
State: active
Privilege: GROUP1
Example
Adding a DS3 line in a loopback state.
MGX8850.1.11.AXSM.a > addlnloop -ds3 1.1 -lpb 2
Cisco MGX 8850 Routing Switch Command Reference
9-8
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
clrallcnf
clrallcnf
Clear All Configurations
Clear all configurations for all the cards in the node. After you enter the command, the system prompts
you to confirm the action.
Caution
Be absolutely sure you need to execute this command because it clears all configuration files on the
PXM45. After clrallcnf, you need to reconfigure the switch.
Cards on Which This Command Runs
PXM45
Syntax
clrallcnf
Related Commands
restoreallcnf
Attributes
Log: log
State: active, init
Privilege: SERVICE_GP
Example
Clear all the configuration elements for all the cards in the node.
node1.7.PXM.a > clrallcnf
All SM's config will be deleted, and
the shelf will be reset.
Do you want to proceed (Yes/No)?
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-9
Chapter 9
Troubleshooting Commands
clralmcnt
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
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
Log: log
State: active
Privilege: SUPER_GP
Example
Clear the alarms on line 1 or the lower back card.
node1.1.2.AXSM.a > clralmcnt 2.1
Cisco MGX 8850 Routing Switch Command Reference
9-10
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
clrbecnt
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
Log: no log
State: active
Privilege: SUPER_GP
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-11
Chapter 9
Troubleshooting Commands
clrcdcnt
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
Log: log
State: active
Privilege: SUPER_GP
Cisco MGX 8850 Routing Switch Command Reference
9-12
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
clrchancnt
clrchancnt
Clear Channel Counters—clears the error counters for a single connection.
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
This command does not apply to OC-48 cards.
Cards on Which This Command Runs
AXSM
Syntax
clrchancnt <ifNum> <vpi> <vci>
Syntax Description
ifNum
The logical port number. The range for AXSM is 1–60.
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
Log: log
State: active
Privilege: SUPER_GP
Example
Clear all the connection counters on AXSM for connection 100.1000 on logical port 3.
node1.1.AXSM.a > clrchancnt 3 100 1000
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-13
Chapter 9
Troubleshooting Commands
clrchancnts
clrchancnts
Clear Channel Counters—clears the error counters for all connections on a card.
Clears the statistics counters on all connections.
Cards on Which This Command Runs
AXSM
Syntax
clrchancnts
Syntax Description
No parameters.
Related Commands
dspchancnt, clrchancnt
Attributes
Log: no log
State: active
Privilege: SUPER_GP
Example
SunnyVale.13.AXSM.a > clrchancnts
Cisco MGX 8850 Routing Switch Command Reference
9-14
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
clrdiagerr
clrdiagerr
Clear Diagnostics Errors
Clears all diagnostics error messages that are currently in memory.
Note
See the cnfdiag command for a detailed description of MGX 8850 diagnostics.
Syntax
clrdiagerr
<slot>
Syntax Description
slot
The slot of the card for which to clear the diagnostics errors.
Cards on Which This Command Runs
PXM45
Related Commands
dspdiagerr
Attributes
Log: No
State: active, standby
Privilege: SERVICE_GP
Example
clrdiagerr 7
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-15
Chapter 9
Troubleshooting Commands
clrdiagstat
clrdiagstat
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
See the cnfdiag command for a detailed description of MGX 8850 diagnostics.
Syntax
clrdiagstat <slot>
Syntax Description
slot
The slot of the card for which to clear the diagnostics statistics.
Cards on Which This Command Runs
PXM45
Related Commands
dspdiagstat
Attributes
Log: no
State: active or standby
Privilege: SERVICE_GP
Example
clrdiagstat 7
Cisco MGX 8850 Routing Switch Command Reference
9-16
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
clrerr
clrerr
Clear Error
Clear all error log files for a slot. 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
-sl
Number of the slot. The value of slot is any slot in the switch.
Related Commands
dsperr
Attributes
Log: no log
State: active, standby
Privilege: SUPER_GP
Example
Clear all error log files on the PXM45.
pinnacle.7.PXM.a > clrerr
Do you want to clear error log file (Yes/No)?
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-17
Chapter 9
Troubleshooting Commands
clrerrhist
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
Log: no log
State: active, standby, init
Privilege: ANYUSER
Example
Clear the error history for the current PXM45. The system returns a message indicating whether the
operation succeeded.
pop20one.7.PXM.a > clrerrhist 7
Log of Errors and Failures for slot# 7 is cleared.
Cisco MGX 8850 Routing Switch Command Reference
9-18
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
clrilmicnt
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
Syntax
clrilmicnt <ifNum> <partId>
Syntax Description
ifNum
The logical port number. The range for AXSM is 1–60.
partId
Number of the partition in the range 1–20.
Related Commands
dspilmicnt, dspilmi, dspilmis
Attributes
Log: no log
State: active
Privilege: SUPER_GP
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 > dspparts
if part Ctlr egr
egr
ingr
ingr
min max
min
max min
max
Num 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
10
pop20two.1.AXSM.a > clrilmicnt 1 1
ilmi stats for ifNum 1, partId 1 cleared
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-19
Chapter 9
Troubleshooting Commands
clrlncnt
clrlncnt
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
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
Log: log
State: active
Privilege: SUPER_GP
Example
Clear the line counters for line 1 in bay 1 on the current AXSM.
wilco.1.AXSM.a > clrlncnt 1.1
Cisco MGX 8850 Routing Switch Command Reference
9-20
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
clrlog
clrlog
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
Log: log
State: active, standby
Privilege: SUPER_GP
Example
Clear all event log files on the PXM45 card.
wilco.7.PXM.a > clrlog
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-21
Chapter 9
Troubleshooting Commands
clrportcnt
clrportcnt
Clear Port Counter
Clear counter values on a specific logical port.
Cards on Which This Command Runs
AXSM
Syntax
clrportcnt <ifNum>
Syntax Description
ifNum
The logical port number. The range for AXSM is 1–60.
Related Commands
clrportcnts, dspportcnt
Attributes
Log: log
State: active
Privilege: SUPER_GP
Example
Clear all the port counters on port 1.
flyers01.17.AXSM.a > clrportcnt 1
Cisco MGX 8850 Routing Switch Command Reference
9-22
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
clrportcnts
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
Log: log
State: active
Privilege: SUPER_GP
Example
Clear all the port counters on the current AXSM.
flyers01.17.AXSM.a > clrportcnts
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-23
Chapter 9
Troubleshooting Commands
clrxbaralm
clrxbaralm
Clear Crossbar Alarm—clear the crossbar alarms.
To see the alarms that clrxbaralm clears, execute dspxbaralarm or dspswalms. The clrxbaralm
command clears the alarms for either a specific switch plane or for all the switch planes on the active
switching card. In an MGX 8850 node, the switching slot is the slot number of the PXM45.
Cards on Which This Command Runs
PXM45
Syntax
clrxbaralm < * | [ slot plane ]>
Syntax Description
*
Enter an asterisk to clear all crossbar alarms on the active PXM45.
slot
The slot number of the crossbar planes. The slot number is 7 or 8.
plane
The range for plane numbers is 0–2.
Related Commands
dspxbaralm, dspswalms
Attributes
Log: log
State: active
Privilege: SUPER_GP
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 dspxbaralm.
pop20two.7.PXM.a > clrxbaralm 7 0
Cisco MGX 8850 Routing Switch Command Reference
9-24
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
clrxbarerrcnt
clrxbarerrcnt
Clear Crossbar Error Count—clear the counters for crossbar errors.
To see the errors that clrxbarerrcnt clears, execute dspxbarerrcnt. The clrxbarerrcnt command clears
the errors for either a specific switch plane or all the switch planes on the active switching card. In the
MGX 8850 node, the switching slot is the slot number of the PXM45.
Cards on Which This Command Runs
PXM45
Syntax
clrxbarerrcnt < * | [ slot plane ]>
Syntax Description
*
Enter an asterisk to clear all crossbar errors on the active PXM45.
slot
The slot number of the crossbar planes. The slot number is 7 or 8.
plane
The range for plane numbers is 0–2.
Related Commands
dspxbarerrcnt, cnfxbarerrthresh, dspxbarerrthresh, dspswalms
Attributes
Log: log
State: active, standby
Privilege: SUPER_GP
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 dspxbarerrcnt.
pop20two.7.PXM.a > clrxbarerrcnt 7 0
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-25
Chapter 9
Troubleshooting Commands
cnfalm
cnfalm
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:
•
Line type: SONET, DS3, E3, or PLCP
•
Tested layer: section, line, or path (for example, SONET line)
•
Test periods of 15 minutes and 24 hours
•
Degrees of error-time: errored seconds and severely errored seconds
•
Types of errors, including framing errors, code violations, and unavailable
•
Severity of alarm triggered when a threshold is crossed: minor or major
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
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.
line type
The line type is specified as one of the following keywords (including the hyphen):
-sonetsec (for SONET section)
-sonetline (for SONET line)
-sonetpath (for SONET path)
-ds3
-e3
-plcp
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.
Cisco MGX 8850 Routing Switch Command Reference
9-26
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
cnfalm
alarm
severity
A keyword and number to identify the severity of the alarm that is triggered when any
of the specified thresholds is crossed: 1 = minor alarm, and 2 = major alarm. Precede
the alarm severity with the appropriate keyword. For the alarm severity keyword for
each line type, see the first item in each of the lists follows. (For example, -secsev
refers to the severity of the section alarm on a SONET line.)
thresholds
The number of instances of whatever the keyword identifies. The range for each
threshold is 1 to 2^32-1. The keyword precedes each threshold. For example,
-lnsesf15 10 means 10 instances of severely errored framing seconds on a line during
a 15-minute period.
Thresholds for SONET Section
-secsev <Severity>
Severity of the alarm (1 = minor, 2 = major) for SONET
section.
-seces15 <ES15min>
Errored seconds during a 15-minute period.
-seces24 <ES24Hr>
Errored seconds during a 24-hour period.
-secses15 <SES15min>
Severely errored seconds during a 15-minute period.
-secses24 <SES24Hr>
Severely errored seconds during a 24-hour period.
-secsefs15 <SEFS15min> Severely errored frame seconds during a 15-minute period.
-secsefs24 <SEFS24Hr>
Severely errored frame seconds during a 24-hour period.
-seccv15 <UAS15min>
Unavailable seconds during a 15-minute period.
-seccv24 <UAS24Hr>
Unavailable seconds during a 24-hour period.
Thresholds for SONET Line
-lnsev <Severity>
Severity of the alarm (1 = minor, 2 = major) for SONET line.
-lnes15 <ES15min>
Errored seconds during a 15-minute period.
-lnes24 <ES24Hr>
Errored seconds during a 24-hour period.
-lnses15 <SES15min>
Severely errored seconds during a 15-minute period.
-lnses24 <SES24Hr>
Severely errored seconds during a 24-hour period.
-lncv15 <CV15min>
Code violations during a 15-minute period.
-lncv24 <CV24Hr>
Code violations seconds during a 24-hour period.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-27
Chapter 9
Troubleshooting Commands
cnfalm
-lnuas15 <UAS15min> Unavailable seconds during a 15-minute period.
-lnuas24 <UAS24Hr>
Unavailable seconds during a 24-hour period.
Thresholds for SONET Path
-sev
Severity of the alarm (1 = minor, 2 = major) for SONET path.
-es15 <ES15min>
Errored seconds during a 15-minute period.
-es24 <ES24Hr>
Errored seconds during a 24-hour period.
-ses15 <SES15min>
Severely errored seconds during a 15-minute period.
-ses24 <SES24Hr>
Severely errored seconds during a 24-hour period.
-cv15 <CV15min>
Code violations during a 15-minute period.
-cv24 <CV24Hr>
Code violations seconds during a 24-hour period.
-uas15 <UAS15min> Unavailable seconds during a 15-minute period.
-uas24 <UAS24Hr>
Unavailable seconds during a 24-hour period.
Thresholds for DS3
-dsev <severity>
Severity of the alarm (1 = minor, 2 = major) for DS3.
-lcv15 <LCV15min>
Code violations for a line during a 15-minute period.
-lcv24 <LCV24Hr>
Code violations for a line seconds during a 24-hour period.
-les15 <LES15min>
Line errored seconds during a 15-minute period.
-les24 <LES24Hr>
Line errored seconds during a 24-hour period.
-pcv15 <PCV15min>
P-bit coding violations for a line during a 15-minute period.
-pcv24 <PCV24Hr>
P-bit coding violations for a line during a 24-hour period.
-pes15 <PES15min>
P-bit errored seconds during a 15-minute period.
-pes24 <PES24Hr>
P-bit errored seconds during a 24-hour period.
-pses15 <PSES15min> P-bit severely errored seconds during a 15-minute period.
-pses24 <PSES24Hr>
P-bit severely errored seconds during a 24-hour period.
Cisco MGX 8850 Routing Switch Command Reference
9-28
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
cnfalm
-sefs15 <SEFS15min> Severely errored frame seconds during a 15-minute period.
-sefs24 <SEFS24Hr>
Severely errored frame seconds during a 24-hour period.
-uas15 <UAS15min>
Unavailable seconds during a 15-minute period.
-uas24 <UAS24Hr>
Unavailable seconds during a 24-hour period.
-dsev <severity>
Severity of the alarm (1 = minor, 2 = major) for DS3.
-lcv15 <LCV15min>
Code violations for a line during a 15-minute period.
-lcv24 <LCV24Hr>
Code violations for a line seconds during a 24-hour period.
-les15 <LES15min>
Line errored seconds during a 15-minute period.
-les24 <LES24Hr>
Line errored seconds during a 24-hour period.
Thresholds for E3
-sefs15 <SEFS15min> Severely errored frame seconds during a 15-minute period.
-sefs24 <SEFS24Hr>
Severely errored frame seconds during a 24-hour period.
-duas15 <UAS15min> Unavailable seconds during a 15-minute period.
-duast24 <UAS24Hr> Unavailable seconds during a 24-hour period.
Thresholds for PLCP
-psev <severity>
Severity of the alarm (1 = minor, 2 = major) for PLCP.
-bcv15 <CV15min>
Bipolar violation code violations during a 15-minute period.
-bcv24 <CV24Hr>
Bipolar violation code violations during a 24-hour period.
-bes15 <ES15min>
Bipolar violation errored seconds during a 15-minute period.
-bes24 <ES24Hr>
Bipolar violation errored seconds during a 24-hour period.
-bses15 <SES15min>
Bipolar violation severely errored seconds during a 15-minute period.
-bses24 <SES24Hr>
Bipolar violation severely errored seconds during a 24-hour period.
-psefs15 <SEFS15min> PLCP severely errored frame seconds during a 15-minute period.
-psefs24 <SEFS24Hr>
PLCP severely errored frame seconds during a 24-hour period.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-29
Chapter 9
Troubleshooting Commands
cnfalm
-puas15 <UAS15min>
PLCP unavailable seconds during a 15-minute period.
-puas24<UAS24Hr>
PLCP unavailable seconds during a 24-hour period.
Related Commands
dspalmcnf
Attributes
Log: log
State: active
Privilege: GROUP1
Example
Configure the following thresholds for triggering a major line-level alarm on line 2 in bay 1:
•
The line type is SONET line.
•
The bay is 1, and the line number is 2.
•
The severity of the triggered alarm is major.
•
The errored seconds for a 15-minutes period and a 24-hour period are 60 and 600, respectively.
•
The severely errored seconds for a 15-minutes period and a 24-hour period are 3 and 7, respectively.
•
The code violations for a 15-minutes period and a 24-hour period are 75 and 750, respectively.
•
The unavailable seconds for a 15-minutes period and a 24-hour period are 10 and 10, respectively
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 10
Check the configuration by executing dspalmcnf for the line number and line type in this example.
node4.1.AXSM.a > dspalmcnf -sonetline 1.2
LineNum: 1.2
Line Stat Alarm Severity: No Alarm
15min Threshold
24hr Threshold
Line ESs : 60
600
Line SESs: 3
7
Line CVs : 75
750
Line UASs: 10
10
Cisco MGX 8850 Routing Switch Command Reference
9-30
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
cnfdiag
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.
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:
•
A 1.2 Gbps Cellbus
•
A 45 Gbps MGX 8850 Release 2.1 bus
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:
•
Crossbar loopback test on QE1210, Humvee, and Crossbar paths
Standby State
When you enable online diagnostics on a standby PXM45 card, the following tests run:
•
Framer loopback test on QE1210, ATLAS, and OC-3 Framer paths
•
Crossbar loopback walk test on QE1210, Humvee, and Crossbar paths
AXSM Online Diagnostics
Active State
When you enable online diagnostics on an active AXSM card, the following test runs:
•
Crossbar loopback test on QE, Humvee, and Crossbar paths
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-31
Chapter 9
Troubleshooting Commands
cnfdiag
Standby State
When you enable online diagnostics on a standby AXSM card, the following tests run:
•
Crossbar loopback walk test on QE, Humvee, and Crossbar paths
•
Back card loopback test on T3/E3 lines
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 an active card fails, the shelf manager must stop the diagnostics on the standby card
immediately, reset, and allow normal arbitration to occur.
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.
Processor Subsystem Test
•
Flash EPROM
•
SDRAM
•
SCC
•
PCI Bridge
Component Level Test
•
PIO
•
FPGA
•
LEDs
•
Fan / Power Supply
•
BRAM / RTC
•
SEEPROM / NovRAM Checksum Test
ASIC Tests
•
QE1210 Register and DMA RAM Test
•
CBC Register Test
•
Humvee Register Test
•
Switch ASIC Register Test
•
Atlas Register and RAM Test
•
Framer Register and RAM Test
UI S3/S4 Back card test
Cisco MGX 8850 Routing Switch Command Reference
9-32
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
cnfdiag
•
5.
NovRAM Checksum Test
Cell Path Test
•
CBC Cell Path Test - Backplane Side
•
Framer Cell Path Test - Port Side
•
Humvee / Transceiver / Crossbar Switch Cell Path Test
AXSM Offline Diagnostics
1.
I/O PLD data bus test
2.
Skystone Framer register & RAM test.
3.
Humvee ASIC register test
4.
CBC register test
5.
ATMizer RAM test
6.
QE48 register and RAM test
7.
NovRAM checksum test
8.
Flash EPROM checksum test
Syntax
cnfdiag <slot> <onEnb> <offEnb>
[<offCover> <offStart> <offDow>]
Syntax Description
slot
The slot of the card for which to configure the diagnostics.
onEnb
Enable or disable online diagnostics. The default is disable.
offEnb
Enable or disable offline diagnostics. The default is disable.
offCover
Set the offline diagnostics coverage time to light, medium, or full.
•
light = 5 minutes or less
•
medium = 30 minutes or less
•
full = 60 minutes or more
offStart
Set the time for the offline diagnostics to begin using 24 hour time. The format is:
hh:mm. For example: 03:45 or 22:30.
offDow
Sets the day of the week for the offline diagnostics to run.The format is SMTWTFS.
For example: -M-W--- is Mondays and Wednesdays only
Cards on Which This Command Runs
PXM45
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-33
Chapter 9
Troubleshooting Commands
cnfdiag
Related Commands
cnfdiagall, dspdiagcnf
Attributes
Log: no log
State: active
Privilege: SERVICE_GP
Example
cnfdiag 7 enable disable light 22:30 -M-W-F-
Cisco MGX 8850 Routing Switch Command Reference
9-34
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
cnfdiagall
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
See the cnfdiag command for a detailed description of MGX 8850 diagnostics.
Syntax
cnfdiagall <onEnb> <offEnb>
[<offCover> <offStart> <offDow>]
Syntax Description
onEnb
Enables online diagnostics.
offEnb
Enables offline diagnostics.
offCover
Sets the offline diagnostics coverage time to light, medium, or full.
offStart
•
light = 5 minutes or less
•
medium = 30 minutes or less
•
full = unlimited
Sets the time for the offline diagnostics to begin using 24 hour time. The format is:
hh:mm
For example: 03:45 or 22:30.
offDow
Sets the day of the week for the offline diagnostics to run. The format is SMTWTFS.
Enter a dash (-) for days on which you do not want diagnostics to run. For example:
-M-W--- is Mondays and Wednesdays only
Cards on Which This Command Runs
PXM45
Related Commands
cnfdiag, dspdiagcnf
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-35
Chapter 9
Troubleshooting Commands
cnfdiagall
Attributes
Log: no log
State: active, standby
Privilege: SERVICE_GP
Example
cnfdiagall enable disable light 22:30 -M-W-F-
Cisco MGX 8850 Routing Switch Command Reference
9-36
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
cnfpnportloscallrel
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
The portid represents the PNNI logical port and has the format
[shelf.]slot[:subslot].port[:subport]. See also PNNI Format, page 9-3.
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
Log: log
State: active
Privilege: SUPER_GP
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 :enabled
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-37
Chapter 9
Troubleshooting Commands
cnfxbarerrthresh
cnfxbarerrthresh
Configure Crossbar Error Threshold—specify a threshold for a particular crossbar error
The Syntax Description contains a list of possible errors. A crossbar error threshold consists of:
Note
•
A period for counting errors
•
Severity of the resulting alarm (minor, major, and critical)
•
Upper and lower counts for each alarm severity
The default settings for crossbar error thresholds are optimal for nearly all applications. The
dspxbarerrthresh command shows the existing thresholds. If necessary, you can change thresholds
through the cnfxbarerrthresh command.
Cards on Which This Command Runs
PXM45
Syntax
cnfxbarerrthresh <errtype(1..9)> <threshtime> <severity(0..2)> <clrcount> <almcount>
Syntax Description
errtype
A number that identifies the type of error, as follows:
1.
Loss of synchronization (LossOfSync).
2.
Transceiver error (TranscieverErr)
3.
DisparityErr—an accumulation of five ASIC-level errors
4.
ParityErr—a parity error in the switch frame as a whole
5.
HeaderCRCErr—a CRC error for the switch frame header
6.
PayloadCRCErr—a CRC error for the switch frame payload
7.
RemapTwiceErr
8.
RemapRecurrErr
9.
Backpressure parity error (B.P.ParityErr)—a parity error in the signaling for
backpressure
threshtime
The number of milliseconds over which the system counts errors.
severity
The severity of the alarm resulting from the error count per threshold time.
clrcnt
The clear count is the number of errors below which the alarm changes to the next
lowest severity. For example, the system clears a minor alarm for a particular type of
error when the number of errors goes to 0. Similarly, if clrcnt for a major alarm is 30,
the alarm goes to minor when the count drops below 30.
Cisco MGX 8850 Routing Switch Command Reference
9-38
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
cnfxbarerrthresh
almcnt
The number of errors for an alarm severity above which the alarm goes to the next
highest severity.
Usage Guidelines for cnfxbarerrthresh
You can change the threshold for only one type of error at a time. Also, you must enter all parameters of
the threshold whether or not you change them. For example, if you want to change only the duration of
errored milliseconds, you must include the existing parameters. Therefore, you probably need to execute
dspxbarerrthresh before cnfxbarerrthresh.
Related Commands
dspxbarerrthresh
Attributes
Log: log
State: active
Privilege: SERVICE_GP
Example
For Loss of Sync, set the clear count for critical alarms to 200.
pop20two.7.PXM.a > cnfxbarerrthresh 1 2000 2 200 301
In 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
MGX8850
Thresh
Device Error
Time
Type
(msec)
-------------------- -----LossOfSync
2000
System Rev: 02.01
Dec. 05, 2000 02:29:17 GMT
Node Alarm: MAJOR
CROSSBAR ERROR CONFIGURATION
-- MINOR --- MAJOR --- CRITICAL -Clear Alarm
Clear Alarm
Clear Alarm
Count Count
Count Count
Count Count
----- --------- --------- ----0
3
4
15
200
301
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-39
Chapter 9
Troubleshooting Commands
cnfxbarmgmt
cnfxbarmgmt
Configure Crossbar Management—configure load sharing
The application for is a redundant PXM45 setup. It allows the MGX 8850 to maintain its peak throughput
of 45 Gbps without requiring a switchover to the standby cards if a switch ASIC becomes defective. In
this scheme, one of the switch ASICs on the standby PXM45 takes over the switching for the defective
ASIC on the active PXM45.
Note
On an MGX 8850 node, this command applies to Release 2.1 or higher.
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.
dspndalms
2.
dspswalms
3.
dspxbaralm
4.
dspxbarerrcnt
Cards on Which This Command Runs
PXM45
Syntax
cnfxbarmgmt
<loadSharing>
<autoShutdown>
<planeAlarmThresh>
Syntax Description
loadSharing
0 = disable load sharing.
1 = enable load sharing.
However, if a bad switch ASIC already exists, the switch blocks the
command.
–1 = force load sharing to be disabled
when one or more bad switch ASICs exist on the active PXM45.
autoShutdown
A 0 disables automatic shut-down. A 1 enables automatic shut-down. The
default is disabled.
planeAlarmThresh
An alarm threshold for declaring that a switch plane is bad. Each unit of the
threshold represents a link between the switch ASIC and the card. (The
determination of a bad link depends on the crossbar error threshold.)
If the number of bad links reaches the threshold, the active PXM45 shuts
down the ASIC and shifts the switching load to the standby PXM45. The
range for planeAlarmThresh is 1–32.
Cisco MGX 8850 Routing Switch Command Reference
9-40
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
cnfxbarmgmt
Related Commands
dspxbarmgmt, dspxbarerrthresh, dspxbarerrcnt
Attributes
Log: log
State: active
Privilege: SERVICE_GP
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 5
pop20two.7.PXM.a > dspxbarmgmt
pop20two
MGX8850
Load Sharing: Enable
Auto Shutdown: Enable
Plane Alarm Threshold: 5
System Rev: 02.01
Dec. 06, 2000 00:44:20 GMT
Node Alarm: MAJOR
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-41
Chapter 9
Troubleshooting Commands
conntrace
conntrace
Call Control Operations
Trace an established connection and display the result.
Cards on Which This Command Runs
PXM45
Syntax
conntrace <portid>
callref
[EndPtRef]
Syntax Description
portid
The portid represents the PNNI logical port and has the format
[shelf.]slot[:subslot].port[:subport]. See also PNNI Format, page 9-3.
callref
Call reference for the call.
EndPtRef
Endpoint reference for a p2mp call. If no endpoint reference is specified, this is a p2p
call.
Related Commands
pathtraceport, pathracenode, pathtraceie
Attributes
Log: log
State: active
Privilege: SUPER_GP
Examples
Result:Succ/Fail Reason: " Desc"
InterfaceId: "--" EndptRef: "--"
Originating Interface VPI: " --"
Originating Interface VCI: " --"
Originating Interface CallRef: " --"
NodeId Egress Port Vpi Vci CallRef PhysPortid
XXXX ZZZZ aaa bbb cccc eeee
XXXX ZZZZ aaa bbb cccc eeee
Terminating Interface VPI: " --"
Terminating Interface VCI: " --"
Terminating Interface CallRef: " --"
Cisco MGX 8850 Routing Switch Command Reference
9-42
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
copycons
copycons
Copy Channels (Debugging Command)
Copies one or more endpoints from a specified endpoint. The number of entries to copy is specified using
the -num option.
This 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. First add a slave endpoint and then a master endpoint.
2. Copy the slave endpoints first using copychans.
3. Copy the master endpoints next using copychans.
Caution
Improper use of this command can result in dangling (unpaired) endpoints in the network.
Cards on Which This Command Runs
AXSM
Syntax
copycons <source> <destn>
[-rem <remote Conn Id>]
[-num <num. conns to add>]
[-verbose <1|0>]
Syntax Description
source
source ID: The endpoint that is to be used as a template for copying, specified in the
format: ifNum.vpi.vci
destn
destination ID: The endpoint to paste the copied connection template into, specified
in the format: ifNum.vpi.vci
-num
The number of consecutive endpoints to be added, starting from destn endpoint.
Default: 1
-rem
The remote connection ID specified in the format: ifNum.vpi.vci
-verbose
Prints the status of cloning process if enabled. Default is disabled.
verbose: Enable(1) | Disable (0)
Related Commands
addcon, delcon
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-43
Chapter 9
Troubleshooting Commands
copycons
Attributes
Log: log
State: active
Privilege: SERVICE_GP
Example
MGX8850.1.11.AXSM.a > copycons 3.10.50 3.10.60 -num 10
Cisco MGX 8850 Routing Switch Command Reference
9-44
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
core
core
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):
•
It displays:
– Whether core files from the processor card exist, the reset reason that triggered the core dump
as well as a list of all possible reset reasons, a time stamp, and so on
– Status of core dumps in progress
– The current configuration of various parameters
– A subset of core-related information on the CLI of a service module
•
It lets you configure a wide variety of applicable functions.
•
It can take an immediate action, such as aborting an active core dump or acquiring a snapshot of a
card’s core memory.
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:
•
For the PXM, the controller writes the RAM contents as a raw data image to an unmarked part of
the hard disk on the back card. Before doing so, the processor compares the reset reason to the core
mask. For any match, it writes core memory to the unmarked part of the disk drive. The drive holds
only two raw data images for the PXM, so you must copy that data to a zip file before it is
overwritten. Using parameters described in the section, “Syntax Description (PXM45)," you can
save an image to a zipped file having a name you choose, as follows:
specified_name.zip
•
For any model of the AXSM, a core dump can occur during card boot-up after a reset. The processor
compares the reset reason to the core mask for that slot. For any match, core memory is written to a
file in the root directory of the C drive. The zipped file has the following format:
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
Syntax
core (optional parameters—see Syntax Description for AXSM or PXM45)
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-45
Chapter 9
Troubleshooting Commands
core
Syntax Description (AXSM)
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:
•
A list of all possible reset reasons
•
Whether the reset is enabled to trigger a core dump
•
The associated hexadecimal value of each reason
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:
•
A list of all possible reset reasons
•
Whether the reset is enabled to trigger a core dump
•
The associated hexadecimal value of each reason
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."
Cisco MGX 8850 Routing Switch Command Reference
9-46
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
core
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
timeInSecs
You 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.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-47
Chapter 9
Troubleshooting Commands
core
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.
Cisco MGX 8850 Routing Switch Command Reference
9-48
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
core
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:
•
You may have isolated a problem and want to save the time required to write RAM contents to disk.
•
The traffic on a card may be of such high priority that you do not want to dump core memory to disk.
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 “can't be turned
ON.” A reset reason that cannot trigger a core dump removes pertinent information from memory.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-49
Chapter 9
Troubleshooting Commands
core
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:
•
Two or three core dumps begin, but you do not want the switch to take the time or resources to
complete these processes. Additionally, one core dump may be crucial, so to ensure that it does not
time out, you could abort one or two of the other core dumps.
•
You could have removed redundancy from a pair of card slots but did not disable core dumps on a
card where you do not want core dumps. If a core dump begins at such a slot, you can abort the core
dump from the PXM then change the configuration on the service module after it comes up.
Related Commands
ftp, ll, cd, dsplog (use the dsplog command with the following parameter: -mod CRDMP)
Attributes
Log: log
State: active, standby, init
Privilege: SERVICE_GP
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 > core
Saved PXM core images:
Bin Reset Reason
Type
Slot
Dump Time
-------------------------------------------------------------------------------0
Manual dump
POPEYE 2
8
WED JAN 30 19:28:13 2002
1
Software Error Reset
POPEYE 2
8
TUE FEB 27 17:48:24 2001
The 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 clear
All the raw core dump images will be erased.
core: Do you want to proceed (Yes/No)? y
Cisco MGX 8850 Routing Switch Command Reference
9-50
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
core
Check the mask and observe it has returned to the default.
M8850_LA.8.PXM.a > core
Saved 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 gradual display of dots across the screen shows the
progress of the dump to disk. Check the status by using the core command without parameters. The
display shows that a snapshot occurred (“Manual dump”). Save the core dump to a zipped file called
test_1.zip and confirm that it resides on the C drive.
M8850_LA.8.PXM.a > core hot-dump
core: Do you want to proceed (Yes/No)? y
Dumping PXM Core Image[0]:
................................................................................
Done.
M8850_LA.8.PXM.a > core
Saved PXM core images:
Bin Reset Reason
Type
Slot
Dump Time
-------------------------------------------------------------------------------0
Manual dump
POPEYE 2
8
WED JAN 30 19:28:13 2002
1
Software Error Reset
POPEYE 2
8
TUE FEB 27 17:48:24 2001
The 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 >
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
------------19517299
JAN-31-2002
time
-----22:42:22
name
-------test_1.zip
In the file system :
total space : 819200 K bytes
free space : 689221 K bytes
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-51
Chapter 9
Troubleshooting Commands
core
This 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 mask
Automatic core dumping is ** disabled ** for this slot.
The current core mask is 0x64e0.
OFF
OFF
OFF
OFF
OFF
ON
ON
ON
OFF
OFF
ON
OFF
OFF
ON
ON
OFF
OFF
OFF
00001
00002
00004
00008
00010
00020
00040
00080
00100
00200
00400
00800
01000
02000
04000
08000
10000
20000
not used (can't be turned ON)
DRAM Parity Error
WatchDog Timeout Reset
Resource Overflow
Clear All Configuration (can't be turned ON)
Missing Task
Reset because of PXM Low Voltage
Reset By Event Log Task
Reset from Shell
Unknown
Reset from PXM
Reset System (can't be turned ON)
Switch Core Card
Secondary Cache Error
Software Error Reset
S/W reset due to upgrade (can't be turned ON)
Restore All Configuration (can't be turned ON)
Device Driver Error
Set 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 c
Automatic core dumping is ** disabled ** for this slot.
The current core mask is 0xc.
OFF
OFF
ON
ON
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
00001
00002
00004
00008
00010
00020
00040
00080
00100
00200
00400
00800
01000
02000
04000
08000
10000
20000
not used (can't be turned ON)
DRAM Parity Error
WatchDog Timeout Reset
Resource Overflow
Clear All Configuration (can't be turned ON)
Missing Task
Reset because of PXM Low Voltage
Reset By Event Log Task
Reset from Shell
Unknown
Reset from PXM
Reset System (can't be turned ON)
Switch Core Card
Secondary Cache Error
Software Error Reset
S/W reset due to upgrade (can't be turned ON)
Restore All Configuration (can't be turned ON)
Device Driver Error
Cisco MGX 8850 Routing Switch Command Reference
9-52
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
core
Reset 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 default
Automatic core dumping is ** disabled ** for this slot.
The current core mask is 0x262ee.
OFF
ON
ON
ON
OFF
ON
ON
ON
OFF
ON
OFF
OFF
OFF
ON
ON
OFF
OFF
ON
00001
00002
00004
00008
00010
00020
00040
00080
00100
00200
00400
00800
01000
02000
04000
08000
10000
20000
not used (can't be turned ON)
DRAM Parity Error
WatchDog Timeout Reset
Resource Overflow
Clear All Configuration (can't be turned ON)
Missing Task
Reset because of PXM Low Voltage
Reset By Event Log Task
Reset from Shell
Unknown
Reset from PXM
Reset System (can't be turned ON)
Switch Core Card
Secondary Cache Error
Software Error Reset
S/W reset due to upgrade (can't be turned ON)
Restore All Configuration (can't be turned ON)
Device Driver Error
M8850_LA.8.PXM.a >
Display the redundancy policy.
M8850_LA.8.PXM.a > core red-policy
Non-redundant SMs are allowed to dump core.
Examples (AXSM)
Check the core mask on the current AXSM.
M8850_LA.1.AXSM.s > core mask
Automatic core dumping is enabled for this slot.
The current core mask is 0x262ee.
OFF
ON
ON
ON
OFF
ON
ON
ON
OFF
ON
OFF
OFF
OFF
ON
ON
OFF
OFF
ON
00001
00002
00004
00008
00010
00020
00040
00080
00100
00200
00400
00800
01000
02000
04000
08000
10000
20000
not used (can't be turned ON)
DRAM Parity Error
WatchDog Timeout Reset
Resource Overflow
Clear All Configuration (can't be turned ON)
Missing Task
Reset because of PXM Low Voltage
Reset By Event Log Task
Reset from Shell
Unknown
Reset from PXM
Reset System (can't be turned ON)
Switch Core Card
Secondary Cache Error
Software Error Reset
S/W reset due to upgrade (can't be turned ON)
Restore All Configuration (can't be turned ON)
Device Driver Error
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-53
Chapter 9
Troubleshooting Commands
core
Set the core mask to 0xc and note the result in the display.
M8850_LA.1.AXSM.s > core mask c
Automatic core dumping is enabled for this slot.
The current core mask is 0xc.
OFF
OFF
ON
ON
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
00001
00002
00004
00008
00010
00020
00040
00080
00100
00200
00400
00800
01000
02000
04000
08000
10000
20000
not used (can't be turned ON)
DRAM Parity Error
WatchDog Timeout Reset
Resource Overflow
Clear All Configuration (can't be turned ON)
Missing Task
Reset because of PXM Low Voltage
Reset By Event Log Task
Reset from Shell
Unknown
Reset from PXM
Reset System (can't be turned ON)
Switch Core Card
Secondary Cache Error
Software Error Reset
S/W reset due to upgrade (can't be turned ON)
Restore All Configuration (can't be turned ON)
Device Driver Error
Determine if core dump is enabled for the current slot.
M8850_NY.1.AXSM.s > core
Automatic core dumping is enabled for this slot.
Saved core images are on PXM's hard disk (C:/).
M8850_NY.1.AXSM.s >
Cisco MGX 8850 Routing Switch Command Reference
9-54
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dbgcon
dbgcon
Debug Connection—enables or disables logging of SPVC-related errors.
Enable or disable the SPVC log.To see whether the SPVC log is enabled, use dspcons-dbg.
Cards on Which This Command Runs
PXM45
Syntax
dbgcon
<enable | disable>
Syntax Description
enable | disable
Enable or disable the SPVC log. Type the entire word. The default is disabled.
Related Commands
dspcons-dbg
Attributes
Log: no log
State: active, standby
Privilege: SERVICE_GP
Example
Enable the SPVC log.
MGX8850.8.PXM.a > dbgcon enable
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-55
Chapter 9
Troubleshooting Commands
delchanloop
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
Syntax
delchanloop <ifNumber> <vpi> <vci>
Syntax Description
ifNumber
The logical port number. The range for AXSM is 1–60.
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
Log: log
State: active, standby
Privilege: SERVICE_GP
Example
Remove the loopback from VPI/VCI 1 50 on logical port 4.
pop20two.1.AXSM.a > delchanloop 4 1 50
Cisco MGX 8850 Routing Switch Command Reference
9-56
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dellnloop
dellnloop
Delete Line Loop
Remove the line loopback state from a line.
Cards on Which This Command Runs
AXSM
AXSM Syntax
dellnloop <-ds3 | -sonet> <bay.line>
Note
For AXSM cards, the keyword ds3 applies to both T3 and E3 line types.
Syntax Description
-ds3 | -sonet bay.line
Specifies a SONET line (OC-3c, OC-12c, OC-48c) or a DS3 line (E3 or T3),
the bay (1 for upper or 2 for lower), and the line number. The line number
ranges from 1 to the highest number line on the back card.
Related Commands
addlnloop
Attributes
Log: log
State: active
Privilege: GROUP1
Example
Deleting a DS3 loopback line.
MGX8850.1.11.AXSN.a > dellnloop -ds3 1.6 -lpb 3
Line loop-back status will be changed.
Do you want to proceed (Yes/No) ?
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-57
Chapter 9
Troubleshooting Commands
dncon
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
Syntax
dncon <ifNum> <vpi> <vci>
Syntax Description
ifNum
The logical port number. The range for AXSM is 1–60.
vpi
Virtual path identifier in the range 1–255 for a UNI or 1–4095 for an NNI.
vci
For a virtual connection (VCC), the VCI range is 0–65535. For a virtual path
connection (VPC), the VCI is always 0.
Related Commands
upcon
Attributes
Log: log
State: active
Privilege: GROUP1
Cisco MGX 8850 Routing Switch Command Reference
9-58
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dnln
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
Remove connections. Use delcon or delcons.
Step 2
Remove any resource partitions. Use dsprscprtn to see existing partitions and delrscprtn to remove
partitions.
Step 3
Remove all logical ports. Use dspports to see existing logical ports on the line and delport to remove
logical ports.
Cards on Which This Command Runs
AXSM
Syntax
dnln <bay.line>
Syntax Description
bay.line
Specifies a SONET line (OC-3c, OC-12c, OC-48c) or a DS3 line (E3 or T3), the bay
(1 for upper or 2 for lower), and the line number. The line number ranges from 1 to
the highest number line on the back card.
Related Commands
dspln, dsplns, cnfln, upln
Attributes
Log: log
State: active
Privilege: GROUP1
Example
De-activate line 1 in bay 1.
MGX8850.1.AXSM.a > dnln 1.1
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-59
Chapter 9
Troubleshooting Commands
dnport
dnport
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.
Cards on Which This Command Runs
AXSM
Syntax
dnport <ifNum>
Syntax Description
ifNum
A logical port (interface) number. Only one logical port is allowed if the line operates
as a UNI or NNI. For the virtual network to network interface (VNNI), multiple ports
can exist on a line. For AXSM, the range 1–60.
Use dspports or dspport as needed to determine the need to disable a port.
Related Commands
dspport, dspports, upport
Attributes
Log: log
State: active
Privilege: GROUP1
Example
Disable port 1 on the current card.
MGX8850.1.AXSM.a > dnport 1
Cisco MGX 8850 Routing Switch Command Reference
9-60
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspalm
dspalm
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 Syntax
dspalm -ds3|-e3|-sonet|-ds1|-e1 <bay.Line>
Syntax Description
-ds3 | -e3 | -sonet
-ds1 | -e1
Specifies a SONET line (OC-3c, OC-12c, OC-48c), DS3 line, E3
line. or DS1 line.
<bay>
The bay (1 for upper or 2 for lower), and the line number. The line
number ranges from 1 to the highest number line on the back card.
<line>
Line number:
•
For OC12: 1
•
For OC3: 1–4
•
T3, E3: 1–8
Related Commands
cnfalm, clralm, dspalms, dspalmcnt
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-61
Chapter 9
Troubleshooting Commands
dspalm
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.1
Line Number
: 1.1
Section Alarm State
: LOS
Line Alarm State
: Clear
Path Alarm State
: Clear
Section Stat Alarm State: TotalESs,TotalSESs,TotalSEFSs,CurrentESs,CurrentSESss
Line Stat Alarm State
: TotalUASs,CurrentUASs
Path Stat Alarm State
: TotalUASs,CurrentUASs
LOCD Alarm State
: Clear
APS Alarm State
: N/A
On 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.1
Line Number
: 1.1
Section Alarm State
: LOS
Line Alarm State
: Clear
Path Alarm State
: Clear
Section Stat Alarm State: CurrentESs,CurrentSESs,CurrentSEFSs
Line Stat Alarm State
: CurrentSESs,CurrentUASs
Path Stat Alarm State
: CurrentSESs,CurrentUASs
LOCD Alarm State
: Clear
APS Alarm State
: N/A
Cisco MGX 8850 Routing Switch Command Reference
9-62
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspalmcnf
dspalmcnf
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
Syntax
dspalmcnf
-sonetsec|-sonetline|-sonetpath|-ds3|-e3|-plcp <bay.line>
Syntax Description
-sonetsec
-sonetline
-sonetpath
-ds3-e3
-plcp
bay.line
Keywords that specify the type of alarms to display:
•
-sonetsec – Displays the section alarms for the given sonet line (bay.line).
•
sonetline – Displays the line alarms for the given sonet line (bay.line).
•
-sonetpath –Displays the path alarms for the given sonet line (bay.line).
•
-ds3 – Displays the statistical alarms for the given DS3 line (bay.line).
•
-e3 – Displays the statistical alarms for the given E3 line (bay.line).
•
-plcp – Displays the PLCP alarms for the given line (bay.line). Physical Layer
Convergence Procedure (PLCP) is the specification that maps ATM cells into
physical media, such as T3 or E3, and defines certain management information.
Specifies the type of line, 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
cnfalm, dspalm, dspalms
Attributes
Log: no log
State: active, standby,
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-63
Chapter 9
Troubleshooting Commands
dspalmcnf
Examples
Display alarm configuration for AXSM cards.
MGX8850.1.AXSM.a > dspalmcnf -sonetline 1.2
LineNum: 1.2
Line Stat Alarm Severity: No Alarm
15min Threshold
24hr Threshold
Line ESs : 60
600
Line SESs: 3
7
Line CVs : 75
750
Line UASs: 10
10
MGX8850.1.AXSM.a > dspalmcnf -sonetsec 1.1
LineNum: 1.1
Section Stat Alarm Severity: No Alarm
15min Threshold
24hr Threshold
Section ESs :
60
600
Section SESs :
3
7
Section SEFSs:
3
7
Section CVs :
75
750
Cisco MGX 8850 Routing Switch Command Reference
9-64
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspalmcnt
dspalmcnt
Display Alarm Counters
Displays the performance monitoring alarm counters for either a SONET or DS3 line.
Cards on Which This Command Runs
AXSM
AXSM Syntax
dspalmcnf -ds3|e3|-plcp|-sonet|ds1|-e1 <bay.line >
Syntax Description
-ds3
e3
-plcp
-sonet
ds1
-e1
Keywords that specify the type of alarm counters (see dspalmcnf for definitions) to
display for the given line (bay.line) on an AXSM card.
bay.line
Specifies the type of line, 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
clralmcnt
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Examples
Display the alarm count for T3 line 1 in bay 1.
MGX8850.11.AXSM.a > dspalmcnt -ds3 1.1
Line Num:
2.1
CurrentLCV :
9109365
CurrentLES :
13
CurrentPCV :
1
CurrentPES :
1
CurrentPSES:
0
CurrentSEFS:
11
CurrentUAS :
0
Num of LOS :
1
Num of OOF :
1
Num of RAI :
0
Num of CCV :
0
Num of FE :
0
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-65
Chapter 9
Troubleshooting Commands
dspalmcnt
Display SONET line 1 in bay 1.
MGX8850.6.AXSM.a > dspalmcnt -sonet 1.1
Line Num:
1.1
Elapsed Time (in sec):
1634
Section PM:
----------Num of LOSs:
1
Num of LOFs:
1
CurrentESs:
0
CurrentSESs:
0
CurrentSEFSs:
1
CurrentCVs:
1
Line PM:
-------Num of AISs:
0
Num of RFIs:
0
Near End
Far End
CurrentESs :
1
CurrentESs :
CurrentSESs:
0
CurrentSESs:
CurrentCVs :
1
CurrentCVs :
CurrentUASs:
0
CurrentUASs:
Path PM:
-------Num of AISs:
1
Num of RFIs:
1
Near End
Far End
CurrentESs :
0
CurrentESs :
CurrentSESs:
0
CurrentSESs:
CurrentCVs :
0
CurrentCVs:
CurrentUASs:
0
CurrentUASs:
1
0
1
0
0
0
0
0
Cisco MGX 8850 Routing Switch Command Reference
9-66
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspalms
dspalms
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
Syntax
dspalms
Syntax Description
This command takes no parameters.
Related Commands
dspalm, clralm
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Example
Display alarms for the lines on the current AXSM card.
MGX8850.1.AXSM.a > dspalms
Line Number: 1.1
Alarm State
Section : LOS
Line
: Clear
Path
: Clear
Statistical Alarm State
Section : TotalESs,TotalSESs,TotalSEFSs,CurrentESs,CurrentSESs,CurrentSEFSs
Line
: TotalSESs,TotalUASs,CurrentUASs
Path
: TotalSESs,TotalUASs,CurrentUASs
LOCD Alarm : Clear
Line Number: 1.2
Alarm State
Section : LOS
Line
: Clear
Path
: Clear
Statistical Alarm State
Section : TotalSESs,TotalSEFSs,CurrentESs,CurrentSESs,CurrentSEFSs
Line
: TotalSESs,TotalUASs,CurrentUASs
Path
: TotalSESs,TotalUASs,CurrentUASs
LOCD Alarm : Clear
Line Number: 2.1
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-67
Chapter 9
Troubleshooting Commands
dspalms
Alarm State
Section : Clear
Line
: Clear
Path
: Clear
Statistical Alarm State
Section : Clear
Line
: Clear
Path
: Clear
LOCD Alarm : Clear
Line Number: 2.2
Alarm State
Section : Clear
Line
: Clear
Path
: Clear
Statistical Alarm State
Section : Clear
Line
: Clear
Path
: Clear
LOCD Alarm : Clear
Cisco MGX 8850 Routing Switch Command Reference
9-68
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspbecnt
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
Log: no log
State: active
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-69
Chapter 9
Troubleshooting Commands
dspcd
dspcd
Display Card
Display the following information about a card:
Note
•
Hardware serial number.
•
Firmware revision level. (See the loadrev description for an explanation of how to interpret the
revision filed.) If a card has no firmware, the display shows a version number of 0.0.0.
•
Status, possibly including the reason for the last reset (FunctionModuleResetReason) and state of
the integrated alarm (cardIntegratedAlarm).
•
For a service module only, a count of configured lines, ports, and connections.
The connection count includes control VCs when you execute dspcd on the CLI of a service module.
However, when you execute dspcd or dsppnport(s) on the CLI of the controller card, the display
does not include control VCs.
•
For a service module only: which physical lines constitute a port group and the maximum number
of connections in that port group. A port group consists of one to many physical lines. This
maximum connection count is a function of the hardware interface type (OC-3, OC-12, and so on).
The port group information also shows the number of existing SVCs, SPVCs, and SPVPs.
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
Syntax
dspcd
Syntax Description
This command does not take parameters.
Related Commands
dspcds, version
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
9-70
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcd
Examples
Display card details for the current PXM45.
Note
The A1 at the end of the primary software revision and boot firmware revision numbers shows that
these versions are pre-release. Refer to the setrev description for details.
MGX8850.7.PXM.a > dspcd
MGX8850
System Rev: 02.00
MGX8850
Slot Number
7
Redundant Slot: 8
Front Card
---------Inserted Card:
PXM45
Reserved Card:
PXM45
State:
Active
Serial Number:
SAK0405008B
Prim SW Rev:
2.0(246)A1
Sec SW Rev:
2.0(246)A1
Cur SW Rev:
2.0(246)A1
Boot FW Rev:
2.0(168)A1
800-level Rev:
18
Orderable Part#:
800-06147-01
CLEI Code:
0000000000
Reset Reason:
On Reset From Shell
Card Alarm:
NONE
Failed Reason:
None
Miscellaneous Information:
MGX8850
MGX8850
Upper Card
----------
Lower Card
----------
UI Stratum3
UI Stratum3
Active
SAK0325009M
--------03
800-05787-01
È
PXM HardDiskDrive
PXM HardDiskDrive
Active
12345678901
--------22
800-12345-99
1234567898
System Rev: 02.00
Crossbar Slot Status:
Aug. 02, 2000 23:39:06 GMT
Node Alarm: CRITICAL
Aug. 02, 2000 23:39:06 GMT
Node Alarm: CRITICAL
Present
Alarm Causes
-----------NO ALARMS
Display card details for the current AXSM-1-2488.
MGX8850.1.AXSM.a > dspcd
Front Card
----------
Upper Card
----------
Card Type:
AXSM-1-2488
SMFSR-1-2488
---
State:
Active
Present
Undefined
Serial 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
---
Lower Card
------------
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-71
Chapter 9
Troubleshooting Commands
dspcd
Reset Reason:On Power up
Card SCT Id: 2
#Lines #Ports #Partitions
#SPVC
#SVC
------ ------ ----------- ------- ------1
1
1
2
1
Port Group[1]:
#Chans supported:32512
Port Group[2]:
#Chans supported:32512
Port Group[3]:
#Chans supported:32512
Port Group[4]:
#Chans supported:32512
Lines:1.1
Lines:1.2
Lines:2.1
Lines:2.2
Cisco MGX 8850 Routing Switch Command Reference
9-72
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcdalms
dspcdalms
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:
•
Line (dsplns and dspln)
•
Port (dspports and dspport)
•
Feeder (dspfdr, dspfdrs, and dspfdrstat)
•
Connection (dspcons and dspcon)
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:
•
Critical, indicating complete, non-recoverable failure, loss of data, and do on. The failed entity must
be restored. A power failure or a disconnected line is an example.
•
Major, indicating service-affecting errors. This event indicates that a major service is damaged or
lost, but the existing traffic is not affected.
•
Minor, indicating non-service affecting errors or errors on a remote node. Corrective action is
appropriate to prevent a serious fault from developing. An example is a fan failure, where no
subscribers are immediately affected, but calamity could result if the situation persists. Note that an
accumulation of lower-level alarms does equal a higher-level alarm.
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, dspslotalms, dspswalms, dspclkalms
AXSM: dspalm, dspalms
Attributes
Log: no log
State: active
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-73
Chapter 9
Troubleshooting Commands
dspcdalms
Examples
Display card-level alarms for the card in slot 8.
node19.8.PXM.a > dspcdalms 8
Node Card Alarm Summary
Line Alarm
Port Alarm
Connect Alarm
Slot
Slot
Slot
8
8
8
Critical
Critical
Critical
0
0
0
Major
Major
Major
0
0
0
Minor
Minor
Minor
0
0
0
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
0
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
Minor
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
Display card alarms without specifying a slot.
MGX8850.7.PXM.a > dspcdalms
Node Card Alarm Summary
Line Alarm
Port Alarm
Feeder Alarm
Channel Alarm
Line Alarm
Port Alarm
Feeder Alarm
Channel Alarm
Line Alarm
Port Alarm
Feeder Alarm
Channel Alarm
Line Alarm
Port Alarm
Feeder Alarm
Channel Alarm
Line Alarm
Port Alarm
Feeder Alarm
Channel Alarm
Line Alarm
Port Alarm
Feeder Alarm
Channel Alarm
Line Alarm
Port Alarm
Feeder Alarm
Channel Alarm
Line Alarm
Port Alarm
Feeder Alarm
Channel Alarm
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
Slot
1
1
1
1
2
2
2
2
3
3
3
3
5
5
5
5
6
6
6
6
9
9
9
9
10
10
10
10
12
12
12
12
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
2
0
0
0
0
0
0
0
MGX8850.7.PXM.a > dspcdalms
Card Alarm Summary
Slot 1 Crit 0 Maj 0 Min 0 || Slot 17 Crit 0 Maj 0 Min 0
Slot 2 Crit 0 Maj 0 Min 0 || Slot 18 Crit 0 Maj 0 Min 0
Slot 3 Crit 0 Maj 0 Min 0 || Slot 19 Crit 0 Maj 0 Min 0
Slot 4 Crit 0 Maj 0 Min 0 || Slot 20 Crit 0 Maj 0 Min 0
Slot 5 Crit 0 Maj 0 Min 0 || Slot 21 Crit 0 Maj 0 Min 0
Slot 6 Crit 12 Maj 15 Min 19 || Slot 22 Crit 0 Maj 0 Min 0
Slot 7 Crit 0 Maj 0 Min 1 || Slot 23 Crit 0 Maj 0 Min 0
Slot 8 Crit 0 Maj 2 Min 0 || Slot 24 Crit 0 Maj 0 Min 0
Slot 9 Crit 0 Maj 0 Min 0 || Slot 25 Crit 0 Maj 0 Min 0
Slot 10 Crit 0 Maj 0 Min 0 || Slot 26 Crit 0 Maj 0 Min 0
Slot 11 Crit 0 Maj 0 Min 0 || Slot 27 Crit 0 Maj 0 Min 0
Slot 12 Crit 0 Maj 0 Min 0 || Slot 28 Crit 0 Maj 0 Min 0
Cisco MGX 8850 Routing Switch Command Reference
9-74
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcdalms
Slot 13 Crit 0 Maj 0
Slot 14 Crit 0 Maj 0
Slot 15 Crit 0 Maj 0
Slot 16 Crit 0 Maj 0
Use dspcdalms <slot>
Min 0 || Slot 29 Crit
Min 0 || Slot 30 Crit
Min 0 || Slot 31 Crit
Min 0 || Slot 32 Crit
to see more detail.
0
0
0
0
Maj
Maj
Maj
Maj
0
0
0
0
Min
Min
Min
Min
0
0
0
0
MGX8850.7.PXM.a > dspcdalms 6
Card Alarm Summary
Hardware Alarm Critical 0 Major 0 Minor 0
Card State Alarm Critical 0 Major 0 Minor 0
Disk Alarm Critical 0 Major 0 Minor 0
Line Alarm Critical 3 Major 4 Minor 5
Port Alarm Critical 4 Major 5 Minor 6
Feeder Alarm Critical 0 Major 0 Minor 0
Channel Alarm Critical 5 Major 6 Minor 7
MGX8850.7.PXM.a > dspndalms
Node Alarm Summary
Alarm Type Critical Major Minor
Clock Alarms 0 0 0
Switching Alarms 0 0 2
Environment Alarms 0 0 0
Card Alarms 12 17 18
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-75
Chapter 9
Troubleshooting Commands
dspcdbucketcnt
dspcdbucketcnt
Display Cell Counts for the Card
The dspcdbucketcnt command shows the following cell-related counts:
•
Cells transferred between the card and the backplane
•
Cells from the QE 48
•
CLP0 and CLP1 cells that the card dropped
•
Invalid, errored, and unsupported OAM cells
•
Errored RM cells
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
Log: no log
State: active, standby
Privilege: ANYUSER
Example
Display the bucket counters for the current AXSM.
MGX8850.12.AXSM.a > dspcdbucketcnt
cells to backplane(QLSI) : 0
cells from QE 48 : 5347
cells from backplane(QLSI) : 6917
CLP0 cells dropped : 0
CLP1 cells dropped : 0
undefined cells from port : 0
errored OAM from port : 0
invalid OAM from port : 0
unsupported OAM from port : 0
errored RM cells from port :0
Cisco MGX 8850 Routing Switch Command Reference
9-76
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcdcnt
dspcdcnt
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:
•
Cells transferred between the service module and each of the switch planes within the total array of
switch planes.
•
Total cells transferred between the service module and the backplane.
•
Cells to and from QE48.
•
Undefined cells.
•
Total number of CLP0 and CLP1 cells that have been discarded.
•
Errored, invalid, and unsupported OAM cells.
•
Errored RM cells.
•
Cells transferred between and individual switch plane and each slot. This information is centered on
the switch fabric itself rather than the card. Each switch fabric can route cells to and from any slot,
so the display includes this information for each switching plane.
Cards on Which This Command Runs
AXSM
Syntax
dspcdcnt
Related Commands
clrcdcnt (on the AXSM), dspxbar, dspxbaralm, dspxbarerrcnt, dspxbarerrthresh
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-77
Chapter 9
Troubleshooting Commands
dspcdcnt
AXSM Example
Display the cell transfers between the current AXSM and the switch planes (crossbar planes).
SanJose.4.AXSM.a > dspcdcnt
Ingress Count
------------Cells to xbar plane[1]:
Cells to xbar plane[2]:
Cells to xbar plane[3]:
Cells to xbar plane[4]:
Cells to xbar plane[5]:
Cells to xbar plane[6]:
Cells to xbar plane[7]:
Cells to xbar plane[8]:
Total cells to backplane:
Cells from QE48
:
Undefined cells
:
Errored OAM cells
:
Invalid OAM cells
:
Unsupported OAM cells
:
Errored RM cells
:
1505
0
1488
0
0
0
0
0
2993
2993
0
0
0
0
0
Cells
Cells
Cells
Cells
Cells
Cells
Cells
0
0
0
2993
0
0
0
to
to
to
to
to
to
to
dest
dest
dest
dest
dest
dest
dest
slot[01]:
slot[03]:
slot[05]:
slot[07]:
slot[09]:
slot[11]:
slot[13]:
Egress Count
-----------Cells from xbar plane[1]: 743
Cells from xbar plane[2]: 1
Cells from xbar plane[3]: 445
Cells from xbar plane[4]: 0
Cells from xbar plane[5]: 0
Cells from xbar plane[6]: 0
Cells from xbar plane[7]: 0
Cells from xbar plane[8]: 0
Total cells from backplane: 1189
Cells to QE48:
1188
CLP0 cells discard:
0
CLP1 cells discard:
0
Cells
Cells
Cells
Cells
Cells
Cells
Cells
to
to
to
to
to
to
to
dest
dest
dest
dest
dest
dest
dest
slot[02]:
slot[04]:
slot[06]:
slot[08]:
slot[10]:
slot[12]:
slot[14]:
0
0
0
0
0
0
0
Cisco MGX 8850 Routing Switch Command Reference
9-78
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcderrs
dspcderrs
Display Card Errors
Display information about card errors.
Cards on Which This Command Runs
PXM45
Syntax
dspcderrs
Related Commands
clrerr
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Example
Display all card errors.
wilco.7.PXM.a > dspcderrs
dspcderrs
08/05/95-18:53:05 tRootTask
09/05/95-09:14:08 tRootTask
value = 0 = 0x0
3 Task failed
3 Task failed
: scm
: scm
wilco.7.PXM.a >
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-79
Chapter 9
Troubleshooting Commands
dspcds
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:
•
Revision level of the boot firmware
•
Revision level of the system software
•
Date and time of command execution, including GMT offset
•
Backplane serial number and its hardware revision level
•
The IP address of the statistics master (a workstation)
•
Type of card in the front and back slots and the (active/standby) state of each
•
Alarm status for each card and the shelf itself
•
Redundancy configuration for each slot
Cards on Which This Command Runs
PXM45
Syntax
dspcds
Related Commands
dspcd, version
Attributes
Log: no log
State: active, standby, init
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
9-80
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcds
Example
Display information for all cards in the MGX 8850 switch.
MGX8850.7.PXM.a > dspcds
MGX8850
System Rev: 02.00
Backplane Serial No: SAA03270618 Bp HW Rev: B0
Card
Slot
---
Front/Back
Card State
----------
Card
Type
--------
Alarm
Status
--------
Aug. 06, 2000 18:03:35 GMT
GMT Offset: 0
Node Alarm: CRITICAL
Redundant
Redundancy
Slot
Type
-----------
01
02
03
04
05
06
07
08
09
10
11
12
13
14
Active/Active
Active/Active
Active/Active
Standby/Active
Active/Active
Active/Active
Active/Active
Standby/Active
Active/Active
Active/Active
Empty
Active/Active
Empty
Empty
AXSM_1OC48
AXSM_1OC48
AXSM_16OC3
AXSM_16OC3
AXSM_4OC12
AXSM_4OC12
PXM45
PXM45
AXSM_16T3E3
AXSM_16T3E3
--AXSM_2OC12
-----
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
--NONE
-----
NA
NA
04
03
NA
NA
08
07
NA
NA
--NA
-----
NO REDUNDANCY
NO REDUNDANCY
PRIMARY SLOT
SECONDARY SLOT
NO REDUNDANCY
NO REDUNDANCY
PRIMARY SLOT
SECONDARY SLOT
NO REDUNDANCY
NO REDUNDANCY
--NO REDUNDANCY
-----
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-81
Chapter 9
Troubleshooting Commands
dspcdstatus
dspcdstatus
Display Card Status
Displays the most serious alarms reported by a service module. The alarm information pertains to:
•
Lines
•
Ports
•
Connections
•
Feeders
•
Severity of each alarm
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:
•
dspndalms 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 other commands to investigate the
alarm further.
•
dspcdalms identifies line, port, feeder, or connection alarms on an AXSM.
•
dspclkalms shows alarms related to network clocks.
•
dspenvalms lists alarms for out-of-range conditions for temperature, voltage sources, and so on.
•
dspslotalms shows card-level alarms, such as a missing card or a disk problem on the PXM-HD.
•
dspswalms shows alarms related to the switching hardware on the PXM45.
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:
•
Critical, indicating complete, non-recoverable failure, loss of data, and do on. The failed entity must
be restored. A power failure or a line being disconnected is an example.
•
Major, indicating service-affecting errors. This event indicates that a major service is damaged or
lost, but the existing traffic is not affected.
•
Minor, indicating non-service affecting errors or errors on a remote node. Corrective action is
appropriate to prevent a serious fault from developing. An example is a fan failure, where no
subscribers are immediately affected, but calamity could result if the situation persists. Note that an
accumulation of lower-level alarms does equal a higher-level alarm.
Two hierarchies of alarm types exist. They are card alarms and node alarms. See Figure 9-2 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.
Cisco MGX 8850 Routing Switch Command Reference
9-82
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcdstatus
Figure 9-2
Alarm Type Hierarchy
Disk
Card
Power supply
Line
DC level
Port
Fan
Feeder
Temperature
Channel
Legacy alarms
34910
Card alarms
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
Log: no log
State: active
Privilege: ANYUSER
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 11
Logical Slot
11
Physical Slot
Card Alarm Status - Type LINE
11
Severity CRITICAL
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-83
Chapter 9
Troubleshooting Commands
dspcdstatus
The 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 > dspalms
Line Number: 1.1
Alarm State
Section : LOS,LOF
Line
: AIS
Path
: RDI
Cisco MGX 8850 Routing Switch Command Reference
9-84
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspchancnt
dspchancnt
Display Channel Counters
Display the statistical counters for a connection (channel). See the cnfdiag command for a detailed
description of MGX 8850 diagnostics.
Note
This command does not apply to OC-48 cards.
Cards on Which This Command Runs
AXSM
Syntax
dspchancnt <ifNum> <vpi> <vci> <isPVC>
Syntax Description
ifNum
The logical port number. The range for AXSM is 1–60.
vpi
The VPI in the range 1–4095.
vci
The VCI in the range 1–65535.
isPVC
A Boolean expression that identifies either an SVC or a SPVC. Type a 0 for an SVC
or a 1 for an SPVC.
Related Commands
dspchstats, clrchancnt, dspcdcnt
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Example
Display channel counters on AXSM for 1 10 100.
Golden_U2.11.AXSM.a > dspchancnt 1 10 100
Ingress
Egress
Instantaneous Qdepth:
0
0
Arrival CLP0 cells:
0
492305
Arrival CLP1 cells:
0
0
Dscd CLP0 cells:
0
Dscd CLP0+1 cells:
0
Noncompliant cells:
0
Arrival EFCI cells:
0
0
Arrival EOF cells:
0
0
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-85
Chapter 9
Troubleshooting Commands
dspchanloop
dspchanloop
Display Channel Loopbacks
Show channel (connection) loopbacks on a logical port.
Cards on Which This Command Runs
AXSM
Syntax
dspchanloop <ifNumber>
Syntax Description
ifNumber
The logical port number. The range for AXSM is 1–60.
Related Commands
addchanloop, delchanloop
Attributes
Log: no log
State: active, standby
Privilege: SERVICE_GP
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 4
Port
Type
lVPI
lVCI
4
igrLpbk
1
50
rVPI
0
rVCI
35
Cisco MGX 8850 Routing Switch Command Reference
9-86
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspchantests
dspchantests
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
Syntax
dspchantests <ifNum> <vpi> <vci>
[-num <count>]
Syntax Description
ifNum
The logical port number. The range for AXSM is 1–60.
vpi
The VPI range for the SVC or SPVC is 1–255.
vci
The VCI range for a VCC SPVC is 32–65535. For a VPC, the only VCI value for an
SPVC is 0.
-num
(Optional) A keyword that indicates an aggregate connection count follows.
number
The number of connections to display.
Related Commands
tstdelay, tstconseg, dspcon
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-87
Chapter 9
Troubleshooting Commands
dspchantests
Examples
Run tstdelay on connection 1 10 100 then display the results.
Step 1
Execute tstdelay:
node19.1.AXSM.a > tstdelay 1 10 100
Test started; Use dspcon/dspchantests to see test results
Step 2
Check the results:
node19.1.AXSM.a > dspchantests 1 10 100
Connection Id
Test Type
Direction
=============
=========
=========
01.0010.00100:
OAM Lpbk
ingress
Result
=======
Success
Round Trip Delay
================
40000
Run tstconseg for 1 10 100 then display the results.
Step 1
Run the test for 1 10 100:
node19.1.AXSM.a > tstconseg 1 10 100
Test started; Use dspcon/dspchantests to see test results
Step 2
Check the results:
node19.1.AXSM.a > dspchantests 1 10 100
Connection Id
Test Type
Direction
=============
=========
=========
01.0010.00100:
OAM Lpbk
egress
Result
=======
TimeOut
Round Trip Delay
================
0
Cisco MGX 8850 Routing Switch Command Reference
9-88
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspclkalms
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:
•
Critical, indicating complete, non-recoverable failure, loss of data, and do on. The failed entity must
be restored. A power failure or a line being disconnected is an example.
•
Major, indicating service-affecting errors. This event indicates that a major service is damaged or
lost, but the existing traffic is not affected.
•
Minor, indicating non-service affecting errors or errors on a remote node. Corrective action is
appropriate to prevent a serious fault from developing. An example is a fan failure, where no
subscribers are immediately affected, but calamity could result if the situation persists. Note that an
accumulation of lower-level alarms does equal a higher-level alarm.
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
Log: no log
State: active
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-89
Chapter 9
Troubleshooting Commands
dspclkalms
Example
Display clock alarms.
pop20two.7.PXM.a > dspclkalms
pop20two
System Rev: 02.00
MGX8850
Clock Manager Alarm Summary
---------------------------Critical
Major
Minor
000
000
000
Jul. 31, 2000 11:23:17 GMT
Shelf Alarm: NONE
Cisco MGX 8850 Routing Switch Command Reference
9-90
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspclksrcs
dspclksrcs
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
•
For the primary clock: the type, source, status, and reason (for status change) of the clock.
•
For the secondary clock: the type, source, status, and reason (for status change) of the clock.
•
The active clock—the clock that currently provides synchronization. The active clock can be
primary, secondary, holdover, or internal.
•
Whether revertive mode is enabled or disabled.
Changes to the configuration and status of clocks go into the database on the active PXM45. If a
standby (redundant) PXM45 exists, it receives the initial clock configuration and status but receives
internal status updates only when you interact with the node in a way that changes a configuration or
when the standby PXM45 switches to the active state.
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:
•
“ok” (good), which means the clock source is operational and stable.
(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.)
•
“bad” means a fault in the clock source has been detected. Use the Reason field to help isolate the
problem. See the section, “Reason for Status Change.”
•
“unknown” is a temporary string while the clock manager is sending a message to the clock source.
•
“not configured” means that this source—primary or secondary—has not been configured.
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.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-91
Chapter 9
Troubleshooting Commands
dspclksrcs
Table 9-3
Reasons for Change of Clock State
Reason
Meaning
okay
The clock source is okay.
unknown reason
The clock manager has no information for Reason.
no clock signal
Loss of signal (LOS) on the clock source.
frequency too high
The frequency has drifted too high.
frequency too low
The frequency has drifted too low
excessive jitter
Jitter has exceeded tolerance for this stratum.
missing card or component
The active PXM45 has no clock hardware support.
non-existent logical interface The interface is non-existent or not functioning.
interface does not
support clocking
The interface does not support clocking.
phase error
The clock manager has detected a phase error in the clock.
unlockable
The clock manager has attempted to lock the source but found that
the clock signal from this source is unlockable.
out of lock or null
The clock circuitry is again trying to lock a source that went out of
locking range. Note: for Reason, out of lock and null are the same.
reset—not a valid state
The clock source has been reset.
in locking—wideband test
The clock circuitry is in wide bandwidth mode of the locking
process. In this mode, the circuit tests the integrity of the source but
with wide latitude for frequency accuracy. If the source passes this
test, the circuit proceeds to the narrowband test.
in locking—narrowband test
The clock circuitry is in narrow bandwidth locking mode. In this
mode, the circuit stringently tests the integrity of the source.
locked
The clock circuitry is locked to this source.
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:
•
in locking—wideband test
•
in locking—narrowband test
•
locked
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
Cisco MGX 8850 Routing Switch Command Reference
9-92
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspclksrcs
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.
Cards on Which This Command Runs
PXM45
Syntax
dspclksrcs
Related Commands
cnfclksrc, delclksrc, dspclkalms
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
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> dspclksrcs
Primary clock type:
generic
Primary clock source:
6.2
Primary clock status: good
Primary clock reason:
okay
Secondary clock type:
generic
Secondary clock source: 6.3
Secondary clock status:
good
Secondary clock reason:
okay
Active clock:
primary
source switchover mode: revertive
Display information about the clock sources. This example shows a BITS clock for the primary source
with revertive mode enabled.
pop20one.7.PXM.a > dspclksrcs
Primary clock type:
bits t1
Primary clock source:
7.35
Primary clock status:
ok
Primary clock reason:
okay
Secondary clock type:
generic
Secondary clock source: 9:1.1:1
Secondary clock status:
ok
Secondary clock reason:
okay
Active clock:
primary
source switchover mode: revertive
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-93
Chapter 9
Troubleshooting Commands
dspcon
dspcon
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.
Display Connection on the PXM45
On the PXM45, dspcon shows the following connection identifiers:
•
NSAP address, status, and ownership of local and remote ends of the connection. The display shows
whether a particular endpoint is the master or slave.
The provisioning parameters in the display show:
•
Connection type of VPC or VCC.
•
Service type and compliance (for example, UBR for service type and UBR.1 for ATM Forum
compliance).
•
Bearer class (relates to voice traffic and is reserved for future use).
•
Whether continuity checking or frame discard are enabled (see addcon description).
•
Cause of the last failure. This field can also show that no errors have occurred since the connection
was first added by displaying “SPVC Established.” If a failure occurred, the Attempts field shows
the number of times the system attempted to re-establish service. If no failures have occurred, the
Attempts field contains a 0.
•
L-Util and R-Util are the local and remote percent of utilization assigned to the connection.
Currently, the default of 100% is the only value.
•
Cost values for the connection’s route: the two fields in this category are Max Cost and Routing
Cost. The Max Cost is a cost-per-link configured for a service type (such as UBR) through the
cnfpnni-intf command. When you add the SPVC through addcon, you can specify a maximum
routing cost through the maximum cost (maxcost) parameter. The maxcost represents the maximum
cost for an individual connection. The system uses the cost-per-link for the service type and the
maxcost for the connection to determine whether a route costs too much. After the system creates a
route, the total number of links yields the Routing Cost.
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.
•
Broadcast type: point-to-point or multicast.
The Traffic Parameters section shows the standard parameters PCR, SCR, and CDV in the receive and
transmit directions.
Cisco MGX 8850 Routing Switch Command Reference
9-94
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcon
Display Connection on the AXSM
On the AXSM, dspcon shows the following connection identifiers:
•
NSAP address, logical port, VPI/VCI, status, and ownership of local and remote ends of the
connection. The display shows whether a particular endpoint is the master or slave.
The provisioning parameters in the display show:
•
Connection type of VPC or VCC.
•
Service type (for example, ABR).
•
A number indicating the controller. For example, 2 refers to PNNI. The addcontroller command
specifies the controller.
•
The administrative state is either up or down. This state results from addcon or dncon/upcon. Note
that, after you down a connection with at the connection master endpoint, the dspcon command
shows the connection as “down” when you execute it at the master endpoint and “failed” when you
execute it at the slave endpoint. (See also dncon description).
•
The operational state is either OK or failed. The operational state can apply to a connection
regardless of the administrative state.
The traffic management parameters consist of:
•
Local and remote UPC parameters of PCR, MBS, CTD, CDVT, and so on. A –1 in a field means that
the parameter was not specified. The characters “N/A” indicate that the parameter does not apply to
the service type.
These other fields also pertain to connection integrity:
•
OAM connectivity check enable or disable.
•
Loopback test enable/disable and loopback type.
•
Round trip delay in microseconds. This field is non-zero only if you previously executed tstdelay.
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).
and Egress directions.
Cards on Which This Command Runs
AXSM, PXM45
AXSM Syntax
dspcon
<ifNum >
<vpi>
<vci>
PXM45 Syntax
dspcon
<portid >
<vpi>
<vci>
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-95
Chapter 9
Troubleshooting Commands
dspcon
Syntax Description
ifNum
(AXSM) Logical interface (port) number. For AXSM, the range is 1–60.
portid
(PXM45) The portid represents the PNNI logical port and has the format
[shelf.]slot[:subslot].port[:subport]. See also PNNI Format, page 9-3.
vpi
VPI number. At the UNI, the range is 0–255. At the NNI, the range is 0–4095.
vci
VCI number. For a VCC, the range is 32–65535. For a VPC, the VCI is 0.
Related Commands
addcon, dspcons, cnfcon
PXM45 Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Log: no log
State: active
Privilege: GROUP1
AXSM Attributes
Examples
Display connection 5 31 63000 on the current AXSM.
MGX8850.1.AXSM.a > dspcon 5 31 63000
-------------------------------------------------------------------------Local
:
(M)
Remote
:
NSAP
Address
port
4700918100000000107BE92F3F00000101180500
NSAP Address
vpi
vci
1.01.05 31 63000
port
vpi
vci
(S)
4700918100000000107BE92F3F00000101180500 1.01.05
3201 100
-------------------------------------------------------------------------Conn. Type
:
VCC
Admn Status : ADMN-UP
Service Type :
cbr1
Oper Status : FAIL
Controller
:
2
-------------------------------------------------------------------------Local PCR
:
10000
Remote PCR
: 1000
Local SCR
:
N/A
Remote SCR
: N/A
Local CDV
:
-1
Remote CDV
: -1
Local CTD
:
-1
Remote CTD
: -1
Local MBS
:
N/A
Remote MBS
: N/A
Local CDVT
:
-1
Remote CDVT : -1
Admin weight :
-1
Frame discard: N
-------------------------------------------------------------------------OAM CC Config :DISABLED
Statistics
: DISABLED
Cisco MGX 8850 Routing Switch Command Reference
9-96
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcon
-------------------------------------------------------------------------Loopback Type :No
Lpbk | Dir:N/A
| Status: No Lpbk | RTD: 0 us
On the CLI of the PXM45, display connection 20 100 on 11:1.1:2.
Unknown.7.PXM.a > dspcon 11:1.1:2 20 100
Port
Vpi Vci
Owner
State
------------------------------------------------------------------------Local 11:1.1:2
20.100
MASTER
FAIL
Address: 47.00918100000000107b65f33d.0000010b1802.00
Remote 11:1.1:2
10.100
SLAVE
FAIL
Address: 47.00918100000000107b65f33d.0000010b1802.00
-------------------- Provisioning Parameters -------------------Connection Type: VCC
Cast Type: Point-to-Point
Service Category: CBR
Conformance: CBR.1
Bearer Class: BCOB-X
Last Fail Cause: SPVC Established
Attempts: 0
Continuity Check: Disabled
Frame Discard: Disabled
L-Utils: 100
R-Utils: 100
Max Cost: -1
Routing Cost: 0
---------- Traffic Parameters ---------Tx PCR: 50
Rx PCR: 50
Tx CDV: N/A
Rx CDV: N/A
Tx CTD: N/A
Rx CTD: N/A
Display 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 100
Port
Vpi Vci
Owner
State
------------------------------------------------------------------------Local 1:1.1:1
10.100
SLAVE
OK
Address: 47.00918100000000001a53c82d.000001011801.00
Remote 1:1.1:1
11.101
MASTER
OK
Address: 47.00918100000000001a53c82d.000001011801.00
-------------------- Provisioning Parameters -------------------Connection Type: VCC
Cast Type: Point-to-Point
Service Category: UBR
Conformance: UBR.1
Bearer Class: BCOB-X
Last Fail Cause: SPVC Established
Attempts: 0
Continuity Check: Disabled
Frame Discard: Disabled
L-Utils: 100
R-Utils: 100
Max Cost: -1
Routing Cost: 0
---------- Traffic Parameters ---------Tx PCR: 14
Rx PCR: 14
Tx SCR: 3
Rx SCR: 3
Tx MBS: 1
Rx MBS: 1
Tx CDVT: -1
Rx CDVT: -1
Tx CDV: N/A
Rx CDV: N/A
Tx CTD: N/A
Rx CTD: N/A
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-97
Chapter 9
Troubleshooting Commands
dspconinfo
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 node.
the default is all ports on the node, but you can also specify a particular PNNI port. For each port, the
display shows:
•
Number of active connections
•
Number of failed connections
•
Number of administratively inactive (or down) connections as a result of dncon
•
Number of alarm indication (AIS) failures
•
Number of A-bit failures
•
Total number of connections
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]
Syntax Description
-port
Specifies a particular port for the connections. The default for this command is all
ports (portid not specified) You can specify a particular port by using the port
keyword followed by the portID in the following format:
[shelf.]slot[:subslot].port[:subport]
Currently, the value for shelf is 0 and so is not necessary.
Related Commands
none
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
9-98
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspconinfo
Example
Display the SPVC summaries for the current node.
svcswp10.7.PXM.a > dspconinfo
Local Port
#Active
#Fail
#AISFail #ABITFail
#Down
#Total
----------------------------+-----------------------------+--------------------5.4
3998
0
0
0
0
3998
6.4
3997
0
0
0
0
3997
An example of an individual port follows. The display shows 1096 connections on 11:1.1:11.
Geneva.7.PXM.a > dspconinfo -port 11:1.1:11
Local Port
#Active
#Failed
#Total
--------------------------------------------11:1.1:11
1096
0
1096
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-99
Chapter 9
Troubleshooting Commands
dspcons
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:
record
A number for the connection with internal application only. It resides in the
database on the AXSM and is not affected by user input. The system creates
this number when you create the connection. The Cisco WAN Manager
application uses this number.
Identifier
Identifies the connection in the format port vpi vci.
Type
Shows whether the connection is a VCC or a VPC.
SrvcType
The service type—VBR, and so on. (See addcon description).
M/S
Indicates whether the endpoint specified by Identifier is the master or slave.
Upld
The hexadecimal Upload number is an encoded timestamp the Cisco WAN
Manager application uses to determine when a connection was created or
modified. In the CLI context, this field has little meaning.
Adm
The administrative state of the connection. If the connection is down, it
may have resulted from the dncon command.
Alarm
Shows the alarm status of the connection.
When you execute dspcons on the CLI of the PXM45, the output shows:
Local and
Remote Port ID
The display contains a column for the local port ID and a column for the
remote port ID. The port ID has the format that the network controller
utilizes: [shelf.]slot[:subslot].port[:subport]
Local and
Remote VPI.VCI
The VPI and VCI at the local and remote ends of the connection.
State
The State column shows whether the connection is OK, down (by the dncon
command), failed, or has an alarm indication signal (AIS) or abit errors.
Owner
Whether the endpoint is master or slave.
Local and
Remote NSAP
An NSAP address for each end of the connection.
Cisco MGX 8850 Routing Switch Command Reference
9-100
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcons
Cards on Which This Command Runs
PXM45, AXSM
PXM45 Syntax
dspcons
[-port portid]
[-vpi starting-vpi]
[-vci starting vci]
[-state {fail|ais|abit|ok|down}]
[-owner {master|slave}]
PXM45 Syntax Description
-port
The port identifier (portid) in the format that the network controller utilizes:
[shelf.]slot[:subslot].port[:subport]
Currently, the value for shelf is not necessary.
-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.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-101
Chapter 9
Troubleshooting Commands
dspcons
AXSM Syntax
dspcons
[-conn <conn id>]
[-filt <filter options>]
[-if <intf no>]
[-vpi <vpi filter>]
[-vci <vci filter>]
AXSM Syntax Description
-conn
The connection ID (conn ID) of the connection to begin the display. The
format of conn ID is:
ifNum.vpi.vci
The range for ifNum is 1–60 for the AXSM.
The VPI has the range 0–4095. The VCI has the range 32–65535.
-filt
Unlike on the PXM45, you do not use keywords for this parameter on the
AXSM. You enter only a number on the AXSM CLI to indicate the state. The
display criteria are:
1 ingr—for errors in the ingress direction
2 egr—for errors in the egress direction
3 condn—for connections where the switch has conditioned the connection
4 iffail—for connection on a failed logical interface
5 ccfail
6 mis
7 abit—for connections where an A-bit error has occurred
-if
A particular logical interface for connection display.
-vpi
The VPI of all the connections that you would like to display.
-vci
The VCI of all the connections that you would like to display.
Related Commands
dspcon, addcon, cnfcon, delcon, dncon, upcon
PXM45 Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Log: no log
State: active, standby
Privilege: GROUP1
AXSM Attributes
Cisco MGX 8850 Routing Switch Command Reference
9-102
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcons
PXM45 Example
Display all connections by entering dspcons on the CLI of the PXM45.
MGX8850.7.PXM.a > dspcons
Local Port
Vpi.Vci
Remote Port
Vpi.Vci
State
Owner
----------------------------+-----------------------------+-------+-----3:1.1:1
20 0
6:1.1:1
20 0
OK
MASTER
Local Addr: 47.00918100000000107b65f33d.000001031801.00
Remote Addr: 47.00918100000000107b65f33d.000001061801.00
5:1.1:1
100 100
5:1.1:1
100 200
OK
SLAVE
Local Addr: 47.00918100000000107b65f33d.000001051801.00
Remote Addr: 47.00918100000000107b65f33d.000001051801.00
5:1.1:1
100 200
5:1.1:1
100 100
OK
MASTER
Local Addr: 47.00918100000000107b65f33d.000001051801.00
Remote Addr: 47.00918100000000107b65f33d.000001051801.00
6:1.1:1
20 0
3:1.1:1
20 0
OK
SLAVE
Local Addr: 47.00918100000000107b65f33d.000001061801.00
Remote Addr: 47.00918100000000107b65f33d.000001031801.00
6:1.1:1
100 100
6:1.1:1
100 200
OK
SLAVE
Local Addr: 47.00918100000000107b65f33d.000001061801.00
Remote Addr: 47.00918100000000107b65f33d.000001061801.00
6:1.1:1
100 200
6:1.1:1
100 100
OK
MASTER
Local Addr: 47.00918100000000107b65f33d.000001061801.00
Remote Addr: 47.00918100000000107b65f33d.000001061801.00
6:1.1:1
200 100
6:2.1:3
200 200
OK
SLAVE
6:1.1:1
100 200
6:1.1:1
100 100
Local Addr: 47.00918100000000107b65f33d.000001061801.00
Remote Addr: 47.00918100000000107b65f33d.000001061801.00
6:1.1:1
200 100
6:2.1:3
200 200
Local Addr:
Remote Addr:
6:2.1:3
Local Addr:
Remote Addr:
9:1.3:3
Local Addr:
Remote Addr:
11:1.1:2
Local Addr:
Remote Addr:
47.00918100000000107b65f33d.000001061801.00
47.00918100000000107b65f33d.000001061803.00
200 200
6:1.1:1
200 100
47.00918100000000107b65f33d.000001061803.00
47.00918100000000107b65f33d.000001061801.00
10 100
Routed
0 0
47.00918100000000107b65f33d.000001091803.00
00.000000000000000000000000.000000000000.00
10 100
11:1.1:2
20 100
47.00918100000000107b65f33d.0000010b1802.00
47.00918100000000107b65f33d.0000010b1802.00
OK
MASTER
OK
SLAVE
OK
MASTER
FAIL
SLAVE
OK
SLAVE
Local Port
Vpi.Vci
Remote Port
Vpi.Vci
State
Owner
----------------------------+-----------------------------+-------+-----11:1.1:2
20 100
11:1.1:2
10 100
OK
MASTER
Local Addr: 47.00918100000000107b65f33d.0000010b1802.00
Remote Addr: 47.00918100000000107b65f33d.0000010b1802.00
AXSM 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 > dspcons
record
Identifier
--------------0 01.0010.00100
1 04.0020.00100
Type
---VCC
VCC
SrvcType
-------cbr1
cbr1
M/S
Upld
-----S
010c7953
M
010c7964
Admn
---UP
UP
Alarm
----none
none
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-103
Chapter 9
Troubleshooting Commands
dspcons-dbg
dspcons-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
Log: no log
State: active, standby
Privilege: ANYUSER
Examples
Determine whether SPVC logging is enabled. The output shows that the log is disabled.
MGX8850.8.PXM.a > dspcons-dbg
Global SPVC Event Log Status: Disable
Cisco MGX 8850 Routing Switch Command Reference
9-104
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspcontrollers
dspcontrollers
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
Log: no log
State: active
Privilege: ANYUSER
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.
pop20two.7.PXM.a > dspcontrollers
pop20two
System Rev: 02.00
MGX8850
Number of Controllers:
1
Controller Name:
PNNITWO
Controller Id:
2
Controller Location:
Internal
Controller Type:
PNNI
Controller Logical Slot:
7
Controller Bay Number:
0
Controller Line Number:
0
Controller VPI:
0
Controller VCI:
0
Controller In Alarm:
NO
Controller Error:
Jul. 30, 2000 09:39:36 GMT
Shelf Alarm: NONE
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-105
Chapter 9
Troubleshooting Commands
dspdiagcnf
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
•
light = 5 minutes or less
•
medium = 30 minutes or less
•
full = 60 minutes or more
See the cnfdiag command for a detailed description of MGX 8850 diagnostics.
Syntax
dspdiagcnf
Syntax Description
This command takes no parameters.
Cards on Which This Command Runs
PXM45
Related Commands
cnfdiag, cnfdiagall
Attributes
Log: no log
State: active, standby
Privilege: SERVICE_GP
Cisco MGX 8850 Routing Switch Command Reference
9-106
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspdiagcnf
Example
pop20one.7.PXM.a > dspdiagcnf
Online
-------------- Offline ------------SlotEnableEnableCoverageStartTimeSMTWTFS
1enableenablefull10:30-M-W-F2disableenablefull22:00-M-W-F3enabledisablemedium11:15-M-W-F4enabledisablelight03:20-M-W-F5enabledisablelight14:30------S
6disableenablefull12:00-M-W-F7disableenablelight18:00------S
8enableenablemedium05:00-M-W-F9enabledisablelight04:30-M-W-F10enabledisablefull22:00------S
11enabledisablelight24:15-M-W-F12disableenablefull11:00------S
13enableenablelight13:15-M-W-F14enableenablemedium01:00-M-W-F15enableenablefull02:30-M-W-F16disabledisablelight00:00SMTWTFS
17disabledisablelight00:00SMTWTFS
18disabledisablelight00:00SMTWTFS
19disabledisablelight00:00SMTWTFS
20disabledisablelight00:00SMTWTFS
21disabledisablelight00:00SMTWTFS
22disabledisablelight00:00SMTWTFS
23disabledisablelight00:00SMTWTFS
24disabledisablelight00:00SMTWTFS
25disabledisablelight00:00SMTWTFS
26disabledisablelight00:00SMTWTFS
27disabledisablelight00:00SMTWTFS
28disabledisablelight00:00SMTWTFS
29disabledisablelight00:00SMTWTFS
30disabledisablelight00:00SMTWTFS
31disabledisablelight00:00SMTWTFS
32disabledisablelight00:00SMTWTFS
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-107
Chapter 9
Troubleshooting Commands
dspdiagerr
dspdiagerr
Display Diagnostics Errors
Displays the current offline or online diagnostics errors.
Cards on Which This Command Runs
PXM45
Syntax
dspdiagerr <online/offline>
Syntax Description
online/offline
Specify whether to display the online or the offline diagnostics errors.
Related Commands
clrdiagerr
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Example
MGX8850.7.PXM.a >
Slot Date
Time
---- ------1
--2
24-Aug 13:35
3
--4
--5
--6
--7
--8
--9
--10
--11
--12
--13
18-Aug 03:24
14
--15
--16
--17
--18
--19
--20
--21
--22
--23
---
dspdiagerr offline
Message
------SAR send failed
HUMVEE IRQ test failed
Cisco MGX 8850 Routing Switch Command Reference
9-108
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspdiagerr
24
25
26
27
28
29
30
31
32
----------
----------
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-109
Chapter 9
Troubleshooting Commands
dspdiagstat
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
See the cnfdiag command for a detailed description of MGX 8850 diagnostics.
Syntax
dspdiagstat
<slot>
Syntax Description
slot
The slot of the card for which to display the diagnostics statistics.
Cards on Which This Command Runs
PXM45
Related Commands
clrdiagstat
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Example
pop20two.7.PXM.a > dspdiagstat 7
Slot 7 diagnostics statistics:
online diag attempted
online diag failed
offline diag attempted
offline diag failed
=
=
=
=
0x00000000
0x00000000
0x00000000
0x00000000
Cisco MGX 8850 Routing Switch Command Reference
9-110
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspdiagstatus
dspdiagstatus
Display Diagnostics Status
Displays the diagnostics status for each card on the switch. The diagnostics statuses are:
Note
•
Idle
•
Ready
•
Offline
•
Online
See the cnfdiag command for a detailed description of MGX 8850 diagnostics.
Syntax
dspdiagstatus
Syntax Description
This command takes no parameters.
Cards on Which This Command Runs
PXM45
Related Commands
cnfdiag, cnfdiagall
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Example
pop20one.7.PXM.a > dspdiagstatus
SlotStateRole
1ReadyACTIVE CARD ROLE
2ReadyACTIVE CARD ROLE
3OfflineSTANDBY CARD ROLE
4OnlineACTIVE CARD ROLE
5ReadyACTIVE CARD ROLE
6OfflineSTANDBY CARD ROLE
7ReadyACTIVE CARD ROLE
8OnlineACTIVE CARD ROLE
9IdleACTIVE CARD ROLE
10ReadyACTIVE CARD ROLE
11OnlineACTIVE CARD ROLE
12IdleACTIVE CARD ROLE
13ReadyACTIVE CARD ROLE
14OfflineSTANDBY CARD ROLE
15IdleACTIVE CARD ROLE
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-111
Chapter 9
Troubleshooting Commands
dspdiagstatus
16IdleACTIVE
17IdleACTIVE
18IdleACTIVE
19IdleACTIVE
20IdleACTIVE
21IdleACTIVE
22IdleACTIVE
23IdleACTIVE
24IdleACTIVE
25IdleACTIVE
26IdleACTIVE
27IdleACTIVE
28IdleACTIVE
29IdleACTIVE
30IdleACTIVE
31IdleACTIVE
32IdleACTIVE
CARD
CARD
CARD
CARD
CARD
CARD
CARD
CARD
CARD
CARD
CARD
CARD
CARD
CARD
CARD
CARD
CARD
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
ROLE
Cisco MGX 8850 Routing Switch Command Reference
9-112
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspenvalms
dspenvalms
Display Environment Alarms
Display alarms related to the environment of the node. The monitored categories are:
•
Temperature inside the enclosure
•
AC power supplies if applicable
•
DC supply power
•
DC system power
•
Bottom fan tray operation
•
Top fan tray operation
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
•
Critical, indicating complete, non-recoverable failure, loss of data, and do on. The failed entity must
be restored. A power failure or a line being disconnected is an example.
•
Major, indicating service-affecting errors. This event indicates that a major service is damaged or
lost, but the existing traffic is not affected.
•
Minor, indicating non-service affecting errors or errors on a remote node. Corrective action is
appropriate to prevent a serious fault from developing. An example is a fan failure, where no
subscribers are immediately affected, but calamity could result if the situation persists. Note that an
accumulation of lower-level alarms does equal a higher-level alarm.
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
temp
(temperature) shows the temperature and whether an alarm condition exists.
psw
(power supply units) shows how many AC power supplies reside in the power supply
tray, and also shows the high and low DC output values that the AC power supplies
should be able to maintain.
fan
shows the presence of top and bottom fan trays, minimum rotation rate of each fan,
and actual rotation rate of each fan in RPMs.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-113
Chapter 9
Troubleshooting Commands
dspenvalms
vmon
(voltage monitor) shows permitted ranges and actual DC voltages.
Related Commands
dspndalms, dspcdstatus
Attributes
Log: no log
State: active
Privilege: ANYUSER
Examples
Check the temperature.
MGX8850.7.PXM.a > dspenvalms temp
MGX8850
System Rev: 02.00
Aug. 06, 2000 18:28:33 GMT
MGX8850
Node Alarm: CRITICAL
ENVIRONMENTAL ALARM STATE INFO
^Notification Disabled
Alarm Type
Unit
Threshold
DataType
Value
State
---------------- ---- --------------------- ---------- ------------Temperature
<= 50
Celsius
33
Normal
Check 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 fan
MGX8850
System Rev: 02.00
Aug. 06, 2000 22:33:08 GMT
MGX8850
Node Alarm: CRITICAL
ENVIRONMENTAL ALARM STATE INFO
^Notification Disabled
Alarm Type
Unit
Threshold
DataType
Value
State
---------------- ---- --------------------- ---------- ------------Top Fan Tray
1
>= 2000
RPM
3504
Normal
Top Fan Tray
2
>= 2000
RPM
3498
Normal
Top Fan Tray
3
>= 2000
RPM
3576
Normal
Top Fan Tray
4
>= 2000
RPM
3492
Normal
Top Fan Tray
5
>= 2000
RPM
3474
Normal
Top Fan Tray
6
>= 2000
RPM
3564
Normal
Top Fan Tray
7
>= 2000
RPM
3462
Normal
Top Fan Tray
8
>= 2000
RPM
3366
Normal
Top Fan Tray
9
>= 2000
RPM
3444
Normal
Bottom
Bottom
Bottom
Bottom
Bottom
Bottom
Bottom
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Tray
Tray
Tray
Tray
Tray
Tray
Tray
1
2
3
4
5
6
7
>=
>=
>=
>=
>=
>=
>=
2000
2000
2000
2000
2000
2000
2000
RPM
RPM
RPM
RPM
RPM
RPM
RPM
0
0
0
0
0
0
0
Missing
Missing
Missing
Missing
Missing
Missing
Missing
Display all environment alarms for the enclosure by entering dspenvalms with no optional parameters.
MGX8850.7.PXM.a > dspenvalms
MGX8850
System Rev: 02.00
Aug. 06, 2000 18:20:35 GMT
MGX8850
Node Alarm: CRITICAL
ENVIRONMENTAL ALARM STATE INFO
^Notification Disabled
Alarm Type
Unit
Threshold
DataType
Value
State
---------------- ---- --------------------- ---------- ------------Temperature
<= 50
Celsius
33
Normal
Cisco MGX 8850 Routing Switch Command Reference
9-114
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspenvalms
Power Supply
Power Supply
Power Supply
DC Voltage
A1
A2
A3
A
none
none
none
42 to 54
None
None
None
VoltsDC
none
none
none
49
Normal
Normal
Normal
Normal
Power Supply
Power Supply
Power Supply
DC Voltage
B1
B2
B3
B
none
none
none
42 to 54
None
None
None
VoltsDC
none
none
none
0
Missing
Missing
Missing
Normal
Top Fan Tray
Top Fan Tray
Top Fan Tray
Top Fan Tray
Top Fan Tray
Top Fan Tray
Top Fan Tray
Top Fan Tray
Top Fan Tray
Bottom
Bottom
Bottom
Bottom
Bottom
Bottom
Bottom
Bottom
Bottom
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
+5V Input
+3.3V Input
+2.5V Input
Calibration VDC
1
2
3
4
5
>= 2000
>= 2000
>= 2000
>= 2000
>= 2000
>= 2000
>= 2000
>= 2000
>= 2000
6
7
8
9
1
2
3
4
5
6
7
8
9
>=
>=
>=
>=
>=
>=
>=
>=
>=
2000
2000
2000
2000
2000
2000
2000
2000
2000
4.850^ to 5.150^
3.200^ to 3.400^
2.425^ to 2.575^
0x7e^ to 0x82^
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
VoltsDC
VoltsDC
VoltsDC
Other
3504
3498
3576
3498
3480
3570
3468
3366
3444
0
0
0
0
0
0
0
0
0
5.017
3.259
2.440
0x80
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Missing
Missing
Missing
Missing
Missing
Missing
Missing
Missing
Missing
Informational
Informational
Informational
Informational
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-115
Chapter 9
Troubleshooting Commands
dsperr
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
-sl
(Mandatory) Number of the slot. The value of slot is any slot in the switch.
-en
An option that lets you specify a particular error record. You can list all the errors by using
dsperr without this parameter and note the Error Num then display just that error record.
-tr
This option allows you specify 3 options for printing trace data: P, L, or N. If -tr is not
specified, the trace data is printed normally.
P–Pause prompts before printing the trace data with the following message:
This section contains trace data that may span multiple pages. This data is contained
in the file:
C:\LOG\slot09\error08.log
You can ftp this file to a workstation for further analysis
Do you want to view this data now [Yes/No]?
L–Lists all of the trace data file names, for example:
C:\LOG\slot09\error08.log
C:\LOG\slot09\error07.log
C:\LOG\slot09\error06.log
C:\LOG\slot09\error09.log
N–No disables trace data printing.
Related Commands
clrerr
Cisco MGX 8850 Routing Switch Command Reference
9-116
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dsperr
Attributes
Log: no log
State: active, standby, init
Privilege: ANYUSER
Example
Display one screen of internal error messages for slot 1. The Error Num is 4849.
pop20two.8.PXM.a > dsperr -sl 1
Error Log for Slot 01: Error Num 4849
Firmware version:
Product Id: 8850
Timestamp: 02/20/2001-14:04:42 Node name: pop20two
Section Number 0:
Event Logged:
01-00266 02/20/2001-14:04:38 SHMA-7-API_BC_REPORT
E:04849 tEmFaultMg 0x801d2fc0
shmBackCardInsertReport: AppId 0x10005, tId 0x1003d, tName tEmFaultMgr , BayTyp
e 1, callerPc 0x80237ff0
Section 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()
--------------
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-117
Chapter 9
Troubleshooting Commands
dsperrhist
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:
•
A number for the entry in the error history file
•
An event number in hexadecimal format
•
An event name—a few words that describe the error (such as the severity or affected area)
•
A time stamp
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
Log: no log
State: active, standby, init
Privilege: ANYUSER
Examples
Display the error history for the current PXM45. This PXM45 resides in slot 8.
jdlenoir.8.PXM.a > dsperrhist
Log of Errors and Failures (Slot 8):
Entry#--Event#---EventName-------------------------------TimeStamp----------General:
01
0x5006
CBC(Slave) Non-Fatal Minor
11/21/2000-17:55:49
02
0x5006
CBC(Slave) Non-Fatal Minor
11/21/2000-17:57:36
03
0x5006
CBC(Slave) Non-Fatal Minor
11/21/2000-18:22:47
-----------------------------------------------------------------------------
Cisco MGX 8850 Routing Switch Command Reference
9-118
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dsperrhist
Display the error history for the AXSM in slot 6.
jbscott.8.PXM.a > dsperrhist 6
Log 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 1
Log of Errors and Failures (Slot 1):
Entry#--Event#---EventName-------------------------------TimeStamp----------General:
01
0x0005
SHM_CDF_DISCOVER_TMR_POP
11/29/2000-16:45:18
02
0x0001
SHM_CDF_INVALID_SW_ID
11/29/2000-16:45:48
03
0x0002
SHM_CDF_SW_DNLD_FAILED
11/29/2000-16:51:17
04
0x0005
SHM_CDF_DISCOVER_TMR_POP
12/26/2000-16:23:19
Hardware Alarm:
01
0x5000
Humvee Non-Fatal Minor
12/18/2000-16:48:36
02
0x5000
Humvee Non-Fatal Minor
12/18/2000-16:49:11
03
0x5000
Humvee Non-Fatal Minor
12/18/2000-16:49:38
04
0x5000
Humvee Non-Fatal Minor
12/18/2000-16:54:31
05
0x5000
Humvee Non-Fatal Minor
12/26/2000-16:16:34
-----------------------------------------------------------------------------
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-119
Chapter 9
Troubleshooting Commands
dspilmicnt
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
Syntax
dspilmicnt <ifNum> <partId>
Syntax Description
ifNum
The logical port number. The range for AXSM is 1–60.
partId
The number of the resource partition. The range is 1–20.
Related Commands
cnfilmi, dspilmi, dspilmis, clrilmicnt, dnilmi, upilmi
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Example
Display the ILMI counters for logical port 1 on the current AXSM card.
pinnacle3.1.2.AXSM.a > dspilmicnt 1
Port Num:
SNMPPDUsReceived:
Get RequestsReceived:
GetNextRequestsReceived:
SetRequestsReceived:
TrapReceived:
GetResponseReceived
GetResponseTransmitted:
GetRequestTransmitted:
TrapsTransmitted:
InvalidPDUReceived:
Asn1ParseError:
NoSuchNameError:
TooBigError:
1
0
0
0
0
0
0
0
0
0
0
0
0
0
Cisco MGX 8850 Routing Switch Command Reference
9-120
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspln
dspln
Display Line
Display the configuration of a physical line.
Note
The connection count includes control VCs when you execute dspln on the CLI of a service module.
However, when you execute dspcd or dsppnport(s) on the CLI of the controller card, the display
does not include control VCs.
Cards on Which This Command Runs
AXSM
Syntax
dspln
<-ds3 | -sonet> <bay.line>
Syntax Description
-ds3
Command delineator that precedes the line number entry for a T3 of E3 line.
-sonet
Command delineator that precedes the line number entry for a SONET line.
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
upln, cnfln, delln
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Examples
Display T3 line 1 on the current AXSM.
pinnacle.2.AXSM.a > dspln -ds3 1.2
LineNum:
1.2
LineEnable:
Down
LineType:
ds3cbitadm
LineCoding:
ds3B3ZS
LineLength(meters):
0
LineOOFCriteria:
fBits3Of8
LineAIScBitsCheck:
Check
LineLoopback:
NoLoop
Xmt. Clock source:
localTiming
LineRcvFEACValidation: 4 out of 5 FEAC codes
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-121
Chapter 9
Troubleshooting Commands
dspln
Display OC-48 line on the current OC-12 AXSM.
pop20two.1.AXSM.a > dspln -sonet 2.1
Line Number
: 2.1
Admin Status
: Up
Loopback
: NoLoop
Frame Scrambling
: Enable
Xmt Clock source
: localTiming
Line Type
: sonetSts12c
Medium Type(SONET/SDH) : SONET
Medium Time Elapsed
: 506223
Medium Valid Intervals : 96
Medium Line Type
: ShortSMF
Alarm Status
:
APS enabled
:
Number of ports
:
Number of partitions:
Number of SPVC
:
Number of SVC
:
Clear
Disable
1
1
0
4
Cisco MGX 8850 Routing Switch Command Reference
9-122
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dsplncnt
dsplncnt
Display Line Counters—display the contents of counters for various cell-related statistics on a line.
The dsplncnt command displays counters for the following:
•
CLP0 and CLP1 cells*
•
Valid and errored OAM cells
•
Invalid VPI/VCI/PTI cells*
•
Last unknown VPI/VCI*
•
Non-zero generic flow control (GFC) cells*
•
Discarded or corrected HEC errors
•
Discarded usage parameter control (UPC) cells with CLP0*
•
Total UPC cells*
•
Total non-compliant UPC cells*
An asterisk (*) indicates the displayed field does not apply to the AXSM-1-2488.
Note
Some counters apply to both the ingress direction and the egress direction. Some apply to only the
ingress direction. See the example output.
Cards on Which This Command Runs
AXSM
AXSM Syntax
dsplncnt <bay.line>
Syntax Description
<intvl>
The time interval to display (0–96). 0 is the current 15-minute interval. 1 is the most
recent 15-minute interval. 2 is the next most recent 15-minute interval, and so on.
96 being the oldest 15-minute interval.
<bay>
Bay number: 1 or 2
<line>
Line number:
•
For OC12: 1
•
For OC3: 1–4
•
T3, E3: 1–8
Related Commands
clrlncnt
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-123
Chapter 9
Troubleshooting Commands
dsplncnt
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Example
Display the cell counters for line 1 in bay 1.
MGX8850.11.AXSM.a > dsplncnt 1.1
Line Number
: 1.1
Ingress
Egress
CLP0 Cells
: 0
0
CLP1 Cells*
: 0
0
Valid OAM Cells*
: 0
0
Err OAM Cells*
: 0
0
Invalid VPI/VCI/PTI Cells*: 0
0
Non-zero GFC Cells*
: 0
Last Unknown VPI*
: 0
Last Unknown VCI*
: 0
Discard HecErr Cells
: 115
Corrected HecErr Cells
: 0
NOTE: Counters with '*' do NOT apply to AXSM-1-2488 (OC48)
Cisco MGX 8850 Routing Switch Command Reference
9-124
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dsplns
dsplns
Display Lines
Displays the configuration for all lines on a card. For each line, the output information consists of the:
•
Bay and line number
•
Line state—up (active) or down (inactive)
•
The line type
•
Whether any loopback currently exists on the line
•
Line coding
•
Frame scrambling status (enabled or disabled)
•
Configured line length in meters (applies to only T3 or E3)
•
Criteria for Out of Frame (OOF) error (applies to only T3 or E3)
•
Whether C-bit (AIS) checking is enabled (applies to only T3 or E3)
•
The medium line type—long reach, single-mode fiber, for example
•
The alarm status—clear, critical, and so on
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
Syntax
dsplns
Related Commands
cnfln, delln, dspcds, dspln, upln
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Example
Display the configuration of the lines on an AXSM-4-622.
pop20two.1.AXSM.a > dsplns
Medium Medium
Sonet Line
Line
Line
Frame
Line
Line
Alarm
Line State
Type
Lpbk
Scramble Coding Type
State
----- ----- ------------ ------ -------- ------ ------- -----1.1
Down sonetSts12c NoLoop
Enable Other
Other Clear
1.2
Down sonetSts12c NoLoop
Enable Other
Other Clear
2.1
Up sonetSts12c NoLoop
Enable Other ShortSMF Clear
2.2
Up sonetSts12c NoLoop
Enable Other ShortSMF Critical
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-125
Chapter 9
Troubleshooting Commands
dsplns
Examples
Display line configuration on the current AXSM-1-2488.
pinnacle.1.AXSM.a > dsplns
Medium Medium
Sonet Line
Line
Line
Frame
Line
Line
Line Status
Type
Lpbk
Scramble
Coding Type
----- ----- ------------ ------ -------- -------- ------1.1
Down sonetSts48c NoLoop
Enable Other ShortSingleMode
Display the configuration of each T3 line on the current AXSM-16-T3E3.
jdlenoir.11.AXSM.a > dsplns
Line Line
Line
Line
Length OOF
AIS
Alarm
Num
State
Type
Lpbk
(meters) Criteria cBitsCheck State
---- ------- ----------- ----------- ------ -------- ---------- ----1.1 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
1.2 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
1.3 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
1.4 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
1.5 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
1.6 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
1.7 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
1.8 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
2.1 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
2.2 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
2.3 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
2.4 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
2.5 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
2.6 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
2.7 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
2.8 Down ds3cbitadm
NoLoop
0 3Of8Bits
Check Clear
Cisco MGX 8850 Routing Switch Command Reference
9-126
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dsplog
dsplog
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:
•
Specify an individual log file.
•
Target a specific task.
•
Specify an area of system functionality (called a module in the syntax).
•
Display messages of a particular severity.
•
Specify relative time periods in which errors may have occurred.
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
-log
Specifies the filename of the error log. If you do not specify a file, the output scrolls
through all log files one file at a time. To see a list of the existing log files, execute
dsplogs.
-sl
Specifies the slot number for which to display errors.
-task
Specifies the task for which to display errors.
-mod
Specifies the module or functional area of switch software. The categories are
numerous. Examples are: node alarm manager, card alarm manager, inter-process
communications.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-127
Chapter 9
Troubleshooting Commands
dsplog
-sev
Specifies the severity of the alarm. Select it by entering a number in the range 1–7:
1. EVENT_FATAL: This severity indicates that the event affects the existing data
traffic for the systems and is considered fatal because the platform cannot recover.
Fatal events cause a card reset. Also, any error or condition that damages or causes
loss of ongoing data traffic is fatal. Examples of fatal events are hardware watchdog
timeout, critical task failure or suspension, and hardware device failures of CBC or
QE.
2. EVENT_MAJOR_ALERT: This severity indicates a major service or feature of the
platform has been damaged or lost but that existing data traffic is not affected. These
events indicate that immediate action is necessary to recover the platform or service
by posting traps and major alarms. Examples of major alerts are hard disk crashes,
critical memory shortages, and inability to complete a configuration change.
3. EVENT_MINOR_ALERT: This severity indicates a minor event or partial damage
to or loss of a service on the platform. Nevertheless, existing data traffic and critical
services are not affected. These events indicate that eventual action is necessary to
recover the platform or service by posting a minor alarm condition. Examples of
minor alerts are loss of some tftp or telnet sessions and loss of statistics or other
non-critical features.
4. EVENT_ERROR: This severity indicates that an error occurred but is not sever
enough or it does not know the scope of its implication to be more sever. Most
detected failures are reported with this severity, then the higher levels of software
determine the appropriate response. Examples of these errors are malloc failures,
illegal API parameter values, bad PDUs, and most internally detected failures.
5. EVENT_WARNING: This severity indicates that some threshold has been reached
and could be a warning of a future error condition. Examples are resource shortages
of memory and disk space, voltage and temperature just out of tolerance, and other
conditions that could lead to a more serious situation.
6. EVENT_NOTICE: This severity indicates that a normal but significant event has
occurred on the platform. Events for significant configuration changes would be in
this category. Examples of notice type events would be addition of lines or ports and
connection alarms.
7. EVENT_INFO: This severity indicates an event is informational. It does not
indicate an abnormal condition. Examples of informational events are logging of user
logins and important commands.
-tle
Specifies a particular time for which to display events: same time or earlier time.
-tge
Specifies a particular time for which to display events: same time or later time.
Related Commands
clrlog, dsplogs
Attributes
Log: no log
State: active, standby, init
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
9-128
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dsplog
Example
Display the contents of log file number 1. This example shows the first of multiple screens.
jdlenoir.7.PXM.a > dsplog -log 1
07-00236 11/16/2000-15:21:26 CLI-7-CMDLOG
tTnInTsk01 0x8037558c
cliCmdLog: cisco@telnet.01: (cc 7).
11-00017 11/16/2000-15:21:26 CLI-7-CMDLOG
tSmInTsk03 0x801ef16c
cliCmdLog: cisco@smterm.03: (logout). - 1 dropped
07-00235 11/16/2000-15:18:26 CLI-7-CMDLOG
tTnInTsk01 0x8037558c
cliCmdLog: cisco@telnet.01: (cc 11).
11-00016 11/16/2000-15:18:25 CLI-7-CMDLOG
tSmInTsk02 0x801ef16c
cliCmdLog: cisco@smterm.02: (logout).
11-00015 11/16/2000-15:18:24 CLI-7-CMDLOG
tSmInTsk02 0x801ef16c
cliCmdLog: cisco@smterm.02: (cc 11).
07-00234 11/16/2000-15:18:18 CLI-7-CMDLOG
tTnInTsk01 0x8037558c
cliCmdLog: cisco@telnet.01: (cc 7).
07-00233 11/16/2000-15:18:17 CLI-7-CMDLOG
tTnInTsk01 0x8037558c
cliCmdLog: cisco@telnet.01: (login).
07-00232 11/16/2000-15:18:12 CLI-7-CLITNLOG
Display 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 11
11-00032 11/16/2000-16:35:34 CLI-7-CMDLOG
tSmInTsk03 0x801ef16c
cliCmdLog: superuser@smterm.03: (logout). - 1 dropped
11-00031 11/16/2000-16:34:44 CLI-7-CMDLOG
tSmInTsk02 0x801ef16c
cliCmdLog: superuser@smterm.02: (logout).
11-00030 11/16/2000-16:34:44 CLI-7-CMDLOG
tSmInTsk02 0x801ef16c
cliCmdLog: superuser@smterm.02: (cc 11).
11-00029 11/16/2000-16:33:59 CLI-7-CMDLOG
tSmInTsk03 0x801ef16c
cliCmdLog: superuser@smterm.03: (logout). - 1 dropped
11-00028 11/16/2000-16:32:01 CLI-7-CMDLOG
tSmInTsk02 0x801ef16c
cliCmdLog: superuser@smterm.02: (logout).
11-00027 11/16/2000-16:32:00 CLI-7-CMDLOG
tSmInTsk02 0x801ef16c
cliCmdLog: superuser@smterm.02: (cc 11).
11-00026 11/16/2000-16:15:10 CLI-7-CMDLOG
tSmInTsk03 0x801ef16c
cliCmdLog: superuser@smterm.03: (logout). - 1 dropped
11-00025 11/16/2000-16:12:46 CLI-7-CMDLOG
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-129
Chapter 9
Troubleshooting Commands
dsplogs
dsplogs
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
Log: no log
State: active, standby, init
Privilege: ANYUSER
Example
The output shows that one log file exists. To view the contents of the log file 1, you would enter
dsplog -log 1. See description of dsplog.
jdlenoir.7.PXM.a > dsplogs
Current Event log number: 01
Event log 01: C:/LOG/event01.log
starting timestamp: 11/16/2000-13:29:13
Cisco MGX 8850 Routing Switch Command Reference
9-130
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspndalms
dspndalms
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:
•
dspcdalms identifies line, port, or connection alarms on an AXSM.
•
dspclkalms shows alarms related to network clocks.
•
dspenvalms lists alarms for out-of-range conditions for temperature, voltage sources, and so on.
•
dspslotalms shows card-level alarms, such as a missing card or a disk problem on the PXM-HD.
•
dspswalms shows alarms related to the switching fabric on the PXM45.
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:
•
Critical, indicating complete, non-recoverable failure, loss of data, and do on. The failed entity must
be restored. A power failure or a line being disconnected is an example.
•
Major, indicating service-affecting errors. This event indicates that a major service is damaged or
lost, but the existing traffic is not affected.
•
Minor, indicating non-service affecting errors or errors on a remote node. Corrective action is
appropriate to prevent a serious fault from developing. An example is a fan failure, where no
subscribers are immediately affected, but calamity could result if the situation persists. Note that an
accumulation of lower-level alarms does equal a higher-level alarm.
Cards on Which This Command Runs
PXM45
Syntax
dspndalms [slot]
Syntax Description
slot
The slot number of the card.
Related Commands
dspalm, dspalms
Attributes
Log: no log
State: active
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-131
Chapter 9
Troubleshooting Commands
dspndalms
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 > dspndalms
Node Alarm Summary
Alarm Type
---------Clock Alarms
Switching Alarms
Environment Alarms
Card Alarms
Critical
-------0
0
0
0
Major
------0
0
0
2
Minor
------0
0
0
0
The 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 > dspcdalms
Card Alarm Summary
Slot
---1
2
3
4
5
6
7
8
9
10
11
12
13
14
Critical
-------0
0
0
0
0
0
0
0
0
0
0
0
0
0
Major
------0
0
0
0
0
0
0
2
0
0
0
0
0
0
Minor
------0
0
0
0
0
0
0
0
0
0
0
0
0
0
Use 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 8
Card Alarm Summary
Alarm Type
---------Hardware Alarm
Card State Alarm
Disk Alarm
Line Alarm
Port Alarm
Feeder Alarm
Channel Alarm
Critical
-------0
0
0
0
0
0
0
Major
------0
1
1
0
0
0
0
Minor
------0
0
0
0
0
0
0
Cisco MGX 8850 Routing Switch Command Reference
9-132
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspndalms
Execute dspcds to get an idea of the card state and then, if necessary, execute dspcd for slot 8 to acquire
more details on the state of the card in slot 8. However, the output of dspcds shows that the card set is
missing, which also explains the disk error.
ITNODE3.7.PXM.a > dspcds
ITNODE3
System Rev: 02.00
Backplane Serial No: SAA03140750 Bp HW Rev: B0
Card
Slot
---
Front/Back
Card State
----------
Card
Type
--------
Alarm
Status
--------
Dec. 02, 2000 13:50:15 PST
GMT Offset: -8
Node Alarm: MAJOR
Redundant
Redundancy
Slot
Type
-----------
01
02
03
04
05
06
07
08
09
10
11
12
13
14
Active/Active
Empty
Active/Active
Empty
Active/Active
Empty
Active/Active
Empty Resvd/Emp
Empty
Empty
Empty
Empty
Empty
Empty
AXSM_16T3E3
--AXSM_16OC3
--AXSM_1OC48
--PXM45
---------------
NONE
--NONE
--NONE
--NONE
MAJOR
-------------
NA
--NA
--NA
--08
07
-------------
NO REDUNDANCY
--NO REDUNDANCY
--NO REDUNDANCY
--PRIMARY SLOT
SECONDARY SLOT
-------------
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-133
Chapter 9
Troubleshooting Commands
dsppnportloscallrel
dsppnportloscallrel
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
The portid represents the PNNI logical port and has the format
[shelf.]slot[:subslot].port[:subport]. See also PNNI Format, page 9-3.
Related Commands
cnfpnportloscallrel
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
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 :enabled
Cisco MGX 8850 Routing Switch Command Reference
9-134
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspportcnt
dspportcnt
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 Syntax
dspportcnt <ifNum>
Syntax Description
ifNum
Logical port number. The range depends on the card. For AXSM, the range 1–60.
Related Commands
dspports, dspport, cnfport, dspcds
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-135
Chapter 9
Troubleshooting Commands
dspportcnt
Examples
Display port counters on logical port (ifNum) 1 of the current AXSM.
MGX8850.1.AXSM.a > dspportcnt 1
Cleared at
Current time
Elapsed time
: 06/27/2001 17:43:13
: 06/27/2001 17:44:43
: 0 day(s) 0:1:30 [hh:mm:ss]
Total
Running Avg (cps)
Peak
-------------------------------------------------------------------Arrival CLP0
Ing: 0000000000000000000000
0
0
Arrival CLP1
Ing: 0000000000000000000000
0
0
Ar CLP0 discard Ing: 0000000000000000000000
0
0
Ar CLP1 discard Ing: 0000000000000000000000
0
0
Departure CLP0 Ing: 0000000000000000000000
0
0
Departure CLP1 Ing: 0000000000000000000000
0
0
Arrival CLP0
Arrival CLP1
Ar CLP0 discard
Ar CLP1 discard
Departure CLP0
Departure CLP1
Egr:
Egr:
Egr:
Egr:
Egr:
Egr:
0000000000000000000000
0000000000000000000000
0000000000000000000000
0000000000000000000000
0000000000000000000000
0000000000000000000000
0
0
0
0
0
0
0
0
0
0
0
0
Cisco MGX 8850 Routing Switch Command Reference
9-136
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspprfhist
dspprfhist
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
Syntax
dspprfhist
Syntax Description
This command takes no parameters.
Attributes
Log: no log
State: active, standby
Privilege: ANYUSER
Example
Display the performance history on the current AXSM. The example display shows a completely idle
system.
pop20two.1.AXSM.a > dspprfhist
CURRENT TIME
0:45:4
Sample #
0
0:44:27(From)-0:44:47(To)
TASK
TaskId
%
--------------------------------------INTERRUPT
0.0000
KERNEL
0.0000
IDLE
100.0000
UNKOWN
0.0000
Sample #
-1
0:44:7(From)-0:44:27(To)
TASK
TaskId
%
--------------------------------------INTERRUPT
0.0000
KERNEL
0.0000
IDLE
100.0000
UNKOWN
0.0000
Sample #
-2
0:43:47(From)-0:44:7(To)
TASK
TaskId
%
---------------------------------------
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-137
Chapter 9
Troubleshooting Commands
dspswalm
dspswalm
Display Switching Alarms—displays alarms for switching circuits on the PXM45.
The dspswalm command can be used to determine if a card should be returned to Cisco for repair. For
optional fault isolation after you execute dspswalm, use the crossbar commands to see if crossbar errors
have occurred. The crossbar-specific commands apply to hardware or software developers who may need
analyze the behavior of the switch ASIC. In the PXM45, if one switch ASIC (out of three) has serious
errors, the total switch capacity falls short of the maximum 45 Gbps.
The following is a top-down sequence of alarm-related commands that lead to isolating possible faults
in the switch fabric (or crossbar):
1.
dspndalms
2.
dspswalms
3.
dspxbaralm
4.
dspxbarerrcnt
An alarm can originate in any of the following:
•
The backplane or any other part of signal path that connects a service module with a switch ASIC
•
Crossbar ASIC on the PXM45
•
Buffer circuitry on a service module
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
•
Critical, indicating complete, non-recoverable failure, loss of data, and do on. The failed entity must
be restored. A power failure or a line being disconnected is an example.
•
Major, indicating service-affecting errors. This event indicates that a major service is damaged or
lost, but the existing traffic is not affected.
•
Minor, indicating non-service affecting errors or errors on a remote node. Corrective action is
appropriate to prevent a serious fault from developing. An example is a fan failure, where no
subscribers are immediately affected, but calamity could result if the situation persists. Note that an
accumulation of lower-level alarms does equal a higher-level alarm.
Cards on Which This Command Runs
PXM45
Syntax
dspswalms
Syntax Description
This command takes no parameters.
Related Commands
dspndalms, dspxbarerrcnt
Cisco MGX 8850 Routing Switch Command Reference
9-138
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspswalm
Attributes
Log: no log
State: active
Privilege: ANYUSER
Examples
Display switching alarms.
node_chi.8.PXM.a > dspswalms
Node Switching Alarm Summary
Card Crossbar
Crossbar Fabric
Humvee Alarm
Critical
Critical
Critical
0
0
0
Major
Major
Major
0
0
0
Minor
Minor
Minor
0
0
0
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-139
Chapter 9
Troubleshooting Commands
dsptrapmgr
dsptrapmgr
Display Trap Manager
Display details about all existing trap managers. The dsptrapmgr output shows:
•
IP address of each trap manager
•
Port number on the connected work station
•
Row status
•
Read trap flag stats
•
Next trap sequence number
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
Log: no log
State: active
Privilege: ANYUSER
Example
Display trap managers.
node19.8.PXM.a > dsptrapmgr
ipAddress
PortNum RowStatus
--------------- ------- ---------171.71.55.21
2500
Add
172.29.65.87
2500
Add
172.71.59.21
2500
Add
LastTrapSeqNum:
NumOfValidEntries:
ReadTrapFlag
-----------Off
Off
Off
NextTrapSeqNum
-------------0
348
0
385
3
Cisco MGX 8850 Routing Switch Command Reference
9-140
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspxbar
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 configuration normally has fixed
default values and is not configurable.
Note
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. Normally, to isolate a
switching problem to determine whether to return a card, the dspswalm command is sufficient.
The crossbar-related commands are special debug commands with infrequent use. An engineer that
needs to alter certain error thresholds for hardware or software development can use the
cnfxbarerrthresh commands.
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 focus of the crossbar commands is from the switch ASICs outwards, to
the card slots. The reference point in relation to card slots is important and has to do with the wiring of
the backplane. The connectivity between the cards and the switch fabric—consisting of all the switch
ASICs in total—forms a mesh: each switch ASIC communicates with each card, and each card can use
any ASIC. Therefore, if one 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 backplane trace can no longer carry data between an
individual ASIC pin and a particular card slot. The dspxbarerrcnt command can help isolate such faults.
Regardless, at the node level, the dspswalms command is sufficient for determining whether to replace
the card with switching problem.
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 the:
•
Selected ASIC number (default 0 is unspecified).
•
Number of the slot where the crossbar ASIC resides (7 or 8 for an MGX 8850 node).
•
Number of the ASIC (0–2 in an MGX 8850 node).
•
Revision number of the ASIC.
•
Status of the ASIC.The status is either failed or OK. If the status is failed, the other ASICs must
carry the switching load, and the throughput of the switch falls below the maximum. In this case,
Cisco Systems recommends you replace the card.
•
The cell grant mode is always Multicast Preferred.
•
The Resync Sframe Tic is the rising edge of the clock. Sframe refers to a switch frame. (A switch
frame is a 60-byte cell that carries a 53-byte ATM cell plus a special header for internal fabric use
between the switching fabric and the service module.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-141
Chapter 9
Troubleshooting Commands
dspxbar
The crossbar configuration consists of four categories of information for each slot:
•
The type of backpressure is always Inband (meaning ingress direction). A crossbar does not have
buffers (as the AXSMs do) and therefore must send backpressure signals to the queuing chips on
each AXSM if congestion begins to occur in the switching plane.
•
The Disable Request field automatically indicates any requests to turn off a source or destination for
the link between the ASIC and the service module. The hardware alone generates the disable
request, so you cannot make a disable request as part of troubleshooting.
•
The Disable Data field indicates whether data transfer has been turned off for source or destination.
In the current product, the field for source and destination always is No.
•
The Redundancy Configuration field shows the mode of redundancy used by the ASIC and whether
redundancy configuration exists for a slot. The redundancy mode is always Remap. Remap means
that the switching fabric automatically maps cell transfers to the correct slot if a switchover occurs
in a redundant pair. Note that, if a switchover occurs, the logical slot number in the endpoint ID stays
the same.
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
From the number of fixed values in the preceding fields, you can see that very little can change in the
crossbar configuration itself.
Cards on Which This Command Runs
PXM45
Syntax
dspxbar [slot] [plane]
Syntax Description
slot
(Optional.) The slot number of the XM60. Valid slot numbers are 9, 10, 25, and 26.
Subsequently, specify a switching plane in the range 0 to 3.
plane
(Optional.) The number of the switching plane. If you do not specify a plane, the
system displays information for plane 0 as a default. In an MGX 8850 node, the range
is 0–2.
Related Commands
dspswalm, dspxbaralm, dspxbarerrthresh, dspxbarerrcnt, clrxbaralm, clrxbarerrcnt
Attributes
Log: no log
State: active, standby, init
Privilege: ANYUSER
Cisco MGX 8850 Routing Switch Command Reference
9-142
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspxbar
Example
Display switch ASIC (or switch plane or crossbar) 0.
MGX8850.8.PXM.a > dspxbar
MGX8850
System Rev: 02.00
Jul. 13, 2000 18:14:33 GMT
PXM45 CROSSBAR CONFIGURATION
Crossbar Slot No: 7
Switch Asic No: 0
Status: OK
Cell Grant Mode: Multicast Pref
Resync Sframe Tic: Rising-Edge Detect
Asic Revision: 1
Slot BACK PRESSURE
DISABLE REQUEST DISABLE DATA
REDUNDANCY CONFIG
No
Grant
Mode
Dest
Src
Dest
Src
Mode
Slot
---- --------------------------- ----------------------------1
Valid
InBand
No
No
No
No
Remap
1
2
Valid
InBand
No
No
No
No
Remap
2
3
Valid
InBand
No
No
No
No
Remap
3
4
Valid
InBand
No
No
No
No
Remap
4
5
Valid
InBand
No
No
No
No
Remap
5
6
Valid
InBand
No
No
No
No
Remap
6
7
Valid
InBand
No
No
No
No
Remap
7
8
Valid
InBand
No
No
No
No
Remap
8
9
Valid
InBand
No
No
No
No
Remap
9
10
Valid
InBand
No
No
No
No
Remap
10
11
Valid
InBand
No
No
No
No
Remap
11
12
Valid
InBand
No
No
No
No
Remap
12
13
Valid
InBand
No
No
No
No
Remap
13
14
Valid
InBand
No
No
No
No
Remap
14
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-143
Chapter 9
Troubleshooting Commands
dspxbaralm
dspxbaralm
Display Crossbar Alarms—display severity of crossbar alarms.
The dspxbaralm command shows whether a crossbar alarm is minor, major, or critical. The display
shows status on both the active and standby PXM45.
Note
This low-level command normally applies to software or hardware development and therefore is not
useful for troubleshooting at the network or node level. For troubleshooting at the switch level, use
dspndalms and dspswalms.
For fault isolation after you execute dspxbaralm, you can survey the possible errors (illustrated in the
example). The following is a top-down sequence of alarm-related commands:
1.
dspndalms
2.
dspswalms
3.
dspxbaralm
4.
dspxbarerrcnt
Cards on Which This Command Runs
PXM45
Syntax
dspxbaralm
Syntax Description
This command takes no parameters.
Attributes
Log: no log
State: active
Privilege: ANYUSER
Related Commands
dspxbar, dspxbarerrcnt, dspxbarerrthresh, dspndalms, dspswalms
Cisco MGX 8850 Routing Switch Command Reference
9-144
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspxbaralm
Example
Display the severity of crossbar alarms. On the card in slot 7, crossbars 1 and 2 show errors. In such a
case as two crossbars showing major errors, a card in a slot rather than a switch ASIC may be at fault.
Therefore, you could execute dspcds to see if service module has an alarm or dspxbarerrcnt for switch
ASICs 1 and 2 to see if each ASIC is showing similar data for the same card slot. You could also execute
dspcdalm on the PXM45.
MGX8850.7.PXM.a > dspxbaralm
MGX8850
System Rev: 02.00
MGX8850
Slot
Plane
Severity
--------------7
0
None
7
1
Major
7
2
Major
8
0
None
8
1
None
8
2
None
Aug. 06, 2000 17:46:15 GMT
Node Alarm: CRITICAL
Subsequent execution of dspxbarerrcnt shows the slot number (or link) and types of errors.
Note the large number of errors in slot 12. Many of the errors are parity or CRC related,
but the one error that is most serious is loss of sync. With a loss if sync between the
service module and the switching fabric, many other, comparatively less significant errors
are possible.
MGX8850.7.PXM.a > dspxbarerrcnt 7 2
MGX8850
System Rev: 02.00
MGX8850
Aug. 06, 2000 17:47:53 GMT
Node Alarm: CRITICAL
PXM45 CROSSBAR CURRENT ERROR COUNTERS
Crossbar Slot No: 7
Loss
Rx
Slot
Sync
Cv
------ ------ -----1
0
0
2
0
0
3
0
0
4
0
0
5
0
0
6
0
0
7
0
0
8
0
0
9
0
0
10
0
0
11
0
0
12
2772K 41594K
13
0
0
MGX8850
MGX8850
14
Rx
Disp
-----0
0
0
0
0
0
0
0
0
0
0
41594K
0
Switch ASIC No:
Xmit
Hdr
Par
CRC
------ -----0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
41594K
0
0
2
Pload
CRC
-----0
0
0
0
0
0
0
0
0
0
0
41594K
0
System Rev: 02.00
0
0
0
0
0
Slot
Remap
-----0
0
0
0
0
0
0
0
0
0
0
0
0
Slot
Recur
-----0
0
0
0
0
0
0
0
0
0
0
0
0
BP
Par
-----0
0
0
0
0
0
0
0
0
0
0
41594K
0
Aug. 06, 2000 17:47:53 GMT
Node Alarm: CRITICAL
0
0
0
0
Frame Tick Error: 0
Frame Lock Error: 0
ACP Illegal Address Error: 0
Note: for big error counter, suffix K(x1000) or M(x1000000) is used.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-145
Chapter 9
Troubleshooting Commands
dspxbarerrcnt
dspxbarerrcnt
Display Crossbar Error Counters—display the count of various types of errors.
The dspxbarerrcnt 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
This low-level command applies to software or hardware development and is not useful for
troubleshooting the network or node. For troubleshooting the node, use dspndalms and dspswalms.
You can see the thresholds of the alarms that the errors trigger by using dspxbarerrthresh.
The following types and instances of errors appear by slot number (see example screen):
•
Loss of synchronization between the ASIC and the queuing circuitry on the service module. The
synchronization in this case applies to the timing of the internal switching frames (Sframes). Loss
of synchronization is a very serious error.
•
Receiver code violations (Rx Cv column in the display).
•
Receiver disparity errors (Rx Disp column in the display). A disparity error is a summary of five
ASIC-specific alarms.
•
Transmitter parity errors.
•
CRC failures for the header or the payload of the 60-byte Sframe.
•
Failures to remap between slots as needed or excessive remapping between slots (Slot Remap and
Slot Recur columns in the display).
•
Parity errors in back-pressure messages.
A top-down sequence of troubleshooting commands for isolating faults in the switching fabric are:
1.
dspndalms
2.
dspswalms
3.
dspxbaralm
4.
dspxbarerrcnt
Cards on Which This Command Runs
PXM45
Syntax
dspxbarerrcnt <slot> <plane>
Syntax Description
slot
The slot of the switching fabric. On the MGX 8850 node, the slot is 7 or 8.
plane
The plane is the number of the switch ASIC. On the MGX 8850 node, the range for
either slot is 0–2.
Cisco MGX 8850 Routing Switch Command Reference
9-146
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspxbarerrcnt
Related Commands
dspxbar, dspxbaralm, dspxbarerrthresh, cnfxbarerrthresh, dspndalms, dspswalms
Attributes
Log: log
State: active, standby
Privilege: ANYUSER
Example
Display the crossbar error counters for switch ASIC 2 in slot 7. The Node Alarm field of the display
shows the errors have resulted in a critical alarm. A large number of errors have occurred in the slot 12
link. Many of the errors are parity or CRC related, but the one error that is most serious is loss of sync.
With a loss if sync between the service module and the switching fabric, many other, comparatively less
significant errors are possible.
Note at the bottom of the display a message about multipliers for large numbers of errors. Because the
display can accommodate a finite number of errors without being distorted, a K (for 1000) and M (for
1000000) multiplier may be necessary, as this example shows.
MGX8850.7.PXM.a > dspxbarerrcnt 7 2
MGX8850
System Rev: 02.00
MGX8850
Aug. 06, 2000 17:47:53 GMT
Node Alarm: CRITICAL
PXM45 CROSSBAR CURRENT ERROR COUNTERS
Crossbar Slot No: 7
Loss
Rx
Slot
Sync
Cv
------ ------ -----1
0
0
2
0
0
3
0
0
4
0
0
5
0
0
6
0
0
7
0
0
8
0
0
9
0
0
10
0
0
11
0
0
12
2772K 41594K
13
0
0
Rx
Disp
-----0
0
0
0
0
0
0
0
0
0
0
41594K
0
Switch ASIC No:
Xmit
Hdr
Par
CRC
------ -----0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
41594K
0
0
2
Pload
CRC
-----0
0
0
0
0
0
0
0
0
0
0
41594K
0
Slot
Remap
-----0
0
0
0
0
0
0
0
0
0
0
0
0
Slot
Recur
-----0
0
0
0
0
0
0
0
0
0
0
0
0
BP
Par
-----0
0
0
0
0
0
0
0
0
0
0
41594K
0
MGX8850
System Rev: 02.00
Aug. 06, 2000 17:47:53 GMT
MGX8850
Node Alarm: CRITICAL
14
0
0
0
0
0
0
0
0
0
Frame Tick Error: 0
Frame Lock Error: 0
ACP Illegal Address Error: 0
Note: for big error counter, suffix K(x1000) or M(x1000000) is used.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-147
Chapter 9
Troubleshooting Commands
dspxbarerrthresh
dspxbarerrthresh
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
•
Duration of the errored state
•
Number of errors during that time period
•
Upper and lower error counts within a particular alarm severity (minor, major, and critical)
The default settings for crossbar error thresholds are optimal for nearly all applications. The
dspxbarerrthresh command shows the existing thresholds. If necessary, you can change thresholds
through the cnfxbarerrthresh command.
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.
Loss of synchronization (LossOfSync)
2.
Transceiver error (TranscieverErr)
3.
DisparityErr—an accumulation of five ASIC-level errors
4.
ParityErr—a parity error in the switch frame as a whole
5.
HeaderCRCErr—a CRC error for the switch frame header
6.
PayloadCRCErr—a CRC error for the switch frame payload
7.
RemapTwiceErr
8.
RemapRecurrErr
9.
Backpressure parity error (B.P.ParityErr)—a parity error in the signaling for backpressure
Cards on Which This Command Runs
PXM45
Syntax
dspxbarerrthresh
Syntax Description
This command takes no parameters.
Cisco MGX 8850 Routing Switch Command Reference
9-148
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspxbarerrthresh
Related Commands
dspxbar, dspxbaralm, dspxbarerrcnt
Attributes
Log: no log
State: active
Privilege: ANYUSER
Example
Display the current crossbar error thresholds.
JBP2_Lower.8.PXM.a > dspxbarerrthresh
JBP2_Lower
System Rev: 02.01
Nov. 28, 2000 21:39:29 GMT
MGX8850 (JBP-2)
Node Alarm: MAJOR
CROSSBAR ERROR CONFIGURATION
Thresh -- MINOR --- MAJOR --- CRITICAL -Device Error
Time
Clear Alarm
Clear Alarm
Clear Alarm
Type
(msec) Count Count
Count Count
Count Count
-------------------- ------ ----- --------- --------- ----LossOfSync
20000
0
3
4
15
300
301
TranscieverErr
20000
0
31
40
150
300
301
DisparityErr
20000
0
31
40
150
300
301
ParityErr
20000
300
301
300
301
300
301
HeaderCRCErr
20000
0
31
40
150
300
301
PayloadCRCErr
20000
0
31
40
150
300
301
RemapTwiceErr
20000
0
1
0
1
300
301
RemapRecurrErr
20000
300
301
300
301
300
301
B.P.ParityErr
20000
0
31
40
150
300
301
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-149
Chapter 9
Troubleshooting Commands
dspxbarmgmt
dspxbarmgmt
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
Log: no log
State: active, standby, init
Privilege: ANYUSER
Example
Display the crossbar management state for the current node. The settings are the defaults.
pop20two.7.PXM.a > dspxbarmgmt
pop20two
MGX8850
Load Sharing: Enable
Auto Shutdown: Disable
Plane Alarm Threshold: 3
System Rev: 02.01
Dec. 05, 2000 20:43:43 GMT
Node Alarm: MAJOR
Cisco MGX 8850 Routing Switch Command Reference
9-150
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dspxbarstatus
dspxbarstatus
Display Crossbar Status
Display status of each slot for a crossbar.
Cards on Which This Command Runs
PXM45
Syntax
dspxbarstatus [plane]
Syntax Description
plane
(Optional.) The number of the switching plane. The default is 0. For the MGX 8850
node, the range is 0–2.
Related Commands
dspxbar, dspxbaralm, dsperrcnt, dsperrthresh
Attributes
Log: no log
State: active, standby, init
Privilege: ANYUSER
Example
Display the status of switch ASIC 0. The active PXM45 in this example is in slot 7.
MGX8850
System Rev: 02.00
MGX8850
Switch CD No: 7
Switch ASIC No: 0
Administrative Status Bitmap: 0xFFFFFFFF
Operational Status Bitmap
: 0x0
Error Status Bitmap:
Slot 1: 0x0
Slot 2: 0x0
Slot 3: 0x0
Slot 4: 0x0
Slot 5: 0x0
Slot 6: 0x0
Slot 7: 0x0
Slot 8: 0x0
Slot 9: 0x0
Slot 10: 0x0
Slot 11: 0x0
Slot 12: 0x0
Slot 13: 0x0
Slot 14: 0x0
Slot 15: 0x0
Slot 16: 0x0
Jul. 13, 2000 18:26:54 GMT
Node Alarm: UNKNOWN
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-151
Chapter 9
Troubleshooting Commands
dspxbarstatus
Misc Error Bitmap: 0x0
Cisco MGX 8850 Routing Switch Command Reference
9-152
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
dumptrace
dumptrace
Dump Trace—place the contents of a trace in a log file and show the name of the file.
The output of dumptrace is a filename. Provide this name to dsplog -log option to see its contents.
Cards on Which This Command Runs
PXM45
Syntax
dumptrace
Syntax Description
This command takes no parameters.
Related Commands
dsplog, dsplogs
Attributes
Log: no log
State: active, standby
Privilege: SERVICE_GP
Example
Execute dumptrace, then view the contents with dsplog.
pop20one.7.PXM.a > dumptrace
The trace is saved in file error50.log
Display the contents of error log file 50. This example shows only the first screen.
pop20two.7.PXM.a > dsplog -log error50
07-00140 11/30/2000-23:10:59 SCM-4-RESP_TIMEOUT
tSCM
0x80260d20
Timeout waiting for response for slot 9, report to PMM
07-00139 11/30/2000-23:10:20 CLI-7-CMDLOG
tDbgCmdTsk 0x80377d9c
cliCmdLog: cisco@console: "cnfname pop20two".
07-00138 11/30/2000-23:10:20 PROO-6-soPRctcEvRcv
PnProot
0x8068b894
proot_ctc_event_hdlr(): received EVENT 0x63 from CTC
07-00137 11/30/2000-23:10:08 CLI-7-CMDLOG
tDbgInTask 0x80377d9c
cliCmdLog: cisco@console: (cc 7).
07-00136 11/30/2000-23:10:07 CLI-7-CMDLOG
tDbgInTask 0x80377d9c
cliCmdLog: cisco@console: (login).
07-00134 11/30/2000-23:08:23 SHM_-7-CARD_FAIL
ShelfMgr
0x802e73b4
SHM: slot 9 failed reason SHM_CDF_MAX_RESETS_REACHED [7]
07-00135 11/30/2000-23:08:23 SHM_-7-ALM_SET
ShelfMgr
0x8030ccf4
SHM Alarm Raised: pslot: 9, AlarmId: 0x2800b(SHM_ALM_NON_RES_FC_FAILED) - 3 dropped
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-153
Chapter 9
Troubleshooting Commands
offdiagstat
offdiagstat
Off Diagnostics Statistics
Halts the statistical diagnostic program that keeps count of how many times the diagnostics have run.
Syntax
offdiagstat
Syntax Description
This command takes no parameters.
Cards on Which This Command Runs
AXSM
Related Commands
ondiagstat
Attributes
Log: log
State: active
Privilege: SERVICE_GP
Example
pop20one.10.AXSM.a > offdiagstat
Disabling diag stats, enabling bucket stats.
Cisco MGX 8850 Routing Switch Command Reference
9-154
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
ondiagstat
ondiagstat
On Diagnostics Statistics
Starts running the diagnostics statistics program that keeps count of how many times diagnostics has run.
Syntax
ondiagstat
Syntax Description
This command takes no parameters.
Cards on Which This Command Runs
AXSM
Related Commands
offdiagstat
Attributes
Log: log
State: active
Privilege: SERVICE_GP
Example
pop20one.10.AXSM.a > ondiagstat
Enabling diag stats, disabling bucket stats.
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-155
Chapter 9
Troubleshooting Commands
pathtraceie
pathtraceie
Path Trace IE
Removes or inserts path trace information element (IE) at port level.
Cards on Which This Command Runs
PXM45
Syntax
pathtraceie <portid>
{rmv | ins}
Syntax Description
portid
The portid represents the PNNI logical port and has the format
[shelf.]slot[:subslot].port[:subport]. See also PNNI Format, page 9-3.
rmv
Allow to remove Trace Transit List IE at the port.
ins
Allow to insert Trace Transit List IE at the port.
Related Commands
conntrace, pathtraceport, pathracenode
Attributes
Log: log
State: active
Privilege: SUPER_GP
Cisco MGX 8850 Routing Switch Command Reference
9-156
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
pathtracenode
pathtracenode
Path Trace Node
Enables or disables path trace feature at the node level.
Cards on Which This Command Runs
PXM45
Syntax
pathtracenode {enable | disable}
Syntax Description
enable/disable
Enables (disables) path trace at node level.
Related Commands
conntrace, pathtraceport, pathtraceie
Attributes
Log: log
State: active
Privilege: SUPER_GP
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-157
Chapter 9
Troubleshooting Commands
pathtraceport
pathtraceport
Call Control Operations: Enable/Disable Path Trace at Port Level
Enables (disables) path trace feature at port level, then saves the result of the path trace in the log file.
Cards on Which This Command Runs
PXM45
Syntax
pathtraceport <portid>
{enable | disable}
[-H {on | off}]
[-CB {on | off}]
[-V {on | off}]
[-CR {on | off}]
[-cldnum called-AESA]
[-clgnum calling-AESA]
Syntax Description
portid
The portid represents the PNNI logical port and has the format
[shelf.]slot[:subslot].port[:subport]. See also PNNI Format, page 9-3.
enable | disable
Enables (disables) path trace at port level.
-H
Specifies the hierarchy option. If enabled, information from all the DTLs in
the hierarchy are added in the TTL IE.
Default = off
-CB
Specifies the crankback option. If enabled, the failure cause for crankback is
included in the TTL IE.
Default = on
-V
Specifies the VPI/VCI option. If enabled, VPI/VCI values of the egress port
are added in the TTL IE at every node.
Default = off
-CR
Specifies the call reference option. If enabled, call reference values of all
egress ports are added in the TTL IE.
Default = off
-cldnum
Specifies the called party number. Enables (disables) path trace on a specific
called address.
-clgnum
Specifies the calling party number. Enables (disables) path trace on a specific
calling address.
Cisco MGX 8850 Routing Switch Command Reference
9-158
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
pathtraceport
Related Commands
conntrace, pathracenode, pathraceie
Attributes
Log: log
State: active
Privilege: SUPER_GP
Examples
Format of the path trace result for a call in the log file:
Result:Succ/Fail Reason: "Desc" Called No: "--" Calling No: "--"
Cause: "value:Desc"
NodeId Ingress Port Egress Port Vpi/Vci Call Ref EndPtRef (opt)
XXXX
YYYY
ZZZZ
aaa/bbb
cccc
dddd
XXXX
YYYY
ZZZZ
aaa/bbb
cccc
dddd
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-159
Chapter 9
Troubleshooting Commands
resetcd
resetcd
Reset Card—resets the card or the failure history.
The resetcd command lets you reset a card or, if you specify the appropriate option, the failure history
of a card.
Using the resetcd command without defining a slot number results in an ungraceful (disruptive)
upgrade. This is the fastest method to upgrade a card, but it disrupts service.
A graceful (non-disruptive) upgrade requires that the loadrev, runrev, and commitrev commands have
already been executed and that the card is identified in the command string.
Cards on Which This Command Runs
PXM45
Syntax
resetcd
[slot]
[ -f]
Syntax Description
slot
The optional slot parameter identifies a card to reset. If you do not specify a slot, the
command targets the current PXM45.
-f
Specifies that the command resets only the failure history of a card.
Related Commands
resetsys
Attributes
Log: no log
State: active, init
Privilege: SUPER_GP
Example
Reset the current PXM45.
pinnacle.7.PXM.a > resetcd
The card in slot number 7, will be reset. Please confirm action
Do you want to proceed (Yes/No)? n
(command not executed)
Reset the failure history of the card in slot 1.
8850_NY.7.PXM.a > resetcd 1 -f
Clearing (-F) Failed state on slot 1. Please confirm action
resetcd: Do you want to proceed (Yes/No)?
Cisco MGX 8850 Routing Switch Command Reference
9-160
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
resetsys
resetsys
Reset System
Reset the entire node.
Cards on Which This Command Runs
PXM45
Syntax
resetsys
Syntax Description
This command takes no parameters but displays a warning and prompts you to continue the execution.
Related Commands
resetcd
Attributes
Log: no log
State: active, init
Privilege: SUPER_GP
Example
Reset the system.
pinnacle.7.PXM.a > resetsys
This command resets the entire shelf, a destructive command.
Please confirm now!
Do you want to proceed (Yes/No)? n
(command not executed)
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-161
Chapter 9
Troubleshooting Commands
switchcc
switchcc
Switch Core Cards
Switch control of the node from the active PXM45 to the standby PXM45. If a standby PXM45 is not
available, the switchcc command fails.
You cannot execute switchcc during a configuration-copy. If you attempt it, the system blocks the
command. Furthermore, the command fails if the switch is unstable or if the standby PXM45 is not in
the standby state.
Cards on Which This Command Runs
PXM45
Syntax
switchcc
Related Commands
None
Attributes
Log: no log
State: active
Privilege: SERVICE_GP
Example
Attempt a switchcc without a standby PXM45 in the backplane.
raviraj.7.PXM.a > switchcc
Do you want to proceed (Yes/No)? y
Core card redundancy unavailable
raviraj.7.PXM.a >
Cisco MGX 8850 Routing Switch Command Reference
9-162
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
tstconseg
tstconseg
Test Connection Segment
Test the integrity of an SVC or SPVC. With tstconseg, a single collection of supervisory cells is sent in
the egress direction between the card and service equipment (CPE). (See tstdelay for ingress direction.)
When the test successfully starts, the system displays a message stating that the test has begun and
directs you to use either dspcon or dspchantests to see the results. The dspcon command shows detailed
information about the connection and has a field for the results of this test. The dspchantests command
display only the results of the test.
Note
The dspcon fields on the AXSM for round trip delay—including the status of OAM
loopback—always show the results of the latest test and are not changed until a new execution of
tstconseg or tstdelay. Therefore, re-executing dspcon does not clear the value for RTD or the
indication that an OAM loopback is present. The only way to reset these fields to null is to down the
port (through dnport).
Cards on Which This Command Runs
AXSM
Syntax
tstconseg <ifNum> <vpi> <vci>
[-num <iterations>]
Syntax Description
ifNum
The logical port number. The range for AXSM is 1–60.
vpi
The VPI range for the SVC or SPVC is 1–255.
vci
The VCI range for the SVC is 32–65535.
-num
(Optional) Specifies the number of times a collection of supervisory cells should
traverse the SVC for the current execution of tstconseg.
Related Commands
dspcon, tstdelay, dspchantests
Attributes
Log: log
State: active
Privilege: GROUP1
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-163
Chapter 9
Troubleshooting Commands
tstconseg
Example
Test the integrity of 1 10 1000 in the egress direction.
node19.1.AXSM.a > tstconseg 1 10 100
Test started; Use dspcon/dspchantests to see test results
Cisco MGX 8850 Routing Switch Command Reference
9-164
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
tstdelay
tstdelay
Test Delay
Test the integrity of the connection in the ingress direction by sending a collection of supervisory cells
to the remote end of the network and back. (See tstconseg for the egress direction.) The tstdelay
command applies to only SPVCs.
If the test successfully begins, the display states the fact and directs you to use the dspcon or
dspchantests command to view the round trip time in microseconds. The dspcon display shows detailed
information on the connection and has a field for the test results. The dspchantests display shows the
results of only the round trip delay test.
Note
The dspcon fields on the AXSM for round trip delay—including the status of OAM
loopback—always show the results of the latest test and are not changed until a new execution of
tstconseg or tstdelay. Therefore, re-executing dspcon does not clear the value for RTD or the
indication that an OAM loopback is present. The only way to reset these fields to null is to down the
port (through dnport).
Note
The primary purpose of tstdelay is to test the integrity of the connection. The round trip time is not
accurate enough for any use that requires an accurate measurement of delay.
Cards on Which This Command Runs
AXSM
Syntax
tstdelay <ifNum> <vpi> <vci>
[-num <iterations>]
Syntax Description
ifNum
The logical port number. The range for AXSM is 1–60.
vpi
Virtual path identifier. On the AXSM, the range is 1–255.
vci
Virtual connection identifier. On the AXSM, the range is 32–65535 for a VCC. For a
VPC, the vci is 0.
-num
(Optional) Specifies the number of times a collection of supervisory cells should
traverse the SVC for the current execution of tstdelay.
Related Commands
dspcons, tstconseg, dspcon
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-165
Chapter 9
Troubleshooting Commands
tstdelay
Attributes
Log: log
State: active
Privilege: GROUP1
Example
On the AXSM slot, get the round-trip delay for connection 1 10 100. This example contains four
command executions to illustrate how to obtain a list of logical ports; obtain a connection number; start
the test; and view the results. the commands are dspports, dspcons, tstdelay, and dspcon.
Step 1
Identify the logical ports on the card by executing dspports. For this example, the logical port (ifNum
in the display) is 1.
node19.1.AXSM.a > dspports
ifNum Line Admin Oper. Guaranteed Maximum
Port SCT Id
ifType VPI
State State Rate
Rate
(VNNI only)
----- ---- ----- ----- ---------- --------- ----------------- ------ ---------1 1.1
Up
Up
1412831
1412831
6
UNI
0
Step 2
Get the connection ID to provide to tstdelay. The connection identifier appears in NSAP format. In this
example, assume tstdelay execution occurs at the slave end of the SPVC. Take the significant digits from
the Identifier (01.0010.00100) to get the logical port, VPI, and VCI for tstdelay. These values are 1, 10,
and 100.
node19.1.AXSM.a > dspcons
record
Identifier
Type
-----------------0 01.0010.00100
VCC
1 01.0011.00101
VCC
Step 3
SrvcType
-------ubr1
ubr1
M/S
--S
M
Upld
---0000ebfb
0000ec27
Alarm
----none
none
Execute tstdelay for logical port 1, vpi 10, vci 100. The system response shows that the command started
correctly and directs you to use dspcon or dspchantests to see the results.
node19.1.AXSM.a > tstdelay 1 10 100
Test started; Use dspcon/dspchantests to see test results
Step 4
Execute dspchantests to see the results as displayed by this command. The units of measure for the
round trip delay is microseconds.
node19.1.AXSM.a > dspchantests 1 10 100
Connection Id
Test Type
Direction
=============
=========
=========
01.0010.00100:
OAM Lpbk
ingress
Step 5
Result
=======
Success
Round Trip Delay
================
30000
Execute dspcon to see the results as displayed by this command. The line with test results appears
towards the end of the display and begins with Loopback Type. The Direction field shows ingress,
indicating the tstdelay command produced these results. (If tstconseg had been the last test command,
this field would say egress.) The RTD (round trip delay) field shows 30000 microseconds.
node19.1.AXSM.a > dspcon 1 10 100
-------------------------------------------------------------------------Local
:
NSAP Address
port
vpi
vci
(S)
4700918100000000001A53C82D00000101180100 1.01.01
10
100
Remote :
NSAP Address
port
vpi
vci
(M)
4700918100000000001A53C82D00000101180100 1.01.01
11
101
-------------------------------------------------------------------------Conn. Type
:
VCC
Admn Status : ADMN-UP
Service Type :
ubr1
Rtng Status : -67372037
Controller
:
2
Cisco MGX 8850 Routing Switch Command Reference
9-166
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
tstdelay
-------------------------------------------------------------------------Local PCR
:
14
Remote PCR
:
14
Local SCR
:
3
Remote SCR
:
3
Local CDV
:
-1
Remote CDV
:
-1
Local CTD
:
-1
Remote CTD
:
-1
Local MBS
:
1
Remote MBS
:
1
Local CDVT
:
-1
Remote CDVT :
-1
Admin weight :
-1
Frame discard:
N
-------------------------------------------------------------------------OAM CC Config : DISABLED
Statistics
: DISABLED
-------------------------------------------------------------------------Loopback Type : OAM Lpbk | Dir: ingress | Status: Success | RTD:
30000 us
--------------------------------------------------------------------------------------------------------------------------------------------------Port side Tx : normal
Swth side Tx : normal
Port side Rx : normal
Swth side Rx : normal
-------------------------------------------------------------------------I-AIS/RDI
E-AIS/RDI
CONDITIONED
CCFAIL
IfFail
Mismatch
NO
NO
NO
NO
NO
NO
--------------------------------------------------------------------------
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-167
Chapter 9
Troubleshooting Commands
upcon
upcon
Up Connection—return a downed connection to the active (administratively up) state.
Activate a connection that was previously brought down by the dncon command. (The typical purpose
of dncon is some form of operational modification or troubleshooting.) Execute upcon at the master end
of the connection.
Cards on Which This Command Runs
AXSM
Syntax
upcon <ifNum > <vpi> <vci>
Syntax Description
ifNum
The logical port number. The range for AXSM is 1–60.
vpi
Virtual path identifier. On the AXSM, the range is 1–255.
vci
Virtual connection identifier. On t he AXSM, the range is 32–65535 for a VCC. For
a VPC, the only vci is 0.
Related Commands
dncon
Attributes
Log: log
State: active
Privilege: GROUP1
Cisco MGX 8850 Routing Switch Command Reference
9-168
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 9
Troubleshooting Commands
upln
upln
Up Line
Activates a line on the current card. After you have activated the line, use cnfln to configure the line
characteristics such as the type of line (for SONET types, T3, or E3), line signaling, and so on.
Note
See description of cnfcdsct for important planning considerations before you use upln.
Cards on Which This Command Runs
AXSM
Syntax
upln <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
dspln, dsplns, cnfln, dnln
Attributes
Log: log
State: active
Privilege: GROUP1
Example
Activate line 1 in bay 1.
MGX8850.1.AXSM.a > upln 1.1
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
9-169
Chapter 9
Troubleshooting Commands
upport
upport
Up Port
The upport command returns a logical port to the up state (or ups the port) so the port can again carry
traffic. The upport command concludes possible re-configuration or troubleshooting steps. Before you
execute upport, you must have downed the port by executing dnport. Throughout the sequence of
downing and upping a port, the configuration for the port remains intact whether the logical port is a UNI
or an NNI.
The routes for connections vary by interface type:
•
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.
Cards on Which This Command Runs
AXSM
Syntax
upport <ifNum>
Syntax Description
ifNum
A logical port (interface) number. Only one logical port is allowed if the line operates
as a UNI or NNI. For the virtual network to network interface (VNNI), multiple ports
can exist on a line. For AXSM, the range 1–60.
Use dspports or dspport as needed to determine which port to bring up.
Related Commands
dspport, dspports, dnport
Attributes
Log: log
State: active
Privilege: GROUP1
Example
Restore port 1 on the current card to operation.
MGX8850.1.AXSM.a > upport 1
Cisco MGX 8850 Routing Switch Command Reference
9-170
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising