There are a number of parameters and definitions related to FC, FCoE, and iSCSI configuration limits.
|Visible target ports per host (iSCSI)||The maximum number of target iSCSI Ethernet ports that a host can see or access on iSCSI-attached controllers.|
|Visible target ports per host (FC)||The maximum number of FC adapters that a host can see or access on the attached Fibre Channel controllers.|
|LUNs per host||The maximum number of LUNs that you can map from the controllers to a single host.|
|Maximum paths from host to LUN||The maximum number of paths from the host to a single LUN
Note: Using the maximum number of paths is not recommended.
|Maximum paths from host to storage solution||
The maximum total number of paths from the host to the entire cluster. If you have more than 4 nodes, the best practice is to use portsets to limit paths to a subset of the nodes in the cluster. You should not exceed more than 8 paths.
|Maximum LUN size||The maximum size of an individual LUN on the respective operating system.|
|Vservers||The total number of Vservers, including the default node Vserver. There are limits on Vservers per node and Vservers per cluster.|
|Volumes per node||The total number of volumes supported on a single node.|
|LUNs per controller or node||The maximum number of LUNs that you can configure per controller, including cloned LUNs and LUNs contained within cloned volumes. LUNs contained in Snapshot copies do not count in this limit and there is no limit on the number of LUNs that can be contained within Snapshot copies.|
|LUNs per volume||The maximum number of LUNs that you can configure within a single volume. LUNs contained in Snapshot copies do not count in this limit and there is no limit on the number of LUNs that can be contained within Snapshot copies.|
|FC port fan-in||The maximum number of hosts that can connect to a single FC port on a controller. Connecting the maximum number of hosts is generally not recommended, and you might need to tune the FC queue depths on the host to achieve this maximum value.|
|FC LIFs per port||The maximum number of Fibre Channel logical interfaces (LIFs) that can be defined on a single physical FC port.|
|FC port fan-out||The maximum number of LUNs mapped to a host through a FC target port on a controller.|
|iSCSI sessions per controller or node||The recommended maximum number of iSCSI sessions that you can connect to a single controller. The general formula to calculate this is as follows: Maximum sessions = 8 * System Memory divided by 512 MB.|
|IP LIFs per port||The maximum combined number of iSCSI, NFS, CIFS, and FlexCache logical interfaces (LIFs) that can be defined on a single physical Ethernet port.|
|iSCSI LIFs per portset||The maximum number of iSCSI logical interfaces that can be assigned to a single portset.|
|Hosts per controller (FC)||The maximum number of hosts that can connect to a controller. Connecting the maximum number of hosts is generally not recommended, and you might need to tune the FC queue depths on the host to achieve this maximum value. This value assumes two initiators per host.
Note: Virtualized hosts, using NPIV to access the fabric with virtual WWPNs, count as additional hosts for the purpose of this limitation.
|igroups per controller||The maximum number of initiator groups that you can configure per controller.|
|Initiators per igroup||The maximum number of FC initiators (HBA WWNs) or iSCSI initiators (host iqn/eui node names) that you can include in a single igroup.|
|LUN mappings per controller||The maximum number of LUN mappings per controller. For example, a LUN mapped to two igroups counts as two mappings.|
|LUN path name length||The maximum number of characters in a full LUN name. For example, /vol/abc/def has 12 characters.|
|LUN size||The maximum capacity of an individual LUN on a controller.|
|FC queue depth available per port||The usable queue depth capacity of each FC target port. The number of LUNs is limited by available FC queue depth.|
|Ethernet ports per node||The maximum number of supported Ethernet ports per node.|
|FC target ports per controller or node||The maximum number of supported FC target ports per controller. FC initiator ports used for back-end disk connections, for example, connections to disk shelves, are not included in this number.|
|Portsets per node||The maximum number of portsets that can be created on a single node.|