Installation and Setup Guide for Device Fault Manager 1.2 and 1.2 Updated for Common Services Version 2.2 on Windows (With LMS 2.2) - Installing Device Fault Manager [CiscoWorks Device Fault Manager]

Table Of Contents

Installing Device Fault Manager

Performing a New Installation

Performing a New Installation of DFM 1.2

Performing a New Installation of DFM 1.2 Updated for Common Services Version 2.2

Upgrading Device Fault Manager

Upgrading DFM 1.1 to DFM 1.2

Upgrading DFM 1.1 to DFM 1.2 Updated for Common Services Version 2.2

Upgrading DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2

Exporting Local DFM Information to an Upgraded Remote DFM Host

Reinstalling Device Fault Manager

Reinstalling DFM 1.2

Reinstalling DFM 1.2 Updated for Common Services Version 2.2

Removing Device Fault Manager

Installing and Upgrading Adapters

Types of Adapters: Local and Remote

Local Adapters

Remote Adapters

Configuring and Starting Adapters

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

Installing or Upgrading the HPOV-NetView Adapter on a Remote Host Running CiscoWorks

Installing or Upgrading the HPOV-NetView Adapter on a Remote Host Not Running CiscoWorks

Installing or Upgrading the RME Adapter on a Remote Host

Installing or Upgrading the RME Adapter on a Remote DFM Host

Removing Adapters

Removing the HPOV-NetView Adapter from a Remote Host

Removing the HPOV-NetView Adapter from a Remote Host Running CiscoWorks

Removing the HPOV-NetView Adapter from a Remote Host Not Running CiscoWorks

Removing the RME Adapter from a Remote Host

Installing Device Fault Manager

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

•Performing a New Installation

•Upgrading Device Fault Manager

•Reinstalling Device Fault Manager

•Removing Device Fault Manager

•Installing and Upgrading Adapters

•Removing Adapters

This chapter contains instructions for installing both DFM 1.2 and DFM 1.2 Updated for Common Services Version 2.2. Differences in the installations are noted. Keep the following in mind when deciding whether to upgrade to DFM 1.2 Updated for Common Services Version 2.2:

•Upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2 allows your system to manage devices that were not supported when DFM 1.2 was released, and also provides a number of DFM bug fixes. The devices and bug fixes are listed in the Release Notes for Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Windows.

•If you do not plan to upgrade to Common Services 2.2, it may be easier to download and install the latest DFM IDU from: http://www.cisco.com/en/US/products/sw/cscowork/ps2421/prod_upgrades_and_downloads.html.

The IDU includes the same functionality as DFM 1.2 Updated for Common Services Version 2.2, plus additional device support and bug fixes. (If you do upgrade to Common Services 2.2, you can always download and install the DFM IDU after upgrading or re-enabling DFM from the CD.)

•If you upgrade to DFM 1.2 Updated for Common Services Version 2.2, and your system contains installed IDUs that were released after DFM 1.2.3, you will not lose any existing device support.

Performing a New Installation

This section explains how to perform these new installations:

•Performing a New Installation of DFM 1.2

•Performing a New Installation of DFM 1.2 Updated for Common Services Version 2.2

Performing a New Installation of DFM 1.2

Follow these steps to perform a new DFM 1.2 installation on a Windows system.

Step 1 Make sure your system meets these prerequisites:

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

•All installed applications are supported by CD One, 5th Edition. Applications not supported by CD One, 5th Edition will be disabled when you upgrade CD One.

•CD One, 5th Edition has been installed. (Refer to Installation and Setup Guide for CD One on Windows.)

•If desired, HP OpenView or NetView has been installed (to use the HPOV-NetView Adapter with a local version of HP OpenView or NetView).

Note NetView must be installed on the same drive as DFM (for local integration) or on the same drive as the HPOV-NetView Adapter (for remote integration).

•If HP OpenView is installed and operational, stop all HP OpenView services (or the installation will take significantly longer).

Step 2 Close all open or active programs. Do not run other programs during the installation process.

Step 3 As the local administrator, log on to the machine on which you will install the DFM software, and insert the DFM CD-ROM into the CD-ROM drive. The installer window appears, asking you if you want to install DFM.

Note If the CD-ROM is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click Setup.exe to restart the process.

Step 4 Click Install. The Welcome window appears.

Step 5 Click Next. The Setup Type dialog box appears.

Step 6 Select Typical to install the complete DFM package, which contains DFM, the DFM incremental device support base package, the HPOV-NetView Adapter, and the RME Adapter. (For more information on installation components, refer to Table 1-1.)

Step 7 Click Next. The Start Copying Files window appears.

Step 8 Click Next. The installation program checks dependencies and system requirements.

Step 9 The Requirements Verification dialog box displays the results of the requirements check and advises whether the installation can continue. One of the following should then occur:

•If minimum requirements are met, click OK. The Setup screen appears, displaying installation progress while files are copied. The Setup Complete dialog box appears.

•If recommended requirements are not met, an error message appears. To continue the installation, click OK.

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 the SNMP Trap Adapter to use a different UDP port, such as port 9000. (Refer to the "Configuring the SNMP Trap Adapter" section.)

Step 10 A dialog box appears, asking if you want to connect this instance of DFM with VHM 1.0. Do one of the following:

•If you will be using a remote version of VHM 1.0 with DFM, click Yes.

The installation program copies the files to the CiscoWorks default installation directory C:\Program Files\CSCOpx (NMSROOT). The Restart window appears.

Proceed to Step 13.

•If you will not be using a remote version of VHM 1.0 with DFM, click No. Proceed to Step 11.

Note You must give the same answer to this question when you install adapters. If you answer No and provide a DFM username and password, you must provide the same username and password pair when you install adapters.

Step 11 The Setup window appears. In the username field, enter the DFM username. In the password field, enter the DFM password.

Note You can change your username and password. Refer to the User Guide for Device Fault Manager, available from the online help, for more information.

Step 12 Click Next. The installation program copies the files to the CiscoWorks default installation directory C:\Program Files\CSCOpx (NMSROOT). The Restart window appears.

Step 13 Remove the DFM CD-ROM from the drive, and store the CD-ROM in a secure, climate-controlled area for safekeeping.

Step 14 Click Finish to reboot the machine.

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:

–For DFM notification adapters:
# NMSROOT\bin\pdcmd.exe -u DfmFileNotifier
# NMSROOT\bin\pdcmd.exe -u DfmTrapNotifier
# NMSROOT\bin\pdcmd.exe -u DfmMailNotifier
–For DfmServer:
# NMSROOT\bin\pdcmd.exe -u DfmServer
–For DfmBroker:
# NMSROOT\bin\pdcmd.exe -u DfmBroker
b. Decide which hosts you want to specify using the --accept option with arguments shown in Table 2-1.

Note If you specify registration options using pdcmd, you must re-run your command whenever the daemon manager restarts.

Table 2-1 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, 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 may result in configurations that forward incoming connections (such as through software that provides an encrypted tunnel).

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):

–For DfmBroker (the following command is one line):
# NMSROOT\bin\pdcmd.exe -r DfmBroker -e NMSROOT\objects\smarts\bin\brstart.exe -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.exe -r DfmServer -e NMSROOT\objects\smarts\bin\sm_server.exe -d 
DfmBroker -f "--bootstrap=DFM_bootstrap.conf --accept=lucy,ethel --output --name=DFM"
–For DFM notification adapters (the following commands are each one line, and will register the adapter processes to automatically start upon reboot):
# NMSROOT\bin\pdcmd.exe -r DfmFileNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=filelog --output=sm_file_notifier"
# NMSROOT\bin\pdcmd.exe -r DfmTrapNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=trap --output=sm_trap_notifier"
# NMSROOT\bin\pdcmd.exe -r DfmMailNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=mail --output=sm_mail_notifier"
If you do not want the daemons to start after a reboot, add the -n option to the end of the command, as in this File Notifier Adapter example:
# NMSROOT\bin\pdcmd.exe -r DfmFileNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=filelog --output=sm_file_notifier" 
-n
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 16 To verify that the DfmServer process is running, log on to the CiscoWorks desktop as the administrator and select Server Configuration >
Administration > Process Management > Process Status.

Note If your client does not have the Java plug-in, you will receive a message asking if you want to install it. The plug-in is required for DFM 1.2.

Step 17 If you plan to use remote adapters with Device Fault Manager 1.2, perform these steps:

a. Make sure the machine running the DfmBroker is registered with DNS.

b. Install all remote adapters as described in the "Installing and Upgrading Adapters" section.
Step 18 To use DFM, select Device Fault Manager from the CiscoWorks navigation tree.

If the standard UDP trap port (162) is being used by another NMS, you must configure the SNMP Trap Adapter to use a different UDP port, such as port 9000. Refer to the "Configuring the SNMP Trap Adapter" section.

If you install another NMS after installing DFM, you must:

1. Configure DFM to forward traps to the listening port for the NMSs. Refer to the "Enabling DFM to Send Traps to NMSs" section.

2. Make sure the NMSs are configured to receive traps at the port you specify in Step 1. Refer to the appropriate documentation for the NMS.

When HP OpenView or NetView is restarted, CiscoWorks automatically configures the adapters to foward SNMP traps from HP OpenView or NetView to DFM. If you install HP OpenView or NetView later, you will have to either configure the SNMP Trap Adapter to use another port (as described in the "Configuring the SNMP Trap Adapter" section), or reinstall DFM.

If a local version of Essentials is already installed (or is installed later), CiscoWorks automatically configures the adapters to forward Essentials inventory device information to DFM. To do this with remote versions of HP OpenView, NetView, or Essentials, you must install the remote adapters as described in the "Installing and Upgrading Adapters" section.

If you had any errors during installation, check the installation log in the root directory on the drive where the operating system is installed. Each installation creates a new log file. (For example, the CiscoWorks installation might create C:\cw2000_in001.log, the DFM installation might create C:\cw2000_in002.log, and so forth.) The Technical Assistance Center (TAC) might ask you to send them the installation log.

Performing a New Installation of DFM 1.2 Updated for Common Services Version 2.2

Follow these steps to perform a new installation of DFM 1.2 Updated for Common Services Version 2.2 on a Windows system.

Note You can also use this procedure to upgrade from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2 (as described in the "Upgrading DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2" section).

Step 1 Make sure your system meets these prerequisites:

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

•All installed applications are supported by CD One, 5th Edition, or Common Services 2.2. Applications not supported by CD One, 5th Edition, or Common Services 2.2, will be disabled when you upgrade CD One.

•CD One, 5th Edition, or Common Services 2.2 has been installed. (Refer to Installation and Setup Guide for CD One on Windows or Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows.)

•If desired, HP OpenView or NetView has been installed (to use the HPOV-NetView Adapter with a local version of HP OpenView or NetView).

Note NetView must be installed on the same drive as DFM (for local integration) or on the same drive as the HPOV-NetView Adapter (for remote integration).

•If HP OpenView is installed and operational, stop all HP OpenView services (or the installation will take significantly longer).

Step 2 Close all open or active programs. Do not run other programs during the installation process.

Step 3 As the local administrator, log on to the machine on which you will install the DFM software, and insert the DFM CD-ROM into the CD-ROM drive. The installer window appears, asking you if you want to install DFM.

Note If the CD-ROM is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click Setup.exe to restart the process.

Step 4 Click Install. The Welcome window appears.

Step 5 Click Next. The Software License Agreement window appears.

Note You may be asked to validate your DFM image if you are installing DFM using a Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.2). If you are prompted to validate the image, insert a DFM 1.2 (or earlier) CD into one of your system drives. (If autoplay is enabled, a new installation window will open whenever a CD is inserted. Click Cancel in each new installation window.) If the DFM image cannot be validated — that is, if you do not have a DFM 1.2 (or earlier) CD — the installation cannot proceed. Contact your Cisco sales representative.

Step 6 To accept the agreement and continue the installation, click Yes.

Step 7 If your system contains installed IDUs that were released after DFM 1.2.3 (such as DFM 1.2 IDU 1.2.4), the Enable DFM window opens, displaying the following message:
The installation program has detected a newer version of DFM already 
on your system. The newer version is disabled. Do you want to enable 
it?
Click "Yes" to enable the newer version of DFM.
Click "No" to abort the installation.
Do one of the following:

•To enable DFM, click Yes. Because continuing the installation would add no new functionality, further DFM installation is not required, and the installation program exits. To re-establish settings that were lost when CiscoWorks Common Services 2.2 was installed (and DFM was disabled), proceed to Step 15 in the "Performing a New Installation of DFM 1.2" section.

•To keep DFM disabled, select No. DFM remains disabled, and the installation program exits.

Step 8 The Setup Type dialog box appears. Select Typical to install the complete DFM package, which contains DFM, the DFM incremental device support base package, the HPOV-NetView Adapter, and the RME Adapter. (For more information on installation components, refer to Table 1-1.)

Step 9 Click Next. The installation program checks dependencies and system requirements.

Step 10 The System Requirements window appears, displays the results of the requirements check, and advises whether installation can continue. One of the following should then occur:

•If minimum requirements are met, click Next.

•If recommended requirements are not met, an error message appears. To continue the installation, click Next.

Step 11 The Summary dialog box displays your selected settings. Click Next.

Step 12 The Setup window appears, displaying installation progress while files are copied.

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 the SNMP Trap Adapter to use a different UDP port, such as port 9000. (Refer to the "Configuring the SNMP Trap Adapter" section.)

Step 13 To finish installing DFM 1.2 Updated for Common Services Version 2.2, follow Step 10 through Step 18 in the "Performing a New Installation of DFM 1.2" section.

Upgrading Device Fault Manager

Refer to these sections for procedures on how to perform these upgrades:

•Upgrading DFM 1.1 to DFM 1.2

•Upgrading DFM 1.1 to DFM 1.2 Updated for Common Services Version 2.2

•Upgrading DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2

•Exporting Local DFM Information to an Upgraded Remote DFM Host

Upgrading DFM 1.1 to DFM 1.2

You can upgrade Device Fault Manager 1.1 (installed with or without IDS 1.1.x patches) on local or remote machines. If desired, you can upgrade a remote machine and then export your local DFM information to the upgraded remote machine.

When you upgrade a local version of DFM 1.1 to DFM 1.2, the upgrade program saves and restores the DFM 1.1 seed file, adapter files, repository, and consoles. If desired, you can manually restore the log files from NMSROOT\objects\smarts\logs.

Note Customized remote consoles are not saved after upgrade.

Follow these steps to upgrade a local host to DFM 1.2:

Step 1 Make sure your system meets these prerequisites:

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

•All installed applications are supported by CD One, 5th Edition. Applications not supported by CD One, 5th Edition will be disabled when you upgrade CD One.

•CD One, 5th Edition has been installed. (Refer to Installation and Setup Guide for CD One on Windows.)

•If desired, HP OpenView or NetView has been installed (to use the HPOV-NetView Adapter with a local version of HP OpenView or NetView).

Note NetView must be installed on the same drive as DFM (for local integration) or on the same drive as the HPOV-NetView Adapter (for remote integration).

•If HP OpenView is installed and operational, all HP OpenView services have been stopped. (If not, the installation will take significantly longer).

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

Step 3 As the local administrator, log on to the machine on which you will install the DFM software, and insert the DFM CD-ROM into the CD-ROM drive. The installer window appears, asking you if you want to install DFM.

Note If the CD-ROM is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click Setup.exe to restart the process.

Step 4 Click Install. The Welcome window appears.

Step 5 Click Next. The Setup Type dialog box appears.

Step 6 Select Typical to upgrade the complete DFM package, which contains DFM, the DFM incremental device support base package, the HPOV-NetView Adapter, and the RME Adapter. (For more information on upgrade components, refer to Table 1-1.)

Step 7 Click Next. The Start Copying Files window appears.

Step 8 Click Next. The installation program checks dependencies and system requirements.

Step 9 The Requirements Verification dialog box displays the results of the requirements check and advises whether the installation can continue. One of the following should then occur:

•If minimum requirements are met, click OK. The Setup screen appears, displaying installation progress while files are copied. The Setup Complete dialog box appears.

•If recommended requirements are not met, an error message appears. To continue the installation, click OK.

•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 the SNMP Trap Adapter to use a different UDP port, such as port 9000. (Refer to the "Configuring the SNMP Trap Adapter" section.)

Step 10 A dialog box appears, asking if you want to connect this instance of DFM with VHM 1.0. Do one of the following:

•If you will be using a remote version of VHM 1.0 with DFM, click Yes.

The installation program copies the files to the CiscoWorks default installation directory C:\Program Files\CSCOpx (NMSROOT).

Proceed to Step 13.

•If you will not be using a remote version of VHM 1.0 with DFM, click No. Proceed to Step 11.

Note You must give the same answer to this question when you install adapters. If you answer No and provide a DFM username and password, you must provide the same username and password pair when you install adapters.

Step 11 The Setup window appears. In the username field, enter the DFM username. In the password field, enter the DFM password.

Note You can change your username and password. Refer to the User Guide for Device Fault Manager, available from the online help, for more information.

Step 12 Click Next. The installation program copies the files to the CiscoWorks default installation directory C:\Program Files\CSCOpx (NMSROOT).

Step 13 A dialog box appears, reminding you to run rediscovery from the Administration Console; this procedure is described in Step 19. Click OK. The Restart window appears.

Step 14 Remove the DFM CD-ROM from the drive, and store the CD-ROM in a secure, climate-controlled area for safekeeping.

Step 15 Click Finish to reboot the machine.

Note You must reboot the machine to make sure the DFM broker attaches to the correct port (9002).

Step 16 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:

–For DFM notification adapters:
# NMSROOT\bin\pdcmd.exe -u DfmFileNotifier
# NMSROOT\bin\pdcmd.exe -u DfmTrapNotifier
# NMSROOT\bin\pdcmd.exe -u DfmMailNotifier
–For DfmServer:
# NMSROOT\bin\pdcmd.exe -u DfmServer
–For DfmBroker:
# NMSROOT\bin\pdcmd.exe -u DfmBroker
b. Decide which hosts you want to specify using the --accept option with arguments shown in Table 2-2.

Note If you specify registration options using pdcmd, you must re-run your command whenever the daemon manager restarts.

Table 2-2 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, 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 may result in configurations that forward incoming connections (such as through software that provides an encrypted tunnel).

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):

–For DfmBroker (the following command is one line):
# NMSROOT\bin\pdcmd.exe -r DfmBroker -e NMSROOT\objects\smarts\bin\brstart.exe -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.exe -r DfmServer -e NMSROOT\objects\smarts\bin\sm_server.exe -d 
DfmBroker -f "--bootstrap=DFM_bootstrap.conf --accept=lucy,ethel --output --name=DFM"
–For DFM notification adapters (the following commands are each one line, and will register the adapter processes to automatically start upon reboot):
# NMSROOT\bin\pdcmd.exe -r DfmFileNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=filelog --output=sm_file_notifier"
# NMSROOT\bin\pdcmd.exe -r DfmTrapNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=trap --output=sm_trap_notifier"
# NMSROOT\bin\pdcmd.exe -r DfmMailNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=mail --output=sm_mail_notifier"
If you do not want the daemons to start after a reboot, add the -n option to the end of the command, as in this File Notifier Adapter example:
# NMSROOT\bin\pdcmd.exe -r DfmFileNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=filelog --output=sm_file_notifier" 
-n
d. Make sure that the client names and current IP addresses are registered with DNS if:

–You are running DHCP and/or

–You specified the clients with hostnames

Step 17 To verify that the DfmServer process is running, log on to the CiscoWorks desktop as the administrator and select Server Configuration > Administration > Process Management > Process Status.

Note If your client does not have the Java plug-in, you will receive a message asking if you want to install it. The plug-in is required for DFM 1.2.

Step 18 Make sure the DFM broker has attached to the correct port:

a. Clear the browser cache.

b. Exit the browser.

c. Reopen the browser.

Step 19 Rediscover the devices in your DFM inventory by opening the Administration Console and selecting Inventory > Inventory Collect All.

Note Depending on the number of managed devices, rediscovering the entire DFM inventory could take several hours.

Step 20 If you plan to use remote clients (such as adapters) with Device Fault Manager 1.2, perform these steps:

a. Make sure the machine running the DfmBroker is registered with DNS.

b. Upgrade all remote adapters as described in the "Installing and Upgrading Adapters" section. If the adapters are installed on a remote VHM 1.0 machine, they do not need to be upgraded.

c. For remote versions of VHM 1.0, restart the remote VHM server process.

Step 21 Proceed to the "Exporting Local DFM Information to an Upgraded Remote DFM Host" section.

If the standard UDP trap port (162) is being used by another NMS—such as Cisco Voice Manager, Traffic Director, or Real Time Monitor—you must configure the SNMP Trap Adapter to use a different UDP port, such as port 9000. Refer to the "Configuring the SNMP Trap Adapter" section.

If you install another NMS—such as Cisco Voice Manager, Traffic Director, or Real Time Monitor—after installing DFM, you must:

1. Configure DFM to forward traps to the listening port for the NMSs. Refer to the "Enabling DFM to Send Traps to NMSs" section.

2. Make sure the NMSs are configured to receive traps at the port you specify in Step 1. Refer to the appropriate documentation for the NMS.

When HP OpenView or NetView are restarted, CiscoWorks automatically configures the adapters to foward SNMP traps from HP OpenView and NetView to DFM. If you install HP OpenView or NetView later, you will have to either configure the SNMP Trap Adapter to use another port (as described in the "Configuring the SNMP Trap Adapter" section), or reinstall DFM.

If a local version of Essentials is already installed (or is installed later), CiscoWorks automatically configures the adapters to forward Essentials inventory device information to DFM. To do this with remote versions of HP OpenView, NetView, or Essentials, you must install the remote adapters as described in the "Installing and Upgrading Adapters" section.

If you had any errors during upgrade, check the installation log in the root directory on the drive where the operating system is installed. Each installation creates a new log file. (For example, the CiscoWorks CD One installation might create C:\cw2000_in001.log, the DFM installation might create C:\cw2000_in002.log, and so forth.) The Technical Assistance Center (TAC) might ask you to send them the installation log.

Upgrading DFM 1.1 to DFM 1.2 Updated for Common Services Version 2.2

When you upgrade a local version of DFM 1.1 to DFM 1.2 Updated for Common Services Version 2.2, the upgrade program saves and restores the DFM 1.1 seed file, adapter files, repository, and consoles. If desired, you can manually restore the log files from NMSROOT\objects\smarts\logs. You can also upgrade a remote machine and then export your local DFM information to the upgraded remote machine (see the "Exporting Local DFM Information to an Upgraded Remote DFM Host" section).

Note Customized remote consoles are not saved after the upgrade.

Follow these steps to upgrade a local host to DFM 1.2 Updated for Common Services Version 2.2:

Step 1 Make sure your system meets these prerequisites:

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

•All installed applications are supported by CD One, 5th Edition, or Common Services 2.2. Applications not supported by CD One, 5th Edition, or Common Services 2.2, will be disabled when you upgrade CD One.

•CD One, 5th Edition, or Common Services 2.2 has been installed. (Refer to Installation and Setup Guide for CD One on Windows or Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows.)

•If desired, HP OpenView or NetView has been installed (to use the HPOV-NetView Adapter with a local version of HP OpenView or NetView).

Note NetView must be installed on the same drive as DFM (for local integration) or on the same drive as the HPOV-NetView Adapter (for remote integration).

•If HP OpenView is installed and operational, all HP OpenView services have been stopped (if not, the installation will take significantly longer).

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

Step 3 As the local administrator, log on to the machine on which you will install the DFM software, and insert the DFM CD-ROM into the CD-ROM drive. The installer window appears, asking you if you want to install DFM.

Note If the CD-ROM is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click Setup.exe to restart the process.

Step 4 Click Install. The Welcome window appears.

Step 5 Click Next.

Step 6 If you are installing DFM on Common Services Version 2.2, the Software License Agreement window appears. To accept the agreement and continue the installation, click Yes.

Note You may be asked to validate your DFM image if you are installing DFM using a Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.2). If you are prompted to validate the image, insert a DFM 1.2 (or earlier) CD into one of your system drives. (If autoplay is enabled, a new installation window will open whenever a CD is inserted. Click Cancel in each new installation window.) If the DFM image cannot be validated — that is, if you do not have a DFM 1.2 (or earlier) CD — the installation cannot proceed. Contact your Cisco sales representative.

Step 7 The Setup Type dialog box appears. Select Typical to upgrade the complete DFM package, which contains DFM, the DFM incremental device support base package, the HPOV-NetView Adapter, and the RME Adapter. (For more information on upgrade components, refer to Table 1-1.)

The installation program checks dependencies and system requirements.

Step 8 The System Requirements window appears, displays the results of the requirements check, and advises whether installation can continue. One of the following should then occur:

•If minimum requirements are met, click Next.

•If recommended requirements are not met, an error message appears. To continue the installation, click Next.

Step 9 The Summary dialog box displays your selected settings. Click Next.

Step 10 The Setup window appears, displaying installation progress while files are copied.

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.
Step 11 To finish upgrading DFM 1.1 to DFM 1.2 Updated for Common Services Version 2.2, follow Step 10 through Step 21 in the "Upgrading DFM 1.1 to DFM 1.2" section.

Upgrading DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2

You can upgrade Device Fault Manager 1.2, 1.2.1, or 1.2.2 on local or remote machines. To perform the upgrade, follow the procedure in the "Performing a New Installation of DFM 1.2 Updated for Common Services Version 2.2" section. You do not need to do any data preservation, nor do you need to upgrade any adapters, when upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2.

Keep the following in mind when deciding whether to upgrade to DFM 1.2 Updated for Common Services Version 2.2:

•Upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2 allows your system to manage devices that were not supported when DFM 1.2 was released, and also provides a number of DFM bug fixes. The devices and bug fixes are listed in the Release Notes for Device Fault Manage 1.2 Updated for Common Services Version 2.2 on Windows.

•If you do not plan to upgrade to Common Services 2.2, it may be easier to download and install the latest DFM IDU from: http://www.cisco.com/en/US/products/sw/cscowork/ps2421/prod_upgrades_and_downloads.html.

The IDU includes the same functionality as DFM 1.2 Updated for Common Services Version 2.2, plus additional device support and bug fixes. (If you do upgrade to Common Services 2.2, you can always download and install the DFM IDU after upgrading or re-enabling DFM from the CD.)

•If you upgrade to DFM 1.2 Updated for Common Services Version 2.2, and your system contains installed IDUs that were released after DFM 1.2.3, you will not lose any existing device support.

If desired, you can upgrade a remote machine and then export your local DFM information to the upgraded remote machine. See the "Exporting Local DFM Information to an Upgraded Remote DFM Host" section for more information.

Exporting Local DFM Information to an Upgraded Remote DFM Host

This procedure exports your local DFM configuration information and imports it to a remote DFM machine that has been upgraded. This procedure applies to the following scenarios:

•Exporting local DFM 1.1 information to a remote host running DFM 1.2

•Exporting local DFM 1.1 information to a remote host running DFM 1.2 Upgraded for Common Services Version 2.2

•Exporting local DFM 1.2 information to a remote host running DFM 1.2 Updated for Common Services Version 2.2

Step 1 As the local administrator, log on to the local DFM system, and insert the upgrade CD-ROM into the CD-ROM drive. For example, do one of the following:

•On the DFM 1.1 system, insert the DFM 1.2 CD-ROM

•On the DFM 1.1 system, insert the DFM 1.2 Updated for Common Services Version 2.2 CD-ROM

•On the DFM 1.2 system, insert the DFM 1.2 Updated for Common Services Version 2.2 CD-ROM.

The installer window appears, asking you if you want to install DFM.

Step 2 Click Cancel.

Step 3 From a DOS command prompt, stop the CiscoWorks daemon manager:
Z:\> net stop crmdmgtd
Step 4 If desired, export your CD One information. Refer to Installation and Setup Guide for CD One on Windows, or Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows.

Step 5 Run the export script, which is on the DFM upgrade CD ROM drive under the disk1 directory, from the top-level directory:
Z:\> cd \
Z:\> perl export_dfm.pl
Step 6 Copy all files and directories in NMSROOT\rigel to an identical location on the remote machine.

Caution The DFM upgrade NMSROOT\rigel\scripts directory contains a file that may not be in the local NMSROOT\rigel\scripts directory. This file is called import_userinfo.pl. Therefore, do not do a simple directory copy or you will lose this file.

Caution Be sure to copy the files to the same directory path (NMSROOT\rigel). Copy all files, not just the files and directories under the dfm directory, because the import script needs files that are not stored under the dfm directory.

For example, you could do one of the following:

•Map the source drive to the destination drive, and copy the files.

•Copy the files to disk or tape and transfer the files to the remote machine.

Step 7 On the local DFM machine, restart the CiscoWorks daemon manager:
Z:\> net start crmdmgtd
Step 8 On the remote (upgraded) DFM machine, stop the CiscoWorks daemon manager:
C:\> net stop crmdmgtd
Step 9 If desired, import your CD One information. Refer to Installation and Setup Guide for CD One on Windows, or Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows.

Step 10 Run the import script, where NMSROOT is the default installation directory (normally C:\Program Files\CSCOpx):
C:\> cd NMSROOT\rigel\scripts
C:\> perl import_dfm.pl
The import script checks the space requirements, ensures that the daemon manager is stopped, and displays the following prompt:
Importing will cause all the files to be overwritten.
Are you sure you want to import (Y/N)?
Step 11 Enter Y and press Return.

Step 12 Restart the CiscoWorks daemon manager:
C:\> net start crmdmgtd
Step 13 Rediscover the devices in your DFM inventory by selecting Inventory > Inventory Collect All.

If any errors occurred during the upgrade, check the installation log in the root directory on the drive where the operating system is installed. Each installation creates a new log file. (For example, the CiscoWorks CD One installation might create C:\cw2000_in001.log, the DFM installation might create C:\cw2000_in002.log, and so forth.) The Technical Assistance Center (TAC) might ask you to send them the installation log. Also check import log, NMSROOT\rigel\manifest\dfm\import_dfm.log (where NMSROOT is the default installation directory, normally C:\Program Files\CSCOpx).

Reinstalling Device Fault Manager

The following sections describe how to reinstall DFM on the Windows operating system:

•Reinstalling DFM 1.2

•Reinstalling DFM 1.2 Updated for Common Services Version 2.2

Reinstalling DFM 1.2

Step 1 If HP OpenView is installed and operational, make sure it has been stopped (or the installation will take significantly longer).

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

Step 3 As the local administrator, log on to the machine on which you will install the DFM software, and insert the DFM CD-ROM into the CD-ROM drive. The installer window appears, asking you if you want to reinstall DFM.

Note If the CD-ROM is already in the CD-ROM drive and you stopped the reinstallation process to close programs or if Autostart is disabled, click Setup.exe from the top directory of your CD-ROM to restart the process.

Step 4 Click Install. The Welcome window appears.

Step 5 Click Next to continue. The Setup Type dialog box appears.

Step 6 Select Custom to select the components to reinstall. The Select Components dialog box appears. (For more information on reinstallation components, refer to Table 1-1.)

Step 7 Select the component you want to reinstall and click Next. The Start Copying Files window appears.

Step 8 Click Next.

Step 9 If you reinstalled only the HPOV-NetView Adapter or the RME Adapter, you are prompted to enter the name of the machine running the DFM Broker. Enter the name of the host (the default is localhost).

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

Step 10 Click Next.

Step 11 The Requirements Verification dialog box displays the results of the requirements check and advises whether the reinstallation can continue. One of the following should then occur:

•If minimum requirements are met, click OK. The Setup screen appears, displaying reinstallation progress while files are copied. The Setup Complete dialog box appears.

•If recommended requirements are not met, an error message appears. To continue the reinstallation, click OK.

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.
Step 12 If you see this message, after the installation completes, you must configure the SNMP Trap Adapter to use a different UDP port, such as port 9000. (Refer to the "Configuring the SNMP Trap Adapter" section.)

Step 13 A dialog box appears, asking if you want to connect this instance of DFM with VHM 1.0. Do one of the following:

•If you will be using a remote version of VHM 1.0 with DFM, click Yes.

The reinstallation program copies the files to the directory in which DFM was originally installed. The Restart window appears.

Proceed to Step 16.

•If you will not be using a remote version of VHM 1.0 with DFM, click No. Proceed to Step 14.

Note You must give the same answer to this question when you install adapters. If you answer No and provide a DFM username and password, you must provide the same username and password

Step 14 The Setup window appears. In the username field, enter the DFM username. In the password field, enter the DFM password.

Note You can change your username and password. Refer to the User Guide for Device Fault Manager, available from the online help, for more information.

Step 15 Click Next. The reinstallation program copies the files to the directory in which DFM was originally installed. The Restart window appears.

Step 16 Remove the DFM CD-ROM from the drive, and store the CD-ROM in a secure, climate-controlled area for safekeeping.

Step 17 Click Finish to reboot the machine.

Step 18 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:

–For DFM notification adapters:
# NMSROOT\bin\pdcmd.exe -u DfmFileNotifier
# NMSROOT\bin\pdcmd.exe -u DfmTrapNotifier
# NMSROOT\bin\pdcmd.exe -u DfmMailNotifier
–For DfmServer:
# NMSROOT\bin\pdcmd.exe -u DfmServer
–For DfmBroker:
# NMSROOT\bin\pdcmd.exe -u DfmBroker
b. Decide which hosts you want to specify using the --accept option with arguments shown in Table 2-3.

Note If you specify registration options using pdcmd, you must re-run your command whenever the daemon manager restarts.

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 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 may result in configurations that forward incoming connections (such as through software that provides an encrypted tunnel).

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):

–For DfmBroker (the following command is one line):
# NMSROOT\bin\pdcmd.exe -r DfmBroker -e NMSROOT\objects\smarts\bin\brstart.exe -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.exe -r DfmServer -e NMSROOT\objects\smarts\bin\sm_server.exe -d 
DfmBroker -f "--bootstrap=DFM_bootstrap.conf --accept=lucy,ethel --output --name=DFM"
–For DFM notification adapters (the following commands are each one line, and will register the adapter processes to automatically start upon reboot):
# NMSROOT\bin\pdcmd.exe -r DfmFileNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=filelog --output=sm_file_notifier"
# NMSROOT\bin\pdcmd.exe -r DfmTrapNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=trap --output=sm_trap_notifier"
# NMSROOT\bin\pdcmd.exe -r DfmMailNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=mail --output=sm_mail_notifier"
If you do not want the daemons to start after a reboot, add the -n option to the end of the command, as in this File Notifier Adapter example:
# NMSROOT\bin\pdcmd.exe -r DfmFileNotifier -d DfmServer -e 
NMSROOT\objects\smarts\bin\sm_notify.exe -f "--adapter=filelog --output=sm_file_notifier" 
-n
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 19 To verify that the DfmServer process is running, log on to the CiscoWorks desktop as the administrator and select Server Configuration >
Administration > Process Management > Process Status.

Note If your client does not have the Java plug-in, you will receive a message asking if you want to install it. The plug-in is required for DFM 1.2.

Step 20 To use DFM, select Device Fault Manager from the CiscoWorks navigation tree.

Step 21 Rediscover the devices in your DFM inventory by opening the Administration Console and selecting Inventory > Inventory Collect All.

Note Depending on the number of managed devices, rediscovering the entire DFM inventory could take several hours.

Step 22 If you used remote adapters with Device Fault Manager 1.1, perform these steps:

a. Make sure the machine running the DfmBroker is registered with DNS.

b. Upgrade all remote adapters as described in the "Installing and Upgrading Adapters" section.

When HP OpenView or NetView is restarted, CiscoWorks automatically configures the adapters to forward SNMP traps from HP OpenView or NetView to DFM. If you install HP OpenView or NetView later, you will have to either configure the SNMP Trap Adapter to use another port (as described in the "Configuring the SNMP Trap Adapter" section), or reinstall DFM.

If Essentials is presently (or subsequently) installed locally, CiscoWorks automatically configures the adapters to forward Essentials inventory device information to DFM. To do this with remote versions of HP OpenView, NetView, or Essentials, you must install the remote adapters as described in the "Installing and Upgrading Adapters" section.

If you had any errors during reinstallation, check the installation log in the root directory on the drive (For example, the CiscoWorks installation might create C:\cw2000_in001.log, the DFM installation might create C:\cw2000_in002.log, and so forth.) The Technical Assistance Center (TAC) might ask you to send them the installation log.

Reinstalling DFM 1.2 Updated for Common Services Version 2.2

Step 1 If HP OpenView is installed and operational, make sure it has been stopped (or the installation will take significantly longer).

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

Step 3 As the local administrator, log on to the machine on which you will install the DFM software, and insert the DFM CD-ROM into the CD-ROM drive. The installer window appears, asking you if you want to reinstall DFM.

Note If the CD-ROM is already in the CD-ROM drive and you stopped the reinstallation process to close programs or if Autostart is disabled, click Setup.exe from the top directory of your CD-ROM to restart the process.

Step 4 Click Install. The Welcome window appears.

Step 5 Click Next to continue. The Software License Agreement window appears.

Step 6 To accept the agreement and continue the reinstallation, click Yes.

Step 7 If your system contains installed IDUs that were released after DFM 1.2.3 (such as DFM 1.2 IDU 1.2.4), one of the following will happen:

•If you did enable DFM when you first installed it, a window opens displaying the following message:
A newer version of DFM is already running on your system.
Because the installation would provide no new functionality, the installation program exits, and your existing device support is preserved.

•If you did not enable DFM when you first installed it, the Enable DFM window opens, displaying the following message:
The installation program has detected a newer version of DFM 
already on your system. The newer version is disabled. Do you want 
to enable it?
Click "Yes" to enable the newer version of DFM.
Click "No" to abort the installation.
Do one of the following:

–To enable DFM, click Yes. Because continuing the installation would add no new functionality, further DFM installation is not required, and the installation program exits. To re-establish settings that were lost when CiscoWorks Common Services 2.2 was installed (and DFM was disabled), proceed to Step 15 in the "Performing a New Installation of DFM 1.2" section.

–To keep DFM disabled, select No. DFM remains disabled, and the installation program exits.

Step 8 The Setup Type dialog box appears. Select Custom to select the components to reinstall. The Select Components dialog box appears.

The system displays these options (the choices may vary, depending on your configuration):
CiscoWorks Device Fault Manager (reinstall) 
Device Fault Manager Incremental Device Support (reinstall)
(For more information on reinstallation components, refer to Table 1-1.)

Step 9 Select the component you want to reinstall and click Next. The installation program checks dependencies and system requirements.

Step 10 The System Requirements dialog box appears, displays the results of the requirements check, and advises whether the installation can continue. One of the following should then occur:

•If minimum requirements are met, click Next.

•If recommended requirements are not met, an error message appears. To continue the reinstallation, click Next.

Step 11 If you reinstalled only the HPOV-NetView Adapter or the RME Adapter, you are prompted to enter the name of the machine running the DFM Broker. Enter the name of the host (the default is localhost).

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

Step 12 Click Next.

Step 13 The Summary dialog box displays your selected settings. Click Next.

Step 14 The Setup window appears, displaying installation progress while files are copied.

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 the SNMP Trap Adapter to use a different UDP port, such as port 9000. (Refer to the "Configuring the SNMP Trap Adapter" section.)

Step 15 To finish reinstalling DFM 1.2 Updated for Common Services Version 2.2, follow Step 13 through Step 22 in the "Reinstalling DFM 1.2" section.

Removing Device Fault Manager

This section explains the steps for removing DFM 1.2 or DFM 1.2 Updated for Common Services Version 2.2 from Windows systems.

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 the local administrator, log on to the system on which DFM is installed, and select Start > Programs > CiscoWorks > Uninstall CiscoWorks to start the uninstallation process. The Uninstallation window appears, and the system displays these options (the choices may vary, depending on your configuration):
CiscoWorks Common Services 
CiscoView 
Device Fault Manager
Step 2 Deselect everything except Device Fault Manager and click Next. A dialog box listing the components selected for removal appears. (Removing DFM also removes DFM incremental device support. For more information on uninstallation components, refer to Table 1-1.)

Step 3 Click Next. Messages appear, showing the progress of the uninstallation, and the uninstallation completes.

Installing and Upgrading Adapters

Several software adapters link DFM with its environment. For the purposes of installation, this section classifies these adapters as local or remote, depending on whether or not they are installed on the same host as DFM. Detailed information on the adapters is provided in the User Guide for Device Fault Manager (available from online help).

Types of Adapters: Local and Remote

Local adapters are installed for forwarding traps or synchronizing information with NMSs running on the DFM host; remote adapters do the same, but on remote hosts not running DFM.

Local Adapters

When you install DFM locally, all adapters are installed. The local adapters include:

•File Notifier Adapter—Logs alarms detected by the DFM server and forwards them to a file. A file is the only valid recipient for this adapter. This adapter is normally used to create a historical file containing all alarms generated by DFM.

•Trap Notifier Adapter—Converts DFM alarms into SNMP trap messages and forwards the traps to recipients. You can specify recipients, such as NMSs or other domain managers, using an IP address or a system name. This adapter is normally used to send DFM alarms to another application for additional processing or display.

•Mail Notifier Adapter—Using SMTP, send mail notifications to recipients. As with the Trap Notifier Adapter, you can specify recipients—in this case, an email address. This adapter is normally used to generate asynchronous email notifications (for example, to an epage or an email address) when one or more alarm conditions occur.

•SNMP Trap Adapter—Listens on a user-specified port for traps sent to DFM from managed devices, and forwards traps to specified destinations. This adapter provides a generic method for integrating DFM with other NMS applications. The SNMP Trap Adapter is normally used to allow DFM to coexist with another trap-receiving application (such as an NMS) on the same server; have an NMS forward traps to DFM for processing; or have DFM listen for traps on devices and forward the traps to an NMS that does not support trap forwarding. Basic steps for configuring this adapter are provided in "Getting Started."

•HPOV-NetView Adapter—Forwards traps that managed devices send to a local HP OpenView or NetView NMS to DFM. This adapter is normally used when you want DFM to monitor faults on devices managed by a local version of HP OpenView or NetView. (For information on supported HP OpenView and NetView versions, refer to the "Supported NMS Integration" section.)

•RME Adapter—Synchronizes the list of managed devices in a local Essentials inventory with a DFM inventory. This adapter is normally used when you want DFM to monitor faults on devices managed by a local version of Essentials. (For information on supported Essentials versions, refer to the "Supported NMS Environments for Device Import" section.)

Remote Adapters

In addition to using the following adapters locally, you can install them remotely (on hosts not running DFM) to exchange remote device information with DFM:

•RME Adapter—Synchronizes the list of managed devices in a remote Essentials inventory with a local DFM inventory. This adapter is normally used when you want a local DFM to monitor faults on devices managed by a remote version of Essentials. (For information on supported Essentials versions, refer to the "Supported NMS Environments for Device Import" section.)

•HPOV-NetView Adapter—Forwards traps that managed devices send to a remote HP OpenView or NetView NMS to DFM. This adapter is normally used when you want a local DFM to monitor faults on devices managed by a remote version of HP OpenView or NetView. (For information on supported HP OpenView and NetView versions, refer to the "Supported NMS Integration" section.)

Note NetView must be installed on the same drive as DFM (for local integration) or on the same drive as the HPOV-NetView Adapter (for remote integration).

Configuring and Starting Adapters

Table 2-4 summarizes which adapters you must configure, whether you can use the GUI or command line to configure the adapter, and whether you must manually start the adapter. Additional information on configuring and starting adapters is provided in the User Guide for Device Fault Manager (available from online help).

Note Whenever you configure any adapter using the command line, you must manually stop and restart the adapter. Adapters configured with the DFM administration menus do not need to be stopped and restarted.

Table 2-4 Configuring and Starting Adapters

Adapter Type
and Name

Must Be Configured Before Use

Can Be Configured Using...

Automatically Starts with CiscoWorks

GUI

CLI

Notification Adapters

File Notifier

Trap Notifier

Mail Notifier

Yes

Yes

Yes

No

Yes

Yes

Yes

No

Yes

Yes

Yes

No

Event Adapters

HPOV-NetView

No

No

Yes

Yes, if HP OpenView or NetView is installed on the same machine as the adapter

Special Adapters

SNMP Trap

RME Adapter

Yes

Yes

Yes

Yes

No

N/A, but can be started using the GUI

N/A

Yes, if Essentials is installed on the same machine as the adapter

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

This section describes how to install or upgrade the HPOV-NetView Adapter on a remote host so the adapter can exchange information with DFM on a local host. You can install or upgrade the HPOV-NetView Adapter on remote hosts regardless of whether CiscoWorks is present. You can also use this procedure to reinstall the HPOV-NetView Adapter on a machine running CiscoWorks; reinstallation of the HPOV-NetView Adapter is supported only on machines running CiscoWorks.

If you upgrade a local version of DFM 1.1, you must also upgrade all remote adapters. You do not need to upgrade DFM 1.2 adapters if you are upgrading to DFM 1.2 Updated for Common Services Version 2.2.

Note NetView must be installed on the same drive as DFM (for local integration) or on the same drive as the HPOV-NetView Adapter (for remote integration).

Note To upgrade a remote HPOV-NetView Adapter, you must first remove the old adapter and then install the new version.

Note If the DFM broker is moved—for example, if DFM is moved to a different machine, or you want to use a different instance of DFM—you must reinstall the remote adapters.

Installing or Upgrading the HPOV-NetView Adapter on a Remote Host Running CiscoWorks

Use this procedure to do the following:

•Install a new HPOV-NetView Adapter on a remote host running CiscoWorks, or

•Upgrade a DFM 1.1 version of the HPOV-NetView Adapter on a remote host running CiscoWorks

You do not need to upgrade DFM 1.2 adapters if you are upgrading to DFM 1.2 Updated for Common Services Version 2.2.

Step 1 If you want to upgrade a DFM 1.1 version of the HPOV-NetView Adapter, remove the adapter as described in the "Removing the HPOV-NetView Adapter from a Remote Host Running CiscoWorks" section.

Step 2 As the local administrator, log on to the machine on which you will install the HPOV-NetView Adapter, and insert the DFM CD-ROM into the CD-ROM drive. The installer window appears, asking you if you want to install DFM. (Alternatively, you can install the adapter using DFM 1.2 Patch/IDU 1.2.7 or later, and proceed to Step 3.)

Note If the CD-ROM is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click Setup.exe to restart the process.

Note To use the HPOV-NetView Adapter with NetView, be sure to install the adapter on the same drive as NetView.

Step 3 Click Install. The Welcome window appears.

Step 4 Click Next.

Step 5 If you are upgrading your DFM 1.1 adapter to DFM 1.2 Updated for Common Services Version 2.2, the Software License Agreement window appears. To accept the agreement and continue the installation, click Yes.

Step 6 The Setup Type dialog box appears. Select Custom to select a component to install and click Next. The Select Components dialog box appears.

Step 7 Select Device Fault Manager HPOV-NetView adapters and click Next. HP OpenView and NetView are stopped. The installation program checks dependencies and system requirements.

Step 8 Click Next. HP OpenView and NetView are stopped. The Requirements Verification dialog box displays the results of the requirements check and advises whether installation can continue.

Step 9 When prompted, enter the machine name or IP address of the machine on which the DfmBroker is running (this is normally the machine that is running DFM).

Note Do not use the default, localhost. Also, make sure the machine running the DfmBroker is registered with DNS.

Step 10 A dialog box appears, asking if you want to connect this instance of DFM with VHM 1.0.

Note You must give the same answer to this question that you gave when installing DFM. If you answered No to this question when installing DFM, you must provide the same username and password pair that you provided for DFM.

Do one of the following:

•If you will be using a remote version of VHM 1.0 with DFM, click Yes.

HP OpenView and NetView are stopped. The Requirements Verification dialog box displays the results of the requirements check and advises whether installation can continue

Proceed to Step 12.

•If you will not be using a remote version of VHM 1.0 with DFM, click No. Proceed to Step 11.

Step 11 The Setup window appears. In the username field, enter the DFM username. In the password field, enter the DFM password.

Note You can change your username and password. Refer to the User Guide for Device Fault Manager, available from the online help, for more information.

Step 12 Click OK. The installation program copies the files to the directory in which CD One was installed.

Step 13 Remove the DFM CD-ROM from the drive.

Installing or Upgrading the HPOV-NetView Adapter on a Remote Host Not Running CiscoWorks

Use this procedure to do the following:

•Install a new HPOV-NetView Adapter on a remote host that is not running CiscoWorks, or

•Upgrade a DFM 1.1 version of the HPOV-NetView Adapter on a remote host that is not running CiscoWorks

If you try to run the DFMadapter.exe script on a host that is running CiscoWorks or DFM, you will receive an error message and the installation will abort.

You do not need to upgrade DFM 1.2 adapters if you are upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2.

Note The DFMadapter.exe script does not support reinstallation.

Step 1 Verify that you have 31 MB of space for installing the adapter.

Step 2 If you want to upgrade a 1.1 version of the HPOV-NetView Adapter, remove the adapter as described in the "Removing the HPOV-NetView Adapter from a Remote Host Not Running CiscoWorks" section.

Step 3 From a temporary directory, use ftp to copy the binary file NMSROOT\htdocs\rdist\dfm\DFMadapter.exe from the running DFM. In the following commands, dfm-host is where DFM is installed, and NMSROOT is the DFM installation directory (normally C:\Program Files\CSCOpx):
# cd \Temp 
# ftp dfm-host 
User (dfm-host:(none)): login
Password: password
ftp> cd NMSROOT\htdocs\rdist\dfm 
ftp> get DFMadapter.exe
ftp> quit
Step 4 Double-click DFMadapter.exe. The Choose Destination Location window appears.

Step 5 In the Select Destination Folder field, select C:\DFM and click Next. The Setup Window appears.

Step 6 Enter the machine name or IP address of the machine on which the DfmBroker is running (normally the machine that is running DFM).

Note Do not use the default, localhost. Also make sure the machine running the DfmBroker is registered with DNS.

Step 7 A dialog box appears, asking if you want to connect this instance of DFM with VHM 1.0.

Note You must give the same answer to this question that you gave when installing DFM. If you answered No to this question when installing DFM, you must provide the same username and password pair that you provided for DFM.

Do one of the following:

•If you will be using a remote version of VHM 1.0 with DFM, click Yes.

The adapter is installed (or upgraded), and HP OpenView and NetView are stopped.

Proceed to Step 10.

•If you will not be using a remote version of VHM 1.0 with DFM, click No. Proceed to Step 8.

Step 8 The Setup window appears. In the username field, enter the DFM username. In the password field, enter the DFM password.

Note You can change your username and password. Refer to the User Guide for Device Fault Manager, available from the online help, for more information.

Step 9 Click Next. The adapter is installed (or upgraded), and HP OpenView and NetView are stopped.

Step 10 Click Finish. The Restarting Windows dialog box appears.

Step 11 Select Yes to confirm that you want to reboot, and click OK.

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

CiscoWorks automatically configures the remote adapters to foward SNMP traps from HP OpenView and NetView to DFM.

Installing or Upgrading the RME Adapter on a Remote Host

This section describes how to install or upgrade the RME Adapter on a remote host so the adapter can exchange information with DFM on a local host. You can also use this procedure to reinstall the RME Adapter.

Installing or Upgrading the RME Adapter on a Remote DFM Host

Use this procedure to do the following:

•Install a new RME Adapter on a remote host running CiscoWorks, or

•Upgrade a DFM 1.1 version of the RME Adapter on a remote host running CiscoWorks

You do not need to upgrade DFM 1.2 adapters if you are upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2.

Note If the DFM broker is moved—for example, if DFM is moved to a different machine, or you want to use a different instance of DFM—you must reinstall the remote adapters.

Step 1 As the local administrator, log on to the machine on which you will install the HPOV-NetView Adapter, and insert the DFM CD-ROM into the CD-ROM drive. (Alternatively, you can install the adapter using DFM 1.2 Patch/IDU 1.2.7 or later.) The installer window appears, asking you if you want to install DFM.

Note If the CD-ROM is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click Setup.exe to restart the process.

Step 2 Click Install. The Welcome window appears.

Step 3 Click Next.

Step 4 If you are upgrading your DFM 1.1 adapter to DFM 1.2 Updated for Common Services Version 2.2, the Software License Agreement window appears. To accept the agreement and continue the installation, click Yes.

Step 5 The Setup Type dialog box appears. Select Custom to select a component to install and click Next. The Select Components dialog box appears.

Step 6 Select Device Fault Manager RME Adapter and click Next. The Start Copying Files dialog box appears.

Step 7 Click Next. The Requirements Verification dialog box displays the results of the requirements check and advises whether installation can continue.

Step 8 Click OK. The installation program copies the files to the CiscoWorks default installation directory C:\Program Files\CSCOpx (NMSROOT). The Enter Information window appears, asking you for the name of the machine running the DFM Broker.

Step 9 Enter the machine name or IP address of the machine on which the DfmBroker is running (this is normally the machine that is running DFM).

Note Do not use the default, localhost. Also make sure the machine running the DfmBroker is registered with DNS.

Step 10 A dialog box appears, asking if you want to connect this instance of DFM with VHM 1.0.

Note You must give the same answer to this question that you gave when installing DFM. If you answered No to this question when installing DFM, you must provide the same username and password pair that you provided for DFM.

Do one of the following:

•If you will be using a remote version of VHM 1.0 with DFM, click Yes.

The Restart Windows dialog box appears.

Proceed to Step 13.

•If you will not be using a remote version of VHM 1.0 with DFM, click No. Proceed to Step 11.

Step 11 The Setup window appears. In the username field, enter the DFM username. In the password field, enter the DFM password.

Note You can change your username and password. Refer to the User Guide for Device Fault Manager, available from the online help, for more information.

Step 12 Click Next. The Restart Windows dialog box appears.

Step 13 Select Yes and click OK to reboot the machine.

Step 14 Remove the DFM CD-ROM from the drive.

After Essentials is installed, CiscoWorks automatically configures the remote adapters to forward Essentials inventory device information to DFM.

If you had any errors during installation (or upgrade), check the installation log in the root directory on the drive. (For example, the CiscoWorks installation might create C:\cw2000_in001.log, the DFM installation might create C:\cw2000_in002.log, and so forth.) The Technical Assistance Center (TAC) might ask you to send them the installation log.

Removing Adapters

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

Removing the HPOV-NetView Adapter from a Remote Host

You can remove the HPOV-NetView Adapter from remote host machines with or without installed CiscoWorks products.

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

Removing the HPOV-NetView Adapter from a Remote Host Running CiscoWorks

Use this procedure to remove the HPOV-NetView Adapter from a remote host that is running CiscoWorks.

Step 1 As the local administrator, log on to the system on which the remote HPOV-NetView Adapter is installed, and select Start > Programs > CiscoWorks > Uninstall CiscoWorks to start the uninstallation process. The Uninstall window appears, displaying a list of the installed applications.

Step 2 Deselect everything except Device Fault Manager HPOV-NetView Adapters.

Step 3 Click Next. A dialog box listing the components selected for removal appears.

Step 4 Click Next to begin removing the HPOV-NetView Adapter. Messages appear, showing the progress of the uninstallation, and the uninstallation completes.

Step 5 Click OK.

If you had any errors during uninstallation, check the installation log in the root directory on the drive. (For example, the CiscoWorks installation might create C:\cw2000_in001.log, the DFM installation might create C:\cw2000_in002.log, and so forth.) The Technical Assistance Center (TAC) might ask you to send them the installation log.

Removing the HPOV-NetView Adapter from a Remote Host Not Running CiscoWorks

Use this procedure to remove the HPOV-NetView Adapter from a remote host that does not contain CiscoWorks. If you try to run the DFMadapter.exe on a host that is running CiscoWorks or DFM, you will receive an error message and the uninstallation will abort.

Step 1 From a temporary directory, use ftp to copy the NMSROOT\htdocs\rdist\dfm\DFMadapter.exe binary file from the running DFM. In the following commands, dfm-host is where DFM is installed, and NMSROOT is the DFM installation directory (normally
C:\Program Files\CSCOpx):
# cd \Temp 
# ftp dfm-host 
User (dfm-host:(none)):login
Password: password
ftp> cd NMSROOT\htdocs\rdist\dfm 
ftp> get DFMadapter.exe
ftp> quit
Step 2 Double-click DFMadapter.exe. The Confirm File Deletion window appears.

Step 3 Click OK. The adapter is removed, and HP OpenView and NetView are stopped and restarted. The Setup window appears.

Step 4 Click Finish.

Removing the RME Adapter from a Remote Host

This section describes how to remove the RME Adapter from a remote host.

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

Step 1 As the local administrator, log on to the system on which the RME Adapter is installed, and select Start > Programs > CiscoWorks > Uninstall CiscoWorks to start the uninstallation process. The Uninstall window appears, displaying a list of the installed applications.

Step 2 Deselect everything except Device Fault Manager RME adapter.

Step 3 Click Next. The Uninstallation window lists the components selected for removal.

Step 4 Click Next to begin removing the RME Adapter. Messages appear, showing the progress of the uninstallation, and the uninstallation completes.

If you had any errors during installation, check the installation log in the root directory on the drive. (For example, the CiscoWorks installation might create C:\cw2000_in001.log, the DFM installation might create C:\cw2000_in002.log, and so forth.) The Technical Assistance Center (TAC) might ask you to send them the installation log.