Solved

Network issue after upgrade to 11SP24


Userlevel 3
Badge +12

Hi All,

 

After upgrading the CommServe from 11SP16 to SP24 with a hardware refresh, we are facing some network issues, where the communication is failing between the CommServe and the clients. Anyone has any idea about the reason why this is happening ?

 

Regards.

icon

Best answer by Commvault Engineer 8 May 2022, 09:10

View original

If you have a question or comment, please create a topic

13 replies

Userlevel 6
Badge +15

Good morning.  Can you please share the error that you are seeing?  Does check readiness pass or fail?

Userlevel 3
Badge +10

For what it is worth…..  I’ve done such an upgrade a few months back and didn’t notice any issues in regards to networking…  (Updated a Commcell with approx 4000 clients of all sorts) 

 

/RubeckDK

Userlevel 3
Badge +12

Good morning.  Can you please share the error that you are seeing?  Does check readiness pass or fail?

When we run the CheckReadiness report, it fails.

The jobs stay in pending status, with an error code of 19:1131 (Unable to reach <client name> Please confirm the serve is up and running, then check Network connectivity between Commserve and the remote computer).

 

BR

Userlevel 3
Badge +12

Good morning.  Can you please share the error that you are seeing?  Does check readiness pass or fail?

When we run the CheckReadiness report, it fails.

The jobs stay in pending status, with an error code of 19:1131 (Unable to reach <client name> Please confirm the serve is up and running, then check Network connectivity between Commserve and the remote computer).

 

BR

One of the events it is showing : Failed to start phase [Scan] on [Client_name] due to network error [Remote machine [IP address]. The socket connect failed. Error returned [-1=Connect to IP address:8400/8400 failed: Failed to find tunnel to Client]. Check network Connectivity.]. Will attempt to restart. Please check if this product’s services are running on the remote host. 

Userlevel 3
Badge +12

Just to update, the clients that are facing the issue, are clients which are on Commvault version 10.

Userlevel 6
Badge +15

This very well could be the change that added the network daemon to clients which would have been in one of the service packs that you updated to.  Can you restart Commvault services on the v10 client and then attempt a check readiness and provide the results?

Userlevel 3
Badge +12

This very well could be the change that added the network daemon to clients which would have been in one of the service packs that you updated to.  Can you restart Commvault services on the v10 client and then attempt a check readiness and provide the results?

Hi @Orazan,

 

Thanks a lot for your time and efforts.

Actually, we cannot even restart the services, with the following error “Failed to send service control request to client [Client_name]”. It seems like there is no more communication between the CS and the v10 Clients.

 

Even when restarting the services from the client (Not from the CS), still same issue.

 

Thanks again.

Userlevel 6
Badge +13

What OS are these clients running that they are still on v10? 

Userlevel 3
Badge +12

What OS are these clients running that they are still on v10? 

All clients are mostly on Linux 2.6.32.xxx

Userlevel 3
Badge +5

You might have run into this issue:

Jobs Don't Run on V10/V11 Client at SP14 or Earlier Service Pack

If you install a new MediaAgent with 11.22 or a later feature release, and if you have an existing V10/V11 client at SP14 or earlier service pack that connects to that MediaAgent, no jobs will run on that client.

To fix the issue, on the newly installed MediaAgent, set the nCLNT_FORCE_TUNNEL additional setting to 0. For more information, see Enforcing Automatic Tunneling for Network Traffic.

Source: https://documentation.commvault.com/11.24/expert/7553_troubleshooting.html

Userlevel 3
Badge +12

You might have run into this issue:

Jobs Don't Run on V10/V11 Client at SP14 or Earlier Service Pack

If you install a new MediaAgent with 11.22 or a later feature release, and if you have an existing V10/V11 client at SP14 or earlier service pack that connects to that MediaAgent, no jobs will run on that client.

To fix the issue, on the newly installed MediaAgent, set the nCLNT_FORCE_TUNNEL additional setting to 0. For more information, see Enforcing Automatic Tunneling for Network Traffic.

Source: https://documentation.commvault.com/11.24/expert/7553_troubleshooting.html

Hi Steven,

 

Thanks for your response, unfortunately, we already tried it, but it didn’t fix it, as of what I believe, the clients on v10 are using ports 8400 to 8402 but the CS is using 8403, and that’s what is causing the issue.

Userlevel 3
Badge +12

Hello Guys,

 

Just to update on this, and help others which will maybe face the same issue regarding v10 clients.

We had a fix from the support, setting up a One-Way Direct Connection between the CommServe and the concerned clients, which lost connectivity to the CommServe after upgrading it from 11FR16 to 11FR24, after that, the connection was established again.

 

 

Userlevel 6
Badge +15

Thank you for the update.  I am glad you were able to get this resolved.