HiWe have 2 local controllers at 1 of our sites. The master controller is located at another site. I am trying to set up local/local redundancy. There are 2 VRRP Ids each set up on local controllers.On controller 1 the VRRP config isvrrp 161 priority 110 ip address 10.x.x.9 description "Initial-Primary" vlan 19 no shutdown!vrrp 162 ip address 10.x.x.8 description "Initial-Standby" vlan 19 no shutdownOn controller 2 the VRRP config isvrrp 161 ip address 10.x.x.9 description "Initial-Standby" vlan 19 no shutdown!vrrp 162 priority 110 ip address 10.x.x.8 description "Initial-Primary" vlan 19 no shutdownThe scenario is that we want to split the APs 50/50 across the 2 local controllers so in the event of a controller failure, the APs will failover to the other controller. When we test this, initially the AP will failover, but as soon as the failed controller comes back up the AP will fail back to the original controller. We do not want this to happen. If the failed controller keeps bouncing, the APs will just keep failing between controllers. We want the APs to failover but stay on the second controller so we can then manually move them back when the controller is fully operational again.I assumed that not enabling router pre-emption in the virtual router config would mean the AP would failover, remaining on the the new controller until some sort of manual intervention.Does anyone have any ideas how to achieve what we want?ThanksRoy
Can you point me to any document that explains the various tracking options? My searches so far don't explain it fully.
Should each vrrp on each controller be configured identically? e.g. if preemption is configured on 1 controller but not the other, would it cause any issues?
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.