Guides you through troubleshooting legacy BUNDLE-mode upgrade issues, including recovering stack members that are unable to boot the bundle image and performing supported conversions from BUNDLE mode to INSTALL mode.
Use this procedure to troubleshoot legacy bundle-mode upgrade issues, including recovering stack members that are unable to boot the bundle image and to perform supported conversions from bundle mode to install mode.
Use the exact procedure for source release because older releases can require a different syntax. Do not mix deprecated request platform software package commands with the current install workflow unless the exact source release requires them.
Cisco recommends install mode. Use bundle mode only when the exact Cisco Catalyst 9000 platform and release support it.
Procedure
-
Recover a stack member that cannot boot the bundle image.
- Identify the mismatched stack member.
Example:
switch# show switch
Switch# Role State
-------------------------
*1 Active Ready
2 Member V-Mismatch
The V-Mismatch state means the member is running incompatible software or did not boot the intended image.
- Verify that the bundle image exists on the active member.
Example:
switch# dir flash:<IMAGE.bin>
<IMAGE.bin>
- Verify whether the image is missing from the affected member.
Example:
switch# dir flash-2:<IMAGE.bin>
%Error opening flash-2:<IMAGE.bin> (No such file or directory)
In bundle mode the complete .bin must be available to every stack member through its configured boot path.
- Copy the bundle image to the affected member.
Example:
switch# copy flash:<IMAGE.bin> flash-2:
Destination filename [<IMAGE.bin>]?
Copy in progress...!!!!!!!!!!!!!!!!!!
[OK - <BYTES> bytes]
- Verify the copied image hash on the affected member.
Example:
switch# verify /sha512 flash-2:<IMAGE.bin>
verify /sha512 (flash-2:<IMAGE.bin>) = <MATCHING_SHA512>
The affected member now has the complete hash-verified bundle image. Confirm that the saved boot statement uses the exact image on all members before the approved reload.
Guidance
Copy and verify the exact same image on the affected member before the next approved reload. Also confirm the boot variable on every member. Do not format member flash as the first recovery action.
-
Convert from bundle to install mode. If the platform supports conversion and the target image is verified, use the supported one-step install workflow.
- Confirm current BUNDLE mode.
Example:
switch# show version | begin Switch Ports
Switch Ports Model SW Version SW Image Mode
------ ----- ------------ ----------- -------------- -------
* 1 48 C9300-48P <RELEASE> CAT9K_IOSXE BUNDLE
- Configure the next boot target for INSTALL mode.
Example:
switch# configure terminal
switch(config)# no boot system
switch(config)# boot system flash:packages.conf
switch(config)# no boot manual
switch(config)# end
- Save the boot configuration.
Example:
switch# write memory
Building configuration...
[OK]
- Verify the next boot target.
Example:
switch# show boot
Boot Variables on next reload:
BOOT variable = flash:packages.conf;
Manual Boot = no
Confirm the persistent next-reload target before running the installation. A stack can require the platform-specific switch-all boot syntax.
- Run the supported conversion workflow for install operation.
Example:
switch# install add file flash:<IMAGE.bin> activate commit
...
Add: Passed on [1]
Activate: Passed on [1]
Commit: Passed on [1]
SUCCESS: install_add_activate_commit
The conversion is disruptive. Do not reload manually if the install command fails before packages.conf file is created.
After the automatic reload, verify the install mode, the packages.conf file , and committed state.