Flash Storage​

 View Only

  • 1.  External Volume as P-Vol for GAD

    Posted 03-16-2023 12:29

    Hi guys,

    I try to use an External Volume as a P-Vol for a GAD Pair replication.
    OpsCenter Administrator does not show the "External_Volume" in the Volume list under Storage/<Serial>/Volumes. I see it only in Storage/<Serial>/External Volumes. 

    Also I'm not able to start a HORCM instance, pointing to this LDEV ID (under section HORCM_LDEV)

    The device [Serial#(XXX),LDEV#(1234)] is not mapped to any logical units

    Is this an expected behavior not able to use this External_Volume as P-Vol for a GAD replication ?
    Also not normal seen by OpsCenter and not able to access by HORCM as LDEV ? 

    regards
    Sven 



    ------------------------------
    Sven Kirsten
    Systems Engineer
    SVA System Vertrieb Alexander GmbH
    ------------------------------


  • 2.  RE: External Volume as P-Vol for GAD

    Posted 03-17-2023 00:52

    It is not clear from your description whether the External Volume is a supported type for use as a P-Vol in a GAD replication. However, it is not uncommon for storage systems to have specific requirements for external volumes to be used in certain functions, such as replication.

    Regarding your issue with OpsCenter not showing the External Volume in the Volume list, this may be due to the way that the storage system is configured or the permissions that are set for the OpsCenter user. You should check with your storage system documentation or support team to confirm the expected behavior in this situation.

    Regarding your issue with starting a HORCM instance and not being able to access the External Volume as an LDEV, it is possible that the External Volume is not properly mapped to the storage system or there may be a configuration issue with your HORCM instance. You should consult with your storage system documentation or support team to confirm that the External Volume is properly mapped and configured for use with your HORCM instance.

    Overall, it is difficult to determine the root cause of your issue without more information about your storage system and configuration. It is recommended that you consult with your storage system documentation or support team to determine the expected behavior for using External Volumes in GAD replication and to troubleshoot any issues that you are experiencing.  

    I hope this will help you.  SkyWard Alpine



    ------------------------------
    Diana Stanley
    Chief Financial Officer
    Glicks Furniture
    ------------------------------

    Original Message


  • 3.  RE: External Volume as P-Vol for GAD

    Posted 03-17-2023 03:14

    Hi Diana, 

    thank you for your response. 

    So from your answer I derivate that the OpsCenter Software and the HORCM should be able to use External Volume LDEVs as P-Vol in a GAD replication. There are no limitations. 

    To give you more Details: 

    • VSP E-790
    • OpsCenter 10.9.1

    And I would expect that this External_Volume is also able to "Attach to a Server". But this is also not possible because the External_Volume does not appear in the normal Storage / <Serial> / Volumes list.

    But when I understand you right - this should be also possible in OpsCenter. 

    regards
    Sven 


    ------------------------------
    Sven Kirsten
    Systems Engineer
    SVA System Vertrieb Alexander GmbH
    ------------------------------

    Original Message


  • 4.  RE: External Volume as P-Vol for GAD

    Posted 04-18-2023 13:18

    Hi

    Can you post some screen grabs ?

    Thanks
    Vinod



    ------------------------------
    Vinod Subramaniam
    Technical Expert
    Hitachi Vantara
    ------------------------------

    Original Message


  • 5.  RE: External Volume as P-Vol for GAD

    Posted 04-20-2023 08:22

    Hi ,
    This could be all wrong but here is how I see it.


    when you add that external volume,
    it will show up as a external volume under the meta resource group.
    It will also now have a virtual ldev_id.
    It will not show up in Ops Center as a "Volume"
    but as a "External Volume"
    To Map to a different Resource Group you must unmap the Vir. LDEV_ID, map this LDEV_ID to your preferred Resource group, then map the Virtual_LDEV_ID back to this LDEV. Then you could map this to a host in your preferred Resource Group using Raidcom, or SVP... but not OpsCenter.

    To Protect an external Volume
    you must first migrate the external volume to a DPpool , then you can protect it.

    Or the external Volume is a DataDirect Mapping volume, then you could protect with GAD if the secondary is also a DDM Volume.





    Here are some expirements i made on this.

    Source Storage System: E790

     

    Target Storage System: F350

     

     

     

     

    Before adding the external LDEV

     

    452006-1:$ raidcom get ldev -ldev_id 45

    Serial#  : 452006

    LDEV : 45

    SL : -

    CL : -

    VOL_TYPE : NOT DEFINED

    SSID : 0004

    RSGID : 0

     

    After adding the external LDEV via OpsCenter…  but not migrating it! And not mapping it to a host!

    452006-1:$ raidcom get ldev -ldev_id 45

    Serial#  : 452006

    LDEV : 45

    SL : 0

    CL : 0

    VOL_TYPE : OPEN-V-CVS

    VOL_Capacity(BLK) : 29360128

    NUM_PORT : 0

    PORTs :

    F_POOLID : NONE

    VOL_ATTR : CVS : ELUN

    CMP : -

    EXP_SPACE : -

    E_VendorID : HITACHI

    E_ProductID : OPEN-V

    E_VOLID : 484954414348492035303630324235303030324500000000000000000000000000000000

    E_VOLID_C : HITACHI 50602B50002E................

    NUM_E_PORT : 1

    E_PORTs : CL1-A-0 11 50060e80212b5000

    LDEV_NAMING : testxy

    STS : NML

    OPE_TYPE : NONE

    OPE_RATE : 100

    MP# : 0

    SSID : 0004

    ALUA : Disable

    RSGID : 0                    (This ELUN belongs to the Meta-Resource Group)

    PWSV_S : -

    CL_MIG : N

    452006-1:$

     

     

    Attempted to add the LDEV to a new VSM / Resource Group 5

     

    452006-1:$ raidcom add resource -resource_name rainier_VSM_M850S1F_455555 -ldev_id 45

    raidcom: [EX_CMDRJE] An order to the control/command device was rejected

    It was rejected due to SKEY=0x05, ASC=0x26, ASCQ=0x00, SSB=0x2E21,0x9305 on Serial#(452006)

    CAUSE : The specified resource is set the information of virtual storage.

    452006-1:$

    The LDEV_ID belongs to Resource Group 0 meta-resource group and the Virtual_ID is set.

     

    To move the LDEV Resource  to a new group /VSM:

     

    1. unmap the virtual ID
    2. add the LDEV to the VSM you want to use
    3. map the virtual ID back again

     

    1. 452006-1:$ raidcom unmap  resource -ldev_id 45 -virtual_ldev_id 45
    2. 452006-1:$ raidcom add resource -resource_name rainier_VSM_M850S1F_455555 -ldev_id 45
    3. 452006-1:$ raidcom map resource -ldev_id 45 -virtual_ldev_id 45

     

     

    Now the LDEV belongs to the VSM Resource Group 5 rainier_VSM_M850S1F_455555

     

    452006-1:$ raidcom get ldev -ldev_id 45

    Serial#  : 452006

    LDEV : 45 VIR_LDEV : 45

    SL : 0

    CL : 0

    VOL_TYPE : OPEN-V-CVS

    VOL_Capacity(BLK) : 29360128

    NUM_PORT : 0

    PORTs :

    F_POOLID : NONE

    VOL_ATTR : CVS : ELUN

    CMP : -

    EXP_SPACE : -

    E_VendorID : HITACHI

    E_ProductID : OPEN-V

    E_VOLID : 484954414348492035303630324235303030324500000000000000000000000000000000

    E_VOLID_C : HITACHI 50602B50002E................

    NUM_E_PORT : 1

    E_PORTs : CL1-A-0 11 50060e80212b5000

    LDEV_NAMING : testxy

    STS : NML

    OPE_TYPE : NONE

    OPE_RATE : 100

    MP# : 0

    SSID : 0004

    ALUA : Disable

    RSGID : 5

    PWSV_S : -

    CL_MIG : N

    452006-1:$

     

    Now you can map the LDEV to a hostgroup in the VSM

    452006-1:$ raidcom add lun -port cl1-a-5 -ldev_id 45

    raidcom: LUN 0(0x0) will be used for adding.

    452006-1:$

     

     

     

    452006-1:$ raidcom get ldev -ldev_id 45

    Serial#  : 452006

    LDEV : 45 VIR_LDEV : 45

    SL : 0

    CL : 0

    VOL_TYPE : OPEN-V-CVS

    VOL_Capacity(BLK) : 29360128

    NUM_PORT : 1

    PORTs : CL1-A-5 0 Uli

    F_POOLID : NONE

    VOL_ATTR : CVS : ELUN

    CMP : -

    EXP_SPACE : -

    E_VendorID : HITACHI

    E_ProductID : OPEN-V

    E_VOLID : 484954414348492035303630324235303030324500000000000000000000000000000000

    E_VOLID_C : HITACHI 50602B50002E................

    NUM_E_PORT : 1

    E_PORTs : CL1-A-0 11 50060e80212b5000

    LDEV_NAMING : testxy

    STS : NML

    OPE_TYPE : NONE

    OPE_RATE : 100

    MP# : 0

    SSID : 0004

    ALUA : Disable

    RSGID : 5

    PWSV_S : -

    CL_MIG : N

    452006-1:$

     

    In OpsCenter Administrator  the ELUN shows up under Servers  

     

     

    The Elun can only be migrated  in ops center administrator but not protected.

     

     

     

     

     

     








    ------------------------------
    Matt Muldoon
    Systems Engineer
    TD SYNNEX Germany GmbH & Co. OHG
    ------------------------------

    Original Message


Related Content