Professional Documents
Culture Documents
1) Performance alarms collection (identification and procedure to collect the alarms) 2) alarms to be analyse for improvement of performance(awareness regarding causes for occurrence, criteria for analysis) 3) understanding the correlations of alarms(simulteneous occurrence of various alarms) 4) action to be taken for alarms reduction(methodology and procedure for alarm reduction) 5) frequency for monitoring alarms(schedule for alarm collection and analysis) 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.
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
Alarm number in: switching equipment O&M equipment transmission equipment diagnosis report number base station/ transmission equipment alarms power equipment
50005499
external equipment
55005999
a.Type of alarm printout b.Name of the network element c.Remote subscriber stage (4 characters) Printed only if the object of the alarm is in a remote subscriber stage. d.Computer sending the alarm e.Alarm equipment type
SWITCH switching equipment O&M operation and maintenance equipment TRANSM transmission equipment POWER power equipment EXTERN external equipment
Unknown equipment type is printed as ??????
f.Date and time Start or termination time of the 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 (*). h.Printout type i.Alarm object j.Position coordinates of the alarm object k.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..
12) Trial information If the network element has been divided into a traffic transmitting part and a trial part, this field displays the text TRIAL if the alarm was issued in the trial side. 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. 18)Supplementary information fields 19)Supplementary text A more detailed text printed out in some alarms. 20)Alarm operating instructions The user defines an operating instruction with the AOA MML command for an alarm. If the instruction has been defined, then it is displayed in the alarm printout.
COMM communication failure QUAL quality of service PROCES processing failure EQUIPM equipment failure ENVIR environmental failure
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 (*). i.Printout type
ALARM fault situation CANCEL fault terminated DISTUR disturbance NOTICE notice
j.TRX number k.BTS name (15 characters) l.Alarm object (FU/CU/LAPD/PCM/RTSL/TRE/DMR/TRU) m.State of the alarm object
ENABLED The alarm object is able to provide traffic services DISABLED The alarm object is not able to provide traffic services
14) Consecutive alarm number 15) Alarm number Alarm number is a search index in the alarm reference documentation. 16)Text The text is a short description of the alarm.
17) Supplementary text In the case of alarms number range 7600...7699 this field indicates the fault reason. 18) Supplementary information fields A maximum of 16 fields which are separated from one another by one or several spaces.
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.
IP ftp
10.64.2.1
Path
m/home/nocldr/system_alarm_count
Cont..
Net doctor report 34 and 35 can be taken for alarms count in the circle. Performance report for transmission equipment. MML alarms logs ZEOL,ZAHO,ZEOH and ZAHP output for each NE. Daily MAPA also provide information about KPI degradation in cells.
179 487 6926 472 421 9418 388 3241 23691 149 239 155 1684 338 5052 1020 817 1037 279 148 369 6312 1413 3549 248 232 3160 970 140
41
BSS OMC BSS OMC BSS OMC Transmission Transmission BSS OMC Transmission BSS OMC BSS OMC BSS OMC BSS OMC RF RF BSS OMC RF RF Transmission Transmission Transmission BSS FLM Transmission BSS FLM Transmission BSS FLM BSS FLM BSS OMC BSS FLM BSS FLM BSS FLM BSS FLM BSS FLM BSS OMC
SGSN SGSN
7600 BCF FAULTY : Power unit is probably broken. Oven oscillator is broken. Temperature inside the TRX is dangerously high. Temperature inside the BTS is too high. The TX output power is out of limits (over maximum or under minimum). RF Impacted KPI : High TCH and SDCCH Blocking.
Calls have been cleared repeatedly on the same A interface circuit due to BTS and transcoder unsynchronisation and the number of successive releases has exceeded the limit defined. This alarm only informs the user that calls are cleared due to unsatisfactory transmission or equipment failure but it does not directly indicate the faulty equipment, for example a plug-in unit. Block the circuit. Check the transmission between (the BTS) the BSC and transcoder. Check other active alarms concerning (the BTS) the BSC and transcoder transmission or transcoder plug-in units. RF Impacted KPI : High TCH and SDCCH Drops.
Calls have been cleared three successive times on the same Abis interface channel due to BTS and transcoder unsynchronisation. This alarm only informs the user that calls are cleared due to unsatisfactory transmission or equipment failure but it does not directly indicate the faulty equipment, for example a plug-in unit. Lock the channel. Check the transmission between the BTS and the BSC (and transcoder). Check the alarms in transcoder plug-in units. RF Impacted KPI : High TCH and SDCCH Drops,TASR and HOSR.
A Network Service Virtual Connection is unavailable. It cannot be used for General Packet Radio Service, that is, the data transfer capacity has decreased. In FR transport mode Check first if the other end has manually taken down the Network Service Virtual Connection. Check the possible hardware and configuration problems mentioned below. Check that the pcm lines carrying the Frame Relay bearer channel and Network Service Virtual Connection are operational. Check that the plug-in units terminating the Network Service Virtual Connection, the AS7 in the SGSN's PAPU and the PCU in the BSC's BCSU, are operational. Check also that the identification parameters (NS-VCI, NSEI) of the connections are the same in both ends. Check that the DLCI is configured right. It has to be same in both ends of a point-topoint link. In IP transport mode (value of the first supplementary information field is 0xFFFF). Check first if the other end has manually taken down the Network Service Virtual Connection. check the possible hardware and configuration problems. RF Impacted KPI : Complete EDGE/GPRS service unavailable on the cells defined in the NS-VCI.
3019 NETWORK SERVICE ENTITY UNAVAILABLE ( Complete outage) 7704 PCM FAILURE (Complete Outage) 7705 LAPD FAILURE (TCH and SDCCH blocking) 7715 CONTINUOUS RESTARTS OF BCF/TRX (TCH and SDCCH blocking & Drops ) 7725 TRAFFIC CHANNEL ACTIVATION FAILURE(TCH Drop and Blocking) 7730 CONFIGURATION OF BCF FAILED ( SDCCH and TCH blocking or Complete outage) 7738 BTS WITH NO TRANSACTIONS ( 2915 FAULT RATE MONITORING
Displaying alarms
Alarms are written in a logical file. From the logical file, they can be directed to a local printer or to Nokia NetAct. The table below shows the logical files used with alarms. For further information on the logical files used with alarms, refer to the Logical files directed to terminal devices section of Logical Files. Table: The logical files used with alarms
Explanation LOGICAL FILE SWITCH1 TRANSM1 POWER1 EXTERN1 Two- or three-star switching equipment alarms Two- or three-star transmission equipment alarms Two- or three-star power equipment alarms Two- or three-star external alarms
OPERMA1
SWITCH2 TRANSM2 POWER2 EXTERN2 OPERMA2 BTSALARM1 BTSALARM2 BTSALARM3 BTSALARM4
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 .