3.2.11 SCPUpstreamResponseTimeout

Table 3-15 SCPUpstreamResponseTimeout

Field	Description
Severity	info
Conditions	idelta(ocscp_metric_upstream_response_timeout_total[2m]) > 0
OID used for SNMP Traps	1.3.6.1.4.1.323.5.3.35.1.2.7011
Description	Alert is raised when Upstream connection to a producer NF fails
Recommended Actions	Cause: When a producer NF is down, not reachable, or latency is high. Diagnostic Information: Check whether the producer NF is up and network connectivity to the producer NF is established by using one of the following steps: Run the ping command from primary/secondary nodes by using IP of producer NF. Example of a ping command: ping <IPAddress>. Run the ping command from inside the pod, if FQDN of producer NF 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>. Check the upstream response time by using the following metric and determine if upstream is taking too long to respond: ocscp_metric_upstream_service_time (producer FQDN) Recovery: This alert is cleared automatically in the next scrape interval if the system does not observe any error. For any assistance, contact My Oracle Support.