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

2-56
Configuring the ProCurve Wireless Services xl Module
System Maintenance
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 xl 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.
Whatever name you give the file that you save to the Update Server, it should
always contain the same configuration that is saved on the module’s startup-
config. When you save the startup-config (whether or not you have made
configuration changes), you should immediately copy this file to the Update
Server.
When you save the startup-config file and the Update Server is enabled, the
Wireless Edge Services xl Module saves a checksum of the startup-config.
When the Wireless Edge Services xl Module reboots, it compares the check-
sum it saved with the checksum of the startup-config it loads. If the two match,
the module boots normally with the startup-config.
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 it saved for the startup-config
with this file’s checksum. If the two checksums match, the module loads the
configuration file 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.