MSM7xx Controllers Configuration Guide v6.4.0

Network requirements
The network that interconnects the controllers and APs that make up a mobility domain must not
block any of the following ports/protocols:
• UDP port 1194
• UDP port 12141
• UDP port 3000
• UDP port 3001
• UDP port 3518
• TCP port 5432
• Internet protocol number 47 (GRE)
• NAT must not be used. The IP address of each AP must be visible to the controller.
Home networks
A home network is the root network for a user within a mobility domain. The home network specifies
the network on which a users wireless traffic is sent onto the wired infrastructure. A users connection
is always local to their home network, regardless of where their wireless connection is made within
the mobility domain. For example, if a user roams between an AP that is directly connected to
their home network, to an AP on a different subnet, MTM creates a tunnel that connects the user
back to their home network.
When a user first connects to an AP, MTM must determine whether the user is at home (i.e.,
connected to the users home network) or roaming (connected to an AP on a different network).
MTM does this by comparing the home network assigned to the user with the list of local networks
associated with the AP.
• If a match is found, the user is considered to be at home and the users traffic is sent onto the
wired network via the APs Ethernet port.
• If no match is found, MTM then tries to locate the users network within the mobility domain.
If found, MTM creates a tunnel between the AP and the controller to carry the user's traffic. If
the network is not defined on any controller within the mobility domain, the user is blocked
(or assigned to the network on which the AP discovered the controller, depending on how
MTM support is configured on the VSC).
NOTE: Certain configuration settings on the controller may override the specific configuration
settings that you define on a VSC to assign user traffic to a home network. For details, see “Traffic
flow for wireless users” (page 221).
Example
In following example, User A roams between AP # 1 and AP #2. When connected to AP #2, User
A is identified as roaming and traffic is tunneled back to subnet 10.0 via controller 1 and controller
2. (On an MSM720, replace LAN port with Access network in the following diagram.)
288 Mobility traffic manager