Indicates the number of the alarm. Alarms are numbered
sequentially from 1 - n. A management station can keep track
of the last event it uploaded and periodically GET-NEXT from
there to determine if there have been any new events. This
means that, as alarms are removed from the table their indices
are not reused until the next reset to default configuration
(which loses all stored alarms). The agent must store
the 'next available alarm number' value across
re-initializations of the system, resetting it to 1 only when
the configuration is reset to defaults.
Parsed from file qbsystem.mib.txt
Company: None
Module: QBSYS-SYSTEM-MIB
Indicates the number of the alarm. Alarms are numbered
sequentially from 1 - n. A management station can keep track
of the last event it uploaded and periodically GET-NEXT from
there to determine if there have been any new events. This
means that, as alarms are removed from the table their indices
are not reused until the next reset to default configuration
(which loses all stored alarms). The agent must store
the 'next available alarm number' value across
re-initializations of the system, resetting it to 1 only when
the configuration is reset to defaults.
Parsed from file QBSYS-SYSTEM-MIB.mib
Module: QBSYS-SYSTEM-MIB
Vendor: Quantum Bridge
Module: QBSYS-SYSTEM-MIB
[Automatically extracted from oidview.com]
qbSysAlarmHistoryIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "Indicates the number of the alarm. Alarms are numbered sequentially from 1 - n. A management station can keep track of the last event it uploaded and periodically GET-NEXT from there to determine if there have been any new events. This means that, as alarms are removed from the table their indices are not reused until the next reset to default configuration (which loses all stored alarms). The agent must store the 'next available alarm number' value across re-initializations of the system, resetting it to 1 only when the configuration is reset to defaults." ::= { qbSysAlarmHistoryEntry 1 }
qbSysAlarmHistoryIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "Indicates the number of the alarm. Alarms are numbered sequentially from 1 - n. A management station can keep track of the last event it uploaded and periodically GET-NEXT from there to determine if there have been any new events. This means that, as alarms are removed from the table their indices are not reused until the next reset to default configuration (which loses all stored alarms). The agent must store the 'next available alarm number' value across re-initializations of the system, resetting it to 1 only when the configuration is reset to defaults." ::= { qbSysAlarmHistoryEntry 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4323.2.2.1.3.7.1.2 | qbSysAlarmHistoryDateTime | 0 | 0 | The date and time when this alarm was generated. |
| 1.3.6.1.4.1.4323.2.2.1.3.7.1.3 | qbSysAlarmHistorySubsystem | 0 | 0 | The subsystem that generated this alarm. |
| 1.3.6.1.4.1.4323.2.2.1.3.7.1.4 | qbSysAlarmHistorySrvAffect | 0 | 0 | Describes whether the event was service affecting. |
| 1.3.6.1.4.1.4323.2.2.1.3.7.1.5 | qbSysAlarmHistorySeverity | 0 | 0 | The severity of the alarm. |
| 1.3.6.1.4.1.4323.2.2.1.3.7.1.6 | qbSysAlarmHistoryCondition | 0 | 0 | The condition of the alarm. |
| 1.3.6.1.4.1.4323.2.2.1.3.7.1.7 | qbSysAlarmHistoryId | 0 | 0 | The identifier of the alarm. This id is unique within a system. This is used to lookup the alarm description in the qbSysAlarmIdT… |
| 1.3.6.1.4.1.4323.2.2.1.3.7.1.8 | qbSysAlarmHistoryMsg | 0 | 0 | Textual message associated with the alarm. |