Data Migration Guide for CiscoWorks LAN Management Solution 2.5.1 - Chapter 2: Migration Data to LAN Management Solution 2.5.1 on Solaris [CiscoWorks LAN Management Solution]

Table Of Contents

Migrating Data to
LAN Management Solution 2.5.1 on Solaris

Migrating Data From LMS 2.1/LMS 1.2/RWAN 1.2

Local Migration From LMS 2.1/LMS 1.2/RWAN 1.2

Remote Migration From LMS 2.1/LMS 1.2/RWAN 1.2

Migrating Data From LMS 2.2/LMS 1.3/RWAN 1.3

Local Migration From LMS 2.2/LMS 1.3/RWAN 1.3

Remote Migration From LMS 2.2/LMS 1.3/RWAN 1.3

Understanding LMS Backup Files Created During CS Installation

Migrating Data to
LAN Management Solution 2.5.1 on Solaris

This chapter describes the steps involved in migrating data to CiscoWorks LAN Management Solution (LMS) 2.5.1 on Solaris.

This chapter has the following sections:

•Migrating Data From LMS 2.1/LMS 1.2/RWAN 1.2

•Migrating Data From LMS 2.2/LMS 1.3/RWAN 1.3

Migrating Data From LMS 2.1/LMS 1.2/RWAN 1.2

This section explains how to migrate data from LMS 2.1/LMS 1.2 and RWAN 1.2 components to LMS 2.5.1.

Note LMS 1.2 has all the LMS 2.1 applications except DFM.

Figure 2-1 Migrating Data from LMS 2.1/LMS 1.2/RWAN 1.2

* Real-Time Monitor (RTM) and Access Control List Manager are not part of LMS 2.5.1.

If you have installed CiscoWorks Routed WAN Management Solution (RWAN) 1.2 and LMS 2.1 on the same server, you may also have the RWAN 1.2 components such as ACL Manager (ACLM) 1.4 and Internetwork Performance Monitor (IPM) 2.4 on your system.

Caution If you are upgrading your operating system to Solaris 9 (Solaris 2.9), upgrade DFM before upgrading the OS.

You can migrate to LMS 2.5.1 in two ways—Local Migration or Remote Migration. For details, see "Understanding Terms Used in the Data Migration Guide" section on page 1-5.

Note We recommend that you use Remote Migration to migrate to LMS 2.5.1.

Figure 2-2 describes the steps involved in migration from LMS 2.1/RWAN 1.2 to LMS 2.5.1.

Figure 2-2 Steps for Migration from LMS 2.1/LMS 1.2/RWAN 1.2

Local Migration From LMS 2.1/LMS 1.2/RWAN 1.2

To migrate data on the same machine:

Step 1 Login as root to the machine where LMS is installed.

Step 2 Verify that your operating system is supported by LMS 2.5.1. For details on OS platforms supported by LMS 2.5.1, see "System Requirements" section on page 1-5.

Caution If you are upgrading your operating system to Solaris 9 (Solaris 2.9), upgrade DFM before upgrading the OS.

Step 3 Install Common Services 3.0.3.

CS 3.0.3 installer prompts you for a backup directory during local migration, and automatically does a backup. The automatic backup facility only backs up data for CS, RME, Campus Manager and DFM. It does not back up the data for IPM.

Step 4 Install the required LMS applications.

Note We recommend that you upgrade all the applications which were present in LMS 2.1/RWAN 1.2.

When you uninstall RME 3.4.x, dependent applications such as ACLM and VPN Monitor are also uninstalled.

At the end of RME installation, the following warning message appears. You may ignore them.

=======- Possible Warnings/Errors Encountered - =======

WARNING: Please install/upgrade all the required apps

WARNING: in the bundle and then run the migration scripts

[...]

==========================================================

Data for Common Services, Campus Manager, and IPM are automatically migrated when you install the respective applications. To restore RME and DFM data, you must run the restorebackup.pl script.

Step 5 If you are upgrading RME and/or DFM, stop the daemon manager by entering:

/etc/init.d/dmgtd stop

Step 6 Restore LMS 2.1 data by entering:

NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP -gen generationNumber-t temporary_directory

For more details, see "Syntax and Usage for Restore and Backup Script" section on page B-1.

Data for all applications except IPM are migrated now. The restorebackup.pl script overwrites the already existing data for CS, RME, CM, and DFM.

If there is a mismatch in the applications installed and the applications in the backup archive, the following warning messages appear. You may ignore them.
WARNING: There is a mismatch between the list of applications 
installed in this machine and the list of applications present in the 
backup archive. The application data from the backup archive will get 
restored only if that application is installed in this machine. Do you 
want to continue the Restore operation?  (y-continue or n-quit, y/n)?y 
Applications to be restored are............ : [Common Services] [Campus Manager] [Resource Manager Essentials] [Device Fault Manager]

Step 7 Examine the log file in the following location to verify that the database was restored.

The location is /var/adm/CSCOpx/log/restorebackup.log

Step 8 If you stopped the daemon manager in Step 5, restart it by entering:

/etc/init.d/dmgtd start

Remote Migration From LMS 2.1/LMS 1.2/RWAN 1.2

To migrate data on a remote machine:

Step 1 Login as root to the machine with LMS where the older applications are installed.

Step 2 Back up your LMS data.

a. Back up CS, RME, CM, and DFM data by:

•Entering the following command:

NMSROOT/bin/perl NMSROOT/bin/backup.pl BKP num_generations

where num_generations is the maximum backup generations to be kept in the backup directory

If BKP is the backup directory, the data is stored in the directories BKP/0, BKP/1, and BKP/2 etc., where BKP/n stores the data of the (n+1)th generation.

Or

•Using the CD One, Fifth Edition Administration GUI (Server Configuration > Administration > Database Management > Back Up Data Now). Click Help, and follow the instructions to back up your data.

b. If you are upgrading IPM, create the necessary backup files.

To take backup, run RBackup.sh from the IPM 2.6 CD-ROM root directory.

This stops all IPM servers that are running and takes a backup of the database, the seed files, the environment variables, and the version information.

While running RBackup.sh, you are prompted to specify the backup directory. However, the default backup directory is /opt. The data is compressed and the ipmBackup.tar file is created in the specified directory.

Step 3 Login as root into the remote machine where you want to install LMS 2.5.1.

Step 4 Install LMS 2.5.1 applications in the remote machine. You must first install Common Services (CS 3.0.3), then the other LMS applications.

Step 5 If you are upgrading to DFM 2.0.3, assemble the files needed for the DFM migration:

a. Copy the DFM 2.0.3 Upgrade Kit from the remote DFM 2.0.3 image to your local DFM 1.2.x host. The upgrade kit contains the DFMMigrate.pl script and other required files.

In the following command, NMSROOT is the remote DFM 2.0.3 installation directory (by default, /opt/CSCOpx), and dir is a directory on your local DFM 1.2.x host.

NMSROOT/bin/cw-dfm-20-UpgradeKit-sol.zip dir

b. Locate your copy of the 1.2.x DFM.rps file, normally located in NMSROOT/objects/smarts/repos/icf/DFM.rps.

If you plan to use a copy of this file that was created during a backup, the file will be located in the backup directory you specified when using CiscoWorks Common Services or CiscoWorks 2000 CD One.

c. Make sure the DFM.rps file is named DFM.rps, otherwise Step 5 d.will fail.

Caution For DFM users, if you plan to upgrade your operating system from Solaris 8 (Solaris 2.8) to Solaris 9 (Solaris 2.9), you need to run the DFMMigrate.pl script (in the DFM 2.0.3 upgrade kit) on Solaris 8 (Solaris 2.8), before migrating your operating system for the remote upgrade.

d. Use the DFMMigrate.pl script to create the required migration files.

–Move to the directory into which you copied the cw-dfm-20UpgradeKit-sol.zip file.

–Unzip the file. It creates a directory called cw-dfm-20-UpgradeKit-sol.

–Run the DFMMigrate.pl script:
NMSROOT/bin/perl script dir/cw-dfm-20-UpgradeKit-sol/smarts/ 
DFMMigrate.pl -n NMSROOT -o DFM.rps_directory
The command variables are:

NMSROOT

CiscoWorks installation directory (by default, /opt/CSCOpx).

script dir

Directory where the scripts are extracted.

DFM.rps_directory

Full pathname of directory containing DFM 1.2.x DFM.rps file. For DFM 1.2.x installations, this file is located in NMSROOT/objects/smarts/repos/icf/DFM.rps.

Caution Be sure to run the following DFMMigrate.pl from the directory in which it resides; the script requires files that are relative to that directory.

For example (the following command is one line):
/opt/CSCOpx/bin/perl   /opt/CSCOpx/cw-dfm-20-UpgradeKit-sol/smarts/ 
DFMMigrate.pl   -n /opt/CSCOpx   -o /opt/backup
This creates the text files ICseed.txt, ICinventory.txt, and ICptm.xml and places them in script dir/cw-dfm-20-UpgradeKit-sol/smarts/conf.

Step 6 Copy the LMS data to any temporary location in the new server.

Step 7 Copy the following files from your local DFM 1.2.x host to the corresponding directory on the remote DFM 2.0.3 host:

File Name

Location in LMS 2.1

Copy into this location in LMS 2.5.1

ICseed.txt

NMSROOT/objects/smarts/conf

NMSROOT/objects/smarts/conf

ICinventory.txt

ICptm.xml

mail_notify.conf

NMSROOT/objects/smarts/conf/
notifier

NMSROOT/objects/smarts/conf/notifier

trap_notify.conf

Also, copy the DFM 1.2.x backup files to a safe location on the DFM 2.0.3 machine.

Step 8 Stop the daemon manager by entering:

/etc/init.d/dmgtd stop

Step 9 Restore CS, CM, DFM, and RME data by entering:

NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP -gen generationNumber-t temporary_directory

For more details, see Syntax and Usage for Restore and Backup Script, page B-1.

Step 10 If you created IPM backup data, restore it now.

a. Copy ipmBackup.tar to the IPM 2.6 root directory.

b. Change your working directory to the bin directory of the IPM server.

c. Make sure that the License Server process of Common Services, called LicenseServer, is up and running. (Server Configuration > Administration > Process Management > Process Status)

d. Run ipm upgrade at the command prompt.

IPM data is now migrated.

Step 11 Examine the log file in the following location to verify that the database was restored.

The location is /var/adm/CSCOpx/log/restorebackup.log

Step 12 Start the daemon manager by entering:

/etc/init.d/dmgtd start

Migrating Data From LMS 2.2/LMS 1.3/RWAN 1.3

This section explains how to migrate data from LMS 2.2/LMS 1.3 and RWAN 1.3 to LMS 2.5.1.

Note LMS 1.3 has all the LMS 2.2 applications except DFM.

Figure 2-3 Migrating Data from LMS 2.2 /LMS 1.3/RWAN 1.3

* Real-Time Monitor (RTM) and Access Control List Manager are not part of LMS 2.5.1.

If you have installed CiscoWorks Routed WAN Management Solution (RWAN) 1.3 and LMS 2.2 on the same server, you may also have the RWAN 1.3 components such as ACL Manager (ACLM) 1.5 and Internetwork Performance Monitor (IPM) 2.5 on your system.

Caution If you are upgrading your operating system to Solaris 9 (Solaris 2.9), upgrade DFM before upgrading the OS.

You can migrate to LMS 2.5.1 in two ways—Local Migration or Remote Migration. For details, see Understanding Terms Used in the Data Migration Guide, page 1-5.

Note We recommend that you use Remote Migration to migrate to LMS 2.5.1.

Figure 2-4 describes the steps involved in local migration from LMS 2.2/LMS 1.3/RWAN 1.3 to LMS 2.5.1.

Figure 2-4 Steps for Migration from LMS 2.2 /LMS 1.3/RWAN 1.3

Local Migration From LMS 2.2/LMS 1.3/RWAN 1.3

To migrate data on the same machine:

Step 1 Login as root to the machine where LMS applications are installed.

Step 2 Verify that your operating system is supported by LMS 2.5.1. For details on OS platforms supported by LMS 2.5.1, see System Requirements, page 1-5.

Caution If you are upgrading your operating system to Solaris 9 (Solaris 2.9), upgrade DFM before upgrading the OS.

Step 3 Install Common Services 3.0.3.

CS 3.0.3 installer prompts you for a backup directory during local migration, and automatically does a backup. The automatic backup facility only backs up data for CS, RME, Campus Manager and DFM. It does not back up the data for IPM.

Step 4 Optionally install one or more of the required LMS applications.

Note We recommend that you upgrade all the applications which were present in LMS 2.2/RWAN 1.3.

When you uninstall RME 3.5.x, the dependant applications such as ACLM and VPN Monitor are also uninstalled.

At the end of RME installation, the following warning message appears. You may ignore them.

=======- Possible Warnings/Errors Encountered - =======

WARNING: Please install/upgrade all the required apps

WARNING: in the bundle and then run the migration scripts

[...]

==========================================================

Data for Common Services, Campus Manager, and IPM are automatically migrated when you install the respective applications. To restore RME and DFM data, you must run the restorebackup.pl script.

Step 5 If you are upgrading RME and/or DFM, stop the daemon manager by entering:

/etc/init.d/dmgtd stop

Step 6 Restore LMS data by entering:

NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP -gen generationNumber-t temporary_directory

For more details, see Syntax and Usage for Restore and Backup Script, page B-1.

Data for all applications except IPM are migrated now. The restorebackup.pl script overwrites the already existing data for CS, RME, CM, and DFM.

If there is a mismatch in the applications installed and the applications in the backup archive, the following warning messages appear. You may ignore them.
WARNING: There is a mismatch between the list of applications 
installed in this machine and the list of applications present in the 
backup archive. The application data from the backup archive will get 
restored only if that application is installed in this machine. Do you 
want to continue the Restore operation?  (y-continue or n-quit, y/n)?y 
Applications to be restored are............ : [Common Services] [Campus Manager] [Resource Manager Essentials] [Device Fault Manager]

Step 7 Examine the log file in the following location to verify that the database was restored.

The location is /var/adm/CSCOpx/log/restorebackup.log

Step 8 If you stopped the daemon manager in Step 5, restart it by entering:

/etc/init.d/dmgtd start

Remote Migration From LMS 2.2/LMS 1.3/RWAN 1.3

To migrate data on a remote machine:

Step 1 Login as root to the machine where the LMS applications are installed.

Step 2 Back up your LMS data.

a. Back up CS, RME, CM, and DFM data by:

•Entering the following command:

NMSROOT/bin/perl NMSROOT/bin/backup.pl BKP num_generations

where num_generations is the maximum backup generations to be kept in the backup directory

If BKP is the backup directory, the data is stored in the directories BKP/0, BKP/1, and BKP/2 etc., where BKP/n stores the data of the (n+1)th generation.

Or

•Using the CS 2.2 GUI (Server Configuration > Administration > Database Management > Back Up Data Now). Click Help, and follow the instructions to back up your data.

b. If you are upgrading IPM, create the necessary backup files.

To take a backup, run RBackup.sh from the IPM 2.6 CD-ROM root directory.

This stops all IPM servers that are running and takes a backup of the database, the seed files, the environment variables, and the version information.

While running RBackup.sh, you are prompted to specify the backup directory. However, the default backup directory is /opt. The data is compressed and the ipmBackup.tar file is created in the specified directory.

Step 3 Login as root into the remote machine where you want to install LMS 2.5.1.

Step 4 Install LMS 2.5.1 applications in the remote machine. You must first install Common Services (CS 3.0.3), then install the required LMS applications.

Step 5 If you are upgrading to DFM 2.0.3, assemble the files needed for the DFM migration:

a. Copy the DFM 2.0.3 Upgrade Kit from the remote DFM 2.0.3 image to your local DFM 1.2.x host. The upgrade kit contains the DFMMigrate.pl script and other required files.

In the following command, NMSROOT is the remote DFM 2.0.3 installation directory (normally /opt/CSCOpx), and dir is a directory on your local DFM 1.2.x host.

NMSROOT/bin/cw-dfm-20-UpgradeKit-sol.zip dir

b. Locate your copy of the 1.2.x DFM.rps file, normally located in NMSROOT/objects/smarts/repos/icf/DFM.rps.

If you plan to use a copy of this file that was created during a backup, the file will be located in the backup directory you specified when using CiscoWorks Common Services or CiscoWorks 2000 CD One.

c. Make sure the DFM.rps file is named DFM.rps, otherwise Step 5 d.will fail.

Caution For DFM users, if you plan to upgrade your operating system from Solaris 8 (Solaris 2.8) to Solaris 9 (Solaris 2.9), you need to run the DFMMigrate.pl script (in the DFM 2.0.3 upgrade kit) on Solaris 8 (Solaris 2.8), before migrating your operating system for the remote upgrade.

d. Use the DFMMigrate.pl script to create the required migration files.

–Move to the directory into which you copied the cw-dfm-20UpgradeKit-sol.zip file.

–Unzip the file. It creates a directory called cw-dfm-20-UpgradeKit-sol.

–Run the DFMMigrate.pl script:
NMSROOT/bin/perl script dir/cw-dfm-20-UpgradeKit-sol/smarts/ 
DFMMigrate.pl -n NMSROOT -o DFM.rps_directory
The command variables are:

NMSROOT

CiscoWorks installation directory (by default, /opt/CSCOpx).

script dir

Directory where the script is extracted.

DFM.rps_directory

Full pathname of directory containing DFM 1.2.x DFM.rps file. For DFM 1.2.x installations, this file is located in NMSROOT/objects/smarts/repos/icf/DFM.rps.

Caution Be sure to run the following DFMMigrate.pl from the directory in which it resides; the script requires files that are relative to that directory.

For example (the following command is one line):
/opt/CSCOpx/bin/perl   /opt/CSCOpx/cw-dfm-20-UpgradeKit-sol/smarts/ 
DFMMigrate.pl   -n /opt/CSCOpx   -o /opt/backup
This creates the text files ICseed.txt, ICinventory.txt, and ICptm.xml and places them in script dir/cw-dfm-20-UpgradeKit-sol/smarts/conf.

Step 6 Copy the LMS data to any temporary location in the new server.

Step 7 Copy the following files from your local DFM 1.2.x host to the corresponding directory on the remote DFM 2.0.3 host.

File Name

Location in LMS 2.2

Copy into this location in LMS 2.5.1

ICseed.txt

NMSROOT/objects/smarts/conf

NMSROOT/objects/smarts/conf

ICinventory.txt

ICptm.xml

mail_notify.conf

NMSROOT/objects/smarts/conf/
notifier

NMSROOT/objects/smarts/conf/notifier

trap_notify.conf

Also, copy the DFM 1.2.x backup files to a safe location on the DFM 2.0.3 machine.

Step 8 Stop the daemon manager by entering:

/etc/init.d/dmgtd stop

Step 9 Restore CS, CM, DFM, and RME data by entering:

NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP -gen generationNumber-t temporary_directory

For more details, see Syntax and Usage for Restore and Backup Script, page B-1.

Step 10 If you created IPM backup data, restore it now.

a. Copy ipmBackup.tar to the IPM 2.6 root directory.

b. Change your working directory to the bin directory of the IPM server.

c. Make sure that the License Server process of Common Services, called LicenseServer, is up and running. (Server Configuration > Administration > Process Management > Process Status)

d. Run ipm upgrade at the command prompt.

IPM data is now migrated.

Step 11 Examine the log file in the following location to verify that the database was restored.

The location is /var/adm/CSCOpx/log/restorebackup.log

Step 12 Start the daemon manager by entering:

/etc/init.d/dmgtd start

Understanding LMS Backup Files Created During CS Installation

If DB_BKP is the directory you gave during the CS installation process, the location of the backup directory and structures are:

•DB_BKP/automaticbackup/cmfbackup

•DB_BKP/automaticbackup/mcbackup

The DB_BKP/automaticbackup/cmfbackup directory and the DB_BKP/automaticbackup/mcbackup directory are used to store LMS backup data and VMS backup data, respectively.

VMS is another solutions bundle available from Cisco. VMS applications are sometimes known as MC or Monitoring Center applications, hence the mc in the directory name.

If the DB_BKP/automaticbackup/mcbackup directory is empty, there are no VMS based applications installed in the machine.

To restore data on LMS 2.5.1 Server, you should specify DB_BKP/automaticbackup/cmfbackup as the backup directory.
Table 2-1 Restoring LMS Data from Backup
To restore...

Enter...
The most recent version of LMS backup data
NMSROOT/bin/perl 
NMSROOT/bin/restorebackup.pl -d 
DB_BKP/automaticbackup/cmfbackup
The (n+1)th generation of LMS backup data
NMSROOT/bin/perl 
NMSROOT/bin/restorebackup.pl -d 
DB_BKPautomaticbackup/cmfbackup-
gen n
The 1st generation of LMS backup data
NMSROOT/bin/perl 
NMSROOT/bin/restorebackup.pl -d 
DB_BKPautomaticbackup/cmfbackup-
gen now
The 3rd generation of LMS backup data
NMSROOT/bin/perl 
NMSROOT/bin/restorebackup.pl -d 
DB_BKPautomaticbackup/cmfbackup-
gen 2

Table Of Contents

Migrating Data to LAN Management Solution 2.5.1 on Solaris

Migrating Data From LMS 2.1/LMS 1.2/RWAN 1.2

Local Migration From LMS 2.1/LMS 1.2/RWAN 1.2

Remote Migration From LMS 2.1/LMS 1.2/RWAN 1.2

Migrating Data From LMS 2.2/LMS 1.3/RWAN 1.3

Local Migration From LMS 2.2/LMS 1.3/RWAN 1.3

Remote Migration From LMS 2.2/LMS 1.3/RWAN 1.3

Understanding LMS Backup Files Created During CS Installation

Migrating Data to
LAN Management Solution 2.5.1 on Solaris