3.2.106 SCPPeerCustomRoamingProxyUnhealthy

Table 3-110 SCPPeerCustomRoamingProxyUnhealthy

Field Details
Description Peer Custom Roaming Proxy is marked unhealthy
Summary 'Peer Custom Roaming Proxy is marked unhealthy. custom_roaming_proxy_fqdn: {{$labels.ocscp_custom_roaming_proxy_fqdn}}, custom_roaming_proxy_nfType: {{$labels.ocscp_custom_roaming_proxy_nf_type},namespace: {{$labels.namespace}}, podname: {{$labels.pod}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}'
Severity Info
Condition

This alert is raised when peer Custom Roaming Proxy is marked unhealthy.

ocscp_worker_custom_roaming_proxy_unhealthy_current == 1
OID

1.3.6.1.4.1.323.5.3.35.1.2.15043
Metric Used ocscp_worker_custom_roaming_proxy_unhealthy_current
Recommended Action

Cause: The peer Custom Roaming Proxy is marked unhealthy because of consecutive failure responses.

Diagnostic Information:
  • Check transport failures and routing errors on peer SCP.
  • Use ping command (ping <IPAddress>) from primary or secondary nodes using IP address of the service.
  • If FQDN of the service is used, run the ping command inside the pod.
  • If the pod does not support ping command, use the Debug container of SCP pod.
  • Alternatively, collect tcpdump for ensuring proper connectivity.
    tcpdump -w capture.pcap -i <pod interface>

Recovery: This alert is automatically after the degradation time is over.

Degradation time = number of consecutive degradations * configured base ejection.

For any assistance, contact My Oracle Support.