Data Migration Guide for LAN Management Solution 3.2
Chapter 1: Overview
Download this chapter
Chapter 1: OverviewChapter 1: Overview
Download the complete book
Data Migration Guide for LAN Management Solution 3.2 - PDF of Entire BookData Migration Guide for LAN Management Solution 3.2 - PDF of Entire Book (PDF - 1 MB)
 Feedback

Table Of Contents

Overview

Overview of Migration to LMS 3.2

System Requirements

Terms Used in the Data Migration Guide

Scope of Data Migration

CS Data Migration Scope

CM Data Migration Scope

RME Data Migration Scope

DFM Data Migration Scope

IPM Data Migration Scope

CV Data Migration Scope

HUM Data Migration Scope

Portal Data Migration Scope

CiscoWorks Assistant Data Migration Scope


Overview

This document describes the steps involved in migrating data for CiscoWorks LAN Management Solutions (LMS) 3.2. The Selective Backup feature explained in this document is limited to LMS 3.2 and it is not supported in the previous version of LMS.

The following migration paths are described in this document:

•LMS 2.6 or LMS 2.6 Service Pack (SP1) to LMS 3.2

•LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 to LMS 3.2

For more information on the applications and the version numbers, see the Overview of CiscoWorks LAN Management Solution 3.2 section in Installing and Getting Started With CiscoWorks LAN Management Solution.

This chapter contains:

•Overview of Migration to LMS 3.2

•System Requirements

•Terms Used in the Data Migration Guide

•Scope of Data Migration

Overview of Migration to LMS 3.2

Migration is the process of carrying over data from an older version of LMS to a newer version of LMS.

Migration involves:

1. Backing up the older version of LMS data.

2. Installing the newer version of LMS.

3. Restoring the backed up data.

You can migrate to LMS 3.2 using either of these methods:

•Local Migration. This is installing LMS 3.2 on top of the existing LMS version, on the same machine and migrating the data into it.

Or

•Remote Migration. This is installing LMS 3.2 on a different machine and migrating the backed up data into it.

Note On Solaris machine, the backed up folder must be compressed and transferred. If not, the restore may fail due to the changes in the file name and checksum, as the file name changes from the upper case to the lowercase.

Notes for Remote Migration

The application list in the backed up data should exactly match the application list in the machine where it is restored except for CiscoWorks Assistant and Portal. If there is a difference, the behavior of the applications after upgrade will be unpredictable.

Table 1-1 is an example of a scenario when the behavior of the application is unpredictable.

Table 1-1

Example No
Applications in the Backup Archive
Applications in the Restore Machine
Explanation

Example 1

CS 3.2

RME 4.2

CM 5.1

DFM 3.1

CS 3.3

RME 4.3

CM 5.2

DFM 3.2

This is a supported combination for remote migration.

Example 2

CS 3.2

CM 5.1

IPM 4.1

HUM 1.1

CS 3.3

RME 4.3

CM 5.2

DFM 3.2

IPM 4.2

HUM 1.2

This is not a supported combination for remote migration.

When you try to migrate this backup data on a remote machine, the behavior of the applications may be unpredictable and few features in the CiscoWorks applications may not work properly

Example 3

CS 3.2

CM 5.1

RME 4.2

IPM 4.1

HUM 1.1

DFM 3.1

CS 3.3

CM 5.2

IPM 4.2

HUM 1.2


Remote Migration Scenario

For details on migrating data for all applications to LMS 3.2, see:

•Migrating Data to CiscoWorks LAN Management Solution 3.2 on Solaris

•Migrating Data to CiscoWorks LAN Management Solution 3.2 on Windows

System Requirements

Table 1-2 provides details of the system requirements for LMS 3.2 servers:

Table 1-2 Operating Systems Supported for LMS 3.2 Servers

Operating System
Version

Solaris

9, 10

Windows

Windows 2003 Standard and Enterprise Editions with SP1 and SP2

Windows 2003 R2 Standard and Enterprise Editions with SP1 and SP2

Windows 2008 Standard and Enterprise Editions with SP1

Note Both 32 bit and 64 bit operating systems are supported on these versions.


LMS 3.2 supports virtualization systems: VMware ESX Server 3.0.x, VMware ESX Server 3.5.x, VMware ESXi 3.5 Update 2, Hyper-V, Zone based Virtualization in Solaris 10 and Logical domains (LDoms) in Solaris 10.

For complete information on the System Requirements, see the "System and Browser Requirements for Server and Client" section in the Prerequisites chapter in the Installing and Getting Started with CiscoWorks LAN Management Solution 3.2 guide at this location:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html

Terms Used in the Data Migration Guide

The terms frequently used in this document are explained below:

•Copying —Copying the LMS Data in a directory.

•Upgrading—Installing a newer software version on top of an older version (For example, installing LMS 3.2 on LMS 3.1).

•Migrating—Carrying over data from an older version of LMS to a newer version.

•Restoring—Bringing the backed up data into the newer version of LMS.

Scope of Data Migration

This section lists the data that is migrated for CS, CiscoWorks Assistant, CM, RME, DFM, IPM,CV, HUM and Portal when you upgrade to LMS 3.2.

•On both platforms, migration is supported across different NMSROOT directories, where NMSROOT is the CiscoWorks installation directory. By default, it is:

–/opt/CSCOpx for Solaris

–C:\Program Files\CSCOpx for Windows, where C: is the System Drive

•Cross platform data migration is not supported.

This section contains the following topics:

•CS Data Migration Scope

•CM Data Migration Scope

•RME Data Migration Scope

•DFM Data Migration Scope

•IPM Data Migration Scope

•Portal Data Migration Scope

•CiscoWorks Assistant Data Migration Scope

•CV Data Migration Scope

•HUM Data Migration Scope

Data Migration for LMS 3.2 application can be done using the following methods:

•Normal Backup - Process by which all the configuration files and collected data can be backed up from application database.

•Selective Backup - Process by which only required system configurations and data can be backed up.

CS Data Migration Scope

The Common Services (CS) data can be backed up using either the Normal or the Selective mode.

Normal Backup

The following data gets migrated when you upgrade to Common Services 3.3:

•CiscoWorks User information

•Single Sign-on configuration

•Device and Credential Repository (DCR) configuration

•Peer Certificates and Self Signed Certificates

•Peer Server Account information

•Login Module settings

•Software Center map files

•License data

•Core Client Registry

•System Identity Account configuration

•Cisco.com User configuration

•Proxy User configuration

•Jobs and Resources data, DCR data, Groups data, and other data stored in the database

•Discovery settings and Scheduled jobs

•ACS Credentials

•Local User Policy Setup

•System Preferences

•Multiple Default Credentials— Multiple Default Credentials are migrated only when you restore data from LMS 3.2.

•Policy Configuration— Policy Configuration are migrated only when you restore data from LMS 3.2.

•Logrot Configuration— Logrot Configuration are migrated only when you restore data from LMS 3.2.

•DCR Exclude list— DCR Exclude list are migrated only when you restore data from LMS 3.2.

•Unreachable Device Polling Settings— Unreachable Device Polling Settings are migrated only when you restore data from LMS 3.2.

•LDAP Configuration— LDAP Configuration are migrated only when you restore data from LMS 3.2.

Note CS Discovery configuration data and Discovery jobs will be migrated only from LMS 3.0 December 2007 Update and LMS 3.1.

Selective Backup

When you run a selective data backup from CLI, all the data mentioned above gets backed up except:

•Software Center map files

•Completed jobs data

CM Data Migration Scope

The Campus Manager (CM) data can be backed up using either the Normal or the Selective mode.

Normal Backup

The following data gets migrated when you upgrade to Campus Manager 5.2:

•SNMP Settings

•CM Homepage Settings

•Data Collection Scheduled Details

•User Defined Groups

•RME Credentials

•Data Purge Settings

•Trap Configuration Settings

•Custom Reports and Layouts

•Topo Map Preferences— This is applicable only for upgrade.

•Topology Layouts— Manually changed topology layouts will not be migrated in both upgrade and backup/restore scenarios.

•MAC Detection Settings.

•Device Details

•Port and VLAN Details

•Campus Jobs and Archives

•User Tracking Jobs and Archives

•VNM Settings, Jobs and Archives— VNM Settings Jobs and Archives are migrated only when you restore data from LMS 3.2.

Selective Backup

When you run a selective data backup from CLI, all the data mentioned above gets backed up except:

•Device Details

•Port and VLAN Details

•Campus Archives, UT Archives and VNM Archives

Note Discovery settings will be migrated for LMS 3.0 or lower versions.

RME Data Migration Scope

The Resource Manager Essentials (RME) data can be backed up using either the Normal or the Selective mode.

Normal Backup

The following data gets migrated when you upgrade to RME 4.3:

•Change Audit

–Set Purge Policy

–Force Purge

–Config Change Filter

•Config Management

–Transport Settings

–Archive Settings

–Collection Settings

–Purge Settings

–Exclude Commands

–Fetch Settings

–Config Editor

–Config Job Policies

•Device Management

–Device Management Settings

–Device Credential Verification Settings

•Reports

–Archive Settings

–PSIRT/EOS/EOL Reports

•Config Archive

–Shadow directory

–ChangeAudit records. This includes Configuration change details

–Archived configuration versions

•NetConfig

–User-defined Templates (UDT)

–Default Template Usage

By default, all templates are assigned to Admin on migration. The device-to-task mapping is not migrated.

•RME groups

–Archive Management

–All jobs

–Label Configs

–Custom queries

–Baseline templates

–Shadow directory

–ChangeAudit records. This includes Configuration change details.

–Archived configuration versions

•Admin— Purge policies

•Config Editor:

–Private Configs

–Public Configs

–Config Editor jobs

–Editing mode in which the files are opened. It is either Raw or Processed.

•NetConfig:

–Netconfig jobs. This includes Device based jobs, Port based jobs and Module based jobs. Port and Module based jobs are migrated only when you restore data from LMS 3.2.

–User-defined tasks

•NetShow:

–NetShow jobs

–Output archives

–Commandsets

•Software Management

–View/Edit Preferences

–Update Upgrade Information

–Software Management repository images

–All jobs in a Job Browser

•System Preferences

–Application Log Level Settings

–Job Purge

–RME Device Attributes

–RME Secondary Credentials

–Collection Failure Notification

•Inventory

–Inventory Change Filter

–System Job Schedule

–Cisco.com Fetch Interval

–Inventory jobs

–Device details

–Inventory Collection status

–DCA jobs

–Device Management state

–User -defined groups

•Syslog details

–Set Backup Policy

–Set Purge Policy

–Force Purge

–Automated actions

–Message filters

–Custom reports

–Syslog messages for the past 14 days

–Report jobs and archives

•Port and Module group administration— Port and Module group administration are migrated only when you restore data from LMS 3.2.

–Port groups

–Module groups

Note While restoring data from RME 4.2 to RME 4.3, all jobs, data and admin settings will be migrated.

Selective Backup

When you run a selective data backup from CLI, all the data mentioned above gets backed up except:

•SWIM Images

•Common Reporting Infrastructure archives

•Config editor data

•Syslog data

DFM Data Migration Scope

The Device Fault Manager (DFM) data can be backed up using either the Normal or the Selective mode.

Normal Backup

The following data gets migrated when you upgrade to DFM 3.2:

•Device list—The migration procedure adds devices to Common Services Device and Credentials Repository (DCR). To manage them in DFM, either enable Auto Manage feature or manually add the devices to DFM

The following notification information:

–Mail notification information

–Mail recipient information

–Mail sender ID

–Syslog notification

–SMTP addresses

–Trap forwarding addresses

–Trap notification addresses and ports

•DFM groups

•AAD page

•Data Purge settings— Data Purge settings are migrated only when you restore data from LMS 3.0 December 2007 Update or LMS 3.1.

•Log settings—Log settings are migrated only when you restore data during a Local Migration.

•Some polling and threshold settings

•Device details

•Trap forward settings

•Notification settings (group, email, trap and syslog settings)

•Notification customization changes

•Event sets

•AAD views, user defined and customizable groups

•JRM Jobs

•Alerts and Events details

•Fault History details

•SNMP Settings— SNMP Settings are migrated only when you restore data from LMS 3.2.

•Email Subject customization settings— Email Subject customization settings are migrated only when you restore data from LMS 3.2.

Selective Backup

When you run a selective data backup from CLI, all the data mentioned above gets backed up except:

•Alerts and Events details

•Fault History details

IPM Data Migration Scope

The Internetwork Performance Manager (IPM) data can be backed up using either the Normal or the Selective mode.

Normal Backup

The following data gets migrated when you upgrade to IPM 4.2:

•IPM Collectors

•IPM database—Contains information about source devices, target devices, operations, collectors, and the statistics of data collected.

•The settings in ipm.env file

Note HTML reports available in IPM 2.6 is backed-up but not restored by running restorebackup.pl.

You can generate consolidated System Reports for data migrated from IPM 2.6 to IPM 4.2. However, the time taken to generate the reports depends on the length of the period for which you are querying.

For example, generating reports for a period of 6 months may take a longer time, than generating reports for a period of 10 days.

During the same version backup/restore, do not run /NMSROOT/bin/restorebackup.pl script from the following directories:

•Solaris

NMSROOT/MDC/tomcat/webapps/ipm/system_reports

/var/adm/CSCOpx/files/ipm/ and

NMSROOT/CSCOpx/MDC/tomcat/webapps/ipm/archive_charts

•Windows

NMSROOT\MDC\tomcat\webapps\ipm\system_reports

NMSROOT\CSCOpx\files\ipm\ and

NMSROOT\CSCOpx\MDC\tomcat\webapps\ipm\archive_charts

When you install IPM 4.2, and migrate from LMS 3.0 or LMS3.0 December 2007 Update or LMS 3.1to LMS 3.2, the following data gets migrated:

•IPM database—contains information about source devices, target devices, operations, collectors, admin settings and the statistics of data collected.

•Settings in IPM properties.

•Log Settings.

•System Reports

•Report Jobs and archives.

•Exported data (Statistics and Collectors).

Selective Backup

When you run a selective data backup from CLI, all the data mentioned above gets backed up except the statistical table available in database.

CV Data Migration Scope

The CiscoView (CV) data can be backed up using the Normal mode. When you upgrade to CiscoView 6.1.9, the user's device preferences are migrated.

HUM Data Migration Scope

The Health and Utilization Monitor (HUM) data can be backed up using either the Normal or the Selective mode.

Normal Backup

The following data gets migrated when you upgrade to HUM 1.2:

•Configuration Data

•Threshold Violation Scripts

•Reports

•Template Configuration

•Database

–Poller Configuration

–Threshold Configuration

–Admin Settings

–Polled data

–Threshold Violation data

–Summarization data

–Job information.

–Trendwatch Configurations— Trendwatch Configurations are migrated only when you restore data from HUM 1.2.

–TrendWatch Violation data— TrendWatch Violation data are migrated only when you restore data from HUM 1.2.

•Trap Receiver Groups— Trap Receiver Groups are migrated only when you restore data from HUM 1.2.

•Syslog Receiver Groups— Syslog Receiver Groups are migrated only when you restore data from HUM 1.2.

Selective Backup

When you run a selective data backup from CLI, all the data mentioned above gets backed up except the Polled data and completed reports.

HUM will not backup old reports and immediate reports as part of selective backup. HUM will backup periodic reports.

Portal Data Migration Scope

The LMS Portal data can be backed up using the Normal mode. The CiscoWorks Portal configuration or settings get migrated when you upgrade to Portal 1.2. All the private page customization in the earlier LMS version (3.0/3.0.1/3.1) will be migrated to the My portal page after upgrade.

CiscoWorks Assistant Data Migration Scope

No data gets migrated when you upgrade to CiscoWorks Assistant 1.2.