Esxi 5.1 Virtual Machine can't connect

[Kkweit93lr]

Hi,

Got a problem with Esxi 5.1 host. When I create a Virtual Machine it can't connect to the LAN.

The ESXi host can connect but not the Virtual Machine whatever the OS i put on it.

Think that it might be a network configuration problem on the host but don't what i did wrong.

Does anybody have a clue ?

[nielse]

Can you double check if the NIC is connected and if "connect at power on" is checked in the settings?

[Kkweit93lr]

Already done ! I'm connecting to the host through SSH and/or Vsphere client.

Think that i can resolve this by doing the good configuration through Vsphere client but what do i have to change ?

Here is the question ! Am i wrong ?

[nielse]

Normally if you create a new virtual machine with a network interface it should be connected (using the vSphere client and the wizard). Unless you added the nic afterwards it might happen that it doesn't get connected.

Good thing your problem is solved .

[Kkweit93lr]

Maybe i did click on the bad button but my problem isn't solved ! I'm still looking for a solution !

[jrmunday]

it can't connect to the LAN.

Could you please clarify this point so that we can understand the issue further?

Can you also please provide details of how your networing is configured?

If it helps you can post the results of this DCUI command so that we can analyse this further;

~ # esxcli network  vswitch standard list

or this if you are using Distributed switches;

~ # esxcli network  vswitch dvs vmware list

Thanks,

Jon

[Kkweit93lr]

I don't know how to be more clear than that

Got an ESXi 5.1 host running on a LAN (Local Area Network). Know that network is working on my host because i can connect through vsphere and ssh.

Problem is with the virtual machine which can't do the same thing. Can't see the VM on network I can't ping it and it can't ping the gateway either

In previous version of esxi or vcenter (don't remeber exactly) there was a place where you were supposed to specifiy the way your VM receive network from the host. Was it with NAT or a Bridge.

I think that if i found out how do that it may solve my problem.

What do you think about that ?

@jrmunday :

# esxcli network  vswitch standard list

vSwitch0

   Name: vSwitch0

   Class: etherswitch

   Num Ports: 128

   Used Ports: 7

   Configured Ports: 128

   MTU: 1500

   CDP Status: listen

   Beacon Enabled: false

   Beacon Interval: 1

   Beacon Threshold: 3

   Beacon Required By:

   Uplinks: vmnic1, vmnic0

   Portgroups: VM Network, Management Network

[nielse]

The thing you are referring is workstation. In ESXi you add a network card to the virtual machine (under edit settings). I presume you have one attached to it. Are you using VLAN's by any chance in your network?

[Kkweit93lr]

Sorry i'm not english nor american so my english may have some wrong words or sentenses but I never aimed at talk about workstation

No I'm not using VLAN

[nielse]

I know you are talking about ESXi but the bridged/NAT thing is something which is in Workstation not in ESXi . Anyhow not relevant.

What type of OS are you running the guest? Could you maybe attach some screenshots:

- Networking settings on the host

- VM settings (especially the network card)

[Kkweit93lr]

If wasn't Esxi it might be some similar server. Saw it running in previous job office and it was kind of an old thing. Don't remember the name anyway

I can say for  sure that the problem don't come from the VM.

I did create 3 VM:1 linux, 1 Win2008r2, 1 BSD

None of them can ping the gateway nor the host

I tried both network adaptor E1000 & VMXNET 3 but it doesn't seems to change anything.

I quite sure that it's a network setting problem.

What information do you need to help me ?

[jrmunday]

Ok, I can see see that you have a single vSwitch with 2x uplinks and 2x port groups (one for guest networking and the other for management).

   Name: vSwitch0

   Uplinks: vmnic1, vmnic0

   Portgroups: VM Network, Management Network

Using the vSphere Client, select your host, select the configuration tab, select Networking. You should see this configuration represented graphically on the right. Now click on the callout icon to the right of vmnic0 and vmnic1 to see the CPD information to see the switches and ports.

I assume that you are using access ports, instead of trunk ports with VLAN tagging - is this correct? How are these ports configured?

[Kkweit93lr]

Hi,

Thanks for your answer.

Yes i'm not using trunk but you can see it as a problem too since i want to use access port where i have to configure it.

Esxi 5.1 is a fresh install ! Thought it wouldn't be so complicated !

How fool am i made the install in french. It should not be a problem since i'm french but when you learn about computers in France words like "switch" are not being translated. The problem is that on the vsphere client everything is in french and there is some french words i don't know what they mean.

Got two physical adaptators vmnic0 and vmnic1. The first one appear to be unused. 

here is vmnic1 configuration:

Router : no

transparent gateway : no

source route bridge: no

network switch: yes

host: no

IGMP: yes

[jrmunday]

everything is in french and there is some french words i don't know what they mean.

... Afraid I cant help with this this - I'm South African so most French words I dont understand

Have a look at this thread where we discussed segregating services through the network configuration as it will give you a good understanding of how this is achieved;

http://communities.vmware.com/message/2147099#2147099

Yes i'm not using trunk but you can see it as a problem too since i want to use access port where i have to configure it.

Since you are not using trunk ports and both your port groups are on the same vSwitch with both uplinks (vmnic0 and vmnic1) then your management network and guest networks need to use the same subnet (not recommended - refer to the link above for segregation).

[Kkweit93lr]

What do you mean by "Guest network" ? Are you talking about my VM's network ?

If you are then you got to know that all of them are on the same subnet.