Skip to main content
commvault.com commvault.com
Solved

Cluster Instance Remote nodes update failed, Error during...

S
Bit
Forum|alt.badge.img+2

Hi, 

 

Does anyone has seen/been able to solve the following error. 

Reason: <There was error during initialization of information from input XML / local registry.>

 

I have a cluster instance with 2 nodes. 

The nodes are online and i can make a back-up of the file system. 

But the Cluster Instance can't update/connect to nodes somehow. (add nodes to cluster in CommVault). 

This is the error i am getting so far. 

I deleted the nodes in the cluster instance and force sync, then added and force sync, still the same error remains as it is. 

 

 

Best answer by sakuragi

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, 

View original
Did this answer your question?
If you have a question or comment, please create a topic

S
Vaulter
Forum|alt.badge.img+14

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.

S
Bit
Forum|alt.badge.img+2
Scott Reynolds wrote:

Hello @sakuragi 

Can you make sure that the hostname you are entering into the cluster client itself if resolvable from the Commserve/client machines?

Yes it is possible. I can ping/resolve/back-up both Nodes of the instance. 

The Instance is also ready, when checked readiness. 

The Instance is also resolvable. 

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.

We only use hostnames. But the hostname + ip is resolvable from the CommVault CommCell server. 

Somehow it stucks at 5% with Network error. 

Failed to start phase [Scan] on [P-CL52-R1] due to network error [Remote machine [​​​​​​​P-CL52-R1.xxxx]. The socket connect failed. Error returned [-1=CON523133/​​​​​​​P-CL52-R1.xxxxxx*​​​​​​​P-CL52-R1*8400*8402: Failed to find tunnel for sv1501167=>​​​​​​​P-CL52-R1:8400/8400]. Check Network Connectivity.]. Will attempt to restart. Please check if this product's services are running on the remote host.

 

S
Vaulter
Forum|alt.badge.img+14

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:

https://community.commvault.com/tech-blogs-commvault-39/check-readiness-failing-here-is-how-to-troubleshoot-1015

 

S
Bit
Forum|alt.badge.img+2

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, 

Mike Struening
Vaulter
Forum|alt.badge.img+23

Appreciate you sharing back with everyone!

https://www.linkedin.com/in/michael-struening

Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings