CISCO-WAN-MODULE-MIB :: cwmIngressSCTFileId

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-WAN-MODULE-MIB › cwmIngressSCTFileId

cwmIngressSCTFileId

Module: CISCO-WAN-MODULE-MIB

OID (symbolic): CISCO-WAN-MODULE-MIB::cwmIngressSCTFileId

OID (numeric): 1.3.6.1.4.1.9.9.145.1.1.1.1.2

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-write

Description: The file ID of the Service Class Template(SCT) file. The SCT holds the connection specific parameters for this module in the ingress direction(From Network to the Switch).

Terminologies used: SCT : Service Class Template The Service Class Template ( or Service Template or SCT ) provides a means for inferring extended parameters, which are generally platform-specific, from the set of standard ATM protocol parameters passed in VSI(Virtual Switch Interface) connection setup primitives. A set of Service Templates are available in a non-volatile storage and is downloaded onto each Service Module on power up.

In general, SCTs contain two classes of data. One class consists of parameters necessary to establish a Virtual Connection (i.e. Per-VC) and includes entries such as UPC(Usage Parameter Control) actions, various bandwidth-related items, per-VC thresholds, and some hardware-specific items.The second class of data items includes those necessary to configure the associated Class-of-Service Buffers that provide the QoS support.

What is cwmIngressSCTFileId?

This read-write Unsigned32, ranging 0 to 255, is the file ID of the Service Class Template (SCT) file that holds connection-specific parameters for this module in the ingress direction (network to switch), described as inferring extended, platform-specific parameters from standard ATM protocol parameters. An admin sets this to select which SCT file governs how ingress connections on this module are treated at a detailed hardware level. Choosing the wrong SCT file ID here could apply the wrong platform-specific traffic parameters to every ingress connection on that module.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.145.1.1.1.1.2
snmpwalk -v2c -c public <target> CISCO-WAN-MODULE-MIB::cwmIngressSCTFileId

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.145.1.1.1.1.2.1
snmpget -v2c -c public <target> CISCO-WAN-MODULE-MIB::cwmIngressSCTFileId.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.9.9.145.1.1.1.1.2.1 i <value>

Start monitoring Cisco WAN switches (Service Modules, legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-WAN-MODULE-MIB::cwmIngressSCTFileId OID value, configure state conditions and alerts, and monitor any Cisco WAN switches (Service Modules, legacy) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.145ciscoWanModuleMIBCISCO-WAN-MODULE-MIB
1.3.6.1.4.1.9.9.145.1cwmMIBObjectsCISCO-WAN-MODULE-MIB
1.3.6.1.4.1.9.9.145.1.1cwmConfigCISCO-WAN-MODULE-MIB
1.3.6.1.4.1.9.9.145.1.1.1cwmConfigTableCISCO-WAN-MODULE-MIB
1.3.6.1.4.1.9.9.145.1.1.1.1cwmConfigEntryCISCO-WAN-MODULE-MIB
1.3.6.1.4.1.9.9.145.1.1.1.1.2cwmIngressSCTFileIdCISCO-WAN-MODULE-MIB