5.2.25.1 configMgrNoHealthyNIFAlert

Table 5-119 configMgrNoHealthyNIFAlert

Field Details
Trigger Condition Raised when there is no healthy NIF found from NRF discovery for NIF.
Severity Critical
Alert details provided
Expression: 
(sum(ocsepp_nif_registration_status{namespace="sepp-namespace"}) by (namespace)) <= 0
OID 1.3.6.1.4.1.323.5.3.46.1.2.4070
Metric Used ocsepp_network_id_validation_header_failure_total
Resolution Cleared when there is at least one healthy NIF for forwarding traffic,

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.