Dell 3640 error No network interfaces found (verifyNetworkConnection)

rabdel

Bonjour,

Je n’arrive pas à déployer d’images sur ma nouvelle machine la DELL T3640. Fog n’arrive pas à trouver l’interface. Mais quand je branche les deux cartes réseaux, le déploiement fonctionne.
Merci pour l’aide.

Hello,

I can’t déploy image on the Dell T3640, see error on title. He can’t find interface. But when i pluy my 2 cards, thats works.
Thanks for help

Sebastian Roth

@rabdel said in Dell 3640 error No network interfaces found (verifyNetworkConnection):

But when i pluy my 2 cards, thats works.

What do you mean by that?

rabdel

@sebastian-roth
By that, i mean, i plug a RJ45 cable to each network interfaces.

george1421

@rabdel Ok we need a little more information about the problem you have. I understand what you say, but we need a picture of the error to understand the context of the error. Please take a clear picture of the error with a mobile phone and upload it here.

Also the 3640, is a Dell Precision 3640? That workstation should have a network connector on the motherboard. Do you tell us that you have a second network connector in an expansion slot? If yes what model number of this add on network connector?

rabdel

@george1421 Here is a picture of the error: https://imgur.com/a/5suL36l
The dhcp is working well.
Yes it’s a Dell Precision 3640; The workstation have a network connector on the motherboard and a second network connector in an expansion. Still got the error when i unplug the second card. The model is: Aquantia AQtion 5Gbit Network Adapter.

Sebastian Roth

@rabdel To me this sounds as if FOS doesn’t find the onboard NIC but only the one in the expansion port. To be able to help we need to know exactly what NICs you have in the machines.

When you run into the error (picture you posted) hit ENTER to get to a command shell. Type lspci -nn | grep -i net, take a picture and post that here.

george1421

@rabdel As Sebastian said FOS Linux doesn’t seem to find the network interface. Collect the information as Sebastian posted or go into windows on a running computer and get the hardware ID for both network adapters. The Hardware ID will look like this: PCI\VEN_8086&DEV_15BB&CC_020000 We need the vendor ID and Device ID in your hardware ID. Using my example we need to know 8086:15BB But just give us the entire string and we will decide.

There is 2 information we need to.

What version of FOG are you using
What version of FOS Linux kernel FOG Configuration->Kernel update are you using. You may need to install FOS Linux kernel 5.10.x or later to get support for that new T3640 computer.

rabdel

@george1421 I can’t put command. When i tape ENTER, i got this error: https://imgur.com/a/mSz1Ff2

Network card on the motherboarb:
PCI\VEN_8086&DEV_0D4C&CC_020000&REV_00
The second network card:
PCI\VEN_1D6A&DEV_D108&CC_020000&REV_02

For information, this model accept only UEFI boot.
For my UEFI machines, i added this snippet in my dhcp server config file:

    match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
        if substring (option vendor-class-identifier, 15, 5) = "00000" {
            filename "undionly.kpxe";
        }
        elsif substring (option vendor-class-identifier, 15, 5) = "00006" {
            filename   "ipxe32.efi";
        }
        else {
            filename   "ipxe.efi";
        }
    }

The vendor-class-identifier of my machine = “MSFT 5.0”;

FOG Version: 1.5.9
FOS Kernel: Kernel.TomElliott.5.10.34

george1421

@rabdel When I get to the office (~ 1hr) I’ll look up the network adapter codes to see if they are in the linux kernel.

Also just as a point of information since you are using a linux dhcp server, FOG does have a full configuration for the isc-dhcp server here: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Example_1 So you can see all of the class identifiers. The dhcp server and iPXE boot loader do not change your error because your error is in FOS Linux not iPXE.

george1421

@rabdel OK the intel nic [8086:0D4C] driver has been in the linux kernel since linux version 5.5. The aquantia nic [1D6A:D108] driver has been the linux kernel since 4.11.

So the signs are good in that it should be working. With that said something is missing. So now we debug.

I want you to connect one network interface cable to the intel nic. Have a second network interface cable ready because we will need it during debugging. Get the mac address of the intel nic and manually register (via the web ui create a host definition) this computer with FOG.

Now create a debug deployment/capture it doesn’t matter. Before you select the schedule task button, tick the debug checkbox. Schedule the task then pxe boot the target computer.

The target computer should boot right into debug imaging. After a few screens of text you will be dropped to the FOS Linux command prompt. At that command prompt I want you to key in a few commands.

As soon as you are at the command prompt key in ip a s and see if your intel nic has an ip address.

If yes, then see if you can ping the fog server from the FOS Linux command prompt.

If no, wait 30 seconds then key in this command. /sbin/udhcpc -i enp3s0 --now I think the intel nic’s kernel name is enp3s0 but you can confirm with the ip a s command. You will see both the intel and aquantia nics so you will need to identify which is which by mac address. After the udhcp command completes then type in the ip a s command again to see if the intel nic gets an ip address.

If still no, then try with the aquantia nic interface the same process. My guess is the intel nic will work after 30 seconds. But lets test.

If still no luck then we need to look at the syslog. I am guessing at the file name here, so you may need to confirm by looking in /var/log key in grep firmware /var/log/messages See if we have any errors related to missing nic firmware.

rabdel

@george1421 So i reproduced what you asked for:
When i put the command ip a s, i got no address ip, he detect only one card, enp3s0(Aquantia).
Still got no ip with this command /sbin/udhcpc -i enp3s0 --now.
So, when i plug the cable to the second card, i got an IP Address.
I understood where the problem comes from. During boot, IPXE detects the internal card, but just after, when FOS takes over, it can no longer detect the internal card, suddenly it switches to the 2nd card and since it is not connected it crashes.
I think the kernel has not the driver of the intel card.

george1421

@rabdel This is very strange because FOS linux should find the intel card.

If you still have access to the FOS Linux console I want you to post the results of uname -a

Also look through the log file in /var/log its either called messages or syslog.

If your second nic has an ip address, you can give root a password with this command passwd make it simple like hello then you know the ip address of the second nic you can use winscp or other program like putty to connect to the target computer. If you use winscp then download that log file to your windows or linux computer to look through the log file. See if there is any reference to firmware missing in fos linux. That is the only thing I can think where linux is not detecting the intel nic.

rabdel

@george1421 When i tape uname -a i got this: Linux fogclient.localdomain 4.19.145 #1 SMP Sun Sep 13 05:35:01 CDT 2020 x86_64 GNU/Linux
I don’t know why m not in the version Kernel.TomElliott.5.10.34.64
So i did it again, i downloaded this new version and now FOS see the second card and its working
Thanks a lot for your help George, you can close this ticket.
Have a nice day.

Dell 3640 error No network interfaces found (verifyNetworkConnection)

188

11.6k

17.1k

154.6k