Wireless/Redundant Edge Services xl Module Management and Configuration Guide WS.02.xx and greater

2-100
Configuring the ProCurve Wireless Edge Services xl Module
System Maintenance
Avoiding Problems in Using the Update Server
To ensure that the Wireless Edge Services xl Module does not boot with the
wrong software image or the factory default settings, follow these guidelines:
■ Keep the Update Server settings current.
For example, if you upgrade the software image on the Wireless Edge
Services xl Module, you must save the new software image to the Update
Server and change the software image file defined in the module’s Update
Server settings. If the Update Server settings specify an older software
image, the module will attempt to use this older software image the next
time that it is rebooted.
Alternatively, you can also force the Update Server to upload the config-
uration file whether or not the checksum matches. While perhaps less
secure, this option prevents the Wireless Edge Services xl Module from
reverting to factory default settings when you do not follow the above
guidelines exactly.
■ Ensure that the Update Server is available when the Wireless Edge
Services xl Module reboots.
If the module must request an image or configuration file but the Update
Server is unavailable for any reason, the module uses its current image to
reboot and loads the factory default startup-config.
■ Ensure that the latest software image and a file named “startup-config”
are saved on the Update Server.
Problems can occur if the Update Server does not have the specified
software image or a file name “startup-config.” In this case, the module
boots with its primary image and the factory defaults.