Filter
Top Products
32 | Mobility Controller and Access Point Deployment Campus Wireless Networks Validated Reference Design Version 3.3 | Design Guide
With Mobile IP, the ArubaOS will automatically tunnel traffic between a roaming client’s original
controller (the ‘Home Agent’) and the controller where the user currently terminates (‘Foreign Agent’).
With Mobile IP and automatic tunneling, users are able to roam the enterprise without a change of IP
address even when they are connected to controllers where their original subnet does not exist.
ArubaOS Mobility Domain
The ArubaOS Mobility Domain is the implementation of mobile IP addressing specified in RFC 3344,
also known as Layer 3 roaming. Roaming with a Mobile IP device allows the client to stay connected to
services and removes the necessity to re-authenticate Layer 3 services as the point of attachment to the
network changes. The Aruba solution extends the RFC functionality in that it requires no special
software to be loaded on the wireless client. The Aruba Mobility Controller automatically handles the
location changes without client intervention or client side software configuration.
An Aruba Mobility Domain is a logical construct that defines a group of controllers physically close
enough to one another that it could be reasonable that a user would roam between them in a single
session. You can scale your Mobility Domain from a single domain on a limited number of controllers to
multiple domains; each handling a separate country, campus, or building depending on your network
design and business needs. Controllers can exist in one or more Mobility Domains at the same time,
much the way a Border Area Router exists in more than one Area in OSPF. The Mobility Domain must
be explicitly configured to allow roaming between the various controllers.
arun_050
Home network
Server
Roaming
client
Traffic to client
Traffic from client
Foreign network
arun_073
Home
Agent
Foreign
Agent
172.16.20.1
172.16.20.1
LAN
MD1
Los Angeles
Client travels