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
| Roaming |
Server | client |
|
Home network | Foreign network |
Traffic to client |
|
Traffic from client | arun_050 |
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.
Los Angeles
Home | LAN | |
MD1 | ||
Agent | ||
| Foreign | |
| Agent |
172.16.20.1
172.16.20.1
Client travels
32 Mobility Controller and Access Point Deployment | Campus Wireless Networks Validated Reference Design Version 3.3 Design Guide |
