User Manual

Table Of Contents
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2
7.9.2 Usage
Attribute type: Read only
Format:
<Number of alarm log entries>
where <Number of alarm log entries> is an integer indicating how many alarms are
currently in the alarm log.
Example:
GET LLN
Returns:
89
meaning that there are 89 alarms that can be read out from the alarm log, starting
with log item 1.
7.10 MAR – Minimum Alarm Repetition Cycle
7.10.1 Overview
This attribute defines minimum time that must elapse between two concurrent
alarms from the same alarm source.
7.10.2 Usage
Attribute type: Read and Write
If there is an alarm toggling between OK and ERROR, the controller will
continuously send alarms to the Axell Element Manager, with the new alarm
detected, and then directly end of alarm, causing the communications interface
between the controller and the AEM to be blocked for a long time. If lots of alarms
are received at the AEM, the operator must be able to send a message to disable
the particular alarm at the controller until service of the unit has been performed.
The Minimum Alarm Repetition Cycle takes care of this problemby defining a
minimum time between two consecutive alarms from the same alarm source.
Typically the MAR should be set to a minimum of two or three times the time it
takes for the controller to report the alarm to the OMC.
Format:
<Minimum Alarm Repetition>
<Minimum Alarm Repetion> is an integer representing number of minutes between
each alarm. Allowed interval is from 0 (disabling this functionality) to 99 minutes.
Example:
GET MAR
Reply:
3
meaning that the minimum time between two consecutive alarms is three minutes.
Example:
SET MAR 4
changes this interval to four minutes.
Common Commands and Attributes 29/123