Severe degradation of E-RAB Success Rate in specific cells only

There are two more.
Statis and userspec and rruuserlic.
Rruuserlic if pegging then no option license has to be increased at any cost.
Statis if having parameters to control it’s failures.

These are the counters in Huawei M2000, and may be not activated.

I see.
Well I double checked PRS and only those are available.

The counters could be not activated
Will check on that.

But knowing the exact issue (SRS, PUCCH, DL or UL lic) will not solve the issue.
Try to split traffic with surrounding cells.

Sum of connected user is more than 400 at that time and license is user.
Then either lic or split traffic is option.
But if failing in statis there are parameters which can resolve issues related to threshold satisfaction rate and switches.

Yep, that is the case.
I have just activated and will keep monitoring it.

Unfortunately this is a lone site.
On the long term, expansion will be the only option I believe.

Take care.
With Huawei some access failures are not even recorded in counters.
You can find them only in CHR file.

What was failure cause license?
How many carriers are there in that site?
How many license are in other sites?
Rrc connected.

Oh, good to know! Thanks!

The main failure is L.E-RAB.FAILEST.NORADIORES.
But there is one subcounter for license issue is not active.
Just activated it and will keep monitoring it.

Only one carrier. L1800 20 MHz.

From 400 to 2000, depends on location.

Great.
Just monitor for something.
Hope it gets solved.

Does anyone knows what command to increase RRC users?

I know how to check, not sure about increasing.
Maybe to increase it, you need to modify the license file.

DSP LICINFO you can use to check.

Are all cells in same board?
LST BASEBANDEQM:;

There is no command, @SimoSamKun is right: Only applying new license.

How many RAB attempts (L.E-RAB.AttEst) per cell which sector has?
Remember that for each attempt failure the UE will re attempt so the number can increase and the percentage (%) decrease.

It does not reach the RAB att state.
It fails at RRC failure.

No, for eNB it is a RAB phase.
The MME send the E-Rab Setup Request and there is no Resource at eNB Level and it return fail to MME.

First UE needs an RRC connection.
After RRC is established then ERAB is established.
In his case most of UEs fail at RRC estab so such UEs do not reach RAB estab phase.

OK, but the problem phase is in RAB.
Sometimes the RRC Accessibility is good but RAB is not.