Management and Configuration Guide Supplement 4.4.0.50

4
Support for VLANs and Subnets
Support for VLANs and Subnets
Software release 4.4.0.50 has introduced some important changes and
enhancements regarding how VLANs and subnets are handled. Prior to ver-
sion 4.4.0.50, the only way to ensure that client traffic would be routed to a
specific upstream subnet was to configure a subnet address range on a
downlink port. This would cause the client to receive a real IP address within
that subnet, and the client traffic could also be tagged with an appropriate
802.1Q VLAN ID based on the downlink port through which they were con-
nected (through the Location/Connection Profile/Access Policy association).
In version 4.4.0.50, subnets are no longer associated with downlink ports; they
are now configured as an upstream VLAN on the Access Controller, on the
uplink side. Client traffic can now get its real IP address within a specific
subnet, and have its traffic tagged with the appropriate VLAN tag, based on
the Access Policy in force for the client. It does not need to enter the system
through any particular downlink port.
In order to implement this, configuration of key aspects of both the Access
Control Server 740wl and its associated Access Controllers has changed. The
previous Network Setup configuration has been split into two components,
the Global Network and Local Networks.
Global Network settings include the configuration of DHCP, DNS, and WINS
server settings, which are now configured for a Subnet Group, not per Access
Controller. It also provides a mechanism for defining global subnets, which
can then be associated with specific VLAN IDs on individual Access Control-
lers.
In Local Networks settings, the Basic Setup tab now provides the interface for
specifying VLANs to be associated with upstream subnets. The subnets can
be selected from the set of Global subnets defined under the Global Network
area, or can be defined locally. The other tabs previously found on the Network
Setup page (Advanced Setup, HTTP Proxy, and SSL, depending on the type of
device) are still provided.
Note: After upgrading from 4.1, each Access Controller will be configured with a
default untagged subnet that is the subnet configured for the Access Control-
ler under version 4.1.3.93. A corresponding Global Subnet Group will exists
that is configured with the DHCP server, domain, DNS and WINS information