Users Guide

Dell PowerConnect ArubaOS 5.0 | User Guide IP Mobility | 401
Configuring a Mobility Domain
You configure mobility domains on master controllers. All local controllers managed by the master controller
share the list of mobility domains configured on the master. Mobility is disabled by default and must be explicitly
enabled on all controllers that will support client mobility. Disabling mobility does not delete any mobility-
related configuration.
The home agent table (HAT) maps a user VLAN IP subnet to potential home agent addresses. The mobility
feature uses the HAT table to locate a potential home agent for each mobile client, and then uses this
information to perform home agent discovery. To configure a mobility domain, you must assign a home agent
address to at least one controller with direct access to the user VLAN IP subnet. (Some network topologies may
require multiple home agents.)
Dell recommends you configure the switch IP address to match the AP’s local controller or define the Virtual
Router Redundancy Protocol (VRRP) IP address to match the VRRP IP used for controller redundancy. Do not
configure both a switch IP address and a VRRP IP address as a home agent address, or multiple home agent
discoveries may be sent to the controller.
Configure the HAT with a list of every subnetwork, mask, VLAN ID, VRRP IP, and home agent IP address in the
mobility domain. Include an entry for every home agent and user VLAN to which an IP subnetwork maps. If there
is more than one controller in the mobility domain providing service for the same user VLAN, you must configure
an entry for the VLAN for each controller. Dell recommends using the same VRRP IP used by the AP.
The mobility domain named “default” is the default active domain for all controllers. If you need only one
mobility domain, you can use this default domain. However, you also have the flexibility to create one or more
user-defined domains to meet the unique needs of your network topology. Once you assign a controller to a user-
defined domain, it automatically leaves the “default” mobility domain. If you want a controller to belong to both
the “default” and a user-defined mobility domain at the same time, you must explicitly configure the “default”
domain as an active domain for the controller.
Using the WebUI
The following procedure illustrates configuring mobility domain on a master controller.
1. Navigate to the Configuration > Advanced Services > IP Mobility page. Select the Enable IP Mobility
checkbox.
2. To configure the default mobility domain, select the “default” domain in the Mobility Domain list.
To create a new mobility domain, enter the name of the domain in Mobility Domain Name and click Add.
The new domain name appears in the Mobility Domain list.
3. Select the newly-created domain name. Click Add under the Subnet column. Enter the subnetwork, mask,
VLAN ID, VRIP, and home agent IP address and click Add. Repeat this step for each HAT entry.
4. Click Apply.
Using the CLI
The following command configures mobility domain on a master controller.
router mobile
ip mobile domain <name>
hat <subnetwork> <netmask> <vlan-id> <home-agent-address>
The VLAN ID must be the VLAN number on the home agent controller.
To view currently-configured mobility domains in the CLI, use the show ip mobile domain command.
Note: All user VLANs that are part of a mobility domain must have an IP address that can correctly forward layer-3 broadcast
multicast traffic to clients when they are away from home network.