VMware Cloud Community
Islanders
Enthusiast
Enthusiast
Jump to solution

About vMotion on vSphere6.7

I want to know does vMotion on vSphere6.7 still require a common share storage?

I setup my lab as following. I have one Master ESXi6.7 and then I install two nested ESXi6.7 in the master call ESXi-1a and ESXi-2a.

There is a small VM running in ESXi-2a. I config vmkernel for vMotion for them.

ESXi-1a has vmkernel port# 172.16.200.220 and ESXi-2a has vmkernal port#172.16.200.221..

When the vm power off then I able to vMotion from ESXi-2a to ESXi1a , but when the vm power on then I won't able to vMotion them?

Any idea?

Thank you

Michael

26 Replies
Islanders
Enthusiast
Enthusiast
Jump to solution

Joerg

Yes. I rebuild two ESXi hosts and keep it simple only one vswitch and 1 port group.

It does work on management side as long as vMotion enable.

Is the vMotion only layer 2 function? If so why it need a IP ?

Thank you

Reply
0 Kudos
Islanders
Enthusiast
Enthusiast
Jump to solution

Joerg,

Same setup on ESXi-2A and ESXi-1A.

After it work on the management network, I created a kernel for vMotion only and disable vMotion on the Management port group.

Why it stop working for vMotion?

Thanks

Reply
0 Kudos
IRIX201110141
Champion
Champion
Jump to solution

When you created VMK1 did you choose the default TCP Stack or the vMotion one?  If its the later one please delete VMK1 and recreate VMK1 but this time please choose the default TCP Stack. Than send us a screenshot from vCenter vSphere Client(HTML5) where all VMKs are listet.

vmk.PNG

Please ignore that i have 2 vMotion enabled VMKs.

Regards,
Joerg

Reply
0 Kudos
IRIX201110141
Champion
Champion
Jump to solution

Is this a virtual ESXi???????????????

Well... you already told this in your first post.  Please check if you have enabled promiscuous mode, mac address changes and forged transmits on the portgroup of the "real" ESXi.

Regards,
Joerg

Islanders
Enthusiast
Enthusiast
Jump to solution

Joerg,

Yes. It is nested ESXi for ESXi-1a and ESXi-2a.

Yes. It does work as you expected after I enable "Promiscuous mode,MAC address changed, Forged transmits accept." on Main ESXi host vSwtich0.

I thought each vSwitch0 it independent from each ESXi host?

I just out of curiosity. Let's say the real main ESXi host the master has four vswitch name as following vMainSwitch01,vMainSwitch01,vMainSwitch02.

And nested ESXi-1a has two virtual switches call vswitch01 and vswitch02.

How does those virtual switch mapping work between the main ESXi host and nested ESXi-1a?

I guess base on the vMotion testing there is no routing so Is vMotion is layer two traffic?

Thank you so much

Reply
0 Kudos
IRIX201110141
Champion
Champion
Jump to solution

No the "problem" was the following. By default security baselines (Promi, MAC, Forged) are active on a new created vSwitch or Portgroup.  If you create a VM(your vESXI) with a single vNIC you get one MAC for use. If you create within this GuestOS(your vESXi) new Interfaces with virtual MACs  and the GuestOS will use these to leave the VM the underlaying ESXi will drop these packets because of the security baselines.  This was the reason why it works with VMK0 which use the MAC which was assigned by and known for the underlaying ESXi and not with the additional VMKs.

Question: Did you get it working that some of your VM within then nested ESXi to reach the internet or devices in your local network? I think no Smiley Happy

Regards,
Joerg

Reply
0 Kudos
Islanders
Enthusiast
Enthusiast
Jump to solution

Thank you!

Reply
0 Kudos