Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Troubleshoot Deployment Issues

SUMMARY This topic provides information about how to troubleshoot deployment issues using Kubernetes commands and how to view the cloud-native router configuration files.

Troubleshoot Deployment Issues

This topic provides information on some of the issues that might be seen during deployment of the cloud-native router components and provides a number of Kubernetes (K8s) and shell commands that you run on the host server to help determine the cause of deployment issues.

Table 1: Investigate Deployment Issues
Potential issue What to check Related Commands

Image not found

Check if registry is accessible, image tags are correct

  • kubectl -n jcnr describe pod <crpd-pod-name>
Initialization errors

Check if jcnr-secrets is loaded and has a valid license key

cat /var/run/jcnr/juniper.conf

Confirm that root password and license key are present

cRPD Pod in CrashLoopBackOff state
  • Check if startup/liveness probe is failing or vrouter pod not running

  • rpd-vrouter-agent gRPC connection not UP

  • Composed configuration is invalid or config template is invalid

  • kubectl get pods -A
    kubectl -n jcnr describe pod <crpd-pod-name>
  • See Access the Cloud-Native Router CLIs to enter the cRPD CLI and run the following command:

    show krt state channel vrouter
  • cat /var/run/jcnr/juniper.conf

vRouter Pod in CrashLoopBackOff state

Check the contail-k8s-deployer pod for errors
kubectl logs contrail-k8s-deployer-<pod-hash> -n contrail-deploy

View Cloud-Native Router Controller Configuration

The cloud-native router deployment process creates a configuration file for the cloud-native router controller (cRPD) as a result of entries in the values.yaml file. You can view this configuration file to see the details of the cRPD configuration. To view the cRPD configuration:

  1. Navigate to the /var/run/jcnr folder to access the configuration file details.
  2. View the contents of the configuration file.
    root@server:/var/run/jcnr#vi juniper.conf

View Log Files

SUMMARY In this topic, we use the default log_path directory, /var/log/jcnr/, and the default syslog_notifications directory, /var/log/jcnr/jcnr-notifications.json. You can change the location of the log files by changing the value of the log_path: or syslog_notifications: keys in the values.yaml file prior to deployment.
Navigate to the following path and issue the ls command to list the log files for each of the cloud-native router components.