If the source array does not have the Consistent LUN attribute set, but the target does (if it is a pre-created IG) then there will be consistent LUN addresses on the Target array. However, there is no attempt to use the same LUN addresses as on the source even if, by chance, the LUN addresses on the source are consistent across all the paths.
- By default, VMAX and PowerMax arrays are delivered with the ACLX using LUN 0 and visible on a number of ports. Therefore, if the SHOW_ACLX_DEV attribute is still in effect on a port that NDM will choose and the source array is using Consistent LUN and is also using LUN 0, then we will not be able to set the same LUN addresses. This is because LUN 0 is not available on the target array for all the ports that NDM will use when it builds the Masking View.
- When the target VMAX or PowerMax array is deployed and storage is provisioned to the host and uses the LUN addresses for these new LUNs that it is also using for the ‘application to be migrated’ that resides currently on the source array:
- Obviously, the existing application is using a different set of ports/paths because it is on a different array.
- When we migrate that application, the LUN addresses we would want to use will not be available. Thus, you will get consistent, but different LUN addresses.