Installation and Setup Guide for Device Fault Manager 2.0.6 on Solaris (With LMS 2.6) - Upgrading and Migrating DFM [CiscoWorks Device Fault Manager]

Table Of Contents

Upgrading and Migrating DFM

Upgrade and Migration Overview

Terminology: Upgrade and Migration

Supported DFM Versions for Upgrade and Migration

Data that Is Migrated to DFM 2.x

How Polling Settings Are Affected After Migration and Restoration

How Threshold Settings Are Affected After Migration

Migrating from DFM 1.2.x to DFM 2.x

Preparing to Migrate to DFM 2.x

Performing a Local Migration from DFM 1.2.x to DFM 2.x

Performing a Remote Migration from DFM 1.2.x to DFM 2.x

Installing DFM 2.x on the Remote Host

Validating the Installation on the Remote DFM 2.x Host

Backing Up Your Data on the Local DFM 1.2.x Host

Generating Your DFM 1.2.x Migration Files from Your Local DFM 1.2.x Host

Restoring Your DFM Data on the Remote DFM 2.x Host

Upgrading DFM 2.0.x to DFM 2.0.6

Preparing to Upgrade to DFM 2.0.6

Performing a Local Upgrade from DFM 2.0.x to DFM 2.0.6

Performing a Remote Upgrade from DFM 2.0.x to DFM 2.0.6

Installing DFM 2.0.6 on the Remote Host

Backing Up Your DFM Data

Copy the Backup Files from Your Local DFM 2.0.x Host

Restoring the DFM Data on Your Remote DFM 2.0.6 Host

Post-Upgrade Steps

Upgrading and Migrating DFM

This chapter describes upgrading and migrating Device Fault Manager (DFM) on a Solaris system. It includes:

•Upgrade and Migration Overview

•Migrating from DFM 1.2.x to DFM 2.x

•Upgrading DFM 2.0.x to DFM 2.0.6

•Post-Upgrade Steps

Upgrade and Migration Overview

This section provides overview information on upgrade and migration process topics:

•Terminology: Upgrade and Migration

•Supported DFM Versions for Upgrade and Migration

•Data that Is Migrated to DFM 2.x

Terminology: Upgrade and Migration

This topic describes the difference between the terms migration and upgrade.

Migration

Migration is the transfer of data from an older version of DFM to a newer version of DFM. It involves:

1. Backing up the older version of DFM data.

2. Installing the newer version of DFM.

3. Restoring the backed up data.

You can migrate data using either of these two methods:

•Local migration: installing DFM 2.0.3 and DFM 2.0.6 on top of DFM 1.2.x.

•Remote migration: installing DFM 2.0.3 and DFM 2.0.6 on a different machine.

For information on the data that is migrated to DFM 2.0.6, see Data that Is Migrated to DFM 2.x. The migration procedures are provided in Migrating from DFM 1.2.x to DFM 2.x.

Upgrade

Upgrading involves overwriting the existing DFM version with the new DFM version. The data and user settings of the old version are retained in the new version (in other words, the migration of data is automatic). However, for upgrades from DFM 1.2.x, this data migration is not automatic; you must intervene and run a special script, as documented in this guide.

You can upgrade using either of these two methods:

•Local upgrade: installing DFM 2.0.6 on top of DFM 2.0.x on the same machine. You can perform this upgrade using the DFM CD or using LMS 2.5 Update 2 (available from Cisco.com).

•Remote upgrade: installing DFM 2.0.6 on a different machine and then restoring the DFM 2.0.x data on the machine that has DFM 2.0.6.

The upgrade procedures are provided in Upgrading DFM 2.0.x to DFM 2.0.6.

Supported DFM Versions for Upgrade and Migration

You can migrate or upgrade the following versions of DFM to DFM 2.0.6.

Device Fault Manager Version¹

...Which Came with LAN Management Solution Version...

Reference

DFM 1.2

LMS 2.1

Migrating from DFM 1.2.x to DFM 2.x

DFM 1.2 Updated for Common Services Version 2.2

LMS 2.2

DFM 2.0²

LMS 2.5

Upgrading DFM 2.0.x to DFM 2.0.6

DFM 2.0.3³

LMS 2.5.1

Upgrading DFM 2.0.x to DFM 2.0.6

¹Migration/upgrade is also supported when any patch/IDUs or service packs are installed on these versions of DFM.

²In this scenario, all DFM 2.0.x data is preserved.

³In this scenario, all DFM 2.0.x data is preserved.

Data that Is Migrated to DFM 2.x

The following data is restored when you perform a migration from DFM 1.2.x:

•Device list—The migration procedure adds devices to Common Services Device and Credentials Repository and to DFM.

•Device managed state (managed or unmanaged).

•The following notification information:

–Mail recipient information

–Mail sender ID

–SMTP addresses

–Trap destination addresses

–Trap destination ports

•Some polling and threshold settings—See How Polling Settings Are Affected After Migration and Restoration and How Threshold Settings Are Affected After Migration.

No other data is migrated.

How Polling Settings Are Affected After Migration and Restoration

Table 3-1 lists DFM 1.2.x polling groups and settings and those in DFM 2.x that correspond to them. For a device to retain polling settings from DFM 1.2.x, a corresponding polling group (and settings) must exist in DFM 2.x and the device must belong to it.

In DFM 2.x, there are several additional polling groups not listed in Table 3-1 (for more information, see User Guide for Device Fault Manager). A device might belong to a new polling group in DFM 2.x. For example, a voice gateway is a member of the Routers polling group in DFM 1.2.x and the Voice and Telephony polling group in DFM 2.x.

After upgrade, DFM 2.0.3 applies factory default settings to:

•Any device that belongs to a different polling group than it did in DFM 1.2.x.

•Any setting that was removed from a polling group in DFM 1.2.x.

The device support table lists the DFM 1.2.x and DFM 2.x groups; refer to Product Documentation, page x.

Table 3-1 Comparison of Polling Groups and Settings between DFM 1.2.x and DFM 2.x

Polling Groups

Polling Settings

Devices that were members of these groups in DFM 1.2.x...

And become members of these groups in DFM 2.x...

Retain the values from these DFM 1.2.x polling settings...¹

Reflected in these DFM 2.x polling settings

Optical Switches

Optical Networking

•Connectivity Polling

•Environment Polling

•Performance Polling - Processor and Memory

•Performance Polling - Ports and Interfaces (includes access port)

•Reachability settings

•Environment

•Processor and memory utilization

•Connector port and interface

•Access port

Switches

Switches and Hubs

Routers

Routers

Other Systems

Voice and Telephony

Connectivity Polling

Reachability settings

¹For any polling setting that was removed from a polling group in DFM 1.2.x, DFM 2.0.3 sets its value to the DFM 2.0.3 factory default value.

How Threshold Settings Are Affected After Migration

Like polling settings, threshold settings are retained when a device (or device component) is a member of a DFM 2.x threshold group that corresponds to the DFM 1.2.x threshold group it was a member of. Table 3-2 lists the corresponding threshold groups and settings.

There are additional threshold groups in DFM 2.x not listed in Table 3-2 (for more information, see User Guide for Device Fault Manager). DFM 2.0.3 applies factory default threshold values to devices that are members of new DFM 2.x threshold groups. The device support table lists the DFM 1.2.x and DFM 2.x groups; refer to Product Documentation, page x.

Table 3-2 Comparison of Threshold Groups and Settings between DFM 1.2.x and DFM 2.x

Threshold Groups

Threshold Settings/Categories

Devices that were members of these in DFM 1.2.x...

And become members of these groups in DFM 2.x...¹

Retain the values from these DFM 1.2.x threshold settings...²

Reflected in these DFM 2.x threshold categories

Interface Groups

Interface Groups

For Interface Groups, Access Port Groups, and Trunk Port Groups, the threshold settings in DFM 1.2.x correspond closely to the threshold categories in DFM 2.x For a list of threshold categories for these groups, see User Guide for Device Fault Manager.

Access Ports Groups

Access Port Groups

Trunk Ports Groups

Trunk Port Groups

Optical Switches

Optical Networking

•Connectivity

•Environment

•Processor and Memory

•Reachability

•Environment

•Processor and Memory

Routers

Routers

Switches

Switches and Hubs

¹Each DFM 2.0 threshold group contains subgroups. This allows you to set threshold settings appropriately for each group of devices.

²For any threshold setting that was removed from a threshold group in DFM 1.2.x, DFM 2.0 sets its value to the DFM 2.0 factory default value.

Migrating from DFM 1.2.x to DFM 2.x

You can perform a migration from DFM 1.2.x either locally or remotely.

Preparing to Migrate to DFM 2.x

Before you migrate, determine whether you need to gather additional information and media.

If you purchased an upgrade license and are migrating from DFM 1.2.x, you are required to validate the installation by providing one of the following:

•The original CD containing DFM 1.2 (which shipped with LMS 2.1).

•The original CD containing DFM 1.2 Updated for Common Services Version 2.2 (which shipped with LMS 2.2).

•Login information for a remote server where the previous version of DFM (DFM 1.2.x) is running.

Caution If validation is not successful, DFM is installed with an evaluation license; access to DFM functionality will be prohibited when the license expires.

You might need to provide the following information during the migration:

•DFM database password and a DFM username and password for use by DFM processes—Only required when you perform a custom installation; otherwise, this information is randomly generated.

For more information on creating passwords, see the appendix "Password Information" in Installation and Setup Guide for Common Services 3.0.6 (Includes CiscoView) on Solaris.

•License information—If you must supply license information, the installation script prompts you for one of the following:

–Information that you will find printed on the software claim certificate—Product Identification Number (PIN) and Product Authorization Key (PAK).

–Location of the license file—If you have a license file, provide its location. If not, be sure to obtain one. You can do so before or after you install DFM; see Registering Your License.

Note You can determine the status of your license from the CiscoWorks home page, by selecting Common Services > Server > Admin > Licensing.

Note If you are installing DFM for evaluation purposes:

•You do not need to supply a license file or PIN and PAK.

•You might be interested in the following information:

–Upgrading Your Evaluation License

–Licensing Reminders

Performing a Local Migration from DFM 1.2.x to DFM 2.x

You can migrate to DFM 2.x on a local system as described in this section. Table 3-3 provides an overview of the local migration procedure.

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

Table 3-3 Procedure for Local Migration from DFM 1.2.x to DFM 2.x

Tasks

Reference

Step 1

Back up your data.

This section

Step 2

Install DFM from the CD. (You may have to run the validation script, as documented in this section, to stop the Proof of Purchase nag message.)

Step 3

Run the restorebackup.pl script to migrate your data.

Step 4

Perform post-migration steps to complete basic configuration of DFM 2.x.

Post-Upgrade Steps

Follow these steps to migrate a local DFM 1.2.x host to DFM 2.x. If you are installing DFM 2.x on a clean machine (onto which you will migrate your DFM data), use the installation instructions in Performing a New Installation.

Note Device import can take up to 3 hours, depending on the number of devices in your inventory.

Step 1 Make sure your system meets the following prerequisites:

•Required (or desired) operating system upgrades have been performed, and required service packs are installed.

Caution Do not upgrade your operating system if you are upgrading Solaris 8 (Solaris 2.8) to Solaris 9 (Solaris 2.9), and plan to upgrade DFM 1.2.x to 2.0.3. Upgrade your OS after upgrading DFM.

•All installed applications are supported by Common Services 3.0.6. If you have not upgraded to Common Services 3.0.6, DFM 1.2.x links will be disabled.

•Common Services has been installed. (See Installation and Setup Guide for Common Services 3.0.6 (Includes CiscoView) on Solaris.)

•If you want a locally installed NMS to send traps to DFM, HP OpenView or NetView has been installed. See Supported NMS Integration.

Step 2 Make sure you have the data described in Preparing to Migrate to DFM 2.x.

Step 3 Back up your DFM data by selecting Server Configuration > Administration > Database Management > Back Up Data Now. Click Help, and follow the instructions to back up your information.

Step 4 As root, log into the system onto which you will migrate DFM, and do the following:

a. Mount a local or remote CD-ROM drive. For instructions on mounting the CD-ROM, see "Mounting and Unmounting on Solaris."

b. Close all open or active programs. Do not run other programs during the upgrade process.

Step 5 Start the installation program by entering one of the following:

•To install from a locally mounted CD drive, enter:
# cd remotedir/cdrom0
# ./setup.sh
•To install from a remotely mounted CD drive, enter:
# cd remotedir
# ./setup.sh
where remotedir is the remote location where the CD-ROM is mounted.

The installation program stops CiscoWorks, performs a requirements check, and might display a request to enter license information; for more information, see "Licensing."

Step 6 The installation program displays the following installation choices (the choices may vary, depending on your configuration; see Table 1-1):
1) Install Device Fault Manager 2.0.3 
2) Install Device Fault Manager 2.0.3 HPOV-NetView adapters 
Step 7 Select 1 and press Return. This installs the complete DFM package, which contains DFM and the HPOV-NetView adapters. (For more information on installation components, see Table 1-1.)

The following message is displayed:
The application that you are installing requires new tasks to be registered with ACS. If 
you have already registered this application with ACS from another server, you do not need 
to register it again. However, if you re-register the application, you will lose any 
custom roles that you had created earlier for this application in ACS.
Enter (Y)es to Register, (N)o to continue without registering, (Q)uit: [N]
Step 8 Do one of the following:

•If you want to register (or re-register) DFM with the ACS server, enter Y. DFM will be registered with the ACS server.

•If you do not want to register with the ACS server, enter N. (You will be prompted to register later.)

•If you want to abort the installation, enter Q.

The installation program checks dependencies and system requirements:

•If there is not enough disk space for the installation, the installation program displays an error message and stops.

Note Do not be alarmed if you see the following message:
INFO: total size (MB) required = 87
This message applies to disk space required by the current set of individual packages being installed.

•If the minimum recommended requirements are not met, the installation program displays an error message and continues installing.

The following message is displayed:
If no other CiscoWorks application installations are pending, you can choose to start 
CiscoWorks daemons. 
Do you want to restart CiscoWorks Daemons at the end of this installation? (y/n) [n]:
Step 9 Do one of the following:

•If you plan to install another LMS application after installing DFM, enter n, and the daemons are not restarted. (You will be prompted to restart the daemons later.)

•If do not plan to install another LMS application after installing RME, enter y, and the daemons are restarted.

Depending upon your configuration, you maybe reminded to run the restorebackup.pl script. The migration proceeds without displaying any more questions. The migration program:

•Copies the files to the CiscoWorks default installation directory /opt/CSCOpx (NMSROOT).

•Exports data (see Data that Is Migrated to DFM 2.x).

The system prompt appears.

Step 10 If you did not register DFM with the ACS server in Step 8, and you want to register now, use the AcsRegCli.pl script, as follows. (NMSROOT is the default installation directory, normally /opt/CSCOpx.)
NMSROOT/bin/perl NMSROOT/bin/AcsRegCli.pl -register dfm
Step 11 Unmount and eject the CD-ROM.

Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.

Step 12 Upgrade to DFM 2.0.6 by installing the LMS 2.6 Update on Solaris (see Installing the LMS 2.6 Update).

Step 13 If you receive a nag message asking for your Proof of Purchase, run the validation script to stop the message (NMSROOT is the CiscoWorks installation directory, normally /opt/CSCOpx). You will not be prompted to enter any information.
cd NMSROOT/bin
./dfmValidateUpgrade.sh 
Step 14 Restore your DFM data using restorebackup.pl:

Note Make sure you have backed up the latest DFM data, as described in Step 3.

Note If you are installing DFM with other LAN Management Solution components, perform this step after all components are installed. Refer to the Quick Start Guide for LAN Management Solution 2.5.1 for more information.

a. Stop the daemon manager:
/etc/init.d/dmgtd stop
b. Run the script:
NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d backup_location -gen version -t 
tempbackup_dir
In the previous command, NMSROOT is the CiscoWorks installation directory, normally /opt/CSCOpx.

Example:
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl -d /opt/CSCOpx/backup -t /tmp
where:

–/opt/CSCOpx is the CiscoWorks installation directory.

–/opt/CSCOpx/backup is the backup location you specified in Step 3. This is mandatory.

–/tmp is a temporary location into which the backup files are extracted. These files are used by the restore backup script. This is optional and will be deleted after the data migration is complete. By default, the restore backup script uses /opt/CSCOpx/tempbackupdata directory.

You can optionally include -gen version to specify a backup version to be migrated to DFM 2.x. By default, it will restore the latest backup data.

Depending upon your configuration, you may be prompted to give your approval when migration begins, and you may also be reminded to check for updates on Cisco.com.

The script imports the seedfile into the DCR, imports the devices into DFM, and restores all of the data described in Data that Is Migrated to DFM 2.x.

Note Device import can take up to 3 hours, depending on the number of devices in your inventory.

c. Restart the daemon manager:
/etc/init.d/dmgtd start
Step 15 To check the status of device discovery and to complete your configuration of DFM, see Post-Upgrade Steps.

If you had any errors, check /var/adm/CSCOpx/log/restorebackup.log. The Cisco Technical Assistance Center (TAC) might ask you to send them this log.

Performing a Remote Migration from DFM 1.2.x to DFM 2.x

Table 3-4 provides an overview of the remote migration when migrating DFM 1.2.x to DFM 2.x.

Table 3-4 Procedure for Remote Migration from DFM 1.2.x to DFM 2.x

Tasks

Reference

Step 1

Install DFM 2.x on the remote host.

Performing a New Installation

Step 2

Validate the installation on the remote DFM 2.x host.

Validating the Installation on the Remote DFM 2.x Host

Step 3

Back up your data on the DFM 1.2.x host.

Backing Up Your Data on the Local DFM 1.2.x Host

Step 4

Run the DFMMigrate.pl script, assemble your DFM 1.2.x migration files, and copy the migration files onto the DFM 2.x host.

Generating Your DFM 1.2.x Migration Files from Your Local DFM 1.2.x Host

Step 5

Run the restorebackup.pl script on the DFM 2.x host to restore your data.

Restoring Your DFM Data on the Remote DFM 2.x Host

Step 6

Perform post-migration steps to complete basic configuration of DFM 2.x.

Post-Upgrade Steps

Installing DFM 2.x on the Remote Host

Install DFM 2.x on your remote host, as described in Performing a New Installation. You will be reminded to run the restorebackup.pl script, which is described in Restoring Your DFM Data on the Remote DFM 2.x Host. (Depending upon your configuration, you may also be reminded to check for updates on Cisco.com.)

Validating the Installation on the Remote DFM 2.x Host

If you have not done so already, validate the installation on the system where DFM 2.x is installed using the following commands:
cd   NMSROOT/bin
./dfmValidateUpgrade.sh 
In the previous command, NMSROOT is the default installation directory, normally /opt/CSCOpx.

The following prompt is displayed:
This utility will validate your proof of purchase of the product and allows you to obtain 
an upgrade license. 
Please select the source for upgrade validation from the following:
1. Validate from a CD (old version).
2. Validate from a remote server (old version).
Please enter option [1 / 2]: 
Enter 1 or 2 and follow the instructions provided by the prompts. For example, if you enter 1:
Please insert the previous versions of DFM CD into the CDROM drive and provide the 
absolute path to the CD drive:
/cdrom/cdrom0
Validation succeeded.
For example, if you enter 2:
Please enter the remote CiscoWorks server host name or the IP address: dfm-host
Please enter the remote CiscoWorks server http port number: 1741
Please enter the remote CiscoWorks server login name: admin
Please enter the remote CiscoWorks server login password: *******
Please be patient. Upgrade validation is in progress from a remote server.
Validation succeeded.
Note If validation does not succeed, you can continue with the upgrade, however:

•DFM is licensed for evaluation only and operates in nag mode for no more than 90 days before ceasing operation. (See Evaluation Version: Before Expiry.)

•You must contact your Cisco representative to purchase a fully licensed version of DFM. (See Upgrading Your Evaluation License.)

Backing Up Your Data on the Local DFM 1.2.x Host

On the local DFM 1.2.x host, back up your DFM data using Common Services.

Step 1 From the Common Services home page, select Server Configuration > Administration > Database Management > Back Up Data Now.

Step 2 In the Back Up Data Now dialog box, enter the path and name for the backup directory.

Step 3 Click Finish to start the backup.

By default, the information will be placed in the NMSROOT/backup directory (where NMSROOT is the CiscoWorks installation directory, normally /opt/CSCOpx).

Generating Your DFM 1.2.x Migration Files from Your Local DFM 1.2.x Host

This procedure explains how to generate and collect the files required by DFM 2.x so you can migrate your local DFM 1.2.x data to your remote DFM 2.x host. In this procedure you will do the following:

•Use the DFMMigrate.pl script to create files that contain the device list, device management state information, and polling and threshold information.

•Optionally, copy the Mail Notifier Adapter and Trap Notifier Adapter files so you can migrate the adapter configurations.

In Restoring Your DFM Data on the Remote DFM 2.x Host, you will copy these files to your remote DFM 2.x host so you can restore your DFM data.

Step 1 Copy the DFM Upgrade Kit to a temporary directory on your local DFM 1.2.x host. The Upgrade Kit contains the DFMMigrate.pl script and other required files. Use one of the following methods:

•Copy the Upgrade Kit from the following location on the remote DFM 2.x installation. In the following, NMSROOT is the remote DFM 2.x installation directory (normally /opt/CSCOpx).
NMSROOT/bin/cw-dfm-20-UpgradeKit-sol.zip
•Download the Upgrade Kit by logging in to Cisco.com and going to http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-dfm. Extract the kit as described in the Readme file located on the download site.

Step 2 Locate your copy of the 1.2.x DFM.rps file:

•In a DFM 1.2.x installation, the DFM.rps file is normally located in NMSROOT/objects/smarts/repos/icf (where NMSROOT is the CiscoWorks installation directory, normally /opt/CSCOpx).

•For a backup copy, the file will be located in the backup directory you specified when you backed up the file using CiscoWorks Common Services.

Step 3 Make sure the DFM.rps file is named DFM.rps, otherwise Step 4 will fail.

Step 4 Use the DFMMigrate.pl script to create the required migration files.

a. Move to the directory into which you copied the cw-dfm-20UpgradeKit-sol.zip file in Step 1.

b. Unzip the file. It will create a directory called cw-dfm-20-UpgradeKit-sol.

c. Move to the cw-dfm-20-UpgradeKit-sol/smarts directory, which contains the migration script:
cd cw-dfm-20-UpgradeKit-sol/smarts
d. Run the DFMMigrate.pl script:

Caution Be sure to run DFMMigrate.pl from the cw-dfm-20-UpgradeKit-sol/smarts directory; the script requires files that are relative to that directory.
NMSROOT/bin/perl DFMMigrate.pl -n NMSROOT -o DFM.rps_directory
The command variables are as follows:

NMSROOT

CiscoWorks installation directory (normally /opt/CSCOpx).

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.

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

Step 5 Copy the following migration files from your local DFM 1.2.x host to the corresponding directory on the remote DFM 2.x host:

•Copy the three files in NMSROOT/cw-dfm-20-UpgradeKit-sol/smarts/conf/ to the following location on the DFM 2.x host:

NMSROOT/objects/smarts/conf

•Optionally, copy the Mail Notifier and Trap Notifier Adapter files from the following location on the DFM 1.2.x host:

NMSROOT/objects/smarts/conf/notifier/mail_notify.conf NMSROOT/objects/smarts/conf/notifier/trap_notify.conf

•to the following directory on the DFM 2.x host:

NMSROOT/objects/smarts/conf/notifier

•Copy the DFM 1.2.x backup files (from Backing Up Your Data on the Local DFM 1.2.x Host) to a safe location on the DFM 2.x host.

Restoring Your DFM Data on the Remote DFM 2.x Host

Note When restoring your data, device import can take up to 3 hours, depending on the number of devices in your inventory.

Step 1 On the remote DFM 2.x host, confirm that you have properly copied the files described in Step 5 of Generating Your DFM 1.2.x Migration Files from Your Local DFM 1.2.x Host.

Step 2 Restore your DFM data using restorebackup.pl.

a. Stop the daemon manager:
/etc/init.d/dmgtd stop
b. Run the script:
NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d backup_location -gen version 
-t tempbackup_dir
where NMSROOT is the CiscoWorks installation directory, normally /opt/CSCOpx.

Example:
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl -d /opt/CSCOpx/backup -t /tmp
In the previous command, the values are as follows:

–/opt/CSCOpx is the CiscoWorks installation directory.

–/opt/CSCOpx/backup is the location into which you copied your backup files in Step 5 of Generating Your DFM 1.2.x Migration Files from Your Local DFM 1.2.x Host. This is mandatory.

–/tmp is a temporary location into which the backup files are extracted. These files are used by the restore backup script. This is optional and will be deleted after the data migration is complete. By default, the restore backup script uses /opt/CSCOpx/tempbackupdata directory.

You can optionally include -gen version to specify a backup version to be migrated to DFM 2.0.3. By default, it will restore the latest backup data.

The migration script imports the seedfile into the DCR, imports the devices into DFM, and migrates all of the data described in Data that Is Migrated to DFM 2.x.

Note Device import can take up to 3 hours, depending on the number of devices in your inventory.

c. Restart the daemon manager:
/etc/init.d/dmgtd start
Step 3 To check the status of device discovery and to complete your configuration of DFM, see Post-Upgrade Steps.

If you had any errors, check /var/adm/CSCOpx/log/restorebackup.log. The Cisco Technical Assistance Center (TAC) might ask you to send them this log.

Upgrading DFM 2.0.x to DFM 2.0.6

You can perform an upgrade either locally or remotely, as described in these topics.

Preparing to Upgrade to DFM 2.0.6

Before you upgrade, determine whether you need to gather additional information and media. You might need to provide it during the upgrade:

•DFM database password and a DFM username and password for use by DFM processes—Only required when you perform a custom installation; otherwise, this information is randomly generated.

For more information on creating passwords, see the appendix "Password Information" in Installation and Setup Guide for Common Services 3.0.6 (Includes CiscoView) on Solaris.

•License information—If you must supply license information, the installation script prompts you for one of the following:

–Information that you will find printed on the software claim certificate—Product Identification Number (PIN) and Product Authorization Key (PAK).

–Location of the license file—If you have a license file, provide its location. If not, be sure to obtain one. You can do so before or after you install DFM; see Registering Your License.

Note You can determine the status of your license from the CiscoWorks home page, by selecting Common Services > Server > Admin > Licensing.

Note If you are installing DFM for evaluation purposes:

•You do not need to supply a license file or PIN and PAK.

•You might be interested in the following information:

–Upgrading Your Evaluation License

–Licensing Reminders

Performing a Local Upgrade from DFM 2.0.x to DFM 2.0.6

You can upgrade to DFM 2.0.6 on a local system as described in this section. Table 3-5 provides an overview of the local upgrade procedure.

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

Table 3-5 Procedure for Local Upgrade from DFM 2.0.x to DFM 2.0.6

Tasks

Reference

Step 1

Back up your data.

This section

Step 2

Install DFM from the CD.

Step 3

Perform post-upgrade steps to complete basic configuration of DFM 2.0.6.

Post-Upgrade Steps

Follow these steps to upgrade a local DFM 2.0.x host to DFM 2.0.6. If you are installing DFM 2.0.6 on a clean machine (onto which you will migrate your DFM data), use the installation instructions in Performing a New Installation.

Note If you have DFM 2.0.3 (supplied with LMS 2.5.1), install the LMS 2.5 Update 2 by downloading it from Cisco.com, and installing it..
If you have DFM 2.0 (which came with LMS 2.5), install the LMS 2.5 Dec 2005 Update, and then install the LMS 2.5 Update 2.
You can download the required software from Cisco.com, http://www.cisco.com/public/sw-center/cw2000/lan-planner.shtml.

Note Device import can take up to 3 hours, depending on the number of devices in your inventory.

Step 1 Make sure your system meets the following prerequisites:

•Required (or desired) operating system upgrades have been performed, and required service packs are installed.

Caution If you are upgrading Solaris 8 (Solaris 2.8) to Solaris 9 (Solaris 2.9), you must upgrade your OS after upgrading DFM 1.2.x to 2.0.6.

•All installed applications are supported by Common Services 3.0.6. If you have not upgraded to Common Services 3.0.6, DFM 2.0.x links will remain enabled, but Common Services will issue a warning message.

•Common Services has been installed. (See Installation and Setup Guide for Common Services 3.0.6 (Includes CiscoView) on Solaris.)

•If you want a locally installed NMS to send traps to DFM, HP OpenView or NetView has been installed. See Supported NMS Integration.

Step 2 Make sure you have the data described in Preparing to Upgrade to DFM 2.0.6.

Step 3 Back up your DFM data from the Common Services home page by selecting Server > Admin > Backup. Click Help, and follow the instructions to back up your information.

Step 4 As root, log into the system on which you will upgrade DFM, and do the following:

a. Mount a local or remote CD-ROM drive. For instructions on mounting the CD-ROM, see "Mounting and Unmounting on Solaris."

b. Close all open or active programs. Do not run other programs during the upgrade process.

Step 5 Start the installation program by entering one of the following:

•To install from a locally mounted CD drive, enter:
cd localdir/cdrom0
./setup.sh
•To install from a remotely mounted CD drive, enter:
cd remotedir
./setup.sh
where remotedir is the remote location where the CD-ROM is mounted.

The installation program stops CiscoWorks, performs a requirements check, and might display a request to enter license information; for more information, see "Licensing."

Step 6 The installation program displays the following installation choices (the choices may vary, depending on your configuration; see Table 1-1):
1) Install Device Fault Manager 2.0.6 
2) Install Device Fault Manager 2.0.6 HPOV-NetView adapters 
Step 7 Select 1 and press Return. This installs the complete DFM package, which contains DFM and the HPOV-NetView adapters. (For more information on installation components, see Table 1-1.)

The installation program checks dependencies and system requirements:

•If there is not enough disk space for the installation, the installation program displays an error message and stops.

Note Do not be alarmed if you see the following message:
INFO: total size (MB) required = 87
This message applies to disk space required by the current set of individual packages being installed.

•If the minimum recommended requirements are not met, the installation program displays an error message and continues installing.

Depending upon your configuration, you may be reminded to check for updates on Cisco.com. The upgrade proceeds without displaying any more questions. The upgrade program:

•Copies the files to the CiscoWorks default installation directory /opt/CSCOpx (NMSROOT).

•Exports data (see Data that Is Migrated to DFM 2.x).

The system prompt appears.

Step 8 Unmount and eject the CD-ROM.

Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.

Step 9 To check the status of device discovery and to complete your configuration of DFM, see Post-Upgrade Steps.

If you had any errors, check /var/adm/CSCOpx/log/restorebackup.log. The Cisco Technical Assistance Center (TAC) might ask you to send them this log.

Performing a Remote Upgrade from DFM 2.0.x to DFM 2.0.6

Table 3-6 provides an overview of the remote upgrade procedure when upgrading DFM 2.0.x to DFM 2.0.6.

Table 3-6 Procedure for Remote Upgrade from DFM 2.0.x to DFM 2.0.6

Tasks

Reference

Step 1

Install DFM 2.0.6 on the remote system.

Performing a New Installation

Step 2

Back up your DFM 2.0.x data on the local host.

Backing Up Your DFM Data

Step 3

Copy the backup files from your local DFM 2.0.x host to the remote DFM 2.0.6 host.

Copy the Backup Files from Your Local DFM 2.0.x Host

Step 4

Run the restorebackup.pl script on the DFM 2.0.6 host to restore your data.

Restoring the DFM Data on Your Remote DFM 2.0.6 Host

Step 5

Perform post-upgrade steps to complete basic configuration of DFM 2.0.6.

Post-Upgrade Steps

Installing DFM 2.0.6 on the Remote Host

Install DFM 2.0.6 on your remote host, as described in Performing a New Installation. (Depending upon your configuration, you may be reminded to check for updates on Cisco.com.)

Backing Up Your DFM Data

On the local DFM 2.0.x host, back up your DFM data using Common Services.

Step 1 From the Common Services home page, select Server > Admin > Backup.

Step 2 In the Backup dialog box, enter the path and name for the backup directory.

Step 3 Click Finish to start the backup.

By default, the information will be placed in the NMSROOT/backup directory (where NMSROOT is the CiscoWorks installation directory, normally /opt/CSCOpx).

Copy the Backup Files from Your Local DFM 2.0.x Host

Step 1 On your local DFM 2.0.x host, locate the files you backed up in Backing Up Your DFM Data.

Step 2 Copy the backup files from your local DFM 2.0.x host to a safe location on the remote DFM 2.0.6 host (for example, using ftp).

Restoring the DFM Data on Your Remote DFM 2.0.6 Host

Note When migrating your data, device import can take up to 3 hours, depending on the number of devices in your inventory.

Step 1 On your upgraded DFM 2.0.6 host, restore your DFM data using restorebackup.pl.

a. Stop the daemon manager:
/etc/init.d/dmgtd stop
b. Run the script:
NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d backup_location -gen version 
-t tempbackup_dir
where NMSROOT is the CiscoWorks installation directory, normally /opt/CSCOpx.

Example:
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl -d /opt/CSCOpx/backup -t /tmp
where:

–/opt/CSCOpx is the CiscoWorks installation directory.

–/opt/CSCOpx/backup is the backup location you specified in Step 2 of Copy the Backup Files from Your Local DFM 2.0.x Host. This is mandatory.

–/tmp is a temporary location into which the backup files are extracted. These files are used by the restore backup script. This is optional and will be deleted after the data migration is complete. By default, the restore backup script uses /opt/CSCOpx/tempbackupdata directory.

You can optionally include -gen version to specify a backup version to be migrated to DFM 2.0.6. By default, it will restore the latest backup data.

The migration script imports the seedfile into the DCR, imports the devices into DFM, and migrates all of the data described in Data that Is Migrated to DFM 2.x.

c. Restart the daemon manager:
/etc/init.d/dmgtd start
Note Device import can take up to 3 hours, depending on the number of devices in your inventory.

Step 2 To check the status of device discovery and to complete your configuration of DFM, see Post-Upgrade Steps.

If you had any errors, check the upgrade log, /var/adm/CSCOpx/log/restorebackup.log. The Cisco Technical Assistance Center (TAC) might ask you to send them this log.

Post-Upgrade Steps

After the upgrade script completes, DFM discovers devices and updates its managed inventory. DFM might take some time to complete this task. Afterward, you should do the following:

•Reconfigure the Rediscovery Schedule (which is not migrated during an upgrade); select Configuration > Other Configurations > Rediscovery Schedule.

•Reconfigure SNMP trap forwarding (which is not migrated during an upgrade); see Updating the SNMP Trap Receiving Port.

•Familiarize yourself with new device management procedures; see Performing Device Management.

•Perform SNMP trap configuration tasks; see Configuring SNMP Trap Receiving and Forwarding.

•Verify discovery status; see Verifying Devices Added to DFM.

•Start using DFM to monitor the network; see Viewing Alerts and What Next?.

If you plan to use HPOV-NetView adapters on a remote system with Device Fault Manager 2.0.6 on a local system, perform these steps:

1. Make sure the system running DFM is registered with DNS.

2. Upgrade all remote adapters as described in Installing and Upgrading HPOV-NetView Adapters.

Note If you install another NMS—such as Cisco Voice Manager—after installing DFM, you must:

1. Configure DFM to forward traps to the listening port for the NMS. See Configuring SNMP Trap Forwarding.

2. Make sure the NMS is configured to receive traps at the port you specified in Step 1. See the appropriate documentation for the NMS.

If a local version of HP OpenView or NetView is already installed (or is installed later), CiscoWorks automatically configures the adapters to forward SNMP traps to DFM. To configure remote versions of HP OpenView and NetView to forward SNMP traps to DFM, you must install the HPOV-NetView adapters on the remote systems as described in Installing and Upgrading HPOV-NetView Adapters.