Table Of Contents

Migrating Data to
LAN Management Solution 2.5.1 on Windows

Migrating Data From LMS 2.1/LMS 1.2/RWAN 1.2

Before You Begin Migration

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 Windows

---

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

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 LMS 2.1 applications except DFM.

---

Figure 3-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.

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

---

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

---

Before You Begin Migration

When you attempt to restore your data during remote or local migration, you may see the following error message, and must follow the instructions in the message:

"ERROR: Unable to copy from backup archive folder to temporary folder POSSIBLE REASON:

Some files in the backup archive might not have enough permissions to read and copy.

SUGGESTION TO RESOLVE:

1. Open 'Windows Explorer'.

2. Right click on the generation folder (DB_BKP\0) and select 'Properties'

3. Click the 'Security tab'

4. Select/De-Select the allow/deny boxes so that you have permission to read

5. Click the 'Advanced button'

6. Enable the 'Reset permissions on all child objects.......' check boxes.

7. Click 'Apply', and 'OK' Button

Try doing the restore again, you should succeed."

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

Figure 3-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 administrator to the machine where LMS is installed.

Step 2 Set the permissions on the backup folder as described in "Before You Begin Migration" section.

Step 3 Verify that your operating system is supported for LMS 2.5.1. For details on OS platforms supported by LMS 2.5.1, see "System Requirements" section.

Step 4 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 5 Install one or more of 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, the 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 upgrade the respective applications. To restore RME and DFM data, you must run the restorebackup.pl script.

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

net stop crmdmgtd

Step 7 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" section.

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

If there is a mismatch in the applications installed and the applications in the backup archive, the following warning messages appear:

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 8 Examine the log file in the following location to verify that the database was restored.

The location is CSCOpx\log\restorebackup.log

Step 9 If you have stopped the daemon manager in Step 6, restart it by entering:

net start crmdmgtd

---

Remote Migration From LMS 2.1/LMS 1.2/RWAN 1.2

To migrate data on a remote machine:

---

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

Step 2 Set the permissions of the backup folder as described in "Before You Begin Migration" section.

Step 3 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

For details, see "Syntax and Usage for Backup Script" section.

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 a backup, run rbackup.exe 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.exe, the default backup directory is the backup directory under the IPM installation root directory. However, you can specify any directory.

---

Note When using a custom directory, some of the files do not have proper permissions. While you move these files to remote machine, you need to manually modify their permissions.

---

Change your working directory to the directory where you have installed IPM 2.4 and change to the backup directory.

Step 4 Login as administrator into the machine where you want to install LMS 2.5.1.

Step 5 Install LMS 2.5.1 applications in the remote machine. You must first install Common Services (CS 3.0.3), then optionally install one or more of the required LMS applications.

Step 6 If you are upgrading to DFM 2.0.3, assemble the files needed for 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 C:\Program Files\CSCOpx), and dir is a directory on your local DFM 1.2.x host.

NMSROOT\bin\cw-dfm-20-UpgradeKit-win.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 6 d.will fail.

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

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

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

–Run the DFMMigrate.pl script:

NMSROOT\bin\perl script dir\cw-dfm-20-UpgradeKit-win\smarts\ 
DFMMigrate.pl -n NMSROOT -o DFM.rps_directory

The command variables are:

NMSROOT	CiscoWorks installation directory (by default, C:\Program Files\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):

C:\Program Files\CSCOpx\bin\perl   \opt\CSCOpx\cw-dfm-20-UpgradeKit-wi
n\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-win\smarts\conf.

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

Step 8 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 9 Stop the daemon manager by entering:

net stop crmdmgtd

Step 10 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" section.

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

a. Copy the entire contents in this directory to the backup directory under the directory where you have installed IPM 2.6.

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

c. Make sure that the License Server process (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 12 Examine the log file in the following location to verify that the database was restored.

The location is \CSCOpx\log\restorebackup.log

Step 13 Start the daemon manager by entering:

net start crmdmgtd

---

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/RWAN 1.3.

---

Note LMS 1.3 has all LMS 2.2 applications except DFM.

---

Figure 3-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.

You can migrate to LMS 2.5.1 in two ways—Local Migration or Remote Migration. We recommend that you use Remote Migration to migrate to LMS 2.5.1. For details, see "Understanding Terms Used in the Data Migration Guide" section.

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

Figure 3-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 administrator to the machine where LMS is installed.

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

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 dependent applications such as ACLM and VPN Monitor are also uninstalled.

At the end of RME installation, the following warning messages appear. 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 upgrade the respective applications. To restore RME and DFM data, you must run the restore backup script.

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

net stop crmdmgtd

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.

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

If there is a mismatch in the applications installed and the applications in the backup archive, the following warning messages appear:

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 CSCOpx\log\restorebackup.log

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

net start crmdmgtd

---

Remote Migration From LMS 2.2/LMS 1.3/RWAN 1.3

To migrate data on a remote machine:

---

Step 1 Login as administrator 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

For details, see Syntax and Usage for Backup Script.

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 a backup, run rbackup.exe 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.exe, the default backup directory is the backup directory under the IPM installation root directory. However, you can specify any directory.

---

Note When using a custom directory, some of the files do not have proper permissions. While you move these files to remote machine, you need to manually modify their permissions.

---

Change your working directory to the directory where you have installed IPM 2.4 and change to the backup directory.

Step 3 Login as administrator into the 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 optionally install one or more of the applications—RME 4.0.3, Campus Manager 4.0.3, DFM 2.0.3 or IPM 2.6.

Step 5 If you are upgrading to DFM 2.0.3, assemble the files needed for 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, C:\Program Files\CSCOpx), and dir is a directory on your local DFM 1.2.x host.

NMSROOT\bin\cw-dfm-20-UpgradeKit-win.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.

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

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

–Unzip the file. It will create a directory called cw-dfm-20-UpgradeKit-win.

–Run the DFMMigrate.pl script:

NMSROOT\bin\perl script dir\cw-dfm-20-UpgradeKit-win\smarts\ 
DFMMigrate.pl -n NMSROOT -o DFM.rps_directory

The command variables are:

NMSROOT	CiscoWorks installation directory (by default, C:\Program Files\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):

C:\Program Files\CSCOpx\bin\perl   \opt\CSCOpx\cw-dfm-20-UpgradeKit-wi
n\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-win\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:

net stop crmdmgtd

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" section.

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

a. Copy the entire contents in this directory to the backup directory under the directory where you have installed IPM 2.6.

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

c. Make sure that the License Server process (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 \CSCOpx\log\restorebackup.log

Step 12 Start the daemon manager by entering:

net start crmdmgtd

---

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 as follows:

•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 3-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_BKP\automaticbackup\ cmfbackup -gen n
The 1st generation of LMS backup data	NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d DB_BKP\automaticbackup\ cmfbackup -gen now
The 3rd generation of LMS backup data	NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d DB_BKP\automaticbackup\ cmfbackup -gen 2