Actual status of the power supply:
o unknown(1) - status not known.
o empty(2) - no power supply installed in slot
o disabled(3) - unable to supply power due to
chasPowerConfigAdminStatus
o bad(4) - unable to supply power due to failure
o warning(5) - supplying power but an output or
sensor is bad or warning
o standby(6) - believed usable but not supplying
power
o engaged(7) - supplying power
o redundant(8) - supplying power but not needed
It is an implementation specific matter whether
the agent keeps entries with status unknown(1) or
empty(2) in the table.
Parsed from file DEChub900-Chassis.mib.txt
Company: None
Module: DECHUB900-CHASSIS-MIB-V3-0
Actual status of the power supply:
o unknown(1) - status not known.
o empty(2) - no power supply installed in slot
o disabled(3) - unable to supply power due to
chasPowerConfigAdminStatus
o bad(4) - unable to supply power due to failure
o warning(5) - supplying power but an output or
sensor is bad or warning
o standby(6) - believed usable but not supplying
power
o engaged(7) - supplying power
o redundant(8) - supplying power but not needed
It is an implementation specific matter whether
the agent keeps entries with status unknown(1) or
empty(2) in the table.
Parsed from file DECHUB900-CHASSIS-MIB-V3-0.mib
Module: DECHUB900-CHASSIS-MIB-V3-0
Vendor: DEC
Module: DECHUB900-CHASSIS-MIB-V3-0
[Automatically extracted from oidview.com]
chasPowerConfigOperStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), empty(2), disabled(3), bad(4), warning(5), standby(6), engaged(7), redundant(8) } ACCESS read-only STATUS mandatory DESCRIPTION "Actual status of the power supply: o unknown(1) - status not known. o empty(2) - no power supply installed in slot o disabled(3) - unable to supply power due to chasPowerConfigAdminStatus o bad(4) - unable to supply power due to failure o warning(5) - supplying power but an output or sensor is bad or warning o standby(6) - believed usable but not supplying power o engaged(7) - supplying power o redundant(8) - supplying power but not needed It is an implementation specific matter whether the agent keeps entries with status unknown(1) or empty(2) in the table." ::= { chasPowerConfigEntry 4 }
chasPowerConfigOperStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), empty(2), disabled(3), bad(4), warning(5), standby(6), engaged(7), redundant(8) } ACCESS read-only STATUS mandatory DESCRIPTION "Actual status of the power supply: o unknown(1) - status not known. o empty(2) - no power supply installed in slot o disabled(3) - unable to supply power due to chasPowerConfigAdminStatus o bad(4) - unable to supply power due to failure o warning(5) - supplying power but an output or sensor is bad or warning o standby(6) - believed usable but not supplying power o engaged(7) - supplying power o redundant(8) - supplying power but not needed It is an implementation specific matter whether the agent keeps entries with status unknown(1) or empty(2) in the table." ::= { chasPowerConfigEntry 4 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.36.2.18.11.1.1.1.7.5.1.1 | chasPowerConfigIndex | 0 | 0 | An index value that uniquely identifies a power supply. |
| 1.3.6.1.4.1.36.2.18.11.1.1.1.7.5.1.2 | chasPowerConfigDescr | 0 | 0 | A textual description of the power supply, including the vendor's name and version. |
| 1.3.6.1.4.1.36.2.18.11.1.1.1.7.5.1.3 | chasPowerConfigAdminStatus | 0 | 0 | Desired status of the power supply. |
| 1.3.6.1.4.1.36.2.18.11.1.1.1.7.5.1.5 | chasPowerConfigHealthText | 0 | 0 | chasPowerConfigHealthtext |
| 1.3.6.1.4.1.36.2.18.11.1.1.1.7.5.1.6 | chasPowerConfigWarnings | 0 | 0 | The number of times chasPowerConfigOperStatus has gone to warning(5). |
| 1.3.6.1.4.1.36.2.18.11.1.1.1.7.5.1.7 | chasPowerConfigFailures | 0 | 0 | The number of times chasPowerConfigOperStatus has become bad(4). |