Wireless Access

 View Only
Expand all | Collapse all

MC, L2 REDUNDANCY CONTROLLER AND DIFFERENT AP MODELS

This thread has been viewed 17 times
  • 1.  MC, L2 REDUNDANCY CONTROLLER AND DIFFERENT AP MODELS

    Posted Nov 17, 2025 07:42 AM

    Hello Community,
    I'm reaching out to see if anyone has encountered the following scenario:

    We have an infrastructure with Mobility Conductor, two controllers configured in L2 redundancy, AP models 515, 615, and 635, and Cisco ISE as the authentication server.

    The issue I'm facing occurs with AP 635 units within the same AP group but on different controllers. When roaming between AP 635s, users experience frequent disconnections and instability. This behavior does not occur with AP 515 or AP 615 models.

    As a temporary workaround, I removed the AP 635 units from the affected area, but this situation is causing significant disruption for end users.

    The current software version running on the devices is 8.13.1 LSR.

    If anyone has experienced this issue and managed to resolve it, please feel free to reach out to me. Any guidance or best practices would be greatly appreciated.



    ------------------------------
    Francisco Pinto
    francisco.pinto@novatec-corp.com
    ------------------------------


  • 2.  RE: MC, L2 REDUNDANCY CONTROLLER AND DIFFERENT AP MODELS
    Best Answer

    Posted Nov 17, 2025 08:27 AM

    Hello @Francisco Pinto

    The issue you're experiencing seems to be a bug. It causes "beacon stuck events, watchdog resets, and random user disconnections".
     
    When I read the 8.13.1 release notes related to this issue, it confirms that it is a bug. However, they haven't released a hotfix for this issue yet.
     
    https://arubanetworking.hpe.com/techdocs/ArubaOS-8.x-Books/Release-Notes/813/ArubaOS-8.13.1.0-Release-Notes.pdf
    If you wish, you can quickly file a ticket with TAC and request when they will share the hotfix file.
    -------------------------------------------