Build a CentOS7 server for: pxe boot, kickstart, reposync, repotrack, nfs, https (STEP 9)

Posted on by Daniel Oliver
STEP 9 – ENABLE and CONFIGURE PXE:
note: This does NOT require CentOS/RHEL to provide NTP, DHCP, DNSMASQ/BIND, vsftd, or xinetd.  The VMware Fusion VMNET2 DHCP scope can provide PXE Server location to clients.
  • enable firewall port for tftp
  • enable the service.
    • systemctl start tftp.socket
    • systemctl enable tftp.socket
  • put some important files into the tftp server location:
    • cd /var/lib/tftpboot                                  # // it starts out empty.
    • cp /usr/share/syslinux/{pxelinux.0,vesamenu.c32} .    # // now it has those two files in it.
  • Create a menu for the PXE Service… (the options a client machine gets):
    • mkdir /var/lib/tftpboot/pxelinux.cfg
    • cd /var/lib/tftpboot/pxelinux.cfg/
    • nano default
* In the next step, I’ll provide a detailed example of a /var/lib/tftpboot/pxelinux.cfg/default PXE BOOT MENU.

One thought on “Build a CentOS7 server for: pxe boot, kickstart, reposync, repotrack, nfs, https (STEP 9)”

  1. Pingback: Build a CentOS7 server for: pxe boot, kickstart, reposync, repotrack, nfs, https (summary of steps) – aitrusblog

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Google photo

You are commenting using your Google account. ( Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s