Problem:If we are troubleshooting client connectivity issues and we happen to notice association rejection from the ap, we can get to know the reason for the failure using this command.
Diagnostics:If we are troubleshooting client connectivity issue and we are seeing association rejection from the ap we can get to know the reason from this command.
show ap debug sta-msg-stats
STA Up/Down Message Counters
----------------------------
Num Messages Received 3872636
--------------------- -------
Messages Received per slot 1293885 1289678 1289073
STA Messages: Up Down Total 2037045 1842365 3872636
Success: Assoc Re-Assoc AcksSent 514146 219601 3872636
Unpack Errors 0
Not found Errors: sta sap; sta_alloc UP: 0 0 DN: 1355170 0; alloc_err=0
Duplicate Sequence Num, Auth Busy Drops 1944, 0
Assoc Rejections: Total BLIST CAC VLAN AID ALLOC FT TIME CTRMSR SCTRMSR 1301354 3280 0 1298074 0 0 0 0 0 0
In the above example we have found the "Assoc Rejections:Total and vlan" counts were increasing.
We can also execute the same command for an ap where we see the issue and we can look into the same count on bssid basis.
show ap debug sta-msg-stats ap-name "Aruba_test1"
STA Up/Down Message Counters for BSSID d8:c7:c8:19:87:2d (essid: Employee_test)
--------------------------------------------------------
Name Value
---- -----
STA Messages: Up Down 750 753
Dup Seqnum 0
Success: Assoc Re-Assoc 0 0
STA Not found Errors UP: 0 DN 617
Assoc Rejections: Total BLIST CAC VLAN AID ALLOC FT 750 0 0 750 0 0 0
STA Up/Down Message Counters for BSSID d8:c7:c8:19:87:25 (essid: Employee_test)
--------------------------------------------------------
Name Value
---- -----
STA Messages: Up Down 218 218
Dup Seqnum 0
Success: Assoc Re-Assoc 0 0
STA Not found Errors UP: 0 DN 176
Assoc Rejections: Total BLIST CAC VLAN AID ALLOC FT 218 0 0 218 0 0 0
SolutionIn this scenario we had connectivity issue on the "Employee_test" ssid and this count was increasing on that particular bssid alone.
"Assoc Rejections:vlan" value was increasing since we didn't have a vlan assigned on the virtual-ap and that was causing the connectivity issue.
!
wlan virtual-ap "Employee_test"
aaa-profile "Employee_test"
ssid-profile "Employee_test"
broadcast-filter all
!
Once we assigned the vlan on the virtual-ap we did not experience the connectivity issue and this corresponding numbers stopped increasing.