Escolar Documentos
Profissional Documentos
Cultura Documentos
Alarms
1) Performance alarms collection (identification and procedure to collect the alarms)
4) action to be taken for alarms reduction(methodology and procedure for alarm reduction)
6) important KPI can be affected by alarms(impact of various alarms on various KPI and other
performance parameters)
7) different report can help for analyzing the performance(daily performance logs to be collected i.e.
G.826 performance report for all MW links)
As discussed in the Bharti Operational meeting held in Gurgaon me, Rishi and Gagan Bhashin will be
conducting this workshop in Patna and Kolkata.
Alarm groups and numbers
The Alarm Reference documentation consists of alarm printouts and diagnosis reports. The alarms have been divided into four groups, and each of
them is described in a dedicated piece of documentation.
The alarms are numbered in ascending order as follows:
Table: Alarm groups and numbers
diagnosis 3700–3999
report number
power 5000–5499
equipment
external 5500–5999
equipment
Structure of the BSC alarm
g.Urgency level
*** requires immediate actions ** requires actions during normal working hours * normally no actions required
Unknown urgency level is printed as a question mark (?).
The urgency level is output in all alarm printouts except notices (NOTICE). The urgency levels of terminated alarms are indicated by dots (.)
instead of asterisks (*).
a.Printout type
b.Alarm object
c.Alarm issuer
The program block issuing the alarm. If the name of the program block issuing the alarm is not available, the family identifier of the program
block is output in hexadecimal form instead of the name.
If the alarm is set in a preprocessor plug-in unit, the plug-in unit name and index are output in this field (for example PCU_S-1). In this case, the
alarm concerns the functioning of the plug-in unit in question.
Cont…..
13)Recovery information
When recovery is informed of the alarm in order to start the automatic recovery actions, this field displays *RECOV*.
14)Processing information
If the alarm is set before the start-up of the distributed part of the alarm system, this field displays LIB. Note that this kind of alarm does not stay as an active alarm
and thus there will be no cancel printout for it.
15)Consecutive number
Failure printouts (***, **, *) are numbered in ascending order. With the help of the number the operating personnel can follow the update and cancel printouts of the
original failure printout.
16)Alarm number
Alarm number is an unambiguous identifier for an alarm. It is also a search index for the description of the alarm.
17)Alarm text
Alarm text is a short description of the alarm.
19)Supplementary text
A more detailed text printed out in some alarms.
c.BCF number
d.BTS number
e.Event type
f.Date
g.Time
h.Urgency level
*** requires immediate actions ** requires actions during working hours * no actions required
The urgency level is output in all alarm printouts except notices (NOTICE). The urgency levels of terminated alarms are indicated by dots (.) instead of asterisks (*).
•Printout type
ALARM fault situation CANCEL fault terminated DISTUR disturbance NOTICE notice
c.TRX number
16)Text
The text is a short description of the alarm.
In the case of alarms number range 7600...7699 this field indicates the fault reason.
A maximum of 16 fields which are separated from one another by one or several spaces.
Reasons for Alarm triggering
• Tramsmission Problem
– Cable/Connector
– Mux
– M/W ODU/IDU
– M/W fading/interference
– Configuration problem
• Hardware problem at BTS.
• VSWR/loose cables at BTS.
• Configuration Problem in BSC.
• Hardware Problem at BSC.
• Configuration Problem in BTS.
• Equipment failure(BSC/BTS)
• Environmental failure(High Temp)
• Configuration Problem in MSC.
• Configuration Problem in SGSN.
• Wrong RF parameters.
How to get the Alarms in the
network
• GNSC is sending a list of active alarms in the
network daily.
• GNSC is preparing a daily report for alarm
history of the circles and store it at the given
locations. Report can be collected from there.
Explanation
LOGICAL FILE
SWITCH2 Switching equipment alarms whose type is notice, disturbance, or one-star alarm
TRANSM2 Transmission equipment alarms whose type is notice, disturbance, or one-star alarm
POWER2 Power equipment alarms whose type is notice, disturbance, or one-star alarm
OPERMA2 Operation and maintenance alarms whose type is notice, disturbance, or one-star
alarm
Each alarm event, alarm and its cancellation, not filtered by the alarm system, is saved in a log file. This log data is called alarm history. Using the AH command
group commands, you can display the history data concerning the system's alarm situation. For further information on displaying alarm history, refer to Alarm
History Handling (AH ) for DX 200 alarms, and Base Transceiver Station Alarms Handling (EO ) for BTS alarms.
You can either display the alarm history, or merely the active alarms, on the selected output device.
The printout format is the same as in alarm printouts.
It is recommended that you print out the active alarms every day. Check if they require maintenance actions.
A DX 200 alarm whose object unit is not in the normal working state is normally filtered by the alarm system. When the alarm is filtered (by any means), it is
neither printed out nor stored in the alarm history. However, an alarm that is filtered purely on the basis of the state of its object unit is printed out when
displaying active alarms.
You can print out active DX 200 alarms with the command AHO , and active BTS alarms with the command EOL .
You can display the DX 200 alarm history data with the command AHP , and the BTS alarm history data with the command EOH .