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

AP 1042N with ios 15.2(4)JB5 is not joining to WLC with ios 7.4.121.0

 

I am trying to add AP 1042N with ios15.2(4)JB5  in WLC 2504 with IOS version 7.4.121.0 , but AP is not joining and

Below mentioned is the log I am getting in the AP , here 192.168.100.10 is WLC ip

 

*May 20 19:31:22.745: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*May 20 19:51:24.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.100.10 peer_port: 5246
*May 20 19:51:24.804: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.100.10 peer_port: 5246
*May 20 19:51:24.805: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.100.10
*May 20 19:51:29.804: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.100.10
*May 20 19:52:23.222: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.100.10
*May 20 19:52:23.222: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.100.10:5246
*May 20 19:52:23.223: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*May 20 19:51:24.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.100.10 peer_port: 5246
*May 20 19:51:24.818: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.100.10 peer_port: 5246
*May 20 19:51:24.819: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.100.10
*May 20 19:51:29.819: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.100.10

 

Can anyone tell me, is there any issue between the AP & WLC IOS compatibility or what else could be reason for this.

 

 

           

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Blue

Can't be firmware

Can't be firmware compatibility.  Can you post the following command output: 

 

1.  WLC:  sh sysinfo; 

2.  AP:  sh version; and

3.  AP:  sh ip interface brief

 

Your logs is showing the AP is getting the correct time and date.  The only culprit left is the AP has a different regulatory domain against the country settings on the WLC.

3 REPLIES
Hall of Fame Super Blue

Can't be firmware

Can't be firmware compatibility.  Can you post the following command output: 

 

1.  WLC:  sh sysinfo; 

2.  AP:  sh version; and

3.  AP:  sh ip interface brief

 

Your logs is showing the AP is getting the correct time and date.  The only culprit left is the AP has a different regulatory domain against the country settings on the WLC.

Community Member

Hi Thanks for everyone's

Hi Thanks for everyone's comments,

                    I found solution,  I  i was extracting only one file from the tar  image and supporting files were not extracted to flash

Now I did " “archive tar /xtract  tftp://<TFTP server IP>/<ImageName>.tar flash: “ and extracted complete tar in to the flash and changed boot priority. Now it is joining to controller

 

 Thank you

VIP Purple

Hi,Please provide the info

Hi,

Please provide the info asked by LEO then only we can find out the root cause of issue.

sh version from AP

sh sysinfo from WLC.

 

Regards

173
Views
0
Helpful
3
Replies
CreatePlease to create content