Wireless Edge Services xl Module Release Notes WS.02.27
Table Of Contents
- Release Notes: Version WS.02.27 Software for the ProCurve Wireless Edge Services xl Module (J9001A) and the ProCurve Redundant Wireless Services xl Module (J9003A)
- Copyright and Disclaimers
- Contents
- Software Management
- Support Notes
- Release WS.02.07
- Reconfigure Management Passwords After a Software Update from Version WS.01.xx to Version WS.02.xx
- Accessing the Web Browser Interface After a Software Update from Version WS.01.xx to Version WS.02.xx
- Configuring Authentication for Web-Users
- Special Characters for the ACL ID Field
- Correction: SNMP v3 Default Password
- Correction: Stations per Radio
- Correction: Stations per Module in a Layer 3 Mobility Domain
- Correction: Disabling TKIP Countermeasures
- Clarification: Setting Intrusion Detection with TKIP Countermeasures
- Release WS.02.07
- Enhancements
- Software Fixes
- Known Software Issues and Limitations
- Back Cover
2
Software Management
Saving Configurations
Downloading Software to the Module
Caution
The startup-config file generated by the latest software release is compatible with the same file
generated by earlier software releases. HP recommends that you backup your current configuration
before performing any software update. See the Management and Configuration Guide (5013-5912)
for instructions and more information.
ProCurve Networking periodically provides software updates through the ProCurve Networking Web
site h
ttp://www.procurve.com/software). After you acquire the new software file, use TFTP or FTP from
the Web browser interface or the CLI to update the module software. See the Management and
Configuration Guide (5013-5912) for instructions and more information.
Note
Downloading new software does not change the current module configuration. The module config-
uration is contained in a separate file that can also be transferred, for example, for archive purposes
or to be used in another module of the same model.
Saving Configurations
The module operates with two configuration files:
■ Running-Config File: Exists in volatile memory and controls module operation. Rebooting
the module erases the current running-config file and replaces it with an exact copy of the
current startup-config file. To save a configuration change, you must save the current
configuration in the running-config file to the startup-config file.
■ Startup-Config File: Exists in flash (non-volatile) memory and preserves the most recently-
saved configuration as the “permanent” configuration. When the module reboots for any
reason, an exact copy of the current startup-config file becomes the new running-config file
in volatile memory.
In the wireless-services context of the CLI, you may use the write memory command to save changes
made to the running-config file to the startup-up config file. Also, the system prompts you to save
any unsaved changes when you leave the wireless-services context.