Difference between revisions of "Pxe"

From SME Server
Jump to navigationJump to search
(→‎Description: Reference to boot architecture types)
Line 50: Line 50:
 
    }
 
    }
  
</syntaxhighlight>Additional boot architectures can be supported by adding them to pxe as <arch> <executable> e.g. <syntaxhighlight lang="bash">
+
</syntaxhighlight>Additional boot architectures (as per https://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xhtml#processor-architecture) can be supported by adding them to pxe as <arch> <executable> e.g. <syntaxhighlight lang="bash">
 
config set-prop pxe 00:09 syslinux.efi
 
config set-prop pxe 00:09 syslinux.efi
 
</syntaxhighlight>
 
</syntaxhighlight>
Line 103: Line 103:
 
|<boot executable>
 
|<boot executable>
 
|boot architecture and associated boot executable
 
|boot architecture and associated boot executable
e.g. 00:09 syslinux.EFI
+
e.g. 00:09 syslinux.efi
 
|optional
 
|optional
 
|}
 
|}

Revision as of 05:39, 2 May 2022




pxe
NeedImage.svg
pxe logo
MaintainerTrevorB
Urlhttps://wiki.koozali.org
Category

Administration

Tags networkpxe boottftpthinclient


Maintainer

User:TrevorB

Version

Contrib 10:
smeserver-pxe
The latest version of smeserver-pxe is available in the SME repository, click on the version number(s) for more information.


Description

Global settings for dhcp to allow clients to network boot. Assumes sme server is acting as dhcp server.

This contrib supplies the basic parameters to dhcpd to allow pxe booting on your network.

It is ONLY config db parameters and /etc/dhcpd.conf template fragments. No panels or scripts.

Just restart dhcpd to get updated parameters added into /etc/dhcpd.conf

service dhcpd restart

This will update your /etc/dhcpd.conf file to include

option client-architecture code 93 = unsigned integer 16;

<and within the subnet scope>

    if option client-architecture = 00:07 {
        filename "/bootx64.efi";
    }
    elsif option client-architecture = 00:06 {
        filename "/bootia32.efi";
    }
    else {
        filename "/pxelinux.0";
    }

Additional boot architectures (as per https://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xhtml#processor-architecture) can be supported by adding them to pxe as <arch> <executable> e.g.

config set-prop pxe 00:09 syslinux.efi

Installation

yum --enablerepo=smecontribs install smeserver-pxe

Configuration

you can list the available configuration with the following command :

config show pxe

Some of the properties are not shown, but are defaulted in a template or a script. Here a more comprehensive list with default and expected values :

property default values
status enabled enabled, disabled
default pxelinux.0 any name of executable
00:06 bootia32.efi pxe boot executable for this boot architecture (32 bit EFI)
00:07 bootx64.efi pxe boot executable for this boot architecture (64 bit EFI)
dir <directory> subdirectory of /tftpboot in which to find executable

e.g. EFI

optional
nextserver <IP address> IP address of tftp server in your network optional
<arch> <boot executable> boot architecture and associated boot executable

e.g. 00:09 syslinux.efi

optional

Uninstall

yum remove smeserver-pxe

Bugs

Please raise bugs under the SME-Contribs section in bugzilla

and select the smeserver-pxe component or use this link


Below is an overview of the current issues for this contrib:

No open bugs found.

Changelog

Only released version in smecontrib are listed here.

smeserver-pxe Changelog: SME 10 (smecontribs)
2022/07/02 Trevor Batley 0.1-4.sme
- add event smeserver-pxe-update to trigger dhcpd restart via creatlinks [12087]
2022/05/28 Trevor Batley 0.1-3.sme
- Remove incorrect = sign from nextserver parameter and enclsing "'s
2022/05/09 Trevor Batley 0.1-2.sme
- Set default architecture executables to Centos 7 defaults [SME 11969]

2022/04/28 Trevor Batley 0.1-1.sme
- Initial release [SME 10821]
- Split of PXE Global parameters out of smeserver-thinclient

- Allow for different architectures (including UEFI booting)