Wireless Access

 View Only
last person joined: yesterday 

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

Remote Mesh Points Take Long Time Connect to Cluster

This thread has been viewed 4 times

  • 1.  Remote Mesh Points Take Long Time Connect to Cluster

    Posted Jun 02, 2020 05:24 PM

    Hi all,

    Previous version AOS 8.x when RAP and Remote Mesh Portal and Point can only terminate to a non-cluster controller. We have to designate a controller just for this purpose, no problem then and now.
    After upgrading to 8.4, the cluster can terminate RAP and Remote mesh portal. However, the Remote mesh point is not as good. The point will not connect to the portal for a long period. We have to let the point run overnight, probably after multiple self-reboots and it would show up. If the point power cycle, same long period for point to terminate at cluster. Console to the point shows it sticks at DHCP, it could not get an IP address.
    Environment: Point and portal are 303H, AOS 8.5.0.8. RAP and portal terminate at cluster of two 7220s. Portal provisions with static public VIP of the cluster, point LMS-IP  is the internal VIP of cluster.



  • 2.  RE: Remote Mesh Points Take Long Time Connect to Cluster

    Posted Jun 03, 2020 04:52 PM

    While I have deployed many Remote Meshes successfully, there are not many admins utilize this feature. I usually bump into a colleague who has no idea or only hears about the solution but not wanting to deploy because there are many cool solutions out there for SOHO, pricey, of course.

    I write this to promote the Remote Mesh so hopefully there are more users to implement it and when the problem arises, we have more voices to Aruba team to look for a solution like this one I posted.

     

    1. I use this guide to configure Remote Mesh: How do I set up a remote mesh portal
    2. I deploy Remote Mesh with 1 portal, 2 points to a remote site with about 20 users and guests
    3. I configure the portal to not serve clients, but for wireless back-haul from two mesh points.
    4. The RF for wireless back-haul configures for a-band
    5. The point serves clients on both g and a-band (if a-band is used for back-haul, they recommend to use g-band only for clients, but I found it seems to work OK this way when portal uses for RF back-haul only.)
    6. The important mesh troubleshooting is checking the mesh health with “show ap mesh topology”. I use PRTG for this purpose. Check out my post here: How to Monitor Aruba Wireless Mesh Back-Haul with PRTG.

    mesh.jpg