5.2.18.2 SEPPPn32fPreviousLocationCheckValidationFailureAlertMajor

Table 5-87 SEPPPn32fPreviousLocationCheckValidationFailureAlertMajor

Field Details
Trigger Condition When previous location check validation failure error is detected between 40 to 50 Percent of total transactions, this alert will be raised.
Severity Major
Alert Details Provided

Summary

namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}
Expression:
sum(rate(ocsepp_previous_location_validation_failure_total{namespace="sepp-namespace"}[2m]))by(namespace,nf_instance_id,app,pod)/sum(rate(ocsepp_previous_location_validation_requests_total{namespace="sepp-namespace"}[2m]))by(namespace,nf_instance_id,app,pod)>=0.4 and sum(rate(ocsepp_previous_location_validation_failure_total{namespace="sepp-namespace"}[2m]))by(namespace,nf_instance_id,app,pod)/sum(rate(ocsepp_previous_location_validation_requests_total{namespace="sepp-namespace"}[2m]))by(namespace,nf_instance_id,app,pod)<0.5
OID 1.3.6.1.4.1.323.5.3.46.1.2.4033
Metric Name ocsepp_previous_location_validation_failure_total
Resolution The alerts gets cleared when the previous location check validation failure error does not lie between 40 to 50 percent of total transactions.

Possible Resolutions:

  1. Look for the following error codes in the PN32F microservice logs:
    • SEPP-PREVIOUS-LOCATION-CHECK-VALIDATION-ERROR-0019
    • SEPP-PN32FSEPP-ERROR-0018
    • SEPP-PREVIOUS-LOCATION-CHECK-VALIDATION-EXCEPTION-0020
  2. Ensure that the correct regex is configured for UE ID and Serving Network ID under the Header or Body IE configuration within the Cat 3 – Previous Location Check section of the Security Countermeasure tab in the SEPP CNC Console.
  3. Check that the MCC and MNC values (configured in either the header or body) match the serving network name. These values are returned in the UDR response, so also confirm that the UDR response is successful.
  4. If Cat 3 – Previous Location Check is enabled, ensure the SUPI is present in the incoming request message.
  5. Verify the following:
    • Confirm the UDR discovery procedure completes successfully.
    • Ensure the FQDN or IP of the UDR is reachable.
    • Verify the Coherence service is up and running.
    • Make sure the SUPI falls within the IMSI range defined in the UDR profile.
  6. Ensure that DNS resolution is properly configured for the UDR discovery call, specifically for the pn32f-svc service used in subscription use cases.