Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

JDM CLI Overview

date_range 24-Nov-23

Understanding the JDM CLI

Junos Device Manager (JDM) can be configured using the JDM CLI. In most cases, you are logged into the JDM CLI by default when you access a disaggregated Junos OS platform.

The JDM CLI is similar to the Junos OS CLI in look and feel. It provides the same value-added facilities as the Junos OS CLI, which include:

  • Separate configuration and command modes

  • Commit check

  • Configuration save, restore, and rollback

  • NETCONF and YANG support

The JDM CLI is based on the Junos OS CLI and follows many of its processes and procedures. Like Junos OS, the JDM CLI has an operational mode and configuration mode. You use the configure command to go from operational mode to configuration mode, and the exit command to exit configuration mode. Many operational mode commands—such as show and request commands—are available in the JDM CLI and the Junos OS CLI. Many configuration commands available in the Junos OS CLI are also available in the JDM CLI, and are often entered using the same command at the same hierarchy level.

If you are placed in the JDM shell for any reason, such as if you logged in to the disaggregated Junos OS platform as the root user, enter the cli command from the JDM shell prompt to get to the JDM CLI prompt:

content_copy zoom_out_map
root# cli
 root@jdm>

Accessing the JDM Shell, JDM CLI, and JCP Prompts in a Disaggregated Junos OS Platform

This topic describes how to access the JDM shell, JDM CLI, and JCP prompts in a disaggregated Junos OS platform.

It contains the following sections:

Accessing the JDM CLI

You are in operational mode in the JDM CLI if you see the @jdm> prompt. The JDM CLI also includes the configuration prompt @jdm#, which can be accessed by entering the configure command at the JDM CLI operational mode prompt.

By default, most logins to a disaggregated Junos OS platform take the user to the operational mode in the JDM CLI prompt.

The JDM CLI prompt can also be accessed from the JDM shell.

To access the JDM CLI from the JDM shell, enter the cli command at the JDM shell prompt:

content_copy zoom_out_map
root@jdm:~# cli
root@jdm> 

Accessing the JDM Shell

By default, you are placed in the JDM shell when you login to the console port as the root user. The JDM shell uses the ~# prompt.

To access the JDM shell from the JDM CLI, enter the start shell command at the JDM CLI prompt:

content_copy zoom_out_map
root@jdm> start shell
jdm:~#

Accessing the JCP Prompt from the JDM CLI

To access the JCP prompt from the JDM CLI, enter the ssh vjunos0 command at the JDM CLI prompt:

content_copy zoom_out_map
root@jdm> ssh vjunos0
The authenticity of host 'vjunos0 (192.168.1.2)' can't be established.

ECDSA key fingerprint is 18:83:1f:95:88:db:1b:75:9f:07:ce:2c:4a:45:a3:b0.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'vjunos0,192.168.1.2' (ECDSA) to the list of known hosts.
Password:
Last login: Thu Oct  8 09:47:42 2015
--- JUNOS 15.1I20150824_0501 built 2015-08-24 05:13:01 UTC

root@:RE:0% cli
root>

Accessing the Hypervisor from the JDM CLI

To access the Hypervisor from the JDM CLI, enter the ssh hypervisor statement at the JDM CLI prompt:

content_copy zoom_out_map
root@jdm> ssh hypervisor
Last login: Sun Jan 18 15:01:55 2015 from jdm

Note:

Only a root user can use this option.

Accessing the ipsec-nm from the JDM CLI

To access the ipsec-nm from the JDM CLI, enter the ssh ipsec-nm statement at the JDM CLI prompt:

content_copy zoom_out_map
root@jdm> ssh ipsec-nm
Last login: Sun Jan 18 15:01:55 2015 from jdm

root@ipsec-nm: % cli
root@ipsec-nm> 
footer-navigation