Controller Based WLANs

1. We see a lot of disconnects for a client.

2. We see that a static client may roam between the APs.

3. Debugging for the client shows return errors like "Deauth to sta: 58:7f:57:f2:26:c5: Ageout AP 192.168.1.16-d8:c7:c8:49:d7:02-Aruba-AP Tx fail reached maximum"

1. We need to enable user debug for the client:

# config t
# logging level debugging user-debug 58:7f:57:f2:26:c5

2. We can see that the user debug return the following error messages:

Dec 23 18:03:42 :501080:  <NOTI> |AP Aruba-AP@192.168.157.16 stm|  Deauth to sta: 58:7f:57:f2:26:c5: Ageout AP 192.168.1.16-d8:c7:c8:49:d7:02-Aruba-AP Tx fail reached maximum
Dec 23 18:05:08 :501080:  <NOTI> |AP Aruba-AP@192.168.157.16 stm|  Deauth to sta: 58:7f:57:f2:26:c5: Ageout AP 192.168.1.16-d8:c7:c8:49:d7:02-Aruba-AP Tx fail reached maximum
Dec 23 18:05:59 :501080:  <NOTI> |AP Aruba-AP@192.168.157.16 stm|  Deauth to sta: 58:7f:57:f2:26:c5: Ageout AP 192.168.1.16-d8:c7:c8:49:d7:02-Aruba-AP Tx fail reached maximum

3. We can verify the same in AP debug logs:

#show ap debug log  ap-name "Aruba-AP"

    Dec 23 17:12:28 stm[1141]: <501080> <NOTI> |AP Aruba-AP@192.168.157.16 stm|  ^[mac 58:7f:57:f2:26:c5] [ip 192.168.157.16] [bssid d8:c7:c8:49:d7:02] [name Aruba-AP] [reason Tx fail reached maximum ]
    Dec 23 17:12:28 stm[1141]: <501000> <DBUG> |AP Aruba-AP@192.168.157.16 stm|  ^[mac 58:7f:57:f2:26:c5]
    Dec 23 17:14:25 stm[1141]: <501109> <NOTI> |AP Aruba-AP@192.168.157.16 stm|  ^[mac 58:7f:57:f2:26:c5] [ip 192.168.157.16] [bssid d8:c7:c8:49:d7:02] [name Aruba-AP] [auth_alg 0]
    Dec 23 17:14:25 stm[1141]: <501093> <NOTI> |AP Aruba-AP@192.168.157.16 stm|  ^[mac 58:7f:57:f2:26:c5] [ip 192.168.157.16] [bssid d8:c7:c8:49:d7:02] [name Aruba-AP]
    Dec 23 17:14:25 stm[1141]: <501095> <NOTI> |AP Aruba-AP@192.168.157.16 stm|  ^[tstr 17:14:25.501326] [mac 58:7f:57:f2:26:c5] [sn 3112] [ip 192.168.157.16] [bssid d8:c7:c8:49:d7:02] [name Aruba-AP]
    Dec 23 17:14:25 stm[1141]: <501100> <NOTI> |AP Aruba-AP@192.168.157.16 stm|  ^[tstr 17:14:25.503184] [mac 58:7f:57:f2:26:c5] [ip 192.168.157.16] [bssid d8:c7:c8:49:d7:02] [name Aruba-AP]
    Dec 23 17:14:40 stm[1141]: <501106> <NOTI> |AP Aruba-AP@192.168.157.16 stm|  ^[mac 58:7f:57:f2:26:c5] [ip 192.168.157.16] [bssid d8:c7:c8:49:d7:02] [name Aruba-AP] [func handle_sapcp]
    Dec 23 17:14:40 stm[1141]: <501080> <NOTI> |AP Aruba-AP@192.168.157.16 stm|  ^[mac 58:7f:57:f2:26:c5] [ip 192.168.157.16] [bssid d8:c7:c8:49:d7:02] [name Aruba-AP] [reason Tx fail reached maximum ]

4. We need to verify the SSID profile configuration:

wlan ssid-profile "Aruba-AP-SSID-Profile"
essid "Aruba-AP"
max-retries 24
max-clients 100
wmm-vo-dscp "56"
wmm-vi-dscp "40"
wmm-be-dscp "24"
wmm-bk-dscp "8"
max-tx-fail 28

max-retries          : AP will try to send a frame n number of times before it gets confirmation from a client that it has received it.

max-tx-fail            : AP will de-authorize a client if it detects n consecutive frames were not delivered as the max-retries threshold was exceeded. Default value is disabled (0).

If the max-tx-fail is set to a non 0 value, we may see the error "Tx fail reached maximum"

We need to reset max-tx-fail:

wlan ssid-profile "Aruba-AP-SSID-Profile"

no max-tx-fail

If the issue persists, contact Aruba support to open a case and provide the following:

1. User debug output.

2. AP tech support.

3. Controller logs.