Re: D-Link DGE-528T 1GB Network Card on ESXi4.1

cyber7 · ‎08-16-2010

Hi Guys

I read all over the place (prior to ESXi4) that this network card is not supported. That said, I have plugged into my machine one of these cards and doing a "lspci" get the following information:

000:008:04.0 Network controller: D-Link System Inc DGE-528T Gigabit Ethernet Adapter

the "lspci -n" command also displays the following information:

000:008:04.0 Class 0200: 1186:4300

I also had a look at the /etc/vmware/pci.ids file and can find an entry in it for this card:

4300 DGE-528T Gigabit Ethernet Adapter

This tells me that the network controlled is active, working and identiefied 100%.

Questions:

1. Why can I not find this in my ESXi Console to use as a device?

2. Why would all the info be on the OS, but not made available within the EXSi environment?

Kind regards

cyber7

cyber7 · ‎03-04-2011

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.

Cheers

cyber7

cyber7 · ‎03-04-2011

as stated in my post. It works with my custom built oem

Automsoftdotcom · ‎03-22-2011

Hi there,

I would very much appreciate it if you could post your oem file!

Ronan

cyber7 · ‎03-22-2011

Hi Ronan

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.

Cheers

Aubrey Kloppers

ps - I include rsync into all my oem's to make it easier to transfer files...

Automsoftdotcom · ‎03-22-2011

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

Ronan

cyber7 · ‎03-23-2011

Hi Ronan

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.

Cheers

Aubrey

kabuataya123 · ‎03-30-2011

i got it to work perfectly fine, thanks man,

Karam Abuataya

DervMan · ‎03-30-2011

Hi Aubrey,

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

Any suggestions?

kabuataya123 · ‎03-30-2011

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.

Karam Abuataya

DervMan · ‎03-30-2011

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/

total 1024

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?

Dave_Mishchenko · ‎03-30-2011

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.

kabuataya123 · ‎03-30-2011

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

Karam Abuataya

Dave_Mishchenko · ‎03-30-2011

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.

DervMan · ‎03-30-2011

Hi Dave,

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.tgz

mode of `/bootbank/oem.tgz' changed to 0755 (rwxr-xr-x)

[root@ESX1 test]# chmod 755 -v /altbootbank/oem.tgz

mode 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

[root@ESX1 ~]#

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)

[root@ESX1 ~]#

The oem.tgz I created following the instructions above contains the correct line.

[root@ESX1 after]# more etc/vmware/simple.map | grep r8169

1186:4300 0000:0000 network r8169

I also copied the oem.tgz to the /vmfs/volumes directory

[root@ESX1 after]# ls -al /vmfs/volumes/datastore1/

total 574528

drwxr-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.sf

Any other ideas?

Dave_Mishchenko · ‎03-30-2011

You just want to copy the file to /bootbank and /altbootbank. You don't need to copy it to the datastore.

If you run ls -l /bootbank/ do you see your oem.tgz file. The size of the file should not be about 139 bytes.

If the correct file is there after you've rebooted your host could you verify that the driver exists in /usr/lib/vmware/vmkmod/ ?

If it is there, take a look at the file /var/log/messages (pretty soon after you reboot). You should see a section where the host tried to load the driver and how it enumerated PCI devices to find a NIC that it could use. If you don't see that in the logs then there could be an issue with the simple.map file.

If the driver is in the vmkmod folder, try to load it manually with vmkload_mod <drivername> . If you don't see the NIC with esxcfg-nics -l after that then the problem is the driver and changing simple.map won't help.

DervMan · ‎03-30-2011

Even though the driver is assigned to the PCI ID in simple.map contained in oem.tgz it's not being picked up by ESX?!

I've copied the oem.tgz from /bootbank to /root/after and extracted the files to confirm all is correct. Here's the relevant part of simple.map from the oem.tgz I created.

[root@ESX1 after]# more etc/vmware/simple.map | grep r8169

1186:4300 0000:0000 network r8169

But that line does not exist in /etc/vmware/simple.map.

[root@ESX1 after]# more /etc/vmware/simple.map | grep r8169

[root@ESX1 after]#

The driver exists in my oem.tgz

[root@ESX1 after]# ls -al usr/lib/vmware/vmkmod/r8169.o

-rwxr-xr-x 1 root root 74029 Aug 18 2010 usr/lib/vmware/vmkmod/r8169.o

But not in [root@ESX1 after]# ls -al /usr/lib/vmware/vmkmod/r8169.o

ls: /usr/lib/vmware/vmkmod/r8169.o: No such file or directory

Nothing jumps out at me in the syslog

[root@ESX1 after]# less /var/log/messages | grep pci

Mar 30 21:20:22 ESX1 kernel: [ 16.236962] pci_hotplug: PCI Hot Plug PCI Core version: 0.5

Mar 30 21:56:22 ESX1 kernel: [ 15.239656] pci_hotplug: PCI Hot Plug PCI Core version: 0.5

[root@ESX1 after]#

[root@ESX1 after]# less /var/log/messages | grep PCI

Mar 30 21:20:22 ESX1 kernel: [ 0.000000] ISA/PCI bus type with no IRQ information... falling back to ELCR

Mar 30 21:20:22 ESX1 kernel: [ 0.000000] Using ELCR to identify PCI interrupts

Mar 30 21:20:22 ESX1 kernel: [ 0.000000] Allocating PCI resources starting at 88000000 (gap: 80000000:70000000)

Mar 30 21:20:22 ESX1 kernel: [ 16.079133] PCI: Using configuration type 1

Mar 30 21:20:22 ESX1 kernel: [ 16.079414] PCI: Probing PCI hardware

Mar 30 21:20:22 ESX1 kernel: [ 16.080016] PCI quirk: region f800-f87f claimed by ICH6 ACPI/GPIO/TCO

Mar 30 21:20:22 ESX1 kernel: [ 16.080020] PCI quirk: region fa00-fa3f claimed by ICH6 GPIO

Mar 30 21:20:22 ESX1 kernel: [ 16.080069] PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1

Mar 30 21:20:22 ESX1 kernel: [ 16.080437] PCI: device 0000:05:04.0 has unknown header type 10, ignoring.

Mar 30 21:20:22 ESX1 kernel: [ 16.080566] PCI: Transparent bridge - 0000:00:1e.0

Mar 30 21:20:22 ESX1 kernel: [ 16.088541] PCI: Discovered primary peer bus 01 [IRQ]

Mar 30 21:20:22 ESX1 kernel: [ 16.088549] PCI: Using IRQ router PIIX/ICH [8086/27b8] at 0000:00:1f.0

Mar 30 21:20:22 ESX1 kernel: [ 16.088563] PCI -> IRQ mapping bus:0, slot:2, int pin:0 irq 16 vector 169 apic 124-0.

Mar 30 21:20:22 ESX1 kernel: [ 16.088566] PCI->APIC IRQ transform: 0000:00:02.0[A] -> IRQ 16

Mar 30 21:20:22 ESX1 kernel: [ 16.088574] PCI -> IRQ mapping bus:0, slot:27, int pin:0 irq 17 vector 177 apic 124-1.

Mar 30 21:20:22 ESX1 kernel: [ 16.088576] PCI->APIC IRQ transform: 0000:00:1b.0[A] -> IRQ 17

Mar 30 21:20:22 ESX1 kernel: [ 16.088585] PCI -> IRQ mapping bus:0, slot:28, int pin:1 irq 18 vector 185 apic 124-2.

Mar 30 21:20:22 ESX1 kernel: [ 16.088587] PCI->APIC IRQ transform: 0000:00:1c.1[B] -> IRQ 18

Mar 30 21:20:22 ESX1 kernel: [ 16.088595] PCI -> IRQ mapping bus:0, slot:29, int pin:0 irq 19 vector 193 apic 124-3.

Mar 30 21:20:22 ESX1 kernel: [ 16.088597] PCI->APIC IRQ transform: 0000:00:1d.0[A] -> IRQ 19

Mar 30 21:20:22 ESX1 kernel: [ 16.088605] PCI -> IRQ mapping bus:0, slot:29, int pin:1 irq 20 vector 201 apic 124-4.

Mar 30 21:20:22 ESX1 kernel: [ 16.088607] PCI->APIC IRQ transform: 0000:00:1d.1[B] -> IRQ 20

Mar 30 21:20:22 ESX1 kernel: [ 16.088615] PCI -> IRQ mapping bus:0, slot:29, int pin:2 irq 21 vector 209 apic 124-5.

Mar 30 21:20:22 ESX1 kernel: [ 16.088618] PCI->APIC IRQ transform: 0000:00:1d.2[C] -> IRQ 21

Mar 30 21:20:22 ESX1 kernel: [ 16.088625] PCI -> IRQ mapping bus:0, slot:29, int pin:3 irq 22 vector 217 apic 124-6.

Mar 30 21:20:22 ESX1 kernel: [ 16.088628] PCI->APIC IRQ transform: 0000:00:1d.3[D] -> IRQ 22

Mar 30 21:20:22 ESX1 kernel: [ 16.088633] PCI->APIC IRQ transform: 0000:00:1d.7[A] -> IRQ 19

Mar 30 21:20:22 ESX1 kernel: [ 16.088644] PCI -> IRQ mapping bus:0, slot:31, int pin:0 irq 23 vector 225 apic 124-7.

Mar 30 21:20:22 ESX1 kernel: [ 16.088647] PCI->APIC IRQ transform: 0000:00:1f.1[A] -> IRQ 23

Mar 30 21:20:22 ESX1 kernel: [ 16.088655] PCI -> IRQ mapping bus:0, slot:31, int pin:1 irq 24 vector 233 apic 124-8.

Mar 30 21:20:22 ESX1 kernel: [ 16.088657] PCI->APIC IRQ transform: 0000:00:1f.2[B] -> IRQ 24

Mar 30 21:20:22 ESX1 kernel: [ 16.088666] PCI -> IRQ mapping bus:63, slot:0, int pin:0 irq 25 vector 50 apic 124-9.

Mar 30 21:20:22 ESX1 kernel: [ 16.088669] PCI->APIC IRQ transform: 0000:3f:00.0[A] -> IRQ 25

Mar 30 21:20:22 ESX1 kernel: [ 16.088677] PCI -> IRQ mapping bus:5, slot:9, int pin:0 irq 26 vector 58 apic 124-10.

Mar 30 21:20:22 ESX1 kernel: [ 16.088680] PCI->APIC IRQ transform: 0000:05:09.0[A] -> IRQ 26

Mar 30 21:20:22 ESX1 kernel: [ 16.089052] PCI: Bridge: 0000:00:1c.0

Mar 30 21:20:22 ESX1 kernel: [ 16.089069] PCI: Bridge: 0000:00:1c.1

Mar 30 21:20:22 ESX1 kernel: [ 16.089085] PCI: Bridge: 0000:00:1e.0

Mar 30 21:20:22 ESX1 kernel: [ 16.236962] pci_hotplug: PCI Hot Plug PCI Core version: 0.5

Mar 30 21:56:21 ESX1 kernel: [ 0.000000] ISA/PCI bus type with no IRQ information... falling back to ELCR

Mar 30 21:56:21 ESX1 kernel: [ 0.000000] Using ELCR to identify PCI interrupts

Mar 30 21:56:22 ESX1 kernel: [ 0.000000] Allocating PCI resources starting at 88000000 (gap: 80000000:70000000)

Mar 30 21:56:22 ESX1 kernel: [ 15.081803] PCI: Using configuration type 1

Mar 30 21:56:22 ESX1 kernel: [ 15.082082] PCI: Probing PCI hardware

Mar 30 21:56:22 ESX1 kernel: [ 15.082688] PCI quirk: region f800-f87f claimed by ICH6 ACPI/GPIO/TCO

Mar 30 21:56:22 ESX1 kernel: [ 15.082692] PCI quirk: region fa00-fa3f claimed by ICH6 GPIO

Mar 30 21:56:22 ESX1 kernel: [ 15.082741] PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1

Mar 30 21:56:22 ESX1 kernel: [ 15.083109] PCI: device 0000:05:04.0 has unknown header type 10, ignoring.

Mar 30 21:56:22 ESX1 kernel: [ 15.083239] PCI: Transparent bridge - 0000:00:1e.0

Mar 30 21:56:22 ESX1 kernel: [ 15.091199] PCI: Discovered primary peer bus 01 [IRQ]

Mar 30 21:56:22 ESX1 kernel: [ 15.091206] PCI: Using IRQ router PIIX/ICH [8086/27b8] at 0000:00:1f.0

Mar 30 21:56:22 ESX1 kernel: [ 15.091220] PCI -> IRQ mapping bus:0, slot:2, int pin:0 irq 16 vector 169 apic 124-0.

Mar 30 21:56:22 ESX1 kernel: [ 15.091223] PCI->APIC IRQ transform: 0000:00:02.0[A] -> IRQ 16

Mar 30 21:56:22 ESX1 kernel: [ 15.091231] PCI -> IRQ mapping bus:0, slot:27, int pin:0 irq 17 vector 177 apic 124-1.

Mar 30 21:56:22 ESX1 kernel: [ 15.091233] PCI->APIC IRQ transform: 0000:00:1b.0[A] -> IRQ 17

Mar 30 21:56:22 ESX1 kernel: [ 15.091242] PCI -> IRQ mapping bus:0, slot:28, int pin:1 irq 18 vector 185 apic 124-2.

Mar 30 21:56:22 ESX1 kernel: [ 15.091245] PCI->APIC IRQ transform: 0000:00:1c.1[B] -> IRQ 18

Mar 30 21:56:22 ESX1 kernel: [ 15.091252] PCI -> IRQ mapping bus:0, slot:29, int pin:0 irq 19 vector 193 apic 124-3.

Mar 30 21:56:22 ESX1 kernel: [ 15.091255] PCI->APIC IRQ transform: 0000:00:1d.0[A] -> IRQ 19

Mar 30 21:56:22 ESX1 kernel: [ 15.091262] PCI -> IRQ mapping bus:0, slot:29, int pin:1 irq 20 vector 201 apic 124-4.

Mar 30 21:56:22 ESX1 kernel: [ 15.091265] PCI->APIC IRQ transform: 0000:00:1d.1[B] -> IRQ 20

Mar 30 21:56:22 ESX1 kernel: [ 15.091272] PCI -> IRQ mapping bus:0, slot:29, int pin:2 irq 21 vector 209 apic 124-5.

Mar 30 21:56:22 ESX1 kernel: [ 15.091275] PCI->APIC IRQ transform: 0000:00:1d.2[C] -> IRQ 21

Mar 30 21:56:22 ESX1 kernel: [ 15.091283] PCI -> IRQ mapping bus:0, slot:29, int pin:3 irq 22 vector 217 apic 124-6.

Mar 30 21:56:22 ESX1 kernel: [ 15.091285] PCI->APIC IRQ transform: 0000:00:1d.3[D] -> IRQ 22

Mar 30 21:56:22 ESX1 kernel: [ 15.091291] PCI->APIC IRQ transform: 0000:00:1d.7[A] -> IRQ 19

Mar 30 21:56:22 ESX1 kernel: [ 15.091302] PCI -> IRQ mapping bus:0, slot:31, int pin:0 irq 23 vector 225 apic 124-7.

Mar 30 21:56:22 ESX1 kernel: [ 15.091304] PCI->APIC IRQ transform: 0000:00:1f.1[A] -> IRQ 23

Mar 30 21:56:22 ESX1 kernel: [ 15.091312] PCI -> IRQ mapping bus:0, slot:31, int pin:1 irq 24 vector 233 apic 124-8.

Mar 30 21:56:22 ESX1 kernel: [ 15.091315] PCI->APIC IRQ transform: 0000:00:1f.2[B] -> IRQ 24

Mar 30 21:56:22 ESX1 kernel: [ 15.091324] PCI -> IRQ mapping bus:63, slot:0, int pin:0 irq 25 vector 50 apic 124-9.

Mar 30 21:56:22 ESX1 kernel: [ 15.091326] PCI->APIC IRQ transform: 0000:3f:00.0[A] -> IRQ 25

Mar 30 21:56:22 ESX1 kernel: [ 15.091335] PCI -> IRQ mapping bus:5, slot:9, int pin:0 irq 26 vector 58 apic 124-10.

Mar 30 21:56:22 ESX1 kernel: [ 15.091337] PCI->APIC IRQ transform: 0000:05:09.0[A] -> IRQ 26

Mar 30 21:56:22 ESX1 kernel: [ 15.091706] PCI: Bridge: 0000:00:1c.0

Mar 30 21:56:22 ESX1 kernel: [ 15.091722] PCI: Bridge: 0000:00:1c.1

Mar 30 21:56:22 ESX1 kernel: [ 15.091738] PCI: Bridge: 0000:00:1e.0

Mar 30 21:56:22 ESX1 kernel: [ 15.239656] pci_hotplug: PCI Hot Plug PCI Core version: 0.5

[root@ESX1 after]#

Loading the driver manually

[root@ESX1 after]# vmkload_mod usr/lib/vmware/vmkmod/r8169.o

Module usr/lib/vmware/vmkmod/r8169.o loaded successfully

[root@ESX1 after]# 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

[root@ESX1 after]#

It does look to me that my oem.tgz is being completely ignored but there again I know very little about ESX!?!

Dave_Mishchenko · ‎03-30-2011

Hmm - you're using ESX (yes/no)? ESX doesn't use a simple.map file (that's for ESXi only).

For ESX you have to put the driver in the right place, in this case create a driver XML file and update the main PCI database file.

However, given the following output that you pasted it doesn't appear that the driver is recognizing the NIC. You'll need to fix that problem first.

[root@ESX1 after]# vmkload_mod usr/lib/vmware/vmkmod/r8169.o

Module usr/lib/vmware/vmkmod/r8169.o loaded successfully

[root@ESX1 after]# 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

[root@ESX1 after]#

DervMan · ‎03-30-2011

mmmmm good question about ESX/ESXi, I wanted to install the 60 day trial so I could better understand the data networking side of vmotion so perhaps I've downloaded and installed the wrong version :smileyconfused:!

It doesn't say 'i' here

[root@ESX1 ~]# uname -ar

Linux ESX1 2.6.18-194.ESX #1 Fri Nov 12 03:44:34 PST 2010 x86_64 x86_64 x86_64 GNU/Linux

[

I'm running version "VMWare ESX, 4.1.0, 348481 | Eval....."

Dave_Mishchenko · ‎03-30-2011

You have ESX. I think it would be easier to just reinstall with ESXi. Functionality wise they are the same product.