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 Solaris 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 Solaris 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 Solaris.)
•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).
Step 2 Close all open or active programs. Do not run other programs during the installation process.
Step 3 As root, log on to the system on which you will install DFM, and mount a local or remote CD-ROM drive. For instructions on mounting the CD-ROM, refer to Appendix A, "Mounting and Unmounting on Solaris."
Step 4 Start the installation program by entering one of the following:
•For a local installation, enter:
•For a remote installation, enter:
where remotedir is the remote location where the CD-ROM is mounted.
The installation program stops CiscoWorks2000, performs a requirements check, and displays the following prompt:
WARNING: User casuser already exists, the installation process will
overwrite its privilege.
Do you want to continue ? (y/n)? [y]
Step 5 Press Return to confirm installing the packages with the correct privileges. The installation program displays the following installation choices (the choices may vary, depending on your configuration):
1) CiscoWorks2000 Device Fault Manager
2) Device Fault Manager HPOV-NetView adapters
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 6 Select 1 and press Return. This installs 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.)
The installation program checks dependencies and system requirements.
•If there is not enough disk space for the installation, the installation program displays an error message and stops.
Note Do not be alarmed if you see the following message:
INFO: total size (MB) required = 87
This message applies to disk space required by the current set of individual packages being installed.
•If the minimum recommended requirements are not met, the installation program displays an error message and continues installing.
If DFM detects another application using port 162, DFM displays the following message:
WARNING: Installation has detected port 162 in use. DFM is set to use
port 9000 for receiving SNMP traps.
If you see this message, after the installation completes, you must configure the SNMP Trap Adapter to use a different UDP port, such as port 9000. (Refer to the "Configuring the SNMP Trap Adapter" section.)
The installation proceeds without displaying any more questions, and the system prompt appears. The installation program copies the files to the CiscoWorks2000 default installation directory /opt/CSCOpx (NMSROOT).
Step 7 Unmount and eject the CD-ROM.
Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.
Step 8 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 -u DfmFileNotifier
# NMSROOT/bin/pdcmd -u DfmTrapNotifier
# NMSROOT/bin/pdcmd -u DfmMailNotifier
–For DfmServer:
# NMSROOT/bin/pdcmd -u DfmServer
–For DfmBroker:
# NMSROOT/bin/pdcmd -u DfmBroker
b. Decide which hosts you want to specify using the --accept option with arguments shown in Table 2-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 -r DfmBroker -e NMSROOT/objects/smarts/bin/brstart -f "--output
--port=9002 --accept=lucy,ethel --restore=NMSROOT/objects/smarts/conf/broker.rps"
–For the DFM server (the following command is one line):
# NMSROOT/bin/pdcmd -r DfmServer -e NMSROOT/objects/smarts/bin/sm_server -d DfmBroker -f
"--bootstrap=DFM_bootstrap.conf --accept=lucy,ethel --output --name=DFM"
–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 -r DfmFileNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -f "--adapter=filelog --output=sm_file_notifier"
# NMSROOT/bin/pdcmd -r DfmTrapNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -f "--adapter=trap --output=sm_trap_notifier"
# NMSROOT/bin/pdcmd -r DfmMailNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -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 -r DfmFileNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -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 9 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 10 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 11 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.
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.
After you install or restart a local version of HP OpenView and NetView, 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), 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, check the installation log, /var/tmp/ciscoinstall.log. 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 the following 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 Solaris.)
•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).
Step 2 Close all open or active programs. Do not run other programs during the reinstallation process.
Step 3 As root, log on to the system on which you will upgrade DFM, and mount a local or remote CD-ROM drive. For instructions on mounting the CD-ROM, refer to Appendix A, "Mounting and Unmounting on Solaris."
Step 4 Start the installation program by entering one of the following:
•For a local upgrade, enter:
•For a remote upgrade, enter:
where remotedir is the remote location where the CD-ROM is mounted.
The installation program stops CiscoWorks2000, performs a requirements check, and displays the following prompt:
WARNING: User casuser already exists, the installation process will
overwrite its privilege.
Do you want to continue ? (y/n)? [y]
Step 5 Press Return to confirm installing the packages with the correct privileges.
The installation program displays the following installation choices (the choices may vary, depending on your configuration):
1) CiscoWorks2000 Device Fault Manager
2) Device Fault Manager HPOV-NetView adapters
2) RME Adapter
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 6 Select 1 and press Return. This installs 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.)
The installation program checks dependencies and system requirements:
•If there is not enough disk space for the installation, the installation program displays an error message and stops.
Note Do not be alarmed if you see the following message:
INFO: total size (MB) required = 87
This message applies to disk space required by the current set of individual packages being installed.
•If the minimum recommended requirements are not met, the installation program displays an error message and continues installing.
If DFM detects another application using port 162, DFM displays the following message:
WARNING: Installation has detected port 162 in use. DFM is set to use
port 9000 for receiving SNMP traps.
If you see this message, after the installation completes, you must configure the SNMP Trap Adapter to use a different UDP port, such as port 9000. (Refer to the "Configuring the SNMP Trap Adapter" section.)
As the installation completes, you will see the following reminder:
WARNING: After the installation is complete, you need to run
rediscovery from the Administration Console for DFM to correctly
classify the devices.
(The procedure for rediscovering devices is described in Step 11.)
The installation program copies the files to the CiscoWorks2000 default installation directory /opt/CSCOpx (NMSROOT), and the system prompt appears.
Step 7 Unmount and eject the CD-ROM.
Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.
Step 8 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 -u DfmFileNotifier
# NMSROOT/bin/pdcmd -u DfmTrapNotifier
# NMSROOT/bin/pdcmd -u DfmMailNotifier
–For DfmServer:
# NMSROOT/bin/pdcmd -u DfmServer
–For DfmBroker:
# NMSROOT/bin/pdcmd -u DfmBroker
b. Decide which hosts you want to specify using the --accept option with arguments shown in Table 2-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 -r DfmBroker -e NMSROOT/objects/smarts/bin/brstart -f "--output
--port=9002 --accept=lucy,ethel --restore=NMSROOT/objects/smarts/conf/broker.rps"
–For the DFM server (the following command is one line):
# NMSROOT/bin/pdcmd -r DfmServer -e NMSROOT/objects/smarts/bin/sm_server -d DfmBroker -f
"--bootstrap=DFM_bootstrap.conf --accept=lucy,ethel --output --name=DFM"
–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 -r DfmFileNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -f "--adapter=filelog --output=sm_file_notifier"
# NMSROOT/bin/pdcmd -r DfmTrapNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -f "--adapter=trap --output=sm_trap_notifier"
# NMSROOT/bin/pdcmd -r DfmMailNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -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 -r DfmFileNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -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 9 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 10 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 11 Rediscover the devices in your DFM inventory by selecting Inventory > Inventory Collect All.
Note Depending on the number of managed devices, rediscovering the entire DFM inventory could take several hours.
Step 12 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.
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.
After you install or restart a local version of HP OpenView and NetView, 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), 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, check the installation log, /var/tmp/ciscoinstall.log. 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 root, log on to the local DFM 1.0 system, and mount a local CD-ROM drive. For instructions on mounting the CD-ROM, refer to Appendix A, "Mounting and Unmounting on Solaris."
Step 2 Stop the CiscoWorks2000 daemon manager:
Step 3 If desired, export your CD One information. Refer to Installing and Setting Up CD One on Solaris.
Step 4 Run the export script from the top-level directory:
Step 5 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:
•Copy the files using tar:
# tar cvf dfmupgrade.tar rigel
Use ftp to copy the files to the remote machine.
•Copy the files to disk or tape and transfer the files to the remote machine.
Step 6 On the local DFM 1.0 machine, restart the CiscoWorks2000 daemon manager:
# /etc/init.d/dmgtd start
Step 7 On the remote DFM 1.1 machine, stop the CiscoWorks2000 daemon manager:
Step 8 If desired, import your CD One information. Refer to Installing and Setting Up CD One on Solaris.
Step 9 Run the import script, where NMSROOT is the default installation directory (normally /opt/CSCOpx):
# 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 10 Enter Y and press Return. When the import has completed, you will see the following message:
Finished upgrading DFM files...
Step 11 Restart the CiscoWorks2000 daemon manager:
# /etc/init.d/dmgtd start
If you had any errors, check the installation log, /var/tmp/ciscoinstall.log. The Technical Assistance Center might ask you to send them the installation log. Also check the import log, NMSROOT/rigel/manifest/dfm/import_dfm.log (where NMSROOT is the default installation directory, normally /opt/CSCOpx).
Reinstalling Device Fault Manager
Follow these steps to reinstall DFM on the Solaris operating system.
Step 1 Close all open or active programs. Do not run other programs during the reinstallation process.
Step 2 As root, log on to the system on which you will reinstall DFM, and mount a local or remote CD-ROM drive. For instructions on mounting the CD-ROM, refer to Appendix A, "Mounting and Unmounting on Solaris."
Step 3 Start the installation program by entering one of the following:
•For a local reinstallation, enter:
•For a remote reinstallation, enter:
where remotedir is the remote location where the CD-ROM is mounted.
The installation program stops CiscoWorks2000, performs a requirements check, and displays the following prompt:
WARNING: User casuser already exists, the installation process will
overwrite its privilege.
Do you want to continue ? (y/n)? [y]
Step 4 Press Return to confirm installing the packages with the correct privileges.
The installation program displays the following installation choices (the choices may vary, depending on your configuration):
1) CiscoWorks2000 Device Fault Manager (reinstall)
2) Device Fault Manager Incremental Device Support (reinstall)
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.
(For more information on reinstallation components, refer to Table 1-1.)
Step 5 Select 1 and 2 and press Return.
Step 6 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.
The reinstallation program checks dependencies and system requirements.
•If there is not enough disk space for the reinstallation, the program displays an error message and stops.
•If the minimum recommended requirements are not met, the program displays an error message and continues installing.
If DFM detects another application using port 162, DFM displays the following message:
WARNING: Installation has detected port 162 in use. DFM is set to use
port 9000 for receiving SNMP traps.
If you see this message, after the reinstallation 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.)
The reinstallation proceeds without displaying any more questions, and the system prompt appears. The reinstallation program copies the files to wherever DFM was originally installed.
Step 7 Unmount and eject the CD-ROM.
Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.
Step 8 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 -u DfmFileNotifier
# NMSROOT/bin/pdcmd -u DfmTrapNotifier
# NMSROOT/bin/pdcmd -u DfmMailNotifier
–For DfmServer:
# NMSROOT/bin/pdcmd -u DfmServer
–For DfmBroker:
# NMSROOT/bin/pdcmd -u DfmBroker
b. Decide which hosts you want to specify using the --accept option with arguments shown in Table 2-3.
Table 2-3 Arguments to the --accept Option
Argument
|
Description
|
host1,host2,...
|
Allow only host1,host2,... to connect to the server. If the hostname is registered with DNS, you can specify the client by hostname. Otherwise, specify explicit IP addresses in a comma-separated list. Hostnames are resolved to one or more IP addresses, which are then used (the server does not use reverse lookups to determine the name of a connecting host).
Note If you specify the clients as hostnames, be sure the 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 -r DfmBroker -e NMSROOT/objects/smarts/bin/brstart -f "--output
--port=9002 --accept=lucy,ethel --restore=NMSROOT/objects/smarts/conf/broker.rps"
–For the DFM server (the following command is one line):
# NMSROOT/bin/pdcmd -r DfmServer -e NMSROOT/objects/smarts/bin/sm_server -d DfmBroker -f
"--bootstrap=DFM_bootstrap.conf --accept=lucy,ethel --output --name=DFM"
–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 -r DfmFileNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -f "--adapter=filelog --output=sm_file_notifier"
# NMSROOT/bin/pdcmd -r DfmTrapNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -f "--adapter=trap --output=sm_trap_notifier"
# NMSROOT/bin/pdcmd -r DfmMailNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -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 -r DfmFileNotifier -d DfmServer -e
NMSROOT/objects/smarts/bin/sm_notify -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 9 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 10 To use DFM, select Device Fault Manager from the CiscoWorks2000 navigation tree.
Step 11 If desired, 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 12 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.
After you install or restart a local version of HP OpenView and NetView, 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), 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, check the installation log, /var/tmp/ciscoinstall.log. 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 the Solaris operating system.
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 root, log on to the system on which DFM is installed, and enter the following to start the uninstallation program (NMSROOT is the DFM installation directory):
# NMSROOT/bin/uninstall.sh
The following prompt appears (the uninstallation choices may vary, depending on your configuration):
1) CiscoWorks2000 Device Fault Manager
(Removing DFM also removes DFM incremental device support. For more information on uninstallation components, refer to Table 1-1.)
Step 2 Enter the appropriate number and press Return. The following prompt appears:
Are you sure you want to uninstall CiscoWorks2000 (y/n)? [y]
Step 3 Press Return to remove your selections.
Ignore all messages that ask if you want to remove packages. The uninstallation program does not accept input to these questions.
When the uninstallation program finishes, the following message appears:
All files were deleted successfully.
The uninstallation program removes the DFM application and updates the system. To install DFM again, refer to the "Performing a New Installation" section.
If you had any errors, check the installation log, /var/tmp/ciscouninstall.log. The Technical Assistance Center (TAC) might ask you to send them the installation log.
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 "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.)
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).
•RME Adapter—Synchronizes the list of managed devices in a local Essentials inventory with the 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 a local 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.)
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 explains 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 these procedures to reinstall the HPOV-NetView Adapter.
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 the HPOV-NetView Adapter.
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 HPOV-NetView Adapter.
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 root, log on to the machine on which you will install or upgrade the HPOV-NetView Adapter, and mount a local or remote CD-ROM drive. For instructions on mounting the CD-ROM, refer to Appendix A, "Mounting and Unmounting on Solaris."
Step 3 Start the installation program by entering one of the following:
•For a local installation, enter:
•For a remote installation, enter:
where remotedir is the remote location where the CD-ROM is mounted.
Step 4 Enter the following to start the installation program:
The installation program stops CiscoWorks2000, performs a requirements check, and displays the following installation choices (the choices may vary, depending on your configuration):
1) CiscoWorks2000 Device Fault Manager
2) Device Fault Manager HPOV-NetView Adapter
Step 5 Enter the appropriate number for the HPOV-NetView Adapter and press Return. (For more information on installation components, refer to Table 1-1.)
Step 6 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). Press Return.
Note Do not use the default, localhost. Also make sure the machine running the DfmBroker is registered with DNS.
The installation program stops HP OpenView or NetView and copies the files to the directory in which CiscoWorks2000 was installed.
Step 7 Eject the CD-ROM.
Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.
Step 8 Restart HP OpenView or NetView to activate the adapter (using the ovstart/nvstart commands).
CiscoWorks2000 automatically configures the remote adapters to forward SNMP traps from HP OpenView and NetView to DFM.
If you had any errors during installation or upgrade, check the installation log, /var/tmp/ciscoinstall.log. The 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
Follow these steps to install or upgrade a remote HPOV-NetView adapter on a host that is not running CiscoWorks2000.
Caution Do not use this script if DFM is installed. If you use the script on a machine containing DFM, you will corrupt the DFM configuration.
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 Not Running CiscoWorks2000" section.
Step 2 Verify that you have 17 MB of space for installing the adapter.
Step 3 Log in as root on the target machine.
Step 4 Verify that DFM is not installed on this machine:
Caution If the dfm.info file is present, DFM is installed. Do not use this script or you will corrupt the DFM configuration.
Step 5 From a temporary directory, use ftp to copy the ascii file NMSROOT/htdocs/rdist/dfm/NMS.bin 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 /opt/CSCOpx).
# cd /tmp
# ftp dfm-host
User (dfm-host:(none)): login
ftp> cd NMSROOT/htdocs/rdist/dfm
ftp> get NMS.bin
Step 6 Run the NMS.bin script:
This message is displayed:
This script will install the Device Fault Manager HPOV-NetView Adapter
Package. Do you want to continue? (y/n) [y]
Step 7 Press Return. You will see this message:
Would you like to install in the default directory? (y/n) [Y]
Step 8 Press Return to install the adapter in the default directory, /opt/DFM.
Caution If you want to install or upgrade the adapter in another directory, you must enter the fully qualified pathname, and a symbolic link is created between that directory and the /opt directory. Do not remove the symbolic link.
This message is displayed:
Enter name or IP address of the machine running DFM Broker:
?[localhost]
Step 9 Enter the name of the machine running the DfmBroker (normally the machine that is running DFM), and press Return.
Note Do not use the default, localhost. Also make sure the machine running the DfmBroker is registered with DNS.
This message is displayed:
You do not need to stop or restart HP OpenView or NetView. CiscoWorks2000 automatically configures the remote adapters to forward SNMP traps from HP OpenView and NetView to DFM.
If you had any errors during installation, check the installation log, /opt/DFM/ciscoNMSinstall.log. The Technical Assistance Center (TAC) might ask you to send them the installation log.
Installing or Upgrading the RME Adapter on a Remote Host
This section explains how to install or upgrade the RME Adapter on a remote host so the adapters 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 RME Adapters.
Step 1 As root, log onto the machine on which you will install or upgrade the HPOV-NetView Adapter, and mount a local or remote CD-ROM drive. For instructions on mounting the CD-ROM, refer to Appendix A, "Mounting and Unmounting on Solaris."
Step 2 Start the installation program by entering one of the following:
•For a local installation, enter:
•For a remote installation, enter:
where remotedir is the remote location where the CD-ROM is mounted.
Step 3 Enter the following to start the installation program:
The installation program stops CiscoWorks2000, performs a requirements check, and displays the following prompt:
WARNING: User casuser already exists, the installation process will
overwrite its privilege.
Do you want to continue ? (y/n)? [y]
Step 4 Press Return to confirm installing or upgrade the adapter with the correct privileges.
The installation program displays the following installation choices (the choices may vary, depending on your configuration):
1) CiscoWorks2000 Device Fault Manager
2) Device Fault Manager RME Adapter
3) Device Fault Manager HPOV-NetView Adapter
Step 5 Enter the appropriate number for the RME Adapter and press Return. (For more information on installation components, refer to Table 1-1.)
The following message is displayed:
Enter name or IP address of the machine running DFM Broker: ?
[localhost]
Step 6 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), and press Return.
Note Do not use the default, localhost. Also make sure the machine running the DfmBroker is registered with DNS.
The installation program copies the files to the default CiscoWorks2000 installation directory, /opt/CSCOpx (NMSROOT).
Step 7 Unmount and eject the CD-ROM.
Note Store the CD-ROM in a secure, climate-controlled area for safekeeping.
After the RME Adapter is installed or upgraded, CiscoWorks2000 automatically configures the adapters to forward Essentials inventory device information to DFM.
If you had any errors during installation, check the installation log, /var/tmp/ciscoinstall.log. The Technical Assistance Center (TAC) might ask you to send them the installation log.
