PowerProtect: No se puede implementar el motor de protección de VM Direct debido a una falla de inicialización
Summary: La implementación del motor de Virtual Machine (VM) Direct no se puede inicializar y se muestra el mensaje No se puede conectar al vProxy externo a través del puerto 9090.
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
El dispositivo PowerProtect Data Manager se utiliza para proteger el entorno de vSphere con la solución VM Direct Engine. La implementación del motor de VM Direct en un clúster de zona desmilitarizada (DMZ) falla durante la fase de inicialización. El estado del trabajo del sistema muestra lo siguiente:
ProxySession unsuccessful during initialization. Unable to deploy and verify the vProxy my-proxy.my-domain.com. Unable to query vProxy status after 'Deploy'. Request unsuccessful. Unable to connect to External vproxy 'my-proxy.my-domain.com' on port '9090', the host service is not running. Action : Deploy TransportMode : HotaddPreferred Vproxy : my-proxy.my-domain.com Error : ProxySession unsuccessful during initialization. Unable to deploy and verify the vProxy my-proxy.my-domain.com. Unable to query vProxy status after 'Deploy'. Request unsuccessful. Unable to connect to External vproxy 'my-proxy.my-domain.com' on port '9090', the host service is not running. (0) ProtectionType : VM VproxyStatus : Failed
La variable /var/log/brs/vmdm/vmdm.log Muestra:
YYYY-MM-DD20:37:02.229Z ERROR [] [vproxyMonitor] [][][][TRACE_ID:b28dabec92e4fcae][] [c.e.b.v.v.s.VPEProxyService.updateTask(809)] - Update VM Direct Protection Engine failed 40be4802-972d-416f-b131-43890b6c32ac ManagedProxySession(state=Failure, id=32a99bf2-1c6e-47e7-aff1-4b26b7026cc8, error: code=0, text=ProxySession unsuccessful during initialization. Unable to deploy and verify the vProxy my-proxy.my-domain.com. Unable to query vProxy status after 'Deploy'. Request unsuccessful. Unable to resolve External vproxy 'my-proxy.my-domain.com' IP address in DNS server(s).)
Cause
El dispositivo PowerProtect no tiene acceso al motor de VM Direct por medio del puerto 9090.
admin@ppdm:~> curl -v my-proxy.my-domain.com:9090 * Trying 192.168.9.131:9090... * connect to 192.168.9.131 port 9090 failed: No route to host * Failed to connect to my-proxy.my-domain.com port 9090 after 18548 ms: Couldn't connect to server * Closing connection 0 curl: (7) Failed to connect to my-proxy.my-domain.com port 9090 after 18548 ms: Couldn't connect to server admin@ppdm:~>
Resolution
El firewall o las redes del entorno se deben configurar para permitir que el dispositivo PowerProtect se comunique con el motor de VM Direct a través de los puertos 22 y 9090.
Article Properties
Article Number: 000399113
Article Type: Solution
Last Modified: 19 Dec 2025
Version: 2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.