Beginning with version 6.0, an image-based ISO installation process has been implemented for users who manage their network using the Mist Cloud. This installation and upgrade process is only available for SSR version 6.0 and higher, and is currently only available for Mist-managed deployments.
For conductor-managed deployments, the package-based installation is used.
The image-based installation creates two volumes on the disk, installs the full 6.0 image into one of the volumes, and boots into that image. When an upgrades is intiated, the new ISO image is copied into the other volume. The upgrade process then copies configurations and persistent information from the old image to the new image, then reboots into the new version.
The image-based ISO's are available to download at the following location:
You will be prompted for your username and token to access the web page listing the software versions. Download is done directly from the page. For the detailed download process, see Downloading an ISO.
Create a Bootable USB
Use the instructions Creating a Bootable ISO to create a USB to be used to install the image.
Insert the flash drive into the appliance, and boot into the flash drive.
Select the installation methods; Serial Console or VGA. If you do not make a selection, the Serial mode installation is selected by default.
In the Installer window, select 2 for the ZTP Install Mode. This is the default mode for image-based installation.
When using the image-based 6.0 installation, be aware that if Interactive Install is selected,
intialize128t does not launch automatically on first boot. This must be run manually; log in to the console as root using the default credentials, and type
initialize128t to perform interactive initialization. This will be resolved in a future release.
On a system with multiple disks, the Install Devices selection allows you to steer the boot and root filesystems to individual devices if necessary.
If you require FIPS enforcement, select 5 for
Enable FIPS 140-2 mode. If you do not require FIPS enforcement, skip to step 7.
The resulting system boots into FIPS 140-2 enforcing mode.
Verify FIPS mode is active by reading the kernel crypto state using
sysctl. The result is an error when attempting to use a non-FIPS compliant crypto such as md5.
Press the enter key to start the installation.
Once complete, you are prompted with an option to press Esc to reboot immediately, or Enter to shutdown and continue later.
Upon restart, the system initializes and is internet ready. You can now use one of the following ways to associate the device with a Mist organization.
- GUI through LAN port.
- Have a USB flash drive inserted on first boot with whitebox configuration.
Do not insert the USB before reaching step 5, or it may be erased during install.
Associate the Router with Mist
This section covers the basic steps to associate your router with a Mist Organization using the SSR and Mist GUI. The following animation presents the steps for associating the onboarded router with a Mist organization.
The steps performed in the animation are listed here.
Upon reboot, you are presented with the SSR login screen where you can choose to Manage the router through the Mist cloud. Select this option.
Choose how to associate the router with the Mist Cloud; selecting an Organization, or use a registration code. In this example, we will choose the organization.
Log in to Mist.
Select the organization from the drop down list.
If you assigned your router a name, enter it here and select ADOPT.
If there are no errors, the router is associated with the organization and visible in the Mist UI.
Click on the link to the Mist Cloud to see the router in the Mist inventory.
Adopt the Router from the SSR PCLI
If you prefer to work from the PCLI, you can use the
adopt command to associate the router with Mist.
When the device is installed with SSR software, the software scans the device to generate a default port map. When the device is recognized as a certified device a known port layout is prescribed as the device default. When the device is unrecognized, a default port layout is generated based upon PCI address order. This order often does NOT match the external bezel port order. Some plugging in and testing may be required.
For information about port layout on Juniper certified or compatible devices, see Device Default Port Layout.