3.2.62 SCPPeerSeppUnhealthy

Table 3-65 SCPPeerSeppUnhealthy

Field Details
Description Peer Sepp is marked unhealthy
Summary 'Peer Sepp is marked unhealthy. seppFqdn: {{$labels.ocscp_sepp_fqdn}}, namespace: {{$labels.namespace}}, podname: {{$labels.pod}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}'
Severity Info
Condition

This alert is raised when peer SEPP is marked unhealthy.

ocscp_sepp_unhealthy > 0
OID 1.3.6.1.4.1.323.5.3.35.1.2.7028
Metric Used ocscp_sepp_unhealthy
Recommended Action

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

Diagnostic Information:
  1. Check transport failures and routing errors on peer SCP.
  2. Run the ping command from primary or secondary 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.