+ All Categories
Home > Documents > 10.Alarm Handling of ZTE B8018 Bts

10.Alarm Handling of ZTE B8018 Bts

Date post: 11-Oct-2015
Category:
Upload: yadav-mahesh
View: 369 times
Download: 39 times
Share this document with a friend
Description:
About BTS ZTE B8018
Popular Tags:

of 45

Transcript
  • Troubleshooting

  • OMC-R OverviewOMC-R is used to manage ZXG10-BSS realize real-time O&M to BSC and BTS, perform real-time monitoring and trouble-shooting of radio network and provides friendly man-machine interface at the same time. Its easy to operate.

  • OMC-R Compositions1Security Managementto define and control the right of O&M staff, to prevent illegal operation to ensure secure subscriber access and secure service usage.Performance management: to fulfil performance measurement and traffic statistics. By formulating a series of measurement tasks and collecting all kinds of system specifications and data, find potential problems of the system in advance.

  • OMC-R Compositions(2)Configuration management: to realize equipment configuration, radio resources configuration, CCS7 signaling configuration, dynamic data management and software loading, etc.Fault management: to realize centralized monitoring of BSS operation status in order to maintain and recover the system in time; to display synchronously the BSS alarms, to diagnose and test the system, in order that the maintenance staff could locate and solve the troubles as soon as possible.

  • Alarming Sources in BSS Alarming sources in BSS include:Hardware and software of single board alarmingTransmission channel alarmingExternal environment alarming

  • Alarms Collection(1)In ZXG10-BSS, each board is designed with a module functioning alarm collecting and detecting. For boards that can be operated and maintained directly, FUC, CKU an BIE in BTS, TC, DSN and GPP in BSC, for example, they have their own alarm-reporting software module.

  • Alarms Collection(2)For boards without CPUs, for example, HYCOM, MUL and FAN in BTS and DSNI, POWER in BSC, the alarms can be collected and reported by special modules, say EAM and MONI boards. For equipment room environmental alarm collecting, its realized by EAM for BTS and by PEPD for BSC.

  • Alarm Types and ClassificationClass 1: will seriously affect the services and security of the whole BSS.Class 2: will affect one site, some sites or the whole BSS.Class 3: will affect one carrier, some carriers,one sites or a BSC.Class 4: no affection, one channel(or carrier), or some channels (carriers).

  • Alarms Checkup and LocatingAll types of alarms of every BSS are collected and stored, according to the date, type and sources of alarm, in alarm data base of OMC-R server, for the purpose of being checked up by OMC-R terminals.The alarms are displayed in graphics, reflecting directly the current alarming situation of every network element. The most important alarms, say the longest-lasting and the most frequently-occurring, are summed up.

  • Automatic and Artificial Recovery of AlarmsSome alarms, not reporting within given time, communication link break, for example, will recover within a period of time. After recovering, the alarming will disappear in the background server but the recovering time and alarming time is still stored in alarm database for convenience of checking alarming history and equipment maintenance.Some alarms that are unable to recover after a long time need mans recovery.

  • BSC Alarms and Handling

  • MP AlarmLevel2CauseBackup MP fault, power-down, not-installed, software fault and Watchdog overflow.Effect: decrease system operating reliability. If the active MP is in trouble, itll not able to switch to stand-by MP.Processing: power up MP or reset it.

  • Disk AlarmLevel: 2Cause: MPs disk space is insufficientEffect: Affect system software operating. Processing: Deleting useless files in MP to release disk space using File Management Tool of OMC-R. The space should be remain at least one-fifth of the total space.

  • MP Bus AlarmLevel1Cause: the buses between MP and SMEM and all COMM boards is in trouble.Effect: BSC will not operate normally. The system or boards will be locked out and data transmission disordered.

  • DSN AlarmLevel2Causehardware, software and clock interface trouble.Effect: DSN usually operates in stand-by mode. Generally, this will not affect system operation.Processing: check HW cable connection between control layer and switching layer and reset.

  • SYCK Severe Alarm Level1Cause: troubles in 8K frame head, 8K output clock, 16M frame head and 16M output clock.Effect: unstable communication inside BSC, concurring with other many alarmings.

  • ProcessingIf only active board has alarm, then swap from active to stand-by board and activate it.If both active and stand-by boards have alarms, they should be displaced at once.

  • Ordinary SYCK Alarm Level3CauseClock aging.Effect: Occasional code slippery , bit error, asynchronous framing, CCS7 link and LAPD link. In general, however, this wouldnt affect normal operation of system.Processing: displace the active with standby board.

  • DSNI AlarmLevel: 2Cause: communication break with MP, not inserted well or out of slot.Effect: boards connected with it will have troubles in communication transmission.Processing: if the troubled is active board, then swap it to standby one; if its standby, displace it as soon as possible with a good one.

  • Power Board AlarmLevel2Cause: Over-voltage or Under-voltage.Effect: will severely affect longevity of all kinds of boards and make them unable to work properly when in worst condition.Processing: displace troubled power board as soon as possible.

  • MPPP AlarmLevel2Cause: communication break between MPPP and MP, power drop and clock lost etc.Effect: MPPP operates in the mode of load-sharing. One MPPPs trouble wont affect normal system operation, but the system reliability. If both MPPPs are in trouble, the links between MP and PP will break, causing PP boards out of control.Processing: check power, connection, clock.

  • MTP Alarm

    Level: 3Cause: communication break between MTP and MP, power drop and clock lost etc.Effect: the same as that of MPPP. It will also cause communication link break between BSC and MSC.Processing: the same as that of MPPP.

  • MONI AlarmLevel: 3Cause: link with MP is broken, power down, clock is lost and hardware fault.Effect: unable to monitor the boards connecting to it, power, clock and DSNI, for example.Processing: the same as MTP.

  • SMEM AlarmLevel: 2Cause: the same as MONI except that the link is between SMEM and MP.Effect: communication between active and standby MPs is broken.Processing : the same as MONI.

  • PEPD AlarmLevel: 2Cause: link between PEPD and MP is broken, power-down, hardware trouble and clock lost.Effect: unable to monitor temperature, humidity and smog etc., of the equipment room.

  • LAPD Alarm

    Level: 2Cause: link between LAPD and MP is broken, power-down, hardware trouble and clock lost.Effect: LAPD communication link and links with relevant sites are broken.Processing: the same as above.

  • TIC Alarm

    Level: 2Cause: link between TIC and MP is broken, power-down, hardware trouble and clock lost.Effect: the BTS it connects with is unable to operate normally.Processing: check the cable connecting to DSNI, clock or resetting.

  • DRT AlarmLevel: 2Cause: link between DRT and MP is broken, power-down, hardware trouble and clock lost.Effect: the TC unit it connects to will not operate normally. If there is No.7 link in it, the communication between BSC and MSC will be affected.Processing: the same as TIC

  • BTS ALARMS

  • PA Link Broken

    Level: 4Cause: corresponding TRU power-off, off-line or fault; OMU power-off, off-line or fault.Effect: affect O&M of PAProcessing: check OMU, TRU(especially CUI) and backplane O&M cable.

  • VSWR of PA AlarmLevel: 3Cause: backward power over-high due to open end output of PA or high resistance.Effect: TRU out of operation or PA damaged.Processing: check PA output and see if the cable connection is fastened.

  • VSWR of Combiner AlarmLevel: 2Cause: combiner output open-ended, high resistance or interference is received by EAM.Effect: PA is closed for protection, making the corresponding cell wont operate normally.Processing:check EAM and connectors involved.

  • OMU AlarmContent: OMU communication link broken.Level: 2Cause: broken link between OMU and BSC. OMU Fault, BTS power-off , faults on LAPD, TIC and DSN boards in BSC.Effect: O&M to BTS is affected (broken)Processing: check all the boards concerned and E1 line and LAPD time slots allocation.

  • BIE Link BrokenContent: BIE communication brokenLevel: 3Cause: HDLC link between OMU and BIE is brokenEffect: data transmission between BIE and OMU is unable to conduct, data configuration to BIE and its status reporting is unable to fulfil.

  • CKU Link Broken

    Level: 3Cause: the HDLC link between OMU and CKU is brokenEffect: data transmission between CKU and OMU is unable to conduct, data configuration to CKU and its status reporting is unable to fulfil.Processing: check if the board is well inserted, reset it or displace it.

  • EAM Link BrokenLevel: 3Cause: the HDLC link between OMU and EAM is brokenEffect: the same as that of CKUProcessing: check if the board is well inserted, if the clock is good, reset it or displace it.

  • Examples of Troubleshooting

  • No.7 Signaling not Successful when connected with MSCCheck if MTP board is flashing fast. Check if data configuration of No.7 signaling link is correct. Are SPCs on both sides correct? Is SLC coding the same?Is Frame format the same?

  • E1 Slippery(1)Interface board problem: check TICs(BIU&AIU)Re-plug E1 cable or the whole board, or replace board.2Synchronization problem: may exist between MSC-BSC or BSC-BTS.If MSC is unable to synchronize with PSTN, SYCK and CKI board replacing is strongly suggested.

  • Alarm Collection

    BTS BSC

    MP

    MP

    At BUS

    Comm

    (LAPD)

    (

    Comm

    (LAPD)

    COMI

    TIC

    Abis

    LAPD

    LAPD

    B

    I

    E

    OMU

    FU0

    FU5

    LAPD

    LAPD

    LAPD

    RMU

  • LAPD Link Fault(1)If the whole BTSs LAPD link is broken:Check the cable between TIC and (E)BIE boardsExchange the INPUT and OUTPUT end and see if LAPD is OK.Use service phone to test the E1 cable Check data configurationCheck if there is any alarm on TIC and BIE boardCheck BTS backplane connections,especially connection between BIE and FU

  • LAPD Link Fault(2)If alarm occurs on a single LAPD board Check BTS backplane connectionCheck if there is clock alarmCheck OMC-R data configurationObserve LAPD status using Dynamic Data ManagementReset the board

  • Low SDCCH Assignment Success RateAdjust RACH parameter, that is, the interval between two random access requests

  • BTS Alarm Collection

  • HDLC Link BrokenAll boards of HDLC links brokenCheck if CKU has provided good 4MHz and 8KHz clocksSingle board of HDLC link brokenCheck if this board is well-pluggedReplace this board


Recommended