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

2-98
Configuring the ProCurve Wireless Edge Services xl Module
System Maintenance
Update Server
The Wireless Edge Services xl Module can communicate with an Update
Server, on which you can store backup copies of the software image and the
configuration file for your Wireless Edge Services xl Module. If the module’s
software image or configuration file becomes corrupted, you can reboot the
module, and it will retrieve the necessary file from the Update Server—
provided you have configured the Update Server settings correctly and copied
the necessary files to the Update Server.
When you configure the Update Server on the Wireless Edge Services xl
Module, you define the following:
■ IP address of the Update Server
■ protocol of the Update Server (FTP or TFTP)
■ server username and password (for the FTP server)
■ location of the software image on the Update Server
■ software image that the module should use
■ location of the configuration file
■ location of a redundancy configuration file—a common configuration for
an entire redundancy group, an optional supplement to (not replacement
for) the configuration file
Checking the Software Image File
When the Wireless Edge Services xl Module reboots, it checks the Update
Server settings that you have configured to ensure that it is using the correct
software image. If the module is already using the software image that you
specified, it simply reboots and then checks the configuration file. (See
“Checking the Configuration File” on page 2-99.)
However, if you have specified a different software image for the Update
Server settings, the module requests that image from the Update Server. For
example, if you configure the Update Server settings and specify that the
software image is WS.02.02, the module first checks its own software image
file to see if it is using WS.02.02. If the module is using WS.02.02, it reboots
with this image. If the module is using a different image—such as WS.02.01—
it contacts the Update Server and requests the WS.02.02 image. If the Update
Server has the WS.02.02 image and sends it, the module boots with WS.02.02.