Client connectivity status not ready for MediaAgent

Hi Mahendra, 

Please confirm with you network team if there are any firewall rules and check what rules for the Commvault firewall are in place. 

Please read through this documentation on port requirements for Commvault and confirm they are open 

https://documentation.commvault.com/commvault/v11_sp20/article?p=7102_1.htm

https://documentation.commvault.com/commvault/v11_sp20/article?p=8572.htm

Please test the communication on the ports from the commserve to the media agent and then back from the media agent to the commserve.

Check the network connectivity between CommServe and the client computer.

• Login into client computer.
• Navigate to /opt/ContentStore/Base
• Run the following command:

  # ./cvping CommServe_host_nameport_number

On the commserve run cvping from an admin command line. 

You can review the cvfwd.log for the communication errors if any. 

Hi @Mahendra Kurniawan 

Thanks for the question and welcome to the Community.

There’s a few things you can check:

1. Services are running on the client, MA, etc.
2. Default communications are over tcp ports 8400-8403 - is there a firewall between the clients? Check CommCell Network Requirements
3. If there is a firewall and network communications is restricted, perhaps try setting up Network Routes using Direct Connections. Tunnel port 8403 is used by default to route all traffic between client/MA and client/CS - please ensure firewall rules are configured to allow port 8403.
4. Ensure each client/MA/CS can resolve names of the other clients, check the names used in setup are resolvable by all machines.

Thanks,

Stuart

Hi all,

Thanks for prompt response.. 

Yes, I have already check those probability and do troubleshooting step as:

1. Checking if there is no firewall installed in the network.. Commserve have connected to another media agent with same configuration but they can running normally. Also, I have Virtual Server Agent in same host, it’s working fine, no problem with readiness

2. Do ping and cvping from commserve to Media Agent → they are:
   Ping to port 8400 & 8403 OK
   Ping to port 8401 & 8402 NOK
   I do with other Media agent it give same condition, they don’t have issue with readiness
3. Client/MA/CS can resolve names of the other clients
4. Services → compared with normal media agent it’s same
5. Commvault list, commserve name can’t be fetch from commserve:
   
   Problematic MA:
   e General ]
    Version = 11.20.9
    Media Revision = 798
    CommServe Host Name = @@COMMSERVE@@
    CommServe Client Name = @@COMMSERVE@@
    Home Directory = /opt/commvault/Base
    Log Directory = /var/log/commvault/Log_Files
   
   Normal MA:
   b General ]
    Version = 11.20.9
    Media Revision = 798
    CommServe Host Name = CVLT-MDN-CSPROD
    CommServe Client Name = cvlt-mdn-csprod
    Home Directory = /opt/commvault/Base
    Log Directory = /var/log/commvault/Log_Files

Thanks

Mahe

Hi @Mahendra Kurniawan 

Thanks for the extra detail, it looks like the MA has failed to register correctly and has the Commserve placeholder instead of the actual name - there is a known issue with this in SP20.

Please apply the latest Maintenance Release and the MA should then register successfully.

Hotfix 2195 is provided in MR12 for SP20 with these details:
HotFix: 2195 
Issue: v11 sp20 custom package decoupled install setting CS hostname as @@COMMSERVE@@ 

Thanks,

Stuart

Hi All,

Thank you for the response, gather many knowledge here

This problem have been resolved, it’s my mistake since I input duplicate VSA and MA IP address in local DNS in windows hosts (Commserve)

Thank you

BR,

Mahe 

Hi Mahe

Thanks for the response, I’m glad you got that fixed!

I’ll go ahead and mark your latest update as Best answer.

Thanks,

Stuart