关于残疾VM AutoStartup＆vSphere HA群集的错误

r
徽章 +3
  • 租金
  • 资源管理器
  • 0答复
大家好，

我们正忙于建造使用VSPHERE 5.5的NUTANIX 3.5.3.1基础架构。我们有两个块中有六个节点，设计由2个Nutanix簇组成，每个簇都有自己的vSphere群集。HA在每个集群上启用。

我们在Prism UI中的两个Nutanix群集中都有错误：

虚拟机自动启动在控制器VM的管理程序上被禁用

Nutanix最佳实践建议在每个主机上启用“使用系统的启动和停止虚拟机”，并将Nutanix CVM启动移至自动启动。但是，根据此VMware KB，在启用HA启用集群中移动ESXI主机时，自动启动功能将被禁用。就像错误消息所说的那样。

这是预期的行为吗？是否可以禁用此错误消息，因为它与启用VMware HA的群集相结合而无效？还是这仍然是配置错误？
    \n
    \nWe are busy building a Nutanix 3.5.3.1 infrastructure with vSphere 5.5. We have six nodes in two blocks, and the design consists of 2 Nutanix clusters with each its own vSphere cluster. HA is enabled on each cluster.
    \n
    \nWe are getting an error on both Nutanix clusters in PRISM UI:
    \n
    \nVirtual Machine auto start is disabled on the hypervisor of Controller VM <\/i>
    \n
    \nNutanix best practices recommend to enable \"Start and Stop Virtual Machines with the system\" on each host, and move the Nutanix CVM startup to Automatic startup. But, according to This VMware KB the automatic startup feature is disabled when moving an ESXi host in an HA enabled cluster. Just like the error message says.
    \n
    \nIs this expected behavior? Can this error message be disabled because it is just not valid in combination with VMware HA enabled clusters? Or is this still a configuration error?","quoteUsername":"rerents","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    3个答复

    Shuguet
    UserLevel 4
    徽章 +20
    Nutanix设置书还要求您禁用所有CVM，因此配置如下：
    - 创建HA群
    - 添加nutanix节点
    - 通过将“ VM重新启动优先级”设置为CVM的“ VM RESTART优先级”，禁用“ VSphere HA->虚拟机选项”中的CVM的HA。
    - 在每个节点的ESX级别上重新启用VM自动启动。

    我目前有此设置，一切正常，在节点供电后，CVM正确启动。

    西尔万。
    Sylvain Huguet -2X Nutanix技术冠军2015-2016，法国Nutanix Connect Chapter Champion，法国VMUG首领，6倍VMware Vexpert 2011至2016
    \n- Create the HA cluster
    \n- Add your Nutanix nodes
    \n- Disable HA for the CVMs in \"vSphere HA -> Virtual Machine options\" by setting \"VM restart priority\" to \"Disabled\" for the CVMs.
    \n- Re-enable VM automatic startup at the ESX level for each node.
    \n
    \nI currently have this setup and everything is working fine, with the CVM properly booting after a node is powered on.
    \n
    \nSylvain.","quoteUsername":"shuguet","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    b
    徽章 +5
    当vCenter对VMware进行重新配置时，设置每次都禁用了设置
    因此警告将返回。
    另外，在vSphere 5.5 WebClient中，当启用HA时，我什至无法活跃的自动启动。
    在5.5手册（手册）中，您会找到这条线
    “虚拟机启动和关闭（自动启动）功能均用于驻留在vSphere ha群集中的主机上的所有虚拟机。vSphere ha不支持自动启动。”

    我在Nutanix为此开了一个案例，他们给了这些“解决方法”

    我们可以禁用HA，启用自动启动，然后再次启用HA，或者（除此之外）可以将脚本放在ESXI主机中，以确保在重新启动时自动启动我们的VM。
    如果您在以下链接中查看提供的说明：http：//download.nutanix.com/guides/c_3_5/xhtml/index.html#oxy_ex-1/topics/topics/vsphere/host_upgrade_upgrade_complete_vsphere_vsphere_vsphere_htmll
    在步骤3（配置VSPHERE主机）中，您可以找到有关如何应用脚本以确保CVM在每个重启时自动供电的指令。关于这些步骤，请注意您无需重新启动ESXI主机以应用配置的事实。
    只要您更改脚本并保存配置，它就可以在重新启动时使用。
    您总是可以重新启动以确保。



    希望这可以帮助
    \nso the warning will return.
    \nAlso, in Vsphere 5.5 webclient I can't even active automatic startup anymore when HA is enabled.
    \nIn the 5.5 manual (Manual) you will find this line
    \n\"The Virtual Machine Startup and Shutdown (automatic startup) feature is disabled for all virtual machines residing on hosts that are in a vSphere HA cluster. Automatic startup is not supported with vSphere HA.\"<\/i>
    \n
    \nI opened a case for this at Nutanix and they gave these \"workarounds\"
    \n
    \nWe can disable HA, enable the auto-start and then enable HA back again, or we can (besides that) place an script in the ESXi hosts to make sure that our VM is auto-powered up upon reboot.
    \nIf you have a look at the instructions provided at the following link: http:\/\/download.nutanix.com\/guides\/c_3_5\/xhtml\/index.html#oxy_ex-1\/topics\/vsphere\/host_upgrade_complete_vsphere_t.html
    \nIn step 3 (Configure the vSphere host) you can find the instructions on how to apply the script to make sure the CVM is powered on automatically on every reboot. In regards to those steps, please be aware of the fact you don't need to reboot the ESXi host to apply the configuration.
    \nAs long as you change the script and save the configuration, it should work upon reboot.
    \nYou can always do a reboot just to make sure though.
    \n
    \n
    \n
    \nHope this helps","quoteUsername":"bleyers","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    j
    徽章 +5
    我们发现了同样的错误，并被告知，当我们进入VMware 5.5U1时，问题已经解决（我们喜欢大多数Nutanix客户由于NFS错误而尚未使用5.5U1）。

    同时，在等待升级时，我们从NOS Web管理员中禁用了警报。它的警报A1057。

    如果您曾经解决此问题，请告诉我。
    \n
    \nIn the mean time, whilst waiting for the upgrade we disabled the alert from the NoS web admin. Its alert A1057.
    \n
    \nPlease let me know if you ever fixed this issue.","quoteUsername":"JamesTMagna","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    条款和条件
    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