Switch> enable\nSwitch#\n<\/code><\/pre>\nThe prompt switches from ><\/code> to #<\/code>, indicating privileged mode.<\/em><\/p>\n<\/span>Step 2: Commit Changes with copy running-config startup-config<\/code><\/span><\/h3>\nExecute the standard Cisco command:<\/p>\n
Switch# copy running-config startup-config\nDestination filename [startup-config]? \nBuilding configuration...\n[OK]\nSwitch#\n<\/code><\/pre>\nWhen prompted for the Destination filename [startup-config]?<\/code>, press Enter<\/strong> to accept the default file destination. Once [OK]<\/code> appears, the configuration is written to NVRAM.<\/p>\n<\/span>Step 3: Alternative Shortcut (write memory<\/code>)<\/span><\/h3>\nYou can also use the traditional shorthand command:<\/p>\n
Switch# write memory\nBuilding configuration...\n[OK]\nSwitch#\n<\/code><\/pre>\nOr simply:<\/p>\n
Switch# wr\n<\/code><\/pre>\nThis performs the identical action without prompting to confirm the destination filename.<\/p>\n
<\/span>Step 4: Verify the Saved Configuration<\/span><\/h3>\nTo confirm that your changes are written to persistent storage, inspect the file stored in NVRAM:<\/p>\n
Switch# show startup-config\n<\/code><\/pre>\nCompare this output with show running-config<\/code> to verify parity between live operations and persistent storage.<\/p>\n
\n<\/span>Comparison: copy running-config startup-config<\/code> vs. write memory<\/code><\/span><\/h2>\nNetwork engineers frequently debate whether to use the full copy<\/code> syntax or the legacy write<\/code> shortcut. The following table highlights the functional and operational differences between both methods.<\/p>\n\n\n\n| Evaluation Criteria<\/th>\n | copy running-config startup-config<\/code> (copy run start<\/code>)<\/th>\nwrite memory<\/code> (wr<\/code>)<\/th>\n<\/tr>\n<\/thead>\n\n\nCommand Syntax<\/strong><\/td>\nUniversal Cisco file copy model (copy source destination<\/code>)<\/td>\n| Legacy standalone command<\/td>\n<\/tr>\n | \nConfirmation Prompt<\/strong><\/td>\nPrompts for destination file name ([startup-config]?<\/code>)<\/td>\n| Executes immediately without prompts<\/td>\n<\/tr>\n | \nIOS \/ IOS-XE Support<\/strong><\/td>\n| Fully supported across all versions<\/td>\n | Supported across all standard Catalyst IOS\/IOS-XE platforms<\/td>\n<\/tr>\n | \nNX-OS Compatibility<\/strong><\/td>\n| Supported natively<\/td>\n | Requires CLI alias (cli alias name wr copy run start<\/code>)<\/td>\n<\/tr>\n\nScripting & Automation<\/strong><\/td>\n| Requires carriage return handling in expect\/push scripts<\/td>\n | Highly script-friendly due to non-interactive execution<\/td>\n<\/tr>\n | \nCisco Exam Standards<\/strong><\/td>\n| Primary standard evaluated in CCNA\/CCNP exams<\/td>\n | Often accepted in simulation, but non-canonical in official theory<\/td>\n<\/tr>\n | \nTarget Flexibility<\/strong><\/td>\nCan copy to remote targets (tftp:<\/code>, ftp:<\/code>, flash:<\/code>)<\/td>\nHardcoded to copy running-config<\/code> to NVRAM only<\/td>\n<\/tr>\n\nDeprecation Status<\/strong><\/td>\n| Modern, officially maintained syntax standard<\/td>\n | Marked legacy in standard Cisco references, yet maintained for usability<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n<\/span>Automated Backups: Cisco IOS Archive and Remote Offloading<\/span><\/h2>\nSaving to NVRAM protects your configuration against reboots, but it does not protect against physical switch failure or chassis replacement. Using the native Cisco IOS archive<\/code> feature allows you to automatically save date-stamped backup files locally and offload them to an external TFTP, FTP, or SCP server whenever an administrator executes a save command.<\/p>\n<\/span>Configuration Template<\/span><\/h3>\n! Enter global configuration mode\nconfigure terminal\n\n! Enter the archive configuration submode\narchive\n\n ! Specify the storage destination path (TFTP, FTP, or Flash)\n ! Use $h for hostname and $t for timestamp variables\n path tftp:\/\/192.168.10.50\/backups\/$h-config-\n\n ! Automatically trigger an archive upload whenever 'write memory' or 'copy run start' is run\n write-memory\n\n ! Automatically archive the configuration on a recurring schedule (value in minutes: 1440 = 24 hours)\n time-period 1440\n\n ! Retain a maximum number of local archive files (1-14)\n maximum 14\n\nexit\n<\/code><\/pre>\n<\/span>Manual Trigger and Verification<\/span><\/h3>\nTo manually generate an archive file without modifying the schedule:<\/p>\n Switch# archive config\n<\/code><\/pre>\nTo display existing archived copies:<\/p>\n Switch# show archive\nThe maximum archive configurations allowed is 14.\nThe next archive file will be named tftp:\/\/192.168.10.50\/backups\/Switch-config--1\nArchive # Name\n 1 tftp:\/\/192.168.10.50\/backups\/Switch-config--Nov-03-2026-00-15-0\n 2 tftp:\/\/192.168.10.50\/backups\/Switch-config--Nov-03-2026-08-30-1 <- Most Recent\n<\/code><\/pre>\n
\n<\/span>Troubleshooting: Switch Loses Configuration After Reload<\/span><\/h2>\nIf a switch reverts to default factory settings or an empty configuration prompt after rebooting\u2014despite running copy run start<\/code>\u2014the device is failing to read the startup-config<\/code> from NVRAM.<\/p>\n<\/span>FAQ: Diagnosing and Fixing Reload Configuration Loss<\/span><\/h3>\nWhy does the switch boot with a blank configuration even after saving?<\/h4>\nThis condition occurs when the device bootloader is instructed to bypass NVRAM during startup. On routers and select switches, this is governed by the configuration register<\/strong>. On modular Catalyst switches running IOS-XE, it is typically governed by a ROMmon environment variable (SWITCH_IGNORE_STARTUP_CFG<\/code>).<\/p>\nHow do I check the Configuration Register on standard switches?<\/h4>\nRun the show version<\/code> command and inspect the final line of output:<\/p>\nSwitch# show version\n...\nConfiguration register is 0x2142\n<\/code><\/pre>\n\n0x2102<\/code> (Normal):<\/strong> The switch loads the startup configuration from NVRAM during boot.<\/li>\n0x2142<\/code> (Bypass Mode):<\/strong> Used during password recovery. The switch ignores NVRAM contents and starts with an empty configuration.<\/li>\n<\/ul>\nHow do I reset the Configuration Register back to normal?<\/h4>\nIf your switch displays 0x2142<\/code>, restore default boot behavior from global configuration mode:<\/p>\nSwitch# configure terminal\nSwitch(config)# config-register 0x2102\nSwitch(config)# exit\nSwitch# copy running-config startup-config\nSwitch# reload\n<\/code><\/pre>\nWhat if config-register<\/code> is not supported on my Catalyst switch?<\/h4>\nCatalyst switches (such as the Catalyst 2960, 3560, 3850, and 9000 series) handle NVRAM bypass directly via ROMmon environment settings. Check if startup config ignoring is active:<\/p>\n Switch# show boot\n...\nManual Boot: NO\nEnable Break: NO\nIgnore Startup-Config: YES\n<\/code><\/pre>\nIf Ignore Startup-Config<\/code> is enabled, disable it using:<\/p>\nSwitch# configure terminal\nSwitch(config)# no system ignore startupconfig\nSwitch(config)# exit\nSwitch# write memory\n<\/code><\/pre>\nIf configuration issues persist from a previous password recovery, access the bootloader (ROMmon) via console during startup and verify that the variable is cleared:<\/p>\n switch: unset SWITCH_IGNORE_STARTUP_CFG\nswitch: boot\n<\/code><\/pre>\n
\n<\/span>Official Cisco Documentation and Technical Standards<\/span><\/h2>\nCisco Systems details configuration management and command hierarchies within the Cisco IOS \/ IOS-XE Software Configuration Guides: System Management<\/em>.<\/p>\n<\/span>Canonical Command Syntax Reference<\/span><\/h3>\nAccording to Cisco\u2019s official command references, the primary command is defined as:<\/p>\n copy system:\/running-config nvram:\/startup-config\n<\/code><\/pre>\n\nsystem:\/running-config<\/code><\/strong>: The absolute file-system URI representing active RAM.<\/li>\nnvram:\/startup-config<\/code><\/strong>: The target file-system URI representing NVRAM.<\/li>\n<\/ul>\nThe standard syntax copy running-config startup-config<\/code> is an alias to this absolute path specification.<\/p>\n<\/span>Navigating Official Technical Resources<\/span><\/h3>\nFor product-specific variations and command trees:
\n1. Navigate to Cisco.com > Support & Downloads > Product Support<\/strong>.
\n2. Select your switch family (e.g., Cisco Catalyst 9200 \/ 9300 \/ 9500 Series Switches<\/em>).
\n3. Access Configure > Configuration Guides<\/strong>.
\n4. Open the System Management Configuration Guide<\/strong> for your active IOS-XE release and locate the section titled Managing Configuration Files<\/strong>.<\/p>\n
\nCommitting configuration changes to NVRAM using copy running-config startup-config<\/code> or
| | | | | | | | | | | | | | | |