解决了

Repair Host Boot Disk: phoenix模式应用IPv4地址失败

  • 2020年3月24日
  • 2回答
  • 1667的浏览量
J
Userlevel 4
徽章 + 12
  • j_seet
  • 开拓者
  • 35个回复

有没有人曾经尝试主机书磁盘修复和遇到这个问题之前?

所有的电缆和sfp都插在插头上，就像它还在生产一样。还没有尝试通过基金会重建，因为下面是Nutanix提供的步骤:https://portal.nutanix.com/page/documents/details?targetId=Hypervisor-Boot-Drive-Replacement-Platform-v510-Multinode-G3G4G5:Hypervisor-Boot-Drive-Replacement-Platform-v510-Multinode-G3G4G5

采取的措施:

  • 下载并烧毁凤凰。iso, USB
  • 启动USB进入凤凰城
  • 启动Repair Host boot Disk并上传ESXi白名单镜像
  • 遇到错误

我有一个案子需要支持，并且已经升级了，我想在我等待的时候，我可以问问社区。一旦我们发现问题，将在这里提供一个回应。


干杯!

(编辑:我无意在行政长官论坛上发表这篇文章)

图标

最佳答案j_seet2020年3月24日，09:09

Just an update on the resolution.\u00a0 Nutanix support was able to work around this by manually installing ESXi then Phoenix.\u00a0 We suspect that the original problem was due to our network requiring a vLAN to be configured but the Host Repair wizard doesn\u2019t allow for a vLAN to be defined hence the manual install route.<\/p>","className":"post__content__best_answer"}">
查看原始
    Has anyone ever attempted a Host book disk repair and encountered this issue before?<\/p>

    \u00a0<\/p>

    \"//www.jhbzcj.com/next/installation-configuration-23/\"<\/figure>

    \u00a0<\/p>

    All cables and SFPs are plugged in as if it were still in production. Have not yet attempted to rebuild via foundation as these were the steps provided by Nutanix support:\u00a0\u00a0https:\/\/portal.nutanix.com\/page\/documents\/details?targetId=Hypervisor-Boot-Drive-Replacement-Platform-v510-Multinode-G3G4G5:Hypervisor-Boot-Drive-Replacement-Platform-v510-Multinode-G3G4G5<\/a><\/p>

    \u00a0<\/p>

    Steps Taken:<\/p>

    2回答

    J
    Userlevel 4
    徽章 + 12

    这是最新的决议。Nutanix支持能够通过手动安装ESXi然后安装Phoenix来解决这个问题。我们怀疑最初的问题是由于我们的网络需要配置一个vLAN，但主机修复向导不允许定义一个vLAN，因此手动安装路由。

    Just an update on the resolution.\u00a0 Nutanix support was able to work around this by manually installing ESXi then Phoenix.\u00a0 We suspect that the original problem was due to our network requiring a vLAN to be configured but the Host Repair wizard doesn\u2019t allow for a vLAN to be defined hence the manual install route.<\/p>","quoteUsername":"j_seet","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    J

    同样的问题。

    我可以设置CVM的ip地址…并重启修复主机的启动设备。但是我已经失去了在第一步成功完成的SATADOM图像。

    实际上，Nutanix没有办法将保存的SATADOM图像推回到新插入的SATADOM。

    所以一遍又一遍的重新成像....浪费时间和金钱。

    他们需要极大地改善陡坡。

    Got exactly the same issue.\u00a0<\/p>

    \u00a0<\/p>

    I was able to set the ip address of CVM\u2026\u00a0And restart the repair host boot device. But I\u2019ve lost the SATADOM image which was successfully done at the first step.\u00a0<\/p>

    \u00a0<\/p>

    Actually Nutanix have no way to push back the SATADOM image saved back to the newly inserted SATADOM.\u00a0<\/p>

    \u00a0<\/p>

    So reimage process again and again and again \u2026\u00a0and again\u2026. on my +600 nodes \u2026\u00a0Waste of a time and money.<\/p>

    \u00a0<\/p>

    They need to improved that steep so badly.<\/p>","quoteUsername":"Jacques MARENGO","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    回复


    Baidu