Cisco Wireless :: 1042 LAP With 5508 Series Controller - AP Will Not Associate
Jun 11, 2012
I have a 5508 WLC licensed for 100 APs. I have 1 - 1042 LAP connected for testing. I have DHCP configured for the AP, and it gets an address of 192.168.254.100/24 - the controller's management interface is 192.168.254.99/24. I can see that the AP is getting an IP and I can ping it from the controller. However, I simply do not see the AP associating. I enabled capwap debiugging and watched the events, but I didn't see anything crazy that clued me in. What am I doing wrong?
The controller is v6.0.199.4
Every time I have set these up in the past they have been pretty straight forward. I haven't gotten too deep into the config on the WLC becuase I don't want to cause more issues.
When I connect the access-Point to the network, the AP associate only one time but i go to wireless for see the AP, i can see downloading of IOS, but the ios is 3.0.59, the ap don not nothing. I can not change any parameters.
how to setup the 5508 Series LAN wireless controller. The online documentation are not details. What different between Service Interface IP and Management interface IP. The device IP is using what type service or management interface.
I am at one of our remote offices and I am noticing my laptop, despite excellent signal strength is periodically losing IP connectivity on the wireless network. When it drops, all of my IP connectivity stops (pings fail, RDP sessions "await reconnection", etc...). The lower right corner still shows I'm connected to the hidden WPA2 Enterprise SSID. The only way to reconnect is to select disconnect on it, then click connect again. Immediately everything IP based starts working.
There is a 5508 controller in the headquarters. The site I am at has a 30mbps fiber point to point WAN to the headquarters. This site has 2 x 3300 series LAPs which are very good coverage. H-REAP mode is on so traffic terminates at the local office because it is more efficient than traversing the LAN twice for things like local file and print sharing, dhcp, proper active directory sites and services mapping, etc.
I ordered controller 2504 and will arrive soon. I want to know that after configure the initial setup of 2504 (i.e. AP manager , Management IPs etc) and defining the DHCP for AP. Will the 1042 lightweight AP will register with the controller automatically or i need to manually define the AP (MAC address) on WLC. and also whether the Option 43 and 60 are correctly defined?
Management Interface: 10.10.22.15 AP Manager Int: 10.10.22.16 ip dhcp pool WLAN103 network 10.10.3.0 255.255.255.0 [code]...
I am not able to join 1042 wireless AP with 2106 controller, even i mention that controller ip is 192.168.200.5 it try to join with controller on 192.168.200.6 ip address always. following are the error logs i can see on console.
*Nov 30 19:50:20.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.200.6 peer_port: 5246 *Nov 30 19:50:20.001: %CAPWAP-5-CHANGED: CAPWAP changed state to *Nov 30 19:50:21.435: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.200.6 peer_port: 5246 *Nov 30 19:50:21.436: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.200.6 *Nov 30 19:50:21.436: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
We have other APs that associate w/o issue AIR-LAP1141N-A-K9. However our 1 1310 is having issues.. The Controller log shows:
2012-08-29 21:16:51 local0.error 172.16.10.70 ITCNJ1WC01: *spamApTask0: Aug 28 21:17:15.038: %LWAPP-3-DECRYPT_ERR5: spam_crypto.c:293 Error decrypting packet (using old key) from AP d4:8c:b5:15:3c:04 (session identifier a3ddb9c5) 2012-08-29 21:17:33 local0.error 172.16.10.70 ITCNJ1WC01: *spamApTask0: Aug 28 21:17:17.037: %LWAPP-3-DECRYPT_ERR: spam_lrad.c:3642 The system is unable to decrypt image data message; AP d4:8c:b5:15:3c:04 2012-08-29 21:17:33 local0.error 172.16.10.70 ITCNJ1WC01: *spamApTask0: Aug 28 21:17:17.037: %LWAPP-3-DECRYPT_ERR: spam_crypto.c:735 The system is unable to decrypt LWAPP packet; AP d4:8c:b5:15:3c:04
Is it possible to rename the default webauthentication URL from [URL] to something like [URL]. We are running on 7.0.98.0, is it possible to do http for web authentication and https for Mgmt access if we upgrade the controller software?
We configured our guest wireless with no layer 2 authetication so users can associate with an AP and get an ip adress but they can't go anywhere unless they have a valid username and password(web authentication) - does this affect the performance of an AP since there will be many people associated with each AP, is there any setting in the WLC to de associate a client from an AP if its idle for certain time.
When I connect the APs to a port on our 3550 switch, the AP gets an IP and associates with the 2106 controller. I can ping the AP from a wired PC and associate a wireless client to it. When I connect them to the PoE ports that are on the controller, it gets an IP and associates with the controller but, I cannot ping it from a wired PC or wireless client but, I can associate a wireless client to it.
The AP manager and Management interfaces, under PHYSICAL OPERATION are configured for port 1, which is the port that connects the Controller to the rest of the network. Since the whole network is using VLAN 1, I set the VLANs for the Management interface and AP interface to 0, untagged. I noticed when I set the AP manager interface to 1 I get the same results.
I know that the 3600 series APs are not supported on the 4404 WLC. However, would the following scenario be supported? I would like to use the 4404 (software rel. 7.0) as a guest anchor with a 5508 (software release 7.2) as the foreign controller supporting series 3600 APs. I ask because the APs do not need to join the guest anchor.
We have a customer that have 2 5508 as primary and backup controller and a 4400 as an anchor controller. We plan to upgrade the 5508 to 7.3.112.0 and the 4400 is already 7.0.116.0. Will there be any issue if the anchor controller is not the same code as the foreign controller? Do I also have to upgrade the acnhor controller to 7.0.240.0?
I've download a login.html into the controller successfully, but when I preview the page there isn't an accept button. Do I need to create the accept button with the html file or is there some place I need to enable on the controller itself. After download the .tar file I reboot the controller but no luck. I also create a java script button redirect but it didn't redirect to where I needed to go. It just stuck on the splash page.
I have new 1600 series Access Points. I am trying to join those APs on controller but unable to join.
After doing config reset using mode button, I was able to join only. Please find the logs or error messages below:
*Mar 4 18:53:13.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.2.241.50:5246 *Mar 4 18:53:14.063: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255 *Mar 4 18:53:14.079: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down *Mar 4 18:53:14.123: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up [Code] ....
I have a customer whom has six LAP1131AG-K9 but no controller and they are interested in one of the new 2500 series, specifically a AIR-CT2504-5-K9 with a 5 AP add-on license to bring total AP capacity to 10. I can't determine clearly if this controller will work for these older AP's prior to them making the jump to 802.11n via the 3500 or 3600 series, looking to the community to confirm.
We have 4 1142N LAPs that I want to divide between an internal wireless and a guest wireless network using the controller. Currently all of the APs are on an established internal network, but I want to migrate one over to a test guest network before buying more LAPs to augment the networks further. Currently the port connecting to the WCS from the 3560 switch is configured as an access port using VLAN 10. Whenever I make it a trunk port carrying VLAN 10 as well as the other ports we will be using for the guest and ap-manager networks, I lose connection with the controller. To me this implies that the port on the controller is configured as an access port as well. In the documentation I found for the controller it states that by default the ports are al configured to be trunks, but it appears as though something was changed by the previous tech. All of the APs are connected to other switches, not to the controller itself.
1) How can I get the port on the controller back to being a trunk port
2) Can I use the internal DHCP server for the guest network if the subnet is different than the management subnet, or will I have to use another external server and relay/proxy it through the controller to give guest clients IP addresses?
The Release Notes for 7.0.116.0 of WLC 5500 has a table which title is "Client Type", and it shows wireless adapters. My question is, what kind of customer means? Wireless clients or clients for an specific application? If it was the first option, does it mean tha just this adapters could connect to my wireless network?
I have an AP group on a Cisco 5508 WLAN controller. Currently, it is populated with 13 Cisco 1142 lightweight access points. When I try to add a Cisco 3602i access point to the group, I get the following error in NCS: Error: OfficeExtend requires primary, secondary, or tertiary controller management IP to be set.I am using DNS to allow my AP's to find the controller and they work just fine. Is there a reason I can't add the 3600 series AP's to the AP group?
I have a 5508 controller with a bunch of 3600 Series APs. I did all the basic config on the controller and added all the APs through distribution port #1. Now I was trying to config a second interface ( port #2) and use it for the Guest SSID on a separate VLAN. After I rebooted the controller, it dumped all the APs. I would like to know if this is normal, If I need to enroll the APs everytime I reboot the controller.
We are facing an issue with a customer where a Cisco 4400 Series controller is blocking the 802.11a/n Radio Interface of a 1250 AP. The radio shows as down on the controller GUI. The error message on the GUI is that the 'Regulatory Domain' is not supported. This can be seen from the attached screenshot. Also relevant parts of the WLC configs are attached. WLC: Cisco 4402 WirelessWLC Country: SADevice: Cisco Lightweight Access Point 1250 (LAP) is controlled through the 4402 Cisco Wireless LAN Controller (WLC)The operating system version of the LAP: c1250-k9w8-mx.124-18a.JA version of the WLC: Software Version 5.2.178.0 The problem is that the controller shows that the 802.11a/n Radio Interface in Radio Slot # 1 is always down , the customer tried to manually 'no shut' the AP interface from the console and it worked , but obviously this solution would not work as the configuration cannot be saved (LW AP).
If the 2600 series access points are compatible with a 4404 controller running 7.0.235.3 code? I was looking for a compatibilty matrix for the AP to controller to code comparison but couldn't find one.
I recently upgraded our controllers to the latest version 7 software, as I read this was one of the requirements to get them to connect. But I am not having any luck getting into a controller. Normally I plug them in to the network, they pop into the controller listed as something like AP5057.a844.xxxx and then I can finish configuring them, but a static IP on them, etc. This is the first of this model AP I have tried to deploy, so I am wondering what is different with these. or what I might be missing in the default config in the WLAN controllers. Niether of which are set to "Master" either.
I have a 5508 controller at our headquarters and am installing some 3502 AP's at a remote branch. Unfortunatly, the remote branch has a different Vlan setup for some reason and the vlan that is used for the WLC (90) is designated for telephony at this branch. Can I put the AP's on a different VLAN (10) without having any issues? I will still use DHCP option 43 to point them back to the controller. Below are the configs for the WLC interfaces and what I am proposing for the AP interfaces:
Cisco 5508 Series Wireless Controller for up to 100 APs 802.11a/g/n Ctrlr-based AP w/CleanAir; Ext Ant; E Reg Domain..For Mobility i want to settup the device such that the SSID would be the same with thesame security key and in different subnet.
I use WLC 5508 (ver 7.0.116.0) with aironet 1140. I need to connect my APs to different controller .After log in via ssh to AP i am trying to do:
capwap ap controller ip add x.x.x.x reset
But after reload, AP is still joined to the old WLC. So another idea was to log to that WLC and put:
config ap primary-base WLC2 AP_NAME x.x.x.x
and after that:
config ap reset AP_NAME
But still nothing, it's joined to another controller although "show ap client config" shows that primary-base switch is x.x.x.x ?How can i force it to join to other controller?
We are looking to upgrade our 5508 wireless controller from 7.0.98.0 to 7.0.220.0. Reason being, we have experienced a lot of access points disassociating from the controller as well as client authentication issues. Upgraded from 7.0.98.0 to 7.0.220.0 and any issues during the upgrade or after the upgrade?
We have a WLC (5508) in our main office in Brisbane that is hosting two WLANs. One provides wireless access to our internal network and the second provides wireless guest access. The guest WLAN is anchored to a controller sitting in the DMZ at our Data Centre.
In the DMZ the anchor controller has a management interface and an interface in the DMZ for the wireless guest access. I am using the DHCP server on the anchor DMZ to provide IPs etc to wireless guest clients. The default gateway is 10.8.144.1 which is a VIP or a pair of firewalls.
Initially everything works fine. Guests connect to the guest network, have to authenticate via a web portal (Cisco ISE server) and then can go on an use the internet. Works perfectly until the firewalls fail over and the secondary firewall takes over the VIP address. All access to the internet is lost at that point. If I try to disconnect and then reconnect a wireless client it connects, as in it will get an IP address, but DNS resolution stops and I do not get redirected to the web auth portal. If the firewalls are failed back to the primary then everything works again, no issues. However, if I reboot the WLC while the secondary firewall has the VIP IP everything will work fine as it did on the primary. If the firewalls now fail over to the primary again everything goes to ****. Until either the firewalls are failed back or the anchor WLC is rebooted.
Initially I thought this was an issue on the firewall, but this doesn't appear to be the case. When the firewall fails over it sends out a gratuitous ARP advising of the change in MAC address for the 10.8.144.1 IP address. The WLC seems to update its ARP table because if I run the command "show arp switch" it has the 10.8.144.1 IP address with the MAC address of the active firewall. From the client perspective I have run a wireshark and captured packets on the wireless interface when trying to connect. The laptop is continuously send ARP requests for 10.8.144.1 but gets not reply. Without this the client cannot send an ethernet frame to the gateway and hence get to the DNS server and WEB portal. Internet access breaks. Doing a TCP dump on the active firewall shows it receiving and then sending a reply to the ARP request. It just never gets to the wireless client. Debugging ARP packets on the anchor WLC seems to indicate that the controller is receiving the ARP replies from the firewall. So I'm at a loss as to why things should break when the firewalls fail over.
I have a 3750 switch in the DMZ with SVI of 10.8.144.4. I thought I could get a work around where I would make this the default gateway. The theory being that this interface MAC address would never change. However I was wrong. Even with this IP set as the gateway address for the wireless clients I see the exact same bahaviour when the firewalls fail over. I can't explain it other than to say that the gratuitous ARP sent by the firewalls seems to kill the ability of ARP replies to be sent back to the wireless client.
Just replaced a 2106(ver 5.1) with a 5508 (ver.7.2)...Everything was OK.. AP's got on 5508 and we shut the 2106. (AP's are on L2 with controller)During some investigation of why new LAP's from a location via VPN/GRE don't show up in controller, i type the following command on 5508: test ap pmtu enable all....All AP's on 5508 is now in Not Joined state..Have powered up the old 2106 and put AP's on that .. This is OK ....Have rebooted/downgraded/upgraded the 5508 controller but with same result.....No AP's can join this controller (exept from a oeap600)
