Univention Bugzilla – Bug 47590
Univention recommendation on how to use DHCP with UEFI clients
Last modified: 2018-10-08 09:47:47 CEST
opsi on UCS makes have use of the DHCP server. In customer environments clients with UEFI and non-UEFI are used and they are configured to get their boot image via PXE and netboot from the DHCP server. The administrator just creates a client object in UCS and the DHCP server takes care of everything. There is no need for an attribute on UEFI or non-UEFI of the client. UEFI and non-UEFI PXE requests are different and the DHCP server is capable of recognizing them and answer appropriately. This requires an appropriate configuration in UCS. A SDB article should describe this configuration. One method I heard of, was to configure a DHCP policy that basically implements a switch and answers with the right method depending on the PXE request type.
A documentation of the recommended way on how to do it would make life easier in projects where opsi and UCS are involved. uib could simply refer to the recommendation.
Does uib not ship their own DHCP server package with opsi, or has that changed? A feature request for UCS is at Bug 43728
(In reply to Erik Damrose from comment #2) > Does uib not ship their own DHCP server package with opsi, or has that > changed? > > A feature request for UCS is at Bug 43728 They ship their own tftpd, but use the UCS DHCP server.
The setup has already been described in the following forum posting: https://help.univention.com/t/ucs-school-mit-opsi-uefi-pxe-im-ldap-korrekt-eingerichtet/9221 It would be great to destille the content to an SDB article.
I created a howto in our forum ready for QA. https://help.univention.com/t/how-to-configure-a-dhcp-switch-for-uefi-and-non-uefi-boot/9931
Article looks good. Can confirm that the DHCP statement is working like a charm at a current customer installation.
Article has been released under Knowledge Base - Community: https://help.univention.com/t/how-to-configure-a-dhcp-switch-for-uefi-and-non-uefi-boot/9931