Hi, if you erase the cluster - related config in all cluster units (supposedly you have 2), that should do the trick. Safest way is to delete it from existing startup-config and reload the "clean" one again. If your WLANs are locally bridged (always ...
Also note, that when upgrading RFS4k from 4.2.1, you need to go through 4.3I remember, there was quite a mess around 5.2.x versions, as they did follow multiple paths of functionality upgrades. (Read release notes for 5.4, as this was a consolidating...
I suppose, you are using Layer 2 (MAC) adoption (MINT Level 1) together with tunelling. In such a scenario, besides all the traffic going through an RFS (bottleneck), the RFS is also doing the RF-Domain manager (it usually takes over, once it is in t...
That's not true...Within WING5 you can have more RFS within 1 cluster. (6 units since FW v 5.6.x) We still have installations with 3 units, for example. With legacy WING 3 - this limit was 12 units, then, perhaps with some earlier WING 5 versions, th...
Here you can download some of the FW for RFS4000. RFS4000Although, I would strongly recommned to use a more recent version than 5.8.1 (at least 5.8.6.7, which addressed the Krack vulnerability, better 5.9.1.11 - last one to support the broadest range...
