VMware Cloud Community
andymiller6891
Contributor
Contributor
‎03-07-2011 08:08 AM

Esxi Lan Support

I have an s3000ah intel server board running esxi with a perc 5i.

problem is only 1 of the lan ports are detected by esxi.

does anyone know if and how i can add in the support for the other lan port???

Thanks.

0 Kudos
23 Replies
Dave_Mishchenko
Immortal
Immortal
‎03-07-2011 08:19 AM

If you see page 34 here - http://download.intel.com/support/motherboards/server/s3000ah/sb/d72579003_s3000ah_tps_1_4.pdf - you'll see that you have two different models of NICs.  Once you determince which driver the 2nd NIC needs (e1000 or e1000e) you can check the drivers download page for an updated driver - http://downloads.vmware.com/d/info/datacenter_downloads/vmware_vsphere_4/4_0#drivers_tools that may support the model of NIC.  Otherwise you can manually try to load the driver (vmkload_mod) if one NIC uses the e1000 and the other the e1000e.  If that works then you need to edit simple.map (see the customizing oem.tgz article on vm-help.com).

0 Kudos
andymiller6891
Contributor
Contributor
‎03-07-2011 08:24 AM

It is the Intel 82541PI that seems to be missing a driver.

0 Kudos
andymiller6891
Contributor
Contributor
‎03-07-2011 08:42 AM

according to the simple.map for esxi 4.1 the 82541pi should be supported yet it isnt being picked up by esxi.

any ideas???

Thanks.

0 Kudos
Dave_Mishchenko
Immortal
Immortal
‎03-07-2011 08:45 AM

When you boot the server take a look through /var/log/messages.  You'll see a section where the e1000 driver is loaded.  It may report an error. The NIC was dropped from the HCL with the release of 4.0 .  It may indicate a problem with the driver or just that testing wasn't performed on it.

0 Kudos
Dave_Mishchenko
Immortal
Immortal
‎03-07-2011 08:46 AM

See my last post.

0 Kudos
DSTAVERT
Immortal
Immortal
‎03-07-2011 08:47 AM

Acording to the Hardware Compatibility List that card is not supported for ESX(i) 4.x. It did have support under 3.5

http://www.vmware.com/resources/compatibility/search.php?action=search&deviceCategory=io&productId=1...[]=-1&manufacturer[]=-1&vid=&did=&svid=&ssid=&rorre=0

-- David -- VMware Communities Moderator
0 Kudos
andymiller6891
Contributor
Contributor
‎03-07-2011 09:06 AM

ok, i just rebooted and this was the output from log when filtering out e1000/e1000e

Mar  7 17:01:09 vmkernel: 0:00:00:30.390 cpu1:4599)Loading module e1000e ...

Mar  7 17:01:09 vmkernel: 0:00:00:30.390 cpu1:4599)Elf: 2187: <e1000e> provides name-space <esx:nover>

Mar  7 17:01:09 vmkernel: 0:00:00:30.391 cpu1:4599)Elf: 1612: <e1000e> : R_X86_64_32 relocation(s) ignored

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)module heap vmklnx_e1000e: creation succeeded. id = 0x41000fc00000

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)<6>e1000e: Intel(R) PRO/1000 Network Driver - 1.1.2-NAPI

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)<6>e1000e: Copyright(c) 1999 - 2009 Intel Corporation.

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: driver e1000e is looking for devices

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)PCI: driver e1000e claimed device 0000:04:00.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.702 cpu1:4599)<4>e1000e 0000:06:00.0: Warning: detected ASPM enabled in EEPROM

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: driver e1000e claimed device 0000:06:00.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: driver e1000e claimed 2 devices

Mar  7 17:01:09 vmkernel: 0:00:00:31.103 cpu0:4599)Mod: 4163: Initialization of e1000e succeeded with module ID 31.

Mar  7 17:01:09 vmkernel: 0:00:00:31.103 cpu0:4599)e1000e loaded successfully.

Mar  7 17:01:10 vmkernel: 0:00:00:31.184 cpu0:4599)Loading module e1000 ...

Mar  7 17:01:10 vmkernel: 0:00:00:31.185 cpu0:4599)Elf: 2187: <e1000> provides name-space <esx:nover>

Mar  7 17:01:10 vmkernel: 0:00:00:31.186 cpu0:4599)Elf: 1612: <e1000> : R_X86_64_32 relocation(s) ignored

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)module heap vmklnx_e1000: creation succeeded. id = 0x4100b4000000

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: driver e1000 is looking for devices

Mar  7 17:01:10 vmkernel: 0:00:00:31.259 cpu0:4599)<3>e1000: 0000:07:05.0: e1000_probe: The NVM Checksum Is Not Valid

Mar  7 17:01:10 vmkernel: 0:00:00:31.396 cpu0:4599)PCI: driver e1000 claimed 0 device

Mar  7 17:01:10 vmkernel: 0:00:00:31.396 cpu0:4599)Mod: 4163: Initialization of e1000 succeeded with module ID 32.

Mar  7 17:01:10 vmkernel: 0:00:00:31.396 cpu0:4599)e1000 loaded successfully.

Mar  7 17:01:12 vmkernel: 0:00:00:33.599 cpu3:4360)<6>e1000e: vmnic2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Mar  7 17:01:12 vmkernel: 0:00:00:33.770 cpu2:4361)<6>e1000e: vmnic0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Mar  7 17:01:23 vmkernel: 0:00:00:44.587 cpu1:4359)<6>e1000e: vmnic0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Does that shed any light on the problem???

BTW i currently have a pci-e intel gigabit adapter installed to make the nic count upto 2, but as it is borrowed from a mail server it isnt a permanent fixture hopefully.

Thanks.

0 Kudos
andymiller6891
Contributor
Contributor
‎03-07-2011 09:11 AM

This is the whole log for the nic section.

Mar  7 17:01:09 vmkernel: 0:00:00:30.390 cpu1:4599)Loading module e1000e ...

Mar  7 17:01:09 vmkernel: 0:00:00:30.390 cpu1:4599)Elf: 2187: <e1000e> provides name-space <esx:nover>

Mar  7 17:01:09 vmkernel: 0:00:00:30.391 cpu1:4599)Elf: 1612: <e1000e> : R_X86_64_32 relocation(s) ignored

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)module heap : Initial heap size : 102400, max heap size: 5750784

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)module heap vmklnx_e1000e: creation succeeded. id = 0x41000fc00000

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)module skb heap : Initial heap size : 524288, max heap size: 23068672

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)module skb heap : creation succeeded

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)<6>e1000e: Intel(R) PRO/1000 Network Driver - 1.1.2-NAPI

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)<6>e1000e: Copyright(c) 1999 - 2009 Intel Corporation.

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: driver e1000e is looking for devices

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:00:01.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Announcing 0000:00:01.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:00:1c.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Announcing 0000:00:1c.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:00:1c.4

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Announcing 0000:00:1c.4

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:00:1c.5

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Announcing 0000:00:1c.5

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:00:1d.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:00:1d.1

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:00:1d.2

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:00:1d.3

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:00:1d.7

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:00:1f.2

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Announcing 0000:00:1f.2

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:00:1f.3

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Announcing 0000:00:1f.3

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:02:0e.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Announcing 0000:02:0e.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Trying 0000:04:00.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)PCI: Announcing 0000:04:00.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)VMK_PCI: 746: device 000:004:00.0 capType 16 capIndex 224

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)socket buffer cache creation succeeded for vmnic%d

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)Enabling MSI for dev 4:0.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)IntrVector: 283: 0xc0

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)VMK_PCI: 1115: device 000:004:00.0 allocated 1 vectors (intrType 2)

Mar  7 17:01:09 vmkernel: 0:00:00:30.392 cpu1:4599)VMK_PCI: 746: device 000:004:00.0 capType 16 capIndex 224

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)<6>0000:04:00.0: vmnic0: (PCI Express:2.5GB/s:Width x1) 00:15:17:1c:3e:0f

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)<6>0000:04:00.0: vmnic0: Intel(R) PRO/1000 Network Connection

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)<6>0000:04:00.0: vmnic0: MAC: 2, PHY: 4, PBA No: d50854-002

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)PCI: driver e1000e claimed device 0000:04:00.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)PCI: Registering network device 0000:04:00.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)VMK_PCI: 646: Device 000:004:00.0 name: vmnic2

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)Uplink: 11078: Device vmnic2 not yet opened

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)LinPCI: LinuxPCI_DeviceClaimed: Device 4:0 claimed.

Mar  7 17:01:09 vmkernel:

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)PCI: Trying 0000:06:00.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)PCI: Announcing 0000:06:00.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)VMK_PCI: 746: device 000:006:00.0 capType 16 capIndex 224

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)Enabling MSI for dev 6:0.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)IntrVector: 283: 0xc8

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)VMK_PCI: 1115: device 000:006:00.0 allocated 1 vectors (intrType 2)

Mar  7 17:01:09 vmkernel: 0:00:00:30.617 cpu0:4599)VMK_PCI: 746: device 000:006:00.0 capType 16 capIndex 224

Mar  7 17:01:09 vmkernel: 0:00:00:30.702 cpu1:4599)<4>e1000e 0000:06:00.0: Warning: detected ASPM enabled in EEPROM

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)<6>0000:06:00.0: vmnic0: (PCI Express:2.5GB/s:Width x1) 00:15:17:2c:73:54

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)<6>0000:06:00.0: vmnic0: Intel(R) PRO/1000 Network Connection

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)<6>0000:06:00.0: vmnic0: MAC: 3, PHY: 2, PBA No: ffffff-0ff

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: driver e1000e claimed device 0000:06:00.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: Registering network device 0000:06:00.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)VMK_PCI: 646: Device 000:006:00.0 name: vmnic0

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)Uplink: 11078: Device vmnic0 not yet opened

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)LinPCI: LinuxPCI_DeviceClaimed: Device 6:0 claimed.

Mar  7 17:01:09 vmkernel:

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: Trying 0000:06:00.3

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: Announcing 0000:06:00.3

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: Trying 0000:06:00.4

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: Announcing 0000:06:00.4

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: Trying 0000:07:04.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: Announcing 0000:07:04.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: Trying 0000:07:05.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: Announcing 0000:07:05.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)PCI: driver e1000e claimed 2 devices

Mar  7 17:01:09 vmkernel: 0:00:00:30.794 cpu1:4599)Uplink: 13003: Opening device vmnic2

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)IDT: 1036: 0xc0 <vmnic2> exclusive (entropy source), flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)VMK_VECTOR: 143: Added handler for  vector 192, flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)IDT: 1133: 0xc0 for vmkernel

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)VMK_VECTOR: 231: vector 192 enabled

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)IDT: 1565: 0xc0

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)IDT: 1634: <vmnic2>

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)Disabling MSI for dev 4:0.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)VMK_PCI: 1115: device 000:004:00.0 allocated 1 vectors (intrType 1)

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)Enabling MSI for dev 4:0.0

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)VMK_PCI: 1115: device 000:004:00.0 allocated 1 vectors (intrType 2)

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)IDT: 1036: 0xc0 <vmnic2> exclusive (entropy source), flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)VMK_VECTOR: 143: Added handler for  vector 192, flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)IDT: 1133: 0xc0 for vmkernel

Mar  7 17:01:09 vmkernel: 0:00:00:30.952 cpu1:4125)VMK_VECTOR: 231: vector 192 enabled

Mar  7 17:01:09 vmkernel: 0:00:00:31.012 cpu0:4125)IDT: 1565: 0xc0

Mar  7 17:01:09 vmkernel: 0:00:00:31.012 cpu0:4125)IDT: 1634: <vmnic2>

Mar  7 17:01:09 vmkernel: 0:00:00:31.012 cpu0:4125)Disabling MSI for dev 4:0.0

Mar  7 17:01:09 vmkernel: 0:00:00:31.012 cpu0:4125)VMK_PCI: 1115: device 000:004:00.0 allocated 1 vectors (intrType 1)

Mar  7 17:01:09 vmkernel: 0:00:00:31.012 cpu0:4125)Enabling MSI for dev 4:0.0

Mar  7 17:01:09 vmkernel: 0:00:00:31.012 cpu0:4125)VMK_PCI: 1115: device 000:004:00.0 allocated 1 vectors (intrType 2)

Mar  7 17:01:09 vmkernel: 0:00:00:31.012 cpu0:4125)IDT: 1036: 0xc0 <vmnic2> exclusive (entropy source), flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:31.013 cpu0:4125)VMK_VECTOR: 143: Added handler for  vector 192, flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:31.013 cpu0:4125)IDT: 1133: 0xc0 for vmkernel

Mar  7 17:01:09 vmkernel: 0:00:00:31.013 cpu0:4125)VMK_VECTOR: 231: vector 192 enabled

Mar  7 17:01:09 vmkernel: 0:00:00:31.013 cpu0:4599)NetPort: 982: enabled port 0x2 with mac 00:00:00:00:00:00

Mar  7 17:01:09 vmkernel: 0:00:00:31.013 cpu0:4599)Uplink: 13145: vmnic2 is opened

Mar  7 17:01:09 vmkernel: 0:00:00:31.013 cpu0:4599)Uplink: 13003: Opening device vmnic0

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)IDT: 1036: 0xc8 <vmnic0> exclusive (entropy source), flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)VMK_VECTOR: 143: Added handler for  vector 200, flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)IDT: 1133: 0xc8 for vmkernel

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)VMK_VECTOR: 231: vector 200 enabled

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)IDT: 1565: 0xc8

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)IDT: 1634: <vmnic0>

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)Disabling MSI for dev 6:0.0

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)VMK_PCI: 1115: device 000:006:00.0 allocated 1 vectors (intrType 1)

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)Enabling MSI for dev 6:0.0

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)VMK_PCI: 1115: device 000:006:00.0 allocated 1 vectors (intrType 2)

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)IDT: 1036: 0xc8 <vmnic0> exclusive (entropy source), flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)VMK_VECTOR: 143: Added handler for  vector 200, flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)IDT: 1133: 0xc8 for vmkernel

Mar  7 17:01:09 vmkernel: 0:00:00:31.042 cpu1:4125)VMK_VECTOR: 231: vector 200 enabled

Mar  7 17:01:09 vmkernel: 0:00:00:31.102 cpu0:4125)IDT: 1565: 0xc8

Mar  7 17:01:09 vmkernel: 0:00:00:31.102 cpu0:4125)IDT: 1634: <vmnic0>

Mar  7 17:01:09 vmkernel: 0:00:00:31.102 cpu0:4125)Disabling MSI for dev 6:0.0

Mar  7 17:01:09 vmkernel: 0:00:00:31.102 cpu0:4125)VMK_PCI: 1115: device 000:006:00.0 allocated 1 vectors (intrType 1)

Mar  7 17:01:09 vmkernel: 0:00:00:31.102 cpu0:4125)Enabling MSI for dev 6:0.0

Mar  7 17:01:09 vmkernel: 0:00:00:31.102 cpu0:4125)VMK_PCI: 1115: device 000:006:00.0 allocated 1 vectors (intrType 2)

Mar  7 17:01:09 vmkernel: 0:00:00:31.102 cpu0:4125)IDT: 1036: 0xc8 <vmnic0> exclusive (entropy source), flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:31.102 cpu0:4125)VMK_VECTOR: 143: Added handler for  vector 200, flags 0x10

Mar  7 17:01:09 vmkernel: 0:00:00:31.102 cpu0:4125)IDT: 1133: 0xc8 for vmkernel

Mar  7 17:01:09 vmkernel: 0:00:00:31.103 cpu0:4125)VMK_VECTOR: 231: vector 200 enabled

Mar  7 17:01:09 vmkernel: 0:00:00:31.103 cpu1:4599)NetPort: 982: enabled port 0x3 with mac 00:00:00:00:00:00

Mar  7 17:01:09 vmkernel: 0:00:00:31.103 cpu0:4599)Uplink: 13145: vmnic0 is opened

Mar  7 17:01:09 vmkernel: 0:00:00:31.103 cpu0:4599)Mod: 4163: Initialization of e1000e succeeded with module ID 31.

Mar  7 17:01:09 vmkernel: 0:00:00:31.103 cpu0:4599)e1000e loaded successfully.

Mar  7 17:01:09 vmkernel:

Mar  7 17:01:10 vmkernel: 0:00:00:31.184 cpu0:4599)Loading module e1000 ...

Mar  7 17:01:10 vmkernel: 0:00:00:31.185 cpu0:4599)Elf: 2187: <e1000> provides name-space <esx:nover>

Mar  7 17:01:10 vmkernel: 0:00:00:31.186 cpu0:4599)Elf: 1612: <e1000> : R_X86_64_32 relocation(s) ignored

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)module heap : Initial heap size : 102400, max heap size: 5750784

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)module heap vmklnx_e1000: creation succeeded. id = 0x4100b4000000

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)module skb heap : Initial heap size : 524288, max heap size: 23068672

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)module skb heap : creation succeeded

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)<6>Intel(R) PRO/1000 Network Driver - version 8.0.3.2-1vmw-NAPI

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)<6>Copyright (c) 1999-2008 Intel Corporation.

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: driver e1000 is looking for devices

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:00:01.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Announcing 0000:00:01.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:00:1c.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Announcing 0000:00:1c.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:00:1c.4

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Announcing 0000:00:1c.4

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:00:1c.5

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Announcing 0000:00:1c.5

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:00:1d.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:00:1d.1

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:00:1d.2

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:00:1d.3

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:00:1d.7

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:00:1f.2

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Announcing 0000:00:1f.2

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:00:1f.3

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Announcing 0000:00:1f.3

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:02:0e.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Announcing 0000:02:0e.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:04:00.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:06:00.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:06:00.3

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Announcing 0000:06:00.3

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:06:00.4

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Announcing 0000:06:00.4

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:07:04.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Announcing 0000:07:04.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Trying 0000:07:05.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)PCI: Announcing 0000:07:05.0

Mar  7 17:01:10 vmkernel: 0:00:00:31.187 cpu0:4599)socket buffer cache creation succeeded for vmnic%d

Mar  7 17:01:10 vmkernel: 0:00:00:31.259 cpu0:4599)<3>e1000: 0000:07:05.0: e1000_probe: The NVM Checksum Is Not Valid

Mar  7 17:01:10 vmkernel: 0:00:00:31.396 cpu0:4599)PCI: driver e1000 claimed 0 device

Mar  7 17:01:10 vmkernel: 0:00:00:31.396 cpu0:4599)Mod: 4163: Initialization of e1000 succeeded with module ID 32.

Mar  7 17:01:10 vmkernel: 0:00:00:31.396 cpu0:4599)e1000 loaded successfully.

Mar  7 17:01:10 vmkernel:

0 Kudos
Dave_Mishchenko
Immortal
Immortal
‎03-07-2011 12:02 PM

Is there any IRQ sharing for that NIC or devices in conflict with it?  You might need to compile a new driver for it.  If you search for The NVM Checksum Is Not Valid the problem doesn't seem to be limited to ESXi (but rather a Linux source issue).

andymiller6891
Contributor
Contributor
‎03-07-2011 12:05 PM

is there any way of finding out if it is sharing an irq?? and what do you mean by compile a new driver???

im not really a linux guy but i am picking up shh on esxi with putty.

i have checked my simple.map and the 82541pi is in the list and also in my pci.ids.

0 Kudos
Dave_Mishchenko
Immortal
Immortal
‎03-07-2011 12:14 PM

You can use lspci -p to check that. pci.ids just provides text descriptions for hardware devices that are displayed in the console, vSphere client, etc.  Simple.map directs ESXi which drivers to load, but inclusion on that list doesn't guarantee that a device will work.  If the problem is with the driver (and perhaps that explains why it's not on the 4.x HCL) then you'd be better off adding something like an Intel Pro 1000 GT.  Compiling a driver is a bit of a task (I'm no expert on it) and  dropping in another NIC would be far quicker.

0 Kudos
andymiller6891
Contributor
Contributor
‎03-07-2011 12:17 PM

i just purchased a dual port pro1000ct pci-e this evening from ebay, hopefully have more luck with that.

0 Kudos
andymiller6891
Contributor
Contributor
‎03-07-2011 12:27 PM

i just listed my hardware and it shows 3 lan cards instead of the 2 im using.

maybe this may help.

http://img716.imageshack.us/img716/6636/screengrabk.jpg  

it seems to be vnic1 that my system wont use.

0 Kudos
Dave_Mishchenko
Immortal
Immortal
‎03-07-2011 12:33 PM

If you disable vmnic0 in the BIOS does that make a difference?  I'm not suggesting that as the solution.  🙂 Once a device is recognized for storage or network it'll get the vmnic or vmhba label, but the driver may still not load properly (in your cases you'll note that the module is missing for that NIC).

0 Kudos
andymiller6891
Contributor
Contributor
‎03-07-2011 12:33 PM

deleted.

0 Kudos
Dave_Mishchenko
Immortal
Immortal
‎03-07-2011 12:39 PM

The following command loads the driver manually.  If a driver can work with a device, it will claim it.  vmkload_mod e1000 In your original log file you had the following: Mar  7 17:01:10 vmkernel: 0:00:00:31.259 cpu0:4599)<3>e1000: 0000:07:05.0: e1000_probe: The NVM Checksum Is Not Valid Mar  7 17:01:10 vmkernel: 0:00:00:31.396 cpu0:4599)PCI: driver e1000 claimed 0 device So the e1000 driver is loading, but can claim (communicate properly) with the NIC.

0 Kudos
andymiller6891
Contributor
Contributor
‎03-07-2011 12:53 PM

being as this card seems to be supported in 3.5 would there be any reason apart from going to a 32bit system not to downgrade down to 3.5 and what complications will that have on my already functioning vm's???

0 Kudos
andymiller6891
Contributor
Contributor
‎03-07-2011 12:58 PM

According to the intel manual this particular nic shares irqs with the onboard video, I believe.

Sent from my BlackBerry® wireless device

0 Kudos
andymiller6891
Contributor
Contributor
‎03-07-2011 01:06 PM

Essentially my problem is for what i want to do i need 4 lan connections without packing out my pci-e's as im saving the 8x for an extra perc5i.

there is a pci 4x left which i plan to put in the dual lan card i just brought, so ideally i need the onbard 2 working as i have 2 seperate WAN connections and 2 seperate subnets that i wanted 1 physical lan connection for.

without going crazy and buyint a 4 port lan card which i wouldnt have a slot for anyway then 2 onboards and 2 on single card is the best way.

0 Kudos