Aruba Networks Version 3.3 manual Branch Office Deployment

Page 73

Redundancy in this model is handled via Master redundancy, with both controllers acting as a Master Mobility Controller. One controller will be in standby, and should be deployed such that it is not serviced by the same power and data connections as the primary Master. Both Mobility controllers are typically deployed in the same data center. As with the Small Network Deployment, the Management and Aggregation layer are coresident in the same production controllers.

Figure 3 Redundant Master Mobility Controllers deployed in the network data center

Internet

Data center

The typical controllers that would be selected for this type of deployment are the MMC-6000 series controllers or the Multiservice Module embedded in the MMC-6000 chassis based controller. The chassis approach offers the advantage of redundant power supplies for greater reliability. The choice should be made based on the size of the network and the expected growth patterns.

Branch Office Deployment

Many large organizations have remote sites that do not have a local IT staff. It is common that such locations have high bandwidth, high availability links that exist to a central data center. For these deployments, wireless redundancy is typically handled across the WAN link to the central data center instead of placing a redundant controller onsite. There may be some type of on-demand backup connectivity in the event of a primary WAN link failure.

The recommended reference architecture for this deployment model would include a single Local Controller that is deployed at each site, with the Master Controller in the central data center acting as the redundant controller. This redundancy model is termed “N+1” because the central controller is intended to provide continuity for the failure of just a few remote controllers at any given time. It requires that APs do not receive power via PoE from the Local Controller and that the Local Controller is not the default gateway for the local site.

The Master Controller is the backup for all Local controllers, and it should be scaled such that a number of sites could potentially encounter issues and remain operational with APs terminating on the Master Controller. The Master must be licensed according to the maximum number of APs and users expected to fail over at any one time. The Master Controller should be deployed in a redundant pair at the central data center to ensure availability. The Management and Aggregation layers are coresident in the data center controllers.

Campus Wireless Networks Validated Reference Design Version 3.3 Design Guide

Alternative Deployment Architectures 73

Page 72 Page 74
Image 73
Page 72 Page 74
Contents Campus Wireless Networks Validated Reference Design Version Crossman Avenue Sunnyvale, California Phone Fax Contents Chapter RF Planning and Operation Reference Documents Aruba Reference ArchitecturesContacting Aruba Networks IntroductionTelephone Support Aruba’s User-Centric Network Architecture Understanding Centralized Wireless LAN NetworksCentralized Wlan Model Introducing Aruba’s User-Centric NetworkArubaOS ArubaOS and Mobility ControllerMobility Controller Access Point Multi-function Thin Access PointsAir Monitor Aruba’s Secure Enterprise Mesh Network Mesh Portal or Mesh PointRemote AP Mobility Management SystemMobility Management System Proof-of-Concept Network PoC Network Physical DesignVlan PoC Network Logical and RF DesignProof-of-Concept Network Proof-of-Concept Network Campus Wlan Validated Reference Design Aruba Campus Wlan Physical ArchitectureAruba Campus Wlan Logical Architecture Data center ManagementMaster Campus Wlan Validated Reference Design Understanding Master and Local Operation Mobility Controller Access Point DeploymentMobility Controller High Availability Master Controller Redundancy Local Controller Redundancy Second Local controller has an opposite configuration Vlan Design Do Not Use Special VLANs Do Not Make Aruba the Default RouterVlan Vlan PoolsVLANs 10, 20, 30 User Mobility and Mobility DomainsMD1 ArubaOS Mobility DomainMaster Controller Placement Mobility Controller Physical Placement and ConnectivityLocal Controller Placement AP Placement, Power, and ConnectivityMobility Controller and Thin AP Communication AP Location and Density Considerations AP Power and ConnectivityOffice Deployment Active Rfid Tag Deployment Voice DeploymentMobility Controller Configuration Configuration Profiles and AP GroupsConfiguration Profiles Required LicensesAP group Profile TypesAP Groups SSIDs, VLANs and Role DerivationProfile Planning VLANs SSIDsRole Derivation Secure Authentication MethodsAuthenticating with Corporate Authentication Methods for Legacy Devices Authenticating with Captive PortalEmployee Role Configuring Roles for Employee, Guest and Application UsersGuest 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 Planning and Operation RF Plan ToolAdaptive Radio Management Page Minimum Scan Time Sec Quality of Service Voice over Wi-FiWMM and QoS Traffic Prioritization Voice Functionality and FeaturesNetwork Wide QoS Voice-Aware RF ManagementComprehensive Voice Management Voice over Wi-Fi LAN / WAN Controller Clusters Mobility Management SystemMultiple Master/Local Clusters Page Multiple Master/Local Clusters Licenses Appendix aLicenses Wlan Extension with Remote AP Appendix BWlan Extension with Remote AP Alternative Deployment Architectures Small Network DeploymentMobility Controller located in the network data center Medium Network DeploymentBranch Office Deployment Corporate data center DMZ Pure Remote Access Deployment
Top Page Image Contents