AIR-CAP3501I access point not joining the Cisco 2100 Wireless Lan controller.

Hello All,
I am installing a new LAP (AIR-CAP3501I ) through the wireless lan controller (AIR-WLC2112-K9) with software version 7.0. I have an external ADSL modem which will act as the DHCP server for the wireless clients and the LAP.
Please find my network setup as below:
The ISP ADSL modem , WLC and LAP are connected to a unmanaged POE switch. The LAP gets its power through the POE switch. When i 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.1 ( 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.
I will paste the logs very soon.
Please let me know if i am doing anything wrong oe what will be the issue.
Thanks in advance,
Mohammed Ameen

Hello All,
Please find the logs for "debug capwap event" from the WLC below:
*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).
The Acess point joins the Controller for 2-3 seconds and then unjoins again. I am not sure what i am doing wrong here. The access points are getting the IPs from the ADSL modem through the switch, then it talks to the WLC, however it does not join the controller for further process.
Note:
The Managemnet interface and the AP manager interface are assigned to the same port 1 with unassigned Vlan as mention above.

Similar Messages

How to replace the certificate of Cisco 2106 wireless LAN controller for CAPWAP ?

I have interested in CAPWAP feature and I download the open capwap project to make Access Controller (AC) and Wireless Terminal Point (WTP). I had built the AC which used PC and WTP which used Atheros AP. The CAPWAP feature work well when I enabled the CAPWAP that used my own AC and WTP. When I got the Cisco 2106 wireless LAN controller (Cisco WLC), I configured the Cisco WLC to instead my own AC but I got the authorize fail in Cisco WLC side. It seem the Cisco WLC could not recognize the CAPWAP message which sent form my own WTP. I think this issue just need to synchronize the certificate between Cisco WLC and WTP.So I need to replace the Cisco WLC's certificate manually. Does anyone know how to replace the certificate manually with Cisco WLC ?
Best Regards,
Alan

Unfortunately this Support Community is for Cisco Small Business & Small Business Pro product offerings. The WLC2106 is a traditional Cisco product. You can find this type of support on the Cisco NetPro Forum for all traditional Cisco products.
Best Regards,
Glenn

How do i ensure the new access point is joined the controller or not

How do i ensure the new access point is joined the controller or not

To Verifying that Access Points Join the Controller or not there are two ways as below.
Please go through the step by step to find the APs joined state
When replacing a controller, you need to make sure that access points join the new controller.
Using the GUI to Verify that Access Points Join the Controller
Follow these steps to ensure that access points join the new controller.
Step 1 Follow these steps to configure the new controller as a master controller.
a. Click Controller > Advanced > Master Controller Mode to open the Master Controller Configuration page.
b. Check the Master Controller Mode check box.
c. Click Apply to commit your changes.
d. Click Save Configuration to save your changes.
Step 2 (Optional) Flush the ARP and MAC address tables within the network infrastructure. Ask your network administrator for more information about this step.
Step 3 Restart the access points.
Step 4 Once all the access points have joined the new controller, configure the controller not to be a master controller by unchecking the Master Controller Mode check box on the Master Controller Configuration page.
Using the CLI to Verify that Access Points Join the Controller
Follow these steps to ensure that access points join the new controller.
Step 1 To configure the new controller as a master controller, enter this command:
config network master-base enable
Step 2 (Optional) Flush the ARP and MAC address tables within the network infrastructure. Ask your network administrator for more information about this step.
Step 3 Restart the access points.

Software Version Upgrade for Cisco 4402 Wireless Lan Controller

Hi,
We have Cisco 4402 Wireless Lan Controller with Software Version 3.2.171.6 and we want to upgrade it to latest version.
So can anyone please let me know the latest version to upgrade the WLC?
Also since WLC is running on very lower version is it possible to upgrade to the latest version directly or we have to move it step by step to upgrade this to latest version?
Thanks

Take a look at the compatibility matrix below:
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
7.0.235 is the latest that you can go to:
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn7_0_235_0.html
The release notes outline the upgrade process.
"Upgrade to 4.0.206.0 or later 4.0 release, then upgrade to 4.2.176.0, before upgrading to 7.0.235.0."

Access Points not joining WLC

Hello All,
I am trying to deploy several AIR-CAP3502E-E-K9 access points from a cisco 5508 wire lan contoller running ver 7 code. However iam having difficulty regiserting the access points with the WLC. The wlc is connect to a 3650 switch, and each access point is connected to a 2960 switch.
Problem Solved. A bad update was not allowing the access points to get their correct firmware.

You need to provide what Leo stated, that would help a lot. Anyways you can't telnet or ssh into a capwap AP if it has not joined the WLC. So that being said, provide the info Leo requested and then console into the ap and provide use with output from the console. Make sure you reboot the AP and then start capturing the output for around 5 minutes.
Sent from Cisco Technical Support iPad App

2100 wireless LAN controller intermittant DHCP issue does not respond to clients

Hi everyone,
I have been struggling with a difficult problem for some time now:
The cisco 2100 wlan controller I have is configured with a dhcp scope in the same ip address range as its WLAN. The configuration works and on a good day I have up to 200 clients connecting with out issue. In the web interface they display as associated and authenticated
On a bad day I find I will begin seeing about 50-80% of all new devices that attempt to join the WLAN show up as associated but not authenticated. These clients end up self assigning themselves a 169.254.0.0/16 (APIPA) address
When my controller / WLAN enters into this state: if clients leave the WLAN they typically fail to get back on and successfully authenticate. By the end of a day around 80-90% of all devices are essentially without Internet access due to this issue.
Rebooting the controller and or APs typically makes no difference or makes things worse – although sometimes it appears to resolve the issue. The same holds for disabling the entire wlan for about 10 minutes and then re enabling it.
Im using 1130 cisco aironet APs with the controller. I have checked extensively for interference and congestion – I think I have congestion – some APs typically host 40 to 90 devices. However as mentioned on a good day the wlan will host 200 devices all day without any issue and some APs will host 50 to 70 devices without major issue.
I can provide more specifics if anyone should need – eg firmware, IP addresses, exact model numbers etc.
Please let me know if anyone has seen something like this before ?
I believe the 2100 is rated to handle up to 350 devices and its recommended not to load a 1130 AP with more than 25 devices ??
Regards
Matthew

Hi Amijad, Hi George:
Thank you both for your time in considering my situation.
I will think about implementing an independant DHCP server; im really wondering if the equipment is just overloaded
- What software versoin the WLC uses?
Product Version.................................. 6.0.199.4
RTOS Version..................................... 6.0.199.4
Bootloader Version............................... 4.0.191.0
Emergency Image Version.......................... 6.0.199.4
PID: AIR-WLC2106-K9, VID: V05
- What ports of the WLC are connected to the neighbor swtich? one or more?
2 ports connect to the neighbor switch on separate vlans
- port 1 is vlan 0 and hosts the management and ap-management IPs for the wlan controller
- port 2 is vlan 1 and hosts the wlan
- the controller has one dhcp scope defined on port 2 for the WLAN
- What is the security of your WLAN?
WPA+WPA2
AES
PSK
- Do you have "DHCP required" enabled on the WLAN?
yes DHCP required is enabled in the WLAN
please let me know if you have any additional advice.
regards
Matthew

Linksys access point is better than cisco's wireless router !?

I bought a Linksys WAP54G yesterday to
see whether my 871w is faulty. (Constant signal drops).
While I was testing, I noticed that WAP54G has a better signal strength than the 871w. What's interesting is, Linksys WAP54G only has a max power output of 15.5dbm, while the Cisco 871w has the max output of 17 dbm.
I used the netstumbler to measure the signal strength. Linksys WAP54G can constantly stay at -60dbm, while the Cisco 871w (with the max power configured) goes up and down (between -70 and -60 dbm).
They are both configured to use the same channel. I find this strange as to why a higher power output has a much lower efficiency compare to a lower power output.
Any ideas?

Do you see this happening with all the 870 ISRs? I am suspecting a hardware issue. Can you check with a different ISR and see if you are observing the same behaviour ?

Issues after changing the AP Name on Wireless LAN Controller

I recently changed the AP Name of all the Wireless Access Points in my branch office (which are all associated to the branch office Wireless LAN Controller(s)). After that I noticed that all branch office employees are unable to connect to the employee SSID. The employee SSID uses web authentication and employees are authenticated using Head Office AD via Cisco ACS, both located at the Head Office.
There are other SSID's on the WLC which all work fine, but only employee SSID which uses AD authentication does not work. AD authenticaion is working fine because employee's in HO are successfully able to connect to the employee SSID at HO.
The branch office is connected to the HO via a tunnel link. We noticed that if we restart both the ASA at either ends of the tunnel. The employee SSID starts working again but only temporarily for a day or so... what could be the issue? Can renaming the AP's cause issues? How can I fix this problem?
Thanks in advance

Thanks Elliott,
I did the debug like you said and I am getting the following debug messages:
*apfMsConnTask_0: Jun 20 08:18:14.580: Deleting the client immediatly since WLAN is changed
and also
*apfReceiveTask: Jun 20 05:25:11.857: 00:1f:3c:86:af:15 Orphan Packet from 192.168.52.34
The logging on the WLC shows
*apfReceiveTask: Jun 18 17:56:41.788: %MM-1-ANCHOR_UNAVAILABLE: mm_mobile.c:2155
All export anchors are down. Cannot anchor the client.00:c0:a8:f3:cd:ae
The DHCP pool for the employee users are configured on a guest WLC which sits behind an ASA

Cisco Wireless Control System need wireless Lan Controller ?

Cisco Wireless Control System need wireless Lan Controller , for Rogue detection

Hi Joao,
The WCS is used in conjuntion with the WLC (Wireless Lan Controller) for Rogue Detection. It is not a must for this function but more of an add-on :)
The Cisco WCS is an optional network component that works in conjunction with Cisco Aironet Lightweight Access Points, Cisco wireless LAN controllers and the Cisco Wireless Location Appliance.
From this doc;
http://www.cisco.com/en/US/products/ps6305/index.html
Overview of WCS
The Cisco Wireless Control System (WCS) is a Cisco Unified Wireless Network Solution management tool that adds to the capabilities of the web user interface and command line interface (CLI), moving from individual controllers to a network of controllers. WCS includes the same configuration, performance monitoring, security, fault management, and accounting options used at the controller level and adds a graphical view of multiple controllers and managed access points.
WCS runs on Windows 2003 and Red Hat Enterprise Linux ES 4.0 and AS 4.0 servers. On both Windows and Linux, WCS can run as a normal application or as a service, which runs continuously and resumes running after a reboot.
The WCS user interface enables operators to control all permitted Cisco Unified Wireless Network Solution configuration, monitoring, and control functions through Internet Explorer 6.0 or later. Operator permissions are defined by the administrator using the WCS user interface Administration menu, which enables the administrator to manage user accounts and schedule periodic maintenance tasks.
WCS simplifies controller configuration and monitoring while reducing data entry errors with the Cisco Unified Wireless Network Controller autodiscovery algorithm. WCS uses the industry-standard SNMP protocol to communicate with the controllers.
From this good doc;
http://www.cisco.com/en/US/products/ps6305/products_configuration_guide_chapter09186a00806b7270.html#wp1131195
Detect and Locate Rogue Access Points
From this WCS doc;
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806f070a.shtml#new5
Rogue Detection under Unified Wireless Networks
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_white_paper09186a0080722d8c.shtml
Hope this helps!
Rob

Does disabling all access points turn off the WiFi radio on Cisco SA520W

As per the title - does disabling all access points turn off the WiFi radio on Cisco SA520W? Thanks!

Hi Denny,
Yes, if you disable all available Access Points configured on your SA520W, then your radio should be off.
Best regards,
Julio

AIR-LAP1242AG-K9 could not join a 2106 WLC: i ma getting ready for a deployment, how can i resolve this?

Hi,
I setup a mini wireless LAN network lab with a not for resale 2106 wireless lan controller and a sales air-lap1242ag access point. I do not have a DHCP and DNS in my lab environment. I have configured the WLC with the basic configuration using the CLI wizard, i also configured the WLC as a DHCP server for clients that will be connecting to the APs associated to the controller.
I powered up the AP and connect the ethernet port directly to the controller, the controller issued an IP address to the AP, the AP downloaded a new operating system from the controller but failed to join the controller.
I check both debug message on the controller console and the trap messages on the controller's GUI and it say the AP could not download a configuration from the controller and it is beacuse of invalid license. Below is the trap message:
Configuration Phase Statistics
Requests Received
Responses Sent
Unsuccessful Request Processed
Reason For Last Unsuccessful Attempt
Last Successful Attempt Time
Last Unsuccessful Attempt Time
Last Error Summary
Last AP Message Decryption Failure
Last AP Connection Failure
Last Error Occurred
Last Error Occurred Reason
Last Join Error Timestamp
Also, I tried to log into the GUI of the AP using the both the username and password ''Cisco'' but I cannot get into the device. I can only get in through the CLI. In the CLI, almost all the commands I enter gives an error the it is disabled. I don't know what to do any more, I want to know if the access point is faulty or i am not doing the right thing.
PLEASE HELP!!!!!!!!!!!!!!!!!!!

Thank you for the quick response.
The controller is running firmware version:
Software Version 6.0.199.4
Emergency Image Version 6.0.199.4
The AP can ping the Management IP address of the controller successfully via console. I have also entered in the AP the WLC's Management IP address information and it is still the same. Below is the message I'm getting on the console of the AP it self:
*Jul 9 13:06:09.803: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jul 9 13:06:10.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip:
192.168.50.246 peer_port: 5246
*Jul 9 13:06:10.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Jul 9 13:06:11.636: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully
peer_ip: 192.168.50.246 peer_port: 5246
*Jul 9 13:06:11.638: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.50.246
*Jul 9 13:06:11.638: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Jul 9 13:06:11.724: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Jul 9 13:06:11.726: %DTLS-5-ALERT: Received WARNING : Close notify alert from
192.168.50.246
*Jul 9 13:06:11.727: %DTLS-5-PEER_DISCONNECT: Peer 192.168.50.246 has closed conne
ction.
*Jul 9 13:06:11.727: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 1
92.168.50.246:5246
*Jul 9 13:06:11.772: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Jul 9 13:06:11.772: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
I will also like to know if AIR-LAP1242AG is compatible with WLC 2106 controller.
Any help will be greatly appreciated, i really need to resolve this issue in my LAB now so that I don't go to my customer site to fumble.
thanks in advance.

LAP not joining the controller

Gents
I have 1 AP out of ten not joining the controller. I connected the access point to the network and I checked its boot. the access point reaches LWAPP Discovery" and then give me console input. I hard reset the access point and I hard coded an IP address for the AP the AP joins the controller, but when I reset it to assign it to another controller it did not join again.
why the discovery process is not showing the DHCP option 43 configured and DNS for CISCO-LWAPP-CONTROLLER configured on the DNS. All the access point is operating normally except this one. it has many certificate inside, why a hard reset did not work to solve the problem?
Please advise
Thanks,

Does the LAP have a valid IP address?
Can the LAP ping the WLC managment IP address?
Console into the LAP and in enable mode, type the command "lwapp ap controller ".

Is AIR-OPT60-DHCP available on autonomous AIR-SAP2602I access point?

Hello Wireless Experts,
I was able to order AIR-OPT60-DHCP on controller based AP AIR-CAP2602I-E-K9 using CCW, but this option is not available on autonomous AIR-SAP2602I access points.
Is AIR-OPT60-DHCP available on autonomous AIR-SAP2602I access point?
Thanks.
George

That is a feature and only used in lightweight access points. The standalone autonomous access points don't use that. Just follow the configuration guide for your access point to get you started.
Sent from Cisco Technical Support iPhone App

Access point not online on controller

Hi,
I have been trying to get a 1262AP registered to wireless lan controller.
The core switch has three 2 vlans in it, management which is vlan 41 and AP interaction vlan which is vlan 51.
Controller also has both these vlans.
Vlan 41 - 192.168.40.x/23 ( management vlan)
Vlan 61 - 192.168.61.x/24 (AP vlan)
WLC management interface IP is 192.168.40.18
WLC AP interface IP is 192.168.6.241
Now , during the initial steps, the access points are attached to the switchports on vlan41, wherein they get the dhcp ip from the temporary pool created on the controller and get registered.
But, these access points in actual environment needs to be on static ip address. When it's ip is changed to a static IP address from the controller , it fails to register to the controller. the switchport is put on vlan6 as access port , after static ip is assigned to the access point.
The error i receive is ;
%CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1
the core switch we are using in this new setup is a 2960 with a lanbase image. I realised the switch is not routing enabled. it doesn't accept the command "ip routing". Will this be creating a problem for the access points?
From the switch , the controller management and AP vlan IP address can be pinged. similarly, from the controller, AP and management vlan interface ip address of the switch can be pinged.
Please help.

Did you get it to work? The thing you have to understand is how the AP is able to join the WLC and the process the AP goes through to try to join. Here is a document that will help you understand the process and the various ways an AP can join or find the WLC. The easiest almost fool proof way is to place the ap in the same subnet as the management of the WLC. If the AP joins, then the AP will know of the ip of that WLC it joined or any in the mobility group if defined. Take a look at the doc as it explains it better than I can:)
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Could not provision the RemoteApp collection. Error: Could not join the domain. Unable to reach the domain.

Hi
I am trying to set up an Azure RemoteApp Hybrid solution.
I have created RemoteApp net and uploaded a custom image and all that is fine.
When I link my template to my Collection it fails after provisioning for about an hour.
I recive the following message: Could not provision the RemoteApp collection. Error: Could not join the domain. Unable to reach the domain.
The join domin works fine and I have tryed with account with different lvl of access to my AD.
Any suggestion how to solve this?

Hello Eric,
I am landing into the same Problem and i read your guidance on this issue. Let me answer it point by point.
1. Check the VPN state to ensure it is active or connected state:
Sundesh:My Azure RemoteApp Virtual Network after successfull S2S configuration shows as Ready. Is that what you mean by Connected State? Earlier to S2S, it was just under connecting state.
2. Verify your VNET configurations have proper IP address ranges
Sundesh: The VNET address range, the Local address range and DNS has already been verified twice. In fact the same address ranges(with exception to VNET) are working fine on a VENT config on Azure VM instance. Verified.
3. Verify your DNS IP configurations are valid, (often this is the problem)
Sundesh: Yes its done and verified
4. Verify the credentials entered for domain join are valid.
Sundesh: Tested these credentials by joining a regular Azure VM to domain and it works there.
5. Make sure your VPN endpoint that Azure RemoteApp service is connecting to is not blocking traffic.
Sundesh: Can you please let us know the specific port numbers that we need to consider and i can have it checked with the Network team
Thanks
SUndesh

AIR-CAP3501I access point not joining the Cisco 2100 Wireless Lan controller.

Similar Messages

Maybe you are looking for