Example system-mode maintenance usage for firmware upgrade.
In 7.0.0, this command system-mode maintenance was introduced.
The command enables maintenance mode for graceful traffic diversion from the switch by shutting down edge ports and increasing the cost of ISLs, to facilitate debugging or firmware upgrades.
Software Release: 7.0.0 Fixed in Version: 7.2.0
This is a known Defect. Upgrade to a version of code that contains the fix. Review Release Notes to see which versions have been fixed.
Below is a use case example of system-mode maintenance for firmware upgrade in a 2 switch cluster. ===== 1. Enable maintenance-mode on non-principal RB2 2. Perform shutdown on all ISLs between the two rbridges 3. Confirm all data traffic is forwarding only on RB1 4. Perform firmware coldboot upgrade on RB2 5. Confirm firmware upgrade is successful on RB2 6. Disable maintenance-mode on RB2 7. Enable maintenance-mode on RB1 8. Confirm all data traffic is forwarding only on RB2 9. Perform firmware coldboot upgrade on RB1 10. Confirm firmware upgrade is successful on RB1 11. Disable maintenance-mode on RB1 12. Perform no shutdown on all ISLs between the two rbridges 13. Confirm RB1 and RB2 rejoins VCS successfully with new firmware version and maintenance-mode disabled on both nodes. ===== Note: If the above procedure is not followed, attempt to disable maintenance mode (no system-mode maintenance) on the upgraded switch may fail with "Operation failed as cluster is in transient state" error.