Table Of Contents
Prerequisites
Product Overview
Installation and Upgrade Roadmap
Installation Paths
Server Requirements and Recommendations
Solaris Patches
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 Solaris system. It includes:
•
Product Overview
•
Installation and Upgrade Roadmap
•
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
|
CiscoWorks2000 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 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 on page 2-26.
|
Device Fault Manager RME Adapter
|
Only 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 Essentials inventory to a local DFM. For information on how to configure and start this adapter, refer to Table 2-4 on page 2-26.
|
Installation and Upgrade Roadmap
Table 1-2 provides an overview of DFM installation scenarios.
Table 1-2 DFM Installation Roadmap
If you want to use...
|
And...
|
You must...
|
For instructions, refer to...
|
CiscoWorks2000 Device Fault Manager as a standalone
|
N/A
|
Install CiscoWorks2000 Device Fault Manager
|
Performing a New Installation, page 2-2
|
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)
|
Performing a New Installation, page 2-2
|
Essentials is not installed on the DFM host
|
Install RME Adapter on the remote Essentials host
|
Installing or Upgrading the RME Adapter on a Remote Host, page 2-32
|
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)
|
Performing a New Installation, page 2-2
|
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, page 2-27
|
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, page 2-29
|
Device Fault Manager with another NMS
|
You want DFM to both receive traps from and forward traps (including correlation traps) to the NMS
|
1. Install Device Fault Manager
|
Performing a New Installation, page 2-2
|
2. Enable devices to send traps to DFM
|
Enabling Devices to Send Traps to DFM, page 3-2
|
3. Enable DFM to send traps to NMSs
|
Enabling DFM to Send Traps to NMSs, page 3-2
|
Table 1-3 provides an overview of upgrade scenarios.
Table 1-3 DFM Upgrade Roadmap
If you want to upgrade to...
|
And...
|
You must...
|
For instructions, refer to...
|
CiscoWorks2000 Device Fault Manager 1.1 as a standalone
|
CiscoWorks2000 Device Fault Manager 1.0 is installed
|
1. Install CD One, 4th Edition
|
Installing and Setting Up CD One on Solaris
|
2. Upgrade to Device Fault Manager 1.1
|
Upgrading from Device Fault Manager 1.0, page 2-8
|
CiscoWorks2000 Device Fault Manager 1.1
|
CiscoWorks2000 Device Fault Manager 1.0 is installed, along with other applications
|
1. Determine if all installed applications are supported by CD One, 4th Edition, and upgrade them, if required
|
Appropriate documentation
|
2. Install CD One, 4th Edition
|
Installing and Setting Up CD One on Solaris
|
3. Upgrade to Device Fault Manager 1.1
|
Upgrading from Device Fault Manager 1.0, page 2-8
|
4. Upgrade any remote adapters to Device Fault Manager 1.1
|
Installing and Upgrading Adapters, page 2-23
|
CiscoWorks2000 Device Fault Manager 1.1
|
You also want to upgrade your local/remote operating system
|
1. Upgrade your local/remote operating system and install any required patches
|
Your vendor documentation
|
2. Determine if all installed local/remote applications are supported by CD One, 4th Edition, and upgrade them, if required
|
Appropriate documentation
|
3. Install CD One, 4th Edition locally and remotely
|
Installing and Setting Up CD One on Solaris
|
4. Upgrade to Device Fault Manager 1.1
|
Upgrading from Device Fault Manager 1.0, page 2-8
|
5. Upgrade any remote adapters to Device Fault Manager 1.1
|
Installing and Upgrading Adapters, page 2-23
|
Installation Paths
You can install DFM on:
•
CD One, 4th Edition (as a "standalone" DFM)
•
Resource Manager Essentials 3.3
To support integration with remote HP OpenView and NetView, and device list synchronization with remote Essentials 3.x systems, you can also install individual adapters on remote NMS machines. For more information, refer to the "Installing and Upgrading Adapters" section on page 2-23.
Server Requirements and Recommendations
The server system requirements for installing DFM are shown in Table 1-4. These requirements apply when installing DFM on:
•
CD One, 4th Edition
•
Resource Manager Essentials 3.3, when the Availability application is not running
Table 1-4 also provides configuration recommendations for running DFM with CD One or Essentials. 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 the import causes the DFM system to exceed its device limit, the Essentials 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 Device Fault Manager User Guide, available from online help):
# NMSROOT/objects/smarts/bin/sm_tpmgr --server=DFM --sizes
•
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 for the appropriate bundle for additional information.
Table 1-4 Server System Requirements and Recommendations
Requirement Type
|
Required or Recommended Configuration
|
System Hardware
|
• Sparc Ultra 10
• 17-inch 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.
|
System Software
|
Solaris 2.6 or Solaris 2.7
|
Additional Software (Optional)
|
Netscape Navigator 4.75 (if you are using the CiscoWorks2000 desktop on the server system)
|
Solaris Patches
Table 1-5 lists the required and recommended patches for Solaris 2.6 and Solaris 2.7.
Table 1-5 Solaris Patches
Operating System
|
Required
|
Recommended
|
Solaris 2.6
|
• 105181-19
• 105210-27
• 105490-07 (or 107733)
• 105568-16
• 105591-06
• 105633-36 (Asian only)
• 106040-13 (Japanese only)
• 106409-01 (traditional Chinese only)
• 108091-03 (ISO 8859-1 and 8859-15 only)
|
• 105284-31
• 105669-10
|
Solaris 2.7
|
• 106327-05
• 106980-10
• 107081-11
• 107636-03
• 108376-03 (Asian only)
|
|
Use the showrev -p command to verify that these patches have been applied.
Client Requirements
The minimum system requirements for the CiscoWorks2000 client are shown in Table 1-6.
Table 1-6 Client System Requirements Summary
Requirement Type
|
Minimum Requirements
|
System Hardware and Software
|
• Client system:
Note Use Windows clients for optimal performance.
– IBM PC-compatible computer with 450 MHz Pentium processor running Windows NT 4.0, Windows 95, Windows 98, or Windows 2000.
– SPARC Ultra 10 running Solaris 2.6 or Solaris 2.7.
– IBM RS/6000 workstation running AIX 4.33.
– HP900 workstation running HP-UX 11.0.
• Color monitor with video card set to 256 colors.
|
Memory (RAM)
|
128 MB
|
Browser
|
• Netscape Navigator 4.75. (Windows NT 4.0 Workstation and Server, Windows 98, Windows 2000 Professional and Server, Solaris 2.6, Solaris 2.7, AIX 4.33, HP-UX 11.0)
• Microsoft Internet Explorer 5.5, Service Pack 1. Java Virtual Machine (JVM) version 5.0.0.3167 or current shipping version (Windows NT 4.0 Workstation and Server, Windows 98, Windows 2000 Professional and Server). To verify the JVM version, select View > Java Console.
|
Supported NMS Environments for Device Import
DFM can synchronize the DFM inventory with a list of devices managed by these versions of Essentials:
•
Local versions of Resource Manager Essentials 3.3
•
Remote versions of Resource Manager Essentials 3.x
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 on page 2-32.
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 on page 3-2.)
•
HPOV-NetView Adapter, which forwards traps (sent from managed devices to the NMS) to DFM from remote or local hosts running:
–
HP OpenView 5.x or 6.x
–
NetView 5.x
Note
NetView must be installed on the same drive as DFM (for local integration) or on the save drive as the HPOV-NetView Adapter (for remote integration).
Installing this adapter on remote machines is described in the "Installing or Upgrading the HPOV-NetView Adapter on a Remote Host" section on page 2-27.
Note
To use the HPOV-NetView Adapter with a local version of HP OpenView or NetView, make sure that HP OpenView or NetView are 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 on page 3-3.
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.