3.2.5 SCPRoutingFailedForProducer

Table 3-9 SCPRoutingFailedForProducer

Field	Description
Severity	Info
Conditions	increase(ocscp_metric_routing_attempt_fail_total{app_kubernetes_io_name="scp-worker"}[2m]) > 0
OID used for SNMP Traps	1.3.6.1.4.1.323.5.3.35.1.2.7005
Description	Notify that Routing failed for producer. Provides detail such as NFService Type, NFType, Locality, producer FQDN and value.
Recommended Actions	Cause: When routing fails to select a producer NF due to unavailability of routing rules for an NF service or producer. Diagnostic Information: Check whether the routing rules are configured for the NF for which routing failed. Check the notification logs for any error while processing the notification of the NF for which routing failed. Then, run the following command to get the notification logs: kubectl logs <podname> -n <namespace> Check whether the NF is reachable or not by using one of the following steps: Run the ping command from primary/secondary nodes using IP of service. Example of a ping command: ping <IPAddress>. Run the ping command from inside the pod, if FQDN of service is used. Instead of using the ping command, you can collect tcpdump for ensuring the connectivity. tcpdump must be run on the debug container for scp-worker microservice. Example of a tcpdump: tcpdump -w capture.pcap -i <pod interface>. Recovery: This alert is cleared automatically when the routing is complete for a producer NF or no more traffic is received in the next Promethues scrape interval. Check if the NF is deregistered. Register the NF to create routing rules if rules do not exist. For any assistance, contact My Oracle Support.