08-20-2013 09:52 AM
We have a cluster at a school campus that has a access point that won't give up being VC.
If we unplug it users can no longer connect to the network even though the APs are still up and broadcasting.
Eventually another AP becomes the VC and user can connect.
If we plug the original AP it takes over as VC again.
This should not happen. The new VC should stay the VC unless is
08-20-2013 12:26 PM
Take that VC and factory default it (paper clip reset button on bottom of AP). Then re-connect it to the cluster.
Consulting Systems Engineer - ACCX, ACDX, ACMX
If you found my post helpful, please give kudos
08-20-2013 10:50 PM
-What model AP is this?
-What version of SW?
-Any chance that you are connecting to a downlink port (E1,E2,E3,E4) rather than the uplink port (E0). If you were connecting to a downlink port this is expected behavior as an IAP with multiple ports has a higher VC priority and if connected to a downlink port the group assumes the IAP with the downlink port connected is the gateway.
-Can you get the console output from this AP when powering up? Do you see anything interesting like the following:
OOPS. someone else thinks hes the master too
I am MASTER. recv-ed a master normal-beacon.
(00:01:50) !!! Win the master election
Sorry....................more questions than answers .
08-21-2013 07:11 AM
Well, my theory does not apply given that this is a 105.
If you can, capture the console output of this IAP on bootup, the output of show-tech, then open a case with TAC for debugging.
It isn't running in "Standalone Mode" is it?
08-21-2013 09:07 AM
We downgraded yesterday and pulled the plug on the VC this morning. Another VC was elected. We plugged in the AP and it did not become the VC.
Go to 3.4 do the exact same thing and the AP always stays the VC. Users can't even connect anymore when the VC is unplugged.
Roll back to 3.3 and we're good.
Don't know if anyone else is experiencing this, but seems pretty conclusive.