Cisco Frame Relay Services (FRSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5
Chapter: Managing FRSM and MPSM Cards
Managing FRSM and MPSM Cards
This chapter provides procedures for managing FRSM-8T1, FRSM-8E1, FRSM-2T3E3, FRSM-2CT3, FRSM-HS2/B, MPSM-8T1-FRM, and MPSM-8E1-FRM 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.10, and the Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3 documentation. The provisioning of FRSM and MPSM cards is described in "Preparing FRSM and MPSM Lines and Ports for Communications," "Provisioning SPVCs (PXM1E/PXM45) on FRSM and MPSM Cards," and "Provisioning PVCs (PXM1) on FRSM and MPSM Cards."
This chapter describes the following FRSM and MPSM management procedures:
•Managing MPSM Feature Licenses
•Managing Bit Error Rate Testing (BERT)
•Managing MPSM Online Diagnostics
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.10, 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 FRSM and MPSM cards. For more information on these commands, see Chapter 6, "FRSM and MPSM Command Reference."
Managing Cards
Basic card initialization and configuration 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.10, and the Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3 documentation.
The following sections provide procedures for doing the following:
•Displaying General Card Information
•Displaying Software Version and Status Information
•Displaying FRSM Card Features
Note 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, "FRSM and MPSM Command Reference."
Displaying General Card Information
To display general information about a FRSM or MPSM card, use the dspcd command.
The following example shows general information about a FRSM-HS2/B card:
PXM1E_SJ.1.11.VHSHS2B.a > dspcd
ModuleSlotNumber: 11
FunctionModuleState: Active
FunctionModuleType: FRSM-HS2B-12IN1
FunctionModuleSerialNum: SAG05274SFR
FunctionModuleHWRev: ex
FunctionModuleFWRev: 020.000.001.046-A
FunctionModuleResetReason: Reset by PXM
LineModuleType: LM-12in1-8s
LineModuleState: Present
mibVersionNumber: 80
configChangeTypeBitMap: CardCnfChng, LineCnfChng
cardIntegratedAlarm: Major
cardMajorAlarmBitMap: Line Alarm
cardMinorAlarmBitMap: Channel failure
Front Card Info
pcb part no-(800 level): 800-17066-01
pcb part no-(73 level): 73-06948-01
pcb revision (800 level): 02
fab par no-(28 level): 28-05059-01
pcb serial no: SAG05274SFR
clei code: 0
manufacturing eng: 0x0
rma test history1: 0x0
rma test history2: 0x0
rma history: 0x0
platform features: 0x1
self test result: 0x0
Back Card Info
pcb part no-(800 level): 800-12345-01
pcb part no-(73 level): 73-01234-01
pcb revision (800 level): 02
fab par no-(28 level): 28-01234-01
pcb serial no: 123456
clei code: 00
manufacturing eng: 0x0
rma test history1: 0x0
rma test history2: 0x0
rma history: 0x0
PXM1E_SJ.1.11.VHSHS2B.a >
Note Note that the dspcd command displays information on card alarms.
The following example shows general information about an MPSM-8T1-FRM card:
M8850_SF.1.28.MPSM8T1.FRM.a > dspcd
ModuleSlotNumber: 28
FunctionModuleState: Active
FunctionModuleType: MPSM-8T1-FRM
FunctionModuleSerialNum: SAG07208RRA
FunctionModuleHWRev: 02
FunctionModuleFWRev: 030.000.001.077-A
FunctionModuleResetReason: Software Error
LineModuleType: ?
LineModuleState: Not Present
mibVersionNumber: 100
configChangeTypeBitMap: No changes
cardIntegratedAlarm: Minor
cardMinorAlarmBitMap: Channel failure
Front Card Info
PCB PART NO-(800 LEVEL): 800-22480-04
PCB PART_NO-(73 LEVEL): 73-8466-04
PCB REVISION (800 LEVEL):
PCB SERIAL NO: SAG07208RRA
CLEI CODE: 0
MANUFACTURING ENG: 0x0
RMA TEST HISTORY: 0x0
Back Card Info
PCB PART NO-(800 LEVEL): ??
PCB PART NO-(73 LEVEL): ??
PCB REVISION (800 LEVEL): ??
FAB PART NO-(28 LEVEL): ??
PCB SERIAL NO: ??
CLEI CODE: ??
MANUFACTURING ENG: ??
RMA HISTORY: ??
M8850_SF.1.28.MPSM8T1.FRM.a >
To determine whether a card is a FRSM-8T1, FRSM-8E1, FRSM-2T3E3, FRSM-2CT3, FRSM-HS2/B, MPSM-8T1-FRM, or MPSM-8E1-FRM card, use the dspcd command on the FRSM or MPSM card, or use the dspcds command on the PXM1, PXM1E, or PXM45 controller card.
Displaying Software Version and Status Information
To display information about the software running on a FRSM or MPSM card, use the chkflash and version commands.
The following example shows the status of the boot software on a FRSM card:
PXM1E_SJ.1.30.FRSM.a > chkflash
Program length = 300145
Calculated checksum = 147bc308 stored checksum = 147bc308
Flash checksum passed
The following example shows the status of the boot software on an MPSM-8T1-FRM card:
M8850_SF.1.28.MPSM8T1.FRM.a > chkflash
[chkflashfn]: Program length = 1415976
Calculated checksum = 0xad984cff stored checksum = 0xad984cff
Flash checksum passed
M8850_SF.1.28.MPSM8T1.FRM.a >
The following example displays the software versions running on a FRSM-HS2/B card:
PXM1E_SJ.1.11.VHSHS2B.a > version
***** Cisco System. FRSM-VHS Card *****
Firmware Version = 020.000.001.046-A
Backup Boot version = VHS_BT_1.0.04_19Jul0
VxWorks (for CISCO) version 5.3.1.
Kernel: WIND version 2.5.
Made on Mon Apr 29 02:03:54 PDT 2002.
Boot line:
PXM1E_SJ.1.11.VHSHS2B.a >
The following example displays the software versions running on an MPSM-8T1-FRM card
M8850_SF.1.28.MPSM8T1.FRM.a > version
***** Cisco System MPSM-8-T1E1 Card *****
Firmware Version = 030.000.001.077-A
Backup Boot Version = 030.000.001.077-A
VxWorks (for Broadcom BCM1125) version VxWorks5.4.2.
Kernel: WIND version 2.5.
Made on Dec 5 2003, 12:19:50.
Boot line:
M8850_SF.1.28.MPSM8T1.FRM.a >
Displaying FRSM Card Features
Use the dspfeature command to display the features supported on FRSM cards. Some FRSM cards are available in channelized and nonchannelized versions, and all FRSM cards support the rate control feature for standard ABR and ForeSight services. ForeSight is supported only on PXM1 platforms.
The FRSM-8T1 and FRSM-8E1 cards are available in channelized and nonchannelized versions. The nonchannelized versions are labeled FRSM-8T1 and FRSM-8E1 on the front of the cards, and the channelized versions are labeled FRSM-8T1-C and FRSM-8E1-C. However, the CLI prompt on the FRSM card and the output of the dspcds (supported on the PXM1, PXM1E, or PXM45 controller card) and dspcd (supported on the FRSM card) commands do not differentiate between the channelized and nonchannelized versions.
To determine if a FRSM-8T1 or FRSM-8E1 is a nonchannelized or channelized version using the CLI, enter the dspfeature command as shown in the following example:
PXM1E_SJ.1.30.FRSM.a > dspfeature
Channelized: On
Rate Control: On
This example also shows that rate control is supported on the FRSM card.
The FRSM-2CT3 card also supports channelized T1 lines. Normally, this feature is enabled. If the channelization feature is turned off on the FRSM-2CT3 card, the T1 lines support only fractional T1 ports.
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 allocated to the MPSM card.
The following sections provide procedures for doing the following:
•Displaying MPSM Feature Licenses
•Allocating MPSM Feature Licenses
•Managing MPSM Feature License Alarms
Note 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.10.
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.
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. A rate control feature license is required to provision standard ABR and ForeSight services. ForeSight is supported only on PXM1 platforms.
In the following example, a standard ABR connection has been provisioned on an MPSM-8T1-FRM card. The displiccd command shows that one rate control feature license was needed and that one rate control feature license has been allocated to the MPSM card from the PXM license pool in order to provision the connection successfully:
M8850_SF.1.28.MPSM8T1.FRM.a > dspliccd
Card License Alarm: None
Service Module Type: MPSM8T1E1
Service Module Serial Number: SAG07208RRA
Provisioning (addcon) Allowed: YES
=========================================================
Needed License Type Needed Licenses
------------------- ---------------
RateControl 1
=========================================================
Allocated License Type Allocated licenses
---------------------- ------------------
RateControl 1
=========================================================
Programmed License Type Programmed licenses
------------------------ -------------------
=========================================================
Programmed License Registered: NO
License registration node: NONE
License registration chassis: NONE
=========================================================
M8850_SF.1.28.MPSM8T1.FRM.a >
This example also shows that no feature licenses have been programmed into the NVRAM of the MPSM card.
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 into the switch license pool on the PXM processor card.
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:
M8250_SJ.1.22.MPSM8T1.FRM.a > dspliccd
Card License Alarm: None
Service Module Type: MPSM8T1E1
Service Module Serial Number: SAG07208RSX
Provisioning (addcon) Allowed: YES
=========================================================
Needed License Type Needed Licenses
------------------- ---------------
=========================================================
Allocated License Type Allocated licenses
---------------------- ------------------
=========================================================
Programmed License Type Programmed licenses
------------------------ -------------------
Rate-Control 1
=========================================================
Programmed License Registered: NO
License registration node: NONE
License registration chassis: NONE
=========================================================
M8250_SJ.1.22.MPSM8T1.FRM.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:
M8250_SJ.1.22.MPSM8T1.FRM.a > movelic
------------------------------------------------
Programmed License Type #Programmed
----------------------- -----------
Rate-Control 1
Do you want to proceed (Yes/No)? Yes
Card Licenses have been moved to license pool.
M8250_SJ.1.22.MPSM8T1.FRM.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.
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:
M8250_SJ.1.22.MPSM8T1.FRM.a > dspliccd
Card License Alarm: None
Service Module Type: MPSM8T1E1
Service Module Serial Number: SAG07208RSX
Provisioning (addcon) Allowed: YES
=========================================================
Needed License Type Needed Licenses
------------------- ---------------
=========================================================
Allocated License Type Allocated licenses
---------------------- ------------------
=========================================================
Programmed License Type Programmed licenses
------------------------ -------------------
Rate-Control 1
=========================================================
Programmed License Registered: YES
License registration node: M8250_SJ
License registration chassis: SCA05020GGR
=========================================================
M8250_SJ.1.22.MPSM8T1.FRM.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:
M8250_SJ.1.7.PXM.a > dsplics
Licensed License Licenses Licenses Licenses
Card Type Type Installed Allocated Available
----------------- ----------- --------- --------- ---------
MPSM-8T1E1 RateControl 1 0 1
M8250_SJ.1.7.PXM.a >
In this example, one Rate Control feature license has been successfully moved from the MPSM-8T1E1 card into the PXM license pool.
Allocating MPSM Feature Licenses
To allocate a feature license to an MPSM card, configure the card to use the licensed feature.
For example, to allocate a rate control feature license to an MPSM card using Frame Relay services, add a standard ABR connection using the addcon command. If the license pool on the PXM card has an available license for that feature and MPSM card type, that license is automatically allocated to the MPSM 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 allocated to the MPSM card, it is no longer available for use by other MPSM cards until it returns to the license pool.
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:
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. As shown in the following example on the PXM45 platform, the output of this command will indicate if the switch is in the node license alarm state:
M8850_SF.8.PXM.a > dspndalms
Node Alarm Summary
Alarm Type Critical Major Minor
---------- -------- ------- -------
Clock Alarms 0 0 0
Switching Alarms 0 0 0
Environment Alarms 0 0 0
Card Alarms 0 0 0
Node License Alarm 0 0 1
M8850_SF.8.PXM.a >
On PXM1 platforms, use the PXM dspcd command to troubleshoot the node license alarm. As shown in the following example, if the switch is in the node license alarm state, the cardIntegratedAlarm will be minor and the cardMinorAlarmBitMap will indicate License Alarm:
M8850_R1.1.7.PXM.a > dspcd
ModuleSlotNumber: 7
FunctionModuleState: Active
FunctionModuleType: PXM1-OC3
FunctionModuleSerialNum: SAG05304YHH
FunctionModuleHWRev: D0
FunctionModuleFWRev: 1.3.10.065
FunctionModuleResetReason: Restoreallcnf
LineModuleType: PXM-UI
LineModuleState: Present
SecondaryLineModuleType: SMFIR-4-155
SecondaryLineModuleState: Present
mibVersionNumber: 1.2.20
configChangeTypeBitMap: No changes
cardIntegratedAlarm: Minor
cardMajorAlarmBitMap: Clear
cardMinorAlarmBitMap: License Alarm
BkCardSerialNum: SBK042501CN
TrunkBkCardSerialNum: SBK05070188
FrontCardPCBNumber: 800-06229-04
TrunkBkCardPCBNumber: 800-05351-01
UIBkCardPCBNumber: 800-03688-01
SrmBackCardPCBNumber: Not Applicable
M8850_R1.1.7.PXM.a >
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.10.
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 PXM1E, PXM45, and PXM1 platforms, use the PXM dsplicalms command to troubleshoot slot license alarms. The output of this command will indicate which MPSM cards are in the slot license alarm state.
The following example shows the output of the PXM dsplicalms command on the PXM45 platform. In this example, the MPSM card in slot 28 is in slot license alarm:
M8850_SF.8.PXM.a > dsplicalms
M8850_SF System Rev: 05.00 Jul. 10, 2004 04:35:12 GMT
MGX8850 Node Alarm: MINOR
Slot Critical Major Minor || Slot Critical Major Minor
---- -------- ------- ------- || ---- -------- ------- -------
1 0 0 0 || 17 0 0 0
2 0 0 0 || 18 0 0 0
3 0 0 0 || 19 0 0 0
4 0 0 0 || 20 0 0 0
5 0 0 0 || 21 0 0 0
6 0 0 0 || 22 0 0 0
7 0 0 0 || 23 0 0 0
8 0 0 0 || 24 0 0 0
9 0 0 0 || 25 0 0 0
10 0 0 0 || 26 0 0 0
11 0 0 0 || 27 0 0 0
12 0 0 0 || 28 0 0 1
13 0 0 0 || 29 0 0 0
14 0 0 0 || 30 0 0 0
15 0 0 0 || 31 0 0 0
16 0 0 0 || 32 0 0 0
M8850_SF.8.PXM.a >
The following example shows the output of the PXM dsplicalms command on the PXM1 platform. In this example, the MPSM card in slot 22 is in slot license alarm:
M8850_R1.1.7.PXM.a > dsplicalms
Slot Critical Major Minor || Slot Critical Major Minor
---- -------- ------- ------- || ---- -------- ------- -------
1 0 0 0 || 17 0 0 0
2 0 0 0 || 18 0 0 0
3 0 0 0 || 19 0 0 0
4 0 0 0 || 20 0 0 0
5 0 0 0 || 21 0 0 0
6 0 0 0 || 22 0 0 1
7 0 0 0 || 23 0 0 0
8 0 0 0 || 24 0 0 0
9 0 0 0 || 25 0 0 0
10 0 0 0 || 26 0 0 0
11 0 0 0 || 27 0 0 0
12 0 0 0 || 28 0 0 0
13 0 0 0 || 29 0 0 0
14 0 0 0 || 30 0 0 0
15 0 0 0 || 31 0 0 0
16 0 0 0 || 32 0 0 0
M8850_R1.1.7.PXM.a >
On PXM45, PXM1E, and PXM1 platforms, the output of the PXM dspliccd <slot> command also shows if a card is in slot license alarm and displays how much time is left in the alarm grace period and if provisioning is allowed with the addcon command.
The following example shows the output of the PXM dspliccd <slot> command of an MPSM-8T1-FRM card in a PXM45 platform in the slot license alarm state:
M8850_SF.8.PXM.a > dspliccd 28
M8850_SF System Rev: 05.00 Jul. 10, 2004 05:02:24 GMT
MGX8850 Node Alarm: MINOR
Card License Alarm: Minor
Service Module Type: MPSM-8T1-FRM
Service Module Serial Number: SAG07208RRA
Provisioning Allowed: Yes
Grace-Period Remaining: 4 Days, 22 Hrs
=========================================================
Allocated License Type Quantity
-------------------- --------
RateControl 1
=========================================================
Programmed License Type Quantity
-------------------- --------
RateControl 1
=========================================================
Programmed License Registered: Yes
License Registeration Node: M8850_SF
License Registeration Chassis Serial No: SCA062300GF
M8850_SF.8.PXM.a >
The following example shows the output of the PXM dspliccd <slot> command of an MPSM-8T1-FRM card in a PXM1 platform in the slot license alarm state:
M8850_R1.1.7.PXM.a > dspliccd 22
Card License Alarm: Minor
Service Module Type: MPSM-8T1E1
Service Module Serial Number: SAD073103HH
Provisioning Allowed: Yes
Grace-Period Remaining: 4 Days, 23 Hrs
=========================================================
Allocated License Type Quantity
-------------------- --------
RateControl 1
=========================================================
Programmed License Type Quantity
-------------------- --------
=========================================================
Programmed Licenses Registered: N/A
License Registration Node: --
License Registration Chassis Serial No: --
M8850_R1.1.7.PXM.a >
On PXM45, PXM1E, and PXM1 platforms, the dspcd command will indicate if a card is in slot license alarm. If the card is in the slot license alarm state, the cardIntegratedAlarm will be minor and the cardMinorAlarmBitMap will indicate License Alarm.
The following example shows the output of the dspcd command of an MPSM-8T1-FRM card in a PXM45 platform in the slot license alarm state:
M8850_SF.1.28.MPSM8T1.FRM.a > dspcd
ModuleSlotNumber: 28
FunctionModuleState: Active
FunctionModuleType: MPSM-8T1-FRM
FunctionModuleSerialNum: SAG07208RRA
FunctionModuleHWRev: 02
FunctionModuleFWRev: 030.000.004.016-P2
FunctionModuleResetReason: Reset by PXM
LineModuleType: LM-RJ48-8T1
LineModuleState: Present
mibVersionNumber: 102
configChangeTypeBitMap: No changes
cardIntegratedAlarm: Minor
cardMinorAlarmBitMap: LICENSE ALARM
Front Card Info
PCB PART NO-(800 LEVEL): 800-22480-04
PCB PART_NO-(73 LEVEL): 73-8466-04
PCB REVISION (800 LEVEL):
PCB SERIAL NO: SAG07208RRA
CLEI CODE: 0
MANUFACTURING ENG: 0x0
RMA TEST HISTORY: 0x0
Back Card Info
PCB PART NO-(800 LEVEL): 000-00000-00
PCB PART NO-(73 LEVEL): 00-00000-00
PCB REVISION (800 LEVEL): AA
FAB PART NO-(28 LEVEL): 28-02011-01
PCB SERIAL NO: 648467
MANUFACTURING ENG: 0x1C
RMA HISTORY: 0x0
M8850_SF.1.28.MPSM8T1.FRM.a >
The following example shows the output of the dspcd command on an MPSM-8T1-FRM card in a PXM1 platform in the slot license alarm state:
M8850_R1.1.22.MPSM8T1.FRM.a > dspcd
ModuleSlotNumber: 22
FunctionModuleState: Active
FunctionModuleType: MPSM-8T1-FRM
FunctionModuleSerialNum: SAD073103HH
FunctionModuleHWRev: 02
FunctionModuleFWRev: 030.000.004.016-P2
FunctionModuleResetReason: Reset by PXM
LineModuleType: LM-RJ48-8T1
LineModuleState: Present
mibVersionNumber: 102
configChangeTypeBitMap: No changes
cardIntegratedAlarm: Minor
cardMinorAlarmBitMap: LICENSE ALARM
Front Card Info
PCB PART NO-(800 LEVEL): 800-24473-01
PCB PART_NO-(73 LEVEL): 73-9197-01
PCB REVISION (800 LEVEL):
PCB SERIAL NO: SAD073103HH
CLEI CODE: 0
MANUFACTURING ENG: 0x0
RMA TEST HISTORY: 0x0
Back Card Info
PCB PART NO-(800 LEVEL): 000-00000-00
PCB PART NO-(73 LEVEL): 00-00000-00
PCB REVISION (800 LEVEL): AC
FAB PART NO-(28 LEVEL): 28-02011-01
PCB SERIAL NO: B75816
MANUFACTURING ENG: 0x1C
RMA HISTORY: 0x0
M8850_R1.1.22.MPSM8T1.FRM.a >
On PXM45, PXM1E, and PXM1 platforms, the output of the dspliccd command also shows if a card is in slot license alarm.
The following example shows the output of the dspliccd command of an MPSM-8T1-FRM card in a PXM45 platform in the slot license alarm state:
M8850_SF.1.28.MPSM8T1.FRM.a > dspliccd
Card License Alarm: Minor
Service Module Type: MPSM8T1E1
Service Module Serial Number: SAG07208RRA
Provisioning (addcon) Allowed: YES
=========================================================
Needed License Type Needed Licenses
------------------- ---------------
RateControl 1
=========================================================
Allocated License Type Allocated licenses
---------------------- ------------------
RateControl 1
=========================================================
Programmed License Type Programmed licenses
------------------------ -------------------
RateControl 1
=========================================================
Programmed License Registered: YES
License registration node: M8850_SF
Type <CR> to continue, Q<CR> to stop:
License registration chassis: SCA062300GF
=========================================================
M8850_SF.1.28.MPSM8T1.FRM.a >
The following example shows the output of the dspliccd command of an MPSM-8T1-FRM card in a PXM1 platform in the slot license alarm state:
M8850_R1.1.22.MPSM8T1.FRM.a > dspliccd
Card License Alarm: Minor
Service Module Type: MPSM8T1E1
Service Module Serial Number: SAD073103HH
Provisioning (addcon) Allowed: YES
=========================================================
Needed License Type Needed Licenses
------------------- ---------------
RateControl 1
=========================================================
Allocated License Type Allocated licenses
---------------------- ------------------
RateControl 1
=========================================================
Programmed License Type Programmed licenses
------------------------ -------------------
=========================================================
Programmed License Registered: NO
License registration node: NONE
License registration chassis: NONE
=========================================================
M8850_R1.1.22.MPSM8T1.FRM.a >
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.10.
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.
Managing Lines
"Preparing FRSM and MPSM Lines and Ports for Communications," describes how to bring up (add) and modify FRSM and MPSM card lines. The following sections provide procedures for doing the following:
•Displaying the Configuration for a Single Line
Note 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, "FRSM and MPSM Command Reference."
Displaying a List of Lines
To display a list of lines on a FRSM or MPSM card, enter the dsplns command as follows:
PXM1E_SJ.1.25.FRSM.a > dsplns
Line Conn Type Status/Coding Length XmtClock Alarm Stats
Type Source Alarm
---- ----- ------------ ------ -------- ------------- -------- ----- -----
25.1 RJ-48 dsx1ESF Mod/dsx1B8ZS 0-131 ft LocalTim Yes No
25.2 RJ-48 dsx1ESF Ena/dsx1B8ZS 0-131 ft LocalTim No No
25.3 RJ-48 dsx1ESF Dis/dsx1B8ZS 0-131 ft LocalTim
25.4 RJ-48 dsx1ESF Dis/dsx1B8ZS 0-131 ft LocalTim
25.5 RJ-48 dsx1ESF Dis/dsx1B8ZS 0-131 ft LocalTim
25.6 RJ-48 dsx1ESF Dis/dsx1B8ZS 0-131 ft LocalTim
25.7 RJ-48 dsx1ESF Dis/dsx1B8ZS 0-131 ft LocalTim
25.8 RJ-48 dsx1ESF Ena/dsx1B8ZS 0-131 ft LocalTim Yes No
LineNumOfValidEntries: 8
The line number is found in the Line column in the format Slot.Line.
Displaying the Configuration for a Single Line
To display the configuration of a single line on a FRSM or MPSM card, enter the dspln command as follows:
PXM1E_SJ.1.30.FRSM.a > dspln <line>
Enter the line number with the command. You can view the available line numbers in the dsplns display.
The following example shows the information you can display with the dspln command on a FRSM card:
PXM1E_SJ.1.25.FRSM.a > dspln 2
LineNum: 2
LineConnectorType: RJ-48
LineType: dsx1ESF
LineEnable: Enabled
LineCoding: dsx1B8ZS
LineLength: 0-131 ft
LineXmtClockSource: LocalTiming
LineLoopbackCommand: NoLoop
LineSendCode: NoCode
LineUsedTimeslotsBitMap: 0x400
LineLoopbackCodeDetection: codeDetectDisabled
LineBertEnable: Disable
LineNumOfValidEntries: 8
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 Delete all connections that are associated with the line (dspcons and delcon commands).
Tip 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).
Tip 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.
Step 3 Enter the delln command as follows:
PXM1E_SJ.1.30.FRSM.a > delln <line>
Enter the line number with the command. You can view the available line numbers in the dsplns display.
The following example shows how to use the delln command:
PXM1E_SJ.1.11.VHSHS2B.a > delln 8
PXM1E_SJ.1.11.VHSHS2B.a >
Managing Line Alarms
FRSM and MPSM cards generate line alarms when errors occur as specified in ANSI T1.231. The significance of the different types of alarms appears in Table 5-2.
Note When the line is in alarm, the 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.
Use the commands in table Table 5-3 to display, clear, and configure FRSM and MPSM line alarms.
Managing Ports
"Preparing FRSM and MPSM Lines and Ports for Communications," describes how to add logical ports to the lines on FRSM and MPSM cards. The following sections provide procedures for doing the following:
•Displaying the Status of a Single Port
Displaying a List of Ports
To display a list of provisioned ports on the FRSM or MPSM card, enter the dspports command as follows:
PXM1E_SJ.1.30.FRSM.a > dspports
Port Ena/Speed EQServ SignalType T391 T392 N391 N392 N393 Type Alarm ELMI
Ratio
-------- --- ----- ------ ------------ ---- ---- ---- ---- ---- -------- ----- ----
30.3.3 Add/1536k 1 NoSignalling 10 15 6 3 4 frameRel No Off
30.4.4 Add/1536k 1 NoSignalling 10 15 6 3 4 frameRel No Off
Number of ports: 2
PortDs0UsedLine1: 0x00000000
PortDs0UsedLine2: 0x00000000
PortDs0UsedLine3: 0x00ffffff
PortDs0UsedLine4: 0x00ffffff
PortDs0UsedLine5: 0x00000000
PortDs0UsedLine6: 0x00000000
PortDs0UsedLine7: 0x00000000
PortDs0UsedLine8: 0x00000000
PortNumNextAvailable: 1
The port number is found in the Port column in the format Slot.Line.Port. To determine if a port is in alarm, check the status in the Alarm column. For more information on a single port, use the dspport command.
Displaying the Status of a Single Port
To display the configuration and status of a single provisioned port on the FRSM or MPSM card, enter the dspport command as follows:
PXM1E_SJ.1.30.FRSM.a > dspport <port>
Enter the port number with the command. You can view the provisioned port numbers in the dspports display. The following example shows the dspport display for port 3.
PXM1E_SJ.1.30.FRSM.a > dspport 3
SlotNum: 30
PortLineNum: 3
PortNum: 3
PortRowStatus: Add
PortDs0Speed: 64k
PortDs0ConfigBitMap(1stDS0): 0xffffff(1)
PortEqueueServiceRatio: 1
PortFlagsBetweenFrames: 1
PortSpeed: 1536kbps
SignallingProtocolType: NoSignalling
AsynchronousMsgs: UPD_UFS disabled
T391LineIntegrityTimer: 10
T392PollingVerificationTimer: 15
N391FullStatusPollingCounter: 6
N392ErrorThreshold: 3
N393MonitoredEventCount: 4
EnhancedLmi: Off
PortState: Active
PortSignallingState: No Signalling Failure
CLLMEnableStatus: Disable
CLLMxmtStatusTimer: 0
portType: frameRelay
PortIngrPercentUtil: 0
PortEgrPercentUtil: 0
PortOversubscribed: False
PortSvcStatus: Disable
PortSvcInUse: Not In-Use
PortSvcShareLcn: Card-based
PortSvcLcnLow: 0
PortSvcLcnHigh: 0
PortSvcDlciLow: 0
PortSvcDlciHigh: 0
PortDs0UsedLine1: 0x00000000
PortDs0UsedLine2: 0x00000000
PortDs0UsedLine3: 0x00ffffff
PortDs0UsedLine4: 0x00ffffff
PortDs0UsedLine5: 0x00000000
PortDs0UsedLine6: 0x00000000
PortDs0UsedLine7: 0x00000000
PortDs0UsedLine8: 0x00000000
PortNumNextAvailable: 1
Deleting Ports
To delete a Frame Relay port on a FRSM or MPSM card, 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:
PXM1E_SJ.1.30.FRSM.a > delport <port>
Replace the port parameter with the port number you want to delete. Port numbers are listed in the dspports command display.
Tip 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:
PXM1E_SJ.1.30.FRSM.a > delport 1
PXM1E_SJ.1.30.FRSM.a >
Monitoring Port Statistics
Use the commands in table Table 5-4 to display and clear FRSM and MPSM port statistics. These commands enable the user to monitor the traffic being transmitted to and received from attached end-user equipment.
The following example shows the output of the dspportcnt command on an MPSM card:
M8250_SJ.1.22.MPSM8T1.FRM.a > dspportcnt 1
PortNum: 1
Tx Rx
--------------- ---------------
Total Frames: 15548 16038
Total Bytes: 233220 269716
Frames FECN: 0 0
Frames BECN: 0 0
Frames Abort: 0 1
Buf Not Available: 0 0
KbpsAIR: 0 0
XmtFramesDiscXceedQDepth: 0
XmtBytesDiscXceedQDepth: 0
XmtFramesDuringLMIAlarm: 28
XmtByteDuringLMIAlarm: 420
XmtFramesUnderrun: 0
RcvFramesDE: 0
RcvFramesDiscCRCError: 14
RcvFramesDiscIllegalHeader: 199259
RcvFramesDiscAlignmentError: 228
RcvFramesDiscIllegalLen: 30
RcvFramesDiscXceedDEThresh: 0
RcvFramesDiscNoChan: 0
RcvFramesUnknownDLCI: 749736
RcvLastUnknownDLCI: 755
RcvFramesTaggedFECN: 0
RcvFramesTaggedBECN: 0
RcvFramesTaggedDE: 0
Status: 15548 0
StatusInquiry: 0 15548
AsynchUpdate: 0 0
RcvInvalidRequest: 761
RcvUNISeqMismatch: 2
RcvNNISeqMismatch: 0
UNISignallingTimeout: 10
NNISignallingTimeout: 0
FramesCLLM: 0 0
BytesCLLM: 0 0
CLLMFailures: 0
RcvFramesDiscard: 949268
XmtFramesDE: 0
Bytes DE: 0 0
XmtFramesDiscXceedDEThresh: 0
BytesDiscXceedDEThresh: 0 0
M8250_SJ.1.22.MPSM8T1.FRM.a >
Managing Resource Partitions
Resource partitions define how a switch's limited resources are distributed between two or more virtual 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 FRSM 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 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.
These 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, FRSM 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 Port Resource Partitions on PXM45 and PXM1E 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 tasks 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 FRSM and MPSM cards, you will not need to add a port resource partition. Port resource partitions are created automatically when you add a port to a line.
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.
Table 5-5 lists the FRSM 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, "FRSM and MPSM Command Reference."
|
|
|
|
|
|
|
|---|---|---|---|---|---|
addrscprtn |
X |
X |
X |
X |
X |
cnfrscprtn |
X1 |
X |
X |
X |
X |
delrscprtn |
X2 |
X |
X |
X |
X |
dsprscprtn |
X3 |
X |
X |
X |
X |
xcnfrscprtn |
X |
||||
cnfportrscprtn |
X4 |
||||
dspportrscprtn |
X5 |
||||
xcnfportrscprtn |
X |
X |
X |
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 FRSM or MPSM card, enter the dsprscprtn command as follows:
PXM1E_SJ.1.30.FRSM.a > dsprscprtn <port_num>
Replace the port parameter with the port number. For example:
PXM1E_SJ.1.30.FRSM.a > dsprscprtn 3
Port User Status NumOfLcnAvail DlciLow DlciHigh IngrBW EgrBW CtrlrId
---- ------ ------ -------------- ------- -------- ------ ----- -------
3 PNNI Add 1000 16 1023 100 100 2
PXM1E_SJ.1.30.FRSM.a >
Adding a Port Resource Partition on PXM45 and PXM1E Based Switches
To add a resource partition to a port on a FRSM or MPSM card, enter the addrscprtn command as follows:
PXM1E_SJ.1.30.FRSM.a > addrscprtn <port_num> <cntrlr_type> <pct_bw_ingr> <pct_bw_egr> <min_dlci> <max_dlci> <max_lcn> <cntrlr_id>
Table 5-6 lists and describes the parameters for the addrscprtn command on PXM45 and PXM1E platforms in Cisco MGX Release 5.
The following example adds a resource partition to a FRSM port after the default partition was deleted.
PXM1E_SJ.1.30.FRSM.a > addrscprtn 6 2 100 100 16 1023 1000 2
PXM1E_SJ.1.30.FRSM.a >
Modifying a Port Resource Partition on PXM45 and PXM1E Based Switches
To modify the resource partition of a port on a FRSM or MPSM card, enter the cnfrscprtn command as follows:
PXM1E_SJ.1.30.FRSM.a > cnfrscprtn <port_num> <cntrlr_type> <pct_bw_ingr> <pct_bw_egr> <min_dlci> <max_dlci> <max_lcn> <cntrlr_id>
Table 5-6 lists and describes the parameters for the cnfrscprtn command on PXM45 and PXM1E platforms in Cisco MGX Release 5.
The following example changes the default lower DLCI value to 20 and leaves all other resource partition values set to the default values:
PXM1E_SJ1.1.30.FRSM.a > cnfrscprtn 6 2 100 100 20 1023 1000 2
PXM1E_SJ1.1.30.FRSM.a >
Deleting a Port Resource Partition Configuration on PXM45 and PXM1E Based Switches
To delete the resource partition configuration of a port on a FRSM 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:
PXM1E_SJ.1.30.FRSM.a > delrscprtn <port_num> <cntrlr_type> <cntrlr_id>
Table 5-7 lists and describes the parameters for the delrscprtn command on PXM45 and PXM1E platforms in Cisco MGX Release 5.
The following example shows how to use the delrscprtn command:
PXM1E_SJ.1.30.FRSM.a > delrscprtn 6 2 2
PXM1E_SJ.1.30.FRSM.a >
To delete the resource partition configuration of a port on an MPSM card, use the xcnfrscprtn command.
Resource Partitions on PXM1 Based Switches
On the PXM1 platform, FRSM 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 even though the PNNI and TAG controllers are present in the card and port partition display commands. This resource 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
•Modifying a Card Resource Partition on PXM1 Based Switches
•Deleting a Card Resource Partition Configuration on PXM1 Based Switches
On FRSM 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 FRSM 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 FRSM and MPSM cards, except the FRSM-HS1/B card, 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. On the FRSM-HS1/B card, you can only view and make changes to the card resource partition.
Table 5-8 lists the FRSM 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, "FRSM and MPSM Command Reference."
|
|
|
|
|
|
|
|
|
|---|---|---|---|---|---|---|---|
cnfcdprtntype |
X1 |
X1 |
X1 |
X1 |
X1 |
X1 |
X1 |
dspcdprtntype |
X |
X |
X |
X |
X |
X |
X |
xcnfcdprtntype |
X1 |
X1 |
X1 |
X1 |
|||
addcdrscprtn |
X |
X |
X |
X |
X |
X |
X2 |
cnfcdrscprtn |
X3 |
X4 |
X4 |
X4 |
X4 |
X4 |
X |
delcdrscprtn |
X |
X |
X |
X |
X |
X |
X1 |
dspcdrscprtn |
X |
X |
X |
X |
X |
X |
X |
xcnfcdrscprtn |
X |
X |
X |
X |
1 This command is in the CLI, but it is not supported. 2 This command will modify the card resource partition if the status of the card resource partition is modified. 3 This command modifies all controllers. All controllers do not have to be present. Does not add controllers not present in the card resource partition. 4 This command modifies all controllers. All controllers do not have to be present. Adds any controller 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 a FRSM or MPSM card, enter the dspcdprtntype command as follows:
M8250_SJ.1.7.PXM.a > dspcdprtntype
cardLcnPartitionType : portControllerBased
M8250_SJ.1.7.PXM.a >
The default setting for a FRSM or MPSM card is a Port Controller Based card resource partition type. This default setting is not configurable.
Displaying a Card Resource Partition Configuration on PXM1 Based Switches
To display the card resource partition configuration of a FRSM or MPSM card, enter the dspcdrscprtn command as follows:
M8250_SJ.1.22.MPSM8T1.FRM.a > dspcdrscprtn
User NumOfLcnAvail
------ -------------
PAR 1000
PNNI 1000
TAG 1000
M8250_SJ.1.22.MPSM8T1.FRM.a >
Note in this example that although the PAR controller is the only controller supported on the FRSM 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 a FRSM or MPSM card, enter the addcdrscprtn command as follows:
M8250_SJ.1.22.MPSM8T1.FRM.a > addcdrscprtn <controller> <numOfLcnAvail>
Table 5-9 lists and describes the parameters for the addcdrscprtn command on PXM1 platforms in Cisco MGX Release 1.3.
The following example adds a card resource partition to an MPSM card after the default partition was deleted.
M8250_SJ.1.22.MPSM8T1.FRM.a > addcdrscprtn 1 900
M8250_SJ.1.22.MPSM8T1.FRM.a >
Modifying a Card Resource Partition on PXM1 Based Switches
To modify the card resource partition on a FRSM or MPSM card, enter the cnfcdrscprtn command as follows:
M8250_SJ.1.22.MPSM8T1.FRM.a > cnfcdrscprtn <#PARcon> <#PNNIcon> <#TAGcon>
Table 5-10 lists and describes the parameters for the cnfcdrscprtn command on PXM1 platforms in Cisco MGX Release 1.3.
The following example configures an MPSM card to support up to 500 connections per controller:
M8250_SJ.1.22.MPSM8T1.FRM.a > cnfcdrscprtn 500 500 500
M8250_SJ.1.22.MPSM8T1.FRM.a >
Deleting a Card Resource Partition Configuration on PXM1 Based Switches
To delete a card resource partition on a FRSM or MPSM card, enter the delcdrscprtn command as follows:
M8250_SJ.1.22.MPSM8T1.FRM.a > delcdrscprtn <controller>
Table 5-11 lists and describes the parameters for the delcdrscprtn command on PXM1 platforms in Cisco MGX Release 1.3.
|
|
|
|---|---|
controller |
Controller of the resource partition to delete: • • • |
The following example deletes a PNNI card resource partition from an MPSM card:
M8250_SJ.1.22.MPSM8T1.FRM.a > delcdrscprtn 2
M8250_SJ.1.22.MPSM8T1.FRM.a >
The delcdrscprtn command is not supported on the FRSM-HS1/B card.
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 FRSM 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.
Table 5-12 lists the FRSM 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, "FRSM and MPSM Command Reference."
|
|
|
|
|
|
|
|
|
|---|---|---|---|---|---|---|---|
addrscprtn |
X1 |
X1 |
X1 |
X1 |
X1 |
X1 |
X2 |
cnfrscprtn |
X3 |
X3 |
X4 |
X4 |
X4 |
X4 |
X3 |
delrscprtn |
X1 |
X1 |
X1 |
X1 |
X1 |
||
dsprscprtn |
X5 |
X5 |
X5 |
||||
xcnfrscprtn |
X6 |
||||||
cnfportrscprtn |
X7 |
X7 |
X8 |
X8 |
X8 |
X8 |
X7 |
delportrscprtn |
X1 |
X1 |
X1 |
X1 |
|||
dspportrscprtn |
X9 |
X9 |
X |
X |
X |
X |
X9 |
xcnfportrscprtn |
X6 |
X6 |
X6 |
X6 |
1 This command is in the CLI, but it is not supported. 2 This command will modify the port resource partition if the status of the port resource partition is modified. 3 This command is similar to the cnfportrscprtn command. The ingress and egress bandwidth are configured separately. 4 This command is the same as the cnfportrscprtn command. The ingress and egress bandwidth are configured together. 5 This command gives the same output as the dspportrscprtn command. 6 This command cannot add or delete, only modify. 7 This command is similar to the cnfrscprtn command. The ingress and egress bandwidth are configured together. 8 This command is the same as the cnfrscprtn command. The ingress and egress bandwidth are configured together. 9 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 a FRSM or MPSM card, enter the dspportrscprtn command as follows:
M8250_SJ.1.22.MPSM8T1.FRM.a > dspportrscprtn
Port User Status NumOfLcnAvail DlciLow DlciHigh IngrBW EgrBW
---- ------ ------ -------------- ------- -------- ------ -----
1 PAR Add 1000 0 1023 100 100
1 PNNI Add 1000 0 1023 100 100
1 TAG Add 1000 0 1023 100 100
M8250_SJ.1.22.MPSM8T1.FRM.a >
Modifying a Port Resource Partition on PXM1 Based Switches
To modify a resource partition of a port on a FRSM or MPSM card, enter the cnfportrscprtn command as follows:
M8250_SJ.1.22.MPSM8T1.FRM>.a > cnfportrscprtn <port_num> <controller-name> <pct_bw> <min_dlci> <max_dlci> <max_lcn>
Table 5-13 lists and describes the parameters for the cnfportrscprtn command on PXM1 platforms in Cisco MGX Release 1.3.
The following example modifies a port resource partition on an MPSM card:
M8250_SJ.1.22.MPSM8T1.FRM.a > cnfportrscprtn 1 par 100 16 1023 500
M8250_SJ.1.22.MPSM8T1.FRM.a >
Managing Connections
"Provisioning SPVCs (PXM1E/PXM45) on FRSM and MPSM Cards," and "Provisioning PVCs (PXM1) on FRSM and MPSM Cards," describe how to add connections to FRSM and MPSM cards. The following sections provide procedures for doing the following:
•Displaying a List of Connections
•Displaying the Status of a Single Connection
•Monitoring Connection Statistics
Displaying a List of Connections
Enter the dspcons command to display a list of the connections provisioned on the current FRSM or MPSM card.
The following example shows the connections provisioned on an MPSM-8T1-FRM card installed in a PXM45 platform:
M8850_SF.1.28.MPSM8T1.FRM.a > dspcons
LCN Port.DLCI VPI.VCI Class Type M/S CIR DE EgrQ Admin Alarm
---- --------- ------- ------ ----- --- -------- --- ---- ----- -----
0016 001.0016 28.0035 CBR NIW S 1536000 Dis Hi Up CTRLR-ABIT
0043 002.0017 28.0036 CBR NIW S 128000 Dis Hi Up CTRLR-ABIT
0044 003.0018 28.0037 CBR NIW S 256000 Dis Hi Up CTRLR-ABIT
0045 004.0019 28.0038 CBR NIW S 256000 Dis Hi Up CTRLR-ABIT
Number of channels: 4
ChanNumNextAvailable: 46
M8850_SF.1.28.MPSM8T1.FRM.a >
The following example shows the connections provisioned on an MPSM-8T1-FRM card installed in a PXM1 platform:
M8250_SJ.1.22.MPSM8T1.FRM.a > dspcons
Line ConnId Chan EQ ServType I/EQDepth I/EQDEThre I/EECNThre Fst/ DE Type LocRmtLpbk Alarm
--- ------------------- ---- -- -------- ----- ----- ----- ----- ----- ----- --- --- ----- --------- ------
1 M8250_SJ.22.1.0.16 18 Lo NotConf 65535/65535 32767/32767 6553/6553 Dis/Dis NIW Disabled Yes
3 M8250_SJ.22.2.0.17 19 Lo NotConf 65535/65535 32767/32767 6553/6553 Dis/Dis NIW Disabled Yes
ChanNumNextAvailable: 20
M8250_SJ.1.22.MPSM8T1.FRM.a >
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.
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.30.FRSM.a > dspcon <port.DLCI>
Enter the port number and DLCI number with the command. You can view the port and DLCI numbers in the dspcons display.
This example shows the configuration and status of a single connection provisioned on a MPSM-8T1-FRM card installed in a PXM45 platform:
M8850_SF.1.28.MPSM8T1.FRM.a > dspcon 1.16
--------------------------------------------------------
ChanNum: 16 RowStatus: Mod
AdmnState: Up ChanState: Failed
---------- ---------- ---------- ---------- ----------
PORT-ALARM CTRLR-ABIT E-AIS/RDI LMI-ABIT RAS FAIL
---------- ---------- ---------- ---------- ----------
NO YES NO NO NO
------------------------------------------------------
ChanNum: 16
ChanRowStatus: Mod
ConnAdminStatus: Up
ChanPortNum: 1
ChanDLCI: 16
EgressQSelect: Hi
ChanServType: CBR
IngressQDepth: 65535
IngressQDEThresh: 32767
IngressQECNThresh: 6553
EgressQDepth: 65535
EgressQDEThresh: 32767
EgressQECNThresh: 6553
DETaggingEnable: Disabled
CIR: 1536000
Bc: 5100
Be: 5100
IBS: 100
ICR: 0
MCR: 0
PCR: 0
RIF: 64
RDF: 16
Nrm: 64
Trm: 255 ms
TBE: 16777215 Cells
FRTT: 0 ms
ADTF: 500 ms
CDF: 16
ChanLocalRemoteLpbkState: Enabled
ChanTestType: TestOff
ChanTestState: NotInProgress
ChanRTDresult: 65535 ms
ChanType: NIW
ChanFECNmap: setEFCIzero
ChanDEtoCLPmap: mapCLP
ChanCLPtoDEmap: mapDE
ChanFrConnType: SPVC
ChanIngrPercentUtil: 100
ChanEgrPercentUtil: 100
ChanEgrSrvRate: 1536000
ChanOvrSubOvrRide: Do not apply CAC
ChanLocalVpi: 28
ChanLocalVci: 35
ChanLocalNSAP: NULL NSAP
ChanRemoteVpi: 0
ChanRemoteVci: 0
ChanRemoteNSAP: NULL NSAP
ChanMastership: Slave
ChanVpcFlag: Vcc
ChanConnServiceType: CBR1
ChanRoutingPriority: 8
ChanPreferredRouteId: 0
ChanDirectedRoute: No
ChanMaxCost: 2147483647
ChanRestrictTrunkType: No Restriction
ChanConnPCR: 5760
ChanConnSCR: 5760
ChanConnMCR: 10
ChanConnPercentUtil: 100
ChanConnRemotePCR: 5760 cps
ChanConnRemoteSCR: 10 cps
ChanConnRemoteMCR: 10 cps
ChanConnRemotePercentUtil:100
ChanServiceRateOverride: disabled
ChanServiceRate: 4000 cps
ChanZeroCirEir: 0 bps
ChanReRoute: False
RemoteConnMBS: 1024 cells
ChanNumNextAvailable: 46
M8850_SF.1.28.MPSM8T1.FRM.a >
This example shows the configuration and status of a connection provisioned on a MPSM-8T1-FRM card installed in a PXM1 platform:
M8250_SJ.1.22.MPSM8T1.FRM.a > dspcon 1.16
ChanNum: 18
ChanRowStatus: Add
ChanPortNum: 1
ChanDLCI: 16
EgressQSelect: Lo
ChanServType: NotConf
IngressQDepth: 65535
IngressQDEThresh: 32767
IngressQECNThresh: 6553
EgressQDepth: 65535
EgressQDEThresh: 32767
EgressQECNThresh: 6553
DETaggingEnable: Disabled
CIR: 1536000
Bc: 5100
Be: 5100
IBS: 100
ForeSightEnable: Disabled
QIR: 4000
MIR: 4000
PIR: 4000
ICR: 0
MCR: 0
PCR: 0
RIF: 64
RDF: 16
Nrm: 64
Trm: 255 ms
TBE: 16777215 Cells
FRTT: 0 ms
ADTF: 500 ms
CDF: 16
ChanLocalRemoteLpbkState: Disabled
ChanTestType: TestOff
ChanTestState: NotInProgress
ChanRTDresult: 65535 ms
ChanType: NIW
ChanFECNmap: setEFCIzero
ChanDEtoCLPmap: mapCLP
ChanCLPtoDEmap: mapDE
ChanFrConnType: PVC
ChanIngrPercentUtil: 100
ChanEgrPercentUtil: 100
ChanEgrSrvRate: 1536000
ChanOvrSubOvrRide: Disabled
ChanLocalVpi: 0
ChanLocalVci: 16
ChanLocalNSAP: 4d383235305f534a000000000000000016000100
ChanRemoteVpi: 0
ChanRemoteVci: 0
ChanRemoteNSAP: NULL NSAP
ChanMastership: Slave
ChanVpcFlag: Vcc
ChanConnServiceType: ATFR
ChanRoutingPriority: 1
ChanMaxCost: 2147483647
ChanRestrictTrunkType: No Restriction
ChanConnPCR: 4000 cps
ChanConnMCR: 4000 cps
ChanConnPercentUtil: 100
ChanServiceRateOverride: disabled
ChanServiceRate: 4000 cps
ChanZeroCirEir: 0 bps
ChanNumNextAvailable: 20
M8250_SJ.1.22.MPSM8T1.FRM.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.30.FRSM.a > delcon <port.DLCI>
Replace the port.DLCI parameter with the port number and DLCI number for the connection you want to delete. On PXM1E and PXM45 platforms, the port number and DLCI is found in the Port.DLCI column in the output of the dspcons and dspchans commands.
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 FRSM or MPSM card that hosts the feeder segment connection, enter the delcon command as shown below:
M8850_R1.1.18.FRSM.a > delcon <port.DLCI>
Replace the port.DLCI parameter with the port number and DLCI number for the connection you want to delete. On the PXM1 platform, the port number and DLCI is found in the ConnID column in the format Nodename.Slot.Port.0.DLCI 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.
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 a FRSM 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 a Frame Relay 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 FRSM or MPSM card that hosts one end of the local connection, enter the delcon command as shown below:
M8850_R1.1.18.FRSM.a > delcon <port.DLCI>
Replace the port.DLCI parameter with the port number and DLCI number for the connection you want to delete. On the PXM1 platform, the port number and DLCI is found in the ConnID column in the format Nodename.Slot.Port.0.DLCI 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 a FRSM 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 a Frame Relay service module, refer to the documentation for that card for instructions on deleting the connection.
Testing Connections
The following tasks describe how to test Frame Relay connections on FRSM and MPSM cards:
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 a Frame Relay connection on a FRSM or MPSM card with the tstcon command, enter the command as follows:
PXM1E_SJ.1.30.FRSM.a > tstcon <port.DLCI|Channel Number>
Replace the port.DLCI parameter with the port number and DLCI number for the connection you want to test. On PXM1E and PXM45 platforms, the port number and DLCI is found in the Port.DLCI column in the output of the dspcons and dspchans commands. On the PXM1 platform, the port number and DLCI is found in the ConnID column in the format Nodename.Slot.Port.0.DLCI in the output of the dspcons command, and in the DLCI column in the format Slot.Line.Port.DLCI in the output of the dspchans command.
Alternatively, you can replace the Channel Number parameter with the channel number for the connection you want to test. On PXM1E and PXM45 platforms, the channel number is found in the LCN column in the output of the dspcons, dspchans, and xdspchans commands. On the PXM1 platform, the channel number is found in the Chan column in the output of the dspcons, dspchans, and xdspchans commands.
The following is an example of a tstcon test:
PXM1E_SJ.1.30.FRSM.a > tstcon 1.32
TestCon in progress.
TestCon Passed.
PXM1E_SJ.1.30.FRSM.a >
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 a connection, and it returns a measurement of the round-trip delay across the connection. To test a Frame Relay connection on a FRSM or MPSM card with the tstdelay command, enter the command as follows:
PXM1E_SJ.1.30.FRSM.a > tstdelay <port.DLCI|Channel Number>
Replace the port.DLCI parameter with the port number and DLCI number for the connection you want to test. On PXM1E and PXM45 platforms, the port number and DLCI is found in the Port.DLCI column in the output of the dspcons and dspchans commands. On the PXM1 platform, the port number and DLCI is found in the ConnID column in the format Nodename.Slot.Port.0.DLCI in the output of the dspcons command, and in the DLCI column in the format Slot.Line.Port.DLCI in the output of the dspchans command.
Alternatively, you can replace the Channel Number parameter with the channel number for the connection you want to test. On PXM1E and PXM45 platforms, the channel number is found in the LCN column in the output of the dspcons, dspchans, and xdspchans commands. On the PXM1 platform, the channel number is found in the Chan column in the output of the dspcons, dspchans, and xdspchans commands.
The following is an example of a tstdelay test:
PXM1E_SF.1.11.FRSM.a > tstdelay 18
TestDelay in progress.
TestDelay Passed with 1 ms.
PXM1E_SF.1.11.FRSM.a >
The tstdelay command shares the same limitations as the tstcon command.
Testing with cnftrafficgen
The cnftrafficgen command sends a test pattern between two connection endpoints and checks to see if the pattern sent is returned correctly. Unlike the tstcon and tstdelay tests, on FRSM cards the number of frames sent for the test can be specified; on MPSM cards, the test is continuous until you stop it.
To start, stop, or abort a connection test on the MPSM-8T1-FRM, MPSM-8E1-FRM, FRSM-8T1, FRSM-8T1-C, FRSM-8E1, and FRSM-8E1-C cards with the cnftrafficgen command, enter the command as follows:
PXM1E_SJ.1.30.FRSM.a > cnftrafficgen <PortDLCI|pvc_num> <action> [num_frames] [pattern_type]
To start, stop, or abort a connection test on the FRSM-2T3E3, FRSM-2CT3, and FRSM-HS2/B cards with the cnftrafficgen command, enter the command as follows:
PXM1E_SJ.1.12.VHS2E3.a > cnftrafficgen <pvc_num> <action> [num_frames] [pattern_type]
Table 5-14 lists and describes the parameters for the cnftrafficgen command.
The following example starts a traffic generation test on a FRSM card on channel 16 using 50 frames and an all-ones pattern.
8830-SF.1.11.FRSM.a > cnftrafficgen 16 1 50 1
Wait for the prompt......
Starting Test
8830-SF.1.11.FRSM.a >
To display the test progress, enter the dsptrafficgen command as follows:
PXM1E_SJ.1.30.FRSM.a > dsptrafficgen [1]
The [1] option displays test statistics. The following example shows the test status without statistics:
8830-SF.1.11.FRSM.a > dsptrafficgen
Pvc Under Test : 16
8830-SF.1.11.FRSM.a >
The next example shows the test status with statistics.
8830-SF.1.11.FRSM.a > dsptrafficgen 1
Pvc Under Test : 16
Pattern type : 1( All 0's )
Total Test Frames To Send : 50
Total Test Frames Transmitted : 50
Total Test Frames Received : 0
8830-SF.1.11.FRSM.a >
Monitoring Connection Statistics
Use the commands in table Table 5-15 to display and clear FRSM and MPSM connection statistics. The channel count and statistics 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.
The following example shows the output of the dspchancnt command on a FRSM card:
M8850_SF.1.12.FRSM.a > dspchancnt 18
ChanNum: 18
ChanState: okay
ChanUpTime: 4066218
Tx Rx
--------------- ---------------
AbitState: Sending A=1 Off
ATMState: Not sending any state Not receiving any state
Total Frames: 1 2
Total Bytes: 32 64
Frames DE: 0 0
Bytes DE: 0 0
Frames Discarded: 0 0
Bytes Discarded: 0 0
FramesDiscXceedQDepth: 0 0
BytesDiscXceedQDepth: 0 0
FramesDiscXceedDEThresh: 0 0
Frames FECN: 0 0
Frames BECN: 0 0
FramesTagged FECN: 0 0
FramesTagged BECN: 0 0
KbpsAIR: 0 0
FramesTaggedDE: 0 0
BytesTaggedDE: 0 0
RcvFramesDiscShelfAlarm: 0
XmtFramesDiscPhyLayerFail: 0
XmtFramesDiscCRCError: 0
XmtFramesDiscReAssmFail: 0
XmtFramesDiscSrcAbort: 0
XmtFramesDuringLMIAlarm: 0
XmtBytesDuringLMIAlarm: 0
RcvFramesDiscUPC: 0
XmtFramesInvalidCPIs: 0
XmtFramesLengthViolations: 0
XmtFramesOversizedSDUs: 0
XmtFramesUnknownProtocols: 0
RcvFramesUnknownProtocols: 0
BytesDiscXceedDEThresh: 0 0
M8850_SF.1.12.FRSM.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 FRSM card:
M8850_SF.1.12.FRSM.a > dspsarcnt 1.100
SarShelfNum: 1
SarSlotNum: 12
SarChanNum: 18
Tx Rx
--------------- ---------------
Total Cells: 2 1
Total CellsCLP: 0 0
Total CellsAIS: 44 44
Total CellsFERF: 46 46
Total CellsEnd2EndLpBk: 0 0
Total CellsSegmentLpBk: 0 0
RcvCellsDiscOAM: 0
M8850_SF.1.12.FRSM.a >
Displaying Connection Alarms
To display a list of any connections in alarm use the dspcons command:
M8850_SF.1.28.MPSM8T1.FRM.a > dspcons
LCN Port.DLCI VPI.VCI Class Type M/S CIR DE EgrQ Admin Alarm
---- --------- ------- ------ ----- --- -------- --- ---- ----- -----
0043 002.0017 28.0036 CBR NIW S 128000 Dis Hi Up CTRLR-ABIT
0044 003.0018 28.0037 CBR NIW S 256000 Dis Hi Up CTRLR-ABIT
0045 004.0019 28.0038 CBR NIW S 256000 Dis Hi Up CTRLR-ABIT
Number of channels: 4
ChanNumNextAvailable: 46
M8850_SF.1.28.MPSM8T1.FRM.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:
M8850_SF.1.28.MPSM8T1.FRM.a > dspcon 7.70
--------------------------------------------------------
ChanNum: 18 RowStatus: Add
AdmnState: Up ChanState: Failed
---------- ---------- ---------- ---------- ----------
PORT-ALARM CTRLR-ABIT E-AIS/RDI LMI-ABIT RAS FAIL
---------- ---------- ---------- ---------- ----------
NO YES NO NO NO
------------------------------------------------------
ChanNum: 18
ChanRowStatus: Add
ConnAdminStatus: Up
ChanPortNum: 7
ChanDLCI: 70
EgressQSelect: Hi
ChanServType: CBR
IngressQDepth: 65535
IngressQDEThresh: 32767
IngressQECNThresh: 6553
EgressQDepth: 65535
EgressQDEThresh: 32767
EgressQECNThresh: 6553
DETaggingEnable: Disabled
CIR: 1536000
Bc: 5100
Be: 5100
IBS: 100
ICR: 0
MCR: 0
PCR: 0
RIF: 64
RDF: 16
Nrm: 64
Trm: 255 ms
TBE: 16777215 Cells
FRTT: 0 ms
ADTF: 500 ms
CDF: 16
ChanLocalRemoteLpbkState: Disabled
ChanTestType: TestOff
ChanTestState: NotInProgress
ChanRTDresult: 65535 ms
ChanType: NIW
ChanFECNmap: setEFCIzero
ChanDEtoCLPmap: mapCLP
ChanCLPtoDEmap: mapDE
ChanFrConnType: SPVC
ChanIngrPercentUtil: 100
ChanEgrPercentUtil: 100
ChanEgrSrvRate: 1536000
ChanOvrSubOvrRide: Do not apply CAC
ChanLocalVpi: 28
ChanLocalVci: 89
ChanLocalNSAP: 47009181000000000164444b6100000107e30700
ChanRemoteVpi: 0
ChanRemoteVci: 0
ChanRemoteNSAP: NULL NSAP
ChanMastership: Slave
ChanVpcFlag: Vcc
ChanConnServiceType: CBR1
ChanRoutingPriority: 8
ChanPreferredRouteId: 0
ChanDirectedRoute: No
ChanMaxCost: 2147483647
ChanRestrictTrunkType: No Restriction
ChanConnPCR: 5760
ChanConnSCR: 5760
ChanConnMCR: 10
ChanConnPercentUtil: 100
ChanConnRemotePCR: 5760 cps
ChanConnRemoteSCR: 10 cps
ChanConnRemoteMCR: 10 cps
ChanConnRemotePercentUtil:100
ChanServiceRateOverride: disabled
ChanServiceRate: 4000 cps
ChanZeroCirEir: 0 bps
ChanReRoute: False
RemoteConnMBS: 1024 cells
ChanNumNextAvailable: 19
M8850_SF.1.28.MPSM8T1.FRM.a >
Managing Loopbacks
Loopbacks are used as a troubleshooting tool to aid in resolving problems with physical lines and logical connections. These topics describe loopbacks on the FRSM and MPSM cards:
FRSM Card Loopbacks
The FRSM cards support line and channel loopbacks.
Line loopbacks can be enabled by:
•Manually placing the line in loopback mode using FRSM CLI commands.
•Enabling loopback code detection using FRSM CLI commands.
•Placing a line in loopback mode using the SRM by means of PXM BERT CLI commands. (Supported only on FRSM-8T1, FRSM-8T1-C, FRSM-8E1, FRSM-8E1-C, and FRSM-2CT3 cards.)
Channel loopbacks are enabled through use of CLI commands on the FRSM cards.
Figure 5-1, Figure 5-2, Figure 5-3, and Figure 5-4 show the details of where the various types of loopbacks occur within the architecture of the FRSM-8T1E1, FRSM-2CT3, FRSM-2T3E3, and FRSM-2HS/B cards, respectively.
Figure 5-1 FRSM-8T1E1 Line and Channel Loopbacks
Figure 5-2 FRSM-2CT3 Line and Channel Loopbacks
Figure 5-3 FRSM-2T3E3 Line and Channel Loopbacks
Figure 5-4 FRSM-HS2/B Line and Channel Loopbacks
Table 5-16 shows the loopback commands supported by each FRSM card. For more information on the use of these commands, see Chapter 6, "FRSM and MPSM Command Reference."
|
|
FRSM-8E1 |
|
|
|
|---|---|---|---|---|
addlnloop |
Local loopback |
Local loopback (T1) |
Local loopback |
|
dellnloop |
Delete local loopback |
Delete local or remote loopback (T1) |
Delete local loopback |
|
addrmtloop |
Remote loopback (T1) |
|||
cnflnloop |
Loopback code detection |
|||
addds3loop |
Local loopback (DS3) |
Local loopback |
||
delds3loop |
Delete local or remote loopback |
Delete local or remote loopback |
||
addds3rmtloop |
Remote loopback (DS3) |
Remote loopback |
||
xcnfln |
Local loopback using -lpb option1 ; Loopback code detection using -detect option |
Local and remote loopback using the -ds1/-lpb option; Loopback code detection using -ds1/-detect option Local, remote, and inband local loopback using the -ds3/-lpb option |
Local, remote, and inband local loopback using the -ds3/-lpb option |
Metallic and remote loopback using the -x21/-lpb option; Loopback code detection using -x21/-detect option |
addchanloop |
Channel local remote loopback2 |
Channel local remote loopback2 |
Channel local remote loopback2 |
Channel local remote loopback2 |
delchanloop |
Delete channel local remote loopback2 |
Delete channel local remote loopback2 |
Delete channel local remote loopback2 |
Delete channel local remote loopback2 |
xcnfchan |
Channel local remote loopback2 using -rmtlb option |
Channel local remote loopback2 using -rmtlb option |
Channel local remote loopback2 using -rmtlb option |
Channel local remote loopback2 using -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-FRM and MPSM-8E1-FRM cards support line and channel loopbacks.
Line loopbacks can be enabled by:
•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-5 shows the details of where the various types of loopbacks occur within the architecture of the MPSM-8T1E1 card.
Figure 5-5 MPSM-8T1E1 Line and Channel Loopbacks
Table 5-17 describes the loopback commands supported by the MPSM-8T1-FRM and MPSM-8E1-FRM cards. For more information on the use of these commands, see Chapter 6, "FRSM and MPSM Command Reference."
|
|
|
|---|---|
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 loopback1 . |
delchanloop |
Enter this command to remove the channel local remote loopback1 from a connection. |
xcnfchan |
Enter this command to enable or disable a channel local remote loopback1 using the -rmtlb option. |
1 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 |
Managing Bit Error Rate Testing (BERT)
The following topics discuss Bit Error Rate Testing (BERT) on FRSM and MPSM cards:
Bit Error Rate Testing (BERT) is utilized to determine the health of a full T1, E1, or DS3 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, a repetitive, or a 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.
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 (AIS, and so forth.) 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.
SRM Supported BERT
The following topics provide an overview of SRM supported Bit Error Rate Testing (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-FRM, MPSM-8E1-FRM, FRSM-8T1, FRSM-8T1-C, FRSM-8E1, FRSM-8E1-C, and FRSM-2CT3 cards.
There are two BERT buses in the Cisco MGX 8250 and Cisco MGX 8850 switches. 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 8230 and the Cisco MGX 8830 switches have 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 SRM supported Bit Error Rate Tests 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-18 shows a summary of the SRM supported BERT configuration options available on the MPSM-8T1-FRM, FRSM-8T1, FRSM-8T1-C, and FRSM-2CT3 cards.
|
|
|
|
|
|
|
|---|---|---|---|---|---|
Port with multiple timeslots (Nx56K, Nx64K) |
BERT pattern Loopback |
v541 |
|||
Port with one 64K timeslot |
BERT pattern DDS seek2 Loopback |
latch3 v541 |
all l |
Far end loopback Remote loopback |
|
Port |
Port with one 56K timeslot |
BERT pattern DDS seek2 |
nolatch4 |
2^9 2^11 |
|
Loopback |
latch3 v541 |
all |
|||
Line |
BERT pattern Loopback |
inband/ESF5 metallic6 |
all |
Far end loopback 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-19 shows a summary of the SRM supported BERT configuration options available on the MPSM-8E1-FRM, FRSM-8E1, and FRSM-8E1-C cards.
|
|
|
|
|
|
|---|---|---|---|---|
Port |
BERT pattern Loopback |
all |
Remote loopback |
|
Line |
BERT pattern Loopback |
metallic1 |
all |
Remote loopback Metallic loopback |
1 A local loopback within the service module which does not involve an external device. |
The available SRM supported T1 and E1 BERT patterns to choose from are shown in Table 5-20.
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-21.
MPSM-8T1E1 Onboard BERT
The following topics describe MPSM-8T1E1 onboard BERT:
•MPSM-8T1E1 Onboard BERT Features
•Managing a BERT Session on the MPSM-8T1E1
MPSM-8T1E1 Onboard BERT Features
MPSM Onboard BERT features and limitations common to the MPSM-8T1E1 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 supported 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-22 describes the onboard BERT commands supported by the MPSM-8T1-FRM and MPSM-8E1-FRM cards. For more information on the use of these commands, see Chapter 6, "FRSM and MPSM Command Reference."
Managing a BERT Session on the MPSM-8T1E1
To manage a Bit Error Rate Test 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.FRM.a > cnfbert <ifNumber> [-tp <TestPattern>] [-lpbk <loopback>] [-eir <errorInsertRate>]
Table 5-23 lists and describes the parameters for the cnfbert command on the MPSM-8T1-FRM and MPSM-8E1-FRM cards.
The following example configures a Bit Error Rate Test on an MPSM-8T1-FRM card on line 1 using the default parameters:
M8850_SF.1.28.MPSM8T1.FRM.a > cnfbert 1.0
Use startbert to start BERT
Use delbert followed by cnfbert to re-configure BERT parameters
M8850_SF.1.28.MPSM8T1.FRM.a >
Step 4 Enter the dspbert command as follows to view the BERT parameters configured with the cnfbert command:
M8850_SF.1.28.MPSM8T1.FRM.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 the previous step:
M8850_SF.1.28.MPSM8T1.FRM.a > dspbert 1.0
Interface Number : 1.0
Loopback Code : No Loopback
Pattern : TwoE20MinusOneQRSS
ErrorInsertRate : NoError
Start Date/Time : Not Started
Operational Status : Out Of Sync
M8850_SF.1.28.MPSM8T1.FRM.a >
Step 5 Enter the startbert command as follows to start a Bit Error Rate Test:
M8850_SF.1.28.MPSM8T1.FRM.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.FRM.a > startbert 1.0
M8850_SF.1.28.MPSM8T1.FRM.a >
Step 6 Enter the dspbert command to verify the start of the Bit Error Rate Test:
M8850_SF.1.28.MPSM8T1.FRM.a > dspbert 1.0
Interface Number : 1.0
Loopback Code : No Loopback
Pattern : TwoE20MinusOneQRSS
ErrorInsertRate : NoError
Start Date/Time : 03/17/2004 04:55:52
Operational Status : In Sync
M8850_SF.1.28.MPSM8T1.FRM.a >
In this example, an 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 Bit Error Rate Test in progress:
M8850_SF.1.28.MPSM8T1.FRM.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:
M8850_SF.1.28.MPSM8T1.FRM.a > dspbertstats 1.0
Interface Number : 1.0
Rx Bit Count : 33793765
Rx Bit Error Count : 83
Sync Loss Transition : 0
Pattern Loss Count (secs) : 0
M8850_SF.1.28.MPSM8T1.FRM.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, use 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.FRM.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.FRM.a > insbiterror 1.0
M8850_SF.1.28.MPSM8T1.FRM.a >
Step 9 Enter the stopbert command as follows to stop a BERT session:
M8850_SF.1.28.MPSM8T1.FRM.a > stopbert <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.FRM.a > stopbert 1.0
M8850_SF.1.28.MPSM8T1.FRM.a >
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.FRM.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:
M8850_SF.1.28.MPSM8T1.FRM.a > delbert 1.0
M8850_SF.1.28.MPSM8T1.FRM.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.
FRSM-2T3E3 Onboard BERT
The following topics describe FRSM-2T3E3 onboard BERT:
•FRSM-2T3E3 Onboard BERT Features
•Managing a BERT Session on the FRSM-2T3E3
FRSM-2T3E3 Onboard BERT Features
Onboard BERT is supported on the unchannelized FRSM-2T3E3 card through the use of CLI commands on the service module. Because the FRSM-2T3E3 contains its own BERT controller, BERT sessions can run on any number of these cards in the system. However, only one user at a time can run BERT on a card.
The FRSM-2T3E3 card supports only line BERT sessions. Port BERT sessions and loopbacks are not supported.
Table 5-24 shows the CLI commands used to configure and manage onboard BERT on the FRSM-2T3E3. For more information on the use of these commands, see Chapter 6, "FRSM and MPSM Command Reference."
Managing a BERT Session on the FRSM-2T3E3
To manage a Bit Error Rate Test using the FRSM-2T3E3 onboard BERT feature, perform the following steps:
Step 1 Log into the attached end-user equipment and place the line under test into loopback mode.
Step 2 Enter the acqdsx3bert command as follows to acquire control of the onboard BERT resources:
M8850_R1.1.14.VHS2T3.a > acqdsx3bert
M8850_R1.1.14.VHS2T3.a >
Step 3 Enter the cnfdsx3bert command as follows to specify a test pattern for a BERT session:
M8850_R1.1.14.VHS2T3.a > cnfdsx3bert <line_num> <test-pattern>
Table 5-25 lists and describes the parameters for the cnfdsx3bert command on the FRSM-2T3E3 card.
The following example configures a Bit Error Rate Test on a FRSM-2T3 card on line 1 using pattern number 25:
M8850_R1.1.14.VHS2T3.a > cnfdsx3bert 1 25
M8850_R1.1.14.VHS2T3.a >
Step 4 Enter the dspdsx3bert command as follows to view the BERT parameters configured with the cnfdsx3bert command:
M8850_R1.1.14.VHS2T3.a > dspdsx3bert
Bert Control: Configure dsx3Bert
Bert Resource Status State: In Use
Bert Owner: CLI
Bert Status: Inactive
Bert Test Medium: Line
Line Number : 1
Bert Mode : bertPatternTest
Bert Pattern : twentyBitQRSS
Start time (secs.) Not Configured Yet
Start Date Not Configured Yet
Bit uppercount: 0
Bit lowercount: 0
Bit Error uppercount 0
Bit Error lowercount 0
Error Insertion Rate: Error injection disabled
Error Insertion count: 0
M8850_R1.1.14.VHS2T3.a >
Step 5 If you are configuring a line BERT session on a PXM1 platform, make sure the DS3 line is enabled for BERT before starting the BERT session, otherwise the startdsx3bert command will fail. Enter the dspds3ln command to view the line BERT enable status.
To enable the line for BERT, use the xcnfln command as follows:
M8850_R1.1.14.VHS2T3.a > xcnfln -ds3 <lineNum> -e <dsx3LineEnable> -ds3ben <dsx3LineBERTEnable>
Replace the lineNum parameter with the number of the line to configure, the dsx3LineEnable parameter with option 3 (modify), and the dsx3LineBERTEnable parameter with option 2 (enable).
The following example enables BERT on line 1 of a FRSM-2T3E3 card:
M8850_R1.1.14.VHS2T3.a > xcnfln -ds3 1 -e 3 -ds3ben 2
M8850_R1.1.14.VHS2T3.a >
Step 6 Enter the startdsx3bert command as follows to start a Bit Error Rate Test:
M8850_R1.1.14.VHS2T3.a > startdsx3bert
M8850_R1.1.14.VHS2T3.a >
Step 7 Enter the dspdsx3bert command as follows to verify the start of the Bit Error Rate Test and to view statistics from a test in progress:
M8850_R1.1.14.VHS2T3.a > dspdsx3bert
Bert Control: Start dsx3Bert
Bert Resource Status State: In Use
Bert Owner: CLI
Bert Status: In Sync
Bert Test Medium: Line
Line Number : 1
Bert Mode : bertPatternTest
Bert Pattern : twentyBitQRSS
Start time (secs.) 01:20:26
Start Date 03/19/04
Bit uppercount: 41
Bit lowercount: 1720158207
Bit Error uppercount 0
Bit Error lowercount 0
Error Insertion Rate: Error injection disabled
Error Insertion count: 0
M8850_R1.1.14.VHS2T3.a >
In this example, a BERT Status of In Sync indicates that the test has been successfully started.
To clear the incrementing statistics during a BERT session, use the clrbertcntrs command to reset the statistics counters.
Step 8 Enter the moddsx3bert command as follows to insert bit errors into an active BERT session:
M8850_R1.1.14.VHS2T3.a > moddsx3bert <eir>
Table 5-26 lists and describes the parameters for the moddsx3bert command on the FRSM-2T3E3 card.
The following example inserts a 1 in 10^7 bit error into a BERT session in progress:
M8850_R1.1.14.VHS2T3.a > moddsx3bert 8
M8850_R1.1.14.VHS2T3.a >
Step 9 Enter the deldsx3bert command as follows to end the current BERT session, clear all BERT counters, and release control of all BERT resources:
M8850_R1.1.14.VHS2T3.a > deldsx3bert
M8850_R1.1.14.VHS2T3.a >
Step 10 If you have been running BERT on a PXM1 platform, disable the DS3 line for BERT with the xcnfln command, otherwise the DS3 line will remain in alarm after releasing control of all BERT resources with the deldsx3bert command.
The following example disables BERT on line 1 of a FRSM-2T3E3 card:
M8850_R1.1.14.VHS2T3.a > xcnfln -ds3 1 -e 3 -ds3ben 1
M8850_R1.1.14.VHS2T3.a >
Enter the dspds3ln command to verify that the BERT line status has been disabled.
Managing MPSM Online Diagnostics
The following topics describe MPSM-8T1E1 Online Diagnostics:
•MPSM-8T1E1 Online Diagnostics Features
•Configuring 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.
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.
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-27 shows the online diagnostics tests available on the MPSM-8T1E1 card.
Table 5-28 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, "FRSM and MPSM Command Reference."
Configuring Online Diagnostics on the MPSM-8T1E1
To configure 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:
M8250_SJ.1.22.MPSM8T1.FRM.a > dspdiagtests
ID Name Enable Role StartTOD Period Iteratns
-- ---------------------------- ------- ------ -------- ------ --------
1 Boot Checksum No Active NOW 1440 FOREVER
2 Front card NVRAM Checksum No Active NOW 1440 FOREVER
3 CPU Performance Monitor No Active NOW 5 FOREVER
4 NP Performance Monitor No Active NOW 5 FOREVER
5 SLFP Access No Active NOW 5 FOREVER
6 MPCTL Access No Active NOW 5 FOREVER
7 FRAMER Access No Active NOW 5 FOREVER
8 LDRAM Memory Availability No Active NOW 5 FOREVER
9 Host Memory Availability No Active NOW 30 FOREVER
10 Packet Memory Availability No Active NOW 30 FOREVER
11 Internal Memory Availability No Active NOW 30 FOREVER
12 Parameter Memory Availability No Active NOW 30 FOREVER
13 Host Memory Access No Active NOW 1 FOREVER
14 Packet Memory Access No Active NOW 5 FOREVER
15 Parameter Memory Access No Active NOW 5 FOREVER
16 MPCTL Error Monitor No Active NOW 5 FOREVER
17 NP Error Monitor No Active NOW 5 FOREVER
18 NP Health Check No Active NOW 5 FOREVER
19 MPCTL Loopback No Active NOW 1 FOREVER
20 PXM Data Path Loopback Test No Active NOW 1 FOREVER
21 NP TDM Loopback Test No Active NOW 30 FOREVER
22 SLFP TDM Loopback Test No Active NOW 30 FOREVER
23 Framer Loopback Test No Active NOW 30 FOREVER
Online Diagnostic tests RUNNING.
M8250_SJ.1.22.MPSM8T1.FRM.a >
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.FRM.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 10:
M8250_SJ.1.22.MPSM8T1.FRM.a > dspdiagtests 10
Test Name: Packet Memory Availability
Function: Monitors the available Packet memory.
Input Parameters:
Threshold for available memory: 0 - 100%
NP ID: 0 for MPSM-8T1E1, 0/1/2(Both NP) for MPSM-16T1E1
Alarm Raised on Failure: Major
Recovery Action: N.A
Role: Active
Enable: No
StartTOD: NOW
Period: 30
Iterations: FOREVER
Configured Parameters: 2, 0
M8250_SJ.1.22.MPSM8T1.FRM.a >
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.FRM.a > cnfdiagtest <TestId> [<enable|disable>] [-role <role>] [-startTOD <time>] [-period <period>] [-iterns <iterns>] [-param1 <param>] [-param2 <param>]
Table 5-29 lists and describes the parameters for the cnfdiagtest command on the MPSM-8T1-FRM and MPSM-8E1-FRM cards.
The following example modifies diagnostic test number 9 to enabled in the active state, to start now, to wait one minute between successive tests, and run only twice:
M8250_SJ.1.22.MPSM8T1.FRM.a > cnfdiagtest 9 enable -role 1 -startTOD now -period 1 -iterns 2
M8250_SJ.1.22.MPSM8T1.FRM.a >
Step 5 Enter the rundiagtest command as follows to run an online diagnostic test on the MPSM-8T1E1 card:
M8250_SJ.1.22.MPSM8T1.FRM.a > rundiagtest <TestId> [param1] [param2]
Table 5-30 lists and describes the parameters for the rundiagtest command on the MPSM-8T1-FRM and MPSM-8E1-FRM cards.
The following example runs online diagnostic test number 9 on the current MPSM-8T1-FRM card:
M8250_SJ.1.22.MPSM8T1.FRM.a > rundiagtest 9 15
Host Memory Availability PASSED
M8250_SJ.1.22.MPSM8T1.FRM.a >
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.
Step 6 Enter the dspdiagresults command as follows to view the results of an online diagnostic test:
M8250_SJ.1.22.MPSM8T1.FRM.a > dspdiagresults
Online Diagnostic tests RUNNING.
ID Name Enable Attempts FailCnt Result
-- ------------------------------ ------- -------- ------- -------
1 Boot Checksum No 1 0 Pass
2 Front card NVRAM Checksum No 0 0 N/A
3 CPU Performance Monitor No 0 0 N/A
4 NP Performance Monitor No 0 0 N/A
5 SLFP Access No 0 0 N/A
6 MPCTL Access No 0 0 N/A
7 FRAMER Access No 0 0 N/A
8 LDRAM Memory Availability No 0 0 N/A
9 Host Memory Availability Yes 16 0 Pass
10 Packet Memory Availability No 0 0 N/A
11 Internal Memory Availability No 0 0 N/A
12 Parameter Memory Availability No 0 0 N/A
13 Host Memory Access No 0 0 N/A
14 Packet Memory Access No 0 0 N/A
15 Parameter Memory Access No 0 0 N/A
16 MPCTL Error Monitor No 0 0 N/A
17 NP Error Monitor No 0 0 N/A
18 NP Health Check No 0 0 N/A
19 MPCTL Loopback No 0 0 N/A
20 PXM Data Path Loopback Test No 0 0 N/A
21 NP TDM Loopback Test No 0 0 N/A
22 SLFP TDM Loopback Test No 0 0 N/A
23 Framer Loopback Test No 0 0 N/A
M8250_SJ.1.22.MPSM8T1.FRM.a >
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-29 lists and describes the parameters for the cnfdiagtest command on the MPSM-8T1-FRM and MPSM-8E1-FRM cards
The following example stops online diagnostic test number 9:
M8250_SJ.1.22.MPSM8T1.FRM.a > cnfdiagtest 9 disable
M8250_SJ.1.22.MPSM8T1.FRM.a >
Managing MPSM Core Dumps
The following topics describe managing MPSM core dumps:
•Displaying Core Command Options
•Displaying Core Dump Settings
•Displaying the Core Dump Mask
•Configuring Core Dump Settings
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.
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:
•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.
Note 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.
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.FRM.a > core ?
core command syntax:
core ( show settings and saved images )
core ? ( print usage information )
core mask ( show autodump conditions )
core mask default ( set default coredump mask )
core mask <hex-mask> ( select autodump conditions )
core enable ( enable auto coredump )
core disable ( disable auto coredump )
core hot-dump <filename.zip> ( take hot dump and save to file )
M8850_SF.1.28.MPSM8T1.FRM.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.FRM.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.FRM.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.FRM.a > core mask
Automatic core dumping is enabled for this slot.
The current core mask is 0x273ae.
OFF 00001 not used (can't be turned ON)
ON 00002 DRAM Parity Error
ON 00004 WatchDog Timeout Reset
ON 00008 Resource Overflow
OFF 00010 Clear All Configuration (can't be turned ON)
ON 00020 Missing Task
OFF 00040 Reset because of PXM Low Voltage (can't be turned ON)
ON 00080 Reset By Event Log Task
ON 00100 Reset from Shell
ON 00200 Unknown
OFF 00400 Reset from PXM (can't be turned ON)
OFF 00800 Reset System (can't be turned ON)
ON 01000 Switch Core Card
ON 02000 Secondary Cache Error
ON 04000 Software Error Reset
OFF 08000 S/W reset due to upgrade (can't be turned ON)
OFF 10000 Restore All Configuration (can't be turned ON)
ON 20000 Device Driver Error
M8850_SF.1.28.MPSM8T1.FRM.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
•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.FRM.a > core enable
Automatic core dumping is enabled for this slot.
M8850_SF.1.28.MPSM8T1.FRM.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:
•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.
Note 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.
Enter the core disable command to disable automatic core dumping as shown in the following example:
M8850_SF.1.28.MPSM8T1.FRM.a > core disable
Automatic core dumping is ** disabled ** for this slot.
M8850_SF.1.28.MPSM8T1.FRM.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.FRM.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.FRM.a > core mask 263ac
Automatic core dumping is enabled for this slot.
The current core mask is 0x263ac.
OFF 00001 not used (can't be turned ON)
OFF 00002 DRAM Parity Error
ON 00004 WatchDog Timeout Reset
ON 00008 Resource Overflow
OFF 00010 Clear All Configuration (can't be turned ON)
ON 00020 Missing Task
OFF 00040 Reset because of PXM Low Voltage (can't be turned ON)
ON 00080 Reset By Event Log Task
ON 00100 Reset from Shell
ON 00200 Unknown
OFF 00400 Reset from PXM (can't be turned ON)
OFF 00800 Reset System (can't be turned ON)
OFF 01000 Switch Core Card
ON 02000 Secondary Cache Error
ON 04000 Software Error Reset
OFF 08000 S/W reset due to upgrade (can't be turned ON)
OFF 10000 Restore All Configuration (can't be turned ON)
ON 20000 Device Driver Error
M8850_SF.1.28.MPSM8T1.FRM.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.
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.FRM.a > core mask default
Automatic core dumping is enabled for this slot.
The current core mask is 0x273ae.
OFF 00001 not used (can't be turned ON)
ON 00002 DRAM Parity Error
ON 00004 WatchDog Timeout Reset
ON 00008 Resource Overflow
OFF 00010 Clear All Configuration (can't be turned ON)
ON 00020 Missing Task
OFF 00040 Reset because of PXM Low Voltage (can't be turned ON)
ON 00080 Reset By Event Log Task
ON 00100 Reset from Shell
ON 00200 Unknown
OFF 00400 Reset from PXM (can't be turned ON)
OFF 00800 Reset System (can't be turned ON)
ON 01000 Switch Core Card
ON 02000 Secondary Cache Error
ON 04000 Software Error Reset
OFF 08000 S/W reset due to upgrade (can't be turned ON)
OFF 10000 Restore All Configuration (can't be turned ON)
ON 20000 Device Driver Error
M8850_SF.1.28.MPSM8T1.FRM.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.FRM.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 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.
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.FRM.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.FRM.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.
Feedback