Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Installing Software on QFX Series Devices

 

QFX Series devices are delivered with preinstalled Junos operating system (Junos OS). Before you start this procedure, decide which software package you need and download it. For information on which packages to use for which upgrades, see Junos OS Installation Package Names.

Installing Software Packages on QFX Series Devices

We recommend that you connect to the console port while installing the installation package so you can respond to any required user input and detect any errors that may occur.

Before you install the new installation package, back up your current configuration files because the upgrade process removes all of the stored files on the switch.

To back up your current configuration files, enter the save command:

user@switch# save filename

Executing this command saves a copy of your configuration files to a remote location such as an external USB device.

Installation procedures are in the following subsections:

Installing the Software on QFX10002-60C Switches

This section explains how to upgrade the software, which includes both the host OS and the Junos OS. This upgrade requires that you use a VM host package—for example, a junos-vmhost-install-x.tgz .

During a software upgrade, the alternate partition of the SSD is upgraded, which will become primary partition after a reboot. If there is a bootfailure on the primary SSD, the switch can boot using the snapshot available on the alternate SSD.

Note

The QFX10002-60C switch supports only the 64-bit version of Junos OS.

Note

If you have important files in directories other than /config and /var, copy the files to a secure location before upgrading. The files under /config and /var (except /var/etc) are preserved after the upgrade.

To upgrade the software, you can use the following methods:

If the installation package resides locally on the switch, execute the request vmhost software add <pathname><source> command.

For example:

user@switch> request vmhost software add /var/tmp/ -18.1R1.9.tgz

If the Install Package resides remotely from the switch, execute the request vmhost software add <pathname><source> command.

For example:

user@switch> request vmhost software add ftp://ftpserver/directory/junos-vmhost-install-qfx-x86-64-18.1R1.9.tgz

After the reboot has finished, verify that the new version of software has been properly installed by executing the show version command.

user@switch> show version

Installing a Standard Software Package on QFX5100, QFX5110, QFX5200, QFX5210, and EX4600 Switches

Note

Before you install the software, back up any critical files in /var/home. For more information regarding how to back up critical files, contact Customer Support at https://www.juniper.net/support.

Note

On QFX5100 and EX4600 switches, the Host OS is not upgraded automatically, so you must use the force-host option if you want the Junos OS and Host OS versions to be the same.

However, pay attention to these notes regarding Junos OS and Host OS versions:

  • The Junos OS and Host OS versions do not need to be the same.

  • During an ISSU, the Host OS cannot be upgraded.

  • Upgrading the Host OS is not required for every software upgrade, as noted above.

Note

On QFX5100 and EX4600 switches, you must use the force-host option if you are downgrading from Junos OS Release 14.1X53-D40 to any release earlier than 14.1X53-D40 otherwise the switch will issue core dumps.

If the installation package resides locally on the switch, execute the request system software add <pathname><source> reboot command.

For example:

user@switch> request system software add /var/tmp/jinstall-host-qfx-5-17.2R1.n-signed.tgz reboot

If the Install Package resides remotely, execute the request system software add <pathname><source> reboot command.

For example:

user@switch> request system software add ftp://ftpserver/directory/jinstall-host-qfx-5-17.2R1.n-signed.tgz reboot

After the reboot has finished, verify that the new version of software has been properly installed by executing the show version command.

user@switch> show version

Installing a Standard Software Package on QFX10002 Switches

Note

Before you install the software, back up any critical files in /var/home. For more information regarding how to back up critical files, contact Customer Support at https://www.juniper.net/support.

Note

If you want to downgrade from Junos OS Release 15.1X53-D60 to a previous release, pay attention to these caveats:

Table 1: Caveats for Downgrading from Junos OS Release 15.1X53-D60 to Previous Software Releases

Junos OS Software Releases

Using the CLI

Using a USB Stick

15.1X53-D33

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

15.1X53-D32

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D32.

15.1X53-D30

No

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.

Releases prior to 15.1X53-D30

No

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.

Install the software in one of two ways:

  • If the installation package resides locally on the switch, execute the request system software add <pathname><source> reboot command.

    For example:

    user@switch> request system software add /var/tmp/jinstall-host-qfx-10-17.2R1.n-secure-signed.tgz reboot
  • If the Install Package resides remotely, execute the request system software add <pathname><source> reboot command.

    For example:

    user@switch> request system software add ftp://ftpserver/directory/jinstall-host-qfx-10-17.2R1.n-secure-signed.tgz reboot

After the reboot has finished, verify that the new version of software has been properly installed by executing the show version command.

user@switch> show version

Upgrading Software from Junos OS Release 15.1X53-D3X to Junos OS Release 15.1X53-D60, 15.1X53-D61.7, 15.1X53-D62, and 15.1X53-D63 on QFX10008 and QFX10016 Switches

Note

Before you install the software, back up any critical files in /var/home. For more information regarding how to back up critical files, contact Customer Support at https://www.juniper.net/support.

Note

If you want to downgrade from Junos OS Release 15.1X53-D60 to a previous release, pay attention to these caveats:

Table 2: Caveats for Downgrading from Junos OS Release 15.1X53-D60 to Previous Software Releases

Junos OS Software Releases

Using the CLI

Using a USB Stick

15.1X53-D33

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

15.1X53-D32

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D32.

15.1X53-D30

No

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.

Releases prior to 15.1X53-D30

No

Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.

Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.

The switch contains two routing engines, so you will need to install the software on each routing engine (re0 and re1).

If the installation package resides locally on the switch, execute the request system software add <pathname><source> command.

To install the software on re0:

user@switch> request system software add /var/tmp/jinstall-host-qfx-10-m-15.1X53-D60.4-secure-domestic-signed.tgz re0

If the Install Package resides remotely from the switch, execute the request system software add <pathname><source> re0 command.

For example:

user@switch> request system software add ftp://ftpserver/directory/jinstall-host-qfx-10-m-15.1X53-D60.4-secure-domestic-signed.tgz re0

To install the software on re1:

user@switch> request system software add /var/tmp/jinstall-host-qfx-10-m-15.1X53-D60.4-secure-domestic-signed.tgz re1

If the Install Package resides remotely from the switch, execute the request system software add <pathname><source> re1 command.

For example:

user@switch> request system software add ftp://ftpserver/directory/jinstall-host-qfx-10-m-15.1X53-D60.4-secure-domestic-signed.tgz re1

Reboot both routing engines.

For example:

user@switch> request system reboot both-routing-engines

After the reboot has finished, verify that the new version of software has been properly installed by executing the show version command.

user@switch> show version

Installing a Software Package on QFX10008 and QFX10016 Switches

Because the switch has two Routing Engines, perform a Junos OS installation on each Routing Engine separately to avoid disrupting network operation.

Note

Before you install the software, back up any critical files in /var/home. For more information regarding how to back up critical files, contact Customer Support at https://www.juniper.net/support.

Caution

If graceful Routing Engine switchover (GRES), nonstop bridging (NSB), or nonstop active routing (NSR) is enabled when you initiate a software installation, the software does not install properly. Make sure you issue the CLI delete chassis redundancy command when prompted. If GRES is enabled, it will be removed with the redundancy command. By default, NSR is disabled. If NSR is enabled, remove the nonstop-routing statement from the [edit routing-options] hierarchy level to disable it.

To upgrade the software, perform the following tasks:

  1. Preparing the Switch for Installation

  2. Installing Software on the Backup Routing Engine

  3. Installing Software on the Master Routing Engine

Preparing the Switch for Installation

Perform the following steps before installing the software:

  1. Log in to the master Routing Engine’s console.

    For more information about logging in to the Routing Engine through the console port, see the specific hardware guide for your switch.

  2. From the command line, enter configuration mode:

    user@switch> configure
  3. Disable Routing Engine redundancy:

    user@switch# delete chassis redundancy
  4. Disable nonstop-bridging:

    user@switch# delete protocols layer2-control nonstop-bridging
  5. Save the configuration change on both Routing Engines:

    user@switch# commit synchronize
  6. Exit the CLI configuration mode:

    user@switch# exit

Installing Software on the Backup Routing Engine

After the switch has been prepared, you first install the new Junos OS release on the backup Routing Engine, while keeping the currently running software version on the master Routing Engine. This enables the master Routing Engine to continue operations, minimizing disruption to your network.

After making sure that the new software version is running correctly on the backup Routing Engine, you are ready to switch routing control to the backup Routing Engine, and then upgrade or downgrade the software version on the other Routing Engine.

  1. Log in to the console port on the other Routing Engine (currently the backup).

    For more information about logging in to the Routing Engine through the console port, see the specific hardware guide for your switch.

  2. Install the new software package using the request system software add command:

    user@switch> request system software add validate /var/tmp/jinstall-host-qfx-10-17.2R1.n-secure-signed.tgz

    For more information about the request system software add command, see the CLI Explorer.

  3. Reboot the switch to start the new software using the request system reboot command:

    user@switch> request system reboot
    Note

    You must reboot the switch to load the new installation of Junos OS on the switch.

    To abort the installation, do not reboot your switch. Instead, finish the installation and then issue the request system software delete <package-name> command. This is your last chance to stop the installation.

    All the software is loaded when you reboot the switch. Installation can take between 5 and 10 minutes. The switch then reboots from the boot device on which the software was just installed. When the reboot is complete, the switch displays the login prompt.

    While the software is being upgraded, the Routing Engine on which you are performing the installation is not sending traffic.

  4. Log in and issue the show version command to verify the version of the software installed.

    user@switch> show version

Installing Software on the Master Routing Engine

Once the software is installed on the backup Routing Engine, you are ready to switch routing control to the backup Routing Engine, and then upgrade or downgrade the master Routing Engine software:

  1. Log in to the master Routing Engine console port.

    For more information about logging in to the Routing Engine through the console port, see the specific hardware guide for your switch.

  2. Transfer routing control to the backup Routing Engine:

    user@switch> request chassis routing-engine master switch

    For more information about the request chassis routing-engine master command, see the CLI Explorer.

  3. Verify that the backup Routing Engine (slot 1) is the master Routing Engine:

    user@switch> show chassis routing-engine
  4. Install the new software package using the request system software add command:

    user@switch> request system software add validate /var/tmp/jinstall-host-qfx-10-17.2R1.n-secure-signed.tgz

    For more information about the request system software add command, see the CLI Explorer.

  5. Reboot the Routing Engine using the request system reboot command:

    user@switch> request system reboot
    Note

    You must reboot to load the new installation of Junos OS on the switch.

    To abort the installation, do not reboot your system. Instead, finish the installation and then issue the request system software delete jinstall <package-name> command. This is your last chance to stop the installation.

    The software is loaded when you reboot the system. Installation can take between 5 and 10 minutes. The switch then reboots from the boot device on which the software was just installed. When the reboot is complete, the switch displays the login prompt.

    While the software is being upgraded, the Routing Engine on which you are performing the installation does not send traffic.

  6. Log in and issue the show version command to verify the version of the software installed.

  7. Transfer routing control back to the master Routing Engine:

    user@switch> request chassis routing-engine master switch

    For more information about the request chassis routing-engine master command, see the CLI Explorer.

  8. Verify that the master Routing Engine (slot 0) is indeed the master Routing Engine:

    user@switch> show chassis routing-engine

Upgrading Software by Using Automatic Software Download for Switches

The automatic software download feature uses the Dynamic Host Configuration Protocol (DHCP) message exchange process to download and install software packages. You configure the automatic software download feature on switches that act as DHCP clients. You must enable automatic software download on a switch before the software upgrade can occur.

You configure a path to a software package file on the DHCP server. The server communicates the path to the software package file through DHCP server messages.

If you enable automatic software download, the DHCP client switch compares the software package name in the DHCP server message with the name of the software package that booted the switch. If the software packages are different, the DHCP client switch downloads and installs the software package specified in the DHCP server message.

Complete the following tasks in order:

Configuring DHCP Services for the Switch

Before you upgrade software by using automatic software download, ensure that you have configured DHCP services for the switch, including configuring a path to a boot server and a boot file.

To configure a path to a boot server and a boot file:

  1. Configure the name of the boot server advertised to DHCP clients. The client uses a boot file located on the boot server to complete DHCP setup. This configuration is equivalent to DHCP option 66:
  2. Set the boot file advertised to DHCP clients. After the client receives an IP address and the boot file location from the DHCP server, the client uses the boot image stored in the boot file to complete the DHCP setup. This configuration is equivalent to DHCP option 67:

Enabling Automatic Software Download on a Switch

To enable automatic software download on a switch that acts as a DHCP client:

After automatic software download is enabled on your DHCP client switch and after DHCP services are enabled on your network, an automatic software download can occur at any time as part of the DHCP message exchange process.

If an automatic software download occurs, you see the following message on the switch:

The switch reboots automatically to complete the upgrade.

Verifying That Automatic Software Download Is Working Correctly

Purpose

Verify that the automatic software download feature is working correctly.

Action

Use the show system services dhcp client interface-name command to verify that the automatic software download feature has been used to install a software package.

user@switch> show system services dhcp client ge-0/0/1.0

Meaning

The output from this command shows the name and location of the software package under DHCP options when automatic software download was last used to install a software package. The sample output in DHCP options shows that the last DHCP server message to arrive on the DHCP client had a boot server address of 10.1.1.1 and a boot file named jinstall-ex-4200-9.6R1.5-domestic-signed.tgz. If automatic software download was enabled on this client switch during the last DHCP message exchange, these values were used by the switch to upgrade the software.

Upgrading Jloader Software on QFX Series Devices

Jloader software contains a boot loader (Uboot), which is used to bring up QFX Series devices and load the Junos OS from the flash memory of these devices. You can upgrade Jloader software on QFX3500 switches, QFX3500 and QFX3600 Node devices, and QFX3600-I and QFX3008-I Interconnect devices.

Note

Before you upgrade the Jloader software, see Table 3, Table 4, and Table 5 to make sure that you are upgrading to the right version of Jloader software for the Junos OS software release running on your QFX3500 switches, or Node devices and Interconnect devices in your QFabric system.

See Table 6 to see which Uboot software versions are available and the filenames of the Jloader software packages.

Table 3: Junos OS and Jloader Software Compatibility Matrix for the QFX3500 Switch and QFX3500 Node Device

Junos OS Software Version

  

1.1.2

1.1.4

1.1.5

1.1.8

11.3R1 and later (QFX3500 switch)

Supported

Supported

Not supported

Supported and recommended

11.3X30.6 and later (QFX3500 Node device)

Supported

Supported

Not supported

Supported and recommended

12.1X49-D1 and later (QFX3500 switch)

Supported

Supported

Not supported

Supported and recommended

12.2X50-D1 and later (QFX3500 switch and QFX3500 Node device)

Supported

Supported

Not supported

Supported and recommended

Note

An en dash means that the item is not applicable.

Table 4: Junos OS and Jloader Software Compatibility Matrix for the QFX3008-I Interconnect Device

Junos OS Software Version

 

1.1.2

1.1.4

1.1.5

1.1.8

11.3X30.9 and later (QFX3008-I Interconnect device)

Supported

Supported

Not supported

Supported and recommended

11.3X30.6 and later (QFX3008-I Interconnect device)

Supported

Supported

Not supported

Supported and recommended

12.2X50-D10.3 and later (QFX3008-I Interconnect device)

Supported

Supported

Not supported

Supported and recommended

Note

An en dash means that the item is not applicable.

Table 5: Junos OS and Jloader Software Compatibility Matrix for the QFX3600-I Interconnect Device and QFX3600 Node Device

Junos OS Software Version

 

1.1.2

1.1.4

1.1.5

1.1.8

12.2X50-D10.3 and later (QFX3600-I Interconnect Device and QFX3600 Node Device)

-

-

Supported

Supported and recommended

12.2X50-D20 and later (QFX3600 switch)

-

-

Supported

Supported and recommended

Table 6: Uboot Software Release and Jloader Software Compatibility Matrix

Uboot Software Release Number

Jloader Software Package Name

1.1.2

jloader-qfx-11.3X30.9-signed.tgz

1.1.4 (11.3R3 and 11.3R2 releases only. Not supported on 11.3R1)

jloader-qfx-11.3I20120127_0733_dc-builder-signed.tgz

1.1.4 (12.1R1 release and later)

jloader-qfx-12.1-20120125_pr.0-signed.tgz

1.1.5 (12.2X50-D10.3 and later)

jloader-qfx-12.2X50.D10.3-signed.tgz

1.1.8 (13.1X50-D15.1 and later)

jloader-qfx-13.3-20130831_pr_branch_qfd.0.tgz

Jloader Software Version 1.1.4 Guidelines

Jloader Release 1.1.4 is compatible with Junos OS Release 11.3R3 and 11.3R2, and Junos OS Release 12.1R1 and later. Jloader Release 1.1.4 is not compatible with Junos OS

Release 11.3R1. The Jloader software package names are different for versions 1.1.4 (Junos OS 11.3R3 and 11.3R2) and 1.1.4 (Junos OS 12.2R1 release and later), but the binaries are the same. Because the binaries are the same, you can upgrade or downgrade to any Junos OS release.

  • If you have Junos OS Release 11.3 installed and want to upgrade the Jloader software from version 1.1.2 to version 1.1.4, you need to upgrade using the jloader-qfx-11.3I20120127_0733_dc-builder-signed.tgz software package.

  • If you have Junos OS Release 11.3R2 installed and want to upgrade to Junos OS Release 12.1, you do not need to upgrade the Jloader Release and can continue to use Jloader Release 1.1.2.

  • If you have Junos OS Release 12.1 installed and want to upgrade the Jloader software from version 1.1.2 to version 1.1.4, you need to upgrade using the jloader-qfx-12.1-20120125_pr.0-signed.tgz software package.

  • If you upgrade to Junos OS Release 12.1, you can upgrade to Jloader Release 1.1.4 using the jloader-qfx-12.1-20120125_pr.0-signed.tgz software package.

Upgrading Jloader Software on a QFX3500 Switch

The Jloader software for a QFX3500 switch resides in two flash memory banks. At any time, one bank acts as the primary bank, and the QFX3500 switch boots from it. The other bank is the backup bank—if the QFX3500 switch cannot boot from the primary bank, it boots from the backup bank. When you upgrade the Jloader software, the upgraded software is installed in the backup bank, which then becomes the new primary bank. Thus the primary and backup banks alternate each time you upgrade the Jloader software, with the primary bank containing the most recently installed version of the software, and the backup bank containing the previous version. To upgrade the Jloader software on a QFX3500 switch, you must perform the upgrade twice: once for each bank. Each upgrade requires that you to reboot the QFX3500 switch.

Note

If you are running Junos OS Release 11.3R1 or Junos OS Release 11.3R2, you must use the no-validate option when you issue the request system software add command to upgrade the Jloader software. Otherwise, the installation will fail and you receive a configuration error. The no-validate option is not required for Junos OS Release 11.3R3 and later.

Note

After you upgrade the Jloader software on the first bank, the software package is deleted after you reboot. Make sure that you have either downloaded the Jloader software package to either a remote site or in a local directory on the switch, such as the /var/tmp directory on the QFX3500 device.

  1. In a browser, go to https://support.juniper.net.

    The Junos Platforms Download Software page appears.

  2. In the QFX Series section of the Junos Platforms Download Software download page, select the QFX Series platform software you want to download.
  3. Select the number of the software version that you want to download.
  4. Read the End User License Agreement, click the I agree radio button, and then click Proceed.
  5. Open or save the jloader-qfx-version-signed.tgz file either to a local system or to a remote location. If you are saving the installation package to a remote system, make sure that you can access it using HTTP, TFTP, FTP, or scp.
  6. Log in to the QFX3500 switch and enter the shell. We recommend using a console connection.
  7. Determine the version of the Jloader software package installed on the switch.

    For example:

    root@switch% ls
    gres-tp krt_gencfg_filter.txt
    jloader-qfx-11.3-20110510.0-signed.tgz
  8. Determine the version of the Uboot software that is running in the bank:

    For example:

    root@switch% kenv | grep boot.version
    boot.version="1.0.7"
  9. Enter the CLI and install the Jloader software package.
    • To install a Jloader software package that is located in the /var/tmp directory, issue the request system software add /var/tmp/jloader-qfx-version.tgz no-validate command:

      For example:

      user@switch> request system software add /var/tmp/jloader-qfx-11.3-20110510.0-signed.tgz no-validate

      You see the following messages during the installation:

    • To install a Jloader software package located on a remote server using FTP, issue the request system software add /ftp://hostname/pathname/jloader-qfx-version-signed.tgz no-validate command.

      For example:

      user@switch> request system software add /ftp://hostname/pathname/jloader-qfx-11.3-20110510.0-signed.tgz no-validate
    • To install a Jloader software package located on a remote server using HTTP, issue the request system software add /http://hostname/pathname/jloader-qfx- version-signed.tgz no-validate command.

      For example:

      user@switch> request system software add /http://hostname/pathname/jloader-qfx-11.3-20110510.0-signed.tgz no-validate
  10. When prompted, reboot the Control Board by issuing the request system reboot command.

    For example:

    user@switch> request system reboot
  11. Enter the shell and verify that the version of the Uboot software in the primary bank is the version you just installed.

    For example:

    root@switch% kenv | grep boot.version
    boot.version="1.1.1"
  12. To install the Jloader software package on the current backup bank, repeat Step 10 through Step 14.

Upgrading Jloader Software on a QFabric System

This procedure explains how to upgrade the Jloader software on your Node devices and Interconnect devices. The example shows how to upgrade the Jloader Release 1.1.1 to 1.1.2 on a Node device with the serial number BBAK1186.

Note

Before you upgrade the Jloader software, make sure you have the serial numbers of the Node devices, Interconnect devices, and Control Boards in the Interconnect devices you want to upgrade.

  1. Issue the show chassis hardware node-device ? command to view the serial numbers of the Node devices.

    For example:

    user@qfabric> show chassis hardware node-device ?

    An example of a Node device serial number is BBAK1186.

  2. Issue the show chassis hardware interconnect-device ? command to view the serial numbers of the Interconnect devices.

    For example:

    user@qfabric> show chassis hardware interconnect-device ?

    The Interconnect device serial numbers are IC-F1052 and IC-F3947.

  3. Issue the show chassis hardware interconnect-device name command to view the serial numbers of the Control Boards in the Interconnect device.

    For example:

    user@qfabric> show chassis hardware interconnect-device IC-F3947

    The Control Board serial numbers are ZJ9432 and ZJ9404.

  4. Issue the show chassis firmware node-device name command to see which version of Uboot software you have installed on your Node device.

    For example:

    user@qfabric> show chassis firmware node-device BBAK1186

    The Uboot software version is 1.1.1. The loader software version appears after the timestamp for U-Boot 1.1.6.

  5. Issue the show chassis firmware interconnect-device name command to see which version of Uboot software you have installed on the Routing Engines located on the Control Boards of the Interconnect device.

    For example:

    user@qfabric> show chassis firmware interconnect-device IC-F3947

    The Uboot software version is 1.1.4. The loader software version appears after the timestamp for U-Boot 1.1.6.

  6. In a browser, go to https://support.juniper.net.

    The Downloads page appears.

  7. Select the product you want software for.
  8. Find and click the file you want to download.

    A login screen appears.

  9. Enter your username and password, and press Enter.
  10. Read the End User License Agreement, click the I agree radio button, and then click Proceed.
  11. Open or save the jloader-qfx-version-signed.tgz file either to a local system or to a remote location. If you are saving the installation package to a remote system, make sure that you can access it using HTTP, TFTP, FTP, or scp.
  12. Retrieve the software from the location in which you downloaded it. To do this, issue the request system software download /path/package-name command.

    For example:

    user@qfabric> request system software download ftp://server/files/jloader-qfx-11.3X30.9-signed.tgz
  13. Log in to the Director device as root and enter the shell to verify that you have downloaded the Jloader software package. We recommend using a console connection. The software package is copied from where you downloaded it and is placed locally on the QFabric system in the /pbdata/packages directory.

    For example:

    [root@dg0] # pwd
    [root@dg0] # ls
  14. Before you copy over the Jloader software package to the Node device or Interconnect device, determine the directory that matches the serial number of the Node device or Interconnect device that you want to upgrade. View the remote logs and the Node device and Interconnect device serial numbers by issuing the ls /pdbata/export/rlogs command at the command line of the Director device before you copy the software package over to the device.Note

    The /pbdata/export/rlogs/node-device-serial-ID and /pbdata/export/rlogs/interconnect-device-serial-ID directories on the Director device are NFS mounted as the /tftpboot/logfiles directories on the Node device and Interconnect device. These directories are created for all Node devices and Interconnect devices in a QFabric system. The Jloader files are stored in the /tftpboot/logfiles directories for each Node device and Interconnect device.

    For example:

    [root@dg0 tmp] # ls /pdbata/export/rlogs

    BBAK1186 is the serial number of the Node device that needs to be upgraded.

  15. Copy the Jloader software package from the /var/tmp directory to the /pbdata/export/rlogs/BBAK1186 directory.

    For example:

    [root@dg0 tmp] # cp jloader-qfx-11.3X30.9-signed.tgz /pbdata/export/rlogs/BBAK1186
  16. Confirm that the Jloader software package you copied over is in the /pbdata/export/rlogs/BBAK1186 directory.

    For example:

    [root@dg0 tmp] # ls /pbdata/export/rlogs/BBAK1186
  17. Issue the /root/dns.dump command to find out the internal IP addresses of the Node device or Interconnect device.
    [root@dg0 tmp] # /root/dns.dump

    The internal IP address for BBAK1186 is 169.254.128.14.

  18. Upgrade the Jloader software on the Node device or Interconnect device.

    Before you can upgrade the Jloader software, you need to use SSH to log in to the Node device or Interconnect device and verify that the software is in the /tftpboot/logfiles directory.

    1. Use SSH to log in to the Node device or Interconnect device.

      For example:

      [root@dg0 tmp] # ssh 160.254.128.14
    2. Verify that the Jloader software package is in the tftpboot/logfiles directory of the Node device or Interconnect device.

      For example:

      root@sng3% ls /tftpboot/logfiles
    3. Copy the Jloader software package from the /tftpboot/logfiles directory to the /var/tmp directory of the Node device or Interconnect device.

      For example:

      root@sng3% cp /tftpboot/logfiles/jloader-qfx-11.3X30.9-signed.tgz /var/tmp
    4. Verify that the Jloader software package is in the /var/tmp directory of the Node device or Interconnect device.

      For example:

      root@sng3% ls /var/tmp
    5. Enter CLI mode and issue the request system software add /var/tmp/jloader-qfx-version-signed.tgz command.

      For example:

      root@sng3% cli
      root@sng3> request system software add /var/tmp/jloader-qfx-11.3X30.9-signed.tgz
    6. Reboot both the Node device and Interconnect device twice, because they each contain two partitions.

      For example:

      root@sng3> request system reboot
    7. Verify that the Uboot software on the Node device or Interconnect device has been upgraded to the new Uboot software by logging in to the QFabric CLI and issuing either the show chassis firmware node-device name command or the show chassis firmware interconnect-device name command.

      For example:

      user@qfabric> show chassis firmware node-device BBAK1186

      The Uboot software version is now 1.1.2. The loader software version appears after the timestamp for U-Boot 1.1.6.

Installing Junos OS Software with Junos Automation Enhancements

Junos operating system (Junos OS) with Junos Automation Enhancements is a full-featured version of Junos OS with Veriexec disabled, which can only be installed on supported devices.

Note

You must install the jinstall-qfx-5-flex-x.tgz software bundle in order to use the automation enhancements.

Before you install software, download the Junos OS jinstall-qfx-5-flex-x.tgz software bundle. For information on downloading and accessing the files, see Installing Software Packages on QFX Series Devices.

Best Practice

Before you install the software, back up any critical files in /var/home. For more information regarding how to back up critical files, contact Customer Support at https://www.juniper.net/support.

Install the software:

  1. Execute the request system software add command with the validate option:

    • If the installation package resides locally on the switch, execute the request system software add validate pathname source reboot command, using the following format:

      user@switch> request system software add validate /var/tmp/jinstall-qfx-5-flex-x.tgz reboot
    • If the installation package resides remotely, execute the request system software add validate pathname source reboot command, using the following format:

      user@switch> request system software add validate ftp://ftpserver/directory/jinstall-qfx-5-flex-x.tgz reboot
  2. After the reboot has finished, verify that the new version of software has been properly installed by executing the show version command.

    user@switch> show version
Note

If you are upgrading a device from standard Junos OS to use Junos Automation Enhancements and you are not loading the new factory default configuration, you need to use the following procedure.

To upgrade an existing device from standard Junos to use Junos Automation Enhancements:

  1. Edit your existing Junos OS configuration to include the following configuration statements:
    [edit]

    user@switch# set system extensions providers juniper license-type juniper deployment-scope commercial

    user@switch# set system extensions providers chef license-type juniper deployment-scope commercial
Note

The factory default configuration of the QFX5100 switch jinstall-qfx-5-flex-x.tgz software bundle is a Layer 3 configuration, whereas the factory default configuration for QFX5100 switch software bundles is a Layer 2 configuration. Therefore, if you are running the jinstall-qfx-5-flex-x.tgz software bundle on a QFX5100 switch and you use the load factory-default command, the resulting factory default configuration is set up for Layer 3 interfaces.

This is the factory default configuration for QFX5100 switch jinstall-qfx-5-flex-x.tgz software bundle:

user@switch> show configuration