Wireless Access

 View Only
last person joined: 13 hours ago 

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

New Aruba AP-325 generating dirty flag immediately after connecting to controller.

This thread has been viewed 10 times

  • 1.  New Aruba AP-325 generating dirty flag immediately after connecting to controller.

    Posted Apr 22, 2020 10:59 AM

    We recently replaced a MD controller and this is the first time we are attempting to provision a new AP.  The existing APs connected to the controller are working as expected, however when we attempt to provision a new AP it immediately generates a D flag while it's still in the default AP-Group.  We can ping it and see it online in the controller database, but are unable to provision it or even send a boot command to it. It basically ignores any command we send it.  Any ideas as to what could be causing this?  

     

    As info, we use DHCP options to point this AP to the correct controller.



  • 2.  RE: New Aruba AP-325 generating dirty flag immediately after connecting to controller.

    EMPLOYEE
    Posted Apr 22, 2020 11:03 AM

    #1  Check to make sure the default ap-group does not have an AP system profile that has an LMS-IP pointing to another controller

    #2 Check to make sure there is not a firewall between the access point and the MD blocking AP to MD traffic

    #3  If this is a remote site, you might have an MTU issue.

     

    Those are my 3 guesses.



  • 3.  RE: New Aruba AP-325 generating dirty flag immediately after connecting to controller.

    Posted Apr 22, 2020 11:55 AM
      |   view attached

    Hi Colin, thanks for the reply.  I was looking at the AP tech-support output and noticed as lot of Dirty messages in the Group List.. for example see attached screen shot.

     

     

    Attachment(s)

    pdf
    ap-tech.pdf   58 KB 1 version


  • 4.  RE: New Aruba AP-325 generating dirty flag immediately after connecting to controller.

    Posted Apr 22, 2020 11:58 AM
      |   view attached

    I checked and made sure there wasn't a LMS IP in the LMS field of the ap system profile and there aren't any firewalls in between the controller and AP.  I do see a bunch of Dirty messages in the ap-tech-support output (see attached).

    Attachment(s)

    pdf
    ap-tech.pdf   58 KB 1 version


  • 5.  RE: New Aruba AP-325 generating dirty flag immediately after connecting to controller.

    EMPLOYEE
    Posted Apr 22, 2020 12:11 PM

    "dirty" typically means that some ports between the AP and the controller are blocked, whether it be GRE or papi (udp 8211).  When you type "show ap database" on the MD are there any other flags on that AP?  When was the last time you brought up a new AP?



  • 6.  RE: New Aruba AP-325 generating dirty flag immediately after connecting to controller.

    EMPLOYEE
    Posted Apr 22, 2020 11:16 AM

    Hi Eric,

     

    Is the new AP deployed in a different subnet than the other APs? Is there any firewall blocking traffic between AP and controller? Is the MTU different on this path?

     

    Make sure all these ports are allowed between AP and controller

    https://www.arubanetworks.com/techdocs/ArubaOS_64x_WebHelp/Content/ArubaFrameStyles/Firewall_Port_Info/Communication_Between__D.htm