Wireless Access

last person joined: 17 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

HA Fast Failover - failure scenario

This thread has been viewed 1 times
  • 1.  HA Fast Failover - failure scenario

    Posted Nov 10, 2015 08:10 PM

    Hi there,

     

    I have a couple of questions regarding HA fast failover in the following scenario.

     

    2 x 7205 controllers deployed in different datacentres (no stretched VLANs).

     

    First controller configured as Master and 'Active' in HA group.

    Second controller configured as Local and 'Standby' in HA group.

     

    As I understand, only one LMS IP is configured (HA active address) and when the AP connects it establishes a tunnel to the secondary controller as well.

     

    What happens if, following failure of the master controller, an AP reboots - it won't be able to communicate with the Master to get LMS IP address? Or does it cache the information about the secondary controller?

     

    Also, in an HA fast failover scenario, will all clients be disconnected when the AP's start to use their standby tunnel? (Egress tunnel is different L3 subnet at each datacentre).

     

    TIA!

     



  • 2.  RE: HA Fast Failover - failure scenario

    Posted Nov 10, 2015 08:27 PM

     

    If the AP reboots while attached to the Standby controller and the Active controller still down then the AP won't be able to find the Standby controller , you will need to configure the Standby as the Backup LMS IP so the AP is able to find the Standby Controller while the Active Controller still down.



  • 3.  RE: HA Fast Failover - failure scenario
    Best Answer

    EMPLOYEE
    Posted Nov 10, 2015 08:36 PM

     

    Also, in an HA fast failover scenario, will all clients be disconnected when the AP's start to use their standby tunnel? (Egress tunnel is different L3 subnet at each datacentre).

     

    TIA!

     


    Access points send a deauth to all clients attached when they fail over to their secondary controller.  The client has an opportunity to perform a full authentication and get an ip address from a new subnet, as a result.