HP BL10e Setting up a Linux PXE server and integrating clients - Page 9

A sample syslinux.cfg is included in Appendix b.

Get HP BL10e - ProLiant - G2 PDF manuals and user guides
UPC - 808736933599
View all HP BL10e manuals
Add to My Manuals
Save this manual to your list of manuals

Page 9 highlights

Once the previous steps are complete, the following directory structure will exist: • /tftpboot/ • /tftpboot/pxelinux.0 • /tftpboot/rhl80-vmlinuz • /tftpboot/rhl80-initrd.img • /tftpboot/pxelinux.cfg/ • /tftpboot/pxelinux.cfg/rhl80-syslinux.cfg Note Run the "import-to-tftpboot.sh" script located in Appendix b to automatically accomplish the tasks described this step. 5. A configuration file must be created to control what happens when the PXE client boots to PXE. As an example, we will create the rhl80-kickstart-install-syslinux.cfg file by copying it from rhl80syslinux.cfg using the following command: cp -a rhl80-syslinux.cfg rhl80-kickstart-install-syslinux.cfg A sample of the file contents is located in Sample 2 of Appendix b. 6. Create a soft link from the syslinux.cfg file to the IP address of the client server, which is converted to HEX. In this example, the client server, 172.48.1.253, converted to HEX is AC3001FD. Use these commands to create the soft link: cd /tftpboot/pxelinux.cfg ln -s rhl80-kickstart-install-syslinux.cfg AC3001FD Another acceptable soft link to create is one named "default." The use of the default entry affects any clients that may PXE boot and do not have a specific HEX IP address entry in /tftpboot/pxelinux.cfg. In the following example, we demonstrate linking the sample "localbootsyslinux.cfg" to a soft link called "default": cd /tftpboot/pxelinux.cfg ln -s localboot-syslinux.cfg default A sample syslinux.cfg is included in Appendix b. 7. Boot the client to PXE to begin kickstart installation. PXE is often the fourth choice in the boot order list. If no bootable media is found in the floppy, CD-ROM drive, or hard drive, it will default to PXE. If the hard drive has been partitioned, it may no longer default to PXE even though the hard drive is not bootable. In some large cluster farms, boot to PXE is moved to the top of the boot order. Then the PXE server, through the use of soft links in the /tftpboot/pxelinux.cfg directory, controls whether the client loads a new operating system or if the client boots to its hard drive. 9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
Once the previous steps are complete, the following directory structure will exist:
•
/tftpboot/
•
/tftpboot/pxelinux.0
•
/tftpboot/rhl80-vmlinuz
•
/tftpboot/rhl80-initrd.img
•
/tftpboot/pxelinux.cfg/
•
/tftpboot/pxelinux.cfg/rhl80-syslinux.cfg
Note
Run the "import-to-tftpboot.sh" script located in Appendix b to
automatically accomplish the tasks described this step.
5.
A configuration file must be created to control what happens when the PXE client boots to PXE.
As an example, we will create the rhl80-kickstart-install-syslinux.cfg file by copying it from rhl80-
syslinux.cfg using the following command:
cp -a rhl80-syslinux.cfg rhl80-kickstart-install-syslinux.cfg
A sample of the file contents is located in Sample 2 of Appendix b.
6.
Create a soft link from the syslinux.cfg file to the IP address of the client server, which is converted
to HEX. In this example, the client server, 172.48.1.253, converted to HEX is AC3001FD. Use
these commands to create the soft link:
cd /tftpboot/pxelinux.cfg
ln -s
rhl80-kickstart-install-syslinux.cfg
AC3001FD
Another acceptable soft link to create is one named "default." The use of the default entry affects
any clients that may PXE boot and do not have a specific HEX IP address entry in
/tftpboot/pxelinux.cfg. In the following example, we demonstrate linking the sample "localboot-
syslinux.cfg" to a soft link called "default":
cd /tftpboot/pxelinux.cfg
ln -s
localboot-syslinux.cfg
default
A sample syslinux.cfg is included in Appendix b.
7.
Boot the client to PXE to begin kickstart installation.
PXE is often the fourth choice in the boot order list. If no bootable media is found in the floppy,
CD-ROM drive, or hard drive, it will default to PXE. If the hard drive has been partitioned, it may
no longer default to PXE even though the hard drive is not bootable. In some large cluster farms,
boot to PXE is moved to the top of the boot order. Then the PXE server, through the use of soft links
in the /tftpboot/pxelinux.cfg directory, controls whether the client loads a new operating system or
if the client boots to its hard drive.
9