Cisco Console: How to Reliably Interrupt Boot and Enter ROMMON or the Bootloader

February 12, 2026

Sometimes all you need is one small pause during startup. The device powers on, the text flies by, and there’s a short window where you can stop the process and drop into ROMMON or the switch bootloader prompt (switch:). On paper it’s simple. In real life it often turns into this: you hit the “right” keys and the device ignores you.

Most of the time the reason is straightforward: different Cisco platforms expect different kinds of interrupts. Some want a true BREAK signal, while others will happily accept regular keystrokes like Ctrl+C, Ctrl+L, or ESC. Add timing to the mix—the window can be so short that “press it once at the perfect moment” becomes pure luck.

Below is a method that removes the luck and makes this repeatable.

If you work with console ports often (especially across lots of devices), take a look at clideck.com—we’re building practical guides and tools around real-world serial/console work, focused on the stuff that actually slows you down.

Quick fix (if you need it right now)

Open the console with sane settings (most of the time that’s 9600 / 8N1 / no flow control).

Reload or power-cycle the device.

Right after the reboot, don’t try to “hit the one perfect second.” Cover the window instead:

if you need ROMMON on a router, try sending BREAK (best via a terminal’s “Send Break” command if it has one);

if you need switch: on a switch, and the device has a physical MODE button, use it during power-on; if MODE isn’t an option (or you’re remote), try BREAK;

if it looks like the loader is reacting to normal keystrokes, try Ctrl+C, then Ctrl+L, then ESC, then Space/Enter.

When it works, you’ll see rommon> or switch: (or another boot/loader prompt).

What you’re trying to reach (and why it changes what you press)

Before the main OS comes up, Cisco devices can drop you into a few different places:

ROMMON (common on routers): prompt looks like rommon>

Switch bootloader (common on many fixed Catalyst switches): prompt often looks like switch:

Loader/boot menu: a menu or a different pre-OS prompt

The important part is not to mix up two very different kinds of “interrupt”:

BREAK is not really “a key combo.” It’s a specific signal on the line. Many routers expect this.

Ctrl+C / Ctrl+L / ESC are normal keyboard input. Some bootloaders watch for these instead.

So when someone says “Ctrl+C doesn’t work,” it often doesn’t mean they did it wrong—it means the platform was waiting for BREAK.

Two things that commonly get in the way

Wrong speed or flow control enabled

If the screen is garbled or characters drop/merge, fix your console settings first. Otherwise you might actually succeed but never recognize the prompt.

Make sure you’re on the CONSOLE port

It sounds obvious, but it’s a real time-waster. If you’re not on the real console path (or the cable isn’t what you think it is), nothing you press will matter.

How to stop missing the timing window

Trying to hit a one-second window is a bad strategy. A more reliable approach is:

Reload the device.

Immediately start sending the interrupt multiple times, not once.

Keep doing it for the first 10–30 seconds (sometimes longer, depending on the platform).

You’re not waiting for the prompt—you’re acting early so you don’t have to guess.

What to try in practice (in the order that saves time)

This is the sequence that usually gets you there fastest. Start at the top and work down.

If it’s a router and you need ROMMON (rommon>)

Use the terminal’s Send Break (if available)

Try Ctrl+Break (only if your setup actually generates BREAK that way)

If BREAK won’t go through, jump to “When BREAK doesn’t work”

Why: on many routers, ROMMON entry is tied to BREAK. Ctrl+C may do nothing.

If it’s a switch and you need the bootloader (switch:)

Use MODE during power-on (if the device has it—this is often the most predictable path)

Try BREAK (Send Break / Ctrl+Break)

If the loader seems to accept normal input: Ctrl+C, then Ctrl+L, then ESC

Space or Enter (yes, sometimes that’s all it takes to stop autoboot)

Why: switch bootloaders often behave differently than router ROMMON. BREAK can be flaky over some console servers, while regular keystrokes can work consistently.

If the screen tells you what to press

Sometimes the device prints a message like “Press ESC…” or “Press any key…”—in that case, follow the instruction and press it a few times in a row. Don’t overthink it.

When BREAK doesn’t work

If you’re confident BREAK is required but the device won’t react:

Change how you send BREAK The most common issue is that your terminal/adapter combo doesn’t generate BREAK the way the platform expects. If your terminal has an explicit “Send Break” action, use that instead of guessing key combos.

Check the whole chain: USB-serial adapter, cable, hubs/docks Some cheap adapters (or certain hubs) “mostly work” but behave unpredictably for BREAK.

Try the old 1200-baud + Space trick It’s not universal, but it can rescue you when you can’t get a clean BREAK through. The idea is to trigger a break-like effect on platforms that support it.

How you’ll know you made it

rommon> means you’re in ROMMON

switch: means you’re in the switch bootloader

Any loader menu/prompt still counts—you stopped the boot, and you can proceed with recovery or manual boot from there

One last note

If you do this kind of recovery work often—password resets, image issues, manual boot selection—you already know the “hard” part isn’t the commands. It’s the little things: which port, which cable, which interrupt, and why it worked yesterday but not today.

That’s exactly what we focus on at clideck.com: practical console workflows that save you time when you’re staring at a flashing cursor and a ticking boot timer. ## Cisco boot-interrupt cheat sheet (family-based, vertical format)

IOS / IOS XE routers (general) — ISR / ASR (many), some 8xx/19xx/29xx/39xx/4k

Target prompt: rommon> Primary method (try first): BREAK during early boot (prefer a terminal’s explicit Send Break) Fallbacks (in order):

Ctrl+Break (only if your setup truly generates BREAK)
Retry BREAK as a tight series for the first 10–30 seconds after reload
Switch terminal app and/or USB-serial adapter
1200 baud + hold Space (break-simulation, only if the platform supports it) On-screen signs: “Press BREAK to interrupt” or you drop straight into rommon>

ISR 4000 (IOS XE) — 43xx / 44xx

Target prompt: rommon 1 > Primary method: BREAK sequence during early boot (best via Send Break) Fallbacks:

Send BREAK repeatedly right after power-cycle (don’t time a single press)
Change terminal app (use one with a real Send Break action)
Check/replace the USB-serial adapter and hubs/docks On-screen signs: you land at rommon 1 >

Catalyst fixed switches (classic) — 2900XL/3500XL/2940/2950/2960/2970/3550/3560/3750

Target prompt: switch: Primary method: MODE button during power-on (most predictable when available) Fallbacks:

If MODE isn’t available: try BREAK (Send Break / Ctrl+Break)
If the loader clearly accepts normal keystrokes: Ctrl+C, then ESC
Space/Enter (only if the device hints “press any key…”) On-screen signs: switch:

Catalyst 3850 (and close-generation fixed platforms)

Target prompt: switch: Primary method: MODE button during power-on (watch LEDs / follow the boot messages) Fallbacks:

Repeat the MODE attempt (timing can matter)
Remote-only scenario: try BREAK (less consistent on some setups) On-screen signs: switch:

Catalyst 9000 (C9K) — 9200/9300/9400/9500/9600

Target prompt: bootloader / recovery prompt (varies by model and situation) Primary method:

Fixed models: typically MODE button during power-on
Chassis/others: follow the platform’s boot/recovery behavior and on-screen prompts Fallbacks:

If you see an explicit instruction (ESC / any key / Ctrl+C): follow it and press it a few times
If BREAK is supported in your exact scenario: use Send Break and retry as a series On-screen signs: a bootloader/recovery prompt or a loader menu

Cisco ASA (classic ASA families)

Target prompt: rommon #> Primary method: ESC when prompted during boot Fallbacks:

Press ESC several times in a row (don’t rely on a single tap)
If the platform/terminal supports it in your case: try BREAK-style interruption On-screen signs: “Press ESC to enter ROMMON” then rommon #>

Firepower / Secure Firewall (FTD/FXOS) — common on 1000/2100/3100 families

Target prompt: ROMMON / pre-OS recovery prompt Primary method: ESC during the early boot window Fallbacks:

Press ESC repeatedly during the window (it can be short)
Follow any on-screen hint (some loaders show exactly what to press) On-screen signs: ROMMON/recovery prompt appears after the ESC window

Nexus 9000 (NX-OS)

Target prompt: loader> Primary method: Ctrl+C during the “Loading Boot Loader” phase (press more than once) Fallbacks:

Send Ctrl+C as a short burst during that phase
Power-cycle and retry (timing is tight)
Follow the on-screen instruction if it changes across versions On-screen signs: loader>