Direct links to fixes
4.1.1-TIV-SAMP-Linux64-FP0001
4.1.1-TIV-SAMP-AIX-FP0001
4.1.0-TIV-SAMP-AIX-FP0002
4.1.0-TIV-SAMP-Linux64-FP0002
4.1.0-TIV-SAMP-Linux-FP0002
3.2.2-TIV-SAMP-Linux-FP0009
3.2.2-TIV-SAMP-AIX-FP0009
3.2.2-TIV-SAMP-Solaris-FP0009
3.2.2-TIV-SAMP-Windows-FP0009
3.2.2-TIV-SAMP-Windows-FP0009
4.1.0-TIV-SAMP-AIX-FP0003
4.1.0-TIV-SAMP-Linux-FP0003
4.1.0-TIV-SAMP-Linux64-FP0003
4.1.0-TIV-SAMP-AIX-FP0006
4.1.0-TIV-SAMP-Linux-FP0006
4.1.0-TIV-SAMP-Linux64-FP0006
4.1.0-TIV-SAMP-AIX-FP0007
4.1.0-TIV-SAMP-Linux64-FP0007
SAMP4107_Verification_Signatures
4.1.1-TIV-SAMP-AIX-FP0000
4.1.1-TIV-SAMP-Linux64-FP0000
3.2.2-TIV-ITSAMP-FP0009, Tivoli System Automation for Multiplatforms
4.1.0-TIV-ITSAMP-FP0003, Tivoli System Automation for Multiplatforms
4.1.0-TIV-ITSAMP-FP0004, Tivoli System Automation for Multiplatforms
APAR status
Closed as program error.
Error description
Support Engineer: GBH Change Team Eng: EJ Environment: TSAMP 4.1.0.1 Details: Primary node fails and all resources are successfully started on standby node. When the original primary node rejoins the cluster, all its resource constituents are reported online, even though this is not possible. This then triggers global offline orders for all resource consituents on all nodes, hence causing an outage.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Tivoli System Automation for Multiplatforms * users **************************************************************** * PROBLEM DESCRIPTION: * Due to a race condition the resources on a rebooted node might * be reported as 'Online', even if those are not. This triggers * automation actions to stop the resources on all nodes, which * results in an outage of the resources. * The problem is caused by improper internal handling that * prevents that the resources' internal OpState is set to * 'Offline' during node reboot. **************************************************************** * RECOMMENDATION: ****************************************************************
Problem conclusion
The internal handling of the automation engine has been adjusted to address the problem. Now resources on a rebooted node will honor the OpState reported by the resource monitor. . The official fix for this problem is included in Tivoli System Automation for Multiplatforms 4.1 fix pack 2 | 4.1.0-TIV-ITSAMP-FP0002 | . Additional Search Keywords .
Temporary fix
Comments
APAR Information
APAR number
IV73411
Reported component name
SA MULTIPLATFOR
Reported component ID
5724M0000
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-05-19
Closed date
2015-07-01
Last modified date
2015-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SA MULTIPLATFOR
Fixed component ID
5724M0000
Applicable component levels
Document Information
Modified date:
25 September 2023