5.1.3 NnrfNFManagementServiceDown

Table 5-4 NnrfNFManagementServiceDown

Field Details
Description 'OCNRF Nnrf_Management service <nfregistration|nfsubscription|nrfauditor> is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : NFManagement service is down'
Severity Critical
Condition This alert is raised when either NFRegistration, NFSubscription, or NrfAuditor services are unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7018
Metric Used ''up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions The alert is cleared when all the Nnrf_NFManagement services nfregistration, nfsubscription, and nrfauditor are available.

Steps:

  1. Check if NfService specific alerts are generated to understand which service is down.

    Either some or all of the following alerts are generated based on which services are down

    • OcnrfRegistrationServiceDown
    • OcnrfSubscriptionServiceDown
    • OcnrfAuditorServiceDown
  2. To check the orchestration logs for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  3. Check for the POD’s status if they are in “Running” state using the following command:
    $ kubectl get pod –n <namespace>
    If it is not in “Running” state, capture the pod logs and events by running the following command:
    $ kubectl get events --sort-by=.metadata.creationTimestamp -n <namespace>
  4. Refer to the application logs on Kibana and filter based on aforementioned service names. Check for ERROR WARNING logs for each of these services.
  5. Check the database status. For more information on how to check the database status, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  6. Refer to the application logs on Kibana and filter the service appinfo, check for the service status of the nfregistration, nfsubscription, and nrfauditor services.
  7. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

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

Available in OCI No