Overview
Managing Configuration Files Using a Text Editor
The CLI will prompt you to save the system configuration. If you have already
made the configurations that you want to test, reply no. If you are getting ready
to make the configurations to be tested and want to save previous configura-
tions, reply yes. The CLI then displays:
You are about to reboot the system. Continue? [y/n]
Enter
. The system will not reboot immediately. It will wait the amount of
y
time you have specified. Remember that while you are doing a delicate
configuration and using the reload in command, you must not save the
running-config to the startup-config (by entering either write memory or
copy run start). Otherwise, the ProCurve Secure Router will load these
configurations when it reboots.
To cancel the reload, enter:
ProCurve# reload cancel
N o t e
SafeMode automates this process if you are configuring the router using a
Telnet or SSH session. (See "SafeMode" on page 1-61.)
Managing Configuration Files Using a
Text Editor
Configuration files can be adjusted to each router's needs using your com-
puter's text editor. This allows you to set up a configuration on one router,
save it to a file, and edit it for installation on another router.
ProCurve Secure router configuration files are robust. If you miskey a com-
mand or make a mistake in the text editor, the router will simply ignore the
mistake and use the default settings. If any necessary command is missing,
the router will substitute the default. Problem commands will trigger an error
message during bootup.
It is not necessary to re-edit the configuration in a text editor to repair a
problem; simply enter the pertinent command in the CLI. View the error
messages displayed during bootup to determine which command is faulty.
1-73