Study guide
Configuration Save, Reset, and File System
Huawei Certified ICT Associate - Datacom HCIA-Datacom H12-811 V1.0
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About HCIA-Datacom H12-811 V1.0 Study Strategies and Exam Logistics
2 Chapter 1: Network Models and Ethernet Fundamentals
OSI and TCP/IP Models Ethernet Technology and MAC Addressing Data Forwarding and Campus Network Lifecycle
3 Chapter 2: IPv4 Addressing and Transport Protocols
IPv4 Addressing and Subnetting ARP and ICMP TCP and UDP Principles Common Ports and Application Protocols
4 Chapter 3: Huawei VRP Basics and Device Management
VRP CLI Views and Core Commands Configuration Save, Reset, and File System SSH, Telnet, and Console Access Display Commands and Basic Troubleshooting
5 Chapter 4: Ethernet Switching and VLANs
Switch Forwarding and MAC Address Tables VLAN Concepts and Segmentation Access, Trunk, and Hybrid Link Types VLANIF and Inter-VLAN Routing
6 Chapter 5: STP, RSTP/MSTP, and Link Aggregation
STP Concepts and Election RSTP and MSTP Eth-Trunk Static and LACP Stacking Basics for Campus Switches
7 Chapter 6: IP Routing Fundamentals
RIB, FIB, and Forwarding Decisions Static and Default Routes on VRP Route Preference and Longest Match Floating Static Routes and Blackhole Routes
8 Chapter 7: OSPF Fundamentals
OSPF Areas and Router Types Neighbor States and Adjacency LSA Types and LSDB DR/BDR Election and VRP OSPF Configuration
9 Chapter 8: ACLs and AAA
Basic and Advanced ACLs traffic-filter Application and Matching Order AAA with Local, RADIUS, and HWTACACS
10 Chapter 9: DHCP, NAT, and Network Services
DHCP Server, Relay, and Snooping NAT, Easy IP, and NAT Server FTP, TFTP, DNS, NTP, HTTP Basics
11 Chapter 10: WLAN Basics
WLAN Architecture: AC, AP, and Fit Mode CAPWAP Tunnels and Forwarding Modes WPA2, WPA3, and WLAN Security Basics Basic WLAN Configuration Concepts
12 Chapter 11: WAN Basics
WAN Concepts and Encapsulation PPP Authentication: PAP and CHAP PPPoE Basics and Client Configuration
13 Chapter 12: IPv6 Fundamentals
IPv6 Address Types and Format Neighbor Discovery and ICMPv6 Stateful and Stateless DHCPv6 IPv6 Static Routes on VRP
14 Chapter 13: SDN and NFV Fundamentals
SDN and NFV Fundamentals
15 Chapter 14: Network Management and O&M
Network Management, O&M, and Automation Basics
Configuration Save, Reset, and File System
Key Takeaways Explain This Topic AI
Running configuration is active in RAM; startup configuration is the saved file loaded at boot—save commits running to startup.
display current-configuration shows running config; display saved-configuration shows the startup file.
reset saved-configuration clears the startup file after confirmation; a reboot then loads defaults unless you save again.
flash:/ is the primary storage; dir, pwd, and cd navigate the VRP file system for images and config files.
Forgetting to save before reboot is a classic HCIA failure mode: lab work disappears even though display current-configuration looked perfect.
Last updated: July 2026
Running Config vs Saved Config
Every VRP device maintains at least two configuration concepts you must separate under exam pressure:
- Concept Where it lives What it affects
- Current / running configuration Device memory (active) Forwarding and services right now
- Saved / startup configuration Non-volatile storage (commonly flash) What loads after the next reboot
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
- Command Shows
- display current-configuration Active running configuration
- display saved-configuration Contents of the startup configuration file
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:
Configure in system-view.
Verify with display commands.
Return to user-view if needed.
save and confirm.
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:
- Situation Risk
- Unsaved good work + reboot without save Lose configuration
- Bad experimental config + save then reboot Bad config becomes permanent startup
- reset saved-configuration then reboot without save Load empty/default startup
- reset saved-configuration then save then reboot Boot with whatever was running when you saved
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:
- Command Purpose
- dir List files and directories in the current path
- pwd Print working directory
- cd Change directory (for example cd flash:/ )
- more / view tools (platform-dependent) Inspect text file contents
- delete / undelete (where supported) Manage files carefully
- pwd + dir combo Confirm you are looking at the intended storage
- 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:
Obtain a compatible system software package for the exact platform.
Transfer it to the device (common lab methods: FTP/SFTP/TFTP or USB where supported).
Place the file on flash (verify with dir ).
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).
save configuration if required by the procedure.
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
- Goal Command family
- See active settings display current-configuration
- See boot settings file display saved-configuration
- Commit active → startup save
- Clear startup file reset saved-configuration
- Restart device reboot
- List flash files dir
- Confirm software build display version
- 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.