WESM zl Management and Configuration Guide WT.01.28 and greater
2-100
Configuring the ProCurve Wireless Edge Services zl Module
System Maintenance
If the startup-config is corrupted, the checksums will not match, and the module will
request the configuration file from the location specified in the Update Server
settings. When the module receives the configuration file from the Update Server, it
compares the checksum that it saved for the startup-config with this file’s checksum.
If the two checksums match, the module loads the configuration file that it received
from the Update Server.
If the two checksums do not match, the module assumes that the Update Server does
not have the correct configuration file. The module boots with the factory default
startup-config.
However, you can configure the Wireless Edge Services zl Module to ignore the
checksum and always use the startup-config file sent by the Update Server. This
option is called forcing the config update.
Avoiding Problems in Using the Update Server
To ensure that the Wireless Edge Services zl 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
zl 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 configuration
file whether or not the checksum matches. While perhaps less secure, this option
prevents the Wireless Edge Services zl 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 zl
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.