fibre channel and iscsi configuration guide for

Fibre Channel and iSCSI Configuration Guidefor the Data ONTAP® 8.1 7-Mode Release Family

NetApp, Inc.495 East Java Drive Sunnyvale, CA 94089 U.S. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support telephone: +1 (888) 463-8277Web: www.netapp.comFeedback: [email protected]

Part number 210-05455_A0January 2012

Contents

iSCSI configurations .................................................................................... 7Single-network HA pair in an iSCSI SAN .................................................................. 7

Multinetwork HA pair in an iSCSI SAN .................................................................... 9

Direct-attached single-controller configurations in an iSCSI SAN .......................... 10

VLANs for iSCSI configurations .............................................................................. 11

Static VLANs ................................................................................................ 11

Dynamic VLANs ........................................................................................... 11

Fibre Channel configurations .................................................................... 13FC onboard and expansion port combinations .......................................................... 13

Fibre Channel supported hop count .......................................................................... 14

Fibre Channel supported speeds ................................................................................ 15

Fibre Channel switch configuration best practices ................................................... 15

Host multipathing software requirements ................................................................. 16

62xx supported fibre channel configurations ............................................................ 16

62xx target port configuration recommendations ......................................... 16

62xx: Single-controller configurations .......................................................... 17

62xx: Single-fabric HA configurations ......................................................... 18

62xx: Multifabric HA configurations ............................................................ 20

62xx: Direct-attached single-controller configuration .................................. 21

62xx: Direct-attached HA configurations ..................................................... 22

60xx supported configurations .................................................................................. 23



60xx: Single-fabric HA pair .......................................................................... 25

60xx: Multifabric HA pair ............................................................................. 27

60xx: Direct-attached single-controller configuration .................................. 28

60xx: Direct-attached HA pair ...................................................................... 29




32xx: Single-fabric HA configurations ......................................................... 32

32xx: Multifabric HA configurations ............................................................ 33

Table of Contents | 3

32xx: Direct-attached single-controller configurations ................................. 34

32xx: Direct-attached HA configurations ..................................................... 35

FAS2240 supported configurations ........................................................................... 36

FAS2240: Single-fabric single-controller configuration ............................... 37

FAS2240: Single-fabric HA pair ................................................................... 38

FAS2240: Multifabric single-controller configuration ................................. 39

FAS2240: Multifabric HA pair ..................................................................... 40

FAS2240: Direct-attached single-controller configurations ......................... 41

FAS2240: Direct-attached HA pair ............................................................... 42




31xx: Single-fabric HA pair .......................................................................... 45

31xx: Multifabric HA pair ............................................................................. 46

31xx: Direct-attached single-controller configurations ................................. 47

31xx: Direct-attached HA pair ...................................................................... 49

30xx supported configurations .................................................................................. 50


3040 and 3070 supported configurations ...................................................... 50

FAS2040 supported configurations ........................................................................... 57

FAS2040: Single-fabric single-controller configuration ............................... 57

FAS2040: Single-fabric HA pair ................................................................... 58

FAS2040: Multifabric single-controller configuration ................................. 59

FAS2040: Multifabric HA pair ..................................................................... 60

FAS2040: Direct-attached single-controller configurations ......................... 61

FAS2040: Direct-attached HA pair ............................................................... 61

Fibre Channel over Ethernet overview .................................................... 63FCoE initiator and target combinations .................................................................... 63

Fibre Channel over Ethernet supported hop count .................................................... 64

Fibre Channel over Ethernet supported configurations ............................................. 64

FCoE: FCoE initiator to FC target configuration .......................................... 65

FCoE: FCoE end-to-end configuration ......................................................... 67

FCoE: FCoE mixed with FC ......................................................................... 68

FCoE: FCoE mixed with IP storage protocols .............................................. 70

Fibre Channel and FCoE zoning .............................................................. 73Port zoning ................................................................................................................ 73

4 | Fibre Channel and iSCSI Configuration Guide for the Data ONTAP® 8.1 7-Mode Release Family

World Wide Name based zoning .............................................................................. 74

Individual zones ........................................................................................................ 74

Single-fabric zoning .................................................................................................. 75

Dual-fabric HA pair zoning ....................................................................................... 76

Shared SAN configurations ....................................................................... 79ALUA configurations ................................................................................. 81Configuration limits for FC, FCoE, and iSCSI configurations .............. 83

SAN Configuration limit parameters and definitions ............................................... 83

Host operating system limits for SAN configurations .............................................. 84

62xx single-controller limits ..................................................................................... 85

62xx HA configuration limits ................................................................................... 86


32xx HA configuration limits ................................................................................... 88

FAS2240 single-controller limits .............................................................................. 90

FAS2240 HA configuration limits ............................................................................ 91

60xx and 31xx single-controller limits ...................................................................... 92

60xx and 31xx HA pair limits ................................................................................... 93


30xx HA pair limits ................................................................................................... 95

FAS2040 single-controller limits .............................................................................. 96

FAS2040 HA pair configuration limits ..................................................................... 97

Copyright information ............................................................................... 99Trademark information ........................................................................... 101How to send your comments .................................................................... 103Index ........................................................................................................... 105

Table of Contents | 5

iSCSI configurations

Supported iSCSI configurations include direct-attached and network-attached configurations. Bothsingle-controller and HA pairs are supported.

In an iSCSI environment, all methods of connecting Ethernet switches to a network approved by theswitch vendor are supported. Ethernet switch counts are not a limitation in Ethernet iSCSIconfigurations. For specific recommendations and best practices, see the Ethernet switch vendor'sdocumentation.

For Windows iSCSI multipathing options, please see Technical Report 3441: Windows MultipathingOptions with Data ONTAP: FCP and iSCSI.

Related information

NetApp Interoperability Matrix - now.netapp.com/NOW/products/interoperability/Technical Report 3441: Windows Multipathing Options with Data ONTAP: FCP and iSCSI -media.netapp.com/documents/tr-3441.pdf

Single-network HA pair in an iSCSI SANYou can connect hosts to HA pair controllers that use the iSCSI protocol over a single IP network.The network can consist of one or more switches. Each controller can have multiple iSCSIconnections to the network. The number of ports available depends on the storage controller model.

The following figure shows two Ethernet connections to the network per storage controller.Depending on the controller model, more connections are possible.

7

http://now.netapp.com/NOW/products/interoperability/

http://media.netapp.com/documents/tr-3441.pdf

http://media.netapp.com/documents/tr-3441.pdf

Figure 1: iSCSI single-network HA pair

Attribute Value

Fully redundant No, due to the single network

Type of network Single network

Different host operating systems Yes, with multiple-host configurations

Multipathing required Yes

Type of configuration HA pair


Multinetwork HA pair in an iSCSI SANYou can connect hosts to HA pair controllers that use the iSCSI protocol over multiple IP networks.To be fully redundant, a minimum of two connections to separate networks per controller isnecessary to protect against NIC, network, or cabling failure.

Figure 2: iSCSI multinetwork HA pair

Attribute Value

Fully redundant Yes

Type of network Multinetwork




iSCSI configurations | 9

Direct-attached single-controller configurations in an iSCSISAN

You can connect hosts using iSCSI directly to controllers. The number of hosts that can be directlyconnected to a controller or pair of controllers depends on the number of available Ethernet ports.

Note: Direct-attached configurations are not supported in HA pairs.

Figure 3: iSCSI direct-attached single-controller configurations

Attribute Value

Fully redundant No, due to the single controller

Type of network None, direct-attached



Type of configuration Single controller


VLANs for iSCSI configurationsA VLAN consists of a group of switch ports grouped together into a broadcast domain. A VLAN canbe on a single switch or span multiple switch chassis. Static and dynamic VLANs enable you toincrease security, isolate problems, and limit available paths within your IP network infrastructure.

Reasons for implementing VLANs

Implementing VLANs in larger IP network infrastructures has the following benefits.

• VLANs provide increased security because they limit access between different nodes of anEthernet network or an IP SAN. VLANs enable you to leverage existing infrastructure while stillproviding enhanced security.

• VLANs improve Ethernet network and IP SAN reliability by isolating problems.• VLANs can also help reduce problem resolution time by limiting the problem space.• VLANs enable you to reduce the number of available paths to a particular iSCSI target port.• VLANs enable you to reduce the maximum number of paths used by a host. Having too many

paths slows reconnect times. If a host does not have a multipathing solution, you can use VLANsto allow only one path.

Static VLANsStatic VLANs are port-based. The switch and switch port are used to define the VLAN and itsmembers.

Static VLANs offer improved security because it is not possible to breach VLANs using mediaaccess control (MAC) spoofing. However, if someone has physical access to the switch, replacing acable and reconfiguring the network address can allow access.

In some environments, it is easier to create and manage static VLANs than dynamic VLANs. This isbecause static VLANs require only the switch and port identifier to be specified, instead of the 48-bitMAC address. In addition, you can label switch port ranges with the VLAN identifier.

Dynamic VLANsDynamic VLANs are MAC-address based. You can define a VLAN by specifying the MAC addressof the members you want to include.

Dynamic VLANs provide flexibility and do not require mapping to the physical ports where thedevice is physically connected to the switch. You can move a cable from one port to another withoutreconfiguring the VLAN.

iSCSI configurations | 11

Fibre Channel configurations

Supported FC configurations include single-fabric, multifabric, and direct-attached configurations.Both single-controller and HA pairs are supported.

For multiple-host configurations, hosts can use different operating systems, such as Windows orUNIX.

HA pairs with multiple, physically independent storage fabrics (minimum of two) are recommendedfor SAN solutions. This provides redundancy at the fabric and storage system layers, which isparticularly important because these layers typically support many hosts.

The use of heterogeneous FC switch fabrics is not supported, except in the case of embedded bladeswitches. For specific exceptions, see the Interoperability Matrix on the NetApp Support Site.

Cascade, mesh, and core-edge fabrics are all industry-accepted methods of connecting FC switches toa fabric, and all are supported.

A fabric can consist of one or multiple switches, and the storage arrays can be connected to multipleswitches.

Note: The following sections show detailed SAN configuration diagrams for each type of storagesystem. For simplicity, the diagrams show only a single fabric or, in the case of the dual-fabricconfigurations, two fabrics. However, it is possible to have multiple fabrics connected to a singlestorage system. In the case of dual-fabric configurations, even multiples of fabrics are supported.This is true for both HA pairs and single-controller configurations.

Related information

NetApp Interoperability Matrix - now.netapp.com/NOW/products/interoperability/

FC onboard and expansion port combinationsYou can use storage controller onboard FC ports as both initiators and targets. You can also addstorage controller FC ports on expansion adapters and use them as initiators and targets.

The following table lists supported combinations.

Onboard ports Expansion ports Supported?

Initiator + Target None Yes

Initiator + Target Target only Yes

Initiator + Target Initiator only Yes

Initiator + Target Initiator + Target Yes

13


Onboard ports Expansion ports Supported?

Initiator only Target only Yes

Initiator only Initiator + Target Yes

Initiator only Initiator only Yes, but no FC SAN support

Initiator only None Yes, but no FC SAN support

Target only Initiator only Yes

Target only Initiator + Target Yes

Target only Target only Yes, but no FC disk shelf, V-Series configurations, or FCtape support

Target only None Yes, but no FC disk shelf, V-Series configurations, or FCtape support

Related concepts

Configuration limits for FC, FCoE, and iSCSI configurations on page 83

Related references

FCoE initiator and target combinations on page 63

Fibre Channel supported hop countThe maximum supported FC hop count between a host and storage system depends on switchsupplier and storage system support for FC configurations.

The hop count is defined as the number of switches in the path between the initiator (host) and target(storage system). Cisco also refers to this value as the diameter of the SAN fabric.

The following table lists supported hop counts:

Switch supplier Supported hop count

Brocade 6

Cisco 7

Up to 3 of the switches can be FCoE switches.


Fibre Channel supported speedsFibre Channel target ports can be configured to run at different speeds. You should set the target portspeed to match the speed of the device to which it connects.

The recommended best practice is to set the port speed to match the speed of the device connected tothe port. This is instead of using autonegotiation; a port set to autonegotiation can take longer toreconnect after a takeover/giveback or other interruption.

It is also recommended to set all ports used by a given host to the same speed.

4-Gb target ports

You can configure 4-Gb onboard ports and 4-Gb expansion adapters to run at the following speeds.Each controller and expansion adapter port can be configured individually. This allows configurationwith a different speed from the other ports as needed.

• 4 Gb• 2 Gb• 1 Gb

8-Gb target ports

You can configure 8-Gb onboard ports and 8-Gb expansion adapters to run at the following speeds.Each controller and expansion adapter port can be configured individually. This allows configurationwith a different speed from the other ports as needed.

• 8 Gb• 4 Gb• 2 Gb

Fibre Channel switch configuration best practicesA fixed link speed setting works best, especially for large fabrics, because it provides the bestperformance for fabric rebuild times. In large fabrics, this can create significant time savings.

Although autonegotiation provides the greatest flexibility, it does not always perform as expected.Also, it adds time to the overall fabric-build sequence because the FC port has to autonegotiate.

Note: Where supported, it works best to set the switch port topology to F (point-to-point).

Fibre Channel configurations | 15

Host multipathing software requirementsMultipathing software is required on a host computer any time it can access a LUN through morethan one path.

The multipathing software presents a single disk to the operating system for all paths to a LUN.Without multipathing software, the operating system could see each path as a separate disk, whichcan lead to data corruption.

Multipathing software is also known as MPIO (multipath I/O) software. Supported multipathingsoftware for an operating system is listed in the Interoperability Matrix.

For single-fabric single-controller configurations, multipathing software is not required if you have asingle path from the host to the controller. You can use zoning to limit paths.

For an HA pair, host multipathing software is required unless you use zoning to limit the host to asingle path.

62xx supported fibre channel configurations62xx controllers are available in single-controller and HA configurations.

The 62xx systems have four onboard 8-Gb FC ports per controller and each one can be configured aseither a target or initiator FC port.

The 62xx systems also have vertical I/O slots (slots 1, 11, and 12) that can use a special 4-port 8-GbFC adapter. Each port on these adapters can be individually configured as either a target or initiatorFC port, just like the onboard FC ports.

Each 62xx controller supports 4-Gb and 8-Gb FC target expansion adapters.

62xx target port configuration recommendationsFor best performance and highest availability, use the recommended FC target port configuration.

The port pairs on a 62xx controller that share an ASIC are 0a+0b and 0c+0d.

The following table shows the preferred port usage order for onboard FC target ports. For targetexpansion adapters, the preferred slot order is listed in the System Configuration Guide for theversion of Data ONTAP software that the controllers use.

Number of target ports Ports

1 0a

2 0a, 0c



3 0a, 0c, 0b

4 0a, 0c, 0b, 0d

62xx: Single-controller configurationsYou can connect hosts to single controllers using a single FC fabric or with multiple FC fabrics. Ifyou use multiple paths, multipathing software is required on the host.

FC switch zoning is recommended to limit the number of paths between hosts and LUNs inconfigurations with multiple target ports connected to the same fabric.

Note: The FC target port numbers in the following figure are examples. The actual port numbersmight vary depending on whether you are using onboard ports or FC target expansion adapters. Ifyou are using FC target expansion adapters, the target port numbers also depend on the expansionslots into which your target expansion adapters are installed.

Host 1 Host 2 Host N

Controller

Single Switch/Fabric 1

0a 0c 0b 0d

Figure 4: 62xx single-fabric single-controller configuration



Controller

Switch/Fabric 1 Switch/Fabric 2

0a 0c 0b 0d

Figure 5: 62xx multifabric single-controller configuration

Attribute Value


Type of fabric Single fabric or multifabric


FC ports or adapters One to the maximum number of supported onboard FC ports percontroller

One to the maximum number of supported 4-Gb or 8-Gb FCtarget expansion adapters

Type of configuration Single-controller configuration

62xx: Single-fabric HA configurationsYou can connect hosts to both controllers in an HA configuration through a single FC switch.

If you use multiple paths to a LUN, multipathing software is required on the host. FC switch zoningis recommended to limit the number of paths between hosts and LUNs in configurations withmultiple target ports connected to the same fabric.

Note: The FC target port numbers in the following figure are examples. The actual port numbersmight vary depending on whether you are using onboard ports or FC target expansion adapters. If


you are using FC target expansion adapters, the target port numbers also depend on the expansionslots into which your target expansion adapters are installed.


Controller 1

Controller 2


0a 0c0a 0c

Figure 6: 62xx single-fabric HA configuration

Attribute Value

Fully redundant No, due to the single fabric

Type of fabric Single fabric



One to the maximum number of supported 4-Gb or 8-Gb FCports using target expansion adapters per controller

Type of configuration HA configuration


62xx: Multifabric HA configurationsYou can connect hosts to both controllers in an HA configuration through two or more FC switchfabrics for redundancy.




Controller 1

Controller 2


0a 0c 0b 0d

0b 0d0a 0c

Figure 7: 62xx multifabric HA configurations

Attribute Value

Fully redundant Yes

Type of fabric Multifabric


Attribute Value





62xx: Direct-attached single-controller configurationYou can connect hosts directly to FC target ports on a single controller. Each host can connect to oneport, or to two ports for redundancy. The number of hosts is limited by the number of available targetports.

If you use multiple paths to a LUN, multipathing software is required on the host.

Direct-attached configurations typically need the FC ports set to loop mode. Be sure to follow therecommendation of your host operating system provider for FC port settings. You can use the DataONTAP fcp config mediatype command to set the target ports; see the fcp man page for moreinformation about the command.

Host 1

Host 2 Host 3

Host 2 Host NHost N

Figure 8: 62xx direct-attached single-controller configuration


Attribute Value


Type of fabric None





62xx: Direct-attached HA configurationsYou can connect hosts directly to FC target ports on both controllers in an HA configuration. Thenumber of hosts is limited by the number of available target ports.




Host

Controller 1

Controller 2

0c

0c

Figure 9: 62xx direct-attached HA configuration


Attribute Value

Fully redundant Yes

Type of fabric None





60xx supported configurations60xx controllers are available in single-controller and HA pairs.

The 6030 and 6070 systems have eight onboard 2-Gb FC ports per controller and each one can beconfigured as either a target or initiator FC port. 2-Gb target connections are supported with theonboard 2-Gb ports. 4-Gb and 8-Gb target connections are supported with 4-Gb and 8-Gb targetexpansion adapters. You cannot use both 2-Gb and 4-Gb or 8-Gb targets on the same controller or ontwo different controllers in an HA pair.

The 6040 and 6080 systems have eight onboard 4-Gb FC ports per controller and each one can beconfigured as either a target or initiator FC port. 4-Gb target connections are supported with theonboard 4-Gb ports configured as targets.

Additional target connections can be supported using 4-Gb and 8-Gb target expansion adapters.


The port pairs on a 60xx controller that share an ASIC are 0a+0b, 0c+0d, 0e+0f, and 0g+0h.

The following table shows the preferred port usage order for onboard FC target ports. For targetexpansion adapters, the preferred slot order is given in the System Configuration Guide for theversion of Data ONTAP software being used by the controllers.


1 0h

2 0h, 0d



3 0h, 0d, 0f

4 0h, 0d, 0f, 0b

5 0h, 0d, 0f, 0b, 0g

6 0h, 0d, 0f, 0b, 0g, 0c

7 0h, 0d, 0f, 0b, 0g, 0c, 0e

8 0h, 0d, 0f, 0b, 0g, 0c, 0e, 0a

60xx: Single-controller configurationsYou can connect hosts to a single controller using a single FC fabric or with multiple FC fabrics. Ifyou use multiple paths, multipathing software is required on the host.


Note: The FC target port numbers in the following figures are examples. The actual port numbersmight vary depending on whether you are using onboard ports or FC target expansion adapters. Ifyou are using FC target expansion adapters, the target port numbers also depend on the expansionslots into which your target expansion adapters are installed.




Controller


0c 1a 0d 1b


Attribute Value







Related references

60xx target port configuration recommendations on page 23

60xx: Single-fabric HA pairYou can connect hosts to both controllers in an HA pair using a single FC switch.





Figure 12: 60xx single-fabric HA pair

Attribute Value







Related references



60xx: Multifabric HA pairYou can connect hosts to both controllers in an HA pair using two or more FC switch fabrics forredundancy.



Figure 13: 60xx multifabric HA pair

Attribute Value

Fully redundant Yes




Attribute Value




Related references


60xx: Direct-attached single-controller configurationYou can connect hosts directly to FC target ports on a single controller. Each host can connect to oneport, or to two ports for redundancy. The number of hosts is limited by the number of available targetports.



Figure 14: 60xx direct-attached single-controller configuration


Attribute Value


Type of fabric None





Related references


60xx: Direct-attached HA pairYou can connect hosts directly to FC target ports on both controllers in an HA pair. The number ofhosts is limited by the number of available target ports.





Figure 15: 60xx direct-attached HA pair

Attribute Value

Fully redundant Yes

Type of fabric None





Related references


32xx supported fibre channel configurations32xx systems are available in single-controller and HA configurations.

The 32xx systems have two onboard 4-Gb FC ports per controller that can be configured as FC targetports. There are also two SAS ports for connecting disk shelves.




The following table shows the preferred port usage order for 32xx onboard FC target ports. For targetexpansion adapters, the preferred slot order is given in the System Configuration Guide for theversion of Data ONTAP software being used by the controllers.


1 0c

2 0c, 0d

32xx: Single-controller configurationsYou can connect hosts to a single controller using a single FC fabric or with multiple FC fabrics.




Controller 1


0c 0d




Controller


0c 1a 0d 1b


Attribute Value







32xx: Single-fabric HA configurationsYou can connect hosts to both controllers in an HA configuration using a single FC switch.





Controller 1

Controller 2


0c 0d0c 0d

Figure 18: 32xx single-fabric HA configuration

Attribute Value







32xx: Multifabric HA configurationsYou can connect hosts to both controllers in an HA configuration using two or more FC switchfabrics for redundancy.






Controller 1

Controller 2


0c 1a 0d 1b

0d 1b0c 1a

Figure 19: 32xx multifabric HA configuration

Attribute Value

Fully redundant Yes






32xx: Direct-attached single-controller configurationsYou can connect hosts directly to FC target ports on a single controller. Each host can connect to oneport, or to two ports for redundancy. The number of hosts is limited by the number of available targetports.





Host 1

Host 1

Host 2

Host 3 Host 1 Host 2Host N

Controller 1 Controller 1 Controller 1

Figure 20: 32xx direct-attached single-controller configurations

Attribute Value


Type of fabric None





32xx: Direct-attached HA configurationsYou can connect hosts directly to FC target ports on both controllers in an HA configuration. Thenumber of hosts is limited by the number of available target ports.





Host

Controller 1

Controller 2

0c0c

Figure 21: 32xx direct-attached HA configuration

Attribute Value

Fully redundant Yes

Type of fabric None

FC ports or adapters One to the maximum number of supported onboard FC ports per controller

One to the maximum number of supported 4-Gb or 8-Gb FC targetexpansion adapters


FAS2240 supported configurationsFAS2240 systems are available in single-controller and HA configurations.

The FAS2240 systems have no onboard FC ports. For FC configurations, you must add the optional2-port 8-Gb FC adapter in slot 1. No other FC ports are available.

Each port on the optional FAS2240 FC adapter can be individually configured as either a target orinitiator FC port using the fcadmin config command, just like the onboard FC ports on othercontroller models.


There are also two SAS ports for connecting disk shelves.

FAS2240: Single-fabric single-controller configurationYou can connect hosts to a single controller using a single FC switch. If you use multiple paths,multipathing software is required on the host.


Note: The following illustration shows the storage controllers side by side, which is how they aremounted in the FAS2240-2. For the FAS2240-4, the controllers are mounted one above the other.There is no difference between the SAN configuration for the two models.

Controller 1

1a 1b


Figure 22: FAS2240 single-fabric single-controller configuration

Attribute Value

Fully redundant No, due to the single fabric and single controller



FC ports or adapters One or two ports on the 2-port 8-Gb FC expansion adapterconfigured as targets



FAS2240: Single-fabric HA pairYou can connect hosts to both controllers in an HA pair using a single FC switch.


Note: The following illustration shows the storage controllers side by side, which is how they aremounted in the FAS2240-2. For the FAS2240-4, the controllers are mounted one above the other.There is no difference in the SAN configuration between the two models.

Controller 1 Controller 2

1a 1b 1a 1b


Figure 23: FAS2240 single-fabric HA pair

Attribute Value




FC ports or adapters One or two ports on the 2-port 8-Gb FC expansion adapterconfigured as targets on each controller



FAS2240: Multifabric single-controller configurationYou can connect hosts to one controller using two or more FC switch fabrics for redundancy.



Controller 1

1a 1b


Figure 24: FAS2240 multifabric single-controller configuration

Attribute Value




FC ports or adapters Both ports on the supported 2-port 8-Gb FC expansion adapterconfigured as targets



FAS2240: Multifabric HA pairYou can connect hosts to both controllers in an HA pair using two or more FC switch fabrics forredundancy.




1a 1b 1a 1b


Figure 25: FAS2240 multifabric HA pair

Attribute Value

Fully redundant Yes



FC ports or adapters Both ports on the supported 2-port 8-Gb FC expansion adapterconfigured as targets on each controller



FAS2240: Direct-attached single-controller configurationsYou can connect hosts directly to FC target ports on a single controller. Each host can connect to oneport, or to two ports for redundancy. The number of hosts is limited by the number of available targetports.




1a 1b 1a 1b

Host 1 Host 2 Host 1


Figure 26: FAS2240 direct-attached single-controller configurations

Attribute Value


Type of fabric None


FC ports or adapters One or two ports on the 2-port 8-Gb FC expansion adapterconfigured as targets



FAS2240: Direct-attached HA pairYou can connect hosts directly to FC target ports on both controllers in an HA pair. The number ofhosts is limited by the number of available target ports.



Note: The following illustration shows the storage controllers side by side, which is how they aremounted in the FAS2240-2. For the FAS2240-4, the controllers are mounted one above the other.There is no difference in the SAN configuration for the two models.


1a 1b 1a 1b

Host 1 Host 2

Figure 27: FAS2240 direct-attached HA pair

Attribute Value

Fully redundant Yes

Type of fabric None


FC ports or adapters One or two ports on the 2-port 8-Gb FC expansion adapterconfigured as targets on each controller



31xx supported fibre channel configurations31xx systems are available in single-controller and HA pairs.

The 31xx systems have four onboard 4-Gb FC ports per controller and each port can be configured aseither an FC target port or an initiator port. For example, you can configure two ports as SAN targetsand two ports as initiators for disk shelves.



The port pairs on a 31xx controller that share an ASIC are 0a+0b and 0c+0d.



1 0d

2 0d, 0b

3 0d, 0b, 0c

4 0d, 0b, 0c, 0a

31xx: Single-controller configurationsYou can connect hosts to a single controller using a single FC fabric or with multiple FC fabrics. Ifyou use multiple paths, multipathing software is required on the host.






Controller


0c 1a 0d 1b


Attribute Value





Attribute Value




Related references


31xx: Single-fabric HA pairYou can connect hosts to both controllers in an HA pair using a single FC switch.



Figure 30: 31xx single-fabric HA pair


Attribute Value







Related references


31xx: Multifabric HA pairYou can connect hosts to both controllers in an HA pair using two or more FC switch fabrics forredundancy.




Figure 31: 31xx multifabric HA pair

Attribute Value

Fully redundant Yes






Related references


31xx: Direct-attached single-controller configurationsYou can connect hosts directly to FC target ports on a single controller. Each host can connect to oneport, or to two ports for redundancy. The number of hosts is limited by the number of available targetports.





Figure 32: 31xx direct-attached single-controller configurations

Attribute Value


Type of fabric None





Related references



31xx: Direct-attached HA pairYou can connect hosts directly to FC target ports on both controllers in an HA pair. The number ofhosts is limited by the number of available target ports.




Figure 33: 31xx direct-attached HA pair

Attribute Value

Fully redundant Yes

Type of fabric None




Related references



30xx supported configurations30xx systems are available in single-controller and HA pairs.

Each 3040 and 3070 controller supports 4-Gb and 8-Gb FC target expansion adapters.


The port pairs on a 30xx controller that share an ASIC are 0a+0b, 0c+0d.



1 0d

2 0d, 0b

3 0d, 0b, 0c

4 0d, 0b, 0c, 0a

3040 and 3070 supported configurations3040 and 3070 systems are available in single-controller and HA pairs.

The 3040 and 3070 controllers have four onboard 4-Gb FC ports per controller and each port can beconfigured as either an FC target port or an initiator port. For example, you can configure two portsas SAN targets and two ports as initiators for disk shelves.

3040 and 3070: Single-controller configurations

You can connect hosts to single controllers using a single FC fabric or with multiple FC fabrics. Ifyou use multiple paths, multipathing software is required on the host.




Figure 34: 3040 and 3070 single-fabric single-controller configuration


Controller


0c 1a 0d 1b

Figure 35: 3040 and 3070 multifabric single-controller configuration

Attribute Value





Attribute Value




Related references


3040 and 3070: Single-fabric HA pair

You can connect hosts to both controllers in an HA pair using a single FC switch.



Figure 36: 3040 and 3070 single-fabric HA pair


Attribute Value







Related references


3040 and 3070: Multifabric HA pair

You can connect hosts to both controllers in an HA pair using two or more FC switch fabrics forredundancy.




Figure 37: 3040 and 3070 multifabric HA pair

Attribute Value

Fully redundant Yes






Related references


3040 and 3070: Direct-attached single-controller configurations

You can connect hosts directly to FC target ports on a single controller. Each host can connect to oneport, or to two ports for redundancy. The number of hosts is limited by the number of available targetports.




Figure 38: 3040 and 3070 direct-attached single-controller configurations

Attribute Value


Type of fabric None





Related references


3040 and 3070: Direct-attached HA pair

You can connect hosts directly to FC target ports on both controllers in an HA pair. The number ofhosts is limited by the number of available target ports.





Figure 39: 3040 and 3070 direct-attached HA pair

Attribute Value

Fully redundant Yes

Type of fabric None




Related references



FAS2040 supported configurationsFAS2040 systems are available in single-controller and HA pairs.

The FAS2040 have two onboard 4-Gb FC ports per controller. You can configure these ports aseither target ports for FC SANs or initiator ports for connecting to disk shelves.

FAS2040: Single-fabric single-controller configurationYou can connect hosts to a single controller using a single FC switch. If you use multiple paths,multipathing software is required on the host.


Note: The FC target port numbers in the following illustration are examples.

Figure 40: FAS2040 single-fabric single-controller configuration

Attribute Value

Fully redundant No, due to the single fabric and single controller






FAS2040: Single-fabric HA pairYou can connect hosts to both controllers in an HA pair using a single FC switch.



Figure 41: FAS2040 single-fabric HA pair

Attribute Value







FAS2040: Multifabric single-controller configurationYou can connect hosts to one controller using two or more FC switch fabrics for redundancy.



Figure 42: FAS2040 multifabric single-controller configuration

Attribute Value







FAS2040: Multifabric HA pairYou can connect hosts to both controllers in an HA pair using two or more FC switch fabrics forredundancy.



Figure 43: FAS2040 multifabric HA pair

Attribute Value

Fully redundant Yes






FAS2040: Direct-attached single-controller configurationsYou can connect hosts directly to FC target ports on a single controller. Each host can connect to oneport, or to two ports for redundancy. The number of hosts is limited by the number of available targetports.


Direct-attached configurations typically need the FC ports set to loop mode. Be sure to follow therecommendation of your host operating system provider for FC port settings. You can use the DataONTAP fcp config mediatype command to set the target ports; see the fcp man page for moreinformation about this command.


Figure 44: FAS2040 direct-attached single-controller configurations

Attribute Value


Type of fabric None




FAS2040: Direct-attached HA pairYou can connect hosts directly to FC target ports on both controllers in an HA pair. The number ofhosts is limited by the number of available target ports.





Figure 45: FAS2040 direct-attached HA pair

Attribute Value

Fully redundant Yes

Type of fabric None





Fibre Channel over Ethernet overview

Fibre Channel over Ethernet (FCoE) is a model for connecting hosts to storage systems. As withFibre Channel (FC), FCoE maintains existing FC management and controls. However, the hardwaretransport is a lossless 10-Gb Ethernet network.

Setting up an FCoE connection requires one or more supported converged network adapters (CNAs)in the host, connected to a supported FCoE switch. The CNA is a consolidation point and effectivelyserves as both an FC HBA and an Ethernet adapter.

The CNA is presented to the host as both an FCoE HBA and a 10-Gb Ethernet adapter. The FCoEHBA portion of the CNA handles the FCoE traffic when traffic is sent and received as FC framesmapped into Ethernet packets (FC over Ethernet). The Ethernet adapter portion of the CNA handlesthe standard Ethernet host IP traffic, such as iSCSI, CIFS, NFS, and HTTP, for the host. Both theFCoE and standard Ethernet portions of the CNA communicate over the same Ethernet port, whichconnects to the FCoE switch.

It is recommended that you configure jumbo frames (MTU = 9000) for the Ethernet adapter portionof the CNA. You cannot change the MTU for the FCoE portion of the adapter.

Note: Unified target adapters (UTAs) are 10-Gb converged network adapters that you install onyour storage systems. Starting with Data ONTAP 8.0.1, you can use UTAs for non-FCoE IP trafficsuch as NFS, CIFS, or iSCSI. Data ONTAP 8.0 and earlier do not support UTAs for non-FCoE IPtraffic (NFS, CIFS or iSCSI).

In general, you configure and use FCoE connections just like traditional FC connections.

Note: For detailed information about how to set up and configure your host to run FCoE, see yourhost documentation.

FCoE initiator and target combinationsCertain combinations of FCoE and traditional FC initiators and targets are supported.

FCoE initiators

You can use FCoE initiators in host computers with both FCoE and traditional FC targets in storagecontrollers. The FCoE initiator must connect to an FCoE DCB (data center bridging) switch; directconnection to a target is not supported.

The following table lists the supported combinations.

Initiator Target Supported?

FC FC Yes

63

Initiator Target Supported?

FC FCoE Yes

FCoE FC Yes

FCoE FCoE Yes

FCoE targets

You can mix FCoE target ports with 4-Gb or 8-Gb FC ports on the storage controller regardless ofwhether the FC ports are add-in target adapters or onboard ports. You can have both FCoE and FCtarget adapters in the same storage controller.

Note: The rules for combining onboard and expansion FC ports still apply.

Related references

Rules for combining onboard and expansion FC ports on page 13

Fibre Channel over Ethernet supported hop countThe maximum supported FCoE hop count between a host and storage system depends on the switchsupplier and storage system support for FCoE configurations.

The hop count is defined as the number of switches in the path between the initiator (host) and target(storage system). Cisco also refers to this value as the diameter of the SAN fabric.

For FCoE, you can have FCoE switches connected to FC switches.

For end-to-end FCoE connections, the FCoE switches must be running a firmware version thatsupports Ethernet inter-switch links (ISLs).

The following table lists the maximum supported hop counts:

Switch supplier Supported hop count

Cisco 7

Up to 3 of the switches can be FCoE switches.

Fibre Channel over Ethernet supported configurationsSupported FCoE native configurations include single-fabric and multifabric configurations. Bothsingle-controller and HA configurations are supported.

Supported storage systems with native FCoE target expansion adapters (called unified target adaptersor UTAs) are the 62xx, 60xx, 32xx,


The FCoE initiator with FC target configuration is also supported on all storage systems using anFCoE/DCB switch.

Note: The following configuration diagrams are examples only. Most supported FC and iSCSIconfigurations on supported storage systems can be substituted for the example FC or iSCSIconfigurations in the following diagrams. However, direct-attached configurations are notsupported in FCoE.

Note: While iSCSI configurations allow any number of Ethernet switches, there must be noadditional Ethernet switches in FCoE configurations. The CNA must connect directly to the FCoEswitch.

FCoE: FCoE initiator to FC target configurationYou can connect hosts to both controllers in an HA pair using FCoE initiators through FCoEswitches to FC target ports. This requires an FCoE switch that also has FC ports.

The FCoE initiator always connects to a supported FCoE switch. The FCoE switch can connectdirectly to an FC target, or can connect through FC switches to the FC target.

Note: The FC target expansion adapter port numbers (2a and 2b) in the following figure areexamples. The actual port numbers might vary, depending on the expansion slot in which the FCtarget expansion adapter is installed.

Fibre Channel over Ethernet overview | 65

Host 1

CNA Ports CNA Ports CNA Ports

Switch/Fabric 1

Controller 1

Controller 2

0d0b

0d0b

Switch/Fabric 2

Host 2 Host N

FCoE Switch

IP NetworkIP Network

FCoE Switch

DCBPorts

DCBPorts

FC Ports FC Ports

Figure 46: FCoE initiator to FC dual-fabric HA pair

Attribute Value

Fully redundant Yes

Type of fabric Dual fabric



One to the maximum number of supported 4-Gb or 8-Gb FCports per controller using FC target expansion adapters




FCoE: FCoE end-to-end configurationYou can connect hosts to both controllers in an HA pair. This connection is achieved using FCoEinitiators through DCB switches to FCoE target ports.

The FCoE target adapter is also called a unified target adapter or UTA. Like the CNA in a host, theUTA supports both FCoE and regular Ethernet traffic.

You can have multiple FCoE and FC switches in the path between the initiator and target, up to themaximum hop count limit. To connect FCoE switches to each other, the switches must run afirmware version that supports Ethernet ISLs.

Note: The FCoE target expansion adapter port numbers (2a and 2b) in the following figure areexamples. The actual port numbers might vary, depending on the expansion slot in which theFCoE target expansion adapter is installed.

Host 1

CNA Ports

UTA Ports

UTA Ports

CNA Ports CNA Ports

Controller 1

Controller 2

2b2a

2b2a

Host 2 Host N

FCoE Switch


FCoE Switch

DCBPorts

DCBPorts

DCBPorts

DCBPorts

Figure 47: FCoE end-to-end

Attribute Value

Fully redundant Yes


Different host operating systems Yes, with multiple host-configurations


Attribute Value

FCoE ports or adapters One or more FCoE target expansion adapters per controller



FCoE: FCoE mixed with FCYou can connect hosts to both controllers in an HA pair. This connection is achieved using FCoEinitiators through FCoE switches to FCoE and FC mixed target ports.


You can have multiple FCoE and FC switches in the path between the initiator and target, up to themaximum hop count limit. To connect FCoE switches to each other, the switches must run afirmware version that supports Ethernet ISLs.

Note: The FCoE target expansion adapter port numbers (2a and 2b) and FC target port numbers(4a and 4b) are examples. The actual port numbers might vary, depending on the expansion slotsin which the FCoE target expansion adapter and FC target expansion adapter are installed.


Host 1

Switch/Fabric 1

Controller 1

UTA Ports

UTA Ports

Controller 2

0d0b

0d0b

2b2a

2a2b

Switch/Fabric 2

Host 2 Host N


FCoE Switch


FCoE Switch

DCBPorts

DCBPorts

DCBPorts

DCBPorts

FCPorts

FCPorts

Figure 48: FCoE mixed with FC

Attribute Value

Fully redundant Yes



FC/FCoE ports or adapters One to the maximum number of supported onboard FC ports percontroller

One or more FCoE target expansion adapters per controller

At least one 4-Gb or 8-Gb FC target expansion adapter percontroller




FCoE: FCoE mixed with IP storage protocolsYou can connect hosts to both controllers in an HA pair using FCoE initiators through FCoEswitches to FCoE target ports. You can also run non-FCoE Ethernet traffic through the sameswitches.


You can have multiple FCoE and FC switches in the path between the initiator and target, up to themaximum hop count limit. To connect FCoE switches to each other over Ethernet, the switches mustrun a firmware version that supports Ethernet ISLs. You can also connect switches using FC ISLs.

The FCoE ports are connected to DCB ports on the FCoE switches. FCoE ports cannot use traditionallink aggregation to a single switch. Cisco switches support a special type of link aggregation calledVirtual Port Channel that does support FCoE. A Virtual Port Channel aggregates individual links totwo switches. You can also use the Virtual Port Channel for other Ethernet traffic. For moreinformation about configuring Virtual Port Channels, see Technical Report TR-3800: Fibre Channelover Ethernet (FCoE) End-to-End Deployment Guide or your Cisco switch documentation.

Ports used for traffic other than FCoE, including NFS, CIFS, iSCSI, and other Ethernet traffic, canuse regular Ethernet ports on the FCoE switches.

Note: The FCoE target expansion adapter port numbers (2a and 2b) and the Ethernet port numbers(e0a and e0b) in the following figure are examples. The actual port numbers might vary,depending on the expansion slots in which the FCoE target expansion adapters are installed.



UTA Ports

UTA Ports

Host 1

Controller 1

Controller 2

2b2a

2b2a

e0a e0b

e0ae0b

Host 2 Host N

FCoE Switch


FCoE Switch

DCBPorts

DCBPorts

DCBPorts

DCB/Ethernet

Ports

DCBPorts

DCB/Ethernet

Ports

Figure 49: FCoE mixed with IP storage protocols

Attribute Value

Fully redundant Yes



FCoE ports or adapters One or more FCoE target expansion adapters per controller



Related information

TR-3800: Fibre Channel over Ethernet (FCoE) End-to-End Deployment Guide -media.netapp.com/documents/TR-3800.pdf


http://media.netapp.com/documents/TR-3800.pdf

http://media.netapp.com/documents/TR-3800.pdf

Fibre Channel and FCoE zoning

An FC or FCoE zone is a subset of the fabric that consists of a group of FC or FCoE ports or nodesthat can communicate with each other. You must contain the nodes within the same zone to allowcommunication.

Reasons for zoning

• Zoning reduces or eliminates cross talk between initiator HBAs. This occurs even in smallenvironments and is one of the best arguments for implementing zoning. The logical fabricsubsets created by zoning eliminate crosstalk problems.

• Zoning reduces the number of available paths to a particular FC or FCoE port and reduces thenumber of paths between a host and a particular LUN that is visible. For example, some host OSmultipathing solutions have a limit on the number of paths they can manage. Zoning can reducethe number of paths that an OS multipathing driver sees. If a host does not have a multipathingsolution installed, you need to verify that only one path to a LUN is visible.

• Zoning increases security because there is limited access between different nodes of a SAN.• Zoning improves SAN reliability by isolating problems that occur and helps to reduce problem

resolution time by limiting the problem space.

Recommendations for zoning

• You should implement zoning anytime four or more hosts are connected to a SAN.• Although World Wide Node Name zoning is possible with some switch vendors, World Wide

Port Name zoning is recommended.• You should limit the zone size while still maintaining manageability. Multiple zones can overlap

to limit size. Ideally, a zone is defined for each host or host cluster.• You should use single-initiator zoning to eliminate crosstalk between initiator HBAs.

Port zoningPort zoning, also referred to as hard zoning, specifies the unique fabric N_port IDs of the ports to beincluded within the zone. The switch and switch port are used to define the zone members.

Port zoning provides the following advantages:

• Port zoning offers improved security because it is not possible to breach the zoning by usingWWN spoofing. However, if someone has physical access to the switch, replacing a cable canallow access.

• In some environments, port zoning is easier to create and manage because you only work with theswitch or switch domain and port number.

73

World Wide Name based zoningZoning based on World Wide Name (WWN) specifies the WWN of the members to be includedwithin the zone. Depending on the switch vendor, either World Wide Node Name or World WidePort Names can be used. The recommendation is that you should use World Wide Port Name zoningwhen possible.

WWN zoning provides flexibility because access is not determined by where the device is physicallyconnected to the fabric. You can move a cable from one port to another without reconfiguring zones.

Individual zonesIn the standard zoning configuration for a simple environment where each host is shown in anindividual zone, the zones overlap because the storage ports are included in each zone to allow eachhost to access the storage.

Each host can see all of the FC target ports but cannot see or interact with the other host ports.

For example, Zone 1 would consist of switch ports 1, 2, 3, 4 (storage ports) and 5 (Host1 port).Zone 2 would consist of switch ports 1, 2, 3, 4 (storage ports) and 6 (Host2 port), and so on.

This diagram shows only a single fabric, but multiple fabrics are supported. Each subsequent fabrichas the same zone structure.


Figure 50: Hosts in individual zones

Single-fabric zoningZoning and multipathing software, used together, prevents possible controller failure in a single-fabric environment. Without multipathing software in a single-fabric environment, hosts are notprotected from a possible controller failure.

In the following figure, Host1 and Host2 do not have multipathing software and are zoned so thatthere is only one path to each LUN (Zone 1). Therefore, Zone 1 contains only one of the two storageports.

Even though the host has only one HBA, both storage ports are included in Zone 2. The LUNs arevisible through two different paths, one going from the host FC port to storage port 0 and the othergoing from host FC port to storage port 1.

Because this figure contains only a single fabric, it is not fully redundant. However, as shown, Host3and Host4 have multipathing software that protects against a possible controller failure. They arezoned so that a path to the LUNs is available through each of the controllers.

Fibre Channel and FCoE zoning | 75

Figure 51: Single-fabric zoning

Dual-fabric HA pair zoningZoning can separate hosts in a topology to eliminate HBA cross talk. Zoning can also prevent a hostfrom accessing LUNs from a storage system in a different zone.

The following figure shows a configuration where Host1 accesses LUNs from controller 1 and Host2accesses LUNs from controller 2. Each controller is an HA pair and both are fully redundant.

Multiple storage systems are shown in this figure, but they are not necessary for redundancy.


Figure 52: Dual-fabric zoning

Fibre Channel and FCoE zoning | 77

Shared SAN configurations

Shared SAN configurations are defined as hosts that are attached to both NetApp and non-NetAppstorage systems. Accessing NetApp storage systems and other vendors' storage systems from a singlehost is supported as long as several requirements are met.

To access NetApp storage systems and other vendors' storage systems from a single host requires:

• Native Host OS multipathing or VERITAS DMP is used for multipathing (see exception for EMCPowerPath co-existence below)

• NetApp configuration requirements (such as timeout settings) as specified in the appropriateNetApp Host Utilities documents are met

• Single_image cfmode is used

Support for Native Host OS multipathing in combination with EMC PowerPath is supported for thefollowing configurations. For configurations that do meet these requirements, a PVR is required todetermine supportability.

Host Supported configuration

Windows EMC CX3, CX4, and VNX arrays with PowerPath 4.5 or later connected to a NetAppstorage system using Data ONTAP DSM for Windows MPIO

Solaris EMC CX3, CX4, and VNX arrays PowerPath 5 or later connected to a NetApp storagesystem using SUN Traffic Manager (MPxIO)

AIX EMC CX3, CX4, and VNX arrays PowerPath 5 or later connected to a NetApp storagesystem using AIX MPIO

79

ALUA configurations

Asymmetric logical unit access (ALUA) is supported for certain combinations of host operatingsystems and host multipathing software.

ALUA is an industry standard protocol for identifying optimized paths between a storage system anda host computer. The administrator of the host computer does not need to manually select the paths touse.

You should use ALUA whenever the host configuration supports it. For information about whichspecific configurations support ALUA, see the Interoperability Matrix and the Host UtilitiesInstallation and Setup Guide for your host operating system

ALUA is enabled or disabled on the igroup to which the LUN is mapped. The default ALUA settingin Data ONTAP depends on the igroup type. ALUA is not supported for iSCSI paths.

For information about enabling ALUA on the storage system, see the Data ONTAP .

Related information

NetApp Interoperability Matrix - now.netapp.com/NOW/products/interoperability/Host Utilities documentation - now.netapp.com/NOW/knowledge/docs/san

81



Configuration limits for FC, FCoE, and iSCSIconfigurations

Configuration limits are available for FC, FCoE, and iSCSI configurations. In some cases, theoreticallimits might be higher, but the published limits are tested and supported.

SAN Configuration limit parameters and definitionsThere are a number of parameters and definitions related to FC, FCoE, and iSCSI configurationlimits.

Parameter Definition

Visible target portsper host (iSCSI)

The maximum number of target iSCSI Ethernet ports that a host can see oraccess on iSCSI-attached controllers.

Visible target portsper host (FC)

The maximum number of FC adapters that a host can see or access on theattached Fibre Channel controllers.

LUNs per host The maximum number of LUNs that you can map from the controllers to asingle host.

Paths per LUN The maximum number of accessible paths that a host has to a LUN.

Note: Using the maximum number of paths is not recommended.

Maximum LUN size The maximum size of an individual LUN on the respective operatingsystem.

LUNs per controlleror node

The maximum number of LUNs that you can configure per controller,including cloned LUNs and LUNs contained within cloned volumes. LUNscontained in Snapshot copies do not count in this limit and there is no limiton 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 singlevolume. LUNs contained in Snapshot copies do not count in this limit andthere is no limit on the number of LUNs that can be contained withinSnapshot copies.

FC port fan-in The maximum number of hosts that can connect to a single FC port on acontroller. Connecting the maximum number of hosts is generally notrecommended and you might need to tune the FC queue depths on the hostto achieve this maximum value.

83

Parameter Definition

FC port fan-out The maximum number of LUNs mapped to a host through a FC target porton a controller.

iSCSI sessions percontroller or node

The recommended maximum number of iSCSI sessions that you canconnect to a single controller. The general formula to calculate this is asfollows: Maximum sessions = 8 * System Memory divided by 512 MB.

Hosts per controller(FC)

The maximum number of hosts that you can connect to a controller.Connecting the maximum number of hosts is generally not recommendedand you might need to tune the FC queue depths on the host to achieve thismaximum value. This value assumes two initiators per host.

igroups per controller The maximum number of initiator groups that you can configure percontroller.

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 percontroller

The maximum number of LUN mappings per controller. For example, aLUN mapped to two igroups counts as two mappings.

LUN path namelength

The maximum number of characters in a full LUN name. Forexample, /vol/abc/def has 12 characters.

LUN size The maximum capacity of an individual LUN on a controller.

FC queue depthavailable per port

The usable queue depth capacity of each FC target port. The number ofLUNs is limited by available FC queue depth.

FC target ports percontroller or node

The maximum number of supported FC target ports per controller. FCinitiator ports used for back-end disk connections, for example, connectionsto disk shelves, are not included in this number.

Related information

Technical Report: NetApp Storage Controllers and Fibre Channel Queue Depth -now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/QuickRef/Queue_Depth.pdf

Host operating system limits for SAN configurationsEach host operating system has host-based configuration limits for FC, FCoE, and iSCSI.

The following table lists the maximum supported value for each parameter based on testing. Allvalues are for FC, FCoE, and iSCSI unless noted.


http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/QuickRef/Queue_Depth.pdf


Note: The values listed are the maximum supported by NetApp. The operating system vendormight support a different value. For best performance, do not configure your system at themaximum values.

Parameter Windows Linux HP-UX Solaris AIX ESX

Visible target portsper host

32 16 16 16 16 16

LUNs per host 64(Windows2000)

255(Windows2003)

255(Windows2008)

1024devicesmax(whereeach pathto a LUNis adevice)

11iv2: 512

11iv3:1024

512 1024 3.x: 256

4.x: 256

Localdrives,CD-ROM,and so oncountagainstthis value.

Paths per LUN 8 (max of1024 perhost)

8 (max of1024 perhost)

11iv2: 8

11iv3: 32

16 16 3.x: 8

4.x: 8

(max of1024 perhost)

Max LUN size 2 TB(MBR)

16 TB(GPT)Server2003 SP2and later

16 TB 11iv2: 2TB

11iv3: 16TB

16 TB 16 TB 2 TB

Related references

SAN Configuration limit parameters and definitions on page 83

62xx single-controller limitsEach system model has configuration limits for reliable operation. Do not exceed the tested limits.

The following table lists the maximum supported value for each parameter based on testing. Allvalues are for FC, FCoE, and iSCSI unless otherwise noted.

Note: The values listed are the maximum that can be supported. For best performance, do notconfigure your system at the maximum values.

Configuration limits for FC, FCoE, and iSCSI configurations | 85

The maximum number of LUNs and the number of HBAs that can connect to an FC port is limitedby the available queue depth on the FC target ports.

Parameter 6210 6240 6280

LUNs per controller 2,048 2,048 2,048


1966 1966 1966

LUNs per volume 2,048 2,048 2,048

Port fan-in 64 64 64

Connected hosts perstorage controller (FC)

256 256 256

iSCSI sessions percontroller

256 512 512

igroups per controller 1024 1024 1024

Initiators per igroup 256 256 256


4,096 8,192 8,192

LUN path name length 255 255 255

LUN size 16 TB 16 TB 16 TB

FC target ports percontroller

32 32 32

Related information


62xx HA configuration limitsEach system model has configuration limits for reliable operation. Do not exceed the tested limits.


Limits for HA configuration systems are NOT double the limits for single-controller systems. This isbecause one controller in the HA configuration must be able to handle the entire system load duringfailover.






Parameter 6210 6240 6280

LUNs per HA pair 4,096 4,096 4,096


1,966 1,966 1,966

LUNs per volume 2,048 2,048 2,048

FC port fan-in 64 64 64

Connected hosts perHA pair (FC)

512 512 512

iSCSI sessions per HApair

512 1,024 1,024

igroups per HA pair 2048 2048 2048


LUN mappings per HApair

8,192 8,192 8,192



FC target ports per HApair

64 64 64

Related information









Parameter 3210 3240 3270



1966 1966 1966

LUNs per volume 2,048 2,048 2,048



256 256 256


256 256 512




4,096 4,096 4,096




10 24 24

Related information


32xx HA configuration limitsEach system model has configuration limits for reliable operation. Do not exceed the tested limits.


Limits for HA configuration systems are NOT double the limits for single-controller systems. This isbecause one controller in the HA configuration must be able to handle the entire system load duringfailover.






Parameter 3210 3240 3270

LUNs per HAconfiguration

2,048 2,048 4,096


1,966 1,966 1,966

LUNs per volume 2,048 2,048 2,048


Connected hosts perHA configuration (FC)

256 256 256

512 (with PVRapproval)

iSCSI sessions per HAconfiguration

512 512 1,024

igroups per HAconfiguration

512 512 1024


LUN mappings per HAconfiguration

4,096 4,096 4,096



FC target ports per HAconfiguration

20 48 48

Related information





FAS2240 single-controller limitsEach system model has configuration limits for reliable operation. Do not exceed the tested limits.

The following table lists the maximum supported value for each parameter based on testing. Allvalues are for FC and iSCSI unless noted.



Parameter FAS2240

LUNs per controller 1,024

FC queue depth available per port 1,966

LUNs per volume 1,024

FC port fan-in 64

Connected hosts per controller (FC) 128

iSCSI sessions per controller 128

igroups per controller 256

Initiators per igroup 256

LUN mappings per controller 4,096

LUN path name length 255

LUN size 16 TB

FC target ports per controller 2

Related information





FAS2240 HA configuration limitsEach system model has configuration limits for reliable operation. Do not exceed the tested limits.

The following table lists the maximum supported value for each parameter based on testing. Allvalues are for FC and iSCSI unless noted.

Limits for HA pair systems are NOT double the limits for single-controller systems. This is becauseone controller in the HA pair must be able to handle the entire system load during failover.



Parameter FAS2240

LUNs per HA pair 1,024



FC port fan-in 64

Connected hosts per HA pair (FC) 128

iSCSI sessions per HA pair 128

igroups per HA pair 256


LUN mappings per HA pair 4,096


LUN size 16 TB

FC target ports per HA pair 4

Related information





60xx and 31xx single-controller limitsEach system model has configuration limits for reliable operation. Do not exceed the tested limits.




Parameter 31xx 6030 or 6040 6070 or 6080



1,966 1,966 1,966

LUNs per volume 2,048 2,048 2,048



256 256 256


256 256 512




4,096 8,192 8,192




16 16 16

Related references



Related information


60xx and 31xx HA pair limitsEach system model has configuration limits for reliable operation. Do not exceed the tested limits.







4,096 (available on the3160A and 3170A withPVR approval)

2,048

4,096 (with PVRapproval)

4,096


1966 1966 1966

LUNs per volume 2,048 2,048 2,048


Connected hosts perHA pair (FC)

256

512 (available on the3160A and 3170A withPVR approval)

256


256


iSCSI sessions per HApair

512 512 1,024

igroups per HA pair 512 2048 2048






LUN mappings per HApair

4,096

8,192 (available on the3160A and 3170A withPVR approval)

8,192 8,192



FC target ports per HApair

32 32 32

Related references


Related information






Parameter 3040 and 3070




Port fan-in 64

Connected hosts per storage controller (FC) 256





Parameter 3040 and 3070





LUN size 16 TB


Related references


Related information


30xx HA pair limitsEach system model has configuration limits for reliable operation. Do not exceed the tested limits.





Parameter 3040A and 3070A




FC port fan-in 64





Parameter 3040A and 3070A






LUN size 16 TB


Related references


Related information


FAS2040 single-controller limitsEach system model has configuration limits for reliable operation. Do not exceed the tested limits.




Parameter FAS2040




FC port fan-in 64

Connected hosts per controller (FC) 128





Parameter FAS2040





LUN size 16 TB


Related references


Related information


FAS2040 HA pair configuration limitsEach system model has configuration limits for reliable operation. Do not exceed the tested limits.





Parameter FAS2040A




FC port fan-in 64





Parameter FAS2040A






LUN size 16 TB


Related references


Related information





Copyright information

Copyright © 1994–2012 NetApp, Inc. All rights reserved. Printed in the U.S.

No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in anelectronic retrieval system—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license anddisclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice.NetApp assumes no responsibility or liability arising from the use of products described herein,except as expressly agreed to in writing by NetApp. The use or purchase of this product does notconvey a license under any patent rights, trademark rights, or any other intellectual property rights ofNetApp.

The product described in this manual may be protected by one or more U.S. patents, foreign patents,or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject torestrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

99

Trademark information

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri,ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, CampaignExpress, ComplianceClock, Cryptainer, CryptoShred, Data ONTAP, DataFabric, DataFort, Decru,Decru DataFort, DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful,gFiler, Go further, faster, Imagine Virtually Anything, Lifetime Key Management, LockVault,Manage ONTAP, MetroCluster, MultiStore, NearStore, NetCache, NOW (NetApp on the Web),Onaro, OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX, SANscreen,SANshare, SANtricity, SecureAdmin, SecureShare, Select, Service Builder, Shadow Tape,Simplicity, Simulate ONTAP, SnapCopy, SnapDirector, SnapDrive, SnapFilter, SnapLock,SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot,SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror,Tech OnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager, VPolicy, WAFL,Web Filer, and XBB are trademarks or registered trademarks of NetApp, Inc. in the United States,other countries, or both.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. A complete and current list ofother IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.

Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the United Statesand/or other countries. Microsoft is a registered trademark and Windows Media is a trademark ofMicrosoft Corporation in the United States and/or other countries. RealAudio, RealNetworks,RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia,RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the United States and/or othercountries.

All other brands or products are trademarks or registered trademarks of their respective holders andshould be treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.

101

http://www.ibm.com/legal/copytrade.shtml

How to send your comments

You can help us to improve the quality of our documentation by sending us your feedback.

Your feedback is important in helping us to provide the most accurate and high-quality information.If you have suggestions for improving this document, send us your comments by email to [email protected]. To help us direct your comments to the correct division, include in thesubject line the product name, version, and operating system.

You can also contact us in the following ways:

• NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.• Telephone: +1 (408) 822-6000• Fax: +1 (408) 822-4501• Support telephone: +1 (888) 463-8277

103

mailto:[email protected]

Index10-Gb 6320xx

HA pair configuration limits 97single-controller limits 96

2240FC configurations 36direct-attached HA pair FC configurations 42direct-attached single-controller FC configurations

41HA pair configuration limits 91multifabric HA pair FC configurations 40multifabric single-controller FC configurations 39single-controller limits 90single-fabric HA pair FC configurations 38single-fabric single-controller FC configurations 37

3040 and 3070direct-attached HA pair FC configurations 55direct-attached single-controller FC configurations

54multifabric HA pair FC configurations 53single-controller FC configurations 50single-fabric HA pair FC configurations 52

30xxFC configurations 50HA pair configuration limits 95single-controller configuration limits 94target port configuration 50

31xxFC configurations 43direct-attached HA pair FC configurations 49direct-attached single-controller FC configurations

47HA pair configuration limits 93multifabric HA pair FC configurations 46single-controller configuration limits 92single-controller FC configurations 43single-fabric HA pair FC configurations 45target port configuration 43

32xxFC configurations 30direct-attached HA FC configurations 35direct-attached single-controller FC configurations

34HA configuration limits 88multifabric HA configuration 33single-controller configuration limits 87

single-controller FC configurations 31single-fabric HA configuration 32target port configuration 31

4-Gb FC portsupported speed 15


28HA pair configuration limits 93multifabric HA pair FC configurations 27single-controller configuration limits 92single-controller FC configurations 24single-fabric HA pair FC configurations 25target port configuration 23


21HA configuration limits 86multifabric HA pair FC configurations 20single-controller configuration limits 85single-controller FC configurations 17single-fabric HA pair FC configurations 18target port configuration 16

8-Gb FC portsupported speed 15

A

AIXhost configuration limits 84

ALUA configurations 81asymmetric logical unit access (ALUA) configurations

81

C

configuration limits20xx HA pair storage systems 9720xx single-controller storage systems 962240 HA pair storage systems 912240 single-controller storage systems 9030xx HA pair storage systems 95

Index | 105

30xx single-controller storage systems 9431xx HA pair storage systems 9331xx single-controller storage systems 9232xx HA configurations 8832xx single-controller storage systems 8760xx HA pair storage systems 9360xx single-controller storage systems 9262xx HA configuration storage systems 8662xx single-controller storage systems 85by host operating system 84parameters defined 83

configurations2240 FC configurations 3630xx FC configurations 5031xx FC configurations 4332xx FC configurations 3060xx FC configurations 2362xx FC configurations 16FAS20xx FC configurations 57FC 13FCoE 64FCoE initiator to FC target 65FCoE initiator to FCoE and FC mixed target 68FCoE initiator to FCoE target 67FCoE initiator to FCoE target mixed with IP traffic

70iSCSI 7

configurations, 2240direct-attached HA pair FC configuration 42direct-attached single-controller FC configurations

41multifabric HA pair FC configuration 40multifabric single-controller FC configurations 39single-fabric HA pair FC configuration 38single-fabric single-controller FC configurations 37

configurations, 3040 and 3070direct-attached HA pair FC configuration 55direct-attached single-controller FC configurations

54multifabric HA pair FC configuration 53single-controller FC configurations 50single-fabric HA pair FC configuration 52

configurations, 31xxdirect-attached HA pair FC configuration 49direct-attached single-controller FC configurations


configurations, 32xx

direct-attached HA FC configuration 35direct-attached single-controller FC configurations

34multifabric HA configuration 33single-controller FC configurations 31single-fabric HA configuration 32





configurations, FAS20xxdirect-attached HA pair FC configuration 61direct-attached single-controller FC configurations

61multifabric HA pair FC configuration 60multifabric single-controller FC configurations 59single-fabric HA pair FC configuration 58single-fabric single-controller FC configurations 57

D

DCB (data center bridging) switchfor FCoE 63

direct-attached configurationiSCSI 10

direct-attached HA FC configurations32xx 35

direct-attached HA pair FC configurations2240 423040 and 3070 5531xx 4960xx 2962xx 22FAS20xx 61

direct-attached single-controller FC configurations2240 413040 and 3070 5431xx 4732xx 3460xx 28


62xx 21FAS20xx 61

dynamic VLANs 11

E

EMC CLARiiONshared configurations 79

ESXhost configuration limits 84

expansion FC adaptersupported port speed 15

expansion FC portsusage rules 13

F

FAS20xxFC configurations 57direct-attached HA pair FC configurations 61direct-attached single-controller FC configurations

61multifabric HA pair FC configurations 60multifabric single-controller FC configurations 59single-fabric HA pair FC configurations 58single-fabric single-controller FC configurations 57

FC2240 configurations 3630xx configurations 5030xx target port configuration 5031xx configurations 4331xx target port configuration 4332xx configurations 3032xx target port configuration 3160xx configurations 2360xx target port configuration 2362xx configurations 1662xx target port configuration 16configurations overview 13FAS20xx configurations 57multifabric switch zoning 76onboard and expansion port usage rules 13port speed 15single-fabric switch zoning 75supported port speed 15switch configuration 15switch hop count 14switch port zoning 73switch WWN zoning 74switch zoning 73

switch zoning with individual zones 74FCoE

initiator and target combinations 63, 64supported configurations 64switch hop count 64switch zoning 73

FCoE configurationsFCoE initiator to FC target 65FCoE initiator to FCoE and FC mixed target 68FCoE initiator to FCoE target 67FCoE initiator to FCoE target mixed with IP traffic

70Fibre Channel over Ethernet (FCoE)

overview 63

H

HA pairiSCSI direct-attached configuration 10iSCSI multinetwork configuration 9iSCSI single-network configuration 7

hard zoningFC switch 73

HBA 63heterogeneous SAN

using VSAN 13hop count

for FC switches 14for FCoE switches 64

host multipathing softwarewhen required 16

HP-UXhost configuration limits 84

I

initiator FC portsonboard and expansion usage rules 13

initiatorsFCoE and FC combinations 63, 64

IP trafficin FCoE configurations 70

iSCSIconfigurations 7direct-attached configuration 10dynamic VLANs 11multinetwork configuration 9single-network configuration 7static VLANs 11using VLANs 11

Index | 107

LLinux

host configuration limits 84

MMPIO software

when required 16multifabric HA pair FC configurations

2240 403040 and 3070 5331xx 4632xx 3360xx 2762xx 20FAS20xx 60

multifabric single-controller FC configurations2240 393040 and 3070 5031xx 4332xx 3160xx 2462xx 17FAS20xx 59

multipathing softwarewhen required 16

Oonboard FC port

supported port speed 15onboard FC ports

usage rules 13

Pparameters

configuration limit definitions 83point-to-point

FC switch port topology 15port speed

supported for FC 15port topology

FC switch 15port zoning

FC switch 73PowerPath

with shared configurations 79

SSAN configuration limits

by host operating system 84parameters defined 83

shared SAN configurations 79single-fabric HA configurations

32xx 32single-fabric HA pair FC configurations

2240 383040 and 3070 5231xx 4560xx 2562xx 18FAS20xx 58

single-fabric single-controller FC configurations2240 373040 and 3070 5031xx 4332xx 3160xx 2462xx 17FAS20xx 57

soft zoningFC switch 74

Solarishost configuration limits 84

static VLANs 11supported configurations

FCoE 64switch

FC configuration 15FC hop count 14FC multifabric zoning 76FC port zoning 73FC single-fabric zoning 75FC WWN zoning 74FC zoning 73FC zoning with individual zones 74FCoE hop count 64FCoE zoning 73

T

target FC portsonboard and expansion usage rules 13

target port configurations30xx 5031xx 4332xx 3160xx 2362xx 16

targetsFCoE and FC combinations 63, 64


Vvirtual LANs

reasons for using 11VLANs

dynamic 11reasons for using 11static 11

VSANfor heterogeneous SAN 13

WWindows

host configuration limits 84

WWN zoningFC switch 74

Z

zoningFC switch 73FC switch by port 73FC switch by WWN 74FC switch multifabric 76FC switch single-fabric 75FC switch with individual zones 74FCoE switch 73

Index | 109

fibre channel and iscsi configuration guide for

Documents

supported configurations

multifabric ha configurations

contentsiscsi configurations

singlefabric ha pair

singlenetwork ha pair

multifabric ha pair

multinetwork ha pair

iscsi configuration