topic Control path to mobility member flaps in Wireless

Control path to mobility member flaps

cisconell — Sun, 04 Jul 2021 04:21:34 GMT

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

Re: test

Scott Fella — Wed, 11 Jan 2012 16:44:36 GMT

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

test

George Stefanick — Wed, 11 Jan 2012 16:46:23 GMT

Here is the link to the matrix. "What Scott said" ...

Re: test

Scott Fella — Wed, 11 Jan 2012 16:46:36 GMT

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

Control path to mobility member flaps

George Stefanick — Wed, 11 Jan 2012 16:55:26 GMT

Gezzz I was shooting blank links again!

Re: Control path to mobility member flaps

Scott Fella — Wed, 11 Jan 2012 16:56:36 GMT

Haha

Thanks,

Scott Fella

Sent from my iPhone

Re: Control path to mobility member flaps

cisconell — Wed, 11 Jan 2012 18:50:10 GMT

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

Re: Control path to mobility member flaps

Scott Fella — Wed, 11 Jan 2012 19:03:07 GMT

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

Control path to mobility member flaps

cisconell — Wed, 11 Jan 2012 19:30:19 GMT

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

Re: Control path to mobility member flaps

Scott Fella — Wed, 11 Jan 2012 19:44:06 GMT

Do you see anything in the logs?

Thanks,

Scott Fella

Sent from my iPhone

Re: Control path to mobility member flaps

Scott Fella — Wed, 11 Jan 2012 19:47:36 GMT

Can you screen shot the mobility group info.

Thanks,

Scott Fella

Sent from my iPhone

Re: Control path to mobility member flaps

weterry — Wed, 11 Jan 2012 22:31:46 GMT

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?

Control path to mobility member flaps

cisconell — Thu, 12 Jan 2012 07:16:56 GMT

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.

Re: Control path to mobility member flaps

Scott Fella — Thu, 12 Jan 2012 12:21:10 GMT

Can you post the members in the mobility group.

Thanks,

Scott Fella

Sent from my iPhone

Control path to mobility member flaps

cisconell — Thu, 12 Jan 2012 12:52:37 GMT

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

Control path to mobility member flaps

Stephen Rodriguez — Thu, 12 Jan 2012 13:02:24 GMT

can you post the show mobility summary and show interface detailed management from the two WLC? Sometimes the mac address you see under the managmeent interface, is not what gets used in the mobility group. Though that should cause the mobility tunnel to not come up.

Also, which way are you allowing the communication in the FW? As Wesley hinted at, there is the possiblity that the keepalive is only allowed to initiate one way. I like to allow this bi-direcitonally, as you can't tell which WLC will initiate the keepalive by default. IIRC the keepalive is initiated by the WLC with the lower mac address and this is per WLC pair.

Steve

Re: Control path to mobility member flaps

Scott Fella — Thu, 12 Jan 2012 13:18:36 GMT

Like Steve mentioned this doesn't help... What I wanted to check is the Mac address on each of the wlc mobility group info.

Thanks,

Scott Fella

Sent from my iPhone

Control path to mobility member flaps

cisconell — Thu, 12 Jan 2012 14:11:06 GMT

Thanks Scott and Stephen Rodriguez

Here is the whole set up

In the current scenario

3 internal controller
WLC1 (5.2)
WLC2 (5.2)
WLC3 (6.0)

1 guest controller (5.2) WLC GUEST

the control path between

WLC 1 and WLC guest - good and stable
WLC 2 and WLC guest - good and stable
WLC 3 and WLC guest - unstable (get stable for about a while , last time it got stable for 3 hrs and when down for 30 minutes and then came up )

Now with reference to Stephen Rodriguez .

The mac to be entered in the mobility group should be off the management ? the one which see in show interface detailed management ?

Now whats the mac I see when give the command show sysinfo ?

For

WLC 1 , WLC 2 , Guest I see the mac shown in sysinfo and show interface detailed management is same and thats what in mobility group .

But here is the catch

For wlc 3

The mac seen in show sysinfo and show interface detailed management is different . the one in mobility group is of management.

But if you say in the mobilty group it should be off management mac

how the links are stable between WLC1 and WLC3 and WLC2 and WLC 3 ? could be that because they are on 5.2 and work with both macs in sys info and mgmt

and does the higher version like 6.0 will work only on the mgmt mac ?

and not sure how come some time it get stable for about 3hrs .

Your thoughts , hope now we are in right direction

Re: Control path to mobility member flaps

Scott Fella — Thu, 12 Jan 2012 14:28:06 GMT

You should use the Mac address off the wlc mobility group list. The top entry is for that wlc and that should be entered on the other WLC's.

Thanks,

Scott Fella

Sent from my iPhone

Control path to mobility member flaps

cisconell — Thu, 12 Jan 2012 14:30:18 GMT

Correction on my last post

For

WLC 1 , WLC 2 , Guest I see the mac shown in sysinfo and show interface detailed management is same and thats what in mobility group .

But here is the catch

For wlc 3

The mac seen in show sysinfo and show interface detailed management is different . the one in mobility group is of

*show sys info*

Checking on Scott last point