Aruba Networks Version 3.3 manual Master Controller Redundancy

Page 25

Master Controller Redundancy

To achieve high availability of the Master Controller, use the Master Redundancy method. In this scenario, two controllers are used at the Management layer with one controller configured as an active Master and one configured as a standby Master. The two controllers will synchronize databases and RF planning diagrams, and will run a Virtual Router Redundancy Protocol (VRRP) instance between them accessed by a Virtual IP (VIP) address. This is the address given to Access Points attempting to discover a Mobility Controller, and is used for network administration.

		Active	Periodic database	Standby
		Master	Periodic database	Master
	GRE	Master	synchronization	Master
			synchronization

VRRP

keepalives

PAPI keepalives

One Mobility Controller is always the Active Master Controller, and the other one is always the Standby Master Controller. Users managing the system will always log into the Active Master. It is not recommended that pre-emption be enabled on this setup. This configuration is known as "Active- Standby" redundancy.

In the Aruba Validated Reference Design, the recommended controller model to serve as a Master is the MMC-3600. The recommended network attachment method is to have each controller configured in a full mesh with redundant links to separate data center distribution switches.

Listed below is an example of the configuration of the “initially-preferred master”.

vrrp 22 vlan 22

ip address 10.200.22.254 priority 110 authentication <password> description Preferred-Master tracking master-up-time 30 add 20 no shutdown

database synchronize period 60 database synchronize rf-plan-data

The following shows the corresponding VRRP configuration for the peer Master Controller.

vrrp 22 vlan 22

ip address 10.200.22.254 priority 100 authentication <password> description Backup-Master tracking master-up-time 30 add 20 no shutdown

database synchronize period 60 database synchronize rf-plan data

Campus Wireless Networks Validated Reference Design Version 3.3 Design Guide

Mobility Controller and Access Point Deployment 25

Image 25

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