Buy or Renew
Buy or Renew
Cisco Virtual Engineer generative AI bot now active in Wireless Discussion Forum. Learn more.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1247
Views
0
Helpful
5
Replies

3602E won't connect to 5508 WLAN

Gerald Mulvaney
Level 1
Level 1

‎08-12-2013 02:59 PM - edited ‎07-04-2021 12:38 AM

Hi all,

This is a lab system that I'm just building out- I try to see the obvious but it does bite me occasionally.  I have a 5508 WLC running release 7.4.1.  My AP's are all Cisco 3602E's with the AC modules.  My problem is that the Access points can't seem to join the WLAN- I can see them talking, debug output below. They are pingable from the WLC CLI, verified that options 43 and 60 are ok, Here's my debug:

Under SECURITY > AAA > AP Policies the only thing checked is:

Accept Manufactured Installed Certificate (MIC)

*spamApTask4: Aug 12 17:35:35.724: ec:e1:a9:da:65:b0 CAPWAP Control Msg Received from 192.168.1.79:34805

*spamApTask4: Aug 12 17:35:35.724: ec:e1:a9:da:65:b0 packet received of length 1400 from 192.168.1.79:34805

*spamApTask4: Aug 12 17:35:35.724: ec:e1:a9:da:65:b0 Msg Type = 3 Capwap state = 0

*spamApTask4: Aug 12 17:35:35.725: ec:e1:a9:da:65:b0 Total msgEleLen = 1348

*spamApTask4: Aug 12 17:35:35.725: ec:e1:a9:da:65:b0 Total msgEleLen = 1279

*spamApTask4: Aug 12 17:35:35.725: ec:e1:a9:da:65:b0 Total msgEleLen = 1235

*spamApTask4: Aug 12 17:35:35.725: ec:e1:a9:da:65:b0 Total msgEleLen = 1215

*spamApTask4: Aug 12 17:35:35.725: ec:e1:a9:da:65:b0 Total msgEleLen = 1207

*spamApTask4: Aug 12 17:35:35.725: ec:e1:a9:da:65:b0 Total msgEleLen = 1202

*spamApTask4: Aug 12 17:35:35.725: ec:e1:a9:da:65:b0 Total msgEleLen = 1197

*spamApTask4: Aug 12 17:35:35.726: ec:e1:a9:da:65:b0 Total msgEleLen = 1189

*spamApTask4: Aug 12 17:35:35.726: ec:e1:a9:da:65:b0 Total msgEleLen = 1183

*spamApTask4: Aug 12 17:35:35.726: ec:e1:a9:da:65:b0 Vendor specific payload from AP  EC:E1:A9:DA:65:B0 validated

*spamApTask4: Aug 12 17:35:35.726: ec:e1:a9:da:65:b0 Total msgEleLen = 1166

*spamApTask4: Aug 12 17:35:35.726: ec:e1:a9:da:65:b0 Vendor specific payload from AP  EC:E1:A9:DA:65:B0 validated

*spamApTask4: Aug 12 17:35:35.726: ec:e1:a9:da:65:b0 Created AP ec:e1:a9:da:65:b0

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1348

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1279

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1235

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1215

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1207

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1202

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1197

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1189

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1183

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Vendor specific payload from AP  EC:E1:A9:DA:65:B0 validated

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join request: Vendor payload type = 2, length = 13

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1166

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Vendor specific payload from AP  EC:E1:A9:DA:65:B0 validated

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join request: Vendor payload type = 207, length = 10

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1152

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Vendor specific payload from AP  EC:E1:A9:DA:65:B0 validated

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join request: Vendor payload type = 123, length = 19

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1129

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1120

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 1111

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Vendor specific payload from AP  EC:E1:A9:DA:65:B0 validated

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join request: Vendor payload type = 104, length = 1107

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Sending encrypted packet to AP 192.168.1.79(34805)

*spamApTask4: Aug 12 17:35:35.727: ec:e1:a9:da:65:b0 Join Request: Total msgEleLen = 0

*spamApTask0: Aug 12 17:35:35.728:  Received SPAM_GOT_AAA_RESPONSE

*spamApTask0: Aug 12 17:35:35.728: ec:e1:a9:da:65:b0 DTLS connection 0x1769a5b0 closed by controller

*spamApTask0: Aug 12 17:35:35.728: DTL Deleting AP 36 - 0.0.0.0

*spamApTask4: Aug 12 17:35:35.729: CAPWAP DTLS connection closed msg

My console messages from the AP are:

*Aug 12 21:54:09.135: %MESH-6-LINK_UPDOWN: Mesh station f872.eae8.7f40 link Down

*Aug 12 21:54:11.135: %LINK-6-UPDOWN: Interface BVI1, changed state to down

*Aug 12 21:54:16.079: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Aug 12 21:54:16.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.21 peer_port: 5246

*Aug 12 21:54:19.555: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down

*Aug 12 21:54:19.555: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Aug 12 21:54:20.031: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Aug 12 21:54:25.187: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Aug 12 21:54:25.195: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Aug 12 21:54:26.187: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Aug 12 21:54:26.215: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Aug 12 21:54:27.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Aug 12 21:54:49.531: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Aug 12 21:54:49.539: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Aug 12 21:54:49.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!

*Aug 12 21:54:50.531: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Aug 12 21:54:50.559: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Aug 12 21:54:51.559: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Aug 12 21:54:59.671: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.21:5246

*Aug 12 21:54:59.671: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Aug 12 21:54:59.671: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Aug 12 21:54:16.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.21 peer_port: 5246

*Aug 12 21:54:16.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Aug 12 21:54:16.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Aug 12 21:54:17.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Aug 12 21:54:17.031: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Aug 12 21:54:17.999: %LINK-6-UPDOWN: Interface BVI1, changed state to up

*Aug 12 21:54:18.031: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Aug 12 21:54:18.999: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up

*Aug 12 21:54:21.159: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.21:5246

*Aug 12 21:54:21.199: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.1.80, mask 255.255.255.0, hostname APf872.eae8.7f40

Odd thing is that I am seeing this under recent traps, although I am not using any AAA sergver or RADIUS server- none are configured at all.

Thanks!

Jerry

1 person had this problem
Labels:
0 Helpful
5 Replies 5

Marco Gonzalez
Level 1
Level 1

‎08-12-2013 08:45 PM

I would upgrade your wireless LAN controller to 7.5 version because the 802.11ac technology is supported on that version only so the access point might be waiting for that version to join. I say might because I don't have access points with ac modules yet but I am completelly sure and possitive that 802.11ac is supported from the 7.5 version so, if you have the modules and want to use the ac technology you will need to upgrade your WLC anyways.

Best regards,

Marco Gonzalez

0 Helpful

Gerald Mulvaney
Level 1
Level 1
In response to Marco Gonzalez

‎08-13-2013 03:27 AM

Thanks, Marco- I tried that as well. I have the AC modules installed now running

7.5.102.0 (default) (active), and I can see the AC options- unfortunately, same results as before- can't seem to add any access points.

0 Helpful

Gerald Mulvaney
Level 1
Level 1

‎09-26-2013 09:40 AM

Fixed, finally.  The AP's were shipped in mesh mode for some reason.   Added the macs to the filter list, at which point they showed up as bridged. Changed the mode and worked fine.  It's hard to believe that more people aren't having this problem as documentation on it seems minimal- in any case, it's fixed.

0 Helpful

Dale Wood
Level 1
Level 1

‎05-09-2014 10:47 AM

Thanks for that. We had the same problem. This fixed it.

0 Helpful

jmeachum
Level 1
Level 1

‎05-28-2014 04:40 PM

You can either add the AP into the filter list on the WLC or reset it using the Mode button.  It is running in MESH mode as Mulvanj pointed out.

John

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card