Upgrading switches by using the vsx update-software command

Prerequisites

  1. Ensure that there is a scheduled maintenance window. There will be a minimal disruption of service until the upgrade is completed. It is advisable to have a support engineer from HPE available during this procedure.

  2. If you have enabled loop protect, enter the show loop-protect command for verifying that the action on loop detection has a value of TX disable on the VSX interface. If the setting has a different value, reset the value to TX disable by entering the loop-protect action tx-disable command: 
    switch(config)# interface lag 2 multi-chassis
switch(config-if)# loop-protect action tx-disable
switch(config-if)# exit
switch(config)# exit

  3. The vsx update-software command provides the option to save the configuration on the primary and secondary VSX switches; however, you can save the configuration manually by using one of the following methods:

    • To copy the running configuration into the startup configuration: 

      switch# copy running-config startup-config

      If the startup configuration is already present, the command overwrites the pre-existing startup configuration.

    • To copy the running configuration into a checkpoint that has not been created yet: 

      switch# copy running-config checkpoint <CHECKPOINT-NAME>

  4. Check the status of the show vsx brief command and validate the ISL is in-sync and the keepalive is established.

  5. Check the output of the show lacp interfaces multi-chassis command and note which LACP interfaces are in a forwarding state of up.

Procedure
  1. Enter the vsx update-software command. Prefix the path, for downloading the software, with tftp://, as shown in the following example: 
    switch# vsx update-software tftp://192.168.1.1/XL.10.03.0001 vrf mgmt
Do you want to save the current configuration (y/n)? y
The running configuration was saved to the startup configuration.

This command will download new software to the %s image of both the VSX primary and secondary systems, 
then reboot them in sequence. The VSX secondary will reboot first, followed by the primary.
Continue (y/n)? y
VSX Primary Software Update Status     : <VSX primary software update status>
VSX Secondary Software Update Status   : <VSX secondary software update status>
VSX ISL Status                         : <VSX ISL status>
Progress [..........................................................................................]
Secondary VSX system updated completely. Rebooting primary.

    This command gives you the option to save the running configuration on the primary and secondary VSX switches. After the command saves the running configuration, it downloads new software from the TFTP server and verifies the download. After a successful verification, the command installs the software to the alternative image of both the VSX primary and secondary switches.

    The command displays the status of the VSX primary and secondary switches during the upgrade. The command also refreshes the progress bar as the image update progresses. Do not interrupt the VSX primary CLI session until the software updates completes; however, software update process can be stopped. If you stop the upgrade when the secondary switch has already installed the image in its flash memory or the secondary switch has started the reboot the process, it comes up with the new software. The primary switch continues to have with older software. You can stop the software update process by pressing ctrl+c.

  2. Run the show vsx brief command on both switches. Verify that ISL is In-Sync by running the show vsx brief command on both switches. Verify in the output of the command that the ISL is In-Sync and the keepalive state is Keepalive-Established.
  3. Validate on both switches that the downstream LACP links are all forwarding correctly by entering the show lacp interfaces command.
  4. Save the running configuration to the startup configuration: 
    switch# write memory
Success