Cisco Prime Network Registrar 8.1.2 Release Notes

Table Of Contents

Cisco Prime Network Registrar 8.1.2 Release Notes

Contents

Introduction

Before you Begin

Interoperability

Software Features Added in Release 8.1.2

Market Segment Specific Licensing

PNR Licenses

PNR-SG Licenses

Issues Resolved and Enhancements Added in Release 8.1.2

Issues Resolved in Release 8.1.2

Enhancement Features Added in Release 8.1.2

Limitations and Restrictions

Important Notes

Moving a Regional Cluster to a New Machine

New DHCP Policy Attributes

Troubleshooting Local Cluster Licensing Issues

Product Documentation

Obtaining Documentation and Submitting a Service Request

Cisco Prime Network Registrar 8.1.2 Release Notes

---

Revised: January 2013, OL-28487-01

Cisco Prime Network Registrar is comprised of four components including an IP address management application, a Domain Name System (DNS) protocol service, a Caching DNS service, and a Dynamic Host Configuration Protocol (DHCP) service.

Cisco offers these components as individually licensable applications or in a mix of suites.

These release notes describe the new software features, software and standards compatibility, interoperability and important notes for Cisco Prime Network Registrar 8.1.2.

Contents

These release notes includes the following sections:

•Introduction

•Before you Begin

•Interoperability

•Software Features Added in Release 8.1.2

•Issues Resolved and Enhancements Added in Release 8.1.2

•Limitations and Restrictions

•Important Notes

•Product Documentation

•Obtaining Documentation and Submitting a Service Request

Introduction

Cisco Prime Network Registrar is one of the Prime suite of network solution products. The Cisco Prime portfolio offerings empower IT organizations to more effectively manage their networks and the services they deliver. Built on a service-centric foundation, the Cisco Prime portfolio of products supports integrated lifecycle management through an intuitive workflow-oriented user experience and a set of common operational attributes.

Cisco Prime products deliver unified management by supporting integrated lifecycle operations across Cisco architectures, technologies, and networks. The portfolio of Cisco Prime for Service Providers solutions provides A-to-Z management for IP Next-Generation Networks, Mobility, Video, and Managed services. Cisco Prime Network Registrar is a product of the Prime portfolio.

Cisco Prime Network Registrar is comprised of these components:

•An IP address management application

•A Domain Name System (DNS) protocol service

•A Caching DNS service

•A Dynamic Host Configuration Protocol (DHCP) service.

Cisco offers these components as individually licensable applications or in a mix of suites.

Cisco Prime Network Registrar provides the tools to configure and control the servers necessary to manage your IP address space.

Before you Begin

Before installing Cisco Prime Network Registrar 8.1.2, review the system requirements and licensing in the Cisco Prime Network Registrar 8.1 Installation Guide.

---

Note If you are migrating to Cisco Prime Network Registrar 8.1.2 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.

---

Before Cisco Prime Network Registrar 8.0, Cisco Network Registrar was licensed as a single system with a single license type called ip-node. With the introduction of Cisco Prime Network Registrar 8.0 and later releases, the licensing is done according to the services that you require. Cisco Prime Network Registrar 8.0 and later releases provides separate licenses for Authoritative DNS, Caching DNS, DHCP, and IPAM services or for combinations of these services.

---

Note Licenses for Cisco Network Registrar 6.x and 7.x are not valid for Cisco Prime Network Registrar 8.x.

---

Cisco Prime Network Registrar DHCP, Authoritative DNS, and Caching DNS components are licensed and managed from the Regional server. All services in the local clusters are licensed through the regional cluster. Only a regional install asks for 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.

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 on the Licensing, see the "License Files" section in the Overview chapter of the Installation Guide for Cisco Prime Network Registrar 8.x.

The Cisco Prime Network Registrar 8.1.2 kit contains the following files and directories:

•Solaris—Solaris 10 installation kit

•Linux5—Red Hat Linux ES 5.x or 6.x installation kit

•Windows—Windows Server 2008 R2 installation kit

•Docs—Product documentation in the PDF format

Interoperability

Cisco Prime Network Registrar 8.1.2 uses individual component licenses first introduced for version 8.0. Licenses issued for 8.0 or 8.1 or 8.1.1 are also valid for 8.1.2. The component licenses allow users to purchase and install Dynamic Host Configuration Protocol services (DHCP), and Domain Name System services (DNS) individually, or as a suite. When purchasing the full complement of Cisco Prime Network Registrar components, customers will receive a separate license package for Cisco Prime Network Registrar DHCP and DNS components.

To install and manage DHCP, DNS, and Caching DNS licenses customers must establish a Regional server. The Regional server is used to install, count, and manage licensing for these components.

For common features, Cisco Prime Network Registrar 8.1.2 is interoperable with 8.0 and later releases. External SDK clients using version 8.0 or later can be used to connect to 8.1.2 regional or local clusters. However, to make full use of new features in the later releases, it is recommended that the regional server and any external SDK clients be upgraded to use the new version. External SDK clients should be recompiled with the new kit whenever an updated SDK kit is deployed. Synchronizing operations between 8.1.2 and pre-8.1.2 local clusters should also be done from an 8.1.2 regional or the 8.1.2 local cluster.

Cisco Prime Network Registrar 8.1.2 protocol servers interoperate with versions 7.0 through 8.1.2. Cisco Prime Network Registrar 8.1.2 will not support interoperability with the versions before 7.0.x.

•Cisco Prime Network Registrar 8.1.2 DHCPv4 failover servers interoperate with Cisco Network Registrar 7.0 through 8.1.2 failover servers.

•By the nature of the EDNS0 protocol, Cisco Prime Network Registrar 8.1.2 DNS servers interoperate with earlier versions of Cisco Prime Network Registrar DNS (and 3rd party DNS vendors). EDNS0 defines the interoperability with DNS servers that do not support EDNS0; Cisco Prime Network Registrar 8.1.2 DNS adhere to the RFC and consequently interoperate with earlier versions of Cisco Prime Network Registrar.

•Cisco Prime Network Registrar 8.1.2 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).

•The HA protocol version has been updated in Cisco Prime Network Registrar and communications with versions before 8.0 is not supported.

---

Note Interoperability applies only if the features are supported in both versions involved. You may not be able to synchronize configurations with clusters running older clusters if the feature is not supported in the older cluster.

---

Software Features Added in Release 8.1.2

This section describes the software features added in Cisco Prime Network Registrar Release 8.1.2. The following feature is introduced in this release:

•Market Segment Specific Licensing

Market Segment Specific Licensing

Cisco Prime Network Registrar introduced separate licenses for 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 Cisco Prime Network Registrar Installation Guide.

From 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 so on. Cisco Prime Network Registrar features are enabled based on the market segment specific license you choose. For example, the PNR license offers features designed for the Service Provider market segment which requires all the functionalities of Cisco Prime Network Registrar, whereas the PNR-SG license offers limited set of features which Smart Grid market segment requires.

In release 8.1.2, two sets of market segment based licenses are offered:

•PNR

•PNR-SG

---

Note If the licenses for both market segments are installed, then only the PNR license will be active.

---

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.

PNR Licenses

The PNR license provides all the features available for the Cisco Prime Network Registrar release you install. If you are using the license set for releases before 8.1.2, it means you are using the PNR license.

PNR-SG Licenses

The PNR-SG licensing offers you the Central Configuration Management (CCM) service license without the following PNR features:

•Tenants

•External Authentication

The DHCP service PNR-SG license offers you the PNR features with the exception of:

•Extensions

•Lightweight Directory Access Protocol (LDAP)

•TCP Listeners (client notification)

•Trivial File Transfer Protocol (TFTP)

•Router Interface Configuration (RIC)

•Virtual Private Networks (VPNs)

•Regional lease history and subnet utilization

Issues Resolved and Enhancements Added in Release 8.1.2

This section describes the most important changes made in the Cisco Prime Network Registrar 8.1.2.

•Issues Resolved in Release 8.1.2

•Enhancement Features Added in Release 8.1.2

Issues Resolved in Release 8.1.2

Table 1 lists the issues resolved in the Cisco Prime Network Registrar 8.1.2 release.

Click on the bug ID to view the bug details. This information is displayed in the Bug Toolkit.

Table 1 Issues Resolved in Cisco Prime Network Registrar 8.1.2 Release 

Bug ID	Description
CSCuc96698	DNS caches multiple copies of NS records when resolving recursive query
CSCuc99199	CDNS running on many cores may not start
CSCuc14576	Change logging to only flush after Warning or Error
CSCuc52453	Inhibit-renews-at-reboot does not work for DHCPv6
CSCuc77137	nrcmd cannot import root zone in bind format
CSCud39184	DNS is not consistently returning glue records that reside in subzones

For the complete list of bugs for this release, see the cnr_8_1_2-buglist.pdf file available at the product download site. Refer to this list especially for information about fixes to customer-reported issues.

Enhancement Features Added in Release 8.1.2

Table 2 lists the enhancement features added in the Cisco Prime Network Registrar 8.1.2 release.

Click on the bug ID to view the bug details. This information is displayed in the Bug Toolkit.

Table 2 Enhancement Features Added in Cisco Prime Network Registrar 8.1.2 Release

Bug ID	Description
CSCua62983	Ensure offered T1/T2 times don't exceed configured T1/T2 times
CSCub11485	Support unprotected names for primary zone creation from zone file
CSCub24296	Documented nrcmd zone create primary from file syntax not supported
CSCuc71781	Expand information on new Cisco Prime Network Registrar 8.x licensing
CSCuc01674	CPNR should support 64-bit RHEL 6

For the complete list of enhancements for this release, see the cnr_8_1_2-enhancement_list.pdf file available at the product download site.

Limitations and Restrictions

This section describes limitations and restrictions you might encounter using Cisco Prime Network Registrar 8.1.2.

•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 work around 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 server running DHCPv6 cannot support as many leases (clients) as 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.

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

Important Notes

This section contains important information related to this software release that was unavailable when the user documentation was completed. This section describes:

•Moving a Regional Cluster to a New Machine

•New DHCP Policy Attributes

•Troubleshooting Local Cluster Licensing Issues

Moving a Regional Cluster to a New Machine

License management is done from the regional cluster when Cisco Prime Network Registrar is installed. The regional server is installed first and all licenses are loaded in the regional server. When the local cluster is installed, it registers with the regional server to obtain its license.

When you want to move a regional cluster to a new machine, you need to back up the data on the old regional cluster and copy the data to the same location on the new machine.

---

Note When the regional server goes down or is taken out of service, the local cluster is not aware of this action. If the outage lasts for less than 24 hours it results in no impact on the functioning of the local clusters. However, if the regional cluster is not restored for more than 24 hours, the local cluster will get warning messages that the local cluster is not properly licensed (in the web UI, CLI, or SDK). This does not impact the operation of the local clusters and the local clusters continue to work and service requests.

---

To move an existing Cisco Prime Network Registrar installation to a new machine:

---

Step 1 Stop the server agent on the old regional server:

•Windows:
net stop nwregregion

•Solaris and Linux:
# etc/init.d/nwregregion stop

Step 2 Zip up the data directory on the old regional server.

Step 3 Copy the zip file over to the same location on the new server.

Step 4 Install Cisco Prime Network Registrar (regional cluster) on the new server. For more information, see Installation and Upgrade Procedure section of Cisco Prime Network Registrar 8.1 Installation Guide.

The installation will detect an upgrade and will do so based on the copied data. This procedure preserves your original data from the old regional server.

---

Note When you install Cisco Prime Network Registrar on the new machine, you must choose the data directory on which you have copied the data from the old regional server.

---

Step 5 Start the Cisco Prime Network Registrar web UI or CLI. For more information, see Starting Cisco Prime Network Registrar section of Cisco Prime Network Registrar 8.1 Installation Guide.

Step 6 Log in as superuser to the CLI for the new regional cluster.

Step 7 To list the local clusters:

nrcmd-R>cluster listnames

Step 8 To synchronize the data as well as the license information:

nrcmd-R>cluster <name of local cluster> sync

---

New DHCP Policy Attributes

In the Cisco Prime Network Registrar 8.1.2 release, new attributes have been added to the DHCP policy. These attributes can be used to limit the values that are sent to the DHCPv4 clients for the lease time, t1 (renewal), and t2 (rebinding) and to the DHCPv6 clients for the valid and preferred lifetimes, t1 (renewal), and t2 (rebinding).

The DHCPv4 client attributes (max-client-renewal-time, max-client-rebinding-time, and max-client-lease-time) must be set explicitly. For example, if the lease time attribute is specified then the renewal and rebinding attributes should also be specified. This restriction does not apply to the DHCPv6 attributes but it is recommended that the DHCPv6 attributes (v6-max-client-renewal-time, v6-max-client-rebinding-time, v6-max-client-preferred-lifetime, and v6-max-client-valid-lifetime) are set as a group.

Table 3 lists the DHCP policy attributes that have been added in the Cisco Prime Network Registrar 8.1.2 release.

Table 3 DHCP Policy Attributes

Option Name	Description
max-client-renewal-time	The maximum client renewal time (T1) that the server is allowed to send to the client. This attribute limits the time sent to the client; it does not impact any of the lease time calculations made by the server. Value (in seconds): 30 to 2147483647
max-client-rebinding-time	The maximum client rebinding time (T2) that the server is allowed to send to the client. This attribute limits the time sent to the client; it does not impact any of the lease time calculations made by the server. Value (in seconds): 30 to 2147483647
max-client-lease-time	The maximum client lease time that the server is allowed to send to the client. This attribute limits the time sent to the client; it does not impact any of the lease time calculations made by the server, including when it expects the client to renew (T1). Value (in seconds): 60 to 2147483647
v6-max-client-renewal-time	The maximum client renewal time (T1) that the server is allowed to send to the client. This attribute limits the time sent to the client; it does not impact any of the lease time calculations made by the server. Value (in seconds): 30 to 2147483647
v6-max-client-rebinding-time	The maximum client rebinding time (T2) that the server is allowed to send to the client. This attribute limits the time sent to the client; it does not impact any of the lease time calculations made by the server. Value (in seconds): 30 to 2147483647
v6-max-client-preferred-lifetime	The maximum client preferred lifetime that the server is allowed to send to the client. This attribute limits the preferred lifetime sent to the client; it does not impact any of the time calculations made by the server. Value (in seconds): 60 to 2147483647
v6-max-client-valid-lifetime	The maximum client valid lifetime that the server is allowed to send to the client. This attribute limits the valid lifetime sent to the client; it does not impact any of the time calculations made by the server. Value (in seconds): 60 to 2147483647

Troubleshooting Local Cluster Licensing Issues

If your regional cluster and local cluster are located in isolated networks, are separated by a firewall, or the time skew between the regional and local clusters is more than five minutes, then the local cluster may be unable to register with the regional server. The firewall may block the return connection used to validate the local cluster admin credentials that are sent from the local cluster to the regional cluster.

To register a local cluster with the regional cluster:

---

Step 1 Install Cisco Prime Network Registrar (local cluster) on the server and create the admin user for the local cluster. For more information, see Installation and Upgrade Procedure section of Cisco Prime Network Registrar 8.1 Installation Guide.

When you install Cisco Prime Network Registrar on the local cluster, you can skip the registration of the local cluster with the regional cluster.

Step 2 Log into the regional cluster, and add the new local cluster to the regional cluster with the admin credentials. For more information, see Adding Local Clusters section of Cisco Prime Network Registrar 8.1 User Guide.

Step 3 To synchronize the data as well as the license information, click the Resynchronize icon next to the cluster name on the List/Add.

---

Product Documentation

---

Note We sometimes update the documentation after original publication. Therefore, you should review the documentation on Cisco.com for any updates.

---

You can view the marketing and user documents for Cisco Prime Network Registrar 8.1 at: http://www.cisco.com/en/US/products/ps11808/tsd_products_support_series_home.html.

The following document lists the documents available for Cisco Prime Network Registrar 8.1:
http://www.cisco.com/en/US/docs/net_mgmt/prime/network_registrar/8.1/doc_overview/guide/
CNR81DocGuide.html

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.

---

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.

© 2013 Cisco Systems, Inc. All rights reserved.