Host registration error.
-
@erasp21 There was someone else who had a similar issue.
What we saw in that thread was the mac address displayed on the FOG iPXE menu was not the same mac address that was registered to the host in the web ui.
So will you confirm that the mac address on the FOG iPXE menu is the same mac address that is listed on the usb network adapter?
If you plug that usb network adapter into a windows computer and look at the device manager, will you tell me the hardware ID of that network adapter? I need the vendor and device ID.
What target computer (mfg and model) are you trying to PXE boot?
In the other thread, both FOS Linux and Windows saw the same mac address and iPXE (displayed on the pxe boot menu) saw a different mac address.
ref: https://forums.fogproject.org/topic/15072/hp-elitebook-840-g7
-
Thank you for reply.
I have confirmed that the MAC address is the same as the one recorded on the USB network adapter and the Fog Server Host.
I connected the USB network adapter to Windows and checked the information.
-
Realtek USB GbE Family Controller
-
Hardware ID: UBS \ VID_0BDA & PID_8153 & REV_3100
-> USB Type-C is used for connection.
Just in case, proceeding with verification by ordering a USB network adapter from another manufacturer. -
PXE Target computer trying to boot
-
HP EliteBook 830 G7
-
-
@erasp21 Could be MAC-paththrough as well. Some BIOS/UEFI firmware has the capability to pass on the MAC address of your notebook to the USB-adapter. That might be the case when booting into Windows but not on PXE boot up in iPXE.
Please compare the MAC address you see:
- on the BIOS screen
- in iPXE output
- after system is booted
- maybe even boot some live Linux from DVD and check MAC address there
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@sebastian-roth what I was seeing in the other thread is that ipxe was seeing one mac address and displaying that on the FOG iPXE screen with unregistered. When the OP of that thread ran through full registration and the system would reboot, the fog iPXE menu would still say unregistered. I had the OP of that thread manually register the mac displayed on the iPXE menu and then iPXE would see it as registered. We then compared what iPXE was seeing and what FOS was seeing for the mac address of the interface. iPXE and FOS showed a different mac address for the same network adapter. Booting into widows showed the same mac address that FOS linux sees. Its possible that the complete OS’ are seeing the pass through mac address, where iPXE is seeing the adapter mac since it may not have the driver to see the pass through mac (guess). But this appears now to be the second issue with these unique circumstances.
-
Thank you for your answer.
What exactly can I do to solve this problem?
Try manually registering the MAC address displayed on the Fog Server iPXE screen.
-
I manually registered the Mac displayed in the iPXE menu, iPXE recognized it as registered.
And I succeeded in uploading the image.Why do iPXE and FOS show different MAC addresses for the same network adapter?
Also, how can I improve the situation where I have to manually register the MAC address, and can I expect improvements in future updates?
-
@erasp21 What we are guessing that these 830/840 G7 models are doing something strange. Would you look into the firmware of one of your systems and see if there is something regarding mac address pass through? If so note the setting, then change the setting to see if the network adapter responds normally. The G6 versions of these models act as it should.
What we are guessing is that the iPXE boot loader uses a lower level driver where it only sees the mac address built into the adapter, where both linux and windows has a higher level driver where it sees the mac pass through address. But without the hardware we can only guess
-
@george1421
I would like to check one firmware of the system to see if there is anything about MAC address passthrough.What steps do you need to take?
I will disclose what I can cooperate with and necessary information.
-
@sebastian-roth
Sebastian Roth-san
Thank you for your reply.
Please wait for a while as we will have the opportunity to touch the verification machine next week.Certainly I confirmed the two MAC addresses.
- MAC address confirmed by fogserver’s iPXE.
- USB-The MAC address that your wired LAN device may have.
The MAC address confirmed by iPXE of fogserver was manually corrected on the web-UI of fogserver, and the image was uploaded and deployed.
I’m more interested in this issue and want to know why there are two MAC addresses.
-
@erasp21 I’m sorry I can not help with this since we do not use hp on our campus. So I can’t give you step by step instructions.
I would look through the firmware settings to see if there is any settings that talk about mac pass through.
-
@george1421 said in Host registration error.:
I’m sorry I can not help with this since we do not use hp on our campus. So I can’t give you step by step instructions.
I would look through the firmware settings to see if there is any settings that talk about mac pass through.Thank you for your answer.
Please let me know if there is anything I can confirm.
If you know the procedure, I can cooperate.
-
@erasp21 As I mentioned in my previous post I don’t use HP so I can’t give you a step by step.
A quick google-fu search finds this
“From the BIOS setup, under Main, click System Information. Then click the link at the top, “Show Advanced System Information.” Then scroll all the way down and under the COMMUNICATION header you will see Integrated MAC Address 1.”Read the built in mac address from the above link.
Compare this to the mac address the FOG hardware registration/inventory collects.
ref: https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/MAC-Address/td-p/5719257
Then in the bios Advanced menu there is a sub menu for MAC Address Pass Through, what are the setting there? What happens if you change the settings from their default values and try to image again?
ref: http://h10032.www1.hp.com/ctg/Manual/c06691369
There has to be a reason why iPXE is seeing a different mac address than FOG and Windows.
-
I checked the BIOS notation on the HP 830 G7.
Advanced --MAC Address Pass Thruough
The MAC address was written here.There were three options for Host Based MAC Address.
“Disable”
“System Address”
“Custom Address”The MAC address registered for the first time in FogServer this time recognizes the MAC address of the NIC of USB Type-c, and after being registered as Host in FogServer, the MAC address used for Uploading and Deploying Image is HP 830 G7 Pass. It turned out to be a Thruough MAC address.
The problem this time is that when registering a new Host in Fog Server, the MAC address of the USB Type-c NIC is registered instead of the MAC address of the MAC Address Pass Thruough that the PC has.
Is it possible to solve the problem by changing the FogServer settings in order to register the Host Based MAC Address of the PC?
-
@erasp21 said in Host registration error.:
There were three options for Host Based MAC Address.
So what was the default setting for this value?
-
The default setting was “System Address”.
-
Hello.
In the BIOS settings of the PC
Advanced --MAC Address Pass Thruough
“System Address” (default)
I feel that the problem is that FogServer reads the USB Type-C NIC MAC Address when trying to register the Host.How can I make FogServer read only the MAC Address that my PC has?
-
@erasp21 said in Host registration error.:
I feel that the problem is that FogServer reads the USB Type-C NIC MAC Address when trying to register the Host.
This is something deep down in how firmware (UEFI), NIC adapter and probably the OS driver handle things. It’s not something we can change in FOG. Well there might be special driver options you could set via /proc in FOS but I really doubt you can change that behavior of which MAC is seen.
-
@george1421 it looks like you hit the nail on the head here. I’m having this same issue with a hp 1040 g7. After disabling MAC passthrough in BIOS I was able to capture an image! Deploying is similar, disabling mac passthrough and everything is good!
-
@jpolk91 said in Host registration error.:
disabling mac passthrough and everything is good
Just to help me and the OP of the thread. Disabling mac pass through and imaging a second computer. Does FOG see that second computer’s mac address as already registered. Or you have to register the second computer with FOG, which gets a different mac address.
Since I don’t have HP on my campus we need to fully understand this feature because I’ve seen an uptick in posts regarding this issue.
-
@george1421 sure.
With MAC pass through disabled FOG registers the MAC of the adapter, so if you use a different adapter for the computer receiving the image it will need to be registered. If you use the same adapter as the computer that uploaded the image it will not.
However, even if you use the same adapter to deploy as you did to upload it seems MAC pass through needs to be disabled on the receiving machine as well or it will error out before deploying. This could be wrong though, I haven’t thoroughly tested it, just tried it on one machine one time.
Let me know if you want me to try anything. I should have one or two of these machines for a little while yet.
