Wireless Access

last person joined: yesterday 

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

Controller High Avaialbility

This thread has been viewed 1 times
  • 1.  Controller High Avaialbility

    Posted Feb 25, 2015 11:11 PM

    Hello, Im going to be setting up a new 7200 controllers for HA to an active already configured 7200. Active/standby configuration. I see how to complete this in the user guide. A few questions I dont see or overlooked are: 

     

    When the second controller is setup in the HA group as standby, does the config from the active controller sync to the standby? 

    After the HA group and config - is a controller reboot required? 

    As for inter-controller heartbeat, is there a crossover cable that needs to be connected between the 2 controllers? 

     

    thanks 



  • 2.  RE: Controller High Avaialbility

    EMPLOYEE
    Posted Feb 25, 2015 11:16 PM
    1) no, this is done via the master/local relationship or the master/backup relationship

    2) no reboot required 

    3) inter-controller heartbeats are sent over the existing network. 


    Thanks, 
    Tim


  • 3.  RE: Controller High Avaialbility

    Posted Feb 26, 2015 12:09 AM
    So if I make one controller active, does it take the master role and the standby becomes backup, or do I need to configure that separately?

    Jeremy Rouse
    Technical Specialist II, Bird Rock Systems, Inc.
    Phone: (858) 346-1384

    "We Build Rock Solid Solutions"
    www.birdrockusa.com


  • 4.  RE: Controller High Avaialbility

    EMPLOYEE
    Posted Feb 26, 2015 07:33 AM
    If you are doing master-local and the LMS-IP is pointed to the local, the APs will build a standby tunnel to the master when you assign an HA group. 


    Thanks, 
    Tim


  • 5.  RE: Controller High Avaialbility

    Posted Feb 26, 2015 10:56 AM

    Ok, so I take it you're telling me that redundancy (master/local) is a requirment before building an HA group?



  • 6.  RE: Controller High Avaialbility
    Best Answer

    EMPLOYEE
    Posted Feb 26, 2015 07:46 PM

    No. It's just the more common method.

     

    If you are doing master/master-standby, you can still use AP fast failover, but intercontroller heartbeats are not supported for this topology.

     

     



  • 7.  RE: Controller High Avaialbility

    Posted Mar 05, 2015 02:14 PM

    thanks resolved 



  • 8.  RE: Controller High Avaialbility

    Posted Feb 14, 2017 01:26 PM

    I think this is the part where I get a little mixed up.

     

    If using master-backup master (no locals) configuration and ultimately using HA, then what IP is passed to the APs as the standby controller.

     

    For the example configuration below (for my lab environment)

     

    interface vlan 1
            ip address 10.3.1.99 255.255.255.0

     

    master-redundancy
      master-vrrp 1
      peer-ip-address 10.3.1.249 ipsec 38abf8a843e037c768d137a778b65eed67f6cf96dc6903b6

     

    vrrp 1
      priority 110
      ip address 10.3.1.250
      vlan 1
      no shutdown

     

    ha group-profile "HA Group 1"
       preemption
       state-sync
       pre-shared-key b5ea51fbaaeee697dc7e290426df8eb71d601534bac85c53
       controller 10.3.1.249 role standby
       controller 10.3.1.99 role active

     

     

    Essentially I would provide the LMS IP for an AP group as the 10.3.1.99 address, and it will provide 10.3.1.249 as the standby controller. Totally ignoring the VRRP address of 10.3.1.250.

     

    Limited lab, so I'm not sure if I can actually produce a failover situation to see if this works. I'm looking to see what configuration the AP received.

     



  • 9.  RE: Controller High Avaialbility

    Posted Feb 16, 2017 12:26 PM

    I've clarified my own confusion by carefully reading (and re-reading the User Guide). It would totally ignore VRRP address.

     

    ap-system profile would have to be configured as such

    lms-ip 10.3.1.99

    bklms-ip 10.3.1.249

     

    posted config was correct for the most part except the following corrections

     

    ha group-profile "HA Group 1"
       preemption
       state-sync
       pre-shared-key b5ea51fbaaeee697dc7e290426df8eb71d601534bac85c53
       controller 10.3.1.249 role dual
       controller 10.3.1.99 role dual

     

    Can someone verify my statements?