Trying to get an lightweight AP to register with a controller, never seen this one before where the Discovery request is going out to the controller, the discovery response is coming back, but then nothing. At this point the AP should then send a JOIN request, but it just doesnt.
I am using L3 LWAPP, and have the AP statically configured. its a 1131, connecting to a 184.108.40.206 in a WISM. I have run a wireshark and can see the discovery going out, its response coming back, but then nothing (the debugs below also back this up). I have also jumped on the controller and can see the discovery responces are going out but it says no JOIN's are coming in. I'm aware this is an old version of controller but still..
I've tried many different IOS on the AP, including the one it came with in the box, other previously successful IOS and the IOS that 220.127.116.11 dishes out to its registered AP's, multiple AP hardware resets, controller reboots, tried different controllers. etc... What would cause this? Possibly something in the response? See info below:
AP LWAPP Static IP Configuration IP Address 172.18.240.244 IP netmask 255.255.255.192 Default Gateway 172.18.240.193 [Code]....
We're in the process of upgrading our Wireless AP's from autonomus to LWAP. We're doing the upgrades remotely (we have 100's of sites to do, and it's not possible to be there to console on to each one), using a local computer to upgrade them to LWAP's with the Cisco Upgrade Tool.Having some inconsistent bugs pop up though from time to time.The most common one is that it basically buggers up the IP address after applying the recovery firmware image. It's supposed to keep the IP it had according to the IPFile.txt (for example 172.25.25.4), but it does something very weird... it keeps the last two octets (so 25.4 from the e.g) but replaces the first two octets with a 192.168 address. So the final address in this example after the UpgradeTool has done its work, is 192.168.25.4 - which is compeltely wrong.
This causes it to be unable to talk to the WLC (obviously, with bogus IP information it will struggle), and gives us big problems in that it wont ever come up unless someone can console to the AP and fix it. We can usually resolve the issue by munging about on the switch - switching the port it's connected to between access and trunk and doing some shut/noshut cycles seems to do the trick mostly.
I recently had to deploy about 4 cisco 1131 AP's to one of our branch location. When configuring them on the controller, i needed to put them in HREAP mode. As soon as i do that and the AP needs to reboot, it will continue to reboot in a loop and indicate the following:
Unexpected exception to CPUvector 1100, PC = 5A9048 -Traceback= 0x5A9048 0x48A8A0 0x4361FC 0x42E078 0x44880C 0x42A280 0x42AA68 0x18A990
I have an AP(1131) that keeps disassociating from the controller. It stays alive for about 10 mins then it doens't work anymore. I tired changing the AP but that didn't make a difference. I also tried changing the port on your 500 POE switch. My last effort to fix it was to put the AP on a 3550 switch with a power injector. Still no luck.
I don't understand why its doing this. I am able to connected to it and surf the internet for about 10 mins. After that It leaves the controller and just cycles through different colors.
I have some questions about this AP and it's IOS. I have some AP's 1131 and they have IOS 12.34(3g) JA I'm working with a 4402 WLC I'm going to change this WLC for one 5508 but this WLC has a different version software it has 7.2.103. My questions is I need to do any upgrade to my AP's IOS for join to the new WLC ?
I found a compatibility Matrix, in this document I guess i nedd to do some upgrade: URLs
The WGB can be any autonomous access point that supports the workgroup bridge mode and is running Cisco IOS Release 12.4(3g)JA or later releases (on 32-MB access points) or Cisco IOS Release 12.3(8)JEB or later releases (on 16-MB access points). These access points include the AP1120, AP1121, AP1130, AP1231, AP1240, and AP1310. Cisco IOS releases prior to 12.4(3g)JA and 12.3(8)JEB are not supported.
I have a static IP given to me by the service provider, and I need to make the Access point as a DHCP server to provide me IPs inside my LAN.I have created a DHCP pool in the AP. But do I have to NAT the public IP onto the private DHCP range ? This setup is possible.
i have a air-lap01131-ag-e-k9 that was originally in lightweight mode and configured with a controller, but i am in the process of wanting to convert to autonomous mode, i am having issues with connectivity to the AP from my laptop.
i have followed numerous guides on this forum, i have successfully
downloaded correct firmware renamed the firmware to .default placed this in root of tftp server folder connected laptop via console to view output connected laptop via Ethernet to Ethernet port of AP changed static ip on laptop to 10.0.0.2 set subnet mask to 255.255.255.0, default gateway to 10.0.0.1 held reset button on AP when applying power and waiting for radio light to flash red AP gets a IP address then of 10.0.0.1
But even though both laptop and AP are in the same subnet, i am unable to ping the AP from my laptop and it doesn't start the tftp process
I have disabled firewall etc, and tried with both crossover and straight through cable, it seems there is something missing at this last stage, i even tried on a second laptop but that would not ping either, am i missing something.
I want to install lightweight IOS into Aironet 1131AG by using Upgrade Tool. However, some error messages appear saying:
1. ACL / Firewall might be blocking the TFTP. 2. Disable the ACL/Firewall setting for TFTP.
I don't set up any ACL because I am trying to install to the Aironet which was just initialized by using mode button. Configuration is just like followings.
Is there any possibility that the configuration block the TFTP communication ? now, ping is reachable and directly, I am connecting AP and PC with upgrade tool . and windows firewall is disable on the PC. But the upgrade tool is error. Why the TFTP communication is failed.
Building configuration... Current configuration : 1361 bytes!version 12.4no service padservice timestamps debug datetime msecservice timestamps log date time msec service password-encryption!host name ap!no aaa new-mode[ code]...
We are evaluating the 5508 WLC Series controller. When trying to associate the 3602i/e wireless access points we have no success. However the 1131 and 1242 legacy AP's will associate.....LWAP Vs CAWAP ?
We've reloaded the 7.2.130 code and it didn't work.
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.
I configured DHCP pool on Cisco AP 1131, Laptop users are working fine and obtain IP address from AP 1131 DHCP Server, but IPad user is getting IP problem when he try to connect Cisco AP 1131.when i reboot the AP, IPad user getting IP address from 1131 AP dhcp server and access the network resource for the 2-3 hr after that IPad show "obtaining ip address from .....".
AP Detail- AIR-AP1131AG-N-K9 c1130-k9w7-tar.124-10b.JA2 12.3(8)JEA
I have this issue regarding the 1131 Access Points. These access points were fat access points from the factory and were applied with LAP ios so that they can join our controller. We have 2 controllers 5108 for Internal network office use and a seperate 2125 for Guest internet both these are physically seperate networks. These AP's have been working fine since say like 8-9 months and suddenly they started giving problems. The status light keeps changing colour and the AP does not join the controller 2125. Whenever i am connecting this ap to our internal network it joins the controller 5508 and works fine but somehow does not register with our 2125 guest controller. This issue is being faced by one of our client. Could this be an issue due to the ap being loaded with lap ios or does it have anything to do with the different software version fo the controllers as i could not find any things regarding this.
I have an 1131ag AP attached to our 5508 as an OEAP over the Internet. Everything with the corporate SSIDs is working correctly, so no issue there. I was wondering if a local ssid can be configured on the AP, similar to what can be done with the OEAP600, in order to provide wireless access to the Internet only? On the WLC, on the H_REAP tab, there is a button labeled "Reset Personal SSID"
I have the 1131 hardware manual and it is stating that this is caused by a boot loader issue or the AP did not get the IOS file from the controller. We have a Cisco 4404 controller that this AP reports to. It was one out of 30 and after a reboot it is working fine. What can i do in the future to catch this and prevent this from happening.
I have WLC 520 with software version 5.2.178. Currently we purchased Cisco AIR-LAP1131G access points and tried to join to WLC 520 but it is not joining. My question is WLC 520 will support 1131G access pont or not.?
Can I change the untagged vlan on a 1131 to a new vlan. I need to move my management vlan from 10.1.1.1 on vlan 1 , to 172.16.0.1 on vlan 200. I attempted several configuration options including removing the vlan1 ip, changing my new vlan200 to untagged and mirroring it on the switch, and adding my new ip to vlan 1 untagged and then untagging the switch with access vlan 200 on the connected port. Nothing worked.
Below is a sample of what I changed:
interface Dot11Radio1 no ip address no ip route-cache
I've ran into an issue that I haven't seen before. A client of mine has a WLC that manages AP's at several different sites on the East Coast. They are all connected via a multilinked T1x2 connection. One site in particular contains 7 AP's, and users at this site are unable to connect. The remaining sites have no issue at all connecting. I noticed that when users began reporting this that all AP's had failed interference profiles. Also, when I instruct a user to attempt a connection, I don't ever see their mac address come across a debug session on the controller, which I find odd. Is it possible that a neighboring business is sending deauth packets and containing my AP's?
I am new to Cisco wireless solution and would like to ask how to add the AP to the WLC properly. All Cisco 1041 and Cisco 2500 WLC are new. I connect those AP and WLC to the switch without any VLAN tag and the AP can gain the IP address from our DHCP correctly. However, the AP 1041 could not join the WLC successfully.
WLC: Cisco 2500 IP Address: 192.168.1.225 version: 18.104.22.168
Our offcie use WLC2100 Series controller with AIR-LAP1031 and successfully join and running. Now i am trying to replace one ap with AIR-LAP1041N and join with WLC, but i can't and below the error message generate: