CISCO-WAN-SCT-MGMT-MIB

All MIBs › CISCO-WAN-SCT-MGMT-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2002-05-21

Category: ATM, Vendor: Cisco Devices

Description: Manages Cisco WAN Service Class Template (SCT) definitions for ATM traffic descriptor assignment.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-WAN-SCT-MGMT-MIB?

CISCO-WAN-SCT-MGMT-MIB manages Service Class Template (SCT) files on Cisco WAN switching nodes, where SCTs are per-card-type configuration files defining the traffic/QoS characteristics of class-of-service queues for a switch. It exposes a table keyed by card type, SCT type, SCT ID, and major version, with fields for file name, minor version, checksum, description, and operational/row status. Its monitoring purpose is software-configuration integrity: checking cwSctFileOperStatus and cwSctFileChecksum confirms an SCT file was correctly downloaded and activated on a card, and a checksum mismatch or non-operational status indicates the traffic/QoS profile in use may not match the intended template, risking misapplied QoS behavior. It is Cisco-specific to the MGX/AXSM WAN switch card architecture and has no direct IETF MIB dependency, though it relates conceptually to ATM traffic descriptor standards. It is used in Cisco MGX WAN switch deployments to manage and verify QoS template distribution across line cards like AXSM. Network engineers evaluating or troubleshooting this functionality can download the CISCO-WAN-SCT-MGMT-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-WAN-SCT-MGMT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco MGX WAN switch line cards (e.g., AXSM)

Monitoring Examples

An operator would query cwSctFileMgmtTable using cwSctCardType, cwSctType, cwSctId, and cwSctMajorVersion to identify the active SCT (e.g., an AXSM_PORT_SCT file) on a given card, then verify cwSctFileChecksum matches the expected value and cwSctFileOperStatus shows the file successfully loaded. A cwSctFileMinorVersion mismatch across cards of the same type could reveal inconsistent QoS template versions in the network.

What Can Be Monitored

SCT file name and version
checksum integrity
operational status of loaded template
card type/SCT ID association

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus

How to Use in IPNetwork Monitor

Example using cwSctFileOperStatus OID:

Select a Cisco MGX WAN switch as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cwSctFileOperStatus into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. Reflects the operational status of the SCT file. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'valid', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoWanSctMgmtMIB	1.3.6.1.4.1.9.9.236			MIB module to manage SCT files in a node. SCTs (Service Class Templates) are nodal configuration files, which define the traffic characteristics of a switch based on class of service queues. There is a unique SCT file for every combination of card type, SCT type, SCT Id and major SCT version. For instance, the file AXSM_PORT_SCT.4.V2 refers to a SCT for the card type AXSM, port type SCT, SCT id 4 and a major version of 2. SCTs are transfered to a node using FTP by NMS. The NMS adds, deletes, discovers and monitors SCT files in a node using this MIB.
ciscoWanSctMgmtMIBObjects	1.3.6.1.4.1.9.9.236.1
cwSctFileMgmtTable	1.3.6.1.4.1.9.9.236.1.1		not-accessible	This MIB defines a SCT file management table in which each row corresponds to a unique SCT file. When the NMS needs to add a SCT to a node, it transfers the SCT file to a transient storage area on the node. The NMS then performs a SET operation requesting the agent to accept the transferred file. The agent validates the integrity of the file and if valid, transfers the file to a secure area. It would then create a new row in the SCT file management table. This newly added row is then advertised to all NMS in the network using appropriate traps (refer CISCO-WAN-SCT-MGMT-TRAPS-MIB). Once a row is created, the agent keeps track of the operational status of the corresponding SCT file. The NMS can query the status of a SCT file by performing a GET operation on the row. The NMS can delete a SCT file and its corresponding row in the SCT file management table by performing a SET operation with the appropriate RowStatus. The agent, upon successful deletion of the row would advertise this configuration change to all the NMS using appropriate traps. The NMS could also perform a GETNEXT operation to discover all the configured SCTs on a node.
cwSctFileMgmtEntry	1.3.6.1.4.1.9.9.236.1.1.1		not-accessible	An entry in the SCT file Management Table. This represents a unique SCT file in the node. Each entry contains the configuration and status information of a specific SCT in the node.
INT cwSctCardType	1.3.6.1.4.1.9.9.236.1.1.1.1	INTEGER	not-accessible	This represents service modules in a node that require the use of a SCT. The content of the SCT varies depending on the specific hardware used. Hence there is a different SCT for every type of card. The card types that support SCTs are listed in the SYNTAX clause
INT cwSctType	1.3.6.1.4.1.9.9.236.1.1.1.2	INTEGER	not-accessible	There are several types of SCTs. The portSct (1) specifies traffic parameters that are applicable to a logical port within a card. The cardSct (2) specifies traffic parameters that are applicable to the whole card.
U32 cwSctId	1.3.6.1.4.1.9.9.236.1.1.1.3	Unsigned32	not-accessible	Each logical port on a service module could need different 'class of service' characteristics. This can be achieved by applying different SCTs on different ports. Thus for a given card type, there could be multiple SCTs of different IDs.
U32 cwSctMajorVersion	1.3.6.1.4.1.9.9.236.1.1.1.4	Unsigned32	not-accessible	The SCT file consists of several tables. The number of tables depend on the service module card type. Both the contents and the row/column size of a table are subject to change. The major version is incremented by the manager whenever there is a change in the row/column size of the table.
STR cwSctFileName	1.3.6.1.4.1.9.9.236.1.1.1.5	SnmpAdminString	read-only	This object specifies the absolute path name of the file corresponding to the SCT indices. After the agent accepts a SET operation and creates a new row in the SCT file management table, it transfers the file from the transient storage area to a secure location on the disk. This object identifies the absolute path name of the secure location on disk. The file name would be in the format: _SCT...V
U32 cwSctFileMinorVersion	1.3.6.1.4.1.9.9.236.1.1.1.6	Unsigned32	read-only	The SCT file consists of several tables. The number of tables depend on the service module card type. Both the contents and the row/column size of a table are subject to change. The minor version is incremented by the manager whenever there is a change in contents of the table.
U32 cwSctFileChecksum	1.3.6.1.4.1.9.9.236.1.1.1.7	Unsigned32	read-create	The manager specifies this checksum when trying to add a SCT on the node. The agent while acting on the SET operation would perform a checksum computation on the FTPed file and compare against this object. If they differ, the SET operation would be negated. If same, the file is considered valid and this value is stored in a persistent database. SCT files across the network with the same combination of card type, sct type, major and minor versions would have the same checksum.
STR cwSctFileDescription	1.3.6.1.4.1.9.9.236.1.1.1.8	SnmpAdminString	read-create	A description string can be associated with a specific SCT index and in turn the SCT file. This may be used for associating customized filenames.
INT cwSctFileOperStatusEx	1.3.6.1.4.1.9.9.236.1.1.1.9	INTEGER	read-only	Reflects the operational status of the SCT file. The agent sets the value to valid(1) if the computed checksum of the SCT file matches the provisioned checksum. The agent sets the value to invalid(2) if the computed checksum of the SCT file mismatches with the provisioned checksum. This usually suggests a corrupted SCT file. The agent sets the value to absent(3) if the file is missing in the secure area of the disk, while a row exists in the SCT file management table.
ROW cwSctFileRowStatus	1.3.6.1.4.1.9.9.236.1.1.1.10	RowStatus	read-create	* To create a row, the manager needs to perform a SET operations with a 'CreateAndGo' option. The agent would validate the file specified by the indices if found valid would create a new row. * SET operation with 'CreateAndWait' option will be rejected by the agent. * SET operations with 'active' option would be treated as a modify operation. The only objects that can be modified in a row are the cwSctFileDescription and the cwSctFileMinorVersion. * SET operation with a 'Destroy' option would be used for deleting a row in the cwSctFileMgmtTable and its associated SCT file in the switch. * The GET status of this object would always return 'active'.
ciscoWanSctMgmtMIBConformance	1.3.6.1.4.1.9.9.236.3
ciscoWanSctMgmtMIBCompliances	1.3.6.1.4.1.9.9.236.3.1
cwSctFileMgmtMIBCompliance	1.3.6.1.4.1.9.9.236.3.1.1			The compliance statement for Cisco SCT file management group.
ciscoWanSctMgmtMIBGroups	1.3.6.1.4.1.9.9.236.3.2
cwSctFileMgmtObjectGroup	1.3.6.1.4.1.9.9.236.3.2.1			Objects used for SCT file management.

RFC description

Manages Service Class Template (SCT) files in Cisco WAN nodes, defining traffic characteristics by quality of service.

Start monitoring Cisco MGX WAN switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-WAN-SCT-MGMT-MIB