Cisco MGX 8850 (PXM1E/PXM45), MGX 8950, MGX 8830, and MGX 8880 Configuration Guide, Release 5 - Managing Service Class Templates [Cisco MGX 8800 Series Switches]

Table Of Contents

Managing Service Class Templates

Cisco SCTs

Managing SCTs

Locating SCT Files on a Switch

SCT File Naming Convention

Creating and Modifying SCT Files

Downloading SCT Files to the Switch

Registering SCT Files

Updating Registered SCT Files

Applying a New Major Version of an AXSM SCT to a Card or Port

Deleting a Registered SCT

Deleting Unregistered SCTs

Displaying all Registered Card and Port SCTs on a Switch

Managing Card SCTs

Managing PXM1E Port SCTs

Displaying the SCT Assigned to a Port

Selecting a Port SCT

Changing a Port SCT

Displaying Port SCT Settings

Port SCT ABR Parameters (dspportsct abr)

Port SCT Bandwidth Parameters (dspportsct bw)

Port SCT General Parameters (dspportsct gen)

Port SCT COSB Parameters (dspportsct cosb)

Port SCT Virtual Circuit Threshold Parameters (dspportsct vcThr)

Port SCT COSB Threshold Parameters (dspportsct cosThr)

Managing Service Class Templates

A Service Class Template (SCT) is a file that contains default configuration data for switch connections and for configuring the hardware to support connections. When you configure a connection, or when an SVC is established, the switch analyzes the connection setup request data, any local configuration data, and the SCTs that apply to the port and to the card. For example, if an SPVC configuration does not include required data for the requested class of service (COS), default values from the SCT files are used. If an SVC request or SPVC configuration specifies configuration values that are different from the SCT values, the specified values override the default SCT values.

There are two types of SCTs: card SCTs and port SCTs. Card SCTs define configuration parameters for the hardware that transfers data between the a service module and the switch back plane. You can assign one card SCT to each service module.

Note The PXM1E supports port SCTs only. PXM1E cards do not support card SCTs.

Port SCTs define configuration parameters for the hardware that transfers data between a PXM1E or service module and a communication line to another switch or CPE. Port SCTs are assigned when a port is configured, and you can use different port SCTs on the same card, provided that the port SCT you select is designed for that card type.

Some SCT parameters control the PXM1E or service module hardware, and others are used as default values for connection parameters. A complete discussion of the SCT parameters is beyond the scope of this book.

SCT parameters are used to do the following:

•connection policing

•connection admission control (CAC)

•provide default connection parameters

•provide connection threshold parameters

•set up class of service buffer (COSB) parameters and threshold values

SCTs simplify configuration by providing default values that will work for most connections. This reduces the number of parameters that need to be defined when setting up connections. When configuring a service module card SCT, your goal should be to select the card SCT that will support the majority of planned connections on that card. When configuring a PXM1E or service module port SCT, your goal should be to select the port SCT that supports the majority of planned connections on that port.

Each PXM1E and service module contains default SCT parameters that you can use for communications. Cisco also supplies additional SCTs that you can use to better support communications. If none of the Cisco supplied SCTs meet your needs, you can use Cisco WAN Manager (CWM) to create your own custom SCTs.

This chapter provides information on the Cisco supplied SCTs, describes how to manage the SCTs available on the switch, and describes how to view the port SCT parameters in use on PXM1E cards.

Note For information on displaying service module SCT parameters, refer to the service module documentation, which is listed in Table 1-1. For more information on configuring SCTs and SCT parameters, refer to the Cisco WAN Manager User's Guide, Release 15.

Cisco SCTs

Cisco provides SCTs with the Release 5 software. Each SCT is classified by card or service module type, by whether it is a card or port SCT, and as either policing or non-policing. Although card SCTs may contain policing parameters, these parameters are ignored. Typically, policing SCTs are used on UNI ports at the edge of the ATM network and control traffic entering the network. Non-policing SCTs are typically on trunk ports that interconnect switches within the network.

Note If traffic is properly controlled at the edges of an ATM network, there should be no need for policing within the network.

Table 7-1 lists the SCTs supplied by Cisco in the Release 5 software. For the very latest information on Cisco SCTs, refer to the following release note documents:

•Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00

•Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00

Table 7-1 Cisco Provided SCTs

Card Type

SCT Type

SCT ID

PNNI

MPLS

Notes

Policing¹

Policing1

AXSM

Card²

2³

N/A

—

There is no operational difference between AXSM card SCTs 2 and 3. Cisco recommends using AXSM card SCT 4 or 5.

33

N/A

—

4

N/A

N/A

There is no operational difference between AXSM card SCTs 4 and 5.

5

N/A

N/A

Port

23

On

—

Cisco recommends using AXSM port SCT 4 or 5.

33

Off

—

4

On

Off

PNNI policing on.

5

Off

Off

PNNI policing off.

AXSM-E

Card2

4

N/A

N/A

All three AXSM-E card SCTs are identical.

5

N/A

N/A

52

N/A

N/A

Port

4

On

Off

Use for UNI ports on interfaces faster than T1 or E1. There is no difference between port SCTs 4 and 5.

5

On

Off

6

Off

Off

Use for NNI ports on interfaces faster than T1 or E1.

52

On

Off

Use on AXSM-32-T1-E1-E UNI ports.

53

Off

Off

Use on AXSM-32-T1-E1-E NNI ports.

54

On

Off

Optimized for UNI IMA groups that use 4 T1/E1 lines or less.⁴

55

Off

Off

Optimized for NNI IMA groups that use 4 T1/E1 lines or less.4

AXSM-XG

Card2

1

N/A

N/A

Optimized for an OC-192 backplane rate. Recommended for use in MGX 8950 switches.

2

N/A

N/A

Optimized for an OC-48 backplane rate. Recommended for use in MGX 8850 switches.

Port

100

Off

Off

Optimized for OC-192 interface path rates.

101

Off

On

110

On

Off

111

On

On

200

Off

Off

Optimized for OC-48 interface path rates.

201

Off

On

210

On

Off

211

On

On

300

Off

Off

Optimized for OC-12 interface path rates.

301

Off

On

310

On

Off

311

On

On

400

Off

Off

Optimized for OC-3 interface path rates.

401

Off

On

410

On

Off

411

On

On

500

Off

Off

Optimized for DS-3 interface path rates.

501

Off

On

510

On

Off

511

On

On

FRSM-12-T3E3

Card2

4

N/A

N/A

This is the only card SCT for this card.

Port

4

On

On

This is the only port SCT for this card.

MPSM-T3E3-155

Card2

1

N/A

—

This is the only card SCT for this card.

Port

1

On

—

Optimized for UNI connections that use 5 or more T1/E1 lines.

2

Off

—

Optimized for NNI connections that use 5 or more T1/E1 lines.

3

On

—

Optimized for IMA or MFR UNI connections that use 4 T1/E1 lines or less.

4

Off

—

Optimized for IMA or MFR NNI connections that use 4 T1/E1 lines or less.

PXM1E

Port

5

On

Off

Use for UNI ports on interfaces faster than T1 or E1.

6

Off

Off

Use for NNI ports on interfaces faster than T1 or E1.

52

On

Off

Use for T1 and E1 UNI ports.

53

Off

Off

Use for T1 and E1 NNI ports.

54

On

Off

Optimized for UNI IMA groups that use 4 T1/E1 lines or less.4

55

Off

Off

Optimized for NNI IMA groups that use 4 T1/E1 lines or less.4

¹Cisco recommends using SCTs with policing enabled for UNI ports and using SCTs with policing disabled for NNI ports.

²Although policing card SCTs are provided for some service modules, the policing parameters are not used. All card SCTs are non-policing.

³SCTs 2 and 3 were created when MGX switches supported PNNI only and were distributed with Release 2.0. These SCTs are provided for backward compatibility. Cisco recommends the use of SCTs that support PNNI and MPLS for all new installations and upgrades.

⁴For IMA groups with 5-8 links, construct an SCT that uses 1/2 of the value of thresholds defined in SCTs 54 and 55. For IMA groups with 9-16 links, construct an SCT that uses 1/4 of the value of thresholds defined in SCTs 54 and 55.

Managing SCTs

Cisco MGX switches provide SCTs for PXM1E and for each service module type. The following sections describe the following tasks and topics for managing SCTs:

•Locating SCT Files on a Switch

•SCT File Naming Convention

•Creating and Modifying SCT Files

•Downloading SCT Files to the Switch

•Registering SCT Files

•Updating Registered SCT Files

•Deleting a Registered SCT

•Deleting Unregistered SCTs

Locating SCT Files on a Switch

SCT files are stored in two locations on a switch. Unregistered files are stored in the C:/SCT/TEMP directory, which is used to store unregistered files until they are registered using the CLI (as described later in this chapter) or CWM. You can use FTP to transfer files to this directory as described in the "Copying Software Files to the Switch" section in "Downloading and Installing Software Upgrades."

Registered files are stored in the F:/SCT directory. Switch administrators can view the contents of this directory for version management control purposes, but administrators are not allowed to copy files to this directory. To register files or to update files in this directory, you must use the CLI commands described in this chapter or use CWM as described in the Cisco WAN Manager User's Guide, Release 15.

SCT File Naming Convention

SCT file names use a name format that defines the file attributes in the following terms:

•Service module type supported

•SCT type (port or card) supported

•SCT ID for SCT selection

•Major version for the SCT file

The format for SCT file names is:
<service_module_type>_SCT.<PORT|CARD>.<SCT_ID>.V<major_version> 
The following example shows a directory listing of SCT files:
M8850_SF.7.PXM.a > cd SCT/TEMP
M8850_SF.7.PXM.a > ll
Listing Directory .:
drwxrwxrwx  1 0       0            13312 Jun 17 21:35 ./
drwxrwxrwx  1 0       0            13312 Mar 11 23:38 ../
-rwxrwxrwx  1 0       0             9975 Jun 17 21:34 AXSME_SCT.CARD.5.V1 
-rwxrwxrwx  1 0       0             9975 Jun 17 21:35 AXSME_SCT.PORT.5.V1 
-rwxrwxrwx  1 0       0             9975 Jun 17 21:35 AXSME_SCT.PORT.6.V1 
-rwxrwxrwx  1 0       0             7214 Jun 17 21:35 AXSM_SCT.CARD.2.V1 
-rwxrwxrwx  1 0       0             7214 Jun 17 21:35 AXSM_SCT.CARD.3.V1 
-rwxrwxrwx  1 0       0             9959 Jun 17 21:35 AXSM_SCT.CARD.4.V1 
-rwxrwxrwx  1 0       0             9959 Jun 17 21:35 AXSM_SCT.CARD.5.V1 
-rwxrwxrwx  1 0       0             7214 Jun 17 21:35 AXSM_SCT.PORT.2.V1 
-rwxrwxrwx  1 0       0             7214 Jun 17 21:35 AXSM_SCT.PORT.3.V1 
-rwxrwxrwx  1 0       0             9959 Jun 17 21:35 AXSM_SCT.PORT.4.V1 
-rwxrwxrwx  1 0       0             9959 Jun 17 21:35 AXSM_SCT.PORT.5.V1 
-rwxrwxrwx  1 0       0             8025 Jun 17 21:35 FRSM12_SCT.CARD.4.V1 
-rwxrwxrwx  1 0       0             8025 Jun 17 21:35 FRSM12_SCT.CARD.5.V1 
-rwxrwxrwx  1 0       0             8025 Jun 17 21:35 FRSM12_SCT.CARD.6.V1 
-rwxrwxrwx  1 0       0             8025 Jun 17 21:35 FRSM12_SCT.CARD.7.V1 
-rwxrwxrwx  1 0       0             8028 Jun 17 21:35 FRSM12_SCT.PORT.4.V1 
-rwxrwxrwx  1 0       0             8025 Jun 17 21:35 FRSM12_SCT.PORT.5.V1 
-rwxrwxrwx  1 0       0             8028 Jun 17 21:35 FRSM12_SCT.PORT.6.V1 
-rwxrwxrwx  1 0       0             8028 Jun 17 21:35 FRSM12_SCT.PORT.7.V1 
In the file system : 
    total space :  818961 K bytes
    free  space :  672282 K bytes
Table 7-2 describes the parameters used in the SCT naming convention.

Table 7-2 SCT Naming Conventions

Parameter

Description

service_module_type

The type of the service module on which the SCT will be applied. The possible service module types are AXSM, AXSME, AXSMXG, FRSM12, MPSM155, and PXM1E.

PORT|CARD

Specifies whether this is a port SCT or a card SCT.

Note PXM1E cards use port SCTs only. Card SCT s are not applicable to PXM1E cards.

SCT_ID

This decimal number identifies an SCT and is the number used to select a SCT when specifying a port or card SCT. The following SCT numbers indicate additional information:

•0 = Default SCT for the card type

•1-99 = Cisco provided SCTs which may be modified with CWM

•100 -255 = Custom SCTs created with CWM

V<major_version>

This decimal number identifies the major version of the SCT. The major version of the SCT changes whenever a new object is added or deprecated in the SCT MIB. Only Cisco can change the major version of an SCT.

A minor version change occurs when an SCT is modified using CWM. Minor version numbers do not appear in the filename but they do appear in CWM and in the CLI after the SCT is registered. To see the minor version of registered SCTs, use the dspscts command.

Creating and Modifying SCT Files

SCT files can be created and modified using CWM as described in the Cisco WAN Manager User's Guide, Release 15. While there are no CLI commands for modifying SCT files, you can override SCT file settings for specific connections using CLI commands such as cnfabr and cnfabrtparmdft. If you need to modify multiple settings or multiple connections, it can be more efficient to modify SCTs with CWM.

Downloading SCT Files to the Switch

When you want to download a new or modified SCT file, you can download the file using CWM or by using an FTP program. If you have used CWM to create or modify an SCT or if you are using CWM to manage your SCTs, it is best to use CWM to download and to register the file. For more information, refer to the Cisco WAN Manager User's Guide, Release 15.

When using an FTP program, copy the files to the C:SCT/TEMP directory on the switch. For the latest information on Cisco provided SCTs, refer to the following release note documents:

•Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00

•Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00

For more information on transferring files to the switch, see the "Copying Software Files to the Switch" section in "Downloading and Installing Software Upgrades."

After you download a file to a switch, you must register the SCT on the switch if it has not been registered before, or you must update a preregistered SCT. The next two sections describe how to register SCT files and how to update previously registered SCT files.

Registering SCT Files

SCT files must be registered on a switch before they can be used to configure card and port communications. The registration process checks for version conflicts and registers SCTs with CWM when CWM is used for network management.

The primary goal of SCT registration is to prevent the confusion that can result when two SCT files with the same name contain different configurations. Registration on a switch ensures that no two registered SCT files have the same name. When CWM is used to manage SCTs on a network, CWM can be used to prevent different configurations for the same file name within the network, and CWM can be used to distribute and register SCTs to multiple switches simultaneously. To learn how to manage SCT files with CWM, refer to the Cisco WAN Manager User's Guide, Release 15.

There are three types of registration:

•Auto registration during an upgrade

•Registration directed by CWM

•Manual registration initiated in the CLI

Autoregistration is used during upgrades from releases that did not support registered SCT files. Auto registration registers SCT files that were in use before the upgrade.

When an SCT is autoregistered or registered through CWM, there is no need to manually register the SCT. To view registered SCTs, use the dspscts command as described in "Displaying all Registered Card and Port SCTs on a Switch," which appears later in this chapter.

If the dspscts command display does not show the SCT you want to use, you can manually FTP an SCT file to the switch and then manually register that SCT. If the upgrade files are copied to the switch as described in the "Copying Software Files to the Switch" section in "Downloading and Installing Software Upgrades," you can manually register the SCT using the procedure described later in this section.

When you manually register an SCT, the SCT is moved from a temporary directory to the directory where registered SCTs are stored. You cannot use SCTs that are stored in the temporary directory. Once an SCT is registered, it is removed from the temporary directory so that it cannot be registered again.

Use the following procedure to manually register SCT files.

Step 1 Check the SCT temporary directory on the switch to see if the SCT file you want to register is available. The directory path is C:SCT/TEMP. For information on viewing directories, see the "Browsing the File System" section in "Downloading and Installing Software Upgrades."

Step 2 If the SCT file you want to register is not on the switch, FTP the SCT file to the C:SCT/TEMP folder, as described in the "Copying Software Files to the Switch" section in "Downloading and Installing Software Upgrades." For information on locating SCT files provided by Cisco, refer to the following release note documents:

•Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00

•Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00

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

Step 4 Obtain the checksum for the SCT file you are registering. You can look up the checksum in the release note documents listed in Step 2.

Note The checksum is calculated based on the file contents. If two files share the same name and define different configurations, the checksums will be different, and the registration process will detect the conflict. When you use a checksum displayed in the Release Notes for your product, successful registration verifies that the SCT is the same file that is distributed by Cisco. If registration with a Cisco supplied checksum is unsuccessful, the SCT you are trying to register has been modified.

Step 5 Register the SCT file using the addsct command and the checksum displayed in the previous step. The command format is:
D1.8.PXM.a > addsct <card type> <sct type> <sct id> <major ver> <checksum>
The required parameters identify the file name and the internal checksum and are defined in Table 7-3.

Table 7-3 addsct and cnfsct Command Parameters

Option

Description

card type

Identifies the type of card the SCT runs on. Enter one of the following:

•AXSM = axsm or 1

•AXSME = axsme or 2

•AXSMXG = axsmxg or 5

•FRSM12 = frsm12 or 4

•MPSM-155-T3E3 = mpsm155 or 6

•PXM1E = pxm1e or 3

sct type

Defines the SCT type as one of the following:

•Port SCT = 1

•Card SCT = 2

Note MGX 8850 (PXM1E) and MGX 8830 switches support only the PXM1E port SCTs.

sct id

Enter the SCT identification number, which appears in the file name.

major ver

Enter the major version number of the SCT file as it appears in the filename. This number changes when a new parameter is added to a MIB. Only Cisco can generate a new major version of a file.

checksum

Enter the hexadecimal SCT checksum number published in one of the following documents:

•Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00

•Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00

In the following example, FRSM card SCT 4, version 1, is registered on the switch.
M8850_SF.7.PXM.a > addsct frsm12 2 4 1 0x357d963a
You must enter this command once for each new SCT, or for each new major and minor version of a pre-existing SCT.

Step 6 Enter the dspscts command and verify that the SCT file is registered on your switch.

The status of the SCT would be marked as "failed" if the file does not exist or does not match the major and minor versions.

Updating Registered SCT Files

Once you have registered an SCT file on your switch, you can use the cnfsct command to update a registered SCT with a different major or minor version of the same SCT. To update a registered SCT, use the following procedure:

Step 1 FTP the new SCT file to the C:SCT/TEMP folder, as described in the "Copying Software Files to the Switch" section in "Downloading and Installing Software Upgrades."

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

Step 3 Obtain the checksum for the SCT file you are registering. You can look up the checksum in the following release note documents:

•Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00

•Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00

Note You will need the checksum for the cnfsct command in Step 4.

Step 4 Enter the cnfsct command at the active PXM switch prompt.
M8830_CH.2.PXM.a > cnfsct <card type> <sct type> <sct id> <major ver> <checksum>
The required parameters for this command are described in Table 7-3.

In the following example, the user overwrites and old MPSM card SCT with a new one:
M8830_CH.2.PXM.a > cnfsct mpsm155 1 2 1 0xbc8cd86c
The cnfsct command does not cause a new SCT to become active on the card type you specify 
with this command. To activate the new SCT on an individual card,you must reset the 
standby card in a redundant pair or the active card in a non-redundant configuration
Do you want to proceed (Yes/No) ? y
Step 5 Enter the dspscts command to ensure that the latest SCT version was registered on your switch. If the status is valid, the SCT is ready for use. The status of the SCT is marked as failed if the file does not exist or does not match the major and minor versions. If the checksum computed for the file does not match the checksum entered, the status is checksum mismatch.

Step 6 In order for the newer version of the SCT to take effect, you must reset each card that uses the SCT. The procedure is different for different card types and configurations. Select the procedure that applies to your situation from the following list:

•On a redundant pair of PXM1E cards or service modules, enter the switchredcd <fromSlot> <toSlot> command.

•On a standalone PXM1E card, enter the resetcd command.

•On a standalone service module, enter the resetcd <slot> command at the PXM prompt.

Step 7 To verify that the new card SCT version has been applied to the appropriate card, use the cc command to switch to that card, then enter the dspcdsct command.

Step 8 To verify that a new port SCT is in use on a card, use the cc command to switch to that card, then enter the dspportsct gen <sctId> command.

Applying a New Major Version of an AXSM SCT to a Card or Port

The major version number of an AXSM SCT file changes when a new parameter is added to an SCT, or when an existing parameter is deleted from an SCT. Only Cisco can warrant a major version change to an SCT file, and as of the publishing date of this guide, no major version updates have been released. Major version changes are posted in the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00.

To apply a new major version of an SCT file to an AXSM card or port, use the following procedures:

Step 1 Download the new SCT file to your switch, as described in "Downloading and Installing Software Upgrades."

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

Step 3 Enter the cc command to change to the appropriate AXSM (the card on which you will apply the new SCT).

Step 4 Enter the setsctver <sctver> command. Replace <sctver> with the new SCT major version number.
M8850_SF.5.AXSM.a > setsctver 2
Step 5 In order for the newer version of the SCT to take effect, you must reset the card. On a redundant pair, enter the switchredcd command to reset the card. On a standalone card, enter the resetcd command.

Step 6 To verify that the new SCT version has been applied to the appropriate card, enter the dspcd command.

Step 7 To verify that a new port SCT is in use on a card, enter the dspportsct gen <port> command.

Deleting a Registered SCT

When you delete a registered SCT, the SCT is removed from the list of available SCTs and the switch. The SCT is no longer available to cards that match the SCT card type.

Note You cannot simply use the addsct command to add a previously deleted SCT. To add a previously deleted SCT, you must transfer the appropriate SCT file to the switch and then register the SCT.

To delete a registered SCT file from the switch, use the following procedure:

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

Step 2 Enter the dspscts command to display the registered SCTs and the parameters you will need when deleting an SCT.

Step 3 At the PXM prompt, enter the delsct <card type> <sct type> <sctid> <major ver> command, as shown in the following example:
M8830_CH.2.PXM.a > delsct pxm1e 1 5 1
Warning: this SCT may be in use on the service modules or the PXM1E. Please verify SCT 
usage on these cards by using the "dspports" 
Do you want to proceed (Yes/No) ? y
Table 7-4 describes the parameters for the delsct command.

Table 7-4 delsct Command Parameters

Option

Description

card type

Identifies the type of card the SCT runs on. The possible card types are as follows:

•AXSM = axsm or 1

•AXSME = axsme or 2

•AXSM-XG = axsmxg or 5

•FRSM-12-T3E3 = frsm12 or 4

•MPSM-T3E3-155 = mpsm155 or 6

•PXM1E = pxm1e or 3

sct type

Specifies whether the SCT is a port SCT or a card SCT.

sct id

Specifies the SCT ID number to be deleted.

major ver

Specifies the major version number of the SCT to be deleted.

Step 4 Enter the dspscts command to ensure that the proper SCT was deleted from your network.

Deleting Unregistered SCTs

Unregistered SCTs are stored as files in the temporary storage directory, C:SCT/TEMP/. Cisco recommends that you register all SCTs in this directory and delete any SCT files that you do not want to register. If you want to save SCT files that you do not want to register, Cisco recommends that you store these files on external media. Unregistered files that are in the temporary storage directory consume disk space and can create problems during software upgrades.

To navigate to the SCT temporary storage directory and make changes, use the commands described in the "Browsing the File System" section of "Downloading and Installing Software Upgrades."

Displaying all Registered Card and Port SCTs on a Switch

To display all registered SCTs on a switch and their status, enter the dspscts command at the active PXM switch prompt.
M8830_CH.2.PXM.a > dspscts
-----------------------------------------------------------------------------
 Card  Type   ID   Major Minor Checksum   Status   Description
-----------------------------------------------------------------------------
 PXM1E PORT  00005 00001 00000 0x53c67945  valid   cisco :PXM1E_SCT.PORT.5.V1
 PXM1E PORT  00006 00001 00000 0xb69ce935  valid   cisco :PXM1E_SCT.PORT.6.V1
 PXM1E PORT  00052 00001 00000 0x199550ec  valid   cisco :PXM1E_SCT.PORT.52.V1
 PXM1E PORT  00053 00001 00000 0xf6d53485  valid   cisco :PXM1E_SCT.PORT.53.V1
 PXM1E PORT  00054 00001 00000 0x2a96b5b9  valid   cisco :PXM1E_SCT.PORT.54.V1
 PXM1E PORT  00055 00001 00000 0x5403c5ac  valid   cisco :PXM1E_SCT.PORT.55.V1
MPSM155 PORT  00001 00001 00000 0x0fac7e45  valid   cisco :MPSM155_SCT.PORT.1.V1
MPSM155 CARD  00001 00001 00000 0x4c964664  valid   cisco :MPSM155_SCT.CARD.1.V1
MPSM155 CARD  00002 00001 00000 0xe0cbccd8  valid   cisco :MPSM155_SCT.CARD.2.V1
Table 7-5 describes the dspscts command display components.

Table 7-5 dspscts Command Display Components

Object

Description

card type

Type of Service Module to which the SCT is registered. Possible service modules are AXSM, AXSME, AXMS-XG, FRSM12, MPSM-155-T3E3, and PXM1E.

sct type

Describes whether the SCT is a port SCT or a card SCT.

sctid

A 16-bit number uniquely identifying the SCT.

major

A 16-bit number which identifies the major version of the SCT. When an object is deleted or added to an SCT MIB and an upgrade is required, the major version number of the file changes. The major version of a file is always in consecutive order and cannot be deleted.

minor

A 16-bit number which identifies the minor version of the SCT. Each time an SCT file is modified, saved, and downloaded, the minor version number changes. A minor version change does not require an upgrade or re-configuration of the card and port database. However, the card must be reset before the card can use the changed SCT settings. The minor version of a file can be deleted; therefore, the minor version number of a file may not be in consecutive order from the previous minor version of the same file.

checksum

An SCT identification number between 0 and 65535 that matches the checksum embedded in the SCT file. The checksum number for all new SCT files is advertised to the user through the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00.

status

Status of the SCT file on the switch. The status of the SCT would be marked as "failed" if the file does not exist or does not match the major and minor versions.

description

Identifies whether the file is provided by Cisco and displays the source filename.

Managing Card SCTs

Card SCTs are used only on service modules. For instructions on managing card SCTs on service modules, refer to the service module documentation, which is listed in Table 1-1.

Managing PXM1E Port SCTs

The following sections describe how to manage PXM1E 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

Note For instructions on managing port SCTs on service modules, refer to the service module documentation, which is listed in Table 1-1.

Displaying the SCT Assigned to a Port

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

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

Step 2 Enter the following command:
mgx8830a.1.PXM.a > dspports
The dspports report displays a column labeled "Port SCT Id," which identifies the SCT assigned to 
each port.
mgx8830a.1.PXM.a > dspports
ifNum Line Admin Oper. Guaranteed Maximum     Port SCT Id     ifType  VPI
           State State Rate       Rate                               (VNNI only)
----- ---- ----- ----- ---------- --------- ----------------- ------ ----------
    1  1.1    Up    Up    1412830   1412830   2                   NNI    0 
    2  1.2    Up    Up    1412830   1412830   2                   NNI    0 
    3  2.1    Up    Up    1412830   1412830   2                   NNI    0 
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 a PXM1E port, enter the addport command as described in the "Adding ATM Ports" section in Chapter 3, "Provisioning PXM1E Communication Links."

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 "Registering SCT Files," which appears earlier in this chapter.

Changing a Port SCT

To change the SCT assigned to a port, enter the cnfport command as described in the "Modifying ATM Ports" section in Chapter 3, "Provisioning PXM1E Communication Links."

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 "Registering SCT Files," which appears earlier in this chapter.

Displaying Port SCT Settings

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

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

Step 2 Enter the following command:
mgx8830a.1.PXM.a > dspportsct <abr|bw|gen|cosb|vcThr|cosThr> <ifNum>
Select one of the options to display one of the six SCT configuration reports, and replace <ifNum> with the number of the port you want to view. Table 7-6 describes the reports for each of these options.

Note The option names are case sensitive. The switch does not recognize the vcthr option. You must enter vcThr.

Table 7-6 Options for dspportsct Command

Option

Description

abr

Displays ABR parameters.

bw

Displays bandwidth and policing parameters.

gen

Displays general SCT parameters.

cosb

Displays COSB parameters.

vcThr

Displays virtual circuit threshold parameters.

cosThr

Displays COSB threshold parameters.

The SCT parameters are divided within SCT files into two groups: VC descriptors and COSB parameters. A COSB is special memory that temporarily stores incoming or outgoing connection data.

The sections that follow show the display for each of the dspportsct command options and describe the SCT parameters that appear in the display.

Port SCT ABR Parameters (dspportsct abr)

The following report appears when you enter the dspportsct abr command:
M8830_CH.1.PXM.a > dspportsct abr 1
Service Class Template [  6] : VC ABR Parameters
Major Version [  1]          : Minor Version [  0]
+----------------------------------------------+
|    SERV TYPE    | CI CTRL |  VSVD   |
+----------------------------------------------+
|  VSI_SIGNAL(  2)|DISABLED | DISABLED|
|   ATMF_CBR1(256)|DISABLED | DISABLED|
| ATMF_VBRrt1(257)|DISABLED | DISABLED|
| ATMF_VBRrt2(258)|DISABLED | DISABLED|
| ATMF_VBRrt3(259)|DISABLED | DISABLED|
|ATMF_VBRnrt1(260)|DISABLED | DISABLED|
|ATMF_VBRnrt2(261)|DISABLED | DISABLED|
|ATMF_VBRnrt3(262)|DISABLED | DISABLED|
|   ATMF_UBR1(263)|DISABLED | DISABLED|
|   ATMF_UBR2(264)|DISABLED | DISABLED|
|    ATMF_ABR(265)| ENABLED | DISABLED|
|   ATMF_CBR2(266)|DISABLED | DISABLED|
|   ATMF_CBR3(267)|DISABLED | DISABLED|
|    TAG_COS0(512)|DISABLED | DISABLED|
|    TAG_COS1(513)|DISABLED | DISABLED|
|    TAG_COS2(514)|DISABLED | DISABLED|
|    TAG_COS3(515)|DISABLED | DISABLED|
|    TAG_COS4(516)|DISABLED | DISABLED|
|    TAG_COS5(517)|DISABLED | DISABLED|
|    TAG_COS6(518)|DISABLED | DISABLED|
|    TAG_COS7(519)|DISABLED | DISABLED|
+----------------------------------------------+
Table 7-7 describes the SCT ABR Parameters shown in the example.

Table 7-7 SCT ABR Descriptions

Parameter

Description

SERV-TYPE

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

CI CTRL

Congestion indicator (CI) control. When enabled, this parameter specifies that the CI field is an RM¹ cell that is used to cause the source to decrease the ACR. When an RM cell is sent, the source sets CI=1. When EFCI is received on a previous data cell, CI=1.

VSVD²

When enabled, this parameter divides an ABR connection into two or more separately controlled ABR segments. Each ABR control segment, except the first, is sourced by a virtual source. Sources and destinations are linked through bidirectional connections, and each connection termination point is both a source and a destination, a source for data that is transmitting, and a destination for data that is receiving.

¹RM = resource management

²VSVD = virtual source/virtual destination

Port SCT Bandwidth Parameters (dspportsct bw)

The following report appears when you enter the dspportsct bw command:
M8830_CH.1.PXM.a > dspportsct bw 1 
Service Class Template [  6] : Bw and Policing Parameters
Major Version [  1]          : Minor Version [  0]
+---------------------------------------------------------+
| SERV-TYPE(DEC)  |   PCR   |   SCR   |   MCR   |   MBS   |
+---------------------------------------------------------+
|  VSI_SIGNAL(  2)|    1000 |    1000 |    5000 |      50 |
|   ATMF_CBR1(256)|    1000 |    1000 |    5000 |     800 |
| ATMF_VBRrt1(257)|    1000 |    1000 |    5000 |      50 |
| ATMF_VBRrt2(258)|    1000 |    1000 |    5000 |      50 |
| ATMF_VBRrt3(259)|    1000 |    1000 |    5000 |      50 |
|ATMF_VBRnrt1(260)|    1000 |    1000 |    5000 |      50 |
|ATMF_VBRnrt2(261)|    1000 |    1000 |    5000 |      50 |
|ATMF_VBRnrt3(262)|    1000 |    1000 |    5000 |      50 |
|   ATMF_UBR1(263)|      10 |      10 |    5000 |     800 |
|   ATMF_UBR2(264)|      10 |      10 |    5000 |     800 |
|    ATMF_ABR(265)|      10 |      10 |       0 |      50 |
|   ATMF_CBR2(266)|    1000 |    1000 |    5000 |     800 |
|   ATMF_CBR3(267)|    1000 |    1000 |    5000 |     800 |
|    TAG_COS0(512)|    1000 |    1000 |    5000 |     800 |
|    TAG_COS1(513)|    1000 |    1000 |    5000 |     800 |
|    TAG_COS2(514)|    1000 |    1000 |    5000 |     800 |
|    TAG_COS3(515)|    1000 |    1000 |    5000 |     800 |
|    TAG_COS4(516)|    1000 |    1000 |    5000 |     800 |
|    TAG_COS5(517)|    1000 |    1000 |    5000 |     800 |
|    TAG_COS6(518)|    1000 |    1000 |    5000 |     800 |
|    TAG_COS7(519)|    1000 |    1000 |    5000 |     800 |
+---------------------------------------------------------+
+-----------------------------------------------+
| SERV-TYPE(DEC)  |  CDVT   |   ICR   |   MFS   |
+-----------------------------------------------+
|  VSI_SIGNAL(  2)|  250000 |     100 |     100 |
|   ATMF_CBR1(256)|  250000 |     100 |     100 |
| ATMF_VBRrt1(257)|  250000 |     100 |     100 |
| ATMF_VBRrt2(258)|  250000 |     100 |     100 |
| ATMF_VBRrt3(259)|  250000 |     100 |     100 |
|ATMF_VBRnrt1(260)|  250000 |     100 |     100 |
|ATMF_VBRnrt2(261)|  250000 |     100 |     100 |
|ATMF_VBRnrt3(262)|  250000 |     100 |     100 |
|   ATMF_UBR1(263)|  250000 |     100 |     100 |
|   ATMF_UBR2(264)|  250000 |     100 |     100 |
|    ATMF_ABR(265)|  250000 |       0 |     100 |
|   ATMF_CBR2(266)|  250000 |     100 |     100 |
|   ATMF_CBR3(267)|  250000 |     100 |     100 |
|    TAG_COS0(512)|  250000 |     100 |     100 |
|    TAG_COS1(513)|  250000 |     100 |     100 |
|    TAG_COS2(514)|  250000 |     100 |     100 |
|    TAG_COS3(515)|  250000 |     100 |     100 |
|    TAG_COS4(516)|  250000 |     100 |     100 |
|    TAG_COS5(517)|  250000 |     100 |     100 |
|    TAG_COS6(518)|  250000 |     100 |     100 |
|    TAG_COS7(519)|  250000 |     100 |     100 |
+-----------------------------------------------+
Table 7-8 describes the SCT ABR Parameters shown in the example.

Table 7-8 SCT Bandwidth Parameter Descriptions

Parameter

Description

SERV-TYPE

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

PCR

Specifies the maximum PCR for a connection using this service type. The value is a percentage of the maximum cell rate for the logical interface. 1000000 is equal to 100%.

The range and units are 0 to 1000000.

SCR

Specifies the SCR¹ for a connection using this service type. The value is a percentage of the maximum cell rate for the logical interface. 1000000 is equal to 100%.

The range and units are from 0 to 1000000.

MCR

Specifies the MCR² for a connection using this service type. The value is a percentage of the maximum cell rate for the logical interface. 1000000 is equal to 100%.

The range and units are from 0 to 1000000.

MBS

Specifies the maximum number of cells that can arrive at a rate equal to the PCR. The MBS³ is used for policing.

The range and units are from 1 to 5000000.

CDVT

Specifies the CDVT⁴ for the first leaky bucket.

ICR

Specifies the ICR⁵ for a transmission on a connection that has been idle for a configured period of time. The value is a percentage of the PCR for the logical interface. 1000000 is equal to 100%.

Note ABR service type connections are used only.

The range and units are from 0 to 1000000.

MFS

Specifies the AAL5 MFS⁶ in cells.

¹SCR = sustained cell rate

²MCR = minimum cell rate

³MBS = maximum burst size

⁴CDVT = cell delay variation tolerance

⁵ICR = initial cell rate

⁶MFS = maximum frame size

Port SCT General Parameters (dspportsct gen)

The following report appears when you enter the dspportsct gen command:
M8830_CH.1.PXM.a > dspportsct gen 1
Service Class Template [  6] : General Parameters
Major Version [  1]          : Minor Version [  0]
+---------------------------------------------------------------+ 
| SERV-TYPE(DEC)  | COSB_NUM | CAC_TYPE |  UPC_ENB   | WFQ_ENB  | 
+---------------------------------------------------------------+ 
|  VSI_SIGNAL(  2)|      1   |     BCAC | DISABLED   | DISABLED | 
|   ATMF_CBR1(256)|      4   |     BCAC | DISABLED   | DISABLED | 
| ATMF_VBRrt1(257)|      5   |     BCAC | DISABLED   | DISABLED | 
| ATMF_VBRrt2(258)|      5   |     BCAC | DISABLED   | DISABLED | 
| ATMF_VBRrt3(259)|      5   |     BCAC | DISABLED   | DISABLED | 
|ATMF_VBRnrt1(260)|      6   |     BCAC | DISABLED   | DISABLED | 
|ATMF_VBRnrt2(261)|      6   |     BCAC | DISABLED   | DISABLED | 
|ATMF_VBRnrt3(262)|      6   |     BCAC | DISABLED   | DISABLED | 
|   ATMF_UBR1(263)|      7   |  LCN_CAC | DISABLED   | DISABLED | 
|   ATMF_UBR2(264)|      7   |  LCN_CAC | DISABLED   | DISABLED | 
|    ATMF_ABR(265)|      2   |     BCAC | DISABLED   | DISABLED | 
|   ATMF_CBR2(266)|      4   |     BCAC | DISABLED   | DISABLED | 
|   ATMF_CBR3(267)|      4   |     BCAC | DISABLED   | DISABLED | 
|    TAG_COS0(512)|      8   |  LCN_CAC | DISABLED   | DISABLED | 
|    TAG_COS1(513)|      9   |  LCN_CAC | DISABLED   | DISABLED | 
|    TAG_COS2(514)|     10   |  LCN_CAC | DISABLED   | DISABLED | 
|    TAG_COS3(515)|     11   |  LCN_CAC | DISABLED   | DISABLED | 
|    TAG_COS4(516)|      8   |  LCN_CAC | DISABLED   | DISABLED | 
|    TAG_COS5(517)|      9   |  LCN_CAC | DISABLED   | DISABLED | 
|    TAG_COS6(518)|     10   |  LCN_CAC | DISABLED   | DISABLED | 
|    TAG_COS7(519)|     11   |  LCN_CAC | DISABLED   | DISABLED | 
+---------------------------------------------------------------+ 
+--------------------------------------------------------------------+ 
| SERV-TYPE(DEC)  |  UPC_SELECT  |   GCRA1_PLCY    |   GCRA2_PLCY    |
|                 |  BKT1_BKT2   |                 |                 |
+--------------------------------------------------------------------+ 
|  VSI_SIGNAL(  2)|   CLP01_CLP01|          DISCARD|          DISCARD| 
|   ATMF_CBR1(256)|    CLP01_DISC|          DISCARD|          DISCARD| 
| ATMF_VBRrt1(257)|   CLP01_CLP01|          DISCARD|          DISCARD| 
| ATMF_VBRrt2(258)|    CLP01_CLP0|          DISCARD|          DISCARD| 
| ATMF_VBRrt3(259)|    CLP01_CLP0|          DISCARD|          SET_CLP| 
|ATMF_VBRnrt1(260)|   CLP01_CLP01|          DISCARD|          DISCARD| 
|ATMF_VBRnrt2(261)|    CLP01_CLP0|          DISCARD|          DISCARD| 
|ATMF_VBRnrt3(262)|    CLP01_CLP0|          DISCARD|          SET_CLP| 
|   ATMF_UBR1(263)|    CLP01_DISC|          DISCARD|          DISCARD| 
|   ATMF_UBR2(264)|    CLP01_DISC|SET_CLP_DISC_TAGD|          DISCARD| 
|    ATMF_ABR(265)|    CLP01_DISC|          DISCARD