User guide

Summit WM20 User Guide, Software Release 4.2 97
5 WM Access Domain Services Configuration
This chapter discusses WM Access Domain Services (WM-AD) configuration, including:
“Topology for a WM-AD” on page 98
“Assigning Wireless AP Radios to a WM-AD” on page 106
“Authentication for a WM-AD” on page 108
“Defining Accounting Methods for a WM-AD” on page 120
“Defining RADIUS Filter Policy for WM-ADs and WM-AD Groups” on page 121
“Configuring Filtering Rules for a WM-AD” on page 122
“Enabling Multicast for a WM-AD” on page 132
“Configuring Privacy for a WM-AD” on page 134
“Defining a WM-AD With No Authentication” on page 140
“Defining Priority Level and Service Class for WM-AD Traffic” on page 141
“Working with Quality of Service (QoS)” on page 143
“Configuring the QoS Policy on a WM-AD” on page 145
“Bridging Traffic Locally” on page 148
Setting up a WM-AD defines a virtual IP subnet for a group of wireless device users, where the Summit
WM Controller acts as a default gateway to wireless devices. For each WM-AD, you define its topology,
authentication, accounting, RADIUS servers, filtering, multicast parameters, privacy and policy
mechanism. When you set up a new WM-AD, additional tabs appear only after you save the topology.
A critical topology option to define for a WM-AD is the WM-AD type:
Routed WM-AD – User traffic is tunneled to the Summit WM Controller. (This is the default setup.)
Bridged at the AP WM-AD User traffic is directly bridged to a VLAN at the AP network point of
access (switch port).
VLAN bridged WM-AD – User traffic is tunneled to the Summit WM Controller and is directly
bridged at the controller to a specific VLAN. WIth this WM-AD type, mobile users become a natural
extension of a VLAN subnet.
Setting up a new WM-AD involves the following general steps:
Step one – Create a WM-AD name
Step two – Define the topology parameters
Step three – Configure the WM-AD
Before you can define the WM-AD topology parameters and configure the WM-AD, you must first
create a new WM-AD name.