3.2.37 SCPUnhealthyPeerSCPDetected

Table 3-41 SCPUnhealthyPeerSCPDetected

Field Details
Description Next hop SCP is marked unhealthy
Summary 'Next hop SCP is marked unhealthy. peerscphost: {{labels.peerScpName}}, scpFqdn: {{labels.scpFqdn}} , namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} and value = {{ $value }} '
Severity Info
Condition This alert is raised when peer SCP is marked as unhealthy.

ocscp_peer_scp_unhealthy > 0
OID 1.3.6.1.4.1.323.5.3.35.1.2.7022
Metric Used ocscp_peer_scp_unhealthy
Recommended Action

Cause: The peer SCP is marked as unhealthy because of consecutive failure responses.

Diagnostic Information:
  1. Check transport failures and routing errors on the peer SCP.
  2. Run the ping command from primary or worker nodes using IP of Service.

    Sample command: ping <IPAddress>.

  3. If FQDN of service is used, run the ping command from inside the pod.
  4. If the pod does not support the ping command, get the debug container of SCP pod.
  5. If you do not want to use the ping command, collect tcpdump to establish the connection.

    Sample command: tcpdump -w capture.pcap -i <pod interface>

Recovery: This alert is automatically cleared after the degradation time is over. Degradation time = Number of consecutive degradations multiplied by configured base ejection.

For any assistance, contact My Oracle Support.