Fc Iscsi Config Guide 73

Fibre Channel and iSCSI Configuration Guidefor the Data ONTAP 7.3 Release Family

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

Part number 215-06167_A0July 2011

ContentsiSCSI topologies ............................................................................................ 7

Single-network active/active configuration in an iSCSI SAN .................................... 7Multinetwork active/active configuration in an iSCSI SAN ....................................... 9Direct-attached single-controller configurations in an iSCSI SAN .......................... 10VLANs ...................................................................................................................... 11

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

Fibre Channel topologies ........................................................................... 13FC onboard and expansion port combinations .......................................................... 13Fibre Channel supported hop count .......................................................................... 14Fibre Channel supported speeds ................................................................................ 15Fibre Channel switch configuration best practices ................................................... 16The cfmode setting .................................................................................................... 16Host multipathing software requirements ................................................................. 1760xx supported topologies ........................................................................................ 17

60xx target port configuration recommendations ......................................... 1760xx: Single-fabric single-controller configuration ...................................... 1860xx: Single-fabric active/active configuration ............................................ 1960xx: Multifabric active/active configuration ............................................... 2160xx: Direct-attached single-controller configuration .................................. 2260xx: Direct-attached active/active configuration ........................................ 23

32xx supported topologies ........................................................................................ 2432xx target port configuration recommendations ......................................... 2532xx: Single-fabric single-controller configuration ...................................... 2532xx: Single-fabric active/active configurations ........................................... 2632xx: Multifabric active/active configurations ............................................. 2732xx: Direct-attached single-controller configurations ................................. 2832xx: Direct-attached active/active configurations ....................................... 29

31xx supported topologies ........................................................................................ 3031xx target port configuration recommendations ......................................... 3131xx: Single-fabric single-controller configuration ...................................... 3131xx: Single-fabric active/active configuration ............................................ 32

Table of Contents | 3

31xx: Multifabric active/active configuration ............................................... 3431xx: Direct-attached single-controller configurations ................................. 3531xx: Direct-attached active/active configuration ........................................ 36

30xx supported topologies ........................................................................................ 3730xx target port configuration recommendations ......................................... 383040 and 3070 supported topologies ............................................................. 383020 and 3050 supported topologies ............................................................. 44

FAS20xx supported topologies ................................................................................. 50FAS20xx: Single-fabric single-controller configuration ............................... 50FAS20xx: Single-fabric active/active configuration ..................................... 51FAS20xx: Multifabric single-controller configuration ................................. 52FAS20xx: Multifabric active/active configuration ....................................... 53FAS20xx: Direct-attached single-controller configurations ......................... 54FAS20xx: Direct-attached active/active configuration ................................. 55

FAS270/GF270c supported topologies ..................................................................... 56FAS270/GF270c: Single-fabric active/active configuration ......................... 56FAS270/GF270c: Multifabric active/active configuration ........................... 57FAS270/GF270c: Direct-attached configurations ......................................... 58

Other Fibre Channel topologies ................................................................................ 59R200 and 900 series supported topologies .................................................... 59

Fibre Channel over Ethernet overview .................................................... 65FCoE initiator and target combinations .................................................................... 65Fibre Channel over Ethernet supported hop count .................................................... 66Fibre Channel over Ethernet supported topologies ................................................... 66

FCoE: FCoE initiator to FC target configuration .......................................... 67FCoE: FCoE end-to-end configuration ......................................................... 69FCoE: FCoE mixed with FC ......................................................................... 70FCoE: FCoE mixed with IP storage protocols .............................................. 71

Fibre Channel and FCoE zoning .............................................................. 73Port zoning ................................................................................................................ 73World Wide Name based zoning .............................................................................. 74Individual zones ........................................................................................................ 74Single-fabric zoning .................................................................................................. 75Dual-fabric active/active configuration zoning ......................................................... 76

Shared SAN configurations ....................................................................... 79ALUA configurations ................................................................................. 81

4 | Fibre Channel and iSCSI Configuration Guide for the Data ONTAP 7.3 Release Family

(FC) Specific AIX Host Utilities environments that support ALUA ........................ 81ESX configurations that support ALUA ................................................................... 82HP-UX configurations that support ALUA .............................................................. 83Linux configurations that support ALUA ................................................................. 84(FC) Solaris Host Utilities configurations that support ALUA ................................. 84Windows configurations that support ALUA ........................................................... 85

Configuration limits ................................................................................... 87Configuration limit parameters and definitions ........................................................ 87Host operating system configuration limits for iSCSI and FC .................................. 8832xx single-controller limits ..................................................................................... 8932xx active/active configuration limits ..................................................................... 9060xx and 31xx single-controller limits ...................................................................... 9260xx and 31xx active/active configuration limits ..................................................... 9330xx single-controller limits ..................................................................................... 9430xx active/active configuration limits ..................................................................... 95FAS20xx single-controller limits .............................................................................. 97FAS20xxactive/active configuration limits ............................................................... 98FAS270/GF270 , 900 series, and R200 single-controller limits ............................... 99FAS270c/GF270c and 900 series active/active configuration limits ...................... 101

Copyright information ............................................................................. 103Trademark information ........................................................................... 105How to send your comments .................................................................... 107Index ........................................................................................................... 109

Table of Contents | 5

iSCSI topologiesSupported iSCSI configurations include direct-attached and network-attached topologies. Bothsingle-controller and active/active configurations 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 iSCSItopologies. For specific recommendations and best practices, see the Ethernet switch vendor'sdocumentation.

For Windows iSCSI multipathing options, please see Technical Report 3441.

Related information

NetApp Interoperability Matrix - now.netapp.com/NOW/products/interoperability/Technical Report 3441: iSCSI multipathing possibilities on Windows with Data ONTAP -media.netapp.com/documents/tr-3441.pdf

Single-network active/active configuration in an iSCSI SANYou can connect hosts using iSCSI to active/active configuration controllers using a single IPnetwork. The network can consist of one or more switches, and the controllers can be attached tomultiple switches. Each controller can have multiple iSCSI connections to the network. The numberof ports is based on the storage controller model and the number of supported Ethernet ports.

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

7

Figure 1: iSCSI single network active/active configuration

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 Active/active configuration


Multinetwork active/active configuration in an iSCSI SANYou can connect hosts using iSCSI to active/active configuration controllers using multiple IPnetworks. To be fully redundant, a minimum of two connections to separate networks per controlleris necessary to protect against NIC, network, or cabling failure.

Figure 2: iSCSI multinetwork active/active configuration

Attribute Value

Fully redundant Yes

Type of network Multinetwork




iSCSI topologies | 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 active/active configurations.

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


VLANsA VLAN consists of a group of switch ports, optionally across multiple switch chassis, groupedtogether into a broadcast domain. Static and dynamic VLANs enable you to increase security, isolateproblems, and limit available paths within your IP network infrastructure.

Reasons for implementing VLANsImplementing 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 to a manageable number. You need

to verify that only one path to a LUN is visible if a host does not have a multipathing solutionavailable.

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, static VLANs are also easier to create and manage because only the switchand port identifier need to be specified, instead of the 48-bit MAC address. In addition, you can labelswitch 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 topologies | 11

Fibre Channel topologiesSupported FC configurations include single-fabric, multifabric, and direct-attached topologies. Bothsingle-controller and active/active configurations are supported.

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

Active/active configurations with multiple, physically independent storage fabrics (minimum of two)are recommended for SAN solutions. This provides redundancy at the fabric and storage systemlayers, which is particularly 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 active/active configurations 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 FC port combinations and specifies which combinations are supported.

Onboard ports Expansion ports Supported?

Initiator + Target None Yes

Initiator + Target Target only Yes with Data ONTAP 7.3.2and later

Initiator + Target Initiator only Yes

13

Onboard ports Expansion ports Supported?

Initiator + Target Initiator + Target Yes with Data ONTAP 7.3.2and later

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 with Data ONTAP 7.3.2and later

Target only Target only Yes with Data ONTAP 7.3.2and later, but no FC disk shelfor V-Series configurations ortape support

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

Related concepts

Configuration limits on page 87

Related references

FCoE initiator and target combinations on page 65

Fibre Channel supported hop countThe maximum supported FC hop count between a particular host and storage system depends on thehop count that the switch supplier and storage system support for FC configurations.

The hop count is the number of switches in the path between the initiator (host) and target (storagesystem). Cisco also refers to this value as the diameter of the SAN fabric.The following table shows the supported hop count for each switch supplier.

Switch supplier Supported hop count

Brocade 6



Cisco 7Up to 3 of the switches can be FCoE switches.

McData 3

QLogic 4

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 and not use autonegotiation. A port set to autonegotiation can take longer to reconnect after atakeover/giveback or other interruption.

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

4-Gb target portsYou can configure both 4-Gb onboard ports and 4-Gb expansion adapters to run at the followingspeeds. Each controller and expansion adapter port can be individually configured with a differentspeed from the other ports as needed.

4 Gb 2 Gb 1 Gb

8-Gb target portsYou can configure both 8-Gb onboard ports and 8-Gb expansion adapters to run at the followingspeeds. Each controller and expansion adapter port can be individually configured with a differentspeed from the other ports as needed.

8 Gb 4 Gb 2 Gb

Fibre Channel topologies | 15

Fibre Channel switch configuration best practicesA fixed link speed setting is highly recommended, especially for large fabrics, because it provides thebest performance 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 is recommended to set the switch port topology to F (point-to-point).

The cfmode settingThe cfmode setting controls how the FC adapters of a storage system in an active/activeconfiguration log in to the fabric, handle local and partner traffic in normal operation and duringtakeover, and provide access to local and partner LUNs. The cfmode setting of your storage systemand the number of paths available to the storage system must align with cabling, configuration limits,and zoning requirements.

Both controllers in an active/active configuration must have the same cfmode setting.

A cfmode setting is not available on single-controller configurations. You can change the cfmodesetting from the storage system console by setting privileges to advanced and then using the fcpset command.

The Data ONTAP 7.3 release family only supports single_image cfmode, unless you are upgradingfrom an earlier release. The mixed cfmode is not supported even when upgrading; you must changefrom mixed to single_image.

Detailed descriptions of port behavior with each cfmode are available in the Data ONTAP BlockAccess Management Guide for iSCSI and FC.For details about migrating to single_image cfmode and reconfiguring hosts, see Changing theCluster cfmode Setting in Fibre Channel SAN Configurations.

Related information

Data ONTAP Blocks Access Management Guide for iSCSI and FC - now.netapp.com/NOW/knowledge/docs/ontap/ontap_index.shtmlChanging the Cluster cfmode Setting in Fibre Channel SAN Configurations -now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/


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 active/active configuration in single_image cfmode, host multipathing software is requiredunless you use zoning to limit the host to a single path.

60xx supported topologies60xx controllers are available in single-controller and active/active configurations.

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. If you use 4-Gb or 8-Gb target expansion adapters, then you can only configurethe onboard ports as initiators. You cannot use both 2-Gb and 4-Gb or 8-Gb targets on the samecontroller or on two different controllers in an active/active configuration.

The 6030 and 6070 systems are supported by single_image cfmode.

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 target expansion adapters with DataONTAP 7.3 and later.

The 6040 and 6080 systems are only supported by single_image cfmode.

Note: The 60xx systems support the use of 8-Gb target expansion adapters beginning with DataONTAP version 7.3.1.

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

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.

Number of target ports Ports

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-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.

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.


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

Attribute Value

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

Type of fabric Single fabric


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

Related references60xx target port configuration recommendations on page 17

60xx: Single-fabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using 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.

Figure 5: 60xx single-fabric active/active configuration

Attribute Value

Fully redundant No, due to the single fabric




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


Related references

60xx target port configuration recommendations on page 17


60xx: Multifabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using two or more FCswitch fabrics for redundancy.



Figure 6: 60xx multifabric active/active configuration

Attribute Value

Fully redundant Yes

Type of fabric Multifabric



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.

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.

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


Attribute Value


Type of fabric None





Related references


60xx: Direct-attached active/active configurationYou can connect hosts directly to FC target ports on both controllers in an active/activeconfiguration. The number of hosts is limited by the number of available target ports.





Figure 8: 60xx direct-attached active/active configuration

Attribute Value

Fully redundant Yes

Type of fabric None





Related references


32xx supported topologies32xx systems are available in single-controller and active/active 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.


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


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-fabric single-controller configurationYou can connect hosts to a single controller using a single FC switch.



Host 1 Host 2 Host N

Controller 1

Single Switch/Fabric 1

0c 0d



Attribute Value







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




Controller 1

Controller 2

Single Switch/Fabric 1

0c 0d0c 0d



Attribute Value






Type of configuration active/active configuration

32xx: Multifabric active/active configurationsYou can connect hosts to both controllers in an active/active configuration using two or more FCswitch fabrics for redundancy.





Controller 1

Controller 2

Switch/Fabric 1 Switch/Fabric 2

0c 1a 0d 1b

0d 1b0c 1a


Attribute Value

Fully redundant Yes





Type of configuration active/active configuration

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 12: 32xx direct-attached single-controller configurations

Attribute Value


Type of fabric None





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





Host

Controller 1

Controller 2

0c0c


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



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.

Each 31xx controller supports 4-Gb FC target expansion adapters.

The 31xx systems are only supported by single_image cfmode.


Note: 31xx controllers support the use of 8-Gb target expansion adapters beginning with DataONTAP 7.3.1.


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-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.





Attribute Value







Related references


31xx: Single-fabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using a single FC switch.






Attribute Value







Related references



31xx: Multifabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using two or more FCswitch fabrics for redundancy.




Attribute Value

Fully redundant Yes




Attribute Value




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 17: 31xx direct-attached single-controller configurations


Attribute Value


Type of fabric None





Related references


31xx: Direct-attached active/active configurationYou can connect hosts directly to FC target ports on both controllers in an active/activeconfiguration. The number of hosts is limited by the number of available target ports.






Attribute Value

Fully redundant Yes

Type of fabric None




Related references



Note: 3040 and 3070 controllers support the use of 8-Gb target expansion adapters beginning withData ONTAP 7.3.1. 3020 and 3050 controllers do not support the use of 8-Gb target expansionadapters.

3020 and 3050 controllers support 2-Gb or 4-Gb FC target connections, but you cannot use both onthe same controller or on two different controllers in an active/active configuration. If you use targetexpansion adapters, then you can only use onboard adapters as initiators.

Only single_image cfmode is supported with new installations of the Data ONTAP 7.3 release familysoftware. For 3020 and 3050 controllers running partner or standby cfmode with earlier versions of


Data ONTAP, those cfmodes continue to be supported when upgrading the controllers to DataONTAP 7.3. However, converting to single_image cfmode is recommended.


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 topologies3040 and 3070 systems are available in single-controller and active/active configurations.

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-fabric single-controller configurationYou can connect hosts to single controllers using a single FC switch. If you use multiple paths,multipathing software is required on the host.




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

Attribute Value







Related references


3040 and 3070: Single-fabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using a single FC switch.





Figure 20: 3040 and 3070 single-fabric active/active configuration

Attribute Value







Related references



3040 and 3070: Multifabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using two or more FCswitch fabrics for redundancy.



Figure 21: 3040 and 3070 multifabric active/active configuration

Attribute Value

Fully redundant Yes




Attribute Value




Related references


3040 and 3070: 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 22: 3040 and 3070 direct-attached single-controller configurations

Attribute Value


Type of fabric None


Attribute Value





Related references


3040 and 3070: Direct-attached active/active configurationYou can connect hosts directly to FC target ports on both controllers in an active/activeconfiguration. The number of hosts is limited by the number of available target ports.




Figure 23: 3040 and 3070 direct-attached active/active configuration


Attribute Value

Fully redundant Yes

Type of fabric None




Related references


3020 and 3050 supported topologies3020 and 3050 systems are available in single-controller and active/active configurations.

The 3020 and 3050 controllers have four onboard 2-Gb FC ports per controller and each port can beconfigured as either an FC target port or an initiator port.

2-Gb FC target ports are supported with the onboard 2-Gb FC ports on the 3020 and 3050controllers. 4-Gb FC target connections are supported with 4-Gb FC target HBAs.

Each 3020 and 3050 controller supports 2-Gb or 4-Gb FC target HBAs, but you cannot use both onthe same controller or on two different controllers in an active/active configuration. If you use targetexpansion HBAs, then you can only use onboard ports as initiators.

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



Figure 24: 3020 and 3050 single-fabric single-controller configuration

Attribute Value






Related references


3020 and 3050: Single-fabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using a single FC switch.



Figure 25: 3020 and 3050 single-fabric active/active configuration

Attribute Value







Related references


3020 and 3050: Multifabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using two or more FCswitch fabrics for redundancy.




Figure 26: 3020 and 3050 multifabric active/active configuration

Attribute Value

Fully redundant Yes






Related references



3020 and 3050: 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 27: 3020 and 3050 direct-attached single-controller configurations

Attribute Value


Type of fabric None





Related references



3020 and 3050: Direct-attached active/active configurationYou can connect hosts directly to FC target ports on both controllers in an active/activeconfiguration. The number of hosts is limited by the number of available target ports.



Figure 28: 3020 and 3050 direct-attached active/active configuration

Attribute Value

Fully redundant Yes, if configured with multipathing software

Type of fabric None




Related references



FAS20xx supported topologiesFAS20xx systems are available in single-controller and active/active configurations and aresupported by single_image cfmode only.

The FAS20xx 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.

FAS20xx: 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. The actual portnumbers might vary depending on whether you are using onboard ports or an FC target expansionadapter. The FC target expansion adapter is supported only for the FAS2050 controller.

Figure 29: FAS20xx single-fabric single-controller configuration

Attribute Value





Attribute Value


For FAS2050 only, one supported 4-Gb or 8-Gb FC targetexpansion adapter


FAS20xx: Single-fabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using a single FC switch.



Figure 30: FAS20xx single-fabric active/active configuration

Attribute Value




Attribute Value





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



Figure 31: FAS20xx multifabric single-controller configuration

Attribute Value




Attribute Value





FAS20xx: Multifabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using two or more FCswitch fabrics for redundancy.



Figure 32: FAS20xx multifabric active/active configuration


Attribute Value

Fully redundant Yes






FAS20xx: 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 33: FAS20xx direct-attached single-controller configurations


Attribute Value


Type of fabric None





FAS20xx: Direct-attached active/active configurationYou can connect hosts directly to FC target ports on both controllers in an active/activeconfiguration. The number of hosts is limited by the number of available target ports.




Figure 34: FAS20xx direct-attached active/active configuration


Attribute Value

Fully redundant Yes

Type of fabric None





FAS270/GF270c supported topologiesFAS270/GF270c systems are available in active/active configurations.

FAS270/GF270c: Single-fabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using a single FC switch.

FC Fabric 1


Controller 1 / Controller 2

Figure 35: FAS270/GF270c single-fabric active/active configuration


Attribute Value

Fully Redundant No, due to the single fabric




FAS270/GF270c: Multifabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using two or more FCswitch fabrics for redundancy.

Host 1

FC Fabric 1 FC Fabric 2


Controller 1 and Controller 2

Figure 36: FAS270/GF270c multifabric active/active configuration

Attribute Value

Fully redundant Yes, if a host is dual-attached

No, if a host is single-attached





FAS270/GF270c: Direct-attached configurationsYou can connect hosts directly to FC target ports on a single controller or an Active/activeconfiguration. The number of hosts is limited by the number of available target ports.


Host 1 Host 1 Host 1 Host 2

Controller 1 Controller 1 / Controller 2 Controller 1 / Controller 2

Figure 37: FAS270/GF270c direct-attached configurations

Attribute Value

Fully Redundant First configuration: No, due to the single controller

Second configuration: Yes

Third configuration: No, due to a single connection from storagesystem to hosts

Type of fabric None

Different host operatingsystems

Yes, with multiple-host configurations

Type of configuration First configuration: Single controller configuration

Second configuration: Active/active configuration

Third configuration: Active/active configuration


Other Fibre Channel topologiesOther FC systems, such as the 900 series and R200, are no longer sold, but are still supported.

R200 and 900 series supported topologiesR200 and 900 series systems are available in single controller and active/active configurations.

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

FC Fabric 1

Controller 1


Figure 38: R200 and 900 series single-fabric single-controller configuration

Attribute Value





Attribute Value

FC ports or adapters One to four connections to the fabric, depending on the numberof target expansion adapters installed in each controller

Type of configuration Single controller configuration

900 series: Single-fabric active/active configurationYou can connect hosts to both controllers in an active/active configuration using a single FC switch.

The following diagram shows the minimum FC cabling configuration for connecting an active/activeconfiguration to a single fabric.

Figure 39: 900 series single-fabric active/active configuration

Attribute Value




FC ports or adapters Two to 16 connections to the fabric, depending on the number oftarget expansion adapters connected to the system



900 series: Multifabric active/active configuration, one dual-ported FC target expansionadapter

You can connect hosts to both controllers in an active/active configuration using two or more FCswitch fabrics and a single FC target expansion adapter in each controller.

Figure 40: 900 series multifabric active/active configuration

Attribute Value

Fully redundant Yes, when the host has multipathing software properlyconfigured



FC ports or adapters One dual-ported FC target expansion adapter per controller



900 series: Multifabric active/active configuration, two dual-ported FC target expansionadapters

You can connect hosts to both controllers in an active/active configuration using two or more FCswitch fabrics and two FC target expansion adapters in each controller.

Note: The port numbers used in the following figure (7a, 7b, 9a, and 9b) are examples. The actualport numbers might vary, depending on the expansion slot in which the FC target expansionadapters are installed.


Attribute Value

Fully redundant Yes, when the host is dually attached to two physically separatefabrics



FC ports or adapters Two dual-ported FC target expansion adapters per controller



900 series: Multifabric active/active configuration, four dual-ported FC target expansionadapters

You can connect hosts to both controllers in an active/active configuration using two or more FCswitch fabrics and four FC target expansion adapters in each controller.

This configuration is used in combination with larger, more complex fabrics where the eightconnections between the controller and the fabric are not attached to a single FC switch.


Attribute Value

Fully redundant Yes



FC ports or adapters Four dual-ported FC target expansion adapters per controller



R200 and 900 series: Direct-attached 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 1Host 1

Host 2

Host 3

Host N

Host 2

Controller 1 Controller 1 Controller 1

Host 1

Figure 43: 900 series, or R200 direct-attached single-controller configurations

Attribute Value


Type of fabric None


Type of configuration Single controller configuration


Fibre Channel over Ethernet overviewFibre Channel over Ethernet (FCoE) is a new model for connecting hosts to storage systems. FCoE isvery similar to traditional Fibre Channel (FC), as it maintains existing FC management and controls,but the hardware transport 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 for the host, such as iSCSI, CIFS, NFS, and HTTP. Both theFCoE and standard Ethernet portions of the CNA communicate over the same Ethernet port, whichconnects to the FCoE switch.

Note: Unified target adapters (UTAs) are 10-Gb converged network adapters that you install onyour storage systems. Using UTAs for non-FCoE IP traffic such as NFS, CIFS, or iSCSI is NOTsupported for Data ONTAP 7.3.

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 yourappropriate host documentation.

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

FCoE initiatorsYou 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

FC FCoE Yes with Data ONTAP 7.3.2and later

FCoE FC Yes

65

Initiator Target Supported?

FCoE FCoE Yes with Data ONTAP 7.3.2and later

FCoE targetsYou 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

FC onboard and expansion port combinations on page 13

Fibre Channel over Ethernet supported hop countThe maximum supported FCoE hop count between a particular host and storage system depends onthe hop count that the switch supplier and storage system support for FCoE configurations.

The hop count is the number of switches in the path between the initiator (host) and target (storagesystem). 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 thatsupport Ethernet inter-switch links (ISLs).The following table shows the maximum supported hop count for each switch supplier.


Cisco 7Up to 3 of the switches can be FCoE switches.

Fibre Channel over Ethernet supported topologiesSupported FCoE native configurations include single-fabric and multifabric topologies. Both single-controller and active/active configurations are supported.

Supported storage systems with native FCoE target expansion adapters are the 60xx, 32xx, 31xx,3040, and the 3070.

In active/active configurations, only single_image cfmode is supported.


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 active/active configuration using FCoE initiatorsthrough FCoE switches 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 | 67

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 44: FCoE initiator to FC dual-fabric active/active configuration

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 active/active configuration using FCoE initiatorsthrough DCB switches to FCoE 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) 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

CNA Ports

CNA Ports

CNA Ports CNA Ports

Controller 1

Controller 2

2b2a

2b2a

Host 2 Host N

FCoE Switch

IP NetworkIP Network

FCoE Switch

DCBPorts

DCBPorts

DCBPorts

DCBPorts

Figure 45: FCoE end-to-end

Fc Iscsi Config Guide 73

Documents

Transcript of Fc Iscsi Config Guide 73