We have a couple of CAPWAP 1140 aps in a remote office with HREAP enabled. 802.1X+CCKM is used for the SSID.
Everything seems to work normally (local switching, RADIUS authentication, etc.), however, client roaming seems to be an issue. Clients who are very close to an AP are being connected to a remote AP, regardless of the much stronger signal strength. Additionally, it seems that regardless of where they roam in the building, it never switches them to the other access point.
my config is such that there is an AP group with both APs and appropriate WLANs, an HREAP group that contains the APs, each AP has the HREAP configuration set up appropriately (VLAN mappings, etc.). The "Client Roaming" section is set to default for both a/n and b/g/n. Clients connect typically with a/g.
can someone point me in the right direction in troubleshooting why clients don't seem to be roaming correctly?
There are alot of different ways to approach this, and TAC may very well be the best way to get a structured troubleshooting plan.
Perhaps you could clarify a few things.
1) Does anything ever connect successfully to the AP that clients don't roam to?
2) Is it possible that clients are attempting to roam but failing?
3) Do you have multiple types of clients with this behavior? Multiple WLANs?
I suppose my suggestion would be to get a client debug on the WLC with : debug client
I would then test by having the client stay within specific APs that you expect them to roam between and periodically collect "show client detail " from the WLC while you have the client moving.
Generally speaking, roaming is a decision of the client so you need to make sure that your roam test covers whatever the trigger is for roaming of that particular client.
Learn, share, save
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
