IV99384: VG MODIFICATION TO 'CRITICAL' USING CLMGR IS NOT WORKING

APAR status

• Closed as program error.

Error description

• .
  ----------------------------- Test Environment Details
  ----------------------------- CLUSTER INFORMATION:2 nodes
  Cluster Nodes (Hostname/IP): Site A: r1r2m1p41(172.19.67.51)
  site B : r1r2m1p42(172.19.67.52) Cluster Access
  (User/Password): root/abc123) HMC/Console access: 172.19.69.5
  (GuestUser/ibm@123) Pre AIX Level : 1441D_61c Pre RSCT level :
  rmut1433a 3.2.0.0 RSCT_Build_Context=power Pre PowerHA : 610
  GOLD + SP16 Post AIX level: 1709A_71X RSCT LEVEL : rootas001a
  3.2.1.11 power PowerHA SM Level : 713 Gold + SP7 HA_SP: VG
  modification to 'critical' using clmgr is not working
  ================ Steps followed are:  1)installed caa aix
  1441D_61c 2)installed powerha 713 GOLD+ SP7 3) Created cluster
  and sites 4)Created VG 5)Modified VG as critical using the
  following command clmgr modify vg <VGNAME> critical=true Output
  is displayed as "clmgr: The cluster configuration has been
  changed - CRITICAL Volume Group VG01 has been added.  The
  configuration must be synchronized to make this change
  effective across the cluster" But, "critical" attribute's value
  in "clmgr query vg <VGNAME>" shows "false".  The same behavior
  is observed in Powerha 720 SP3
  .
  The details are:
  .
      clmgr q vg VG01 NAME="VG01" TYPE="SCALABLE"
      NODES="r1r2m1p41,r1r2m1p42" LOGICAL_VOLUMES="LV01,loglv01"
      PHYSICAL_VOLUMES="hdisk3@r1r2m1p41@00cde1376fafe841"
      MIRROR_POOLS="" STRICT_MIRROR_POOLS="no"
      RESOURCE_GROUP="RG01" AUTO_ACTIVATE="false" QUORUM="true"
      CONCURRENT_ACCESS="true" CRITICAL="false"
      ON_LOSS_OF_ACCESS="" NOTIFYMETHOD=""
      MIGRATE_FAILED_DISKS="false" SYNCHRONIZE="false"
      LOGICAL_TRACK_GROUP_SIZE="512"
      MAX_PHYSICAL_PARTITIONS="32768" PPART_SIZE="2048"
      MAX_LOGICAL_VOLUMES="256" MAJOR_NUMBER="40"
      IDENTIFIER="00cde13700004c000000015b0f132430"
      TIMESTAMP="58da498c20af3985" clmgr modify vg VG01
      CRITICAL=true clmgr: The cluster configuration has been
      changed - CRITICAL Volume Group VG01 has been added. The
      configuration must be synchronized to make this change
      effective across the cluster.# clmgr q vg VG01 NAME="VG01"
      TYPE="SCALABLE" NODES="r1r2m1p41,r1r2m1p42"
      LOGICAL_VOLUMES="LV01,loglv01"
      PHYSICAL_VOLUMES="hdisk3@r1r2m1p41@00cde1376fafe841"
      MIRROR_POOLS="" STRICT_MIRROR_POOLS="no"
      RESOURCE_GROUP="RG01" AUTO_ACTIVATE="false" QUORUM="true"
      CONCURRENT_ACCESS="true" CRITICAL="false"
      ON_LOSS_OF_ACCESS="" NOTIFYMETHOD=""
      MIGRATE_FAILED_DISKS="false" SYNCHRONIZE="false"
      LOGICAL_TRACK_GROUP_SIZE="512"
      MAX_PHYSICAL_PARTITIONS="32768" PPART_SIZE="2048"
      MAX_LOGICAL_VOLUMES="256" MAJOR_NUMBER="40"
      IDENTIFIER="00cde13700004c000000015b0f132430"
      TIMESTAMP="58da49b222543c73"
  

Local fix

Problem summary

• Modification of vg as
  critical not effected.
  

Problem conclusion

• Display Warning message when trying
  to mark vg as critical in
  "Fast Disk Takeover" mode.
  

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:

  IV99385 IV99386

Fix information

• Fixed component name

  POWERHA SYSMIR

• Fixed component ID

  5765H3900

Applicable component levels

• R713 PSY

     UP