MGX 8850 and MGX 8950 Command Reference, Release 2.1
Troubleshooting Commands
Downloads: This chapterpdf (PDF - 1.64MB) The complete bookPDF (PDF - 7.36MB) | Feedback

Troubleshooting Commands

Table Of Contents

Troubleshooting Commands

Position-Dependent and Keyword-Driven Parameters

Command Entry

Identifying the AXSM Models

Identifying Physical and Logical Elements

AXSM Format

PNNI Format

abortofflinediag

addchanloop

addlnloop

clradjlnalmcnt

clrallcnf

clralmcnt

clrbecnt

clrcdcnt

clrchancnt

clrchancnts

clrdiagerr

clrdiagstat

clrerr

clrerrhist

clrilmicnt

clrlncnt

clrlog

clrportcnt

clrportcnts

clrxbaralm

clrxbarerrcnt

cnfalm

cnfautolndiag

cnfbert

cnfconsegep

cnfdiag

cnfdiagall

cnfpnportloscallrel

cnfxbaradmin

cnfxbarerrthresh

cnfxbarmgmt

conntrace

copycons

core

dclk

dbgcon

delchanloop

dellnloop

dncon

dnln

dnport

dspadjlnalm

dspadjlnalmcnt

dspalm

dspalmcnf

dspalmcnt

dspalms

dspautolndiag

dspbecnt

dspbert

dspbertstats

dspcd

dspcdalms

dspcdbucketcnt

dspcdcnt

dspcderrs

dspcds

dspcdstatus

dspchancnt

dspchanloop

dspchantests

dspclkalms

dspclksrcs

dspcon

dspconalmcnts

dspconalms

dspconinfo

dspconload

dspcons

dspcons-dbg

dspcontrollers

dspdevalms

dspdeverr

dspdeverrhist

dspdiagcnf

dspdiagerr

dspdiagstat

dspdiagstatus

dspegrbucketcnt

dspenvalms

dsperr

dsperrhist

dspilmicnt

dspln

dsplncnt

dsplnpmbucketcnt

dsplns

dsplog

dsplogs

dspndalms

dspingbucketcnt

dsplnbucketcnt

dsppnportloscallrel

dspportbucketcnt

dspportcnt

dspprfhist

dspswalms

dsptrapmgr

dspxbar

dspxbarerrthresh

dspxbarmgmt

dspxbarplanealms

dspxbarslotbwalms

dspxbarstatus

dumpconfigs

dumptrace

dumpversions

insbiterror

offdiagstat

ondiagstat

pathtraceie

pathtracenode

pathtraceport

resetcd

resetsys

stackdump

startbert

stopbert

switchcc

tstconseg

tstdelay

upcon

upln

upport


Troubleshooting Commands


This chapter describes commands that directly or indirectly facilitate troubleshooting. They include commands for viewing and clearing alarms and statistics. The chapter begins descriptions of the CLI, various elements of the AXSM, and the PNNI port identifier.

Position-Dependent and Keyword-Driven Parameters

A command can include parameters that are keyword-driven or position-dependent.

For position-dependent parameters, you must type parameters in the order they appear in the syntax description or on-line help. To create a logical port, for example, the position-dependent syntax is:

addport <ifNum> <bay.line> <guaranteedRate> <maxrate> <sctID> <ifType> [vpi]

For a keyword-driven parameter, a keyword must precede the value. The keyword is preceded by a dash and followed by the parameter (-timeout <secs>, for example). The order you enter keyword-driven parameters does not matter—although any preceding or succeeding, position-dependent parameters must appear as they do in the command syntax description.

In the following syntax example, the command is to delete more than one connection at a time. The mandatory, position-dependent connection identifier consist of a logical port (ifNum) and the VPI and VCI of the first connection to delete. After the connection identifier, the line shows two optional, keyword-driven parameters. These keyword-driven parameters let you enter the number of connections to delete and specify verbose mode:

delcons <ifNum> <vpi> <vci> [-num <num.conns to del>] [-verbose < 1 | 0 >]

Command Entry

When you enter a command with the current version of the product, you must type all intended arguments before you press the Return key or Enter key.

If you press the Return key or Enter key with incorrect parameters or no parameters (if the command requires parameters), a message displays the syntax and parameter ranges. The returned message may also suggest what the problem is. For example, the message may warn of too few parameters. No error messages or warnings appear until you complete the command.

Identifying the AXSM Models

The model number of an AXSM identifies the line speed, line count, and number of bays (see Table 9-1.) Note that the number of lines applies to an individual back card, so the total number of lines supported by the front card equals the highest line number times the number of bays. The OC-48 card AXSM-1-2488 has the lowest number of lines—one. The highest number of lines exist on the AXSM-16-155 and AXSM-16-T3E3—16, as the name indicates.

An MGX 8850 or MGX 8950 node uses the concept of a bay. The bay refers to the upper or lower location of a single-height card. (The switch has a double-height card cage, so a single-height back card necessarily occupies either an upper or lower position.)

The T3/E3, OC-3, and OC-12 versions of the AXSM can have two back cards, one in bay 1 (upper location of the back slot) and the second in bay 2 (lower slot). The MGX-AXSM-1-2488 (OC-48 AXSM) can have a back card in bay 1 only. For further descriptions and illustrations of the card sets, refer to Cisco MGX 8850 Routing Switch Hardware Installation, Release 2.1 or Cisco MGX 8950 Routing Switch Hardware Installation, Release 1.

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

AXSM-16-T3E3-E

T3, E3

1-8

1-2


Identifying Physical and Logical Elements

The Private Network-to-Network Interface (PNNI) control protocol and the AXSM use different formats to identify the same elements. This section describes the format of these elements in the PNNI and AXSM contexts and how they correspond to each other. When you configure or view items on the CLIs of different cards, you often need to specify it in PNNI as well as the AXSM. For example, when you configure a PNNI port on the CLI of the PXM45, you also need to configure a port on the CLI of the AXSM. Furthermore, when you display a connection on the AXSM, you identify that same connection using a different format on the PXM45 CLI. For specific examples of these parallel actions, see the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1.


Note Apart from the way PNNI and the lower levels of logic identify the same element, the issue of configuration sequence needs explanation. When you configure logical ports—as just one example—you must complete certain tasks on the AXSM CLI before and after related PNNI tasks. This manual describes prerequisites for certain commands, but refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1, for more details of this sequence.


AXSM Format

The AXSM items that you identify for addressing purposes are:

Slot

Bay

Line

Logical port

A logical port on an AXSM (and its CLI) always uses the label ifNum. For a UNI and NNI interface, a one-to-one correspondence exists between a logical port and a physical line. For virtual trunks, you can configure multiple ports for a line.

The range of logical ports (ifNum) is 1-60 for the AXSM and 1-32 for the AXSM-E regardless of whether the interface type is UNI, NNI, or VNNI (virtual network-to-network interface).

PNNI Format

The PNNI controller requires the following format to identify a physical port:

[shelf.]slot:subslot.port:subport

The PNNI physical port identifier (physical port ID) consists of a series of mandatory elements. Note the period or colon associated with each element inside the square brackets. The elements of the physical port ID are as follows:

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), these numbers do not directly correspond to each other.

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)


As the table shows, a port from the PNNI side is a line on the AXSM, and a subport from the PNNI side is a logical interface (or logical port) on an AXSM. An example of a PNNI physical port identifier is 1:2.1:1. This portid corresponds to an AXSM, with the following particulars:

Slot 1

Bay 2

Line 1

Logical interface 1 (or logical port 1)

abortofflinediag

Abort Offline Diagnostics

Aborts the currently running offline diagnostics.


Note See the cnfdiag command for a detailed description of the 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

State: active, standby

Privilege: SERVICE_GP



Caution If offline diagnostic is running on the AXSM, the AXSM must be in the standby state.

Example

abortofflinediag 1

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 very intrusive. The test requires a testing device to generate a cell stream. The parameters for such a stream are the number of cells transmitted through the loop, the cell transfer rate, and so on. (To test connection integrity in a non-destructive way while the connection carries user data, use tstdelay on the ingress or tstconseg on the egress. These commands generate one OAM cell for each command execution.)

A connection can have only one loopback at a time. Therefore, you cannot add a loopback for both directions at the same time. The loopback remains until you delete it by executing delchanloop. To see the presence of connection loopbacks on a per-port basis, use dspchanloop.

The addchanloop command lets you specify the direction of cell flow within the loop (see Figure 9-1):

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

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

addchanloop <ifNumber> <vpi> <vci> <loopback mode>

Syntax Description

ifNumber

The logical port number. The ranges for AXSM are as follows:

AXSM: 1-60

AXSM-E: 1-32

vpi

The VPI of the connection. The range is 0-4095.

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: yes

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      rVPI      rVCI
4     igrLpbk       1        50         0        35 

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-E

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

-sonet

Specifies a DS3 line (E3 or T3) or a SONET line (OC-3c, OC-12c, OC-48c).

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


AXSM-E Syntax

addlnloop < -ds3 | -e3 | -sonet | -ds1 | -e1 bay.line> <-lpb loopback type>

AXSM-E Syntax Description

-ds3
-e3
-sonet
-ds1
-e1

Specifies a DS3, E3, T3 , SONET (OC-3c, OC-12c, OC-48c), DS1, or E1 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.

-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: yes

State: active

Privilege: GROUP1


Example

Adding a DS3 line in a loopback state.

MGX8850.1.11.AXSME.a > addlnloop -ds3 1.1 -lpb 2

clradjlnalmcnt

Clear Adjacent Card Alarm Count

The clradjlnalmcnt command lets you clear the statistical alarms and alarm counters for the adjacent back card in an automatic protection system (APS) configuration.


Note The clradjlnalmcnt command works for only inter-card APS.


Cards on Which This Command Runs

AXSM-E

Syntax

clradjlnalmcnt <bay.line>

Syntax Description

bay.line

Identifies the bay (1 or 2) and the number of the line. The line number can be 1 to the highest numbered line on the back card.


Related Commands

dspadjlnalm, dspadjlnalmcnt

Attributes

Log: yes

State: active

Privilege: SUPER_GP


Example

On the card in slot 3, clear the alarm count for the card adjacent to bay 1, line 1. Check the alarm status for the same adjacent bay and line.

MGX8850.3.AXSME.a > clradjlnalmcnt 1.1
MGX8850.3.AXSME.a > dspadjlnalm 1.1
Line Number              : 1.1
 Section Alarm State     : Clear
 Line Alarm State        : Clear
 Path Alarm State        : Clear
 Section Stat Alarm State: Clear
 Line Stat Alarm State   : Clear
 Path Stat Alarm State   : Clear
 LOCD Alarm State        : Clear

clrallcnf

Clear All Configurations

Clear all configuration for all the cards in the node. After you enter the command, the system prompts you to confirm the action.


Caution Be absolutely sure you need to use this command because it clears all configuration files on the PXM45. After clrallcnf, you must reconfigure the switch The clrcnf command clears fewer files.

Cards on Which This Command Runs

PXM45

Syntax

clrallcnf

Related Commands

restoreallcnf, clrcnf

Attributes

Log: yes

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)?

clralmcnt

Clear Alarm Counters

Clear all the alarm counters and statistics on the specified line on the current card. All counters are reset to 0. All statistical alarms that are displayed by dspalms and dspalmcnt are cleared. The system does not display a response unless it detects a syntax error.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

clralmcnt <bay.line>

Syntax Description

bay.line

Identifies the bay (1 or 2) and the number of the line. The line number can be 1 to the highest numbered line on the back card.


Related Commands

dspalmcnt

Attributes

Log: yes

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

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: SERVICE_GP


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: yes

State: active

Privilege: SERVICE_GP


clrchancnt

Clear Channel Counters

Clear all counters for ATM cells on a connection (channel). The command applies to an SVC or an SPVC. For a list of displayed counters, see the example of dspchancnt. Once you execute clrchancnt, the previous counter contents are unrecoverable.


Note This command does not apply to OC-48 cards.


Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

clrchancnt <ifNum> <vpi> <vci>

Syntax Description

ifNum

The logical port number. The range for AXSM is 1-60. The range for AXSM-E is 1-32.

vpi

The VPI has the range 0-255 for a UNI or 0-4095 for a UNI or VNNI.

vci

The VCI in the range 1-65535.


Related Commands

dspchancnt

Attributes

Log: yes

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

clrchancnts

Clear Channel Counters

Clears the statistics counters on all connections.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

clrchancnts

Syntax Description

No parameters.


Related Commands

dspchancnt, clrchancnt

Attributes

Log: yes

State: active

Privilege: SUPER_GP


Example

SunnyVale.13.AXSME.a > clrchancnts

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

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.


Cards on Which This Command Runs

PXM45

Syntax

clrdiagstat <slot>

Syntax Description

slot

The slot of the card for which to clear the diagnostics statistics.


Related Commands

dspdiagstat

Attributes

Log: no

State: active or standby

Privilege: SERVICE_GP


Example

clrdiagstat 7

clrerr

Clear Error

Clear all error log files. After you execute clrerr, the information is unrecoverable. The cleared information consists of system-level or internal errors and so applies more to developers and individuals capable of internal troubleshooting. To see the information that clrerr removes, see dsperr.

After you enter clrerr, the system prompts you to confirm that you want to clear all error log files.

Cards on Which This Command Runs

PXM45

Syntax

clrerr <-s1 slot>

Syntax Description

-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)? 

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.

clrilmicnt

Clear ILMI Counters

Clears the ILMI statistics for a partition and logical port on a service module.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

clrilmicnt <ifNum> <partId>

Syntax Description

ifNum

The ranges for logical interface (or AXSM port) number are as follows:

AXSM: 1-60

AXSM-E: 1-32

partId

The ranges for partition identifier are as follows:

AXSM: 1-5

AXSM-E: 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

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, AXSM-E

Syntax

clrlncnt <bay.line>

Syntax Description

bay.line

Identifies the bay (1 or 2) and the number of the line. The range for line can be 1 to the highest numbered line on the back card.


Related Commands

dsplncnt

Attributes

Log: yes

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

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: yes

State: active, standby

Privilege: SUPER_GP


Example

Clear all event log files on the PXM45 card.

wilco.7.PXM.a > clrlog

clrportcnt

Clear Port Counter

Clear counter values on a specific logical port.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

clrportcnt <ifNum>

Syntax Description

ifNum

The logical port number. The range for AXSM is 1-60. The range for AXSM-E is 1-32.


Related Commands

clrportcnts, dspportcnt

Attributes

Log: yes

State: active

Privilege: SUPER_GP


Example

Display the counters for logical interface 1, then clear the counters on port 1. Re-check the port counters.

M8850_NY.1.AXSM.a > dspportcnt 1

 Cleared at      : 10/26/2001 00:00:44 
 Current time    : 12/02/2001 21:44:41 
 Elapsed time    : 37 day(s) 21:43:21 [hh:mm:ss] 

                          Total             Running Avg (cps)   Peak
--------------------------------------------------------------------
Arrival CLP0    Ing: 0000000000000007326214            2           21
Arrival CLP1    Ing: 0000000000000000000000            0            0
Ar CLP0 discard Ing: 0000000000000000000056            0            3
Ar CLP1 discard Ing: 0000000000000000000000            0            0
Departure CLP0  Ing: 0000000000000007326211            2           21
Departure CLP1  Ing: 0000000000000000000000            0            0

Arrival CLP0    Egr: 0000000000000007326217            2           21
Arrival CLP1    Egr: 0000000000000000000000            0            0
Ar CLP0 discard Egr: 0000000000000000000000            0            0
Ar CLP1 discard Egr: 0000000000000000000000            0            0
Departure CLP0  Egr: 0000000000000007326218            2           21
Departure CLP1  Egr: 0000000000000000000000            0            0

M8850_NY.1.AXSM.a > clrportcnt 1

M8850_NY.1.AXSM.a > dspportcnt 1

 Cleared at      : 12/02/2001 21:44:56 
 Current time    : 12/02/2001 21:45:19 
 Elapsed time    : 0 day(s) 0:0:22 [hh:mm:ss] 

                          Total             Running Avg (cps)   Peak
--------------------------------------------------------------------
Arrival CLP0    Ing: 0000000000000000000054            2            2
Arrival CLP1    Ing: 0000000000000000000000            0            0
Ar CLP0 discard Ing: 0000000000000000000000            0            0
Ar CLP1 discard Ing: 0000000000000000000000            0            0
Departure CLP0  Ing: 0000000000000000000054            2            2
Departure CLP1  Ing: 0000000000000000000000            0            0

Arrival CLP0    Egr: 0000000000000000000051            2            2
Arrival CLP1    Egr: 0000000000000000000000            0            0
Ar CLP0 discard Egr: 0000000000000000000000            0            0
Ar CLP1 discard Egr: 0000000000000000000000            0            0
Departure CLP0  Egr: 0000000000000000000051            2            2
Departure CLP1  Egr: 0000000000000000000000            0            0

M8850_NY.1.AXSM.a > 

clrportcnts

Clear Port Counters

Clear all port counters on the current AXSM. The system does not return a message unless a syntax error occurs (such as a spurious character following the command on the CLI).

Cards on Which This Command Runs

AXSM

Syntax

clrportcnts

Syntax Description

This command takes no parameters.

Related Commands

clrportcnt, dspportcnt

Attributes

Log: yes

State: active

Privilege: SUPER_GP


Example

Display the counters for logical interface 2, then clear all the port counters on the current AXSM. Again display the counters for logical interface 2.

M8850_NY.1.AXSM.a > dspportcnt 2

 Cleared at      : 10/26/2001 00:00:44 
 Current time    : 12/02/2001 21:46:42 
 Elapsed time    : 37 day(s) 21:45:22 [hh:mm:ss] 

                          Total             Running Avg (cps)   Peak
--------------------------------------------------------------------
Arrival CLP0    Ing: 0000000000000000655030            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: 0000000000000000655030            0            0
Departure CLP1  Ing: 0000000000000000000000            0            0

Arrival CLP0    Egr: 0000000000000000655030            0            0
Arrival CLP1    Egr: 0000000000000000000000            0            0
Ar CLP0 discard Egr: 0000000000000000000000            0            0
Ar CLP1 discard Egr: 0000000000000000000000            0            0
Departure CLP0  Egr: 0000000000000000655030            0            0
Departure CLP1  Egr: 0000000000000000000000            0            0

M8850_NY.1.AXSM.a > clrportcnts

M8850_NY.1.AXSM.a > dspportcnt 2

 Cleared at      : 12/02/2001 21:46:57 
 Current time    : 12/02/2001 21:47:02 
 Elapsed time    : 0 day(s) 0:0:5 [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    Egr: 0000000000000000000000            0            0
Arrival CLP1    Egr: 0000000000000000000000            0            0
Ar CLP0 discard Egr: 0000000000000000000000            0            0
Ar CLP1 discard Egr: 0000000000000000000000            0            0
Departure CLP0  Egr: 0000000000000000000000            0            0
Departure CLP1  Egr: 0000000000000000000000            0            0

M8850_NY.1.AXSM.a > 

clrxbaralm

Clear Crossbar Alarm—clear the crossbar alarms.

The clrxbaralm command clears the alarms for either a specific switch plane or for all the switch planes on the switching card. In an MGX 8850 node, the slot is the physical slot number of the PXM45. In an MGX 8950 node, the slot is the number of the slot where an XM60 resides. To see the alarms that clrxbaralm clears, use dspdevalms or dspswalms.

Cards on Which This Command Runs

PXM45

Syntax

clrxbaralm <slot> <plane>

clrxbaralm *

Syntax Description

*

Enter an asterisk to clear all crossbar alarms on the active PXM45 or the XM60s.

slot

The slot number of the crossbar planes. The possible slot numbers in an MGX 8850 switch is 7-8. In an MGX 8950 switch, the possible slot numbers are 9, 10, 25, and 26.

plane

In n MGX 8850 switch, the range of plane numbers is 0-2. In an MGX 8950 switch, the range of plane numbers is 0-3.


Related Commands

dspdevalms, dspswalms

Attributes

Log: yes

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 dspdevalms.

pop20two.7.PXM.a > clrxbaralm 7 0

clrxbarerrcnt

Clear Crossbar Error Count—clear the counters for crossbar errors.

The clrxbarerrcnt command clears the errors for either a specific switch plane or all the switch planes on the active switching card. In an MGX 8850 node, the slot is the physical slot number of the PXM45. In an MGX 8950 node, the slot is the number of the slot where an XM60 resides. To see the errors that clrxbarerrcnt clears, execute dspdeverrhist.

Cards on Which This Command Runs

PXM45

Syntax

clrxbarerrcnt < * | [ slot plane ]>

Syntax Description

*

Enter an asterisk to clear all crossbar errors.

slot

The slot number of the crossbar planes. On an MGX 8850 switch, the slot number is 7 or 8. On an MGX 8950 switch, the slot number is 9, 10, 25, or 26.

plane

On an MGX 8850 switch, the range for plane numbers is 0-2. On an MGX 8950 switch, the range for plane numbers is 0-3.


Related Commands

dspdeverrhist, cnfxbarerrthresh, dspxbarerrthresh, dspswalms

Attributes

Log: yes

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 dspdeverrhist.

M8850_NY.7.PXM.a > clrxbarerrcnt 7 0
M8850_NY.7.PXM.a > 

Clear all crossbar alarms on the current PXM45.

M8850_NY.7.PXM.a > clrxbarerrcnt *
XBAR errors of slot 7 are cleared

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, AXSM-E

Syntax

The required parameters are the line type the line identifier in the format bay.line, and the severity of the alarm (minor or major). All other parameters are optional and must be preceded by the keyword that identifies the type of parameter.

Generic Syntax Description

The generic syntax is.

cnfalm <line type> <bay.line> <alarm severity> <thresholds>

The meaning of the generic syntax appears in the following list. Refer to subsequent lists for the descriptions of alarm severities and thresholds for each line type.

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 and the line. The ranges are as follows:

Bay: 1-2

Line: 1 to the highest numbered line on the back card

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.

-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.

-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.


Thresholds for E3

-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.

-sefs15 SEFS15min

Severely errored frame seconds during a 15-minute period.

-efs24 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.

-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: yes

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 

cnfautolndiag

Configure Auto Line Diagnostics

Enables or disables auto line diagnostic on the card.

Cards on Which This Command Runs

AXSM-E

Syntax

cnfautolndiag <enable | disable>

Syntax Description

enable or
disable

A numeric value indicates enable or disable:

1 = enable

2 = disable


Attributes

Log: yes

State: active

Privilege: GROUP1


Example

MGX8850.10.AXSME.a > cnfautolndiag 1

cnfbert

Configure Bit Error Rate Test

Configures the bit error rate test patterns for the given line. The new configuration will not take effect if a BERT test is already running on the given line. It will, however, take effect when the currently running BERT test is stopped and started again.

Cards on Which This Command Runs

AXSM-E

Syntax

cnfbert -ln <bay.line> -tp <test pattern> -tpi <transmit pattern inverse>
-rpi <receive pattern inverse> -eir <error insertion rate 1 - 8 >

Syntax Description

bay

Bay number: 1 or 2

line

Line number:

For OC12: 1

For OC3: 1-4

T3, E3: 1-8

test pattern

Patterns range from 1-32.

1 = allZeros: All Zeroes(Continuous spaces).

2 = allOnes: All Ones(Continuous Marks).

3 = altOneZero: Alternate one/zero pattern(..1010..).

4 = doubleAltOnesZeros: Double alternate one/zero(..1100..).

5 = oneIn4: Standard loop up remote code.

6 = oneIn8: An eight bit pattern which contains single one.

7 = oneIn16: N repetitive pattern, 1 in 16.

8 = threeIn24: A 24 bit pattern which contains 3 ones.

9 = inbandLoopup: D4/SF Loopback activate.

10 = inbandLoopdown: D4/SF Loopback deactivate.

11 = twoE3MinusOne: This is 23-1 (7 bits in length) pattern.

12 = twoE4MinusOne: This is 24-1 (15 bits in length) pattern.

13 = twoE5MinusOne: This is 25-1 (31 bits in length) pattern.

14 = twoE6MinusOne: This is 26-1 (63 bits in length) pattern.

15 = twoE7MinusOne: This is 27-1 (127 bits in length) pattern.

16 = twoE7MinusOneFT1Loopup: 27-1 Fractional T1 Loop Back Activate.

18 = twoE9MinusOne: 29-1(511 bits in length). It has the maximum of 8(non-inverted) sequential zeros and 9 sequential ones.

19 = twoE10MinusOne: This is the 210-1(1023 bits in length).

20 = twoE11MinusOne: 211-1(2047 bits in length). It has the maximum of 15(inverted) sequential zeros.

21 = twoE15MinusOne: 215-1(32767 bit length). It has the maximum of 15(inverted) sequential zeros.

22 = twoE17MinusOne: 217-1(131071 bits in length).

23 = twoE18MinusOne: 218-1(262144 bits in length).

24 = twoE20MinusOne: 220-1(1048575 bits in length). It has the maximum of 19(non-inverted) sequential zeros.

25 = twoE20MinusOneQRSS: 220-1(1048575 bits). This is the pattern with Zero suppression(Quasi Random Signal Source).

26 = twoE21MinusOne: 221-1(2097151 bit length).

27 = twoE22MinusOne: 222-1(4194303 bit length).

28 = twoE23MinusOne: 223-1(8388607 bit length).Highest stress pseudorandom pattern, with a maximum of 23(inverted) sequential zeros and 23 sequential ones.

 

29 = twoE25MinusOne: 221-1(33554431 bit length).

30 = twoE28MinusOne: 228-1( 268435455 bit length).

31 = twoE29MinusOne: Highest stress pseudo random pattern, with a maximum of 29(inverted) sequential zeros.

32 = twoE31MinusOne: Maximum 31 sequential zeros.

transmit pattern inverse

Controls inversion of the transmit BERT pattern:

1: Not inverted

2: Inverted

receive pattern inverse

Controls inversion of the received BERT pattern:

1: Not inverted

2: Inverted

error insertion rate

Injects errors into the transmitted pattern. Type a number in the range 1-8:

1 = noError(1): No bit errors are inserted.

2 = oneInTen: Insert bit errors at the rate of 1 bit error per 10 bits(10-1) transmitted.

3 = oneInHundred: Insert bit errors at the rate of 1 bit error per 100 bits(10-2) transmitted.

4 = oneInThousand: Insert bit errors at the rate of 1 bit error per 1000 bits(10-3) transmitted.

5 = oneIn10Thousand: Insert bit errors at the rate of 1 bit error per 10000(10-4) bits transmitted.

6 = oneInHundredThousand: Insert bit errors at the rate of 1 bit error per 100000 bits(10-5) transmitted.

7 = oneInMillion: Insert bit errors at the rate of 1 bit error per 1000000 bits(10-6) transmitted.

8 = oneInTenMillion: Insert bit errors at the rate of 1 bit error per 10,000,000(10-7)bits transmitted.


Related Commands

stopbert, startbert

Attributes

Log: yes

State: active

Privilege: GROUP1


cnfconsegep

Configure Connection Segment Endpoint

The cnfconsegep command lets you configure a segment endpoint for an SVC or SVP on a via node. Its purpose is part of a troubleshooting scheme. After you create an endpoint, you can use the tstdelay command and specify the endpoint created with the cnfconsegep command. The Example section shows how to use tstdelay and conntrace in conjunction with the cnfconsegep command.

You can specify more than one endpoint as long as each one complies with the requirements of the cnfconsegep command, as follows:

Before using the cnfconsegep command, be sure continuity checking is disabled. If you leave continuity checking on, a continuity failure occurs for the connection. Use the dspcon command to see if is enabled. To disable it, use cnfcon and include the optional parameter sequence -cc

When both the VPI and the VCI are present, the segment endpoint is an F5 flow endpoint (for VCCs). When the optional VCI is not present, the segment endpoint is an F4 flow endpoint (for VPCs). Use the cnfconsegep command only for established calls.

The endpoints must be part of an SVC or SVP. For an SPVC, you can specify only the SVC endpoints within the SPVC. The controller determines if either side (from its perspective) is an SPVC or SPVP and rejects the command if either endpoint belongs to an SPVC or SPVP. For an SPVC, you can use the cnfconsegep command if one or more via nodes exist in the connection path. (See Figure 9-2.)

In Figure 9-2, an SPVC has endpoints at UNI1 and UNI2. You can use cnfconsegep to configure segment endpoints at NNI2, NNI3, NNI4, and NNI5. You cannot configure segment endpoints at UNI1, UNI2, NNI1, and NNI6. After you configure any of these endpoints, you could verify the electrical integrity by using the tstdelay command from UNI1 or UNI2 to each of NNI2, NNI3, NNI4, or NNI5. After you finish troubleshooting, remove all segment endpoints by using delconsegep for each endpoint.

Figure 9-2 Configurable Endpoints for the cnfconsegep Command

Command(s) on Which Command Executes

PXM45

Syntax

cnfconsegep <portid> <vpi> [vci]

Syntax Description

portid

Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.

vpi

VPI of the connection.

vci

VCI of the connection.


Related Commands

cnfoamsegep, dspoamsegep, delconsegep, dspconsegep

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

This example shows how the cnfconsegep, conntrace, and tstdelay commands can work to show a point of failure. In Figure 9-3, the following are the NNIs:

9:1.1:1 on "tokyo"

9:1.1:1 on "fiorano"

9:1.2:2 on "tokyo"

9:1.2:2 on "auckland"

9:1.3:3 on "auckland"

9:1.1:3 on "fiorano"

In this network, the following have also been established:

UNI port 9:1.8:8 on "tokyo"

UNI port 9:1.8:8 on "auckland"

A connection between these two ports has a VPI/VCI of 66/66.

Figure 9-3 Sample Network for Testing Segment Integrity

Check the connection path by using the conntrace command. As expected, it traverses the direct link (PhysPortId=9:1.2:2), as follows:

tokyo.8.PXM.a > conntrace 9:1.8:8 -vpi 66 -vci 66

Result:SUCCESS  Reason: N/
InterfaceId:9:1.8:8
Originating Interface VPI : 66
Originating Interface VCI : 66
Originating Interface Call Ref : 1
    NodeId                                          EgressPort   VPI    VCI  CallRef
  56:160:47.00918100000000107b65f448.00107b65f448.01 17373186        0     35        1 
PhysPortId=9:1.2:2
  56:160:47.00918100000000309409f3bb.00309409f3bb.01      0
  Terminating Interface VPI : 66
  Terminating Interface VCI : 66
  Terminating Interface Call Ref : 1

To continue this example, the following tasks are performed:

1. To force the connection to take the longer route (using node ""fiorano""), use the dnpnport command to administratively down PNNI port 9:1.2:2.

2. Repeat the connection trace for 66/66 on UNI port 9:1.8:8 on node "tokyo." The physical port ID now is 9:1.1:1. Note that 66/66 mapped to 0/36 on 9:1.1:1.

3. Use the uppnport command to bring the port back into service.

tokyo.8.PXM.a > dnpnport 9:1.2:2

tokyo.8.PXM.a > conntrace 9:1.8:8 -vpi 66 -vci 66
 
  Result:SUCCESS  Reason: N/A
  InterfaceId:9:1.8:8
  Originating Interface VPI : 66
  Originating Interface VCI : 66
  Originating Interface Call Ref : 2
    NodeId                                          EgressPort   VPI    VCI  CallRef
  56:160:47.00918100000000107b65f448.00107b65f448.01 17373185        0     36        2 
PhysPortId=9:1.1:1
  56:160:47.00918100000000309409f3b8.00309409f3b8.01 17373187        0     41        1 
PhysPortId=9:1.3:3
  56:160:47.00918100000000309409f3bb.00309409f3bb.01      0
  Terminating Interface VPI : 66
  Terminating Interface VCI : 66
  Terminating Interface Call Ref : 2
 
tokyo.8.PXM.a > uppnport 9:1.2:2

Configure a connection segment endpoint by using the following values on node "fiorano":

The PNNI port ID is 9:1.1:1.

The VPI/VCI is 0/35—the mapped value observed in the last display of the conntrace command.

fiorano.7.PXM.a > cnfconsegep 9:1.1:1 0 36
PortId: 0.9:1.1:1      Vpi:      0     Vci:     36 

The connection is configured as a segment end point.

cnfdiag

Configure Diagnostics

Enables the online or offline diagnostics. The cnfdiag command also configures the time settings for the start time and coverage for running the offline diagnostics. When you enter cnfdiag with no parameters, it displays the current configuration and status of the diagnostics.

The cnfdiagall command is the same as cnfdiag except that it configures all slots on the card at once.


Note Do not remove the active PXM45 card while the offline diagnostic is running on the redundant PXM45. If you remove it, the redundant PXM45 reboots but will not be able to become active unless its hard disk drive was previously synchronized to the hard disk on the previously active PXM45.


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

Standby State

When you enable online diagnostics on a standby AXSM card, the following tests run:

Framer loopback test on QE48, UDP, ATLAS, and Framer paths (AXSM-E only)

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. Processor Subsystem Test

Flash EPROM

SDRAM

SCC

PCI Bridge

2. Component Level Test

PIO

FPGA

LEDs

Fan / Power Supply

BRAM / RTC

SEEPROM / NovRAM Checksum Test

3. 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

4. UI S3/S4 Back card test

NovRAM Checksum Test

5. 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

Related Commands

cnfdiagall, dspdiagcnf

Attributes

Log: no log

State: active

Privilege: SERVICE_GP


Example

cnfdiag 7 enable disable light 22:30 -M-W-F-

cnfdiagall

Configure Diagnostics All

This command enables and configures online or offline diagnostics for all card slots. (This command is the same as cnfdiag except that it effects all slots instead of just one.)

When you enter this command with no parameters, it displays the current configuration and status of the diagnostics.


Note See the cnfdiag command for a detailed description of MGX 8850 diagnostics.



Note Do not remove the active PXM45 card while the offline diagnostic is running on the redundant PXM45. If you remove it, the redundant PXM45 reboots but will not be able to become active unless its hard disk drive was previously synchronized to the hard disk on the previously active PXM45.


Cards on Which This Command Runs

PXM45

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.

light = 5 minutes or less

medium = 30 minutes or less

full = unlimited

offStart

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


Related Commands

cnfdiag, dspdiagcnf

Attributes

Log: no log

State: active, standby

Privilege: SERVICE_GP


Example

cnfdiagall enable disable light 22:30 -M-W-F-

cnfpnportloscallrel

Configure PNNI Port Loss of Signal Call Release

The cnfpnportloscallrel command lets you shut off the standard delay for rerouting calls on a port when the system detects loss of signal (LOS) on a port.

When the system detects LOS on an NNI link, the switch does not immediately tear down the calls on the link—in case the break is momentary. By default, the system waits for the SSCOP "no-response" and T309 timers to time out before it releases calls on the broken link. The default values for these timers are 30 seconds and 10 seconds, respectively. The system-level assumption (and therefore the default for cnfpnportloscallrel) is to retain all the calls for a temporary loss of connectivity, but this can also have the effect of delaying the rerouting of connections. The cnfpnportloscallrel command lets you direct the system to reroute calls without delay on a particular port.

Cards on Which This Command Runs

PXM45

Syntax

cnfpnportloscallrel <portid> <yes | no>

Syntax Description

portid

Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.

yes | no

Specifies whether immediate call release is enabled upon LOS. To enable this feature—to remove the standard reroute delay—type "yes."

Default: no


Related Commands

dsppnportloscallrel

Attributes

Log: yes

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

cnfxbaradmin

Configure Crossbar Administration—turn a switch plane on or off.

The cnfxbaradmin command lets you turn off the switch planes on a switch card. The purpose for turning off switch planes is a graceful removal of the standby PXM45 in an MGX 8850 switch or an XM60 in an MGX 8950 switch. The circumstance for removing the card is a bad switch plane.

Graceful removal reduces lost traffic due to card removal. Removing a switching card normally causes very little cell loss, and using the cnfxbaradmin command further reduces the loss. The actual impact of the command is relatively small. (For most plane-centric failures, the switching ASIC can continue to switch cells but at a lower rate.)


Note If you change your mind about removing a card after turning off switch planes, you can turn them back on with the appropriate command parameter.


Cards on Which This Command Runs

PXM45

Syntax

cnfxbaradmin <xbarSlot> <adminStatus>

Syntax Description

xbarSlot

Identifies the slot where the switch planes reside. In an MGX 8850 switch, the range for xbarSlot is 7-8. In an MGX 8950 switch, the range for xbarSlot is 9-10 and 25-26.

adminStatus

Specifies whether the switch planes are on or off. Type the entire word "on" or "off."

Default: on


Related Commands

cnfxbarerrthresh, cnfxbarmgmt, dspxbar, dspdevalms, dspdeverrhist, dspxbarstatus

Attributes

Log: yes

State: active

Privilege: SUPER_GP


Examples

Do the following:

1. Turn off the switch fabric for the PXM45 in slot 8—the standby card.

2. Use the dspxbarstatus command for this slot but check only one switch plane for activity. Note that the available bandwidth is 0.

3. Turn on the switch fabric for slot 8.

4. Check the status by using the dspxbarstatus command and again specifying switch plane 0.

M8850_NY.7.PXM.a > cnfxbaradmin 8 off
Shut-down of switch could be service affecting!
cnfxbaradmin: Do you want to proceed (Yes/No)? y



M8850_NY.7.PXM.a > dspxbarstatus 8 0
M8850_NY                         System Rev: 02.01   Nov. 28, 2001 15:42:22 PST
MGX8850                                              Node Alarm: CRITICAL
Switch CD No: 8          Switch ASIC No: 0
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
Misc Error Bitmap: 0x0
Fabric Available Bandwidth: 3000 Mbps
Switch Card Available Bandwidth: 0 Mbps
Highest Bandwidth Needed: 2488 Mbps

M8850_NY.7.PXM.a > cnfxbaradmin 8 on

M8850_NY.7.PXM.a > dspxbarstatus 8 0
M8850_NY                         System Rev: 02.01   Nov. 28, 2001 15:42:46 PST
MGX8850                                              Node Alarm: CRITICAL
Switch CD No: 8          Switch ASIC No: 0
Operational Status Bitmap   : 0x3FFF
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
Misc Error Bitmap: 0x0
Fabric Available Bandwidth: 6000 Mbps
Switch Card Available Bandwidth: 3000 Mbps
Highest Bandwidth Needed: 2488 Mbps

M8850_NY.7.PXM.a > 

Do the following on an MGX 8950 switch:

1. Turn off the switch fabric in slot 9.

2. Use the dspxbarstatus command for this slot but check only one switch plane for activity. Note that the available bandwidth is 0.

3. Turn on the switch fabric for slot 9.

4. Check the status by using the dspxbarstatus command and again specifying switch plane 0.

M8950_DC.7.PXM.a > cnfxbaradmin 9 off
Shut-down of switch could be service affecting!
cnfxbaradmin: Do you want to proceed (Yes/No)? y
M8950_DC.7.PXM.a > dspxbarstatus 9 0
M8950_DC                         System Rev: 02.01   Nov. 28, 2001 14:45:35 PST
MGX8950 (JBP-2)                                      Node Alarm: MAJOR
Switch CD No: 9          Switch ASIC No: 0
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
Misc Error Bitmap: 0x0
Fabric Available Bandwidth: 5000 Mbps
Switch Card Available Bandwidth: 0 Mbps
Highest Bandwidth Needed: 2488 Mbps
M8950_DC.7.PXM.a > cnfxbaradmin 9 on

M8950_DC.7.PXM.a > dspxbarstatus 9 0
M8950_DC                         System Rev: 02.01   Nov. 28, 2001 14:58:47 PST
MGX8950 (JBP-2)                                      Node Alarm: MAJOR
Switch CD No: 9          Switch ASIC No: 0
Operational Status Bitmap   : 0xFCFF
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
Misc Error Bitmap: 0x0
Fabric Available Bandwidth: 7000 Mbps
Switch Card Available Bandwidth: 2000 Mbps
Highest Bandwidth Needed: 2488 Mbps

cnfxbarerrthresh

Configure Crossbar Error Threshold—specify a threshold for a particular crossbar alarm severity.

The Syntax Description contains a list of possible errors. A crossbar error threshold consists of:

A period for counting errors

Severity of the resulting alarm (minor, major, and critical)

Upper and lower thresholds for each alarm severity

Usage Guidelines for cnfxbarerrthresh

Note the following details about this command:

You can specify only one error type and one severity for each execution of the cnfxbarerrthresh command. For example, to change the thresholds for minor, major, and critical alarms for one error type, you must run cnfxbarerrthresh three times.

You must enter all parameters of the threshold whether or not you change them. For example, if you want to change only the number of milliseconds (threshtime), you must include the existing error type, severity, alarm count, and clear count.


Note The default settings for crossbar error thresholds are optimal for most applications. The dspxbarerrthresh command shows the existing thresholds. Before changing thresholds, consider using dspxbarerrthresh to check current thresholds.


Cards on Which This Command Runs

PXM45

Syntax

cnfxbarerrthresh <errtype> <threshtime> <severity> <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—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. The range is 0-2, as follows

0 = minor alarm
1 = major alarm
2 = critical alarm

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.

almcnt

The number of errors for an alarm severity above which the alarm goes to the next higher severity.


Related Commands

dspxbarerrthresh

Attributes

Log: yes

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                         System Rev: 02.01   Dec. 05, 2000 02:29:17 GMT
MGX8850                                              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             2000      0     3         4    15        200   301

cnfxbarmgmt

Configure Crossbar Management—configure load sharing.

The purpose of load sharing is to a provide backup for the switch planes on the active PXM45. The backup is provided by the switch planes on the standby PXM45. The hardware on which cnfxbarmgmt focuses is a redundant pair of PXM45s in an MGX 8850 switch. (In an MGX 8950 switch, load sharing is always enabled.) If a switch plane fails on the active PXM45, a switch plane on the standby PXM45 takes over the switching tasks of the failed ASIC.


Note The switch blocks the cnfxbarmgmt command if a bad switch ASIC already exists on the active PXM45.


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. dspdevalms

4. dspdeverrhist

Cards on Which This Command Runs

PXM45

Syntax

cnfxbarmgmt <loadSharing> <autoShutdown> <planeAlarmThresh>

Syntax Description

loadSharing

0: Disable load sharing.

1: Enable load sharing.

-1: Force load sharing to be disabled when one or more bad switch ASICs exist on the active PXM45.

autoShutdown

If auto shutdown is enabled, a crossbar link is shut down when errors cross a major-alarm threshold for the crossbar core or crossbar port. Type 1 or 0.

0 (the default): disables automatic shut-down

1: enable automatic shut-down

planeAlarmThresh

An alarm threshold for declaring that a switch plane is bad: the determination of a bad link depends on the crossbar error threshold. Each unit of the threshold represents a link between the switch ASIC and the card.

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.
Range: 1-32


Related Commands

dspxbarmgmt, dspxbarerrthresh, dspdeverrhist

Attributes

Log: yes

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                         System Rev: 02.01   Dec. 06, 2000 00:44:20 GMT
MGX8850                                              Node Alarm: MAJOR
Load Sharing: Enable
Auto Shutdown: Enable
Plane Alarm Threshold: 5

conntrace

Connection Trace

The conntrace command lets you start a trace on an established connection and display the result. The required parameter is the PNNI physical port identifier. To identify the connection, you can specify the call reference or the VPI and VCI.

Cards on Which This Command Runs

PXM45

Syntax

conntrace <portid> [-callRef callRef [-endptRef endptRef]] [-vpi vpi [-vci vci]]

Syntax Description

portid

Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.

-callRef

You can provide a call reference by itself to trace the connection. A call reference by itself identifies a point-to-point call.

Range for callRef: 1-16777215

-endptRef

If you provide a call reference, you can also provide an endpoint reference for a point-to-multipoint (P2MP) call.


Note This release does not support P2MP calls.


Range for endptRef:1-32767

-vpi

The VPI has a range that depends on whether the connection is a virtual path connection or a virtual channel connection, as follows:

1-4095 for a VPC

1-4095 for a VCC

-vci

The VCI has a range of 0-65355.


Related Commands

pathtraceport, pathracenode, pathtraceie

Attributes

Log: yes

State: active

Privilege: SUPER_GP


Example

Do a connection trace on by using a known VPI and VCI. The port ID is 9:1.8:8, and the VPI and VCI are both 66.

tokyo.8.PXM.a > conntrace 9:1.8:8 -vpi 66 -vci 66

Result:SUCCESS  Reason: N/
InterfaceId:9:1.8:8
Originating Interface VPI : 66
Originating Interface VCI : 66
Originating Interface Call Ref : 1
    NodeId                                          EgressPort   VPI    VCI  CallRef
  56:160:47.00918100000000107b65f448.00107b65f448.01 17373186        0     35        1 
PhysPortId=9:1.2:2
  56:160:47.00918100000000309409f3bb.00309409f3bb.01      0
  Terminating Interface VPI : 66
  Terminating Interface VCI : 66

Terminating Interface Call Ref : 1

copycons

Copy Connections

The purpose of the copycons command is debugging. It copies one or more endpoints from a specified endpoint.

This debugging command works by incrementing the VCI for a VCC endpoints and the VPI for a VPC endpoints.

The following steps are recommended when using this command:

1. Add a slave endpoint then a master endpoint.

2. Copy the slave endpoints by using the copycons command.

3. Copy the master endpoints by using the copycons command.


Caution The purpose of this command is to facillitate debugging and is not intended to be an easy way to add significant numbers of user connection.

Improper use of this command can result in dangling (unpaired) endpoints in the network.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

copycons <source> <destn> [-rem <remote Conn Id>] [-num <num. conns to add>]
[-verbose <1 | 0>]

Syntax Description

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.

1 = enable verbose

0 = disable verbose

Default: disabled


Related Commands

addcon, delcon

Attributes

Log: yes

State: active

Privilege: SERVICE_GP


Example

MGX8850.1.11.AXSME.a > copycons 3.10.50 3.10.60 -num 10

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, AXSM-E

Syntax

core (optional parameters—see Syntax Description for AXSM or PXM45)

Syntax Description (AXSMs)

The first entry in the following list is the core command itself because it produces a unique output when no parameters follow it. The list entries after the core command are the parameters. Each of these parameters must follow the core command even though each parameter description does not show core.

core

The core command without parameters indicates whether core dumps are enabled for the current slot and that files reside on the C drive.

?

The core command with a question mark lists the optional parameters.

mask

Enter core mask to display the following:

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."

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.

priority high

Enter core priority high to make core-dumping a high-priority task at the node level. High priority is the default for the switch to ensure that no cores are lost, so this command is necessary only if the priority is low and needs to change.

priority low

Enter core priority low to make core-dumping a low-priority at the node level.


Usage Guidelines

A description of usage considerations for the more complex parameters follows.

Disabling Core Dumps, Timeout, and Priority

You may want to disable core dumps for a slot due to the time to write core memory to disk. For example:

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 "cannot be turned ON." A reset reason that cannot trigger a core dump removes pertinent information from memory.

Redundancy Policy

After a redundant pair of service modules switches over, the former active card is rebooting, so a core dump is possible. Because the activated card is carrying the traffic, the time to write RAM contents from the reset card to disk normally is not an issue. For non-redundant service modules, however, the dump time may be a concern. The parameters for redundancy policy let you determine whether core dumps can occur in non-redundant service modules.

The redundancy policy is a node-level configuration. You can override the configuration on a per slot basis by enabling or disabling core dumps at the CLI of the individual card.

Aborting a Core Dump

In some circumstances, you would want to abort a service module core dump. Example situations follow:

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: yes

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

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 dots crossing the screen shows the progress of the dump. Check the status by entering core without parameters. The display shows that a snapshot occurred ("Manual dump"). Save the dump to the file called test_1.zip and confirm that it resides on the C drive.

M8850_LA.8.PXM.a > core hot-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:/.

Enter ll C: to check for the test_1.zip file. The example display is truncated to show just the zip file.

M8850_LA.8.PXM.a > ll C:
  size          date       time       name
--------       ------     ------    --------

19517299    JAN-31-2002  22:42:22   test_1.zip        

In the file system : 
    total space :  819200 K bytes
    free  space :  689221 K bytes

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 00001 not used (can't be turned ON)
OFF 00002 DRAM Parity Error 
OFF 00004 WatchDog Timeout Reset 
OFF 00008 Resource Overflow 
OFF 00010 Clear All Configuration (can't 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 
OFF 00200 Unknown 
ON  00400 Reset from PXM 
OFF 00800 Reset System (can't be turned ON)
OFF 01000 Switch Core Card 
ON  02000 Secondary Cache Error 
ON  04000 Software Error Reset 
OFF 08000 S/W reset due to upgrade (can't be turned ON)
OFF 10000 Restore All Configuration (can't be turned ON)
OFF 20000 Device Driver 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 00001 not used (can't be turned ON)
OFF 00002 DRAM Parity Error 
ON  00004 WatchDog Timeout Reset 
ON  00008 Resource Overflow 
OFF 00010 Clear All Configuration (can't be turned ON)
OFF 00020 Missing Task 
OFF 00040 Reset because of PXM Low Voltage 
OFF 00080 Reset By Event Log Task 
OFF 00100 Reset from Shell 
OFF 00200 Unknown 
OFF 00400 Reset from PXM 
OFF 00800 Reset System (can't be turned ON)
OFF 01000 Switch Core Card 
OFF 02000 Secondary Cache Error 
OFF 04000 Software Error Reset 
OFF 08000 S/W reset due to upgrade (can't be turned ON)
OFF 10000 Restore All Configuration (can't be turned ON)
OFF 20000 Device Driver Error 

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 00001 not used (can't be turned ON)
ON  00002 DRAM Parity Error 
ON  00004 WatchDog Timeout Reset 
ON  00008 Resource Overflow 
OFF 00010 Clear All Configuration (can't 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 
ON  00200 Unknown 
OFF 00400 Reset from PXM 
OFF 00800 Reset System (can't be turned ON)
OFF 01000 Switch Core Card 
ON  02000 Secondary Cache Error 
ON  04000 Software Error Reset 
OFF 08000 S/W reset due to upgrade (can't be turned ON)
OFF 10000 Restore All Configuration (can't be turned ON)
ON  20000 Device Driver 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 00001 not used (can't be turned ON)
ON  00002 DRAM Parity Error 
ON  00004 WatchDog Timeout Reset 
ON  00008 Resource Overflow 
OFF 00010 Clear All Configuration (can't 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 
ON  00200 Unknown 
OFF 00400 Reset from PXM 
OFF 00800 Reset System (can't be turned ON)
OFF 01000 Switch Core Card 
ON  02000 Secondary Cache Error 
ON  04000 Software Error Reset 
OFF 08000 S/W reset due to upgrade (can't be turned ON)
OFF 10000 Restore All Configuration (can't be turned ON)
ON  20000 Device Driver Error

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 00001 not used (can't be turned ON)
OFF 00002 DRAM Parity Error 
ON  00004 WatchDog Timeout Reset 
ON  00008 Resource Overflow 
OFF 00010 Clear All Configuration (can't be turned ON)
OFF 00020 Missing Task 
OFF 00040 Reset because of PXM Low Voltage 
OFF 00080 Reset By Event Log Task 
OFF 00100 Reset from Shell 
OFF 00200 Unknown 
OFF 00400 Reset from PXM 
OFF 00800 Reset System (can't be turned ON)
OFF 01000 Switch Core Card 
OFF 02000 Secondary Cache Error 
OFF 04000 Software Error Reset 
OFF 08000 S/W reset due to upgrade (can't be turned ON)
OFF 10000 Restore All Configuration (can't be turned ON)
OFF 20000 Device Driver 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 >

dclk

Display Clock Measured by System Clock Test

Display the Digital to Analog Converter (DAC) value and the deviation, in parts-per-million, of the output frequency of the current clock source. This is the nominal frequency value for the local oscillator on the PXM45 UIS3 card.

The local oscillator of the UIS3 is an Over-Controlled Crystal Oscillator (OCXO) with a nominal frequency of 19.44Mhz. The control voltage applied to the OCXO by the hardware circuitry on the board adjusts the output frequency range of the clock between +/- 7 PPM (136Hz) to +/- 14PPM (272Hz).

The DAC value is used to convert the digital voltage value, from the DSP FPGA, to the analog voltage, which controls the OCXO. The range of the input DAC value is from 0x0000 to 0xffff with a nominal value of 0x8000.

The dclk output displays the DAC value field, which is the difference between the current measured DAC value and the nominal DAC value of 0x8000, and the PPM values for the last 100 current clock samples that have been taken at the rate of one every second.

Cards on Which This Command Runs

PXM45

Syntax

dclk

Syntax Description

No parameters.


Related Commands

None

Attributes

Log: no log

State: active

Privilege: SERVICE_GP


Example

M8850_NY.7.PXM.a > dclk
    Sample        DAC   Dev ppm. 
      1         -900      -0.19
      2         -915      -0.19
      3         -915      -0.19
      4         -915      -0.19
      5         -900      -0.19
      6         -900      -0.19
      7         -916      -0.19
      8         -916      -0.19
      9         -916      -0.19
     10         -916      -0.19
     11         -916      -0.19
     12         -916      -0.19
     13         -900      -0.19
     14         -900      -0.19
     15         -899      -0.19
     16         -899      -0.19
     17         -899      -0.19
     18         -900      -0.19
     19         -900      -0.19
     20         -900      -0.19
     21         -899      -0.19
     22         -899      -0.19

Type <CR> to continue, Q<CR> to stop: 
     23         -900      -0.19
     24         -916      -0.19
     25         -899      -0.19
     26         -915      -0.19
     27         -915      -0.19
     28         -916      -0.19
     29         -900      -0.19
     30         -916      -0.19
     31         -916      -0.19
     32         -915      -0.19
     33         -915      -0.19
     34         -916      -0.19
     35         -916      -0.19
     36         -916      -0.19
     37         -900      -0.19
     38         -899      -0.19
     39         -900      -0.19
     40         -900      -0.19
     41         -900      -0.19
     42         -900      -0.19
     43         -915      -0.19
     44         -915      -0.19
     45         -916      -0.19

Type <CR> to continue, Q<CR> to stop: 
     46         -916      -0.19
     47         -915      -0.19
     48         -916      -0.19

dbgcon

Debug Connection—enables or disables logging of SPVC or SPVP-related errors.

Enable or disable the SPVC log at the switch level or for an individual SPVC or SPVP. To see whether the SPVC log is enabled, use the dspcons-dbg command.

Cards on Which This Command Runs

PXM45

Syntax

dbgcon <enable | disable> [-port <portid> -vpi <vpi> -vci <vci>]

Syntax Description

enable | disable

Enable or disable the SPVC log. Type the entire word. The default is disabled.

-port

The port specification. The portid has the format [shelf.]slot:subslot.port:subport, but shelf currently is always 1 and optional.

-vpi

A VPI has the range 0-4095.

-vci

A VCI has the range 0-65535. For an SPVP, specify a VCI of 0.


Related Commands

dspcons-dbg

Attributes

Log: no log

State: active, standby

Privilege: SERVICE_GP


Example

Enable the SPVC log. Specify PNNI port 9:1.8:8 and a VPI/VCI of 100/100.

ja8850.8.PXM.a > dbgcon enable -port 9:1.8:8 -vpi 100 -vci 100

Enable the log for the whole switch then check the status by using the dspcons-dbg command.

M8850_NY.7.PXM.a > dbgcon enable

  WARNING: This could significantly increase CPU
                               load and severely degrade performance.
  Do you want to proceed (Yes/No) ? y

M8850_NY.7.PXM.a > dspcons-dbg

Global SPVC/SPVP Event Log Status: Enable 
M8850_NY.7.PXM.a >

delchanloop

Delete Channel Loopback

Delete a loopback from a connection (channel). For an understanding of the purpose of channel loopbacks, see the description of addchanloop.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

delchanloop <ifNumber> <vpi> <vci>

Syntax Description

ifNumber

The logical port number. The range for AXSM is 1-60. The range for AXSM-E is 1-32.

vpi

The VPI of the connection. The range is 0-4095.

vci

The VCI of the connection. The range is 1-65535.


Related Commands

addchanloop, dspchanloop

Attributes

Log: yes

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

dellnloop

Delete Line Loop

Remove the line loopback state from a line.

Cards on Which This Command Runs

AXSM, AXSM-E

AXSM Syntax

dellnloop <-ds3 | -sonet> <bay.line>


Note For AXSM cards, the keyword ds3 applies to both T3 and E3 line types.


AXSM 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.


AXSM-E Syntax

dellnloop < -ds3 | -e3 | -sonet | -ds1 | -e1 bay.line>

AXSM-E Syntax Description

-ds3
-e3
-sonet
-ds1
-e1

Specifies a DS3, E3, T3 , SONET (OC-3c, OC-12c, OC-48c), DS1, or E1 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

addlnloop

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

Deleting a DS3 loopback line.

MGX8850.1.11.AXSME.a > dellnloop -ds3 1.6 -lpb 3
Line loop-back status will be changed.
Do you want to proceed (Yes/No) ?

dncon

Down Connection

Temporarily deactivates (or downs) a connection so you can modify or troubleshoot it. The dncon command applies to only an SPVC. Execute at the master endpoint of a connection. Subsequently, when you view commands with dspconinfo or dspcon at the master endpoint, the display shows the connection state as down. If you execute either of these commands at the slave endpoint, the state appears as failed.

To reactivate the connection, use upcon.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

dncon <ifNum> <vpi> <vci>

Syntax Description

ifNum

The logical port number. The range for AXSM is 1-60. The range for AXSM-E is 1-32.

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: yes

State: active

Privilege: GROUP1


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, AXSM-E

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: yes

State: active

Privilege: GROUP1


Example

De-activate line 1 in bay 1.

MGX8850.1.AXSM.a > dnln 1.1

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.


Caution For AXSM-E card, do not execute this command unless you want to change the SCT configuration. All connection configurations on the port are lost when you execute this command on the AXSM-E.

Cards on Which This Command Runs

AXSM, AXSM-E

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 is 1-60.

For AXSM-E, the range is 1-32.

Use dspports or dspport as needed to determine the need to disable a port.


Related Commands

dspport, dspports, upport

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

Disable port 1 on the current card.

MGX8850.1.AXSM.a > dnport 1

dspadjlnalm

Display Adjacent Line Alarms

The dspadjlnalm command lets you display the alarm status line for the adjacent back card. To acquire the status, enter the bay and line number for the active back card.


Note The clradjlnalmcnt command works for only inter-card APS.


Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

dspadjlnalm <bay.line>

Syntax Description

bay.line

The active bay and line.


Related Commands

dspadjlnalmcnt, clradjlnalmcnt

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


Example

MGX8850.3.AXSME.a > dspadjlnalm 1.1
Line Number              : 1.1
 Section Alarm State     : Clear
 Line Alarm State        : Clear
 Path Alarm State        : Clear
 Section Stat Alarm State: Clear
 Line Stat Alarm State   : Clear
 Path Stat Alarm State   : Clear
 LOCD Alarm State        : Clear

dspadjlnalmcnt

Display Adjacent Line Alarm Counters

You give the active card bay.line number and this command displays the alarm status line for the adjacent back card at the given time interval (intvl).


Note The clradjlnalmcnt command works for only inter-card APS.


Cards on Which This Command Runs

AXSM-E

Syntax

dspadjlnalmcnt <bay.line> <intvl>

Syntax Description

bay.line

The active bay and line.

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.


Related Commands

dspadjlnalm, clradjlnalmcnt

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


Example

MGX88503.AXSME.a> dspadjlnalmcnt 1.1 1
  Line Number     : 1.1       
  Interval Number : 1         

Section PM:     
  -----------     
  Num of LOSs     :          0
  Num of LOFs     :          0
  ESs             :          0
  SESs            :          0
  SEFSs           :          0
  CVs             :          0

Line PM:        
  -----------     
  Num of AISs     :          0
  Num of RFIs     :          0
                         Near End      Far End
  ESs             :          0           0
  SESs            :          0           0
  CVs             :          0           0
  UASs            :          0           0

Path PM:        
  -----------     
  Num of AISs     :          0
  Num of RFIs     :          0
                         Near End      Far End
  ESs             :          0           0
  SESs            :          0           0
  CVs             :          0           0
  UASs            :          0           0


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-E

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. DS1 line, or E1 line for AXSM-E card.

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


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

Display examples for AXSM-E.

MGX8850.11.AXSME.a > dspalm -sonet 1.1
Line Number             : 1.1
 Section Alarm State     : LOS,LOF
 Line Alarm State        : AIS
 Path Alarm State        : Clear
 Section Stat Alarm State: 
TotalESs,TotalSESs,TotalSEFSs,CurrentESs,CurrentSESs,CurrentSEFSs
 Line Stat Alarm State   : TotalUASs,CurrentUASs
 Path Stat Alarm State   : TotalUASs,CurrentUASs
 LOCD Alarm State        : LOCD

MGX8850.5.AXSME.a > dspalm -ds3 1.1
Line Number       : 1.1
  Alarm State            : XmtRAI,RcvLOF,RcvLOS,RcvOtherFailure
  Statistical Alarm State: SEFS15minAlarm,SEFS24hrAlarm,UAS15minAlarm,UAS24hrAlarm
  PLCP Alarm State       : Clear
  LOCD Alarm State       : LOCD

MGX8850.9.AXSME.a > dspalm -ds1 1.1
  Line Number            : 1.1
  Alarm State            : XmtFarEndLOF,LOF,LOS
  LOCD Alarm State       : LOCD

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, AXSM-E

Syntax

dspalmcnf <-sonetsec | -sonetline |-sonetpath | -ds3 | -e3 | -plcp> <bay.line>

Syntax Description

-sonetsec
-sonetline
-sonetpath
-ds3-
-e3
-plcp

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.

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.


Related Commands

cnfalm, dspalm, dspalms

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


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 

Display alarm configuration for AXSM-E cards.

MGX8850.1.11.AXSME.a > dspalmcnf -ds3 1.1
  LineNum:                 1.1
  Stat Alarm Severity:        Minor
             15min Threshold     24hr Threshold 
  LCV  :     20                 20
  LES  :     20                 20
  PCV  :     25                 25
  PES  :     20                 20
  PSES :     3                  3
  SEFS :     20                 20
  UAS  :     10                 10

MGX8850.1.6.AXSME.a > dspalmcnf -sonetsec 1.1
  LineNum: 1.1
  Section Stat Alarm Severity: Minor
                   15min Threshold    24hr Threshold
  Section ESs  :   20                 20
  Section SESs :   3                  3
  Section SEFSs:   3                  3
  Section CVs  :   25                 25

MGX8850.1.6.AXSME.a > dspalmcnf -sonetline 1.1   
  LineNum: 1.1
  Line Stat Alarm Severity: Minor
               15min Threshold    24hr Threshold 
  Line  ESs :  20                 20
  Line  SESs:  3                  3
  Line  CVs :  25                 25
  Line  UASs:  10                 10

MGX8850.1.6.AXSME.a > dspalmcnf -sonetpath 1.1
  LineNum: 1.1
  Path Stat Alarm Severity: Minor
                15min Threshold    24hr Threshold 
  Path ESs :    20                 20
  Path SESs:    3                  3
  Path CVs :    25                 25
  Path UASs:    10                 10

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-E

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-E 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

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 : 1
  CurrentSESs:              0           CurrentSESs: 0
  CurrentCVs :              1           CurrentCVs : 1
  CurrentUASs:              0           CurrentUASs: 0
Path PM:
--------
  Num of AISs:                      1
  Num of RFIs:                      1
  Near End                            Far End
  CurrentESs :              0           CurrentESs : 0
  CurrentSESs:              0           CurrentSESs: 0
  CurrentCVs :              0           CurrentCVs:  0
  CurrentUASs:              0           CurrentUASs: 0

For AXSM-E, examples show the performance monitoring alarm counters of a DS3, SONET, and DS1 line for current 15 minute interval. Counters with description "Num of . . ." are counters for the current 15 minute interval.

MGX8850.5.AXSME.a > dspalmcnt -ds3 1.1

  Line Number:      1.1
  Elapsed Time(in sec): 188
  Num of LOS :     0
  Num of OOF :     0
  Num of RAI :     0
  Near End                              Far End
  CurrentCCVs    : 0                    CurrentCCVs     : 0
  CurrentCESs    : 0                    CurrentCESs     : 0
  CurrentCSESs   : 0                    CurrentCSESs    : 0
  CurrentUASs    : 189                  CurrentUASs     : 0
  CurrentLCV     : 0
  CurrentLES     : 0
  CurrentPCV     : 0
  CurrentPES     : 0
  CurrentPSES    : 0
  CurrentSEFS    : 189
  CurrentLSES    : 0
  Current24HrLCV : 0
  Current24HrLES : 0
  Current24HrPCV : 0
  Current24HrPES : 0
  Current24HrPSES: 0
  Current24HrSEFS: 29700
  Current24HrUAS : 29700
  Current24HrCCV : 0
  Current24HrCES : 0
  Current24HrCSES: 0
  Current24HrLSES: 0

MGX8850.11.AXSME.a > dspalmcnt -sonet 1.1 
Line Number         : 1.1
Elapsed Time(in sec): 298
Section PM: 
----------- 
  Num of LOSs     : 0
  Num of LOFs     : 0
  CurrentESs      : 299
  CurrentSESs     : 299
  CurrentSEFSs    : 299
  CurrentCVs      : 0
  Current24HrESs  : 64795
  Current24HrSESs : 64795
  Current24HrSEFSs: 64795
  Current24HrCVs  : 0
Line PM:
--------
  Num of AISs: 0
  Num of RFIs: 0
  Near End                              Far End
  CurrentESs     : 0                    CurrentESs     : 0
  CurrentSESs    : 0                    CurrentSESs    : 0
  CurrentCVs     : 0                    CurrentCVs     : 0
  CurrentUASs    : 299                  CurrentUASs    : 0
  Current24HrESs : 0                    Current24HrESs : 0
  Current24HrSESs: 0                    Current24HrSESs: 0
  Current24HrCVs : 0                    Current24HrCVs : 0
  Current24HrUASs: 64795                Current24HrUASs: 0
Path PM:
--------
  Num of AISs: 0
  Num of RFIs: 0
  Near End                              Far End
  CurrentESs     : 0                    CurrentESs     : 0
  CurrentSESs    : 0                    CurrentSESs    : 0
  CurrentCVs     : 0                    CurrentCVs     : 0
  CurrentUASs    : 299                  CurrentUASs    : 0
  Current24HrESs : 0                    Current24HrESs : 0
  Current24HrSESs: 0                    Current24HrSESs: 0
  Current24HrCVs : 0                    Current24HrCVs : 0
  Current24HrUASs: 64795                Current24HrUASs: 0

MGX8850.5.AXSME.a > dspalmcnt -ds1 1.1

  Line Number:      1.1
  Elapsed Time(in sec): 520

  Near End                               Far End
  CurrentUASs     : 0                    CurrentUASs     : 0
  CurrentLESs     : 0                    CurrentLESs     : 0
  CurrentESs      : 0                    CurrentESs      : 0
  CurrentSESs     : 0                    CurrentSESs     : 0
  CurrentSEFSs    : 0                    CurrentSEFSs    : 0
  CurrentPCVs     : 0                    CurrentPCVs     : 0
  CurrentLCVs     : 0

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, AXSM-E

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
   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

Display alarms for the lines on the current AXSM-E card.

MGX8850.11.AXSME.a > dspalms

---------------------------------------------
Line Number: 1.1 
Alarm State 
   Section : LOS,LOF
   Line    : AIS
   Path    : Clear
   LOCD    : LOCD
Statistical Alarm State
   Section : TotalESs,TotalSESs,TotalSEFSs,CurrentESs,CurrentSESs,CurrentSEFSs
   Line    : TotalUASs,CurrentUASs
   Path    : TotalUASs,CurrentUASs

Line Number: 1.2 
Alarm State 
   Section : LOS,LOF
   Line    : AIS
   Path    : Clear
   LOCD    : LOCD
Statistical Alarm State
   Section : TotalESs,TotalSESs,TotalSEFSs,CurrentESs,CurrentSESs,CurrentSEFSs
   Line    : TotalUASs,CurrentUASs
   Path    : TotalUASs,CurrentUASs

Line Number: 1.3 
Alarm State 
   Section : Clear
   Line    : Clear
   Path    : Clear
   LOCD    : Clear
Statistical Alarm State
   Section : Clear
   Line    : Clear
   Path    : Clear

Line Number: 1.4 
Alarm State 
   Section : Clear
   Line    : Clear
   Path    : Clear
   LOCD    : Clear
Statistical Alarm State
   Section : Clear
   Line    : Clear
   Path    : Clear

dspautolndiag

Display Auto Line Diagnostics

Displays the status of auto line diagnostic feature on card.

Cards on Which This Command Runs

AXSM-E

Syntax

dspautolndiag

Syntax Description

No Parameters


Related Commands

cnfautolndiag

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


Example

MGX8850.5.AXSME.a > dspautolndiag
Auto Line Diagnostics : Disabled

M8850_NY.5.AXSME.a >

dspbecnt

Display Bit Error Count

The dspbecnt command lets you display the APS-related bit error counters.

Cards on Which This Command Runs

AXSM

Syntax

dspbecnt <working-bay.line>

Syntax Description

working-bay.line

Identifies the bay (1 or 2) and the number of the line. The line number is from 1 to the highest numbered line on the back card. For the range of line numbers on specific AXSM models, see Table 9-1.


Related Commands

addapsln, cnfapsln, delapsln, dspapsln, dspapslns, switchapsln, dspapsbkplane, dspbecnt

Attributes

Log: no log

State: active

Privilege: ANYUSER


dspbert

Display Bit Error Rate Test

Displays the status of the bit error rate test.

Cards on Which This Command Runs

AXSM-E

Syntax

dspbert <bay.line>

Syntax Description

bay

Bay number: 1 or 2.

line

Line number:

For OC12: 1

For OC3, T3, E3: 1-4


Related Commands

dspbertstats

Attributes

Log: no log

State: active

Privilege: ANYUSER


Example

MGX8850.10.AXSME.a > dspbert 1.1
  Bert Admin  Operational   BERT 		 			Start               
  Line Status Status        Pattern                   	 			 	Date                
  ---- ------ ------------- ---------------------- --------------------
   1.1  Down      OutOfSync            AltOneZero 

dspbertstats

Display Bit Error Rate Test Statistics

Displays the bit error rate test statistics.

Cards on Which This Command Runs

AXSM-E

Syntax

dspbertstats <bay.line>

Syntax Description

bay

Bay number: 1 or 2

line

Line number:

For OC12: 1

For OC3, T3, E3: 1-4


Related Commands

dspbert

Attributes

Log: no log

State: active

Privilege: ANYUSER


Example

MGX8850.5.AXSME.a > dspbertstats 1.1     
    Bert Bits        Bit Errors Errors 
    Line Received    Received 		 Injected 
    ---- ----------  ---------- --------
     1.1 0           0 			 0

dspcd

Display Card

Display the following information about a card:

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.


Note 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, AXSM-E

Syntax

dspcd

Syntax Description

This command does not take parameters.

Related Commands

dspcds, version

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


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.


M8850_NY.7.PXM.a > dspcd
M8850_NY                         System Rev: 02.01   Dec. 22, 2001 22:38:43 PST
MGX8850                                              Node Alarm: MAJOR
Slot Number    7    Redundant Slot:  8

                    Front Card          Upper Card          Lower Card
                    ----------          ----------          ----------

Inserted Card:      PXM45               UI Stratum3         PXM HardDiskDrive  
Reserved Card:      PXM45               UI Stratum3         PXM HardDiskDrive  
State:              Active              Active              Active         
Serial Number:      SBK050302AF         SBK045203PJ         SBK044602HJ 
Prim SW Rev:        2.1(70.131)A        ---                 ---
Sec SW Rev:         2.1(70.131)A        ---                 ---
Cur SW Rev:         2.1(70.131)A        ---                 ---
Boot FW Rev:        2.1(70.131)A        ---                 ---
800-level Rev:      A0                  A0                  A0   
800-level Part#:    800-06147-08        800-05787-02        800-05052-04
CLEI Code:          BAA670YCAA          BA7IBCLAAA          BA7IADNAAA 
Reset Reason:       On Reset From Shell
Card Alarm:         NONE                
Failed Reason:      None                
Miscellaneous Information:

M8850_NY                         System Rev: 02.01   Dec. 22, 2001 22:38:43 PST
MGX8850                                              Node Alarm: MAJOR

Crossbar Slot Status:      Present

Alarm Causes
------------
    NO ALARMS                 

M8850_NY.7.PXM.a > 

Display card details for the current AXSM-1-2488.

MGX8850.1.AXSM.a > dspcd
                    Front Card          Upper Card          Lower 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           ---

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  Lines:1.1
Port Group[2]:
#Chans supported:32512  Lines:1.2
Port Group[3]:
#Chans supported:32512  Lines:2.1
Port Group[4]:
#Chans supported:32512  Lines:2.2 

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, dspswalms, dspclkalms,

AXSM: dspalm, dspalms

Attributes

Log: no log

State: active

Privilege: ANYUSER


Examples

Display card-level alarms for the card in slot 8.

node19.8.PXM.a > dspcdalms 8
Node Card Alarm Summary

Line Alarm       Slot   8  Critical    0   Major    0   Minor    0
Port Alarm       Slot   8  Critical    0   Major    0   Minor    0
Connect Alarm    Slot   8  Critical    0   Major    0   Minor    0

Display card alarms without specifying a slot.

MGX8850.7.PXM.a > dspcdalms
Node Card Alarm Summary

Line Alarm       Slot   1  Critical    0   Major    0   Minor    0
Port Alarm       Slot   1  Critical    0   Major    0   Minor    0
Feeder Alarm     Slot   1  Critical    0   Major    0   Minor    0
Channel Alarm    Slot   1  Critical    0   Major    0   Minor    0
Line Alarm       Slot   2  Critical    0   Major    0   Minor    0
Port Alarm       Slot   2  Critical    0   Major    0   Minor    0
Feeder Alarm     Slot   2  Critical    0   Major    0   Minor    0
Channel Alarm    Slot   2  Critical    0   Major    0   Minor    0
Line Alarm       Slot   3  Critical    0   Major    0   Minor    0
Port Alarm       Slot   3  Critical    0   Major    0   Minor    0
Feeder Alarm     Slot   3  Critical    0   Major    0   Minor    0
Channel Alarm    Slot   3  Critical    0   Major    2   Minor    0
Line Alarm       Slot   5  Critical    0   Major    0   Minor    0
Port Alarm       Slot   5  Critical    0   Major    0   Minor    0
Feeder Alarm     Slot   5  Critical    0   Major    0   Minor    0
Channel Alarm    Slot   5  Critical    0   Major    0   Minor    0
Line Alarm       Slot   6  Critical    0   Major    0   Minor    0
Port Alarm       Slot   6  Critical    0   Major    0   Minor    0
Feeder Alarm     Slot   6  Critical    0   Major    0   Minor    0
Channel Alarm    Slot   6  Critical    0   Major    0   Minor    0
Line Alarm       Slot   9  Critical    1   Major    0   Minor    0
Port Alarm       Slot   9  Critical    0   Major    0   Minor    0
Feeder Alarm     Slot   9  Critical    0   Major    0   Minor    0
Channel Alarm    Slot   9  Critical    0   Major    0   Minor    0
Line Alarm       Slot  10  Critical    2   Major    0   Minor    1
Port Alarm       Slot  10  Critical    0   Major    0   Minor    0
Feeder Alarm     Slot  10  Critical    0   Major    0   Minor    0
Channel Alarm    Slot  10  Critical    0   Major    0   Minor    0
Line Alarm       Slot  12  Critical    0   Major    0   Minor    0
Port Alarm       Slot  12  Critical    0   Major    0   Minor    0
Feeder Alarm     Slot  12  Critical    0   Major    0   Minor    0
Channel Alarm    Slot  12  Critical    0   Major    0   Minor    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 
Slot 13 Crit 0 Maj 0 Min 0 || Slot 29 Crit 0 Maj 0 Min 0 
Slot 14 Crit 0 Maj 0 Min 0 || Slot 30 Crit 0 Maj 0 Min 0 
Slot 15 Crit 0 Maj 0 Min 0 || Slot 31 Crit 0 Maj 0 Min 0 
Slot 16 Crit 0 Maj 0 Min 0 || Slot 32 Crit 0 Maj 0 Min 0 
Use dspcdalms <slot> to see more detail. 

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

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 

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. (AXSM)

Cells to and from QE1210. (AXSM-E)

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, AXSM-E

Syntax

dspcdcnt

Related Commands

clrcdcnt (on the AXSM), dspxbar, dspdevalms, dspdeverrhist, dspxbarerrthresh

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


AXSM Example

Display the cell transfers between the current AXSM and the switch planes (crossbar planes).

U1.11.AXSM.a > dspcdcnt
Ingress cells to xbar Egress cells from xbar 
--------------------- ---------------------- 
plane 1 : 0000000000000000326416 0000000000000000325869 
plane 2 : 0000000000000000326415 0000000000000000325890 
plane 3 : 0000000000000000217610 0000000000000000217413 
plane 4 : 0000000000000000000000 0000000000000000000000 
plane 5 : 0000000000000000217611 0000000000000000217433 
plane 6 : 0000000000000000326417 0000000000000000325996 
plane 7 : 0000000000000000326417 0000000000000000325996 
plane 8 : 0000000000000000000000 0000000000000000000000
Ingress cells to destination slot 
---------------------------------------------------------------- 
slot 01: 0000000000000000000000 slot 02: 0000000000000000000000 
slot 03: 0000000000000000000000 slot 04: 0000000000000000000000 
slot 05: 0000000000000000000000 slot 06: 0000000000000000000000 
slot 07: 0000000000000000004036 slot 08: 0000000000000000000000 
slot 09: 0000000000000000000000 slot 10: 0000000000000000000000 
slot 11: 0000000000000001736851 slot 12: 0000000000000000000000 
slot 13: 0000000000000000000000 slot 14: 0000000000000000000000 

Ingress cells Egress cells 
------------------------------------ --------------------------- 
To backplane: 0000000000000001740886 From backplane: 
0000000000000001738597 
From QE : 0000000000000001740888 To QE: 
0000000000000001738599
QE Total (Ingress + Egress) 
----------------------------------------------------- 
Undefined cell type : 0000000000000000000000 
Err OAM (bad CRC) cells : 0000000000000000000000 
Invalid OAM type or function: 0000000000000000000000 
Unsupported OAM cells : 0000000000000000000000 
Err RM (bad CRC) cells : 0000000000000000000000 
QE congestion discard CLP0 : 0000000000000000000000 
QE congestion discard CLP1 : 0000000000000000000000

Display cell transfers between the current AXSM and the switching planes (crossbars) on the XM60 cards.

NODE_U4.3.AXSM.a > dspcdcnt
Ingress Count                          Egress Count
-------------                          ------------
Cells to xbar plane[1]:         8702  Cells from xbar plane[1]: 8733
Cells to xbar plane[2]:         8702  Cells from xbar plane[2]: 8627
Cells to xbar plane[3]:        10443  Cells from xbar plane[3]: 10503
Cells to xbar plane[4]:            0  Cells from xbar plane[4]: 0
Cells to xbar plane[5]:            0  Cells from xbar plane[5]: 0
Cells to xbar plane[6]:            0  Cells from xbar plane[6]: 0
Cells to xbar plane[7]:            0  Cells from xbar plane[7]: 0
Cells to xbar plane[8]:            0  Cells from xbar plane[8]: 0
Total cells to backplane:      27847  Total cells from backplane:27863
Cells from QE48         :      27847  Cells to QE48:             27863
Undefined cells         :          0  CLP0 cells discard:        0
Errored OAM cells       :          0  CLP1 cells discard:        0
Invalid OAM cells       :          0
Unsupported OAM cells   :          0
Errored RM cells        :          0
 
Cells to dest slot[01]:            0  Cells to dest slot[02]:   0
Cells to dest slot[03]:            0  Cells to dest slot[04]:   0
Cells to dest slot[05]:            0  Cells to dest slot[06]:   0
Cells to dest slot[07]:        27847  Cells to dest slot[08]:   0
Cells to dest slot[11]:            0  Cells to dest slot[12]:   0
Cells to dest slot[13]:            0  Cells to dest slot[14]:   0
Cells to dest slot[15]:            0  Cells to dest slot[16]:   0

AXSM-E Example

Display card count on AXSM-E.

MGX8850.6.AXSME.a > dspcdcnt
All cell counters are cleared upon read!

           Ingress cells to xbar       Egress cells from xbar
           ---------------------       ----------------------
plane 1 :  0000000000000000219156      0000000000000000219204
plane 2 :  0000000000000000219201      0000000000000000219027
plane 3 :  0000000000000000263077      0000000000000000263335
plane 4 :  0000000000000000000000      0000000000000000000000
plane 5 :  0000000000000000000000      0000000000000000000000
plane 6 :  0000000000000000000000      0000000000000000000000
plane 7 :  0000000000000000000000      0000000000000000000000
plane 8 :  0000000000000000000000      0000000000000000000000

          Ingress cells to destination slot
----------------------------------------------------------------
slot 01 :  0000000000000000000000      slot 02: 0000000000000000000000
slot 03 :  0000000000000000000000      slot 04: 0000000000000000000000
slot 05 :  0000000000000000000000      slot 06: 0000000000000000688036
slot 07 :  0000000000000000013398      slot 08: 0000000000000000000000
slot 09 :  0000000000000000000000      slot 10: 0000000000000000000000
slot 11 :  0000000000000000000000      slot 12: 0000000000000000000000
slot 13 :  0000000000000000000000      slot 14: 0000000000000000000000

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    3 Task failed          : scm                     
09/05/95-09:14:08 tRootTask    3 Task failed          : scm                     
value = 0 = 0x0

wilco.7.PXM.a >

dspcds

Display Cards

Displays high-level information for all the cards in the node. For more detailed information about a card, execute dspcd on the CLI of that card. The information that dspcds provides is the:

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


Example

Display information for all cards in the MGX 8850 switch.

M8850_NY.7.PXM.a > dspcds
M8850_NY                         System Rev: 02.01   Dec. 22, 2001 22:40:51 PST
Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: -8
                                                     Node Alarm: MAJOR
Card  Front/Back          Card           Alarm      Redundant   Redundancy     
Slot  Card State          Type           Status     Slot        Type   
---   ----------          --------       --------   -------     -----  

01    Active/Active       AXSM_4OC12     NONE       02          PRIMARY SLOT
02    Standby/Active      AXSM_4OC12     NONE       01          SECONDARY SLOT
03    Active-U/Active     AXSM_4OC12     NONE       NA          NO REDUNDANCY
04    Empty               ---            ---        ---         ---    
05    Active/Empty Resv   AXSME_2OC12    MAJOR      NA          NO REDUNDANCY
06    Active/Mismatch     AXSM_16OC3_B   MINOR      NA          NO REDUNDANCY
07    Active/Active       PXM45          NONE       08          PRIMARY SLOT
08    Standby/Active      PXM45          NONE       07          SECONDARY SLOT
09    Active/Active       RPM_PR         NONE       NA          NO REDUNDANCY
10    Empty               ---            ---        ---         ---    
11    Empty               ---            ---        ---         ---    
12    Empty               ---            ---        ---         ---    
13    Empty               ---            ---        ---         ---    
14    Empty               ---            ---        ---         ---    

M8850_NY.7.PXM.a >

Display information for all cards in the current MGX 8950 switch.

M8950_DC.7.PXM.a > dspcds
M8950_DC                         System Rev: 02.01   Dec. 22, 2001 22:40:53 PST
Chassis Serial No:   SCA0504043H Chassis Rev: A0     GMT Offset: -8
                                                     Node Alarm: CRITICAL
Card  Front/Back          Card           Alarm      Redundant   Redundancy     
Slot  Card State          Type           Status     Slot        Type   
---   ----------          --------       --------   -------     -----  

01    Active/Active       AXSM_4OC12     NONE       NA          NO REDUNDANCY
02    Empty               ---            ---        ---         ---    
03    Empty               ---            ---        ---         ---    
04    Empty               ---            ---        ---         ---    
05    Active/Active       AXSM_1OC48_B   NONE       NA          NO REDUNDANCY
06    Empty               ---            ---        ---         ---    
07    Active/Active       PXM45B         NONE       08          PRIMARY SLOT
08    Empty Resvd/Empty   ---            MAJOR      07          SECONDARY SLOT
09    Active/Empty        XM_60          NONE       NA          NO REDUNDANCY
10    Active/Empty        XM_60          NONE       NA          NO REDUNDANCY
11    Active/Active       RPM_PR         NONE       NA          NO REDUNDANCY
12    Empty               ---            ---        ---         ---    
13    Empty               ---            ---        ---         ---    
14    Empty               ---            ---        ---         ---    
15    Empty               ---            ---        ---         ---    

Type <CR> to continue, Q<CR> to stop: 
M8950_DC                         System Rev: 02.01   Dec. 22, 2001 22:40:53 PST
Chassis Serial No:   SCA0504043H Chassis Rev: A0     GMT Offset: -8
                                                     Node Alarm: CRITICAL
Card  Front/Back          Card           Alarm      Redundant   Redundancy     
Slot  Card State          Type           Status     Slot        Type   
---   ----------          --------       --------   -------     -----  

16    Empty               ---            ---        ---         ---    
25    Active/Empty        XM_60          NONE       NA          NO REDUNDANCY
26    Active/Empty        XM_60          NONE       NA          NO REDUNDANCY

M8950_DC.7.PXM.a > 

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.

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-4 for a list of alarm categories. Note that, although the card alarms appear to apply to only service modules, this category can also apply to the PXM45.

Figure 9-4 Alarm Type Hierarchy

The alarm monitoring function reports the highest status alarm after it sorts the current alarms first by severity then by hierarchy. If alarms of equal severity exit in both hierarchies, the system reports the node alarm as the highest status alarm. For example, if a major alarm exists on a line and a major power alarm exists, the dspcdstatus command displays the power alarm as the highest status alarm.

Cards on Which This Command Runs

PXM45

Syntax

dspcdstatus

Syntax Description

This command requires a slot number.

Related Commands

dspndalms, dspcdalms, dspenvalms, dspclkalms, dspswalms, dspalm (AXSM), dspalms (AXSM)

Attributes

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  11

Card Alarm Status - Type LINE              Severity CRITICAL 

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

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, AXSM-E

AXSM Syntax

dspchancnt <ifNum> <vpi> <vci> <isPVC>

AXSM Syntax Description

ifNum

The logical port number. The range for AXSM is 1-60. The range for AXSM-E is 1-32.

vpi

The VPI 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.


AXSM-E Syntax

dspchancnt <ifNum> <vpi> <vci> -r <dsp interval> -max <max dsp time>

AXSM-E Syntax Description

ifNum

The logical port number. The range for AXSM is 1-60. The range for AXSM-E is 1-32.

vpi

The VPI in the range 1-4095.

vci

The VCI in the range 1-65535.

-r

The display interval in which to display the channel statistics in the range of 1-60 seconds.

-max

The duration of time to display the channel statistics in the range of 0-3600 seconds.


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

Display channel counters on AXSM-E for 1 10 100.

MGX8850.6.AXSME.a > dspchancnt 1 10 100 -r 1 -max 1
           Ingress chan stat                          Egress chan stat
--------------------------------------      --------------------------------------
All non-compliant cells   :          0
CLP1 non-compliant        :          0
CLP0 non-compliant        :          0
CLP0 -> CLP1              :          0
Cells from port          
(Before policing)         :          0      Cells to port             :          0
CLP0 from port            :          0      CLP0 to port              :          0
CLP1 from port            :          0      CLP1 to port              :          0
EOF from port             :          0      EOF to port               :          0
EFCI1 from port           :          0      EFCI1 to port             :          0
                                            RM to port                :          0
Cells to network          :          0      Cells from network        :          0
CLP0 to network           :          0      CLP0 from network         :          0
CLP1 to network           :          0      CLP1 from network         :          0
EFCI1 to network          :          0      EFCI1 from network        :          0
Cells discarded in qe     :          0      Cells discarded in qe     :          0
CLP0 discarded in qe      :          0      CLP0 discarded in qe      :          0
CLP1 discarded in qe      :          0      CLP1 discarded in qe      :          0
EOF discarded in qe       :          0
                                            EFCI1 discarded in qe     :          0
VC queue depth            :          0      VC queue depth            :          0
ACR (Valid for WFQ conns) :          1      ACR (Valid for WFQ conns) :          1
OAM from port             :          0      OAM to port               :          0
RM from port              :          0
RM to network             :          0      RM from network           :          0
OAM to network            :          0      OAM from network          :          0
OAM discarded in qe       :          0      OAM discarded in qe       :          0
EFCI1 discarded in qe     :          0
RM discarded in qe        :          0      RM discarded in qe        :          0


                             Type <Ctrl>C to quit
----------------------------------------------------------------------------------
           Ingress chan stat                          Egress chan stat
--------------------------------------      --------------------------------------
All non-compliant cells   :          0
CLP1 non-compliant        :          0
CLP0 non-compliant        :          0
CLP0 -> CLP1              :          0
Cells from port          
(Before policing)         :        999      Cells to port             :       1000
CLP0 from port            :        999      CLP0 to port              :       1000
CLP1 from port            :          0      CLP1 to port              :          0
EOF from port             :          0      EOF to port               :          0
EFCI1 from port           :          0      EFCI1 to port             :          0
                                            RM to port                :          0
Cells to network          :       1000      Cells from network        :       1000
CLP0 to network           :       1000      CLP0 from network         :       1000
CLP1 to network           :          0      CLP1 from network         :          0
EFCI1 to network          :          0      EFCI1 from network        :          0
Cells discarded in qe     :          0      Cells discarded in qe     :          0
CLP0 discarded in qe      :          0      CLP0 discarded in qe      :          0
CLP1 discarded in qe      :          0      CLP1 discarded in qe      :          0
EOF discarded in qe       :          0
                                            EFCI1 discarded in qe     :          0
VC queue depth            :          0      VC queue depth            :          0
ACR (Valid for WFQ conns) :          1      ACR (Valid for WFQ conns) :          1
OAM from port             :          0      OAM to port               :          0
RM from port              :          0
RM to network             :          0      RM from network           :          0
OAM to network            :          0      OAM from network          :          0
OAM discarded in qe       :          0      OAM discarded in qe       :          0
EFCI1 discarded in qe     :          0
RM discarded in qe        :          0      RM discarded in qe        :          0


dspchanloop

Display Channel Loopbacks

Show channel (connection) loopbacks on a logical port.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

dspchanloop <ifNumber>

Syntax Description

ifNumber

The logical port number. The ranges for ifNumber are as follows:

AXSM: 1-60

AXSM-E: 1-32


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      rVPI      rVCI
  4     igrLpbk       1        50         0        35 

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, AXSM-E

Syntax

dspchantests <ifNum> <vpi> <vci> [-num <count>]

Syntax Description

ifNum

The logical port number. The range for AXSM is 1-60. The range for AXSM-E is 1-32.

vpi

The VPI 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


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    Result     Round Trip Delay
=============    =========    =========    =======    ================
01.0010.00100:    OAM Lpbk     ingress     Success          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    Result     Round Trip Delay
=============    =========    =========    =======    ================
01.0010.00100:    OAM Lpbk     egress      TimeOut              0 


dspclkalms

Display Clock Alarms

Displays alarms associated with the primary or secondary clock source.

The switch constantly monitors the state of the clocks. On the local node, the clock monitor declares an alarm if the clock becomes undetectable or goes out of specification for any reason. The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:

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


Example

Display clock alarms.

M8850_NY.7.PXM.a > dspclkalms
M8850_NY                         System Rev: 02.01   Dec. 22, 2001 22:44:28 PST
MGX8850                                              Node Alarm: MAJOR
Clock Manager Alarm Summary
----------------------------
NETWORK CLOCK ALARM : LOST PRIMARY REFERENCE : MINOR
NETWORK CLOCK ALARM : STANDBY LOST PRIMARY REFERENCE : MINOR
Critical       Major          Minor          
000            000            002

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:

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.


Note 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.


Cards on Which This Command Runs

PXM45

Type of Clock Source

The type is either BITS or generic. Currently, generic applies to only an AXSM-sourced clock. If a user-specified priority of clock is not configured, the source is null. For the current release, the null source is presumed to be the internal oscillator.

Possible Sources

The source of the clock has the format [shelf.]slot:subslot.port:subport. More typically, the source has the two-part, short-hand form slot.line or slot.port. If the source is an AXSM, the format is slot.line.

For a BITS clock, the format is slot.port. The slot for a BITS clock is 7. The logical port is always 35 or 36. Port 35 refers to the upper external clock connector, and port 36 refers to the lower connector.

Clock Status

The status of a particular clock source can be one of the following:

"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.

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—narrow-
band 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 clock source is the internal oscillator in either the free running mode or the hold-over mode: in this case, the software omits this final validation attempt because no other clocks sources within a clock hierarchy are available.

Revertive Behavior

For information on revertive behavior, see the cnfclksrc description.

Syntax

dspclksrcs

Related Commands

cnfclksrc, delclksrc, dspclkalms

Attributes

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

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.

Cards on Which This Command Runs

AXSM, AXSM-E, PXM45

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 consist of the following:

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.

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).

Display Connection on the AXSM-E

The display output on the AXSM-E also displays RDI (Remote Defect Indication) information at the ATM Layer through the OAM mechanism in Ingress and Egress directions.

AXSM and AXSM-E Syntax

dspcon <ifNum> <vpi> <vci>

PXM45 Syntax

dspcon <portid> <vpi> <vci>

Syntax Description

ifNum

(AXSM, AXSM-E) Logical interface (port) number. The ranges are as follows:

AXSM: 1-60

AXSM-E: 1-32

portid

(PXM45) The port ID has the format [shelf.]slot:subslot.port:subport,
but shelf currently is always 1 and optional.

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


AXSM and AXSM-E Attributes

Log: no log

State: active

Privilege: GROUP1


Examples

Display connection 5 31 63000 on the current AXSM.

MGX8850.1.AXSM.a > dspcon 5 31 63000
--------------------------------------------------------------------------

Local   :               NSAP  Address               port     vpi    vci

(M)       4700918100000000107BE92F3F00000101180500  1.01.05 31 63000
Remote  :               NSAP  Address               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
--------------------------------------------------------------------------

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 

Display output for AXSM-E, port 1, vpi 10, vci 100.

MGX8850.6.AXSME.a > dspcon 1 10 100
--------------------------------------------------------------------------
Local   :                NSAP  Address                     vpi       vci   
(S)       47009181000000002A231F3C4A00000106180100          10       100  
Remote  :                NSAP  Address                     vpi       vci   
(M)       47009181000000002A231F3C4A00000106180200          10       100  
--------------------------------------------------------------------------
Conn. Type    :        VCC                      Admn Status  :    ADMN-UP
Service Type  :       cbr1                      Oper Status  :         OK
Controller    :          2                      Record #     :          0
--------------------------------------------------------------------------
Local PCR     :       1000                      Remote PCR   :       1000 
Local SCR     :        N/A                      Remote SCR   :        N/A 
Local CDV     :        N/A                      Remote CDV   :        N/A 
Local CTD     :        N/A                      Remote CTD   :        N/A 
Local MBS     :        N/A                      Remote MBS   :        N/A 
Max Cost      :        N/A                      Frame discard:          N
Local CDVT    :     250000                      OAM segment  :    ENABLED
--------------------------------------------------------------------------
OAM CC Config :   DISABLED                      Statistics   :   DISABLED
--------------------------------------------------------------------------
Loopback Type : No  Lpbk | Dir: N/A     | Status: No Lpbk | RTD:      0us 
--------------------------------------------------------------------------

--------------------------------------------------------------------------
Port side Tx  :     normal                      Swth side Tx :        AIS
Port side Rx  :     normal                      Swth side Rx :     normal
--------------------------------------------------------------------------
Ing-E2E-AIS   ING-SEG-AIS   Ing-E2E-RDI   Ing-SEG-RDI  
   NO              NO             NO            NO 
--------------------------------------------------------------------------
Egr-E2E-AIS   Egr-SEG-AIS   Egr-E2E-RDI   Egr-SEG-RDI  
  YES             NO             NO              NO 
--------------------------------------------------------------------------
Ing-E2E-CCFAIL   Ing-SEG-CCFAIL   Egr-E2E-CCFail   Egr-SEG-CCFail 
  ---               ---              ---            --- 
--------------------------------------------------------------------------
CONDITIONED  IfFail   Mismatch   LMI-ABIT
   NO         YES         NO         NO 
--------------------------------------------------------------------------

dspconalmcnts

Display Connection Alarm Counts—display connection alarms on interfaces by alarm cause.

The dspconalmcnts command lists errored connections on the logical interfaces on the card. It lists by alarm cause. The causes are:

Conditioning

Ingress alarm

Egress alarm

Connection conditioning failure

Mismatch

A-bit

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

dspconalmcnts

Syntax Description

This command takes no parameters.

Related Commands

dspconalms

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


Example

Display the connection alarms by alarm cause.

M8850_SF.1.AXSM.a > dspconalmcnts
**************************************************************************
************ CONNECTIONS IN ALARM PER INTERFACE (BY ALM CAUSE)************
**************************************************************************
IF#  IfState  #Condn  #IngAlm  #EgrAlm  #CCFail  #ifFail  #mismatch  #Abit
--   -------  ------  -------  -------  -------  -------  ---------  -----
01   ACTV     00000   00000    00000    00000    00000    00000      00000
02   ACTV     00000   00000    00000    00000    00000    00000      00000
03   ACTV     00000   00000    00000    00000    00000    00000      00000
********************  SUMMARY ALARM COUNT FOR THE CARD *******************
#Condn    #IngAlm    #EgrAlm    #CCFail    #ifFail   #mismatch   #abit
000000     000000     000000     000000     000000    000000    000000

dspconalms

Display Connection Alarms—display connection alarms on interfaces by alarm severity.

Use the dspconalms command to display connection alarms. The command lists alarms by port and shows instances by the severities of critical, major, and minor alarms. The display also shows which types of failures constitute each of these severities.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

dspconalms

Syntax Description

This command takes no parameters.

Related Commands

dspconalmcnts

Attributes

Log: no log

State: active

Privilege: ANYUSER


Example

Display connection alarms. This card has three logical interfaces but no connection alarms.

M8850_SF.1.AXSM.a > dspconalms
****************************************************************
******* CONNECTIONS IN ALARM PER INTERFACE (BY SEVERITY) *******
****************************************************************
IF#      IfState    #Critical    #Major     #Minor
--       -------    ---------    ------     ------
01       ACTV          00000     00000      00000
02       ACTV          00000     00000      00000
03       ACTV          00000     00000      00000
****************************************************************
**************  PRESENT ALARM SEVERITY CONFIGURATION  **********
****************************************************************

CRITICAL:  Mismatch  
MAJOR   :  Condn  CCFail  
MINOR   :  IngAlm  EgrAlm  IfFail  Abit  

M8850_SF.1.AXSM.a > 

dspconinfo

Display Summaries of Connection Information—display general information about SPVCs.

The dspconinfo runs on the PXM45 and lists the total number SPVCs on each PNNI port on the switch. The default operation of the command is to show all SPVCs or SPVPs, With the optional parameters, you can specify one or more types of information to display.

The display shows:

PNNI physical port number

Number of active connections

Number of failed connections

Number of administratively inactive (or down) connections as a result of dncon

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] [-detail {true | false}] [-owner {master | slav] -sc {cbr | rtvbr | nrtvbr | abr | ubr}

Syntax Description

-port

Identifies a PNNI physical port. The format for portid is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.

-detail

Determines whether the display contains information for all interfaces and slots or just slots. Type "true" after the keyword for all interfaces and slots. Type "false" for just slots.

Default: true

-owner

Lets you specify the endpoint of the connection. Type "master" or "slave."

-sc

Directs the command to display connections of a particular service type. Type one of the following after the keyword: cbr, nrtvbr, rtvbr, abr, or ubr.

Default: no default


Related Commands

None

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


Examples

Display the SPVC summaries on the switch with the following conditions:

No options: a total of 13 active connections exist.

UBR connections: a total of 2 endpoints are listed.

Connections on port 5:1.2:2.

Connections at slot 5.

Slave endpoints.

atlanta.7.PXM.a > dspconinfo

Local Port     #Active   #Failed      #Down     #Total  
-----------------------------------------------------------
5:1.2:2            13          0          0         13


atlanta.7.PXM.a > dspconinfo -sc ubr

Local Port     #Active   #Failed      #Down     #Total  
-----------------------------------------------------------
5:1.2:2             2          0          0          2
atlanta.7.PXM.a > dspconinfo -port 5:1.2:2

Local Port     #Active   #Failed      #Down     #Total  
-----------------------------------------------------------
5:1.2:2            13          0          0         13

atlanta.7.PXM.a > dspconinfo -detail false

Local Slot     #Active    #Failed      #Down     #Total  
-----------------------------------------------------------
5                   13          0          0         13
atlanta.7.PXM.a > dspconinfo -owner slave

Local Port     #Active   #Failed      #Down     #Total  
-----------------------------------------------------------
5:1.2:2             0          0          0          0

dspconload

Display Connection Load—display the number of cells actually traversing the ingress and egress.

The dspconload command lets you see the current load on a connection. With the statistics provided by dspconload, you can determine whether the current load on the connection suggests a modification to the connection or possible troubleshooting.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

dspconload <ifNum> <vpi> <vci>

ifNum

Logical interface (port) number. For AXSM, the range is 1-60. For AXSM-E, the range is 1-32.

vpi

The VPI of the connection. The range is 0-4095.

vci

The VCI of the connection. The range is 0-65635.


Related Commands

dspcons, dspcon, dspload

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


AXSM Example

Display the load on the connection with a VPI and VCI of 101 and 101, respectively, on logical port 3. In this case, no traffic currently exists on the connection.

MGX8850.10.AXSM.a > dspconload 3 101 101
Getting the stats. Please wait ...
                        Ingress            Egress
Cell rate (cps)       : 0                  0 

AXSM-E Example

Display the load on the connection with a VPI and VCI of 10 and 100, respectively, on logical port 1.

MGX8850.6.AXSME.a > dspconload 1 10 100
           Ingress                                         Egress
--------------------------------------      --------------------------------------
All non-compliant cells   :          0
CLP1 non-compliant        :          0
CLP0 non-compliant        :          0
CLP0 -> CLP1              :          0
Cells from port          
(Before policing)         :        999      Cells to port             :        999
CLP0 from port            :        999      CLP0 to port              :        999
CLP1 from port            :          0      CLP1 to port              :          0
EOF from port             :          0      EOF to port               :          0
EFCI1 from port           :          0      EFCI1 to port             :          0
                                            RM to port                :          0
Cells to network          :        999      Cells from network        :        999
CLP0 to network           :        999      CLP0 from network         :        999
CLP1 to network           :          0      CLP1 from network         :          0
EFCI1 to network          :          0      EFCI1 from network        :          0
Cells discarded in qe     :          0      Cells discarded in qe     :          0
CLP0 discarded in qe      :          0      CLP0 discarded in qe      :          0
CLP1 discarded in qe      :          0      CLP1 discarded in qe      :          0
EOF discarded in qe       :          0
                                            EFCI1 discarded in qe     :          0
VC queue depth            :          0      VC queue depth            :          0
ACR (Valid for WFQ conns) :          1      ACR (Valid for WFQ conns) :          1
OAM from port             :          0      OAM to port               :          0
RM from port              :          0
RM to network             :          0      RM from network           :          0
OAM to network            :          0      OAM from network          :          0
OAM discarded in qe       :          0      OAM discarded in qe       :          0
EFCI1 discarded in qe     :          0
RM discarded in qe        :          0      RM discarded in qe        :

dspcons

Display Connections—display basic information for all connections.

The default usage of dspcons uses no parameters and causes all available information for the connections to appear. To narrow the scope of the output, use one or more optional parameters.

The dspcons command runs on the CLI of either the AXSM or the PXM45. The set of optional parameters and the output are different on these cards. (See Syntax Description for the card-specific parameters.) On the AXSM, the columns at the head of the information fields are:

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.


Cards on Which This Command Runs

PXM45, AXSM, AXSM-E

PXM45 Syntax

dspcons [-port portid] [-vpi starting-vpi] [-vci starting vci] [-state {fail | ais | abit | ok | down}]
[-owner {master | slave}]

PXM45 Syntax Description

-port

Identifies a PNNI physical port. The format for portid is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.

-vpi

The VPI of the connection that you would like to serve as the starting connection in the display.

-vci

The VPI of the connection that you would like to serve as the starting connection in the display.

-state

A specific connection state. The display shows only the connections with the state you specify. Note that on the PXM45, you must spell out the entire state keyword. The keywords for specifying a state are

failed—only failed connections

ais—connections with alarm indication signal (AIS) set

abit—connections on which an A-bit error has occurred

ok—connections with no problems

down—connections that are administratively down because a user has executed dncon to down the connection

-owner

Specifies connections where the local endpoint is either master or slave.


AXSM Syntax

dspcons [-conn <conn id>] [-filt <filter options>] [-if <intf no>] [-vpi <vpi filter>] [-vci <vci filter>]

AXSM Syntax Description

-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 and 1-32 for the AXSM-E.
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.


AXSM-E Syntax

dspcons [-conn <conn id>] [-filt <filter options>]

AXSM-E Syntax Description

-conn

The connection ID (conn ID) of the connection to begin the display. The format of conn ID is:

ifNum.vpi.vci

On the AXSM-E, the range for ifNum is 1-32. The VPI has the range 0-4095. The VCI has the range 32-65535.

-filt

Filter criteria: An optional keyword to specify a filter for finding the endpoints which are in an alarm state. The default is all (5), meaning all endpoints are displayed irrespective of their alarm state.

ais (1} | condn (2} | iffail (3} | ccfail (4} | all(5)


Related Commands

dspcon, addcon, cnfcon, delcon, dncon, upcon

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


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     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

Local  Addr: 47.00918100000000107b65f33d.000001061801.00
Remote Addr: 47.00918100000000107b65f33d.000001061803.00
6:2.1:3           200 200    6:1.1:1           200 100     OK          MASTER
Local  Addr: 47.00918100000000107b65f33d.000001061803.00
Remote Addr: 47.00918100000000107b65f33d.000001061801.00
9:1.3:3            10 100    Routed              0 0       FAIL        SLAVE
Local  Addr: 47.00918100000000107b65f33d.000001091803.00
Remote Addr: 00.000000000000000000000000.000000000000.00
11:1.1:2           10 100    11:1.1:2           20 100     OK          SLAVE
Local  Addr: 47.00918100000000107b65f33d.0000010b1802.00
Remote Addr: 47.00918100000000107b65f33d.0000010b1802.00

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   Type   SrvcType   M/S    Upld    Admn   Alarm
------    ----------   ----   --------   ---    ----    ----   -----
    0  01.0010.00100   VCC        cbr1   S   010c7953    UP      none
    1  04.0020.00100   VCC        cbr1   M   010c7964    UP      none

AXSM-E Example

Display all connections on the current AXSM-E.

MGX8850.6.AXSME.a > dspcons
record    Identifier   Type   SrvcType   M/S    Upld    Admn   Alarm
------    ----------   ----   --------   ---    ----    ----   -----
    0  01 0010 00100   VCC        cbr1   S   01b945d2     UP   multiple
    1  02 0010 00100   VCC        cbr1   M   01b945f2     UP   E-AisRdi

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 

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.

M8850_NY.7.PXM.a > dspcontrollers
M8850_NY                         System Rev: 02.01   Dec. 22, 2001 22:46:53 PST
MGX8850                                              Node Alarm: MAJOR
Number of Controllers:        1                                       
Controller Name:              PNNI Controller                         
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:                                                     


M8850_NY.7.PXM.a > 

dspdevalms

Display Device Alarms—display severity of crossbar alarms.

The dspdevalms command shows whether a crossbar alarm is minor, major, or critical. The display shows status on both the active and standby PXM45 or all the XM60s.

For fault isolation after you execute dspdevalms, you can check the possible errors (illustrated in the example). The following is a top-down sequence of commands related to switch planes (or ASICs):

1. dspndalms

2. dspswalms

3. dspdevalms

4. dspdeverr

5. dspdeverrhist

Cards on Which This Command Runs

PXM45

Syntax

dspdevalms <device name> [-pslot <slot no>]

dspdevalms <device name> [-xslot <xbar slot>] [-pl <plane No>]

Syntax Description

device
name

Type the mandatory device name in upper case characters. Choices are:


Note In the current release, only XBAR CORE is supported.


XBAR CORE indicates whether the errors on a link or the whole switch plane crossed any of the alarm thresholds. Most alarms pertain to individual links, but several are plane-based. If necessary, you can configure thresholds by using cnfxbarerrthresh.

XBAR PORT indicates whether the errors on the crossbar ports (Humvee or any equivalent) on a service module crossed the alarm thresholds.

XBAR SLOT BANDWIDTH alarm is raised based on the number of crossbar links that are up for a service module.

-pslot

Refers to the physical slot number of the card that sends and receives cells to and from the switch planes. You can specify an individual slot for details or display all slots (with an asterisk) to show whether an error has occurred on any switch plane. In the MGX 8850 node, the slot number range is 1-14. In the MGX 8950 node, the slot number range is 1-16.

-xslot

The number of the slot where the crossbar fabric resides. You can type an asterisk to specify all switching cards. On the MGX 8850 node, the individual slot number is 7 or 8. On the
MGX 8950 node, the slot is 9, 10, 25, or 26.

-pl

The plane number applies only when you specify the xslot parameter. On an MGX 8850 node, the range for switch planes is 0-2, otherwise type an asterisk * for all planes.

On the MGX 8950 node, the range of plane numbers in any slot is 0-3 or * for all planes.


Related Commands

dspswalms, dspdeverr, dspdeverrhist, dspxbarerrthresh, clrxbaralms

Attributes

Log: no log

State: active

Privilege: ANYUSER


Example (8850)

Display switching device alarms for physical slot 7 and switch ASIC 0. Thereafter, display switching device alarms for crossbar slot 7, switch ASIC 0.

M8850_NY.7.PXM.a > dspdevalms XBARCORE -pslot 7 -pl 0
M8850_NY                         System Rev: 02.01   Dec. 09, 2001 23:31:46 PST
MGX8850                                              Node Alarm: CRITICAL

          XBAR CORE ERROR ALARM INFO FOR SLOT: 7
Fabric
Slot/ Loss  Rx    Rx    Xmit  Hdr   Pload Slot  Slot  BP
Plane Sync  Cv    Disp  Par   CRC   CRC   Remap Recur Par
----- ----  ----  ----  ----  ----  ----  ----  ----  ---
 7/0  --    --    --    --    --    --    --    --    --    
 7/1  --    --    --    --    --    --    --    --    --    
 7/2  --    --    --    --    --    --    --    --    --    

 8/0  --    --    --    --    --    --    --    --    --    
 8/1  --    --    --    --    --    --    --    --    --    
 8/2  --    --    --    --    --    --    --    --    -- 
          XBAR CORE ERROR ALARM INFO FOR SLOT: 7
Fabric
Slot/   SFrame SFrame ACP   Sev
Plane   Tick   Lock   Addr  Summ.
-----   ----   ----   ---   ----
 7/0    --     --     --    --  
 7/1    --     --     --    --  
 7/2    --     --     --    --  

 8/0    --     --     --    --  
 8/1    --     --     --    --  
 8/2    --     --     --    --  

M8850_NY.7.PXM.a > dspdevalms XBARCORE -xslot 7 -pl 0
M8850_NY                         System Rev: 02.01   Dec. 10, 2001 15:23:29 PST
MGX8850                                              Node Alarm: MAJOR

          XBAR CORE ERROR ALARM INFO:
 Fabric Slot No: 7        Xbar Plane No: 0 
      Loss  Rx    Rx    Xmit  Hdr   Pload Slot  Slot  BP
Slot  Sync  Cv    Disp  Par   CRC   CRC   Remap Recur Par
----- ----  ----  ----  ----  ----  ----  ----  ----  ---
   1  --    --    --    --    --    --    --    --    --    
   2  --    --    --    --    --    --    --    --    --    
   3  --    --    --    --    --    --    --    --    --    
   4  --    --    --    --    --    --    --    --    --
   5  --    --    --    --    --    --    --    --    --    
   6  --    --    --    --    --    --    --    --    --    
   7  --    --    --    --    --    --    --    --    --    
   8  --    --    --    --    --    --    --    --    --    
   9  --    --    --    --    --    --    --    --    --
  10  --    --    --    --    --    --    --    --    --
  11  --    --    --    --    --    --    --    --    --
  12  --    --    --    --    --    --    --    --    --
  13  --    --    --    --    --    --    --    --    --
  14  --    --    --    --    --    --    --    --    --

M8850_NY                         System Rev: 02.01   Dec. 10, 2001 15:23:29 PST
MGX8850                                              Node Alarm: MAJOR

          XBAR CORE ERROR ALARM INFO:
 Fabric Slot No: 7        Xbar Plane No: 0 
        SFrame SFrame ACP    Sev
Slot    Tick   Lock   Addr   Summ.
-----   ----   ----   ----   ----
   1    --     --     --     --  
   2    --     --     --     --  
   3    --     --     --     --  
   4    --     --     --     --
   5    --     --     --     --  
   6    --     --     --     --  
   7    --     --     --     --  
   8    --     --     --     --  
   9    --     --     --     --
  10    --     --     --     --
  11    --     --     --     --
  12    --     --     --     --
  13    --     --     --     --
  14    --     --     --     --

M8850_NY.7.PXM.a > 

Example (8950)

Display switch device alarms for physical slot 1. At the end of the display, critical alarms are indicated for the XM60 is slot 26. Use the command with the -xbar parameter to investigate these alarms. For this second action, the command entry is as follows:

dspdevalms XBARCORE -xslot 26 -pl 3

Thereafter, use dspdeverr for the physical slot and the crossbar slot. The displays show a bad link between slot 1 only and switch ASIC 3 on the XM60 in slot 26.

M8950_DC.7.PXM.a > dspdevalms XBARCORE -pslot 1
M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:39:30 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL

          XBAR CORE ERROR ALARM INFO FOR SLOT: 1
Fabric
Slot/ Loss  Rx    Rx    Xmit  Hdr   Pload Slot  Slot  BP
Plane Sync  Cv    Disp  Par   CRC   CRC   Remap Recur Par
----- ----  ----  ----  ----  ----  ----  ----  ----  ---
 9/0  --    --    --    --    --    --    --    --    --    
 9/1  --    --    --    --    --    --    --    --    --    
 9/2  --    --    --    --    --    --    --    --    --    
 9/3  --    --    --    --    --    --    --    --    --    

10/0  --    --    --    --    --    --    --    --    --    
10/1  --    --    --    --    --    --    --    --    --    
10/2  --    --    --    --    --    --    --    --    --    
10/3  --    --    --    --    --    --    --    --    --    
 

M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:39:30 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL


          XBAR CORE ERROR ALARM INFO FOR SLOT: 1
Fabric
Slot/   SFrame SFrame ACP   Sev
Plane   Tick   Lock   Addr  Summ.
-----   ----   ----   ---   ----
 9/0    --     --     --    --  
 9/1    --     --     --    --  
 9/2    --     --     --    --  
 9/3    --     --     --    --  

10/0    --     --     --    --  
10/1    --     --     --    --  
10/2    --     --     --    --  
10/3    --     --     --    --  

25/0  --    --    --    --    --    --    --    --    --    
25/1  --    --    --    --    --    --    --    --    --    
25/2  --    --    --    --    --    --    --    --    --    
25/3  --    --    --    --    --    --    --    --    --    

26/0  --    --    --    --    --    --    --    --    --    
26/1  --    --    --    --    --    --    --    --    --    
26/2  --    --    --    --    --    --    --    --    --    
26/3  Maj   Crit  Crit  --    Crit  Crit  --    --    --    
 


M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:39:30 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL


          XBAR CORE ERROR ALARM INFO FOR SLOT: 1
Fabric
Slot/   SFrame SFrame ACP   Sev
Plane   Tick   Lock   Addr  Summ.
-----   ----   ----   ---   ----
25/0    --     --     --    --  
25/1    --     --     --    --  
25/2    --     --     --    --  
25/3    --     --     --    --  

26/0    --     --     --    --  
26/1    --     --     --    --  
26/2    --     --     --    --  
26/3    --     --     --    Crit

M8950_DC.7.PXM.a > dspdevalms XBARCORE -xslot 26 -pl 3
M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:43:51 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL

          XBAR CORE ERROR ALARM INFO:
 Fabric Slot No: 26        Xbar Plane No: 3 
      Loss  Rx    Rx    Xmit  Hdr   Pload Slot  Slot  BP
Slot  Sync  Cv    Disp  Par   CRC   CRC   Remap Recur Par
----- ----  ----  ----  ----  ----  ----  ----  ----  ---
   1  Maj   Crit  Crit  --    Crit  Crit  --    --    --    
   2  --    --    --    --    --    --    --    --    --
   3  --    --    --    --    --    --    --    --    --
   4  --    --    --    --    --    --    --    --    --
   5  --    --    --    --    --    --    --    --    --    
   6  --    --    --    --    --    --    --    --    --
   7  --    --    --    --    --    --    --    --    --    
   8  --    --    --    --    --    --    --    --    --
  11  --    --    --    --    --    --    --    --    --
  12  --    --    --    --    --    --    --    --    --
  13  --    --    --    --    --    --    --    --    --
  14  --    --    --    --    --    --    --    --    --
  15  --    --    --    --    --    --    --    --    --
  16  --    --    --    --    --    --    --    --    --


          XBAR CORE ERROR ALARM INFO:
 Fabric Slot No: 26        Xbar Plane No: 3 
        SFrame SFrame ACP    Sev
Slot    Tick   Lock   Addr   Summ.
-----   ----   ----   ----   ----
   1    --     --     --     Crit
   2    --     --     --     --
   3    --     --     --     --
   4    --     --     --     --
   5    --     --     --     --  
   6    --     --     --     --
   7    --     --     --     --  
   8    --     --     --     --
  11    --     --     --     --
  12    --     --     --     --
  13    --     --     --     --
  14    --     --     --     --
  15    --     --     --     --
  16    --     --     --     --

M8950_DC.7.PXM.a > dspdeverr XBARCORE -pslot 1
M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:38:56 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL

        XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1
Fabric
Slot/   Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Plane   Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
 9/0        0       0       0       0       0       0       0       0       0 
 9/1        0       0       0       0       0       0       0       0       0 
 9/2        0       0       0       0       0       0       0       0       0 
 9/3        0       0       0       0       0       0       0       0       0 

10/0        0       0       0       0       0       0       0       0       0 
10/1        0       0       0       0       0       0       0       0       0 
10/2        0       0       0       0       0       0       0       0       0 
10/3        0       0       0       0       0       0       0       0       0 

        XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1
Fabric
Slot/   SFrame  SFrame  ACP     
Plane   Tick    Lock    Addr    
-----   ------  ------  ----    
 9/0       0       0       0 
 9/1       0       0       0 
 9/2       0       0       0 
 9/3       0       0       0 

10/0       0       0       0 
10/1       0       0       0 
10/2       0       0       0 
10/3       0       0       0 
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL


        XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1
Fabric
Slot/   Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Plane   Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
25/0        0       0       0       0       0       0       0       0       0 
25/1        0       0       0       0       0       0       0       0       0 
25/2        0       0       0       0       0       0       0       0       0 
25/3        0       0       0       0       0       0       0       0       0 

26/0        0       0       0       0       0       0       0       0       0 
26/1        0       0       0       0       0       0       0       0       0 
26/2        0       0       0       0       0       0       0       0       0 
26/3      220    3300    3300       0    3300    3300       0       0       0 
M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:38:56 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL


        XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1
Fabric
Slot/   SFrame  SFrame  ACP     
Plane   Tick    Lock    Addr    
-----   ------  ------  ----    
25/0       0       0       0 
25/1       0       0       0 
25/2       0       0       0 
25/3       0       0       0 

26/0       0       0       0 
26/1       0       0       0 
26/2       0       0       0 
26/3       0       0       0 

M8950_DC.7.PXM.a > dspdeverr XBARCORE -xslot 26 -pl 3
M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:45:43 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL

         XBAR CORE CURRENT ERROR COUNT :
 Fabric Slot No: 26        Xbar Plane No: 3 
        Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Slot    Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
   1      220    3300    3300       0    3300    3300       0       0       0 
   2       --      --      --      --      --      --      --      --      --
   3       --      --      --      --      --      --      --      --      --
   4       --      --      --      --      --      --      --      --      --
   5        0       0       0       0       0       0       0       0       0 
   6       --      --      --      --      --      --      --      --      --
   7        0       0       0       0       0       0       0       0       0 
   8       --      --      --      --      --      --      --      --      --
  11       --      --      --      --      --      --      --      --      --
  12       --      --      --      --      --      --      --      --      --
  13       --      --      --      --      --      --      --      --      --
  14       --      --      --      --      --      --      --      --      --
  15       --      --      --      --      --      --      --      --      --
  16       --      --      --      --      --      --      --      --      --

XBAR CORE CURRENT ERROR COUNT : 
 Fabric Slot No: 26        Xbar Plane No: 3 
Slot/   SFrame  SFrame   ACP    
Plane   Tick    Lock     Addr   
-----   ------  ------   ----   
   1        0       0       0 
   2       --      --      --
   3       --      --      --
   4       --      --      --
   5        0       0       0 
   6       --      --      --
   7        0       0       0 
   8       --      --      --
  11       --      --      --
  12       --      --      --
  13       --      --      --
  14       --      --      --
  15       --      --      --
  16       --      --      --

M8950_DC.7.PXM.a > 

dspdeverr

Display Device Errors—display current errors related to the switching fabric.

The dspdeverr command shows current alarms for the switch planes. The errors can be isolated to a specific link or the entire switch plane. (A link is the hardware path between the switch plane and the recipient card's bus transceiver.) Most errors result in the shutdown of only a link. Two of the three plane-based errors shut down the entire switch plane. Also, the error r types can be


Note The SFrame Tick and SFrame lock errors are critical and cause the whole plane to be unusable. The whole plane (and all the links on that plane) are shut down.


Cards on Which This Command Runs

PXM45

Syntax

dspdeverr <device name> [-pslot <slot no>]

dspdeverr <device name> [-xslot <xbar slot>] [-pl <plane No>]

Syntax Description

device
name

Type the mandatory device name in upper case characters. Choices are:


Note In the current release, only XBAR CORE is supported.


XBAR CORE indicates whether the errors on a link or the whole switch plane crossed any of the alarm thresholds. Most alarms pertain to individual links, but several are plane-based. If necessary, you can configure thresholds by using cnfxbarerrthresh.

XBAR PORT indicates whether the errors on the crossbar ports (Humvee or any equivalent) on a service module crossed the alarm thresholds.

XBAR SLOT BANDWIDTH alarm is raised based on the number of crossbar links that are up for a service module.

-pslot

The physical slot number of the card that sends and receives cells to and from the switch planes. You can specify an individual slot for details or display all slots (with an asterisk) to show whether an error has occurred on any switch plane. In the MGX 8850 node, the slot number range is 1-14. In the MGX 8950 node, the slot number range is 1-16.

-xslot

The number of the slot where the crossbar fabric resides. You can type an asterisk to specify all switching cards. On the MGX 8850 node, the individual slot number is 7 or 8. On the
MGX 8950 node, the slot is 9, 10, 25, or 26.

-pl

The plane number option applies only when you also specify the xslot parameter. On the MGX 8850 node, the switch plane range for either slot is 0-2 or * for all planes.

On the MGX 8950 node, the range of plane numbers in any slot is 0-3 or * for all planes.


Related Commands

dspdevalms, dspdeverrhist, cnfxbarerrthresh, dspxbarerrthresh

Attributes

Log: no log

State: active

Privilege: ANYUSER


Example

Do the following sequence of tasks:

1. Display XBARCORE errors for all physical slots.

2. Display XBARCORE errors for the physical slot that shows errors (slot 3).

3. Display XBARCORE errors for the switching card that shows errors (slot 8).

M8850_NY.7.PXM.a > dspdeverr XBARCORE -pslot *
M8850_NY                         System Rev: 02.01   Dec. 25, 2001 21:17:06 PST
MGX8850                                              Node Alarm: MAJOR

         XBAR CORE CURRENT ERROR COUNTERS SUMMARY
                   Fabric Slot / Plane
Slot    7/0     7/1     7/2       8/0     8/1     8/2
-----  ------  ------  ------    ------  ------  ------
 01        0       0       0         0       0       0 
 02        0       0       0         0       0       0 
 03        0       0       0        76      68      76 
 04       --      --      --        --      --      -- 
 05        0       0       0         0       0       0 
 06        0       0       0         0       0       0 
 07        0       0       0         0       0       0 
 08        0       0       0         0       0       0 
 09       --      --      --        --      --      -- 
 10       --      --      --        --      --      -- 
 11       --      --      --        --      --      -- 
 12       --      --      --        --      --      -- 
 13       --      --      --        --      --      -- 
 14       --      --      --        --      --      --

M8850_NY.7.PXM.a > dspdeverr XBARCORE -pslot 3
M8850_NY                         System Rev: 02.01   Dec. 24, 2001 22:49:24 PST
MGX8850                                              Node Alarm: MAJOR

        XBAR CORE CURRENT ERROR COUNT FOR SLOT: 3
Fabric
Slot/   Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Plane   Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
 7/0        0       0       0       0       0       0       0       0       0 
 7/1        0       0       0       0       0       0       0       0       0 
 7/2        0       0       0       0       0       0       0       0       0 

 8/0        1      15      15       0      15      15       0       0      15 
 8/1        1      15      15       0      15      15       0       0       7 
 8/2        1      15      15       0      15      15       0       0      15 
 
Type <CR> to continue, Q<CR> to stop: 
M8850_NY                         System Rev: 02.01   Dec. 24, 2001 22:49:24 PST
MGX8850                                              Node Alarm: MAJOR


        XBAR CORE CURRENT ERROR COUNT FOR SLOT: 3
Fabric
Slot/   SFrame  SFrame  ACP     
Plane   Tick    Lock    Addr    
-----   ------  ------  ----    
7/0       0       0       0 
7/1       0       0       0 
7/2       0       0       0 

8/0       0       0       0 
8/1       0       0       0 
8/2       0       0       0

M8850_NY.7.PXM.a > dspdeverr XBARCORE -xslot 8 -pl 2
M8850_NY                         System Rev: 02.01   Dec. 25, 2001 21:40:39 PST
MGX8850                                              Node Alarm: MAJOR

         XBAR CORE CURRENT ERROR COUNT :
 Fabric Slot No: 8        Xbar Plane No: 2 
        Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Slot    Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
   1        0       0       0       0       0       0       0       0       0 
   2        0       0       0       0       0       0       0       0       0 
   3        1      15      15       0      15      15       0       0      15 
   4       --      --      --      --      --      --      --      --      --
   5        0       0       0       0       0       0       0       0       0 
   6        0       0       0       0       0       0       0       0       0 
   7        0       0       0       0       0       0       0       0       0 
   8        0       0       0       0       0       0       0       0       0 
   9       --      --      --      --      --      --      --      --      --
  10       --      --      --      --      --      --      --      --      --
  11       --      --      --      --      --      --      --      --      --
  12       --      --      --      --      --      --      --      --      --
  13       --      --      --      --      --      --      --      --      --
  14       --      --      --      --      --      --      --      --      --

Type <CR> to continue, Q<CR> to stop: 
M8850_NY                         System Rev: 02.01   Dec. 25, 2001 21:40:39 PST
MGX8850                                              Node Alarm: MAJOR

         XBAR CORE CURRENT ERROR COUNT : 
 Fabric Slot No: 8        Xbar Plane No: 2 
Slot/   SFrame  SFrame   ACP    
Plane   Tick    Lock     Addr   
-----   ------  ------   ----   
   1        0       0       0 
   2        0       0       0 
   3        0       0       0 
   4       --      --      --
   5        0       0       0 
   6        0       0       0 
   7        0       0       0 
   8        0       0       0 
   9       --      --      --
  10       --      --      --
  11       --      --      --
  12       --      --      --
  13       --      --      --
  14       --      --      --


M8850_NY.7.PXM.a > dspdeverr XBARCORE -xslot 8
M8850_NY                         System Rev: 02.01   Dec. 24, 2001 22:14:02 PST
MGX8850                                              Node Alarm: MAJOR

         XBAR CORE CURRENT ERROR COUNT :
 Fabric Slot No: 8        Xbar Plane No: 0 
        Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Slot    Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
   1        0       0       0       0       0       0       0       0       0 
   2        0       0       0       0       0       0       0       0       0 
   3        1      15      15       0      15      15       0       0      15 
   4       --      --      --      --      --      --      --      --      --
   5        0       0       0       0       0       0       0       0       0 
   6        0       0       0       0       0       0       0       0       0 
   7        0       0       0       0       0       0       0       0       0 
   8        0       0       0       0       0       0       0       0       0 
   9       --      --      --      --      --      --      --      --      --
  10       --      --      --      --      --      --      --      --      --
  11       --      --      --      --      --      --      --      --      --
  12       --      --      --      --      --      --      --      --      --
  13       --      --      --      --      --      --      --      --      --
  14       --      --      --      --      --      --      --      --      --

Type <CR> to continue, Q<CR> to stop: 
M8850_NY                         System Rev: 02.01   Dec. 24, 2001 22:14:02 PST
MGX8850                                              Node Alarm: MAJOR

         XBAR CORE CURRENT ERROR COUNT : 
 Fabric Slot No: 8        Xbar Plane No: 0 
Slot/   SFrame  SFrame   ACP    
Plane   Tick    Lock     Addr   
-----   ------  ------   ----   
   1        0       0       0 
   2        0       0       0 
   3        0       0       0 
   4       --      --      --
   5        0       0       0 
   6        0       0       0 
   7        0       0       0 
   8        0       0       0 
   9       --      --      --
  10       --      --      --
  11       --      --      --
  12       --      --      --
  13       --      --      --
  14       --      --      --

dspdeverrhist

Display Device Error History—display specific crossbar errors since last reset of a switch card.

The dspdeverrhist command shows numbers of various types of errors on each slot-link. Note that the error can occur anywhere along the path of the ASIC and the hardware on the service module. The types of errors apply to the 60-byte switch frames.


Note 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 for triggering the alarms 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.

The plane-based alarms are of three types: SFrame Tick, SFrame Lock and ACP illegal target error. All slots are affected by plane based errors.


Note The SFrame Tick and SFrame lock errors are critical and cause the whole plane to be unusable. The whole plane (and all the links on that plane) are shut down.


A top-down sequence of troubleshooting commands for isolating faults in the switching fabric are:

1. dspndalms

2. dspswalms

3. dspdevalms

4. dspdeverrhist

Cards on Which This Command Runs

PXM45

Syntax

dspdeverrhist <device name> [-pslot <slot no>]

dspdeverrhist <device name> [-xslot <xbar slot>] [-pl <plane no>]

Syntax Description

device
name

Type the mandatory device name in upper case characters. Choices are:


Note In the current release, only XBAR CORE is supported.


XBAR CORE indicates whether the errors on a link or the whole switch plane crossed any of the alarm thresholds. Most alarms pertain to individual links, but several are plane-based. If necessary, you can configure thresholds by using cnfxbarerrthresh.

XBAR PORT indicates whether the errors on the crossbar ports (Humvee or any equivalent) on a service module crossed the alarm thresholds.

XBAR SLOT BANDWIDTH alarm is raised based on the number of crossbar links that are up for a service module.

-pslot

The physical slot number of the card that sends and receives cells to and from the switch planes. You can specify an individual slot for details or display all slots (with an asterisk) to show whether an error has occurred on any switch plane. In the MGX 8850 node, the slot number range is 1-14. In the MGX 8950 node, the slot number range is 1-16.

-xslot

The number of the slot where the crossbar fabric resides. You can type an asterisk to specify all switching cards. On the MGX 8850 node, the individual slot number is 7 or 8. On the
MGX 8950 node, the slot is 9, 10, 25, or 26.

-pl

The plane number option applies only when you also specify the xslot parameter. On the MGX 8850 node, the switch plane range for either slot is 0-2 or * for all planes.

On the MGX 8950 node, the range of plane numbers in any slot is 0-3 or * for all planes.


Related Commands

dspxbar, dspdevalms, dspxbarerrthresh, cnfxbarerrthresh, dspndalms, dspswalms

Attributes

Log: yes

State: active, standby

Privilege: ANYUSER


Example

Two screens are necessary to display all error types. Note that the screen display can accommodate only a finite number of errors without being distorted. Therefore, a K for 1000 or an M for 1000000 multiplier may be necessary—not the case in the first example.

Display the physical slot error history for slot 1. The command parameters are XBARCORE -pslot 1. The view of this display is from the card in slot 1 to all the switch planes. The display shows a small number of errors on the switch planes on the backup PXM45. The errors are not the plane-based errors that would shut down the planes entirely (Sframe tick and SFrame lock). That the same variety of errors appear for all three switch planes suggests that the problem is not in the ASICs themselves.

M8850_NY.7.PXM.a > dspdeverrhist XBARCORE -pslot 1
M8850_NY                         System Rev: 02.01   Dec. 21, 2001 23:07:37 PST
MGX8850                                              Node Alarm: MAJOR

        XBAR CORE HISTORY ERROR COUNT FOR SLOT: 1
Fabric
Slot/   Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Plane   Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
 7/0        0       0       0       0       0       0       0       0       0 
 7/1        0       0       0       0       0       0       0       0       0 
 7/2        0       0       0       0       0       0       0       0       0 

 8/0        2      30      30       0      30      30       0       0      21 
 8/1        2      30      30       0      30      30       0       0      21 
 8/2        2      30      30       0      30      30       0       0      19 

        XBAR CORE HISTORY ERROR COUNT FOR SLOT: 1
Fabric
Slot/   SFrame  SFrame  ACP     
Plane   Tick    Lock    Addr    
-----   ------  ------  ----    
 7/0       0       0       0 
 7/1       0       0       0 
 7/2       0       0       0 

 8/0       0       0       0 
 8/1       0       0       0 
 8/2       0       0       0

Display errors for each card slot addressed by the switch planes in slot 8.

M8850_NY.7.PXM.a > dspdeverrhist XBARCORE -xslot 8
M8850_NY                         System Rev: 02.01   Dec. 21, 2001 23:11:39 PST
MGX8850                                              Node Alarm: MAJOR

         XBAR CORE HISTORY ERROR COUNT :
 Fabric Slot No: 8        Xbar Plane No: 0 
        Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Slot    Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
   1        2      30      30       0      30      30       0       0      21 
   2        3      45      45       0      45      45       0       0      30 
   3        1      15      15       0      15      15       0       0      15 
   4       --      --      --      --      --      --      --      --      --
   5        1      15      15       0      15      15       0       0      15 
   6        0       0       0       0       0       0       0       0       0 
   7        0       0       0       0       0       0       0       0       0 
   8        0       0       0       0       0       0       0       0       0 
   9       --      --      --      --      --      --      --      --      --
  10       --      --      --      --      --      --      --      --      --
  11       --      --      --      --      --      --      --      --      --
  12       --      --      --      --      --      --      --      --      --
  13       --      --      --      --      --      --      --      --      --
  14       --      --      --      --      --      --      --      --      --
Type <CR> to continue, Q<CR> to stop: 
M8850_NY                         System Rev: 02.01   Dec. 21, 2001 23:11:39 PST
MGX8850                                              Node Alarm: MAJOR

         XBAR CORE HISTORY ERROR COUNT :
 Fabric Slot No: 8        Xbar Plane No: 0 
Slot/   SFrame  SFrame   ACP    
Plane   Tick    Lock     Addr   
-----   ------  ------   ----   
   1        0       0       0 
   2        0       0       0 
   3        0       0       0 
   4       --      --      --
   5        0       0       0 
   6        0       0       0 
   7        0       0       0 
   8        0       0       0 
   9       --      --      --
  10       --      --      --
  11       --      --      --
  12       --      --      --
  13       --      --      --
  14       --      --      --

M8850_NY.7.PXM.a > 

The dspswalms display shows a critical crossbar core alarm related to slot 1. Run the dspdeverrhist command for physical slot then crossbar slot (see Syntax Description as needed). The alarm type is critical because the number of errors has exceeded the threshold for critical alarms. Note that plane 3 in slot 26 has not shut down because the errors are nether SFrame Tick nor SFrame lock errors—the critical failures that cause the whole plane to be unusable.

M8950_DC.7.PXM.a > dspswalms

             XBAR SWITCHING FABRIC ALARMS SUMMARY

            Xbar Core Alarm         Xbar Port Alarm     Xbar Slot B/W alarm
Slot No.  Critical Major Minor   Critical Major Minor  Critical Major Minor
-------   -------- ----- -----   -------- ----- -----  -------- ----- -----
  01           1      0     0        0      0     0        0      1     0
  02          --     --    --       --     --    --       --     --    --
  03          --     --    --       --     --    --       --     --    --
  04          --     --    --       --     --    --       --     --    --
  05           0      0     0        0      0     0        0      0     0
  06          --     --    --       --     --    --       --     --    --
  07           0      0     0        0      0     0        0      0     0
  08          --     --    --       --     --    --       --     --    --
  11          --     --    --       --     --    --       --     --    --
  12          --     --    --       --     --    --       --     --    --
  13          --     --    --       --     --    --       --     --    --
  14          --     --    --       --     --    --       --     --    --
  15          --     --    --       --     --    --       --     --    --
  16          --     --    --       --     --    --       --     --    --

M8950_DC.7.PXM.a >

Note that the screen display can accommodate only a finite number of errors without being distorted. 
Therefore, a K (for 1000) and M (for 1000000) multiplier may be necessary, as this example shows.

M8950_DC.7.PXM.a > dspdeverrhist XBARCORE -pslot 1
M8950_DC                         System Rev: 02.01   Dec. 21, 2001 22:34:30 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL

        XBAR CORE HISTORY ERROR COUNT FOR SLOT: 1
Fabric
Slot/   Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Plane   Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
 9/0        0       0       0       0       0       0       0       0       0 
 9/1        0       0       0       0       0       0       0       0       0 
 9/2        0       0       0       0       0       0       0       0       0 
 9/3        0       0       0       0       0       0       0       0       0 

10/0        0       0       0       0       0       0       0       0       0 
10/1        0       0       0       0       0       0       0       0       0 
10/2        0       0       0       0       0       0       0       0       0 
10/3        0       0       0       0       0       0       0       0       0 

        XBAR CORE HISTORY ERROR COUNT FOR SLOT: 1
Fabric
Slot/   SFrame  SFrame  ACP     
Plane   Tick    Lock    Addr    
-----   ------  ------  ----    
 9/0       0       0       0 
 9/1       0       0       0 
 9/2       0       0       0 
 9/3       0       0       0 

10/0       0       0       0 
10/1       0       0       0 
10/2       0       0       0 
10/3       0       0       0 



Type <CR> to continue, Q<CR> to stop: 
M8950_DC                         System Rev: 02.01   Dec. 21, 2001 22:34:30 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL


        XBAR CORE HISTORY ERROR COUNT FOR SLOT: 1
Fabric
Slot/   Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Plane   Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
25/0        0       0       0       0       0       0       0       0       0 
25/1        0       0       0       0       0       0       0       0       0 
25/2        0       0       0       0       0       0       0       0       0 
25/3        0       0       0       0       0       0       0       0       0 

26/0        0       0       0       0       0       0       0       0       0 
26/1        0       0       0       0       0       0       0       0       0 
26/2        0       0       0       0       0       0       0       0       0 
26/3    10275K 154132K 154132K      0  154132K 154132K      0       0       0 
 



Type <CR> to continue, Q<CR> to stop: 
M8950_DC                         System Rev: 02.01   Dec. 21, 2001 22:34:30 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL


        XBAR CORE HISTORY ERROR COUNT FOR SLOT: 1
Fabric
Slot/   SFrame  SFrame  ACP     
Plane   Tick    Lock    Addr    
-----   ------  ------  ----    
25/0       0       0       0 
25/1       0       0       0 
25/2       0       0       0 
25/3       0       0       0 

26/0       0       0       0 
26/1       0       0       0 
26/2       0       0       0 
26/3       0       0       0 

M8950_DC.7.PXM.a > dspdeverrhist XBARCORE -xslot 26 -pl 3
M8950_DC                         System Rev: 02.01   Dec. 21, 2001 22:36:56 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL

         XBAR CORE HISTORY ERROR COUNT :
 Fabric Slot No: 26        Xbar Plane No: 3 
        Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Slot    Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
   1    10276K 154154K 154154K      0  154154K 154154K      0       0       0 
   2       --      --      --      --      --      --      --      --      --
   3       --      --      --      --      --      --      --      --      --
   4       --      --      --      --      --      --      --      --      --
   5        0       0       0       0       0       0       0       0       0 
   6       --      --      --      --      --      --      --      --      --
   7        0       0       0       0       0       0       0       0       0 
   8       --      --      --      --      --      --      --      --      --
  11       --      --      --      --      --      --      --      --      --
  12       --      --      --      --      --      --      --      --      --
  13       --      --      --      --      --      --      --      --      --
  14       --      --      --      --      --      --      --      --      --
  15       --      --      --      --      --      --      --      --      --
  16       --      --      --      --      --      --      --      --      --

         XBAR CORE HISTORY ERROR COUNT :
 Fabric Slot No: 26        Xbar Plane No: 3 
Slot/   SFrame  SFrame   ACP    
Plane   Tick    Lock     Addr   
-----   ------  ------   ----   
   1        0       0       0 
   2       --      --      --
   3       --      --      --
   4       --      --      --
   5        0       0       0 
   6       --      --      --
   7        0       0       0 
   8       --      --      --
  11       --      --      --
  12       --      --      --
  13       --      --      --
  14       --      --      --
  15       --      --      --
  16       --      --      --

M8950_DC.7.PXM.a >

dspdiagcnf

Display Diagnostics Configuration

Displays the current diagnostics configuration, such as whether online or offline is enabled, the coverage time, starting time, and the days of the week (SMTWTFS) that the offline diagnostics runs.

Coverage indicates the length of time that the diagnostics will run as follows:

light = 5 minutes or less

medium = 30 minutes or less

full = 60 minutes or more


Note 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


Example

pop20one.7.PXM.a > dspdiagcnf
		Online   -------------- Offline -------------
Slot	Enable	Enable	Coverage	StartTime	SMTWTFS

1	enable	enable	full	10:30	-M-W-F-
2	disable	enable	full	22:00	-M-W-F-
3	enable	disable	medium	11:15	-M-W-F-
4	enable	disable	light	03:20	-M-W-F-
5	enable	disable	light	14:30	------S
6	disable	enable	full	12:00	-M-W-F-
7	disable	enable	light	18:00	------S
8	enable	enable	medium	05:00	-M-W-F-
9	enable	disable	light	04:30	-M-W-F-
10	enable	disable	full	22:00	------S
11	enable	disable	light	24:15	-M-W-F-
12	disable	enable	full	11:00	------S
13	enable	enable	light	13:15	-M-W-F-
14	enable	enable	medium	01:00	-M-W-F-
15	enable	enable	full	02:30	-M-W-F-
16	disable	disable	light	00:00	SMTWTFS
17	disable	disable	light	00:00	SMTWTFS
18	disable	disable	light	00:00	SMTWTFS
19	disable	disable	light	00:00	SMTWTFS
20	disable	disable	light	00:00	SMTWTFS
21	disable	disable	light	00:00	SMTWTFS
22	disable	disable	light	00:00	SMTWTFS
23	disable	disable	light	00:00	SMTWTFS
24	disable	disable	light	00:00	SMTWTFS
25	disable	disable	light	00:00	SMTWTFS
26	disable	disable	light	00:00	SMTWTFS
27	disable	disable	light	00:00	SMTWTFS
28	disable	disable	light	00:00	SMTWTFS
29	disable	disable	light	00:00	SMTWTFS
30	disable	disable	light	00:00	SMTWTFS
31	disable	disable	light	00:00	SMTWTFS
32	disable	disable	light	00:00	SMTWTFS

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 > dspdiagerr offline
Slot Date   Time  Message
---- ----   ----  -------
1    --     --
2    24-Aug 13:35 SAR send failed
3    --     --
4    --     --
5    --     --
6    --     --
7    --     --
8    --     --
9    --     --
10   --     --
11   --     --
12   --     --
13   18-Aug 03:24 HUMVEE IRQ test failed
14   --     --
15   --     --
16   --     --
17   --     --
18   --     --
19   --     --
20   --     --
21   --     --
22   --     --
23   --     --
24   --     --
25   --     --
26   --     --
27   --     --
28   --     --
29   --     --
30   --     --
31   --     --
32   --     --

dspdiagstat

Display Diagnostics Statistics

Displays the number of times that the diagnostics has run. The output shows the number of attempts and the number of failures for both offline and online diagnostics.


Note 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  = 0x00000000
online diag failed     = 0x00000000
offline diag attempted = 0x00000000
offline diag failed    = 0x00000000

dspdiagstatus

Display Diagnostics Status

Displays the diagnostics status for each card on the switch. The diagnostics statuses are:

Idle

Ready

Offline

Online


Note 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
Slot	State	Role

1	Ready	ACTIVE CARD ROLE
2	Ready	ACTIVE CARD ROLE
3	Offline	STANDBY CARD ROLE
4	Online	ACTIVE CARD ROLE
5	Ready	ACTIVE CARD ROLE
6	Offline	STANDBY CARD ROLE
7	Ready	ACTIVE CARD ROLE
8	Online	ACTIVE CARD ROLE
9	Idle	ACTIVE CARD ROLE
10	Ready	ACTIVE CARD ROLE
11	Online	ACTIVE CARD ROLE
12	Idle	ACTIVE CARD ROLE
13	Ready	ACTIVE CARD ROLE
14	Offline	STANDBY CARD ROLE
15	Idle	ACTIVE CARD ROLE
16	Idle	ACTIVE CARD ROLE
17	Idle	ACTIVE CARD ROLE
18	Idle	ACTIVE CARD ROLE
19	Idle	ACTIVE CARD ROLE
20	Idle	ACTIVE CARD ROLE
21	Idle	ACTIVE CARD ROLE
22	Idle	ACTIVE CARD ROLE
23	Idle	ACTIVE CARD ROLE
24	Idle	ACTIVE CARD ROLE
25	Idle	ACTIVE CARD ROLE
26	Idle	ACTIVE CARD ROLE
27	Idle	ACTIVE CARD ROLE
28	Idle	ACTIVE CARD ROLE
29	Idle	ACTIVE CARD ROLE
30	Idle	ACTIVE CARD ROLE
31	Idle	ACTIVE CARD ROLE
32	Idle	ACTIVE CARD ROLE

dspegrbucketcnt

Display Alarm Counters

Displays selected statistical counters for the specified 15 minute interval (intvl) for all lines and virtual interfaces on the card.

Cards on Which This Command Runs

AXSM-E

Syntax

dspegrbucketcnt <intvl>

Syntax Description

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.


Related Commands

dspingbucketcnt

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


Example

MGX8850.1.10.AXSME.a > dspegrbucketcnt 0
Line        Total Cells
               Received
------- ---------------
1.1                   0
1.2                   0
1.3                   0
1.4                   0
1.5                   0
1.6                   0
1.7                   0
1.8                   0
2.1                   0
2.2                   0
2.3                   0
2.4                   0

IfNum     Total Cells     Total Cells
             Received       Discarded
----- --------------- ---------------
1                   0               0
2                   0               0

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.

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 Fan Tray    1    >= 2000          RPM       0        Missing
 Bottom Fan Tray    2    >= 2000          RPM       0        Missing
 Bottom Fan Tray    3    >= 2000          RPM       0        Missing
 Bottom Fan Tray    4    >= 2000          RPM       0        Missing
 Bottom Fan Tray    5    >= 2000          RPM       0        Missing
 Bottom Fan Tray    6    >= 2000          RPM       0        Missing
 Bottom Fan Tray    7    >= 2000          RPM       0        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

 Power Supply       A1   none             None      none     Normal
 Power Supply       A2   none             None      none     Normal
 Power Supply       A3   none             None      none     Normal
 DC Voltage         A    42  to 54        VoltsDC   49       Normal

 Power Supply       B1   none             None      none     Missing
 Power Supply       B2   none             None      none     Missing
 Power Supply       B3   none             None      none     Missing
 DC Voltage         B    42  to 54        VoltsDC   0        Normal

 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       3498     Normal
 Top Fan Tray       5    >= 2000          RPM       3480     Normal 
Top Fan Tray       6    >= 2000          RPM       3570     Normal
 Top Fan Tray       7    >= 2000          RPM       3468     Normal
 Top Fan Tray       8    >= 2000          RPM       3366     Normal
 Top Fan Tray       9    >= 2000          RPM       3444     Normal

 Bottom Fan Tray    1    >= 2000          RPM       0        Missing
 Bottom Fan Tray    2    >= 2000          RPM       0        Missing
 Bottom Fan Tray    3    >= 2000          RPM       0        Missing
 Bottom Fan Tray    4    >= 2000          RPM       0        Missing
 Bottom Fan Tray    5    >= 2000          RPM       0        Missing
 Bottom Fan Tray    6    >= 2000          RPM       0        Missing
 Bottom Fan Tray    7    >= 2000          RPM       0        Missing
 Bottom Fan Tray    8    >= 2000          RPM       0        Missing
 Bottom Fan Tray    9    >= 2000          RPM       0        Missing

 +5V Input             4.850^ to 5.150^   VoltsDC   5.017    Informational
 +3.3V Input           3.200^ to 3.400^   VoltsDC   3.259    Informational
+2.5V Input           2.425^ to 2.575^   VoltsDC   2.440    Informational
 Calibration VDC        0x7e^ to 0x82^    Other     0x80     Informational

Display the state of the fans. The display shows that upper and lower fan trays exist in the system—a requirement of the MGX 8950 node.

Jupiter_Lower.7.PXM.a > dspenvalms fan
Jupiter_Lower                    System Rev: 02.00   Aug. 06, 2000 22:36:35 GMT
JUPITER                                              Node Alarm: NONE
ENVIRONMENTAL ALARM STATE INFO   ^Notification Disabled
   Alarm Type      Unit   Threshold      DataType   Value       State
 ----------------  ---- --------------   -------- ---------- -------------
 Top Fan Tray       1    >= 2000          RPM       3432     Normal
 Top Fan Tray       2    >= 2000          RPM       3516     Normal
 Top Fan Tray       3    >= 2000          RPM       3552     Normal
 Top Fan Tray       4    >= 2000          RPM       3402     Normal
 Top Fan Tray       5    >= 2000          RPM       3558     Normal
 Top Fan Tray       6    >= 2000          RPM       3564     Normal
 Top Fan Tray       7    >= 2000          RPM       3618     Normal
 Top Fan Tray       8    >= 2000          RPM       3522     Normal
 Top Fan Tray       9    >= 2000          RPM       3516     Normal

 Bottom Fan Tray    1    >= 2000          RPM       3576     Normal
 Bottom Fan Tray    2    >= 2000          RPM       3558     Normal
 Bottom Fan Tray    3    >= 2000          RPM       3594     Normal
 Bottom Fan Tray    4    >= 2000          RPM       3570     Normal
 Bottom Fan Tray    5    >= 2000          RPM       3492     Normal
 Bottom Fan Tray    6    >= 2000          RPM       3600     Normal
 Bottom Fan Tray    7    >= 2000          RPM       3504     Normal

Type <CR> to continue, Q<CR> to stop: 

dsperr

Display Error

Display error message files. The dsperr command is primarily a debug command. Because it displays tasks and system calls, the information is more suitable to developers or others who can use information that is internal to the switch rather than applicable to the network. The information may also be useful to Cisco support personnel.

Cards on Which This Command Runs

PXM45

Syntax

dsperr <-s1 slot> [-en <Error#>] [ -tr {P | L | N}]

Syntax Description

-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

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()

--------------

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
----------------------------------------------------------------------------- 

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
-----------------------------------------------------------------------------

dspilmicnt

Display ILMI Counters

Displays the ILMI counters for a particular resource partition on a particular logical port.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

dspilmicnt <ifNum> <partId>

Syntax Description

ifNum

The ranges for logical interface (or AXSM port) number are as follows:

AXSM: 1-60

AXSM-E: 1-32

partId

The ranges for partition identifier are as follows:

AXSM: 1-5

AXSM-E: 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:                 1
  SNMPPDUsReceived:         0
  Get RequestsReceived:     0
  GetNextRequestsReceived:  0
  SetRequestsReceived:      0
  TrapReceived:             0
  GetResponseReceived       0
  GetResponseTransmitted:   0
  GetRequestTransmitted:    0
  TrapsTransmitted:         0
  InvalidPDUReceived:       0
  Asn1ParseError:           0
  NoSuchNameError:          0
  TooBigError:              0

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, AXSM-E

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 

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                Alarm Status        : Clear
  Loopback               : NoLoop            APS enabled         : Disable
  Frame Scrambling       : Enable            Number of ports     : 1
  Xmt Clock source       : localTiming       Number of partitions: 1
  Line Type              : sonetSts12c       Number of SPVC      : 0
  Medium Type(SONET/SDH) : SONET             Number of SVC       : 4
  Medium Time Elapsed    : 506223
  Medium Valid Intervals : 96
  Medium Line Type       : ShortSMF 

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-E

AXSM Syntax

dsplncnt <bay.line>

AXSM-E Syntax

dsplncnt <bay.line> <intvl>

Syntax Description

bay

Bay number: 1 or 2

line

Line number:

For OC12: 1

For OC3: 1-4

T3, E3: 1-8

intvl

AXSM-E
only

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.


Related Commands

clrlncnt

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


Example

Display example for AXSM-E.

MGX8850.5.AXSME.a > dsplncnt 1.1 1
Line              : 1.1
Interval          : 1

                         Ingress           Egress
Rcv CLP0 Cells         : 180                180
Rcv CLP1 Cells         : 0                  0
Valid OAM Cells        : 0                  0
Err OAM Cells          : 0                  0
Rcv Valid RM Cells     : 0                  0
VpiVciErr Cells        : 0
Rcv Idle Cells         : 317903602
Ing Gfc Cells          : 0
Ing LastUnknVpi        : 0
Ing LastUnknVci        : 0
Discard HecErr Cells   : 0
Corrected HecErr Cells : 0

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) 

dsplnpmbucketcnt

Display Line Performance Bucket Counters

Displays the line specific performance monitoring interval counters.

Cards on Which This Command Runs

AXSM-E

Syntax

dsplnpmbucketcnt <bay.line> <intvl>

Syntax Description

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

dspalmcnt

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


Example

MGX8850.1.10.AXSME.a > dsplnpmbucketcnt 2.1 96
Line Number      : 2.1
Interval Number  : 96
Section PM: 
----------- 
ESs   : 1125
SESs  : 1125
SEFSs : 1125
CVs   : 43199586
 
Line PM:
--------
       Near End           Far End
ESs  : 1125               1125
SESs : 1125               1125
CVs  : 43199586           165598436
UASs : 1125               1125
 
Path PM:
--------
       Near End           Far End
ESs  : 1125               1125
SESs : 1125               1125
CVs : 14399862            0
UASs : 1125               1125

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, AXSM-E

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 

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

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.

-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


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

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 many log files exist. To view the contents of log file 41, for example, you would enter dsplog -log error041.log. See also the description of the dsplog command.

M8850_SF.7.PXM.a > dsplogs

Current Event log number: 47
Event log 47:  C:/LOG/event47.log
   starting timestamp: 11/19/2001-18:24:39
Event log 46:  C:/LOG/event46.log
   starting timestamp: 11/17/2001-02:26:33
Event log 45:  C:/LOG/event45.log
   starting timestamp: 11/15/2001-02:25:48
Event log 44:  C:/LOG/event44.log
   starting timestamp: 11/12/2001-18:35:01
Event log 43:  C:/LOG/event43.log
   starting timestamp: 11/10/2001-02:30:37
Event log 42:  C:/LOG/event42.log
   starting timestamp: 11/07/2001-16:44:35
Event log 41:  C:/LOG/event41.log
   starting timestamp: 11/06/2001-20:05:54
Event log 40:  C:/LOG/event40.log
   starting timestamp: 11/05/2001-13:05:23
Event log 39:  C:/LOG/event39.log
   starting timestamp: 11/04/2001-03:37:16
Event log 38:  C:/LOG/event38.log
   starting timestamp: 11/02/2001-16:47:52
Event log 37:  C:/LOG/event37.log

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.

dspswalms shows alarms related to the switching fabric on the PXM45 or XM60.

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 so 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 a sufficient accumulation of lower-level alarms results in a higher-severity 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


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                     Critical        Major          Minor
----------                     --------       -------        -------
Clock Alarms                         0             0              0
Switching Alarms                     0             0              0
Environment Alarms                   0             0              0
Card Alarms                          0             2              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  Critical   Major     Minor
----  --------  -------   -------
 1          0        0         0
 2          0        0         0
 3          0        0         0
 4          0        0         0
 5          0        0         0
 6          0        0         0
 7          0        0         0
 8          0        2         0
 9          0        0         0
10          0        0         0
11          0        0         0
12          0        0         0
13          0        0         0
14          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                     Critical        Major          Minor
----------                     --------       -------        -------
Hardware Alarm                       0             0              0
Card State Alarm                     0             1              0
Disk Alarm                           0             1              0
Line Alarm                           0             0              0
Port Alarm                           0             0              0
Feeder Alarm                         0             0              0
Channel Alarm                        0             0              0 

Run dspcds to see general information about the cards, then use dspcd to acquire details on the state of a particular card.

M8850_NY.7.PXM.a > dspcds
M8850_NY                         System Rev: 02.01   Dec. 22, 2001 22:50:20 PST
Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: -8
                                                     Node Alarm: MAJOR
Card  Front/Back          Card           Alarm      Redundant   Redundancy     
Slot  Card State          Type           Status     Slot        Type   
---   ----------          --------       --------   -------     -----  

01    Active/Active       AXSM_4OC12     NONE       02          PRIMARY SLOT
02    Standby/Active      AXSM_4OC12     NONE       01          SECONDARY SLOT
03    Active-U/Active     AXSM_4OC12     NONE       NA          NO REDUNDANCY
04    Empty               ---            ---        ---         ---    
05    Active/Empty Resv   AXSME_2OC12    MAJOR      NA          NO REDUNDANCY
06    Active/Mismatch     AXSM_16OC3_B   MINOR      NA          NO REDUNDANCY
07    Active/Active       PXM45          NONE       08          PRIMARY SLOT
08    Standby/Active      PXM45          NONE       07          SECONDARY SLOT
09    Active/Active       RPM_PR         NONE       NA          NO REDUNDANCY
10    Empty               ---            ---        ---         ---    
11    Empty               ---            ---        ---         ---    
12    Empty               ---            ---        ---         ---    
13    Empty               ---            ---        ---         ---    
14    Empty               ---            ---        ---         ---    

M8850_NY.7.PXM.a > 

dspingbucketcnt

Display Alarm Counters

Displays selected statistical counters for the specified 15 minute interval (intvl) for all the lines on card.

Cards on Which This Command Runs

AXSM-E

Syntax

dspingbucketcnt <intvl>

Syntax Description

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 is the oldest 15-minute interval.


Related Commands

dspegrbucketcnt

Attributes

Log: no

State: active, standby

Privilege: ANYUSER


Example

MGX8850.1.10.AXSME.a > dspingbucketcnt 
Line        Total Cells     Total Cells
               Received       Discarded
------- --------------- ---------------
1.1                   0               0
1.2                   0               0
1.3                   0               0
1.4                   0               0
1.5                   0               0
1.6                   0               0
1.7                   0               0
1.8                   0               0
2.1                   0               0
2.2                   0               0
2.3                   0               0
2.4                   0               0

dsplnbucketcnt

Display Line Bucket Counters—display the contents of cell counters.

The dsplnbucketcnt command lets you display counters for various cell-related statistics on a line for the current bucket interval. For bucket statistics, line statistics are collected for a period of 15 minutes (bucket interval), then a statistics file is generated at the end of this bucket interval. This file is then uploaded to CWM. The bucket counters are cleared at the start of the next bucket interval.

The dsplnbucketcnt command displays counters for the following:

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


Note Some counters apply to both the ingress direction and the egress direction. Some apply to only the ingress direction. See the output in the Example section.


Cards on Which This Command Runs

AXSM

Syntax

dsplnbucketcnt <bay.line>

Syntax Description

bay

Bay number: 1 or 2

line

Line number:

For OC12: 1

For OC3: 1-4

T3, E3: 1-8


Related Commands

dsplncnt

Attributes

Log: no

State: active

Privilege: ANYUSER


Example

Display the bucket cell counters for line 1 in bay 1.

U2Golden.9.AXSM.a > dsplnbucketcnt 1.1
                     Ingress           Egress
Rcv CLP0 Cells     :0                  216
Rcv CLP1 Cells     :0                  0
Valid OAM Cells    :0                  180
Err OAM Cells      :0                  0
VpiVciErr Cells    :0                  0
Ing Gfc Cells          :0
Ing LastUnknVpi        :0
Ing LastUnknVci        :0
Discard HecErr Cells   :0
Corrected HecErr Cells :0
Discard Upc CLP0 Cells :0
Discard Upc Total Cells:0
Total Upc NonComp Cells:0

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

Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.


Related Commands

cnfpnportloscallrel

Attributes

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

dspportbucketcnt

Display Port Bucket Counters—display the contents of cell counters.

The dspportbucketcnt command lets you display counters for various cell-related statistics on a port for the current bucket interval. For bucket statistics, port statistics are collected for a period of 15 minutes (bucket interval), then a statistics file is generated at the end of this bucket interval. This file is then uploaded to CWM. The bucket counters are cleared at the start of the next bucket interval and continue to accumulate values until the end of this interval. The dspportbucketcnt command shows the (Ingress & Egress) counters for the following:

Arrival CLP0 cells

Arrival CLP1 cells

CLP0 discard cells

CLP1 discard cells

Departure CLP0 cells

Departure CLP1 cells

Cards on Which This Command Runs

AXSM

Syntax

dspportbucketcnt <ifNum>

Syntax Description

ifNum

Logical port number. For AXSM, the range 1-60.


Related Commands

dspportcnt

Attributes

Log: no

State: active

Privilege: ANYUSER


Examples

Display port bucket counters on logical port (ifNum) 1 of the current AXSM.

U2Golden.9.AXSM.a > dspportbucketcnt 11
                  Ingress           Egress
Rcv Clp0 Cells  :0                  216
Rcv Clp1 Cells  :0                  0
Clp0 Disc Cells :0                  0
Clp1 Disc  Cells:0                  0
Xmt Clp0  Cells :0                  216
Xmt Clp1  Cells :0                  0

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-E

AXSM Syntax

dspportcnt <ifNum>

AXSM-E Syntax

dspportcnt <ifNum> <intvl>

Syntax Description

ifNum

Logical port number. The range depends on the card.

For AXSM, the range 1-60.

For AXSM-E, the range is 1-32.

intvl

(AXSM-E ONLY) 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.


Related Commands

dspports, dspport, cnfport, dspcds

Attributes

Log: no log

State: active, standby

Privilege: ANYUSER


Examples

Display port counters on logical port (ifNum) 1 of the current AXSM.

MGX8850.1.AXSM.a > dspportcnt 1

Cleared at      : 06/27/2001 17:43:13 
Current time    : 06/27/2001 17:44:43 
Elapsed time    : 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    Egr: 0000000000000000000000            0            0
 Arrival CLP1    Egr: 0000000000000000000000            0            0
 Ar CLP0 discard Egr: 0000000000000000000000            0            0
 Ar CLP1 discard Egr: 0000000000000000000000            0            0
 Departure CLP0  Egr: 0000000000000000000000            0            0
 Departure CLP1  Egr: 0000000000000000000000            0            0

Display port counters on logical port (ifNum) 1 of the current AXSM.

MGX8850.1.10.AXSME.a > dspportcnt  1 1
Interface Num              : 1
Interval  Num              : 1
Egr Rcv Clp0 Cells         : 0
Egr Rcv Clp1 Cells         : 0
Egr Clp0 Disc Cells        : 0
Egr Clp1 Disc  Cells       : 0
Egr Xmt Clp0  Cells        : 0
Egr Xmt Clp1  Cells        : 0
Egr Rcv OAM  Cells         : 0
Egr Rcv RM Cells           : 0
Egr Xmt EFCI Cells         : 0
Egr Rcv EFCI Cells         : 0
Egr Xmt OAM Cells          : 0

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, AXSM-E

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           %

dspswalms

Display Switching Alarms—displays alarms for the switching fabrics.

The dspswalms command helps you isolate the cause of switch fabric alarms. The display shows whether the alarm severity is critical, major, or minor. It also lists information by slot and by alarm type. (See Example section.)

The three alarm types are:

XBAR CORE indicates whether the errors on the links on the fabric crossed the alarm thresholds.

XBAR PORT indicates whether the errors on the crossbar ports (Humvee or any equivalent) on a service module crossed the alarm thresholds.

XBAR SLOT BANDWIDTH alarm is raised based on the number of crossbar links that are up for a service module.


Note Currently, XBAR PORT and XBAR SLOT BANDWIDTH are not implemented.


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 so 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 a sufficient accumulation of lower-level alarms results in a higher-severity alarm.

Usage Guidelines for dspswalms

After determining the error type and the related slot, you can use the crossbar troubleshooting commands to isolate the problem further.

The following is a top-down sequence of alarm-related commands that lead to isolating possible faults in the switch fabric:

1. dspndalms indicates the general region of the problem and can indicate the switching fabric.

2. dspswalms shows the error type, alarm severity, and related slot.

3. dspdevalms shows a recent crossbar error list by physical slot or by switching slot.

4. dspdeverrhist shows total crossbar error history since the last power-up or card reset by physical slot or by switching slot.

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 or XM60

Buffer circuitry on the module serviced by the switch planes

The dspswalms display shows how many errors have occurred and generally where the errors have occurred. For purposes of troubleshooting the switch, you can decide which card to replace by using the dspdeverr, dspdevalms, dspxbarplanealms, and dspxbarslotbwalms commands. These commands can help you isolate the problem to a particular switch ASIC, the receiving card, or the link between them. (In the context of the switch ASICs, the hardware path between the switch card and the recipient card's bus transceiver is called a link.) The crossbar troubleshooting commands can be either plane-centric or slot-centric. Plane-centric is from the switch ASICs outwards. Slot-centric is from a slot toward a switch ASIC. The reference point in relation to card slots is important for fault isolation. For example, a plane-centric command sequence is:

1. dspndalms

2. dspswalms

3. dspxbarplanealms

4. dspdevalms

Cards on Which This Command Runs

PXM45

Syntax

dspswalms

Syntax Description

This command takes no parameters.

Related Commands

dspndalms, dspdeverr, dspdeverrhist, dspdevalms

Attributes

Log: no log

State: active

Privilege: ANYUSER


Examples

Display switching alarms. Where no card resides, the display shows dashes. No errors have occurred.

M8850_NY.7.PXM.a > dspswalms

             XBAR SWITCHING FABRIC ALARMS SUMMARY

            Xbar Core Alarm         Xbar Port Alarm     Xbar Slot B/W alarm
Slot No.  Critical Major Minor   Critical Major Minor  Critical Major Minor
-------   -------- ----- -----   -------- ----- -----  -------- ----- -----
  01           0      0     0        0      0     0        0      0     0
  02           0      0     0        0      0     0        0      0     0
  03           0      0     0        0      0     0        0      0     0
  04          --     --    --       --     --    --       --     --    --
  05           0      0     0        0      0     0        0      0     0
  06           0      0     0        0      0     0        0      0     0
  07           0      0     0        0      0     0        0      0     0
  08           0      0     0        0      0     0        0      0     0
  09          --     --    --       --     --    --       --     --    --
  10          --     --    --       --     --    --       --     --    --
  11          --     --    --       --     --    --       --     --    --
  12          --     --    --       --     --    --       --     --    --
  13          --     --    --       --     --    --       --     --    --
  14          --     --    --       --     --    --       --     --    --

M8850_NY.7.PXM.a >


M8950_DC.7.PXM.a > dspndalms
Node Alarm Summary

Alarm Type                     Critical        Major          Minor
----------                     --------       -------        -------
Clock Alarms                         0             1              0
Switching Alarms                     1             1              0
Environment Alarms                   0             0              0
Card Alarms                          0             2              0

M8950_DC.7.PXM.a >
M8950_DC.7.PXM.a > dspswalms

             XBAR SWITCHING FABRIC ALARMS SUMMARY

            Xbar Core Alarm         Xbar Port Alarm     Xbar Slot B/W alarm
Slot No.  Critical Major Minor   Critical Major Minor  Critical Major Minor
-------   -------- ----- -----   -------- ----- -----  -------- ----- -----
  01           1      0     0        0      0     0        0      1     0
  02          --     --    --       --     --    --       --     --    --
  03          --     --    --       --     --    --       --     --    --
  04          --     --    --       --     --    --       --     --    --
  05           0      0     0        0      0     0        0      0     0
  06          --     --    --       --     --    --       --     --    --
  07           0      0     0        0      0     0        0      0     0
  08          --     --    --       --     --    --       --     --    --
  11          --     --    --       --     --    --       --     --    --
  12          --     --    --       --     --    --       --     --    --
  13          --     --    --       --     --    --       --     --    --
  14          --     --    --       --     --    --       --     --    --
  15          --     --    --       --     --    --       --     --    --
  16          --     --    --       --     --    --       --     --    --

M8950_DC.7.PXM.a > 
M8950_DC.7.PXM.a > dspxbarplanealms
M8950_DC                         System Rev: 02.01   Dec. 15, 2001 17:55:13 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL

      XBAR PLANE ALARM INFO
XbarSlot  Xbar Core    Xbar Plane 
/plane    Alarm        Based Alarm
------    -----        -----------
 9/0      --           --      
 9/1      --           --      
 9/2      --           --      
 9/3      --           --      

10/0      --           --      
10/1      --           --      
10/2      --           --      
10/3      --           --      

25/0      --           --      
25/1      --           --      
25/2      --           --      
25/3      --           --      

26/0      --           --      
26/1      --           --      
26/2      --           --      
26/3      Critical     --      

M8950_DC.7.PXM.a > dspxbarslotbwalms
M8950_DC                         System Rev: 02.01   Dec. 15, 2001 17:55:26 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL

                XBAR SLOT BANDWIDTH ALARM INFO SUMMARY

LoadSharing < Enabled >                  AutoShutDown < Enabled > 
Slot   Xbar Slot    Required no.   Available no.    Operational no. 
No.    Bw Alarm     of Planes      of Planes        of Planes       
----   ---------    -----------    ------------     --------------  
 01      Major           3              8                 7
 02        --           --             --                -- 
 03        --           --             --                -- 
 04        --           --             --                -- 
 05      None            3              8                 8
 06        --           --             --                -- 
 07      None            1              4                 4
 08        --           --             --                -- 
 12        --           --             --                -- 
 13        --           --             --                -- 
 14        --           --             --                -- 
 15        --           --             --                -- 
 16        --           --             --                -- 

M8950_DC.7.PXM.a > 
M8950_DC.7.PXM.a > dspdeverr XBARCORE -pslot *
M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:02:14 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL

         XBAR CORE CURRENT ERROR COUNTERS SUMMARY
                   Fabric Slot / Plane
Slot     9/0     9/1     9/2     9/3      10/0    10/1    10/2    10/3
-----  ------  ------  ------  ------    ------  ------  ------  ------
 01        0       0       0       0         0       0       0       0 
 02       --      --      --      --        --      --      --      -- 
 03       --      --      --      --        --      --      --      -- 
 04       --      --      --      --        --      --      --      -- 
 05        0       0       0       0         0       0       0       0 
 06       --      --      --      --        --      --      --      -- 
 07        0       0       0       0         0       0       0       0 
 08       --      --      --      --        --      --      --      -- 
 11       --      --      --      --        --      --      --      -- 
 12       --      --      --      --        --      --      --      -- 
 13       --      --      --      --        --      --      --      -- 
 14       --      --      --      --        --      --      --      -- 
 15       --      --      --      --        --      --      --      -- 
 16       --      --      --      --        --      --      --      -- 


M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:02:14 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL
         XBAR CORE CURRENT ERROR COUNTERS SUMMARY
                   Fabric Slot / Plane
Slot    25/0    25/1    25/2    25/3      26/0    26/1    26/2    26/3
-----  ------  ------  ------  ------    ------  ------  ------  ------
 01        0       0       0       0         0       0       0   13420 
 02       --      --      --      --        --      --      --      -- 
 03       --      --      --      --        --      --      --      -- 
 04       --      --      --      --        --      --      --      -- 
 05        0       0       0       0         0       0       0       0 
 06       --      --      --      --        --      --      --      -- 
 07        0       0       0       0         0       0       0       0 
 08       --      --      --      --        --      --      --      -- 
 11       --      --      --      --        --      --      --      -- 
 12       --      --      --      --        --      --      --      -- 
 13       --      --      --      --        --      --      --      -- 
 14       --      --      --      --        --      --      --      -- 
 15       --      --      --      --        --      --      --      -- 
 16       --      --      --      --        --      --      --      -- 

M8950_DC.7.PXM.a > dspdeverr XBARCORE -pslot 1
M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:06:02 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL

        XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1
Fabric
Slot/   Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Plane   Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
 9/0        0       0       0       0       0       0       0       0       0 
 9/1        0       0       0       0       0       0       0       0       0 
 9/2        0       0       0       0       0       0       0       0       0 
 9/3        0       0       0       0       0       0       0       0       0 

10/0        0       0       0       0       0       0       0       0       0 
10/1        0       0       0       0       0       0       0       0       0 
10/2        0       0       0       0       0       0       0       0       0 
10/3        0       0       0       0       0       0       0       0       0 
 


M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:06:02 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL


        XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1
Fabric
Slot/   SFrame  SFrame  ACP     
Plane   Tick    Lock    Addr    
-----   ------  ------  ----    
 9/0       0       0       0 
 9/1       0       0       0 
 9/2       0       0       0 
 9/3       0       0       0 

10/0       0       0       0 
10/1       0       0       0 
10/2       0       0       0 
10/3       0       0       0 
 


M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:06:02 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL


        XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1
Fabric
Slot/   Loss    Rx      Rx      Xmit    Hdr     Pload   Slot    Slot    BP      
Plane   Sync    Cv      Disp    Par     CRC     CRC     Remap   Recur   Par     
------  ------  ------  ------  ------  ------  ------  ------  ------  ------  
25/0        0       0       0       0       0       0       0       0       0 
25/1        0       0       0       0       0       0       0       0       0 
25/2        0       0       0       0       0       0       0       0       0 
25/3        0       0       0       0       0       0       0       0       0 

26/0        0       0       0       0       0       0       0       0       0 
26/1        0       0       0       0       0       0       0       0       0 
26/2        0       0       0       0       0       0       0       0       0 
26/3      220    3300    3300       0    3300    3300       0       0       0 
 


Type <CR> to continue, Q<CR> to stop: 
M8950_DC                         System Rev: 02.01   Dec. 15, 2001 18:06:02 PST
MGX8950 (JBP-2)                                      Node Alarm: CRITICAL