Installation and Setup Guide for Device Fault Manager 2.0 on Solaris (With LMS 2.5) - Upgrading Device Fault Manager [CiscoWorks Device Fault Manager]

Table Of Contents

Upgrading DFM

Upgrade Overview

Local Upgrade

Procedure for Local Upgrade

Data that Is Migrated by a Local Upgrade

Remote Upgrade

Procedure for Remote Upgrade

Data that Is Migrated by a Remote Upgrade

Preparing to Upgrade DFM

Upgrading to DFM 2.0

Performing a Local Upgrade

Performing a Remote Upgrade

Validating the Upgrade

Exporting DFM 1.2.x Information to an Upgraded Remote Host

Post-Upgrade Steps

Upgrading DFM

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

•Upgrade Overview

•Preparing to Upgrade DFM

•Upgrading to DFM 2.0

•Post-Upgrade Steps

Upgrade Overview

DFM 2.0 provides a completely new user interface and many new functions. For more information, see Appendix C, "How is DFM 2.0 Different from DFM 1.2.x?."

You can perform a local in-place upgrade or a remote upgrade from the following:

•DFM 1.2 (with or without patch/IDUs).

•DFM 1.2 Updated for Common Services Version 2.2 (with or without patch/IDUs).

This document refers to these previous versions as DFM 1.2.x. This section provides a brief outline of the procedures and the data migration for each type of upgrade.

Local Upgrade

You perform a local upgrade on the system where DFM 1.2.x is installed.

Procedure for Local Upgrade

Table 3-1 Local Upgrade Procedure

Tasks

Reference

Step 1

Upgrade from DFM 1.2.x to DFM 2.0.

Note To perform the upgrade, you will install DFM 2.0 from the CD and then manually run a program to upgrade your data.

Performing a Local Upgrade

Step 2

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

Post-Upgrade Steps

Data that Is Migrated by a Local Upgrade

The following data is migrated from DFM 1.2.x to DFM 2.0 when you perform a local upgrade:

•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 Upgrading Polling Settings and Upgrading Threshold Settings.

No other data is migrated.

Upgrading Polling Settings

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

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

After upgrade, DFM 2.0 applies factory default settings to:

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

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

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

Table 3-2 Comparison of Polling Groups and Settings between DFM 1.2 and DFM 2.0

Polling Groups

Polling Settings

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

And become members of these groups in DFM 2.0...

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

Reflected in these DFM 2.0 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, DFM 2.0 sets its value to the DFM 2.0 factory default value.

Upgrading Threshold Settings

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

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

Table 3-3 Comparison of Threshold Groups and Settings between DFM 1.2 and DFM 2.0

Threshold Groups

Threshold Settings/Categories

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

And become members of these groups in DFM 2.0...¹

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

Reflected in these DFM 2.0 threshold categories

Interface Groups

Interface Groups

For Interface Groups, Access Port Groups, and Trunk Port Groups, the threshold settings in DFM 1.2 correspond closely to the threshold categories in DFM 2.0. 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, DFM 2.0 sets its value to the DFM 2.0 factory default value.

Remote Upgrade

You perform a remote upgrade on a system where DFM 1.2.x is not installed.

Procedure for Remote Upgrade

Caution If you are upgrading your operating system from Solaris 2.8 to Solaris 2.9, run the upgrade script on Solaris 2.8 (before migrating your operating system). Otherwise the upgrade script will fail.

Table 3-4 Remote Upgrade Procedure

Tasks

Reference

Step 1

Upgrade or install DFM 2.0 on the remote system.

•Performing a Local Upgrade

•Performing a New Installation

Step 2

If you purchased a DFM 2.0 upgrade license, validate the upgrade by providing proof of purchase of DFM 1.2.x.

Validating the Upgrade

Step 3

Export the DFM 1.2.x seed file and import it to DFM 2.0; or

Use the DFM 2.0 Upgrade Kit to perform your data migration.

Exporting DFM 1.2.x Information to an Upgraded Remote Host

Data that Is Migrated by a Remote Upgrade

Step 4

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

Post-Upgrade Steps

Data that Is Migrated by a Remote Upgrade

Only the device list is migrated. However, you can use a DFM 2.0 Upgrade Kit to migrate the following additional DFM 1.2.x information:

•Device managed state (managed or unmanaged).

•Some polling and threshold settings (as described in Data that Is Migrated by a Local Upgrade).

To use the Upgrade Kit, you must have a copy of the DFM 1.2.x DFM.rps (inventory) file. The Upgrade Kit and accompanying Readmes are available from the DFM download page at http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-dfm

Preparing to Upgrade DFM

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

If you purchased an upgrade license of DFM 2.0, you are required to validate the upgrade by providing one of the following:

•The original CD containing DFM 1.2 or DFM 1.2 Updated for Common Services Version 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 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 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

Upgrading to DFM 2.0

You can upgrade from DFM 1.2.x, with or without patch/IDUs, to DFM 2.0 on local or remote systems. If desired, you can upgrade a remote system and then export your local DFM 1.2.x information to the upgraded remote system. These procedures are described in the following sections:

•Performing a Local Upgrade

•Performing a Remote Upgrade

Performing a Local Upgrade

Follow these steps to upgrade a local host to DFM 2.0.

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 your operating system from Solaris 2.8 to Solaris 2.9, run the upgrade script on Solaris 2.8 (before migrating your operating system). Otherwise the upgrade script will fail.

•All installed applications are supported by Common Services 3.0. Applications not supported by Common Services will be disabled when you upgrade CD One.

•Common Services has been installed. (See Installation and Setup Guide for Common Services (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 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 3 Start the installation program by entering one of the following:

•To install from a locally mounted CD drive, enter:
# cd /cdrom/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 4 If you are using ACS mode, you will be warned that if you configured any custom ACS roles, they will be lost unless you exit the upgrade and change the AAA security mode to CiscoWorks Local. Do one of the following:

• If you want to continue the upgrade (you will lose any ACS custom roles), click Yes and proceed to Step 5.

• If you do not want to continue the upgrade (so you can change your AAA security mode to CiscoWorks Local and save any ACS custom roles), do the following:

–Click No. (You will need to reset your mode to ACS after you have installed DFM, as described in Step 8.) The installation will abort.

–From the command prompt, run the following command:
NMSROOT/bin/perl NMSROOT/bin/ResetLoginModule.pl
–Return to Step 3 to begin the upgrade process again.

Step 5 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 
2) Install Device Fault Manager 2.0 HPOV-NetView adapters 
Step 6 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.

If DFM detects another application using port 162, DFM displays the following message:
WARNING: Installation has detected port 162 in use. DFM is set to use 
port 9000 for receiving SNMP traps.
If you see this message, after the installation completes, you must configure DFM SNMP trap receiving to use a different UDP port, such as port 9000. (See Configuring SNMP Trap Receiving and Forwarding.)

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 by a Local Upgrade).

The system prompt appears.

Step 7 Unmount and eject the CD-ROM.

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

Step 8 If you exited the upgrade in order to change your AAA security mode from ACS to CiscoWorks Local (in Step 4), reset your security role back to ACS. From the Common Services home page, select Server > Security > AAA Mode Setup, click Help, and follow the instructions.

Step 9 Upgrade DFM 1.2.x data to DFM 2.0 using the following command:
perl NMSROOT/bin/DFM12x-DFM20-upgrade.pl
where NMSROOT is the default installation directory, normally /opt/CSCOpx.

The script automatically does all of the following:

1. Imports the seedfile generated from DFM 1.2.x into DCR.

2. Imports devices from DCR into DFM 2.0 and monitors device import status.

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

3. Applies the manage/unmanage state of the devices/device components obtained from DFM 1.2.x during the upgrade.

4. Applies new polling and threshold settings to the devices.

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

Performing a Remote Upgrade

Perform these steps after DFM 2.0 is installed on a remote system:

•If you purchased an upgrade license of DFM 2.0, you must validate the upgrade.See Validating the Upgrade.

•Export DFM 1.2.x information to DFM 2.0. See Exporting DFM 1.2.x Information to an Upgraded Remote Host.

Validating the Upgrade

If you purchased an upgrade license of DFM 2.0, you must validate the upgrade on the system where DFM 2.0 is installed using the following commands:
cd NMSROOT/bin
./dfmValidateUpgrade.sh 
where 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.)

Exporting DFM 1.2.x Information to an Upgraded Remote Host

This procedure exports your local DFM 1.2.x device list and imports it to a remote system that has been upgraded to DFM 2.0.

Step 1 As root, log in to the local DFM 1.2.x system.

Step 2 Export the device inventory to a seed file using the following command:
NMSROOT/objects/smarts/bin/sm_tpmgr -s DFM --dump-agents > 
seedfile.txt 
where NMSROOT is the default installation directory (normally /opt/CSCOpx).

Step 3 Copy the seed file to the remote system.

Step 4 Log in to the remote DFM 2.0 system as root.

Step 5 Import the inventory into DFM 2.0 using the following command:
NMSROOT/bin/dfmimport fn=completePath/seedfile.txct
where NMSROOT is the default installation directory (normally /opt/CSCOpx) and completePath/seedfile.txt is the complete path to the seed file and the seed file name.

The script will initiate device discovery.

Note If an error occurs because the CiscoWorks daemon manager is not running, start it by typing the following command:
/etc/init.d/dmgtd start
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:

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

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

•Complete basic configuration steps; see Configuring SNMP Trap Receiving and Forwarding.

•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 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 the standard UDP trap port (162) is being used by another NMS, such as Cisco Voice Manager, you must configure DFM SNMP trap receiving to use a different UDP port, such as port 9000. See Integrating DFM Trap Receiving with Other NMSs or Trap Daemons.

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.