Often we see cases where Check Readiness is failing or backups failing due to communication issues. Whether these clients be Media Agents, VSA Proxies, Exchange servers or Linux FS.
This article will cover common issues that, we, as support frequently come across in tickets that are raised.
Check readiness is a simple tool that can be run from the CommCell or Command Center that does a network check to ensure that the Commvault Ports are opened and listening.
The first things we want to check:
- Are Commvault services running on client?
- Is DNS resolving?
- Are the required ports opened?
- Is Windows firewall enabled?
First, we want to check to see if the Commvault Services are running on the client. Without the services running, check readiness will fail by default because there is no service/process running that will be listening.
- Windows File System: Open "Commvault Process Manager" and go to the "Services" tab. Here you will see a green play button if they are running.
- Linux File System: type "Commvault List"
Next, now that we have verified services are running, we want to ensure that the Commserver is able to resolve the short and long name of the client through DNS.
- On the Commserver, open up CMD. Type in the command "nslookup servername.fqdn" and for the short name "nslookup servername". Verify that the correct IP address is showing for this client. If the client has multiple NICS/IP addresses, you may need to configure Data Interface Pairs.
How to verify that the required ports are opened:
- Commvault has a tool built into any install called "CVPing". This is basically the same tool that windows has called "Telnet"
- On the Commserve, Open up the CMD window in the Commvault Base directory "Typically C:\Program Files\Commvault\Contentstore\Base". This directory can be different based on the drive the software is installed on.
- Type the command "cvping servername.fqdn -port 8400", "cvping servername.fqdn -port 8401" and "cvping servername.fqdn -port 8403". If this is successful, then we know that the ports are opened. If one of them fails, you will need to discuss this with your network team and show them the failure as proof the port is not opened.
- The same tool can be run on the client by replacing the "Servername" with the Commserver and Media Agent hostnames to verify connectivity all around!
Lastly, if Windows Firewall is being used on any Commservers, Clients or Media Agents than we can use the AddFWExclusions.bat script to automatically add the exclusions!
