The ROM Monitor (ROMMON) mode—indicated on Cisco switches by the switch: prompt—is a low-level diagnostic and bootstrap environment stored in read-only memory. It operates independently of the Cisco IOS or Cisco IOS-XE operating systems, providing network engineers with an essential out-of-band recovery tool. When a switch suffers from corrupted system images, misconfigured boot variables, or lost administrative credentials, booting into ROMMON is the primary method to restore device operation.
Accessing ROMMON requires deliberately halting the hardware initialization sequence before the primary operating system kernel loads into memory. Depending on whether you have physical access to the device rack or are managing the switch through a remote serial console server, multiple techniques exist to reach this environment.
Table of Contents
Frequently Asked Questions: Why Switches Boot into ROMMON Automatically
When a switch drops into ROMMON without administrative intervention, it indicates that the hardware bootloader failed to load an operating system image. Below are the most common root causes and their resolutions.
Why does my Cisco switch boot directly to the switch: prompt instead of loading IOS?
A Cisco switch defaults to the bootloader prompt whenever the primary boot routine fails to complete. This typically occurs because the bootloader cannot find a valid executable binary image in flash storage, the filesystem is unreadable, or a manual boot instruction was explicitly defined in the switch environment variables.
How does a missing or incorrect boot system pointer trigger ROMMON?
During the final stage of POST (Power-On Self-Test), the bootloader checks NVRAM for a valid BOOT variable pointing to an image path (such as flash:packages.conf or flash:c2960x-universalk9-mz.152-7.E8.bin). If this variable is missing, points to a filename that was deleted during an upgrade, or contains a typographical error, the switch cannot resolve what file to execute. Because no valid fallback image is specified, it terminates the sequence and drops to switch:.
Can a corrupted flash filesystem or failed IOS image cause a boot loop?
Yes. If an unexpected power outage occurs during a software upgrade or flash write cycle, the system image may become truncated or corrupted. During boot, the bootloader performs an MD5 checksum and file header verification. If the image fails integrity checks or if the internal flash filesystem table is corrupt, the bootloader rejects the binary and halts at ROMMON to prevent continuous kernel crashing.
What environment flags force the switch into manual boot mode?
Cisco switches maintain internal environment variables that govern boot behavior. If the MANUAL_BOOT variable is set to 1 (or BOOT_MANUAL=yes on certain models), the switch is explicitly instructed to pause and wait for operator intervention at the bootloader prompt after completing POST, even if a valid system image exists in flash.
How to Boot into ROMMON Using the Front-Panel Mode Button
Using the physical Mode button on the switch faceplate is the standard hardware-based method to interrupt the normal initialization sequence. This technique is applicable to most classic fixed-configuration switches, including the Cisco Catalyst 2960, 3560, 3750, and 3850 series.
Front Panel Mode Button
┌────────────────────────┐
│ [Mode] O O O O O O │
│ STAT DUPLX SPD │
└────────────────────────┘
Step 1: Connect to the Switch Console
Attach an RJ-45 or USB console rollover cable to the switch’s console port and connect it to your workstation. Open your terminal emulator configured to standard serial settings:
– Baud Rate: 9600 bps
– Data Bits: 8
– Parity: None
– Stop Bits: 1
– Flow Control: None
Step 2: Disconnect the Power Cable
Remove the AC or DC power cord from the rear power supply of the switch. If the switch uses redundant power supplies or a Cisco Redundant Power System (RPS), ensure all power feeds are disconnected so the unit is completely dark.
Step 3: Reconnect Power While Depressing the Mode Button
Press and hold the Mode button on the front panel of the switch. While keeping the button held down, reconnect the power cord to the primary power supply.
Step 4: Monitor the Front-Panel LEDs
Continue holding the Mode button. The System (SYST) LED will illuminate solid green, transition to amber, and then flash amber or return to solid green depending on the hardware generation. Hold the button for approximately 10 to 15 seconds.
On your console terminal, watch for confirmation text indicating boot interruption:
The system has been interrupted, or encountered an error
during initial initialization. The following commands will
initialize the flash filesystem, and finish loading the
operating system software:
flash_init
boot
Step 5: Release the Mode Button
Release the Mode button once the interruption banner appears on the console or the SYST LED flashes green. The terminal will display the bootloader prompt:
switch:
How to Interrupt Boot and Force ROMMON via Console Break Key
When physical access to the device is unavailable—such as when managing equipment across remote terminal servers—you can interrupt the boot process using a serial Break signal sent from your terminal emulator.
Step 1: Establish an Active Console Session
Open your terminal client and establish a live serial connection to the switch console. Ensure the serial port settings match the switch defaults (9600-8-N-1).
Step 2: Initiate a Hardware Reload or Power Cycle
Execute a reload from the command-line interface:
Switch# reload
Proceed with reload? [confirm]
If the switch is unresponsive, power cycle the switch remotely via a Switched Power Distribution Unit (ePDU).
Step 3: Identify the Break Window
The break signal must be issued within a specific hardware initialization window:
1. Immediately upon power-up, the switch runs low-level POST diagnostics (RAM and ASIC tests).
2. As soon as POST completes and the console displays initial memory sizing or text like Base Ethernet MAC Address...—but before the message Loading "flash:..." or decompression hashes (###) begin—the bootloader listens for a serial interrupt. This window lasts between 5 and 10 seconds.
Step 4: Transmit the Break Signal
Send the Break command from your terminal client (e.g., press Ctrl + Break in PuTTY). Once received by the UART controller, the bootloader aborts OS decompression and displays:
Interrupt:
switch:
Step 5: The 1200 Baud Rate Workaround (If Break Fails)
Some modern USB-to-Serial adapters (especially counterfeit Prolific or FTDI chipsets) fail to transmit a true RS-232 framing break. If the Break key does not halt the boot sequence:
1. Power cycle the switch.
2. In your terminal client settings, change the baud rate from 9600 to 1200.
3. Press and hold the Spacebar continuously for 10 to 15 seconds during the boot window. At 1200 baud, transmitting continuous spaces generates a long stream of binary zeros, which the switch’s serial controller interprets as an electrical break condition.
4. Set the terminal baud rate back to 9600. Press Enter, and the switch: prompt will appear.
Standard Console Break Key Sequences by Terminal Software
An RS-232 Break signal is not a standard ASCII character; it is a hardware framing state where the serial transmit line is driven to a continuous logical zero (space state) for longer than a complete character frame—typically for 200 to 500 milliseconds. Because modern computer keyboards lack a dedicated hardware break pin, terminal emulation programs map key combinations to signal the serial driver to pull the line low.
The following reference details manufacturer-verified break sequences across standard terminal emulation clients:
| Terminal Client | Operating System | Primary Break Key Combination | Menu / Alternative Navigation |
|---|---|---|---|
| PuTTY | Windows | Ctrl + Break | Right-click Title Bar → Special Command → Break |
| SecureCRT | Windows / macOS | Ctrl + Break | Transfer or Edit Menu → Send Break |
| Tera Term | Windows | Alt + B | Control Menu → Send break |
| Solar-PuTTY | Windows | Ctrl + Break | Right-click active session tab → Send Break |
| Minicom | Linux | Ctrl + A, then F | Press Ctrl + A release, then press F (Configurable via minicom -s) |
| GNU Screen | Linux / macOS | Ctrl + A, then Ctrl + B | Enter command mode (Ctrl + A), then type :break |
macOS Terminal (cu) | macOS | ~ followed by Ctrl + B | Escape sequence: Press Return, then ~, then Ctrl + B |
| Zoc Terminal | Windows / macOS | Alt + B | Transfer Menu → Send Break |
Entering ROMMON Mode on Cisco Catalyst 9000 Series Switches
The Cisco Catalyst 9000 series (including the 9200, 9300, 9400, 9500, and 9600 platforms) operates on modern x86 multi-core processors running an enterprise Linux foundation beneath Cisco IOS-XE. While these switches still present a switch: prompt, their bootloader behaves similarly to a PC UEFI environment.
Catalyst 9000 x86 Architecture Boot Stages:
[Power Applied] ──> [UEFI / Coreboot] ──> [GRUB / switch: Prompt] ──> [IOS-XE Linux Kernel]
│
Break / Ctrl+C
▼
[ switch: prompt ]
Hardware Differences and Boot Timing
Catalyst 9000 switches feature SSD storage, internal eMMC flash, and substantially longer boot sequences than legacy platforms. The window to halt execution occurs during early initialization before the system mounts the internal SSD partition (bootflash:).
Procedure 1: Interrupting the Cat 9000 Bootloader via Console
- Connect to the switch console via the standard mini-USB, USB-C, or RJ-45 console port at
9600-8-N-1. - Apply power or enter
reloadfrom privileged EXEC mode. - Watch the console stream as the x86 firmware initializes. You will see memory checks and CPU initialization banners:
text
Initializing Hardware......
System Bootstrap, Version 17.9.1r, RELEASE SOFTWARE (fc1)
Copyright (c) 1994-2022 by cisco Systems, Inc. - When the message
Initializing Hardware...orPress ESC or Ctrl+C to enter boot promptappears, continuously sendCtrl + Cor a standard Break sequence. - The switch will stop the automatic boot routine and load the bootloader prompt:
text
switch:
Procedure 2: Using the Catalyst 9200 / 9300 Mode Button
- Disconnect all primary and secondary power cords from the switch.
- Press and hold the Mode button on the far left of the switch faceplate.
- Re-insert the power cable while holding the button.
- On Catalyst 9000 switches, continue holding the Mode button until the console confirms the interrupt or the STAT and SYST LEDs cycle to solid amber (approximately 12 seconds).
- Release the button when the console output displays:
text
The system has been interrupted, or encountered an error
during initial initialization.
switch:
Modern Recovery on Catalyst 9000 (emergency-install)
Unlike classic switches that boot directly from simple .bin files, Catalyst 9000 switches typically boot in Install Mode via packages.conf. If you are in ROMMON due to a corrupted bootflash, you can restore the switch from a USB drive formatted in FAT32 containing a valid .bin file using the emergency-install command:
switch: emergency-install usb9:/cat9k_iosxe.17.09.04a.SPA.bin
This utility automatically wipes the target bootflash, partitions the internal storage, extracts the modular packages, and boots the switch back into a operational state.
Cisco Switch Password Recovery Steps in ROMMON Mode
Once in ROMMON mode, administrators can bypass the startup configuration (startup-config), boot into base software without credentials, reset the administrative accounts, and preserve the original network configuration.
The procedure differs between classic switches (which read configuration files directly from the flash filesystem) and modern IOS-XE switches (which use boot environment flags).
Classic Catalyst Switches (Catalyst 2960, 3560, 3750)
Step 1: Initialize Flash Storage
The ROMMON environment cannot access storage media by default until the file drivers are loaded. Initialize flash:
switch: flash_init
Verify the contents of flash:
switch: dir flash:
Step 2: Rename the Startup Configuration File
Cisco IOS looks specifically for the file named config.text on the flash drive during boot. Rename this file to prevent IOS from reading it:
switch: rename flash:config.text flash:config.text.old
Step 3: Boot the Operating System Image
Identify your system software binary file using dir flash: and boot the switch:
switch: boot flash:c2960x-universalk9-mz.152-7.E8.bin
Step 4: Restore Configuration and Reset Password
When prompted with Would you like to enter the initial configuration dialog? [yes/no]:, type no and press Enter. You will enter non-privileged EXEC mode:
Switch> enable
Switch#
Rename the old configuration file back to its standard name and copy it into the current memory:
Switch# rename flash:config.text.old flash:config.text
Switch# copy flash:config.text system:running-config
Destination filename [running-config]? [Enter]
Enter configuration mode, overwrite the administrative secret, and save changes:
Switch# configure terminal
Switch(config)# enable secret YourNewStrongPassword123!
Switch(config)# username admin privilege 15 secret YourNewStrongPassword123!
Switch(config)# exit
Switch# write memory
Modern IOS-XE Switches (Catalyst 3850, 9200, 9300, 9500)
Modern platforms avoid file-renaming routines by offering a dedicated bootloader bypass environment variable: SWITCH_IGNORE_STARTUP_CFG.
Step 1: Set Configuration Ignore Variable in ROMMON
At the switch: prompt, instruct the bootloader to ignore the startup configuration stored in flash:
switch: SWITCH_IGNORE_STARTUP_CFG=1
Step 2: Boot the Switch Image
Boot using the current package manifest or binary image:
switch: boot flash:packages.conf
Step 3: Recover Access and Disable the Bypass Flag
The switch will boot into factory-default setup mode. Answer no to the initial setup dialog. At the prompt, enter privileged mode, merge the saved startup configuration into running memory, and update the credentials:
Switch> enable
Switch# copy startup-config running-config
Destination filename [running-config]? [Enter]
Switch# configure terminal
Switch(config)# enable secret YourNewStrongPassword123!
Switch(config)# username admin privilege 15 secret YourNewStrongPassword123!
Step 4: Re-enable Startup Configuration Loading
Clear the bypass flag so future reboots read the configuration normally:
Switch(config)# no system ignore startupconfig
Switch(config)# exit
Switch# write memory
Cisco ROMMON Mode Command Reference Cheat Sheet
The commands below are valid at the switch: bootloader prompt across both classic Cisco Catalyst and modern Catalyst 9000 switches.
# ==============================================================================
# FILESYSTEM & DIRECTORY OPERATIONS
# ==============================================================================
flash_init # Initializes the flash file system driver
dir flash: # Lists files and directories in internal flash
dir usbflash0: # Lists contents of external USB drive (slot 0)
dir bootflash: # Lists contents on Catalyst 9000 internal SSD
format flash: # Formats the internal flash filesystem (Destructive)
# ==============================================================================
# SYSTEM BOOT OPERATIONS
# ==============================================================================
boot # Attempts to boot using default variables
boot flash:packages.conf # Boots modular IOS-XE via package manifest
boot flash:image_name.bin # Boots a standalone classic IOS binary image
boot usbflash0:image_name.bin # Boots directly from an external USB drive
# ==============================================================================
# ENVIRONMENT VARIABLES CONFIGURATION
# ==============================================================================
set # Displays all currently defined variables
BOOT=flash:packages.conf # Defines the primary boot file path
SWITCH_IGNORE_STARTUP_CFG=1 # Ignores startup configuration on next boot (Cat 9k)
SWITCH_IGNORE_STARTUP_CFG=0 # Disables startup configuration bypass
MANUAL_BOOT=0 # Sets automatic booting on power cycle
MANUAL_BOOT=1 # Forces switch to halt at switch: prompt on boot
unset BOOT # Clears an existing variable assignment
unset SWITCH_IGNORE_STARTUP_CFG # Removes the password recovery variable
# ==============================================================================
# CATALYST 9000 EMERGENCY INSTALL UTILITY
# ==============================================================================
# Recovers a corrupted Catalyst 9000 bootflash from an external USB drive
emergency-install usbflash0:cat9k_iosxe.17.09.04a.SPA.bin
# ==============================================================================
# HARDWARE DIAGNOSTICS & SYSTEM CONTROL
# ==============================================================================
version # Displays bootloader ROMMON software release
reset # Reboots the switch hardware platform
help # Displays available bootloader commands
Navigating the Cisco ROMMON environment is an essential skill for restoring switches after failed software installations, damaged filesystems, or lost login credentials. By using either the physical Mode button or a console Break sequence, you can reliably interrupt the hardware initialization routine and drop to the switch: prompt. Once the necessary password recovery flags or filesystem repairs are completed, remember to reset your boot variables to valid system paths (BOOT=flash:packages.conf or equivalent) and verify your startup configuration before returning the switch to production service.











Comments