5.2.17.2 SEPPN32fNetworkIDValidationBodyIEFailureAlert

Table 5-85 SEPPN32fNetworkIDValidationBodyIEFailureAlert

Field Details
Trigger Condition If Network ID Validation for Body fails, this metrics will be pegged and corresponding alert will be raised.
Severity Major
Alert details provided Summary:

'namespace: {{ $labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Network ID Body Validation has failed because {{ $labels.cause }}'

Expression:

sum(increase(ocsepp_network_id_validation_body_failure_total{namespace="sepp-namespace"}[2m]) >0 or (ocsepp_network_id_validation_body_failure_total{namespace="sepp-namespace"} unless ocsepp_network_id_validation_body_failure_total{namespace="sepp-namespace"} offset 2m )) by (namespace, remote_sepp_name, nf_instance_id, peer_fqdn, plmn_identifier, app, resource_uri, pod) > 0
OID 1.3.6.1.4.1.323.5.3.46.1.2.4012
Metric Used ocsepp_network_id_validation_body_failure_total
Resolution The alerts gets cleared when the count goes below 0.

Possible Resolutions:

  1. Review CN32F logs for error codes SEPP-CN32FSEPP-ERROR-0013 or SEPP-CN32FSEPP-ERROR-0014 (indicating the incoming request was rejected with error code 406 by the CN32F microservice).
  2. Similarly, check PN32F logs for error codes SEPP-PN32FSEPP-ERROR-0016 or SEPP-PN32FSEPP-ERROR-0017 (indicating the request was rejected with error code 406 by the PN32F microservice).
  3. Ensure the correct regular expression is configured under Header/Body IE in the Cat 2 – Network ID Validation section (located under the Security Countermeasure tab in SEPP).
  4. Confirm that the PLMN ID specified in the request headers is included in the SEPP’s configured PLMN ID List.
  5. For issues related to invalid PLMN ID configurations in the body or headers, refer to 'Cat-2 Network ID Validation Feature' section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Troubleshooting Guide.