RMON events and alarms are a useful tool for monitoring internal system status such asCPU utilization.
RMON has some advantages over external snmp monitoring in that the polling is less impacting on the systems tasks and can also generate/report alarms even if the external monitoring device is not reachable.
There are two steps to create the RMONalarm. First we define the alarm and then define with an RMONevent what happens when the alarm is triggered.
For example, in this case we will configure an RMON alarm to trigger when linecard CPUutilization on linecard 1 of an RX rises above 50%. We will configure the RMON event to send a snmp trap and RMON log when this trigger happens:
telnet@1323803_hashim_Jun11_MLXe-8_MLX2(config)#rmon alarm 1 snAgentCpuUtilPercent.1.1.5 1 absolute rising-threshold 50 1 owner test
telnet@1323803_hashim_Jun11_MLXe-8_MLX2(config)# rmon event 1 description "linecard-cpumon" log-and-trap "private" owner test
NOTE:This object is deprecated for FastIron GS, and FastIron SX devices and it is not supported on the
Brocade NetIron MLX, Brocade MLXe, Brocade NetIron XMR, Brocade NetIron CES, and Brocade NetIron CER series devices. Use the
snAgentCpuUtilPercent and snAgentCpuUtil100thPercent objects for these devices.
NOTE:Execute cpu-usage oncommand in the config mode, if MP CPU utilization is needed on the Brocade NetIron devices.
This object is supported on the Brocade NetIron MLX, Brocade MLXe, Brocade NetIron XMR,
FastIron GS, and FastIron SX devices