Juniper Networks supports Ansible for managing devices running the Junos operating system (Junos OS and Junos Evolved). This collection is hosted on the Ansible Galaxy website under the collection juniper.device.
The juniper.device collection includes a set of Ansible modules that perform specific operational and configuration tasks on devices running Junos OS.
These tasks include: installing and upgrading Junos OS, provisioning new Junos devices in the network, loading configuration changes,
retrieving information, and resetting, rebooting, or shutting down managed devices. Please refer to the
INSTALLATION section for instructions on installing this collection.
Since Ansible version >= 2.1, Ansible also natively includes
core modules for Junos. The Junos modules included
in Ansible core have names which begin with the prefix junos_. The Junos modules included in this Juniper.device
collection have names starting with module types. These two sets of Junos modules can coexist on the same
Ansible control machine, and an Ansible playbook may invoke a module from either (or both) sets. Juniper Networks recommends
using the modules in juniper.device collection when writing new playbooks that manage Junos devices.
This juniper.device collection includes the following modules:
- command — Execute one or more CLI commands on a Junos device.
- config — Manipulate the configuration of a Junos device.
- facts — Retrieve facts from a Junos device.
- jsnapy — Execute JSNAPy tests on a Junos device.
- ping — Execute ping from a Junos device.
- pmtud — Perform path MTU discovery from a Junos device to a destination.
- rpc — Execute one or more NETCONF RPCs on a Junos device.
- software — Install software on a Junos device.
- srx_cluster — Add or remove SRX chassis cluster configuration.
- system — Initiate operational actions on the Junos system.
- table — Retrieve data from a Junos device using a PyEZ table/view.
For ansible collection juniper.device we will need to install junos-eznc version 2.6.0 or higher.
In addition to the modules listed above, a callback_plugin jsnapy is available for the module jsnapy.
The callback_plugin jsnapy helps to print on the screen additional information regarding jsnapy failed tests.
For each failed test, a log will be printed after the RECAP of the playbook as shown in this example:
PLAY RECAP *********************************************************************
qfx10002-01 : ok=3 changed=0 unreachable=0 failed=1
qfx10002-02 : ok=3 changed=0 unreachable=0 failed=1
qfx5100-01 : ok=1 changed=0 unreachable=0 failed=1
JSNAPy Results for: qfx10002-01 ************************************************
Value of 'peer-state' not 'is-equal' at '//bgp-information/bgp-peer' with {"peer-as": "65200", "peer-state": "Active", "peer-address": "100.0.0.21"}
Value of 'peer-state' not 'is-equal' at '//bgp-information/bgp-peer' with {"peer-as": "60021", "peer-state": "Idle", "peer-address": "192.168.0.1"}
Value of 'oper-status' not 'is-equal' at '//interface-information/physical-interface[normalize-space(admin-status)='up' and logical-interface/address-family/address-family-name ]' with {"oper-status": "down", "name": "et-0/0/18"}
JSNAPy Results for: qfx10002-02 ************************************************
Value of 'peer-state' not 'is-equal' at '//bgp-information/bgp-peer' with {"peer-as": "65200", "peer-state": "Active", "peer-address": "100.0.0.21"}
Callback plugins are not activated by default. They must be manually added to the Ansible
configuration file under the [defaults] section using the variable callback_whitelist. Specifically, these lines
should be added to the Ansible configuration file in order to allow the jsnapy callback plugin:
[defaults]
callback_whitelist = jsnapy
Official Juniper documentation (detailed information, including examples)
You must have the DEPENDENCIES installed on your system. Check requirements.txt for the dependencies.
In MacOS Mojave and newer (>=10.14), ssh keys created with the system ssh-keygen are created using the newer 'OPENSSH' key format, even when specifying -t rsa during creation. This directly affects the usage of ssh keys, particularly when using the ssh_private_key_file. To create/convert/check keys, follow these steps:
- Create a new RSA key:
ssh-keygen -m PEM -t rsa -b 4096 - Check existing keys:
head -n1 ~/.ssh/some_private_keyRSA keys will be-----BEGIN RSA PRIVATE KEY-----and OPENSSH keys will be-----BEGIN OPENSSH PRIVATE KEY----- - Convert an OPENSSH key to an RSA key:
ssh-keygen -p -m PEM -f ~/.ssh/some_key
You can use the ansible-galaxy install command to install the latest
version of the juniper.device collection.
sudo ansible-galaxy collection install juniper.deviceYou can also use the ansible-galaxy install command to install the latest development version of the junos collections directly from GitHub.
sudo ansible-galaxy collection install git+https://github.com/Juniper/ansible-junos-stdlib.git#/ansible_collections/juniper/deviceFor more information visit - https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#specifying-the-location-to-search-for-collections
For testing you can git clone this repo and run the env-setup script in the repo directory:
user@ansible-junos-stdlib> source env-setup
This will set your $ANSIBLE_LIBRARY variable to the repo location and the installed Ansible library path. For example:
$ echo $ANSIBLE_LIBRARY /home/jeremy/Ansible/ansible-junos-stdlib/library:/usr/share/ansible
To run this as a Docker container, which includes JSNAPy and PyEZ, simply pull it from the Docker hub and run it. The following will pull the latest image and run it in an interactive ash shell.
docker run -it --rm juniper/pyez-ansible
Although, you'll probably want to bind mount a host directory (perhaps the directory containing your playbooks and associated files). The following will bind mount the current working directory and start the ash shell.
docker run -it --rm -v $PWD:/project juniper/pyez-ansible
You can also use the container as an executable to run your playbooks. Let's assume we have a typical playbook structure as below:
example
|playbook.yml
|hosts
|-vars
|-templates
|-scripts
We can move to the example directory and run the playbook with the following command:
cd example/ docker run -it --rm -v $PWD:/playbooks juniper/pyez-ansible ansible-playbook -i hosts playbook.yml
You can pass any valid command string after the container name and it will be passed to Bash for execution.
You may have noticed that the base command is almost always the same. We can also use an alias to save some keystrokes.
alias pb-ansible="docker run -it --rm -v $PWD:/project juniper/pyez-ansible ansible-playbook" pb-ansible -i hosts playbook.yml
It's possible to install additional OS (Alpine) packages, Python packages (via pip), and Ansible collections at container instantiation. This can be done by passing in environment variables or binding mount files.
Environment Variable: $APK
Bind Mount: /extras/apk.txt
File Format: list of valid Alpine packages, one per line
Examples:
As an environment variable, where the file containing a list of packages is in the current directory.
docker run -it --rm -v $PWD:/project -e APK="apk.txt" juniper/pyez-ansible
As a bind mount.
docker run -it --rm -v $PWD/apk.txt:/extras/apk.txt juniper/pyez-ansible
Environment Variable: $REQ
Bind Mount: /extras/requirements.txt
File Format: pip requirements file
Examples:
docker run -it --rm -v $PWD:/project -e REQ="requirements.txt" juniper/pyez-ansible
As a bind mount.
docker run -it --rm -v $PWD/requirements.txt:/extras/requirements.txt juniper/pyez-ansible
Environment Variable: $ROLES
Bind Mount: /extras/requirements.yml
File Format: Ansible requirements file
NOTE: This works for collections as well as roles.
Examples:
docker run -it --rm -v $PWD:/project -e REQ="requirements.yml" juniper/pyez-ansible
As a bind mount.
docker run -it --rm -v $PWD/requirements.txt:/extras/requirements.yml juniper/pyez-ansible
This example outlines how to use Ansible to install or upgrade the software image on a device running Junos OS.
---
- name: Install Junos OS
hosts: dc1
collections:
- juniper.device
connection: local
gather_facts: no
vars:
wait_time: 3600
pkg_dir: /var/tmp/junos-install
OS_version: 14.1R1.10
OS_package: jinstall-14.1R1.10-domestic-signed.tgz
log_dir: /var/log/ansible
tasks:
- name: Checking NETCONF connectivity
wait_for: host={{ inventory_hostname }} port=830 timeout=5
- name: Install Junos OS package
software:
reboot: yes
version: "{{ OS_version }}"
package: "{{ pkg_dir }}/{{ OS_package }}"
logfile: "{{ log_dir }}/software.log"
register: sw
notify:
- wait_reboot
handlers:
- name: wait_reboot
wait_for: host={{ inventory_hostname }} port=830 timeout={{ wait_time }}
when: not sw.check_modeThis modules requires the following to be installed on the Ansible control machine:
- Python >= 3.8
- Ansible 2.9 or later
- Junos py-junos-eznc 2.6.0 or later
- jxmlease 1.0.1 or later
- xmltodict 0.13.0 or later
- jsnapy 1.3.7 or later
Apache 2.0
Support for this juniper.device collection is provided by the community and Juniper Networks. If you have an
issue with a module in the juniper.device collection, you may:
- Open a GitHub issue.
- Post a question on our Google Group
- Email [email protected]
- Open a JTAC Case
Support for the Junos modules included in Ansible core is provided by Ansible. If you have an issue with an Ansible core module you should open a Github issue against the Ansible project.
Juniper Networks is actively contributing to and maintaining this repo. Please contact [email protected] for any queries.
Contributors: Stephen Steiner, Dinesh Babu, Chidanand Pujar
Former Contributors:
Stacy W Smith, Jeremy Schulman, Rick Sherman, Damien Garros, David Gethings, Nitin Kumar, Rahul Kumar