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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Cisco AP1142N won't join controller

Hi

 

When upgrading one of our WISM controller cards a problem occurred with some AP1142N.

The can’t join controller with 7.6.120.0, upgrading was from 7.4.121.0

 

When CLI into the AP I got this messages:

 

  1. Reboot and tries to connect to the WISM2 with  7.6.120.0, but it fails.
  2. Then tries to connect to another WISM2 with 7.4.121.0 and this work
  3. But then the image on the AP is not correct (have a 7.6.120.0 image)
  4. Downgrading AP to 7.4.121.0 image
  5. Reboot and are back to number 1.

 

*Mar  1 00:01:09.564: %CAPWAP-3-ERRORLOG: Selected MWAR 'JKP-WISM-02-I '(index 0).

*Mar  1 00:01:09.564: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Sep 10 11:25:00.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.16.25 peer_port: 5246

*Sep 10 11:25:29.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!

 

 

Translating "CISCO-CAPWAP-CONTROLLER.net.yyyy.se"...domain server (xxx.xxx.xxx.xxx) [OK]

 

*Mar  1 00:00:59.550: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Mar  1 00:01:09.564: %CAPWAP-3-ERRORLOG: Selected MWAR 'JKP-WISM-02-I '(index 0).

*Mar  1 00:01:09.564: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Sep 10 11:25:00.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.16.25 peer_port: 5246

*Sep 10 11:25:29.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!

*Sep 10 11:25:59.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.17.16.25:5246

*Sep 10 11:26:00.000: %CAPWAP-3-ERRORLOG: Selected MWAR 'JKP-WISM-02-I (index 0).

*Sep 10 11:26:00.000: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Sep 10 11:25:00.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.16.25 peer_port: 5246

*Sep 10 11:25:30.000: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!

examining image...

extracting info (292 bytes)

Image info:

    Version Suffix: k9w8-.124-23c.JA8

    Image Name: c1140-k9w8-mx.124-23c.JA8

    Version Directory: c1140-k9w8-mx.124-23c.JA8

    Ios Image Size: 4915712

    Total Image Size: 5110272

    Image Feature: WIRELESS LAN|LWAPP

    Image Family: C1140

    Wireless Switch Management Version: 7.0.250.0

Extracting files...

c1140-k9w8-mx.124-23c.JA8/ (directory) 0 (bytes)

extracting c1140-k9w8-mx.124-23c.JA8/T5.bin (23836 bytes)

*Sep 10 11

extracting c1140-k9w8-mx.124-23c.JA8/8001.img (174932 bytes):25:59.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.17.16.25:5246

Everyone's tags (1)
4 REPLIES
Hall of Fame Super Gold

Power down the AP for about

Power down the AP for about ten seconds and power it back up.  See if this fixes it.

New Member

With a WISM, you have by

With a WISM, you have by definition an etherchannel between your controller & APs.  Try setting the load balancing algorithm on the switch housing the WISM to src-dst-mac before connecting the AP.  There is/was an issue that shows itself rarely where other load balancing mechanisms interfere with an AP's initial join to a controller.  The problem declined significantly over the years, but you may be running into it. 

Once the AP joins, you can reset your load balancing and you shouldn't have the problem even if the AP reboots later.  It usually impacts APs that have never joined your controller.  Don't know why.  Since this was an upgrade it may not be your problem, but it won't hurt to try.

New Member

I have located the problem to

I have located the problem to bug QSCuh46442.

159
Views
0
Helpful
4
Replies
CreatePlease to create content