Wireless Access

last person joined: 19 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

ap can't connect

This thread has been viewed 2 times
  • 1.  ap can't connect

    Posted Mar 26, 2015 10:45 AM

    I've got a new controller and AP that i'm trying to get working for a customer install. 

     

    There is no firewall on the network. The AP is plugged into the same default switch that the controllers are. 

    The AP has a static address and can ping both the controllers (master and local). Serverip is also set.

    The Controller addresses are in Vlan 29. 

    Vlan 1 has no address on the controller. 

     

    Show datapath session shows the ap connecting but it has a Y flag indicating "no syn".

     

    Where can I go next in troubleshooting?  CPE is off (and was disabled by default) I enabled and disable again and added the AP to the whitelist just in case.



  • 2.  RE: ap can't connect

    Posted Mar 26, 2015 11:03 AM

    from ap rebooting:

     

    AP rebooted Wed Dec 31 16:04:35 PST 1969; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1040 dest=172.29.30.5 tries=10 seq=0
     

     


  • 3.  RE: ap can't connect

    Posted Mar 26, 2015 11:29 AM

    Hi,

     

    What is the flag of this AP in "show ap database" ? and also the status ?

    BTW, you mentioned that configured static IP, only IP also master IP ? or you are using ADP for master discovery ?

     

    In "show datapsth session" are you able to see PAPI (UDP 8211) traffic ?

     

    Please clarify all above, we can fix the issue .



  • 4.  RE: ap can't connect

    Posted Mar 26, 2015 12:33 PM

    The AP never shows up in the controller. I do not see PAPI traffic but I dont know what would be blocking it. I do see PAPI traffic in between the 2 controllers.

     

    I have a static master defined as well but the AP uses ADP and finds the master too.

     

    (MDF-A7210-A) #show datapath session table | include 172.20.30.20
    172.20.30.20 172.29.30.5 17 51013 514 0/0 0 0 0 0/0/0 a 1 266 FC
    172.20.30.5 172.29.30.20 17 514 51013 0/0 0 0 1 0/0/0 a 0 0 FY



  • 5.  RE: ap can't connect

    Posted Mar 26, 2015 12:35 PM

    here is some more as well....

     

    (MDF-A7210-A) #show datapath session table | include 172.29.30.20
    172.29.30.5 172.29.30.20 17 8222 8211 0/0 0 0 1 0/0/0 e 0 0 FYI
    172.29.30.5 172.29.30.20 17 8211 8211 0/0 0 0 1 0/0/0 e 0 0 FYI
    172.29.30.20 172.29.30.5 17 8211 8211 0/0 0 0 1 0/0/0 e 3 3400 FCI
    172.29.30.20 172.29.30.5 17 8211 8222 0/0 0 0 0 0/0/0 e 0 0 FYCI



  • 6.  RE: ap can't connect

    Posted Mar 26, 2015 12:53 PM

    Hi,

     

    All the provided outputs are saying that, there is no PAPI traffic between Controller and AP.

     

    Is it test env or in production ?

     

    If it is a test setup,

    1. Reset the AP ( apboot> purge, save, set ipaddr x.x.x.x, set netmask x.x.x.x, save, boot)

    2. Connect the AP directly to the controller.

    3. observe the traffic between AP and Controller (show datapath session | include <AP IP>)

     

    Let me know if it is in the production, let us do some logging level debugging.

     



  • 7.  RE: ap can't connect

    Posted Mar 30, 2015 02:43 PM

    we wiped the configuration and using Vlan 1 with a DHCP server were able to get the AP to come up. Now that we'lvee switched over to VLAN 29, the AP will no longer come up. What settings do I need to change to get this working?

     

    We've enabled gig-0/0/1-1 on vlan 29. Changed the controller IP to vlan 29. 

     

    We've also changed the adp igmp-broadcast to vlan 29.

     

    The AP gets an address from the controller, finds the master, and then it wont come up.