Avamar : échec du PDM avec une erreur lors du déploiement du proxy

Le déploiement des proxys à l’aide de Proxy Deployment Manager échoue avec le message Erreur lors du déploiement du proxy.

Par exemple :

Avamar Utility Node ne peut pas communiquer avec l’hôte ESX sur le port 443 lors du déploiement du proxy.

À partir de l' deploymanager.log (dans /data01/avamar/var/log/vcs/ /tmp/proxydeploy/vcs/_

2016-05-15T21:57:10.329-0700 TRACE [cTaskExecutor-4][ impl.ConnectionManagerService# closeTicket]: Closing connection manager ticket: ...6c4657958ef8
2016-05-15T21:57:12.503-0700 TRACE [Thread-22 ][ util.VcConnection# keepAlive]: Keep-aliving VC session
2016-05-15T21:57:12.504-0700 TRACE [Thread-22 ][ impl.ConnectionManagerService# sendKeepAlive]: Keep-alive connection manager session: ...0de2820e9fc9
2016-05-15T21:57:12.611-0700 DEBUG [Thread-23 ][ worker.TaskWorker# updateProgress]: Updating task progress: 0
2016-05-15T21:57:12.616-0700 DEBUG [Thread-23 ][ events.VCSEvent# send]: Sending event: template: org.springframework.amqp.rabbit.core.RabbitTemplate@59074829 com.emc.avamar.vmware.vcs.deploymanager.deploy.status_event: com.emc.avamar.vmware.events.VCSEvent@2bf66009
2016-05-15T21:57:13.559-0700 ERROR [pool-8-thread-2][ worker.DeployWorker# run]: Error deploying proxy
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
at sun.security.ssl.BaseSSLSocketImpl.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
at com.emc.avamar.vmware.deploymanager.worker.DeployWorker.uploadVmdkFile(DeployWorker.java:917)
at com.emc.avamar.vmware.deploymanager.worker.DeployWorker.run(DeployWorker.java:340)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Autorisez la communication entre la grille Avamar et les hôtes ESXi sur le port 443, comme indiqué dans le guide de l’utilisateur d’Avamar for VMware :