Telenium Fault Management

Advanced Logic Processor enables the designing of logic procedures (ALPs) that trigger based on any combination of events, including detection of alarms, changes to database fields, expiration of timers and ON/OFF indicators. Activation of the ALP can generate alarms, modify database fields, execute scripts or perform complex correlations.

Alarm Chrono displays current alarm lists and alarm information for all equipment in the network, and can be used to acknowledge, enable, disable, and sort alarms for enhanced system monitoring. Alarm comments can also be added to alarms to help field technicians communicate with operators.

Uses presentation views, charts and 3d rotations to provide a categorized count and graphical screen of active alarms.

The Alarm History application allows you to view the local Alarm History stored in your database. The number of history entries stored in the logs at the Network Element and Global level is determined from the tunable parameter found in the $NODE record. Site and Group levels show history for all Network Elements within them (to the entry limit for each NE). Global (Node) history is limited by the maximum limit as determined in the tunable parameters.

Telenium allows associated alarms to be organized into incidents for better tracking and control of alarm events. Once created, these incidents are available in other applicable Telenium applications.

Alarms are displayed graphically within seconds of being received from the network element. Network fault management alarm data consists of conditions reported by the field equipment. All alarm event details, including the original message received from the element, can be archived for post analysis.

Telenium AORs allow correlation of alarms based on user-defined parameters such as geographic location, network element type, alarm severity, alarm impact, and many other combinations of criteria.

Policy Manager gives you extensive control over every alarm, event and analog handled by the Telenium system. Policies can be created to affect a myriad of characteristics including setting alarms to one of 99 different priorities, enforcing analog threshold limit checking and modifying alarm descriptions to improve readability.

The Telenium system monitors itself and raises alarms when disk or other system faults occur (such as disk or memory capacities reaching dangerously low conditions, applications consuming excess CPU time, or applications failing unexpectedly). All Telenium system applications are monitored and automatically restarted if a failure occurs.