EAP225outdoor wireless mesh disconnected/not even visible/adopt failed
Hi,
my new toys (see pic) bring me some unexpected headache.
first the EAP225 was visible and adopted without any issue. later they connected in strange ways... in a chain or all to one of the wired EAPs even it there is a other EAP more near and with better signal.
now they refuse to stay connected of the adopt even works most of the time it fails.
rebooting/powercycling (also the OC200 and the wired EAPs) and also factory resetting the 225's don't change anything
now i moved them back in and put them within 1m of the wired EAPs and they still don't work ... whole setup is only a few weeks old
did i miss some incompatibility with this devices?
Is there something wrong with this setup expect the wrong brand switch :) I wrote already a letter to Santa about a correctly branded switch :)
Regards
ASD
It is good that you locked the channels for the root APs, ideally to channels which allow for maximum output power in your region. This helps when there is a minor glitch on the root AP, when it comes back it comes back on the same channel and the mesh APs will lock on more quickly. There is a WLAN page in Wikipedia that will help you out...for instance, in the great white north, Channels 149+ provide the best performance for me. You also want to leave a gap so that your uplink channels can move 20/40/80Mhz without stomping all over each other (though my advice is to fix them at 40Mhz if your RF environment can sustain that).
Next up you should set the 'Preferred Uplink' for each of the child/meshed APs. The reason for this, especially in your case where your root APs are different hardware models, is that you want the mesh to be deterministic and not random based on the timing of different APs coming online after a power outage or other system-wide event.
You should be good to go...I've been running outdoor meshed 225's for years now and they've been truly solid.