Specifications

7-6
Cisco MGX 8800/8900 Series Software Configuration Guide
Release 5.1, Part Number OL-6482-01, Rev. A0, January 25, 2005
Chapter 7 Managing Service Class Templates
Managing SCTs
-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.
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.1. 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.
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 cards, AXSME cards,
AXSM-16-155-XG, FRSM-12-T3E3, MPSM-T3E3-155,
MPSM-16-T1E1, and PXM1E.
Note AXSM-16-155-XG cards use SCTs up to #511.
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.