01-07-2013 10:41 AM - edited 07-03-2021 11:18 PM
I'm getting this error msg with my AP. It sees the IP address of the AP Manager of the WLC 44002, however it times out.
Note: The operating mode for this AP is H-REAP
The WLC is at the DataCenter.
We have APs working at other remote site (MPLS, Network)
The AP (1262) i'm having an issue with is at a remote with regular internet.
I have already configured port fowarding on the Linksys router for port 5246
Please Help!
======
Jan 7 14:28:55.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.99.3 peer_port: 5246
*Jan 7 14:29:25.003: DTLS_CLIENT_ERROR: ../dtls/dtls_connection_db.c:2017 Max retransmission count reached!
*Jan 7 14:29:25.003: %DTLS-3-HANDSHAKE_RETRANSMIT: Max retransmit count for 10.1.99.3 is reached.
*Jan 7 14:29:55.048: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.1.99.3:5246
*Jan 7 14:29:55.102: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Jan 7 14:29:55.102: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Jan 7 14:29:55.162: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jan 7 14:29:55.162: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jan 7 14:29:55.171: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jan 7 14:29:55.180: status of voice_diag_test from WLC is false
*Jan 7 14:29:55.180: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Jan 7 14:29:55.190: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Jan 7 14:29:55.199: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jan 7 14:31:04.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.99.3 peer_port: 5246
*Jan 7 14:31:04.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
VH-SAT-AP1-1262#
*Jan 7 14:31:34.003: DTLS_CLIENT_ERROR: ../dtls/dtls_connection_db.c:2017 Max retransmission count reached!
*Jan 7 14:31:34.003: %DTLS-3-HANDSHAKE_RETRANSMIT: Max retransmit count for 10.1.99.3 is reached.
01-10-2013 10:15 AM
Scott Fella:
Thanks.
Regular Internet, as in Home-Class Internet vs. MPLS Network, as in MPLS T1 Internet service.
01-09-2013 01:38 PM
So here is the question: Using the same AP ( AIR-LAP1262N-N-K9), how come HREAP worked on an MPLS network, but not work on a regular internet?
Ok, let me explain it this way ...
If the said AP freshly came out from a sealed box, the AP will initially join a WLC and download the full controller-based IOS. After the AP downloads the IOS, it will reboot. So far so good. All of this is very standard.
However, the AP with the wrong regulatory domain will search for a WLC to finally JOIN. The WLC should have the correct country code set or the AP will continuously "twiddle it's thumbs and going waiting, waiting, waiting ...".
I don't believe this AP has joined a WLC other than to download the firmware.
This behaviour is exactly what you are seeing. You're not the first and you won't be the last to make this error.
01-10-2013 10:36 AM
leolaohoo:
Thank you..
...... AP will continuously "twiddle it's thumbs and going waiting, waiting, waiting ...".
Sounds awful!
So i took this AP (AIR-LAP1262N-N-K9) back to the HQ office, Primed with the local (private) IP address of the AP Mgmt, it finds and join the WLC wihich located at the COLO. Connection between HQ and COLO is over an MPLS T1 line.
01-10-2013 01:35 PM
So i took this AP (AIR-LAP1262N-N-K9) back to the HQ office, Primed with the local (private) IP address of the AP Mgmt, it finds and join the WLC wihich located at the COLO. Connection between HQ and COLO is over an MPLS T1 line.
Look at the country domain. Someone must've configured another country aside from US which corresponds to the Regulatory Domain equivalent to "-N".
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide