Fibre Channel and iscsi Configuration Guide

(1)

for 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-NETAPP

Documentation comments: doccomments@netapp.com Information Web: http://www.netapp.com

Part number 215-04943_A0 December 2009

(2)

(3)

Copyright information ... 7

Trademark information ... 9

About this guide ... 11

Audience ... 11

Terminology ... 11

Keyboard and formatting conventions ... 12

Special messages ... 13

How to send your comments ... 14

iSCSI topologies ... 15

Single-network active/active configuration in an iSCSI SAN ... 15

Multinetwork active/active configuration 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 ... 21

FC onboard and expansion port combinations ... 22

Fibre Channel supported hop count ... 23

Fibre Channel switch configuration best practices ... 23

The cfmode setting ... 23

Host multipathing software requirements ... 24

60xx supported topologies ... 24

60xx target port configuration recommendations ... 25

60xx: Single-fabric single-controller configuration ... 26

60xx: Single-fabric active/active configuration ... 27

60xx: Multifabric active/active configuration ... 28

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

60xx: Direct-attached active/active configuration ... 31

31xx: Single-fabric single-controller configuration ... 33

(4)

31xx: Multifabric active/active configuration ... 35

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

31xx: Direct-attached active/active configuration ... 37

3040 and 3070 supported topologies ... 39

3020 and 3050 supported topologies ... 45

FAS20xx supported topologies ... 51

FAS20xx: Single-fabric single-controller configuration ... 51

FAS20xx: Single-fabric active/active configuration ... 52

FAS20xx: Multifabric single-controller configuration ... 53

FAS20xx: Multifabric active/active configuration ... 54

FAS20xx: Direct-attached single-controller configurations ... 55

FAS20xx: Direct-attached active/active configuration ... 56

FAS270/GF270c supported topologies ... 57

FAS270/GF270c: Single-fabric active/active configuration ... 57

FAS270/GF270c: Multifabric active/active configuration ... 58

FAS270/GF270c: Direct-attached configurations ... 59

Other Fibre Channel topologies ... 60

R200 and 900 series supported topologies ... 60

Fibre Channel over Ethernet overview ... 67

FCoE initiator and target combinations ... 67

Fibre Channel over Ethernet supported topologies ... 68

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

FCoE: FCoE end-to-end configuration ... 70

FCoE: FCoE mixed with FC ... 71

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

Fibre Channel and FCoE zoning ... 75

Port zoning ... 76

World Wide Name based zoning ... 76

Individual zones ... 76

Single-fabric zoning ... 77

Dual-fabric active/active configuration zoning ... 78

Shared SAN configurations ... 81

ALUA configurations ... 83

(5)

ESX configurations that support ALUA ... 85

HP-UX configurations that support ALUA ... 85

Linux configurations that support ALUA ... 86

(MPxIO/FC) Solaris Host Utilities configurations that support ALUA ... 86

Windows configurations that support ALUA ... 87

Configuration limits ... 89

Configuration limit parameters and definitions ... 89

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

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

60xx and 31xx active/active configuration limits ... 93

30xx single-controller limits ... 95

30xx active/active configuration limits ... 96

FAS20xx single-controller limits ... 97

FAS20xx active/active configuration limits ... 98

FAS270/GF270 , 900 series, and R200 single-controller limits ... 100

FAS270c/GF270c and 900 series active/active configuration limits ... 101

(6)

(7)

Copyright information

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 an electronic retrieval system—without prior written permission of the copyright owner.

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

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED 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 not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp.

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

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

(8)

(9)

Trademark information

NetApp, the Network Appliance logo, the bolt design, NetApp-the Network Appliance Company, Cryptainer, Cryptoshred, DataFabric, DataFort, Data ONTAP, Decru, FAServer, FilerView,

FlexClone, FlexVol, Manage ONTAP, MultiStore, NearStore, NetCache, NOW NetApp on the Web, SANscreen, SecureShare, SnapDrive, SnapLock, SnapManager, SnapMirror, SnapMover,

SnapRestore, SnapValidator, SnapVault, Spinnaker Networks, SpinCluster, SpinFS, SpinHA, SpinMove, SpinServer, StoreVault, SyncMirror, Topio, VFM, VFM Virtual File Manager, and WAFL are registered trademarks of NetApp, Inc. in the U.S.A. and/or other countries. gFiler, Network Appliance, SnapCopy, Snapshot, and The evolution of storage are trademarks of NetApp, Inc. in the U.S.A. and/or other countries and registered trademarks in some other countries. The NetApp arch logo; the StoreVault logo; ApplianceWatch; BareMetal; Camera-to-Viewer; ComplianceClock; ComplianceJournal; ContentDirector; ContentFabric; Data Motion; EdgeFiler; FlexShare; FPolicy; Go Further, Faster; HyperSAN; InfoFabric; Lifetime Key Management, LockVault; NOW; ONTAPI; OpenKey, RAID-DP; ReplicatorX; RoboCache; RoboFiler; SecureAdmin; SecureView; Serving Data by Design; Shadow Tape; SharedStorage; Simplicore; Simulate ONTAP; Smart SAN; SnapCache; SnapDirector; SnapFilter; SnapMigrator; SnapSuite; SohoFiler; SpinMirror; SpinRestore; SpinShot; SpinStor; vFiler; VPolicy; and Web Filer are trademarks of NetApp, Inc. in the U.S.A. and other countries. NetApp Availability Assurance and NetApp ProTech Expert 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 Business Machines Corporation in the United States, other countries, or both. A complete and current list of other IBM trademarks is available on the Web at http://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/or other countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft Corporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer,

RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the U.S.A. and/or other countries.

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

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks. NetApp, Inc. NetCache is certified RealSystem compatible.

(10)

(11)

About this guide

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

This document describes the configuration of fabric-attached, network-attached, and direct-attached storage systems in Fibre Channel (FC), Fibre Channel over Ethernet (FCoE), and iSCSI

environments. This guide explains the various topologies that are supported and describes the relevant 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

Terminology on page 11

Keyboard and formatting conventions on page 12

Special messages on page 13

How to send your comments on page 14

Audience

This 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 connecting to 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.

Terminology

To understand the concepts in this document, you might need to know how certain terms are used.

Storage terms

array LUN Refers to storage that third-party storage arrays provide to storage systems running Data ONTAP software. One array LUN is the equivalent of one disk on a native disk shelf.

LUN (Logical Unit Number)

(12)

native disk Refers to a disk that is sold as local storage for storage systems that run Data ONTAP software.

native disk shelf Refers to a disk shelf that is sold as local storage for storage systems that run Data ONTAP software.

storage controller

Refers to the component of a storage system that runs the Data ONTAP operating system and controls its disk subsystem. Storage controllers are also sometimes called controllers, storage appliances, appliances, storage engines, heads, CPU modules, or controller modules.

storage system Refers to the hardware device running Data ONTAP that receives data from and sends data to native disk shelves, third-party storage, or both. Storage systems that run Data ONTAP are sometimes referred to as filers, appliances, storage appliances, V-Series systems, or systems.

third-party storage

Refers to back-end storage arrays, such as IBM, Hitachi Data Systems, and HP, that provide storage for storage systems running Data ONTAP.

Cluster and high-availability terms

active/active configuration

In the Data ONTAP 7.2 and 7.3 release families, refers to a pair of storage systems (sometimes called nodes) configured to serve data for each other if one of the two systems stops functioning. Also sometimes referred to as active/active pairs. In the Data ONTAP 7.1 release family and earlier releases, this

functionality is referred to as a cluster.

cluster In the Data ONTAP 7.1 release family and earlier releases, refers to a pair of storage systems (sometimes called nodes) configured to serve data for each other if one of the two systems stops functioning. In the Data ONTAP 7.3 and 7.2 release families, this functionality is referred to as an active/active configuration.

Keyboard and formatting conventions

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

Keyboard conventions

Convention What it means

(13)

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

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

hyphen (-) Used to separate individual keys. For example, Ctrl-D means holding down the Ctrl 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 -dhostname 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

font

Words or characters you type. What you type is always shown in lowercase letters, unless your program is case-sensitive and uppercase letters are necessary for it to work properly.

Special messages

This document might contain the following types of messages to alert you to conditions that you need to be aware of.

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

(14)

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 comments

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

Your feedback is important in helping us to provide the most accurate and high-quality information. If you have suggestions for improving this document, send us your comments by e-mail to

doccomments@netapp.com. To help us direct your comments to the correct division, include in the subject 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.

(15)

iSCSI topologies

Supported iSCSI configurations include direct-attached and network-attached topologies. Both single-controller and active/active configurations are supported.

In an iSCSI environment, all methods of connecting Ethernet switches to a network approved by the switch vendor are supported. Ethernet switch counts are not a limitation in Ethernet iSCSI

topologies. For specific recommendations and best practices, see the Ethernet switch vendor's documentation.

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

Next topics

Single-network active/active configuration in an iSCSI SAN on page 15

Multinetwork active/active configuration 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 active/active configuration in an iSCSI SAN

You can connect hosts using iSCSI to active/active configuration controllers using a single IP network. The network can consist of one or more switches, and the controllers can be attached to multiple switches. Each controller can have multiple iSCSI connections to the network. The number of 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.

(16)

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

(17)

Multinetwork active/active configuration in an iSCSI SAN

You can connect hosts using iSCSI to active/active configuration controllers using multiple IP networks. To be fully redundant, a minimum of two connections to separate networks per controller is necessary to protect against NIC, network, or cabling failure.

Figure 2: iSCSI multinetwork active/active configuration

Fully redundant Yes

Type of network Multinetwork

(18)

Direct-attached single-controller configurations in an iSCSI

SAN

You can connect hosts using iSCSI directly to controllers. The number of hosts that can be directly connected 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

Fully redundant No, due to the single controller Type of network None, direct-attached

(19)

VLANs

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

Reasons for implementing VLANs

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

• VLANs provide increased security because they limit access between different nodes of an Ethernet network or an IP SAN. VLANs enable you to leverage existing infrastructure while still providing 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 solution available.

Next topics

Static VLANs on page 19

Dynamic VLANs on page 19

Static VLANs

Static VLANs are port-based. The switch and switch port are used to define the VLAN and its members.

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

In some environments, static VLANs are also easier to create and manage because only the switch and port identifier need to be specified, instead of the 48-bit MAC address. In addition, you can label switch port ranges with the VLAN identifier.

Dynamic VLANs

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

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

(20)

(21)

Fibre Channel topologies

Supported FC configurations include single-fabric, multifabric, and direct-attached topologies. Both single-controller and active/active configurations are supported.

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

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 system layers, 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 blade switches. 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 to a fabric, and all are supported.

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

Note: The following sections show detailed SAN configuration diagrams for each type of storage system. For simplicity, the diagrams show only a single fabric or, in the case of the dual-fabric configurations, two fabrics. However, it is possible to have multiple fabrics connected to a single storage 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.

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

The cfmode setting on page 23

Host multipathing software requirements on page 24

60xx supported topologies on page 24

FAS20xx supported topologies on page 51

FAS270/GF270c supported topologies on page 57

Other Fibre Channel topologies on page 60

(22)

FC onboard and expansion port combinations

You can use storage controller onboard FC ports as both initiators and targets. You can also add storage 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. All expansion adapters should be the same speed (2 Gb, 4 Gb, or 8 Gb); you can configure 4-Gb or 8-Gb ports to run at a lower speed if needed for the connected device.

Onboard ports Expansion ports Supported? Initiator + Target None Yes

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

Initiator + Target Initiator only Yes

Initiator + Target Initiator + Target Yes with Data ONTAP 7.3.2 and 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.2 and later

Target only Target only Yes with Data ONTAP 7.3.2 and later, but no FC disk shelf or V-Series configurations or tape support

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

Related concepts

Configuration limits on page 89

Related references

(23)

Fibre Channel supported hop count

The maximum supported FC hop count, or the number of inter-switch links (ISLs) crossed between a particular host and storage system, depends on the hop count that the switch supplier and storage system 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 practices

A fixed link speed setting is highly recommended, especially for large fabrics, because it provides the best 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 setting

The cfmode setting controls how the FC adapters of a storage system in an active/active

configuration log in to the fabric, handle local and partner traffic in normal operation and during takeover, and provide access to local and partner LUNs. The cfmode setting of your storage system and 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 cfmode setting from the storage system console by setting privileges to advanced and then using the fcp set command.

(24)

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

Detailed descriptions of port behavior with each cfmode are available in the Data ONTAP Block Access Management Guide for iSCSI and FC.

For details about migrating to single_image cfmode and reconfiguring hosts, see Changing the Cluster cfmode Setting in Fibre Channel SAN Configurations.

Data ONTAP Blocks Access Management Guide for iSCSI and FC - now.netapp.com/NOW/ knowledge/docs/ontap/ontap_index.shtml

Changing the Cluster cfmode Setting in Fibre Channel SAN Configurations - now.netapp.com/ NOW/knowledge/docs/san/fcp_iscsi_config/

Host multipathing software requirements

Multipathing software is required on a host computer any time it can access a LUN through more than 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, which can lead to data corruption.

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

For single-fabric single-controller configurations, multipathing software is not required if you have a single 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 required unless you use zoning to limit the host to a single path.

60xx supported topologies

60xx 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 be configured as either a target or initiator FC port. 2-Gb target connections are supported with the onboard 2-Gb ports. 4-Gb target connections are supported with 4-Gb target expansion adapters. If you 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 in an active/active configuration.

(25)

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

Additional target connections can be supported using 4-Gb target expansion adapters with Data ONTAP 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 Data ONTAP version 7.3.1. While 8-Gb and 4-Gb target expansion adapters function similarly, 8-Gb targets cannot be combined with 2-Gb or 4-Gb targets (whether using expansion adapters or onboard).

Next topics

60xx target port configuration recommendations on page 25

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

60xx : Single-fabric active/active configuration on page 27

60xx : Multifabric active/active configuration on page 28

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

60xx : Direct-attached active/active configuration on page 31

60xx target port configuration recommendations

For 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 target expansion adapters, the preferred slot order is given in the System Configuration Guide for the version 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

(26)

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

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

Note: The FC target port numbers in the following figure are examples. The actual port numbers might 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 expansion slots into which your target expansion adapters are installed.

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

Fully redundant No, due to the single fabric and single controller Type of fabric Single fabric

(27)

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 target expansion adapters

Type of configuration Single-controller configuration

60xx: Single-fabric active/active configuration

You can connect hosts to both controllers in an active/active configuration using a single FC switch.

(28)

Fully redundant No, due to the single fabric Type of fabric Single fabric

Different host operating systems Yes, with multiple-host configurations

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 ports using target expansion adapters per controller

Type of configuration Active/active configuration

60xx: Multifabric active/active configuration

You can connect hosts to both controllers in an active/active configuration using two or more FC switch fabrics for redundancy.

(29)

Figure 6: 60xx multifabric active/active configuration

Fully redundant Yes Type of fabric Multifabric

(30)

60xx: Direct-attached single-controller configuration

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

Direct-attached configurations typically need the FC ports set to loop mode. Be sure to follow the recommendation of your host operating system provider for FC port settings. You can use the Data ONTAP fcp config mediatype command to set the target ports.

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

Fully redundant No, due to the single controller Type of fabric None

(31)

60xx: Direct-attached active/active configuration

You can connect hosts directly to FC target ports on both controllers in an active/active configuration. The number of hosts is limited by the number of available target ports.

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

Fully redundant Yes Type of fabric None

(32)

31xx supported topologies

31xx systems are available in single-controller and active/active configurations.

The 31xx systems have four onboard 4-Gb FC ports per controller and each port can be configured as either an FC target port or an initiator port. For example, you can configure two ports as SAN targets and 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 Data ONTAP 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 33

31xx : Single-fabric active/active configuration on page 34

31xx : Multifabric active/active configuration on page 35

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

31xx : Direct-attached active/active configuration on page 37

31xx target port configuration recommendations

For best performance and highest availability, use the recommended FC target port configuration. The port pairs on a 31xx 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 target expansion adapters, the preferred slot order is given in the System Configuration Guide for the version of Data ONTAP software being used by the controllers.

(33)

1 0d

2 0d, 0b

3 0d, 0b, 0c

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

31xx: Single-fabric single-controller configuration

Figure 9: 31xx single-fabric single-controller configuration

(34)

31xx: Single-fabric active/active configuration

Figure 10: 31xx single-fabric active/active configuration

(35)

Type of fabric Single fabric

31xx: Multifabric active/active configuration

(36)

31xx: Direct-attached single-controller configurations

(37)

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

31xx: Direct-attached active/active configuration

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

(38)

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

Figure 13: 31xx direct-attached active/active configuration

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 target expansion adapters

30xx supported topologies

30xx systems are available in single-controller and active/active configurations.

Note: 3040 and 3070 controllers support the use of 8-Gb target expansion adapters beginning with Data ONTAP 7.3.1. While 8-Gb and 4-Gb target expansion adapters function similarly, please note that the 8-Gb target expansion adapters cannot be combined with 4-Gb targets (expansion adapters or onboard). 3020 and 3050 controllers do not support the use of 8-Gb target expansion adapters.

(39)

3020 and 3050 controllers support 2-Gb or 4-Gb FC target connections, but you cannot use both on the same controller or on two different controllers in an active/active configuration. If you use target expansion 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 family software. 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 Data ONTAP 7.3. However, converting to single_image cfmode is recommended.

Next topics

3040 and 3070 supported topologies on page 39

3020 and 3050 supported topologies on page 45

30xx target port configuration recommendations

For best performance and highest availability, use the recommended FC target port configuration. The port pairs on a 30xx controller that share an ASIC are 0a+0b, 0c+0d.

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

1 0d

2 0d, 0b

3 0d, 0b, 0c

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

3040 and 3070 supported topologies

3040 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 be configured as either an FC target port or an initiator port. For example, you can configure two ports as SAN targets and two ports as initiators for disk shelves.

Next topics

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

3040 and 3070 : Single-fabric active/active configuration on page 41

(40)

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

3040 and 3070 : Direct-attached active/active configuration on page 44

3040 and 3070: Single-fabric single-controller configuration

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

(41)

3040 and 3070: Single-fabric active/active configuration

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

(42)

3040 and 3070: Multifabric active/active configuration

Figure 16: 3040 and 3070 multifabric active/active configuration

(43)

3040 and 3070: Direct-attached single-controller configurations

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

(44)

3040 and 3070: Direct-attached active/active configuration

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

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 target expansion adapters

(45)

3020 and 3050 supported topologies

3020 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 be configured 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 3050 controllers. 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 on the same controller or on two different controllers in an active/active configuration. If you use target expansion HBAs, then you can only use onboard ports as initiators.

Next topics

3020 and 3050 : Single-fabric single-controller configuration on page 45

3020 and 3050 : Single-fabric active/active configuration on page 46

3020 and 3050 : Multifabric active/active configuration on page 47

3020 and 3050 : Direct-attached single-controller configurations on page 49

3020 and 3050 : Direct-attached active/active configuration on page 50

3020 and 3050: Single-fabric single-controller configuration

(46)

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

FC ports or adapters One to the maximum number of supported onboard FC ports per controller One to the maximum number of supported 2-Gb or 4-Gb FC target expansion adapters

3020 and 3050: Single-fabric active/active configuration

(47)

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

3020 and 3050: Multifabric active/active configuration

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

(48)

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

Figure 21: 3020 and 3050 multifabric active/active configuration

(49)

3020 and 3050: Direct-attached single-controller configurations

Figure 22: 3020 and 3050 direct-attached single-controller configurations

(50)

3020 and 3050: Direct-attached active/active configuration

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

Fully redundant Yes, if configured with multipathing software 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 2-Gb or 4-Gb FC target expansion adapters

(51)

FAS20xx supported topologies

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

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

Next topics

FAS20xx : Single-fabric single-controller configuration on page 51

FAS20xx : Single-fabric active/active configuration on page 52

FAS20xx : Multifabric single-controller configuration on page 53

FAS20xx : Multifabric active/active configuration on page 54

FAS20xx : Direct-attached single-controller configurations on page 55

FAS20xx : Direct-attached active/active configuration on page 56

FAS20xx: Single-fabric single-controller configuration

Note: The FC target port numbers in the following illustration are examples. The actual port numbers might vary depending on whether you are using onboard ports or an FC target expansion adapter. The FC target expansion adapter is supported only for the FAS2050 controller.

(52)

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

FAS20xx: Single-fabric active/active configuration

(53)

FAS20xx: Multifabric single-controller configuration

You can connect hosts to one controller using two or more FC switch fabrics for redundancy.

Figure 26: FAS20xx multifabric single-controller configuration

Fully redundant No, due to the single controller Type of fabric Multifabric

(54)

FAS20xx: Multifabric active/active configuration

Figure 27: FAS20xx multifabric active/active configuration

(55)

FAS20xx: Direct-attached single-controller configurations

Figure 28: FAS20xx direct-attached single-controller configurations

(56)

FAS20xx: Direct-attached active/active configuration

Figure 29: FAS20xx direct-attached active/active configuration

(57)

FAS270/GF270c supported topologies

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

Next topics

FAS270/GF270c : Single-fabric active/active configuration on page 57

FAS270/GF270c : Multifabric active/active configuration on page 58

FAS270/GF270c : Direct-attached configurations on page 59

FAS270/GF270c: Single-fabric active/active configuration

FC Fabric 1

Host 1 Host 2 Host N

Controller 1 / Controller 2

(58)

Fully Redundant No, due to the single fabric Type of fabric Single fabric

Different host operating systems Yes, with multiple-host configurations Type of configuration Active/active configuration

FAS270/GF270c: Multifabric active/active configuration

Host 1

FC Fabric 1 FC Fabric 2

Host 2 Host 3 Host N

Controller 1 and Controller 2

Figure 31: FAS270/GF270c multifabric active/active configuration

Fully redundant Yes, if a host is dual-attached No, if a host is single-attached Type of fabric Multifabric

Different host operating systems Yes, with multiple-host configurations Type of configuration Active/active configuration

(59)

FAS270/GF270c: Direct-attached configurations

You can connect hosts directly to FC target ports on a single controller or an Active/active configuration. 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 32: FAS270/GF270c direct-attached configurations

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

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

Type of fabric None Different host operating

systems

Yes, with multiple-host configurations

Type of configuration First configuration: Single controller configuration Second configuration: Active/active configuration Third configuration: Active/active configuration

(60)

Other Fibre Channel topologies

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

R200 and 900 series supported topologies

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

Next topics

R200 and 900 series: Single-fabric single-controller configuration on page 61

900 series: Single-fabric active/active configuration on page 62

900 series: Multifabric active/active configuration , one dual-ported FC target expansion adapter on page 63

900 series: Multifabric active/active configuration , two dual-ported FC target expansion adapters on page 64

900 series: Multifabric active/active configuration , four dual-ported FC target expansion adapters on page 65