Enabling individual alarms
Individual alarms are individual, trigger-based network alarms. Before these alarms can prove useful, they must be enabled. There are four basic types of alarms in Observer:
Predefined Alarms–These are alarms created by VIAVI and includes alarms for packet size, checksum, Bit Torrent, duplicate IP addresses, microbursts, VoIP, and more.
Trading Multicast Dropped Sequence Alarms–These alarms must be wholly created and configured by you because it requires specific details about your trading and network environment. There are several pre-defined trading multicast protocols that you can import for the alarm.
IPTV Alarms–These alarms must be wholly created and configured by you because it requires specific details about your multicast stream and device environment.
Filter Based Alarms–These alarms based on packet capture filters that exist in Observer.
Note: You cannot set an alarm for excessive retransmissions or high latency, nor can either be custom created. Instead, you can see these events (if they occur) using Expert Analysis. See .
Enable individual alarms by completing the following steps:
1. Click the Alarms Settings button, near the bottommost portion of Observer’s window. The Alarm Settings window appears.
2. Click a probe instance to highlight it.
3. Click the Selected Instance Alarm Settings button. The Probe Alarms Settings window appears.
 
Figure 42: Enable individual alarms here
 
4. Enable each alarm you want to enable.
Until you customize the alarms, Observer uses the built-in, default triggers and actions for each. If necessary, see these pages:
5. Select “Enable Probe SNMP trap generation” and configure up to 10 Observer or other network management systems (for instance, HPOpenView or IBM Tivoli) to receive the SNMP traps. By enabling SNMP trap generation here, an SNMP trap is generated even when no Observer are connected to the probe.
6. Click OK to save your changes.
 
You successfully enabled individual alarms. Remember, individual alarms remain disabled if the probe instance alarm they are associated with is disabled—even if the individual alarms are enabled.