Cisco Prime Network Registrar IPAM 8.1.3 Release Notes
June 3, 2015
These release notes provide an overview of the fixed and open defects in Cisco Prime Network Registrar IPAM 8.1.3, and describe how to access information about the known problems in Cisco Prime Network Registrar IPAM 8.1.3.
Note: You can access the most current Cisco Prime Network Registrar IPAM documentation, including these release notes, online at:
Cisco Prime Network Registrar IPAM is a comprehensive software solution that helps organizations plan and maintain their IP address space and leverages that information for use by IP services such as DNS and DHCP.
Cisco Prime Network Registrar IPAM is a next generation tool that offers advanced functionality:
■Centralized planning and management of the complete address space down to the individual IP address level
■Centralized DNS and DHCP configuration management.
■IPv4 and IPv6 support.
■Automated address utilization collection and reporting.
■Address utilization forecasting and trending analysis.
■APIs and Command Line Interfaces for integration with any type of system. Examples are work-flow systems, provisioning systems, change management systems, or network management systems.
Unlike other tools that maintain IP name and address data as discrete information maintained uniquely and separately, Cisco Prime Network Registrar IPAM interacts with network devices and services to:
■Verify that the actual network matches the information in Cisco Prime Network Registrar IPAM.
■Capture and record utilization information to be able to establish historical trends.
■Reclaim inactive addresses.
This interaction not only maintains consistency between the planned and deployed network, but allows proactive modification to the network to adjust for IP address shortages and overages.
Before you Begin
For information on installing Cisco Prime Network Registrar IPAM, refer to Cisco Prime Network Registrar IPAM 8.1.3 Installation Guide.
To start using the Cisco Prime Network Registrar IPAM Management System, all Cisco Prime Network Registrar IPAM services, and the Cisco Prime Network Registrar IPAM database must be started.
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.
Limitations and Restrictions
When IPAM 8.1.3 is installed in Solaris platform, a missing library file (libstdc++.so.6) has to be manually copied to <INCHOME>/cnrsdk/lib directory of IPAM Remote Agent from /opt/nwreg2/local/lib (CPNR install directory) to make the DHCP/DNS/CDNS deployment tasks complete successfully. For more details, refer to the release notes enclosure of CSCuu39438.
Cisco Prime Network Registrar IPAM Bugs
For more information on a specific bug or to search all bugs in a particular Cisco Prime Network Registrar IPAM release, see Using the Bug Search Tool.
This section contains the following information:
■Using the Bug Search Tool
Resolved Bugs in Cisco Prime Network Registrar IPAM 8.1.3 lists the key issues resolved in the Cisco Prime Network Registrar IPAM 8.1.3 release.
Table 1 Resolved Bugs in Cisco Prime Network Registrar IPAM 8.1.3
Container Management Administrator Policy does not work after upgrade
Symptom: Container Management Administrator Policy does not work in IPAM 8.1.2 after upgrade from 8.1.1.
Conditions: When upgrading from 8.1.1
Open Caveats in Cisco Prime Network Registrar IPAM 8.1.3 lists the open caveats in the Cisco Prime Network Registrar IPAM 8.1.3 release.
Table 2 Open Caveats in Cisco Prime Network Registrar IPAM 8.1.3
IPAM is not able to establish secure connection with CPNR
Symptom: If CPNR is installed in secure mode (by choosing the Security Mode configuration as Required), IPAM is not able to establish connection to CPNR through SDKs and “AX_SCP_SECURITY_REQUIRE” exception is thrown while deploying a DHCP/DNS task and the task fails.
Conditions: When IPAM manages DHCP/DNS servers of CPNR installed in secure mode
Workaround: Install CPNR in unsecure mode by choosing the option as “Optional. Allow fallback to unsecure connection” which is the default option for Security mode configuration.
Unable to deploy tasks from IPAM in Solaris platform
Symptom: Deployment of DHCP/DNS configuration task fails in IPAM with an error due to missing library in CNR SDK.
2015-05-07 08:49:14,453 ()[Thread-6] ERROR Engine - Exception running task 12: /opt/incontrol/cnrsdk/lib/libscp_java01.so: ld.so.1: java: fatal: libstdc++.so.6: open failed: No such file or directory
java.lang.UnsatisfiedLinkError: /opt/incontrol/cnrsdk/lib/libscp_java01.so: ld.so.1: java: fatal: libstdc++.so.6: open failed: No such file or directory
Conditions: This occurs in IPAM 8.1.3 Executive/ Remote Agent installation in Solaris platform
Workaround: Copy the missing library 'libstdc++.so.6' from CPNR installation to cnrsdk folder in IPAM Remote Agent installation, since we use IPAM remote agent to manage CPNR DHCP/DNS servers.
In the Solaris machine where CPNR DHCP/DNS server is running with IPAM Remote agent:
■Navigate to /opt/nwreg2/local/lib folder in CPNR installation directory.
■Copy the 'libstdc++.so.6' to 'lib' folder of IPAM Remote Agent directory by executing the below command
cp libstdc++.so.6 /opt/incontrol/cnrsdk/lib
■Restart the IPAM Remote Agent service by executing the below command as incadmin user
Try to deploy DHCP/DNS configuration task deployment now.
Primary subnet usage becomes invalid in IPAM
Symptom: Deploying a primary subnet from IPAM results in all the other subnets previously created becoming the secondary subnet irrespective of the block created. Hence there can be only one primary subnet created and all the other subnets become the secondary subnet.
Conditions: This problem occurs when a child address block is created by selecting the “Primary Subnet” option and the DHCP task is deployed.
Workaround: None. The “Primary Subnet” option should not be selected when creating a child address block is created.
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.
1. Go to http://tools.cisco.com/bugsearch.
2. At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Search page opens.
Note: If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.
3. To search for a specific bug, enter the bug ID in the Search For field and press Return.
4. To search for bugs in the current release:
a. Click the Search Bugs tab and specify the following criteria:
b. In the Search For field, enter Prime Network Registrar IPAM 8.1.3 and press Return. (Leave the other fields empty.)
c. When the search results are displayed, use the filter tools to find the types of bugs you are looking for. You can search for bugs by status, severity, modified date, and so forth.
Note: To export the results to a spreadsheet, click the Export All to Spreadsheet link.
Accessibility Features in Cisco Prime Network Registrar IPAM 8.1.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 email@example.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
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.
© 2015 Cisco Systems, Inc. All rights reserved.