upsAutoRestart

UPS-MIB · liebert variant · .1.3.6.1.2.1.33.1.8.5

Object

scalar r/w Enumeration
Setting this object to 'on' will cause the UPS system
to restart after a shutdown if the shutdown occurred
during a power loss as a result of either a
upsShutdownAfterDelay or an internal battery depleted
condition.  Setting this object to 'off' will prevent
the UPS system from restarting after a shutdown until
an operator manually or remotely explicitly restarts
it.  If the UPS is in a startup or reboot countdown,
then the UPS will not restart until that delay has
been satisfied.

Context

MIB
UPS-MIB
OID
.1.3.6.1.2.1.33.1.8.5
Type
scalar
Access
readwrite
Status
current
Parent
upsControl
Groups
3

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'UPS-MIB' -M '/opt/observium/mibs/liebert:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'UPS-MIB::upsAutoRestart.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'UPS-MIB' -M '/opt/observium/mibs/liebert:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'UPS-MIB::upsAutoRestart'

Syntax

Enumeration

Values & Constraints

Enumerated Values
1on
2off

Conformance

Member of
Compliance refinements
The upsAutoRestart is only applicable for UPS system shutdown.
Read-write access is not required, i.e., compliant
systems need not support more than one restart type.
Read-write access is not required, i.e., compliant
systems need not support more than one restart type.
Read-write access is not required, i.e., compliant
systems need not support more than one restart type.