Knowledge Base
Searching in : Article
ID: AR11L00826
Applies to: NoMachine Server
Added on: 2014-11-25
Last Update: 2017-11-07

When to synchronize the failover cluster configuration (v. 5)

This article applies to Enterprise Server and Cloud Server installations with the failover cluster service enabled.

When the failover cluster is active (high-availability), there are some particular cases which require updating the cluster configuration to synchronize the master and secondary server.

Updating the cluster servers is necessary when:

a) The nodes database (/usr/NX/etc/nodes.db) has been changed, e.g. one or more nodes have been added or removed.

b) The host certificate has been changed on one or more remote nodes. This happens when the NoMachine software has been re-installed on the remote node.

c) A new key pair to access remote nodes has been generated according to instructions available here:

for v. 5   https://www.nomachine.com/DT09M00103#4

for v. 4    https://www.nomachine.com/DT04L00069#4

      
d) A new key pair to access cluster hosts has been generated according to instructions available here:

for v. 5   https://www.nomachine.com/DT09M00103#5

for v. 4   https://www.nomachine.com/DT04L00069#5


    
To update the cluster configuration, run on the cluster master server or on the secondary server the following command:

nxserver --clusterupdate

  

References

NoMachine Enterprise Products 5.x - Server Administrator's Guide - Advanced Functions

https://www.nomachine.com/DT07M00091

NoMachine Enterprise Products 4.x - Server Administrator's Guide - Advanced Functions

https://www.nomachine.com/DT09K00058

Information about keys and certificates used by NoMachine:

https://www.nomachine.com/AR04K00665