I need a help in of the configuration here in my client place. They had 2host cluster and 3 vLans on one vmkernel port group, where Guests are configured to use the specific vlans (for ex: Guest1/172.1.1.10/ uses vLan10, ex2:Guest1/172.1.2.20/ uses vLan20 )
I have rebuilt the hosts and cluster yesterday, and I have configured the networking as per the screenshots I made. Now I see the vmotion is not happening, though the all vlans present in the host. I manually migrated one of the guest and I see the Guest moved to different vlan and hence it is not pingable.
Even the host is above 93% mem usage, it is not vmotioning. what could be the reason? how can i set this one?
Seems like you attached the same image for both hosts 🙂 Please, attach the correct image and like André said, check the physical port of switch where your hosts are connected.
You have not attached any screenshots, please upload the screenshots. Also, just to clarify, vmotion will not change the network settings of the VM when it moves between hosts. vMotion will move a VM from physical host to another. Your post is not clear, can you give us more details in what you are trying to do?
Thanks for the response, I have attached the screen shots of both the hosts. data network has 3 Vlans and when I vmotion the guest from host1 to host2, it goes un pingable
I think this could issue could be related to the physical switch port's settings (e.g. port security, spanning-tree, ...). How are the physical ports configured? In case of Cisco switches, please post the output of sh run int <interface> for the ports to see how they look like.
Btw. depending on the physical network infrastructure, I'd recommend you check whether combining the Management and vMotion network on a single vSwitch (802.1Q with an active/standby port group configuration) would make sense for redundancy.
André
Seems like you attached the same image for both hosts 🙂 Please, attach the correct image and like André said, check the physical port of switch where your hosts are connected.
Yes, I got it resolved by resetting the vmotion IP
This problem is resolved, this chassis has issue with network load balancing issue, So instead the NIC Teaming Default - Route Based on the Originating Virtual Port ID, I have chose to Route Based on IP hash worked.
Issue is resolved