Pxe+kickstart Configuration Detailed

PXE Concept Introduction:

The difference between PXE technology and RPL technology is that RPL is a static route and PXE is a dynamic route. RPL is a frame (frame) that makes a request to the server based on the ID number on the network card plus other records. This ID data is already in the server, and the match succeeds for remote boot. PXE uses the DHCP service to specify an IP address for this MAC address based on the MAC address of the artifact station that is received by the server. Each start may have the same workstation with the last boot has a different IP, that is, dynamic allocation of addresses. The principle of PXE is described under the client boot process.

(1) After the client boot up, the PXE bootrom (since the start chip) to obtain control to perform self-test, and then broadcast the form of a request find frame.

(2) If the server receives the request sent by the client, it will send back the DHCP response, including the IP address, the preset communication channel, and the boot image file, otherwise the server will ignore this requirement.

(3) When the client receives a response from the server, it responds with a frame to request that the file be started and the MAC address is written to the server-side netnames.db file.

(4) More messages will be answered between the client and the server to determine the startup parameters. Bootrom Download the boot image document from the server by the TFTP communication protocol. After the client receives the boot file using the TFTP protocol, it forwards the control to the boot block to boot the operating system and completes the remote boot.

Kickstart Concept Introduction:

Kickstart is a way to install unattended. Kickstart works by recording the various parameters that are required for manual intervention during a typical installation process, and generates a file called Ks.cfg, and in subsequent installations (not limited to machines that generate kickstart installation files) when a request for a parameter is required, The installer will first look for the files generated by the kickstart, and when the appropriate parameters are found, use the found parameters, and the installer must manually intervene when the appropriate parameters are not found. This way, if the kickstart file covers all the parameters that appear during installation, the installer can simply tell the installer where to take the Ks.cfg file, and then go to your own business. After installation, the installer restarts the system according to the reboot option set in Ks.cfg and ends the installation.

Kickstart process:

General process: DHCP (get IP, look for TFTP) >tftp (Swap get boot file/tftpboot that folder) >http (load installation files) > Local Installation

Detailed Flowchart:

Installation process:

One, closed the SELinux iptables

Vim/etc/sysconfig/selinux

Change into selinux=disabled

Service Iptables Stop

Chkconfig iptables off