01-11-2012 08:40 AM - edited 07-03-2021 09:21 PM
Here is the problem I have 2 controllers as below one with 6.0 version and other with 5.2 version
AIR-WLC4404-100-K9 6.0.202.0
AIR-WLC4402-12-K9 5.2.178.0 GUEST
Control path between controller flaps
All mobility anchors on wlan index 7 are down.
All mobility anchors on wlan index 3 are down.
Control path to mobility member x.x.x.x is down.
No problem observed when i have software 5.2.178.0 on both the controler
Did some one experience this problem , or any thoughts on this please
Solved! Go to Solution.
01-11-2012 11:47 AM
Can you screen shot the mobility group info.
Thanks,
Scott Fella
Sent from my iPhone
01-11-2012 08:44 AM
You should have them on the same code. The 5.x and 6.x are different and I don't think it is in the matrix. I will try to find the matrix and post it.
Thanks,
Scott Fella
Sent from my iPhone
01-11-2012 08:46 AM
Here is the link to the matrix. "What Scott said" ...
01-11-2012 08:46 AM
Well here is the matrix, but you should get of the 5.x code... Worse ever:)
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a00809ba482.shtml#Q-Aug08
Thanks,
Scott Fella
Sent from my iPhone
01-11-2012 08:55 AM
Gezzz I was shooting blank links again!
01-11-2012 08:56 AM
Haha
Thanks,
Scott Fella
Sent from my iPhone
01-11-2012 10:50 AM
Thanks guys for you quick respone
I missed one more point
When I have 2 controller on 5.2.178.0 - No problem
When I have 2 controller on 6.0.202.0 - Control path between controller flaps
When I have 2 Controller one on 5.2.178.0 and other on 6.0.202.0 :- Control path between controller flaps
From the link which Scott Fella gave 5.2 and 6.0 is in Matrix right ? and 6.0 and 6.0 is also in Matirx , So both this combination should not give problem . So does that prove the problem is not with image . its some thing else ?
fyi one controller is working as guest in DMZ
01-11-2012 11:03 AM
Even thought it does show it, really doesn't meant will work:). 5.x is not a good code to be on. I don't know why your mobility would be flapping on the 6.x. Have you tried to delete your wlc in the mobility group and add it back on. Make sure that that the Mac address is correct on the mobility group you have.
Thanks,
Scott Fella
Sent from my iPhone
01-11-2012 11:30 AM
You are right its does not prove the matrix gona work
Have you tried to delete your wlc in the mobility group and add it back on. Make sure that that the Mac address is correct on the mobility group you have--------Above 2 things already tried , no luck
01-11-2012 11:44 AM
Do you see anything in the logs?
Thanks,
Scott Fella
Sent from my iPhone
01-11-2012 11:47 AM
Can you screen shot the mobility group info.
Thanks,
Scott Fella
Sent from my iPhone
01-11-2012 02:31 PM
If this is a true statement: "When I have 2 controller on 6.0.202.0 - Control path between controller flaps" then I would focus on that. No one can say 5.2 is your problem when both WLCs are on 6.0.202.0
As far as proper troubleshooting.... mobility debugs (debug mobility keepalive enable) on both WLC will help characterize who isn't hearing who, which is the primary reason for a mobility flap. Then of course the dreaded packet capture is really how you backup that what the debug is saying is true...
I'm not aware of any mobility issues with 6.0.202.0 to anything else, so it sure seems peculiar that Control Path is down for you.
In reference to Scott wanting a screen shot, can you post the full output of "show mobility summary" from each WLC?
01-11-2012 11:16 PM
Output of show mobility summary
Internal
Symmetric Mobility Tunneling (current) .......... Enabled
Symmetric Mobility Tunneling (after reboot) ..... Enabled
Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... WLC-TEST
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xccb2
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 4
Mobility Control Message DSCP Value.............. 0
Guest
Symmetric Mobility Tunneling (current) .......... Enabled
Symmetric Mobility Tunneling (after reboot) ..... Enabled
Mobility Protocol Port........................... 16666
Mobility Security Mode........................... Disabled
Default Mobility Domain.......................... WLC-TEST
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xccb2
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 4
Mobility Control Message DSCP Value.............. 0
fyi - mping and eping works fine when the control path is up but when down does not.
01-12-2012 04:21 AM
Can you post the members in the mobility group.
Thanks,
Scott Fella
Sent from my iPhone
01-12-2012 04:52 AM
For example I have it in this way
guest
aa:bb:cc:dd:ee:ff 1.1.1.1
gg:hh:ii:jj:kk:ll 2.2.2.2 WLC-TEST
internal
gg:hh:ii:jj:kk:ll 2.2.2.2
aa:bb:cc:dd:ee:ff 1.1.1.1 WLC-TEST
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