Hello @sakuragi
Can you make sure that the hostname you are entering into the cluster client itself if resolvable from the Commserve/client machines?
While the nodes could be reachable all clients and CS must be able to resolve that cluster name and/or IP that is entered in hostname section.
This might be the way the cluster was configured. Are you sure you are using the application name not the cluster name? In cluster admin there is the cluster at the top then there are applications. The application is where the unique name/IP, etc lives not in the root.
Also do you know if there are any firewalls, etc?
You can test using cvping command line. There is a writeup on that here:
Hi,
The problem was not firewall related.
Like i wrote before, that was all done.
Had a service request created at CommVault.
They came with same answer. DNS/Firewall related. Because, the cluster instance (in CommVault) could not connect to the client.
The cause and solution was not that hard to find out.
The Cluster instance had been configured in CommVault, before the firewall issue was solved. So, CommVault somehow was still giving an error, related to firewall DNS (could not connect to client/cluster instance). Even when the connection issue was solved.
Solution, delete cluster instance in CommVault, reconfigure it (add new again).
Tadaa.
I had seen this same problem solution before. But could not think, this could be the reason again. And CommVault was like, no no its dns/firewall related. So. Next time, delete and add again, just in case.
Thanks for help so far. Hope this can help someone later on.
Kind regards,
Appreciate you sharing back with everyone!