Netappfc Iscsi Config Guide 80

Fibre Channel and iSCSI Configuration Guidefor the Data ONTAP 8.0 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-05658_A0November 2010

Contents

Copyright information ................................................................................. 7Trademark information ............................................................................... 9About this guide .......................................................................................... 11

Audience .................................................................................................................... 11

Keyboard and formatting conventions ...................................................................... 11

Special messages ....................................................................................................... 12

How to send your comments ..................................................................................... 13

iSCSI topologies .......................................................................................... 15Single-network HA pair in an iSCSI SAN ................................................................ 15

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

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

VLANs ...................................................................................................................... 19

Static VLANs ................................................................................................ 19

Dynamic VLANs ........................................................................................... 19

Fibre Channel topologies ........................................................................... 21FC onboard and expansion port combinations .......................................................... 22

Fibre Channel supported hop count .......................................................................... 23

Fibre Channel switch configuration best practices ................................................... 23

Host multipathing software requirements ................................................................. 23

62xx supported topologies ........................................................................................ 24

62xx target port configuration recommendations ......................................... 24

62xx: Single-fabric single-controller configuration ...................................... 24

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

62xx: Multifabric HA configurations ............................................................ 26

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

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




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

60xx: Multifabric HA pair ............................................................................. 34

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

Table of Contents | 3

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




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

32xx: Multifabric HA configurations ............................................................ 40

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

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




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

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

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

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



3040 and 3070 supported topologies ............................................................. 50

FAS2040 supported topologies ................................................................................. 56

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

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

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

FAS2040: Multifabric HA pair ..................................................................... 59

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

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

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

Fibre Channel over Ethernet supported topologies ................................................... 64

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

FCoE: FCoE end-to-end configuration ......................................................... 66

FCoE: FCoE mixed with FC ......................................................................... 67

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

Fibre Channel and FCoE zoning .............................................................. 71Port zoning ................................................................................................................ 72

World Wide Name based zoning .............................................................................. 72

Individual zones ........................................................................................................ 72

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

Single-fabric zoning .................................................................................................. 73

Dual-fabric HA pair zoning ....................................................................................... 74

Shared SAN configurations ....................................................................... 77ALUA configurations ................................................................................. 79

(FC) Specific AIX Host Utilities configurations that support ALUA ...................... 79

ESX configurations that support ALUA ................................................................... 81

HP-UX configurations that support ALUA .............................................................. 81

Linux configurations that support ALUA ................................................................. 82

(FC) Solaris Host Utilities configurations that support ALUA ................................. 82

Windows configurations that support ALUA ........................................................... 83

Configuration limits ................................................................................... 85Configuration limit parameters and definitions ........................................................ 85

Host operating system configuration limits for iSCSI and FC .................................. 87

62xx single-controller limits ..................................................................................... 88

62xx HA configuration limits ................................................................................... 89


32xx 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

Index ............................................................................................................. 99

Table of Contents | 5

Copyright information

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

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.A. patents, foreignpatents, 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).

Copyright information | 7

Trademark information

NetApp; the NetApp logo; the Network Appliance logo; Bycast; Cryptainer; Cryptoshred;DataFabric; Data ONTAP; Decru; Decru DataFort; FAServer; FilerView; FlexCache; FlexClone;FlexShare; FlexVol; FPolicy; gFiler; Go further, faster; Manage ONTAP; MultiStore; NearStore;NetCache; NOW (NetApp on the Web); ONTAPI; RAID-DP; SANscreen; SecureShare; SimulateONTAP; SnapCopy; SnapDrive; SnapLock; SnapManager; SnapMirror; SnapMover; SnapRestore;SnapValidator; SnapVault; Spinnaker Networks; Spinnaker Networks logo; SpinAccess;SpinCluster; SpinFlex; SpinFS; SpinHA; SpinMove; SpinServer; SpinStor; StorageGRID;StoreVault; SyncMirror; Topio; vFiler; VFM; and WAFL are registered trademarks of NetApp, Inc.in the U.S.A. and/or other countries. Network Appliance, Snapshot, and The evolution of storage aretrademarks of NetApp, Inc. in the U.S.A. and/or other countries and registered trademarks in someother countries. The StoreVault logo, ApplianceWatch, ApplianceWatch PRO, ASUP, AutoSupport,ComplianceClock, DataFort, Data Motion, FlexScale, FlexSuite, Lifetime Key Management,LockVault, NOW, MetroCluster, OpenKey, ReplicatorX, SecureAdmin, Shadow Tape,SnapDirector, SnapFilter, SnapMigrator, SnapSuite, Tech OnTap, Virtual File Manager, VPolicy,and Web Filer are trademarks of NetApp, Inc. in the U.S.A. and other countries. Get Successful andSelect are service marks of NetApp, Inc. in the U.S.A.

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 U.S.A. and/orother countries. Microsoft is a registered trademark and Windows Media is a trademark of MicrosoftCorporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer,RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, andSureStream are trademarks of RealNetworks, Inc. in the U.S.A. and/or other countries.

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.

Trademark information | 9

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

About this guide

You can use your product more effectively when you understand this document's intended audienceand the conventions that this document uses to present information.

This document describes the configuration of fabric-attached, network-attached, and direct-attachedstorage systems in Fibre Channel (FC), Fibre Channel over Ethernet (FCoE), and iSCSIenvironments. This guide explains the various topologies that are supported and describes therelevant SAN configuration limits for each controller model.

The configurations apply to controllers with their own disks and to V-Series configurations.

Next topics

Audience on page 11

Keyboard and formatting conventions on page 11

Special messages on page 12

How to send your comments on page 13

AudienceThis document is written with certain assumptions about your technical knowledge and experience.

This document is for system administrators who are familiar with host operating systems connectingto storage systems using FC, FCoE, and iSCSI protocols.

This guide assumes that you are familiar with basic FC, FCoE, and iSCSI solutions and terminology.This guide does not cover basic system or network administration topics, such as IP addressing,routing, and network topology; it emphasizes the characteristics of the storage system.

Keyboard and formatting conventionsYou can use your product more effectively when you understand how this document uses keyboardand formatting conventions to present information.

Keyboard conventions

Convention What it means

The NOW site Refers to the NetApp Support site at now.netapp.com.

About this guide | 11

http://now.netapp.com/


Enter, enter • Used to refer to the key that generates a carriage return; the key is namedReturn on some keyboards.

• Used to mean pressing one or more keys on the keyboard and then pressing theEnter key, or clicking in a field in a graphical interface and then typinginformation into the field.

hyphen (-) Used to separate individual keys. For example, Ctrl-D means holding down theCtrl key while pressing the D key.

type Used to mean pressing one or more keys on the keyboard.

Formatting conventions


Italic font • Words or characters that require special attention.• Placeholders for information that you must supply.

For example, if the guide says to enter the arp -d hostname command,you enter the characters "arp -d" followed by the actual name of the host.

• Book titles in cross-references.

Monospaced font • Command names, option names, keywords, and daemon names.• Information displayed on the system console or other computer monitors.• Contents of files.• File, path, and directory names.

Bold monospaced

fontWords or characters you type. What you type is always shown in lowercaseletters, unless your program is case-sensitive and uppercase letters arenecessary for it to work properly.

Special messagesThis document might contain the following types of messages to alert you to conditions that youneed to be aware of.

Note: A note contains important information that helps you install or operate the systemefficiently.

Attention: An attention notice contains instructions that you must follow to avoid a system crash,loss of data, or damage to the equipment.


How to send your commentsYou 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 e-mail to [email protected]. To help us direct your comments to the correct division, include in thesubject line the name of your product and the applicable operating system. For example, FAS6070—Data ONTAP 7.3, or Host Utilities—Solaris, or Operations Manager 3.8—Windows.

About this guide | 13

mailto:[email protected]

iSCSI topologies

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

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

Next topics

Single-network HA pair in an iSCSI SAN on page 15

Multinetwork HA pair in an iSCSI SAN on page 17

Direct-attached single-controller configurations in an iSCSI SAN on page 18

VLANs on page 19

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 HA pair in an iSCSI SANYou can connect hosts using iSCSI to HA pair controllers using a single IP network. The networkcan consist of one or more switches, and the controllers can be attached to multiple switches. Eachcontroller can have multiple iSCSI connections to the network. The number of ports is based on thestorage 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.

iSCSI topologies | 15

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 using iSCSI to HA pair controllers using multiple IP networks. To be fullyredundant, a minimum of two connections to separate networks per controller is necessary to protectagainst NIC, network, or cabling failure.

Figure 2: iSCSI multinetwork HA pair

Attribute Value

Fully redundant Yes

Type of network Multinetwork





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


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

Next topics

Static VLANs on page 19

Dynamic VLANs on page 19

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.


Fibre Channel topologies

Supported FC configurations include single-fabric, multifabric, and direct-attached topologies. Bothsingle-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 NOW 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.

Next topics

FC onboard and expansion port combinations on page 22

Fibre Channel supported hop count on page 23

Fibre Channel switch configuration best practices on page 23

Host multipathing software requirements on page 23

62xx supported topologies on page 24





FAS2040 supported topologies on page 56

Related information

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

Fibre Channel topologies | 21


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

Initiator + Target Initiator only Yes

Initiator + Target Initiator + Target Yes with Data ONTAP 7.3.2 andlater

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

Target only Target only Yes with Data ONTAP 7.3.2 andlater, but no FC disk shelf or V-Series configurations or tapesupport

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

Related concepts

Configuration limits on page 85

Related references

FCoE initiator and target combinations on page 63


Fibre Channel supported hop countThe maximum supported FC hop count, or the number of inter-switch links (ISLs) crossed between aparticular host and storage system, depends on the hop count that the switch supplier and storagesystem support for FC configurations.

The following table shows the supported hop count for each switch supplier.

Switch supplier Supported hop count

Brocade 6

Cisco 5

McData 3

QLogic 4

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

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

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

Next topics

62xx target port configuration recommendations on page 24

62xx: Single-fabric single-controller configuration on page 24

62xx: Single-fabric HA configurations on page 25

62xx: Multifabric HA configurations on page 26

62xx: Direct-attached single-controller configuration on page 28

62xx: Direct-attached HA configurations on page 29

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 given in the System Configuration Guide for theversion of Data ONTAP software being used by the controllers.

Number of target ports Ports

1 0a

2 0a, 0c

3 0a, 0c, 0b

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

62xx: 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.

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

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

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




Controller 1

Controller 2


0a 0c0a 0c

Figure 5: 62xx single-fabric HA 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

Type of configuration HA configuration

62xx: 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

Switch/Fabric 1 Switch/Fabric 2

0a 0c 0b 0d

0b 0d0a 0c

Figure 6: 62xx multifabric HA configurations

Attribute Value

Fully redundant Yes

Type of fabric Multifabric






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.

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.

Host 1

Host 2 Host 3

Host 2 Host NHost N

Figure 7: 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 8: 62xx direct-attached HA configuration

Attribute Value

Fully redundant Yes

Type of fabric None






60xx supported topologies60xx 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 target connections are supported with 4-Gb target expansion adapters. Ifyou use 4-Gb target expansion adapters, then you can only configure the onboard ports as initiators.You cannot use both 2-Gb and 4-Gb targets on the same controller or on two different controllers inan 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 target expansion adapters with DataONTAP 7.3 and later.

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

Next topics


60xx : Single-fabric single-controller configuration on page 31

60xx : Single-fabric HA pair on page 32

60xx : Multifabric HA pair on page 34

60xx : Direct-attached single-controller configuration on page 35

60xx : Direct-attached HA pair on page 36


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



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




Attribute Value




Attribute Value





Related references


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



Figure 10: 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 11: 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 12: 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 13: 60xx direct-attached HA pair

Attribute Value

Fully redundant Yes

Type of fabric None





Related references


32xx supported topologies32xx 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.


Each 32xx controller supports 4-Gb and 8-Gb FC target expansion adapters. Note that the 8-Gbexpansion adapters cannot be combined with 4-Gb targets (whether using expansion adapters oronboard).

Next topics


32xx: Single-fabric single-controller configuration on page 38

32xx: Single-fabric HA configurations on page 39

32xx: Multifabric HA configurations on page 40

32xx: Direct-attached single-controller configurations on page 41

32xx: Direct-attached HA configurations on page 42


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





Controller 1


0c 0d


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 15: 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

Switch/Fabric 1 Switch/Fabric 2

0c 1a 0d 1b

0d 1b0c 1a

Figure 16: 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 17: 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.


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.

Host

Controller 1

Controller 2

0c0c

Figure 18: 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


31xx supported topologies31xx 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.

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

Note: 31xx controllers support the use of 8-Gb target expansion adapters beginning with DataONTAP 7.3.1. However, the 8-Gb expansion adapters cannot be combined with 4-Gb targets(whether using expansion adapters or onboard).

Next topics


31xx : Single-fabric single-controller configuration on page 44


31xx : Single-fabric HA pair on page 45

31xx : Multifabric HA pair on page 46

31xx : Direct-attached single-controller configurations on page 48

31xx : Direct-attached HA pair on page 49


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





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

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 21: 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 22: 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 23: 31xx direct-attached HA pair

Attribute Value

Fully redundant Yes

Type of fabric None




Related references



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

Note: 3040 and 3070 controllers support the use of 8-Gb target expansion adapters beginning withData ONTAP 7.3.1. While 8-Gb and 4-Gb target expansion adapters function similarly, pleasenote that the 8-Gb target expansion adapters cannot be combined with 4-Gb targets (expansionadapters or onboard).

Next topics


3040 and 3070 supported topologies on page 50


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

Next topics

3040 and 3070 : Single-fabric single-controller configuration on page 51

3040 and 3070 : Single-fabric HA pair on page 52

3040 and 3070 : Multifabric HA pair on page 53


3040 and 3070 : Direct-attached single-controller configurations on page 54

3040 and 3070 : Direct-attached HA pair on page 55

3040 and 3070: Single-fabric single-controller configuration

You 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: 3040 and 3070 single-fabric single-controller configuration

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 25: 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 26: 3040 and 3070 multifabric HA pair

Attribute Value

Fully redundant Yes






Attribute Value


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

Attribute Value


Type of fabric None





Attribute Value


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 28: 3040 and 3070 direct-attached HA pair

Attribute Value

Fully redundant Yes

Type of fabric None




Attribute Value


Related references


FAS2040 supported topologiesFAS2040 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.

Next topics

FAS2040 : Single-fabric single-controller configuration on page 56

FAS2040 : Single-fabric HA pair on page 57

FAS2040 : Multifabric single-controller configuration on page 58

FAS2040 : Multifabric HA pair on page 59

FAS2040 : Direct-attached single-controller configurations on page 60

FAS2040 : Direct-attached HA pair on page 61

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

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


Figure 29: FAS2040 single-fabric single-controller configuration

Attribute Value






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



Figure 30: 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 31: 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 32: 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.




Figure 33: 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 34: 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 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 data center bridging (DCB) Ethernet switch. The CNA is aconsolidation point and effectively serves as both an HBA and an Ethernet adapter.

The CNA is presented to the host as both a FC HBA and a 10 Gb Ethernet adapter. The FC HBAportion of the CNA operates on all of the FC traffic when the FC traffic is sent and received as FCframes mapped into Ethernet packets (FC over Ethernet). The Ethernet adapter portion of the CNAoperates on the host IP traffic, such as iSCSI, CIFS, NFS, and HTTP. Both the FCoE and IP portionsof the CNA communicate over the same Ethernet port, which connects to the DCB switch.

Note: Unified target adapters (UTAs) are 10 Gb Ethernet adapters that you install on your storagesystems. Starting with Data ONTAP 8.0.1, you can use UTAs for non-FCoE IP traffic such asNFS, CIFS, or iSCSI. This is not supported for Data ONTAP 8.0 and earlier.

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.

Next topics

FCoE initiator and target combinations on page 63

Fibre Channel over Ethernet supported topologies on page 64

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

Fibre Channel over Ethernet overview | 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

FC onboard and expansion port combinations on page 22

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

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

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.

Next topics

FCoE: FCoE initiator to FC target configuration on page 65

FCoE: FCoE end-to-end configuration on page 66

FCoE: FCoE mixed with FC on page 67

FCoE: FCoE mixed with IP storage protocols on page 69


FCoE: FCoE initiator to FC target configurationYou can connect hosts to both controllers in an HA pair using FCoE initiators through data centerbridging (DCB) Ethernet switches to FC target ports.

The FCoE initiator always connects to a supported DCB switch. The DCB 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.

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 35: FCoE initiator to FC dual-fabric HA pair

Attribute Value

Fully redundant Yes

Type of fabric Dual fabric


Attribute Value



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 using FCoE initiators through DCB switchesto FCoE target ports.

The FCoE initiator and FCoE target must connect to the same supported DCB switch. You can usemultiple switches for redundant paths, but only one DCB switch in a given path.

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


FCoE Switch

DCBPorts

DCBPorts

DCBPorts

DCBPorts

Figure 36: FCoE end-to-end

Attribute Value

Fully redundant Yes


Different host operating systems Yes, with multiple host-configurations

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 using FCoE initiators through data centerbridging (DCB) Ethernet switches to FCoE and FC mixed target ports.

The FCoE initiator and FCoE target must connect to the same supported DCB switch. The DCBswitch can connect directly to the FC target, or can connect through FC switches to the FC target.You can use multiple DCB switches for redundant paths, but only one DCB switch in a given path.


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

CNA Ports

CNA 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 37: FCoE mixed with FC

Attribute Value

Fully redundant Yes




Attribute Value

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 data centerbridging (DCB) Ethernet switches to FCoE target ports. You can also run non-FCoE IP trafficthrough the same switches.

The FCoE initiator and FCoE target must connect to the same supported DCB switch. You can usemultiple switches for redundant paths, but only one DCB switch in a given path.

Note: The FCoE ports are connected to DCB ports on the DCB switches. Ports used to connectiSCSI are not required to be DCB ports; they can also be regular (non-DCB) Ethernet ports. Theseports can also be used to carry NFS, CIFS, or other IP traffic. The use of FCoE does not add anyadditional restrictions or limitations on the configuration or use of iSCSI, NFS, CIFS, or other IPtraffic.

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.



CNA Ports

CNA 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 38: FCoE mixed with IP storage protocols

Attribute Value

Fully redundant Yes



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




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

Next topics

Port zoning on page 72

World Wide Name based zoning on page 72

Individual zones on page 72

Single-fabric zoning on page 73

Dual-fabric HA pair zoning on page 74

Fibre Channel and FCoE zoning | 71

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.

World Wide Name based zoningWorld Wide Name based zoning (WWN) specifies the WWN of the members to be included withinthe zone. Depending on the switch vendor, either World Wide Node Name or World Wide PortNames can be used. You should use World Wide Port Name zoning when 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 a separatezone, the zones overlap because the storage ports are included in each zone to allow each host toaccess the storage.

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

Using port zoning, you can do this zoning configuration in advance even if all of the hosts are notpresent. You can define each zone to contain a single switch port for the host and switch ports onethrough four for the storage system.

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

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


Figure 39: Hosts in individual zones

Single-fabric zoningZoning and multipathing software used in conjunction prevent 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.


Figure 40: 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 storage system 1 andHost2 accesses LUNs from storage system 2. Each storage system is an HA pair and both are fullyredundant.

Multiple FAS270c storage systems are shown in this figure, but they are not necessary forredundancy.


Figure 41: Dual-fabric zoning


Shared SAN configurations

Shared SAN configurations are defined as hosts that are attached to both NetApp and non-NetAppstorage arrays. Accessing NetApp arrays and other vendors' arrays from a single host is supported aslong as several requirements are met.

The following requirements must be met for support of accessing NetApp arrays and other vendors'arrays from a single host:

• 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 CLARiiON CX3-20, CX3-40, CX3-80 w/ PowerPath 4.5+ and connected to aNetApp storage system using Data ONTAP DSM for Windows MPIO

Solaris EMC CLARiiON CX3-20, CX3-40, CX3-80 / PowerPath 5+ and connected to aNetApp storage system using SUN Traffic Manager (MPxIO)

AIX EMC CLARiiON CX3-20, CX3-40, CX3-80 / PowerPath 5+ and connected to aNetApp storage system using AIX MPIO

Shared SAN configurations | 77

ALUA configurations

ALUA (asymmetric logical unit access) is supported for certain combinations of host operatingsystems and Data ONTAP 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.

ALUA is enabled or disabled on the igroup mapped to a NetApp LUN. The default ALUA setting inData ONTAP is disabled.

For information about using ALUA on a host, see the Host Utilities Installation and Setup Guide foryour host operating system. For information about enabling ALUA on the storage system, see theBlock Access Management Guide for iSCSI and FC for your version of Data ONTAP software.

Next topics

(FC) Specific AIX Host Utilities configurations that support ALUA on page 79

ESX configurations that support ALUA on page 81

HP-UX configurations that support ALUA on page 81

Linux configurations that support ALUA on page 82

(FC) Solaris Host Utilities configurations that support ALUA on page 82

Windows configurations that support ALUA on page 83

(FC) Specific AIX Host Utilities configurations that supportALUA

You can use ALUA if you have an AIX Host Utilities FC environment, either MPIO or Veritas, anda version of Data ONTAP that supports ALUA.

The following AIX configurations support ALUA when you are using the FC protocol:

ALUA configurations | 79

Host Utilities version Host requirements Data ONTAP version

Host Utilities 4.0, 4.1, and 5.0 One of the following or later:

• 5.2 TL8

• 5.3 TL9 SP4 with APARIZ53157




Note: It is stronglyrecommended that, if you wantto use ALUA, you use the latestlevels of 5.3 TL9 or 6.1 TL2listed in the support matrix.ALUA is supported on all AIXService Streams that have thecorresponding APAR(authorized program analysisreport) installed. At the time thisdocument was prepared, theHost Utilities supported AIXService Streams with theAPARs listed above as well aswith APARs IZ53718, IZ53730,IZ53856, IZ54130, IZ57806,and IZ61549. If an APAR listedhere has not been publiclyreleased, contact IBM andrequest a copy.

7.3.1 and later

Note: The Host Utilities do not support ALUA with AIX environments using iSCSI.

You can also use ALUA if you are running Veritas Storage Foundation 5.1 with the FC protocol.Veritas environments also let you use VxVM instead of ALUA to specify the path priorities.

If you have an MPIO environment and do not want to use ALUA, you can use the dotpaths utilityto specify path priorities. The Host Utilities provide dotpaths as part of the SAN Toolkit.


ESX configurations that support ALUAESX hosts support ALUA with certain combinations of ESX, Data ONTAP, and guest operatingsystem configurations.

The following table lists which configurations support ALUA (asymmetric logical unit access). Usethe Interoperability Matrix to determine a supported combination of ESX, Data ONTAP, and HostUtilities software. Then enable or disable ALUA based on the information in the table.

ESX version Minimum Data ONTAP Windows guest in Microsoftcluster

Supported ?

4.0 or later 7.3.1 with single_image cfmode No Yes

4.0 or later 7.3.1 with single_image cfmode Yes No

3.5 and earlier any any No

Using ALUA is strongly recommend, but not required, for configurations that support ALUA. If youdo not use ALUA, be sure to set an optimized path using the tools supplied with ESX Host Utilitiesor Virtual Storage Console.

HP-UX configurations that support ALUAThe HP-UX Host Utilities support asymmetric logical unit access (ALUA). ALUA defines a standardset of SCSI commands for discovering and managing multiple paths to LUNs on FC and iSCSISANs.

You should enable ALUA when your HP-UX configuration supports it. ALUA is enabled on theigroup mapped to NetApp LUNs used by the HP-UX host. Currently, the default setting in DataONTAP software for ALUA is disabled.

You can use the NetApp Interoperability Matrix to determine a supported combination of HP-UX,Data ONTAP, Host Utilities, and Native MPIO software. You can then enable or disable ALUAbased on the information in the following table:

HP-UX version Native MPIO software Minimum Data ONTAP Supported

HP-UX 11iv3 ALUA 7.2.5 or later Yes

HP-UX 11iv2 ALUA None No

Note: ALUA is mandatory and is supported with HP UX 11iv3 September 2007 and later.

Related information

NetApp Interoperability Matrix - http://now.netapp.com/matrix/mtx/login.do



Linux configurations that support ALUAThe Linux Host Utilities support ALUA (asymmetric logical unit access) on hosts running Red HatEnterprise Linux or SUSE Linux Enterprise Server, the FC protocol, and a version of Data ONTAPthat supports ALUA.

Note: ALUA is also known as Target Port Group Support (TPGS).

ALUA defines a standard set of SCSI commands for discovering path priorities to LUNs on FCSANs. When you have the host and storage controller configured to use ALUA, it automaticallydetermines which target ports provide optimized and unoptionized access to LUNs.

Note: ALUA is not supported when you are running the iSCSI protocol. It is only supported withthe FC protocol.

ALUA is automatically enabled for Linux operating system when you set up your storage.

The following configurations support ALUA:

Host Utilities Version Host requirements Data ONTAP versions

Host Utilities 4.0 and later • Red Hat Enterprise Linux 5Update 2 and later

• SUSE Linux Enterprise Server10 SP2 and later

• SUSE Linux Enterprise Server11

Note: Veritas StorageFoundation 5.1 and later supportALUA with the FC protocol.

7.2.4 and later

(FC) Solaris Host Utilities configurations that support ALUAThe Solaris Host Utilities support ALUA in both MPxIO environments and certain Veritas StorageFoundation environments as long as the environments are running the FC protocol. ALUA is notsupported in environments running the iSCSI protocol.

If you are using MPxIO with FC and active/active storage controllers with any of the followingconfigurations, you must have ALUA enabled:


Host Utilities 4.1 through 5.1 Solaris 10 update 3 and later 7.2.1.1 and later



Host Utilities 4.0 Solaris 10 update 2 only withQLogic drivers and SPARCprocessors

7.2.1 and later

If you are running the Host Utilities with Veritas Storage Foundation 5.1 P1 and the FC protocol, youcan use ALUA.

Note: Earlier versions of Veritas Storage Foundation do not support ALUA.

Windows configurations that support ALUAWindows hosts support ALUA with certain combinations of Windows, Data ONTAP, Host Utilities,and MPIO software.

The following table lists configurations that support ALUA (asymmetric logical unit access). Use theInteroperability Matrix to determine a supported combination of Windows, Data ONTAP, HostUtilities, and MPIO software. Then enable or disable ALUA based on the information in the table.

Windows version MPIO software Minimum Data ONTAP Supported ?

Server 2008

Server 2008 R2

Microsoft DSM (msdsm) 7.3.0 Yes

Server 2008 SP2

Server 2008 R2

Data ONTAP DSM 3.4 andlater

7.3.2 Yes

Server 2008

Server 2008 R2

Data ONTAP DSM 3.3.1 andearlier

none No

Server 2008

Server 2008 R2

Veritas DSM from StorageFoundation for Windows 5.1and earlier

none No

Server 2003 SP2

Server 2003 R2

Data ONTAP DSM 3.4 andlater

7.3.2 Yes

Server 2003 Data ONTAP DSM 3.3.1 andearlier

none No

Server 2003 Veritas DSM from StorageFoundation for Windows 5.1and earlier

none No

Note: For MPIO software not listed in this table, see the documentation for that software forupdated ALUA support and requirements.


ALUA is required for FC paths when using the Microsoft DSM (msdsm) or the Data ONTAP DSM3.4 or later. ALUA is not currently supported for iSCSI paths.


Configuration limits

Configuration limits are available for FC , FCoE, and iSCSI topologies. In some cases, limits mightbe theoretically higher, but the published limits are tested and supported.

Next topics

Configuration limit parameters and definitions on page 85

Host operating system configuration limits for iSCSI and FC on page 87

62xx single-controller limits on page 88

62xx HA configuration limits on page 89


32xx HA configuration limits on page 91

60xx and 31xx single-controller limits on page 92

60xx and 31xx HA pair limits on page 93


30xx HA pair limits on page 95

FAS2040 single-controller limits on page 96

FAS2040 HA pair configuration limits on page 97

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.

Configuration limits | 85

Parameter Definition

LUNs per controller 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.

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

iSCSI sessions percontroller

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 percontroller

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. For example, /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

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 configuration limits for iSCSI and FCEach 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.

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 ports perhost

28 16 16 16 16 16

LUNs per host 64(Windows2000)

128(Windows2003)

255(Windows2008)

1024devices max(where eachpath to aLUN is adevice)

11iv2: 512

11iv3: 1024

512 128 3.x: 256

4.x: 256

Localdrives, CD-ROM, andso on countagainst thisvalue.

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 16 TB 16 TB 11iv2: 2 TB

11iv3: 16TB

16 TB 16 TB 2 TB

Related references



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


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


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

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

FC queue depth availableper port

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


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


24 24 24

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 2,048

(4,096 with PVRapproval)

2,048

4,096 (with PVRapproval)

2,048



1,966 1,966 1,966

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

FC port fan-in 64 64 64

Connected hosts per HApair (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

48 48 48


Related information






Parameter 3210 3240 3270



1966 1966 1966

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



256 256 256


256 256 512

igroups per controller 256 256 512



4,096 4,096 8,192




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 2,048



1,966 1,966 1,966

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


Connected hosts per HAconfiguration (FC)

256 256 256

512 (with PVR approval)

iSCSI sessions per HAconfiguration

512 512 1,024

igroups per HAconfiguration

512 512 1024


LUN mappings per HAconfiguration

4,096 4,096 8,192





Parameter 3210 3240 3270


FC target ports per HAconfiguration

20 48 48

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



1966 1966 1966

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



256 256 256


256 256 512

igroups per controller 256 256

8.0.1 and later: 1024

256

8.0.1 and later: 1024



4,096 8,192 8,192






LUN size 16 TB (might requirededuplication and thinprovisioning)

16 TB (might requirededuplication and thinprovisioning)



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.


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.





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

2,048


2,048



1,720 1,720 1,720

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






Connected hosts per HApair (FC)

256

512 (available on the3160A and 3170A withPVR approval)

256


256


iSCSI sessions per HApair

512 512 1,024

igroups per HA pair 256

512 (available on the3160A and 3170A withPVR approval)

256


8.0.1 and later: 2048

256


8.0.1 and later: 2048


LUN mappings per HApair

4,096

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

8,192 8,192


LUN size 16 TB (might requirededuplication and thinprovisioning)



FC target ports per HApair

32 32 3216

Related references


Related information









Parameter 3040 and 3070

LUNs per controller 2,048

FC queue depth available per port 1,720

LUNs per volume 2,048

Port fan-in 64

Connected hosts per storage controller (FC) 256

iSCSI sessions per controller 256

igroups per controller 256

Initiators per igroup 256

LUN mappings per controller 4,096

LUN path name length 255

LUN size 16 TB (might require deduplication and thinprovisioning)

FC target ports per controller Data ONTAP 7.3.0: 8

7.3.1 and later: 12

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 queue depth available per port 1,720


FC port fan-in 64

Connected hosts per HA pair (FC) 256

iSCSI sessions per HA pair 512



LUN mappings per HA pair 4,096



FC target ports per HA pair Data ONTAP 7.3.0: 16

7.3.1: 24

Related references


Related information


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







Parameter FAS2040

LUNs per controller 1,024

FC queue depth available per port 1720


FC port fan-in 64

Connected hosts per controller (FC) 128

iSCSI sessions per controller 128

igroups per controller 256


LUN mappings per controller 4,096



FC target ports per controller 2

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 queue depth available per port 1720


FC port fan-in 64

Connected hosts per HA pair (FC) 128

iSCSI sessions per HA pair 128



LUN mappings per HA pair 4,096



FC target ports per HA pair 4

Related references


Related information





Index20xx 96, 97

HA pair configuration limits 97single-controller limits 96

3040 and 3070 51–55direct-attached HA pair FC topologies 55direct-attached single-controller FC topologies 54multifabric HA pair FC topologies 53single-fabric HA pair FC topologies 52single-fabric single-controller FC topologies 51

30xx 50, 94, 95FC topologies 50HA pair configuration limits 95single-controller configuration limits 94target port configuration 50

31xx 43–46, 48, 49, 92, 93FC topologies 43direct-attached HA pair FC topologies 49direct-attached single-controller FC topologies 48HA pair configuration limits 93multifabric HA pair FC topologies 46single-controller configuration limits 92single-fabric HA pair FC topologies 45single-fabric single-controller FC topologies 44target port configuration 44

32xx 37–42, 90, 91FC topologies 37direct-attached HA FC topologies 42direct-attached single-controller FC topologies 41HA configuration limits 91multifabric HA configuration 40single-controller configuration limits 90single-fabric HA configuration 39single-fabric single-controller FC topologies 38target port configuration 38

60xx 30–32, 34–36, 92, 93FC topologies 30direct-attached HA pair FC topologies 36direct-attached single-controller FC topologies 35HA pair configuration limits 93multifabric HA pair FC topologies 34single-controller configuration limits 92single-fabric HA pair FC topologies 32single-fabric single-controller FC topologies 31target port configuration 30

62xx 24–26, 28, 29, 88, 89FC topologies 24

direct-attached HA pair FC topologies 29direct-attached single-controller FC topologies 28HA configuration limits 89multifabric HA pair FC topologies 26single-controller configuration limits 88single-fabric HA pair FC topologies 25single-fabric single-controller FC topologies 24target port configuration 24

A

AIX 87host configuration limits 87

ALUA 79, 81–83ESX configurations supported 81supported AIX configurations 79supported configurations 82supported environments 82Windows configurations supported 83

ALUA configurations 79asymmetric logical unit access (ALUA) configurations

79

C

configuration limits 85, 87–9720xx HA pair storage systems 9720xx single-controller storage systems 9630xx HA pair storage systems 9530xx single-controller storage systems 9431xx HA pair storage systems 9331xx single-controller storage systems 9232xx HA configurations 9132xx single-controller storage systems 9060xx HA pair storage systems 9360xx single-controller storage systems 9262xx HA configuration storage systems 8962xx single-controller storage systems 88by host operating system 87N7750T HA configuration storage systems 89parameters defined 85

configurations 64FCoE 64

Index | 99

D

DCB (data center bridging) switch 63for FCoE 63

direct-attached configuration 18iSCSI 18

direct-attached HA FC topologies 4232xx 42

direct-attached HA pair FC topologies 29, 36, 49, 55, 613040 and 3070 5531xx 4960xx 3662xx 29FAS20xx 61

direct-attached single-controller FC topologies 28, 35,41, 48, 54, 60

3040 and 3070 5431xx 4832xx 4160xx 3562xx 28FAS20xx 60

dynamic VLANs 19

E

EMC CLARiiON 77shared configurations 77

ESX 81, 87host configuration limits 87supported ALUA configurations 81

expansion FC ports 22usage rules 22

F

FAS20xx 56–61FC topologies 56direct-attached HA pair FC topologies 61direct-attached single-controller FC topologies 60multifabric HA pair FC topologies 59multifabric single-controller FC topologies 58single-fabric HA pair FC topologies 57single-fabric single-controller FC topologies 56

FC 21–24, 30, 37, 38, 43, 44, 50, 56, 71–7430xx target port configuration 5030xx topologies 5031xx target port configuration 4431xx topologies 4332xx target port configuration 38

32xx topologies 3760xx target port configuration 3060xx topologies 3062xx target port configuration 2462xx topologies 24FAS20xx topologies 56multifabric switch zoning 74onboard and expansion port usage rules 22single-fabric switch zoning 73switch configuration 23switch hop count 23switch port zoning 72switch WWN zoning 72switch zoning 71switch zoning with individual zones 72topologies overview 21

FC protocol 79, 82ALUA configurations 79, 82

FCoE 63, 64, 71initiator and target combinations 63, 64supported configurations 64switch zoning 71

FCoE topologies 65–67, 69FCoE initiator to FC target 65FCoE initiator to FCoE and FC mixed target 67FCoE initiator to FCoE target 66FCoE initiator to FCoE target mixed with IP traffic

69Fibre Channel over Ethernet (FCoE) 63

overview 63

H

HA pair 15, 17, 18iSCSI direct-attached configuration 18iSCSI multinetwork configuration 17iSCSI single-network configuration 15

hard zoning 72FC switch 72

heterogeneous SAN 21using VSAN 21

hop count 23for FC switches 23

host multipathing software 23when required 23

HP-UX 87host configuration limits 87


Iinitiator FC ports 22

onboard and expansion usage rules 22initiators 63, 64

FCoE and FC combinations 63, 64inter-switch links (ISLs) 23

supported hop count 23IP traffic 69

in FCoE configurations 69iSCSI 15, 17–19

direct-attached configuration 18dynamic VLANs 19multinetwork configuration 17single-network configuration 15static VLANs 19topologies 15using VLANs 19

LLinux 87

host configuration limits 87Linux configurations 82

ALUA support 82automatically enabled 82

asymmetric logical unit access 82Target Port Group Support 82

MMPIO 79

ALUA configurations 79MPIO software 23

when required 23MPxIO 82

ALUA configurations 82multifabric HA pair FC topologies 26, 34, 40, 46, 53, 59


multifabric single-controller FC topologies 58FAS20xx 58

multipathing software 23when required 23

NN7750T 89

HA configuration limits 89

O

onboard FC ports 22usage rules 22

P

parameters 85configuration limit definitions 85

point-to-point 23FC switch port topology 23

port topology 23FC switch 23

port zoning 72FC switch 72

PowerPath 77with shared configurations 77

S

shared SAN configurations 77single-fabric HA pair FC topologies 25, 32, 45, 52, 57

3040 and 3070 5231xx 4560xx 3262xx 25FAS20xx 57

single-fabric HA topologies 3932xx 39

single-fabric single-controller FC topologies 24, 31, 38,44, 51, 56


soft zoning 72FC switch 72

Solaris 87host configuration limits 87

static VLANs 19supported configurations 64

FCoE 64switch 23, 71–74

FC configuration 23FC hop count 23FC multifabric zoning 74FC port zoning 72FC single-fabric zoning 73

Index | 101

FC WWN zoning 72FC zoning 71FC zoning with individual zones 72FCoE zoning 71

T

target FC ports 22onboard and expansion usage rules 22

target port configurations 24, 30, 38, 44, 5030xx 5031xx 4432xx 3860xx 3062xx 24

targets 63, 64FCoE and FC combinations 63, 64

topologies 15, 21, 24, 30, 37, 43, 50, 56, 65–67, 6930xx FC topologies 5031xx FC topologies 4332xx FC topologies 3760xx FC topologies 3062xx FC topologies 24FAS20xx FC topologies 56FC 21FCoE initiator to FC target 65FCoE initiator to FCoE and FC mixed target 67FCoE initiator to FCoE target 66FCoE initiator to FCoE target mixed with IP traffic

69iSCSI 15

topologies, 3040 and 3070 51–55direct-attached HA pair FC configuration 55direct-attached single-controller FC topologies 54multifabric HA pair FC configuration 53single-fabric HA pair FC configuration 52single-fabric single-controller FC topologies 51

topologies, 31xx 44–46, 48, 49direct-attached HA pair FC configuration 49direct-attached single-controller FC topologies 48multifabric HA pair FC configuration 46single-fabric HA pair FC configuration 45single-fabric single-controller FC topologies 44

topologies, 32xx 38–42direct-attached HA FC configuration 42direct-attached single-controller FC topologies 41multifabric HA configuration 40single-fabric HA configuration 39single-fabric single-controller FC topologies 38

topologies, 60xx 31, 32, 34–36

direct-attached HA pair FC configuration 36direct-attached single-controller FC topologies 35multifabric HA pair FC configuration 34single-fabric HA pair FC configuration 32single-fabric single-controller FC topologies 31

topologies, 62xx 24–26, 28, 29direct-attached HA pair FC configuration 29direct-attached single-controller FC topologies 28multifabric HA pair FC configuration 26single-fabric HA pair FC configuration 25single-fabric single-controller FC topologies 24

topologies, FAS20xx 56–61direct-attached HA pair FC configuration 61direct-attached single-controller FC topologies 60multifabric HA pair FC configuration 59multifabric single-controller FC topologies 58single-fabric HA pair FC configuration 57single-fabric single-controller FC topologies 56

V

Veritas 82ALUA configurations 82

virtual LANs 19reasons for using 19

VLANs 19dynamic 19reasons for using 19static 19

VSAN 21for heterogeneous SAN 21

W

Windows 83, 87host configuration limits 87supported ALUA configurations 83

WWN zoning 72FC switch 72

Z

zoning 71–74FC switch 71FC switch by port 72FC switch by WWN 72FC switch multifabric 74FC switch single-fabric 73FC switch with individual zones 72


FCoE switch 71

Index | 103

Documents

Netappfc Iscsi Config Guide 80