Remote Network Monitoring (RMON)
Page 14-4
The Alarm probe attempts to prevent a flood of alarms from being generated by fluctuating
values. It does so by continuously comparing the upper and lower limits. What this means is
that the first time either an upper or lower limit is exceeded, an alarm will be generated.
However, if the variable moves back inside the limit, then out again, another alarm will not
be generated unless the opposite limit is exceeded. For example, consider a situation where
an upper limit of 75 and a lower limit of 25 is set. The variable goes to 76. An alarm is gener-
ated. If it drops to 74 then goes back up to 76, no alarm will be generated. Only when the
variable drops below 25 will another alarm be generated. If it goes back up to 76 then
another alarm will be generated, etc. This procedure prevents a flood of alarms from being
generated if the value fluctuates between 74 and 76.

Monitoring Probes

The probes command is used to monitor, activate, and inactivate existing probes (remember,
you cannot create probes in the switch’s UI). You can do three things with the command:
1. View all the current probes.
2. View a specific probe.
3. Activate or inactivate a History or Alarm Probe. (You can only do this with the “admin”
login.)
The probes command has three optional parameters. The format is:
probes [active | inactive] [n]
where:
active - activates an existing probe
inactive - inactivates an existing probe
n - is the entry number of the probe to view
If you enter the probes command without parameters, it displays all the current probes.
RMON Probe Summary
Entry Slot/Port Flavor Status Time System Resources
1 2/ 1 Ethernet Active 0 hrs 39 mins 312 bytes
2 2/ 1 History Active 0 hrs 4 mins 3656 bytes
3 2/ 1 Alarm Active 0 hrs 0 mins 1336 bytes
Entry
The entry number in the list of probes (1-16).
Slot/Port
The slot port number (interface) that this probe is monitoring.
Flavor
Ethernet, History, or Alarm.
Status
Creating, Active, or Inactive.