We recently opened a new office area, with an Aruba solution.
A couple clients told me they get a brief interruption of their wireless connection sometimes, randomly.
I used one client as test subject, and setup a debug on her MAC address. I have now figured out that Client Match is causing her to connect to another access point.
Imagine the office to be a rectangle shaped open office. We have two AP's, one on each "short" side of the rectangle. The test user always sits on here steady place, and never moved her laptop, but still I'm seeing her disconnect and connect to the other AP.
I noticed this message in the debug log:
## deauth from AP 261 (left side office)##
Jul 18 07:46:52 :501080: <NOTI> |AP NDHAM01AP261@10.25.34.31 stm| Deauth to sta: 34:02:86:a6:bb:3e: Ageout AP 10.25.34.31-94:b4:0f:94:c2:01-NDHAM01AP261 Client Match
Jul 18 07:46:52 :501000: <DBUG> |AP NDHAM01AP261@10.25.34.31 stm| Station 34:02:86:a6:bb:3e: Clearing state
Jul 18 07:46:52 :522296: <DBUG> |authmgr| Auth GSM : USER_STA delete event for user 34:02:86:a6:bb:3e age 0 deauth_reason 22
Jul 18 07:46:52 :522036: <INFO> |authmgr| MAC=34:02:86:a6:bb:3e Station DN: BSSID=94:b4:0f:94:c2:01 ESSID=AirFlight VLAN=3000 AP-name=NDHAM01AP261
Jul 18 07:46:52 :522234: <DBUG> |authmgr| Setting idle timer for user 34:02:86:a6:bb:3e to 300 seconds (idle timeout: 300 ageout: 0).
Jul 18 07:46:52 :522152: <DBUG> |authmgr| station free: bssid=94:b4:0f:94:c2:01, @=0x0x16ca0f4.
Jul 18 07:46:52 :501000: <DBUG> |stm| Station 34:02:86:a6:bb:3e: Clearing state
## auth to AP 262 (right side office)##
Jul 18 07:46:57 :501093: <NOTI> |AP NDHAM01AP262@10.25.34.30 stm| Auth success: 34:02:86:a6:bb:3e: AP 10.25.34.30-94:b4:0f:94:38:b1-NDHAM01AP262
Jul 18 07:46:57 :501095: <NOTI> |AP NDHAM01AP262@10.25.34.30 stm| Assoc request @ 07:46:57.254841: 34:02:86:a6:bb:3e (SN 309): AP 10.25.34.30-94:b4:0f:94:38:b1-NDHAM01AP262
Jul 18 07:46:57 :501100: <NOTI> |AP NDHAM01AP262@10.25.34.30 stm| Assoc success @ 07:46:57.256046: 34:02:86:a6:bb:3e: AP 10.25.34.30-94:b4:0f:94:38:b1-NDHAM01AP262
Jul 18 07:46:57 :501100: <NOTI> |stm| Assoc success @ 07:46:57.271437: 34:02:86:a6:bb:3e: AP 10.25.34.30-94:b4:0f:94:38:b1-NDHAM01AP262
Can we overcome this from happening? I don't want to disable Client Match, since it's a good feature for roaming in other parts of the building.