1. Cloud Native Security Edge Protection Proxy (SEPP) Installation Guide
  2. SEPP Troubleshooting Information

6 SEPP Troubleshooting Information

This section provides information to troubleshoot the common error which can be encountered during the installation and upgrade of SEPP:

Error Trigger based debugging

The following table lists the SEPP Alarms, cause for the errors and the solution:
Event Type Severity Cause of the error Steps to get out of error scenario
SEPPCn32cHandshakeFailureAlert Alert Major Handshake procedure has failed on Consumer sepp for peer sepp.

Check for handshake failure reason.

Based on the handshake failure reason, configure roaming partner profile.

If error is at TCP level, then check fqdn/ip/certificates in gateways.

Re-Initiate the handshake procedure.
SEPPPn32cHandshakeFailureAlert Alert Major Handshake procedure has failed on Producer sepp for peer sepp.

Check for handshake failure reason.

Based on the handshake failure reason, configure roaming partner profile properly.
SEPPN32fRoutingFailure Alert Warning N32f service not able to forward message

Check whether context is established between sepps.

If not, then initiate the handshake procedure first.
SEPPPodMemoryUsageAlert Alert Warning Pod memory usage is above threshold ( 70% )  
SEPPPodCpuUsageAlert Alert Warning Pod CPU usage is above threshold ( 70% )  

The environment is not working as expected

Problem: The environment is not working as expected.

Solution:
  1. Check if kubectl is installed and working as expected.
  2. Check if kubectl version command works: This must display the versions of client and server.
  3. Check if $ kubectl create namespace test command works.
  4. Check if kubectl delete namespace test command works.
  5. Check if Helm is installed and working as expected.
  6. Check if helm version command works: This must display the versions of client and server.

Debugging of Installation while Installing using helm

Problem: The user is getting the error: failed to parse ocsepp-custom-values-1.4.0.yaml: error converting YAML to JSON: yaml.

Solution:

Verify the following:
  1. The ocsepp-custom-values-1.4.0.yaml may not be created properly.
  2. The tree structure may not be followed.
  3. There may be tab spaces in the file.
  4. Verify that the ocsepp-custom-values-1.4.0.yaml is proper

    Refer Security Edge Protection Proxy (SEPP) Cloud Native Installation Guide .

  5. If there is no error, helm installation will be deployed.

    Helm status can be checked using following command :

    helm status <helm release name>

SEPP Installation issues

Problem: The SEPP installation is not successful.

Solution:

  1. Verify if SEPP specific pods are working as expected by executing the following command:

    kubectl get pods -n <ocsepp _namespace>

    Check whether all the pods are up and running.

    Sample output:
    
NAME                                          READY   STATUS  RESTARTS     AGE
ocsepp-appinfo-7687997858-2vn4r               1/1     Running   0          20m
ocsepp-cn32c-svc-845f689879-r8zcr             1/1     Running   0          20m
ocsepp-cn32f-svc-6655cdf7bc-8sxrl             1/1     Running   0          20m
ocsepp-config-mgr-svc-6c8c5c968d-qqd4f        1/1     Running   0          20m
ocsepp-n32-egress-gateway-76bdbc7546-t7msc    2/2     Running   0          20m
ocsepp-n32-ingress-gateway-5545f455c-br2cv    2/2     Running   0          20m
ocsepp-ocpm-config-854dd8b7b5-j2lgg           1/1     Running   0          20m
ocsepp-plmn-egress-gateway-655886df4f-b9rl6   2/2     Running   0          20m
ocsepp-plmn-ingress-gateway-6586fbfc59-9f4lx  2/2     Running   0          20m
ocsepp-pn32c-svc-55d5748b76-p6p4t             1/1     Running   0          20m
ocsepp-pn32f-svc-846558995b-5wvpt             1/1     Running   0          20m
ocsepp-sepp-nrf-client-nfmanagement
            -7c94cf8dbf-lxbsb                 1/1     Running   0          20m
  2. If status of any pod is shown as ImagePullBackOff or ErrImagePull then it can be due to:
    1. Incorrect ImageName provided in ocsepp-custom-values-1.4.0.yaml.

      Then, double check the image name and tags in ocsepp-custom-values-1.4.0.yaml.

    2. Docker registry is incorrectly configured.

      Then, check docker registry is properly configured in all master and slave nodes.

  3. If RESTARTS count of the pods is continuously increasing, then it can happen due to the following reasons:
    1. MySQL primary and secondary hosts may not be configured properly in ocsepp-custom-values-1.4.0.yaml
    2. MySQL servers may not be configured properly according to the pre-installation steps mentioned in Security Edge Protection Proxy (SEPP) Cloud Native Installation Guide .

Debugging General CNE

Problem: The environment is not working as expected

Solution:

Execute the command kubectl get events -n <ocsepp_namespace>to get all the events related to a particular namespace.

Collect the SEPP Logs to check the error scenarios

Problem: The error scenarios are checked by collecting the SEPP logs.

Solution:

The following commands must be executed to get the logs from sepp specific pods:

  1. Fetch the list of all pods by executing kubectl get pods -n <ocsepp_namespace>
  2. Collect the logs from the pod and redirect to file by executing kubectl logs <pod_name> -n <ocsepp_namespace> > <Log File>

Example:

kubectl logs ocsepp-nsselection-57cff5665c-skk4l -n ocsepp > ocsepp_logs1.log