VMware Cloud Community
mousseau_45
Contributor
Contributor

New hosts not connecting VMs to the external network

Our environment consists of mostly IBM blades in an H chassis, however recently we have tried to introduce two test hosts into the environment which are HP DL 380's. The problem we're running into is that the networking doe not seem to work quite right. We can add the hosts to our distributive switch and we vMotion between the "test" hosts and the "production" hosts without issue. But when the VM's are placed on the "test" hosts they can no longer communicate with the in-house network or the Internet. We've noticed that the vmkernel nic did not migrate when we added it to the vDS and we cannot migrate now either. The hosts keep giving us the "lost connectivity" error and they rollback. Research into this error has turned up no results, we have ensured that the vmkernel port was not locked for logging and have also tried re-installing ESXi. In addition to that we have also created a new vDS to allow them to talk to the Internet directly and have also had success with host to host communication but cannot get these hosts to communicate with our in-house network at all. The uplinks look good the physical ports are in the correct VLAN and we can vMotion them, we just cannot get these hosts and the VMs we put on them to talk to the in-house network. Any assistance is greatly appreciated.

Mike M.

0 Kudos
2 Replies
abhilashhb
VMware Employee
VMware Employee

Do these VM's sitting on the Test Host ping each other?

Abhilash B
LinkedIn : https://www.linkedin.com/in/abhilashhb/

0 Kudos
mousseau_45
Contributor
Contributor

Yes the VMs can communicate to each other while on the same test host as well as on different test hosts. In either scenario they can ping and communicate with each other.

0 Kudos