ESXi consider VMotion vmkernel port as Management Traffic port

[ferdis]

Hello,

please dont you know if ESXi consider VMotion vmkernel port as Management Traffic port in some situations? One situation could be when both Management Traffic vmkernel port and VMotion vmkernel port are on same physical network?

Becouse customer got situation when he got Management Traffic port which he originally created at start. After that he created VMkernel port for VMotion with connectivity to the same physical network. After this he realized that in ESXi Bios page he sees in Management Network ip address of VMotion VMkernel port! And this is exactly same what I have seen today in Troubleshooting class!

Thank you very much for ideas.

[rickardnobel]

The other Vmkernel interface does not have the "Management" checkbox selected?

Have you tried to point the vSphere Client to the vMotion interface IP address and see if it really is available for management?

[Texiwill]

Hello,

please dont you know if ESXi consider VMotion vmkernel port as Management Traffic port in some situations?

Yes this is possible if your vMotion network is on the same subnet as the management port. This happens because with ESXi, both ports are vmkernel ports and only one route is used, the one for the management port. This is the default route for ALL vmkernel ports unless they use a secondary subnet.

One situation could be when both Management Traffic vmkernel port and VMotion vmkernel port are on same physical network?

Correct.

To separate vmknic (vmkernel ports) traffic you need to at least use different subnets routing down different wires, else everything falls back to the default route.

Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, 2010

Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security'[/url]

Also available 'VMWare ESX Server in the Enterprise'[/url]

Blogging: The Virtualization Practice[/url]|Blue Gears[/url]|TechTarget[/url]|Network World[/url]

Podcast: Virtualization Security Round Table Podcast[/url]|Twitter: Texiwll[/url]

[hharold]

We are having the same issue.

We have configured two portgroups:

One with only the Management traffic option enabled, and configured with an IP address in subnet X

The other one with only the VMotion traffic option enabled, and configured with an IP address in subnet Y

The DCUI is shows the IP address form the VMotion portgroup.

Even the /etc/hosts file is showing the VMotion IP address as its IP address.

Because VMware HA is affected heavily by wrong name resolving / DNS, we are suspecting this to be causing random HA errors.

Anyone can explain / solve this issue?

Thanks and kind regards,

Harold