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.
Parsed from file DEChub900-Common.mib.txt
Company: None
Module: DECHUB900-COMMON-MIB-V3-0
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.
Parsed from file DECHUB900-COMMON-MIB-V3-0.mib
Module: DECHUB900-COMMON-MIB-V3-0
Vendor: DEC
Module: DECHUB900-COMMON-MIB-V3-0
[Automatically extracted from oidview.com]
pcomOperStatus OBJECT-TYPE SYNTAX INTEGER { enabled(1), initializing(2), failure(3), nonFatalFailure(4), loading(5), disabled(6), needProgramLoad(7), testing(8), lowPowerMode(9) } ACCESS read-only STATUS mandatory 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." ::= { pcomSlot 1 }
pcomOperStatus OBJECT-TYPE SYNTAX INTEGER { enabled(1), initializing(2), failure(3), nonFatalFailure(4), loading(5), disabled(6), needProgramLoad(7), testing(8), lowPowerMode(9) } ACCESS read-only STATUS mandatory 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." ::= { pcomSlot 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.36.2.18.11.2.1.1.0 | pcomOperStatus | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.36.2.18.11.2.1.2 | pcomAdminStatus | 1 | 1 | enabled(1) - setting this object to enabled causes the device to begin it's power up sequence and attempt to enter its operationa… |
| 1.3.6.1.4.1.36.2.18.11.2.1.3 | pcomDiagFailure | 1 | 1 | This object contains the results of power-on self test. When zero, the unit passed self test okay. When non-zero and pcomOperSta… |
| 1.3.6.1.4.1.36.2.18.11.2.1.4 | pcomSerialNumber | 1 | 1 | Serial number for the module. This variable is set to a zero length string initially. Users may store a serial number for the mod… |
| 1.3.6.1.4.1.36.2.18.11.2.1.5 | pcomSlotNumber | 1 | 1 | Number of the slot in which module is inserted, as indicated by pins on the backplane connector. If module is not inserted in a … |
| 1.3.6.1.4.1.36.2.18.11.2.1.6 | pcomEsn | 1 | 1 | Extended Slot Number assigned to module. An ESN is a 32-bit integer which has a decimal representation that indicates the physica… |