IBM Support

IJ45661: DISK FENCING QUARANTAINE POLICY NOT USED EVEN IF SMIT SHOWS YES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • 'smitty cm_cluster_quarintine_disk_dialog'
    shows 'Disk Fencing' = 'Yes' even if no
    stanza with 'policy = "scsi"' exists
    in HACMPsplitmerge ODM.
    
    But PowerHA's clvaryonvg event script
    does not call the required commands,
    if the stanza is missing.
    
    hacmp.out looks like:
    ...
    +[RG]:cl_activate_vgs(0.105):[VG][vgs_chk:103]
     clvaryonvg -n [VG]
    +[RG]:clvaryonvg(0.011):[VG][985] version=1.21.7.22
    ...
    +[RG]:clvaryonvg(0.069):[VG][1098]
     clodmget -n -q policy=scsi -f value HACMPsplitmerge
    +[RG]:clvaryonvg(0.073):[VG][1098] SCSIPR_ENABLED=''
    +[RG]:clvaryonvg(0.074):[VG][1098]
     typeset SCSIPR_ENABLED
    +[RG]:clvaryonvg(0.074):[VG][1099]
     clodmget -q $'name like \'*VOLUME_GROUP\'
     and value = [VG]' -f group -n HACMPresource
    +[RG]:clvaryonvg(0.077):[VG][1099] resgrp=[RG]
    +[RG]:clvaryonvg(0.077):[VG][1099] typeset resgrp
    +[RG]:clvaryonvg(0.077):[VG][1100] [[ '' == Yes ]]
    +[RG]:clvaryonvg(0.078):[VG][1134]
     : Operations such as varying on the volume group
     are likely to
    +[RG]:clvaryonvg(0.078):[VG][1135]
     : require read/write access. So, set any
     volume group fencing appropriately.
    +[RG]:clvaryonvg(0.078):[VG][1137]
     cl_set_vg_fence_height -c [VG] rw
    ...
    
    and so a fallover event fails, if the disks are
    configured with Persistent Reserve for the Disk
    Fencing Quarantaine Policy.
    

Local fix

Problem summary

  • While modifying cluster to define only CRITICAL_RG value using
    below command
    ?clmgr modify cluster CRITICAL_RG=RG1? this issue will be
    observed. In this case Quarantine policy is not provided hence,
    only CRITICAL_RG value will be updated
    in the ODM and will not have the Quarantine Policy in the ODM.
    

Problem conclusion

  • Code change is done to verify if Quarantine Policy is also
    provided with CRITICAL_RG or not. Only Critical_RG value
    updating will not be supported from now.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ45661

  • Reported component name

    POWERHA SYSMIR

  • Reported component ID

    5765H3900

  • Reported release

    727

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-03-02

  • Closed date

    2023-03-02

  • Last modified date

    2023-03-02

  • APAR is sysrouted FROM one or more of the following:

    IJ44703

  • APAR is sysrouted TO one or more of the following:

    IJ45770 IJ45771

Fix information

  • Fixed component name

    POWERHA SYSMIR

  • Fixed component ID

    5765H3900

Applicable component levels

[{"Business Unit":{"code":"BU008","label":"Security"},"Product":{"code":"SGL4G4","label":"PowerHA"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"727"}]

Document Information

Modified date:
10 March 2023