Redundant DHCP Reservations

Hi, I'd like to set up a redundant DHCP server using
superscopes and exclusion ranges.

My question is, for the reservations I have set up, is it
ok to duplicate each of the reservations on both servers,
so if one goes down the servers can still receive IP
addresses?

Or will that create problems so instead I should create
the reservations but put them in an exclusion range to
they don't mess up the clients?

It appears that the Windows 2000 Resource Kit recommends
the second option, but that doesn't really meet my
redundancy needs. Any suggestions?

Thanks for the help.

Hi
I believe you may have mis read the resource kit. If you include the
reservations in your exclusions, the addresses will not be released to the
clients. Any IP addresses listed in the Exclusions are ignored whether
you have a reservation or not. What the resource kit is saying is for
your Servers, you should give the STATIC IP addresses and the exclude the
range of static addresses out of your DHCP scope.

There is another problem. If you include the reservations on both servers,
then there is the possibility of both servers getting a NACK and the hence
the server is left with NO ipaddress at all. Also, if that didn't happen,
one DHCP server would mark the address as BAD_ADDRESS for the lease
duration, during that time if the other DHCP server is down, and the server
reservation client was rebooted, the server is still not going to get an
address.

If the systems are that important and must maintain the same IPaddress, I
would strongley suggest statically configuring the Servers.

Thank you,

Alan Wood[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.

AlanWood@NoSpam ("Alan Wood" [MSFT]) wrote in message news:<Lps$(E-Mail Removed)>...
> Hi
> I believe you may have mis read the resource kit. If you include the
> reservations in your exclusions, the addresses will not be released to the
> clients. Any IP addresses listed in the Exclusions are ignored whether
> you have a reservation or not. What the resource kit is saying is for
> your Servers, you should give the STATIC IP addresses and the exclude the
> range of static addresses out of your DHCP scope.
>
> There is another problem. If you include the reservations on both servers,
> then there is the possibility of both servers getting a NACK and the hence
> the server is left with NO ipaddress at all. Also, if that didn't happen,
> one DHCP server would mark the address as BAD_ADDRESS for the lease
> duration, during that time if the other DHCP server is down, and the server
> reservation client was rebooted, the server is still not going to get an
> address.
>
> If the systems are that important and must maintain the same IPaddress, I
> would strongley suggest statically configuring the Servers.
>
> Thank you,
>
> Alan Wood[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights.

It depends on the OS, Windows NT handles this differently from W2k.
Excluded IP addresses can be active on your network, but only when
these addresses are manually configured or distributed as reserved IP
addresses.
http://www.microsoft.com/technet/tre...c_dhc_asrc.asp