CCNA 200-301

CCNP Enterprise

CCNP Security

CCIE Enterprise Lab

CCIE Security Lab

CCNP Service Provider

CCNP Data Center

CCNP Collaboration

CCIE DC Lab

When network administrators transition from legacy Cisco Catalyst platforms—such as the Catalyst 2960X, 3560, or 3750—to the enterprise-grade Cisco Catalyst 9300 Series, one of the first discrepancies they encounter is during routine hardware audits or password recovery workflows. Running the traditional show version command does not yield the expected hexadecimal configuration register at the bottom of the output.

In classic Cisco IOS, the 16-bit software configuration register (such as 0x2102 or 0x2142) governed fundamental boot behaviors, console line speeds, and whether the system loaded or bypassed NVRAM startup configurations. On modern Catalyst 9000 Series switches powered by Cisco IOS XE, this legacy register has been fully superseded. Below is everything you need to know about checking boot parameters, inspecting ROMMON variables, replacing obsolete register settings, and executing administrative recoveries on the Catalyst 9300.


Frequently Asked Questions: The Catalyst 9300 Configuration Register

Why is the configuration register not showing in Cisco Catalyst 9300 show version?

Cisco Catalyst 9300 switches run Cisco IOS XE, a modern operating system built on a Linux kernel that interacts directly with modular bootloaders rather than legacy monolithic IOS microcode. The traditional 16-bit software configuration register does not exist at a hardware or architectural level on the Catalyst 9300.

In early Cisco IOS XE releases, a dummy configuration register value was still displayed at the bottom of show version, and the global configuration command config-register was technically accepted by the parser. However, these settings had no functional impact on the actual hardware boot process, which led to operational confusion and misconfigurations. Consequently, Cisco permanently removed the configuration register line from the show version output starting in Cisco IOS XE Everest 16.12.4 and Amsterdam 17.3.1.

Can I still use the config-register CLI command in Cisco IOS XE?

On current IOS XE releases, the config-register <hex-value> command is deprecated, ineffective, or completely removed from the CLI hierarchy. Entering a command like config-register 0x2142 will either return a syntax rejection or have zero effect on subsequent reloads. Boot parameters and configuration bypass flags are now handled exclusively through dedicated IOS XE CLI commands and low-level ROMMON environment variables.


Official Cisco Architecture: Configuration Register Replacement CLIs

Cisco outlines the architectural shift from legacy register masks to modern commands in Cisco Technical Support Documentation (Doc ID 216850: “Configuration Register Equivalent CLIs in Cisco IOS XE”).

Under legacy Cisco IOS, administrators manipulated specific bit positions inside a 16-bit hexadecimal word:
* Bits 0–3 (Boot Field): Determined whether the device dropped to ROMMON (0x0), booted a bootloader helper image (0x1), or parsed boot system parameters from NVRAM (0x2–0xF).
* Bit 6 (Ignore NVRAM): Instructed the bootloader to ignore the startup configuration stored in NVRAM (commonly 0x2142 during password recovery).
* Bit 8 (Break Disable): Controlled console break key capability during the initial boot sequence.
* Bits 5, 11, and 12 (Console Speed): Defined console port baud rates ranging from 1200 bps up to 115200 bps.

In Cisco IOS XE on Catalyst 9000 Series switches, bitmask registers are replaced by explicit, human-readable CLI commands in Cisco IOS XE EXEC and Global Configuration modes. These commands write discrete key-value pairs directly to non-volatile flash environment variables (ROMMON variables). Rather than interpreting a cryptographic-like hex value, the bootloader evaluates explicit environment flags, such as MANUAL_BOOT, ENABLE_BREAK, and SWITCH_IGNORE_STARTUP_CFG.


Classic Cisco IOS vs. Cisco IOS XE Boot Settings Comparison

The following table maps classic Cisco IOS configuration register values directly to their modern Cisco IOS XE command equivalents and underlying ROMMON variables on Catalyst 9300 switches:

Desired Switch BehaviorClassic Cisco IOS Hex ValueModern Cisco IOS XE CommandActive ROMMON Variable
Boot Normally from Flash0x2102 / 0x102Switch(config)# no boot manualMANUAL_BOOT=no
Stop at ROMMON Prompt on Reload0x0 / 0x2120Switch(config)# boot manualMANUAL_BOOT=yes
Bypass Startup Configuration0x2142Switch(config)# system ignore startupconfig switch allSWITCH_IGNORE_STARTUP_CFG=1
Load Startup Configuration Normally0x2102Switch(config)# no system ignore startupconfig switch allSWITCH_IGNORE_STARTUP_CFG=0
Enable Console Break Signal0x2102 (Bit 8 unset)Switch(config)# boot enable-breakENABLE_BREAK=yes
Disable Console Break Signal0x2002 (Bit 8 set)Switch(config)# no boot enable-breakENABLE_BREAK=no
Change Console Baud Rate (e.g., 115200)0x3922Switch(config-line)# speed 115200BAUD=115200
Disable Standard Password Recoveryservice password-recovery disabledSwitch(config)# system disable password recovery switch allSWITCH_DISABLE_PASSWORD_RECOVERY=1

Step-by-Step Guide: How to Check Boot Variables and ROMMON Settings

Because show version no longer presents configuration register state, switch administrators must use specific verification commands in Cisco IOS XE or directly within ROMMON.

Step 1: Inspect System Boot Paths

To check which software image the switch is scheduled to load, run the show boot command from privileged EXEC mode:

Switch# show boot
---------------------------
Switch 1
---------------------------
Current Boot Variables:
BOOT variable = flash:packages.conf;
Configuration Register Variable = 0x102

Boot Variables on next reload:
BOOT variable = flash:packages.conf;
Manual Boot = no
Enable Break = yes
Boot Mode = DEVICE
iPXE Timeout = 0

Note: While legacy field labels like “Configuration Register Variable” may still linger as residual cosmetic artifacts on certain firmware builds, the actionable parameters are BOOT variable, Manual Boot, and Enable Break.

Step 2: Display Low-Level ROMMON Variables (show romvar)

The authoritative command to verify all underlying boot variables on a Catalyst 9300 is show romvar:

Switch# show romvar
ROMMON variables:
 SWITCH_NUMBER = 1
 BOARD_REVISION = 5
 MOTHERBOARD_SERIAL_NUM = FOC23000000
 MODEL_NUM = C9300-48P
 SYSTEM_SERIAL_NUM = FOC23000000
 MAC_ADDR = 70:69:79:00:11:22
 MANUAL_BOOT = no
 ENABLE_BREAK = yes
 SWITCH_IGNORE_STARTUP_CFG = 0
 BAUD = 9600
 BPF_REV = 1
 RET_2_RTS = 
 BOOT = flash:packages.conf;

This output confirms the active operational parameters. If SWITCH_IGNORE_STARTUP_CFG is set to 0, the switch will load the saved startup configuration upon reboot.

Step 3: Check Environment Variables from ROMMON Mode

If the switch is halted at the switch: bootloader prompt, view the same variables using the set command:

switch: set
BAUD=9600
BOOT=flash:packages.conf;
ENABLE_BREAK=yes
MANUAL_BOOT=no
MODEL_NUM=C9300-48P
SWITCH_IGNORE_STARTUP_CFG=0
SWITCH_NUMBER=1

Step-by-Step Guide: Bypassing Startup Configuration for Password Recovery

On classic Cisco switches, password recovery required changing the register to 0x2142. On a Catalyst 9300, password recovery is completed by manipulating the SWITCH_IGNORE_STARTUP_CFG variable in the bootloader.

+------------------------------------+
| 1. Connect Console & Power Cycle   |
+------------------------------------+
                  |
                  v
+------------------------------------+
| 2. Hold Mode Button -> switch:     |
+------------------------------------+
                  |
                  v
+------------------------------------+
| 3. SWITCH_IGNORE_STARTUP_CFG=1     |
|    boot flash:packages.conf        |
+------------------------------------+
                  |
                  v
+------------------------------------+
| 4. copy startup-config running-cfg |
+------------------------------------+
                  |
                  v
+------------------------------------+
| 5. Reset Admin Credentials         |
+------------------------------------+
                  |
                  v
+------------------------------------+
| 6. no system ignore startupconfig  |
|    write memory                    |
+------------------------------------+

Step 1: Connect Console and Interrupt Boot

  1. Attach a rollover console cable (9600-8-N-1) to the console port.
  2. Power cycle the switch.
  3. As the switch initiates bootstrap, press and hold the physical Mode button on the front panel. Release it after approximately 10–12 seconds once the SYST LED transitions from amber to blinking green/amber, dropping the console to the switch: prompt.

Step 2: Set the Startup Config Ignore Variable

At the bootloader prompt, define the environment flag to bypass NVRAM:

switch: SWITCH_IGNORE_STARTUP_CFG=1

Note: Bootloader commands and variable names in ROMMON are strictly case-sensitive.

Step 3: Boot Cisco IOS XE

Identify and boot the installed system image. For standard install-mode deployments:

switch: boot flash:packages.conf

Step 4: Merge Existing Startup Configuration

Once the switch finishes initialization, it bypasses NVRAM and opens the unconfigured prompt without asking for a password. Do not enter initial setup mode.

Switch> enable
Switch# copy startup-config running-config

Warning: You must copy startup-config into running-config. Reversing this command will overwrite your entire saved network configuration with an empty file.

Step 5: Configure New Administrative Passwords

Re-establish local authentication credentials:

Switch# configure terminal
Switch(config)# enable secret <NEW_SECURE_PASSWORD>
Switch(config)# username admin privilege 15 secret <NEW_ADMIN_PASSWORD>

Step 6: Reset the Startup-Config Bypass Flag and Save

As covered in the comparison architecture above, you must return the bypass variable to normal operation before rebooting:

Switch(config)# no system ignore startupconfig switch all
Switch(config)# end
Switch# copy running-config startup-config

Verify that SWITCH_IGNORE_STARTUP_CFG reads 0 via show romvar before conducting any further reboots.


Troubleshooting Guide: Catalyst 9300 Not Loading Startup Config After Reload

A recurring issue on Catalyst 9300 switches is a unit that continuously reverts to the Initial Configuration Dialog (Would you like to enter the initial configuration dialog? [yes/no]:) every time it reboots, despite administrators issuing write memory or copy running-config startup-config.

Cause of the Issue

This behavior occurs when the switch underwent prior password recovery or staging, and the administrator neglected to clear the SWITCH_IGNORE_STARTUP_CFG variable. The switch continues to write valid configurations to flash:startup-config, but on every subsequent boot, the bootloader honors the active variable and deliberately skips NVRAM parsing.

Resolution Steps

Method A: Remediation from Cisco IOS XE (Recommended)

If you can access privileged EXEC mode on the switch:

  1. Check current ROMMON variables to verify the culprit:
    text
    Switch# show romvar | include SWITCH_IGNORE_STARTUP_CFG
    SWITCH_IGNORE_STARTUP_CFG = 1
  2. Enter global configuration mode and clear the variable across all stack members:
    text
    Switch# configure terminal
    Switch(config)# no system ignore startupconfig switch all
    Switch(config)# end
  3. Commit the changes to NVRAM:
    text
    Switch# write memory
  4. Confirm the variable has flipped to 0:
    text
    Switch# show romvar | include SWITCH_IGNORE_STARTUP_CFG
    SWITCH_IGNORE_STARTUP_CFG = 0

Method B: Remediation from ROMMON Mode

If the switch cannot boot into an operable configuration or is stuck in an administrative loop:

  1. Interrupt boot via the Mode button to reach the switch: prompt.
  2. Check active variables using set:
    text
    switch: set
  3. Clear the ignore variable explicitly:
    text
    switch: unset SWITCH_IGNORE_STARTUP_CFG

    (Alternatively: switch: SWITCH_IGNORE_STARTUP_CFG=0)
  4. Boot the switch:
    text
    switch: boot flash:packages.conf
  5. Once loaded, re-save your running configuration using write memory.

Catalyst 9300 Boot Configuration and ROMMON Cheat Sheet

Use this reference template for day-to-day administrative checks, register-replacement tasks, and boot variable auditing.

Cisco IOS XE EXEC Mode Verification Commands

! Verify software version and active package bundle
show version

! Verify current and next-reload boot paths and break status
show boot

! View low-level ROMMON environment variables (replaces config-register check)
show romvar

! Inspect active console baud rate and line parameters
show running-config | section line con 0

Cisco IOS XE Global Configuration Commands

configure terminal

! Set switch to boot normally (Equivalent to 0x2102)
no boot manual

! Force switch to halt at ROMMON prompt on reboot (Equivalent to 0x2120 / 0x0)
boot manual

! Set startup-config bypass on next reload (Equivalent to 0x2142)
system ignore startupconfig switch all

! Restore normal startup-config parsing on next reload (Clear 0x2142)
no system ignore startupconfig switch all

! Enable/Disable console break key during bootstrap
boot enable-break
no boot enable-break

! Set primary boot image path
boot system flash:packages.conf

end
write memory

ROMMON Mode (switch:) Syntax Template

! List all active environment variables
set

! Ignore startup configuration for password recovery
SWITCH_IGNORE_STARTUP_CFG=1

! Re-enable startup configuration loading from ROMMON
SWITCH_IGNORE_STARTUP_CFG=0
! or
unset SWITCH_IGNORE_STARTUP_CFG

! Set or disable manual boot
MANUAL_BOOT=0
! or
unset MANUAL_BOOT

! Manually trigger boot sequence using installed packages
boot flash:packages.conf

! Recover from USB drive in emergency mode
boot usbflash0:cat9k_iosxe.<version>.SPA.bin

Conclusion

The omission of the configuration register from the Cisco Catalyst 9300 show version output represents a permanent architectural evolution in Cisco IOS XE. Hexadecimal bitmasks have been replaced by explicit, readable CLI commands and persistent ROMMON variables. By replacing outdated config-register habits with modern commands like show romvar, show boot, and no system ignore startupconfig switch all, network engineers can accurately verify boot paths, execute seamless password recoveries, and prevent persistent startup configuration loading failures.

Please follow and like us:
Last modified: November 17, 2026

Author

Comments

Write a Reply or Comment

Your email address will not be published.