07-25-2013 02:55 PM - edited 07-04-2021 12:31 AM
Any and all help is appreciated..
So I am seeing an issue where guest clients on an open L3 passthrough anchored wlan are having to reauth upon every roam. (intractroller) I scoured documentation today and found verbage of several variations of this situation, just not this exactly. I do not have mac filter failure enabled and the below logs are from Prime via the foreign.
2013-Jul-25, 10:16:21 EST | INFO | 172.27.26.9 | Controller association request message received. |
2013-Jul-25, 10:16:21 EST | INFO | 172.27.26.9 | Mobility role update request. from Export Foreign to Local Peer = 172.21.21.8, Old Anchor = 172.21.21.8, New Anchor = 172.27.26.9 |
2013-Jul-25, 10:16:21 EST | INFO | 172.27.26.9 | Received reassociation request from client. |
2013-Jul-25, 10:16:21 EST | INFO | 172.27.26.9 | Client moved to associated state successfully. |
2013-Jul-25, 10:16:21 EST | INFO | 172.27.26.9 | Mobility role update request. from Export Foreign to Export Foreign Peer = 172.21.21.8, Old Anchor = 172.21.21.8, New Anchor = 172.21.21.8 |
2013-Jul-25, 10:16:21 EST | INFO | 172.27.26.9 | Mobility role changed. State Update from Mobility-Incomplete to Mobility-Complete, mobility role=ExpForeign, client state=APF_MS_STATE_ASSOCIATED |
2013-Jul-25, 10:17:24 EST | INFO | 172.27.26.9 | Controller association request message received. |
2013-Jul-25, 10:17:24 EST | INFO | 172.27.26.9 | Mobility role update request. from Export Foreign to Local Peer = 172.21.21.8, Old Anchor = 172.21.21.8, New Anchor = 172.27.26.9 |
2013-Jul-25, 10:17:24 EST | INFO | 172.27.26.9 | Received reassociation request from client. |
2013-Jul-25, 10:17:24 EST | INFO | 172.27.26.9 | Client moved to associated state successfully. |
2013-Jul-25, 10:17:24 EST | INFO | 172.27.26.9 | Mobility role update request. from Export Foreign to Export Foreign Peer = 172.21.21.8, Old Anchor = 172.21.21.8, New Anchor = 172.21.21.8 |
2013-Jul-25, 10:17:24 EST | INFO | 172.27.26.9 | Mobility role changed. State Update from Mobility-Incomplete to Mobility-Complete, mobility role=ExpForeign, client state=APF_MS_STATE_ASSOCIATED |
07-25-2013 03:00 PM
You have multiple anchors?
Sent from Cisco Technical Support iPhone App
07-25-2013 03:03 PM
We did, but currently only anchored off the wlan to one of them. The other anchor that used to also be used is still probably a mobility member from another group in an up/up state, but not referenced here.
07-25-2013 03:04 PM
I see .8 and .9 for the roaming.
Sent from Cisco Technical Support iPhone App
07-25-2013 03:06 PM
The .9 is actually the ip of the foreign that my APs home to, the other anchor is a .10.
07-25-2013 03:09 PM
Post your show WLAN
Sent from Cisco Technical Support iPhone App
07-26-2013 05:24 AM
07-26-2013 07:08 AM
I need to see both controllers... you just have one.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"
07-26-2013 07:13 AM
07-26-2013 06:04 PM
That is fine that your WiSM is running v7.4 and the 4400 is running v7.0.... thats not an issue.
I would change the session timout on the WiSM2 to Infinity and make sure the idle timer on the anchor is set to 14400.
See if that helps.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"
09-04-2014 05:02 PM
Did you solve this issue? I am having a very similar issue.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide