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

AIR CAP 3501I Cisco access point (AP) unable to join Cisco Wireless Lan controller (WLC)

 

 

Introduction

 

Scenario

 

New LAP (AIR-CAP3501I ) is installed through wireless lan controller (AIR-WLC2112-K9) with software version 7.0.

The Access point joins the Controller for 2-3 seconds and then disconnects again.

 

Network Topology

 

The ISP ADSL modem , WLC and LAP are connected to a unmanaged POE switch. The LAP gets its power through the POE switch. When it connect the LAP and the WLC to the switch along with the ADSL modem, the LAPs are getting the ip address from the ADSL modem, however they are not joining the WLC for further process.

 

ADSL Modem ip address: 192.168.1.254

Management ip address on the LAP: 192.168.1.1 ( Assigned to port 1, untagged Vlan).

Ap Manager ip address: 192.168.1.2 ( Assigned to the same port i.e port1, Untagged Vlan).

The LAP is getting an IP address from the ADSL modem in the range of the DHCP scope.

 

The Management interface and the AP manager interface are assigned to the same port 1 with unassigned Vlan as mention above.

 

Condition

Not able to ping the AP manager ip (192.168.1.2) from the LAP. External ADSL modem is used as DHCP server for the wireless clients and the LAP.

 

 

Logs from the LAP

 

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (192.168.1.254)
*Sep 25 00:15:52.996: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Sep 25 00:15:53.996: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
*Sep  25 00:16:11.002: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Sep 25 22:11:22.965: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Sep 25 22:11:22.965: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Sep 25 22:11:29.027:  status of voice_diag_test from WLC is false
*Sep 25 22:17:22.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Sep 25 22:17:22.767: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246
*Sep 25 22:17:22.767: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2
*Sep 25 22:17:22.767: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Sep 25 22:17:22.921: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Sep 25 22:17:22.921: %DTLS-5-ALERT: Received WARNING : Close notify alert from  192.168.1.2
*Sep 25 22:17:22.924: %DTLS-5-PEER_DISCONNECT: Peer 192.168.1.2 has closed connection.
*Sep 25 22:17:22.924: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.2:5246
*Sep 25 22:17:22.972: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Sep 25 22:17:22.972: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

 

 

Solution

In such scenarios LAP logs are not very helpful. WLC logs are used to find out the root cause e.g. "Show Tech" or "Debug capwap event"

.

 

"debug capwap event" from the WLC

 

*spamReceiveTask: Sep 26 19:44:59.196: e8:04:62:0a:3f:10 Join Version: = 117465600

*spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 Join resp: CAPWAP Maximum Msg element len = 92

*spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 Join Response sent to 192.168.1.156:45510

*spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 CAPWAP State: Join

*spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 capwap_ac_platform.c:1216 - Operation State 0 ===> 4

apfReceiveTask: Sep 26 19:44:59.198: e8:04:62:0a:3f:10 Register LWAPP event for AP e8:04:62:0a:3f:10 slot 0
*spamReceiveTask: Sep 26 19:44:59.341: e8:04:62:0a:d1:20 DTLS connection not found, creating new connection for 192:168:1:158 (45644) 192:168:1:2 (5246)

*spamReceiveTask: Sep 26 19:45:00.119: e8:04:62:0a:d1:20 DTLS Session established server (192.168.1.2:5246), client (192.168.1.158:45644)

spamReceiveTask: Sep 26 19:45:00.119: e8:04:62:0a:d1:20 Starting wait join timer for AP: 192.168.1.158:45644

*spamReceiveTask: Sep 26 19:45:00.121: e8:04:62:0a:d1:20 Join Request from 192.168.1.158:45644

*spamReceiveTask: Sep 26 19:45:00.123: e8:04:62:0a:d1:20 Join Version: = 117465600

*spamReceiveTask: Sep 26 19:45:00.123: e8:04:62:0a:d1:20 Join resp: CAPWAP Maximum Msg element len = 92

*spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 Join Response sent to 192.168.1.158:45644

*spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 CAPWAP State: Join

*spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 capwap_ac_platform.c:1216 - Operation State 0 ===> 4

*apfReceiveTask: Sep 26 19:45:00.125: e8:04:62:0a:d1:20 Register LWAPP event for AP e8:04:62:0a:d1:20 slot 0
*spamReceiveTask: Sep 26 19:45:00.273: e8:04:62:0a:d1:20 Configuration Status from 192.168.1.158:45644

*spamReceiveTask: Sep 26 19:45:00.273: e8:04:62:0a:d1:20 CAPWAP State: Configure

*spamReceiveTask: Sep 26 19:45:00.273: Invalid channel 1 spacified for the AP APf866.f2ab.24b6, slotId = 0

*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Updating IP info for AP e8:04:62:0a:d1:20 -- static 0, 192.168.1.158/255.255.255.0, gtw 192.168.1.254

*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Updating IP 192.168.1.158 ===> 192.168.1.158 for AP e8:04:62:0a:d1:20
*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Setting MTU to 1485
*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Finding DTLS connection to delete for AP (192:168:1:158/45644)
*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Disconnecting DTLS Capwap-Ctrl session 0xa06d6a4 for AP (192:168:1:158/45644)

*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 CAPWAP State: Dtls tear down

*spamReceiveTask: Sep 26 19:45:00.277: spamProcessGlobalPathMtuUpdate: Changing Global LRAD MTU to 576

*spamReceiveTask: Sep 26 19:45:00.277: e8:04:62:0a:d1:20 DTLS connection closed event receivedserver (192:168:1:2/5246) client 192:168:1:158/45644).

 

 

"Show tech" output logs

 

1#

 

interface address ap-manager 192.168.1.2 255.255.255.0 192.168.1.254
interface address management 192.168.1.1 255.255.255.0 192.168.1.254
interface address virtual 1.1.1.1
interface dhcp ap-manager primary 192.168.1.254  
interface dhcp management primary 192.168.1.254  
interface port ap-manager 1
interface port management 1

 

2#

 

*spamReceiveTask: Sep 26 21:14:37.013: %CAPWAP-3-POST_DECODE_ERR: capwap_ac_sm.c:4452 Post decode processing failed for Config status from AP e8:04:62:0a:d1:20
*spamReceiveTask: Sep 26 21:14:37.011: %LWAPP-3-RD_ERR4: capwap_ac_sm.c:2431 Invalid regulatory domain 802.11bg:-A     802.11a:-A for AP e8:04:62:0a:d1:20
*spamReceiveTask: Sep 26 21:14:37.011: %LOG-3-Q_IND: spam_lrad.c:9223 Invalid country code () for AP e8:04:62:0a:d1:20
*spamReceiveTask: Sep 26 21:14:37.010: %LWAPP-3-RD_ERR7: spam_lrad.c:9223 Invalid country code () for AP e8:04:62:0a:d1:20
*apfReceiveTask: Sep 26 21:14:36.861: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*spamReceiveTask: Sep 26 21:14:26.047: %CAPWAP-3-POST_DECODE_ERR: capwap_ac_sm.c:4452 Post decode processing failed for Config status from AP e8:04:62:0a:d1:20
*spamReceiveTask: Sep 26 21:14:26.044: %LWAPP-3-RD_ERR4: capwap_ac_sm.c:2431 Invalid regulatory domain 802.11bg:-A     802.11a:-A for AP e8:04:62:0a:d1:20
*spamReceiveTask: Sep 26 21:14:26.044: %LOG-3-Q_IND: spam_lrad.c:9223 Invalid country code () for AP e8:04:62:0a:d1:20
*spamReceiveTask: Sep 26 21:14:26.044: %LWAPP-3-RD_ERR7: spam_lrad.c:9223 Invalid country code () for AP e8:04:62:0a:d1:20
*apfReceiveTask: Sep 26 21:14:25.896: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*spamReceiveTask: Sep 26 21:14:15.078: %CAPWAP-3-POST_DECODE_ERR: capwap_ac_sm.c:4452 Post decode processing failed for Config status from AP e8:04:62:0a:d1:20

 

 

From the message log, we can clearly see that "Invalid regulatory domain 802.11bg:-A     802.11a:-A for AP e8:04:62:0a:d1:20 and Invalid country code". So correction of WLC's country code settings to be the same as AP under (wireless-->country).

 

 

Using the GUI to Configure Country Codes on WLC

 

To configure country codes using the controller GUI, follow these steps:

 

Step 1     Follow these steps to disable the 802.11a and 802.11b/g networks as follows:-

 

  • Choose Wireless> 802.11a/n > Network.
  • Unselect the 802.11a Network Status check box.
  • Click Apply to commit your changes.
  • Choose Wireless > 802.11b/g/n > Network.
  • Unselect the 802.11b/g Network Status check box.
  • Click Apply to commit your changes.

 

Step 2     Choose Wireless > Country to open the Country page

 

 

2.jpg

 

 

Step 3     Select the check box for each country where your access points are installed. If you selected more than one check box, a message appears indicating that RRM channels and power levels are limited to common channels and power levels.

Step 4     Click OK to continue or Cancel to cancel the operation.

Step 5     Click Apply to commit your changes.

 

If you selected multiple country codes in Step 3, each access point is assigned to a country.

 

Step 6     See the default country chosen for each access point and choose a different country if necessary as follows:

 

Note:- If you remove a country code from the configuration, any access points currently assigned to the deleted country reboot and when they rejoin the controller, they get re-assigned to one of the remaining countries if possible.

 

A.     Perform one of the following:-

–Leave the 802.11a and 802.11b/g networks disabled.

–Reenable the 802.11a and 802.11b/g networks and then disable only the access points for which you are configuring a country code. To disable an access point, choose Wireless > Access Points > All APs, click the link of the desired access point, choose Disable from the Status drop-down list, and click Apply.

 

B.     Choose Wireless > Access Points > All APs to open the All APs page.

C.     Click the link for the desired access point.

D.     Choose the Advanced tab to open the All APs > Details for (Advanced) page.

 

The default country for this access point appears in the Country Code drop-down list.

 

3.jpg

 

 

e.     If the access point is installed in a country other than the one shown, choose the correct country from the drop-down list. The box containsonly those country codes that are compatible with the regulatory domain of at least one of the access point's radios.

f.     Click Apply to commit your changes.

g.     Repeat these steps to assign all access points joined to the controller to a specific country.

h.     Re-enable any access points that you disabled in a..

 

Step 7     Re-enable the 802.11a and 802.11b/g networks if you did not enable them in Step 6.

Step 8     Click Save Configuration to save your settings.

 

Using the CLI to Configure Country Codes

 

 

This document was generated from the following discussion: AIR-CAP3501I access point not joining the Cisco 2100 Wireless Lan controller.

Version history
Revision #:
2 of 2
Last update:
‎08-29-2017 07:10 AM
Updated by:
 
Labels (1)
Contributors