Cisco Prime Network Registrar

Introduction

This Tech Note documents the compatibility of Cisco Prime Network Registrar IPAM 8.1.2 with Cisco Prime Network Registrar 8.2. It describes the changes which must be made during the installation of the IPAM Executive/Remote agents in order to enable IPAM 8.1.2 to work with Cisco Prime Network Registrar 8.2.

This document also identifies the Cisco Prime Network Registrar 8.2 features which can be used with IPAM 8.1.2.

Before You Begin

Requirements

Cisco Prime Network Registrar 8.2 SDK package should be used to replace the ‘cnrsdk’ folder in IPAM Remote Agent.

Conventions

For more information on document conventions, refer to Cisco Technical Tips Conventions.

IPAM 8.1.2 with Cisco Prime Network Registrar 8.2 - Setup

To make IPAM 8.1.2 work with Cisco Prime Network Registrar 8.2, the ‘cnrsdk’ folder (<INC-HOME>/cnrsdk) in the IPAM Executive/Remote agent has to be replaced with the latest Cisco Prime Network Registrar 8.2 SDK package. Starting from IPAM 8.1.2 the use of the IPAM Remote Agent to manage Cisco Prime Network Registrar 8.x is mandatory. So it will suffice to replace the cnrsdk folder only on the IPAM 8.1.2 Remote agent.

These are the steps involved in replacing the ‘cnrsdk’ folder of the IPAM Remote Agent:

1. Stop the IPAM 8.1.2 Remote agent.

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

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

   By default <INC-HOME> directory for:

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

   Linux/Solaris: /opt/incontrol

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

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

4. Copy the Cisco Prime Network Registrar 8.2 SDK package (e.g.: cnrsdk-8.2.1311191408-Linux.tar for Linux) into the <INC-HOME>/cnrsdk folder.

5. Extract the Cisco Prime Network Registrar 8.2 SDK package.

6. Start the IPAM 8.1.2 Remote Agent.

   For Linux/Solaris: <INC-HOME>/etc/incontrol start (You must be logged in as the ‘incadmin’ user to start the IPAM agents)

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

   Once the ‘cnrsdk’ folder is replaced with the Cisco Prime Network Registrar 8.2 SDK, IPAM 8.1.2 can be used with Cisco Prime Network Registrar 8.2 on the Windows and Linux platforms.

For Solaris users:

In addition to the replacement of 'cnrsdk' folder in IPAM Remote Agent, the value of LD_LIBRARY_PATH in the ‘shrc’ file in <INC-HOME>/etc folder should be modified to make IPAM 8.1.2 work with Cisco Prime Network Registrar 8.2 in Solaris environment. Follow these steps to modify the value the LD_LIBRARY_PATH:

1. Stop the IPAM 8.1.2 Remote Agent.

   In Linux/Solaris: <INC-HOME>/etc/incontrol stop

   In Windows: Use Windows Service Controller to stop the IPAM Services

2. Open the ‘shrc’ file in <INC-HOME>/etc folder.

3. Modify the value of LD_LIBRARY_PATH to include the ‘lib' folder of Cisco Prime Network Registrar 8.2 Local cluster.

   Existing value of LD_LIBRARY_PATH:

   LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INCHOME/cnrsdk/lib;

   New value of LD_LIBRARY_PATH:

   LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INCHOME/cnrsdk/lib:/opt/nwreg2/local/lib; (if the installation directory of Cisco Prime Network Registrar is the default directory)

4. Start the IPAM 8.1.2 Remote Agent.

   In Linux/Solaris: <INC-HOME>/etc/incontrol start (You must be logged in as the ‘incadmin’ user to start the IPAM agents)

   In Windows: Use Windows Service Controller to start the IPAM Services.

   Once the above steps are executed after replacing the ‘cnrsdk’ folder, IPAM 8.1.2 can be used with Cisco Prime Network Registrar 8.2 on the Solaris platform.

New Features in Cisco Prime Network Registrar 8.2

The following new features are introduced with Prime Network Registrar 8.2:

1. DNS Database Enhancements

2. DNS Views

3. DNS ENUM

4. CDNS Domain Redirect

5. DHCID RR Support

6. DHCPv6 Dynamic Lease Notification

7. DHCPv6 Failover

8. Enhanced Web UI

Limitations of Prime IPAM 8.1.2 when used with Prime Network Registrar 8.2

This section describes the Cisco Prime Network Registrar 8.2 features that are not supported or which cannot be used when IPAM 8.1.2 is used to manage Cisco Prime Network Registrar 8.2. It also includes the list of deprecated attributes of the DHCP and DNS servers of Cisco Prime Network Registrar 8.2. These attributes should not be configured in IPAM 8.1.2 in order to make IPAM 8.1.2 compatible with Cisco Prime Network Registrar 8.2.

Unsupported Cisco Prime Network Registrar 8.2 Features

If IPAM 8.1.2 is used to manage Cisco Prime Network Registrar 8.2, the following features should not be configured in Cisco Prime Network Registrar 8.2 and cannot be used:

1. DNS Views

2. DNS ENUM

Configuring either DNS Views or DNS ENUM objects in Cisco Prime Network Registrar 8.2 will result in failure of DNS deployment tasks in IPAM 8.1.2.

Deprecated Attributes not to be configured in IPAM 8.1.2

There are a number of DHCP/DNS attributes that are deprecated in Cisco Prime Network Registrar 8.2 . If the values for the deprecated attributes are configured in DHCP/DNS server pages of IPAM 8.1.2, the DHCP/DNS deployment tasks will fail. The following list of deprecated attributes should not be configured in IPAM 8.1.2.

DNS Server Configuration Page

The following attributes are deprecated in the DNS Server page of Cisco Prime Network Registrar 8.2. Configuring these attributes in IPAM 8.1.2 will result in failure of the DNS deployment task.

Basic and Advanced Mode Attributes:

auth-db-cache-kbytes
checkpoint-interval (Zone Checkpoint Interval)
fake-ip-name-response (Fake responses for IP address-like names)
hide-subzones (Hide Subzones)
notify-defer-cnt (NOTIFY max. changes to accumulate)

Expert Mode Attributes:

auth-reconnect
check-parent-zone-acl
config-db-checkpoint-interval
config-db-purge-logs-interval
changeset-db-cache-partitions
changeset-db-cache-size
changeset-db-checkpoint-interval
changeset-db-err-log-enabled
changeset-db-heap-size
changeset-db-hist-max-trim-count
changeset-db-history-kept
changeset-db-log-buffer-size
changeset-db-log-size
changeset-db-logs-trimming-interval
changeset-db-max-age
changeset-db-max-rr-size
changeset-db-reads-per-transaction
changeset-db-transaction-interval
checkpoint-min-interval
chset-db-lock-count
do-incr-zone-load
enforce-min-ttl
full-reload-recovery-options
ha-dns-error-handling
ha-dns-failure-detection-timeout
ha-dns-max-connect-timeout
ha-dns-max-frame-size
ha-dns-max-records
ha-dns-max-retries
ha-dns-min-zone-size
ha-dns-serial-gap-delay
ha-dns-wait-between-retries
ha-dns-zonesync-check-interval
ha-dns-zonesync-failed-timeout
hierarchical-alphabetic-rr-ordering
htrim-ddns-between-htrims
htrim-zone-max-hist-allowed
htrim-zone-size-check-interval
htrim-zone-size-to-travel
ixfr-min-zone-size
optimistic-ddns-responses
optimize-zone-lookup
relax-ixfr-query-validation
relax-cname-rules
round-trip-time-limit
synthesize-aaaa-records
use-update-optimization
zone-checkpoint-file-buf-ksize
zone-db-cache-kbytes

In Cisco Prime Network Registrar 8.2, the DNS Server attribute ‘activity-counter-log-settings’ has been split into two attributes as ‘activity-summary-type’ and ‘activity-counter-log-settings’ with the following values as flags. Whereas in previous releases it was a single attribute (activity-counter-log-settings) with all the flags together.

Flags of ‘activity-summary-type’ (Statistics Type) attribute:

sample
total

Flags of ‘activity-counter-log-settings’ (Statistics Settings) attribute:

performance
query
errors
security
maxcounters
ha
ipv6
datastore

In IPAM 8.1.2 if the flags ‘sample’ and ‘total’ are selected for the attribute ‘activity-counter-log-settings’, the DNS deployment task will fail with errors. The remaining flags of this attribute can be set in IPAM 8.1.2 and the configuration can be pushed successfully.

Edit Forward/Reverse Zone Configuration Page

The following attributes and configuration options have been deprecated in the Edit Forward/Reverse zone page of Cisco Prime Network Registrar 8.2. Configuring these attributes in IPAM 8.1.2 will result in failure of the DNS Deployment task.

Basic and Advanced Mode Attribute:

checkpoint-interval
checkpoint-min-interval
dynamic
scvg-ignore-restart-interval
scvg-interval
scvg-max-records
scvg-max-records-searched
scvg-no-refresh-interval
scvg-pause-interval
scvg-refresh-interval

Expert Mode Attributes:

full-reload-recovery-options
name-protection

Edit Secondary Zone Configuration Page

The following attributes have been deprecated from the Edit Secondary zone page in Cisco Prime Network Registrar 8.2. The values for these attributes should not be configured in IPAM 8.1.2, as the DNS deployment task will fail if the values are set.

Basic and Advanced Mode Attributes:

checkpoint-interval
checkpoint-min-interval

Expert Mode Attributes:

full-reload-recovery-options

HA DNS Pair Configuration Page

As part of implementing some DNS Database Enhancements in Cisco Prime Network Registrar 8.2, the following HA-DNS attributes are moved from the DNS Server page to the HA Pairs page. If the DNS HA Pair of Cisco Prime Network Registrar 8.2 is managed by IPAM 8.1.2 it is advised that the following attributes should not be configured in the DNS Server page of IPAM 8.1.2 as the DNS Deployment task will fail.

Expert Mode Attributes:

ha-dns-error-handling
ha-dns-failure-detection-timeout
ha-dns-max-connect-timeout
ha-dns-max-frame-size
ha-dns-max-records
ha-dns-max-retries
ha-dns-min-zone-size
ha-dns-serial-gap-delay
ha-dns-wait-between-retries
ha-dns-zonesync-check-interval
ha-dns-zonesync-failed-timeout

DHCP Server page

The following attributes are deprecated from the DHCP Server page as part of DHCPv6 failover feature in Cisco Prime Network Registrar 8.2. If the values of these attributes are set in IPAM 8.1.2 the DHCP deployment task will fail.

Basic and Advanced Mode Attributes:

ip-history-detail
	failover-bulking
failover-poll-interval
failover-poll-timeout

Expert Mode Attributes:

failover
failover-allow-ack-on-update
failover-remote-port
failover-update-retry-time
failover-control-retry-time
failover-update-retry-count
failover-control-retry-count
failover-send-batch-updates
failover-skip-ack-on-update
udp-send-packet-size

The DHCP Server attribute ‘Enabled Traps’ has two new flags (address6-conflict & prefix6-conflict) added to it as part of DHCPv6 Failover in Cisco Prime Network Registrar 8.2. If the Failover-Pair of Cisco Prime Network Registrar 8.2 is managed by IPAM 8.1.2 then the new flags added in the ‘Enabled Traps’ attribute cannot be enabled in the DHCP Server Page.

DNS Deployment task

In IPAM 8.1.2 and in previous releases, when the DNS Deployment task is performed, the user can select the ‘Overwrite Zones’ option if the entire zone data in Cisco Prime Network Registrar has to be replaced with new zone data from IPAM.

If Cisco Prime Network Registrar 8.2 is managed by IPAM 8.1.2, it is advised that the option ‘Overwrite Zones’ should not be selected during the DNS Deployment task as it will result in failure of the task.

Summary

All the supported features of IPAM 8.1.2 will work correctly with Cisco Prime Network Registrar 8.2 if the ‘cnrsdk’ folder or subdirectory on the IPAM 8.1.2 Remote Agent is updated as described above.

The following new features of Cisco Prime Network Registrar 8.2 can be used in a Cisco Prime Network Registrar 8.2 installation managed by IPAM 8.1.2:

1. CDNS Domain Redirect

2. DHCID RR Support

3. DHCPv6 Dynamic Lease Notification

4. DHCPv6 Failover (Except for the limitation in section 4.2.5 regarding ‘Enabled Traps’ attribute)

5. Enhanced Web UI

Related Information

• Cisco Prime Network Registrar Documentation