Good day. Just a brief post on something we ran into while setting up Omada SDN in a Hot-Standby Backup configuration.

Installed SDN 6.1.0.19 on two nodes: One directly into the OS on a Dell 9020 and the second in a Proxmox VM on a Dell R420. Both up to date on Debian trixie/Pmox 9.1.5.

Initially had trouble getting the nodes to sync and if one rebooted we had to start/stop mongod and tpeap repeatedly to get the nodes to resync.

Finally identified this file: /opt/tplink/EAPController/data/cluster/omada_hsb_cluster.properties which had the following contents:

## local cluster config
# Cluster mode, hsb: Hot-Standby Backup
omada.cluster.mode=hsb

## Hot-Standby Backup Config
## Please edit:
omada.cluster.hsb.primary.host=192.168.0.100
omada.cluster.hsb.primary.device.host=

omada.cluster.hsb.secondary.host=192.168.0.101
omada.cluster.hsb.secondary.device.host=

omada.cluster.hsb.key=tplink123

We updated the IP addresses and Cluster Key in this file on both nodes, rebooted both and have not had to struggle to get them resynced since making that change. 

There is also a file for the full 3-node+ cluster approach in the same folder - omada_distributed_internal_mongo_cluster.properties.

Apologies in advance if this is something we missed in the install, setup or documentation, or if we are simply in error re: the purpose of the file(s).

Thanks,

Carl