Alarm Messages
242
SSU-2000 User’s Guide
12713020-002-2 Revision D – April 2004
Alarm Messages
After the Communications module is installed and functioning properly, it monitors
the SSU-2000 and logs events into non-volatile memory, where you can inspect it at
a later date. 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.
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.
The following sections list all alarm and event messages by their designated
numbers, a description of each, and any corrective action to clear the alarm or
condition, if necessary.
Figure A-1
shows the structure of a typical Alarm message.
Figure A-1.
Alarm and Event Message Structure
With the exception of loss of power alarms (on main chassis and expansion unit) all
alarms are module alarms.
lists each module with corresponding alarm
descriptions, alarm levels, status messages, and corrective action. Since a “no fault”
alarm requires no action, the “Description/Corrective Action” category applies only to
fault messages requiring user intervention.
Summary of Contents for SDU-2000
Page 12: ...12 SSU 2000 User s Guide 12713020 002 2 Revision D April 2004 ...
Page 18: ...18 SSU 2000 User s Guide 12713020 002 2 Revision D April 2004 ...
Page 390: ...SNMP Protocol 390 SSU 2000 User s Guide 12713020 002 2 Revision D April 2004 ...
Page 420: ...I O Connector Grounding 420 SSU 2000 User s Guide 12713020 002 2 Revision D April 2004 ...