Configuring Automatic Software Update on Virtual Chassis Member Switches
The automatic software update feature allows you to automatically update the software version on prospective member switches as they are added so that they can join the Virtual Chassis.
The version of Junos OS running on the Virtual Chassis must be compatible with the software running on the prospective member switch for an automatic software update to occur. For information on Junos OS compatibility and other automatic software update restrictions, see Understanding Automatic Software Update on Virtual Chassis Member Switches.
Before you begin, ensure that you know the name or the URL of the software package to be used by the automatic software update feature.
To configure the automatic software update feature for an EX Series or QFX Series Virtual Chassis that is not a mixed-mode Virtual Chassis:
user@switch# set virtual-chassis auto-sw-update package-name package-name
An EX4300 Virtual Chassis with a combination of EX4300 multigigabit model switches (EX4300-48MP) and other EX4300 switches must be configured in mixed mode, and the automatic software update feature is not supported in this case.
A QFX5110 Virtual Chassis is considered to be a non-mixed Virtual Chassis. Because both QFX5110 and QFX5100 switches in a QFX5110 Virtual Chassis run the same software image, you can use the auto-sw-update command with one software package name for all members.
A QFX5100 switch running a Junos OS software image with “-qfx-5-” in the package filename must first be upgraded to a Junos OS software image with “-qfx-5e-” in the package filename before it can be added to a QFX5110 Virtual Chassis or VCF. The automatic software update process cannot update a switch from a “-qfx-5-” image to a “-qfx-5e-” image. See Upgrading a QFX5100 Switch with a USB Device to Join a QFX5110 Virtual Chassis or Virtual Chassis Fabric.
After a QFX5100 switch is installed with a “-qfx-5e-” Junos OS software image, the automatic software update process can successfully update the switch automatically with a different version of a “-qfx-5e-” Junos OS image to match the other members in the Virtual Chassis or VCF.
To configure the automatic software update feature on a mixed Virtual Chassis containing at least one EX4200 switch and at least one EX4500 or EX4550 switch, use the ex-4200 option when you are specifying a path to a package for the EX4200 switches and the ex-4500 option when you are specifying a path to a package for the EX4500 or EX4550 switches, as follows:
user@switch# set virtual-chassis auto-sw-update ex-4200 package-name package-name
user@switch# set virtual-chassis auto-sw-update ex-4500 package-name package-name
You do not need to specify the ex4500 option when configuring automatic software update for a Virtual Chassis with only a combination of EX4500 and EX4550 switches, which does not need to run in mixed mode. Specifying only a Junos OS package name for an EX4500 switch updates the software for both EX4500 and EX4550 switches.
To configure the automatic software update feature on a mixed QFX5100 Virtual Chassis composed of QFX5100 switches and at least one other supported type of device (QFX3500, QFX3600, or EX4300 switches), you must specify a software package name for each type or family of device in the mixed Virtual Chassis:
Specify the qfx-5 option with the path to the Junos OS package for QFX5100 switches
Specify the qfx-3 option with the path to the Junos OS package for QFX3600 and QFX3500 switches
Specify the ex4300 option with the path to the Junos OS package for EX4300 switches
user@device# set virtual-chassis auto-sw-update qfx-5 package-name package-name
user@device# set virtual-chassis auto-sw-update qfx-3 package-name package-name
user@device# set virtual-chassis auto-sw-update ex-4300 package-name package-name
You can similarly specify different package names using the ex-4600 and ex-4300 options with the auto-sw-update statement to configure the automatic software update feature for a mixed EX4600 Virtual Chassis that contains EX4600 and EX4300 member switches.
If the software package is located on a local directory on the switch, use the following format for package-name:
If the software package is to be downloaded and installed from a remote location, use one of the following formats: