Configuration File Formats; Startup Configuration File Selection; Configuration File Content Organization And Format - HP 12500 Configuration Manual

Routing switch series
Table of Contents

Advertisement

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.
For reliability, 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:
Searches for a valid .cfg next-startup configuration file.
1.
If one is found, searches for an .mdb file that has the same name and content as the .cfg file.
2.
If an .mdb file has the same name and content as the .cfg file, starts up with the .mdb file. If none
3.
is found, 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 of the device. To
avoid any configuration loading problem 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 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 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 class manage
password simple admin
service-type ssh telnet terminal
authorization-attribute user-role network-admin
#
interface GigabitEthernet3/0/1
port link-mode route
ip address 1.1.1.1 255.255.255.0
#
88

Advertisement

Table of Contents
loading

Table of Contents