Alarms And Events - Symmetricom SSU-2000e User Manual

When the Communications module is installed, it performs an initial software
verification test to verify operation. If the module is being installed in the SSU-2000e
with power already applied and with other modules installed, the Communications
module reads the configuration of the modules in the SSU-2000e and the modules
in all installed SDU-2000e expansion shelves. This information is saved in
nonvolatile memory on the Communications module. If power is applied to the
SSU-2000e after the Communications module is installed, it initializes before any of
the other modules and provides configuration information to the individual modules.
Note: The clock modules also store configuration information and
can download this information to the various modules, if the
Communications module is not installed in the system.

Alarms and Events

The SSU-2000e has extensive event detection, reporting, and alarm generation and
storage capabilities that permit monitoring of the system from external sites.
Alarms are conditions within the unit or at the interfaces of the unit which may
indicate abnormal operation or a change in the unit's operational status. For
example, an alarm may be generated when a parameter exceeds a user-settable
threshold. Most alarms can be assigned by the user to one of the following modes:
IGNORE, REPORT, MINOR, MAJOR, or CRITICAL.
All Alarms detected in the SSU-2000e system are reported by three methods,
including:
Display on the module LEDs
Relay contact closures on the back of the SSU-2000e chassis
Messages transmitted on all communications ports
All Alarm indications clear when the condition(s) that caused them no longer exist.
In a case where a module in alarm is unplugged from the system, the ICS command
CONFIG xAy REMOVE clears the module's active alarms. In addition, normal
operating status is indicated by green LEDs on the modules.
Events are conditions within the unit, or at the interfaces of the unit, which may
indicate abnormal operation or a change in the unit's operational status. Recurring
events may be escalated to alarm status and may require action by the user.
Conversely, alarms may be de-escalated and corrected automatically. See the
SSU-2000e Technical Reference for details.
Although every alarm is considered to be an event, not every event is an alarm. For
example, a login is recorded as an event but is not considered to be an alarm. In
this case, no action is required by the user.
12713140-002-2 Revision E – October 2006
Chapter 1 Product Overview
System Architecture
SSU-2000e User's Guide 29