Contents

This document contain the following sections:

■Introduction

■Before you Begin

■Market Segment Specific Licensing

■Interoperability

■Cisco Prime Network Registrar Bugs

■Important Notes

■Related Documentation

■Accessibility Features in Cisco Prime Network Registrar 8.3.3

■Obtaining Documentation and Submitting a Service Request

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.

In addition, for IP address management, you can deploy Cisco Prime Network Registrar IPAM, or you can integrate it with the DHCP and DNS components of Cisco Prime Network Registrar.

Before you Begin

Before you install Cisco Prime Network Registrar 8.3.3, review the system requirements and licensing information available in the Cisco Prime Network Registrar 8.3.2 Installation Guide.

Note: If you are migrating to Cisco Prime Network Registrar 8.3.3 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 for Cisco Network Registrar 7.x or earlier are not valid for Cisco Prime Network Registrar 8.x.

Cisco Prime Network Registrar IPAM is licensed separately from Cisco Prime Network Registrar DHCP, DNS, and Caching DNS. When installing IPAM, you will be asked to install as a separate process using a separate license key. To receive the IPAM license, you must purchase Cisco Prime Network Registrar IPAM, either individually, or as part of a Cisco Prime Network Registrar suite.

For more details about Licensing, see the License Files section in the Overview chapter of the Cisco Prime Network Registrar 8.3.2 Installation Guide.

The Cisco Prime Network Registrar 8.3.3 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) will be July 2017.

■Linux—Red Hat Linux ES 5.x /6.x installation kit.

Note: Cisco Prime Network Registrar 8.3.3 supports two Linux kits—32-bit applications and 64-bit applications.

■Windows—Windows Server 2008 R2 installation kit.

■Docs—Pointer card, Bugs, Enhancement List.

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.2 Installation Guide.

Since release 8.1.2, 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 two 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.

Interoperability

Cisco Prime Network Registrar 8.3 uses individual component licenses. This allows users to purchase and install DHCP services, Authoritative DNS and Caching DNS services, and IPAM services individually, or as a suite.

When you purchase the full set of Cisco Prime Network Registrar components, you receive a license package for IPAM, and a separate license for Cisco Prime Network Registrar DHCP and DNS components (Authoritative and Caching DNS).

Customers ordering the DDI 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 Cisco Prime Network Registrar IPAM license is installed separately and does not use the regional server.

The synchronization between version 8.3 and pre-8.3 local clusters must be done from an 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.

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 Using the Bug Search Tool.

This section contains the following information:

■Resolved Bugs

■Enhancement Features

■Using the Bug Search Tool

Important Notes

This section contains the important information related to this software release and information in response to recent customer queries. It describes:

■RFC 3597 Standard for Unknown RR Types and Classes

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.3

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, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.

This document is to be used in conjunction with the documents listed in the Related Documentation section.

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: 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. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2016 Cisco Systems, Inc. All rights reserved.