IBM Platform Cluster Manager Advanced Edition 4.1 Fix 230291 Readme File
Abstract
Fix 230291 provides enhancements to Windows VM support.
Description
Readme documentation for IBM Platform Cluster Manager Advanced Edition Fix 230291 including installation-related instructions.
IBM Platform Cluster Manager Advanced Edition 4.1 supports Windows VM. Fix 230291 addresses the following issues related to Windows VM:
1. Windows VM provisioning fails due to an internal failure.
2. Windows VM does not assign an IP address after it is provisioned.3. Windows VM does not get resource data after installing LSF on Windows.Applying this fix fixes the issues listed above.
Readme file for: IBM Platform Cluster Manager Advanced Edition
Product/Component Release: 4.1
Update Name: Fix 230291
Fix ID: pcmae-4.1-build230291-dagang
Publication date: 25 March 2014
Last modified date: 25 March 2014
Contents:
1. Download location
2. Products or components affected
3. System requirements
4. Installation and configuration
5. List of files
6. Copyright and trademark information
1. Download Location
Download Fix 230291 from the following location: http://www.ibm.com/eserver/support/fixes/
2. Products or components affected
Affected components include: ICM, API, and VMTools for Windows
3. System requirements
3.1 Software requirements
Red Hat Enterprise Linux (RHEL) 6.3 x86_64
3.2 Hardware requirements
IBM System x3650 M3
IBM System x iDataPlex dx360 M3
IBM System x iDataPlex dx360 M4
4. Installation prerequisites
Make sure that you install the prerequisite fixes in the order specified before installing this fix.
Product/Component Name: |
Platform: |
File: |
Platform Cluster Manager Advanced Edition 4.1 Fix 213575 |
Red Hat Enterprise Linux (RHEL) 6.3 x86_64 |
|
Platform Cluster Manager Advanced Edition 4.1 Fix 217270 |
Red Hat Enterprise Linux (RHEL) 6.3 x86_64 |
|
Platform Cluster Manager Advanced Edition 4.1 Fix 215584 |
Red Hat Enterprise Linux (RHEL) 6.3 x86_64 |
|
Platform Cluster Manager Advanced Edition 4.1 Fix 225475 |
Red Hat Enterprise Linux (RHEL) 6.3 x86_64 |
5. Installation and configuration
5.1 Before installation
1. Log in to the Platform Cluster Manager Advanced Edition management server as root.
2. Source the environment for the previous Platform Cluster Manager Advanced Edition installation.
- C shell: # source <PCMAE_TOP>/cshrc.platform
- Bourne shell: # . <PCMAE_TOP>/profile.platform
- Where <PCMAE_TOP> is the top-level directory where the Platform Cluster Manager Advanced Edition is installed (for example, /opt/platform).
3.
Log on to EGO as a Platform Cluster Manager Advanced Edition administrator.If your Platform Cluster Manager Advanced Edition management server
integrated with LDAP or PAM plug-in, log into Platform Cluster Manager Advanced Edition using the password of the LDAP or PAM user
mapped to the Platform Cluster Manager Advanced Edition administrator user Admin.
# egosh user logon -u Admin -x Admin
4. Shut down all EGO services.
# egosh service stop all
5.2 Installation steps
1. Extract the fix tar archive on the management node:
# tar -xvf PCMAE41Fix230291.tar
2. Install the fix from the extracted directory(PCMAE41Fix230291):
# ./install.sh apply
5.3 After installation
1. Start all EGO services.
# egosh service start all
2. Refer to the Administering Platform Cluster Manager Advanced Edition guide to do following:
- Install Windows VMs using new VMTools and convert it to provision template;
- Modify the OS template in the machine layer to use the new Windows VMs template, then publish it for use;
- Set up cluster with new published cluster definition.
Note: After applying this fix, internal scripts can stop working on a Windows VM. This includes any internal scripts, such as LDAP or GPFS scripts.
5.4 Uninstallation
1. Log in to the Platform Cluster Manager Advanced Edition management server as root.
2. Source the environment for the previous Platform Cluster Manager Advanced Edition installation.
- C shell: # source <PCMAE_TOP>/cshrc.platform
- Bourne shell: # . <PCMAE_TOP>/profile.platform
- Where <PCMAE_TOP> is the top-level directory where the Platform Cluster Manager Advanced Edition is installed (for example, /opt/platform).
3.
Log on to EGO as a Platform Cluster Manager Advanced Edition administrator.If your Platform Cluster Manager Advanced Edition management server
integrated with LDAP or PAM plug-in, log into Platform Cluster Manager Advanced Edition using the password of the LDAP or PAM user
mapped to the Platform Cluster Manager Advanced Edition administrator user Admin.
# egosh user logon -u Admin -x Admin
4. Shut down all EGO services.
# egosh service stop all
5. Uninstall the fix from the extracted directory(PCMAE41Fix230291):
# ./install.sh rollback
6. Start all EGO services.
# egosh service start all
Note: When uninstalling fixes, ensure that they are uninstalled in the reverse order of installation.
6. List of files
|-- com/
| `-- platform/
| |-- icm/
| | `-- icmgr/
| | |-- cloudObjMgr/
| | | `-- scriptLayerMgr/
| | | `-- internal/
| | | `-- ScriptLayerMgrI.class
| | `-- ICMResource.properties
| `-- vmo/
| `-- vmomgr/
| `-- util/
| `-- PostInstallScriptHelper.class
|-- VMTools/
| `-- scripts/
| |-- network.vbs
| `-- startego.vbs
`-- install.sh
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.