User`s guide

Alarms and Traps

Setting Alarms

444 5967–9446

Alarms and Packet Capture Instances

Alarms work with Protocol Analyzer packet capture instances in two

ways:

● You can set the monitored object to be a packet capture instance,

triggering an alarm when some number of packets are captured or

when the number of packets captured in a time interval reaches the

indicated level.

● You can start or stop a packet capture in response to an alarm trigger

or rearm event.

In either case, the packet capture instance must already exist on the

agent. That is, you must create and conﬁgure the instance, then start or

arm it. Until the instance is actually started or armed, it does not exist

on the agent.

For information about packet capture instances, refer to the Protocol

Analyzer chapter, which begins on page 339.

Two examples of alarms with packet captures are given below.

Examples

The following pages give several examples of alarms using advanced

options to control what happens when the alarm triggers and rearms.

Example 1 The following example conﬁgures an alarm based on Station Count, that

is, the number of hosts on the network (as seen by the agent).

The alarm triggers when the data source detects a new host on the net-

work. It also sends a trap to notify you when the alarm triggers. You’ve

already deﬁned a trap destination group, called “admin,” that includes

your OpenView NNM management station.

To conﬁgure this alarm, follow these steps:

1 Open the Alarms application for the data source, and conﬁgure the

basics of a new alarm: description, monitored object of

Administrative➤Station Count, and threshold of 1 unit delta for 10

seconds. Set the trap destination group to admin, which was deﬁned

earlier.