Fallback

If an issue prevents any of the switches from being updated, all switches must be returned to their initial state.

The following fallback process includes high-level steps to accomplish this. In general, the same commands specified in this document to perform the switch updates can be used to return the switches to their original state.

1. If one of the switch updates fails, do not proceed to another switch. If XClarity Administrator reports an error when attempting to transfer the image files to the switch, refer to Appendix B: Updating ThinkAgile SXM Series switches using the CLI (Lenovo switches only) for instructions on using the switch CLI method to update switch firmware.

2. The original switch firmware is available in the “standby” image slot for all switches in the ThinkAgile SXM Series solution except the RackSwitch G8052 BMC switch. For this switch, the original firmware is available in the non-active image slot, which could be “image1” or “image2.” If a switch update fails, the switch can be reverted to the original firmware using the following command syntax:

   All switches except the G8052: boot image <standby | active

   RackSwitch G8052 BMC switch: boot image <image1 | image2

   Important

   Do not allow the TOR switches to run different versions of firmware except during the period in which TOR1 has been updated and the TOR2 update is pending. That is, if TOR1 fails to update properly, do not update TOR2. Also, if TOR2 fails to update properly, TOR1 must be reverted to the previous firmware until the update issue can be resolved.

3. The configuration file from each switch is backed up before updating the switches. These files are also saved to D:\Lenovo\SwitchConfigBackups on the HLH. Any switch can be restored to its backup configuration to restore the switch to its previous configuration.