How to use PXE provisioning with multiple subnets in Red Hat Satellite 6?

Environment

• Red Hat Satellite 6.x

Issue

• When trying to create a host using hammer below error is seen:

    Could not create the host: Create DHCP Settings for         
    client.example.com task failed with the following error: ERF12-6899         
    [ProxyAPI:ProxyException]: Unable to set DHCP entry         
    ([RestClient::Conflict]: 409 Conflict) for Capsule
  

Resolution

• In DHCP configuration, mention DHCP server to boot clients using the boot files that Satellite offers. This is done by setting DHCP's next-server & filename options.

• Edit /etc/dhcp/dhcpd.conf file and add subnet details as below:

    {
      subnet 192.168.0.0 netmask 255.255.255.0 {
      range 192.168.0.100 192.168.5.150;
      option domain-name-servers 8.8.8.8:
      option bootfile-name "pxelinux.0";
      option domain-name "yourcompany.com";
      default-lease-time 1800;
      max-lease-time 7200;
      next-server "satellite.example.com";
    }
  

• As satellite-installer only sets up one subnet for DHCP. To run multiple subnets using DHCP, re-run the installer with the foreman-proxy-dhcp-managed option set to FALSE. This tells puppet-based installer that DHCP file is being managed manually. Lastly, configure DHCP as per your needs.

• This issue has been discussed in the Red Hat forum as well, For further information, refer below This content is not included.Satellite 6.2 provisioning on different subnets/vlans

For more KB articles/solutions related to Red Hat Satellite 6.x Provisioning Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Provisioning related Issues

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.