3.2.22 SCPNrfRegistrationFailureForRegionOrSetId
Table 3-26 SCPNrfRegistrationFailureForRegionOrSetId
| Field | Description |
|---|---|
| Description | 'SCP Registration Failure for Region Or SetId: {{$labels.nrfRegionOrSetId}}' |
| Summary | 'SCP Registration Failure for Region Or SetId: {{$labels.nrfRegionOrSetId}}, namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}},scpFqdn: ' {{$labels.scpFqdn}} ', timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}' |
| Severity | Major |
| Conditions | This alert is raised when SCP registration fails. This
alert is labeled with specific nftype, nrfRegionOrSetId, and
auditmethod.
increase(ocscp_subscription_nrf_registration_failure_total[2m]) > 0 |
| OID used for SNMP Traps | 1.3.6.1.4.1.323.5.3.35.1.2.2003 |
| Metric Used | ocscp_subscription_nrf_registration_failure_total |
| Recommended Actions |
Cause: When the registration 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:
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>. Sample logs:
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. |