Software Update Guide for 4.1.3.93 to 4.4.0.50

5
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.50 software, subnets and VLANs are defined on the uplink side,
through the Global Network and Local Networks pages. In this system you
would do the following:
1. Configure a Global Subnet and Global Subnet Group that matches the
upstream subnet.
2. On each Access Controller, define the appropriate VLAN using the Global
Subnet you just defined, or define a VLAN and subnet directly on the
Access Controller.
3. Create an Access Policy that ensures that the appropriate VLAN tag is
applied to designate traffic for the desired subnet.
The VLAN tag defined in the Access Policy is also used to determine what
subnet the DHCP request should specify for clients that should get a real
(non-NAT) IP address.
4. Create rows in the Rights Table that associate these Access Policies with
the appropriate authenticated clients.
In this way, authenticated clients can be associated with the appropriate
Access Policy (and thus VLAN and subnet) through a variety of criteria, such
as identity and group membership, without having to specify the port or
Access Controller through which the connection is made.
The next section discusses an example of how to configure the 700wl Series
system to use upstream VLANs/subnets.
Configuring Uplink Subnets
The simplified network topology shown in Figure 1 will illustrate how
upstream subnets are handled in software version 4.4.0.50.