These release notes provide an overview of the new and changed features in Cisco Prime Network Registrar 8.3.7 and describe how to access information about the known problems in Cisco Prime Network Registrar 8.3.7.
Note |
You can access the most current Cisco Prime Network Registrar documentation, including these release notes, online at: |
This document contains the following sections:
Introduction
Cisco Prime Network Registrar is comprised of these components:
-
An Authoritative Domain Name System (DNS) protocol service
-
A Caching DNS (CDNS) service
-
A Dynamic Host Configuration Protocol (DHCP) service
Cisco offers these components as individually licensed applications or in a mix of suites.
Before you Begin
Before you install Cisco Prime Network Registrar 8.3.7, review the system requirements and licensing information available in the Cisco Prime Network Registrar 8.3.7 Installation Guide.
Note |
If you are migrating to Cisco Prime Network Registrar 8.3.7 from an earlier version of Cisco Prime Network Registrar, you must review the release notes for the releases that occurred in between, to fully understand all the changes. |
Cisco Prime Network Registrar DHCP, Authoritative DNS, and Caching DNS components are licensed and managed from the Cisco Prime Network Registrar regional server. All services in the local clusters are licensed through the regional cluster. Only a regional install requires a license file and only the regional server accepts new license files. Then the regional server can authorize individual local clusters, based on available licenses.
Note |
Licenses of Cisco Network Registrar 7.x or earlier are not valid for Cisco Prime Network Registrar 8.x. |
For more details about Licensing, see the "License Files" section of the Cisco Prime Network Registrar 8.3.7 Installation Guide.
The Cisco Prime Network Registrar 8.3.7 kit contains the following files and directories:
-
Solaris—Solaris 10 installation kit
Note
The last date of support on Solaris for all 8.x PNR releases (that is, 8.1, 8.2, and 8.3) was July 2017. However, Solaris is supported in Cisco Prime Network Registrar 8.3.7 to meet the customer requirements.
-
Linux—CentOS 6.5/Red Hat Linux ES 6.5 and later installation kit
Note
Cisco Prime Network Registrar 8.3.7 supports 64-bit Linux installations only.
-
Windows—Windows Server 2008 R2 installation kit.
-
Docs—Pointer card, Bugs, and Enhancement List
The Cisco Prime Network Registrar also ships as a virtual appliance which includes all the functionality available in Cisco Prime Network Registrar along with the CentOS 7.6 operating system. The Cisco Prime Network Registrar virtual appliance is supported on VMware ESXi 5.5 or later platforms, and CentOS/RHEL 7.6 KVM Hypervisor. For more details, see the "Cisco Prime Network Registrar Virtual Appliance" section of the Cisco Prime Network Registrar 8.3.7 Installation Guide.
Market Segment Specific Licensing
Cisco Prime Network Registrar introduced separate licenses for the components (System, DHCP, DNS, and CDNS) in release 8.0. For information on the Cisco Prime Network Registrar component-based license set, see the "License Files" section of the Cisco Prime Network Registrar 8.3.7 Installation Guide.
Cisco Prime Network Registrar license types are offered specific to market segments. Market-specific licensing generates license keys for use by market segments, that is, Service Provider, Smart Grid, and others. Cisco Prime Network Registrar features are enabled based on the market segment specific license you choose.
Cisco Prime Network Registrar currently offers the following sets of market segment based licenses:
-
PNR
-
PNR-SG
Note |
If the licenses for both market segments are installed, then only the PNR license will be active. |
The PNR license offers features designed for the Enterprise and Service Provider market segment, whereas the PNR-SG license offers features designed for the Smart Grid market segment.
The regional server which uses the PNR-SG license can be converted to PNR by installing the PNR license. Local cluster licenses will be converted automatically at the next compliance check, or can be manually updated by resynchronizing the local cluster.
For a given market segment license, only the counts from corresponding market segment license will apply.
For example, if the PNR count license is applied when the PNR-SG base license is active, the Right to Use count will not be updated. If the PNR-SG count license is applied when the PNR base license is active, the Right to Use count will not be updated.
Cisco Prime Network Registrar 8.3.7 requires 8.x licenses for DHCP and DNS authoritative services. These licenses are applied system-wide and support both 8.3.7 local clusters and existing 8.x local clusters. Cisco Prime Network Registrar 8.3.7 supports earlier versions of the DNS caching license for existing 8.x local clusters. 8.3.7 local clusters require 8.x licenses. If you are using the Cisco Prime Network Registrar 8.x platform, you can purchase upgrade licenses. Versions released prior to Cisco Prime Network Registrar 8.x are not eligible for upgrade licensing and are directed to the Cisco Prime Network Registrar 8.x full license.
PNR Licenses
The PNR license provides all the features available for the Cisco Prime Network Registrar release you install.
PNR-SG Licenses
The PNR-SG license offers all the PNR features with the exception of (identified as not necessary for Smart Grid Implementations):
-
Tenants
-
External Authentication (RADIUS and Active Directory (AD))
-
DHCP Extensions
-
Lightweight Directory Access Protocol (LDAP)
-
TCP Listeners (lease notification)
-
Trivial File Transfer Protocol (TFTP)
-
Router Interface Configuration (RIC)
-
Regional lease history
-
Regional subnet utilization history
-
Bring Your Own Device (BYOD)
Note |
Before you install Cisco Prime Network Registrar 8.3.7, review the system requirements and licensing in the Cisco Prime Network Registrar 8.3.7 Installation Guide. |
Interoperability
Cisco Prime Network Registrar 8.3 uses individual component licenses. This allows users to purchase and install DHCP services, Authoritative DNS services, and Caching DNS services individually, or as a suite.
Customers ordering the DD bundle would obtain a quantity one of the Caching DNS when they acquire the DNS authoritative license. If they need additional DNS caching licenses they are ordered based on Server count since DNS caching is a server based license.
To install and manage DHCP, DNS, and Caching DNS licenses, you must establish a regional server. The regional server is used to install, count, and manage licensing for these components.
The synchronization between version 8.3 and pre-8.3 local clusters must be done from a 8.3 regional cluster. Cisco Prime Network Registrar 8.3 protocol servers interoperate with versions 7.2 or later except as noted below.
-
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.
-
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 Bugs
For more information on a specific bug or to search all bugs in a particular Cisco Prime Network Registrar release, see Using the Bug Search Tool.
This section contains the following information:
Resolved Bugs
The following table lists the key issues resolved in the Cisco Prime Network Registrar 8.3.7 release.
Bug ID |
Description |
---|---|
CPNR will not install on CentOS 7.2 because not finding libsasl |
|
Calculation of total average response time overflows when number of queries gets large |
|
CSCvm91901 |
Use of utilization history can cause DHCP server to crash |
CSCvn03816 | Use of release-grace-period can cause issues with DHCPv4 |
DNS does not automatically remove sub zone delegations after a full zone transfer |
|
CSCvn49047 | CPNR installation/upgrade fails with krb5-libs-1.15.1-34.el7.x86_64 rpm version |
CSCvo02059 | Backup failover partner can run low or out of Prefix Delegation Leases |
DNS does not include OPT RR in TCP responses to DNS queries |
For the complete list of bugs for this release, see the cpnr_ipx_8_3_7_buglist.pdf file available at the product download site. See this list especially for information about fixes to customer-reported issues.
Enhancement Features
The following table lists the key enhancement features added in the Cisco Prime Network Registrar 8.3.7 release.
Bug ID |
Description |
---|---|
CSCvo39720 | Include CentOS 7.6.1810 as the base OS for virtual appliance |
For the complete list of enhancement features added in this release, see the cpnr_ipx_8_3_7_enhancements.pdf file available at the product download site.
Using the Bug Search Tool
Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.
Procedure
Step 1 | |||
Step 2 |
At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Search page opens.
|
||
Step 3 |
To search for a specific bug, enter the bug ID in the Search For field and press Return. |
||
Step 4 |
To search for bugs in the current release, click the Search Bugs tab and specify the following criteria:
|
Note |
To export the results to a spreadsheet, click the Export All to Spreadsheet link. |
Important Notes
Start/stop CPNR on CentOS/RHEL 7.x
When CPNR is installed on CentOS/RHEL 7.x, you must use systemctl commands to start and stop CPNR. The scripts /etc/init.d/nwreglocal or /etc/init.d/nwegregion no longer exist when CPNR is installed on RHEL/CentOS 7.x.
-
To start Cisco Prime Network Registrar regional cluster:
-
Solaris and RHEL/CentOS 6.x:
# /etc/init.d/nwregregion start
-
RHEL/CentOS 7.x:
# systemctl start nwregregion
-
-
To stop Cisco Prime Network Registrar regional cluster:
-
Solaris and RHEL/CentOS 6.x:
# /etc/init.d/nwregregion stop
-
RHEL/CentOS 7.x:
# systemctl stop nwregregion
-
-
To start Cisco Prime Network Registrar local cluster:
-
Solaris and RHEL/CentOS 6.x:
# /etc/init.d/nwreglocal start
-
RHEL/CentOS 7.x:
# systemctl start nwreglocal
-
-
To stop Cisco Prime Network Registrar local cluster:
-
Solaris and RHEL/CentOS 6.x:
# /etc/init.d/nwreglocal stop
-
RHEL/CentOS 7.x:
# systemctl stop nwreglocal
-
Related Documentation
See Cisco Prime Network Registrar Documentation Overview for a list of Cisco Prime Network Registrar 8.3 guides.
Accessibility Features in Cisco Prime Network Registrar 8.3.7
All product documents are accessible except for images, graphics, and some charts. If you would like to receive the product documentation in audio format, braille, or large print, contact accessibility@cisco.com.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation.
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's New in Cisco Product Documentation RSS feed. RSS feeds are a free service.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2019 Cisco Systems, Inc. All rights reserved.