Cisco Catalyst 9200 Install Mode vs Bundle Mode Explained

On Catalyst 9200 switches, Install and Bundle modes have different boot dependencies. The mode determines which software files must stay in flash and how to approach upgrades and cleanup. Install mode boots from packages.conf and extracted .pkg files. Bundle mode boots a monolithic .bin image. Cisco recommends Install mode for Catalyst 9200 switches.

Install and Bundle mode comparison

Item	Install Mode	Bundle Mode
Primary boot reference	`flash:packages.conf`	`flash:<IOS-XE-IMAGE>.bin`
Required software files	`packages.conf` and the referenced `.pkg` files	The selected `.bin` image
Mode shown by `show version`	`INSTALL`	`BUNDLE`
Upgrade approach	IOS XE install workflow	Boot-variable change to another BIN image and reload
Cisco recommendation for C9200	Recommended	Supported, but not the recommended operating mode

How Install mode boots

Install mode expands the downloaded BIN into packages. The provisioning file, packages.conf, identifies the packages the release needs. A flash directory may contain:

packages.conf
<PLATFORM>-rpbase.<VERSION>.pkg
<PLATFORM>-rpboot.<VERSION>.pkg
<PLATFORM>-srdriver.<VERSION>.pkg
<PLATFORM>-webui.<VERSION>.pkg
...

Package names and contents vary by platform and release. Preserve packages.conf together with the packages it references; this mode does not boot the original BIN directly. Cisco describes Install mode as newer and recommended. It can boot faster and use memory more efficiently than Bundle mode.

How Bundle mode boots

Bundle mode points the boot variable to the BIN:

BOOT variable = flash:<IOS-XE-IMAGE>.bin

During boot, the switch extracts the bundle's packages and copies them to RAM. Cisco documents the additional memory use compared with Install mode. The selected BIN remains a boot dependency. Removing or renaming it without a valid alternative can prevent normal startup after a reload.

Checking the current mode and next boot path

Check both the running mode and the next boot path. show version identifies the current mode; show boot shows the configured boot variables.

show version
show boot
show install summary
dir flash:

Check show version

The switch member table near the end of show version has a Mode column. The first example shows Install mode:

Switch Ports Model        SW Version   SW Image         Mode
------ ----- ------------ ------------ ---------------- -------
*    1   ... C9200...     <VERSION>    CAT9K_LITE_IOSXE INSTALL

In Bundle mode:

Switch Ports Model        SW Version   SW Image         Mode
------ ----- ------------ ------------ ---------------- ------
*    1   ... C9200...     <VERSION>    CAT9K_LITE_IOSXE BUNDLE

Look for INSTALL or BUNDLE; spacing and other fields vary by model and release.

Check the system image file

The same output normally lists the running system image. For Install mode:

System image file is "flash:packages.conf"

For Bundle mode:

System image file is "flash:<IOS-XE-IMAGE>.bin"

Check show boot

An Install-mode boot variable typically shows:

BOOT variable = flash:packages.conf;

A Bundle-mode variable points to the selected BIN:

BOOT variable = flash:<IOS-XE-IMAGE>.bin;

When both are displayed, read the current and next-reload boot variables. The saved path can differ from the mode currently running.

Why a BIN in flash does not establish the mode

An Install-mode switch can retain a BIN in flash as:

The source image used during the most recent installation
A target image copied in preparation for an upgrade
An older image retained for an approved recovery procedure
An unused file waiting for cleanup

A listing from dir flash: does not establish the boot mode. Use show version for the running mode and show boot for the next path.

Upgrade workflows

Install mode

Cisco documents a combined Add, Activate, and Commit operation:

install add file flash:<IOS-XE-IMAGE>.bin activate commit

The workflow can be staged where the release supports it. Add extracts and prepares packages. Activate selects the new package set and normally reloads the switch. Commit makes the release the committed boot set. Check the state before and after installation:

show version
show boot
show install summary
dir flash:

For a real Catalyst 9200L upgrade in which the Add stage had already completed, see Cisco Catalyst 9200L Upgrade: Fixing “Super Package Already Added”.

Bundle mode

A traditional Bundle-mode upgrade copies and verifies the target BIN, changes the boot variable, saves the configuration, and reloads. For a Catalyst 9200 conversion to Cisco's recommended Install mode, follow the procedure for the platform and release. Changing the boot variable alone does not prepare the package set.

Preparing the files before changing the boot path

A boot path using packages.conf needs a valid provisioning file and every referenced package in flash. A BIN boot path needs an intact, supported image available on each required stack member. Follow Cisco's conversion or upgrade procedure for the exact platform and release. Do not use an arbitrary .conf file, edit packages.conf manually, or select an inactive package set.

Files to preserve during cleanup

Install mode

Do not delete the active packages.conf.
Do not delete .pkg files referenced by the active provisioning file.
Do not assume every BIN file is disposable; it may be a newly copied target image or part of the recovery plan.
Confirm that the active package set is committed before post-upgrade cleanup.

Bundle mode

Do not delete the BIN image referenced by the boot variable.
Verify that the target BIN exists and passes the published checksum before changing the boot path.
In a switch stack, confirm that the required image is available on every applicable member.

The install remove inactive command can also list standalone BIN files for deletion. For a detailed explanation of the deletion list and safe timing, see Cisco Catalyst 9200 install remove inactive Explained.

Common mistakes

Checking only the files in flash. A BIN file can exist on an Install-mode switch.
Checking only the current running mode. The next-reload boot variable may point somewhere else.
Setting packages.conf without a valid package set. The provisioning file and referenced packages must match.
Deleting active PKG files manually. Install mode depends on them at boot.
Deleting the active BIN in Bundle mode. The switch needs that file after a reload.
Ignoring stack consistency. Stack members must use a compatible image and boot design.
Treating all releases identically. Supported commands and recommended workflows can differ by IOS XE release.

Pre-upgrade checklist

Record the model, current IOS XE release, and stack topology.
Use show version to identify the current mode.
Use show boot to verify the next-reload boot variable.
Use show install summary to review the installation state, especially in Install mode.
Check the required BIN, CONF, and PKG files in flash.
Verify available flash space and the target image checksum.
Use the Cisco upgrade or conversion procedure for the exact platform and release.
Confirm the rollback and recovery plan before removing any software files.

Checks before changing software

Protect packages.conf and its referenced packages in Install mode, or the selected BIN in Bundle mode. Install mode is Cisco's recommended option for Catalyst 9200. Before upgrading, converting, or deleting software, compare show version, show boot, show install summary, and the flash contents. The running mode and the next-reload path can differ.

References

Software installation and boot-variable changes can reload the switch or prevent startup when required files are missing. Check the model, stack state, IOS XE release, image family, checksum, and approved procedure before a production change.

Search This Blog

NetOps Field