Junos OS Evolved Installation Packages
The installation package is used to upgrade or downgrade from one Junos OS Evolved release to another. When added, the installation package completely re-installs the software, rebuilds the file system, and can erase system logs and other auxiliary information from the previous installation. The system does, however, retain the configuration files from the previous installation.
The names of the Junos OS Evolved installation packages have the following general pattern:
-
prefix-release-edition-EVO.iso
The names of the Junos OS Evolved jfirmware
packages have the following
general pattern:
-
jfirmware-prefix-release-edition-EVO.tgz
Juniper Networks delivers the Junos OS Evolved software in signed packages that contain digital signatures. The system only installs a package if the checksum within it matches the hash recorded in its corresponding file.
Junos OS Evolved Installation Package Prefixes
The first part of the installation package filename is a combination of a standard prefix and a product designation.
Prefix | Description |
---|---|
junos-evo-install* or junos-evo-install-media* |
Introduced as of Junos OS Evolved Release 18.3R1. For Junos OS Evolved, there is a single image for all fixed form (versus chassis) platforms, and a platform image name can also be distinguished as merchant silicon (ms). Starting in Junos OS Evolved Release 20.3R1, install packages are available in limited editions. Here are some examples:
|
Junos OS Evolved includes the binaries and libraries for any firmware updates in the
software image. You must first install the Junos OS Evolved software image before you can
perform any firmware upgrades associated with that image. Upgrading the Junos OS Evolved
software does not automatically upgrade the firmware. Starting in Junos OS Evolved Release
24.4R1, for those platforms that support this feature, we now provide separate
jfirmware
packages that contain the firmware binaries necessary to
upgrade the firmware on individual components. (Prior to this release, and for platforms
that do not support this feature, the firmware binaries are included only as part of the
install package.) With this feature, you can download and install the latest
jfirmware
package at any time, and then upgrade the firmware of
individual components with the request system firmware upgrade
command.
This feature enables firmware updates without requiring a complete system upgrade,
minimizing disruption and downtime. You also do not have to wait to upgrade the firmware
until the next time you upgrade the software on your
system.
Install package name | Jfirmware package name |
---|---|
junos-evo-install-acx-chassis-x86-64-<release>-EVO.iso |
jfirmware-junos-evo-install-acx-chassis-x86-64-<release>-EVO.tgz |
junos-evo-install-ptx-chassis-x86-64-<release>-EVO.iso |
jfirmware-junos-evo-install-ptx-chassis-x86-64-<release>-EVO.tgz |
Although the jfirmware
package names have release numbers in them, the
packages themselves are version independent; that is, they can be installed on a system that
is running a different version of software.
Junos OS Evolved Release Numbers
Junos OS Evolved uses the same release numbering system as Junos OS.
Each release has certain new features that complement the software processes that support Internet routing protocols, control the device’s interfaces and the device chassis, and allow for device system management. From the web page for Juniper Networks Software Downloads, you download software for a particular release number.
In this example, we dissect the format of the software release number in the installation package to show what it indicates. The generalized format is as follows:
Given the format of:
-
m.nZb.s-EVO
The software release number 20.4R1.17-EVO, for example, maps to this format as follows:
-
m is the main release number of the product, for example, 20.
-
n is the minor release number of the product, for example, 4.
-
Z is the type of software release, for example, R for an FRS or a maintenance release.
-
b is the build number of the product, for example, 1, indicating the FRS rather than a maintenance release.
-
s is the spin number of the product, for example, 17.
-
-EVO means that it is a Junos OS Evolved package.
Release Type | Description |
---|---|
R |
First revenue ship (FRS) or maintenance release software. R1 is FRS. R2 is a maintenance release. |
B |
Beta release software. |
I |
Internal release software. These packages are private software releases for verifying fixes. |
S |
Service release software, released to customers to solve a specific problem—Juniper Networks will maintain this release along with the life span of the underlying release. The service release number is after the R number; for example, 20.3R1-S2.12. Here, S2 represents the 2nd service release on top of 20.3R1 and is the 12th re-spin. |
Junos OS Evolved Editions
Edition names show up in the installation package name between the release number string and the extension.
For Junos OS Evolved:
-
A null (empty) edition field denotes the standard image for Junos OS Evolved.
-
limited—Starting in Junos OS Evolved 20.3R1, limited packages are available. Limited packages do not have cryptographic support and are intended for countries in the Eurasian Customs Union (EACU). These countries have import restrictions on software containing data-plane encryption. An example of a limited package image for a PTX router is junos-evo-install-ptx-fixed-x86-64-20.4R1.17-EVO-limited.iso.