ELTEX MA4000-PX, Руководство по эксплуатации и обслуживанию

Страница: 146 / 181

146 User Manual, Part V
Subscriber access/aggregation node МA4000-РХ
39 ACTIVE ALARMS LOG
39.1 Introduction
The system of logging is built on a central application systemdb, which organizes interfaces to
events database (DB). All emerging events both from interface boards and PP4X switch itself are sent
into systemdb to be saved in the base.
All events are divided into 2 types: one-time and state changing events. One-time events are
saved in the base and generate SNMP trap, if necessary. State changing events imply the following: if
the state has changed (e.g., Link Flapping has been found on interface) and this state is normalized, then
we will get a new event indicating situation improvement. State changing events, if they are alarms, are
to be added into a list of active alarms during registration in the base. If situation gets corrected the
alarm will be removed from active alarms.
39.2 Alarm Generation and Registration
An event can get into the system of logging by two methods: it can be generated at PP4X itself, or
on one of interface boards in MA4000 basket. All codes of events in the basket are entered into a
common list for convenience to promptly get SNMP OID code for any event.
39.2.1 Structure of Alarm/Event

Alarm code – code of alarm MA4000, an integer value which can range from 1000 to
7000. PP4X uses a range from 1,000 to 3,000.

Time – time of occurrence of alarm of this type. The figure is given in seconds from the
beginning of epoch.

Priority – alarm rate. An integer value from 0 to 3.

Text – a text field with description that can hold up to 255 symbols. The name of alarm as
well as auxiliary parameters are always preserved in Text field.

Params – array of 4 integers specific for every particular alarm or notification.
The Active field will indicate, whether this particular alarm is currently active. The alarm will be
active from the time of arriving of the first alarm of this type until arrival of an event for its
normalization. E.g.: the state will always be Active for ALARM_LINK_CHANGED after dropping the port
unless ALARM_LINK_CHANGED event arrives indicating that the port has recovered again.

Time field – time of occurrence of the event.
39.2.2 Alarm rates

Critical – Critical, level 0. Basket operation functionality disturbed.

Major – High, level 1. Basket separate modules affected.

Minor – Low, level 2. Non-critical comments in separate modules.

Notify – Notification, level 3. Not considered as alarm, it informs on the event that
happened.