VxRail:升級失敗,並顯示預先檢查錯誤「Source vSphere ESX Agent Manager (EAM)」
摘要: 將 vCenter Server 升級或修補至 8.0 U2 失敗,並出現預先檢查錯誤「來源 vSphere ESX Agent Manager (EAM) 升級失敗,無法取得 EAM URL 以檢查系統信任的憑證」
本文章適用於
本文章不適用於
本文無關於任何特定產品。
本文未識別所有產品版本。
症狀
8.0 U2 升級預先檢查失敗,並顯示以下錯誤訊息:
Pre-upgrade check result Error: Source vSphere ESX Agent Manager (EAM) upgrade failed to obtain EAM URLs to check against trusted certificates by the System! Resolution: Verify that the ESX Agent Manager extension is running properly on the source vCenter Server instance and https://VC_IP/eam/mob presents correct data. If log in to the MOB is not successful, try resolving the issue with https://kb.vmware.com/s/article/94934.

EAM 記錄 (/var/log/vmware/eam/eam.log):
eam.log: 2024-03-13T10:11:33.816Z | INFO | vim-async-0 | OpIdLogger.java | 43 | [vim:loginExtensionByCertificate:881dd5a1dbf48356] Failed. 2024-03-13T10:11:33.816Z | WARN | vim-async-0 | ExtensionSessionRenewer.java | 227 | [Retry:Login:com.vmware.vim.eam:19090b37a54a32a] Re-login failed, due to: com.vmware.eam.security.NotAuthenticated: Failed to authenticate extension com.vmware.vim.eam to vCenter. at com.vmware.eam.vim.security.impl.SessionManager.convertLoginException(SessionManager.java:295) ~[eam-server.jar:?] at com.vmware.eam.vim.security.impl.SessionManager.lambda$loginExtension$4(SessionManager.java:154) ~[eam-server.jar:?] at com.vmware.eam.async.remote.Completion.onError(Completion.java:86) [eam-server.jar:?] at com.vmware.eam.vmomi.async.FutureAdapter.setException(FutureAdapter.java:81) [eam-server.jar:?] at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$ClientFutureAdapter.setException(MethodInvocationHandlerImpl.java:731) [vlsi-client.jar:?] at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.run(HttpExchangeBase.java:57) [vlsi-client.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_351] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_351] at java.lang.Thread.run(Thread.java:750) [?:1.8.0_351] Caused by: com.vmware.vim.binding.vim.fault.InvalidLogin: Cannot complete login due to an incorrect user name or password. at sun.reflect.GeneratedConstructorAccessor56.newInstance(Unknown Source) ~[?:?] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_351] at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_351]
原因
作為 EAM 升級預檢查的一部分,將創建一個 EAM 用戶端來檢索所有 EAM 機構並執行必要的 SSL 信任檢查。如果因為 EAM 服務無法登入 vCenter 而無法建立 EAM 用戶端,則此步驟可能不會成功。這可能是由於”vpxd-extension」的憑證儲存在 VECS 中,而憑證資訊則儲存在 EAM 延伸模組的 vCenter Server 資料庫中。
解析度
按照以下任一選項更新 VPXD 中延伸模組的憑證:
注意:如果來源是 Windows vCenter Server,請按照選項 2。
選項 1 - 使用 fixcerts 指令檔
更新擴充選項 2 - 使用 KB 2112577更新延伸
使用 fixcerts 指令檔更新擴充的憑證:
- 從 https://via.vmw.com/fixcerts 下載 fixcerts 指令檔
- 將下載的指令檔複製到 VCSA
- 使用以下引數執行指令檔以更新擴充
python fixcerts.py update --ExtensionType all
範例螢幕擷取畫面:

受影響的產品
VMWare Cloud on Dell EMC VxRail E560F, VMWare Cloud on Dell EMC VxRail E560N, VxRail Appliance Series文章屬性
文章編號: 000223593
文章類型: Solution
上次修改時間: 28 8月 2024
版本: 3
向其他 Dell 使用者尋求您問題的答案
支援服務
檢查您的裝置是否在支援服務的涵蓋範圍內。