Installer logs pointing the problem with ping/ssh.
PING 192.168.10.211 (192.168.10.211) 56(84) bytes of data.
0 18:50:53 cmd exit=0 (duration: 10.01 seconds)
0 18:50:53 cmd /sbin/ip -o addr show 2>/dev/null | /bin/grep 'inet 192.168.10.211/'
0 18:50:53 cmd exit=1 (duration: 0.01 seconds)
0 18:50:53 cmd LC_ALL=C LANG=C /usr/bin/ssh -x -o NumberOfPasswordPrompts=0 -o StrictHostKeyChecking=no root@192.168.10.211 echo 2>&1
0 19:02:22 CPI WARNING V-9-20-1183 Interrupt Received--installer terminated
--- 192.168.xx.xxx ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
SSH/ICMP blocked between the CPS client and Server.
Installer during CPS client configuration automates the process of generating the keys/certificates for communication between CP Server and clients. It takes care of copying the certificates to the right location. Along with this, it also creates/updates CPS database with this new cluster details like cluster name, cluster UUID, Nodes and users details.
To do all this work without manual intervention, it requires passwordless SSH communication and ICMP enabled.
Once the CPS is configured, Port 443 is sufficient to handle the fencing until unless any additional nodes or CPS changes required. Veritas recommendation is to use the installer to do the automated configuration.
In case of no possibility to enable the ports/ICMP, below are the Infoscale documents to do the manual procedure.
Generating the client key and certificates manually for the clients:
https://www.veritas.com/content/support/en_US/doc/79757062-141543634-0/v90036434-141543634
To add cluster/nodes manually:
https://www.veritas.com/content/support/en_US/doc/79630152-141543514-0/v30144320-141543514
Note : This is applicable for all environments including Cloud environments.