F3726, F3211, F3174, R5135, R3816-HP Firewalls and UTM Devices System Management and Maintenance Configuration Guide-6PW100
51
4. Select the .cfg file to be imported as prompted.
5. Click Apply.
52B
Managing configuration files at the CLI
193BSaving the running configuration
To make configuration changes take effect at the next startup, save the running configuration to the
startup configuration file to be used at the next startup before the device reboots.
Complete the following tasks to save the running configuration:
Task Remarks
749H
Enabling configuration encryption
Optional.
Perform this task to make sure a configuration
file is accessible only to trustworthy devices.
750H
Saving running configuration in different approaches Required.
383BEnabling configuration encryption
Configuration encryption enables the device to automatically encrypt a startup configuration file when
saving the running configuration to it. This function has the following approaches:
• Private key approach—Only the encrypting device can decrypt the encrypted configuration file.
• Public key approach—Any device that supports the configuration encryption function can decrypt
the encrypted configuration file.
To view encrypted configuration, use the display saved-configuration command instead of the more
command. If you use the more command, the system displays a failure message or garbled text.
To enable configuration encryption:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enable configuration
encryption.
configuration encrypt { private-key |
public-key }
By default, configuration
encryption is disabled.
Configuration is saved
unencrypted.
384BSaving running configuration in different approaches
When saving the running configuration to a configuration file, you can specify the file as the next-startup
configuration file.
If you are specifying the file as the next-startup configuration file, use one of the following methods to
save the configuration:
• Fast mode—Use the save command without the safely keyword. In this mode, the device directly
overwrites the target next-startup configuration file. If a reboot or power failure occurs during this
process, the next-startup configuration file is lost. You must specify a new startup configuration file
after the device reboots (see "
751HSpecifying the next-startup configuration file").