WiSM - Mobility Group - Control Path Down

I have 2 WiSMs with 4 WLCs. Each WLC is in the same subnet. I have set up the mobility group using the virtual interface MAC address. I get a Control Path Down message for any WLC on another WiSM e.g
From controller 10.x.x.1 on WiSM 1, 10.x.x.1 and 10.x.x.2 (on WiSM 1) show as UP in mobility groups, but 10.x.x.3 and 10.x.x.4 (on WiSM 2) show Control Path Down.
I have tried setting them up using the management interface MAC address but when I click apply it says there is a problem creating the member with MAC (MAC address of the controller I am on).
Any suggestions?

It SHOULD BE MANAGEMENT INT MAC WHICH ENDS WITH ZERO..
Either
WLC >> Controller >> Interfaces >> Managemet >> MAC address
OR
WLC >> Controller >> Interfaces >> Managemet >>Inventory >> MAC Address..
Regards
Surendra

Similar Messages

WLC 7.4.100.0 Mobility group control and data path down

Hi All,
Today i am facing issue with mobility group. i checked and found control and data path is down on foreign controller.I am able to ping anchor controller. Required ports are open on firewall but mping and eping fails. Any idea whats wrong. On Anchor controller, i have 7 foreign controller configured and among these 3 are working fine. Having problem with 4 foreign controller. Previously all are working fine and there is no changes made on network or firewall.

Post output of "show mobility summary" of your Anchor WLC & a non-working WLC. Also "show sysinfo" of those two controllers.
Regards
Rasika

Problem configuring mobility group

Hi, I'm trying to configure a mobility group between 4 WLC's. 2 of 4 form a group and those two are the two on the same cards.
The two cards are on separate subnets and each have are connected to a FW. I've opened up for UDP12222-12223 UDP16666-16667 protocol 50 and protocol 97
any other ideas?

Yes these are WiSM blades!
##from .15## Controllers configured in the Mobility Group
MAC Address IP Address Group Name Status
00:1e:4a:fa:68:c0 x.x.x.10 brf Control and Data Path Down
00:1e:4a:fa:68:e0 x.x.x.42 brf Control Path Down
00:1e:4a:fa:99:60 x.x.x.15 brf Up
00:1e:4a:fa:99:80 x.x.x.47 brf Control Path Down
##from .10## Controllers configured in the Mobility Group
MAC Address IP Address Group Name Status
00:1e:4a:fa:68:c0 x.x.x.10 brf Up
00:1e:4a:fa:68:e0 x.x.x.42 brf Control and Data Path Down
00:1e:4a:fa:99:60 x.x.x.15 brf Control and Data Path Down
00:1e:4a:fa:99:80 x.x.x.47 brf Control and Data Path Down
10 and 15 are on the same subnet and the same wism
42 and 47 are on the same subnet and the same wism

WLC mobility group between 4404 and 5508 controllers

Mobility 'Control and Data Path Down' between 4404 and 5508 WLC's.
Hello, we have 5 x 4404 WLC's running 7.0.240.0 with mobility configured fine between them.
We have installed a 5508 with HA running 7.4.110.0, and have tried to add it to the mobility group, however we see 'Control and Data Path Down' between the new 5508 and all the 4404 controllers.
All controllers have:
The same virtual address
Management interfaces are in the same VLAN, and indeed all the controllers connect via the same pair of 3750X stacked switches.
The default mobility domain name is the same
4404 output when issung the command 'show mobility summary'
Symmetric Mobility Tunneling (current) .......... Enabled
Symmetric Mobility Tunneling (after reboot) ..... Enabled
Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... SGH-Mobility
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xe209
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 6
Mobility Control Message DSCP Value.............. 0
5508 ouput when issueing the command 'show mobility summary'
Mobility Architecture ........................... Flat
Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... SGH-Mobility
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xe209
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 6
Mobility Control Message DSCP Value.............. 0
I've spent quite some time double checking all the configurations to no avail.
Has anybody seen this problem before?
Kind regards
Dave Bell

Thanks Sandeep.
I am well versed with WLC's and mobility, however trying to add a 5508 to a mobility group with 4404's has come up with a bit of a curve ball.
All the 4404 controllers all joined the mobility group fine, no problems at all - its only the 5508 I am struggling with.
In theory its simple, populate the IP address, and MAC addres of the management interface of the remote WLC, as long as the management interfaces are in the same VLAN, and the Default Mobility Domain Name are the same it should come up.
Interestingly I have found the 5508 reports its own management interface MAC address incorrectly when viewing the Mobility Groups:
For example:
{Screen shot WLC1.jpg}
5508 management address is 10.95.x.x and when viewing the Mobility Management screen it shows its own MAC address as bc:16:65:f9:37:60.
however!
From our router is I do an sh arp | i 10.95.x.x (controller management address), I see:f872.eaee.becf.
{Screen shot wlc2.jpg}
Hence the WLC reports as: bc:16:65:f9:37:60
and
The network reports as: f872.eaee.becf for the same IP address.
I have changed the other WLC's to the MAC adress seen on the network for the new controller, aka changed from
bc:16:65:f9:37:60
to
f8:72:ea:ee:be:cf
I now see the controllers reporting the mobility with the new controller as 'Control Path Down', however I am at a loss as to what may be causing this?
Kind regards
Dave Bell

Mobility Group Issue

I have a WiSM configured with the same mobility group name and all pre-reqs are ok but the roaming does not works and the client lost connection when change of access-point.
I saw that RF-group are diferents and bootloader version is diferent too.
Does any one Know if bootloader and RF-group diferent can be the reason for that.
thanks a lot

An incorrect or incomplete mobility group configuration should be the most common reason for your problem. In order to overcome this, you need to ensure that your WiSM mobility group is configured correctly as follows:
The mobility group name configured must be the same on all the controllers that belong to a particular mobility group. This mobility group name is case sensitive.
The mobility group members list configured on each controller needs to contain all the controllers of that particular mobility group.
These configurations ensure that the failover occurs seamlessly and also that when the primary controller comes back on, the previously registered APs fall back to it.

WiSM redundancy, mobility groups and RF groups

Hi there
we would like to implement the following:
- Support for about 2000 LAP's
- 1 x Catalyst 6509
- 1 x Sup 720
- 7 x WiSM's
What I'm interesting is are the following points:
1. I thought that we would build the switch completly redudant, so we have to wlan switches (switch A and B) with 7 WiSM's eatch. So I can garanty a N+N redundancy --> each LAP's has a primary controller on switch A and it's secondary controller on switch B. The LAP's can be splitted on the two switches, but for your understanding there is a 1:1 redundancy. What do you think of this design, is the too much or is this appropriate?
2. As I know you can build up a mobility group of a maximum of 24 controllers or 12 WiSM's. I would put only these controllers in a mobility group, where Layer 2 roaming can occure.
3. But what is about the RF groups - there is a maximum of 1000 LAP's, so I can put only 3 WiSM's in one group. But this would not work form me, then I would have 2 WiSM's on switch A and only 1 WiSM on switch B in a RF group (not a 1:1 redundancy). First is it possible to put WiSM-A and WiSM-B into different RF groups, I think so because they are logically splitted, aren't they?
And what RF group design would be best (just as a reference)? I thought that it would make sense to form a RF group for each of the seven pairs (1 WiSM on switch A and 1 WiSM on switch B) for redundancy? What do you think of that approach?
4. So I would have 1 mobility group and 7 RF groups. Or do you recommend to form the mobility groups like the RF groups? But what happens with Layer 2 roaming in that case?
I'm sorry for the long and messy text, but I hope you can see my design questions?
Thanks a lot in advance.
Dominic

It sounds like you already have some good replies. Personally I like N+1 redundancy, but that is a designers choice. One thing I should point out is that the 6500 can only support 5 WiSM cards each. In this case a 4 WiSM x 3 chassis option would give your more spare capacity with only 12 total cards. The lower WiSM cost (12 vs 14) would help offset the cost of the extra chassis. You could also support 2400 APs with 8 WiSM cards even if one switch is down.
Not too long ago Cisco added the ability to set the priority of APs so your critical ones would join a controller and the less critical ones would go down if a controller failed and there were no redundancy. That is something to keep in mind when designing wireless. You may not need redundancy for all APs and that could affect your design and costs.
Randy

Mobility Group Member Down Status

The mobility group members from our guest controller have went into a down status twice since upgrading the 5508 WLC to software version 7.4.110. What can we do to remedy the problem?

1. First upgrade the WLC to 7.4.121.0 version (this is pretty stable).
2. paste the config and logs from WLC.
Regards
Dont forget to rate helpful posts

WLC Mobility Group problem

Hi to all,
we've two internal WLC which belong to the same MG (the default one), and one DMZ WLC which belongs to another MG.
All are running OS 4.2.61
After configuring Mobility Group using the "edit all" inserting the WLC IP address and MAC of the MGMT interface and the name of the MG which they belong, I notice a strange behaviour:
- WLC1 has Data path UP with internal's WLC2 and DMZ WLC...but Control path is down.
- WLC2 has Data path and Control path UP with DMZ WLC and only Data path UP with WLC1
- DMZ WLC has Data path and Control path UP with DMZ WLC and only Data path UP with WLC1
MG Secure Mode is disabled on all WLC's seeing the following bug CSCsk36683 (The mobility control path is down when secure mode is enabled).
Reachability via ping is OK, via eping the same but mping are not working from WLC1 to WCL2 and from DMZ WLC to WLC2
I've already restarted both controllers without success...what i've noticed is on WLC2 and DMZ WLC msglog there are a lot of these entries with a lot of RX errors ===>>>MM-3-INVALID_PKT_RECVD: Received an invalid packet from X.X.X.X. Source member:0.0.0.0. source member unknown.
any idea?
Tnx
Omar

Here is the URL for the configuration for the Mobility Group follow the URL which will help you :
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00809817ca.shtml

WLC 7.3.101.0 Mobility group peer cannot up.

Hi Guys,
It seems the 7.3.101 version Mobility group peer cannot up,: refer to the attach,
Peer 1: version: 7.3.101
Peer 2: version 7.0.98
Peer3: version 7.2.103
Today we got new two WLC for Anchor use, and config the mobility group, but it's failed and cannot up, the ping is ok.

Chris is right here. One thing I tell my clients is to allow everything between the foreign and the anchor WLC's just to verify that the mobility can come up, then lock it down. Here is some links that explain what test is for what port.
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a00809a30cc.shtml#qa8
Anchor Controller Positioning
Because the anchor controller is responsible for termination of guest WLAN traffic and subsequent access to the Internet, it is typically positioned in the enterprise Internet DMZ. In doing so, rules can be established within the firewall to precisely manage communications between authorized controllers throughout the enterprise and the anchor controller. Such rules might including filtering on source or destination controller addresses, UDP port 16666 for inter-WLC communication, and IP protocol ID 97 Ethernet in IP for client traffic. Other rules that might be needed include the following:
•TCP 161 and 162 for SNMP
•UDP 69 for TFTP
•TCP 80 or 443 for HTTP, or HTTPS for GUI access
•TCP 23 or 22 for Telnet, or SSH for CLI access
Depending on the topology, the firewall can be used to protect the anchor controller from outside threats.
For the best possible performance and because of its suggested positioning in the network, it is strongly recommended that the guest anchor controller be dedicated to supporting guest access functions only. In other words, the anchor controller should not be used to support guest access in addition to controlling and managing other LWAPP APs (LAPs) in the enterprise.
Sent from Cisco Technical Support iPhone App

WLC 5508 to WLC 5508 for Mobility Group

Hi
I have 5508 WLC (Running 7.2) in seperate buildings. I have created ACL's on both Controllers and the only thing that is failing is the Mobility Control Function. The ACL on WLC B is the Exactly the same except with some IP's being reversed. I have allowed EoIP and Mobility Traffic on both Controllers. The Data Path is Fine but the Control Path is stating down. I apologize in advance if I have been to vague. Any help would be appreciated.
Thank You
Bill

Well for mping, that is upd 16666/16667. So in your rule, your rule you shoulod have something like this:
17 16666-16666 16666-16666 Any Permit
17 16667-16667 16667-16667 Any Permit
What is the ip of the WLC's? YOur counters are all zero also.
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a0080a7c988.shtml#t4
Take a look at your show rules output without the ACL and then witht he ACL.

Multiple Ports & Mobility Groups

On our wireless network we have two 6509-E switches each with a WiSM and a 5508 WLC. The 5508 WLC only had one port connected to one of the 6509 units then we added another port on the 5508 to the other 6509. Do I need to add the IP and MAC address of the the second port of the 5508 to the existing Mobility Group?
Thanks for any help.
Jeff

When you adding mobility member you need to configure the Controller IP address & its MAC address (NOT the interface MAC address WLC connect to). Therefore in any connection type (LAG enabled or NOT) it has to be your 5508 controller IP address & its own MAC address.
If you type "show sysinfo" or "show mobility summary" on your 5508 you can get this information as shown below. Then you can add that onto your exisiting mobility group configuration of WiSM (you have to add WiSM detail on your 5508 mobility config as well)
(5508) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.5.102.0
System Name...................................... 5508
IP Address....................................... 10.10.10.10
Burned-in MAC Address............................ 64:00:F1:F5:B0:80
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
(5508) >show mobility summary
Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... dmz
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xe49d
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 9
Mobility Control Message DSCP Value.............. 0
Controllers configured in the Mobility Group
MAC Address IP Address Group Name Multicast IP Status
64:00:f1:f5:b0:80 10.10.10.10 dmz 0.0.0.0
HTH
Rasika
***** Pls rate all useful responses ****

N+1 redundancy and different mobility groups

Is it possible to backup 2 controllers with 2 different mobility groups (for example GROUP1 and GROUP2) to the same backup controller (running HA SKU N+1 (7.4)) ?
Since a controller can only be configured in 1 mobility group, this doesn't seem to be possible. Can someone confirm ?
regards,
Geert

Hello,
As per your query i can suggest you the following solution-
In all Wireless LAN Controller (WLC) versions earlier than 4.2.61.0, when a WLC goes "down," the LAP registered to this WLC can failover only to another WLC of the same Mobility Group, if the LAP is configured for failover. From Cisco WLC version 4.2.61.0 and later, a new feature called Backup Controller Support is introduced for access points to failover to controllers even outside the Mobility Group. Refer to Wireless LAN Controller and Light Weight Access Points Failover Outside the Mobility Group Configuration Example for more information.
Hope this will help you.

Mobility groups with multicast - 7.4.100.60

Hello all,
I am not sure if this is a bug, but here we go. I configured 2 controllers in a mobility group using multicast signalling.
I expect that from the moment i enable multicast, the controller joins this group AND STAYS IN THIS GROUP so he will get messages from all other controllers.
On the first hop router, i can see the join:
#sh ip igmp mem 239.194.248.10
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       <mac-or-ip-address> - last reporter if group is not explicitly tracked
       <n>/<m>      - <n> reporter in include mode, <m> reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
*,239.194.248.10               10.102.78.98    00:00:05 02:54 2A     Vl350
However, this entry does not get refreshed. I have the impression that the controller does not reply to the IGMP general queries:
IGMP(0): Send v2 general Query on Vlan350 -> no replies
#sh ip igmp mem 239.194.248.10
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       <mac-or-ip-address> - last reporter if group is not explicitly tracked
       <n>/<m>      - <n> reporter in include mode, <m> reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
*,239.194.248.10               10.102.78.98    00:02:35 00:24 2A     Vl350
>> 20 seconds from expiry.
#sh ip igmp mem 239.194.248.10
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       <mac-or-ip-address> - last reporter if group is not explicitly tracked
       <n>/<m>      - <n> reporter in include mode, <m> reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
>> 20 seconds later, gone
>> At this moment the controller doesn't receive any messages anymore from remote controllers:
>>sh ip mroute 239.194.248.10
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group
       V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.194.248.10), 00:05:38/00:00:21, RP 10.102.90.20, flags: SP
Incoming interface: Port-channel30, RPF nbr 10.102.78.13, RPF-MFD
Outgoing interface list: Null
This is seen on 8500 platform running 7.4.100.60
We have also WISMs running at 7.0.230.0, and there it can be seen that the entry refreshes every minute (like it should be)
IGMP(0): Received v2 Report on Vlan950 from 10.96.9.67 for 239.194.240.1
IGMP(0): Received Group record for group 239.194.240.1, mode 2 from 10.96.9.67 for 0 sources
IGMP(0): Updating EXCLUDE group timer for 239.194.240.1
IGMP(0): MRT Add/Update Vlan950 for (*,239.194.240.1) by 0
Shouldn't the controller at all times stay joined in its mobiility group ?

ok, some more debugging.
I loaded up 7.4.100.60 on a 5500 controller and got the same result.
NOTE: my global multicast settings are:
Controller->General: AP Multicast Mode: UNICAST
Controller->Multicast->Global Multicast is NOT enabled
Controller->Mobility->Multicast Messaging: enabled and group is 239.194.240.3
With this config, the IGMP entry is not retained, and i see on the controller the message (debug bcast all):
>>processEthernetIGMPpacket Received IGMP Pkt from DS when either igmp snooping or global multicast is disabled.
So, i then enabled Global Multicast (Controller->Multicast->Global Multicast to enable), and then the IGMP entry is refreshed:
bcastReceiveTask: Sep 05 13:11:17.734: IGMP packet received over vlanid = 102 from DS side
*bcastReceiveTask: Sep 05 13:11:17.734: received an IGMP query for multicast vlan = 102 address 0.0.0.0 intfnum = 3
*bcastReceiveTask: Sep 05 13:11:17.734: IGMP report scheduled for grp=0xefc2f003, vlan=102, intf=3, slot=70, maxRespTime=100
>>sh ip igmp membership 239.194.240.3
004586: Sep 5 15:11:50.710 CEST: IGMP(0): Send v2 general Query on Vlan101
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       - last reporter if group is not explicitly tracked
       /      - reporter in include mode, reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
*,239.194.240.3                10.102.180.218 00:38:51 02:28 2A     Vl102
Now, on the 5500 controller i can enable global multicast, while AP multicast mode is in UNICAST.
However, on the 8500 controller, running the same firmware (7.4.100.60), when i try to enable "Global Multicast", i get:
"Multicast-Unicast mode does not support IGMP/MLD snooping. Config mode to multicast-multicast first". I did not get this message on the 5500.
So when switching to Multicast->Multicast mode, and then enabled "Global Multicast", then it works.
This means that in order to have mobility messaging working on 8500 in multicast, you MUST put the AP Multicast Mode to Multicast AND you must enabled "Global Multicast", otherwise it won't work.

Mobility Group Requirements for Guest Anchor WLC

Hello -
I've alway assumed you can't create a guest tunnel between a local WLC and an anchor WLC that are in different mobility groups.   However, I was told recently (without much detail) that this is possible. So I have set out to test this.
I am trying to point one of my local WLCs guest SSIDs to a guest anchor WLC in a different mobility group.   I have a maintenance window coming up and I am looking to anchor the clients on one campus to the anchor WLC on the other campus so guest service does not go down.   Each campus is it's own mobility group.   In trying to set this up I went to the "mobility anchors" screen for the guest SSID on one of the local WLCs and I am unable to add the anchor WLC from the other campus because it's non in the drop-down menu. This is because it's not in the same mobility group.   So my question is how do I anchor clients coming through a local WLC in one mobility group to an anchor WLC in another mobility group?
To me it doesn't seem possible without significant configuration changes.   I don't want to reconfigure/recreate mobility groups.
Thanks
Chuck

Not only is it possible, I would recommend it. However, you may be confusing some concepts.
The Mobility Group is different than the Mobility Domain. I generally refer to the Mobility Group as those WLCs with the same Default Mobility Group Name, and the Mobility Domain as the entire Mobility List (where you can define up to 72 controllers from various mobility groups).
The point is that if WLCs 1-10 are GroupA, and WLCs 11-20 are GroupB, for anchoring to work you at least need to add the anchor to the mobility list of the foreign wlc, and vice versa.
If you notice, when you add a mobility entry to the list, it should ask you for mobility group. If you leave it blank, it should default to that of that WLC, but on GroupA controllers, you could define GroupB controllers (and specific GroupB) and then you should now have mobility established between your controllers and the Anchor configuration will have your anchors in the drop-down....
Does that make sense?

WLC Mobility Group Confusion

Can some please clarify how Mobility groups work and when to use them. I have 2 data centers, each with a WLC, for centralized control. I just want to provide simple redundancy.
When should I use an Anchor group.
Thanks for your help.

To make it simple, any wlc's that will be a primary, secondary or tertiary WLC for lap's will need to be placed in the same mobility group. Now if you have a guest anchor controller for guest, then that will need to be added in the same mobility group. Bottom line, when users roam from AP to AP from WLC to another even getting tunneled (anchor) the WLC's need to be aware of the roaming and that is what mobility group does.
Anchor is if you want to tunnel users to a specific controller like in a guest wireless situation when the WLC is located in the DMZ. There are other reasons, but this is most likely why.

WiSM - Mobility Group - Control Path Down

Similar Messages

Maybe you are looking for