Table Of Contents
dspabrtparmdft
dspaddr
dspadjlnalm
dspadjlnalmcnt
dspainihopcount
dspalm
dspalmcnf
dspalmcnt
dspalms
dspapsbkplane
dspapsln
dspapslns
dspatmaddr
dspatmimagrp
dspatmln
dspbecnt
dspbert
dspbertcap
dspbkpl
dspcbclk
dspcd
dspcdalms
dspcderrs
dspcdhealth
dspcds
dspcdstatcnf
dspcdstatus
dspcdvtdft
dspchan
dspchancnt
dspchans
dspchantests
dspchassis
dspcli
dspclkalms
dspclksrcs
dspcmdabbr
dspcon
dspconalmcnts
dspconalms
dspconinfo
dspconload
dspconntracebuffer
dspconntracebuffers
dspcons
dspcons-dbg
dspconsegep
dspcontrollers
dspcurclk
dspdate
dspdevalms
dspdeverr
dspdeverrhist
dspdiagcnf
dspdiagerr
dspdiagstat
dspdiagstatus
dspdisk
dspegrbucketcnt
dspenhiisp
dspenvalms
dsperr
dsperrhist
dspetherif
dspfile
dspfltset
dsphotstandby
dspilmi
dspilmiaddr
dspilmicnt
dspilmis
dspimagrp
dspimagrpalm
dspimagrpalms
dspimagrpbucketcnt
dspimagrpcnt
dspimagrps
dspimalnk
dspimalnkalm
dspimalnkalms
dspimalnkbucketcnt
dspimalnkcnt
dspimalnks
dspingbucketcnt
dspintfcongcntr
dspintfcongflags
dspintfcongth
dspipconntask
dspipif
dspipifcache
dsplink
dsplinkalm
dspln
dsplncnt
dsplnload
dsplnpmbucketcnt
dsplns
dspload
dsplog
dsploginmsg
dsplogs
dspmbsdft
dspmempart
dspncdp
dspncdpclksrc
dspncdpclksrcs
dspncdpport
dspncdpports
dspndalms
dspndparms
dspndstatus
dspnodalcongcntr
dspnodalcongflags
dspnodalcongth
dspnodalconstats
dspnodalfd
dspoamsegep
dsppart
dspparts
dsppathtracebuffer
dsppathtracebuffers
dsppathtraceie
dsppathtracenode
dsppathtraceport
dsppingatmaddr
dspabrtparmdft
Display ABR Parameter Defaults—PXM45, PXM1E
The dspabrtparmdft command displays the default ABR parameters for a logical port under PNNI.
Syntax
dspabrtparmdft <portid>
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
Related Commands
addcon, cnfabr, cnfabrtparmdft
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display the default ABR parameters on port ID 1:1.1:1.
8850_NY.8.PXM.a > dspabrtparmdft 1:1.1:1
Default ABR Traffic Parameters For: 1:1.1:1
-----------------------------------
dspaddr
Display Address—PXM45, PXM1E
The dspaddr command displays ATM addresses and associated information for a UNI or IISP. For details on the displayed items, see the addaddr description. The items in the display are as follows:
•
ATM addresses on the port and the length of each
•
Address plan
•
The type of address—internal or external
•
The protocol for advertising the address
•
The choice for address distribution
•
The ID number of transit node
•
The scope—applicable to multi-peer groups only
Syntax
dspaddr <portid>
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
Related Commands
addaddr, deladdr
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Examples
Display the ATM address and other details for port 3:1.1:1.
8850_NY.8.PXM.a > dspaddr 3:1.1:1
47.0091.8100.0002.0003.6b5e.30c0
length: 104 type: internal proto: local
scope: 0 plan: nsap_icd redistribute: false
dspadjlnalm
Display Adjacent Line Alarms—PXM1E
The dspadjlnalm command lets you display the alarm status line for the adjacent back card. To acquire the status, enter the bay and line number for the active back card.
Note
The clradjlnalmcnt command works for only inter-card APS.
Syntax
dspadjlnalm <X.line>
Syntax Description
X
|
X identifies the card. For SRMs, X differs in an MGX 8850 and MGX 8830 chassis:
• X = 2 identifies the UNI/NNI back card on the PXM1E
• X = 15 or 31 identifies an SRM in an MGX 8850 chassis (includes redundant cards in 16 or 32)
• X = 7 is an SRM in an MGX 8830 chassis (includes redundant card in slot 14)
|
Related Commands
dspadjlnalmcnt, clradjlnalmcnt
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
MGX8850.7.PXM1E.a > dspadjlnalm 15.1
Section Alarm State : LOS
Section Stat Alarm State: CurrentESs,CurrentSESs,CurrentSEFSs
Line Stat Alarm State : CurrentSESs,CurrentUASs
Path Stat Alarm State : CurrentSESs,CurrentUASs
dspadjlnalmcnt
Display Adjacent Line Alarm Counters—PXM1E
The dspadjlnalmcnt command lets you display the alarm counters for the adjacent back card. To acquire the status, enter the bay and line number for the active back card.
Note
The clradjlnalmcnt command works for only inter-card APS.
Syntax
dspadjlnalmcnt <bay.line> <intvl>
Syntax Description
bay.line
|
The active bay and line.
|
intvl
|
The time interval to display (0-96). 0 is the current 15-minute interval. 1 is the most recent 15-minute interval. 2 is the next most recent 15-minute interval, and so on. 96 being the oldest 15-minute interval.
|
Related Commands
dspadjlnalm, clradjlnalmcnt
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
MGX88503.7.PXM1E.a> dspadjlnalmcnt 15.1 1
dspainihopcount
Display AINI Hop Count—PXM45, PXM1E
The dspainihopcount command shows the enable or disable status and the limit for the number of hops a connection can have over AINI links. The counter is the Hop Counter Information Element. This configuration applies to the entire node.
Syntax
dspainihopcount
Syntax Description
This command takes no parameters.
Related Commands
cnfainihopcount
Attributes
Log: yes
|
State: active, standby
|
Privilege: ANYUSERP
|
Example
Display the current configuration for AINI hop count.
8850_NY.8.PXM.a > dspainihopcount
AINI Hop Counter Generation: enable
8850_NY.8.PXM.a >
dspalm
Display Alarm—PXM1E
The dspalm command on the PXM1E displays line alarms on either the UNI/NNI back card or an SRM. See cnfalm for a description of the types of alarms you can see. In addition to the configurable alarm types, the output also shows instances of loss of cell delineation (LOCD). (For line alarms on an AXSM, see the dspalm description in the AXSM-specific documentation.)
Note
In the current release, this command applies to the PXM1E only.
Syntax
dspalm -<lineType> <X>.<line>
Syntax Description
lineType
|
The line type varies for each card, as follows:
• PXM back card: -ds3, -sonet, -plcp, -e1, -ds1
• SRME: -sonet
• SRM-3T3: -ds3
|
X
|
X identifies the card. For SRMs, X differs in an MGX 8850 and MGX 8830 chassis:
• X = 2 identifies the UNI/NNI back card on the PXM1E
• X = 15 or 31 identifies an SRM in an MGX 8850 chassis (includes redundant cards in 16 or 32)
• X = 7 is an SRM in an MGX 8830 chassis (includes redundant card in slot 14)
|
line
|
The range for line numbers depends on the card type and is from 1 to the highest numbered line on the back card, as follows:
• PXM1E back card: 1-12
• SRM-3T3: 1-3
• SRME: 1
• For T1 or E1 back card: 1-16
|
Related Commands
dspln, dsplns, dspalmcnts
Attributes
Log: yes
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display alarms for line 1 on the UNI/NNI back card. In this case, the back card has E3 lines.
Unknown.8.PXM.a > dspalm -e3 2.1
Statistical Alarm State: No Statistical Alarms
dspalmcnf
Display Alarm Configuration—PXM1E
The dspalmcnf command on the PXM1E lets you display lines alarms on either the UNI/NNI back card or an SRM. For line alarms on an AXSM, see the other version of the dspalmcnt command.
Syntax
dspalmcnf -<lineType> <X.line>
Syntax Description
-lineType
|
The possible line types depend on what X.line identifies, as follows:
• For X = 2, possible line types for PXM1E back card are as follows:
-sonetsec - Displays the section alarms for the given sonet line.
-sonetline - Displays the line alarms for the given sonet line.
-sonetpath -Displays the path alarms for the given sonet line.
-ds3 - Displays the statistical alarms for the given DS3 line.
-plcp - Displays alarms for Physical Layer Convergence Procedure (PLCP).
• For X = 7, 15, or 31, possible line types for SRMs are as follows:
-sonetsec - Displays the section alarms for the given SONET line.
-sonetline - Displays the line alarms for the given SONET line.
-sonetpath -Displays the path alarms for the given SONET line.
-ds3 - Displays the statistical alarms for the given DS3 line.
|
X.line
|
The X field identifies either of the following:
• The UNI/NNI back card in bay 2 of the PXM1E
• The logical slot of the SRM under the control of a PXM1E
The value for X can be one of the following:
• 2 identifies the UNI/NNI back card attached to a PXM1E.
• In an MGX 8850 chassis, 15 or 31 identifies the logical slot number of the active SRM (regardless of physical slot number).
• In an MGX 8830 chassis, 7 identifies the logical slot number of the active SRM (regardless of physical slot number).
The values for line depends on the type of card. Possible values are as follows:
• SRME: 1
• SRM-3T3: 1-3
• PXM1E back card: 1-16 (whatever is the highest line number on the card)
|
Related Commands
cnfalm, dspalm, dspalms
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display the SONET section alarm configuration for the SRME in slot 31.
Unknown.8.PXM.a > dspalmcnf -sonetsec 31.1
Section Stat Alarm Severity: None
15min Threshold 24hr Threshold
dspalmcnt
Display Alarm Counters—PXM1E
The dspalmcnt command on the PXM1E lets you display lines alarms on either the UNI/NNI back card or an SRM. For line alarms on an AXSM, see the other version of the dspalmcnt command.
Note
In the current release, this command applies to the PXM1E only.
Syntax
dspalmcnt -<lineType> <X.line>
Syntax Description
lineType
|
The line type varies for each card, as follows:
• PXM back card: -ds3, -sonet, -plcp, -e1, -ds1
• SRME: -sonet
• SRM-3T3: -ds3
|
X
|
X identifies the card. For SRMs, X differs in an MGX 8850 and MGX 8830 chassis:
• X = 2 identifies the UNI/NNI back card on the PXM1E
• X = 15 or 31 identifies an SRM in an MGX 8850 chassis (includes redundant cards in 16 or 32)
• X = 7 is an SRM in an MGX 8830 chassis (includes redundant card in slot 14)
|
line
|
The range for line numbers depends on the card type and is from 1 to the highest numbered line on the back card, as follows:
• PXM1E back card: 1-16 (whatever is the highest number line on the back card)
• SRM-3T3: 1-3
• SRME: 1
|
Related Commands
dspln, dsplns, clralmcnt
Attributes
Log: yes
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display the alarm count for the SRME in slot 31. To see the alarm configuration, use dspalmcnf.
Unknown.8.PXM.a > dspalmcnt -sonet 31.1
dspalms
Display Alarms—PXM1E
Display all line-related alarms on the card. RFC 2258 describes the alarm categories. The display can easily scroll for many pages if more than one line is active. See cnfalm for a description of types of alarms you might see. In addition to the alarms from cnfalm, the dspalms command also displays instances of loss of cell delineation (LOCD).
Syntax
dspalms
Syntax Description
This command takes no parameters.
Related Commands
dspalm, clralm
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display alarms for the lines on the current card.
pxm1enode.7.PXM.a > dspalms
---------------------------------------------
Alarm State : XmtRAI,RcvLOF,RcvLOS,RcvOtherFailure
Statistical Alarm State: UAS15minAlarm,UAS24hrAlarm
Alarm State : XmtRAI,RcvLOF,RcvLOS,RcvOtherFailure
Statistical Alarm State: UAS15minAlarm,UAS24hrAlarm
Statistical Alarm State: No Statistical Alarms
LOCD Alarms State : Clear
Statistical Alarm State: No Statistical Alarms
LOCD Alarms State : Clear
Type <CR> to continue, Q<CR> to stop:
Statistical Alarm State: No Statistical Alarms
LOCD Alarms State : Clear
Statistical Alarm State: No Statistical Alarms
LOCD Alarms State : Clear
Statistical Alarm State: No Statistical Alarms
LOCD Alarms State : Clear
Statistical Alarm State: No Statistical Alarms
LOCD Alarms State : Clear
dspapsbkplane
Display APS Backplane—PXM1E
The dspapsbkplane output states whether or not the APS mini-backplane is properly seated and engaged with the back cards. (See the addapsln description for details on automatic protection switching (APS).
Caution 
If you are installing a 4-OC3 back card on the PXM1E but plan to upgrade to an 8-OC3 back card and use APS, the upgrade can be graceful only if an APS mini-backplane already resides in the chassis. You can install it before powering up the switch even though it is not immediately used.
If you have to install the mini-backplane after the switch starts carrying live traffic, service disruption is unavoidable.
See the hardware installation guide for information on installing the APS assembly to the backplane.
Syntax
dspapsbkplane
Syntax Description
Related Commands
addapsln, cnfapsln, delapsln, dspapsln, dspapslns, switchapsln, clrbecnt, dspbecnt
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Example of dspapsbkplane when no APS mini-backplane is in the backplane.
Mumbai.7.PXM.a > dspapsbkplane
This feature does not apply to the card present in this slot
SRME Top Bay:APS Back Plane Not Engaged or Adjacent Back Card Not
SRME Bottom Bay:APS Back Plane Not Engaged or Adjacent Back Card Not
dspapsln
Display APS Line—PXM45, PXM1E
The dspapsln command displays the configuration of an APS line on a Service Resource Module (SRM) or the PXM1E UNI/NNI back card. This command can be executed for either a working line or a protection line.
See the addapsln command for an explanation of automatic protection switching (APS).
Note
In the current release, the PXM45 does not support the SRM.
Syntax
dspapsln <working-slot.bay.line>
Syntax Description
working-slot
|
The working-slot identifies either of the following:
• The UNI/NNI back card in of the PXM1E
• The logical slot of the SRM under the control of a PXM1E
The value for working-slot can be one of the following:
• 2 identifies the UNI/NNI back card attached to a PXM1E.
• 15 or 31 in an MGX 8850 chassis identifies the logical slot number of the active SRM (regardless of physical slot number).
• 7 in an MGX 8830 chassis identifies the logical slot number of the active SRM (regardless of physical slot number).
|
bay
|
The bay depends on the card type and the chassis, as follows:
• PXM1E back card: always 1
• SRME in an MGX 8850 chassis:
– upper bay: 1
– lower bay: 2
• SRME in an MGX 8830 chassis: always 1
|
line
|
The values for line depends on the type of card, as follows:
• SRME: 1
• PXM1E back card: 1-4
|
Related Commands
addapsln, cnfapsln, delapsln, dspapslns, switchapsln, dspapsbkplane, clrbecnt, dspbecnt
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
dspapslns
Display APS Lines—PXM1E
Displays all working and protection APS lines on a card. This command can be executed only on an active card. After identifying a particular APS line, you can use dspapsln to view details about the line.
See the addapsln command for an explanation of Automatic Protection Switching (APS).
Syntax
dspapslns
Syntax Description
This command takes no parameters.
Related Commands
addapsln, cnfapsln, delapsln, dspapsln, switchapsln, dspapsbkplane, clrbecnt, dspbecnt
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
dspatmaddr
Display ATM Addresses—PXM45, PXM1E
The output of dspatmaddr includes configured ATM addresses, configured ILMI address prefixes, and ATM addresses registered by way of the ILMI address registration procedure.
Syntax
dspatmaddr <portid>
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
Related Commands
dspaddr
Attributes
Log: yes
|
State: active, standby
|
Privilege: ANYUSER
|
Examples
Display the ATM addresses and prefixes on port 2:1.1:1.
Geneva.7.PXM.a > dspatmaddr 2:1.1:1
Configured Port Address(es):
39.840f.8011.3744.0000.0040.1005.3456.7834.7777.77
length: 160 type: internal proto: local
scope: 0 plan: nsap-dcc redistribute: false
ILMI Configured Port Prefix(es):
47.0091.8100.0000.0000.0ca7.9e01
88.8888.8888.0000.0000.0000.0000
ILMI Registered Port Address(es):
47.0091.8100.0000.0000.0ca7.9e01.1234.5678.9012.34
88.8888.8888.0000.0000.0000.0000.1234.5678.9012.34
length: 160 type: internal proto: local
scope: 0 plan: nsap-dcc redistribute: false
dspatmimagrp
Display ATM IMA Group—PXM1E
The dspatmimagrp command displays the ATM payload scramble enable for an IMA group. The command that lets you enable or disable payload scrambling is cnfatmimagrp. The setting applies to all links in an IMA group.
Syntax
dspatmimagrp <group>
Syntax Description
group
|
The group identifier consists of a bay number as well as a group number in the format bay.group, as follows:
• bay: always 2 on the PXM1E
• group: 1-16
|
Related Commands
cnfatmimagrp
Attributes
Log: yes
|
State: active
|
Privilege: ANYUSER
|
Example
Display the payload scrambling enable status for IMA group 1.
PXM1E.7.PXM.a > dspatmimagrp 2.1
Group HCScoset PayloadScramble
------- --------- ---------------
dspatmln
Display ATM Line—PXM45, PXM1E
Displays the cell header configuration for the line that was set using cnfatmln. The display indicates NNI or UNI cell headers.
Note
In the current release, this command does not apply to a PXM45.
Syntax
dspatmln <X.line>
Syntax Description
X
|
X identifies the card. For SRMs, X differs in an MGX 8850 and MGX 8830 chassis:
• X = 2 identifies the UNI/NNI back card on the PXM1E
• X = 15 or 31 identifies an SRM in an MGX 8850 chassis (includes redundant cards in 16 or 32)
• X = 7 is an SRM in an MGX 8830 chassis (includes redundant card in slot 14)
|
line
|
The range for line numbers depends on the card type and is from 1 to the highest numbered line on the back card, as follows:
• PXM1E back card: 1-16 (whatever is the highest number line on the back card)
• SRM-3T3: 1-3
• SRME: 1
|
Related Commands
cnfatmln, clratmlncnt
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display the ATM line configuration for line 1 on the PXM1E UNI.NNI card.
Unknown.8.PXM.a > dspatmln 2.1
LineNum HCScoset PayloadScramble NullCellHdr NullCellPayload
------- --------- --------------- ----------- ---------------
? Enable Enable 0x00000001 6a
dspbecnt
Display Bit Error Count—PXM1E
The dspbecnt command displays the APS-related bit error counters.
Syntax
dspbecnt <working-slot.bay.line>
Syntax Description
working-slot
|
The working-slot identifies either of the following:
• The UNI/NNI back card in of the PXM1E
• The logical slot of the SRM under the control of a PXM1E
The value for working-slot can be one of the following:
• 2 identifies the UNI/NNI back card attached to a PXM1E.
• 15 or 31 in an MGX 8850 chassis identifies the logical slot number of the active SRM (regardless of physical slot number).
• 7 in an MGX 8830 chassis identifies the logical slot number of the active SRM (regardless of physical slot number).
|
bay
|
The bay depends on the card type and the chassis, as follows:
• PXM1E back card: always 1
• SRME in an MGX 8850 chassis:
– upper bay: 0
– lower bay: 1
• SRME in an MGX 8830 chassis: always 1
|
line
|
The values for line depends on the type of card, as follows:
• SRME: 1
• PXM1E back card: 1-4
|
Related Commands
addapsln, clrbecnt, cnfapsln, delapsln, dspapsln, dspapslns, switchapsln, dspapsbkplane
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
MGX8850.7.PXM1EE.a > dspbecnt 7.2.9
Working Section 1 7.2.9 :
24 Hour Bit Error Count 0
15 Minute Bit Error Count 130
15 Second Bit Error Count 0
Working Section 2 8.2.9 :
24 Hour Bit Error Count 0
15 Minute Bit Error Count 30413
15 Second Bit Error Count 2307
dspbert
Display Bit Error Rate Test—PXM45, PXM1E
The dspbert command lets you display the configuration and current data for a bit error rate test (BERT). Only one BERT session at a time can run in a particular bay. A dspbert command also runs on the AXSM-E. Refer to that description for BERT on an AXSM-E.
The information this command displays is as follows:
•
The user Id of the person who started the BERT session
•
Start date and time
•
Current date and time
•
Physical slot number running BERT
•
Line number
•
Port number, if applicable (port is an optional parameter for configuring a BERT session)
•
DS0 speed
•
Type of test
The screen layout includes the following:
•
One or more rows for the results of the BERT: bit count, bit error count, bit error rate, and so on.
•
Whether and how many times errors were injected.
Syntax
dspbert <SMbay>
Syntax Description
SMbay
|
To specify a bay, enter one of the following numbers:
• 0: upper bay
• 1: lower bay
For an MGX 8830 chassis, SMbay must be 0.
|
Related Commands
addbert, delbert, dspbertcap
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Display the BERT session in the lower bay. The target is line 1 of an FRSM in slot 25.
modena1.7.PXM.a > dspbert 1
Current Date : 05/07/2002
Physical Slot Number : 25
Line Number : 1 (Line test)
Device To Loop : Local Loopback
BERT Pattern : All Zeroes Pattern
Bit Count Received : 3107466159
dspbertcap
Display BERT Capabilities—PXM1E
The dspbertcap command lists the capability of a particular line or port on a service module to support specific BERT patterns or loopbacks. The numbers in the dspbertcap output are the possible pattern or loopback numbers you can provide to the cnfbert command. For example, a particular service module may support 12 of the 32 possible BERT patterns, so you would use the dspbertcap command for that service module to see what you can provide to the cnfbert command.
Only the SRME supports smart jack loopbacks, so the dspbertcap output for loopbacks shows where the capability requires an SRME.
Note
The current release supports this command on the PXM1E only.
Also, the current release does not support DDS patterns.
Syntax
dspbertcap <SM Interface> <Test Option>
Syntax Description
SM Interface
|
The format of Service Module Interface is: SMslot.SMLine[.SMport], as follows:
• SMslot has a value that depends on the chassis model, as follows:
– For an MGX 8850 chassis, the ranges are 1-6, 9-14, 17-22, 25-30.
– For an MGX 8830 chassis, the ranges are 3-6 and 10-13.
• SMLine has a range from 1 though the maximum number of lines on the card.
• The optional SMport has a value from 1 though the maximum ports supported by the service module.
|
Test Option
|
Type one of the following numbers to select the capability to display:
• 1: BERT capability
• 2: Loopback capability
|
Related Commands
dspbert, cnfbert
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Determine the pattern list for line 1 of the card in slot 3. In this example, the card is an FRSM-2CT3.
pxm1e.7.PXM.a > dspbertcap 3.1 1
1: allZeros, 2: allOnes, 3: altOneZero,
4: doubleAltOnesZeros 6: oneIn8, 8: threeIn24,
18: twoE9MinusOne, 20: twoE11MinusOne 21: twoE15MinusOne,
24: twoE20MinusOne, 25: twoE20MinusOneQRSS 28: twoE23MinusOne
Device to loop options supported:
---------------------------------
FarEnd Loopback: All listed patterns supported
12: lineInband, 13: lineLoopbackESF
18: smartJackInband -Supported only on SRME
Local Loopback: All listed patterns supported
No Loopback: All listed patterns supported
Use cnfbert and delbert cli to configure and delete bert
Display the loopback capabilities of the same card and line.
pxm1e.7.PXM.a > dspbertcap 3.1 2
1: farEndLineLoopback: supported
12: lineInband, 13: lineLoopbackESF
17: smartJackInband - Supported only on SRME
3: remoteLineLoopback: supported
5: localLoopback: supported
Use addlpback and dellpback cli to add and delete loopback codes
Display the BERT capabilities of line 1 of the CESM in slot 20.
pxm1e.7.PXM.a > dspbertcap 20.1 1
1: allZeros, 2: allOnes, 3: altOneZero,
4: doubleAltOnesZeros 6: oneIn8, 8: threeIn24,
18: twoE9MinusOne, 20: twoE11MinusOne 21: twoE15MinusOne,
24: twoE20MinusOne, 25: twoE20MinusOneQRSS 28: twoE23MinusOne
Device to loop options supported:
---------------------------------
FarEnd Loopback: All listed patterns supported
12: lineInband, 13: lineLoopbackESF
18: smartJackInband -Supported only on SRME
Local Loopback: All listed patterns supported
No Loopback: All listed patterns supported
Use cnfbert and delbert cli to configure and delete bert
Display the loopback capabilities of line 1 of the CESM in slot 20.
pxm1e.7.PXM.a > dspbertcap 20.1 2
1: farEndLineLoopback: supported
12: lineInband, 13: lineLoopbackESF
17: smartJackInband - Supported only on SRME
3: remoteLineLoopback: supported
5: localLoopback: supported
Use addlpback and dellpback cli to add and delete loopback codes
dspbkpl
Display Backplane—PXM45, PXM1E
The dspbkpl command shows the following types of information about the backplane:
•
Card type (a hexadecimal number)
•
Chassis-level part number and revision number
•
PCB 73-level part number
•
Chassis serial number
•
CLEI code
•
PCB 28-level part number
Syntax
dspbkpl
Syntax Description
This command takes no parameters.
Related Commands
dspcd
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Display details about the backplane.
Unknown.8.PXM.a > dspbkpl
Chassis 800-level P/N: 800-03145-07
Chassis 800-level rev: B0
PCB 73-level P/N: 73-3094-02
Chassis serial number: SAA03190530
PCB 28-level P/N: 28-2681-02
dspcbclk
Display Cellbus Clock—PXM45, PXM1E
The dspcbclk command displays the following for individual Cellbuses:
•
The Cellbuses that support only the default clock rate of 21 MHz and the Cellbuses that support either 21 Mhz or 42 Mhz rates
•
Whether an individual Cellbus is running at the standard rate of 21 MHz or the double-speed rate of 42 Mhz
•
The card slots that reside on each of the eight Cellbuses
The application of dspcbclk and cnfcbclk is the clocking for the Route Processor Module Premium (RPM-PR). The RPM-PR runs much more efficiently at 42 Mhz, but not all card slots can receive this double-speed clock. Use dspcbclk to see which slots can receive 42 Mhz, then use cnfcbclk to configure the applicable Cellbus for double-speed clocking.
Syntax
dspcbclk
Syntax Description
This command takes no parameters.
Related Commands
cnfcbclk
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display the current Cellbus clock configuration. The display shows that all Cellbuses currently have the default speed of 21 Mhz.
pop20two.8.PXM.a > dspcbclk
CellBus Rate (MHz) Slots Allowable Rates (MHz)
----------------------------------------------------------
dspcd
Display Card—PXM45, PXM1E
The dspcd command displays card-level details. On a PXM, you can display information about the PXM or another card. On a service module, you can display details for only that service module. Different card types result in variations in the display. (See the Examples section.)
A list of information in the dspcd output follows. Refer to the Syntax Description and the Examples for additional details. In general, the display shows:
•
Serial numbers.
•
Front and back card types and the status of each.
•
Runtime and boot firmware revision numbers. (See the loadrev description for an explanation of how to interpret the revision field.)
•
Status, possibly including the reason for the last reset and state of the integrated alarm.
•
When dspcd is entered on the CLI of a service module:
–
A count of configured lines, ports, and connections
–
Card-level SCT number
–
The APS-related mode of an AXSM/A or AXSM/B (see the enableaxsmbaps description)
•
On the PXM only:
–
General node information, such as nodename, date, and time
–
Crossbar status (PXM45 only—the PXM1E does not have crossbar ASICs)
–
The version of firmware that is currently running
–
Back card mismatch information if you specify a slot number
On a service module, the dspcd display shows the physical lines that constitute a port group and the maximum number of connections in that port group. A port group consists of one to many physical lines. This maximum connection count is a function of the line type (OC-3, OC-12, and so on). The port group information also shows the number of existing SVCs, SPVCs, and SPVPs. This part of the dspcd output can help you configure resource partitions by showing the maximum number of supported connections. If a particular resource partition has close to the maximum supported by hardware on a line, few or no connections would be possible in another partition on the same line.
Note
The total number of connections in the dspcd output includes control VCs. The types of control VCs are SSCOP, PNNI-RCC, and ILMI (if ILMI is enabled). To see connection counts that do not include control VCs, use dsppnport.
Syntax
dspcd [slot]
Syntax Description
slot
|
The optional slot parameter is available on a PXM only and refers to the physical slot of a card other than the PXM where you are using the dspcd command. Entering a slot number on the PXM displays information about the card in that slot. If you do not include a slot number on the PXM, the display applies to only the current PXM.
For a service module, slightly different information appears when you run dspcd on the PXM rather than the service module. For example, when you enter dspcd slot on the PXM, it shows the current version of the firmware that is running on the card. See the Examples section to compare display contents.
|
Related Commands
dspcds, dsppnport, dspversion
Attributes
Log: no
|
State: active, standby, init
|
Privilege: ANYUSER
|
Examples
Display the current PXM45.
Note
The "P1" at the end of the software revision and boot firmware revision numbers shows that these versions are pre-release. Refer to the loadrev or setrev description for details.
M8850_LA System Rev: 03.00 Dec. 10, 2002 19:27:21 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: SBK044900QN SBK044200J8 SAK0403005Q
Prim SW Rev: 3.0(6.1)P1 --- ---
Sec SW Rev: 3.0(6.1)P1 --- ---
Cur SW Rev: 3.0(6.1)P1 --- ---
Boot FW Rev: 3.0(6.1)P1 --- ---
800-level Part#: 800-06147-08 800-05787-02 800-05052-03
CLEI Code: BAA670YCAA BA7IBCLAAA 0000000000
Reset Reason: On Reset From Shell
Miscellaneous Information:
Crossbar Slot Status: Present
Backcard Mismatch Reasons
-------------------------
Display the AXSM in slot 1.
M8850_LA.7.PXM.a > dspcd 1
M8850_LA System Rev: 03.00 Dec. 10, 2002 19:27:54 GMT
MGX8850 Node Alarm: CRITICAL
Slot Number: 1 Redundant Slot: NONE
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
Reserved Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
State: Active Active Active
Serial Number: SAK0350007N SAK0346003F SBK043902FE
Prim SW Rev: 3.0(6.1)P1 --- ---
Sec SW Rev: 3.0(6.1)P1 --- ---
Cur SW Rev: 3.0(6.1)P1 --- ---
Boot FW Rev: 3.0(6.1)P1 --- ---
800-level Part#: 800-05774-05 800-05383-01 800-05383-01
CLEI Code: BAA1BADAAA 0000000000 BAI9ADTAAA
Reset Reason: On Power up
Miscellaneous Information:
Crossbar Slot Status: Present
Backcard Mismatch Reasons
-------------------------
The following example is added to illustrate the difference between service module information as it appear on the PXM45 and the service module itself. It starts with a cc to the AXSM.
M8850_LA.1.AXSM.a > dspcd
Front Card Upper Card Lower Card
---------- ---------- ------------
Card Type: AXSM-4-622 SMFIR-2-622 SMFIR-2-622
State: Active Present Present
Serial Number: SAK0350007N SAK0346003F SBK043902FE
Boot FW Rev: 3.9(6.1)P1 --- ---
SW Rev: 3.9(6.1)P1 --- ---
Orderable Part#: 800-05774-05 800-05383-01 800-05383-01
PCA Part#: 73-4504-2 73-4125-1 73-4125-1
CLEI Code: BAA1BADAAA 0000000000 BAI9ADTAAA
Reset Reason: Power ON Reset
Card Operating Mode: AXSM-A
SCT File Configured Version: 1
SCT File Operational Version: 1
#Lines #Ports #Partitions #SPVC #SPVP #SVC
------ ------ ----------- ------- ------- -------
#Chans supported:32512 Lines:1.1
#Chans supported:32512 Lines:1.2
#Chans supported:32512 Lines:2.1
#Chans supported:32512 Lines:2.2
The controller in this example is a PXM1E. Display first the card in slot 31 then the card in slot 32, the SRM slots. For slot 31 (the logical slot), note that the "Inserted Card" field in the Front Card columns is blank, The second display shows that an SRM exists in slot 32.
Unknown.8.PXM.a > dspcd 31
Unknown System Rev: 03.00 May. 09, 2002 22:58:51 GMT
MGX8850 Node Alarm: MAJOR
Slot Number 31 Redundant Slot: 32
Inserted Card: --- SMFIR_1_155
Reserved Card: UnReserved UnReserved
Serial Number: LKJHGFDSAPO SAG053355HF
800-level Part#: --- 800-14460-02
CLEI Code: --- ZZXXCCVVBB
Reset Reason: On Power up
Miscellaneous Information:
Unknown System Rev: 03.00 May. 09, 2002 22:58:51 GMT
MGX8850 Node Alarm: MAJOR
Crossbar Slot Status: No Crossbar
Unknown.8.PXM.a > dspcd 32
Unknown System Rev: 03.00 May. 09, 2002 22:59:06 GMT
MGX8850 Node Alarm: MAJOR
Slot Number 32 Redundant Slot: 31
Inserted Card: SRME_OC3 SMFIR_1_155
Reserved Card: UnReserved UnReserved
Serial Number: ABCDEFGHIJK SAG053355H1
800-level Part#: 800-23700-02 800-14460-02
CLEI Code: QWERTYYUIO AASSDDFFGG
Reset Reason: On Reset From Shell
Miscellaneous Information:
Unknown System Rev: 03.00 May. 09, 2002 22:59:06 GMT
MGX8850 Node Alarm: MAJOR
Crossbar Slot Status: No Crossbar
Display the active PXM1E then the standby card. The display shows that one lower back card is missing.
jan-4oc3 System Rev:03.09 Sep. 11, 2002
Slot Number 7 Redundant Slot: 8
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: PXM1E-4-155 UI Stratum3 SMFIR_4_OC3
Reserved Card: PXM1E-4-155 UI Stratum3
State: Active Active Active
Serial Number: SAG05385FE5 SBK043000TK SAG05435ZB8
Prim SW Rev: 3.0(1.39)P1 --- ---
Sec SW Rev: 3.0(1.39)P1 --- ---
Cur SW Rev: 3.0(1.39)P1 --- ---
Boot FW Rev: 3.0(1.9)P1 --- ---
800-level Part#: 800-18588-02 800-05787-02 800-18664-01
CLEI Code: 0 BA7IBCLAAA 0
Reset Reason: On Reset From Shell
Miscellaneous Information:
Crossbar Slot Status: EMPTY
Backcard Mismatch Reasons
-------------------------
Display the standby PXM1E.
jan-4oc3.7.PXM.a > dspcd 8
jan-4oc3 System Rev:03.09 Sep. 11, 2002
Slot Number 8 Redundant Slot: 7
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: PXM1E-4-155 UI Stratum3 ---
Reserved Card: PXM1E-4-155 UI Stratum3
State: Standby Active Empty Resvd
Serial Number: SAG05385FFH SBK043300ET ---
Prim SW Rev: 3.0(1.39)P1 --- ---
Sec SW Rev: 3.0(1.39)P1 --- ---
Cur SW Rev: 3.0(1.39)P1 --- ---
Boot FW Rev: 3.0(10.118)P2 --- ---
800-level Part#: 800-18588-02 800-05787-02 ---
CLEI Code: BA7IBCLAAA ---
Reset Reason: On Reset From Shell
Miscellaneous Information:
Crossbar Slot Status: EMPTY
Reserved Back Card Missing :ALARM
Backcard Mismatch Reasons
-------------------------
dspcdalms
Display Card Alarms—PXM45, PXM1E
Use dspcdalms to display alarms that have been reported by any of the following:
•
A service module (a service module also reports LMI alarms)
•
Applications on the PXM that detect service module alarms (by slot)
•
The PXM1E UNI.NNI back card
•
A Service Resource Module (SRM)
If dspcdalms shows an alarm for one of the following parts of a card, you can cc to that card and use one of the following commands:
•
Line (dsplns and dspln)
•
Port (dspports and dspport)
•
LMI (dsplmi, dspfdr, dspfdrs, and dspfdrstat)
•
Connection (dspcons and dspcon) on a service module or PXM1E UNI/NNI back card
•
Channel (dspchans or dspchan on a PXM1E only)
A service module can report alarms for all of the preceding categories. In addition to the preceding commands, you can also use dspalm and dspalms on a service module. A PXM1E UNI/NNI back card can report all preceding categories.
The shelf manager reports hardware, card state, and disk alarms. For example, the shelf manager may detect an alarm for the hardware in a service module slot, or running dspcdalms on the standby PXM may report a hard disk problem. See Example section.
Note
The feeder alarms fit in the category of LMI alarms. See Example section for an illustration. If the switch has a feeder and the dspcdalms commands shows an LMI alarm, try the feeder-specific commands to check for feeder problems. If no feeder alarm is detected, use the dsplmi command.
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
•
Critical, indicating complete, non-recoverable failure, loss of data, and do on. The failed entity must be restored. A power failure or a disconnected line is an example.
•
Major, indicating service-affecting errors. This event indicates that a major service is damaged or lost, but the existing traffic is not affected.
•
Minor, indicating non-service affecting errors or errors on a remote node. Corrective action is appropriate to prevent a serious fault from developing. An example is a fan failure, where no subscribers are immediately affected, but calamity could result if the situation persists. Note that an accumulation of lower-level alarms does equal a higher-level alarm.
The dspcdalms command is part of a hierarchy of troubleshooting commands. Frequently, dspcdalms follows the higher-level command dspndalms.
Syntax
dspcdalms [slot]
Syntax Description
slot identifies a particular slot.
Related Commands
PXM45: dspcdstatus, dspndalms, dspswalms, dspclkalms
PXM1E: dspcdstatus, dspndalms, dspswalms, dspclkalms, dspalm, dspalms
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Examples
Display card-level alarms for the card in slot 5.
M8850_LA.8.PXM.a > dspcdalms 5
Alarm Type Critical Major Minor
---------- -------- ------- -------
Display card alarms without specifying a slot.
M8850_LA.8.PXM.a > dspcdalms
Slot Critical Major Minor || Slot Critical Major Minor
---- -------- ------- ------- || ---- -------- ------- -------
Use dspcdalms <slot> to see more detail.
dspcderrs
Display Card Errors—PXM45, PXM1E
Display information about card errors.
Syntax
dspcderrs
Related Commands
clrerr
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display all card errors.
wilco.7.PXM.a > dspcderrs
08/05/95-18:53:05 tRootTask 3 Task failed : scm
09/05/95-09:14:08 tRootTask 3 Task failed : scm
dspcdhealth
Display Card Health—PXM45, PXM1E
The dspcdhealth command displays a list of trouble conditions on a PXM and suggested remedies. The valid targets are PXMs. You can specify either the current PXM or the other PXM.
Syntax
dspcdhealth [slot]
Syntax Description
slot
|
The slot number is one of the following:
• In a Cisco MGX 8950 or MGX 8850 chassis: 7 or 8
• In a Cisco MGX 8830 chassis: 1 or 2
|
Related Commands
None
Attributes
Log: no
|
State: active, standby, init
|
Privilege: ANYUSER
|
Examples
The first example shows a PXM with only one problem.
London21.7.PXM.a > dspcdhealth 7
* PXM Failed for the following reasons:
* ====== =================
* 1. BRAM Clr Valid Replace PXM Front Card
The second example shows an extensive list of trouble conditions.
London21.7.PXM.a > dspcdhealth 7
* PXM Failed for the following reasons:
* ====== =================
* 1. BRAM Clr Valid Replace PXM Front Card
* 2. BRAM Read Valid shellConn cmd: shmRecoverRbldDisk or shmRecoverClrallcnf
* 3. BRAM Ver Mismatch shellConn cmd: shmRecoverRbldDisk or shmRecoverClrallcnf
* 4. Disk Read Valid shellConn cmd: shmRecoverClrallcnf
* 5. Disk Ver Mismatch shellConn cmd: shmRecoverClrallcnf
* 6. Disk Not Synch shellConn cmd: shmRecoverClrallcnf
* 7. BRAM access failure Replace PXM Front card
* 8. FC Mismatch Program FC NVRAM or Replace FC
* 9. FC NVRAM Read Fail Program FC NVRAM or Replace FC
* 10. Image Mismatch Load right image
* 11. BRAM Non Native CLI cmd: forcecdnative
* 12. Disk Non Native CLI cmd: forcecdnative
* 13. Disk Access Fail Reseat the Disk/FC or Replace Disk
* 14. Lower BC NVRAM Read Program its NVRAM or Replace it
* 15. Upper BC NVRAM Read Program its NVRAM or Replace it
* 16. Lower BC Mismatch Program its NVRAM or Replace it
* 17. Upper BC Mismatch Insert a lower BC
* 18. Lower BC Missing Program its NVRAM or Replace it
* 19. Upper BC Missing Insert an upper BC
* 20. Software ver. mismatch Load correct version image
* 21. Memory Init Fail CLI cmd: resetcd
* 22. Timer Init Fail CLI cmd: resetcd
* 23. EPID Init Fail CLI cmd: resetcd
* 24. HW Init Fail Re-seat the card
dspcds
Display Cards—PXM45, PXM1E
Displays high-level information for all the cards in the node. For more detailed information about a card, execute dspcd on the CLI of that card. The information that dspcds provides is the:
•
Revision level of the boot firmware
•
Revision level of the system software
•
Date and time of command execution, including GMT offset
•
Backplane serial number and its hardware revision level
•
Type of card in the front and back slots and the (active/standby) state of each
•
Alarm status for each card and the shelf itself
•
Redundancy configuration for each slot
Syntax
dspcds
Related Commands
dspcd, dspred, dspversion
Attributes
Log: no
|
State: active, standby, init
|
Privilege: ANYUSER
|
Examples
Display the cards in the current MGX 8830 switch.
Unknown System Rev: 03.00 Mar. 01, 2002 20:19:31 GMT
Chassis Serial No: SCA053000KM Chassis Rev: A0 GMT Offset: 0
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----
01 Active/Active PXM1E-4-155 CRITICAL 02 PRIMARY SLOT
02 Standby/Active PXM1E-4-155 NONE 01 SECONDARY SLOT
03 Active/Empty RPM_PR NONE NA NO REDUNDANCY
04 Active/Active FRSM_2CT3 NONE NA NO REDUNDANCY
05 Boot/Empty FRSM_2CT3 NONE NA NO REDUNDANCY
06 Boot/Empty CESM_8T1 NONE NA NO REDUNDANCY
07 Active/Active SRM_3T3 NONE 14 PRIMARY SLOT
11 Active/Active VISM_PR_8T1 MINOR 12 PRIMARY SLOT
12 Standby/Active VISM_PR_8T1 NONE 12 SECONDARY SLOT
13 Boot/Empty AUSMB_8T1 NONE NA NO REDUNDANCY
14 Standby/Active SRM_3T3 NONE 07 SECONDARY SLOT
Display information for all cards in the MGX 8850 switch. Note that the card state for the RPM in
slot 9 is "Active/Active." Although the dspcds command shows the presence of the back card, the dspcd command does not have the ability to show what type the back card is (so it just shows "Unknown").
M8850_LA.8.PXM.a > dspcds
M8850_LA System Rev: 03.00 Feb. 21, 2002 20:12:33 PST
Chassis Serial No: SAA03230375 Chassis Rev: B0 GMT Offset: -8
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----
01 Active/Active AXSM_4OC12 NONE 02 PRIMARY SLOT
02 Standby/Active AXSM_4OC12 NONE 01 SECONDARY SLOT
03 Active/Active AXSM_16T3E3 MAJOR NA NO REDUNDANCY
05 Active/Active AXSME_2OC12 CRITICAL NA NO REDUNDANCY
06 Active-U/Active AXSM_16OC3_B NONE NA NO REDUNDANCY
07 Standby/Active PXM45 NONE 08 PRIMARY SLOT
08 Active/Active PXM45 NONE 07 SECONDARY SLOT
09 Active/Active RPM_PR NONE NA NO REDUNDANCY
Display information for all cards in the current MGX 8950 switch. Note that an XM60 has no back card, so the display shows "Empty" for the back card position.
M8950_DC.7.PXM.a > dspcds
M8950_DC System Rev: 02.01 Nov. 28, 2001 14:46:29 PST
Chassis Serial No: SCA0504043H Chassis Rev: A0 GMT Offset: -8
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----
01 Active/Active AXSM_4OC12 NONE NA NO REDUNDANCY
02 Active/Active AXSM_4OC12 NONE NA NO REDUNDANCY
05 Active/Active AXSM_1OC48_B NONE NA NO REDUNDANCY
07 Active/Active PXM45B NONE 08 PRIMARY SLOT
08 Empty Resvd/Empty --- MAJOR 07 SECONDARY SLOT
09 Active/Empty XM_60 NONE NA NO REDUNDANCY
10 Active/Empty XM_60 NONE NA NO REDUNDANCY
25 Active/Empty XM_60 NONE NA NO REDUNDANCY
26 Active/Empty XM_60 NONE NA NO REDUNDANCY
dspcdstatcnf
Display Card Statistics Configuration—PXM1E
The dspcdstatcnf command displays the configuration of the card-level bucket statistics for the PXM1E. See the cnfcdstat description for details on this configuration. The configuration controls the generation of bucket statistics that are transferred to the Cisco WAN Manager (CWM) via FTP.
Syntax
dspcdstatcnf
Syntax Description
Related Commands
cnfcdstat
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Display the statistics configuration on the current PXM1E.
MGX8850.7.PXM1E.a > dspcdstatcnf
Bucket Interval : fifteen
Collection Interval : five
dspcdstatus
Display Card Status—PXM45, PXM1E
The dspcdstatus command shows the most serious alarms reported by a card. The alarm information pertains to:
•
Lines
•
Ports
•
Connections
•
Crossbar planes (does not apply to PXM1E)
•
Local management interface (LMI)
•
Severity of each alarm
You can use this command to isolate the alarm source if, for example, you see that a Critical Alarm LED is lit or just want to check the node for alarms. You can subsequently use other alarm commands to locate the problem. Some alarm commands run on only the PXM, and other commands run on service modules. In addition to the dspcdstatus command, other commands on the PXM are as follows:
•
dspndalms displays various types of alarms on the node from a high-level perspective. With the information in the dspndalms display, you can select one of the other commands to investigate the alarm further.
•
dspcdalms identifies line, port, LMI, or connection alarms on a PXM1E UNNI/NNI or an AXSM.
•
dspclkalms shows alarms related to network clocks.
•
dspenvalms lists alarms for out-of-range conditions for temperature, voltage sources, and so on.
•
dspswalms shows alarms related to the switching hardware on the PXM.
The alarm monitoring function on a PXM uses two criteria to determine which alarm to display. One criterion is alarm severity, and the other is hierarchy.
The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
•
Critical, indicating complete, non-recoverable failure, loss of data, and do on. The failed entity must be restored. A power failure or a line being disconnected is an example.
•
Major, indicating service-affecting errors. This event indicates that a major service is damaged or lost, but the existing traffic is not affected.
•
Minor, indicating non-service affecting errors or errors on a remote node. Corrective action is appropriate to prevent a serious fault from developing. An example is a fan failure, where no subscribers are immediately affected, but calamity could result if the situation persists. Note that an accumulation of lower-level alarms does equal a higher-level alarm.
See Figure 2-9 for the hierarchy of alarms. Note that, although the card alarms appear to apply to only service modules, this category can also apply to the PXM. Not all alarms in this figure apply to all platforms. For example:
•
Crossbar alarms and LMI alarms do not apply to the PXM1E.
•
LMI alarms, SRM alarms, and IMA alarms do not apply to the MGX 8950 switch.
Figure 2-9 Alarm Type Hierarchy
Note
The alarm monitoring function reports the highest status alarm after it sorts the current alarms first by severity then by hierarchy. The dspcdstatus command reports the alarm of the greatest severity. (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.) To see all card alarms, use the dspcdalms command.
Syntax
dspcdstatus <slot_number>
Syntax Description
This command requires a slot number.
Related Commands
dspndalms, dspcdalms, dspenvalms, dspclkalms, dspswalms, dspalm, dspalms
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example (PXM45)
Display status of slot 11. The display shows a critical line alarm for slot 11. Next, cc to slot 11 and use the dspalms command.
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
Example (PXM1E)
Display card status on the active PXM1E. Investigate further with the dspalms command (whose output display is truncated in this example).
PXM1E-227.7.PXM.a > dspcdstatus 7
Logical Slot 7 Physical Slot 7
Card Alarm Status - Type IMA Severity CRITICAL
PXM1E-227.7.PXM.a > dspalms
---------------------------------------------
Alarm State : XmtFarEndLOF,LOF,LOS
Alarm State : XmtFarEndLOF,LOF,LOS
Alarm State : XmtFarEndLOF,LOF,LOS
Alarm State : XmtFarEndLOF,LOF,LOS
Type <CR> to continue, Q<CR> to stop:
dspcdvtdft
Display CDVT Default—PXM45, PXM1E
The dspcdvtdft command displays the default CDVT for a PNNI port.
Syntax
dspcdvtdft <portid>
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
Related Commands
dspcdvtdft, cnfcdvtdft
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display the CDVT defaults for port 11:1.1:11.
Geneva.7.PXM.a > dspcdvtdft 11:1.1:11
cbr: rt-vbr: nrt-vbr: ubr: abr:
CDVT: 250000 250000 250000 250000 250000
dspchan
Display Channel—PXM1E
The dspchan command displays a provisioned connection on the PXM1E UNI/NNI back card. The viewpoint of the display is that of a VSI slave. To display a connection from the VSI master side, use the dsppncon or dspcon command on the PXM1E.
The contents of the dspchan output are as follows:
•
NSAP address, logical port, VPI/VCI, status, and ownership of local and remote ends of the connection. The display shows whether a particular endpoint is the master or slave.
The provisioning parameters in the display show:
•
Connection type of VPC or VCC.
•
Service type (for example, ABR).
•
Whether the slave endpoint is persistent or non-persistent
•
A number indicating the controller. For example, 2 refers to PNNI. (See the addcontroller description for information on this controller ID and why 2 refers to PNNI.
•
The administrative state is either up or down. This state results from addcon or dncon/upcon. Note that, after you down a connection with at the connection master endpoint, the dspchan command shows the connection as "down" when you execute it at the master endpoint and "failed" when you execute it at the slave endpoint. (See also dncon description).
•
The operational state is either OK or failed. The operational state can apply to a connection regardless of the administrative state.
The traffic management parameters consist of:
•
Local and remote UPC parameters of PCR, MBS, CTD, CDVT, and so on. A -1 in a field means that the parameter was not specified. The characters "N/A" indicate that the parameter does not apply to the service type.
These other fields also pertain to connection integrity:
•
OAM continuity check enable or disable.
•
Loopback test enable/disable and loopback type.
•
Round trip delay in microseconds. This field is non-zero only if you previously executed tstdelay.
Syntax
dspchan <ifNum> <vpi> <vci>
Syntax Description
ifNum
|
The range for interface number is 1-31.
|
vpi
|
The range for VPI is 0-4095.
|
vci
|
The range for VCI is 1-65535.
|
Related Commands
dspchans, dsppncons, addcon
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Display the channel on logical port 1 with the VPI and VCI of 20 and 200, respectively.
Janus11.7.PXM.a > dspchan 1 20 200
--------------------------------------------------------------------------
Local : NSAP Address vpi vci
(M) 4700918100000000001A531C59000001073B0100 20 200
Remote : NSAP Address vpi vci
(S) 4700918100000000001A531C59000001073B1400 20 200
--------------------------------------------------------------------------
Conn. Type : VCC Admn Status : ADMN-UP
Service Type : cbr1 Oper Status : OK
Controller : 2 Record # : 7
--------------------------------------------------------------------------
Local PCR : 50 Remote PCR : 50
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
Max Cost : -1 Frame discard: DISABLED
Local CDVT : 250000 OAM segment : ENABLED
Local PercentUtil: 100 Remote PercentUtil: 100
--------------------------------------------------------------------------
OAM CC Config : DISABLED Statistics : DISABLED
--------------------------------------------------------------------------
Loopback Type :No Lpbk | Dir:N/A | Status:No Lpbk | RTD: 0us
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Port side Tx : normal Swth side Tx : normal
Port side Rx : normal Swth side Rx : normal
--------------------------------------------------------------------------
Ing-E2E-AIS ING-SEG-AIS Ing-E2E-RDI Ing-SEG-RDI
--------------------------------------------------------------------------
Egr-E2E-AIS Egr-SEG-AIS Egr-E2E-RDI Egr-SEG-RDI
--------------------------------------------------------------------------
Ing-E2E-CCFAIL Ing-SEG-CCFAIL Egr-E2E-CCFail Egr-SEG-CCFail
--------------------------------------------------------------------------
CONDITIONED IfFail Mismatch LMI-ABIT
--------------------------------------------------------------------------
dspchancnt
Display Channel Counters—PXM1E
The dspchancnt command displays the statistical counters for a connection (or channel). See the cnfdiag command for a description of the related diagnostics.
Syntax
dspchancnt <ifNum> <vpi> <vci> -r <dsp interval> -max <max dsp time>
Syntax Description
ifNum
|
The logical port number has a range of 1-31.
|
vpi
|
The range for VPI depends on the interface type. as follows:
• UNI: 0-255
• NNI: 0-4095
|
vci
|
The possible values for VCI depend on the connection type. as follows:
• VCC: 0-65535
• VPC: 0
|
-r
|
The display interval in which to display the channel statistics in the range of 1-60 seconds.
|
-max
|
The duration of time to display the channel statistics in the range of 0-3600 seconds.
|
Related Commands
clrchancnt, dspcdcnt
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
On the PXM1E, display channel counters as indicated on the command line:
OC38830.1.PXM.a > dspchancnt 1 10 100
Ingress chan stat Egress chan stat
-------------------------------------- --------------------------------------
All non-compliant cells : 0
(Before policing) : 0 Cells to port : 0
CLP0 from port : 0 CLP0 to port : 0
CLP1 from port : 0 CLP1 to port : 0
Cells to network : 0 Cells from network : 0
Cells discarded in qe : 0 Cells discarded in qe : 0
VC queue depth : 0 VC queue depth : 0
dspchans
Display Channels—PXM1E
The dspchans command shows all provisioned connections on the PXM1E's UNI/NNI back card. Due to the potentially large number of connections, the parameters let you narrow the scope of the display.
The viewpoint of the display is that of a VSI slave. To display all provisioned connections from the VSI master side, use the dspcons command on the PXM1E
The contents of the dspchans output are as follows:
record
|
A number for the connection with internal application only. It resides in the database and is not affected by user input. The system creates this number when you create the connection. Cisco WAN Manager 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 also the 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 that Cisco WAN Manager 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.
|
Syntax
dspchans [-conn <conn id>] [-filt <filter options>] [-if <intf no>] [-vpi <vpi filter>] [-vci <vci filter>]
Syntax Description
-conn
|
The connection identifier consists of the logical interface number, VPI, and VCI of where the display is to begin. The format is ifNum.vpi.vci. The range for ifNum is 1-31.
|
-filt
|
The filters confine the display to a particular criterion. Enter one of the follow numbers:
• 1: All connections on the ingress
• 2: All connections on the egress
• 3: All conditions that are currently conditioned
• 4: Al connections provisioned on interfaces that are now failed
• 5: All connections that show a CC failure
• 6: All connections where a card mismatch has occurred.
• 7: All connections with an A-bit error
• 8: All connections with no errors
• 9: No filters (default)
|
-if
|
The range for interface number is 1-31.
|
-vpi
|
The range for VPI is 0-4095.
|
-vci
|
The range for VCI is 1-65535.
|
Related Commands
dspchan, dspcons, dsppncon
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display all provisioned connections.
Unknown.8.PXM.a > dspchans
record Identifier Type SrvcType M/S Upld Admn Alarm
------ ---------- ---- -------- --- ---- ---- -----
7 01 0020 00200 VCC cbr1 M c09bb734 UP none
5 01 0055 00050 VCC cbr1 M c0180af9 UP none
2 01 0088 00040 VCC cbr1 S c017f2c8 UP none
6 20 0020 00200 VCC cbr1 S c09bb728 UP none
4 25 0055 00050 VCC cbr1 S c0180aef UP none
0 28 0088 00035 VCC cbr1 S be08afc4 UP none
1 28 0088 00036 VCC cbr1 M be08b01c UP none
3 28 0088 00040 VCC cbr1 M c017f2d0 UP none
dspchantests
Display Channel Tests—PXM1E
The tstdelay or tstconseg commands test the integrity of the path of a connection in the ingress and egress directions, respectively. After you successfully start a test through tstdelay or tstconseg, the returned message directs you to use dspchantests or dspcon to see the results. The same test results presented by dspchantests appears in the dspcon display, but dspchantests shows only the test results.
Syntax
dspchantests <ifNum> <vpi> <vci> [-num <count>]
Syntax Description
ifNum
|
The logical port number has a range of 1-31.
|
vpi
|
The VPI range on a UNI is 0-255.
The VPI range on an NNI is 0-4095.
|
vci
|
The VCI range for a VCC is 1-65535.
For a VPC, the VCI is 0.
|
-num
|
(Optional) A keyword that indicates an aggregate connection count follows.
|
number
|
The number of connections to display.
|
Related Commands
tstdelay, tstconseg, dspcon
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Examples
Run tstdelay on connection 1 10 100 then display the results.
Step 1
Execute tstdelay:
node19.7.PXM1E.a > tstdelay 1 10 100
Test started; Use dspcon/dspchantests to see test results
Step 2
Check the results:
node19.7.PXM1E.a > dspchantests 1 10 100
Connection Id Test Type Direction Result Round Trip Delay
============= ========= ========= ======= ================
01.0010.00100: OAM Lpbk ingress Success 40000
Run tstconseg for 1 10 100 then display the results.
Step 1
Run the test for 1 10 100:
node19.7.PXM1E.a > tstconseg 1 10 100
Test started; Use dspcon/dspchantests to see test results
Step 2
Check the results:
node19.7.PXM1E.a > dspchantests 1 10 100
Connection Id Test Type Direction Result Round Trip Delay
============= ========= ========= ======= ================
01.0010.00100: OAM Lpbk egress TimeOut 0
dspchassis
Display Chassis—PXM45, PXM1E
This command displays details about the capability of the chassis.
Syntax
dspchassis
Syntax Description
This command takes no parameters.
Related Commands
dspcds
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Examples
Display chassis details for the current switch. The controller card is a PXM45.
M8850_LA.8.PXM.a > dspchassis
Supports Narrow Band Service Module Functionality - YES
Supports VSIMASTER Functionality - NO
Supports ROUTING Functionality - YES
Supports FEEDER Functionality - YES
Display the chassis for the current switch. The controller is a PXM1E.
Unknown.8.PXM.a > dspchassis
Supports Narrow Band Service Module Functionality - YES
Supports VSIMASTER Functionality - NO
Supports ROUTING Functionality - YES
Supports FEEDER Functionality - YES
dspcli
Display CLI—PXM45, PXM1E
The dspcli command displays commands whose user-privilege level has been modified through the cnfcli command. The display also shows the default privilege for each modified command.
The dspcli command shows privilege changes only for commands on the card where you run dspcli. For example, using the dspcli command on a PXM shows only the affected commands that are available on the PXM. To see affected commands on an AXSM, use dspcli on that AXSM.
Refer to the cnfcli description for extensive details on this feature.
Syntax
dspcli <accesslevel>
Syntax Description
The mandatory parameter is the subcommand string, "accesslevel."
Related Commands
cnfcli
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display any commands whose access level has changed.
PXM1E_SJ.7.PXM.a > dspcli accesslevel
Command Name Current Default
-----------------------------------------------------------
addapsln SERVICE_GP GROUP1
addlnloop SERVICE_GP GROUP1
arpFlush SERVICE_GP SUPER_GP
arpShow SERVICE_GP ANYUSER
cnfserialif SERVICE_GP SUPER_GP
cnfsntprmtsvr SERVICE_GP GROUP1
cnfspvcprfx SERVICE_GP SUPER_GP
cnfsscop SERVICE_GP GROUP1
cnfsvcoverride SERVICE_GP SUPER_GP
cnftmzn SERVICE_GP SUPER_GP
dspclkalms
Display Clock Alarms—PXM45, PXM1E
The dspclkalms command displays alarms associated with the primary or secondary clock source.
The switch constantly monitors the state of the clocks. On the local node, the clock monitor declares an alarm if the clock becomes undetectable or goes out of specification for any reason. The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:
•
Critical, indicating complete, non-recoverable failure, loss of data, and do on. The failed entity must be restored. A power failure or a line being disconnected is an example.
•
Major, indicating service-affecting errors. This event indicates that a major service is damaged or lost, but the existing traffic is not affected.
•
Minor, indicating non-service affecting errors or errors on a remote node. Corrective action is appropriate to prevent a serious fault from developing. An example is a fan failure, where no subscribers are immediately affected, but calamity could result if the situation persists. Note that an accumulation of lower-level alarms does equal a higher-level alarm.
The dspclkalms command is part of a hierarchy of troubleshooting commands you can execute on the PXM 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.
Syntax
dspclkalms
Syntax Description
This command takes no parameters.
Related Commands
dspcdstatus, dspndalms, dspalm, dspalms, dspclksrcs, cnfclksrc
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
M8850_NY.7.PXM.a > dspclkalms
M8850_NY System Rev: 02.01 Dec. 22, 2001 22:44:28 PST
MGX8850 Node Alarm: MAJOR
Clock Manager Alarm Summary
----------------------------
NETWORK CLOCK ALARM : LOST PRIMARY REFERENCE : MINOR
NETWORK CLOCK ALARM : STANDBY LOST PRIMARY REFERENCE : MINOR
dspclksrcs
Display Clock Sources—PXM45, PXM1E
The dspclksrcs command lets you display the clock sources if the switch is using the manually configured clock sources.
Note
Even though this command applies primarily to manual clocking, it can show one status that does not appear in the NCDP displays: "holdover." Holdover is described in this command definition, below.
The dspclksrcs display has the configuration and status of the clock sources. (For details about network synchronization, see the description of cnfclksrc.) The dspclksrcs output consists of the following:
•
For the primary clock: the type, source, status, and reason (for status change) of the clock.
•
For the secondary clock: the type, source, status, and reason (for status change) of the clock.
•
The active clock—the clock that currently provides synchronization—can be primary, secondary, holdover, or the free-running oscillator.
Note that "holdover" is a situation where the UI-S3 card maintains the clock based on the primary or secondary clock parameters that the hardware has recorded. Even for a stratum 1 source, the hardware can maintain the frequency and stability of the clock for up to 24 hours if the source is not usable. If the source cannot return to use after 24 hours, the node switches to the internal oscillator.
•
Whether revertive mode is enabled or disabled.
Note
Changes to the configuration and status of clocks go into the database on the active PXM. If a standby PXM 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 PXM switches to the active state.
Type of Clock Source
The type is either BITS or generic. Currently, generic applies to only a service module-sourced clock. If a user-specified priority of a clock is not configured, the source is null. For the current release, the null source is presumed to be the internal oscillator.
Possible Sources
The source of the clock has the format [shelf.]slot:subslot.port:subport. More typically, the source has the two-part, short-hand form slot.line or slot.port. If the source is an AXSM, the format is slot.line.
For a BITS clock, the format is slot.port. The slot for a BITS clock is logical slot 7 in an MGX 8850 or MGX 8950 chassis or is logical slot 1 in an MGX 8830 chassis. The logical port is always 35 or 36. Port 35 refers to the upper external clock connector, and port 36 refers to the lower connector.
Clock Status
The status of a particular clock source can be one of the following:
•
"ok" (good), which means the clock source is operational and stable. (If the status is "ok," then the Reason field shows "okay." If the status is "ok," the reason for the status change that is described in the section, "Reason for Status Change," is not important.)
•
"bad" means a fault in the clock source has been detected. Use the Reason field to help isolate the problem. See the section, "Reason for Status Change."
•
"unknown" is a temporary string while the clock manager is sending a message to the clock source.
•
"not configured" means that this source—primary or secondary—has not been configured.
•
"holdover"—see definition earlier in the command description.
Reason for Status Change
The reasons that clock status can change are numerous. The dspclksrcs command displays a Reason field for both the primary and the secondary clock source. The reason can include the first-time, user-specification of the clock source. The reason strings and their meaning appear in Table 2-12. Additional information about "okay" and the locking process follows.
Table 2-12 Reasons for Changing Clock States
Reason
|
Meaning
|
okay
|
The clock source is okay.
|
unknown reason
|
The clock manager has no information for Reason.
|
no clock signal
|
Loss of signal (LOS) on the clock source.
|
frequency too high
|
The frequency has drifted too high.
|
frequency too low
|
The frequency has drifted too low
|
excessive jitter
|
Jitter has exceeded tolerance for this stratum.
|
missing card or component
|
The active PXM45 has no clock hardware support.
|
non-existent logical interface
|
The interface is non-existent or not functioning.
|
interface does not support clocking
|
The interface does not support clocking.
|
phase error
|
The clock manager has detected a phase error in the clock.
|
unlockable
|
The clock manager has attempted to lock the source but found that the clock signal from this source is unlockable.
|
out of lock or null
|
The clock circuitry is again trying to lock a source that went out of locking range. Note: for Reason, out of lock and null are the same.
|
reset—not a valid state
|
The clock source has been reset.
|
in locking—wideband test
|
The clock circuitry is in wide bandwidth mode of the locking process. In this mode, the circuit tests the integrity of the source but with wide latitude for frequency accuracy. If the source passes this test, the circuit proceeds to the narrowband test.
|
in locking—narrow- band test
|
The clock circuitry is in narrow bandwidth locking mode. In this mode, the circuit stringently tests the integrity of the source.
|
locked
|
The clock circuitry is locked to this source.
|
When you configure a new clock source or the current clock source changes due to any reason, the software goes through the process of validating the new, current clock source again. (For example, the reasons other than direct user-configuration can be: the previous clock source goes out of lock or a resync of the clock sources takes place due to a switch-over or a rebuild.) This validation process takes the current clock source through the following states:
•
in locking—wideband test
•
in locking—narrowband test
•
locked
During these states, the node is already using the new clock source as the synchronizing source.
You might also see the states in the sequence just listed if the current source was momentarily lost because it drifted out of the lockable range for either the frequency or the phase. In this case, software again tries to confirm that the current source is lockable before it declares the source to be unlockable. If the software finds that the clock source still does not return to the lockable range, it declares the clock source as unlockable then proceeds to use the next clock in the hierarchy (of primary, secondary, internal oscillator). The exception to this final scenario occurs if the current clock source is the internal oscillator in either the free running mode or the hold-over mode: in this case, the software omits this final validation attempt because no other clocks sources within a clock hierarchy are available.
Revertive Behavior
For information on revertive behavior, see the cnfclksrc description.
Syntax
dspclksrcs
Related Commands
cnfclksrc, delclksrc, dspclkalms
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display the clocks. The display shows that both the primary and secondary clocks are good. They are sourced at lines 2 and 3 of the AXSM in slot 6. Also, the primary source is providing the active clock, and the system is configured for revertive behavior. The primary and secondary clock reasons are okay.
pinnacle.7.PXM.a> dspclksrcs
Primary clock type: generic
Primary clock source: 6.2
Primary clock status: good
Primary clock reason: okay
Secondary clock type: generic
Secondary clock source: 6.3
Secondary clock status: good
Secondary clock reason: okay
source switchover mode: revertive
Display information about the clock sources. This example shows a BITS clock for the primary source with revertive mode enabled.
pop20one.7.PXM.a > dspclksrcs
Primary clock type: bits t1
Primary clock source: 7.35
Primary clock reason: okay
Secondary clock type: generic
Secondary clock source: 9:1.1:1
Secondary clock status: ok
Secondary clock reason: okay
source switchover mode: revertive
dspcmdabbr
Display Command Abbreviation—PXM45, PXM1E
The dspcmdabbr command lets you see whether the CLI requires the entire name of a command or accepts the first unique string of characters that identifies a command. For example, "loa" is enough to identify loadrev if command abbreviation is enabled. (The string "lo" is not enough to identify a particular command because of the logout command.)
Syntax
dspcmdabbr
Syntax Description
This command takes no parameters.
Related Commands
cnfcmdabbr
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Check the status of command abbreviation.
MGX8850.1.3.PXM.a > dspcmdabbr
MGX8850.7.PXM.a > dspcmdabbr
Command Abbreviation feature currently enabled
dspcon
Display Connection—PXM45, PXM1E
The dspcon command displays the configuration of an SPVC or SPVP. (For additional, dynamic information on the connection, use the dsppncon command.). The dspcon output appears in sections to make the information easier to sort. Most of the information in the dspcon output comes from the addcon or cnfcon command. See addcon description for more information. Note also that values specified through the cnfpnni-intf command can affect the dspcon output.
Display Contents
On the PXM, dspcon shows the following connection identifiers:
•
NSAP address, status, and ownership of local and remote ends of the connection. The display shows whether a particular endpoint is the master or slave.
The provisioning parameters in the display consist of the following:
•
Connection type of VPC or VCC.
•
Service type and compliance (for example, UBR for service type and UBR.1 for ATM Forum compliance).
•
Bearer class (relates to voice traffic and is reserved for future use).
•
Whether continuity checking or frame discard are enabled (see addcon description).
•
Cause of the last failure. This field can also show that no errors have occurred since the connection was first added by displaying "SPVC Established." If a failure occurred, the Attempts field shows the number of times the system attempted to re-establish service. If no failures have occurred, the Attempts field contains a 0.
•
L-Util and R-Util are the local and remote percent of utilization assigned to the connection. Currently, the default of 100% is the only value.
•
Cost values for the connection's route: the two fields in this category are Max Cost and Routing Cost. The Max Cost is a cost-per-link configured for a service type (such as UBR) through the cnfpnni-intf command. When you add or modify an SPVC through addcon or cnfcon, you can specify the maximum cost for an individual connection (-mc parameter), then PNNI uses the cost-per-link for the service type and the maxcost for the connection to determine whether a route costs too much. After the system creates a route, the total number of links yields the Routing Cost.
The default cost-per-link is 5040, so if a particular service type uses the default and a route consists of 4 links, the Routing Cost is 20160. If the dspcon display shows that Max Cost is -1, no limit was specified, and the resulting Routing Cost field shows "0 (N/A)."
•
Broadcast type: point-to-point or multicast (point-to-multipoint).
•
The persistence state of the slave endpoint.
•
The routing priority of the connection.
•
Prefered reroute information.
The Traffic Parameters section shows the standard parameters PCR, SCR, and CDV in the receive and transmit directions.
Syntax
dspcon <portid> <vpi> <vci>
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
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 1-65535. For a VPC, the VCI is 0.
|
Related Commands
addcon, dspcons, cnfcon
PXM1E only: dspchan, dspchans
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
On the CLI of the PXM45, display the connection on port 3:1.1:1 with a VPI and VCI of 102 and 102.
M8850_LA.8.PXM.a > dspcon 3:1.1:1 102 102
Port Vpi Vci Owner State Persistency
----------------------------------------------------------------------------
Local 3:1.1:1 102.102 MASTER FAIL Persistent
Address: 47.00918100000100001a531c2a.000001031801.00
Remote Routed 102.102 SLAVE -- Persistent
Address: 47.00918100000200036b5e30cd.000001011802.00
-------------------- Provisioning Parameters --------------------
Connection Type: VCC Cast Type: Point-to-Point
Service Category: CBR Conformance: CBR.1
Last Fail Cause: unallocated (unassigned) number Attempts: 20005
Continuity Check: Disabled Frame Discard: Disabled
L-Utils: 100 R-Utils: 100 Max Cost: -1 Routing Cost: 0
---------- Traffic Parameters ----------
Values: Configured (Signalled)
Tx PCR: 50 (-) Rx PCR: 50 (-)
Tx CDV: -1 (-) Rx CDV: -1 (-)
Tx CTD: -1 (-) Rx CTD: -1 (-)
-------------------- Preferred Route Parameters------------------
Currently on preferred route: N/A
On the PXM1E, display the connection on port 15 with a VPI/VCI of 10/100.
p2spvc4.7.PXM1E.a > dspcon 15 10 100
--------------------------------------------------------------------------
Local : NSAP Address vpi vci
(M) 4700918100000000001A531C7700000101180F00 10 100
Remote : NSAP Address vpi vci
(S) 47009181000000003071F805E600000009010000 10 100
--------------------------------------------------------------------------
Conn. Type : VCC Admn Status : ADMN-UP
Service Type : abrstd Oper Status : OK
Controller : 2 Record # : 0
SlavePersist : YES Cast-type : P2P
--------------------------------------------------------------------------
Local PCR : 100 Remote PCR : 100
Local SCR : N/A Remote SCR : N/A
Local CDV : N/A Remote CDV : N/A
Local CTD : N/A Remote CTD : N/A
Local MBS : N/A Remote MBS : N/A
Max Cost : -1 Frame discard: DISABLED
Local CDVT : 250000 OAM segment : ENABLED
Local PercentUtil: 100 Remote PercentUtil: 100
--------------------------------------------------------------------------
OAM CC Config : DISABLED Statistics : ENABLED
--------------------------------------------------------------------------
Loopback Type : No Lpbk | Dir: N/A | Status: No Lpbk | RTD: 0us
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Port side Tx : normal Swth side Tx : normal
Port side Rx : AIS Swth side Rx : AIS
--------------------------------------------------------------------------
I-AIS/RDI E-AIS/RDI CONDITIONED CCFAIL IfFail Mismatch LMI-ABIT
--------------------------------------------------------------------------
Internal VSVD config : N/A
External VSVD config : N/A
Local MCR : 50 cells/second
Remote MCR : 50 cells/second
Initial cell rate (ICR) : N/A cells/second
ACR decrease factor (ADTF) : N/A x 10 millisec
Rate decrease factor (RDF) : N/A
Rate increase factor (RIF) : N/A
Cells per forward RM (NRM) : N/A
Time between forward RM (TRM) : N/A
cutoff decrease factor (CDF) : N/A
Type <CR> to continue, Q<CR> to stop:
fixed round trip delay (FRTT) : N/A microseconds
transient buffer exposure (TBE) : N/A cells
--------------------------------------------------------------------------
dspconalmcnts
Display Connection Alarm Counts—PXM1E
The dspconalmcnts command lists errored connections on the logical interfaces on the card. This command lists by alarm cause. The causes are:
•
Conditioning
•
Ingress alarm
•
Egress alarm
•
Connection conditioning failure
•
Mismatch
•
A-bit
Syntax
dspconalmcnts
Syntax Description
This command takes no parameters.
Related Commands
dspconalms
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display the connection alarms by alarm cause.
M8850_SF.7.PXM1E??.a > dspconalmcnts
**************************************************************************
************ CONNECTIONS IN ALARM PER INTERFACE (BY ALM CAUSE)************
**************************************************************************
IF# IfState #Condn #IngAlm #EgrAlm #CCFail #ifFail #mismatch #Abit
-- ------- ------ ------- ------- ------- ------- --------- -----
01 ACTV 00000 00000 00000 00000 00000 00000 00000
02 ACTV 00000 00000 00000 00000 00000 00000 00000
03 ACTV 00000 00000 00000 00000 00000 00000 00000
******************** SUMMARY ALARM COUNT FOR THE CARD *******************
#Condn #IngAlm #EgrAlm #CCFail #ifFail #mismatch #abit
000000 000000 000000 000000 000000 000000 000000
dspconalms
Display Connection Alarms—PXM1E
The dspconalms command displays connection alarms. The command lists alarms by port and shows instances by the severities of critical, major, and minor alarms. The display also shows which types of failures constitute each of these severities.
Syntax
dspconalms
Syntax Description
This command takes no parameters.
Related Commands
dspconalmcnts
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Display connection alarms. This card has three logical interfaces but no connection alarms.
M8850_SF.7.PXM1E.a > dspconalms
****************************************************************
******* CONNECTIONS IN ALARM PER INTERFACE (BY SEVERITY) *******
****************************************************************
IF# IfState #Critical #Major #Minor
-- ------- --------- ------ ------
01 ACTV 00000 00000 00000
02 ACTV 00000 00000 00000
03 ACTV 00000 00000 00000
****************************************************************
************** PRESENT ALARM SEVERITY CONFIGURATION **********
****************************************************************
MINOR : IngAlm EgrAlm IfFail Abit
dspconinfo
Display Connection Information—PXM45, PXM1E
The dspconinfo runs on the PXM45 and lists the total number SPVCs on each PNNI port on the switch. The default operation of the command is to show all SPVCs or SPVPs, With the optional parameters, you can specify one or more types of information to display.
The display shows:
•
PNNI physical port number
•
Number of active connections
•
Number of failed connections
•
Number of administratively inactive (or down) connections as a result of dncon
•
Total number of connections
Note that dspconinfo checks for the down state at the master end of the connection (status at the slave endpoint is failed). See also the descriptions for dncon and dspcon.
Syntax
dspconinfo
[-port portid] [-detail {true | false}] [-owner {master | slav] -sc {cbr | rtvbr | nrtvbr | abr | ubr}
Syntax Description
-port
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
-detail
|
Determines whether the display contains information for all interfaces and slots or just slots. Type "true" after the keyword for all interfaces and slots. Type "false" for just slots.
Default: true
|
-owner
|
Lets you specify the endpoint of the connection. Type "master" or "slave."
|
-sc
|
Directs the command to display connections of a particular service type. Type one of the following after the keyword: cbr, nrtvbr, rtvbr, abr, or ubr.
Default: no default
|
Related Commands
None
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Examples
Display the SPVC summaries on the switch with the following conditions:
•
No options: a total of 13 active connections exist.
•
UBR connections: a total of 2 endpoints are listed.
•
Connections on port 5:1.2:2.
•
Connections at slot 5.
•
Slave endpoints.
atlanta.7.PXM.a > dspconinfo
Local Port #Active #Failed #Down #Total
-----------------------------------------------------------
atlanta.7.PXM.a > dspconinfo -sc ubr
Local Port #Active #Failed #Down #Total
-----------------------------------------------------------
atlanta.7.PXM.a > dspconinfo -port 5:1.2:2
Local Port #Active #Failed #Down #Total
-----------------------------------------------------------
atlanta.7.PXM.a > dspconinfo -detail false
Local Slot #Active #Failed #Down #Total
-----------------------------------------------------------
atlanta.7.PXM.a > dspconinfo -owner slave
Local Port #Active #Failed #Down #Total
-----------------------------------------------------------
dspconload
Display Connection Load—PXM1E
The dspconload command displays the number of ingress and egress cells per second on a connection (ifNum/vpi/vci). With the statistics provided by dspconload, you can determine whether the current load on the connection suggests a modification to the connection or possible troubleshooting.
Syntax
dspconload <ifNum> <vpi> <vci>
Syntax Description
ifNum
|
The range for logical interface (port) numbers is 1-31.
|
vpi
|
The VPI of the connection. The range is 0-4095.
|
vci
|
The VCI of the connection. The range is 0-65635.
|
Related Commands
dspcons, dspcon, dspload
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display the load on the connection with a VPI and VCI of 10 and 100, respectively, on logical port 1.
MGX8850.7.PXM1E.a > dspconload 1 10 100
-------------------------------------- --------------------------------------
All non-compliant cells : 0
(Before policing) : 999 Cells to port : 999
CLP0 from port : 999 CLP0 to port : 999
CLP1 from port : 0 CLP1 to port : 0
EOF from port : 0 EOF to port : 0
EFCI1 from port : 0 EFCI1 to port : 0
Cells to network : 999 Cells from network : 999
CLP0 to network : 999 CLP0 from network : 999
CLP1 to network : 0 CLP1 from network : 0
EFCI1 to network : 0 EFCI1 from network : 0
Cells discarded in qe : 0 Cells discarded in qe : 0
CLP0 discarded in qe : 0 CLP0 discarded in qe : 0
CLP1 discarded in qe : 0 CLP1 discarded in qe : 0
EFCI1 discarded in qe : 0
VC queue depth : 0 VC queue depth : 0
ACR (Valid for WFQ conns) : 1 ACR (Valid for WFQ conns) : 1
OAM from port : 0 OAM to port : 0
RM to network : 0 RM from network : 0
OAM to network : 0 OAM from network : 0
OAM discarded in qe : 0 OAM discarded in qe : 0
EFCI1 discarded in qe : 0
RM discarded in qe : 0 RM discarded in qe :
dspconntracebuffer
Display Connection Trace Buffer—PXM45, PXM1E
The dspconntracebuffer command lets you display the results of a connection trace. The trace occurs after you provide an identifier for a routed connection to the conntrace command.
The trace consists of the following information for each switch:
•
The result of the trace—success or failure
•
The date and time of the last update
•
Node names and node IDs of all the nodes that the connection traverses
•
Incoming port ID (at the UNI) in the format of logical port number and physical port ID
•
Outgoing port ID (at the network egress) in the format of logical port number and physical port ID
•
VPI and VCI at the incoming and outgoing ports
•
Call reference number at the incoming and outgoing ports
•
The name, node ID, port and call identifiers at the next node in the path
Syntax
dspconntracebuffer <portid> <vpi> <vci>
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
vpi
|
The VPI of the connection.
|
vci
|
The VCI of the connection.
|
Related Commands
dspconntracebuffers, clrconntracebuffer, clrconntracebuffers, conntrace
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Do a connection trace on the connection with a VPI/VCI of 1/100 on port 5:1.1:1, then display the trace buffer for this connection.
r18pop157.7.PXM.a > conntrace 5:1.1:1 -vpi 1 -vci 100
r18pop157.7.PXM.a > dspconntracebuffer 5:1.1:1 1 100
Last update time:Jul 9 2002 23:42:46
Result:SUCCESS Reason:N/A
Incoming Port:17111041 Physical PortId:5:1.1:1
VPI :1 VCI:100 CallRef:147019
Node Name:r18pop157 NodeId:
56:160:47.00918100000000016444456a.00016444456a.01
Outgoing Port:16914433 Physical PortId:2:1.1:1
VPI :1 VCI:47161 CallRef:72760
Node Name:r18pop161 NodeId:
56:160:47.009181000000000164444b71.000164444b71.01
Outgoing Port:16848897 Physical PortId:1:1.1:1
VPI :1 VCI:55482 CallRef:93315
Node Name: NodeId:56:160:47.0091810000000004c113b985.0004c113b985.01
Outgoing Port:17045505 Physical PortId:4:1.1:1
VPI :1 VCI:47074 CallRef:36277
Node Name: NodeId:56:160:47.009181000000000164444b35.000164444b35.01
Outgoing Port:16979969 VPI :1 VCI:100 CallRef:142329 Physical
dspconntracebuffers
Display Connection Trace Buffers—PXM45, PXM1E
The dspconntracebuffers command displays all connection trace buffers. The maximum number of traces on a switch is 100, and each trace buffer is separated by a message indicating the beginning of the next trace record. (A connection trace occurs after you provide an identifier for a routed connection to the conntrace command.) To see an individual trace, use the dspconntracebuffer command.
Syntax
dspconntracebuffers
Syntax Description
No parameters
Related Commands
dspconntracebuffer, clrconntracebuffer, clrconntracebuffers, conntrace
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Display all connection trace buffers recorded on the local switch. Each connection trace is separated by a message indicating the next buffer record is about to begin.
Note
The node name appears only if the node exists in the peer group where you started the trace. For a hop outside the local peer group, a blank space follows the "Node Name:" label. (Immediately following this blank space, the ID of the node outside the local peer group appears.)
r18pop157.7.PXM.a > dspconntracebuffers
--------------------------------
dspconntracebuffers:next record
--------------------------------
Last update time:Jul 9 2002 23:43:31
Result:SUCCESS Reason:N/A
Incoming Port:17111041 Physical PortId:5:1.1:1
VPI :1 VCI:101 CallRef:147020
Node Name:r18pop157 NodeId:
56:160:47.00918100000000016444456a.00016444456a.01
Outgoing Port:16914433 Physical PortId:2:1.1:1
VPI :1 VCI:47162 CallRef:72761
Node Name:r18pop161 NodeId:
56:160:47.009181000000000164444b71.000164444b71.01
Outgoing Port:16848897 Physical PortId:1:1.1:1
VPI :1 VCI:55483 CallRef:93316
Node Name: NodeId:56:160:47.0091810000000004c113b985.0004c113b985.01
Outgoing Port:17045505 Physical PortId:4:1.1:1
VPI :1 VCI:47075 CallRef:36278
Type <CR> to continue, Q<CR> to stop:
Node Name: NodeId:56:160:47.009181000000000164444b35.000164444b35.01
Outgoing Port:16979969 VPI :1 VCI:101 CallRef:142330 Physical
--------------------------------
dspconntracebuffers:next record
--------------------------------
Last update time:Jul 9 2002 23:42:46
Result:SUCCESS Reason:N/A
Incoming Port:17111041 Physical PortId:5:1.1:1
VPI :1 VCI:100 CallRef:147019
Node Name:r18pop157 NodeId:
56:160:47.00918100000000016444456a.00016444456a.01
Outgoing Port:16914433 Physical PortId:2:1.1:1
VPI :1 VCI:47161 CallRef:72760
Node Name:r18pop161 NodeId:
56:160:47.009181000000000164444b71.000164444b71.01
Outgoing Port:16848897 Physical PortId:1:1.1:1
VPI :1 VCI:55482 CallRef:93315
Node Name: NodeId:56:160:47.0091810000000004c113b985.0004c113b985.01
Type <CR> to continue, Q<CR> to stop:
Outgoing Port:17045505 Physical PortId:4:1.1:1
VPI :1 VCI:47074 CallRef:36277
Node Name: NodeId:56:160:47.009181000000000164444b35.000164444b35.01
Outgoing Port:16979969 VPI :1 VCI:100 CallRef:142329 Physical
dspcons
Display Connections—PXM45, PXM1E
The default entry of the dspcons command requires no parameters and displays general information for all connections. Because of the very large number of possible connections, optional filters are available to let you narrow the scope of the output. See Syntax Description for each card type.
The dspcons command runs on a PXM or any model of broadband or narrowband service module. The optional parameters and the output are different on these card types. See Syntax Description for card-specific parameters.
Note
The dspcons command on the PXM1E shows provisioned connections on the narrowband service modules and the UNI/NNI back card—from the VSI master viewpoint. To display connections on a narrowband VSI slave, cc to the card and use the dspcon or dspcons command. To see connections on the UNI/NNI card as a VSI slave, two commands are available especially for this purpose: dspchan and dspchans. Refer to their descriptions.
The dspcons Output
When you run dspcons on the CLI of a PXM45 or PXM1E, 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 physical port ID has the format used by PNNI:
• On the PXM45: slot:subslot.port:subport
• On the PXM1E: slot.port
|
Local and Remote VPI.VCI
|
The VPI and VCI at the local and remote ends of the connection.
|
State
|
The State column shows whether the connection is OK, down (by the dncon command), failed, or has an alarm indication signal (AIS) or abit errors.
|
Owner
|
Whether the endpoint is master or slave.
|
Local and Remote NSAP
|
An NSAP address for each end of the connection.
|
Syntax
dspcons [-port portid] [-vpi starting-vpi] [-vci starting vci] [-state {fail | ok | down}]
[-owner {master | slave}] [-sc {cbr | rtvbr | nrtvbr | abr | ubr}] [-persflag {nonpersistent | persistent}] [-rteid Pref Route Id]
Syntax Description
-port
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
-vpi
|
The VPI of the connection that you would like to serve as the starting connection in the display.
|
-vci
|
The VPI of the connection that you would like to serve as the starting connection in the display.
|
-state
|
A specific connection state. The display shows only the connections with the state you specify. Note that on the PXM45, you must spell out the entire state keyword. The keywords for specifying a state are
failed—only failed connections
ais—connections with alarm indication signal (AIS) set
abit—connections on which an A-bit error has occurred
ok—connections with no problems
down—connections that are administratively down because a user has executed dncon to down the connection
|
-owner
|
Specifies connections where the local endpoint is either master or slave.
|
-sc
|
The -sc option lets you display connections of a particular service class. The choices are cbr, rtvbr, nrtvbr, abr, and ubr.
|
-persflag
|
The -persflag option lets direct the display to show only persistent or non-persistent endpoints. Type persistent or nonpersistent.
|
-rteidb
|
The -rteidb option lets you specify connections with a particular preferred route ID.
|
Related Commands
dspcon, addcon, cnfcon, delcon, dncon, upcon, dsppncon, dsppncons
PXM1E only: dspchan, dspchans
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example PXM45
Display all connections.
M8850_LA.8.PXM.a > dspcons
Local Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persisteny
----------------------+------------------------+---------+-------+---+----------
3:1.1:1 102 102 Routed 102 102 FAIL MASTER 8 Persistent
Local Addr: 47.00918100000100001a531c2a.000001031801.00
Remote Addr: 47.00918100000200036b5e30cd.000001011802.00
Example PXM1E
Display all connections. The only connection is a daxcon that terminates at slots 19 and 20.
Unknown.8.PXM.a > dspcons
Local Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persisteny
----------------------+------------------------+---------+-------+---+----------
19.1 19 119 20.1 20 119 OK SLAVE - Persistent
Local Addr: 47.0091810000000007856e1204.000001079b01.00
Remote Addr: 47.0091810000000007856e1204.00000107a301.00
20.1 20 119 19.1 19 119 OK MASTER 8 Persistent
Local Addr: 47.0091810000000007856e1204.00000107a301.00
Remote Addr: 47.0091810000000007856e1204.000001079b01.00
dspcons-dbg
Display Connections-Debug—PXM45, PXM1E
The dspcons-dbg command shows whether the SPVC log is enabled. The dbgcon command lets you enable or disable this log.
Syntax
dspcons-dbg
Syntax Description
This command takes no parameters.
Related Commands
dbgcon
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Examples
Determine whether SPVC logging is enabled. The output shows that the log is disabled.
MGX8850.8.PXM.a > dspcons-dbg
Global SPVC Event Log Status: Disable
dspconsegep
Display Connection Segment Endpoint—PXM45, PXM1E
Displays OAM segment endpoint for a connection endpoint. When both vpi and vci are present, the segment endpoint is a F5 flow endpoint (for VCCs). When the optional vci is not present, the segment endpoint is a F4 flow endpoint (for VPCs). This command applies to established calls only.
Syntax
dspconsegep <portid> <vpi> [vci]
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
vpi
|
The VPI of the connection.
|
vci
|
The VCI of the connection.
|
Related Commands
cnfoamsegep, dspoamsegep, cnfconsegep, delconsegep
Attributes
Log: yes
|
State: active, standby
|
Privilege: ANYUSER
|
dspcontrollers
Display Controllers—PXM45, PXM1E
Displays all controllers that have been added through the addcontroller command.
Syntax
dspcontrollers
Syntax Description
This command takes no parameters.
Related Commands
addcontroller, delcontroller
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Display all controller. In this example, the switch has only one controller—PNNI. The display also shows that the controller is internal (slot 7) and has the optional, user-specified name PNNITWO. Apart from controller information, the display shows that no shelf alarms exist.
M8850_NY.7.PXM.a > dspcontrollers
M8850_NY System Rev: 02.01 Dec. 22, 2001 22:46:53 PST
MGX8850 Node Alarm: MAJOR
Controller Name: PNNI Controller
Controller Location: Internal
Controller Logical Slot: 7
Controller Line Number: 0
dspcurclk
Display Current Clock—PXM45, PXM1E
The dspcurclk command displays the current status of the network synchronization clock. For information on the fields in this display, see the following commands: cnfclksrc, cnfncdp, dspclksrcs, and dspncdpclksrc.
Syntax
dspcurclk
Syntax Description
This command takes no parameters.
Related Commands
cnfclksrc, cnfncdp, dspclksrcs, dspncdp, dspncdpclksrcs
Attributes
log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display the current clock.
PXM1E_SJ.8.PXM.a > dspcurclk
Source switchover mode :non-revertive
Use dspclksrcs, dspncdp, dspncdpclksrcs for more information.
dspdate
Display Date—PXM45, PXM1E
Display the date, time, and timezone configured on the current switch.
Syntax
dspdate
Syntax Description
This command takes no parameters.
Related Commands
cnfdate
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display the date.
Unknown.8.PXM.a > dspdate
dspdevalms
Display Device Alarms—PXM45
The dspdevalms command shows whether a crossbar alarm is minor, major, or critical. The display shows status on both the active and standby PXM45 or all the XM60s.
For fault isolation after you execute dspdevalms, you can survey the possible errors (illustrated in the example). The following is a top-down sequence of alarm-related commands:
1.
dspndalms
2.
dspswalms
3.
dspdevalms
4.
dspdeverr
5.
dspdeverrhist
Syntax
dspdevalms <device name> [-pslot <slot no>]
dspdevalms <device name> [-xslot <xbar slot>] [-pl <plane No>]
Syntax Description
device name
|
Type the mandatory device name in upper case characters. Choices are:
Note In the current release, only XBAR CORE is supported.
• XBAR CORE indicates whether the errors on a link or the whole switch plane crossed any of the alarm thresholds. Most alarms pertain to individual links, but several are plane-based. If necessary, you can configure thresholds by using cnfxbarerrthresh.
• XBAR PORT indicates whether the errors on the crossbar ports (Humvee or any equivalent) on a service module crossed the alarm thresholds.
• XBAR SLOT BANDWIDTH alarm is raised based on the number of crossbar links that are up for a service module.
|
-pslot
|
Refers to the physical slot number of the card that sends and receives cells to and from the switch planes. You can specify an individual slot for details or display all slots (with an asterisk) to show whether an error has occurred on any switch plane. In the MGX 8850 node, the slot number range is 1-14. In the MGX 8950 node, the slot number range is 1-16.
|
-xslot
|
The number of the slot where the crossbar fabric resides. You can type an asterisk to specify all switching cards. On the MGX 8850 node, the individual slot number is 7 or 8. On the MGX 8950 node, the slot is 9, 10, 25, or 26.
|
-pl
|
The plane number applies only when you specify the xslot parameter. On an MGX 8850 node, the range for switch planes is 0-2, otherwise type an asterisk * for all planes. On the MGX 8950 node, the range of plane numbers in any slot is 0-3 or * for all planes.
|
Related Commands
dspswalms, dspdeverr, dspdeverrhist, dspxbarerrthresh, clrxbaralms
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Examples
M8850_NY.7.PXM.a > dspdevalms XBARCORE -pslot 7 -pl 0
M8850_NY System Rev: 02.01 Dec. 09, 2001 23:31:46 PST
MGX8850 Node Alarm: CRITICAL
XBAR CORE ERROR ALARM INFO FOR SLOT: 7
Slot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Plane Sync Cv Disp Par CRC CRC Remap Recur Par
----- ---- ---- ---- ---- ---- ---- ---- ---- ---
7/0 -- -- -- -- -- -- -- -- --
7/1 -- -- -- -- -- -- -- -- --
7/2 -- -- -- -- -- -- -- -- --
8/0 -- -- -- -- -- -- -- -- --
8/1 -- -- -- -- -- -- -- -- --
8/2 -- -- -- -- -- -- -- -- --
XBAR CORE ERROR ALARM INFO FOR SLOT: 7
Slot/ SFrame SFrame ACP Sev
Plane Tick Lock Addr Summ.
M8850_NY.7.PXM.a > dspdevalms XBARCORE -xslot 7 -pl 0
M8850_NY System Rev: 02.01 Dec. 10, 2001 15:23:29 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE ERROR ALARM INFO:
Fabric Slot No: 7 Xbar Plane No: 0
Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Slot Sync Cv Disp Par CRC CRC Remap Recur Par
----- ---- ---- ---- ---- ---- ---- ---- ---- ---
1 -- -- -- -- -- -- -- -- --
2 -- -- -- -- -- -- -- -- --
3 -- -- -- -- -- -- -- -- --
4 -- -- -- -- -- -- -- -- --
5 -- -- -- -- -- -- -- -- --
6 -- -- -- -- -- -- -- -- --
7 -- -- -- -- -- -- -- -- --
8 -- -- -- -- -- -- -- -- --
9 -- -- -- -- -- -- -- -- --
10 -- -- -- -- -- -- -- -- --
11 -- -- -- -- -- -- -- -- --
12 -- -- -- -- -- -- -- -- --
13 -- -- -- -- -- -- -- -- --
14 -- -- -- -- -- -- -- -- --
Type <CR> to continue, Q<CR> to stop:
M8850_NY System Rev: 02.01 Dec. 10, 2001 15:23:29 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE ERROR ALARM INFO:
Fabric Slot No: 7 Xbar Plane No: 0
Slot Tick Lock Addr Summ.
----- ---- ---- ---- ----
M8950_DC.7.PXM.a > dspdevalms XBARCORE -pslot 1
M8950_DC System Rev: 02.01 Dec. 15, 2001 18:39:30 PST
MGX8950 (JBP-2) Node Alarm: CRITICAL
XBAR CORE ERROR ALARM INFO FOR SLOT: 1
Slot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Plane Sync Cv Disp Par CRC CRC Remap Recur Par
----- ---- ---- ---- ---- ---- ---- ---- ---- ---
9/0 -- -- -- -- -- -- -- -- --
9/1 -- -- -- -- -- -- -- -- --
9/2 -- -- -- -- -- -- -- -- --
9/3 -- -- -- -- -- -- -- -- --
10/0 -- -- -- -- -- -- -- -- --
10/1 -- -- -- -- -- -- -- -- --
10/2 -- -- -- -- -- -- -- -- --
10/3 -- -- -- -- -- -- -- -- --
Type <CR> to continue, Q<CR> to stop:
M8950_DC System Rev: 02.01 Dec. 15, 2001 18:39:30 PST
MGX8950 (JBP-2) Node Alarm: CRITICAL
XBAR CORE ERROR ALARM INFO FOR SLOT: 1
Slot/ SFrame SFrame ACP Sev
Plane Tick Lock Addr Summ.
Type <CR> to continue, Q<CR> to stop:
M8950_DC System Rev: 02.01 Dec. 15, 2001 18:39:30 PST
MGX8950 (JBP-2) Node Alarm: CRITICAL
XBAR CORE ERROR ALARM INFO FOR SLOT: 1
Slot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Plane Sync Cv Disp Par CRC CRC Remap Recur Par
----- ---- ---- ---- ---- ---- ---- ---- ---- ---
25/0 -- -- -- -- -- -- -- -- --
25/1 -- -- -- -- -- -- -- -- --
25/2 -- -- -- -- -- -- -- -- --
25/3 -- -- -- -- -- -- -- -- --
26/0 -- -- -- -- -- -- -- -- --
26/1 -- -- -- -- -- -- -- -- --
26/2 -- -- -- -- -- -- -- -- --
26/3 Maj Crit Crit -- Crit Crit -- -- --
Type <CR> to continue, Q<CR> to stop:
M8950_DC System Rev: 02.01 Dec. 15, 2001 18:39:30 PST
MGX8950 (JBP-2) Node Alarm: CRITICAL
XBAR CORE ERROR ALARM INFO FOR SLOT: 1
Slot/ SFrame SFrame ACP Sev
Plane Tick Lock Addr Summ.
M8950_DC.7.PXM.a > dspdevalms XBARCORE -xslot 26 -pl 3
M8950_DC System Rev: 02.01 Dec. 15, 2001 18:43:51 PST
MGX8950 (JBP-2) Node Alarm: CRITICAL
XBAR CORE ERROR ALARM INFO:
Fabric Slot No: 26 Xbar Plane No: 3
Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Slot Sync Cv Disp Par CRC CRC Remap Recur Par
----- ---- ---- ---- ---- ---- ---- ---- ---- ---
1 Maj Crit Crit -- Crit Crit -- -- --
2 -- -- -- -- -- -- -- -- --
3 -- -- -- -- -- -- -- -- --
4 -- -- -- -- -- -- -- -- --
5 -- -- -- -- -- -- -- -- --
6 -- -- -- -- -- -- -- -- --
7 -- -- -- -- -- -- -- -- --
8 -- -- -- -- -- -- -- -- --
11 -- -- -- -- -- -- -- -- --
12 -- -- -- -- -- -- -- -- --
13 -- -- -- -- -- -- -- -- --
14 -- -- -- -- -- -- -- -- --
15 -- -- -- -- -- -- -- -- --
16 -- -- -- -- -- -- -- -- --
Type <CR> to continue, Q<CR> to stop:
M8950_DC System Rev: 02.01 Dec. 15, 2001 18:43:51 PST
MGX8950 (JBP-2) Node Alarm: CRITICAL
XBAR CORE ERROR ALARM INFO:
Fabric Slot No: 26 Xbar Plane No: 3
Slot Tick Lock Addr Summ.
----- ---- ---- ---- ----
M8950_DC.7.PXM.a > dspdeverr XBARCORE -pslot 1
M8950_DC System Rev: 02.01 Dec. 15, 2001 18:38:56 PST
MGX8950 (JBP-2) Node Alarm: CRITICAL
XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1
Slot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Plane Sync Cv Disp Par CRC CRC Remap Recur Par
------ ------ ------ ------ ------ ------ ------ ------ ------ ------
XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1
MGX8950 (JBP-2) Node Alarm: CRITICAL
XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1
Slot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Plane Sync Cv Disp Par CRC CRC Remap Recur Par
------ ------ ------ ------ ------ ------ ------ ------ ------ ------
26/3 220 3300 3300 0 3300 3300 0 0 0
M8950_DC System Rev: 02.01 Dec. 15, 2001 18:38:56 PST
MGX8950 (JBP-2) Node Alarm: CRITICAL
XBAR CORE CURRENT ERROR COUNT FOR SLOT: 1
M8950_DC.7.PXM.a > dspdeverr XBARCORE -xslot 26 -pl 3
M8950_DC System Rev: 02.01 Dec. 15, 2001 18:45:43 PST
MGX8950 (JBP-2) Node Alarm: CRITICAL
XBAR CORE CURRENT ERROR COUNT :
Fabric Slot No: 26 Xbar Plane No: 3
Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Slot Sync Cv Disp Par CRC CRC Remap Recur Par
------ ------ ------ ------ ------ ------ ------ ------ ------ ------
1 220 3300 3300 0 3300 3300 0 0 0
2 -- -- -- -- -- -- -- -- --
3 -- -- -- -- -- -- -- -- --
4 -- -- -- -- -- -- -- -- --
6 -- -- -- -- -- -- -- -- --
8 -- -- -- -- -- -- -- -- --
11 -- -- -- -- -- -- -- -- --
12 -- -- -- -- -- -- -- -- --
13 -- -- -- -- -- -- -- -- --
14 -- -- -- -- -- -- -- -- --
15 -- -- -- -- -- -- -- -- --
16 -- -- -- -- -- -- -- -- --
XBAR CORE CURRENT ERROR COUNT :
Fabric Slot No: 26 Xbar Plane No: 3
dspdeverr
Display Device Errors—PXM45
The dspdeverr command shows current alarms for the switch planes. The errors can be isolated to a specific link or the entire switch plane. (A link is the hardware path between the switch plane and the recipient card's bus transceiver.) Most errors result in the shutdown of only a link. Two of the three plane-based errors shut down the entire switch plane. Also, the error r types can be
Note
The SFrame Tick and SFrame lock errors are critical and cause the whole plane to be unusable. The whole plane (and all the links on that plane) are shut down.
Syntax
dspdeverr <device name> [-pslot <slot no>]
dspdeverr <device name> [-xslot <xbar slot>] [-pl <plane No>]
Syntax Description
device name
|
Type the mandatory device name in upper case characters. Choices are:
Note In the current release, only XBAR CORE is supported.
• XBAR CORE indicates whether the errors on a link or the whole switch plane crossed any of the alarm thresholds. Most alarms pertain to individual links, but several are plane-based. If necessary, you can configure thresholds by using cnfxbarerrthresh.
• XBAR PORT indicates whether the errors on the crossbar ports (Humvee or any equivalent) on a service module crossed the alarm thresholds.
• XBAR SLOT BANDWIDTH alarm is raised based on the number of crossbar links that are up for a service module.
|
-pslot
|
The physical slot number of the card that sends and receives cells to and from the switch planes. You can specify an individual slot for details or display all slots (with an asterisk) to show whether an error has occurred on any switch plane. In the MGX 8850 node, the slot number range is 1-14. In the MGX 8950 node, the slot number range is 1-16.
|
-xslot
|
The number of the slot where the crossbar fabric resides. You can type an asterisk to specify all switching cards. On the MGX 8850 node, the individual slot number is 7 or 8. On the MGX 8950 node, the slot is 9, 10, 25, or 26.
|
-pl
|
The plane number option applies only when you also specify the xslot parameter. On the MGX 8850 node, the switch plane range for either slot is 0-2 or * for all planes.
On the MGX 8950 node, the range of plane numbers in any slot is 0-3 or * for all planes.
|
Related Commands
dspdevalms, dspdeverrhist, cnfxbarerrthresh, dspxbarerrthresh
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Do the following sequence of tasks:
1.
Display XBARCORE errors for all physical slots.
2.
Display XBARCORE errors for the physical slot that shows errors (slot 3).
3.
Display XBARCORE errors for the switching card that shows errors (slot 8).
M8850_NY.7.PXM.a > dspdeverr XBARCORE -pslot *
M8850_NY System Rev: 02.01 Dec. 25, 2001 21:17:06 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE CURRENT ERROR COUNTERS SUMMARY
Slot 7/0 7/1 7/2 8/0 8/1 8/2
----- ------ ------ ------ ------ ------ ------
M8850_NY.7.PXM.a > dspdeverr XBARCORE -pslot 3
M8850_NY System Rev: 02.01 Dec. 24, 2001 22:49:24 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE CURRENT ERROR COUNT FOR SLOT: 3
Slot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Plane Sync Cv Disp Par CRC CRC Remap Recur Par
------ ------ ------ ------ ------ ------ ------ ------ ------ ------
8/0 1 15 15 0 15 15 0 0 15
8/1 1 15 15 0 15 15 0 0 7
8/2 1 15 15 0 15 15 0 0 15
Type <CR> to continue, Q<CR> to stop:
M8850_NY System Rev: 02.01 Dec. 24, 2001 22:49:24 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE CURRENT ERROR COUNT FOR SLOT: 3
M8850_NY.7.PXM.a > dspdeverr XBARCORE -xslot 8 -pl 2
M8850_NY System Rev: 02.01 Dec. 25, 2001 21:40:39 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE CURRENT ERROR COUNT :
Fabric Slot No: 8 Xbar Plane No: 2
Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Slot Sync Cv Disp Par CRC CRC Remap Recur Par
------ ------ ------ ------ ------ ------ ------ ------ ------ ------
4 -- -- -- -- -- -- -- -- --
9 -- -- -- -- -- -- -- -- --
10 -- -- -- -- -- -- -- -- --
11 -- -- -- -- -- -- -- -- --
12 -- -- -- -- -- -- -- -- --
13 -- -- -- -- -- -- -- -- --
14 -- -- -- -- -- -- -- -- --
Type <CR> to continue, Q<CR> to stop:
M8850_NY System Rev: 02.01 Dec. 25, 2001 21:40:39 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE CURRENT ERROR COUNT :
Fabric Slot No: 8 Xbar Plane No: 2
M8850_NY.7.PXM.a > dspdeverr XBARCORE -xslot 8
M8850_NY System Rev: 02.01 Dec. 24, 2001 22:14:02 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE CURRENT ERROR COUNT :
Fabric Slot No: 8 Xbar Plane No: 0
Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Slot Sync Cv Disp Par CRC CRC Remap Recur Par
------ ------ ------ ------ ------ ------ ------ ------ ------ ------
4 -- -- -- -- -- -- -- -- --
9 -- -- -- -- -- -- -- -- --
10 -- -- -- -- -- -- -- -- --
11 -- -- -- -- -- -- -- -- --
12 -- -- -- -- -- -- -- -- --
13 -- -- -- -- -- -- -- -- --
14 -- -- -- -- -- -- -- -- --
Type <CR> to continue, Q<CR> to stop:
M8850_NY System Rev: 02.01 Dec. 24, 2001 22:14:02 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE CURRENT ERROR COUNT :
Fabric Slot No: 8 Xbar Plane No: 0
dspdeverrhist
Display Device Error History—PXM45
The dspdeverrhist command shows numbers of various types of errors on each slot-link. Note that the error can occur anywhere along the path of the ASIC and the hardware on the service module. The types of errors apply to the 60-byte switch frames.
Note
This low-level command applies to software or hardware development and is not useful for troubleshooting the network or node. For troubleshooting the node, use dspndalms and dspswalms.
You can see the thresholds for triggering the alarms by using dspxbarerrthresh.
The following types and instances of errors appear by slot number (see example screen):
•
Loss of synchronization between the ASIC and the queuing circuitry on the service module. The synchronization in this case applies to the timing of the internal switching frames (SFrames). Loss of synchronization is a very serious error.
•
Receiver code violations (Rx Cv column in the display).
•
Receiver disparity errors (Rx Disp column in the display). A disparity error is a summary of five ASIC-specific alarms.
•
Transmitter parity errors.
•
CRC failures for the header or the payload of the 60-byte Sframe.
•
Failures to remap between slots as needed or excessive remapping between slots (Slot Remap and Slot Recur columns in the display).
•
Parity errors in back-pressure messages.
•
The plane-based alarms are of three types: SFrame Tick, SFrame Lock and ACP illegal target error. All slots are affected by plane based errors.
Note
The SFrame Tick and SFrame lock errors are critical and cause the whole plane to be unusable. The whole plane (and all the links on that plane) are shut down.
A top-down sequence of troubleshooting commands for isolating faults in the switching fabric are:
1.
dspndalms
2.
dspswalms
3.
dspdevalms
4.
dspdeverrhist
Syntax
dspdeverrhist <device name> [-pslot <slot no>]
dspdeverrhist <device name> [-xslot <xbar slot>] [-pl <plane no>]
Syntax Description
device name
|
Type the mandatory device name in upper case characters. Choices are:
Note In the current release, only XBAR CORE is supported.
• XBAR CORE indicates whether the errors on a link or the whole switch plane crossed any of the alarm thresholds. Most alarms pertain to individual links, but several are plane-based. If necessary, you can configure thresholds by using cnfxbarerrthresh.
• XBAR PORT indicates whether the errors on the crossbar ports (Humvee or any equivalent) on a service module crossed the alarm thresholds.
• XBAR SLOT BANDWIDTH alarm is raised based on the number of crossbar links that are up for a service module.
|
-pslot
|
The physical slot number of the card that sends and receives cells to and from the switch planes. You can specify an individual slot for details or display all slots (with an asterisk) to show whether an error has occurred on any switch plane. In the MGX 8850 node, the slot number range is 1-14. In the MGX 8950 node, the slot number range is 1-16.
|
-xslot
|
The number of the slot where the crossbar fabric resides. You can type an asterisk to specify all switching cards. On the MGX 8850 node, the individual slot number is 7 or 8. On the MGX 8950 node, the slot is 9, 10, 25, or 26.
|
-pl
|
The plane number option applies only when you also specify the xslot parameter. On the MGX 8850 node, the switch plane range for either slot is 0-2 or * for all planes. On the MGX 8950 node, the range of plane numbers in any slot is 0-3 or * for all planes.
|
Related Commands
dspxbar, dspdevalms, dspxbarerrthresh, cnfxbarerrthresh, dspndalms, dspswalms
Attributes
Log: yes
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Two screens are necessary to display all error types. Note that the screen display can accommodate only a finite number of errors without being distorted. Therefore, a K for 1000 or an M for 1000000 multiplier may be necessary—not the case in the first example.
Display the physical slot error history for slot 1. The command parameters are XBARCORE -pslot 1. The view of this display is from the card in slot 1 to all the switch planes. The display shows a small number of errors on the switch planes on the backup PXM45. The errors are not the plane-based errors that would shut down the planes entirely (Sframe tick and SFrame lock). That the same variety of errors appear for all three switch planes suggests that the problem is not in the ASICs themselves.
M8850_NY.7.PXM.a > dspdeverrhist XBARCORE -pslot 1
M8850_NY System Rev: 02.01 Dec. 21, 2001 23:07:37 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE HISTORY ERROR COUNT FOR SLOT: 1
Slot/ Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Plane Sync Cv Disp Par CRC CRC Remap Recur Par
------ ------ ------ ------ ------ ------ ------ ------ ------ ------
8/0 2 30 30 0 30 30 0 0 21
8/1 2 30 30 0 30 30 0 0 21
8/2 2 30 30 0 30 30 0 0 19
XBAR CORE HISTORY ERROR COUNT FOR SLOT: 1
Display errors for each card slot addressed by the switch planes in slot 8.
M8850_NY.7.PXM.a > dspdeverrhist XBARCORE -xslot 8
M8850_NY System Rev: 02.01 Dec. 21, 2001 23:11:39 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE HISTORY ERROR COUNT :
Fabric Slot No: 8 Xbar Plane No: 0
Loss Rx Rx Xmit Hdr Pload Slot Slot BP
Slot Sync Cv Disp Par CRC CRC Remap Recur Par
------ ------ ------ ------ ------ ------ ------ ------ ------ ------
4 -- -- -- -- -- -- -- -- --
9 -- -- -- -- -- -- -- -- --
10 -- -- -- -- -- -- -- -- --
11 -- -- -- -- -- -- -- -- --
12 -- -- -- -- -- -- -- -- --
13 -- -- -- -- -- -- -- -- --
14 -- -- -- -- -- -- -- -- --
Type <CR> to continue, Q<CR> to stop:
M8850_NY System Rev: 02.01 Dec. 21, 2001 23:11:39 PST
MGX8850 Node Alarm: MAJOR
XBAR CORE HISTORY ERROR COUNT :
Fabric Slot No: 8 Xbar Plane No: 0
dspdiagcnf
Display Diagnostics Configuration—PXM45, PXM1E
Displays the current diagnostics configuration, such as whether online or offline is enabled, the coverage time, starting time, and the days of the week (SMTWTFS) that the offline diagnostics runs.
Coverage indicates the length of time that the diagnostics will run as follows:
•
light = 5 minutes or less
•
medium = 30 minutes or less
•
full = any number of minutes-no limit
Note
See the cnfdiag command for a detailed description of MGX 8850 diagnostics.
Syntax
dspdiagcnf
Syntax Description
This command takes no parameters.
Related Commands
cnfdiag, cnfdiagall
Attributes
Log: no
|
State: active, standby
|
Privilege: SERVICE_GP
|
Example
Unknown.8.PXM.a > dspdiagcnf
Online -------------- Offline -------------
Slot Enable Enable Coverage StartTime SMTWTFS
---- ------ ------ -------- --------- -------
1 disable disable light 00:00 SMTWTFSÄã²
2 disable disable light 00:00 SMTWTFSÄã²
3 disable disable light 00:00 SMTWTFSÄã²
4 disable disable light 00:00 SMTWTFSÄã²
5 disable disable light 00:00 SMTWTFSÄã²
6 disable disable light 00:00 SMTWTFSÄã²
7 disable disable light 00:00 SMTWTFSÄã²
8 disable enable light 18:35 -M-----Äã²
9 disable disable light 00:00 SMTWTFSÄã²
10 disable disable light 00:00 SMTWTFSÄã²
11 disable disable light 00:00 SMTWTFSÄã²
12 disable disable light 00:00 SMTWTFSÄã²
13 disable disable light 00:00 SMTWTFSÄã²
14 disable disable light 00:00 SMTWTFSÄã²
15 disable disable light 00:00 SMTWTFSÄã²
16 disable disable light 00:00 SMTWTFSÄã²
17 disable disable light 00:00 SMTWTFSÄã²
18 disable disable light 00:00 SMTWTFSÄã²
19 disable disable light 00:00 SMTWTFSÄã²
20 disable disable light 00:00 SMTWTFSÄã²
21 disable disable light 00:00 SMTWTFSÄã²
22 disable disable light 00:00 SMTWTFSÄã²
23 disable disable light 00:00 SMTWTFSÄã²
24 disable disable light 00:00 SMTWTFSÄã²
25 disable disable light 00:00 SMTWTFSÄã²
26 disable disable light 00:00 SMTWTFSÄã²
27 disable disable light 00:00 SMTWTFSÄã²
28 disable disable light 00:00 SMTWTFSÄã²
29 disable disable light 00:00 SMTWTFSÄã²
30 disable disable light 00:00 SMTWTFSÄã²
31 disable disable light 00:00 SMTWTFSÄã²
32 disable disable light 12:48 ----T--Äã²
dspdiagerr
Display Diagnostic Statistics—PXM45, PXM1E
Displays the current offline or online diagnostics errors.
Syntax
dspdiagerr <online/offline>
Syntax Description
online/offline
|
Specify whether to display the online or the offline diagnostics errors.
|
Related Commands
clrdiagerr
Attributes
Log: no
|
State: active, standby
|
Privilege: ANYUSER
|
Example
Display errors for online diagnostics.
Unknown.8.PXM.a > dspdiagerr online
dspdiagstat
Display Diagnostics Status—PXM45, PXM1E
Displays the number of times that the diagnostics has run. The output shows the number of attempts and the number of failures for both offline and online diagnostics.