Startup Configuration File Selection; Configuration File Content Organization And Format; Fips Compliance - HP 10500 Series Configuration Manual

Startup configuration file selection

At startup, the device uses the following procedure to identify the configuration file to load:
1. The device searches for a valid .cfg next-startup configuration file.
2. If one is found, the device searches for an .mdb file that has the same name and content as the .cfg
file.
3. If an .mdb file has the same name and content as the .cfg file, the device starts up with the .mdb
file. If none is found, the device starts up with the .cfg file.
Unless otherwise stated, the term "configuration file" in this document refers to a .cfg configuration file.

Configuration file content organization and format

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 configuration file that was automatically created on the
device or created by using the save command. If you edit the configuration file, make sure all edits are
compliant with the requirements.
A configuration file must meet the following requirements:
All commands are saved in their complete form.
•
Commands are sorted in sections by command view, typically in this order: system view, interface
•
view, protocol views, and user interface view.
• Two adjacent sections are separated by a comment line that starts with a pound sign (#).
The configuration file ends with the word return.
•
The following is a sample configuration file excerpt:
#
local-user root
password simple admin
service-type ssh telnet terminal
authorization-attribute user-role network-admin
#
interface Ten-GigabitEthernet1/0/1
port link-mode route
ip address 1.1.1.1 255.255.255.0
#

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 Security Configuration Guide.
99