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

Normal time for AP505 to connect to Controller

This thread has been viewed 16 times

  • 1.  Normal time for AP505 to connect to Controller

    Posted Aug 10, 2024 06:19 AM

    Dear Experts, 

    I am testing in my lab for a customer. Everything is connected directly so there should be any link delays. I have also opened wireshark since VMC is running on my laptop. I see too many ntp and dns queries from AP505 (factory reset), the AP doesnt connect to controller which is beyond a router (VSR in my case). How long usually a 505 AP takes to connect to controller on L3. Its almost 20 mins now but no sign on connecting to VMC



    ------------------------------
    iqbal
    ------------------------------


  • 2.  RE: Normal time for AP505 to connect to Controller

    Posted Aug 11, 2024 06:06 AM

    You do not mention whether you have the AOS 8 or AOS 10 environment. You write that you have a VMC controller, so I assume that you are using AOS 8.
    Aruba AOS APs follow certain algorithm when searching for the controller. They use DNS, DHCP or the Aruba Discovery Protocol (ADP). With ADP, APs send multicast and broadcast queries to locate the controller. As long as the AP and controller are in the same VLAN or IP subnet, no additional steps are required, the controller is found via ADP.

    If the controller is located behind a firewall or a router, as in your case, so-called controller Layer 3 discovery must be used.
    Have you set it up?


    If you are using L3 DNS discovery, you need to create an "aruba-master" or "aruba-conductor" entry in the DNS - depending on the controller software version. With L3 DHCP Discovery, DHCP server option 43 must be set up.

    You can find details in this Aruba Guide.

    Furthermore, the AP 505 is a unified campus access point. This means that the first time it boots up, it decides whether to become a Campus AP (CAP) or an Instant AP (IAP). If a controller is located, it converts to a campus AP, otherwise it becomes an instant AP. It is possible that your AP has already become an IAP and is not looking for the controller at all. Can you connect to the AP with WEG-GUI? Then you already have an IAP, reset it to factory default as described in this Aruba Guide.

    Once Layer 3 Discovery has been set up, the AP will then find the controller and convert to CAP.



    ------------------------------
    Regards,

    Waldemar
    ACCX # 1377, ACEP, ACX - Network Security
    If you find my answer useful, consider giving kudos and/or mark as solution
    ------------------------------

    Original Message


  • 3.  RE: Normal time for AP505 to connect to Controller

    Posted 29 days ago

    Not a 505, but 515s take at least 15 minutes to get to the controller.

    Even in the same subnet, with controller IPs provided via DHCP option, a new access point takes around 15 minutes to appear in the allowlist. As far as i know, the biggest delay is the unified nature of these APs, since they boot as IAP by default.


    Original Message


  • 4.  RE: Normal time for AP505 to connect to Controller

    Posted 29 days ago
    Oh ok, its a relief because i thought i was doing something wrong. I see a long list of packets where AP is attempting to connect to NTP etc.





    Original Message


  • 5.  RE: Normal time for AP505 to connect to Controller

    Posted 29 days ago

    Whether you are doing something wrong or not depends on whether you have set up Layer 3 Controller Discovery.

    Without L3 discovery, the AP will not find the controller because it is behind a router. The AP converts itself to an IAP and no longer tries to locate the controller.



    ------------------------------
    Regards,

    Waldemar
    ACCX # 1377, ACEP, ACX - Network Security
    If you find my answer useful, consider giving kudos and/or mark as solution
    ------------------------------

    Original Message