Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About ForceFlow
08-18-2017
Stats
Member since
09-27-2012
7
Posts
10
Helpful
0
Solutions
Created by
ForceFlow
in Small Business Wireless
in Small Business Wireless
02-16-2014
02:43 PM
02-16-2014
02:43 PM
Unfortunately, this was never solved. The workaround helped slightly, but did not come anywhere close to fully resolving the issue. I finally gave up and ended up returning the WAPs that I could and then ended up going with another vendor-- Ubiquiti Unifi-AP-Pro WAPs. I also heard that Meraki WAPs were a viable replacement, but I haven't actually used them myself.
... View more
05-14-2013
12:41 PM
I ended up calling Small Business Support a while back, and eventually got passed to someone in "Business Support Level 2 Escalations". After going through all the standard troubleshooting stuff (including a hard reset), the technican said it was a known issue and there were no more firmware updates planned for the WAP4400N to address the issue. Since the issue couldn't be fixed, I was offered a refund for the devices still under warranty. However, the refund process has taken 2 months so far, and it's probably going to be another 1-2 months before I actually see a refund check, even though I sent in the WAPs over a month ago. In any case, I ended up going with Ubiquiti's Unifi-AP-Pro access points, which were about $250 each--slightly more expensive than what the WAP4410's were, but after using them for the past 2-3 months, they are certainly a superior product--they can handle more simultaneous users, have a larger coverage area, and are centrally managed with a free software tool. I'll probably never go with linksys/cisco again unless they really shape up in a drastic manner. Cisco is no longer top-dog in the networking arena. There are now many options on the market at more reasonable prices.
... View more
Created by
ForceFlow
in Small Business Wireless
in Small Business Wireless
02-14-2013
12:57 PM
02-14-2013
12:57 PM
I ended up increasing the beacon rate back up to 350ms, since the access points were still locking up a few times a day.
... View more
Created by
ForceFlow
in Small Business Wireless
in Small Business Wireless
02-11-2013
06:45 AM
02-11-2013
06:45 AM
1) LAN port speed doesn't appear to have any effect 2) Forcing a connection type doesn't seem to have any effect. This is also rather impractical. 3) I don't have that option (though there is a TKIP/AES mixed option). Either way, I'd rather not have to resort to using a weaker encryption method. 4) No effect. I did manage to find some information about the error message (older versions of firmware didn't even offer that clue). http://www.dd-wrt.com/wiki/index.php/Advanced_wireless_settings#Beacon_Interval I ended up increasing the beacon interval from 100ms to 500ms under Wireless > Advanced Settings. The wifi analyzer app on android seems to keep dropping the SSID when the beacon interval is set that high, so I might have to adjust it to find a good balance. However, while it was set to 500ms, none of the access points went down for two days. [edit]: I reduced the beacon interval incrementally down to 300ms. It started locking up at 250ms.
... View more
Created by
ForceFlow
in Small Business Wireless
in Small Business Wireless
02-08-2013
10:49 AM
02-08-2013
10:49 AM
I maintain multiple buildings, and each building has anywhere between 1 and 4 Cisco/Linksys WAP4410N access points. The problem is that at random intervals, the access points just stop sending and receiving wireless traffic. Every day or two, I have to log into every single access point (either via HTTPS or SSH) and reboot them in order for them to start working again. In short, here are the config details: They are all version 2 hardware (either WAP4410N-A V02 or WAP4410N-E V02). They are running IPv4 (IPv6 is disabled) and get static IP addresses via DHCP. When there are WAPs with overlapping signals, each WAP is on a different non-overlapping channel (1, 6, or 11). Each WAP has two SSIDs (with spaces in their names). One is secured with WPA2. The other is unsecured. There are two VLANs on the Ethernet interface. Each of the two SSIDs are assigned to a separate VLAN. There is a DHCP server on the network, so the WAPs do not actually assign IP addresses to clients. All of the WAPs are running on PoE switches. However, some are gigabit and some are 10/100 switches. Brands vary (Dell and Linksys) and models vary. Cisco finally recognized this issue as: CSCtx62203—In certain environments and traffic model, the WAP4410N may lockup after some undetermined time. Workaround: Reboot the device. As such, the workaround didn’t really offer anything new. Rebooting every WAP ends up being a very time consuming process. It’s awful. And since you have no control over when this issue surfaces and can’t put any safeguards in place, I get calls about it at various points of the day almost every day. Supposedly the most recent firmware update (2.0.6.1) claimed to fix the issue, but it only seemed to make it worse. So now instead of a WAP locking up every day or two, it locks up anywhere between every 15 minutes to 4 hours when in use. The firmware was updated and the following issue was fixed in firmware version 2.0.6.1: CSCtx62203—In certain environments and traffic model, the WAP4410N may lockup after some undetermined time. (A protection mechanism was added to guard against sporadic problems with client association that could occur after six to 24 hours.) As for troubleshooting, there are no error packets. On access points running firmware 2.0.6.1, these messages appear: Feb 7 13:42:27 Syslogd start up Feb 7 13:51:59 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 13:52:01 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 13:52:05 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 14:47:01 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 14:47:02 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 14:47:05 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 15:22:53 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 15:22:56 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 16:15:19 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 16:15:33 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 12:27:25 Syslogd start up Feb 7 14:06:18 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 14:06:23 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 14:44:28 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 14:44:31 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 15:09:18 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 15:09:24 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 15:42:23 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 15:42:25 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 16:52:18 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 16:52:24 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 16:53:05 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 17:20:05 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 17:20:08 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 17:23:34 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 17:23:39 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 21:21:28 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 21:21:30 syslog: Found beacon stuck, down and up the VAP interface. Feb 8 09:55:23 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 8 09:55:29 syslog: Found beacon stuck, down and up the VAP interface. These log messages appear on both WAP4410N-A V02 and WAP4410N-E V02 devices. I noticed that when the “beacon stuck” message appears, wireless traffic locked up 10-15 minutes prior to the message’s appearance in the log, and the SSID drops for 4-6 minutes after the message appears. Is there anything that can be done to address the issue?
... View more
Labels:
02-08-2013
09:20 AM
I maintain multiple buildings, and each building has anywhere between 1 and 4 Cisco/Linksys WAP4410N access points. The problem is that at random intervals, the access points just stop sending and receiving wireless traffic. Every day or two, I have to log into every single access point (either via HTTPS or SSH) and reboot them in order for them to start working again. In short, here are the config details: They are all version 2 hardware (either WAP4410N-A V02 or WAP4410N-E V02). They are running IPv4 (IPv6 is disabled) and get static IP addresses via DHCP. When there are WAPs with overlapping signals, each WAP is on a different non-overlapping channel (1, 6, or 11). Each WAP has two SSIDs (with spaces in their names). One is secured with WPA2. The other is unsecured. There are two VLANs on the Ethernet interface. Each of the two SSIDs are assigned to a separate VLAN. There is a DHCP server on the network, so the WAPs do not actually assign IP addresses to clients. All of the WAPs are running on PoE switches. However, some are gigabit and some are 10/100 switches. Brands vary (Dell and Linksys) and models vary. Cisco finally recognized this issue as: CSCtx62203—In certain environments and traffic model, the WAP4410N may lockup after some undetermined time. Workaround: Reboot the device. As such, the workaround didn’t really offer anything new. Rebooting every WAP ends up being a very time consuming process. It’s awful. And since you have no control over when this issue surfaces and can’t put any safeguards in place, I get calls about it at various points of the day almost every day. Supposedly the most recent firmware update (2.0.6.1) claimed to fix the issue, but it only seemed to make it worse. So now instead of a WAP locking up every day or two, it locks up anywhere between every 15 minutes to 4 hours when in use. The firmware was updated and the following issue was fixed in firmware version 2.0.6.1: CSCtx62203—In certain environments and traffic model, the WAP4410N may lockup after some undetermined time. (A protection mechanism was added to guard against sporadic problems with client association that could occur after six to 24 hours.) As for troubleshooting, there are no error packets. On access points running firmware 2.0.6.1, these messages appear: Feb 7 13:42:27 Syslogd start up Feb 7 13:51:59 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 13:52:01 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 13:52:05 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 14:47:01 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 14:47:02 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 14:47:05 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 15:22:53 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 15:22:56 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 16:15:19 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 16:15:33 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 12:27:25 Syslogd start up Feb 7 14:06:18 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 14:06:23 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 14:44:28 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 14:44:31 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 15:09:18 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 15:09:24 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 15:42:23 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 15:42:25 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 16:52:18 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 16:52:24 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 16:53:05 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 17:20:05 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 17:20:08 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 17:23:34 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 17:23:39 syslog: Found beacon stuck, down and up the VAP interface. Feb 7 21:21:28 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 7 21:21:30 syslog: Found beacon stuck, down and up the VAP interface. Feb 8 09:55:23 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36) Feb 8 09:55:29 syslog: Found beacon stuck, down and up the VAP interface. These log messages appear on both WAP4410N-A V02 and WAP4410N-E V02 devices. I noticed that when the “beacon stuck” message appears, wireless traffic locked up 10-15 minutes prior to the message’s appearance in the log, and the SSID drops for 4-6 minutes after the message appears. Is there anything that can be done to address the issue?
... View more
Labels:
09-27-2012
12:31 PM
I have two WAP4410N wireless access points powered using Power-Over-Ethernet. Both are running the latest available firmware version (2.0.5.3) They are both connected to the same LAN and broadcasting the same SSID with a WPA2 password. One is using channel 1, while the other is using channel 11. There is coverage overlap where the signal from both access points hover around -75db to -85db while standing in the same physical location. DHCP is disabled, and is being provided by another network device. Every day or so, devices can connect and authenticate to the access points, but are not granted an IP address (and subsequently are unable access to the LAN or Internet). For devices that had already retrieved an IP address prior to the issue exhibiting itself, the devices simply stop communicating with LAN and Internet. However, I can still access each access point's web admin interface from the LAN. If I reboot both devices, the problem vanishes and devices are once again able to get an IP address and connect to the LAN and Internet. Are these symptoms of signal interference between the two WAPs or is this a completely different issue?
... View more
Labels:
Created by
ForceFlow
in Small Business Wireless
02-16-2014
02-16-2014
Unfortunately, this was never solved. The workaround helped slightly,
but did not come anywhere clos...
Created by
ForceFlow
in Small Business Wireless
02-14-2013
02-14-2013
I ended up increasing the beacon rate back up to 350ms, since the access
points were still locking u...
Created by
ForceFlow
in Small Business Wireless
02-11-2013
02-11-2013
1) LAN port speed doesn't appear to have any effect2) Forcing a
connection type doesn't seem to have...
Created by
ForceFlow
in Small Business Wireless
02-08-2013
02-08-2013
I maintain multiple buildings, and each building has anywhere between 1
and 4 Cisco/Linksys WAP4410N...
Public Statistics
| Date Registered | 09-27-2012 12:16 PM |
| Date Last Visited | 08-18-2017 04:00 AM |
| Total Messages Posted | 7 |
| Total Helpful Votes Received | 10 |
