Examples, Rmon event traps – Brocade 6910 Ethernet Access Switch MIB Reference User Manual

Page 98

Advertising
background image

86

Brocade 6910 Ethernet Access Switch MIB Reference

53-1002652-02

14

Examples

Examples

RMON event traps

The following is an example of how to generate an SNMP trap for an RMON event.

If you want to configure a device to send an SNMP trap when the number of broadcast packets
exceeds 100, do the following:

1. Configure an RMON alarm with an ID of 1 that checks etherStatsBroadcastPkts for Port 1 every

15 seconds to see if it exceeds a specified delta threshold (i.e., a change compared to the last
reading). In every sample, check if etherStatsBroadcastPkts exceeds 100 packets compared to
the last measurement. If it does, send an event (id 1) with “Tom” as the owner name. The event
trigger is re-armed, when the falling-threshold value falls below 30 packets since the last
reading.

Console(config)#rmon alarm 1 1.3.6.1.2.1.16.1.1.1.6.1 15 delta

rising-threshold 100 1 falling-threshold 80 1 owner Tom

The rising and the falling thresholds are used for the presence and absence of one specific
condition, with an oscillation buffer in between (e.g. warning versus no warning, not opposite
events like “too much” and “too little”), and should be near each other to be meaningful. The
data monitored may oscillate between these thresholds over time, triggering multiple events,
e.g. when using the settings of 100 and 80 as in the preceding example.

2. Configure an RMON event with an ID of 1, which sends an send a SNMP trap that contains the

community string “public”, some description, and owner Tom whenever broadcasts exceed
100 packets.

Console(config)#rmon event 1 trap public description broadcast_above_100 owner

Tom

Advertising