Example: Configuring Automatic Software Update on EX4200 Virtual Chassis Member Switches
The automatic software update feature automatically updates the Junos OS version on prospective member switches as they are added to a Virtual Chassis configuration of EX4200 switches so the new member switch immediately joins the EX4200 Virtual Chassis configuration and is put in the active state. If the software version on the new switch is not the same as the version running on the master, the master keeps the new switch in the inactive state. If you have not enabled the automatic software update feature, you will have to manually install the correct software version on each prospective member switch as it is added to the Virtual Chassis configuration.
This example describes how to configure the Virtual Chassis automatic software update feature:
This example uses the following hardware and software components:
Three EX4200 switches
Junos OS Release 10.0 or later for EX Series switches
Before you begin, be sure you have:
- Ensured that two member switches are running the same version of Junos OS for EX Series switches so that they can form the initial Virtual Chassis configuration.
- Cabled and powered on those two switches to create the Virtual Chassis configuration. See Connecting a Virtual Chassis Cable to an EX4200 Switch.
- Ensured that you know the name or the URL of the software package to be used by the automatic software update feature.
- If you are going to perform an automatic software update, ensure that the version of Junos OS running on the Virtual Chassis is compatible with the version of Junos OS running on the prospective member switch for automatic software update. See Understanding Automatic Software Update on Virtual Chassis Member Switches.
Overview and Topology
For a standalone EX4200 switch to join an existing Virtual Chassis configuration, it must be running the same version of Junos OS that is running on the Virtual Chassis master. If the software version on the new switch is not the same as the version running on the master, the master keeps the new switch in the inactive state.
The topology for this example consists of three EX Series switches. Two of the switches are connected in a Virtual Chassis configuration and are therefore running the same version of Junos OS for EX Series switches. The third switch is a standalone switch that is running a different software version than the Virtual Chassis member switches. In this example, we will enable the automatic software update feature on the Virtual Chassis configuration and then add the third switch to the configuration. The master will detect the presence of the new switch, check the software version running on the new switch, and, because it is not the same version currently running on the master, will update the software version on the new switch and reboot the switch so that it can join the Virtual Chassis configuration and immediately be put in the active state.
To configure automatic software update, perform this task:
To configure automatic software update:
- Enable automatic software update and configure the path
to the software package:
user@switch# set virtual-chassis auto-sw-update package-name /var/tmp/jinstall-ex-4200-10.0R1.1-domestic-signed.tgz
- Connect the new switch to the existing Virtual Chassis configuration, and power on the switch.
Check the results of the configuration:
To verify that the software version on the new switch has been updated and that the switch has joined the Virtual Chassis configuration, perform this task:
Verifying That the Software Version Is Updated
Verify that the new switch has joined the Virtual Chassis configuration.
If the software version on the new switch had not been updated successfully, the master would not allow the switch to join the Virtual Chassis configuration.
Issue the show virtual-chassis command.
user@switch> show virtual-chassis
Virtual Chassis ID: 0019.e250.47a0 Mastership Neighbor List Member ID Status Serial No Model priority Role ID Interface 0 (FPC 0) Prsnt AK0207360276 ex4200-24t 255 Master* 1 vcp-1 2 vcp-0 1 (FPC 1) Prsnt AK0207360281 ex4200-24t 255 Backup 2 vcp-1 0 vcp-0 2 (FPC 2) Prsnt AJ0207391130 ex4200-48p 128 Linecard 0 vcp-1 1 vcp-0
Because in the initial two-member Virtual Chassis configuration member 0 was the master and member 1 was the backup, the output shows that the new switch has been assigned member ID 2 and has been given the Linecard role. The Status field shows that member 2 is Prsnt, which means that it is in the active state.