Wireless Access

last person joined: 3 days ago 

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

AP103H on a go slow

This thread has been viewed 0 times
  • 1.  AP103H on a go slow

    Posted Jun 15, 2016 05:41 AM

    Wondering if anyone else has seen this problem... We have a number of AP103H units and sometimes, usually following a user complaint, we'll find one is behaving strangely. It's up and serving clients, nothing looks amiss that I can see. When pinging the AP the response time will alternate between <1ms and over 100ms, sometimes up to over 500ms. Clearly not right. Rebooting the AP will bring it back to normal service, but we've seen this happen a few times randomly across different buildings.



  • 2.  RE: AP103H on a go slow

    Posted Jun 15, 2016 09:13 AM

    Hi!

     

    What Aruba OS version are you running? How´s the AP configured CAP or RAP? Is control plane security enabled? What network devices are deployed in the path between the AP and controller?

     

    Cheers,



  • 3.  RE: AP103H on a go slow

    Posted Jun 15, 2016 09:36 AM

    Hi Christoffer

     

    Our controllers are running 6.4.3.6. The affected APs are running in CAP mode. Control place security is not enabled. Twixt APs and controllers there's a variety of models of Procurve switches, with 5400 used as routers and an ospf routed network.

     

    We have no indication there's a network problem that could be responsible. We have over 2000APs and only the AP103H has demonstrated this problem. When it occurs we'll see maybe only one AP with the issue, out of about 40 on the same switch and many more on the same subnet.



  • 4.  RE: AP103H on a go slow

    Posted Jun 15, 2016 09:42 AM

    Ok, that does sound like a model/firmware related issue. I´d open up a TAC case so they can take a look at it.

     

    Cheers,



  • 5.  RE: AP103H on a go slow

    Posted Jun 15, 2016 09:53 AM

    Yeah, done that. Thought it would be interesting to know if it's something anyone else has seen. Feels like a driver issue, perhaps.