Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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.