From 7b79db84525600183b6ead82c65bd15ab67e814f Mon Sep 17 00:00:00 2001 From: Jana Halackova Date: Thu, 17 Oct 2024 15:11:44 +0200 Subject: [PATCH] Added DHCP dynamic addresses configuration. --- articles/deployment-pxe-boot.asm.xml | 7 +- concepts/deployment-network-boot.xml | 38 ++++++++ tasks/deployment-network-dhcp.xml | 141 +++++++++++++++++++++++++++ 3 files changed, 183 insertions(+), 3 deletions(-) create mode 100644 concepts/deployment-network-boot.xml create mode 100644 tasks/deployment-network-dhcp.xml diff --git a/articles/deployment-pxe-boot.asm.xml b/articles/deployment-pxe-boot.asm.xml index 499ebcbb..5cb6bdd8 100644 --- a/articles/deployment-pxe-boot.asm.xml +++ b/articles/deployment-pxe-boot.asm.xml @@ -123,7 +123,7 @@ Smart Docs Documentation - maintainer@suse.com + jsindelarova@suse.com yes @@ -133,7 +133,8 @@ WHAT? - Describe your topic in one sentence. + &productname; provides images that can be deployed remotely using the PXE boot of the + target device. @@ -141,7 +142,7 @@ WHY? - State the reason why one should read this. + You want to deploy &productname; remotely. diff --git a/concepts/deployment-network-boot.xml b/concepts/deployment-network-boot.xml new file mode 100644 index 00000000..84b16215 --- /dev/null +++ b/concepts/deployment-network-boot.xml @@ -0,0 +1,38 @@ + + + + + %entities; +]> + + + + + + + Preparing network boot environment + + + + + The topic is an overview of prerequisites needed for network boot. + + + + + &productname; can be installed via a Preboot Execution Environment (PXE). The client hardware needs to support booting via PXE. The network needs to provide a DHCP server and a TFTP server providing the required data to the clients. This section guides you through setting up the required servers. + + + This section covers the configuration tasks needed in complex boot scenarios. It contains + ready-to-apply configuration examples for DHCP, PXE boot, TFTP, and Wake on LAN. On contrary, + the section does not provide instructions on deploying an installation server. + + diff --git a/tasks/deployment-network-dhcp.xml b/tasks/deployment-network-dhcp.xml new file mode 100644 index 00000000..595fdb0b --- /dev/null +++ b/tasks/deployment-network-dhcp.xml @@ -0,0 +1,141 @@ + + + + + %entities; +]> + + + + + + + Setting up a DHCP server + + + + + The topic covers steps to configure the DHCP server for PXE network boot. + + + + + A DHCP server provides both dynamic and static IP address assignments to your network clients. + It advertises servers, routes, and domains. The clients transmit their architecture type in their DHCP requests. Based on this information, the DHCP server decides which files the client must download for booting. + +
+ Dynamic address assignment + + The following example shows how to set up a DHCP server that dynamically + assigns IP addresses to clients, and advertises servers, routers, domains, + and boot files. + + + + + Log in as &rootuser; to the machine hosting the DHCP server. + + + + + Enable the DHCP server by executing systemctl enable + dhcpd. + + + + + Append the following lines to a subnet configuration of your DHCP + server's configuration file located under + /etc/dhcpd.conf: + + # The following lines are optional + option domain-name "my.lab"; + option domain-name-servers 192.168.1.1; + option routers 192.168.1.1; + option ntp-servers 192.168.1.1; + ddns-update-style none; + default-lease-time 3600; + + # The following lines are required + option arch code 93 = unsigned integer 16; # RFC4578 + subnet 192.168.1.0 netmask 255.255.255.0 { + next-server 192.168.1.1; + range 192.168.1.100 192.168.1.199; + default-lease-time 3600; + max-lease-time 3600; + if option arch = 00:07 or option arch = 00:09 { + filename "/EFI/x86/grub.efi"; + } + else if option arch = 00:0b { + filename "/EFI/aarch64/bootaa64.efi"; + } + else { + filename "/BIOS/x86/pxelinux.0"; + } + } + + This configuration example uses the subnet + 192.168.1.0/24 with the DHCP, DNS and gateway on the + server with the IP 192.168.1.1. Make sure that all + IP addresses are changed according to your network layout. For more + information about the options available in + dhcpd.conf, refer to the + dhcpd.conf manual page. + + + + + Restart the DHCP server by executing systemctl restart + dhcpd. + + + +
+
+ Executing the task + + A paragraph of text. + + + + A short introduction to the procedure. + + + + A step. + + + + + A second step. + + + + + A third step. + + + +
+
+ Summary + + A paragraph of text, summing up the result of the task. + +
+
+ Troubleshooting + + Add some troubleshooting information, if applicable. + +
+