Table Of Contents
Installing Device Fault Manager
Performing a New Installation
Upgrading Device Fault Manager
Upgrading DFM 1.1 to DFM 1.2 or DFM 1.2 Updated for Common Services Version 2.2
Upgrading DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2
Exporting DFM Information to an Upgraded DFM 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 CiscoWorks
Installing or Upgrading the HPOV-NetView Adapter on a Remote Host Not Running CiscoWorks
Installing or Upgrading the RME Adapter on a Remote Host
Removing Adapters
Removing the HPOV-NetView Adapter from a Remote Host
Removing the HPOV-NetView Adapter from a Remote Host Running CiscoWorks
Removing the HPOV-NetView Adapter from a Remote Host Not Running CiscoWorks
Removing the RME Adapter from a Remote Host
Installing Device Fault Manager
This chapter describes installing Device Fault Manager (DFM) on a Solaris system. It includes:
•
Performing a New Installation
•Upgrading Device Fault Manager
•Reinstalling Device Fault Manager
•Removing Device Fault Manager
•Installing and Upgrading Adapters
•Removing Adapters
This chapter contains instructions for installing both DFM 1.2 and DFM 1.2 Updated for Common Services Version 2.2. Differences in the installations are noted. Keep the following in mind when deciding whether to upgrade to DFM 1.2 Updated for Common Services Version 2.2:
•Upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2 allows your system to manage devices that were not supported when DFM 1.2 was released, and also provides a number of DFM bug fixes. The devices and bug fixes are listed in the Release Notes for Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Windows.
•If you do not plan to upgrade to Common Services 2.2, it may be easier to download and install the latest DFM IDU from: http://www.cisco.com/en/US/products/sw/cscowork/ps2421/prod_upgrades_and_downloads.html.
The IDU includes the same functionality as DFM 1.2 Updated for Common Services Version 2.2, plus additional device support and bug fixes. (If you do upgrade to Common Services 2.2, you can always download and install the DFM IDU after upgrading or re-enabling DFM from the CD.)
•If you upgrade to DFM 1.2 Updated for Common Services Version 2.2, and your system contains installed IDUs that were released after DFM 1.2.3, you will not lose any existing device support.
Performing a New Installation
Follow these steps to perform a new installation of DFM 1.2 or DFM 1.2 Updated for Common Services Version 2.2 on a Solaris system.
Note You can also use this procedure to perform an upgrade from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2 (as directed by the "Upgrading DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2" section). Any differences in the new and upgrade scenarios are duly noted.
Step 1 Make sure your system meets these prerequisites:
•Required (or desired) operating system upgrades have been performed, and required service packs are installed.
•All installed applications are supported by CD One, 5th Edition, or Common Services 2.2, depending on your configuration (see the "Installation and Upgrade Roadmap" section for more information). Applications not supported by CD One, 5th Edition, or Common Services 2.2 will be disabled when you upgrade CD One.
•CD One, 5th Edition, or Common Services 2.2 has been installed. (Refer to Installation and Setup Guide for CD One on Solaris or Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) 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 the HPOV-NetView Adapter (for remote integration).
•If you are installing DFM on top of a machine that already has an installation of the HPOV-NetView Adapter, you must first remove the adapter (refer to the "Removing Adapters" section).
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 "Mounting and Unmounting on Solaris."
Step 4 Start the installation program by entering one of the following:
•For a local installation, enter:
Note If you are installing DFM 1.2 Updated for Common Services 2.2 using a Maintenance Kit CD, run the setup.sh command from a directory other than /cdrom/cdrom0. If you are prompted to validate your DFM image (as described in Step 5), you will have to eject and reinsert CDs, which cannot be done if you are running setup.sh from the /cdrom/cdrom0 directory.
•For a remote installation, enter:
where remotedir is the remote location where the CD-ROM is mounted.
Step 5 If you are installing DFM 1.2 Updated for Common Services Version 2.2, the following may occur:
•If you are installing DFM on CiscoWorks Common Services Version 2.2, you are prompted to accept (and view) the license agreement. Press Return. The installation program stops CiscoWorks and performs a requirements check.
•If you are upgrading using a Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.2), depending on your configuration, you may be prompted to validate your DFM image, as described in the following steps:
a. If you are required to validate your DFM image, you will see this prompt:
To validate the upgrade image, insert a Device Fault Manager
(DFM) 1.2 or earlier CD.
Please ensure that the CD is mounted on /cdrom/cdrom0.
b. Insert a DFM 1.2 (or earlier) CD into one of your system drives. (Close the File Manager window that will open.) The installation software will start validating the DFM image.
c. When the DFM image has been validated, you will see this message:
Please reinsert the original CD to complete the installation.
Press any key to continue.
Reinsert the original CD (containing DFM 1.2 Updated for Common Services Version 2.2) into the drive (close the File Manager window that will open), and continue the installation.
If the DFM image cannot be validated — that is, if you do not have a DFM 1.2 (or earlier) CD — the installation cannot proceed. Contact your Cisco sales representative.
•If you have been directed by this document to use this procedure to perform an upgrade from DFM 1.2, but your system contains installed IDUs that were released after DFM 1.2.3 (such as DFM 1.2 IDU 1.2.4), the installation program displays the following prompt:
The installation program has detected a newer version of DFM
already on your system. The newer version is disabled. Do you want
to enable it? (y/n) [y]
Do one of the following:
–To enable DFM, press Return. Because continuing the installation would add no new functionality, further DFM installation is not required, and the installation program exits. To re-establish settings that were lost when CiscoWorks Common Services 2.2 was installed (and DFM was disabled), proceed to Step 15.
–To keep DFM disabled, enter n and press Return. DFM remains disabled, and the installation program exits.
Step 6 If you are installing DFM 1.2, the installation program stops CiscoWorks, 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]
Press Return to confirm installing the packages with the correct privileges.
Step 7 The installation program displays the following installation choices (the choices may vary, depending on your configuration):
1) CiscoWorks Device Fault Manager
2) Device Fault Manager HPOV-NetView adapters
Select one of the items using its number or enter q to quit [q]
Step 8 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.)
Step 9 The installation program asks if you will be using DFM with a remote version of VHM 1.0:
Will you be connecting VHM 1.0 with this instance of DFM? [y/n] ? [n]
Do one of the following:
•If you will be using a remote version of VHM 1.0 with DFM, enter y and press Return.
The installation proceeds without displaying any more questions, and the system prompt appears. The installation program copies the files to the CiscoWorks default installation directory /opt/CSCOpx (NMSROOT). Proceed to Step 14.
•If you will not be using a remote version of VHM 1.0 with DFM, press Return. Proceed to Step 10.
Note You must give the same answer to this question when you install adapters. If you answer N and provide a DFM username and password, you must provide the same username and password pair when you install adapters.
Step 10 The installation program asks for your DFM username and displays the following message and prompt:
Valid username is 4-20 characters, [a-z], [A-Z], [0-9],- _,$
Step 11 Enter a username using valid characters and press Return.
Step 12 The installation program asks you for your DFM password and displays the following message and prompt:
Valid password is 4-20 characters, [a-z], [A-Z], [0-9],-,_,$
Step 13 Enter a password using valid characters and press Return.
Note You can change your username and password. See the User Guide for Device Fault Manager, available from the online help, for more information.
The installation proceeds without displaying any more questions, and the system prompt appears. The installation program copies the files to the CiscoWorks default installation directory /opt/CSCOpx (NMSROOT).
Step 14 Unmount and eject the CD-ROM, and store it in a secure, climate-controlled area for safekeeping.
Step 15 Specify the clients that are allowed to connect to the DFM server. (DFM provides this fine-grain control as an additional security feature.)
Note If you specify registration options using pdcmd, you must re-run your command whenever the daemon manager restarts.
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 one or both of the following apply:
–You are running DHCP
–You specified the clients with hostnames
Step 16 To verify that the DfmServer process is running, log on to the CiscoWorks desktop as the administrator and select Server Configuration >
Administration > Process Management > Process Status.
Note If your client does not have the Java plug-in, you will receive a message asking if you want to install it. The plug-in is required for DFM.
Step 17 If you plan to use remote adapters with Device Fault Manager 1.2, perform these steps:
a. Make sure the machine running the DfmBroker is registered with DNS.
b. Install all remote adapters as described in the "Installing and Upgrading Adapters" section.
Step 18 If you have been directed by this document to use this procedure to perform an upgrade from DFM 1.2, proceed to "Exporting DFM Information to an Upgraded DFM Remote Host" section.
Step 19 To use DFM, select Device Fault Manager from the CiscoWorks navigation tree.
If the standard UDP trap port (162) is being used by another NMS, you must configure the SNMP Trap Adapter to use a different UDP port, such as port 9000. Refer to the "Configuring the SNMP Trap Adapter" section.
If you install another NMS after installing DFM, you must:
1. Configure DFM to forward traps to the listening port for the NMSs. Refer to the "Enabling DFM to Send Traps to NMSs" section.
2. Make sure the NMSs are configured to receive traps at the port you specify in Step 1. Refer to the appropriate documentation for the NMS.
After you install or restart a local version of HP OpenView and NetView, CiscoWorks 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 is installed later), CiscoWorks automatically configures the adapters to forward Essentials inventory device information to DFM. To do this with remote versions of HP OpenView, NetView, or Essentials, you must install the remote adapters as described in the "Installing and Upgrading Adapters" section.
If you had any errors, check the installation log, /var/tmp/ciscoinstall.log. The Technical Assistance Center (TAC) might ask you to send them the installation log.
Upgrading Device Fault Manager
These sections provide for upgrading procedures.
•Upgrading DFM 1.1 to DFM 1.2 or DFM 1.2 Updated for Common Services Version 2.2
•Upgrading DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2
•Exporting DFM Information to an Upgraded DFM Remote Host
Upgrading DFM 1.1 to DFM 1.2 or DFM 1.2 Updated for Common Services Version 2.2
You can upgrade Device Fault Manager 1.1 (installed with or without IDS 1.1.x patches) on local or remote machines. If desired, you can upgrade a remote machine and then export your local DFM 1.1 information to the upgraded remote machine.
When you upgrade a local version of DFM 1.1 to either DFM 1.2 or DFM 1.2 Updated for Common Services Version 2.2, the upgrade program saves and restores the DFM 1.1 seed file, adapter files, repository, and consoles. If desired, you can manually restore the log files from NMSROOT/objects/smarts/logs.
Note Customized remote consoles are not saved after the upgrade.
Follow these steps to upgrade a local DFM 1.1 host to either DFM 1.2 or DFM 1.2 Updated for Common Services Version 2.2.
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, 5th Edition, or Common Services 2.2, depending on your configuration (see the "Installation and Upgrade Roadmap" section for more information). Applications not supported by CD One, 5th Edition, or Common Services 2.2 will be disabled when you upgrade CD One.
•CD One, 5th Edition, or Common Services 2.2 has been installed. (Refer to Installation and Setup Guide for CD One on Solaris or Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) 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).
•If you are installing DFM on top of a machine that already has an installation of the HPOV-NetView Adapter, you must first remove the adapter (refer to the "Removing Adapters" section).
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 "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.
Note If you are upgrading to DFM 1.2 Updated for Common Services 2.2 using a Maintenance Kit CD, run the setup.sh command from a directory other than /cdrom/cdrom0. If you are prompted to validate your DFM image (as described in Step 5), you will have to eject and reinsert CDs, which cannot be done if you are running setup.sh from the /cdrom/cdrom0 directory.
Step 5 If you are upgrading to DFM 1.2 Updated for Common Services Version 2.2, the following occurs:
a. You are prompted to accept (and view) the license agreement. Press Return. The installation program stops CiscoWorks and performs a requirements check.
b. If you are upgrading using a Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.2), depending on your configuration, you may be prompted to validate your DFM image, as described in the following steps:
a. If you are required to validate your DFM image, you will see this prompt:
To validate the upgrade image, insert a Device Fault Manager
(DFM) 1.2 or earlier CD.
Please ensure that the CD is mounted on /cdrom/cdrom0.
b. Insert a DFM 1.2 (or earlier) CD into one of your system drives. (Close the File Manager window that opens.) The installation software will start validating the DFM image.
c. When the DFM image has been validated, you will see this message:
Please reinsert the original CD to complete the installation.
Press any key to continue.
Reinsert the original CD (containing DFM 1.2 Updated for Common Services Version 2.2) into the drive (close the File Manager window that will open) and continue the installation.
If the DFM image cannot be validated — that is, if you do not have a DFM 1.2 (or earlier) CD — the installation cannot proceed. Contact your Cisco sales representative.
c. If your system contains installed IDUs that were released after DFM 1.2.3 (such as DFM 1.2 IDU 1.2.4), the installation program displays the following prompt:
The installation program has detected a newer version of DFM
already on your system. The newer version is disabled. Do you want
to enable it? (y/n) [y]
Do one of the following:
–To enable DFM, press Return. Because continuing the installation would add no new functionality, further DFM installation is not required, and the installation program exits. To re-establish settings that were lost when CiscoWorks Common Services 2.2 was installed (and DFM was disabled), proceed to Step 15.
–To keep DFM disabled, enter n and press Return. DFM remains disabled, and the installation program exits.
Step 6 If you are upgrading to DFM 1.2, the installation program stops CiscoWorks, 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]
Press Return to confirm installing the packages with the correct privileges.
Step 7 The installation program displays the following installation choices (the choices may vary, depending on your configuration; see Table 1-1):
1) CiscoWorks Device Fault Manager
2) Device Fault Manager HPOV-NetView adapters
2) RME Adapter
Step 8 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 18.)
Step 9 The installation program asks if you will be using DFM with a remote version of VHM 1.0:
Will you be connecting VHM 1.0 with this instance of DFM? [y/n] ? [n]
Do one of the following:
•If you will be using a remote version of VHM 1.0 with DFM, enter y and press Return.
The installation program copies the files to the CiscoWorks default installation directory /opt/CSCOpx (NMSROOT), and the system prompt appears.
Proceed to Step 14.
•If you will not be using a remote version of VHM 1.0 with DFM, Return. Proceed to Step 10.
Note You must give the same answer to this question when you install adapters. If you answer n and provide a DFM username and password, you must provide the same username and password pair when you install adapters.
Step 10 The installation program asks for your DFM username and displays the following message and prompt:
Valid username is 4-20 characters, [a-z], [A-Z], [0-9],- _,$
Step 11 Enter a username using valid characters and press Return.
Step 12 The installation program asks you for your DFM password and displays the following message and prompt:
Valid password is 4-20 characters, [a-z], [A-Z], [0-9],-,_,$
Step 13 Enter a password using valid characters and press Return.
Note You can change your username and password. See the User Guide for Device Fault Manager, available from the online help, for more information.
The installation program copies the files to the CiscoWorks default installation directory /opt/CSCOpx (NMSROOT), and the system prompt appears.
Step 14 Unmount and eject the CD-ROM, and store it in a secure, climate-controlled area for safekeeping.
Step 15 Specify the clients that are allowed to connect to the DFM server. (DFM provides this fine-grain control as an additional security feature.)
Note If you specify registration options using pdcmd, you must re-run your command whenever the daemon manager restarts.
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 one or both of the following apply:
–You are running DHCP
–You specified the clients with hostnames
Step 16 To verify that the DfmServer process is running, log on to the CiscoWorks desktop as the administrator and select Server Configuration >
Administration > Process Management > Process Status.
Note If your client does not have the Java plug-in, you will receive a message asking if you want to install it. The plug-in is required for DFM.
Step 17 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 18 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 19 If you are upgrading from DFM 1.1 and plan to use remote adapters with either DFM 1.2 or DFM 1.2 Updated for Common Services Version 2.2, perform these steps:
a. Make sure the machine running the DfmBroker is registered with DNS.
b. Upgrade all remote adapters as described in the "Installing and Upgrading Adapters" section. If the adapters are installed on a remote VHM 1.0 machine, they do not need to be upgraded.
c. For remote versions of VHM 1.0, restart the remote VHM server process.
Step 20 Proceed to the "Exporting DFM Information to an Upgraded DFM Remote Host" section.
If the standard UDP trap port (162) is being used by another NMS—such as Cisco Voice Manager, Traffic Director, or Real Time Monitor—you must configure the SNMP Trap Adapter to use a different UDP port, such as port 9000. Refer to the "Configuring the SNMP Trap Adapter" section.
If you install another NMS—such as Cisco Voice Manager, Traffic Director, or Real Time Monitor—after installing DFM, you must:
1. Configure DFM to forward traps to the listening port for the NMSs. Refer to the "Enabling DFM to Send Traps to NMSs" section.
2. Make sure the NMSs are configured to receive traps at the port you specify in Step 1. Refer to the appropriate documentation for the NMS.
After you install or restart a local version of HP OpenView and NetView, CiscoWorks 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 is installed later), CiscoWorks automatically configures the adapters to forward Essentials inventory device information to DFM. To do this with remote versions of HP OpenView, NetView, or Essentials, you must install the remote adapters as described in the "Installing and Upgrading Adapters" section.
If you had any errors, check the installation log, /var/tmp/ciscoinstall.log. The Technical Assistance Center (TAC) might ask you to send them the installation log.
Upgrading DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2
You can upgrade Device Fault Manager 1.2, 1.2.1, and 1.2.2 on local or remote machines. To upgrade from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2, follow the procedure in the "Performing a New Installation" section. You do not need to do any data preservation, nor do you need to upgrade any adapters when upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2.
Keep the following in mind when deciding whether to upgrade to DFM 1.2 Updated for Common Services Version 2.2:
•Upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2 allows your system to manage devices that were not supported when DFM 1.2 was released, and also provides a number of DFM bug fixes. The devices and bug fixes are listed in the Release Notes for Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Windows.
•If you do not plan to upgrade to Common Services 2.2, it may be easier to download and install the latest DFM IDU from: http://www.cisco.com/en/US/products/sw/cscowork/ps2421/prod_upgrades_and_downloads.html.
The IDU includes the same functionality as DFM 1.2 Updated for Common Services Version 2.2, plus additional device support and bug fixes. (If you do upgrade to Common Services 2.2, you can always download and install the DFM IDU after upgrading or re-enabling DFM from the CD.)
•If you upgrade to DFM 1.2 Updated for Common Services Version 2.2, and your system contains installed IDUs that were released after DFM 1.2.3, you will not lose any existing device support.
If desired, you can upgrade a remote machine and then export your local DFM information to the upgraded remote machine. See the "Exporting DFM Information to an Upgraded DFM Remote Host" section for more information.
Exporting DFM Information to an Upgraded DFM Remote Host
This procedure exports your local DFM configuration information and imports it to a remote DFM machine that has been upgraded. This procedure applies to the following scenarios:
•Exporting local DFM 1.1 information to a remote host running DFM 1.2
•Exporting local DFM 1.1 information to a remote host running DFM 1.2 Upgraded for Common Services Version 2.2
•Exporting local DFM 1.2 information to a remote host running DFM 1.2 Updated for Common Services Version 2.2
Step 1 As the local administrator, log on to the local DFM system, and insert the upgrade CD-ROM into the CD-ROM drive. (For instructions on mounting the CD-ROM, refer to "Mounting and Unmounting on Solaris.") For example:
•On the DFM 1.1 system, insert the DFM 1.2 CD-ROM
•On the DFM 1.1 system, insert the DFM 1.2 Updated for Common Services Version 2.2 CD-ROM
•On the DFM 1.2 system, insert the DFM 1.2 Updated for Common Services Version 2.2 CD-ROM.
Step 2 Stop the CiscoWorks daemon manager:
Step 3 If desired, export your CD One information. Refer to Installation and Setup Guide for CD One on Solaris.
Step 4 From the top-level directory, run the export script:
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 Extract the files on the remote machine:
# tar -xvf dfmupgrade.tar
Step 7 On the local DFM machine, restart the CiscoWorks daemon manager:
# /etc/init.d/dmgtd start
Step 8 On the remote (upgraded) DFM machine, stop the CiscoWorks daemon manager:
Step 9 If desired, import your CD One information. Refer to Installation and Setup Guide for CD One on Solaris.
Step 10 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 11 Enter Y and press Return. When the import has completed, you will see the following message:
Finished upgrading DFM files...
Step 12 Restart the CiscoWorks daemon manager:
# /etc/init.d/dmgtd start
Step 13 Rediscover the devices in your DFM inventory by selecting Inventory > Inventory Collect All.
If any errors occurred during the upgrade, check the installation log, /var/tmp/ciscoinstall.log. The Technical Assistance Center (TAC) 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 "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.
Step 4 If you are reinstalling DFM 1.2 Updated for Common Services Version 2.2, and you are reinstalling DFM on CiscoWorks Common Services 2.2, you are prompted to accept (and view) the license agreement. Press Return. The installation program stops CiscoWorks and performs a requirements check.
Step 5 If you are reinstalling DFM 1.2 Updated for Common Services Version 2.2 and your system contains installed IDUs that were released after DFM 1.2.3 (such as DFM 1.2 IDU 1.2.4), you will see one of the following messages:
•If you did enable DFM when you first installed it, the installation program displays the following prompt:
A newer version of DFM is already running on your system.
Because the installation would provide no new functionality, the installation program exits, and your existing device support is preserved.
•If you did not enable DFM when you first installed it, the installation program displays the following prompt:
The installation program has detected a newer version of DFM
already on your system. The newer version is disabled. Do you want
to enable it? (y/n) [y]
Do one of the following:
–To enable DFM, press Return. Because continuing the installation would add no new functionality, further DFM installation is not required, and the installation program exits. To re-establish settings that were lost when CiscoWorks Common Services 2.2 was installed (and DFM was disabled), proceed to Step 17.
–To keep DFM disabled, enter n and press Return. DFM remains disabled, and the installation program exits.
Step 6 If you are installing DFM 1.2, the installation program stops CiscoWorks, 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 7 Press Return to confirm installing the packages with the correct privileges.
The reinstallation program displays the following installation choices (the choices may vary, depending on your configuration; refer to Table 1-1):
1) CiscoWorks Device Fault Manager (reinstall)
2) Device Fault Manager Incremental Device Support (reinstall)
(For more information on reinstallation components, refer to Table 1-1.)
Step 8 If you are reinstalling DFM 1.2 Updated for Common Services Version 2.2, select 1 and press Return.
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.
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.)
Step 10 The installation program asks if you will be using DFM with a remote version of VHM 1.0:
Will you be connecting VHM 1.0 with this instance of DFM? [y/n] ? [n]
Do one of the following:
•If you will be using a remote version of VHM 1.0 with DFM, enter y and press Return. Proceed to Step 15.
The reinstallation proceeds without displaying any more questions, and the system prompt appears. The reinstallation program copies the files to the directory DFM was originally installed.
•If you will not be using a remote version of VHM 1.0 with DFM, press Return. Proceed to Step 11.
Note You must give the same answer to this question when you install adapters. If you answer n and provide a DFM username and password, you must provide the same username and password pair when you install adapters.
Step 11 The installation program asks for your DFM username and displays the following message and prompt:
Valid username is 4-20 characters, [a-z], [A-Z], [0-9],- _,$
Step 12 Enter a username using valid characters and press Return.
Step 13 The installation program asks you for your DFM password and displays the following message and prompt:
Valid password is 4-20 characters, [a-z], [A-Z], [0-9],-,_,$
Step 14 Enter a password using valid characters and press Return.
Note You can change your username and password. See the User Guide for Device Fault Manager, available from the online help, for more information
The reinstallation proceeds without displaying any more questions, and the system prompt appears. The reinstallation program copies the files to the directory DFM was originally installed.
Step 15 Unmount and eject the CD-ROM, and store it in a secure, climate-controlled area for safekeeping.
Step 16 Specify the clients that are allowed to connect to the DFM server. (DFM provides this fine-grain control as an additional security feature.)
Note If you specify registration options using pdcmd, you must re-run your command whenever the daemon manager restarts.
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: one or both of the following apply
–You are running DHCP
–You specified the clients with hostnames
Step 17 To verify that the DfmServer process is running, log on to the CiscoWorks desktop as the administrator and select Server Configuration >
Administration > Process Management > Process Status.
Note If your client does not have the Java plug-in, you will receive a message asking if you want to install it. The plug-in is required for DFM.
Step 18 To use DFM, select Device Fault Manager from the CiscoWorks navigation tree.
Step 19 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 20 If you used remote adapters with either Device Fault Manager 1.2 or DFM 1.2 Updated for Common Services Version 2.2, perform these steps:
a. Make sure the machine running the DfmBroker is registered with DNS.
b. Upgrade all remote adapters as described in the "Installing and Upgrading Adapters" section.
After you install or restart a local version of HP OpenView and NetView, CiscoWorks 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 is installed later), CiscoWorks automatically configures the adapters to forward Essentials inventory device information to DFM. To do this with remote versions of HP OpenView, NetView, or Essentials, you must install the remote adapters as described in the "Installing and Upgrading Adapters" section.
If you had any errors, 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 CiscoWorks uninstallation program to remove DFM from your system. If you try to remove the files and programs manually, you can seriously damage your system.
Step 1 As root, log 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; see Table 1-1):
3) CiscoWorks Common Services
Select one of the items using its number or enter q to quit [q]
(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: the name of the selection (y/n)?
[n]
Step 3 Enter y and press Return to remove your selections. The following prompt appears:
Delete the CiscoWorks packages? (y/n) [y]
Step 4 Press Return.
Ignore all messages that ask if you want to remove packages. The uninstallation program does not accept input to these questions.
When the uninstallation program finishes, the following message appears:
All files were deleted successfully.
The uninstallation program removes the DFM application and updates the system. To install DFM again, 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 User Guide for Device Fault Manager (available from online help).
Types of Adapters: Local and Remote
Local adapters are installed for forwarding traps or synchronizing information with NMSs running on the DFM host; remote adapters do the same, but on remote hosts not running DFM.
Local Adapters
When you install DFM locally, all adapters are installed. The local adapters include:
•File Notifier Adapter—Logs alarms detected by the DFM server and forwards them to a file. A file is the only valid recipient for this adapter. This adapter is normally used to create a historical file containing all alarms generated by DFM.
•Trap Notifier Adapter—Converts DFM alarms into SNMP trap messages and forwards the traps to recipients. You can specify recipients, such as NMSs or other domain managers, using an IP address or a system name. This adapter is normally used to send DFM alarms to another application for additional processing or display.
•Mail Notifier Adapter—Using SMTP, send mail notifications to recipients. As with the Trap Notifier Adapter, you can specify recipients—in this case, an email address. This adapter is normally used to generate asynchronous email notifications (for example, to an epage or an email address) when one or more alarm conditions occur.
•SNMP Trap Adapter—Listens on a user-specified port for traps sent to DFM from managed devices, and forwards traps to specified destinations. This adapter provides a generic method for integrating DFM with other NMS applications. The SNMP Trap Adapter is normally used to allow DFM to coexist with another trap-receiving application (such as an NMS) on the same server; have an NMS forward traps to DFM for processing; or have DFM listen for traps on devices and forward the traps to an NMS that does not support trap forwarding. Basic steps for configuring this adapter are provided in "Getting Started."
•HPOV-NetView Adapter—Forwards traps that managed devices send to a local HP OpenView or NetView NMS to DFM. This adapter is normally used when you want DFM to monitor faults on devices managed by a local version of HP OpenView or NetView. (For information on supported HP OpenView and NetView versions, refer to the "Supported NMS Integration" section.)
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.)
Note If you want to install DFM on top of a machine that already has an installation of the HPOV-NetView Adapter, you must first remove the adapter (refer to the "Removing Adapters" 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 User Guide for Device Fault Manager (available from online help).
Note Whenever you configure any adapter using the command line, you must manually stop and restart the adapter. Adapters configured with the DFM administration menus do not need to be stopped and restarted.
Table 2-4 Configuring and Starting Adapters
Adapter Type
and Name
|
Must Be Configured Before Use
|
Can Be Configured Using...
|
Automatically Starts with CiscoWorks
|
GUI
|
CLI
|
Notification Adapters
|
File Notifier
Trap Notifier
Mail Notifier
|
Yes
|
Yes
|
Yes
|
No
|
Yes
|
Yes
|
Yes
|
No
|
Yes
|
Yes
|
Yes
|
No
|
Event Adapters
|
HPOV-NetView
|
No
|
No
|
Yes
|
Yes, if HP OpenView or NetView is installed on the same machine as the adapter
|
Special Adapters
|
SNMP Trap
RME Adapter
|
Yes
|
Yes
|
Yes
|
Yes
|
No
|
N/A, but can be started using the GUI
|
N/A
|
Yes, if Essentials is installed on the same machine as the adapter
|
Installing or Upgrading the HPOV-NetView Adapter on a Remote Host
This section 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 CiscoWorks is present. You can also use these procedures to reinstall the HPOV-NetView Adapter.
If you upgrade a local version of DFM 1.1, you must also upgrade all remote adapters. You do not need to upgrade DFM 1.2 adapters if you are upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2.
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 CiscoWorks
Follow these steps to install or upgrade a remote 1.1 version of the HPOV-NetView adapter on a host that is running CiscoWorks. You do not need to upgrade DFM 1.2 adapters if you are upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2.
Step 1 If you want to upgrade a 1.1 version of the HPOV-NetView Adapter, remove the adapter as described in the "Removing the HPOV-NetView Adapter from a Remote Host Running CiscoWorks" 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 "Mounting and Unmounting on Solaris." (Alternatively, you can install the adapter using DFM 1.2 Patch/IDU 1.2.7 or later, and proceed to Step 4.)
Note To use the HPOV-NetView Adapter with NetView, be sure to install the adapter on the same drive as NetView.
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 CiscoWorks, performs a requirements check, and displays the following installation choices (the choices may vary, depending on your configuration; refer to Table 1-1):
1) CiscoWorks 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.
Step 7 The installation program asks if you will be using DFM with a remote version of VHM 1.0:
Will you be connecting VHM 1.0 with this instance of DFM? [y/n] ? [n]
Note You must give the same answer to this question that you gave when installing DFM. If you answered n to this question when installing DFM, you must provide the same username and password pair that you provided for DFM.
Do one of the following:
•If you will be using a remote version of VHM 1.0 with DFM, enter y and press Return.
The installation program stops HP OpenView or NetView and copies the files to the directory in which CiscoWorks was installed.
Proceed to Step 12.
•If you will not be using a remote version of VHM 1.0 with DFM, press Return. Proceed to Step 8.
Step 8 The installation program asks for your DFM username and displays the following message and prompt:
Valid username is 4-20 characters, [a-z], [A-Z], [0-9],- _,$
Step 9 Enter a username using valid characters and press Return.
Step 10 The installation program asks you for your DFM password and displays the following message and prompt:
Valid password is 4-20 characters, [a-z], [A-Z], [0-9],-,_,$
Step 11 Enter a password using valid characters and press Return.
Note You can change your username and password. See the User Guide for Device Fault Manager, available from the online help, for more information.
The installation program stops HP OpenView or NetView and copies the files to the directory in which CiscoWorks was installed.
Step 12 Eject the CD-ROM, and store it in a secure, climate-controlled area for safekeeping.
Step 13 Restart HP OpenView or NetView to activate the adapter (using the ovstart/nvstart commands).
If you want to install DFM on top of a machine that already has an installation of the HPOV-NetView Adapter, you must first remove the adapter (refer to the "Removing Adapters" section).
CiscoWorks 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 CiscoWorks
Follow these steps to install or upgrade a remote 1.1 version of the HPOV-NetView adapter on a host that is not running CiscoWorks. You do not need to upgrade DFM 1.2 adapters if you are upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2.
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.1 version of the HPOV-NetView Adapter, remove the adapter as described in the "Removing the HPOV-NetView Adapter from a Remote Host Not Running CiscoWorks" section.
Step 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.2 or DFM 1.2 Updated for Common Services Version 2.2 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.
Step 10 The installation program asks if you will be using DFM with a remote version of VHM 1.0:
Will you be connecting VHM 1.0 with this instance of DFM? [y/n] ? [n]
Note You must give the same answer to this question that you gave when installing DFM. If you answered n to this question when installing DFM, you must provide the same username and password pair that you provided for DFM.
Do one of the following:
•If you will be using a remote version of VHM 1.0 with DFM, enter y and press Return.
This message is displayed:
You do not need to stop or restart HP OpenView or NetView. CiscoWorks 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.
•If you will not be using a remote version of VHM 1.0 with DFM, press Return. Proceed to Step 11.
Step 11 The installation program asks for your DFM username and displays the following prompt:
Valid username is 4-20 characters, [a-z], [A-Z], [0-9],- _,$
Step 12 Enter a username using valid characters and press Return.
Step 13 The installation program asks you for your DFM password and displays the following prompt:
Valid password is 4-20 characters, [a-z], [A-Z], [0-9],-,_,$
Step 14 Enter a password using valid characters and press Return.
Note You can change your username and password. See the User Guide for Device Fault Manager, available from the online help, for more information.
This message is displayed:
If you want to install DFM on top of a machine that already has an installation of the HPOV-NetView Adapter, you must first remove the adapter (refer to the "Removing Adapters" section).
You do not need to stop or restart HP OpenView or NetView. CiscoWorks 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 1.1, you must also upgrade all remote adapters. You do not need to upgrade DFM 1.2 adapters if you are upgrading from DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2.
Note If the DFM broker is moved—for example, if DFM is moved to a different machine, or you want to use a different instance of DFM—you must reinstall the 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 "Mounting and Unmounting on Solaris." (Alternatively, you can install the adapter using DFM 1.2 Patch/IDU 1.2.7 or later, and proceed to Step 3.)
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 CiscoWorks, 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; see Table 1-1):
1) CiscoWorks 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.
Step 7 The installation program asks if you will be using DFM with a remote version of VHM 1.0:
Will you be connecting VHM 1.0 with this instance of DFM? [y/n] ? [n]
Note You must give the same answer to this question that you gave when installing DFM. If you answered n to this question when installing DFM, you must provide the same username and password pair that you provided for DFM.
Do one of the following:
•If you will be using a remote version of VHM 1.0 with DFM, enter y and press Return.
The installation program copies the files to the default CiscoWorks installation directory, /opt/CSCOpx (NMSROOT).
Proceed to Step 12.
•If you will not be using a remote version of VHM 1.0 with DFM, press Return. Proceed to Step 8.
Step 8 The installation program asks for your DFM username and displays the following message and prompt:
Valid username is 4-20 characters, [a-z], [A-Z], [0-9],- _,$
Step 9 Enter a username using valid characters and press Return.
Step 10 The installation program asks you for your DFM password and displays the following message and prompt:
Valid password is 4-20 characters, [a-z], [A-Z], [0-9],-,_,$
Step 11 Enter a password using valid characters and press Return.
Note You can change your username and password. See the User Guide for Device Fault Manager for more information.
The installation program copies the files to the default CiscoWorks installation directory, /opt/CSCOpx (NMSROOT).
Step 12 Unmount and eject the CD-ROM, and store it in a secure, climate-controlled area for safekeeping.
After the RME Adapter is installed or upgraded, CiscoWorks 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.
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.
Note If you want to install DFM on top of a machine that already has an installation of the HPOV-NetView Adapter, you must first remove the adapter (refer to the "Removing Adapters" section).
Removing the HPOV-NetView Adapter from a Remote Host
You can remove the HPOV-NetView Adapter from remote host machines with or without installed CiscoWorks products.
Caution You must use the following uninstallation programs to remove the adapters from your system. If you try to remove the files and programs manually, you can seriously damage your system.
Removing the HPOV-NetView Adapter from a Remote Host Running CiscoWorks
Use this procedure to remove the HPOV-NetView Adapter from a remote host that is running CiscoWorks.
Step 1 Log in as root on the target machine.
Step 2 Run the uninstall shell script (NMSROOT is the DFM installation directory):
# NMSROOT/bin/uninstall.sh
The following prompt appears (depending on your configuration):
3) CiscoWorks Common Services
4) Device Fault Manager HPOV-NetView adapters
Step 3 Enter the appropriate number for the HPOV-NetView Adapter and press Return.
The following prompt appears:
Are you sure you want to uninstall: Device Fault Manager HPOV-NetView
adapters (y/n)? [n]
Step 4 Enter y and press Return
The following prompt appears:
Delete the CiscoWorks packages? (y/n)? [y]
Step 5 Press Return to remove your selections.
When the uninstallation program finishes, the following message appears:
All files were deleted successfully.
Removing the HPOV-NetView Adapter from a Remote Host Not Running CiscoWorks
Use this procedure to remove the HPOV-NetView Adapter from a remote host that is not running CiscoWorks.
Step 1 Log in as root on the target machine.
Step 2 Run the uninstallation script:
# cd /tmp
# /opt/DFM/objects/dfm/bin/removeNMS
This message is displayed:
Calling remove script.
Removing /opt/DFM.
Removing the RME Adapter from a Remote Host
This section describes how to remove the RME Adapter from a remote host.
Caution You must use the CiscoWorks uninstallation program to remove the RME Adapter from your system. If you try to remove the files and programs manually, you can seriously damage your system.
Step 1 Log in as root on the target machine.
Step 2 Run the uninstall shell script (NMSROOT is the DFM installation directory):
# NMSROOT/bin/uninstall.sh
The following prompt appears (depending on your configuration):
3) CiscoWorks Common Services
4) Device Fault Manager RME Adapter
5) Resource Manager Essentials
6) all of the above
Select one of the items using its number or enter q to quit [q]
Step 3 Enter the appropriate number for the RME Adapter and press Return. The following prompt appears:
Are you sure you want to uninstall: Device Fault Manager RME adapter
(y/n)? [n]
Step 4 Enter y and press Return. The following prompt appears:
Delete the CiscoWorks packages? (y/n)? [y]
Step 5 Press Return. CiscoWorks stops and the package is uninstalled.
If you had any errors during uninstallation, check the installation log, /var/tmp/ciscouninstall.log. The Technical Assistance Center (TAC) might ask you to send them the installation log.
