Примечания к выпуску для Cisco Cisco Prime Network Registrar 8.3

Скачать
Страница из 6
4
Cisco Prime Network Registrar 8.3.1 Release Notes
 
Cisco Prime Network Registrar Bugs
Cisco Prime Network Registrar 8.2 and later DHCPv4 failover servers do not interoperate with versions prior to 8.2. 
Therefore, if you are upgrading from 8.1 and earlier to 8.2 and later, you must upgrade both failover partners. Also, 
any firewalls need to be updated to allow TCP traffic on the failover port (547). And, for 8.2 and later failover extends 
to DHCPv6.
The HA protocol version has been updated in Cisco Prime Network Registrar 8.0 and communications with earlier 
versions is not supported.
Caution:
By the nature of the EDNS0 protocol, Cisco Prime Network Registrar 8.3 DNS servers interoperate with earlier 
versions of Cisco Prime Network Registrar DNS (and third party DNS vendors). EDNS0 defines the interoperability 
with DNS servers that do not support EDNS0. Cisco Prime Network Registrar 8.3 DNS adheres to the RFC and 
consequently interoperates with earlier versions of Cisco Prime Network Registrar.
Cisco Prime Network Registrar 8.3 DDNSv6 interoperates with Cisco Network Registrar 7.0 and later DNS servers 
because of the use of the DHCID RRs (in place of TXT RRs for DDNSv6).
Cisco Prime Network Registrar 8.3 does not interoperate with Cisco Prime Network Registrar IPAM 8.1.1 or 8.1.2. 
An updated version of Cisco Prime Network Registrar IPAM is required to interoperate with Cisco Prime Network 
Registrar 8.3.
Cisco Prime Network Registrar Bugs
For more information on a specific bug or to search all bugs in a particular Cisco Prime Network Registrar release, see 
.
This section contains the following information:
Resolved Bugs
 lists the key issues resolved in the Cisco Prime Network Registrar 8.3.1 release.
Table 1
Resolved Bugs in Cisco Prime Network Registrar 8.3.1
Bug ID
Description
Need to document special characters to be used in REST requests
Forward zones ending in arpa may experience errors
CDNS ignores configured forwarders in hybrid-mode
License parameters are not applied in silent install
DHCPv6 option 75 (krb-principal-name) was incorrectly defined
DNS upgrade considerations should be documented
Authoritative DNS upgrades of large DBs is very slow
Zone host sync is limited to 1000 rrsets
Regional replica update fails to get changes
force-dns-update attribute has no effect when enabled
TXT records of forward zones in ha pair are not deleted on lease expiry