topic Re: AP 1010 join wrong WLC in Wireless

AP 1010 join wrong WLC

hkj0516 — Sat, 03 Jul 2021 23:56:11 GMT

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

Re: AP 1010 join wrong WLC

jordanperks — Tue, 30 Dec 2008 21:57:59 GMT

I have seen it before with 1131s. The issue stemmed from my controllers being in the same mobility group, but had completely different configs. Are all of your controllers in the same mobility group? If so, do they all have the same basic config?

Once I removed the controllers from the same mobility group the APs began associating with the controller I told it to.

Re: AP 1010 join wrong WLC

Scott Fella — Wed, 31 Dec 2008 01:59:14 GMT

John is right.... check your mobility group and config. Also, do you have any issues with other ap's moving from the 4400 to the WiSM or vice-versa? What you can look at is the log on the AP. This can tell you if it initially joins, but either gets rejected or if it never does get a join response. All the WLC's in the same subnet?

Re: AP 1010 join wrong WLC

hkj0516 — Sun, 04 Jan 2009 18:56:30 GMT

My mobility group is same to all WLC. The AP is AP1010. So, I can't look at the any log on the AP.

All the WLC's interface management is different subnet.

The IBC-AP's are connect to Cisco 3750. I have define DHCP pool for IBC-AP's on the 3750.

The DHCP configuration is below:

ip dhcp pool NET_65

network 10.100.65.0 255.255.255.0

default-router 10.100.65.1

domain-name wri

option 43 ascii "10.100.64.150"

option 60 ascii "Airespace.AP1200"

The 4402-50-IBC management IP is 10.100.64.150 and I have configure the primary WLC to 4402-50-IBC for all IBC-AP. But, the all IBC-AP's always join to WiSM-1 and WiSM-2. I can't have any AP log on the 4402-50-IBC.

How to confirm the WLC system name is correct on all WLC's?

My object of IBC-APs have two SSID's. One SSID name is PUBLIC, other SSID name is IBC.

When the 4402-50-IBC is down, the IBC-AP's can re-join WiSM-1 or WiSM-2. The client is connect to PUBLIC to ensure work.

Re: AP 1010 join wrong WLC

hkj0516 — Mon, 05 Jan 2009 02:39:09 GMT

This is my wireless topology.

Re: AP 1010 join wrong WLC

Leo Laohoo — Wed, 14 Jan 2009 05:55:40 GMT

It's a bug with the v4.x between the HTML and the CLI) particularly when you specify the primary/secondary/tertiary controllers using CLI.

The work-around is to use the CLI on the WLC:

config ap primary-base

config ap secondary-base

config ap tertiary-base

Does this response help?

Re: AP 1010 join wrong WLC

hkj0516 — Wed, 14 Jan 2009 06:36:10 GMT

Do you know this bug id ?

Re: AP 1010 join wrong WLC

hkj0516 — Wed, 14 Jan 2009 15:53:10 GMT

The WLC is running version 4.1.185.

It can't use this CLI.

config ap primary-base

Re: AP 1010 join wrong WLC

Leo Laohoo — Wed, 14 Jan 2009 23:23:32 GMT

The command works:

http://www.cisco.com/en/US/partner/docs/wireless/controller/4.1/command/reference/clic1.html#wp1553111

config ap primary-base [WLC_Controller_IP_Address]

Can you try to enter the command:

config ap primary-base ?

I am sure you can enter the WLC_Controller_IP_Address after that.

Re: AP 1010 join wrong WLC

Leo Laohoo — Wed, 14 Jan 2009 23:31:25 GMT

The command works:

http://www.cisco.com/en/US/partner/docs/wireless/controller/4.1/command/reference/clic1.html#wp1553111

config ap primary-base [WLC_Controller_IP_Address]

Can you try to enter the command:

config ap primary-base ?

I am sure you can enter the WLC_Controller_IP_Address after that.

Re: AP 1010 join wrong WLC

hkj0516 — Thu, 15 Jan 2009 17:17:50 GMT

I am input the WLC_Controller_IP_Address. This display is "Incorrect input! Use 'config ap primary-base '"

It's not input WLC_Controller_IP_Address .

Re: AP 1010 join wrong WLC

Leo Laohoo — Thu, 15 Jan 2009 22:29:43 GMT

Can you please change WLC_Controller_IP_Address to YOUR controller's Management IP Address?

Re: AP 1010 join wrong WLC

Scott Fella — Sat, 17 Jan 2009 05:03:17 GMT

You can only input the WLC System name not the ip on the code you are running. I think the 5.x code has the option to specify the ip address also, but I would not suggest you upgrade to the 5.x. So just enter the WLC system name in the field.

Re: AP 1010 join wrong WLC

hkj0516 — Sat, 17 Jan 2009 05:38:21 GMT

YES~

The WLC IP is Management IP Address.

Re: AP 1010 join wrong WLC

hkj0516 — Sat, 17 Jan 2009 06:03:32 GMT

My customer AP is AP1000. It's support 4.x.

I think I must to find what happened to bring this problem.

I was reboot a AP. It mac address is 00:0b:85:84:ed:10. The result is

display below.

5 16:07:48 2009: 00:0b:85:84:ed:10 Received LWAPP DISCOVERY REQUEST

from AP 00:0b:85:84:ed:10 to 00:0b:85:43:d4:e0 on port '1'

Mon Jan 5 16:07:48 2009: 00:1e:14:04:a6:c9 Successful transmission of

LWAPP Discovery-Response to AP 00:0b:85:84:ed:10 on Port 1

It's successful find to WLC4402. But, It's not registration the WLC.

Re: AP 1010 join wrong WLC

Scott Fella — Sat, 17 Jan 2009 16:33:23 GMT

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.

Re: AP 1010 join wrong WLC

hkj0516 — Sat, 17 Jan 2009 17:10:19 GMT

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.

Re: AP 1010 join wrong WLC

Scott Fella — Sat, 17 Jan 2009 17:19:48 GMT

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.

Re: AP 1010 join wrong WLC

hkj0516 — Sat, 17 Jan 2009 17:53:08 GMT

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.

Re: AP 1010 join wrong WLC

Scott Fella — Sat, 17 Jan 2009 20:19:24 GMT

Glad to be of help:)