5.2.2.1 SEPPCn32cHandshakeFailureAlert

Table 5-26 SEPPCn32cHandshakeFailureAlert

Field Details
Trigger Condition Handshake procedure has failed on Consumer SEPP
Severity Major
Alert details provided Summary
'namespace: {{ $labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first |
      value | humanizeTimestamp }}{{ end }}'
Expression:
sum(increase(ocsepp_n32c_handshake_failure_attempts_total{app="cn32c-svc",namespace="sepp-namespace"}[5m]) >0 or
        (ocsepp_n32c_handshake_failure_attempts_total{app="cn32c-svc",namespace="sepp-namespace"} unless
        ocsepp_n32c_handshake_failure_attempts_total{app="cn32c-svc",namespace="sepp-namespace"} offset 5m )) by
      (namespace,remote_sepp_name,nf_instance_id,peer_fqdn,app,container,reason)
      > 0
OID 1.3.6.1.4.1.323.5.3.46.1.2.2001
Metric Used ocsepp_n32c_handshake_failure_attempts_total filtered by app=cn32-svc
Resolution 1 The alert gets cleared when the N32C Handshake is established after successful TCP connection to remote SEPP.

Failure reason: Release name used while helm installation is other than ocsepp-release.

Error Verification: Check the failure reason in the alert. If the failure reason is 404 –route not found or Route not found, follow the recovery steps:

  1. Run the following command to get pod details:

    $ kubectl get pods –n <namespace>

    Example:
    
# kubectl get pods -n csepp
NAME                                                 READY   STATUS                  RESTARTS   AGE
ocsepp-release-appinfo-6cdc48fc47-c9gfv              1/1     Running                 0          8d
ocsepp-release-cn32c-svc-6547db777d-76gwd            1/1     Running                 0          8d
ocsepp-release-cn32f-svc-7cd54bdf68-czbnb            1/1     Running                 0          8d
ocsepp-release-config-mgr-svc-79c95d4b9d-8stk7       1/1     Running                 0          8d
ocsepp-release-n32-egress-gateway-54c658b947-s5f9m   0/2     Pending                 0          23h
ocsepp-release-n32-egress-gateway-54c658b947-scvvp   2/2     Running                 0          7d23h
ocsepp-release-n32-ingress-gateway-777c68cb9-8jsdc   0/2     Pending                 0          23h
ocsepp-release-n32-ingress-gateway-777c68cb9-98t7x   0/2     Init:ImagePullBackOff   0          23h
ocsepp-release-pn32c-svc-58bff857f-jmfdd             1/1     Running                 0          8d
ocsepp-release-pn32f-svc-784d5c7568-rh24g
  2. Run the following command to navigate to the pod:

    $ kubectl exec –it <config-mgr-pod name> –n <namespace> bash

    Example:

    $ kubectl exec -it ocsepp-release-config-mgr-svc-79c95d4b9d-8stk7 -n csepp bash
  3. Run the command to get the existing route details present on N32 Egress Gateway:

    curl -X GET http://<config-manager-service-name>:9090/sepp/nf-common-component/v1/egw/n32/routesconfiguration

    Example:

    curl -X GET http://ocsepp-release-config-mgr-svc:9090/sepp/nf-common-component/v1/egw/n32/routesconfiguration
  4. If this output is null, add the configuration details in config-mgr-svc deployment.

    For more information about the configuration details, see the Deployment Configuration for Config-mgr-svc section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation Guide.

  5. After the config-mgr-svc pod is restarted, run the step1 to step3 again. After adding the configuration, rerun the curl command mentioned in step3 to get the route details.
  6. Delete and add the RemoteSepp and reinitiate the handshake.

    If the value is still null, contact My Oracle Support.
Resolution 2

The alert gets cleared when the N32C Handshake is established after successful TCP connection to remote SEPP.

Steps:

The failure reason is present in the alert.

Possible Resolutions:

  1. Disable the Remote SEPP.
  2. Delete the Remote SEPP.
  3. Update and reinitiate Handshake.