Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

LAP 1141N Join problem on WLC 4402 Ver 7.0

Hi All,

Please, I need your help with LAP join proccess:

70:ca:9b:25:5b:9d -> AP MAC

10.10.1.30 -> DNS

Thanks in advance!

debug capwap events:

*spamReceiveTask: Mar 07 11:23:14.661: 70:ca:9b:25:5b:9d Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '1'

*spamReceiveTask: Mar 07 11:23:24.660: 70:ca:9b:25:5b:9d Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '1'

*spamReceiveTask: Mar 07 11:23:34.660: 70:ca:9b:25:5b:9d Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '1'

*spamReceiveTask: Mar 07 11:23:44.660: 70:ca:9b:25:5b:9d Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '1'

*spamReceiveTask: Mar 07 11:23:54.660: 70:ca:9b:25:5b:9d Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '1'

*spamReceiveTask: Mar 07 11:24:04.659: 70:ca:9b:25:5b:9d Discovery Request from 10.10.1.30:46525

*spamReceiveTask: Mar 07 11:24:04.660: 70:ca:9b:25:5b:9d Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =21

*spamReceiveTask: Mar 07 11:24:14.659: 70:ca:9b:25:5b:9d Discovery Request from 10.10.1.30:46525

*spamReceiveTask: Mar 07 11:24:14.659: 70:ca:9b:25:5b:9d Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =21

*spamReceiveTask: Mar 07 11:24:24.659: 70:ca:9b:25:5b:9d Discovery Request from 10.10.1.30:46525

*spamReceiveTask: Mar 07 11:24:24.659: 70:ca:9b:25:5b:9d Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =21

*spamReceiveTask: Mar 07 11:24:34.659: 70:ca:9b:25:5b:9d Discovery Request from 10.10.1.30:46525

*spamReceiveTask: Mar 07 11:24:34.659: 70:ca:9b:25:5b:9d Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =21

*spamReceiveTask: Mar 07 11:24:44.658: 70:ca:9b:25:5b:9d Discovery Request from 10.10.1.30:46525

*spamReceiveTask: Mar 07 11:24:44.659: 70:ca:9b:25:5b:9d Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =21

*spamReceiveTask: Mar 07 11:24:54.658: 70:ca:9b:25:5b:9d Discovery Request from 10.10.1.30:46525

*spamReceiveTask: Mar 07 11:24:54.658: 70:ca:9b:25:5b:9d Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =21

*spamReceiveTask: Mar 07 11:25:04.658: 70:ca:9b:25:5b:9d Discovery Request from 10.10.1.30:46525

*spamReceiveTask: Mar 07 11:25:04.658: 70:ca:9b:25:5b:9d Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =21

*spamReceiveTask: Mar 07 11:25:14.658: 70:ca:9b:25:5b:9d Discovery Request from 10.10.1.30:46525

*spamReceiveTask: Mar 07 11:25:14.658: 70:ca:9b:25:5b:9d Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =21

*spamReceiveTask: Mar 07 11:25:24.658: 70:ca:9b:25:5b:9d Discovery Request from 10.10.1.30:46525

*spamReceiveTask: Mar 07 11:25:24.658: 70:ca:9b:25:5b:9d Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =21

*spamReceiveTask: Mar 07 11:25:34.657: 70:ca:9b:25:5b:9d Discovery Request from 10.10.1.30:46525

*spamReceiveTask: Mar 07 11:25:34.658: 70:ca:9b:25:5b:9d Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =21

8 REPLIES
Hall of Fame Super Silver

Re: LAP 1141N Join problem on WLC 4402 Ver 7.0

Have you tried to place the ap on the same subnet as the management and ap manager interface to see if the ap joins. That is the easiest way to have an ap join. You can change the ports vlan after the ap has joined.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***

LAP 1141N Join problem on WLC 4402 Ver 7.0

what version of code are you running on the WLC?  can you show the output from show interface summary?  While running the debug capwap events enable please also enable debug capwap errors enable.

Steve

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
New Member

LAP 1141N Join problem on WLC 4402 Ver 7.0

Thanks for answer.

Scott, I don't know the reason, I can't give an IP in the same subnet, do you know how configure manually an IP to AP?

3 subnet on the same vlan.

interface Vlan150

ip address 10.126.96.1 255.255.254.0 secondary

ip address 10.160.96.1 255.255.254.0 secondary  ->ap manager subnet

ip address 160.10.1.1 255.255.255.0  -> IP AP 160.10.1.50

ip helper-address 10.10.1.30

Stephen,

How know the code?

Interface summary:

Interface Name                   Port Vlan Id  IP Address      Type    Ap Mgr Guest

-------------------------------- ---- -------- --------------- ------- ------ -----

ap-manager                       1    untagged 10.160.96.11    Static  Yes    No

management                       1    untagged 10.160.96.10    Static  No     No

vlan 140                         1    140     10.125.96.30    Dynamic No     No

vlan 160                         1    160      10.160.18.2     Dynamic No     No

vlan 170                         1    170      10.160.10.2     Dynamic No     No

Debug:

*spamReceiveTask: Mar 07 17:36:33.442: 70:ca:9b:25:5b:9d Discovery Request from 160.10.1.50:46525

*spamReceiveTask: Mar 07 17:36:33.442: 70:ca:9b:25:5b:9d Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =21

*spamReceiveTask: Mar 07 17:36:33.442: 70:ca:9b:25:5b:9d Received a Discovery Request from 70:CA:9B:25:5B:9D via IP broadcast address but the source IP address (160.10.1.50) is not in any of the configured subnets. Dropping it

*spamReceiveTask: Mar 07 17:36:33.442: 70:ca:9b:25:5b:9d State machine handler: Failed to process  msg type = 1 state = 0 from 160.10.1.50:46525

*spamReceiveTask: Mar 07 17:36:33.442: 70:ca:9b:25:5b:9d Failed to parse CAPWAP packet from 160.10.1.50:46525

Re: LAP 1141N Join problem on WLC 4402 Ver 7.0

The WLC doesn't work well with secondary addresses/interfaces in the same subnet.

Basically what is happening is the WLC is getting  the discovery packet as a broadcast, that is untagged as it's supposed to be in the same VLAN as the management, but the source IP is not correct as the WLC sees it.

Is it possible for you to create a new subnet for the AP?  You can use the 160.10.1.x address space. 

Steve

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
New Member

Re: LAP 1141N Join problem on WLC 4402 Ver 7.0

It's complicated, because I have others AP connected. It's strange because others work with IP  160.10.1.x and 10.160.96.x

Re: LAP 1141N Join problem on WLC 4402 Ver 7.0

as I said, it doesn't work well.

Sometimes it will, sometimes it won't.  From my tenure in TAC, we would never have recommended secondaries as it can cause really weired issues.

Steve

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
New Member

Re: LAP 1141N Join problem on WLC 4402 Ver 7.0

Stephen,

There are two controllers, one does not have secondary networks.
How I can configure the AP that attempts to connect to the secondary WLC?

Re: LAP 1141N Join problem on WLC 4402 Ver 7.0

you could add option 43 to the DHCP scope pointing at the management interface of the WLC that doesn't have the secondary.  If you have all of your AP set with a primary WLC, you could try enabling Master Controller Mode on it as well. This would supercede the discovery mechanism and force the AP to join that WLC.

Steve

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
980
Views
0
Helpful
8
Replies
CreatePlease to create content