MSM7xx Controllers Configuration Guide v6.4.0

If you are using MTM to tunnel the traffic from wireless users to their home networks, set the
following parameter to determine how MTM routes traffic if no home network is assigned to
a user (via their RADIUS account or local user account), or if the users home network is not
found in the mobility domain.
If no matching network is assigned
• Block user: User access is blocked.
• Consider the user at home: The users home network is considered to be the network
assigned to the APs Ethernet port and traffic is bridged locally by the AP.
4. Configure the Wireless security filters so that they do not interfere with roaming functionality.
In most cases, these filters should be disabled. If you need to use them, note that:
• The Restrict wireless traffic to: Custom option can be used provided that it restricts traffic
to destinations that are reachable from all subnets in the mobility domain.
• Neither the Restrict wireless traffic to: Access points default gateway nor Restrict wireless
traffic to: MAC address options can be used.
5. Select Save.
Binding a VSC to an AP
After you have defined a VSC, you need to bind it to all the APs in the mobility domain.
• Select Controller > Controlled APs > [group] >> VSC bindings and then the VSC configured
for mobility. The VSC binding page opens.
For VSC profile, select the VSC that you just configured for mobility.
You have the option of assigning an Egress network to the binding. When mobility is active on
the VSC, the Egress network is assigned as the users home network (unless a dynamic VLAN is
assigned to the user).
A number of configuration settings on the controller can affect how user traffic is routed. Some of
these settings may override the choices you make to assign user traffic to a home network. See
“Traffic flow for wireless users” (page 221).
Monitoring the mobility domain
The mobility overview page displays status information for the mobility domain. For example:
Monitoring the mobility domain 295