All MIBs › AIMOS › aimosAlarmListResync
aimosAlarmListResync
Module: AIMOS
OID (symbolic): AIMOS::aimosAlarmListResync
OID (numeric): 1.3.6.1.4.1.6408.201.3.4.19
Node type: OBJECT-TYPE
Type: OperationMode
Access: read-write
Description: This object of type OperationMode is provided to give each SNMP Manager the ability to synchronise its alarm table. Setting this value to start(5) will start the alarm list synchronisation process. If the current SNMP Manager has more than one IP address or if his phonebook entry is 127.0.0.1, the SNMP Agent cannot determine for which phonebook entry the Alarm List Resync is to be done. In such a case - either aimosPhoneBookAlarmListResync must be used - or the aimosLoginPhoneBookID should be set manually (recommended) in order to start the Alarm List Resync Process. The Alarm List Resync process ============================= When an employee discovers that the internal alarm table of the SNMP Manager is flawed, a resynchronisation of the alarm list can be initiated, which is e.g. the case when the trap count (aimosAlarmTrapNotificationID), which is continuous for each SNMP Manager, is interrupted. Each SNMP Manager receiving alarms is allowed to start a synchronisation of the alarm list. In order to do that the SNMP Manager shall first clean the internal alarm table and then request for an alarm list rebuild by setting aimosAlarmListResync to start(5). This request does not cause the agent to send a notification like the alarm list rebuild process will do, but the A.I.M.O.S. SNMP Agent will perform the following steps: . Set the value of aimosAlarmListResync to running(3) . It resets the managers aimosAlarmTrapNotificationID to zero . All alarms in the alarm list related to the specific manager will be emit with unchanged aimosAlarmListID, aimosAlarmListAlarmEventID and aimosAlarmTrapID values. The aimosAlarmTrapNotificationID is a new generated consecutive numbered value. The agent doesn't wait for acknowledgement before emitting the next notification. . If the last notification is sent to the manager, aimosAlarmListResync is set to idle(0) The manager is required to acknowledge all notifications as usual. An alarm list synchronisation neither effect the contents from the A.I.M.O.S. SNMP Agent's nor from other SNMP Manager's alarm lists except of the affected SNMP Manager's notification ID.
What is aimosAlarmListResync?
Set to 'start(5)' to sync alarm table with specific SNMP manager. State synchronization. Example: Set to 'start(5)' for manager recovery.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6408.201.3.4.19 snmpwalk -v2c -c public <target> AIMOS::aimosAlarmListResync
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.6408.201.3.4.19.1 snmpget -v2c -c public <target> AIMOS::aimosAlarmListResync.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.6408.201.3.4.19.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::aimosAlarmListResync 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.6408 | mikom | AIMOS |
| 1.3.6.1.4.1.6408.201 | aimos | AIMOS |
| 1.3.6.1.4.1.6408.201.3 | aimosObjects | AIMOS |
| 1.3.6.1.4.1.6408.201.3.4 | aimosAlarmManagement | AIMOS |
| 1.3.6.1.4.1.6408.201.3.4.19 | aimosAlarmListResync | AIMOS |