5.4.13.8 OcnrfTotalNFsRegisteredAtSegmentBelowCriticalThreshold

Table 5-113 OcnrfTotalNFsRegisteredAtSegmentBelowCriticalThreshold

Field Details
Description The alert is raised when the number of NFs registered at the segment is below the configured critical threshold.
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The number of NFs registered at the segment is below critical threshold'
Severity Critical
Condition The number of NFs registered at the segment is below critical threshold.

Note: This alert is triggered when the registered NF count is below 2. This default value can be modified in the ocnrf_alertrules_24.2.6.yaml or ocnrf_alertrules_promha_24.2.6.yaml file depending on Prometheus version.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7105
Metric Used ocnrf_nf_registered_count
Recommended Actions

The alert is cleared when the number of registered NFs in the segment is above the critical threshold.

Steps:

  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running in all NRF sets.
  2. Check if the Ingress Gateway pod is up and running in all NRF sets. 
    kubectl get po -n <namespace>
  3. Validate that the CDS synchronization with remote NRF sets is successful. Validate below alerts are not present in the system:
    1. OcnrfSyncFailureFromAllNrfsOfAnyRemoteSet
    2. OcnrfSyncFailureFromAllNrfsOfAllRemoteSets
  4. Check for registration pod logs on Kibana for ERROR WARN logs.
  5. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use the CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using the Data Collector tool, see Oracle Communications Cloud Native Core, cnDBTier User Guide.

Available in OCI No