Go Back   TechArena Community > Technology > Networking & Security
Become a Member!
Forgot your username/password?
Tags Active Topics RSS Search Mark Forums Read

Reply
 
Thread Tools Search this Thread
  #1  
Old 31-12-2011
Member
 
Join Date: Nov 2011
Posts: 61
Why does AIR-CAP3501I Cisco Access Point not able to connect with Cisco Wireless LAN controller?

can you tell me why I am not able to access AIR-CAP3501I Cisco Access Point? In simple terms the Access point is not able to connect with Cisco Wireless LAN controller? any help on the above mentioned issue will be highly appreciated. Thanks a lot in advance.
Reply With Quote
  #2  
Old 31-12-2011
Member
 
Join Date: May 2011
Posts: 424
Re: Why does AIR-CAP3501I Cisco Access Point not able to connect with Cisco Wireless LAN controller?

After going through the entire issue I wanted to tell you that ISP ADSL modem , WLC and LAP are connected with POE switch. LAP is getting power through the POE switch. As it is connected with LAP the WLC to the switching with ADSL modem and the LAP are supposed to getting the IP address from ADSL modem. Also they are not able to join with the WLC for the further process.
Reply With Quote
  #3  
Old 31-12-2011
Member
 
Join Date: May 2011
Posts: 442
Re: Why does AIR-CAP3501I Cisco Access Point not able to connect with Cisco Wireless LAN controller?

Do you have given look on the log file of WLC? I recommend that you should provide the same. also you can also use the debug capwap event and debug mac addr ap-mac from the WLC so that you can figure what went wrong?
Reply With Quote
  #4  
Old 31-12-2011
Member
 
Join Date: Nov 2011
Posts: 61
Re: Why does AIR-CAP3501I Cisco Access Point not able to connect with Cisco Wireless LAN controller?

Following are the log from LAP
Quote:
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
Also below mentioned is debug capwap from WLC.
Quote:
*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).
Reply With Quote
  #5  
Old 31-12-2011
Member
 
Join Date: May 2011
Posts: 231
Re: Why does AIR-CAP3501I Cisco Access Point not able to connect with Cisco Wireless LAN controller?

The above mentioned issue might be happening because mismatched regulatory domain so you have to check the country setting into WLC and Access Point.
Reply With Quote
  #6  
Old 31-12-2011
Member
 
Join Date: Jun 2011
Posts: 451
Re: Why does AIR-CAP3501I Cisco Access Point not able to connect with Cisco Wireless LAN controller?

Well you can use the following steps to configure the Country Codes.
  • You have to use the below mentioned steps to disable 802.11a and 802.11b/g networks
  • Select 802.11a/n network.
  • now uncheck 802.11a Network status checkbox and after that click on the Apply settings.
  • Again select Wireless and go for 802.11b/g/n network and uncheck 802.11b/g/n Network Status checkbox. After that click on the Apply button.

  • Now again select Wireless and go for Country and launch the Country pag.
  • After that you have to checkbox for the each country where the access point has been installed. if you have selected the more the one countries then you will get an error message which are saying that RRM channels and power levels are seems to be limited to the common channels and the power levels.
  • Now you have to click on OK button to continue or if you wanted to cancel the operation.
  • After that click on the Apply button.
  • You have to give a look on default country selected for the every single access point and also you can select the different option.
  • The 802.11a and 802.11b/g networks should be disabled.
  • Enable the 802.11a and 802.11b/g networks and disable the access points for the country which you are supposed to configure.
  • To disable the access point you have to perform following steps.
  • You should go for Wireless then go for Access Points and select All APs.
  • Now select the desired AP and disable the status from the drop-down list and click on the Apply button.
  • Once you have done you have to open all the APs into the new page and select Advanced tab to open all the AP and click on Details.
  • If the desire access point is installed into the country than that of which has been displayed the select the correct country from the drop down list.
  • After that click on the Apply button to changes which you have done. Re do the same steps to assign AP to controller to desire country.
  • Enable all the disable Access point and also enable the 802.11a and 802.11b/g networks.
  • Finally click on the Save Configuration so that you can save the settings which you have done.
Reply With Quote
Reply

  TechArena Community > Technology > Networking & Security
Tags: , , ,



Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "Why does AIR-CAP3501I Cisco Access Point not able to connect with Cisco Wireless LAN controller?"
Thread Thread Starter Forum Replies Last Post
How to set Cisco Linksys WRT160N V2 as access point on LAN |Gyani| Networking & Security 7 25-03-2012 05:46 PM
How to set Cisco Linksys E420 wireless router as Access Point mode? Chheda Networking & Security 4 30-01-2012 11:50 PM
Can I do conversion of Cisco AIR-LAP1262N-x-K9 router to Access Point? Chheda Networking & Security 1 31-12-2011 03:29 PM
Cisco Aironet 1140 Series Access Point with Cisco M-Drive technology Trog Reviews 0 19-01-2009 10:41 AM
How do you use Cisco Wireless Router for Wireless Access Point? GANGSTA Small Business Server 2 16-07-2008 12:54 AM


All times are GMT +5.5. The time now is 11:36 AM.