h1. ERF12-6899 - Unable to set DHCP entry

h2. Generic or SSL connection errors

Please see [[Proxy_communication_errors]] first for SSL or communication errors, which aren't specific to this particular proxy action.

h2. Foreman 1.5.1: Removing a Proxy::DHCP Record which doesn't exist

Seen on Foreman 1.5.1, this is bug #6412.

<pre>

E, [2014-06-20T15:14:54.521280 #1384] ERROR -- : Removing a Proxy::DHCP Record which doesn't exist

D, [2014-06-20T15:14:54.521353 #1384] DEBUG -- : /usr/share/foreman-proxy/bin/../lib/proxy/dhcp/subnet.rb:184:in `delete'

/usr/share/foreman-proxy/bin/../lib/proxy/dhcp/server/isc.rb:64:in `loadSubnetData'

</pre>

Note that stack trace contains @loadSubnetData@ on line 64.

Workaround: @service dhcpd restart@

h2. [RestClient::RequestTimeout]: Request Timeout

If the DHCP reservation isn't added, see [[Proxy_communication_errors]].

If it is added, the proxy is taking too long to add it, so Foreman is timing out.  If you have many subnets configured but only need to manage a few, try setting dhcp_subnets in the proxy configuration to restrict those it loads (available from Foreman 1.5.1):

<pre>

:dhcp_subnets: [192.168.205.0/255.255.255.128, 192.168.205.128/255.255.255.128]

</pre>

Issue #5847 tracks this problem.

h2. Using AD DHCP and Windows 2008

Seen on Windows 2008 R2.  In proxy.log, it logs:

<pre>

I, [2014-05-30T09:06:23.096367 #2620]  INFO -- : Vendor class not found

E, [2014-05-30T09:06:23.096367 #2620] ERROR -- : Netsh failed:

Changed the current scope context to 172.28.4.0 scope.

The specified option does not exist.

</pre>

This is bug #13575, which has been fixed in version 1.12.1.  On older versions, to workaround it, remove the option 60 added here: https://github.com/theforeman/smart-proxy/commit/296617a