Need help getting 3500 AP to talk to WLC 2100

[avrilsalter]

Hello,

I am trying to config my wireless lan controller (WLC) 2106 to discover my new 3500 access points.

I followed the example Cisco configuration doc. 69719.

I am using a Cisco 3760 switch to interconnect the AP and WLC.

I set up DHCP in the switch.

I update the sw on the controller

Product Name..................................... Cisco Controller
Product Version.................................. 7.0.116.0

The ap is getting an ip address.

I can ping WLC to AP.

When I turn on debug events in WLC I get

(Cisco Controller) >*spamReceiveTask: Jul 17 22:34:04.255: 64:9e:f3:0e:a6:f9 Discovery Request from 10.5.5.142:60016

*spamReceiveTask: Jul 17 22:34:04.255: 64:9e:f3:0e:a6:f9 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 6, joined Aps =0
*spamReceiveTask: Jul 17 22:34:20.156: 64:9e:f3:0e:a6:f9 Discovery Request from 10.5.5.142:60016

*spamReceiveTask: Jul 17 22:34:20.156: 64:9e:f3:0e:a6:f9 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 6, joined Aps =0
no de*spamReceiveTask: Jul 17 22:35:58.058: 64:9e:f3:0e:a6:f9 Discovery Request from 10.5.5.143:60016

*spamReceiveTask: Jul 17 22:35:58.058: 64:9e:f3:0e:a6:f9 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 6, joined Aps =0
*spamReceiveTask: Jul 17 22:36:13.959: 64:9e:f3:0e:a6:f9 Discovery Request from 10.5.5.143:60016

*spamReceiveTask: Jul 17 22:36:13.959: 64:9e:f3:0e:a6:f9 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 6, joined Aps =0
*spamReceiveTask: Jul 17 22:36:29.860: 64:9e:f3:0e:a6:f9 Discovery Request from 10.5.5.143:60016

*spamReceiveTask: Jul 17 22:36:29.860: 64:9e:f3:0e:a6:f9 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 6, joined Aps =0
*spamReceiveTask: Jul 17 22:38:07.762: 64:9e:f3:0e:a6:f9 Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '1'
*spamReceiveTask: Jul 17 22:38:07.762: 64:9e:f3:0e:a6:f9 Discarding discovery request in LWAPP from AP supporting CAPWAP

*spamReceiveTask: Jul 17 22:38:23.663: 64:9e:f3:0e:a6:f9 Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '1'
*spamReceiveTask: Jul 17 22:38:23.663: 64:9e:f3:0e:a6:f9 Discarding discovery request in LWAPP from AP supporting CAPWAP

Does anyone know what the problem might be?

I really would appreciate some guidance.

Avril

[Leo Laohoo]

Can you please post the following outputs:

1.  WAP:  sh version;

2.  WAP:  sh inventory; and

3.  WLC:  sh sysinfo

[avrilsalter]

Hello Leo,

I have attached the info you requested.

Except the WAP sh inventory -- because it shows nothing.

I discovered this bug + a problem with my DNS settings.

I now have the WLC sending a discovery response. But the AP is not responding.

Showing a DTLS fetal alert! So the secure tunnel is not set up.

I amwondering if it could be a certificate error, but I am fishing in the dark

I have attached new configs, error msgs, etc..

I so appreciate any direction.

Thanks,

Avril

[Leo Laohoo]

Except the WAP sh inventory -- because it shows nothing.

What do you mean "it shows nothing"???

Kindly post the output to the following commands:

1.  WAP:  sh version;

2.  WAP:  sh inventory

[avrilsalter]

I have had problems uploading files to this site for the past 16 hours. Not sure if anyone else has a problem

My problems was fixed. A combination of

- changing the WLC management and AP manager interfaces to native (and the same on the switch)

- applying this Cisco bug fix

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtw55476

Thank you Loe for looking it to this.

Avril

[avrilsalter]

Sorry Leo -- I spelt you name wrong

[Saravanan Lakshmanan]

Can force the AP to try on capwap.

AP#debug capwap con cli

AP#test capwap controller ip

AP#test capwap controller name