Creating GAD pairs when virtual LDEV IDs are deleted from the P-VOL and S-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

Some failure recovery operations, such as a primary storage system failure or secondary storage system failure, require you to delete GAD pairs. You might not be able to create them again until you assign a virtual LDEV ID.

Confirm that the GAD reserve attribute is assigned to the P-VOL (LDEV ID: 0x4444) and the S-VOL (LDEV ID: 0x5555) by using the raidcom get ldev command.
raidcom get ldev -ldev_id 0x4444 -fx -IH0
```
LDEV : 4444 VIR_LDEV : ffff
```
raidcom get ldev -ldev_id 0x5555 -fx -IH1
```
LDEV : 5555 VIR_LDEV : ffff
```
If you execute the raidcom get ldev command for a volume that has the GAD reserve attribute, ffff is displayed for VIR_LDEV (virtual LDEV ID).
Delete all of the LU paths to the P-VOL.
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 4. If AUTO_VIRTUAL_STORAGE is NO or if the DKCMAIN microcode version is earlier than A0-05-41, go to step 6.
```
raidcom get ldev –ldev_id 0x4444 –key virtual –fx –IH0
LDEV# VIR_LDEV Serial# V_Serial# V_ID V_NUMBER VOL_TYPE
VIR_VOL_TYPE SSID VIR_SSID　AUTO_VIRTUAL_STORAGE
4444 ffff 900061 911111 RH20ETP 1 OPEN-V-CVS
- a - YES
```

Reset the virtual information (-virtual_info reset) of the P-VOL.

raidcom modify ldev -virtual_info reset -ldev_id 0x4444 -request_id
auto -IH0

Perform the procedure of VSM manual configuration in Setting up the secondary storage system, in which replace the S-VOL with the P-VOL when performing the procedure.

If you set the virtual LDEV ID that is the same as the actual LDEV ID, perform the procedure in Setting the GAD reserve attribute on the S-VOL (VSM manual configuration), in which set the actual LDEV ID instead of assigning the GAD reserve attribute. After the settings are complete, go to step 8.
Release the GAD reserve attribute of the P-VOL (LDEV ID: 0x4444) by using the raidcom unmap resource command.
raidcom unmap resource -ldev_id 0x4444 -virtual_ldev_id reserve -IH0
Display the information about the P-VOL by using the raidcom get ldev command.
raidcom get ldev -ldev_id 0x4444 -fx -IH0
```
LDEV : 4444 VIR_LDEV : fffe
```
For the volume whose GAD reserve attribute was released, a virtual LDEV ID is not assigned. If you execute the raidcom get ldev command for a volume to which a virtual LDEV ID is not assigned, fffe is displayed for VIR_LDEV (virtual LDEV ID).
Set a virtual LDEV ID for the P-VOL (LDEV ID: 0x4444) by using the raidcom map resource command.
raidcom map resource -ldev_id 0x4444 -virtual_ldev_id 0x4444 -IH0
Display the information about the P-VOL by using the raidcom get ldev command.
raidcom get ldev -ldev_id 0x4444 -fx -IH0
```
LDEV : 4444 VIR_LDEV : 4444
```
Check the virtual attributes of the P-VOL and the S-VOL by using the raidcom get ldev command.
raidcom get ldev -ldev_id 0x4444 -fx -IH0
```
LDEV : 4444
```
raidcom get ldev -ldev_id 0x5555 -fx -IH1
```
LDEV : 5555 VIR_LDEV : ffff
```
The virtual LDEV ID (0x4444) is assigned to the P-VOL (LDEV ID: 0x4444) and the GAD reserve attribute ( VIR_LDEV : ffff) is assigned to the S-VOL (LDEV ID: 0x5555).
Specify a port and host group for the P-VOL, and set the LU path again.
Create GAD pairs again.
If a failure occurs after the one volume capacity of a GAD pair can be expanded, the creation, resync, swap resync, and horctakeover operations of the GAD pair cannot be performed because the capacity of both the volumes is not the same. Make sure to expand the other volume capacity so that the capacity of both the volumes is the same, and then retry the operation.