Open internet explorer on the proxy used for the backup and open the vcenter 10.11.25.110 and then try to login. Easy way to test credentials and ports from the proxy.
Hi @Eldan,
It looks like the MA “ilbevcvma03” isn’t getting any response from the vCenter:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
Can you login the vCenter Web Console from this MA in IE/Browser?
Is there any Windows FW Enabled or Firewall in between MA and VC?
You could run this CVPing (Basically telnet) from Base folder on the MA to test connectivity: Cvping <vcenterIP> -port 443
Best Regards,
Michael
Hello @Eldan,
To add to the other responses, please ensure that the port requirements are met as per documentation:
Port Requirements
In an environment with firewalls, the vCenter, ESX servers, and Virtual Server Agent must be able to communicate with each other. To ensure that all components can communicate through the firewall, ensure that the ports for web services (default: 443) and TCP/IP (default: 902) are opened for bidirectional communication on each of these machines.
Additional port requirements can apply for the MediaAgent when you use specific features such as Live Browse, Live File Recovery, and Live Mount. For more information, see Entering Required Firewall Settings.
Prior to performing any backup or restore operations, ensure that the following port requirements are met.
Note: If a non-default port is used with VDDK 5.5, backup or restore operations can fail. See KB Article VMW0013.
vCenter
- Port for web service (default: 443) must be opened. If vCenter is configured to use non-default ports, the non-default ports must also be opened.
ESX Server
- Ports for web service (default: 443) and TCP/IP (default: 902) must be opened for the vStorage APIs for Data Protection.
https://documentation.commvault.com/commvault/v11/article?p=3368.htm
Regards,
Dan
Hey @Eldan , hope all is well! Have you had a chance to run through these suggestions? If one of them worked out for you, feel free to mark it as the Best Answer.
Thanks!
Thanks guys, it was a firewall problem after all :)
Glad to hear you got it resolved!!