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

2-105
Configuring the ProCurve Wireless Edge Services xl Module
System Maintenance
5. Enter the login credentials for the FTP server.
a. In the User ID field, enter the username.
b. In the Password field, enter the password for this username.
6. In the Software section, configure the version number, filename and path
for the software image.
a. In the Version field, enter the version of the software image that is
stored on the FTP or TFTP server.
b. In the File Name (with Path) field, enter the name of the file that
contains the software image and the path to that filename (if the path
is required by the Update Server). If you are using an FTP server and
the configuration file is saved at the server’s root level, enter a period
followed by a slash (./) for the path. If the configuration file resides
at a different level on the FTP server, enter the complete path. (If you
are using a TFTP server, this field may not be required.)
7. In the Configuration File section, in the File Name (with Path) field, enter the
name of the file that contains the configuration and the path to that
filename (if the path is required by the Update Server).
8. If your Wireless Edge Services xl Module is a member of a redundancy
group, you should store a common configuration for all members on the
Update Server. Specify the name and path for this common configuration
in the Redundancy File Name (with Path) field.
The file specified in the File Name (with Path) field should include individ-
ualized settings, such as IP address, for this particular module. You must
specify the individualized configuration. The redundancy configuration
alone is not sufficient.
9. Click the Apply button to save your changes to the running-config.
10. Click the Save button in the navigation bar to save your changes to the
startup-up config.
Password Encryption
The Wireless Edge Services xl Module might store a variety of passwords.
Encryption prevents someone from accessing the module’s configuration file
(whether through the CLI or an insecurely transmitted file) and reading the
passwords.