AP 1010 join wrong WLC

[hkj0516]

Dear all,

I have 1 WISM and 1 4402-50 and running on OS4.1.185

They name are WISM-1, WISM-2, 4402-50.

The AP was got ip by DHCP server.

I have configure primary wlc is 4402-50, secondary wlc is WISM-2 and tertiary wlc is WISM-1.

But, the AP1010 always join secondary and tertiary, it's not to join primary.

Have anyone to same issus?

THANKS

Stephen

[Scott Fella]

If you run a show mobility summary from the 4400, do you see the other wlc's as up? If not, then the ap1000 already has the information for wism1 & wism2 thus will not join the 4400.

What ap's do you have on the 4400 currently and can you fail any of the ap's to the wism and vice versa.

[hkj0516]

The all mobility WLC's status are up on the 4402.

I was see some information on this WLC.

Sun Jan 18 00:35:39 2009: 00:0b:85:84:ea:90 Received LWAPP PRIMARY_DISCOVERY_REQ from AP 00:0b:85:84:ea:90

Sun Jan 18 00:36:00 2009: 00:0b:85:84:ea:90 Received LWAPP DISCOVERY REQUEST from AP 00:0b:85:84:ea:90 to 00:0b:85:43:d4:e0 on port '1'

I think this is the AP find the 4402 information.

[Scott Fella · Accepted solution]

Well, it looks like there isn't a join response.... again, do you have any ap's on the wism's in which you can move to the 4400 or the other way around. This will identify if mobility is working.

If you don't have any ap's on the 4400, then try to ping the AP manager IP address.... you shouldn't be able to. Disconnect the 4400 from the network and see if you can ping that address. You might have a duplicate address for the AP manager which might cause the output you are seeing.

[hkj0516]

Thank you for your infromation. I found some misconfiguration. My AP manager IP address have a duplicate address.

So, I'm change AP manager IP address. It's work.

[Scott Fella]

Glad to be of help:)