|
|
This chapter describes commands that directly or indirectly facilitate troubleshooting. They include commands for viewing and clearing alarms and statistics. The chapter begins with a description of the CLI, the PNNI port identifier, and various elements of the AXSM.
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 >]
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.
The model number of an AXSM identifies the line speed, line count, and number of bays (see Table 9-1.) Note that the number of lines applies to an individual back card, so the total number of lines supported by the front card equals the highest line number times the number of bays. The OC-48 card AXSM-1-2488 has the lowest number of lines—one. The highest number of lines exist on the AXSM-16-155 and AXSM-16-T3E3—16, as the name indicates.
The MGX 8850 node use the concept of a bay. The bay refers to the upper or lower location of a single-height card. (The switch has a double-height card cage, so a single-height back card necessarily occupies either an upper or lower position.)
The T3/E3, OC-3, and OC-12 versions of the AXSM can have two back cards, one in bay 1 (upper location of the back slot) and the second in bay 2 (lower slot). The MGX-AXSM-1-2488 (OC-48 AXSM) can have a back card in bay 1 only. For further descriptions and illustrations of the card sets, refer to Cisco MGX 8850 Hardware Installation, Rel 2.0.
| 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 or E3 | 1-8 | 1-2 |
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 Software Configuration Guide, 2.0.
 |
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 Software Configuration Guide, 2.0 for more details of this sequence. |
The AXSM items that you identify for addressing purposes are:
A logical port on an AXSM (and its CLI) always uses the label ifNum. For a UNI and NNI interface, a one-to-one correspondence exists between a logical port and a physical line. For virtual trunks, you can configure multiple ports for a line.
The maximum number of logical ports on an AXSM is 60 regardless of the AXSM model or the number of AXSM back cards. The range for ifNum is 1-60, also regardless of the whether the interface type is UNI. NNI, or VNNI.
The elements of a port in the PNNI protocol are as follows:
The PNNI port identifier (portid) appears on only the PXM45 CLI. Throughout this manual, portid refers the following format:
[shelf.]slot[:subslot].port[:subport]
The portid consists of a series of mandatory and optional elements. Note the period or colon associated with each optional element inside the square brackets. For the correspondence between a PNNI port and the AXSM elements, see Table 9-2.
| PNNI port | AXSM |
|---|---|
Shelf | N/A |
Slot | Slot |
Subslot | Bay (for back cards |
Port | Line |
Subport | Logical port (ifNum) |
An example of a PNNI port identifier is 1:2.1:3. This portid corresponds to slot 1, bay 2, line 1, and logical port 3 on an AXSM.
Add Line Loop
Specifies a loopback state for a line on the current service module.
AXSM
addlnloop
<-ds3 | -sonet bay.line>
<-lpb loopback type>
|
Note The keyword ds3 applies to both T3 and E3 line types. |
|
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. |
-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. |
-lpb | Keyword that 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 |
dellnloop
Log: log | State: active | Privilege: GROUP1 |
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 execute this command because it clears all configuration files on the PXM45. After clrallcnf, you need to reconfigure the switch. |
PXM45
clrallcnf
None
Log: log | State: active | Privilege: SERVICE_GP |
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)?
Clear Alarm Counters
Clear all the alarm counters and statistics on the specified line on the current card. All counters are reset to 0. The system does not display a response unless it detects a syntax error.
AXSM
clralmcnt
<bay.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. |
dspalmcnt, clralmcnts
Log: nolog | State: active, standby | Privilege: SUPER_GP |
Clear all the alarm counters and statistics for line 1 on the current card. The -ds3 indicates either a T3 or E3 line.
node1.1.2.AXSM.a > clralmcnt -ds3 1
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.
AXSM
clrcdcnt
This command takes no parameters.
dspcdcnt, dspchancnt
Log: nolog | State: active, standby | Privilege: SUPER_GP |
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.
PXM45
clrerr
After you enter clrerr, the system prompts you to confirm that you want to clear all error log files.
dsperr
Log: nolog | State: active, standby | Privilege: SUPER_GP |
Clear all error log files on the PXM45.
pinnacle.7.PXM.a > clrerr Do you want to clear error log file (Yes/No)?
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 output of dspchancnt. Once you execute clrchancnt, the previous counter contents are unrecoverable.
AXSM
clrchancnt <ifNum>
<vpi>
<vci>
ifNum | The logical port number in the range 1-60. |
vpi | The VPI has the range 0-255 for a UNI or 0-4095 for a UNI or VNNI. |
vci | The VCI in the range 1-65535. |
dspchancnt
Log: log | State: active | Privilege: SUPER_GP |
Clear all the connection counters for connection 100.1000 on logical port 3.
node1.1.AXSM.a > clrchancnt 3 100 1000
Clear ILMI Counters
Clears the ILMI statistics for a partition and logical port on a service module.
AXSM
clrilmicnt <ifNum> <partId>
ifNum | Logical port in the range 1-60. |
partId | Number of the partition in the range 1-20. |
dspilmicnt, dspilmi, dspilmis
Log: nolog | State: active, standby | Privilege: SUPER_GP |
Clear the ILMI statistics on the AXSM.
wilco.1.AXSM.a > clrilmicnt
Clear the Counters for a Line
Clear various cell and connection-related counters for a line. See dsplncnt for content descriptions. The system returns a response only if an error occurs.
PXM45
clrlncnt
<bay.line>
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. |
dsplncnt
Log: log | State: active | Privilege: SUPER_GP |
Clear the line counters for line 1 in bay 1 on the current AXSM.
wilco.1.AXSM.a > clrlncnt 1.1
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.
PXM45
clrlog [-log <log>]
-log | Keyword that specifies the type of log file (log) to clear. See dsplog for a list of the types of logs files. |
dsplog, dsplogs
Log: log | State: active, standby | Privilege: SUPER_GP |
Clear all event log files on the PXM45 card.
wilco.7.PXM.a > clrlog
Clear Port Counters
Clear counter values on a specific logical port.
AXSM
clrportcnt <ifNum>
ifNum | The logical port number. On the AXSM, the range is 1-60. |
clrportcnts, dspportcnt
Log: nolog | State: active, standby | Privilege: SUPER_GP |
Clear all the port counters on port 1.
flyers01.17.AXSM.a > clrportcnt 1
Configure Alarm
Configures statistical alarm thresholds for a line. The configurable items are defined in RFC 2258 for SONET and PLCP and in RFC 2496 for DS3 and E3. The items that constitute a configuration are:
The format of each keyword identifies the criteria. It contains the tested layer (line, and so on), the type of threshold (errored seconds, code violations, and so on), and the test period of 15 minutes or 24 hours. For example, -lnes15 identifies the number of errored seconds on a line during any 15 minute period.
AXSM
The required parameters are the line type the line identifier in the form 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.
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 parameter descriptions 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 | The logical port number in the range 1-60. |
alarm severity | A number to identify alarm severity: 1=minor, and 2=major. |
thresholds | The number of instances of whatever the keyword identifies. The range for each threshold is 1-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. |
-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> | Code violations during a 15-minute period. |
-seccv24 <UAS24Hr> | Code violations during a 24-hour period. |
-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. |
-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. |
-cvt24 <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. |
-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. |
-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. |
-sefs24 <SEFS24Hr> | Severely errored frame seconds during a 24-hour period. |
-duas15 <UAS15min> | Unavailable seconds during a 15-minute period. |
-duast24 <UAS24Hr> | Unavailable seconds during a 24-hour period. |
-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. |
dspalmcnf
Log: log | State: active | Privilege: GROUP1 |
Display the alarm configuration for line 2 of the upper back card (bay 2). The type of SONET alarm is "line."
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
Display the alarm configuration for line 1 in bay 1. The type of SONET alarm is "section."
node4.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
Configure SPVC Log
Enable or disable the SPVC log.
PXM45
cnfspvclog
<enable | disable>
enable | disable | Keyword that either enables or disables the SPVC log. The default is disabled. |
AXSM
dspspvclog
Log: nolog | State: active, standby | Privilege: SERVICE_GP |
Enable the SPVC log.
Unknown.8.PXM.a > cnfspvclog enable
Call Control Operations: Connection Trace
Trace an established connection and display the result.
conntrace <portid> callref [EndPtRef]
portid | See the section, "PNNI Format" at the front of this chapter. |
callref | Call reference for the call. |
EndPtRef | Endpoint reference for a p2mp call. If no endpoint reference is specified, this is a p2p call. |
pathtraceport, pathracenode, pathtraceie
Log: log | State: active | Privilege: SUPER_GP |
Result:Succ/Fail Reason: " Desc" InterfaceId: "--" EndptRef: "--" Originating Interface VPI: " --" Originating Interface VCI: " --" Originating Interface CallRef: " --" NodeId Egress Port Vpi Vci CallRef PhysPortid XXXX ZZZZ aaa bbb cccc eeee XXXX ZZZZ aaa bbb cccc eeee Terminating Interface VPI: " --" Terminating Interface VCI: " --" Terminating Interface CallRef: " --"
Delete Line Loop
Use the dellnloop command to remove a line loopback state for a line.
|
Note The keyword ds3 applies to both T3 and E3 line types. |
AXSM
dellnloop
<-ds3 | -sonet> <bay.line>
-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. |
addlnloop
Log: log | State: active | Privilege: GROUP1 |
Down Connection
Temporarily deactivates (or "downs") so you can modify or troubleshoot it. This operation applies to only an SPVC. To reactivate the connection, use upcon.
AXSM
dncon
<ifNum>
<vpi>
<vci>
ifNum | The logical port (or logical interface) number. On the AXSM, the range is 1-60. |
vpi | Virtual path identifier in the range 1-255. |
vci | For a virtual connection (VCC), the VCI range is 0-65535. For a virtual path connection (VPC), the VCI is always 0. |
upcon
Log: nolog | State: active | Privilege: GROUP1 |
Down Line
Use dnln to de-activate a line on the current card. Before you can de-activate a line, you must:
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.
AXSM
dnln
<-ds3 | -e3 | -sonet> <bay.line>
-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. |
dspln, dsplns, cnfln, upln
Log: nolog | State: active, standby | Privilege: GROUP1 |
De-activate line 1 in bay 1.
chicago.1.AXSM.a > dnln 1.1
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.
dnport
<ifNum>
ifNum | The logical port number. Use dspports or dspport as needed to determine the need to disable a port. |
dspport, dspports, upport
Log: nolog | State: active, standby | Privilege: GROUP1 |
Disable port 1 on the current card.
chicago.1.AXSM.a > dnport 1
Display Alarms for a Line
Use the dspalm command to view the alarms associated with a specified line.
AXSM
dspalm
-sonet <bay.line> | -ds3 <bay.line> | -e3 <bay.line> | -plcp <bay.line>
-ds3 | -sonet | -e3 | -plcp bay.line | Specifies a Sonet line (OC-3c, OC-12c, OC-48c), DS3 line, E3 line, or a PLCP line, 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. PLCP (physical layer convergence procedure) is a specification that maps ATM cells into physical media, such as T3 or E3, and defines certain management information. |
cnfalm, clralm, dspalms
Log: nolog | State: active | Privilege: ANYUSER |
Display alarms on OC-12 line 1.1.
node19.1.AXSM.a > dspalm -sonet 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
Display Alarm Configuration
Display the threshold information about the alarm statistics being collected. Refer to the cnfalm description for details regarding alarm threshold configuration.
AXSM
dspalmcnf
-sonetsec <bay.line> | -sonetline <bay.line> | -sonetpath <bay.line> | -ds3 <bay.line> | -e3 <bay.line> | -plcp <bay.line>
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. |
cnfalm, dspalm, dspalms
Log: nolog | State: active | Privilege: ANYUSER |
Display the alarm configuration for SONET line 1.1.
pinnacle.10.AXSM.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
Display Alarm Counters
Displays the performance monitoring alarm counters for either a SONET or DS3 line.
AXSM
dspalmcnt
-ds3 <bay.line> | -e3 <bay.line> | -sonet <bay.line> | -plcp <bay.line>
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. |
clralmcnt
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display the alarm count for T3 line 1 in bay 1.
pinnacle.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.
pinnacle.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
Display Alarms
Display all line-related alarms on the card. RFC 2258 describes the categories of alarms. The display can easily scroll for many pages if more than one line is active.
AXSM
dspalms
This command tales no parameters.
dspalm, clralm
Log: nolog | State: active | Privilege: ANYUSER |
Display alarms for the lines on the current card.
node19.1.AXSM.a > dspalms
Line Number: 1.1
Alarm State
Section : Clear
Line : Clear
Path : Clear
Statistical Alarm State
Section : Clear
Line : Clear
Path : Clear
Line Number: 1.2
Alarm State
Section : Clear
Line : Clear
Path : Clear
Statistical Alarm State
Section : Clear
Line : Clear
Path : Clear
Line Number: 2.1
Alarm State
Section : Clear
Line : Clear
Path : Clear
Statistical Alarm State
Section : Clear
Line : Clear
Path : Clear
Line Number: 2.2
Alarm State
Section : Clear
Line : Clear
Path : Clear
Statistical Alarm State
Section : Clear
Line : Clear
Path : Clear
Display Card
Display the following information about a card:
Some of the information that dspcd shows is common to the version command, but version shows the boot code version in bold.
PXM45, AXSM
dspcd
This command does not take parameters.
dspcds, version
Log: nolog | State: active, standby | Privilege: ANYUSER |
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. |
Unknown.7.PXM.a > dspcd
Unknown System Rev: 02.00 Aug. 02, 2000 23:39:06 GMT
MGX8850 Node Alarm: CRITICAL
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: SAK0405008B SAK0325009M 12345678901
Prim SW Rev: 2.0(246)A1 --- ---
Sec SW Rev: 2.0(246)A1 --- ---
Cur SW Rev: 2.0(246)A1 --- ---
Boot FW Rev: 2.0(168)A1 --- ---
800-level Rev: 18 03 22
Orderable Part#: 800-06147-01 800-05787-01 800-12345-99
CLEI Code: 0000000000 È 1234567898
Reset Reason: On Reset From Shell
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
Unknown System Rev: 02.00 Aug. 02, 2000 23:39:06 GMT
MGX8850 Node Alarm: CRITICAL
Crossbar Slot Status: Present
Alarm Causes
------------
NO ALARMS
Display card details for the current AXSM-1-2488.
Unknown.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
Display Card Alarms
Use dspcdalms on the PXM45 to display alarms that have been reported by a service module. If dspcdalms shows an alarm for one of the following parts of a card, you can cc to that card and execute one of the applicable commands:
In addition to the preceding, on the AXSM you can also execute dspalm and dspalms.
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
The dspcdalms command is part of a hierarchy of troubleshooting commands you can execute on the PXM45 or a service module. Frequently, dspcdalms follows the higher-level command dspndalms.
PXM45
dspcdalms [slot]
slot identifies a particular slot. For the current PXM45, slot is unnecessary. For any other card, you must include slot.
PXM45: dspndalms, dspslotalms, dspswalms, dspclkalms,
AXSM: dspalm, dspalms
Log: nolog | State: active | Privilege: ANYUSER |
Display card-level alarms for the card in slot 1.
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. The system uses the default of logical slot 7 (the active PXM45). In this case, the active PXM45 resides in slot 8.
Unknown.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 Type <CR> to continue, Q<CR> to stop: 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
Display Cell Counts for the Card
The dspcdbucketcnt command shows the following cell-related counts:
In addition to the other bucket command on the AXSM (dsplnbucketcnt), the display commands for the switch planes on the PXM45 may help you analyze cell flows. (See the dspxbar-type commands.)
AXSM
dspcdbucketcnt
This command takes no parameters.
dsplnbucketcnt, all the dspxbar-type of commands (on the PXM45)
Log: nolog | State: active | Privilege: ANYUSER |
Display the bucket counters for the current AXSM.
Unknown.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
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:
AXSM
dspcdcnt
clrcdcnt (on the AXSM), dspxbar, dspxbaralm, dspxbaralms, dspxbarerrcnt, dspxbarerrthresh, dspxbarmgmt, dspxbarstatus (on the PXM45)
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display the cell transfers between the current AXSM and the switching planes (crossbar planes) on an MGX 8850 node.
Golden_U2.11.AXSM.a > dspcdcnt Ingress Count Egress Count ------------- ------------ Cells to xbar plane[1]: 0 Cells from xbar plane[1]: 0 Cells to xbar plane[2]: 0 Cells from xbar plane[2]: 0 Cells to xbar plane[3]: 0 Cells from xbar plane[3]: 0 Cells to xbar plane[4]: 0 Cells from xbar plane[4]: 0 Cells to xbar plane[5]: 2527801 Cells from xbar plane[5]: 2371128 Cells to xbar plane[6]: 3030277 Cells from xbar plane[6]: 2806944 Cells to xbar plane[7]: 2526655 Cells from xbar plane[7]: 2407638 Cells to xbar plane[8]: 0 Cells from xbar plane[8]: 0 Total cells to backplane: 8084733 Total cells from backplane: 7585710 Cells from QE48 : 8084733 Cells to QE48: 7585710 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]: 499058 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]: 598869 Cells to dest slot[08]: 0 Cells to dest slot[09]: 0 Cells to dest slot[10]: 0 Cells to dest slot[11]: 6986806 Cells to dest slot[12]: 0 Cells to dest slot[13]: 0 Cells to dest slot[14]: 0
Display Card Errors
Display information about card errors.
PXM45
dspcderrs
clrerr
Log: nolog | State: active, standby | Privilege: ANYUSER |
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 >
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:
PXM45
dspcds
dspcd, version
Log: nolog | State: active | Privilege: ANYUSER |
Display information for all cards in the MGX 8850 switch.
Unknown.7.PXM.a > dspcds
Unknown System Rev: 02.00 Aug. 06, 2000 18:03:35 GMT
Backplane Serial No: SAA03270618 Bp HW Rev: B0 GMT Offset: 0
Node Alarm: CRITICAL
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----
01 Active/Active AXSM_1OC48 NONE NA NO REDUNDANCY
02 Active/Active AXSM_1OC48 NONE NA NO REDUNDANCY
03 Active/Active AXSM_16OC3 NONE 04 PRIMARY SLOT
04 Standby/Active AXSM_16OC3 NONE 03 SECONDARY SLOT
05 Active/Active AXSM_4OC12 NONE NA NO REDUNDANCY
06 Active/Active AXSM_4OC12 NONE NA NO REDUNDANCY
07 Active/Active PXM45 NONE 08 PRIMARY SLOT
08 Standby/Active PXM45 NONE 07 SECONDARY SLOT
09 Active/Active AXSM_16T3E3 NONE NA NO REDUNDANCY
10 Active/Active AXSM_16T3E3 NONE NA NO REDUNDANCY
11 Empty --- --- --- ---
12 Active/Active AXSM_2OC12 NONE NA NO REDUNDANCY
13 Empty --- --- --- ---
14 Empty --- --- --- ---
Display Card Status
Displays the most serious alarms reported by a service module. The alarm information pertains to:
You can use this command to isolate the alarm source if, for example, you see that a Critical Alarm LED is lit or just want to check the node for alarms. You can subsequently use other alarm commands to locate the problem. Some alarm commands run on only the PXM45, and other commands run on service modules. The commands other than dspcdstatus on the PXM45 are:
The alarm monitoring function on the PXM45 uses two criteria to determine which alarm to display. One criterion is alarm severity, and the other is hierarchy.
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
Two hierarchies of alarm types exist. They are card alarms and node alarms. See Figure 9-1 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.
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.
PXM45
dspcdstatus
This command requires a slot number.
dspndalms, dspcdalms, dspenvalms, dspclkalms, dspswalms, dspalm (AXSM), dspalms (AXSM)
Log: nolog | State: active | Privilege: ANYUSER |
Display alarms for slot 11. The display shows a critical line alarm for slot 11. Next, cc to slot 11 and execute dspalms.
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
Display Channel Counters
Display the statistical counters for a connection (channel).
AXSM
dspchancnt
<ifNum>
<vpi>
<vci>
<isPVC>
ifNum | Logical port number. The range depends on the card type. On the AXSM, the range is 1-60. |
vpi | The VPI in the range 1-4095. |
vci | The VCI in the range 1-65535. |
isPVC | A Boolean expression that identifies either an SVC or a SPVC. Type a 0 for an SVC or a 1 for an SPVC. |
dspchstats, clrchancnt, dspcdcnt
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display channel counters 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 Clock Alarms
Displays alarms associated with the primary or secondary clock source.
The switch constantly monitors the state of the clocks. On the local node, the clock monitor declares an alarm if the clock becomes undetectable or goes out of specification for any reason. The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
The dspclkalms command is part of a hierarchy of troubleshooting commands you can execute on the PXM45 or a service module. Frequently, dspclkalms follows the higher-level command dspndalms. The dspndalms command shows a variety of alarms within the switch and helps isolate the problem.
The dspndalms and dspclkalms commands run on the PXM45. If the errored clock source appears to be on a service module, you can cc to the CLI of that card and execute a variety of alarm commands and other troubleshooting commands.
PXM45
dspclkalms
This command takes no parameters.
dspcdstatus, dspndalms, dspalm, dspalms, dspclksrcs, cnfclksrc
Log: nolog | State: active | Privilege: ANYUSER |
Display clock alarms.
pop20two.7.PXM.a > dspclkalms pop20two System Rev: 02.00 Jul. 31, 2000 11:23:17 GMT MGX8850 Shelf Alarm: NONE Clock Manager Alarm Summary ---------------------------- Critical Major Minor 000 000 000
Display Clock Sources
Displays the configuration and status of the clock sources on the node. (For details about network synchronization, see the description of cnfclksrc.) The dspclksrcs output consists of:
|
Note 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. |
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.
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.
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 that appears 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.
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 first-time, user-specification of the clock source. The reason fields and their meaning appear in Table 9-3.
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 The interface does not support clocking. phase error The clock manger 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 has gone out of locking range. Note that for Reason, "out of lock" and "null" is synonymous. 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- 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.
Table 9-3: Reasons for Change of Clock State
Reason
Meaning
support clocking
band test
For information on revertive behavior, see the cnfclksrc description.
PXM45
dspclksrcs
cnfclksrc, delclksrc, dspclkalms
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display the current clock status. 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 reason is "okay" in each case.
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 on the clock sources. The display shows that nothing has been configured, so the internal oscillator generates the primary and secondary clocks. The primary and secondary clock reason is "okay" in each case.
Unknown.7.PXM.a > dspclksrcs Primary clock type: null Primary clock source: 0.0 Primary clock status: not configured Primary clock reason: okay Secondary clock type: null Secondary clock source: 0.0 Secondary clock status: not configured Secondary clock reason: okay Active clock: internal clock source switchover mode: non-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
Display Connection
Display information about an SPVC. The contents of the display on the AXSM and the PXM45 slightly differ. 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.
On the PXM45, dspcon shows the following connection identifiers:
The provisioning parameters in the display show:
The Traffic Parameters section shows the standard parameters PCR, SCR, and CDV in the receive and transmit directions.
On the AXSM, dspcon shows the following connection identifiers:
The provisioning parameters in the display show:
The traffic management parameters consist of:
Other fields pertain to connection integrity:
The dspcon command requires a unique connection identifier. If you do not have the information to identify a connection, execute dspcons. On the AXSM, dspcons identifies all the connections on the AXSM. On the PXM45, dspcons identifies all the connections on the node. (See dspcons description).
AXSM, PXM45
On the AXSM:
dspcon
<ifNum>
<vpi>
<vci>
On the PXM45:
dspcon
<portid>
<vpi>
<vci>
ifNum AXSM | The logical port number in the range 1-60. |
portid PXM45 | The portid 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. |
addcon, dspcons, cnfcon
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display connection 5 31 63000 on the current AXSM.
pinnacle.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 Summaries of Connection Information (SPVCs Only)
The dspconinfo runs on the PXM45 and lists the total number SPVCs on each PNNI port on the node. For each port, the display shows:
PXM45
dspconinfo
This command takes no parameters.
none
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display the SPVC summaries for the current node. This example shows all connections as failed.
popeye10.7.PXM.a > dspconinfo Local Port #Active #Failed #Total --------------------------------------------- 6:1.4:4 0 1 1 6:1.5:5 0 19800 19800 12:1.1:1 0 10001 10001 14:1.1:1 0 10000 10000 14:1.2:2 0 19900 19900
Display Connections
Display basic information for all connections. The dspcons command runs on the CLI of either the AXSM or the PXM45. The output is different on these two cards. On the AXSM, the display shows:
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 | OK or failed. |
Owner | Whether the endpoint is master or slave. |
Local and Remote NSAP | An NSAP address for each end of the connection. |
AXSM, PXM45
dspcons
dspcon, addcon, cnfcon, delcon
Log: nolog | State: active | Privilege: ANYUSER |
Display 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
Display all connections by entering dspcons on the CLI of the PXM45.
Unknown.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 Type <CR> to continue, Q<CR> to stop: 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 Type <CR> to continue, Q<CR> to stop: 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
Display Connection Tests
Display the results of the tstdelay or tstconseg command. These tests show 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 dspcontests or dspcon to see the results. The same test results presented by dspcontests appears in the dspcon display (along with detailed information about a connection).
dspcontests
<ifNum>
<vpi>
<vci>
[-num <count>]
ifNum | The number of the logical interface. On the AXSM, the range is 1-60. |
vpi | The VPI range for the SVC or SPVC is 1-255. |
vci | The VCI range for a VCC SPVC is 32-65535. For a VPC, the only VCI value for an SPVC is 0. |
-num | (Optional) A keyword that indicates an aggregate connection count follows. |
number | The number of connections to display. |
tstdelay, tstconseg, dspcon
Log: log | State: active | Privilege: ANYUSER |
Run tstdelay for 1 10 100 then display the results.
node19.1.AXSM.a > tstdelay 1 10 100 Test started; Use dspcon/dspcontests to see test results
Step 2 Check the results:
node19.1.AXSM.a > dspcontests 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.
node19.1.AXSM.a > tstconseg 1 10 100 Test started; Use dspcon/dspcontests to see test results
Step 2 Check the results:
node19.1.AXSM.a > dspcontests 1 10 100 Connection Id Test Type Direction Result Round Trip Delay ============= ========= ========= ======= ================ 01.0010.00100: OAM Lpbk egress TimeOut 0
Display Controllers
Displays all controllers that have been added through the addcontroller command.
PXM45
dspcontrollers
This command takes no parameters.
addcontroller, delcontroller
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display all controller. In this example, the switch has only one controller—PNNI. The display also shows that the controller is internal (slot 7) and has the optional, user-specified name "PNNITWO." Apart from controller information, the display shows that no shelf alarms exist.
pop20two.7.PXM.a > dspcontrollers pop20two System Rev: 02.00 Jul. 30, 2000 09:39:36 GMT MGX8850 Shelf Alarm: NONE Number of Controllers: 1 Controller Name: PNNITWO Controller Id: 2 Controller Location: Internal Controller Type: PNNI Controller Logical Slot: 7 Controller Bay Number: 0 Controller Line Number: 0 Controller VPI: 0 Controller VCI: 0 Controller In Alarm: NO Controller Error:
Display Environment Alarms
Display alarms related to the environment of the node. The monitored categories are:
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
The dspenvalms command is part of a hierarchy of troubleshooting commands you can execute on the PXM45. Frequently, dspenvalms follows the higher-level command dspndalms. The dspndalms command shows a variety of alarm types within the switch and helps isolate the problem.
PXM45
dspenvalms
[temp]
[psu]
[fan]
[vmon]
temp | Temperature shows the temperature and whether an alarm condition exists. |
psw | Power supply units (psw) shows how many AC power supplies reside in the power supply tray. Applies to only AC-powered systems. Also shows the high and low DC values at the output the supplies should be able to maintain. |
fan | 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. |
dspndalms, dspcdstatus
Log: nolog | State: active | Privilege: ANYUSER |
Check the temperature.
Unknown.7.PXM.a > dspenvalms temp Unknown 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 no bottom fan tray.
Unknown.7.PXM.a > dspenvalms fan Unknown 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
Type <CR> to continue, Q<CR> to stop:
Display all environment alarms for the enclosure by entering dspenvalms. with none of the optional parameters.
Unknown.7.PXM.a > dspenvalms Unknown 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 Error
Display error message files. The dsperr command is primarily a debug command. Because is displays tasks and system calls, the information is more suitable to developers or others that can use information that is internal to the switch rather than applicable to the network. The displayed information may be useful to Cisco support personnel.
dsperr
This command takes no parameters.
clrerr
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display several screens of internal error messages.
pinnacle.7.pxm.a> dsperr
Error Log for Slot 08: Error Num 987
Firmware version: 002.000.001-D_fconrad Product Id: 8850
Timestamp: 04/04/2000-09:04:18 Node name: ÿÿÿÿ
Section Number 0:
Event Logged:
04/04/2000-09:04:18 08 FtpdServ1 SSI-4-STRTOOLONG 00987
ssiStringCopy: Source String longer than Dest Buffer Size = 5, Src Str ptr = 0x
824aaec0.
Section Number 1:
Stack Trace:
0x8078b6b8 vxTaskEntry +00c: ftpdDelete+0()
0x8034a834 ftpdDelete +fbc: ftpSendReplicationRequest+0()
0x8034cc04 ftpSendReplicationRequest+044: ssiFRFileSendStandbyAsync+0()
0x801d5bcc ssiFRFileSendStandbyAsync+1a0: dbsync_dir_name_get+0()
0x801d3838 dbsync_dir_name_get +078: ssiStringCopy+0()
0x80165a18 ssiStringCopy +178: ssiEvent+0()
0x801522d4 ssiEvent +264: ssiEventMsgReport+0()
0x801525a0 ssiEventMsgReport +280: ssiStackTrace+0()
--------------
Type <CR> to continue, Q<CR> to stop:
Timestamp: 04/04/2000-10:29:11 Node name: ÿÿÿÿ
Section Number 0:
Event Logged:
04/04/2000-10:29:11 08 IPC Ctl FIPC-4-COMEPIDINVALID 00986
An invalid FIPC_COM_EPID of 0x8590 was passed as an argument.
Section Number 1:
Stack Trace:
0x8078b6b8 vxTaskEntry +00c: sysTaskSetup+0()
0x801646a8 sysTaskSetup +0a4: ctc_app_root_start+0()
0x8027357c ctc_app_root_start +0d4: ssiIpcCtlRoot+0()
0x801783e8 ssiIpcCtlRoot +1a8: ssiIpcComEpWait+0()
0x8016fd20 ssiIpcComEpWait +070: ssi_ipc_mhdlr_receive_loop+0()
0x801725f8 ssi_ipc_mhdlr_receive_loop+100: ssi_ipc_mhdlr_msg_receive+0()
0x80172e64 ssi_ipc_mhdlr_msg_receive+054: ssi_ipc_ctl_handler+0()
0x80178ca0 ssi_ipc_ctl_handler +0a0: ssi_ipc_handle_bind_ack+0()
0x80179884 ssi_ipc_handle_bind_ack +0c4: ssi_ipc_bind_state_set+0()
0x80172278 ssi_ipc_bind_state_set +1a0: ssiEvent+0()
0x801522d4 ssiEvent +264: ssiEventMsgReport+0()
0x801525a0 ssiEventMsgReport +280: ssiStackTrace+0()
--------------
Section Number 1:
Stack Trace:
0x8078b6b8 vxTaskEntry +00c: sysTaskSetup+0()
0x801646a8 sysTaskSetup +0a4: ctc_app_root_start+0()
0x8027357c ctc_app_root_start +0d4: shmMain+0()
0x80202ee4 shmMain +1c0: ssiIpcComEpWait+0()
0x8016fd20 ssiIpcComEpWait +070: ssi_ipc_mhdlr_receive_loop+0()
0x801725f8 ssi_ipc_mhdlr_receive_loop+100: ssi_ipc_mhdlr_msg_receive+0()
0x80172e64 ssi_ipc_mhdlr_msg_receive+054: ssiRmiMsgHandler+0()
0x801818c4 ssiRmiMsgHandler +98c: shmMhIntPortMsgHandler+0()
0x8022fb90 shmMhIntPortMsgHandler +164: shmMainMsgHdlr+0()
0x80203184 shmMainMsgHdlr +274: shmSmeEventsProcess+0()
0x80216190 shmSmeEventsProcess +168: shm_sme_event_dispatch+0()
0x80216818 shm_sme_event_dispatch +130: shmCsmEvtHandler+0()
0x8021777c shmCsmEvtHandler +23c: shmCsmCdBootInitProc+0()
0x8021950c shmCsmCdBootInitProc +244: shmTrapGen+0()
0x80245ecc shmTrapGen +35c: shmTrapBackCdType2VendorType+0()
0x8024656c shmTrapBackCdType2VendorType+020: entityLineModuleVendorTypeGet+0()
0x802b39f4 entityLineModuleVendorTypeGet+040: ssiEvent+0()
0x801522d4 ssiEvent +264: ssiEventMsgReport+0()
0x801525a0 ssiEventMsgReport +280: ssiStackTrace+0()
Section Number 1:
Stack Trace:
0x8078b6b8 vxTaskEntry +00c: sysTaskSetup+0()
0x801646a8 sysTaskSetup +0a4: ctc_app_root_start+0()
0x8027357c ctc_app_root_start +0d4: shmMain+0()
0x80202ee4 shmMain +1c0: ssiIpcComEpWait+0()
0x8016fd20 ssiIpcComEpWait +070: ssi_ipc_mhdlr_receive_loop+0()
0x801725f8 ssi_ipc_mhdlr_receive_loop+100: ssi_ipc_mhdlr_msg_receive+0()
0x80172e64 ssi_ipc_mhdlr_msg_receive+054: ssiRmiMsgHandler+0()
0x801818c4 ssiRmiMsgHandler +98c: shmMhIntPortMsgHandler+0()
0x8022fb90 shmMhIntPortMsgHandler +164: shmMainMsgHdlr+0()
0x80203184 shmMainMsgHdlr +274: shmSmeEventsProcess+0()
0x80216190 shmSmeEventsProcess +168: shm_sme_event_dispatch+0()
0x80216818 shm_sme_event_dispatch +130: shmCsmEvtHandler+0()
0x8021777c shmCsmEvtHandler +23c: shmCsmCdBootInitProc+0()
0x802194fc shmCsmCdBootInitProc +234: shmTrapGen+0()
0x80245da8 shmTrapGen +238: shmTrapBackCdType2VendorType+0()
0x8024656c shmTrapBackCdType2VendorType+020: entityLineModuleVendorTypeGet+0()
0x802b39f4 entityLineModuleVendorTypeGet+040: ssiEvent+0()
0x801522d4 ssiEvent +264: ssiEventMsgReport+0()
0x801525a0 ssiEventMsgReport +280: ssiStackTrace+0()
Display ILMI Counters
Displays the ILMI counters for a particular resource partition on a particular logical port.
AXSM
dspilmicnt
<ifNum>
<partId>
ifNum | Logical port number. On the AXSM, the range is 1-60. |
partId | The number of the resource partition. The range is 1-20. |
cnfilmi, dspilmi, dspilmis, clrilmicnt, dnilmi, upilmi
Log: nolog | State: active, standby | Privilege: ANYUSER |
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
Display Line
Display the characteristics of a physical line.
AXSM
dspln
<-ds3 | -e3 | -sonet>
<bay.line>
-ds3 | Command delineator that precedes the line number entry for a T3 line. |
-e3 | Command delineator that precedes the line number entry for an 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. |
upln, cnfln, delln
Log: nolog | State: active | Privilege: ANYUSER |
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
Display Lines
Displays the configuration for all lines on a card. For each line, the output information consists of the:
For information on an individual line, use dspln. Also, the dspln command shows the transmit clock configuration if one exists.
AXSM
dsplns
cnfln, delln, dspcds, dspln, upln
Log: nolog | State: active, standby | Privilege: ANYUSER |
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
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.
local.7.AXSM.a > dsplns Line Line Line Line Length OOF AIS Num State Type Lpbk (meters) Criteria c-BitsCheck ------------ ----------- ----------- ------ -------- --------- 1.1 Up ds3m23plcp PayloadLoop 0 fBits3Of8 Check 1.2 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 1.3 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 1.4 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 1.5 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 1.6 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 1.7 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 1.8 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 2.1 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 2.2 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 2.3 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 2.4 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 2.5 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 2.6 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 2.7 Down ds3cbitadm NoLoop 0 fBits3Of8 Check 2.8 Down ds3cbitadm NoLoop 0 fBits3Of8 Check
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:
PXM45
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>
-log | Keyword that 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 | Keyword that specifies the slot number for which to display errors. |
-task | Keyword that specifies the task for which to display errors. |
-mod | Keyword that 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 | Keyword that specifies the severity of the alarm specified by 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 | Keyword that specifies a particular time for which to display events: same time or earlier time. |
-tge | Keyword that specifies a particular time for which to display events: same time or later time. |
clrlog, dsplogs
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display all contents of the log files. This example shows only the first of many screens. Note the display begins with the most recent entry then progresses to the oldest entry.
node19.8.PXM.a > dsplog 03/29/2000-13:28:36 08 tLOGD FIPC-5-EPHNDLRFAIL FIPC EPHandler 8013b4f8 on Ep 8 returning sts ffffffff, errno 23009 03/29/2000-13:28:36 08 tLOGD SYS-4-MSGINVALID Received invalid msg to sysLogProcessIpcMsgs. Size=232 Msg=011c00e8 fbfbfbfb 30312d30 30303032 2030332f 03/29/2000-13:23:17 08 ShelfMgr SHM_-7-UI_SHMCLI_PROC_ SHM CLI PROC INFO: Request being processed by shmProcSnmpSlotInfoMsg - 2 dropped 03/29/2000-13:23:17 08 ShelfMgr SHM_-7-UI_CMDTYPE_INFO SHM INFO: Info requested for command type = 74 - 2 dropped 03/29/2000-13:08:17 08 ShelfMgr SHM_-7-UI_SHMCLI_PROC_ SHM CLI PROC INFO: Request being processed by shmProcSnmpSlotInfoMsg - 2 dropped 03/29/2000-13:08:17 08 ShelfMgr SHM_-7-UI_CMDTYPE_INFO SHM INFO: Info requested for command type = 74 - 2 dropped 03/29/2000-12:53:17 08 ShelfMgr SHM_-7-UI_SHMCLI_PROC_ SHM CLI PROC INFO: Request being processed by shmProcSnmpSlotInfoMsg - 2 dropped 03/29/2000-12:53:17 08 ShelfMgr SHM_-7-UI_CMDTYPE_INFO SHM INFO: Info requested for command type = 74 - 2 dropped
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 further:
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:
PXM45
dspndalms
This command takes no parameters.
dspalm, dspalms
Log: nolog | State: active | Privilege: ANYUSER |
Display node alarms. The output shows alarms of all three severities.
Unknown.7.PXM.a > dspndalms Node Alarm Summary Alarm Type Critical Major Minor Clock Alarms 0 0 0 Switching Alarms 0 1 1 Shelf Slot Alarms 0 0 0 Environment Alarms 0 0 0 Alarms From Cards 3 2 1
Display Port Counters
Displays ATM cell counters for a logical port. Refer to the example for contents.
AXSM
dspportcnt <ifNum>
ifNum | Logical port number. The range depends on the card. For an AXSM, the range is 1-60. |
dspports, dspport, cnfport, dspcds
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display port counters on logical port (ifNum) 1 of the current AXSM.
pinnacle.6.AXSM.a > dspportcnt 1 Ingress Egress Arrival Clp0 Cells : 491845 491849 Arrival Clp1 Cells : 0 0 Clp0 dscd Cells : 0 0 Clp1 dscd Cells: 0 0 Departure Clp0 Cells : 491846 491849 Departure Clp1 Cells : 0 0
Display Slot Alarms
Display alarms for a slot. The dspslotalms command provides a slot-level view of alarms, so further investigation through other commands may be appropriate. For example, if the hard drive on the PXM-HD back card has a problem, dspslotalms identifies the problem.
The categories of alarms displayed by dspslotalms are
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
The dspslotalms command is part of a hierarchy of troubleshooting commands you can execute on the PXM45. Frequently, dspslotalms follows the higher-level command dspndalms. The dspndalms command shows a variety of alarms within the switch and helps isolate the problem. You can subsequently cc to the CLI of a suspect card and execute a variety of other troubleshooting commands.
PXM45
dspslotalms [slot]
The optional slot number lets you display alarms for a specific slot, otherwise the commands displays alarms for all slots.
dspndalms, dspalm, dspalms
Log: nolog | State: active | Privilege: ANYUSER |
Display alarms detected by card slot number.
node19.8.PXM.a > dspslotalms Node Slot Alarm Summary Card Alarm Critical 0 Major 1 Minor 0 Disk Alarm Slot 7 Critical 3 Major 4 Minor 5
Display SPVC Log
Show whether the SPVC log has been enabled.
AXSM
dspspvclog
This command takes no parameters.
cnfspvclog
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display the current SPVC log. The output shows that the log is disabled.
Unknown.8.PXM.a > dspspvclog Global SPVC Event Log Status: Disable
Display Switching Alarms
Displays alarms for circuits on the PXM45:
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
PXM45
dspswalms
This command takes no parameters.
dspndalms
Log: nolog | State: active | Privilege: ANYUSER |
Display switching alarms.
node_chi.8.PXM.a > dspswalms Node Switching Alarm Summary Card Crossbar Critical 0 Major 0 Minor 0 Crossbar Fabric Critical 0 Major 0 Minor 0 Humvee Alarm Critical 0 Major 0 Minor 0
Display Trap Manager
Display details about all existing trap managers. The dsptrapmgr output shows:
Of these elements, the IP address and port number result from addtrapmgr.
PXM45
dsptrapmgr
This command takes no parameters.
addtrapmgr, deltrapmgr
Log: nolog | State: active | Privilege: ANYUSER |
Display trap managers.
node19.8.PXM.a > dsptrapmgr
ipAddress PortNum RowStatus ReadTrapFlag NextTrapSeqNum
--------------- ------- ---------- ------------ --------------
171.71.55.21 2500 Add Off 0
172.29.65.87 2500 Add Off 348
172.71.59.21 2500 Add Off 0
LastTrapSeqNum: 385
NumOfValidEntries: 3
Display Crossbar Planes
The dspxbar command displays general information about the status of a specified switch plane (ASIC). The crossbar commands are specialized debug commands with infrequent use. You may be asked by personnel in the Cisco Technical Assistance Center (TAC) to use one of these commands.
The dspxbar output shows
PXM45
dspxbar [plane]
| (Optional.) The slot number of the XM60. Valid slot numbers are 9, 10, 25, and 26. Subsequently, specify a switching plane in the range 0-3. |
plane | (Optional.) The number of the switching plane. If you do not specify a plane, the system displays information for plane 0 as a default. For the MGX 8850 node, the range is 0-2. |
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display switch ASIC (or switch plane or crossbar) 1.
Unknown.8.PXM.a > dspxbar Unknown System Rev: 02.00 Jul. 13, 2000 18:14:33 GMT PXM45 CROSSBAR CONFIGURATION Crossbar Slot No: 7 Switch Asic No: 0 Status: OK Cell Grant Mode: Multicast Pref Resync Sframe Tic: Rising-Edge Detect Asic Revision: 1 Slot BACK PRESSURE DISABLE REQUEST DISABLE DATA REDUNDANCY CONFIG No Grant Mode Dest Src Dest Src Mode Slot ---- ------------- --------------- ------------ ------------------ 1 Valid InBand No No No No Remap 1 2 Valid InBand No No No No Remap 2 3 Valid InBand No No No No Remap 3 4 Valid InBand No No No No Remap 4 5 Valid InBand No No No No Remap 5 6 Valid InBand No No No No Remap 6 7 Valid InBand No No No No Remap 7 8 Valid InBand No No No No Remap 8 9 Valid InBand No No No No Remap 9 10 Valid InBand No No No No Remap 10 11 Valid InBand No No No No Remap 11 12 Valid InBand No No No No Remap 12 13 Valid InBand No No No No Remap 13 Type <CR> to continue, Q<CR> to stop: 14 Valid InBand No No No No Remap 14
Display Crossbar Alarms
The dspxbaralm command shows whether any crossbar (switch fabric) has an alarm. If an alarm appears, use dspxbarerrcnt or dspxbarstatus to help isolate the problem. The output shows the slot and switch ASIC number in the alarmed state.
PXM45
dspxbaralm
This command takes no parameters.
Log: nolog | State: active, standby | Privilege: ANYUSER |
dspxbar, dsperrcnt, dsperrthresh, dspxbarstatus
Display the current crossbar alarms. The display shows status on both the active and standby PXM45. On the card in slot 7, crossbars 1 and 2 show errors. Subsequent execution of dspxbarerrcnt shows the slot number that switch ASIC 2 (or plane 2) cannot support.
Unknown.7.PXM.a > dspxbaralm
Unknown System Rev: 02.00 Aug. 06, 2000 17:46:15 GMT
MGX8850 Node Alarm: CRITICAL
Slot Plane Severity
---- ----- --------
7 0 None
7 1 Major
7 2 Major
8 0 None
8 1 None
8 2 None
Unknown.7.PXM.a > dspxbarerrcnt 7 2
Unknown System Rev: 02.00 Aug. 06, 2000 17:47:53 GMT
MGX8850 Node Alarm: CRITICAL
PXM45 CROSSBAR CURRENT ERROR COUNTERS
Crossbar Slot No: 7 Switch ASIC 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 0 0 0 0 0 0 0 0 0
4 0 0 0 0 0 0 0 0 0
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 0 0 0 0 0 0 0 0 0
10 0 0 0 0 0 0 0 0 0
11 0 0 0 0 0 0 0 0 0
12 2772K 41594K 41594K 0 41594K 41594K 0 0 41594K
13 0 0 0 0 0 0 0 0 0
Type <CR> to continue, Q<CR> to stop:
Unknown System Rev: 02.00 Aug. 06, 2000 17:47:53 GMT
MGX8850 Node Alarm: CRITICAL
14 0 0 0 0 0 0 0 0 0
Frame Tick Error: 0
Frame Lock Error: 0
ACP Illegal Address Error: 0
Note: for big error counter, suffix K(x1000) or M(x1000000) is used.
Display Crossbar Error Counters
The dspxbarerrcnt command shows errored cell counts of various types for a specific crossbar (or switch ASIC). Furthermore, the display shows arrays of information by the number of the slot. (For a crossbar, a slot number represents the capacity of the ASIC itself to address a particular slot: it does not refer to information about a service module in a slot.)
The types of error counts apply to the 60-byte switch frames:
PXM45
dspxbarerrcnt
<slot>
<plane>
slot | The slot of the switching fabric. On the MGX 8850 node, the slot is 7 or 8. |
plane | The plane is the number of the switch ASIC (or crossbar). On the |
Log: log | State: active, standby | Privilege: ANYUSER |
Display the crossbar error counters for switch ASIC 2 in slot 7. The Node Alarm field of the display shows the errors have resulted in a critical alarm. A large number of errors have occurred in the slot 12 path. The card's ability to address the service module in slot 12 has been significantly compromised.
Note at the bottom of the display a message about multipliers for large numbers of errors. Because the display can accommodate a finite number of errors without being distorted, a "K" (for 1000) and "M" (for 1000000) multiplier may be necessary, as is the case in this example.
Unknown.7.PXM.a > dspxbarerrcnt 7 2
Unknown System Rev: 02.00 Aug. 06, 2000 17:47:53 GMT
MGX8850 Node Alarm: CRITICAL
PXM45 CROSSBAR CURRENT ERROR COUNTERS
Crossbar Slot No: 7 Switch ASIC 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 0 0 0 0 0 0 0 0 0
4 0 0 0 0 0 0 0 0 0
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 0 0 0 0 0 0 0 0 0
10 0 0 0 0 0 0 0 0 0
11 0 0 0 0 0 0 0 0 0
12 2772K 41594K 41594K 0 41594K 41594K 0 0 41594K
13 0 0 0 0 0 0 0 0 0
Type <CR> to continue, Q<CR> to stop:
Unknown System Rev: 02.00 Aug. 06, 2000 17:47:53 GMT
MGX8850 Node Alarm: CRITICAL
14 0 0 0 0 0 0 0 0 0
Frame Tick Error: 0
Frame Lock Error: 0
ACP Illegal Address Error: 0
Note: for big error counter, suffix K(x1000) or M(x1000000) is used.
Display Crossbar Error Threshold
Although the default settings for crossbar error thresholds are optimal for nearly all applications, they can be through the cnfxbarerrthresh command. The dspxbarerrthresh command shows the existing thresholds. The output shows the numbers if errors that result in a minor, major, or critical alarm for each type of failure.
PXM45
dspxbarerrthresh
This command takes no parameters.
dspxbar, dspxbaralms, dspxbarerrcnt
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display the current crossbar error thresholds.
sanfran.8.PXM.a > dspxbarerrthresh
Unknown System Rev: 02.00 May. 26, 2000 14:47:50 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 1000 0 5 10 20 30 40
TranscieverErr 200 0 100 500 550 650 700
DisparityErr 200 0 100 500 550 650 700
ParityErr 200 0 100 500 550 650 700
HeaderCRCErr 200 0 100 500 550 650 700
PayloadCRCErr 200 0 100 500 550 650 700
RemapTwiceErr 200 0 1 2 3 4 5
RemapRecurrErr 200 0 1 2 3 4 5
B.P.ParityErr 200 1 100 500 550 650 700
Display Crossbar Status
Display status of each slot for a crossbar.
PXM45
dspxbar [plane]
planeIndex | (Optional.) The number of the switching plane. If you do not specify a plane, the system displays information for plane 0 as a default. For the MGX 8850 node, the range is 0-2. |
dspxbar, dspxbaralms, dsperrcnt, dsperrthresh
Log: nolog | State: active | Privilege: ANYUSER |
Display the status of switch ASIC 0. The active PXM45 in this example is in slot 7.
Unknown System Rev: 02.00 Jul. 13, 2000 18:26:54 GMT MGX8850 Node Alarm: UNKNOWN Switch CD No: 7 Switch ASIC No: 0 Administrative Status Bitmap: 0xFFFFFFFF Operational Status Bitmap : 0x0 Error Status Bitmap: Slot 1: 0x0 Slot 2: 0x0 Slot 3: 0x0 Slot 4: 0x0 Slot 5: 0x0 Slot 6: 0x0 Slot 7: 0x0 Slot 8: 0x0 Slot 9: 0x0 Slot 10: 0x0 Slot 11: 0x0 Slot 12: 0x0 Slot 13: 0x0 Slot 14: 0x0 Slot 15: 0x0 Slot 16: 0x0 Misc Error Bitmap: 0x0
Path Trace IE
Removes/inserts path trace IE at port level.
pathtraceie <portid>
{rmv | ins}
portid | See the section, "PNNI Format" at the front of this chapter. |
rmv | Allow to remove Trace Transit List IE at the port. |
ins | Allow to insert Trace Transit List IE at the port. |
conntrace, pathtraceport, pathracenode
Log: log | State: active_only | Privilege: SUPER_GP |
Call Control Operations: Enable/Disable Path Trace at Node Level
Enables/disables path trace feature at node level.
pathtracenode {enable | disable}
enable/disable | Enables (disables) path trace at node level. |
conntrace, pathtraceport, pathtraceie
Log: log | State: active_only | Privilege: SUPER_GP |
Call Control Operations: Enable/Disable Path Trace at Port Level
Enables (disables) path trace feature at port level, then saves the result of the path trace in the log file.
pathtraceport <portid>
{enable | disable}
[-H {on | off}]
[-CB {on | off}]
[-V {on | off}]
[-CR {on | off}]
[-cldnum called-AESA]
[-clgnum calling-AESA]
portid | See the section, "PNNI Format" at the front of this chapter. |
enable | disable | Enables (disables) path trace at port level. |
-H | Keyword that specifies the hierarchy option. If enabled, information from all the DTLs in the hierarchy are added in the TTL IE. Default = off |
-CB | Keyword that specifies the crankback option. If enabled, the failure cause for crankback is included in the TTL IE. Default = on |
-V | Keyword that specifies the VPI/VCI option. If enabled, VPI/VCI values of the egress port are added in the TTL IE at every node. Default = off |
-CR | Keyword that specifies the call reference option. If enabled, call reference values of all egress ports are added in the TTL IE. Default = off |
-cldnum | Keyword that specifies the called party number. Enables (disables) path trace on a specific called address. |
-clgnum | Keyword that specifies the calling party number. Enables (disables) path trace on a specific calling address. |
conntrace, pathracenode, pathraceie
Log: log | State: active_only | Privilege: SUPER_GP |
Format of the path trace result for a call in the log file:
Result:Succ/Fail Reason: "Desc" Called No: "--" Calling No: "--"
Cause: "value:Desc"
NodeId Ingress Port Egress Port Vpi/Vci Call Ref EndPtRef (opt)
XXXX YYYY ZZZZ aaa/bbb cccc dddd
XXXX YYYY ZZZZ aaa/bbb cccc dddd
Reset Card
Resets either the hardware of a user-specified card or the failure history of the current card.
Using the resetcd command without defining a slot number results in an ungraceful (disruptive) upgrade. This is the fastest method to upgrade a card but interrupts service.
A graceful (non-disruptive) upgrade requires that the loadrev, runrev, and commitrev commands have already been executed, and that the card is identified in the command string.
PXM45
resetcd
[slot]
The optional slot parameter identifies a card to reset. If you do not specify a slot, the command clears the card-level error history on the current PXM45.
resetsys
Log: log | State: active | Privilege: SUPER_GP |
Reset the current PXM45.
pinnacle.7.PXM.a > resetcd The card in slot number 7, will be reset. Please confirm action Do you want to proceed (Yes/No)? n (command not executed)
Reset System
Reset the entire node.
PXM45
This command takes no parameters but displays a warning and prompts you to continue the execution.
resetsys
resetcd
Log: log | State: active | Privilege: SUPER_GP |
Reset the system.
pinnacle.7.PXM.a > resetsys This command resets the entire shelf, a destructive command. Please confirm now! Do you want to proceed (Yes/No)? n (command not executed)
Switch Core Cards
Switch control of the node from the active PXM45 to the standby PXM45. If a standby PXM45 is not available, the switchcc command fails.
You cannot execute switchcc during a configuration-copy. If you attempt it, the system blocks the command.
PXM45
None
Log: log | State: active | Privilege: SERVICE_GP |
Attempt a switchcc without a standby PXM45 in the backplane.
raviraj.7.PXM.a > switchcc Do you want to proceed (Yes/No)? y Core card redundancy unavailable
raviraj.7.PXM.a >
Test Connection Segment
Test the integrity of an SVC or SPVC. With tstconseg, a single collection of supervisory cells is sent in the egress direction between the card and service equipment (CPE). (See tstdelay for ingress direction.)
When the test successfully starts, the system displays a message stating that the test has begun and directs you to use either dspcon or dspcontests to see the results. The dspcon command shows detailed information about the connection and has a field for the results of this test. The dspcontests command display only the results of the test.
AXSM
tstconseg
<ifNum>
<vpi>
<vci>
[-num <iterations>]
ifNum | The number of the logical interface. On the AXSM, the range is 1-60. |
vpi | The VPI range for the SVC or SPVC is 1-255. |
vci | The VCI range for the SVC is 32-65535. |
-num | (Optional) Keyword that specifies the number of times a collection of supervisory cells should traverse the SVC for the current execution of tstconseg. |
dspcon, tstdelay, dspcontests
Log: log | State: active | Privilege: SERVICE_GP |
Test the integrity of 1 10 1000 in the egress direction.
node19.1.AXSM.a > tstconseg 1 10 100 Test started; Use dspcon/dspcontests to see test results
Test Delay
Test the integrity of the connection in the ingress direction by sending a collection of supervisory cells to the remote end of the network and back. (See tstconseg for the egress direction.) The tstdelay command applies to only SPVCs.
If the test successfully begins, the display states the fact and directs you to use the dspcon or dspcontests command to view the round trip time in microseconds. The dspcon display shows detailed information on the connection and has a field for the test results. The dspcontests display shows the results of only the round trip delay test.
|
Note The primary purpose of tstdelay is to test the integrity of the connection. The round trip time is not accurate enough for any use that requires an accurate measurement of delay. |
AXSM
tstdelay
<ifNum>
<vpi>
<vci>
[-num <iterations>]
ifNum | The logical port number. On the AXSM, the range is 1-60. |
vpi | Virtual path identifier. On the AXSM, the range is 1-255. |
vci | Virtual connection identifier. On t he AXSM, the range is 32-65535 for a VCC. For a VPC, the only vci is 0. |
-num | (Optional) Keyword that specifies the number of times a collection of supervisory cells should traverse the SVC for the current execution of tstdelay. |
dspcons, tstconseg, dspcon
Log: log | State: active | Privilege: SERVICE_GP |
On the AXSM in slot, get the round-trip delay for connection 1 10 100. This example contains four command executions to illustrate how to obtain a list of logical ports; obtain a connection number; start the test; and view the results. the commands are dspports, dspcons, tstdelay, and dspcon.
node19.1.AXSM.a > dspports
ifNum Line Admin Oper. Guaranteed Maximum Port SCT Id ifType VPI
State State Rate Rate (VNNI only)
----- ---- ----- ----- ---------- --------- ----------------- ------ ----------
1 1.1 Up Up 1412831 1412831 6 UNI 0
Step 2 Get the connection ID to provide to tstdelay. The connection identifier appears in NSAP format. In this example, assume tstdelay execution will occur at the slave end of the SPVC. Take the significant digits from the Identifier (01.0010.00100) to get the logical port, vpi, and vci for tstdelay. These values are 1, 10, and 100.
node19.1.AXSM.a > dspcons
record Identifier Type SrvcType M/S Upld Alarm
------ ---------- ---- -------- --- ---- -----
0 01.0010.00100 VCC ubr1 S 0000ebfb none
1 01.0011.00101 VCC ubr1 M 0000ec27 none
Step 3 Execute tstdelay for logical port 1, vpi 10, vci 100. The system response shows that the command started correctly and directs you to use dspcon or dspcontests to see the results.
node19.1.AXSM.a > tstdelay 1 10 100 Test started; Use dspcon/dspcontests to see test results
Step 4 Execute dspcontests to see the results as displayed by this command. The units of measure for the round trip delay is microseconds.
node19.1.AXSM.a > dspcontests 1 10 100 Connection Id Test Type Direction Result Round Trip Delay ============= ========= ========= ======= ================ 01.0010.00100: OAM Lpbk ingress Success 30000
Step 5 Execute dspcon to see the results as displayed by this command. The line with test results appears towards the end of the display and begins with "Loopback Type." The Direction field shows "ingress," indicating the tstdelay command produced these results. (If tstconseg had been the last test command, this field would say "egress.") The RTD (round trip delay) field shows 30000 microseconds.
node19.1.AXSM.a > dspcon 1 10 100 -------------------------------------------------------------------------- Local : NSAP Address port vpi vci (S) 4700918100000000001A53C82D00000101180100 1.01.01 10 100 Remote : NSAP Address port vpi vci (M) 4700918100000000001A53C82D00000101180100 1.01.01 11 101 -------------------------------------------------------------------------- Conn. Type : VCC Admn Status : ADMN-UP Service Type : ubr1 Rtng Status : -67372037 Controller : 2 -------------------------------------------------------------------------- Local PCR : 14 Remote PCR : 14 Local SCR : 3 Remote SCR : 3 Local CDV : -1 Remote CDV : -1 Local CTD : -1 Remote CTD : -1 Local MBS : 1 Remote MBS : 1 Local CDVT : -1 Remote CDVT : -1 Admin weight : -1 Frame discard: N -------------------------------------------------------------------------- OAM CC Config : DISABLED Statistics : DISABLED -------------------------------------------------------------------------- Loopback Type : OAM Lpbk | Dir: ingress | Status: Success | RTD: 30000 us -------------------------------------------------------------------------- -------------------------------------------------------------------------- Port side Tx : normal Swth side Tx : normal Port side Rx : normal Swth side Rx : normal -------------------------------------------------------------------------- I-AIS/RDI E-AIS/RDI CONDITIONED CCFAIL IfFail Mismatch NO NO NO NO NO NO --------------------------------------------------------------------------
Up Connection
Activate a connection that was previously brought down by the dncon command. (The typical purpose of dncon is some form of operational modification or troubleshooting.)
AXSM
upcon
<ifNum >
<vpi>
<vci>
ifNum | Port number, in the range 1-60. |
vpi | Virtual path identifier. On the AXSM, the range is 1-255. |
vci | Virtual connection identifier. On t he AXSM, the range is 32-65535 for a VCC. For a VPC, the only vci is 0. |
dncon
Log: nolog | State: active | Privilege: GROUP1 |
Up Line
Activates a line on the current card. After you have activated the line, use cnfln to configure the line characteristics such as the type of line (for SONET types, T3, or E3), line signaling, and so on.
|
Note See description of cnfcdsct for important planning considerations before you use upln. |
AXSM
upln
<bay.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. |
dspln, dsplns, cnfln, dnln
Log: nolog | State: active, standby | Privilege: GROUP1 |
Activate line 1 in bay 1.
chicago.1.AXSM.a > upln 1.1
Up Port
The upport command returns a logical port to the up state (or "ups" the port) so the port can again carry traffic. The upport command concludes possible re-configuration or troubleshooting steps. Before you execute upport, you must have downed the port by executing dnport. Throughout the sequence of downing and upping a port, the configuration for the port remains intact whether the logical port is a UNI or an NNI.
The routes for connections vary by interface type:
upport
<ifNum>
ifNum | A logical port number in the range 1-60. Use dspports or dspport as needed to determine which port to bring up. |
dspport, dspports, dnport
Log: nolog | State: active, standby | Privilege: GROUP1 |
Restore port 1 on the current card to operation.
chicago.1.AXSM.a > upport 1
Posted: Mon Oct 2 19:38:33 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.