Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Roaming causing ReauthC on anchored controller

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

10 REPLIES
Hall of Fame Super Silver

Re: Roaming causing ReauthC on anchored controller

You have multiple anchors?

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
New Member

Roaming causing ReauthC on anchored controller

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.

Hall of Fame Super Silver

Re: Roaming causing ReauthC on anchored controller

I see .8 and .9 for the roaming.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
New Member

Roaming causing ReauthC on anchored controller

The .9 is actually the ip of the foreign that my APs home to, the other anchor is a .10.

Hall of Fame Super Silver

Re: Roaming causing ReauthC on anchored controller

Post your show WLAN on both WLC's.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
New Member

Re: Roaming causing ReauthC on anchored controller

Attached...

Show Wlan    

Hall of Fame Super Silver

Roaming causing ReauthC on anchored controller

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"

-Scott
*** Please rate helpful posts ***
New Member

Re: Roaming causing ReauthC on anchored controller

Attached is the anchor show wlan < >

I will also mention that the foreign is a WiSM2 running 7.4.100.0

and the anchor is a 4400 running 7.0.240.0

Hall of Fame Super Silver

Roaming causing ReauthC on anchored controller

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"

-Scott
*** Please rate helpful posts ***
New Member

Did you solve this issue? I

Did you solve this issue? I am having a very similar issue.

312
Views
0
Helpful
10
Replies
CreatePlease login to create content