upsAlarmDescr

UPS-MIB · liebert variant · .1.3.6.1.2.1.33.1.6.2.1.2
Commands MIB view Table view

Object

column SNMPv2-TCAutonomousType 
A reference to an alarm description object.  The
object referenced should not be accessible, but rather
be used to provide a unique description of the alarm
condition.

Context

MIB
UPS-MIB
OID
.1.3.6.1.2.1.33.1.6.2.1.2
Type
column
Access
readonly
Status
current
Parent
upsAlarmEntry
Groups
3

Net-SNMP examples

How SNMP and these commands work

Walk the column to discover its indexed instances, or supply every index to read one instance.

Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'UPS-MIB' -M '/opt/observium/mibs/liebert:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'UPS-MIB::upsAlarmDescr'
More examples
Read one indexed 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::upsAlarmDescr.<upsAlarmId>'
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::upsAlarmDescr'

Syntax

SNMPv2-TCAutonomousType
Source
SNMPv2-TCAutonomousType
Base type
ObjectIdentifier
Type Description
Represents an independently extensible type identification
value.  It may, for example, indicate a particular sub-tree
with further MIB definitions, or define a particular type of
protocol or hardware.

Values & Constraints

No enumerated values or constraints recorded.

Conformance

Member of
upsBasicAlarmGroup upsFullAlarmGroup upsSubsetAlarmGroup
Compliance refinements
CLAB-UPS-MIB::clabUpsMibCompliance
Descriptions for the following well known alarm types:

upsAlarmBatteryBad,
upsAlarmOnBattery,
upsAlarmLowBattery,
upsAlarmDepletedBattery,
upsAlarmOutputOffAsRequested,
upsAlarmUpsOutputOff,
upsAlarmGeneralFault,
upsAlarmAwaitingPower,
upsAlarmShutdownPending,
upsAlarmShutdownImminent.
upsBasicCompliance
Support of all `well known' alarm types is not
required. The well known alarm types which must be
supported are: upsAlarmOnBattery, upsAlarmLowBattery,
upsAlarmDepletedBattery, upsAlarmTempBad,
upsAlarmInputBad, upsAlarmOutputOverload,
upsAlarmOnBypass, upsAlarmBypassBad,
upsAlarmOutputOffAsRequested,
upsAlarmUpsOffAsRequested, upsAlarmUpsOutputOff,
upsAlarmUpsSystemOff, upsAlarmGeneralFault,
upsAlarmDiagnosticTestFailed,
upsAlarmCommunicationsLost, upsAlarmShutdownPending,
and upsAlarmTestInProgress.
upsFullCompliance
Support of all `well known' alarm types is not
required. The well known alarm types which must be
supported are: upsAlarmBatteryBad, upsAlarmOnBattery,
upsAlarmLowBattery, upsAlarmDepletedBattery,
upsAlarmTempBad, upsAlarmInputBad, upsAlarmOnBypass,
upsAlarmBypassBad, upsAlarmOutputOffAsRequested,
upsAlarmUpsOffAsRequested, upsAlarmUpsOutputOff,
upsAlarmUpsSystemOff, upsAlarmGeneralFault,
upsAlarmDiagnosticTestFailed,
upsAlarmCommunicationsLost, upsAlarmShutdownPending,
and upsAlarmTestInProgress.
upsSubsetCompliance
Support of all `well known' alarm types is not
required. The well known alarm types which must be
supported are: upsAlarmOnBattery, upsAlarmLowBattery,
upsAlarmInputBad, upsAlarmUpsOutputOff,
upsAlarmUpsSystemOff, and upsAlarmTestInProgress.