Overclock.net › Forums › Specialty Builds › Servers › ESXi VM networking issues, can't figure out.
New Posts  All Forums:Forum Nav:

ESXi VM networking issues, can't figure out.

post #1 of 9
Thread Starter 
I need a bit of help here.

I'm coming from hyper-v. I wanted to try out ESXi so I loaded all of my four C6100 nodes with ESXi 5.5. All of C6100 are connected to a switch, and this switch is local only, additionally, I have my laptop connected to the switch as well. No internet here.

I've installed ESXi, and made my first VM, a windows 2012R2 with address of 192.168.0.205. Noticed something was wrong.

First node has 192.168.0.201 as mgmt IP. My laptop has 192.168.0.99, in the VM I can't get to laptop or the VM ping each to other, however I can ping to the root os, and other nodes. The VM can ping 192.168.0.201 as well 192.168.0.202 but cannot ping 192.168.0.99, my laptop can ping 201/202 but can't ping 205.

All of them has 255.255.255.0 subnet

Laptop: 192.168.0.99
Node0: 192.168.0.201
Node1: 192.168.0.202
VM00: 192.168.0.205

cbc95209de.png

Does anyone have any suggestions?
post #2 of 9
Are you sure the vswitches are inheriting the security attributes properly and using the adapter? Also, if you're not going to use ipv6, turn it off just to make sure it's not interfering.

post #3 of 9
Thread Starter 
Quote:
Originally Posted by herkalurk View Post

Are you sure the vswitches are inheriting the security attributes properly and using the adapter? Also, if you're not going to use ipv6, turn it off just to make sure it's not interfering.


post #4 of 9
That box has more than one nic per node, have you tried making a vswitch on another nic for your guest communication? It all looks correct. We just implemented a similar vswitch due to vshield connecting to our hosts. We have an isolated vmware management network, layer 1 separated from the rest of the network. I haven't had any issues, the vcenter server communicates with the guest attached to the management network without problem. But yeah, for testing purposes please try another nic to ensure that at least you can communicate with the guest, host and remote laptop.

I'm not a VCP, but I've been working with ESXI in production for 3 years and it's always had weird quirks.
post #5 of 9
Thread Starter 
Yep I did, I've mess around with numberous settings and configurations. none of them worked. everything is back to default.
post #6 of 9
I don't see at first glance why this shouldn't work, however do note that the C6100 is not on VMware's list of supported hardware for ESXi 5.5.
It is on the ESXi 5.1 compatibility list, though. Since you don't really have anything configured, do you care to overwrite 5.5 with 5.1 instead and see what happens?
post #7 of 9
Stick with Hyper-V and it will work. Simple.

smile.gif
post #8 of 9
Thread Starter 
Quote:
Originally Posted by tycoonbob View Post

Stick with Hyper-V and it will work. Simple.

smile.gif
HAHAHA. I still have hyper-v's.

ESXi is truly it's own world, I still don't know what to say, but, hyper-v has been serving me good, it's all due to the mirco****'s failover-clustering that is making me consider the alternatives such as ESXi.
post #9 of 9
Quote:
Originally Posted by Zankza View Post

HAHAHA. I still have hyper-v's.

ESXi is truly it's own world, I still don't know what to say, but, hyper-v has been serving me good, it's all due to the mirco****'s failover-clustering that is making me consider the alternatives such as ESXi.

Honestly, the days of thinking ESXi is better than Hyper-V are gone. Hyper-V is a great product, and definitely has VMware's attention (hence the releasing of features that used to be paid only, and lowering prices of ESXi). Adoption rates are slow mainly because a lot of companies are so embedded with ESXi it's hard to make a change that's cost effective.

Anyway, what is the problem with Failover Clustering that you have? For me, it's generally rock solid (especially with Server 2012 R2).
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Servers
Overclock.net › Forums › Specialty Builds › Servers › ESXi VM networking issues, can't figure out.