5.2.22.2 SEPPConnectionFailureN32IGWAlert

Table 5-103 SEPPConnectionFailureN32IGWAlert

Field Details
Trigger Condition Connection failure occurs for incoming traffic at N32 Ingress Gateway
Severity Major
Alert details provided
Summary: 
namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Incoming connection failure on n32-ingress-gateway due to {{ $labels.error_reason }}
Expression: 
sum(increase(oc_ingressgateway_connection_failure_total{namespace="sepp-namespace",app="n32-ingress-gateway"}[5m]) >0 or (oc_ingressgateway_connection_failure_total{namespace="sepp-namespace",app="n32-ingress-gateway"} unless oc_ingressgateway_connection_failure_total{namespace="sepp-namespace",app="n32-ingress-gateway"} offset 5m )) by (namespace,app) > 0
OID 1.3.6.1.4.1.323.5.3.46.1.2.4044
Metric used oc_ingressgateway_connection_failure_total
Resolution After resolving the reason for connection failure, this alert will be removed.
Possible resolutions:
  1. If SSLHandshakeException or SSLException error is observed, verify that both the server and client have one common TLS version supported.
  2. If a common TLS version is supported, then check if both the client and server have compatible cipher suites.
  3. Also, ensure that CA certificate of server must be present inside client's truststore.
  4. For more details, refer 'Support for TLS 1.3' section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Troubleshooting Guide.