Switch Memory and Configuration

Using Primary and Secondary Flash Image Options

Using the Fastboot feature. The fastboot command allows a boot sequence that skips the internal power-on self-tests, resulting in a faster boot time. When using redundant management and fastboot is enabled, it is saved to the standby management module when the config files are synchronized. Fastboot is used during the next bootup on either management module.

Syntax: [no] fastbootEnables the fastboot optionThe no option disables the feature.Syntax: show fastbootShows the status of the fastboot feature, either enabled or disabled.The fastboot command is shown below.ProCurve(config)# fastbootUsing Reload

The Reload command reboots the switch from the flash image that you are currently booted on (primary or secondary) or the flash image that was set either by the boot set-defaultcommand or by the last executed boot system flash <primary secondary> command. Because reload bypasses some subsystem self-tests, the switch reboots faster than if you use either of the boot command options. If you are using redundant management and redundancy is enabled, the switch will failover to the other management module.

Syntax: reload

For example, if you change the number of VLANs the switch supports, you must reboot the switch in order to implement the change. The reload command prompts you to save or discard the configuration changes.

ProCurve(config)# max-vlans 12

Command will take effect after saving configuration and reboot.

ProCurve(config)# reload

This command will cause a switchover to the other management module which may not be running the same software image and configurations. Do you want to continue [y/n]? y

Figure 6-17. Using Reload with Redundant Management and Pending Configuration Changes

6-24