Contents

Introduction

Before You Begin

Requirements

IPAM 8.3 with CPNR 9.0 - Setup

New Features in CPNR 8.3 and 9.0

New Features in IPAM 8.3

Summary

Related Information

Introduction

This document describes the compatibility of Cisco Prime Network Registrar (CPNR) IP Address Management (IPAM) 8.3 with CPNR 9.0. It describes the changes which must be made when you install the IPAM Executive/Remote agents in order to enable IPAM 8.3 to work with CPNR 9.0.

This document also identifies the CPNR 8.3 and 9.0 features which can be used with IPAM 8.3.

Before You Begin

Requirements

The CPNR 9.0 32-bit Software Development Kit (SDK) package should be used to replace the "cnrsdk" folder in the IPAM 8.3 Executive/Remote agent.

IPAM 8.3 with CPNR 9.0 - Setup

In order to make IPAM 8.3 work with CPNR 9.0, the "cnrsdk"folder (<INC-HOME>/cnrsdk) in the IPAM Executive/Remote agent has to be replaced with the contents of the 32-bit CPNR 9.0 SDK package. In IPAM 8.1.2 and later, the use of the IPAM Remote Agent to manage CPNR servers is mandatory. It will suffice to replace the "cnrsdk" folder with CPNR 9.0 SDK on the IPAM 8.3 Remote agent only.

Complete these steps in order to replace the "cnrsdk" folder of the IPAM Remote Agent:

1. Stop the IPAM 8.3 Remote agent.

For Linux: <INC-HOME>/etc/incontrol stop

For Windows: Use Windows Service Controller in order to stop the IPAM Services.

By default <INC-HOME> directory for:

Windows: C:\Program Files\Cisco\Cisco Prime Network Registrar IPAM

Linux: /opt/incontrol

2. Navigate to the "<INC-HOME>/cnrsdk" folder or subdirectory on the IPAM Remote agent.

3. Remove all the files/folders in the "cnrsdk" folder or subdirectory, but not the folder itself.

4. Copy the CPNR 9.0 32-bit SDK package into the "<INC-HOME>/cnrsdk" folder.

5. Extract the CPNR 9.0 SDK package.

6. Copy the cnrsdk.jar from the "<INC-HOME>/cnrsdk/classes" folder to the "<INC-HOME>/classes" directory.

cp <INC-HOME>/cnrsdk/classes/cnrsdk.jar <INC-HOME>/classes

7. Start the IPAM services in remote agent.

For Linux: <INC-HOME>/etc/incontrol start (you must be logged in as the "incadmin" user in order to start the IPAM agents).

For Windows: Use the Windows Service Controller in order to start the IPAM Services.

Note: In IPAM 8.3, when you create DHCP or Domain Name Server/Caching DNS (DNS/CDNS) servers for CPNR 9.0 DHCP/DNS/CDNS servers, the Product Name selected should be 'CNR DHCP 8.3' and 'CNR Authoritative DNS 8.3/CNR Caching DNS 8.3' respectively.

New Features in CPNR 8.3 and 9.0

These new features are introduced with CPNR 8.3:

- Client-based DNS64 prefixes

- Internationalized domain names

- CDNS and ADNS on the same OS (DNS hybrid)

- DNS Response Policy Zone (RPZ)

- Secured dynamic DNS and zone transfer using Generic Security Service Algorithm for Secret Key Transaction (GSS-TSIG)

- Representational State Transfer (REST) API support

- Resource limit alarms

- Installation of protocol servers without superuser privilege

- External authentication with Active Directory (AD)

- Bring Your Own Device (BYOD) support

These new features were introduced in CPNR 9.0:

- End-to-end IPv6 support

- Windows Server 2012 support

- DNS push notifications

- Weighted round robin for RRs

- Multiple DHCPv6 option instances

New Features in IPAM 8.3

IPAM 8.3 supports these features of CPNR 8.3 apart from various other enhancements:

- Client-based DNS64 prefixes

- DNS views (8.2 feature)

- Internationalized domain names

Summary

All the supported features of IPAM 8.3 will work correctly with CPNR 9.0 if the "cnrsdk" folder or subdirectory on the IPAM 8.3 Remote Agent is updated as described previously.

These new features of CPNR 8.3 and CPNR 9.0 can be used in a CPNR 9.0 installation managed by IPAM 8.3. The configuration for these new features can be done in CPNR 9.0 and be used:

- DNS Response Policy Zone (RPZ)

- REST API support
Note: Objects created/modified in CPNR through REST API calls will be wiped out if the DHCP/DNS configuration task is pushed from IPAM 8.3 to CPNR 9.0.

- Resource limit alarms

- Installation of protocol servers without superuser privilege

- External authentication with AD

- End-to-end IPv6 support

- Windows Server 2012 support

- DNS push notifications

- Weighted round robin for RRs

These features of CPNR 8.3 and 9.0 cannot be used with IPAM 8.3 if it is used to manage the CPNR 9.0 server:

- Secured dynamic DNS and zone transfer using GSS-TSIG

- CDNS and ADNS on the same OS (DNS hybrid)
Note: IPAM does not support configuration of both CDNS and ADNS servers with same IP address.

- BYOD Support
Note: The objects such as Scopes, Client Classes, and Clients created in Local will be removed when DHCP configuration is pushed from IPAM to CPNR.

Related Information

- Cisco Prime Network Registrar Documentation

- Technical Support & Documentation - Cisco Systems