@Sebastian-Roth said:
@Eldorado What you experience is perfectly fine. The clients shouts back to the server not when it starts a task but when it finishes! You need to cancel the task in the web interface to stop the client from booting into it again and again…
innnnteresting.
I’ll give it a try… this is great… lol thanks for everything!
@Eldorado said:
@Sebastian-Roth said:
@Eldorado Oh well, I somehow thought that you are running FOG trunk. But looks like version 1.2.0 by the directory listing you just posted. You can download the latest ipxe.iso here (click ‘view raw’).
Thanks - I’ll look into that…
having said that - your suggestion in the first post to run the default.ipxe rather than the boot.php file worked! everything is working as expected now once I added the PARAM_CMD file…
Thank you so much for everything!
Spoke too soon -
it’s registering the host now (and it shows on the menu screen it’s registered).
I am now successfully able to push down tasks from the server. I’ve started memtest, and tried to trigger an antivirus scan (even though the av scan fails, it still attempts to run at boot).
But now it won’t break out of the task… do the tasks need to complete fully for the server to stop sending it down?
For example, here is my experience:
Here is what i’m expecting:
Is my understanding correct?
@Sebastian-Roth said:
@Eldorado Oh well, I somehow thought that you are running FOG trunk. But looks like version 1.2.0 by the directory listing you just posted. You can download the latest ipxe.iso here (click ‘view raw’).
Thanks - I’ll look into that…
having said that - your suggestion in the first post to run the default.ipxe rather than the boot.php file worked! everything is working as expected now once I added the PARAM_CMD file…
Thank you so much for everything!
@Sebastian-Roth said:
@Eldorado Well, add PARAM_CMD when building on rom-o-matic.eu
Tom was asking why you don’t use the ISO provided by FOG? See in your /tftpboot directory on the FOG server. There should be an ipxe.iso file that you can use. It hast got an advanced ipxe script embedded - same as all the other iPXE binaries you see in that directory.
Take a look at the script. It does some checks but essentially it does just get an IP via DHCP and then loads default.ipxe…
Hi Sebastian - When I look at the Fog tftpboot folder, I see:
boot.txt
default.ipxe
ipxe.kkpxe
ipxe.kpxe
ipxe.krn
ipxe.pxe
memdisk
pxelinux.0.old
snponly.efi
endionly.kkpxe
undionly.kpxe
undionly.kpxe.intel
undion.pxe
vesamenu.c32
I don’t see an ipxe.iso file.
@Sebastian-Roth said:
@Eldorado Try using this as embedded script:
#!ipxe dhcp chain tftp://ip.of.fog.server/default.ipxeBy the way, you don’t need to burn CD/DVDs every time you change iPXE. You can generate iPXE image to write onto USB key…
Hi Sebastian, thank you for the suggestion.
I tried what you did, and i’m getting this error at boot:
tftp://#.#.#.#/default.ipxe... ok
params: command not found
Cound not boot: Exec format error (http://ipxe.org/2e022001)
Here is the content of my default.ipxe file:
#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain http://#.#.#.#/fog/service/ipxe/boot.php##params
Hi Tom,
the current .iso i’m using has the embedded script. Sebastian has asked me to run something different other than what I have.
Hi Sebastian - thanks for the USB suggestion.
I’m testing the ISO by mounting it in the VM first. I burned it to a cd to test on a workstation outside of a VM to see if it was VMware that was causing the problem. same result.
We will be using usb keys for the final deployment though.
thanks for this - I’ll give it a try. I tried generating a new iPXE a few minutes ago and it was failing… will try again later.
I used the rom-o-matic.eu site with the following options checked:
PCI_SETTINGS
COMDATA
COMSTOP
NET_PROTO_IPV4
NET_PROTO_STP
PXE_STACK
PXE_MENU
DOWNLOAD_PROTO_TFTP
DOWNLOAD_PROTO_HTTP
HTTP_AUTH_BASIC
HTTP_AUTH_DIGEST
CRYPTO_80211_WEP
CRYPTO_80211_WPA
CRYPTO_80211_WPA2
DNS_RESOLVER
AUTOBOOT_CMD
NVO_CMD
CONFIG_CMD
IFMGMT_CMD
IWMGMT_CMD
FCMGMT_CMD
ROUTE_CMD
IMAGE_CMD
DHCP_CMD
SANBOOT_CMD
MENU_CMD
LOGIN_CMD
SYNC_CMD
AUTOBOOT_ROM_FILTER
DHCP_DISC_MAX_DEFERRALS
PXEBS_START_TIMEOUT_SEC
And my pasted script:
#!ipxe
dhcp
chain http://IPofSERVER/fog/service/ipxe/boot.php
|
it built the ISO and I used Imgburn to burn to DVD.
Thanks Tom.
How can I rectify this? Would this be in the ipxe config?
Hi All,
presently testing a Fog deployment using virtual machines. I have everything seemingly working properly. On the client workstations, I’m using a boot cd with ipxe configured to look to my Fog server running in VMware/Ubuntu.
The clients boot to the CD, find the Fog server, load the menu and give me options.
I can successfully perform a registration, according to the client. It takes the data, and says it successfully sends to the server. Checking the server confirms this - everything is there. MAC address is properly configured, as well as all other details.
When I reboot the client to the Fog menu, it shows me in red text “Host is NOT Registered!”
Performing another registration fails because it says it IS registered.
So help me try to understand what i’m doing wrong. I thought it was a fault of my install (using Ubuntu 14.10), so I tried using Ubuntu 12.10 as well - same results.
any help troubleshooting this would be appreciated. I found a few posts on here related to this issue, but their steps to resolve their problems didn’t help me.
Thanks Everyone.
@Wayne-Workman said:
@george1421 said:
Why would you not use dnsmasq to supply the pxe boot information instead of building your own ipxe boot images? dnsmasq can be used to fill in missing information that your dhcp server can’t/won’t supply.
Why would you not just set your DHCP to support your infrastructure? That’s how I see it. In my mind, proxyDHCP is best suited for a mobile FOG server.
George – I’m new to everything around here… what i’ve done, i only started even reading about a couple of days ago. can you give me more information on the dnsmasq method you mention? It might suit my needs better.
Wayne – our environment is very different from most workplaces as there are multiple IT teams in a hospital environment. The hospital manages the network and infrastructure - my team just supports a single department within the big group… so chances of the hospital allowing us to edit the DHCP server is next to nil.
great success with #2 above – I was missing CONSOLE_FRAMEBUFFER and CONSOLE_DIRECT_VGA.
Adding these in allowed the menu to appear as it should… awesome! one step closer.
any additional suggestions on how to best manage multiple client hard drives?
@Sebastian-Roth hi Sebastian - thanks for your reply.
I have everything working in a VM test environment as it should be (background and all) when server/client are on the same IP subnet.
The problem is in our real world environment, we have many different IPs ranging from 10.2.x.x, 10.3.x.x, 10.4.x.x, etc… — and we do not have direct access to the DHCP server.
I’m new to all of this PXE booting business, and thought that this was my only option.
@ITSolutions said:
You can run debug to find which drive shows up in which order on the particular machine.
thank you for your reply! I appreciate the help.
Is there a way to tell this information from the server side? Is it possible to, say, return the drive type/serial number?
or would using something like WMIC something that I would have to resort to here?
Hi All, I started looking into FOG last week and have learned a ton.
I’ve set up the server and it’s running successfully with PXE on the same network segment.
I have two questions.
some of our workstations have 1 hdd and some have 2. I’ve seen tutorials online of restoring images and it seems straight forward enough, but how do I capture an image of only 1 of the hard drives and restore to a drive of my choosing? (may not always be the same drive). ----or is this even possible?
this may be the wrong forum to ask for quick help on iPXE, if so then just ignore… but I’m having trouble with the ROM-o-matic build I’m creating. It’s not showing the FOG formatted screen properly. There is no image, it’s all blue, and the tables don’t look to be lined up properly. I’ve ensured that I have selected PNG image support, but not sure where else to check here… (i suspect it might be a resolution issue of the test VM that i’m using, but not sure yet).
Any and all help with the above would be greatly appreciated. Thanks!