5.4.15.1 OcnrfMaxSlfAttemptsExhausted

Table 5-120 OcnrfMaxSlfAttemptsExhausted

Field Details
Description 'NF discovery request with fqdn {{$labels.NfProfileFqdn}} NF type {{$labels.NfType}} has exhausted maximum SLF attempts'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, NfProfileFqdn: {{$labels.NfProfileFqdn}}, NfType: {{$labels.NfType}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: The maximum slf attempts have exhausted.'
Severity Critical
Condition

NF discovery request with FQDN of the given NFType UDR has exhausted maximum SLF attempts. This alert is raised when the ocnrf_max_slf_attempts_exhausted_total metric is pegged.

Note: This alert is included if SLF selection from registered profiles is enabled.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7054
Metric Used 'ocnrf_max_slf_attempts_exhausted_total'
Recommended Actions

The alert is cleared automatically after 5 minutes.

Steps:
  1. Check logs in NF discovery pod to check the reason for SLF query failures.
  2. In DISCOVERED_SLF_CONFIG_MODE, make sure that SLFs are registered with valid IPV4, PV6, or FQDN information. Verify the same in the slfDiscoveredCandidateList from the slfOptions.
  3. In STATIC_SLF_CONFIG_MODE, verify if slfHostConfig details are configured correctly.

    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 Yes