Data Protection

 View Only
  • 1.  HUR For Multiple resource groups in G5600

    Posted 07-17-2025 14:34
    Edited by System 10-17-2025 19:06

    We have a new VSM resource group in addition to the default meta resource group on the G5600. All LDEVs in the VSM group were migrated using GAD NDM. I need to set up HUR for some LDEVs in the meta resource group and some in the VSM group.

    CCI commands like pairdisplay and paircreate work fine for the LDEVs in the meta resource group, but they fail when I run them against LDEVs in the new VSM resource group:

    16:37:52-98215-09044280- [pairdisplay][exit(201)]
    [EX_EGPERM] Permission denied with the Resource Group
    [Cause ]:A User does not have a permission to access this Resource Group.
    [Action]:Please specify the permitted resource(group,Ldev,port,etc) for this user.

    I tried to login the instance successfully with admin user and permission by raidcom -login admin_user xxxxxx -IHxxx,  but 'pairdisplay' still failed afterward with same errors. What can I do to fix it?



    ------------------------------
    Sam Liang
    University of California - Davis Medical Center
    ------------------------------


  • 2.  RE: HUR For Multiple resource groups in G5600
    Best Answer

    Posted 07-18-2025 05:43
    Edited by System 10-17-2025 19:06

    Hello SAM. 

    I dont see a problem with what you're doing. As long as the GAD relationship was cleaned up properly or if you're setting the correct mirror ID.

    Users belong to a VSM. It could be that the user you're using doesn't have access to the VSM that the migrated volumes are in. Could you for instance get the ldev_id details using that users to check the host_groups? If not maybe use a user that does have access to those resources and resource_groups. 



    ------------------------------
    William Jansen Van Nieuwenhuizen
    Hitachi Vantara
    ------------------------------



  • 3.  RE: HUR For Multiple resource groups in G5600

    Posted 07-18-2025 16:12
    Edited by System 10-17-2025 19:06

    Thanks William.

    This issue was resolved by enabling the user authentication attribute on the command device.



    ------------------------------
    Sam
    ------------------------------