Problem configuring mobility group

Unanswered Question
Nov 5th, 2008
User Badges:

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?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
jeff.kish Thu, 11/06/2008 - 07:05
User Badges:
  • Silver, 250 points or more

What do you mean by "Cards"? Are these WiSM blades, or are they WLC modules on an ISR?


Have you added the other controllers to each controller's list of mobility group controllers?

Scott Fella Thu, 11/06/2008 - 07:15
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

I think he is referring to the WiSM's. One WiSM in a chassis is in one mobility group and the other WiSM is in another and separated by a FW???


I Think that is what he meant.

Scott Fella Thu, 11/06/2008 - 07:12
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

Is both the control path and data path down? Do an mping from the two wlcs, if the mping fails then UDP 16666 & 16667 (if using secure mobility) are blocked. If eping fails between the two, then IP 97 is blocked. These are all you need to configure mobility between a FW. Make sure the mac address, IP address and mobility group name are correct on the mobility group configuration.

Tyrone Van Der Haar Thu, 11/06/2008 - 07:45
User Badges:

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


Tyrone Van Der Haar Thu, 11/06/2008 - 08:09
User Badges:

mping and eping only works from those that are "UP"

##FROM .47## 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 Up

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 Up


#FROM .42## 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 Up

00:1e:4a:fa:99:60 x.x.x.15 brf Control Path Down

00:1e:4a:fa:99:80 x.x.x.47 brf Up

Scott Fella Thu, 11/06/2008 - 08:23
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

Looks like you configuration of your mobility group is wrong.... WiSM (10/15) is not going through a FW and the mobiliity is not up. Make sure you either have Symetric tunneling enabled on all or disabled. Can you post your show run-config?

Tyrone Van Der Haar Thu, 11/06/2008 - 09:35
User Badges:

Now I got the wism 10/15 to form a mobility group, I found a static route in the running config of the wism.

How would I get the others up or how can I troubleshoot some more?




Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode