Installation and Setup Guide for Device Fault Manager 2.0.6 on Solaris (With LMS 2.6) - Prerequisites [CiscoWorks Device Fault Manager]

Table Of Contents

Prerequisites

Product Overview

Installation, Upgrade, and Migration Paths

Installation Paths

Upgrade/Migration Paths

Server Requirements and Recommendations

Minimum Server Requirements

Server Recommendations

Solaris Patches

Client Requirements

Supported NMS Environments for Device Import

Supported NMS Integration

Supported Devices

Number of Ports/Interfaces that DFM Supports

Prerequisites

This chapter describes the prerequisites for installing Device Fault Manager (DFM) on a Solaris system. It includes:

•Product Overview

•Installation, Upgrade, and Migration 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. 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

Installation Option

Installation Option Components

Device Fault Manager 2.0.3

This option installs the entire DFM product on the local system, including:

•DFM—Provides the graphical user interface (GUI) and back-end processes for DFM.

•HPOV-NetView adapters for integrating DFM with HP OpenView and NetView, if already installed on the same box.

LMS 2.6 Update

A single installable bundle update containing the incremental versions of LMS applications, including Device Fault Manager 2.0.6.

Device Fault Manager HPOV- NetView adapters

This option installs 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, Upgrade, and Migration Paths

This section outlines the steps for installing, upgrading, and migrating to DFM 2.0.6.

Installation Paths

You must install DFM 2.0.6 on a system with Device Fault Manager 2.0.3 and CiscoWorks Common Services 3.0.3. You can install DFM 2.0.6 on a system with:

•CiscoWorks Common Services only (as a "standalone" DFM)

•Common Services and any of the following:

–Other CiscoWorks applications that are included in the LAN Management Solution 2.5.1 product.

Note If you are installing DFM with contents of the LAN Management Solution, check the installation order as described in the quick start guide (see Related Documentation).

–Another NMS, such as NetView or HP OpenView (see Supported NMS Integration).

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.

Table 1-2 lists the basic installation sequence.

Table 1-2 Installation Roadmap

Description

References

Step 1

Install Device Fault Manager 2.0.3 and Common Services 3.0.3.

Installation and Setup Guide for Device Fault Manager 2.0.3 on Solaris

Installation and Setup Guide for Common Services 3.0.3 (Includes CiscoView) on Solaris

Step 2

If you want to install DFM on a system with an NMS (HP OpenView or NetView), install the NMS.

Note If the desired NMS is not installed before DFM, you will have to reinstall DFM later.

•For supported versions of NMSs, see Supported NMS Integration

•For installation instructions, see vendor documentation

Step 3

If you want to install DFM on a system with the contents of the LAN Management Solution:

a. Check the quick start guide for the order of installation.

b. Install any products that should be installed before DFM.

Quick Start Guide for LAN Management Solution 2.5.1

Step 4

Install Device Fault Manager 2.0.6.

Installing LMS 2.6

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 the DFM HPOV-NetView adapters on the remote system.

Note Be sure to install the adapters on the same drive as HP OpenView or NetView.

Installing and Upgrading HPOV-NetView Adapters

Upgrade/Migration Paths

You may upgrade DFM 2.0.6 on a system with Common Services 3.0.3 and DFM 2.0.3 or higher. You can perform a local (inline) upgrade or a remote upgrade. For more information, see "Upgrading and Migrating DFM."

Table 1-3 lists the basic upgrade/migration sequence.

Note The specific upgrade sequence may vary depending on whether you are doing a local or remote upgrade, and whether you are upgrading from DFM 1.2.x or DFM 2.0.x.

Table 1-3 Upgrade/Migration Roadmap

Description

References

Step 1

Upgrade your operating system, if required or desired.

Caution If you are upgrading your operating system from Solaris 8 (Solaris 2.8) to Solaris 9 (Solaris 2.9), perform this step after upgrading DFM.

See vendor documentation

Step 2

Upgrade Common Services 3.0.3.

Installation and Setup Guide for Common Services 3.0.3 (Includes CiscoView) on Solaris

Step 3

If you want to upgrade DFM 2.0.3 on a system with an NMS (HP OpenView or NetView), do one of the following:

•If the NMS is already installed, determine whether to upgrade it and do so if required.

•Install the NMS.

Note If the NMS is not installed before DFM, you will have to reinstall DFM later.

•For supported versions of NMSs, see Supported NMS Integration

•For installation instructions, see vendor documentation

Step 4

If you want to upgrade DFM 2.0.3 on a system with the contents of the LAN Management Solution:

a. Check the quick start guide for the order of installation.

b. Install any products that should be installed before DFM.

Quick Start Guide for LAN Management Solution 2.5.1 (Maintenance Kit)

Step 5

Upgrade to Device Fault Manager 2.0.6.

"Upgrading and Migrating DFM."

Step 6

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.

Note Be sure to install the adapters on the same drive as HP OpenView or NetView.

Installing and Upgrading HPOV-NetView Adapters

Server Requirements and Recommendations

This section describes the server requirements and recommendations for Common Services and DFM 2.0.6.

Note If you are installing DFM with the contents of the LAN Management Solution, the server requirements might be different. See the quick start guide for the appropriate bundle for additional information.

Minimum Server Requirements

The minimum system requirements for a CiscoWorks server running Common Services 3.0.3 and Device Fault Manager 2.0.6 are shown in Table 1-4. For requirements when running the LMS 2.5.1 bundle, see the Quick Start Guide for the LAN Management Solution 2.5.1 (see Related Documentation).

Table 1-4 Server System Minimum Requirements

Requirement Type

Minimum Requirements

System hardware

•Sun UltraSPARC IIIi¹ with two² 1-GHz CPUs.

•17-inch color monitor.

•CD-ROM drive.

System software

Solaris 8 (Solaris 2.8) or Solaris 9 (Solaris 2.9).

Note DFM supports only US-English and Japanese language versions of Solaris operating systems. Set the default locale to US-English for the US-English version and Japanese for the Japanese version.

Available memory (RAM)

2 GB.

Available disk space

•4 GB on the partition on which you install the product. The default partition is /opt, and the default path is /opt/CSCOpx.³

•Swap space equal to double the amount of memory (RAM). For example, if your system has 2 GB of RAM, you need 4 GB of swap space.

Additional required software

Common Services must be installed before you install DFM. For installation instructions, see Installation and Setup Guide for Common Services 3.0.3 (Includes CiscoView) on Solaris.

Additional optional software

To use the desktop on the server system, you need one of the following browsers:

•Netscape Navigator 7.0—Use Netscape Navigator downloaded from the Sun website only.

•Mozilla 1.7.13

¹DFM supports Sun SPARC Ultra IIIi machines, such as Sun Fire V440.

²If you are operating DFM with a restricted license, only one CPU is required.

³DFM 2.0.6 is installed in the same directory as Common Services.

Caution Do not use nonstandard Java options through the JAVA_OPTIONS environment variable.

To verify the amount of available disk space in each of the specified partitions and directories, enter:
# df -k directory
where directory is the partition or directory for which you want to check the available disk space.

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 If you choose to automatically synchronize DFM device inventory with the Common Services Device and Credentials Repository (DCR) and the synchronization causes DFM to exceed the limits, DFM stops adding devices to the managed inventory. (See Supported NMS Environments for Device Import.)

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 --sizes
For 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.

Solaris Patches

Table 1-5 lists the required and recommended patches for Solaris. Use the showrev -p command to verify that these patches have been applied. The required patches are mandatory for all CiscoWorks features to function properly. The recommended patches are optional. Some of the CiscoWorks features may not work if these patches are not installed on your system.

Table 1-5 Solaris Patches

Operating System

Required Server Patches

Required Client Patches

Recommended Server Patches

Recommended Client Patches

Solaris 8 (Solaris 2.8)

111327-05

110945-08

110934-16

110898-09

109326-14

108827-40

108528-29

111626-03

108652-81

108921-21

108940-62

110951-05

110662-12

110615-11

108964-06

110286-11 109324-05

Solaris 9 (Solaris 2.9)

114224-01

113580-01

112839-04

112233-12

114006-01

112771-14

112661-06

113244-05

113326-01

112998-03

113713-14

112964-07

113575-05

112970-07

112874-31

112808-06

Client Requirements

The minimum system requirements for the CiscoWorks client are shown in Table 1-6.

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-6 Client System Requirements Summary

Requirement Type

Minimum Requirements

System hardware and software

One of the following:

•IBM system with at least a 1-GHz Pentium processor running:

–Windows 2000 Professional, Server, and Enterprise Server

–Windows XP with Service Pack 2

–Windows Server 2003 Standard or Enterprise Edition with Service Pack 1

•Sun SPARC III running Solaris 8 (Solaris 2.8) or Solaris 9 (Solaris 2.9)

Note DFM supports only US-English and Japanese versions of the Windows Operating System (OS) and the Solaris OS. Set the default locale to US-English for the US-English OS, and Japanese for the Japanese OS.

Color monitor with video card set to 24 bits color depth.

Available memory (RAM)

512 MB.

Available disk space

1 GB swap space.

Note Swap space should be equal to twice the amount of RAM.

Browser

One of these browsers:

•On Windows clients:

–Internet Explorer SP1 (6.0.28) on Windows

–Internet Explorer SP2 (6.0.29) on Windows XP SP2

–Internet Explorer SP1 (6.0.3790) on Windows 2003

–Netscape 7.2 on Windows

–Mozilla 1.7.13 on Windows

•On Solaris clients:

–Netscape Navigator 7.0

–Mozilla 1.7 and 1.7.5

For Solaris, use Netscape Navigator downloaded from the Sun website only.

Supported NMS Environments for Device Import

DFM device inventory is imported 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.

Using DCR, you can import devices from:

•A local network management system (NMS)—Common Services supports import from NetView and HP OpenView. For supported versions, see Supported NMS Integration.

•A remote NMS—The same NMSs supported locally are supported remotely.

•A file—File can be exported from another product and formatted for import to DCR.

By default, DFM is configured to automatically synchronize its device list with DCR. If the synchronization causes the DFM system to exceed its limits, 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. For more information, see the User Guide for Device Fault Manager 2.0.6.

Supported NMS Integration

DFM supports integration with network management systems (NMSs) as follows:

•DFM listens for traps from managed devices on port 162 (by default). If another NMS on the system with DFM uses port 162, DFM uses port 9000 (and the installation script adds an informational note to the DFM installation log that port 162 was in use).

•DFM forwards traps to destinations that you specify, as follows:

–To forward pass-through traps, see Configuring SNMP Trap Forwarding.

–To forward processed traps, see "Managing SNMP Trap Notifications" in the "Using Notification Services" chapter of User Guide for Device Fault Manager 2.0.6.

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 2.0.6.

•DFM provides the HPOV-NetView adapters, which forward traps (sent from managed devices to the NMS) to DFM from remote or local hosts running:

–HP OpenView 6.4 and 7.0.1

–NetView 7.1 and 7.1.4

Installing these adapters on remote machines is described in Installing and Upgrading HPOV-NetView Adapters.

Note To use the HPOV-NetView adapters with a local version of HP OpenView or NetView, make sure that HP OpenView or NetView is installed before you install DFM.

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 this URL:

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.6, see Release Notes for Device Fault Manager 2.0.6 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 service packs (formerly called 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.