Ever bought a used router, plugged it in, and watched it boot up like it already knew your name? That little bit of memory doing the remembering is probably NVRAM. And if you've ever sat in a Cisco exam or scrolled through a forum thread asking "what are two functions of nvram choose two," you know the answers matter more than people admit Worth knowing..
Real talk — this step gets skipped all the time.
Here's the thing — most folks treat NVRAM like a black box. It just sits there. But when it fails, or when you don't understand what it's holding onto, that's when networks go sideways.
I've reset more devices than I care to count. And every time, the question of what NVRAM actually does comes back around.
What Is NVRAM
NVRAM stands for non-volatile random-access memory. Think about it: say that three times fast. The short version is: it's memory that doesn't forget when you pull the power. Which means regular RAM? Gone the second the lights go out. On the flip side, nVRAM? It keeps its contents like a stubborn notebook Still holds up..
In routers and switches, especially Cisco gear, NVRAM is the quiet storage spot that holds the stuff the device needs to come back to life the right way. That's why it's not the operating system — that lives in flash. It's not the running config — that's in RAM while the box is up. NVRAM is the landing pad for the startup configuration and a few other critical bits Easy to understand, harder to ignore..
The Startup Configuration Lives Here
When you type copy running-config startup-config, you're writing to NVRAM. That startup-config is the blueprint the device loads on boot. In real terms, no NVRAM, no saved config. Even so, you'd be reconfiguring from scratch every single reboot. Nobody wants that Turns out it matters..
It Tracks the Configuration Register
There's a small setting called the configuration register — that's also kept in NVRAM. Now, it tells the router how to boot, whether to load the saved config, or whether to drop into ROMMON mode if something's broken. Plus, most people never touch it. But when you do a password recovery, you're messing with this value, and it's stored right there.
Why It Matters
Why does this matter? Because most people skip it until something breaks.
Picture a branch office router. Power flickers. Device reboots. Think about it: if NVRAM is healthy, it pulls the startup config and the network's back in thirty seconds. If that memory is corrupted — or someone never saved the config — you're staring at a factory-default prompt while the whole office complains the Wi-Fi is down.
And in the cert world, knowing the two functions of NVRAM is a classic trap question. The prompt "what are two functions of nvram choose two" shows up because people confuse NVRAM with flash or RAM. Flash holds the IOS image. Still, rAM holds the running config and routing tables. NVRAM? Because of that, it holds the startup config and the config register. Miss that distinction and you'll fail the question — and maybe misdiagnose a real outage later No workaround needed..
Turns out, understanding this tiny slice of memory makes you faster at troubleshooting. You stop blaming the ISP when the problem is a missing startup-config.
How It Works
So how does NVRAM actually do its job? Let's break it down without getting lost in silicon Simple, but easy to overlook..
Storing the Startup Configuration
When the device is running, your active settings live in RAM as the running-config. On boot, the bootstrap code reads the startup-config from NVRAM and loads it into RAM. Worth adding: that's volatile. The moment you reboot, it's wiped. NVRAM is where you send a copy to survive the power loss. Boom — running-config restored The details matter here..
In practice, this is why the command write memory (or wr) is still typed by old-timers. It's the same as copying running to startup. You're etching the config into non-volatile space Most people skip this — try not to..
Holding the Configuration Register
The config register is a 16-bit value. Change it to 0x2142 and the router ignores the startup-config on boot, which is how you break into a locked device. On Cisco routers, 0x2102 is the normal one — boot from flash, load NVRAM config. That value is stored in NVRAM and read before anything else happens.
It's a tiny thing, but it controls the whole boot personality of the box.
How It Stays Non-Volatile
Early NVRAM was battery-backed SRAM. A small coin cell kept the data alive. Later designs used flash-like memory that didn't need a battery. Worth adding: either way, the goal is the same: retain data with no power. Which means the capacity is small — we're talking kilobytes, not gigabytes. Which means it doesn't need to be big. Just enough for a text config and a register Easy to understand, harder to ignore..
Not obvious, but once you see it — you'll see it everywhere.
What Happens on Boot
Power on. If the register says "ignore," it skips that step. POST runs. Bootstrap loads. It checks the config register in NVRAM. Practically speaking, then it grabs the startup-config from NVRAM and pushes it to RAM. Then the IOS image (from flash) takes over with the config it found — or didn't.
That sequence is why NVRAM sits in the critical path of every single boot Small thing, real impact..
Common Mistakes
Here's what most people get wrong. And honestly, this is the part most guides get wrong too.
They say NVRAM "stores the IOS." No. That's flash. NVRAM is too small for an image. If you're studying for a test and someone tells you NVRAM holds the operating system, walk away.
Another mistake: thinking RAM and NVRAM are interchangeable because both hold configs. NVRAM holds the saved one. Still, rAM holds the running one. Still, if you change a setting and don't save, a reboot throws it away. I know it sounds simple — but it's easy to miss during a late-night change window Easy to understand, harder to ignore..
And the big one tied to the exam question: when asked "what are two functions of nvram choose two," people pick "stores running config" and "stores IOS.The right two are: stores startup configuration and stores the configuration register. Here's the thing — " Both wrong. That's it.
Some also forget NVRAM can be erased. Still, erase nvram: or write erase wipes the startup config. Do that on a live box and you've got a paperweight until you rebuild.
Practical Tips
What actually works when you're dealing with NVRAM day to day?
Save often. After any config change, copy run start. Don't trust yourself to remember. I've been burned by a reboot before the save. Never again Still holds up..
Verify the register. Before a reboot during maintenance, do show version and check the last line for the config register. If it's not 0x2102, figure out why. A wrong register means your saved config might not load.
Back up startup-config off-box. NVRAM is reliable, but it's not immortal. Pull the config to a TFTP server or a USB stick. When the device dies, you'll care a lot less about the chip and a lot more about the text file you saved.
Don't confuse your memories. Flash = IOS. RAM = running state. NVRAM = startup config + register. Say it like a mantra. It'll keep you sane on exams and on consoles.
Use ROMMON as a safety net. If NVRAM's startup config is corrupted, the router often boots to a default state or ROMMON. That's not the end. You can recover. But you need to know the register trick — which lives in NVRAM — to get there.
FAQ
What are two functions of NVRAM choose two? The two correct functions are: it stores the startup configuration, and it stores the configuration register. It does not store the IOS image or the running configuration It's one of those things that adds up. Surprisingly effective..
Is NVRAM the same as flash memory? No. Flash holds the operating system image and is much larger. NVRAM is small and holds the startup config and boot settings. Flash is also non-volatile, but they serve different jobs Worth keeping that in mind..
Can you clear NVRAM without deleting the IOS?
Yes. Commands like write erase or erase nvram: remove the startup config but leave the IOS in flash untouched. The device will boot, just with no saved settings Practical, not theoretical..
Why is my router ignoring my saved config? Check the configuration register. If it
is set to bypass the startup-config (for example, 0x2142), the router loads with factory defaults even though your NVRAM still holds the saved file. Change it back to 0x2102 and reload That's the part that actually makes a difference..
How do I confirm what's actually in NVRAM?
Run show startup-config to view the saved config, or show version to see the configuration register at the bottom. If the startup-config is empty, the device will tell you it's not present.
In short, NVRAM is a small but critical piece of every Cisco device. Treat it with respect: save your work, verify your register, and keep an off-box backup. It quietly holds the startup configuration and the configuration register — nothing more, nothing less. Master those habits and the "what are two functions of NVRAM choose two" question becomes trivial, while your production gear stays one reboot away from a clean recovery instead of a crisis.
The official docs gloss over this. That's a mistake.
