J
Jerry
Perhaps one DHCP server is always responding faster than
the other, thus it is leasing first?
Try narrowing the scope of available IPs it can give out
to force clients to go to the 2nd DHCP server. Instead of
making 50 addresses available on DHCP1, for example, try
making only 2 or 3 available on DHCP1 and having 5 or more
clients try to obtain an address.
What happens if you shut down the DHCP server responding
to all the client requests for a lease? Does the 2nd
server kick in as it should? If that's the case, looks
like load balancing might not be what you're getting, but
you're sure protected in the event of the 1st server
failing (i.e. redundancy).
Jerry
the other, thus it is leasing first?
Try narrowing the scope of available IPs it can give out
to force clients to go to the 2nd DHCP server. Instead of
making 50 addresses available on DHCP1, for example, try
making only 2 or 3 available on DHCP1 and having 5 or more
clients try to obtain an address.
What happens if you shut down the DHCP server responding
to all the client requests for a lease? Does the 2nd
server kick in as it should? If that's the case, looks
like load balancing might not be what you're getting, but
you're sure protected in the event of the 1st server
failing (i.e. redundancy).
Jerry