Action to be taken if the measurement exceeds its supervised threshold:

Check the EBM log, and look for L_ATTACH or L_TAU events containing a Sub-Cause Code. Continue
with the action proposed for the Sub-Cause Code. The Sub-Cause Code reveals if the problem is
missing TA-LA mapping configuration, or no mapped LA can be used Check the EBM log, and look for
L_ATTACH or L_TAU events containing a Sub-Cause Code. Continue with the action proposed for the
Sub-Cause Code. The Sub-Cause Code reveals if the problem is missing TA-LA mapping
* SGSN-MME needs to send an SGsAP-LOCATION-UPDATE-REQUEST message to the MSC but cannot
due to missing TA-LA mapping configuration.

* SGSN-MME needs to send an SGsAP-LOCATION-UPDATE-REQUEST message to the MSC but cannot

due to no LAI can be selected although there are mapped LAIs to the TAI.

* SGSN-MME does not receive a response from the MSC to a SGsAP-LOCATION-UPDATE-REQUEST

message.

* SGSN-MME receives an SGsAP-LOCATION-UPDATE-REJECT with any cause code from the MSC.

Action to be taken if the measurement exceeds its supervised threshold:

Check the EBM log, and look for L_ATTACH or L_TAU events containing a Sub-Cause Code. Continue
with the action proposed for the Sub-Cause Code. The Sub-Cause Code reveals if the problem is
missing TA-LA mapping configuration, or no mapped LA can be used due to being restricted by access
restriction or LA selection profile, or missing response from the MSC, or reject from the MSC
(including the cause code given by the MSC). The EBM log also reveals which TA(s), LA(s), and MSC(s)
the problem is related to.
It may happen that this counter is incremented but nothing is visible in the EBM log. This happens in
case MSC pool is deployed and Location Update fails towards the MSC initially selected but succeeds
after fallback to another MSC in the pool. In this case capture the SGs traffic with ITC and search for
SGsAP-LOCATION-UPDATE-REJECT or no response to SGsAP-LOCATION-UPDATE-REQUEST.