HP ProCurve Series 2810, Management And Configuration Manual

Page: 105 / 420

Switch Memory and Configuration
Using the CLI To Implement Configuration Changes
ProCurve(config)# interface e 1 disable
Disables port 1 in the running configuration, which causes port 1 to block all traffic.
ProCurve(config)# boot
Device will be rebooted, do you want to continue [y/n]? y
Do you want to save current configuration [y/n]?
Press
[Y]
to continue the rebooting process.
You will then see this prompt.
Figure 6-2. Boot Prompt for an Unsaved Configuration
The above prompt means that one or more parameter settings in the running­
config file differ from their counterparts in the startup-config file and you need
to choose which config file to retain and which to discard.
■
If you want to update the startup-config file to match the running-config
file, press
[Y]
for "yes". (This means that the changes you entered in the
running-config file will be saved in the startup-config file.)
■ If you want to discard the changes you made to the running-config file so
that it will match the startup-config file, then press
[N] for "no". (This means
that the switch will discard the changes you entered in the running-config
file and will update the running-config file to match the startup-config
file.)
N o t e
If you use the CLI to make a change to the running-config file, you should
either use the
write memory command or select the save option allowed during
a reboot (figure 6-2, above) to save the change to the startup-config file. That
is, if you use the CLI to change a parameter setting, but then reboot the switch
from either the CLI or the menu interface without first executing the
write
memory command in the CLI, the current startup-config file will replace the
running-config file, and any changes in the running-config file will be lost.
Using the
Save
command in the menu interface does not save a change made
to the running config by the CLI unless you have also made a configuration
change in the menu interface. Also, the menu interface displays the current
running-config values. Thus, where a parameter setting is accessible from both
the CLI and the menu interface, if you change the setting in the CLI, the new
value will appear in the menu interface display for that parameter.
However,
as indicated above, unless you also make a configuration change in the
menu interface, only the
write memory
command in the CLI will actually
save the change to the startup-config file .
6-7