You are on page 1of 7

Internal Use Only ZXG10 B8018 - ON and OFF HDLC communication link broken alarm on Awassa_Tele_D site

ZXG10 B8018/GUBS/GU-SYS/GU Network Management Version Equipment Software Version Board Software Version

Product

Equipment Hardware Version Board Hardware Version Incident Error Code Author ChenXiaoPing

Page Views Knowledge No.

Incident Description (Incident Phenomena) Cell one TX1,TX2,TX3,and TX4 has got on and off HDLC communication link link broken alarm on 2 dtru Networking Environment

Problem Cause Analysis NULL Solution 1- Checking the alarm on the site, and it happens no alarm on the physical boards to the contrary it handles traffic 2- DTRUD boards are changed

3- Still the problem exist we have changed 3 times suspecting the new boards have some problem but not. 4- Checking the performance of that cell and the performance is not satisfactory
5- Inform Optimization Engineer to test 6- And found out 3 TRX has got serious problem and check physically

7- Then checked the physical cabling and found the 3 TRX are connected to the same CDU 8- After CDUD changed and waited to the test result 9- And found out that the problem was resolved.

<> All Rights reserved, No Spreading abroad without Permission of ZTE

Internal Use Only ZXG10 B8018-BS-SYS/GU-BS-BSC-SYS/GU-BS-SYS/GU-How to handle the two cells down and one cell have unstable alarm on OMCR on 8018 site type
ZXG10 B8018/GUBS/GU-SYS/GU Network Management Version Equipment Software Version Board Software Version HDLC communication Incident Error Code link between CMB and FUC broken (16784222) ,8018,iBSC Author Knowledge No. WHH2012081679115 3 Page Views 30

Product

Equipment Hardware Version Board Hardware Version

V6.20.614 iOMCR-V6.20.614

Incident Description (Incident Phenomena)

<> All Rights reserved, No Spreading abroad without Permission of ZTE

Internal Use Only


The customer said site X on one island network have the cell interruption alarm on cell 2 ,3, unstable HDLC communication link between CMB and FUC broken (16784222) alarm on cell 1 and also have the unstable cell interruption alarm.

Those two unstable alarm cause the customer can't have a successful call during the coverage, and the unstable alarm caused the many history alarm on OMCR. Therefore, the customer ask for solve this issue as soon as possible.

Networking Environment

<> All Rights reserved, No Spreading abroad without Permission of ZTE

Internal Use Only


One iBSC and the site X is the S222 on this Network.

Problem Cause Analysis This alarm is due to the HDLC link between CMB and TPU breaks, or CMB hardware has error ,etc. Need to check from the following: 1.Check whether DTRU is plugged tightly and properly .Re-plug DTRU module, addDTRU incorresponding position according to the configuration, and check whether the alarm is recovered.

2.Reset DTRU board to check whether the alarm is recovered.

3.If alarms occur in all the cells,check whether CMB board works normally .Re-plug CMB to check whether the alarm is recovered.

4.Check whether the address switch on the backboard is correct. If not,adjust the switch to correct position, and check whether the alarm is recovered.

5.Check whether the transmission line of the rear board is connected correctly .Otherwise connect the line to correct position and check whether th ealarm is recovered.

Solution

<> All Rights reserved, No Spreading abroad without Permission of ZTE

Internal Use Only


1.Check the hardware of CMB, BOBTR(CMB backboard). The onsite engineer to unplug and replug the CMB board, the alarm didn't have any change, then change a new brand of CMB and BOBTR, the same alarms.

2.Check the hardware of DTRU and BBTR (DTRU backboard). (1) Have a cross test on each shelf, use the normal running DTRU to change the orginal one on each shelf, but the alarm didn't change. (2) Unplug the BBTR, check the bent pin didn't have any bent pin so we suspose to use a new one to have a test. The alarm still on it after change a new brang BBTR on each shelf

<> All Rights reserved, No Spreading abroad without Permission of ZTE

Internal Use Only

3. Check the S1 configuration on BBTR backboard and S1 &S2 configuration on ID_PORT on top cabinet. After rule out the possible issue from the hardware, I suspose the unstable alarm due to the configuration on switch. Suggest the onsite engineer to set the following configuration on BBTR and ID_PORT: (1) S1 configuration on BBTR on each shelf: ON ON OFF ON shelf 3 ON OFF ON ON shelf 2

<> All Rights reserved, No Spreading abroad without Permission of ZTE

Internal Use Only


OFF ON ON ON shelf 1 (2)S1 & S1 configuration on Top cabinet: (Just have one rack on this site) S1 00000000 S2 00000011 The alarm disappear after onsite engineer to check the S1 configuration on BBTR , found didn't set any value on each shelf, then set the above value then found the alarm disappear.

In a word, we can rule out the hardware issue first then check the another possible reason, so that it's easy to found the root reason.

Summary and Notes

<> All Rights reserved, No Spreading abroad without Permission of ZTE