07-22-2014 09:57 AM
I have a couple of WAP 321's using running 1.0.4.4. There are 3 SSID/VLAN networks that are functionally fine - a business use network on vap0, a guest network on vap1, and a third network for employee use during breaks on vap2. The employee break network (vap2) has an associated schedule and work as expected.
The annoyance is that when the scheduled time for vap2 arrives (either on or off time), it causes a temporary interruption of the other 2 [unscheduled] networks. It only lasts for less than a minute, but during that time wireless clients on the other vap's are disconnected.
Solved! Go to Solution.
07-23-2014 08:49 AM
My name is Eric Moyers. I am one of the Wireless Subject Matter Experts for Cisco's Small Business Support Center.
I am sorry that you are having this issue with our product.
I have set you particular scenario up several times, but have not seen that issue before. But to be honest, I have not actually been looking for it. I am going to try and set this up in my lab and see if I can recreate it.
Eric Moyers
.:|:.:|:. CISCO | Eric Moyers | Cisco Technical Support |
Wireless and Surveillance Subject Matter Expert
Please rate helpful Posts and Let others know when your Question has been answered
You can click my name beside the picture if you need to email me directly
07-23-2014 08:49 AM
My name is Eric Moyers. I am one of the Wireless Subject Matter Experts for Cisco's Small Business Support Center.
I am sorry that you are having this issue with our product.
I have set you particular scenario up several times, but have not seen that issue before. But to be honest, I have not actually been looking for it. I am going to try and set this up in my lab and see if I can recreate it.
Eric Moyers
.:|:.:|:. CISCO | Eric Moyers | Cisco Technical Support |
Wireless and Surveillance Subject Matter Expert
Please rate helpful Posts and Let others know when your Question has been answered
You can click my name beside the picture if you need to email me directly
07-24-2014 05:53 AM
Hi Eric,
The 2 AP's are in a cluster. I know this event occurs with the 'near' AP that I am always connected to.
I have not yet gone far enough out in the back area of the facility to confirm that the event also occurs when connected to the 'far' AP
07-25-2014 04:33 AM
OK, I have now taken the time to test out in the back area an know that I am connected to the 'far' AP and the same event occurs.
11-20-2014 10:27 AM
The problem still exists with firmware 1.0.5.3
Will there ever be a resolution or should I start shopping for new access points?
08-26-2015 01:49 PM
Bug CSCuv95869
09-16-2015 10:24 AM
For the sake of finishing this off in case anyone finds this topic in the future...
Unfortunately, the official response is that this behavior cannot (and will not) be changed on this platform. The AP has to reset when the schedule time occurs. The documentation will be updated in some way to reflect this.
08-07-2014 06:11 AM
Bump..
Eric, has there been any further research into this issue?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: