问题

加入Nutanix，以在现有vCenter上进行现有群集

  • 2020年4月17日
  • 1回复
  • 1747年的观点
r
徽章 +2

嗨，团队，

我对Nutanix和ESX中的迁移过程有疑问，

我可以在现有vCenter上的现有群集中加入Nutanix节点，现有节点中的处理器以及我的新Nutanix节点是相同的，并且EVC启用了，那么我可以在同一群集中加入Nutanix和常规服务器吗？

Hi teams,<\/p>

\u00a0<\/p>

i have question about migration process in nutanix and esx,<\/p>

can i joining nutanix node in existing cluster on existing vcenter, processor in my existing node and my new nutanix node is same, and evc is enable, so can i joining nutanix and general server in same cluster?<\/p>","quoteUsername":"randyramandani","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

该主题已关闭以供评论

1回复

杰里米
秩
UserLevel 3
徽章 +4

嘿 @randyramandani
我对此用例感到好奇，而不是将其设置为同一vCenter下的单独群集。
我认为，如果您将非Nutanix和Nutanix节点组合在同一集群中，您可能会遇到问题，这主要是因为它们不容易共享相同的存储空间。

从vCenter的角度来看，即使您设置了对其的访问权限，您的非Nutanix节点也不会将Nutanix数据存储视为相同的数据存储。This is because on the Nutanix nodes the datastore is (and needs to be) accessed on the internal switch at 192.168.5.2, but this address isn’t accessible externally (and really can’t be, since every host has this IP address presented by the local CVM, thus it must be an isolated network within the host to avoid IP address conflict.)

当数据存储名称，NFS Server IP地址和MOUNT路径相同时，Vcenter将NFS数据存储视为跨多个主机的“同一数据存储”。对于所有Nutanix节点，他们正在访问192.168.5.2：/Container-name，这意味着您可以在它们之间迁移VM，而无需存储迁移。对于任何其他ESXI主机，要访问相同的容器，都需要使用：/Container-name和Vcenter将其解释为不同的数据存储。这在vCenter库存中有点混乱。

如果您正在考虑将Nutanix节点附加到ESXI传统数据存储中，我将不得不建议您反对。请参阅文章“第三方存储可能会在Nutanix系统上引起问题“ 更多细节。

Hey\u00a0@randyramandani<\/user-mention>\u00a0
I\u2019m curious about the use case for this, versus setting it up as a separate cluster under the same vCenter.\u00a0
I think you might run into issues if you\u2019re combining non-Nutanix and Nutanix nodes in the same cluster, primarily since they wouldn\u2019t easily share the same storage.

From a vCenter perspective your non-Nutanix nodes would not see the Nutanix datastore as the same datastore even if you set up access to it. This is because on the Nutanix nodes the datastore is (and needs to be) accessed on the internal switch at 192.168.5.2, but this address isn\u2019t accessible externally (and really can\u2019t be, since every host has this IP address presented by the local CVM, thus it must be an isolated network within the host to avoid IP address conflict.)\u00a0

vCenter sees an NFS datastore as \u201cthe same datastore\u201d across multiple hosts when the datastore name,\u00a0NFS server IP address, and mount path are the same. For all the Nutanix nodes they are accessing 192.168.5.2:\/container-name and this means you can migrate VMs between them without storage migration.\u00a0\u00a0For any other ESXi host to access that same container it would need to use the <cluster virtual IP>:\/container-name and vCenter would interpret this as a different datastore. This gets a bit messy in the vCenter inventory.\u00a0

If you\u2019re looking at attaching the Nutanix nodes to your traditional datastores for ESXi, I\u2019d have to advise against it. See the article \u201c3rd party storage might cause issues on a Nutanix system<\/a>\u201d for more details.\u00a0<\/p>","quoteUsername":"JeremyJ","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