Table Of Contents
Prerequisites
Product Overview
Installation and Upgrade Roadmaps
Roadmap for a New DFM Installation
Roadmap for Upgrading to DFM 1.2
Roadmap for Upgrading to DFM 1.2 Updated for Common Services Version 2.2
Installation Paths
Server Requirements and Recommendations
Client Requirements
Supported NMS Environments for Device Import
Supported NMS Integration
Supported Devices
Prerequisites
This chapter describes the prerequisites for installing Device Fault Manager (DFM) on a Windows system. It includes:
•
Product Overview
•
Installation and Upgrade Roadmaps
•
Installation Paths
•
Server Requirements and Recommendations
•
Client Requirements
•
Supported NMS Environments for Device Import
•
Supported NMS Integration
•
Supported Devices
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
Installation Option
|
Installation Option Contents
|
CiscoWorks Device Fault Manager
|
DFM; 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 DeviceUpdate (IDU).
|
Device Fault Manager HPOV-NetView Adapter
|
Only the HPOV-NetView Adapter. (This option is only displayed if HP OpenView or NetView are installed.) 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. You can also install remote adapters using DFM 1.2 Patch/IDU 1.2.7 or later.
|
Device Fault Manager RME Adapter
|
Only the RME Adapter. (This option is only displayed if Essentials is installed.) 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. You can also install remote adapters using DFM 1.2 Patch/IDU 1.2.7 or later.
|
Installation and Upgrade Roadmaps
This section contains installation and upgrade roadmaps for the following scenarios:
•
Roadmap for a New DFM Installation
•
Roadmap for Upgrading to DFM 1.2
•
Roadmap for Upgrading to DFM 1.2 Updated for Common Services Version 2.2
Roadmap for a New DFM Installation
Table 1-2 provides an overview of how to perform a new DFM installation.
Roadmap for Upgrading to DFM 1.2
Table 1-3 provides an overview of how to upgrade to DFM 1.2.
Note
If you are upgrading to DFM 1.2 Updated for Common Services Version 2.2, refer to "Roadmap for Upgrading to DFM 1.2 Updated for Common Services Version 2.2" section.
Table 1-3 DFM 1.2 Upgrade Roadmap
If you want to upgrade to...
|
And...
|
You must...
|
For instructions, refer to...
|
DFM 1.2 as a standalone
|
DFM 1.1 (with or without any DFM 1.1 IDSs) is installed
|
1. Install CD One, 5th Edition
|
Installation and Setup Guide for CD One on Windows
|
2. Upgrade to DFM 1.2
|
Upgrading DFM 1.1 to DFM 1.2
|
DFM 1.2
|
DFM 1.1 (with or without any DFM 1.1 IDSs) is installed, along with other applications
|
1. Determine if all installed applications are supported by CD One, 5th Edition, and upgrade them, if required
|
Appropriate documentation
|
2. Install CD One, 5th Edition
|
Installation and Setup Guide for CD One on Windows
|
3. Upgrade to DFM 1.2
|
Upgrading DFM 1.1 to DFM 1.2
|
4. Upgrade any remote adapters to DFM 1.2
|
Installing and Upgrading Adapters
|
DFM 1.2
|
You also want to upgrade your local operating system
|
1. Upgrade your local operating system and install any required patches
|
Your vendor documentation
|
2. Determine if all installed local applications are supported by CD One, 5th Edition, and upgrade them, if required
|
Appropriate documentation
|
3. Install CD One, 5th Edition locally
|
Installation and Setup Guide for CD One on Windows
|
4. Upgrade to DFM 1.2
|
Upgrading DFM 1.1 to DFM 1.2
|
5. Upgrade any remote adapters to DFM 1.2
|
Installing and Upgrading Adapters
|
DFM 1.2
|
You also want to upgrade your remote operating system from a local operating system that has not been upgraded
|
1. Upgrade your remote operating system and instal any required patches
|
Your vendor documentation
|
2. Determine if all installed remote applications are supported by CD One, 5th Edition, and upgrade them if required
|
Appropriate Documentation
|
3. Install CD One, 5th Edition remotely
|
Installation and Setup Guide for CD One on Windows
|
4. Export local CD One, 4th Edition information to the upgraded CD One, 5th Edition remote host
|
Installation and Setup Guide for CD One on Windows
|
5. Install DFM 1.2 remotely
|
Performing a New Installation of DFM 1.2
|
6. Export DFM 1.1 information to the upgraded DFM 1.2 remote host
|
Exporting Local DFM Information to an Upgraded Remote DFM Host
|
Roadmap for Upgrading to DFM 1.2 Updated for Common Services Version 2.2
Table 1-4 provides an overview of how to perform an upgrade to DFM 1.2 Updated for Common Services Version 2.2.
Table 1-4 DFM 1.2 Updated for Common Services Version 2.2 Upgrade Roadmap
If you want to upgrade to...
|
And...
|
You must...
|
For instructions, refer to...
|
DFM 1.2 Updated for Common Services Version 2.2 as a standalone
|
DFM 1.1 (with or without any DFM 1.1 IDSs) is installed
|
1. Install CD One, 5th Edition or Common Services 2.2
|
Installation and Setup Guide for CD One on Windows or Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows
|
2. Upgrade to DFM 1.2 Updated for Common Services Version 2.2
|
Upgrading DFM 1.1 to DFM 1.2 Updated for Common Services Version 2.2
|
DFM 1.2 Updated for Common Services Version 2.2
|
DFM 1.1 (with or without any DFM 1.1 IDSs) is installed, along with other applications
|
1. Determine if all installed applications are supported by CD One, 5th Edition or Common Services 2.2, and upgrade them, if required
|
Appropriate documentation
|
2. Install CD One, 5th Edition or Common Services 2.2
|
Installation and Setup Guide for CD One on Windows or Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows
|
3. Upgrade to DFM 1.2 Updated for Common Services Version 2.2
|
Upgrading DFM 1.1 to DFM 1.2 Updated for Common Services Version 2.2
|
4. Upgrade any remote adapters to DFM 1.2 Updated for Common Services Version 2.2
|
Installing and Upgrading Adapters
|
DFM 1.2 Updated for Common Services Version 2.2 as a standalone
|
DFM 1.2 (with or without IDU 1.2.1 or Patch 1.2.2) is installed1 ,2
|
1. If desired, install Common Services 2.2
|
Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows
|
2. Upgrade to 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
|
DFM 1.2 Updated for Common Services Version 2.2
|
DFM 1.2 (with or without IDU 1.2.1 or Patch 1.2.2) is installed, along with other applications1,2
|
1. Determine if all installed applications are supported by Common Services 2.2, and upgrade them, if required
|
Appropriate documentation
|
2. If desired, install Common Services 2.2
|
Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows
|
3. Upgrade to 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
|
DFM 1.2 Updated for Common Services Version 2.2
|
You also want to upgrade your local operating system1,2
|
1. Upgrade your local operating system and install any required patches
|
Your vendor documentation
|
2. Determine if all installed local applications are supported by CD One, 5th Edition or Common Services 2.2, and upgrade them, if required
|
Appropriate documentation
|
3. Install CD One, 5th Edition or Common Services 2.2 locally
|
Installation and Setup Guide for CD One on Windows or Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows
|
4. Install DFM 1.2 Updated for Common Services Version 2.2
|
Upgrading DFM 1.1 to DFM 1.2 Updated for Common Services Version 2.2 or Upgrading DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2
|
5. If you are upgrading from DFM 1.1, upgrade any remote adapters to DFM 1.2 Updated for Common Services Version 2.2
|
Installing and Upgrading Adapters
|
DFM 1.2 Updated for Common Services Version 2.2
|
You also want to upgrade your remote operating system from a local operating system that has not been upgraded1,2
|
1. Upgrade your remote operating system and install any required patches
|
Your vendor documentation
|
2. Determine if all installed remote applications are supported by CD One, 5th Edition or Common Services 2.2, and upgrade them if required.
|
Appropriate documentation
|
3. Install CD One, 5th Edition or Common Services 2.2 remotely
|
Installation and Setup Guide for CD One on Windows or Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows
|
4. Export local CD One, 4th Edition information to the upgraded CD One, 5th Edition or Common Services 2.2 remote host
|
Installation and Setup Guide for CD One on Windows or Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows
|
5. Install DFM 1.2 Updated for Common Services Version 2.2 remotely
|
Performing a New Installation
|
DFM 1.2 Updated for Common Services Version 2.2 (continued)
|
You also want to upgrade your remote operating system from a local operating system that has not been upgraded
|
6. Export DFM information to the upgraded DFM 1.2 Updated for Common Services Version 2.2 remote host
|
Exporting Local DFM Information to an Upgraded Remote DFM Host
|
Installation Paths
You can install DFM 1.2 on:
•
CD One, 5th Edition (as a standalone DFM)
•
Resource Manager Essentials 3.4
You can install DFM 1.2 Updated for Common Services Version 2.2 on:
•
CD One, 5th Edition (as a standalone DFM)
•
Common Services 2.2 (as a standalone DFM)
•
Resource Manager Essentials 3.5
To support integration with remote HP OpenView and NetView, and to support device list synchronization with remote Essentials 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 1.2 are shown in Table 1-5. These requirements apply when installing DFM on:
•
CD One, 5th Edition
•
Resource Manager Essentials 3.4 when the Availability application is not running
The server system requirements for installing DFM 1.2 Updated for Common Services Version 2.2 are shown in Table 1-6. These requirements apply when installing DFM on:
•
CD One, 5th Edition
•
Common Services 2.2
•
Resource Manager Essentials 3.5 when the Availability application is not running
Table 1-5 and Table 1-6 also provide configuration recommendations when running DFM with CD One, Essentials, or Common Services. These major considerations can help you select or configure a server system that best meets your needs:
•
The number of ports being managed. Configurations of over 30,000 ports (of which 15% are trunk ports) are not supported.
Note
If you use the RME Adapter to synchronize the DFM inventory with a list of Essentials devices, and the synchronization causes DFM to exceed this limit, the Essentials device list will be truncated. (Refer to the "Supported NMS Environments for Device Import" section.)
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 User Guide for Device Fault Manager, available from online help):
# NMSROOT\objects\smarts\bin\sm_tpmgr.exe --server=DFM --sizes
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.
•
Whether you plan to use DFM with the Essentials Availability application. (If you plan to use Availability, you must run Essentials and DFM on different machines.)
Note
If you are installing DFM with the contents of a Cisco product bundle, the server requirements may be different. See the Read Me First document or the quick start guide for the appropriate bundle for additional information.
Table 1-5 DFM 1.2 Server System Requirements and Recommendations
Requirement Type
|
Required or Recommended Configuration
|
System Hardware
|
• IBM PC-compatible computer with 450 MHz Intel Pentium processor
• Color monitor
• CD-ROM drive
|
Memory (RAM)
|
• 512 MB
|
Available Drive Space
|
• 4 GB
• Swap space equal to double the amount of memory (RAM). For example, if your system has 512 MB of RAM, you need 1024 MB of swap space.
• NTFS file system required for secure operation.
|
System Software
|
• Windows 2000 Professional and Server with Service Pack 2
Note DFM supports only US-English and Japanese versions of Windows operating systems. DFM does not support any other language versions. Set the default locale to US-English or Japanese.
|
Additional Software (Optional)
|
One of the following browsers (if you are using the CiscoWorks desktop on the server system):
• Microsoft Internet Explorer 5.5 with Service Pack 2, or Microsoft Internet Explorer 6.0
• Netscape Navigator 4.77, 4.78, or 4.79
|
Table 1-6 DFM 1.2 Updated for Common Services Version 2.2 Server System Requirements and Recommendations
Requirement Type
|
Required or Recommended Configuration for CD One
|
Required or Recommended Configuration for Common Services 2.2 and Essentials 3.5
|
System Hardware
|
• IBM PC-compatible computer with 450 MHz Intel Pentium processor
• Color monitor
• CD-ROM drive
|
• IBM PC-compatible computer with 500 MHz Intel Pentium processor
• Color monitor
• CD-ROM drive
|
Memory (RAM)
|
• 512 MB
|
512 MB
|
Available Drive Space1
|
• 4 GB
• Swap space equal to double the amount of memory (RAM). For example, if your system has 512 MB of RAM, you need 1024 MB of swap space.
• NTFS file system required for secure operation.
|
• 4 GB
• Paging file space equal to double the amount of memory (RAM). For example, if your system has 256 MB of RAM, you need 512 MB of page file.
• NTFS file system required for secure operation.
• At least 16 MB in Windows temporary directory (%TEMP%).
|
System Software2 ,3
|
• Windows 2000 Professional and Server with Service Pack 2
|
• ODBC Driver Manager 3.5.10.
• Windows 2000 Professional; Windows 2000 Server with Service Pack 3; Windows 2000 with Service Pack 44
• Windows Advanced Server without enabling terminal services.
|
Additional Software (Optional)
Browsers
|
• Microsoft Internet Explorer 5.5 with Service Pack 2, or Microsoft Internet Explorer 6.0.
|
• Microsoft Internet Explorer 6.0 (version 6.0.2600.0000); Internet Explorer 6.0 with Service Pack 1 (version 6.0.2800.1106); Java Virtual Machine (JVM) 5.1.3182; Java plug-in version 1.3.1; Java plug-in version 1.4.1_024
To verify the JVM, select View > Java Console from Internet Explorer.
|
• Netscape Navigator 4.77, 4.78, or 4.79.
|
• Netscape Navigator 4.78; Netscape Navigator 4.79; Netscape Navigator 7.14
|

Note
Installation will continue with a warning message on Windows Advanced Server if terminal services are enabled in remote admin mode, but will abort when terminal services are enabled in application mode.
Do not use nonstandard java options through the _JAVA_OPTIONS environment variable.
Client Requirements
The minimum system requirements for the CiscoWorks client are shown in Table 1-7.
Table 1-7 Client System Requirements Summary
Requirement Type
|
Minimum Requirements for CD One
|
Minimum Requirements for Common Services 2.2
|
System Hardware and Software
|
Client system: Any of the following with video cards set to 256 colors:
Tip  Use Windows clients for optimal performance.
• IBM PC-compatible computer with 450 MHz Pentium processor running:
– Windows NT 4.0 Workstation and Server with Service Pack 6a.
– Windows 98.
– Windows 2000 Professional and Server with Service Pack 2.
• SPARC Ultra 10 running Solaris 2.7 or Solaris 2.8.
• IBM RS/6000 workstation running AIX 4.3.3.
• HP900 workstation running HP-UX 11.0.
|
Client system: Any of the following with video card set to 256 colors:
Tip  Use Windows clients for optimal performance.
• IBM PC-compatible computer with at least a 300 MHz Pentium processor running:
– Windows 2000 with Service Pack 3 (Professional and Server).
– Windows 2000 with Service Pack 41 .
– Windows XP with Service Pack 1.
– Windows XP with ServicePack 1a1.
DFM supports English and Japanese Windows OS as clients.
• SPARC Ultra 10 running Solaris 2.7 or 2.8.
|
Memory (RAM)
|
128 MB
|
256 MB
|
Browser
|
On clients running Windows NT 4.0 Workstation and Server with Service Pack 6a, Windows 98, Windows 2000 Professional and Server with Service Pack 2:
• Microsoft Internet Explorer 5.5 with Service Pack 2, or Microsoft Internet Explorer 6.0.
• Java Virtual Machine (JVM) version 5.0.0.3182 or current shipping version.
To verify the JVM version, select View > Java Console.
• Netscape Navigator 4.77, Netscape Navigator 4.78, or Netscape Navigator 4.79.
On Solaris clients (Solaris 2.7 and 2.8):
• Netscape Navigator 4.76.
On AIX 4.3.3, HP-UX 11.0 clients:
• Netscape Navigator 4.77, Netscape Navigator 4.78, or Netscape Navigator 4.79.
|
On clients running Windows and Windows XP:
• Microsoft Internet Explorer 6.0 (version 6.0.2600.0000), or Internet Explorer 6.0 with Service Pack 1 (version 6.0.2800.1106).
• Java Virtual Machine (JVM) 5.1.3182, Java plug-in version 1.3.1, or Java plug-in version 1.4.1_021.
To verify the JVM version , select View > Java Console from Internet Explorer and Tools > Server > Java Console from Netscape Navigator.
• Netscape Navigator 4.78, Netscape Navigator 4.79, or Netscape Navigator 7.11.
On Solaris clients (Solaris 2.7 and 2.8):
• Netscape Navigator 4.76, or Netscape Navigator 7.01.
Caution  Use Netscape Navigator downloaded from the Sun Microsystems website only.
|
Supported NMS Environments for Device Import
DFM can synchronize the DFM inventory with a list of devices managed by local or remote versions of Resource Manager Essentials 3.5. If the import causes the DFM system to exceed its device limit, the Essentials list will be truncated. (Refer to "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:
•
SNMP Trap Adapter, which listens on a user-specified port for traps sent to DFM from managed devices, and forwards the traps to specified destinations. (Configuring this adapter is described in the "Enabling DFM to Send Traps to NMSs" section.)
•
HPOV-NetView Adapter, which forwards traps (sent from managed devices to the NMS) to DFM from remote or local hosts running:
–
HP OpenView 6.2
–
NetView 6.01
–
NetView 7.1 (supported only on DFM 1.2 Updated for Common Services Version 2.2 when it is installed on CiscoWorks Common Services 2.2)
For remote machines without CiscoWorks the remote HPOV-NetView adapter is supported on:
•
For DFM 1.2:
–
Solaris 2.7 or 2.8
–
Windows 2000 Professional or Server with Service Pack 2
•
For DFM 1.2 Updated for Common Services Version 2.2:
–
Solaris 2.7 or 2.8
–
Windows 2000 Professional or Server with Service Pack 3 or higher; Windows Advanced Server
Installing this adapter on remote machines is described in the "Installing or Upgrading the HPOV-NetView Adapter on a Remote Host" section.
Note
To use the HPOV-NetView Adapter with a local version of HP OpenView or NetView, make sure that HP OpenView or NetView is installed before you install DFM.
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/en/US/products/sw/cscowork/ps2421/products_device_support_tables_list.html
You can download device packages for new devices from Cisco.com and find information about all supported devices by logging into Cisco.com at
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-dfm.
Device packages are released cumulatively; that is, new device packages contain the contents of any previous packages.
To determine which packages are installed on your CiscoWorks Server, select Server Configuration > About the Server > Applications and Versions.
You can also obtain any published patches from the download site.