MPSM Card Management

Table Of Contents

Card Management on MPSM-T3E3-155 and MPSM-16-T1E1

Managing CLI Sessions

Managing Cards

Displaying General Card Information

Displaying Software Version and Status Information

Managing Feature Licenses

Displaying Feature Licenses

Moving MPSM Feature Licenses

Allocating MPSM Feature Licenses

Managing MPSM Feature License Alarms

Managing the Card Clock Source

Managing Card SCTs

Displaying the SCT Assigned to a Card

Selecting or Changing a Card SCT

Displaying Card SCT Settings

Managing Port SCTs

Displaying the SCT Assigned to a Port

Selecting a Port SCT

Changing a Port SCT

Displaying Port SCT Settings

Managing Lines

Displaying a List of Lines

Displaying the Configuration for One Line

Bringing Down a Line

Managing Line Alarms

Managing Ports

Displaying a List of Ports

Displaying the Status of One Port

Modifying an ATM Port

Modifying a Frame Relay Port

Deleting Ports

Managing Multilink Frame Relay Services

Managing MFR Bundles

Managing MFR Links

Managing Ports

Deleting Bundles, Links, and Ports

Managing Multilink PPP Services

Managing Bundles

Managing PPP Links

Managing PPPMUX

Deleting MLPPP Bundles, Links, and PPPMUX

Displaying Statistics

Displaying Operational Loads

Displaying Load Assignments

Managing Resource Partitions

ATM Port Resource Partitions

Frame Relay Port Resource Partitions

Managing Connections

ATM Connections

Frame Relay Connections

Verifying PNNI Communication

Verifying PNNI Trunk Communication

Verifying End-to-End PNNI Communications

Managing IMA Groups

Displaying a List of IMA Groups

Displaying the Configuration for One IMA Group

Configuring an IMA Group

Configuring an IMA Link

Deleting Lines from an IMA Group

Deleting an IMA Group

Administratively Enabling and Disabling IMA

Testing an IMA Link

Modifying an IMA Link Test

Performing Loopback Tests

Performing Bit Error Rate Tests

Managing MPSM Core Dumps

Overview of MPSM Core Dumps

Managing Core Dump Files

Aborting Core Dumps

Displaying Core Command Options

Displaying Core Dump Settings

Displaying the Core Dump Mask

Configuring Core Dump Settings

Hot-Dumping the Core

Card Management on MPSM-T3E3-155 and MPSM-16-T1E1

This chapter describes management and test procedures for the Cisco MPSM-T3E3-155 and MPSM-16-T1E1 cards.

• Managing CLI Sessions

• Managing Cards

• Managing Feature Licenses

• Managing the Card Clock Source

• Managing Card SCTs

• Managing Port SCTs

• Managing Lines

• Managing Ports

• Managing Multilink Frame Relay Services

• Managing Multilink PPP Services

• Managing Resource Partitions

• Managing Connections

• Verifying PNNI Communication

• Managing IMA Groups

• Performing Loopback Tests

• Performing Bit Error Rate Tests

• Managing MPSM Core Dumps

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.12, and the Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3 documentation.

Table 6-1 describes session management commands supported on the cards. For more information on these commands, see Chapter 7, "Command Reference."

Table 6-1 Session Management Commands

Command

Description

?

Help

Displays available commands.

clrscrn

Clears the session window.

timeout

Sets the amount of idle time in a user-session. Default time is 10 minutes.

who

whoami

Displays details about the user currently logged into a card.

Managing Cards

Basic card initialization and configuration are described in the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2, and the Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3 documentation.

The following sections describe:

• Displaying General Card Information

• Displaying Software Version and Status Information

The following procedures are some of the most common card management commands. For a list of all card management commands, refer to Chapter 7, "Command Reference."

Displaying General Card Information

To display general information about a card, enter the dspcd command, as shown in the following example:

M8830_CH.12.MPSM155[ATM].a > dspcd
Front Card Back Card
---------- ---------
Card Type: MPSM-T3E3-155 SFP-2-155
State: Active Present
Serial Number: SAD073504CT SAD0732038H
Boot FW Rev: 4.9(23.88)P1 ---
SW Rev: 4.9(23.88)P1 ---
HW Rev: 02 04
Orderable Part#: 800-23005-04 800-23170-02
PCA Part#: 73-8597-04 73-8684-02
CLEI Code: 0 0

SFP Information:
Line FRU Type Vendor Name Part # Rev Serial #
---- ----------------- ---------------- ---------------- ---- ----------------
1.1 SMFSR-1-155-SFP OCP TRP-03L3I1BCS 2109325
1.2 --- --- --- --- ---

Product ID:
Version ID:
Reset Reason: Reset from PXM
Card Summary:

Type <CR> to continue, Q<CR> to stop:
Card SCT Id: 0
Features Enabled: ATM, FRAME RELAY
#Max ATM Conns #ATM Ports #ATM Partitions #ATM SPVCs #ATM SPVPs #ATM SVCs
-------------- ---------- --------------- ---------- ---------- ---------
4000 0 0 0 0 0
#Max FR Conns #FR Ports #FR Partitions #FR SPVCs
------------- --------- -------------- ---------
4000 0 0 0
#IMA Groups #IMA Links
----------- ----------
0 0

FC Operation Mode: CARD_OPER_MODE_155

M8830_CH.12.MPSM155[ATM].a >
Displaying Software Version and Status Information

To display information about the boot and runtime software running on a card, enter the dspversion command, as shown in the following example:

M8830_CH.12.MPSM155[ATM].a > dspversion

Image Type Shelf Type Card Type Version Built On
---------- ---------- ---------- ------------ ------------
Runtime MGX MPSM-T3E3-155 4.9(23.88)P1 Jan 19 2004, 20:54:33
Boot MGX MPSM-T3E3-155 4.9(23.88)P1 -

Managing Feature Licenses

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

The following sections describe:

• Displaying 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 rekey 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.12.

Displaying Feature Licenses

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 cards, use the dspliccd command.

In the following example, the displiccd command shows one multilink feature license programmed into the NVRAM on the card:

M8830_CH.12.MPSM155[ATM].a > dspliccd
Card License Alarm: None
Service Module Type: MPSM-T3E3-155
Service Module Serial Number: SAD073504CT
Provisioning (addcon) Allowed: YES
=========================================================
Needed License Type Needed Licenses
------------------- ---------------
MultiLink 1

=========================================================
Allocated License Type Allocated licenses
---------------------- ------------------
MultiLink 1

=========================================================
Programmed License Type Programmed licenses
------------------------ -------------------

=========================================================
Programmed License Registered: NO
License registration node: NONE
License registration chassis: NONE

Type <CR> to continue, Q<CR> to stop:
=========================================================

M8830_CH.12.MPSM155[ATM].a >

If a feature license is moved to the PXM license pool, then the Programmed License Registered field in the output of the dspliccd command states YES. In this example, the multilink license programmed into the NVRAM on the card is not moved to the PXM license pool.

Moving MPSM Feature Licenses

To move feature licenses programmed on cards to the switch license pool on the PXM processor card, use the movelic command.

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

To move feature licenses, perform the following steps:

Step 1 To view the feature licenses that are programmed on the card, enter the dspliccd command:

M8830_CH.12.MPSM155[ATM].a > dspliccd
Card License Alarm: None
Service Module Type: MPSM-T3E3-155
Service Module Serial Number: SAD073504CT
Provisioning (addcon) Allowed: YES
=========================================================
Needed License Type Needed Licenses
------------------- ---------------

=========================================================
Allocated License Type Allocated licenses
---------------------- ------------------
1

=========================================================
Programmed License Type Programmed licenses
------------------------ -------------------
MultiLink 1

=========================================================
Programmed License Registered: NO
License registration node: NONE
License registration chassis: NONE

=========================================================

In this example, the output of the dspliccd command shows that one multilink feature license is programmed into the NVRAM on the card.

Step 2 To move the feature licenses programmed on the card to the switch license pool on the PXM processor card, enter the movelic command:

M8830_CH.12.MPSM155[ATM].a > movelic
------------------------------------
Programmed License Type#Programmed
-----------------------------------------------
MultiLink

Do you want to proceed (Yes/No)? y
Card Licenses have been moved to license pool.

After the feature licenses are moved from the card and installed in the switch license pool on the PXM processor card, the feature licenses are available for use by the cards installed in that switch.

Step 3 When feature licenses are moved from the NVRAM on the card to the PXM license pool, the process is also referred to as registration of licenses with the switch.

To verify feature license registration into the switch license pool, enter the dspliccd command:

M8830_CH.12.MPSM155[ATM].a > dspliccd
Card License Alarm: None
Service Module Type: MPSM8T1E1
Service Module Serial Number: SAG07208RRA
Provisioning (addcon) Allowed: YES
=========================================================
Needed License Type Needed Licenses
------------------- ---------------

=========================================================
Allocated License Type Allocated licenses
---------------------- ------------------

=========================================================
Programmed License Type Programmed licenses
------------------------ -------------------
MultiLink 1

=========================================================
Programmed License Registered: YES
License registration node: CH
License registration chassis: SCA062300GF
=========================================================

This example shows that the multilink feature license has been registered, the name of the switch where the license is registered, and the chassis serial number of the switch where the feature license is registered.

Step 4 Enter the dsplics command on the PXM processor card to view the MPSM feature licenses installed in the PXM license pool:

M8830_CH.1.PXM.a > dsplics
M8850_SF System Rev: 05.00 Aug. 05, 2004 09:12:39 GMT
MGX8850 Node Alarm: MAJOR
Licensed License Licenses Licenses Licenses
Card Type Type Installed Allocated Available
----------------- ----------- --------- --------- ---------
MPSM-T3E3-155 MultiLink 1 0 1

In this example, one multilink feature license is successfully moved from the card into the PXM license pool.

Allocating MPSM Feature Licenses

To allocate a feature license to an MPSM-T3E3-155 or MPSM-16-T1E1 card, configure the card to use the licensed feature.

For example, to assign a multilink ATM feature license to an MPSM-T3E3-155 card, enter the addimagrp command and add an IMA group on the card. If the license pool on the PXM has an available license for that feature and card type, that license is automatically assigned to the card and the feature is successfully configured.

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

Managing MPSM Feature License Alarms

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

Node License Alarm

Node license alarms can occur under the following conditions:

•A switch configuration that was saved before licenses were added or transferred to and from the PXM license pool is 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 are raised.

To troubleshoot the node license alarm:

•On PXM45 and PXM1E platforms—Use the PXM dspndalms command

•On PXM1 platforms—Use the PXM dspcd command

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 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.12.

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. To clear slot license alarms raised under this condition, rekey 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. To clear slot license alarms raised under this condition, add the required number of licenses to the PXM license pool or release 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.

To troubleshoot slot license alarms on the PXM card, use the dsplicalms and dspliccd <slot> commands. To troubleshoot slot license alarms, use the dspcd and dspliccd commands.

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.

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 alarms. 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 clear, the following actions are taken:

•An event is logged indicating the expiration of the grace period for a given slot needing licenses.

•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 clear.

When the PXM license pool is rekeyed or licenses are added to the PXM license pool, provisioning is restored and the switch exits the license alarm state.

Managing the Card Clock Source

To configure a switch to receive a clock source on a MPSM-T3E3-155 or MPSM-16-T1E1card line, perform the following general tasks:

•Bring up and configure a physical line between the card and the node supplying the clock source (see the "Setting Up Lines" section in Chapter 2, "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication.")

•To configure a SONET line, configure a path on the SONET line. (See the "Channelizing MPSM-T3E3-155 SONET, SDH, and DS3 (T3) Lines" section in Chapter 2, "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication.")

•Create a logical port (subport) on the active physical line to receive the clock signal (To create an ATM port, see the "Adding ATM Ports" section in Chapter 3, "Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1.")

Note If the connection is between two cards of the same type, you must perform this task on both ends of the connection. If the connection is between an MPSM-T3E3-155 card and a different product or card, perform this task only on the MPSM-T3E3-155 or MPSM-16-T1E1 end of the connection, and then refer to the other product or card's documentation for instructions on configuring the other end of the clock source connection.

•Create a resource partition to define how the port resources on the card are to be used by the PNNI controller. (To create a resource partition on an ATM port, see the "Partitioning Port Resources on the PNNI Controller" section in Chapter 3, "Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1.")

Note If the connection is between two cards of the same type, you must perform this task on both ends of the connection. If the connection is between an MPSM-T3E3-155 card and a different product or card, perform this task only on the MPSM-T3E3-155 or MPSM-16-T1E1 end of the connection, and then refer to the other product or card's documentation for instructions on configuring the other end of the clock source connection.

Note Frame Relay ports cannot be clock sources for the node.

To configure a clock source after the physical line and port are configured on the MPSM-T3E3-155 or MPSM-16-T1E1 card, perform the following steps:

Step 1 Establish a configuration session with the active PXM using a username with Group1 privileges or higher.

Step 2 To establish a primary or secondary card clock source, enter the cnfclksrc command at the active PXM as follows:

mgx8850a.7.PXM45.a > cnfclksrc <priority> [shelf.] <slot.ifNum>

Tip To obtain the correct portid specification, use the port ID displayed when you enter the dsppnports command.

Table 6-2 describes the arguments for the cnfclksrc command.

Table 6-2 Arguments for cnfclksrc Command When Used with MPSM-T3E3-155 or MPSM-16-T1E1 Card

Argument

Value

Description

priority

primary or secondary

Clock source type.

Replace the priority argument with the type of clock source for the card. This argument can be either primary or secondary (the latter is the default value).

shelf

1

Shelf identifier (optional).

The shelf value is always 1.

slot

MGX 8850 (PXM1E/PXM45):
1 to 6, 9 to 22, and 25 to 32

MGX 8830:

3 to 14

Slot identifier.

Identifies the slot number of the card that is to receive the clock signal.

ifnum

1 to 1003

Interface number.

Corresponds to the interface number or logical port number which can range from 1 to 1003. The interface number must be previously defined by means of the addport command.

In the following example, the cnfclksrc command configures a secondary clock source for subport (logical port) 10 on a card in slot 3.

mgx8850a.7.PXM45.a > cnfclksrc secondary 3.10

Step 3 To configure a secondary clock source, repeat Step 2 using the appropriate arguments for the secondary clock source.

Managing Card SCTs

The sections that follow describe how to manage card SCTs using the following tasks:

• Displaying the SCT Assigned to a Card

• Selecting or Changing a Card SCT

• Displaying Card SCT Settings

Displaying the SCT Assigned to a Card

To display the SCT assigned to a card, use the following procedure.

Step 1 Establish a configuration session at any user access level.

Step 2 Enter the cc command to change to the card for which you want to display the SCT number.

Step 3 Enter the dspcd command.

The dspcd report displays a row labeled "Card SCT Id," which identifies the SCT assigned to the card. In the following example, the Card SCT Id is 0 (the default SCT):

M8830_CH.12.MPSM155[FR].a > dspcd
Front Card Back Card
---------- ---------
Card Type: MPSM-T3E3-155 SFP-2-155
State: Active Present
Serial Number: SAD073504CT SAD0732038H
Boot FW Rev: 4.9(23.88)P1 ---
SW Rev: 4.9(23.88)P1 ---
HW Rev: 02 04
Orderable Part#: 800-23005-04 800-23170-02
PCA Part#: 73-8597-04 73-8684-02
CLEI Code: 0 0

SFP Information:
Line FRU Type Vendor Name Part # Rev Serial #
---- ----------------- ---------------- ---------------- ---- ----------------
1.1 SMFSR-1-155-SFP OCP TRP-03L3I1BCS 2109325
1.2 --- --- --- --- ---

Product ID:
Version ID:
Reset Reason: Reset from PXM
Card Summary:

Type <CR> to continue, Q<CR> to stop:
Card SCT Id: 0
Features Enabled: ATM, FRAME RELAY
#Max ATM Conns #ATM Ports #ATM Partitions #ATM SPVCs #ATM SPVPs #ATM SVCs
-------------- ---------- --------------- ---------- ---------- ---------
4000 2 2 2 0 0
#Max FR Conns #FR Ports #FR Partitions #FR SPVCs
------------- --------- -------------- ---------
4000 3 3 2
#IMA Groups #IMA Links
----------- ----------
0 0

FC Operation Mode: CARD_OPER_MODE_155

M8830_CH.12.MPSM155[FR].a >

Selecting or Changing a Card SCT

A card SCT defines the queue parameters for the destination slot based cell queues towards the backplane. The same card SCT may be used for multiple cards of the same card type. The default card SCT is SCT 0.

Note An SCT must be registered before you can select it for a card or port. The exception to this requirement is the default SCT (SCT 0), which is permanently registered. For instructions on registering SCTs, see Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.

To select an SCT for a card, use the following procedure.

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Change to the active service module for which you will select or change an SCT by entering the cc command.

M8830_CH.1.PXM.a > cc 12

(session redirected)

Note In a redundant pair, you must specify the SCT on the active card.

Step 3 Before you can change the card SCT, all ports on the card must be down. To verify the status of ports on the card, enter the dspports command.

M8830_CH.12.MPSM155[ATM].a > dspports
ifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IA
Path State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GP
VUNI) EVNNI) EVNNI)
----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- --
5 1.1.2 Up Up 1000 1000 0/ 0 =Def NNI 0 0 0 NA
10 1.1.1 Up Up 100 100 0/ 0 =Def NNI 0 0 0 NA

Step 4 Bring down all ports that are in the admin state `up.'

If you are in the ATM CLI context, enter the dnallports command to bring down all active ATM ports on the current card, as shown in the following example:

M8830_CH.12.MPSM155[ATM].a > dnallports
dnport/dnallports can disrupt traffic on existing connections.
Use this command only to modify partition parameters or change SCT
Do you want to proceed (Yes/No) ? y

If you are in the Frame Relay CLI context, you must bring down each port individually using the dnport<ifNum> command. Replace <ifNum> with the number of the active port you want to bring down. In the following example, the user enters the dnport <ifNum> three times to bring down three active Frame Relay ports:

M8830_CH.12.MPSM155[FR].a > dnport 20
Traffic loss will result on all frame relay connections on this card.
Do you want to proceed (Yes/No) ? y

M8830_CH.12.MPSM155[FR].a > dnport 30
Traffic loss will result on all frame relay connections on this card.
Do you want to proceed (Yes/No) ? y

M8830_CH.12.MPSM155[FR].a > dnport 40
Traffic loss will result on all frame relay connections on this card.
Do you want to proceed (Yes/No) ? y

Step 5 To configure the card SCT, enter the cnfcdsct command as follows:

M8830_CH.12.MPSM155[FR].a > cnfcdsct <sctID>

Replace sctID with the number of the SCT that you want to assign to the card.

In the following example, the user assigns the SCT 1 to the current card:

M8850_NY.13.MPSM155[ATM].a > cnfcdsct 1

Step 6 To verify the SCT change, enter the dspcd command.

Step 7 Bring up all of the ports that you brought down in Step 4.

If you are in the ATM CLI context, enter the upallports command to bring up all ATM ports at one time, as shown in the following example.

M8830_CH.12.MPSM155[ATM].a > upallports

If you are in the Frame Relay CLI context, you must activate each port individually with the upport <ifNum> command. Replace <ifNum> with the number of the port you want to activate. In the following example, the user enters the upport <ifNum> command three times to active the three Frame Relay ports that were brought down in the example in Step 4:

M8830_CH.12.MPSM155[FR].a > upport 20

M8830_CH.12.MPSM155[FR].a > upport 30

M8830_CH.12.MPSM155[FR].a > upport 40

Step 8 Enter the dspports command in the appropriate CLI context to verify that the appropriate ports are up.

To verify that all ATM ports are brought up, enter the dspports command in the ATM CLI context:

M8830_CH.12.MPSM155[ATM].a > dspports
ifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IA
Path State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GP
VUNI) EVNNI) EVNNI)
----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- --
5 1.1.2 Up Up 1000 1000 0/ 0 =Def NNI 0 0 0 NA
10 1.1.1 Up Up 100 100 0/ 0 =Def NNI 0 0 0 NA

To verify that all Frame Relay ports are brought up, enter the dspports command in the Frame Relay CLI context as shown in the following example.

M8830_CH.12.MPSM155[FR].a > dspports
ifNum Line/Path Admin Oper ifType SCT id FRF 12
State State Conf./InUse Fragmentation
----- ----------- ----- --------------- ------------ ----------- -------------
20 1.1.3:2 Up Up Frame Forward 0/ 0 =Def Disabled
30 1.1.3:3 Up Up Frame Forward 0/ 0 =Def Disabled
40 1.1.3:4 Up Up Frame Forward 0/ 0 =Def Disabled

Note To change to the ATM CLI context, enter the setctx atm command. To change to the Frame Relay CLI context, enter the setctx fr command.

Displaying Card SCT Settings

To view the card SCT settings, use the following procedure:

Step 1 Establish a CLI management session at any user access level, and enter the cc command to change to the card.

Step 2 Enter the dspcdsct command:

M8830_CH.12.MPSM155[FR].a > dspcdsct <gen|cosThr|vcFr> [-units <units>]

Select an option to display one of the following SCT configuration reports:

•gen—Displays general SCT parameters.

•costhr—Displays COSB threshold parameters.

•vcFr—displays virtual circuit (VC) Frame Relay parameters.

Note The vcFr SCT is available only in the Frame Relay CLI context. If you are not in the Frame Relay CLI context, enter the setctx fr command to change the Frame Relay CLI context before you enter the dspcdsct vcFr command.

The following section lists sample reports for each of these options.

To specify the units in time or cells and bytes, enter the dspcdsct command with the optional -units keyword, followed by one of the following options:

•time—Units in time and 0.0001% of max (default)

•cellbyte—Units in cells and bytes

The sections that follow display the reports for each of the dspcdsct command options.

Card SCT General SCT Parameters—dspcdsct gen

When you enter the dspcdsct gen command, the following report appears:

M8830_CH.12.MPSM155[FR].a > dspcdsct gen

+----------------------------------------------------+
| Service Class Template [ 0] : General Parameters |
| Major Version [ 1] : Minor Version [ 0] |
+---------------------------------------------------------------------------+
| SERV-TYPE(HEX) |COSB_NUM | CAC_TYPE | UPC_ENB | GCRA1_PLCY |GCRA2_PLCY |
+---------------------------------------------------------------------------+
| VSI_DEFAULT( 1)| 1 | BCAC | DISABLED | DISCARD | DISCARD |
| VSI_SIGNAL( 2)| 2 | BCAC | DISABLED | DISCARD | DISCARD |
| VSI_TERM_SIG( 3)| 13 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_CBR1(100)| 2 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_VBRrt1(101)| 3 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_VBRrt2(102)| 3 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_VBRrt3(103)| 3 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_VBRnrt1(104)| 4 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_VBRnrt2(105)| 4 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_VBRnrt3(106)| 4 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_UBR1(107)| 5 | LCN_CAC | DISABLED | DISCARD | DISCARD |
| ATMF_UBR2(108)| 5 | LCN_CAC | DISABLED | DISCARD | DISCARD |
| ATMF_ABR(109)| 4 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_CBR2(10a)| 2 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_CBR3(10b)| 2 | BCAC | DISABLED | DISCARD | DISCARD |

Type <CR> to continue, Q<CR> to stop:
| FR_HIPRIORITY(500)| 6 | LCN_CAC | DISABLED | DISCARD | DISCARD |
| FR_LOPRIORITY(501)| 7 | LCN_CAC | DISABLED | DISCARD | DISCARD |
| FR_ATMCBR(502)| 8 | LCN_CAC | DISABLED | DISCARD | DISCARD |
| FR_ATMVBRrt(503)| 9 | LCN_CAC | DISABLED | DISCARD | DISCARD |
| FR_ATMVBRnrt(504)| 10 | LCN_CAC | DISABLED | DISCARD | DISCARD |
| FR_ATMABR(505)| 11 | LCN_CAC | DISABLED | DISCARD | DISCARD |
| FR_ATMUBR(506)| 12 | LCN_CAC | DISABLED | DISCARD | DISCARD |
+-----------------------------------------------------------------------------+

Note The dspcdsct gen command displays the same information, regardless of the CLI context of the card.

Card SCT COSB Threshold Parameters—dspcdsct cosThr

When you enter the dspcdsct cosThr command, the following report appears:

M8850_NY.13.MPSM155[ATM].a > dspcdsct cosThr
+----------------------------------------------------------+
| Service Class Template [ 0] : COSB Threshold Parameters |
| Major Version [ 1] : Minor Version [ 0] |
+----------------------------------------------------------+
|COSB| MAX_THR | FR_MAX_THR | DE_THR | FECN_THR |
| | (uSec) | (mSec) | (0.0001%)| (0.0001%)|
+---------------------------------------------------+
| 1 | 5700 | 2000 | 6000000 | 6000000 |
| 2 | 30000 | 2000 | 6000000 | 6000000 |
| 3 | 40000 | 2000 | 6000000 | 6000000 |
| 4 | 90000 | 2000 | 6000000 | 6000000 |
| 5 | 90000 | 2000 | 6000000 | 6000000 |
| 6 | 20000 | 2000 | 6000000 | 6000000 |
| 7 | 20000 | 2000 | 6000000 | 6000000 |
| 8 | 20000 | 2000 | 6000000 | 6000000 |
| 9 | 20000 | 2000 | 6000000 | 6000000 |
| 10 | 20000 | 2000 | 6000000 | 6000000 |
| 11 | 20000 | 2000 | 6000000 | 6000000 |
| 12 | 20000 | 2000 | 6000000 | 6000000 |
| 13 | 20000 | 2000 | 6000000 | 6000000 |
| 14 | 20000 | 2000 | 6000000 | 6000000 |
| 15 | 20000 | 2000 | 6000000 | 6000000 |

Type <CR> to continue, Q<CR> to stop:
| 16 | 20000 | 2000 | 6000000 | 6000000 |
+---------------------------------------------------+
+ cosb_max_threshold is valid for ATM port only +
COSB threshold are used only from port sct
COSB threshold are used only from port sct
+---------------------------------------------------+

Note The dspcdsct cosThr command displays the same information, regardless of the CLI context of the card.

Card SCT Virtual Circuit Frame Relay Parameters—dspcdsct vcFr

When you enter the dspcdsct vcFr command, the following report appears:

M8830_CH.12.MPSM155[FR].a > dspcdsct vcFr

+-----------------------------------------------------------------+
| Service Class Template [0] : Bw and Policing Parameters |
+-------------------------------------------------------------------+
| SERV TYPE(DEC) | DE TAG | FECN | DE TO | CLP TO |
| | ENABLE | TO EFCI | CLP MAP | DE MAP |
+-------------------------------------------------------------------+
|FR_HIPRIORITY(1280)| DISABLED | SET_ZERO | MAP | MAP |
|FR_LOPRIORITY(1281)| DISABLED | SET_ZERO | MAP | MAP |
+-----------------------------------------------+
| SERV TYPE(DEC) | MAX Th | FECN | DE |
| | MILLSEC |0.0001% |0.0001% |
+-----------------------------------------------+
|FR_HIPRIORITY(1280)| 3 |1000000| 800000|
|FR_LOPRIORITY(1281)| 3 |1000000| 800000|
+-------------------------------------------------------------------+
BECN and GLB TH not used
+-------------------------------------------------------------------+

Note The dspcdsct vcFr command is available only in the Frame Relay CLI context. If the card is in the ATM CLI context, enter the setctx fr command to change to the Frame Relay CLI context before you enter the dspcdsct vcFr command.

Managing Port SCTs

The following sections describe how to manage port SCTs using the following tasks:

• Displaying the SCT Assigned to a Port

• Selecting a Port SCT

• Changing a Port SCT

• Displaying Port SCT Settings

Displaying the SCT Assigned to a Port

To display the SCT assigned to a port, use the following procedure.

Step 1 Establish a configuration session at any user access level, and enter the cc command to change to the appropriate card.

Step 2 Enter the dspports command.

In both the Frame Relay and ATM CLI context, the dspports report displays a column labeled "sctID Cnf/InUse," which identifies the SCT assigned to each port.

The following example shows the dspports report in the ATM CLI context.

M8830_CH.12.MPSM155[ATM].a > dspports
ifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IMA
Path State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GRP
VUNI) EVNNI) EVNNI)
----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- ---
5 1.1.2 Up Up 1000 1000 0/ 0 =Def NNI 0 0 0 N/A
10 1.1.1 Up Up 100 100 0/ 0 =Def NNI 0 0 0 N/A

The following example shows the dspports report in the Frame Relay CLI context.

M8830_CH.12.MPSM155[FR].a > dspports
ifNum Line/Path Admin Oper ifType SCT id FRF 12
State State Conf./InUse Fragmentation
----- ----------- ----- --------------- ------------ ----------- -------------
20 1.1.3:2 Up Up Frame Forward 0/ 0 =Def Disabled
30 1.1.3:3 Up Up Frame Forward 0/ 0 =Def Disabled
40 1.1.3:4 Up Up Frame Forward 0/ 0 =Def Disabled

Selecting a Port SCT

A port SCT defines queue parameters that apply to egress queues on a port. You can use the same port SCT for multiple ports. To select an SCT for an ATM port, enter the addport command as described in the "Adding ATM Ports" section in Chapter 3, "Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1." To select an SCT for a Frame Relay port, enter the addport command as described in " Provisioning Frame Relay Ports" section in Chapter 4, "Provisioning Frame Relay Services on MPSM-T3E3-155 and MPSM-16-T1E1."

Note An SCT must be registered before you can select it for a card or port. The exception to this requirement is the default SCT (SCT 0), which is permanently registered. For instructions on registering SCTs, see Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.

Changing a Port SCT

To change the SCT assigned to a port, use the following procedure.

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Enter the cc command to change to the active service module for which you will select or change an SCT.

M8830_CH.1.PXM.a > cc 12

(session redirected)

Note In a redundant pair, you must specify the SCT on the active card.

Step 3 Ensure that you are in the appropriate CLI context for the port that owns the SCT you want to change. To change an ATM port SCT, you must be in the ATM CLI context. To change a Frame Relay port SCT, you must be in the Frame Relay CLI context.

Note To change to the ATM CLI context, enter the setctx atm command. To change to the Frame Relay CLI context, enter the setctx fr command.

Step 4 Enter the dnport <ifNum> command to bring down the port whose SCT you want to change. Replace <ifNum> with the number of the port you want to bring down.

Note Enter the dspports command in the ATM CLI context to see a list of all ATM ports on the current card. Enter the dspports command in the Frame Relay CLI context to see a list of all Frame Relay ports on the current card.

Note You cannot change a port SCT while the port is up.

Step 5 Enter the cnfport <ifNum> -sct <sct> command to configure a new SCT on the port. Replace <ifNum> with the number of the port whose SCT you are replacing, and enter the -sct keyword, followed by the number of the SCT you want to assign to the port.

In the following example, the user assigns SCT 1 to the ATM port 5.

M8830_CH.12.MPSM155[ATM].a > cnfport 5 -sct 1

Note An SCT must be registered before you can select it for a card or port. The exception to this requirement is the default SCT (SCT 0), which is permanently registered. For instructions on registering SCTs, see the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.

Step 6 Enter the dspport <ifNum> command to verify that the appropriate SCT has been assigned to the port. Replace <ifNum> with the number of the port whose SCT you changed in Step 5. The new SCT associated with the port appears in the "SCT Id" column in the dspport command display.

Displaying Port SCT Settings

The MPSM-T3E3-155 and MPSM-16-T1E1 support different SCTs for Frame Relay ports and ATM ports. This section describes the following port SCT management tasks:

• Displaying ATM Port SCT Settings

• Displaying Frame Relay Port SCT Settings

• Displaying Port SCT General Parameters—dspportsct gen

• Displaying Port SCT Virtual Circuit Threshold Parameters—vcThr

• Displaying Port SCT COSB Threshold Parameters—cosThr

• Displaying Port SCT Virtual Circuit Frame Relay Parameters—vcFR

Displaying ATM Port SCT Settings

To view ATM port SCT settings, use the following procedure.

Step 1 Establish a CLI management session at any user access level.

Step 2 Verify that you are in the ATM CLI context.

Note The current service context appears within brackets next to the switch name in the switch prompt.

If you are in the Frame Relay CLI context, enter the setctx atm command to change to the ATM CLI context, as shown in the following example:

M8830_CH.12.MPSM155[FR].a > setctx atm

Step 3 Enter the dspportsct command.

M8830_CH.12.MPSM155[ATM].a > dspportsct <gen|vcThr|cosThr> <ifNum>

Select one of the options to display one of the SCT configuration reports, and replace <ifNum> with the number of the port you want to view. Table 6-3 describes the reports for each of these options.

Table 6-3 Options for dspportsct Command—ATM CLI Context

Option

Description

gen

Displays general SCT parameters.

vcThr

Displays virtual circuit threshold parameters.

cosThr

Displays COSB threshold parameters.

Displaying Frame Relay Port SCT Settings

To view the Frame Relay port SCT settings, use the following procedure.

Step 1 Establish a CLI management session at any user access level.

Step 2 Verify that you are in the Frame Relay CLI context.

Note The current service context appears within brackets next to the switch name in the switch prompt.

If you are in the ATM CLI context, enter the setctx fr command to change to the Frame Relay CLI context, as shown in the following example:

M8830_CH.12.MPSM155[ATM].a > setctx fr

Step 3 Enter the dspportsct command.

M8830_CH.12.MPSM155[FR].a > dspportsct <gen|cosThr|vcFR> <ifNum>

Select one of the options to display one of the SCT configuration reports, and replace <ifNum> with the number of the port you want to view. Table 6-4 describes the reports for each of these options.

Table 6-4 Options for dspportsct Command—Frame Relay CLI Context

Option

Description

gen

Displays general SCT parameters.

cosThr

Displays COSB threshold parameters.

vcFR

Displays virtual circuit Frame Relay parameters.

Displaying Port SCT General Parameters—dspportsct gen

When you enter the dspportsct gen command, the following report appears.

M8830_CH.12.MPSM155[FR].a > dspportsct gen 20

+----------------------------------------------------+
| Service Class Template [ 1] : General Parameters |
| Major Version [ 1] : Minor Version [ 0] |
+---------------------------------------------------------------------------+
| SERV-TYPE(HEX) |COSB_NUM | CAC_TYPE | UPC_ENB | GCRA1_PLCY |GCRA2_PLCY |
+---------------------------------------------------------------------------+
| VSI_SIGNAL( 2)| 1 | BCAC | DISABLED | DISCARD | DISCARD |
| VSI_TERM_SIG( 3)| 12 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_CBR1(100)| 1 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_VBRrt1(101)| 2 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_VBRrt2(102)| 2 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_VBRrt3(103)| 2 | BCAC | DISABLED | DISCARD | SET_DISC_TAGD |

| ATMF_VBRnrt1(104)| 3 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_VBRnrt2(105)| 3 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_VBRnrt3(106)| 3 | BCAC | DISABLED | DISCARD | SET_DISC_TAGD |

| ATMF_UBR1(107)| 4 | LCN_CAC | DISABLED | DISCARD | DISCARD |
| ATMF_UBR2(108)| 4 | LCN_CAC | DISABLED | DISCARD | DISCARD |
| ATMF_ABR(109)| 3 | BCAC | DISABLED | DISCARD | DISCARD |
| ATMF_CBR2(10a)| 1 | BCAC | DISABLED | DISCARD | SET_CLP |

Type <CR> to continue, Q<CR> to stop:
| ATMF_CBR3(10b)| 1 | BCAC | DISABLED | DISCARD | DISCARD |
| FR_HIPRIORITY(500)| 5 | BCAC | DISABLED | DISCARD | DISCARD |
| FR_LOPRIORITY(501)| 6 | BCAC | DISABLED | DISCARD | DISCARD |
| FR_ATMCBR(502)| 7 | BCAC | DISABLED | DISCARD | DISCARD |
| FR_ATMVBRrt(503)| 8 | BCAC | DISABLED | DISCARD | DISCARD |
| FR_ATMVBRnrt(504)| 9 | BCAC | DISABLED | DISCARD | DISCARD |
| FR_ATMABR(505)| 10 | BCAC | DISABLED | DISCARD | DISCARD |
| FR_ATMUBR(506)| 11 | BCAC | DISABLED | DISCARD | DISCARD |
+-----------------------------------------------------------------------------+

Note The dspportsct gen command display is the same for Frame Relay and ATM ports. To display general ATM port SCT parameters, you must be in the ATM CLI context. To display general Frame Relay port SCT parameters, you must be in the Frame Relay CLI context.

Table 6-5 describes the SCT general parameters shown in the example.

Table 6-5 SCT General Parameter Descriptions

Parameter

Range

Description

SERV-TYPE

—

Service type (for example, CBR, VBR, ABR) to which the parameters in this table apply (for example, COSB_NUM, CAC_TYPE, UPC_ENB).

COSB_NUM

1 to 16

Class of Service Buffer Number. The number that identifies one of the sixteen CoS buffers. A CoS buffer is a buffer that services connections with similar QoS requirements.

CAC_TYPE

LCN_CAC

B_CAC

E_CAC

Connection Admission Control. Used by an ATM switch during setup to determine if a connection requested QoS conforms to the guaranteed QoS standards for ATM connections.

•LCN_CAC: Logical Connection Number CAC

•B_CAC: Basic-CAC

•E_CAC: Enhanced-CAC

UPC_ENB

ENABLED

DISABLED

Usage Parameter Control Enable. Enables or disables GCRA policing functions on the connection.

GCRA-1

1 to 3

Generic Cell Rate Algorithm—Bucket 1. In ATM, an algorithm that defines conformance with respect to the traffic contract of the connection. For each cell arrival, the GCRA determines if the cell conforms to the traffic contract.

Note If UPC-Enable is set to disable, this object is not used.

Choose one of the following options to indicate how cells that fail the first bucket of the policer should be handled:

•1—Discard

•2—Set CLP bit

•3—Set CLP of untagged cells, discard tagged cells

GCRA-2

1 to 3

Generic Cell Rate Algorithm—Bucket 2. In ATM, an algorithm that defines conformance with respect to the traffic contract of the connection. For each cell arrival, the GCRA determines if the cell conforms to the traffic contract.

Note If UPC-Enable is set to disable, this object is not used.

Choose one of the following options to indicate how cells that fail the second bucket of the policer should be handled:

•1—Discard

•2—Set CLP bit

•3—Set CLP of untagged cells, discard tagged cells

Displaying Port SCT Virtual Circuit Threshold Parameters—vcThr

The following report appears when you enter the dspportsct vcThr command in the ATM CLI context:

mpsm_node1.3.MPSM155[ATM].a > dspportsct vcThr 5

+------------------------------------------------------+
| Service Class Template [ 0] : VC Threshold Parameters |
| Major Version [ 1] : Minor Version [ 0] |
+-------------------------------------------------------------------------+
| SERV TYPE(DEC) | MAX_CELL | EFCI |CLPlo/EPD1| CLPhi | EPD0 |
| | THR(uSec) | (0.0001%)| (0.0001%)| (0.0001%)| (0.0001%)|
+-------------------------------------------------------------------------+
| ATMF_CBR1( 256)| 5000 | 400000 | 400000 | 600000 | 800000 |
| ATMF_VBRrt1( 257)| 10000 | 400000 | 400000 | 600000 | 800000 |
| ATMF_VBRrt2( 258)| 10000 | 400000 | 400000 | 600000 | 800000 |
| ATMF_VBRrt3( 259)| 10000 | 400000 | 400000 | 600000 | 800000 |
| ATMF_VBRnrt1( 260)| 50000 | 400000 | 400000 | 600000 | 800000 |
| ATMF_VBRnrt2( 261)| 50000 | 400000 | 400000 | 600000 | 800000 |
| ATMF_VBRnrt3( 262)| 50000 | 400000 | 400000 | 600000 | 800000 |
| ATMF_UBR1( 263)| 100000 | 300000 | 300000 | 500000 | 700000 |
| ATMF_UBR2( 264)| 100000 | 300000 | 300000 | 500000 | 700000 |
| ATMF_ABR( 265)| 70000 | 400000 | 400000 | 600000 | 800000 |
| ATMF_CBR2( 266)| 5000 | 400000 | 400000 | 600000 | 800000 |
| ATMF_CBR3( 267)| 5000 | 400000 | 400000 | 600000 | 800000 |
+------------------------------------------+
| SERV TYPE(DEC) |PKT DISCARD| ABR_CNG_THR|

Type <CR> to continue, Q<CR> to stop:
| | MODE | (0.0001%) |
+------------------------------------------+
| ATMF_CBR1( 256)| DISABLED |
| ATMF_VBRrt1( 257)| DISABLED |
| ATMF_VBRrt2( 258)| DISABLED |
| ATMF_VBRrt3( 259)| DISABLED |
| ATMF_VBRnrt1( 260)| DISABLED |
| ATMF_VBRnrt2( 261)| DISABLED |
| ATMF_VBRnrt3( 262)| DISABLED |
| ATMF_UBR1( 263)| DISABLED |
| ATMF_UBR2( 264)| DISABLED |
| ATMF_ABR( 265)| DISABLED |
| ATMF_CBR2( 266)| DISABLED |
| ATMF_CBR3( 267)| DISABLED |
+-------------------------------+

Note The dspportsct vcThr command is available only in the ATM CLI context.

Table 6-6 describes the SCT VC Threshold parameters shown in the example.

Table 6-6 SCT VC Threshold Parameter Descriptions

Label

Range and Units

Description

SERV-TYPE

—

The service type (for example, CBR, VBR, ABR) to which the parameters (for example, EFCI, CLP_HI, EPD0) in this table apply.

MAX_CELL THR (uSec)

—

Indicates the MAX number of cells that can be buffered in the cell memory for that VC.

EFCI (.0.0001%)

1000000 = 100%

Indicates the threshold for Explicit Forward congestion Indication (EFCI). EFCI is represented as a percentage of the MAX_CELL THR. A value of 1000000 is equal to 100%.

CLPlo/EPD1 (.0.0001%)

1000000 = 100%

Indicates the minimum delay any CLP1cell entering this VC encounters. If packet mode is enabled for the VC, then the cells are treated as EPD1 cells. The CLP/EDP1 threshold is represented as a percentage of the MAX_CELL THR. A value of 1000000 is equal to 100%.

CLPhi (.0.0001%)

1000000 = 100%

Indicates the maximum delay any CLP cell entering this VC will encounter. Any cell that encounters a queue latency greater than the CLPhi will be dropped. The CLPhi is represented as a percentage of the MAX_CELL THR. A value of 1000000 is equal to 100%.

EPD0 (.0.0001%)

1000000 = 100%

Indicates the maximum threshold for the EPD0 cells. Any cell that encounters a queue latency greater than the EPD0 threshold will be dropped. The EPD0 is represented as a percentage of the MAX_CELL THR. A value of 1000000 is equal to 100%.

Table 6-7 Class of Service Scaling Table—CoS

Index

Scaling Class Table #1 (CBR)

Scaling Class Table #2 (VBR)

Scaling Class Table #3 (ABR)

Scaling Class Table #4 (UBR)

0

100.00%

100.00%

100.00%

100.00%

1

100.00%

100.00%

100.00%

100.00%

2

100.00%

100.00%

100.00%

100.00%

3

100.00%

100.00%

100.00%

100.00%

4

100.00%

100.00%

100.00%

100.00%

5

100.00%

100.00%

100.00%

100.00%

6

100.00%

100.00%

100.00%

67.00%

7

100.00%

100.00%

100.00%

34.00%

8

100.00%

100.00%

50.00%

20.00%

9

100.00%

50.00%

25.00%

12.00%

10

100.00%

25.00%

12.00%

8.00%

11

100.00%

12.00%

6.00%

4.00%

12

100.00%

6.00%

3.00%

2.50%

13

100.00%

3.00%

1.30%

1.40%

14

100.00%

1.30%

0.75%

1.00%

15

100.00%

0.50%

0.50%

0.50%

Table 6-8 Logical Interface Scaling Table

Index

Scaling Class Table #1 (CBR)

Scaling Class Table #2 (VBR)

Scaling Class Table #3 (ABR)

Scaling Class Table #4 (UBR)

0

100.00%

100.00%

100.00%

100.00%

1

100.00%

100.00%

100.00%

100.00%

2

100.00%

100.00%

100.00%

100.00%

3

100.00%

100.00%

100.00%

100.00%

4

100.00%

100.00%

100.00%

100.00%

5

100.00%

100.00%

100.00%

100.00%

6

100.00%

100.00%

100.00%

67.00%

7

100.00%

100.00%

100.00%

34.00%

8

100.00%

100.00%

50.00%

20.00%

9

100.00%

50.00%

25.00%

12.00%

10

100.00%

25.00%

12.00%

8.00%

11

100.00%

12.00%

6.00%

4.00%

12

50.00%

6.00%

3.00%

2.50%

13

25.00%

3.00%

1.30%

1.40%

14

6.00%

1.30%

0.75%

1.00%

15

0.50%

0.50%

0.50%

0.50%

Displaying Port SCT COSB Threshold Parameters—cosThr

When you enter the dspportsct cosThr command, the following report appears:

M8830_CH.12.MPSM155[ATM].a > dspportsct cosThr 5
+----------------------------------------------------------+
| Service Class Template [ 1] : COSB Threshold Parameters |
| Major Version [ 1] : Minor Version [ 0] |
+----------------------------------------------------------+
|COSB| MAX_THR | FR_MAX_THR | DE_THR | FECN_THR |
| | (uSec) | (mSec) | (0.0001%)| (0.0001%)|
+---------------------------------------------------+
| 1 | 200000 | 15300000 | 1000000 | 1000000 |
| 2 | 200000 | 15300000 | 1000000 | 1000000 |
| 3 | 1000000 | 15300000 | 1000000 | 1000000 |
| 4 | 1000000 | 15300000 | 1000000 | 1000000 |
| 5 | 200000 | 15300000 | 1000000 | 1000000 |
| 6 | 200000 | 15300000 | 1000000 | 1000000 |
| 7 | 200000 | 15300000 | 1000000 | 1000000 |
| 8 | 200000 | 15300000 | 1000000 | 1000000 |
| 9 | 200000 | 15300000 | 1000000 | 1000000 |
| 10 | 200000 | 15300000 | 1000000 | 1000000 |
| 11 | 200000 | 15300000 | 1000000 | 1000000 |
| 12 | 200000 | 15300000 | 1000000 | 1000000 |
| 13 | 200000 | 15300000 | 1000000 | 1000000 |
| 14 | 200000 | 15300000 | 1000000 | 1000000 |
| 15 | 200000 | 15300000 | 1000000 | 1000000 |

Type <CR> to continue, Q<CR> to stop:
+---------------------------------------------------+
+ cosb_max_threshold is valid for ATM port only +
+ cosb_fr_*_threshold is valid for FR port only +
+---------------------------------------------------+

Table 6-9 describes the SCT COSB parameters shown in the example.

Note The dspportsct cosThr command display is the same for Frame Relay and ATM ports. To display general ATM port SCT parameters, you must be in the ATM CLI context. To display general Frame Relay port SCT parameters, you must be in the Frame Relay CLI context.

Table 6-9 SCT COSB Threshold Parameter Descriptions

Label

Range and Units

Description

COSB

—

The service type (for example, CBR, VBR, ABR) to which the parameters (for example, EFCI, CLP_HI, EPD0) in this table apply.

MAX_THR (usec)

0-5000000 microseconds

Indicates the maximum delay, in microseconds, that any CLP (0+1) cells entering this COSB might encounter. Any cell that encounters a queue latency greater than the MAX_THR are dropped.

FR_MAX_THR

0-5000000 microseconds

Indicates the maximum threshold on the payload memory that all Frame Relay VCs belonging to the same class of service occupy. The threshold is expressed as a percentage of the MAX_THR. A value of 1000000 is equal to 100%.

DE_THR

1000000 = 100%

Indicates the maximum threshold beyond which all Frame Relay cells marked with DE must be dropped. The threshold is expressed as a percentage of the MAX_THR. A value of 1000000 is equal to 100%.

FECN_THR

1000000 = 100%

Indicates the maximum threshold, in microseconds, beyond which all Frame Relay cells marked with FECN must be dropped. The threshold is expressed as a percentage of the MAX_THR. A value of 1000000 is equal to 100%.

Displaying Port SCT Virtual Circuit Frame Relay Parameters—vcFR

When you enter the dspportsct vcFR command in the Frame Relay CLI context, the following report appears:

M8830_CH.12.MPSM155[FR].a > dspportsct vcFR 20

+-----------------------------------------------------------------+
| Service Class Template [1] : Bw and Policing Parameters |
+-------------------------------------------------------------------+
| SERV TYPE(DEC) | DE TAG | FECN | DE TO | CLP TO |
| | ENABLE | TO EFCI | CLP MAP | DE MAP |
+-------------------------------------------------------------------+
|FR_HIPRIORITY(1280)| ENABLED | SET_ZERO | MAP | MAP |
|FR_LOPRIORITY(1281)| DISABLED | SET_ZERO | MAP | MAP |
+-----------------------------------------------+
| SERV TYPE(DEC) | MAX Th | FECN | DE |
| | MILLSEC |0.0001% |0.0001% |
+-----------------------------------------------+
|FR_HIPRIORITY(1280)| 200 | 600000| 600000|
|FR_LOPRIORITY(1281)| 341 | 600000| 600000|
+-------------------------------------------------------------------+
BECN and GLB TH not used
+-------------------------------------------------------------------+

Table 6-10 describes the SCT COSB parameters shown in the example.

Note The dspportsct vcFR command is available only in the Frame Relay CLI context.

Table 6-10 SCT General Parameter Descriptions

Parameter

Range

Description

SERV-TYPE

—

The service type (for example, high priority Frame Relay) to which the parameters in this table apply.

DE TAG ENABLE

ENABLED

DISABLED

Enables/disables DE tagging in the ingress direction.

FECN TO EFCI

MAP

SET_ZERO

Sets the FECN configuration to one of the following options:

•MAP—The Frame Relay FECN bits are mapped to EFCI bits in ATM cells.

•SET_ZERO—The FECN bits are ignored, and the EFCI bit is set to zero.

DE TO CLP MAP

MAP

SET_ZERO

SET_ONE

Sets the DE configuration to MAP, SET_ZERO, or SET_ONE.

•MAP—The Frame Relay DE bits are mapped to CLP bits in ATM cells.

•SET_ZERO—The DE bits are ignored, and the CLP bit is set to zero.

•SET_ONE—The DE bits are ignored, and the CLP bit is set to one.

CLP TO DE MAP

MAP

SET_ZERO

SET_ONE

IGNORE_CLP

Sets the CLP configuration to MAP, SET_ZERO, or SET_ONE.

•MAP—The ATM CLP bits are mapped to DE bits in Frame Relay cells.

•SET_ZERO—The CLP bits are ignored, and the DE bit is set to zero.

•SET_ONE—The CLP bits are ignored, and the DE bit is set to one.

•IGNORE—The CLP bits are ignored, and the DE bit remains as it is when it is received.

Managing Lines

Chapter 2, "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication,"describes how to bring up (add) and modify MPSM-T3E3-155 and MPSM-16-T1E1 card lines. The sections that follow provide procedures for doing the following tasks:

• Displaying a List of Lines

• Displaying the Configuration for One Line

• Bringing Down a Line

• Managing Line Alarms

Displaying a List of Lines

To display a list of lines on an a card, enter the dsplns command.

In the following example, the user displays lines on a MPSM-T3E3-155 card:

M8850_SF.10.MPSM155[ATM].a > dsplns
Line Line Line Line Length OOF AIS Valid Alarm
Num State Type Lpbk (meters) Criteria cBitsCheck Intvls State
---- ----- --------------- ---------- -------- ----------- ---------- ------ ----------
1.1 Up dsx3CbitParity NoLoop 0 3Of16Bits Check 96 Clear
1.2 Up dsx3CbitParity NoLoop 0 3Of16Bits Check 96 Clear
1.3 Up dsx3CbitParity NoLoop 0 3Of16Bits Check 96 Critical

In the following example, the user displays lines on a MPSM-16-T1E1 card:

M8850_SF.27.MPSM16T1E1[ATM].a > dsplns
Line Line Line Line Length Valid Alarm
Num State Type Lpbk (meters) Intvls State
---- ----- ----------- ----------- -------- ---------- -------
1.1 Up dsx1ESF NoLoop 1 96 Clear
1.2 Up dsx1ESF NoLoop 1 96 Clear
1.3 Up dsx1ESF NoLoop 1 96 Clear
1.4 Up dsx1ESF NoLoop 1 96 Clear
1.5 Up dsx1ESF NoLoop 1 96 Clear
1.6 Up dsx1ESF NoLoop 1 96 Clear
1.7 Down dsx1ESF NoLoop 1 0 Clear
1.8 Up dsx1ESF NoLoop 1 96 Clear
1.9 Up dsx1ESF NoLoop 1 96 Critical
1.10 Down dsx1ESF NoLoop 1 0 Clear
1.11 Down dsx1ESF NoLoop 1 0 Clear
1.12 Down dsx1ESF NoLoop 1 0 Clear
1.13 Up dsx1ESF NoLoop 1 96 Clear
1.14 Up dsx1ESF NoLoop 1 96 Clear
1.15 Down dsx1ESF NoLoop 1 0 Clear

Note The line number appears in the Line Num column in the format bay.line.

Displaying the Configuration for One Line

To display the configuration of one line on a card, enter the dspln <bay.line> command. Replace <bay.line> with the number of the line you want to display.

In the following example, the user displays the configuration for line 1.1 on a MPSM-T3E3-155 card:

M8850_SF.10.MPSM155[ATM].a > dspln 1.1
Line Number : 1.1
Admin Status : Up Alarm Status : Clear
Line Type : dsx3CbitParity Number of ATM ports : 1
Line Coding : ds3B3ZS Number of ATM partitions : 1
Line Length(meters) : 0 Number of ATM SPVC : 1
OOFCriteria : 3Of16Bits Number of ATM SPVP : 0
AIS c-Bits Check : Check Number of ATM SVC : 0
Loopback : NoLoop Number of ATM Sig VC : 0
Xmt. Clock source : localTiming Number of FR ports : 4
Rcv FEAC Validation : 8 out of 10 Number of FR Connections : 2
Channelized : Enabled Number of IMA Links : 4
Number of MFR Links : 8
NOTE: Number of ATM ports/parts/conns excludes those on IMA groups
Number of FR ports/conns excludes those on MFR bundles

In the following example, the user displays the configuration for line 1.1 on a MPSM-16-T1E1 card:

M8850_SF.27.MPSM16T1E1[ATM].a > dspln 1.1
Line Number : 1.1
Admin Status : Up Alarm Status : Clear
Line Type : dsx1ESF Number of ATM ports : 0
Line Coding : dsx1B8ZS Number of ATM partitions : 0
Line Length(meters) : 1 Number of ATM SPVC : 0
Loopback : NoLoop Number of ATM SPVP : 0
Xmt. Clock source : localTiming Number of ATM SVC : 0
Valid Intervals : 96 Number of ATM Sig VC : 0
Number of FR ports : 1
Number of FR Connections : 1
Number of IMA Links : 0
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, perform the following steps:

Step 1 Delete all connections to ports that are associated with the line or paths using the delcon command. To display all active connections, use the dspcons commands.

Tip Connections are associated with ports (dspcons), and ports are associated with lines or paths. To determine which connections use a line, first determine which ports are configured for that line using the dspports command.

Step 2 Delete all ports that are associated with the line or paths using the delport command. To display all active ports, use the dspports command. Before deleting ports on a path, bring down the path first using the dnpath 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 before you delete the port.

Step 3 If the line is channelized, remove the channelization using the cnfln command. See Chapter 2, "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication".

Step 4 To deactivate a line, enter the dnln <bay.line> command. Replace <bay.line> with the number of the line you want to bring down. You can view the available line numbers using the dsplns command.

In the following example, the user deactivates line 1.5, which is associated with port 5 and has a connection that uses DLCI 500.

M8850_SF.27.MPSM16T1E1[FR].a > delcon 5 500
Deletion successful

M8850_SF.27.MPSM16T1E1[FR].a > delport 5

M8850_SF.27.MPSM16T1E1[FR].a > dnln 1.5

Step 5 Enter the dsplns command to verify that the line is in the down in the Line State column. In the following example, the user verifies that line 1.5 is down.

M8850_SF.27.MPSM16T1E1[FR].a > dsplns
Line Line Line Line Length Valid Alarm
Num State Type Lpbk (meters) Intvls State
---- ----- ----------- ----------- -------- ---------- -------
1.1 Up dsx1ESF NoLoop 1 96 Clear
1.2 Up dsx1ESF NoLoop 1 96 Clear
1.3 Up dsx1ESF NoLoop 1 96 Clear
1.4 Up dsx1ESF NoLoop 1 96 Clear
1.5 Down dsx1ESF NoLoop 1 0 Clear
...
Managing Line Alarms

MPSM-T3E3-155 and MPSM-16-T1E1 cards generate line alarms when errors occur, as specified in ANSI T1.231. The significance of different types of alarms is listed in Table 6-11.

Table 6-11 Line Errors and Alarms

Error

Alarm Type

Transmit Downstream

Transmit Upstream

Comments

LOS (Loss of Signal)

Red

If a connection exists on the line, AIS OAM cells are transmitted over that connection.

RAI

Send line alarm trap

LOF (Loss of Frame)

Red

If a connection exists on the line, AIS OAM cells are transmitted over that connection.

RAI

Send line alarm trap

AIS (Alarm Indication Signal)

AIS (Yellow) when receiving AIS on the line

If a connection exists on the line, AIS OAM cells are transmitted over that connection.

RAI

Send connection alarm trap

MFAIS (E1 CAS only)

AIS (Yellow) when receiving AIS on the line

If a connection exists on the line, AIS OAM cells are transmitted over that connection.

RAI

Send line alarm trap

RAI (Remote Alarm Indication)

Yellow

—

—

Send line alarm trap

MFRAI (E1 CAS only)

Yellow

—

—

Send line alarm trap

Loss of Multi-frame Sync (E1 CAS only)

Red

If a connection exists on the line, AIS OAM cells are transmitted over that connection.

RAI

Send line alarm trap

Loss of CRC MF Alignment (E1 CRC only)

Red

If a connection exists on the line, AIS OAM cells are transmitted over that connection.

RAI

Send line alarm trap

Note When the line is in alarm, the line alarm trap is sent. Separate traps are not 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 separate traps are not sent for the connections that go into alarm due to the port alarm.

Use the commands in Table 6-12 to display, clear, and configure line alarms.

Table 6-12 Line and Path Alarm Commands

Command

Purpose

clradjlnalmcnt

Clears the statistical alarms and alarm counters for the adjacent back card in an automatic protection system (APS) configuration.

clrlnalmcnt

Clears the statistical alarms and alarm counters for a specific line.

clrpathalmcnt

Clears all the current alarm counters on the specified path (path_num). All counters are reset to zero.

cnflnalm

Configures statistical line alarms thresholds. You can use this command to make the lines more or less sensitive to alarms.

cnfpathalm

Configures a specified statistical alarm threshold for a specified path (path_num). It also configures the severity of the alarm.

dspadjlnalm

Displays the line alarm status for the adjacent back card.

dspadjlnalmcnt

Displays the alarm counters for the adjacent back card.

dsplnalm

Display the line and statistical alarm state for the specified line.

dsplnalms

Displays line and statistical alarms for all lines on the current card.

dsppathalm

Displays the following alarm information for the specified path (path_num).

dsppathalms

Displays the following alarm information for all the specified paths (path_filter).

dsplnalmcnf

Displays the current statistical line alarm thresholds on the specified line.

dsplnalmcnt

Displays the alarm counters for the specified line.

Use the commands in table Table 6-13 to display MFR alarms.

Table 6-13 Multilink Frame Relay Alarm Commands—MPSM-T3E3-155 Only

Command

Purpose

dspmfrbundlealm

Displays alarms and statistics for an MFR bundle.

dspmfrbundlealms

Displays alarms and statistic for a all MFR bundles.

dspmfrlnkalm

Displays alarms and statistics for an MFR link.

dspmfrlnkalms

Displays alarms and statistic for a all MFR links.

Managing Ports

This section explains how to manage ports:

• Displaying a List of Ports

• Displaying the Status of One Port

• Modifying an ATM Port

• Modifying a Frame Relay Port

• Deleting Ports

For information about adding ports and configuring services, see the following chapters:

•ATM— Chapter 3, "Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1"

•Frame Relay— Chapter 4, "Provisioning Frame Relay Services on MPSM-T3E3-155 and MPSM-16-T1E1"

•PPP— Chapter 5, "Provisioning Multilink PPP Services on MPSM-T3E3-155 and MPSM-16-T1E1"

Displaying a List of Ports

To display a list of all provisioned Frame Relay or ATM ports on the card, enter the dspports command in the appropriate CLI context.

Note The current CLI context of the card is displayed within brackets in the switch prompt. You can change the current CLI context of the card at any time by entering the setctx [atm | fr] command. Remember that the cards switch to the default service context as soon as you switch to another card via the cc command. To change the default service context of the card, enter the cnfclictx [atm | fr] command.

In the following example, the user displays all ATM ports on the current card:

M8850_SF.10.MPSM155[ATM].a > dspports
ifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IMA
Path State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GRP
VUNI) EVNNI) EVNNI)
----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- ---
17 1.1:17 Up Up 3622 3622 0/ 0 =Def UNI 0 0 0 N/A
18 1.2:17 Up Up 3622 3622 0/ 0 =Def UNI 0 0 0 N/A

In the following example, the user displays all Frame Relay ports on the current card:

M8850_SF.27.MPSM16T1E1[FR].a > dspports
ESR: Egress queue Service Ratio
SCT DS0 Port E FRF
If Line/Path Admn Oper if In Start Speed Signaling LMI 12
Num Num Stat Stat Type Use (Num) kbps ESR Type St Frg
---- ----------- ---- ---- ---- --- ------ ------ --- --------- --- ---
6 1.6 Up Up FR 0 1(24) 1536 1 None Off Off
11 1.1 Up Up FR 0 1(24) 1536 1 None Off Off
13 1.3 Up Up FR 0 1(24) 1536 1 None Off Off
14 1.4 Up Up FR 0 1(24) 1536 1 None Off Off
18 1.8 Up Up FR 0 1(24) 1536 1 None Off Off
19 1.9 Up LLDn FR 0 1(24) 1536 1 None Off Off

In the following example, the user displays all ports on the current card in MLPPP mode:

M8850_SF.25.MPSM16T1E1PPP[FR].a > dspports

ESR: Egress queue Service Ratio

SCT DS0 Port E FRF

If Line/Path Admn Oper if In Start Speed Signaling LMI 12 MLPPP

Num Num Stat Stat Type Use (Num) kbps ESR Type St Frg Bundle

---- ----------- ---- ---- ---- --- ------ ------ --- --------- --- --- ------

5 N/A Up Up FFwd 0 N/A 1536 1 None Off N/A 5

13 N/A Up Up FFwd 0 N/A 1536 1 None Off N/A 13

Displaying the Status of One Port

To display configuration information for one port on a card, enter the dspport <ifnum> command in the appropriate CLI context. Replace <ifnum> with the port or path identifier

Note The current CLI context of the card is displayed within brackets in the switch prompt. You can change the current CLI context of the card at any time by entering the setctx [atm | fr] command. Remember that the cards switch to the default service context as soon as you switch to another card using the cc command. To change the default service context of the card, enter the cnfclictx [atm | fr] command.

In the following example, the user displays the status for ATM port 17.

M8850_SF.10.MPSM155[ATM].a > dspport 17
Interface Number : 17
Line/Path Number : 1.1:17 IMA Group Number : N/A
Admin State : Up Operational State : Up
Guaranteed bandwidth(cells/sec): 3622 Number of partitions : 1
Maximum bandwidth(cells/sec) : 3622 Number of SPVC : 1
ifType : UNI Number of SPVP : 0
VPI number (VNNI, VUNI) : 0 Number of SVC : 0
Number of Sig VC : 0
MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0
SCT Id : 0 =Def
F4 to F5 Conversion : Disabled

In the following example, the user displays the status for Frame Relay port 11.

M8850_SF.27.MPSM16T1E1[FR].a > dspport 11
Interface Number : 11
Line Number : 1.1
DS0 Speed : 64 Kbps
DS0 Configuration Bit Map : 1(24)
Admin State : Up
Operational State : Up
Port State : Active
Port Signaling State : No Signaling Failure
Interface Type : Frame Relay
SCT Id : 0/0 =Def
Frame Header Length : Two Bytes
Flags Between Frames : 1
Equeue Service Ratio : 1
Port Speed : 1536 kbps
Checksum type : crc16
Over-subscription : Disabled
Signaling Protocol Type : None
Enhanced LMI : Disabled
FRF 1.2 Support : Disabled
Asynchronous Updates : Disabled
T391 Link Integrity Timer : 10 secs
T392 Polling Verification Timer : 15 secs

Type <CR> to continue, Q<CR> to stop:
N391 Full Status Polling Counter : 6
N392 Error Threshold : 3
N393 Monitored Event Count : 4
FRF.12 Fragmentation : Disabled
FRF.12 Fragment Size : 64 Bytes
Port HDLC Frame Inversion : Disabled
Number of Partitions : 1
Number of SPVC : 1
Modifying an ATM Port

To modify the configuration of an ATM port, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 If you are in the Frame Relay CLI context, enter the setctx atm command to change to the ATM CLI context, as shown in the following example:

M8830_CH.12.MPSM155[FR].a > setctx atm

Note The current service context appears within brackets in the switch prompt.

Step 3 Enter the dspports command to display all ATM ports on the current MPSM, and to obtain the ifnum of the port you want to modify.

M8850_SF.10.MPSM155[ATM].a > dspports
ifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IMA
Path State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GRP
VUNI) EVNNI) EVNNI)
----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- ---
17 1.1:17 Up Up 3622 3622 0/ 0 =Def UNI 0 0 0 N/A
18 1.2:17 Up Up 3622 3622 0/ 0 =Def UNI 0 0 0 N/A
19 1.1:18 Up Up 3622 3622 0/ 0 =Def EVUNI 0 0 128 N/A
20 1.2:18 Up Up 3622 3622 0/ 0 =Def EVUNI 0 0 128 N/A

Note The interface number for each port appears in the ifNum column.

Step 4 To modify SCT ID, enter the dnport <ifNum> command to bring down the port that you want to modify. Otherwise, skip this step.

In the following example, the user brings down the ATM port 19:

M8850_SF.10.MPSM155[ATM].a > dnport 19
Traffic loss will result on all connections on this port.
Do you want to proceed (Yes/No) ? y

Step 5 To modify port parameters, enter the cnfport command as follows:

M8850_SF.10.MPSM155[ATM].a > cnfport <ifNum> [-min <guaranteedRate>] [-max <maxrate>] [-sct <sctID>] [-minvpi <minVpi>] [-maxvpi <maxvpi>]

Table 6-14 describes the parameters for the cnfport command in the ATM CLI context.

Table 6-14 Parameters for the cnfport Command—ATM CLI Context

Parameter

Description

ifNum

Specifies the interface number (port number) of the port you are adding.

•MPSM-16-T1E1 range: 4-499

•MPSM-T3E3-155 range: 4-1003

Note To see the port numbers for all active ATM ports, use the dspports command in the ATM CLI context.

-min

Specifies the guaranteed rate on a logical port in cells per second (cps). The minimum rate can be either max cell rate of the interface, or a multiple of 50.

Use one of the following methods to calculate the guaranteed rate on an IMA port:

•T1 based IMA group—Multiple of 50 not greater than N * (3622 * (M - 1)/M * 2048/2049), where N is the number of IMA links in the IMA group, and M is the IMA group frame length.

•E1 based IMA group—Multiple of 50 not greater than N * (M - 1)/M * 2048/2049), where N is the number of IMA links in the IMA group, and M is the IMA group frame length.

The cumulative guaranteed rate cannot exceed the highest value in the following ranges:

•OC-192: Between 50 and 22605280

•OC-48: Between 50 and 5651320

•OC-3: 50-353207 cps

•T3: 50-96000 (PLCP) or 104268 (ADM) cps

•E3: 50-80000 cps

•T1: 50-3622 cps

•E1: 50-4528 cps

Note The guaranteed rate and max rate settings must be the same.

-max

Specifies the maximum rate on a logical port in cells/second. For all interface types (UNI, NNI, VNNI, EVNNI, and EVUNI), maxrate must be the same as guaranteedRate. See guaranteedRate.

-sct

Specifies the number of a service class template (SCT) for the port. The range is 0-255. Cisco provides SCT numbers 2, 3, 4, and 5. You can modify one of these SCTs through the Cisco WAN Manager application and assign a number in the range 6-255 to the new SCT. Subsequently, you can assign the new SCT to the port using the sctID parameter in cnfport. To see the ID of the current SCT for this port, use dspport. To see the parameters within the current SCT, use the dspportsct command.

Note The default setting for -sct is 0.

-minvpi

The minimum VPI for an EVUNI or EVNNI interface:

•EVUNI range: 0-255

•EVNNI range: 0-4095

-maxvpi

The maximum VPI for an EVUNI or EVNNI interface:

•EVUNI range: 0-255

•EVNNI range: 0-4095

In the following example, the user changes the minimum and maximum rates on port 19 to 3000 cps:

M8850_SF.10.MPSM155[ATM].a > cnfport 19 -min 3000 -max 3000

Step 6 If you brought down a port using the dnport command, enter the upport <ifNum> command as follows to re-activate that port. Replace <ifNum> with the interface number of the port you want to activate. Otherwise, skip this step.

M8850_SF.10.MPSM155[ATM].a > upport 19

Step 7 To verify the configuration of the port, enter the dspport <ifNum> command. Replace <ifNum> with the interface number of the port you modified.

M8850_SF.10.MPSM155[ATM].a > dspport 19
Interface Number : 19
Line/Path Number : 1.1:18 IMA Group Number : N/A
Admin State : Up Operational State : Up
Guaranteed bandwidth(cells/sec): 3000 Number of partitions : 1
Maximum bandwidth(cells/sec) : 3000 Number of SPVC : 1
ifType : EVUNI Number of SPVP : 0
VPI number (VNNI, VUNI) : 0 Number of SVC : 0
Number of Sig VC : 0
MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 128
SCT Id : 0 =Def
F4 to F5 Conversion : Disabled

Modifying a Frame Relay Port

This section explains how to modify Frame Relay ports on the MPSM-T3E3-155 and MPSM-16-T1E1 cards, and multilink Frame Relay ports on the MPSM-T3E3-155. You do not need to configure ports on the MPSM-16-T1E1 in the PPP mode; you work with MLPPP bundles instead.

For information about managing multilink Frame Relay ports and multilink PPP bundles, see the following sections:

• "Managing Multilink PPP Services" section

• "Managing Multilink Frame Relay Services" section

To modify a Frame Relay port, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 If you are in the ATM CLI context, enter the setctx fr command to change to the ATM CLI context, as shown in the following example

M8850_SF.27.MPSM16T1E1[ATM].a > setctx fr

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 To display all Frame Relay ports on the current MPSM, and to obtain the ifnum of the port you want to modify, enter the dspports command as follows.

M8850_SF.27.MPSM16T1E1[FR].a > dspports
ESR: Egress queue Service Ratio
SCT DS0 Port E FRF
If Line/Path Admn Oper if In Start Speed Signaling LMI 12
Num Num Stat Stat Type Use (Num) kbps ESR Type St Frg
---- ----------- ---- ---- ---- --- ------ ------ --- --------- --- ---
6 1.6 Up Up FR 0 1(24) 1536 1 None Off Off
11 1.1 Up Up FR 0 1(24) 1536 1 None Off Off
13 1.3 Up Up FR 0 1(24) 1536 1 None Off Off
14 1.4 Up Up FR 0 1(24) 1536 1 None Off Off
18 1.8 Up Up FR 0 1(24) 1536 1 None Off Off

Step 4 To modify the SCT used by the port, enter the dnport <ifNum> command to bring down the port you want to modify. Otherwise, skip this step.

In the following example, the user brings down the Frame Relay port 11:

M8850_SF.27.MPSM16T1E1[FR].a > dnport 113
Traffic loss will result on all frame relay connections on this card.
Do you want to proceed (Yes/No) ? y

Step 5 If you want to modify any of the connection-affecting parameters, you must delete any connections configured on the port. The connection-affecting parameters include:

•DLCI length

•Number of flags between frames

•Service ratio

•Checksum type indicator

•Oversubscription

To bring down any connections on the port you want to modify, enter the delcon <ifNum> <dlci> command. Replace <ifNum> with the interface number of the port you want to modify, and replace <dlci> with the DLCI of the connection you want to de-activate. Before deleting a connection, record connection parameters so you can easily add it later. Use the dspcon <ifNum> <dlci> command to display a connection.

Note Enter the dspcons command in the Frame Relay CLI context to see all connections associated with Frame Relay ports on the current card. The port ID and the DLCI number appear under the Identifier column in the dspcons command display. You need the port ID and the DLCI number to bring down

M8850_SF.27.MPSM16T1E1[FR].a > delcon 113 130
Admin state of connection is DOWN

Step 6 To modify port parameters, enter the cnfport command as follows:

M8850_SF.27.MPSM16T1E1[FR].a > cnfport <ifNum>
[-sct <sctID>] [-dlciLen <dlciLen>] [-flags <portFlagsBetweenFrames>] [-rat <PortEqueueServiceRatio>] [-csum <checksum>] [-oversub <overSubscribeEnable>] [-lmiSig <lmiSigType>] [-asynUpdt <updateType>] [-elmi <elmiState>] [-segLmi <segLmiStatus>] [-t391 <t391Value>] [-t392 <t392Value>] [-n391 <n391Value>] [-n392 <n392Value>] [-n393 <n393Value>] [-fragEnable <fragEnable>] [-fragSize <fragSize>} [-hdlcinv <hdlcinv>]

Table 6-15 describes the parameters for the cnfport command in the Frame Relay CLI context.

Table 6-15 Parameters for the cnfport Command—Frame Relay CLI Context

Parameter

Description

ifNum

Specifies the interface number (port number) of the port you are adding.

•MPSM-16-T1E1 range: 4-499

•MPSM-T3E3-155 range: 4-1003

Note Use the dspports command in the Frame Relay CLI context to see the port numbers for all active Frame Relay ports.

-sct

Specifies the number of a service class template (SCT) for the port, in the range 1-255.

Note Before you can change the port SCT, you must bring down the port using the dnport command.

-dlciLen

Specifies the DLCI header length:

•1 = 2-byte DLCI header

•2 = 4-byte DLC header

Note You cannot modify the DLCI header length while active connections exist on the port. Before you modify the -dlciLen parameter, enter the delcon command to delete any connections on the specified port.

-flags

Specifies the flags between frames:

•1 = 1 flag

•2 = 2 flags

•3 = 4 flags

•4 = 8 flags

•5 = 16 flags

•6 = 32 flags

•7 = 64 flags

•8 = 128 flags

Note You cannot modify the DLCI header length while active connections exist on the port. Before you modify the -flags parameter, enter the delcon command to delete any connections on the specified port.

-rat

This keyword and argument defines the egress service ratio between high priority and low priority queues.

Enter the keyword followed by a number that indicates the egress service ratio, in the range from 1 to 15.

•Enter 1 to indicate that no service ratio is configured. In this case, bandwidth is allocated to both the high priority and the low priority queues on demand, which means that traffic is dynamically allocated on a first-come, first-serve basis.

•The default setting is 1 which allocates the traffic of the CBR and rt-VBR service categories to the high priority queue, while the traffic of the nrt-VBR, ABR, and UBR service categories is allocated to the low priority queue.

Note You cannot modify the DLCI header length while active connections exist on the port. Before you modify the -rat parameter, enter the delcon command to delete any connections on the specified port.

-csum

Checksum type indicator:

•1 = crc16

•2 = crc32

Note You cannot modify the DLCI header length while active connections exist on the port. Before you modify the -csum parameter, enter the delcon command to delete any connections on the specified port.

-oversub

Oversubscription indicator:

•1 = enable

•2 = disable

Note You cannot modify the DLCI header length while active connections exist on the port. Before you modify the -oversub parameter, enter the delcon command to delete any connections on the specified port.

-lmiSig

LMI signaling type indicator:

•2 = No Signaling

•3 = StrataLMI

•4 = AnnexAUNI

•5 = AnnexDUNI

•6 = AnnexANNI

•7 = AnnexDNNI

Note When LMI is configured, the maximum number of connections per port for Strata LMI port is 560 and for Annex A/D UNI/NNI port is 898.

-asynUpdt

Enables or disables asynchronous updates. Asynchronous updates are an extension to the LMI protocol that notify the user immediately of changes in PVC and multicast status. Before enabling this feature, make sure that any DTE equipment you are connected to supports asynchronous updates from the network.

Asynchronous update control:

•1 = Disable both Asynchronous Status Updates and Unsolicited Full Status

•2 = Enable Asynchronous Status Updates

•3 = Enable Unsolicited Full Status

•4 = Enable Asynchronous Status Updates and Unsolicited Full Status

-elmi

Enable or disable enhanced LMI. Enhanced LMI enables the automatic exchange of Frame Relay QoS parameter information between the DTE and DCE. When enabled on both the DTE and the MPSM port, this allows the DTE device to learn QoS parameters from the frame relay port and use them for traffic shaping, configuration, or management.

•1 = enable

•2 = disable

-segLmi

Segmented LMI control:

•1 = enable

•2 = disable

-t391

T391 timer—Link Integrity Verification polling timer. The user (DTE) sends status inquiry messages to the network (DCE) every T391 seconds. An error is recorded if a status message is not received within T391 seconds. The T391 counter always applies to the user equipment. It applies to the user and network if NNI bidirectional polling is present. Range 5-30.

-t392

T392 timer—Polling Verification timer. The network (DCE) expects status inquiry messages from the user (DTE) every T392 seconds. If the network does not receive a status inquiry message from the user within T392 seconds and the timer expires, the network records a missing status inquiry message by incrementing the N392 counter. This timer value must be set greater than the T391 timer. The T392 timer always applies to the network. It applies to the network and user if NNI bidirectional polling is present. Range 5-30.

-n391

N391 counter. This setting establishes the Full Status (status of all PVCs) polling cycle. The user (DTE) sends a Full Report Status Enquiry to the network (DCE) every N391 polls. The N391 counter always applies to the user equipment. It applies to the user and network if NNI bidirectional polling is present. Range 1-255.

-n392

N392 counter—Specifies the UNI/NNI error threshold. This is the number of errors during N393 events that trigger an error condition. This counter should be less than or equal to the N393 counter. This counter can apply to both the user (DTE) and the network (DCE). Range 1-10.

-n393

N393 counter. This setting is the monitored UNI/NNI events count, which must be greater than the N392 counter. N392 errors during N393 events cause an error condition. If the N393 counter is set to a value much less than the N391 counter, the port could enter and exit error condition without notification to either the user equipment or the network. This counter can apply to both the user (DTE) and the network (DCE). The value of this parameter should be greater than that for the -n392 parameter. Range: 1-10.

-fragEnable

Controls fragmentation on the port.

•1=enable

•2= disable

-fragSize

Specifies the size of the fragments in bytes:

•40

•64

•128

•256

•512

-hdlcinv

Controls HDLCI NV on the port.

•1=enable

•2= disable

In the following example, the user enables oversubscription on port 11, DLCI 150:

M8850_SF.27.MPSM16T1E1[FR].a > cnfport 113 -oversub 1

Step 7 If you brought down a port in Step 4 using the dnport command, enter the upport <ifNum> command as follows to re-activate that port. Replace <ifNum> with the interface number of the port you want to activate. Otherwise, skip this step.

M8850_SF.27.MPSM16T1E1[FR].a > upport 113

Step 8 If you brought down a connection in Step 5 using the addcon command, specify the parameters of the connection you previously deleted. Otherwise, skip this step.

In the following example, the user activates the connection on port 30, DLCI 100:

M8850_SF.27.MPSM16T1E1[FR].a > addcon 113 130 1 1 1 1536000 -slave 47009181000000000164444B610000011B1FFF00.28.150
master endpoint added successfully
master endpoint id : 47009181000000000164444B610000011B1FFF00.224.130

Step 9 To verify the configuration of the modified port, enter the dspport <ifNum> command. Replace <ifNum> with the interface number of the port you modified.

M8850_SF.27.MPSM16T1E1[FR].a > dspport 113
Interface Number : 113
Line Number : 1.13
DS0 Speed : 64 Kbps
DS0 Configuration Bit Map : 1(24)
Admin State : Up
Operational State : Up
Port State : Active
Port Signaling State : No Signaling Failure
Interface Type : Frame Relay
SCT Id : 0/0 =Def
Frame Header Length : Two Bytes
Flags Between Frames : 1
Equeue Service Ratio : 1
Port Speed : 1536 kbps
Checksum type : crc16
Over-subscription : Enabled
Signaling Protocol Type : None
Enhanced LMI : Disabled
FRF 1.2 Support : Disabled
Asynchronous Updates : Disabled
T391 Link Integrity Timer : 10 secs
T392 Polling Verification Timer : 15 secs

Type <CR> to continue, Q<CR> to stop:
N391 Full Status Polling Counter : 6
N392 Error Threshold : 3
N393 Monitored Event Count : 4
FRF.12 Fragmentation : Disabled
FRF.12 Fragment Size : 64 Bytes
Port HDLC Frame Inversion : Disabled
Number of Partitions : 1
Number of SPVC : 1

Deleting Ports

Use the delport command to delete ATM and Frame Relay ports from an MPSM-T3E3-155 or MPSM-16-T1E1 card, or a multilink Frame Relay port from an MPSM-T3E3-155 card.

Before you can delete a port, the following conditions apply:

•You must be in the CLI context that corresponds to the port type to delete, either ATM or Frame Relay.

•You must delete active connections associated with the port you want to delete.

•You must disable signaling on the port. Enter the dsppnportsig command on the PXM to see if signaling is disabled or enabled on the port.

Deleting an ATM Port

To delete an ATM port on a card, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 If you are in the Frame Relay CLI context, enter the setctx atm command to change to the ATM CLI context, as shown in the following example:

M8830_CH.12.MPSM155[FR].a > setctx atm

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 To display all ATM ports on the current card, and to obtain the ifnum of the port you want to delete, enter the dspports command as follows.

M8850_SF.27.MPSM16T1E1[ATM].a > dspports
ifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IMA
Path State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GRP
VUNI) EVNNI) EVNNI)
----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- ---
12 1.2 Up Up 3622 3622 0/ 0 =Def NNI 0 0 0 N/A

The interface number for each port appears in the ifNum column.

Step 4 If connections are associated with the port you want to delete, enter the delcon <ifNum> <vpi> <vci> command to delete them. Replace the <ifNum> <vpi> <vci> parameters with the interface number, VPI, and VCI of the port you want to delete.

Note To display the vpi and vci for a specific port (ifNum), enter the dspcons command. This information is in the Identifier column in the display.

In the following example, the user displays all connections on the current MPSM, and deletes the connection on port 12 with a VPI of 35 and a VCI of 120.

M8850_SF.27.MPSM16T1E1[ATM].a > dspcons
record Identifier Type SrvcType M/S Upld Admn Alarm
------ ---------- ---- -------- --- ---- ---- -----
1 12 0035 00120 VCC cbr1 S 0000001b UP none

M8850_SF.27.MPSM16T1E1[ATM].a > delcon 12 35 120
Deletion successful

Step 5 To delete a specific port, enter the delport <ifNum> command. Replace <ifNum> with the interface number for the port you want to delete.

Note To view the interface numbers for all ATM ports on the current card, enter the dspports command.

In the following example, the user deletes port 12 from the current card:

M8850_SF.27.MPSM16T1E1[ATM].a > delport 12

Step 6 Verify that the appropriate port is deleted by entering the dspports command.

Deleting a Frame Relay Port

To delete a Frame Relay port on a card, use the following procedure.

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 If you are in the ATM CLI context, enter the setctx fr command to change to the ATM CLI context, as shown in the following example:

M8850_SF.27.MPSM16T1E1[ATM].a > setctx fr

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 Enter the dspports command as follows to display all Frame Relay ports on the current card, and to obtain the ifnum of the port you want to delete.

M8850_SF.27.MPSM16T1E1[FR].a > dspports
ESR: Egress queue Service Ratio
SCT DS0 Port E FRF
If Line/Path Admn Oper if In Start Speed Signaling LMI 12
Num Num Stat Stat Type Use (Num) kbps ESR Type St Frg
---- ----------- ---- ---- ---- --- ------ ------ --- --------- --- ---
11 1.1 Up Up FR 0 1(24) 1536 1 None Off Off
13 1.3 Up Up FR 0 1(24) 1536 1 None Off Off
14 1.4 Up Up FR 0 1(24) 1536 1 None Off Off
18 1.8 Up Up FR 0 1(24) 1536 1 None Off Off

The interface number for each port appears in the ifNum column.

Step 4 If connections are associated with the port you want to delete, enter the delcon <ifNum> <dlci> command to delete them. Replace the <ifNum> <dlci> parameters with the port number and the DLCI of the port you want to delete.

Note To obtain the DLCI for a specific port (ifNum), consult the Identifier column in the dspcons command display.

In the following example, the user displays all connections on the current card, and deletes the connection on port 10 that has a DLCI of 200.

MM8850_SF.27.MPSM16T1E1[FR].a > dspcons
record Identifier SrvcType M/S Upld Admn Alarm
------ ---------- -------- --- ---- ---- ---------------------
0 11 0000150 High Priority M 00000021 UP None

M8850_SF.27.MPSM16T1E1[FR].a > delcon 11 150
Deletion successful

Step 5 To delete a specific port, enter the delport <ifNum> command. Replace <ifNum> with the interface number for the port you want to delete.

Note To view the interface numbers for all Frame Relay ports on the current MPSM, enter the dspports command.

In the following example, the user deletes port 11 from the current card:

M8850_SF.27.MPSM16T1E1[FR].a > delport 11

Step 6 Verify that the appropriate port is deleted by entering the dspports command.

Managing Multilink Frame Relay Services

This section explains how to manage multilink Frame Relay (MFR) services on the MPSM-T3E3-155 card, in the following sections:

• Managing MFR Bundles

• Managing MFR Links

• Managing Ports

• Deleting Bundles, Links, and Ports

Managing MFR Bundles

This section explains how to display and configure MFR bundles.

Displaying Bundles

To display summary and detail MFR bundle information, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Change to the MPSM-16-T1E1 card using the cc command.

Step 3 To list all MFR bundles configured on the current card, enter the dspmfrbundles command.

M8850_SF.10.MPSM155[FR].a > dspmfrbundles
Mfr Activation Minimum Configured Active Admin Oper Max Diff
Bundle Class Links Links Links State State Delay
------------------------------------------------------------------------------
1 A 1 4 4 Up Up 300
2 A 1 4 4 Up Up 300
4 C 2 2 0 Up Down 300
5 C 2 2 0 Up Down 300

Table 6-16 describes the bundle display.

Table 6-16 dspmfrbundles Display

Column

Description

MFRBundle

The bundle number.

Activation Class

•Class A—At least one bundle link must be operational for the MFR bundle to be operational

•Class B—All of the bundle links must be operational for the MFR bundle to be operational

•Class C—Configured number of bundle links must be operational for the MFR bundle to be operational

Minimum Links

Minimum number of links for the bundle to be operational.

Configured Links

Number of links configured on the bundles.

Active Links

Number of active links.

Admin State

Admin state, as controlled by upmfrbundle and dnmfrbundle.

Oper State

Up—The MFR bundle is negotiated and accepted, and the minimum number of links are operational.

Down—The following are possible causes for a bundle to be down:

•Bundle is in admin down state

•Insufficient or no links in this bundle are operational

•Insufficient or no links are added to this bundle

Max Diff Delay

The maximum differential delay in the bundle.

Step 4 To display detailed configuration and operational information for a specific MFR bundle, enter the dspmfrbundle <bundleNum> command, specifying the number of the bundle you want to display.

M8850_SF.10.MPSM155[FR].a > dspmfrbundle 1
Bundle Number : 1
Activation Class : A
Minimum Links : 1
Admin state : Up
Oper State : Up
Hello Timer (seconds) : 10
Ack Timer (seconds) : 4
Max Retry Count : 2
Maximum Bundle Links : 12
Configured Number of Links : 4
Active Number of Links : 4
Available Bandwidth : 6176000
Near End Bundle Name : M8850_SF.Slot10.Bundle01
Far End Bundle Name : M8850_SF.Slot10.Bundle02

Configuring an MFR Bundle

To configure an MFR bundle, perform the following steps:

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a username with Group1 privileges or higher.

Step 2 Enter the dspmfrbundles command to list the MFR bundles configured on the current card.

Step 3 If the MFR bundle is administratively up, bring it down by entering the dnmfrbundle <bundleNum> command.

Step 4 Configure MFR bundle parameters using the cnfmfrbundle command.

M8850_SF.9.MPSM155[FR].a > cnfmfrbundle -bundle <bundleNum> [-class <activationclass>] [-minlinks <minimumlinks>] [-hellotimer <hellotimer>] [-acktimer <acktime>] [-maxretry <maxretry>] [-bname <bundleName>]

Table 6-17 describes cnfmfrbundle command parameters.

Table 6-17 cnfmfrbundle Command Parameters

Parameter

Description

-bundle

MFR bundle number, range 1-42

-class

Bundle activation class:

•1 = Class A—At least one bundle link must be operational for the MFR bundle to be operational

•2 = Class B—All of the bundle links must be operational for the MFR bundle to be operational

•3 = Class C—Configured number of bundle links must be operational for the MFR bundle to be operational

-minlinks

Minimum number of links for class-C activation class. Range 1-12

-hellotimer

Interval for sending hello messages. Range 1-180 seconds

-acktimer

Maximum time period to wait for an acknowledgement from the far en. Range 1-10 seconds

-maxretry

Maximum number of retries (maximum retries). Range 1-5 retries

-bname

Near-end bundle name:

A null-terminated string consisting of ASCII characters A-Z, a-z, 0-9, and any printable characters, with a maximum of 49 characters.

In the following example, the user increases the minimum number of links for a Class C MFR bundle to 4 and sets the maximum number of retries to 4.

M8850_SF.9.MPSM155[FR].a > dnmfrbundle 4
M8850_SF.9.MPSM155[FR].a > cnfmfrbundle -bundle 4 -minlinks 4 -maxretry 4

Step 5 Restore the bundle to the administrative up state by entering the upmfrbundle <bundleNum> command.

Step 6 To verify MFR bundle configuration, enter the dspmfrbundle <bundleNum> command, specifying the number of the bundle you want to display.

M8850_SF.10.MPSM155[FR].a > dspmfrbundle 4
Bundle Number : 4
Activation Class : C
Minimum Links : 4
Admin state : Up
Oper State : Down
Hello Timer (seconds) : 10
Ack Timer (seconds) : 4
Max Retry Count : 4
Maximum Bundle Links : 12
Configured Number of Links : 0
Active Number of Links : 0
Available Bandwidth : 0
Near End Bundle Name : M8850_SF.Slot10.Bundle04
Far End Bundle Name : <not defined>

Managing MFR Links

This section explains how to display, configure, add and delete MFR links.

Displaying Links

To display summary and detail MFR link information, perform the following procedure:

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a username with Group1 privileges or higher.

Step 2 List all MFR links configured on the current card by entering the dspmfrlnks command.

M8850_SF.10.MPSM155[FR].a > dspmfrlnks
Link Bundle Link Link Alarm Link PHY Oper
Num Num State State Delay(ms) State
------------------------------------------------------------------
1.1:3 1 Up Clear 21 Up
1.1:4 1 Up Clear 20 Up
1.1:5 1 Up Clear 20 Up
1.1:6 1 Up Clear 20 Up
1.2:3 2 Up Clear 20 Up
1.2:4 2 Up Clear 20 Up
1.2:5 2 Up Clear 20 Up
1.2:6 2 Up Clear 20 Up

Table 6-18 describes the display.

Table 6-18 dspmfrlnks Display

Column

Description

Link Num

Link (path id) for the link.

Bundle Num

Number of the bundle of which the link is a member.

Link State

Current state of link activation.

Link Alarm State

Link alarm, if any.

Link Delay

Link delay, in ms.

PHY Oper State

Up—MFR link is negotiated and accepted.

Down—MFR link is not negotiated nor accepted.

Step 3 To display detail configuration and operational information for a specific MFR link, enter the dspmfrlnk <link> command, specifying the number of the link you want to display.

M8850_SF.10.MPSM155[FR].a > dspmfrlnk 1.1:3
Link Number : 1.1:3
Bundle Number : 1
Link State : Up
Link Alarm State : Clear
Link Delay (Rtt in msec) : 21
Link Near End Name : M8850_SF.Slot10.Link03
Link Far End Name : M8850_SF.Slot10.Link31
Link Far End Bundle Name : M8850_SF.Slot10.Bundle02
Link PHY Operational Status : Up

Configuring MFR Links

Links have a default near-end name in the format node.slot.link, for example M8850_SF.Slot10.Link11.

To rename a link, perform the following steps.

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a username with Group1 privileges or higher.

Step 2 Reconfigure the link by entering the cnfmfrlnk command.

M8850_SF.10.MPSM155[FR].a > cnfmfrlnk -link <lnkNum> -lname <linkname>

Table 6-19 describes cnfmfrlnk command parameters.

Table 6-19 cnfmfrlnk Command Parameters

Parameter

Description

-link

Link identifier:

•DS3 payload: bay.line.sts:ds1

•VT payload: bay.line.sts:vtg.vt

•VT structured: bay.line.sts:tug3.vtg.vt

where: bay = 1, line = 1-3, sts = 0-3, ds1 = 1-28,
tug3 = 1-3, vtg = 1-7, vt = 1-4 (VT15) or 1-3(VT2)

-lname

Near-end link name:

A null-terminated string consisting of ASCII characters A-Z, a-z, 0-9, and any printable characters with a maximum of 49 characters.

In the following example, the user changes the MFR link name to M8850_SF.Slot09.Bundle04.Link11.

M8850_SF.9.MPSM155[FR].a > cnfmfrlnk -link 1.1.1:1 -lname M8850_SF.Slot09.Bundle04.Link11

Step 3 To verify MFR link configuration, enter the dspmfrlnk <lnkNum> command.

M8850_SF.10.MPSM155[FR].a > dspmfrlnk 1.1:11
Link Number : 1.1:11
Bundle Number : 4
Link State : Down
Link Alarm State : Other
Link Delay (Rtt in msec) : 0
Link Near End Name : M8850_SF.Slot09.Bundle04.Link11
Link Far End Name : <not defined>
Link Far End Bundle Name : <not defined>
Link PHY Operational Status : Down

Adding or Removing Links

You can add or remove links from an operational bundle to change the bundle bandwidth. To add a link to a MFR bundle, enter the addmfrlnk <link> <bundleNum> command. The link becomes operational after successful negotiation with the remote end. For more information about adding links, see the "Adding Links to an MFR Bundle" section on page 4-39.

To delete a link, enter the delmfrlnk <link> command. Deleting a link sends a remove-link request message to the far-end of the link. The bundle stops transmitting data on the link after the remove-link request has been sent. However, data received on the link is processed until the acknowledgement for the remove-link request is received.

Note A Class C bundle becomes inoperative if the number of links drops below the minimum number.

Managing Ports

To manage MFR ports, use the same commands used for Frame Relay ports. To manage MFR ports, refer to the following Frame Relay Sections sections:

• Displaying the Status of One Port

• Modifying a Frame Relay Port

• Deleting Ports

Deleting Bundles, Links, and Ports

MRF bundles, links, ports and connections are interdependent, so you must delete these components in the reverse order that you created them.

To delete an MFR bundle, link, or port, perform the following steps.

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a username with Group1 privileges or higher.

Step 2 Delete the MFR port by entering the delport <ifNum> command. You must delete the connection to the port before deleting the port.

Step 3 Delete all MFR links by entering the delmfrlnk <link> command. You must delete the port before deleting the last link.

Step 4 Delete the MFR bundle by entering the delmfrbundle <bundleNum> command. You must delete all links from the bundle before deleting the bundle.

Step 5 To verify the deletion of ports, links, or bundles, enter the dspports, dspmfrlnks, or dspmfrbundles commands respectively.

Managing Multilink PPP Services

This section explains how to manage multilink PPP (MLPPP) services on the MPSM-16-T1E1 and MPSM-T3E3-155 cards, in the following sections:

• Managing Bundles

• Managing PPP Links

• Managing PPPMUX

• Deleting MLPPP Bundles, Links, and PPPMUX

• Displaying Statistics

Managing Bundles

This section explains how to display and configure MLPPP bundles.

Displaying MLPPP Bundles

To display summary and detail MLPPP bundle information, perform the following procedure:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command.

Step 3 To list all MLPPP bundles configured on the current card, enter the dspmpbundles command.

M8850_SF.9.MPSM155PPP[FR].a > dspmpbundles
MLPPP Admin Oper Active Available Alarm MUX AutoBW WP
Bundle State State Links Bandwidth Cause Status Mode Id
-------------------------------------------------------------------------------
1 Up Up 2 512000 No Alarm Disable Enable 1
2 Up Up 2 3968000 No Alarm Disable Enable 2
3 Up Up 3 5952000 No Alarm Disable Enable 1

Note WP Id is displayed for the MPSM-T3E3-155 only.

Table 6-20 describes the information displayed.

Table 6-20 dspmpbundles Display

Column

Description

MLPPP Bundle

Bundle number.

Admin State

Administrative state, as controlled by upmpbundle and dnmpbundle.

Oper State

Operational state:

•Up—The MLPPP is negotiated and accepted. At least one link is operational in this MLPPP bundle.

•Down—The following are possible causes for an MLPPP bundle to be down:

–Bundle is in admin down state

–No link in this bundle is operational

–No links are added to this bundle

–PPP LCP negotiation with remote end failed on all links in this bundle

–MLPPP LCP negotiation with remote end failed on all links in this bundle

Active Links

Number of operational links in the bundle.

Available Bandwidth

Aggregate bandwidth of the bundle.

Alarm Cause

Cause of the alarm for the bundle, if any.

MUX Status

State of PPPMUX for the bundle, either Enable or Disable.

Auto BW Mode

State of the dynamic bandwidth feature for bundle, either Enable or Disable.

WP Id

Winpath packet processing engine assigned to the bundle.
(MPSM-T3E3-155 only)

Step 4 To display detailed configuration and operational information for a specific MLPPP bundle, enter the dspmpbundle <bundleNumber> command, specifying the number of the bundle you want to display.

M8850_SF.9.MPSM155PPP[FR].a > dspmpbundle 3
Bundle Number : 3
Admin State : Up
Oper State : Up
Alarm Cause : No Alarm
MRRU : 1524
SeqNumFormat : 24 bit
Fragmentation : Disable
EndpointDiscrimClass : 2
EndpointDiscriminator : M8850_SF.9.3
LinksConfigured : 3
LinksActive : 3
RemoteMRRU : 1524
RemoteEndpDiscrimClass : 2
RemoteEndpDiscriminator : M8830_SF.6.3
Configured Bandwidth : 5952000
Available Bandwidth : 5952000

Step 5 To display MLPPP bundle QoS configuration information, enter the dspmpbundleparams <bundleNumber> command, specifying the number of the bundle you want to display.

M8850_SF.9.MPSM155PPP[FR].a > dspmpbundleparams 1

MP Bundle (1) HW Parameters
-----------------------------
Queue[0] Threshold : 100
Queue[1] Threshold : 100
Queue[2] Threshold : 100
Normalized PVC Bandwidth : 8600
AutoBandwidth Mode : Enable

Configuring MLPPP Bundles

To change the configuration of an existing MLPPP bundle, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command.

Step 3 Configure an MLPPP bundle using the cnfmpbundle command.

M8850_SF.9.MPSM155PPP[FR].a > cnfmpbundle -bundle <bundleNumber> [-mrru <value>] [-endDisc <value>]

Table 6-21 describes the parameters for the cnfmpbundle command.

Table 6-21 cnfmpbundle Command Parameters

Parameter

Description

-bundle

Specifies the MLPPP bundle number.

Note Enter the dspmpbundles command to display all MLPPP bundles on the card.

-mrru

Specifies the Max Received Reconstructed Unit (MRRU), in the range 64 - 1524.

After the user adds a link to an MLPPP bundle, the MRRU is sent to the remote end, which notifies the remote end that this link is capable of receiving MLPPP packets.

-endDisc

Describes the bundle endpoint. The value is null terminated string that contains printable ASCII characters, which include A-Z, a-z, and 0-9. Maximum length: 20 characters.

The following example changes the MRRU of bundle 2 to 64.

M8850_SF.9.MPSM155PPP[FR].a > cnfmpbundle -bundle 2 -mrru 64
Warning: Bundle Config is being changed, traffic might be interrupted briefly

Step 4 Verify the MLPPP bundle configuration using the dspmpbundle commands. See the "Displaying MLPPP Bundles" section.

Configuring Bundle QoS

You can customize Layer 2 QoS queues and configure PVC bandwidth control using the cnfmpbundle command. The MPSM enforces Layer 2 QoS in the RPM-XF to MPSM direction using the following queues:

•Q0—Queues high-priority traffic, such as voice.

•Q1—Queues important traffic, such as control packets

•Q2—Queues all other traffic

The RPM-XF defines the target queue when it passes data to the MPSM. Because these are strict priority queues, high-priority traffic can delay low-priority traffic if the RPM-XF sends data to the bundle faster than the bundle can send it out. To avoid this problem, the dynamic bandwidth feature (auto-bw) automatically limits the PVC bandwidth between the RPM-XF and MPSM to a value less than the bundle bandwidth.

When recomputing the PVC bandwidth, the MPSM considers:

•Operational bundle bandwidth

•Normalized PVC bandwidth (normpvcbw) parameter

The normalized PVC bandwidth represents the cells/sec that a single T1/E1 span generates. Set this value according to the traffic model, the voice and data payload size, the bundle utilization, and the multiplex factor in your network.

If you disable the dynamic bandwidth feature, you must manually provision the PVC bandwidth between the RPM-XF and MPSM to a value somewhat less than the MLPPP bundle bandwidth. Any subsequent change you make to bundle bandwidth, such as adding a PPP link, requires reprovisioning of the PVC bandwidth.

To configure MLPPP bundle parameters, perform the following steps:

Step 1 Establish a configuration session using a username with GROUP1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command.

Step 3 Enter the cnfmpbundleparams command to configure the bundle, specifying the bundle number and desired parameters.

M8850_SF.25.MPSM16T1E1PPP[FR].a > cnfmpbundleparams -bundle <bundleNumber> [-q0threshold <value>] [-q1threshold <value>] [-q2threshold <value>] [-normpvcbw <value>] [-autobw <value>]

Table 6-22 describes the parameters for the cnfmpbundleparams command.

Table 6-22 cnfmpbundleparams Command Parameters

-bundle

Specifies the MLPPP bundle number.

Enter the dspmpbundles command to display all MLPPP bundles on the card.

-q0threshold

Q0 threshold, range 0 - 65535 packets

Default: 100

-q1threshold

Q1 threshold, range 0 - 65535 packets

Default: 100

-q2threshold

Q2 threshold, range 0 - 65535 packets

Default: 100

-normpvcbw

Normalized PVC bandwidth, range 0 - 176603 cps

Default: 8600 cps

-autobw

Auto PVC bandwidth mode. When enabled, the bundle automatically negotiates the bandwidth on connections to the RPM-XF.

•1 = enable

•2 = disable

The following example shows how to disable the automatic bandwidth feature on bundle 2.

M8850_SF.27.MPSM16T1E1PPP[FR].a > cnfmpbundleparams -bundle 2 -autobw 2

Step 4 Verify the MLPPP bundle configuration using the dspmpbundleparams commands. See the "Displaying MLPPP Bundles" section.

Managing PPP Links

This section explains how to display, configure, add, and delete MLPPP links.

Displaying PPP Links

To display MLPPP link information, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command.

Step 3 To list all MLPPP links configured on the current card, enter the dspppplinks command.

M8850_SF.27.MPSM16T1E1PPP[FR].a > dspppplinks
Link Admin Oper Start Number Bundle Bay.Line PPP Link
Number State State DS0 of DS0 Number Number Description
-------------------------------------------------------------------------------
1 Up Up 2 31 1 1.1 LineSide
2 Up Up 2 31 1 1.2 LineSide
3 Up Up 2 31 1 1.3 LineSide
4 Up Up 2 31 1 1.4 LineSide
5 Up Up 2 31 5 1.5 LineSide
6 Up Up 2 31 5 1.6 LineSide
7 Up Up 2 31 5 1.7 LineSide
8 Up Up 2 31 5 1.8 LineSide
13 Up Up 2 31 13 1.13 LineSide
14 Up Up 2 31 13 1.14 LineSide
15 Up Up 2 31 13 1.15 LineSide
16 Up Up 2 31 13 1.16 LineSide
512 Up Up 1 0 1 N/A SwitchSide
516 Up Up 1 0 5 N/A SwitchSide
524 Up Up 1 0 13 N/A SwitchSide

Table 6-23 describes the link display.

Table 6-23 dspppplinks Display

Column

Description

Link Number

PPP link number.

Admin State

Administrative state of the link, as controlled by upppplink and dnppplink.

Oper State

The operational state of the link.

•up—The PPP is negotiated and accepted, and there are no other alarms on this PPP link.

•down—Possible causes for PPP to be in a down state:

–Physical layer is in alarm

–PPP LCP negotiation with remote end failed on this link

Start DS0

The first DS0 in the link.

Number DS0

Number of DS0s in the link.

Bundle Number

Bundle to which the link is a member.

Bay.Line Number or Path ID

The link identifier:

•MPSM-16-T1E1—The line number, in the format bay.line.

•MPSM-T3E3-155—The path identifier for a channelized line.

PPP Link Description

The type of link:

•LineSide—Identifies line-side links that were manually added to the bundle.

•SwitchSide—Identifies switch-side links, which the MPSM automatically creates for the bundle.

Step 4 To display detailed configuration and operational information for a specific MLPPP link, enter the dspppplink <linkNumber> command, specifying the number of the link you want to display.

M8850_SF.25.MPSM16T1E1PPP[FR].a > dspppplink 1
PPP Link ID : 1
AdminStatus : Up
OperState : Up
Fail Reason : NoAlarm
BundleID : 1
PhysicalLineID : 1.1
DS1LinkStartDS0 : 2
DS1LinkNumDS0 : 12
DS1Link56KbpsMode : Disable
MRU : 1234
LcpTimeout : 10000
LcpLoopCheck : Disable
RemoteMRU : 1234
PFCReceive : Enable
ACFCReceive : Enable
PFCTransmit : Enable
ACFCTransmit : Enable
PFCTransmitOper : Enable
ACFCTransmitOper : Enable
LinkDescriptor : LineSide
RestartTimer : 3000
MaxConfigReqRetry : 10

Configuring PPP Links

To configure an individual PPP link, perform the following steps

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command.

Step 3 Configure a PPP link using the cnfppplink command as follows:

mpsm_node1.2.MPSM16T1E1[ATM].a > cnfppplink -link <LinkId> [-mru <MRU> -lcptimeout <LCPTimeout> -ds0speed <ds0speed> -pfcTx <PFC> -acfcTx <ACFC> -lpbkCheck <loopCheck>]

Table 6-24 describes cnfppplink command parameters.

Table 6-24 cnfppplink Command Parameters

Parameter

Description

-link

Specifies the PPP link number.

Enter the dspppplinks command to display all PPP links on the card.

-mru

The Maximum Receive Unit, in the range 64-1524

-lcpTimeout

The length of time to wait for a Echo Reply before bringing down LCP. The value is in msec, rounded down to the nearest 100 msec. Range 1000-4294967.

-ds0speed

DS0 Speed

•1 = 56K

•2 = 64K

-pfcTx

Controls the compression of PF in PPP packets transmitted from this end.

•1 = enable, PFC is performed if the far end is capable of receiving compressed PF.

•2= disable, PFC is not performed, even if far end is capable of receiving compressed PF.

-acfcTX

Controls the compression of address/control fields in PPP packets transmitted from this end.

•1 = enable, ACFC is performed if the far end is capable of receiving compressed address/control fields.

•2 = disable, ACFC is not performed, even if far end is capable of receiving compressed address/control fields.

-loopCheck

Controls loopback check. If loopback check is enabled, when the magic number in the incoming echo reply is the same as of this PPP link, then this PPP link assumes that the far end is in loopback and brings down its own LCP session.

•1 = Enable

•2 = Disable

In the following example, the user configures PPP link 1 with an MRU value of 1234, PFC transmit disabled, and ACFC transmit enabled.

M8850_SF.27.MPSM16T1E1PPP[FR].a > cnfppplink -link 1 -mru 1234 -acfcTx 1 -pfcTx 1

Step 4 To verify PPP link configuration, use the dspppplinks or dspppplink command. See the "Displaying PPP Links" section.

Adding or Removing Links

You can add or remove links from an operational bundle to change the available bandwidth. To add a link to a MLPPP bundle, use the addppplink command. The link becomes operational after successful negotiation with the remote end. For more information about adding links, see the "Adding Links to an MLPPP Bundle" section on page 5-5.

To delete a link, enter the delppplink <link> command. Deleting a link sends a remove-link request message to the far-end of the link. The bundle stops transmitting data on the link after the remove-link request has been sent. However, data received on the link is processed until the acknowledgement for the remove-link request is received.

Managing PPPMUX

This section explains how to display, enable, or disable the PPPMUX feature.

Displaying PPPMUX

To display PPPMUX information, perform the following procedure:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command

Step 3 To display the operational status of PPPMUX by bundle, enter the dspmpbundles command. The MUX Status column shows the MUX status for each bundle.

M8850_SF.27.MPSM16T1E1PPP[FR].a > dspmpbundles
MLPPP Admin Oper Active Available Alarm MUX AutoBW
Bundle State State Links Bandwidth Cause Status Mode
-------------------------------------------------------------------------------
1 Up Up 1 1984000 No Alarm Disable Disable
5 Up Up 4 7936000 No Alarm Enable Enable
13 Up Up 4 7936000 No Alarm Enable Enable

Step 4 To display PPPMUX information for a specific bundle, enter the dsppppmux <bundleNumber> command.

M8850_SF.27.MPSM16T1E1PPP[FR].a > dsppppmux 5
Mux Bundle Number : 5
Mux Protocol Status : Active
MuxEnable State : Enable
MuxOperStatus : OperUp
DeMuxEnable State : Enable
DeMuxOperStatus : OperUp
DeMuxPID : 33
DeMuxRemotePID : 33
MuxTimer : 600
MuxMaxSubFrameLength : 64
MuxMaxSubFrameCount : 15
MuxMaxFrameLength : 256

Configuring PPPMUX

To configure PPPMUX, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command

Step 3 To configure multiplexer parameters, enter the cnfpppmux command as follows.

M8850_SF.27.MPSM16T1E1PPP[FR].a > cnfpppmux -bundle <bundleNumber> [-pid <pid> -muxTimer <muxtimer> -frameLength <length> -subFrameLength <length> -subFrameCount <count>]

Table 6-25 describes the parameters for the cnfpppmux command.

Table 6-25 cnfpppmux Command Parameters

Parameter

Description

-bundle

Specifies the MLPPP bundle number for which to configure PPPMUX.

Note Enter the dspmpbundles command to display all MLPPP bundles on the card.

-pid

Default Protocol ID, in the range 0-65535

-muxTimer

Specifies the maximum length of time that the hardware multiplexes packets after multiplexing begins.

Values: 0 (disabled), or 64-4000000 microseconds

-frameLength

Maximum mux frame length, in the range 1-512

-subFrameLength

Maximum sub-frame length, in the range 1-512

-subFrameCount

Maximum number of sub-frames in a multiplex super-frame, in the range 2-15.

In the following example, the user configures the multiplex timer on bundle 2 to 64.

M8850_SF.27.MPSM16T1E1PPP[FR].a > cnfpppmux -bundle 5-muxTimer 64

Step 4 To verify PPPMUX configuration, enter the dsppppmux command. See the "Displaying PPPMUX" section

Enabling or Disabling PPPMUX

To enable or disable PPPMUX on a MLPPP bundle, enter the addpppmux command. For more information, see "Adding PPPMUX to an MLPPP Bundle" section on page 5-9.

To disable PPPMUX on an MLPPP bundle, enter the delpppmux <bundleNumber> command, specifying the number of the bundle.

Deleting MLPPP Bundles, Links, and PPPMUX

MLPPP bundles, links, PPPMUX, and connections are interdependent, so you must delete them in the reverse order that you created them.

Use the following procedure to delete an MLPPP bundle, link, and port.

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command

Step 3 Delete PPPMUX on a bundle by entering the delpppmux <bundleNumber> command.

Step 4 Delete MLPPP links by entering the delppplnk <link> command. Before deleting the last link, you must delete existing connections to the bundle.

Step 5 Delete the MLPPP bundle by entering the delmpbundle <bundleNumber> command. Before deleting the bundle, you must delete all links on the bundle.

Step 6 To verify the deletion of PPPMUX, MLPPP links, and bundle, enter the dspppplinks and dspmpbundles commands. See the "Displaying MLPPP Bundles" section and the "Displaying PPP Links" section.

Displaying Statistics

This section explains how to display bundle, link, and PPPMUX statistics.

Displaying MLPPP Bundle Statistics

The MPSM collects PPP link statistics for PPP sessions between MPSM cards and MWR routers. These statistics consist of 96 buckets of 15-minute interval statistics, for a total of 24 hours of statistics.

To view MLPPP bundle statistics, perform the following procedure:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command

Step 3 Display MLPPP bundle statistics for the desired interval using the dspmpbundlecnt <bundleNumber> <intvl> command, specifying the bundle number and desired 15-minute interval number.

The following example shows how to display statistics for interval 1 of bundle 5.

M8850_SF.27.MPSM16T1E1PPP[FR].a > dspmpbundlecnt 5 1
MLPPP Bundle Number : 5
Interval Number : 1

Receive Packets : 1620
Receive Bytes : 88380
Receive Discard Bytes : 0
Receive MRRU Error Packets : 0
Receive Discard Packets : 0
Receive FCS Error Packets : 0
Send Packets : 1620
Send Bytes : 88380

Table 6-26 lists the bundle statistics displayed. The send direction is towards the line.

Table 6-26 MLPPP Bundle Statistics

Counter

Description

Receive Packets

The number of frames received

Receive Bytes

The number of bytes received

Receive Discard Bytes

The number of bytes discarded for any error

Receive MRRU Errors

The number of MRRU error packets

Receive Miscellaneous Errors

The number of packets with miscellaneous errors

Receive FCS Error packets

The number of packets with FCS errors (MPSM-16-T1E1 only)

Send Packets

The number of packets transmitted on this bundle

Send Bytes

The number of bytes transmitted on this bundle

Step 4 To clear statistics for a bundle, enter the clrmpbundlecnt <bundleNumber> command, specifying the bundle number to clear.

Displaying PPP Link Statistics

The MPSM collects PPP link statistics for PPP Sessions between MPSM and MWR. These statistics consist of 96 buckets of 15-minute interval statistics, for a total of 24 hours of statistics.

To view PPP link statistics, perform the following procedure:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command

Step 3 Display statistics for the desired link using the dspppplnkcnt <link> <intvl> command, specifying the link number and desired 15-minute interval number.

The following example displays statistics for interval 0 of link 1.

M8850_SF.27.MPSM16T1E1PPP[FR].a > dspppplnkcnt 1 0
MLPPP Link Number : 1
Interval Number : 0

Receive Packets : 164
Receive Bytes : 2296
Receive Discard Bytes : 0
Receive MRU Errors : 0
Receive FCS Error Packets : 0
Receive Miscellaneous Errors : 0
Send Packets : 164
Send Bytes : 2296

Table 6-27 lists the PPP link statistics displayed. The send direction is towards the line.

Table 6-27 PPP Link Statistics

Counter

Description

Receive Packets

The number of frames received

Receive Bytes

The number of bytes received

Receive Discard Bytes

The number of bytes discarded for any error

Receive MRU Errors

The number of MRRU Error Packets

Receive Discard Packets

The number of packets discarded for any error

Receive FCS Error packets

The number of packets with FCS errors (MPSM-16-T1E1 only)

Send Packets

The number of packets transmitted on this bundle

Send Bytes

The number of bytes transmitted on this bundle

Step 4 To clear PPP statistics for a link, enter the clrppplnkcnt <link> command, specifying the link number to clear.

Displaying PPPMUX Statistics

To view PPPMUX statistics, perform the following procedure:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command

Step 3 Display statistics for the desired link using the dsppppmuxcnt <link> <intvl> command, specifying the bundle number and desired 15-minute interval number.

The following example shows how to display PPPMUX statistics for interval 1 of bundle 5.

M8850_SF.27.MPSM16T1E1PPP[FR].a > dsppppmuxcnt 5 1
MLPPP MUX Number : 5
Interval Number : 1

Receive Subframes : 0
Receive Packet : 0
Receive Error Packets : 0
Send Sub Frames : 0
Send Packets : 0
Send Non-Mux Packets : 1620

Table 6-28 describes the display.

Table 6-28 MLPPP PPPMUX Statistics

Counter

Description

MLPPP MUX Number

Bundle number associated with the PPPMUX

Interval Number

15-minute interval number

Receive Subframes

Number of PPPMux frames received

Receive Packet

Number of extracted PPP packets

Receive Error Packets

Number of PPPMux frames with demultiplex errors

Send Sub Frames

Number of PPPMux frames transmitted

Send Packets

Number of PPP packets multiplexed

Send Non-Mux Packets

Number of PPP packets not muxed

Step 4 To clear PPPMUX statistics for a bundle, enter the clrpppmuxcnt <bundleNumber> command, specifying the bundle number to clear.

Displaying Operational Loads

You can display the following operational loads:

•Interval packet and byte loads by WinPath resource

•Interval packet and byte loads by bundle

To display the operational loads, perform the following procedure:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command.

Step 3 To display WinPath loads on the current card, enter the dspwinpathload command.

M8850_SF.9.MPSM155PPP[FR].a > dspwinpathload <winpath> <intvl>

Table 6-29 describes the parameters for the dspwinpathload command.

Table 6-29 dspwinpathload Command Parameters

Parameter

Description

winpath

The number of the WinPath packet processing engine for which t o display loads. Range: 1-2.

intvl

The number of previous intervals to display, in the range 0-96. Interval 0 is the current interval and interval 96 is the oldest 15-minute interval.

The following example displays the current and three previous intervals for the operational load on WinPath 1.

M8850_SF.9.MPSM155PPP[FR].a > dspwinpathload 1 3
Winpath : 1
Intval Duration Rx Packet/s Tx Packet/s Rx Bytes/s Tx Bytes/s
0 4min 18s 259 259 3108 3108
1 15min 0s 900 900 10800 10800
2 15min 0s 898 898 10776 10776
3 15min 0s 900 910 10800 10980

Step 4 To list bundle loads on the current card, enter the dspmpbundleload command.

M8850_SF.9.MPSM155PPP[FR].a > dspmpbundleload <bundleNumber> <intvl>

Table 6-30 describes the parameters for the dspmpbundleload command.

Table 6-30 dspwinpathload Command Parameters

Parameter

Description

bundleNumber

Specifies the MLPPP bundle number.

Note Enter the dspmpbundles command to display all MLPPP bundles on the card.

intvl

The number of previous intervals to display, in the range 0-96. Interval 0 is the current interval and interval 96 is the oldest 15-minute interval.

The following example displays the current and three previous intervals for the operational load on bundle 2.

M8850_SF.9.MPSM155PPP[FR].a > dspmpbundleload 2 3
MLPPP Bundle Number : 2
Intval Duration Rx Packets/s Tx Packets/s Rx Bytes/s Tx Bytes/s

0 4min 26s 0 0 4 4
1 15min 0s 0 0 4 4
2 15min 0s 0 0 4 4
3 15min 0s 0 0 4 4

Displaying Load Assignments

This section explains how to display the assignment of MLPPP bundles to WinPath packet processing engines. Each processing engine can handle up to 64 bundles with up to 2016 DS0s. The software maps new MLPPP bundles to the WinPath with the smallest current load; users cannot configure WinPath resource assignments. Use this procedure to display the following:

•Assignment of bundles to WinPath resources

•Number of bundles and DS0s configured for each WinPath

To display WinPath resource assignments, perform the following procedure:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command.

Step 3 To list WinPath resource assignments on the current card, enter the dspwpbundles command.

M8850_SF.9.MPSM155PPP[FR].a > dspwpbundles

WinpathNum BundleId
1 1
1 3
2 2

Step 4 To list the number of bundles and DS0s for each WinPath, enter the dsptotals command.

M8850_SF.9.MPSM155PPP[FR].a > dsptotals
Interfaces Total Max Admin Up Available Alarm
Physical Lines 2 1 1 0
Sonet STS/SDH-AU 3 1 2 0
Sonet/SDH-TU 21 12 9 0
DS3 0 0 0 0
E3 0 0 0 0
DS1 0 0 0 0
E1 21 12 9 2
MP Bundles 84 3 81 0
PPP Links 84 7 77 0

winpath Total Max Configured
MpBundles on WP 1 64 2
MpBundles on WP 2 64 1

Confg BW on WP 1 2016 DS0s 105 DS0s
Confg BW on WP 2 2016 DS0s 62 DS0s

Interfaces Total Max Configured Available Alarm
FR Ports 1000 3 997 0
FR Connections 4000 0 4000* 0

Managing Resource Partitions

Resource partitions define how switch resources are distributed between two or more virtual switch controllers. Release 5 supports only the PNNI controller on service modules.

The PNNI controller resources include the following:

•Range of DLCI values

•Maximum percent of bandwidth in the ingress and egress directions

•Maximum number of connections

•Minimum and Maximum DLCI values

You configure partitions to control how these connection resources are distributed among the switch, card, and ports within the Cisco MGX 8850/8830 switch. Without these partitions, two or three busy ports could consume all the available connections, thereby disabling communications on all other ports.

On MPSM-T3E3-155 and MPSM-16-T1E1 cards, resource partitions are managed on the port level. During normal operation of the cards, you do not need to add port resource partitions. Port resource partitions are created automatically when you add a port to a line or path.

You can view the port resource partition configuration, make changes to it, or delete it. If you delete a port resource partition, you must to add a new partition for that port before you can assign connections to the port.

The commands used to display, configure, and delete resource partitions differ depending on the service context of port hosting the resource partition. The following sections describe resource partitions for the ATM and Frame relay contexts:

• ATM Port Resource Partitions

• Frame Relay Port Resource Partitions

ATM Port Resource Partitions

The following tasks describe how to manage ATM port resource partitions on the MPSM-T3E3-155 and MPSM-16-T1E1:

• Displaying an ATM Resource Partition

• Configuring an ATM Resource Partition

• Deleting an ATM Resource Partition

Displaying an ATM Resource Partition

Use the following procedure to display a list of the resource partitions configured on an MPSM-T3E3-155 or MPSM-16-T1E1 card, or to display configuration information for a particular resource partition on the card.

Step 1 Establish a CLI management session at any level of user access and enter the cc command to change to the appropriate card.

If you are in the Frame Relay CLI context, enter the setctx atm command to change to the ATM CLI context, as shown in the following example:

M8830_CH.12.MPSM155[FR].a > setctx atm

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 2 To display information for all ATM port resource partitions configured on the current card, enter the dspparts command as shown in the following example.

M8830_CH.12.MPSM155[ATM].a > dspparts
if part Ctlr egr egr ingr ingr min max min max min max
Num ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn
(.0001%)(.0001%)(.0001%)(.0001%)
-----------------------------------------------------------------------------
5 1 2 1000000 1000000 1000000 1000000 0 4095 32 65535 0 4000
10 1 2 1000000 1000000 1000000 1000000 0 4095 32 65535 0 4000

Step 3 To display configuration information for a particular resource partition on the current card, select the ifNum and the partID of the resource partition you want to display, and enter the dsppart <ifNum> <partID> command.

The following example shows typical output from a dsppart command that specifies the ATM port number 5 and partition ID number 1.

M8830_CH.12.MPSM155[ATM].a > dsppart 5 1
Interface Number : 5
Partition Id : 1 Number of SPVC : 0
Controller Id : 2 Number of SPVP : 0
egr Guaranteed bw(.0001percent): 1000000 Number of SVC : 0
egr Maximum bw(.0001percent) : 1000000 Number of Sig VC : 0
ing Guaranteed bw(.0001percent): 1000000
ing Maximum bw(.0001percent) : 1000000
min vpi : 0
max vpi : 4095
min vci : 32
max vci : 65535
guaranteed connections : 0
maximum connections : 4000
Configuring an ATM Resource Partition

To change the configuration of a an ATM port resource partition, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher, and enter the cc command to change to the card.

Step 2 If you are in the Frame Relay CLI context, enter the setctx atm command to change to the ATM CLI context, as shown in the following example:

M8830_CH.12.MPSM155[FR].a > setctx atm

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 Enter the dspparts command to obtain the partition ID for the port partition you want to configure. The port number appears in the if Num column, and the partition ID appears in the part ID column.

M8830_CH.12.MPSM155[ATM].a > dspparts
if part Ctlr egr egr ingr ingr min max min max min max
Num ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn
(.0001%)(.0001%)(.0001%)(.0001%)
-----------------------------------------------------------------------------
5 1 2 10000 1000000 1000000 1000000 0 4095 32 65535 0 4000

Step 4 To modify the configuration of an ATM port resource partition, enter the cnfpart command as follows.

mgx8850a.10.MPSM155[ATM].a > cnfpart -if <if> -id <partionID> -emin <egrMinBw> -emax <egrMaxBw> -imin <ingMinBw> -imax <ingMaxBw> -vpmin <minVpi> -vpmax <maxVpi> -vcmin <minVci> -vcmax <maxVci> -mincon <min connections> -maxcon <max connections>

Table 6-31 describes cnfpart command arguments.

Table 6-31 cnfpart Command Keywords and Arguments—ATM CLI Context

Argument

Description

-if

Interface number (partition number) of the partition to configure.

•MPSM-16-T1E1 range: 4-499

•MPSM-T3E3-155 range: 4-1003

Note To view all active ATM partitions, use the dspparts command in the ATM CLI context.

-id

A number that identifies the partition, in the range 1-20.

-emin

A guaranteed percentage of egress bandwidth. Each unit of egrminbw is 0.0001-percent of the total bandwidth on the port. (An egrMinBw of 1000000 = 100%.) These small increments provide a high level of granularity.

-emax

A maximum percentage of egress bandwidth. Each unit of egrmaxbw is 0.0001-percent of the total bandwidth available to the port. (An egrMaxBw of 1000000 = 100%.) The minimum bandwidth must be at least 50 cps.

-imin

A guaranteed percentage of the ingress bandwidth. Each unit of ingminbw is 0.0001 percent of the total bandwidth available to a port. (An ingMinBw of 1000000 = 100%.)

-imax

A maximum percentage of the ingress bandwidth. Each increment of ingmaxbw is 0.0001 percent of the total bandwidth on the port. (An ingMaxBw of 100000000 = 100%.) The maximum ingress bandwidth must be at least 50 cps.

-vpmin

Minimum VPI for the partition:

•UNI range 0-255

•NNI or VNNI range: 0-4095

-vpmax

Maximum VPI for the partition

•UNI range 0-255

•NNI or VNNI range: 0-4095

The max_vpi cannot be less than the min_vpi.

-vcmin

Minimum VCI, in the range from 1-65535

-vcmax

Maximum VCI, in the range from 1-65535

The max_vci cannot be less than the min_vci.

-mincon

Guaranteed number of connections. Value: 0 only

-maxcon

A maximum number of connections. Range 10-2000

Step 5 To verify the resource partition configuration, enter the dsppart <ifNum> <partID> command to display the configuration.

Deleting an ATM Resource Partition

Normally, you do not need to manually delete an ATM resource partition. When you delete an ATM port, the MPSM automatically deletes the associated partition. If you delete a port resource partition, you must add a new partition for that port before you can assign connections to the port.

To manually delete an ATM port resource partition, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher, and enter the cc command to change to the card.

Step 2 If you are in the Frame Relay CLI context, enter the setctx atm command to change to the ATM CLI context, as shown in the following example:

M8830_CH.12.MPSM155[FR].a > setctx atm

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 To display a list of the partitions for the card, enter the dspparts command as shown in the following example. Note the interface number and controller number for the resource partition you plan to delete.

M8830_CH.12.MPSM155[ATM].a > dspparts
if part Ctlr egr egr ingr ingr min max min max min max
Num ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn
(.0001%)(.0001%)(.0001%)(.0001%)
-----------------------------------------------------------------------------
5 1 2 10000 1000000 1000000 1000000 0 4095 32 65535 0 4000

Step 4 To display a list of all active connections on the current card, enter the dspcons command as shown in the following example. Determine if the interface to which the partition is assigned is being used by a connection.

Note The Identifier column identifies the interface numbers, the VPI, and VCI for each connection. If the interface is in use, note the interface number, the VPI, and the VCI values of all connections using the interface, because you will need these values to delete the connections.

M8830_CH.12.MPSM155[ATM].a > dspcons
record Identifier Type SrvcType M/S Upld Admn Alarm
------ ---------- ---- -------- --- ---- ---- -----
0 05 0100 00100 VCC cbr1 S 00000011 UP none
1 10 0100 00100 VCC cbr1 M 00000012 UP none

Step 5 Enter the delcon command as follows to delete any ATM connection that uses the interface whose partition you want to delete. If the are no connection that use the interface whose partitions you want to delete, skip this step.

M8830_CH.12.MPSM155[ATM].a > delcon <ifNum> <vpi> <vci>

Replace <ifNum > with the interface number of the port associated with the connection you want to delete. Replace <vpi> and <vci> with the VCI and VPI of the connection you want to delete.

Note You must enter the delcon command one time for each connection that uses the interface whose partition you want to delete.

In the following example, the user deletes the connection on port 5 with a VPI of 100 and a VCI of 100.

M8830_CH.12.MPSM155[ATM].a > delcon 5 100 100
Deletion successful

Step 6 To delete the resource partition, enter the delpart command as follows.

mgx8850a.10.MPSM155[FR].a > delpart <ifNum> <partID>

Replace <ifNum> with the interface number of the port whose partition you want to delete. Replace <ctrlNum> with the number 2, which represents the PNNI controller.

Step 7 To verify that the appropriate partition is deleted, enter the dspparts command.

Frame Relay Port Resource Partitions

The following tasks describe how to manage Frame Relay port resource partitions on the MPSM-T3E3-155 and MPSM-16-T1E1:

• Displaying a Frame Relay Resource Partition

• Configuring a Frame Relay Resource Partition

• Deleting a Frame Relay Resource Partition

Displaying a Frame Relay Resource Partition

To display summary or detail information about the resource partitions, perform the following steps.

Step 1 Establish a CLI management session at any level of user access and enter the cc command to change to the appropriate card.

Step 2 If you are in the ATM CLI context, enter the setctx fr command to change to the Frame Relay CLI context, as shown in the following example:

M8830_CH.12.MPSM155[ATM].a > setctx fr

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 Enter the dspparts command to display information for all the Frame Relay port resource partitions configured on the current card, as shown in the following example.

mpsm_node.5.MPSM155[FR].a > dspparts
if Ctlr Ctlr available min max ingr egr
Num Num ID LCNs DLCI DLCI PctBw PctBw
-------------------------------------------------------------
2 pnni 2 4000 0 1023 100 100
50 pnni 2 2000 0 1023 100 100

Step 4 To display configuration information for a particular resource partition on the current card, obtain the ifNum and the CtlrNum of the resource partition you want to display, and enter the dsppart command as follows:

M8850_LA.10.MPSM155[FR].a > dsppart <ifNum> <CtrlNum>

Replace the <ifNum> argument with the interface number of the selected port; replace the <CtrlNum> argument with the PNNI controller ID number for the selected port.

Note In Release 5, the MPSM supports the PNNI controller only.

The following example shows typical output from a dsppart command that specifies the Frame Relay port number 10 and controller ID number 2.

M8850_LA.10.MPSM155[FR].a > dsppart 10 2
Interface Number : 10
Partition Id : pnni Number of SPVC: 1000
Controller Id : 2
Available LCNs : 1000
Min dlci : 0
Max dlci : 65535
Ing Percentage bw : 100
Egr Percentage bw : 100

Configuring a Frame Relay Resource Partition

To change the configuration of a specific Frame Relay port resource partition, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher, and enter the cc command to change to the appropriate card.

Step 2 If you are in the ATM CLI context, enter the setctx fr command to change to the Frame Relay CLI context, as shown in the following example:

M8830_CH.12.MPSM155[ATM].a > setctx fr

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 Obtain the partition ID for the port partition you want to configure by entering the dspparts command. The port number appears in the if Num column, and the partition ID appears in the part ID column.

mpsm_node.5.MPSM155[FR].a > dspparts
if Ctlr Ctlr available min max ingr egr
Num Num ID LCNs DLCI DLCI PctBw PctBw
-------------------------------------------------------------
2 pnni 2 4000 0 1023 100 100
50 pnni 2 2000 0 1023 100 100

Step 4 Modify the configuration of a particular Frame Relay port resource partition by entering the cnfpart command as follows:

mgx8850a.10.MPSM155[FR].a >ccnfpart <ifNum> <ctrlNum> [-lcn <available connections>] [-dlcimin <minDlci>] [-dlcimax <maxDlci>] [-ibw <ingPctBw>] [-ebw <egrPctBw>]

Table 6-32 describes cnfpart command arguments.

Table 6-32 Keywords and Arguments for the cnfpart Command in the Frame Relay CLI Context

ifNum

Specifies the interface number (partition number) of the partition to add.

•MPSM-16-T1E1 range: 1-499

•MPSM-T3E3-155 range: 1-1003

Identifies the logical interface to which you want to add a resource partition.

Note To view all active partitions, use the dspparts command in the Frame Relay CLI context.

ctrlNum

Specifies a network controller protocol. Enter 2 to specify the PNNI controller.

Note Release 5 of the MPSM-T3E3-155 supports only the PNNI controller (option 2). TAG switching (option 1) and MPLS (option 3) are not supported on the MPSM-T3E3-155 card.

-lcn

Maximum number of connections.

•MPSM-16-T1E1 range: 0-2000

•MPSM-T3E3-155 range: 0-4000

-dlcimin

Minimum DLCI value.

•2-byte header range: 0-1023

•4-byte header range: 0-8355840 in multiples of 32,768

For example, you can enter one of the following numbers as the minimum DLCI value, or any other number that is a multiple of 32,768:

0 = (0 x 32768)
163840 = (5 x 32768)
8355840 = (255 x 32768)

Unless your provisioning plan calls for a specific range of DLCI values on a port or card, specify the minimum DLCI value as 0.

-dlcimax

Maximum DLCI value.

•2-byte header range: 0-1023

•4-byte header range: 32,767-8,355,840 in multiples of 32,768 minus 1

For example, you can enter one of the following numbers as the maximum DLCI value, or any other number that is a multiple of 32,768 minus l:

32767 = (32768 * 1) - 1
163839 = (32768 * 5) - 1
6520831 = (32768 * 199) - 1

Unless your provisioning plan calls for a specific range of DLCI value on a port or card, specify the maximum DLCI value as 8388607.

-ibw

Maximum ingress port bandwidth percentage for the controller type specified with the ctrlrNum argument, in the range 0-100 percent.

-ebw

Maximum egress port bandwidth percentage for the controller type specified with the ctrlrNum argument, in the range 0-100 percent.

Step 5 To display and verify the modified resource partition configuration, enter the dsppart command.

Deleting a Frame Relay Resource Partition

You usually do not need to manually delete a resource partition. When you delete a Frame Relay port, the MPSM automatically deletes the partition for that port. If you delete a port resource partition, you must add a new partition for that port before you assign connections to the port.

To manually delete a Frame Relay port resource partition, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher, and enter the cc command to change to the appropriate card.

Step 2 If you are in the ATM CLI context, enter the setctx fr command to change to the Frame Relay CLI context, as shown in the following example:

M8830_CH.12.MPSM155[ATM].a > setctx fr

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 To display a list of the partitions for the card, enter the dspparts command as shown in the following example. Note the interface number and controller number for the resource partition you plan to delete.

M8830_CH.12.MPSM155[FR].a > dspparts
if Ctlr Ctlr available min max ingr egr
Num Num ID LCNs DLCI DLCI PctBw PctBw
-------------------------------------------------------------
20 pnni 2 1 0 1023 100 100
30 pnni 2 1 0 1023 100 100
40 pnni 2 1 0 1023 100 100

Step 4 To display a list of all active connections on the current card, enter the dspcons command as shown in the following example. Determine if the interface to which the partition is assigned is being used by a connection.

mgx8850a.10.MPSM155[FR].a > dspcons

record Identifier SrvcType M/S Upld Admn Alarm
------ ---------- -------- --- ---- ---- ---------------------
1 01 0000100 High Priority S 01417863 UP Multiple
2 01 0000101 High Priority S 01417875 UP Multiple
3 01 0000102 High Priority S 01417875 UP Multiple
4 01 0000103 High Priority S 01417875 UP Multiple
5 01 0000104 High Priority S 01417875 UP Multiple
6 01 0000105 High Priority S 01417875 UP Multiple
7 01 0000106 High Priority S 01417875 UP Multiple
8 01 0000107 High Priority S 01417875 UP Multiple
9 01 0000108 High Priority S 01417875 UP Multiple
10 01 0000109 High Priority S 01417875 UP Multiple
11 01 0000110 High Priority S 01417876 UP Multiple
12 02 0000200 High Priority M 01417886 UP E-AisRdi
13 02 0000201 High Priority M 0141788d UP E-AisRdi
14 02 0000202 High Priority M 0141788e UP E-AisRdi

Note The Identifier column identifies the interface numbers and DLCI values for the connection. If the interface is in use, note the DLCI values of all connections using the interface, because you will need these values to delete the connections.

Step 5 To delete any Frame Relay connection that uses the interface whose partition you want to delete, enter the delcon command as follows. If the are no connections that use the interface whose partitions you want to delete, skip this step.

mgx8850a.10.MPSM155[FR].a > delcon <ifNum> <DLCI>

Replace <ifNum> with the number of the interface whose connection you want to delete, and replace <DLCI> with the DLCI of the interface whose connection you want to delete.

In the following example, the user deletes the connection on port 2 with a DLCI of 200.

M8830_CH.12.MPSM155[FR].a > delcon 2 200
Deletion successful

Note You must enter the delcon command one time for each connection that uses the interface whose partition you want to delete.

Step 6 To delete the resource partition, enter the delpart command as follows.

mgx8850a.10.MPSM155[FR].a > delpart <ifNum> <ctrlNum>

Replace <ifNum > with the interface number of the port whose partition you want to delete. Replace <ctrlNum> with the number 2, which represents the PNNI controller.

Step 7 Verify that the appropriate partition is deleted by entering the dspparts command.

Managing Connections

The commands used to display, configure, a delete connections differ depending on the service context of port hosting the connection. The sections that follow describe the following types of connection management:

• ATM Connections

• Frame Relay Connections

ATM Connections

Chapter 3, "Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1." describes how to add connections to ATM ports on MPSM-T3E3-155 and MPSM-16-T1E1 cards. The following sections describe:

• Displaying All ATM Connections

• Displaying One ATM Connection

• Deleting ATM Connections

• Testing ATM Connections

Displaying All ATM Connections

To display a list of all ATM connections on the current card, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher, and enter the cc command to change to the appropriate card.

Step 2 If you are in the Frame Relay CLI context, enter the setctx atm command to change to the ATM CLI context, as shown in the following example:

M8830_CH.12.MPSM155[FR].a > setctx atm

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 To display a list of all active ATM connections on the current card, enter the dspcons command:

M8830_CH.12.MPSM155[ATM].a > dspcons
record Identifier Type SrvcType M/S Upld Admn Alarm
------ ---------- ---- -------- --- ---- ---- -----
0 05 0100 00100 VCC cbr1 S 00000011 UP none
1 10 0100 00100 VCC cbr1 M 00000012 UP none

Note The Identifier column identifies the interface number, VPI, and VCI for each connection on the current card. You need these values for any connection you want to display, configure, or delete.

Displaying One ATM Connection

To display the configuration and status of one ATM connection, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher, and enter the cc command to change to the card.

Step 2 If you are in the Frame Relay CLI context, enter the setctx atm command to change to the ATM CLI context, as shown in the following example:

M8830_CH.12.MPSM155[FR].a > setctx atm

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 To display a list of all active connections on the current card, enter the dspcons command as shown in the following example.

M8830_CH.12.MPSM155[ATM].a > dspcons
record Identifier Type SrvcType M/S Upld Admn Alarm
------ ---------- ---- -------- --- ---- ---- -----
0 05 0100 00100 VCC cbr1 S 00000011 UP none
1 10 0100 00100 VCC cbr1 M 00000012 UP none

Step 4 To display the configuration and status of one connection on the current card, enter the dspcon command:

M8830_CH.12.MPSM155[ATM].a > dspcon <ifNum> <vpi> <vci>

Replace <ifNum> with the number of the interface whose connection you want to display. Replace <vpi> and <vci> with the VPI and VCI of the connection you want to display.

In the following example, the user displays the connection on port 5, with a VPI of 100 and a VCI of 100.

M8830_CH.12.MPSM155[ATM].a > dspcon 5 100 100
--------------------------------------------------------------------------
Local : NSAP Address vpi vci
(M) 4700918100000000001A5389430000010C180500 100 100
Remote : NSAP Address vpi vci
(S) 4700918100000000001A5389430000010C180A00 100 100
--------------------------------------------------------------------------
Conn. Type : VCC Admn Status : ADMN-UP
Service Type : cbr1 Oper Status : OK
Controller : 2 Record # : 3
SlavePersist : YES Cast-type : P2P
--------------------------------------------------------------------------
Local PCR : 50 Remote PCR : 50
Local SCR : N/A Remote SCR : N/A
Local CDV : -1 Remote CDV : -1
Local CTD : -1 Remote CTD : -1
Local MBS : N/A Remote MBS : N/A
Max Cost : -1 Frame discard: DISABLED
Local CDVT : 250000 OAM segment : ENABLED
Local PctUtil : 100 Rmt PctUtil : 100
Priority : 8
Pref Rte Id : 0 Directed route: NO
--------------------------------------------------------------------------

Type <CR> to continue, Q<CR> to stop:
OAM CC Config : DISABLED Statistics : ENABLED
--------------------------------------------------------------------------
Loopback Type : No Lpbk | Dir: N/A | Status: No Lpbk | RTD: 0us
--------------------------------------------------------------------------

--------------------------------------------------------------------------
Port side Tx : normal Swth side Tx : normal
Port side Rx : normal Swth side Rx : normal
--------------------------------------------------------------------------
I-AIS/RDI E-AIS/RDI CONDITIONED CCFAIL IfFail Mismatch LMI-ABIT
NO NO NO NO NO NO NO
--------------------------------------------------------------------------

Deleting ATM Connections

To delete an ATM connection, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher, and enter the cc command to change to the card.

Step 2 If you are in the Frame Relay CLI context, enter the setctx atm command to change to the ATM CLI context, as shown in the following example:

M8830_CH.12.MPSM155[FR].a > setctx atm

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 To delete an ATM connection, enter the delcon command as follows:

M8830_CH.12.MPSM155[ATM].a > delcon <ifNum> <vpi> <vci>

Replace <ifNum> with the number of the interface whose connection you want to delete. Replace <vpi> and <vci> with the VPI and VCI of the connection you want to display.

Note To obtain the interface number, VPI, and VCI of a connection, enter the dspcons command.

In the following example, the user deletes the connection on port 5 with a VPI of 100 and a VCI of 100.

M8830_CH.12.MPSM155[ATM].a > delcon 5 100 100
Deletion successful

Testing ATM Connections

The following sections describe how to test the integrity of ATM connections in the ingress and egress direction:

• Testing ATM Connections in the Egress Direction

• Testing ATM Connections in the Ingress Direction

• Displaying ATM Connection Test Results

Testing ATM Connections in the Egress Direction

The tstcon command checks to see if the switch can communicate with both ends of the connection in the egress direction. To test the egress direction of a ATM connection, enter the tstcon command in the ATM CLI context as follows:

M8830_CH.12.MPSM155[ATM].a > tstcon <ifNum> vpi> <vci> [-num <iterations>]

Replace <ifNum> with the number of the interface whose connection you want to test. Replace <vpi> and <vci> with the VPI and VCI of the connection you want to display. To specify the number of times a collection of supervisory cells traverses the connection, enter the optional -num keyword, followed by the number of consecutive times you want to run the test on the specified connection. You can run a test up to 10 times for one execution of the tstcon command.

Note If you do not specify the -num <iterations> option, the test runs one time only.

Note To obtain the interface number, VPI, and VCI of a connection, enter the dspcons command.

In the following example, the user runs 3 consecutive tests in the egress direction of the connection on port 10, VPI 100, VCI 100.

M8830_CH.12.MPSM155[ATM].a > tstcon 10 100 100 -num 3
tstconseg is in progress ..
Connection Id Test Type Direction Result Round Trip Delay
============= ========= ========= ======= ================
10.0100.00100: OAM Lpbk egress Success 20119 microsec
tstconseg is in progress ..
Connection Id Test Type Direction Result Round Trip Delay
============= ========= ========= ======= ================
10.0100.00100: OAM Lpbk egress Success 20120 microsec
tstconseg is in progress ..
Connection Id Test Type Direction Result Round Trip Delay
============= ========= ========= ======= ================
10.0100.00100: OAM Lpbk egress Success 20122 microsec
Testing ATM Connections in the Ingress Direction

The tstdelay command checks to see if the switch can communicate with both ends of the connection in the ingress direction, and it returns a measurement of the delay across the connection. To test the ingress direction of an ATM connection, enter the tstdelay command in the ATM CLI context as follows:

M8830_CH.12.MPSM155[ATM].a > tstdelay <ifNum> <vpi> <vci> [-num <iterations>]

Replace <ifNum> with the number of the interface whose connection you want to test. Replace <vpi> and <vci> with the VPI and VCI of the connection you want to display. To specify the number of times a collection of supervisory cells traverses the connection, enter the optional -num keyword, followed by the number of consecutive times you want to run the test on the specified connection. You can run a test up to 10 times for one execution of the tstdelay command.

Note If you do not specify the -num <iterations> option, the test runs one time only.

Note To obtain the interface number, VPI, and VCI of a connection, enter the dspcons command.

In the following example, the user runs 2 consecutive tests the connection on port 10, VPI 100, VCI 100.

M8830_CH.12.MPSM155[ATM].a > tstdelay 10 100 100 -num 2
tstdelay is in progress ..
Connection Id Test Type Direction Result Round Trip Delay
============= ========= ========= ======= ================
10.0100.00100: OAM Lpbk ingress Success 80137 microsec
tstdelay is in progress ..
Connection Id Test Type Direction Result Round Trip Delay
============= ========= ========= ======= ================
10.0100.00100: OAM Lpbk ingress Success 80136 microsec
Displaying ATM Connection Test Results

Enter the dspchantest command in the ATM CLI context as follows to display the results of the last test that was run on a connection with the tstcon command or tstdelay command.

M8830_CH.12.MPSM155[ATM].a > tstdelay <ifNum> <vpi> <vci> [-num <iteration>]

Replace <ifNum> with the number of the interface whose connection test results you want to display. Replace <vpi> with the VPI of the connection whose test results you want to display. Replace <vpi> and <vci> with the VPI and VCI of the connection you want to display. To specify the number of tests whose results you want to display, enter the options -num keyword, followed by the number of consecutive connections whose test results to display. You can display test results for up to 10 connections.

Note The dspchantest command displays the results of the last test run on the specified number of connections, regardless of whether it was a tstcon test or a tstdelay test.

Note If you do not specify the -num <iterations> option, the test displays only the results for the last test that was run on the specified connection.

Note To obtain the interface number, VPI, and VCI of a connection, enter the dspcons command in the ATM CLI context.

In the following example, the user displays the results for the last test that was run on the connection on port 10, VPI 100, VCI 100.

M8830_CH.12.MPSM155[ATM].a > dspchantests 10 100 100
Connection Id Test Type Direction Result Round Trip Delay
============= ========= ========= ======= ================
10.0100.00100: OAM Lpbk ingress Success 80136 microsec
Frame Relay Connections

Chapter 4, "Provisioning Frame Relay Services on MPSM-T3E3-155 and MPSM-16-T1E1." describes how to add Frame Relay connections to MPSM-T3E3-155 and MPSM-16-T1E1 cards. The following sections provide procedures for the following tasks:

• Displaying all Frame Relay Connections

• Displaying One Frame Relay Connection

• Deleting Frame Relay Connections

• Testing Frame Relay Connections

These procedures apply to the MPSM-T3E3-155 and MPSM-16-T1E1 in the Frame Relay context, and the MPSM-16-T1E1 in the PPP mode.

Displaying all Frame Relay Connections

To display a list of Frame Relay connections on the current card, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher, and enter the cc command to change to the card.

Step 2 If you are in the ATM CLI context, enter the setctx fr command to change to the Frame Relay CLI context, as shown in the following example:

M8830_CH.12.MPSM155[ATM].a > setctx fr

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 Enter the dspcons command as shown in the following example to display a list of all active connections on the current card.

Note The Identifier column identifies the interface numbers and DLCI values for each connection on the current card. You will need these values for any connection you want to display, configure, or delete.

mgx8850a.10.MPSM155[FR].a > dspcons

record Identifier SrvcType M/S Upld Admn Alarm
------ ---------- -------- --- ---- ---- ---------------------
1 01 0000100 High Priority S 01417863 UP Multiple
2 01 0000101 High Priority S 01417875 UP Multiple
3 01 0000102 High Priority S 01417875 UP Multiple
4 01 0000103 High Priority S 01417875 UP Multiple
5 01 0000104 High Priority S 01417875 UP Multiple
6 01 0000105 High Priority S 01417875 UP Multiple
7 01 0000106 High Priority S 01417875 UP Multiple
8 01 0000107 High Priority S 01417875 UP Multiple
9 01 0000108 High Priority S 01417875 UP Multiple
10 01 0000109 High Priority S 01417875 UP Multiple
11 01 0000110 High Priority S 01417876 UP Multiple
12 02 0000200 High Priority M 01417886 UP E-AisRdi
13 02 0000201 High Priority M 0141788d UP E-AisRdi
14 02 0000202 High Priority M 0141788e UP E-AisRdi

Displaying One Frame Relay Connection

To display the configuration and status of a single Frame Relay connection, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher, and enter the cc command to change to the card.

Step 2 If you are in the ATM CLI context, enter the setctx fr command to change to the Frame Relay CLI context as shown in the following example:

M8830_CH.12.MPSM155[ATM].a > setctx fr

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 To display a list of all active connections on the current card, enter the dspcon command:

M8830_CH.12.MPSM155[FR].a > dspcon <ifNum> <DLCI>

Replace <ifNum> with the number of the interface whose connection you want to display, and replace <DLCI> with the DLCI of the connection you want to display.

In the following example, the user displays the connection on port 20, DLCI 100.

M8830_CH.12.MPSM155[FR].a > dspcon 20 100
--------------------------------------------------------------------------
Local : NSAP Address vpi vci
(S) 4700918100000000001A5389430000010C1FFF00 38 100
Remote : NSAP Address vpi vci
(M) 4700918100000000001A5389430000010C1FFF00 58 100
--------------------------------------------------------------------------
Port Number : 20 DLCI : 100
Conn. Type : frForward Chan Service Type: uBR
Conn Service Type : ubr1 Egress Queue Type: lowPriority
Admn Status : UP Oper Status : OK
Slave Persist : N/A Max Cost : N/A
CIR (bps) : 10000 BC (bytes) : 10300
BE (bytes) : 10300 FECN Config : setEFCIzero
ChanDEtoCLPmap : setCLPzero ChanCLPtoDEmap : ignoreCLP
IngrPercentUtil : 100 EgrPercentUtil : 100
EgrSrvRate (bps) : 10000 ZeroCirEir (bps) : N/A
DE Tagging : DISABLED IgnoreIncomingDE : DISABLED
Pref Rte Id : 0 Directed Route : NO
Upload : 00000019 Routing Priority : 0
OAM CC Config : DISABLED Statistics : ENABLED
Local Loopback : DISABLED UPC : ENABLED
--------------------------------------------------------------------------

Type <CR> to continue, Q<CR> to stop:
Local PCR (cps) : 38 Remote PCR (cps) : 38
Local SCR (cps) : N/A Remote SCR (cps) : N/A
Local MCR (cps) : N/A Remote MCR (cps) : N/A
: Remote MBS (cps) : N/A
--------------------------------------------------------------------------
Xmt Abit State : A equal 1 Rcv Abit State : OFF
Xmt ATM State : Not Sending Rcv ATM State : Not Recving
--------------------------------------------------------------------------
E-AIS/RDI CONDITIONED CCFAIL IfFail Mismatch LMI-ABIT
NO NO NO NO NO NO
--------------------------------------------------------------------------

M8830_CH.12.MPSM155[FR].a >

Deleting Frame Relay Connections

Use the following procedure to delete a Frame Relay connection:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 If you are in the ATM CLI context, enter the setctx fr command to change to the Frame Relay CLI context as shown in the following example:

M8830_CH.12.MPSM155[ATM].a > setctx fr

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 To delete a Frame Relay connection, enter the delcon command as follows.

mgx8850a.10.MPSM155[FR].a > delcon <ifNum> <DLCI>

Replace <ifNum> with the number of the interface whose connection you want to delete, and replace <DLCI> with the DLCI of the interface whose connection you want to delete.

Note To obtain the interface number and DLCI of a connection, enter the dspcons command.

In the following example, the user deletes the connection on port 2 with a DLCI of 200.

M8830_CH.12.MPSM155[FR].a > delcon 2 200
Deletion successful

Testing Frame Relay Connections

The following sections describe how to test the integrity of Frame Relay connections in the ingress and egress direction:

• Testing Frame Relay Connections in the Egress Direction

• Testing Frame Relay Connections in the Ingress Direction

• Displaying Frame Relay Connection Test Results

Testing Frame Relay Connections in the Egress Direction

The tstcon command checks to see if the switch can communicate with both ends of the connection in the egress direction. To test the egress direction of a Frame Relay connection with the tstcon command, enter the tstcon command in the Frame Relay CLI context, as follows:

M8830_CH.12.MPSM155[FR].a > tstcon <ifNum> <dlci>

Replace <ifNum> with the number of the interface whose connection you want to test. Replace <dlci> with the DLCI of the connection you want to test.

Note To obtain the interface number, VPI, and VCI of a connection, enter the dspcons command in the Frame Relay CLI context.

In the following example, the user tests the connection on port 20, DLCI 100.

M8830_CH.12.MPSM155[FR].a > tstcon 20 100
tstcon is in progress ..
Connection Id Test Type Result Round Trip Delay
============= ========== ============ ================
20.0000100 Test Con Passed
Testing Frame Relay Connections in the Ingress Direction

The tstdelay command checks to see if the switch can communicate with both ends of the connection in the ingress direction, and it returns a measurement of the delay across the connection. To test the ingress direction of a Frame Relay connection, enter the tstdelay command in the Frame Relay CLI context as follows:

M8830_CH.12.MPSM155[FR].a > tstdelay <ifNum> <dlci>

Replace <ifNum> with the number of the interface whose connection you want to test. Replace <dlci> with the DLCI of the connection you want to test.

Note Enter the dspcons command in the Frame Relay CLI context to obtain the interface number and DLCI of a connection.

In the following example, the user runs 5 consecutive tests the connection on port 20, DLCI 100.

M8830_CH.12.MPSM155[FR].a > tstdelay 20 100
tstdelay is in progress ..
Connection Id Test Type Result Round Trip Delay
============= ========== ============ ================
20.0000100 Test Delay Passed 19905 microsec

Displaying Frame Relay Connection Test Results

Enter the dspchantest command in the Frame Relay CLI context as follows to display the results of the last test that was run on a connection using the tstcon command or the last tstdelay command.

M8830_CH.12.MPSM155[FR].a > tstdelay <ifNum> <dlci>

Replace <ifNum> with the number of the interface whose connection test results you plan to display. Replace <dlci> with the DLCI of the connection whose test results you plan to display.

Note You cannot specify whether you want to display results for the tstcon or tstdelay tests. The dspchantest command shows the results of the last test run on the specified connection, regardless of whether it was a tstcon or tstdelay test.

Note To obtain the interface number and DLCI of a connection, enter the dspcons command in the Frame Relay CLI context.

In the following example, the user displays the results for the last test that was run on the connection on port 20, DLCI 100.

M8830_CH.12.MPSM155[FR].a > dspchantest 20 100 -num 2
Connection Id Test Type Result Round Trip Delay
============= ========== ============ ================
20.0000100 Test Delay Passed 19905 microsec
30.0000100 No Test Not In Progress

Verifying PNNI Communication

After setting up trunks or when problems occur, use the procedures in this section to determine if PNNI is operating. The next section describes how to verify PNNI communications on one trunk. The following section describes how to verify PNNI communications between two nodes, which can be separated by multiple PNNI links.

Verifying PNNI Trunk Communication

After you configure both ends of a PNNI trunk, prepare the trunk to support SVCs and any configured SPVCs or SPVPs. To verify that the trunk is functioning, use the following procedure.

Step 1 Establish a CLI session with the active PXM using a username at any access level.

If you are configuring a point-to-point (P2P) connection where both ends of the trunk are connected to Cisco MGX 8850 (PXM1E/PXM45) or Cisco MGX 8830 switches, you can start the CLI session at either end of the connection.

If you are configuring a point-to-multipoint (P2MP) connection where both ends of the trunk are connected to Cisco MGX 8850 (PXM1E/PXM45) or Cisco MGX 8830 switches, you can start the CLI session at either end of the connection.

Step 2 If you do not know the line number you are validating, you can view the port and line numbers by entering the dsppnports command at the active PXM.

The first three numbers identify the slot, bay, and line. For example, port 10:1.1:3 represents slot 10, bay 1, line 1. The remaining number is the interface number assigned using the addport command.

Step 3 To display all PNNI links on the current switch, enter the dsppnni-link command as follows:

MGX8850.7.PXM.a > dsppnni-link

The dsppnni-link command displays a report for each PNNI link on the switch. The following example shows the report for a switch with one PNNI link.

MGX8850.7.PXM.a > dsppnni-link

node index : 1
Local port id: 16848897 Remote port id: 17438721
Local Phy Port Id: 1:1.1:1
Type. lowestLevelHorizontalLink Hello state....... twoWayInside
Derive agg........... 0 Intf index........... 16848897
SVC RCC index........ 0 Hello pkt RX......... 10
Hello pkt TX......... 9
Remote node name.......MGX8850
Remote node id.........56:160:47.00918100000000107b65f33c.00107b65f33c.01
Upnode id..............0:0:00.000000000000000000000000.000000000000.00
Upnode ATM addr........00.000000000000000000000000.000000000000.00
Common peer group id...00:00.00.0000.0000.0000.0000.0000.00

In the dsppnni-link command report, make sure there is an entry for the port for which you are verifying communications. The Local Phy Port Id field in this entry displays the port ID in the same format shown in the dsppnports command report. The Hello state reported for the port should be twoWayInside. The Remote note ID should display the remote node ATM address.

In the example, the report shown is for port 1:1.1:1. The Hello state is twoWayInside, and the ATM address of the node at the other end of the link is 47.00918100000000107b65f33c.00107b65f33c.01. This link is ready to support connections between the two switches.

Tip If the Hello state for the link is oneWayInside, that side is trying to communicate. Check the status at the other end. Remember that the configuration at each end of the trunk must be compatible with that on the other end. For example, if ILMI autoconfiguration is configured at one end and not at the other, the Hello state cannot change to twoWayInside or twoWayOutside.

Verifying End-to-End PNNI Communications

When connections between two nodes travel over multiple trunks, use the following steps to verify that the PNNI communications path is operational.

Step 1 Establish a CLI session with the active PXM using a username at any access level. When both ends of the communications path are connected to MGX 8850/8830 switches, you can start the CLI session at either end.

Step 2 To display information on all accessible nodes, enter the dsppnni-node-list command as shown:

MGX8850.7.PXM.a > dsppnni-node-list

node # node id node name
------- -------------------------------------------------- ----------
1 56:160:47.00918100000000001a531c2a.00001a531c2a.01 MGX8850

node # node id node name
------- -------------------------------------------------- ----------
2 56:160:47.00918100000000036b5e2bb2.00036b5e2bb2.01 8850_NY

If a switch appears in this list, you have verified communications with the switch.

Step 3 To display additional information on the local switch, enter the dsppnni-node command. For example:

MGX8850.7.PXM.a > dsppnni-node

node index: 1 node name: MGX8850
Level............... 56 Lowest.............. true
Restricted transit.. off Complex node........ off
Branching restricted on
Admin status........ up Operational status.. up
Non-transit for PGL election.. off
Node id...............56:160:47.00918100000000001a531c2a.00001a531c2a.01
ATM address...........47.00918100000000001a531c2a.00001a531c2a.01
Peer group id.........56:47.00.9181.0000.0000.0000.0000.00

Step 4 To display additional information on remote switches, enter the dsppnni-reachable-addr command as follows:

MGX8850.7.PXM.a > dsppnni-reachable-addr network

scope............... 0 Advertising node number 2
Exterior............ false
ATM addr prefix.....47.0091.8100.0000.0003.6b5e.2bb2/104
Advertising nodeid..56:160:47.00918100000000036b5e2bb2.00036b5e2bb2.01
Node name...........8850_NY

The remote node ATM address appears in the Advertising nodeid row. The information before the first colon (56) is the PNNI level, the information between the first and second colons (160) is the ATM address length, and the remainder of the node ID is the ATM address for the remote node.

Tip If you cannot verify communications with a remote node, try verifying communications across each of the links between the nodes as described in the previous section, " Verifying PNNI Trunk Communication."

Managing IMA Groups

The "Configuring Inverse Multiplexing over ATM" section in Chapter 3, "Provisioning ATM Services," describes how to create and configure IMA groups. The sections that follow describe:

• Displaying a List of IMA Groups

• Displaying the Configuration for One IMA Group

• Configuring an IMA Group

• Configuring an IMA Link

• Deleting Lines from an IMA Group

• Deleting an IMA Group

• Administratively Enabling and Disabling IMA

• Testing an IMA Link

• Modifying an IMA Link Test

Note To perform these IMA configuration tasks, you must be in the ATM CLI context

Displaying a List of IMA Groups

To display a list of IMA groups on the current card, enter the dspimagrps command in the ATM CLI context as follows:

M8830_CH.12.MPSM155[ATM].a > dspimagrps
Ima Min Tx Rx Tx Diff NE-IMA FE-IMA IMA
Grp Lnks Frm Frm Clk Delay State State Ver
Len Len Mode (ms)
--------------------------------------------------------------------------------
1 3 128 128 CTC 100 StartUp StartUp 1.0
Displaying the Configuration for One IMA Group

To display the configuration of one IMA group, enter the dspimagrp < group> command in the ATM CLI context. Replace <group> with the IMA group number you want to display.

The following example shows the information you can display using the dspimagrp command:

NodeB.6.MPSM155[ATM].a > dspimagrp 1
Group Number : 1
NE IMA Version : 1.1
Group Symmetry : Symm Operation
Tx Min Num Links : 1
Rx Min Num Links : 1
NE Tx Clk Mode : CTC
FE Tx Clk Mode : CTC
Tx Frame Len (bytes) : 128
Rx Frame Len (bytes) : 128
Group GTSM : Up
NE Group State : Operational
FE Group State : Operational
Group Failure Status : No Failure
Tx Ima ID : 1
Rx Ima ID : 22
Max Cell Rate (c/s) : 7183
Avail Cell Rate (c/s) : 7183
Diff Delay Max (msecs) : 200
Diff Delay Max Observed (msecs) : 0
Accumulated Delay (msecs) : 0
Clear Accumulated Delay Status : Not In Progress
GTSM Up Integ Time (msecs) : 0

Type <CR> to continue, Q<CR> to stop:
GTSM Dn Integ Time (msecs) : 4000
Num Tx Cfg Links : 2
Num Rx Cfg Links : 2
Num Act Tx Links : 2
Num Act Rx Links : 2
Least Delay Link : 1.1:28
Tx Timing Ref Link : 1.1:28
Rx Timing Ref Link : 1.1:27
Group Running Secs : 276430
Alpha Val : 2
Beta Val : 2
Gamma Val : 1
Tx OAM Label : 3
Rx OAM Label : 3
Test Pattern Procedure Status : Disabled
Test Link : Unknown
Test Pattern : 255
Stuff Cell Indication (frames) : 1
Version Fallback Enabled : true
Auto-Restart Mode : disable
Rx IMA ID Expected : -1
Auto-Restart Sync State : disable
Configuring an IMA Group

To configure IMA group parameters, perform the following steps:

Step 1 Establish a configuration session with the active card.

Step 2 If you are in the Frame Relay CLI context, enter the setctx atm command to change to the ATM CLI context:

M8830_CH.12.MPSM155[FR].a > setctx atm

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 Enter the cnfimagrp command to change IMA group parameters. To display the current configuration of the group, enter the dspimagrp < group> command. Replace <group> with the number of the IMA group you want to display.

M8830_CH.12.MPSM155[FR].a > cnfimagrp <-grp group> [-ver <version>] [-txm <minLinks>] [-txid <txImaId>] [-txfl <txFrameLen>] [-dd <diffDelayMax>] [-uptim groupUpTime] [-dntim <groupDownTime>] [-vfb <verFallback> [-mode <autoRestart>] [-rxid <rxImaIdExpected>] [-cm <txclkMode>]

Table 6-33 describes cnfimagrp command parameters.

Table 6-33 cnfmagrp Command Parameters

Parameter

Description

-grp

Specifies the IMA group.

•MPSM-T3E3-155 range: 1-42

•MPSM-16-T1E1 range: 1-16

Note To see a list of all IMA groups on the current card, enter the dspimagrps command.

-ver

The version number of ATM Forum IMA specification.

•1 = Version 1.0

•2 = Version 1.1

-txm

The minimum number of links that must be operational before the IMA group is operational.

•MPSM-T3E3-155 range: 1-16

•MPSM-16-T1E1 range: 1-8

For example, if you create an IMA group of 4 links and specify a minimum number of 3 links, then 3 of the 4 specified links must be operational before the IMA group can be used.

-txid

The IMA ID number transmitted in the IMA ID field of the ICP cell, in the range 0-255.

-txfl

The length of transmitted IMA frame in megabytes. For IMA Version 1.0, the txImaFrameLength value is 128. For Version 1.1, the txImaFrameLength value can be 32, 64, 128, or 256.

-dd

The maximum differential delay in milliseconds.

•T1 range: 1-275 ms

•E1 range: 1-220 ms

-uptim

Group uptime, in the range 0-400000 milliseconds. Default: 10000

-dntim

Group downtime in the range 0-100000 milliseconds. Default: 2500

-vfb

Enables or disables version fallback on the IMA group.

•1 = Enable version fallback

•2 = Disable version fallback

Note Before you enable version fallback for individual IMA groups, you must enable version fallback on the card level. See cnfimaparms -fallback.

-mode

Configures IMA auto restart functionality for the current group.

•1 = Disable IMA autorestart

•2 = Relearn IMA autorestart

•3 = Resume a previous IMA autorestart

Note Before you enable autorestart for individual IMA groups, you must enable autorestart on the card level. See cnfimaparms -restart.

-rxid

Identifies the expected received IMA ID, either -1 or in the range 1-255.

-cm

Sets the transmit clock mode.

Note Applies to MPSM-16-T1E1 only.

In the following example, the user modifies the IMA group uptime and IMA group downtime, and enables version fallback for IMA group 1.

M8850_NY.13.MPSM155[ATM].a > cnfimagrp -grp 1 -uptim 10000 -dntim 100 -vfb 1

Step 4 To verify IMA group configuration changes, enter a dspimagrp <group> command for the appropriate IMA group. Replace <group> with the number of the IMA group you modified.

In the following example, the user verifies the changes made to IMA group 1.

M8850_NY.13.MPSM155[ATM].a > dspimagrp 1
Group Number : 1
NE IMA Version : 1.1
Group Symmetry : Symm Operation
Tx Min Num Links : 1
Rx Min Num Links : 1
NE Tx Clk Mode : CTC
FE Tx Clk Mode : CTC
Tx Frame Len (bytes) : 128
Rx Frame Len (bytes) : 128
Group GTSM : Down
NE Group State : StartUp
FE Group State : StartUp
Group Failure Status : StartUp NE
Tx Ima ID : 100
Rx Ima ID : 0
Max Cell Rate (c/s) : 0
Avail Cell Rate (c/s) : 0
Diff Delay Max (msecs) : 150
Diff Delay Max Observed (msecs) : 0
Accumulated Delay (msecs) : 0
Clear Accumulated Delay Status : Not In Progress
GTSM Up Integ Time (msecs) : 10000

Type <CR> to continue, Q<CR> to stop:
GTSM Dn Integ Time (msecs) : 100
Num Tx Cfg Links : 0
Num Rx Cfg Links : 0
Num Act Tx Links : 0
Num Act Rx Links : 0
Least Delay Link : Unknown
Tx Timing Ref Link : Unknown
Rx Timing Ref Link : Unknown
Group Running Secs : 0
Alpha Val : 2
Beta Val : 2
Gamma Val : 1
Tx OAM Label : 3
Rx OAM Label : 0
Test Pattern Procedure Status : Disabled
Test Link : Unknown
Test Pattern : 255
Stuff Cell Indication (frames) : 1
Version Fallback Enabled : true
Auto-Restart Mode : disable
Rx IMA ID Expected : -1
Auto-Restart Sync State : disable

Configuring an IMA Link

To configure IMA link parameters, perform the following steps:

Step 1 Establish a configuration session with the active card.

Step 2 If you are in the Frame Relay CLI context, enter the setctx atm command to change to the ATM CLI context, as shown in the following example:

M8850_SF.27.MPSM16T1E1[ATM].a > setctx atm

Note The current service context appears within brackets next to the switch name in the switch prompt.

Step 3 To modify the configuration of an IMA link, enter the cnfimalnk command in the ATM CLI context as follows. To display all IMA links and the groups to which they belong, enter the dspimalnks command.

M8850_SF.27.MPSM16T1E1[ATM].a > cnfimalnk -lnk <line/pathId>, -uplif <lifUpTime>, -dnlif <lifDnTime>, -uplods <lodsUpTime>, -dnlods <lodsDnTime>

Table 6-34 describes cnfimalnk command parameters.

Table 6-34 Parameters for cnfimalnk Command

Parameter

Description

-lnk

The link (line or path) in the IMA group to configure:

•Physical line: bay.line[:ds1]

•DS3 payload: bay.line.sts:ds1

•VT payload: bay.line.sts:vtg.vt

•VT structured: bay.line.sts:tug3.vtg.vt

where: bay = 1, line = 1-3, sts = 0-3, ds1 = 1-28,
tug3 = 1-3, vtg = 1-7, vt = 1-4 (VT15) or 1-3 (VT2)

Note The MPSM-16T1E1 requires all links in an IMA Group be within lines 1-8 or 9-16. For example, an IMA Group with lines 7, 8, and 9 is not valid.

Note To view a list of all line or path numbers on the current card, enter the dsplns or dsppaths command.

-uplif

LIF integration uptime, in the range 0-25000 milliseconds. The LIF (Loss of IMA Frame) defect is the occurrence of persistent OIF (Out of IMA Frame) anomalies for at least 2 IMA frames.

-dnlif

LIF integration downtime, in the range 0-25000 milliseconds. The LIF (Loss of IMA Frame) defect is the occurrence of persistent OIF (Out of IMA Frame) anomalies for at least 2 IMA frames.

-uplods

LODS integration uptime, in the range 0-25000 milliseconds. The LODS (Link Out of Delay Synchronization) is a link event indicating that the link is not synchronized with the other links within the IMA group.

-dnlods

LODS integration downtime, in the range 0-25000 milliseconds. The LODS (Link Out of Delay Synchronization) is a link event indicating that the link is not synchronized with the other links within the IMA group.

In the following example, the user modifies the IMA link 1.2:2 so that is has a link LIF uptime of 20000, a Link LIF downtime of 10000, a Link LODS uptime of 2500, and a link LODS integrated downtime of 10000:

M8850_SF.27.MPSM16T1E1[ATM].a > cnfimalnk -lnk 1.5 -uplif 20000 -dnlif 10000 -uplods 2500 -dnlods 10000
Deleting Lines from an IMA Group

To delete a line from an IMA group, enter the delimalnk <link> command in the ATM CLI context as follows. Replace <link> with the number of the IMA link you plan to delete.

Note Deleting a line from an IMA group reduces the available throughput for the group and may have an impact on ATM traffic through the group. Also, the switch does not allow you to delete lines when the resulting number of lines equals less than the minimum number of lines specified for group operation. To change the minimum number of lines for an IMA group, use the cnfimagrp command.

In the following example, the user deletes the IMA link 1.1:5:

NodeB.6.MPSM155[ATM].a > delimalnk 1.1:5
Deleting an IMA Group

To delete an IMA group, perform the following procedure in the ATM CLI context.

Step 1 Delete all connections that are associated with the IMA group (dspcons and delcon commands).

Step 2 Delete all ports that are associated with the IMA group (dspports and delport commands).

Step 3 Delete all links that are associated with the IMA group (dspimalnks and delimalnk commands).

Step 4 Enter the delimagrp <group> command to delete the IMA group. Replace group with the number of the IMA group you want to delete, in the range from1 through 16. To display existing group numbers, enter the dspimagrps command.

The following example shows how to use the delimagrp command:

NodeB.6.MPSM155[ATM].a > delimagrp 12

Step 5 Enter the dspimagrps command to verify that the appropriate IMA group is deleted.

Administratively Enabling and Disabling IMA

You can administratively enable or disable an IMA group. You typically disable an IMA group to change the configuration or perform other maintenance.

Disabling IMA

To disable an IMA group, enter the dnimagrp <group> command in the ATM CLI context. Replace <group> with the number of the IMA group you want to disable.

Note When an IMA group is disabled, no user traffic can flow through that IMA group.

In the following example, the user disables the IMA group 11.

mpsm_node.5.MPSM155[ATM].a > dnimagrp 11
Warning: Traffic loss will result on all connections on this IMA group.
Do you want to proceed (Yes/No) ? y
Enabling IMA

To enable an IMA group, enter the upimagrp <group> command. Replace <group> with the number of the IMA group you want to enable.

In the following example, the user enables the IMA group 11.

mpsm_node.5.MPSM155[ATM].a > upimagrp 11

Note When an IMA group is enabled, that IMA group is ready to carry ATM traffic.

Testing an IMA Link

You can check the validity of an IMA connection by sending a test pattern to the link. If the test pattern is the same when it arrives at the receive endpoint of the link, then the link is valid. If the test pattern is different or does not arrive, then the link is invalid. You can run only one test at a time.

To perform a connectivity test on an IMA link, perform the following steps in the ATM CLI context:

Step 1 Establish a configuration session with the appropriate card using a username with Group1 privileges or higher.

Step 2 To start an IMA test on an IMA link, enter the startimalnktst command as follows. To display all existing IMA links and the groups to which they belong, enter the dspimalnks command.

startimalnktst <group> <link> <testPat>

Replace <group> with the number of the IMA group that owns the link you want to test. Replace <link> with the number of the IMA link or path you want to test. Replace <testPat> with the number of the transmit test pattern, in the range 0-254.

Note If no value is entered, -1 is the default, which causes the program to select a pattern.

In the following example, the users starts an IMA link test on IMA group 1, link 1.1.1:1.1, using test pattern 1:

M8830_CH.4.MPSM155[ATM].a > startimalnktst 1 1.1.1:1.1 -pat 1

Step 3 To stop a IMA link test launched using the startimalnktst command, enter the stopimalnktst <group> command. Replace <group> with the number of the IMA group that owns the link that is being tested.

In the following example, the user stops an IMA link test that is running on IMA group 1:

NodeB.5.MPSM155[ATM].a > stopimalnktst 1

Modifying an IMA Link Test

To modify an IMA test link or IMA test pattern after the test is started, enter the cnfimalnktst command as follows:

NodeB.6.MPSM155[ATM].a > cnfimalnktst -grp <group> -lnk <link> -pat <testPat>
Replace <group> with the number of the IMA group that owns the link whose test you want to modify. Replace <link> with the number of the IMA link or path whose test you want to modify. Replace <testPat> with the number of the transmit test pattern you want to modify, in the range 0-254.

In the following example, the user modifies the link test pattern on IMA group 1, link 1.2:2, to be 200.

NodeB.6.MPSM155[ATM].a > cnfimalnktst -grp 1 -lnk 1.2:2 -pat 200

Performing Loopback Tests

The MPSM-T3E3-155 and MPSM-16-T1E1 cards support line and channel loopbacks.

Line loopbacks can be enabled by:

•Manually placing the line in loopback mode using CLI commands

•Enabling loopback code detection using CLI commands

Channel loopbacks are enabled through use of the following CLI commands on the cards:

•addlnloop—Add local or remote loopback

•dellnloop—Delete local or remote loopback

For more information on the use of these commands, see Chapter 7, "Command Reference."

Performing Bit Error Rate Tests

Bit Error Rate Testing (BERT) is used to determine the health of a full Frame Relay T1 or E1 line, or can be run on a fractional T1 or E1 line, such as one DS0 or group of DS0s. 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 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, because it is a diagnostic feature. However, 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 or other kinds of traffic (such as AIS) reporting the channel alarms. This might negatively impact the performance of other functions.

A typical sequence in performing Bit Error Rate Testing consists of the following steps:

1. Place the far end interface on the attached end-user equipment in loopback mode if it does not support loopback code detection.

2. Configure BERT. The user can configure the following parameters:

–Type of loopback (The loopbacks configured are enabled when the BERT is started and deleted when the BERT is stopped)

–Pattern to transmit

–Error rate insertion

3. Start BERT—Start the Bit Error Rate Test on the specified interface. Generate the test pattern and detect the incoming pattern. Compare the two patterns and update the counters.

4. Display BERT results— Display the bit error count and the bit error rate.

5. Stop BERT—Stop generating the test pattern and the Bit Error Rate test.

The following topics describe how to manage Bit Error Rate Tests using the onboard BERT functionality:

• Onboard BERT Features

• Managing a BERT Session

Onboard BERT Features

Onboard BERT features include:

•The onboard BERT session is initiated from the MPSM-T3E3-155 or MPSM-16-T1E1 card.

•Only one BERT session per line is supported.

•On the MPSM-T3E3-155, a total of 6 concurrent BERT sessions on T1 paths is supported. BERT sessions are not supported on NxDS0 or E1 paths.

•On the MPSM-16-T1E1, a total of 16 concurrent BERT sessions on NxDS0 and T1/E1 interfaces is supported.

•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-T3E3-155 or MPSM-16-T1E1 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 6-35 describes the onboard BERT commands supported by the MPSM-T3E3-155 and MPSM-16-T1E1 cards. For more information on the use of these commands, see Chapter 7, "Command Reference."

Table 6-35 Onboard BERT Commands

Command

Enter this command to�

addbert

Add a Bit Error Rate Test to a line, path, or port.

cnfbert

Configure a Bit Error Rate Test on a line, path, or port.

startbert

Begin the Bit Error Rate Test configured on the specified line, path, or port.

dspbert

View the BERT parameters configured using the cnfbert command and to view the status of the current BERT session.

dspbertstat

View statistics for a Bit Error Rate Test. Use this command to view changing statistics while the Bit Error Rate Test is running or to view the total statistics accumulated during the test period (after testing has stopped).

insbiterror

Use this command to insert single bit errors into the transmitted BERT pattern configured on the specified path.

stopbert

Enter this command to stop the Bit Error Rate Test running on the specified line, path, or port.

delbert

Enter this command to remove a Bit Error Rate Testing configuration from a line, path, or port. Use this command to delete a BERT session that is running or after the BERT session stops.

Managing a BERT Session

The following restrictions apply to bert tests:

•The MPSM-T3E3-155 supports a total of 6 concurrent BERT sessions on T1 paths only; BERT sessions on NxDS0 or E1 paths are not supported.

•The MPSM-16-T1E1 supports a total of 16 concurrent BERT sessions on NxDS0 and T1 or E1 lines.

To manage a Bit Error Rate Test using the MPSM-T3E3-155 or MPSM-16-T1E1 onboard BERT feature, perform the following procedure:

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 username with Group1 privileges or higher.

Step 3 To add a BERT session to a specific line, path, or port, enter the addbert command as follows:

M8830_CH.12.MPSM155[FR].a > addbert <bertIfNum>

Replace <bertIfNum> with the number of the line, path, or port to which you want to add a BERT session.

Note To see all DS1 (T1) path numbers on the current card on the MPSM-T3E3-155, enter the dsppaths -ds1 command. On the MPSM-16-T1E1 card, enter the dsplns or the dspports command to see all of the lines and ports on the current card.

Step 4 To configure a BERT session, enter the cnfbert command as follows:

M8830_CH.12.MPSM155[FR].a > cnfbert <bertIfNum> [-tp <test pattern>] [-tpi <transmit pattern inverse>] [-rpi <receive patter inverse>] [-eir <error insertion rate>][-lpbk <loopbackCode>]

Table 6-36 lists and describes the parameters for the cnfbert command on the MPSM-T3E3-155 and MPSM-16-T1E1 cards.

Table 6-36 cnfbert Command Parameters

Parameter

Description

ifNumber

Specifies the line, path, or port number to test.

When you enter the cnfbert command with only the interface number specified with no other options selected, the Bit Error Rate Test is configured using the defaults: test pattern all zeros, no loopback, and no error insertion rate.

-tp

Specifies the BERT test pattern to configure, in the range 1-38. For a description of all the available BERT test patterns on the MPSM-T3E3-155 and MPSM-16-T1E1 cards, see Table 7-13 (under the cnfbert command description) in Chapter 7, "Command Reference."

Note You can also enter the dspbertcap CLI to see the supported Loopback codes and their associated numbers for the line.

-tpi

Controls inversion of the transmit BERT pattern:

1 = Not inverted
2 = Inverted

-rpi

Controls inversion of the received BERT pattern:

1 = Not inverted
2 = Inverted

-eir

Inserts bit errors in the transmitted pattern at the following rates:

1 = noError(1): no errors
2 = oneInTen: 1 bit error per 10 bits
3 = oneInHundred: 1 bit error per 100 bits
4 = oneInThousand: 1 bit error per 1000 bits
5 = oneIn10Thousand: 1 bit error per 10,000 bits
6 = oneInHundredThousand: 1 bit error per 100,000 bits
7 = oneInMillion: 1 bit error per 1,000,000 bits
8 = oneInTenMillion: 1 bit error per 10,000,000 bits

-lpbk

Loopback code number, in the range from 1 through 18.

Note To see the supported Loopback codes and their associated numbers for the line, enter the dspbertcap CLI.

The following example configures the Bit Error Rate Test pattern 25 on the path 1.1:1. In this example, the use configures the transmit BERT pattern to be inverted.

M8830_CH.12.MPSM155[FR].a > cnfbert 1.1:1 -tp 25 -tpi 2

Step 5 To view the BERT parameters configured using the cnfbert command, enter the dspbert command:

M8830_CH.12.MPSM155[FR].a > dspbert <bertIfNumber>

Replace the bertIfNumber parameter with the line, path, or port number configured for the BERT session.

The following example shows the BERT parameters configured in the previous step:

M8830_CH.12.MPSM155[FR].a > dspbert 1.1:1
BertIfNum : 1.1:1
BERT Admin Status : Down
Operational Status : OutOfSync
BERT Pattern : TwoE20MinusOneQRSS
Error Insertion Rate: NoError
Tx Pattern Invert : Inverted
Rx Pattern Invert : NotInverted
Loopback Code : noLoopbackCode
Start Date :

Step 6 To start a Bit Error Rate Test, enter the startbert command as follows:

M8830_CH.12.MPSM155[FR].a > startbert <bertIfNumber>

Replace the bertIfNumber parameter with the line, path, or port number configured for the BERT session. The following example starts a BERT session on the path 1.1:1:

M8830_CH.12.MPSM155[FR].a > startbert 1.1:1

Step 7 To verify the start of the Bit Error Rate Test, enter the dspbert command:

M8830_CH.12.MPSM155[FR].a > dspbert 1.1:1
BertIfNum : 1.1:1
BERT Admin Status : Up
Operational Status : OutOfSync
BERT Pattern : TwoE20MinusOneQRSS
Error Insertion Rate: NoError
Tx Pattern Invert : Inverted
Rx Pattern Invert : NotInverted
Loopback Code : noLoopbackCode
Start Date : Apr 02 2004 00:27:11

In this example, an operational status of In Sync indicates that the test is successfully started.

Step 8 To view statistics from a Bit Error Rate Test in progress, enter the dspbertstat command as follows:

M8830_CH.12.MPSM155[FR].a > dspbertstat <bertIfNumber>

Replace the bertIfNumber parameter with the line, path, or port number configured for the BERT session. The following example displays statistics from a BERT session in progress:

M8830_CH.12.MPSM155[FR].a > dspbertstat 1.1:1
Bert Bits Bit Errors Single Bit
IfNum Received Received Errors Injected
--------- ---------- ---------- ---------------
1.1:1 2880 820 0

To view the total statistics gathered during a BERT session after the test stops, also use the dspbertstat command.

Step 9 To insert one bit errors into an active BERT session, enter the insbiterror command as follows:

M8830_CH.12.MPSM155[FR].a > insbiterror <path_num>

Replace the bertIfNumber parameter with the line, path, or port number configured for the BERT session. The following example inserts one bit error into the BERT session in progress:

M8830_CH.12.MPSM155[FR].a > insbiterror 1.1:1

Step 10 To stop a BERT session, enter the stopbert command:

M8830_CH.12.MPSM155[FR].a > stopbert <bertIfNumber>

Replace the bertIfNumber parameter with the line, path, or port number configured for the BERT session. The following example shows how to stop the current BERT session:

M8830_CH.12.MPSM155[FR].a > stopbert 1.1:1

After a BERT session stops, it may be restarted by using the startbert command.

Step 11 To clear a BERT configuration, enter the delbert command as follows:

M8830_CH.12.MPSM155[FR].a > delbert <bertIfNumber>

Replace the bertIfNumber parameter with the line, path, or port number configured for the BERT session. The following example shows how to clear a current BERT session configuration:

M8830_CH.12.MPSM155[FR].a > delbert 1.1:1

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 using the cnfbert command.

Managing MPSM Core Dumps

The following topics describe managing MPSM core dumps:

• Overview of MPSM Core Dumps

• Managing Core Dump Files

• Aborting Core Dumps

• Displaying Core Command Options

• Displaying Core Dump Settings

• Displaying the Core Dump Mask

• Configuring Core Dump Settings

• Hot-Dumping the Core

Overview of MPSM Core Dumps

The core command is used to manage core memory dumps on the MPSM-T3E3-155 and MPSM-16-T1E1 cards. This command is supported on 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 use in a production network. When such errors occur, it is imperative to capture the software image in memory and the hardware configurations so that troubleshooting can be performed.

Core memory dumps are supported on cards that are in redundancy groups, and on non-redundant cards.

When a software or hardware error condition requiring a reset occurs, the card will be reset after writing the reset reason to the NVRAM. The boot code then examines 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 To support cold-dumps from a non-redundant card, you must set the PXM core red-policy command to enable.

The cards also support 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 a card.

The PXM processor card allows multiple cold-dumps and hot-dumps of the MPSM core memory from different 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 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 troubleshooting.

Aborting Core Dumps

To abort both hot-dumps and cold-dumps of the core memory on the card, use the PXM core abort-dump <slot> command.

Cold-dumps of the MPSM core memory are aborted if any of the following events occur:

•The 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 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 are aborted if any of the following events occur:

•The 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 card.

•The PXM switchredcd command is performed during a hot-dump in progress on the active card in a redundancy group.

•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:

M8830_CH.4.MPSM155[FR].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 )
Displaying Core Dump Settings

To display the current core dump settings on the card, enter the core command without any arguments. The following example shows the core dump settings on a card that has automatic core dumping enabled and where the saved core images are located:

M8830_CH.4.MPSM155[FR].a > core
Automatic core dumping is enabled for this slot.

Saved core images are on PXM's hard disk (C:/).
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 is on, the associated hexadecimal number is an element of the mask.

To display the current core dump mask and the error conditions for which a core dump is enabled, enter the core mask command as shown:

M8830_CH.4.MPSM155[FR].a > core mask
Automatic core dumping is enabled for this slot.
The current core mask is 0x262ee.

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
ON 00040 Reset because of PXM Low Voltage
ON 00080 Reset By Event Log Task
OFF 00100 Reset from Shell
ON 00200 Unknown
OFF 00400 Reset from PXM
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

In this example, the mask is set to the default mask of 0x262ee. To change the mask, see the "Changing the Core Dump Mask" section.

A reason that cannot trigger a core dump is indicated in the preceding example—can't be turned on. A reset reason that can't be turned on removes debugging information from memory and therefore is excluded from being part of the mask.

Configuring Core Dump Settings

The following topics describe the configuration of core dump settings:

• Enabling Automatic Core Dumping

• Disabling Automatic Core Dumping

• Changing the Core Dump Mask

• Restoring the Default Core Dump Mask

Enabling Automatic Core Dumping

To enable automatic core dumping, enter the core enable command:

M8830_CH.4.MPSM155[FR].a > core enable
Automatic core dumping is enabled for this slot.
Disabling Automatic Core Dumping

You may want to disable automatic core dumps for the 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 card may be of such high priority that you do not want to dump core memory to disk.

•The 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 cards. Setting the core red-policy command to disable does not disable hot-dumps of the core memory.

To disable automatic core dumping, enter the core disable command:

M8830_CH.4.MPSM155[FR].a > core disable
Automatic core dumping is ** disabled ** for this slot.

The use of this command is similar to setting the mask to 0x0.

Changing the Core Dump Mask

To change the core dump mask, enter the core mask command as follows:

M8830_CH.4.MPSM155[FR].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 0x262ee is changed to 0x263ae:

M8830_CH.4.MPSM155[FR].a > core mask 263ae
Automatic core dumping is enabled for this slot.
The current core mask is 0x263ae.

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
ON 00080 Reset By Event Log Task
ON 00100 Reset from Shell
ON 00200 Unknown
OFF 00400 Reset from PXM
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

Note When automatic core dumping is disabled, changing the mask does not have any effect until the core dump feature is enabled using the core enable command.

Restoring the Default Core Dump Mask

To restore the default core dump mask, enter the core mask default command as shown:

M8830_CH.4.MPSM155[FR].a > core mask default
Automatic core dumping is enabled for this slot.
The current core mask is 0x262ee.

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
ON 00040 Reset because of PXM Low Voltage
ON 00080 Reset By Event Log Task
OFF 00100 Reset from Shell
ON 00200 Unknown
OFF 00400 Reset from PXM
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

If you add all of the reset reasons that are `on' in the default mask, the sum is the hexadecimal number 0x262ee.

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 a card.

To initiate a hot-dump of the core, enter the core hot-dump command as follows:

M8830_CH.4.MPSM155[FR].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 fails.

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 is initiated and saved to a user-specified file with the name of dump28.zip:

M8830_CH.4.MPSM155[FR].a > core hot-dump dump28.zip
Do you want to proceed (Yes/No)? y
Collecting WinCore
Finished collecting WinCore

Creating dump28.zip
.......................................................................................... ..........
Done.

Note To abort a hot-dump and cold-dump of the core memory on the card, use the PXM core abort-dump <slot> command.

Command	Description
? Help	Displays available commands.
clrscrn	Clears the session window.
timeout	Sets the amount of idle time in a user-session. Default time is 10 minutes.
who whoami	Displays details about the user currently logged into a card.

Argument	Value	Description
priority	primary or secondary	Clock source type. Replace the priority argument with the type of clock source for the card. This argument can be either primary or secondary (the latter is the default value).
shelf	1	Shelf identifier (optional). The shelf value is always 1.
slot	MGX 8850 (PXM1E/PXM45): 1 to 6, 9 to 22, and 25 to 32 MGX 8830: 3 to 14	Slot identifier. Identifies the slot number of the card that is to receive the clock signal.
ifnum	1 to 1003	Interface number. Corresponds to the interface number or logical port number which can range from 1 to 1003. The interface number must be previously defined by means of the addport command.

Option	Description
gen	Displays general SCT parameters.
vcThr	Displays virtual circuit threshold parameters.
cosThr	Displays COSB threshold parameters.

Parameter	Range	Description
SERV-TYPE	—	Service type (for example, CBR, VBR, ABR) to which the parameters in this table apply (for example, COSB_NUM, CAC_TYPE, UPC_ENB).
COSB_NUM	1 to 16	Class of Service Buffer Number. The number that identifies one of the sixteen CoS buffers. A CoS buffer is a buffer that services connections with similar QoS requirements.
CAC_TYPE	LCN_CAC B_CAC E_CAC	Connection Admission Control. Used by an ATM switch during setup to determine if a connection requested QoS conforms to the guaranteed QoS standards for ATM connections. •LCN_CAC: Logical Connection Number CAC •B_CAC: Basic-CAC •E_CAC: Enhanced-CAC
UPC_ENB	ENABLED DISABLED	Usage Parameter Control Enable. Enables or disables GCRA policing functions on the connection.
GCRA-1	1 to 3	Generic Cell Rate Algorithm—Bucket 1. In ATM, an algorithm that defines conformance with respect to the traffic contract of the connection. For each cell arrival, the GCRA determines if the cell conforms to the traffic contract. Note If UPC-Enable is set to disable, this object is not used. Choose one of the following options to indicate how cells that fail the first bucket of the policer should be handled: •1—Discard •2—Set CLP bit •3—Set CLP of untagged cells, discard tagged cells
GCRA-2	1 to 3	Generic Cell Rate Algorithm—Bucket 2. In ATM, an algorithm that defines conformance with respect to the traffic contract of the connection. For each cell arrival, the GCRA determines if the cell conforms to the traffic contract. Note If UPC-Enable is set to disable, this object is not used. Choose one of the following options to indicate how cells that fail the second bucket of the policer should be handled: •1—Discard •2—Set CLP bit •3—Set CLP of untagged cells, discard tagged cells

Label	Range and Units	Description
SERV-TYPE	—	The service type (for example, CBR, VBR, ABR) to which the parameters (for example, EFCI, CLP_HI, EPD0) in this table apply.
MAX_CELL THR (uSec)	—	Indicates the MAX number of cells that can be buffered in the cell memory for that VC.
EFCI (.0.0001%)	1000000 = 100%	Indicates the threshold for Explicit Forward congestion Indication (EFCI). EFCI is represented as a percentage of the MAX_CELL THR. A value of 1000000 is equal to 100%.
CLPlo/EPD1 (.0.0001%)	1000000 = 100%	Indicates the minimum delay any CLP1cell entering this VC encounters. If packet mode is enabled for the VC, then the cells are treated as EPD1 cells. The CLP/EDP1 threshold is represented as a percentage of the MAX_CELL THR. A value of 1000000 is equal to 100%.
CLPhi (.0.0001%)	1000000 = 100%	Indicates the maximum delay any CLP cell entering this VC will encounter. Any cell that encounters a queue latency greater than the CLPhi will be dropped. The CLPhi is represented as a percentage of the MAX_CELL THR. A value of 1000000 is equal to 100%.
EPD0 (.0.0001%)	1000000 = 100%	Indicates the maximum threshold for the EPD0 cells. Any cell that encounters a queue latency greater than the EPD0 threshold will be dropped. The EPD0 is represented as a percentage of the MAX_CELL THR. A value of 1000000 is equal to 100%.

Index	Scaling Class Table #1 (CBR)	Scaling Class Table #2 (VBR)	Scaling Class Table #3 (ABR)	Scaling Class Table #4 (UBR)
0	100.00%	100.00%	100.00%	100.00%
1	100.00%	100.00%	100.00%	100.00%
2	100.00%	100.00%	100.00%	100.00%
3	100.00%	100.00%	100.00%	100.00%
4	100.00%	100.00%	100.00%	100.00%
5	100.00%	100.00%	100.00%	100.00%
6	100.00%	100.00%	100.00%	67.00%
7	100.00%	100.00%	100.00%	34.00%
8	100.00%	100.00%	50.00%	20.00%
9	100.00%	50.00%	25.00%	12.00%
10	100.00%	25.00%	12.00%	8.00%
11	100.00%	12.00%	6.00%	4.00%
12	100.00%	6.00%	3.00%	2.50%
13	100.00%	3.00%	1.30%	1.40%
14	100.00%	1.30%	0.75%	1.00%
15	100.00%	0.50%	0.50%	0.50%

Label	Range and Units	Description
COSB	—	The service type (for example, CBR, VBR, ABR) to which the parameters (for example, EFCI, CLP_HI, EPD0) in this table apply.
MAX_THR (usec)	0-5000000 microseconds	Indicates the maximum delay, in microseconds, that any CLP (0+1) cells entering this COSB might encounter. Any cell that encounters a queue latency greater than the MAX_THR are dropped.
FR_MAX_THR	0-5000000 microseconds	Indicates the maximum threshold on the payload memory that all Frame Relay VCs belonging to the same class of service occupy. The threshold is expressed as a percentage of the MAX_THR. A value of 1000000 is equal to 100%.
DE_THR	1000000 = 100%	Indicates the maximum threshold beyond which all Frame Relay cells marked with DE must be dropped. The threshold is expressed as a percentage of the MAX_THR. A value of 1000000 is equal to 100%.
FECN_THR	1000000 = 100%	Indicates the maximum threshold, in microseconds, beyond which all Frame Relay cells marked with FECN must be dropped. The threshold is expressed as a percentage of the MAX_THR. A value of 1000000 is equal to 100%.

Parameter	Range	Description
SERV-TYPE	—	The service type (for example, high priority Frame Relay) to which the parameters in this table apply.
DE TAG ENABLE	ENABLED DISABLED	Enables/disables DE tagging in the ingress direction.
FECN TO EFCI	MAP SET_ZERO	Sets the FECN configuration to one of the following options: •MAP—The Frame Relay FECN bits are mapped to EFCI bits in ATM cells. •SET_ZERO—The FECN bits are ignored, and the EFCI bit is set to zero.
DE TO CLP MAP	MAP SET_ZERO SET_ONE	Sets the DE configuration to MAP, SET_ZERO, or SET_ONE. •MAP—The Frame Relay DE bits are mapped to CLP bits in ATM cells. •SET_ZERO—The DE bits are ignored, and the CLP bit is set to zero. •SET_ONE—The DE bits are ignored, and the CLP bit is set to one.
CLP TO DE MAP	MAP SET_ZERO SET_ONE IGNORE_CLP	Sets the CLP configuration to MAP, SET_ZERO, or SET_ONE. •MAP—The ATM CLP bits are mapped to DE bits in Frame Relay cells. •SET_ZERO—The CLP bits are ignored, and the DE bit is set to zero. •SET_ONE—The CLP bits are ignored, and the DE bit is set to one. •IGNORE—The CLP bits are ignored, and the DE bit remains as it is when it is received.

Error	Alarm Type	Transmit Downstream	Transmit Upstream	Comments
LOS (Loss of Signal)	Red	If a connection exists on the line, AIS OAM cells are transmitted over that connection.	RAI	Send line alarm trap
LOF (Loss of Frame)	Red	If a connection exists on the line, AIS OAM cells are transmitted over that connection.	RAI	Send line alarm trap
AIS (Alarm Indication Signal)	AIS (Yellow) when receiving AIS on the line	If a connection exists on the line, AIS OAM cells are transmitted over that connection.	RAI	Send connection alarm trap
MFAIS (E1 CAS only)	AIS (Yellow) when receiving AIS on the line	If a connection exists on the line, AIS OAM cells are transmitted over that connection.	RAI	Send line alarm trap
RAI (Remote Alarm Indication)	Yellow	—	—	Send line alarm trap
MFRAI (E1 CAS only)	Yellow	—	—	Send line alarm trap
Loss of Multi-frame Sync (E1 CAS only)	Red	If a connection exists on the line, AIS OAM cells are transmitted over that connection.	RAI	Send line alarm trap
Loss of CRC MF Alignment (E1 CRC only)	Red	If a connection exists on the line, AIS OAM cells are transmitted over that connection.	RAI	Send line alarm trap

Command	Purpose
clradjlnalmcnt	Clears the statistical alarms and alarm counters for the adjacent back card in an automatic protection system (APS) configuration.
clrlnalmcnt	Clears the statistical alarms and alarm counters for a specific line.
clrpathalmcnt	Clears all the current alarm counters on the specified path (path_num). All counters are reset to zero.
cnflnalm	Configures statistical line alarms thresholds. You can use this command to make the lines more or less sensitive to alarms.
cnfpathalm	Configures a specified statistical alarm threshold for a specified path (path_num). It also configures the severity of the alarm.
dspadjlnalm	Displays the line alarm status for the adjacent back card.
dspadjlnalmcnt	Displays the alarm counters for the adjacent back card.
dsplnalm	Display the line and statistical alarm state for the specified line.
dsplnalms	Displays line and statistical alarms for all lines on the current card.
dsppathalm	Displays the following alarm information for the specified path (path_num).
dsppathalms	Displays the following alarm information for all the specified paths (path_filter).
dsplnalmcnf	Displays the current statistical line alarm thresholds on the specified line.
dsplnalmcnt	Displays the alarm counters for the specified line.

Command	Purpose
dspmfrbundlealm	Displays alarms and statistics for an MFR bundle.
dspmfrbundlealms	Displays alarms and statistic for a all MFR bundles.
dspmfrlnkalm	Displays alarms and statistics for an MFR link.
dspmfrlnkalms	Displays alarms and statistic for a all MFR links.

Column	Description
MFRBundle	The bundle number.
Activation Class	•Class A—At least one bundle link must be operational for the MFR bundle to be operational •Class B—All of the bundle links must be operational for the MFR bundle to be operational •Class C—Configured number of bundle links must be operational for the MFR bundle to be operational
Minimum Links	Minimum number of links for the bundle to be operational.
Configured Links	Number of links configured on the bundles.
Active Links	Number of active links.
Admin State	Admin state, as controlled by upmfrbundle and dnmfrbundle.
Oper State	Up—The MFR bundle is negotiated and accepted, and the minimum number of links are operational. Down—The following are possible causes for a bundle to be down: •Bundle is in admin down state •Insufficient or no links in this bundle are operational •Insufficient or no links are added to this bundle
Max Diff Delay	The maximum differential delay in the bundle.

Parameter	Description
-bundle	MFR bundle number, range 1-42
-class	Bundle activation class: •1 = Class A—At least one bundle link must be operational for the MFR bundle to be operational •2 = Class B—All of the bundle links must be operational for the MFR bundle to be operational •3 = Class C—Configured number of bundle links must be operational for the MFR bundle to be operational
-minlinks	Minimum number of links for class-C activation class. Range 1-12
-hellotimer	Interval for sending hello messages. Range 1-180 seconds
-acktimer	Maximum time period to wait for an acknowledgement from the far en. Range 1-10 seconds
-maxretry	Maximum number of retries (maximum retries). Range 1-5 retries
-bname	Near-end bundle name: A null-terminated string consisting of ASCII characters A-Z, a-z, 0-9, and any printable characters, with a maximum of 49 characters.

Column	Description
Link Num	Link (path id) for the link.
Bundle Num	Number of the bundle of which the link is a member.
Link State	Current state of link activation.
Link Alarm State	Link alarm, if any.
Link Delay	Link delay, in ms.
PHY Oper State	Up—MFR link is negotiated and accepted. Down—MFR link is not negotiated nor accepted.

Parameter	Description
-link	Link identifier: •DS3 payload: bay.line.sts:ds1 •VT payload: bay.line.sts:vtg.vt •VT structured: bay.line.sts:tug3.vtg.vt where: bay = 1, line = 1-3, sts = 0-3, ds1 = 1-28, tug3 = 1-3, vtg = 1-7, vt = 1-4 (VT15) or 1-3(VT2)
-lname	Near-end link name: A null-terminated string consisting of ASCII characters A-Z, a-z, 0-9, and any printable characters with a maximum of 49 characters.

Column	Description
MLPPP Bundle	Bundle number.
Admin State	Administrative state, as controlled by upmpbundle and dnmpbundle.
Oper State	Operational state: •Up—The MLPPP is negotiated and accepted. At least one link is operational in this MLPPP bundle. •Down—The following are possible causes for an MLPPP bundle to be down: –Bundle is in admin down state –No link in this bundle is operational –No links are added to this bundle –PPP LCP negotiation with remote end failed on all links in this bundle –MLPPP LCP negotiation with remote end failed on all links in this bundle
Active Links	Number of operational links in the bundle.
Available Bandwidth	Aggregate bandwidth of the bundle.
Alarm Cause	Cause of the alarm for the bundle, if any.
MUX Status	State of PPPMUX for the bundle, either Enable or Disable.
Auto BW Mode	State of the dynamic bandwidth feature for bundle, either Enable or Disable.
WP Id	Winpath packet processing engine assigned to the bundle. (MPSM-T3E3-155 only)

Parameter	Description
-bundle	Specifies the MLPPP bundle number. Note Enter the dspmpbundles command to display all MLPPP bundles on the card.
-mrru	Specifies the Max Received Reconstructed Unit (MRRU), in the range 64 - 1524. After the user adds a link to an MLPPP bundle, the MRRU is sent to the remote end, which notifies the remote end that this link is capable of receiving MLPPP packets.
-endDisc	Describes the bundle endpoint. The value is null terminated string that contains printable ASCII characters, which include A-Z, a-z, and 0-9. Maximum length: 20 characters.

-bundle	Specifies the MLPPP bundle number. Enter the dspmpbundles command to display all MLPPP bundles on the card.
-q0threshold	Q0 threshold, range 0 - 65535 packets Default: 100
-q1threshold	Q1 threshold, range 0 - 65535 packets Default: 100
-q2threshold	Q2 threshold, range 0 - 65535 packets Default: 100
-normpvcbw	Normalized PVC bandwidth, range 0 - 176603 cps Default: 8600 cps
-autobw	Auto PVC bandwidth mode. When enabled, the bundle automatically negotiates the bandwidth on connections to the RPM-XF. •1 = enable •2 = disable

Column	Description
Link Number	PPP link number.
Admin State	Administrative state of the link, as controlled by upppplink and dnppplink.
Oper State	The operational state of the link. •up—The PPP is negotiated and accepted, and there are no other alarms on this PPP link. •down—Possible causes for PPP to be in a down state: –Physical layer is in alarm –PPP LCP negotiation with remote end failed on this link
Start DS0	The first DS0 in the link.
Number DS0	Number of DS0s in the link.
Bundle Number	Bundle to which the link is a member.
Bay.Line Number or Path ID	The link identifier: •MPSM-16-T1E1—The line number, in the format bay.line. •MPSM-T3E3-155—The path identifier for a channelized line.
PPP Link Description	The type of link: •LineSide—Identifies line-side links that were manually added to the bundle. •SwitchSide—Identifies switch-side links, which the MPSM automatically creates for the bundle.

Parameter	Description
-link	Specifies the PPP link number. Enter the dspppplinks command to display all PPP links on the card.
-mru	The Maximum Receive Unit, in the range 64-1524
-lcpTimeout	The length of time to wait for a Echo Reply before bringing down LCP. The value is in msec, rounded down to the nearest 100 msec. Range 1000-4294967.
-ds0speed	DS0 Speed •1 = 56K •2 = 64K
-pfcTx	Controls the compression of PF in PPP packets transmitted from this end. •1 = enable, PFC is performed if the far end is capable of receiving compressed PF. •2= disable, PFC is not performed, even if far end is capable of receiving compressed PF.
-acfcTX	Controls the compression of address/control fields in PPP packets transmitted from this end. •1 = enable, ACFC is performed if the far end is capable of receiving compressed address/control fields. •2 = disable, ACFC is not performed, even if far end is capable of receiving compressed address/control fields.
-loopCheck	Controls loopback check. If loopback check is enabled, when the magic number in the incoming echo reply is the same as of this PPP link, then this PPP link assumes that the far end is in loopback and brings down its own LCP session. •1 = Enable •2 = Disable

Parameter	Description
-bundle	Specifies the MLPPP bundle number for which to configure PPPMUX. Note Enter the dspmpbundles command to display all MLPPP bundles on the card.
-pid	Default Protocol ID, in the range 0-65535
-muxTimer	Specifies the maximum length of time that the hardware multiplexes packets after multiplexing begins. Values: 0 (disabled), or 64-4000000 microseconds
-frameLength	Maximum mux frame length, in the range 1-512
-subFrameLength	Maximum sub-frame length, in the range 1-512
-subFrameCount	Maximum number of sub-frames in a multiplex super-frame, in the range 2-15.

Counter	Description
Receive Packets	The number of frames received
Receive Bytes	The number of bytes received
Receive Discard Bytes	The number of bytes discarded for any error
Receive MRRU Errors	The number of MRRU error packets
Receive Miscellaneous Errors	The number of packets with miscellaneous errors
Receive FCS Error packets	The number of packets with FCS errors (MPSM-16-T1E1 only)
Send Packets	The number of packets transmitted on this bundle
Send Bytes	The number of bytes transmitted on this bundle

Counter	Description
MLPPP MUX Number	Bundle number associated with the PPPMUX
Interval Number	15-minute interval number
Receive Subframes	Number of PPPMux frames received
Receive Packet	Number of extracted PPP packets
Receive Error Packets	Number of PPPMux frames with demultiplex errors
Send Sub Frames	Number of PPPMux frames transmitted
Send Packets	Number of PPP packets multiplexed
Send Non-Mux Packets	Number of PPP packets not muxed

Parameter	Description
winpath	The number of the WinPath packet processing engine for which t o display loads. Range: 1-2.
intvl	The number of previous intervals to display, in the range 0-96. Interval 0 is the current interval and interval 96 is the oldest 15-minute interval.

Parameter	Description
bundleNumber	Specifies the MLPPP bundle number. Note Enter the dspmpbundles command to display all MLPPP bundles on the card.
intvl	The number of previous intervals to display, in the range 0-96. Interval 0 is the current interval and interval 96 is the oldest 15-minute interval.

Argument	Description
-if	Interface number (partition number) of the partition to configure. •MPSM-16-T1E1 range: 4-499 •MPSM-T3E3-155 range: 4-1003 Note To view all active ATM partitions, use the dspparts command in the ATM CLI context.
-id	A number that identifies the partition, in the range 1-20.
-emin	A guaranteed percentage of egress bandwidth. Each unit of egrminbw is 0.0001-percent of the total bandwidth on the port. (An egrMinBw of 1000000 = 100%.) These small increments provide a high level of granularity.
-emax	A maximum percentage of egress bandwidth. Each unit of egrmaxbw is 0.0001-percent of the total bandwidth available to the port. (An egrMaxBw of 1000000 = 100%.) The minimum bandwidth must be at least 50 cps.
-imin	A guaranteed percentage of the ingress bandwidth. Each unit of ingminbw is 0.0001 percent of the total bandwidth available to a port. (An ingMinBw of 1000000 = 100%.)
-imax	A maximum percentage of the ingress bandwidth. Each increment of ingmaxbw is 0.0001 percent of the total bandwidth on the port. (An ingMaxBw of 100000000 = 100%.) The maximum ingress bandwidth must be at least 50 cps.
-vpmin	Minimum VPI for the partition: •UNI range 0-255 •NNI or VNNI range: 0-4095
-vpmax	Maximum VPI for the partition •UNI range 0-255 •NNI or VNNI range: 0-4095 The max_vpi cannot be less than the min_vpi.
-vcmin	Minimum VCI, in the range from 1-65535
-vcmax	Maximum VCI, in the range from 1-65535 The max_vci cannot be less than the min_vci.
-mincon	Guaranteed number of connections. Value: 0 only
-maxcon	A maximum number of connections. Range 10-2000

ifNum	Specifies the interface number (partition number) of the partition to add. •MPSM-16-T1E1 range: 1-499 •MPSM-T3E3-155 range: 1-1003 Identifies the logical interface to which you want to add a resource partition. Note To view all active partitions, use the dspparts command in the Frame Relay CLI context.
ctrlNum	Specifies a network controller protocol. Enter 2 to specify the PNNI controller. Note Release 5 of the MPSM-T3E3-155 supports only the PNNI controller (option 2). TAG switching (option 1) and MPLS (option 3) are not supported on the MPSM-T3E3-155 card.
-lcn	Maximum number of connections. •MPSM-16-T1E1 range: 0-2000 •MPSM-T3E3-155 range: 0-4000
-dlcimin	Minimum DLCI value. •2-byte header range: 0-1023 •4-byte header range: 0-8355840 in multiples of 32,768 For example, you can enter one of the following numbers as the minimum DLCI value, or any other number that is a multiple of 32,768: 0 = (0 x 32768) 163840 = (5 x 32768) 8355840 = (255 x 32768) Unless your provisioning plan calls for a specific range of DLCI values on a port or card, specify the minimum DLCI value as 0.
-dlcimax	Maximum DLCI value. •2-byte header range: 0-1023 •4-byte header range: 32,767-8,355,840 in multiples of 32,768 minus 1 For example, you can enter one of the following numbers as the maximum DLCI value, or any other number that is a multiple of 32,768 minus l: 32767 = (32768 * 1) - 1 163839 = (32768 * 5) - 1 6520831 = (32768 * 199) - 1 Unless your provisioning plan calls for a specific range of DLCI value on a port or card, specify the maximum DLCI value as 8388607.
-ibw	Maximum ingress port bandwidth percentage for the controller type specified with the ctrlrNum argument, in the range 0-100 percent.
-ebw	Maximum egress port bandwidth percentage for the controller type specified with the ctrlrNum argument, in the range 0-100 percent.

Parameter	Description
-grp	Specifies the IMA group. •MPSM-T3E3-155 range: 1-42 •MPSM-16-T1E1 range: 1-16 Note To see a list of all IMA groups on the current card, enter the dspimagrps command.
-ver	The version number of ATM Forum IMA specification. •1 = Version 1.0 •2 = Version 1.1
-txm	The minimum number of links that must be operational before the IMA group is operational. •MPSM-T3E3-155 range: 1-16 •MPSM-16-T1E1 range: 1-8 For example, if you create an IMA group of 4 links and specify a minimum number of 3 links, then 3 of the 4 specified links must be operational before the IMA group can be used.
-txid	The IMA ID number transmitted in the IMA ID field of the ICP cell, in the range 0-255.
-txfl	The length of transmitted IMA frame in megabytes. For IMA Version 1.0, the txImaFrameLength value is 128. For Version 1.1, the txImaFrameLength value can be 32, 64, 128, or 256.
-dd	The maximum differential delay in milliseconds. •T1 range: 1-275 ms •E1 range: 1-220 ms
-uptim	Group uptime, in the range 0-400000 milliseconds. Default: 10000
-dntim	Group downtime in the range 0-100000 milliseconds. Default: 2500
-vfb	Enables or disables version fallback on the IMA group. •1 = Enable version fallback •2 = Disable version fallback Note Before you enable version fallback for individual IMA groups, you must enable version fallback on the card level. See cnfimaparms -fallback.
-mode	Configures IMA auto restart functionality for the current group. •1 = Disable IMA autorestart •2 = Relearn IMA autorestart •3 = Resume a previous IMA autorestart Note Before you enable autorestart for individual IMA groups, you must enable autorestart on the card level. See cnfimaparms -restart.
-rxid	Identifies the expected received IMA ID, either -1 or in the range 1-255.
-cm	Sets the transmit clock mode. Note Applies to MPSM-16-T1E1 only.

Parameter	Description
-lnk	The link (line or path) in the IMA group to configure: •Physical line: bay.line[:ds1] •DS3 payload: bay.line.sts:ds1 •VT payload: bay.line.sts:vtg.vt •VT structured: bay.line.sts:tug3.vtg.vt where: bay = 1, line = 1-3, sts = 0-3, ds1 = 1-28, tug3 = 1-3, vtg = 1-7, vt = 1-4 (VT15) or 1-3 (VT2) Note The MPSM-16T1E1 requires all links in an IMA Group be within lines 1-8 or 9-16. For example, an IMA Group with lines 7, 8, and 9 is not valid. Note To view a list of all line or path numbers on the current card, enter the dsplns or dsppaths command.
-uplif	LIF integration uptime, in the range 0-25000 milliseconds. The LIF (Loss of IMA Frame) defect is the occurrence of persistent OIF (Out of IMA Frame) anomalies for at least 2 IMA frames.
-dnlif	LIF integration downtime, in the range 0-25000 milliseconds. The LIF (Loss of IMA Frame) defect is the occurrence of persistent OIF (Out of IMA Frame) anomalies for at least 2 IMA frames.
-uplods	LODS integration uptime, in the range 0-25000 milliseconds. The LODS (Link Out of Delay Synchronization) is a link event indicating that the link is not synchronized with the other links within the IMA group.
-dnlods	LODS integration downtime, in the range 0-25000 milliseconds. The LODS (Link Out of Delay Synchronization) is a link event indicating that the link is not synchronized with the other links within the IMA group.

Command	Enter this command to�
addbert	Add a Bit Error Rate Test to a line, path, or port.
cnfbert	Configure a Bit Error Rate Test on a line, path, or port.
startbert	Begin the Bit Error Rate Test configured on the specified line, path, or port.
dspbert	View the BERT parameters configured using the cnfbert command and to view the status of the current BERT session.
dspbertstat	View statistics for a Bit Error Rate Test. Use this command to view changing statistics while the Bit Error Rate Test is running or to view the total statistics accumulated during the test period (after testing has stopped).
insbiterror	Use this command to insert single bit errors into the transmitted BERT pattern configured on the specified path.
stopbert	Enter this command to stop the Bit Error Rate Test running on the specified line, path, or port.
delbert	Enter this command to remove a Bit Error Rate Testing configuration from a line, path, or port. Use this command to delete a BERT session that is running or after the BERT session stops.