virtualteam
Contributor
Contributor

Prob with nic driver after vmware tools installation

Jump to solution

Hello,

I have 3 ESX 3.5 Update 3 and a VC 2.5 Update 4. I have updated one ESX to release 3.5.0 153875. I have also updated the vlmware client on each vm on this esx server. When i restart the vm (Linux Redhat 5.2 or Windows 2K or Windows2003,) i can't ping the vm during +- 5 minutes from my pc but that works if i do a ping from a vm in the same vswitch. If i disable/enabled the network device, i can ping directly.

If i remove the vmware-tools i can ping directly after a restart ...

Thank you for your help

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
kjb007
Immortal
Immortal

Very strange. Try using a different NIC type, enhanced vmxnet, and see if you see the same behavior. There may be a bug with latest release, and if this continues, you can open an SR with vmware.

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB

View solution in original post

0 Kudos
18 Replies
kjb007
Immortal
Immortal

What type of NIC are you using in your vm's? Is the problem with all of the vm's on one ESX host, or different vm's different ESX hosts and not all vm's?

If you're having an issue, but can ping vm's on the same vSwitch, then they're not going out to the physica switch and back. Have you checked port settings on the physical switch as well?

If you're using enhanced vmxnet, then the driver is loaded with the vmware tools. Flexible will behave one way without the tools, and another way after the tools are loaded.

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
0 Kudos
virtualteam
Contributor
Contributor

for windows 2003 i use : vmware accelerated PCNet Adapter

for windows 2000 i use : the same

for linux : i use the vmxnet driver and now that's work

All are flexible type

I have the problem on all my cluster (3 ESX) but i have another cluster with the same hardware and with the same configuration (vswitch and link failure) buth with VC update 3 and ESX3.5.0, 130756 whitout any problem

0 Kudos
kjb007
Immortal
Immortal

Have you verified the configuration is the same on the physical switch side? If you can ping the vm correctly from within a vm on the same vSwitch, then there may be a misconfiguration on the physical switch that your ESX hosts connect to.

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
0 Kudos
virtualteam
Contributor
Contributor

I think it's working because if a remove the vmware tools or repair the network card (via windows) , all works fine

And i have the same configuration on another place whitout this problem

How can i explain that without vmware-tools all works fine ?

0 Kudos
kjb007
Immortal
Immortal

With the flexible NIC, without vmware tools, you are using the AMD VLance driver, and with vmware tools, you are using the vmxnet driver. The difference here is the driver being used. Maybe there is a problem with the vmware tools installation. Have you tried to reinstall vmware tools?

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
0 Kudos
virtualteam
Contributor
Contributor

i have removed, installed the vmware-tool agin.

It's working fine until the tird reboot ... no ping agin.

0 Kudos
kjb007
Immortal
Immortal

Very strange. Try using a different NIC type, enhanced vmxnet, and see if you see the same behavior. There may be a bug with latest release, and if this continues, you can open an SR with vmware.

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB

View solution in original post

0 Kudos
virtualteam
Contributor
Contributor

It's working now, thank you for your help

0 Kudos
virtualteam
Contributor
Contributor

just a problem : i can't use this driver with windows 2000 ... must i use e1000 instead of ?

0 Kudos
kjb007
Immortal
Immortal

Was the 2000 server a new vm or from a P2V?

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
0 Kudos
virtualteam
Contributor
Contributor

from a convertion

I have seen this message : http://communities.vmware.com/message/1210285#1210285

0 Kudos
kjb007
Immortal
Immortal

You may have some hidden devices that may be causing conflicts when starting up. Open a dos prompt, run set DEVMGR_SHOW_NONPRESENT_DEVICES=1. Then open device manager, and in view, select show hidden devices. Then, make sure there are no devices still present from the conversion. Most probably, there are additional network devices and drivers causing problems.

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
0 Kudos
virtualteam
Contributor
Contributor

The W2000 is clean now and i have still the problem

I have also a w2003 (fresh installation) and i have the same problem

0 Kudos
kjb007
Immortal
Immortal

Have you modified your vSwitch properties? Specifically the notify switch option, either on your vSwitch properties or portgroup properties?

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
0 Kudos
virtualteam
Contributor
Contributor

I don't have changed default valueas you can see with the attachements

0 Kudos
kjb007
Immortal
Immortal

Very strange indeed. I'm all out of ideas on the 2000 box. I have flexible and enhanced in my environment and don't see what you're seeing. I would suggest opening an SR with vmware and have them take a look at your config.

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
0 Kudos
virtualteam
Contributor
Contributor

i ha ve the same problem with a windows xp machine, .... ( fresh installation)

Thank you for your help

0 Kudos
virtualteam
Contributor
Contributor

Ok i have resolved the problem :

1. make a bonding configuration whit same controllers

2. upgrade the switch's firmware

3. found the duplicate ip adress

Thank you

0 Kudos