Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

6.3.0 update download upgrade procedure #770

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/config_reference_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -2086,8 +2086,8 @@ This controls which repository or repositories a router will use to retrieve sof

| Element | Type | Description |
| --- | --- | --- |
| offline-mode | boolean | Default: false. Controls whether the router will only be able to retrieve software upgrade images via its conductor.|
| source-type | enumeration | Valid values: conductor-only, prefer-conductor, internet-only. Default: internet-only. To use the conductor as a proxy server to reach the SSR public internet repository, set this to `conductor-only` or `prefer-conductor`. To reach it via the public internet and not use the conductor as a proxy, set it to `internet-only`.|
| offline-mode | boolean | Default: `false`. Set this to `true` to limit the router to only retrieve software upgrade images from its conductor.|
| source-type | enumeration | Valid values: `conductor-only`, `prefer-conductor`, `internet-only`. Default: `internet-only`. To use the conductor as a proxy server to reach the SSR public internet repository, set this to `conductor-only` or `prefer-conductor`. To reach it via the public internet and not use the conductor as a proxy, set it to `internet-only`.|

## reverse-packet-session-resiliency

Expand Down Expand Up @@ -2708,7 +2708,7 @@ By default, an SSR retrieves software from a public software repository hosted b
| Element | Type | Description |
| --- | --- | --- |
| max-bandwidth | enumeration | Valid values: unlimited, 1-999999999999. This value is in bits/second. This represents the bandwidth limiter applied to software downloads. |
| repository | sub-element | Which repository/repositories the SSR will use.|
| [repository](#repository) | sub-element | Which repository/repositories the SSR will use.|

## ssh-keepalive

Expand Down
20 changes: 6 additions & 14 deletions docs/intro_downloading_iso.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,36 +9,28 @@ With your purchase of a SSR license, you are provided a set of credentials used

Juniper Session Smart Networking provides the following workflows for the installation process:

- **Universal ISO:** Beginning with version 6.3.0, the SSR uses a single downloadable ISO with a significantly simplified installation process. After the SSR installation completes, the GUI provides clear choices and processes for each of the device configuration options: Conductor, a Conductor-managed router, or a Mist-managed router.
- **SSR Image-based ISO:** **Beginning with version 6.3.0**, the SSR uses a single downloadable image-based ISO with a significantly simplified installation process. After the SSR installation completes, the GUI provides clear choices and processes for each of the device configuration options: Conductor, a Conductor-managed router, or a Mist-managed router.

Please see [SSR Universal ISO Installation Overview](intro_installation_univ-iso.md) for the download location and related installation instructions.
Please see [SSR Image-based ISO Installation Overview](intro_installation_univ-iso.md) for the installation instructions and software image download location.

- **Image-based ISO:** 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 details about the Image-based install process, see [Image-based Installation.](intro_installation_image.md)
For users installing *earlier, package-based versions of the SSR software*, the following installation methods are available:

- **Package-based ISO:** For users who do not use Mist Cloud, this ISO offers multiple local installation methods.
- **One Touch Provisioning (OTP)** is the default and preferred method of installation. OTP sets up DHCP on all interfaces and boots a Web Server GUI. After installing the Conductor and configuring routers through the Conductor, the OTP bootstrap process will install and configure the router. See the following procedures for OTP installation steps:
- [Router Installation Using OTP](intro_otp_iso_install.mdx)
- [Quickstart from the OTP ISO](intro_install_quickstart_otpiso.md)
- **Interactive:** Beginning with SSR version 6.3.0, the use of the interactive installer is not supported, nor necessary. Software installation and upgrade upgrade activities are supported from the GUI or PCLI. With software versions earlier than 6.3.0, upgrading the SSR software on a peer conductor or router that is managed by a conductor using the interactive installer may result in the system becoming unresponsive. For this reason it is highly recommended that installations and upgrades be performed through the conductor UI.

:::note
Beginning with release 5.4.7-7 and any 5.x ISO [**released after August 4, 2022**](about_releases.mdx#all-releases---limited-general-availability-and-out-of-support), the ISO name format has changed from using `OTP` to `ISO`:

- 128T-5.4.7-7.el7.ISO.v1.x86_64.iso
:::
- **Interactive:** Beginning with SSR version 6.3.0, the use of the interactive installer is not supported, nor necessary. Software installation and upgrade upgrade activities are supported from the GUI or PCLI. With software versions earlier than 6.3.0, upgrading the SSR software on a conductor or router that is managed by a conductor using the interactive installer may result in the system becoming unresponsive. For this reason it is highly recommended that installations and upgrades be performed through the conductor UI.

## Downloading an ISO

The SSR Software packages are available from our public servers using the username and token provided to you and can be accessed at the following location:

The image-based ISOs for Mist-managed deployments are available to download at the following location:
The image-based ISOs are available to download at the following location:

<!-- markdown-link-check-disable-next-line -->
- https://software.128technology.com/artifactory/list/generic-128t-install-images-release-local

The package-based ISOs for Conductor-managed deployments are available to download at the following location:
The package-based ISOs are available to download at the following location:

<!-- markdown-link-check-disable-next-line -->
- https://software.128technology.com/artifactory/list/generic-128t-isos-release-local
Expand Down
10 changes: 5 additions & 5 deletions docs/intro_installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,12 +18,10 @@ The examples listed in this guide generally prefer running commands as a non-roo

## Installation Process

Beginning with SSR 6.3.0, the Universal ISO Installation simplifies and streamlines the SSR installation and initialization process, and supports Conductor-managed image-based installations as well as Mist-managed deployments.
Beginning with SSR 6.3.0, a universal image-based ISO is provided to simplify and streamline the SSR installation and initialization process. This version supports Conductor-managed image-based installations as well as Mist-managed deployments.

Installation to your device utilizes the SSR ISO, downloaded as a bootable image to a USB drive or from disk. The install process is as follows:

Installation is done from the SSR ISOs, typically from a bootable image on a flash drive or disk. The install process is as follows:
- Pre-Installation Process:
- [Download the ISOs](intro_downloading_iso.md)
- [Create Bootable Media](intro_creating_bootable_usb.md)
- [SSR Universal ISO Installation (SSR 6.3.0+)](intro_installation_univ-iso.md)
- [SSR Installation](install_univ_iso.md)
- [Device Initialization](initialize_u-iso_device.md)
Expand All @@ -33,6 +31,8 @@ Installation is done from the SSR ISOs, typically from a bootable image on a fla
- [Installation in Microsoft Azure](intro_installation_azure.md)
- [Installing in VMWare](install_vmware_config.mdx)

- [Legacy Installations](intro_installation_legacy.md) for installation of versions prior to 6.3.0

A Mist-redirect ZTP process for Conductor-managed deployments is supported on Juniper branded hardware devices - the SSR1x0/1x00. See [Onboard an SSR Device to a Conductor](onboard_ssr_to_conductor.md) for details about this process.

## Upgrades
Expand Down
14 changes: 7 additions & 7 deletions docs/intro_installation_univ-iso.md
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
---
title: SSR Universal ISO Installation Overview
sidebar_label: SSR Universal ISO Installation Overview
title: SSR Image-based ISO Installation Overview
sidebar_label: SSR Image-based ISO Installation Overview
---

Beginning with version 6.3.0, the SSR uses a single downloadable ISO with a significantly simplified installation process. After the SSR installation completes, the GUI provides clear choices and processes for each of the device configuration options: Conductor, a Conductor-managed router, or a Mist-managed router.
Beginning with version 6.3.0, the SSR uses a single image-based ISO with a significantly simplified installation process. After the SSR installation completes, the GUI provides clear choices and processes for each of the device configuration options: Conductor, a Conductor-managed router, or a Mist-managed router.

#### Version History

| Release | Modification |
| ------- | ------------ |
| 6.0.0 | Image-based ISO installation process implemented for Mist-managed networks. |
| 6.3.0 | Universal ISO released, migrating to a single ISO installation format for Conductor, Conductor-managed, and Mist-managed deployments. |
| 6.3.0 | Image-based ISO updated, migrating to a single ISO installation format for Conductor, Conductor-managed, and Mist-managed deployments. |

The installation workflow consists of the following steps:

Expand All @@ -21,20 +21,20 @@ The installation workflow consists of the following steps:

## Download

The ISO is available for download at the following location:
The image-based ISOs are available for download at the following location:

<!-- markdown-link-check-disable-next-line -->
https://software.128technology.com/artifactory/list/generic-128t-install-images-release-local/

Files available for download are:

- `*.iso` - This file is used for installing/staging bare metal platforms. **Use this file to perform an image-based install.**
- `*.iso` - This file is used for installing/staging bare metal platforms. **Use this file to perform an initial image-based install.**
- `*.tar` - This file is used by Mist or the SSR conductor for image-based upgrades, and is accessed directly by the system during the upgrade. User download is not necessary or advised.

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.

### Create a Bootable USB

Use the instructions for [Creating a Bootable USB](intro_creating_bootable_usb.md) to create a bootable USB drive containing the universal ISO image.
Use the instructions for [Creating a Bootable USB](intro_creating_bootable_usb.md) to create a bootable USB drive containing the latest image-based ISO.

Once you have the USB, let's go [Install the SSR software!](install_univ_iso.md)
23 changes: 11 additions & 12 deletions docs/intro_upgrading.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,13 @@ Please refer to the [Upgrade Considerations](intro_upgrade_considerations.md) be

Your SSR conductor or router must have internet access to download the latest software packages; however, we recognize that there are deployments where the SSR does not have internet access. In those cases you can use the SSR conductor as a repository (or proxy) to retrieve or store software images. For information about upgrading offline or air-gap network devices, refer to [Upgrades with Restricted Internet Access](upgrade_restricted_access.md).

For Upgrade procedures, refer to the appropriate section:

- [Upgrading the Conductor](upgrade_ibu_conductor.md)
- [Upgrading the Router](upgrade_router.md)
- [Upgrades with Restricted Internet Access](upgrade_restricted_access.md)
- [Legacy Upgrades](upgrade_legacy.md) Software versions prior to SSR 6.3.0

As with any upgrade activity, it is always prudent to create a backup of your current software configuration before initiating any upgrade activity.

Conductor and router upgrades may be performed from the GUI of the Conductor, the PCLI of the conductor, or in the case of an unmanaged router, from the router itself.
Expand All @@ -24,15 +31,7 @@ Prerequisites for upgrades include configuring a user with super user (sudo) pri
The conductor `major.minor` version must be greater than or equal to the router version. The router version can not exceed the conductors `major.minor` version, but it can have a greater patch version. All [versions currently under support](about_support_policy.md) can be run on a router and managed by the conductor, provided that the conductor version is greater. Versions of software not under support *may* work, but are not guaranteed to do so.

Examples:
- Conductor running version 6.0.5, managing Routers running version 6.0.1: Supported.
- Conductor running version 5.4.8, managing Routers running version 5.4.10: Supported.
- Conductor running version 6.0.5, managing Routers running version 5.5.7: Supported.
- Conductor running version 5.6.8, managing Routers running version 6.1.3; Not supported.

For Upgrade procedures, refer to the appropriate section:

- [Upgrading the Conductor](upgrade_ibu_conductor.md)
- [Upgrading the Router](upgrade_router.md)
- [Upgrades with Restricted Internet Access](upgrade_restricted_access.md)
- [Legacy Upgrades](upgrade_legacy.md) Software versions prior to SSR 6.3.0

- Conductor running version 6.2.6, managing Routers running version 6.2.5: Supported.
- Conductor running version 6.2.5, managing Routers running version 6.2.6: Supported.
- Conductor running version 6.3.0, managing Routers running version 6.1.10: Supported.
- Conductor running version 5.6.10, managing Routers running version 6.1.3; Not supported.
Loading
Loading