Wireless Access

 View Only
Expand all | Collapse all

Moving RAPs between non-clustered Data Centers

This thread has been viewed 6 times
  • 1.  Moving RAPs between non-clustered Data Centers

    Posted Sep 19, 2024 04:23 PM

    Hello All,

    I am trying to update a wireless controller in a data center that controls vpn connections and RAPs (505H). I am trying to move two test RAPs I have from the data center to a controller in a second data center. I click on the RAPs and then click provision. I enter the ip address I want the RAPs to join and provision them as RAPs. The RAPs reboot and go through the process of upgrading since the controller they are moving to are on newer code 8.10.0.6. I notice after awhile that they seem to join the controller but they are in a down state and are also showing the flags R-c2. 

    The two controllers do not have the same VPN certificate. I am not sure if that matters. I am kinda new to these RAPs. I also see the following in the logs:

    User (mac address) Failed Authentication (Processing FETCH_RSP on DBType(13))

    Any help or links to documentation would be greatly appreciated.



  • 2.  RE: Moving RAPs between non-clustered Data Centers

    Posted Sep 23, 2024 11:54 AM

    If you are not familiar with setting up RAPs, I'd recommend to work with your Aruba partner, or open a case with support on what the FETCH_RSP. This probably is an issue with the authentication/allowlisting service for your RAPs which can be done in multiple ways but if you have multiple controllers needs to be centralized or synchronized.

    The Authentication Failed is probably because the RAP is only allowlisted on one of your controllers, or RADIUS authentication does not work from both sites.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------