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

2-14
Configuring the ProCurve Wireless Services xl Module
Management Interfaces
Saving Changes to the startup-config
When you make configuration changes to the Wireless Edge Services xl
Module, you must enter the write memory command to save these changes to
the module’s startup-config. When you enter this command, you must be in
the wireless-services context:
ProCurve(wireless-services-C)# write memory
If you exit the wireless-services context and enter the write memory command
in the CLI for the wireless services-enabled switch, the configuration changes
for the Wireless Edge Services xl Module are not saved to its startup-config file.
CLI Commands
For a list of CLI commands for the Wireless Edge Services xl Module and their
descriptions, see Appendix A, “ProCurve Wireless Services xl Module Com-
mand Line Reference”.
Security
In addition to supporting the latest security standards for wireless communi-
cations, the Wireless Edge Services xl Module allows you to secure manage-
ment access. To protect communications between the Wireless Edge Services
xl Module and your management workstation, the module supports SSH,
secure hypertext transfer protocol (HTTPS) over Secure Socket Layer (SSL),
and SNMP v3. Management users and their related passwords are also con-
trolled through SNMP v3.
SSH Access
If you want to access the module’s CLI from a remote location, you should use
SSH rather than Telnet. Although Telnet can be used to configure the Wireless
Edge Services xl Module from a remote location, it is not secure from eavesdrop-
ping. The SSH protocol, on the other hand, generates public keys to encrypt all
the data exchanged between the module and your management workstation.
Further, SSH ensures that data traveling over the network arrives unaltered.