is there an option, which keeps my cAP’s working, if they loose the connection to the CAPSMAN server for a short time?
They are configured for a local breakout (“Local Forwarding”), they do NOT send everything to the CAPSMAN. But if they loose the connection the CAPSMAN for a few seconds, they stop broadcasting their SSIDs.
Obviously you must leave the wlan well configured before join the wlan to capsman.
Simply use netwatch, when capsman do no reply, disable with script the cap on wlan interface (and the predefined configuration is run).
When capsman return, enable again cap on wlan by script and wi-fi go back to work by capsman.
There is no option to keep the devices in operation, unlike every other vendors WAPs?
OK, thats a point, I would advise every customer againts Mikrotik regarding WAPs. But on the other hand, that stuff is really CHEAPO and maybe, thats a point the cheapo stuff falls behind…
I hope you can see my point. In large deployments, with 400, 500, 600 or more WAPs, you update the CAPSMAN for new ROS and boom, a few thousand clients offline?! GOOD JOB MT
And in any case, I doubt the seriousness of someone who controls more than 50 access points from one single point,
without any form of failover, and without split the network on segments, regardless of the manufacturer and the software used.
It’s actually the power of capsman.
You add a cap without any form of config, just caps mode et voila, it will get config and it will participate in the network.
It can also be seen as a security measure.
I would not like to see such a number of aps to be operating if the controller is down.
And it will be a hell of a trigger to get it resolved asap
There is no automated way integrated that will sync capsman config between devices. You could script syncing changes or use the rest api to make changes on multiple servers at the same time.
You don’t use Mikrotik radios for their performance serving clients.
Dropping when they can’t reach the manager… Shouldn’t even be a concern.
And like others stated… You can setup another Mikrotik to be the back up manager. When a unit looses connection to the primary it will go looking for the backup.
As for syncing them… What really changes on caps-man ON IT’S OWN? The config tends to be pretty static once you set it up properly. Copy and paste the config into the back up and let it run.