3.2.42 SCPSeppRoutingFailed

Table 3-46 SCPSeppRoutingFailed

Field Details
Description Routing towards SEPP failed
Summary Routing towards SEPP failed. sepp_fqdn: {{$labels.ocscp_sepp_fqdn}}, scpfqdn: {{$labels.scp_fqdn}}, namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}'
Severity Minor
Condition This alert is raised when routing towards SEPP fails.

ocscp_metric_sepp_routing_attempt_fail_current == 1
OID 1.3.6.1.4.1.323.5.3.35.1.2.7026
Metric Used ocscp_metric_sepp_routing_attempt_fail_current
Recommended Action

Cause: Inter-PLMN routing failed for the selected SEPP instances.

Diagnostic Information:
  1. Check whether selected SEPP is up and healthy.
  2. Check if selected SEPP is reachable.
  3. Use the ping command from primary or secondary nodes using IP of SEPP.

    Sample ping command is ping <IpAddress>

  4. If FQDN of SEPP is used, try ping command from inside the pod.
  5. Alternative to ping, collect tcpdump for ensuring proper connectivity.

    Sample command: tcpdump -w capture.pcap -i <pod interface>

  6. Check scp-worker logs for any error response from selected SEPP. If there are error responses, monitor selected SEPP logs by running this command: kubectl logs <pod name> -n <namespace>

Recovery: This alert clears automatically when routing is successful for selected SEPP.

For any assistance, contact My Oracle Support.