Specifying A Next-Startup Configuration File - HP 10500 Series Configuration Manual

Step
2. Roll the running configuration
back to the configuration
defined by a configuration
file.
The configuration rollback function might fail to reconfigure some commands in the running configuration
for one of the following reasons:
A command cannot be undone because prefixing the undo keyword to the command does not
•
result in a valid undo command. For example, if the undo form designed for the A [B] C command
is undo A C, the configuration rollback function cannot undo the A B C command. This is because
the system does not recognize the undo A B C command.
• A command (for example, a hardware-dependent command) cannot be deleted, overwritten, or
undone due to system restrictions.
The commands in different views are dependent on each other.
•
Commands or command settings that the device does not support cannot be added to the running
•
configuration.

Specifying a next-startup configuration file

CAUTION:
In an IRF fabric, use the undo startup saved-configuration command with caution. This command can
cause an IRF split after the IRF fabric or an IRF member reboots.
You can execute the save [ safely ] [ backup | main ] [ force ] command to save the running configuration
to a .cfg configuration file. The .cfg configuration file can be specified as both the main and backup
next-startup configuration files.
Alternatively, you can execute the startup saved-configuration cfgfile [ backup | main ] command to
specify a .cfg configuration file as the main or backup next-startup configuration file. Make sure the
specified configuration file is valid and saved to the root directory of each MPU's default storage
medium.
To specify a next-startup configuration file, perform the following task in user view:
Command
configuration replace file filename
107
Remarks
The specified configuration file
must not be encrypted.