Wireless/Redundant Edge Services xl Module Management and Configuration Guide WS.01.03 or greater

2-57
Configuring the ProCurve Wireless 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 it is rebooted.
■ 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 configuration file are saved on
the Update Server.
Problems can occur if the configuration file stored on the Update Server
is different from the configuration file that the module is currently using.
In this case, the module boots with the factory default settings. If the
Update Server does not have the specified image or configuration file, the
module boots with its primary image and the factory defaults.
Table 2-3 lists the image and configuration file that the Wireless Edge Services
xl Module uses if:
■ the image file specified in the Update Server settings is the image file that
the module is already using
■ the Update Server is enabled, but no settings are configured for the image
file and the configuration file location
■ the Update Server is unavailable