MSM7xx Controllers Configuration Guide v6.4.0

Each profile must be assigned to an AP as well as a controller. This is done to ensure that when a
user logs in on an AP installed on the same subnet as the home network, traffic is not routed through
the controller, but is sent directly onto the network via the Ethernet port on the AP. For example:
• When User A logs onto AP 1, RADIUS returns the VLAN ID Net1. Since Net1 is defined as a
home network on AP 1, traffic is sent directly onto network 1 via the Ethernet port on the AP.
• When User A roams to (or logs into) AP 2, RADIUS returns the VLAN ID Net1. Since Net1 is
not defined as a home network on AP 2, MTM tunnels the users traffic back to network 1.
A RADIUS account is defined for each user with attributes set as follows to identify the home network
using a network profile name:
Network 2 usersNetwork 1 usersRADIUS attribute
802802Tunnel-Medium-Type
Net2Net1Tunnel-Private-Group-ID
VLANVLANTunnel-Type
Configuration overview
The following sections provide a summary of the configuration settings needed to enable MTM
support only. It is assumed that installation and configuration of all controllers and APs so that they
are fully operational on the network was performed as explained in the other chapters in this guide.
Controller 1 configuration
Mobility domain
1. Select Controller >> Management > Device discovery.
• Select Mobility controller discovery.
• Select This is the primary mobility controller.
(For a complete screenshot of this page, see “Defining the mobility domain” (page 291).)
2. Select Save.
Scenario 4: Assigning home networks on a per-user basis 313