No DHCP Response on eno1
-
HARDWARE
SERVER:
PRIMERGY RX2530 M1
2 x Intel
Xeon CPU E5-2620 v3 @ 2.40GHz
32GiB System Memory
Four Network Cards BondedNODE:
PRIMERGY RX2530 M1
2 x Intel Xeon CPU E5-2640 v3 @ 2.60GHz
32GiB System Memory
Storage 2TiB
Four Network Cards BondedDHCP
Infoblox
Using Unionly.kpxeClients BIOS
Mainly HP Computers
Configured to use Legacy Network Boot
Secure Boot DisabledSOFTWARE
FOG Info:
dev-branch version: 1.5.9.111
bzImage Version: 5.10.50
bzImage32 Version: 5.10.50Description of Problem:
After updating to the latest version, I noticed that the speed decreased. The image size being pushed to the computers is about 300GB, this used to take between 2 and 3 hours. Now it is taking about 8 hours. I also noticed that some of the computers fail to image. The computers get an IP address from PXE and continue to load but then give an error saying that it could not obtain an IP from the DHCP server or is unable to reach the FOG Server.
I canceled the task and tried to launch it from the client machine PXE menu, and got the same error. I launched the FOG compatibility from the PXE menu and noticed that it was unable to get an IP address. I loaded the computer back into windows and the computer was able to connect to the internet with no issues. I have 3 rooms of 24 computers in this particular area and about a third of them have this issue. The other computers were able to be imaged but noticed that the PXE loading was very slow and the time that it usually takes to the image was doubled. Here is a screenshot of when I tried loading the computer compatibility from the client PXE menu.
I tried Switching to older kernels and it did not work. I would appreciate any ideas that can help in figuring out this problem.
-
@kleber said in No DHCP Response on eno1:
After updating to the latest version, I noticed that the speed decreased.
Which version did you upgrade from?
-
I upgraded from version 1.5.5
-
@kleber said in No DHCP Response on eno1:
After updating to the latest version, I noticed that the speed decreased. […] The computers get an IP address from PXE and continue to load but then give an error saying that it could not obtain an IP from the DHCP server or is unable to reach the FOG Server.
What you describe are two totally different issues as far as I see things. Just saw this when I read your post again. While they could be related in terms of being a general network or Linux kernel driver issue.
No DHCP response sounds like a network issue. Anything that changed beside the FOG update from 1.5.5 to 1.5.9.111? Any custom modifications you had before the update?
By the way, can’t check out the pictures because it asks for a login. Would be helpful if you can upload those to a different location again.
-
I Just noticed that the links to the screenshot on the original post are broken. Here are new links to the images:
This is the error I get when a computer is trying to execute a task from fog and it goes thru PXE:
This the error I get when I try to launch from the PXE menu the Computer Compatability:
-
No modifications to the network or the computers. The computer is able to obtain an IP address in windows, link speed auto-negotiates to 1Gbps. I tested the network path and it had no issues, but just in case I switch to a different port. The issue still remains.