Software Update Guide for 4.1.3.93 to 4.4.0.50

6
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.
Under version 4.4.0.50, subnets are much more flexible. The uplink port on
the 720wl can be configured as a tagged member of each of the upstream
VLANs, and those same VLAN could be configured on the uplink port of
multiple 720wls, though none are shown in this figure. The Access Policy still
determines the VLAN tag to be associated with a specific client’s traffic, but
the client can be matched to the Access Policy based on its Identity Profile,
with no restrictions on where it entered the 700wl Series system.
Further, there are fewer restrictions in terms of the subnets themselves, as
each subnet may have its own configuration of gateway, DHCP server, DNS
services and so on (via the Global Subnet Group) rather than being restricted
to a single configuration determined by the Access Controller through which
the client is connected.
Figure 1. Network topology with multiple upstream VLANs/subnets
AP
720wl
740wl
Client
AP AP AP
10.250.120.10/24
Subnet A
Subnet B
Subnet C
Subnet D
10.200.20.x/24
Untagged
Untagged
Untagged: VLAN to 740wl
Tagged: VLAN to subnet
Switch
VLAN 20
10.200.30.x/24
VLAN 30
10.200.50.x/24
VLAN 50
10.200.40.x/24
VLAN 40