Wireless Access

 View Only
last person joined: 2 days ago 

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

Mobility Controller Redundancy

This thread has been viewed 68 times

  • 1.  Mobility Controller Redundancy

    Posted Dec 10, 2020 04:26 AM
    Hi community,

    i have a aruba wifi installation with a single aruba 7205 mobility controller and a few aruba 305 access points in our headquarter.
    Also i have installed a few aruba 305 access points in our secondary locations, which are configured as remote access points.

    Now I' ve got a second aruba 7205 mobility controller for redundancy.

    My question is, what redundancy configuration would be the best for my enviroment?
    The "HA group" configuration or the "VRRP" configuration?

    All SSIDs are tunneled to the mobility controller.

    Thanks in advance.

    Regards


    ------------------------------
    Christopher vBargen
    ------------------------------


  • 2.  RE: Mobility Controller Redundancy

    Posted Dec 10, 2020 04:27 AM
    Hi community, i have a aruba wifi installation with a single aruba 7205 mobility controller and a few aruba 305 access points in our headquarter. Also i have installed a few aruba 305 access points in our secondary locations, which are configured as remote access points. Now I' ve got a second aruba 7205 mobility controller for redundancy. My question is, what redundancy configuration would be the best for my enviroment? The


    ------------------------------
    Christopher vBargen
    ------------------------------

    Original Message


  • 3.  RE: Mobility Controller Redundancy

    Posted Dec 12, 2020 06:29 AM
    In a solution very similar to yours we are using HA. The only difference is that we have use 2nd pair of 7220s to terminate local APs.

    ------------------------------
    [NesaM - ACMP|ACCP|ACDP]
    ------------------------------

    Original Message


  • 4.  RE: Mobility Controller Redundancy

    Posted Dec 13, 2020 07:44 AM
    You have to use VRRP instance for Master redundancy, Master-Standby.
    HA group for LMS and Backup and LMS. HA is failover time is less than comparing to VRRP.

    ------------------------------
    harendra nishshanka
    ------------------------------

    Original Message


  • 5.  RE: Mobility Controller Redundancy

    MVP EXPERT
    Posted Dec 14, 2020 04:10 AM
    Hi Christopher,

    You can add the controller and use it in Master-Standby mode. In this use case access points can only be terminated on the Master controller and not at the Master-Standby controller until the Master fail and the Standby controller becomes the Master. 

    VRRP configuration is required for the database sync. between the Master and Master Standby controllers. Be sure your current controller have a higher VRRP priority, because else you can wipeout your Master configuration when sync is start in the opposite direction, be careful with that one.

    HA (also known as AP fast failover) can be configured on top of your configuration. The advance of HA is that it pre-established IPSEC/GRE tunnels to Active and Standby controllers, and in case of a failover AP' can failover really quick because there is no wait time for establish the tunnels. From ArubaOS 6.4 or later the failover time with HA will be aprox. 1 sec.

    To let this work, be sure that the LMS IP and LMS Backup IP is configured in the AP System Profile. Note that when change this settings your AP's will be bootstrapped. A Master-Standby setup give you redundancy but no load balancing or active-active configuration, you Master Standby cannot terminate AP's until it becomes the Master and is therefore used as "spare". 

    In ArubaOS8 you can add a (virtual) Mobility Master (licenced) what make it possible to create a cluster where both controller are active and can load balanced users also access points. The Mobility Master comes with other features like; seamless failover, Airmatch (RF), live-migration and more. It's maybe not required in your current setup but known when you have a cluster managed by an ArubaOS8 Mobility Master, that for RAP termination each controller must be configured with is own WAN IP address.   

    ------------------------------
    Marcel Koedijk | MVP Expert 2020 | ACMP | ACCP | Ekahau ECSE
    ------------------------------

    Original Message