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

How to setup controller redundancy (Aruba 620 to Aruba 620)

This thread has been viewed 0 times
  • 1.  How to setup controller redundancy (Aruba 620 to Aruba 620)

    Posted May 14, 2015 09:39 PM

    Do I need to have a same Firmware Image? What Licenses do I need to have? What Firmware Image that will support this redundancy? How will be the Configuration? does the 2 Controllers need to be in the same subnet?

     

    Thanks!



  • 2.  RE: How to setup controller redundancy (Aruba 620 to Aruba 620)

    EMPLOYEE
    Posted May 14, 2015 09:45 PM

    Take a look at these:

     

    Chapter 3: http://community.arubanetworks.com/aruba/attachments/aruba/Aruba-VRDs/22/1/Campus%20Redundancy%20Models.pdf

     

    http://www.arubanetworks.com/techdocs/ArubaOS%206_3_1_Web_Help/Web_Help_Index.htm#ArubaFrameStyles/VRRP/Redundancy_Parameters.htm

     

    TL;DR

    Master-Standby requires same subnet for VRRP, Master-local does not. Controllers must be running the same firmware.



  • 3.  RE: How to setup controller redundancy (Aruba 620 to Aruba 620)

    Posted May 15, 2015 12:06 AM

    Hi,

    Aruba supports two different types of redundancy,

    1. Master-Standby : this will run on VRRP hence bot the controllers need to be in the same subnet (VLAN) but it doesn't require any license.

    2. Master-Local : This is a distributed model with fail over redundancy,generally master will handle Configuration, ARM IDS etc and APs will be terminated on Local. Here both the controllers are assumed to be deployed different locations (Master - Head office, Local- Branch office) hence they need not be in the same subnet and does not require any license.

     

    For both it required to have same image and licenses ( AP, PEF, RFP etc..)

     

    Hope you got some more clarity, please feel free for any further clarity on this.