Reusing a volume that was a P-VOL

Global Active Device for VSP One Block

Version
10.5.x
File Size
25537 KB
Audience
anonymous
Part Number
MK-23VSP1B011-11
ft:lastEdition
2026-06-23

After you delete a GAD pair by specifying the P-VOL, you can continue to use the volume that was the P-VOL of the pair. When you execute the raidcom get ldev command for a volume that continues to be available after pair deletion, a value other than ffff or fffe is displayed for the VIR_LDEV (virtual LDEV ID), or the VIR_LDEV is not displayed.

Use the following procedure to move the volume to another resource group (virtual storage machine) so that the server recognizes it as a different volume and it can be used.

  1. Delete the LU path to the volume.
  2. If the DKCMAIN microcode version is A0-05-41 or later, check whether VSM auto-configuration is used on the operation-target volume.

    If AUTO_VIRTUAL_STORAGE is YES, go to step 3. If AUTO_VIRTUAL_STORAGE is NO or if the DKCMAIN microcode version is earlier than A0-05-41, go to step 4.

    raidcom get ldev –ldev_id 0x1111 –key virtual –fx –IH100
    LDEV# VIR_LDEV Serial# V_Serial# V_ID V_NUMBER VOL_TYPE
    VIR_VOL_TYPE SSID VIR_SSID AUTO_VIRTUAL_STORAGE
    4444 5555 900061 900061 RH20ETP 1 OPEN-V-CVS
    - a - NO
    
  3. Reset the virtual information of the volume (-virtual_info reset_and_delete_ldev_id).

    After the operation is complete, go to step 5.

    raidcom modify ldev -virtual_info reset_and_delete_ldev_id -ldev_id 0x4444 -request_id auto -IH1
  4. Delete the virtual LDEV ID.

    Command example for deleting virtual LDEV ID (0x5555) set for LDEV ID (0x4444):

    raidcom unmap resource -ldev_id 0x4444 -virtual_ldev_id 0x5555

    When you delete the virtual LDEV ID, the volume changes to a volume whose virtual LDEV ID has been deleted. If you execute the raidcom get ldev command for a volume whose virtual LDEV ID has been deleted, fffe is displayed for the VIR_LDEV (virtual LDEV ID).

  5. Reserve an LDEV ID for a resource group to be used for a different purpose.

    Command example for reserving LDEV ID (0x4444) for resource group (AnotherGroup) to which the volume is registered:

    raidcom add resource -resource_name AnotherGroup -ldev_id 0x4444

  6. Set a virtual LDEV ID for the volume.
    Note: You must set a virtual LDEV ID that is unique within the storage system that uses the volume. If the same virtual LDEV ID is used in other storage systems or virtual storage machines with the same serial number and model, identification of multiple volumes with the same virtual LDEV ID might cause problems. At worst, the server might detect an inconsistency.

    Command example for setting virtual LDEV ID (0xe000) for volume (0x4444):

    raidcom map resource -ldev_id 0x4444 -virtual_ldev_id 0xe000

  7. Specify a new port and host group for the volume, and set an LU path to the volume.