ESXi 6.5U1升级AOS 5.1.1.3

  • 2017年8月29日
  • 2回复
  • 957观
M.
徽章 +5
我最近从6.0 - > 6.5U1升级了我的vCenter，我不希望升级我的ESXi 6.0U3安装到6.5U1。我的第一次尝试是使用一键式管理程序升级，并且我能够上传ISO和MD5校验和，但是升级预升级的错误相当快速地用相当通用的错误消息说“无法确定捆绑版本”。有几次重新下载并重新上传尝试验证我的文件完整性，但错误持久。然后我试图使用vum进行升级旧学校风格，它可以方便地烘焙到我的vcsa，因为6.5，我在更新管理器里面有另一个通用错误消息，“升级包含以下一组冲突的vib：”没有但是结肠后面的空白空间。通常，我预计会看到一个单独的vib以列表形式呼出，但没有任何内容。我完全修补了使用Nutanix LCM的当前，所以我怀疑LCM已经滑入的LSI HBA更新之一 - 有没有其他人在类似的问题上运行？有些人在VMware社区论坛上搜索，我还没有看到任何“空白”不兼容的VIB错误，所以我有一个肠道感觉，它是我们所执行的特定Nutanix的症状/有关的症状/目的。
    6.5u1, and I'm not looking to upgrade my ESXi 6.0u3 installs to 6.5u1. My first attempt was to use one-click hypervisor upgrade, and I was able to uploading the ISO and MD5 checksum, but the pre-upgrade check errors out pretty quickly with a fairly generic error message saying \"unable to determine version of bundle.\" Did a few re-download and re-upload attempts to verify my file integrity but the error persisted. I then tried to do the upgrade old-school style using VUM which is conveniently baked into my VCSA as of 6.5, and I got another generic error message inside of update manager, \"The upgrade contains the following set of conflicting VIBs:\" with nothing but blank space following the colon. Typically I would have expected to see an individual VIB called out in list form, but there is just nothing there. I am fully patched to current using Nutanix LCM, so I suspect it is probably one of the LSI HBA updates that LCM has slipped in - has anybody else run across a similar problem? Did some searching around the VMware community forums and I haven't seen any \"blank\" incompatible VIB errors so I have a gut feeling that it is a symptom\/something related to specific Nutanix LCM updates that we have performed.","quoteUsername":"mdt_tjagoda","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    2回复

    D.
    徽章 +1
    当我ran vmware更新管理器升级到6.5u1时，我遇到了几个VIB不兼容。我有一个基于Windows的vCenter 6.5Server，但在我的Update Manager上，它告诉我有问题的VIB。
    当我用6.5U1 ISO和扫描附加基线并扫描时，Update Manager表示，合规性是不兼容的，并且在状态详细信息下我得到类似的东西：
    升级包含以下冲突VIB集：
    emulex_bootbank_scsi-lpfc820_8.2.4.141.55-1OEM.500.0.0.472560
    emulex_bootbank_scsi-lpfc820_8.2.4.141.55-1OEM.500.0.0.472560
    mellanox_bootbank_net-mst_2.0.0.0-1oem.550.0.0.472560
    mellanox_bootbank_net-mst_2.0.0.0-1oem.550.0.0.472560

    （注意：这是来自旧的HP服务器，只需扫描示例）
    要解决我的问题，我点击谷歌和VMware，在vmwares站点上找到了更新的驱动程序，将它们上传到更新管理器修补场存储库并使用修复按钮从那里应用它们。从这里，我可以从更新管理器运行ESX 6.5U1主机升级。
    如果您无法从更新管理器中获取冲突VIB，我建议在Nutanix节点IPMI接口中安装6.5U1 ISO，并尝试运行升级。它会失败，但它应该至少吐出一个原因，并且常备的名字阻止它从后续成功。
    \nWhen I attached the baseline with the 6.5u1 ISO and ran a Scan, Update Manager says the Compliance is Incompatable and under Status details I get something similar to this:
    \nThe upgrade contains the following set of conflicting VIBs:
    \nEmulex_bootbank_scsi-lpfc820_8.2.4.141.55-1OEM.500.0.0.472560
    \nEmulex_bootbank_scsi-lpfc820_8.2.4.141.55-1OEM.500.0.0.472560
    \nMellanox_bootbank_net-mst_2.0.0.0-1OEM.550.0.0.472560
    \nMellanox_bootbank_net-mst_2.0.0.0-1OEM.550.0.0.472560
    \n
    \n(Note: This is from an old HP server, just ran a scan for an example)
    \nTo solve my problem I hit google and VMWare, found updated drivers on VMWares site, uploaded them into Update Manager Patch Repository and applied them from there using the Remediate button. From here I was able to run the ESX 6.5u1 Host Upgrade from Update Manager.
    \nIf you cannot get the conflicting VIBs out of Update Manager, I would suggest mounting the 6.5u1 ISO in the Nutanix node\u2019s IPMI interface, and try to run the upgrade. It will fail, but it should spit out a reason at least and the names of the VIBs stopping it from succeeding.","quoteUsername":"dbolognani1","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    T.
    Dbolognani1，请将我指出，将您下载的司机指向达到此目的吗？我有同样的错误，我找不到它们。先感谢您！

    回复


    条款和条件
    Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
    Functional","cookiepolicy.modal.level2":"Normal
    Functional + analytics","cookiepolicy.modal.level3":"Complete
    Functional + analytics + social media + embedded videos"}}}">
    Baidu