-
Title
Setting up non Microsoft DHCP server (Cisco, Solaris, and others) -
Description
If you are not using Microsoft DHCP, the process of getting the KACE SDA appliance and DHCP to work together is not as easy as setting two scope options. This information should assist you in getting the issue resolved. This has been used on Solaris and other non MS DHCP systems with success. -
Resolution
Starting in version 4.0, the KACE Systems Deployment Appliance (K2000) has the ability to leverage iPXE boot options for both UEFI and Legacy BIOS target devices.
For UEFI PXE booting, you must configure the boot file as ipxe.efi
For Legacy/BIOS PXE booting, you must configure the boot file as undionly.kpxe
For Legacy/BIOS PXE booting with PXELINUX (Versions prior to 6.0), you must configure the boot file as k2000.0
Below are several examples, each leveraging a different boot file. You may only use PXELINUX and the boot file k2000.0 in version 5.1 and prior.
On the KACE SDA appliance, we set the "next server" and "boot filename" values in the "sname" and "file" fields in the DHCP header. Our instructions for Microsoft's DHCP server set these values in the options section of the DHCP message. It's possible to try both to see if it is easier to configure Solaris to do one or the other.
KACE recommends using the IP address for the TFTP server name instead of a host name.
Here is what the end result should look like for Solaris. Key values are in red, and this example is leveraging the Legacy/BIOS boot file:
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.1;
next-server 192.168.1.23;
filename "undionly.kpxe";
pool {
failover peer "mypeer";
deny unknown clients;
deny dynamic bootp clients;
range 192.168.1.71 192.168.1.254;
}
}Here's an example of what a Cisco environment might use for their DHCP pool options while leveraging the Legacy/BIOS boot file:
ip dhcp pool name
network ip subnet
bootfile undionly.kpxe
next-server ip.of.the.KACESDAorRSA
default-router gateway
dns-server dns1 dns2 dn3
lease 0 4
A different Cisco environment might use the below configuration instead of using bootfile while leveraging the UEFI boot file:ip dhcp pool name
network ip subnet
next-server ip.of.the.KACESDAorRSA
option 66 ascii ip.of.the.KACESDAorRSA
option 244 ascii ip.of.the.KACESDAorRSA
option 67 ascii ipxe.efi
default-router gateway
dns-server dns1 dns2 dn3
lease 0 4
Note: Make sure to use 'ascii' options not 'IP' options.
-
Additional Information
Dynamic Host Configuration Protocol Document, from the Internet Engineering Task Force:
http://www.ietf.org/rfc/rfc2131.txt
NOTE: Search for "Table 1: Description of fields in a DHCP message"
Linux DHCP Configuration via dhcpd on Linux Centos 5.5:pfSense dhcpd configuration for UEFI and BIOS PXE Boot: