Using ISAAC 1.1, and want to set up the PXE server using the ISAAC.cfg and firstbox_run.sh
The PXE server script completed without errors, but I noticed the following in the output.
2011-10-11 09:29:44 leo-pxe.leo.austin.ibm.com Network Configuration 5, 255, RANGE=250, NUM_VMS=11
2011-10-11 09:29:44 leo-pxe.leo.austin.ibm.com Network Configuration Network: 10.0.0.0
2011-10-11 09:29:44 leo-pxe.leo.austin.ibm.com Network Configuration First box: 0
2011-10-11 09:29:44 leo-pxe.leo.austin.ibm.com Network Configuration Gateway: 10.0.0.1
That caused the http URLs put into the kickstart files build them like http://0/isaac/storage-ks.cfg
Question: Should the URL be instead containing the IP address of the PXE server ? Like http://10.0.0.1/isaac/storage-ks.cfg, or is this a symptom of a bigger problem.
Cannot recollect how this looked like when I had Beta_3 installed. But, the storage and other nodes did not fail on ks download.
This PXE server, set up using GA build, is causing the storage-node to not find the kickstart file. If I modify the URL with the correct IP address when the storage-node boot stalls with an error, the install moves forward.
Is the ISAAC.cfg missing any key=value pair, or did I miss any steps prior to running the firstbox_run.
SystemAdmin 110000D4XK24 Posts
Re: Set up PXE server2011-10-12T16:24:40ZThis is the accepted answer. This is the accepted answer.Resolved.
Set up the system again as a Beta-3 first server, confirmed all required services (dhcp, tftp, http, dns) are running. Ran the first box set up on ISAAC1.1 again, and that fixed it.
ken_yang 1200009CHT1 Post
bjyangf 2700043GTA1 Post
Re: Set up PXE server2011-10-31T05:29:34ZThis is the accepted answer. This is the accepted answer.Withou any further logs, I guess this is probably caused by not setting the IP address for the first box prior to running firstbox_run. But to make things sure, can you guys please attach the log of firstbox_run, which is something like /tmp/firstbox-<date and time>.log?