OID reference
1.3.6.1.4.1.534.8.1.0.12
An update to the alarm entry at alarmID has occurred; however, the alarmLevel has not changed due to this update. This is normally seen with latching alarms when condition that caused the alarm is removed or recurs before the alarm has been closed. Alarm and source information are contained in the OBJECTS.
Identification
{1 3 6 1 4 1 534 8 1 0 12}
The displayed source records contain one distinct definition. Compare its source records.
powerChainAlarmUpdated NOTIFICATION-TYPE
OBJECTS { alarmID, alarmSequenceIndex, alarmDescription,
alarmValue, alarmLevel, entPhysicalName
}
STATUS current
DESCRIPTION
"An update to the alarm entry at alarmID has occurred;
however, the alarmLevel has not changed due to this update.
This is normally seen with latching alarms when condition that caused
the alarm is removed or recurs before the alarm has been closed.
Alarm and source information are contained in the OBJECTS."
::= { pxgNotifications 12 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
An update to the alarm entry at alarmID has occurred; however, the alarmLevel has not changed due to this update. This is normally seen with latching alarms when condition that caused the alarm is removed or recurs before the alarm has been closed. Alarm and source information are contained in the OBJECTS.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: powerChainAlarmUpdated
{
"smi_kind": "NOTIFICATION-TYPE",
"definition": [
"powerChainAlarmUpdated",
"NOTIFICATION-TYPE",
"OBJECTS",
"{",
"alarmID",
",",
"alarmSequenceIndex",
",",
"alarmDescription",
",",
"alarmValue",
",",
"alarmLevel",
",",
"entPhysicalName",
"}",
"STATUS",
"current",
"DESCRIPTION",
"\"An update to the alarm entry at alarmID has occurred; however, the alarmLevel has not changed due to this update. This is normally seen with latching alarms when condition that caused the alarm is removed or recurs before the alarm has been closed. Alarm and source information are contained in the OBJECTS.\"",
"::=",
"{",
"pxgNotifications",
"12",
"}"
],
"syntax_tree": [
[
"Objects",
[
"alarmID",
"alarmSequenceIndex",
"alarmDescription",
"alarmValue",
"alarmLevel",
"entPhysicalName"
]
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"An update to the alarm entry at alarmID has occurred; however, the alarmLevel has not changed due to this update. This is normally seen with latching alarms when condition that caused the alarm is removed or recurs before the alarm has been closed. Alarm and source information are contained in the OBJECTS."
],
null
]
}Vendor MIB copy from the Observium Community archive.
Module: EATON-PXG-MIB
See published definition above
{'SNMPv2-TC': ['TimeStamp'], 'EATON-OIDS': ['powerChain'], 'ENTITY-MIB': ['entPhysicalName'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Gauge32', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.534.8.1.0.1 | powerChainCriticalAlarmEvent | 0 | 0 | |
| 1.3.6.1.4.1.534.8.1.0.2 | powerChainCautionaryAlarmEvent | 0 | 0 | |
| 1.3.6.1.4.1.534.8.1.0.3 | powerChainAlarmEventAcknowledged | 0 | 0 | |
| 1.3.6.1.4.1.534.8.1.0.4 | powerChainEventCleared | 0 | 0 | |
| 1.3.6.1.4.1.534.8.1.0.5 | powerChainEvent | 0 | 0 | |
| 1.3.6.1.4.1.534.8.1.0.6 | powerChainAlarmEventClosed | 0 | 0 | |
| 1.3.6.1.4.1.534.8.1.0.7 | powerChainCriticalAlarm | 0 | 0 | |
| 1.3.6.1.4.1.534.8.1.0.8 | powerChainCautionaryAlarm | 0 | 0 | |
| 1.3.6.1.4.1.534.8.1.0.9 | powerChainAlarmAcknowledged | 0 | 0 | |
| 1.3.6.1.4.1.534.8.1.0.10 | powerChainAlarmCleared | 0 | 0 | |
| 1.3.6.1.4.1.534.8.1.0.11 | powerChainAlarmClosed | 0 | 0 |