All MIBs › CHASSIS-MIB › chasModuleAdminStatus
chasModuleAdminStatus
Module: CHASSIS-MIB
OID (symbolic): CHASSIS-MIB::chasModuleAdminStatus
OID (numeric): 1.3.6.1.4.1.800.2.1.2.1.1.13
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: Provides desired (and actual) state of the given module. Notice that not all values may be supported by a specified physical module. In this case an SNMP error returned when a set is attempted.
All modules (even empty slots) are in an unknown(1) state when the chassis first powers up.
The invalid state is for non-existant modules, and hence is never seen. Neither of the unknown(1) or invalid(2) status values can be written.
A physical module can be activated by writing a value of enable(3).
A physical module may be de-activated by writing a value of disable(4). In a disabled state, the module is present in the chassis, but is benign. A disabled module is availible for subsequent activation.
Writing a value of reset(5), disables the module AND initiates a reset sequence.
Writing a value of load(6), disables the module AND initiates a software load sequence.
Writing a value of test(7), disables the module AND initiates selftest within the module.
What is chasModuleAdminStatus?
This object lets an admin request a desired operational state for a specific module, such as enabling, disabling, resetting, reloading firmware onto, or testing it, with the description noting that all modules start in unknown(1) state at chassis power-up and that not every module type supports every value. This gives remote SNMP-based control over individual cards without needing console access, so an admin can remotely reset a misbehaving line card rather than sending someone to the site; attempting an unsupported value on a card without self-test support returns an SNMP error rather than silently failing. An admin remotely troubleshooting a hung network interface module would SET chasModuleAdminStatus to reset(5) on that module's row to force a reboot without power-cycling the whole chassis.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.800.2.1.2.1.1.13 snmpwalk -v2c -c public <target> CHASSIS-MIB::chasModuleAdminStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.800.2.1.2.1.1.13.1 snmpget -v2c -c public <target> CHASSIS-MIB::chasModuleAdminStatus.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.800.2.1.2.1.1.13.1 i <value>
Start monitoring Modular/chassis-based network switches and routers (any vendor) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CHASSIS-MIB::chasModuleAdminStatus OID value, configure state conditions and alerts, and monitor any Modular/chassis-based network switches and routers (any vendor) from a single console.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.800 | xylan | XYLAN-BASE-MIB |
| 1.3.6.1.4.1.800.2 | xylanArch | XYLAN-BASE-MIB |
| 1.3.6.1.4.1.800.2.1 | xylanChassis | XYLAN-BASE-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.800.2.1.2 | chasPhysical | CHASSIS-MIB |
| 1.3.6.1.4.1.800.2.1.2.1 | chasModuleTable | CHASSIS-MIB |
| 1.3.6.1.4.1.800.2.1.2.1.1 | chasModuleEntry | CHASSIS-MIB |
| 1.3.6.1.4.1.800.2.1.2.1.1.13 | chasModuleAdminStatus | CHASSIS-MIB |