MOP for TR Fail.pdf

3
MOP for TR Fail 1. Check the following two alarms (both current and history): BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON A INTERFACE (2992) BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON ABIS INTERFACE (2993) Command: ZAHO::NR=2992; ZAHO::NR=2993; ZAHP::NR=2992; ZAHP::NR=2993; CIC PCM Here, PCM number indicates both ET and TCSM number. BTS PCM These alarms only inform that calls are cleared due to unsatisfactory transmission or equipment failure. Now to find the root cause, please check the transmission of following interface or plugin unit of transcoder. 2. For TCSM and ET current and history alarm of the BSC: ZAHO:TCSM, <tcsm>; ZAHP:TCSM,<tcsm>; ZAHO:ET,<et>; ZAHP:ET,<et>; For whole BSC ET/TCSM no need to mention the <number>. 3. Check the status of the TCSM & ET in which alarms found

description

MOP for transcoder fail in NSN

Transcript of MOP for TR Fail.pdf

  • MOP for TR Fail

    1. Check the following two alarms (both current and history):

    BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON A INTERFACE (2992)

    BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON ABIS INTERFACE (2993)

    Command:

    ZAHO::NR=2992;

    ZAHO::NR=2993;

    ZAHP::NR=2992;

    ZAHP::NR=2993;

    CIC PCM

    Here, PCM number indicates both ET and TCSM number.

    BTS PCM

    These alarms only inform that calls are cleared due to unsatisfactory transmission

    or equipment failure.

    Now to find the root cause, please check the transmission of following interface

    or plugin unit of transcoder.

    2. For TCSM and ET current and history alarm of the BSC:

    ZAHO:TCSM, ;

    ZAHP:TCSM,;

    ZAHO:ET,;

    ZAHP:ET,;

    For whole BSC ET/TCSM no need to mention the .

    3. Check the status of the TCSM & ET in which alarms found

  • ZUSI:TCSM,; (if applicable)

    ZUSI:ET ,;

    ZYEF:ET,;

    If HW state WO_EX but PCM down then forward the issue to check transmission.

    Abis ET----- Regional Operation

    Ater ET----- TX BO via FLS-TX

    4. If TCSM and ET physical state WO_EX and PCM OK then block that TCSM step

    by step by following commands-

    ZUSC:TCSM,:BL;

    ZUSC:TCSM,:TE;

    ZUSC:TCSM,:SE; [SE_OU]

    ZUSC:TCSM,:SE; [SE_NH]

    Here, if any state changes of the followings aborted then do it forcibly

    Example:

    ZUSC:TCSM,:BL,FCD;

    5. Now revert to the TE state by following commands:

    ZUSC:TCSM,:SE; [SE_OU]

    ZUSC:TCSM,:TE;

    In revert process do not change state forcibly.

    If it is not possible to revert up to TE state (without using FCD) then again make

    the state SE_NH, block the ckt of the TCSM and forward TT to RO (in where TC

    located) to check HW and reset TC card of that TCSM.

    Here, command to block ckt is- ZCEC:ETPCM=,CRCT=x-y&&-z:BL; (for ckt info use cmd: ZRCI:SEA=4:ETPCM=;)

    Plugin unit LOC check command-

    ZWTI:PI:TCSM,;

  • 6. If ckt are BL_SY and it is possible to revert TE state smoothly then wait almost

    10 minutes and start diagnosis:

    Run the diagnostic program-

    ZUDU:TCSM,;

    Wait few minutes execute following command to check the progress of

    diagnostic test-

    ZUDQ;

    Check the diagnostic result-

    ZUDH:TCSM,;

    7. If diagnosis result found OK then change the TCSM state to WO_EX and check

    the ckt status by command

    ZRCI:SEA=4:ETPCM=;

    If ckt found ok then the issue resolved.

    8. If ckt not ok then forward to CN concern mentioning the CCSPCM to check from

    their end.

    9. In case of TCSM physical reset, after reset completion check OMU and perform

    step 5, 6 & 7 one after another.

    10. In case of diagnostic result not ok then forward to second level.