@Vincent-TP 

In my opinion, all devices operating under Omada Controller (OC) should be fully supported. Currently, I manage around 70 devices – ranging from EAP access points to routers and switches. At this scale, it clearly calls for proper protection of the environment in case of a failure.

At the moment, one of the problematic devices is the EAP115 (EU), of which I only have a single unit. This device also has firmware-related issues.

To better manage and control this environment, I would like to suggest the following improvements:

1. Update the website and the list of supported products
   https://www.omadanetworks.com/pl/omada-cluster-deployment/product-list/

2. Add a tool to verify device compatibility with the cluster
   Before enabling the cluster, the system should verify whether all managed devices are compatible with the cluster feature.

3. Provide a detailed procedure for disabling the cluster
   The website states that devices will revert to factory settings after disabling the cluster. However, I have not tested this in practice and am unsure whether it is worth disabling the cluster.
   The key question is: if I create a backup of a running OC within a cluster, will that backup work correctly after the cluster is disabled and restored on a standalone controller?

4. Clarify NAT configuration for a remote OC location
   I have devices located in a different site than the Omada Controller. The question is whether, in the NAT configuration, in addition to the IP address of OC1, the IP address of OC2 should also be added.