Hi everyone!
I could use a bit of help here ...
Our users have been reporting frequent disconnections, which seem random, for a long time now. Unfortunately we have never been able to get a reliable reproduce scenario.
Today, amazingly, I found one and can reproduce their exact issue on demand every time. I've tracked it down to a failure to roam and it looks like the failure may be coming from the Aruba side. I've taken the two involved access points out of service and set them up to lab this scenario. Unfortunately this creates a minor outage but thankfully the users are tolerating it in hopes of finally fixing this issue.
Our controller is an Aruba7030 running 8.3.0.0. All access points through the entire enterprise, including the two affected units, are 205's.
The client test devices are an iPad and an iPhone (Others client devices may be affected as well - we just don't know - these were chosen as they represent our user base and are also the most modern available from this major vendor - Apple.. so they simply must be made to work). The iPad is an iPad Pro and the iPhone is an iPhone X. Both run the latest iOS version.
Our controller is an Aruba7030 running 8.3.0.0. All access points through the entire enterprise, including the two affected units, are 205's.
To reproduce the failure, all I need to do is walk from one office to the adjacent office. The offices are separated by a type of wall which the RF does not penetrate (I dont know why) and so each area has its own AP. This was determined during the initial install by the RF site survey.
When walking from one office to the other I will see the wifi signal indicator on the iPad (iPhone) drop markedly and any network activity that may have been going on usually slows or stops. Next I see the wifi indicator jump up to full strength (presumably indicating that the better AP has been seen and it has, or is, doing a roam). After a few moments the wifi indicator will disappear and the device will raise a popup informing me that my cellular data is turned off and I should go into settings to enable it. (.. it is turned off specifically for this test).
After this event, returning to my console to view syslog data output resulting from a "logging level debugging user-debug <client-mac>" setting I find the following (below). Notably I see what appears to be my client attempting to associate with the better (the "roam to") AP, herein called "TestAP2" and then seemingly being rejected by an "deauth_reason 30" from the Aruba system. Seemingly the client device accepts this and makes no more attempts.
Looking up deauth code 30 I see that it has something to do with the client not being permitted, or permitted to use some service. This is all a bit nebulous.
On separate tests, I can associate initially to this TestAP2 just fine, and then walk to the first office ("TestAP1") and the same pattern happens.. just in reverse.
After spending several hours on this today I have made zero progress other than to isolate this item. Could this be a bug?
Can anyone suggest anything I can try?
Thanks!
-J
-- log excerpt --
Sep 12 17:41:43 2018 Aruba7030 authmgr[4509]: <522260> <5390> <DBUG> <Aruba7030 192.168.0.6> "VDR - Cur VLAN updated 78:7b:8a:a4:a7:ac mob 0 inform 1 remote 1 wired 0 defvlan 1 exportedvlan 0 curvlan 1.
Sep 12 17:41:43 2018 Aruba7030 authmgr[4509]: <522301> <5390> <DBUG> <Aruba7030 192.168.0.6> Auth GSM : USER publish for uuid 000b86b4e4e70000000e0109 mac 78:7b:8a:a4:a7:ac name role authenticated devtype wired 0 authtype 0 subtype 0 encrypt-type 9 conn-port 0 fwd-mode 1 roam 0 repkey -1
Sep 12 17:41:43 2018 Aruba7030 authmgr[4509]: <522287> <5390> <DBUG> <Aruba7030 192.168.0.6> Auth GSM : MAC_USER publish for mac 78:7b:8a:a4:a7:ac bssid ac:a3:1e:a5:3e:11 vlan 1 type 1 data-ready 0 HA-IP n.a
Sep 12 17:41:43 2018 Aruba7030 authmgr[4509]: <522096> <5390> <DBUG> <Aruba7030 192.168.0.6> 78:7b:8a:a4:a7:ac: Sending STM new Role ACL : 79, and Vlan info: 1, action : 10, AP IP: 192.168.0.136, flags : 0 idle-timeout: 300
Sep 12 17:41:43 2018 Aruba7030 authmgr[4509]: <522308> <5390> <DBUG> <Aruba7030 192.168.0.6> Device Type index derivation for 78:7b:8a:a4:a7:ac : dhcp (0,0,0) oui (0,0) ua (21,5,35) derived iPad(5):iOS
Sep 12 17:41:43 2018 Aruba7030 authmgr[4509]: <522242> <5390> <DBUG> <Aruba7030 192.168.0.6> MAC=78:7b:8a:a4:a7:ac Station Created Update MMS: BSSID=ac:a3:1e:a5:3e:11 ESSID=TestESSID VLAN=1 AP-name=TestAP2
Sep 12 17:41:43 2018 192.168.0.134 stm[1257]: <501000> <DBUG> |TestAP2@192.168.0.134 stm| Station 78:7b:8a:a4:a7:ac: Clearing state
Sep 12 17:41:52 2018 Aruba7030 authmgr[4509]: <522296> <5390> <DBUG> <Aruba7030 192.168.0.6> Auth GSM : USER_STA delete event for user 78:7b:8a:a4:a7:ac age 0 deauth_reason 30
Sep 12 17:41:52 2018 Aruba7030 stm[4526]: <501000> <4526> <DBUG> <Aruba7030 192.168.0.6> Station 78:7b:8a:a4:a7:ac: Clearing state
Sep 12 17:41:52 2018 Aruba7030 authmgr[4509]: <522152> <5390> <DBUG> <Aruba7030 192.168.0.6> station free: bssid=ac:a3:1e:a5:3e:11, mac=78:7b:8a:a4:a7:ac.