Wireless Access

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

Ipad Wifi, Sleep and max stations

This thread has been viewed 1 times

  • 1.  Ipad Wifi, Sleep and max stations

    Posted Feb 21, 2012 12:08 AM

    hello all, wanted to ping (no pun intended) the community

     

    I have two sites with a200 controllers running the latest 5.0.4.4 code. after much troubleshooting we realized that after a few days we were hitting the max 128 users on the controllers even when show user was at most 70 or 80.

     

    well turns out if you do show station you see plenty more devices, turns out each and every one was an ipad that was sleeping. according to the log all of these ipads send a ping a command every so often that gets them added back to the station list and driving up my max counts.

     

    a reload of the controller clears these devices out, I will also be testing restricting wireless at say 2-2:05 am, as these ipads that sleep don't appear to reconnect to wifi they have lost.

     

    any thoughts on alternatives would be greatly appreciated.



  • 2.  RE: Ipad Wifi, Sleep and max stations

    EMPLOYEE
    Posted Feb 21, 2012 01:49 AM
    Are the iPads running iOS 5.0.1?


  • 3.  RE: Ipad Wifi, Sleep and max stations

    Posted Feb 21, 2012 08:48 PM

    some are, probably not all. digging into it further it's possible other devices are covered in this as well.

     

    for instance on one of my controllers right now (after hours) I have 13 users, the station list shows 24, most aged 6+ hours, some from around the time about 12 hours I ago I did the last reload of this controller.

     

    all of the ipads on the list (about 9) show up in the the logs as so, many of the others don't show at all even with debug enabled.

     

    Feb 21 20:38:43  authmgr[583]: <522006> <INFO> |authmgr|  MAC=d8:a2:5e:67:ac:91 IP=192.168.4.134 User entry added: reason=Sibtye
    Feb 21 20:38:43  authmgr[583]: <522026> <INFO> |authmgr|  MAC=d8:a2:5e:67:ac:91 IP=192.168.4.134 User miss: ingress=0x1046, VLAN=1
    Feb 21 20:43:15  authmgr[583]: <522004> <DBUG> |authmgr|  MAC=d8:a2:5e:67:ac:91 IP=192.168.4.134 Sending ping 1 of 3 (id=8214, seq=4149)
    Feb 21 20:43:20  authmgr[583]: <522004> <DBUG> |authmgr|  MAC=d8:a2:5e:67:ac:91 IP=192.168.4.134 Sending ping 2 of 3 (id=8214, seq=4150)
    Feb 21 20:43:25  authmgr[583]: <522004> <DBUG> |authmgr|  MAC=d8:a2:5e:67:ac:91 IP=192.168.4.134 Sending ping 3 of 3 (id=8214, seq=4151)
    Feb 21 20:43:30  authmgr[583]: <522004> <DBUG> |authmgr|  MAC=d8:a2:5e:67:ac:91 IP=192.168.4.134 Send mobility delete message, flags=0x0
    Feb 21 20:43:30  authmgr[583]: <522004> <DBUG> |authmgr|  MAC=d8:a2:5e:67:ac:91 Reset station role to authenticated (59) (ingress=4166)
    Feb 21 20:43:30  authmgr[583]: <522005> <INFO> |authmgr|  MAC=d8:a2:5e:67:ac:91 IP=192.168.4.134 User entry deleted: reason=idle timeout
    Feb 21 21:08:28  authmgr[583]: <522006> <INFO> |authmgr|  MAC=d8:a2:5e:67:ac:91 IP=192.168.4.134 User entry added: reason=Sibtye
    Feb 21 21:08:28  authmgr[583]: <522026> <INFO> |authmgr|  MAC=d8:a2:5e:67:ac:91 IP=192.168.4.134 User miss: ingress=0x1046, VLAN=1