5.2.1.1 SEPPN32fRoutingFailure

Table 5-22 SEPPN32fRoutingFailure

Field Details
Trigger Condition N32f service not able to forward message
Severity Info
Alert details provided Summary
namespace: {{ $labels.namespace}}, podname: {{ $labels.pod}}, timestamp: {{ with query
      "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}
Expression:
idelta(ocsepp_cn32f_requests_failure_total{namespace="sepp-namespace"}[2m]) > 0 or (ocsepp_cn32f_requests_failure_total{namespace="sepp-namespace"} unless ocsepp_cn32f_requests_failure_total{namespace="sepp-namespace"} offset 2m)
OID 1.3.6.1.4.1.323.5.3.46.1.2.4001
Metric Used ocsepp_cn32f_requests_failure_total
Resolution

The alert gets cleared when Consumer SEPP accepts request only if producer NF domain and PLMN match the Remote SEPP configured.

Steps:

The failure reason is present in the alert.

Possible Resolutions :

  1. Check whether the Remote SEPP is present in database.
  2. Validate the Remote SEPP PLMN which is configured.
  3. Validate the handshake is completed with the remote SEPP and context is present in database.
  4. Validate the producer NF Domain.
  5. Check whether the Remote SEPP Set for required Remote SEPP is present in the database.
  6. Check whether the N32F route is present in database (common_configuration table).