rsrp is -108 but sinr is good.
Possible reason why eNodeB not receive Sec Mod complete message from UE is due poor RF Condition of UE (Look into other failure)
Can you check if eNodeB receive RRC reestab message from UE After RRC Secur Mod-Comand
It receives an rrc con request with establishment cause mo signalling not rrc re-establishment.then starts the process again and fails with same reason
Did you check with EPC Team .
1)if only one single need to check SIM card
2)if Multiple UEs need to check MME configuration (TAC)
can you check Attach Reject reason ?
there is reject message on the NAS layer, such as Attach Reject and Service Reject
Yes. Issue came from core network.
They get ems signaling message saying enode b response times out. Ask ran engineer to diagnose problem.
They get initial context failure saying failure in radio interface procedure.
So I check on my end and I get failure reason interaction with other procedure. But I don’t see any handover messages and no rrc reconfig &rrc security mode command completion messages.
but you click to reject message and see result
Yes. They clicked and showed me.
Ems signaling said cause protocol error then under detail it said enode b response times out.
And on context failure it gave cause 26 failure in radio interface procedure.
check Attach reject happen before S1AP _intitial_Contex_Fail for all 26 failure?
if yes then we can check reason
Attached Reject due to protocol error is devided into two reason
- Protocol error, unspecified (HSS Not Responding)
- Protocol error, unspecified (Security Algorithm Negotiation Failure)
enode b response time is the biggest contributor. the rise shown on the 9th was due to increase in context failures due to no radio resource,but that was rectified and it is now back to the 400 times.
when i run context fail counter in u2020 it has a high number that fall under unknown.
Got it ,issue is due enodeB IP configuration.
First :check S1 interface in this sites and compare with other good site in same TAC.
Second :check if S1 flex was implemented in bad sites.
Third:check if this sites is new integrated sites and when issue started increase
for 1: using the mml dsp s1interface?
for 2 ,how do you check s1 flex , is it MME capinfo MO?
LST S1 or DSP S1interface (Should be Same IP MME like NBRs in same Tac)
for S1 flex feature (Below command)
If the S1 interface is set up in link configuration mode, perform the following steps for multiple MMEs:
- Run the ADD SCTPLNK command to add an SCTP link to the S1 interface.
- Run the ADD CPBEARER command to add a control-plane bearer to the S1 interface.
- Run the ADD S1INTERFACE command to add an S1 interface, which connects the eNodeB and the MME. In this step, set the MME Selection Priority parameter based on the network plan.
If the S1 interface is set up in end point configuration mode, perform the following steps:
- Run the ADD SCTPTEMPLATE command to add an SCTP parameter template. A parameter template can be shared by multiple SCTP links.
- Run the ADD SCTPHOST command to add an SCTP host. One operator can use only one SCTP host.
- Run the ADD SCTPPEER command to add an SCTP peer. Each MME must be configured as an SCTP peer and the SCTP port number must be configured based on the network plan.
- Run the ADD EPGROUP command to add an end point group. Multiple end point groups must be configured for an eNodeB connecting to multiple MMEs.
- Run the ADD SCTPHOST2EPGRP command to add the SCTP host to the end point group. One operator uses the same SCTP host. Add the SCTP host to the end point group corresponding to the connected MME.
- Run the ADD SCTPPEER2EPGRP command to add the SCTP peer to the end point group. One operator can use only one SCTP host.
- Run the ADD S1 command to add an S1 object. Then, associate the S1 object with the operator and control-plane end point group. In this step, set the MME Selection Priority parameter based on the network plan. Multiple S1 interfaces must be configured for an eNodeB connecting to multiple MMEs.
s1 interface has Served GUMMEIs no ips. so can GUMME can be used instead for comparison?
yes exactly :A GUMMEI of a serving MME consists of the MCC, MNC, MME group ID, and MME code.
Compared 6 enode b s in the same TAC . 3 good and 3 bad.
some have different s1 interface id but same config and even with a pair with same s1 id and gummei its still big diffrence in contexxt failures
Check below Status of S1 interface (normal)
MME Release = Release 9
S1 Interface Is Blocked = FALSE
S1 Interface State = Normal
S1 CP Bearer State = Normal
Served PLMNs = X
Served GUMMEIs = X
LST IPPATH & LST ENODEBPATH & LST SCTPPEER to check if IP as per design team
they all show normal.
@cheikh789 Radio network cause: interaction with other procedure.
Which other procedure can cause this apart from handover.
I have a number of erab fails due to L.E-RAB.FailEst.MME.S1AP but L.E-RAB.FailEst.Conflict.Hofail are 0.
The L.E-RAB.FailEst.MME.S1AP counter is incremented if the E-RAB setup failure is caused because of a cross between the initial UE context setup procedure and other S1AP-related procedures. which other s1-ap procedures can these be?
other S1AP-related procedures:
when the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME during the UE context setup procedure.
check below point
1)check Interference from day issue
2)LTE coverage (RRC Redirection E2W attempt increased )from day issue
3)check reason of failure from CHR log (FMA Tool)
4)what is DL AMBR And UL AMBR in UE Context setup request