Cisco Circuit Emulation Services (CESM/MPSM-8-T1E1) Configuration Guide and Command Reference for MGX Switches, Release 5.2 - Managing CESM and MPSM Cards [Cisco MGX 8800 Series Switches]

Table Of Contents

Managing CESM and MPSM Cards

Managing CLI Sessions

Managing Cards

Displaying General Card Information

Displaying Software Version and Status Information

Displaying CESM Card Features

Managing MPSM Feature Licenses

Displaying MPSM Feature Licenses

Moving MPSM Feature Licenses

Allocating MPSM Feature Licenses

Managing MPSM Feature License Alarms

Node License Alarm

Slot License Alarms

Managing Lines

Displaying a List of Lines

Displaying the Configuration for a Single Line

Bringing Down a Line

Managing Line Alarms

Managing Ports

Displaying a List of Ports

Displaying the Status of a Single Port

Changing a Port Configuration

Deleting Ports

Managing Resource Partitions

Resource Partitions on PXM45 and PXM1E Based Switches

Managing Port Resource Partitions on PXM45 and PXM1E Based Switches

Resource Partitions on PXM1 Based Switches

Managing Card Resource Partitions on PXM1 Based Switches

Managing Port Resource Partitions on PXM1 Based Switches

Managing Connections

Displaying a List of Connections

Displaying the Status of a Single Connection

Deleting SPVC Connections

Deleting PVC Connections

Testing Connections

Testing with tstcon

Testing with tstdelay

Monitoring Connection Statistics

Displaying Connection Alarms

Managing Loopbacks

CESM Card Loopbacks

MPSM Card Loopbacks

Managing Bit Error Rate Testing (BERT)

SRM Supported BERT

Overview of SRM Supported BERT

BERT Configuration Parameters on the SRM

MPSM-8T1E1 Onboard BERT

MPSM-8T1E1 Onboard BERT Features

Managing a BERT Session on the MPSM-8T1E1

Managing MPSM Online Diagnostics

MPSM-8T1E1 Online Diagnostics Features

Configuring Online Diagnostics on the MPSM-8T1E1

Managing MPSM Core Dumps

Overview of MPSM Core Dumps

Managing Core Dump Files

Aborting Core Dumps

Displaying Core Command Options

Displaying Core Dump Settings

Displaying the Core Dump Mask

Configuring Core Dump Settings

Enabling Automatic Core Dumping

Disabling Automatic Core Dumping

Changing the Core Dump Mask

Restoring the Default Core Dump Mask

Hot-Dumping the Core

Managing Line Conditioning

Overview of Line Conditioning

Line Conditioning Feature Limitations

Configuring Line Conditioning on CESM and MPSM Cards

Managing CESM and MPSM Cards

This chapter provides procedures for managing CESM-8T1/B, CESM-8T1, CESM-8E1, MPSM-8T1-CES, and MPSM-8E1-CES cards after the initial card setup and provisioning.

Note Initial card setup is described in the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2, 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 CESM and MPSM cards is described in "Preparing CESM and MPSM Lines and Ports for Communications," "Provisioning SPVCs (PXM1E/PXM45) on CESM and MPSM Cards," and "Provisioning PVCs (PXM1) on CESM and MPSM Cards."

This chapter describes the following CESM and MPSM management procedures:

•Managing CLI Sessions

•Managing Cards

•Managing MPSM Feature Licenses

•Managing Lines

•Managing Ports

•Managing Resource Partitions

•Managing Connections

•Managing Loopbacks

•Managing Bit Error Rate Testing (BERT)

•Managing MPSM Online Diagnostics

•Managing MPSM Core Dumps

•Managing Line Conditioning

Managing CLI Sessions

Basic session initialization and management are described in the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2, 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 CESM and MPSM cards. For more information on these commands, see Chapter 6, "CESM and MPSM Command Reference."

Table 5-1 Session Management Commands

Command

Purpose

?
Help

Enter this command to display the available commands.

clear
clrscrn
cls

Enter this command to clear the session screen.

myid

Enter this command to display the user ID that was used to start the current session.

setcmdc

Enter this command to enable or disable the command completion feature, which automatically completes an incomplete command if the command portion entered uniquely identifies a supported command. This command is supported on the MPSM-8T1-CES and MPSM-8E1-CES only.

setpagemode

Enter this command to enable or disable the page feature, which breaks command displays into pages for easier viewing.

Managing Cards

Basic card initialization and configuration are described in the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2, 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 CESM 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, "CESM and MPSM Command Reference."

Displaying General Card Information

To display general information about a CESM or MPSM card use the dspcd command.

The following example shows general information about a CESM-8T1/B card:
M8850_SF.1.26.CESM.a > dspcd
  ModuleSlotNumber:          26
  FunctionModuleState:       Active
  FunctionModuleType:        CESM-8T1/B
  FunctionModuleSerialNum:   B24356
  FunctionModuleHWRev:       aa
  FunctionModuleFWRev:       021.000.001.193-A
  FunctionModuleResetReason: Reset by PXM
  LineModuleType:            LM-RJ48-8T1
  LineModuleState:           Present
  mibVersionNumber:          82
  configChangeTypeBitMap:    CardCnfChng, LineCnfChng
  cardIntegratedAlarm:       Clear
       Front Card Info 
  Hardware Revision      :   AA
  Card Type              :   787
  Serial Number          :   B24356
  Fab Number             :   28-4253-01         
       Back Card Info 
  Hardware Revision      :   AA
  Card Type              :   22
  Serial Number          :   648395
  Fab Number             :   28-2011-01
Note The dspcd command displays information on card alarms.

The following example shows general information about an MPSM-8T1-CES card:
M8850_SF.1.28.MPSM8T1.CES.a > dspcd
ModuleSlotNumber:          29
  FunctionModuleState:       Active
  FunctionModuleType:        MPSM-8E1-CES
  FunctionModuleSerialNum:   SAD090805TL
  FunctionModuleHWRev:       B0
  FunctionModuleFWRev:       030.001.205.033-A
  FunctionModuleResetReason: Reset by PXM
  LineModuleType:            LM-RJ48-8E1
  LineModuleState:           Present
  mibVersionNumber:          102
  configChangeTypeBitMap:    No changes
  cardIntegratedAlarm:       Clear
Front Card Info        
  PCB PART NO-(800 LEVEL):   800-24473-07 
  PCB PART_NO-(73 LEVEL):    73-9197-07 
  PCB REVISION (800 LEVEL):  B0 
  PCB SERIAL NO:             SAD090805TL 
  CLEI CODE:                 BA9A770EAA 
  MANUFACTURING ENG:         0x0        
  RMA TEST HISTORY:          0x0        
  Version ID (VID):          V01 
      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:             969462 
  MANUFACTURING ENG:         0x1C       
  RMA HISTORY:               0x0 
M8850_SF.1.28.MPSM8T1.CES.a > 
To determine whether a card is a CESM-8T1/B, CESM-8T1, CESM-8E1, MPSM-8T1-CES, or MPSM-8E1-CES card, use the dspcd command on the CESM 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 CESM or MPSM card, use the chkflash and version commands.

The following example shows the status of the boot software on a CESM card:
PXM1E_SJ.1.20.CESM.a > chkflash
Program length = 264592
Calculated checksum = a9f614f6 stored checksum = a9f614f6
Flash checksum passed
PXM1E_SJ.1.20.CESM.a >
The following example shows the status of the boot software on an MPSM card:
M8850_SF.1.28.MPSM8T1.CES.a > chkflash
[chkflashfn]: Program length = 1477096
Calculated checksum = 0x5a73afb6 stored checksum = 0x5a73afb6
Flash checksum passed
M8850_SF.1.28.MPSM8T1.CES.a >
The following example displays the software versions running on a CESM card:
PXM1E_SJ.1.20.CESM.a > version
***** Cisco Systems CESM-8T1E1 Card *****
    Firmware Version    = 021.000.001.193-A
    Backup Boot version = CE8_BT_1.0.02
    ASCFRSM Xilinx file = cbslave.h
VxWorks (for CISCO) version 5.3.1.
Kernel: WIND version 2.5.
Made on Feb 11 2003, 03:07:58.
Boot line:
Boot from PROM 
PXM1E_SJ.1.20.CESM.a >
The following example displays the software versions running on an MPSM card:
M8850_SF.1.28.MPSM8T1.CES.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.CES.a > 
Displaying CESM Card Features

The CESM-8T1/B, CESM-8T1, and CESM-8E1 cards are available in channelized (structured) and nonchannelized (unstructured) versions. To determine if a CESM-8T1/B, CESM-8T1, or CESM-8E1 is a nonchannelized or channelized version, enter the dspfeature command as shown in the following example:
PXM1E_SJ.1.20.CESM.a > dspfeature
  Channelized:  On
PXM1E_SJ.1.20.CESM.a >
The example above is for a channelized CESM-8T1/B card.

Managing MPSM Feature Licenses

Some features on the MPSM-8T1E1 card are enabled by the use of feature licenses. These feature licenses reside on the PXM processor in a license pool until needed by the MPSM card.

The following sections provide procedures for doing the following:

•Displaying MPSM Feature Licenses

•Moving 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 re-key feature licenses, refer to the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 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.

Because the MPSM-8T1E1 card configured for Circuit Emulation services does not require any feature licenses, the dspliccd command is used exclusively to view feature licenses that have been programmed into the NVRAM of the MPSM-8T1E1 card.

Note The rate control feature license is the only feature license available for the MPSM-8T1E1 card. This feature license is used by the MPSM-8T1E1 card when configured for Frame Relay services.

In the following example, the dspliccd command shows one rate control feature license programmed into the NVRAM on the MPSM-8T1-CES card:
M8850_SF.1.28.MPSM8T1.CES.a > dspliccd
Card License Alarm:              None
Service Module Type:             MPSM8T1E1
Service Module Serial Number:    SAG07208RRA
Provisioning (addcon) Allowed:   YES
=========================================================
Needed License Type               Needed Licenses
-------------------               ---------------
=========================================================
Allocated License Type            Allocated licenses
----------------------            ------------------
=========================================================
Programmed  License Type          Programmed licenses
------------------------          -------------------
RateControl                       1
=========================================================
Programmed License Registered:   NO
License registration node:       NONE
License registration chassis:    NONE
=========================================================
M8850_SF.1.28.MPSM8T1.CES.a >
If a feature license is moved to the PXM license pool, then the Programmed License Registered field in the output of the dspliccd command will state YES. Notice in this example that the rate control license programmed into the NVRAM on the MPSM-8T1-CES card has not been moved to the PXM license pool.

Moving MPSM Feature Licenses

If a feature license is purchased at the same time as the MPSM card, that license can be programmed into the NVRAM on the MPSM card. When a feature license is programmed on an MPSM card, the license is unavailable to that MPSM card and all other cards on the switch. To enable use of the programmed feature license, it must be moved from the MPSM card and installed in the switch license pool, which is a database on the PXM processor card.

The movelic command is used to move feature licenses programmed on MPSM cards to the switch license pool on the PXM processor card.

To move feature licenses, perform the following steps:

Step 1 Enter the dspliccd command to view the feature licenses that have been programmed on the MPSM card:
M8850_SF.1.28.MPSM8T1.CES.a > dspliccd
Card License Alarm:              None
Service Module Type:             MPSM8T1E1
Service Module Serial Number:    SAG07208RRA
Provisioning (addcon) Allowed:   YES
=========================================================
Needed License Type               Needed Licenses
-------------------               ---------------
=========================================================
Allocated License Type            Allocated licenses
----------------------            ------------------
=========================================================
Programmed  License Type          Programmed licenses
------------------------          -------------------
RateControl                       1
=========================================================
Programmed License Registered:   NO
License registration node:       NONE
License registration chassis:    NONE
=========================================================
M8850_SF.1.28.MPSM8T1.CES.a >
In this example, the output of the dspliccd command shows that one Rate Control feature license has been programmed into the NVRAM on the MPSM card.

Step 2 Enter the movelic command to move the feature licenses programmed on the MPSM card to the switch license pool on the PXM processor card:
M8850_SF.1.28.MPSM8T1.CES.a > movelic
------------------------------------------------
Programmed License Type          #Programmed
-----------------------          -----------
RateControl                       1
Do you want to proceed (Yes/No)? y
Card Licenses have been moved to license pool.
M8850_SF.1.28.MPSM8T1.CES.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:
M8850_SF.1.28.MPSM8T1.CES.a > dspliccd
Card License Alarm:              None
Service Module Type:             MPSM8T1E1
Service Module Serial Number:    SAG07208RRA
Provisioning (addcon) Allowed:   YES
=========================================================
Needed License Type               Needed Licenses
-------------------               ---------------
=========================================================
Allocated License Type            Allocated licenses
----------------------            ------------------
=========================================================
Programmed  License Type          Programmed licenses
------------------------          -------------------
RateControl                       1
=========================================================
Programmed License Registered:   YES
License registration node:       M8850_SF
License registration chassis:    SCA062300GF
=========================================================
M8850_SF.1.28.MPSM8T1.CES.a >
This example shows that the Rate Control feature license has been registered, the name of the switch where the license has been registered, and the chassis serial number of the switch where the feature license has been registered.

Step 4 Enter the dsplics command on the PXM processor card to view the MPSM feature licenses installed in the PXM license pool:
M8850_SF.7.PXM.a > dsplics
M8850_SF                         System Rev: 05.00   Jul. 02, 2004 01:51:22 GMT
MGX8850                                              Node Alarm: MINOR
Licensed           License      Licenses   Licenses   Licenses
Card Type          Type         Installed  Allocated  Available
-----------------  -----------  ---------  ---------  ---------
MPSM-8T1E1         RateControl  1          0          1
M8850_SF.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 assign a channelized feature license to an MPSM card, enter the addport command and use the channelization parameters to channelize the line. If the license pool on the PXM has an available license for that feature and MPSM card type, that license is automatically assigned to the card and the feature is successfully configured.

If you try to configure an MPSM card to use a feature for which no licenses are available, the configuration attempt will fail. Once a license is assigned to an MPSM card, it is no longer available for use by other MPSM cards until it returns to the license pool.

Note•Because the MPSM-8T1E1 card configured for Circuit Emulation services does not require any feature licenses, no feature licenses are allocated from the PXM license pool for any features or services configured on the MPSM-8T1-CES or MPSM-8E1-CES cards.

•The rate control feature license is the only feature license available for the MPSM-8T1E1 card. This feature license is used by the MPSM-8T1E1 card when configured for Frame Relay services.

Managing MPSM Feature License Alarms

MPSM feature license alarms can occur at the node level or the slot level of the switch. The following sections describe these alarms:

•Node License Alarm

•Slot License Alarms

Note Because the MPSM-8T1E1 card configured for Circuit Emulation services does not require any feature licenses, no feature licenses alarms will be raised on the MPSM-8T1-CES or MPSM-8E1-CES cards. The following sections are useful in alerting the user to MPSM feature license alarm conditions that may occur for MPSM-8T1E1 cards configured for Frame Relay services.

Node License Alarm

Node license alarms can happen under the following conditions:

•A switch configuration that was saved before licenses were added or transferred to and from the PXM license pool has been restored. Any mismatch between the actual license count and the restored license count generates a minor license alarm. To prevent this type of alarm, always save the switch configuration after you move, transfer, or add licenses.

•The switch configuration is restored on a different node, or the Cisco MGX chassis is replaced with another chassis. Because licenses are authorized for a specific backplane serial number, such conditions will cause a mismatch between the physical backplane serial number and serial number recorded in the database.

When a node license alarm is raised, all cards that are using feature licenses go into the slot license alarm state. If no licenses are in use by the cards, no slot license alarms will be raised.

On PXM45 and PXM1E platforms, use the PXM dspndalms command to troubleshoot the node license alarm. On PXM1 platforms, use the PXM dspcd command to troubleshoot the node license alarm.

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 8800/8900 Series Configuration Guide, Release 5.2 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 the PXM card, use the dsplicalms and dspliccd <slot> commands to troubleshoot slot license alarms. On the MPSM card, use the dspcd and dspliccd commands to troubleshoot slot license alarms.

For the procedures to rekey feature licenses, recover feature licenses, and add feature licenses to the PXM license pool see the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 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 CESM and MPSM Lines and Ports for Communications," describes how to bring up (add) and modify CESM and MPSM card lines. The following sections provide procedures for doing the following:

•Displaying a List of Lines

•Displaying the Configuration for a Single Line

•Bringing Down a Line

•Managing Line Alarms

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, "CESM and MPSM Command Reference."

Displaying a List of Lines

To display a list of lines on the CESM or MPSM card, enter the dsplns command as follows:
PXM1E_SJ.1.20.CESM.a > dsplns
  Line  Conn      Type     Status/Coding      Length     XmtClock Alarm Stats
        Type                                             Source         Alarm
  ----  ----- ------------ ------ -------- ------------- -------- ----- -----
  20.1  RJ-48 dsx1ESF         Ena/dsx1B8ZS 0-131 ft      LocalTim  No    No 
  20.2  RJ-48 dsx1ESF         Ena/dsx1B8ZS 0-131 ft      LocalTim  No    No 
  20.3  RJ-48 dsx1ESF         Ena/dsx1B8ZS 0-131 ft      LocalTim  No    No 
  20.4  RJ-48 dsx1ESF         Ena/dsx1B8ZS 0-131 ft      LocalTim  Yes   No 
  20.5  RJ-48 dsx1ESF         Dis/dsx1B8ZS 0-131 ft      LocalTim           
  20.6  RJ-48 dsx1ESF         Dis/dsx1B8ZS 0-131 ft      LocalTim           
  20.7  RJ-48 dsx1ESF         Dis/dsx1B8ZS 0-131 ft      LocalTim           
  20.8  RJ-48 dsx1ESF         Dis/dsx1B8ZS 0-131 ft      LocalTim           
  LineNumOfValidEntries: 8
PXM1E_SJ.1.20.CESM.a >
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 the CESM or MPSM card, enter the dspln command as follows:
PXM1E_SJ.1.20.CESM.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 the CESM card:
PXM1E_SJ.1.20.CESM.a > dspln 8
  LineNum:                   8
  LineConnectorType:         RJ-48
  LineEnable:                Modify
  LineType:                  dsx1ESF
  LineCoding:                dsx1B8ZS
  LineLength:                0-131 ft
  LineXmtClockSource:        LocalTiming
  LineLoopbackCommand:       LocalLineLoop
  LineSendCode:              NoCode
  LineUsedTimeslotsBitMap:   0x0
  LineLoopbackCodeDetection: codeDetectDisabled
  LineNumOfValidEntries: 8
PXM1E_SJ.1.20.CESM.a >
The following example shows the information you can display with the dspln command on the MPSM card:
M8250_SJ.1.6.MPSM8T1.CES.a > dspln 1
  LineNum:                   1
  LineConnectorType:         RJ-48
  LineType:                  dsx1ESF
  LineEnable:                Enabled
  LineCoding:                dsx1B8ZS
  LineLength:                0-131 ft
  LineXmtClockSource:        LocalTiming
  LineLoopbackCommand:       NoLoop
  LineSendCode:              NoCode
  LineUsedTimeslotsBitMap:   0x0
  LineLoopbackCodeDetection: codeDetectDisabled
  LineBERTEnable:            Disable
  LineNumOfValidEntries: 8
M8250_SJ.1.6.MPSM8T1.CES.a > 
Bringing Down a Line

When a line is not working properly, it generates a line alarm. If you want to suppress the alarm and you do not have time to correct the problem, you can bring down the line. Bringing down the line takes it out of service, so no alarms are generated.

Tip You can reduce the level of an alarm on a failed line from major to minor by using the addlnloop command to place the line in local loopback mode. This does not completely eliminate the alarm, but it does reduce the severity and allow you to preserve the configured resources for that line.

To bring down a line, use the following procedure.

Step 1 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.20.CESM.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.20.CESM.a > delln 8
PXM1E_SJ.1.20.CESM.a >
Managing Line Alarms

CESM and MPSM cards generate line alarms when problems occur. When a loss of signal (LOS) alarm is detected, a CESM or MPSM card notifies the connected CPE in the upstream direction after an integration period. The CESM or MPSM card then continues to emit cells at the nominal rate but sets the ATM cell payload with an appropriate data pattern as specified by the ATM Forum CES-IS V2.0 specification. Also, an OAM cell with RDI code goes to the far end to indicate out-of-service. The significance of the different types of alarms appears in Table 5-2.

Table 5-2 CESM and MPSM Line Errors and Alarms

Error

Alarm

Type

Transmit Downstream

Transmit Upstream

Comments

Receive LOS

Red

AIS

RAI

—

Receive LOF

Red

AIS

RAI

—

Receive AIS

Blue (AIS)

AIS (link)

FERF OAM cells

AIS—done over the T1/E1 link by sending the AIS data over the T1/E1 link

Receive RAI

Yellow

RAI

—

—

ATM Link Failure (RX)

Red (AIS)

AIS—OAM cells

None

Data cells According to ATM-Forum CES-IS V 2.0

Tip For more information on T1 and E1 signaling procedures and alarms, refer to the ATM Forum Circuit Emulation Service Interoperability Specification (AF-SAA-0032.00) or the Bellcore TR-NWT-000170.

Use the commands in table Table 5-3 to display, clear, and configure CESM and MPSM line alarms.

Table 5-3 CESM and MPSM Line Alarm Commands

Command

Purpose

dspalm

Enter this command to display the active alarms associated with a specific line.

dspalms

Enter this command to display a summary of the active line alarms.

dspalmcnf

Enter this command to display the alarm configuration and thresholds for a specific line.

dspalmcnt

Enter this command to display the alarm counters for a specific line.

clralm

Enter this command to clear any active alarms on a specific line (Alarms will not clear if the cause for the alarm is still present).

clralms

Enter this command to clear active alarms on all lines (Alarms will not clear if the cause for the alarm is still present).

clralmcnt

Enter this command to clear the alarm counters for a specific line.

clralmcnts

Enter this command to clear the alarm counters for all lines.

xcnfalm

Enter this command to modify alarm counters, thresholds, and statistics for a specific line.

xcnfalmcnt

Enter this command to modify threshold values of statistical alarm counters for a specific line.

Table 5-4 lists other CESM and MPSM card alarms and shows how these alarms affect the transmit and receive channels for a line.

Table 5-4 CESM and MPSM Card Alarms

Type of

Alarm

Channel RCV ATM State

Channel XMT ATM State

Action

Port Alarm

—

Sending AIS OAM

Generate OAM-AIS towards the network

Abit (from PXM)

Normal

Normal

—

Underrun

Normal

Normal

Conditioning towards line

Overrun

Normal

Normal

Conditioning towards line

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.

Managing Ports

"Preparing CESM and MPSM Lines and Ports for Communications," describes how to add logical ports to the lines on CESM and MPSM cards. The following sections provide procedures for doing the following:

•Displaying a List of Ports

•Displaying the Status of a Single Port

•Changing a Port Configuration

•Deleting Ports

Displaying a List of Ports

To display a list of ports provisioned on the CESM or MPSM card, enter the dspports command as follows:
PXM1E_SJ.1.4.CESM.a > dspports
  Port     Ena/Speed   Type
  ------   --- ------ --------
  4.1.1    Add/1536k structur
  4.2.2    Add/1536k structur
  4.3.3    Add/1536k structur
  4.4.4    Add/1536k structur
  Number of ports:              4
  PortDs0UsedLine1:             0x00ffffff
  PortDs0UsedLine2:             0x00ffffff
  PortDs0UsedLine3:             0x00ffffff
  PortDs0UsedLine4:             0x00ffffff
  PortDs0UsedLine5:             0x00000000
  PortDs0UsedLine6:             0x00000000
  PortDs0UsedLine7:             0x00000000
  PortDs0UsedLine8:             0x00000000
  PortNumNextAvailable:         5
PXM1E_SJ.1.4.CESM.a >
The port number is found in the Port column in the format Slot.Line.Port. 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 CESM or MPSM card, enter the dspport command as follows:
PXM1E_SJ.1.4.CESM.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 report for a CESM-8T1/B card.
PXM1E_SJ.1.4.CESM.a > dspport 1
  SlotNum:                      4
  PortLineNum:                  1
  PortNum:                      1
  PortRowStatus:                Add
  PortNumOfSlots:               24
  PortDs0ConfigBitMap(1stDS0):  0xffffff(1)
  PortSpeed:                    1536kbps
  PortType:                     structured
  PortState:                    Active
PXM1E_SJ.1.4.CESM.a >
Changing a Port Configuration

To modify a circuit emulation port configuration that has been added using the addport command on a CESM or MPSM card, you must first delete the port using the delport command. Add the port again with the new port configuration parameters using the addport command.

Tip If there are any SPVC or PVC connections provisioned on the port, these must be deleted before you can change the port configuration.

Deleting Ports

To delete a Circuit Emulation port on a CESM 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.20.CESM.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.20.CESM.a > delport 1
PXM1E_SJ.1.20.CESM.a >
To delete multiple CESM or MPSM ports, enter the delports command as described in Chapter 6, "CESM and MPSM Command Reference."

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 CESM 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, CESM and MPSM resource partitions are managed only on the port level. Cisco MGX Release 5.1 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 CESM and MPSM cards installed in PXM45 and PXM1E based 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 CESM 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.

On the MPSM card, you can view the port resource partition configuration, make changes to it, or delete it. If you delete a port resource partition, you will have to add a new partition for that port before you can assign connections to the port. On the CESM card, you can view the port resource partition configuration and delete it, but you cannot modify it.

Table 5-5 lists the CESM and MPSM port resource partition commands supported on PXM45 and PXM1E platforms in Cisco MGX Release 5.1. For more information on these commands, see Chapter 6, "CESM and MPSM Command Reference."

Table 5-5 CESM/MPSM Port Resource Partitioning Commands (PXM45/PXM1E Platform)

Command

MPSM-8T1-CES

MPSM-8E1-CES

CESM-8T1/B
CESM-8T1
CESM-8E1

addrscprtn

X

X

cnfrscprtn

X

delrscprtn

X

X

dsprscprtn

X¹

X

xcnfrscprtn

X

cnfportrscprtn

X²

dspportrscprtn

X³

¹This command gives the same output as the dspportrscprtn command.

²This command does nothing except change the partition status to modified. There are no options supported.

³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 CESM or MPSM card, enter the dsprscprtn command as follows:
PXM1E_SJ.1.4.CESM.a > dsprscprtn <port>
Replace the port parameter with the port number. For example:
PXM1E_SJ.1.4.CESM.a > dsprscprtn 1
  Port  User  Status  NumOfLcnAvail   LcnLow   LcnHigh   IngrBW  EgrBW CtrlrId
  ---- ------ ------ --------------  -------- ---------  ------  ----- --------
   1    PNNI   Add          1           1         1        100     100    2  
PXM1E_SJ.1.4.CESM.a >
Adding a Port Resource Partition on PXM45 and PXM1E Based Switches

To add a resource partition to a port on a CESM or MPSM card, enter the addrscprtn command as follows:
PXM1E_SJ.1.4.CESM.a > addrscprtn <port_num> <cntrlr_type> <cntrlr_id>
Table 5-6 lists and describes the parameters for the addrscprtn command on PXM45 and PXM1E platforms in Cisco MGX Release 5.1.

Table 5-6 Parameters for the addrscprtn/delrscprtn Commands

Parameter

Description

port_num

Port number associated with the resource partition to be added or deleted. You must add a port to a line before you can define a partition for a port. Use the dspports command to view the available ports. The port number is found in the Port column in the format Slot.Line.Port.

cntrlr_type

Controller for this partition. Enter 2 as the PNNI controller is the only controller type supported in MGX Release 5.1.

•1 = PAR (PVC)

•2 = PNNI (SPVC)

•3 = TAG (MPLS)

cntrlr_id

If adding a resource partition, enter a number that will be associated with the controller used by this partition. Range is 1 to 255.

If deleting a resource partition, enter the controller ID assigned to the partition you are deleting. To display the controller ID, use the dsprscprtn command. Valid range is from 1 to 255.

The following example adds a resource partition to a CESM port after the default partition was deleted:
PXM1E_SJ.1.4.CESM.a > addrscprtn 1 2 2
PXM1E_SJ.1.4.CESM.a >
Modifying a Port Resource Partition on PXM45 and PXM1E Based Switches

To modify the resource partition of a port on an MPSM card, enter the cnfrscprtn command as follows:
M8850_SF.1.28.MPSM8T1.CES.a > cnfrscprtn <port_num> <cntrlr> <pct_bw_ingr> <pct_bw_egr> 
<low_lcn> <high_lcn> <numOfLcnAvail>
Table 5-7 lists and describes the parameters for the cnfrscprtn command on PXM45 and PXM1E platforms in Cisco MGX Release 5.1.

Table 5-7 Parameters for the cnfrscprtn Command

Parameter

Description

port_num

Port number associated with the resource partition to be modified. You must add a port to a line before you can modify the resource partition on a port. Use the dspports command to view the available ports. The port number is found in the Port column in the format Slot.Line.Port.

cntrlr

Controller for this partition. Enter 2 as the PNNI controller is the only controller type supported in MGX Release 5.1.

•1 = PAR (PVC)

•2 = PNNI (SPVC)

•3 = TAG (MPLS)

pct_bw_ingr

Ingress bandwidth percentage. Enter the percentage of the line bandwidth to be used by this controller for ingress communications. Range is 0 to 100 percent.

pct_bw_egr

Egress bandwidth percentage. Enter the percentage of the line bandwidth to be used by this controller for egress communications. Range is 0 to 100 percent.

low_lcn

Low LCN number available in this port resource partition. Range is 1 to 1000.

high_lcn

High LCN number available in this port resource partition. Range is 1 to 1000.

numOfLcnAvail

Maximum LCNs (connections) available in this port resource partition. Range by card type:

•CESM-8T1/B, CESM-8T1, MPSM-8T1-CES: 1-192

•CESM-8E1, MPSM-8E1-CES: 1-248

The following example changes the PNNI port resource partition configured on port 1 of an MPSM card to use an ingress and egress bandwidth of 50 percent, a low LCN number of 1, a high LCN number of 1, and the maximum connections available as 1:
M8850_SF.1.28.MPSM8T1.CES.a > cnfrscprtn 1 2 50 50 1 1 1
M8850_SF.1.28.MPSM8T1.CES.a > 
Deleting a Port Resource Partition Configuration on PXM45 and PXM1E Based Switches

To delete the resource partition configuration of a port on a CESM or MPSM card, use the following procedure.

Step 1 Delete all connections that are associated with the port resource partition (dspcons and delcon commands).