Convert Bin To Pkg Better 2021 — Cisco

Converting a Cisco IOS-XE monolithic image (.bin) into individual package files (.pkg) transitions the device from Bundle Mode to Install Mode. Cisco recommends Install Mode for production because it is more efficient and supports modern features. Why Convert? (Bundle vs. Install) Bundle Mode (.bin) Install Mode (.pkg) Boot Speed Slower; must extract .bin to RAM first. Faster; reads pre-extracted .pkg files. Memory Use Higher RAM consumption. Lower; only loads required packages. Auto-Upgrade Not supported for new stack members. Automatically upgrades joining stack members. Key Features SMUs and ISSU may be limited. Full support for SMUs and patching.

💡 Note: Cisco has announced that Bundle Mode will be discontinued after IOS-XE Release 17.18. How to Convert: The Procedure

The goal is to extract the .bin file into .pkg files and update the boot variable to point to a provisioning file called packages.conf. Step 1: Verify Current Mode Check if you are currently in Bundle or Install mode.

show version | include mode # Output will say "Mode: BUNDLE" or "Mode: INSTALL" Use code with caution. Copied to clipboard Step 2: Extract the Packages

Use the expansion command to break the .bin file into its component .pkg parts.

Converting Cisco IOS XE devices from a monolithic file (Bundle Mode) to individual cisco convert bin to pkg better

files (Install Mode) is the Cisco-recommended practice for modern networking hardware. This shift optimizes resource utilization and enables advanced features that are unavailable in legacy modes. Why Install Mode (.pkg) is Superior Faster Boot Times : In Bundle Mode, the device must extract the file into memory every time it boots. In Install Mode, the

files are already extracted to the flash memory, allowing the device to start significantly faster. Reduced RAM Consumption

: Because the OS is already extracted on the flash, the device only loads the necessary components into RAM, rather than the entire monolithic image. Advanced Features Support : Critical maintenance and high-availability features like Software Maintenance Upgrades (SMUs) In-Service Software Upgrades (ISSU) , and patching are only supported in Install Mode. Automated Stack Synchronization

: Install Mode allows a stack master to automatically push firmware to new members joining with incorrect versions. Comparison Table: Bundle vs. Install Mode Bundle Mode (.bin) Install Mode (.pkg) Monolithic packages.conf (pointers to Extraction Done at every boot to RAM Done once to flash during installation Boot Speed SMU/Patching Not supported (as of 17.9.x) Full Support Auto-Upgrade Incompatible Compatible How to Convert from .bin to .pkg The conversion process involves using the command suite to extract the contents of the

Prerequisites

Before beginning, ensure you have:

Root Access: You need the username and password for the ISE CLI (typically the admin account).
A Secure FTP (SFTP) Server: You need a place to host the .bin file so ISE can download it.
Disk Space: Ensure the ISE repository has enough space for both the downloaded .bin and the resulting .pkg.

Technique A: Offline Expansion Using a Virtual Machine

Run Cisco’s IOS-XE in CML (Cisco Modeling Labs) or EVE-NG, expand once, then copy the PKG folder to all devices.

Workflow:

Spin up a virtual Catalyst 9000v in CML.
Copy the BIN to its flash.
Run request platform software package expand.
Download the entire flash folder (all PKGs + packages.conf) via SCP.
Deploy the folder to all production switches.

Benefit: No need to perform expansion on live production switches.

Pro Tip: Use Cisco’s VCS (Expressway) as a Proxy

If you have a Cisco VCS (Video Communication Server) on your network, you can tftp the BIN file to the VCS and configure it to repackage the firmware as a PKG on-the-fly using the xConfiguration Firmware Upgrade commands. This is the only enterprise-grade "transparent" conversion.

What is a Cisco `.bin` File?

Binary Image: A raw, monolithic binary file containing the operating system (CE/TC/ROOM OS) or DSP firmware.
Common Use: Typically used for manual recovery via serial port (XMODEM), USB boot, or for older generation devices.
Structure: Usually a flat file or a compressed tarball without a strict integrity manifest for the device installer.

Step 3 – Observe the Output

The system will:

Decompress the BIN.
Extract individual .pkg files (e.g., routing-pkg.pkg, crypto-pkg.pkg, esp-pkg.pkg, etc.).
Create a packages.conf file that lists them.

Sample successful output:

Expanding file flash:cat9k_iosxe.17.09.01.SPA.bin
Extracting packages:
  cat9k-cc_17.09.01.SPA.pkg ... OK
  cat9k-espbase_17.09.01.SPA.pkg ... OK
  cat9k-routing_17.09.01.SPA.pkg ... OK
  packages.conf (updated) ... OK
Expansion completed successfully.

Technical Paper: Converting Cisco BIN to PKG – Best Practices and Methodology

Date: April 21, 2026
Subject: Cisco IOS-XE Software Package Conversion

Step 1: Upload the Bin File

Upload your .bin file (e.g., ise-upgrade-3.1.0.518.SPA.x86_64.bin) to your external SFTP server.

Warning: Do not upload the .bin file directly to the ISE disk via USB or SCP unless necessary. It is best practice to let ISE pull the file from a repository during the conversion process to prevent filling up the local disk.