physical exitance of TRX

kawa,

the hopping list is a list of frequencies on which the active trx will hop (= synthetized frequency hopping)

when locking a trx from the OMCR, the trx will not carry any traffic, and if you were using BBH or No-Hopping, then the frequency “attached” to this TRX will not be sent “on air” anymore.

regards,
pix

i seriously doubt something like this can happen, but it depends on your vendor implementation.
In BBH, all active MS’s will hop on all BBH frequencies.

Do you see a call drop/sdcch drop of 100% or a tch assignment failure of 100% ?

kawa,

ok, so for your problem, i don’t think hopping is the issue. actually, i would suspect two possibilities :

1/ one trx is faulty, but the wrong TRX was locked –> the faulty trx carries more traffic, therefore, there is more call drops, etc.

2/ the faulty trx is locked, indeed, so the other trx’s are going to carry more traffic. It is a possibility that another trx is also faulty, so by locking one TRX, you actually reveal another faulty trx.

🙂

that sounds more probable than a wrong hopping management, but who knows…

Dear Kawa,

Which vendor? if ericsson check the counters CNRELCONG and TNRELCONG, are they increased,if yes, this mean that you needed this TRX, and you shouldn’t lock it. Unless you are ready with cell load sharing strategy. on the other hand, in BBH number of frequencies = number of TRXs, and when you lock a TRX, then you are locking the Frequency you assigned to it, this means hoping will not include this frequency.

Regards,