Filter
Top Products
B. SNMP MIBs, Traps, and RMON Alarm Defaults
B-14 December 2002 9700-A2-GB20-20
RMON Alarm and Event Defaults
The FrameSaver unit supports automatic generation of RMON alarm and event
information. Each alarm sets an SNMP variable to monitor. Thresholds are set
using the OpenLane SLM System. When the threshold set for the monitored
variable is exceeded, an SNMP trap is sent or an event is logged.
Event Defaults
Since all events sent are under the control of the FrameSaver unit, there is no
need to define multiple events for each alarm type, so only the following two events
need to be generated:
The following alarm default tables show how each RMON default alarm is set by
the FrameSaver unit, alarm and event types, interval used when generating
alarms, and alarm thresholds.
Table B-9, Network Physical Interface Alarm Defaults
Table B-10, Frame Relay Link Alarm Defaults
Table B-11, DLCI Alarm Defaults
See
Standards Compliance for SNMP Traps
on page B-6 for information about
how traps work, and
Trap: RMON-Specific
on page B-13 for traps specific to
remote monitoring.
Rising Event Operation
If a rising threshold is crossed during the interval shown in a table (e.g., frames
dropped by the network), the event is armed and an alarm is generated at the end
of the interval. Only one alarm per event per interval is generated. The alarm
condition persists until the event has been disarmed (reset).
The event is disarmed when a falling threshold has been crossed and the rising
threshold has not been crossed during an interval, allowing the event to return to
its original disarmed state.
eventIndex eventDescription eventType
1 Default SLV Rising Event log-and-trap(4)
2 Default SLV Falling Event log-and-trap(4)