Cisco Cisco Prime Network Registrar 8.3 Installation Guide
Cisco Prime Network Registrar IPAM 8.3 Upgrade Guide
7
2 Upgrading a Linux Executive
This section describes the steps for upgrading IPAM to version 8.3 on a Linux system.
Before you begin the upgrade procedure, the IPAM services on the Executive and/or Agent
system must be running. During this procedure the services will be stopped. On an Executive
Before you begin the upgrade procedure, the IPAM services on the Executive and/or Agent
system must be running. During this procedure the services will be stopped. On an Executive
system, the schema will be modified (MySQL and Oracle). A database backup will be saved
automatically for local MySQL users. Oracle and remote MySQL users must backup their
automatically for local MySQL users. Oracle and remote MySQL users must backup their
data manually before proceeding because the current data will be modified. Oracle users, you
may also want to run “PURGE RECYCLEBIN;” against your IPAM database, prior to the
may also want to run “PURGE RECYCLEBIN;” against your IPAM database, prior to the
upgrade procedure, to prevent errors during the schema update phase of the upgrade.
2.1 Step 1: Obtain your IPAM 8.3 License Key
Call the Cisco Technical Assistance Center (TAC) and ask for the Licensing Team to request a
license key that is compatible with IPAM 8.3. For your local Cisco TAC phone number, see
the Cisco Worldwide Contacts page at:
the Cisco Worldwide Contacts page at:
. After the
upgrade completes successfully, upon logging into IPAM 8.3 for the first time, the new 8.3
license key must be entered to access the product. Your existing keys will not work with
version 8.3. Do not proceed without a new 8.3 License Key or your setup will become
version 8.3. Do not proceed without a new 8.3 License Key or your setup will become
inaccessible.
2.2 Step 2: Verify Free Space
The upgrade procedure requires the following amount of free space in order to run
successfully:
successfully:
3 x DB Size + 5GB
The current DB Size can be obtained using the “du” command, e.g.
du –sh /opt/incontrol/mysql/data
3.1G /opt/incontrol/mysql/data
In this example, the database occupies 3.1GB of space, so the total free space required will be
14.3 GB. The value you come up with does not represent the final amount of space used, but
14.3 GB. The value you come up with does not represent the final amount of space used, but
only the amount of space needed for upgrade flexibility.