Alarm System - Alcatel-Lucent Security Management Server (SMS) Release 9.4 Technical Overview

Alcatel-Lucent Security Management Server (SMS)

Alarm System

...................................................................................................................................................................................................................................
Overview
The SMS generates alarms based on Brick device log messages, as well as locally
generated log messages from the various SMS subsystems. Alarms consist of two parts:
triggers and actions. Alarms are configured per-administrator, so each system
administrator may configure the alarms in which they are interested, and be notified by
methods appropriate to the administrator, as well as the specific alarm.
The SMS provides a number of preconfigured alarms, to allow fast initial deployment.
Triggers
Triggers cause the alarm to be fired. Triggers contain the criteria matching information,
thresholding information, applicable devices or subsystems, etc. Each trigger must be
mapped to one or more action.
Some of the configurable trigger types are as follows:
• Application Process Hung
• SMS Error
• Brick Error
• Brick Lost/Found
• Brick Interface Up/Down
• Proactive Monitoring Threshold Crossing
• Brick Redundancy Alarms
• SMS Redundancy Alarms
• Brick SLA Round Trip Delay Alarms
• QoS Bandwidth Alarms
• Alarm Code
• VPN Proactive Monitoring
• User Authentication
• Unauthorized SMS login attempts
• LAN-LAN tunnel lost/up
• Brick ICM Alarm
Actions
Actions allow each trigger to cause some response to be taken by the SMS. These
actions all center around notifying the administrator. Actions are customizable so as to
send to each administrator in the most convenient notification mechanism for that
particular administrator.
...................................................................................................................................................................................................................................
2-12
260-100-022R9.4
Issue 1, June 2009