Cisco Wireless :: AP3502 Registration Failure On WLC 5508
Oct 11, 2011
I am having issues registering Cisco 3502 APs with a WLC 5508. They initially register and then disassociate with the controller and fail to re-register. Is it possible to telnet to AP and factory rest the AP. I get connection refused when I try
i have a problem with 1552E to register with 5508 WLC, and always got "AAA authentication error” in the WLC log, while AAA is not enabled. so my question is , do i need to add the MAC address to the WLC MAC filter list even if i not enable the AAA server in the WLC.
I've set up several local network users (Security > Local Net Users) on the WLC (5508 running 7.0.98.0). Whenever I try to connect with one of these user accounts (I'm testing this out for now), the attempt is unsuccessful and I see an "AAA Authentication Failure for UserName: xxxxxxx User Type: WLAN USER" in the Trap Log. I thought that after trying to authenticate through a RADIUS server, the local user database would be polled and then a user account in that database would be able to authenticate.
I have been noticing in my trap logs that there are an excessive amount of Client Association/Authentication Failures. I cannot figure out why. I have a Cisco 5508 WLC with 81 AP's (1131ag, 1142abgn, 1262N) models. The wireless devices are on a Windows Domain and use 802.1x EAP authentication, authenticating the user and computer info with a RADIUS Server. I look at the logs and all it can tell me is Reason:Unspecified ReasonCode:1. I read that the Reason Code is due to "Client associated but no longer authorized" but to be honest I am not sure what that means.
I have implemented a Guest WLAN solution as per the recommended design from Cisco. We have two internal WiSM2 controllers providing services for Internal secure SSIDs. Both these controllers are members of a Mobility and RF management group.
Two 5508 controllers have been installed in our DMZ for resilience and have been placed into a separate Mobility group. All controllers (internal and external) have been linked together as mobility neighbours in a full mesh and a new SSID for Web Guest traffic has been anchored to the controllers in the DMZ.
Web page authentication works perfectly fine, but I cannot for the life of me get the MAC filtering override to work, i.e. if a MAC address is present, do not redirect to the splash page for web auth. I know I can get around this by just creating two separate SSIDs. But the business is used to just having the one SSID for all guest traffic. Is this a known limitation when anchoring SSIDs to controllers in the DMZ ?
I have implemented a Guest WLAN solution as per the recommended design from Cisco. We have two internal WiSM2 controllers providing services for Internal secure SSIDs. Both these controllers are members of a Mobility and RF management group.
Two 5508 controllers have been installed in our DMZ for resilience and have been placed into a separate Mobility group. All controllers (internal and external) have been linked together as mobility neighbours in a full mesh and a new SSID for Web Guest traffic has been anchored to the controllers in the DMZ.
Web page authentication works perfectly fine, but I cannot for the life of me get the MAC filtering override to work, i.e. if a MAC address is present, do not redirect to the splash page for web auth.
I am running WLC 5508 and WCS version 7.0.98. We are noticing with some of our handheld devices that have Sychip Wireless cards that they constantly have issues communicating. The error I see on the WCS side is shown below:
Client '00:0b:6c:2f:d0:32 (0.0.0.0)' failed to associate with interface '802.11b/g' of AP 'HO-BRSales'. The reason code is '0(null)'.
We have Cisco WiSM modules on our 6500 switch. I tried to register a 1142 access point to the WiSM. Is there any difference in the way an AP registers and appears on the WiSM as compared to the Wireless Lan controller?
I could see the AP get an ip from dhcp pool ( configured on the switch ) and Ap was visible on the cdp neighbor of switch.
However, i could not locate the new AP on the WiSM module. Do i need to add MAC address to the WiSM as same as WLC.
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 just started a project to make a guest wireless network available at every site in my enterprise. Guest wireless networks are currently available at some sites. Two key goals of this project is to enable WPA/WPA2 encryption and to develop a web based registration/autentication solution. All of the sites have a mixture of 1230, 1240, and 1250 autonomous access points. What do I need to do/get in order to make this happen?
I am attempting to register QPM 4.1.5 into LMS 3.2.1 Portal, under Home Page Admin - Application Registration but It fails.It seems to be a bug where it puts the details in the wrong place when submitting the info.
This is the output that it tries to submit obviously - Description, host name, port number and protocol are mixed up.You have selected the following application to be imported from the remote server. [code]
I'm not sure where to find the Tomcat logs or how much use they would be.
I just bought 2 Cisco3750 X Switches, After I open the box, there are too many numbers lables on the switch.
1. Which number is for product registration ? 2. Can any give me the link for product registration ?
BTW, can explain to me what is PAK, is it come with the switch ? Where I can find it ? I can find serial number but I don't know how to use it and connect with PAK.
I've just had to rebuild my ACS appliance with new hardrives but I am unable to register the devices to each I get a system error. I thought it may have had something to do with the rebuilt device not being joined tothe domain but it has now been joined albeit using a different ad account, but still cannot register to primary.
We have a SRP527W, we have created VLAN for DATA and VOICE remotly connected to an office by VPN.
VPN is working fine.
Now we want to register SIP lines integrated in SRP527W to a Cisco Call Manager located in our office.
The problem is that the source of SIP packets is WAN interface of the SRP527W, so packet wont pass in the VPN. Is possible to change the IP source of the SIP registration ? The most useful will be to set the IP source SIP on the voice VLAN.
I'm constantly seeing that the sync and replication status for my secondary admin/monitor node in the primary node as node not reachable. The secondary still thinks it is in standalone mode. When I run the ISE diag tool connectivity tests I am able successfully ping the devices from each other using both hostname and ip and the nslookup also works fine between both nodes. Ping and nslookups also work from different networks within the environment. The two nodes are in the same vlan on a 6500 vss pair but on different switches of the pair.
I recently bought a Cisco WAP 321 for my company, but when i connect it to the network, the switch on which I connect crashes, and I lose all connectivity to the network, (internet also). i have to unplug the WAP321 and wait for a few minutes to be able to use the network again.
I'm currently using a small 8 port switch, There are usually 3 or 4 users connected on it. When I try connecting the WAP321 on another switch, only connected to 1 computer, it seems to be working : I can access the configuration page, and make some modifications.
trying to connect studio 540 desktop by wireless connection with homeowners airport extreme. windows cant find connection. sure had wireless card installed at purchase. what adapter do i need? wireless card? what are options for wireless network connection for this desktop
We have cisco wlc 2125 with 13 AP 1131g. All works good. But after power failure one AP can not join to controller, only reset work to recover connection AP to WLC. Additionally, we don't have access to rs-232 port on AP. In this moment on WLC we can see DISCOVERY request from AP and response from WLC to AP, but AP don't send JOIN to controller.
I have an 1142 CAPWAP AP running IOS 12.4(25e)JA$ on a 2504 controller running 7.2.103 that's frequently reloading. NCS is reporting the reason for the reload as 'AP Crashed Due To Software Failure'. Other 1142 APs on the same controller aren't experiencing any problems. The AP is in H-REAP mode with local switching but central auth.
I'm having the following issue with a couple of 1231's.
Some overall config info first:
This is a small office with 2x Catalyst 2950 (24-port, no PoE) switches and 4 AP1231G (autonomous). The APs get PoE from a PWRINJ3 each. The injectors are powered by the AP power supplies. Injectors and power supplies are mounted in the patch closet.
The 2 switches are connected together over 4 ports (20-23 on each switch), these ports are set to 1Q Trunk mode.
The APs are connected to the switches, 2 to each switch, on port 1-2. These ports again are configured as 1Q Trunk.
All this has been working without problems for a number of years.
A few weeks back, AP2 did not restart after a power cut (everything else did). All LEDs are off, port on switch has no LEDs lit. I did not get around to investigating this furtehr until last week. I unmounted (failed) AP2, took it to the spot where (working) AP3 hangs, and plugged it to the cable of AP3. AP2 came to life immediately. I unplugged it and plugged AP3 back in, which restarted immediately.
So I suspect a power supply issue on AP2. I took the injector and power supply that fed AP2 out of the patch closet. When connecting AP2 directly to the power supply, it came to life immediately. So I figure the injector is defective.
On the same day, I notice AP4 is also dead (again all LEDs off, no idea how long, could have been that day or could have been a few days - it has definitely been working after the power cut that appeared to have killed AP2).
So I order 2 new PWRINJ3s and for good measure 2 new power supplies. Later that day, I took the injector and power supply that fed AP4 out of the patch closet. When I try this combination (AP4, injector4 and P/S4), and connect it to a different wall outlet (and therefore a different port -16 - on the switch) IT WORKS! Should have triggered questions, but did not immediately.
Last Thursday I got the new injectors and power supplies. So I take one of each, hook them upto AP2 at my desk, and AP2 starts up. So I mount new injector2 and new P/S2 in the patch closet, put AP2 back in its place, connect all the cables - NOTHING. AP2 does not start. The "power" LED on the injecvtor lights up green, the "device status" LED remains off. I take AP2, new injector2 and new P/S2 to my desk, hook them upto a wall outlet (connected to switch port 17). AP2 starts immediately.
Meanwhile AP3 has (also) stopped working (no LEDs on at all). As far as I can tell, it stopped working after I briefly disconnected (and reconnected) the patch cable between injector3 and the patch panel in the patch closet. The LEDs on switch port 1 are off.
I have since tried to power cycle both switches (took power off both, waited a while, poewerd both back on). No change.
PS: the APs ran firmware 12.3(8)-JA until recently. AP1, AP3 and AP4 were upgraded to 12.3(8)-JEE after the the power cut that took AP2 out. THis is when I found out AP2 was dead. AP2 was still on 12.3(8)-JA. It was upgraded to 12.3(8)-JEE last week when it was on direct power on my desk.
I have recently purchased a Wireless-N repeater which is now up and running and connects with both Ipad, iPhone and other laptops with ease. The problem is that I can't connect using my own PC. I'm using Windows Vista and the connection to the repeater seems fine, it just can't connect to the Internet. Every time I try and open a web page I receive the following message.Error 105 (net:ERR_NAME_NOT_RESOLVED) Unable to resolve the servers DNS address.
I have had a wag320n for a while and ever since I bought it, The wireless stops functioning after a day or 2, if I save the settings and then restore the settings (even after it has stopped working) then it works again for a day or to then I have to repeat the process.While it was annoying most of my PC's were wired so it wasn't a major issue but in my new place I am mostly wireless so I am well over it already.
We have a client that has a large number of AIR-AP1252AG-N-K9 installed in the network with power injectors. We have seen a about 48% failure rate of AP's failing with all 3 red lights on the unit. Once I get the AP in the lab I'm unable to get any response from the console, therefore unable to troubleshoot.
I made a lot of tests during some days with a wlc4402 and everything was ok.
One day when I tried to reset the system I had a lot of errors (see attach) and could not go on. After changing the image the following output appeared: "RAM Disk Image Integrity Check Failed (Bad Magic Number) Hanging". Now I have no response from the controller.
The wireless client can't get the DHCP address when I enable the On-MAC-Filter-failure, MAC Filtering and Web Auth. Client can get the DHCP address when I only enable the Web Auth in the same WLAN SSID. The WiSM verion is v7.0.235.0. [code]
I've been working with a client's integrated 3750 WLC running 4.0.179.11. I want to upgrade the code because it is old plus I am having DHCP trouble. I have a couple of questions:
1. Is it OK to upgrade to SWLC3750K9-5-2-193-0.aes ? or do I need to go through 4.2 first ? 2. Will that code upgrade the bootloader at the same time? 3. How can I make sure there is enough flash space on the WLC? 4. Are there any special considerations to plan/prepare for?
The DHCP issue is failure of associated clients to get an IP address with this message found in WLC debugging:
I have been attempting to set up a linksys wireless-n e1200 router on my hp p6-2007c (Windows 7 SP1, 64-bit) desktop pc for the last day and have exhausted everything i can think of. The previous router was a linksys WRT54G and it worked fine. However, upon setting up this new router i get a "no internet access" message accompanied by the little yellow triangle and the ability to still connect to my router via its ip address to alter its configuration. The connection status for the network and the internet is identical for all the laptops in my house. I originally attempted setting up the router using Cisco's setup program. At its conclusion, the setup program informs me that i am connected to the router, but my internet connection has been lost (even though it was never there) I have tried starting over from scratch by resetting the router back to its default settings and using a variety of different channels (Auto, 1, 6, and 11), frequencies, etc. I have uninstalled norton antivirus, disarmed the windows security programs, made sure of TCP/IP settings, rolled back, uninstalled, and finally updated firmware, uninstalled/reinstalled driver for wireless card, disabled/enabled the card itself, deleted all other previous network profiles still present in the "Manage Wireless Networks" screen, and probably some other suggestions i came across in this forum. They all failed with the same results, i.e. the ability to connect to the network locally and having no internet access.
I am using filezilla (ftp client) to upload to file server as well as other sites including free host and 000webhost, on large files my upload fail near the end,This does not happen if I bypass my e200 router, so it must be something about the the e2000 that is causing the failures.