Configuration file management, Configuration file overview, Types of configuration – H3C Technologies H3C SecPath F1000-E User Manual
Page 176: Format and content of a configuration file
1
Configuration File Management
The device provides the configuration file management function. You can manage configuration files at
a user-friendly command line interface (CLI).
This chapter includes these sections:
•
•
Saving the Current Running Configuration
•
Setting Configuration Rollback
•
Specifying a Startup Configuration File to Be Used at the Next System Startup
•
Backing Up the Startup Configuration File
•
Deleting a Startup Configuration File to Be Used at the Next Startup
•
Restoring a Startup Configuration File
•
Displaying and Maintaining Device Configuration
Configuration File Overview
A configuration file saves the device configurations in command lines in text format to ensure that these
configurations can be kept when the device restarts or the configurations are rolled back. You can view
the configuration information conveniently through configuration files.
Types of Configuration
The device maintains two types of configuration files:
•
Startup configuration: Configuration used for initialization when the device boots. If this file does
not exist, the system boots using null configuration, that is, using the default parameters.
•
Running configuration: The currently running configuration of the system. The current running
configuration may include the startup configuration if the startup configuration is not modified
during system operation, and it also includes the new configuration added during the system
operation. The current running configuration is stored in the temporary storage medium of the
device, and will be removed if not saved when the device reboots.
Format and Content of a Configuration File
A configuration file is saved as a text file. It is saved following these rules:
•
A configuration file contains commands, and only non-default configuration settings are saved.
•
Commands in a configuration file are listed in sections by views, usually in the order of system view,
interface view, routing protocol view, and user interface view. Sections are separated with one or
multiple blank lines or comment lines that start with a pound sign #.
•
A configuration file ends with a return.