R3303-HP HSR6800 Routers Fundamentals Configuration Guide

104
IMPORTANT:
To run on the device, a configuration file must meet the content and format requirements. To ensure a
successful configuration load at startup, use a confi
g
uration file created on the device at startup. If you edi
t
the configuration file, make sure all edits are compliant with the requirements.
A configuration file is saved as a text file according to the following rules:
• Commands are saved in their complete form.
• The commands are listed 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
(#).
• A 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 modifying the content and format of the
configuration file.
Next-startup configuration file redundancy
You can specify one main next-startup configuration file and one backup next-startup configuration file
for redundancy. If a configuration file is not assigned the main or backup attribute, its file attribute is
NULL.
At startup, the device tries to start up with the main configuration file. If the main configuration file is
corrupted or unavailable, the device tries the backup configuration file. If the backup configuration file is
corrupted or unavailable, the device starts up with the factory defaults.
You can specify a main or backup next-startup configuration file directly (see "Specifying a configuration
fi
le for the next startup") or when saving the running configuration (see "Saving the running
c
onfiguration").
For high availability, do not specify a configuration file as both the main and backup configuration files.
Startup with a configuration file
The device selects the configuration file to load at startup, as follows:
1. If the specified main startup configuration file exists, the device starts up with this configuration file.
2. If the specified main startup configuration file does not exist but the backup startup configuration
file exists, the device starts up with the backup startup configuration file.
3. If neither the main nor the backup startup configuration file exists, the device starts up with the
factory defaults.
FIPS compliance
The router 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 Security Configuration Guide.