VS.RRC.Rej.RL.Fail Counter
Hi Friends,
I want ask Huawei 3g counter of VS.RRC.Rej.RL.Fai.
What can be the reasons of this RRC Reject an what about the solutions.
Is any body have detailed document or have any experiences.
I read some Huawei docs but these are not sufficient.
Counter Description
VS.RRC.Rej.RL.Fail Number of rejected RRC connection setups due to RL establishment failure (excluding RL establishment failure due to CE congestion).
Re: VS.RRC.Rej.RL.Fail Counter
Quote:
Originally Posted by
gageloz
Hi Friends,
I want ask Huawei 3g counter of VS.RRC.Rej.RL.Fai.
What can be the reasons of this RRC Reject an what about the solutions.
Is any body have detailed document or have any experiences.
I read some Huawei docs but these are not sufficient.
Counter Description
VS.RRC.Rej.RL.Fail Number of rejected RRC connection setups due to RL establishment failure (excluding RL establishment failure due to CE congestion).
There are few more counters for RRC rejects by reasons, check them as well to see what might be the reson - congestion, radio failure and etc..
BR
Re: VS.RRC.Rej.RL.Fail Counter
Hi,
In 3G there is procedure called radio link failure. It supervised by RL failure Timer, this radio link failure is caused by bad coverage/quality which can yield on out of synch problem. If during this out of sync, the node B doesnt receive any specific number of in synch indicator then it will generate this radio link failure procedure if this timer expires so this counter will increase.
Those RRC reject maybe because of this, during the RRC phase, the RL failure condition was met.
br
Re: VS.RRC.Rej.RL.Fail Counter
Wbbp Overload.. check the alarms
solution is to add the second Wbbp board
Br
Re: VS.RRC.Rej.RL.Fail Counter
what exactly do you mean by processing board overload?
BR
Alex
Quote:
Originally Posted by
Leon@rdo
Wbbp Overload.. check the alarms
solution is to add the second Wbbp board
Br
Re: VS.RRC.Rej.RL.Fail Counter
Actually we have this issue.
In our case the pattern of bad performance are when Wbbp with capacity 384 CE DL/UL.
Solution.
Replace board 1 Wbbp 384 DL/UL -> 3 board 128 DL/UL
processing in 1 card very high and show VS.RRC.Rej.RL.Fail
BR
1 Attachment(s)
Re: VS.RRC.Rej.RL.Fail Counter
Please note that this counter will not count if CE congestion happened, CE congestion has different counter: VS.RRC.Rej.ULCE.Cong & VS.RRC.Rej.DLCE.Cong
Please check this counter if there is..
So no problem with CE and no need to add WBBP..
It should be from bad coverage/quality which RL failure timer expired..
Attachment 25674
Re: VS.RRC.Rej.RL.Fail Counter
well i have an experience with this one, may be you should check alarm first, it can be from board faulty like WMPT or BBU. in my experience, RLFail was increased after there is a CE upgrade, the execution team didnt follow the proper rule when changing the WBBP board, and impacted to WMPT then it is raise a WMPT fault. it is impacted to increase of RRCRejRLFail
Re: VS.RRC.Rej.RL.Fail Counter
Replace 1 card 384 by 3 Card 128 and comment result in this ISSUE is Huawei Bug in proccesing of WBBP.
BR
Re: VS.RRC.Rej.RL.Fail Counter
Hi, this counter is a very general which can be happened as explained by fellow experts above (T313, N313, N315, wbbp, etc). However i would suggest you would need to correlate to other counters to ensure which is the main cause of the problem (i.e.RRC.No.Reply). You may want to check the transmission related parts (congestion, link down, etc). Remember, checking the alarm is the first step in solving the issue.