Aruba Networks Version 3.3 AP Placement, Power, and Connectivity, Local Controller Placement

Page 34

least two connections setting up redundant links to two data center distribution switches. With the Active-Standby configuration recommended in this VRD, this yields a full mesh between the two controllers and the distribution switches. The MMC-3600 does not have redundant power supplies; connect each appliance to discrete power sources in the data center.

Data center

Master

 

File

Mobility

Web

Controller

 

 

 

 

 

PBX

 

 

Distribution

 

 

 

 

 

 

 

 

 

 

RADIUS

switches

 

 

 

 

arun_051

Local Controller Placement

The Local Controller should be connected to the distribution layer switches in an MDF or similar suitable location with backup power, with each Active-Active pair connecting to separate switches. Using the MMC-6000 Multiservice Mobility Controller as recommended by this VRD, each blade should be connected to its own distribution layer switch with two 10 Gigabit Ethernet connections bonded with Etherchannel. A fully populated MMC-6000 chassis with four blades require eight Gigabit connections. Each MMC-6000 chassis should contain redundant power supplies connected to discrete power sources.

Two 10 gigabit links

Distribution

Local

Distribution layer

Mobility

switch

Controller

 

AP Placement, Power, and Connectivity

Mobility Controller and Thin AP Communication

Mobility Controllers and thin APs work as a system. Configuration for all APs is automated and centralized on the Mobility Controller. Upon bootup, each AP uses DHCP to obtain its IP information then connects to the Local Controller to retrieve its initial configuration, and to check for firmware updates. Subsequent configuration changes are performed centrally within the Local Controller and pushed to each AP. If the firmware on the AP does not match the controller, the AP will automatically use either FTP or TFTP to upgrade itself to the new firmware stored on the Local Controller with no administrator intervention.

Communication between the AP and the Local Controller at the Aggregation layer occurs using a GRE tunnel established during the boot process. Because the GRE tunnel is in place, all wireless traffic is transmitted directly to the controller, so no special VLANs need to be deployed for APs; they will function over the existing infrastructure as would any other client. This avoids the “VLAN explosion” problem in some other architectures where every user VLAN must terminate on every AP throughout the enterprise. On the other side of the GRE tunnel, the user traffic is then switched to the correct

34 Mobility Controller and Access Point Deployment

Campus Wireless Networks Validated Reference Design Version 3.3 Design Guide

Page 33 Page 35
Image 34
Page 33 Page 35
Contents Campus Wireless Networks Validated Reference Design Version Crossman Avenue Sunnyvale, California Phone Fax Contents Chapter RF Planning and Operation Contacting Aruba Networks Aruba Reference ArchitecturesReference Documents 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 Access Point Multi-function Thin Access PointsAir Monitor 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 Vlan User Mobility and Mobility Domains VLANs 10, 20, 30ArubaOS Mobility Domain MD1Mobility Controller Physical Placement and Connectivity Master Controller PlacementLocal Controller Placement AP Placement, Power, and ConnectivityMobility Controller and Thin AP Communication AP Location and Density Considerations AP Power and ConnectivityOffice Deployment Voice Deployment Active Rfid Tag DeploymentConfiguration Profiles Configuration Profiles and AP GroupsMobility Controller Configuration Required LicensesProfile Types AP groupAP Groups SSIDs, VLANs and Role DerivationProfile Planning 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 Role Variation by Authentication Method Wireless Intrusion Detection SystemWireless Attacks Rogue APs Page Mobility Controller Configuration RF Plan Tool RF Planning and OperationAdaptive Radio Management Page Minimum Scan Time Sec Quality of Service Voice over Wi-FiWMM and QoS Network Wide QoS Voice Functionality and FeaturesTraffic Prioritization 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
Top Page Image Contents