MAX number of LUNS that can be mapped to a Single FA port on VMAX?

On the DMX this depended on the FA Port Bits that were set.  If the -v bit was set you had something like 16 x 16 x 8 = 2048.  On the VMAX I'm not sure, but they still have default FA Port Bit settings....

    Stuart

I believe the limit is 4096 devices per FA processor so that takes both ports 0  and 1 into account.  

Meta members also count towards the total

Hi Quincy,

You mean to say that we need to create a new  Mask view with new port group to allocate the new symdevices

You can just create a 2nd masking view for the host that contains a different port group and a new storage group populated with the devices you want to add. 

Thank you for your reply. Now that we have reached the maximum limit. How can I assign new LUNS to the HOST.

Thanks for your reply. You are correct VMAX uses default settings.

If the FA CPU has reached that limit, you would have to use another FA, or reduce the device count.  Maybe use smaller number of larger devices?

Thanks for your reply. You are correct. only 4096 can be mapped to single FA processor including the meta members.

Now that we have reached the maximum limit on FA director.  How can I assign the new symmetrix devices to the Host for which Port group has reached its max limit.

Hi Chris,

That was my initial plan to create a second masking view.

By creating a new masking view. Will there be any impact on Host end?   I've two HBA's zoned to four FA ports which are in the same group.  Now in order to create new Masking view  I'll be zoning the existing two HBA's with Four new FA ports from different port group.

My questtion : If I assign the LUNS through different maskview the new LUNS may end up having the same HLUN ID which the existing devices already have. Will that be any issue on Host end or Powerpath.

What OS is it?  Windows will work fine, just rescan.

The host lun id may be the same i.e Lun1, Lun2 etc but it will be on a different target (FA port), we had the same issue a few days ago with a windows host and followed this workaround.

i have seen instances where Redhat would not discover new targets on the fly, had to reboot the host.

Thanks for sharing the information.

We have LINUX host here.

Thanks for the information. We will do a reboot here, that should not be a problem.

So we can create a new Maskview with new Port Group and assign the new devices through it. My only concern was same LUN ID's if I assign it from different Maskveiws.

zoning, masking view. Don't worry about the same LUN IDs, like it was mentioned above, they will have new target ID's so PowerPath will figure it out.