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 This article is not tied to any specific product. Not all product versions are identified in this article.

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 Cluster (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 Appliance (RPA) VM 之間的埠 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 Plugin 檔案。

 

解析度:
RecoverPoint 應用裝置如預期運作,這是您出現與組態問題相關症狀的原因。

 

Affected Products

RecoverPoint for Virtual Machines
Article Properties
Article Number: 000188622
Article Type: Solution
Last Modified: 26 Sep 2023
Version:  9
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.