Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Rapid Deployment Overview

The Junos Space Rapid Deployment solution enables you to model Juniper Networks devices quickly and effectively from Junos Space Network Management Platform. Devices are modeled by using the Model Devices workflow in the Devices workspace. When you add physical devices to your network, you can activate the modeled devices and associate the physical devices to the modeled devices. If you are deploying a ACX Series or SRX Series Firewall, you can use the autoinstallation feature during deployment. For more information, see Zero Touch Deployment Using Autoinstallation and Junos Space Network Management Platform on ACX Series and SRX Series Devices.

Devices are either activated from Junos Space Platform (by using the Activate workflow) or by using the configlets (also known as one-touch deployment) generated from the Create Modeled Instance workflow. By default, configlets contain the minimum initial configuration (connection parameters) for modeled devices to connect to Junos Space Platform. The minimum initial configuration includes the FQDN of Junos Space, SSH secure key to access the device from Junos Space Platform, ID of the device, keep-alive timer, WAN IP configuration: static or DHCP, and default gateway and DNS details.

If you associate the modeled instance with a device template and select to update a device template manually, the configlet contains the configuration in the device template in addition to the minimum initial configuration.

Following are the six steps that outline the Rapid Deployment solution in Junos Space Platform:

  1. Create a modeled instance that defines the number of devices that will be added to the Junos Space Platform database. You can assign a hostname, IP address, subnet mask, platform, and serial number on a per-device basis. Refer to Creating a Modeled Instance for more information.

  2. Generate a configlet and Initiate a connection between Junos Space Platform in one of the following ways:

    • Copy the contents of the configlet generated by the modeled instance to the CLI console of the device. When this initial configuration is committed on the device, the device connects to Junos Space Platform.

    • Connect the USB device containing the configlet to the device and reboot the device. The device then connects to Junos Space Platform. Refer to Activating Devices by Using Configlets for more information.

    • Initiate the workflow to activate the modeled instance that contains the device. Refer to Activating a Modeled or Cloned Device in Junos Space Network Management Platform for more information.

  3. When the device boots up and connects to the WAN link, an IP address is assigned to the device depending on the connection profile you assigned to the modeled instance containing the device.

  4. The device connects to Junos Space Platform through an SSH session.

  5. Junos Space Platform authenticates the device and optionally validates the serial number and hostname of the device. The device is managed in Junos Space Platform only if the validation succeeds. If the validation fails, the device is not managed in Junos Space Platform.

  6. Junos Space Platform either upgrades or downgrades the Junos OS version of the device if you select the Image Upgrade/Downgrade check box in the Model Devices workflow.

    Junos Space Platform also pushes additional configuration settings through device templates if you select the Template Association check box and choose to update the configuration automatically. If you select a manual update of the device configuration, you must load the configlets to the device through a USB device or an FTP server.