What Does Startup Configuration Mean?
On This Page
Quick Definition
Think of startup configuration as the device's permanent settings that it remembers even when the power is off. When you turn on a router or switch, it reads this file to apply all your custom settings like IP addresses and security rules. Unlike running configuration, which is the current active config, startup configuration lives in non-volatile memory so it doesn't disappear on reboot.
Commonly Confused With
Running configuration is the active configuration in RAM that the device is currently using. Startup configuration is the saved version in NVRAM that loads on boot. The key difference is persistence: running config is volatile, startup config is non-volatile.
If you change an IP address on an interface, it changes in running config immediately. If you do not save, that change is gone after a reload. Saving copies running config to startup config.
NVRAM is the memory chip that stores the startup configuration. It is not the configuration itself. The startup configuration is the data file stored inside NVRAM. You manage the file through commands like 'show startup-config' and 'copy running-config startup-config', not by directly manipulating NVRAM.
NVRAM is like a filing cabinet. The startup configuration is the document inside the cabinet. You open the cabinet (NVRAM) to read or write the document, but they are not the same thing.
The configuration register is a 16-bit software register that controls boot options, such as whether to load the startup configuration. It is not a configuration file. The startup configuration is the actual set of commands to be applied. Changing the register to 0x2142 does not erase or alter the startup configuration; it only tells IOS to skip loading it.
Think of the configuration register as a switch on a machine that says 'ignore saved settings'. The startup configuration is the saved settings file. Throwing the switch does not erase the file, it just bypasses it.
Must Know for Exams
The topic of startup configuration is a staple in the CCNA exam, appearing in multiple domains including Network Fundamentals, Network Access, and IP Connectivity. Cisco explicitly lists configuration file management as an exam objective, asking candidates to distinguish between running config and startup config, and to know the commands to manage them. On the CCNA 200-301 exam, you can expect questions that test your understanding of the boot sequence, the copy command, and the behavior when no startup configuration exists. These questions may be multiple-choice, drag-and-drop, or part of a simulated lab environment using Packet Tracer.
Beyond CCNA, startup configuration is also relevant to the CCNP Enterprise ENCOR (350-401) exam, though it appears more as background knowledge than a core topic. In CCNP, the focus shifts to more advanced configuration management, such as using configuration replace, rollback, and automated provisioning with tools like Ansible. However, the foundational concept of startup vs. running config remains essential. For the CCNA Security exam (though it is now part of the core CCNP Security track), understanding startup configuration is important because security features like ACLs and AAA configurations must survive reboots.
Question types you will encounter include: scenario-based questions where a technician makes changes and the device is reloaded, requiring the candidate to identify what settings will be present after reboot. Another common question is a configuration output interpretation where you are shown a 'show startup-config' output and asked to identify a specific setting like the enable password or the IP address of an interface. There are also troubleshooting questions where a router boots without its intended configuration, and you must determine the cause, often related to a configuration register setting or a missing startup config file. Additionally, the CCNA exam frequently tests the exact syntax of the 'copy running-config startup-config' command, including the option to copy to 'startup-config' or 'nvram:startup-config'. Knowing that 'write memory' is a deprecated but widely accepted alternative is also helpful. Because startup configuration is such a basic and essential component of Cisco IOS, exam designers can easily embed it into broader troubleshooting or configuration scenarios, so mastering this concept gives you a strong foundation for tackling more complex topics.
Simple Meaning
Imagine you are setting up a new coffee maker for the first time. You program it to start brewing at 6 AM, use a certain water temperature, and keep a timer for two hours. These settings are like the startup configuration of the machine. Every morning when the power comes back on, the coffee maker remembers those exact settings without you having to re-enter them. In the world of Cisco networking, a router or switch needs a similar kind of memory so it knows how to work immediately when it boots up.
The startup configuration is stored inside the device's NVRAM, which stands for non-volatile random-access memory. NVRAM is special because it keeps its data even after you unplug the device. This is different from the RAM that holds the running configuration, which disappears as soon as the power goes out. The startup configuration contains all the essential commands that define the device's identity, like its hostname, configured IP addresses on interfaces, routing protocols, security settings, and network policies.
When a Cisco device boots up, it first loads the operating system and then looks for the startup configuration. If it finds one, it copies the entire file into the running memory and applies those commands. This process is automatic and happens every single time the device starts. If no startup configuration exists, the device will boot with a default, minimal configuration, which usually means all interfaces are shut down and no passwords are set. That can be a security risk if the device is connected to a live network.
For IT professionals, managing the startup configuration is a daily task. When you make changes to a device, those changes only affect the running configuration. To save them so they survive a restart, you must run the command 'copy running-config startup-config'. If you forget to do that, all your work is lost the next time someone hits the power button. This one-step process is the single most important habit for any network engineer, especially those studying for the CCNA exam.
Full Technical Definition
Startup configuration is a text-based file stored in NVRAM (non-volatile random-access memory) that contains the saved configuration commands for a Cisco IOS device. It is one of two primary configuration files used in Cisco networking, the other being the running configuration stored in volatile DRAM. When a device is powered on or reloaded, the boot sequence first initializes the hardware and loads the IOS image. Next, the device checks for a valid startup configuration in NVRAM. If it exists, the system copies the entire startup configuration into the running configuration in RAM and applies those commands sequentially. If no startup configuration is found, the device enters setup mode, a legacy interactive dialog that prompts the user for basic settings, or it boots with a default configuration that leaves interfaces administratively down.
The format of startup configuration is a plain-text file made up of Cisco IOS commands, one per line, structurally similar to the running configuration. It includes global commands like 'hostname', 'enable secret', and 'ip route', as well as interface-specific commands such as 'ip address' and 'no shutdown'. The file is saved automatically when you issue 'write memory' or 'copy running-config startup-config'. On newer platforms, the command 'write' is also accepted. The startup configuration can be viewed using 'show startup-config' (or 'show config' on some older platforms) and can be deleted with 'erase startup-config', which resets the device to factory defaults upon the next reload.
The role of startup configuration in network management is critical. It enables consistency across reboots, simplifies disaster recovery, and allows network engineers to pre-stage devices. For example, a technician can create a configuration file offline and copy it into NVRAM via TFTP, USB, or SCP before deploying the device. This minimizes downtime and configuration drift. In exam contexts such as the CCNA (Cisco Certified Network Associate), candidates must understand the relationship between startup and running configurations, the commands to manage them, and the default boot behavior when the file is missing. Questions often require the candidate to identify the correct command to save a configuration, interpret the output of 'show startup-config', or troubleshoot a device that loses settings after a reboot. Mastery of this concept also involves understanding that the startup configuration is not the only determinant of device behavior during boot; the configuration register, typically set to 0x2102, tells IOS to load the startup configuration automatically. Changing the configuration register to 0x2142 instructs the device to ignore the startup configuration, which is a common password recovery technique. Overall, startup configuration is one of the foundational building blocks of reliable network operations and is a tested concept on all Cisco certifications.
Real-Life Example
Think of startup configuration like the saved settings on a smart thermostat in your home. You spend a Sunday afternoon programming your thermostat: you set the wake-up temperature to 68 degrees at 7 AM, the daytime temperature to 72 degrees, and a cooler 65 degrees at night. You also set it to turn off the heat when you are away on vacation. All these settings are saved into the thermostat's memory. Now, imagine a power outage. The lights go out, the refrigerator hums to a stop, and your smart thermostat goes blank. When power is restored, your coffee maker might need to be reprogrammed, but your thermostat? It remembers everything. It comes back on, shows 72 degrees, and goes right back to your schedule. That is exactly how startup configuration works for a Cisco router.
In this analogy, your thermostat's permanent memory is NVRAM. It holds your preferences even without electricity. The thermostat's active state right now, showing the current temperature and what it is doing at this moment, is like the running configuration. If you walk over to the thermostat and change the temperature manually, that change only affects the current state. But if you don't save that change using the thermostat's menu, the next time the thermostat reboots (maybe after a firmware update), it will revert to your Sunday afternoon settings. The smartphone app that lets you set schedules is like the command line interface where you type 'copy running-config startup-config' to save your work.
Now, what if you accidentally delete all your thermostat schedules? The thermostat might go to some default behavior, perhaps running at a fixed 70 degrees all day. In networking terms, that is like erasing the startup configuration. The device boots with minimal settings, and all the custom interface IPs, routing protocols, and security filters are gone. The thermostat analogy breaks down a bit because a router is far more complex, but the core idea is the same: the saved settings are what make the device useful every single day, and forgetting to save them leads to frustration and lost time.
Why This Term Matters
Startup configuration matters for anyone managing network devices because it directly impacts network uptime, security, and consistency. In a real-world IT environment, routers and switches are not just turned on once and forgotten. They undergo planned maintenance, firmware upgrades, power outages, and occasional crashes. Without a properly saved startup configuration, every one of those events would force a network engineer to manually reconfigure the device from scratch. For a large enterprise with hundreds of devices, that kind of manual work is impossible. The startup configuration ensures that after a simple reload, every interface is back up, every routing neighbor relationship is restored, and every security ACL is in place.
Another critical aspect is change management. When a network engineer makes a mistake during a maintenance window, the ability to reload the device and revert to the known-good startup configuration can save the network from extended downtime. It acts as a restore point. In contrast, if the running configuration is accidentally saved over the startup configuration with a bad config, the engineer could lose that fallback. That is why many professionals keep a backup copy of the startup configuration on an external server, often using TFTP, FTP, or SCP. This practice is a fundamental part of network documentation and disaster recovery planning.
From a security standpoint, the startup configuration often contains sensitive data such as enable passwords (though these can be encrypted with 'service password-encryption' or 'enable secret'), SNMP community strings, and VPN pre-shared keys. If an attacker gains access to the startup configuration file, they can learn the network topology and compromise the entire infrastructure. That is why access to NVRAM and the ability to view or copy the startup configuration should be tightly controlled via privilege levels and authentication. For CCNA candidates, understanding that the startup configuration is the source of truth for the device's persistent state is essential. It is a simple concept, but its implications for network stability, security, and recovery are enormous.
How It Appears in Exam Questions
On the CCNA exam, questions about startup configuration show up primarily in three forms: direct knowledge questions, scenario-based troubleshooting, and output interpretation. In direct knowledge questions, you will be asked something like, 'Which command saves the running configuration to the startup configuration?' The answer options might include 'copy startup-config running-config', 'copy running-config startup-config', 'write erase', or 'reload'. The correct answer is obviously 'copy running-config startup-config', but Cisco often throws in command variations like 'copy run start' as a valid shortcut. Another direct question might ask: 'What memory type holds the startup configuration?' The answer is NVRAM. These questions are straightforward but require memorization of exact command syntax and memory types.
Scenario-based questions are more challenging. For example: 'A network engineer configures a new VLAN interface on a switch and assigns an IP address. The engineer wants the configuration to persist after the next power cycle. What step must be taken?' The correct answer is to save the configuration using 'copy running-config startup-config'. A trickier scenario might involve a password recovery procedure: 'You have lost the enable password to a router. You change the configuration register to 0x2142 and reload the device. What is the state of the startup configuration after reload?' The correct answer is that the startup configuration is ignored during boot, but it still exists in NVRAM. The candidate must understand that changing the register does not erase the file, only prevents it from being loaded.
Output interpretation questions give you a partial or full 'show startup-config' output. For instance, you might see an interface configured with 'ip address 192.168.1.1 255.255.255.0' and 'shutdown'. The question asks: 'After a reload, what is the state of the interface?' Since 'shutdown' is in the startup config, the interface will be administratively down. Another common output pattern is when the startup config is empty or missing. The 'show startup-config' command might return '%% Non-volatile configuration memory is not present' or simply show nothing. The question then asks what the device will do on reload. The correct answer is that it will enter the setup dialog or boot with default settings. Understanding these patterns will help you quickly eliminate wrong answers and locate the key detail in the output.
Practise Startup Configuration Questions
Test your understanding with exam-style practice questions.
Example Scenario
You are the new junior network administrator at a small company. The company has a single Cisco router that connects the office to the internet. The senior admin tells you to add a new static route so traffic to a remote branch office goes through a specific next-hop IP address.
You log into the router, enter global configuration mode, and type: 'ip route 192.168.10.0 255.255.255.0 172.16.1.2'. You verify the route is in the routing table with 'show ip route' and everything looks good.
You close your session and go home. The next morning, the senior admin calls you in a panic. The remote branch cannot reach the main office. The router was accidentally unplugged by the cleaning crew the night before.
When it came back up, all your changes were gone. The static route you added is nowhere to be found. You check the routing table and see only directly connected networks. The senior admin asks, 'What did you forget to do?'
At this point, you realize your mistake. You had added the route only to the running configuration. It was working perfectly as long as the router stayed up, but it was never saved to the startup configuration.
When the router lost power and reloaded, it loaded the old startup config from NVRAM, which did not include your static route. The company lost connectivity to the branch office for several hours because you missed one simple but critical step. To fix it, you re-enter the route, then immediately run 'copy running-config startup-config' and confirm the overwrite.
You also verify with 'show startup-config | include ip route' to confirm the route is now saved. This situation is a classic beginner mistake, and it is exactly the kind of scenario that CCNA exam questions use to test your understanding of startup configuration. It shows that knowing the commands is not enough; you must also know when to use them and what happens if you do not.
Common Mistakes
Thinking that typing a command instantly saves it permanently
Any configuration change made in the CLI affects only the running configuration in DRAM, not the startup configuration in NVRAM. Until you specifically issue the save command, the change will be lost on reload.
Always save your changes after making them. Get into the habit of running 'copy running-config startup-config' or 'write memory' at the end of every configuration session.
Confusing the direction of the copy command
Many beginners remember the 'copy' command but mix up the source and destination. They type 'copy startup-config running-config' when they intended to save their work. That command reverses the direction and overwrites the current active config with the old saved config, undoing all recent changes.
Remember the phrase 'run to start' for saving, and 'start to run' for restoring. The command 'copy running-config startup-config' saves your current work. The command 'copy startup-config running-config' restores an old config.
Believing the 'reload' command automatically saves the running configuration
When you issue the 'reload' command, the router will prompt you to save the configuration. If you answer 'yes' or 'y', it will save. But if you answer 'no' or 'n', or if you automate the reload via a script, changes are lost. The reload command does not save the configuration by itself.
Always explicitly save your configuration before issuing a reload, or set your automation scripts to include a save step. Do not rely on the interactive prompt.
Assuming 'erase startup-config' only clears the running config
The 'erase startup-config' command specifically deletes the contents of NVRAM, i.e., the startup configuration. It does not affect the running configuration. After erasing, the device continues to work with the current running config until the next reload. This can be confusing because the running config still exists but the fallback is gone.
Understand the difference: 'erase startup-config' removes the file that is loaded at boot. The running config stays intact. If you want to factory reset, you must erase startup config and reload.
Confusing the configuration register function with startup config
Some learners think that changing the configuration register to 0x2142 also erases the startup configuration. It does not. It only tells the device to skip loading the startup config during boot. The file remains in NVRAM and can be recovered later.
Remember that the configuration register controls boot behavior, not file storage. Use 'show version' to check the register value and 'config-register' to change it. The startup config is a separate entity.
Exam Trap — Don't Get Fooled
{"trap":"The exam presents a scenario: 'A network engineer configures a router with new OSPF settings. After testing, the engineer types 'copy running-config startup-config' and then issues 'reload'. After reload, the OSPF settings are missing.
Why?'","why_learners_choose_it":"The learner assumes the copy command was typed correctly, but they may have accidentally typed 'copy startup-config running-config' or they may have had a typo. Another trap is that the learner thinks the save command was not necessary because they believe changes are automatically saved on reload in some circumstances."
,"how_to_avoid_it":"Read the question carefully. Verify the exact command syntax used in the scenario. If the command was 'copy running-config startup-config', the config should be persistent.
The most likely cause of missing config is either that the command was applied to the wrong file, or that the configuration register was set to ignore startup config. Always check for the configuration register value and ensure the command was correct."
Step-by-Step Breakdown
Device Power-On
When a Cisco router or switch is first powered on, the device performs a power-on self-test (POST) to verify hardware functionality. The system then loads the bootstrap code stored in ROM, which initializes the CPU and memory.
Locate and Load IOS Image
The system looks for an IOS image file. The location of the IOS image is determined by the boot system commands in the startup configuration (if present) or the value of the configuration register. Typically, IOS is loaded from flash memory into RAM.
Look for Startup Configuration
After IOS is running, the device checks NVRAM for the presence of a startup configuration file. The configuration register value is examined. If the register is set to a normal value like 0x2102 (default), the device proceeds to load the startup config.
Load and Apply Startup Configuration
If a valid startup configuration exists, the entire file is copied into the running configuration in RAM. The commands are executed sequentially, configuring interfaces, routing protocols, security settings, and any other parameters. The device becomes fully operational with the saved settings.
Enter User CLI Prompt
Once all startup configuration commands are applied, the system presents the user with a command-line interface prompt. The device is now ready for administrative access and network traffic. If the startup configuration included a 'banner' or 'hostname', those are visible at this point.
User Makes Changes
When a network engineer logs in and makes configuration changes, those changes are made directly to the running configuration in RAM. They take effect immediately but are not persistent.
Save Changes to Startup Configuration
To make changes permanent, the engineer must explicitly copy the running configuration to the startup configuration using 'copy running-config startup-config' or 'write memory'. This overwrites the previous startup configuration file in NVRAM with the current running configuration.
Practical Mini-Lesson
In real-world network operations, managing the startup configuration is a daily task that goes far beyond just remembering the 'copy run start' command. For professionals, the workflow typically involves several layers of discipline. First, always keep a backup of the startup configuration off the device. This could be on a TFTP server, a USB drive attached to the device, or a central configuration management system like SolarWinds or ManageEngine. The reason is simple: if the NVRAM chip fails and your startup config is corrupted, you lose the entire device configuration. A backup allows you to quickly restore by copying the file back via 'copy tftp startup-config'.
Second, understanding the difference between 'copy running-config startup-config' and 'write memory' is important because some older IOS versions treat them differently. In most modern IOS, they are functionally identical. However, 'write memory' is a legacy command that still works everywhere. On newer IOS-XE devices, 'copy running-config startup-config' is the recommended method. The command 'write' alone also works on some platforms. Professionals should know all three to be comfortable on any Cisco device.
Third, there is the concept of configuration archival. Many organizations configure their devices to automatically save the startup configuration to a remote server at regular intervals, or to create a versioned backup every time a configuration change is made. This is part of a broader change management process. If a change causes a problem, you can quickly revert to a known good startup configuration from a specific date and time. On the CLI, you can use the 'archive' command to automate this, including setting a path and a maximum number of backup files.
What can go wrong? One common issue is running out of space in NVRAM. Although NVRAM is small (usually between 128 KB and 1 MB on older platforms), a large startup configuration with many ACLs, routes, and interface commands can fill it up. If that happens, the 'copy running-config startup-config' command will fail with an error like '%% Error: Not enough space on device'. The solution is to review the configuration and trim unnecessary lines, or upgrade to a device with larger NVRAM. Another issue is that the startup configuration can become corrupt due to a power failure during a write operation. That is why it is a good practice to verify the startup configuration after saving by using 'show startup-config' and checking for any malformed output or missing lines. If corruption is detected, you must restore from a backup immediately.
Finally, professionals use the startup configuration as a diagnostic tool. If a device is behaving strangely after a reboot, the first step is to compare the startup config to the running config. The command 'show startup-config | include hostname' and 'show running-config | include hostname' can quickly reveal if the correct hostname is set. A mismatch between the two might indicate that someone changed the running config but did not save it, or that a previous config was accidentally overwritten. This comparison is a fundamental troubleshooting skill for any CCNA-level engineer.
Memory Tip
Remember: 'Run to Start' for save, 'Start to Run' for restore. If you run to start, you save the day. If you start to run, you restore yesterday.
Covered in These Exams
Current Exam Context
Current exam versions that test this topic — use these objectives when studying.
200-301Cisco CCNA →Related Glossary Terms
802.1Q is the networking standard that allows multiple virtual LANs (VLANs) to share a single physical network link by tagging Ethernet frames with VLAN identification information.
802.1X is a network access control standard that authenticates devices before they are allowed to connect to a wired or wireless network.
An A record is a DNS record that maps a domain name to the IPv4 address of the server hosting that domain.
Two-factor authentication (2FA) is a security method that requires two different types of proof before granting access to an account or system.
5G is the fifth generation of cellular network technology, designed to deliver faster speeds, lower latency, and support for many more connected devices than previous generations.
Frequently Asked Questions
What command saves the running configuration to the startup configuration?
Use 'copy running-config startup-config' or the legacy command 'write memory'. Both achieve the same result.
What happens if no startup configuration exists when a router boots?
The router will either enter an interactive setup dialog known as the System Configuration Dialog, or boot with a default minimal configuration where all interfaces are administratively down.
Is the startup configuration stored in RAM or NVRAM?
Startup configuration is stored in NVRAM (non-volatile RAM), which retains data even when the device is powered off.
Can I view the startup configuration without logging into the device?
No, you must log in via console, SSH, or other management access and use the 'show startup-config' command to view it.
How do I clear the startup configuration to reset a router to factory defaults?
Use 'erase startup-config' or 'write erase', then issue 'reload'. The device will reboot without a saved configuration.
What is the difference between 'copy running-config startup-config' and 'copy startup-config running-config'?
The first saves your current changes to permanent memory. The second overwrites your current running config with the old saved config, undoing any unsaved changes.
Does changing the configuration register affect the startup configuration?
No, it only changes boot behavior. Setting it to 0x2142 bypasses the loading of startup config but does not erase it.
Summary
Startup configuration is one of the simplest yet most important concepts in Cisco networking. It is the file stored in NVRAM that contains all the commands a device needs to operate correctly every time it boots. Without it, every power cycle would erase all your work, forcing you to reconfigure the device from scratch. The relationship between running config and startup config is straightforward: you work in the running config, and you save to startup config. The one command to remember is 'copy running-config startup-config', and the one habit to develop is using it every time you make a change.
For the CCNA exam, expect to see questions that test your knowledge of this relationship, the correct syntax, and the consequences of not saving. You must also understand the role of NVRAM and the configuration register. The exam will not ask you to remember every nuance, but it will expect you to distinguish between volatile and non-volatile memory, and to know what happens when a device boots without a startup configuration.
In professional practice, managing startup configuration goes beyond mere saving. It involves backing up, archiving, comparing, and sometimes restoring configuration files. It is a skill that separates a novice from a competent network engineer. By mastering this concept, you build a strong foundation for more advanced topics in network management and automation. It is not glamorous, but it is absolutely essential.