8 Troubleshooting Information

If you experience issues while using NSSF, refer to the topics below:

Verifying Environment

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 NSSF Installation while Installing using helm

1. If the user is getting the following error:
   failed to parse ocnssf-custom-values-1.3.0.yaml: error converting YAML to JSON: yaml. Then

   1. The ocnssf-custom-values-1.3.0.yaml may not be created properly.
   2. The tree structure may not be followed.
   3. There may be tab spaces in the file.

   Verify that the ocnssf-custom-values-1.3.0.yaml is proper

   Refer Network Slice Selection Function (NSSF) Cloud Native Installation Guide .

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

   Helm status can be checked using following command :

   helm status <helm release name>

Verifying NSSF Installation

To verify whether the NSSF installation is successful or not, check:

1. Verify NSSF specific pods are working as expected by executing following command

   kubectl get pods -n <ocnssf_namespace>

   Check whether all the pods are up and running.

   Sample output:

   NAME                            READY   STATUS  RESTARTS  AGE
   ocnssf-appinfo-55bcc48477-knc8t             1/1   Running    0     317s
   ocnssf-config-server-5d8c7968fc-d8q9z       1/1   Running    0     317s
   ocnssf-egress-595948cd5-d6hw2               1/1   Running    0     317s
   ocnssf-ingress-54c8b668c5-nlcbf             1/1   Running    0     317s
   ocnssf-nrf-clientservice-7d9c64f566-z9dnw   1/1   Running    0     317s
   ocnssf-nsavailability-8646844976-8pljq      1/1   Running    0     317s
   ocnssf-nsconfig-5d755b7865-nh4r9            1/1   Running    0     317s
   ocnssf-nsdb-585f7bd7d-bwwjd                 1/1   Running    0     317s
   ocnssf-nsselection-56674986bf-fmswv         1/1   Running    0     317s
   ocnssf-nssubscription-76478c6c84-fdz7f      1/1   Running    0     317s
   ocnssf-performance-6d75c7f966-57fgt         1/1   Running    0     317s
   
   

2. If status of any pod is shown as ImagePullBackOff or ErrImagePull then it can be due to:
   1. Incorrect ImageName provided in ocnssf-custom-values-1.3.0.yaml.

      Then, double check the image name and tags in ocnssf-custom-values-1.3.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 ocnssf-custom-values-1.3.0.yaml
   2. MySQL servers may not be configured properly according to the pre-installation steps mentioned in Network Slice Selection Function (NSSF) Cloud Native Installation Guide .

Debugging General CNE

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

Collecting NSSF Logs

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

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

Example:

kubectl logs ocnssf-nsselection-57cff5665c-skk4l -n ocnssf > ocnssf_logs1.log