Managing Shared Disks

Recabling without adding new physical disks

Follow these steps to use the IBM Recoverable Virtual Shared Disk subsystem when you are recabling to add the connection to a secondary node but do not need to add new physical disks.

1. Stop any applications that use the affected volume groups.
2. Stop the IBM Recoverable Virtual Shared Disk subsystem on all the nodes. For example:

   ha.vsd stop
   

3. Add a physical connection from each of the physical disks in the IBM Recoverable Virtual Shared Disk configuration to a secondary node.
4. On the secondary node, import the volume group. For example:

   importvg -y volume_group_name hdiskx
   

5. On the secondary node, disable auto varyon for the volume group. For example:

   chvg -a n volume_group_name
   

6. On the secondary node, varyoff the volume group. For example:

   varyoffvg volume_group_name
   

7. On the secondary node, redefine the virtual shared disks with the secondary nodes identified. For example:

   SDRChangeAttrValues VSD_Global_Volume_Group \
     global_group_name==your_global_group_name \
     secondary_node=your_secondary_node_number
   

8. On the secondary node, update the volume group timestamps that the IBM Virtual Shared Disk subsystem maintains. For example:

   vsdvgts -a volume_group_name
   

9. If the secondary node has not previously been designated as a virtual shared disk node, do so by using the IBM Virtual Shared Disk Perspective graphical user interface or the vsdnode command.
10. Issue a reset to make all the virtual shared disks in the configuration active and start the IBM Recoverable Virtual Shared Disk subsystem. For example:

    ha_vsd reset