Users Guide

On a master controller: On all controllers in the mobility domain:
l Configure the mobility domain,
including the entries in the home agent
table (HAT)
l Enable mobility (disabled by default)
l Join a specified mobility domain (not required for “default”
mobility domain)
Table 139: Tasks to Configure a Mobility Domain
You can enable or disable IP mobility in a virtual AP profile (IP mobility is enabled by default). When you enable
IP mobility in a virtual AP profile, the ESSID that is configured for the virtual AP supports layer-3 mobility. If you
disable IP mobility for a virtual AP, any clients that associate to the virtual AP will not have mobility service.
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.
In ArubaOS versions before 6.3, the home agent table (HAT) maps a user VLAN IP subnet to potential home
agent addresses. Starting from 6.3, when you enable mobility the controller to which the client connects for
the first time becomes its home agent. 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.)
It is recommended that 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.
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 the home network.
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.
In the WebUI
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.
Dell Networking W-Series ArubaOS 6.5.x | User Guide IP Mobility |
649