I have an issue with client registration on SuMa3:
When host2 is registered (pull) the existing host1 gets kicked out of SuMa and vice versa.
Reproducible: always
Both systems are part of an OES11 SP2 NCS 2-node cluster. Several other 2-node clusters of the same type have been registered successfully without problems.
Both affected systems are VMware guests, and they show up in SuMa with unique UUIDs and System IDs. There are no apparent DNS lookup issues - forward and reverse lookup work fine from the clients as well as from the SuMa server.

Weird phenomenon. Any hint appreciated.