Next-Startup Configuration File Redundancy; Configuration File Formats; Startup Configuration File Selection; Configuration File Content Organization And Format - HP 10500 Series Configuration Manual

Next-startup configuration file redundancy

You can specify one main next-startup configuration file and one backup next-startup configuration file
for redundancy.
At startup, the device tries to start up with the main configuration file. If the main configuration file is
corrupt or unavailable, the device tries the backup configuration file. If the backup configuration file is
corrupt or unavailable, the device starts up with the factory defaults.
For high availability, do not specify one configuration file as both the main and backup configuration
files.

Configuration file formats

Configuration files you specify for saving configuration must use the .cfg extension. A .cfg configuration
file is a human-readable text file. When you save configuration to a .cfg file, the device automatically
saves the configuration to an .mdb user-inaccessible binary file that has the same name as the .cfg file.
The device loads an .mdb file faster than loading a .cfg file.

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 created on the device. 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 different command views, including system view, interface
•
view, protocol view, and user line 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 class manage
101