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

LAP 1262 N is not joining WISM Contrl and not getting IP from DHCP

Hello friends

cisco LAPs 1262 N are not joining the wism's controller and also not getting ip addresses from external DHCP server

i have controller with image 7.1.116 and laps 1262N

External DHCP server on win sever 2003

external DNS server on win server 2003

i have configred all vlan dhcp pools there in dhcp server

also configure option43 VCI in there

also i configure DNS discover for Laps in DNS server

my controllers and laps are in different subnets

let's say controllers are in 10.135.64.0

and laps are in 10.135.65.0

but at joining proccess of aps i am getting this error

*Mar  1 00:17:04.991: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:17:14.991: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:17:24.991: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:17:34.991: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:17:44.992: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

Not in Bound state.

*Mar  1 00:17:54.992: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:17:54.992: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

*Mar  1 00:17:56.533: %CDP_PD-2-POWER_LOW: All radios disabled - NEGOTIATED WS-C3750X-24P (c89c.1d80.8812)

APe05f.b95f.980a>

APe05f.b95f.980a>

*Mar  1 00:18:04.995: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:18:14.996: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:18:24.996: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:18:34.996: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

Not in Bound state.

*Mar  1 00:18:44.996: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:18:44.996: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

*Mar  1 00:18:54.997: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:19:04.997: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:19:14.997: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:19:24.997: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

Not in Bound state.

*Mar  1 00:19:34.998: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar  1 00:19:34.998: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

*Mar  1 00:19:44.998: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

how to get rid of this error

any seggustion

please

thanks in advance

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Silver

Re: LAP 1262 N is not joining WISM Contrl and not getting IP fro

Make sure the WLC date and time are correct

-Scott
*** Please rate helpful posts ***
7 REPLIES
Hall of Fame Super Silver

Re: LAP 1262 N is not joining WISM Contrl and not getting IP fro

Do you have an ip helper on the L3 interface. Plug a pc to port the ap is on and verify that machine gets an ip.

Thanks,

Scott Fella

Sent from my iPhone

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

LAP 1262 N is not joining WISM Contrl and not getting IP from DH

Can you also post the DHCP config?

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

LAP 1262 N is not joining WISM Contrl and not getting IP from DH

thanks for your reply

this issue has been solved it got ipaddress actually

but now i am facing another ceretificate error

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (xx.xx.xx.xx) (xx.xx.xx.xx.)

*Mar  1 00:17:05.997: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.135.64.225 obtained through DHCP

*Mar  1 00:17:05.997: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.135.64.226 obtained through DHCP

*Mar  1 00:17:05.997: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.135.64.227 obtained through DHCP

*Mar  1 00:17:05.997: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.135.64.228 obtained through DHCP

*Mar  1 00:17:05.997: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.135.64.229 obtained through DHCP

*Mar  1 00:17:05.997: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.135.64.230 obtained through DHCP

*Mar  1 00:17:05.997: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.135.64.231 obtained through DHCP

*Mar  1 00:17:05.997: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.135.64.232 obtained through DHCP

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

*Mar  1 00:17:16.007: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jul  1 04:50:47.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.135.64.235 peer_port: 5246

*Jul  1 04:50:47.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Jul  1 04:50:47.390: %DTLS-5-ALERT: Received FATAL : Certificate unknown alert from 10.135.64.235

*Jul  1 04:50:47.390: %CAPWAP-3-ERRORLOG: Bad certificate alert received from peer.

*Jul  1 04:50:47.390: %DTLS-5-PEER_DISCONNECT: Peer 10.135.64.235 has closed connection.

*Jul  1 04:50:47.390: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.135.64.235:5246

*Jul  1 04:50:47.390: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 3 combination.

*Jul  1 04:51:27.595: %CDP_PD-2-POWER_LOW: All radios disabled - NEGOTIATED WS-C3750X-24P (c89c.1d80.8812)

APe05f.b95f.980a>

*Jul  1 04:51:52.003: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jul  1 05:19:17.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.135.64.236 peer_port: 5246

*Jul  1 05:19:17.386: %DTLS-5-ALERT: Received FATAL : Certificate unknown alert from 10.135.64.236

*Jul  1 05:19:17.386: %CAPWAP-3-ERRORLOG: Bad certificate alert received from peer.

*Jul  1 05:19:17.386: %DTLS-5-PEER_DISCONNECT: Peer 10.135.64.236 has closed connection.

*Jul  1 05:19:17.386: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.135.64.236:5246

*Jul  1 05:19:17.390: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 3 combination.

*Jul  1 05:20:22.003: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Oct 14 11:21:47.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.135.64.233 peer_port: 5246

*Oct 14 11:21:47.075: %PKI-3-CERTIFICATE_INVALID_EXPIRED: Certificate chain validation has failed.  The certificate (SN: 14D37528000000113426) has expired.    Validity period ended on 02:36:58 UTC Nov 26 2020

*Oct 14 11:21:47.075: %LWAPP-3-CLIENTERRORLOG: Peer certificate verification failed

*Oct 14 11:21:47.075: %CAPWAP-3-ERRORLOG: Certificate verification failed!

*Oct 14 11:21:47.075: DTLS_CLIENT_ERROR: ../capwap/capwap_wtp_dtls.c:333 Certificate verified failed!

*Oct 14 11:21:47.075: %DTLS-4-BAD_CERT: Certificate verification failed. Peer IP: 10.135.64.233

*Oct 14 11:21:47.075: %DTLS-5-SEND_ALERT: Send FATAL : Bad certificate Alert to 10.135.64.233:5246

*Oct 14 11:21:47.075: %DTLS-3-BAD_RECORD: Erroneous record received from 10.135.64.233: Malformed Certificate

*Oct 14 11:21:47.075: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.135.64.233:5246

*Oct 14 11:22:52.003: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jan 27 00:18:42.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.135.64.234 peer_port: 5246

*Jan 27 00:18:42.390: %DTLS-5-ALERT: Received FATAL : Certificate unknown alert from 10.135.64.234

*Jan 27 00:18:42.390: %CAPWAP-3-ERRORLOG: Bad certificate alert received from peer.

*Jan 27 00:18:42.390: %DTLS-5-PEER_DISCONNECT: Peer 10.135.64.234 has closed connection.

*Jan 27 00:18:42.390: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.135.64.234:5246

*Jan 27 00:18:42.390: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 3 combination.

any seggustion please

Hall of Fame Super Silver

Re: LAP 1262 N is not joining WISM Contrl and not getting IP fro

Make sure the WLC date and time are correct

-Scott
*** Please rate helpful posts ***
New Member

Re: LAP 1262 N is not joining WISM Contrl and not getting IP fro

if i have not configured ntp in my distribution switch where i have all vlan data base and also wism moduls

so what do you say if i configure in controller ntp server is wism service vlan's ip address or my distribution mgmt ip or same controller mgmt vlan's gateway ip address it will not sync the time configuration to controller?

and are you it would be the just date and time are not correct when i configure manually in controller in Command than

set time and date here the access point will join the controllers?

New Member

Re: LAP 1262 N is not joining WISM Contrl and not getting IP fro

thank you sooooooo much fella

setting the time on wlc did helped and aps joined the wlc

thank you

Hall of Fame Super Silver

Re: LAP 1262 N is not joining WISM Contrl and not getting IP fro

No problem.

Thanks,

Scott Fella

Sent from my iPhone

-Scott
*** Please rate helpful posts ***
1183
Views
0
Helpful
7
Replies
CreatePlease to create content