This article lists the complete steps to upgrade an QFX5100 virtual chassis.

• In order to upgrade a virtual chassis, the following steps are to be followed -

• Check if QFX5100 is running a 5 series version or 5e version with the command: >show version | match "fpc|host"

• 5 series version output:

fpc1:

--------------------------------------------------------------------------

Hostname: QFX5100

JUNOS Host Software [21.4R3-S8.4]

5e version output:

Hostname: QFX5100

JUNOS Host Software [3.14.52-rt50-WR7.0.0.9_ovp:3.1.0]

JUNOS Host qfx-5e host-control package [22.1R1.10]

JUNOS Host qfx-5e host-platform package [22.1R1.10]

JUNOS Host qfx-5e control-plane package [22.1R1.10]

JUNOS Host qfx-5e platform package [22.1R1.10]

JUNOS Host qfx-5e base package [22.1R1.10]

JUNOS Host qfx-5e data-plane package [22.1R1.10]

https://supportportal.juniper.net/s/article/QFX5100-QFX5110-Requirements-for-Creating-the-mixed-QFX5110-QFX5100-Virtual-Chassis-VC-Upgrading-the-QFX5100-with-the-qfx-5e-Image

• Download the required Junos software package: https://support.juniper.net/support/downloads/

• Prior to the upgrade, please record the outputs of the pre-check commands which can be found at: https://supportportal.juniper.net/s/article/EX-QFX-Command-List-for-Pre-Post-Upgrades-or-for-General-Health-Checks

• Back up the current software configuration to a secondary storage option. Alternately, run the command and copy the outputs onto a Word document or notepad file -> show configuration | display set | no-more

• Copy the software package to the master member's /var/tmp directory using a software like Filezilla or WinSCP.

• Push the Junos image onto all the members using the following command. This will copy the file from the master to each of the stack members -> request system software add /var/tmp/<file-name> no-validate

• In order to push the image onto a particular member, the command to be used -> request system software add /var/tmp/<file-name> member <member-id> no-validate

• Once the file is pushed onto all the members, reboot the entire stack at once using the command -> request system reboot all-members

• After the reboot has completed, log in and verify that the new version of the software is properly installed -> show version

• Confirm the status of the stack -> show virtual-chassis status

• The post-checks of the stack can be done by running the commands and comparing the outputs with the pre-check outputs.

Note: Please make sure to reboot the entire stack at the same time after the Junos file is pushed onto all the members. If the members are rebooted individually, there will be a Junos version difference between the members which will cause the VC to break.