FC Iscsi Config Guide

iSCSI and Fibre Channel Configuration Guide
NetApp, Inc.
495 East Java Drive
Sunnyvale, CA 94089 USA
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: NA
Processed: Wed Aug 13 08:36:58 2008
Table of Contents | 3
Contents
Copyright information...................................................................................7
Trademark information...............................................................................11
About this guide............................................................................................13
Audience......................................................................................................................13
Accessing Data ONTAP man pages............................................................................14
Terminology.................................................................................................................14
FilerView as an alternative to the command-line interface.........................................16
Command, keyboard, and typographic conventions....................................................17
Special messages.........................................................................................................18
iSCSI topologies............................................................................................19
Dual-network active/active configuration in an iSCSI SAN.......................................19
Single-network active/active configuration in an iSCSI SAN.....................................20
Direct-attached single controller configurations in an iSCSI SAN ............................21
VLANs.........................................................................................................................22
Static VLANs...................................................................................................23
Dynamic VLANs.............................................................................................23
Fibre Channel topologies.............................................................................25
Fibre Channel supported hop count.............................................................................26
Fibre Channel switch configuration best practices......................................................26
The cfmode setting......................................................................................................26
FAS6000 series supported topologies..........................................................................27
FAS6000 series target port configuration recommendations...........................28
FAS6000 series: Dual-fabric active/active configuration,
two onboard FC ports.................................................................................28
four onboard FC ports................................................................................29
eight onboard FC ports...............................................................................31
FAS6000 series: Single-fabric active/active configuration,
two onboard FC ports.................................................................................32
one onboard FC port..................................................................................33
4 | iSCSI and Fibre Channel Configuration Guide
FAS6000 series: Single-fabric single-controller

configuration, one to eight onboard FC adapters.......................................34
two ports of a 4-Gb FC target HBA...........................................................35
one port of a 4-Gb FC target HBA.............................................................37
two 4-Gb FC target HBAs..........................................................................38
one 4-Gb FC target HBA...........................................................................39
FAS6000 series: Single-fabric single-controller
configuration, one to eight 4-Gb FC target HBAs.....................................41
FAS6000 series: Direct-attached active/active
configuration, one 4-Gb FC target HBA....................................................42
FAS6000 series: Direct-attached active/active
configuration, one onboard FC port...........................................................43
FAS6000 series: Direct-attached single-controller
configuration, 2-Gb or 4-Gb FC ports.......................................................43
FAS31xx series supported topologies..........................................................................44
FAS31xx series target port configuration recommendations...........................45
FAS3140 and FAS3170 supported topologies.................................................45
FAS3140 and FAS3170: Dual-fabric active/active
configuration, two onboard FC ports.........................................................46
configuration, one onboard FC port...........................................................46
configuration, four onboard FC ports........................................................47
FAS3140 and FAS3170: Single-fabric active/active
configuration, two onboard FC ports.........................................................48
FAS3140 and FAS3170: Single-fabric single-controller
configuration, one to four 4-Gb FC target HBAs......................................49
configuration, one 4-Gb FC target HBA....................................................50
configuration, two ports of multiple 4-Gb FC target HBAs......................51
Table of Contents | 5
FAS3140 and FAS3170: Direct-attached active/active

configuration, one port of a 4-Gb FC target HBA.....................................52
FAS30xx series supported topologies..........................................................................53
FAS30xx series target port configuration recommendations...........................54
FAS2000 series supported topologies..........................................................................79
FAS2020A and FAS2050A supported topologies...........................................80
FAS270 supported topologies......................................................................................86
FAS270c: Dual-fabric active/active configuration..........................................86
FAS270c: Single-fabric active/active configuration........................................87
FAS270: Direct-attached configurations.........................................................88
Other Fibre Channel topologies...................................................................................89
F800 and FAS900 supported topologies..........................................................90
Fibre Channel zoning...................................................................................................97
Port zoning.......................................................................................................98
World Wide Name based zoning.....................................................................98
Individual zones...........................................................................................................99
Single-fabric zoning...................................................................................................100
Dual-fabric active/active configuration zoning..........................................................101
Configuration limits....................................................................................103
Configuration limit parameters and definitions for FC and iSCSI............................103
Host operating system configuration limits for iSCSI and FC..................................104
Configuration limits for single-controller FAS6000 series,
FAS30xx series, and FAS31xx series storage systems........................................105
Configuration limits for active/active FAS6000 series, FAS30xx
series, and FAS31xx series storage systems........................................................107
Configuration limits for FAS2020 and FAS2050 systems.........................................109
Configuration limits for FAS2020A and FAS2050A systems...................................110
Configuration limits for single-controller FAS270, F800, FAS900
series, V-Series, and R200 systems......................................................................111
Configuration limits for active/active FAS270, F800, and FAS900
series systems.......................................................................................................113
Copyright information | 7
Copyright information
Copyright © 1994–2008 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 an electronic retrieval
system—without prior written permission of the copyright owner.
Portions of this product are derived from the Berkeley Net2 release and the 4.4-Lite-2 release, which
are copyrighted and publicly distributed by The Regents of the University of California.
Copyright © 1980–1995 The Regents of the University of California. All rights reserved.
Portions of this product are derived from NetBSD, copyright © Carnegie Mellon University.
Copyright © 1994, 1995 Carnegie Mellon University. All rights reserved. Author Chris G. Demetriou.
Permission to use, copy, modify, and distribute this software and its documentation is hereby granted,
provided that both the copyright notice and its permission notice appear in all copies of the software,
derivative works or modified versions, and any portions thereof, and that both notices appear in
supporting documentation.
CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS “AS IS” CONDITION.
CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES
WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
Software derived from copyrighted material of The Regents of the University of California and Carnegie
Mellon University is subject to the following license and disclaimer:
Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:
Redistributions of source code must retain the above copyright notices, this list of conditions, and the
following disclaimer.
Redistributions in binary form must reproduce the above copyright notices, this list of conditions, and
the following disclaimer in the documentation and/or other materials provided with the distribution.
All advertising materials mentioning features or use of this software must display this text:
This product includes software developed by the University of California, Berkeley and its contributors.
Neither the name of the University nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS 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.
This software contains materials from third parties licensed to NetApp Inc. which is sublicensed, and
not sold, and title to such material is not passed to the end user. All rights reserved by the licensors.
You shall not sublicense or permit timesharing, rental, facility management or service bureau usage of
the Software.
Portions developed by the Apache Software Foundation (http://www.apache.org/). Copyright © 1999
The Apache Software Foundation.
Portions Copyright © 1995–1998, Jean-loup Gailly and Mark Adler
Portions Copyright © 2001, Sitraka Inc.
Portions Copyright © 2001, iAnywhere Solutions
Portions Copyright © 2001, i-net software GmbH
Portions Copyright © 1995 University of Southern California. All rights reserved.
Redistribution and use in source and binary forms are permitted provided that the above copyright
notice and this paragraph are duplicated in all such forms and that any documentation, advertising
materials, and other materials related to such distribution and use acknowledge that the software was
developed by the University of Southern California, Information Sciences Institute. The name of the
University may not be used to endorse or promote products derived from this software without specific
prior written permission.
Portions of this product are derived from version 2.4.11 of the libxml2 library, which is copyrighted
by the World Wide Web Consortium.
NetApp modified the libxml2 software on December 6, 2001, to enable it to compile cleanly on Windows,
Solaris, and Linux. The changes have been sent to the maintainers of libxml2. The unmodified libxml2
software can be downloaded from http://www.xmlsoft.org/.
Copyright © 1994–2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut
National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved.
http://www.w3.org/Consortium/Legal/
Software derived from copyrighted material of the World Wide Web Consortium is subject to the
following license and disclaimer:
Permission to use, copy, modify, and distribute this software and its documentation, with or without
modification, for any purpose and without fee or royalty is hereby granted, provided that you include
the following on ALL copies of the software and documentation or portions thereof, including
modifications, that you make:
The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
Copyright information | 9
Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a
short notice of the following form (hypertext is preferred, text is permitted) should be used within the
body of any redistributed or derivative code: “Copyright © [$date-of-software] World Wide Web
Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique
et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/”
Notice of any changes or modifications to the W3C files, including the date changes were made.
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED “AS IS,” AND COPYRIGHT
HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR
DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR
DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining
to the software without specific, written prior permission. Title to copyright in this software and any
associated documentation will at all times remain with copyright holders.
Software derived from copyrighted material of NetApp, Inc. is subject to the following license and
disclaimer:
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).
Trademark information | 11
Trademark information
All applicable trademark attribution is listed here.
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; EdgeFiler; FlexShare; FPolicy; Go Further, Faster; HyperSAN;
InfoFabric; Lifetime Key Management, LockVault; NOW; ONTAPI; OpenKey, RAID-DP; ReplicatorX;
RoboCache; RoboFiler; SecureAdmin; Serving Data by Design; SharedStorage; Simplicore; Simulate
ONTAP; Smart SAN; SnapCache; SnapDirector; SnapFilter; SnapMigrator; SnapSuite; SohoFiler;
SpinMirror; SpinRestore; SpinShot; SpinStor; vFiler; Virtual File Manager; 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, AIX, and System Storage are trademarks and/or registered trademarks of
International Business Machines Corporation.
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.
About this guide | 13
About this guide

Here you can learn what this document describes and who it is intended for, what special terminology
is used in the document, what command, keyboard, and typographic conventions this document uses
to convey information, and other details about finding and using information.
This document describes the configuration of fabric-attached and network-attached storage systems in
iSCSI and FC environments. This guide explains the various topologies that are supported and describes
the relevant SAN configuration limits for each model.
For detailed compatibility matrices, including information on Operating Systems (OS), FC switches,
host bus adapters (HBAs), storage systems, and Data ONTAP versions, see the Compatibility and
Configuration Guide for NetApp FC and iSCSI Products on the NOW site.
Next topics
Audience on page 13
Accessing Data ONTAP man pages on page 14
Terminology on page 14
FilerView as an alternative to the command-line interface on page 16
Command, keyboard, and typographic conventions on page 17
Special messages on page 18
Related information
Compatibility and Configuration Guide for NetApp FCP and iSCSI Products
Audience
Here you can learn who this document is written for and the assumptions that were made about the
preexisting knowledge and experience you have.
This document is for system administrators who are familiar with operating systems such as UNIX®
and Windows® that run on the storage system's clients.
This guide assumes that you are familiar with basic Fibre Channel and iSCSI solutions and termonology.
This guide doesn’t cover basic system or network administration topics, such as IP addressing, routing,
and network topology; it emphasizes the characteristics of the storage system.
Accessing Data ONTAP man pages

You can use the Data ONTAP manual (man) pages to access technical information.
Considerations
Data ONTAP man pages are available for the following types of information. They are grouped into
sections according to standard UNIX naming conventions.
Types of information Man page section
Commands 1
Special files 4
File formats and conventions 5
System management and services 8
Step
1. View man pages in the following ways:

• By entering the following command at the storage system command line:
man command_or_file_name
• By clicking the manual pages button on the main Data ONTAP navigational page in the FilerView
user interface
• By using the Commands: Manual Page Reference, Volumes 1 and 2 (which can be downloaded
or ordered through the NOW NetApp on the Web site)
Note: All Data ONTAP man pages are stored in the storage system in files whose names are
prefixed with the string "na_" to distinguish them from client man pages. The prefixed names are
used to distinguish storage system man pages from other man pages and sometimes appear in the
NAME field of the man page, but the prefixes are not part of the command, file, or services.
Terminology
To understand the concepts in this document, you might need to know the terms defined here.
General storage system terminology

• Storage systems that run Data ONTAP are sometimes referred to as filers, appliances, storage
appliances, or systems. The name of the FilerView graphical user interface for Data ONTAP reflects
one of these common usages.
• Controller or storage controller refers to the component of a storage system that runs the Data
ONTAP operating system and controls its disk subsystem. Controllers or storage controllers are
also sometimes called storage appliances, appliances, storage engines, heads, CPU modules, or
controller modules.
Active/active configuration terminology

• An active/active configuration is a pair of storage systems configured to serve data for each other
if one of the two systems becomes impaired. In Data ONTAP documentation and other information
resources, active/active configurations are sometimes also referred to as clusters or active/active
pairs.
• When in an active/active configuration, systems are often called nodes. One node is sometimes
called the local node, and the other node is called the partner node or remote node.
• Controller failover, also referred to as cluster failover or CFO, refers to the technology that enables
two storage systems to take over each other's data, thus improving data availability.
• Fabric-attached MetroCluster refers to an active/active configuration running the syncmirror_local
and cluster_remote licenses, where the nodes are attached to two pairs of Fibre Channel switches,
and they are separated by more than 500 meters.
• FC direct-attached topologies are topologies in which the hosts are directly attached to the storage
system. Direct-attached systems do not use a fabric or FC switches.
• FC dual fabric topologies are topologies in which each host is attached to two physically independent
fabrics that are connected to storage systems. Each independent fabric can consist of multiple FC
switches. A fabric that is zoned into two logically independent fabrics is not a dual fabric connection.
• FC single fabric topologies are topologies in which the hosts are attached to the storage systems
through a single FC fabric. The fabric can consist of multiple FC switches.
• iSCSI direct-attached topologies are topologies in which the hosts are directly attached to the storage
controller. Direct-attached systems do not use networks or Ethernet switches.
• iSCSI network-attached topologies are topologies in which the hosts are attached to storage controllers
through Ethernet switches. Networks can contain multiple Ethernet switches in any configuration.
• Mirrored active/active configuration is similar to the standard active/active configuration, except
that there are two copies, or plexes, of the data. This is also called data mirroring.
• Remote storage refers to the storage that is accessible to the local node, but is at the location of the
remote node.
• Single storage controller configurations are topologies in which there is only one storage controller
used. Single storage controller configurations have a single point of failure and do not support
cfmodes in FC SAN configurations.
• Standard active/active configuration refers to a configuration set up so that one node automatically
takes over for its partner when the partner node becomes impaired.
• Stretch MetroCluster refers to an active/active configuration running the syncmirror_local and
cluster_remote licenses, where the nodes are separated by up to 500 meters, and no switches are
used between the nodes. This configuration is also sometimes called a nonswitched MetroCluster.
Storage hardware terminology

• AT-FCX refers to an enhanced FC-AL to Serial ATA (SATA) bridge used in some disk shelves.
• Disk shelf refers to a unit of the disk subsystem component of the storage system.
• ESH (Embedded Switching Hub) disk shelf module refers to a component that provides a means of
managing an FC-AL loop in an intelligent manner, such that a single drive failure does not take
down the loop. It also contains the enclosure services processor, which communicates the
environmental data of the disk shelf.
• ESH2 disk shelf module refers to a second-generation ESH module.
• ESH4 disk shelf module refers to a third-generation ESH module.
• FC HBA for Disk or FC HBA refers to the Fibre Channel host bus adapter that connects the node
to the switch or to the disks.
• Host bus adapters (HBAs) are FC or iSCSI I/O adapters that connect a host I/O bus to a computer's
memory system in SCSI environments.
• Target adapters are I/O adapters that reside on the storage system and receive data from the host.
A target adapter that is already attached to the storage system controller is an onboard adapter; a
target adapter that is separately installed in one of the system’s available slots is a target expansion
adapter. Onboard adapters can also be configured to operate in initiator mode in which they connect
to disk shelves. Most storage systems also support the use of expansion adapters that operate in
initiator mode.
General terms
• The term enter 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 typing information into it.
• The term type means pressing one or more keys on the keyboard.
FilerView as an alternative to the command-line interface

Use the FilerView graphical user interface to perform many common tasks, as well as to view and
manage a storage system from a Web browser.
Your tasks as a Data ONTAP administrator can be performed by entering commands at the storage
system console, in configuration files, or through a Telnet session or Remote Shell connection.
Another method of performing many common tasks is to use FilerView. FilerView comes with every
storage system, is easy to use, and includes Help that explains Data ONTAP features and how to work
with them in FilerView.
For more information about accessing a storage system with FilerView, and about FilerView Help, see
the System Administration Guide.
Command, keyboard, and typographic conventions

This document uses command, keyboard, and typographic conventions that help you enter commands.
Command conventions
In examples that illustrate commands executed on a UNIX workstation, the command syntax and output
might differ, depending on your version of UNIX.
Keyboard conventions
• When describing key combinations, this document uses the hyphen (-) to separate individual keys.
For example, "Ctrl-D" means pressing the "Control" and "D" keys simultaneously.
• This document uses the term "Enter" to refer to the key that generates the digital equivalent of a
carriage return, although the key is named "Return" on some keyboards.
Typographic conventions
The following table describes typographic conventions used in this document.
Convention Type of information
Italic font Words or characters that require special attention.

Placeholders for information 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.
The contents of files.
Bold monospaced Words or characters you type. What you type is always shown in lowercase letters,
font unless you must type it in uppercase letters.
Special messages
This document might contain the following types of messages to alert you to conditions you need to
be aware of. Danger notices and caution notices only appear in hardware documentation, where
applicable.
Note: A note contains important information that helps you install or operate the system efficiently.
Attention: An attention notice contains instructions that you must follow to avoid a system crash,
loss of data, or damage to the equipment.
Danger: A danger notice warns you of conditions or procedures that can result in death or severe
personal injury.
Caution: A caution notice warns you of conditions or procedures that can cause personal injury that
is neither lethal nor extremely hazardous.
iSCSI topologies | 19
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 are equivalent and
all configurations approved by the switch vendor are supported. Ethernet switch counts are not a
limitation in Ethernet iSCSI topologies. Refer to the Ethernet switch vendor documentation for specific
recommendations and best practices.
For Windows iSCSI multipathing options, please see Technical Report 3441.
Next topics
Dual-network active/active configuration in an iSCSI SAN on page 19
Single-network active/active configuration in an iSCSI SAN on page 20
Direct-attached single controller configurations in an iSCSI SAN on page 21
VLANs on page 22
Related information
Technical Report 3441: iSCSI multipathing possibilities on Windows with Data ONTAP
Dual-network active/active configuration in an iSCSI SAN

The following figure and table show the supported topology and attributes specific to this configuration.
To be fully redundant, a minimum of two connections to the network per controller is necessary to
protect against NIC, network, or cabling failure.
Figure 1: iSCSI dual network active/active configuration
Attribute Value
Fully redundant Yes
Type of network Dual network
Different host operating systems Yes, with multiple-host configurations
Multipathing required Yes, to be fully redundant
Type of configuration Active/active configuration
Single-network active/active configuration in an iSCSI SAN

The network can consist of one or multiple switches, and the storage systems can be attached to multiple
switches. Each controller can have multiple iSCSI connections to the network. The number of ports is
based on the FAS system and the number of supported Ethernet ports.
The following figure shows two Ethernet connections to the network per storage controller. Depending
on the storage system, more connections are possible.
Figure 2: 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, if a host has multiple paths to a LUN
Direct-attached single controller configurations in an iSCSI

SAN
Figure 3: iSCSI direct attached-single controller configurations
Attribute Value
Fully redundant No, due to the single controller
Type of network None, direct-attached
Type of configuration Single controller
VLANs
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 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 23
Dynamic VLANs on page 23
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 the 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.
Fibre Channel topologies | 25
Fibre Channel topologies

Supported FC configurations include direct-attached, single-fabric, and dual-fabric 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 dual, physically independent storage fabrics 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 a heterogeneous SAN, or a fabric with storage from multiple vendors, is supported as long
as the storage systems are contained in exclusive zones, or VSANs. A tape SAN should also be in a
separate zone or VSAN, apart from the disk SAN.
Cascade, mesh, and core-edge fabrics are all industry-accepted methods of connecting FC switches into
a fabric, and all are supported.
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 supported to have multiple fabrics connected to a single
storage system. In the case of the dual-fabric configurations, even multiples of fabrics are supported.
This is true for both active/active configurations and single-controller configurations.
Next topics
Fibre Channel supported hop count on page 26
Fibre Channel switch configuration best practices on page 26
The cfmode setting on page 26
FAS6000 series supported topologies on page 27
FAS31xx series supported topologies on page 44
FAS30xx series supported topologies on page 53
FAS2000 series supported topologies on page 79
FAS270 supported topologies on page 86
Other Fibre Channel topologies on page 89
Fibre Channel zoning on page 97
Individual zones on page 99
Single-fabric zoning on page 100
Dual-fabric active/active configuration zoning on page 101
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 5
Cisco 5
McData 3
QLogic 4
Fibre Channel switch configuration best practices

A fixed link speed setting is highly recommended, especially for large fabrics, as it provides the best
performance for fabric rebuild times. In large fabrics, this can create significant time savings..
Although auto-negotiation 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 auto-negotiate.
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.
Single_image cfmode is strongly recommended for all configurations.
Detailed descriptions of port behavior with each cfmode are available in the Data ONTAP Block Access
Management Guide for iSCSI and FCP.
For details about migrating to single_image cfmode and reconfiguring hosts, see Changing the Cluster
cfmode Setting in Fibre Channel SAN Configurations.
Related information
Data ONTAP Blocks Access Management Guide
Changing the Cluster cfmode Setting in Fibre Channel SAN Configurations
FAS6000 series supported topologies

FAS6000 series storage systems are available in single-controller and active/active configurations. They
are also supported by single_image and, in some configurations, standby cfmodes.
Each FAS6000 series storage system is capable of supporting 2-Gb or 4-Gb FC target connections, but
you cannot use both on the same storage system or on two different storage systems in an active/active
configuration.
The FAS6030 and FAS6070 storage system has 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 HBAs. If you use 4-Gb
target HBAs, then you must configure the onboard ports as initiators. FAS6030 and FAS6070 storage
systems are supported by single_image and, in some configurations, standby cfmode.
The FAS6040 and FAS6080 storage system has 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, and additional target connections can be supported using
4-Gb target HBAs with Data ONTAP 7.3 and later. FAS6040 and FAS6080 storage systems are only
supported by single_image cfmode.
Next topics
FAS6000 series target port configuration recommendations on page 28
FAS6000 series: Dual-fabric active/active configuration, two onboard FC ports on page 28
FAS6000 series: Dual-fabric active/active configuration, four onboard FC ports on page 29
FAS6000 series: Dual-fabric active/active configuration, eight onboard FC ports on page 31
FAS6000 series: Single-fabric active/active configuration, two onboard FC ports on page 32
FAS6000 series: Single-fabric active/active configuration, one onboard FC port on page 33
FAS6000 series: Single-fabric single-controller configuration, one to eight onboard FC
adapters on page 34
FAS6000 series: Dual-fabric active/active configuration, two ports of a 4-Gb FC target
HBA on page 35
FAS6000 series: Dual-fabric active/active configuration, one port of a 4-Gb FC target

HBA on page 37
FAS6000 series: Dual-fabric active/active configuration, two 4-Gb FC target HBAs on page 38
FAS6000 series: Single-fabric active/active configuration, one 4-Gb FC target HBA on page 39
FAS6000 series: Single-fabric single-controller configuration, one to eight 4-Gb FC target
HBAs on page 41
FAS6000 series: Direct-attached active/active configuration, one 4-Gb FC target HBA on page 42
FAS6000 series: Direct-attached active/active configuration, one onboard FC port on page 43
FAS6000 series: Direct-attached single-controller configuration, 2-Gb or 4-Gb FC
ports on page 43
FAS6000 series target port configuration recommendations

The following table shows recommended target ports using single_image cfmode.
The port pairs on a FAS6000 series storage system that share an ASIC are 0a+0b, 0c+0d, 0e+0f, 0g+0h.
Number of target ports Ports
1 0h
2 0h, 0d
3 0h, 0d, 0f
4 0h, 0d, 0f, 0b
5 0h, 0d, 0f, 0b, 0g
6 0h, 0d, 0f, 0b, 0g, 0c
7 0h, 0d, 0f, 0b, 0g, 0c, 0e
8 0h, 0d, 0f, 0b, 0g, 0c, 0e, 0a
FAS6000 series: Dual-fabric active/active configuration, two onboard FC ports

Figure 4: FAS6000 series dual-fabric active/active configuration
Attribute Value
Fully redundant Yes
Type of fabric Dual fabric
FC ports or adapters Two onboard FC ports per controller
Supported cfmodes Single_image cfmode
Multipathing required Yes, for full redundancy
FAS6000 series: Dual-fabric active/active configuration, four onboard FC

ports
Each controller can have one or up to the maximum number of target ports supported per controller
connecting into the fabrics. See the system configuration guide for the version of Data ONTAP being
used by the controllers for these values.
Attribute Value
Fully redundant Yes
FC ports or adapters Four onboard FC ports per controller
Supported cfmodes Single_image cfmode and, if host platform supports it,
standby cfmode
FAS6000 series: Dual-fabric active/active configuration, eight onboard FC

ports
Attribute Value
Fully redundant Yes
Attribute Value
FC ports or adapters Eight onboard FC ports per controller
Supported cfmodes Single_image and standby cfmode
FAS6000 series: Single-fabric active/active configuration, two onboard FC

ports
connecting into the fabrics while an active/active configuration can have two or up to the maximum
number of target ports supported per configuration connecting into the fabric. See the system
configuration guide for the version of Data ONTAP being used by the controllers for these values.
Figure 7: FAS6000 series single-fabric active/active configuration

Attribute Value
Fully redundant No, due to the single fabric
Type of fabric Single fabric
Supported cfmodes Single_image and standby cfmodes
Multipathing required Yes, if a host has multiple paths to a single LUN
No, in standby cfmode and with single-attached hosts
FAS6000 series: Single-fabric active/active configuration, one onboard FC

port
Attribute Value
FC ports or adapters One onboard FC port per controller
FAS6000 series: Single-fabric single-controller configuration, one to eight

onboard FC adapters
Figure 9: FAS6000 series single-fabric single-controller configuration
Attribute Value
Fully redundant No, due to the single fabric and single controller
FC ports or adapters One to eight onboard FC ports per controller
Supported cfmodes Not applicable
Type of configuration Single-controller configuration
FAS6000 series: Dual-fabric active/active configuration, two ports of a 4-Gb

FC target HBA
Note: The 4-Gb FC target HBA port numbers (5a and 5b) are examples. The actual port numbers
might vary depending on the expansion slot in which the FC target HBAs are installed.
Attribute Value
Fully redundant Yes
FC ports or adapters Two ports of a 4-Gb FC target HBA per controller
FAS6000 series: Dual-fabric active/active configuration, one port of a 4-Gb

FC target HBA
Note: The 4-Gb FC target HBA port number (5a) is an example. The actual port number might vary
depending on the expansion slot in which the FC target HBA is installed.
Attribute Value
Fully redundant Yes
FC ports or adapters One port of a 4-Gb FC target HBA per controller
Attribute Value
FAS6000 series: Dual-fabric active/active configuration, two 4-Gb FC target

HBAs
Note: The 4-Gb FC target HBA port numbers (5a, 5b, 6a, and 6b) are examples. The actual port
numbers might vary depending on the expansion slots in which the FC target HBAs are installed.
Attribute Value
Fully redundant Yes
Attribute Value
FC ports or adapters Two 4-Gb FC target HBAs per controller
FAS6000 series: Single-fabric active/active configuration, one 4-Gb FC target

HBA
Note: The 4-Gb FC target port numbers (5a and 5b) are examples. The actual port numbers might
vary depending on the expansion slots in which the FC target HBAs are installed.
Attribute Value
FC ports or adapters One 4-Gb FC target HBA per controller
Supported cfmodes Single_image and standby cfmode

FAS6000 series: Single-fabric single-controller configuration, one to eight

4-Gb FC target HBAs
A single controller can have one or up to the maximum number of target ports supported per controller
used by the controller for these values.
Note: The 4-Gb FC target port numbers (5a, 5b, 6a, and 6b) are examples. The actual port numbers
might vary depending on the expansion slots in which the FC target HBAs are installed.
Figure 14: FAS6000 series single-fabric single-controller configuration
Attribute Value
FC ports or adapters One to eight 4-Gb FC target HBAs
Type of configuration Single controller configuration
FAS6000 series: Direct-attached active/active configuration, one 4-Gb FC

target HBA
Additional hosts can be attached directly to 4-Gb FC HBAs in each controller.
You might have to set the Data ONTAP FCP adapter media type to loop on the 4-Gb FC target HBAs
for some direct-attached topologies.
Note: The 4-Gb FC target HBA port number (5a) is an example. The actual port number might vary
Figure 15: FAS6000 series direct-attached active/active configuration
Attribute Value
Fully redundant Yes
Type of fabric None
FC ports or adapters One port of a 4-Gb FC target HBA
FAS6000 series: Direct-attached active/active configuration, one onboard FC

port
Additional hosts can be attached directly to the onboard FC ports on each controller.
Figure 16: FAS6000 series direct-attached active/active configuration
Attribute Value
Fully redundant Yes
Type of fabric None
FC ports or adapters One onboard FC port
FAS6000 series: Direct-attached single-controller configuration, 2-Gb or 4-Gb

FC ports
Figure 17: FAS6000 series direct-attached single-controller configuration
Attribute Value
Type of fabric None
FC ports or adapters 2-Gb or 4-Gb FC ports
Multipathing required Yes, if a host have multiple paths to LUNs
FAS31xx series supported topologies

FAS31xx series storage systems are available in single-controller and active/active configurations.
FAS3140 and FAS3170 systems are supported by single_image cfmode.
Each FAS31xx series storage system supports 4-Gb FC target HBAs.
Next topics
FAS31xx series target port configuration recommendations on page 45
FAS3140 and FAS3170 supported topologies on page 45
FAS31xx series target port configuration recommendations

The port pairs on a FAS31xx series storage system that share an ASIC are 0a+0b, 0c+0d.
1 0d
2 0d, 0b
3 0d, 0b, 0c
4 0d, 0b, 0c, 0a
FAS3140 and FAS3170 supported topologies

FAS3140 and FAS3170 storage systems are available in single-controller and active/active configurations
and are supported by single_image cfmode.
The FAS3140 and FAS3170 storage 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.
Next topics
FAS3140 and FAS3170: Dual-fabric active/active configuration, two onboard FC ports on page 46
FAS3140 and FAS3170: Dual-fabric active/active configuration, one onboard FC port on page 46
FAS3140 and FAS3170: Dual-fabric active/active configuration, four onboard FC ports on page 47
FAS3140 and FAS3170: Single-fabric active/active configuration, two onboard FC
ports on page 48
FAS3140 and FAS3170: Single-fabric single-controller configuration, one to four 4-Gb FC target
HBAs on page 49
FAS3140 and FAS3170: Dual-fabric active/active configuration, one 4-Gb FC target
HBA on page 50
FAS3140 and FAS3170: Dual-fabric active/active configuration, two ports of multiple 4-Gb FC
target HBAs on page 51
FAS3140 and FAS3170: Direct-attached active/active configuration, one port of a 4-Gb FC target
HBA on page 52
FAS3140 and FAS3170: Dual-fabric active/active configuration, two onboard

FC ports
Figure 18: FAS3140 and FAS3170 dual-fabric active/active configuration
Attribute Value
Fully redundant Yes
FAS3140 and FAS3170: Dual-fabric active/active configuration, one onboard

FC port
Attribute Value
Fully redundant Yes
FAS3140 and FAS3170: Dual-fabric active/active configuration, four onboard

FC ports
Attribute Value
Fully redundant Yes
FAS3140 and FAS3170: Single-fabric active/active configuration, two onboard

FC ports
Figure 21: FAS3140 and FAS3170 single-fabric active/active configuration
Attribute Value
FAS3140 and FAS3170: Single-fabric single-controller configuration, one to

four 4-Gb FC target HBAs
numbers might vary, depending on the expansion slot in which the FC target HBAs are installed.
Figure 22: FAS3140 and FAS3170 single-fabric single-controller configuration
Attribute Value
FC ports or adapters One to four 4-Gb FC target HBAs per controller
Multipathing required Yes, if multiple paths to a single LUN
FAS3140 and FAS3170: Dual-fabric active/active configuration, one 4-Gb FC

target HBA
might vary, depending on the expansion slot in which the FC target HBA is installed.
Attribute Value
Fully redundant Yes
FAS3140 and FAS3170: Dual-fabric active/active configuration, two ports of

multiple 4-Gb FC target HBAs
Attribute Value
Fully redundant Yes
FC ports or adapters Two ports of multiple 4-Gb FC target HBAs per controller
FAS3140 and FAS3170: Direct-attached active/active configuration, one port

of a 4-Gb FC target HBA
Note: The 4-Gb FC target HBA port number (2a) is an example. The actual port number might vary,
Figure 25: FAS3140 and FAS3170 direct-attached active/active configuration
Attribute Value
Fully redundant Yes
Type of fabric None
FAS30xx series supported topologies

FAS30xx series storage systems are available in single-controller and active/active configurations.
FAS3020 and FAS3050 systems are supported by single_image, standby, and partner cfmodes. FAS3040
and FAS3070 systems are supported by single_image and standby cfmodes.
Each FAS30xx series storage system supports 2-Gb or 4-Gb FC target connections, but you cannot use
both on the same storage system or on two different storage systems in an an active/active configuration.
If you use target expansion adapters, then you can only use onboard adapters as initiators.
Next topics
FAS30xx series target port configuration recommendations on page 54
FAS30xx series target port configuration recommendations

The port pairs on a FAS30xx series storage system that share an ASIC are 0a+0b, 0c+0d.
1 0d
2 0d, 0b
3 0d, 0b, 0c
4 0d, 0b, 0c, 0a

and are supported by single_image and standby cfmodes.
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
FAS3040 and FAS3070: Dual-fabric active/active configuration, two onboard FC ports on page 55
FAS3040 and FAS3070: Dual-fabric active/active configuration, four onboard FC ports
(single_image cfmode) on page 56
(single_image and standby cfmodes) on page 57
ports on page 58
FAS3040 and FAS3070: Single-fabric single-controller configuration, one to four 4-Gb FC target
HBAs on page 59
FAS3040 and FAS3070: Dual-fabric active/active configuration, two ports of a 4-Gb FC target
HBA on page 60
target HBAs (single_image cfmode) on page 61
target HBAs (single_image and standby cfmodes) on page 62
HBA on page 64
FAS3040 and FAS3070: Dual-fabric active/active configuration, two onboard FC ports

Attribute Value
Fully redundant Yes
FAS3040 and FAS3070: Dual-fabric active/active configuration, one onboard FC port

Attribute Value
Fully redundant Yes

(single_image cfmode)
Note: Although this topology appears similar to a topology with standby cfmode support, the
following diagram shows the difference in cabling. Ports 0a and 0c connect to switch or fabric 1 and
ports 0b and 0d connect to switch or fabric 2.
Attribute Value
Fully redundant Yes

(single_image and standby cfmodes)
Note: Although this topology appears similar to the topology with single_image only cfmode support,
there are significant differences in the cabling. Ports 0a and 0b connect to switch or fabric 1 and ports
0c and 0d connect to switch or fabric 2.
Attribute Value
Fully redundant Yes
FAS3040 and FAS3070: Single-fabric active/active configuration, two onboard FC ports

connecting into the fabrics, while an active/active configuration can have two or up to the maximum
number of target ports supported per configuration connecting into the fabric . See the system
Attribute Value
No, if in standby cfmode and with single-attached hosts
FAS3040 and FAS3070: Single-fabric single-controller configuration, one to four 4-Gb FC

target HBAs
Attribute Value
FC ports or adapters One to four 4-Gb FC target HBAs per controller
Multipathing required Yes, if multiple paths to a single LUN
FAS3040 and FAS3070: Dual-fabric active/active configuration, two ports of a 4-Gb FC target
HBA
Attribute Value
Fully redundant Yes
FC ports or adapters Two ports of a 4-Gb FC target HBA per controller
FAS3040 and FAS3070: Dual-fabric active/active configuration, two ports of multiple 4-Gb
FC target HBAs (single_image cfmode)
Note: Although this topology is similar to the topology supported by standby cfmode, there are
significant differences in the cabling in this configuration. Ports 2a and 4a connect to switch or fabric
1 and ports 2b and 4b connect to switch or fabric 2.
Attribute Value
Fully redundant Yes
FAS3040 and FAS3070: Dual-fabric active/active configuration, two ports of multiple 4-Gb
FC target HBAs (single_image and standby cfmodes)
Note: Although this topology is similar to the topology supported only by single_image only cfmode,
there are significant differences in the cabling. Ports 2a and 2b connect to switch or fabric 1 and ports
4a and 4b connect to switch or fabric 2.
Attribute Value
Fully redundant Yes
FAS3040 and FAS3070: Direct-attached active/active configuration, one port of a 4-Gb FC

target HBA
Attribute Value
Fully redundant Yes
Type of fabric None

and are supported by single_image, partner, and standby cfmodes.
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 FAS3020 and FAS3050
storage system. 4-Gb FC target connections are supported with 4-Gb FC target HBAs.
Each FAS30xx series storage system supports 2-Gb or 4-Gb FC target HBAs, but you cannot use both
on the same storage system or on two different storage systems in an an active/active configuration. If
you use target expansion HBAs, then you can only use onboard ports as initiators.
Next topics
(single_image and partner cfmode) on page 65
FAS3020 and FAS3050: Dual-fabric active/active configuration, four onboard FC ports on page 68
(single_image and partner cfmodes) on page 69
ports on page 70
FAS3020 and FAS3050: Single-fabric single-controller configuration, one to four onboard FC
ports on page 71
FAS3020 and FAS3050: Dual-fabric active/active configuration, one 4-Gb FC target
HBA on page 72
FAS3020 and FAS3050: Dual-fabric active/active configuration, two 4-Gb FC target HBAs
FAS3020 and FAS3050: Dual-fabric active/active configuration, two 4-Gb FC target HBAs (standby
cfmode) on page 74
FAS3020 and FAS3050: Dual-fabric active/active configuration, one port of a 4-Gb FC target
HBA on page 76
HBA on page 77
FAS3020 and FAS3050: Direct-attached active/active configuration, one onboard FC
port on page 77
FAS3020 and FAS3050: Direct-attached single controller configurations, 2-Gb or 4-Gb FC
ports on page 78

(single_image and partner cfmode)
Attribute Value
Fully redundant Yes
Supported cfmodes Single_image and partner cfmodes

Attribute Value
Fully redundant Yes
FAS3020 and FAS3050: Dual-fabric active/active configuration, one onboard FC port

Attribute Value
Fully redundant Yes

Note: Although this topology is similar to the topology supported by single_image and standby
cfmodes, there are significant differences in the cabling. Ports 0a and 0b connect to switch or fabric
1 and ports 0c and 0d connect to switch or fabric 2.
Attribute Value
Fully redundant Yes
Supported cfmodes Single_image, standby, and partner cfmodes

(single_image and partner cfmodes)
Note: Although this topology is similar to the topology supported by single_image, standby, and
partner cfmodes, there are significant differences in the cabling. Ports 0a and 0c connect to switch
or fabric 1 and ports 0b and 0d connect to switch or fabric 2.
Attribute Value
Fully redundant Yes
FAS3020 and FAS3050: Single-fabric active/active configuration, two onboard FC ports

connecting into the fabrics, while an active/active configuration can have two or up to the maximum
Attribute Value
Supported cfmodes Single_image, standby, and partner cfmodes
Multipathing required Yes, in single_image cfmode
FAS3020 and FAS3050: Single-fabric single-controller configuration, one to four onboard

FC ports
Attribute Value
FC ports or adapters One to four onboard FC ports per controller
FAS3020 and FAS3050: Dual-fabric active/active configuration, one 4-Gb FC target HBA
Attribute Value
Fully redundant Yes
Note: Although this topology is similar to the target topology supported by standby cfmode, there
are significant differences in the cabling of this configuration. Ports 2a and 4a connect to switch or
fabric 1 and ports 2b and 4b connect to switch or fabric 2.
Attribute Value
Fully redundant Yes
(standby cfmode)
Note: Although this topology is similar to the target topology supported by single_image only
cfmode, there are significant differences in the cabling of this configuration. Ports 2a and 2b connect
to switch or fabric 1 and ports 4a and 4b connect to switch or fabric 2.
Attribute Value
Fully redundant Yes
FAS3020 and FAS3050: Dual-fabric active/active configuration, one port of a 4-Gb FC target
HBA
Attribute Value
Fully redundant Yes
FAS3020 and FAS3050: Direct-attached active/active configuration, one port of a 4-Gb FC

target HBA
Attribute Value
Fully redundant Yes, if configured with multipathing software
Type of fabric None
FAS3020 and FAS3050: Direct-attached active/active configuration, one onboard FC port

Attribute Value
Fully redundant Yes, when properly configured with multipathing software
Type of fabric None
FAS3020 and FAS3050: Direct-attached single controller configurations, 2-Gb or 4-Gb FC

ports
Figure 49: FAS3020 and FAS3050 direct-attached single-controller configurations
Attribute Value
Type of fabric None
FC ports or adapters 2-Gb or 4-Gb FC ports
FAS2000 series supported topologies

FAS2000 series storage systems are available in single-controller and active/active configurations and
are supported by single_image cfmode.
The FAS2000 series storage systems 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.
FC target HBAs are not supported on the FAS2000 series storage systems.
Next topics
FAS2020A and FAS2050A supported topologies on page 80
FAS2020A and FAS2050A supported topologies

FAS2020A and FAS2050A storage systems are available in active/active configurations and are supported
by single_image cfmode.
Next topics
FAS2020A and FAS2050A: Single-fabric configuration, one to two onboard FC ports on page 80
FAS2020A and FAS2050A: Dual-fabric configuration, one onboard FC port on page 81
FAS2020A and FAS2050A: Dual-fabric configuration, two onboard FC ports on page 82
FAS2020A and FAS2050A: Direct-attached configuration, two onboard FC ports on page 82
FAS2020A and FAS2050A: Single-fabric configuration, one to two onboard FC ports

Figure 50: FAS2020A and FAS2050A single-fabric configuration
Attribute Value
Attribute Value
FC ports or adapters One to two onboard FC ports per controller
FAS2020A and FAS2050A: Dual-fabric configuration, one onboard FC port

Figure 51: FAS2020A and FAS2050A dual-fabric configuration
Attribute Value
Fully redundant Yes
FAS2020A and FAS2050A: Dual-fabric configuration, two onboard FC ports

Figure 52: FAS2020A and FAS2050A dual-fabric configuration
Attribute Value
Fully redundant Yes
FAS2020A and FAS2050A: Direct-attached configuration, two onboard FC ports

Figure 53: FAS2020A and FAS2050A direct-attached configuration
Attribute Value
Fully redundant Yes
Type of fabric None

FAS2020 and FAS2050 storage systems are available in single-controller configurations and are not
supported by a cfmode.
Next topics
FAS2020 and FAS2050: Dual-fabric single-controller configuration, two onboard FC
ports on page 84
FAS2020 and FAS2050: Single-fabric single-controller configuration, two onboard FC
ports on page 84
FAS2020 and FAS2050: Direct-attached single-controller configurations, two onboard FC
ports on page 85
FAS2020 and FAS2050: Dual-fabric single-controller configuration, two onboard FC ports

Figure 54: FAS2020 and FAS2050 dual-fabric single-controller configuration
Attribute Value
FAS2020 and FAS2050: Single-fabric single-controller configuration, two onboard FC ports

Attribute Value
FAS2020 and FAS2050: Direct-attached single-controller configurations, two onboard FC

ports
Figure 56: FAS2020 and FAS2050 direct-attached single-controller configurations
Attribute Value
Type of fabric None
FAS270 supported topologies

FAS270 storage systems are available in active/active configurations and are supported by dual fabric
and single_image cfmodes.
Next topics
FAS270c: Dual-fabric active/active configuration on page 86
FAS270c: Single-fabric active/active configuration on page 87
FAS270: Direct-attached configurations on page 88
FAS270c: Dual-fabric active/active configuration

Figure 57: FAS270c dual-fabric active/active configuration
Attribute Value
Fully redundant Yes, if a host is dual-attached
No, if a host is single-attached

Supported cfmodes Single_image and dual fabric cfmodes
FAS270c: Single-fabric active/active configuration

Figure 58: FAS270c single-fabric active/active configuration
Attribute Value
Fully Redundant No, due to the single fabric
Supported cfmodes Single_image and dual fabric cfmodes
FAS270: Direct-attached configurations

Figure 59: FAS270 direct-attached configurations
Attribute Value
Fully Redundant First configuration: No, due to the single controller
Second configuration: Yes
Third configuration: No, due to a single connection from storage system
to hosts
Type of fabric None

Supported cfmodes Single_image cfmode, highly recommended, and dual fabric cfmode
Type of configuration First configuration: Single controller configuration
Second configuration: Active/active configuration
Third configuration: Active/active configuration
Other Fibre Channel topologies

Other FC storage systems, like the F800 and FAS900 and NearStore storage systems, are no longer
sold, but are still supported.
F800 and FAS900 supported topologies

F800 and FAS900 storage systems are available in single controller and active/active configurations
and are supported in partner, standby, mixed, and single_image cfmodes.
Next topics
F800 and FAS900: Dual-fabric active/active configuration, one dual-ported FC target
HBA on page 90
F800 and FAS900: Dual-fabric active/active configuration, two dual-ported FC target
HBAs on page 91
F800 and FAS900: Dual-fabric active/active configuration, one dual-ported FC target
HBA on page 92
F800 and FAS900: Dual-fabric active/active configuration, four dual-ported FC target
HBAs on page 93
F800 and FAS900: Single-fabric active/active configuration on page 94
F800 and FAS900: Single-fabric single-controller configuration on page 96
F800 and FAS900: Direct-attached configurations on page 97
F800 and FAS900: Dual-fabric active/active configuration, one dual-ported FC target HBA
The single_image cfmode requires only a single adapter per controller to protect against fabric and
controller failures. In the case of a cluster failover, the identity of the FC target HBAs remains unchanged.
Figure 60: F800 and FAS900 dual-fabric active/active configuration
Attribute Value
Fully redundant Yes
FC ports or adapters One dual-ported FC target HBA per controller
F800 and FAS900: Dual-fabric active/active configuration, two dual-ported FC target HBAs
Note: The port numbers used (for example, 7a, 7b, 9a, and 9b) are examples. The actual port numbers
might vary, depending on the expansion slot in which the FC target HBAs are installed.
Attribute Value
Fully redundant Yes, when the host is dually attached to two physically separate
fabrics
FC ports or adapters Two dual-ported FC target HBAs per controller
Supported cfmodes Single_image, partner, standby, and mixed cfmodes
Multipathing required Yes, to be fully redundant.
F800 and FAS900: Dual-fabric active/active configuration, one dual-ported FC target HBA
Attribute Value
Fully redundant Yes, when the host has multipathing software properly
configured
FC ports or adapters One dual-ported FC target HBA per controller
F800 and FAS900: Dual-fabric active/active configuration, four dual-ported FC target HBAs
This configuration is used in combination with larger, more complex fabrics where the eight connections
between the controller and the fabric are not attached to a single FC switch.
Attribute Value
Fully redundant Yes
FC ports or adapters Four dual-ported FC target HBAs per controller
Supported cfmodes Single_image, partner, standby, and mixed cfmodes
Multipathing required Yes, to be fully redundant.
F800 and FAS900: Single-fabric active/active configuration

The following diagram shows the minimum FC cabling configuration for connecting an active/active
configuration to a single fabric.
Note: Single_image cfmode is highly recommended when there is only one FC target connection
per controller. The following topology is only supported in single_image cfmode if LUNs are being
served by one controller.
In partner cfmode, if LUNs are being served from both controllers, two connections per controller
are required. It is important that the a port and the corresponding b port on the partner controller are
attached to allow access to the LUNs in a failover situation.
Figure 64: F800 and FAS900 single-fabric active/active configuration
Attribute Value
FC ports or adapters Two to 16 connections to the fabric, depending on the number of
target HBAs connected to the storage system
F800 and FAS900: Single-fabric single-controller configuration

Figure 65: F800 and FAS900 single-fabric single-controller configuration
Attribute Value
FC ports or adapters One to four connections to the fabric, depending on the number
of target HBAs installed in each controller
F800 and FAS900: Direct-attached configurations

Figure 66: F800, FAS900 series, or NearStore direct-attached single-controller configurations
Attribute Value
Type of fabric None
Fibre Channel zoning

A FC zone is a subset of the fabric that consists of a group of FC ports or nodes that can communicate
with each other. You must contain the nodes within the same zone to allow communication.
Reasons for zoning

• Zoning reduces or eliminates cross talk between initiator HBAs. This occurs even in small
environments and is one of the best arguments for implementing zoning. The logical fabric subsets
created by zoning eliminate cross-talk problems.
• Zoning reduces the number of available paths to a particular FC port and reduces the number of
paths between a host and a particular LUN that is visible. For example, some host OS multipathing
solutions have a limit on the number of paths they can manage. Zoning can reduce the number of
paths that an OS multipathing driver sees. If a host does not have a multipathing solution 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 which 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.
Next topics
Port zoning on page 98
World Wide Name based zoning on page 98
Port zoning
Port zoning, also referred to as hard zoning, specifies the unique fabric N_port IDs of the ports to be
included 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 using WWN
spoofing. However, if someone has physical access to the switch, replacing a cable can allow access.
• In some environments, port zoning is easier to create and manage because you only work with the
switch or switch domain and port number.
World Wide Name based zoning

World Wide Name based zoning (WWN) specifies the WWN of the members to be included within
the zone. Depending on the switch vendor, either World Wide Node Name or World Wide Port Names
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 physically
connected to the fabric. You can move a cable from one port to another without reconfiguring zones.
Individual zones
The following figure shows the standard zoning configuration for a simple environment where each
host is shown in a separate zone. The zones overlap because the storage ports are included in each zone
to allow each host to access 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 not
present. You can define each zone to contain a single switch port for the host and switch ports one
through 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 a supported configuration has two fabrics. The second
fabric has the same zone structure.
Figure 67: Hosts in individual zones
Single-fabric zoning
The following figure shows how zoning 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 not protected from a possible controller failure.
In the following figure, Host1 and Host2 do not have multipathing software and are zoned so that there
is only one path to each LUN (Zone 1). Therefore, Zone 1 contains only one of the two storage ports.
Even though the host has only one HBA, both storage ports are included in Zone 2. The LUNs are
visible through two different paths, one going from the host FC port to storage port 0 and the other
going from host FC port to storage port 1.
Because this figure contains only a single fabric, it is not fully redundant. However, as shown, Host3
and Host4 have multipathing software that protects against a possible controller failure. They are zoned
so that a path to the LUNs is available through each of the controllers.
Figure 68: Single-fabric zoning
Dual-fabric active/active configuration zoning

The following figure shows how zoning separates hosts in a topology to eliminate HBA cross talk.
Zoning can also prevent a host from accessing LUNs from a storage system in a different zone.
The following figure shows a configuration where Host1 accesses LUNs from storage system 1 and
Host2 accesses LUNs from storage system 2. Each storage system is an active/active configuration and
both are fully redundant.
Multiple FAS270c storage systems are shown in this figure, but they are not necessary for redundancy.
Figure 69: Dual-fabric zoning

Configuration limits | 103
Configuration limits
Configuration limits are available for iSCSI and FC topologies. In some cases, limits might be
theoretically higher, but these limits are tested and supported.
Next topics
Configuration limit parameters and definitions for FC and iSCSI on page 103
Host operating system configuration limits for iSCSI and FC on page 104
Configuration limits for single-controller FAS6000 series, FAS30xx series, and FAS31xx series
storage systems on page 105
Configuration limits for active/active FAS6000 series, FAS30xx series, and FAS31xx series storage
systems on page 107
Configuration limits for FAS2020 and FAS2050 systems on page 109
Configuration limits for FAS2020A and FAS2050A systems on page 110
Configuration limits for single-controller FAS270, F800, FAS900 series, V-Series, and R200
systems on page 111
Configuration limits for active/active FAS270, F800, and FAS900 series systems on page 113
Configuration limit parameters and definitions for FC and

iSCSI
The following tables provide parameters and definitions for FC and iSCSI configuration limits.
Parameter Definition
Visible target ports per host The maximum number of target iSCSI Ethernet ports that a host can see or
(iSCSI) access on iSCSI attached controllers.
Visible target ports per host The maximum number of FC adapters that a host can see or access on the
(FC) attached Fibre Channel controllers.
LUNs per host The maximum number of LUNs that you can map from the controllers to a
single host.
Paths per LUN The maximum number of accessible paths that a host has to a LUN.
Maximum LUN size The maximum size of an individual LUN on the respective operating system.
LUNs per controller The maximum number of LUNs that you can configure per controller, including
cloned LUNs and LUNs contained within cloned volumes. LUNs contained in
Snapshot copies do not count in this limit and there is no limit on the number
of LUNs that can be contained within Snapshot copies.
Parameter Definition
LUNs per volume The maximum number of LUNs that you can configure within a single volume.
LUNs contained in Snapshot copies do not count in this limit and there is no
limit on the number of LUNs that can be contained within Snapshot copies.
FC port fan-in The maximum number of hosts that can connect to a single FC port on a
controller. Connecting the maximum number of hosts is generally not
recommended and you need to tune the FC queue depths on the host to achieve
this maximum value.
FC port fan-out The number of LUNs mapped to a host through a FC target port on a controller.
Hosts per controller (iSCSI) The recommended maximum number of iSCSI hosts that you can connect to a
single controller. The general formula to calculate this is as follows: Maximum
hosts = 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 recommended and you need to
tune the FC queue depths on the host to achieve this maximum value.
igroups per controller The maximum number of initiator groups that you can configure per controller.
Number of 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.
Number of LUN mappings per The maximum number of LUN mappings per controller. For example, a LUN
controller mapped to two igroups counts as two mappings.
Length of LUN path name The maximum number of characters in a full LUN name. For example,
/vol/abc/def has 12 characters.
LUN size The maximum capacity of an individual LUN on a controller.
FC queue depth available per The usable queue depth capacity of each FC target port.
port
The older X1028 HBA has a maximum queue depth of 491 and the X1033A
HBA has a maximum queue depth of 1966.
FC target ports per controller The maximum number of supported FC target ports per controller. FC initiator
ports used for back-end disk connections, for example, connections to disk
shelves, are not included in this number.
Related information
Technical Report: NetApp Storage Controllers and Fibre Channel Queue Depth
Host operating system configuration limits for iSCSI and FC

The following table shows host-based configuration limits for Fibre Channel and iSCSI for their
respective host operating systems.
Note: The following configuration limits represent the maximum values that have been tested. Do
not use these limits as sizing guidelines.
Parameter Operating system
Windows Linux HP-UX Solaris AIX VMware

Visible target ports per 16 16 16 16 16 16
host
LUNs per host 128 512 512 128
64 2.x=128
(Windows
3.x=256
2000)
128
(Windows
2003)
Paths per LUN 8 4 8 more 16 16

2.x=4
possible, but
pvlinks only 3.x=8
utilizes 8
2 TB 2 TB 2 TB
Max LUN size • 2 TB • 1023 GB • 1 TB
Note: The maximum • 12 TB • 12 TB • 12 TB
LUN sizes are due to (Windows with with
restrictions at the 2003 or Solaris AIX
operating system later 9, 5.2ML7
level, not the storage VxVM, or later
system level. EFI, and and AIX
appropriate 5.3ML3
patches or later
Configuration limits for single-controller FAS6000 series,

FAS30xx series, and FAS31xx series storage systems
The following table shows the storage system-based configuration limits for individual system models.
All values are for FC and iSCSI unless noted.
Note: Do not create more LUNs than the available queue depth on the storage system.
Parameter Storage system
FAS3020 FAS3050 FAS3040 and FAS3140 and FAS6030 FAS6070

FAS3070 FAS3170
and FAS6040 and FAS6080
Maximum 1,024 1,024 2,048 2,048 2,048 2,048

number of
LUNs per
controller
Maximum 1,024 1,024 2,048 2,048 2,048 2,048
number of
LUNs per
volume
Maximum 64 64 64 64 64 64
port fan-in
Maximum 256 256 256 256 256 256
connected
hosts per
storage
controller
(FC)
Maximum 64 128 256 256 256 512
connected
hosts per
controller
(iSCSI)
Maximum 256 256 256 256 256 256
number of
igroups per
controller
Maximum 256 256 256 256 256 256
number of
initiators per
igroup
Maximum 4,096 4,096 4,096 4,096 8,192 8,192
number of
LUN
mappings per
controller
Maximum 255 255 255 255 255 255
length of LUN
path name
Maximum 12 TB 12 TB 12 TB 12 TB 12 TB 12 TB
LUN size
Maximum FC 1,720 1,720 1,720 1,720 1,720 1,720
queue depth
available per
port
Maximum FC 4 4 8 12 12 12
target ports
per controller
Related information
Configuration limits for active/active FAS6000 series, FAS30xx

series, and FAS31xx series storage systems
FAS3020 in FAS3050 in FAS3040A FAS3140A FAS6030 in FAS6070 in

an an and and an an
active/active active/active FAS3070A FAS3170A active/active active/active
configuration configuration configuration configuration
and FAS6040 and FAS6080
in an in an
active/active active/active
configuration configuration
Maximum 1,024 1,024 2,048 2,048 2,048 2,048

number of
LUNs per
active/active
configuration
Maximum 1,024 1,024 2,048 2,048 2,048 2,048

number of
LUNs per
volume
Maximum FC 64 64 64 64 64 64
port fan-in
Maximum 256 256 256 256 256 256
connected
hosts per
active/active
configuration
(FC)
Maximum 128 256 512 512 512 1,024
connected
hosts per
active/active
configuration
(iSCSI)
Maximum 256 256 256 256 256 256
number of
igroups per
active/active
configuration
Maximum 256 256 256 256 256 256
number of
initiators per
igroup
Maximum 4,096 4,096 4,096 4,096 8,192 8,192
number of
LUN
mappings per
active/active
configuration
Maximum 255 255 255 255 255 255
length of LUN
path name
Maximum 12 TB 12 TB 12 TB 12 TB 12 TB 12 TB
LUN size
Maximum FC 1,720 1,720 1,720 1,720 1,720 1,720
queue depth
available per
port
Maximum FC 8 8 16 24 24 24
target ports
per
active/active
configuration
Related information
Configuration limits for FAS2020 and FAS2050 systems

Parameter Controller
FAS2020 FAS2050
Maximum number of LUNs per 1,024 1,024
controller
volume
Maximum FC port fan-in 16 16
Maximum connected hosts per 24 32
controller (FC)
controller (iSCSI)
Maximum number of igroups per 256 256
controller
Maximum number of initiators per 256 256
igroup
Maximum number of LUN mappings 4,096 4,096
per controller
Maximum length of LUN path name 255 255
Parameter Controller
Maximum LUN size 12 TB 12 TB

Maximum FC queue depth available 737 737
per port
Maximum FC target ports per 2 2
controller
Related information
Configuration limits for FAS2020A and FAS2050A systems

FAS2020A FAS2050A
active/active storage system
volume
Maximum FC port fan-in 16 16
active/active configuration (FC)
active/active configuration (iSCSI)
Maximum number of igroups per 256 256
Maximum number of initiators per 256 256
igroup
Maximum number of LUN mappings 4,096 4,096
per active/active storage system
Maximum length of LUN path name 255 255

Maximum LUN size 12 TB 12 TB
Maximum FC queue depth available 737 737
per port
Maximum FC target ports per 4 4
Related information
Configuration limits for single-controller FAS270, F800, FAS900

series, V-Series, and R200 systems
FAS270 F825 F880 R200

FAS920 FAS940 FAS960 FAS980
GF920 GF940 GF960 GF980
Maximum 1,024 1,024 2,048 2,048 2,048 2,048 2,048 2,048

number of
LUNS per
controller
Maximum 1,024 1,024 2,048 2,048 2,048 2,048 2,048 2,048
Number of
LUNs per
volume
Maximum 16 16 64 64 64 64 64 64
FC port
fan-in
Maximum 16 64 256 256 256 256 256 256

connected
hosts per
controller
(FC)
Maximum 8 8 8 32 48 64 72 64
connected
hosts per
controller
(iSCSI)
Maximum 256 256 256 256 256 256 256 256
number of
igroups
per
controller
Maximum 256 256 256 256 256 256 256 256
number of
initiators
per igroup
Maximum 4,096 4,096 4,096 8,192 8,192 8,192 8,192 8,192
number of
LUN
mappings
per
controller
Maximum 255 255 255 255 255 255 255 255
length of
LUN path
name
Maximum 6 TB 2 TB 6 TB 4 TB 6 TB 12 TB 12 TB 12 TB
LUN size
Maximum 491 491 or 491 or 1,966 1,966 1,966 1,966 491
FC queue 1,966 1,966
depth
available
per port
Maximum 1 4 4 4 4 4 8 4
FC target
ports per
controller
Related information
Configuration limits for active/active FAS270, F800, and

FAS900 series systems
FAS270c F825C F880

FAS920C FAS940C FAS960C FAS980C
GF920C GF940C GF960C GF980C
Maximum 1,024 1,024 2,048 2,048 2,048 2,048 2,048

number of
LUNS per
active/active
storage
system
Maximum 1,024 1,024 2,048 2,048 2,048 2,048 2,048
Number of
LUNs per
volume
Maximum 16 16 64 64 64 64 64
FC port
fan-in
Maximum 16 64 256 256 256 256 256
connected
hosts per
active/active
storage
system (FC)
Maximum 32 32 32 64 96 128 144

connected
hosts per
active/active
storage
system
(iSCSI)
Maximum 256 256 256 256 256 256 256
number of
igroups per
active/active
storage
system
Maximum 256 256 256 256 256 256 256
number of
initiators per
igroup
Maximum 4,096 4,096 8,192 8,192 8,192 8,192 8,192
number of
LUN
mappings
per
active/active
storage
system
Maximum 255 255 255 255 255 255 255
length of
LUN path
name
Maximum 6 TB 2 TB 6 TB 4 TB 6 TB 12 TB 12 TB
LUN size
Maximum 491 491 or 1,966 491 or 1,966 1,966 1,966 1,966 1,966
FC queue
depth
available per
port
Maximum 2 16 16 16 16 16 16
FC target
ports per
active/active
storage
system
Related information

FC Iscsi Config Guide

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

FC Iscsi Config Guide

Transféré par

Droits d'auteur :

Formats disponibles

iSCSI and Fibre Channel Configuration Guide

FAS6000 series: Single-fabric single-controller

FAS3140 and FAS3170: Direct-attached active/active

DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

About this guide

Accessing Data ONTAP man pages

Types of information Man page section

File formats and conventions 5

System management and services 8

1. View man pages in the following ways:

General storage system terminology

Active/active configuration terminology

Storage hardware terminology

FilerView as an alternative to the command-line interface

Command, keyboard, and typographic conventions

Convention Type of information

Italic font Words or characters that require special attention.

Dual-network active/active configuration in an iSCSI SAN

Figure 1: iSCSI dual network active/active configuration

Single-network active/active configuration in an iSCSI SAN

Figure 2: iSCSI single network active/active configuration

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, if a host has multiple paths to a LUN

Type of configuration Active/active configuration

Direct-attached single controller configurations in an iSCSI

Figure 3: iSCSI direct attached-single controller configurations

Reasons for implementing VLANs

Fibre Channel topologies

Fibre Channel supported hop count

Switch supplier Supported hop count

Fibre Channel switch configuration best practices

The cfmode setting

FAS6000 series supported topologies

FAS6000 series: Dual-fabric active/active configuration, one port of a 4-Gb FC target

FAS6000 series target port configuration recommendations

Number of target ports Ports

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

FAS6000 series: Dual-fabric active/active configuration, two onboard FC ports

Figure 4: FAS6000 series dual-fabric active/active configuration

FAS6000 series: Dual-fabric active/active configuration, four onboard FC

Figure 5: FAS6000 series dual-fabric active/active configuration

FAS6000 series: Dual-fabric active/active configuration, eight onboard FC

Figure 6: FAS6000 series dual-fabric active/active configuration

FAS6000 series: Single-fabric active/active configuration, two onboard FC

Figure 7: FAS6000 series single-fabric active/active configuration

Type of configuration Active/active configuration

FAS6000 series: Single-fabric active/active configuration, one onboard FC

Figure 8: FAS6000 series single-fabric active/active configuration

FAS6000 series: Single-fabric single-controller configuration, one to eight

Figure 9: FAS6000 series single-fabric single-controller configuration

FAS6000 series: Dual-fabric active/active configuration, two ports of a 4-Gb

Figure 10: FAS6000 series dual-fabric active/active configuration

FAS6000 series: Dual-fabric active/active configuration, one port of a 4-Gb

Figure 11: FAS6000 series dual-fabric active/active configuration

FAS6000 series: Dual-fabric active/active configuration, two 4-Gb FC target

Figure 12: FAS6000 series dual-fabric active/active configuration