Cisco Cisco Prime Network Registrar 8.3 Installation Guide
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Cisco Prime Network Registrar IPAM 8.3 Upgrade Guide
19
my.cnf file that are desired. Do not overwrite this file with the backup copy. Also, you may
need to confirm your original customizations to the new format of the file.
Any customizations to MySQL that were made dynamically and not via the my.cnf/my.ini file
will have to be done again on the new MySQL database if they are still desired. This procedure
need to confirm your original customizations to the new format of the file.
Any customizations to MySQL that were made dynamically and not via the my.cnf/my.ini file
will have to be done again on the new MySQL database if they are still desired. This procedure
is not recommended. All database configurations should be made in the my.cnf file. Before
the upgrade, you may use the ‘SHOW STATUS;’ command in MySQL to compare the
the upgrade, you may use the ‘SHOW STATUS;’ command in MySQL to compare the
differences between the output and what’s defined in the my.cnf file.
6.2 Database Credentials
If your database resides on a separate system from the Executive server system, or if you’ve
changed the database username and password for the IPAM database from its default value,
then you will need to modify INCHOME/classes/jdbc.properties. Again, the automatic
then you will need to modify INCHOME/classes/jdbc.properties. Again, the automatic
upgrade script attempts to carry forward these changes. Compare the old version of this file
with the new version, and if the values are different, make sure the new file is modified to
with the new version, and if the values are different, make sure the new file is modified to
retain your old values. The parameter names may be slightly different. Do not overwrite this
file with the backup copy.
file with the backup copy.
6.3 Custom Callout Manager Routines
If you had configured Callout Manager to execute a script when a specific function takes
place, then you may need to restore those scripts.
If your custom scripts resided under the IPAM directory tree, the automatic upgrade will try
carrying them forward to your new IPAM 8.3 Installation.
Verify the new INCHOME/callout_manager.properties. Make changes as necessary. Do not
overwrite this file with the backup copy. The backup copy of this file will be helpful for
place, then you may need to restore those scripts.
If your custom scripts resided under the IPAM directory tree, the automatic upgrade will try
carrying them forward to your new IPAM 8.3 Installation.
Verify the new INCHOME/callout_manager.properties. Make changes as necessary. Do not
overwrite this file with the backup copy. The backup copy of this file will be helpful for
restoring which functions you had previously set, as well as the path locations to the custom
scripts being called. Those custom scripts should be copied from the backup directory to the
scripts being called. Those custom scripts should be copied from the backup directory to the
new installation directory, if they were not copied automatically.
After callout_manager.properties has been modified, double-check the new Tools > System
After callout_manager.properties has been modified, double-check the new Tools > System
> Policies and Options menu in IPAM 8.3 to make sure the desired callout policies are still
enabled.
enabled.
6.4 Custom mysqlexport script
You may have modified your old /opt/incontrol/etc/mysqlexport.sh file (on UNIX only) to
be more specific to your environment. Compare the old version of this file with the new
version and, if they are different, make sure the new file is modified to conform to your old
version and, if they are different, make sure the new file is modified to conform to your old
settings. Do not overwrite this file with the backup copy.