Table Of Contents
Installation and Upgrade Roadmap
Server Requirements and Recommendations
Supported NMS Environments for Device Import
Prerequisites
This chapter describes the prerequisites for installing Device Fault Manager (DFM) on a Windows 2000 or Windows NT system. It includes:
•
Installation and Upgrade Roadmap
•
•
Product Overview
Device Fault Manager is a network management and analytical tool that enables you to monitor your network devices and determine the cause of device problems. It consists of both internal components and a graphical user interface (GUI).
Table 1-1 describes which DFM components are installed when you select one of the installation options.
Table 1-1 DFM Installation Options and Their Contents
CiscoWorks2000
Device Fault ManagerDFM; the base package for DFM incremental device support (which enables you to download support for new devices from Cisco.com); the RME Adapter for synchronizing DFM with a local version of Resource Manager Essentials (Essentials); and the HPOV-NetView Adapter for integrating DFM with local versions of HP OpenView and NetView. This option is normally chosen to install the entire DFM product on a local machine.
Device Fault Manager Incremental Device Support
Only the base package for DFM incremental device support, which enables you to download support for new devices from Cisco.com. This option is normally chosen to reinstall Incremental Device Support (IDS).
Device Fault Manager HPOV-NetView Adapter
Only the HPOV-NetView Adapter. This option is normally chosen to install the adapter on a remote machine running HP OpenView or NetView, to forward traps from these remote network management systems (NMSs) to a local DFM. For information on how to configure and start this adapter, refer to Table 2-4.
Device Fault Manager
RME AdapterOnly the RME Adapter. This option is normally chosen to install the adapter on a remote machine running Resource Manager Essentials (RME), to send a list of devices in the remote Essentials inventory to a local DFM. For information on how to configure and start this adapter, refer to Table 2-4.
Installation and Upgrade Roadmap
Table 1-2 provides an overview of DFM installation scenarios.
Table 1-2 DFM Installation Roadmap
refer to...CiscoWorks2000 Device Fault Manager as a standalone
N/A
Install CiscoWorks2000 Device Fault Manager
Device Fault Manager with Resource Manager Essentials
Essentials is installed on the DFM host
Install CiscoWorks2000 Device Fault Manager (the RME Adapter will be installed)
Essentials is not installed on the DFM host
Install RME Adapter on the remote Essentials host
Device Fault Manager with HP OpenView or NetView
HP OpenView or NetView is installed on the DFM host
Install CiscoWorks2000 Device Fault Manager (the HPOV-NetView Adapter will be installed)
HP OpenView or NetView is not installed on the DFM host
and CiscoWorks2000 is installed on the HP OpenView or NetView host
Install HPOV-NetView Adapter on the remote HP OpenView or NetView host
Installing or Upgrading the HPOV-NetView Adapter on a Remote Host Running CiscoWorks2000
and CiscoWorks2000 is not installed on the HP OpenView or NetView host
Install HPOV-NetView Adapter on the remote HP OpenView or NetView host
Installing or Upgrading the HPOV-NetView Adapter on a Remote Host Not Running CiscoWorks2000
Device Fault Manager with another NMS
You want DFM to both receive traps from and forward traps (including correlation traps) to the NMS
1.
2.
3.
Table 1-3 provides an overview of upgrade scenarios.
Installation Paths
You can install DFM on:
•
•
To support integration with remote HP OpenView and NetView, and device list synchronization with remote Essentials 3.x systems, you must also install individual adapters on the remote NMS machines. For more information, refer to the "Installing and Upgrading Adapters" section.
Server Requirements and Recommendations
The server system requirements for installing DFM are shown in Table 1-4. These requirements apply when installing DFM on:
•
•
Table 1-4 also provides configuration recommendations when running DFM with CD One or Essentials. These major considerations can help you select or configure a server system that best meets your needs:
•
Note
To find out how many trunk and access ports are currently imported into DFM, use the sm_tpmgr command (described in more detail in the Device Fault Manager User Guide, available from online help):
# NMSROOT\objects\smarts\bin\sm_tpmgr.exe --server=DFM --sizes•
Note
Table 1-4 Server System Requirements and Recommendations
System Hardware
•
•
•
Memory (RAM)
•
Available Drive Space
•
•
•
System Software
One of the following:
•
•
•
Additional Software (Optional)
One of the following browsers (if you are using the CiscoWorks2000 desktop on the server system):
•
Java Virtual Machine (JVM) version 5.0.0.3167 or current shipping version.
To verify the JVM version, select View > Java Console.•
1 If you plan to use DFM with the HPOV-NetView Adapter and HP OpenView is installed on an NTFS partition on a Windows NT system, you will have to create an account that has full NTFS privileges. This is described in Appendix A, "Configuring HP OpenView for Full NTFS Privileges."
Client Requirements
The minimum system requirements for the CiscoWorks2000 client are shown in Table 1-5.
Supported NMS Environments for Device Import
DFM can synchronize the DFM inventory with a list of devices managed by these versions of Essentials:
•
•
If the import causes the DFM system to exceed its device limit, the Essentials list will be truncated. (Refer to the "Server Requirements and Recommendations" section.)
Synchronizing is done automatically if you install DFM on the same host that is running Essentials, or if you locally install Essentials later. If Essentials is running on a remote host, you must install the RME Adapter on the remote Essentials host as described in the "Installing or Upgrading the RME Adapter on a Remote Host" section.
Supported NMS Integration
DFM includes several adapters that collect inventory information, gather network event information, and send event notifications to the domain manager or other SNMP recipients, such as NMSs. The adapters are automatically installed when you install DFM.
NMS integration adapters include:
•
•
–
–
Installing this adapter on remote machines is described in the "Installing or Upgrading the HPOV-NetView Adapter on a Remote Host" section.
Note
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.
Supported Devices
Device adapter packages for all supported devices are installed when you install DFM. Information about devices installed with DFM can be found at:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dev_sup/index.htm
You can download device packages for new devices from Cisco.com and find information about all supported devices from Cisco.com at:
www.cisco.com
To find out which packages are installed on your CiscoWorks2000 Server, select Server Configuration > About the Server > Applications and Versions.
