Technical References
Sets the maximum number of leases, regardless of state or whether
reserved or not, that the server can associate with a DHCPv6
client. A DHCPv6 lease is always associated with a client; if it
is not, it is deleted.
This setting is to prevent a client from using lots of leases
(such as by issuing many requests with different IAID values). It
is not intended to limit the number of active leases a client may
have.
While 1 can be configured as the minimum for backwards
compatibility, the server uses a minium of 2 to allow for a
client that usually only has a single lease to be renumbered or
moved to a different prefix on the link.
This limit is not applied when existing leases are loaded from
the lease state database during server start-up.
max-dhcp-requests int default = 500, required
Controls the number of buffers that the DHCP server allocates
for receiving client requests.
When you enable failover, allocate at least 150 buffers. Up to
1500 buffers might be reasonable for high capacity
installations.
Caution: Increasing the number of buffers can degrade
performance. Cisco recommends using the default value
in most situations. When buffer size exceeds capacity, a burst
of DHCP activity can clog the server with requests that become
stale before they are processed. This increases the processing
load and might severely degrade performance as clients try to
obtain a new lease. A lower buffer setting throttles requests
and avoids wasted processing on requests that would otherwise be
stale.
When using LDAP client lookups, buffers should not exceed the
LDAP lookup queue size defined by the total number of LDAP
connections and the maximum number of requests allowed for each
connection. Set the LDAP queue size to match the LDAP server?s
capacity to service client lookups.
max-dhcp-responses int default = 1000, required
Controls the number of buffers that the DHCP server allocates
for responses to client requests. The server ignores this
value if max-dhcp-requests is higher, or other configuration
options such as failover require that the value be set higher
than configured.
max-dns-renaming-retries int default = 3, required
Controls the number of times that the DHCP server can attempt
adding a host into DNS, even if the DHCP server detects that the
hostname is already present in DNS. The DHCP server attempts
to modify the hostname in order to resolve a conflict on each
failed update.
max-dns-retries int default = 3, required
Controls the number of times that the DHCP server can try to
send dynamic updates to a DNS server.
max-dns-ttl int default = 86400, required