ALPHA-NOTIFICATION-MIB

        This MIB defines the notification block(s) available in system controllers.
    
Source file
ALPHA-NOTIFICATION-MIB
Last revised
Identity
alphaAlarmNotifications
Base OID
1.3.6.1.4.1.7309.100
Imported Objects
ALARM-MIB alarmActiveModelPointer alarmActiveResourceId alarmModelDescription
ALPHA-RESOURCE-MIB alpha componentListReference componentListStaticName controllerInfoName
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
Net-SNMP examples using the alpha MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'ALPHA-NOTIFICATION-MIB' -M '/opt/observium/mibs/alpha:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ALPHA-NOTIFICATION-MIB::alphaAlarmNotifications'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ALPHA-NOTIFICATION-MIB' -M '/opt/observium/mibs/alpha:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ALPHA-NOTIFICATION-MIB::alphaAlarmNotifications'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (9)
.1.3.6.1.4.1.7309.100
.1.3.6.1.4.1.7309.100.102
.1.3.6.1.4.1.7309.100.102.1
.1.3.6.1.4.1.7309.100.102.1.2
.1.3.6.1.4.1.7309.101
.1.3.6.1.4.1.7309.101.1
OctetString
.1.3.6.1.4.1.7309.101.2
OctetString
.1.3.6.1.4.1.7309.101.3
OctetString
.1.3.6.1.4.1.7309.101.4
Dependencies (17) 4 direct · 13 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Conformance Groups (2)
Active alpha list group.
.1.3.6.1.4.1.7309.100.102.1.2.1
The collection of notifications that can be used to
model alarms for faults lacking pre-existing
notification definitions.
.1.3.6.1.4.1.7309.100.102.1.2.2
Compliance Statements (1)

OID .1.3.6.1.4.1.7309.100.102.1.1
The compliance statement for systems supporting
the alpha MIB.
Required groups
mandatory alphaParameterGroup
optional alphaNotificationsGroup Alarm extension group for Alpha specific data field.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.7309.100.1
SNMPv2 notification varbinds start with SysUptime
and Notification Oid as the first two in the list
by default. The first varbind in this definition
would be the third varbind in the raw output of the
notification.

An instance of the alarm indicated by
alarmActiveModelPointer has been raised
against the entity indicated by
alarmActiveResourceId.

The state of the alarm is indicated by the
alarmModelState.

The description of the alarm along with its source
is indicated by the alarmModelDescription and
componentListStaticName respectively.

componentListSnmpId provides the Id set to the
source of the alarm.

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 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.
.1.3.6.1.4.1.7309.100.2
SNMPv2 notification varbinds start with SysUptime
and Notification Oid as the first two in the list
by default. The first varbind in this definition
would be the third varbind in the raw output of the
notification.

An instance of the alarm indicated by
alarmActiveModelPointer has been cleared against
the entity indicated by alarmActiveResourceId.

The state of the alarm is indicated by the
alarmModelState.

The description of the alarm along with its source
is indicated by the alarmModelDescription and
componentListStaticName respectively.

componentListSnmpId provides the Id set to the
source of the alarm.

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 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.