PXE Windows Client registration
-
@krishna I am not sure where exacly the issue/error is?! In the picture we see it boot to the boot.php which is fine in general. You should see the menu after that. I suppose you don’t, so please tell us more about what exactly happens after the boot.php. Does it just hang at this stage?
If so it would be interesting to run
tail -f /var/log/apache2/access.logwhile you PXE boot one of the HP Probook x360 435 G7 devices. Best if you make sure there isn’t anyone logged into the web UI and no deployment/capture is going on as you would see many requests in the log then. -
@sebastian-roth
After the boot.php the computer restarts and i dont get to the fog menu.the access.log file is empty.
/var/log/apache2$ ls -ltr
total 15460
-rwxr-xr-x 1 root adm 0 May 6 11:57 access.logi dont see any messages in the access.log during the booth up
Thanks
-
@krishna From a web browser if you key in
http://10.20.0.9/fog/service/ipxe/boot.php?mac=00:00:00:00:00you should get the text that makes the iPXE menu. Do you get this menu? -
@george1421
Hi, this is what i get. when i go to the URL#!ipxe set fog-ip 192.168.172.10 set fog-webroot fog set boot-url http://${fog-ip}/${fog-webroot} cpuid --ext 29 && set arch x86_64 || set arch i386 goto get_console :console_set colour --rgb 0x00567a 1 || colour --rgb 0x00567a 2 || colour --rgb 0x00567a 4 || cpair --foreground 7 --background 2 2 || goto MENU :alt_console cpair --background 0 1 || cpair --background 1 2 || goto MENU :get_console console --picture http://192.168.172.10/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console :MENU menu colour --rgb 0xff0000 0 || cpair --foreground 1 1 || cpair --foreground 0 3 || cpair --foreground 4 4 || item --gap Host is NOT registered! item --gap -- ------------------------------------- item fog.local Boot from hard disk item fog.memtest Run Memtest86+ item fog.reginput Perform Full Host Registration and Inventory item fog.reg Quick Registration and Inventory item fog.deployimage Deploy Image item fog.multijoin Join Multicast Session item fog.sysinfo Client System Information (Compatibility) choose --default fog.local --timeout 10000 target && goto ${target} :fog.local sanboot --no-describe --drive 0x80 || goto MENU :fog.memtest kernel memdisk initrd=memtest.bin iso raw initrd memtest.bin boot || goto MENU :fog.reginput kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.172.10/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.172.10:/images/ storageip=192.168.172.10 nvme_core.default_ps_max_latency_us=0 loglevel=4 mode=manreg imgfetch init_32.xz boot || goto MENU :fog.reg kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.172.10/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.172.10:/images/ storageip=192.168.172.10 nvme_core.default_ps_max_latency_us=0 loglevel=4 mode=autoreg imgfetch init_32.xz boot || goto MENU :fog.deployimage login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme param sysuuid ${uuid} :fog.multijoin login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param sessionJoin 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme param sysuuid ${uuid} :fog.sysinfo kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.172.10/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.172.10:/images/ storageip=192.168.172.10 nvme_core.default_ps_max_latency_us=0 loglevel=4 mode=sysinfo imgfetch init_32.xz boot || goto MENU :bootme chain -ar http://192.168.172.10/fog/service/ipxe/boot.php##params || goto MENU autobootThanks
-
@krishna You seem to have different nodes. The one with IP 10.20.0.9 is probably a storage node at one of your office locations while 192.168.172.10 is your FOG master node. Am I right? Do you also use the location plugin?
In this case you need to run the
tail ...command on your storage node.Are you sure other clients properly PXE boot to the FOG menu in this location? Just trying to rule out this is not a general issue at that location.
-
@sebastian-roth
Hi,
I just got one Fog server i.e. 192.168.172.10
the original screen capture i sent was just a reference to where i am getting stuck with the PXE.
10.20.0.9 has no relation to my environment.Sorry about the confusion…
At this point i am not able to get any client work with fog server and looking for some help desperately.
Thanks again.
-
@krishna said in PXE Windows Client registration:
10.20.0.9 has no relation to my environment.
Well this information has to be coming from somewhere.
For the subnet where your clients are running, look at your dhcp server. Confirm what is at dhcp option 66 on your dhcp server. If its set correctly then we will need you to get a pcap of the booting process. To that point is the fog server and the target computers on the same IP subnet?
-
@george1421
66 on dhcp has the fog ip i.e. 192.168.172.10 -
@george1421
the screen capture is a random one from the web and got nothing to do with my fog environment.thanks
-
@krishna Using a random screenshot and not explain it costed you two days by pointing to the wrong direction. The clearer your information is the more we are able to help you.
OK, so this is a normal single master FOG node setup and we can rule out routing because FOG server and PXE booting clients are all in the same subnet?
So you have the firewall disabled in the FOG server?
Where clients ever able to PXE boot to the menu? If yes, when did it work last and what changed since then?
About the access.log - I just figured that Ubuntu moved to a different name at some point. Please run
tail -f /var/log/apache2/*.logwhile you PXE boot one client to see if it shows up in the log. -
This post is deleted! -
This post is deleted! -
Here is the log output
tail -f /var/log/apache2/*.log
==> /var/log/apache2/access.log <====> /var/log/apache2/error.log <==
[Mon May 17 00:00:01.329479 2021] [mpm_prefork:notice] [pid 18103] AH00163: Apache/2.4.41 (Ubuntu) OpenSSL/1.1.1f configured – resuming normal operations
[Mon May 17 00:00:01.329494 2021] [core:notice] [pid 18103] AH00094: Command line: ‘/usr/sbin/apache2’==> /var/log/apache2/other_vhosts_access.log <==
192.168.172.10:80 192.168.172.54 - - [17/May/2021:14:12:01 +0930] “POST /fog/service/ipxe/boot.php HTTP/1.1” 200 3388 “-” “iPXE/1.20.1+ (g4bd0)” -
@krishna said in PXE Windows Client registration:
==> /var/log/apache2/other_vhosts_access.log <==
192.168.172.10:80 192.168.172.54 - - [17/May/2021:14:12:01 +0930] “POST /fog/service/ipxe/boot.php HTTP/1.1” 200 3388 “-” “iPXE/1.20.1+ (g4bd0)”Did that show up exactly at that Point in time when the client tried to load it? We see the client requesting the boot.php file for the FOG menu and it’s answered with a HTTP 200 status code. So it doesn’t seem to be an issue on the FOG server.
Does this happen with different hardware clients?
-
-
@sebastian-roth
We only got HP Laptop hardware at the moment to test and all the devices reboot at this point and the FOG menu doesnt comeup at all,Thanks
-
@krishna Are these HP laptops different models?
I suggest you install tcpdump on your FOG server and capture network traffic so we might get more of an idea what’s happening:
tcpdump -w /tmp/pxe_no_boot.pcap port 80 or port 67 or port 68 or port 69Prepare this command and start up one of the laptops. Fire up the command and let it sit there (does not return to the command line). Let the laptop boot up to that point we see in the picture and then stop tcpdump (ctrl-c). Upload the captured PCAP file here in the forums or to an external fileshare and post a link.
-
@sebastian-roth
All the laptops we have are HP Probook x360 435 G7 model,thanks
