How are you doing DHCPv6 ?
bjorn at mork.no
Sat Jan 21 07:03:32 CST 2012
Randy Carpenter <rcarpen at network1.net> writes:
> DHCP is certainly not stateless, which is why there is a concept of
> leases, which are stored in a file. You can't have 2 servers answering
> for the same subnet without some sort of coordination, or you would
> have a potential for duplicate addresses being assigned.
Duplicate assignments are not a problem as long as you ensure that the
client is the same.
I.e. if the prefix delegating DHCPv6 server serves a statically assigned
prefix to an end user based on information *uniquely identifying that
user*, then you can replicate that setup to as many completely
independent DHCPv6 servers as you like. Different end users will still
not receive duplicate assignments.
But if you want the DHCPv6 server to dynamically allocate a new prefix
to each client, then you are up for problems of course. Don't see why
you would want to do that though. Redundant DHCPv6 will be only one of
many problems in such a setup.
More information about the NANOG