03-25-2011 09:04 AM
Hello,
We have 2 of these access points, both configured with 2 SSIDs: 1 WPA-enterprise, 1 WPA PSK which is not yet in use, but provided for reference. Running on latest firmware. Have tested the access points running on thier own with the same results.
We have been using them in a closed test for several weeks without issue. Since we made the acces details availble to the company we have experienced problems similar to the below posts:
https://supportforums.cisco.com/message/3078011
https://supportforums.cisco.com/thread/2018665#2018665
What happens in our scenario is no one can connect to the AP, and a power cycle is required to kick it back into life. It then will stay fine for anything from a minute to a few hours. As I said we've had the APs up for several weeks without issue so our suspicion is that a client may be to blame
Here are some recent log entries:
Date | Time | Priority | Hostname | Message |
03-25-2011 | 15:49:08 | Local0.Info | 192.168.16.232 | Mar 25 15:49:07 WAP1 kernel: [][00:23:6C:97:6B:52] SUBTYPE_AUTH |
03-25-2011 | 15:35:10 | Local0.Info | 192.168.16.232 | Mar 25 15:35:09 WAP1 kernel: [Meteor][F0:7B:CB:67:F1:9C] Associated |
03-25-2011 | 15:35:10 | Local0.Info | 192.168.16.232 | Mar 25 15:35:08 WAP1 kernel: [][F0:7B:CB:67:F1:9C] SUBTYPE_AUTH |
03-25-2011 | 15:35:09 | Local0.Info | 192.168.16.232 | Mar 25 15:35:08 WAP1 kernel: [Meteor][F0:7B:CB:67:F1:9C] Deauthenticated |
03-25-2011 | 15:35:08 | Local0.Info | 192.168.16.232 | Mar 25 15:35:07 WAP1 kernel: [Meteor][F0:7B:CB:67:F1:9C] Associated |
03-25-2011 | 15:35:08 | Local0.Info | 192.168.16.232 | Mar 25 15:35:07 WAP1 kernel: [][F0:7B:CB:67:F1:9C] SUBTYPE_AUTH |
03-25-2011 | 15:35:07 | Local0.Info | 192.168.16.232 | Mar 25 15:35:06 WAP1 kernel: [Meteor][F0:7B:CB:67:F1:9C] Deauthenticated |
03-25-2011 | 15:35:06 | Local0.Info | 192.168.16.232 | Mar 25 15:35:05 WAP1 kernel: [Meteor][F0:7B:CB:67:F1:9C] Associated |
03-25-2011 | 15:35:06 | Local0.Info | 192.168.16.232 | Mar 25 15:35:04 WAP1 kernel: [][F0:7B:CB:67:F1:9C] SUBTYPE_AUTH |
03-25-2011 | 15:35:05 | Local0.Info | 192.168.16.232 | Mar 25 15:35:04 WAP1 kernel: [Meteor][F0:7B:CB:67:F1:9C] Deauthenticated |
03-25-2011 | 15:35:02 | Local0.Info | 192.168.16.232 | Mar 25 15:35:01 WAP1 kernel: [Meteor][F0:7B:CB:67:F1:9C] Associated |
03-25-2011 | 15:35:02 | Local0.Info | 192.168.16.232 | Mar 25 15:35:01 WAP1 kernel: [][F0:7B:CB:67:F1:9C] SUBTYPE_AUTH |
03-25-2011 | 15:35:01 | Local0.Info | 192.168.16.232 | Mar 25 15:35:00 WAP1 kernel: [Meteor][F0:7B:CB:67:F1:9C] Deauthenticated |
03-25-2011 | 15:35:00 | Local0.Info | 192.168.16.232 | Mar 25 15:34:59 WAP1 kernel: [Meteor][F0:7B:CB:67:F1:9C] Associated |
03-25-2011 | 15:35:00 | Local0.Info | 192.168.16.232 | Mar 25 15:34:59 WAP1 kernel: [][F0:7B:CB:67:F1:9C] SUBTYPE_AUTH |
03-25-2011 | 15:10:09 | Auth.Info | 192.168.16.232 | Mar 25 15:10:08 WAP1 auth: Authorized Login from 192.168.16.81 |
03-25-2011 | 15:09:23 | User.Info | 192.168.16.232 | Mar 25 15:09:22 WAP1 syslog: lan_dns2 is change to 0.0.0.0 |
03-25-2011 | 15:09:23 | User.Info | 192.168.16.232 | Mar 25 15:09:22 WAP1 syslog: lan_dns1 is change to 0.0.0.0 |
03-25-2011 | 15:08:44 | Auth.Info | 192.168.16.232 | Mar 25 15:08:43 WAP1 auth: Authorized Login from 192.168.16.81 |
Many thanks for your help
Ben
03-26-2011 07:00 PM
Hello Sir,
Just need a little bit more of information to asses your situation.
1) How are the access points setup. Are they in wireless client repeater mode, are just used as standard individual access points.
2) What's the max distance that some of these wireless devices are trying to connect from.
3) Create a test wireless connection. Without security, test the connection see if the connection is consistant and stable. If the connection is strong and stable, then your problem would be with the security settings. Set the channel for (auto) the device will choose the best channel with the least amount of traffic for your area.
4) If the problem persist you would need to call in to our office so that we can start a support ticket, your device may require Beta firmware that can only be issued with a support ticket. We would have to escalate your case and request the beta firmware that could resolve this problem.
Fredrick A Wofford
Network Support Engineer
Cisco Small Busness
03-28-2011 02:20 AM
Hi There Frederick,
Thanks for the reply. In response to your questions:
1. They are individual access points. we have powered one down for the time being but the situation hasn't changed.
2. The abosolute furtherest anyone is connecting from is a few metres, the APs display the same behaviour from any distance though.
3. This has been done, and it behaves in line with the other SSIDs
4. Should I call now?
Thanks
Ben
03-28-2011 03:28 AM
A support ticket definitely needs to be created for this issue. Your case may need to be escalated, there could be Beta firmware available for this device that could correct the problems that you are having with this device. If it is proven that the device is having hardware issue's than an RMA can be processed and a replacement will be issued to you as long as the device you have is under warranty.
Please call in for support when you have time.
Fredrick A Wofford
Network Support Engineer
Cisco Small Business Support
03-28-2011 03:30 AM
Thanks Frederick.
I've raised call #617270271
05-25-2011 06:56 AM
Hi Ben,
Please let me know if you have managed to resolve this issue. I am facing the same problem, I have two units (WAP4410N), one configured as the BASE STATION and the other as RELAY (WDS repeater mode). Both are running the same firmware (lates version updated from the website) and are using WPA-PSK/AES for WiFi security. The connection keeps droping after a few hours and then clients cannot connect to the access point. I have opened a case with CISCO (Case ID 617767151),and an engineer connected to the routers and re configured them after tweaking some settings, but the result was the same, it worked for a few hours and then stops working until the BASE and the RELAY stations are restarted. I'm really getting a lot of slack from the client due to this, any help will be greatly appreciated.
Thanks/Pete
05-25-2011 08:20 AM
Hi Pete,
What I got from the support call i raised was that this is an unofficially recognised issue, that cisco is in no hurry to fix. I had to ask a few times, but there is beta firmware (2.0.4.1), not avaialble on the site that the agent sent me, and installing that has appeared to fix this issue for us.
05-25-2011 08:56 AM
Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center. That is correct there is a beta firmware that fixes this issue. I am pulling your case and getting that escalated for you. I will email you as soon as that is done.
Eric Moyers
Cisco Network Support Engineer
1-866-606-1866
05-25-2011 09:08 AM
SIr, I have escalated your case. Someone should be in contact with you by email to get things started to get you the beta FW.
Eric
05-25-2011 09:44 AM
Hi Eric,
Thank you....
Dear Ben,
Thank you for your Input as well...
Regards,
Pete
05-30-2011 04:32 AM
I really have almost the same problem here
can any one help me to get the beta FW
05-31-2011 07:27 AM
I also have the same problem where the connection keeps dropping off and restarting only helps for some time. I cannot seem to find where I can raise a support ticket to get the beta firmware !?!?
Please can someone either send me the firmware 2.0.4 or tell me how I can get hold of support.
05-31-2011 07:43 AM
Jaffer,
Here is a contact list of support centers all around the world. Find the one that is local to where your at and give them a call and reference this community posting.
http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html
05-31-2011 09:21 AM
Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center. Anyone who is experiencing this issue with DHCP Dropping or Freezing with their WAP4410N and having to reboot the device to get it working again, should call their respective Cisco Support Center. You can find it by checking the link that Mr. Carr provided above. If after doing that you are still unable to get in touch with anyone, please come back here and post a message or contact me directly at emoyers @ cisco . com
I will be glad to help in anyway possible. But first try contacting the center directly. If they are unwilling to help you, please get a name and badge number and let me know.
Eric Moyers
Cisco Network Support Engineer
1-866-606-1866
06-01-2011 03:42 PM
***UPDATE***
Engineering is anticipating the public release of WAP4410N firmware v 2.0.4.2 within the next seven weeks (sooner if possible). It's currently undergoing system test and all signs are positive so far.
SPECIAL THANKS to all of you who helped out with the Beta Firmware. Your feedback is invaluable to us. (And if you're a Beta Firmware recipient who hasn't yet sent feedback, consider this your gentle reminder.)
Thanks to Eric and the Small Business Support Team for all of their help. They are committed (as are we) to providing the best possible products and support for our Small Business customers.
Stay tuned. We'll announce the firmware release in the community.
Thanks again,
Stephanie Reaves
Cisco Small Business Technology Group
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide