HP VPN Firewall Appliances System Management and Maintenance Configuration Guide

52
Configuration file content organization and format
IMPORTANT:
To run on the device, a confi
g
uration file must meet the content and format requirements of the device. To
ensure a successful confi
g
uration load at startup, use a confi
g
uration file created on the device. If you edi
t
the configuration file, make sure all edits are compliant with the requirements of the device.
A configuration file must meet the following requirements:
• All commands are saved in their complete form.
• Commands are sorted in sections by view, typically in this order: system view, interface view,
protocol views, and user interface view.
• Sections are separated with one or more blank lines or comment lines that start with a pound sign
(#).
• The configuration file ends with the word return.
You can execute the save command to save the running configuration to a configuration file. To make
sure the configuration file can be loaded, HP recommends not editing the content and format of the
configuration file.
Startup with a configuration file
The device selects the configuration file to load at startup, as follows:
1. If you have specified a startup configuration file that already exists on the storage medium, the
device starts up with this startup configuration file.
2. If the specified startup configuration file does not exist, the device starts up with the factory
defaults.
FIPS compliance
The device supports the FIPS mode that complies with NIST FIPS 140-2 requirements. Support for features,
commands, and parameters might differ in FIPS mode and non-FIPS mode. For more information about
FIPS mode, see Access Control Configuration Guide.
Managing configuration files in the Web interface
Saving the running configuration
The save configuration module allows administrators to save the running configuration to the next-startup
configuration file (.cfg file or .xml file).
Guidelines
• Saving the configuration takes some time.