WESM zl Management and Configuration Guide WT.01.03 and greater

2-99
Configuring the ProCurve Wireless Edge Services zl Module
System Maintenance
■ server username and password (for FTP server)
■ location of the software image on the Update Server
■ software image that the module should use
■ location of 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 zl 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 WT.01.07, the module first checks its own software image
file to see if it is using WT.01.07. If the module is using WT.01.07, it reboots
with this image. If the module is using a different image—such as WT.01.03—
it contacts the Update Server and requests the WT.01.07 image. If the Update
Server has the WT.01.07 image and sends it, the module boots with WT.01.07.
Whenever the module requests the software image file from the Update Server,
it also requests the configuration file. The configuration file that the Update
Server sends must be exactly the same as the startup-config saved on the
module. You can ensure that these files are the same by always saving the
latest startup-config to the Update Server.
Checking the Configuration File
The configuration file is handled slightly differently from the software image.
For the configuration file, the Update Server is designed to recover a corrupted
configuration file. It is not intended to deploy new configurations.
You cannot define the configuration file in the Update Server settings. The
Wireless Edge Services zl Module always requests the startup-config. When
you define the File Name (with Path) field in the Update Server settings, you
define the location of the startup-config file on the Update Server.