Table Of Contents
Installation and Upgrade Paths
Server Requirements and Recommendations
Supported NMS Environments for Device Import
Number of Ports/Interfaces that DFM Supports
Prerequisites
This chapter describes the prerequisites for installing Device Fault Manager (DFM) on a Windows system. It includes:
•
Installation and Upgrade Paths
•
•
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. Table 1-1 describes installation options that are displayed under different circumstances and lists the DFM components that can be installed in each case.
Table 1-1 DFM Installation Options and Their Components
Device Fault Manager 2.0
This option is available when DFM 2.0 has not been installed on the local system. It is normally chosen to install the entire DFM product on the local system, including:
•
•
Device Fault Manager HPOV-NetView adapters
This option is available whether or not DFM 2.0 is already installed on the local system. However, when this option is selected, it will install only the HPOV-NetView adapters, not the entire DFM product.
This option is normally chosen to install the adapters 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 these adapters, see Installing and Upgrading HPOV-NetView Adapters.
Installation and Upgrade Paths
This section outlines the steps for installing and upgrading DFM 2.0.
Installation Paths
You must install DFM 2.0 on a system with CiscoWorks Common Services 3.0. You can install DFM 2.0 on a system with:
•
•
–
Note
–
Before you install DFM, you should determine whether you will install DFM as a standalone or with other products. For more information, see Server Requirements and Recommendations.
Whether DFM is installed as a standalone or not, you can integrate it with:
•
•
Table 1-2 lists the basic installation sequence.
Table 1-2 Installation Roadmap
Step 1
Install Common Services.
Installation and Setup Guide for Common Services (Includes CiscoView) on Windows
Step 2
If you want to install DFM on a system with an NMS (HP OpenView or NetView), install the NMS.
Note
•
•
Step 3
If you want to install DFM on a system with the contents of a Cisco product bundle:
a.
b.
Quick Start Guide for LAN Management Solution 2.5
Step 4
Install DFM.
Note
Step 5
If HP OpenView or NetView is installed on a remote system and you want DFM to receive SNMP traps from one of them, install or upgrade the HPOV-NetView adapters on the remote system.
•
Step 6
If HP OpenView or NetView is installed on the same system as DFM and uses the standard UDP trap port (162), you must configure DFM SNMP trap receiving to use a different UDP port, such as port 9000.
Step 7
If you want a standalone DFM to access the DCR on a remote system (to share the device list across applications from a Cisco product bundle):
a.
b.
•
Upgrade Paths
You must upgrade DFM 2.0 on a system with Common Services 3.0. You can perform a local in-place upgrade from DFM 1.2.x or a remote upgrade. (For more information, see Upgrading to DFM 2.0.)
After the upgrade, whether DFM 2.0 is installed as a standalone or not, you can integrate it with:
•
•
Table 1-3 lists the basic upgrade sequence.
Table 1-3 Upgrade Roadmap
Step 1
Upgrade Common Services.
Note
Installation and Setup Guide for Common Services (Includes CiscoView) on Windows
Step 2
If you want to upgrade DFM on a system with an NMS (HP OpenView or NetView), do one of the following:
•
•
Note
•
•
Step 3
If you want to upgrade DFM on a system with the contents of a Cisco product bundle:
a.
b.
Quick Start Guide for LAN Management Solution 2.5 (Maintenance Kit)
Step 4
Upgrade DFM.
Note
Note
Step 5
If HP OpenView or NetView is installed on a remote system and you want DFM to receive SNMP traps from one of them, install or upgrade the HPOV-NetView adapters on the remote system.
•
Step 6
If HP OpenView or NetView is installed on the same system as DFM and uses the standard UDP trap port (162), you must configure DFM SNMP trap receiving to use a different UDP port, such as port 9000.
Step 7
If you want a standalone DFM to access the DCR on a remote system (to share the device list across applications from a Cisco product bundle):
a.
b.
•
Server Requirements and Recommendations
This section describes the server requirements and recommendations for Common Services and DFM 2.0.
Note
Minimum Server Requirements
The minimum system requirements for a CiscoWorks Server running Common Services 3.0 and Device Fault Manager 2.0 are shown in Table 1-4.
Table 1-4 Server System Minimum Requirements
System hardware
•
•
•
System software
•
•
–
–
Note
Note
Available memory (RAM)
2 GB.
Available drive space
•
•
Note
Additional required software
Common Services must be installed before you install DFM. For installation instructions, see Installation and Setup Guide for Common Services (Includes CiscoView) on Windows.
Additional optional software
To use the desktop on the server system, you need one of the following browsers:
•
•
•
1 To verify the version of ODBC Driver Manager, from the Windows desktop, select Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC). Select the About tab. If necessary, install Microsoft Data Access Component (MDAC) 2.5 or later.
Server Recommendations
To select or configure a server system that best meets your needs, consider the number of ports and interfaces being managed. (For the maximum number of ports and interfaces, see Number of Ports/Interfaces that DFM Supports.)
Note
To find out how many trunk and access ports and interfaces are currently imported into DFM, use the sm_tpmgr command:
# NMSROOT/objects/smarts/bin/sm_tpmgr --server=DFM --sizesFor ports, locate the line that is similar to the following:
Number of Ports: 761 [92/92]In this example, 761 represents the number of discovered ports, out of which 92 are managed. Unless you have reconfigured DFM to manage access ports, you can assume these 92 ports are trunk ports.
For interfaces, locate the line that is similar to the following:
Number of Interfaces: 351 [322/280]In this example, 351 represents the number of discovered interfaces, out of which 322 are managed.
Client Requirements
The minimum system requirements for the CiscoWorks client are shown in Table 1-5.
Before you access DFM from a client system, you must configure the system. For more information about client system requirements and configuring clients, see Installation and Setup Guide for Common Services (Includes CiscoView) on Windows.
Table 1-5 Client System Requirements Summary
System hardware and software
•
–
–
DFM supports only US-English and Japanese versions of Windows Operating System (OS) and Solaris OS. Set the default locale to US-English for the US-English OS, and Japanese for the Japanese OS.
•
Available memory (RAM)
512 MB.
Available disk apace
1 GB swap space.
Note
Browser
One of these browsers:
•
–
To verify the JVM:
From Internet Explorer, select View > Java Console.
From Netscape Navigator, select Tools > Server > Java Console.–
–
•
–
–
For Solaris, use Netscape Navigator downloaded from the Sun website only.
1 To verify the existing service pack, from the Start menu, select Run and enter winver.
Supported NMS Environments for Device Import
DFM device inventory is taken from the Common Services Device and Credentials Repository (DCR). DCR is a common repository of devices, their attributes, and credentials. It is the central place where users add or import new devices.
DCR enables you to share devices lists with other applications as follows:
•
–
–
–
•
By default, DFM is configured to automatically synchronize its device list with DCR. If the synchronization causes the DFM system to exceed its limit, the device and credentials list will be truncated. (See Number of Ports/Interfaces that DFM Supports.)
Alternatively, you can configure DFM to allow only manual selection of devices in DCR that you want DFM to manage. When you do so, DFM displays a list of devices in DCR, but not in DFM, for you to choose from.
The following scenarios illustrate only a few possible ways to configure DFM and DCR to share device lists and credentials.
Scenario One
In this scenario, DFM and RME are installed on separate systems. On the RME system, DCR is configured as a server (master). On the DFM system, DCR is configured as a client (slave) of the DCR server on the RME system. The DFM system is configured for manual selection devices from DCR.
In this scenario, devices imported to the DCR server on the RME system are also added to the DCR client on the DFM system. Since DFM is not configured to automatically synchronize with DCR, the devices are not added to the DFM inventory. However, these devices are available in DCR and if DFM users want to manage them, they can do so by selecting them.
Scenario Two
In this scenario, DFM and an NMS are installed on the same system. DCR is configured to run bulk import regularly, importing devices from a local NMS. DFM is configured to synchronize with DCR.
In this scenario, DCR regularly imports devices from the local NMS, updating DCR with any new devices. Since DFM is configured to automatically synchronize with DCR, the devices are also added to the DFM inventory.
Note
Supported NMS Integration
DFM supports integration with network management systems (NMSs) as follows:
•
–
–
•
–
–
For more information on pass-through and processed traps, see the appendix "Processed and Pass-through Traps, and Other Unidentified Traps and Events" in User Guide for Device Fault Manager.
•
–
–
For remote machines without CiscoWorks, the remote adapters are supported on:
–
–
–
Installing these adapters on remote machines is described in Installing and Upgrading HPOV-NetView Adapters.
Note
If the standard User Datagram Protocol (UDP) trap port (162) is being used by another NMS, you must configure DFM SNMP trap receiving to use a different UDP port, such as port 9000. See Configuring SNMP Trap Receiving and Forwarding.
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
For information on how device support compares between DFM 1.2.x and DFM 2.0, see Release Notes for Device Fault Manager 2.0 at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dfm20
/rel_note/index.htm.As additional device adapter packages become available, you can download the IDUs that contain them, by logging into Cisco.com at:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-DFM
Number of Ports/Interfaces that DFM Supports
DFM supports configurations of up to 45,000 ports/interfaces, of which 6,750 (or 15%) are managed. This support was tested with an average of 30 ports/interfaces per device.
If you have an unrestricted license, DFM stops adding devices to its managed inventory when the supported number of ports/interfaces on the devices is reached.
If you have a restricted license, however, DFM stops adding devices to its managed inventory after the number of devices in managed inventory equals or surpasses the number of devices specified by the license. DFM displays licensing reminders as the number of devices nears the limit; see Restricted Version: Device Limit Exceeded.
