Why does the switch respond with startup config is not present

If you’re asking, “why does the switch respond with startup config is not present,” the usual answer is that no configuration has been saved in NVRAM. The switch may still have active settings in its running configuration, which resides in RAM, but no startup configuration file is available to load after the next boot.

Save the active configuration with copy running-config startup-config, or the abbreviated cop r s. After saving, show startup-config displays the NVRAM configuration, and the settings can persist through a restart or power-down.

Why Does the Switch Respond with Startup Config Is Not Present

Your active settings may still be operating as the running configuration in RAM, but they have not been written to the location used at startup. NVRAM holds the startup file, whereas RAM holds the current active configuration.

Save the active configuration. The command copies the RAM-based running configuration into the NVRAM startup configuration, making it available after a restart or power-down. Administrators may instead use cop r s, reported as the shortest abbreviation, or copy run start, another shortened save command. If you are in configuration mode, do copy running-config startup-config runs the save command without leaving that mode.

Once the copy command is issued, the switch prompts the user to save the startup configuration. Confirm the result with show startup-config, which displays the configuration held in NVRAM. That check addresses a Cisco switch configuration not saved concern by distinguishing active RAM settings from the saved file intended for boot.

In course material, show startup-configuration also appears as an alternate spelling for displaying NVRAM contents. That separation explains why both commands can produce different results at the same time on one switch during operation.

Meanwhile, show running-config, or sh run, displays the current configuration. Users on Network Engineering Stack Exchange report that a fresh IOS switch can show initial or default settings, such as an IOS version, hostname, and interface details, even while show startup-config reports no file. Their explanation describes IOS beginning with an initial settings state and applying a saved startup configuration to that state when one exists.

Unsaved changes can be lost if the switch is powered down, so saving matters whenever a configuration must survive a shutdown. For example, a configured IP address that is not saved is discarded after a reboot. Occasionally, the same message can be associated with a missing or corrupted file, accidental deletion, file-system corruption, incorrect boot settings, insufficient disk space, or rare storage-hardware failures. Those possibilities are troubleshooting considerations, rather than the usual explanation for a fresh switch or a configuration that has not yet been saved.

Running Config vs Startup Config

Running configuration and startup configuration are separate views of a switch’s settings. A Cisco switch can display settings through show running-config even when its startup-config is missing, because the active configuration resides in RAM rather than in the saved file.

If a startup configuration exists, IOS applies that file to the initial state as the switch boots. On a fresh IOS switch, ordinary show run can include automatically established details.

Later, commands entered by an administrator alter the running configuration immediately while the device remains powered. Those changes appear in show running-config, alongside applicable initial-state settings, but they are not automatically reflected in the startup configuration. Ordinary show run is a shortened form of show running-config; show run all provides a fuller view that includes default settings omitted from ordinary output.

What Each View Represents

Command or Configuration What It Shows or Does Configuration Location Boot Implication
show running-config Shows the current active configuration. RAM, including applicable IOS initial-state settings. Active changes can exist without being saved.
show startup-config Shows the saved startup configuration. NVRAM. Represents configuration available for boot.
show run all Shows the fuller configuration, including default settings. Running configuration and defaults. Provides a broader view, not a save action.
copy running-config startup-config Copies active settings into the startup configuration. From RAM to NVRAM. Retains the configuration for a later boot.

For a Cisco switch with a missing startup-config, visible running output does not by itself prove that a user-created configuration was saved. Instead, it can represent the IOS initial state, later live changes, or both. Posters on Network Engineering Stack Exchange say more system:/default-running-config displays the default configuration for the current IOS version, and caution that defaults can change between versions.

Its output can expose passwords in plain text. Avoid treating a populated running configuration as evidence that the same content will be present after a restart. Saved and active configurations may match only after an administrator uses the appropriate copy command to move the running configuration into the startup configuration.

Before making operational decisions, compare the two command outputs according to what each one is designed to show. Configuration details that appear only in RAM remain usable during the current session, while the saved view represents the configuration intended for a subsequent boot.

Recognizing that distinction prevents a Cisco switch configuration not saved from being confused with an empty or inactive running configuration. That comparison also separates defaults shown in running output from settings introduced by later user changes. Readers can then interpret displays according to their storage location and boot role.

How to Save the Active Configuration

Use the save command to preserve completed changes.

Enter the command after completing changes that must persist, such as a hostname, console access settings, passwords, an MOTD, or password encryption. From global configuration mode, prefix it with do. Doing so lets you save the configuration without first leaving configuration mode.

Save the Configuration

  1. Complete the active settings that need to persist.
  2. Run the save command.
  3. Alternatively, use it from configuration mode.
  4. Respond to the switch prompt to save the startup configuration.
  5. Inspect the saved contents with show startup-config after the copy.

This is the point at which active settings are copied for a later boot, rather than simply viewed on screen. Once the operation has completed, the saved file is intended to load when the switch starts.

Confirming the copy matters because it prevents a Cisco switch configuration not saved from being discarded at the next reboot. Afterward, show startup-config is the Cisco command used to display the contents held in NVRAM.

Its output should reflect the configuration chosen for preservation. Review it to check that the expected settings were included. For a straightforward check, compare the displayed saved entries with the changes you intended to retain.

Abbreviated forms are accepted in the supplied command examples. copy run start is another shortened save command. Choose the full command when clarity is preferable, especially while learning the sequence or documenting a change. Either form performs the same copy from the active configuration to the startup configuration. Avoid assuming that merely entering settings completes the process; the save command writes the startup configuration.

Sensitive values deserve care during configuration review because passwords may appear in plain text. Password protection can be configured with service password-encryption, which encrypts current and future passwords on the switch. Enable secret and enable password values can display differently. Use care when handling configuration output that contains those values.

How to Check the Saved Configuration

Compare its output with show running-config, or sh run, to distinguish the saved file from the switch’s settings. If the startup file is absent, the command reports startup-config is not present. Both commands are display commands, so each serves as an inspection point rather than a configuration change.

Compare Saved and Active Settings

Reading both outputs after a change provides a direct check of what is active and what has been retained for a later boot. For example, a hostname configured on the switch appears among settings, while the saved output shows the version held in NVRAM. The current display may also need careful handling.

Ordinary show running-config is not necessarily a full list of defaults. This behavior is reported on fresh IOS switches. Reported guidance identifies show run all for a fuller view that includes default settings. Another command can be used to examine the applicable defaults.

Interpret the Differences

When comparing outputs, focus on lines that appear in one display but not the other. A setting shown by show running-config but missing from show startup-config is active now without appearing in the saved file.

Conversely, entries in the startup configuration describe what the switch is intended to load when it starts. Checking the NVRAM display after the configuration has been copied there provides the supplied method for inspecting the saved result. Side-by-side review is useful after several commands have been entered during a configuration session.

Careful handling of the running-configuration display matters in shared terminals, because passwords can appear as plain text. Other troubleshooting causes can also be relevant when this message appears. Those possibilities are troubleshooting considerations when the expected saved file does not appear.

Why a Fresh Switch Can Still Show Settings

A fresh Cisco switch can display a running configuration because IOS creates and uses an initial set of settings during startup. That active state exists even when no separately saved startup configuration file is available. Built-in values appear as part of the initial state before any later user changes.

Otherwise, the initial state remains the working configuration until an administrator makes changes. Users on Network Engineering Stack Exchange report that this explains recognizable output on a new device.

Ordinary show running-config output therefore reflects the current operating state, not merely settings created by an administrator. Posters on Network Engineering Stack Exchange say show run all presents the fuller configuration, including default settings that ordinary output may leave out. They also discuss version-specific defaults.

Consequently, a Cisco switch startup-config missing message does not mean every visible setting has disappeared or that the device is unable to operate. Rather, it distinguishes IOS’s live initial state and any later live edits from a separately retained boot-time file.

The distinction matters when interpreting output after a reset, initial setup, or reboot. Seen this way, the apparent mismatch is expected behavior on an untouched switch, rather than proof that the running configuration came from NVRAM. User-entered settings can join that live state during a session, alongside the initial values IOS already supplied.

Take care when inspecting a running configuration.

Configuration displays can therefore reveal more than just interface and system defaults, so treat them appropriately when reviewing a freshly configured device. Sensitive credentials may be visible to readers. Avoid sharing such output casually.

What Happens When Configuration Changes Are Not Saved

Unsaved configuration changes can be discarded after a restart or power-down. After the switch starts again, only the configuration stored as its startup configuration is intended to load. Any hostname, console-access setting, password, banner, or IP address entered but not saved can therefore disappear.

Consequently, an unsaved configuration can appear correct while the device stays on, even though its later startup behavior will not reflect the work in that session. That distinction matters when an administrator expects a maintenance change to remain in place after a planned restart, an unexpected power-down, or another reboot. For example, Packet Tracer material describes an IP address configured without a save as discarded after reboot, illustrating why a working result before shutdown is not evidence of persistence.

Save it before the restart or power-down when the active settings need to survive. Use copy running-config startup-config to save the active configuration to NVRAM.

Before shutting down or restarting the device, make saving a deliberate final step after meaningful changes. Use show startup-config to inspect the configuration held in NVRAM after saving. A displayed saved configuration provides a record of what is available to load at startup.

Otherwise, successful testing can create a false sense that a change has become permanent. Power interruptions and planned maintenance carry the same risk whenever active settings have not been written to NVRAM. Regular saves prevent configuration loss across a subsequent boot and avoid having to re-enter the changes after the switch comes back up. Keeping this routine matters after modifying access settings or an IP address, since those are among the configuration examples used in the switch exercises.

Beyond an unsaved configuration, a Cisco switch startup-config missing message can warrant further troubleshooting when the expected file may have been deleted, corrupted, or made inaccessible. Accidental deletion can leave the switch without the startup configuration file it expects to find. Corruption can likewise affect the file or the file system that holds it.

File-system corruption is another reported possibility, because it can interfere with access to a saved file. Incorrect boot settings may also direct the switch away from the startup configuration it is intended to load at startup. Rare storage-hardware failures are included as a further potential cause.

Before treating any of those conditions as the cause, separate an expected unsaved state from a case where a configuration was expected to be present. That distinction keeps a routine save issue from being confused with a missing-file or storage problem. A saved startup configuration is the file meant to load when the switch starts. If that expected file cannot be found, the switch starts from its default state according to the reported troubleshooting explanation.

Checking show startup-config lets an administrator inspect the NVRAM contents after a configuration is expected to have been saved. Where the command continues to report that the startup configuration is not present, the reported possibilities extend beyond an ordinary unsaved change. None should be assumed from that message alone. Instead, each is a potential troubleshooting path identified for a missing file.

Careful troubleshooting focuses on why a saved file is absent or inaccessible, rather than treating each appearance of the message as evidence of one fault. Administrators dealing with an unsaved configuration can use the message and the presence of a file to frame the issue. Investigation may suit those possibilities. Each listed condition is a consideration, not a diagnosis established by the message.

Frequently Asked Questions

Why Does Show Startup-Config Say Startup-Config Is Not Present?

The message means no startup configuration file has been saved in NVRAM. A fresh switch commonly produces this result because it has no saved file to display. On a fresh switch, the active configuration is present as the running configuration in RAM.

Can Show Running-Config Display Settings When Startup-Config Is Missing?

Yes. show running-config displays the current configuration held in RAM, even when no startup configuration exists in NVRAM. Users on Network Engineering Stack Exchange report that a fresh IOS switch can also display default or initial settings, such as IOS details, hostname, and interface information.

What Command Saves a Cisco Switch Configuration?

Use copy running-config startup-config to copy the active running configuration into the startup configuration. That saves the configuration from RAM to NVRAM so it can be retained through a restart or power-down.

Is Copy Run Start the Same as Copy Running-Config Startup-Config?

Both commands copy the current running configuration to the startup configuration in NVRAM.

What Does Cop R S Do on a Cisco Switch?

cop r s is the shortest reported abbreviation for copy running-config startup-config. It saves the active configuration by copying it from RAM into the startup configuration. That makes the configuration available for a later boot.

Will an Unsaved Cisco Switch Configuration Survive a Reboot?

An unsaved configuration can be lost after a reboot or power-down because it exists only in RAM as the running configuration. Save the settings with copy running-config startup-config before restarting the switch. For example, an IP address configured but not saved is discarded after reboot.

The key distinction is between the running configuration in RAM and the startup configuration stored in NVRAM. Seeing “startup-config is not present” means the switch has no saved configuration file, not that it has no current settings. Check current settings with show running-config, inspect saved settings with show startup-config, and save persistent changes with copy running-config startup-config before a restart or shutdown.

References

Sources read in September 2026.