Upgrading Cisco Prime Optical in an High Availability Environment Using the Data Migrator Wizard
This chapter describes how to use the Cisco Prime Optical 10.5 Data Migrator wizard to migrate select data from CTM R8.5 or later to Prime Optical 10.5. With the wizard, you can migrate a subset of an existing database to a newly installed Prime Optical 10.5 server.
The following are the benefits and limitations of the Data Migrator wizard:
- Reduces the migration time and provides a safer, easier migration.
- Lets you migrate the following data:
–
Core tables and database pruning policy information.
–
Service states and configurations, including CORBA and SNMP gateway states and configurations.
–
Users, user profile information, and CORBA and SNMP gateway users.
–
(Optional) Managed NEs, NE logical grouping information, network partition information, security information to authenticate to nodes, Domain Explorer and Subnetwork Explorer map coordinates, basic NE service configuration, and PM service states.
–
(Optional) Manual links and Layer 1 circuits with user data.
–
(Optional) VLAN customer-related information, Layer 2 topologies, and QoS templates.
–
(Optional) Alarm Log Data
- Does not migrate PM data.
As the root user, install and run the tool on the same server where the Prime Optical database is installed.
The tool prepares a newly installed Prime Optical 10.5 server to use the data as used in the earlier server.
Caution
You cannot migrate and preserve your
entire database. You can only migrate a
subset of your database by using the Data Migrator wizard.
Note
In the bottom right corner of the wizard screens, the memory footprint progress bar shows the rate of available memory compared to the allocated memory; for example: “Available: x MB of y MB.” The “Request garbage collection” tool lets you free up memory when the amount of data is greater than what is expected, and the running task is taking too long to complete.
This chapter contains the following sections:
Overview of the Upgrade Process Using the Data Migrator Wizard
Using the Data Migrator wizard to upgrade from CTM 8.5, 9.0, 9.1, 9.2, 9.3, 9.3.1, 9.5, 9.5.1, 9.6, 9.8 or 10.0 to Prime Optical 10.5 involves the following process:
1.
Perform a full backup or export of your earlier database.
2.
Install the Data Migrator wizard on any server in the same network as the Prime Optical server. (See Installing the Data Migrator Wizard.)
3.
Export the database from the previous CTM or Prime Optical release server that you want to upgrade. (See Using the Data Migrator Wizard to Export the Database.)
4.
Install Prime Optical HA 10.5 from scratch. (See Chapter3, “Installing the Cisco Prime Optical High Availability Solution in a Single-Node Geographical Redundancy Configuration on a Linux Server”)
Caution Before you install the operating system from scratch, save the.zip export archive on another server.
5.
Import the database to the new Prime Optical 10.5 database. (See Using the Data Migrator Wizard to Import Your Data.)
Installing the Data Migrator Wizard
As the root user, do the following:
Step 1
Insert one of the following USB drive based on your configuration, in your workstation:
Cisco Prime Optical Server installation USB drive—Linux
Note Wait for the automatic discovery of the device.
Enter the following command for Linux only if the device is not automatically discovered.
mount -t ext3 <USB device> /media/<USB-mount-point>
For example:
mount -t ext3 /dev/sdd1 /media/<USB-mount-point>
Step 2
Enter the following commands to mount the ISO image:
For Linux, enter:
cd /media/<USB-mount-point>/PrimeOptical_10_5
mount -o loop PRIME_OPTICAL_10_5_LNX.iso /mnt
The output is displayed as follows:
/dev/lofi/ N
To mount the iso image, enter the command:
mount -F hsfs </dev/lofi/N> /mnt
Note
You can also replace the /mnt directory with a different mount point. Sometimes Cisco will create a software update (patch) for a Prime Optical release. If you install a patch at a later date, be sure to install the latest Data Migrator tool. To install the latest tool, go to the Download Software page (http://www.cisco.com/cisco/software/navigator.html?mdfid=283812777&i=rm) and navigate to the latest Prime Optical 10.5 release. Select and download the appropriate Data Migrator configuration (LINUX), extract the DataMigrator.tar file, then proceed to Step 5.
Step 3
Copy the /mnt/DataMigrator/DataMigrator.tar file to a local folder.
Step 4
Enter the following commands to extract the.tar archive contents:
cd local-folder/DataMigrator
Step 5
Enter the following commands to run the installer:
Step 6
In the Introduction screen, click Next.
Step 7
At the Choose Installation Folder screen, specify where you want to install the Data Migrator wizard. The default folder is $HOME/DataMigrator. You can click Choose to choose a different destination. After you specify your destination, click Next.
Step 8
The Preinstallation Summary screen shows the items that will be installed and the disk space required. Click Install.
Step 9
The Installing Data Migrator screen tracks the progress of the installation.
Step 10
The Installation Complete screen summarizes the results of the installation. Click Done.
After installation, the directory structure contains a folder with the DataMigrator executable script.
Using the Data Migrator Wizard in a Geographic Redundancy, HA Environment on Linux
Step 1
Stop the server that is running on the active node.
Step 2
Enter the following command:
Step 3
Use the Data Migrator wizard to export the database. See Using the Data Migrator Wizard to Export the Database.
Step 4
Save the.zip file generated by the Data Migrator wizard, and any other important files, to a different server.
Step 5
Reinstall Prime Optical HA 10.5 as a completely new installation. Follow the steps in Chapter4, “Installing the Cisco Prime Optical High Availability Solution in a Local Redundancy Configuration on a Linux Server”
Step 6
Freeze the Clusvcadm -Z ctm_service.
Step 7
Enter the following command to stop Prime Optical:
Step 8
Enter the following commands to perform a full export of the database. (At this point, the database is empty, but retaining an export can save time if the import fails during the next step.)
cd /cisco/CiscoTransportManagerServer/bin
Step 9
Use the Data Migrator wizard to import the export.zip file to the newly installed server. See Using the Data Migrator Wizard to Import Your Data.
Step 10
Enter the following command to start Prime Optical:
Step 11
Connect to a Prime Optical client and verify that Prime Optical is running correctly.
Step 12
Unfreeze the primary cluster by entering the following command:
Using the Data Migrator Wizard in a Dual-Node Cluster, Local Redundancy, HA Environment on Linux
Step 1
Freeze the primary cluster by executing the following command:
Step 2
Stop the server on the primary node by executing the following command:
Step 3
Use the Data Migrator wizard to export the database. See Using the Data Migrator Wizard to Export the Database.
Step 4
Save the.zip file generated by the Data Migrator wizard and any other important files to a different server.
Step 5
Reinstall Prime Optical HA 10.5 as a completely new installation. Follow the steps in Chapter3, “Installing the Cisco Prime Optical High Availability Solution in a Single-Node Geographical Redundancy Configuration on a Linux Server”
Step 6
Freeze the Clusvcadm -Z ctm_service.
Step 7
Stop the Prime Optical server by executing the following command:
Step 8
Enter the following commands to perform a full export of the database. (At this point, the database is empty, but retaining an export can save time if the import fails during the next step.)
cd /cisco/CiscoTransportManagerServer/bin
Step 9
Use the Data Migrator wizard to import the export.zip file to the newly installed server. See Using the Data Migrator Wizard to Import Your Data.
Step 10
Enter the following command to start the Prime Optical server:
Step 11
Connect to a Prime Optical client and verify that Prime Optical is running correctly.
Step 12
Unfreeze the primary cluster by executing the following command:
Step 13
Freeze the cluster executing the following command:
Using the Data Migrator Wizard to Export the Database
Step 1
Enter the following command to verify whether the Prime Optical server is running:
If the Prime Optical server is running, enter the following command to stop it:
Step 2
Navigate to the installation folder (for example, /tmp/DataMigrator/bin) and run the DataMigrator executable.
Step 3
The Data Migrator wizard opens. Do the following:
a.
(Optional) To view the supported versions that are available for export, click Show Migration Matrix. The Supported Migration Paths dialog box opens, listing the valid migration versions. After reviewing the supported migration paths, click Close.
b.
From the Migration Mode drop-down list, choose Export.
c.
Click OK.
Note
For Embedded database, the Oracle SID is CTM for 8.5 through 9.6.3 and optdb for 10.5.
Step 4
In the Database Connection screen, specify details of the database from which you want to export data.
Step 5
Click Connect. The progress bar at the bottom of the screen tracks the progress of the operation. (To cancel the operation, click the X icon to the right of the progress bar.)
After the connection succeeds, the Connection State area shows the state as “Connected.” The version, size, and installed modules are retrieved from the database and displayed.
Step 6
Click Next.
Step 7
If you receive the following prompt, shut down the server and reconnect to the database and then click OK :
The server is still running on the selected server. The connection to the database will be closed. Before continuing, you must shut down the server and then reconnect to the database.
Caution It is important that you shut down the server and reconnect to the database before proceeding to the next step.
Step 8
In the Categories screen, review the data categories that will be exported. Click Next.
Step 9
In the Open dialog box, select the directory and the.zip archive where you want to store the exported data and then click Open.
Step 10
The File Selection screen displays the selected archive file and the estimated time to complete the export process. Click Next.
Step 11
In the Export screen, click Start. All data categories are exported and compressed.
A progress bar tracks the progress of the export. You can quit exporting at any time by clicking the X button next to the progress bar.
The table summarizes the results of the export. For each data category, the table lists the exported database tables, the number of rows exported, and the length of time the export took.
Step 12
Click Exit.
Step 13
At the prompt “The operation is complete,” click OK.
Using the Data Migrator Wizard to Import Your Data
Step 1
Enter the following command to verify whether the server is running:
Step 2
If the server is running, enter the following command to stop it:
Step 3
Navigate to the installation folder (for example, /tmp/DataMigrator/bin) and run the DataMigrator executable.
Step 4
The Data Migrator wizard opens. Do the following:
a.
(Optional) To view the supported versions that are available for import, click Show Migration Matrix. The Supported Migration Paths dialog box opens, listing the valid migration versions. After reviewing the supported migration paths, click Close.
b.
From the Migration Mode drop-down list, choose Import.
c.
Click OK.
Step 5
In the Open dialog box, select the.zip archive file to import and then click Open.
Step 6
In the Archive Summary screen, review the details of the archive file to import. To select a different archive file to import, click the browse (...) button. The table summary shows the database tables that will be imported, including the data category and the number of rows in each table. Click Next.
Step 7
In the Categories screen, do the following:
a.
Select the categories to import. General, Services, and Users are mandatory categories; the NEs, L1, and L2 topology, and Alarm Log categories are optional.
b.
(Optional) In the General category, click the Setup link to open the General Import Options dialog box. If desired, check the Import pruning options check box and then click Apply. The dialog box closes.
c.
(Optional) In the NEs category, click the Setup link to open the NE Import Options dialog box and specify additional setup options for the import. The dialog box has the following tabs:
–
NE Services—Lets you tune the NE services of the target server after the import.
–
NEs—Lets you change the NE state and disable automatic subnetwork grouping. (Automatic subnetwork grouping slows down the initial discovery of the new server.)
–
Miscellaneous—Lets you customize the import of user maps and equipment inventory notes.
After making your selections in the NE Import Options dialog box, click Apply. The dialog box closes.
d.
Click Next.
Step 8
In the Database Connection screen, specify details of the database to which you want to import data. Do the following:
a.
If the release to which you want to import data has an embedded database, check the Server uses an embedded database check box.
When the Server uses an embedded database check box is checked:
–
You cannot edit any fields in the Connection Properties area.
–
The hostname is set to the current machine’s name.
–
The instance name is set to CTM, which is the default for an embedded database and can be changed.
–
The port number is set to 1521, which is the default for an embedded database and cannot be changed.
–
The Username and Password fields are cleared. After you click the Connect button, the Username and Password fields are filled in if the Data Migrator wizard can find those properties in the CTMServer.cfg configuration file.
b.
If the release to which you want to import data does not use an embedded database, verify that the Server uses an embedded database check box is unchecked.
When the Server uses an embedded database check box is unchecked:
–
You can edit all fields in the Connection Properties area.
–
The Username and Password fields are restored to their default values.
–
You must enter a hostname in the Hostname field.
–
You must enter a port number in the Port Number field. The default port number is 1521.
–
You can either enter values in the remaining fields, or accept the defaults.
c.
Click Connect.
The progress bar at the bottom of the screen tracks the progress of the operation. (To cancel the operation, click the X icon to the right of the progress bar.)
After the connection succeeds, the Connection State area shows the state as “Connected.” The version, size, and installed modules are retrieved from the database and displayed.
d.
Click Next.
Step 9
If you receive the following prompt, shut down the server and reconnect to the database and then click OK :
The server is still running on the selected server. The connection to the database will be closed. Before continuing, you must shut down the server and then reconnect to the database.
Caution It is important that you shut down the server and reconnect to the database before proceeding to the next step.
Step 10
In the Validation screen, do the following:
a.
Click the Start button to validate the size, installed modules, and data on the selected destination server. The Result field shows whether the validation succeeded (Allowed) or failed (Impossible).
The following server sizes produce the following results:
Table 5-1 Server Size Results
|
|
|
Small |
Small |
Allowed |
Small |
Medium |
Allowed |
Small |
Large |
Allowed |
Small |
High end |
Allowed |
Medium |
Small |
Impossible |
Medium |
Medium |
Allowed |
Medium |
Large |
Allowed |
Medium |
High end |
Allowed |
Large |
Small |
Impossible |
Large |
Medium |
Impossible |
Large |
Large |
Allowed |
Large |
High end |
Allowed |
High end |
Small |
Impossible |
High end |
Medium |
Impossible |
High end |
Large |
Impossible |
High end |
High end |
Allowed |
Small |
Small |
Allowed |
Small |
Medium |
Allowed |
b.
In the Data Validation area > Details column, click the Details link to see why a particular table could not be imported. At the following prompt, click OK :
Table-name must be empty; it contains x row(s) instead.
Note
To avoid this error, click Back, return to the Validation screen, and select a different server that has a new Prime Optical 10.5 installation.
c.
Click Next.
Step 11
In the Import screen, click the Start button to import the data to the target database.
Step 12
The confirmation popup reminds you that if you have not done so already, you should run the export_full_db.sh script to make a backup copy of your current data before proceeding. (Without a backup copy of your data, you would need to completely reinstall the Prime Optical server if problems were to occur.) Click Yes at the following prompt:
This action will write the selected data to the target database.
Make a copy of the current data using the export_full_db.sh tool.
Select Yes to proceed or No to cancel the operation.
Step 13
A progress bar tracks the progress of the import. (To cancel the operation, click the X icon to the right of the progress bar.)
The table summarizes the results of the import. For each data category, the table lists the imported database tables, the result of the housekeeping phase (purging old data to make room for the new data), the result of the data migration phase, and the length of time the import took.
Caution If a database table was not imported, click the
Details link to show the reason for the failure. If errors occurred during the import, use the import_full_db.sh script to reimport the Prime Optical database. See the
Cisco Prime Optical 10.5 User Guide section “Restoring the Prime Optical Database from the Previous Backup.”
Step 14
Click Exit.
Uninstalling the Data Migrator Wizard
To uninstall the Data Migrator wizard, delete the folder where you installed the wizard. The default folder is $HOME/DataMigrator.