ttsl operations bss troubleshooting guide ver1 1 12022013

BSS Troubleshooting guide Updated by Date Revised

Draft Version (BSC / RNC / Transmission / BTS) Amit Jindal 11/Feb/2013

Tellabs details added P U B Sharma 12/Feb/2013

Additional point of RNC and BSC added 12/Feb/2013C Jaya/Uday

Nayak

Revision No. Comments

1.0

1.1

1.2

BSS TROUBLESHOOTING GUIDE

1 BSC

2 RNC

3 TRANSMISSION

4 BTS

BSS TROUBLESHOOTING GUIDE

OSS connectivity down - both x.25 downOne X.25 downNSEI DownBVCI DownZero Voice calls on particular CellUnit re-startSIGNALLING LINK OVERLOADSIGNALLING LINK DOWNSIGNALLING LINK ACTIVATION OR RESTORATION FAILURESIGNALLING LINK SET DOWNGPRS/EDGE LOAD IS VERY HIGH IN PCU OF PSEBTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON ABIS INTERFACEWDU FAULTYSTMU FAULTYMCMU RESTARTBCSU RESTARTBCSU SWITCHOVER

Iu-CS link downBoth Iu-PS links downOne Iu-PS link downBASE STATION FAULTYBASE STATION OPERATION DEGRADEDBASE STATION NOTIFICATIONCELL FAULTYCELL OPERATION DEGRADEDCELL NOTIFICATIONBASE STATION LICENCE NOTIFICATIONBASE STATION TRANSMISSION ALARMBEATING WCDMA BTS ALARMFAILURE IN WCDMA WBTS O&M CONNECTIONRNW O&M SCENARIO FAILUREWCDMA CELL OUT OF USEHSDPA CONFIGURATION FAILEDWCDMA BTS DEDICATED MEASUREMENT FAILUREHSUPA FAILURE IN WCELWCDMA BASE STATION OUT OF USE

BFD Down in AXC (Tellabs)3G Sites down 2G or 3G sites down (Mw ring collapsed)2G/3G multiple sites down

Some Subscribers not able to latch on TATA network from specific handsets

EXxx TRX module cooling fan s report no rotation,ESMA System module cooling fan s report no rotation ERxx DDU module has detected VSWR above minor limit at anten

SYNCHRONISATION IS MISSING

Rx levels differ too much between main and diversity antennas, RSSI detected Rx signal difference exceeding threshold

S. No. Problem Alarm No. at BSC

1 2175

2 One X.25 down 2175

3 NSEI Down 3315

4 BVCI Down

OSS connectivity down - both x.25 down

4 BVCI Down

5 7738

7 26

8 1072

9 2072

10 2070

11 3415

12 2993

Zero Voice calls on particular Cell

SIGNALLING LINK OVERLOAD

SIGNALLING LINK DOWN

SIGNALLING LINK ACTIVATION OR

RESTORATION FAILURE

SIGNALLING LINK SET DOWN

GPRS/EDGE LOAD IS VERY HIGH IN PCU OF

PSE

BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON ABIS

INTERFACE

13 2992

13 DISK FAILURE 2860

14 WDU FAULTY 2861, 2692

15 STMU FAULTY 2794

BTS AND TC UNSYNCHRONIZATION

CLEAR CALLS ON A INTERFACE

16 MCMU RESTART

17 BCSU RESTART

18 BCSU SWITCHOVER

26920690,1001

269206901001

269206901001

19 2,641

20 2631

21 3030

22 3020

23

2133

24

2760

25

Loss of Synchronization in BSC

OPERATION MODE CHANGED TO PLESIOCHRONOUS

BSSGP VIRTUAL CONNECTION BLOCK PROCEDURE FAILED

NETWORK SERVICE VIRTUAL CONNECTION UNAVAILABLE

SEND BUFFER OVERFLOW IN SIGNALLING TERMINAL

BSC Internal & External alarms are not reporting

BSC External alarms are not reporting

Alarm Description / Comments Catergory

OSI CLNS LINKAGE NOT AVAILABLE

Serv

ice

affec

ting

non-

Serv

ice

affec

ting

OSI CLNS LINKAGE NOT AVAILABLE

ALL NETWORK SERVICE ENTITIES UNAVAILABLE

Serv

ice

affec

ting

Serv

ice

affec

ting

Non-Service

affecting

Serv

ice

affec

ting

BTS WITH NO TRANSACTIONS

SIGNALLING LINK LOAD OVER THRESHOLD

SIGNALLING LINK OUT OF SERVICE

FAILURE IN SIGNALLING LINK ACTIVATION OR RESTORATION

LINK SET UNAVAILABLE

GPRS/EDGE LOAD IS VERY HIGH IN PCU OF PSE

BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON ABIS INTERFACE

Serv

ice

affec

ting

Service affecting

Non-Service

affecting

BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON A INTERFACE

DISK FAILURE

NO ACCESS TO DISK ,INCORRECT WORKING STATE

non-

Serv

ice

affec

ting

HW BLOCK FAILURE IN PLUG-IN UNIT, HOT LINK FAILURE ALARMS.

Serv

ice

Thre

aten

ing

Serv

ice

Thre

aten

ing

Serv

ice

affec

ting

Serv

ice

Thre

aten

ing

INCORRECT WORKING STATEworking State Changed , Unit restarted

INCORRECT WORKING STATEworking State Changed , Unit restarted

INCORRECT WORKING STATEworking State ChangedUnit Restarted

Failure in Synchronization Signal

Serv

ice

Thre

aten

ing

Hwat failure

BSC External alarms are not reporting

The operation mode of the unit has been changed to plesiochronous due to a failure in all the external synchronization signals. Slips occur generally in the plesiochronous operation mode. The number of slips depends on thecorrectness of the control word value which is in the synchronizationunit. The situation is serious if the control word of the synchronizationunit has drifted too far from its correct value.

Service Threatening

The system has unsuccessfully tried to block a BSSGP virtualconnection as many times as defined with the BVC-BLOCK-RETRIESparameter. An acknowledgement has not been received from the SGSN.In spite of the failure the virtual connection has been marked asblocked in the BSC.

Service Threatening

A Network Service Virtual Connection/Link is unavailable. It cannotbe used for General Packet Radio Service, that is, the data transfercapacity has decreased.

Service Threatening

This alarm reports is AS7_c of BCSU,this will cause LAPd fluctutation & TRX fluctitation

Service Threatening

Service Threatening

Service Threatening

Affect / Steps to be follow for troubleshoot

1. Check the signalling links states at MSS end

2. If signalling links / link set down means BSC down(Alarm-Link Set Unavailable)

3. Send local engineer at BSC site

1. Check the signalling links states at MSS end

5. If media ok, Send local engineer at BSC site

1. Check the Transmission path - Is there any alarm in X.25 E1 path / path broken.

2. Check the alarms. If PCM ok then reset the X.25 ET as well as X.25 links from BSC .

Data traffic affect, down

If only some NSEI down (one or two) follow below steps1. Check the PCU - BCSU combination

2. Ping SGSN (PAPU) IP from that BCSU-PCU

3. Trace PCU IP from SGSN

4. Shift the traffic (DAP) to other PCU-BCSU

Data traffic affect, down

1. GENA toggle & check status.

2. Check PCU-BCSU combination:

(c) BCSU switchover.

4. Check BSC end Mux status & alarm. 1st: Mux unmanaged - check alarm at connected Mux, Power issue at BSC site. Check the end-end E1 connectivity and reoute the E1 on alternate path if there is a break in main path.2. Mux managed - check alarm at Mux & verify the power status for BSC.

5. Login BSC via VDU / LANU. Check the alarms & current computer unit status, if login is possible.In case login is not possible ,get login through OMU CPU and check the status of OMU and other computer units.If we will not get the login through OMU also ,raise the emergency and follow steps as per with care team recommandation.

2. If Signalling links found ok, Check the voice & data traffic at MSS & PACO end (normal or any degradation)3. Check the Transmission path - Is there any alarm in X.25 E1 path / path broken, then re-route path & check X.25 links status.

6. Locally login the BSC via VDU / LANU & check the alarms. Reset the X.25 ET as well as X.25 links.

7. If BSC not login via VDU / LANU than login through CPU of OMU unit and check the status: after login ask for password then login ok, or if continuously restarting phase means OMU unit faulty. Do as per care team recommendations.

Check no. of NESI's down, if down all - Trace PCU IP from SGSN & find last hop address & check media B/W that hop to BSC

5. During MW Hrs diagnose that BCSU. 1. Diagnose ok - make BCSU in WO state and observe the alarm & UP/DL tbf. 2 Diagnose not ok - change the PCU and again run diagnosis.

(a) In case a particular PCU-BCSU combination: shift the traffic to other PCU & Switchover BCSU in MW and run diagnosis. (b) PCU-BCSU combination random on many BCSU-PCU combinations - Traffic prevent - unprevent from both end and PSE re-set.

(d) PAPU re-set / switchover .Check hardware, cabling & commissioning

This notice appears repeatedly - consider adding more signalling links

Check the Transmission path

Check the Transmission path

Check GPRS/EDGE load & balance the load by reallocate the DAPs

Thershold value need to be change or PCU addition require if load balancing ok.

Impact: Call drop, Quality degradation, Call muting

Check the Transmission Media, if not ok then clear the path issue.

Impact: Call drop, Quality degradation, Call muting

Need to give sector reset as a first step. If still persists, need to verify the traffic trend of a sector from NPO team.Then need to verify at site level like physical power level of TRX and Orientation of Antenna and Check UP/DL quality, path imbalance/VSWR/RSSI.

A signalling link has failed and changed state from IN SERVICE to OUT OF SERVICE, or its initial alignment attempt has failed.

If there are other path available, signalling links path re-route with discussion with planning team

The activation or restoration of a signalling link fails. Signalling transmission capacity decreased.

If there are other path available, signalling links path re-route with discussion with planning teamAll signalling links in the signalling link set are unavailable. 100% traffic of that link set down.Check alarm: 2064 - ROUTE SET UNAVAILABLE. If this alarm present means no route is availableCheck for the end to end connectivity for the Aters carrying signalling (MSC,TXN and BSC), transmission alarms.If found OK then send the engineers at the BSC for further troubleshooting.

If Transmission Media found OK, then check the timeslot mapping between bts and bsc should be checked. if mapping is fine, timeslot bypassing should be checked for the problem BTS/TRX, and if it is coming on more than one timeslot, and everything else is fine, trx should be replaced and call test should be done on all time slots after replacement. If it is coming for only one timeslot, the time slot may be locked till the time , replacement is made. the site should also be checked for other alarms and reqd action should be taken .

Impact: No hard disk Redundancy, Measurements might be affected.

Need to identify the Ater No and CCSPCM's from where there alarms are getting triggered from ZAHP of BSC, should get verify the Transmission media between the BSC and MGW for the connected ATER links. It should be corrected if any CCSPCM mismatches between BSC and MGW.After correcting this need to verify the reoccurance of alarms from history and test calls to be made.

The system has detected a serious error that may have been caused by the hard disk or the SCSI controller plug-in unit breaking down.Saving data into the hard disk or reading data from the hard disk fails.Run the diagnosis on the faulty hard disk and if diagnosis fail then change the hard disk as per standard procedure for replacing the WDU

should be checked. If it is one WDU or both WDU are in BL-SY state . 2. Perform the JOJI of harddisk ( with JOJI the HDSAM ) and DCAR card .perform the OMU restart and check .if problem reolved, perform the diagonisis of WDU and check the all database is updated or not .3. if problem does not resolved , swap the position of WDUs in DCAR card and check if problem shifted to another hard dsik it means it is hard disk issue ,if problem is with same slot it means it is a problem of DCAR card. (During this troubleshooting SOMAFI patching document should be available with Engineer)4. If problem does not resolved or repeat again and again than replace the DCAR

1. Check the status of STMU with ZUSI:STMU:; commands. Check the current & History alarms & Site/aters outage if any related to faulty STMU.2. Check the supplementary information of alarms & work as per information .3. Clear the faulty tag with ZUST command and observe.4. Check the alarms of ET/ transmission and set loss with ZYWI command.5. Temperature condition need to check at BSC location.6. Check the STMU cabling and if required replace the Hardware.7. Check the SFU modules by swapping with spare and isolate the break if any.

1. Check the status of computer units with ZUSI:COMP:; commands. Check the current & History alarms. 2. Check the supplementary information of alarms & work as per information (switchover / diagnose).3. check ZIGO & ZUDH.4. Change the state of MCMU to SE-NH and perform the JOJI of all cards og MCMU and GSW .after Diagonise the unit and check.4. if problem repeates on same MCMU ,replace the hardware with help of alarm info. 5. Perform the diagonistics of that MCMU /EMB and make it in working State.6. If no alarm found or problem occur on different -different units with same alarm Number it may be a SW bug.Note : Kindly note before switchoff the MCMU respective MCMU and EMB should be in SE-NH state also during any hardware replacement check the Jumper setting of the card.during any hardware replacement check the Jumper setting of the card.

1. Check the status of computer units with ZUSI:COMP:; commands. Check the current & History alarms. 2. Check the supplementary information of alarms & work as per information (switchover / diagnose).3. check ZIGO & ZUDH.4. if problem repeates on same BCSU ,replace the hardware with help of alarm info. 5. Perform the diagonistics of the BCSU with both MCMU and make it in working State.6. Check the BVCI state and lapd States7. If no alarm found or problem occur on different -different units with same alarm Number it may be a SW bug.Note : During any hardware replacement check the Jumper setting of the card accordingly.

1. Check the status of computer units with ZUSI:COMP:; commands. Check the current & History alarms. 2. Check the supplementary information of alarm & work as per information (switchover / diagnose).3. check ZIGO & ZUDH.4. if problem repeates on same BCSU ,replace the hardware with help of alarm info. 5. Perform the diagonistics of the BCSU with both MCMU and make it in working State.6. Check the BVCI and Lapd state.7. If no alarm found or problem occur on different -different units with same alarm Number it may be a SW bug.Note : During any hardware replacement check the Jumper setting of the card accordingly.

1. Check the ZDRI :; command output with Current alarms.2. Check the ET alarms on Sync ET .3. Disconnect the all sync with ZDRC command ,setthe ossilator control word value to 32000 on both CLS and reconnect the all sync inputs with correct priority.Note : If any BSC is out of Sync ,there will be slip on all ETs of that BSC .

1. Verify the input sync quality.2. Monitor slips on ATER links and check the transmission path for any degraded errors.3. Switch Hardware, if problem persists replace it.

The transmission lines carrying bearer channels/IP packets are operational and that the Network Service Entityused by the cell is OK1. Swap BCSU of that particular cells having this alarm.2. Give GENA reset to the cells.

Check for the transmission link errors and rectify them. The configuration at both ends should be same, If problem persists than verify the hardware associated with link and reset/change the hardware.

1:Check the alarm in which computer uint alarm is reported. 2:Jo/Ji of AS7_C card in MW & Diagnosis of the unit. 3:Replace AS7_C is diagnosis is getting failed

1:Need to give one OMU restart in MW,If still alarm persist need to replace HWAT card

1:Check the Extarnal alarmscable & connector. 2: Check the loop test from DDF. 3: Check the continuity of cable fromend to end. 4:Check if any shot with grounding

S. No. Node Problem

1 RNC Iu-CS link down 2070

2 RNC Both Iu-PS links down 2070

3 RNC One Iu-PS link down 2070

4 Nod BBASE STATION FAULTY 7650

5 Nod B BASE STATION OPERATION DEGRADED 7651

6 Nod B BASE STATION NOTIFICATION 7652

Alarm No. at RNC

Alarm Description / Comments




No connection to Flexi transport submodule

BTS reference clock missing

BTS RNC/I-HSPA interface signalling link failure

System module failure

BTS requires restart because license status has changed

BTS time not corrected

6 Nod B BASE STATION NOTIFICATION 7652

Fan failure

Temperature alarm

7 Node B CELL FAULTY 7653RF module failure

VSWR alarm

8 Node B CELL OPERATION DEGRADED 7654

RF module failure

9 Node BCELL NOTIFICATION 7655

10 Node B BASE STATION LICENCE NOTIFICATION 7661

Difference between BTS master clock and reference frequency

Heating element not working

Failure in optical RP3 interface

Incompatible SW version detected

Rx signal level failure

Radio resources switched off

HW capacity too low for feature 308, Licence Based BTS channel c

10 Node B BASE STATION LICENCE NOTIFICATION 7661

11 Node B BASE STATION TRANSMISSION ALARM 7665

12 Node B BEATING WCDMA BTS ALARM 7740 (blank)

13 Node BFAILURE IN WCDMA WBTS O&M CONNECTION 7750 (blank)

14 Node B RNW O&M SCENARIO FAILURE 7761

Licence missing 00000001125, Flexi WCDMA BTS 60W Power License

Licence missing 0000000306, HSDPA 16QAM SW Licence Support

Licence missing 0000000307, HSDPA Proportional Fair Resource Pac

Licence missing 0000000649, Shared HSDPA Scheduler for Baseband

Verification of target ID failed 3 times.

License missing for feature Additional 2 E1, T1, JT1 interface o

License missing for feature UBR+.

AAL2 path unblock not accomplished

BCCH information updating has failed

Common channel deletion has failed

NBAP interface type unknown failure

15 Node B WCDMA CELL OUT OF USE 7771NBAP link failure

WCEL state not WO

16 Node B HSDPA CONFIGURATION FAILED 7772

RNC internal error

17 Node B

WCDMA BTS DEDICATED MEASUREMENT FAILURE 7778

18 Node B HS(U/D)PA FAILURE IN WCEL 7780

19 Node BWCDMA BASE STATION OUT OF USE 7786 (blank)

20 RNC SCTP Association lost3159

21 RNC

FDU Faulty

Block resource request, normal priority

Common measurement failure scenario

Resource status indication, cell disabled

WCEL state not WO after setup

WBTS rejects the configuration

22 RNC

OSS Link Down

23 RNC Redundancy issue at SET

24 RNC Multiple cells down in same RNC at same time

25 RNC

Traffic dip in RNC

26 Node B Interface down alarms

27 RNC

ROUTE SET UNAVAILABLE

28 RNCVP/VC LEVEL AIS RECEIVED 3974

Cateagory Impact

SA RNC Total Outage

SA RNC data traffic outage

NSA No Data traffic outage

SA Transmission to NodeB will be affected

SD

SA NBAP/AAL2 signalling link failure

SA

SA Mentioned licence feature will not work

NSA BTS time will not be correct

Service will be affected based on the degradtion threshold level

NodeB Capacity may be reduced/NodeB totally may not be opreational

NSA BTS frequecy deviates from IuB referecne

NSA Temparature will be increased

SA

SA

SASectors will be affected depends on severity

SA Sectors Operation will be degraded

NSA Sectors Operation will be degraded

SA Cell will be down

NSA

Heating from the heating element isnot available. The module temperaturemay not reach the working level ormay reach it very slowly

Depending on severity BTS Capacity may be reduced/BTS totally may not be opreational




The licenses are granted but cannot be used. Some of the licensed features are not available.

SA Sector down

SA SDPA Traffic will affect

SA

SAService Degraded

Cell Down

NSA Repeatation of any alarm causes

NSA

SA

Cell Down

Cell Down

Cell Down

Cell Down

NSA Degradation

NSA Degradation

Degradation of system module

BTS Cannot be logined remotly & Measurements will not be updated

SA

Sector down

Sector down

Sector down

Sector down

Sector down

When Site Down Or Sector Down

SD

Service Degraded

Service Degraded

SA DCN state - Disable Or Cell Faulty

SA

SA WBTS will be down

SATraffic will be affected

UMS backup cannot be taken

A unit (or units),taking care of HSUPA traffic in the WCEL can be faulty



NSA Remote login of RNC is not possible

During main SET breakdown, outage will report

3G voice and data outage

Partial outage

Alloted Bandwidth for Site decreases

RNC Outage

Site outage


Possible Causes

Affects: Communication with MSS down: Total outage

2. Ping & trace MSS control plane and user plane IP

3. Check Association set and association links status and end IP

4. Check connectivity B/W end trace IP to MSS.

Affects: Communication with Both SGSN down: Total data Traffic outage

2. Ping & trace SGSN control plane and user plane IP


Affects: Communication with one SGSN down: data working fine with connected SGSN, no outage happened in this case,only redundant path down.

2. Ping & trace SGSN control plane and user plane IP


Malfunction of Transport Module in System Module

Site Clock E1 having errors / AIS

Abnormal functioning of FSM

After licence installation BTS not given restart

NTP Server IP mismatch

1. Check the unit status for any failure and check the current and history alarms


4. Check connectivity B/W end trace IP to SGSN.


4. Check connectivity B/W end trace IP to SGSN.

Transmission break or fluctuations-Take ping from working OMU to TRS IP

DAC Valure variations

The heater control connection of the FSM is faulty, there is no heater or the heater is faulty.

Abnormal/ failure in optical cable between FSM & FRGP

SW Mismatch of BTS

Abnormal functioning of FRGP

High VSWR

Abnormal functioning of FRGP

As per configuration H/W mismatch/unavailability

H/W Faulty-Dust on Fan

The internal temperature of the RF Module or System Module exceeds the threshold value, or the ambient temperature of the module(s) is outside the specified limits.

The RX signal level is less than -112dBm or the difference between the maximum and minimum power levels of all RX antennas in the same cell and sector is more than the limit (4 dB). The jumper cable is faulty, water entry, RF module antenna port faulty

The HW capacity is too low to support all licenses of an optional feature. Problem reports when HW is loaded with more than specified number of CEs

During NodeB commissioning seleted 60W power for sector.

HSDPA License Missing Or Cell Down

This basic license missing

HSDPA License Missing

Repeatation of any alarm causes

CoCo/ATM Configuration Mismatches between NodeB/RNC/Tellabs




License missing

License missing

Hanged/config issue/comm issue

DCN Configuration mismimatch in NodeB/RNC/tellabs-All E1s are down/Media is not ready

Cell Down

Cell Down

Cell Down

Cell Down

Cell Down

Cell Down

Cell Down / Interface Down Or H/W configuration In Node-B

Cell Down / Interface Down Or H/W configuration In Node-B

Cell Down

Cell Down

Cell Down

CNBAP/BRM Break

IuCS/IuPS CP, IuR

OMU switchover, corrupted disk

DCN connected E1 Interface needs to be cross check. The alarm reports only after OP3 interface failure

TXMN path, physical connectivity, ESA port, ESA

MSP Configuration at RNC and tellabs

ICSU

TXMN backbone

TXMN Path, physical connectivity, Port faulty in MUX, IDU, TM

TXMN, Physical connectivity, Ports faulty

TXMN, Physical connectivity, Ports faulty


Solution

Check transmission configurations and paths

Reset FSM/Replace FSM

Restart BTS.

Check NTP server IP it should be same as RNC OMS IP

1: After checking points 1,2 &3 in Column G, Check the ping response and traceroute.

2: Based on traceroute, note the problematic hop, and start working on that hop and beyond.

3: The possible cause would be port fault at any router, port configuration etc.

4: If problem is observed in the first hop, then need to check for HW/ Physical connectivity









Reset System Module/Replace Transport Module in System Module

Clock E1 Interface needs to be check & Check the SYNC of TXN side

Set DAC value to standard value

Check working status of Fans or replcae FAN units in FSM

Check the FAN units in FSM/FRGP

Recomission BTS with Correct SW version

Reset FRGP/FSM/Check interface cables/Replace FRGP

Check the VSWR, should be less than 1.3

Reset FRGP/FSM/Check interface cables/Replace FRGP

Check the cell configration & H/W availbilty at site

Check whether the heating element exists at all./ Check the heater control connection and that the heater is working./ Replace the alarming component.

Check the Optical cable connecton between FSM & FRGP/Reset FSM/Replace cable.

1. Locate the problem with supplementary information fields of the alarm.2. Verify the BTS by checking the commissioning, cabling and correct installation of the units/modules at the WCEL.3: Check for RX level value, at ports in questions, and resolve the fault, either by reconnectorisation, changing jumper cables, RF module.Check the VSWR & Antenna cables

Call to GNSC CM Delete the licenses or insert new hardware.

Call to GNSC CM get it clear

GNSC has to load this basic license from Netact

GNSC has to load this basic license from Netact

Cancels once causing Alarm is cleared

To be checked DCN Configrations at RNC/NodeB/Tellabs

Login to nodeB and change parameters of sector power to 20W

License missing

License missing

Hanged/config issue/comm issue

To be checked CoCo/ATM Configuration Mismatches between NodeB/RNC/Tellabs




Need to check WCELL/WBTS alarm





Once Node-b is up, alarm will clear

Node-B Lock & Unlock Or Restart Node-B / Cross check & Rectify Node-B H/W Configuration --All This action based on Sublimentory information of Alarm

Node-B Lock & Unlock Or Restart Node-B / Cross check Node-B H/W Configuration --All This action based on supplementary Alarm Info.

DCN Interface / Lock all the cells under the BCF and delete & Re-create COCO configuration and unlock all the cells / If required Site reset has to be given ( Anlaysis based on supplementary info)

1. Firstly check the working state of WCEL.2. Resolve the other active alarms for the same WCEL or its parent WBTS object.3. A unit (or units),taking care of HSUPA traffic in the WCEL can be faulty



Check the transmission path & Configuration between NodeB to RNC

1: Check destination address, SPC2: Based on Point1 OP, further troubleshooting required similar to "2070" alarm in RNC.

1: Check whether the USB stick is present in FDU of working OMU.2: If FDU is not coming to working state in working OMU, then JOJI of FDU need to perform.3: Replace the USB stick with new USB(USB might be corrupted, if it is used in laptop to copy backup files.

1: Check the reachability of RNC from Router to identify problematic hop.2: If problematic hop is found before gateway IP of RNC, need to check the TXMN path.3: From Router, last hop reachable is next to gateway IP of RNC, then need to check cabling between RNC and its first hop.4: From Router, last hop reachable is gateway IP of RNC, then need to check ESA port, ESA card.

1: Check for MSP configuration at Tellabs and RNC.2: JOJI of SFP modules to be carried out.3: Replace the SFP.

1: Check whether the cells controlled by same ICSU.2: Swicthover ICSU with the SP unit.

1: Problem may report in Voice and Data.2: Take ping wrt destination address for UP/CP.3: Take traceroute OP wrt destination address for UP/CP.4: The problematic hop can be identified by the hop where more delay is observed in traceroute.5: If no such hop found, need to analyse fishing logs and IMSI based trace from RNC.

1: Check the E1 status from NMS, KLM mapping, option for re-routing etc2: If LOS observed at site end in NMS, the cable may be faulty, port faulty in MUX/TM.3: Check for BW availability in TXMN Backbone.

1. Check the supplementary information to which signaling traffic to the signaling point indicated is totally blocked.2.If the signaling link sets to the STP concerned are available, then there may be a fault in the network configuration.

1. The error can be in the physical link, hence check for particular physical path.2. Verify the configuration for that link.

S. No. Problem Alarm No. at BSC Alarm Description / Comments Catergory

1 7665 BFD down

2 3G Sites down Base Station out use

3 Fault rate monitoring & PCM failures

4 Fault rate monitoring & PCM failures

5 M/W Link Problem

Serv

ice

Thre

atni

ng

BFD Down in AXC (Tellabs)

Service Degradation

Service affecting

2G or 3G sites down (Mw ring collapsed)

Service affecting

2G/3G multiple sites down

Service affecting

No Alarm observed in the link, except RSL dip at one end.

At one end, RSL of the link is OK, on other end it dips to -90dBm.

No typical alarm observed in the link.


Deimplement trails for culprits ISA & raplace ISA ASAP.

Sites need to be indentified on particular MUX

Core mux malfunctioning at BSC/RNC location

2G & 3G site database shared with all CTLs

BFD down or fluctutating in AXC & data traffic shifted to ATM, Cause HSPA fallback enabled. Checked txn media as well as ISA card or reset Mux ISA card to restore BFD.

Need to check utilization of GE ports, If broadcast packets incresing then need to check the txn- media & ISA card.

Downs sites need to be check belongs particular AXC card or Mux particular STM-1 port. Need to check alarms on port, If any alarm appears then switch to redundant port to restore sites

If the CPU utilization for both Main & Spare IFMcard are hign then remove one by one & inserted Main card to reduce CPU utilization. Atlast switched CDC card from main to redundant card.

Need to check alrams on ALU mux port during ring collapsed at both end.

Need to ping connecting IDU from GNOC to check alarms & w.r.t appeared alarms we identify either power issue or hardware fault

Enginners need to send at site with hardware for further trouble shooting.

Impact: Microwave Link gets down

Reason of the problem: Normally in this type of scenario, ODU of the link (at the end where RSL is OK) is misbehaving. Its transmitor gets off, stops radiating. But, it receives the signal properly.

Troubleshooting: ODU to be replaced

S. No. Problem BTS Type

1 Flexi/MR 7787

2

3 Flexi 7607

4 Flexi 7607

5 Flexi/MR 7607

6 BTS Faulty Flexi / Ultra 7603

Alarm No. at BSC

SYNCHRONISATION IS MISSING All External Q1 device fail to respond

a)Some Subscribers were not able to latch on TATA network from specific handsets.While Same Handsets were running fine with IDEA or any other operator from a perticular site (N_UW_NRA_001,Muzzafarnagar)

Flexi Edge BTS

Rx levels differ too much between main and diversity antennas, RSSI detected Rx signal difference exceeding threshold

EXxx TRX module cooling fan s report no rotation,ESMA System module cooling fan s report no rotation

a)ERxx DDU module has detected VSWR above minor limit at anten

7 Flexi / Ultra 7604


9 NO E GPRS TRANSACTION IN BTS Flexi / Ultra 7789





Rx LEVEL DIFFER BETWEEN MAIN AND DIVERSITY ANTENNA

CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD

There is a difference in the reference frequency of PCM and base station.

This alarm is generated, If there is a fault in input/output power supply or temperature of TRX is high/low or cooling fan faulty

The Abis frequency is too high or too low, or it fluctuates so muchthat the master clock tune is unreliable and tends to oscillate too much.

The system has blocked the radio time slot because the callcontrol has failed a number of times in the activation ofa radio channel.


Service affecting

Service affecting

service affecting

This alarm blocks the alarming sector. service affecting

DFCA not working in that particular Site,One more Observation:Site will continously restart when DFCA is enabled in the site

Observation:At Problematic location/Premises(N_UW_NRA_001,Muzzafarnagar) there are two NSN equipments serving for IDEA/TATA.No alarm was found on problematic site.

Rx levels differ too much between main and diversity antennas,RSSI Value is high than 10.

Service Degrading

TRX cooling fan not rotate ESMA cooling Fan not rotate

Service Degrading

VSWR limit is high than 1.5 for Minor alarm and >2.7 for major alarm

service affecting

service affecting

service affecting

service affecting

service affecting

service affecting

TRAFFIC CHANNEL ACTIVATION FAILURE service affecting

There is a difference between RX level of main and diversity antenna of BTS.

The percentage of rejected channel seizure requests due to congestionas opposed to all channel seizure requests in the base station isabove the operator-defined alarm threshold.This alarm describes the congestion situation of the whole cell although it is only given to the BCCH BTS. The alarm is used to supervise the traffic capacity of the basestation.

No successful (E)GPRS transactions have occurred within the supervisionperiod

DIFFERENCE BETWEEN PCM AND BASE STATION FREQUENCY REFERENCE

TEMPERATURE, POWER INPUT/OUTPUT AND COOLING FAN FAULTY

OSCILLATOR ADJUSTING TEMPORARILY INTERRUPTED


1.First step to check the site is down or not (ZEOL) 2.if site is working with DFCA unsync and LMU is in stand by mode (ZEFL) than visit the site 3.Check the parameters such as LMU area parameter,DFCA disabled or enabled4.Check ESLA cable connectivity between ESMA to LMU ,if found any abnormality then Replace ESLA cable 5.Check LMU unit Activities steps as follow:-1.Firstly we Check Infra condition of the site2.Check the BTS configuration of the site ,properly check weather there is any alarm in site,But no service affecting/Service degrading alarm found3.After that we check DAC value,RSSI comparision value and VSWR value with Site master but problem not resolved.4.Change the PLMN allowed from 1 upto 7.5.Replaced the ESMA card. 6.Shift BCCH to another TRX and check7.Shift BCCH to another TRX and check.8.Swapping of TRX's from other perfet site to problamatic site and check. 9.Site deletion and further recreation done still no improvement found10.Rehome the site BCF-22/ Muzaffarnagar BSC to Meerut -1 BSC with different LAC and CI and check.11.Finally problem resolved after replacing the ESMA card of IDEA site serving at same location.Conclusion - There was some Sync problem at Idea Site of that perticular loaction 1.Check the RSSI measurements with BTS Manager.2.Check the BTS RF cables and connections.Check the antenna and RX cabling. 3.If the antenna and RX cabling are faulty, correct the problem and run TRX test to cancel the alarm.4.Check and measure VSWR of the antenna lines.5.Check that the RX-DL parameter at the BSC is set to a reasonable value in order to prevent unnecessary alarms.1.90% there is a chance of Over heating or Room tempurature high inside shelter 2.if there in an issue of tempurature resolve the issue along with IP 3.Check that the fan unit cable is correctly connect to DTRX/ESMA 4.Check that there are no obstacles preventing the fan(s) from rotating 5.Clean the fan unit of dust and/or dirt 6.if problem is still presist then Replace the fan unit 7.If problem is not resolved with all above steps then Replace TRX/ESMA

1.Measure VSWR value with Site Master ,If value is found high then second step is to see the fault via Distance to fault location . 2.According to distance found, replace connector,Jumper ,Anteena or damaged feeder cable 3.With external test equipment check VSWR of the antenna line. Repeat step 1 if the measurement is again high 4.Check RSSI comparision value between Main and diversity of that particular sector 1. Analyse and rectify other TRX related alarms in this particular BTS.2. Verify EDGE settings as per configuration.

1. Check the difference in RSSI measurements by BTS Manager.2. Check and measure the antenna lines with >2 db difference.3. Check the VSWR of particular BTS RF cables and connections.4. Replace the combiner unit. Check that the RXDL parameter at the BSC is set to a reasonable value, taking into account the site conditions in order to prevent unnecessary alarms.5. Replace the TSxx unit.

1. Check the object of congestion in supplementary info.2. Verify parameter settings and change the default values.3. Permanent solution is Increase the network capacity if necessary.

The BSC's ability to transfer GPRS/EDGE traffic in the BTS has been totally prevented.1. Swap BCSU of that particular cells having this alarm.2. Reducing the default GPRS/EDGE / extended cell area GPRS/EDGE channels connected to PCU3. Reducing the amount of dynamic Abis pool (DAP) timeslots connected to the PCU4. Moving one cell/segment from the failed PCU to another PCU

Difference in the PCM and BTS synchronisation.1. Analyse the bunch of alarms coming in particular Tx node. 2. Check the synchronisation settings of the transmission interface.3. If the settings are OK, check the transmission chain.

1. Check the conditions related to alarm occurs and resolve the infra related problems.2. Replace the hardware.

Check for the transmission link errors and rectify them. If problem persists than change the hardware.

1. Analyse and monitor affected RTSL by checking supplementary info. Reset if frequency is greater.2. If proplem persist, block that RTSL and shift the channel type as per needs. (e.g. SDCCH)3. The no. of block RTSL is >2, than replace TRX.

D:\userdata\alekar\Desktop\BSS Fault

BCF Alarm Guide

S. No. Problem

1 Loss of timing input

2 Ospf neighbor mtu mismatch

3 Conflicting module

4 If conn rx power too high/Low

5 Incompatible hw version

6 Incompatible sw version

7 Inventory installation error

8 No application sw

9 Cooling fans not running

10 Node clock missing

Alarm No. at Tellabs

11 Loss of IMA links

12 RX circuit down

13 IMA link RX misconnect

14 Loss of frame

15 Loss of IMA link delay synchronisation

16 Unequipped


SA

SA

SA

SA

SA

SA

SA

SA

SA

SA

The clock selection process is not receivingany proper clock signal (due to empty fallbacklist or all clocks in fallback list arefailed). Therefore holdover clock is used.

Neighbor MTU size is different than in this interface.Ospf not started.

The activated module is different from the onephysically present

SFP Received Power exceeds high alarm level setin SFP.

The unit has incompatible HW version with expectedone

This unit has incompatible SW version with referredunit.

The expected configuration is not specified. Atminimum it must contain at least one control unit

There is no downloaded software in the unit, or all softwarefiles are deactivated.

All the fans or more than one fan in the same fan group are rotating more slowly than requested, are not rotating at all, or the RPM information is not available for the fans.The reason for this fault can be too low supply voltage or a broken fan.Perform the steps below in the listed order until the alarm disappears.

Synchronization module is not feeding clock to this unit

SA

SA

SA

Loss of frame alignment SA

SA

SA

An IMA-related remote defect has been detected. A Loss of IMA link (LIF) or Link out of delay synchronisation (LODS) alarm is active at the far end of the IMA link.

Circuit is down in receive direction. The reason may be that the LDP signalling is not successfully executed.

IMA link Rx mis-connect fault. The alarm indicates that Rx link is detected to be mis-connected. This is reported when the IMA unit has determined that the Rx link is not connected to the same NE IMA unit as the other Rx links in the group.

An IMA-related remote defect has been detected. A Loss of IMA link (LIF) or Link out of delay synchronisation (LODS) alarm is active at the far end of the IMA link.

High Order Path Unequipped. The path signal label byte (C2) and the path trace byte (J1),and BIP-8 byte (B3) in the SDH path overhead (POH) all have the value zero. The path is unusable for traffic transport.Probable cause: the unequipped VC-3/VC-4 comes from a VC-level cross-connection node and the VC-3/VC-4 is not connected anywhere in that node.

Unit with newer HW version is required


Sync source to be checked. If the proper sync source is defined, then we need to check the priority setting at the source.

OSPF needs to be restarted. Topology may have to be checked.

Module needs to be activated and configuredas per the planned configured physical module

1.SFPs are to be checked.2.We may have to check for the attenuators added or not. If yes, what is the rating / value.3. Output power at the card level is to be checked.

Either the unit or referred unit SW should be upgraded

The inventory can be added by re-creating the inventory

From the management console, new sw will have to be loaded.

1.Check the fan and cabling, 2. Replace the faulty fan module.

CDC cards are to be checked. We have to JOJI the primary CDC after making the secondary card up. Card replacement should follow, if still alarms exists.

Probable causes:disturbance on the line,physical link defect,- loss of IMA frame- loss of delay synchronisation,for handling the alarms raised at the far end of the IMA link.

LDP signalling is to be checked and executed.

Delete and recreate the complete link. Check the complete path as well.

This is a transmission alarm. The frame/multi frame is not received at the far end properly. Need to check the Tx path.

Probable causes:disturbance on the line,physical link defect,- loss of IMA frame- loss of delay synchronisation,for handling the alarms raised at the far end of the IMA link.

1. Check the configuration and ensure that the cross-connections between the nodes have been properly configured for transporting traffic.2. Ensure that the Path Payload Label for the VC-3/VC-4 at the far end is configured to be"ATM".3. Follow the signal in the network and check whether any other alarms concerning the fault are active.

ttsl operations bss troubleshooting guide ver1 1 12022013

Documents

osi clns linkage

vdu lanu

incompatible

incompatible

flexi ultra

send local

related remote

2g3g multiple