Release Notes for Cisco Network Registrar 7.2.0.1
Available Languages
Table Of Contents
Release Notes for Cisco Network Registrar 7.2.0.1
Software and Standards Compatibility
Installation and Upgrade Notes
About Cisco Network Registrar SDK
Installing Cisco Network Registrar SDK
Installing on Linux or Solaris
Software Features Added in Release 7.2.0.1
Key Defects fixed in this release
External Authentication and Authorization
DB_CONFIG files in the CNRDB database
Displaying Cisco Network Registrar Processes that are Running
Turning off Cisco Network Registrar Processes
Changes to client_mac_addr Attribute
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Network Registrar 7.2.0.1
Revised: September 15, 2011
This release notes describes the system requirements, new software features, and installation and upgrade notes for Cisco Network Registrar 7.2.0.1.
Contents
This release notes includes the following sections:
•
Software and Standards Compatibility
•
•
•
•
Introduction
Cisco Network Registrar provides the tools to configure and control the servers necessary to manage your IP address space. This release of Cisco Network Registrar includes the following features and enhancements:
•
•
•
•
•
•
•
For more information about these features see the "Software Features Added in Release 7.2.0.1" section.
Before you Begin
Review the following sections before installing Cisco Network Registrar 7.2.0.1:
Note
Note
System Requirements
Review these system requirements before installing the Cisco Network Registrar 7.2.0.1 software:
•
•
Cisco Network Registrar now supports running in VMWARE (ESX 4.1 and 4.0) environment.
Note
•
–
Note
–
Note
Tip
Table 1 Cisco Network Registrar System Recommendations
OS version1
Solaris 102
Red Hat Enterprise Linux 5.03
Windows Server 2008 R2
Disk space4
2 x 73/146 SAS5 drives
With basic DHCP and optimal hardware configuration:
SATA6 drives with 7500 RPM drive greater than 500 leases/second
SAS drives with 15K RPM drive greater than 1000 leases/second
(Recommended hard drive 146 GB)
Memory7
16 GB
4 GB (small networks), 8 GB (average networks), or 16 GB (large networks)
1 Cisco Network Registrar must run on 32-bit or 64-bit operating systems.
2 Cisco Network Registrar 7.2.0.1 supports 128-KB block sizes in the Solaris 10 ZFS.
3 Cisco Network Registrar now supports running in VMWARE (ESX 4.1 and 4.0) environment.
4 Higher I/O bandwidth usually results in higher average leases per second.
5 Serial Attached SCSI.
6 Serial Advanced Technology Attachment (Serial ATA).
7 Faster CPU and more memory typically result in higher peak leases per second.
Note
Software and Standards Compatibility
With the features introduced in this release, the software conforms to the following additional document:
•
•
•
Interoperability
Cisco Network Registrar 7.2.0.1 protocol servers interoperate with versions 7.1, 7.0, and 6.3.x. Cisco Network Registrar 7.2.0.1 will not support interoperability with the versions before 6.3.x.
•
•
•
•
Installation and Upgrade Notes
Review the following points before beginning a new installation or an upgrade. For full installation and upgrade procedures, see the Installation Guide for Cisco Network Registrar 7.2.
This section covers:
For information about Network Registrar SDK, see the "About Cisco Network Registrar SDK" section.
General Installation
Refer the Installation Guide for Cisco Network Registrar 7.2 for the detailed installation procedure. Points to remember while installing Cisco Network Registrar 7.2.0.1 are as follows:
Note
•
–
–
When installing Cisco Network Registrar on a 64-bit system, you must ensure that it is installed in the \Program Files (x86) area and that you specify the path to a 32-bit version of the Java Runtime Environment.
•
–
MessageIDIndex.html–
Upgrade Considerations
Cisco Network Registrar no longer supports the Windows Server 2003, Red Hat 4.0, 3.0, and Solaris 8 and 9 operating systems. Backup your Cisco Network Registrar data and upgrade your operating system before installing this latest release. (See Table 1 for currently supported operating systems.)
Note
The MCD DB database technology has been in use in Cisco Network Registrar for several earlier version. The mcdexport kit extracts the MCD DB data, which, during the upgrade procedure, is transferred to new locations.
When you install the software, the installation program automatically detects an existing version and upgrades the software to the latest release. The program first prompts you to archive existing Cisco Network Registrar data. If the program encounters errors during the upgrade, it restores the software to the earlier release.
During an upgrade, Network Registrar displays any pre-existing HTTPS configuration defaults for the keystore filename and password to enable a secure connection for web UI logins. If you have enabled HTTPS, and are unaware of the keystore filename and password at the time of the upgrade, you can preserve HTTPS connectivity during the upgrade, and re-enter the defaults when prompted.
Note
For detailed install and upgrade procedures, see "Installation and Upgrade Procedure" section in Installation Guide for Cisco Network Registrar 7.2.
To revert to an earlier version of Cisco Network Registrar, see the "Reverting to Earlier Product Version" procedure in Installation Guide for Cisco Network Registrar 7.2.
To move Cisco Network Registrar to a new machine, see the "Moving an Installation to a New Machine" procedure in Installation Guide for Cisco Network Registrar 7.2.
About Cisco Network Registrar SDK
This section documents how to install the Cisco Network Registrar SDK and details the compatibility considerations. The following are the topics covered in this section:
•
Installing Cisco Network Registrar SDK
This section documents how to install the Cisco Network Registrar SDK on the Linux, Solaris, and Windows platforms. Before installing the SDK, ensure that you have Java Runtime Environment (JRE) 5.0 (1.5.0_06) or later, or the equivalent Java Development Kit (JDK), installed on your system.
Installing on Linux or Solaris
To install the Cisco Network Registrar SDK on a Linux or Solaris platform:
Step 1
a.
% mkdir /cnr-sdk
b.
% cd /cnr-sdk
% tar xvf sdk_tar_file_location/cnrsdk.tar
Step 2
% export LD_LIBRARY_PATH=/cnr-sdk/lib
% export CLASSPATH=/cnr-sdk/classes/cnrsdk.jar:.
Installing on Windows
To install the Cisco Network Registrar SDK on a Windows platform:
Step 1
a.
> md c:\cnr-sdk
b.
> c:
> cd \cnr-sdk
> tar xvf sdk_tar_file_location\cnrsdk.tar
You may optionally use Winzip to extract cnrsdk.tar to the C:\cnr-sdk directory.
Step 2
> set PATH=%PATH%;c:\cnr-sdk\lib
> set CLASSPATH=c:\cnr-sdk\classes\cnrsdk.jar;.
Testing Your Installation
On Linux or Solaris, the following test program verifies that you have set your PATH or LD_LIBRARY_PATH correctly:
% java -jar /cnr-sdk/classes/cnrsdk.jar
On Windows, the following test program verifies that you have set your CLASSPATH correctly:
> java -jar c:\cnr-sdk\classes\cnrsdk.jar
Compatibility Considerations
For Java SDK client code developed with an earlier version of the SDK, you can simply recompile most code with the latest JAR file to connect to an upgraded server.
But in cases where the client code for versions before 7.1 directly manipulates reservation lists in scopes or prefixes, changes are required. These changes are required because the embedded reservation lists in both scopes and prefixes are no longer used. Beginning with version 7.1, individual reservations are stored separately and reference the parent scope or prefix by name.
The new design provides the following benefits:
•
•
•
No changes are required for client code that adds or removes reservations using the addReservation or removeReservation methods. However, these methods are now deprecated because the edit functionality is replaced and extended by the general addObject, modifyObject, removeObject, addObjectList, modifyObjectList, and removeObjectList methods.
Software Features Added in Release 7.2.0.1
This section describes the most important changes made in the Cisco Network Registrar 7.2.0.1.
•
•
•
•
Key Defects fixed in this release
The following key defects are resolved in this release:
CSCsj27431 - CNR-SDK JNI should use Java's memory allocation.
Problem
The CNR-SDK JNI layer, which calls native C/C++ library routines, does not make use of Java's memory allocation functions but instead uses the C RTL malloc/free routines. The Java objects that hold references to the native CNR C/C++ library objects are extremely small and references huge amounts of memory.
This has implications for users of the CNR-SDK as Java is not aware of this usage and it does not run garbage collection.
Hence, Java applications use up a lot of memory, but relatively little Java memory.
Solution
Changes have been made to the CNR SDK which cause CNR SDK functions, by default, to exclusively allocate memory from the Java heap.
Earlier, the SDK dynamically allocated memory using both the C run time library (RTL) and Java heap management. In some cases, small Java objects allocated by the CNR SDK would maintain handles to larger memory blocks allocated through the C RTL memory management interface.
The Java VM would be aware of the smaller blocks allocated from the Java heap, but would not be aware of the larger blocks allocated through the C RTL, and so would not consider the larger blocks when performing garbage collection. A long-running application could thus grow to consume large amounts of memory before Java VM garbage collection was triggered.
Note
To revert to previous behavior and have the SDK allocate memory using the C RTL, specify the SCPLIB_NO_JAVA_HEAP flag to the init method of the ScpLib object during SDK initialization:
ScpLib.init(ScpLib.SCPLIB_NO_JAVA_HEAP);
This method must be invoked before any other CNR SDK methods are invoked.
Note
Other techniques to reduce SDK application memory consumption are:
•
•
•
SDK applications which periodically invoke System.gc() to control memory use may potentially be modified to eliminate or reduce the frequency of those invocations. However, if the SDK library is initialized to use C RTL allocation (ScpLib.init(ScpLib.SCPLIB_NO_JAVA_HEAP) invoked), then invocations of System.gc() used to control memory use should be retained.
CSCts09966 - Failover sync fails to match all scopes to failover pair
Problem
Scopes are skipped if there is a secondary scope with a lower subnet address and a higher primary-subnet address than the scope subnet address.
Solution
Use the 'SyncFailoverScopes' SDK command-line utility program to sync the scopes, before running CCM failover synchronization.
CSCts22441 - CNR SNMP Agent does not support the .0 instance identifier
Problem
The CNRSNMP agent will report that the OID.0 (OID.<zero>) instance of an object does not exist whereas RFC 1157 indicates that it should be possible to ask for OID and OID.0 interchangeably.
Solution
Behaviour of snmp server is changed to handle an instance identifier of "0" when appropriate.
Note
Client Reservations
Client reservations feature enables you to supply addresses and delegate prefixes through client entries (either stored directly by Cisco Network Registrar or in LDAP) or through extensions. Also, a client can be located on more than a single scope or prefix and the server will select the address appropriate to the location of the client.
For more details, see "Using Client Reservations" in the Managing Leases chapter of the User Guide for Cisco Network Registrar 7.2.
Support Bulk Leasequery in v6
Bulk Leasequery for DHCPv6 is now implemented based on IETF RFC 5460.
For more details, see the "Leasequery for DHCPv6" section in the Managing Leases chapter of the User Guide for Cisco Network Registrar 7.2.
Database Changes
Raima DB is removed from Cisco Network Registrar software. Some of the data (DHCP Client entry and DHCP state data) will be relocated to the new Oracle Berkeley DBs, and the remaining MCD DB data will be relocated to the existing Oracle Berkeley DB.
For more details, see the "Backup and Recovery" chapter of the User Guide for Cisco Network Registrar 7.2.
External Authentication and Authorization
Cisco Network Registrar includes a RADIUS client component, which is integrated with the authentication and authorization module of the Central Configuration Management (CCM) server. You can configure a list of external RADIUS servers to be used for external authorization at local and regional clusters.
For more details, see the "Configuring External Authentication Servers" section in the Configuring Administrators chapter of the User Guide for Cisco Network Registrar 7.2.
Lease History Enhancements
Using Cisco Network Registrar 7.2.0.1, you can search for leases, server-wide. Following are the lease history enhancements introduced in Cisco Network Registrar 7.2.0.1:
•
–
Note
•
For more details, see the "Managing Leases" chapter of the User Guide for Cisco Network Registrar 7.2.
Virtual Appliance
The Cisco Network Registrar application can run on virtual machines. The purpose of this is to package Cisco Network Registrar to run as a virtual appliance. The Cisco Network Registrar Virtual Appliance consists of a virtual machine which contains a guest operating system and a version of Cisco Network Registrar installed on top of that guest operating system.
For more details, see the "Virtual Appliance" section of the User Guide for Cisco Network Registrar 7.2. For details regarding installing and upgrading Virtual Appliance, see Installation Guide for Cisco Network Registrar 7.2.
Multi-Tenancy
The multi-tenant architecture of Cisco Network Registrar provides the ability to segment the data created on regional and local clusters by tenant. When tenants are defined, data is partitioned by tenant in the embedded databases of each cluster. This provides data security and privacy for each tenant, while allowing cloud or managed service providers the flexibility to consolidate many smaller customer configurations on a set of infrastructure servers, or distribute a larger customer configuration across several dedicated servers.
Note
For more details, see the "Configuring Administrators" chapter of User Guide for Cisco Network Registrar 7.2.
DB_CONFIG files in the CNRDB database
CNR now creates a DB_CONFIG file in the CNRDB database directories. The DB_CONFIG files provide the linkage to the log subdirectory that contains the database log files. These DB_CONFIG files must not be deleted. In addition, you must not copy the log files to the database directory before performing database operations (as described in the "Backup and Recovery" chapter of the User Guide for Cisco Network Registrar for versions before 7.2.0.1).
New Platform Support
Cisco Network Registrar 7.2.0.1 supports Windows Server 2008 R2. Cisco Network Registrar 7.2.0.1 does not support Windows Server 2003, Red Hat Enterprise Linux 4.0, and Solaris 8 and 9 operating systems.
Initial Administration User
Cisco Network Registrar no longer creates a default username (admin) and password (changeme). You have to create a new superuser after adding the license during the time of installation of Cisco Network Registrar or when you login to Cisco Network Registrar for the first time after installation (if you did not provide the license at the time of installation but still went ahead with installation). For details, see the Installation Guide and User Guide for Cisco Network Registrar 7.2.
Privacy Protection
Two attributes lease-retention-max-age and lease-retention-min-age are added to specify the lease date restrictions. When these attributes are enabled, the times in leases will be restricted between the lease-retention-min-age and lease-retention-max-age. This can be used to meet data retention restrictions for privacy protection. For details, see the User Guide for Cisco Network Registrar 7.2.
Limitations and Restrictions
This section describes limitations and restrictions you might encounter using Cisco Network Registrar 7.2.0.1.
•
To workaround 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.
•
You must:
–
–
Important Notes
This section contains important information related to this software release that was unavailable when the user documentation was completed. This section describes:
•
•
•
Displaying Cisco Network Registrar Processes that are Running
To display the Cisco Network Registrar processes that are running in Linux or Solaris platform, do the following:
Step 1
#install-path/[local|regional]/usrbin/cnr_statusStep 2
#lsof -i4Run the following command to display the ports that are open for IPv6 ports. The ports and the associated processes are listed based on pid.
#lsof -i6Step 3
To display the Cisco Network Registrar processes that are running in Windows platform, do the following:
Step 1
> wmic process get name,processid,parentprocessid
Step 2
Step 3
The cnrservagt process is the process which is the parent of all of the other processes in
Cisco Network Registrar.Step 4
>netstat -aoThis lists the open ports based on the process ID. Use the process IDs determined from Step 3 to access the information that results from running the above command netstat -ao, to determine all the open ports from any process that is a part of the Cisco Network Registrar.
You can also get some information about the running Cisco Network Registrar processes on all platforms using the Web UI Dashboard. The Dashboard element System Metrics displays some information about the Cisco Network Registrar processes that are running.
Turning off Cisco Network Registrar Processes
In earlier versions of Cisco Network Registrar, the nrcmd program had the server disable start-on-reboot and server enable start-on-reboot commands to control whether the DHCP, DNS, SNMP, and TFTP servers are started automatically or not.
With Cisco Network Registrar 7.2.0.1, nrcmd has the (expert mode, visibility 3) server-agent command which can be used to control the various processes that Cisco Network Registrar runs. For example:
nrcmd> session set visibility=3100 OKnrcmd> server-agent dhcp get enabled100 Okenabled=truenrcmd> server-agent dhcp disable enabled100 Oknrcmd> dhcp get start-on-reboot100 Okstart-on-reboot=disablednrcmd> server-agent dhcp enable enabled100 Oknrcmd> dhcp get start-on-reboot100 Okstart-on-reboot=enabledThe available servers here are dhcp, dns, ric, snmp, tftp, and tomcat. The Cisco Network Registrar cnrservagt and ccmsrv processes are not optional and should always be run.
Note
Changes to client_mac_addr Attribute
In earlier releases of Cisco Network Registrar, the Dynamic Lease Notification Client used to throw an exception when adding lease data if the MAC address length was more than six bytes. This was because the database field for the client_mac_addr attribute could accommodate only six-byte MAC addresses.
From Cisco Network Registrar 7.2.0.1, the Dynamic Lease Notification Client allows adding lease data for the full range of the possible chaddr field lengths (up to 16 bytes).
Note
Defects
You can find the complete list of resolved and known bugs in the cnr_7_2_0_1-buglist.pdf file included with the release. Refer to this list especially for information about fixes to customer-reported issues.
Product Documentation
Note
Table 2 describes the product documentation that is available. You can view the marketing and user documents for Network Registrar at: http://www.cisco.com/en/US/products/sw/netmgtsw/ps1982/index.html.
Table 2 Product Documentation
Documentation Guide for Cisco Network Registrar 7.2
•
•
http://www.cisco.com/en/US/products/sw/netmgtsw/ps1982/products_documentation_roadmaps_list.htmlUser Guide for Cisco Network Registrar 7.2
•
•
Installation Guide for Cisco Network Registrar 7.2
•
•
Quick Start Guide for Cisco Network Registrar 7.2
•
•
CLI Reference Guide for Cisco Network Registrar 7.2
•
•
Release Notes for Cisco Network Registrar 7.2.0.1 (This document)
•
http://www.cisco.com/en/US/products/sw/netmgtsw/ps1982/prod_release_notes_list.htmlCisco Network Registrar 7.2 Third Party and Open Source Licenses and Notices
•
•
Online Help
•
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 a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Product 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.
© 2011 Cisco Systems, Inc. All rights reserved.
Feedback