Ping Latency in one virtual Machine on ESX 3.0.1

[MalozO]

I have a 3 Virtual Machines on 1 ESX 3.0.1, when ping the firt machne every good, when ping second machine every good but ping the third mcachind the results:

Respuesta desde 172.29.55.13: bytes=32 tiempo=2424ms TTL=64

Respuesta desde 172.29.55.13: bytes=32 tiempo=12ms TTL=64

Respuesta desde 172.29.55.13: bytes=32 tiempo=122ms TTL=64

Respuesta desde 172.29.55.13: bytes=32 tiempo=90ms TTL=64

Respuesta desde 172.29.55.13: bytes=32 tiempo=156ms TTL=64

Respuesta desde 172.29.55.13: bytes=32 tiempo=33ms TTL=64

Respuesta desde 172.29.55.13: bytes=32 tiempo=69ms TTL=64

Respuesta desde 172.29.55.13: bytes=32 tiempo=88ms TTL=64

i have a full patched my esx but i dont understand ..... I need hel my friends......

Thanks!

[rubensluque]

Are the three virtual machines in the same Virtual Switch ?

[Rumple]

If the service console is busy it might cause this issue although I would expect it to be slow for all vm's.

Is that VM itself busy or are the other VM's really busy and have a higher priority?

Does the problematic VM have the vmware tools installed and if so, is it using the flexible network card. If its using the vlance driver that might cause problems with latency due to the cpu resources required for that driver.

Are all 3 machines using the same vswitch and physical network card. If you have a bonded physical nics it could be that 2 of the vm;s are running across pnic1 and the other is running on pnic2 indicating a bad nic, cable or duplex/speed issue on that card.

[MalozO]

yes i have a three machines in one virtual swhitch.....

[virtualdud3]

Are you able to ping the other two VMs from the VM that you are not able to ping from the service console?

Are you sure that the problem VM's virtual NICs are connected to the same portgroup?

Are the problem VM's virtual NICs connected at all?

Are you sure that the problem VM is able to obtain an IP address?

I would start out by confirming these; please do so and we can go from there.

[MalozO]

Are you able to ping the other two VMs from the VM that you are not able to ping from the service console? YES I DO

Are you sure that the problem VM's virtual NICs are connected to the same portgroup? TEs same PortGroup

Are the problem VM's virtual NICs connected at all? YES ALL

Are you sure that the problem VM is able to obtain an IP address? IP FIXED

I would start out by confirming these; please do so and we can go from there.

and i have a 1 ethernet and 3 vm. Windows 2003, HP Blade C Class

[virtualdud3]

Okay, a couple more questions:

Is the problem VM on the same subnet/network as the other VMs?

From the problem VM, are you able to ping it's defalt gateway? What about an external IP address?

Are you using any VLANs?

[MalozO]

Okay, a couple more questions:

Is the problem VM on the same subnet/network as the other VMs? YES In the same Subnet (55) but is only Mchine(55.13) have the problem

From the problem VM, are you able to ping it's defalt gateway? Yes Have a ping What about an external IP address? I Dont Have

Are you using any VLANs? Yes!

The machine dont have a virus, Full updated with Microsoft update.etc

[rubensluque]

Is this virtual machine on VLAN 1 ? VMware does not recommend use VLAN number 1 because it could generate a conflict with your physical switch. The most of switches use VLAN 1 as a default VLAN.

[MalozO]

[IMG]http://img135.imageshack.us/img135/1981/123jl1.th.jpg[/IMG][/URL]

VLAN ID *

[jp-H]

Hi Malozo,

I saw that your 3 VM are on the same vswitch, but not on the same portgroup (in your picture).

Is the VM having the problem alone in the last portgroup ?

Do you use 802.1Q (vlan tagging) for the portgroup ?

[MalozO]

[IMG]http://img232.imageshack.us/img232/4236/1234rn4.th.jpg[/IMG][/URL]

The machine with problems is in the same portgroup of vswitch1 see the picture

Do you use 802.1Q (vlan tagging) for the portgroup ? how to????

Regards

[MalozO]

My configuration:

# esxcfg-vswitch -l

Switch Name Num Ports Used Ports Configured Ports Uplinks

vSwitch0 32 3 32 vmnic0

PortGroup Name Internal ID VLAN ID Used Ports Uplinks

VM Network portgroup1 0 0 vmnic0

Service Console portgroup0 0 1 vmnic0

Switch Name Num Ports Used Ports Configured Ports Uplinks

vSwitch1 64 5 64 vmnic1

PortGroup Name Internal ID VLAN ID Used Ports Uplinks

Red 37 portgroup5 65 0 vmnic1

Red 33 portgroup4 55 1 vmnic1

Red 55 Servidores VMportgroup6 255 2 vmnic1

-

---

# esxcfg-nics -l

Name PCI Driver Link Speed Duplex Description

vmnic0 02:03.00 bnx2 Up 1000Mbps Full Broadcom Corporation Broadcom

NetXtreme II BCM5706 1000Base-SX

vmnic1 02:04.00 bnx2 Up 1000Mbps Full Broadcom Corporation Broadcom

NetXtreme II BCM5706 1000Base-SX

# esxcfg-nics -l

Name PCI Driver Link Speed Duplex Description

vmnic0 02:03.00 bnx2 Up 1000Mbps Full Broadcom Corporation Broadcom

vmnic1 02:04.00 bnx2 Up 1000Mbps Full Broadcom Corporation Broadcom

-

---

....

[jp-H]

Vlan tagging (802.1Q) is used to carry multiple vlans on one nic port. In this case each vlan has a tag (from 1 to xxx, and 1 is not a good choice). The tag is given by your switch or router and ESX is able to separate the different vlans in the port correct port switch.

here is an example of esxcfg-vswitch -l :

Switch Name Num Ports Used Ports Configured Ports Uplinks

vSwitch1 64 7 64 vmnic1,vmnic2

PortGroup Name Internal ID VLAN ID Used Ports Uplinks

TEST-74 portgroup15 74 0 vmnic2,vmnic1

TEST-735 portgroup3 735 0 vmnic2,vmnic1

In this case I made a vswitch using two nics (for fault tolerance) and two port groups :test-74 and test-735 deserving vlan 74 for the first and 735 for the second.

For example Vlan 74 is for IP adresses 10.10.74.0 to 10.10.74.255 for example, and vlan 735 is for IP adresses 10.15.73.0 to 10.15.73.255 (all vlan uses 255.255.255.0 mask in this case).

All of this is made by the external router, and vswitch is carying the trafic to VM using the good port group for each vlan.

In your case, I am afraid you try to use one port group for mulitple vlans.

Ask to your network team if they use 802.1Q.