How to find dip of a Site

1)RLCRP:cell=<cell name>; 2)Rxtcp:moty=rxotg,cell=<cell name>; get TG value from here 3)rxapp;mo=rxotg-xx; get devices like ralt-220 or ralt2-220; 4)radep:dev=<dev>; get the snt 5)ntcop:snt=xx; get the dip name corresponding to the devices and SNT. OR give DTDIP:snt=<Snt Name>; 6)dtstp:dip=<dip name>,state=abl; 7)dtstp:dip=<dip name>,state=mbl; Check if the dip has gone down.If dip comes WO go for different analysis.

Superiority ORDER of MOs in descending order: TG most superior CF less superior IS TF CON ODP TRX TX,RX TS least superior You can check each MO by commande RXMSP. IF the superior BLA BLO LMO values shoud be 00000000000000 for an MO to be concluded as working fine. Check: RLSTP:cell=<cell name>; Its state should be active; Check the MOs 1)Rxasp:mo=rxotg-xx; follow the next steps for the MOs that are shown in this. 2)rxmfp:mo=rxotrx-xx; & rxmfp:mo=rxocf-xx; If any fault codes comes in rxmfpcheck it from the RBS fault decoder 3)rxmsp:mo=rxotrx-xx ; or TX or CF If CF shows LMO h0040 or TRX shows LMO H0440 the its in local mode. Ask the person at site to give reset on the MO manually i.e to bring it in REMOTE mode. If the MOs shows some other LMO values like TS shows LMO H0840 and TX H0040 then do:

RXBLI:MO=RXOTRX-xx-yy; or Cf or TX or TS RXTEI:mo=rxotrx-xx-yy; RXBLE:mo=RXO..-xx-yy; OR Rlstc:cell=<cell name>,state=halted,chgr=all; If all TRUs are not working if not then, Rlstc:cell=<cell name>,state=halted,chgr=1; Rlstc:cell=<cell name>,state=halted,chgr=2; Wait for 3-4 minutes. Rlstc:cell=<cell name>,state=active,chgr=0; Rlstc:cell=<cell name>,state=active,chgr=1; Rlstc:cell=<cell name>,state=active,chgr=2;

Health Check & Trouble shooting of BTS

Introduction
This document is to be used as a guideline for the trouble shooting and Operation & Maintenance of BTS related problem. This document is also provide the guideline, in case of escalating the customer service request (CSR) to ELS/GSDC.

Scope
This document is to be used as a counsels for the trouble shooting of BTS related problem. It also incorporates few most common problems related to a BTS site. The document also provides Operation and Maintenance procedures and recommends improvements to reduce down time of BTS equipment as well as the guidelines for escalating the case to ELS. The overall aim is to help the Customers to establish the maintenance routines and procedures, with the assistance from Ericsson O&M personnel. This document however does note override the O&M Manuals which should always be referred for fault finding. This document is mostly based on experience from field and has wider scope of modification.

shooting

Common BTS problem & its trouble

1. CF Loading failed (Site/cell is not coming up)

This is the most common problem of BTS /Site/cell. There can be many reasons of CF loading failed, which are as follows:

1. PCM Quality & Proper connection The PCM quality and proper connection is the most crucial factor of CF loading. We need to check PCM quality , Abis definition, SNT & RBLT devices and proper IDB definition of PCM. It has been seen many time that the DTQUP or DTQDP is not enough to check the PCM quality , sometimes we need to check the up to BER level. Action: 1. Check the BER using BER tester. 2. Try to arrange a new PCM . 3. If possible, swap the problematic PCM with any working site PCM.

2. Insufficient number of TRH TRH (RHSNT) must be properly dimensioned, as it is also an important cause of CF or TRX or TS not coming up. It is really difficult to give exact number of TRX handled by one RHSNT as it depend upon traffic pattern like High Traffic intensity, Many Measurement Reports, Extensive paging, various featured used etc. But based on our experience,roughly it can be calculated as below RPD : 7-8 TRX/Per RHSNT

RPG 2 : 17-18 TRX/Per RHSNT RPG 3 : 24 TRX/RHSNT

Action: Dimensioned the RHSNT as per the guidelines & recommendation of Technical Manager

3.

BTS Software Many a times BTS software lying in BTS gets corrupted or software version is lower then required one. Action: Load a fresh BTS software from BSC. RXMSC:MO=RXOTG-<tg>,SWVER=<sw-name>; RXPLI:MO=RXOTG-<tg>,UC;

4. Corruption in IDB IDB can be corrupt during PCM fluctuation etc, a fresh IDB need to be loaded. Action : Load the fresh IDB using OMT software

5. BSC Parameter Mismatch BSC parameters like BSSWANTED & BSSRELEASE can also the cause CF loaing failed. There must me proper value for these parameters. Action: Change the value of above parameters as per the BSC release. The value of BSSWANTED gets change automatically as per the BSC release, but we need to confirm it.

6. TG Hanging The hanging of particular TG can also be the of CF loading failed. we need to clear the hanging for making CF loading successful. Action:

Print the TGFID using RXMOP of perticular TG. RXMOP:MO=RXOTG-X; Using command SYFIP, check the block and individual connected to any active FORLOPP SYFIP: FID=H YYYY-HZZZZ; Release the FORLOPP using command SYFRI SYFRI:FID=fid, BLOCK=blockname,FILENUM=filenum,IND=ind;

7. Wrong TEI value There must be correct TEI value for CF, especially when it is cascaded. Action: TEI value should be start from 62, in case of cascading it 62 then 61, 60 and so on. 8. Hardware problem In case when all the above mentioned step is not giving the success, we can very well suspect the hardware fault which is most likely DXU. Action: Change the DXU. 9. Wrong cable connection of Group switch It can also be due to wrong connection between SNT and group switch. Action: Need to check the exchange DT & cable connection thoroughly. This is something which need a higher level of investigation. .

2. TRX is/are not coming up

The most common reason for TRX not coming up are as follows: 10. Insufficient RHDEV devices As mentioned in the point 3..1.2 ,RHSNT (Device name is RHDEV) must be properly dimensioned, as it is also an important cause of CF or TRX or TS not coming up. Action: Check whether TRX is picking up the RHDEV device or not. RXMDP:MO=RXOTRX-X-Y;

11. Insufficient RBLT devices One PCM can not handle more than 15 TRU , its handling capacity depend upon the type of LAPD signalling used. Unconcentrate: 10 TRU/PCM Concentrate Multiplexing Action: Check the RBLT devices. RXAPP:MO=RXOTG-X; : 13 TRU/PCM : 15 TRU/PCM

12. Wrong DCP values for RXOTRX DCP value of TRX must be as below:

TEI=0, DCP1=128, DCP2=129,130 TEI=1, DCP1=131, DCP2=132,133 .

. TEI=5, DCP1=143 DCP2=144,145 TEI=6, DCP1=160, DCP2=161,162 . . TEI=11, DCP1=175, DCP2=176,177 Action: Check the DCP value of TEI 6, this is where we do mistake.

13. Hanging in RBLT devices Action: BLODI: dev=x; EXDAE:dev=x; EXDAI:dev=x; BLODE:dec=x; 14. Faulty TRU Action: Change the faulty TRU 15. High VSWR

Action:
Check the value of VSWR using VSWR tester. Identify the problematic jumper or feeder cable or connector and replace it.

16. Insufficient BPC in command RLBDP RLBDP:cell=cellname;

Action: RLBDC is the command where you define the NOREQBPC, it should be either SYSDEF or 8*No. of TRX.

17. High temperature Check the alarm for High temperature. Action: Find out the reason for this high temperature.

18. Wrong power definition for RXOTX RXMOP:MO=RXOTX-X; Action:

Define the power parameter as per the RND recommendations.

. 19. Incorrect MO definition Action: Check the MO definition thoroughly.

3. Loop Test Failed/ TS SYNC fault

The most common reason for Loop test failed/TS sync fault are as follows:

20. PCM Quality Action: This is the most important one, we need to take the action as mentioned in point 3.1.1

21. Wrong SNT definition/Connection Action: Need to check the SNT definition and cable connection thoroughly.

22. Hanging in TRA/RBLT devices Action: We need to take the action as mentioned in point 3.2.4

23. Faulty TRU Action: Change the faulty TRU

24. Incorrect MO definition Action: Check the MO definition.

25. Insufficient RHDEV devices Action: We need to take the action as mentioned in point 3.2.1

26. Insufficient RBLT devices We need to take the action as mentioned in point 3.2.2

27.

TRA software problem Action:

This is something which need a higher level of investigation.

4. RXOIS not coming up

The most common reason for TRX not coming up are as follows 28. PCM quality Action: This is the most important one, we need to take the action as mentioned in point 3.1.1

29. Wrong DCP for TRX Action: We need to take the action as mentioned in point 3.2.3

30. Low Voltage at site Action: Need to check the voltage level at BTS site.

5. RXOTF not coming up/Not config.

The most common reason for TF not coming up are as follows

31. PCM Quality Action: This is the most important one, we need to take the action as mentioned in point 3.1.1

32. DXU faulty Action:

We need to take the action as mentioned in point 3.1.8

33. Wrong value of BSC parameter Action: We need to take the action as mentioned in point 3.1.5

34. BSC clock control values Action: Check the clock control value & group switch status. AXE 501: GSSTP; GSCVP; AXE 810: GDSTP; GDCVP; values must be ~32000+/-2000 values must be ~1800+/- 400

Regular Maintenance Routines

6. Daily Maintenance Routines

35. Maintenance from BTS Whenever visiting a BTS site, check the following points to ensure that everything is in order: Check for BS fault in the DXU or fault in BFU or any other fault indicating alarms or that attention is required. No visual damage to the equipment or site room is evident.

 Climate control i.e. air conditioners are functioning correctly. The air inlet to the cabinet is clean. Check for any surrounding activities or changes close to the site that may affect the performance of the system or safety of the equipment. Indoor light is working. Indoor emergency light is working. Check back-up batteries for corrosion and leakage. In addition, make sure that any other local routines are checked. If a power generator is used as a mains back-up source, check the run time and compare it with the manufacturers recommended service interval regarding the run time and regular service.

36.

Maintenance from BSC. Since the BTS is controlled and supervised by the BSC, a number of operation and maintenance tasks regarding the BTS involve working with the BSC.

The first step in maintenance is always to recognise the fault and to trace it to a specific unit. To obtain a list of the faults in the base station, command ALLIP can be used. It will print out all faults registered in the BSC and base station. Other commands for BTS maintenance are RXMFP and RXELP. Transceiver Group Commands: Transceiver group commands belongs to the RX...command group. The most important RX...command is RXMSP used to print out the state of Managed Object units within the transceiver group.
For the unit(s) specified, a global state is given (UNDEF, DEF,COM, PREOPER, OPER ,NOOPER or FAIL). A blocked object can be given three different blocking statuses BLO, BLA

or LMO. There is a bitmap associated with each bit map specifying the exact blocking reasons.

RXMFP prints a list of currently faulty Managed Object units, which is updated whenever an error is cleared. RXELP is a log-book, preserving one entry for every fault, even if the fault has been cleared. RXELP printouts are suitable for statistical analysis, since the entries indicate date and time and the detection of faults Example: RXMFP:MO=RXOTG-0; (Managed Object Transceiver Group, Print) RXELP:MO=RXOTG-0; (Error Log Transceiver Group, Print)

7. Weekly Maintenance routines

The following information should be collected and analysis to find out the possible cause of the same. Collect the STS reports and check if there is any abnormality pattern in the network . Major disturbances Other matters ( Dropped calls, traffic, ... )

Evaluation of PCM

8. Monthly Maintenance Routines

37. Drive Test Network drive tests should be performed if necessary whenever a new BTS is integrated with the BSC, in cooperation with the Radio network design department. 38. Cell Data check A printout of all cell data should be made once in every month and a check for false data should be carried out.

9. Three-Monthly Maintenance Routines

At a three month maintenance interval, the following should be checked in addition to the regular check-up. Check RBS rack door filters and replace if necessary. Carry out battery back-up voltage test, to ascertain whether the batteries are holding their full charge. Check the site temperature and humidity, see O&M manual.

Customer Service Request routines

10. TR escalation path
CSR: PLM CSR answer Customer Customer PLM GSDC ELS GSDC ELS

11. Data collections for CSR.

BSC version, i.e.: CME level, AC-A level, added corrections (ACs and ECs), type of dump (GSM, mixed) BSC log of commands entered at time of the fault BSC printouts on all appropriate MOs in faulty TGs: RXELP, RXTCP, RXMOP, RXMSP, RXMDP, RXMFP, RXCDP, RXHDP

BSC printouts on faulty cells: RLDEP, RLCRP, RLCPP, RLSSP, RLCFP, RLDGP OMT logs from DXU, TRU, ECU (taken at time of fault)

PCM quality details