RecoverPoint for VMs：安裝在 53% 時失敗 - 無法建立 JAM 設定檔

在 5.2 版及更新版本中，虛擬機器專用的 RecoverPoint 新安裝失敗，並顯示錯誤 "Failed to create JAM profile".
虛擬機器叢集的 RecoverPoint 在部署程式中於 53% 失敗。

clusterLogic.log中的錯誤：

2018/12/11 02:54:03.774 [pool-6-thread-793] (BaseInstallationServerAdapter.java:287) ERROR - errorType: OPERATION_FAILED , userMSG: Operation failed. Failed to create JAM profile. 
2018/12/11 02:54:03.774 [pool-6-thread-793] (BaseInstallationServerAdapter.java:294) ERROR - Transaction failed. transactionId=665, timeoutInSeconds=900, errorMSG=Operation failed. Failed to create JAM profile. , errorType=OPERATION_FAIL ED, value=null 
2018/12/11 02:54:03.774 [pool-6-thread-793] (BaseRpaCall.java:52) ERROR - CreateVirtualRepositoryCall failed. java.lang.RuntimeException: Operation failed. Failed to create JAM profile. All VASA (Storage) IOFilter providers that are seen as online. When looking on the ESX sps logs(var/log/vmware/vmware-sps/sps.log.), we see the provider URL validation fails: 
2018-12-10T17:36:23.155-07:00 [pool-14-thread-15] DEBUG opId= com.vmware.vim.sms.provider.ProviderFactory - [createVasaProvider] Creating VASA provider with the spec : username - IOFilterUser URL - https://esx1.local:9080/version.xml certificate - null 
2018-12-10T17:36:23.155-07:00 [pool-14-thread-15] DEBUG opId= com.vmware.vim.sms.provider.ProviderFactory - Validating Provider Spec... 
2018-12-10T17:36:23.155-07:00 [pool-14-thread-15] DEBUG opId= com.vmware.vim.sms.provider.ProviderFactory - Validating the provider URL - https://esx1.local:9080/version.xml 
2018-12-10T17:36:23.157-07:00 [pool-14-thread-15] ERROR opId= com.vmware.vim.sms.provider.ProviderFactory - Error during the validation of the provider URL java.net.ConnectException: Connection refused (Connection refused) at java.net.PlainSocketImpl.socketConnect(Native Method)

vCenter Server 上的 /var/log/vmware/eam.eam.log 檔案中可能出現另一個錯誤：

2025-08-15T12:29:21.564Z |  INFO | vim-inv-update | VcHostSystem.java | 462 | VcHostSystem(ID: host-30) connection state changed from connected to notResponding
2025-08-15T12:29:21.567Z |  INFO | vim-inv-update | IssueHandlerBase.java | 116 | Updating issues:
New issues:
[
eam.issue.HostNotReachable {
   description = <unset>,
   time = 2025-08-15 12:29:21,566,
   key = 36,
   agency = 'Agency:02c1f3b9-e1c1-4ac6-962b-0fcdxxxxxxxx:null',
   agencyName = 'IoFilter-EMC_bootbank_emcsplitter',
   solutionId = 'VirtualCenter',
   solutionName = 'VirtualCenter',
   agent = 'Agent:2743bb3a-d750-43ee-8e73-1ea64xxxxxxxx:null',
   agentName = '2743bb3a-d750-43ee-8e73-1ea64xxxxxxxx',
   host = 'HostSystem:host-30:e9663bd3-fe85-4dd2-bc3f-cdd3xxxxxxxx',
   hostName = 'Host02.corp.com',
}

• vCenter 無法透過連接埠 9080 連接至 ESXi 主機，以驗證 VASA 提供者，這是建立 JAM 設定檔和儲存庫時的必要操作。
• 防火牆封鎖了 vCenter Server 和 ESXi 之間的連接埠 9080。

主意：

確認已在 vCenter 伺服器和 ESXi 節點之間開啟連接埠 9080 （TCP 和 UDP）。
下列命令可用於驗證連線：

curl -insecure https://xx.xx.xx.xx:9080/version.xml

命令是從 vCenter Server 執行，而 xx.xx.xx.xx 是 ESXi 主機的 IP。
命令不應有回應，但返回代碼應為 60：

sso-user@vcsarp [ ~ ]$ curl -insecure https://192.168.10.10:9080/version.xml
sso-user@vcsarp [ ~ ]$ echo $?
60