VMware Cloud Community
Rao9339
Contributor
Contributor
Jump to solution

Host Migration failed

Hello,

I have 3 node cluster setup Esxi 6.5

ESXi120

ESXi121

ESXi122

I have one VM running pre-prod network ---when this VM is running on 121&122 no issues.

If it is migrated to 120 Host, then VM is out network --unfortunately no other VM is using pre-prod Vlan.

Rest all VM's migration no issues, only this Vm's getting issue.

tried all the ways

I am able to ping the Vm IP and GW from the 120 host.

Host fix this ....Please suggest

Reply
0 Kudos
1 Solution

Accepted Solutions
NicolasAlauzet
Jump to solution

Check if the VLAN is propagated to that ESXi.

If you are using trunk, that vlan should be allowed in that trunk. (when you say "I am able to ping the Vm IP and GW from the 120 host" i undestand you are doing ping from the Management vmk, so maybe the traffic is routed and thats why it works)

Other test you can do, add one VMkernel (with no services) to that portgroup (pre-prod) and test connectivity from there. If it fails, vlan it is.

-------------------------------------------------------------------
Triple VCIX (CMA-NV-DCV) | vExpert | MCSE | CCNA

View solution in original post

Reply
0 Kudos
8 Replies
NicolasAlauzet
Jump to solution

Check if the VLAN is propagated to that ESXi.

If you are using trunk, that vlan should be allowed in that trunk. (when you say "I am able to ping the Vm IP and GW from the 120 host" i undestand you are doing ping from the Management vmk, so maybe the traffic is routed and thats why it works)

Other test you can do, add one VMkernel (with no services) to that portgroup (pre-prod) and test connectivity from there. If it fails, vlan it is.

-------------------------------------------------------------------
Triple VCIX (CMA-NV-DCV) | vExpert | MCSE | CCNA
Reply
0 Kudos
nachogonzalez
Commander
Commander
Jump to solution

IMHO NicolasAlauzet​ gave you the best answer

Reply
0 Kudos
Rao9339
Contributor
Contributor
Jump to solution

Yes, i pining from Host management only.

and also Vlan is propagate to that host.

Then how to proceed.

Reply
0 Kudos
NicolasAlauzet
Jump to solution

As I mention, to check that the traffic is going out on that Portgroup and VLAN. Create a new VMkernel adapter on that portgroup. Put a valid IP and test conectivity (you dont need to enable any kind of service on that new vmk)

-------------------------------------------------------------------
Triple VCIX (CMA-NV-DCV) | vExpert | MCSE | CCNA
Reply
0 Kudos
nachogonzalez
Commander
Commander
Jump to solution

Are you using a standard switch or distributed switch?
If you are using standard switch is the vmname the same across different hosts?

Reply
0 Kudos
Rao9339
Contributor
Contributor
Jump to solution

we are using standard switch.

vmname the same across different hosts?

How to check this ?

Reply
0 Kudos
ZibiM
Enthusiast
Enthusiast
Jump to solution

By eyes - this is the best option.

Portgroup name on the standard switches needs to be exactly the same on all hosts in the cluster.

Even the size of the letters matters -> "VM NETWORK" != "VM Network"

When you confirm that this protgroup has exactly the same name and the configuration as the working portgroups on the other ESXi servers, then you should check with the network team the configuration of the ports on the physical switches.

Reply
0 Kudos
Rao9339
Contributor
Contributor
Jump to solution

Port group name is same across the 3 ESXi host.

I will check with network team on the physical connectivity part and let you know the update.

Reply
0 Kudos