5.2.19.1 pn32fTimeUnauthLocChkValFailAlrtMinor

Table 5-92 pn32fTimeUnauthLocChkValFailAlrtMinor

Field Details
Trigger Condition Triggered in case of a minor failure for Cat-3Time Unauthenticated Location Check.
Severity Minor
Alert Details Provided

Summary

namespace: {{ $labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}
Expression:
 sum(increase(ocsepp_time_unauthenticated_location_validation_failure_total{namespace="sepp-namespace"}[2m]) or ocsepp_time_unauthenticated_location_validation_failure_total{namespace="sepp-namespace"} unless ocsepp_time_unauthenticated_location_validation_failure_total{namespace="sepp-namespace"} offset 2m ) by (namespace,nf_instance_id,app,pod) >=1 and sum(increase(ocsepp_time_unauthenticated_location_validation_failure_total{namespace="sepp-namespace"}[2m]) or ocsepp_time_unauthenticated_location_validation_failure_total{namespace="sepp-namespace"} unless ocsepp_time_unauthenticated_location_validation_failure_total{namespace="sepp-namespace"} offset 2m ) by (namespace,nf_instance_id,app,pod) <=10
OID 1.3.6.1.4.1.323.5.3.46.1.2.4055
Metric Name ocsepp_time_unauthenticated_location_validation_failure_total
Resolution The alert gets cleared when the failure count is above 10.

Possible Resolutions:

  1. Ensure that the Cat-3 Time Check for Roaming Subscribers is enabled at both the global and remote levels. For configuration issues and detailed analysis, refer to Oracle Communications Cloud Native Core, Security Edge Protection Proxy Troubleshooting Guide .
  2. Confirm that SUPI or SUCI is included in the incoming message. The UDM and UDR discovery procedures (FQDN or IP of UDR) must be successful and reachable.
  3. Verify the following:
    • Verify that the Coherence service is operational.
    • Ensure the SUPI falls within the IMSI range defined in the UDR profile.
    • Confirm that the routing indicator from the SUCI matches the routingIndicator in the UDM profile.
  4. DNS Resolution Confirm proper DNS resolution for the UDR discovery call, particularly for the pn32f-svc service used in subscription scenarios.
  5. Ensure the supi Or Suci and servingNetworkName (including MCC/MNC) are present in the NAUSF request JSON body. Verify that the UDR response is successful and that the servingNetworkName values match.
  6. If the request is rejected, verify whether the rejection might be caused by mismatched units of measurement.