Using eventTable to Log Alarms
To use eventTable to log alarms, perform the following tasks:
Creating an Event Entry
The RMON eventTable controls the generation of notifications from the router. Notifications can be logs (entries to logTable and syslogs) or SNMP traps. Each event entry can be configured to generate any combination of these notifications (or no notification). When an event specifies that an SNMP trap is to be generated, the trap group that is used when sending the trap is specified by the value of the associated eventCommunity object. Consequently, the community in the trap message will match the value specified by eventCommunity. If nothing is configured for eventCommunity, a trap is sent using each trap group that has the rmon-alarm category configured.
Configuring the MIB Objects
Once you have created the new row in eventTable, set the following objects:
 | Note: The eventType object is required. All other objects are optional. |
eventType
The type of notification that the router generates when the event is triggered.
This object can be set to the following values:
- log—Adds the event entry to logTable.
- log-and-trap—Sends an SNMP trap and creates a log entry.
- none—Sends no notification.
- snmptrap—Sends an SNMP trap.
For example, to set eventType for event #1 to log-and-trap, use the following SNMP Set request:
snmpset -Os -v2c router community eventType.1 i log-and-trap
eventCommunity
The trap group that is used when generating a trap (if eventType is configured to send traps). If that trap group has the rmon-alarm trap category configured, a trap is sent to all the targets configured for that trap group. The community string in the trap matches the name of the trap group (and hence, the value of eventCommunity). If nothing is configured, traps are sent to each group with the rmon-alarm category set. For example, to set eventCommunity for event #1 to boy-elroy, use the following SNMP Set request:
snmpset -Os -v2c router community eventCommunity.1 s "boy-elroy"
| Note: The eventCommunity object is optional. If you do not set this object, then the field is left blank. |
eventOwner
Any text string specified by the creating management application or the command-line interface (CLI). Typically, it is used to identify a network manager (or application) and can be used for fine access control between participating management applications.
For example, to set eventOwner for event #1 to george jetson, use the following SNMP Set request:
snmpset -Os -v2c router community eventOwner.1 s "george jetson"
| Note: The eventOwner object is optional. If you do not set this object, then the field is left blank. |
eventDescription
Any text string specified by the creating management application or the command-line interface (CLI). The use of this string is application dependent.
For example, to set eventDescription for event #1 to spacelys sprockets, use the following SNMP Set request:
snmpset -Os -v2c router community eventDescription.1 s "spacelys sprockets"
| Note: The eventDescription object is optional. If you do not set this object, then the field is left blank. |
Activating a New Row in eventTable
To activate the new row in eventTable, set eventStatus to valid using an SNMP Set request such as:
snmpset -Os -v2c router community eventStatus.1 i valid
Deactivating a Row in eventTable
To deactivate a row in eventTable, set eventStatus to invalid using an SNMP Set request such as:
snmpset -Os -v2c router community eventStatus.1 i invalid
