V-Series Systems Implementation Guide for EMC Symmetrix Storage

Network Appliance, 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: [email protected] Information Web: http://www.netapp.com Part number 210-04951_A0 June 2010

Copyright and trademark information

Copyright information

Copyright 1994-2010 NetApp, Inc. All rights reserved. Printed in the U.S.A. Software derived from copyrighted NetApp material is subject to the following license and disclaimer: THIS SOFTWARE IS PROVIDED BY NETAPP AS IS AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. NetApp reserves the right to change any products described herein at any time, and without notice. NetApp assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp. The product described in this manual may be protected by one or more U.S.A. patents, foreign patents, or pending applications. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Trademark information

NetApp; the NetApp logo; the Network Appliance logo; Cryptainer; Cryptoshred; DataFabric; Data ONTAP; Decru; Decru DataFort; FAServer; FilerView; FlexCache; FlexClone; FlexShare; FlexVol; FPolicy; gFiler; Go further, faster; Manage ONTAP; MultiStore; NearStore; NetCache; NOW (NetApp on the Web); ONTAPI; RAID-DP; SANscreen; SecureShare; Simulate ONTAP; SnapCopy; SnapDrive; SnapLock; SnapManager; SnapMirror; SnapMover; SnapRestore; SnapValidator; SnapVault; Spinnaker Networks; Spinnaker Networks logo; SpinAccess; SpinCluster; SpinFlex; SpinFS; SpinHA; SpinMove; SpinServer; SpinStor; StoreVault; SyncMirror; Topio; vFiler; VFM; and WAFL are registered trademarks of NetApp, Inc. in the U.S.A. and/or other countries. Network Appliance, Snapshot, and The evolution of storage are trademarks of NetApp, Inc. in the U.S.A. and/or other countries and registered trademarks in some other countries. The StoreVault logo, ApplianceWatch, ApplianceWatch PRO, ASUP, AutoSupport, ComplianceClock, DataFort, Data Motion, FlexScale, FlexSuite, Lifetime Key Management, LockVault, NOW, MetroCluster, OpenKey, ReplicatorX, SecureAdmin, Shadow Tape, SnapDirector, SnapFilter, SnapMigrator, SnapSuite, Tech OnTap, Virtual File Manager, VPolicy, and Web Filer are trademarks of NetApp, Inc. in the U.S.A. and other countries. Get Successful and Select are service marks of NetApp, Inc. in the U.S.A. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. A complete and current list of other IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml.

ii

Copyright and trademark information

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.

Copyright and trademark information

iii

iv

Copyright and trademark information

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1

Implementation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Symmetrix specific terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 Supported Symmetrix storage arrays and firmware . . . . . . . . . . . . . . . 6 Required Symmetrix configuration settings . . . . . . . . . . . . . . . . . . . 7 Assignment of array LUNs to V-Series systems . . . . . . . . . . . . . . . . 11 Guidelines for array LUN sizing . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2

Supported Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Your guide to interpreting the illustrations . . . . . . . . . . . . . . . . . . . 18 Direct-attached configurations . . . . . . . . . . . . . . . . . . . . . . . . . 20 Simple fabric-attached configuration . . . . . . . . . . . . . . . . . . . . . . 23 Fabric-attached configurations that optimize performance. . . . . . . . . . . 25

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Table of Contents

vi

Table of Contents

Preface
About this guide This guide provides information about how to set up your storage array to work with a V-Series system running Data ONTAP software, including configuration guidelines and sample configurations. The information in this guide pertains to all supported V-Series platforms. Note Data ONTAP software runs on multiple hardware platforms. This documentation might describe features that are not supported on your platform.

Audience

This guide is for system administrators who are familiar with operating systems such as UNIX and Windows and who will be installing V-Series systems. This guide does not discuss basic system or network administration topics, such as IP addressing, routing, and network topology; it emphasizes the characteristics of the V-Series system.

Relationship of this guide to other guides

This guide is intended to be used in conjunction with other information in the V-Series and Data ONTAP libraries. The following table describes the relationships between this guide and other documentation. Guide name Installation Requirements and Reference Guide Information includes...

General guidelines for creating and making array LUNs available to V-Series systems. Quick start installation instructions for connecting devices together and for installing Data ONTAP on a V-Series system that uses only third-party storage. Reference information. Detailed background information including layout in aggregates and checksums. Vendor-specific details about how to set up a storage array to work with V-Series systems. More detailed configuration examples than are provided in the Installation Requirements and Reference Guide.
vii

Implementation Guides

Preface

Guide name Implementation Guide for Native Disk Shelves Data ONTAP software setup guides

Information includes... Information about setting up the storage on the native disk shelves connected to the V-Series system. Detailed steps for setting up the V-Series system, including information about installing Data ONTAP software for installations using only thirdparty storage. These guides are most helpful to users who are new to Data ONTAP setup and installation. Detailed information about all Data ONTAP features used by all systems running Data ONTAP, for example, storage features and data protection features.

Data ONTAP guides

See the V-Series Support Matrix for details about Data ONTAP releases that support V-Series, supported switches, supported firmware, capacity, and maximum array LUN count.

Special messages

This guide contains special messages that are described as follows: Note A note contains important information that helps you install or operate the system efficiently. Attention Attention contains instructions that you must follow to avoid damage to the equipment, a system crash, or loss of data.

viii

Preface

Implementation Overview
About this chapter

This chapter provides an overview of how to integrate V-Series systems with supported EMC Symmetrix storage arrays.

Topics in this chapter

This chapter discusses the following topics:

Symmetrix specific terminology on page 2 Supported Symmetrix storage arrays and firmware on page 6 Required Symmetrix configuration settings on page 7 Assignment of array LUNs to V-Series systems on page 11 Guidelines for array LUN sizing on page 13

Generic storage allocation terms used to in this document

Terminology for the same entity varies in EMC Symmetrix documentation and configuration and management tools. The following generic terms are used in this document. array LUN: This guide uses the term array LUN (logical unit number) to describe an area on the storage array that is available for a V-Series system or a non V-Series host to read data from or write data to. You might be accustomed to hearing a different term to describe this area; the term varies among vendors and sometimes among platforms for the same vendor. See the V-Series Implementation Guide for your storage array type for the specific term used for your platforms. HA pair: Two storage systems (nodes) whose controllers are connected to each other either directly or through switches. In some versions of Data ONTAP, this configuration is referred to as an active/active configuration.

Chapter 1: Implementation Overview

Symmetrix specific terminology

channel director

The component in a Symmetrix storage array that interfaces between the host channels and data storage. It transfers data between the channel and global memory. The number of channel directors and total ports on each channel director varies on different Symmetrix storage array models. Some Symmetrix models use another term for this componentfor example, host director or channel adapter.

director

See host director, channel director, and disk director.

disk director

The component in the Symmetrix storage array that interfaces between the global memory and the disk devices.

EMC ControlCenter (ECC)

An EMC application that can be used to monitor, configure, and control storage across platforms and environments.

EMC Symmetrix Management Console (SMC)

A browser-based graphical interface for managing multiple Symmetrix systems.

Enginuity

The operating environment for the EMC Symmetrix Enterprise Storage Platforms. Enginuity provides functional services for its host Symmetrix systems and for the EMX storage application software.

FEBE Board

(Front-End-Back-End Board) Contains up to 16 ports with 8 front-end host ports and 8 back-end disk ports. The FEBE Board is the interface between the Fibre Channel director front-end host ports and back-end disk ports. Each FEBE Board contains 2 channel directors, with 8 ports per channel director.

Symmetrix specific terminology

Fibre Channel director

See host director and channel director.

gatekeeper

A logical device, accessible by a host, through which SYMAPI or the ControlCenter agent communicates with the Symmetrix storage array.

host director

A generic term for a component that manages host-facing I/0 and provides the logical mapping to ports that makes storage available. Terms used to refer to this component vary among storage array models; they include channel director, Fibre Channel director, and director.

Host Type Format

Each logical device in a Symmetrix storage array is formatted using a specific format type. For logical devices that you intend to present to V-Series systems, you must use the default format type for Open Systems, which is Server in the ECC GUI, when you create the logical device. (See Required Symmetrix configuration settings on page 7.)

hypervolume

A data unit on a single disk drive. Depending on its size, a physical disk can contain several hypervolumes. A RAID5 configuration, for example, is composed of four (3+1) or eight (7+1) hypervolumes. You can combine multiple hypervolumes to create a metavolume.

logical device

A logical storage element that is configured on the storage array. Some Symmetrix documentation uses the term logical volume for this element. In the Symmetrix CLI, the term SymmDev is the equivalent term for logical device. Logical devices cannot be accessed by hosts until after they have been mapped to a host-facing port on the storage array. A logical device that has been mapped to an array host director port is often referred to as a LUN. The V-Series documentation uses the term array LUN to refer to a mapped logical device.

Chapter 1: Implementation Overview

logical volume (LV)

A user-defined storage device. A user can define a physical disk device as one-toeight logical volumes (logical devices). (This document used the term logical device instead of logical volume.)

logical unit number (LUN)

An encoded identifier for the logical unit of a SCSI device.

metavolume

A logical volume set created from individual physical disks to define logical volumes larger than the current Symmetrix maximum hypervolume size. Physically, a metavolume is two or more Symmetrix hypervolumes presented to a host as a single addressable device. For example, you can create a pool of equal-sized logical volumes in which each volume in the pool maps directly to a 72-GB metavolume. This 72-GB metavolume is composed of eight hypervolumes of 9 GB each.

Parity RAID, Parity RAID group

A Symmetrix feature that provides parity data protection on the disk device level using physical parity volumes. A Parity RAID (3+1) group consists of three data drives and one parity drive. A Parity RAID (7+1) group consists of seven data drives and one parity drive. In V-Series documentation, the generic term RAID group is used as the equivalent term to Parity RAID group.

SymmDev

In the CLI, the internal name for a logical device.

UWN

(Unique World Wide Name) In a Symmetrix storage array, each Fibre Channel port used for host connectivity has a unique WWN.

volume (EMC)

In a Symmetrix storage array, a general term referring to a storage device. A physical volume corresponds to a single disk device. A user can define a physical disk device as anywhere from one to eight logical volumes. (See also logical volume.)

Symmetrix specific terminology

Note EMC Symmetrix volumes are not the same as Data ONTAP volumes. A Data ONTAP volume is a logical entity that holds user data that is accessible through one or more of the access protocols supported by Data ONTAP, including Network File System (NFS), Common Internet File System (CIFS), HyperText Transfer Protocol (HTTP), Fibre Channel Protocol (FCP), and Internet SCSI (iSCSI). V-Series treats a Symmetrix volume (logical device), hypervolume, or metavolume as a disk.

Chapter 1: Implementation Overview

Supported Symmetrix storage arrays and firmware

Finding out which Data ONTAP release supports which storage arrays

This guide provides information about the storage arrays that V-Series supports at the time of publication. Not all models described in this guide are supported in all Data ONTAP releases. To determine which storage array models are supported in a particular Data ONTAP release, see the V-Series Support Matrix. Note The V-Series Support Matrix is the final authority about which Data ONTAP releases, storage arrays, firmware, switches, features, and so on that V-Series systems support.

Supported storage arrays

To determine which storage array platforms are supported and how they are organized into families, see the V-Series Support Matrix.

Supported Symmetrix storage arrays and firmware

Required Symmetrix configuration settings

Enginuity level required

Symmetrix Enginuity is the operating environment for Symmetrix systems. See the V-Series Support Matrix for the Enginuity level requirements.

You must set both parameters related to SCSI-3

You must set two different parameters related to SCSI-3one at the port level and one at the logical device (LUN) level. The two SCSI-3 flags that you need to set are as follows:

SC3 Flag or SCSI-3 Flag. You must set this flag on each host (channel) director port to which the V-Series system connects. SCSI3_persist_reserv or PER Flag. You must set this flag on each logical device that V-Series will use.

Attention Both SCSI-3 parameters are required for V-Series system to work. The SCSI-3 flag enables the connecting port to understand the SCSI-3 dialect and semantics. In addition to the SCSI-3 flag being enabled, each LUN must have the ability to remember and enforce persistent reservations requested in the SCSI-3 dialectthe SCSI3_persist_reserv flag setting for each logical device enables each LUN to enforce the persistent reservations requests.

Parameters to set on a host (channel) director port basis

Configure the following settings for each host (channel) director port to which the V-Series system connects. Note Parameter names might be different depending on whether they appear in the GUI or CLI.

Chapter 1: Implementation Overview

Parameter Common SN (Common Serial Number flag, also known as the C-bit Flag)

Value to set Enable this parameter so that each array LUN is presented across the various Fibre Channel director ports.

Comments This parameter assigns a common serial number across the logical devices that are exposed through multiple target ports. Note Most multipathing software uses the LUN serial number to determine whether a LUN has multiple paths.

PP Flag (Point-to-Point flag)

Enable this flag on the FA ports if the V-Series systems and Symmetrix storage array are connected through switches. Enable this flag.

Do not enable the PP Flag if the V-Series systems and the storage array are directly connected. Describes the command sets for block-oriented direct-access devicesfor example, disk drives. V-Series supports SCSI-3 command blocks.

SC3 Flag (SCSI-3)

SPC-2 Flag (SCS2_Protocol_version, SCSI Primary Command 2 flag, or Allow inquiry data to be compiled to the standard) UWN Flag (Unique World Wide Name flag)

Enable this flag.

Contains the second-generation definition of the basic commands for all SCSI devices. SPC-2 is used in conjunction with several standards for the specific device type, including SCSI-3 Block Commands (SBC-3).

Enable this flag for each target port so that each FA port that communicates with the V-Series system has a Unique World Wide Name.

Required Symmetrix configuration settings

Parameters to set for each logical device for V-Series Parameter Host Type Format

When you create a logical device that you intend to present to V-Series systems, you must set the values of the parameters in the following table as shown.

Value to set Default format type for Open Systems, which is Server in the EMC ControlCenter. Set this flag to On.

Comments Each logical device in the storage array is formatted using a specific format type. This flag, commonly known as SCSI-3 Persistent Reservations, is set to support hosts that require SCSI-3 persistent reservations. V-Series uses the Write Exclusive Registrants Only persistent reservation type.

SCSI3_persist_reserv

(Persistent Reservations flag or PER Flag)

Requirement for LUN access control

To eliminate the possibility of a non V-Series system overwriting Symmetrix array LUNs owned by a V-Series system, or the reverse, you must present the logical devices through the host (channel) director ports in one of the following ways: Method 1: Present only the Symmetrix logical devices for V-Series on specific Symmetrix host (channel) director ports that are dedicated to V-Series use, and prevent the logical devices for V-Series from being mapped through other host (channel) director ports. Method 2: Use the LUN masking capability to associate all Symmetrix logical devices to all host (channel) director ports, but allow only the V-Series FC initiator ports to see the LUNs for V-Series. If you are setting up a configuration in which you are using multiple array LUN groups for V-Series, you will set up a separate host group for each group of LUNs for V-Series (see Fabric-attached configurations that optimize performance on page 25 for an example of this type of configuration).

Chapter 1: Implementation Overview

Attention If you use Method 2, do not present the VCMDB (Volume Configuration Management DataBase) to all hosts by default. Configure the global setting to restrict visibility to the VCMDB unless it has been specifically made visible to a particular host. The results of Method 2 are the same as Method 1. But the benefit is that masking is at the logical level (initiator port WWN) rather than at the physical or switch zone level.

Recommendation regarding port sharing

It is strongly recommended that you do not share Symmetrix array ports between V-Series clients and non V-Series clients. The reason is that there is great potential for incompatible port requirements when Symmetrix ports are shared between V-Series clients and non V-Series clients. Each host connecting to the Symmetrix storage array has different requirements for port attribute settings, which can result in a configuration that is impossible to implement. If the ports on the Symmetrix storage array cannot be dedicated to the V-Series system, confirm that the port requirements for all other clients using that port are compatible with V-Series port requirements.

10

Required Symmetrix configuration settings

Assignment of array LUNs to V-Series systems

Maximum number of array LUNs you can allocate to V-Series

The maximum number of array LUNs on the Symmetrix system that you can allocate to V-Series is controlled by the following:

The maximum LUN limit of the V-Series model The Data ONTAP-imposed limit of the maximum number of LUNs per host group

Data ONTAP imposes a maximum limit of 256 array LUNs per host group. You cannot exceed the V-Series neighborhood maximum array LUN limit for the models of the V-Series systems in the neighborhood. The maximum number of array LUNs in a V-Series neighborhood is calculated by adding the number of LUNs presented to the V-Series systems in the neighborhood by all storage arrays. See the V-Series Support Matrix for information about the maximum neighborhood array LUN limit.

Required number of paths to an array LUN

V-Series systems expect a storage array to provide access to a specific array LUN on only two of the storage array host (channel) director ports: one is the primary path and the other is the alternate (secondary) path. A given LUN is accessed through only one host (channel) director port at a time. (See the V-Series Installation Requirements and Reference Guide for details about paths.) When you map a logical device, you select the two host (channel) director ports that the V-Series system can use to access the LUN. Ensure that the two director ports that you select to access a given LUN are from alternate FEBE Boards to avoid a single point of failure (SPOF). A SPOF would occur if the two director ports you selected were on the same FEBE Board and the board failed.

LUN numbers you can use with V-Series

Do not use a LUN with a LUN ID of 0.

Requirements for matching LUN IDs

The LUN number used to map the array LUNs must be the same on each host director port in the port pair, or data corruption can occur. (Port pair refers to the two redundant storage array ports that are used to access the same LUN.)

Chapter 1: Implementation Overview

11

Format of Symmetrix LUN IDs

Symmetrix LUN IDs are in hexadecimal format. Data ONTAP LUN IDs are in decimal format. To correlate Symmetrix LUN IDs and Data ONTAP LUN IDs, you must convert the hexadecimal numbers to decimal.

Caution about using the VCMDB LUN

For VCMDB (Volume Configuration Management DataBase) to be enabled, the VCMDB LUN must exist. The VCMDB LUN is a command type LUN, not a storage LUN. VCMDB is typically mapped to LUN 0. However, the VCMDB LUN can be an array LUN other than LUN 0. If you map the VCMDB LUN to the V-Series system, the V-Series system periodically logs a message that the VCMDB LUN is less than the minimum size required, and it marks the VCMDB LUN as failed. The V-Series system continues to function normally after logging this error message.

Caution about using a gatekeeper LUN

If a gatekeeper logical device (LUN) is presented, do not map it to the V-Series system. A V-Series system cannot use a gatekeeper LUN. A gatekeeper LUN is smaller than V-Series can handle. You cannot assign the gatekeeper LUN to the V-Series system with the disk assign command. Note A gatekeeper is a Symmetrix logical device, accessible by a host, through which SYMAPI or the ControlCenter agent communicates with the storage array.

12

Assignment of array LUNs to V-Series systems

Guidelines for array LUN sizing

Relationship of Data ONTAP and storage array units of measure

The size of the array LUNs that you can create on the storage array is limited by the minimum and maximum array LUN sizes that Data ONTAP supports. The Data ONTAP definition of a gigabyte (GB) might not match the definition of a GB for your storage array. When you determine the minimum and maximum array LUN sizes for your storage array, you need to consider whether the units of measure for your storage array are different from Data ONTAP units of measure. The Data ONTAP definition of a GB is as follows: One GB is equal to 1000 x 1024 x 1024 bytes. See the V-Series Support Matrix for the general rule about Data ONTAP minimum and maximum array LUN sizes. Each V-Series Implementation Guide contains specific information about the equivalent limits according to the vendors calculation of units of measure.

Minimum array LUN size for the root volume

The minimum array LUN size shown in this section does not apply to the array LUN for the root volume. It is strongly recommended that you do not set the size of a root volume below the minimum root volume size shown in the V-Series Support Matrix. The reason is that you want to ensure that there is sufficient space in the root volume for system files, log files, and core files. If a system problem occurs, you need to provide these files to technical support.

Minimum and maximum array LUN value usable with EMC Symmetrix

EMC Symmetrix calculates units of measure differently than Data ONTAP. The maximum usable values shown in this section are based on the assumption that the units of measurement for your storage array are calculated as follows. Unit GB MB KB Formula for calculating... 1024 x 1024 x 1024 bytes 1024 x 1024 bytes 1024 bytes

Chapter 1: Implementation Overview

13

If you plan to use a large-sized array LUN that is close to the maximum capacity that Data ONTAP supports, ensure that the size you specify does not exceed the size shown in the Maximum usable value column in the following tables. Note Storage arrays vary as to how you can specify array LUN size (that is, in GB, MB, or 512-byte blocks). Do not create array LUNs that are smaller than the minimum LUN size shown in the V-Series Support Matrix. See the V-Series Installation Requirements and Reference Guide for guidelines about the implications of different size array LUNs on Data ONTAP storage. Values for Data ONTAP 7.3.3 and later in the 7.3 family and 8.0 and later in the 8.0 family: If you are specifying in... GB MB 512-byte blocks Maximum usable value 1,952 GB 1,950,000 MB 4,095,000,000 512-byte blocks

Values for Data ONTAP 7.2.4 and later in the 7.2.x family; and 7.3, 7.3.1, and 7.3.2 in the 7.3.x family: If you are specifying in... GB MB 512-byte blocks Maximum usable value 976 GB 975,000 MB 2,047,500,000 512-byte blocks

Values for Data ONTAP 7.2.3: If you are specifying in... GB MB 512-byte blocks Maximum usable value 732 GB 749,000 MB 1,535,500,000 512-byte blocks

14

Guidelines for array LUN sizing

Values for Data ONTAP 7.2.2 and earlier: If you are specifying in... GB MB 512-byte blocks Maximum usable value 488.281 GB 500,000 MB 1,024,000,000 512-byte blocks

Best practice logical device size recommendation

Creating one large logical device or metavolume from multiple hypervolumes spanning multiple disks is recommended.

Chapter 1: Implementation Overview

15

16

Guidelines for array LUN sizing

Supported Configurations
About this chapter

This chapter discusses the supported configurations for all supported EMC Symmetrix storage arrays. Use the configurations in this chapter as guidelines for connecting your V-Series system to your storage array and setting up zoning.

Topics in this chapter

This chapter discusses the following topics:

Your guide to interpreting the illustrations on page 18 Direct-attached configurations on page 20 Simple fabric-attached configuration on page 23 Fabric-attached configurations that optimize performance on page 25

About the examples in this chapter

The examples in this chapter show Symmetrix DMX800 storage arrays. The number of host (channel) directors and director ports varies between different storage array models.

Chapter 2: Supported Configurations

17

Your guide to interpreting the illustrations

How redundant paths and port pairs are shown

Illustration of redundant paths and port pairs for storage arrays: In each illustration in this chapter, the port pairs on the storage array are shown in relation to the array LUNs mapped to the port, with the ports on alternate channel directors and FEBE Boards. Note You might choose to use more host (channel) director ports than are shown in the illustrations in this chapter.

Channel Director 15
D1 D0 C1 C0

Channel Director 1
D1 D0

LUNs 1-10

C1 C0

D1 D0 C1

D1 D0 C1

Channel C0 Director 16 FEBE Board 1

Channel Director 2 C0 DMX800 FEBE Board 0

Note For simplicity, the following illustration does not show the back-end target ports A0, A1, B0, and B1. See the V-Series Installation Requirements and Reference Guide for rules for setting up redundant ports and examples of valid and invalid configurations. Illustration of redundant paths and port pairs for the V-Series systems: On some V-Series models, the FC initiator ports are on cards. On other models, the FC initiator ports are onboard ports and are labeled 0a, 0b, and so on. Redundancy is achieved on the V-Series system because each port in a pair

18

Your guide to interpreting the illustrations

is on a different bus or on a different card. (For more information about selecting redundant ports on the different V-Series models with onboard FC initiator ports, see the V-Series Installation Requirements and Reference Guide) The following illustration shows a V6000 model, which has both onboard FC initiator ports and cards. In this example, two different redundant port pairs are used on the V-Series system. To use multiple V-Series port pairs to access LUNs on a storage array, as shown in the illustration, each port in a V-Series port pair must access a different fabric.

0a

0b

0c

0d

0e

0f

0g

0h

FC initiator port pair to a LUN set over two independent fabrics FC initiator port pair to a different LUN set over two independent fabrics

The following illustration shows a redundant port pair on a V-Series model that uses cards.

FC port 1A

FC port 2A

1B

2B

One port on each of two different cards is configured to ensure redundancy to the port pair on the storage array. Then, if one card fails, the port on the other card is used. You can use either port on a card. Note The illustration shows two cards, one with FC initiator ports 1A and 1B and the other with FC initiator ports 2A and 2B. The number represents the slot.

Chapter 2: Supported Configurations

19

Direct-attached configurations

Requirement for direct-attached configurations

In a direct-attached V-Series HA pair, one port pair per node is required. You avoid a single point of failure by creating a redundant port pair. Then, if one path from a V-Series node fails, the other path from the node is used; takeover does not occur. (The way you create a redundant port pair differs according to V-Series model.) For models with adapters, choose one port from each adapter. For models with onboard ports, choose one port from each bus. See the Installation Requirements and Reference Guide for more information.

Direct-attached with one 4-port LUN group

The following illustration shows a deployment with a V-Series HA pair that is directly connected to a DMX800 storage array. The number of host (channel) directors and ports and their layout on the storage array might vary between storage array models. In this configuration, four front-end target ports are used to connect to the V-Series systems. The logical devices are mapped to the D1 port on Channel Directors 1, 2, 15, and 16. For redundancy, each V-Series FC initiator port is connected to a separate target port, with each of the target ports on a different channel director (as this example shows). This is a best practice recommendation. Note For simplicity, the following illustration does not show the back-end target ports A0, A1, B0, and B1.

20

Direct-attached configurations

vs1
0a 0b 0c 0 d

vs2
0a 0b 0c 0d

Channel Director 15
D1 D0 C1 C0

Channel Director 1
D1 D0

LUNs 1-10

C1 C0

D1 D0 C1

D1 D0 C1

Channel C0 Director 16 FEBE Board 1

Channel Director 2 C0 DMX800 FEBE Board 0

Direct-attached with two 4-port LUN groups

This direct-attached configuration example provides additional port bandwidth because it uses eight front-end target ports to connect to the V-Series systems instead of the four ports shown in the previous configuration example. To implement this type of configuration, the logical devices are mapped as follows:

Half of the logical devices for the V-Series systems are mapped to four frontend target ports (D1), one on each of Channel Directors 1,2, 15, and 16.
21

Chapter 2: Supported Configurations

The other half of the logical devices are mapped to four other front-end target ports (D0), one on each of Channel Directors 1,2, 15, and 16.

Attention In this type of configuration, do not map all DMX logical devices to all connected target ports.

vs1
0a 0b 0c 0 d

vs2
0a 0b 0c 0d

Channel Director 15
D1 D0 C1 C0

Channel Director 1

LUNs 1-5

D1 D0 C1 C0

D1 D0 C1

LUNs 6-10

D1 D0 C1

Channel C0 Director 16 FEBE Board 1

Channel Director 2 C0

DMX800 FEBE Board 0

22

Direct-attached configurations

Simple fabric-attached configuration

HA pair with one 2port LUN group

The following example shows a simple fabric-attached 2-port configuration two front-end target ports are used on the storage array. To ensure availability, use a redundant port pair on each V-Series system (that is, a port from each bus or adapter). Then, if one path from a V-Series node fails, the other path from the node is used; V-Series controller takeover does not occur.
vs1
0a 0b 0c 0 d

vs2
0a 0b 0c 0d

z1

z3

z2

z4

Fabric 1 Switch 1
z1/z2 z3/z4

Fabric 2 Switch 2

Channel Director 15
D1 D0 C1 C0

Channel Director 1

LUNs 1-10

D1 D0 C1 C0

D1 D0 C1

D1 D0 C1

Channel C0 Director 16 FEBE Board 1

Channel Director 2 C0 DMX800 FEBE Board 0

Chapter 2: Supported Configurations

23

Note Best practice recommendation is that you connect all the V-Series FC initiator 0a ports to Fabric 1 and all the V-Series FC initiator 0c ports to Fabric 2. It makes it easier to visualize the deployment if you connect the ports to the fabrics in this manner. Zoning: The following table shows the single-initiator zoning for this example with a V3xxx HA pair. Note Each pair of ports (the FC initiator port on the V-Series system and the channel director target port on the storage array) must be in its own fabric zone so that it cannot see other devices or ports.

Zone Switch 1 z1 z2 Switch 2 z3 z4

V-Series system

Storage array

V-Series system 1 V-Series system 2

Port 0a Port 0a

FEBE Board 1 FEBE Board 1

Channel Director 15 Channel Director 15

Port D1 Port D1

V-Series system 1 V-Series system 2

Port 0c Port 0c

FEBE Board 0 FEBE Board 0

Channel Director 1 Channel Director 1

Port D1 Port D1

24

Simple fabric-attached configuration

Fabric-attached configurations that optimize performance

How performance is optimized

As the examples in this section illustrate, you can optimize performance by spreading the I/O across the Parity RAID groups on the storage array. You set up your configuration so that different port pairs on a V-Series system access different groups of LUNs on the storage array. Different port pairs on a V-Series system accessing different LUN groups on a Symmetrix storage array works because each port on a Symmetrix storage array has its own WWN and, on Symmetrix storage arrays, you map Symmetrix logical devices to ports. The V-Series system sees any given array LUN over only two paths because a given logical device is mapped to only two alternate ports on the storage array. Different LUN groups are accessed through different ports. Each number used to identify a logical device must be unique on the same storage array, but numbers presented to hosts to identify LUNs (external numbers) can be duplicated on different ports. Attention This configuration example of using two port pairs on a V-Series system to access two different device groups on the Symmetrix storage array does not work with all vendors storage arrays. If the configuration is valid for a particular vendors storage arrays, the V-Series Implementation Guide for that vendor includes the configuration example. In the examples in this section, two V-Series port pairs and four target ports on the Symmetrix array are used. Each V-Series port pair sees a different LUN group.

Rules for implementing this type of configuration

To implement this type of configuration, you need to do the following:

On the storage array, use as many ports as possible to provide access to the LUNs that you allocated for V-Series. In this example, half of the Symmetrix logical devices for V-Series are mapped to two front-end target ports (D1) on redundant channel directors and the other half of the Symmetrix logical devices are mapped to two other Symmetrix front-end target ports (D1) on different redundant channel directors.

Chapter 2: Supported Configurations

25

On the V-Series system, use multiple port pairs. Each port pair accesses a different group of LUNs on the Symmetrix storage array through redundant paths. Create one big aggregate (in the Data ONTAP configuration), assigning the array LUNs from multiple Parity RAID groups to the aggregate. By doing so, the I/O is spread across more disks.

The combination of spreading I/O across the Parity RAID groups and creating one large aggregate results in a significant performance boost.

26

Fabric-attached configurations that optimize performance

Stand-alone with two 2-port LUN groups

The following illustration shows a configuration with a stand-alone V6xxx system. One V-Series port pair accesses LUNs in one LUN group on the storage array and a different V-Series port pair accesses LUNs in a different LUN group on the storage array.
vs1
0a 0 b 0 c 0 d 0e 0f 0g 0h

z1

z3

z4

z2

Fabric 1 Switch 1
z3

Fabric 2 Switch 2

z4

Channel Director 15
D1 D0 C1 C0

Channel Director 1

LUNs 1-10

D1 D0 C1 C0

z1
D1 D0 C1

z2

LUNs 11-25

D1 D0 C1

Channel C0 Director 16 FEBE Board 1

Channel Director 2 C0 DMX800 FEBE Board 0

The relationship between the V-Series port pairs, storage array port pairs, and LUN groups is summarized in the following table.

Chapter 2: Supported Configurations

27

Redundant V-Series port pair 0a and 0h

Redundant storage array port pair to which the Symmetrix logical devices are mapped Channel Director 16, port D1 Channel Director 2, port D1

LUN group LUNs 11-15

0c and 0f

Channel Director 15, port D1 Channel Director 1, port D1

LUNs 1-10

Zoning for this stand-alone configuration: The following table shows single-initiator zoning for this example with a V6xxx standalone system. Note Each pair of ports (the FC initiator port on the V-Series system and the channel director target port on the storage array) must be in its own fabric zone so that it cannot see other devices or ports.

Zone Switch 1 z1 z3 Switch 2 z2 z4

V-Series system port

Storage array

0a 0c

FEBE Board 1 FEBE Board 0

Channel Director 16 Channel Director 15

Port D1 Port D1

LUNs 11 - 25 LUNs 1 - 10

0h 0f

FEBE Board 0 FEBE Board 1

Channel Director 2 Channel Director 1

Port D1 Port D1

LUNs 11 - 25 LUNs 1-10

28

Fabric-attached configurations that optimize performance

HA pair with two 4port LUN groups

The following illustration shows a configuration with a V-Series HA pair with V3xxx V-Series systems. On each V-Series system, two V-Series port pairs are used to optimize performance. The V-Series port pairs are as follows.

0a and 0c 0b and 0d

Each V-Series port pair accesses a separate device group on the storage array.
vs1
0a 0b 0c 0 d

vs2
0a 0b 0c 0d

z1 z5 z3 z7

z2 z6

z4 z8

Fabric 1 Switch 1

Fabric 2 Switch 2

Channel Director 15

Channel Director 1

z1
D1

z3
D1

z2
D0 C1 C0

LUNs 1-10
D0 C1 C0

z4

z5
D1

D1

z7 z8

z6

LUNs 11-25
D0 C1 D0 C1

Channel C0 Director 16 FEBE Board 1

Channel Director 2 C0 DMX800 FEBE Board 0

Chapter 2: Supported Configurations

29

The following table summarizes the zoning for this configuration. V-Series system and port

Zone Switch 1 z1 z2 z5 z6 Switch 2 z3 z4 z7 z8

Storage array

vs1-0a vs2-0a vs1-0b vs2-0b

FEBE Board 1 FEBE Board 1 FEBE Board 1 FEBE Board 1

Channel Director 15 Channel Director 15 Channel Director 16 Channel Director 16

Port D1 Port D0 Port D1 Port D0

LUNs 1 - 10 LUNs 1 - 10 LUNs 11 - 25 LUNs 11 - 25

vs1-0c vs2-0c vs1-0d vs2-0d

FEBE Board 0 FEBE Board 0 FEBE Board 0 FEBE Board 0

Channel Director 1 Channel Director 1 Channel Director 2 Channel Director 2

Port D1 Port D0 Port D1 Port D0

LUNs 1 - 10 LUNs 1 - 10 LUNs 11 - 25 LUNs 11 - 25

30

Fabric-attached configurations that optimize performance

Index
A
array LUNs assignment of 11 defined 1, 4 format of LUN IDs 12 gatekeeper 12 maximum number 11 number of paths to 11 requirement for matching IDs 11 restriction for LUN0 11 VCMDB, caution about using 12

H
host director, defined 3 Host Type Format 3, 9 hypervolume, defined 3

L
logical device, defined 3 logical volume, defined 4 LUN 0 restriction for use 11 LUN IDs, requirement for matching 11 LUN, defined 4 LUN0, restriction for use 12 LUNs (array) assignment of 11 defined 1 format of LUN IDs 12 maximum number 11 number of paths to 11 requirement for matching IDs 11 sizing guidelines 13 VCMDB, caution about using 12

C
C-bit Flag 8 channel director defined 2 specifying ports on 11 Common Serial Number flag 8

D
director defined 2 specifying ports on 11 disk director, defined 2

M
metavolume, defined 4

E
ECC, defined 2 EMC ControlCenter, defined 2 Enginuity defined 2

P
Parity RAID group, defined 4 Parity RAID, defined 4 paths to array LUNs number supported 11 requirement for redundant paths 11 Persistent Reservations flag 9 Point-to-Point flag 8 ports access control 9 parameters set per port 7 sharing, recommendation about 10 PP Flag 8
31

F
fabric-attached configuration, zoning 28 Fibre Channel director 3

G
gatekeeper 12 gigabyte, defined 13
Index

R
redundant paths to an array LUN 11

U
Unique World Wide Name 4, 8

S
SC3 Flag 8 SCSI3_persist_reserv 9 SPC-2 Flag 8 supported storage arrays 6 switch-attached configuration, zoning 28 SymmDev, defined 4 Symmetrix storage arrays maximum number of LUNs supported 11

V
VCMDB LUN results of mapping it 12 volumes Data ONTAP, defined 5

Z
zoning example 28 requirements 24, 28

32

Index