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....
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.
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.
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.
rawstorage
4 Apprentice
•
423 Posts
6753
1
Posted February 18th, 2014 23:00
Chris is 100% correct. the number is across both FA ports as he has stated, and includes meta-members
symcfg -sid 4379 list -address -available -fa 5h -p 0
Symmetrix ID: 000xxxxxxxx (Local)
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-5H 05H 0 09C5 Not Visible ACLX 0 00 000
- AVAILABLE 0 00 001 *
Total ----
Mapped Devices: 1
Including Metamembers: 1
Available Addresses: 4095 (s)
Legend:
Flags:
(A)CLX Enabled : X = True, . = False
(V)olume Set Addressing : X = True, . = False
(P)oint to Point : X = True, . = False
(F)COE Director : X = True, . = False
VNX (G)ateway Direct Attach : X = True, . = False