MSM7xx Controllers Configuration Guide v6.4.0

User A roams from AP 1 to AP 2
W
L
A
N
10.2
1
User A
W
L
A
N
User A
1
LAN port
192.168.10.1/24
Primary
mobility
controller
2
LAN port
192.168.20.1/24
L3 switch
Network 1
192.168.10.0
20.2
2
Network 2
192.168.20.0
Mobility
controller
Local networks
In order for a wireless users traffic to be sent to the appropriate destination within the mobility
network, local networks must be defined on controllers, and optionally APs.
When a user is roaming, the path to the users home network cannot end at an AP. This means that
each home network that is assigned to a user must be defined as the local network on at least one
controller in the mobility domain.
• When an AP is directly connected to a users home network, the users data will only reach the
wired network through the APs Ethernet port when the user is directly connected to the AP.
• When roaming, the users traffic is always tunneled to the controller that provides the data
path to the users home network.
In the previous example, when User A is directly connected to AP 1, traffic reaches Network 1 via
the APs Ethernet port. When User A roams to AP 2, traffic reaches Network 1 via the LAN port
on controller 1.
Mobility controller discovery
The wireless mobility feature defines a mobility domain, which is an interconnection between
multiple controllers for the purpose of exchanging mobility information on wireless users. For more
information, see “Mobility traffic manager” (page 285).
For the controllers to interconnect, each must have the Mobility controller discovery option enabled.
In addition, one controller must be defined as the primary mobility controller. It acts as the central
site for distribution of mobility information.
There can only be one primary controller for each mobility domain. On all other controllers set IP
address of primary controller to the IP address of the primary controller.
Mobility controller discovery 289