PXE help
-
I have an existing environment with an old Solaris DHCP server that I don’t know much about. The only thing that I have done with this server is to vi the IP segment file in /var/dhcp to add new devices that require DHCPing
I installed FOG 1.1.0 configured pointing to my DHCP server and told FOG not to run DHCP - PXE boot does not work
I then deleted the MySQL database, delete fog by rm -R /opt/fog I reinstalled FOG and this time I told it to run DHCP. I erroneously pointed the the DHCP ROUTER to my router instead of the DHCP server. - PXE worked but the new fog DHCP server was stepping on my old DHCP server and devices were getting the wrong IPs
Can anyone provide any guidance on how to make FOG & PXE work with my old DHCP server - keep in mind I don’t know much about the old DHCP server or how it was configured.
-
My guess is the dhcp server you have in place wasn’t working because it’s not passing the next-server or boot file parameters.
I’d make a copy of your FOG Server’s dhcpd.conf file and remove the packages for it from your FOG Server. Compare the dhcpd.conf file from your Solaris and dhcpd.conf from the fog server and find out how DIFFERENT they really are. My guess is it will actually be pretty simple.
-
what file is your option 67 pointing to? it should be undionly.kpxe
-
[quote=“Tom Elliott, post: 29835, member: 7271”]My guess is the dhcp server you have in place wasn’t working because it’s not passing the next-server or boot file parameters.
I’d make a copy of your FOG Server’s dhcpd.conf file and remove the packages for it from your FOG Server. Compare the dhcpd.conf file from your Solaris and dhcpd.conf from the fog server and find out how DIFFERENT they really are. My guess is it will actually be pretty simple.[/quote]
WOW that was a quick response
I attempted to go down that path but I can’t find a dhcp.conf file on my Solaris server - I did find a dhcptab file in /var/dhcp but I’m not sure how to add PXE or next server. The dhcptab file seems to define the DHCP environment. perhaps I can add the next server there if I knew the syntax
Locale m :UTCoffst=-14400:
sun1234 m :Include=Locale:LeaseTim=1728000:LeaseNeg:
172.16.0.0 m :Subnet=255.255.0.0:Router=172.16.0.1:
:DNSserv=172.16.0.2:Broadcst=172.16.255.255:
:MTU=1500:NetBNms=172.16.0.3 172.16.0.2:
:DNSdmain=mydomain.com:NISdmain=xxx.mydomain.com:
:NISservs=172.16.0.2:Timeserv=172.16.0.2: -
P.S. DHCP seems to work - if I add new MAC addresses the server does reply with the address defined in the dhcp pool file
-
Well I’m confused
I redid the fog server and told it to do DHCP
This is what it BUILT
DHCP Server Configuration file.
see /usr/share/doc/dhcp*/dhcpd.conf.sample
This file was created by FOG
use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 172.16.50.254;subnet 172.16.50.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
range dynamic-bootp 172.16.50.10 172.16.50.254;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers 172.16.0.186;
option routers 172.16.0.1;
filename “undionly.kpxe”;The wiki at [url]http://www.fogproject.org/wiki/index.php/Integrating_FOG_into_an_Existing_Network_in_non_intrusive_mode[/url]
talks to modifying this file. Since I don’t know what the file looked like before I’m not sure I know what the differences are. Equally confusing is the machine that is receiving an IP from FOG. - In my environment all machines begin to get DHCP from FOG instead of my existing DHCP server.My network is 172.16.x.x 255.255.0.0 The fog server is bing placed on the same subnet
This does mess with my existing DHCP server.
-
Don’t let fog be DHCP. If you already have a DHCP server it is bad to introduce another into the mix.
If you are having trouble resolving your bootfile in your network, try using DNSMasq to help alleviate the bootfile issues.
-
[quote=“Jaymes Driver, post: 29873, member: 3582”]Don’t let fog be DHCP. If you already have a DHCP server it is bad to introduce another into the mix.
If you are having trouble resolving your bootfile in your network, try using DNSMasq to help alleviate the bootfile issues.
I’m such a noob at this
I’m running FOG on ubuntu server 12.04 LTS - I see in the link you provided ubuntu 12 is tested and working so I will give that a whirl.
Thank you
-
[quote=“DoubleD, post: 29879, member: 24577”]I’m such a noob at this
I’m running FOG on ubuntu - I see in the link you provided ubuntu 12 is tested and working so I will give that a whirl.
Thank you[/quote]
I use this in my environment, it is reliable. I have used it on all version of Ubuntu to date.
-
This post is deleted! -
[quote=“Jaymes Driver, post: 29880, member: 3582”]I use this in my environment, it is reliable. I have used it on all version of Ubuntu to date.[/quote]
Jaymes - Thank you ever so much this worked! ! !
:oops: I erroneously followed the directions for FOD 0.33 and it was all messed up. After rereading the [URL=‘http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE’]install instructions[/URL] I saw my error and undid all the stuff for FOG 033 and it worked like a charm - Now to try to figure out how to make images from an existing machine and then dump the image back
[INDENT=1]This information pertains to FOG 0.33 and the new iPXE boot method.[/INDENT]
[INDENT=1]In order to continue to use dnsmasq to dole out ip addresses and to help find the boot file, some changes need to be made to force the boot file to load the iPXE boot file.[/INDENT]
[INDENT=1][B]FIRST Update the schema by navigating to your fog management page and install the update.[/B][/INDENT]
