Table Of Contents
Installing Device Fault Manager
Performing a New Installation
Upgrading from Device Fault Manager 1.0
Performing the Upgrade
Exporting DFM 1.0 Information to an Upgraded Remote Host
Reinstalling Device Fault Manager
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 CiscoWorks2000
Installing or Upgrading the HPOV-NetView Adapter on a Remote Host Not Running CiscoWorks2000
Installing or Upgrading the RME Adapter on a Remote Host
Removing Adapters
Removing the HPOV-NetView Adapter from a Remote Host
Removing the HPOV-NetView Adapter from a Remote Host Running CiscoWorks2000
Removing the HPOV-NetView Adapter from a Remote Host Not Running CiscoWorks2000
Removing the RME Adapter from a Remote Host
Installing Device Fault Manager
This chapter describes installing Device Fault Manager (DFM) on a Windows 2000 or Windows NT system. It includes:
•
Performing a New Installation
•Upgrading from Device Fault Manager 1.0
•Reinstalling Device Fault Manager
•Removing Device Fault Manager
•Installing and Upgrading Adapters
•Removing Adapters
Performing a New Installation
Follow these steps to perform a new installation on a Windows 2000 or Windows NT 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, 4th Edition. Applications not supported by CD One, 4th Edition, will be disabled when you upgrade CD One.
•CD One, 4th Edition, has been installed. (Refer to Installing and Setting Up CD One on Windows 2000 and Windows NT.)
•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).
–If HP OpenView is installed on a Windows NT NTFS partition, create an account with full NTFS privileges. Refer to Appendix A, "Configuring HP OpenView for Full NTFS Privileges."
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 on page 1-2.)
Note If the HPOV-NetView Adapter or RME Adapter installation options are displayed and you choose one of them, but HP OpenView, NetView or Essentials are not installed, the adapters will still be installed.
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 on page 3-3.)
The installation program copies the files to the CiscoWorks2000 default installation directory C:\Program Files\CSCOpx (NMSROOT). The Restart window appears.
Step 10 Remove the DFM CD-ROM from the drive.
Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.
Step 11 Click Finish to reboot the machine.
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.)
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.
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:
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 13 If HP OpenView is installed on a Windows NT NTFS partition, create an account with full NTFS privileges. Refer to Appendix A, "Configuring HP OpenView for Full NTFS Privileges."
Step 14 To verify that the DfmServer process is running, log on to the CiscoWorks2000 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.1.
Step 15 If you plan to use remote adapters with Device Fault Manager 1.1, 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 16 To use DFM, select Device Fault Manager from the CiscoWorks2000 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 on page 3-3.
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 on page 3-2.
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, CiscoWorks2000 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 on page 3-3), or reinstall DFM.
If a local version of Essentials is already installed (or installed later), CiscoWorks2000 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 CiscoWorks2000 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 from Device Fault Manager 1.0
You can upgrade Device Fault Manager 1.0 on local or remote machines. If desired, you can upgrade a remote machine and then export your local DFM 1.0 information to the upgraded remote machine. These procedures are described in these sections:
•Performing the Upgrade
•Exporting DFM 1.0 Information to an Upgraded Remote Host
Performing the Upgrade
When you upgrade a local version of DFM 1.0 to DFM 1.1, the upgrade program saves and restores the DFM 1.0 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.1.
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, 4th Edition. Applications not supported by CD One, 4th Edition, will be disabled when you upgrade CD One.
•CD One, 4th Edition has been installed. (Refer to Installing and Setting Up CD One on Windows 2000 and Windows NT.)
•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 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 on page 1-2.)
Note If the HPOV-NetView Adapter or RME Adapter installation options are displayed and you choose one of them, but HP OpenView, NetView or Essentials are not installed, the adapters will still be installed.
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 on page 3-3.)
The installation program copies the files to the CiscoWorks2000 default installation directory C:\Program Files\CSCOpx (NMSROOT).
Step 10 A dialog box appears, reminding you to run rediscovery from the Administration Console; this procedure is described in Step 17. Click OK. The Restart window appears.
Step 11 Remove the DFM CD-ROM from the drive.
Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.
Step 12 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 13 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.
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:
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 14 If HP OpenView is installed on a Windows NT NTFS partition, create an account with full NTFS privileges. Refer to Appendix A, "Configuring HP OpenView for Full NTFS Privileges."
Step 15 To verify that the DfmServer process is running, log on to the CiscoWorks2000 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.1.
Step 16 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 17 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 18 If you used remote adapters with Device Fault Manager 1.0, 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.
c. If a remote version of HP OpenView is installed on a Windows NT NTFS partition, create an account with full NTFS privileges (after upgrading the remote adapters). Refer to Appendix A, "Configuring HP OpenView for Full NTFS Privileges."
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 on page 3-3.
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 on page 3-2.
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, CiscoWorks2000 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 on page 3-3), or reinstall DFM.
If a local version of Essentials is already installed (or installed later), CiscoWorks2000 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 CiscoWorks2000 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.
Exporting DFM 1.0 Information to an Upgraded Remote Host
This procedure exports your local DFM 1.0 configuration information and imports it to a remote machine that has been upgraded to DFM 1.1.
Step 1 As the local administrator, log on to the local DFM 1.0 system, and insert the DFM 1.1 CD-ROM into the CD-ROM drive. 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 CiscoWorks2000 daemon manager:
Step 4 If desired, export your CD One information. Refer to Installing and Setting Up CD One on Windows 2000 and Windows NT.
Step 5 Run the export script from the top-level directory:
Step 6 Copy all files and directories in NMSROOT\rigel to an identical location on the remote machine.
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 1.0 machine, restart the CiscoWorks2000 daemon manager on the local DFM 1.0 machine:
Step 8 On the remote DFM 1.1 machine, stop the CiscoWorks2000 daemon manager:
Step 9 If desired, import your CD One information. Refer to Installing and Setting Up CD One on Windows 2000 and Windows NT.
Step 10 Run the import script, where NMSROOT is the default installation directory (normally C:\Program Files\CSCOpx):
C:\> cd NMSROOT\rigel\scripts
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 CiscoWorks2000 daemon manager:
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 CiscoWorks2000 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
Follow these steps to reinstall DFM on the Windows 2000 or Windows NT operating system.
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.
The system displays these options (the choices may vary, depending on your configuration):
CiscoWorks2000 Device Fault Manager (reinstall)
Device Fault Manager Incremental Device Support (reinstall)
(For more information on reinstallation components, refer to Table 1-1 on page 1-2.)
Note If the HPOV-NetView Adapter or RME Adapter installation options are displayed and you choose one of them, but HP OpenView, NetView or Essentials are not installed, the adapters will still be installed.
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.
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 on page 3-3.)
The reinstallation program copies the files to wherever DFM was originally installed.
Step 12 Remove the DFM CD-ROM from the drive.
Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.
Step 13 Click Finish to reboot the machine.
Step 14 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:
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:
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 15 If HP OpenView is installed on a Windows NT NTFS partition, create an account with full NTFS privileges. Refer to Appendix A, "Configuring HP OpenView for Full NTFS Privileges."
Step 16 To verify that the DfmServer process is running, log on to the CiscoWorks2000 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.1.
Step 17 To use DFM, select Device Fault Manager from the CiscoWorks2000 navigation tree.
Step 18 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 make take several hours.
Step 19 If you used remote adapters with Device Fault Manager 1.0, 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.
c. If HP OpenView is installed on a Windows NT NTFS partition, create an account with full NTFS privileges. Refer to Appendix A, "Configuring HP OpenView for Full NTFS Privileges."
When HP OpenView or NetView are restarted, CiscoWorks2000 automatically configures the adapters to forward 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 on page 3-3), or reinstall DFM.
If Essentials is presently (or subsequently) installed locally, CiscoWorks2000 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 CiscoWorks2000 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.
Removing Device Fault Manager
This section explains the steps for removing DFM from Windows 2000 and Windows NT systems.
Caution You must use the CiscoWorks2000 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 > CiscoWorks2000 > Uninstall CiscoWorks2000 to start the uninstall process. The Uninstallation window appears, and the system displays these options (the choices may vary, depending on your configuration):
CD One Fourth Edition
CMF Web Desktop
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 on page 1-2.)
Step 3 Click Next. Messages showing the progress of the uninstallation appear, 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 Device Fault Manager User Guide (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 Chapter 3, "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 on page 1-10.)
•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 on page 1-10.)
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 on page 1-10.)
•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 on page 1-10.)
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 Device Fault Manager User Guide (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 CiscoWorks2000
|
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 CiscoWorks2000 is present. You can also use this procedure to reinstall the HPOV-NetView Adapter on a machine running CiscoWorks2000; reinstallation of the HPOV-NetView Adapter is supported only on machines running CiscoWorks2000.
If you upgrade a local version of DFM, you must also upgrade all remote adapters.
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 CiscoWorks2000
Follow these steps to install or upgrade a remote HPOV-NetView Adapter on a host that is running CiscoWorks2000.
Step 1 If you want to upgrade a 1.0 version of the HPOV-NetView Adapter, remove the adapter as described in the "Removing the HPOV-NetView Adapter from a Remote Host Running CiscoWorks2000" 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.
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 3 Click Install. The Welcome window appears.
Step 4 Click Next. The Setup Type dialog box appears.
Step 5 Select Custom to select a component to install and click Next. The Select Components dialog box appears.
Step 6 Select Device Fault Manager HPOV-NetView adapters and click Next. The Start Copying Files dialog box appears.
Step 7 Click Next.
Step 8 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 9 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 10 Click OK. The installation program copies the files to the directory in which CD One was installed.
Step 11 Remove the DFM CD-ROM from the drive.
Step 12 Click OK to reboot the machine.
Step 13 If HP OpenView is installed on a Windows NT NTFS partition, create an account with full NTFS privileges. Refer to Appendix A, "Configuring HP OpenView for Full NTFS Privileges."
Step 14 Restart HP OpenView or NetView to activate the adapter (using the ovstart or nvstart command).
CiscoWorks2000 automatically configures the remote adapters to foward SNMP traps from HP OpenView and NetView 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 CiscoWorks2000 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.
Installing or Upgrading the HPOV-NetView Adapter on a Remote Host Not Running CiscoWorks2000
Use this procedure to install or upgrade a remote HPOV-NetView Adapter on a host that does not contain CiscoWorks2000. If you try to run the DFMadapter.exe script on a host that is running CiscoWorks2000 or DFM, you will receive an error message and the installation will abort.
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.0 version of the HPOV-NetView Adapter, remove the adapter as described in the "Removing the HPOV-NetView Adapter from a Remote Host Not Running CiscoWorks2000" 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 1.1 is installed, and NMSROOT is the DFM installation directory (normally C:\Program Files\CSCOpx):
# cd \Temp
# ftp dfm-host
User (dfm-host:(none)): login
ftp> cd NMSROOT\htdocs\rdist\dfm
ftp> get DFMadapter.exe
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 Click Next. The adapter is installed (or upgraded), and HP OpenView and NetView are stopped.
Step 8 Click Finish. The Restarting Windows dialog box appears.
Step 9 Select Yes to confirm that you want to reboot, and click OK.
Step 10 If HP OpenView is installed on a Windows NT NTFS partition, create an account with full NTFS privileges. Refer to Appendix A, "Configuring HP OpenView for Full NTFS Privileges."
Step 11 Restart HP OpenView or NetView to activate the adapter (using the ovstart or nvstart command).
CiscoWorks2000 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.
If you upgrade a local version of DFM, you must also upgrade all remote adapters.
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. 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. The Setup Type dialog box appears.
Step 4 Select Custom to select a component to install and click Next. The Select Components dialog box appears.
Step 5 Select Device Fault Manager RME Adapter and click Next. The Start Copying Files dialog box appears.
Step 6 Click Next. The Requirements Verification dialog box displays the results of the requirements check and advises whether installation can continue.
Step 7 Click OK. The installation program copies the files to the CiscoWorks2000 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 8 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 9 Click Next. The Restart Windows dialog box appears.
Step 10 Select Yes and click OK to reboot the machine.
Step 11 Remove the DFM CD-ROM from the drive.
Step 12 If you plan to use the RME Adapter to synchronize Essentials 3.1 or 3.2 information with a DFM 1.0 host in your network, refer to the Release Notes for Device Fault Manager 1.0 on Windows 2000 and Windows NT for information on a required procedure.
After Essentials is installed, CiscoWorks2000 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 CiscoWorks2000 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.
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 CiscoWorks2000 products.
Caution You must use the CiscoWorks2000 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 CiscoWorks2000
Use this procedure to remove the HPOV-NetView Adapter from a remote host that is running CiscoWorks2000.
Step 1 As the local administrator, log on to the system on which the remote HPOV-NetView Adapter is installed, and select Start > Programs > CiscoWorks2000 > Uninstall CiscoWorks2000 to start the uninstall 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 showing the progress of the uninstallation appear, 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 CiscoWorks2000 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.
Removing the HPOV-NetView Adapter from a Remote Host Not Running CiscoWorks2000
Use this procedure to remove the HPOV-NetView Adapter from a remote host that does not contain CiscoWorks2000. If you try to run the DFMadapter.exe on a host that is running CiscoWorks2000 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 1.1 is installed, and NMSROOT is the DFM installation directory (normally
C:\Program Files\CSCOpx):
# cd \Temp
# ftp dfm-host
User (dfm-host:(none)):login
ftp> cd NMSROOT\htdocs\rdist\dfm
ftp> get DFMadapter.exe
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 CiscoWorks2000 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 > CiscoWorks2000 > Uninstall CiscoWorks2000 to start the uninstall 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 showing the progress of the uninstallation appear, 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 CiscoWorks2000 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.
