Performing a rolling upgrade

Prerequisites

Ensure that you have a scheduled maintenance window. This procedure is NOT hitless, but it does aim to minimize the amount of traffic loss. It is advisable to have a support engineer from HPE available during this procedure.
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 MCLAG interface. If the setting has a different value, reset the value to TX disable by entering the loop-protect action tx-disable command:
```
switch# configure terminal
switch(config)# interface lag 2 multi-chassis
switch(config-if)# loop-protect action tx-disable
```
Back up the current software to the secondary image bank. Run the show version command. If the Active Image is primary, copy the primary image to the secondary image bank:
```
switch# copy primary secondary
```
If the Active Image is the secondary image, you do not need to run the copy primary secondary command because the current software is already in the secondary image bank.

Save a copy of the running configuration on both devices:

switch# copy running-config sftp://<username>@<IP>/filename vrf mgmt

Examine the files for your current configuration. Determine the appropriate VSX commands that will need to be run after the software on the device is upgraded. Many MCLAG commands have changed in this release. See MCLAG to VSX command equivalency for finding the equivalent VSX commands.
Check the status of the show mclag brief command and validate the ISL is in-sync and the keepalive is established. Also, verify which switch is the primary switch. This procedure requires you upgrade the primary switch first. If the secondary switch is upgraded first, the downstream MCLAG interfaces will be stuck in LACP-block until both switches are upgraded to this release and the VSX configurations are applied.
Check the output of the show lacp interfaces command and note which LACP interfaces are in a forwarding state of up.

Procedure

Ensure that you are in a maintenance window. There will be some amount of network disruption even with the upgrade of a single switch.
Copy the software from this release onto both switches by using TFTP, SFTP, or USB:
```
switch# copy sftp://<username>@<ip>/XL_10_02_0001.swi primary vrf mgmt
```
Remove the keepalive configurations from both switches so that they can both forward traffic during the upgrade process. The keepalive is restored later when the VSX configuration is applied.
1. Run the command show mclag brief for determining if the switch is the primary switch or the secondary switch.
2. Run the following command on the secondary switch for removing the keepalive configuration:
```
switch(config)# no mclag keepalive
```
If you have an MCLAG configuration that uses active gateway instead of VRRP, on the MCLAG primary switch shutdown any ROPs, SVIs, or layer 3 LAGs that provide an uplink to the rest of the network. These uplinks would typically be links that are connected through OSPF, BGP, or static routes. This shutdown helps to prevent traffic from being routed to this switch until it is properly configured with VSX.
On the MCLAG primary switch, boot the switch to the 10.02 software release:
```
switch# boot system primary
```
While the primary switch is being upgraded and converted to VSX, the secondary switch is still actively forwarding traffic with MCLAGs from version 10.00 of the software. When you are prompted, save the configuration.
Once the primary switch has been booted for this release, all MCLAG configurations are removed with the exception of the MCLAG interfaces. Each of the MCLAG interfaces is in an LACP-block state until VSX is configured and activated.
Ensure the Routed Only Port (ROP) is enabled on the primary switch. The ROP is required for configuring keepalive.

With the information you learned about your configuration in step 5 in prerequisites, configure VSX on the switch by entering the role primary command:

switch(config)# vsx 
switch(config-vsx)# role primary
switch(config-vsx)# inter-switch-link 1/1/1 
switch(config-vsx)# keepalive peer 10.0.0.1 source 10.0.0.2 
switch(config-vsx)# exit
switch(config)# interface vlan 10
switch(config-if-vlan)# active-gateway ip 10.1.1.1 mac 00:00:5E:00:53:FF

Save the configuration from the running configuration to the startup configuration by entering the write memory command.
Approximately 10 minutes after applying the VSX configuration, the VSX LAG interfaces will move from LACP-block to ACTIVE on the designated primary. Monitor the output of show lacp interfaces for determining when the interfaces are active.
Enable any ROPs, SVIs, or layer 3 LAGs that were previously disabled to the uplinks. The VSX configuration is applied, the upgrade is complete, and the primary switch is ready to forward network traffic.
On the designated secondary switch, boot the switch to the 10.02 software release:
```
switch# boot system primary
```
The MCLAG configurations on the secondary switch are removed with the exception of the MCLAG interfaces.
Ensure the Routed Only Port (ROP) is enabled on the secondary switch. The ROP is required for configuring keepalive.

With the information you learned about your configuration in step 5 in prerequisites, configure the VSX on the switch by entering the role secondary command:

switch(config)# vsx 
switch(config-vsx)# role secondary
switch(config-vsx)# inter-switch-link 1/1/1 
switch(config-vsx)# keepalive peer 10.0.0.2 source 10.0.0.1
switch(config-vsx)# exit
switch(config)# interface vlan 10
switch(config-if-vlan)# active-gateway ip 10.1.1.1 mac 00:00:5E:00:53:FF

Save the configuration from the running configuration to the startup configuration by entering the write memory command.
The MCLAG conversion to VSX is complete. Run the show vsx brief command on both switches.
Verify that the ISL state is In-Sync and the keepalive state is Keepalive-Established.
Check the output of the show lacp interfaces command. Validate that the VSX LAGs have a forwarding state of up.
Configure VSX-related features as needed. Consult this guide for additional information about VSX features, such as VSX configuration synchronization and active forwarding.
Save the running configuration to the startup configuration:
```
switch# write memory
Success
```