If the same virtual LDEV ID as the primary volume is displayed for the virtual storage machine of the secondary site, there might be errors in the GAD system implementation plan. Revise the system configuration.
The example when the same virtual LDEV ID as that of the P-VOL (0x2222) is assigned to the volume (LDEV ID: 0xfefe) in the virtual storage machine of the secondary machine is shown below.
When the DKCMAIN microcode version is A0-05-41 or later, check whether VSM auto-configuration is used on the target volume.
If AUTO_VIRTUAL_STORAGE is YES, perform Revising the virtual LDEV ID at the secondary site when VSM auto-configuration is used. If AUTO_VIRTUAL_STORAGE is NO, or when the DKCMAIN microcode version is earlier than A0-05-41, perform Revising the virtual LDEV ID at the secondary site when VSM auto-configuration is not used.
raidcom get ldev –ldev_list virtual –virtual_type 911111 RH20ETP -fx -IH1 LDEV# VIR_LDEV Serial# V_Serial# V_ID V_NUMBER VOL_TYPE VIR_VOL_TYPE SSID VIR_SSID AUTO_VIRTUAL_STORAGE fefe 2222 922222 911111 RH20ETP 1 OPEN-V-CVS OPEN-V-CVS a a YES 2223 2223 922222 911111 RH20ETP 1 OPEN-V-CVS OPEN-V-CVS a a NO