The goal is for users and higher-level tools to be able to test a new remote node before adding it to the cluster. Currently we just recommend using "ssh -p 3121". The new option would attempt a remote connection and display any problems with keys, certificates, network, firewall, etc. We probably want a failsafe to avoid attempting a connection to a remote that is already connected to the cluster (maybe this could be a new connection XML attribute saying "do not drop existing connections" though it would be ignored by older remotes).