Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Manage Cloud-Native Router Controller and Cloud-Native Router vRouter

SUMMARY This topic contains instructions for how to access the cloud-native router CLIs, how to run operational commands in cRPD and vRouter containers, and how to remove cloud-native router.

Access the Cloud-Native Router CLIs

You can access the cloud-native router's CLI to monitor the router's status and to make configuration changes. In this section we provide the commands that you use to access the cRPD and vRouter CLIs and provide some examples of show commands.

Because the cloud-native router controller element runs as a Pod in a Kubernetes (K8s) cluster, you must use K8s commands to access the CLI. We provide an example below. We do not provide specific directory paths in our examples so you can copy and paste the commands into your server.

Access the Cloud-Native Router Controller (cRPD) CLI

In this example we list all of the K8s Pods running on the K8s host server. We use that output to identify the cRPD Pod that hosts the cloud-native router controller container. We then connect to the CLI of the cloud-native router controller and run some show commands.

List the K8s Pods Running in the Cluster

The only Pod that has cRPD in its name is the kube-crpd-worker-ds-npbjq. Thus, this is the name of the Pod we will use to access the cRPD CLI.

Connect to the cRPD CLI

The kubectl command that allows access to the controller's CLI has the following form:

kubectl exec -n <namespace> -it <cRPD worker Pod name> -- bash

In practice, you substitute values from your system for the values contained between angle brackets (<>). For example:

The result of the above command should appear similar to:

At this point, you have connected to the shell of the cloud-native router. Just as with other Junos-based shells, you access the operational mode of the cloud-native router the same way as if you were connected to the console of a physical Junos OS device.

root@jcnr-01:/# cli

Example Show Commands

In the following examples, we remove the prompt, root@jcnr-01>, so you can copy and paste the commands into your system without editing them.

Access the Cloud-Native Router vRouter CLI

In this example we list all of the K8s Pods running on the K8s host server. We use that output to identify the vRouter Pod that hosts the cloud-native router vrouter-agent container. We then connect to the CLI of the vRouter-agent and run a show command to list the available interfaces.

List the K8s Pods Running in the Cluster

Connect to the Cloud-Native Router vRouter CLI

The kubectl command that allows access to the controller's CLI has the following form:

kubectl exec -n contrail -it <contrail-vrouter-masters-pod> -- bash

In practice, you substitute values from your system for the values contained between angle brackets (<>). For example:

The output of this command should look similar to:

At this point, you have connected to the vRouter's CLI. You can run commands in the CLI to learn about the state of the vRouter. For example, the command shown below allows you to see which interfaces are present on the vRouter.

Remove the Juniper Cloud-Native Router

We do not provide specific directory names for the commands in this topic. This allows you to copy and paste the commands from this document onto your server.
Uninstall the Juniper Cloud-Native Router.