network appliance fibre channel configuration guide 2006-7.pdfnetapp figure 1: dual fabric – two...

Network Appliance

Fibre Channel Configuration Guide

Version 1.5 July 2006

Feedback: dl-fcp-config-feedback

Network Appliance, Inc. 2

Table of Contents

1. INTRODUCTION ....................................................................................................... 4

2. SUPPORTED CONFIGURATIONS........................................................................... 4

3. SUPPORTED TOPOLOGIES.................................................................................... 4

3.1. Topology Definition................................................................................................................ 4

3.2. Cascade, Mesh, or Core-Edge Fabrics and Hop Counts ...................................................... 4

3.3. Heterogeneous SAN Storage................................................................................................. 5

3.4. Highly Available vs. Non-Highly Available Storage Systems............................................... 5

3.5. Multiple Fabrics...................................................................................................................... 5

3.6. FAS6000 Supported Topologies............................................................................................ 6 Figure 1: Dual Fabric – Two 4Gb FC Ports per Storage Controller single_image Topology........ 7 Figure 2: Dual Fabric – Two 4Gb FC Ports per Controller with 6 Disk Shelf Connections .......... 8 Figure 3: Dual Fabric – One 4Gb FC Port Per Controller single_image Topology...................... 9 Figure 4: Dual Fabric – Four 4Gb FC Ports per Controller single_image/standby Topology ..... 10 Figure 5: Dual Fabric – Four 4Gb FC Ports per Controller with 4 Back-end Disk Connections . 11 Figure 6: Single Fabric – Two 4Gb FC Ports per Storage Controller Topology......................... 12 Figure 7: Single Fabric – One to Eight 4Gb FC Ports on a Single Storage Controller Topology13 Figure 8: Direct Attach – One 4Gb FC Target Port per Controller single_image Topology ....... 14 Figure 9: Dual Fabric – Two Onboard 2Gb FC Ports per Storage Controller Topology............. 15 Figure 10: Dual Fabric – Two 2Gb FC Ports per Controller with 6 Back-end Disk Connections 16 Figure 11: Dual Fabric – Four 2Gb FC Ports per Controller single_image/standby Topology... 17 Figure 12: Single Fabric – Two Onboard 2Gb FC Ports per Storage Controller Topology ........ 18 Figure 13: Single Fabric – One to Eight 2Gb FC Ports on a Single Storage Controller............. 19 Figure 14: Direct Attach – One 2Gb FC Target Port per Controller single_image Topology ..... 20 Figure 15: Direct Attach – 4Gb or 2Gb FC Single Storage Controller Topology ....................... 21

3.7. FAS3000 Supported Topologies.......................................................................................... 22 Figure 16: Dual Fabric – Two 4Gb FC Ports per Storage Controller single_image Topology.... 23 Figure 17: Dual Fabric – Two 4Gb FC Ports per Controller with 4 Back-end Disk Connections 24 Figure 18: Dual Fabric – Two 4Gb FC Ports per Controller with 6 Back-end Disk Connections 25 Figure 19: Dual Fabric – Four 4Gb FC Ports per Storage Controller single_image Topology... 26 Figure 20: Dual Fabric – Four 4Gb FC Ports per Controller single_image/standby Topology ... 27 Figure 21: Dual Fabric – One 4Gb FC Port Per Controller single_image Topology .................. 28 Figure 22: Direct Attach – One 4Gb FC Target Port per Controller single_image Topology ..... 29 Figure 23: Dual Fabric – Two Onboard 2Gb FC Ports per Storage Controller Topology........... 30 Figure 24: Dual Fabric – Two 2Gb FC Ports per Controller with 4 Back-end Disk Connections 31 Figure 25: Dual Fabric – Four Onboard 2Gb FC Ports per Storage Controller Topology .......... 32 Figure 26: Single Fabric – Two Onboard 2Gb FC Ports per Storage Controller Topology ........ 33 Figure 27: Single Fabric – One to Four Onboard 2Gb FC ports on a Single Storage Controller 34

Figure 28: Direct Attach – 4Gb or 2Gb FC Single Storage Controller Topology ....................... 35 Figure 29: Dual Fabric – One Onboard 2Gb FC Port Per Controller single_image Topology.... 36 Figure 30: Dual Fabric – Two Onboard 2Gb FC Ports Per Controller single_image Topology .. 37 Figure 31: Dual Fabric – Four Onboard 2Gb FC Ports Per Controller single_image Topology . 38 Figure 32: Dual Fabric – Two Onboard 2Gb FC Ports With 6 Back-End Disk Connections ...... 39 Figure 33: Direct Attach – One Onboard 2Gb FC Port per Controller single_image Topology.. 40

3.8. FAS270 and FAS270C Supported Topologies .................................................................... 41 Figure 34: FAS270C – Dual Fabric Connect Topology ............................................................ 41 Figure 35: FAS270C – Single Fabric Connect Topology ......................................................... 42 Figure 36: FAS270 and FAS270C – Direct Attach Topology.................................................... 43

3.9. F800/FAS900 and Nearstore Supported Topologies........................................................... 44 Figure 37: Dual Fabric – One Dual Ported FC Target Card per Controller ............................... 44 Figure 38: Dual Fabric – Two Dual Ported FC Target Cards per Controller.............................. 45 Figure 39: Dual Fabric – Single Dual Ported FC Target Card per Controller ............................ 46 Figure 40: Dual Fabric Connect – Four Dual Ported FC Target Cards Topology...................... 47 Figure 41: Single Fabric –High Availability Storage System Connect Topology ....................... 48 Figure 42: Single Fabric – Single Storage Controller Connect Topology.................................. 49 Figure 43: Direct Attach – Single Storage Controller Topology................................................ 50

4. CONFIGURATION LIMITS...................................................................................... 51 Table 1: Host-based limits in conjunction with NetApp Storage Controllers.............................. 51 Table 2: Limits of Non-HA FAS270, F800, FAS900, V-Series, and R200 Storage Systems ..... 52 Table 3: Limits of Non-HA FAS6000, FAS3000, and V-Series Storage Systems ..................... 53 Table 4: Limits of HA FAS270, F800, and FAS900 Storage Systems...................................... 55 Table 5: Limits of HA FAS6000, FAS3000, and V-Series Storage Systems............................. 56

5. CLUSTER FAILOVER MODE – CFMODE.............................................................. 58

5.1. CFMODE Types .................................................................................................................... 58

5.2. CFMODE Recommendations ............................................................................................... 60

6. ZONING................................................................................................................... 60

6.1. Hard and Soft Zoning ........................................................................................................... 60

6.2. Reasons for Zoning.............................................................................................................. 60

6.3. Network Appliance Zoning Recommendations................................................................... 61

6.4. Zoning Diagrams .................................................................................................................. 62 Figure 44: Hosts in Individual Zones....................................................................................... 62 Figure 45: Single Fabric, No Multipathing Zoning.................................................................... 63 Figure 46: Multiple Storage System Zoning............................................................................. 64

1. Introduction This document is intended to help with the understanding and configuration of Network Appliance Fabric Attached Storage Devices (FAS) in Fibre Channel (FC) environments. It explains the various interconnect topologies that are supported and recommended by Network Appliance and covers areas such as fibre channel zoning and cfmode (cluster failover mode) recommendations.

This document is not intended to specify supported configurations in terms of operating systems, switches, HBAs, etc… Compatibility information is available in the Network Appliance fibre channel compatibility matrices at: http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/.

This document is current as of Data ONTAP 7.2.

2. Supported Configurations Network Appliance has detailed compatibility matrices available on the NOW (NetApp On the Web) site with up-to date information on which Operating Systems (OS), FC switches, HBAs, NetApp Storage Systems and Data ONTAP versions are supported. These matrices are updated a minimum of once per month and can be found at the following web address: http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/.

Note: a login is necessary to access the NOW site.

3. Supported Topologies 3.1. Topology Definition

Network Appliance differentiates between three basic SAN topologies which are possible when connecting Network Appliance Storage Appliances and server systems with fibre channel:

• Direct Attached – The servers (or hosts) are directly attached to the NetApp storage controller. On F800 and FAS900 series direct attached topologies are supported only for non-HA storage controllers.

• Single Fabric – The servers are attached to NetApp storage controllers through a single fibre channel fabric. This fabric may consist of multiple fibre channel switches.

• Dual Fabric – Each server is attached to two physically independent fabrics that are connected to the NetApp storage controllers. NOTE: A fabric zoned into two logically independent fabrics does not qualify as a dual fabric connection.

3.2. Cascade, Mesh, or Core-Edge Fabrics and Hop Counts

Network Appliance does not differentiate between the various methods of connecting fibre channel switches into a fabric and supports all the industry accepted options. The maximum supported hop count, or the number of inter-switch links (ISLs) crossed between a particular host and the storage appliance, is limited to three.

3.3. Heterogeneous SAN Storage

Network Appliance supports the use of heterogeneous SANs (in this context a heterogeneous SAN refers to a fabric with storage from multiple vendors), as long as the Network Appliance storage systems are contained in exclusive zones or VSANs. In the case of a tape SAN being used it should be zoned or in a separate VSAN from the disk SAN.

3.4. Highly Available vs. Non-Highly Available Storage Systems

Network Appliance offers storage systems in highly available (HA) and non-HA configurations. These are often referred to as dual controller and single controller (as well as clustered and non-clustered) configurations. For SAN solutions, Network Appliance recommends, but does not require, using HA storage solutions with dual physically independent storage fabrics as the interconnect between the hosts and the storage controllers. This provides redundancy at the networking and storage controller layers which is particularly important since these layers are typically supporting many hosts.

3.5. Multiple Fabrics

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, in the case of the dual fabric configurations it would be even multiples of fabrics, connected to a single storage system. This holds for both active/active (often referred to as HA or dual controller) storage systems and single controller (non-HA) storage configurations.

3.6. FAS6000 Supported Topologies

The Network Appliance FAS6000 storage systems are available in single and dual controller configurations. Each controller is capable or supporting 2Gb OR 4Gb FC target connections. The FAS6000 has 8 onboard 2Gb FC ports per controller and each port may be configured as either an FC target port or a disk shelf storage port. 2Gb FC target connections are supported with the onboard 2Gb FC ports. 4Gb FC target connections are supported with dual port 4Gb FCP target expansion adapter cards. NOTE: Mixed use of 2Gb AND 4Gb FC targets on single or dual controller FAS6000 configurations is NOT supported. All FAS6000 active/active controller FC target topologies are only supported with single_image (and standby in some topologies) cfmodes. The following figures show the supported topologies for connecting to a FAS6000 series storage appliance.

FAS6030

NetApp

FAS6030

NetApp

Figure 1: Dual Fabric – Two 4Gb FC Ports per Storage Controller single_image Topology

This figure shows a dual-fabric attached configuration for the FA6000 storage system where dual-ported 4Gb FCP target-mode cards are used in each storage controller. In the figure the 4Gb Fibre Channel target port numbers (5a and 5b) are examples and, in reality, will vary depending on expansion slot where the fibre channel target cards are installed in the controllers. This configuration is possible only with an active/active storage controller configuration. When properly configured with multi-pathing software dual-attached hosts are fully redundant from the storage perspective because the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). In this topology, the 2Gb onboard FC ports (0a and 0c) are used for back-end disk shelf storage connections. This configuration is supported with the single_image (SSI) cfmode. Refer to the cfmode section of this document for more information regarding cfmodes.

FAS6030

NetApp

FAS6030

NetApp

Figure 2: Dual Fabric – Two 4Gb FC Ports per Controller with 6 Disk Shelf Connections

This figure shows a dual-fabric attached configuration for the FA6000 storage system where dual-ported 4Gb FCP target-mode cards are used in each storage controller and 6 onboard 2Gb FC ports are used for back-end disk shelf connections. From a host side Fibre Channel perspective, this configuration is the same as the previous configuration but demonstrates that as many as all 8 onboard 2Gb FC ports (0a, 0b, 0c, 0d, 0e, 0f, 0g, and 0h) may be used as back-end disk shelf storage connections. Also the 4Gb fibre channel target port numbers (5a and 5b) in the figure are examples and, in reality, will vary depending on expansion slot where the Fibre Channel target cards are installed in the controllers. Again this topology is supported only with the single_image cfmode.

FAS6030

NetApp

FAS6030

NetApp

Figure 3: Dual Fabric – One 4Gb FC Port Per Controller single_image Topology

This figure shows a dual-fabric attached configuration for the FAS6000 storage system where only one port of a dual-ported 4Gb FC target card is used in each storage controller. The 4Gb Fibre Channel target port number (5a) is an example and, in reality, will vary depending on expansion slot where the FC target cards are installed in the controllers. This topology is possible only with an active/active storage controller configuration. When properly configured with multi-pathing software the hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). In this topology, the onboard 2Gb FC ports (0a and 0c) are used for back-end disk shelf connections. This configuration is supported only in single_image cfmode

FAS6030

NetApp

FAS6030

NetApp

Figure 4: Dual Fabric – Four 4Gb FC Ports per Controller single_image/standby Topology

This configuration is shows a dual-fabric attached FAS6000 storage system where two dual-ported 4Gb FC target cards are used in each storage controller. This cabling topology allows for single_image and standby cfmode support. Also in the figure the 4Gb Fibre Channel target port numbers (5a, 5b, 6a, and 6b) are examples and, in reality, will vary depending on expansion slot where the Fibre Channel target cards are installed in the controllers. This configuration is possible only with an active/active storage controller configuration. When properly configured with multi-pathing software, dual attached hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). This configuration is supported with single_image and standby cfmodes .

FAS6030

NetApp

FAS6030

NetApp

Figure 5: Dual Fabric – Four 4Gb FC Ports per Controller with 4 Back-end Disk Connections

This figure is similar to the previous configuration except it shows that multiple onboard 2Gb FC ports may be used for back-end disk shelf connections. This configuration is also supported with single_image and standby cfmodes

FAS6030

NetApp

FAS6030

NetApp

Figure 6: Single Fabric – Two 4Gb FC Ports per Storage Controller Topology

This figure shows an active/active FAS6000 storage system with 4Gb FC target ports attached to a single fabric. The fabric may consist of one or multiple fibre channel switches and, in fact, the storage controller may be attached to multiple switches. The active/active storage system may have anywhere from four to sixteen connections to the fabric. Because of the non-redundant nature of the single fabric, this configuration cannot be considered to be fully redundant. This configuration is supported in single_image, and standby cfmodes. When a host has multiple paths to a single LUN configured on a storage controller, it is necessary for the host to have multi-pathing software installed. Although in this specific topology with two FC target ports per controller single attached hosts would not require multi-pathing software when the controllers are running in standby cfmode. In single_image cfmode a host with a single fibre channel connection may still have multiple logical paths to the LUN if there are multiple connections from the NetApp storage controllers to the fabric. If it is not desired to have multiple paths to the LUNs, see the section on fibre channel zoning to learn how to eliminate the redundant paths.

FAS6030

NetApp

Single Switch/Fabric

Controller5b

Disk Shelves

Host 1 Host 2 Host N

5a 6a 6b

1 – 8 FC Target Connections

Figure 7: Single Fabric – One to Eight 4Gb FC Ports on a Single Storage Controller Topology

This figure shows a single FAS6000 storage controller with one to eight 4Gb FC target ports attached to a single fabric. The fabric may consist of one or multiple fibre channel switches and, in fact, the storage controller may be attached to multiple switches. The storage controller may have anywhere from one to eight connections to the fabric through any or all of the eight possible 4Gb FC target ports for this topology. Because of the non-redundant nature of the single fabric and single NetApp storage controller, none of these variants may be considered fully redundant configurations. When a host has multiple paths to a single LUN, it is necessary for the host to have multi-pathing software installed. In this diagram, assuming there is more than one connection between the storage controller and the fibre channel fabric, all hosts would have multiple paths unless the fabric is zoned to prevent this. A host with a single fibre channel connection may still have multiple logical paths to the LUN if there are multiple connections from the NetApp storage controller to the fabric. If it is not desired to have multiple paths to the LUNs, see the section on fibre channel zoning to learn how to eliminate the redundant paths. A cfmode setting is not applicable for this configuration because the single FAS6000 controller is not clustered.

FAS6030

NetApp

FAS6030

NetApp

Controller 1

Controller 2

Controller 1 Active Shelves

Figure 8: Direct Attach – One 4Gb FC Target Port per Controller single_image Topology

This figure shows a direct attached FC configuration for the FA6000 storage system where one port of a dual-ported 4Gb FC target card is used in each storage controller. The 4Gb fibre channel target port number (5a) is an example and, in reality, will vary depending on expansion slot where the fibre channel target cards are installed in the controllers. The ONTAP fcp adapter mediatype may have to be set to loop on the 4Gb FC target ports for some host direct attach topologies. To determine which host HBAs and operating systems are supported, refer to the compatibility matrices on the NOW site. The host has a dual connection to the FAS6000 and is fully redundant since, the HBA, wiring, storage controller and disks are all redundantly configured. When a host has multiple paths to a single LUN configured on a storage controller, it is necessary for the host to have multi-pathing software installed. This configuration is only supported with single_image cfmodes.

FAS6030

NetApp

FAS6030

NetApp

Figure 9: Dual Fabric – Two Onboard 2Gb FC Ports per Storage Controller Topology

This figure shows a dual-fabric attached configuration for the FAS6000 storage system where two onboard 2Gb fibre channel target ports are used on each storage controller. This topology is possible only with a HA storage controller configuration. When properly configured with multi-pathing software dual-attached hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). In this configuration two 2Gb onboard FC ports (0a and 0c) are used for back-end disk shelf storage connections. This configuration is supported with single_image cfmode. Refer to the cfmode section of this document for more information regarding cfmodes.

FAS6030

NetApp

FAS6030

NetApp

Figure 10: Dual Fabric – Two 2Gb FC Ports per Controller with 6 Back-end Disk Connections

From a host side fibre channel perspective, this configuration is the same as the previous configuration but demonstrates how all the onboard 2Gb Fibre Channel ports may be used as FC targets or for additional back-end disk shelf storage connections. Again this topology is supported with single_image cfmode.

FAS6030

NetApp

FAS6030

NetApp

This configuration is shows a dual-fabric attached FAS6000 storage system where four onboard 2Gb FC target ports are used in each storage controller. This cabling topology allows for single_image and standby cfmode support. Also in the figure the 2Gb Fibre Channel target port numbers (0a, 0b, 0c, and 0d) are examples and, in reality, will vary depending on expansion slot where the Fibre Channel target cards are installed in the controllers. This configuration is possible only with an active/active storage controller configuration. When properly configured with multi-pathing software, dual attached hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). This configuration is supported with single_image and standby cfmodes .

FAS6030

NetApp

FAS6030

NetApp

Figure 12: Single Fabric – Two Onboard 2Gb FC Ports per Storage Controller Topology

This figure shows an active/active FAS6000 storage system with 2Gb FC target ports attached to a single fabric. The fabric may consist of one or multiple fibre channel switches and, in fact, the storage controller may be attached to multiple switches. The active/active storage system may have anywhere from four to sixteen connections to the fabric. Because of the non-redundant nature of the single fabric, this configuration cannot be considered to be fully redundant. This configuration is supported in single_image, and standby cfmodes. When a host has multiple paths to a single LUN configured on a storage controller, it is necessary for the host to have multi-pathing software installed. Although in this specific topology with two FC target ports per controller single attached hosts would not require multi-pathing software when the controllers are running in standby cfmode. In single_image cfmode a host with a single fibre channel connection may still have multiple logical paths to the LUN if there are multiple connections from the NetApp storage controllers to the fabric. If it is not desired to have multiple paths to the LUNs, see the section on fibre channel zoning to learn how to eliminate the redundant paths.

FAS6030

NetApp

Single Switch/Fabric

Controller0e

Disk Shelves

0d 0f 0g

1 – 8 FC Target Connections

Figure 13: Single Fabric – One to Eight 2Gb FC Ports on a Single Storage Controller

This figure shows a single FAS6000 storage controller with one to eight 2Gb FC target ports attached to a single fabric. The fabric may consist of one or multiple fibre channel switches and, in fact, the storage controller may be attached to multiple switches. The storage controller may have anywhere from one to eight connections to the fabric through any or all of the eight possible 2Gb FC target ports for this topology. Because of the non-redundant nature of the single fabric and single NetApp storage controller, none of these variants may be considered fully redundant configurations. When a host has multiple paths to a single LUN, it is necessary for the host to have multi-pathing software installed. In this diagram, assuming there is more than one connection between the storage controller and the fibre channel fabric, all hosts would have multiple paths unless the fabric is zoned to prevent this. A host with a single fibre channel connection may still have multiple logical paths to the LUN if there are multiple connections from the NetApp storage controller to the fabric. If it is not desired to have multiple paths to the LUNs, see the section on fibre channel zoning to learn how to eliminate the redundant paths. A cfmode setting is not applicable for this configuration because the single FAS6000 controller is not clustered.

FAS6030

NetApp

FAS6030

NetApp

Controller 1

Controller 2

This figure shows a direct attached FC configuration for the FA6000 storage system where one onboard 2Gb FC target port is used in each storage controller. The 2Gb fibre channel target port number (0b) is an example and, in reality, will vary depending on expansion slot where the fibre channel target cards are installed in the controllers. The ONTAP fcp adapter mediatype may have to be set to loop on the 4Gb FC target ports for some host direct attach topologies. To determine which host HBAs and operating systems are supported, refer to the compatibility matrices on the NOW site. The host has a dual connection to the FAS6000 and is fully redundant since, the HBA, wiring, storage controller and disks are all redundantly configured. When a host has multiple paths to a single LUN configured on a storage controller, it is necessary for the host to have multi-pathing software installed. This configuration is only supported with single_image cfmodes.

FAS6030

NetApp

FAS6030

NetApp

Figure 15: Direct Attach – 4Gb or 2Gb FC Single Storage Controller Topology

This figure shows the direct-attached configurations for single FAS6000 storage controllers. To determine which host HBAs and operating systems are supported, refer to the compatibility matrices on the NOW site. Because of the non-redundant components of the single fabric and single FAS6000 storage controller, none of these variants may be considered to be fully redundant. When a host has multiple paths to a single LUN configured on a storage controller (as with Host 2 and Host 3 in the configuration on the right), it is necessary for the host to have multi-pathing software installed. For multiple-host configurations, the hosts may be heterogeneous (e.g. Windows and UNIX). A cfmode setting is not applicable for this configuration because the single FAS6000 controller is not clustered.

3.7. FAS3000 Supported Topologies

The Network Appliance FAS3000 storage systems are available in single and dual controller configurations. Each controller is capable or supporting 2Gb OR 4Gb FC target connections. The FAS3000 has 4 onboard 2Gb FC ports per controller and each port may be configured as either an FC target port or a back-end storage port. 2Gb FC target connections are supported with the onboard 2Gb FC ports. 4Gb FC target connections are supported with dual port 4Gb FCP target expansion adapter cards. NOTE: Mixed use of 2Gb AND 4Gb FC targets on single or dual controller FAS3000 configurations is NOT supported. The 4Gb target topologies are only supported with single_image (and standby in some topologies) cfmodes. The following figures show the supported topologies for connecting to a FAS3000 series storage appliance.

Switch/Fabric 1

Host 1

Controller 12a 2b

Controller 2

Controller 1 Active Shelf (s)

Controller 2 Active Shelf(s)

Switch/Fabric 2

2b2a 0c0a

Host 2 Host N

Figure 16: Dual Fabric – Two 4Gb FC Ports per Storage Controller single_image Topology

This figure shows a dual-fabric attached configuration for the FAS3000 storage system where dual-ported 4Gb fibre channel target cards are used in each storage controller. In the figure the 4Gb fibre channel target port numbers (2a and 2b) are examples and, in reality, will vary depending on expansion slot where the fibre channel target cards are installed in the controllers. This configuration is possible only with an HA storage controller configuration. When properly configured with multi-pathing software dual-attached hosts are fully redundant from the storage perspective because the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). In this topology, the 2Gb onboard FC ports (0a and 0c) are used for back-end disk shelf storage connections. This configuration is supported with the single_image (SSI) cfmode. Refer to the cfmode section of this document for more information regarding cfmodes.

LUNs LUNs

Controller 1

Controller 2

Switch/Fabric 2

Switch/Fabric 1

From a host side fibre channel perspective, this configuration is the same as the previous configuration but demonstrates how all the onboard 2Gb FC ports (0a, 0b, 0c, and 0d) may be used as back-end disk shelf storage connections. Also the 4Gb fibre channel target port numbers (2a and 2b) in the figure are examples and, in reality, will vary depending on expansion slot where the fibre channel target cards are installed in the controllers. Again this topology is supported only with the single_image cfmode.

Switch/Fabric 1

LUNs LUNs

Controller 1

Controller 2

Switch/Fabric 2

1b1a2a 2b

From a host side Fibre Channel perspective, this configuration is the same as the configurations in figures 4 and 5 but demonstrates how all the onboard 2Gb FC ports may be used as back-end storage connections along with expansion Fibre Channel disk shelf storage adapters. In the figure the 4Gb Fibre Channel target port numbers (1a and 1b) as well as the expansion Fibre Channel disk shelf storage adapters (2a and 2b) are examples and, in reality, will vary depending on expansion slot where the fibre channel target cards are installed in the controllers. Again this topology is only supported with single_image cfmode.

Switch/Fabric 1

Host 1

Controller 1 2b 4b

Controller 2

Switch/Fabric 2

2a 4b2b

Host 2 Host N

Figure 19: Dual Fabric – Four 4Gb FC Ports per Storage Controller single_image Topology

This figure shows a dual-fabric attached configuration for the FAS3000 storage appliance where two dual-ported 4Gb FC target cards are used in each storage controller. In the figure the 4Gb fibre channel target port numbers (2a, 2b, 4a, and 4b) are examples and, in reality, will vary depending on expansion slot where the fibre channel target cards are installed in the controllers. This configuration is possible only with a HA storage controller configuration. When properly configured with multi-pathing software, the hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). This configuration is supported in single_image (SSI) cfmode only. Note: This topology may appear similar to a FAS3000 2Gb FC target topology with standby mode support but there are significant differences in the FC target port cabling of this configuration.

Switch/Fabric 1

Host 1

Controller 1 4a 4b

Controller 2

Switch/Fabric 2

2a 4b4a

Host 2 Host N

This configuration is similar to the previous topology with a dual-fabric attached FAS3000 storage system where two dual-ported 4Gb FC target cards are used in each storage controller except the FC target cabling is different. This cabling topology allows for standby (as well as single_image) cfmode support. Also in the figure the 4Gb fibre channel target port numbers (2a, 2b, 4a, and 4b) are examples and, in reality, will vary depending on expansion slot where the fibre channel target cards are installed in the controllers. This configuration is possible only with a HA storage controller configuration. When properly configured with multi-pathing software, dual attached hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). This configuration is supported with single_image and standby cfmodes .

Switch /Fabric 1

LUNs LUNs

Controller 12a

Controller 2

Switch/Fabric 2

Figure 21: Dual Fabric – One 4Gb FC Port Per Controller single_image Topology

This figure shows a dual-fabric attached configuration for the FAS3000 storage system where only one port of a dual-ported 4Gb FC target card is used in each storage controller. The 4Gb fibre channel target port number (2a) is an example and, in reality, will vary depending on expansion slot where the fibre channel target cards are installed in the controllers. This topology is possible only with a HA storage controller configuration. When properly configured with multi-pathing software the hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). In this topology, the onboard 2Gb FC ports (0a and 0c) are used for back-end disk shelf connections. This configuration is supported only in single_image cfmode.

LUNs LUNs

Controller 12a

Controller 2

This figure shows a direct attached FC configuration for the FAS3000 storage system where one port of a dual-ported 4Gb FC target card is used in each storage controller. The 4Gb fibre channel target port number (2a) is an example and, in reality, will vary depending on expansion slot where the fibre channel target cards are installed in the controllers. The ONTAP fcp adapter mediatype may have to be set to loop on the 4Gb FC target ports for some host direct attach topologies. To determine which host HBAs and operating systems are supported, refer to the compatibility matrices on the NOW site. The host has a dual connection to the FAS3000 and is fully redundant since, the HBA, wiring, storage controller and disks are all redundantly configured. When a host has multiple paths to a single LUN configured on a storage controller, it is necessary for the host to have multi-pathing software installed. This configuration is only supported with single_image cfmodes.

Switch/Fabric 1

LUNs LUNs

Controller 10c 0d

Controller 2

Switch/Fabric 2

Figure 23: Dual Fabric – Two Onboard 2Gb FC Ports per Storage Controller Topology

This figure shows a dual-fabric attached configuration for the FAS3000 storage system where two onboard 2Gb fibre channel target ports are used on each storage controller. This topology is possible only with a HA storage controller configuration. When properly configured with multi-pathing software dual-attached hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). In this configuration the remaining 2Gb onboard FC ports (0a and 0b) are used for back-end disk shelf storage connections. This configuration is supported with partner and single_image cfmodes. Refer to the cfmode section of this document for more information regarding cfmodes.

Switch/Fabric 1

LUNs LUNs

Controller 10c 0d

Controller 2

Switch/Fabric 2

From a host side fibre channel perspective, this configuration is the same as the previous configuration but demonstrates how expansion Fibre Channel adapter cards may be added for additional back-end disk shelf storage connections. Again this topology is supported with partner and single_image cfmodes.

Switch/Fabric 1

Host 1

Controller 1 0c 0d

Controller 2

Switch/Fabric 2

0a 0d0c

Host 2 Host N

Figure 25: Dual Fabric – Four Onboard 2Gb FC Ports per Storage Controller Topology

This figure shows a dual-fabric attached topology for the FAS3000 storage system where four onboard 2Gb fibre channel target ports are used on each storage controller. This topology is possible only with a HA storage controller configuration. When properly configured with multi-pathing software, the hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). This configuration is supported in single_image, standby, and partner cfmodes.

Switch/Fabric 1

Controller 10c 0d

Controller 2

Figure 26: Single Fabric – Two Onboard 2Gb FC Ports per Storage Controller Topology

This figure shows a HA FAS3000 storage system with onboard 2Gb FC target ports attached to a single fabric. The fabric may consist of one or multiple fibre channel switches and, in fact, the storage controller may be attached to multiple switches. The HA storage system may have anywhere from four to eight connections to the fabric. Because of the non-redundant nature of the single fabric, this configuration cannot be considered to be fully redundant. This configuration is supported in single_image, standby, and partner, cfmodes. When a host has multiple paths to a single LUN configured on a storage controller, it is necessary for the host to have multi-pathing software installed. Although in this specific topology with two FC target ports per controller single attached hosts would not require multi-pathing software when the controllers are running in standby cfmode. In single_image, and partner cfmodes a host with a single fibre channel connection may still have multiple logical paths to the LUN if there are multiple connections from the NetApp storage controllers to the fabric. If it is not desired to have multiple paths to the LUNs, see the section on fibre channel zoning to learn how to eliminate the redundant paths.

Switch/Fabric 1

Controller 1 0a 0b

- 1 to 4 connections- Any ports

Figure 27: Single Fabric – One to Four Onboard 2Gb FC ports on a Single Storage Controller

This figure shows a single FAS3000 storage controller with one to four onboard 2Gb FC target ports attached to a single fabric. The fabric may consist of one or multiple fibre channel switches and, in fact, the storage controller may be attached to multiple switches. The storage controller may have anywhere from one to four connections to the fabric through any or all of the four onboard (0a, 0b, 0c, and/or 0d) 2Gb FC target ports for this topology. Because of the non-redundant nature of the single fabric and single NetApp storage controller, none of these variants may be considered fully redundant configurations. When a host has multiple paths to a single LUN, it is necessary for the host to have multi-pathing software installed. In this diagram, assuming there is more than one connection between the storage controller and the fibre channel fabric, all hosts would have multiple paths unless the fabric is zoned to prevent this. A host with a single fibre channel connection may still have multiple logical paths to the LUN if there are multiple connections from the NetApp storage controller to the fabric. If it is not desired to have multiple paths to the LUNs, see the section on fibre channel zoning to learn how to eliminate the redundant paths. A cfmode setting is not applicable for this configuration because the single FAS3000 controller is not clustered.

Figure 28: Direct Attach – 4Gb or 2Gb FC Single Storage Controller Topology

This figure shows the direct-attached configurations for single FAS3000 storage controllers. To determine which host HBAs and operating systems are supported, refer to the compatibility matrices on the NOW site. Because of the non-redundant components of the single fabric and single FAS3000 storage controller, none of these variants may be considered to be fully redundant. When a host has multiple paths to a single LUN configured on a storage controller (as with Host 2 in the middle configuration or the hosts in the right-hand configuration), it is necessary for the host to have multi-pathing software installed. For multiple-host configurations, the hosts may be heterogeneous (e.g. Windows and UNIX). A cfmode setting is not applicable for this configuration because the single FAS3000 controller is not clustered.

Host N (max 4)

Controller 1

… Host 1 Host 3

Controller 1

Host 2

Host 1 Host 2

Controller 1

Host 1

Switch /Fabric 1

LUNs LUNs

Controller 10d

Controller 2

Switch/Fabric 2

Figure 29: Dual Fabric – One Onboard 2Gb FC Port Per Controller single_image Topology

This figure shows a dual-fabric attached configuration for the FAS3000 storage system where one onboard 2Gb fibre channel target port is used on each storage controller. The onboard 2Gb fibre channel target port number (0d) is an example and it is possible to use the other remaining onboard 2Gb FC port (0b) or configure it as an additional back-end disk shelf connection. This topology is possible only with a HA storage controller configuration. When properly configured with multi-pathing software the hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). In this configuration, the remaining onboard 2Gb FC ports (0a and 0c) are used for back-end disk shelf connections. This configuration is supported only in single_image cfmode.

Switch /Fabric 1

Host 1

Controller 10b 0d

Controller 2

Switch /Fabric 2

0d0b 0c0a

Host 2 Host N

Figure 30: Dual Fabric – Two Onboard 2Gb FC Ports Per Controller single_image Topology

This figure shows a dual-fabric attached configuration for the FAS3000 storage system where two onboard 2Gb fibre channel target ports are used on each storage controller. This topology is possible only with a HA storage controller configuration. When properly configured with multi-pathing software dual attached hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). In this configuration, the remaining onboard 2Gb FC ports (0a and 0c) are used for back-end disk shelf connections. This configuration is supported only in single_image cfmode.

Switch /Fabric 1

Host 1

L U N s

Controller 1 0b 0d

Controller 2

Switch /Fabric 2

0a 0d0b

Host 2 Host N

Figure 31: Dual Fabric – Four Onboard 2Gb FC Ports Per Controller single_image Topology

This figure shows a dual-fabric attached configuration for the FAS3000 storage system where four onboard 2Gb fibre channel target ports are used on each storage controller. This configuration is possible only with a HA storage controller configuration. When properly configured with multi-pathing software, dual-attached hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). In this configuration dual ported Fibre Channel expansion adapter cards are used for back-end disk shelf connections. This configuration is supported with single_image and partner cfmodes.

Switch /Fabric 1

L U N s L U N s

Controller 1

0 b 1a

Controller 2

Switch /Fabric 2

0 a 0c

0c0a2 b 2a

Figure 32: Dual Fabric – Two Onboard 2Gb FC Ports With 6 Back-End Disk Connections

This figure is the same as a dual-fabric attached configuration for the FAS3000 storage system where two onboard 2Gb fibre channel target ports are used on each storage controller and has six back-end disk shelf storage connections. Onboard ports 0aand 0c are used for 2Gb FC Target connections. Onboard ports 0b and 0d as well as dual ported FC expansion adapters are used to provide back-end disk shelf connections via ports 2a, 2b, 1a, and 1b. This topology is possible only with a HA storage controller configuration. When properly configured with multi-pathing software dual-attached hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX). This configuration is supported with single_image cfmodes.

LUNs LUNs

Controller 10d

Controller 2

Figure 33: Direct Attach – One Onboard 2Gb FC Port per Controller single_image Topology

This figure shows a direct attached FC configuration for the FAS3000 storage system where one onboard 2Gb Fibre Channel target port is used per controller. The ONTAP fcp adapter mediatype may have to be set to loop on each 2Gb FC target port for some host direct attach topologies. To determine which host HBAs and operating systems are supported, refer to the compatibility matrices on the NOW site. This FAS3000 HA topology has dual controllers with one onboard 2Gb fibre channel target port. The host has a dual connection to the FAS3000 and is fully redundant since, the HBA, wiring, storage controller and disks are all redundantly configured. When a host has multiple paths to a single LUN configured on a storage controller, it is necessary for the host to have multi-pathing software installed. This configuration is only supported with single_image cfmodes.

3.8. FAS270 and FAS270C Supported Topologies

The following figures show the supported FC connection topologies for a FAS270 and a FAS270C.

Host 2

Filer 1 / Filer 2 FAS270C

FC Fabric 2

Host 1

…Host N

FC Fabric 1

Host 2

Figure 34: FAS270C – Dual Fabric Connect Topology

This figure shows the supported dual-fabric-attached configuration for the FAS270C. Each of the fabrics may consist of one or multiple FC SAN switches. To determine which host HBAs, operating systems and switches are supported, refer to the compatibility matrices on the NOW site. When properly configured with multi-pathing software, dual attached hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controllers and disks are all redundantly configured. Single-attached hosts are not fully redundant against a storage controller failure because in dual fabric configurations it is not possible for a single attached host to be attached to both storage controllers of the highly available FAS270C. When both the host and the storage controller are dual connected to two physically separate fabrics, this is considered Network A ppliance best practice. For multiple host configurations, the hosts may be heterogeneous (e.g. Windows and UNIX). This configuration is supported with dual_fabric and single_image cfmodes.

Host 2

Controller 1 / Controller 2 FAS270C

FC Fabric 1

Host 1

…Host N

Figure 35: FAS270C – Single Fabric Connect Topology

This figure shows the supported single-fabric-attached configuration for the FAS270C. The fabric may consist of one or multiple FC SAN switches. To determine which host HBAs, operating systems and switches are supported, refer to the compatibility matrices on the NOW site. This is not a fully redundant configuration since the fibre channel fabric is not redundantly configured. Although, both the single attached hosts as well as the dual attached hosts can be protected against a storage controller failure when properly configured with multi-pathing software to use the multiple paths to the LUNs. When a host has multiple paths to a single LUN configured on a storage controller, it is necessary for the host to have multi-pathing software installed. In this diagram all hosts would have multiple paths unless the fabric is zoned to prevent this. A host with a single fibre channel connection can still have multiple logical paths to the LUN if there are multiple connections from the NetApp storage controller to the fabric. For multiple-host configurations, the hosts may be heterogeneous (e.g. Windows and Unix). This configuration is supported with dual_fabric and single_image cfmodes.

Host 1 Host 1Host 1 Host 2

Controller 1FAS270

Controller1 / Controller 2 FAS270C

Figure 36: FAS270 and FAS270C – Direct Attach Topology

This figure shows the supported direct attached configurations for the FAS270 and FAS270C systems. To determine which host HBAs and operating systems are supported, refer to the compatibility matrices on the NOW site. The FAS270 has a single controller and a single fibre channel target port. The 270C has two redundant controllers each with a single fibre channel target port and is considered redundant from a storage perspective. Only the environment where the host has a dual connection to the FAS270C is fully redundant since, the HBA, wiring, storage controller and disks are all redundantly configured. When a host has multiple paths to a single LUN configured on a storage controller, it is necessary for the host to have multi-pathing software installed. For multiple-host configurations, the hosts may be heterogeneous (e.g. Windows and UNIX). This configuration is supported with dual_fabric and single_image cfmodes.

3.9. F800/FAS900 and Nearstore Supported Topologies

Switch/Fabric 1

Controller 1 Controller 2

Switch/Fabric 2

Host 2

7a 7a7b 7b

Figure 37: Dual Fabric – One Dual Ported FC Target Card per Controller

This figure shows a dual-fabric attached configuration for F800 and FAS900 series storage systems where two fibre channel target ports are used on each storage controller. The single_image cfmode requires only a single port per controller to protect against fabric and controller failures. When properly configured with multi-pathing software, dual attached hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controllers and disks are all redundantly configured. In the case of a cluster failover the identity of the FC ports will remain unchanged.

7a 7b 7a 7b

Switch/Fabric 1 Switch/Fabric 2

9a 9b 9a 9b

Figure 38: Dual Fabric – Two Dual Ported FC Target Cards per Controller

This figure shows a dual-fabric-attached configuration for F800 and FAS900 series storage systems. This configuration is possible only with a HA controller configuration. In the diagrams, the port numbers used (i.e. 7a, 7b, 9a, and 9b) are used only for example and, in reality, will vary depending on where the fibre channel target cards are installed on the systems. When properly configured with multi-pathing software the hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controller and disks are all redundantly configured. This is often considered the standard configuration when both the host and the storage controller are dual connected to two physically separate fabrics. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX) since each storage controller port is capable of customizing responses based on what type of operating system is accessing it. This configuration is supported in partner, standby, mixed & single_image cfmodes.

7a 7b7a 7b

Figure 39: Dual Fabric – Single Dual Ported FC Target Card per Controller

This figure shows a dual-fabric-attached configuration for F800 and FAS900 series storage systems where each controller contains only one dual-ported fibre channel HBA. This configuration is supported using partner and single_image cfmodes and typically would be recommended for smaller configurations. Refer to the cfmode section of this document for more information regarding cfmodes. Only a single host is shown in this example but normally multiple hosts would be connected to the dual fabrics, this configuration is possible only with a HA storage controller configuration. When properly configured with multi-pathing software, the hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controllers and disks are all redundantly configured. For multiple-host configurations the hosts may be heterogeneous (i.e. Windows and UNIX) since each storage controller port is capable of customizing responses based on what type of host is accessing it. This configuration only works in partner and single_image cfmodes.

4a/b 7a/b 4a/b

5a/b9a/b 5a/b 9a/b

Figure 40: Dual Fabric Connect – Four Dual Ported FC Target Cards Topology

This figure shows a dual-fabric-attached configuration for F800 and FAS900 series storage systems where each controller contains four dual-ported fibre channel HBAs. This configuration is possible only with a HA storage controller configuration. When properly configured with multi-pathing software, the hosts are fully redundant from the storage perspective since the HBA, wiring, fabrics, storage controllers and disks are all redundantly configured. This configuration is likely to be used in combination with large more complex fabrics where the eight connections between the storage controller and the fabric would not be to a single FC switch. For multiple-host configurations, the hosts may be heterogeneous (i.e. Windows and UNIX) since each controller port is capable of customizing responses based on what type of operating system is accessing it. This configuration is supported in partner, standby, mixed, and single_image cfmodes.

Figure 41: Single Fabric –High Availability Storage System Connect Topology

This figure shows a HA configured F800 or FAS900 series storage system attached to a single fabric. The fabric may consist of one or multiple fibre channel SAN switches and, in fact, the storage controller may be attached to multiple switches. The HA storage system may have anywhere from two to sixteen connections to the fabric depending on the number of fibre channel target cards installed in the storage controller. Because of the non-redundant nature of the single fabric, this configuration cannot be considered to be fully redundant. This diagram shows the absolute minimum FC wiring configuration for connecting a HA storage system to a single fabric. This configuration is supported only with and usable for configurations where LUNs are being served only by one storage controller. If LUNs are being served from both storage controllers, it is necessary to have a minimum of two connections per storage controller. In this case, the LUNs would be being served by the storage controller on the left of the diagram. It is important that the “a” port and the corresponding “b” port on the partner storage controller are attached to allow access to the LUNs in a failover situation. This configuration is supported with partner and single_image cfmodes although the single_image cfmode is highly recommended when there’s only one FC target port connection per controller.

Host 2

Controller 1F8XX/FAS9XXNearstore RXXX

FC Fabric 1

Host 1

…Host N

… 1 to 4 connections

Figure 42: Single Fabric – Single Storage Controller Connect Topology

This figure shows a Nearstore or non-HA configured F800 or FAS900 series storage system attached to a single fabric. The fabric may consist of one or multiple fibre channel SAN switches and, in fact, the controller may be attached to multiple switches. The storage controller may have anywhere from one to four connections to the fabric depending on the number of fibre channel target cards installed in the storage controller. Because of the non-redundant nature of the single fabric and the single NetApp storage controller, none of these variants can be considered to be fully redundant. When a host has multiple paths to a single LUN configured on a storage controller, it is necessary for the host to have multi-pathing software installed. In this diagram, assuming that there is more than one connection between the storage controller and the fibre channel fabric, all hosts would have multiple paths unless the fabric is zoned to prevent this. A host with a single fibre channel connection can still have multiple logical paths to the LUN if there are multiple connections from the NetApp storage controller to the fabric. If it is not desired to have multiple paths to the LUNs, see the section on fibre channel zoning to learn how to eliminate the redundant paths.

Host 1

Host N (max 4)

Controller 1 F8XX/FAS9XXNearstore RXXX

…Host 1 Host 3

Host 2

Host 1 Host 2

Figure 43: Direct Attach – Single Storage Controller Topology

This figure shows the direct-attached configurations for the F800, FAS900 or Nearstore systems. To determine which host HBAs and operating systems are supported, refer to the compatibility matrices referred to earlier in this document. Because of the non-redundant components of the single fabric and single NetApp storage controller, none of these variants can be considered to be fully redundant. When a host has multiple paths to a single LUN configured on a storage controller (as with Host 2 in the middle configuration or the hosts in the right-hand configuration), it is necessary for the host to have multi-pathing software installed. For multiple-host configurations, the hosts may be heterogeneous (e.g. Windows and UNIX) since each storage controller port is capable of customizing responses based on what type of operating system is accessing it. Direct attached is only supported with single controller F800 or FAS900 series storage appliances and is not supported with HA F800 or FAS900 series storage appliances.

4. Configuration Limits The following tables show the NetApp configuration limits. In some cases the limits may be theoretically higher but the tables show the tested and supported limits.

Parameter Operating Systems

Windows Linux HP-UX Solaris AIX VMware

Target Ports per System

16 16 16 16 16 16

LUNs per System

32 128 512 512 128 128

Paths per LUN 4 4 8 more possible but pvlinks will only utilize 8

16 16 4

Max LUN Size 2 TB

__________ 12 TB – Win2K3 SP1 or later

2 TB 2 TB 1023 GB

___________ 2TB With Solaris 9, VxVM and appropriate patches

____________ 2 TB with AIX 5.2ML7 or later and AIX 5.3ML3 or later

Table 1: Host-based limits in conjunction with NetApp Storage Controllers

Table 1 shows the host based configuration limits when using the NetApp Attach Kit (AK) with the respective host operating system. Below is a description of the various parameters.

• Target Ports per System – The number of NetApp FC target ports a server can see or can access on the attached fibre channel SAN.

• LUNs per System – The number of LUNs that can be mapped from the NetApp storage system(s) to a single server system.

• Paths per LUN – The number of active paths that a server has to a particular LUN.

• Max LUN Size – The maximum size of an individual NetApp LUN on the respective operating system.

Parameter Storage System

FAS270 F825 F880 FAS920 GF920

FAS940 FS940

FAS960 GF960

FAS980 GF980

Maximum number of LUNS per storage controller

1024 1024 2048 2048 2048 2048 2048 2048

Maximum Number of LUNs per volume

1024 1024 2048 2048 2048 2048 2048 2048

Maximum port Fan-in 16 16 64 64 64 64 64 64

Maximum storage controller fan-in

16 64 256 256 256 256 256 256

Maximum number of igroups per storage controller

256 256 256 256 256 256 256 256

Maximum number of initiators per igroup

256 256 256 256 256 256 256 256

Maximum number of LUN mappings per storage controller

4096 4096 4096 8192 8192 8192 8192 8192

Maximum length of LUN path name

255 255 255 255 255 255 255 255

Maximum LUN Size 6TB 2TB 6TB 4TB 6TB 12TB 12TB 12TB

Maximum FC target ports per storage controller

1 4 4 4 4 4 4 4

Table 2: Limits of Non-HA FAS270, F800, FAS900, V-Series, and R200 Storage Systems

FAS3020 V3020

FAS3050 V3050

FAS6030 V6030

FAS6070 V6070

Maximum number of LUNs per storage controller

1024 1024 2048 2048

Maximum number of LUNs per volume

1024 1024 2048 2048

Maximum port Fan-in 64 64 64 64

Maximum storage controller Fan-in

256 256 256 256

Maximum number of igroups per storage controller

256 256 256 256

Maximum number of LUN mappings per storage controller

4096 4096 8192 8192

255 255 255 255

Maximum LUN Size 12TB 12TB 12TB 12TB

Maximum FC target ports per storage controller

4 4 8 8

Table 3: Limits of Non-HA FAS6000, FAS3000, and V-Series Storage Systems

The above tables show the NetApp storage controller based configuration limits for the individual appliance models. Below is a description of the various parameters.

• Volumes per storage controller – The maximum number of volumes (either FlexVol or traditional volumes) supported per storage controller in a FC or iSCSI environment.

• LUNs per storage controller – The maximum number of LUNs that can be configured per storage controller. 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.

• LUNs per volume - The maximum number of LUNs that can be configured within a single volume. LUNs contained in Snapshots do not count in this limit and there is no limit on the number of LUNs that can be contained within Snapshot copies.

• Port Fan-in – The maximum number of hosts that can connect to a single fibre channel port on a storage appliance. For performance reasons, connecting this number of hosts is generally not recommended tuning of the Fibre Channel queue depths on the host is necessary to achieve this maximum value.

• Storage controller Fan-in - The maximum number of hosts that can connect to a storage controller. For performance reasons connecting this number of hosts is generally not recommended and tuning of the fibre channel queue depths on the host is necessary to achieve this maximum value.

• igroups per storage controller – Maximum number of initiator groups that can be configured per storage controller.

• Number of initiators per igroup – Maximum number of fibre channel initiators (i.e. host HBA WWNs) that can be included in a single igroup.

• Number of LUN mappings per system – Maximum number of LUN mappings per storage controller. For example, a LUN mapped to two igroups would be counted as two mappings.

• Length of LUN path name – The maximum number of characters a LUN name can consist of. For example, /vol/abc/def has a length of 12.

• LUN Size – The maximum capacity of an individual LUN on a storage appliance.

• FC target ports per storage controller – The maximum number of supported fibre channel ports per storage controller. Fibre Channel initiator ports used for back-end disk connections (i.e., connections to disk shelves) are not included in this number.

FAS270C F825C F880c FAS920c GF920c

FAS940c GF940c

FAS960c GF960c

FAS980c GF980c

Maximum number of LUNS per HA storage system

1024 1024 2048 2048 2048 2048 2048

Maximum port fan-in 16 16 64 64 64 64 64

Maximum HA storage system fan-in

16 64 256 256 256 256 256

Maximum number of Igroups per HA storage system

256 256 256 256 256 256 256

Maximum number of LUN mappings per HA storage system

4096 4096 8192 8192 8192 8192 8192

255 255 255 255 255 255 255

Maximum LUN size 6TB 2TB 6TB 4TB 6TB 12TB 12TB

Maximum FC target ports per HA storage system

2 16 16 16 16 16 16

Table 4: Limits of HA FAS270, F800, and FAS900 Storage Systems

FAS3020c V3020c

FAS3050c V3050c

FAS6030c V6030c

FAS6070c V6070c

Maximum number of LUNS per HA storage system

1024 1024 2048 2048

Maximum port fan-in 64 64 64 64

Maximum HA storage system fan-in

256 256 256 256

Maximum number of igroups per HA storage system

256 256 256 256

Maximum number of LUN mappings per HA storage system

4096 4096 8192 8192

255 255 255 255

Maximum LUN size 12TB 12TB 12TB 12TB

Maximum FC target ports per HA storage system

8 8 16 16

Table 5: Limits of HA FAS6000, FAS3000, and V-Series Storage Systems

The tables above show the NetApp storage controller based configuration limits for the individual appliance models. Below is a description of the various parameters.

• Volumes per storage controller – The maximum number of volumes (either FlexVol or traditional volumes) supported per storage controller in a FC or iSCSI environment.

• LUNs per HA storage system – The maximum number of LUNs that can be configured for an entire HA Storage system. 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.

• LUNs per volume - The maximum number of LUNs that can be configured within a single NetApp storage system 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.

• Port fan-in – The maximum number of hosts that can connect to a single fibre channel port on a NetApp storage system. For performance reasons, connecting this number of hosts is generally not recommended and tuning of the Fibre Channel queue depths on the host is necessary to achieve this maximum value.

• HA storage system fan-in - The maximum number of hosts that can connect to a HA storage system. For performance reasons connecting this number of hosts is generally not recommended and it is important to note that tuning of the fibre channel queue depths on the host side is necessary to get to this maximum value.

• igroups per HA storage system – Maximum number of igroups that can be configured per HA storage system.

• Number of initiators per igroup – Maximum number of fibre channel initiators (i.e. host HBA WWNs) that can be included in a single igroup.

• Number of LUN mappings per HA storage system – Maximum number of LUN mappings per HA storage system. For example, a LUN mapped to two igroups would be counted as two mappings.

• Length of LUN path name – The maximum number of characters a LUN name can consist of. For example, /vol/abc/def has a length of 12.

• LUN Size – The maximum capacity of an individual LUN on a storage controller.

• FC target ports per HA storage system – The maximum number of supported fibre channel target (host connection) ports per HA storage system. Fibre Channel initiator ports used for back-end disk connections (i.e., connections to disk shelves) are not included in this number. The maximum per controller is still the limit defined for non-HA storage systems. For example when there’s a maximum of 16 FC target ports per HA storage system configured there must be 8 FC target ports on each controller. It is not possible to have 12 FC target ports configured on one controller and 4 FC target ports on the partner controller.

5. Cluster Failover Mode – CFMODE CFMODE is a storage appliance FCP failover mode setting which controls how the appliance handles fibre channel before and after cluster failover events. The cfmode is not available and not relevant on non-clustered storage controllers. The mode can be changed using the “fcp set” command from the console after setting the privileges to advanced.

5.1. CFMODE Types

The following is a summary of the cfmodes. Detailed descriptions of the behavior of the ports with each cfmode are available in the ONTAP blocks administration guide.

Single System Image (single_image) cfmode – This mode is available on all NetApp HA storage systems with ONTAP 7.1 and later. SSI also allows all ports on the local controller to be useable for local LUN access and eliminates the port burn issue. SSI requires only a single port per controller to protect against head and fabric failure.

• Features

? Supports all filers and switches

? Efficient use of FC target ports

? All LUNS are visible on all ports

• Considerations

? None

Dual Fabric (dual_fabric) cfmode – This mode is available only on the FAS270C. In dual_fabric mode, LUNs served by a storage controller are always accessible from the fibre channel ports on either of the storage controllers. For performance reasons, it is recommended to access the LUNs primarily though the fibre channel ports on the storage controller which is servicing that LUN. Network Appliance supported multi-pathing software solutions take care of this selection automatically. Because this cfmode requires a fabric loop connection type, it is not supported on some switches, such as the older model enterprise class McData switches.

• Features

? Support for all operating systems

? Requires fewer number of switch ports

• Considerations

? Requires loop mode

Partner cfmode – This is the default cfmode for Data ONTAP 6.5. through ONTAP 7.1. This mode is available on F800, FAS900, and FAS3000 series HA storage systems. In this mode, LUNs served by a storage controller are always accessible from the “A” fibre channel ports on the storage controller serving the LUN and on the “B” fibre channel ports on the partner storage controller. For performance reasons, it is recommended to access the LUNs primarily though the fibre channel ports on the controller which is

servicing that LUN. Network Appliance supported multi-pathing software solutions take care of this selection automatically. This cfmode uses fabric logins and is supported on all switches.

• Features

? Supports all switches

? Easy to manage

• Considerations

? Requires more switch ports/wiring since both the A and B target fibre channel ports need to be connected

Standby cfmode – This was the default cfmode for pre-Data ONTAP 6.5 releases. This mode is available on F800, FAS900, and FAS3000 series HA storage systems. In this mode LUNs served by a storage controller are always accessible from the “A” fibre channel ports on the storage controller serving the LUN and are first made available on the “B” fibre channel ports on the partner storage controller during a failover event. This cfmode uses fabric logins and is supported on all switches.

• Features

? Supports all switches

? Allows multiple active ports with the NetApp ASL 2.0 for VERITAS

? Windows MPIO Version 3.2 or later will round-robin LUNs across the available primary paths

• Considerations

? Does not support all operating systems

? Requires more switch ports/wiring since both the A and B target fibre channel ports need to be connected

? Requires a minimum of two FC target cards per storage controller or 4 FC target ports per controller on FAS3000 for full storage system high availability

Mixed cfmode – This mode is available on F800, FAS900, and FAS3000 series HA storage systems. This cfmode is equivalent to standby mode for Windows and Solaris hosts and partner mode for AIX and HP-UX hosts except that instead of using the physical A and B fibre channel ports this functionality is made available on each physical fibre channel port through the use of virtual ports. Because this cfmode requires a fabric loop connection type, it is not supported on some switches, such as the older-model enterprise class McData switches.

• Features

? Requires fewer number of ports

• Considerations

? Not supported by all switches because loop mode is required

5.2. CFMODE Recommendations

The following are the Network Appliance recommendations for setting the cfmode.

• FAS270C, F800, FAS900, FAS3000, and FAS6000 Series HA storage systems

? single_image cfmode

6. Zoning A fibre channel zone consists of a group of fibre channel ports or nodes that can communicate with each other. It can be thought of as a logical fabric subset. Two fibre channel nodes can communicate with one another only when they are contained in the same zone. A node can be contained in multiple zones. For example, it is typical for a storage node (i.e., NetApp target FC port) to be contained in multiple zones.

6.1. Hard and Soft Zoning

There are generally considered to be two methods of zoning, hard and soft zoning.

• Hard Zoning –

? Port based – Often referred to as “port zoning”, the zone is defined by specifying the fabric unique N_port IDs of the ports to be included. In other words, the switch and switch port (i.e., switch3/Port 4) are used to define the zone members.

? Security – Hard zoning typically is considered to offer improved security since it is not possible to breach the zoning using WWN spoofing. However, if someone has physical access to the switch simply replacing a cable can allow access when hard zoning is used.

? Manageability – In many environments hard zoning is easier to create and manage since only the switch or switch domain and port number need to be worked with instead of the 16-digit WWNs.

• Soft Zoning –

? World Wide Name (WWN) based – The zone is defined by specifying 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 although Network Appliance recommends World Wide Port Name zoning.

? Flexibility – Since access is not determined by where the device is physically plugged into the fabric, it is possible with soft zoning to simply move a cable from one port to another without needing to reconfigure the zoning. This can be useful in troubleshooting situations

6.2. Reasons for Zoning

There are multiple reasons for zoning and the larger the fibre channel SAN the more sense it makes to implement zoning. Some of the most applicable reason to implement zoning are:

• Initiator Cross Talk – Zoning reduces or eliminates “cross talk” between initiator (host) HBAs. This has been experienced 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.

• Limit available Paths – As mentioned earlier in the configuration limits tables, only a particular number of paths between a host and a particular LUN should be visible. For example, a maximum of 4 paths for the Windows MPIO solution or 16 for various UNIX solutions should be available. If a host does not have a multi-pathing solution installed, it is typically necessary to ensure that only one path to a LUN is visible to avoid problems. Zoning is the correct tool to reduce the number of available paths to a particular fibre channel storage port.

• Security – Because zoning limits access between different nodes of a SAN, security is clearly increased

• Problem Reduction/Isolation – The most compelling reason to implement zoning is that it improves SAN reliability by isolating many problems which occur and can help to reduce problem resolution time by helping limit the problem space.

6.3. Network Appliance Zoning Recommendations

• For fibre channel SAN zoning, Network Appliance recommends the following:

• Zoning – Anytime 4 or more hosts are connected to a SAN, zoning should be implemented.

• Hard or WWPN Zoning – World Wide Node Name zoning is possible with some switch vendors but for Network Appliance FC Target connections WWPN zoning is recommended. Because of the various trade-offs there is no specific recommendation between hard versus soft zoning.

• Zone Size – NetApp generally recommends to keeping the zone size as small as possible while still maintaining manageability. It is not a problem to have many multiple overlapping zones to help keep the individual zones smaller. Ideally, a zone will be defined for each host or host cluster.

6.4. Zoning Diagrams

Because of the nature of zoning, it is often easiest to understand by illustration. Below are several diagrams showing several of the assets of zoning.

zone2 zone3

Host2 Host3

Figure 44: Hosts in Individual Zones

This figure shows an example where each host is shown in a separate zone. This should be the standard zoning configuration for a simple environment. The zones are overlapping since the storage ports are included in each zone to allow each server to access the storage. Each host can see all of the fibre channel target ports but cannot see or interact with the other host ports.

Using hard or port zoning, this zoning configuration can be done in advance even if all the servers are not present. Assuming that the storage is connected to ports 1 through 4, each zone can be defined to contain a single port for the server and ports 1 through 4. For example, one zone would consist of port 1, 2, 3, 4, and 5 while the next zone would consist of ports 1, 2, 3, 4, and 6 and so forth.

This diagram shows only a single fabric but a supported configuration would have two fabrics. The second fabric would have the exact same zone structure.

FAS270C

Host2 Host3

FC Fabric

Figure 45: Single Fabric, No Multipathing Zoning

In this figure, Host1 and Host2 do not have multipathing software and therefore have to be zoned so that only one path to each LUN is available to them. Therefore, the zone containing these hosts contains only one of the two storage ports. Even though the host has only one HBA, both storage ports were included in the zone, the LUNs would be 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.

Since this figure contains only a single fabric (may consist of one or more switches), it is not considered fully redundant because a switch or fabric failure would lead to an outage. NetApp only considers dual, physically independent fabrics to be fully redundant. However, as shown, Host3 and Host4 have multipathing software and to protect against a possible storage controller failure are zoned so that a path to the LUN(s) is available through each of the storage controllers.

zone1 zone2

FAS270C

Host1 Host2

FC Switch

FAS270C

zone1 zone2

Appliance #1 Appliance #2

Figure 46: Multiple Storage System Zoning

This figure shows a configuration where Host1 will be accessing LUNs from appliance #1 and Host2 will be accessing LUNs from appliance #2. Both storage appliances are highly available with two storage controllers. This is a fully redundant configuration and both fabrics are shown in this example. Multiple FAS270Cs are shown in this diagram but this is not necessary for high availability. A single FAS270C system offers high availability.

This zoning separates the hosts to eliminate initiator (host HBA) cross talk and prevents Host1 from accessing appliance #2 which increases security while improving reliability, manageability and problem solving.

network appliance fibre channel configuration guide 2006-7.pdfnetapp figure 1: dual fabric – two...

Documents

figure-ground mapping to identify urban fabric ... ·...

a novel dual mode substrate integrated ...progress in...

dual motor rise and walmesley dual motor recline chair in...

dual differential comparator lm393zero crossing detector...

figure 1 the developed dual-arm robots -...

thuraya t2m-dual - thuraya | mobile satellite ... - dual...5...

ptn vs dual fabric pots for sdh migration 1212

route processor - cisco.com · as shown in figure 6-1, the...

windham fabrics...exclusively by windham 'fabrics figure 1...

ddi602am outdoor dual pir/am detector … outdoor dual...

fabric shade dual-shade - hartmannforbes.com |...

the make-up of the city’s fabric - occidental college ·...

little house on the prairie® - andover fabrics house on the...

an h-shaped dual band microstrip patch antenna … ·...

roller shades -...

august 2020 list pricing - compeloffice.com · black base...

circle packing & the koebe-andreev-thurston...

cisco mds 9250i multiservice fabric switch data sheet ·...

project island library/communities/student...

dual-interface card personalization...2018/10/18 · u.s....