Users Guide

648| IP Mobility Dell Networking W-Series ArubaOS 6.5.x| User Guide
3. The foreign agent delivers traffic to the mobile client.
4. Traffic sent by Mobile Client B is also tunneled back to the home agent.
Figure 84 Routing of Traffic to Mobile Client within Mobility Domain
Configuring Mobility Domains
Before configuring a mobility domain, you should determine the user VLAN(s) for which mobility is required.
For example, you may want to allow employees to be able to roam from one subnetwork to another. All
controllers that support the VLANs into which employee users can be placed should be part of the same
mobility domain.
Dell mobility domains are supported only on Dell controllers.
A controller can be part of multiple mobility domains, although it is recommended that a controller belong to
only one domain. The controllers in a mobility domain do not need to be managed by the same master
controller.
You configure a mobility domain on a master controller; the mobility domain information is pushed to all local
controllers that are managed by the same master controller. On each controller, you must specify the active
domain (the domain to which the controller belongs). If you do not specify the active domain, the controller
will be assigned to a predefined “default” domain.
Although you configure a mobility domain on a master controller, the master controller does not need to be a
member of the mobility domain. For example, you could set up a mobility domain that contains only local
controllers; you still need to configure the mobility domain on the master controller that manages the local
controllers. You can also configure a mobility domain that contains multiple master controllers; you need to
configure the mobility domain on each master controller.
The basic tasks you need to perform to configure a mobility domain are listed below. The sections following
describe each task in further detail. A sample mobility domain configuration is provided in Sample
Configuration on page 650.