ehealth installation en

8/21/2019 Ehealth Installation En

1/160

Installation Guide

r6.2

CA eHealth®


2/160

This documentation and any related computer software help programs (hereinafter referred to as the

"Documentation") are for your informational purposes only and are subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part,

without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may

not be used or disclosed by you except as may be permitted in a separate confidentiality agreement between you and

CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation,

you may print a reasonable number of copies of the Documentation for internal use by you and your employees in

connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print copies of the Documentation is limited to the period during which the applicable license for such

software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify

in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION "AS IS" WITHOUT

WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER

OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION,

INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR

LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and

is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with "Restricted Rights." Use, duplication or disclosure by the United States Government is subject to the

restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section

252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2009 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein

belong to their respective companies.


3/160

CA Product References

This document may reference the following CA products:

■ CA eHealth® AdvantEDGE View

■ CA eHealth® Application Response

■ CA eHealth® Business Service Console (eHealth BSC)

■ CA eHealth® Distributed eHealth

■ CA eHealth® Fault Manager

■ CA eHealth® Live Health® Application

■ CA eHealth® Response

■

CA eHealth®

Service Availability■ CA eHealth® SystemEDGE

■ CA eHealth® TrapEXPLODER

■ CA eHealth® Voice Quality Monitor (VQM)

■ CA eHealth® AIM for Apache

■ CA eHealth® AIM for Microsoft Exchange

■ CA eHealth® AIM for Microsoft IIS

■ CA eHealth® AIM for Microsoft SQL Server

■ CA eHealth® AIM for Oracle

■ CA Insight™ AIM for CA eHealth®

■ CA Insight™ Database Performance Monitor for Distributed Databases (CA

Insight DPM for Distributed Databases)

■ CA eHealth® Integration for Alcatel (eHealth - Alcatel)

■ CA eHealth® Integration for Cisco IP Solution Center (eHealth - Cisco ISC)

■ CA eHealth® Integration for Cisco WAN Manager (eHealth - Cisco WAN

Manager)

■ CA eHealth® Integration for HP OpenView (eHealth - OpenView)

■ CA eHealth® Integration for Lucent (eHealth - Lucent)

■

CA eHealth® Integration for Netcool (eHealth - Netcool)

■ CA eHealth® Integration for Nortel Preside (eHealth - Nortel Preside)

■ CA eHealth® Integration for Nortel Shasta SCS GGSN (eHealth - Nortel

GGSN)

■ CA eHealth® Integration for Psytechnics (eHealth - Psytechnics)


4/160

■ CA eHealth® Integration for Starent (eHealth - Starent)

■ CA SPECTRUM®

■ CA Unicenter® Network and Systems Management (Unicenter NSM)

■

eTrust® Identity and Access Management (eTrust IAM)

■ CA Embedded Entitlements Manager (CA EEM)

Note: CA Embedded Entitlements Manager (CA EEM) is the new name for eTrust

IAM. This product will be rebranded throughout the documentation in a future

release.

Contact CA

Contact Technical Support

For your convenience, CA provides one site where you can access the information

you need for your Home Office, Small Business, and Enterprise CA products. At

http://ca.com/support, you can access the following:

■ Online and telephone contact information for technical assistance and

customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about CA product documentation, you can

send a message to [email protected].

If you would like to provide feedback about CA product documentation, complete

our short customer survey, which is also available on the CA Support website,

found at http://ca.com/docs.

http://www.ca.com/supporthttp://www.ca.com/supportmailto:[email protected]:[email protected]:[email protected]://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docsmailto:[email protected]://www.ca.com/support


5/160

Contents 5

Contents

Chapter 1: Overview 9

About This Guide .............................................................................. 9

Audience ...................................................................................... 9

Chapter 2: Preparing for Installations and Upgrades 11

Installation Guidelines and Prerequisites ........................................................ 11

CA Insight Licensing ....................................................................... 11

Installation Guidelines ..................................................................... 12

Installation Prerequisites .................................................................. 16

Upgrade Guidelines and Prerequisites .......................................................... 19

Upgrade Guidelines ....................................................................... 19

Upgrade Prerequisites ..................................................................... 21

Data Loss and Downtime .................................................................. 23

Merging Groups and Group Lists ........................................................... 24

InstallPlus and Oracle Update Software ......................................................... 26

Download and Extract the InstallPlus Program .............................................. 26

Download and Save the Oracle Update Software ............................................ 29

IPv6 Configuration Prerequisites ............................................................... 30

IPv6 Support and Limitations .................................................................. 31

Chapter 3: Installing eHealth (Windows) 33

eHealth Installation ........................................................................... 33

eHealth Installation Package ............................................................... 34

System Security .......................................................................... 35

Copy the DVDs to a Disk .................................................................. 35

Start the eHealth Installation .................................................................. 35

Additional Tasks .......................................................................... 40

Start and License eHealth ..................................................................... 41

Add eHealth Licenses ...................................................................... 41

Install Report Center After eHealth is Installed .................................................. 43

Where to Go from Here .......................................................................

43

Chapter 4: Installing eHealth (UNIX) 45

eHealth Installation ........................................................................... 45

eHealth Installation Package ............................................................... 46

System Security .......................................................................... 46


6/160

6 Installation Guide

Guidelines for Installation from DVD ........................................................ 47

Copy the DVDs to a Disk .................................................................. 48

Mount an ISO Image on a Solaris System ................................................... 49

How to Configure Resource Limits on Solaris ................................................ 51

Start the eHealth Installation .................................................................. 52

Additional Tasks .......................................................................... 58

Start and License eHealth ..................................................................... 59

eHealth Licenses .......................................................................... 60

Install Report Center Manually After eHealth Is Installed ........................................ 62

Where to Go from Here ....................................................................... 63

Chapter 5: Upgrading eHealth (Windows) 65

eHealth Upgrade .............................................................................. 65

Copy the contents of the DVDs ............................................................. 66

eHealth Software Package ................................................................. 66

Start the eHealth Upgrade ................................................................. 67

Additional Tasks .............................................................................. 69

Activate a Distributed eHealth Cluster ...................................................... 70

Finalize Upgrade .......................................................................... 71

Cleanup Tasks ............................................................................ 72

Chapter 6: Upgrading eHealth (UNIX) 75

eHealth Upgrade .............................................................................. 75

eHealth Software Package ................................................................. 76

Start the eHealth Upgrade .................................................................

76 Additional Tasks .............................................................................. 79

Activate a Distributed eHealth Cluster ...................................................... 80

Finalize Upgrade .......................................................................... 82

Cleanup Tasks ............................................................................ 82

Appendix A: Administration Tasks Reference 85

Tasks to Perform Before You Install or Upgrade eHealth ......................................... 85

Check the File System Format (Windows) ................................................... 85

Change the eHealth System Hostname (Windows) .......................................... 86

Add Swap Space (Windows and UNIX) ...................................................... 86

Check and Modify Kernel Requirements (UNIX) ............................................. 88

Mount the DVD Drive (UNIX)............................................................... 94

Unmount the DVD Drive (UNIX) ...........................................................100

Tasks to Perform After You Install or Upgrade eHealth.......................................... 100

Specify the Mail Server (Windows) ........................................................101

Specify the Printer (Windows) ............................................................102


7/160

Contents 7

Change the Web Server Port Number (Windows and UNIX) .................................103

Enable the FtpCollector to Run on Solaris 5.9 and Solaris 10 ................................ 105

Authentication Options ...................................................................106

Appendix B: Troubleshooting 121

Troubleshoot Installation Problems ............................................................121

Installation Program Exits before Completion ..............................................121

Database Creation Is Incomplete ..........................................................121

TrapEXPLODER Unable to Start ...........................................................123

Windows could not start the eHealth httpd61 on Local Computer ............................124

eHealth Console Fails to Start after Installation ............................................125

Troubleshoot Upgrade Problems ..............................................................126

System Does Not Meet Minimum Requirements ............................................126

Installation Program Exits During Activation ...............................................127

One or More Kernel Parameters Are Not Configured Properly ................................ 128

Restore Oracle On Cluster Members .......................................................128

eHealth Upgrade to 6.2 Unsuccessful on a Cluster Member ..................................129

Restore eHealth 5.7 or 6.0 on the Local System ............................................131

Restore eHealth r5.7 or r6.0 Across the Cluster ............................................134

Appendix C: Removing eHealth and Related Applications 139

Before You Remove eHealth ..................................................................139

Files and Directories Backup ..............................................................139

Windows Registry Backup (Windows Only) .................................................140

Directory Confirmation (UNIX Only) .......................................................

140 Remove eHealth r6.2 ........................................................................141

Remove eHealth on a Windows System ....................................................142

Remove eHealth on a UNIX System .......................................................147

Remove eHealth r5.7 or r6.0 .................................................................152

Remove eHealth 5.7 or 6.0 (Windows) ....................................................152

Remove eHealth r5.7 or r6.0 (UNIX) ......................................................153

Remove Report Center .......................................................................154

Remove Report Center from eHealth r6.0 systems .........................................154

Disable Report Center on eHealth r6.2 Systems ............................................155

Remove Report Center from eHealth r6.2 Systems .........................................156

Index 159


8/160


9/160

Chapter 1: Overview 9

Chapter 1: Overview

About This Guide

This guide describes how to do the following:

■ Check and prepare your system for eHealth installation

■ Install eHealth on Windows, Solaris, and HP-UX systems

■ Upgrade eHealth on Windows, Solaris, and HP-UX systems

■ Remove eHealth, Oracle, and third-party applications

■ Troubleshoot installation and database creation problems

Audience

This guide is intended for eHealth administrators who are responsible for

installing, starting, and licensing eHealth.

To configure response elements, you must have administrative permissions for

the eHealth console. To configure and manage your AR agents, you must have

administrative permissions for the eHealth Web interface.


10/160


11/160


Chapter 2: Preparing for Installations and

UpgradesBefore you install eHealth r6.2 or upgrade to r6.2 from eHealth r5.7, r6.0, or

r6.1, read the guidelines and perform any necessary procedures in this chapter.

This section contains the following topics:

Installation Guidelines and Prerequisites (see page 11)

Upgrade Guidelines and Prerequisites (see page 19)

InstallPlus and Oracle Update Software (see page 26)

IPv6 Configuration Prerequisites (see page 30)

IPv6 Support and Limitations (see page 31)

Installation Guidelines and Prerequisites

This section includes eHealth installation guidelines, prerequisites, and other

information you need to know when planning an eHealth installation in your

infrastructure.

You can install eHealth on the following system types:

■ Standard eHealth

■ eHealth Traffic Accountant

■

Distributed eHealth (back-end/polling system)

■ Distributed eHealth (front-end/reporting system)

CA Insight Licensing

CA eHealth Network Performance Manager customers are eligible for one license

of CA Insight Database Performance Monitor for Distributed Databases

exclusively for self-monitoring of their CA eHealth embedded database(s). This

license cannot be used to monitor non-eHealth embedded databases. You can

download CA Insight Database Performance Monitor for Distributed Databases

software from CA Support Online, http://ca.com/support. You can request a

license key for CA Insight Database Performance Monitor for Distributed

Databases from CA Total License Care, http://www.ca.com/us/servicecenter,

under Licensing. Customers who want to deploy CA Insight Database

Performance Monitor for Distributed Databases to monitor databases other than

the CA eHealth Network Performance Manager embedded database can purchase

additional licenses by contacting their CA sales representative.

http://www.ca.com/supporthttp://www.ca.com/supporthttp://www.ca.com/supporthttp://www.ca.com/us/servicecenterhttp://www.ca.com/us/servicecenterhttp://www.ca.com/us/servicecenterhttp://www.ca.com/us/servicecenterhttp://www.ca.com/us/servicecenterhttp://www.ca.com/support


12/160



Installation Guidelines

To avoid problems during the eHealth installation, follow these guidelines:

■ Install eHealth on a separate, dedicated system. eHealth should not be

installed on a system that has another enterprise class application installed,

such as SPECTRUM.

■ Stop the Windows Firewall/Internet Connection Sharing (ICS) service before

installing eHealth to avoid failure of the NuTCRACKER installation.

■ The creation and maintenance of time-aligned data will become an integral

part of eHealth. It is estimated that the database will grow by 30 to 40% to

support this new data. CA recommends that you use the Sizing Wizard at

www.support.concord.com to get a more precise estimation of the impact on

your database.

■ During the regularization backfill process we anticipate increased system

resource utilization including but not limited to:

–

Increased CPU activity

– Increased memory usage

– Increased disk I/O

Note: For information about how to regulate backfill, contact Technical

Support.

■ When choosing the eHealth administrator account, do not use the main

administrator’s account. Use a specific account for tightly controlled

administration purposes only. Using a general, enterprise-wide account

results in more unauthorized users accessing eHealth databases.

■

If SystemEdge 4.3 has been applied, it must be shut down prior to installingeHealth.

■ (Windows) Do not install eHealth on a system used as a domain controller.

■ (Windows) Before installing eHealth, stop and exit any unnecessary

applications running on your system. The following CA services must be

stopped if they are installed on your system:

– CA DSM r11 Common Application Framework

– CA Message Queuing Server

–

CA Pest Patrol Realtime Protection Service

– CA Unicenter NSM Systems Performance Agent for UAM

Also, disable all antivirus programs running on your system. You cannot

install eHealth on a system that has McAfee 8.0 or PowerShell installed.


13/160



■ (UNIX) If you plan to configure your eHealth environment to be highly

available, you must install third-party clusterware before you install eHealth.

Note: See the eHealth High Availability and Disaster Recovery

Administration Guide for more information about how eHealth integrates

with high availability clusterware.

■ (UNIX) Verify that you have the root user password for the target eHealth

system.

■ (UNIX) Determine that your system meets the minimum requirements for

installing eHealth r6.2 by running the prerequisite checker program before

installing eHealth. This lets you make any recommended adjustments and

updates to your system before you run the eHealth installation program.

To start the prerequisite check, insert the eHealth Software DVD. Log on as

root and run the nhCheckInstallPreReqs command. If you do not run this

check before installing eHealth, you will be alerted to system adjustments

and updates during the eHealth installation process.

■ (UNIX) Before installing eHealth, you may have to mount the DVD drive. You

may also want to copy the contents of the DVDs to a disk if the eHealth

system does not have a local DVD drive, or if you want to avoid changing

DVDs during installation.

Note: For instructions on these and other operating system tasks, see

Installing eHealth (UNIX) and Administration Tasks Reference.

■ eHealth provides an installation option (CA eHealth Without Database) that

does not install Oracle and its patches. If you are using this option, you must

use the CA eHealth Without Database DVD. Also, Oracle 10.2.0.4 or 10.2.0.3

and all necessary patches must be installed before you start the installation,

and the pre-installed Oracle must work. Note that only fresh installations on

Windows and Solaris systems are supported for this option. Upgrades from aprevious eHealth release (such as r5.7 or r6.0) and installations on HP-UX

systems are not supported.

More information:

How to Install CA eHealth Without Database (see page 14)


14/160



Software/Database Location Guidelines

When choosing locations for the eHealth software, Oracle software, and Oracle

database, follow these guidelines:

■

You can create a layout configuration file (LCF) that allows you to specify

where to place the database files.

Note: Use the eHealth Sizing Wizard to create the LCF. See the eHealth

Administration Guide for more information.

■ Specify local disks or disk partitions as locations for the eHealth database

files. If you plan to use more than nine locations for the eHealth database,

you must use the eHealth sizing wizard to create an LCF for input to the

eHealth installation program.

■ Specify top-level directories or subdirectories, such as D:\ehealth61 or

D:\oracle\product\ora10. Do not specify a root directory.

■

If you are installing eHealth without the Oracle database, note the following:

– eHealth and Oracle must reside on the same system.

– The Oracle path cannot contain spaces.

–

The installation process does not prompt for the destination location of

Oracle. Instead, it prompts for the existing location of the Oracle

software, which must already be installed.

■ Specify network drives that provide high bandwidth and low latency. For best

performance, consider using storage area networks (SANs) over Fibre

Channel or Gigabit Ethernet networks. However, SAN environments are not

tested, therefore, support is limited. If you experience a problem related to

the SAN, you may need to install on local disks until you can resolve the

issue.

■ (Windows) Do not specify file locations and installation directories by using

the Universal Naming Convention (UNC). Instead, use a mapped drive.

Note: CA neither tests on nor recommends the use of network-attached

storage (NAS) technology to host any eHealth components.

How to Install CA eHealth Without Database

To install CA eHealth without Database, you must install the required version of

Oracle software (including patchset and patches), make sure that Oracle is

functioning properly, and then install the eHealth software.

When you install eHealth without Database, you must specify the location of the

Oracle software. The installation process validates the following:

■ No spaces are in the path.

■ Oracle is installed on a local drive (Windows).

■ The full path is specified (Solaris).


15/160



■ The Oracle SID service is able to be created.

■ The Oracle version is at 10.2.0.4.0 or Oracle 10.2.0.3.0.

The process for installing CA eHealth Without Database is summarized as

follows:

1. Install the Oracle base software (Version 10.2.0.1.0).

Note: The Oracle Enterprise Edition for the Oracle base is required.

Otherwise, the eHealth regularized data will not work without partitioning in

the Enterprise edition.

2.

Install the Oracle patchset (Oracle 10.2.0.4 or 10.2.0.3).

3.

Install Oracle patches.

Note: For a list of Oracle security patches required for the CA eHealth

Without Database installation, see the r6.2 eHealth Release Notes.

4.

Verify that Oracle is installed and working properly.

5. Install CA eHealth Without Database.

Note: For more information about installing Oracle, see the Oracle Installation

Guide and Readme.

Report Center Guidelines

When you install eHealth you have the option to install Report Center, a reporting

system that enables you to create and run custom reports for eHealth elements.

Read these guidelines before you install Report Center:

■ You can install Report Center on Traffic Accountant systems. Report Center

can be installed for use with either a standard eHealth system or a Traffic

Accountant system, but not both.

■ Although you can install Report Center on Solaris and HP-UX eHealth

systems, users must log in to their eHealth web user accounts from Windows

client systems to access Report Center.

■ Running Report Center in a Distributed eHealth environment is not

supported. You can install Report Center on Distributed eHealth (back-end)

Systems, but you cannot install or use Report Center on Distributed eHealth

Consoles (front-end).

Note: For more information about Report Center, see the eHealth Report Center

User and Administration Guide.


16/160



How to Install VMware (Windows)

You can install eHealth on Windows systems that have been configured to use

VMware ESX version 3.0. eHealth can be installed and run with VMware on

stand-alone eHealth systems as well as systems in a Distributed eHealth Clusteror in a remote polling environment. The following steps outline this process:

1.

Configure VMware.

2.

Create virtual machines.

3.

Install the operating system on the newly created virtual machines.

4. Install eHealth.

Note: For information about system requirements, see the eHealth Release

Notes.

Installation Prerequisites

Read the following information to help ensure that you properly prepare the

system on which you plan to install eHealth.

Determine Your System Resources

■ If you plan to poll a large number of elements (approximately 50,000 or

more), Report Center can cause the temporary space to grow up to 24 GB.

The default temp space for eHealth systems is 7 GB. You must verify that the

Oracle database tablespace NH_TEMP resides on a disk that has sufficient

space for it to grow before installing Report Center.

■

When upgrading, you can use the eHealth Sizing Wizard to size your system,but any LCF files that are generated can only be used for new installations.

■ Time-aligned (regularized) statistics data is used by eHealth for custom

reports and the Live Reporting feature. eHealth time-aligns data samples to

help ensure consistent and efficient reporting. The data is stored in four

tablespaces within the eHealth database.


17/160



■ Typically, the additional disk space required is 50 percent of the current

statistics tablespace size. For planning purposes, use the sizing wizard to

obtain disk planning information. If the disk locations where your current

eHealth statistics database resides have enough free space to hold twice the

current tablespace sizes, you should have enough disk space. If the locationsdo not have enough free space, you can use the nhManageDbSpace

command to add more data files to increase the tablespace sizes, as well as

move tablespaces to larger disk locations.

Note: As of this release, time-aligned statistics data is now created during all

eHealth installations, not just Report Center. Additional disk space is

required for all eHealth installations. For details on freeing up space, see the

eHealth Administration Guide.

■ (UNIX) Before installing eHealth, run the prerequisite checker program to

determine if your system meets the minimum requirements for installing

eHealth r6.2. This allows you to make any recommended adjustments and

updates to your system without interrupting the eHealth installation

program.

To start the prerequisite check

1.

Insert the eHealth Software DVD.

2. Log on as root and type the following command:

nhCheckInstallPreReqs

Note: If you do not run this check before installing eHealth, you will be alerted to

system adjustments and updates during the eHealth install process.

Prepare For The eHealth Installation

■ Remove any existing versions of Oracle if you are installing the Oracle

database version shipped with eHealth. Use the commands and tools

provided with eHealth to install and manage the Oracle database software. If

you are using the CA eHealth Performance Manager Without Database

installation option, Oracle and the required Oracle patches must be installed

before you start the eHealth installation.

■ Hostnames can contain characters such as A-Z, a-z, 0-9, dashes (-), and

underscores (_). Hostnames cannot contain characters such as spaces and

periods (.).


18/160



■ Verify that the Simple Network Management Protocol (SNMP) service is

configured to support the community string public and to receive SNMP

packets.

■ Identify the locations where you plan to install the eHealth and Oracle

software, and eHealth database files.

Note: If you are using the CA eHealth Without Database installation option,

eHealth and Oracle must reside on the same system. The installer prompts

for the existing location of Oracle instead of the destination location. You can

use this option only if the Oracle software is already installed on a local drive

and is functioning properly.

■ (Windows) Create an ORA_DBA user group on the system.

Note: For more information, see your Windows documentation.

■ (Windows) Create an eHealth administrator account and add it as a member

of the Administrators and ORA_DBA groups. Use the following guidelines

when creating the account:

–

It can contain numbers and lowercase letters. Uppercase or mixed-case

letters are not supported.

–

The first character cannot be a number.

– It can belong to a Windows 2003 Active Directory domain.

■ (UNIX) Create a specific administrator account that you can use for eHealth.

You cannot use the root account as the eHealth administrator. Use the

following guidelines when creating an administrator account:

– It can contain lowercase letters and numbers. Uppercase or mixed-case

letters are not supported.

–

The first character cannot be a number.

– The account must not use the eHealth installation directory as its home

directory.

– Create the eHealth administrator account as a local user account (not an

enterprise-wide account) to insulate eHealth and its data from other

corporate activities and to limit dependencies on external machines

(such as NIS/NIS+ servers).

– Do not set hard or soft resource limits (ulimits) for the eHealth

administrator account.

– Do not place the eHealth administrator account home directory on a

remote system. If you do so, the loss of a connection could disrupt the

eHealth system.

■ (UNIX) To use diacritical characters on Solaris, you must set up a locale on

the Solaris system that has the right character set. For US, this is locale

en_us and character set Latin1.


19/160

Upgrade Guidelines and Prerequisites



This section includes eHealth upgrade guidelines, prerequisites, and other

information you need to know when planning to upgrade eHealth, Oracle, and

related applications.

Upgrade Guidelines

To avoid problems during the eHealth upgrade, follow these guidelines:

■ Confirm that the current release of eHealth is polling and running reports

without errors.

■ You cannot use a layout configuration file (LCF) to move tablespaces and

data files or otherwise manipulate the eHealth database during the upgrade

process. For more information, see the eHealth Administration Guide.

■ (Windows) Before upgrading eHealth, disable all antivirus programs running

on your system. Re-enable the programs only after the upgrade has finished.

eHealth will not operate on a system that has McAfee 8.0 installed.

■ (UNIX) Confirm the root user password for the target eHealth system.



eHealth r6.2. This step lets you make any recommended adjustments and

updates to your system without interrupting the eHealth installation

program.

■ To upgrade eHealth r6.1 to r6.2, you must first install certification D03 and

then use the eHealth r6.2 service pack installer to perform the upgrade.


1.

Insert the eHealth Software DVD.

2.

Log on as root and type the following command:




Software Location Guidelines

When choosing a location for the eHealth software, follow these guidelines:

■ Specify a local disk or a disk partition.

■ (Windows) Specify a top-level directory or subdirectory, such as

D:\ehealth61. Do not specify a root directory.


20/160



■ Specify a network drive that provides high bandwidth and low latency. For

best performance, consider using storage area networks (SANs) over Fibre

Channel or Gigabit Ethernet networks. However, testing is not done using

SAN environments; therefore, support is limited. If you experience a

problem related to the SAN, you may need to install on local disks until youcan resolve the issue.

■ (Windows) Do not specify a file location using the Universal Naming

Convention (UNC) for identifying shared files. Instead, use a mapped drive.

Note: CA neither tests on nor recommends the use of network-attached storage

(NAS) technology to host any eHealth components.

Report Center Guidelines

When you upgrade eHealth you have the option to install Report Center. Report

Center is a reporting system that enables you to create and run custom reports

for eHealth elements. If Report Center is already installed on your system, it willbe upgraded along with eHealth, Oracle, and other related applications.

Read these guidelines before you install Report Center:

■ You can install Report Center on Traffic Accountant systems. Report Center

can be installed for use with either a standard eHealth system or a Traffic

Accountant system, but not both.

■ If you are upgrading from an eHealth r6.0 Traffic Accountant system, you

can choose to install Report Center r6.2. However, note the following:

– If your eHealth r6.0 Traffic Accountant system uses no base eHealth

statistical elements and you upgrade to eHealth r6.2, the Report Center

installation deploys the new eHealth 6.2 Traffic Accountant reports.

– If your eHealth r6.0 system uses statistics elements, Traffic Accountant

data (some base eHealth statistical elements included), or both, the

Report Center r6.2 installation deploys the base eHealth r6.2 Report

Center statistical reports.

■ If you are upgrading from an r6.0 eHealth system (including a system using

one or more Traffic Accountant components) with Report Center currently

installed, the upgrade deploys the base eHealth r6.2 Report Center statistical

reports.

■ Although you can install Report Center on Solaris and HP-UX eHealth

systems, users must log in to their eHealth web user accounts from Windows

client systems to access Report Center.


21/160



■ Report Studio requires Internet Explorer version 5.5 SP2 or later.

■ Running Report Center in a Distributed eHealth environment is not

supported. You can install Report Center on Distributed eHealth (back-end)

Systems, but you cannot install or use Report Center on Distributed eHealth

Consoles (front-end).

Note: For more information about Report Center, see the eHealth Report Center

User and Administration Guide.

Remote Poller Site Upgrade Guidelines

■ If your eHealth systems are remote polling sites, and they run eHealth 5.6.5,

they must upgrade to eHealth 5.7 or 6.0, before upgrading to eHealth r6.2.

■ If your sites are running a version of eHealth earlier than 5.6.5 Patch 3,

update to eHealth 5.6.5 Patch 8, upgrade to eHealth 5.7 or 6.0, then upgrade

to eHealth r6.2. If you are running eHealth 5.0.2, you must migrate to

eHealth 5.7 before upgrading to eHealth r6.2.

■ When you re-enable a remote polling site after an upgrade, and you use

$NH_HOME_NEW/modules/remotePoller/spool (the default) as the location

for new statistics and configuration output files, you must also update the

FTP home directory to the new location, otherwise data will not get imported

from the remote polling site.

Note: For more information about configuring FTP connections, see the

eHealth Remote Poller User Guide.

■ Upgrade the central site before you upgrade the remote poller sites. Because

remote polling is backwards compatible, upgrading the central site first

allows polling to continue from the remote sites that have not yet upgraded.

Use the following process when upgrading remote poller sites to eHealth r6.2:

1.

Run the nhShowUpgradeChanges command on the central site to identify

any group or group list configuration problems. You must resolve those

problems before you upgrade.

2.

Disable import polling from the remote sites on the central site.

3.

Upgrade the central site to eHealth r6.2.

4.

Enable import remote polling on the central site.

5. Disable one remote site at a time, upgrade the site to eHealth r6.2, and then

re-enable the site.

This step helps ensure that all but one site is enabled at a time.

Upgrade Prerequisites

Review the following information to make sure that you properly prepare the

system on which you plan to upgrade eHealth.


22/160



Determine Your System Resources

■ If you plan to poll a large number of elements (approximately 50,000 or

more), Report Center can cause the temporary space to grow up to 24 GB.

The default temp space for eHealth systems is 7 GB. You must verify that the

Oracle database tablespace NH_TEMP resides on a disk that has sufficient

space for it to grow before installing Report Center.

■ When upgrading, you can use the eHealth Sizing Wizard to size your system,

but any LCF files that are generated can only be used for new installations.

■ Time-aligned (regularized) statistics data is used by eHealth for custom

reports and the Live Reporting feature. eHealth time-aligns data samples to

help ensure consistent and efficient reporting. The data is stored in four

tablespaces within the eHealth database.

■ Typically, the additional disk space required is 50 percent of the current

statistics tablespace size. For planning purposes, use the sizing wizard to

obtain disk planning information. If the disk locations where your current

eHealth statistics database resides have enough free space to hold twice the

current tablespace sizes, you should have enough disk space. If the locations

do not have enough free space, you can use the nhManageDbSpace

command to add more data files to increase the tablespace sizes, as well as

move tablespaces to larger disk locations.

Note: As of this release, time-aligned statistics data is now created during all

eHealth installations, not just Report Center. Additional disk space is

required for all eHealth installations. For details on freeing up space, see the

eHealth Administration Guide.



eHealth r6.2. This allows you to make any recommended adjustments andupdates to your system without interrupting the eHealth installation

program.


1. Insert the eHealth Software DVD.

2.

Log on as root and type the following command:





23/160



Prepare for the eHealth Upgrade

■ Identify an eHealth r6.2 software location that has at least 2 GB of free disk

space.

■

Update your eHealth elements and the poller configuration by rediscovering.Resolve any errors.

■ If you are running any nhConfig jobs that import configuration information

for eHealth integration modules, disable those jobs before upgrading.

■ Back up the eHealth database.

Data Loss and Downtime

Data loss

Data loss refers to the time period when eHealth is not polling elements.

Downtime

Downtime refers to the time period when users are unable to access the

eHealth console, the eHealth web user interface, Report Center, or OneClick

for eHealth and cannot run scheduled reports.

Standard eHealth Upgrades

In a typical eHealth environment (monitoring 50,000 elements or less), the data

loss and downtime will be:

■ Data loss: Minimal loss of statistical data during the eHealth upgrade

process. (Traffic Accountant customers may see a gap in conversation data

of two to three hours.)

■ Downtime: One or more hours depending on the size of your database.

Note: On both stand-alone eHealth systems and systems that are part of a

Distributed eHealth Cluster, the eHealth statistics poller is used to collect data

during the eHealth upgrade. This helps minimize data loss during the upgrade

process.


24/160



Remote Polling and Distributed Upgrades

In a typical eHealth remote polling environment, you will encounter up to 30

minutes of data loss on each remote site during the activation of eHealth r6.2, in

addition to the data loss that occurs during the eHealth upgrade process. Thecentral site will also show these slight data gaps in reports.

If you are upgrading to eHealth r6.2 in a Distributed eHealth environment:

■ Upgrade all systems in the cluster before you activate eHealth.

■ The cluster system might experience more than 30 minutes of data loss and

approximately 1 hour or more of server downtime because of the Oracle

upgrade. The actual times depend on the size and speed of your system.

During this time, the cluster member being upgraded will be unavailable.

Merging Groups and Group Lists

Groups of elements are used for many purposes in eHealth, including reporting,

security, and assigning Live Health profiles. In releases of eHealth before 5.7,

groups had specific types, where a group of a certain type could only contain

elements of that type. For example, a LAN/WAN group included Ethernet and

WAN link elements, and a Router group would contain router and switch

elements.

As of eHealth r6.0, groups are universal. You can place elements of any type into

the same group. This feature helps ease group maintenance.

Security

If you upgrade to eHealth r6.2 from eHealth r5.7, all groups with the same name,

regardless of type, are merged into one group during the database conversion

process. Also, group lists with the same name are merged into one list.

Therefore, eHealth users who are only allowed access to certain

technology-specific groups may be able to view and report on other groups and

elements.

For example, assume that there are three groups named Boston: a LAN/WAN

group, a Router group, and a Server group. Mary is allowed to see only the group

Boston-LAN/WAN and Joe is allowed to see only the group Boston-Server. The

administrator has access to all three. During the upgrade, eHealth merges them

into one group, Boston, which both Joe and Mary will be able to view. This could

potentially cause a problem if Joe does not have rights to view servers and Marydoes not have rights to view LAN/WAN elements. To avoid the group merge,

rename the groups to have unique names before you upgrade.


25/160



Conversion Check

Before you upgrade to eHealth r6.2 from 5.7, run a conversion check to generate

a report which includes the following information:

■

A warning about security changes due to merging

■ Anticipated group and group list changes

■ A summary of the groups and group lists that cannot be merged on a central

site because of remote polling restrictions

After viewing this report and its recommendations, decide which groups and

group lists need to be renamed uniquely. For example, you may want to rename

them to avoid security breaches and to keep groups of different types unique for

purposes of reporting or organization.

Run the Conversion Check

To run the conversion check on a central site of a remote polling environment,

insert the eHealth installation media and run the following command as the

eHealth user:

nhShowUpgradeChanges

The eHealth upgrade process also runs this command to identify possible

security impacts and configuration conflicts. When security impacts are found,

the conversion software displays a warning, creates a log, and asks you if you

want to continue.

Note: As part of the database conversion, existing reports, scheduled reports,

drill-downs, and web security references will also be updated.

Merged Groups and Group Lists on Remote Pollers

In an eHealth Remote Polling environment, when you upgrade each remote

polling site, eHealth merges the groups and group lists created on that polling

site that have the same name. To avoid the merge, you should rename the

groups and group lists before you upgrade. When you upgrade a central site, any

groups that were created on remote sites and imported to the central site could

cause the upgrade to fail if those groups contain elements managed by more

than one eHealth system.

If you are unable to upgrade a central site due to errors with group membership

and merges, contact Technical Support.


26/160

InstallPlus and Oracle Update Software



To help ensure that you receive the current security patches and fixes for both

new installations and upgrades of eHealth, we recommend that you do the

following:

■ Download the latest InstallPlus software.

■ Request the latest Oracle update from the eHealth support web site instead

of using the installation media that you received in the eHealth package.

Note: You can ignore these recommendations if you are installing eHealth

Without Database.

Download and Extract the InstallPlus Program

InstallPlus is the eHealth program that reduces downtime by installing all of thelatest fixes and certifications in one procedure. To help ensure that you install the

latest available software when you install eHealth, you must use InstallPlus.

The InstallPlus program performs the following tasks:

■ Saves the latest installation files in a directory on the eHealth system.

■ Prompts you for the location of the eHealth software.

■ Installs the eHealth software plus the service packs and certification updates

available for this release.

Note: InstallPlus does not replace the standard service pack installation

program: use InstallPlus only when you install an eHealth release for the firsttime, or when you upgrade from a previous eHealth release. After you have

installed an eHealth release, continue to use the service pack installation

program to install service packs for your release.


27/160



To download and extract the InstallPlus program

1.

Access the downloads section of the eHealth support website at

http://support.concord.com.

Select the InstallPlus program for the language and release that you want,and click the corresponding link.

Note: If you cannot access the downloads section, use the InstallPlus

software on the eHealth Software DVD in the eHealth installation package.

2.

Download the file to your eHealth system and save it in a new, empty

directory.

Confirm that you have at least the following disk space available for the

InstallPlus software:

■ Windows: 350 MB

■ Solaris: 1100 MB

■

HP-UX: 800 MB

Note: For the InstallPlus program to work correctly, the file must be saved in

a new directory.


28/160



3.

Extract the file by doing the following, depending on your platform:

■

Windows:

Double-click the LAN _release _WIN_splevel _PLUS.exe file to extract the

InstallPlus files into the current working directory.

LAN

Represents the supported language, either English (ENU), French

(FRA ), or Japanese (JPN)

release

Represents the release number such as 601 for eHealth r6.1.

splevel

Represents the service pack release level.

The InstallPlus program files are extracted into the current directory.

During the eHealth installation you will be prompted to navigate to thisdirectory to start the eHealth installation.

■ UNIX:

a.

Log on as root and change to the new directory.

b.

Enter the following command to make the file executable:

chmod +x LAN_release_UNIX _splevel_PLUS.sh

LAN

Represents the supported language; either English (ENU), French

(FRA ), or Japanese (JPN).

release

Represents the release number, such as 610 for eHealth r6.1.

UNIX

Represents SOL for Solaris or HPX for HP-UX.

splevel

Represents the service pack release level, such as 01.

c.

Run the following command to extract the InstallPlus files into the

current working directory:

./LAN_release_UNIX _splevel_PLUS.sh

The InstallPlus program files are extracted into the current directory.During the eHealth installation you will be prompted to navigate to this

directory to start the eHealth installation.


29/160



Download and Save the Oracle Update Software

The Oracle update software contains security patches and other fixes for the

eHealth database software.

The Release Notes document includes a list of services that must be stopped on

Windows target systems to help ensure that the Oracle software is updated

successfully.

Note: You must contact eHealth Technical Support at

http://support.concord.com to request the latest Oracle update software for the

language and release that you want. Use the Oracle update software on the

installation media in the eHealth installation package only if you cannot access

the Oracle update from Technical Support.

To download and save the Oracle update software

1.

Download the Oracle update file that you receive from Technical Support toyour eHealth system and save it in a new, empty directory.

Note: On Windows systems, do not use a directory path that contains spaces

such as C:\Documents and Settings\All Users\eHealthInstall, or the Windows

Desktop.

The file is saved to a new directory.

2.

Do one of the following, depending on your platform:

■ Windows

Double-click the ORA_WIN_VER.zip file to extract the Oracle update

patch set file into the current working directory.

VER

Represents the database release patch level, such as 10.2.03.

■

UNIX

a.

Log on as root and change to the new directory.

b.

Run the following command to extract the Oracle update patch set

file into the current working directory:

Note: The eHealth installation must finish before you run this command.

/opt/eHealth/bin/sys/nhiUnZip ORA_platform_VER.zip

platform

Represents SOL for Solaris or HPX for HP-UX.

VER

Represents the database release patch level, such as 10.2.03.

The Oracle update software file is extracted into the current directory.


30/160

IPv6 Configuration Prerequisites


IPv6 Configuration Prerequisites

The network that eHealth resides on must be capable of routing both IPv4 and

IPv6 addressed packets. Host name and address lookup must be configured to

support both IPv4 lookups (hosts) and IPv6 lookups (ipnodes).

The host system that eHealth resides on must be configured to support IPv6. The

host system must have a routable IPv6 address. IPv6 technology allows for

non-routable addresses, but these will not work with eHealth outside of a simple

hub the system might be connected to.

The Operating Systems supported by eHealth have differing amounts of

additional pre-installation setup needs, as follows:

■ Solaris 9 and 10 and HP-UX require no additional configuration.

■ Windows 2003 (either R1 or R2; either standard or enterprise) must have at

least SP1 (SP2 is recommended). The design of IPv6 support on Windowsrequires that IPv6 be specifically enabled with the Windows NETSH

command. A routable IPv6 address must also be added, either with this

command or automatically by router assignment.


31/160

IPv6 Support and Limitations



The following eHealth support is available with IPv6:

■

All of the basic behavior of eHealth supports IPv6. You can discover, poll,record statistics for and report on elements of agents on devices with IPv6

addresses.

■ Systems running eHealth in cluster mode can have either IPv4 or IPv6

addresses as long as IPv4 and IPv6 subnets are reachable from each other.

■ The Apache Web server for eHealth supports IPv6 as long as the Web

browser also supports IPv6. Any Firefox browser and Internet Explorer 7

(IE7) support IPv6, while IE6 does not.

■ The eHealth Trap Server supports IPv6 addresses as trap destinations and in

variable bindings using SNMPv1 and SNMPv2c respectively. This is done by

overloading the ASN.1 IP address primitive with an IPv6 address. This is a

non-standard approach that is also being used by Cisco in SNMPv1.■ All of the eHealth Live clients (Exceptions, Status and Trend) support IPv6.

■ The new eHealth Traffic Accountant module with the eHealth Netflow NMS

supports IPv6 addresses as data. As this is an integration module it does

have a limitation as described below.

■ All of the eHealth peripheral products (such as eHealth SystemEDGE and

eHealth Trap Exploder) support IPv6.

■ The eHealth Application Response controller (and all eHealth servers)

support IPv6. There are some limitation for eHealth Application Response.

■ Internal communications between eHealth processes gives priority to IPv6

addresses over IPv4. This does not apply where a user provides an IPv4

address as in discovery. All user supplied addresses are always given

priority.

Limitations of IPv6 support in eHealth include the following:

■ IPv6 will not function correctly on an eHealth host that has no IPv4

connectivity. eHealth r6.2 requires a dual addressed system with at least one

of each of an IPv4 and a routable IPv6 address.

■ On Windows 2003 only, the FTP command does not support IPv6. The result

is that integration modules and an eHealth Central Site cannot establish

communications with the IPv6 address of a NMS such as Netflow or Cisco

Wan Manager or an eHealth Remote Poller system.

■

On Windows 2003, IE6 does not support IPv6. The eHealth OCE will not work

with IPv6 addresses unless IE 7 is installed on the host.

■ The eHealth Application Response agent can monitor IPv4 traffic on a system

with an IPv6 address but it cannot monitor IPv6 traffic.

■ For users of the eHealth High Availability feature, while Sun Cluster does

support IPv6, the Veritas cluster ware package does not.


32/160



■ For users of the eHealth Disaster Recovery feature, XoSoft WANSync does

not support IPv6.

■ The eHealth Traffic Accountant for RMON2 probes and the Cisco Netflow NMS

do not support IPv6.


33/160


Chapter 3: Installing eHealth (Windows)

This chapter describes how to install the following:

■ eHealth r6.2 with embedded Oracle for the first time on a Windows system

■ eHealth r6.2 Without Database for the first time on a Windows system

The installation process takes about three hours to finish but can vary depending

on the speed of your system and disk devices, and the size of your database. If

you are installing eHealth with embedded Oracle, you can save about an hour of

time by copying the eHealth and Oracle software installation media to a local

disk.

The installation program performs the following tasks:

■

Installs the new release of eHealth and related applications

■ Installs Oracle 10g (if you are installing eHealth with embedded Oracle) or

prompts you for the location of your existing Oracle software (if you are

installing eHealth without Oracle)

■ Applies an Oracle update, if needed

Note: Review Preparing for Installations and Upgrades before starting the

eHealth installation.

eHealth Installation

The eHealth installation program installs the core components of eHealth which

enable it to gather, analyze, and manage performance data for the elements in

your infrastructure. When you install the core eHealth software, you also install

the following supporting applications on Windows systems:

■ MKS NuTCRACKER 9.1 which supports scripting aspects of eHealth.

■ Oracle 10g database server for storing eHealth data.

■ Apache 2.2.11 web server for hosting the eHealth web user interface.


34/160

eHealth Installation


■ MKS XServer Version 8.1 for running X Windows processes and eHealth

commands. During the install you can choose to specify another supported X

server.

■ (Optional) Cognos 8 (Report Center).

To view reports from the eHealth console, you need a PDF viewer, such as Adobe

Reader. You can download the latest version of Adobe Reader software on the

Adobe website at http://www.adobe.com.

Note: If you experience problems during the installation, see Troubleshooting.

eHealth Installation Package

The eHealth r6.2 installation package includes the following media:

Name Contents

eHealth

Software DVD■

InstallPlus program. Use the InstallPlus software on this

DVD only if you cannot download the latest InstallPlus

program from the eHealth support website.

■ eHealth software and related applications including

Report Center and OneClick for eHealth.

■ The eHealth documentation.

Oracle

Software DVD■ Oracle Software.

■ Oracle update software. Use the Oracle update software

on this DVD only if you have not obtained the latestupdate from the eHealth support website.

CA eHealth

Without

Database DVD

■ eHealth software that does not support the installation

of Oracle. It also contains related applications.

■ The eHealth documentation.

You can download an ISO image (.ISO file) of the installation DVD instead of

receiving physical media. You must then burn the image file to a DVD that you

can use on a Windows system.


35/160

Start the eHealth Installation


System Security

When the installation program creates the eHealth database, it also changes the

passwords of the Oracle sys and system accounts to ehealth to maintain system

security. If you change these passwords, you must remember them and supplythem when necessary.

Important! You must use the nhManageUsers command when changing these

passwords. Otherwise, a password mismatch results.

Copy the DVDs to a Disk

You can save about an hour of time during the eHealth installation by copying the

installation media to a local disk. The installation media requires approximately

4 GB of disk space.

Note: Do not copy the installation media to a location that has spaces in the

directory name, such as the Windows Desktop. If you run the installation

program from a directory such as D:\eHealth Software, the installation fails.

Oracle 10g Software DVD

Because Oracle does not officially support installation over a network, copying

the installation media to the local system is preferable. Confirm that the target

system has at least 2 GB of free disk space.

Note: Throughout this guide, ehealth represents the full pathname of the

directory in which you are installing eHealth.


Run the installation program as the eHealth administrator.

If the installation program exits with a message that the Windows SNMP trap

service is running, the program cannot configure TrapEXPLODER because both

Windows SNMP trap service and TrapEXPLODER use port 162. You must either

disable the Windows SNMP trap service or configure TrapEXPLODER to use a

different port. For help, see the troubleshooting section TrapEXPLODER Unable

to Start.

If you encounter other problems with the installation, see the log file located in

ehealth/log/install/instehealth.log.


36/160



To start the eHealth installation program

1.

Log on to the Windows system as the eHealth administrator.

You must run the eHealth installation program as the eHealth administrator.

2.

Create a new temporary directory or partition with adequate space for the

InstallPlus files if you are using the InstallPlus software on DVD.

Do not use a directory path that contains spaces such as C:\Documents and

Settings\All Users\eHealth Install.

3.

Do one of the following to start the installation program, depending on the

source from which you are installing eHealth:

■ From DVD: Insert the eHealth Software DVD into the DVD drive.

Double-click setup.exe in the top-level DVD directory. The eHealth

Installation dialog opens. Click Browse; specify the new directory or

partition that you created in Step 2, and then click Next.

The program extracts InstallPlus files to the specified directory. The nexteHealth Installation Setup dialog appears.

■ From Disk: Navigate to the directory into which you extracted the

InstallPlus program files. Double-click setup.exe.

Note: If you have not downloaded and extracted the InstallPlus

program, see InstallPlus and Oracle Update Software.

The Setup dialog appears.

4.

(Optional) Select Start, Run from the Windows Desktop, and enter the

following if you have created an LCF to specify the layout of your eHealth

database:

InstPlusPath\setup -useLcf path\filename InstPlusPath

Represents the directory in which InstallPlus has been extracted (or the

letter of the DVD drive).

path\filename

Represents the full path to the LCF.

5.

Specify the location of the general release version of the eHealth software

that you are installing. Click Next.

The Installation Wizard appears.

6. View the License agreement. You must accept the agreement to install

eHealth.

7.

Review the eHealth Readme file which contains important information about

the current release of eHealth.


37/160



8.

Select the eHealth Installation Directory.

Specify a directory such as C:\ehealth62. Do not specify a top-level (or root)

directory (such as C:\ or D:\). Also, do not refer to a directory using the

Universal Naming Convention (UNC); instead, use a mapped drive.

Note: The default directory is ehealth.

9.

Enter the eHealth User Password; the password of the current user log on.

The installation program uses the password to configure the eHealth

services.

10.

Select the Date and Time Format.

This dialog appears only for English eHealth. French eHealth uses a 24-hour

time format, and Japanese eHealth uses a 12-hour time format.

11.

Select the X Server. Install MKS XServer or specify another supported X

server.

12.

Enter the Web Server Port.

The default port is 80. You can specify another port. If you select the default,

the program checks to see if the port is in use.

13. Select the Program Folder.

Note: The default folder is eHealth 6.2.

14. Do one of the following.

The program has different prompts, depending on which installation option

you are using:

■ eHealth Software DVD (installing eHealth with embedded Oracle)

Specify the directory where the Oracle software will be installed.

The default location follows Oracle conventions. Do not install Oracle in a

root directory such as C:\ or D:\. Also, do not refer to a directory by using

the Universal Naming Convention (UNC). Instead, use a mapped drive.

Note: The default directory is ehdrive:\oracle\Oracle.10.2

■ CA eHealth Without Database DVD (installing eHealth without

Oracle)

Specify the directory where the Oracle software is installed. Note that

Oracle must be installed on a local drive, and the path cannot contain

spaces.

The installer validates that a supported version of Oracle (10.2.0.3 or

10.2.0.4) and the required Oracle patches are installed at the specified

location.


38/160



15.

Specify the eHealth Database Name.

The eHealth database name must be eight characters or less, it must begin

with a letter, and it can consist of uppercase letters (A-Z) and numbers (0-9).

For example EHEALTH or EHDATA1. This value defines the ORACLE_SID

environment variable.

Note: The default database name is EHEALTH.

16.

Select the eHealth System Type:

■

A standard eHealth system polls statistic elements.

■ An eHealth Traffic Accountant system polls conversation elements

(probes).

■ A Distributed eHealth System is the polling back-end of a Distributed

eHealth cluster.

■

A Distributed eHealth Console is the reporting front-end of a Distributed

eHealth cluster.Note: If you choose the eHealth Traffic Accountant system, you are

prompted for the location of the LCF. After you supply this file, go to Step 23.

17.

Select Database Sizing Method.

If you are supplying an LCF, select Custom, and specify the LCF location.

Otherwise, select Typical.

18. Enter Database Sizing Information.

If you are configuring a Distributed eHealth Console system, enter the

number of elements that you plan to monitor in the cluster. The default is

500. Also, enter the number of days for which you will retain as-polled data.

The default is 3.Note: For guidelines, see the Distributed eHealth Administration Guide.

19. Enter the Number of Directories for the eHealth Database.

Follow the recommendations in the eHealth Sizing Wizard. At a minimum,

specify at least two, distinct local disk drives.

20.

Select Database Directories.

For best performance, specify only one directory on each disk or partition.

The directories that you specify for the eHealth database files must be

different from each other and different from the eHealth home directory.

For example, if you specified D:\eHealth62 as the eHealth home directory,

D:\database is a valid database directory, but D:\eHealth62\database isinvalid. Do not specify a location by using the Universal Naming Convention

(UNC); instead, use a mapped drive.

21.

Select Yes if you want to install Report Center.

Note: You can install Report Center later by rerunning the eHealth installer

or by using a manual procedure.


39/160



22.

Select offset time zone information.

Choose yes if your system will report on time zones that have a partial-hour

offset from GMT.

23.

Enter Mail Server.

You can leave the SMTP field blank and specify the SMTP server after the

installation finishes by setting the NH_NT_SMTP_SERVER environment

variable. If you do not know the name of your SMTP server, ask your system

administrator.

24.

Enter Printer Name.

You can leave the Share field blank and specify the printer after the

installation finishes by setting the NH_PRINTER environment variable.

25.

Install Oracle.

The program has different prompts, depending on the installation source:

■

Local disk: The program prompts you for the location of the Oracle Disk

directory.

■ DVD: The program prompts you to insert the Oracle DVD. After you

insert the DVD, it may take a few minutes for the Oracle installation to

begin. Accept the defaults.

Note: This prompt does not appear if you are installing the CA eHealth

Without Database kit.

26.

Update Oracle.

Specify the DVD or disk location of the Oracle update software used to

update the database.

Note: This prompt does not appear if you are installing the CA eHealthWithout Database kit. For instructions on how to install the Oracle update,

open the README text file located on the top level of the Oracle update

directory.

If you experience a failure during database creation and the installation

program stops, see Database Creation Is Incomplete before restarting the

installation program.

The installation program finishes the installation of eHealth and related

applications.

To complete the eHealth installation

1.

Complete the actions listed in the To Do List dialog, if it appears. Click Next.

The Installation Complete dialog appears.

2.

Select Yes, I want to restart my computer now (if it is not already selected)

and click Finish.

Note: You must restart your computer before running eHealth.


40/160



3.

Click Yes when the XServer Optimizer dialog appears.

This step optimizes the ability of the X server to render graphics.

The Server Optimization dialog appears and the program starts running.

After a few minutes, progress bars appear in all of the fields.

4. Click Close.

eHealth is successfully installed.

Additional Tasks

After eHealth is installed, you might need to perform the following tasks:

■ If you are planning to create a Distributed eHealth cluster, see the

Distributed eHealth Administration Guide for details.

■ If the target system will be a site in a remote polling environment, see the

eHealth Remote Poller User Guide.

■ Re-enable all antivirus programs that you disabled, except for McAfee 8.0,

which cannot run on the same system as eHealth r6.2.

■ If you copied the installation media to local disk directories, delete those

directories to free disk space.

■ You must install and configure the Distributed SNMPv3 Security Pack™

software (available from SNMP Research International) on your eHealth

system if you plan to discover and poll SNMPv3 elements.

Note: For more information, see the Distributed SNMP Security Pack Quick

Start Guide provided by SNMP Research.

■ Rename your old trapexploder.cf file and restart TrapEXPLODER to activate

the latest TrapEXPLODER features.

You can also enable LDAP authentication.

Note: The eHealth r6.2 services still use version number 6.1 (for example:

eHealth61, eHealth Httpd61, eHealth Tomcat61, and so on).


41/160

Start and License eHealth


How to Activate a New TrapEXPLODER Configuration File

When you install a new version of eHealth and TrapEXPLODER over an older

version, the previous trapexploder.cf file is not overwritten in order to preserve

the old configuration data. When eHealth starts up, the old configuration file isused and does not let you access the latest TrapEXPLODER features until you

save the old configuration file under a different name.

To activate the new features, follow this process:

1.

Shut down TraxEXPLODER.

2. Rename the trapexploder.cf file to trapexploder.cf.old.

3.

Restart TrapEXPLODER.

This activates the new features with a newtrapexploder.cf file while

preserving your old configuration file.


This section describes how to start eHealth, and specify and add license

information.

To start eHealth and open the eHealth console after installation

1.

Log on to your system as the eHealth administrator.

2.

Select Start, Programs, eHealth 6.2 from the Windows desktop.

The eHealth server starts. The eHealth console and OneClick for eHealth

open.

Add eHealth Licenses

eHealth offers a variety of monitoring and management solutions that require

specific licenses (for example, Traffic Accountant). Included with this release is a

30-day trial eHealth license. This means you can run eHealth, and discover and

poll elements for 30 days out of the box. After 30 days, if you have not purchased

permanent eHealth licenses, eHealth stops discovering and polling elements in

your environment. Be sure to complete all your license purchases before the

30-day trial license expires.

To obtain licenses and more information, log on to http://support.concord.com,

and click Licensing. After you place your request, you will receive your licenses

by email. You must then add the license information to your system.


42/160



To add eHealth licenses

1.

Enter the following commands to stop the eHealth server and the eHealth

license manager:

nhServer stopnhLmgr stop

2.

Open the license.dat file that resides in the ehealth/lmgr directory.

3. Copy and paste only the license keys from the email message into the file to

overwrite the existing entries.

Do not include the e-mail header information.

4.

Save and close the file.

You can add licenses at any time to extend your eHealth management

capabilities.

eHealth saves the license information and enables your access to eHealth

and all associated applications.

5.

Enter the following command to start the eHealth server and the eHealth

license manager:

nhServer start

The eHealth server starts and the license.dat file is read by the system. The

eHealth console and OneClick for eHealth open.

Note: Use OneClick for eHealth to find the network devices that you want to

poll and for which you want to run reports. For details about licensing and

polling, see the eHealth Administration Guide.

License File Example

The following is sample license information for 1000 standard poller licenses and

one LAN/WAN license:

# license.dat - license file for FLEX/lm license manager

# ...

# Key Type TotalExpiresCodeCksum

-----------------------------------------------

# PollerStandard1000never3B9E2051BBA40DD98A2F77

# LAN/WANStandard1never5BBE70611CDB9B4C5A9526

# ...


43/160

Install Report Center After eHealth is Installed


Install Report Center After eHealth is Installed

You can install Report Center on Windows after you have installed eHealth using

either of the following methods:

■ Automated – Uses the eHealth installer. This method automates the

process of installing Report Center but causes the eHealth servers to stop

during the installations of Report Center. This process can take anywhere

from 20 minutes to 3 hours, and eHealth servers will be down during this

time.

■ Manual – Uses a manual multi-step process on UNIX, which does not affect

the eHealth servers.

To install Report Center using the eHealth installer, rerun the eHealth installation

on the same server, point it at the same eHealth location, and answer yes when

asked whether you want to install Report Center.

Manual installations of Report Center require the additional step of copying

cndcReporting.zip to $NH_HOME\crn\deployment.

Where to Go from Here

After completing the installation, you need to perform the following

administration tasks before eHealth can begin to monitor your IT infrastructure:

■ Run the discover process to identify the devices that eHealth will monitor

■ Create groups and group lists to organize the elements that eHealth

discovers■ Schedule reports to monitor the status of your resources

■ Develop a database backup strategy to protect your data from unexpected

events

For the following information, see the eHealth Administration Guide and the

eHealth Overview Guide:

■ Descriptions of system administration tasks

■ A road map to follow to successfully administer your eHealth system

■ An overview of the eHealth interfaces that you use to administer the system


44/160


45/160

Chapter 4: Installing eHealth (UNIX) 45

Chapter 4: Installing eHealth (UNIX)

This chapter describes how to install the following:

■ eHealth r6.2 with embedded Oracle for the first time on a Solaris or HP-UX

system

■ eHealth r6.2 Without Database for the first time on a Solaris system only

The installation process takes about three hours to finish but can vary depending

on the speed of your system and disk devices. If you are installing eHealth with

embedded Oracle, you can save about an hour of time by copying the eHealth

and Oracle software installation media to a local disk. You may also have to

mount the DVD drive.

The installation program performs the following tasks:■

Installs the new release of eHealth and related applications

■ Installs Oracle 10g (if you are installing eHealth with embedded Oracle) or

prompts you for the location of your existing Oracle software (if you are

installin