IV61171: RG MOVE REQUEST CAUSES ALL RESOURCES IN ANOTHER RG TO BE OFFLINED IF A FORCEDDOWNBY RELATIONSHIP EXISTS.

4.1.1-TIV-SAMP-Linux64-FP0001
4.1.1-TIV-SAMP-AIX-FP0001
4.1.0-TIV-SAMP-AIX-FP0001
4.1.0-TIV-SAMP-Linux-FP0001
4.1.0-TIV-SAMP-Linux64-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:  MM
  
  Environment:
  TSAMP v4.1
  
  Details:
  Given two comprising groups with nested groups inside:
  
  her-rg                    ( running per default on node01 )
          her-app-rg    ( holds 15 app resources )
          her-fs-rg        ( holds file systems )
  
  luc-rg                      ( holds 4 app resources, running
                                     per  default on node node02)
          luc-fs-rg         ( holds file systems )
  
  Both RGs are per default running on different nodes.
  We have some startafter relations between apps from luc-rg to
  apps in nested group her-app-rg, which all work well,
  also during a move of the comprising group her-rg.
  
  Then we created a forcedownby rel from
  IBM.Application:sehefeeder ( luc-rg ) to IBM.Application:hermid
  ( her-app-rg )
  
  Now, when moving the comprising group her-rg, not only
  IBM.Application:hermid goes down ( which would be correct ).
  As soon as now the nested group her-fs-rg goes down, also the
  nested  group luc-fs-rg goes down.
  And that of course causes the whole stuff in luc-rg to be
  restarted.
  And as a side effect, if both RGs are on the same node and
  her-rg is  moved back, the luc-rg follows her-rg to the other
  node.
  As soon as we removed the forcedownby-rel, the luc-fs-rg stays
  online  during the move...
  
  Then we used dependsonany instead of forcedownby. The results
  are the  same EXCEPT that luc-rg does'nt follow her-rg to the
  other node anymore.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:
  * Tivoli System Automation for Multiplatforms (SA MP) 4.1 users
  ****************************************************************
  * PROBLEM DESCRIPTION:
  * The ForcedDownBy relationship is not working as expected in
  * complex environments where this relationship has been defined
  * between resources that are members of different nested
  * resource groups. If the target resource of the relationship
  * fails, the source resource is stopped as expected, but in
  * addition to that, other unrelated resources are stopped and
  * restarted too.
  * As a side effect the resources grouped together with the
  * source resource of the relationship might be moved unnecessary
  * to the same node as the target resource of the relationship in
  * case the resource group containing the target resource of the
  * ForcedDownBy relationship is moved.
  ****************************************************************
  * RECOMMENDATION:
  ****************************************************************
  

Problem conclusion

• The internal handling of the ForcedDownBy relationship has been
  adjusted to address this issue.
  .
  The official fix for this issue is included in Tivoli System
  Automation for Multiplatforms 4.1 fix pack 1
  | 4.1.0-TIV-ITSAMP-FP0001 |
  .
  Additional Search Keywords
  .
  

Temporary fix

Comments

APAR Information

• 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