Software Update Guide for 4.1.3.93 to 4.4.0.50

ManualsBrandsHP ManualsComputer AccessoriesHP ProCurve Switch xl Access Controller Module

ProCurve Secure Access 700wl Series Software

Version 4.4.0.50 Update Guide

This document describes the process for updating the ProCurve Secure Access 700wl Series software

from version 4.1.3.93 to version 4.4.0.50. It also provides information on some of the differences in

functionality between these two versions, with information on how to reconfigure the system to take

advantage of these changes.

Related 700wl Series publications include:

■ Software Version 4.4.0.50 Supplement to the ProCurve Secure Access 700wl Series

Management and Configuration Guide

■ ProCurve Secure Access 700wl Series Management and Configuration Guide

ProCurve Networking periodically updates switch software and product manuals, and posts them

on the world wide Web. For the latest software release and publications for your ProCurve

networking product, visit http://www.procurve.com. Click on Software updates to check on the latest

software releases. Click on Technical support, then Product manuals (all) to check on the latest

publications.

Summary of content (14 pages)

PAGE 1
ProCurve Secure Access 700wl Series Software Version 4.4.0.50 Update Guide This document describes the process for updating the ProCurve Secure Access 700wl Series software from version 4.1.3.93 to version 4.4.0.50. It also provides information on some of the differences in functionality between these two versions, with information on how to reconfigure the system to take advantage of these changes. Related 700wl Series publications include: ■ Software Version 4.4.0.
PAGE 2
© Copyright 2005-2006 Hewlett-Packard Company, LP. The information contained herein is subject to change without notice. Publication Number 5991-3830 February, 2006 Applicable Products ProCurve Access Controller 720wl ProCurve Access Controller xl Module ProCurve Access Control Server 740wl ProCurve Integrated Access Manager 760wl (J8153A) (J8162A) (J8154A) (J8155A) Trademark Credits Microsoft®, Windows®, and Windows NT® are US registered trademarks of Microsoft Corporation.
PAGE 3
Contents Contents Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Updating the 700wl Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Network Setup Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Configuring Uplink Subnets . . . . . .
PAGE 4
PAGE 5
Introduction Introduction This document describes how to update a ProCurve Secure Access 700wl Series system from version 4.1.3.93 to version 4.4.0.50, and discusses how to reconfigure your system if you were using port subnets under 4.1.3.93. Version 4.4.0.50 provides a number of new features, including: ■ Significantly enhanced support for multiple 802.1Q VLANs.
PAGE 6
Updating the 700wl Series The enhanced support for 802.1Q VLANs is discussed in this document, as customers using port subnetting will need to reconfigure their system to use VLANs and subnets under the new software. Caution Because of the significant changes in the way subnets and VLANs are handled in release 4.4.0.50, it is not backward compatible with software version 4.1.3.93. However, to support a downgrade from 4.4.0.50 to 4.1.3.93, an intermediate release, version 4.1.4.4, must be used.
PAGE 7
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.
PAGE 8
Updating the 700wl Series There are now two tabs in place of the former Network Setup tab: Network configuration is now divided into Global Network settings and Local Networks settings. The Global Network page provides a picture of the entire set of network subnets present on the uplink ports of all the Access Controllers in the 700wl Series system, organized into Subnet Groups. The Global Network page centralizes the view of these subnets and the subnet groups of which they are members.
PAGE 9
Configuring Uplink Subnets 3. Use the Connection Profile in the Rights Table such that traffic that matched the Connection Profile would be associated with an Access Policy that would ensure that an appropriate VLAN tag would mark traffic for the desired subnet. One of the obvious disadvantages of port subnets is that traffic must connect to the system through a specific downlink port in order to get properly designated for the correct subnet. In the 4.4.0.
PAGE 10
Configuring Uplink Subnets Under version 4.1.3.93, to ensure that a given client has access to a specific subnet, the client would need to enter the 720wl on a specific downlink port. In the scenario in Figure 1, the Access Point the client connects through would determine the subnet to which the client is assigned. If a client gets associated to the wrong AP, his traffic will arrive at the wrong port, and regardless of client identity or any other factors, that traffic will not reach the correct subnet.
PAGE 11
Configuring Uplink Subnets Under 4.4.0.50, configuring VLANs and subnets involves the following steps: 1. The 720wl uplink port should be configured with the untagged default VLAN AutoSubnet_10.250.120.10, which is a member of the global subnet group AutoGroup_10.250.120.10. This VLAN is used to communicate with the 740wl, and to send any untagged traffic onto the network. The setting for the subnet and subnet group should match those configured on the 720wl under version 4.1.3.93. 2.
PAGE 12
Configuring Uplink Subnets 4. Add a set of rows to the Rights Table such that when a client is authenticated, he will be matched to the appropriate Access Policy for the subnet to which he should have access. For example, you might have a set of Identity Profiles defined that match the group Identity information returned with a successful RADIUS authentication—Accounting, Engineering, and so on.
PAGE 13
Downgrading to the Previous Release Downgrading to the Previous Release If for any reason you need to downgrade your systems to re-install the 4.1.3.93 software, you will need to perform several downgrade steps. Any changes you have made since upgrading will be lost. If you did not follow the update procedure specified above, by first installing version 4.1.4.4, then version 4.4.0.50, you will not be able to downgrade to version 4.1.3.93. To downgrade to 4.1.3.93, follow these steps: 1.