Cisco IE3300 IOS XE Image Recovery: Step-by-Step Guide

A Cisco Catalyst IE3300 that stops at the switch: prompt or keeps restarting may have a missing boot path, an unavailable packages.conf file, or a damaged IOS XE image. Before replacing the switch, check whether a bootable image is still available. In many cases, you can recover the software through the console, transfer a new image with TFTP, and restore a saved configuration.

This guide covers two situations: booting an existing packages.conf file and using the emgy0: emergency recovery partition when the normal image is unavailable. The commands below use Cisco IOS XE 17.12.04 as an example, not a recommendation to install that particular release on every IE3300.

Important: Perform recovery during an approved maintenance window. Keep a console connection available, back up any accessible configuration, and isolate the switch from production networks when using the emergency image or TFTP. Recovery can bring the switch up with factory-default settings; do not assume that the previous configuration will load automatically.

Before you begin

You will need a console cable and terminal application, the correct Cisco IOS XE image for your IE3300 model, a laptop running a TFTP server, and a backup configuration if you plan to restore the switch. Download software from Cisco Software Download and verify its compatibility and integrity using Cisco’s release information. Cisco documents 9600 baud, 8 data bits, no parity, and 1 stop bit for the console connection in this recovery procedure.

For the network examples below, the switch will use 192.168.10.1/24 and the TFTP laptop will use 192.168.10.100/24. These are temporary addresses; replace them to suit your isolated recovery network.

Step 1: Check flash for packages.conf

If the switch is at the bootloader prompt (switch:), list the internal flash contents:

switch: dir flash:

Look for packages.conf. This file is used to boot Cisco IOS XE in install mode. It must reference software package files that are also present and valid in flash. Simply seeing the filename does not guarantee that all packages are intact.

If packages.conf is available and the required package files are present, try booting it:

switch: boot flash:packages.conf

If the switch starts successfully and its saved configuration is still available, log in and check the configured boot path. To set the boot path to packages.conf for the next restart, use:

Switch> enable
Switch# configure terminal
Switch(config)# no boot system
Switch(config)# boot system flash:packages.conf
Switch(config)# end
Switch# write memory
Switch# reload

Note: This section applies when the switch is already using a valid install-mode image. If it boots using a .bin file, that is bundle mode; copying a .bin file into flash does not automatically create packages.conf.

Step 2: Locate the emergency recovery image

If packages.conf is missing or unusable, first check whether another valid image exists in flash: or on supported external media. If there is no working normal image, return to the switch: prompt and inspect the emergency partition:

switch: dir emgy0:

The filesystem name is emgy0: (zero), not emgyo: (the letter O). Cisco documents the emergency image in this partition, but the actual filename and version vary between devices.

In this recovery example, the emergency image filename is:

ie3x00-universalk9_literecovery.17.05.01.SPA.bin

Only if that exact file appears in your dir emgy0: output, boot it with:

switch: boot emgy0:ie3x00-universalk9_literecovery.17.05.01.SPA.bin

If your listing shows a different image, substitute the exact filename displayed on your switch. Cisco’s published recovery examples use different filenames, so do not assume every IE3300 includes the literecovery image shown here. The bootloader may update itself first and require you to repeat the boot command; follow the console output.

Configuration warning: Emergency recovery may result in a factory-default running configuration. If the Express Setup button was used to interrupt a boot loop, Cisco notes that the startup configuration is renamed. Make sure you have a usable backup before proceeding with configuration restoration. Avoid erasing or formatting storage simply to make the switch boot.

Step 3: Configure a temporary IP address

After the emergency image boots, set up the temporary connection to your TFTP laptop. Cisco’s IE3x00 emergency recovery instructions identify Gi1/3 as the connection port for the documented recovery setup; confirm your physical model and port configuration before connecting.

Assign the switch an address on VLAN 1:

Switch> enable
Switch# configure terminal
Switch(config)# interface vlan 1
Switch(config-if)# ip address 192.168.10.1 255.255.255.0
Switch(config-if)# no shutdown
Switch(config-if)# end

Set your laptop’s Ethernet address to 192.168.10.100 with subnet mask 255.255.255.0, and make sure the connected switch port is up and belongs to VLAN 1. Run a TFTP server on the laptop, place the firmware in its shared/root directory, and allow TFTP traffic through the laptop’s firewall as required.

Verify connectivity:

Switch# ping 192.168.10.100

If the ping fails, check the physical link, VLAN 1 status, laptop subnet mask, local firewall, and TFTP server binding before attempting the image transfer.

Step 4: Copy the Cisco IOS XE image with TFTP

Once the switch can reach the laptop, transfer the software image to internal flash. This example uses the valid IE3x00 image filename for IOS XE 17.12.04; use the image approved for your hardware and environment.

Switch# copy tftp: flash:
Address or name of remote host []? 192.168.10.100
Source filename []? ie3x00-universalk9.17.12.04.SPA.bin
Destination filename [ie3x00-universalk9.17.12.04.SPA.bin]?

At the destination filename prompt, press Enter to accept the proposed name. Confirm the TFTP server is serving the correct directory, that sufficient flash space is available, and that the copy completes successfully. Transfer time varies with image size, connection speed, and TFTP performance; it is not always 35 minutes.

Check that the image is present:

Switch# dir flash:

Step 5: Configure the recovered image to boot

The following commands use bundle mode, which boots the .bin image directly. They follow the same approach as the original recovery workflow:

Switch# configure terminal
Switch(config)# no boot system
Switch(config)# boot system flash:ie3x00-universalk9.17.12.04.SPA.bin
Switch(config)# end
Switch# write memory
Switch# reload

Let the switch restart and watch the console for image-validation or bootloader messages. Do not interrupt power during a bootloader upgrade. Once IOS XE is available, confirm that the software loaded before restoring the configuration.

If you want to operate in install mode instead, follow the Cisco installation workflow for your specific software release. In install mode, the install process creates/updates the package files and packages.conf; do not set boot system flash:packages.conf just because you copied a .bin file to flash.

Step 6: Restore the saved configuration

After the switch boots the recovered image, reconnect the laptop and, if necessary, temporarily configure VLAN 1 again using Step 3. Place your known-good configuration backup in the TFTP server’s shared directory. This example calls it config.txt.

Copy the file to flash:

Switch# copy tftp: flash:
Address or name of remote host []? 192.168.10.100
Source filename []? config.txt
Destination filename [config.txt]?

Then copy the backup into the startup configuration:

Switch# copy flash:config.txt startup-config

Important: Review the restored configuration’s boot statements before reloading. If it references an image that is no longer installed, correct the backup/boot plan first. Also confirm that the backup is for this switch and does not contain unsuitable credentials, interface assignments, or management settings.

Do not run write memory at this point. Doing so would save the temporary running configuration over the startup configuration you just restored. Reload instead:

Switch# reload

If asked whether to save the modified running configuration, do not save it. Confirm the reload. After the switch starts using the restored startup configuration, log in and verify the network settings and services before saving anything.

Step 7: Verify the recovery

Check the IOS XE version, boot settings, and interface status:

Switch# show version
Switch# show boot
Switch# show ip interface brief
Switch# show startup-config | include boot system

Verify that the expected configuration is active and that the boot path still points to the intended image. Only when the configuration and boot settings are correct should you save them:

Switch# write memory

If you need to prove the recovery will survive another restart, schedule a controlled second reload and check the console and network reachability again.

Common recovery questions

What if packages.conf is missing?

Check for another valid IOS XE image in available storage. If none can boot, use the emgy0: emergency partition to start the switch and transfer a released image. A missing packages.conf alone does not prove that all firmware has been erased.

Will emergency recovery erase the switch configuration?

The switch may start with factory-default settings, and interrupting a boot loop with Express Setup can rename the startup configuration. Treat the saved configuration as unavailable until verified, and keep an off-device backup. Do not describe the emergency boot command itself as a guaranteed secure erase of all configuration data.

Why does the recovery use a .bin file instead of packages.conf?

This walkthrough restores operation using a direct .bin boot in bundle mode. A packages.conf boot is part of install mode, which has a separate software installation process.

Final thoughts

A Cisco IE3300 stuck at the switch: prompt is not necessarily a failed switch. Checking packages.conf, using the emergency image when needed, and carefully restoring the startup configuration can bring the device back into service without replacing the hardware.

At JND Networks LLC, we work with enterprise networking, switching, and troubleshooting. This guide is intended to help network engineers and technicians follow a controlled recovery process and understand what each step changes.

Cisco references: Emergency Recovery Installation for IE3x00 · IE3x00 IOS XE 17.12.x Release Notes · IOS XE 26.2.x Installation Options