Cisco Cisco Network Registrar 7.1 릴리즈 노트
15
Release Notes for Cisco Network Registrar 7.1.1
OL-21835-01
Limitations and Restrictions
DHCP Option Definitions List Enhancements
The DHCP option definitions list has been updated to support the following RFCs, which does not
require any modification to the DHCP server behavior,
require any modification to the DHCP server behavior,
•
RFC5192 is the PANA option, which was not an RFC on CNR 7.0 release
•
RFC5223 is the LOST server option
•
Cisco Vendor Specific Option definitions is included in the dhcp-cisco-config and
dhcp6-cisco-config option definitions sets
dhcp6-cisco-config option definitions sets
For more details about the new software features added, please see the User Guide for Cisco Network
Registrar.
Registrar.
Limitations and Restrictions
This section describes limitations and restrictions you might encounter when using CNR 7.1.1.
•
The Regional Pull Replica Address Space fails when reservations are being pulled for new
failover-pair objects. This problem occurs only if there is a new failover-pair and one or more
reservations associated with that failover-pair. To workaround this issue, repeat the operation
twice—first checking Omit Reservations and then without checking Omit Reservations. After the
failover-pairs have been pulled, subsequent pull replica address space operations will work
correctly.
failover-pair objects. This problem occurs only if there is a new failover-pair and one or more
reservations associated with that failover-pair. To workaround this issue, repeat the operation
twice—first checking Omit Reservations and then without checking Omit Reservations. After the
failover-pairs have been pulled, subsequent pull replica address space operations will work
correctly.
•
In situations where a DHCPv6 server supports clients with multiple leases, the demand on server
memory increases. DHCPv4 supports only one lease per client, while DHCPv6 supports multiple
leases. Therefore, a DHCPv6 server cannot support as many leases (clients) as can the same server
running DHCPv4. For example, one DHCPv6 client might require 2,500 bytes of space compared
to 1,000 bytes per DHCPv4 client. This means that a machine that would support one million
DHCPv4 clients supports only 400,000 DHCPv6 clients. We recommend that you allow three times
the memory for DHCPv6 clients as you would for DHCPv4.
memory increases. DHCPv4 supports only one lease per client, while DHCPv6 supports multiple
leases. Therefore, a DHCPv6 server cannot support as many leases (clients) as can the same server
running DHCPv4. For example, one DHCPv6 client might require 2,500 bytes of space compared
to 1,000 bytes per DHCPv4 client. This means that a machine that would support one million
DHCPv4 clients supports only 400,000 DHCPv6 clients. We recommend that you allow three times
the memory for DHCPv6 clients as you would for DHCPv4.
You must:
–
Be aware of how many prefixes per link are configured. If the configuration has two prefixes on
a link, then with default configuration parameters, you have to cut in half the number of clients.
a link, then with default configuration parameters, you have to cut in half the number of clients.
–
Use care if you enable inhibit-all-renews. When enabled, each client would use at least two
leases, and perhaps three, depending on the grace and affinity times per prefix.
leases, and perhaps three, depending on the grace and affinity times per prefix.
Caveats
You can find the complete list of resolved and known bugs in the cnr_7_1_1-buglist.pdf file included
with the release. Refer to this list especially for information about fixes to customer-reported issues.
with the release. Refer to this list especially for information about fixes to customer-reported issues.