3.2.23 SCPNrfHeartbeatFailureForRegionOrSetId

Table 3-27 SCPNrfHeartbeatFailureForRegionOrSetId

Field Description
Description Alerts is raised when SCP Heartbeat fails.
Summary SCP Heartbeat to NRF Failure for Region Or SetId: {{$labels.nrfRegionOrSetId}}, namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}},scpfqdn: {{$labels.ocscp_fqdn}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}
Severity Major
Conditions increase(ocscp_subscription_nrf_heartbeat_failures_total[2m]) > 0
OID used for SNMP Traps 1.3.6.1.4.1.323.5.3.35.1.2.2004
Recommended Actions

Cause: When the Heartbeat fails for an NF Type with NRF.

Diagnostic Information:

Check whether NRF is up. To check the NRF status, see the Oracle Communications Cloud Native Core, Network Repository Function User Guide.

Check whether the NRF is reachable or not by using one of the following steps:
  • Run the ping command from primaryor secondary nodes by using IP of NRF. Example of a ping command: ping <IPAddress>.
  • Run the ping command from inside the pod if FQDN of NRF is used.
  • Instead of using ping, you can collect tcpdump for ensuring the connectivity. Example of a tcpdump: tcpdump -w capture.pcap -i <pod interface>.

Check scp-worker logs to find any error response from NRF. If there are error responses, monitor NRF logs: kubectl logs <pod name> -n <namespace>.

Recovery: This alert is cleared automatically when NRF is up and running or errors are corrected for received error responses.

For any assistance, contact My Oracle Support.