Generic selectors
Exact matches only
Search in title
Search in content
Search in posts
Search in pages

NOKIA alarms

This topic contains 52 replies, has 0 voices, and was last updated by  Joseph De light 5 months, 1 week ago.

Viewing 15 posts - 1 through 15 (of 53 total)
  • Author
    Posts
  • #54217 Reply

    FLM

    HI
    would you please explain the below alarms and what do the numbers mean??
    7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD
    00 00 01 00 01 01 01 01 05 02 2d

    b- 7745 CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD
    01 00 00 01 00 01 01 01 01 07 02 87d

    c- 7601 BCF OPERATION DEGRADED(Difference between the PCM and BTS frequency
    7607 TRX OPERATION DEGRADED(Mismatch between BSC/MMI configuration and/or IDD TRX)
    g-BCF-109/BTS-325/TRX-1,BCF-109/BTS-325/TRX-2,BCF-109/BTS-326/TRX-4,BCF-110/BTS-328/TRX-1

    h- Low HOSR – CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD on TRX 2 (900). PLMN-PLMN/BSC-941524/BCF-109/BTS-325/TRX-2

    #54218 Reply

    MKT

    Just ask for NED. Its all there.
    Nokia Electronic Ducumentation.

    #54219 Reply

    patrick.fr

    7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD
    Meaning
    Mean holding time on a channel is below the operator-defined minimum
    during the measurement period. The alarm is used to supervise the
    functioning of traffic channels and to detect the possible faulty
    channels.
    1 indicates if the mean holding time is below the defined threshold
    in time slot 0
    00: above threshold (no alarm)
    01: below threshold (alarm)

    2 indicates if the mean holding time is below the defined threshold
    in time slot 1
    00: above threshold (no alarm)
    01: below threshold (alarm)

    3 indicates if the mean holding time is below the defined threshold
    in time slot 2
    00: above threshold (no alarm)
    01: below threshold (alarm)

    4 indicates if the mean holding time is below the defined threshold
    in time slot 3
    00: above threshold (no alarm)
    01: below threshold (alarm)

    5 indicates if the mean holding time is below the defined threshold
    in time slot 4
    00: above threshold (no alarm)
    01: below threshold (alarm)

    6 indicates if the mean holding time is below the defined threshold
    in time slot 5
    00: above threshold (no alarm)
    01: below threshold (alarm)

    7 indicates if the mean holding time is below the defined threshold
    in time slot 6
    00: above threshold (no alarm)
    01: below threshold (alarm)

    8 indicates if the mean holding time is below the defined threshold
    in time slot 7
    00: above threshold (no alarm)
    01: below threshold (alarm)

    9 identifies the time slot where the mean holding time is shortest

    10 identifies the subchannel in the time slot with the shortest mean
    holding time
    00: TCH/H subchannel 0
    01: TCH/H subchannel 1
    02: TCH/F subchannel

    11 shortest mean holding time in seconds during the measurement period(TCH)

    #54220 Reply

    hani

    i got this alarm :
    High Channel Failure Rate on all TRXs.

    please can u tell why this alarm appeared and how to solve it?!!

    #54221 Reply

    bahar

    hi
    for 7607 TRX OPERATION DEGRADED(Mismatch between BSC/MMI configuration and/or IDD TRX)
    you souhl check if some parameters which you active is match the bts/trx or not e.g if your trx’s are not edge-capable and you active EGENA in bts this alarm will occured.

    #54222 Reply

    Leonardo

    7725 Traffic channel active failure ?

    #54223 Reply

    bahar

    hi dear leonardo:
    for solving this alarm first you should check if another alarms are on in that bcf or not.sometimes the alarm will cancled by restart on the channle .sometimes trx should be replaced.sometimes the interference cause this alarm.by checking the KPI you can underestand the problem better.

    #54224 Reply

    Leonardo

    Hi Bahar,
    I realized that this alarm only occurs with TRX enabled for data and that the alarm is intermittent. increasing CDED I solving the problem?

    #54225 Reply

    Gio

    I had a site this week with 7745 on TRX’s in all sectors. The BCF came with TRS alarms, 8081 and 8066 (frame alignment errors). Tried initially to correct the TRS alarms. 7745 on all sectors disappeared when the TRS alarms were corrected. After two days, we got 7745 on TRX5 only, but there was no TRS alarm present. Going for further BTS HW isolation for now.

    #54226 Reply

    muna

    i got this alarm :
    CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD on all TRXs.

    please can u tell why this alarm appeared and how to solve it?!

    #54227 Reply

    Kartik

    In Nokia Flexi BTS TRX operation degraded coming.Why it is ALARM COMING AND HOW TO SOLVE PROBLEM.

    #54228 Reply

    Ashok

    What is the fbus alarm and what to do. this alarm clearetion.

    #54229 Reply

    Bijoy

    Muna
    There are too many reasons for 7745 alarm.If it is coming on all the TRX’s,check its transmit
    path from TRx unit, Tx port, SMA-cables from Tx port to WCxA, WCxA
    itself, and so on, until its feeder connection and antenna.
    Kartik
    What is the supplementary info along with the alarm
    Ashok
    What is your vendor?Is it Nokia?

    #54230 Reply

    pridey

    what about 7746 alarm . what is the reason? how to deal?

    #54231 Reply

    Bijoy

    7746 CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD
    Meaning
    The percentage of rejected channel seizure requests due to congestion
    as opposed to all channel seizure requests in the base station is
    above the operator-defined alarm threshold. In the segment environment
    this alarm describes the congestion situation of the whole cell although
    it is only given to the BCCH BTS.
    The alarm is used to supervise the traffic capacity of the base
    station.
    Supplementary information fields
    1 object of congestion

    01 SDCCH
    02 TCH
    03 extended cell SDCCH
    04 extended cell TCH

    2 the time (hours, minutes) when congestion was last observed during
    the measurement period

    3 number of channel seizure requests during the measurement period

    4 percentage of rejected SDCCH or TCH (depending on the
    congestion object) seizure requests due to congestion in all
    channel seizure requests during the measurement period. The
    TCH percentage includes all half rate, full rate and rate
    recommendation channel seizure requests

    5 percentage of rejected half rate channel seizure requests due
    to congestion in all seizure requests during the measurement period;
    only significant, if the congestion object is a TCH

    6 percentage of rejected full rate channel seizure requests due
    to congestion in all seizure requests during the measurement period;
    only significant, if the congestion object is a TCH

    7 this new field is significant only if the congestion object is a TCH.
    The new field is a percentage value and indicates how big a portion
    of the refused TCH requests (field refused_calls_percentage) have
    been refused due to lack of traffic handling capacity in the BCSUs.
    Instructions
    Increase the network capacity if necessary.

    Check that the parameters affecting the alarm are reasonable.
    MML command EEO outputs the radio network supervision parameter values,
    EEN command modifies the parameter values.

    Parameters, with their default values, affecting the alarm:
    ZEEN: CSR: channel seizure request threshold value (10)
    CNGS: SDCCH congestion threshold value (20 %)
    CNGT: TCH congestion threshold value (20 %)
    PRDCNG: length of congestion supervision period (120 min)

Viewing 15 posts - 1 through 15 (of 53 total)
Reply To: NOKIA alarms
Your information:




<a href="" title="" rel="" target=""> <blockquote cite=""> <code> <pre> <em> <strong> <del datetime=""> <ul> <ol start=""> <li> <img src="" border="" alt="" height="" width="">