Release date: June 2023
Shell version: 4.0.0
Python version: 3.9
Document version: 1.1
- Overview
- Downloading the Shell
- Importing and Configuring the Shell
- Updating Python Dependencies for Shells
- Typical Workflows
- References
- Release Notes
A shell integrates a device model, application or other technology with CloudShell. A shell consists of a data model that defines how the device and its properties are modeled in CloudShell, along with automation that enables interaction with the device via CloudShell.
CloudShell's networking shells provide L2 or L3 connectivity between resources and/or Apps.
The Juniper JunOS Router 2G shell provides you with connectivity and management capabilities such as device structure discovery and power management for the Juniper JunOS Router.
For more information on the Juniper JunOS Router, see the official Juniper product documentation.
Juniper JunOS Router 2G Shell is based on the Networking Shell Standard version 5.0.4.
For detailed information about the shell’s structure and attributes, see the Networking Shell Standard in GitHub.
▪ JunOS
Release: Juniper JunOS Router 2G Shell
▪ CloudShell version: 2022.1 and above
▪ Certified models: Juniper SRX220
Note: If your CloudShell version does not support this shell, you should consider upgrading to a later version of CloudShell or contact customer support.
The shell's data model includes all shell metadata, families, and attributes.
The Juniper JunOS Router 2G shell families and models are listed in the following table:
| Family | Model | Description |
|---|---|---|
| CS_Router | Juniper JunOS Router 2G | Generic Juniper JunOS Router 2 Generation |
| CS_Chassis | Generic Chassis | Default Router chassis |
| CS_Module | Generic Module | Modules located on the chassis |
| CS_SubModule | Generic Sub Module | Sub modules |
| CS_Port | Generic Port | Interface |
| CS_PortChannel | Generic Port Channel | Group of interfaces |
| CS_PowerPort | Generic Power Port | Power Supply module |
The attribute names and types are listed in the following section of the Networking Shell Standard:
This section describes the automation (drivers) associated with the data model. The shell’s driver is provided as part of the shell package. There are two types of automation processes, Autoload and Resource. Autoload is executed when creating the resource in the Inventory dashboard, while resource commands are run in the sandbox.
The command names and types are listed in the following table:
| Command | Description |
|---|---|
| Run Custom Command | Executes any custom command entered in the input on the device. Set the command input as follows: ▪ Custom Command (String): The command to run. Note that commands requiring a response are not supported. |
| Health Check | Checks if the device is powered-up and connectable. |
| Save | Creates a configuration file and saves it to the provided destination. Set the command inputs as follows: ▪ Folder Path (String): Path where the configuration file will be saved. If this field is left empty, the value will be taken from the Backup Location attribute on the root resource. The path should include the protocol type, for example: tftp://asdf. ▪ Configuration Type (String): Specify whether the file should update the Startup or Running config. If left empty, the default configuration type Running will be used. - Startup: Configuration that is loaded when the device boots or powers up. - Running: Current configuration in the device. ▪ VRF Management Name (String): (Optional) Virtual routing and forwarding management name. If left empty, the value in the VRF Management Name attribute on the root model will be used. |
| Restore | Restores a configuration file from the saved file. Set the command inputs as follows: ▪ Path (String): The full path from which the configuration file will be restored. The path should include the protocol type, for example: tftp://10.10.10/asdf. ▪ Configuration Type (Enum): Specify whether the file should update the Startup or Running config. If left empty, the default configuration type Running will be used. - Startup: Configuration that is loaded when the device boots or powers up. - Running: Current configuration in the device. It may have been modified since the last boot. ▪ Restore Method (String): Determines whether the restore should append or override the current configuration. If left empty, the restore method will use the default Override value. ▪ VRF Management Name (String): (Optional) Virtual routing and forwarding management name. If left empty, the value in the VRF Management Name attribute on the root model will be used. |
| Load Firmware | Uploads the firmware on the resource. Set the command inputs as follows: ▪ Path (String): The full path to the location of the firmware to load on the device. ▪ VRF Management Name (String): (Optional) Virtual routing and forwarding management name. If left empty, the value in the VRF Management Name attribute on the root model will be used. |
The Juniper JunOS Router 2G shell is available from the Quali Community Integrations page.
Download the files into a temporary location on your local machine.
The shell comprises:
| File name | Description |
|---|---|
| Juniper.JunOS.Router.Shell.2G.zip | Juniper JunOS Router 2G shell package |
| cloudshell-Juniper-JunOS-Router-Shell-2G-dependencies-linux-package-4.0.0.zip | Shell Python dependencies for linux (for offline deployments only) |
| cloudshell-Juniper-JunOS-Router-Shell-2G-dependencies-win-package-4.0.0.zip | Shell Python dependencies for windows (for offline deployments only) |
This section describes how to import the Juniper JunOS Router 2G shell and configure and modify the shell’s devices.
To import the shell into CloudShell:
-
Make sure you have the shell’s zip package. If not, download the shell from the Quali Community's Integrations page.
-
In CloudShell Portal, as Global administrator, open the Manage – Shells page.
-
Click Import.
-
In the dialog box, navigate to the shell's zip package, select it and click Open.
The shell is displayed in the Shells page and can be used by domain administrators in all CloudShell domains to create new inventory resources, as explained in Adding Inventory Resources.
Note: Offline installation instructions are relevant only if CloudShell Execution Server has no access to PyPi. You can skip this section if your execution server has access to PyPi. For additional information, see the online help topic on offline dependencies.
In offline mode, import the shell into CloudShell and place any dependencies in the appropriate dependencies folder. The dependencies folder may differ, depending on the CloudShell version you are using:
-
For CloudShell version 8.3 and above, see Adding Shell and script packages to the local PyPi Server repository.
-
For CloudShell version 8.2, perform the appropriate procedure: Adding Shell and script packages to the local PyPi Server repository or Setting the python pythonOfflineRepositoryPath configuration key.
-
For CloudShell versions prior to 8.2, see Setting the python pythonOfflineRepositoryPath configuration key.
If your Quali Server and/or execution servers work offline, you will need to copy all required Python packages, including the out-of-the-box ones, to the PyPi Server's repository on the Quali Server computer (by default C:\Program Files (x86)\QualiSystems\CloudShell\Server\Config\Pypi Server Repository).
For more information, see Configuring CloudShell to Execute Python Commands in Offline Mode.
To add Python packages to the local PyPi Server repository:
-
If you haven't created and configured the local PyPi Server repository to work with the execution server, perform the steps in Add Python packages to the local PyPi Server repository (offlinemode).
-
For each shell or script you add into CloudShell, do one of the following (from an online computer):
-
Connect to the Internet and download each dependency specified in the requirements.txt file with the following command:
pip download -r requirements.txt. The shell or script's requirements are downloaded as zip files. -
In the Quali Community's Integrations page, locate the shell and click the shell's Download link. In the page that is displayed, from the Downloads area, extract the dependencies package zip file.
-
-
Place these zip files in the local PyPi Server repository.
Before PyPi Server was introduced as CloudShell’s python package management mechanism, the PythonOfflineRepositoryPath key was used to set the default offline package repository on the Quali Server machine, and could be used on specific Execution Server machines to set a different folder.
To set the offline python repository:
-
Download the cloudshell-networking-juniper-junos2-gen-dependencies-package-2.0.X.zip file, see Downloading the Shell.
-
Unzip it to a local repository. Make sure the execution server has access to this folder.
-
On the Quali Server machine, in the ~\CloudShell\Server\customer.config file, add the following key to specify the path to the default python package folder (for all Execution Servers):
<add key="PythonOfflineRepositoryPath" value="repository full path"/> -
If you want to override the default folder for a specific Execution Server, on the Execution Server machine, in the ~TestShell\Execution Server\customer.config file, add the following key:
<add key="PythonOfflineRepositoryPath" value="repository full path"/> -
Restart the Execution Server.
This section explains how to create a new resource from the shell.
In CloudShell, the component that models the device is called a resource. It is based on the shell that models the device and allows the CloudShell user and API to remotely control the device from CloudShell.
You can also modify existing resources, see Managing Resources in the Inventory.
To create a resource for the device:
-
In the CloudShell Portal, in the Inventory dashboard, click Add New.
-
From the list, select Juniper JunOS Router 2G.
-
Enter the Name and IP address of the Juniper JunOS Router.
-
Click Create.
-
In the Resource dialog box, enter the device's settings. For details, see Juniper JunOS Router Attributes.
-
Click Continue.
CloudShell validates the device’s settings and updates the new resource with the device’s structure (if the device has a structure).
This section explains how to update your Python dependencies folder. This is required when you upgrade a shell that uses new/updated dependencies. It applies to both online and offline dependencies.
To update offline Python dependencies:
-
Download the latest Python dependencies package zip file locally.
-
Extract the zip file to the suitable offline package folder(s).
-
Restart any execution server that has a live instance of the relevant driver or script. This requires running the Execution Server's configuration wizard, as explained in the Configure the Execution Server topic of the CloudShell Suite Installation guide.
In online mode, the execution server automatically downloads and extracts the appropriate dependencies file to the online Python dependencies repository every time a new instance of the driver or script is created.
To update online Python dependencies:
- If there is a live instance of the shell's driver or script, restart the execution server, as explained above. If an instance does not exist, the execution server will download the Python dependencies the next time a command of the driver or script runs.
-
In CloudShell Portal, add the Juniper JunOS Router resource to your blueprint and reserve the blueprint.
-
Run the Save resource command.
-
In the command inputs field, enter the following information:
- Folder Path: For example, tftp://ipaddress/shared folder.
- Configuration Type: Startup or Running.
- VRF Management Name: Provide the VRF Management name, if relevant.
-
Click Run.
The Startup or Running configuration is saved to a file named -<startup/running-config>-, which will be stored in the folder path you entered above.
-
In CloudShell Portal, add the Juniper JunOS Router resource to your blueprint and reserve the blueprint.
-
Run the Restore resource command.
-
In the command inputs field, enter the following information:
- Path: (Mandatory) Enter the full path of the configuration file.
- Restore Method: (Optional) Possible values are Override or Append. If left empty, the Override method is used.
- Configuration Type: (Mandatory) Possible values are Startup or Running.
- VRF Management Name: (Optional) Provide the VRF Management name, if relevant.
-
Click Run.
-
In CloudShell Portal, add the Juniper JunOS Router resource to your blueprint and reserve the blueprint.
-
Run the Load Firmware resource command.
-
In the command inputs field, enter the following information:
- Remote Host (Mandatory). Enter the full path to the firmware file on the remote host, for example: tftp://10.1.1.1/ios12.SE1-smp-k8.bin.
- File Path (Mandatory). Destination file name on the device itself, for example: bootflash:/ios12.SE1-smp-k8.bin.
-
Click Run.
To download and share integrations, see Quali Community's Integrations.
For instructional training and documentation, see Quali University.
To suggest an idea for the product, see Quali's Idea box.
To connect with Quali users and experts from around the world, ask questions and discuss issues, see Quali's Community forums.
- Known issue #15248: Some switches/routers don’t reflect port-channel members correctly in the IEEE 802.3ad Link Aggregation MIB.
- Known Issue #38226: Juniper Shell may discover empty or incomplete structure due to an issue in JunOS firmware releases between 15.1R5 and 16.1R6. To fix please upgrade to JunOS 16.1R7-S5.2.