AIMOS :: aimosAlarmListRebuild

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsAIMOSaimosAlarmListRebuild

aimosAlarmListRebuild

Module: AIMOS

OID (symbolic): AIMOS::aimosAlarmListRebuild

OID (numeric): 1.3.6.1.4.1.6408.201.3.4.18

Node type: OBJECT-TYPE

Type: OperationMode

Access: read-write

Description: ATTENTION: Setting this objects value to start(5) will initiate an Alarm List
Rebuild process. During this process ALL ALARM INFORMATION WILL BE DELETED !

The Alarm List Rebuild process
==============================

When an employee discovers that the internal alarm table of the A.I.M.O.S. SNMP
Agent is flawed, an alarm list rebuild can be triggered. Such a process may also
be necessary if productive operation is to start after a test phase with an empty
alarm list.

The Alarm List Rebuild consists of the following steps:

. A SNMP Manager sets aimosAlarmListRebuild to start(5). The logged in user
  must belong the Provider.

. The A.I.M.O.S. SNMP Agent drops the contents of the internal alarm tables. The
  table is completely deleted; each alarm list entry for each organisation is
  removed !

. The A.I.M.O.S. SNMP Agent resets each alarm notification related counter to
  zero. These counters are aimosAlarmListID, aimosAlarmListAlarmEventID,
  aimosAlarmTrapID and each managers aimosAlarmTrapNotificationID. The values of
  these counters are increased by one with each new alarm, i.e. with the first
  alarms the value is 1. A counter of 0 is only possible after the maximum value
  (2^32-1) has been reached; which is, however, highly unlikely.

. The aimosAlarmListRebuildInitiated notification is forwarded to all SNMP
  Managers configured to receive this alarm. This will result in
  . one new alarm list entry per affected organisation
    (with aimosAlarmListID and aimosAlarmListAlarmEventID each set to 1) and
  . one trap list entry per affected manager
    (with aimosAlarmTrapNotificationID set to 1 and per SNMP Manager consecutive
    numbered values beginning with 1 in aimosAlarmTrapID)

. The A.I.M.O.S. devices are informed about the rebuild in order to reset its
  internal alarm tables, too. The devices will report still existing alarms as new
  alarms immediately.

. Suppress forwarding of further notifications to a specific manager until the
  manager acknowledges the aimosAlarmListRebuildInitiated notification. If the
  acknowledgement is missing for a specific period of time, the agent obviously
  emits the aimosAlarmListRebuildInitiated notification again

On receipt of the aimosAlarmListRebuildInitiated notification, the SNMP Manager
shall clean the internal alarm table prior to acknowledge this notification.

There is no aimosAlarmCleared notification for this alarm. The alarm gets cleared
on acknowledgement. Alarm notifications received after that acknowledgement needs
to get acknowledged by the manager as usual; the manager is neither required nor
able to distinguish if a notification is a result of the alarm list rebuild or a
new (never received before) one.

Changes, which are made here, affect all organizations.
That's why TelCo's are not allowed to initiate an Alarm List Rebuild Process
by setting this value to start(5).

What is aimosAlarmListRebuild?

Set to 'start(5)' to trigger full alarm rebuild (erases all alarm data). Emergency recovery operation. Example: Set to 'start(5)' after suspected data corruption.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6408.201.3.4.18
snmpwalk -v2c -c public <target> AIMOS::aimosAlarmListRebuild

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6408.201.3.4.18.1
snmpget -v2c -c public <target> AIMOS::aimosAlarmListRebuild.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.6408.201.3.4.18.1 s <value>

Start monitoring Andrew Wireless Systems DAS/repeater equipment with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AIMOS::aimosAlarmListRebuild OID value, configure state conditions and alerts, and monitor any Andrew Wireless Systems DAS/repeater equipment from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6408mikomAIMOS
1.3.6.1.4.1.6408.201aimosAIMOS
1.3.6.1.4.1.6408.201.3aimosObjectsAIMOS
1.3.6.1.4.1.6408.201.3.4aimosAlarmManagementAIMOS
1.3.6.1.4.1.6408.201.3.4.18aimosAlarmListRebuildAIMOS