我有一个关于私人网络的问题。我有一个位于192.168.20.x网络中的NFS共享,但是我的Nutanix Public(Internet访问)网络位于10.10.2.x.中。我需要创建一个网络,我的VM可以与NFS服务器交谈。我已经查看了一些YouTube视频,但它们并不是很有帮助。那里有更好的文档吗?
最好的答案Nupur.Sakhalkar
- 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
- 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
- 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
- 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
- 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>
- 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