You are on page 1of 11

Using Fault Management for NW Optimization

RANOP / 2007

Company Confidential
1 © 2007 Nokia

13-468261 v1.0

0 .Summary Introduction Alarms in DX 200 System Alarms in MML Alarms in Top Level User interface Alarms in Network Doctor Company Confidential 2 © 2007 Nokia 13-468261 v1.

Introduction Alarm analysis is the 1st thing to be done in worst cell troubleshooting! No use optimizing parameters if you have a HW problem! • Bad performance of a cell may be caused by faulty equipment. • Monitoring can be done through MML Commands. Nokia NetAct Top Level User Interface or Network Doctor. • Constant monitoring is needed in order to avoid critical alarms in any network element. • Check that there are no performance-affecting alarms in the cell monitored and also in neighbour cells! • Alarms are usually transferred to the NetAct database. • Periodically performance reports can include a resume of alarm status.0 . Company Confidential 3 © 2007 Nokia 13-468261 v1.

Alarms in DX 200 system – Groups Disturbance Failure printouts printouts (DIST UR) (ALARMS) 2000–2799 3000–3799 2800–2899 3800–3899 2900–2999 3900–3999 3700–3999 7000–7999 8000–8999 5000–5499 5500–5999 Diagnosis reports (DIAGN) Base station alarms Numbers T ransmission reserved for equipment possible alarms external alarms 4000–4799 4800–4899 4900–4999 Alarm number in: Notices (NOT ICE) switching equipment 0–799 O&M equipment transmission equipment diagnosis report number base station/ transmission equipment alarms power equipment external equipment 800 .999 1 000–1 799 1 800–1 899 1 900–1 999 Company Confidential 4 © 2007 Nokia 13-468261 v1.899 900 .0 .

0 . TRX number. The urgency levels of terminated alarms are indicated by dots (. Date. Time. • Event type COMM communication failure QUAL quality of service PROCES processing failure EQUIPM equipment failure ENVIR environmental failure Company Confidential 5 © 2007 Nokia 13-468261 v1. Alarm Number • Urgency level * Low Priority ** Med Priority *** High Priority • Printout type ALARM fault situation CANCEL fault terminated DISTUR disturbance NOTICE notice Note: The urgency level is output in all alarm printouts except notices (NOTICE). Alarm Object.) instead of asterisks (*). Unit.Alarms in DX 200 system – Printout Fields • Alarm Number • BCF number. BTS number.

TRX and • TRX and RTSL configuration and status • ZERO: OUTPUT TRANSCEIVER PARAMETERS RTSL are LOCKED or UNLOCKED. WO (working). BL.USR (blocked by user) or Restarting. Company Confidential 6 © 2007 Nokia 13-468261 v1.0 . SEG or BTS configuration and status • ZEEI: OUTPUT RADIO NETWORK CONFIGURATIONVerify if BCF. SEG. BTS.Alarms in MML • Alarms in BSC Level: • ZAHO: PRINT ALARMS CURRENTLY ON • ZAHP: PRINT ALARM HISTORY • Alarms in BTS Level: • ZEOL: LIST ALARMS CURRENTLY ON • ZEOH: LIST ALARM HISTORY • BCF.

Alarms in MML • HW Tests: • ZUBK: HANDLE ABIS LOOP TEST (Parameters: BTS. RTSL. TRX. loop duration) Company Confidential 7 © 2007 Nokia 13-468261 v1. TRX.test selection. RTSL.STM antenna attenuation. Fixed or Dynamic Abis connection and Abis TSL and Sub-TSL.test connection.BS TX power attenuation. test mode. RTSL. diversity path selection. looping time) • ZUBS: START TRANSCEIVER TEST (Parameters: BTS.0 .BTS RX level. RF test signal attenuation.

Alarms Examples • 2993: BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON ABIS INTERFACE Transcoder and transmission alarm. • 7045: TRX/FU DATA TRANSFER ERROR BETWEEN FU AND CU16 Base Station alarm.0 . Abis test is needed. • Example of a BTS alarm printout: Company Confidential 8 © 2007 Nokia 13-468261 v1. A possible solution can be to change the TRX. Observed when TCH failure rate is very high.

Alarms in Top Level User interface • The Top-level User Interface contains graphical views of the network.0 . in which network elements are represented hierarchically with symbols • One of the main functions of the Top-level User Interface in network monitoring is to show the alarm situation in all managed objects • The different colors represent the severity of the produced alarms Company Confidential 9 © 2007 Nokia 13-468261 v1.

0 .Alarms in Network Doctor NWD report 023 – Alarm statistics by cells NWD report 020 – Alarm statistics NWD report 034 – Alarm Types and counts NWD report 035 – Alarm Types and counts for BSC NWD report 024 – Active BCCH missing alarms NWD report 025 – Alarm sum time by cells NWD report 027 – Call outages breakdown over 10 days NWD report 030 – BSC alarm breakdown Company Confidential 10 © 2007 Nokia 13-468261 v1.

0 .Thank you! RANOP / 2007 Company Confidential 11 © 2007 Nokia 13-468261 v1.