Ops Center

Hi Dhruv,

You are trying to delete your two luns from the server group which is not a way to do for your case. Instead do in the following ways:

In Administrator go to Volume inventory.

Select the two volumes->Actions->Detach volumes. 

At next page it will show you all the server where these volumes are connected, select the server/host from where you want them to be disconnected and then submit, wait for Administrator job to be finished.

Hope, this will help you.

Hi Dhruv,

You are trying to delete your two luns from the server group which is not a way to do for your case. Instead do in the following ways:

In Administrator go to Volume inventory.

Select the two volumes->Actions->Detach volumes. 

At next page it will show you all the server where these volumes are connected, select the server/host from where you want them to be disconnected and then submit, wait for Administrator job to be finished.

Hope, this will help you.

Hello Dhruv

It's a bit difficult to see from your screenshot. But can you confirm that this lun is not in a 'shared hostgroup'? If the volume is part of a shared host group you'd typically see the message you're showing. 

If you click on the volume. There should be a section that shows the associated HOST GROUP NAMES. If the volumes is in a shared host group it's a bit more complex you either have to create distinct host groups(moving the WWNN's one by one) and then unmap the lun from those host groups OR delete the host WWN's from the shared host group that would remove all the volume access for the effected hosts. 

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

Hello Dhruv

It's a bit difficult to see from your screenshot. But can you confirm that this lun is not in a 'shared hostgroup'? If the volume is part of a shared host group you'd typically see the message you're showing. 

If you click on the volume. There should be a section that shows the associated HOST GROUP NAMES. If the volumes is in a shared host group it's a bit more complex you either have to create distinct host groups(moving the WWNN's one by one) and then unmap the lun from those host groups OR delete the host WWN's from the shared host group that would remove all the volume access for the effected hosts. 

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

Hello Dhruv

It's a bit difficult to see from your screenshot. But can you confirm that this lun is not in a 'shared hostgroup'? If the volume is part of a shared host group you'd typically see the message you're showing. 

If you click on the volume. There should be a section that shows the associated HOST GROUP NAMES. If the volumes is in a shared host group it's a bit more complex you either have to create distinct host groups(moving the WWNN's one by one) and then unmap the lun from those host groups OR delete the host WWN's from the shared host group that would remove all the volume access for the effected hosts. 

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

Depends on who you ask and the client implementation. 

You can have a max of 255 host groups per port. So if a client has 1000's of Hosts you'll have to either use shared host groups or multiple ports just to connect them.

Personally I don't like shared host groups if I don't have to use them, because it takes away a lot of the granular control as per your post as an example. But in a very large enterprise environment with 1000's, 10 000 or 100 000 of physical hosts you would most likely use shared host groups.