Junos OS Installation Package Names

 

The installation package is used to upgrade or downgrade from one release to another. When installed, the installation package completely reinstalls the software, rebuilds the Junos OS file system, and can erase system logs and other auxiliary information from the previous installation. The installation package does, however, retain the configuration files from the previous installation.

Junos OS installation packages have the following general pattern:

  • prefix-release-edition-signed.extension

For enhanced automation variants of Junos OS, the installation package looks like this:

  • prefix-flex-release-edition-signed.extension

The signed part of the filename indicates that the software is delivered in signed packages that contain digital signatures, Secure Hash Algorithm (SHA-1), and Message Digest 5 (MD5) checksums. A package is installed only if the checksum within it matches the hash recorded in its corresponding file. Which checksum is used depends on the software version:

  • Digital signatures are used when you upgrade or downgrade between Junos OS Release 7.0 and a later version.

  • The SHA-1 checksum is used when you upgrade or downgrade between Junos OS Release 6.4 and a later version.

  • The MD5 checksum is used when you upgrade or downgrade between Junos OS Release 6.3 or earlier and a later version.

Starting in 2015, the word signed appears less frequently after the edition in the filename. But you might still see it in software installation packages. Whether signed appears or not, all Junos OS images from Junos OS Release 15.1 on are signed for validation.

Extensions are tgz, gz, img, iso, etc.

For more detail on the makeup of the installation package filename, see the following sections:

Junos OS Installation Packages Prefixes

The first part of the installation package filename is a combination of a standard prefix and product designation. Table 1 lists a variety of Junos OS package name prefixes.

Starting in Junos OS Release 15.1, certain hardware platforms run a Junos OS based on an upgraded FreeBSD kernel (hereafter called Junos OS with upgraded FreeBSD). Table 1 also indicates the prefixes used for the different platforms running Junos OS with upgraded FreesBSD.

SRX Series packages use the following naming convention for package prefixes:

  • junos-product

Table 1 lists several examples of installation package prefixes for the SRX Series.

Table 1 does not list packages you do not use with the request system software add command. For information on packages you load onto a USB drive to install, see Chapter 10 of the Software Installation and Upgrade Guide.

Table 1: Installation Package Prefixes

Installation Package PrefixDescription

jinstall*

Junos OS for M Series, MX Series, T Series, TX Matrix, and TX Matrix Plus routers.

jinstall64*

64-bit Junos OS for the JCS1200 Route Reflector, TX Matrix Plus routers with 3D SIBs, and PTX Series Packet Transport Routers.

jinstall-ex*

Junos OS for the EX Series Ethernet Switch portfolio.

jinstall-host-nfx-2*

Junos OS with upgraded FreeBSD for NFX2xx platforms that are Linux based; this prefix indicates the image includes the host and Junos OS.

For details and specific examples of package names for Junos OS with upgraded FreeBSD, see Changes in Package Names for Junos OS with Upgraded FreeBSD.

jinstall-host-qfx*

Junos OS with upgraded FreeBSD for QFX platforms that are Linux based; this prefix indicates the image includes the host and Junos OS. For example, jinstall-host-qfx-5-release.tgz is the package name for Junos OS on the QFX5100.

For details and specific examples of package names for Junos OS with upgraded FreeBSD, see Changes in Package Names for Junos OS with Upgraded FreeBSD.

jinstall-ocx-flex*

OCX Series switches.

jinstall-ppc*

Junos OS for the ACX Series, MX5, MX10, MX40, MX80, and MX104 routers.

junos-arm

Junos OS with Upgraded FreeBSD for EX2300 and EX3400 switches.

For details and specific examples of package names for Junos OS with upgraded FreeBSD, see Changes in Package Names for Junos OS with Upgraded FreeBSD.

junos-install*

Junos OS with upgraded FreeBSD for EX Series and MX Series routers that support Junos OS with upgraded FreeBSD.

For specific examples of package names for Junos OS with upgraded FreeBSD, see Changes in Package Names for Junos OS with Upgraded FreeBSD.

junos-evo-install*

Junos OS Evolved, 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). Here are some examples:

  • junos-evo-install-qfx-ms-fixed-x64-64-version.iso—Single image for all QFX platforms based on merchant silicon. It could be Broadcom family or any other vendor.

  • junos-evo-install-ptx-fixed-x64-64-version.iso—All fixed PTX platform variants (that is, PTX 10003, and so on) have a single ISO image. For PTX orders, this image is installed as factory default.

  • junos-evo-install-qfx-fixed-x64-64-version.iso—All fixed QFX platform variants have a single ISO image. For QFX orders, this image is installed as factory default.

  • junos-evo-install-ptx-chassis-x64-64-version.iso—One single ISO image for PTX chassis platforms.

  • junos-evo-install-qfx-chassis-x64-64-version.iso—One single ISO image for PTX chassis platforms.

junos-srx1k3k*

Junos OS for SRX1400, SRX3400 and SRX3600.

junos-srx5000*

Junos OS for SRX5400, SRX5600, and SRX5800.

junos-srxentedge*

Junos OS for SRX1500.

junos-srxmr*

Junos OS for SRX4100 and SRX4200.

junos-srxsme*

Junos OS for SRX300, SRX320, SRX340, SRX345, and SRX550M .

junos-vmhost-install*

Junos OS with upgraded FreeBSD on VM Host.

junos-install-media-pxe-srxhe-x86* (USB)

junos-install-media-usb-srxhe-x86* (PXE

junos-srxhe-x86* (CLI)

Junos OS for SRX4600

See also

Junos OS Release Numbers

Note

Junos OS Evolved uses the same release numbering system as Junos OS.

The Junos OS release number represents a particular revision of the software that runs on a Juniper Networks routing platform, for example, Junos OS Release 14.1,14.2, 15.1, or 17.1. Each Junos OS release has certain new features that complement the software processes that support Internet routing protocols, control the device’s interfaces and the device chassis itself, and allow device system management. On the Juniper Networks Support web page, you download Junos OS for a particular Junos OS release number.

In this example, we dissect the format of the software release number to show what it indicates. The generalized format is as follows:

Given the format of

  • m.nZb.s

The software release number 17.2R1.13, for example, maps to this format as follows:

  • m is the main release number of the product, for example, 17.

  • n is the minor release number of the product, for example, 2.

  • Z is the type of software release, for example, R for FRS or maintenance release.

    For types of software releases, see Table 2.

  • 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, 13.

Table 2: Software Release Types

Release Type

Description

R

First revenue ship (FRS) or maintenance release software. R1 is FRS. R2 onward are maintenance releases.

F

Feature velocity release. Feature velocity releases are only in Junos OS Release 15.1.

B

Beta release software.

I

Internal release software. These are private software releases for verifying fixes.

S

Service release software, which are released to customers to solve a specific problem—this release will be maintained along with the life span of the underlying release. The service release number is added after the R number, for example, 14.2R3-S4.4. Here S4 represents the 4th service release on top of 14.2R3 and is the 4th respin.

X

Special (eXception) release software. X releases follow a numbering system that differs from the standard Junos OS release numbering.

Starting with Junos OS Release 12.1X44-D10, SRX Series devices follow a special naming convention for Junos OS releases. For more information, refer to the Knowledge Base article KB30092 at https://kb.juniper.net/InfoCenter/index?page=home.

Note

Prior to Junos OS Release 11.4, the software release number format for service releases was same as other releases. For example, 10.4S4.2 represented the 4th service release and 2nd respin of 10.4.

Junos OS Editions

Editions show up in the installation package name after the release number string and before signed.

In releases earlier than Junos OS Release 15.1, installation packages came in several major software package categories or editions, such as domestic, worldwide, or Federal Information Processing Standard (FIPS). For those still using packages with names including these terms, here is what they indicate:

  • domestic—Junos OS for customers in the United States and Canada and for all other customers with a valid encryption agreement. This edition includes high-encryption capabilities such as IPsec and SSH for data leaving the router or switch. Later images use a null, or empty, edition field for this category.

  • limited—Junos OS for all other customers. This edition does not include any high-encryption capabilities for data leaving the router or switch. Sometimes referred to as the Export edition, starting in Junos OS Release 15.1R1, this category is is renamed to the limited edition.

  • fips—Junos OS that provides advanced network security for customers who need software tools to configure a network of Juniper Networks routers and switches in a Federal Information Processing Standards (FIPS) 140-2 environment. For more information about Junos-FIPS, see FIPS 140-2 Security Compliance. In later images, FIPS, instead of being a separate edition, is an option you select on installation.

Starting with Junos OS 15.1, a simplified edition scheme was started:

  • Junos OS with a null (empty) edition field is the standard image for Junos OS.

  • limited—Version has no cryptographic support and is intended for countries in the Eurasian Customs Union (EACU). These countries have import restrictions on software containing data-plane encryption.

FIPS 140-2 Security Compliance

For advanced network security, a special version of Junos OS, called Junos-FIPS 140-2, is available. Junos-FIPS 140-2 provides customers with software tools to configure a network of Juniper Networks devices in a FIPS environment. FIPS support includes:

  • Upgrade package to convert Junos OS to Junos-FIPS 140-2

  • Revised installation and configuration procedures

  • Enforced security for remote access

  • FIPS user roles (Crypto Officer, User, and Maintenance)

  • FIPS-specific system logging and error messages

  • IPsec configuration for Routing Engine–to–Routing Engine communication

  • Enhanced password creation and encryption

Starting in Junos OS Release 15.1, Junos-FIPS is packaged in a domestic image only: a single Junos OS image supports both domestic and FIPS features. Users that have the FIPS credentials and permission to login can flip between a regular Junos image and FIPS image.

Note

Junos-FIPS has special password requirements. FIPS passwords must be between 10 and 20 characters in length. Passwords must use at least three of the five defined character sets (uppercase letters, lowercase letters, digits, punctuation marks, and other special characters). If Junos-FIPS is installed on the device, you cannot configure passwords unless they meet this standard.

Changes in Package Names for Junos OS with Upgraded FreeBSD

Junos OS with upgraded FreeBSD is based on an upgraded FreeBSD kernel and has been released on a platform-by-platform basis starting in Junos OS Release 15.1. Package-naming conventions changed in certain ways with the release of Junos OS with upgraded FreeBSD, depending on the hardware platform.

Junos OS with upgraded FreeBSD packages use XML description files instead of scripts.

Installation package names for VM hosts begin with the junos-vmhost-install prefix.

For information on and examples of other installation package names for Junos OS with upgraded FreeBSD, see the following subsections:

Linux-Based Platforms Package Names

The following are components of the Junos OS with upgraded FreeBSD package-naming conventions for Linux-based packages such as those for SRX Series, ACX Series, NFX Series, OCX Series, and PTX Series:

  • Prefix—Linux-based devices use the jinstall-host prefix for Junos OS with upgraded FreeBSD.

  • Platform—This field indicates the major product group, such as acx, nfx, ocx, or ptx.

  • Product—This field indicates the specific product.

  • Architecture—This field indicates the CPU architecture of the platforms. Values include x86 for Intel and arm for Advanced RISC Machines CPUs.

  • Application Binary Interface (ABI)—This field indicates the “word length” of the CPU architecture. Values include 32 for 32-bit architectures and 64 for 64-bit architectures.

  • Release—This field indicates the release number, such as 17.3R1.3.

  • Edition—The edition field is null (empty) for standard (domestic) images. For jurisdictions with limits on dataplane encryption, this field is set to limited.

Examples of valid Junos OS with upgraded FreeBSD package names include the following:

  • jinstall-host-acx5k-17.2R1.13-signed.tgz

  • jinstall-host-nfx-2-flex-x86-32-17.2R1.13-secure-signed.tgz

EX Series Switches Package Names

There are multiple conventions for naming installation packages for EX Series switches.

  • The EX9200 switch is based on the MX Series routers and has the same package-naming convention as the MX Series routers. See MX Series Routers Package Names.

  • The EX4600 switch is based on the QFX5100 platform and has the same package-naming convention as the QFX5100 platform. See QFX Series and EX4600 Switches Package Names.

  • The components of the Junos OS with Upgraded FreeBSD package-naming conventions for EX2300 and EX3400 switches are as follows:

    • Prefix—This is junos-arm. This prefix takes the place of the jinstall prefix used in earlier releases of Junos OS.

    • Media keyword—Added to the prefix, a media keyword is only used when the image is not for use with the request system software add command. Media keywords follow the term media in the package name. Values for the media keyword include the following:

      • usb for images installed from a USB drive

      • net for images installed from the loader prompt

    • Architecture—This field indicates the CPU architecture of the platforms. Values include x86 for Intel and arm for Advanced RISC Machines CPUs.

    • Application Binary Interface (ABI)—This field indicates the “word length” of the CPU architecture. Values include 32 for 32-bit architectures and 64 for 64-bit architectures.

    • Release—This field indicates the release number, such as 15.1R1.9.

    • Edition—The edition field is null (empty) for standard (domestic) images. For jurisdictions with limits on dataplane encryption, this field is set to limited.

    As before, all images are in tarred and gzipped (.tgz) format.

    Note

    There are no longer “export” worldwide images or separate FIPS images. The keyword “signed” no longer appears because all Junos OS images are signed for validation.

Examples of valid Junos OS software package names include the following:

  • junos-arm-32-15.1X53-D50.2.tgz—Image for an EX2300 or EX3400 platform for jurisdictions without limits on dataplane encryption.

  • junos-arm-32-15.1X53-D50.2-limited.tgz —Image for an EX2300 or EX3400 platform for jurisdictions with limits on dataplane encryption.

  • junos-install-media-usb-arm-32-15.1X53-D50.2.img—Image stored on and installed from a USB drive for a EX2300 or EX3400 platform for jurisdictions without limits on dataplane encryption.

  • junos-install-media-net-arm-32-15.1X53-D50.2.tgz—Image stored on the tftp server and installed from a loader prompt for a EX2300 or EX3400 platform for jurisdictions without limits on dataplane encryption.

MX Series Routers Package Names

The components of the Junos OS with Upgraded FreeBSD package-naming conventions for MX Series routers and EX9200 switches are as follows:

  • Prefix—This is junos-install. This prefix takes the place of the jinstall prefix used in earlier releases of Junos OS.

  • Media keyword—Added to the prefix, a media keyword is only used when the image is not for use with the request system software add command. Media keywords follow the term media in the package name. Values for the media keyword include the following:

    • usb for images installed from a USB drive

    • net for images installed from the loader prompt

  • Platform—This field indicates the major product group, such as ex92xx or mx.

  • Architecture—This field indicates the CPU architecture of the platforms. Values include x86 for Intel and arm for Advanced RISC Machines CPUs.

  • Application Binary Interface (ABI)—This field indicates the “word length” of the CPU architecture. Values include 32 for 32-bit architectures and 64 for 64-bit architectures.

  • Release—This field indicates the release number, such as 17.3R1.3.

  • Edition—The edition field is null (empty) for standard (domestic) images. For jurisdictions with limits on dataplane encryption, this field is set to limited.

As before, all images are in tarred and gzipped (.tgz) format.

Note

There are no longer “export” worldwide images or separate FIPS images. The keyword “signed” no longer appears because all Junos OS images are signed for validation.

Examples of valid Junos OS with upgraded FreeBSD package names include the following:

  • junos-install-mx-x86-32-15.1R1.9.tgz—Image for a supported MX Series platform for jurisdictions without limits on dataplane encryption.

  • junos-install-mx-x86-32-15.1R1.9-limited.tgz—Image for a supported MX Series platform used for jurisdictions with limits on dataplane encryption.

  • junos-install-media-usb-mx-x86-32-15.1R1.9.tgz—Image stored on and installed from a USB drive for a supported MX Series platform for jurisdictions without limits on dataplane encryption.

  • junos-install-ex92xx-x86-64-17.2R1.13-limited.tgz—Image for an EX9200 plaform for jurisdictions with limits on dataplane encryption.

  • junos-install-media-usb-ex92xx-17.2R1.13.img.gz—Image stored on and installed from a USB for an EX9200 platform for jurisdictions without limits on dataplace encryption.

QFX Series and EX4600 Switches Package Names

The components of the Junos OS with upgraded FreeBSD package-naming conventions for QFX Series and EX4600 switches installation packages are as follows:

  • Prefix—Linux-based devices use the jinstall-host prefix for Junos OS with upgraded FreeBSD.

  • Platform—This field indicates the major product group, such as ex-4600 or qfx.

  • Product—This field indicates the specific product, such as 5e or 10-f or 10-m

  • Architecture—This field indicates the CPU architecture of the platforms. Values include x86 for Intel and arm for Advanced RISC Machines CPUs.

  • Application Binary Interface (ABI)—This field indicates the “word length” of the CPU architecture. Values include 32 for 32-bit architectures and 64 for 64-bit architectures.

  • Release—This field indicates the release number, such as 17.3R1.3.

  • Edition—The edition field is null (empty) for standard (domestic) images. For jurisdictions with limits on dataplane encryption, this field is set to limited.

Examples of valid Junos OS with upgraded FreeBSD package names include the following:

  • jinstall-host-ex-4600-17.2R1.13-limited-signed.tgz

  • jinstall-host-ex-4600-17.2R1.13-signed.tgz

  • jinstall-host-qfx-5e-x86-64-17.2R1.13.tgz

  • jinstall-host-qfx-10-f-flex-x86-64-17.2R1.13-secure-signed.tgz

  • jinstall-host-qfx-10-m-x86-64-17.2R1.13-secure-limited-signed.tgz

  • jinstall-host-qfx-5-17.2R1.13-limited-signed.tgz

SRX5400, SRX5600, and SRX5800 Devices Package Names

The components of the Junos OS with upgraded FreeBSD package-naming conventions for SRX5400, SRX5600, and SRX5800 are as follows:

  • Prefix—This is junos-install. This prefix takes the place of the prefix junos-srx5000.

  • Media keyword—Added to the prefix, a media keyword is only used when the image is not for use with the request system software add command. Values for the media keyword include usb for images installed from a USB drive or net for images installed from the loader prompt; for example, the entire prefix of your package might be junos-install-media-net or junos-install-media-usb.

  • Architecture—This field indicates the CPU architecture of the platforms. Values include x86 for Intel and arm for Advanced RISC Machines CPUs.

  • Application binary interface (ABI)—This field indicates the “word length” of the CPU architecture. Values include 32 for 32-bit architectures and 64 for 64-bit architectures.

  • Release—This field indicates the release number, such as 17.3.

  • Edition—The edition field is null (empty) for the standard (domestic) images. For jurisdictions with limits on dataplane encryption, this field is set to limited.

Note

There are no longer “export” worldwide images or separate FIPS images. The keyword “signed” no longer appears because all Junos OS images are signed for validation.

Examples of valid Junos OS software package names include the following:

  • junos-install-srx5000-x86-64-17.3R1.9.tgz—An image for a SRX5400, SRX5600, and SRX5800 devices.

  • junos-install-media-usb-srx5000-x86-64-17.3R1.9.img.gz—An image stored on and installed from a USB flash drive for SRX5400, SRX5600, and SRX5800 devices.