This guide may be used for any network operator considering migrating or upgrading to version 8.x of Cisco Prime Network Registrar, Cisco's solution for integrated, scalable, reliable Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), and IP address management (IPAM).
Cisco has simplified the process of migration/upgrading to help ensure a seamless transition with minimal impact on network operation. This tool presents the straightforward migration path and provides guidelines by Cisco Network Registrar release number for operating system, VMware, Java, and browser versions, as well as hardware specifications, upgrade rules, and other considerations to keep in mind.
OS Release
Solaris
Intel
Red Hat (RH)
VMware
Java
Browser
Memory
Disk
Upgrade Rules
Notes
5.0
Solaris 2.6, 7, or 8
NT 4.0
512 MB minimum
Upgrade to 6.1.6
5.5
7 or 8
NT 4.0 SP6
RH 6.2 (kernel version 2.2)
512 MB minimum
Upgrade to 6.1.6
6.0
8 or 9
Win 2000 SP2, NT 4.0 SP6a
RH Linux 7.3 (kernel version 2.4) with RPM Package Manager (RPM) 4.0.4
JRE 1.4.2
IE 6.0 SP2, Firefox 1.0, Netscape 7.0
4 GB RAM
Upgrade to 6.1.6
6.1
8 or 9
Win 2000 SP2
RH Linux 7.3 (kernel version 2.4) with RPM 4.0.4 or RH Linux Enterprise (RHLE) or WS 2.1 (kernel 2.4.9-e.24)
JRE 1.4.2
IE 6.0 SP2, Firefox 1.0, Netscape 7.0
4 GB RAM
Upgrade to 6.1.6
6.1.1
8 or 9
Win 2000 SP2
RH Linux 7.3 (kernel version 2.4) with RPM 4.0.4 or RHLE ES or WS 2.1 (kernel 2.4.9-e.24)
JRE 1.4.2
IE 6.0 SP2, Firefox 1.0, Netscape 7.0
4 GB RAM
Upgrade to 6.1.6
6.1.6
8 or 9
Win 2000 SP2
RH Linux 7.3 (kernel version 2.4) with RPM 4.0.4 or RHEL ES or WS 2.1 kernel (2.4.9-e.24)
JRE 1.4.2
IE 6.0 SP2, Firefox 1.0, Netscape 7.0
4 GB RAM
Upgrade to 6.3.2.2
6.2
9 or 10
XP or Win 2003 Server
RH Enterprise Server (RHES) 3.0
JRE 1.4.2
Internet Explorer (IE) 6.0 SP2, Firefox 1.0, Netscape 7.0
4 GB RAM
Upgrade to 6.3.2.2
6.3
9 or 10
Win 2003 Server
RHES 4.0
JRE 1.4.2
IE 6.0 SP2, Firefox 1.5, Netscape 7.0
4 GB RAM
Upgrade to 6.3.2.2
6.3.2.1
9 or 10
Win 2003 Server
RHES 4.0
JRE 1.4.2
IE 6.0 SP2, Firefox 1.5, Netscape 7.0
4 GB RAM
Upgrade to 6.3.2.2
6.3.2.2
9 or 10
Win 2003 Server
RHES 4.0
JRE 1.4.2
IE 6.0 SP2, Firefox 1.5, Netscape 7.0
4 GB RAM
Upgrade to 8.0
If upgrade is done to both partners (High Availability [HA] and/or Failover), resource records and leases are synchronized at this point
7.0
10
Win 2003 Server
RHES 4.0
JRE 5.0 (1.5.0_06)
IE 6.0 SP2, Firefox 1.5, Netscape 7.0
4 GB RAM
Upgrade to 8.0
As documented in the Cisco Prime Network Registrar 8.0 Install and Upgrade Guide
7.1
10
Win 2003 Server
RHES 4.0 or RH Enterprise Linux (RHEL) 5
JRE 5.0 (1.5.0_06)
IE 6.0 SP2 and 7.0, Firefox 2.0 and 3.0
4 GB RAM
Upgrade to 8.0
7.2
10 (32 bit or 64 bit)
Win 2008 R2
RHEL 5.0
ESXi 4.1
JRE 5.0 (1.5.0_06)
IE 7.1 and 8.0, Firefox 3.0 and 3.5
4 GB RAM
(2) 146GB 15K RPM RAID 1
Upgrade to 8.0
Any release earlier than 7.2 requires running the database upgrade tool that is available in the Cisco Network Registrar 7.2 product download directory under "Network Registrar Tools"
8.0
10
Win 2008 R2
RHEL 5.0 or 6.0
ESXi 4.1
JRE 5.0 (1.5.0_06)
IE 8.0, Firefox 5 and 6
4G-8G-16G
(2) 146GB 15K RPM RAID 1
General Rules
Do not copy a database from one operating system to another.
DHCP Migration Hints
Migrate DHCP prior to migrating DNS in an environment where both servers are in use.
Use DHCP failover functionality to facilitate the migration. To migrate, synchronize existing the configuration with a new backup partner on the target OS. Once failover has started, it will synchronize the DHCP leases with the new backup partner. Migrating in this way minimizes problems, as you can always go back to the original system (fallback) if the new backup gets corrupted.
Subsequent to successful migration to the new partner, reverse the process to update the other new partner.
DNS Migration Hints
Use DNS HA functionality to facilitate DNS migration.
Synchronize the existing (main) configuration with the new system as the backup platform. Once HA is started it will synchronize the resource records with the new partner. Migrating in this way minimizes problems, as you can always go back to the original system (fallback) if the new backup gets corrupted.
Subsequent to successful migration to the new system, reverse the process to update the other new partner.
