Configuration Save, Reset, and File System

Running Config vs Saved Config

Every VRP device maintains at least two configuration concepts you must separate under exam pressure:

Changes typed in system-view update the running configuration immediately (subject to command success). They do not automatically update the startup file. If power fails or you reboot without saving, unsaved changes are gone.

display current-configuration vs display saved-configuration

Use filters and sections in real labs when available, for example focusing on an interface section, but for HCIA memorize the two full command names and their meanings. A frequent scenario question:

• You configure VLAN 100 and see it in display current-configuration.
• You do not save.
• Device reboots.
• VLAN 100 is missing because it never entered the saved file.

If display current-configuration and display saved-configuration disagree, either someone has unsaved changes, or the startup file was reset/edited offline.

Saving Configuration

From user-view (typical):

<Huawei> save

VRP prompts for confirmation and often asks whether to overwrite the existing startup file name (commonly vrpcfg.zip or a similar default depending on platform and version). Answer Y when you intend to commit. After a successful save, running and saved should match for the parameters you care about.

Best practice loop after any successful lab step set:

1. Configure in system-view.
2. Verify with display commands.
3. Return to user-view if needed.
4. save and confirm.
5. Optionally re-check display saved-configuration for critical lines.

Some environments allow save from system-view as well; exam items still treat save as the action that writes startup config. Do not confuse save with write memory (Cisco mental model)—use the Huawei keyword save.

Resetting Saved Configuration

To wipe the startup configuration:

<Huawei> reset saved-configuration

VRP asks for confirmation because this is destructive for the next boot. Important points:

• reset saved-configuration does not immediately erase the running config. The device keeps operating on current memory settings until reload.
• After reset, if you reboot without saving again, the device returns toward factory-default style startup behavior (no custom VLANs, IPs, or passwords you previously saved).
• If you reset saved configuration but then save again, you rewrite a new startup file from the current running config—so you did not factory-reset the operational state; you only refreshed what will be stored.

Exam trap: students run reset saved-configuration expecting the CLI to drop all VLANs instantly. Instant wipe of active services is not what that command alone does.

Reboot Behavior and Prompts

<Huawei> reboot

On reboot, VRP may warn if the current configuration differs from the saved configuration and ask whether to save. Read prompts carefully:

HCIA loves process questions: order of save, reset saved-configuration, and reboot determines the outcome. Draw a quick timeline in your head before answering.

Configuration File Names and Startup

Platforms store a primary configuration file on flash (name varies; vrpcfg.zip appears in many training materials). Advanced operations can specify alternate config files or compare files, but associate-level focus is:

• Know that a config file on flash is what startup uses.
• Know that save updates that relationship for the next boot.
• Know that reset saved-configuration clears that startup selection/content after confirmation.

You are not expected to design dual-image rollback architectures on H12-811, but you should understand that the system software image and the configuration file are different objects on flash.

VRP File System Basics

Storage is commonly exposed as flash:/. Useful commands:

Example exploration pattern:

<Huawei> pwd
<Huawei> dir
<Huawei> cd flash:/
<Huawei> dir

You will typically see system software packages (often .cc images on many Huawei platforms), configuration files, and license or log-related files depending on model. Never delete the running system software in production. In labs, only delete files you understand.

Upgrade Concepts at HCIA Level

H12-811 expects conceptual upgrade literacy, not a multi-hour ISSU deep dive:

1. Obtain a compatible system software package for the exact platform.
2. Transfer it to the device (common lab methods: FTP/SFTP/TFTP or USB where supported).
3. Place the file on flash (verify with dir).
4. Configure the device to boot the new package (startup system-software style commands vary by version—know that a startup software setting exists separate from config save).
5. save configuration if required by the procedure.
6. reboot and verify with display version.

If the new image fails to boot, recovery may involve console access and selecting an alternate image—another reason console skills matter. For the exam, associate “upgrade” with: correct file on flash → point startup software → reboot → verify version.

Comparing Configuration Commands Side by Side

Operational Scenarios

Scenario A — End of successful lab
Configure OSPF and VLANs → verify neighbors and display current-configuration → save → optional controlled reboot to prove persistence.

Scenario B — Return device to defaults for next student
reset saved-configuration → confirm → reboot → do not save the old running config when prompted if the platform asks during reboot after reset workflows—follow the exact lab order taught for your gear so defaults load.

Scenario C — “It worked until the power blip”
Root cause is almost always never saved. Prevention is save discipline, not more OSPF tuning.

Exam Traps

• Treating display current-configuration as proof the config will survive reboot.
• Believing reset saved-configuration instantly removes running VLANs.
• Confusing delete of a file on flash with undo of a CLI setting.
• Saving a broken experimental config, then rebooting into an outage.
• Upgrading by only copying a file without setting startup system software (concept).

Lab Checklist

• Make a small change (hostname or description).
• Confirm it appears in display current-configuration.
• Confirm it is absent from display saved-configuration before save.
• save and confirm presence in saved configuration.
• Practice dir / pwd on flash:/.
• Read (do not execute carelessly) what reset saved-configuration will ask.

Mastering this section protects every hour you spend on later chapters: configuration that is not saved is configuration that never existed after the next power cycle.