Test environment: Win10/vmware Workstation Pro
Operating system: RHEL 6.5 (PXE server)
Installation and configuration:
。 Install DHCP
。 Install xinetd and enable the TFTP service
。 Install Syslinux (yum installation): pxelinux.0 and Seamenu.c32 files are automatically placed in the Tftpboot directory, and there are other files
Configure DHCP: Add filename "pxelinux.0" to the Address assignment subkey
Configuration tftp:enable, no other special configuration, no-C, the entire process will not write to TFTP file
Configuration menu: Under the Tftpboot directory, create a default file, which is a menu file, such as the following file:
Once configured, you can start a PXE client for testing, and normally, you can display the menu. Note that the PXE configuration is successful, then you can customize the default file, develop the Ks.cfg file, and deploy the installation package according to the actual installation requirements.
Workflow analysis (based on the results of the capture package):
1.DHCP: Assign IP address and assign pxelinux.0 file name to PXE client
2. The client gets pxelinux.0 via TFTP, about 19 blocks
3. Client run pxelinux.0, ready to take configuration file
4. Continuous tftp several files (about 10 or so, the filename as if it is related to the MAC address, must not be found), Pxelinux.cfg directory
564d330d-5a45-e2de-eb15-88e321e7dfd2
01-00-0c-29-e7-df-d2
/c0a89464
c0a8946
c0a894
C0a89
C0a8
c0a
C0
C
The above file is definitely not, finally get the default file.
5. After the success, the client will continue TFTP, take vesamenu.c32, about 117blocks
6. The client takes the corresponding MENU.C32, runs on the client, and the client is based on the default display menu that was previously received.
Troubleshooting:
1. PXE client DHCP succeeds, but tftp ..... Error
The iptables of the PXE server is not turned off (regardless of the firewall of the host Windows)
2.
RHEL 6.5 PXE Installation debugging