ZXSDR Node B Troubleshooting-89

download ZXSDR Node B Troubleshooting-89

of 85

Transcript of ZXSDR Node B Troubleshooting-89

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    1/85

    ZXSDR Node BTroubleshooting

    ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Par,Nanshan !istrict, Shenzhen,P" R" China#$%'Tel( )%*+ '## *''$&& %&&-%.&-%.&/a0( )%*+ '## *''.*1R2(htt3(44su33ort"zte"co5"cnE-5ail( doc6zte"co5"cn

    http://support.zte.com.cn/http://support.zte.com.cn/mailto:[email protected]:[email protected]://support.zte.com.cn/
  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    2/85

    Contents

    Chapter 1.................................................................1

    Maintenance Overview..............................................1

    Maintenance Description...................................................1

    Maintenance Requirements.....................................................1

    Maintenance Principles......................................................1

    Right Management................................................................1

    Data Observation..................................................................2

    Data Modification..................................................................3

    Data Snchroni!ation.............................................................3

    Man"machine #ommands.......................................................3

    $oard Operations..................................................................%

    &pdate................................................................................ %

    Maintenance #lassification.................................................'(nalsis Methods.............................................................'

    )ndicator Status (nalsis........................................................'

    Signaling *racing (nalsis.......................................................+

    (larm ,ogs (nalsis...............................................................+

    Replacement (nalsis............................................................-

    Precautions.....................................................................

    Personnel /ualifications.........................................................

    Maintenance Management....................................................10

    Data Maintenance................................................................10

    quipment Room nvironment...............................................10

    *ools and )nstrumentsMeters...............................................11

    Spare Materials and Parts.....................................................11

    *echnical Documents............................................................11

    *echnical Support................................................................11

    Chapter 2................................................................13

    Routine Maintenance...............................................13

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    3/85

    Overvie....................................................................... 13

    Dail Routine Maintenance )tems......................................1%

    4ee5l Routine Maintenance )tems...................................1%

    Monthl Routine Maintenance )tems..................................1'

    Semiannual Routine Maintenance )tems............................1+

    Other Recommended Maintenance )tems...........................16

    Chapter 3................................................................21

    Notification and Handling.........................................21

    7otification Messages......................................................21

    $oard 7otification...........................................................21

    SS#OP rror.......................................................................21

    (,#(P ,in5 rror.................................................................21

    ((,'8M(# rror..................................................................22

    RS232 Serial Port rror........................................................22

    S*M"1 $1 rror #ode...........................................................22

    S*M"1 $2 rror #ode...........................................................23

    S*M"1 Remote $2 rror #ode )ndication.................................23

    9amples of Other Maintenance )tems S*M"1 $3 rror #ode......23

    S*M"1 $3 Remote rror #ode )ndication.................................2%

    S*M"1 Multiple9 Section Remote Defect )ndication :MSRD);.......2%

    S*M"1

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    4/85

    Softare =ersion rror.........................................................31

    Softare Operation >ailure....................................................31

    $oard Parameter Snchroni!ation (bnormal............................31

    (pplication Softare Monitoring (larm....................................32

    Database Save >ailure..........................................................32

    Reference Resource PR) #onfiguration >ailure..........................32

    SS#OP Deliver $uffer Overflo............................................33

    $oard #onfiguration rror (larm............................................33

    S7*P *ime (lignment >ailure (larm........................................33

    #loc5 Reference Source Deterioration.....................................3%

    #P& Overload (larm.............................................................3%

    $oard

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    5/85

    #onfiguring *# Port >ailure....................................................%%

    #onfiguring P=# >ailure........................................................%'

    #P& Overload (larm.............................................................%'

    $oard ailure....................................................'+

    $oard #onfiguration Parameter rror......................................'6

    #P& Overload (larm.............................................................'6

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    6/85

    $oard

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    7/85

    Poer (mplifier Output Poer Protection.................................6+

    ,ightning Stri5e...................................................................6+

    Chapter 7................................................................77

    #er%.....................................................................77

    Appendi' A.............................................................7)

    A$$reviation%..........................................................7)

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    8/85

    C h a p t e r 1

    Maintenance Overview

    *his chapter introduces common maintenance tpesB

    maintenance principles and analsis methods and providesprecautions for routine maintenance.

    Maintenance Description

    Maintenance Requirements

    Maintenance personnel must receive sstematic training to bequalified in sstem maintenanceB master fundamentals of @4R$0B and 5no overall structure and functions of each boardB in

    addition to some 5noledge about netor5 optimi!ation andnetor5 maintenance.

    Maintenance Principles*his section introduces hat maintenance personnel must paattention to in @4R $0 maintenance. (n operation against

    folloing principles ma have a negative impact on sstemoperation.

    Right Management

    (ssign personnel"specific usernames and passords for sstemloginB operation and maintenanceB to restrict operation rights ofmaintenance individuals and find operation histor throughsstem logs in case of sstem malfunction.

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 1

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    9/85

    @SDR 7ode $ *roubleshooting

    Different users are able to perform different groups ofoperationsB depending on their levels and rights. Operation andmaintenance softare classifies operators into four levelsB rootuserB advanced userB medium"level userB and ordinar user in

    descending order of rights.1. Root userB ith highest level of rightB can perform an

    operationsB including creating usersB modifing userinformationB deleting usersB setting rights and modifingsstem configuration. #hange initial passord of root userimmediatel after logging in to the sstemB for securit ofthe sstem

    2. (dvanced user has the same rights as a root userB e9ceptthat it cannot manage user accountsB adddelete boards andadddelete local cells.

    3. Medium"level userB ith basic vieing rightB can vie alarm

    and sstem information. )n additionB a medium"level usercan onl perform limited tpes of configuration operations.

    %. Ordinar userB ith loest rightB can onl vie informationrather than perform an configuration operation.

    Caution

    &se right management function to set ordinar equipmentmaintenance personnel as medium"level users.

    Do not log into the sstem as root user unless absolutelnecessar.

    Do not change netor5 settings of 7MS server and #lient.

    Do not run and operate an other programs not related tooperation and maintenance on 7MS server or #lient.

    >ollo general principles of netor5 management to guardagainst an virus.

    Data Observation

    Caution

    Perform data observation operations carefull ith largequantities of data to reportB including signaling tracingBrunning information observationB all users of service

    observationB and alarm refreshing. 9cessive data reportduring data observation ma cause sstem brea5don ine9treme cases.

    Caution

    Select appropriate time :lo traffic period; for data

    observation operationB ta5e appropriate measuresB saveresults in time and clean temporar data in time.

    2 #onfidential and Proprietar )nformation of * #ORPOR(*)O7

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    10/85

    #hapter 1 Maintenance Overvie

    Data Modification

    Caution

    *a5e care in modifing dataB particularl ireless data.

    Observe carefull hether there is an effect on sstemoperation after modifing data.

    Caution

    $e sure to perform bac5up before modifing an dataB toensure rapid restoration hen an problem occurs.

    Do not perform data snchroni!ation at rush hours :at 10 (M

    or ' PMB *ime varies from place to place;.

    Do not modif foreground database during datime.

    Data Synchronization

    Caution

    $e sure to bac5up data before modifing configuration.

    Caution Do not perform data snchroni!ation in datime unless

    necessar.

    #hec5 operation log to identif the source if finding an dataof an un5non source.

    Man-machine Commands

    Caution

    $e careful in using commands that lead to foregroundactionsB including restartB resetB changeoverB saveB hardaretestB softare donload and cell bloc5unbloc5.

    Do not delete current alarms and histor alarms unlessabsolutel necessar.

    $e sure to loc5 bac5ground man"machine interface aftermaintenance personnel leave operation and maintenanceconsoleB to avoid an accidents.

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 3

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    11/85

    @SDR 7ode $ *roubleshooting

    oard Operations

    Caution

    Do not reset a boardB plugunplug it or poer it off unlessabsolutel necessar.

    Prepare spare board before replacing a board. Ma5e surethere are sufficient technicians present for une9pected

    emergencies in the case of maEor operationsB such aschanging versions of important boardsB or pluggingB

    unplugging and replacing 5e boards. Maintenance personnelor5ing on boards in the foreground must have support frombac5ground personnel.

    Caution*

    (las ear an antistatic rist strap before operating boards

    on the rac5 and connect it to the rac5 before touching aboard.

    *ouch a metal obEect first to release static electricit onhands.

    Reduce poer graduall :to change users in conversation orin netor5 access and to prevent users off"conversation fromaccessing; hen replacing ,P( :,inear Poer (mplifier;.

    !pdate

    Caution

    Perform upgrade at midnight hen there is lo traffic.

    Feep contact information available for relevant personnel:li5e transmission and poer suppl; to get their timelassistance hen required.

    >ormulate upgrade plan in advanceB covering all emergencmeasures.

    Do not change procedures set forth in the planB unlessnecessar.

    )nform supervisors before upgrading for necessar technicalsupport.

    (ssign a person to closel monitor the sstem for an faultsoccurring since the upgrade.

    4 #onfidential and Proprietar )nformation of * #ORPOR(*)O7

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    12/85

    #hapter 1 Maintenance Overvie

    Maintenance ClassificationMaintenance falls into routine maintenanceB notification message

    handlingB alarm message handling and troubleshootingB bcontents.

    1. Routine maintenance

    Routine maintenance refers to chec5ing equipment running

    status periodicall. )t is to find out and handle problems intime to prevent potential damage or fault.

    2. 7otification message handling

    7otification message handling is to anal!e all 5inds ofnotifications during running of the sstemB to Eudge hetheranthing is abnormal and to ta5e appropriate measures.

    3. (larm message handling

    (larm message handling is to anal!e different alarmmessages during running of the equipmentB to Eudgeequipment running condition and to ta5e appropriate

    measures.

    %. *roubleshooting

    *roubleshooting is to anal!eB handle and remove detectedfaults.

    "nalysis Methods#ommon maintenance analsis methodsA

    (nalsis of indicator status

    (nalsis of signalling tracing

    (nalsis of alarm logs

    (nalsis through instruments and meters

    #omparison b replacement

    Others

    #ndicator Status "nalysis

    (nal!e running of a board b statuses of its indicators.

    $oards need frequent observationB for the @4R $0B areAcontrol cloc5 sitching board ##SB )ub"(*M interface board ))(B

    baseband processing board $P and transceiver unit *R@&.

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 5

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    13/85

    @SDR 7ode $ *roubleshooting

    Signaling $racing "nalysis

    Signaling tracing analsis is to chec5 hether signaling flo is

    correct. (ll services have their on signaling flos. )t isacceptable to diagnose sstem problems according to e9perienceb vieing differences beteen current flo and correct floBhen a service is abnormal.

    )mportant or5floB for the @4R $0B includesA cell setupBcommon transmission channel setupB pagingB random accessBsstem information update and ireless lin5 setup.

    "larm %ogs "nalysis

    (larm log analsis is to quer histor alarms and current alarmsof the sstem at 7M interfaceB and to anal!e and determinerunning status of the equipment. )nstruments and Meters

    (nalsis

    #ommonl"used instruments and meters in routine maintenanceinclude signaling metersB line testers and poer meters.

    Signaling Meter "nalysis

    Signaling meter is to monitor signaling interaction beteen 7ode

    $ and R7# in real time. >igure 1shos the connection mode ofsignaling meter ith the equipment.

    6 #onfidential and Proprietar )nformation of * #ORPOR(*)O7

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    14/85

    #hapter 1 Maintenance Overvie

    ! " # R $ 1 %& & ' ! C%T ! O N O S ! " N%' ' ! N" M$ T $ R %T RNS

    R7#

    R7#

    7ode $

    7ode $

    ,aptop computer

    1

    2

    .0G

    100G

    10G

    100G.0GOptical splitter

    Signaling meter

    10G

    R7# and 7ode $ setup several ((,' lin5s to bear (,#(PBcommon 7$(PB dedicated 7$(P and )Po( after poering on the

    equipment. )t is acceptable to quer =P) and =#) correspondingto each ((,' lin5 from OM# bac5ground man"machine interface.

    )t is also acceptable to monitor signaling of corresponding ((,'lin5 after configuring appropriate =P) and =#) on signaling

    meter.

    Set up appropriate =P)B =#) and #)D on signaling meterB hen

    ((,2 bears common transport channels :>(#

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    15/85

    @SDR 7ode $ *roubleshooting

    %. *o measure channel poer.

    '. *o measure scramble of the cell.

    Po&er Meter Measurement

    Poer meter is to measure output poer of *R@& and ,P( andto Eudge hether *R@& and ,P( are or5ing normall.

    Replacement "nalysis

    Replace a board module or possibl a fault connection cableith a normal board module or connection cable of same tpeBand observe hether the fault is recovered after thereplacement.

    &se the folloing replacement analsis methods to rectif faultboards or a subsstem.

    "ctive'Standby S&itchover

    *his method applies to active and standb boards configured on

    the @4R $0 rac5B such as ##S.

    Operate on bac5ground man"machine interface or press

    activestandb sitchover 5e on front panel of the board toreset the board and to trigger activestandb sitchoverfunction.

    Perform a sitchover again hen traffic is light and observehether sstem is normal if the sstem recovers afteractivestandb sitchover. #ircuit or interface of currentl activeboard ma fail if sstem is not normal. Replace it and performfurther tests.

    oard Resource loc(

    *his method applies to $P.

    $loc5B possibl a fault $P and chec5 the or5ing status of thesstem. >ault resides in $P or interface of the board if sstem

    recovers. Replace the boardB unbloc5 it and perform furthertests.

    Slot )*change

    *his method applies to $P and *R@&. *here is need to configure

    multiple $Ps and *R&@s on the @4R $0 rac5.

    8 #onfidential and Proprietar )nformation of * #ORPOR(*)O7

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    16/85

    #hapter 1 Maintenance Overvie

    9change slot of a normal board ith a possibl fault boardBand chec5 or5ing states of boards to determine hether faultresides in the board or interface of the board.

    oard Replacement

    *his method applies to M& and *R@& configured for singlecarrier and single fan. Directl replace a possibl fault boardith a ne board verified as normal.

    Cable Replacement

    #ables that easil fail include *R@& R> cableB ))( port fiber1line and rac5 fan connection line. Specific methodA

    1. #onnect R> cable of the *R@&B parts of hich are possibl

    faultB to DD, of another normal cellB and chec5 status of thecell. *R@& and related parts are normal if the cell is still

    normal. OtheriseB replace them.

    2. Remove connected optical fiber and chec5 it through self"

    loop if an optical interface of ))( is bloc5ed. *his opticalinterface is fault if self"chec5 is abnormal. #onnect the fiber

    to another available optical interface of ))( and reconfigurethe data. Replace the optical fiber or chec5 peer equipment if

    the other optical interface is found normal in self"loop test.

    Caution Do not direct optical fiber interface to eesB this ma result in

    a serious inEur.

    Do not loo5 at ))( board optical interface directlB this maresult in a serious inEur.

    )t is ver difficult to remove fans on the rac5. #hec5 poer cablefirst b connecting it to another slot or using other methodshen finding that a fan is not or5ing normall.

    Precautions

    Personnel +ualifications

    Maintenance personnel must receive pre"service training to learn

    necessar 5noledge about the equipment and related netor5Band the must follo instructions given in related manuals of the

    @4R $0 to conduct maintenance.

    Maintenance personnel must have earnest attitudes and high

    competence.

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 9

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    17/85

    @SDR 7ode $ *roubleshooting

    Maintenance Management

    Ma5e a complete set of equipment room maintenance

    regulations to standardi!e dail or5 of the maintenancepersonnel. >orbid non"maintenance management personnel toperform an maintenance operation.

    Ma5e a detailed on"dut log to provide detailed records about

    sstem runningB version statusB data changeB upgrade andproblem handling for eas analsis and troubleshooting once anfault occurs.

    Ma5e a or5 shift record to clearl define responsibilities.

    Do not pla games or access the )nternet through computerterminal. Do not installB run and cop an other softare notrelated to the sstem at the terminal. Do not use the computerterminal for other purposes.

    Set 7M passords b level. Put them under strict managementand change them periodicall so that the are onl accessible tomaintenance personnel.

    Data Maintenance

    Do not reset the equipmentB load or change an data unless

    absolutel necessar. Do not change bac5ground database at

    ill.

    $ac5up the data before ma5ing an changes. Do not deletebac5up data after changing data until observation period:usuall one ee5; e9pires and be sure that the equipment isrunning normall.

    )quipment Room )nvironment

    Maintain normal temperaturehumidit in the equipment room.Feep the environment tid and cleanB free from dust and

    moisture. Feep rodents or insects out of the equipment room.

    nsure that primar poer of the sstem is stable and reliableB

    and chec5 sstem grounding and lightning protection groundperiodicall. #hec5 lightning protection sstem to ma5e sure all

    facilities are in good conditionB especiall before storm seasonsand after thunderstorms.

    *he equipment room must have sufficient luminance compliantith relevant standards. Repair lamps damaged in time and

    ma5e sure that light reaches all around the equipment room.

    10 #onfidential and Proprietar )nformation of * #ORPOR(*)O7

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    18/85

    #hapter 1 Maintenance Overvie

    $ools and #nstruments'Meters

    (ll common"use toolsB instruments and meters must be

    available.

    )nstruments and meters must be subEect to periodic chec5ing

    and calibration to ensure function availabilit and accurac.

    Spare Materials and Parts

    #hec5 spare materials and parts regularl to ensure sufficientstoc5s and to prevent them from mold.

    Store spare materials and parts and fault ones separatel. Mar5

    them properl for eas identification.

    $echnical Documents

    Store maintenance"related application softare and technicaldocuments b categor at a specified location for eas accesshen necessar.

    $echnical Support

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    19/85

    C h a p t e r (

    Routine Maintenance

    *his chapter introduces basic contents for routine maintenance

    of the @4R $0 and lists dailB ee5lB monthl andsemiannual routine maintenance items.

    Overvie&Routine maintenance refers to periodic preventive maintenanceand chec5 on the equipment so that the equipment can run in astable state for long. Routine maintenance includesA

    1. Periodic maintenance chec5A Ma5e routine chec5 and test the

    $*S equipment runningB required functionsB importantperformance indices and hardare in compliance ithprescribed operation steps and methods through variousdesignated bac5ground operations or ith necessarinstruments and meters on regular and scheduled basis.

    2. Periodic chec5A #hec5 hardare parts of $*S equipment andits attached equipment one b one. (dEustB correct or replacean defective part promptl to ensure equipment hardare isin good condition. Regularl maintain and clean componentsith high dust"proof requirements. #lean importantcomponents of other peripherals regularl for normalrunning.

    Caution

    7ot all routine maintenance items described appl to all5inds of possible cases. )t is acceptable to refer to them andor5 out routine maintenance items according to actualsituation.

    R7# :Radio 7etor5 #ontroller;B in 4#DM( sstemB controlsall radio parametersB so folloing maintenance items do not

    include netor5 qualit analsis and statistics.

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 13

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    20/85

    Daily Routine Maintenance

    #tems*able 1 shos dail routine maintenance items of the @4R$0.

    T%B' $ 1 D%!') RO #T ! N$ M%! NT $ N%NC$ ! T $ M S

    +te ,u$-ite Content%Rear%

    (larms and

    notificationschec5

    (larmmessagehandling

    #hec5 all alarms at the

    7M terminalB and handlethem according to alarm

    level

    7otificationmessagehandling

    (nal!e notificationmessages that frequentloccur and it is acceptableto ignore common ones

    *roubleshooting

    *roubleshooting

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    21/85

    #hapter 2 Routine Maintenance

    Monthly Routine

    Maintenance #tems*able 3shos monthl routine maintenance items of @4R $0.

    T%B' $ , MO NT -' )RO #T ! N$ M%! NT $ N%NC$ !T $ M S

    +te ,u$-ite Content% Rear%

    Radioparameters

    ngineeringparameters

    #hec5 $*S locationparameters

    #hec5 antennaparameters

    &pdateparametersaccording toproEectsituation. Save

    parameters forat least toears

    7M

    B 1fiber

    and all connectors

    #hec5 $*Sequipment

    indicators

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 15

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    22/85

    @SDR 7ode $ *roubleshooting

    +te ,u$-ite Content% Rear%

    quipment

    roomenvironment

    *emperature

    and humidit

    #hec5 temperaturein the equipmentroom

    #hec5 humidit inthe equipmentroom

    Sparematerialsand parts

    Spare partschec5

    #hec5 spare partsfor boards

    #hec5 spare partsfor rac5s

    #hec5 other spareparts

    Semiannual RoutineMaintenance #tems*able % shos semiannual routine maintenance items of the@4R $0.

    T%B' $ . S$ M ! %NN#%' RO #T ! N$ M %! NT $ N%NC$ ! T $ M S

    +te ,u$-ite Content% Rear%

    ,ightninggrounding

    ,ightninggrounding

    #hec5 or5ing groundof the equipment

    #hec5 protection

    ground of theequipment room

    #hec5 groundingtrun5 line of $*S

    #hec5 lightninggrounding of thebuilding

    *est each tpe ofgrounding resistance

    #hec5 all itemsbefore and after a

    natural disaster

    (ntennafeedersstem

    )rontoer

    #hec5 toer light#hec5 structure andfoundation for andistortion or sin5ing

    #hec5 uprightness

    and height of thetoer

    #hec5 all tpes ofbolts

    #hec5 anticorrosionand rustproofmeasures

    #hec5 all itemscomprehensivelhen meetinggale force above-B earthqua5e orother naturaldisaster

    Pole #hec5 installation of

    16 #onfidential and Proprietar )nformation of * #ORPOR(*)O7

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    23/85

    #hapter 2 Routine Maintenance

    +te ,u$-ite Content% Rear%

    fi9ing parts

    #hec5 stress on thepoleB pull ire of pullire toer andground anchor

    #hec5 anticorrosion

    and rustproofmeasures

    #hec5 uprightness ofthe pole

    (ntenna

    #hec5 antennainstallation

    parameters

    #hec5 fi9ing status ofthe antenna

    #hec5 pitch angle ofthe antenna

    >eeder

    #hec5 installation offeeder and Eumper

    #hec5 feederconnectors

    #hec5 aterproof and

    airproof measures forantenna feeder

    sstem

    #hec5 grounding

    status for feeder

    #hec5 ater"droppingbend

    Other RecommendedMaintenance #temsDail Routine Maintenance )tems and Semiannual Routine

    Maintenance )tems list maintenance items closel related to the@4R $0. *here are still other maintenance items that affectthe running of the netor5 in dail operations. Refer to *able 'for e9amples and recommended maintenance periods.

    T%B' $ / $X %M & ' $ S O O T -$ R M %! NT $ N%NC$ !T $ M S

    +te ,u$-ite Content%Recoended/eriod

    $*Sequipment

    Standingave ratiotest

    *est standing averatio of each cell

    Semiannual

    quipment #leanness #lean the floorB Monthl

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 17

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    24/85

    @SDR 7ode $ *roubleshooting

    +te ,u$-ite Content%Recoended/eriod

    roomenvironment

    doorsB indosBcabinets and other

    parts

    ,ighting

    #hec5 routinelighting andemergenc lightingfacilities

    Soc5ets

    #hec5 hether (#soc5ets are

    complete and ingood condition

    Safet

    #hec5 to find outhidden safettroubles

    #hec5 fire"control

    facilities

    #hec5 protectionmeasures for theequipment

    Devices inthe

    equipmentroom

    (ir

    conditioner

    #lean outdoormachine

    #lean the air filter

    #hec5 all alarmmessages

    #hec5 installation of

    air conditioners#hec5 drainages of

    air conditioners

    Measure inputvoltage and current

    Semiannual

    nvironmentmonitoring

    sstem

    #hec5 running

    status of each tpeof sensor

    #hec5 the poerdispla.

    #hec5 the batterdispla.

    #lean chassis ofmonitoring sstem

    Monthl

    ,o"voltagepoerdistributionand sitchpoersuppl

    #hec5 hethersitch andconnector are ingood condition

    #hec5 hethersignal indicator and

    alarm are normal

    #lean poer

    distribution device

    #hec5 (# feeder

    and connection

    Monthl

    18 #onfidential and Proprietar )nformation of * #ORPOR(*)O7

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    25/85

    #hapter 2 Routine Maintenance

    +te ,u$-ite Content%Recoended/eriod

    parts

    Measuretemperature rise ofthe fuser

    $atter

    #lean batteries

    Measure voltage ofa single batter

    Measure endvoltage of each

    batter and ambienttemperature

    #hec5 hetherthere is an liquidlea5age

    #hec5 hethercontact of leadingire and terminalare ell andhether there iserosion

    #hec5 hether

    connection piecesbeteen batteries

    are tight

    /uarterl

    #apacit dischargingtest

    Hearl

    Diesel

    generator

    #harge startupbatterB and adddistilled ater hennecessar

    Semimonthl

    #lean the

    equipment

    #hec5 startupBcoolingB lubricatingand fuel sstems

    Run the machine for20 minutesB ithoutan load

    Monthl

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 19

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    26/85

    C h a p t e r ,

    Noti0ication and -andling

    *his chapter introduces tpes of notification messages that ma

    occur during running of the @4R $0B and gives possiblecauses of them.

    otification Messages4hen an unrepeatable or transient abnormalit occurs duringthe running of @4R $0B the sstem reports in the form ofnotification. Maintenance management personnel learn runningstatus of each part of 7ode $ from notification message.

    oard otification

    SSCOP )rror

    +te Content%

    Description SS#OP error

    (larm level (larm notification

    (larm tpe #ommunication alarm

    #ause SS#OP receives error PD&

    "%C"P %in( )rror

    +te Content%

    Description (,#(P lin5 error

    (larm level (larm notification

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 21

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    27/85

    +te Content%

    (larm tpe rror handling alarm

    #ause(,#(P receives invalid message or the status iserror

    ""%./M"C )rror

    +te Content%

    Description ((,'8M(# error

    (larm level (larm notification

    (larm tpe #ommunication alarm

    #ausePac5et loss or error pac5et occurs on this lin5B orthe sitching netor5 is error

    RS010 Serial Port )rror

    +te Content%

    Description RS232 serial port error

    (larm level 7otification

    (larm tpe #ommunication alarm

    #ause

    1. ?PS RS232 serial port receiving frame #R#errorI

    2. ?PS RS232 serial port sending data errorI

    3. Micro"#ontrol &nit :M#&; RS232 serial port

    receiving frame #R# errorI

    %. Micro"#ontrol &nit :M#&; RS232 serial portsending data error.

    S$M-2 2 )rror Code+te Content%

    Description S*M"1 $1 error code alarm

    (larm level (larm notification

    (larm tpe #ommunication alarm

    #ause /ualit of transmission line is deteriorated :optical

    poer is too big or too small;I there is strongelectromagnetic interference near the optical

    interfaceI optical connector is not cleanI ambient

    temperature here the equipment or5s is too

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 22

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    28/85

    #hapter 3 7otification and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    29/85

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    30/85

    #hapter 3 7otification and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    31/85

    @SDR 7ode $ *roubleshooting

    )2 %in( 5D1 Coding 6iolation

    +te Content%

    Description 1 lin5

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    32/85

    C h a p t e r .

    %lar and -andling

    *his chapter introduces tpes of alarm messages that ma occur

    during running of the @4R $0B and gives severities :levels;Bpossible causes and troubleshooting methods.

    "larm Messages(n problem or fault that occurs during running of the @4R$0 is reported in form of an alarm message.

    &suallB alarm messages last some time and do not disappear

    until corresponding problems or faults disappear.

    (larm messages fall into four levelsB level 1A #riticalB level 2AMaEorB level 3A Minor and level %A (larming.

    1. #ritical alarm

    )t is an alarm for board failure.

    >or e9ampleA related resources of a board are bloc5edBfunctions of the sstem are fatall affectedB and maintenanceand management personnel need to replace the board orperform other troubleshooting procedures to clear the fault.

    2. MaEor alarm

    )t is an alarm for a serious faultB and it ill last for sometime.

    >unctions of the sstem are seriousl affectedB ith signs ofservices being affected. >or e9ampleB /oS of a tpe ofequipment severel degradesB and maintenance andmanagement personnel need to perform emergenc repair to

    eliminate the fault.

    3. Minor alarm

    )t is an alarm for a minor fault.

    >unctions of the sstem are slightl affectedB indicatinge9istence of factors that do not affect normal services. )t is

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 27

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    33/85

    necessar to ta5e measures to prevent severe faults and tolet maintenance and management personnel eliminate thefault.

    %. (larming alarm

    )t is an alarm that indicates e9istence of potential problems

    or problems that are about to affect normal services. )t isnecessar to ta5e measures to prevent them from

    developing into faults that ma severel affect normalservices.

    >olloing sections details possible alarms in the sstem foruserJs reference. #ontact #ustomer Support #enter of * in

    time if failing to handle a generated alarm.

    CCS "larms Note

    4hen handling ith alarmsB perform in the order ofKor e9ampleB if there are 'steps in K

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    34/85

    #hapter % (larm and ##S is normalI

    2. #hec5 the e9ternal cloc5.

    Cloc( Module )rror

    +te Content%

    Description #loc5 module error

    (larm level #ritical alarm

    (larm tpe quipment alarm

    #ause

    1. +1.%% M cloc5 alarmI

    2. 10 M cloc5 alarmI

    3. >R alarmI

    %. >7 alarm.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    35/85

    @SDR 7ode $ *roubleshooting

    oard Communication %in(Disconnected

    +te Content%

    Description $oard communication lin5 is disconnected.

    (larm level #ritical alarm

    (larm tpe #ommunication alarm

    #ause1. #ommunication cables errorI

    2. $oard error.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    36/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    37/85

    @SDR 7ode $ *roubleshooting

    +te Content%

    %. Re"start the board.

    "pplication Soft&are Monitoring"larm

    +te Content%

    Description (pplication softare monitoring alarm

    (larm level #ritical alarm

    (larm tpe #ommunication alarm

    #ause1. #ommunication line errorI

    2. $oard error.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    38/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    39/85

    @SDR 7ode $ *roubleshooting

    Cloc( Reference SourceDeterioration

    +te Content%

    Description #loc5 reference source deterioration

    (larm level MaEor alarm

    (larm tpe quipment alarm

    #ause *he reference cloc5 qualit is too bad.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    40/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    41/85

    @SDR 7ode $ *roubleshooting

    !plin( %6DS %in( )rror

    +te Content%

    Description &plin5 ,=DS lin5 error

    (larm level #ritical alarm

    (larm tpe #ommunication alarm

    #ause

    1. ,=DS transmitting module of corresponding

    *R@& is abnormalI

    2. ,=DS lin5 of corresponding bac5plane isabnormalI

    3. )nterface beteen board and bac5plane isabnormalI

    %. ,=DS receiving module gets abnormal.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    42/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    43/85

    @SDR 7ode $ *roubleshooting

    +te Content%

    remote error. #hec5 the fibers.)f the fibers are normalB go on ith Step +I

    3. Reset the R$)I

    %. Replace R$) alarm optical moduleI

    '. Replace the R$)I

    +. )f conditions permitB chec5 hether

    corresponding R> remote is normal.

    38 #onfidential and Proprietar )nformation of * #ORPOR(*)O7

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    44/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    45/85

    @SDR 7ode $ *roubleshooting

    +te Content%

    (larm level MaEor alarm

    (larm tpe #ommunication alarm

    #ause

    MS"()S alarm is sent to donstream equipment hen,OS and ,O> alarms occur to upstream equipment of

    7ode $. )t is also possible that 7MS inserts an MS()Salarm in transmission equipment.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    46/85

    #hapter % (larm and rame :,O>; snchroni!ation of 1 ,in5

    (larm level MaEor alarm

    (larm tpe #ommunication alarm

    #ause *he cloc5 is out of snchroni!ation.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    47/85

    @SDR 7ode $ *roubleshooting

    +te Content%

    inconsistentI

    2. *he cloc5 is out of snchroni!ation.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    48/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    49/85

    @SDR 7ode $ *roubleshooting

    Configuring #M" 9roup 7ailure

    +te Content%

    Description #onfiguring )M( group failure

    (larm level MaEor alarm

    (larm tpe #ommunication alarm

    #ause )ub port alread e9ists or parameter error

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    50/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    51/85

    @SDR 7ode $ *roubleshooting

    Optical Module ot-in-position

    +te Content%

    Description Optical module is not in position.

    (larm level MaEor alarm

    (larm tpe quipment alarm

    #ause#orresponding optical module is not in position or

    abnormal.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    52/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    53/85

    @SDR 7ode $ *roubleshooting

    +te Content%

    %. Replace the temperature sensorI

    '. Replace the M&.

    ,hole )quipment $emperature Rise"larm

    +te Content%

    Description 4hole equipment temperature rise alarm

    (larm level MaEor alarm

    (larm tpe (mbient alarm

    #ause

    *emperature difference at M& inta5e and outta5edetected b M& is over 1' #. Possible causes

    areA

    1. Dust"proof net is bloc5edI

    2. >an errorI

    3. *emperature sensor errorI

    %. M& board error.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    54/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    55/85

    @SDR 7ode $ *roubleshooting

    Soft&are Operation 7ailure

    +te Content%

    Description Softare operation failure

    (larm level #ritical alarm

    (larm tpe rror handling alarm

    #ause Softare version error or board error

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    56/85

    #hapter % (larm and ## or >#D errorI

    %. M& error.

    #correctlI

    3. Replace the ># board that the fault

    temperature sensor corresponds toI

    %. Reset M&I

    '. Replace M&.

    7ather ode )*ternal )quipment

    )rror

    +te Content%

    Description >ather node e9ternal equipment error

    (larm level (larming alarm

    (larm tpe quipment alarm

    #ause

    1. 9ternal equipment errorI

    2. >ather node connection errorI

    3. M& error.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    57/85

    @SDR 7ode $ *roubleshooting

    CP! Overload "larm

    +te Content%

    Description #P& overload alarm

    (larm level MaEor alarm

    (larm tpe quipment alarm

    #auseR alarmI

    %. >7 alarm.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    58/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    59/85

    @SDR 7ode $ *roubleshooting

    oard Configuration Parameter )rror

    +te Content%

    Description $oard configuration parameter error

    (larm level MaEor alarm

    (larm tpe quipment alarm

    #ause #onfiguration parameter error or hardare error

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    60/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    61/85

    @SDR 7ode $ *roubleshooting

    +te Content%

    2. Reset the R$)I

    3. Reset the corresponding *R@&I

    %. Replace the R$)I'. Replace the corresponding *R@&.

    !plin( Path Operation "bnormal

    +te Content%

    Description &plin5 path operation is abnormal.

    (larm level MaEor alarm

    (larm tpe quipment alarm

    #ause1. )nternal communication errorI

    2.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    62/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    63/85

    @SDR 7ode $ *roubleshooting

    Signal Receiving Path +uality"bnormal "larm

    +te Content%

    Description Signal receiving path qualit abnormal alarm

    (larm level MaEor alarm

    (larm tpe quipment alarm

    #ause Receiving path error

    cable interface :includingantenna interface; of corresponding path is loose.

    RDM "larms

    Cloc( Module )rror

    +te Content%

    Description #loc5 module error

    (larm level #ritical alarm

    (larm tpe quipment alarm

    #ause

    1. +1.%% M cloc5 alarmI

    2. 10 M cloc5 alarmI

    3. >R alarmI

    %. >7 alarm.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    64/85

    #hapter % (larm and cable are not in good

    contact.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    65/85

    @SDR 7ode $ *roubleshooting

    Soft&are Operation 7ailure

    +te Content%

    Description Softare operation failure

    (larm level #ritical alarm

    (larm tpe rror handling alarm

    #ause Softare version error or board error

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    66/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    67/85

    @SDR 7ode $ *roubleshooting

    +te Content%

    #ausePossibl signal poer of poer amplifier ,P(30

    input portB e9ceeds ma9imum output poer 2d$.

    ore9ampleB fans on the poer amplifier laer or5abnormall.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    68/85

    #hapter % (larm and

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    69/85

    C h a p t e r /

    Troubleshooting$2aples

    *his chapter introduces some common problems during routineoperation and maintenance of the @4R $0B and presentssmptomsB possible causes and solutions.

    Overvie&*able +shos possible problems during routine maintenance ofthe @4R $0.

    T%B' $ 3 CO M M O N &RO B' $ M S ! N R O #T ! N$ M %! NT $ N%NC$

    Cla%%ification /ro$le Rear%

    Sstem

    monitoring

    #P& utili!ation toohigh

    See

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    70/85

    System Monitoring

    5igh CP! !tilization

    Symptoms and )ffects

    (larm man"machine interface of operation and maintenanceconsole has a #P& utili!ation alarm reportedB or #P& utili!atione9ceeds normal value for a long time hen monitoring #P&utili!ation at performance management man"machine interface.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    71/85

    #hapter ' *roubleshooting 9amples

    Decreased Radius of $S Coverage

    Symptoms and )ffects

    #onversation qualit at the edge of cell decreasesB andmeasurement ith instruments shos that coverage radius of$*S signals decreases.

    Causes

    1. Some radio parameters are set improperlB particularl pilotchannel transmitting poer and forard transmitting poerBhich affects actual coverage of $*S.

    2. Surrounding landform and geographical feature changesB for

    e9ampleB urban constructionB also affect actual coverage.

    3. )nterference in space electromagnetic environment causespilot pollution.

    %. (ntenna feeder sstem gets fault.

    5andling

    #onduct an on"site surve and detailed spectrum test near the

    siteB and configure radio parameters again based on ambientcharacteristics and test result. )t is better to let professionalnetor5 optimi!ation personnel perform this tas5.

    !ser Complaints

    Difficult Call Connection

    Symptoms and )ffects

    &sers complain that call completion rate :successfull connectedto called part; decreases significantl and calls cannot be

    connected at all in e9treme cases.

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 67

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    72/85

    @SDR 7ode $ *roubleshooting

    Causes

    #all completion rate is a basic inde9 to evaluate overall

    performance of the sstem. ( great variet of factors ma affectitB includingA

    1. $oards and parts of access side equipment :including 7ode $and R7#; failB or parts of core netor5 side equipment :suchas MS#; failB so less resources are available and usersJaccess requests are mostl reEected.

    2. Softare version mismatch e9ists among some equipment orpartsB for operation mista5es at sstem upgrade or versionupdate. )t affects normal or5ing of the sstemB particularlputting interactive flo of important signaling or messageinto disorder. (s a resultB user access becomes difficult.

    3. arl"stage netor5 planning or netor5 construction is notperfect or resource configuration is incorrectB so allocation ofsstem service resources is not reasonable. *here areinsufficient resources in some areasB particularl those ithlarge trafficB hich reduce success ratio of user access.

    3. &ser access is more li5el to fail in promulgation

    environmentB if there is electromagnetic interference :fore9ampleB pilot pollution; and S7R degrades.

    5andling

    1. Set statistical tas5s on performance statistics man"machine

    interface of operation and maintenance bac5groundB tomeasure call completion rate in user complaint areaB andcompare the result ith old statistical data.

    2. *here is a large possibilit of e9ternal electromagnetic

    interference if statistical indices do not decrease significantl.

    &se a radio signaling anal!er to observe connection processof radio signalingB and record characteristics of abnormalinterruptions.

    &se a spectrum anal!er to scan frequenc band in use for

    an e9ternal electromagnetic contamination. ,ocate interference source and tr to eliminate it.

    3. #hec5 equipment faultsB resource configurations andsoftare versions if statistical indices decrease significantl.

    Determine hether hole netor5B a $*SB or a sector isaffected according to problem area reported b the user first.

    #hec5 current alarms and histor alarms. #hec5 or5ing

    status of equipment partsB transmission equipment and cloc5source. liminate an fault found.

    Observe utili!ation of related sources continuouslB for

    e9ampleB board #P& utili!ationB lin5 loadB cell trafficB and

    68 #onfidential and Proprietar )nformation of * #ORPOR(*)O7

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    73/85

    #hapter ' *roubleshooting 9amples

    radio channel utili!ation. (dEust resource configuration dataand e9pand capacit of the equipment if necessarB if relatedresources cannot meet needs continuousl.

    #hec5 softarehardare versions of each equipment and

    partB to eliminate version mismatch.

    %. )t ma be a sign that the sstem is to be don if performance indices of the hole netor5 degrade.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    74/85

    @SDR 7ode $ *roubleshooting

    %. &sers are moving during the conversation. Signals areseriousl bloc5ed suddenlB and air lin5s undergo fast fadingor receiving signal strength undergoes sudden change henthere are obstacles in the surrounding. *he affect continuit

    of voice because rapid poer control function cannoteffectivel follo up.

    '. Resources occupied during the conversationB such as carrierfrequencB lin5B boardB sitching netor5 and transmissionequipment have faults and do not or5 stabl. *he affectstabilit of the conversation.

    +. Data configurations are incorrect or versions of hardare andsoftare do not match. *he affect stabilit of theconversation.

    5andling

    1. #hec5 mobile terminal used for conversation. &se multipleterminals of different models for comparison if possibleB todetermine hether the terminal has an problem.

    2. *est signal field strength in conversation area to evaluatecoverage effect. Optimi!e the netor5 if the area has ea5

    signal field strength.

    3. Monitor ith instruments to see hether an pilot pollution

    or carrier interference e9ists in the region. >ind outinterference source and handle it properl if so.

    %. /uer recent forard poer output status of all adEacent$*Ss at operation and maintenance console. #hec5corresponding $*S and eliminate related fault if finding anabnormal poer output.

    '. &sual reason for voice qualit degradation onl occurringduring motion is that poer control mechanism in specialgeographical and ambient sstem cannot accommodate theapplication. *here is need to optimi!e the netor5 in thiscaseB for e9ampleB b adEusting the antenna.

    +. &se a signaling monitoring meter or start signaling tracing atoperation and maintenance bac5groundB and perform on"site

    dialing testB to monitor signaling flo. /uer histor alarmsand current alarms simultaneousl as a supplement to locatethe fault. #hec5 corresponding data configuration and

    hardaresoftare versions to eliminate the fault if locatingthe fault to a specific board or part.

    Slo& to "ccess #nternet

    Symptoms and )ffects

    #onnection speed is relativel slo hen users access the)nternet through pac5et service.

    70 #onfidential and Proprietar )nformation of * #ORPOR(*)O7

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    75/85

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    76/85

    C h a p t e r 3

    $ergent ault -andling

    *his chapter introduces emergent faults during running of the

    @4R $0B and provides ho to contact the #ustomer Support#enter of *. >or some emergent faultsB a quic5 handlingprocedure on site is given.

    Definition of )mergency7aultmergenc fault means that a maEor fault occurs during running

    of the product and fails to provide basic serviceB for e9ampleAthe equipment is paral!ed or suspendedI the sstem is indisorderI abnormal running time e9ceeds 30 minutes for othercauses or the product endangers personnel safet. *hefolloings are level"1 faultsA

    1. >ail to provide basic service :regardless of an cause such asequipment paralsisB suspensionB sstem disorder or ambientand human factors;B and fails to recover after preliminarhandling. mergenc handling is in need.

    2. Service interruption affects maEor sites or customers.

    3. >oregroundbac5ground communication is completel

    interrupted.

    %. (ffects other equipment to provide basic service.

    '. &se of the product endangers personnel safet.

    5andling#ontact technical support person of * in time if an emergencfault occurs to the @4R $0. * #orporation ill immediatelenable emergenc fault handling to solve the problem ensuring

    qualit

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 73

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    77/85

    On-site 5andling Procedure*his section introduces on"site fast handling procedures for

    some emergenc faults ith e9amples. )nform #ustomerSupport #enter of * immediatel if the problem still e9ists.

    #ustomer Support #enter of * provides round the cloc5service.

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    78/85

    #hapter + mergent >ault

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    79/85

    @SDR 7ode $ *roubleshooting

    Po&er "mplifier Output Po&erProtection

    Output poer protection of the poer amplifier is triggeredB andthere is no output signal or output signal is ver ea5B so 7ode$ does not or5 normall and user services cannot be accessed.

    Output poer protection of the poer amplifier is basicallbecause S4R is too high and poer returned is too large. *hema burn the poer amplifier. *here is need of protection andthe poer amplifier adEusts output poer to decrease poerreturned. )mproper installation of antenna feeder sstem resultsin unmatched input impedance and output impedance in actual

    cases.

    Perform folloing steps in sequence to solve the problemA

    1. Remotel reset the poer amplifier boardB and observehether the sstem recovers. Reset it on site if not.

    2. #hec5 hether antenna feeder sstem is disconnected.)nstall antenna feeder sstem properl if so.

    3. #hec5 hether antenna sstem is in short circuit. Replace itith a ne one if so.

    %. #hec5 hether there is an sign that ater enters antennafeeder sstem or antenna feeder sstem becomes aging. )n

    the first caseB discharge the ater in former case and replace

    antenna feeder sstem in latter case.

    %ightning Stri(e

    ( lightning stri5e ma have damaged the equipmentB if sstemservice suddenl becomes abnormal.

    #hec5 devices in the folloing orderA antenna feederB DD,B*R@&B poer distributorB ))(B and optical interface of ))(.

    )solate failed parts and replace them.

    76 #onfidential and Proprietar )nformation of * #ORPOR(*)O7

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    80/85

    C h a p t e r 4

    Ters

    #er e%cription

    ((( (uthentication (uthori!ation (ccounting

    ((,2 (*M (daptation ,aer tpe 2

    ((,' (*M (daptation ,aer tpe '

    (< (uthentication

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    81/85

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    82/85

    % p p e n d i 2 %

    %bbreviations

    A$$reviation% e%cription

    (3 (uthentication algorithm (3

    ('@ ncrption algorithm ('0"6

    (- #iphering 5e generating algorithm (-

    (#F (#Fnoledgement

    (#M (ccumulated #all Meter

    (#M (ddress #omplete Message

    ( (pplication ntit

    (P$ (*M Process $oard

    (o# (dvice of #harge

    (o##(dvice of #harge #harging supplementarservice

    (o#)(dvice of #harge )nformationsupplementar service

    (S (pplication Service lement

    (S)? (nalog Signaling

    (S7.1 (bstract Snta9 7otation One

    (u# (uthentication #entre

    $()# $arring of (ll )ncoming #alls supplementarservice

    $(O#$arring of (ll Outgoing #alls supplementarservice

    $##< $roadcast #ontrol #hannel

    $#*, $ac5 #ontrol

    $#S7 $ac5plane of #ircuit Sitch 7etor5

    $D* $ac5 Digital *run5

    $#*# $ac5plane of #on*rol #enter

    $>$) $ac5 >iber $us )nterface

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 79

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    83/85

    A$$reviation% e%cription

    $orarding

    ##)***he )nternational *elegraph and *elephone#onsultative #ommittee

    #ct #ircuit#> all #all >orarding services

    #>$#all >orarding on mobile subscriber $ussupplementar service

    #>7Rc#all >orarding on mobile subscriber 7otReachable supplementar service

    #>7R#all >orarding on 7o Repl supplementarservice

    #>all >orarding &nconditionalsupplementar service

    #?# #ircuit ?roup #ongestion signal

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 80

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    84/85

    (ppendi9 ( (bbreviations

    A$$reviation% e%cription

    #) #ell )dentit

    #&? )nde9

    #,F? #,O#F ?enerator

    #,F) #,O#F )nterface

    #,) #alling ,ine )dentit

    #,)P#alling ,ine )dentification Presentationsupplementar service

    #,)R#alling ,ine )dentification Restriction

    supplementar service

    #M #onnection Management

    #MD #oMmanD

    #MP #ontrol Main Processor

    #O,) #Onnected ,ine )dentit

    #O,P#Onnected ,ine identification Presentationsupplementar service

    #O,R#Onnected ,ine identification Restrictionsupplementar service

    D*$ Digital *run5 $oard

    ??,P ??S7 ,ine Processor

    #O,P#Onnected ,ine identification Presentationsupplementar service

    ??MP ??S7 Main Processor

    ??&P ??S7 ?*P"& Processor

    ?,) ? ,ine )nterface

    ?R(7 ?SM nhanced Radio (ccess 7etor5

    )M($ )M( $oard

    )P$ )P Process $oard

    )P) )P bearer )nterface

    )4>$ )4> $oard

    M7)# Multi"service 7etor5 )nterface #ardMO7$ MO7)O*R $O(RD

    MP$ Main Process $oard

    MR$ Media Resource $oard

    OMP Operation Main Processor

    P,) POS ,ine )nterface

    PS7 Pac5et Sitch 7etor5

    P4RD PO4R Distributor

    RMP Router Main Processor

    #onfidential and Proprietar )nformation of * #ORPOR(*)O7 81

  • 8/10/2019 ZXSDR Node B Troubleshooting-89

    85/85

    @SDR 7ode $ *roubleshooting

    A$$reviation% e%cription

    RP$ Router Protocol process $oard

    SD