Aruba Networks Version 3.3 manual ArubaOS Mobility Domain, MD1

Page 32

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.

	Roaming
Server	client
Server

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
	Home	MD1
	Agent	MD1
		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

Image 32

Contents Campus Wireless Networks Validated Reference Design Version Crossman Avenue Sunnyvale, California Phone Fax Contents Chapter RF Planning and Operation Aruba Reference Architectures Reference DocumentsContacting Aruba Networks IntroductionTelephone Support Understanding Centralized Wireless LAN Networks Aruba’s User-Centric Network ArchitectureIntroducing Aruba’s User-Centric Network Centralized Wlan ModelArubaOS and Mobility Controller ArubaOSMobility Controller Air Monitor Multi-function Thin Access PointsAccess Point Mesh Portal or Mesh Point Aruba’s Secure Enterprise Mesh NetworkMobility Management System Remote APMobility Management System PoC Network Physical Design Proof-of-Concept NetworkPoC Network Logical and RF Design VlanProof-of-Concept Network Proof-of-Concept Network Aruba Campus Wlan Physical Architecture Campus Wlan Validated Reference DesignAruba Campus Wlan Logical Architecture Data center ManagementMaster Campus Wlan Validated Reference Design Mobility Controller Access Point Deployment Understanding Master and Local OperationMobility Controller High Availability Master Controller Redundancy Local Controller Redundancy Second Local controller has an opposite configuration Vlan Design Do Not Make Aruba the Default Router Do Not Use Special VLANsVlan Pools VlanUser Mobility and Mobility Domains VLANs 10, 20, 30ArubaOS Mobility Domain MD1Mobility Controller Physical Placement and Connectivity Master Controller PlacementMobility Controller and Thin AP Communication AP Placement, Power, and ConnectivityLocal Controller Placement Office Deployment AP Power and ConnectivityAP Location and Density Considerations Voice Deployment Active Rfid Tag DeploymentConfiguration Profiles and AP Groups Mobility Controller ConfigurationConfiguration Profiles Required LicensesProfile Types AP groupProfile Planning SSIDs, VLANs and Role DerivationAP Groups SSIDs VLANsSecure Authentication Methods Role DerivationAuthenticating with Corporate Authenticating with Captive Portal Authentication Methods for Legacy DevicesConfiguring Roles for Employee, Guest and Application Users Employee RoleGuest Role Create a bandwidth contract and apply it to an AP group Create the block-internal-access policy Modify the guest-logon role Device Role Wireless Attacks Wireless Intrusion Detection SystemRole Variation by Authentication Method Rogue APs Page Mobility Controller Configuration RF Plan Tool RF Planning and OperationAdaptive Radio Management Page Minimum Scan Time Sec WMM and QoS Voice over Wi-FiQuality of Service Voice Functionality and Features Traffic PrioritizationNetwork Wide QoS Voice-Aware RF ManagementComprehensive Voice Management Voice over Wi-Fi Controller Clusters Mobility Management System LAN / WANMultiple Master/Local Clusters Page Multiple Master/Local Clusters Appendix a LicensesLicenses Appendix B Wlan Extension with Remote APWlan Extension with Remote AP Small Network Deployment Alternative Deployment ArchitecturesMedium Network Deployment Mobility Controller located in the network data centerBranch Office Deployment Corporate data center Pure Remote Access Deployment DMZ