01-05-2011 09:14 AM
Hi everyone,
first time posting here.
i have an issue that i can't seem to figure out. here's my environment:
:nexus 1000v (4.0.1.SV1.2) running on ESX version 4.0 Update 1
:2 x nexus 2000; 2 x nexus 5000 (i'm not the cisco engineer at my work so i don't have all the necessary info here)
:virtual machines that are running windows 2003 enterprise; these VM's are using E1000 virtual NIC
:the E1000's are connected to the nexus1000v
:the nexus1000v has two uplink ports; one uplink is connected to one nexus 2000 and the other uplink is connected to another nexus 2000
:the nexus 2000s are connected to two nexus 5000s
:a physical sql server (windows 2008 R2) is connected to one of the nexus 2000
Here's my issue:
:the 4 VM's that are configured with E1000 and are connected to the nexus1000v switch can't communicate with the physical sql server
:if i changed the e1000 NIC to a vmxnet3 NIC, it WORKS!
:if i move the VM (using the e1000 NIC) from the nexus1000v switch to the regular vStandard switch (vmware regular switch), it WORKS!
:if i use a different vLAN on the e1000 NIC, it WORKS!
:the problem seems to be only isolated to these 4 VM's: other VM's don't have communication issues with the physical server using different network configurations (different NIC type or different vLANs, or different type for virtual switch)
why is it that my problem seems to be isolated to those 4 VM's? Why is it that using a new type of virtual NIC (vmxnet3) would work inside the nexus1000v?
I'm running out of ideas...
01-05-2011 09:59 PM
Can you provide output of esxupdate query
There was a VMware bug that affected 1000v operation only with the e1000 driver in some VMs. This was fixed in a patch released by VMware. I'm looking up the info now - hang in there.
Easy workaround is to use the recommended VMXNET3 adapter instead, unless there's some driving reason you need to use the e1000.
Regards,
Robert
01-06-2011 09:04 AM
we have no issues going to vmxnet3 since that is where we want to go anyway. what's puzzling is that the problem is not consistent throughout. anyway, here's the esxupdate query on one of the esx host:
ESX400-Update01 2010-08-05T04:06:16 VMware ESX 4.0 Complete Update 1
ESX400-201002408-BG 2010-08-06T22:31:07 Updates Enic driver
ESX400-201006201-UG 2010-08-06T22:31:07 Updates the VMware ESX 4.0 Core and CIM components
ESX400-201006202-UG 2010-08-06T22:31:07 Updates the VMware ESX 4.0 mpt2sas device driver
ESX400-201006203-UG 2010-08-06T22:31:07 Updates the VMware ESX 4.0 mptsas, mptspi device drivers
ESX400-201006204-UG 2010-08-06T22:31:07 Updates the VMware ESX 4.0 fnic device driver
ESX400-201006205-UG 2010-08-06T22:31:07 Updates the ESX 4.0 SCSI/iSCSI driver
ESX400-201006211-UG 2010-08-06T22:31:07 Updates the VMware ESX 4.0 nx-nic device driver
ESX400-201006212-UG 2010-08-06T22:31:07 Updates the VMware ESX 4.0 bnx2x device driver
ESX400-201006214-UG 2010-08-06T22:31:07 Updates the VMware ESX 4.0 cciss device driver
ESX400-201006215-UG 2010-08-06T22:31:07 Updates Driver for VMware ESX 4.0 HP SAS Controllers
ESX400-201006217-UG 2010-08-06T22:31:07 Updates the ESX 4.0 python component
ESX400-201006218-UG 2010-08-06T22:31:07 Updates the VMware ESX 4.0 SCSI lpfc820 device driver
ESX400-201006219-UG 2010-08-06T22:31:07 Updates the VMware ESX 4.0 ATA libata device driver
ESX400-201006220-UG 2010-08-06T22:31:07 Updates the ESX 4.0 Megaraid SAS device driver
ESX400-201006224-UG 2010-08-06T22:31:07 Updates the ESX 4.0 initscripts rpm
ESX400-201006225-UG 2010-08-06T22:31:07 Updates the ESX 4.0 Web Access components
ESX400-201006226-UG 2010-08-06T22:31:07 Updates the VMware ESX 4.0 EHCI HCD device driver
EMC-PP5.4.1.00.00-b033 2010-08-09T13:02:13 PowerPath 5.4.SP1 for ESX
VEM400-201006011-BG 2010-08-29T00:25:07 Cisco Nexus 1000V VEM
thanks for the feedback.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide