All MIBs › DECHUB900-COMMON-MIB-V3-0 › pcomOperStatus
pcomOperStatus
Module: DECHUB900-COMMON-MIB-V3-0
OID (symbolic): DECHUB900-COMMON-MIB-V3-0::pcomOperStatus
OID (numeric): 1.3.6.1.4.1.36.2.18.11.2.1.1
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: Describes the current operational state of the device. Operational status may be expressed as one of the following:
enabled(1) - indicates that the device in online and fully functional.
initializing(2) - indicates that the device is initializing. Devices enter the initializing state when powered on, or when reset.
failure(3) - indicates that the device's self-test has detected a fault. The device is functionally offline, and may or may not be powered.
nonFatalFailure(4) - indicates that the device's self-test has detected a non-fatal fault. The operates are less than a fully functional level in the presence of non-fatal errors.
loading(5) - indicates that the device is attempting to load.
disabled(6) - indicates that the device has been disabled. The device must still be able to respond to management messages.
needProgramLoad(7) - indicates that the device is waiting to be loaded.
testing(8) - indicates that the device in performing some form of diagnostic testing.
lowPowerMode(9) - indicates that the device is only partially powered. Some classes of device wait in this mode until the Hub Manager to grant additional power.
Modules may only be managed via an NMS when they are in the online and/or disabled states.
Not all components implement all state of this object. For example, if a component can not report 'failure', then it doesn't. The enabled and disabled states are supported by all components.
What is pcomOperStatus?
Reports the module's current operational state — enabled, initializing, failure, disabled, and similar — so a management station can tell whether a DEChub900 card is actually passing traffic. An admin polling this after inserting or resetting a card would expect to see initializing(2) briefly before it settles to enabled(1); values like failure(3) or nonFatalFailure(4) flag a self-test problem worth investigating.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.36.2.18.11.2.1.1 snmpwalk -v2c -c public <target> DECHUB900-COMMON-MIB-V3-0::pcomOperStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.36.2.18.11.2.1.1.1 snmpget -v2c -c public <target> DECHUB900-COMMON-MIB-V3-0::pcomOperStatus.1
Start monitoring DEC/Compaq DEChub 900 modular hub chassis with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DECHUB900-COMMON-MIB-V3-0::pcomOperStatus OID value, configure state conditions and alerts, and monitor any DEC/Compaq DEChub 900 modular hub chassis from a single console.
OID Breakdown
Upper-level ancestors (10 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.36 | dec | CMU-MIB |
| 1.3.6.1.4.1.36.2 | ema | DEC-ATM-CHASSIS-MIB |
| 1.3.6.1.4.1.36.2.18 | decMIBextension | DEC-ATM-CHASSIS-MIB |
| 1.3.6.1.4.1.36.2.18.11 | decHub900 | DECHUB900-CHASSIS-MIB-V3-0 |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.36.2.18.11.2 | pubCommon | DECHUB900-COMMON-MIB-V3-0 |
| 1.3.6.1.4.1.36.2.18.11.2.1 | pcomSlot | DECHUB900-COMMON-MIB-V3-0 |
| 1.3.6.1.4.1.36.2.18.11.2.1.1 | pcomOperStatus | DECHUB900-COMMON-MIB-V3-0 |