Software Update Guide for 4.1.3.93 to 4.4.0.50

4
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.
Under the Global Network tab, after the update, you should see one global
subnet group for each Access Controller in your system. By default they are
named with the base IP address of the Access Controller—for example,
AutoGroup_192.168.200.5. The group is configured with the settings from the old
Network Setup page for the Access Controller.
A global subnet is associated with each Subnet Group, also automatically
created for each Access Controller. The global subnet defines the subnet
itself—the subnet base address, subnet mask, and gateway, and is also named
with the IP address of the Access Controller—for example,
AutoSubnet_92.168.200.5.
With the auto-creation of these subnets and subnet groups, communication
from the 700wl Series systems to the network can occur via the untagged
subnets on the Access Controllers in the same way communication occurred
in the previous version of the system.
However, if you were using port subnets configured on downlink ports, and
the VLAN tag handling through Access Policies to designate traffic for specific
subnets, you may need to configure uplink subnets and VLANs to accomplish
the same results. Port-based subnets are no longer supported on downlink
ports—and the Subnets sub-tab under the Interfaces tab no longer exists.
Under software version 4.1.3.93, you could use port subnetting to designate
traffic for uplink subnets in the following way:
1. Define a subnet for a port that matches the upstream subnet. This will
cause clients connecting through this port that want a real (non-NAT) IP
address, to get an address in the desired subnet.
2. Create a Location defined as that specific port, and use that Location to
define a port-specific Connection Profile. You could filter for specific
VLAN traffic in the Connection Profile, so that only traffic from a specific
VLAN would match the Connection Profile.