This document provides an overview of the new and changed features in Cisco Prime Network Registrar 11.1.1, and describes how to access information about the known problems.
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 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 11.1.1, review the system requirements and licensing information available in Cisco Prime Network Registrar 11.1 Installation Guide.
Note |
If you are migrating to Cisco Prime Network Registrar 11.1.1 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 and only the regional server accepts new licenses. Then the regional server can authorize individual local clusters, based on available licenses.
Note |
Licenses for Cisco Prime Network Registrar 10.x or earlier are not valid for Cisco Prime Network Registrar 11.x. You should have a new license for Cisco Prime Network Registrar 11.x. For the 11.x regional, if one has 10.x CDNS clusters, the 10.x CDNS licenses must be added on the regional server (10.x CDNS clusters will use 10.x licenses, 11.x CDNS clusters will use 11.x licenses). |
Warning |
You MUST upgrade the Cisco Prime Network Registrar 10.x local clusters to 10.1.1 or later before upgrading the regional to 11.x. You should not upgrade the local clusters to 11.0 (or later) directly, as you will not be able to register with the regional until it is upgraded to 11.0 (or later). |
Note |
Smart Licensing is enabled by default in Cisco Prime Network Registrar 11.1.1. Cisco Prime Network Registrar 11.x regional, working in Smart License mode, does not support pre-11.0 local clusters. For more details, see the "Using Smart Licensing" section in "Cisco Prime Network Registrar 11.1 Installation Guide". |
For more details about Licensing, see the "License Files" section in Cisco Prime Network Registrar 11.1 Installation Guide.
The Cisco Prime Network Registrar 11.1.1 kit contains the following files and directories:
-
Linux—Cisco Prime Network Registrar RPM application for RHEL/CentOS 7.3 or later, and RHEL 8.x/AlmaLinux 8.6
-
Docs—Pointer card, Bugs, and Enhancement List
-
Container—Container for Docker on Red Hat UBI 8.6
-
Kubernetes—Sample YAML files for deployment of Cisco Prime Network Registrar container on Kubernetes
The Cisco Prime Network Registrar 11.1.1 also ships as a virtual appliance which includes all the functionality available in Cisco Prime Network Registrar along with the AlmaLinux 8.6 operating system. The Cisco Prime Network Registrar virtual appliance is supported on VMware ESXi 7.x platforms, and OpenStack. For more details, see the "Cisco Prime Network Registrar Virtual Appliance" section in Cisco Prime Network Registrar 11.1 Installation Guide.
Note |
The Linux distribution packaged with the optional pre-built VM downloads for Cisco Prime Network Registrar is Open Source software and not owned or supported by Cisco. Customers seeking support for Linux should reach out to third party software providers. |
Licensing
Cisco Prime Network Registrar 11.1.1 supports both Smart Licensing and traditional licensing. However, it does not support the hybrid model, that is, you can use only one of the license types at a time. For a more detailed overview on Cisco Licensing, go to cisco.com/go/licensingguide.
Cisco Prime Network Registrar 11.x is licensed in two parts: Permanent License and SIA License. The SIA License entitles upgrades to future releases. If you are on SIA from Cisco Prime Network Registrar 10.x, or on unexpired SWSS contract from Cisco Prime Network Registrar 9.x, you can upgrade until either of those entitlements expire. For PAK-based licensing, you must install the PAK onto the Cisco Prime Network Registrar regional server. For Smart Licensing, the licenses are delivered to your Smart Account. Smart Licensing is enabled by default in Cisco Prime Network Registrar 11.1.1, but can be overridden after installation. For Cisco Prime Network Registrar 11.1.1, the licensing is done according to the services that you require. For more information, see the "License Files" section in Cisco Prime Network Registrar 11.1 Installation Guide.
Note |
You should not delete any of the individual licenses loaded from the file. If required, you may delete older versions of DNS and DHCP licenses after the upgrade. Older versions of CDNS licenses must be retained if the servers are not upgraded. |
Interoperability
Cisco Prime Network Registrar 11.1.1 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.
If you need additional DNS caching licenses, you should order them based on Server count since DNS caching is a server based license.
To install and manage DHCP, DNS, and Caching DNS licenses, you must deploy a regional server. The regional server, among other things, is used to install, count, and manage licensing for these components.
The synchronization between version 11.1 and pre-11.1 local clusters must be done from a 11.1 regional cluster. Cisco Prime Network Registrar 11.1.1 protocol servers interoperate with versions 9.0 or later.
What's New in Cisco Prime Network Registrar 11.1.1
In 11.x releases prior to 11.1.1, Cisco Prime Network Registrar can only be installed in the default directories - installation files in directory /opt/nwreg2 and data, logs and configuration in directory /var/nwreg2. Although it is very strongly recommended to install in these default paths, changes are made in the installer to also allow installation in non-default directories by using rpm --relocate option.
With this enhancement, the following command can be used for non-default installation:
-
Default installation: rpm -ivh cpnr-local-11.1.1-1.el8.x86_64.rpm
-
Custom install path: rpm -ivh --relocate /opt/nwreg2/local=/home/cpnrLocal cpnr-local-11.1.1-1.el8.x86_64.rpm
-
Custom data path: rpm -ivh --relocate /var/nwreg2/local=/home/cpnrData cpnr-local-11.1.1-1.el8.x86_64.rpm
-
Custom install & data path: rpm -ivh --relocate /opt/nwreg2/local=/home/cpnrLocal --relocate /var/nwreg2/local=/home/cpnrData cpnr-local-11.1.1-1.el8.x86_64.rpm
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 11.1.1 release
Bug ID | Description |
---|---|
CDNS security events are triggered for valid responses when both DNSSEC and DNS64 are enabled |
|
DHCP server restarts during failover sync if limitation-id is configured |
|
DHCP Server may fail to start after server agent restart |
|
User with dhcp-admin role and owner region constraint cannot view scopes |
|
CCM server may deadlock while disabling smart license |
|
Incorrect key-secret being pushed to local clusters for RADIUS server configuration |
|
REST API returns status code 400 for POST request having object name with special character |
|
DNS may leak memory for queries that matches the wildcard |
For the complete list of bugs for this release, see the cpnr_11_1_1_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 feature added in the Cisco Prime Network Registrar 11.1.1 release.
Bug ID |
Description |
---|---|
Support CPNR installation in non-default path |
For the complete list of enhancement features added in this release, see the cpnr_11_1_1_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. |
Related Documentation
See Cisco Prime Network Registrar Documentation Overview for a list of Cisco Prime Network Registrar 11.1.1 guides.
Accessibility Features in Cisco Prime Network Registrar 11.1.1
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.
© 2023 Cisco Systems, Inc. All rights reserved.