Join this episode for more Stories from the EUC Road as Sean Donahue (Nutanix) and Al Solorzano (E360) tackle this all too familiar question. But does it have to an \u201cOR\u201d statement? Can you have an \u201cAND\u201d statement instead? Tune in to learn more about performance in EUC, happy employees and how you might sleep better at night in the age of Malware and Ransomware.<\/p><\/oembed>

Resources<\/p>

解决了

私人网络

p
徽章

我有一个关于私人网络的问题。我有一个位于192.168.20.x网络中的NFS共享，但是我的Nutanix Public（Internet访问）网络位于10.10.2.x.中。我需要创建一个网络，我的VM可以与NFS服务器交谈。我已经查看了一些YouTube视频，但它们并不是很有帮助。那里有更好的文档吗？

图标

最好的答案Nupur.Sakhalkar2021年2月6日，19：05

Hey\u00a0@PSLAdmin<\/user-mention>\u00a0, to answer your questions:<\/p>
  1. You don\u2019t need to use the same\u00a0IP range as the CVM or AHV for your user VMs -\u00a0 use different IP range for your user VMs\u2019 network. Just make sure to create those networks in Prism first with appropriate VLAN tags and then add these networks to the VMs accordingly.\u00a0In order to create a VM Network via Prism, see the steps mentioned in Network Configuration on VM interfaces<\/a> section on\u00a0Nutanix Support Portal<\/a><\/li>\t
  2. If you are using AHV as your hypervisor, then we already have a default bridge - br0 present in the AHV host.\u00a0If you are ok with using this default bridge br0 for user VM traffic as well, then there is no need to create a separate bridge for user VM traffic. However, if you wish to use a separate bridge\/vswitch for user VM traffic, then you can do so by creating a new bridge in the AHV host. Then, you will need to simply configure the VM Network associated with this\u00a0user VM to use the new bridge instead of using the default bridge - br0. To create a separate vswitch for user VM networks, refer to\u00a0Creating a virtual switch<\/a> section on\u00a0Nutanix Support Portal<\/a><\/li>\t
  3. Create VM Network first (using associated VLAN tags) which you want to use for the user VM and then while creating the user VM, add this VM network to it. Whenever you create a new VM Network via Prism, it will use the\u00a0default bridge -br0 by default (for AHV hosts). As mentioned in (2), if you wish to use a separate bridge in AHV host for this VM network,\u00a0this can be done as well.<\/li>\t
  4. If you are using any VLAN for your user VM network which is different than the VLAN which is used by CVM\/host traffic(default - VLAN 0), then you will need to make sure that those VLANs are configured on the physical switches as well so that once the user VM traffic reaches the switch, switch can handle it accordingly. Also, make sure to use\u00a0VLAN trunking for these AHV host interfaces on the physical switch so that it can carry multiple VLAN traffic.\u00a0<\/li>\t
  5. When you mark the AHV host interfaces as trunk ports on switch side, it can carry multiple VLAN traffic. So, VLANs used by VMs doesn\u2019t need to be on the same native VLAN which is being used by the trunk interface configured on switch side. As mentioned in (4), you will need to make sure that these\u00a0VLANs (used during VM network creation)\u00a0are also configured on physical switches. Moreover, if you want the user VMs to have access to the internet, then you will need to have appropriate network configuration done on your uplink switches so that the user VM traffic\u00a0can reach to the internet once it reaches these uplink switches.\u00a0<\/li><\/ol>

    Also, here are some documentation guides which will be useful\u00a0in the this scenario:<\/p>

    1. Nutanix Tech TopX Video on AHV VM Networking Enhancements: VLAN Trunking<\/a><\/li>\t
    2. AHV Networking recommendations<\/a>\u00a0<\/li>\t
    3. Create a VM in AHV via Prism<\/a>\u00a0<\/li><\/ol>

      The AHV Networking Blueprint<\/a>\u00a0mentioned by\u00a0@Primzy<\/user-mention>\u00a0earlier is also super helpful.\u00a0<\/p>","className":"post__content__best_answer"}">

查看原件
I have a question regarding private networks.\u00a0 I have an NFS share that resides in the 192.168.20.x network, however my Nutanix public (Internet access) network is in the 10.10.2.x.\u00a0 I need to create a network where my VM can talk to the NFS server.\u00a0 I\u2019ve reviewed some YouTube videos but they\u2019re not very helpful.\u00a0 Any better documentation out there?<\/p>","quoteUsername":"PSLAdmin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
该主题已关闭以供评论

6个答复

p
UserLevel 6
徽章 +16

这是Nutanix员工的指南，希望它会有所帮助：AHV网络

p
徽章

我已经用完了想法，希望这里有人可以提供帮助。我在一个节点上部署了nutanix ce。稍后我将再添加2个节点。现在，我想获得非常基本的运行CentOS的虚拟机。

  • 问题1：当我创建一个需要运行需要访问Internet的网络的网络时，我是否分配了与CVM或AHV相同的IP范围内的IP？还是我使用私人IP网络，Nutanix会为我处理路由？
  • 问题2：我还需要创建虚拟开关吗？我看过的许多视频都不会这样做，所以我很困惑。
  • 问题3：我需要创建一个网络，开关和桥梁才能使所有网络工作吗？再次，视频没有提及任何内容。
  • 问题4：看起来很容易在Nutanix中部署VM吗？我没有任何运气模仿我看过的所有视频。如果它很容易，并且VM可以在我的配置中很少出现Internet，那么我的问题也许就位于物理开关中。

获得非常基本的工作VM的任何帮助或建议将不胜感激。我已经回顾了Nutanix圣经，但我什至无法通过基本网络来实现任何意义。

I\u2019ve run out of ideas and I hope someone here can help.\u00a0 I deployed Nutanix CE on one node.\u00a0 I will add 2 more nodes later.\u00a0 For now I want to get a very basic deployment of a virtual machine running Centos.<\/p>
  • Question 1: When I create a network where the VMs will run that need to access to the internet, do I assign IPs that are in the same IP range as the CVM or AHV?\u00a0 Or do I use a private IP network and Nutanix will handle the routing for me?<\/li>\t
  • Question 2: Do I need to create a virtual switch as well?\u00a0 Many of the videos I\u2019ve seen don\u2019t do that so I\u2019m confused.<\/li>\t
  • Question3: Do I need to create a network, a switch and a bridge for all of it to work?\u00a0 Again the videos don\u2019t mention any of that.<\/li>\t
  • Question 4: Is deploying a VM in Nutanix as easy is it looks?\u00a0 I have not had any luck emulating all the videos I\u2019ve seen.\u00a0 If it is easy and the VMs can get out to the Internet with very little configuration on my part then perhaps my problem resides in the physical switch.<\/li><\/ul>

    Any help or suggestions to get a very basic working VM would be greatly appreciated. I have reviewed the Nutanix Bible but I can\u2019t even get passed basic networking for it to mean anything.<\/p>","quoteUsername":"PSLAdmin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

p
徽章

后续问题：Nutanix中的VLAN号是否必须匹配物理开关上的VLAN号码？

Follow up question: Does the Vlan number in the Nutanix have to match the Vlan number on the physical switch?<\/p>","quoteUsername":"PSLAdmin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
p
徽章

问题解决了！如果分配了0以外的VLAN，我将无法与外界进行交流。

Problem solved! If assign a VLAN other than 0 I\u2019m not able to communicate with the outside world.<\/p>","quoteUsername":"PSLAdmin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
n
秩
UserLevel 3
徽章 +5

嘿 @psladmin，回答您的问题：

  1. 您无需为您的用户VM使用与CVM或AHV相同的IP范围 - 为您的用户VMS网络使用不同的IP范围。只要确保首先使用适当的VLAN标签创建这些网络，然后将这些网络添加到VM中。为了通过PRISM创建VM网络，请参阅中提到的步骤VM接口上的网络配置部分Nutanix支持门户
  2. 如果您将AHV用作您的管理程序，那么我们已经在AHV主机中有一个默认的桥梁-BR0。如果您还可以将此默认的桥梁BR0用于用户VM流量，则无需为用户VM流量创建单独的桥梁。但是，如果您想将单独的桥梁/VSWWITCH用于用户VM流量，则可以通过在AHV主机中创建新的桥梁来做到这一点。然后，您将需要仅配置与此用户VM关联的VM网络以使用新桥，而不是使用默认桥梁-BR0。要为用户VM网络创建单独的VSWWITCH，请参阅创建虚拟开关部分Nutanix支持门户
  3. 首先创建VM网络（使用关联的VLAN标签），您要用于用户VM，然后在创建用户VM时，将此VM网络添加到它。每当您通过PRISM创建新的VM网络时，它将使用默认的Bridge -BR0（对于AHV主机）。如（2）中所述，如果您希望在此VM网络中使用AHV主机中的单独桥梁，则可以做到这一点。
  4. 如果您对用户VM网络使用任何VLAN，该网络与CVM/主机流量使用的VLAN不同（默认-VLAN 0），则您将需要确保在物理开关上配置这些VLAN因此，一旦用户VM流量到达开关，开关就可以相应地处理。另外，请确保在物理开关上使用VLAN中继线进行这些AHV主机接口，以便它可以携带多个VLAN流量。
  5. 当您将AHV主机接口标记为开关侧的中继端口时，它可以携带多个VLAN流量。因此，VMS使用的VLAN不必在开关侧配置的中继接口使用的同一本机VLAN上。如（4）中所述，您需要确保在物理开关上还配置了这些VLAN（在VM网络创建过程中使用）。此外，如果您希望用户VM可以访问Internet，则需要在上行链路交换机上进行适当的网络配置，以便用户VM流量达到Internet，一旦达到这些上行链路开关。

另外，这里是一些文档指南，在这种情况下将很有用：

  1. Nutanix Tech Topx视频AHV VM网络增强功能：VLAN中继
  2. AHV网络建议
  3. 通过棱镜在AHV中创建VM

这AHV网络蓝图提到 @primzy早期也非常有帮助。

Hey\u00a0@PSLAdmin<\/user-mention>\u00a0, to answer your questions:<\/p>
  1. You don\u2019t need to use the same\u00a0IP range as the CVM or AHV for your user VMs -\u00a0 use different IP range for your user VMs\u2019 network. Just make sure to create those networks in Prism first with appropriate VLAN tags and then add these networks to the VMs accordingly.\u00a0In order to create a VM Network via Prism, see the steps mentioned in Network Configuration on VM interfaces<\/a> section on\u00a0Nutanix Support Portal<\/a><\/li>\t
  2. If you are using AHV as your hypervisor, then we already have a default bridge - br0 present in the AHV host.\u00a0If you are ok with using this default bridge br0 for user VM traffic as well, then there is no need to create a separate bridge for user VM traffic. However, if you wish to use a separate bridge\/vswitch for user VM traffic, then you can do so by creating a new bridge in the AHV host. Then, you will need to simply configure the VM Network associated with this\u00a0user VM to use the new bridge instead of using the default bridge - br0. To create a separate vswitch for user VM networks, refer to\u00a0Creating a virtual switch<\/a> section on\u00a0Nutanix Support Portal<\/a><\/li>\t
  3. Create VM Network first (using associated VLAN tags) which you want to use for the user VM and then while creating the user VM, add this VM network to it. Whenever you create a new VM Network via Prism, it will use the\u00a0default bridge -br0 by default (for AHV hosts). As mentioned in (2), if you wish to use a separate bridge in AHV host for this VM network,\u00a0this can be done as well.<\/li>\t
  4. If you are using any VLAN for your user VM network which is different than the VLAN which is used by CVM\/host traffic(default - VLAN 0), then you will need to make sure that those VLANs are configured on the physical switches as well so that once the user VM traffic reaches the switch, switch can handle it accordingly. Also, make sure to use\u00a0VLAN trunking for these AHV host interfaces on the physical switch so that it can carry multiple VLAN traffic.\u00a0<\/li>\t
  5. When you mark the AHV host interfaces as trunk ports on switch side, it can carry multiple VLAN traffic. So, VLANs used by VMs doesn\u2019t need to be on the same native VLAN which is being used by the trunk interface configured on switch side. As mentioned in (4), you will need to make sure that these\u00a0VLANs (used during VM network creation)\u00a0are also configured on physical switches. Moreover, if you want the user VMs to have access to the internet, then you will need to have appropriate network configuration done on your uplink switches so that the user VM traffic\u00a0can reach to the internet once it reaches these uplink switches.\u00a0<\/li><\/ol>

    Also, here are some documentation guides which will be useful\u00a0in the this scenario:<\/p>

    1. Nutanix Tech TopX Video on AHV VM Networking Enhancements: VLAN Trunking<\/a><\/li>\t
    2. AHV Networking recommendations<\/a>\u00a0<\/li>\t
    3. Create a VM in AHV via Prism<\/a>\u00a0<\/li><\/ol>

      The AHV Networking Blueprint<\/a>\u00a0mentioned by\u00a0@Primzy<\/user-mention>\u00a0earlier is also super helpful.\u00a0<\/p>","quoteUsername":"Nupur.Sakhalkar","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

阿罗纳
秩
UserLevel 6
徽章 +5

嗨，Psladmin，您似乎依靠视频，但是您是否尝试过阅读诸如AHV和Prism指南之类的Nutanix文档？他们将帮助您更好地进行设置，并提高您对系统的理解。

Hi PSLAdmin,You seem to rely on videos but have you tried reading Nutanix documentation like AHV and Prism guides? They would help you with the set up much better and improve your understanding of the system.<\/p>","quoteUsername":"Alona","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