Quantum scalar 100 User Guide

Events are recorded in the SNC event log. For each event, an assigned Viewing Level 
corresponds with the event log facility available to the Client application (all events are 
recorded in the SNC log regardless of the assigned level).

A Trap Threshold is preset for each event so that when the number of instances of that 
event reaches the threshold, a trap will be sent. The count is then reset. If the threshold is 
0, no traps are sent. If the threshold is 1, a single occurrence of the event will generate a 
Trap. If the threshold is set to 2, it will take two occurrences of the event in order for a 
Trap to be generated. When a trap is received by the Server, it attempts to notify all 
registered Clients (that is, Clients that are actively monitoring the SNC that issued the 

Trap). When the Client receives a trap message, the symbol

 is displayed on the 

status/message area at the bottom of the ADIC Management Console screen. This is an 
indication that a trap has been received and a message has been written to the Event Trap 
window. Figure 3-74 is an example of event trap messages in the Event Trap window.    

The IP address of the SNC, a date/timestamp (provided by the server) the Event Code and 
a brief description of the event are displayed. You can double click on an event in the 
window to display more detailed information.

This information helps locate potential problems and should be monitored regularly. It is 
also stored in the SNC event log.

The communication paths between the three components described in “Client/Server 
Model” on page 17 are checked periodically to make sure that each is listening to the 
other. These checks define “heartbeats.”