7.2 KiB

Raw Blame History

Configure a PXE Boot Server

You can optionally set up a Boot Server to support controller-0 initialization.

includes a setup script to simplify configuring a boot server. If you prefer, you can manually apply a custom configuration; for more information, see Access PXE Boot Server Files for a Custom Configuration <accessing-pxe-boot-server-files-for-a-custom-configuration>.

The setup script accepts a path to the root TFTP directory as a parameter, and copies all required files for BIOS and clients into this directory.

The boot server serves a boot loader file to the requesting client from a specified path on the server. The path depends on whether the client uses BIOS or . The appropriate path is selected by conditional logic in the configuration file.

The boot loader runs on the client, and reads boot parameters, including the location of the kernel and initial ramdisk image files, from a boot file contained on the server. To find the boot file, the boot loader searches a known directory on the server. This search directory can contain more than one entry, supporting the use of separate boot files for different clients.

The file names and locations depend on the BIOS or implementation.

Table 1. boot server file locations for BIOS and implementations
Resource	BIOS	UEFI
boot loader	./pxelinux.0	./EFI/grubx64.efi
boot file search directory	./pxelinux.cfg	./ or ./EFI (system-dependent)
boot file and path	./pxelinux.cfg/default	./grub.cfg and ./EFI/grub.cfg
(./ indicates the root TFTP directory)

Use a Linux workstation as the Boot server.

On the workstation, install the packages required to support , TFTP, and Apache.
Configure , TFTP, and Apache according to your system requirements. For details, refer to the documentation included with the packages.

Additionally, configure to support both BIOS and client architectures. For example:

option arch code 93 unsigned integer 16;  #  ref RFC4578
# ...
subnet 192.168.1.0 netmask 255.255.255.0 {
  if option arch = 00:07 {
    filename "EFI/grubx64.efi";
    # NOTE: substitute the full tftp-boot-dir specified in the setup script
  }
  else {
    filename "pxelinux.0";
  }
# ...
}

Start the , TFTP, and Apache services.
Connect the boot server to the management or boot network.

Copy the ISO image from the source (product DVD, USB device, or WindShare http://windshare.windriver.com) to a temporary location on the PXE boot server.

This example assumes that the copied image file is tmp/TS-host-installer-1.0.iso.

Mount the ISO image and make it executable.

$ mount -o loop /tmp/TS-host-installer-1.0.iso /media/iso
$ mount -o remount,exec,dev /media/iso

Set up the boot configuration.

The ISO image includes a setup script, which you can run to complete the configuration.
```
$ /media/iso/pxeboot_setup.sh -u http://<ip-addr>/<symlink> \
-t <tftp-boot-dir>
```
where

ip-addr

is the Apache listening address.

symlink

is the name of a user-created symbolic link under the Apache document root directory, pointing to the directory specified by <tftp-boot-dir>.

tftp-boot-dir

is the path from which the boot loader is served (the TFTP root directory).

The script creates the directory specified by <tftp-boot-dir>.

For example:
```
$ /media/iso/pxeboot_setup.sh -u http://192.168.100.100/BIOS-client -t /export/pxeboot
```
To serve a specific boot file to a specific controller, assign a special name to the file.

The boot loader searches for a file name that uses a string based on the client interface address. The string uses lower case, substitutes dashes for colons, and includes the prefix "01-".
- For a BIOS client, use the address string as the file name:
```
$ cd <tftp-boot-dir>/pxelinux.cfg/
$ cp pxeboot.cfg <mac-address-string>
```
  where:
  
  <tftp-boot-dir>
  
  is the path from which the boot loader is served.
  
  <mac-address-string>
  
  is a lower-case string formed from the address of the client boot interface, using dashes instead of colons, and prefixed by "01-".
  
  For example, to represent the address 08:00:27:dl:63:c9, use the string 01-08-00-27-d1-63-c9 in the file name.
  
  For example:
```
$ cd /export/pxeboot/pxelinux.cfg/
$ cp pxeboot.cfg 01-08-00-27-d1-63-c9
```
  If the boot loader does not find a file named using this convention, it looks for a file with the name default.
- For a client, use the address string prefixed by "grub.cfg-". To ensure the file is found, copy it to both search directories used by the convention.
```
$ cd <tftp-boot-dir>
$ cp grub.cfg grub.cfg-<mac-address-string>
$ cp grub.cfg ./EFI/grub.cfg-<mac-address-string>
```
  For example:
```
$ cd /export/pxeboot
$ cp grub.cfg grub.cfg-01-08-00-27-d1-63-c9
$ cp grub.cfg ./EFI/grub.cfg-01-08-00-27-d1-63-c9
```
  Note
  
  Alternatively, you can use symlinks in the search directories to ensure the file is found.

7.2 KiB Raw Blame History

Configure a PXE Boot Server

7.2 KiB

Raw Blame History