RuggedCom RS8000 Manuel D’Utilisation
RuggedSwitch
™ User Guide
Troubleshooting
Problem One
• What do I need to do in order get a trap when the frame rate on
port 1 exceeds 1000 fps?
We will start by assuming that the frames are unicasts, the rate is to be measured
in both directions and that the measurement period is 1 second.
1) Verify that an SNMP management station is configured and traps are enabled.
See Administration, Configure SNMP Management Stations for a station and
Administration, Configure IP Services for the correct community name.
Configure the management station with traps enabled.
2) Verify that an RMON Event record exists that has a type of either “snmpTrap”
or “logAndTrap” (See Ethernet Statistics, Configure RMON Event). Verify that
the community name matches that in step 1. The index of this event will be used
in the step 4. Create these records if they do not exist.
3) Determine the name of the MIB variable to be monitored. Type <CTRL> S to
enter the CLI shell. Enter the command “rmon” and press enter. Alternatively,
refer to Appendix D – RMON Acceptable MIB Parameters. The variables to use
in this case are ifInOctets and ifOutOctets.
4) Enter the RMON alarms menu (Ethernet Statistics, Configure RMON Alarms)
and insert the first RMON Alarm record by pressing <CTRL> I. Make the
following changes:
- Set the variable name to ifInOctets.1 (the .1 meaning “port 1”),
- Change the interval to 1 second,
- Set the rising threshold to 1000 (frames),
- Set the falling threshold to 1000 (frames),
- Set the RisingEvent field to that of step 2.
5) Insert another RMON Alarm record using the same values with the exception
that the variable name entered should be ifOutOctets.1.
Traps will now be issued. Note that a measurement period of 1 second can result
in generating 1 trap/second if the statistic crosses the threshold every second. In
the above case a RisingEvent trap but not FallingEvent trap was configured. This
will limit the trap generating rate to a maximum of 1 trap every two seconds. If
this rate is still unacceptably high then increase the measurement period (a period
of 60 seconds and a threshold of 60,000 frames will measure the same rate).
Finally, note that generating both transitions of an alarm (rising and falling)
provides for discovery of the event duration from the SNMP logs.
in both directions and that the measurement period is 1 second.
1) Verify that an SNMP management station is configured and traps are enabled.
See Administration, Configure SNMP Management Stations for a station and
Administration, Configure IP Services for the correct community name.
Configure the management station with traps enabled.
2) Verify that an RMON Event record exists that has a type of either “snmpTrap”
or “logAndTrap” (See Ethernet Statistics, Configure RMON Event). Verify that
the community name matches that in step 1. The index of this event will be used
in the step 4. Create these records if they do not exist.
3) Determine the name of the MIB variable to be monitored. Type <CTRL> S to
enter the CLI shell. Enter the command “rmon” and press enter. Alternatively,
refer to Appendix D – RMON Acceptable MIB Parameters. The variables to use
in this case are ifInOctets and ifOutOctets.
4) Enter the RMON alarms menu (Ethernet Statistics, Configure RMON Alarms)
and insert the first RMON Alarm record by pressing <CTRL> I. Make the
following changes:
- Set the variable name to ifInOctets.1 (the .1 meaning “port 1”),
- Change the interval to 1 second,
- Set the rising threshold to 1000 (frames),
- Set the falling threshold to 1000 (frames),
- Set the RisingEvent field to that of step 2.
5) Insert another RMON Alarm record using the same values with the exception
that the variable name entered should be ifOutOctets.1.
Traps will now be issued. Note that a measurement period of 1 second can result
in generating 1 trap/second if the statistic crosses the threshold every second. In
the above case a RisingEvent trap but not FallingEvent trap was configured. This
will limit the trap generating rate to a maximum of 1 trap every two seconds. If
this rate is still unacceptably high then increase the measurement period (a period
of 60 seconds and a threshold of 60,000 frames will measure the same rate).
Finally, note that generating both transitions of an alarm (rising and falling)
provides for discovery of the event duration from the SNMP logs.
RuggedCom