Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Set Up Junos PyEZ Managed Nodes

Junos PyEZ is a Python library that enables you to manage and automate Junos devices. You do not need to install any client software on the nodes in order to use Junos PyEZ to manage the devices. Also, Python is not required on the managed devices, because Junos PyEZ utilizes NETCONF and the Junos XML APIs to perform operations on a device.

You can use Junos PyEZ to manage Junos devices using any user account that has access to the device. You can explicitly define the user when creating a new instance of the jnpr.junos.device.Device class, or if you do not specify a user in the parameter list, the user defaults to $USER. When you use Junos PyEZ to access and manage Junos devices, Junos OS user account access privileges are enforced. The class configured for the Junos OS user account determines the permissions. Thus, if you use Junos PyEZ to load configuration changes on a device, the user must have permissions to change the relevant portions of the configuration.

Junos PyEZ enables you to connect directly to a Junos device using a serial console connection, telnet, or a NETCONF session over SSH. To telnet directly to a device, you must first configure the Telnet service on the managed device. To manage devices through a NETCONF session over SSH, you must enable the SSH or NETCONF-over-SSH service on the managed device and ensure that the device meets requirements for SSHv2 connections. You do not need to configure these services if the client application connects to the device through a separate console server.

This topic outlines the requirements and required configuration on Junos devices when using Junos PyEZ to access the device using the different connection protocols.

Enable NETCONF over SSH

To enable the NETCONF-over-SSH service on the default port (830) on a Junos device:

  1. Configure the NETCONF-over-SSH service.

    It is also possible to reach the NETCONF-over-SSH service on TCP port 22 by configuring both the netconf ssh and ssh statements at the [edit system services] hierarchy level. The ssh statement enables SSH access to the device for all users and applications. However, we recommend using the default NETCONF port for NETCONF operations so you can more easily identify and filter NETCONF traffic.

  2. Commit the configuration.

Satisfy Requirements for SSHv2 Connections

The NETCONF server communicates with client applications within the context of a NETCONF session. The server and client explicitly establish a connection and session before exchanging data, and close the session and connection when they are finished. Junos PyEZ accesses the NETCONF server using the SSH protocol and standard SSH authentication mechanisms. When you use Junos PyEZ to manage Junos devices, the most convenient way to access the devices is to configure SSH keys.

To establish an SSHv2 connection with a Junos device, you must ensure that the following requirements are met:

  • The NETCONF service over SSH is enabled on each device where a NETCONF session will be established.

  • The client application has a user account and can log in to each device where a NETCONF session will be established.

  • The login account used by the client application has an SSH public/private key pair or a text-based password configured.

  • The client application can access the public/private keys or text-based password.

For additional information about enabling NETCONF on a Junos device and satisfying the requirements for establishing an SSH session, see the NETCONF XML Management Protocol Developer Guide.

Configure Telnet Service

Junos PyEZ applications can telnet to a Junos device, provided that the Telnet service is configured on the device. Configuring Telnet service for a device enables unencrypted, remote access to the device.


Because telnet uses clear-text passwords (therefore creating a potential security vulnerability), we recommend that you use SSH.

To enable Telnet service:

  1. Configure the service.
  2. (Optional) Configure the connection limit, rate limit, and order of authentication, as necessary.
  3. Commit the configuration.