IBM Platform Symphony 5.1 Interim Fix #233594 Readme File

Readme File

Abstract

The master host closes the scavenging host temporarily when the master host cannot get the "Scavenging Control" status from the scavenging host.

Description

The master host will close the scavenging host temporarily when it cannot get the "Scavenging Control" status. The master host then opens the scavenging host when the "Scavenging control" status is successfully reported from scavenging host. This issue is resolved by setting EGO_SCAVENGINGCONTROL_CLOSE_UNAVAILABLE_HOST=Y in the ego.conf file.


This interim fix applies only to the following platform:

Windows 64-bit

Readme file for: IBM® Platform Symphony

Product/Component Release: 5.1

Update Name: Interim Fix #233594

Fix ID: sym-5.1-build233594-socgen

Publication date: 28 April 2014

Last modified date: 28 April 2014

Contents

1. List of fixes

2. Download location

3. Products or components affected

4. System requirements

5. Installation and configuration

6. List of files

7. Copyright and trademark information

1.    List of fixes

SUP_BY_SYM#229834

2.    Download location

Download Fix #233594 from the following location:

http://www.ibm.com/eserver/support/fixes/

3.    Products or components affected

Product/Component Name, Platform, Fix ID:

Platform Symphony/vemkd, Windows 64-bit, sym-5.1-build233594-socgen

4.    System requirements

Not applicable.

5.    Installation and configuration

5.1   Before installation

               1. Disable all applications and shutdown the cluster.

    Log on to the master host as the cluster administrator and run:

C:\>soamcontrol app disable all

C:\>egosh service stop all

C:\>egosh ego shutdown all

5.2   Installation steps

Copy the appropriate Symphony MSP packages of ego1.2.5_win-x64-233594.msp to each management host.

·    Interactive installation:

Double-click the Symphony MSP package to run the Symphony installer.

For example, download and install ego1.2.5_win-x64-233594.msp.

·    Silent installation:

Run the Symphony patch installers from the command line using the following commands:

C:\>msiexec /update <Symphony_package_name_path> /l*v <symphony_install_log> /norestart /quiet REINSTALLMODE=omus

Where:

· Symphony_package_name_path is the fully qualified filename of the Symphony MSP package in this release.

· symphony_install_log is the log file for the Symphony upgrade.

For example, run the following commands:

C:\>msiexec /update C:\ego1.2.5_win-x64-233594.msp /l*v updateSym.log /norestart /quiet REINSTALLMODE=omus

5.3   After installation

               1. Verify the installation.

The following is an example output:

 

C:\EGO\1.2.5\bin>vemkd -V

Platform EGO 1.2.5.233594, April 23 2014

Copyright Platform Computing Inc., an IBM company, 1996-2009, 2012.

 

binary type: win2003-x64

notes:

fixes:

               2. Enable the configuration.

Configure the parameter in ego.conf:

EGO_SCAVENGINGCONTROL_CLOSE_UNAVAILABLE_HOST=Y

               3. Start the cluster and enable the application.

Log on to the master host as the cluster administrator and run:

C:\>egosh ego start all

C:\>soamcontrol app enable <appName>

5.4   Uninstallation

               1. Disable all applications and shutdown the cluster.

    Log on to the master host as the cluster administrator and run:

C:\>soamcontrol app disable all

C:\>egosh service stop all

C:\>egosh ego shutdown all

               2. Uninstall the interim fix.

       Important:

You cannot use the Microsoft Windows "Add/Remove Programs" feature to roll back to a previous Symphony package on a management/compute host.

a.)      Get the Symphony package for Symphony 5.1 (for example, ego1.2.5_win-x64.msi in this case).

b.)      Use the following command to roll back Symphony:

C:\>msiexec /uninstall <Sym_SP_path> /package <Sym_5.1_path> /norestart /quiet /l*v <sym_rollback_log>

 Where:

1) Sym_SP_path is the fully qualified filename of the Symphony MSP package in this release.

2) Sym_5.1_path is the fully qualified filename of the Symphony 5.1 msi package.

3) sym_rollback_log is the log file for the Symphony rollback.

3. Roll back the configuration.

Remove the parameter from ego.conf:

EGO_SCAVENGINGCONTROL_CLOSE_UNAVAILABLE_HOST=Y

4. Start the cluster and enable application.

Log on to the master host as the cluster administrator and run:

C:\>egosh ego start all

C:\>soamcontrol app enable <appName>

6.    List of files

vemkd.exe

vemkd.pdb

7.    Copyright and trademark information

© Copyright IBM Corporation 2014

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM®, the IBM logo and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.