Cisco Prime Network Registrar 8.1 Release Notes

Table Of Contents

Cisco Prime Network Registrar 8.1 Release Notes

Contents

Introduction

Before you Begin

Interoperability

Software Features Added in Release 8.1

Prefix Stability

Prefix Allocation Groups

Issues Resolved in Release 8.1

Enhancement Features Added in Release 8.1

Limitations and Restrictions

Defects

Product Documentation

Obtaining Documentation and Submitting a Service Request

Cisco Prime Network Registrar 8.1 Release Notes

---

Revised: April 2012, OL-26361-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.

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

Contents

This release notes includes the following sections:

•Introduction

•Before you Begin

•Interoperability

•Software Features Added in Release 8.1

•Limitations and Restrictions

•Defects

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

This release of Cisco Prime Network Registrar includes the following features and enhancements:

•Prefix Stability

•Prefix Allocation Groups

For more information about these features see Software Features Added in Release 8.1.

Before you Begin

Before installing Cisco Prime Network Registrar 8.1, 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 from an earlier version of Cisco Network Registrar, you must review the release notes for the releases that occurred in between, to fully understand all the changes.

---

Interoperability

Cisco Prime Network Registrar 8.1 uses individual component licenses. This allows 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.

The synchronizing operation between 8.1 and pre-8.1 local clusters must be done from an 8.1 local cluster. Cisco Prime Network Registrar 8.1 protocol servers interoperate with versions 7.2, 7.1, 7.0, and 8.0. Cisco Prime Network Registrar 8.1 will not support interoperability with the versions before 7.0.x.

•Cisco Prime Network Registrar 8.1 DHCPv4 failover servers interoperate with Cisco Network Registrar 7.2, 7.1.x, 7.0.x, 8.0.x failover servers.

•By the nature of the EDNS0 protocol, Cisco Prime Network Registrar 8.1 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 DNS adhere to the RFC and consequently interoperate with earlier versions of Cisco Prime Network Registrar.

•Cisco Prime Network Registrar 8.1 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 be 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

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

•Prefix Stability

•Prefix Allocation Groups

•Issues Resolved in Release 8.1

•Enhancement Features Added in Release 8.1

Prefix Stability

Cisco Prime Network Registrar 8.1 supports the prefix stability feature which allows the clients to retain the delegated prefix when they change their location, that is even when they move from one CMTS to another or move within an address space. Prefix Stability, with appropriate infrastructure support (CMTS, routers), allows the subscriber to be moved or move without requiring a different delegated prefix (see the Prefix Stability section in the Managing IPv6 Addresses chapter of Cisco Prime Network Registrar 8.1 User Guide).

Prefix Allocation Groups

Cisco Prime Network Registrar 8.1 supports the creation of prefix allocation groups which allows multiple prefixes to be treated as one from an allocation standpoint, and provides control over the order in which the prefixes are used (see the Prefix Allocation Groups section in the Managing IPv6 Addresses chapter of Cisco Prime Network Registrar 8.1 User Guide).

Issues Resolved in Release 8.1

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

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

Table 1 Issues Resolved in Cisco Prime Network Registrar 8.1 Release

Identifier	Description
CSCtx01741	SNMP returns error for deprecated DNS statistics
CSCtr30036	CCM upgrade fails to migrate option definition sets from export to CCM
CSCtu10319	Scope re-subnetting causes failover sync failure
CSCty47576	HA DNS Sync Report may unexpectedly change Host entries
CSCty89662	CCM may crash when using SSL
CSCtx03300	Caching DNS General Indicator chart does not display any information

Enhancement Features Added in Release 8.1

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

Click on the identifier 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 Release

Identifier	Description
CSCtw70519	Add ability to control whether unset attributes are shown or not
CSCty22605	Add query logging to CDNS
CSCty45912	Upgrade Virtual Appliance OS to CentOS 6.0

Limitations and Restrictions

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

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

•Some distributions of Red Hat provide incompatible versions of OpenLDAP libraries. If the expected version of the libraries does not exist, the DHCP server is unable to start.

To know the required version of the OpenLDAP library, run:

ldd /opt/nwreg2/local/bin/dhcp.

To determine whether the DHCP server is failing to start:

–Review the logs/agent_server_1_log file. If it shows frequent "... 08012 server agent loading 'dhcp' ..." messages and there are no name_dhcp_1_log files (or new entries in the log file), then there could be an OpenLDAP version mismatch.

–Enter the following commands:

bash

export ld_library_path=/opt/nwreg2/local/lib

/opt/nwreg2/local/bin/dhcp -v

If the dhcp -v command displays a message that libraries (ldap and lber) cannot be found, then you have a Red Hat release with different LDAP libraries.

There are two workarounds for this issue:

–If the DHCP server is not needed in your environment, you should disable the DHCP server from starting. To do this, use the nrcmd dhcp disable start-on-reboot command, and restart Cisco Prime Network Registrar.

–If the DHCP server is needed, create symbolic links to the OpenLDAP libraries available on your system. For example:

ln -s /lib/libldap_r-2.4.so.2.5.6 /lib/libldap_r-2.3.so.0

ln -s /lib/liblber-2.4.so.2.5.6 /lib/liblber-2.3.so.0

Depending on the Red Hat version, you must replace the first file path in the example, with the proper version for the libraries.

ldd /opt/nwreg2/local/bin/dhcp shows the version that DHCP expects (these are the second file path in the above ln commands):

libldap_r-2.3.so.0 => /lib/libldap_r-2.3.so.0 (0x00a81000)

liblber-2.3.so.0 => /lib/liblber-2.3.so.0 (0x04e65000)

Defects

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

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.

© 2012 Cisco Systems, Inc. All rights reserved.