VxRail:升级失败并显示预检查错误 “Source vSphere ESX Agent Manager (EAM)”
Summary: 将 vCenter Server 升级或修补到 8.0 U2 失败,并显示预检查错误“源 vSphere ESX Agent Manager (EAM) 升级无法获取 EAM URL 以根据系统受信任的证书进行检查”
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
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]
Cause
作为 EAM 升级预检查的一部分,将创建一个 EAM 客户端来检索所有 EAM 机构并执行必要的 SSL 信任检查。如果由于 EAM 服务无法登录 vCenter 而无法创建 EAM 客户端,则此步骤可能不会成功。这可能是由于”vpxd-extension“证书存储在 VECS 中,以及存储在 vCenter Server 数据库中用于 EAM 扩展的证书信息。
Resolution
通过以下任一选项更新 VPXD 中扩展的证书:
提醒:如果源是 Windows vCenter Server,请遵循选项 2。
选项 1 — 使用 fixcerts 脚本
更新扩展选项 2 — 使用 KB 2112577 更新扩展
使用 fixcerts 脚本更新扩展的证书:
- 从 https://via.vmw.com/fixcerts 下载 fixcerts 脚本
- 将下载的脚本复制到 VCSA
- 使用以下参数运行脚本以更新扩展
python fixcerts.py update --ExtensionType all
屏幕截图示例:

Affected Products
VMWare Cloud on Dell EMC VxRail E560F, VMWare Cloud on Dell EMC VxRail E560N, VxRail Appliance SeriesArticle Properties
Article Number: 000223593
Article Type: Solution
Last Modified: 28 Aug 2024
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.