Software Update Guide for 4.1.3.93 to 4.4.0.50
3
Updating the 700wl Series
4. Update the Access Control Server system to software version 4.1.4.4. The
Update... function is found under Maintenance, on the main Software
Setup page. This will lead you through steps for obtaining and installing
the version 4.1.4.4 software. An update key will be required. Note that any
Access Controller or Access Controller xl Module running 4.4.0.50 is not
recognized until version 4.4.0.50 is installed in the Access Control Server.
Follow the instructions in the ProCurve Secure Access 700wl Series
Management and Configuration Guide, Chapter 8 to perform the update.
5. Reboot the Access Control Server to the new version, 4.1.4.4.
6. Running under 4.1.4.4, update the Access Control Server system to version
4.4.0.50. Reboot the system to 4.4.0.50. You should now have 4.4.0.50
installed as the Current Software, and 4.1.4.4 installed as the Alternate
Software
The update process will migrate all your system configuration settings (except
the port subnet configuration) to the new software. However, the configura-
tion of the Network Setup pages will appear differently.
Network Setup Differences
After you have updated to 4.4.0.50, the tabs and information under the Net-
work area will be changed. There are some key differences in how network
configuration is done under 4.4.0.50.
■ Configuration settings for the DHCP server, domain name, DNS and
WINS server addresses, are now configured on a Global Subnet Group
basis on the Access Control Server, rather than per individual Access
Controller. These settings, as previously defined for the Access
Controllers in your system, are automatically transferred and the
corresponding Global Subnet Groups are created as part of the update
process.
■ Each Access Controller may have multiple tagged VLANs and subnets
defined as uplink subnets, in addition to a default, untagged subnet.
Upon update, the Access Controller’s previously-configured subnet (and
default gateway) becomes the untagged default subnet for the Access
Controller. Additional subnets can be defined individually on an Access
Controller, or can be defined on the Access Control Server as Global
Subnets, and then associated with VLAN tags on individual Access Con-
trollers.