It is quite ok. I fixed this by building custom drivers and adding it to oem info. Works for the last couple of months like a charm!
If you guys are interseted, I can post the oem (custom built) to assist any of you.
as stated in my post. It works with my custom built oem
I would very much appreciate it if you could post your oem file!
Here it is.
The following files are included:
1. rsync - installed into the /bin directory.
2. simple.map - installed in the /etc/vmware directory
3. r8169.o - installed in the /usr/lib/vmware/vmkmod directory.
I run 2 machines with 4* DGE-528T and it works like a charm.
ps - I include rsync into all my oem's to make it easier to transfer files...
oem.tgz 444.7 K
Thanks for that Aubrey,
That doesn't seem to have made much difference for us though, is r8169.o the D-Link driver?
Thanks again, we're still working on it
1. Did you put the OEM.TGZ in the correct directory?
1.a. mine is in /vmfs/volumes/<volid>/
1.b. You can do a "tar -ztvf oem.tgz" to test the current file mentioned in 1.a. - it should be empty - replace it with mine.
1.c. If everything works with the reboot, you should have the respective files in the directories as specified.
1.d. You can test this by checking if rsync is in /bin/
1.e. simple.map adds the entry for the driver to your system.
NOTE: You only need the last entry, the rest you should get from your own simple.map. The last entry reads:
1186:4300 0000:0000 network r8169
The 1186:4300 you get from your "lspci -n"
1.f. r8169.o is the driver and should after a reboot end up in your /usr/lib/vmware/vmkmod/ directory.
2. Did you reboot your machine?
3. Do you get the following entry with a "lspci"?000:008:03.0 Network controller: D-Link System Inc DGE-528T Gigabit Ethernet Adapter [vmnic2]000:008:04.0 Network controller: D-Link System Inc DGE-528T Gigabit Ethernet Adapter [vmnic3]and with "lspci -n":
000:008:03.0 Class 0200: 1186:4300 [vmnic2]
000:008:04.0 Class 0200: 1186:4300 [vmnic3]
4. The correct way the driver should be installed is:
4.a. go to the directory where your oem.tgz resides.
4.b. mkdir test; cd test (You are going to do all your edits in TEST)
4.c. tar -zxvf my oem.tgz (this will extract the attached oem.tgz with all the drivers and more)
4.d. mv etc/vmware/simple.map etc/vmware/simple.map.orig (You only want the last line in my map file)
4.e. cp /etc/simple.map etc/vmware/ (You are going to add my entry to your map file)
4.f. vi etc/vmware/simple.map.orig and delete all the lines except the last line.
NOTE: MATCH YOUR ENTRY WITH YOUR lspci -n!!!
4.g. cat etc/vmware/simple.map.orig >> etc/vmware/simple.map (You are going to add my entry to your map file)
4.h. rm oem.tgz etc/vmware/simple.map.orig (Clean up after yourself)
4.i. tar -zcvf oem.tgz (Create your custom oem.tgz)
4.j. cp oem.tgz .. (Copy to the correct directory, overwriting the empty oem.tgz)
Reboot your system.
Please come back to me if there is still a problem.
i got it to work perfectly fine, thanks man,
Many thanks for taking the time to post the instructions.
oem.tgz doesn't exist on my ESX4.1 box so I don't know where to put the file, can you help?
from what I can gather it should be in /vmfs/volumes/datastore1
u have to place it inside /vmfs/volumes/Hypervisor1 folder, this folder already has oem.tgz but it is empty.
you replace the file as per the procedure above and you put the new file in the folder i mentioned at the begining of the answer.
There's the problem I have no oem.tgz or Hypervisor1 folder!
The only oem files are the one I've downloaded from this thread and the new one I've created.[root@ESX1 ~]# find / -name oem.tgz/root/test/oem.tgz/root/oem.tgz[root@ESX1 ~]#
And here's where the hypervisor folder should be
[root@ESX1 ~]# ls -al /vmfs/volumes/
drwxr-xr-x 1 root root 512 Mar 30 20:50 .
drwxrwxrwt 1 root root 512 Mar 30 16:18 ..
drwxr-xr-t 1 root root 1120 Mar 24 13:20 4d8b452f-08842033-34d8-0017a4edef03
lrwxr-xr-x 1 root root 35 Mar 30 20:50 datastore1 -> 4d8b452f-08842033-34d8-0017a4edef03
[root@ESX1 ~]#Any ideas?
If you're able to boot ESXi, then you can enable Tech Support Mode (SSH) to access the host with a SSH client like WinSCP. You can then copy the file to /bootbank and /altbootbank.
this is weired. i have done the procedure myself today itself and i can assure you that inside /vmfs/volumes there is a Hypervisor1 folder with oem.tgz.
if the file doesnt exsist there then i dont think that is a problem because the file that was in this folder is empty.
Let me know what happen
You are correct. The Hypervisor1 - 3 partitions are mounted in /vmfs/volumes by their UUID. You can access the partition by that UUID path, or by the Hypervisor1/2 links or /bootlank and /altbootbank. If you run ls -l in either / or /vmfslvolumes you'll see that the friendly names in both cases point to the UUID path.
Thanks for the suggestions. I created the bootbank and altbootbank directories (see below)
[root@ESX1 test]# mkdir /bootbank[root@ESX1 test]# mkdir /altbootbank[root@ESX1 test]# cp -v oem.tgz /bootbank/`oem.tgz' -> `/bootbank/oem.tgz'[root@ESX1 test]# cp -v oem.tgz /altbootbank/`oem.tgz' -> `/altbootbank/oem.tgz'[root@ESX1 test]# chmod 755 -v /bootbank/oem.tgzmode of `/bootbank/oem.tgz' changed to 0755 (rwxr-xr-x)[root@ESX1 test]# chmod 755 -v /altbootbank/oem.tgzmode of `/altbootbank/oem.tgz' changed to 0755 (rwxr-xr-x)
Following these changes I reboot the server but ESX still doesn't see the new NIC.
[root@ESX1 ~]# esxcfg-nics -l
Name PCI Driver Link Speed Duplex MAC Address MTU Description
vmnic0 0000:3f:00.00 tg3 Up 1000Mbps Full 00:17:a4:ed:ef:03 1500 Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet
but the cards are there!
[root@ESX1 ~]# lspci
05:09.0 Ethernet controller: D-Link System Inc DGE-528T Gigabit Ethernet Adapter (rev 10)
3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet (rev 01)
The oem.tgz I created following the instructions above contains the correct line.[root@ESX1 after]# more etc/vmware/simple.map | grep r81691186:4300 0000:0000 network r8169I also copied the oem.tgz to the /vmfs/volumes directory[root@ESX1 after]# ls -al /vmfs/volumes/datastore1/total 574528drwxr-xr-t 1 root root 1260 Mar 30 21:53 .drwxr-xr-x 1 root root 512 Mar 30 22:02 ..drwxr-xr-x 1 root root 840 Mar 24 13:58 esxconsole-4d8b2d8f-588d-a536-d59f-0017a4edef03-r-------- 1 root root 458752 Mar 24 13:20 .fbb.sf-r-------- 1 root root 63143936 Mar 24 13:20 .fdc.sf-rwxr-xr-x 1 root root 457655 Mar 30 21:53 oem.tgz-r-------- 1 root root 255655936 Mar 24 13:20 .pbc.sf-r-------- 1 root root 260374528 Mar 24 13:20 .sbc.sf-r-------- 1 root root 4194304 Mar 24 13:20 .vh.sfAny other ideas?