Cisco Cisco Prime Network Registrar 8.3 Installation Guide



If your IPAM 8.1.1, 8.1.2 or 8.1.3 environment was customized in any way, you’ll need to go 

through some areas in 8.3 to make sure that the settings were carried forward after the 
upgrade. The upgrader is designed to handle common changes, but it’s still best to verify all of 

your customizations manually for continuity. 
If you used the Automatic upgrader, review the end of the upgrade-<datestamp>.log file in 

the directory where you launched the upgrade (/tmp or C:\tmp). This log file will recommend 
files which it believes are different than the default setup. If it states “Additional action may be 

required”, it is up to you to make the final determination if the differences are still needed in 
the new IPAM version, and then make those modifications manually, if desired. Do not 

overwrite any new files with its backup copy. Since some default IPAM files have changed 
slightly between versions, this check filter may pick up those differences and can likely be 

ignored if you do not remember making changes to a particular file. If you are unsure, please 
contact the Technical Assistance Center. 
After the upgrade, check your new IPAM 8.3 file structure for filenames that end with -
<datestamp>. These files are from your IPAM 8.1.1, 8.1.2 or 8.1.3 environment where IPAM 

suspect’s customizations were made. They have been copied to the new structure to allow for 
easy comparison. Once you’ve finished reviewing these files and finalizing your 

customizations into the new version of the file, feel free to remove the file(s) containing “-
<datestamp>” in the name under the /opt/incontrol or C:\Program Files (x86)\Cisco\Cisco 

Prime Network Registrar IPAM structure. On Unix, a complete backup of your IPAM 8.1.1, 
8.1.2 or 8.1.3 files can be found under the /opt/incontrol-<datestamp> directory. On 

Windows, the upgrader will only retain the DNS config and zone files and IPAM config and 
properties files in C:\tmp\backup-<datestamp>. 
For those who have upgraded manually, you will need to compare any custom files from the 
IPAM 8.1.1, 8.1.2 or 8.1.3 backup directory that you created. 
 

If you’ve made any customizations to your MySQL database in your old environment, you will 

have to verify those same changes in your new installation. The upgrade script attempts to 
carry your changes forward, but the version of MySQL has changed from 5.6.17 to 5.6.28. 

Verify the contents of the my.cnf file found under /opt/incontrol/mysql or C:\Program Files 
(x86)\Cisco\Cisco Prime Network Registrar IPAM \mysql and enter any changes in the new