C9800 Wireless Issue

[duggu19]

I have a pair of C9800's in HA running my entire wireless infrastructure on our campus. In one of our lab buildings I am seeing may clients sitting in a IP Learn state trying to attach to one particular SSID. I've tested with a Macbook, my Dell and my NetScout, and grabbed radioactive trace logs. If I take my devices back across the road to the building I sit in and join the same SSID there, there are no issues at all. It seems to be geographical based but I can't think of what would be causing clients to sit in a IPLearn state in one building and not another.

I know it's not a signal issue, and I don't believe some of the dirty 2.4 Ghz interference is the source. I'm opening a TAC case but thought I'd post here to see if anyone has suggestions.

[Mark Elsen]

-Note that you can have radioactive trace logs analyzed with : https://cway.cisco.com/wireless-debug-analyzer/  , also start with a checkup of the C9800 (HA) configuration , use these commands  (CLI ) on the current active controller  : show  tech   wireless , have the output analyzed by  https://cway.cisco.com/tools/WirelessAnalyzer/  , please note do not use classical show tech-support (short version) , use the command denoted in green for Wireless Analyzer.               Checkout all advisories!

 M.

[eglinsky2012]

Assuming local mode and not FlexConnect, different policy tag on the APs in the other building putting those clients in the wrong VLAN?

[jagan.chowdam]

It doesn't sound like RF issue. More like Config issue.

I would check AP Tags to make sure they are getting correct VLAN assigned via policy TAG (Policy Profile). 

Also, Check the connectivity between the lab building to DHCP server to eliminate any L2/L3 issues.

CJ

/*Please rate all useful responses*/

[Leo Laohoo]

Do both building share the same tags?

[Scott Fella]

What you should try is connect your laptop or nets out to a wired port on the same switch as the AP’s for the same vlan users are supposed to get and see if the device gets the correct ip. At least eliminate any dhcp issues then look at your policies and tags.