All MIBs › CHASSIS-MIB › chasModuleSubUnit
chasModuleSubUnit
Module: CHASSIS-MIB
OID (symbolic): CHASSIS-MIB::chasModuleSubUnit
OID (numeric): 1.3.6.1.4.1.800.2.1.2.1.1.2
Node type: OBJECT-TYPE
Type: XylanModuleSubunit
Access: read-only
Description: The sub-unit number within module in slot 'n'. For each non-empty slot there will exist a module entry with a chasModuleSubUnit value of base. If the chasModuleType of that chasModuleEntry is hsm, then there may be additional chasModuleEntrys with the same chasModuleSlot value but with chasModuleSubUnit values of hsm1, hsm2 or csm3. These are HSM or CSM-U sub-modules. An HSM module can have up to 2 daughter cards on it. The first position would be denoted by hsm1(2) and the second position is hsm2(3). A CSM-U module can have up to 3 daughter cards on it.The first position would be denoted by hsm1(2) and the second position is hsm2(3) and the third postion is csm3(4).
The general implication of this field is: each occupied slot will have an entry field will be base(1), and may if the module supports daughter cards have entries for which if this field is hsm1(2), hsm2(3) or cms3(4), corrosponding to an installed daughter card on the HSM or CMS-U in the specified chasModuleSlot. (and the card type will be listed in chasModuleType).
What is chasModuleSubUnit?
This object distinguishes a module's own base unit from any High-Speed Sub-Modules (HSM) or CSM-U sub-modules plugged into it, since a single slot can host multiple entries sharing the same chasModuleSlot but different subunit values (base, hsm1, hsm2, csm3). An admin managing chassis with hierarchical sub-modular cards needs this field to correctly associate management data, like port counts or firmware version, with the specific sub-module rather than mistakenly attributing it to the parent card. A slot containing a base HSM carrier plus two daughter cards would show three module-table rows for the same slot, distinguished by chasModuleSubUnit values of base, hsm1, and hsm2.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.800.2.1.2.1.1.2 snmpwalk -v2c -c public <target> CHASSIS-MIB::chasModuleSubUnit
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.800.2.1.2.1.1.2.1 snmpget -v2c -c public <target> CHASSIS-MIB::chasModuleSubUnit.1
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::chasModuleSubUnit 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.2 | chasModuleSubUnit | CHASSIS-MIB |