MSA P2050 unmap volume

[WillyEB70]

Dear all

I have a p2050 msa with only one volume and a mapping that allows access to all hosts. When I made this configuration I didn't specify any hosts and I used the "all initiator" parameter instead.

This configuration is not best practice but it worked for me because all servers had to access that volume as part of a cluster.

Now I need to remap the volume because some servers need to be removed from this cluster.

I would like to add that this operation needs to be done without interrupting connectivity between the servers that remain in the cluster and this volume.

My idea is to add explicit mappings between individual hosts and the volume and, after that, remove the default "all initiator" parameter.

What do you think ?

Thanks a lot 

Best Regards

Enrico

[WillyEB70]

This is volume and mapping settings:

# show volumes
Pool Name Total Size Alloc Size Type Large Virtual Extents Health Reason Action
-------------------------------------------------------------------------------------
A Vol0001 19.9TB 7715.9GB base Disabled OK
-------------------------------------------------------------------------------------
Success: Command completed successfully. (2023-02-27 08:42:51)
# show maps

Volume View [Serial Number (***confidential info erased***) Name (Vol0001) ] Mapping:
Ports LUN Access Identifier Nickname Profile
-----------------------------------------------------------------
1-4 0 read-write all other initiators Standard

Could I leave "default all initiator" and add this command for all hosts that don't need to see the volume ?

# map volumeVol0001 access no-access initiator HOST-1,HOST-2

What do you think about it ?

Thanks 

Best Regards

Enrico

[ArunKKR]

Hi Enrico,

I believe that you are trying to make mapping changes without losing access to volumes and zero downtime. 
Any mapping changes is recommended to be performed during a maintenance window with no IOs to MSA volumes.
During mapping changes you might lose access to volume for few seconds.

[WillyEB70]

Hi,

this is the messages that 2050 display when I try to make new settings:

# map volume Vol0001 access no-access initiator HOST-1,HOST-2
WARNING: An existing default mapping with the same LUN was found. The new mapping may override the default mapping on the same LUN. Changes could cause loss of data.
Do you want to continue? n

will other servers still see VOL0001 after this?

Thanks

Best Regards

Enrico

[ArunKKR · Accepted solution]

Hi,

I would suggest using explicit mapping to the required hosts and then delete default mapping rather than using map command with no-access parameter.

It's an informational message to alert about existing mapping.
It should not impact the volume access to other hosts after the mapping changes.
As a best practice data back up is suggested before performing any such actions.