Installation Guide October 2006

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®) This guide describes how to upgrade eHealth® Release 5.6.5 or 5.7 to eHealth Release 6.0 on a Windows® system. If you have an eHealth 5.0.2 system, you must migrate it to eHealth 5.6.5/5.7 before upgrading it to eHealth 6.0. The upgrade process includes an update of the Oracle® database from Oracle 9.2.0.3 to Oracle 9.2.0.7. You must install eHealth 6.0 in a new directory on the existing eHealth system. This requirement is necessary to minimize downtime and data loss.

Upgrade Overview The upgrade process consumes two to three hours, depending on the speed of your system and devices. To save time during the upgrade process, copy the eHealth InstallPlus CD, eHealth Software CD, and Oracle Upgrade CD to a local directory. If you experience problems during the upgrade, see the section Troubleshoot Upgrade Problems. The upgrade program performs the following tasks: •

Installs the new release of eHealth in a directory that is different from the location of eHealth 5.6.5/5.7

•

Copies configuration information and customized files to the new eHealth location

•

Updates the version of the Oracle software

•

Converts the database to the eHealth 6.0 schema

Guidelines for Upgrade To avoid problems during the eHealth upgrade, follow these guidelines: •

Confirm the current release of eHealth is polling and running reports without errors.

•

As a best practice, upgrade Oracle as a separate process before you upgrade eHealth. For more information, see the section Upgrade Oracle before You Upgrade eHealth.

•

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.

•

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 Database Management Guide.

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®)

Remote Poller Upgrade Guidelines •

If your eHealth systems are remote polling sites, and they run eHealth 5.6.5, they must have eHealth 5.6.5 Patch 3 or later installed before upgrading to eHealth 6.0.

•

If your sites are running a version of eHealth earlier than 5.6.5 Patch 3, update to eHealth 5.6.5 Patch 8 before upgrading to eHealth 6.0. If you are running eHealth 5.0.2, you must migrate to eHealth 5.7 before upgrading to eHealth 6.0.

•

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 6.0: – 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. To run this command you must be upgrading from eHealth 5.7. If you are upgrading from eHealth 5.6.5, contact Technical Support for assistance. – On the central site, disable import polling from the remote sites. – Upgrade the central site to eHealth 6.0. – Enable import remote polling on the central site. – Disable one remote site at a time, upgrade the site to eHealth 6.0, and then re-enable the site. This ensures that all but one site is enabled at a time.

Software Location Guidelines When choosing a location for the eHealth software, follow these guidelines: •

Specify a local disk or a disk partition.

•

Specify a top-level directory or subdirectory, such as D:\ehealth60.

•

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 you can resolve the issue.

•

Do not specify a root directory (such as D:\).

•

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.

Support for Japanese and French eHealth The eHealth installation program automatically detects the language of the operating system and installs the appropriate files. Japanese Guidelines

The Japanese character set uses different encoding on the Windows and Solaris platforms. On Windows, Japanese eHealth uses Shift-JIS (Japanese Industrial Standard) encoding. On Solaris, Japanese eHealth uses Extended UNIX Code (EUC) encoding. Because Japanese eHealth is encoded differently on each platform, you cannot perform the following tasks: •

Create a Distributed eHealth cluster that contains both Windows and UNIX systems. (You can create clusters that contain all Windows or all UNIX systems.)

•

Transfer a Japanese version of the eHealth database between a Solaris system and a Windows system. 2

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®) French Guidelines

The SCO X Server (XVision) supplied with French eHealth does not allow you to enter accented characters using the compose keyboard sequence. However, French eHealth allows you to type the character ecircumflex (ê) by using the AltGr+E key combination.

Prerequisites Checklist Use the following checklist to ensure that you properly prepare the system on which you plan to upgrade eHealth: 1. Determine your system resources:

'

Use the eHealth sizing wizard to determine system hardware requirements and verify that your system meets them. On the target system, connect to http://support.concord.com, and click eHealth Sizing Wizard.

'

If you plan to install Report Center (an application that allows you to create and run custom reports for eHealth elements), your target system will need additional disk space. Use the eHealth sizing wizard to estimate the additional disk space needed on your target system. In general, this additional disk space is equal to 50 percent of the current database. Also, if you plan to poll a large number of elements (approximately 50K 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 ensure that NH_TEMP resides on a disk that has sufficient space for it to grow before installing Report Center. Install Report Center only after the eHealth 6.0 upgrade is successfully completed. See the eHealth Report Center Installation and Administration Guide for further disk space guidelines.

2. Verify that your system meets the following basic platform requirements:

'

Operating system: Windows 2003 Server (Standard or Enterprise Editions). For supported service pack levels, see the eHealth Readme file. If you must upgrade the operating system, do so before starting the eHealth upgrade.

'

File system format: NT file system (NTFS).

'

If you plan to access the eHealth web user interface from the eHealth system, one of the following web browsers is required, with JavaScript enabled: Internet Explorer Version 6.0, Mozilla Version 1.6, or Firefox/Mozilla 1.x.

3. Prepare for the eHealth upgrade:

'

Identify a location for the eHealth Release 6.0 software that has at least 2 GB of additional 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 or the eHealth web user interface, and cannot run scheduled reports.

3

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®)

Standard eHealth Upgrades In a typical eHealth environment (monitoring 50,000 elements or less), you will encounter up to the following: •

Data loss: One hour 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 hour.

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 6.0, in addition to the data loss that occurs during the eHealth upgrade process. The central site will also show these slight data gaps in reports. Note: If you are upgrading to eHealth 6.0 in a Distributed eHealth environment, when running the Oracle upgrade, the cluster system may experience more than 30 minutes of data loss and approximately 1 hour of server downtime, depending on the size and speed of your system. During this time, the cluster member being upgraded will be unavailable. To avoid additional downtime/data loss during the eHealth 6.0 upgrade process, you should first run the Oracle Upgrade CD.

Merging Groups and Group Lists Groups of elements are used for many purposes in eHealth, including reporting, security, and assigning Live Health profiles. In previous releases of eHealth, 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. In eHealth Release 6.0, groups are now universal; you can place elements of any type into the same group. This eases group maintenance.

Security When you upgrade to eHealth 6.0, 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. 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 Mary does not have rights to view LAN/WAN elements. To avoid the group merge, rename the groups to have unique names before you upgrade.

Conversion Check Before you upgrade to eHealth 6.0 from eHealth 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 due to 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. 4

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®)

Note: If you are upgrading from eHealth 5.6.5, contact Technical Support. To run the conversion check on a central site, insert the eHealth Software CD 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. If the issues cannot be easily resolved, Technical Support may advise you to wait until eHealth Release 6.0 Service Pack 1 to upgrade your remote polling systems.

InstallPlus and the Oracle Upgrade Software To ensure that you receive the current security patches and fixes, CA recommends downloading the InstallPlus and Oracle Upgrade software from the eHealth support website instead of using the CDs that you received in the eHealth package.

InstallPlus Program InstallPlus is an eHealth program that reduces downtime by installing all of the latest fixes and certifications in one procedure. To ensure that you install the latest available software when you install eHealth 6.0, 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 CD or disk image.

•

Installs the general release eHealth software plus the additional 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 first time, 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.

5

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®) To download 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 eHealth InstallPlus CD in the eHealth installation package. The File Download dialog appears.

2.

Download the file to your eHealth system and save it in a new, empty directory. Ensure you have at least 350 MB of disk space available for the InstallPlus software. 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 in a new directory. Note: For the InstallPlus program to execute successfully, you must placed it in a new directory.

3.

Double-click the LAN_release_WIN_splevel_PLUS.exe file to extract the InstallPlus files into the current working directory. ENU represents the supported language, either English (ENU), French (FRA), or Japanese (JPN); release represents the release number, such as 600 for eHealth 6.0; and splevel represents the service pack release level, such as 00. The InstallPlus files are extracted into the current directory.

Oracle Upgrade Software The Oracle Upgrade software contains security patches and other patch sets and fixes for the eHealth database software. The eHealth Readme file includes a list of services you must stop on the target system to ensure that the Oracle software is upgraded successfully. Note: You must contact eHealth Technical Support at http://support.concord.com to request the latest Oracle Upgrade software for the language and release that you want. Use the Oracle Upgrade CD in the eHealth installation package only if you cannot access the Oracle upgrade from Technical Support. To download the Oracle Upgrade software 1.

Download the file to your eHealth system and save it in a new, empty directory that meets the size requirements determined by the sizing wizard. 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.

Double-click the ORA_WIN_VER.zip file to extract the Oracle Upgrade patch set file into the current working directory, where VER represents the database release patch level, such as 9207. The Oracle Upgrade software file is extracted into the current directory.

Upgrade Oracle before You Upgrade eHealth As a best practice, you should upgrade the Oracle database software before upgrading eHealth to accomplish the following: •

Record the application downtime for the eHealth upgrade and Oracle upgrade separately. Consider running the Oracle upgrade during scheduled system maintenance.

•

Reduce data loss.

•

Apply the database security patches as soon as possible.

6

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®)

eHealth Installation Before you begin the installation process, you may want to copy the contents of the CDs to a disk if the eHealth system does not have a local CD drive, or if you want to avoid changing CDs during installation.

eHealth Installation Package Ensure that you have the appropriate media for the eHealth 6.0 release: Name

Contents

eHealth InstallPlus CD

The eHealth InstallPlus program. Use this CD only if you cannot download the latest InstallPlus program from the eHealth support website.

eHealth Software CD

The eHealth software and related applications.

Report Center CD

The Report Center software. Install Report Center only after you have successfully installed eHealth 6.0.

Oracle Upgrade CD

The Oracle Upgrade software. Use this CD only if you cannot download the latest Oracle Upgrade software from the eHealth support website.

TotalDoc CD

All eHealth 6.0 documentation.

eHealth 6.0 Readme File

Important information about the current release of eHealth.

Note: eHealth upgrades use only the Oracle Upgrade CD, not the Oracle 9i Software CDs. Copy the contents of the CDs To reduce the time spent changing CDs you can copy the CDs to a local disk drive. The CDs require approximately 2 GB of disk space. Note: Do not copy the CDs 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:\60 Software, the installation fails.

Start the eHealth Installation Run the installation program as the eHealth administrator. Throughout this guide, ehealth_new represents the full pathname of the directory in which you are installing eHealth 6.0, and ehealth_old is the directory in which you installed eHealth 5.6.5/5.7. To start the eHealth installation 1.

Log on to the Windows system as the eHealth administrator. You must run the eHealth installation program as the eHealth administrator.

2.

If you are using the eHealth InstallPlus CD, create a new directory or partition with adequate space for the InstallPlus files. Do not use a directory path that contains spaces such as C:\Documents and Settings\All Users\eHealthInstall.

3.

Do one of the following, depending on the source from which you are installing eHealth: •

From CD: Insert the eHealth InstallPlus CD into the CD drive. Double-click setup.exe in the top-level CD directory. A Setup dialog opens. Click Browse, specify the new directory or partition that you created in Step 2, and click Next. The program extracts InstallPlus files to the specified directory. The next Setup dialog appears.

•

From Disk: Navigate to the directory into which you extracted the InstallPlus program files. Double-click setup.exe.

The Setup dialog appears. 7

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®) 4.

Specify the location of the general release version of the eHealth software that you are installing. Click Next. A dialog appears explaining when the installation program checks your database software for possible upgrades.

5.

6.

Select one of the following: •

Click No to exit the program and reschedule this task.

•

Click Yes to continue the installation. The installation program checks the system, and then starts the eHealth Installation Wizard.

The following dialogs prompt you for information:

Dialog

Guidelines

Appears in Typical Installation

Appears in Traffic Accountant Installation

View License Agreement

You must accept the agreement to install eHealth.

√

√

View Readme

Review the Readme file which contains important information about the current release of eHealth and your system requirements.

√

√

Select eHealth Installation Directory

Specify a new directory, such as C:\ehealth60. Do not specify a top-level (or root) directory (such as C:\ or D:\). Also, do not specify a directory using the Universal Naming Convention (UNC); instead, use a mapped drive.

√

√

Enter eHealth Password

The installation program uses the password to configure the eHealth services.

√

√

Select Date and Time Format

This dialog only appears for English eHealth. French eHealth uses a 24-hour time format and Japanese eHealth uses a 12-hour time format.

√

√

Enter Web Server Port

The default is the current web port.

√

√

Select Program Folder

The default is eHealth 6.0.

√

√

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.

√

√

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.

√

√

Confirm Installation

Click Next to begin the eHealth installation.

√

√

Oracle Upgrade

Specify the CD or disk location of the Oracle Upgrade software used to update the database.

√

√

CD Install Only: When the update is finished, insert the eHealth Software CD. The installation process continues.

8

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®)

Complete the eHealth Installation The installation program finishes the installation of eHealth and related applications. If you must or should perform any actions before running eHealth, the installation program displays the To Do List dialog. To complete the eHealth installation 1.

If the To Do List dialog appears, complete the actions listed.

2.

Click Next in the To Do List dialog. The Installation Complete dialog appears.

3.

The eHealth activation process starts. (If you are working in a cluster environment, see the section Activate a Distributed eHealth Cluster.) A window appears showing the progress of the eHealth activation. The system reboots after activation completes.

4.

From the Windows desktop select Start, Programs, eHealth 6.0. The eHealth console opens.

5.

Run reports to confirm that eHealth is polling and running report normally. After a few days of proper function, perform the Finalize Upgrade procedure.

Additional Tasks After you have successfully upgraded your system to eHealth 6.0, perform these tasks to ensure eHealth 6.0 operates properly.

Activate a Distributed eHealth Cluster After you have installed eHealth 6.0 on all cluster members, you must activate the software across the cluster from a single trusted cluster member. Note: Perform this step on the trusted system only. Do not perform this step on each cluster member. Trusted System A trusted system is an eHealth system in a Distributed eHealth cluster that can issue commands (such as nhRunCommand and nhPutFile) to modify the configuration and operation of other systems in the cluster. The trusted member that you select can be a Distributed eHealth System or a Distributed eHealth Console. When you run the nhUpgradeCluster -activate command from this system to activate eHealth 6.0 on all cluster members, the command establishes the trusted system as the controller system for the cluster upgrade process. To activate eHealth 6.0 on all systems in a cluster

Note: The eHealth 5.6.5/5.7 environment is no longer active after eHealth 6.0 is activated. 1.

Log on as the eHealth administrator and open a new command prompt window.

2.

Change to the ehealth_old\bin directory: cd /d ehealth_old\bin

The directory is changed. 3.

Confirm that all cluster member systems are running by entering the following command: nhListClusterMembers -all

Cluster member output appears. Examine the output and ensure that all cluster members are responding with information.

9

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®) 4.

Enter the following command to activate eHealth 6.0 on all cluster members: nhUpgradeCluster -activate

The following prompt appears: This command will run the requested cluster upgrade action on every member in the cluster. Press Ctrl-C to stop, or any other key to continue.

Note: If the nhUpgradeCluster -activate command encounters errors during some of these operations, it rolls back the software to Release 5.6.5/5.7 and issues messages to this effect. 5.

At the prompt, press Return. The nhUpgradeCluster -activate command performs the following processes (some, such as database conversion, require approximately one hour to complete, depending on the size of your database): •

Establishes the current system as the controller system: you must run all subsequent cluster upgrade commands from this system

•

Confirms the ability to communicate with other clustered systems

•

Checks that all cluster members have the eHealth 6.0 software installed and are ready for activation

•

Places all clustered systems in a mode that prevents configuration changes

•

Stops eHealth 5.6.5/5.7 servers

•

Converts the database to use the eHealth 6.0 schema

•

Recreates the eHealth 5.6.5/5.7 configuration in the eHealth 6.0 environment

•

Starts eHealth 6.0 servers

•

Restores all clustered systems to a mode that allows configuration changes

•

Confirms that eHealth 6.0 has started on all systems in the cluster

•

Reboots each Windows system in the cluster

The activation process completes, with all cluster members running eHealth 6.0. The file records the activation of the eHealth cluster upgrade.

ehealth_old\log\runSwitchLocal.log

Finalize Upgrade After a few days, when you have run reports and confirmed that the upgrade to eHealth 6.0 was successful in your environment, finalize the installation changes. To finalize the installation changes 1.

On the eHealth system, open a terminal window and log on as the eHealth administrator.

2.

Enter the following command: nhConvertDb -finalize

Note: During this process, eHealth disables (drops) the database tables that support rolling back to eHealth 5.6.5/5.7. Do not remove eHealth 5.6.5/5.7 until you are sure that eHealth 6.0 is running successfully. This command may take 5 to 15 minutes to complete. To follow the progress of the command, see the log file, ehealth_new\log\convert_finalize_date.time.log, where date and time represent the date and time that the conversion occurred.

10

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®)

Cleanup Tasks To ensure the best performance of your eHealth 6.0 system, complete the following tasks: •

Check scheduled jobs to confirm the accuracy of pathnames and file locations.

•

If you stopped or disabled any nhConfig jobs for eHealth integration modules, enable those jobs.

•

If you use Application Response (AR), upgrade AR agents and check ehealth_new/log/install/ ARUpgrade.log for messages that application rule sets have changed. (If you monitor custom applications, the rules carry over during an upgrade, but if you monitor default applications, the rules may change.) Consider incorporating the changes into the ehealth_new/data/response/Rules.ard file. If you are not familiar with BT Studio and the process of customizing rule sets, consult with Technical Support for assistance.

•

If you currently use any other agents to monitor eHealth, upgrade the agents (if needed) to a version supported by eHealth 6.0. For more information, see the device certification web page at http://support.concord.com/devices.

•

For upgrades from eHealth 5.6.5 only: If you copied MTFs to create custom element types, you may need to add the fullDuplex attribute to certain MTFs. For more information, see the section Cleanup Task for Customized MTFs.

•

Inform Live Health users to upgrade their Live Health client software.

•

If you have created Live Exceptions Notifier rules to run scripts that are specified by hard-coded paths relative to the previous release of eHealth, move the scripts to the eHealth 6.0 home directory and update those rules.

•

Authorize eHealth web users to use new functions of the eHealth user web interface, as appropriate.

•

(Optional) After eHealth 6.0 is polling normally and reports run well for a few days, remove the previous release of eHealth to regain disk space. For instructions, see the Removing eHealth 6.0 (Windows) guide.

•

If you copied the installation CDs to local disk directories, delete those directories to free disk space. Also, delete any InstallPlus files that were extracted to your system.

•

If you plan to discover and poll SNMPv3 elements, you must install and configure the Distributed SNMPv3 Security Pack™ software (available from SNMP Research International) on your eHealth system. For more information, see the product documentation.

Cleanup Task for Customized MTFs If you are upgrading from 5.6.5 to 6.0, and you have copied MTFs to create customized element types, you may need to edit your custom MTFs to add the fullDuplex attribute. Set the attribute to yes or no, as appropriate. You can add the fullDuplex attribute at any time to your custom MTFs; until you do so, however, related data in eHealth reports may not be accurate. To add the fullDuplex attribute to a customized MTF 1.

Open a terminal window. Enter the following commands to view the list of MTFs that have been updated to include the fullDuplex attribute: cd ehealth_new/poller grep fullDuplex *.mtf

The MTF list appears.

11

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®) 2.

Note any MTFs that contain fullDuplex and that you copied to create customized element types in release 5.6.5. Edit each of your customized MTFs to add the fullDuplex attribute in the Support section of the MTF. The fullDuplex attribute is added to the MTF. Example: Suppose that for eHealth 5.6.5 you customized sonoma-enet-port.mtf and renamed it my-sonoma-enetport.mtf. In eHealth 5.7, the fullDuplex attribute was added to sonoma-enet-port.mtf, so you must add the fullDuplex attribute to the Support section of my-sonoma-enet-port.mtf after you upgrade to eHealth 6.0. The following is an example of the my-sonoma-enet-port.mtf after adding fullDuplex: mib sonoma.mib { file sonoma.mib version 2 agent "Sonoma Ethernet Agent" elementType ethernetIf

fullDuplex no translation { mediaSpeed = ifSpeed% operStatus = ifOperStatus% operStatusLastChange = ifLastChange%

Troubleshoot Upgrade Problems This section provides troubleshooting information for problems that you may encounter during the eHealth upgrade process.

Installation Program Exits During Activation Symptom •

In some cases, the installation program rolls the software on that system back to Release 5.6.5/5.7, displaying messages to that effect.

•

In other cases, messages instruct you to perform cleanup tasks before trying the installation again.

Solution 1.

Correct the problem that generated the error. For example, if the installation program indicates insufficient disk space, make additional disk space available before resuming the installation process.

2.

Restart the eHealth installation program. The installation program is designed to skip time-consuming steps that it has already completed successfully.

eHealth Upgrade to 6.0 Is Unsuccessful on a Cluster Member Symptom The upgrade to eHealth 6.0 was not successful on a cluster member. Solution Restore (roll back to) eHealth 5.6.5/5.7 on the local system or on all cluster members. This minimizes data loss because you can troubleshoot the upgrade problems while eHealth 5.6.5/5.7 continues to collect and report on data. Note: eHealth 5.6.5/5.7 cannot be restored once you complete the Finalize Upgrade procedure. Rollback Downtime. During the rollback process, eHealth experiences downtime from the time that the eHealth 6.0 services stop to the time that the eHealth 5.6.5/5.7 services start. On Windows systems, the 12

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®)

rollback process also requires a system reboot. When possible, roll back an individual cluster member rather than the entire cluster, so that eHealth experiences downtime on that system only. If you roll back all cluster members, eHealth experiences more downtime. Important! If you discovered new elements using eHealth 6.0, that information is lost when you roll back to eHealth 5.6.5/5.7.

To restore eHealth 5.6.5/5.7, do the following: a.

Remove systems from the cluster.

Restore eHealth 5.6.5/5.7 on the system or across the cluster. c. Activate eHealth 6.0 after resolving upgrade problems. b.

Remove a System from the Cluster If you plan to restore eHealth 5.6.5/5.7 on one member of the cluster, leaving the rest of the cluster on eHealth 6.0, consider removing that system from the cluster first. In either case, after you roll back the system to eHealth 5.6.5/5.7, you will be able to use eHealth to run reports for that system locally. You may want to remove the system from the cluster if your organization cannot tolerate the errors or if you expect that you will not be able to reactivate eHealth 6.0 on that system soon. If you do not remove the system from the cluster before rolling it back to eHealth 5.6.5/5.7, expect the following results: •

Reports run from a 6.0 Distributed eHealth Console do not include information about elements or groups managed by the eHealth 5.6.5/5.7 system.

•

If you use a 6.0 Distributed eHealth Console to run an element-specific report for an element managed by the eHealth 5.6.5/5.7 system, the report fails.

•

Some scheduled jobs, such as the Synchronize job, generate errors concerning that system.

Leaving the system in the cluster may be acceptable if you plan to reactivate eHealth 6.0 on that system after resolving any issues, and if report and job errors do not pose a problem. If you remove the system from the cluster before rolling back to eHealth 5.6.5/5.7, expect the following results: •

Scheduled jobs and reports do not generate errors regarding that cluster member.

•

Reports run from a 6.0 Distributed eHealth Console do not include information about elements or groups managed by the eHealth 5.6.5/5.7 system that was removed.

To remove the system from the cluster

To remove the system from the member tables of all systems in the Distributed eHealth cluster (including the one on which you run the command), run the following command on one of the cluster members on which eHealth 6.0 is operating: nhRemoveClusterMember -all -name hostname

For more information about removing a cluster member and how to use the nhRemoveClusterMember command and its arguments, see the Distributed eHealth Administration Guide. Also, see that guide for information on how to restore the member to the cluster with the nhRestoreClusterMember command after reactivating eHealth 6.0.

13

Upgrading eHealth® 5.6.5 or 5.7 to eHealth 6.0 (Windows®)

Restore eHealth 5.6.5/5.7 on the System Use the following procedure to restore eHealth 5.6.5/5.7 on a local Windows system. To restore eHealth 5.6.5/5.7 on the Windows system 1.

Log on as the eHealth administrator and open a new command prompt window and restore eHealth 5.6.5/ 5.7 on the local system by entering the following command: nhUpgradeCluster -rollback -local

This command performs the following actions: •

Stops eHealth 6.0 services.

•

Converts the database.

•

Recreates the eHealth 5.6.5/5.7 configuration.

•

Reboots the system.

•

Starts eHealth 5.6.5/5.7 services, including the web server.

Some of these steps, such as restarting servers and rebooting the system, can take several minutes to complete. eHealth 5.6.5/5.7 is restored on the system. 2.

Close all command prompt windows that use eHealth 6.0 environment variables. After restoring eHealth 5.6.5/5.7, you cannot run eHealth commands in those windows. After you resolve the issue that prevented a successful upgrade, and are ready to reactivate eHealth 6.0, see the section Activate eHealth 6.0 after a 5.6.5/5.7 Rollback for instructions.

Restore eHealth 5.6.5/5.7 across the Cluster Use the following procedure to restore eHealth 5.6.5/5.7 on all cluster members. To restore eHealth 5.6.5/5.7 across the cluster 1.

On the trusted system from which you issued the nhUpgradeCluster -activate command, log on as the eHealth administrator. Open a new command prompt window. This ensures that you are using the eHealth 6.0 environment.

2.

Restore eHealth 5.6.5/5.7 on all systems in the cluster by entering the following command: nhUpgradeCluster -rollback

This command performs the following actions on every system in the cluster: •

Stops eHealth 6.0 services

•

Converts the database

•

Recreates the eHealth 5.6.5/5.7 configuration

•

Reboots the Windows systems in the cluster

•

Starts eHealth 5.6.5/5.7 services, including the web server

Some of these steps, such as restarting servers, can take several minutes to complete. Upon successful completion of the rollback process, all Windows systems in the cluster will reboot, and all cluster members will be running eHealth 5.6.5/5.7. 3.

Close all command prompt windows that use eHealth 6.0 environment variables. After restoring eHealth 5.6.5/5.7, you cannot run eHealth release 6.0 commands in those windows.

14

Upgrading eHealth 5.6.5 or 5.7 to eHealth 6.0 (Windows)

Activate eHealth 6.0 after a 5.6.5/5.7 Rollback After you resolve the issues that caused activation errors, reactivate eHealth 6.0 on all cluster members or a local system, then continue the upgrade process. For further information, see the Distributed eHealth Administration Guide. To reactivate eHealth 6.0 on all cluster members 1.

On the trusted system that you used to roll back the upgrade, log on as the eHealth administrator and open a command prompt window.

2.

Enter the following command to activate eHealth 6.0 on all members of the Distributed eHealth cluster: nhUpgradeCluster -activate

This command also confirms that eHealth 6.0 is running on all members of the cluster. However, if you need to perform this validation step manually, use the following command: nhUpgradeCluster -validate

The systems reboot, and eHealth 6.0 is reactivated on all cluster members. To reactivate eHealth 6.0 on a local system 1.

On the system to be reactivated, log on as the eHealth administrator and open a command prompt window.

2.

Enter the following command: nhUpgradeCluster -activate -local

Note: If you issue this command from a trusted system that was removed from a cluster, the command indicates the status of eHealth on all systems in the cluster, even though the activation process occurs only on the local system. 3.

To confirm that eHealth 6.0 is running on the local system, enter the following command: nhUpgradeCluster -validate -local

4.

Restore the system if you removed it from the cluster by using the following command: nhRestoreClusterMember

The system reboots, and eHealth 6.0 is reactivated on the local system.

More Information All eHealth documentation is available in PDF format in the eHealth Web Help and on the eHealth support website. For more information regarding eHealth administration, see the following guides: •

eHealth Installation Administration Tasks Reference (Windows)

•

Removing eHealth 6.0 (Windows)

For the following information, see the eHealth Administration Overview guide: •

Descriptions of system administration tasks

•

A roadmap to follow to successfully administer your eHealth system

•

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

Copyright © 2006 CA. All rights reserved. 15