Cisco Catalyst 9300 switches can run IOS-XE in two modes: INSTALL mode (recommended) and BUNDLE mode. In BUNDLE mode, the switch boots directly from a monolithic .bin file without extracting packages.
BUNDLE mode is similar to traditional IOS upgrade procedures and is simpler but offers less flexibility compared to INSTALL mode. It's typically used for:
This article provides a complete BUNDLE mode upgrade procedure including configuration backup, flash cleanup, image transfer, MD5 validation, boot configuration, upgrade execution, post-upgrade verification, and rollback procedures.
Important Note: Cisco recommends INSTALL mode for production environments due to better rollback capabilities, modular architecture, and easier troubleshooting. Consider converting to INSTALL mode after reviewing your requirements.
Understanding the differences helps you choose the right mode:
show version
Look at the "System image file" line in the output:
flash:cat9k_iosxe.16.12.10.binflash:packages.confshow boot
This displays the boot variable configuration. In BUNDLE mode, you'll see the .bin file path directly.
Example output for BUNDLE mode:
BOOT variable = flash:cat9k_iosxe.16.12.10.bin
If your switch is currently in INSTALL mode and you want to convert to BUNDLE mode, follow these steps:
install remove inactive
First, clean up old packages to free space.
conf t no boot system boot system flash:cat9k_iosxe.16.12.10.bin end write memory reload
Note: The .bin file must already exist in flash. After reload, the switch will boot in BUNDLE mode directly from the .bin file.
Warning: Converting from INSTALL to BUNDLE mode will remove the advanced rollback capabilities. Ensure you have a backup plan.
copy running-config startup-config copy startup-config tftp:
Important: Also backup the startup-config to an external location (TFTP/FTP/USB/SCP) before proceeding with the upgrade. Store the backup with the current IOS version information for easy reference.
Recommended operational verification and documentation commands:
show run show version show ip interface brief show interface status show vlan brief show spanning-tree summary show etherchannel summary show cdp neighbors show ip route summary show mac address-table count
Document current switch behavior, interface status, routing information, and feature status. This baseline will help verify functionality after the upgrade and assist with troubleshooting if issues arise.
Tip: Take screenshots or save the output to text files with timestamps.
Clearly identify the versions involved in your upgrade:
Current Image: cat9k_iosxe.16.12.10.bin Target Image: cat9k_iosxe.17.09.04.bin
Always choose a Cisco-recommended or Gold Star release for production environments. Verify compatibility with your hardware platform and current feature set on Cisco's website or using the Software Advisor tool.
Important Considerations:
dir flash:
Look for available bytes in the output. Catalyst 9300 IOS-XE .bin files are typically 600MB-1GB in size. You need at least 1.5-2 GB of free space to safely store both old and new images during the upgrade process.
show file systems
This command displays all available storage filesystems and their current usage statistics.
Example output interpretation:
Size(b) Free(b) Type Flags Prefixes 11353194496 8245678080 flash rw flash:
In this example, you have approximately 8.2GB free, which is sufficient for the upgrade.
In BUNDLE mode, there are no "install" commands. You must manually delete unwanted files to free up space.
dir flash:
Look for files that can be safely removed:
delete /force flash:old_image.bin delete /force flash:core*.gz delete /force /recursive flash:crashinfo delete /force /recursive flash:.installer delete /force /recursive flash:.prst
Critical Warning - Do NOT Delete:
dir flash:
Confirm you now have sufficient free space for the new image.
TFTP is simple but slower and less secure. Ensure the TFTP server is reachable from the switch management interface.
Example TFTP Server IP: 192.168.1.10
copy tftp: flash:
When prompted, enter the following information:
Address or name of remote host []? 192.168.1.10 Source filename []? cat9k_iosxe.17.09.04.bin Destination filename [cat9k_iosxe.17.09.04.bin]? <press Enter>
The transfer may take 10-30 minutes depending on network speed and file size (typically 600MB-1GB). Monitor the progress carefully and do not interrupt the transfer or power cycle the switch.
SCP provides faster transfer speeds and encryption. First, ensure SCP server is configured:
conf t ip scp server enable aaa new-model aaa authentication login default local aaa authorization exec default local end
Then copy the file:
copy scp://username@192.168.1.10/cat9k_iosxe.17.09.04.bin flash:
You'll be prompted for the password.
copy ftp://username:password@192.168.1.10/cat9k_iosxe.17.09.04.bin flash:
Security Note: FTP sends credentials in clear text. Use SCP when possible.
copy http://192.168.1.10/images/cat9k_iosxe.17.09.04.bin flash:
or for secure transfer:
copy https://192.168.1.10/images/cat9k_iosxe.17.09.04.bin flash:
USB Requirements:
First, verify the USB drive is detected:
dir usbflash0:
Then copy the file:
copy usbflash0:cat9k_iosxe.17.09.04.bin flash:
Note: USB transfer is significantly slower than network transfer but useful when network access is limited or unavailable.
Monitor the transfer: Watch for any error messages. The switch will display progress in hash marks (#) or percentage completion.
This is a CRITICAL step. A corrupted image file can cause boot failures and potentially brick your switch. Never skip MD5 verification.
Download the MD5 checksum from Cisco Software Portal alongside the image file. The checksum is usually displayed on the download page or available in a separate checksum file.
Example MD5 value from Cisco Software Portal:
9f3a6c9c6b2e1f0c3a5d4e7b8a1c2d3e
Run the verification command:
verify /md5 flash:cat9k_iosxe.17.09.04.bin 9f3a6c9c6b2e1f0c3a5d4e7b8a1c2d3e
Expected Output if Successful:
Verified (flash:cat9k_iosxe.17.09.04.bin) = 9f3a6c9c6b2e1f0c3a5d4e7b8a1c2d3e
If the MD5 hash matches, you'll see "Verified" - proceed with upgrade.
If it doesn't match, you'll see an error - DELETE the file immediately and re-transfer it.
If you don't have the MD5 hash readily available, you can compute it:
verify /md5 flash:cat9k_iosxe.17.09.04.bin
This will calculate the MD5 hash (takes 5-10 minutes for large files). Then compare this value manually with the one published on Cisco's website.
verify /sha512 flash:cat9k_iosxe.17.09.04.bin
SHA512 is more secure than MD5. Check if Cisco provides SHA512 checksums for your image version.
What if verification fails?
delete /force flash:cat9k_iosxe.17.09.04.binIn BUNDLE mode, you must manually configure the boot variable to point to the new .bin file. This tells the switch which image to load on the next reload.
show boot
This shows the current BOOT variable. You'll see something like:
BOOT variable = flash:cat9k_iosxe.16.12.10.bin
Important: For safety, configure BOTH old and new images. This creates a fallback if the new image fails to boot.
conf t boot system flash:cat9k_iosxe.17.09.04.bin boot system flash:cat9k_iosxe.16.12.10.bin end
The switch will attempt to boot from the first entry. If it fails, it will try the second entry automatically. This provides basic redundancy.
write memory
or
copy running-config startup-config
Critical: Do NOT skip this step. If you don't save, the boot configuration changes will be lost and the switch will boot the old image.
show boot
Confirm the output shows the new image first in the boot order:
BOOT variable = flash:cat9k_iosxe.17.09.04.bin,flash:cat9k_iosxe.16.12.10.bin
When upgrading a switch stack, ensure ALL members have the new image and boot configuration. The boot configuration is synchronized across stack members, but verify each member has the image file:
dir flash: show switch
If stack members have separate flash storage, you may need to copy the image to each member's flash.
In BUNDLE mode, there is no special upgrade command. You simply reload the switch and it will boot from the new image based on the boot variable configuration.
reload
You'll be prompted to confirm:
System configuration has been modified. Save? [yes/no]: yes Proceed with reload? [confirm]
Press Enter to confirm. The switch will save the configuration and begin the reload process.
To reload all stack members simultaneously:
reload
This reloads the entire stack. All members will reboot together.
Alternative - Reload Individual Stack Members:
reload slot 2
This allows staged upgrades with minimal downtime, but requires more time and careful planning.
Connect via console and monitor the boot process. The switch will:
Boot Time: Typically 5-10 minutes for Catalyst 9300 switches. BUNDLE mode boots faster than INSTALL mode since it doesn't extract packages.
What to Watch For:
After the switch completes its reload, perform comprehensive verification to ensure the upgrade was successful and all services are functioning correctly.
show version
Check the following in the output:
show boot
Confirm the new image is listed in the boot variable. The output should show:
BOOT variable = flash:cat9k_iosxe.17.09.04.bin,flash:cat9k_iosxe.16.12.10.bin
show run | include boot show start | include boot
Verify boot configuration is consistent between running and startup configs.
show switch show module show inventory show environment all
Verify:
show interface status show ip interface brief show interface description show interface trunk
Compare with your pre-upgrade baseline. Verify:
show vlan brief show spanning-tree summary show etherchannel summary show mac address-table count show cdp neighbors show lldp neighbors
Verify:
show ip route show ip route summary show ip ospf neighbor show ip eigrp neighbors show ip bgp summary show ip protocols
Verify:
show processes cpu sorted show processes memory sorted show memory statistics show platform software status control-processor brief
Verify:
show logging show logging | include Error show logging | include Fail
Review logs carefully for:
Depending on your switch configuration, verify specific features:
show ip dhcp snooping show ip arp inspection show authentication sessions show access-lists show ip nat translations show crypto session show power inline show stack-power
Test basic connectivity:
ping <gateway-ip> ping <management-server-ip> ping <adjacent-switch-ip> traceroute <remote-destination>
Establish a new baseline for comparison:
show interfaces counters show interfaces counters errors show platform hardware fed switch active qos queue stats internal cpu policer
Recommendation: Monitor the switch for at least 24-48 hours after upgrade before considering it fully stable. Watch for memory leaks, unexpected behavior, or intermittent issues.
If issues arise after the upgrade, BUNDLE mode rollback is straightforward but requires the old image file to still be present in flash. Unlike INSTALL mode, there are no automated rollback commands - you must manually reconfigure the boot variable and reload.
This is the cleanest method if you followed the best practice of configuring multiple boot entries.
Step 1: Verify the old image exists
dir flash: | include cat9k_iosxe.16.12.10.bin
Step 2: Check current boot configuration
show boot
Step 3: Reconfigure boot order to prioritize old image
conf t no boot system boot system flash:cat9k_iosxe.16.12.10.bin boot system flash:cat9k_iosxe.17.09.04.bin end
This places the old (working) image first in boot order, making it the primary boot image.
Step 4: Save configuration
write memory
Step 5: Verify new boot order
show boot
Should show:
BOOT variable = flash:cat9k_iosxe.16.12.10.bin,flash:cat9k_iosxe.17.09.04.bin
Step 6: Reload the switch
reload
The switch will boot from the old (working) image.
If the boot configuration was somehow lost or corrupted:
conf t boot system flash:cat9k_iosxe.16.12.10.bin end write memory reload
If the switch fails to boot normally, you can boot from ROMMON mode:
Step 1: During boot, press and hold BREAK or CTRL+C to enter ROMMON mode
Step 2: Set boot variable in ROMMON
switch: boot flash:cat9k_iosxe.16.12.10.bin
The switch will boot directly from the specified image.
Step 3: After successful boot, fix the boot configuration
conf t boot system flash:cat9k_iosxe.16.12.10.bin end write memory
For switch stacks, ensure all members have the old image:
show switch dir flash:
Then follow Method 1, configuring the boot variable and reloading. All stack members will synchronize and boot the old image.
conf t no boot system boot system flash:cat9k_iosxe.16.12.10.bin end write memory reload
If you deleted the old .bin file and need to rollback:
copy tftp://192.168.1.10/cat9k_iosxe.16.12.10.bin flash: verify /md5 flash:cat9k_iosxe.16.12.10.bin conf t boot system flash:cat9k_iosxe.16.12.10.bin end write memory reload
If configuration changes were made that need to be reverted:
copy tftp://192.168.1.10/backup-config-16.12.10.cfg running-config
or
configure replace flash:backup-config.cfg
Warning: "configure replace" will reload the entire configuration. Use with caution.
After performing a rollback, verify the system is stable and running the correct version:
show version show boot show switch show interface status show ip interface brief show logging show processes cpu show memory statistics
Document the reason for rollback, any errors encountered, and lessons learned. This information is valuable for planning the next upgrade attempt.
Root Cause Analysis:
Once you've confirmed the upgrade is stable and you're confident in the new version (typically after 24-48 hours of monitoring in production), you can clean up old files to free flash space.
Consider carefully before deleting: Keeping the old image provides a quick rollback option if issues arise later.
dir flash: delete /force flash:cat9k_iosxe.16.12.10.bin
Best Practice: Keep the old .bin file backed up externally for at least 30-90 days before permanently deleting from flash.
If you delete the old image, update the boot variable to remove the reference:
conf t no boot system boot system flash:cat9k_iosxe.17.09.04.bin end write memory
delete /force flash:core*.gz delete /force /recursive flash:crashinfo dir flash:
show boot dir flash:
Confirm only necessary files remain and boot configuration is correct.
After experiencing BUNDLE mode, you may want to convert to INSTALL mode for better rollback capabilities and modular architecture. Here's how:
The .bin file you currently have can be extracted and converted to INSTALL mode:
request platform software package install switch all file flash:cat9k_iosxe.17.09.04.bin auto-copy
or use the standard install command:
install add file flash:cat9k_iosxe.17.09.04.bin activate commit
This will extract the packages, activate them, and configure packages.conf as the boot source. After reload, the switch will be in INSTALL mode.
show version show boot
After reload, the system image file should show "flash:packages.conf" instead of the .bin file, confirming INSTALL mode.
Cause: Boot configuration not saved or overridden by startup-config
Solution:
show boot show start | include boot
Verify boot config is saved in startup-config. Re-configure and save:
conf t no boot system boot system flash:cat9k_iosxe.17.09.04.bin end write memory reload
Cause: Not enough free space for image transfer
Solution:
dir flash: delete /force flash:old_files delete /force /recursive flash:unnecessary_directories squeeze flash:
The "squeeze" command permanently removes deleted files and reclaims space.
Cause: Corrupted image or insufficient memory
Solution:
Cause: Corrupted file during transfer
Solution:
delete /force flash:cat9k_iosxe.17.09.04.bin
Re-download from Cisco and re-transfer. Try different transfer method (SCP instead of TFTP).
Cause: Individual member didn't reload or image wasn't copied
Solution:
show switch show version
Identify member with wrong version and reload individually:
reload slot <member-number>
Cause: Corrupted image or incompatible hardware/software
Solution:
switch: boot flash:cat9k_iosxe.16.12.10.bin
Cause: Configuration incompatibility or deprecated features
Solution:
show logging | include Error show logging | include Fail
Cause: Software bug or process issue in new version
Solution:
show processes cpu sorted show processes memory sorted show platform software status control-processor brief
Identify problematic process and search Cisco bug toolkit. May require rollback or patch to different version.
Cause: Management interface issue or SSH/Telnet configuration problem
Solution:
show ip interface brief show interface status
Cisco recommends INSTALL mode for all production Catalyst 9000 series switches. BUNDLE mode is maintained for backward compatibility and specific use cases but is not the preferred deployment method.
| Feature | BUNDLE Mode | INSTALL Mode |
|---|---|---|
| Upgrade Command | Manual boot config + reload | install add activate commit |
| Rollback Method | Manual boot config change | install rollback to committed |
| Boot Time | 5-7 minutes (faster) | 7-10 minutes (slower) |
| Flash Space Required | 1.5-2 GB | 3-4 GB |
| Complexity | Lower | Higher |
| Production Use | Not recommended | Recommended |
| Package Management | None | Full modular support |
Upgrading a Cisco Catalyst 9300 switch in BUNDLE mode is straightforward and similar to traditional IOS upgrade procedures. The process involves transferring the new .bin file, verifying its integrity, configuring the boot variable, and reloading the switch.
While BUNDLE mode is simpler and requires less flash space, it lacks the advanced rollback capabilities and modular architecture of INSTALL mode. For production environments, Cisco strongly recommends using INSTALL mode for better manageability, easier troubleshooting, and more robust rollback options.
Key Takeaways:
Remember: Proper preparation, thorough verification, and having a tested rollback plan are essential for successful IOS-XE upgrades regardless of the mode used. Always follow Cisco best practices and review release notes before upgrading production switches.
For production environments with critical uptime requirements, strongly consider using INSTALL mode instead of BUNDLE mode for the additional safety and rollback capabilities it provides.