Solved

Should Vmotion network and CVM network be on the same network and VLAN?

  • 10 September 2014
  • 2 replies
  • 5630 views

Badge +5
Hello All,

For one of our customers, we get a critical error saying that ESXi host and CVM are on different network. This happened once we created new vmkernel port and enabled Vmotion on that port. The VLAN and network is different for that. What should we do?

Thank you so much...
icon

Best answer by PaulR 11 September 2014, 23:15

Some customers split Managment traffic and vMotion traffic to separate VMkernel ports, which is fine.Nutanix chooses the Hypervisor IP associated with CVMs by querying ESXi for the list of VMkernel Ports available and, if possible, chooses a VMkernel Port on the same sub-net as the CVM's "eth0" port.Typically, this is the same vmk{n} port IP address which is for ESX "Management traffic" (ie: vCenter's connection).If a new VMkernel port is introduced on another sub-net, for vMotion as you indicate, it should not be chosen unless it is the only one available, which doesn't sound like the case here.There have been similar issues where more than one VMkernel port is enabled for "Use this port group for management traffic".I would first check ESX vmk{n} Port configurations for assigned network and selected functionality, as well as ping-ability through any VLAN associations from the CVMs. Also, check the "/etc/vmware/esx.conf" file for "/adv/Net/ManagementIface" and "/adv/Net/ManagementAddr" contains the expected values.If a configuration change is required, make the change on ESX, then restart genesis on the associated CVM, which should pick up a proper address.If the Management VMkernel port is on the same sub-net as the Nutanix CVMs, and is ping-able, but was not the one Nutanix chose to configure, I would certainly suggest to open a Support case with Nutanix and pursue the issue since fail-over functionality will be affected.

View original

2 replies

Userlevel 4
Badge +21
Trying adding the IP to the NFS whitelist and see if that goes away.
Userlevel 3
Badge +17
Some customers split Managment traffic and vMotion traffic to separate VMkernel ports, which is fine.Nutanix chooses the Hypervisor IP associated with CVMs by querying ESXi for the list of VMkernel Ports available and, if possible, chooses a VMkernel Port on the same sub-net as the CVM's "eth0" port.Typically, this is the same vmk{n} port IP address which is for ESX "Management traffic" (ie: vCenter's connection).If a new VMkernel port is introduced on another sub-net, for vMotion as you indicate, it should not be chosen unless it is the only one available, which doesn't sound like the case here.There have been similar issues where more than one VMkernel port is enabled for "Use this port group for management traffic".I would first check ESX vmk{n} Port configurations for assigned network and selected functionality, as well as ping-ability through any VLAN associations from the CVMs. Also, check the "/etc/vmware/esx.conf" file for "/adv/Net/ManagementIface" and "/adv/Net/ManagementAddr" contains the expected values.If a configuration change is required, make the change on ESX, then restart genesis on the associated CVM, which should pick up a proper address.If the Management VMkernel port is on the same sub-net as the Nutanix CVMs, and is ping-able, but was not the one Nutanix chose to configure, I would certainly suggest to open a Support case with Nutanix and pursue the issue since fail-over functionality will be affected.

Reply