How to Convert Cisco Switch From Install Mode to Bundle Mode

Last updated: 08-04-2026

Introduction

While install mode is Cisco's recommended approach for IOS-XE switches, there are valid scenarios where you may need to revert to bundle mode — for example, when downgrading to an older IOS version that does not support install mode, recovering a switch using a legacy image, or troubleshooting install mode corruption. This guide covers the correct procedure to safely convert Cisco switches from install mode back to bundle mode, with instructions applicable to the Catalyst 9200, 9300, 9400, 9500, 3750, and 3560 series.

Supported Platforms

The procedure described in this guide applies to the following Cisco switch families, with platform-specific notes where applicable:

  • Cisco Catalyst 9200 / 9200L Series — Full install mode support; procedure identical
  • Cisco Catalyst 9300 / 9300L Series — Full install mode support; procedure identical
  • Cisco Catalyst 9400 Series — Modular chassis; same procedure applies per supervisor
  • Cisco Catalyst 9500 / 9500H Series — Full install mode support; procedure identical
  • Cisco Catalyst 3750 / 3750X / 3750G Series — IOS (not IOS-XE); uses a simplified bundle-only boot method described separately below
  • Cisco Catalyst 3560 / 3560X / 3560G Series — IOS (not IOS-XE); uses the same simplified method as 3750

Note: The Catalyst 9000 series runs IOS-XE and uses the install command framework. The 3750 and 3560 series run classic IOS and do not use the install framework — their conversion process is simpler and is covered in the dedicated section at the bottom of this guide.

When Should You Convert Back to Bundle Mode?

Converting back to bundle mode is generally not recommended for production environments, but may be necessary in these situations:

  • Downgrade to Legacy IOS-XE: Older IOS-XE versions (prior to 16.5.x) may only support bundle mode
  • Install Mode Corruption: If packages.conf is corrupted and cannot be rebuilt
  • RMA / Hardware Replacement: Restoring a replacement unit using an older image
  • Lab and Testing: Specific test scenarios requiring bundle mode behavior
  • TAC-Directed Recovery: When Cisco TAC instructs a revert during troubleshooting

Prerequisites and Preparation

System Requirements

Before starting, ensure the following are in place:

  • Bundle Mode Image: A valid IOS-XE .bin monolithic bundle file compatible with your switch model
  • Sufficient Flash Space: Minimum 1–2 GB free (bundle images are large monolithic files)
  • Console Access: Direct console connection strongly recommended
  • TFTP Server or USB: To transfer the bundle image if not already on flash
  • Maintenance Window: The switch will reload during conversion

Pre-Conversion Assessment

1. Confirm the switch is currently running in install mode:

show version | include mode
show install summary
show boot

You should see output indicating Install mode and packages.conf as the boot variable.

2. Document the current system state:

show version
show install summary
dir flash:

3. Back up the current running configuration:

copy running-config startup-config
copy startup-config tftp://192.168.10.10/switch-backup-before-revert.txt

4. Check available flash storage:

show flash: | include bytes

Step-by-Step Conversion Process (Catalyst 9000 Series — IOS-XE)

Step 1: Transfer the Bundle Image to Flash

If the monolithic bundle .bin file is not already on flash, copy it from your TFTP server or USB drive.

Via TFTP:

copy tftp://192.168.10.10/cat9k_iosxe.17.06.05.SPA.bin flash:

Via USB:

copy usbflash0:cat9k_iosxe.17.06.05.SPA.bin flash:

Replace the filename with the appropriate bundle image for your platform and target version.

Step 2: Verify Image Integrity

Confirm the file is present in flash and verify its MD5 checksum against the value from Cisco's software download page.

dir flash: | include cat9k_iosxe.17.06.05.SPA.bin
verify /md5 flash:cat9k_iosxe.17.06.05.SPA.bin <expected-md5-hash>

Step 3: Remove the Install Mode Boot Variable

Enter global configuration mode and remove the existing packages.conf boot entry.

configure terminal
no boot system flash:packages.conf

If there are multiple boot system entries, remove each one individually:

show running-config | include boot system
no boot system flash:packages.conf
no boot system flash:<any-other-entry>

Step 4: Set the Bundle Image as the Boot Variable

Configure the switch to boot directly from the monolithic .bin bundle file.

boot system flash:cat9k_iosxe.17.06.05.SPA.bin
exit

Step 5: Save the Configuration

Save the running configuration so the new boot variable persists after reload.

copy running-config startup-config

Verify the boot variable is correctly set:

show boot

Confirm the output shows your .bin file as the boot system — not packages.conf.

Step 6: Clean Up Install Mode Packages (Optional but Recommended)

Before reloading, remove the installed packages to free up flash space. This step is optional but prevents confusion from leftover install mode files.

Remove all inactive packages:

install remove inactive

To remove all install mode packages (active and inactive) — only do this after confirming your bundle image is on flash and boot variable is correctly set:

install remove all

Warning: Do not run install remove all if your switch is still configured to boot from packages.conf, as this will leave the switch with no bootable image.

Step 7: Reload the Switch

Reload the switch to boot into bundle mode.

reload

When prompted to save configuration, enter no (you already saved in Step 5).

Step 8: Verify Bundle Mode After Reload

After the switch comes back online, confirm it is running in bundle mode.

Check boot mode:

show version | include mode

Verify boot variables:

show boot

Confirm no install packages are active:

show install summary

Success Indicators:

  • Boot mode shows Bundle
  • show boot shows the .bin file (not packages.conf)
  • show install summary shows no active packages or is empty
  • Switch is running the expected IOS-XE version

Conversion Process for Catalyst 3750 and 3560 Series (Classic IOS)

The Catalyst 3750 and 3560 series run classic IOS — not IOS-XE — and do not use the install mode framework at all. These switches always boot from a single monolithic .bin image. There are no packages, no packages.conf, and no install commands.

If your 3750 or 3560 is booting from an incorrect or corrupted image, or you need to change the active IOS image, follow these steps.

Step 1: Transfer the Target IOS Image to Flash

copy tftp://192.168.10.10/c3750e-universalk9-mz.152-4.E10.bin flash:

Step 2: Verify the Image

dir flash: | include .bin
verify /md5 flash:c3750e-universalk9-mz.152-4.E10.bin <expected-md5-hash>

Step 3: Update the Boot System Variable

configure terminal
no boot system flash:<old-image.bin>
boot system flash:c3750e-universalk9-mz.152-4.E10.bin
exit

Step 4: Save and Reload

copy running-config startup-config
show boot
reload

Step 5: Verify After Reload

show version
show boot

On 3750/3560 switches, show version will confirm the currently running IOS image filename. There is no mode indicator, as these switches only support bundle-style (single binary) boot.

Note for Stacked 3750 Systems: In a stack, all member switches must have the same IOS image in flash. Verify all stack members before reloading:

show switch detail
dir flash: (on each stack member via session)

Post-Conversion Verification

System Health Check

1. Verify system version and boot mode:

show version
show boot

2. Check network connectivity and interface status:

ping <gateway-ip>
show ip interface brief

3. Verify Layer 2 features and VLANs:

show interface status
show vlan brief
show spanning-tree summary

Performance Monitoring

Review CPU, memory, and system logs after the revert:

show processes cpu | include five
show memory statistics
show logging | include ERROR|WARN

Cleanup After Conversion

Remove Leftover Install Mode Files

After confirming stable operation in bundle mode, clean up residual install mode files to reclaim flash space.

List all files in flash:

dir flash:

Delete individual package files (they typically have a .pkg extension):

delete flash:<package-file.pkg>

Delete the packages.conf file if it still exists:

delete flash:packages.conf

Delete any stale .conf or .tmp install artifacts:

delete flash:*.conf
delete flash:*.tmp

Verify reclaimed space:

show flash: | include bytes

Caution: Do not delete the startup-config or any image you intend to keep as a backup.

Troubleshooting Common Issues

Switch Boots into Install Mode After Reload

This usually means the boot variable was not saved, or packages.conf still exists and is taking precedence. Verify:

show boot
show running-config | include boot system

If packages.conf is still listed, reenter configuration mode and correct it:

configure terminal
no boot system flash:packages.conf
boot system flash:<your-bundle.bin>
exit
copy running-config startup-config
reload

Boot Loop or Failed to Load Image

If the switch cannot find or load the bundle image, access ROMMON and boot manually:

SWITCH_NUMBER=1
BOOT=flash:cat9k_iosxe.17.06.05.SPA.bin
boot

Once the switch boots, reconfigure the boot variable and save.

Insufficient Flash Space for Bundle Image

Bundle images are large. Free space by removing install packages and unnecessary files before copying:

install remove inactive
delete flash:*.log
delete flash:*.tmp
show flash: | include bytes

MD5 Mismatch on Image Verification

Do not proceed if the MD5 checksum does not match. Re-download the image from Cisco's software portal and retransfer it:

delete flash:<corrupt-image.bin>
copy tftp://192.168.10.10/<image.bin> flash:

Rollback Procedures (Emergency)

Method 1: ROMMON Recovery (Applicable to All Platforms)

If the switch fails to boot after the conversion attempt, use ROMMON to boot directly from a known-good image.

SWITCH_NUMBER=1
BOOT=flash:<known-good-bundle.bin>
boot

After booting, reconfigure and save the boot variable permanently:

configure terminal
no boot system flash:packages.conf
boot system flash:<known-good-bundle.bin>
exit
copy running-config startup-config

Method 2: Revert to Install Mode (If Bundle Mode Fails)

If bundle mode causes issues and you want to return to install mode, copy a compatible image and re-run the install process:

configure terminal
no boot system flash:<bundle.bin>
boot system flash:packages.conf
exit
copy running-config startup-config
install add file flash:<image.bin> activate commit

Considerations and Limitations of Bundle Mode

While bundle mode works reliably, be aware of its limitations compared to install mode:

  • Slower Boot Times: The entire monolithic image is loaded into memory on each boot
  • Higher Flash Consumption: Full .bin files are significantly larger than extracted packages
  • No Granular Rollback: You cannot roll back to individual package states
  • Full Image Upgrades Required: Every upgrade requires transferring and booting a complete new image
  • Feature Limitations: Some advanced IOS-XE features introduced in later releases may require install mode

For these reasons, Cisco recommends reverting to bundle mode only when necessary and planning a return to install mode once the underlying issue is resolved.

Best Practices and Recommendations

Planning Guidelines

  • Always perform this procedure during a scheduled maintenance window
  • Maintain console access throughout — do not rely solely on SSH
  • Keep at least one backup image on flash before deleting anything
  • Verify MD5 checksums before and after every image transfer
  • Test in a lab environment before applying to production switches
  • Document the reason for reverting and plan a path back to install mode

Post-Conversion Maintenance

  • Monitor the switch for 24–48 hours after conversion
  • Validate all critical services: routing, VLAN, spanning tree, LACP
  • Update network documentation to reflect the current boot mode
  • Open a Cisco TAC case if the revert was performed due to a platform defect

Quick Reference: Command Summary by Platform

Catalyst 9000 Series (IOS-XE) — Install to Bundle

# 1. Copy bundle image
copy tftp://<server>/<image.bin> flash:

# 2. Remove install mode boot variable
configure terminal
no boot system flash:packages.conf

# 3. Set bundle boot variable
boot system flash:<image.bin>
exit

# 4. Save and reload
copy running-config startup-config
reload

# 5. Verify
show version | include mode
show boot

Catalyst 3750 / 3560 Series (Classic IOS) — Change Boot Image

# 1. Copy new IOS image
copy tftp://<server>/<image.bin> flash:

# 2. Update boot variable
configure terminal
no boot system flash:<old-image.bin>
boot system flash:<new-image.bin>
exit

# 3. Save and reload
copy running-config startup-config
reload

# 4. Verify
show version
show boot

Conclusion

Converting a Cisco switch from install mode back to bundle mode is a straightforward process when followed in the correct sequence: transfer and verify the bundle image, remove the install mode boot variable, set the new bundle boot variable, save configuration, and reload. The same logical process applies across the Catalyst 9200, 9300, 9400, and 9500 series running IOS-XE.

For the Catalyst 3750 and 3560 series running classic IOS, the concept is even simpler since these platforms have always used a single monolithic boot image — the process is simply a matter of updating the boot system variable to point to the desired image.

Remember that bundle mode is a legacy boot method for IOS-XE platforms, and a return to install mode should be planned once the need for bundle mode has passed. Proper planning, console access, and image verification are the keys to a smooth and safe conversion in either direction.