zxg10 b8018 hdlc alarm troubleshooting

4
ZXG10 B8018-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 Product ZXG10 B8018/GU-BS/GU-SYS/GU Network Management Version Equipment Hardware Version V6.20.614 iOMCR--V6.20.614 Equipment Software Version Board Hardware Version Board Software Version Incident Error Code HDLC communication link between CMB and FUC broken (16784222) ,8018,iBSC Page Views 15 Author 谭亚Knowledge No. WHH20121008446938 Incident Description (Incident Phenomena) 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.

Upload: tongaimutengwa5194

Post on 08-Sep-2015

219 views

Category:

Documents


1 download

DESCRIPTION

Troubleshooting

TRANSCRIPT

  • ZXG10 B8018-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 Product ZXG10 B8018/GU-BS/GU-SYS/GU

    Network Management Version Equipment Hardware Version V6.20.614 iOMCR--V6.20.614

    Equipment Software Version Board Hardware Version Board Software Version Incident Error

    Code HDLC communication link between CMB and FUC broken (16784222) ,8018,iBSC Page

    Views 15 Author Knowledge No. WHH20121008446938 Incident Description (Incident Phenomena)

    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 One iBSC, S222 site. Problem Cause Analysis HDLC link

    between CMB and TPU breaks, or CMB hardware has error, etc will caused HDLC

    communication link between CMB and FUC broken (16784222). Solution

    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

  • 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

  • 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