Hi.
I would like to know if is possible to make change in CAPsMAN configuration without global disconnect and reconnect of client devices - is that possible ?
For example I have two networks with two SSIDs WIFI1 and WIFI2.
When I change settings like a password or other for WIFI1 then after changes CAPsMAN disconnects all devices from both configurations.
Is possible to make changes of 1 configuration (WIFI1) without any impact on other configurations (WIFI2) ?
This function is quite important because in situation when there is some large conference on one network and I change settings on another network, that conference is suddenly stopped and it causes problems with devices, which needs to connect again...
It is very annoying and some customers are very sensitive in today's world where all is dependent on internet and wireless networks.
Could somebody answer this or is there any solution which could MikroTik CAPsMAN handle to solve this ?

I guess ... it depends *) ... an authentication related config change 'must' disconnect all clients for security reasons ... or the state attorney is riding into the stetl.
... changing the vlan-tag in the datapath ... 'would' not require such harsh measures ( in my [not-so-deep-tech-insight] opinion )
True is ... it would be very interesting to know, which parameter-change would disconnect the clients or even would need a whole re-provision of the radios (managed APs).
To use the *) -term again it will also depend on the software-version and the hardware-version of the radios that are in use.
With ~|> v7.12 and ax-radios it's possible to rollout "different" configurations to sets of AP-groups (maybe thats true for more historical software-versions and hardware too).
That looks very mature and reasonable. Testing of a new config could then be done in a building with a more appreciative audience ... without causing major rebellion of the whole shebang.
Unfortunately I own only one cAP AX for my both ambitious as well as fruitless experiments to solve ... this/these question(s).
The community ( or me winning the lottery : ) ... will jump in here ... veery sooon !
: )
.
*) sorry for using the term ... but it's an industry standard by now ... ¯\_(ツ)_/¯

When I disable 5ghz provisioning rule - even 2ghz radio go down for the period of provisioning.

which capsman-version ? ... reviewing the config-options for wave2 it seems possible to provision CAPs in groups and even per radio ?
. .
guess something like a best practice-guide would be nice. channel-management, CHR vs. box ... dangerous NoNo's ... and what not.
So it seems to better start small with a first project (even a lottery generated).

Re wave2 capsman: be careful with that 00:00:00:00:00:00 wildcard.
Doesn't work there. Needs to be blank.

not to much to worry ... my testbed is pretty overseeable in the moment.
tried to convince some people to replace a 120-dual-radio installation, vendor-EOL'ed with cAPGi-5HaxD2HaxD (which is a [the first] competitive MT-enterprise-ap in my opinion).
when they asked: "is this a referenced solution", I said yes ... but they found my testbed ... a little bit too fluffy ... and yes ... they had a point.
in terms of performance, aaa, client-handling etc. I see no problems. but scaling the handling from one to 120 is another ballpark.
so I'm trying to collect information for my next approach.
.

Not 120 but more then 1

: )
indeed ... and on a scale from 1 ... 10 ... how does it feel ? ... (10 would be ... phantastical, I would never buy something else again) ...

Well, I honestly rarely look at it so I can't really tell how it feels.
It is running since August last year with close to zero maintenance, apart from some version upgrades.

Maybe not sexy enough ?

<< close to zero maintenance >> ... is always worth ... an 8 ... at least : )

: )
... and - clearly - a withered 'one' from Hank ...
high bandwidth ... of valuations ... so far

Not 120 but more then 1

.
one more thing ... capsmanv2 is running on one of the cAPGi's ? ... or CHR ... or ?

Rb5009