5 Managing AUSM and MPSM Cards

5 Managing AUSM and MPSM Cards
C H A P T E R
5
Managing AUSM and MPSM Cards
This chapter provides procedures for managing AUSM-8T1/B, AUSM-8E1/B, MSPM-8T1-ATM, and
MSPM-8E1-ATM cards after the initial card setup and provisioning.
Note
Initial card setup is described in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco
MGX 8830 Configuration Guide, Release 5, the Release Notes for Cisco MGX 8230, Cisco MGX 8250,
and Cisco MGX 8850 (PXM1) Switches, Release 1.3.00, and the Cisco MGX 8850 Edge Concentrator
Installation and Configuration, Release 1.1.3 documentation. The provisioning of AUSM and MPSM
cards is described in Chapter 2, “Preparing AUSM and MPSM Lines and Ports for Communications,”
Chapter 3, “Provisioning SPVCs (PXM1E/PXM45) on AUSM and MPSM Cards,” and Chapter 4,
“Provisioning PVCs (PXM1) on AUSM and MPSM Cards.”
This chapter describes the following AUSM and MPSM management procedures:
•
Managing CLI Sessions
•
Managing Cards
•
Managing MPSM Feature Licenses
•
Managing Lines
•
Managing Ports
•
Managing IMA Groups
•
Managing Resource Partitions
•
Managing Connections
•
Managing Loopbacks
•
Managing Bit Error Rate Testing (BERT)
•
Managing MPSM Online Diagnostics
•
Managing MPSM Core Dumps
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-1
Chapter 5
Managing AUSM and MPSM Cards
Managing CLI Sessions
Managing CLI Sessions
Basic session initialization and management are described in the Cisco MGX 8850 (PXM1E/PXM45),
Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5, the Release Notes for Cisco
MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) Switches, Release 1.3.00, and the Cisco
MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3 documentation.
Table 5-1 lists and describes the session management commands supported on the AUSM and MPSM
cards. For more information on these commands, see Chapter 6, “AUSM and MPSM Command
Reference.”
Table 5-1
Session Management Commands
Command
Description
?
aimhelp
Help
Enter this command to display the available commands.
clear
clrscrn
cls
Enter this command to clear the session screen.
myid
Enter this command to display the user ID that was used to start the current
session.
setcmdc
Enter this command to enable or disable the command completion feature, which
automatically completes an incomplete command if the command portion
entered uniquely identifies a supported command.
setpagemode
Enables or disables the page feature, which breaks command displays into pages
for easier viewing.
Managing Cards
Basic card initialization and configuration is described in the Cisco MGX 8850 (PXM1E/PXM45), Cisco
MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5, the Release Notes for Cisco MGX
8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) Switches, Release 1.3.00, and the Cisco MGX
8850 Edge Concentrator Installation and Configuration, Release 1.1.3
The following sections provide procedures for AUSM and MPSM card management:
Note
5-2
•
Displaying General Card Information
•
Displaying Software Version and Status Information
•
Displaying AUSM Card Features
•
Managing MPSM Feature Licenses
•
Managing MPSM Feature Licenses
This section provides procedures for some of the most common card management commands. For a
complete list of card management commands, refer to Table 6-2 in Chapter 6, “AUSM and MPSM
Command Reference.”
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Cards
Displaying General Card Information
To display general information about an AUSM or MPSM card, enter the dspcd command, as shown in
the following example:
PXM1E_SJ.1.21.AUSMB8.a > dspcd
ModuleSlotNumber:
FunctionModuleState:
FunctionModuleType:
FunctionModuleSerialNum:
FunctionModuleHWRev:
FunctionModuleFWRev:
FunctionModuleResetReason:
LineModuleType:
LineModuleState:
mibVersionNumber:
configChangeTypeBitMap:
cardIntegratedAlarm:
cardMajorAlarmBitMap:
cardMinorAlarmBitMap:
21
Active
AUSM-8T1/B
820581
ae
020.000.001.000-D
Reset by PXM
LM-RJ48-8T1
Present
80
CardCnfChng, LineCnfChng
Major
Line Alarm
ATM PORT ALARM
Channel failure
Type <CR> to continue, Q<CR> to stop:
Front Card Info
Hardware Revision
Card Type
Serial Number
Fab Number
:
:
:
:
AE
52
820581
28-2160-01
Back Card Info
Hardware Revision
Card Type
Serial Number
Fab Number
:
:
:
:
AA
22
773224
28-2011-01
PXM1E_SJ.1.21.AUSMB8.a >
Note
The dspcd command displays information on card alarms.
To determine whether a card is an AUSM-8T1/B, AUSM-8E1/B, MPSM-8T1-ATM, or
MPSM-8E1-ATM card, enter the dspcd command on the AUSM or MPSM card, or use the dspcds
command on the PXM1, PXM1E, or PXM45 controller card.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-3
Chapter 5
Managing AUSM and MPSM Cards
Managing Cards
Displaying Software Version and Status Information
Enter the chkflash and version commands to display information on the software running on an AUSM
or MPSM card. The chkflash command shows the status of the boot software, and the version command
displays the software versions running on the card.
The following example shows the status of the boot software on an AUSM card:
PXM1E_SJ.1.21.AUSMB8.a > chkflash
Program length = 377836
Calculated checksum = 3818c59a stored checksum = 3818c59a
Flash checksum passed
PXM1E_SJ.1.21.AUSMB8.a >
The following example shows the status of the boot software on an MPSM card:
M8850_SF.1.28.MPSM8T1.ATM.a > chkflash
[chkflashfn]: Program length = 1427960
Calculated checksum = 0x381220db stored checksum = 0x381220db
Flash checksum passed
M8850_SF.1.28.MPSM8T1.ATM.a >
The following example shows the software versions running on an AUSM card:
PXM1E_SJ.1.21.AUSMB8.a > version
***** Cisco Systems Inc. AXIS AUSM-8T1/E1 Card *****
Firmware Version
= 020.000.001.000-D
Backup Boot version = AU8_BT_1.0.02
AUSM8p Xilinx file = ausm8pXilinx.h
VxWorks (for CISCO) version 5.1.1-R3000.
Kernel: WIND version 2.4.
Made on Mon Jul 1 23:25:34 PDT 2002.
Boot line:
PXM1E_SJ.1.21.AUSMB8.a >
The following example shows the software versions running on an MPSM card:
M8850_SF.1.28.MPSM8T1.ATM.a > version
***** Cisco System MPSM-8-T1E1 Card *****
Firmware Version
= 030.000.003.034-A
Backup Boot Version
= 030.000.003.034-A
VxWorks (for Broadcom BCM1125) version VxWorks5.4.2.
Kernel: WIND version 2.5.
Made on Apr 1 2004, 02:17:49.
Boot line:
lnPci(0,0)
M8850_SF.1.28.MPSM8T1.ATM.a >
5-4
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Feature Licenses
Displaying AUSM Card Features
Enter the dspfeature command to display the features supported on AUSM cards. The AUSM-8T1/B
and AUSM-8E1/B cards support ABR Rate Control and Inverse Multiplexing over ATM (IMA). Enter
the dspfeature command as shown in the following example to display whether Rate Control and/or IMa
are enabled on the current AUSM card:
PXM1E_SJ.1.21.AUSMB8.a > dspfeature
Rate Control: On
IMA feature: On
PXM1E_SJ.1.21.AUSMB8.a >
Managing MPSM Feature Licenses
Some features on the MPSM-8T1E1 card are enabled by the use of feature licenses. These feature
licenses reside on the PXM processor in a license pool until needed by the MPSM card.
The following sections provide procedures for doing the following:
Note
•
Displaying MPSM Feature Licenses
•
Moving MPSM Feature Licenses
•
Allocating MPSM Feature Licenses
•
Managing MPSM Feature License Alarms
To install spare feature licenses into the PXM license pool, transfer feature licenses from one switch to
another switch, and rekey feature licenses, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX
8950, and Cisco MGX 8830 Configuration Guide, Release 5 and the Release Notes for Cisco MGX 8230,
Cisco MGX 8250, and Cisco MGX 8850 (PXM1) Switches, Release 1.3.00.
Displaying MPSM Feature Licenses
Use the dspliccd command to display the details of feature licenses that are needed, that have been
allocated from the PXM license pool, or that have been programmed into the NVRAM of the
MPSM-8T1E1 card.
Because the MPSM-8T1E1 card configured for ATM services does not require any feature licenses, the
dspliccd command is used exclusively to view feature licenses that have been programmed into the
NVRAM of the MPSM-8T1E1 card.
Note
The rate control feature license is the only feature license available for the MPSM-8T1E1 card. This
feature license is used by the MPSM-8T1E1 card when configured for Frame Relay services.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-5
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Feature Licenses
In the following example, the displiccd command shows one rate control feature license programmed
into the NVRAM on the MPSM-8T1-ATM card:
M8850_SF.1.28.MPSM8T1.ATM.a > dspliccd
Card License Alarm:
None
Service Module Type:
MPSM8T1E1
Service Module Serial Number:
SAG07208RRA
Provisioning (addcon) Allowed:
YES
=========================================================
Needed License Type
Needed Licenses
--------------------------------=========================================================
Allocated License Type
Allocated licenses
--------------------------------------=========================================================
Programmed License Type
Programmed licenses
-----------------------------------------RateControl
1
=========================================================
Programmed License Registered:
NO
License registration node:
NONE
License registration chassis:
NONE
=========================================================
M8850_SF.1.28.MPSM8T1.ATM.a >
If a feature license is moved to the PXM license pool, then the Programmed License Registered field in
the output of the dspliccd command will state YES. Notice in this example that the rate control license
programmed into the NVRAM on the MPSM-8T1-ATM card has not been moved to the PXM license
pool.
Moving MPSM Feature Licenses
If a feature license is purchased at the same time as the MPSM card, that license can be programmed
into the NVRAM on the MPSM card. When a feature license is programmed on an MPSM card, the
license is unavailable to that MPSM card and all other cards on the switch. To enable use of the
programmed feature license, it must be moved from the MPSM card and installed in the switch license
pool, which is a database on the PXM processor card.
The movelic command is used to move feature licenses programmed on MPSM cards to the switch
license pool on the PXM processor card.
5-6
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Feature Licenses
To move feature licenses, perform the following steps:
Step 1
Enter the dspliccd command to view the feature licenses that have been programmed on the MPSM card:
M8850_SF.1.28.MPSM8T1.ATM.a > dspliccd
Card License Alarm:
None
Service Module Type:
MPSM8T1E1
Service Module Serial Number:
SAG07208RRA
Provisioning (addcon) Allowed:
YES
=========================================================
Needed License Type
Needed Licenses
--------------------------------=========================================================
Allocated License Type
Allocated licenses
--------------------------------------=========================================================
Programmed License Type
Programmed licenses
-----------------------------------------RateControl
1
=========================================================
Programmed License Registered:
NO
License registration node:
NONE
License registration chassis:
NONE
=========================================================
M8850_SF.1.28.MPSM8T1.ATM.a >
In this example, the output of the dspliccd command shows that one Rate Control feature license has
been programmed into the NVRAM on the MPSM card.
Step 2
Enter the movelic command to move the feature licenses programmed on the MPSM card to the switch
license pool on the PXM processor card:
M8850_SF.1.28.MPSM8T1.ATM.a > movelic
-----------------------------------------------Programmed License Type
#Programmed
--------------------------------RateControl
1
Do you want to proceed (Yes/No)? y
Card Licenses have been moved to license pool.
M8850_SF.1.28.MPSM8T1.ATM.a >
After the feature licenses are moved from the MPSM card and installed in the switch license pool on the
PXM processor card, the feature licenses are available for use by the MPSM cards installed in that switch
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-7
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Feature Licenses
Step 3
When feature licenses are moved from the NVRAM on the MPSM card to the PXM license pool, the
process is also referred to as registration of licenses with the switch.
Enter the dspliccd command to verify feature license registration into the switch license pool:
M8850_SF.1.28.MPSM8T1.ATM.a > dspliccd
Card License Alarm:
None
Service Module Type:
MPSM8T1E1
Service Module Serial Number:
SAG07208RRA
Provisioning (addcon) Allowed:
YES
=========================================================
Needed License Type
Needed Licenses
--------------------------------=========================================================
Allocated License Type
Allocated licenses
--------------------------------------=========================================================
Programmed License Type
Programmed licenses
-----------------------------------------RateControl
1
=========================================================
Programmed License Registered:
YES
License registration node:
M8850_SF
License registration chassis:
SCA062300GF
=========================================================
M8850_SF.1.28.MPSM8T1.ATM.a >
This example shows that the Rate Control feature license has been registered, the name of the switch
where the license has been registered, and the chassis serial number of the switch where the feature
license has been registered.
Step 4
Enter the dsplics command on the PXM processor card to view the MPSM feature licenses installed in
the PXM license pool:
M8850_SF.8.PXM.a >
M8850_SF
MGX8850
Licensed
Card Type
----------------MPSM-8T1E1
dsplics
System Rev: 05.00
License
Type
----------RateControl
Licenses
Installed
--------1
Aug. 05, 2004 09:12:39 GMT
Node Alarm: MAJOR
Licenses
Licenses
Allocated Available
--------- --------0
1
M8850_SF.8.PXM.a >
In this example, one Rate Control feature license has been successfully moved from the MPSM-8T1E1
card into the PXM license pool.
5-8
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Feature Licenses
Allocating MPSM Feature Licenses
To allocate a feature license to an MPSM card, configure the card to use the licensed feature.
For example, to assign a channelized feature license to an MPSM card, enter the addport command and
use the channelization parameters to channelize the line. If the license pool on the PXM has an available
license for that feature and MPSM card type, that license is automatically assigned to the card and the
feature is successfully configured.
If you try to configure an MPSM card to use a feature for which no licenses are available, the
configuration attempt will fail. Once a license is assigned to an MPSM card, it is no longer available for
use by other MPSM cards until it returns to the license pool.
Note
•
Because the MPSM-8T1E1 card configured for ATM services does not require any feature licenses,
no feature licenses are allocated from the PXM license pool for any features or services configured
on the MPSM-8T1-ATM or MPSM-8E1-ATM cards.
•
The rate control feature license is the only feature license available for the MPSM-8T1E1 card. This
feature license is used by the MPSM-8T1E1 card when configured for Frame Relay services.
Managing MPSM Feature License Alarms
MPSM feature license alarms can occur at the node level or the slot level of the switch. The following
sections describe these alarms:
Note
•
Node License Alarm
•
Slot License Alarms
Because the MPSM-8T1E1 card configured for ATM services does not require any feature licenses, no
feature licenses alarms will be raised on the MPSM-8T1-ATM or MPSM-8E1-ATM cards. The following
sections are useful in alerting the user to MPSM feature license alarm conditions that may occur for
MPSM-8T1E1 cards configured for Frame Relay services.
Node License Alarm
Node license alarms can happen under the following conditions:
•
A switch configuration that was saved before licenses were added or transferred to and from the
PXM license pool has been restored. Any mismatch between the actual license count and the
restored license count generates a minor license alarm. To prevent this type of alarm, always save
the switch configuration after you move, transfer, or add licenses.
•
The switch configuration is restored on a different node, or the Cisco MGX chassis is replaced with
another chassis. Because licenses are authorized for a specific backplane serial number, such
conditions will cause a mismatch between the physical backplane serial number and serial number
recorded in the database.
When a node license alarm is raised, all cards that are using feature licenses go into the slot license alarm
state. If no licenses are in use by the cards, no slot license alarms will be raised.
On PXM45 and PXM1E platforms, use the PXM dspndalms command to troubleshoot the node license
alarm. On PXM1 platforms, use the PXM dspcd command to troubleshoot the node license alarm.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-9
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Feature Licenses
Node license alarms are cleared by validating licenses in the license pool. This is done by applying the
special Rekey feature license to the node using the cnflic command. When the pool licenses are
validated, any existing slot license alarms are also cleared and normal operation is restored. For the
procedure to rekey feature licenses, see the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and
Cisco MGX 8830 Configuration Guide, Release 5 and the Release Notes for Cisco MGX 8230, Cisco
MGX 8250, and Cisco MGX 8850 (PXM1) Switches, Release 1.3.00.
Note
If the switch is in node license alarm, you must rekey the PXM license pool before proceeding with any
other license management tasks.
Slot License Alarms
Slot license alarms are raised under the following conditions:
•
When a node license alarm is raised, all cards that are using feature licenses go into the slot license
alarm state. Slot license alarms raised under this condition are cleared by rekeying the PXM license
pool.
•
The slot in alarm has acquired or oversubscribed one or more licenses while these licenses were not
available in the license pool. For example, on the PXM1 platform this situation might occur when a
card is configured to use licenses, the card slot configuration is removed with the PXM clrsmcnf
command, the licenses are assigned to another card, and then the card slot configuration is restored.
Slot license alarms raised under this condition are cleared by adding the required number of licenses
to the PXM license pool or by releasing corresponding licenses from other slots so that they become
available to the slot in alarm. If slots in alarm have redundancy, you must add licenses to cover both
the primary and secondary slots to clear the alarms.
On the PXM card, use the dsplicalms and dspliccd <slot> commands to troubleshoot slot license alarms.
On the MPSM card, use the dspcd and dspliccd commands to troubleshoot slot license alarms.
For the procedures to rekey feature licenses, recover feature licenses, and add feature licenses to the
PXM license pool see the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830
Configuration Guide, Release 5 and the Release Notes for Cisco MGX 8230, Cisco MGX 8250, and Cisco
MGX 8850 (PXM1) Switches, Release 1.3.00.
Note
If the switch is in node license alarm, you must rekey the PXM license pool before proceeding with any
other license management tasks.
When the switch is in slot license alarm, you have a grace period of 5 days (120 hours) to resolve the
alarm(s). During the first 4 days (96 hours), traps are sent every 24 hours. For the final 24 hours of the
grace period, traps are sent every hour of operation. If the alarms do not get cleared, the following actions
are taken:
•
An event is logged indicating the expiration of the grace period for a given slot needing license(s).
•
A trap is sent hourly indicating the expiration of the grace period.
•
The addcon command is blocked on the slot in license alarm until the license alarms are cleared.
When the PXM license pool has been rekeyed or licenses have been added to the PXM license pool,
provisioning is restored and the switch exits the license alarm state.
5-10
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Lines
Managing Lines
Chapter 2, “Preparing AUSM and MPSM Lines and Ports for Communications,” describes how to bring
up (add) and modify AUSM and MPSM card lines. The sections follow provide procedures for
performing the following line management tasks:
Note
•
Displaying a List of Lines
•
Display the Configuration for a Single Line
•
Bringing Down a Line
•
Managing Line Alarms
This section provides procedures for some of the most common line management commands. For a
complete list of line management commands, refer to Table 6-3 in Chapter 6, “AUSM and MPSM
Command Reference.”
Displaying a List of Lines
To display a list of lines on the current AUSM or MPSM card, enter the dsplns command as follows:
PXM1E_SJ.1.21.AUSMB8.a > dsplns
Line
---21.1
21.2
21.3
21.4
21.5
21.6
21.7
21.8
Conn
Type
----RJ-48
RJ-48
RJ-48
RJ-48
RJ-48
RJ-48
RJ-48
RJ-48
Type
Status/Coding
Length
XmtClock Alarm Stats
Source
Alarm
------------ ------ -------- ------------- -------- ----- ----dsx1ESF
Ena/dsx1B8ZS 0-131 ft
LocalTim Yes
Yes
dsx1ESF
Dis/dsx1B8ZS 0-131 ft
LocalTim
dsx1ESF
Dis/dsx1B8ZS 0-131 ft
LocalTim
dsx1ESF
Dis/dsx1B8ZS 0-131 ft
LocalTim
dsx1ESF
Dis/dsx1B8ZS 0-131 ft
LocalTim
dsx1ESF
Dis/dsx1B8ZS 0-131 ft
LocalTim
dsx1ESF
Dis/dsx1B8ZS 0-131 ft
LocalTim
dsx1ESF
Mod/dsx1B8ZS 0-131 ft
LoopTimi No
No
LineNumOfValidEntries: 8
PXM1E_SJ.1.21.AUSMB8.a >
The line number is found in the Line column in the format slot.line.
Display the Configuration for a Single Line
To display the configuration of a single line on an AUSM or MPSM card, enter the dspln command as
follows:
PXM1E_SJ.1.21.AUSMB8.a > dspln <line>
Replace <line> with the number of the line you want to display.
Note
You can view all available line numbers in the dsplns command display.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-11
Chapter 5
Managing AUSM and MPSM Cards
Managing Lines
The following example shows the information you can display with the dspln command on an AUSM
card:
PXM1E_SJ.1.21.AUSMB8.a > dspln 8
LineNum:
LineConnectorType:
LineType:
LineEnable:
LineCoding:
LineLength:
LineXmtClockSource:
LineLoopbackCommand:
LineSendCode:
LineUsedTimeslotsBitMap:
LineLoopbackCodeDetection:
LineBERTEnable:
8
RJ-48
dsx1ESF
Modify
dsx1B8ZS
0-131 ft
LoopTiming
NoLoop
NoCode
0xffffff
codeDetectEnabled
Disable
LineNumOfValidEntries: 8
PXM1E_SJ.1.21.AUSMB8.a >
Bringing Down a Line
When a line is not working properly, it generates a line alarm.If you want to suppress the alarm and you
do not have time to correct the problem, you can bring down the line. Bringing down the line takes it out
of service, so no alarms are generated.
Tip
You can reduce the level of an alarm on a failed line from major to minor by using the addlnloop
command to place the line in local loopback mode. This does not completely eliminate the alarm, but it
does reduce the severity and allow you to preserve the configured resources for that line.
To bring down a line, use the following procedure.
Step 1
Tip
Delete all connections that are associated with the line (dspcons and delcon commands).
Connections are associated with ports (dspcons), and ports are associated with lines (dspports). To
determine which connections use a line, first determine which ports are configured for that line.
Step 2
Delete all ports that are associated with the line (delport command)
Step 3
Enter the delln command as follows:
PXM1E_SJ.1.21.AUSMB8.a > delln <line>
Replace <line> with the number of the line you want to delete.
Note
5-12
You can view all available line numbers in the dsplns command display.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Lines
The following example shows how to use the delln command:
PXM1E_SJ.1.21.AUSMB8.a > delln 8
PXM1E_SJ.1.21.AUSMB8.a >
Managing Line Alarms
AUSM and MPSM cards generate line alarms when problems occur. When a loss of signal (LOS) alarm
is detected, an AUSM or MPSM card notifies the connected CPE in the upstream direction after an
integration period. The AUSM or MPSM card then continues to emit cells at the nominal rate but sets
the ATM cell payload with an appropriate data pattern as specified by the ATM Forum ANSI T1.231
specification. Also, an OAM cell with RDI code goes to the far end to indicate out-of-service. The
significance of the different types of alarms appears in Table 5-2.
Table 5-2
AUSM and MPSM Line Errors and Alarms
Alarm
Type
Transmit
Downstream
Transmit
Upstream
Receive LOS (Loss of
Signal)
Red
AIS OAM cells
RAI
Send line alarm
trap
Receive LOF (Loss of
Frame)
Red
AIS OAM cells
RAI
Send line alarm
trap
Receive AIS (Alarm
Indication Signal)
AIS (Blue) when
receiving AIS on
the line
AIS—OAM cells RAI
Send line alarm
trap
AIS (Blue) when
receiving AIS on
the line
AIS—OAM cells RAI
Send line alarm
trap
Receive RAI (Remote Alarm Yellow
Indication)
—
—
Send line alarm
trap
MFRAI (E1 CAS only)
Yellow
—
—
Send line alarm
trap
Loss of Multi-frame Sync
(E1 CAS only)
Red
AIS—OAM cells RAI
Send line alarm
trap
Loss of CRC MF Alignment
(E1 CRC only)
Red
AIS—OAM cells RAI
Send line alarm
trap
ATM Link Failure (Rx)
Red (AIS)
AIS—OAM cells RAI
Send line alarm
trap
Error
MFAIS (E1 CAS only)
Comments
AIS—done over
the T1/E1 link by
sending AIS data
over the T1/E1
link.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-13
Chapter 5
Managing AUSM and MPSM Cards
Managing Lines
Use the commands in table Table 5-3 to display, clear, and configure AUSM and MPSM line alarms.
Table 5-3
AUSM and MPSM Line Alarm Commands
Command
Purpose
dspalm
Enter this command to display the active alarms associated with a specific line.
dspalms
Enter this command to display a summary of the active line alarms.
dspalmcnf
Enter this command to display the alarm configuration and thresholds for a specific
line.
dspalmcnt
Enter this command to display the alarm counters for a specific line.
clralm
Enter this command to clear any active alarms on a specific line (Alarms will not clear
if the cause for the alarm is still present).
clralms
Enter this command to clear active alarms on all lines (Alarms will not clear if the
cause for the alarm is still present).
clralmcnt
Enter this command to clear the alarm counters for a specific line.
clralmcnts
Enter this command to clear the alarm counters for all lines.
xcnfalm
Enter this command to modify alarm counters, thresholds, and statistics for a specific
line.
xcnfalmcnt
Enter this command to modify threshold values of statistical alarm counters for a
specific line.
Table 5-4 lists other AUSM and MPSM card alarms and shows how these alarms affect the transmit and
receive channels for a line.
Table 5-4
Note
5-14
AUSM and MPSM Card Alarms
Type of Alarm
Channel RCV ATM
State
Channel XMT
ATM State
Port Alarm
—
Sending AIS
OAM
Generate OAM-AIS towards the network.
Abit (from PXM) Normal
Normal
—
Underrun
Normal
Normal
Conditioning towards line.
Overrun
Normal
Normal
Conditioning towards line.
Action
When the line is in alarm, a line alarm trap is sent. There are no separate traps sent for the ports or for
the connections that go into alarm due to the line alarm. Similarly when the port is in alarm, the port
alarm trap is sent, and no separate traps are sent for the connections that go into alarm due to the port
alarm.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Ports
Managing Ports
Chapter 2, “Preparing AUSM and MPSM Lines and Ports for Communications,” describes how to add
logical ports to the lines on AUSM and MPSM cards. The sections that follow provide procedures for
doing the following tasks:
•
Displaying a List of Ports
•
Displaying the Status of a Single Port
•
Deleting Ports
Displaying a List of Ports
To display a list of ports on the current AUSM or MPSM card, enter the dspports command as follows:
M8830_CH.1.13.AUSMB8.a > dspports
List of ATM ports:
==================
Port PortType Line# Portenable
---- -------- ----- ---------13.2 NNI
1
UP
Speed
----3622
PortState
--------Line alarm
List of IMA groups:
===================
ImaGrp PortType Conf Avail
rate rate
------ -------- ----- ----13.1
UNI
10773
0
NextPortNumAvailable:
Lines configured
--------------2.3.4
Lines present
Tol Diff Port State
Delay(ms)
--------------- --------- ---------275
Sig. Failure
7
M8830_CH.1.13.AUSMB8.a >
The port list is divided into two lists: one of ATM ports and one for IMA groups (which are ATM ports
using multiple lines). The port number is found in the Port column, in the format slot.port. To
determine if a port is in alarm, check the status in the Port State column.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-15
Chapter 5
Managing AUSM and MPSM Cards
Managing Ports
Displaying the Status of a Single Port
To display the configuration and status of a single port, enter the dspport command as follows:
PXM1E_SJ.1.1.AUSMB8.a > dspport <port>
Replace <port> with the number of the port you want to display.
Note
You can view the port numbers in the dspports command display.
The following example shows the dspport display for ATM port 8.
PXM1E_SJ.1.1.AUSMB8.a > dspport 8
LogicalPortNumber:
Port Enable:
Port State:
PortType:
PhysicalPortNumber:
CellFraming:
CellScramble:
Plpp Loopback:
Single-bit error correction:
8
UP
Line alarm
UNI
8
ATM
No Scramble
No Loopback
Disabled
PXM1E_SJ.1.1.AUSMB8.a >
The next example shows the report for an ATM port number that is assigned to an IMA group. This is
the same report that appears when you enter the dspimagrp command.
PXM1E_SJ.1.1.AUSMB8.a > dspport 1
IMA Group number
Port type
Lines configured
Enable
IMA Port state
IMA Group Ne state
PortSpeed (cells/sec)
GroupTxAvailCellRate (cells/sec)
ImaGroupTxFrameLength(cells)
LcpDelayTolerance (IMA frames)
ReadPtrWrPtrDiff (cells)
Minimum number of links
MaxTolerableDiffDelay (msec)
Lines Present
Observed Diff delay (msec)
Clock Mode
GroupAlpha
GroupBeta
GroupGamma
GroupConfiguration
IMAGrp Failure status
Timing reference link
ImaGroupTxImaId
ExpectedGroupRxImaId
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
1
NNI
1.2.3.4
Modify
Active
operational
14364
14364
128
1
4
2
275
1.2.3.4
0
CTC
2
2
1
1
No Failure
1
0x0
0x1
PXM1E_SJ.1.1.AUSMB8.a >
5-16
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Ports
Deleting Ports
To delete an AUSM or MPSM port, use the following procedure.
Step 1
Delete all connections that are associated with the port (dspcons and delcon commands).
Step 2
Enter the delport command as follows to delete the port:
PXM1E_SJ.1.1.AUSMB8.a > delport <port>
Replace the <port> parameter with the port number you want to delete.
Note
Tip
All port numbers on the current card are listed in the dspports command display.
When a port is deleted, the resource partition associated with that port is also deleted at the same time.
Therefore, it is not necessary to delete the port resource partition prior to deleting the port.
The following example shows how to use the delport command:
M8830_CH.1.13.AUSMB8.a > delport 1
M8830_CH.1.13.AUSMB8.a >
Note
You cannot use the delport command to delete a port number used by an IMA group. To delete an IMA
group, use the delimagrp command.
Monitoring Port Statistics
Use the commands in table Table 5-5 to display and clear AUSM and MPSM port statistics. These
commands enable the user to monitor the traffic being transmitted to and received from attached end-user
equipment.
Table 5-5
AUSM and MPSM Port Statistics Commands
Command
Purpose
dspportcnt
Enter this command to display port statistics for a specific port.
clrportcnt
Enter this command to clear port counter values on a specific port.
xclrportcnt
Enter this command to clear port counter values on a specific port.
clrportcnts
Enter this command to clear all port counters on a AUSM or MPSM card.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-17
Chapter 5
Managing AUSM and MPSM Cards
Managing Ports
The following example shows the output of the dspportcnt command on an AUSM card:
M8830_CH.1.13.AUSMB8.a > dspportcnt 1
PortNum:
PortState:
IngressRcvCells:
IngressRcvCellRate (cells/sec):
IngressRcvUtilization (percentage):
IngressXmtCells:
IngressGFCErrorCells:
IngressVpiVciErrCells:
IngressUnknownVpiVci:
IngressRcvClpSetCells:
EgressRcvCells:
EgressRcvCellRate (cells/sec):
EgressRcvUtilization (percentage):
EgressXmtCells:
EgressXmtCellRate (cells/sec):
EgressXmtUtilization (percentage):
EgressPortAlarmDiscardCells:
EgressXmtClpSetCells:
EgressXmtEfciSetCells:
PortXmtAisCells:
PortXmtSgmtLpbkCells:
1
Active
47
1
0
0
0
0
0x0
0
0
0
0
47
1
0
0
0
0
47
0
Type <CR> to continue, Q<CR> to stop:
PortRcvAisCells:
PortRcvFerfCells:
PortRcvSgmtLpbkCells:
PortRcvCrcErrOAMCells:
TotalIngressQFullDiscardCells:
TotalIngressClpSetDiscardCells:
TransmitFIFOFullCount (per card):
ReceivedHECErrorCells:
HECErroredSeconds:
SeverelyHECErroredSeconds:
46
0
0
0
0
0
0
0
0
0
M8830_CH.1.13.AUSMB8.a >
The following example clears port counter values on port 1 of an AUSM card with the clrportcnt
command:
M8850_R1.1.17.AUSMB8.a > clrportcnt 1
M8850_R1.1.17.AUSMB8.a >
The following example clears port counter values on port 1 of an AUSM card with the xclrportcnt
command:
M8850_R1.1.17.AUSMB8.a > xclrportcnt -pt 1
M8850_R1.1.17.AUSMB8.a >
The following example clears port counter values on all ports of an AUSM card with the clrportcnt
command:
M8850_R1.1.17.AUSMB8.a > clrportcnts
M8850_R1.1.17.AUSMB8.a >
5-18
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing IMA Groups
Managing IMA Groups
The “Configuring Inverse Multiplexing over ATM” section in Chapter 2, “Preparing AUSM and MPSM
Lines and Ports for Communications,” describes how to create and configure IMA groups. The following
sections provide procedures for doing the following:
Note
•
Displaying a List of IMA Groups
•
Displaying the Configuration for a Single IMA Group
•
Deleting Lines from an IMA Group
•
Deleting Lines from an IMA Group
•
Deleting an IMA Group
This section provides procedures for some of the most common IMA management commands. For a
complete list of IMA management commands, refer to Table 6-5 in Chapter 6, “AUSM and MPSM
Command Reference.”
Displaying a List of IMA Groups
To display a list of IMA groups on the current AUSM or MPSM card, enter the dspimagrps command
as follows:
PXM1E_SJ.1.1.AUSMB8.a > dspimagrps
List of IMA groups:
===================
ImaGrp PortType Conf
rate
------ -------- ----1.1
NNI
14364
1.2
NNI
14364
Avail
rate
----14364
0
NextPortNumAvailable:
Lines configured
--------------1.2.3.4
5.6.7.8
Lines present
Tol Diff
Delay(ms)
--------------- --------1.2.3.4
275
275
Port State
---------Active
Sig. Failure
5
PXM1E_SJ.1.1.AUSMB8.a >
Displaying the Configuration for a Single IMA Group
To display the configuration of a single IMA group, enter the dspimagrp command as follows:
PXM1E_SJ.1.21.AUSMB8.a > dspimagrp <group_num>
Replace <group_num> with the number of the IMA group you want to display.
Note
You can view the available group numbers in the dspimagrps display.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-19
Chapter 5
Managing AUSM and MPSM Cards
Managing IMA Groups
The following example shows the information you can display with the dspimagrp command:
PXM1E_SJ.1.1.AUSMB8.a > dspimagrp 1
IMA Group number
Port type
Lines configured
Enable
IMA Port state
IMA Group Ne state
PortSpeed (cells/sec)
GroupTxAvailCellRate (cells/sec)
ImaGroupTxFrameLength(cells)
LcpDelayTolerance (IMA frames)
ReadPtrWrPtrDiff (cells)
Minimum number of links
MaxTolerableDiffDelay (msec)
Lines Present
Observed Diff delay (msec)
Clock Mode
GroupAlpha
GroupBeta
GroupGamma
GroupConfiguration
IMAGrp Failure status
Timing reference link
ImaGroupTxImaId
ExpectedGroupRxImaId
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
1
NNI
1.2.3.4
Enabled
Active
operational
14364
14364
128
1
4
3
275
1.2.3.4
0
CTC
2
2
1
1
No Failure
1
0x0
0x0
PXM1E_SJ.1.1.AUSMB8.a >
Configuring IMA Groups
To configure an IMA group, perform the following steps:
Step 1
Establish a configuration session using a user name with GROUP 1 privileges or higher.
Step 2
If you do not know the number of the IMA group you want to configure, enter the dspimagrps command
to list the IMA groups configured on the current card.
Step 3
Enter a dspimagrp <group_num> command to display the configuration information for the particular
IMA group that you want to configure. Replace <group_num> with the number of the IMA group you
want to display, as shown in the following example:
PXM1E_SJ.1.1.AUSMB8.a > dspimagrp 1
IMA Group number
Port type
Lines configured
Enable
IMA Port state
IMA Group Ne state
PortSpeed (cells/sec)
GroupTxAvailCellRate (cells/sec)
ImaGroupTxFrameLength(cells)
LcpDelayTolerance (IMA frames)
ReadPtrWrPtrDiff (cells)
Minimum number of links
MaxTolerableDiffDelay (msec)
Lines Present
5-20
:
:
:
:
:
:
:
:
:
:
:
:
:
:
1
NNI
1.2.3.4
Enabled
Active
operational
14364
14364
128
1
4
3
275
1.2.3.4
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing IMA Groups
Observed Diff delay (msec)
Clock Mode
GroupAlpha
GroupBeta
GroupGamma
GroupConfiguration
IMAGrp Failure status
Timing reference link
ImaGroupTxImaId
ExpectedGroupRxImaId
:
:
:
:
:
:
:
:
:
:
0
CTC
2
2
1
1
No Failure
1
0x0
0x0
PXM1E_SJ.1.1.AUSMB8.a >
This sample dspimagrp command shows the configuration parameters for a four-line IMA group on the
AUSM card that is installed in slot 1.
Step 4
To configure an IMA group, enter a cnfimagrp command in the format shown below:
PXM1E_SJ.1.1.AUSMB8.a > cnfimagrp <group_num> <max_diff_delay> <minNumLink>
Table 5-6 lists and describes the parameters that you use in configuring an IMA group on an AUSM or
MPSM card.
Table 5-6
Parameters for cnfimagrp Command
Parameter
Description
group_num
Enter the number for the IMA group you want to configure. Use the dspimagrps
command to display the configured IMA groups.
max_diff_delay
Specify the maximum tolerable differential delay between the various links in
the IMA group in the range appropriate for the SM type.
minNumLink
Step 5
•
AUSM8-T1: 0–275 ms
•
AUSM8-E1: 0–200 ms
•
MPSM8-T1: 0–275 ms
•
MPSM8-E1: 0–200 ms
Enter the minimum number of lines required for group operation. For example,
if you create an IMA group of 4 lines and specify a minimum number of 3 lines,
then three of the four specified lines must be operational before the IMA group
can be used. The range for this value is from 1 to n, where n represents the
number of lines that are dedicated to the group.
Enter a dspimagrp command to verify IMA group configuration changes.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-21
Chapter 5
Managing AUSM and MPSM Cards
Managing IMA Groups
Adding an IMA Link to an IMA Group
Enter the addlns2imagrp command as follows to add one or more lines to an IMA group:
PXM1E_SJ.1.1.AUSMB8.a > addlns2imagrp <group_num> <list_of_lines>
Table 5-7 describes the parameters for the addlns2imagrp command.
Table 5-7
Parameters for addlns2imagrp Commands
Parameter
Description
group_num
Enter the number for the IMA group you want to modify.
Note
list_of_lines
Enter the dspimagrps command to display the configured IMA groups.
List the lines to be included in the group. Separate each line number by a period.
For example, 1.2.3.4 adds lines 1 through 4 to the IMA group.
Note
Enter the dsplns command to display the lines that are available for
addition to the IMA group.
The following example shows how to add a single line to an IMA group.
PXM1E_SJ.1.1.AUSMB8.a > addlns2imagrp 1 8
PXM1E_SJ.1.1.AUSMB8.a >
The next example shows how to add multiple lines to an IMA group.
PXM1E_SJ.1.1.AUSMB8.a > addlns2imagrp 1 7.8
PXM1E_SJ.1.1.AUSMB8.a >
Deleting Lines from an IMA Group
Enter the dellnsfmimagrp command as follows to delete one or more lines from an IMA group:
PXM1E_SJ.1.1.AUSMB8.a > dellnsfmimagrp <group_num> <list_of_lines>
Table 5-8 describes the parameters for this command.
Table 5-8
Parameters for dellnsfmimagrp Command
Parameter
Description
group_num
Enter the number for the IMA group from which you want to delete lines.
Note
list_of_lines
List the lines to be deleted from the group. Separate each line number by a
period. For example, 1.2.3.4 deletes lines 1 through 4 from the IMA group.
Note
5-22
Enter the dspimagrps command to display the configured IMA groups.
Enter the dspimagrp <group_num> command to display the lines that
are included in a specific IMA group. Replace <group_num> with the
number of the IMA group from which you want to delete lines.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing IMA Groups
Note
Deleting a line from an IMA group reduces the available throughput for the group and may impact ATM
traffic through the group. Also, the switch does not allow you to delete lines when the resulting number
of lines would be less than the minimum number of lines specified for group operation. To change the
minimum number of lines for an IMA group, use the cnfimagrp command.
The following example deletes a single line (line 8) from IMA group 1.
PXM1E_SJ.1.1.AUSMB8.a > dellnsfmimagrp 1 8
Warning: If Connections exist under the ima group then the cell rates might require
modification
PXM1E_SJ.1.1.AUSMB8.a >
The next example deletes multiple lines (lines 7and 8) from IMA group 1.
PXM1E_SJ.1.1.AUSMB8.a > dellnsfmimagrp 1 7.8
Warning: If Connections exist under the ima group then the cell rates might require
modification
PXM1E_SJ.1.1.AUSMB8.a >
Deleting an IMA Group
To delete an IMA group, use the following procedure.
Step 1
Tip
Delete all connections that are associated with the IMA group (dspcons and delcon commands).
The port number shown in the dspcons display is the IMA group number.
Step 2
Delete all resource partitions that are associated with the IMA group (delrscprtn command).
Step 3
Enter the delimagrp command as follows:
PXM1E_SJ.1.21.AUSMB8.a > delimagrp <group_num>
Replace <group_num> with the number of the IMA group you want to delete.
Note
You can view the available group numbers in the dspimagrps display.
The following example shows how to use the delimagrp command:
PXM1E_SJ.1.1.AUSMB8.a > delimagrp 1
PXM1E_SJ.1.1.AUSMB8.a >
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-23
Chapter 5
Managing AUSM and MPSM Cards
Managing Resource Partitions
Managing Resource Partitions
Resource partitions define how a switch’s limited resources are distributed between two or more switch
controllers. By defining the limits of the resources available to each controller, competition and overlap
is eliminated for these resources.
How resource partitions are managed on AUSM and MPSM cards is dependent upon the platform in
which the service modules are provisioned. On PXM1 platforms, service module resource partitions are
managed on both the card level and the port level. On PXM45 and PXM1E platforms, service module
resource partitions are managed only on the port level.
When a card is first brought up, the card resource partition consists of each controller sharing the
maximum number of connections available for the service module type. This equal sharing of card level
resources may be modified to eliminate resource conflicts.
When a port or IMA group is added, a port resource partition is created and consists of the number of
connections, the range of connection identifiers, and the ingress and egress bandwidth available to each
controller. By default, the port resources are fully shared among the controllers and the connection
values are inherited from the card resource partition. Port level resources may also be modified to
eliminate resource conflicts.
The following topics describe resource partitions on Cisco MGX switch platforms:
•
Resource Partitions on PXM45 and PXM1E Based Switches
•
Resource Partitions on PXM1 Based Switches
Resource Partitions on PXM45 and PXM1E Based Switches
On the PXM45 and PXM1E platforms, AUSM and MPSM resource partitions are managed only on the
port level. Cisco MGX Release 5 supports only the PNNI controller on service modules, so all port
resources are assigned to the PNNI controller when a port is added. This resource assignment is
automatically made by the software and results in the creation of a resource partition for the port.
The following section, “Managing Card Resource Partitions on PXM1 Based Switches,” describes how
to manage port resource partitions on PXM45 and PXM1E based switches.
Managing Port Resource Partitions on PXM45 and PXM1E Based Switches
The following sections describe how to manage port resource partitions on PXM45 and PXM1E
switches:
•
Displaying a Port Resource Partition Configuration on PXM45 and PXM1E Based Switches
•
Adding a Port Resource Partition on PXM45 and PXM1E Based Switches
•
Modifying a Port Resource Partition on PXM45 and PXM1E Based Switches
•
Deleting a Port Resource Partition Configuration on PXM45 and PXM1E Based Switches
During the normal operation of AUSM and MPSM cards, you do not need to add a port resource
partition. Port resource partitions are created automatically when you add a port to a line.
On the MPSM card, you can view the port resource partition configuration, make changes to it, or delete
it. If you delete a port resource partition, you will have to add a new partition for that port before you
can assign connections to the port. On the AUSM card, you can display and delete the port resource
partition, but you cannot modify it.
5-24
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Resource Partitions
Table 5-9 lists the AUSM and MPSM port resource partition commands supported on PXM45 and
PXM1E platforms in Cisco MGX Release 5. For more information on these commands, see Chapter 6,
“AUSM and MPSM Command Reference.”
Table 5-9
AUSM and MPSM Port Resource Partitioning Commands (PXM45/PXM1E Platform)
Command
Description
addrscprtn
Adds a resource partition after you have deleted the resource partition for a
port.
cnfrscprtn1
Modifies a resource partition after you have created an ATM port or an IMA
group.
delrscprtn2
Deletes a resource partition configuration.
dsprscprtn
3
Displays the configuration of a resource partition that is assigned to a specific
ATM port or IMA group.
xcnfrscprtn
cnfportrscprtn
Modifies the configuration of a port-level resource partition.
4
Modifies the configuration of a port-level resource partition.
5
Displays the configuration of a resource partition that is assigned to a specific
ATM port or IMA group.
dspportrscprtn
1. This command is similar to the cnfportrscprtn command. The ingress and egress bandwidth are configured separately.
2. This command is in the CLI, but it is not functional.
3. This command gives the same output as the dspportrscprtn command.
4. This command is similar to the cnfrscprtn command. The ingress and egress bandwidth are configured together.
5. This command gives the same output as the dsprscprtn command.
Displaying a Port Resource Partition Configuration on PXM45 and PXM1E Based Switches
To display the resource partition configuration of a port on a AUSM or MPSM card, enter the dsprscprtn
command as follows:
M8830_CH.1.13.AUSMB8.a > dsprscprtn <port_num>
Replace <port> with the number of the port whose resource partition you want to display. For example:
M8830_CH.1.13.AUSMB8.a > dsprscprtn 2
Port
User NumOfLcn
---- ----- -------2
PNNI 1000
VPI
VPID
Low/High Low/High
-------- --------0 / 255 1
/ 1000
VCI
Low/High
-----------0
/ 65535
IngrBW
EgrBW CtrlrId
-----100
----- ------100
2
M8830_CH.1.13.AUSMB8.a >
Adding a Port Resource Partition on PXM45 and PXM1E Based Switches
To add a resource partition to a port on a AUSM or MPSM card, enter the addrscprtn command as
follows:
M8830_CH.1.13.AUSMB8.a addrscprtn <portNum> <controller> <IngrPctBW> <EgrPctBW> <LowVPI>
<HighVPI> <LowVCI> <HighVCI> <LowVPID> <HighVPID> [MaxLcns]
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-25
Chapter 5
Managing AUSM and MPSM Cards
Managing Resource Partitions
Table 5-10 lists and describes the parameters for the addrscprtn command on PXM45 and PXM1E
platforms in Cisco MGX Release 5.
Table 5-10 Parameters for the addrscprtn Command
Parameter
Description
portNum
Port number associated with the resource partition to be added. You must add a
port to a line before you can define a partition for a port.
Enter the dspports command to view the available ports.
Note
controller
Controller for this partition. Enter 2 as the PNNI controller is the only controller
type supported in MGX Release 5.
•
1 = PAR (PVC)
•
2 = PNNI (SPVC)
•
3 = TAG (MPLS)
IngrPctBW
Ingress bandwidth percentage. Enter the percentage of the line bandwidth to be
used by this controller for ingress communications. Range is 0 to 100 percent.
EgrPctBW
Egress bandwidth percentage. Enter the percentage of the line bandwidth to be
used by this controller for egress communications. Range is 0 to 100 percent.
LowVPI
Enter the minimum VPI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 255.
HighVPI
Enter the maximum VPI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 255.
LowVCI
Enter the minimum VCI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 65535.
HighVCI
Enter the maximum VCI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 65535.
LowVPID
Enter the minimum virtual path identification number to allow for connections
using the specified controller type (cntrlr_type) on this port. The range is from 1
to 1000.
HighVPID
Enter the maximum virtual path identification number to allow for connections
using the specified controller type (cntrlr_type) on this port. The range is from 1
to 1000.
MaxLcns
Maximum LCNs (connections) available in this port resource partition, in the
range from 1 through 1000.
The following example adds a resource partition to a AUSM port after the default partition was deleted.
M8830_CH.1.13.AUSMB8.a > addrscprtn 1 2 100 100 100 100 3000 3000 500 500 500
M8830_CH.1.13.AUSMB8.a >
5-26
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Resource Partitions
Modifying a Port Resource Partition on PXM45 and PXM1E Based Switches
To modify the resource partition of a port on an AUSM or MPSM card, enter the cnfrscprtn command
as follows:
M8850_R1.1.17.AUSMB8.a > cnfrscprtn <portNum> <controller> <IngrPctBW> <EgrPctBW> <LowVPI>
<HighVPI> <LowVCI> <HighVCI> <LowVPID> <HighVPID> [MaxLCNs]
Table 5-11 lists and describes the parameters for the cnfrscprtn command on PXM45 and PXM1E
platforms in Cisco MGX Release 5.
Table 5-11 Parameters for the cnfrscprtn Command
Parameter
Description
portNum
Port number associated with the resource partition to be modified.
Note
controller
Enter the dspports command to view the available ports.
Controller for this partition.
•
1 = PAR (PVC)
•
2 = PNNI (SPVC)
•
3 = TAG (MPLS)
Note
Enter 2, as the PNNI controller is the only controller type supported in
MGX Release 5.
IngrPctBW
Ingress bandwidth percentage. Enter the percentage of the line bandwidth to be
used by this controller for ingress communications. Range is 0 to 100 percent.
EgrPctBW
Egress bandwidth percentage. Enter the percentage of the line bandwidth to be
used by this controller for egress communications. Range is 0 to 100 percent.
LowVPI
Enter the minimum VPI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 255.
HighVPI
Enter the maximum VPI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 255.
LowVCI
Enter the minimum VCI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 65535.
HighVCI
Enter the maximum VCI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 65535.
LowVPID
Enter the minimum virtual path identification number to allow for connections
using the specified controller type (cntrlr_type) on this port. The range is from 1
to 1000.
HighVPID
Enter the maximum virtual path identification number to allow for connections
using the specified controller type (cntrlr_type) on this port. The range is from 1
to 1000.
MaxLcns
Maximum LCNs (connections) available in this port resource partition, in the
range from 1 through 1000.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-27
Chapter 5
Managing AUSM and MPSM Cards
Managing Resource Partitions
The example that follows makes the following changes to the PNNI resource partition on port 1:
•
ingress bandwidth = 100%
•
egress bandwidth = 100%
•
minimum VPI = 255
•
maximum VPI = 255
•
minimum VCI = 65535
•
maximum VCI = 65535
•
maximum virtual path identification number = 1000
•
maximum virtual path identification number = 1000
•
maximum LCNs available = 1000
M8230_SJ.1.4.AUSM8.a > cnfrscprtn 1 2 100 100 255 255 65535 65535 1000 1000 1000
M8230_SJ.1.4.AUSM8.a >
Deleting a Port Resource Partition Configuration on PXM45 and PXM1E Based Switches
To delete the resource partition configuration of a port on an AUSM or MPSM card, use the following
procedure.
Step 1
Delete all connections that are associated with the port resource partition (dspcons and delcon
commands).
Step 2
Enter the delrscprtn command as follows:
M8230_SJ.1.4.AUSM8.a > delrscprtn <port_num> <cntrlr_type> <cntrlr_id>
Table 5-12 lists and describes the parameters for the delrscprtn command on PXM45 and PXM1E
platforms in Cisco MGX Release 5.
Table 5-12 Parameters for the delrscprtn Command
Parameter
Description
port_num
Port number associated with the resource partition to be deleted. Use the
dspports command to view the available ports.
cntrlr_type
Controller for the resource partition. Enter a number to specify the controller as
follows:
– 1 = PAR (PVC)
– 2 = PNNI (SPVC)
– 3 = TAG (MPLS)
cntrlr_id
Enter the controller ID assigned to the partition you are deleting. To display the
controller ID, use the dsprscprtn command.
The following example shows how to use the delrscprtn command:
M8230_SJ.1.4.AUSM8.a > delrscprtn 6 2 2
5-28
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Resource Partitions
Resource Partitions on PXM1 Based Switches
On the PXM1 platform, AUSM and MPSM resource partitions are managed on both the card level and
the port level. Cisco MGX Release 1.3 supports only the PAR controller on service modules, so all card
and port resources are assigned to the PAR controller when a card is brought up and a port is added.
Although the PNNI and TAG controllers are present in the card and port partition display commands,
only the PAR controller is valid on Cisco MGX Release 1.3 switches. Resource partition assignment is
automatically made by the software, and results in the creation of a resource partition for the card and
the port.
The following topics describe how to manage card and port resource partitions on PXM1 based switches:
•
Managing Card Resource Partitions on PXM1 Based Switches
•
Managing Port Resource Partitions on PXM1 Based Switches
Managing Card Resource Partitions on PXM1 Based Switches
The following tasks describe how to manage card resource partitions on PXM1 switches:
•
Displaying a Card Resource Partition Type on PXM1 Based Switches
•
Displaying a Card Resource Partition Configuration on PXM1 Based Switches
•
Adding a Card Resource Partition on PXM1 Based Switches
•
Deleting a Card Resource Configuration on PXM1 Based Switches
On AUSM and MPSM cards, the card resource partition type is not configurable. The default setting is
for a Port Controller Based card resource partition type.
During the normal operation of AUSM and MPSM cards, you will not need to add a card resource
partition. Card resource partitions are created automatically when you bring up a card.
On the AUSM and MPSM cards, you can view the card resource partition configuration, make changes
to it, or delete it. If you delete a card resource partition, you will have to add a new partition for that card
before you can assign ports to the card.
Table 5-13 lists the AUSM and MPSM card resource partition commands supported on PXM1 platforms
in Cisco MGX Release 1.3. For more information on these commands, see Chapter 6, “AUSM and
MPSM Command Reference.”
Table 5-13 AUSM/MPSM Card Resource Partitioning Commands (PXM1 Platform)
Command
cnfcdprtntype
Description
1
Configures the LCN partition type that serves as the basis for sharing
Global Logical Connection Number (GLCN) resources on a service
module.
Note
dspcdprtntype
This command is valid only on AUSM cards installed in MGX
switches that have PXM1 controllers.
Displays the LCN partition type configured on the current AUSM or
MPSM card.
Note
This command is valid only on AUSM cards installed in MGX
switches that have PXM1 controllers.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-29
Chapter 5
Managing AUSM and MPSM Cards
Managing Resource Partitions
Table 5-13 AUSM/MPSM Card Resource Partitioning Commands (PXM1 Platform) (continued)
Command
cnfcdrscprtn
Description
2
Modifies the card-level resources (LCNs) allocated to resource
partitions configured on the current AUSM card.
Note
delcdrscprtn
Deletes a card-level resource partition configured on the current AUSM
or MPSM card.
Note
dspcdrscprtn
This command is valid only on AUSM cards.
Displays the card-level resources allocated to each resource partition
configured on the current AUSM or MPSM card.
Note
oldcnfcdrscprtn
This command is valid only on AUSM cards.
This command is valid only on AUSM cards.
Modifies the maximum number of LCNs for a specific controller.
Note
This command is valid only on AUSM cards.
1. This command is in the CLI, but it is not supported.
2. This command modifies all controllers. All controllers do not have to be present. Does not add controllers not
present in the card resource partition.
Displaying a Card Resource Partition Type on PXM1 Based Switches
To display the card resource partition type of an AUSM or MPSM card, enter the dspcdprtntype
command as follows:
M8230_SJ.1.4.AUSM8.a > dspcdprtntype
cardLcnPartitionType: port controller based
M8230_SJ.1.4.AUSM8.a >
The default setting for an AUSM or MPSM card is a Port Controller Based card resource partition type.
This default setting is not configurable.
5-30
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Resource Partitions
Displaying a Card Resource Partition Configuration on PXM1 Based Switches
To display the card resource partition configuration of an AUSM or MPSM card, enter the dspcdrscprtn
command as follows:
M8230_SJ.1.4.AUSM8.a > dspcdrscprtn
User
-----PAR
PNNI
TAG
NumOfLcnAvail
------------1000
1000
1000
M8230_SJ.1.4.AUSM8.a >
Note in this example that although the PAR controller is the only controller supported on the AUSM and
MPSM cards on PXM1 platforms, the PNNI and TAG controllers are also present in the display output.
Adding a Card Resource Partition on PXM1 Based Switches
To add a card resource partition to an AUSM or MPSM card, enter the cnfcdrscprtn command as
follows:
M8230_SJ.1.4.AUSM8.a > cnfcdrscprtn <#PARcon> <#PNNIcon> <#TAGcon>
Table 5-14 lists and describes the parameters for the cnfcdrscprtn command on PXM1 platforms in
Cisco MGX Release 1.3.
Table 5-14 Parameters for the cnfcdrscprtn Command
Parameter
Description
#PARcon
Maximum number of connections (LCNs) available to the PAR controller, in the
range from 1 through 1000.
#PNNIcon
Maximum number of connections (LCNs) available to the PNNI controller, in the
range from 1 through 1000.
#TAGcon
Maximum number of connections (LCNs) available to the TAG controller, in the
range from 1 through 1000.
The following example configures an AUSM card to support up to 1000 connections for each controller:
M8230_SJ.1.4.AUSM8.a > cnfcdrscprtn 1000 1000 1000
Configuring a Card Resource Partition on PXM1 Based Switches
To modify the card-level resources (LCNs) allocated to resource partitions on the current AUSM or
MPSM card, enter the cnfcdrscprtn command as follows:
M8230_SJ.1.4.AUSM8.a > cnfcdrscprtn <#PARcon> <#PNNIcon> <#TAGcon>
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-31
Chapter 5
Managing AUSM and MPSM Cards
Managing Resource Partitions
Table 5-15 lists and describes the parameters for the cnfcdrscprtn command.
Table 5-15 Parameters for the cnfcdrscprtn Command
Parameter
Description
#PARcon
Maximum number of connections (LCNs) available to the PAR controller, in the
range from 1 through 1000.
#PNNIcon
Maximum number of connections (LCNs) available to the PNNI controller, in the
range from 1 through 1000.
#TAGcon
Maximum number of connections (LCNs) available to the TAG controller, in the
range from 1 through 1000.
The following example configures an AUSM card to support up to 1000 connections for each controller:
M8230_SJ.1.4.AUSM8.a > cnfcdrscprtn 1000 1000 1000
Deleting a Card Resource Configuration on PXM1 Based Switches
To delete a card resource partition on an AUSM or MPSM card, enter the delcdrscprtn command as
follows:
M8230_SJ.1.4.AUSM8.a > delcdrscprtn <controller>
Table 5-16 lists and describes the parameters for the delcdrscprtn command on PXM1 platforms in
Cisco MGX Release 1.3.
Table 5-16 Parameters for the delcdrscprtn Command
Parameter
Description
controller
Controller of the resource partition to delete:
•
1 = PAR (PVC)
•
2 = PNNI (SPVC)
•
3 = TAG (MPLS)
The following example deletes a PNNI card resource partition from an AUSM card:
M8230_SJ.1.4.AUSM8.a > delcdrscprtn 2
M8230_SJ.1.4.AUSM8.a >
Managing Port Resource Partitions on PXM1 Based Switches
The following tasks describe how to manage port resource partitions on PXM1 switches:
•
Displaying a Port Resource Partition Configuration on PXM1 Based Switches
•
Modifying a Port Resource Partition on PXM1 Based Switches
On the AUSM and MPSM cards, you can only view and make changes to the port resource partition
configuration. The port resource partitions are created automatically when you add a port to a line.
5-32
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Resource Partitions
Table 5-17 lists the AUSM and MPSM port resource partition commands supported on PXM1 platforms
in Cisco MGX Release 1.3. For more information on these commands, see Chapter 6, “AUSM and
MPSM Command Reference.”
Table 5-17 AUSM/MPSM Port Resource Partitioning Commands (PXM1 Platform)
Command
Description
addrscprtn
1
Adds a resource partition after you have deleted the resource partition for a
port.
cnfrscprtn2
Modifies a resource partition after you have created an ATM port or an IMA
group.
delrscprtn1
Deletes a resource partition configuration.
dsprscprtn
3
Displays the port-level resource partitions on the current AUSM or MPSM
card.
xcnfrscprtn4
Modifies the configuration of a port-level resource partition.
cnfportrscprtn
5
Modifies the configuration of a port-level resource partition.
6
Displays the port-level resource partitions on the current AUSM or MPSM
card.
dspportrscprtn
1. This command is in the CLI, but it is not supported.
2. This command is similar to the cnfportrscprtn command. The ingress and egress bandwidth are configured separately.
3. This command gives the same output as the dspportrscprtn command.
4. This command cannot add or delete, only modify.
5. This command is similar to the cnfrscprtn command. The ingress and egress bandwidth are configured together.
6. This command gives the same output as the dsprscprtn command.
Displaying a Port Resource Partition Configuration on PXM1 Based Switches
To display the resource partition configuration of a port on an AUSM or MPSM card, enter the
dspportrscprtn command as follows:
M8230_SJ.1.4.AUSM8.a > dspportrscprtn
Port
User
NumOfLcn
---- ------ -------1
PAR
1000
1
PNNI
1000
1
TAG
1000
VPI
Low/High
-------0 / 255
255/ 255
0 / 255
VPID
Low/High
---------0
/ 1000
1000/ 1000
0
/ 1000
VCI
Low/High
-----------0
/ 65535
65535/ 65535
0
/ 65535
IngrBW
EgrBW
-----100
100
100
----100
100
100
M8230_SJ.1.4.AUSM8.a >
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-33
Chapter 5
Managing AUSM and MPSM Cards
Managing Resource Partitions
Modifying a Port Resource Partition on PXM1 Based Switches
To modify a resource partition of a port on an AUSM or MPSM card, enter the cnfrscprtn command as
follows:
M8230_SJ.1.4.AUSM8.a > cnfrscprtn <port_num> <controller> <IngrPctBW> <EgrPctBW> <LowVPI>
<HighVPI> <LowVCI> <HighVCI> <LowVPID> <HighVPID> [max_lcns]
Table 5-18 lists and describes the parameters for the cnfrscprtn command on PXM1 platforms in Cisco
MGX Release 1.3.
Table 5-18 Parameters for the cnfrscprtn Command
Command
Description
port_num
Port number of the resource partition to be modified. You must add a port to a
line before you can modify the resource partition on a port. Use the dspports
command to view the available ports.
controller
Controller for this port-level resource partition. Enter a number to indicate the
controller, as follows:
– 1 = PAR
– 2 = PNNI
– 3 = TAG.
IngrPctBW
Ingress bandwidth percentage. Enter the percentage of the line bandwidth to
be used by this controller for ingress communications. Range is 1 to 100
percent.
EgrPctBWh
Egress bandwidth percentage. Enter the percentage of the line bandwidth to be
used by this controller for egress communications. Range is 1 to 100 percent.
LowVPI
Enter the minimum VPI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 255.
HighVPI
Enter the maximum VPI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 255.
LowVCI
Enter the minimum VCI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 65535.
HighVCI
Enter the maximum VCI number to allow for connections using the specified
controller type (cntrlr_type) on this port. The range is from 0 to 65535.
LowVPID
Enter the minimum virtual path identification number to allow for connections
using the specified controller type (cntrlr_type) on this port. The range is from
1 to 1000.
HighVPID
Enter the maximum virtual path identification number to allow for connections
using the specified controller type (cntrlr_type) on this port. The range is from
1 to 1000.
MaxLcn
Maximum LCNs to be available in this port resource partition. Range by card
type, in the range from 1 through 1000.
The following example modifies a port resource partition on an AUSM card:
M8850_R1.1.17.AUSMB8.a > cnfrscprtn 1 1 100 100 100 100 100 100 100 100 1000
M8850_R1.1.17.AUSMB8.a >
5-34
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Connections
Managing Connections
Chapter 3, “Provisioning SPVCs (PXM1E/PXM45) on AUSM and MPSM Cards,” and Chapter 4,
“Provisioning PVCs (PXM1) on AUSM and MPSM Cards,” describe how to add connections to AUSM
and MPSM cards. The sections that follow provide procedures for doing the following connection
management tasks:
•
Displaying a List of Connections
•
Displaying the Status of a Single Connection
•
Deleting SPVC Connections
•
Deleting PVC Connections
•
Testing Connections
•
Monitoring Connection Statistics
•
Displaying Connection Alarms
Displaying a List of Connections
Enter the dspcons command to display a list of the connections provisioned on the current AUSM or
MPSM card.
The following example shows the connections provisioned on an MPSM-8T1-ATM card installed in a
PXM45 platform:
M8850_SF.1.28.MPSM8T1.ATM.a > dspcons
LCN
---0017
0018
Port
---001
002
VPI VCI Class
--- ----- ------100 00100 CBR1
200 00200 CBR1
Number of channels:
Type M/S EgrQ Admin
----- --- ---- ----VCC
S
1
Up
VCC
M
1
Up
Alarm
----CTRLR-ABIT
E-AIS/RDI
2
ChanNumNextAvailable
:
Local VpId NextAvailable :
19
1
M8850_SF.1.28.MPSM8T1.ATM.a >
The following example shows the connections provisioned on an AUSM card installed in a PXM1
platform:
M8230_SJ.1.4.AUSM8.a > dspcons
ConnId
-----------------------M8230_SJ.4.1.100.100
M8230_SJ.4.2.200.200
ChanNumNextAvailable
:
Local VpId NextAvailable :
Chan
---16
17
ConnType
------VCC
VCC
Service Type
-----------CBR
CBR
PCR[0+1]
--------3622
3622
Q-Depth
------1000
1000
State
------Alarm
Alarm
18
1
To determine if a connection is in alarm, check the status in the Alarm column. For more information on
a single port, use the dspcon command.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-35
Chapter 5
Managing AUSM and MPSM Cards
Managing Connections
Displaying the Status of a Single Connection
To display the configuration and status of a single connection, enter the dspcon command as follows:
PXM1E_SJ.1.4.AUSMB8.a > dspcon <port.vpi.vci>
or
PXM1E_SJ.1.4.AUSMB8.a > dspcon <port_num> <vpi> <vci>
Replace the port, vpi, and vci parameters with the port number, VPI, and VCI for the connection you
want to display. You can view the port, VPI, and VCI numbers in the dspcons display.
The following example shows the configuration and status of a single connection provisioned on an
AUSM card installed in a PXM1E platform:
:
PXM1E_SJ.1.4.AUSMB8.a > dspcon 1.100.100
------------------------------------------ChanNum:
16
RowStatus: Add
AdmnState: Up
ChanState: Failed
---------- ---------- ---------- ---------PORT-ALARM CTRLR-ABIT E-AIS/RDI I-AIS/RDI
---------- ---------- ---------- ---------YES
YES
NO
NO
------------------------------------------ChanNum:
16
RowStatus:
Add
ConnAdminStatus:
Up
ConnectionType:
VCC
ServiceType:
CBR1
ChanSvcFlag:
PNNI
PortNum:
1
VPI:
100
VCI (For VCC):
100
Local VPId(for VPC):
0
EgressQNum:
1
IngressQDepth(cells):
1000
IngressDiscardOption:
CLP hysterisis
IngressFrameDiscardThreshold
1000
IngressQCLPHigh(cells):
900
IngressQCLPLow(cells):
800
QCLPState:
LOW
IngressEfciThreshold(cells):
1000
5-36
UPCEnable:
PeakCellRate[0+1](cells/sec):
CellDelayVariation[0+1]:
PeakCellRate[0](cells/sec):
CellDelayVariation[0]:
SustainedCellRate(cells/sec):
MaximumBurstSize(cells):
SCRPolicing:
CLPTagEnable:
FrameGCRAEnable:
Enabled
3591
10000 (micro secs)
3591
250000 (micro secs)
10
1024
CLP[0]
Enabled
Disable
InitialBurstSize(cells):
LocalRemoteLpbkState:
ChanTestType:
ChanTestState:
ChanRTDresult:
0
Disable
No Test
Not In Progress
65535 ms
Ingress percentage util:
Egress percentage util :
100
100
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Connections
Egress Service Rate:
LocalVpi:
LocalVci:
LocalNSAP:
RemoteVpi:
RemoteVci:
RemoteNSAP:
Mastership:
VpcFlag:
RoutingPriority:
MaxCost:
RestrictTrunkType:
LocalConnPCR:
LocalConnSCR:
LocalConnMCR:
RemoteConnPCR:
RemoteConnSCR:
RemoteConnMCR:
LocalConnMBS:
RemoteConnMBS:
Chan Reroute:
ConnPercentUtil:
ChanOvrSubOvrRide:
3591
100
100
4700918100000000016444445c00000101230100
0
0
0000000000000000000000000000000000000000
Slave
Vcc
8
2147483647
No Restriction
3591
10
10
3591
10
10
1024
1024
False
100
Enabled
Stdabr Parameters:
Minimum Cell Rate:
Peak Cell Rate:
Initial Cell rate:
Rate Increase Factor:
Rate Decrease Factor:
Nrm -- Inrate Cell Count:
Trm -- Time limit for Frm:
Transient Buffer Exposure:
Fixed Round Trip Time:
ACR Decrease Time Factor:
Cutoff Decrease Factor:
AbrType:
ChanNumNextAvailable
:
Local VpId NextAvailable :
10 Cells per second
10 Cells per second
10 Cells per second
64
16
64
255 milliseconds
16777215 Cells
0 milliseconds
500 milliseconds
16
Switch behavior without VS/VD
18
1
PXM1E_SJ.1.4.AUSMB8.a >
This example shows the configuration and status of a connection provisioned on an AUSM card installed
in a PXM1 platform:
M8230_SJ.1.4.AUSM8.a > dspcon 1 100 100
ChanNum:
RowStatus:
ConnectionType:
ServiceType:
ChanSvcFlag:
PortNum:
VPI:
VCI (For VCC):
Local VPId(for VPC):
EgressQNum:
IngressQDepth(cells):
IngressDiscardOption:
IngressFrameDiscardThreshold
IngressQCLPHigh(cells):
IngressQCLPLow(cells):
QCLPState:
16
Add
VCC
CBR
PVC
1
100
100
0
1
1000
CLP hysterisis
1000
900
800
LOW
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-37
Chapter 5
Managing AUSM and MPSM Cards
Managing Connections
IngressEfciThreshold(cells):
1000
UPCEnable:
PeakCellRate[0+1](cells/sec):
CellDelayVariation[0+1]:
Enabled
3622
10000 (micro secs)
Type <CR> to continue, Q<CR> to stop:
PeakCellRate[0](cells/sec):
CellDelayVariation[0]:
SustainedCellRate(cells/sec):
MaximumBurstSize(cells):
SCRPolicing:
CLPTagEnable:
FrameGCRAEnable:
3622
250000 (micro secs)
3622
1000
CLP[0]
Enabled
Disable
InitialBurstSize(cells):
ForesightEnable:
ForeSightPeakCellRate(cells/sec):
MinimumCellRate(cells/sec):
InitialCellRate(cells/sec):
0
Disable
3622
3622
3622
LocalRemoteLpbkState:
ChanTestType:
ChanTestState:
ChanRTDresult:
Disable
No Test
Not In Progress
65535 ms
Ingress percentage util:
Egress percentage util :
100
100
Type <CR> to continue, Q<CR> to stop:
Egress Service Rate:
LocalVpi:
LocalVci:
LocalNSAP:
RemoteVpi:
RemoteVci:
RemoteNSAP:
Mastership:
VpcFlag:
ConnServiceType:
RoutingPriority:
MaxCost:
RestrictTrunkType:
ConnPCR:
ConnMCR:
ConnPercentUtil:
ChanOvrSubOvrRide:
Stdabr Parameters:
Minimum Cell Rate:
Peak Cell Rate:
Initial Cell rate:
3622
100
100
4d383233305f534a000000000000000004000100
0
0
NULL NSAP
Slave
Vcc
CBR
1
2147483647
No Restriction
3622
3622
100
Enabled
10 Cells per second
10 Cells per second
10 Cells per second
Type <CR> to continue, Q<CR> to stop:
Rate Increase Factor:
Rate Decrease Factor:
Nrm -- Inrate Cell Count:
Trm -- Time limit for Frm:
Transient Buffer Exposure:
Fixed Round Trip Time:
ACR Decrease Time Factor:
Cutoff Decrease Factor:
5-38
64
16
64
255 milliseconds
16777215 Cells
0 milliseconds
500 milliseconds
16
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Connections
AbrType:
ChanNumNextAvailable
:
Local VpId NextAvailable :
Switch behavior without VS/VD
18
1
M8230_SJ.1.4.AUSM8.a >
Deleting SPVC Connections
Each SPVC connection has two endpoints. To completely delete a connection, you need to delete both
endpoints. To delete an SPVC connection endpoint, enter the delcon command, as shown below:
PXM1E_SJ.1.4.AUSMB8.a > delcon <port_num.vpi.vci>
or
PXM1E_SJ.1.4.AUSMB8.a > delcon <port_num> <vpi> <vci>
Replace the port, vpi, and vci parameters with the port number, VPI, and VCI for the connection you
want to delete.You can view the port, VPI, and VCI numbers in the dspcons display.
The delcon command deletes one end of the connection. Note, however, that this command does not
delete the other end of the SPVC. The other endpoint of the SPVC can reside on the same service
module, on a different service module located in the same switch, or on a service module located in a
different switch. Issue the delcon command at the location of where the other endpoint is located to
completely delete the SPVC connection.
Deleting PVC Connections
Each PVC connection has two endpoints. To completely delete a connection, you need to delete both
endpoints. How a PVC is deleted depends upon whether the PVC is a feeder segment connection or a
local connection.
To delete a feeder segment connection, perform the following steps:
Step 1
Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2
On the local AUSM or MPSM card that hosts the feeder segment connection, enter the delcon command
as shown below:
MGX_SJ.1.4.AUSMB8.a > delcon <port.vpi.vci>
or
MGX_SJ.1.4.AUSMB8.a > delcon <port_num> <vpi> <vci>
Replace the port, vpi, and vci parameters with the port number, VPI, and VCI for the connection you
want to delete. On the PXM1 platform, the port number and VPI, and VCI are found in the ConnId
column in the format Nodename.Slot.Port.VPI.VCI in the output of the dspcons command.
Since feeder segment connections are added only as master connections from a service module user port
to the PXM1 feeder trunk, the delcon command will delete both ends of the feeder segment connection.
Step 3
If the PVC you are deleting is part of a two segment feeder connection, delete the routing connection in
the ATM core network. Refer to the software configuration guides for the switches in the ATM core
network for instructions on deleting connections. See the Cisco MGX 8850 (PXM1E/PXM45), Cisco
MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5 or the Cisco BPX 8600 Series
Installation and Configuration, Release 9.3.30.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-39
Chapter 5
Managing AUSM and MPSM Cards
Managing Connections
Step 4
If the PVC you are deleting is part of a three segment feeder connection, delete the routing connection
in the ATM core network, and then log in to the remote feeder switch and delete the feeder connection
on the remote service module.
If the feeder connection on the remote switch originates from an AUSM or MPSM user port, use the
delcon command as outlined in Step 2 to delete the feeder segment connection.
If the feeder connection on the remote feeder switch originates from a user port on a card other than an
ATM service module, refer to the documentation for that card for instructions on deleting the connection.
To delete a local connection on a feeder switch or standalone switch, perform the following steps:
Step 1
Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2
On the AUSM or MPSM card that hosts one end of the local connection, enter the delcon command as
shown below:
MGX_SJ.1.4.AUSMB8.a > delcon <port.vpi.vci>
or
MGX_SJ.1.4.AUSMB8.a > delcon <port_num> <vpi> <vci>
Replace the port, vpi, and vci parameters with the port number, VPI, and VCI for the connection you
want to delete. On the PXM1 platform, the port number and VPI, and VCI is found in the ConnId
column in the format Nodename.Slot.Port.VPI.VCI in the output of the dspcons command.
Since local connections are added as slave and master endpoints, the delcon command deletes only one
endpoint of the local connection. The other endpoint of the local connection can reside on a user port
located on the same service module, or on a user port located on a different service module in the same
switch.
Step 3
If the other end of the local connection is located on an AUSM or MPSM user port, use the delcon
command as outlined in Step 2 to delete the endpoint.
If the other endpoint of the local connection is located on a user port on a card other than an ATM service
module, refer to the documentation for that card for instructions on deleting the connection.
5-40
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Connections
Testing Connections
The following tasks describe how to test ATM connections on AUSM and MPSM cards:
•
Testing with tstcon
•
Testing with tstdelay
The tstcon and tstdelay commands perform short tests that verify that the switch can communicate with
both ends of a connection. The cnftrafficgen command performs a longer or continuous test that can be
used to detect intermittent errors.
Testing with tstcon
The tstcon command checks to see if the switch can communicate with both ends of a connection. To
test an ATM connection on an AUSM or MPSM card, enter the tstcon command as follows:
PXM1E_SJ.1.4.AUSMB8.a > tstcon <port_num.vpi.vci>
Enter the connection port number, VPI, and VCI with the tstcon command.
Note
You can enter the dspcons or dspchans command to see the port number, VPI, and VCI for all
connections on the switch.
The following is an example of a tstcon test:
PXM1E_SJ.1.4.AUSMB8.a > tstcon 1.100.100
PXM1E_SJ.1.4.AUSMB8.a >
TestCon in progress.
TestCon Passed.
The tstcon command sends a single collection of supervisory cells from the local to the remote end of a
connection and displays a pass or fail message. If connection segments are failed or misconfigured, the
tstcon command fails. Note that the tstcon command does not test quality of service or connectivity
beyond the Cisco MGX network. The tstcon command has some limitations:
•
It works only for local connections or connections in a tiered network comprising a Cisco backbone
network
•
It should be issued from both ends of a connection to completely verify connectivity
•
A passing result of the test does not guarantee a connection’s end-to-end performance
Testing with tstdelay
The tstdelay command checks to see if the switch can communicate with both ends of the connection,
and it returns a measurement of the delay across the connection. To test an ATM connection, enter the
tstdelay command as follows:
PXM1E_SJ.1.4.AUSMB8.a > tstdelay <port_num.vpi.vci>
Note
You can enter the dspcons or dspchans command to see the port number, VPI, and VCI for all
connections on the switch.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-41
Chapter 5
Managing AUSM and MPSM Cards
Managing Connections
The following is an example of a tstdelay test:
PXM1E_SJ.1.4.AUSMB8.a > tstdelay 1.100.100
PXM1E_SJ.1.4.AUSMB8.a >
TestDelay in progress.
TestDelay Passed with 1 ms.
PXM1E_SJ.1.4.AUSMB8.a >
Note
The tstdelay command shares the same limitations as the tstcon command.
Monitoring Connection Statistics
Use the commands in table Table 5-19 to display and clear AUSM and MPSM connection statistics. The
channel count commands enable the user to monitor the traffic being transmitted to and received from
attached end-user equipment. The SAR counter commands enable the user to monitor the cell bus SAR
statistics.
Table 5-19 AUSM and MPSM Connection Statistics Commands
Command
Purpose
dspchancnt
Enter this command to display connection statistics of a specific connection.
xdspchancnt
Enter this command to display connection statistics of a specific connection.
clrchancnt
Enter this command to clear connection counter values of a specific connection.
xclrchancnt
Enter this command to clear connection counter values of a specific connection.
clrchancnts
Enter this command to clear connection counter values of all connections on a AUSM
or MPSM card.
dspsarcnt
Enter this command to display connection SAR statistics of a specific connection.
dspsarcnts
Enter this command to display connection SAR statistics of all connections on a
AUSM or MPSM card.
clrsarcnt
Enter this command to clear connection SAR counter values of a specific connection.
clrsarcnts
Enter this command to clear connection SAR counter values of all connections on a
AUSM or MPSM card.
The following example shows the output of the dspchancnt command on an MPSM card:
M8850_SF.1.28.MPSM8T1.ATM.a > dspchancnt 1.100.100
ChanNum:
ChannelState:
ChannelEgressRcvState:
ChannelEgressXmitState:
ChannelIngressRcvState:
ChannelIngressXmtState:
ChanInServiceSeconds:
ChanIngressPeakQDepth(cells):
ChanIngressCurrQDepth(cells):
ChanIngressReceiveCells:
5-42
17
Alarm
Receiving OAM AIS
Sending OAM AIS
Receiving AIS
Sending OAM AIS
0
0
0
0
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Connections
ChanIngressClpSetCells:
ChanIngressEfciSetRcvCells:
ChanIngressEfciSetXmtCells:
ChanIngressUpcClpSetCells:
ChanIngressQfullDiscardCells:
ChanIngressClpSetDiscardCells:
ChanIngressTransmitCells:
ChanShelfAlarmDiscardCells:
ChanEarlyPacketDiscardCells:
ChanPartialPacketDiscardCells:
ChanIngressTransmitAAL5Frames:
0
0
0
0
0
0
0
0
0
0
0
Type <CR> to continue, Q<CR> to stop:
ChanIngressReceiveCellRate(cells/sec):
ChanIngressReceiveUtilization(percentage):
ChanIngressTransmitCellRate(cells/sec):
ChanIngressTransmitUtilization(percentage):
ChanEgressReceiveCellRate(cells/sec):
ChanEgressReceiveUtilization(percentage):
EgressPortQFullDiscardCells:
EgressPortQClpThreshDiscardCells:
ChanTransmitFifoFullCount (per card):
ChanIngressUpcScrExceedCells:
ChanIngressClpHystersisDiscardCells:
0
0
0
0
0
0
0
0
0
0
0
M8850_SF.1.28.MPSM8T1.ATM.a >
In the command output, the transmit (Tx) direction is from the ATM network and service module towards
the CPE. The receive (Rx) direction is from the CPE towards the service module and ATM network.
The following example shows the output of the dspsarcnt command on a AUSM card:
M8850_R1.1.17.AUSMB8.a > dspsarcnt 2.100.0
SarShelfNum:
SarSlotNum:
SarChanNum:
Tx
--------------Total Cells:
0
Total CellsCLP:
0
Total CellsAIS:
1498
Total CellsFERF:
0
Total CellsEnd2EndLpBk: 0
Total CellsSegmentLpBk: 0
RcvCellsDiscOAM:
1
17
16
Rx
--------------0
0
24
0
0
0
0
M8850_R1.1.17.AUSMB8.a >
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-43
Chapter 5
Managing AUSM and MPSM Cards
Managing Connections
Displaying Connection Alarms
To display a list of any connections in alarm use the dspcons command:
M8850_SF.1.28.MPSM8T1.ATM.a > dspcons
LCN
---0017
0018
Port
---001
002
VPI VCI Class
--- ----- ------100 00100 CBR1
200 00200 CBR1
Number of channels:
Type M/S EgrQ Admin
----- --- ---- ----VCC
S
1
Up
VCC
M
1
Up
Alarm
----E-AIS/RDI
E-AIS/RDI
2
ChanNumNextAvailable
:
Local VpId NextAvailable :
19
1
M8850_SF.1.28.MPSM8T1.ATM.a >
The connection alarm state displayed in the dspcons command follows the following hierarchy:
ADMIN_DOWN, PORT_ALARM, CTRLR-ABIT, E-AIS/RDI, CELL LOSS
To display the status and the type of alarms present on a connection use the dspcon command, as shown
in the following example:
M8850_SF.1.28.MPSM8T1.ATM.a > dspcon 1 100 100
---------------------------------------------ChanNum:
17
RowStatus: Add
AdmnState: Up
ChanState: Alarm
---------- ---------- ---------- ---------PORT-ALARM CTRLR-ABIT E-AIS/RDI I-AIS/RDI
---------- ---------- ---------- ---------NO
NO
YES
YES
------------------------------------------Type <CR> to continue, Q<CR> to stop:
ChanNum:
RowStatus:
ConnAdminStatus:
ConnectionType:
ServiceType:
ChanSvcFlag:
PortNum:
VPI:
VCI (For VCC):
Local VPId(for VPC):
EgressQNum:
IngressQDepth(cells):
IngressDiscardOption:
IngressFrameDiscardThreshold
IngressQCLPHigh(cells):
IngressQCLPLow(cells):
QCLPState:
IngressEfciThreshold(cells):
17
Add
Up
VCC
CBR1
PNNI
1
100
100
0
1
1000
CLP hysterisis
1000
900
800
LOW
1000
UPCEnable:
PeakCellRate[0+1](cells/sec):
Enabled
3622
Type <CR> to continue, Q<CR> to stop:
CellDelayVariation[0+1]:
PeakCellRate[0](cells/sec):
5-44
10000 (micro secs)
3622
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Connections
CellDelayVariation[0]:
SustainedCellRate(cells/sec):
MaximumBurstSize(cells):
SCRPolicing:
CLPTagEnable:
FrameGCRAEnable:
250000 (micro secs)
10
1024
CLP[0]
Enabled
Disable
InitialBurstSize(cells):
LocalRemoteLpbkState:
ChanTestType:
ChanTestState:
ChanRTDresult:
0
Disable
No Test
Not In Progress
65535 ms
Ingress percentage util:
Egress percentage util :
Egress Service Rate:
LocalVpi:
LocalVci:
LocalNSAP:
100
100
3622
100
100
47009181000000000164444b6100000107e30100
Type <CR> to continue, Q<CR> to stop:
RemoteVpi:
RemoteVci:
RemoteNSAP:
Mastership:
VpcFlag:
RoutingPriority:
ChanPreferredRouteId:
ChanDirectedRoute:
MaxCost:
RestrictTrunkType:
LocalConnPCR:
LocalConnSCR:
LocalConnMCR:
RemoteConnPCR:
RemoteConnSCR:
RemoteConnMCR:
LocalConnMBS:
RemoteConnMBS:
Chan Reroute:
ConnPercentUtil:
0
0
NULL NSAP
Slave
Vcc
8
0
No
2147483647
No Restriction
3622
10
10
3622
10
10
1024
1024
False
100
Type <CR> to continue, Q<CR> to stop:
ChanOvrSubOvrRide:
Stdabr Parameters:
Minimum Cell Rate:
Peak Cell Rate:
Initial Cell rate:
Rate Increase Factor:
Rate Decrease Factor:
Nrm -- Inrate Cell Count:
Trm -- Time limit for Frm:
Transient Buffer Exposure:
Fixed Round Trip Time:
ACR Decrease Time Factor:
Cutoff Decrease Factor:
AbrType:
Enabled
10 Cells per second
10 Cells per second
10 Cells per second
64
16
64
255 milliseconds
16777215 Cells
0 milliseconds
500 milliseconds
16
Switch behavior without VS/VD
ChanNumNextAvailable
: 19
Local VpId NextAvailable : 1
M8850_SF.1.28.MPSM8T1.ATM.a >
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-45
Chapter 5
Managing AUSM and MPSM Cards
Managing Loopbacks
Managing Loopbacks
Loopbacks are used as a troubleshooting tool to aid in resolving problems with physical lines and logical
connections. The following topics describe loopbacks on the AUSM and MPSM cards:
•
AUSM Card Loopbacks
•
MPSM Card Loopbacks
AUSM Card Loopbacks
The AUSM cards support line and channel loopbacks.
Line loopbacks can be enabled by doing the following:
•
Manually placing the line in loopback mode using AUSM CLI commands
•
Enabling loopback code detection using AUSM CLI commands
•
Placing a line in loopback mode using the SRM by means of PXM BERT CLI commands
Channel loopbacks are enabled through use of CLI commands on the AUSM cards.
Figure 5-2 shows the details of where the various types of loopbacks occur within the architecture of the
AUSM card.
AUSM Line and Channel Loopbacks
Back card
AUSM-8T1E1 front card
T1/E1
T1/E1
Framer
Remote
loopback
ATM mux/
demux
hardware
SAR
Local
loopback
Cell bus
Channel
loopback
122095
Figure 5-1
Table 5-20 shows the loopback commands supported by the AUSM card. For more information on the
use of these commands, see Chapter 6, “AUSM and MPSM Command Reference.”
Table 5-20 Loopback Commands Supported on the AUSM cards
5-46
Command
Description
addlnloop
Enter this command to place a line in local loopback. When a line is in local
loopback, all data is looped back to the network.
dellnloop
Enter this command to remove the local loopback feature from a line.
cnflnloop
Enter this command to enable or disable code detection when the specified line is
placed in loopback mode.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Loopbacks
Table 5-20 Loopback Commands Supported on the AUSM cards (continued)
Command
xcnfln
Description
1
Enter this command to enable or disable a local loopback on a line by using the -lpb
option, and to enable loopback code detection by using the -detect option. Upon
detecting a loopback activate code, the line goes into remote loopback.
Note
Although remote loopback is displayed as an option for this command, it is
not supported and remote loopback must be enabled through the use of the
SRM. A line in remote loopback loops data sent from the CPE back to the
CPE.
addchanloop2
Enter this command to configure a channel loopback to the current AUSM card.
delchanloop
Enter this command to remove the local remote loopback feature from a channel. 2
xcnfcon
Enter this command to enable or disable a channel local remote loopback1 by using
the -rmtlb option.
1. Although remote loopback is displayed as an option for this command, it is not supported and remote loopback must be
enabled through the use of the SRM.
2. A channel local remote loopback is enabled on the local card and looped back in the direction of the network to the remote
end of a connection, hence the term local remote.
MPSM Card Loopbacks
The MPSM-8T1-ATM and MPSM-8E1-ATM cards support line and channel loopbacks.
Line loopbacks can be enabled by doing the following:
•
Manually placing the line in loopback mode using MPSM CLI commands
•
Enabling loopback code detection using MPSM CLI commands
•
Placing a line in loopback mode using the SRM by means of PXM BERT CLI commands
Channel loopbacks are enabled through use of CLI commands on the MPSM card.
Figure 5-2 shows the details of where the various types of loopbacks occur within the architecture of the
MPSM-8T1E1 card.
MPSM-8T1E1 Line and Channel Loopbacks
Back card
Framer/
LIU
Remote
loopback
SLFP
FPGA
Local
loopback
NP
Cell Bus
FPGA
Channel
loopback
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
116205
T1/E1
MPSM-8T1E1 Front card
Cell bus
Figure 5-2
5-47
Chapter 5
Managing AUSM and MPSM Cards
Managing Bit Error Rate Testing (BERT)
Table 5-21 describes the loopback commands supported by the MPSM-8T1-ATM and MPSM-8E1-ATM
cards. For more information on the use of these commands, see Chapter 6, “AUSM and MPSM
Command Reference.”
Table 5-21 Loopback Commands Supported on the MPSM-8T1-ATM and MPSM-8E1-ATM Cards
Command
Purpose
addlnloop
Enter this command to place a line in local loopback. When a line is in local
loopback, all data is looped back to the network.
dellnloop
Enter this command to remove the local line loopback feature from a line.
cnflnloop
Enter this command to enable and disable loopback code detection. Upon
detecting a loopback activate code, the line goes into remote loopback. A line in
remote loopback loops data sent from the CPE back to the CPE.
xcnfln
Enter this command to enable or disable a local loopback or remote loopback on
a line by using the -lpb option.
Enter this command to enable loopback code detection by using the -detect
option. Upon detecting a loopback activate code, the line goes into remote
loopback.
addchanloop
Enter this command to place a connection in channel local remote loopback.
delchanloop
Enter this command to remove the channel local remote loopback from a
connection.
xcnfchan,
xcnfcon
Enter this command to enable or disable a channel local remote loopback1 by
using the -rmtlb option.
1. Although remote loopback is displayed as an option for this command, it is not supported and remote loopback must be
enabled through the use of the SRM.
Managing Bit Error Rate Testing (BERT)
The following topics discuss Bit Error Rate Testing (BERT) on AUSM and MPSM cards:
•
SRM Supported BERT
•
MPSM-8T1E1 Onboard BERT
Bit Error Rate Testing (BERT) is utilized to determine the health of a full T1 or E1 line, or can be run
on a fractional T1 or E1 line, such as a single DS0 or group of DS0’s. Tests are categorized into three
broad areas: BERT pattern tests, loopbacks, and monitoring functions.
Bit Error Rate Testing involves sending a pseudo-random, repetitive, or user-specified pattern on a
physical line. The loopbacked pattern received by the local end is compared with the original test pattern.
The quality of a physical interface/line is determined by the number of bit errors discovered in the
received patterns. When determining the bit error rate, the following formula is used:
Bit Error Rate = bits received in error/bits sent.
BERT operations are data intrusive and regular, user traffic cannot flow on the line/port being tested while
the operation is in progress. A BERT session requires the tested path to be in a loopback mode. The line/port
is put into an alarmed state at the start of the operation and restored to a normal state when the operation is
terminated.
5-48
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Bit Error Rate Testing (BERT)
BERT should not affect performance since it is a diagnostic feature. It is however important to note that this
is a destructive/intrusive feature in that it puts the line or port being tested out of service. As a result, all
channels that exist on the line/port being tested will go into the alarmed state. This may result in a flood of
traps and/or other kinds of traffic (for example, AIS) reporting the channel alarms. This might negatively
impact the performance of other functions.
A typical sequence in performing Bit Error Rate Testing consists of the following steps:
1.
Place the far end interface on the attached end-user equipment in loopback mode if it does not
support loopback code detection.
2.
Configure BERT. The user can configure the following parameters:
– Type of loopback (The loopbacks configured are enabled when the BERT is started and deleted
when the BERT is stopped)
– Pattern to transmit
– Error rate insertion
3.
Start BERT: Start the Bit Error Rate Test on the specified interface. Generate the test pattern and
detect the incoming pattern. Compare the two patterns and update the counters.
4.
Display BERT results: Display the bit error count and the bit error rate.
5.
Stop BERT: Stop generating the test pattern and the Bit Error Rate test.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-49
Chapter 5
Managing AUSM and MPSM Cards
Managing Bit Error Rate Testing (BERT)
SRM Supported BERT
The following topics provide an overview of SRM supported BERT:
•
Overview of SRM Supported BERT
•
BERT Configuration Parameters on the SRM
Overview of SRM Supported BERT
With support from the SRM-3T3/C, SRME, or SRME/B, the Cisco MGX 8230, Cisco MGX 8250, Cisco
MGX 8850 (PXM1), Cisco MGX 8850 (PXM1E/PXM45), and Cisco MGX 8830 switches can perform
a bit error rate test (BERT) on an active T1 or E1 line or port on the MPSM-8T1-ATM,
MPSM-8E1-ATM, AUSM-8T1/B, and AUSM-8E1/B cards.
There are two BERT buses in Cisco MGX 8850 shelf. One is in the top bay and the other in the bottom bay.
The shelf can run a maximum of two sessions at once. However, the Cisco MGX 8830 shelf has only one
BERT bus, and only one BERT session can be conducted at a time.
The commands for configuring, displaying, modifying, and terminating SRM supported BERT are found
on the PXM1, PXM1E, and PXM45 processor cards.
For instructions on how to configure an SRM supported BERT on PXM1, PXM1E, and PXM45
platforms, refer to the Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release
1.1.3 and the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration
Guide, Release 5 documentation.
BERT Configuration Parameters on the SRM
During BERT configuration on the PXM processor card, the choice of parameters or menu items depends
first on the card type to be tested, and then whether the test medium is a physical line or a logical port.
Table 5-22 shows a summary of the SRM supported BERT configuration options available on the
MPSM-8T1-ATM and AUSM-8T1/B.
Table 5-22 SRM Supported BERT Configuration Options for MPSM-8T1-ATM and AUSM-8T1/B Cards
Test Medium
Medium Type
Test Type
Port with multiBERT pattern
ple timeslots
(Nx56K,
Loopback
Nx64K)
BERT pattern
Port with one
64K timeslot
DDS seek2
Loopback
Port
5-50
Port with one
56K timeslot
BERT pattern
DDS seek
2
Device to Loop
BERT Test
Patterns
Loopback Type
all
Far end loopback
v541
latch3
v541
nolatch4
l
Remote loopback
2^9
2^11
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Bit Error Rate Testing (BERT)
Table 5-22 SRM Supported BERT Configuration Options for MPSM-8T1-ATM and AUSM-8T1/B Cards
Test Medium
Medium Type
Test Type
Loopback
Device to Loop
latch3
v541
BERT Test
Patterns
Loopback Type
all
Far end loopback
BERT pattern
Line
Loopback
inband/ESF5
metallic
6
all
Remote loopback
Metallic loopback
1. A polynomial loopback which loops only the timeslots sent across. V54 is used to test select channels and does not affect
other user data on the T1.
2. Digital Dataphone Services (DDS) seek is a monitoring function test type and can be run only on a single DS0. This test is
non-destructive and detects and displays network trouble codes, such as Abnormal Station Condition, Block, Channel
Loopback, DSU Loopback, Far End Voice, Idle, Loopback Enable, MTU Alert, Mux Out of Sync, OCU Loopback, Release,
Test, Test Alert, Transition in Progress, and Unassigned MUX Channel.
3. A device that can latch the data automatically unloops the loopback after the test signal ceases.
4. A device that does not latch the data receives the test pattern sent, enables the loopback automatically, and then must be
manually taken out of loopback mode at the end of testing.
5. Far end inband loopback or far end ESF loopback.
6. A local loopback within the service module which does not involve an external device.
Table 5-23 shows a summary of the SRM supported BERT configuration options available on the
MPSM-8E1-ATM and AUSM-8E1/B cards.
Table 5-23 SRM Supported BERT Configuration Options for MPSM-8E1-ATM and AUSM-8E1/B cards
Test Medium
Port
Line
Test Type
BERT pattern
Loopback
BERT pattern
Loopback
Device to Loop
BERT Test Patterns Loopback Type
all
metallic1
all
Remote loopback
Remote loopback
Metallic loopback
1. A local loopback within the service module which does not involve an external device.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-51
Chapter 5
Managing AUSM and MPSM Cards
Managing Bit Error Rate Testing (BERT)
The available SRM supported T1 and E1 BERT patterns to choose from are shown in Table 5-24.
Table 5-24 SRM Supported T1 and E1 BERT Patterns
Supported T1 and E1 BERT Patterns
1. All zeroes
10. 3 in 24
2. All ones
11. DDS-1
3. Alternate Ones/Zeroes
12. DDS-2
4. Double Ones/Zeroes
13. DDS-3
5. 2^15 - 1 (non-ITU)
14. DDS-4
6. 2^20 - 1
15. DDS-5
7. 2^20 - 1 QRSS
16. 2^9
8. 2^23 - 1 (non-ITU)
17. 2^11
9. 1 in 8
The loopback tests do not monitor the integrity of the data but rather the integrity of the path. The type
of loopback indicates the direction of the data transmission. The loopback types supported by the SRM
are described in Table 5-25.
Table 5-25 SRM Supported BERT Loopback Options
Loopback Type
Far End Loopback
Remote Loopback
Metallic Loopback
Function
The service module transmits data to the CPE and receives the data back.
There are three subtypes of far end loopbacks: Inband, ESF, and SmartJack
inband loop codes (SRME only).
The service module receives the data from the CPE and loops back to the
CPE. Another way of configuring remote loopback is to enable loopback code
detection on the service module, then send the loopback code from the CPE.
The service module receives data from the network and loops it back to the
network. Metallic loopback is not the same as local loopback. Metallic
loopback loops the data back to the network at the physical port on the back
card of a service module, whereas local loopback loops the data back to the
network through the framer in the service module.
MPSM-8T1E1 Onboard BERT
The following topics describe MPSM-8T1E1 onboard BERT:
5-52
•
MPSM-8T1E1 Onboard BERT Features
•
Managing a BERT Session on the MPSM-8T1E1
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Bit Error Rate Testing (BERT)
MPSM-8T1E1 Onboard BERT Features
Onboard BERT features and limitations that are common to the MPSM-8T1E card, regardless of the
interface and service type configured, include:
•
The MPSM onboard BERT session is initiated from the MPSM card.
•
The use of SRM BERT and MPSM onboard BERT at the same time on the same card is not
supported.
•
Only one BERT session per line is supported.
•
All eight lines on the MPSM can be configured for BERT sessions at the same time.
•
The BERT CLI commands are not service dependent.
•
The Cisco BERT MIB is supported.
•
Line inband loopback codes are supported.
•
Remote loopbacks on ports are not supported.
•
Sending loopback codes on ports is not supported.
•
Port BERT session on 56k ports is not supported.
•
BERT sessions can be run only on active MPSM cards.
•
The tests patterns supported by the BERT generator/detector are compliant with CCITT/ITU O.150,
O.151, O.152, O.153, and O.161 standards.
Table 5-26 describes the onboard BERT commands supported by the MPSM-8T1-ATM and
MPSM-8E1-ATM cards. For more information on the use of these commands, see Chapter 5, “Managing
AUSM and MPSM Cards.”
Table 5-26 Onboard BERT Commands Supported on the MPSM-8T1-ATM and MPSM-8E1-ATM Cards
Command
Purpose
cnfbert
Enter this command to configure a BERT on a line or port.
startbert
Enter this command to begin the BERT configured on the specified line or port.
dspbert
Enter this command to view the BERT parameters configured with the cnfbert
command and to view the status of the current BERT session.
dspbertstats
Enter this command to view statistics for the BERT configured on the specified
line or port. This command can be used to view changing statistics while the Bit
Error Rate Test is running or it can be used after testing has stopped to view the
total statistics accumulated during the test period.
clrbertstats
Enter this command to clear all statistics that have accumulated during BERT on
the specified line or port. This command can be used to reset the statistics counters
while a BERT is running, or it can be used to reset statistics counters after a BERT
has been stopped.
insbiterror
Use this command to insert single bit errors into the transmitted BERT pattern
configured on the specified line or port.
stopbert
Enter this command to stop the BERT running on the specified line or port.
delbert
Enter this command to clear a BERT configuration from a line or port. This
command may be used to clear a BERT session that is running, or it may be used
after the BERT session has been stopped.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-53
Chapter 5
Managing AUSM and MPSM Cards
Managing Bit Error Rate Testing (BERT)
Managing a BERT Session on the MPSM-8T1E1
To manage a BERT session using the MPSM-8T1E1 onboard BERT feature, perform the following steps:
Step 1
If the far end interface on the attached end-user equipment does not support loopback code detection,
log into the attached end-user equipment and place the line under test into loopback mode.
Step 2
Establish a configuration session with the MPSM using a user name with GROUP1 privileges or higher.
Step 3
Enter the cnfbert command as follows to configure a BERT session:
M8850_SF.1.28.MPSM8T1.ATM.a > cnfbert <ifNumber> [-tp <TestPattern>] [-lpbk <loopback>]
[-eir <errorInsertRate>]
Table 5-27 lists and describes the parameters for the cnfbert command on the MPSM-8T1-ATM and
MPSM-8E1-ATM cards.
Table 5-27 Parameters for the cnfbert Command
Parameter
Description
ifNumber
Specify the interface number to be configured using the format line.port.
Note
To specify a Line BERT session, the Port Number = 0.
When you enter the cnfbert command with only the interface number specified
with no other options selected, the Bit Error Rate Test is configured using the
defaults: test pattern 25, no loopback, and no error insertion rate.
TestPattern
5-54
Test pattern. Default test pattern is 25.
•
1 = All Zeros
•
2 = All Ones
•
3 = Alternate One and Zero
•
4 = Double Alternate Ones and
Zeroes
•
17 = Seven Bit (2^7-1) Fractional
T1 Loop Down
•
18 = Nine Bit (2^9-1)
•
19 = Ten Bit (2^10-1)
•
20 = Eleven Bit (2^11-1)
•
5 = 1 in 4
•
21 = Fifteen Bit (2^15-1)
•
6 = 1 in 8
•
22 = Seventeen Bit (2^17-1)
•
7 = 1 in 16
•
23 = Eighteen Bit (2^18-1)
•
8 = 3 in 24
•
•
9 = Inband Loop Back Activate
24 = Twenty Bit (2^20-1) (Not
supported in Cisco MGX Releases
5 and 1.3)
•
10 = Inband Loop Back Deactivate
•
25 = Twenty Bit (2^20-1) QRSS
•
11 = Three Bit (2^3-1)
•
26 = TwentyOne Bit (2^21-1)
•
12 = Four Bit (2^4-1)
•
27 = TwentyTwo Bit (2^22-1)
•
13 = Five Bit (2^5-1)
•
28 = TwentyThree Bit (2^23-1)
•
14 = Six Bit (2^6-1)
•
29 = TwentyFive Bit (2^25-1)
•
15 = Seven Bit (2^7-1)
•
30 = TwentyEight Bit (2^28-1)
•
16 = Seven Bit (2^7-1) Fractional
T1 Loop Up
•
31 = TwentyNine Bit (2^29-1)
•
32 = ThirtyOne Bit (2^31-1)
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing Bit Error Rate Testing (BERT)
Table 5-27 Parameters for the cnfbert Command (continued)
loopback
errorInsertRate
Loopback Code.
•
Line Inband = 12
•
No Loopback = 15 (Default)
Error Insertion Rate.
•
1 = No Error (Default)
•
2 = 1 in 10
•
3 = 1 in 100
•
4 = 1 in 1,000
•
5 = 1 in 10,000
•
6 = 1 in 100,000
•
7 = 1 in 1,000,000
•
8 = 1 in 10,000,000
The following example configures a BERT session on an MPSM-8T1-ATM card on line 1 using the
default parameters:
M8850_SF.1.28.MPSM8T1.ATM.a > cnfbert 1
Use startbert to start BERT
Use delbert followed by cnfbert to re-configure BERT parameters
M8850_SF.1.28.MPSM8T1.ATM.a >
Step 4
Enter the dspbert command as follows to view the BERT parameters configured with the cnfbert
command:
M8850_SF.1.28.MPSM8T1.ATM.a > dspbert <ifNumber>
Replace the ifNumber parameter with the line and port number configured for the BERT session, in the
format line.port. To specify a line test, enter a port value of zero.
The following example shows the BERT parameters configured in Step 3:
M8850_SF.1.28.MPSM8T1.ATM.a > dspbert 1
Interface Number
Loopback Code
Pattern
ErrorInsertRate
Start Date/Time
Operational Status
:
:
:
:
:
:
1.0
No Loopback
TwoE20MinusOneQRSS
NoError
Not Started
Out Of Sync
M8850_SF.1.28.MPSM8T1.ATM.a >
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-55
Chapter 5
Managing AUSM and MPSM Cards
Managing Bit Error Rate Testing (BERT)
Step 5
Enter the startbert command as follows to start a BERT session:
M8850_SF.1.28.MPSM8T1.ATM.a > startbert <ifNumber>
Replace the ifNumber parameter with the line and port number configured for the BERT session, in the
format line.port. To specify a line test, enter a port value of zero.
The following example starts a BERT session:
M8850_SF.1.28.MPSM8T1.ATM.a > startbert 1.1
ERR: Port BERT not supported for ATM/IMA Port
Step 6
Enter the dspbert command to verify the start of the BERT session:
M8850_SF.1.28.MPSM8T1.ATM.a > dspbert 1
Interface Number
Loopback Code
Pattern
ErrorInsertRate
Start Date/Time
Operational Status
:
:
:
:
:
:
1.0
No Loopback
TwoE20MinusOneQRSS
NoError
Not Started
Out Of Sync
M8850_SF.1.28.MPSM8T1.ATM.a >
In this example, the Operational Status of In Sync indicates that the test has been successfully started.
Step 7
Enter the dspbertstats command as follows to view statistics from a BERT session in progress:
8850_SF.1.28.MPSM8T1.ATM.a > dspbertstats <ifNumber>
Replace the ifNumber parameter with the line and port number configured for the BERT session, in the
format line.port. To specify a line test, enter a port value of zero.
The following example displays statistics from a BERT session in progress:
M8250_SJ.1.6.MPSM8T1.ATM.a > dspbertstats 1.1
Interface Number
Rx Bit Count
Rx Bit Error Count
Sync Loss Transition
Pattern Loss Count (secs)
:
:
:
:
:
1.1
29493114
1
0
0
M8250_SJ.1.6.MPSM8T1.ATM.a >
The dspbertstats command may also be used to view the total statistics gathered during a BERT session
after the test has been stopped.
To clear the incrementing statistics during a BERT session or after the BERT session has been stopped,
enter the clrbertstats command to reset the statistics counters.
Step 8
Enter the insbiterror command as follows to insert single bit errors into an active BERT session:
M8850_SF.1.28.MPSM8T1.ATM.a > insbiterror <ifNumber>
Replace the ifNumber parameter with the line and port number configured for the BERT session, in the
format line.port. To specify a line test, enter a port value of zero.
The following example inserts a single bit error into the BERT session in progress:
M8850_SF.1.28.MPSM8T1.ATM.a > insbiterror 1.1
5-56
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Online Diagnostics
Step 9
Enter the stopbert command as follows to stop a BERT session:
M8850_SF.1.28.MPSM8T1.ATM.a > delbert <ifNumber>
Replace the ifNumber parameter with the line and port number configured for the BERT session, in the
format line.port. To specify a line test, enter a port value of zero.
The following example stops the current BERT session:
M8850_SF.1.28.MPSM8T1.ATM.a > stopbert 1.1
After a BERT session has been stopped, it may be restarted by using the startbert command.
Step 10
Enter the delbert command as follows to clear a BERT configuration:
M8850_SF.1.28.MPSM8T1.ATM.a > delbert <ifNumber>
Replace the ifNumber parameter with the line and port number configured for the BERT session, in the
format line.port. To specify a line test, enter a port value of zero.
The following example clears the current BERT session configuration:
M8250_SJ.1.6.MPSM8T1.ATM.a > delbert 1.1
M8250_SJ.1.6.MPSM8T1.ATM.a >
To modify the configuration parameters of a BERT session, you must first clear the current BERT
configuration with the delbert command, and then reconfigure the new parameters with the cnfbert
command.
Managing MPSM Online Diagnostics
The following topics describe MPSM-8T1E1 online diagnostics:
•
MPSM-8T1E1 Online Diagnostics Features
•
Managing Online Diagnostics on the MPSM-8T1E1
MPSM-8T1E1 Online Diagnostics Features
The MPSM-8T1E1 online diagnostics are used to test and monitor the health of the components and data
paths on the MPSM card after its successful boot up. These tests are used solely for hardware diagnosis,
and are not used to detect operational errors.
Online tests are diagnostics performed by the run-time firmware while a card is in an Active or Standby
operational state. These tests are limited on the Active card due to the requirements that the tests be
non-intrusive and not affect user traffic. More elaborate tests are performed on the Standby card without
affecting switch-over time. Note that these tests cannot be configured on the Standby card using CLI
commands. The tests have to be pre-configured when the card is in an Active state to run on a card in
Standby mode.
Note
In Cisco MGX Releases 5 and 1.3, diagnostic tests are supported only on Active cards.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-57
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Online Diagnostics
Although alarms, logs, and traps are generated upon the failure of a test, there is no SNMP support for
test configuration. All test configuration must be done by means of CLI commands on the MPSM card.
Tests may be scheduled to run in the online diagnostics test suite, or run individually.
Note
The tests are common to all service types configured on the MPSM-8T1E1 card, however NP Utilization
tests are not supported on an MPSM card in Frame Relay mode.
Table 5-28 shows the online diagnostics tests available on the MPSM-8T1E1 card.
Table 5-28 MPSM-8T1E1 Online Diagnostics Tests
5-58
Test
ID
Test Name
Function
1
Boot Checksum
This test verifies the checksum for the boot code in Flash memory.
2
Front card NVRAM
Checksum
This test performs a front card NVRAM checksum test.
3
CPU Performance Monitor
This test monitors CPU performance based on the idle time.
4
NP Performance Monitor
This test monitors Network Processor performance based on the idle
time.
5
SLFP Access
This test accesses diagnostic registers in the SLFP FPGA and
performs pattern tests to verify databus integrity.
6
MPCTL Access
This test accesses diagnostic registers in the MPCTL FPGA and
performs pattern tests to verify databus integrity.
7
FRAMER Access
This test accesses diagnostic registers in the FRAMER and
performs pattern tests to verify databus integrity.
8
LDRAM Memory
Availability
This test monitors the available DRAM memory.
9
Host Memory Availability
This test monitors the available Host memory.
10
Packet Memory
Availability
This test monitors the available Packet memory.
11
Internal Memory
Availability
This test monitors the available Internal memory.
12
Parameter Memory
Availability
This test monitors the available Parameter memory.
13
Host Memory Access
This test accesses the Host memory and performs diagnostic
pattern tests to verify databus integrity.
14
Packet Memory Access
This test accesses the Packet memory and performs diagnostic
pattern tests to verify databus integrity.
15
Parameter Memory Access This test accesses the Parameter memory and performs diagnostic
pattern tests to verify databus integrity.
16
MPCTL Error Monitor
This test monitors the error counters for the MPCTL FPGA.
17
NP Error Monitor
This test monitors the error counters for the Network Processor
input parameters.
18
NP Health Check
This test monitors the health of the Network Processor.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Online Diagnostics
Table 5-28 MPSM-8T1E1 Online Diagnostics Tests (continued)
Test
ID
Test Name
Function
19
MPCTL Loopback
This test verifies the data path between the CPU and the MPCTL
by injecting cells on a diagnostic LCN that the MPCTL will loop
back.
20
PXM Data Path Loopback
Test
This test verifies the data path between the MPSM and the PXM
by injecting cells on a diagnostic LCN that the PXM will loop
back.
21
NP TDM Loopback Test
This test verifies the data path between the CPU and the NP TDM
port by injecting cells on a diagnostic LCN that the NP will loop
back. (This test is not supported on an MPSM card in Active
mode)
22
SLFP TDM Loopback Test This test verifies the data path between the CPU and the SLFP by
injecting cells on a diagnostic LCN that the SLFP will loop back.
(This test is not supported on an MPSM card in Active mode)
23
Framer Loopback Test
This test verifies the data path between the CPU and the Framer
by injecting cells on a diagnostic LCN that the Framer will loop
back. (This test is not supported on an MPSM card in Active
mode)
Table 5-29 shows the CLI commands used to configure and manage online diagnostics on the
MPSM-8T1E1 card. For more information on the use of these commands, see Chapter 6, “AUSM and
MPSM Command Reference.”
Table 5-29 MPSM-8T1E1 Online Diagnostics Commands
Command
Purpose
dspdiagtests
Enter this command to view the complete list of available online diagnostic tests
configured on the current MPSM card. Using this command with the Test ID
number option will give detailed information about a specific online diagnostic
test.
cnfdiagtest
Enter this command to modify the parameters of a single diagnostic test that is a
member of the online diagnostics test suite. This command may also be used to
modify all online diagnostic tests at the same time.
rundiagtest
Enter this command to run an individual online diagnostic test.
dspdiagresults
Enter this command to display the results of the configured diagnostic tests.
clrdiagresults
Enter this command to clear the results of all the configured online diagnostic
tests.
pausediag
Enter this command to temporarily stop the scheduled online diagnostic tests.
resumediag
Enter this command to resume the previously paused diagnostic tests.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-59
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Online Diagnostics
Managing Online Diagnostics on the MPSM-8T1E1
To manage online diagnostics on the MPSM-8T1E1, perform the following steps:
Step 1
Establish a configuration session with the MPSM using a user name with GROUP1 privileges or higher.
Step 2
Enter the dspdiagtests command as follows to view the available online diagnostics tests on the
MPSM-8T1E1 card:
M8850_SF.1.28.MPSM8T1.ATM.a > dspdiagtests
ID
-1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
Name
---------------------------Boot Checksum
Front card NVRAM Checksum
CPU Performance Monitor
NP Performance Monitor
SLFP Access
MPCTL Access
FRAMER Access
LDRAM Memory Availability
Host Memory Availability
Packet Memory Availability
Internal Memory Availability
Parameter Memory Availability
Host Memory Access
Packet Memory Access
Parameter Memory Access
MPCTL Error Monitor
NP Error Monitor
NP Health Check
MPCTL Loopback
PXM Data Path Loopback Test
NP TDM Loopback Test
SLFP TDM Loopback Test
Framer Loopback Test
Enable
------No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
Role
StartTOD
------ -------Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Active
NOW
Period
-----1440
1440
5
5
5
5
5
5
30
30
30
30
1
5
5
5
5
5
1
1
30
30
30
Iteratns
-------FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
FOREVER
Online Diagnostic tests RUNNING.
The output of the dspdiagtests commands shows the current configuration and status of all the available
tests.
Step 3
Enter the dspdiagtests command as follows to view detailed information about a specific online
diagnostic test:
M8250_SJ.1.22.MPSM8T1.ATM.a > dspdiagtests <TestId>
Replace the TestId parameter with the ID number of the test shown in the dspdiagtests command display.
The following example shows the status and configuration of test number 2:
M8850_SF.1.28.MPSM8T1.ATM.a > dspdiagtests 2
Test Name: Front card NVRAM Checksum
Function: Performs Front card NVRAM Checksum test.
Input Parameters: None
Note: This test cannot be run more than once a day.
Alarm Raised on Failure: Major
Recovery Action: N.A
Role: Active
Enable: No
StartTOD: NOW
Period: 1440
Iterations: FOREVER
Configured Parameters: N/A, N/A
5-60
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Online Diagnostics
Step 4
Enter the cnfdiagtest command as follows to modify the default configuration of a specific test or all
online diagnostic tests:
M8250_SJ.1.22.MPSM8T1.ATM.a > cnfdiagtest <TestId> [<enable|disable>] [-role <role>]
[-startTOD <time>] [-period <period>] [-iterns <iterns>] [-param1 <param>] [-param2
<param>]
Table 5-30 lists and describes the parameters for the cnfdiagtest command on the MPSM-8T1-ATM and
MPSM-8E1-ATM cards.
Table 5-30 Parameters for the cnfdiagtest Command
Parameter
Description
TestId
Test ID number of the diagnostic test to be modified in the range 1 to 23, or enter all
to specify all tests. Enter the dspdiagtests command to view the diagnostic tests
available and the associated test ID numbers.
Note
Only the enable|disable and -role option may be used with the all command
option. All other command options are for use with individual diagnostic
tests.
enable|disable
Enables or disables the diagnostic test on the current card.
-role
State of the card on which the specified diagnostic test is performed:
•
Note
Active state = 1
In Cisco MGX Releases 5 and 1.3, Online Diagnostic tests are supported only
on Active cards.
-startTOD
Scheduled start time of the diagnostic test using a 24 hour format (HH:MM). Enter
Now to execute the test immediately.
-period
Time between successive iterations of the diagnostic test in minutes.
-iterns
Number of times the diagnostic test should be repeated. When the value is specified
as -1, the test will continuously execute.
-param1
Parameter 1 for test. Enter the dspdiagtests <TestId> command to display the
configurable parameters for each online diagnostic test.
-param2
Parameter 2 for test. Enter the dspdiagtests <TestId> command to display the
configurable parameters for each online diagnostic test.
The following example modifies diagnostic test number 9 to be enabled in the active state, to start now,
to wait one minute between successive tests, and run only twice:
M8850_SF.1.28.MPSM8T1.ATM.a > cnfdiagtest 9 enable -role 1 -startTOD now -period 1 -iterns
2
M8850_SF.1.28.MPSM8T1.ATM.a >
Step 5
Enter the rundiagtest command as follows to run an online diagnostic test on the MPSM-8T1E1 card:
M8850_SF.1.28.MPSM8T1.ATM.a > rundiagtest <TestId> [param1] [param2]
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-61
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Online Diagnostics
Table 5-31 lists and describes the parameters for the rundiagtest command on the MPSM-8T1-ATM and
MPSM-8E1-ATM cards.
Table 5-31 Parameters for the rundiagtest Command
Parameter
Description
TestId
Test ID number of the diagnostic test to be executed in the range 1 to 23. Enter the
dspdiagtests command to view the diagnostic tests available and the associated test
ID numbers.
param1
Parameter 1 for tests. Enter the dspdiagtests <TestId> command to display the
configurable parameters for each online diagnostic test.
param2
Parameter 2 for tests. Enter the dspdiagtests <TestId> command to display the
configurable parameters for each online diagnostic test.
The following example runs online diagnostic test number 9 on the current MPSM-8T1-ATM card:
M8850_SF.1.28.MPSM8T1.ATM.a > rundiagtest 9 15
Host Memory Availability
PASSED
M8250_SJ.1.22.MPSM8T1.ATM.a >
Note
Step 6
To pause a currently running online diagnostic test, enter the pausediag command. To resume
an online diagnostic test that has been paused, enter the resumediag command.
Enter the dspdiagresults command as follows to view the results of an online diagnostic test:
M8850_SF.1.28.MPSM8T1.ATM.a > dspdiagresults
Online Diagnostic tests RUNNING.
ID
-1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
5-62
Name
-----------------------------Boot Checksum
Front card NVRAM Checksum
CPU Performance Monitor
NP Performance Monitor
SLFP Access
MPCTL Access
FRAMER Access
LDRAM Memory Availability
Host Memory Availability
Packet Memory Availability
Internal Memory Availability
Parameter Memory Availability
Host Memory Access
Packet Memory Access
Parameter Memory Access
MPCTL Error Monitor
NP Error Monitor
NP Health Check
MPCTL Loopback
PXM Data Path Loopback Test
NP TDM Loopback Test
SLFP TDM Loopback Test
Framer Loopback Test
Enable
------No
No
No
No
No
No
No
No
Yes
No
No
No
No
No
No
No
No
No
No
No
No
No
No
Attempts
-------0
0
0
0
0
0
0
0
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
FailCnt
------0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Result
------N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Pass
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Core Dumps
To clear the results from an online diagnostic test, enter the clrdiagresults command.
Step 7
Enter the cnfdiagtests to stop a test that is continuously running.
Table 5-30 lists and describes the parameters for the cnfdiagtest command on the MPSM-8T1-ATM and
MPSM-8E1-ATM cards
The following example stops online diagnostic test number 9:
M8850_SF.1.28.MPSM8T1.ATM.a > cnfdiagtest 9 disable
M8850_SF.1.28.MPSM8T1.ATM.a >
Managing MPSM Core Dumps
The following topics describe managing MPSM core dumps:
•
Overview of MPSM Core Dumps
•
Managing Core Dump Files
•
Aborting Core Dumps
•
Displaying Core Command Options
•
Displaying Core Dump Settings
•
Displaying the Core Dump Mask
•
Configuring Core Dump Settings
•
Hot-Dumping the Core
Overview of MPSM Core Dumps
The core command is used to manage core memory dumps on the MPSM-8T1E1 card. This command
is supported on PXM1, PXM1E, and PXM45 platforms.
Core dumps are used to debug hardware and software errors. Certain software errors such as memory
corruption, memory leaks, and resource leaks are difficult to catch during product testing. Other types
of errors may manifest only after prolonged usage in a production network. When such errors occur, it
is imperative to capture the software image in memory and the hardware configurations so that
debugging can be performed.
Core memory dumps on the MPSM card are supported on MPSM cards in redundancy groups and on
non-redundant MPSM cards.
When a software or hardware error condition requiring a reset occurs, the MPSM card will be reset after
writing the reset reason to the NVRAM. The boot code will then examine the reset reason. If the reset
reason is part of the core dump mask, a core dump to the PXM hard disk is performed by means of the
cell bus. This type of core dump is known as a cold-dump. The goal is to capture the dump without
affecting the tasks running on the PXM card or other service modules.
Note
You must set the PXM core red-policy command to enable to support cold-dumps from a non-redundant
MPSM card.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-63
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Core Dumps
The MPSM card also supports a hot-dump or run-time snapshot of the current Host CPU memory,
hardware configuration, and Winpath memory. Only one hot-dump of the core memory can take place at
a time on an MPSM card.
The PXM processor card will allow multiple cold-dumps and hot-dumps of the MPSM core memory
from different MPSM cards to take place at the same time on the switch.
Managing Core Dump Files
Cold-dump and hot-dump MPSM core dump files are saved in the C:/ directory on the PXM processor
card.
Cold-dump files are saved in the format core_slotNumber.zip. New cold-dump files from the same slot
will overwrite any existing cold-dump files from that same slot.
Hot-dump files are saved in the format filename.zip using a user specified filename. Do not use the same
filename format used by cold-dump files, otherwise the hot-dump file could be overwritten by a
subsequent cold-dump of the core.
Use FTP to transfer the core dump zip files to a work station. Core dump zip files must be sent to Cisco
TAC for debugging.
Aborting Core Dumps
Both hot-dumps and cold-dumps of the core memory on the MPSM card may be aborted by using the
PXM core abort-dump <slot> command.
Cold-dumps of the MPSM core memory will also be aborted if any of the following events occur:
•
The MPSM card is reset during a cold-dump in progress.
•
The PXM switchcc command is performed on the active PXM card during a cold-dump in progress
on the MPSM card.
•
The cold-dump takes longer than the core dump time-out period in effect on the PXM card.
Hot-dumps of the MPSM core memory will also be aborted if any of the following events occur:
Note
5-64
•
The MPSM card is reset during a hot-dump in progress.
•
The PXM switchcc command is performed on the active PXM card during a hot-dump in progress
on the MPSM card.
•
The PXM switchredcd command is performed during a hot-dump in progress on the active MPSM
card in a redundancy group.
•
On the PXM1 card, if there is less than 20MB of available space on the PXM1 hard drive.
•
The hot-dump takes longer than the core dump time-out period in effect on the PXM card.
To display and set the time-out period for cold and hot dumps of core memory, use the PXM core
time-out command to view the time-out period in effect on the PXM card and use the PXM core
time-out <timeInSecs> command to change the time-out setting on the PXM card.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Core Dumps
Displaying Core Command Options
Enter the core command with a question mark to list the optional parameters for the core command as
shown in the following example:
M8850_SF.1.28.MPSM8T1.ATM.a > core ?
core command syntax:
core
core
core
core
core
core
core
?
mask
mask default
mask <hex-mask>
enable
disable
(
(
(
(
(
(
(
show settings and saved images
print usage information
show autodump conditions
set default coredump mask
select autodump conditions
enable auto coredump
disable auto coredump
)
)
)
)
)
)
)
core hot-dump <filename.zip> ( take hot dump and save to file )
M8850_SF.1.28.MPSM8T1.ATM.a >
Displaying Core Dump Settings
Enter the core command without any arguments to display the current core dump settings on the MPSM
card. The following example shows the core dump settings on an MPSM card that has automatic core
dumping enabled and where the saved core images are located:
M8850_SF.1.28.MPSM8T1.ATM.a > core
Automatic core dumping is enabled for this slot.
Saved core images are on PXM's hard disk (C:/).
M8850_SF.1.28.MPSM8T1.ATM.a >
Displaying the Core Dump Mask
The core dump mask is the sum of the hexadecimal numbers associated with reset reasons that are
enabled to trigger a core dump. Most reasons for a card reset can be enabled to trigger a core dump. If
the reset reason in ON, the associated hexadecimal number is an element of the mask.
Enter the core mask command to display the current core dump mask and the error conditions for which
a core dump is enabled as shown in the following example:
M8850_SF.1.28.MPSM8T1.ATM.a > core mask
Automatic core dumping is enabled for this slot.
The current core mask is 0x273ae.
OFF
ON
ON
ON
OFF
ON
OFF
ON
ON
ON
OFF
OFF
00001
00002
00004
00008
00010
00020
00040
00080
00100
00200
00400
00800
not used (can't be turned ON)
DRAM Parity Error
WatchDog Timeout Reset
Resource Overflow
Clear All Configuration (can't be turned ON)
Missing Task
Reset because of PXM Low Voltage (can't be turned ON)
Reset By Event Log Task
Reset from Shell
Unknown
Reset from PXM (can't be turned ON)
Reset System (can't be turned ON)
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-65
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Core Dumps
ON
ON
ON
OFF
OFF
ON
01000
02000
04000
08000
10000
20000
Switch Core Card
Secondary Cache Error
Software Error Reset
S/W reset due to upgrade (can't be turned ON)
Restore All Configuration (can't be turned ON)
Device Driver Error
M8850_SF.1.28.MPSM8T1.ATM.a >
In this example, the mask is set to the default mask of 0x273ae. To change the mask, see “Changing the
Core Dump Mask”.
A reason that cannot trigger a core dump is indicated in the preceding example with can’t be turned ON.
A reset reason that can’t be turned ON removes debugging information from memory and therefore is
excluded from being part of the mask.
Configuring Core Dump Settings
The following topics describe the configuration of core dump settings:
•
Enabling Automatic Core Dumping
•
Disabling Automatic Core Dumping
•
Changing the Core Dump Mask
•
Restoring the Default Core Dump Mask
Enabling Automatic Core Dumping
Enter the core enable command to enable automatic core dumping as shown in the following example:
M8850_SF.1.28.MPSM8T1.ATM.a > core enable
Automatic core dumping is enabled for this slot.
M8850_SF.1.28.MPSM8T1.ATM.a >
Disabling Automatic Core Dumping
You may want to disable automatic core dumps for the MPSM card due to the time it takes to write core
memory to the PXM hard drive. For example:
Note
5-66
•
You may have isolated a problem and want to save the time required to write RAM contents to disk.
•
The traffic on the MPSM card may be of such high priority that you do not want to dump core
memory to disk.
•
The MPSM card is a non-redundant service module and the dump time may be a concern.
The PXM core red-policy [<enable|disable>] command is used to enable or disable core dumps on
non-redundant MPSM cards. Setting the core red-policy command to disable does not disable
hot-dumps of the core memory.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Core Dumps
Enter the core disable command to disable automatic core dumping as shown in the following example:
M8850_SF.1.28.MPSM8T1.ATM.a > core disable
Automatic core dumping is ** disabled ** for this slot.
M8850_SF.1.28.MPSM8T1.ATM.a >
The use of this command is similar to setting the mask to 0x0.
Changing the Core Dump Mask
Enter the core mask command as follows to change the core dump mask:
M8850_SF.1.28.MPSM8T1.ATM.a > core mask <hex-mask>
Replace the <hex-mask> parameter with the sum of all the hexadecimal values for the reset reasons that
you want to have in the new core dump mask.
In the following example, the default core dump mask of 0x273ae has been changed to 0x263ac:
M8850_SF.1.28.MPSM8T1.ATM.a > core mask 263ac
Automatic core dumping is enabled for this slot.
The current core mask is 0x263ac.
OFF
OFF
ON
ON
OFF
ON
OFF
ON
ON
ON
OFF
OFF
OFF
ON
ON
OFF
OFF
ON
00001
00002
00004
00008
00010
00020
00040
00080
00100
00200
00400
00800
01000
02000
04000
08000
10000
20000
not used (can't be turned ON)
DRAM Parity Error
WatchDog Timeout Reset
Resource Overflow
Clear All Configuration (can't be turned ON)
Missing Task
Reset because of PXM Low Voltage (can't be turned ON)
Reset By Event Log Task
Reset from Shell
Unknown
Reset from PXM (can't be turned ON)
Reset System (can't be turned ON)
Switch Core Card
Secondary Cache Error
Software Error Reset
S/W reset due to upgrade (can't be turned ON)
Restore All Configuration (can't be turned ON)
Device Driver Error
M8850_SF.1.28.MPSM8T1.ATM.a >
Note
When automatic core dumping is disabled, changing the mask will not have any effect until the core
dump feature is enabled using the core enable command.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-67
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Core Dumps
Restoring the Default Core Dump Mask
Enter the core mask default command to restore the default core dump mask as shown in the following
example:
M8850_SF.1.28.MPSM8T1.ATM.a > core mask default
Automatic core dumping is enabled for this slot.
The current core mask is 0x273ae.
OFF
ON
ON
ON
OFF
ON
OFF
ON
ON
ON
OFF
OFF
ON
ON
ON
OFF
OFF
ON
00001
00002
00004
00008
00010
00020
00040
00080
00100
00200
00400
00800
01000
02000
04000
08000
10000
20000
not used (can't be turned ON)
DRAM Parity Error
WatchDog Timeout Reset
Resource Overflow
Clear All Configuration (can't be turned ON)
Missing Task
Reset because of PXM Low Voltage (can't be turned ON)
Reset By Event Log Task
Reset from Shell
Unknown
Reset from PXM (can't be turned ON)
Reset System (can't be turned ON)
Switch Core Card
Secondary Cache Error
Software Error Reset
S/W reset due to upgrade (can't be turned ON)
Restore All Configuration (can't be turned ON)
Device Driver Error
M8850_SF.1.28.MPSM8T1.ATM.a >
If you add all of the reset reasons that are ON in the default mask, the sum is the hexadecimal number
0x273ae.
Hot-Dumping the Core
A hot-dump of the core directs the boot code to save memory but not to reset the card. Because the
memory-read during a hot-dump occurs while other tasks are running and modifying the memory, data
structures may not be accurate or consistent in a hot-dump. The hot-dump is the only memory dump
during which traffic continues to flow. Only one hot-dump of the core memory can take place at a time
on an MPSM card.
Enter the core hot-dump command as follows to initiate a hot-dump of the core:
M8850_SF.1.28.MPSM8T1.ATM.a > core hot-dump <filename.zip>
Replace the <filename.zip> parameter with a user specified filename with the .zip file extension. Specify
a filename not already in use with each hot-dump performed, otherwise the core hot-dump command
will fail.
Note
5-68
When specifying the filename for a hot-dump of the core, do not use the same filename format as used
by cold-dump files. This could cause the hot-dump file to be overwritten by a subsequent cold-dump of
the core.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Core Dumps
In the following example, a hot-dump of the core has been initiated and saved to a user specified file
with the name of dump28.zip:
M8850_SF.1.28.MPSM8T1.ATM.a > core hot-dump dump28.zip
Do you want to proceed (Yes/No)? y
Creating dump28.zip
..........................................................................................
..............
Creating WINPATHZIP
........................
Done.
M8850_SF.1.28.MPSM8T1.ATM.a >
Note
A hot-dump and cold-dump of the core memory on the MPSM card may be aborted by using the PXM
core abort-dump <slot> command.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
5-69
Chapter 5
Managing AUSM and MPSM Cards
Managing MPSM Core Dumps
5-70
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Part Number OL-4540-01 Rev. B0, August 18, 2004
Was this manual useful for you? yes no
Thank you for your participation!

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

Download PDF

advertising