# Go back one pageGo to the next page#Go to this book's Index

Example Alarm

Note Note: The example alarm described here will generate at least one alarm every five minutes. The example is intended only to demonstrate how alarms fire; it is not a useful alarm. Because of the high frequency, you may want to delete this alarm in a real world scenario.

To create an alarm using default values and to receive statistics and history:

  1. Make sure that RMON is globally enabled.

When you enable RMON globally, you also create a default rising and falling event. The default for the events is log-and-trap, meaning you will receive notification through a trap as well as through a log file.

  1. From the Device Manager menu bar, choose RMON > Alarm Manager.
  2. In the Variable field, select a variable for the alarm and a port (or other ID) on which you want to set an alarm.

Alarm variables are in three formats, depending on the type:

REVIEWERS: THESE ARE NOT VALID??

· A chassis, power supply, or fan-related alarm ends in .x where the x index is hard-coded. No further information is required.

· A card, spanning tree group (STG), RIP or OSPF, or EtherStat alarm ends with a dot (.). A card number, STG ID, IP address, or EtherStat information must be entered.

· A port alarm ends with no dot or index and requires using the port shortcut menu (step 6 on "For a port alarm, select the port on which you have created an alarm from the graphical image of the switch and click it with the right mouse button."). An example of a port alarm would be ifInOctets (interface incoming octet count).

  1. For this example, select a rising value of 4 and a falling value of 0.
  2. Leave the remaining fields at their default values, including a sample type of Delta, and click Insert. (If you want to make field changes, see the field descriptions shown in the table below.)


Item Description
Variable
Name and type of alarm--indicated by the format:
  • alarmname.x, where x=0 indicates a chassis alarm, x=1 or 2 indicates a power supply or fan alarm with 1 being the primary unit and 2 the secondary unit.
  • alarmname, where the user must specify the index. This value is a card number for module-related alarms, an STG ID for spanning tree group alarms (the default STG is 1; other STG IDs are user configured), an IP address for RIP or OSPF alarms (RIP/OSPF must be enabled on the VLAN or router port and enabled globally), or the Ether Statistics Control Index for RMON Stats alarms.
  • alarmname with no dot or index is a port-related alarm and results in display of the port picker tool.
Sample Type
Can be either absolute or delta. For more information about sample types, refer to Creating Alarms.
Sample Interval
Time period (in seconds) over which the data is sampled and compared with the rising and falling thresholds.
Index
Uniquely identifies an entry in the alarm table. Each such entry defines a diagnostic sample at a particular interval for an object on the device.

The table below describes the items under Rising Value


Item Description
Value
When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, generates a single event.
Event Index
Index of the event entry that is used when a rising threshold is crossed. The event entry identified by a particular value of this index is the same as identified by the same value of the event index object. (Generally, accept the default that is already filled in.)
Severity
Only used when creating a script. The severity level is passed to the script associated with the alarm as the only command line argument.
Script
Insert a name for your script. For more information about scripts, refer to "Creating Scripts for Alarms".

The table below describes the items under Falling Value.


Item Description
Value
When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, generates a single event.
Event Index
Index of the event entry that is used when a falling threshold is crossed. The event entry identified by a particular value of this index is the same as identified by the same value of the event index object. (Generally, accept the default that is already filled in.)
Severity
Only used when creating a script. The severity level is passed to the script associated with the alarm as the only command line argument.
Script
Insert a name for your script. For more information about scripts, refer to "Creating Scripts for Alarms".

  1. For a port alarm, select the port on which you have created an alarm from the graphical image of the switch and click it with the right mouse button.

The port shortcut menu is displayed.

  1. Choose Enable RMON Stats and Enable RMON History. You can also enable RMON History and RMON Stats on all ports by selecting the Actions menu from the Device Manager menu bar.
  2. If trapping is not enabled, enable trapping.

From the menu bar, choose Edit > Chassis > Trap Receivers.

Two trap versions are available: Version 1 (v1c) and Version 2 (v2c). In general, select Version 2 trapping. If you are using HP OpenView or other network managers that are RMON management applications, select Version 1.

  1. To view RMON statistics and history, select the port on which you have created an alarm and click the graph icon from the toolbar.

Click the RMON window to view statistics, and click the RMON History window to view the history.

  1. View the trap log and the events log.

To view the trap log, click the bell icon from the toolbar.

To view the events log, choose RMON > Alarm and click the Log tab. The log dialog box opens.


Go back one pageGo to the next page##Go to this book's Index