Avamar: Proxy deployment manager fails to Deploy a new Proxy

Summary: Deployment reports "ERROR DEPLOYING PROXY;" registration fails with network timeout because port 5489 is blocked between the utility node and the proxy.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

  • Proxy deployment manager failed to deploy a new proxy in the registration step showing "ERROR DEPLOYING PROXY" error message.
  • The proxy was deployed successfully but destroyed as the registration step to Avamar has failed.
    • When checking the Proxy deployment logs in the below path
/usr/local/avamar/var/log/vcs/deploymanager.log
  •  The logs show the following.
yyyy-mm-19Thh:mm:ss.682+0100 TRACE [Thread-24      ][             util.VcConnection#        keepAlive]: Keep-aliving VC session
yyyy-mm-19Thh:mm:ss.682+0100 TRACE [Thread-24      ][ impl.ConnectionManagerService#    sendKeepAlive]: Keep-alive connection manager session: ...2cc6b4c9b53d
yyyy-mm-19Thh:mm:ss.803+0100 DEBUG [ool-10-thread-5][       util.ProxyNetworkWaiter#mServiceReachable]: Failure (timed out)
yyyy-mm-19Thh:mm:ss.803+0100 WARN  [ool-10-thread-5][       util.ProxyNetworkWaiter#waitForNetworking]: Proxy CIM service is not reachable
yyyy-mm-19Thh:mm:ss.803+0100 ERROR [ool-10-thread-5][       util.ProxyNetworkWaiter#waitForNetworking]: Unable to establish connection to proxy.
yyyy-mm-19Thh:mm:ss+0100 WARN  [ool-10-thread-5][           worker.DeployWorker#              run]: Network timeout
yyyy-mm-19Thh:mm:ss.829+0100 DEBUG [ool-10-thread-5][             worker.TaskWorker#teTaskDescription]: Updating task description: 
yyyy-mm-19Thh:mm:ss.834+0100 INFO  [ool-10-thread-5][             worker.TaskWorker#    sendTaskError]: Sending fault com.emc.avamar.vmware.vcs.deploymanager.network_timeout_fault
yyyy-mm-19Thh:mm:ss.849+0100 INFO  [ool-10-thread-5][           worker.DeployWorker#              run]: Deploy of proxy <New_Proxy_Name> to host <ESX_FQN> was not successful. Cleaning up deploy artifacts...
yyyy-mm-19Thh:mm:ss.849+0100 DEBUG [ool-10-thread-5][             worker.TaskWorker#teTaskDescription]: Updating task description: Cleaning up after error...
	

Cause

  • The proxy is deployed successfully but fails in the registration step and reports waiting for the network in the progress status before failing.
  • Seems that the port 5489 is disabled between the Avamar Utility Node and the proxy as this port is important for the registration process (Virtual Appliance Management Interface process).

Resolution

Enable port #5489 in the direction from Utility node to Proxy and that should solve the issue.

Additional Information

See the following link below to find a list of required data ports for Dell Avamar integration with VMware. (Page 125) 

Dell Avamar for VMware19.12 User Guide

Affected Products

Avamar

Products

Avamar
Article Properties
Article Number: 000054716
Article Type: Solution
Last Modified: 20 Nov 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.