Switch Memory and Configuration
Using the CLI To Implement Configuration Changes
If you use the CLI to change a parameter setting, and then execute the
boot
command without first executing the
write memory
command to save the
change, the switch prompts you to specify whether to save the changes in the
current running-config file. For example:
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-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
6-8
Summary of Contents for PROCURVE 2520
Page 2: ......
Page 3: ...HP ProCurve 2520 Switches November 2009 S 14 03 Management and Configuration Guide ...
Page 60: ...Using the Menu Interface Where To Go From Here 3 16 ...
Page 82: ...Using the Command Line Interface CLI CLI Editing Shortcuts 4 22 ...
Page 146: ...Switch Memory and Configuration Automatic Configuration Update with DHCP Option 66 6 40 ...
Page 164: ...Interface Access and System Information System Information 7 18 ...
Page 292: ...Port Trunking Outbound Traffic Distribution Across Trunked Links 12 30 ...
Page 374: ...Configuring for Network Management Applications LLDP Link Layer Discovery Protocol 13 82 ...
Page 434: ...Monitoring and Analyzing Switch Operation Locating a Device B 30 ...
Page 514: ...Troubleshooting DNS Resolver C 80 ...
Page 524: ...Daylight Savings Time on ProCurve Switches E 4 ...
Page 542: ...16 Index ...
Page 543: ......