The “HA Group” feature enables fast failover. ![]() During a failover, the AP would connect to the standby after VRRP changes. You would use the VRRP address for the connection between AP and controller. In production environments, 10 minutes is ok as well. This is to make the waiting time shorter. I have set the synchronization time to 1 minute. Synchronization doesn't include Captive Portal Custom data Last L2 synchronization time: Mon Nov 27 04:41:22 2017įrom Master Switch at 10.201.201.11: succeeded Synchronization doesn't include Captive Portal Custom data (Standby) * #show database synchronize L2 Periodic synchronization is enabled and runs every 1 minute 元 Synchronization took less than one second License Database backup file size: 5168 bytesĬPSec Database backup file size: 3224 bytes IAP Database backup file size: 3750 bytesĪirgroup Database backup file size: 3052 bytes Global AP Database backup file size: 12953 bytes Local User Database backup file size: 38393 bytes WMS Database backup file size: 31093 bytes To Secondary Master Switch at unknown IP address: succeeded To Master Switch at 10.201.201.12: succeeded Last 元 synchronization time: Secondary not synchronized since last reboot Last L2 synchronization time: Mon Nov 27 04:41:29 2017 To check if it is up and running use the command below: (Master) #show database synchronize It could take some minutes to form the master redundancy. “Submit” the changes and redo the configuration on the standby, except for the IP address. For this lab, I use an “IPSec Key” for “Authentication”. “Submit” the changes and go down to the controller hierarchy again, but the same configuration page: Master Standby – Create Master RedundancyĪdd the “Master VRRP” information, this is the VRRP from above and the “IP address of the peer”. On the master, go to the “Mobility Controller” configuration hierarchy and go to “Configuration–>Services–>Redundancy” and select “Master Redundancy”: Master Standby – Database Synchronization The next step is to enable database synchronization. Priority 100, Advertisement 1 sec, Preemption Enable Delay 0 Tracking is not enabled (Standby) * (config) #show vrrp Priority 110, Advertisement 1 sec, Preemption Enable Delay 0 You can check on the CLI: (Master) (config) #show vrrp For priority use the value of 100, which is the default.Īfter some seconds, VRRP is up and running. “Submit” the configuration and configure the same, except for the priority, on the standby. Set the “Admin state” to up and select the VLAN. I also use pre-emption to make sure the master is master again after he is back. I set the “Priority” of the master to 110, to make sure he is always the master. Enter an “Authentication password” and specify the VRRP “IP address”. So both controllers have IP addresses in that VLAN and the controller IP is in this VLAN as well. Use a meaningful “Description” to avoid confusion later on. Add a new “Virtual Router” with the “+” sign: Master Standby – Create VRRP Make sure, you are in the device hierarchy and not in the “Mobility Controller” hierarchy. On the master, go to “Configuration–>Services–>Redundancy” and select the “Virtual Routing Table”. In the future, I name them master and standby. Login to the one, which will be the active master. ![]() You have configured them with the initial setup wizard to standalone controllers and they have rebooted. Preferably fresh vom the factory or after a factory reset. To start with master redundancy, I assume you have the two controllers running in standalone mode. The first step to build the above design is to create the master redundancy. During failover, the AP fails over to the tunnel to the standby controller. With the HA Group configuration, the AP’s creates a tunnel to each of the controllers. To create minimal downtimes during failover, I also create an HA Group. If the master fails, you can use the licenses on the standby for 30 days. I use the master redundancy configuration to synchronize the configuration, user data and of course the licenses. The two controller run in standalone mode. The design looks like this, from a logical point of view: Master Standby – Design But you can use a variation of the fast failover feature. Only the active controller can terminate AP’s in this design. Keep this in mind during the setup of the controller. The Master Standby design requires two controllers, obviously. So this is just a plan B if you cannot use the benefits of an implementation with VMM. Just to make it clear, you get the most features, the most benefits and the most outcome from a deployment with VMM. ![]() Likely the same design as with ArubaOS 6.x. So the big question is how to build an environment with ArubaOS 8 and two controllers. Many customers deploy two controllers today. ![]() This time, I will not include the VMM in my scenario. In the last posts about ArubaOS 8, I talked a lot about Virtual Mobility Master.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |