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

Table Of Contents

Installing and Uninstalling DFM

Preparing to Install DFM

Verifying TCP and UDP Ports that DFM Uses

Downloading the LMS 2.6 Megapatch

Gathering Information to Provide During Installation

Installing LMS 2.6

Performing a New Installation

Installing the LMS 2.6 Update

Installing the Single Large File Update

Installing the Multiple Small Files Update

When the Installation Is Complete

Reinstalling DFM

Uninstalling DFM

Installing and Upgrading HPOV-NetView Adapters

Reinstalling the HPOV-NetView Adapters on a Local Host

Installing or Upgrading the HPOV-NetView Adapters on a Remote Host

Uninstalling the HPOV-NetView Adapters

Installing and Uninstalling DFM

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

•Preparing to Install DFM

•Performing a New Installation

•Reinstalling DFM

•Uninstalling DFM

•Installing and Upgrading HPOV-NetView Adapters

•Uninstalling the HPOV-NetView Adapters

Preparing to Install DFM

The sections that follow help you to perform the following tasks before you install DFM:

•Determine whether your existing applications are already using ports that DFM uses; see Verifying TCP and UDP Ports that DFM Uses. (Existing applications should not use the ports that DFM uses.)

•Download the LMS 2.6 megapatch if you have an existing LMS 2.5.1 installation; see Downloading the LMS 2.6 Megapatch.

•Gather information that you might need to provide during the DFM installation; see Gathering Information to Provide During Installation.

Verifying TCP and UDP Ports that DFM Uses

Before installing DFM, make sure that the ports DFM uses will be used only by applications listed in Table 2-1. For a complete list of ports used by Common Services and other LAN Management Solution (LMS) applications, see the Quick Start Guide for LAN Management Solution 2.5.1 on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000_b/lms/lms25/index.htm.

DFM uses the following TCP and UDP ports.

Table 2-1 DFM Ports

Protocol

Port Number

Service Name

Direction (of establishment) of Connection

ICMP

—

Ping

Server to Device

UDP

161

Simple Network Management Protocol (SNMP)

Server to Device,
Device to Server

162

SNMP Traps (Standard Port)—Default port number used by DFM for receiving traps

Server to Device,
Device to Server

9000

Used for trap receiving (if port 162 is occupied)

Client to Server

9002

Used by DFM broker

Client to Server

TCP

49

TACACS+ and ACS

Server to ACS

8898

Used by log server

Server internal

15000

Used by log server

Server internal

43445

Used by Fault History database engine (dfmFH)

Server internal

43446

Used by inventory service database engine (DFMInv)

Server internal

43447

Used by event processing database engine (dfmEPM)

Server internal

43500-43520

Used by DFM CSTM (Common Services Transport Mechanism) for internal application messaging

Server internal

Downloading the LMS 2.6 Megapatch

If you have an existing LMS 2.5.1 installation, you will need to download the LMS 2.6 megapatch from the Cisco Software Center, at http://www.cisco.com/public/sw-center/cw2000/lan-planner.shtml.

Instructions on the available methods for downloading software and images from Cisco.com are available; refer to http://www.cisco.com/public/sw-center/sw-usingswc.shtml.

Note If you are performing a new installation of DFM and LMS, use the software from the CD-ROMs supplied.

Gathering Information to Provide During Installation

You might need to supply the following information while you are installing DFM:

•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.3 (Includes CiscoView) on Solaris.

•License information—If you must supply license information, the installation script prompts you to enter 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 already obtained a license file, provide the path. 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 a PIN and a PAK.

•You might be interested in the following information:

–Upgrading Your Evaluation License

–Licensing Reminders

Installing LMS 2.6

DFM is part of the LAN Management Solution (LMS). This section details how to install the application. For more information, refer to the Quick Start Guide for LAN Management Solution 2.6.

•Be aware of the following:

–You must install LMS 2.5.1 applications before you can install LMS 2.6.

Table 2-2 lists the LMS 2.5.1 applications and their versions.

Table 2-2 LMS 2.5.1 Applications and Versions

Application

Version

CiscoWorks Common Services

3.0.3

Resource Manager Essentials

4.0.3

Campus Manager

4.0.3

Device Fault Manager

2.0.3

Internetwork Performance Monitor

2.6

–When you install the LMS 2.5.1 applications, you must install CiscoWorks Common Services 3.0.3 before installing any other application.

–After you have installed CiscoWorks Common Services 3.0.3, you must install each LMS 2.5.1 application separately.

LMS 2.6 Update Description

The LMS 2.6 Update is a bundle update that contains incremental versions of more than one component of the LMS 2.5.1 bundle. It is provided as a single installable and contains updates for the following applications:

•CiscoWorks Common Services 3.0.3 (includes CiscoView 6.1.2)—Common Services 3.0.4 is an incremental release over Common Services 3.0.3, and has been rolled into Common Services 3.0.5 (includes CiscoView 6.1.5), which is part of the LMS 2.6 bundle.

•Resource Manager Essentials (RME) 4.0.3—RME 4.0.4 is an incremental release over RME 4.0.3, and has been rolled into RME 4.0.5, which is part of the LMS 2.6 bundle.

•Campus Manager 4.0.3—Campus Manager 4.0.4 and Campus Manager 4.0.5 are incremental releases over Campus Manager 4.0.3. These releases have been rolled into Campus Manager 4.0.6, which is part of the LMS 2.6 bundle.

•Device Fault Manager 2.0.3—DFM 2.0.4 and DFM 2.0.5 are incremental releases over DFM 2.0.3. These releases have been rolled into DFM 2.0.6, which is part of the LMS 2.6 bundle.

There is no change in Internetwork Performance Monitor 2.6.

Recommended Order of Installation

We recommend that you install LMS 2.6 in the following order:

Step 1 CiscoWorks Common Services 3.0.3.

Step 2 Resource Manager Essentials 4.0.3.

Step 3 Campus Manager 4.0.3.

Step 4 Device Fault Manager 2.0.3.

Step 5 Internetwork Performance Monitor 2.6.

Step 6 LMS 2.6 Update.

Performing a New Installation

Use these steps to perform a fresh installation of DFM.

Step 1 Make sure your system meets these prerequisites:

•Required (or desired) operating system upgrades have been performed.

•Common Services 3.0.3 has been installed. See Installation and Setup Guide for CiscoWorks Common Services 3.0.3 (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 Close all open or active programs. Do not run other programs during the installation process.

Step 3 As root, log into the system on which you will install DFM, and mount a local or remote CD-ROM drive. For instructions on mounting the CD-ROM, see "Mounting and Unmounting on Solaris."

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

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

Step 5 Press Return to read the License Agreement.

Step 6 Press y to accept the agreement, or n to quit installation.

(If the following message is not displayed, skip to Step 8.) The following message might appear:
To ensure full use of the product features, please select one of the following:
(L) If you have a license file for this product,
you will then be prompted for the license file location.
(P) If you know only the PAK and PIN,
but have not obtained the license file.
(E) To evaluate the product only.
You can provide licensing information later if you want to fully enable the product.
Step 7 Enter one of these:

•L for license file

•P for PAK and PIN

•E for evaluation

•Q to quit

Step 8 The installation program checks for required patches and other dependencies and displays:
1) "Typical installation. Recommended for all computers."
2) "Custom installation. Select this if you want to customize the setup options."
Select one of the installation modes using its number or enter q to quit [1]
Note If you choose the Typical installation mode, DFM passwords (for user and database) will be randomly generated for you; you can view the passwords at the end of the installation. If you choose the Custom installation mode, you will be prompted to enter DFM passwords for user and database.

Step 9 The installation program displays the following installation choices (the choices might vary, depending on your configuration):
1) Install Device Fault Manager 2.0.3 
2) Install Device Fault Manager 2.0.3 HPOV-NetView adapters 
Select one of the items using its number or enter q to quit [1]
Step 10 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 11 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 12 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 you do not plan to install another LMS application after installing DFM, enter y, and the daemons are restarted.

The installation proceeds without displaying any more questions, and the system prompt appears. The installation program copies the files to the CiscoWorks default installation directory /opt/CSCOpx (NMSROOT).

Step 13 Depending upon your configuration, you may need to do the following:

•If you purchased an upgrade license of DFM 2.0.3 (because you were formerly using DFM 1.2.x), the following warning message is displayed when the installation completes:
WARNING: Please run the program <NMSROOT>/bin/dfmValidateUpgrade.sh
WARNING: to validate that this is an upgrade.
If you see this message, you must run the program after the installation completes. (See Step 2.)

•If you did not restart the CiscoWorks daemons in Step 12, you are prompted to restart the daemons now, as follows:
/etc/init.d/dmgtd start
•If you did not register DFM with the ACS server in Step 11, 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 14 Unmount and eject the CD-ROM.

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

Step 15 Specify the clients that are allowed to connect to the DFM server. (DFM provides this fine-grain control as an additional security feature.)

a. Unregister the daemons with the daemon manager. (NMSROOT is the default installation directory, normally /opt/CSCOpx.)

•For DfmServer:
NMSROOT/bin/pdcmd -u DfmServer
•For DfmBroker:
NMSROOT/bin/pdcmd -u DfmBroker
b. Decide which hosts you want to specify, using the --accept option with arguments shown in Table 2-3.

Table 2-3 Arguments to the --accept Option

Argument

Description

host1,host2,...

Allow only host1,host2,... to connect to the server. If the hostname is registered with DNS, you can specify the client by hostname. Otherwise, specify explicit IP addresses in a comma-separated list. Hostnames are resolved to one or more IP addresses, which are then used (the server does not use reverse lookups to determine the name of a connecting host).

Note If you specify the clients as hostnames, be sure the hostnames are registered with DNS, especially if you are using DHCP.

=any

Allow all incoming connections (default).

For example, this command fragment would allow connections only from hosts lucy and ethel:
--accept=lucy,ethel
Note To allow connections from processes running on the same host, specify the host's name; do not use "localhost." This is because connections made using the DFM Broker will appear to come from the DFM Broker's host. Only connections that explicitly specify "localhost" as the target address will appear to come from localhost. Such target addresses might result in configurations that forward incoming connections (possibly through software that provides an encrypted tunnel, for example).

c. Re-register the daemons with the daemon manager, specifying the clients that can connect to the broker and server. In this example, the DFM broker port is 9002, and lucy and ethel are the clients. (NMSROOT is the default installation directory, normally /opt/CSCOpx.)

•For DfmBroker (the following command is one line):
NMSROOT/bin/pdcmd -r DfmBroker -e NMSROOT/objects/smarts/bin/brstart -f "--output --port=9002 
--accept=lucy,ethel --restore=NMSROOT/objects/smarts/conf/broker.rps"
•For DFMServer (the following command is one line):
NMSROOT/bin/pdcmd -r DfmServer -e NMSROOT/objects/smarts/bin/sm_server -d DfmBroker -f 
"--bootstrap=DFM_bootstrap.conf --accept=lucy,ethel --output --name=DFM"
d. Make sure that the client names and current IP addresses are registered with DNS if one or both of the following apply:

•You are running DHCP

•You specified the clients with hostnames

Installing the LMS 2.6 Update

The LMS 2.6 Update is a single installable bundle update containing these incremental versions of LMS applications:

•Common Services 3.0.5 (Includes CiscoView 6.1.5)

•Resource Manager Essentials 4.0.5

•Campus Manager 4.0.6

•Device Fault Manager 2.0.6

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 December 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.

The LMS 2.6 Update is installed in the same directory as LMS 2.5.1. The following sections describe the procedure for:

•Installing the Single Large File Update

•Installing the Multiple Small Files Update

Installing the Single Large File Update

To install the Single Large File update:

Step 1 Locate the DFM software:

a. If this is the first time you have installed DFM and you are installing it from the LMS 2.6 Update CD-ROM, mount the CD-ROM.

b. If you have an existing DFM installation, download the LMS 2.6 megapatch from Cisco.com at http://www.cisco.com/public/sw-center/cw2000/lan-planner.shtml.

Note Instructions on the available methods for downloading software and images from Cisco.com are available; refer to http://www.cisco.com/public/sw-center/sw-usingswc.shtml.

Step 2 Change the directory to LMS26_sol by entering:
# cd LMS26_sol
Step 3 Run the installation setup script by entering:
# sh setup.sh
or
# ./setup.sh
A prompt appears:
Press Enter to read/browse the following license agreement:
Step 4 Press Return to read the license agreement.

The following message appears at the end of the license agreement:
Do you accept all the terms of the License Agreement? (y/n) [n]:
Step 5 Enter y to accept the license agreement and proceed with the installation, or enter n to quit the installation.

Based on your LMS 2.5.1 installation, the new updates are listed.

The following message appears:
LMS 2.6 update
=========================================================
New Updates to be installed :
CiscoWorks Common Services 3.0.5 update
CiscoView 6.1.5 update
Resource Manager Essentials 4.0.5 update
Campus Manager 4.0.6 update
Device Fault Manager 2.0.6 update
Do you want to continue the installation:? (y/n) [y]:
Step 6 Enter y.
The following message appears:
INFO: There will be no more user interaction.
INFO: Exiting installation beyond this point might result in system instability.
Do you want to continue the installation? (y/n) [y]:
Step 7 Enter y.

The following messages appear:
To ensure that you retain the latest device support,
please install the latest Device Packages from CCO @
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-rme
Please refer to the Installation and Setup Guide for details.
The above message appears only if you have installed the update for RME.
To ensure that you retain the latest device support and bug fixes, please install
the latest Service Pack (SP) for Campus Manager 4.0.6
You can download the latest SP from 
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-campus.
Please refer to the Installation and Setup Guide for details.
User Tracking Utility 1.0 is not compatible with Campus Manager 4.0.3
User Tracking Utility 1.1.1 is available for Campus Manager 4.0.3
You can download the latest UTU from 
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-campus-crypto.
The above messages appear only if you have installed the update for Campus Manager.
If you plan to install any of the LMS 2.5 applications later, you must reinstall 
CiscoWorks LMS 2.5 Dec 2005 Update after installing these applications.
The installation completes without displaying more questions and the system prompt appears.

Installing the Multiple Small Files Update

To install the Multiple Small Files update:

Step 1 Locate the software:

•If this is a new installation, mount the LMS 2.6 Update CD-ROM.

•If you have an existing installation, download the LMS 2.6 megapatch from Cisco.com.

Note Instructions on the available methods for downloading software and images from Cisco.com are available; refer to http://www.cisco.com/public/sw-center/sw-usingswc.shtml.

Step 2 Run the installation setup script by entering:
# sh lms26_sol_installer.sh
•If you have not downloaded all of the Multiple Small Files, an error message appears:
ERROR: You have not downloaded all the above files  
ERROR: Please download all the above files and  
ERROR: then run this script.
Download all of the Multiple Small Files.

•If you have downloaded all of the Multiple Small Files, a message appears:
INFO: You have downloaded all the necessary files
INFO: creating the zip file from the downloaded files
The update installation starts by displaying this message:
Press Enter to read/browse the following license agreement:
Step 3 Press Return to read the license agreement.

The License agreement appears and the following message appears at the end of the license agreement:
Do you accept all the terms of the License Agreement? (y/n) [n]:
Step 4 Enter y to accept the license agreement and proceed with the installation, or enter n to quit the installation.

Based on your LMS 2.5 installation, the new updates are listed.

The following message appears:
LMS 2.6 update
=========================================================
New Updates to be installed :
CiscoWorks Common Services 3.0.5 update
CiscoView 6.1.5 update
Resource Manager Essentials 4.0.5 update
Campus Manager 4.0.6 update
Device Fault Manager 2.0.6 update
Do you want to continue the installation:? (y/n) [y]:
Step 5 Enter y.

The following message appears:
INFO: There will be no more user interaction.
INFO: Exiting installation beyond this point might result in system instability.
Do you want to continue the installation? (y/n) [y]:
Step 6 Enter y.

The following messages appear:
To ensure that you retain the latest device support,
please install the latest Device Packages from CCO @
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-rme
Please refer to the Installation and Setup Guide for details.
The above message appears only if you have installed the update for RME:
To ensure that you retain the latest device support and bug fixes, please install the 
latest Service Pack (SP) for Campus Manager 4.0.6
You can download the latest SP from 
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-campus.
Please refer to the Installation and Setup Guide for details.
User Tracking Utility 1.0 is not compatible with Campus Manager 4.0.3
User Tracking Utility 1.1.1 is available for Campus Manager 4.0.3
You can download the latest UTU from 
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-campus-crypto.
The above messages appear only if you have installed the update for Campus Manager.
If you plan to install any of the LMS 2.5 applications later, you must reinstall 
CiscoWorks LMS 2.5 Dec 2005 Update after installing these applications.
The installation completes without displaying more questions and the system prompt appears.

When the Installation Is Complete

When the installation is complete you should complete the following tasks.

Step 1 To verify that the DfmServer process is running, log into the CiscoWorks home page as the administrator and select Common Services > Server > Admin > Processes.

Step 2 If you purchased an upgrade license of DFM 2.0.6 (because you were formerly using DFM 1.2.x), and were prompted to validate the upgrade in Step 13, run the following command:
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 use DFM; 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.)

Step 3 If you plan to use the HPOV-NetView adapters with Device Fault Manager 2.0.6, make sure the machine running DFM is registered with DNS.

Step 4 To use DFM, select Device Fault Manager from the CiscoWorks home page.

If you had any errors, check the installation log, /var/tmp/ciscoinstall.log. The Cisco Technical Assistance Center (TAC) might ask you to send them the installation log.

If you install HP OpenView or NetView later, you will have to either configure DFM SNMP trap receiving to use another port (as described in Configuring SNMP Trap Receiving and Forwarding), or reinstall DFM.

To integrate DFM with remote versions of HP OpenView or NetView, you must install the HPOV-NetView adapters as described in Installing and Upgrading HPOV-NetView Adapters.

Reinstalling DFM

You can use this procedure to reinstall DFM or to reinstall the HPOV-NetView adapters.

Step 1 Close all open or active programs. Do not run other programs during the reinstallation process.

Step 2 As root, log into the system on which you will reinstall DFM, and mount a local or remote CD-ROM drive. For instructions on mounting the CD-ROM, see "Mounting and Unmounting on Solaris."

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

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

Step 4 You are prompted to accept (and view) the license agreement. Press Return.

Step 5 The installation program stops CiscoWorks, performs a requirements check, and displays the following installation choices:
1) "Typical installation. Recommended for all computers."
2) "Custom installation. Select this if you want to customize the setup options.
Step 6 Enter 1 or 2 and press Return. The installation program displays the following prompt:
INFO: Device Fault Manager 2.0.6 has been detected on your system, are you sure you want 
to reinstall? (y/n) - y
Step 7 Enter y and press Return.

Step 8 If you reinstalled only the HPOV-NetView adapters, you are prompted to enter the name of the machine running DFM. Enter the name of the host (the default is localhost).

Note Make sure the machine running DFM is registered with DNS.

The reinstallation program checks dependencies and system requirements.

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

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

Step 9 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]:
Do one of the following:

•If you plan to install another LMS application after installing DFM, enter n, and the daemons are not restarted.

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

The reinstallation proceeds without displaying any more questions, and the system prompt appears. The reinstallation program copies the files to the directory where DFM was originally installed.

Step 10 If you did not restart the CiscoWorks daemons in Step 9, you are prompted to restart the daemons now, as follows:
/etc/init.d/dmgtd start
Step 11 Unmount and eject the CD-ROM.

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

Step 12 Specify the clients that are allowed to connect to the DFM server. (DFM provides this fine-grain control as an additional security feature.) (NMSROOT is the default installation directory, normally /opt/CSCOpx.)

a. Unregister the daemons with the daemon manager:

•For DfmServer:
NMSROOT/bin/pdcmd -u DfmServer
•For DfmBroker:
NMSROOT/bin/pdcmd -u DfmBroker
b. Decide which hosts you want to specify using the --accept option with arguments shown in Table 2-4.

Table 2-4 Arguments to the --accept Option

Argument

Description

host1,host2,...

Allow only host1,host2,... to connect to the server. If the hostname is registered with DNS, you can specify the client by hostname. Otherwise, specify explicit IP addresses in a comma-separated list. Hostnames are resolved to one or more IP addresses, which are then used (the server does not use reverse lookups to determine the name of a connecting host).

Note If you specify the clients as hostnames, be sure the hostname is registered with DNS, especially if you are using DHCP.

=any

Allow all incoming connections (default).

For example, the following command fragment would allow connections only from hosts lucy and ethel:
--accept=lucy,ethel
Note To allow connections from processes running on the same host, specify the host's name; do not use "localhost." This is because connections made using the DFM Broker will appear to come from the DFM Broker's host. Only connections that explicitly specify "localhost" as the target address will appear to come from localhost. Such target addresses might result in configurations that forward incoming connections (possibly through software that provides an encrypted tunnel, for example).

c. Re-register the daemons with the daemon manager, specifying the clients that can connect to the broker and server. In this example, the DFM broker port is 9002 and lucy and ethel are the clients. (NMSROOT is the default installation directory, normally /opt/CSCOpx.)

•For DfmBroker (the following command is one line):
NMSROOT/bin/pdcmd -r DfmBroker -e NMSROOT/objects/smarts/bin/brstart -f "--output --port=9002 
--accept=lucy,ethel --restore=NMSROOT/objects/smarts/conf/broker.rps"
•For the DFM server (the following command is one line):
NMSROOT/bin/pdcmd -r DfmServer -e NMSROOT/objects/smarts/bin/sm_server -d DfmBroker -f 
"--bootstrap=DFM_bootstrap.conf --accept=lucy,ethel --output --name=DFM"
d. Make sure that the client names and current IP addresses are registered with DNS if one or both of the following apply:

•You are running DHCP

•You specified the clients with hostnames

Step 13 To verify that the DfmServer process is running, log into the CiscoWorks home page as the administrator and select Common Services > Server > Admin > Processes.

Step 14 To use DFM, select Device Fault Manager from the CiscoWorks home page.

Step 15 If you use remote HPOV-NetView adapters, make sure the machine running DFM is registered with DNS.

If you had any errors, check the installation log, /var/tmp/ciscoinstall.log. The Cisco Technical Assistance Center (TAC) might ask you to send them the installation log.

Uninstalling DFM

Caution You must use the CiscoWorks uninstallation program to remove DFM from your system. If you try to remove the files and programs manually, you can seriously damage your system.

Step 1 As root, log into the system on which DFM is installed, and enter the following to start the uninstallation program (NMSROOT is the DFM installation directory):
# cd /
# NMSROOT/bin/uninstall.sh
The following prompt appears (the uninstallation choices might vary, depending on your configuration; see Table 1-1):
1) CiscoWorks Common Services 3.0.5
2) CiscoView 6.1.2
3) Integration Utility 1.6
4) Device Fault Manager 2.0.6
5) all of the above
Select one of the items using its number or enter q to quit [q]
(Uninstalling DFM also removes DFM IDUs.)

Step 2 Enter the appropriate number and press Return. The following prompt appears:
Are you sure you want to uninstall: the name of the selection (y/n)? [n]
Step 3 Enter y and press Return to remove your selections. The following prompt appears:
Delete the CiscoWorks packages? (y/n) [y]
Step 4 Press Return.

Ignore all messages that ask if you want to remove packages. The uninstallation program does not accept input to these questions.

When the uninstallation program finishes, the following message appears:
All files were deleted successfully.
The uninstallation program removes the DFM application and updates the system. To install DFM again, see Performing a New Installation.

If you had any errors, check the uninstallation log, /var/tmp/ciscouninstall.log. The Cisco Technical Assistance Center (TAC) might ask you to send them the uninstallation log.

Installing and Upgrading HPOV-NetView Adapters

When you install DFM on a system with HP OpenView or NetView, the DFM installation script installs the HPOV-NetView adapters. These adapters take the traps that managed devices send to HP OpenView or Netview and forward them to DFM. For information on supported HP OpenView and NetView versions, see Supported NMS Integration.

This section explains how to install or upgrade the HPOV-NetView adapters on a remote host so the adapters can exchange information with DFM on a local host. You can also use these procedures to reinstall the HPOV-NetView adapters.

Note The HPOV-NetView adapter installation software is not supplied with LMS 2.6. You can install or upgrade the adapters from the DFM 2.0.3 CD-ROM.

If you upgrade a local version of DFM 1.2.x, you must also upgrade remote HPOV-NetView adapters.

Note To upgrade remote HPOV-NetView adapters, you must first remove the old adapters and then install the new ones.

Note If you move DFM to a different machine, or you want to use a different instance of DFM, you must reinstall the HPOV-NetView adapters.

Reinstalling the HPOV-NetView Adapters on a Local Host

If you install NetView or HP OpenView on the local host after you have installed DFM, you should reinstall the HPOV-NetView adapters to configure them appropriately. See Reinstalling DFM.

Installing or Upgrading the HPOV-NetView Adapters on a Remote Host

Step 1 If you want to upgrade a previous version of the HPOV-NetView adapters, remove the adapters as described in Uninstalling the HPOV-NetView Adapters.

Step 2 Make sure the following are installed on the remote host:

•HP OpenView or NetView

•Common Services 3.0.3

Step 3 As root, log into the machine on which you will install or upgrade the HPOV-NetView adapters, and mount a local or remote CD-ROM drive. For instructions on mounting the CD-ROM, see "Mounting and Unmounting on Solaris."

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

Note Be sure to install the adapter on the same drive as HP OpenView or NetView.

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

Step 5 Enter the following to start the installation program:
# ./setup.sh
The installation program stops CiscoWorks, performs a requirements check, and displays the following installation choices (the choices might 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 6 Enter the appropriate number for the HPOV-NetView adapters and press Return. (For more information on installation components, see Table 1-1.)

The installation program stops HP OpenView or NetView and copies the files to the directory in which CiscoWorks is installed.

Step 7 Eject the CD-ROM.

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

Step 8 Restart HP OpenView or NetView to activate the adapter (using the ovstart or nvstart command).

CiscoWorks automatically configures the HPOV-NetView adapters to forward SNMP traps from HP OpenView and NetView to DFM.

If you had any errors during installation or upgrade, check the installation log, /var/tmp/ciscoinstall.log. The Cisco Technical Assistance Center (TAC) might ask you to send them the installation log.

Uninstalling the HPOV-NetView Adapters

When you remove a local version of DFM, the HPOV-Netview adapters are also removed. To remove remote adapters, follow the instructions in this section.

Caution You must use the following uninstallation programs to uninstall the adapters from your system. If you try to remove the files and programs manually, you can seriously damage your system.

Step 1 Log in as root on the target machine.

Step 2 Run the uninstallation shell script (NMSROOT is the DFM installation directory):
NMSROOT/bin/uninstall.sh
The following prompt appears (depending on your configuration):
1) CiscoWorks Common Services 3.0.3
2) Device Fault Manager 2.0.6 HPOV-NetView adapters
3) all of the above
Step 3 Enter the appropriate number for the HPOV-NetView adapters and press Return. The following prompt appears:
Are you sure you want to uninstall: Device Fault Manager HPOV-NetView adapters (y/n)? [n]
Step 4 Enter y and press Return

The following prompt appears:
Delete the CiscoWorks packages? (y/n)? [y]
Step 5 Press Return to uninstall your selections.

When the uninstallation program finishes, the following message appears:
All files were deleted successfully.