Skip to main content

Setting up a PXE-Server with CentOS 7

Setting up a PXE server can be very usefull in home and enterprise networks, whether you want to provision a bunch of machines or just be lazy when it comes to OS installations (kickstart is your friend).
For this setup, I'm using a fully up-to-date CentOS 7 installation.

For making PXE possible, we need a few services which we can install by running the following command:
 [archy@pxe-server ~]$ sudo yum -y install dhcp syslinux tftp-server nfs-utils
I think most of them are pretty self explanatory. Syslinux is a bunch of bootloaders for network-booting. When everything is installed, let's dig in to the configuration.

First up, the dhcp-config, I'll configure a simple subnet.
 [archy@pxe-server ~]$ sudo vim /etc/dhcp/dhcpd.conf 
 subnet 172.31.10.0 netmask 255.255.255.0 {  
     range 172.31.10.100 172.31.10.200;  
     option subnet-mask 255.255.255.0;  
     # my 2 ipa-servers as dns ...  
     option domain-name-servers 172.31.10.250, 172.31.10.251;  
     # ... and ntp-servers  
     option ntp-servers 172.31.10.250, 172.31.10.251;  
     option domain-name "archyslife.lan";  
     option routers 172.31.10.254;  
     option broadcast-address 172.31.10.255;  
     # this is PXE specific  
     filename "pxelinux.0";  
     next-server "172.31.10.10";  
 }
The PXE specific parameters tell the client to look for the 'pxelinux.0'-file on the server '172.31.10.10'. We will get to syslinux later, but for now, we need to download a installation.iso from the centos-mirrors (or use an existing one) to copy the necessary files.
 [archy@pxe-server ~]$ wget http://merlin.fit.vutbr.cz/mirrors/centos/7/isos/x86_64/CentOS-7-x86_64-Everything-1708.iso
and mount the iso temporary to the /mnt folder to copy the necessary files to the tftpboot-directory.
 [archy@pxe-server ~]$ sudo mount -o loop CentOS-7-x86_64-Everything-1708.iso /mnt  
 [archy@pxe-server ~]$ sudo mkdir /var/lib/tftpboot/centos7  
 [archy@pxe-server ~]$ sudo cp /mnt/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/centos7
With that done, we need to create a local repo of the installation disk. I'll cover the installation using nfs, but ftp:// and http:// are also possible to use.
 [archy@pxe-server ~]$ sudo mkdir --parents /images/CentOS-1708  
 [archy@pxe-server ~]$ sudo cp -r /mnt/* /images/CentOS-1708  
 [archy@pxe-server ~]$ sudo chmod -R 755 /images/CentOS-1708  
 [archy@pxe-server ~]$ sudo umount /mnt  
 [archy@pxe-server ~]$ sudo vim /etc/exports
and add the following content
 /images/CentOS-1708  172.31.10.0/24(ro,secure,async,no_subtree_check)
We already installed the syslinux-bootloaders. They are located in the '/usr/share/syslinux' directory. We will copy all of its content to our tftp root directory, which is by default '/var/lib/tftpboot'.
 [archy@pxe-server ~]$ sudo cp -r /usr/share/syslinux/* /var/lib/tftpboot
With the bootloaders copied, the dhcp-server set up and the images copied, there is the pxe-menu still left to work on. Create the pxelinux.cfg folder and the default file which will store our configuration.
 [archy@pxe-server ~]$ sudo mkdir /var/lib/tftpboot/pxelinux.cfg/  
 [archy@pxe-server ~]$ sudo touch /var/lib/tftpboot/pxelinux.cfg/default
And this is what I will add to my configuration file
 default menu.c32   
 prompt 0   
 timeout 300   
 ONTIMEOUT   
 menu title ######## PXE Boot Menu ########  
 label 1   
 menu label ^1) Boot from local drive   
 localboot 0x00  
 label 2  
 menu label ^2) Install CentOS 7 using local Repo with Kickstart   
 kernel centos7/vmlinuz   
 append initrd=centos7/initrd.img ks=http://web01.archyslife.lan/ks-minimal.cfg inst.stage2=nfs:172.31.10.10:/images/CentOS-1708   
 label 3  
 menu label ^3) Install CentOS 7 using local Repo without Kickstart   
 kernel centos7/vmlinuz   
 append initrd=centos7/initrd.img inst.stage2=nfs:172.31.10.10:/images/CentOS-1708
This gives us three options in the boot menu, first being the boot from the local hdd, second being the pxe-installation using a kickstart file and third being the pxe-installation not using a kickstart file. In the second configuration I will fetch my kickstart-file from my internal webserver and use the nfs-share to fetch the necessary files to start the installation automatically.

All that is left to do now, is restart and enable the services and configure the firewall. There is no SELinux configuration necessary for this configuration. You would have to change the contexts of the tftpboot-folder if you would use non-standard folders.
 [archy@pxe-server ~]$ sudo systemctl restart dhcpd.service  
 [archy@pxe-server ~]$ sudo systemctl restart nfs.service  
 [archy@pxe-server ~]$ sudo systemctl enable dhcpd.service  
 [archy@pxe-server ~]$ sudo systemctl enable nfs.service  
 [archy@pxe-server ~]$ sudo systemctl enable tftp.serice  
 [archy@pxe-server ~]$ sudo firewall-cmd --add-service={dhcp,nfs,tftp} --permanent  
 [archy@pxe-server ~]$ sudo firewall-cmd --add-port=20048/tcp --permanent  
 [archy@pxe-server ~]$ sudo firewall-cmd --reload
That's it from the server site. Feel free to spin up any VM and test it out yourself.
For debugging, have a look at the logs created. Some useful commands are listed below.
 journalctl -xn dhcpd.service  
 journalctl -xn nfs.service  
 journalctl -xn tftp.service  
 tail -f /var/log/messages
Feel free to comment and / or sugguest a topic.
Labels:

Comments

Post a Comment

Popular posts from this blog

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0 ...
Post a Comment
Read more

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but  for a detailed comparison check out this  article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla...
8 comments
Read more

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?...
9 comments
Read more

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key"; controls { inet 172.31.0.1 port 953 allow { 172.31.0.5; } keys ...
2 comments
Read more

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the...
Post a Comment
Read more