Fix Readme
Abstract
xxx
Content
Readme file for: CSM-1.7.1.7-power-Linux
Product/Component Release: 1.7.1.7
Update Name: CSM-1.7.1.7-power-Linux
Fix ID: CSM-1.7.1.7-power-Linux
Publication Date: 29 June 2010
Last modified date: 29 June 2010
Installation information
Download location
Below is a list of components, platforms, and file names that apply to this Readme file.
Product/Component Name: | Platform: | Fix: |
---|---|---|
(CSM) IBM Cluster Systems Management | Linux pSeries RHEL Linux pSeries SLES | CSM-1.7.1.7-power-Linux |
Prerequisites and co-requisites
None
Known issues
- Known Issues
- When using Live Partition Mobility (LPM) function to move CSM Managed Node from one Managed System to another, some of the node attributes (Lpar_ID, HWModel, HWType, etc...) will get out of sync as a result.
- When the rpower on/off command is issued, rpower query output can not indicate the true rpower status for the nodes managed by IVM 2.1.1 or lower. This is caused by an event subscription module, which will be fixed in IVM2.1.2.
- Stop cimserver by command: /usr/ios/sbin/climgr cimserver stop
- Delete files in /opt/freeware/cimom/pegasus/etc/repository/root#ibmsd/instances
- Start cimserver by command: /usr/ios/sbin/climgr cimserver start
- The rpower query output for the nodes managed by IVM 2.0.0.0 or higher will stuck after IVM is rebooted.
- If the GFW340 firmware version which is lower than 340_033 installed on POWER6 575 machine, the BPA connection will have some problem, only one side of BPA is shown connected.
- If the BladeCenter Advanced Management Module firmware version is BPET46C, BPET46G or BPET46H, the rpower reboot command against the blades managed by the AMM will fail with error "Communications failed".
- rfwflash command for BladeCenter JS nodes with AIX OS will exit with return code 1, and there will be a dsh timeout error in /var/log/csm/rfwfalsh_detail.log.
- In CSM 1.7's Administration Guide's page 196 Table 21, GPFS script configurations does not list GPFS 3.2 support for SLES 9 and SLES10. And there are no examples listed for SLES 10 and SLES 9 in:
- /csminstall/csm/scripts/data/GPFS.pre
- /csminstall/csm/scripts/data/GPFS
- /csminstall/csm/scripts/data/GPFS.post
- If you have run copycds for normal SLES10 SP1 ISOs, and wants to use csmsetupinstall with -p flag to install SLES10 SP1 Update1 distribution for JS22 machines, they will have to remove the original directory /csminstall/Linux/SLES/10/ppc64/SP1 first, otherwise csmsetupinstall will not copy the new SLES10 SP1 Update1 ISOs since the target directory in /csminstall has already been there.
- When running DCEM with Korean language, if you click on Reports tab ---> select a report ----> click View button, ----> click on Command tab, The Strings Device names , Device groups are not displayed and fields are truncated due to small window size.
- When running DCEM with a language such as Korean which has no alphabetic characters, if you click on Browse button of Name, The Column heading "Description" contains a shortcut character such as "korean_translation(D)". Some of the shortcut strings are not working. There are two "Name" strings on file. The string for column heading is without shortcut function now.
- If a node's IP or MAC address is changed, getadapters or csmsetupinstall may fail to get the node's MAC address.
- When nfs-utils has been installed, running installms with -f option will fail:
installms -f -p .
Creating the required directories for CSM.
...
...
installms: Failed to install Management Server Operating System
Prerequisites Packages!
About to copy CSM command binaries.
Successfully copied CSM command binaries.
installms: Installation of CSM was unsuccessful (rc = 1).
Workaround:
- Remove nfs-utils rpm from the CSM Management Server manually by executing the rpm command with -e option.
- Run installms with -f option again.
- When running a dsh command in which the last character is a semicolon (';') and semicolon is not a delimiter of shell command, dsh will ignore this semicolon, and may cause the command to fail. For example, the following command will fail:
find /tmp -name RATSTempFile -exec ls -l {} \;
Workaround:
CSM won't adjust to dynamic changes, so user need to use the chnode, rmnode, and definenode commands as appropriate to manually update the CSM definitions to match what they have done with partition mobility. Otherwise, it could result in actions being performed on the wrong LPARs.
Workaround:
Restart IBM.HWCTRLRM to register CSM event again after the event subscription is cleared up on IVM. Please follow the steps below:
On IVM:On the CSM Management Server:
Restart IBM.HWCTRLRMWorkaround:
Run rpower -n < node_name > refresh or restart IBM.HWCTRLRM to refresh the rpower state.Workaround:
Update the firmware to 340_033 or higher.Workaround:
Upgrade the AMM firmware to BPET46J or higher.GPFS 3.2 can support both SLES9 and SLES10 and GPFS scripts can be updated by CSM admin.
Workaround:
Remove the original directory /csminstall/Linux/SLES/10/ppc64/SP1 before csmsetupinstall -p is run.Workaround:
Enlarge the window.Workaround:
There isn't workaround for this problem.Workaround:
Check the arp entry on the Install Server and the gateway machine, if an old permanent arp entry for this node exists, remove it with arp command.Workaround:
Add an additional semicolon at the end of shell command, for example:
find /tmp -name RATSTempFile -exec ls -l {} \;;
- The CRHS configuration does not show up on an HMC upgraded to V6.1 and later.
Upgrading an HMC in the ClusterPeerDomain requires that the addpeer command be run again for that HMC. The ClusterPeerDomain is not preserved after an upgrade.
Caution: There is a known problem when upgrading the HMC from Version 5 and early Version 6 to Version 6.1 or later. In this scenario the hardware server resource manager on the HMC fails to start after the upgrade. This results in the HMC not displaying the hardware configuration.
To avoid this problem, ensure that the HMC resources in the ClusterPeerDomain that were created with addpeer have the Manager_Configured attribute set to 1 prior to upgrading.
On the CSM management server enter lsrhws -m . This will list all of the HMCs that are defined in the ClusterPeerDomain. The output for one HMC would be similar to:
lsrhws -m
--------------------------------
Manager_Type = "HMC"
Manager_IP_A = "20.0.0.5"
Manager_IP_B = ""
Manager_Name = "40.0.0.5"
Manager_MTMS = "7315CR2*10407DA"
Manager_Configured = If the HMC listed above was added to the ClusterPeerDomain
using addpeer and the "Manager_Configured" attribute
equals "0" then it needs to be changed to "1".
If all of the HMCs defined in the ClusterPeerDomain were added with addpeer, then all HMCs may be updated at once using the following command:
chrhws -s 'Manager_Type=="HMC"' -a Manager_Configured=1
If only one HMC resource needs to be updated, then use the following command:
chrhws -s 'Manager_Name=="10.0.0.71"' -a Manager_Configured=1
To preserve the Cluster Ready Hardware Server configuration on an HMC, be sure to save "Save upgrade data" prior to upgrading the HMC. This data should automatically be restored after the HMC is upgraded and doesn't require a reboot of the HMC.- When upgrading SLES nodes using the "you" InstallMethod , sometimes the SLES online_update tool does not upgrade all the RPMs to the latest levels, and the SPident tool reports that some of the packages are not at the correct service pack level. This is a SUSE problem, and the workaround is to use the rpm -U command to manually update the missing packages reported by SPident.
- cfmupdatenode does not support all forms of nodegroup ranges on command input. You can use cfmupdatenode -N grp1,grp2,... or cfmupdatenode -N "grp1 grp2 ..." but you cannot use cfmupdatenode -N grp1-grp2 or cfmupdatenode -N grp1+3
- Running installnode on an IVM-managed LPAR, the LPAR remains in and continues to boot to the Open-firmware prompt. To change the LPAR boot-mode back to "Normal", after the install is complete and the node reboots to Open-firmware , run rpower off , wait until the LPAR powers off, and then issue the rpower on command.
- When running commands that run rconsole such as getadapters , netboot , and installnode for an IVM-managed LPAR, other open consoles to that LPAR are forced closed. This is due to a limitation in the IVM firmware.
- Running installnode for a SLES9-SP3 OpenPower 720 MN, OS installation may stop when installing 1# CD packages. It will report "Installation of package suse-build-key-1.0-662.10.noarch failed." and prompts the user to choose "Abort, Retry or Ignore" You can choose Ignore and the installation should continue.
- lshwstat returns inaccurate readings for CPU temperature for System x 3455 servers. When running the lshwstat command with the "temp" or "cputemp" options, an inaccurate reading may be returned for CPU temperature. For example, the command may return a temperature for CPU #1 of 3 degrees C. Also, in a single-CPU x3455 server, a temperature of -128 degrees C may be returned for the non-existent CPU.
- reventlog -a or reventlog -e
will hang when retrieving large event logs of 65K or greater. The event log size required to reproduce this problem is a log with approximately 800 entries; although, this number is dependent on the length of each entry since the real limiting factor is retrieving 65K or greater worth of data.
As a workaround to running reventlog -a , run reventlog -e <#> , where <#> is some number (for example 500) that will not exceed the 65K limit. Since the log is returned in LIFO order, the last (most current) 500 entries will be returned.
Known limitations
- Known Limitations
- When a IBM System P CEC has a large numbers of LPARs, for example 60 LPARs, it will take more than 4 minutes for the HMC to return the power status for each LPAR and CEC. CSM will consider it as a socket timeout and interrupt the communication to the HMC. This will result in a subscription failure for the power status change. The user will see an error message for the rpower query command ""2651-692 Power status event registration failed, retrying".
- In the CSM Cluster-Ready Hardware Server environment, beginning with HMC V7.3.5.0, Open Source software "openslp" is used to setup SLP service on the HMC. It does not support the Broadcast package for SLP discovery, instead, openslp uses the Multicase package.
As a result, CSM has changed the hardware discovery mechanism from Broadcast to Multicast, which requires Multicast support to be enabled on Ethernet switches. - SELinux is disabled in the Red Hat EL 5.3 default kickstart templates. This means that SELinux on Red Hat EL 5.3 CSM managed nodes installed with default kickstart template file is disabled. This is due to a RedHat SELinux bug that prevents the CSM and RSCT packages from being installed after the operating system installation.
- CSM does not support Java5 communication to HMC version7 with SNIA/SSL.
- The support of Cluster Ready Hardware Server (CRHS) redundancy working with POWER6 575/595 frame and servers requires only one active network connection to be used in the cluster service network that is connected between CSM MS, HMCs, POWER6 575/595 Frame BPA, and POWER6 575/595 server FSP.
This change is based on the design modification of the POWER6 Frame Bulk Power Controller (BPC) internal network that is now providing the redundancy support to the Frame BPA and Server FSP. The configuration of having two active network connections from the POWER6 575/595 frame and servers to the HMC and CSM MS may cause SLP network issues working with CRHS. - Can not update system firmware for multiple POWER6 575 CECs in one rfwflash invocation if the HMC version is V7R3.3.0 (lower than Service Pack 2) or system firmware within the same release for multiple System p CECs if the HMC version is V7R3.5.0. The rfwflash command may encounter unknown errors for some CECs or return an error like "HSCF0168E Side A Bulk Power Controller on 9A00-100*992003X is not ready to perform Licensed Internal Code update", and the firmware update will not succeed for all CECs.
- rfwflash command can not be used to update the power code for POWER6 575 and POWER6 595.
- In the CRHS environments, frame -l does not properly show the frame IDs for the POWER6 575 and POWER6 595 frames. frame -l always returns 0 for the frame IDs though frame -i can set the frame IDs correctly. We have also found that the Frame_BPA_MTMS may also be missing in some specific scenarios.
- When launching dsh command through DCEM, the dsh command will always fail with the error "Host is not responding. No command will be issued to this host".
- If BPA slot number is changed due to any reason such as firmware defect, the connection between the HMC and the frame will have "Duplicate IP" error. The error looks like:
resource_type=frame,type_model_serial_num=9A00-100*XXXXXXX,side=unavailable,
ipaddr=10.0.0.1,alt_ipaddr=unavailable,
state=Connecting,connection_error_code=Duplicate IP 0008-0005-0000801E - When executing a remote command via dsh on SLES 9 nodes, the remote command might fail because the command cannot be found on the nodes.
- The SFP events monitoring function for P5 and POWER6 servers does not work if the HMC version is lower than V7R3.3.0 Service Pack 2.
- If you redeploy an AIX LPAR to be installed with SLES9SP3 or SLES10 OS, the node installation will fail if working on P5 550/570 servers. This failed installation will cause a P5 firmware TFTP failure, and make this P5 LPAR unusable to boot back to the original OS on the node, and will fail to install either AIX53J, AIX610 or SLES OS on the node. This problem was reported on firmware level SF240_320 for P5 550 and level SF240_202 P5 570.
- set-defaults;
- dev nvram; wipe-nvram (or try: delenv ibm,fw-forced boot)
- When installing SLES 10 managed nodes, the monitorinstall -r/-R command may not display the correct RPM name that is being installed, it sometimes displays "installing prep" instead of the RPM name.
- When running the mkflashfiles command without the "-f" flag, the command will attempt to process all the update code files it finds in the /csminstall/csm/fw directory. The command will not distinguish between different files for the same target platform (for example, the directory contains two BIOS update packages for System x3650 servers at two different BIOS levels). In this scenario it is possible the later version of the update package will be processed first, and then be overwritten by the older version of the package. For this reason, IBM recommends that only one update package per target platform reside in the /csminstall/csm/fw directory.
- For System P4 nodes with firmware version RG021209_GA3_ALL or higher, SLES9 GA cannot be installed and it reports the error "Claim failed for initrd memory". SLES9 SP3 and higher distribution doesn't have this problem.
- In a cross-network installation environment with a specific switch (which only broadcasts bootp datagrams) as "bootp relay agent", System p nodes cannot get bootp reply when the Management Server runs installnode . The reason is the System p node only sends the unicast request datagram instead of the broadcast one when it requests bootp information.
The workaround is to use the parameter --noreboot on installnode command to avoid this Restriction. - The CSM management server cannot connect to the Baseboard Management Controller (BMC) of a System x3455 server while the x3455 is performing a PXE boot broadcast during power up. This is due to a limitation in the x3455 that prevents access to the LAN interface of the BMC while the PXE boot broadcast is running. This blackout period can last anywhere from 30 seconds to one minute or more. During this time, the BMC will not respond to ping requests, and any power control or remote console requests will return a "Baseboard Management Controller is not responding" message. The behavior of a remote console session that was previously open when the PXE boot occurs depends on the setting of the csmconfig attribute "BMCConsoleKeepAlive". If the attribute is set to 0 (the default setting), there will be no indication that the session is lost, other than the console being non-responsive. The console session must be closed and then restarted when the BMC is available. If the attribute is set to 1, a message will be written to the console approximately 50 seconds after the IPMI session is lost, and the session will be closed. The session must be restarted when the BMC is available.
- If you are using CSM's Blue Gene support and inadvertently run bgsetupms on your management server after Blue Gene monitoring is already active, monitoring may stop and associations built on the conditions involved will be removed. The workaround is to use mkcondresp and startcondresp to redefine the lost associations and restart the Blue Gene monitoring. You should restart the CSM Blue Gene monitoring.
- The rfwflash command cannot be used to flash the Baseboard Management Controller (BMC) firmware on target nodes running Linux Operating System versions lower than Red Hat 4 QU3 or SLES 9 SP3.
Customers that require BMC updates on older versions of the Operating System will need to manually install the OSA IPMI Driver and the IBM IPMI Mapping Layer for Linux packages on the target node before flashing the BMC. Note that the Mapping Layer package for Linux will be a source rpm.
These packages are available for download from the IBM Support Web Site at http://www.ibm.com/support. To install the driver and mapping layer software, follow these steps:- Ensure that the packages for rpm, gcc, glibc, and kernel-source appropriate for the Operating System on the target node are installed.
- Remove any existing installations of the OSA IPMI Driver and IBM IPMI Mapping Layer software.
- Copy the new OSA Driver and IBM IPMI Mapping Layer packages to a temporary directory
- Use the rpm -i command to build and install the OSA IPMI drivers. If the build or installation fail, refer to the build.log file in the /usr/osa/
directory for more information. Once the errors detailed in the build.log file have been corrected, run the build_osadrv script located in the same directory to try the build and install steps again. - Run the ipmi_load script.
- Build the IBM IPMI Mapping Layer installation package by running the command rpmbuild --rebuild
. Note the name of the output Mapping Layer rpm written by the rpmbuild command. - Install the IBM IPMI Mapping Layer rpm.
- The rpower -b option is not working for System x 3455 nodes. The "-b" option to allow selection of the boot device to be used on the next power on or reboot does not work on System x 3455 servers. Any boot device specified will be ignored and the server will boot according to the boot order set in BIOS.
- Selected Linux Update Packages1 that initiate DOS-based updates do not run under Red Hat EL 4 or SUSE LINUX Enterprise Server 9. These packages can usually be identified by their size, which is typically 2 MB or higher, compared to the standard lflash based package, which is usually under 1 MB.
- Selected Linux Update Packages1 that initiate DOS-based updates cannot be run in a pre-Operating System environment. These packages modify the Master Boot Record of the target server to run DOS. In the pre-Operating System environment, the MBR is not available. These packages can usually be identified by their size, which is typically 2 MB or higher, compared to the standard lflash based package, which is usually under 1MB.
Workaround:
Increase the socket timeout value.
To increase the socket timeout value to 10 mins:
Step 1:stopsrc -s IBM.HWCTRLRM
Step 2:startsrc -s IBM.HWCTRLRM -e "HC_SOCKET_TIMEOUT=600000"
Workaround:
For some Ethernet switches, Multicast support is enabled by default, such as Cisco Catalyst 2960 Series Switches. If it is not enabled by default, refer to your Switch Guides to enable Multicast.
Workaround:
If required, enable SELinux manually after the CSM full installation completes.Workaround:
Use Java 1.4 (or lower) version or set environment variable HC_JAVA_PATH=/usr/java14.Workaround: N/A
Workaround:
Work directly with the HMC GUI to update multiple CECs in the same frame. You can run rfwflash -n with only one CEC for each frame, and place multiple rfwflash -n invocations in a script if you want to execute rfwflash from the CSM Management server.
Or upgrade the HMC version V7R3.3.0 to Service Pack 2 or higher, or HMC version V7R3.5.0 to Service Pack 1 or higher.
Workaround:
Work directly with the HMC GUI to update the power code for POWER6 575 and POWER6 595.
Workaround:
After the Frame_ID is set using frame -i, use chrhws to change the Frame_ID to the correct value. If the Frame_BPA_MTMS is also missing, you need to use chrhws to link the Element_IP_A to the Frame_BPA_MTMS.
Workaround:
Before running the command, clear the option "Before running commands, verify that targets are responding" in the Options tab.
Workaround:
Rebooting the HMC can clean up the "Duplicate IP" error.
Workaround:
You need to specify the full path of the remote command.
Workaround:
You can run the following commands in Open Firmware command line to fix this problem:
Additional information
- Description
CSM 1.7.1.7 is a service update level package for Release 1.7.1 Systems Management software for Linux on Power. This package contains a full image for CSM software to support Linux on Power hardware.
See the CSM for AIX and Linux documentation for further information.
The minimum HMC, Service Processor and Bulk Power code level requirements for this release of CSM are:
- HMC: MH00593 (V5 R1.1_2 NLS)
- Service Processor: 01SF235_195_160
- Bulk Power: 02BP235_169_156
What's New?
- CSM 1.7.1.7 provides support for RedHat EL5.5 Server installation
- Package contents
README
RPMS
csm.client-1.7.1.7-9.ppc.rpm
csm.core-1.7.1.7-9.ppc.rpm
csm.dsh-1.7.1.7-9.ppc.rpm
csm.gui.dcem-1.7.1.7-9.ppc.rpm
csm.deploy-1.7.1.7-9.ppc.rpm
csm.server-1.7.1.7-9.ppc.rpm
csm.diagnostics-1.7.1.7-9.ppc.rpm
csm.essl-1.7.1.7-9.ppc.rpm
csm.gpfs-1.7.1.7-9.ppc.rpm
csm.ll-1.7.1.7-9.ppc.rpm
csm.pe-1.7.1.7-9.ppc.rpm
csm.bluegene-1.7.1.7-9.ppc.rpm
csm.hc_utils-1.7.1.7-9.ppc.rpm
csm.hams-1.7.1.7-9.ppc.rpm
csm.pessl-1.7.1.7-9.ppc.rpm
sam-2.3.0.3-08071.ppc.rpm
rsct.basic-2.5.5.0-10047.ppc.rpm
rsct.core-2.5.5.0-10047.ppc.rpm
rsct.core.utils-2.5.5.0-10047.ppc.rpm
rsct.core.cimrm-2.5.5.0-10047.ppc.rpm
rsct.opt.storagerm-2.5.5.0-10047.ppc.rpm
rsct.64bit-2.5.5.0-10047.ppc64.rpm
src-1.3.1.0-10047.ppc.rpm
Software requisites (included in the package)
reqs/conserver-8.1.7-3.i386.rpm
reqs/IBMJava2-JRE-1.4.2-0.0.i386.rpm
reqs/conserver-8.1.7.tar.gz
- Changelog
Problems fixed in CSM 1.7.1.7 [April 29, 2010]
- lppchk error for csm.deploy inside wpar.
- rfwflash hangs for JS blade.
- rpower status stuck with HMC V7R7.
- This update addresses the following APARs: IZ72980 IZ73089
Problems fixed in CSM 1.7.1.6 [March 15, 2010]
- CRHS problem starting hdwr_svr with openssl installp package.
- This update addresses the following APARs: IZ66739 IZ69943
Problems fixed in CSM 1.7.1.5 [January 21, 2010]
- rpower query CEC status fail to work because of CIM event error.
- dsh returns errors when running some commands to Qlogic IB switches.
- cfmupdatenode -F option does not always work.
- This update addresses the following APARs: IZ67540 IZ58284
Problems fixed in CSM 1.7.1.4 [October 26, 2009]
- IBM.CSMAgentRM reports 2610-602 A session could not be established.
- IBM.HWCTRLRM socket connections remain in a CLOSE_WAIT state.
- This update addresses the following APARs: IZ55597 IZ57962 IZ58359
Problems fixed in CSM 1.7.1.3 [August 13, 2009]
- IBM.CSMAgentRM has disabled polling when running on a WPAR.
- Installing RedHat 5.3 from a POWER4 Install Server failing with an LED E143.
- This update addresses the following APARs: IZ54837 IZ54838 IZ54839
Problems fixed in CSM 1.7.1.2 [June 25, 2009]
- cfmupdatenode is not recognizing the "MinManaged-Installing" status
- This update addresses the following APARs: IZ50520 IZ52840
Problems fixed in CSM 1.7.1.1 [May 18, 2009]
- CSM Try-and-Buy license key is not allowed.
- healthCheck does not show unknown speed info on JS blade.
- HWSVRRMD core due to unreserved is being called.
- This update addresses the following APARs: IZ48411 IZ49810
Problems fixed in CSM 1.7.0.19 [April 16, 2009]
- checkpoint of WPAR is failing.
- csm.server prereq issue in multibos.
- This update addresses the following APARs: IZ42536 IZ47932 IZ47935
Problems fixed in CSM 1.7.0.18 [March 5, 2009]
- nodegrp issue when removing nodes.
- cfmupdatenode failing for filename containing ":"
- ibAdapterConfig updated to configure ml0.
- This update addresses the following APARs: IZ41004 IZ42902 IZ43362 IZ43614
Problems fixed in CSM 1.7.0.17 [January 26, 2009]
- dsh fails in non English locale.
- Performance enhancements for CSMAgentRM.
- csmsnap enhancements.
- cfmupdatenode coexistence update.
- This update addresses the following APARs: IZ38648 IZ39065 IZ39066 IZ39067
Problems fixed in CSM 1.7.0.16 [November 13, 2008]
- POWER6 FSP default IP addresses cause Version Mismatch issue in CRHS environment.
- getadapters with -D flag on POWER6 9117-MMA fails with "no adapters found".
- rpower reports wrong status when IBM.HWCTRLRM loses its connection to an HMC.
- dsh -v performance issue on large clusters.
- FSP Proxy Provider connect failures to POWER6 CECs.
- CSMAgentRM not setting certain IBM.ManagementServer attributes.
- This update addresses the following APARs: IZ31725 IZ33415 IZ34163 IZ35702 IZ34290
Problems fixed in CSM 1.7.0.15 [October 7, 2008]
- DLPAR function is unavailable in Power4 environment
- This update addresses the following APARs: IZ29205 IZ33416
Problems fixed in CSM 1.7.0.14 [September 19, 2008]
- Fix for netboot of CSP nodes.
- Update for Hardware Control Java daemon issue on large clusters
- Corrected a dsh issue where the hostname was appearing at the end of some lines.
- This update addresses the following APARs: IZ28845 IZ29741 IZ29195 IZ29199
Problems fixed in CSM 1.7.0.13 [July 24, 2008]
- Update to cfmupdatenode to correctly substitute meta variables.
- Update to cfmupdatenode to prevent files from being copied to incorrect nodes.
- Corrected a dsh issue where the hostname was appearing at the end of some lines.
- Fix for dsh -v reporting the node as not responding when LC_ALL is not C.
- SFP events monitoring updates for POWER5 and POWER6.
- This update addresses the following APARs: IZ20906 IZ21571 IZ23343 IZ23836 IZ23934 IZ26101 IZ26895
Problems fixed in CSM 1.7.0.12 [May 29, 2008]
- Update to dsh for noderanges.
- Fix for dlpar on POWER4 HMCs.
- IBM.HWSVRRM will now process updates to Element_Frame_ID and Element_BPA_MTMS in one request.
- Cluster-Ready Hardware Server updates.
- This update addresses the following APARs: IZ21571 IZ20709 IZ22352
Problems fixed in CSM 1.7.0.11 [May 2, 2008]
- Update IBM Tivoli System Automation for Multiplatforms (TSA) package to 2.3 FP3 to make the HA MS work properly.
- This update addresses the following APARs: IZ16405 IZ16865 IZ18109 IZ18204 IZ18791 IZ18792 IZ19460
Problems fixed in CSM 1.7.0.4 [February 7, 2008]
- Update to prevent hung child processes in dsh.
- RAS enhancement for cfmupdatenode.
- Correction to cfmupdatenode to maintain correct ownership of files.
- Change to certain predefined conditions to make the monitoring of the conditions more efficient.
- Fix for hwsdagent core dump.
- This update addresses the following APARs: IZ11547 IZ11548 IZ11549 IZ12233 IZ12748 IZ14050 IZ14370 IZ14374
Problems fixed in CSM 1.7.0.3 [December 6, 2007]
- Enhanced support for communication between the CSM MS and the 7.0 HMC using SSL.
- Update to predefined conditions that are shipped with CSM for more efficient monitoring.
- Corrected a condition where the ManagedNode Status attribute remains 127.
- This update addresses the following APARs: IZ08386 IZ09468 IZ10063
Problems fixed in CSM 1.7.0.1 [November 12, 2007]
- Support RHEL 5.1 GA.
- Improve updatenode command's performance.
- syslog monitoring performance enhancement.
Was this topic helpful?
Document Information
Modified date:
10 August 2010
UID
isg400000029