Legacy Upgrades
This guide focuses on legacy software upgrades - those prior to version 6.3.0.
Please refer to the Upgrade Considerations before proceeding.
The 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.
As with any upgrade activity, it is always prudent to create a backup of your current software configuration before initiating any upgrade activity.
With software versions prior to 6.3.0, there are three standard ways of upgrading routers:
- Using the conductor's Web Interface to initiate the upgrade
- Using the conductor's PCLI to initiate the upgrade
- Using the Interactive Installer from the Linux shell
The router upgrade process using the PCLI and the GUI is done in two stages: First, the software is downloaded, then it is installed. Use the install128t
application steps through both of these processes.
Prerequisites for upgrades now include configuring a user with super user (sudo) privileges. SSH Root login is not permitted. If the existing version allows SSH Root login, it will be disabled during the upgrade. When a system is installed using the OTP ISO, a t128 user is configured with sudo
privileges.
Version Dependencies
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 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.
Upgrading Software Versions Prior to 6.3.0
Use the following procedure to upgrade your software versions earlier than 6.3.0.
Using the Web Interface
- Navigate to the Router page in the Conductor's GUI. Routers that have available upgrades are indicated with the green Upgrade SSR icon (the arrow within a circle) in the router list.
- Click on the Upgrade SSR icon next to your router. A list of upgrade and download options appears. This list is filterable if the list grows large.
- Click on the target release in the Available Downloads section of the list.
- Confirm the operation to begin downloading the software. Clicking on the router in the router list shows download progress.
- Once complete, click the Upgrade SSR icon again, and select the target software release from the Available Upgrades list. Confirm this operation to begin the upgrade process.
The Automated Provisioner upgrades both nodes in a high availability router in series to minimize/avoid downtime. Despite this, it is still recommended to perform upgrade activity during periods of low traffic or maintenance windows.
Using the PCLI
Before upgrading the SSR Software from the PCLI, use the following procedure to stop the the software.
-
Launch a Linux shell window.
-
Execute the command:
sudo systemctl stop 128T
-
Verify that the software has stopped by executing the command:
sudo systemctl status 128T
Result: The software is listed as inactive (dead).
-
Stop the salt-minion.
sudo systemctl stop salt-minion
-
Close the Linux shell.
Use the steps below to download and upgrade SSR software if you are running earlier software versions.
Log into the PCLI
As an administrator-level user, log into the conductor's PCLI.
-
Use the command
show assets
to list the devices managed by this conductor, and the software revision each asset is currently running. -
For a given asset, use the command
show asset [asset ID]
orshow asset software router [router name]
to view the available software upgrades for that asset. The list will be in the section labeled "Available for Download" at the end of the output.noteIf there are software releases absent from the list that you are confident should appear, use the command
send command yum-cache-refresh router [router name]
to refresh the software list. -
Type
send command download router [your router name] [software version]
. You can monitor the progress by using theshow asset
and/orshow asset [asset ID]
command, which will indicate Automated Provisioner status (e.g., downloading). -
Once the download is complete, use the command
send command upgrade router [your router name]
to initiate the upgrade process.
The conductor's automated provisioner will upgrade both nodes in a high availability router in series to minimize/avoid downtime. Despite this, it is still recommended to perform upgrade activity during periods of low traffic or maintenance windows.