MSM7xx Controllers Configuration Guide v6.4.0

IMPORTANT:
• MTM is only available on non-access-controlled VSCs.
• The same VSCs must be defined on all controllers in the mobility domain, even on controllers
that are not managing any APs.
The mobility domain
The mobility domain is an interconnection between controllers allowing for the exchange of
information about wireless users and the home/local networks managed by controllers. The mobility
domain can span multiple controllers and controller teams, whether they are installed on the same
subnet or on different subnets, and includes all controlled APs managed by the controllers.
In the following example the mobility domain spans three controllers and their APs operating on
three different subnets. (On an MSM720, replace LAN port with Access network in the following
diagram.)
W
L
A
N
LAN port
192.168.10.1/24
L3 switch
Primary
mobility
controller
1
1
2
3
L3 switch L3 switch
LAN port
192.168.20.1/24
LAN port
192.168.30.1/24
W
L
A
N
W
L
A
N
W
L
A
N
W
L
A
N
W
L
A
N
3 4 5 62
Mobility
controller
Mobility
controller
192.168.10.0 192.168.20.0 192.168.30.0
MTM makes use of the mobility domain to locate the home network for roaming users, or the target
network when tunneling traffic to a specific network on the wired infrastructure.
For each mobility domain, one controller is defined as the primary mobility controller. This controller
acts as the central site for the distribution of mobility information to all other controllers. (When
controller teaming is active, an entire team is defined as the primary mobility controller. See
“Mobility support” (page 273).)
NOTE:
• All controllers in the mobility domain must be running the same software version. This means
that the first two numbers in the software revision must be the same. For example: All controllers
running 5.6.x, or all controllers running 5.7.x.
• Discovery automatically takes place on both the LAN port and Internet port. VLANs are not
supported.
Key concepts 287