Register an Event

After you have defined an event or selected a predefined event, you can initiate event-checking and notification by registering the event. When you define an event, you specify a measurement variable in a condition you want to check. Then, when you register the event, you cite the particular link, partition, or class that should be checked for the threshold condition, as well as the specific threshold value. Up to 32 events can be registered at one time.

When you register an event, you specify the following values:

• The name of the event's object (the path to the link, partition, or class)
• Alarm threshold — the value that triggers event notification
• Re-arm level — the value that tells PacketWise that it's okay to once again send notification.
• Notification type (email, SNMP trap, and/or Syslog)
• Interval for event checking, if other than the default for the measurement variable
• Maximum number of event notifications in a day

To register a user-defined or predefined event:

1. Access the CLI.

2. Type event register and press Enter. A list of available events appears.

3. Referring to the list on the screen, enter the name of the event to be registered. (You don't need to type the entire name — just type enough to make it unique.)

4. Enter the path to the object you are testing. For example, if you are testing a link, type outbound or inbound. If you are testing a class or partition, type the path to the traffic class (such as /Inbound/HTTP).

5. Enter a value for the alarm threshold.

6. Enter a re-arm value.

Notes:

• The event-registration process requires that you set a re-arm level to prevent over-notification of a condition. Fluctuating network activity could cause multiple occurrences of the same event, and you usually do not want to be alerted each and every time. For example, you could configure an event to notify you when your web server's tcp-conn-aborts% exceeds 70%. This condition could occur many times within a short time frame, but all of these occurrences signal only one event. In this example, you might set the re-arm value to 60% to tell PacketWise to "notify me after the aborts drop back down to a normal level, and crosses the threshold again." The re-arm level clears the condition so that you'll only be notified of truly new events.
  
• PacketShaper sends a notification when the re-arm value is crossed, allowing you to be alerted automatically when the event has been cleared.

7. Press Enter to specify the default checking interval, or type a different value.

Valid values are 1m or 1h (for PacketShaper ISP, 1m or 4h).

8. Indicate whether you want an email sent when an event occurs: type y for yes or n for no.

Note: This feature requires that the system is configured for email notification. See Set Up Email Notification.

9. Indicate whether you want an SNMP trap sent when an event occurs: type y for yes or n for no.

Note: This feature requires that you have defined the SNMP trap destination. See Configure PacketWise for SNMP Support.

10. Indicate whether you want to send an event message to the Syslog server: type y for yes or n for no.

Note: This feature requires that you have defined a Syslog server. See Set Up Syslog.

11. Specify the maximum number of event notifications to be sent in a 24-hour period.

Note: If the daily limit of event notifications is reached, you will not be notified of the events, and the events will not be recorded into the log file.

After the last prompt, you are provided with an event registration identifier. For example:

Event registration id: 1

You can use this number later if you want to unregister the event.

When an event exceeds the predefined threshold value, the event is in violation and the PacketShaper will automatically send out notification. PacketShaper will also send a notification when the re-arm value is crossed, allowing you to be alerted automatically when the event has been cleared.

To display a list of your registered events and determine which are compliant, disarmed, or in violation, see View Event Status.