AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | Infra | IoT | IT Service | Linux | Network/System | Performance | Protocol | SaaS | Security | Service Level | SNMP | Storage | VMware | VoIP | Web | Wireless

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » RFC » ALARM-MIB » Objects

ALARM-MIB.mib object view, vendor RFC

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file ALARM-MIB and use it to monitor vendor specific OID's.

ALARM-MIB file content

Object view of ALARM-MIB:

Scalar Object
alarmModelLastChanged .1.3.6.1.2.1.118.1.1.1
The value of sysUpTime at the time of the last creation, deletion or modification of an entry in the alarmModelTable. If the number and content of entries has been unchanged since the last re-initialization of the local network management subsystem, then the value of this object MUST be zero.
alarmModelEntry .1.3.6.1.2.1.118.1.1.2.1
Entries appear in this table for each possible alarm state. This table MUST be persistent across system reboots.
alarmActiveLastChanged .1.3.6.1.2.1.118.1.2.1
The value of sysUpTime at the time of the last creation or deletion of an entry in the alarmActiveTable. If the number of entries has been unchanged since the last re-initialization of the local network management subsystem, then this object contains a zero value.
alarmActiveOverflow .1.3.6.1.2.1.118.1.2.5
The number of active alarms that have not been put into the alarmActiveTable since system restart as a result of extreme resource constraints.
alarmActiveEntry .1.3.6.1.2.1.118.1.2.2.1
Entries appear in this table when alarms are raised. They are removed when the alarm is cleared. If under extreme resource constraint the system is unable to add any more entries into this table, then the alarmActiveOverflow statistic will be increased by one.
alarmActiveVariableEntry .1.3.6.1.2.1.118.1.2.3.1
Entries appear in this table when there are variables in the varbind list of a corresponding alarm in alarmActiveTable. Entries appear in this table as though the trap/notification had been transported using a SNMPv2-Trap-PDU, as defined in [RFC3416] - i.e., the alarmActiveVariableIndex 1 will always be sysUpTime and alarmActiveVariableIndex 2 will always be snmpTrapOID. If the incoming notification is instead an SNMPv1 Trap-PDU and the value of alarmModelVarbindIndex is 1 or 2, an appropriate value for sysUpTime.0 or snmpTrapOID.0 shall be determined by using the rules in section 3.1 of [RFC3584].
alarmActiveStatsEntry .1.3.6.1.2.1.118.1.2.4.1
Statistics on the current active alarms.
alarmClearMaximum .1.3.6.1.2.1.118.1.3.1
This object specifies the maximum number of cleared alarms to store in the alarmClearTable. When this number is reached, the cleared alarms with the earliest clear time will be removed from the table.
alarmClearEntry .1.3.6.1.2.1.118.1.3.2.1
Information on a cleared alarm.
Tabular Object
alarmListName .1.3.6.1.2.1.118.1.2.2.1.1
The name of the list of alarms. This SHOULD be the same as nlmLogName if the Notification Log MIB [RFC3014] is supported. This SHOULD be the same as, or contain as a prefix, the applicable snmpNotifyFilterProfileName if the SNMP-NOTIFICATION-MIB DEFINITIONS [RFC3413] is supported. An implementation may allow multiple named alarm lists, up to some implementation-specific limit (which may be none). A zero-length list name is reserved for creation and deletion by the managed system, and MUST be used as the default log name by systems that do not support named alarm lists.
alarmModelIndex .1.3.6.1.2.1.118.1.1.2.1.1
An integer that acts as an alarm Id to uniquely identify each alarm within the named alarm list.
alarmModelState .1.3.6.1.2.1.118.1.1.2.1.2
A value of 1 MUST indicate a clear alarm state. The value of this object MUST be less than the alarmModelState of more severe alarm states for this alarm. The value of this object MUST be more than the alarmModelState of less severe alarm states for this alarm.
alarmModelNotificationId .1.3.6.1.2.1.118.1.1.2.1.3
The NOTIFICATION-TYPE object identifier of this alarm state transition. If there is no notification associated with this alarm state, the value of this object MUST be '0.0'
alarmModelVarbindIndex .1.3.6.1.2.1.118.1.1.2.1.4
The index into the varbind listing of the notification indicated by alarmModelNotificationId which helps signal that the given alarm has changed state. If there is no applicable varbind, the value of this object MUST be zero. Note that the value of alarmModelVarbindIndex acknowledges the existence of the first two obligatory varbinds in the InformRequest-PDU and SNMPv2-Trap-PDU (sysUpTime.0 and snmpTrapOID.0). That is, a value of 2 refers to the snmpTrapOID.0. If the incoming notification is instead an SNMPv1 Trap-PDU, then an appropriate value for sysUpTime.0 or snmpTrapOID.0 shall be determined by using the rules in section 3.1 of [RFC3584]
alarmModelVarbindValue .1.3.6.1.2.1.118.1.1.2.1.5
The value that the varbind indicated by alarmModelVarbindIndex takes to indicate that the alarm has entered this state. If alarmModelVarbindIndex has a value of 0, so MUST alarmModelVarbindValue.
alarmModelDescription .1.3.6.1.2.1.118.1.1.2.1.6
A brief description of this alarm and state suitable to display to operators.
alarmModelSpecificPointer .1.3.6.1.2.1.118.1.1.2.1.7
If no additional, model-specific Alarm MIB is supported by the system the value of this object is `0.0'and attempts to set it to any other value MUST be rejected appropriately. When a model-specific Alarm MIB is supported, this object MUST refer to the first accessible object in a corresponding row of the model definition in one of these model-specific MIB and attempts to set this object to { 0 0 } or any other value MUST be rejected appropriately.
alarmModelVarbindSubtree .1.3.6.1.2.1.118.1.1.2.1.8
The name portion of each VarBind in the notification, in order, is compared to the value of this object. If the name is equal to or a subtree of the value of this object, for purposes of computing the value of AlarmActiveResourceID the 'prefix' will be the matching portion, and the 'indexes' will be any remainder. The examination of varbinds ends with the first match. If the value of this object is 0.0, then the first varbind, or in the case of v2, the first varbind after the timestamp and the trap OID, will always be matched.
alarmModelResourcePrefix .1.3.6.1.2.1.118.1.1.2.1.9
The value of AlarmActiveResourceId is computed by appending any indexes extracted in accordance with the description of alarmModelVarbindSubtree onto the value of this object. If this object's value is 0.0, then the 'prefix' extracted is used instead.
alarmModelRowStatus .1.3.6.1.2.1.118.1.1.2.1.10
Control for creating and deleting entries. Entries may be modified while active. Alarms whose alarmModelRowStatus is not active will not appear in either the alarmActiveTable or the alarmClearTable. Setting this object to notInService cannot be used as an alarm suppression mechanism. Entries that are notInService will disappear as described in RFC2579. This row can not be modified while it is being referenced by a value of alarmActiveModelPointer. In these cases, an error of `inconsistentValue' will be returned to the manager. This entry may be deleted while it is being referenced by a value of alarmActiveModelPointer. This results in the deletion of this entry and entries in the active alarms referencing this entry via an alarmActiveModelPointer. As all read-create objects in this table have a DEFVAL clause, there is no requirement that any object be explicitly set before this row can become active. Note that a row consisting only of default values is not very meaningful.
alarmActiveDateAndTime .1.3.6.1.2.1.118.1.2.2.1.2
The local date and time when the error occurred. This object facilitates retrieving all instances of alarms that have been raised or have changed state since a given point in time. Implementations MUST include the offset from UTC, if available. Implementation in environments in which the UTC offset is not available is NOT RECOMMENDED.
alarmActiveIndex .1.3.6.1.2.1.118.1.2.2.1.3
A strictly monotonically increasing integer which acts as the index of entries within the named alarm list. It wraps back to 1 after it reaches its maximum value.
alarmActiveEngineID .1.3.6.1.2.1.118.1.2.2.1.4
The identification of the SNMP engine at which the alarm originated. If the alarm is from an SNMPv1 system this object is a zero length string.
alarmActiveEngineAddressType .1.3.6.1.2.1.118.1.2.2.1.5
This object indicates what type of address is stored in the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc.
alarmActiveEngineAddress .1.3.6.1.2.1.118.1.2.2.1.6
The address of the SNMP engine on which the alarm is occurring. This object MUST always be instantiated, even if the list can contain alarms from only one engine.
alarmActiveContextName .1.3.6.1.2.1.118.1.2.2.1.7
The name of the SNMP MIB context from which the alarm came. For SNMPv1 alarms this is the community string from the Trap. Note that care MUST be taken when selecting community strings to ensure that these can be represented as a well-formed SnmpAdminString. Community or Context names that are not well-formed SnmpAdminStrings will be mapped to zero length strings. If the alarm's source SNMP engine is known not to support multiple contexts, this object is a zero length string.
alarmActiveVariables .1.3.6.1.2.1.118.1.2.2.1.8
The number of variables in alarmActiveVariableTable for this alarm.
alarmActiveNotificationID .1.3.6.1.2.1.118.1.2.2.1.9
The NOTIFICATION-TYPE object identifier of the alarm state transition that is occurring.
alarmActiveResourceId .1.3.6.1.2.1.118.1.2.2.1.10
This object identifies the resource under alarm. If there is no corresponding resource, then the value of this object MUST be 0.0.
alarmActiveDescription .1.3.6.1.2.1.118.1.2.2.1.11
This object provides a textual description of the active alarm. This text is generated dynamically by the notification generator to provide useful information to the human operator. This information SHOULD provide information allowing the operator to locate the resource for which this alarm is being generated. This information is not intended for consumption by automated tools.
alarmActiveLogPointer .1.3.6.1.2.1.118.1.2.2.1.12
A pointer to the corresponding row in a notification logging MIB where the state change notification for this active alarm is logged. If no log entry applies to this active alarm, then this object MUST have the value of 0.0
alarmActiveModelPointer .1.3.6.1.2.1.118.1.2.2.1.13
A pointer to the corresponding row in the alarmModelTable for this active alarm. This points not only to the alarm model being instantiated, but also to the specific alarm state that is active.
alarmActiveSpecificPointer .1.3.6.1.2.1.118.1.2.2.1.14
If no additional, model-specific, Alarm MIB is supported by the system this object is `0.0'. When a model-specific Alarm MIB is supported, this object is the instance pointer to the specific model-specific active alarm list.
alarmActiveVariableIndex .1.3.6.1.2.1.118.1.2.3.1.1
A strictly monotonically increasing integer, starting at 1 for a given alarmActiveIndex, for indexing variables within the active alarm variable list.
alarmActiveVariableID .1.3.6.1.2.1.118.1.2.3.1.2
The alarm variable's object identifier.
alarmActiveVariableValueType .1.3.6.1.2.1.118.1.2.3.1.3
The type of the value. One and only one of the value objects that follow is used for a given row in this table, based on this type.
alarmActiveVariableCounter32Val .1.3.6.1.2.1.118.1.2.3.1.4
The value when alarmActiveVariableType is 'counter32'.
alarmActiveVariableUnsigned32Val .1.3.6.1.2.1.118.1.2.3.1.5
The value when alarmActiveVariableType is 'unsigned32'.
alarmActiveVariableTimeTicksVal .1.3.6.1.2.1.118.1.2.3.1.6
The value when alarmActiveVariableType is 'timeTicks'.
alarmActiveVariableInteger32Val .1.3.6.1.2.1.118.1.2.3.1.7
The value when alarmActiveVariableType is 'integer32'.
alarmActiveVariableOctetStringVal .1.3.6.1.2.1.118.1.2.3.1.8
The value when alarmActiveVariableType is 'octetString'.
alarmActiveVariableIpAddressVal .1.3.6.1.2.1.118.1.2.3.1.9
The value when alarmActiveVariableType is 'ipAddress'.
alarmActiveVariableOidVal .1.3.6.1.2.1.118.1.2.3.1.10
The value when alarmActiveVariableType is 'objectId'.
alarmActiveVariableCounter64Val .1.3.6.1.2.1.118.1.2.3.1.11
The value when alarmActiveVariableType is 'counter64'.
alarmActiveVariableOpaqueVal .1.3.6.1.2.1.118.1.2.3.1.12
The value when alarmActiveVariableType is 'opaque'. Note that although RFC2578 [RFC2578] forbids the use of Opaque in 'standard' MIB modules, this particular usage is driven by the need to be able to accurately represent any well-formed notification, and justified by the need for backward compatibility.
alarmActiveStatsActiveCurrent .1.3.6.1.2.1.118.1.2.4.1.1
The total number of currently active alarms on the system.
alarmActiveStatsActives .1.3.6.1.2.1.118.1.2.4.1.2
The total number of active alarms since system restarted.
alarmActiveStatsLastRaise .1.3.6.1.2.1.118.1.2.4.1.3
The value of sysUpTime at the time of the last alarm raise for this alarm list. If no alarm raises have occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.
alarmActiveStatsLastClear .1.3.6.1.2.1.118.1.2.4.1.4
The value of sysUpTime at the time of the last alarm clear for this alarm list. If no alarm clears have occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.
alarmClearDateAndTime .1.3.6.1.2.1.118.1.3.2.1.2
The local date and time when the alarm cleared. This object facilitates retrieving all instances of alarms that have been cleared since a given point in time. Implementations MUST include the offset from UTC, if available. Implementation in environments in which the UTC offset is not available is NOT RECOMMENDED.
alarmClearIndex .1.3.6.1.2.1.118.1.3.2.1.1
An integer which acts as the index of entries within the named alarm list. It wraps back to 1 after it reaches its maximum value. This object has the same value as the alarmActiveIndex that this alarm instance had when it was active.
alarmClearEngineID .1.3.6.1.2.1.118.1.3.2.1.3
The identification of the SNMP engine at which the alarm originated. If the alarm is from an SNMPv1 system this object is a zero length string.
alarmClearEngineAddressType .1.3.6.1.2.1.118.1.3.2.1.4
This object indicates what type of address is stored in the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc.
alarmClearEngineAddress .1.3.6.1.2.1.118.1.3.2.1.5
The Address of the SNMP engine on which the alarm was occurring. This is used to identify the source of an SNMPv1 trap, since an alarmActiveEngineId cannot be extracted from the SNMPv1 trap PDU. This object MUST always be instantiated, even if the list can contain alarms from only one engine.
alarmClearContextName .1.3.6.1.2.1.118.1.3.2.1.6
The name of the SNMP MIB context from which the alarm came. For SNMPv1 traps this is the community string from the Trap. Note that care needs to be taken when selecting community strings to ensure that these can be represented as a well-formed SnmpAdminString. Community or Context names that are not well-formed SnmpAdminStrings will be mapped to zero length strings. If the alarm's source SNMP engine is known not to support multiple contexts, this object is a zero length string.
alarmClearNotificationID .1.3.6.1.2.1.118.1.3.2.1.7
The NOTIFICATION-TYPE object identifier of the alarm clear.
alarmClearResourceId .1.3.6.1.2.1.118.1.3.2.1.8
This object identifies the resource that was under alarm. If there is no corresponding resource, then the value of this object MUST be 0.0.
alarmClearLogIndex .1.3.6.1.2.1.118.1.3.2.1.9
This number MUST be the same as the log index of the applicable row in the notification log MIB, if it exists. If no log index applies to the trap, then this object MUST have the value of 0.
alarmClearModelPointer .1.3.6.1.2.1.118.1.3.2.1.10
A pointer to the corresponding row in the alarmModelTable for this cleared alarm.
Table
alarmModelTable .1.3.6.1.2.1.118.1.1.2
A table of information about possible alarms on the system, and how they have been modelled.
alarmActiveTable .1.3.6.1.2.1.118.1.2.2
A table of Active Alarms entries.
alarmActiveVariableTable .1.3.6.1.2.1.118.1.2.3
A table of variables to go with active alarm entries.
alarmActiveStatsTable .1.3.6.1.2.1.118.1.2.4
This table represents the alarm statistics information.
alarmClearTable .1.3.6.1.2.1.118.1.3.2
This table contains information on cleared alarms.
Trap
alarmActiveState .1.3.6.1.2.1.118.0.2
An instance of the alarm indicated by alarmActiveModelPointer has been raised against the entity indicated by alarmActiveResourceId. The agent must throttle the generation of consecutive alarmActiveState traps so that there is at least a two-second gap between traps of this type against the same alarmActiveModelPointer and alarmActiveResourceId. When traps are throttled, they are dropped, not queued for sending at a future time. A management application should periodically check the value of alarmActiveLastChanged to detect any missed alarmActiveState notification-events, e.g., due to throttling or transmission loss.
alarmClearState .1.3.6.1.2.1.118.0.3
An instance of the alarm indicated by alarmActiveModelPointer has been cleared against the entity indicated by alarmActiveResourceId. The agent must throttle the generation of consecutive alarmActiveClear traps so that there is at least a two-second gap between traps of this type against the same alarmActiveModelPointer and alarmActiveResourceId. When traps are throttled, they are dropped, not queued for sending at a future time. A management application should periodically check the value of alarmActiveLastChanged to detect any missed alarmClearState notification-events, e.g., due to throttling or transmission loss.
Object Identifier
alarmMIB .1.3.6.1.2.1.118
The MIB module describes a generic solution to model alarms and to store the current list of active alarms. Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3877. For full legal notices see the RFC itself. Supplementary information may be available on: http://www.ietf.org/copyrights/ianamib.html
alarmObjects .1.3.6.1.2.1.118.1
alarmNotifications .1.3.6.1.2.1.118.0
alarmModel .1.3.6.1.2.1.118.1.1
alarmActive .1.3.6.1.2.1.118.1.2
alarmClear .1.3.6.1.2.1.118.1.3
alarmConformance .1.3.6.1.2.1.118.2
alarmCompliances .1.3.6.1.2.1.118.2.1
alarmGroups .1.3.6.1.2.1.118.2.2
Group
alarmActiveGroup .1.3.6.1.2.1.118.2.2.2
Active Alarm list group.
alarmModelGroup .1.3.6.1.2.1.118.2.2.1
Alarm model group.
alarmActiveStatsGroup .1.3.6.1.2.1.118.2.2.3
Active alarm summary group.
alarmClearGroup .1.3.6.1.2.1.118.2.2.4
Cleared alarm group.
alarmNotificationsGroup .1.3.6.1.2.1.118.2.2.6
The collection of notifications that can be used to model alarms for faults lacking pre-existing notification definitions.