Release Notes 4.4.0.50

Release Notes, Version 4.4.0.50

Other browsers, such as earlier versions of Internet Explorer, earlier version of Netscape, or

Safari (Macintosh) may not display all pages or data correctly.

UPGRADE NOTES

Important: Please read the ProCurve Secure Access 700wl Series Software Version

4.4.0.50 Update Guide for instructions on updating your systems that currently run

software version 4.1.3.93.

The update process is a two-step process, requiring an intermediate update to software version

4.1.4.4 before updating to 4.4.0.50. If you do not update through the intermediate version, you

will not be able to downgrade back to the 4.1.3.93 software should the need arise.

The ProCurve Secure Access 700wl Series Software Version 4.4.0.50 Update Guide may be

downloaded in PDF format from the HP ProCurve Technical Support web site at

http://www.procurve.com.

Important: Back up your systems before upgrading to the version 4.4 software!

CLARIFICATIONS AND USAGE NOTES

• The Integrated Access Manager 760wl no longer supports remote Access Controllers, the

ProCurve Access Controller 720wl (J8153A) or the ProCurve Switch xl Access Controller

Module (J8162A) A 760wl can only be used as a stand-alone unit.

• Release 4.1 on an Access Controller will not work with release 4.4 on an Access Control

Server.

• After migrating to version 4.4.0.50, a downgrade can only be made to version 4.1.4.4. If the

alternate version is lower, 4.1.4.4 must be obtained to ensure a proper downgrade. For more

information, see “Downgrading to the Previous Release” in the ProCurve Secure Access

700wl Series Software Version 4.4.0.50 Update Guide.

• Network and subnet configuration data is split between local network information and global

network information. Configuration data that is likely to be shared between different Access

Controllers is stored in global subnet groups. This includes information like DNS, WINS and

domain names. These fields are entered manually or can be automatically set from

information in a DHCP lease.

If a global subnet group used by a local subnet on an Access Controller is deleted, the

configuration information is lost. The subnet group may be automatically created as a

placeholder, but the DNS, WINS and other settings must either be manually set or

regenerated via a DHCP lease renewal. If the information can be obtained through DHCP,

then the information may be renewed by deleting a related local subnet, waiting about 10-15

seconds and then re-entering the local subnet configuration for the subnet. The lease should

be renewed and the information in the lease renewal will be used to recreate the global subnet

group.

• The failover functionality of the built-in RADIUS server when in proxy mode is as follows: