Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products

RecoverPoint for VMs:无法下载出现在 vCenter 上的插件错误

Summary: vCenter 持续显示错误,指出“Error downloading plug-in.确保 URL 可访问并且注册的指纹正确。“,对于 RecoverPoint 闪存插件。

This article applies to   This article does not apply to 

Symptoms

在 vCenter 任务 期间,它将持续显示错误 ,指出“Error downloading plug-in.确保 URL 可访问并且注册的指纹正确。“,对于 RecoverPoint 闪存插件。

 

您可能会在 vCenter 任务 中看到错误堆栈,如下所示(对于受影响的 vCenter,可以找到 /var/log/vmware/vsphere-ui/logs/vsphere-client-virgo.log相同的输出):

 

vCenter 尝试从 RecoverPoint 群集下载 RPVWCPlugin.zip 文件。(https://xxx.xxx.xxx.xxx/plugin/RPVWCPlugin.zip),但它会失败。

当您检查 vCenter 与 RecoverPoint 群集(RPA1、RPA2 和管理 IP)之间的通信时,会超时。

Download plug-in
Status:
Error downloading plug-in. Make sure that the URL is reachable and the registered thumbprint is correct.
Initiator:
VSPHERE.LOCAL\vsphere-webclient-xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Target:
vCENTER_Trying_to_Download
Server:
vCENTER_Trying_to_Download
Error stack:
Error downloading plug-in. Make sure that the URL is reachable and the registered thumbprint is correct.
java.net.SocketTimeoutException: connect timed out
java.net.PlainSocketImpl.socketConnect(Native Method)
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:476)
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:218)
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:200)
java.net.SocksSocketImpl.connect(SocksSocketImpl.java:394)
java.net.Socket.connect(Socket.java:606)
sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:286)
sun.net.NetworkClient.doConnect(NetworkClient.java:175)
sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:292)
sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:395)
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)
sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162)
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056)
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570)
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:352)
com.vmware.vise.util.http.ConnectionManager.connect(ConnectionManager.java:298)
com.vmware.vise.util.http.SimpleHttpClient.connect(SimpleHttpClient.java:354)
com.vmware.vise.util.http.SimpleHttpClient.connect(SimpleHttpClient.java:324)
com.vmware.vise.util.http.SimpleHttpClient.executeMethodResponseAsStream(SimpleHttpClient.java:222)
com.vmware.vise.vim.extension.VcExtensionManager.writePackageToFile(VcExtensionManager.java:1320)
com.vmware.vise.vim.extension.VcExtensionManager.downloadPackage(VcExtensionManager.java:1175)
com.vmware.vise.vim.extension.VcExtensionManager$2.call(VcExtensionManager.java:793)
com.vmware.vise.vim.extension.VcExtensionManager$2.call(VcExtensionManager.java:783)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
com.vmware.vise.util.concurrent.QueuingCachedThreadPool$QueueProcessor.run(QueuingCachedThreadPool.java:1229)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
com.vmware.vise.util.concurrent.WorkerThreadFactory$1.run(WorkerThreadFactory.java:64)
java.lang.Thread.run(Thread.java:748)
Related events:

adminEmail    string[]    
"support@emc.com"
company    string    "EMC"
description    Description    
NAME    TYPE    VALUE
label    string    "RecoverPoint for Virtual Machines"
summary    string    "5.3.1.1"
serverThumbprint    string    "xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx"
type    string    "HTTPS"
url    string    "https://urldefense.com/v3/__https://xxx.xxx.xxx.xxx/plugin/RPVWCPlugin.zip__;!!LpKI!ygCOZImZxpT8GWMnyBxQ-T7Vuvy0LYr35iOf8DZy31JVkt7sSCjJCEmRIluS1ijakX9CKACEUg$ [xxx[.]xxx[.]xxx[.]xxx]"

 

测试 VC 与 RPA 之间的通信的步骤

  1. 通过 SSH 连接到您的 VC
  2. 收集您的 RPA IP 详细信息
  3. 运行命令 nc -v -w 2 -z RPA_IP 443 (按实际 RPA IP 地址替换RPA1_IP)
  4. 从以前的命令输出中,如果您获得 “Connection timed out”, 则 vCenter 无法与 RecoverPoint 群集建立连接。
    测试 vcenter 和 RecoverPoint 应用装置之间的通信

 

Cause

在 vCenter 版本 6.7 及更低版本中,连接失败的原因与 vCenter 和 RecoverPoint 应用装置 (RPA) 虚拟机之间的端口 443 和 9443 关闭有关。

在 vCenter 版本 7.0 及更高版本中,不再使用 Flex 插件。上述错误可能是由于旧 vCenter 版本的剩余插件和文件造成的。

 

Resolution

解决方法:
在 vCenter 6.7 及更低版本中:

为了解决通信问题,请与您的网络团队合作,以允许端口 443 和 9443 上的 vCenter 和 RPA 计算机之间的流量。允许后,您可以下载并安装插件。

 

有关更多端口和安全详细信息,请参阅我们的安全配置指南: https://dl.dell.com/content/docu100469_recoverpoint-for-vms-5-3-security-configuration-guide.pdf

 

在 vCenter 7.0 及更高版本中:
按照 KB 000157983 清理剩余的 Flex 插件文件。

 

分辨率:
RecoverPoint 应用装置按预期工作,这是您遇到与配置问题相关的症状的原因。

 

Affected Products

RecoverPoint for Virtual Machines