There's a mobile version of our website.
We have an AP541N that has been deployed to replace a Cisco 1200 AP (B/G radio). The 1200 functioned perfectly in our environment. The new AP541N on the other hand seems to work fine right after a reboot but immediately starts to degrade service. Over a short period of time, the devices bandwidth degrades to the point were the wireless network is not usable. This happens with just one device connected. Eventually, the device stops accepting client connections. We are unable to get any relevant logging out of the device to help diagnose the problem.
What should be our course of action?
Thank you for contacting Cisco Community.
Normally we would ask you to perform a factory reset on the device, flash the device with the latest firmware (downloadable from cisco.com) and then Factory default again.
Check to make sure you have a stable power source (no fluctuations).
Change your wireless settings.. i.e. remove security (for testing)
If security was a factor, try using WPA with a 10 character passphrase, remove any spaces or CAPS from the SSID, and use only a single SSID.
If all else fails, contact our Small Business Support Center and continue troubleshooting toward replacement.
Thanks for asking.
I have recently experienced this as well.
I have it setup as this:
1 ssid / wpa2 / psk (8 character, all lowercase or numbers), running on a/n with both 1.72 and 1.8.
I have also experienced this while plugged into an ESW-520-8P and into an 871W.
What I have noticed is that over time, the 'ping' times to the router goes up to 300 - 3000 ms and clients are unable to connect. Rebooting fixes the problem.
I have just put in a new (different) temporary one at our customer testing this, to ensure it is not related to the device.
This was my concern with not putting in a standard Cisco AP.
When I was testing prior to installation, we were using an ESW-540-8P, and didn't seem to have that problem.
We have put in a different ap to ensure it is not a problem with this particular unit.
So in an effort to elminate 'environment' as the issue, I have put in a AP1242AG, this is not a 'N' access point, but it will eliminate switch, router, and local airspace.
So... assuming that I have no issues with this, is my solution going to be the same as garrettct, which is just return them.
This issue sounds a little like the one I've had...
You should want to take a look at this topic (perticularly if you work with MS DHCP servers) :
I just puchased one of these access point for the office to replace the linksys thats currently hosting our wireless. I thought this would be heads above what I was using.
I setup the unit with basic settings and had three clients attached to it. After a few hours we started noticing issues as well.
I upgraded the firmware to 1.8 and reset to factory default. In mixed mode it doesnt take long for it to degrade out with 3 clients attached. I changed it to 5 GHz 802.11n only, and just myself attached. I have been fine for a few hours. Id hate to not be able to use the AP in mixed mode though.
Has anyone else made any progress?
We have the same problem. Have three AP541n's, been using a/n and works for about 1 hour then hangs up. The three units are clustered. Have lock the channel on one unit to see if it makes a difference. Has anyone seen a difference with the firmware update??
Elliott Lichtstein email@example.com
I have tried a bunch of different setups. The access point first had a bunch of VLANs on it. I took them off and ran a native vlan. Tried fixed channels and other configurations. Nothing helps. My dhcp server in this setup is a cisco 3670 switch. We are currently running on our old 1200 AP with no problems (same environment and location).
We have had the same issue here. The problem we are experiencing is that once the AP stops working, we are able to see the AP and connect to it, but we are unable to get an IP address at that point. Initially, clients were obtaining IP addresses through the network DHCP server. We changed the setup and connected the AP directly to our Sonicwall firewall and set up the firewall to run DHCP for this connection. We are still having the issue.
I reported the issue to Cisco and the initial technician I talked to was able to duplictae the problem in their lab. He has sent the case to the higher level support. The last email I got from the higher level support (about a week ago) said the case has been qeued for further testins and that I will be contacted when that is done. It also said that they are very busy and it might take a while for them to get back to me.
We purchased this unit to replace a Lincsys device we were having issues with. We were told by our consultant that the Cisco AP is a much better unit that would resolve all our issues. My clients are a lot more frustrated than they were with the Lincsys unit. Is there another Cisco AP (or any other brand for that matter) that works without any issues in a network environment that costs about the same?
Thank you for the update sbaharaeen, please keep us posted if Cisco responds to your support request.
I really like the features of the unit and the price point we purchased it. I really hope they are able to rectify the issues.
I have just deployed one of these to a remote office, and I am recieving word of this same issue.
This was going to be the first of probably a dozen or more of these devices for me, but until this is resolved, I obviously can not deploy any more.
I really hope this get's resolved, because I was really liking the product.
I've been running ours on strictly 5GHz N mode only for the past week and it seems to stay stable. In mixed mode it continued to have issues.
Ideally I wanted this device to be used for both G and N. Until a fix is available, the change has at least let some users access through the AP.
in order to ensure that this is solved, would the people who are affected by this please sent me the case number as a private message?
This would help a lot as this would provide insides into FW version, problem description etc.
I use a AP541 at home myself and I don't see this behavior, I use it for VoIP using 2 x 525G phones in Wireless mode, 2 cam's and 3 PC's / laptops.
We take this reported issue very serious, so I'm looking forward to see some details.
We was hit severly by this today, but have also seen it sporadicaly during testing. The system consists of 4 AP541 accesspoints with firmware 1.8.0 running in a cluster with 802.11bgn support, where 3 is connected directly to a SA540 gateway with cable, and one acts as repeater with WDS connection to one of the cabled AP's. All AP's broadcasts with the same SSID and on channel 9.
We have applied the recommended key refresh fix and removed WPA2 support. The AP's are now configures with WPA-PSK encryption with both TKIP and AES available. Todays usage scenario was about 20 laptop users roaming around for ~3 hours, and potentially moving from one AP to another. The internet connection is a shared 10Mbit access, where we typically measures a bandwith of 5-7Mbit/sec with speed tests at our location through a wireless AP that is connected with cable to the gateway. The speed degrade did occur on all AP's today, but some was hit more often than others (might seem to be related to number of clients connected). When the degrade happens, we could first sence it that the signal strength from the particular AP started to fluctuate more than normal and also drop for a periode of 1-2 seconds before reappearing (monitored using 'inSSIDer' WI-FI scanner), and if we then connected to the particular AP and ran a speed test through it, it had dropped down in the range 300-100Kbps, and after a short while it would hit ~60Kbps and stay there.
DHCP issues have not been seen here (DHCP assigned by the SA540), connecting to a degraded AP was always possible it seemed, but general all access through an AP that had the degrade state was extremely slow. To be able to access the web interface of such an AP, we typically had to ensure we had a connection to a different AP and then enter the web interface for the degraded AP through the normal functioning one.
To get it properly working for our users, we had to constantly monitor the four AP's, and do a reboot at first sign of degrade. Thankfully, since the AP's overlap each other, most of the connected clients was transferred to a different AP when we hit reboot, but without constantly personally monitoring this, the WLAN had practically gone down.
For us, this is a very serious issue, and really hope for a fix in a short time periode. We would gladly provide any kind of information requested about the issue, and also test other recommended fixes or workarounds for this if available.
Is ther an update or time frame when this will be fixed. Just deployed the AP yesterday to replace a Linksys and the Cisco AP541N is showing 1M connection where the Linksys is showing 11M connection.
Tier 2 Support and the BU have communicated to us that the Level 1 SBSC agents were informed of this AP541N issue and another DHCP issue as being solved in the next FW release for this product. When customers call SBSC, the support the agents will follow proper protocol and due diligence to determine the problem, and in the event it is considered to be resolved in the coming release, the case will be escalated to 2nd level support. At that time and with the Partners agreement, access to the beta firmware 1.9.0 in test right now can be given, once a beta agreement has been accepted.
Any Partner experiencing either DHCP issues or degrading service, please contact the SBSC for further resolution.
I do not have an ETA for the formal release of 1.9.0.
Partner Sales, U.S.
Steve, this is good news. Thank you for posting an update.
Has anyone got their hands on this update yet? I know Steve just posted, but I also know a few of you have been working with level 2 tech support for a while now. Has the beta firmware corrected any of your issues?
i have 8 AP541N on an UC560 with 31 SPA525G.
None of the Phones can make calls all over the day without horrible noise during the calls. It's like talking with a mobile phone in the 1980th.
It is equal if the Phone is in the same room as the AP or in the next room. The Signal on the Phones is jumping from green to red and back without doing anything.
The PCs on the AP with external N USB Adapaters won't get more than 10-30 Mbit.
I took for testing an MSI AP200+ Powernet to WLAN Adapter for 3 Phones and this works. The signal goes 2-4 times wider then the AP541.
Nothing fixes the Problem. The latest new thing is, that the cluster doesn't change the channels. Every AP is on Channel 6.
If i can't fix the Problem this week, i think i will loose my customer.
Did the 1.90 fix this Problem, can i get the Beta Version?
GIG0/1/0 -> SRW2008P -> 4x AP541N -> x Phones and x PCs
-> 1x AP200+Powernet -> 3 Phones (working fine)
GIG0/1/1 -> SRW2008P -> 4x AP541N -> x Phones and x PCs
-> 1x SRW208 -> 4 Phones and 4 PCs (working fine, PCs get 99,3 Mbit from SBS2003)
GiG0/1/2 -> SA520 -> 48 Port 100/1000 Switch -> SBS2003, NAS, ...
-> WAN Port VDSL50000 over speedport 920
-> Opt. WAN Port VDSL50000 over speedport 920
GIG0/1/0+GIG0/1/1 are configured as APs
GIG0/1/2 configured as Desktop Desktops
All phones are configured for cisco-Voice(vlan100) with WPA2 and TKIP (long key and non ASCI Characters)
APs are configured in Cluster like SBSC2.0 2 SSIDs, Qos, Cluster, ...
Please open a case to get the beta code to save this deal. I am not saying the new code will fix you, but we have heard problems with degrading signal i9n the FCS release....
Clue number 1 is: "Nothing fixes the Problem. The latest new thing is, that the cluster doesn't change the channels. Every AP is on Channel 6."
If Channel Management is enabled when clustering, make sure to also statically assigns a channel on the radio page, otherwise the channels won't change. Auto Channel Selection must be disabled to allow Channel Management to change channels automatically in a cluster.
Per the help page, "Note: The proposed channel assignment will not take effect if the Channel field on the Wireless Radio page is set to auto. The channel must be set to a static channel."
How do you get access to the 1.9.0 beta version?
I am new to the Small Business Pro stuff, but we are a Gold level partner.
My AP is just over 90 days old, so I don't think support is going to help me.
Per your post below, here is our case # on this issue. We are a Cisco Select partner and have these Ap's at many locations are experiencing the problem at most of the locations.
Case # for Cisco Wireless Issue
Cisco has replaced my original AP. I have just deployed the new AP. Unfortunately, I believe that it is experiencing the same degrading problem. It is running firmware 1.8 (same as the original AP). One interesting thing I did notice though is the following:
From the linux console the AP is reporting a lot of packet errors on the wireless link (this is with one client attached and uptime of one day):
wlan0 Link encap:Ethernet HWaddr 00:21:29:00:7D:50
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:162000 errors:650285 dropped:0 overruns:0 frame:15361294
TX packets:421509 errors:3336 dropped:0 overruns:0 carrier:0
RX bytes:42518247 (40.5 MiB) TX bytes:291051214 (277.5 MiB)
Here are the radio interface stats for my Cisco 1200 in the same environment (Uptime on this AP is 4 weeks and has several clients connected):
Dot11Radio0 is up, line protocol is up
Hardware is 802.11G Radio, address is 0012.01e5.2e90 (bia 0012.01e5.2e90)
MTU 1500 bytes, BW 54000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/523/0 (size/max/drops/flushes); Total output drops: 130206
Queueing strategy: fifo
Output queue: 0/30 (size/max)
5 minute input rate 5000 bits/sec, 9 packets/sec
5 minute output rate 4000 bits/sec, 4 packets/sec
29633972 packets input, 2302875179 bytes, 4 no buffer
Received 235828 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
26072809 packets output, 2208254017 bytes, 0 underruns
21421 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
I just heard back from the second tier support and they recommended disabling the Key Refresh as well. I will try this tomorrow and let everyone know how it goes. Is everyone who is experiencing this issue using WPA?
I was having issues when I first bought the unit. I switched over to N mode only and I'm only using WPA2 with AES and things have been running fine.
I will enable WPA and TKIP and attempt this workaround today.
Has changing the Refresh Rate to 0 worked for anyone? I changed mine this morning but have not seen any difference. Pings to our core router that were 1ms on the LinkSys the AP541N replaced are still all over the place and are often in the 1000's on the 541.
Dennis and all,
These workarounds are suggested until we can be sure of the root cause and fix it.
Based on what we think is going on, there are code changes under test right now.
But what would really be helpful, is if everyone can post their logs (attach to your discussion threads) so we can see clearly what is happening in your environments?
Came in this morning and the AP is not responding at all, even to the Windows 7 client that was working fine last week. We are taking it offline and switching to our old setup. I will try to run it in a test environment. Attached are the logs from this morning.
My only user using this AP reported losing it 5 times yesterday.
He said it disappears, and then comes back about 5 minutes later.
I can't test it because it is on the other side of Canada from me.
But here is my log file, since the last reboot.
I will ask them not to reboot it again so I can capture more logs.
Thanks for this. Feeling pretty confident, based on your description of whats happening, that what we are fixing will address this, but more logs would be welcomed as well in the mean time since these logs are just showing disassociate deauth from an unknown reason.
Here are the reasons codes our team found in the log file.
1 /* Unspecified reason */
3 /* Deauthenticated because sending station is leaving (or has left) IBSS or ESS
4 /* Disassociated due to inactivity */
8 /* Disassociated because sending station is leaving (or has left) BSS
We will keep you posted and thank you for your help...
When I had this issue, I have set up a syslogd thinking that It should be more verbose than the AP embedded log page...
but even after several days of monitoring, I've never caught any other error than the ones shown in the log you've seen !
I changed the refresh rate to 0 on ours and we were still having issues yesterday. I am attaching the log file from earlier today, but it was quiet around here so I will monitor next week and post the logs.
One interesting thing I noticed though is that one of my notebooks running Windows 7 has no issues whatsoever connecting and maintaining the connection to the AP. Is anyone else seeing this as well?
I made the change as described above and it seems like I am still getting a relatively large amount of receive errors.
wlan0 Link encap:Ethernet HWaddr 00:21:29:00:7D:50
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:82612 errors:84412 dropped:0 overruns:0 frame:774824
TX packets:125679 errors:4 dropped:0 overruns:0 carrier:0
RX bytes:56553958 (53.9 MiB) TX bytes:135659862 (129.3 MiB)
We have tried 1.9.0 beta on our 4 AP541Ns, and during yesterday evening when a number of clients was connected (this is on a football/soccer stadium), the APs seemed to stay stable. The reason I say "seems", is that we had a major problem with our internet provider so the network did not have high traffic during all the 4 hours with use. But I am quite sure some positive things have happened. During testing the evening before, we also found the throughput on a WDS bridge to have increased too. The next scheduled happening with many connected clients will happen in ~2 weeks, so hopefully we will get a real test then. Conclusion so far is good.
I have access to the beta 1.9. The support engineer said to load it and take tho AP back to factory default and re-configure. I'm managing these two boxes remotely and that isn't an easy proposition. Does the AP need to be returned to factory defaults after 1.9 is loaded?
If upgrading from v1.8.0 the upgrade process will probably go smoothly without the need for a factory default. If upgrading from v1.7.2 that's another story as the default AP parameters changed between this version and v1.8.0 so in this scenario that will definitely require a factory default.
Thanks for the information. There were no notifications I could find about resetting to factory defaults when going from 1.7 to 1.8.
The Small Business Support Center engineer said that "Per our policy and past experience, it is highly recommended to reset the device to factory defaults after a firmware upgrade. If you do not reset the AP(s) and they develop problems or become unstable, you will be asked to reset them to factory defaults as the next troubleshooting step."
This is a non starter for me as it really impeeds me from selling these units if the product development team has this "policy".
Please pass along to the product development team that this can't continue for all upgrades. Even though this product is GPL development from the Linksys group, they can't play fast and loose with the product when it is in sitting in a Small Business. I can't charge a small business customer my service time to factory reset their products when upgrading software to fix a bug in their small business systems including these APs.
I actually got the advice I posted to you from our business unit Product manager.
I am sorry for this, and I understand what your saying. I will pass it along...
The latest firmware for the Cisco Small Business Pro Wireless Access Point (AP541N) is now online. The firmware new firmware version is 1.9.0.
Here is the link to the release notes: http://www.cisco.com/en/US/docs/wireless/access_point/csbap/AP541N/release_notes/78-19182.pdf
I can confirm 1.9 solves our problem with speed degrading. We first tested it during a football match the 14th of April, but sadly that day the ISP failed to deliver us a proper service, so we couldn't get a result we could trust. But it seemed at that point that the WLAN acted fine. Today we had a new test with ~30 journalists doing different kind of media work, and it worked perfectly! No speed degrading or other issues, we did also try to stresst the net with several large up/download tests. We are using 4 AP541Ns in a cluster system, where two of them have a WDS bridge between them.
Thanks a lot for fixing this issue!
We recently upgraded our cluster of 3 AP's running 5Ghz N only to 1.9(0), and also reset to factory defaults and reconfigured, and are still experiencing degradation issues. I also disabled (set to 0) the rekeying, also noted from an earlier post in this thread. It also looks like there's a bug with the Sessions info on Cluster management, as they show a steady decline after only a few minutes from 130Mbps+ sessions down to 1-6Mbps, but checking the laptops wireless they still show 130Mbps+. Any further feedback on others that the 1.9(0) firmware fixes this issue or other things to try. We're to the point of returning these AP's as we're only trying to support 6 users and patience is wearing thin. Thanks.
I have upgraded one AP to 1.9 firmware and the unit is still unstable. I can set in front of the computer and watch the signal go from 1 Meg to 5.5 Meg to 54 Meg and back to 1 Meg in matter of seconds. I have 7 users on the AP and all of them are seeing the same thing. I have a Linksys Wireless Router 5 feet from it and have stronger and more stable connections to it. One user is 20 feet from the AP and is see very poor signal and connection. I even have one user that can connect to the Linksys Wireless Router but can not even see the Cisco AP. If I can not get this fixed today I will have to return it.
I had only a few client connected for a week or so after upgrading to 1.9 and everything seemed to be working great.
We are now having issues again with anything connecting using wireless G. The device attempts to connect and then fails to obtain an IP address. The wireless N clients are able to connect and disconnect freely while the G clients are having this issue. Most of the G clients are phones and ipod touch devices.
After a quick reboot, everything is able to connect and things run smoothly for a day or so.
Any ideas where to start troubleshooting? This AP has a ton of features for a great price, but I've bearly been able to use it since I bought it months ago.
We've had an AP541N running at our office for about a week now. I upgraded it to 1.9.1 right out of the box. It has been solid.... Then on Monday, it refused to communicate with the associated wireless devices. It was like all the wireless connections were "dropped", but they clients still thought they were associated with the AP. A quick disable/enable of the wireless on my notebook put me back on-line, where I logged into the AP and it had not restarted and still showed everything to be normal. Every device that had been associated needed to be disassociated/associated in order to gain full connectivity again.
I then, after reading some of the suggestions on here, turned the key refresh to 0. It has been fine the rest of the week so far..... With no reoccurence of what happened.
Just a very puzzling incident.
my company also has a AP541N-N-K9 Wireless AP. WE have had reports from our customer that the wireless is cutting out also exactly like what is reported in this thread.
WE have changed the timeout to zero and the SSID currently still has spaces in it.
Did the upgrade to the new firmware resolve the connection issues.
From our log there were lots of :
- wlan0 deauthed from BSSID x:x:x:x:x:x reason 4
- wlan0 deauthed from BSSID x:x:x:x:x:x reason 1
- wlan0 disassociated from BSSID x:x:x:x:x:x reason 8
The help menu does not descibe these properly.
It is currently set up for 802.11b/g/n
Channel Bandwidth 20MHz
Short Guard interval supported: Yes
Beacon Interval: 100Msec
DTIM Period: 2
Fragmentation Threshold: 2346
RTS Threshold: 2347
Maximum Stations: 200
Fixed Multicast Rate:Auto
Does the Upgrade work? Has there been any other workaround?
Having the same issue (degrading service).
laptops -> 3x AP541n -> SR520 -> switch/fiber
Initially we had 9Mbit down and 5/6 Mbit up, but after a few hours the bandwith dropped to 1.2Mbit.
I managed to get a stable situation by removing 2 AP's and disabling clustering.
It's still not stable! and dropping clients... did they test this device before selling it??
Can anyone confirm that the issues are resolved by the latest firmware?
Have you updated the firmware to 2.0? Has it helped? I was thinking about purchasing several of these and clustering them, but I'm concerned about all the negative posts I've been reading. Does anyone have these installed and working and is completely satisfied with them?
I thouhgt i did post a response earlier, but it looks like it's gone. Did I not press the 'Add Reply' button? Hmmm...
Yes I did update to the latest firmware. What I did was disable clustering and gave each AP it's own SSID.
No degrading service anymore, but this setup is not what I had in mind. I was out if time to do further investigation.
I have tried the above solutions and I have had the same issues repeat themselves regardless. I have a site that uses 12 of these AP541N's and I've had nothing but trouble with them from the start.
What I've tried:
1) Updated the firmware to the newest 2.0(0)
2) Set the key refresh to 0 (disable)
3) Set the radios to wireless b/g only
4) Set the radios to wireless N only
5) Factory reset, default settings
6) Tried using the power adapters instead of the PoE
None of these things had any effect. At times, I thought I had a breakthrough, then all of the annoying things would happen all over again. Lost DHCP, lost access, can see the WAP but can't get online, etc.
Still looking for any help I can get, but in the mean time, I am replacing key points with an
Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center.
Sir I saw your post and wanted to reach out to you.Please contact me at emoyers @ cisco.com. (take out the spaces)
I need to see about getting you the beat FW for AP541N v.2.0.1 which addresses DHCP issues.
Also just as a side note setting the refresh key to 0 does nothing. That was a potential workaround that was suggested a while back, but has been found to have no validity after some replication efforts.
When you contact me please supply your Cisco User ID and AP541N Serial number. That way I can get a case created for you and escalated up to our tier 2 support team that has the beta FW.
Thank you for your support of Cisco and our products and I look forward to helping you resolve your issue.
Cisco Network Support Engineer
Gemtlemen, for any others that are having the same DHCP issue, I am also willing to work with you as well. Please just follow the instructions and I will escalate your case as well.
Thank you for all your help. Are we to expect a public firmware release at some point in the near future as well?
I've noticed one other issue with this device in the field: Lack of stability when set to 5Ghz. Perfectly stable when set to 2.4Ghz. Of course the workaround is not to use 5Ghz, but was just curious is this is a known issue that will be rectified in a later firmware release as well.
I have 10 of these units deployed at 2 different facilities. I have e-mailed you the serial numbers and my Cisco ID.
I have installed the latest 2.0(1) software and still experiencing the same issue of users being dropeed and then not being able to obtain IP address upon reconnection. I have changed multiple settings as recommended, factory reset 3 different times, reapplied firmware, etc... What to do next. How do we get these faulty devices returned and replaced for a functional model?
I would be interested in this outcome as well, the ap that I have (personally) has to be rebooted at least every 3 weeks otherwise it just stops working. I am also running 2.01
Mr. May and Mr. Yeo, I have your information. I was out of the office the last of last week and in training yesterday and today. I will work with my group to get you some answers and will be in contact with you in the next 24 hours to talk with you more.
It is 2 days later, what is the current status? I have been looking
through the Cisco forums and see this problem has been ongoing for over
2 years and the new firmware 2.0(1) has not resolved the problem. Can
you please advise procedure to return these units for units without
requiring daily reboots to keep them up? Nine of my units along with the
SR520 routers was purchase May 2011, less than 12 months ago - this is
well within the warranty, but outside of the 30 day return policy. I did
purchase one additional unit last month in a attempt to resolve
(thinking I had a week signal).
DAG'S Computers, Inc.
14870 Mussey Grade Rd.
Ramona CA, 92065
Phone (760) 440-3230
Fax (760) 440-3231
How to open a ticket with Cisco?
I was sent the following links to open a ticet by Raman at the Cisco Certification & Communities Online Support Center.
If you require immediate assistance regarding your technical issue, we suggest that you open a ticket with Cisco’s Technical Assistance Center. Please visit the following URL for a list of contact numbers appropriate for your country:
You may also open a Technical Support request online at:
neither link will allow me to submit a ticket. The first link opens and reads Forbidden File or Application
The second link simply comes up page unavailable.
I feel link Cisco is ignoring our request for support for a product that is know to have problems for over 2 years.
DAG'S Computers Inc.
Mr. May, I saw this after I just sent you an email. To open tickets with the Small Business Support Center you have to call in. You can do this at 1-866-606-1866.
The first link should have read:
The second link should have worked:
Cisco Network Support Engineer
SBSC Wireless and Surveillance SME
Wow having the same issues with these just after they have been installed. We have deployed 16 of them, the largest customer has 8 and each customer has reported these issues noted in this thread. Wow blow away that this problem has been going on for 2 years now.. I just put 2 and 2 together last weekend when our NFR device at my house started showing issues.
For us the large issues and what I experienced was that the AP stopped passing or resolving DNS.. Looked at our ticket history and we have a pattern now across all customers we have to reboot every 2 weeks or so. We have not loaded them up so I don't know about the speed issue but for sure DNS stops resolving until a reboot.
- Andrew Birch
Open your ticket, submit for a refund and choose another product.
That is what they did with me, no solution just get a different product.
Lots of wasted man hours deploying and troubleshooting these bad products.
That doesn't sound like much of a "solution" nor does it lend a lot of confidence in there being a genuine fix forthcoming for the issues you guys are experiencing.
I've got 7 of these in the field and on the latest firmware. Other than the 5Ghz problem (which I simply don't use as a workaround), they have been reliable. However, if these were an IOS device, I'm thinking that things would have been fixed MUCH quicker....
Yes i would agree to know that the product is bad is somthing that i would not expect out of Cisco that is for sure and this is a bad one for sure.
working with my rep now to get some $$ to fix the issue
I've just spent the last week trying to get four of these boxes working without success. I've tried WPA/WPA2 b/g/n, n only, all the other suggestions in this thread, latest firmware, clustered, not clustered. I still am having the same issue where the performance degrades to unusable levels very quickly.
I've tried PoE, PoE plus, PoE midspans @ 100 Mbps, Gb supporting PoE injectors @ Gb
Has anyone found this issue happening using a mains adapter? It is the only thing left to try before returning them all, but even if it works with mains, I'll probably be sending them back anyway as we need PoE to work and they seem to be complete rubbish.
I recently bought two of these, using the latest FW 2.0.4, and I am experiencing the same problem. Stops forwarding DNS traffic, then RDP traffic, then other traffic, only resolved by rebooting the device.
I was very surprised as I have always thought highly of Cisco products. But having devices that gets unstable after a few days, is totaly unacceptable for this price range.
If this issue is not resolved within days, I will return the APs and go for other devices.
You will certainly have to get your money back on these units, there is no solution! They are bad from factory and CISCO cannot make them work correctly after 2 years of firmware patches each time saying the issue is resolved, just to find out within a couple of days no the issue is not resolved. This particular issue has caused me to move away from Cisco products and over to ENGENIUS TECHNOLOGIES for my wireless networking needs.
I looked through the release notes for 2.0.4, and one CDETS that fits this issue pretty good is:
CSCth14132—Station Isolation is Sporadic, which should be resolved in 2.0.0.
Can it be that CSCth14132 is not properly resolved for all possible scenarios?
If not, can you please open a new CDETS so we can have this issue resolved, as it makes the product completely useless?
I tried to get them to open a case and resolve the issue - I had 10 of the units installed and had to wait nearly 3 months to get most of my money refunded so I could install a product that actually worked. And even when I got the money back they only refunded 9 of the units, left me holding 1 defective unit and a whole bunch of external antennas I had installed with the units. Not to mention the hours of lost labor installing these broken devices and countless hours trying to fix them once they were installed. BAD call on CISCO's part.
Just like to add to this post, we have had the same issue with 6 of these AP541N units. At one point started to question our own competance in setting these units up, (run a compex network with two ASA5500 CSC's Gb Switches, Multilink Routers etc etc) could'nt believe that the Cisco AP's were at fault, but glad to read that we are not the only ones. We had been using them as AP's and Bridges, Clustered and non clustered. Tried all the usual as mentioned in this post but the same issue would keep happenning, the Units would perform OK after a reboot then gradually service became interupted and then no service at all, reboot and again would work for a few hours before eventually no service. NOTHING instant so everytning you tried appeared to work initially but again the AP would stop responding. The MD of the firm decided enough was enough, although a firm Cisco Fan, replaced the items with Ubiquiti Airmax, which worked in our implementation straight away, (what we would have expected from the AP541N units). Now we want Cisco to let us know what we do with 6 x AP541N units that are faulty.