Migration, Upgrade, and Downgrade Instructions
This section contains the procedure to upgrade Junos OS, and the upgrade and downgrade policies for Junos OS for the MX Series. Upgrading or downgrading Junos OS might take several minutes, depending on the size and configuration of the network.
Starting in Junos OS release 21.2R1, all Junos OS products which were previously running on FreeBSD 11.x based Junos OS are migrated to FreeBSD 12.x based Junos OS.
The following table shows detailed information about which Junos OS can be used on which products:
Platform |
FreeBSD 6.x-based Junos OS |
FreeBSD 12.x-based Junos OS |
MX240, MX480, MX960, MX2010, MX2020 |
NO |
YES |
Basic Procedure for Upgrading to Release 21.4R2
Before upgrading, back up the file system and the currently active Junos OS configuration so that you can recover to a known, stable environment in case the upgrade is unsuccessful. Issue the following command:
user@host> request system snapshot
The installation process rebuilds the file system and completely reinstalls Junos OS. Configuration information from the previous software installation is retained, but the contents of log files might be erased. Stored files on the routing platform, such as configuration templates and shell scripts (the only exceptions are the juniper.conf and ssh files might be removed. To preserve the stored files, copy them to another system before upgrading or downgrading the routing platform. For more information, see the Installation and Upgrade Guide.
For more information about the installation process, see Installation and Upgrade Guide and Upgrading Junos OS with Upgraded FreeBSD.
Procedure to Upgrade to FreeBSD 12.x-Based Junos OS
Products impacted: MX240, MX480, MX960, MX2010, and MX2020.
To download and install FreeBSD 12.x-based Junos OS:
-
Using a Web browser, navigate to the All Junos Platforms software download URL on the Juniper Networks webpage:
-
Select the name of the Junos OS platform for the software that you want to download.
-
Select the release number (the number of the software version that you want to download) from the Release drop-down list to the right of the Download Software page.
-
Select the Software tab.
-
In the Install Package section of the Software tab, select the software package for the release.
-
Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by a Juniper Networks representative.
-
Review and accept the End User License Agreement.
-
Download the software to a local host.
-
Copy the software to the routing platform or to your internal software distribution site.
-
Install the new jinstall package on the routing platform.
Note:We recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process.
All customers except the customers in the Eurasian Customs Union (currently composed of Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package:
-
For 32-bit Routing Engine version:
user@host> request system software add no-validate reboot source/junos-install-mx-x86-32-21.4R2.9-signed.tgz
-
For 64-bit Routing Engine version:
user@host> request system software add no-validate reboot source/junos-install-mx-x86-64-21.4R2.9-signed.tgz
Customers in the Eurasian Customs Union (currently composed of Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package (Limited encryption Junos package):
-
For 32-bit Routing Engine version:
user@host> request system software add no-validate reboot source/junos-install-mx-x86-32-21.4R2.x-limited.tgz
-
For 64-bit Routing Engine version:
user@host> request system software add no-validate reboot source/junos-install-mx-x86-64-21.4R2.9-limited.tgz
Replace source with one of the following values:
-
/pathname—For a software package that is installed from a local directory on the router.
-
For software packages that are downloaded and installed from a remote location:
-
ftp://hostname/pathname
-
http://hostname/pathname
-
scp://hostname/pathname
-
Do not use the
validate
option while upgrading from Junos OS (FreeBSD 6.x, 10.x, and 11.x) to Junos OS (FreeBSD 12.x). This is because programs in the junos-upgrade-x package are built based on FreeBSD 12.x, and Junos OS (FreeBSD 6.x, 10.x, and 11.x) would not be able to run these programs. You must run theno-validate
option. Theno-validate
statement disables the validation procedure and allows you to use an import policy instead.Use the
reboot
command to reboot the router after the upgrade is validated and installed. When the reboot is complete, the router displays the login prompt. The loading process might take 5 to 10 minutes.Rebooting occurs only if the upgrade is successful.
-
-
You need to install the Junos OS software package and host software package on the routers with the RE-MX-X6 and RE-MX-X8 Routing Engines. For upgrading the host OS on these routers with VM Host support, use the junos-vmhost-install-x.tgz image and specify the name of the regular package in the
request vmhost software add
command. For more information, see the VM Host Installation topic in the Installation and Upgrade Guide. -
Starting in Junos OS Release 21.4R2, in order to install a VM host image based on Wind River Linux 9, you must upgrade the i40e NVM firmware on the following MX Series routers:
-
MX240, MX480, MX960, MX2010, MX2020, MX2008, MX10016, and MX10008
-
-
Starting in Junos OS Release 21.4R1 and later releases,
ssh root-login
is required for copying the line card image (chspmb.elf) from Junos OS VM to Linux host during installation for MX204 and MX2008 VM host based platforms. Do not disable it through configuration during installation. Usedeny-password
instead ofdeny
as default root-login option underssh
configuration to allow internal trusted communication.For information on VMHost based platforms, see VM Host Overview (Junos OS).
After you install a Junos OS Release
21.4R2
jinstall package, you cannot return to the previously installed Junos OS (FreeBSD 6.x)
software by issuing the request system software rollback
command.
Instead, you must issue the request system software add no-validate
command and specify the jinstall package that corresponds to the previously installed
software.
Most of the existing request system
commands are not supported on
routers with the RE-MX-X6 and RE-MX-X8 Routing Engines. See the VM Host Software
Administrative Commands in the Installation and Upgrade Guide.
Upgrade and Downgrade Support Policy for Junos OS Releases and Extended End-Of- Life Releases
Support for upgrades and downgrades that span more than three Junos OS releases at a time is not provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the next EEOL release even though EEOL releases generally occur in increments beyond three releases.
You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 19.3, 19.4, and 20.1 are EEOL releases. You can upgrade from Junos OS Release 19.3 to Release 19.4 or from Junos OS Release 19.3 to Release 20.1.
You cannot upgrade directly from a non-EEOL release to a release that is more than three releases ahead or behind. To upgrade or downgrade from a non-EEOL release to a release more than three releases before or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release to your target release.
For more information about EEOL releases and to review a list of EEOL releases, see https://www.juniper.net/support/eol/junos.html.
Upgrading a Router with Redundant Routing Engines
If the router has two Routing Engines, perform the following Junos OS installation on each Routing Engine separately to avoid disrupting network operation:
-
Disable graceful Routing Engine switchover (GRES) on the master Routing Engine, and save the configuration change to both Routing Engines.
-
Install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine.
-
After making sure that the new software version is running correctly on the backup Routing Engine, switch over to the backup Routing Engine to activate the new software.
-
Install the new software on the original master Routing Engine that is now active as the backup Routing Engine.
For the detailed procedure, see the Installation and Upgrade Guide.
Downgrading from Release 21.4R2
To downgrade from Release 21.4R2 to another supported release, follow the procedure for upgrading, but replace the 21.4R2 jinstall package with one that corresponds to the appropriate release.
You cannot downgrade more than three releases.
For more information, see the Installation and Upgrade Guide.