Symptom

***Please note, this is expected behavior. The golden and primary images will not be able to sync variables. The golden image should be treated as a simple recovery image and not used as the bootable ROMMON version for normal switch operation. This defect is to document the issues that are possibly encountered by booting from golden ROMMON and the steps to take to recover the primary image.*** Switch boots using golden ROMMON If in stackwise virtual, the switch on golden capsule fails to join the stack due to improperly defined variables in golden ROMMON In addition to the SVL configuration being incorrect, the switch number is not recognized in the startup configuration file, so all interface configuration is seen as invalid input because the interface names do not match the stackwise virtual naming convention (gi1/1/0/1 vs gi1/0/1 for example). Another possible issue that can arise from booting golden ROMMON is the switch console will not be accessible if value other than the default 9600 BAUD rate is used. BAUD rate is not synced in the golden capsule and the default 9600 is needed to access the console. **This issue was found during a failed golden ROMMON upgrade after IOS upgrade to 17.3.3, but can impact devices in other scenarios when the primary ROMMON has failed and is booting on golden. Please note, the upgrade of the golden ROMMON capsule is not required and should not be performed unless a specific use case requires it. If the golden ROMMON capsule upgrade is required, there is a mandatory CPLD upgrade that should be performed. Please contact TAC for information about supported versions and how to perform this upgrade.***

Conditions

failed primary ROMMON image, resulting in booting on golden

Workaround

If booting into the golden capsule was caused by a failed upgrade of ROMMON, please perform the required CPLD upgrade to recover the primary ROMMON image. Please engage TAC support for assistance. A temporary workaround is to create a backup of the startup config file and correctly define the interface names to match expected stackwise virtual naming convention. Save this file to the flash of the switch reapply SVL configurations on the impacted switch and save the configuration Reload the switch to get it to rejoin the stack After SSO is reached, copy the backup config file to the running and startup config on stack However, this will only recover the switch for a single reload, if the device is reloaded and boots again off the golden ROMMON image, the same symptoms will be seen in the broken state.

Further Problem Description