Reference record for OID 1.3.6.1.2.1.33.1.6.2


parent
1.3.6.1.2.1.33.1.6 (upsAlarm)
node code
2
node name
upsAlarmTable
dot oid
1.3.6.1.2.1.33.1.6.2
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) upsMIB(33) upsObjects(1) upsAlarm(6) upsAlarmTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) upsMIB(33) upsObjects(1) upsAlarm(6) upsAlarmTable(2)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) upsMIB(33) upsObjects(1) upsAlarm(6) upsAlarmTable(2)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) upsMIB(33) upsObjects(1) upsAlarm(6) upsAlarmTable(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) upsMIB(33) upsObjects(1) upsAlarm(6) upsAlarmTable(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) upsMIB(33) upsObjects(1) upsAlarm(6) upsAlarmTable(2)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/upsMIB/upsObjects/upsAlarm/upsAlarmTable
  • /iso/identified-organization/dod/internet/mgmt/mib/upsMIB/upsObjects/upsAlarm/upsAlarmTable
  • /iso/org/dod/internet/mgmt/mib-2/upsMIB/upsObjects/upsAlarm/upsAlarmTable
  • /iso/org/dod/internet/mgmt/mib/upsMIB/upsObjects/upsAlarm/upsAlarmTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/upsMIB/upsObjects/upsAlarm/upsAlarmTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/upsMIB/upsObjects/upsAlarm/upsAlarmTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/33/1/6/2

    Description by oid_info

    upsAlarmTable OBJECT-TYPE
    SYNTAX SEQUENCE OF UpsAlarmEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
    "A list of alarm table entries. The table contains
    zero, one, or many rows at any moment, depending upon
    the number of alarm conditions in effect. The table
    is initially empty at agent startup. The agent
    creates a row in the table each time a condition is
    detected and deletes that row when that condition no
    longer pertains. The agent creates the first row with
    upsAlarmId equal to 1, and increments the value of
    upsAlarmId each time a new row is created, wrapping to
    the first free value greater than or equal to 1 when
    the maximum value of upsAlarmId would otherwise be
    exceeded. Consequently, after multiple operations,
    the table may become sparse, e.g., containing entries
    for rows 95, 100, 101, and 203 and the entries should
    not be assumed to be in chronological order because
    upsAlarmId might have wrapped.
    Alarms are named by an AutonomousType (OBJECT
    IDENTIFIER), upsAlarmDescr, to allow a single table to
    reflect well known alarms plus alarms defined by a
    particular implementation, i.e., as documented in the
    private enterprise MIB definition for the device. No
    two rows will have the same value of upsAlarmDescr,
    since alarms define conditions. In order to meet this
    requirement, care should be taken in the definition of
    alarm conditions to insure that a system cannot enter
    the same condition multiple times simultaneously.
    The number of rows in the table at any given time is
    reflected by the value of upsAlarmsPresent."

    View at oid-info.com

    Description by mibdepot

    A list of alarm table entries. The table contains
    zero, one, or many rows at any moment, depending upon
    the number of alarm conditions in effect. The table
    is initially empty at agent startup. The agent
    creates a row in the table each time a condition is
    detected and deletes that row when that condition no
    longer pertains. The agent creates the first row with
    upsAlarmId equal to 1, and increments the value of
    upsAlarmId each time a new row is created, wrapping to
    the first free value greater than or equal to 1 when
    the maximum value of upsAlarmId would otherwise be
    exceeded. Consequently, after multiple operations,
    the table may become sparse, e.g., containing entries
    for rows 95, 100, 101, and 203 and the entries should
    not be assumed to be in chronological order because
    upsAlarmId might have wrapped.

    Alarms are named by an AutonomousType (OBJECT
    IDENTIFIER), upsAlarmDescr, to allow a single table to
    reflect well known alarms plus alarms defined by a
    particular implementation, i.e., as documented in the
    private enterprise MIB definition for the device. No
    two rows will have the same value of upsAlarmDescr,
    since alarms define conditions. In order to meet this
    requirement, care should be taken in the definition of
    alarm conditions to insure that a system cannot enter
    the same condition multiple times simultaneously.

    The number of rows in the table at any given time is
    reflected by the value of upsAlarmsPresent.

    Parsed from file UPS.mib.txt
    Company: None
    Module: UPS-MIB

    Description by circitor

    A list of alarm table entries. The table contains
    zero, one, or many rows at any moment, depending upon
    the number of alarm conditions in effect. The table
    is initially empty at agent startup. The agent
    creates a row in the table each time a condition is
    detected and deletes that row when that condition no
    longer pertains. The agent creates the first row with
    upsAlarmId equal to 1, and increments the value of
    upsAlarmId each time a new row is created, wrapping to
    the first free value greater than or equal to 1 when
    the maximum value of upsAlarmId would otherwise be
    exceeded. Consequently, after multiple operations,
    the table may become sparse, e.g., containing entries
    for rows 95, 100, 101, and 203 and the entries should
    not be assumed to be in chronological order because
    upsAlarmId might have wrapped.

    Alarms are named by an AutonomousType (OBJECT
    IDENTIFIER), upsAlarmDescr, to allow a single table to
    reflect well known alarms plus alarms defined by a
    particular implementation, i.e., as documented in the
    private enterprise MIB definition for the device. No
    two rows will have the same value of upsAlarmDescr,
    since alarms define conditions. In order to meet this
    requirement, care should be taken in the definition of
    alarm conditions to insure that a system cannot enter
    the same condition multiple times simultaneously.

    The number of rows in the table at any given time is
    reflected by the value of upsAlarmsPresent.

    Parsed from file UPS-MIB.mib
    Module: UPS-MIB

    Information by oid_info

    Automatically extracted from RFC1628

    Information by mibdepot

    upsAlarmTable OBJECT-TYPE SYNTAX SEQUENCE OF UpsAlarmEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A list of alarm table entries. The table contains zero, one, or many rows at any moment, depending upon the number of alarm conditions in effect. The table is initially empty at agent startup. The agent creates a row in the table each time a condition is detected and deletes that row when that condition no longer pertains. The agent creates the first row with upsAlarmId equal to 1, and increments the value of upsAlarmId each time a new row is created, wrapping to the first free value greater than or equal to 1 when the maximum value of upsAlarmId would otherwise be exceeded. Consequently, after multiple operations, the table may become sparse, e.g., containing entries for rows 95, 100, 101, and 203 and the entries should not be assumed to be in chronological order because upsAlarmId might have wrapped. Alarms are named by an AutonomousType (OBJECT IDENTIFIER), upsAlarmDescr, to allow a single table to reflect well known alarms plus alarms defined by a particular implementation, i.e., as documented in the private enterprise MIB definition for the device. No two rows will have the same value of upsAlarmDescr, since alarms define conditions. In order to meet this requirement, care should be taken in the definition of alarm conditions to insure that a system cannot enter the same condition multiple times simultaneously. The number of rows in the table at any given time is reflected by the value of upsAlarmsPresent." ::= { upsAlarm 2 }

    Information by circitor

    upsAlarmTable OBJECT-TYPE SYNTAX SEQUENCE OF UpsAlarmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of alarm table entries. The table contains zero, one, or many rows at any moment, depending upon the number of alarm conditions in effect. The table is initially empty at agent startup. The agent creates a row in the table each time a condition is detected and deletes that row when that condition no longer pertains. The agent creates the first row with upsAlarmId equal to 1, and increments the value of upsAlarmId each time a new row is created, wrapping to the first free value greater than or equal to 1 when the maximum value of upsAlarmId would otherwise be exceeded. Consequently, after multiple operations, the table may become sparse, e.g., containing entries for rows 95, 100, 101, and 203 and the entries should not be assumed to be in chronological order because upsAlarmId might have wrapped. Alarms are named by an AutonomousType (OBJECT IDENTIFIER), upsAlarmDescr, to allow a single table to reflect well known alarms plus alarms defined by a particular implementation, i.e., as documented in the private enterprise MIB definition for the device. No two rows will have the same value of upsAlarmDescr, since alarms define conditions. In order to meet this requirement, care should be taken in the definition of alarm conditions to insure that a system cannot enter the same condition multiple times simultaneously. The number of rows in the table at any given time is reflected by the value of upsAlarmsPresent." ::= { upsAlarm 2 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.33.1.6.2.1 upsAlarmEntry 3 3 An entry containing information applicable to a
    particular alarm.

    Brothers (4)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.33.1.6.1 upsAlarmsPresent 1 1 The present number of active alarm conditions.
    1.3.6.1.2.1.33.1.6.3 upsWellKnownAlarms 24 48 None
    1.3.6.1.2.1.33.1.6.4 upsAlarmID 1 1 A unique identifier for an alarm condition. This
    value must remain constant.
    1.3.6.1.2.1.33.1.6.5 upsAlarmDESCR 1 1 A reference to an alarm description object. The
    object references should not be accessible, but rather
    be used to provide a uniq…