Table of Contents
Advertisement
4
WM Access Domain Services
This chapter describes WM Access Domain Services (WM-AD) concepts, including:
"WM-AD overview" on page 141
"Setting up a WM-AD checklist" on page 142
"Topology of a WM-AD" on page 143
"RF assignment for a WM-AD" on page 145
"Authentication for a WM-AD" on page 145
"Filtering for a WM-AD" on page 146
"Data protection on a WM-AD - WEP and WPA" on page 148
"WM-AD global settings" on page 149
"Setting up a new WM-AD" on page 153
WM-AD overview
A WM-AD is an IP subnet designed to enable Wireless APs to interact with wireless devices. A WM-AD
is similar to a regular IP subnet. A WM-AD has the following properties:
Each WM-AD is assigned a unique identifier.
Each WM-AD is assigned a Service Set Identifier (SSID). The SSID does not have to be unique.
Each WM-AD is assigned a range of IP addresses for wireless devices. All of the wireless devices
share the same IP address prefix - the part of the IP address that identifies the network and subnet.
NOTE
If the WM-AD is in branch mode, the Summit WM Controller's DHCP server will not assign IP addresses to the
wireless devices. For a routed WM-AD, you can allow the enterprise network's DHCP server to provide the IP
addresses for the WM-AD by enabling DHCP Relay. The Summit WM Controller can also relay to an external
DHCP server.
The assigned addresses must be within range of the WM-AD definition and the controller must be defined in the
network as the path for traffic delivery to the mobile units. For more information, see
the WM-AD" on page
162.
These IP addresses are not virtual IP addresses. They are regular IP addresses and are unique over
the network. These IP addresses are advertised to other hosts on the network to exchange traffic
with the wireless devices in the WM-AD.
A single overall filtering policy applies to all the wireless devices within the WM-AD. Additional
filtering can be applied when the wireless user is authenticated by the Remote Authentication Dial-
In User Service (RADIUS) server. This does not apply for a bridged WM-AD.
When the Summit WM Controller creates a WM-AD, it also creates a virtual IP subnet for that WM-
AD. This does not apply for a bridged WM-AD at the WAP. It does apply for Bridge Traffic Locally
as SWM. In fact, the IP Address assigned to the interface of a Bridged at Summit WM WM-AD
needs to be in the same subnet as the mobile units otherwise problems might occur.
Summit WM User Guide, Software Version 5.3
"Using a DHCP relay for
141
Advertisement
Table of Contents
