V-Series Systems Implementation Guide for Fujitsu ETERNUS Storage

NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 U.S.A. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support telephone: +1 (888) 4-NETAPP Documentation comments: [email protected] Information Web: http://www.netapp.com Part number: 210-04950_A0 June 2010

Copyright and trademark 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 Fujitsu ETERNUS-specific terminology . . . . . . . . . . . . . . . . . . . . . 3 What Data ONTAP supports for Fujitsu storage arrays . . . . . . . . . . . . . 6 Guidelines for array LUN sizing . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2

Configurations Supported with Fujitsu Systems . . . . . . . . . . . . . . 11 Your guide to interpreting the illustrations . . . . . . . . . . . . . . . . . . . 12 Stand-alone configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 HA pair configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 3

Configuring ETERNUS Storage for V-Series . . . . . . . . . . . . . . . . 29 Configuration overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Configuration requirements for ETERNUS3000. . . . . . . . . . . . . . . . 34 Configuration requirements for ETERNUS6000. . . . . . . . . . . . . . . . 36 Configuration requirements for ETERNUS4000, 8000, DX400, and DX8000 37

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

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 Guide

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. This guide is most helpful to users 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 Fujitsu ETERNUS storage arrays.

Topics in this chapter

This chapter discusses the following topics:

Fujitsu ETERNUS-specific terminology on page 3 What Data ONTAP supports for Fujitsu storage arrays on page 6 Guidelines for array LUN sizing on page 7

Generic storage allocation terms 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 seeing or hearing a different term used 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.

Additional information to read

This guide is intended to be used in conjunction with the following additional documents:

V-Series Installation Requirements and Reference Guide This guide contains general guidelines for setting up the storage array to work with the V-Series systems. When planning your deployment, first read this guide, then read the V-Series Implementation Guide for your storage array type. The Implementation Guides provide additional details that are specific to your vendor.

V-Series Support Matrix at http://now.netapp.com This document provides information about Data ONTAP releases that support V-Series, as well as supported switches, supported firmware, capacity, and maximum array LUN count.

Chapter 1: Implementation Overview

Note The Support Matrix is the final authority on the storage array models, storage array firmware, switches, and so on that V-Series supports.

Implementation Overview

Fujitsu ETERNUS-specific terminology

affinity group

In ETERNUS4000, 6000, 8000, DX400, and DX8000 storage arrays, an affinity group is information that maps the array LUNs a host recognizes to the logical volume numbers the storage array manages. Setting a host affinity enables hosts that have a Host World Wide Name (WWN) that was registered with the ETERNUS4000, 6000, 8000, DX400, and DX8000 to access specific linked affinity groups. See Host Affinity group on page 3. Note In ETERNUS3000 storage arrays, the equivalent functionality is provided by configuring the zoning function on the storage array. The ETERNUS3000 zoning function is not the same as switch zoning. See zoning function on page 5 for more information.

Channel Adapters

(CAs) The interfaces (ports) that provide connections between the storage array and hosts. A CA supports Fibre Channel as an external interface. See also FCCA on page 3.

CM

(Controller Module) This module, which is mounted into a controller enclosure of the ETERNUS storage array, has a central role in managing all operations in the storage array. It has three functions: resource management, cache memory management, and communications service.

FC-CA

(Fibre Channel - Channel Adapter) A channel adapter (port) for a Fibre Channel connection.

Host Affinity group

Specifies the access restrictions of HBAs (host bus adapters) and the logical volumes of the ETERNUS storage arrays. You identify the access restrictions for Fibre Channel connections by specifying the WWNs of authorized HBAs. Affinity groups are used with ETERNUS4000, 6000, 8000, DX400, and DX8000 storage arrays.
3

Chapter 1: Implementation Overview

LUN

A logical unit number of one or more disks or disk partitions into one span of disk storage space. On ETERNUS storage arrays, the LUN is the number that the host recognizes. LUN_V is the internal logical unit number managed by the ETERNUS storage array. A LUN has a RAID type and properties that define it. A LUN looks like an individual disk to the V-Series system. A V-Series system or non V-Series host reads data from or writes data to a LUN. V-Series documents use the term array LUN to refer to LUNs on a storage array.

LUN_V

An internal logical volume. The ETERNUS storage arrays use an internal number to identify with the LUN_V. LUN_Vs are carved out of ETERNUS RAID groups (referred to as LUN_Rs).

Reset Group

A CA Reset Group is a group of CAs that are reset concurrently.

RTs

On ETERNUS6000 storage arrays, RTs are routers that connect the Controller Modules (CMs), Channel Adapters (CAs), and Device Adapters (DAs) and provide high-speed communication among them.

volume

ETERNUS definition: On an ETERNUS storage array, the term associated with the concept of a virtual disk, data container, or physical LUN. You carve volumes out of RAID groups. Through LUN mapping, you associate the internal number assigned to the volume to an external numbera LUN numberwhich initiators use to access the volume through a particular FC-CA port (FCP target port). Data ONTAP: ETERNUS 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 Fujitsu ETERNUS volume as a disk.

Fujitsu ETERNUS-specific terminology

zoning function

On ETERNUS3000 storage arrays, a method for mapping logical volumes to array LUNs that can be recognized from a specified host. You can zone logical volumes for every channel adapter for which a host has a standard connection and the logical volume that specified hosts can use. The ETERNUS3000 zoning function is not the same as switch zoning. Note The equivalent function on ETERNUS4000, 6000, 8000, DX400, and DX8000 storage arrays is Host Affinity. See Host Affinity group on page 3.

Chapter 1: Implementation Overview

What Data ONTAP supports for Fujitsu storage arrays

Finding out which Data ONTAP release supports which storage arrays

This guide provides information about 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. See the V-Series Support Matrix at http://now.netapp.com to determine which vendors and storage array models are supported in a particular Data ONTAP release. Note The V-Series Support Matrix is the final authority about which storage arrays that V-Series systems support.

Firmware versions

See the V-Series Support Matrix for information about supported firmware versions. The Support Matrix is the final authority on the firmware versions that V-Series supports.

Required system parameters

See Chapter 3, Configuring ETERNUS Storage for V-Series, on page 29 for information about the required system parameters for your storage array.

What Data ONTAP supports for Fujitsu storage arrays

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 minimum and maximum 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 Fujitsu ETERNUS

Fujitsu ETERNUS 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

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

Maximum usable value 732 GB 749,000 MB 1,535,500,000 512-byte blocks

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

Chapter 1: Implementation Overview

10

Guidelines for array LUN sizing

Configurations Supported with Fujitsu Systems

About this chapter

This chapter discusses the supported configurations for all supported Fujitsu storage arrays. Use the configurations in this chapter as guidelines when you connect your V-Series system to your storage array. You can also refer to the configurations when you determine desired capacity usage, create array LUNs initially, and add array LUNs to your V-Series system. Note The V-Series Support Matrix is the final authority about which configurations that V-Series systems support.

Topics in this chapter

This chapter discusses the following topics:

Your guide to interpreting the illustrations on page 12 Stand-alone configurations on page 15 HA pair configurations on page 16

Chapter 2: Configurations Supported with Fujitsu Systems

11

Your guide to interpreting the illustrations

Variation in the maximum number of array LUNs supported

The maximum number of array LUNs supported for a configuration is limited by the maximum number of array LUNs that a particular V-Series system supports or by the maximum number of array LUNs that a storage array model supports, whichever is less. See the V-Series Support Matrix for information about the number of array LUNs supported by different V-Series systems.

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 on the port, with the ports on alternate Controller Modules (CMs). Note CA-0 in the illustrations represents FC-CA0 and CA-1 represents FC-CA1. Some ETERNUS models label the ports differently than the labels shown in the examples. Be sure to configure ports on alternate CMs to avoid a single point of failure.

CA0

LUNs 1-10

CA0

Controller Module 0

Controller Module 1

See the V-Series Installation Requirements and Reference Guide for additional rules for setting up redundant ports on the V-Series system and examples of valid and invalid path configurations. Illustration of redundant paths and port pairs for the V-Series systems: On V-Series V3000 and V6000 systems, the FC initiator ports are on cards and also on onboard ports, which are labeled 0a, 0b, and so on. As you look through the illustrations, notice that the connections from the V-Series FC initiator ports are set up for redundancy.

12

Your guide to interpreting the illustrations

The following illustration shows a V6000 V-Series system. This example shows the use of two different redundant port pairs. Redundancy is achieved on the V-Series system because each port in a pair is on a different bus.
V-Series system
0a 0b 0c 0d 0e 0f 0g 0h

FC initiator pair to one storage subsystem over two independent fabrics FC initiator pair to a different storage subsystem over two independent fabrics

To use multiple V-Series port pairs with a Fujitsu storage array, you must follow these rules:

Each port in a V-Series port pair must access a different fabric. No more than one port pair on a specific V-Series system can access array LUNs on one storage array. For a V-Series HA pair, one port pair from each V-Series system must be able to see the same array LUNs.

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

FC port 1A

FC port 2A

1B

2B

One port on each of two different adapter 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.

Chapter 2: Configurations Supported with Fujitsu Systems

13

Note The illustrations show two cards, one with FC ports 1A and 1B and the other with FC ports 2A and 2B. The number represents the slot. For more information about selecting redundant ports on the different V-Series systems with onboard FC initiator ports, see the Installation Requirements and Reference Guide.

14

Your guide to interpreting the illustrations

Stand-alone configurations

Fabric-attached stand-alone configuration

The following illustration shows a fabric-attached configuration for a stand-alone V-Series system, with 125 array LUNs allocated for the V-Series system.
V-Series system
0a 0b 0c 0d 0e 0f 0g 0h

z1

z2

Switch 1 z1
CA0

Switch 2 z2 LUNs 1-125

CA0

Storage subsystem CM 0 CM 1

Zoning: The following table shows single-initiator zoning for this example. Single-initiator zoning is the recommended zoning strategy. V-Series system port

Zone Switch 1 z1 Switch 2 z2

Storage array

0a

CM 0

Port FC-CA0

0h

CM 1

Port FC-CA0

Chapter 2: Configurations Supported with Fujitsu Systems

15

HA pair configurations

About this section

This section provides examples for fabric-attached HA pairs. This section includes the following examples:

Two ports accessed on a single storage array on page 16 Two ports accessed on each storage arrayLayout 1 on page 18 Two ports accessed on each storage arrayLayout 2 on page 20 Four ports accessed on a single storage array Layout 1 on page 22 Four ports accessed on a single storage arrayLayout 2 on page 24 Four ports accessed on each storage array on page 26

Two ports accessed on a single storage array

This is an example of a fabric-attached HA pair in which the V-Series nodes share the two (redundant) storage array ports. This configuration uses the fewest number of ports that are possible for V-Series. This configuration is useful if the number of storage array ports or switch ports that you can use with V-Series is limited.

16

HA pair configurations

Cluster interconnect cables V-Series system 1

0a 0b 0c 0d

V-Series system 2
0a 0b 0c 0d

z1

z3

z2

z4

Switch 1

Switch 2

z1/z2
CA0

z3/z4 LUNs 1-125

CA0

Storage subsystem CM 0 CM 1

To ensure availability, use a redundant port pair on each V-Series system (that is, one connection from each adapter on a V-Series system if you are using cards or a port from each bus if you are using onboard ports). 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.

Chapter 2: Configurations Supported with Fujitsu Systems

17

Zoning: The following table shows single-initiator zoning for this example with a V3000 HA pair. Single-initiator zoning is the recommended zoning strategy. Zone Switch 1 z1 z2 Switch 2 z3 z4 V-Series system 1 V-Series system 2 Port 0c Port 0c CM 1 CM 1 Port FC-CA0 Port FC-CA0 V-Series system 1 V-Series system 2 Port 0a Port 0a CM 0 CM 0 Port FC-CA0 Port FC-CA0 V-Series system Storage array

Two ports accessed on each storage arrayLayout 1

This is an example of a layout in which the V-Series nodes connect to two different storage arrays. The two storage arrays can be from the same vendor or from different vendors. You might want to use this type of layout if you need to use some V-Series FC initiator ports as targets (for example, to use the port pair 0b and 0d for FCP). In this example, the solid connection lines represent Fabric 1 and the dashed connection lines represent Fabric 2. FC initiator ports 0a and 0c are a port pair; any array LUN seen on port 0a is also seen on port 0c.

18

HA pair configurations

Cluster interconnect cables V-Series system 1

0a 0b 0c 0d

V-Series system 2
0a 0b 0c 0d

z1/z5 Fabric 1 Switch 1 z1/z2

z3/z7

z2/z6

z4/z8 Fabric 2 Switch 2

z3/z4

z5/z6
CA0 CA0

z7/z8 LUNs 1-125

CA1 CA1

Storage subsystem 1

CM 0

CM 1

CA0

CA0

LUNs 1-100
CA1 CA1

Storage subsystem 2

CM 0

CM 1

Zoning: The following table shows single-initiator zoning for this example with a V3000 HA pair. Single-initiator zoning is the recommended zoning strategy.

Chapter 2: Configurations Supported with Fujitsu Systems

19

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

V-Series system

Storage array

V-Series system 1 V-Series system 2 V-Series system 1 V-Series system 2

Port 0a Port 0a Port 0a Port 0a

1 1 2 2

CM 0 CM 0 CM 0 CM 0

Port CA0 Port CA0 Port CA0 Port CA0

V-Series system 1 V-Series system 2 V-Series system 1 V-Series system 2

Port 0c Port 0c Port 0c Port 0c

1 1 2 2

CM 1 CM 1 CM 1 CM 1

Port CA0 Port CA0 Port CA0 Port CA0

Two ports accessed on each storage arrayLayout 2

This example is similar to Two ports accessed on each storage arrayLayout 1 on page 18, but in this example two port pairs are used on each V-Series node. To use multiple V-Series port pairs with a Fujitsu storage array, you must follow these rules:

Each port in a V-Series port pair must access a different fabric. No more than one port pair on a specific V-Series system can access array LUNs on one storage array. For a V-Series HA pair, one port pair from each V-Series system must be able to see the same array LUNs.

The two storage arrays can be from the same vendor or from different vendors.

20

HA pair configurations

In this example, the V-Series port pair 0a and 0c (the solid lines) connects to one storage array. Any array LUN seen on 0a is also seen on 0c on the other fabric. The V-Series port pair 0b and 0d (the dashed lines) connects to the other storage array. Any array LUN seen on 0b is also seen on 0d on the other fabric.

Cluster interconnect cables V-Series system 1

0a 0b 0c 0d

V-Series system 2
0a 0b 0c 0d

z1 z5 Fabric 1 Switch 1

z3

z7

z2 z6

z4

z8 Fabric 2 Switch 2

z1/z2

z3/z4

z5/z6
CA0 CA0

z7/z8 LUNs 1-125

CA1 CA1

Storage subsystem 1

CM 0

CM 1

CA0

CA0

LUNs 1-100
CA1 CA1

Storage subsystem 2

CM 0

CM 1

Zoning: The following table shows single-initiator zoning for this example with a V3000 HA pair. Single-initiator zoning is the recommended zoning strategy.

Chapter 2: Configurations Supported with Fujitsu Systems

21

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

V-Series system

Storage array

V-Series system 1 V-Series system 2 V-Series system 1 V-Series system 2

Port 0a Port 0a Port 0b Port 0b

1 1 2 2

CM 0 CM 0 CM 0 CM 0

Port CA0 Port CA0 Port CA0 Port CA0

V-Series system 1 V-Series system 2 V-Series system 1 V-Series system 2

Port 0c Port 0c Port 0d Port 0d

1 1 2 2

CM 1 CM 1 CM 1 CM 1

Port CA0 Port CA0 Port CA0 Port CA0

Four ports accessed on a single storage array Layout 1

The following illustration shows an example of a fabric-attached HA pair in which the V-Series nodes access array LUNs through four (redundant) ports on the storage array. Connections between the switch and the storage array: In this layout, there is a straight connection from the storage array to the switch. (Compare this layout with the connections in Four ports accessed on a single storage array Layout 2 on page 24.)

22

HA pair configurations

Utilization of devices: In this layout, the following occurs with device failure:

If a switch fails, all traffic goes to the same CM. For example, if Switch 1 fails, the path from FC initiator port 0a on both V-Series systems is unavailable. Therefore, all traffic goes from FC initiator port 0c to CM 1. No traffic can go to CM 0.

If a controller fails, all traffic goes through the same switch. For example, if CM 1 fails, traffic goes from V-Series system 1 port 0a and V-Series system 2 port 0a through Switch 1. No traffic can go through Switch 2.

See Four ports accessed on a single storage arrayLayout 2 on page 24 for an example that provides better utilization of the devices than this layout if a switch or a CM on the storage array becomes unavailable.
Cluster interconnect cables V-Series system 1
0a 0b 0c 0d

V-Series system 2
0a 0b 0c 0d

z1 Fabric 1 Switch 1 z1 z2
CA0

z3

z2

z4 Fabric 2 Switch 2

z3 z4
CA0

LUNs 1-125
CA1 CA1

Storage subsystem CM 0 CM 1

Chapter 2: Configurations Supported with Fujitsu Systems

23

Zoning: The following table shows single-initiator zoning for this example with a V3000 HA pair. Single-initiator zoning is the recommended zoning strategy. Zone Switch 1 z1 z2 Switch 2 z3 z4 V-Series system 1 V-Series system 2 Port 0c Port 0c CM 1 CM 1 Port CA0 Port CA1 V-Series system 1 V-Series system 2 Port 0a Port 0a CM 0 CM 0 Port CA0 Port CA1 V-Series system Storage array

Four ports accessed on a single storage arrayLayout 2

The following illustration shows another example of a fabric-attached HA pair in which the V-Series nodes access array LUNs through four (redundant) ports on the storage array. Connections between the switch and the storage array: In this layout, there is a cross-connection from the storage array to the switch. (Compare this layout with the connections in Four ports accessed on a single storage array Layout 1 on page 22.) Utilization of devices: During maintenance or an outage that causes one path to become unavailable, this layout provides better load balancing and utilization than the layout in Four ports accessed on a single storage array Layout 1 on page 22, as follows. During other circumstances, the two layouts are equal.

When the switch is down, there is better storage array utilization. In this layout, if a switch fails, the traffic is still distributed over two CMs. For example, if Switch 1 fails

The path from V-Series system 1 port 0a to Switch 1 to 1A on CM 0 is unavailable. The path from V-Series system 2 port 0a to 2B on CM 1 is unavailable. There is still a path to each storage array CM through Switch 2.

24

When the storage array CM is down, there is better switch utilization.

HA pair configurations

In this layout, even if a CM fails, the traffic is still sent through both switches. For example, if CM 0 fails

The path from V-Series system 1port 0c to CM 1 is available through Switch 2. The path from V-Series system 2 port 0c to CM 1 is available through Switch 1.
Cluster interconnect cables V-Series system 1
0a 0b 0c 0d

V-Series system 2
0a 0b 0c 0d

z1 Fabric 1 Switch 1 z1 z4
CA0

z3

z2

z4 Fabric 2 Switch 2

z2 z3
CA0

LUNs 1-125
CA1 CA1

Storage subsystem

CM 0

CM 1

Zoning: The following table shows single-initiator zoning for this example with a V3000 HA pair. Single-initiator zoning is the recommended zoning strategy. Zone Switch 1 z1 z2 V-Series system 1 V-Series system 2 Port 0a Port 0a CM 0 CM 1 Port CA0 Port CA0 V-Series system Storage array

Chapter 2: Configurations Supported with Fujitsu Systems

25

Zone Switch 2 z3 z4

V-Series system

Storage array

V-Series system 1 V-Series system 2

Port 0c Port 0c

CM 1 CM 0

Port CA1 Port CA1

Four ports accessed on each storage array

This example is similar to Four ports accessed on a single storage array Layout 1 on page 22. But in this example, the V-Series nodes access array LUNs on two different storage arrays through only two ports on each V-Series node. The two storage arrays can be from the same vendor or from different vendors.

26

HA pair configurations

Cluster interconnect cables V-Series system 1

0a 0b 0c 0d

V-Series system 2
0a 0b 0c 0d

z1/z5 Fabric 1 Switch 1 z1

z3/z7 z2/z6

z4/z8 Fabric 2 Switch 2 z3

CA0

CA0

LUNs 1-125 z2
CA1 CA1

z4

Storage subsystem 1

CM 0

CM 1

z5

CA0

CA0

z7 z8 Storage subsystem 2

LUNs 1-100
CA1 CA1

z6 CM 0 CM 1

Chapter 2: Configurations Supported with Fujitsu Systems

27

Zoning: The following table shows single-initiator zoning for this example with a V3000 HA pair. Single-initiator zoning is the recommended zoning strategy. Zone Switch 1 z1 z2 z5 z6 Switch 2 z3 z4 z7 z8 V-Series system 1 V-Series system 2 V-Series system 1 V-Series system 2 Port 0c Port 0c Port 0c Port 0c 1 1 2 2 CM 1 CM 1 CM 1 CM 1 Port CA0 Port CA1 Port CA0 Port CA1 V-Series system 1 V-Series system 2 V-Series system 1 V-Series system 2 Port 0a Port 0a Port 0a Port 0a 1 1 2 2 CM 0 CM 0 CM 0 CM 0 Port CA0 Port CA1 Port CA0 Port CA1 V-Series system Storage array

28

HA pair configurations

Configuring ETERNUS Storage for V-Series

About this chapter

This chapter provides information about the parameters you must set on the different ETERNUS models for them to work with V-Series systems. The chapter also contains an overview of what you need to do to set up an ETERNUS storage array with V-Series. For details about how to configure ETERNUS storage arrays, see your Fujitsu documentation.

Topics in this chapter

This chapter contains the following topics:

Configuration overview on page 30 Configuration requirements for ETERNUS3000 on page 34 Configuration requirements for ETERNUS6000 on page 36 Configuration requirements for ETERNUS4000, 8000, DX400, and DX8000 on page 37

Chapter 3: Configuring ETERNUS Storage for V-Series

29

Configuration overview

ETERNUS configuration tool

You configure ETERNUS storage arrays through ETERNUSmgr.

Configuration overview

The following table provides the high-level steps for setting up a Fujitsu storage array, switches, and V-Series systems to communicate with each other. The configuration screens and parameters differ among the ETERNUS models. Consult the ETERNUS documentation for your model for details. Step 1 2 Action Determine the storage capacity you need for the V-Series systems. Plan the number and size of the array LUNs for the V-Series systems. See Guidelines for array LUN sizing on page 7 and the V-Series Installation Requirements and Reference Guide for recommendations about array LUN size. 3 Confirm that the firmware on the ETERNUS storage array meets the version level required by the V-Series systems. See the V-Series Support Matrix for information about supported firmware versions. 4 5 On the ETERNUS storage array, create RAID groups if you have not already done so. Create and format logical volumes. Creating a volume on a RAID group and mapping it to a array LUN enables a host to access the volume. A host cannot access a RAID group unless you create logical volumes.

30

Configuration overview

Step 6

Action Set up the interface between the V-Series systems and the ETERNUS storage array so that the V-Series systems can access storage on the ETERNUS storage array. This step includes the following (the management interface varies among different ETERNUS models):

Configuring the parameters for the FC-CA port connections on the ETERNUS storage arrays to work with the V-Series systems, including the following:

Adding a response pattern for the V-Series systems If you are sharing the storage array with V-Series and non V-Series hosts, preventing non V-Series hosts from seeing V-Series array LUNs, as follows: On the ETERNUS4000, 6000, 8000, DX400, and DX8000 models: Enable Affinity Mode On ETERNUS3000 models: Select Host table setting mode

Configuring a Host Response pattern For information about required settings, see About the Host Response pattern on page 33 and the applicable section in this chapter for your ETERNUS model.

Mapping logical volumes to V-Series array LUNs (that is, the mapping between the internal array LUN # on the storage array and the array LUN number, which is the external number) Putting all the FC-CA ports that the V-Series uses into one Reset Group Note Copy the attributes associated with one CA port to the second port, which makes the configuration of the array LUN mapping and host response parameters the same.

Chapter 3: Configuring ETERNUS Storage for V-Series

31

Step 7

Action Install each V-Series system. a. b. c. Rack mount the V-Series system. Make sure the power is connected to the V-Series system and that the console is set up. Power on the V-Series system.

d. Interrupt the boot process by pressing Ctrl-C when you see the following message on the console:
Starting Press CTRL-C for boot menu

e.

Select option Maintenance mode boot on the boot menu. Do not proceed any further with V-Series system installation and setup at this time.

Install the Fibre Channel cables to connect the V-Series system to storage. Connect the cables between the storage array and switches and between the switches and the V-Series systems.

Set up zoning on the switches and verify that communication between the storage array and the switch and the switch and the V-Series systems is working. If you are setting up zoning using Worldwide Port Names (WWNs), the V-Series systems and storage array must be powered on and running Data ONTAP (either in maintenance mode or in normal mode) for the WWNs to be automatically discovered by the switch. On the ETERNUS storage array, collect and register the World Wide Names of the V-Series FC initiator ports that can connect to an ETERNUS CA. Although you can obtain WWNs manually, automatic discovery of the WWNs for the ports reduces the likelihood of errors.

32

Configuration overview

Step 10

Action On the V-Series system, verify that all the ETERNUS array LUNs that were allocated for the V-Series systems are visible to the VSeries system. a. Enter the following command:
disk show -v

b.

Verify that all the array LUNs that were allocated for the VSeries systems are displayed. If you do not see all the array LUNs you expect, wait a short time and then enter the command again. There may be a short delay before the array LUNs are visible over the network.

About the Host Response pattern

The Host Response Pattern controls the following:

The behavior of the ETERNUS system when the queue is full. How the ETERNUS storage array responds to certain inquiry commands. Some hosts connected to an ETERNUS storage array send I/O device recognition data and error codes that are different from the host response that the ETERNUS storage array sends to the host. If this is the case, the following problems can occur:

The host might not recognize the ETERNUS storage array. The host might not properly handle an error on the ETERNUS storage array.

See the information in this chapter about required parameters for your ETERNUS model to work with V-Series.

When you are ready to set up and configure Data ONTAP

You can begin Data ONTAP setup and configuration any time after connecting the storage array and the V-Series system together and assigning array LUNs to the V-Series systems. The software setup documentation describes how to set up and configure Data ONTAP.

Chapter 3: Configuring ETERNUS Storage for V-Series

33

Configuration requirements for ETERNUS3000

Required Host Response parameters for V-Series

You need to change some of the parameters for the Host Response function to ensure that the V-Series system recognizes the ETERNUS3000. You configure the Host Response function through the Host Response Settings screen.

Configuring the Host Response for the ETERNUS3000

To create the new Host Response Pattern for the V-Series system, make a copy of the read-only Host Response Pattern#00 that Fujitsu supplies and change the settings, as necessary, to match the settings in the following table. The other parameters should remain as the default values. Parameter Host Response Name Value name It is recommended that you enter a name that makes it easy to identify the V-Series system, for example, vseries. Response status to host when overloaded Response to inquiry command (Peripheral Qualifier/Peripheral Type) Inquiry Standard Data NACA Function Inquiry Standard Data Version Field Inquiry Command Page 83
Queue Full

Default

Disable

03 (Default) Type 01 & 03

Note This might be set to Type 01 by default. Be sure to change it to Type 01 & 03.

34

Configuration requirements for ETERNUS3000

Parameter Reservation Conflict Response to Test Unit Ready Commands Target Port Group Access Support Response Sense at Firmware Hot Switching

Value
Enable

Disable (default) Disable

Chapter 3: Configuring ETERNUS Storage for V-Series

35

Configuration requirements for ETERNUS6000

Required Host Response parameters for V-Series

You need to change some of the parameters for the Host Response function to ensure that the V-Series system recognizes the ETERNUS6000. You configure the Host Response function through the Set Host Response screen. The following table shows the required settings for the V-Series system to operate with the ETERNUS6000. The other parameters should remain as the default values. Parameter Host Response Name Value name It is recommended that you enter a name that makes it easy to identify the V-Series system, for example, vseries. Response status in overload Byte0 of Inquiry response Inquiry Standard Data Version Response data type for Inquiry PageCode 0x83 Reservation Conflict response for Test Unit Ready Ordered Support Mode Host specific mode Pattern of sense code conversion Value is supplied by the management software.
default (no conversion) Version 03 (default) type 1 + type3

conflict response (default)

Off (default) normal moded (default) default (no conversion)

36

Configuration requirements for ETERNUS6000

Configuration requirements for ETERNUS4000, 8000, DX400, and DX8000

Required Host Response parameters for V-Series

For the V-Series system to operate with the ETERNUS 4000, 8000, DX400, and DX8000, you need to create a new Host Response Pattern and set the parameters as required by the V-Series system. Fujitsu provides Host Response Pattern#00, which is read-only. Attention If you do not change the Host Response setting for the V-Series system, the default pattern is assigned to the V-Series system. The Host Response Profile differs depending on the storage array firmware version. Select one of the following tables for the Host Response Profile that matches your storage array firmware. Host Response Profile parameter settings specification 1: Parameter Host Response Name Value name It is recommended that you enter a name that makes it easy to identify the V-Series system, for example, vseries. Response status to host when overloaded Response to inquiry command (Peripheral Qualifier/Peripheral Type) Inquiry Standard Data NACA Function Inquiry Standard Data Version Field Inquiry Command Page 83
Unit Attention

Default

Disable

03 (Default) Type 01 & 03 (Default)

Chapter 3: Configuring ETERNUS Storage for V-Series

37

Parameter Reservation Conflict Response for Test Unit Ready Asymmetric / Symmetric Logical Unit Access

Value
Normal

Active/Active (Default)

Host Response Profile parameter settings specification 2: Parameter Host Response Name Value name It is recommended that you enter a name that makes it easy to identify the V-Series system, for example, vseries. Command Time-out Interval Load Balance Response Byte-0 of Inquiry Response Inquiry VPD ID Type Inquiry Standard Data Version Reservation Conflict Response for Test Unit Ready Host Specific Mode Asymmetric / Symmetric Logical Unit Access LUN Mapping Changes LUN Capacity Expansion Vendor Unique Sense Code Sense Code Conversion Pattern
Standard (25 seconds) Unit Attention No Conversion (Default) Type1 + Type3 (Default) Version 05 (Default) Normal Response (Default)

Normal Mode (Default) Active/Active (Default)

No Report (Default) No Report (Default) No Report No Conversion (Default)

38

Configuration requirements for ETERNUS4000, 8000, DX400, and DX8000

Index
A
affinity group, defined 3, 5 examples 15 zoning 15, 18, 19, 21, 24, 25, 28 FC-CA, defined 3 firmware versions supported 6, 30 Fujitsu storage array configuration overview 29 configuring storage for V-Series use 29

C
Channel Adapter defined 3 CM defined 3 port setup for redundancy 12 configuration overview 29 configurations direct-attached stand-alone 15 fabric-attached stand-alone 15 Controller Module defined 3 port setup for redundancy 12

G
gigabyte, defined 7

H
HA pair configuration fabric-attached example 16, 22, 24 supported deployments 16 Host Affinity function, defined 3

E
ETERNUS DX400 configuration requirements 37 Host Affinity function 3 ETERNUS DX8000 configuratuion requirements 37 Host Affinity function 3 ETERNUS3000 configuration requirements 34 zoning function 5 ETERNUS4000 configuration requirements 37 Host Affinity function 3 ETERNUS6000 configuration requirements 36 Host Affinity function 3 ETERNUS8000 configuration requirements 37 Host Affinity function 3

L
logical unit number, defined 1 LUN_V, defined 4 LUNs (array) defined 1 sizing guidelines 7 LUNs defined 4

P
paths to LUNs number supported 12

R
redundant paths to a LUN 12 RTs, defined 4

S
system parameters required 6

F
fabric-attached configuration
Index

39

T
terminology Data ONTAP 1 terms 3

volumes (Fujitsu), defined 4

Z
zoning fabric-attached HA pair 18, 19, 21, 24, 25, 28 fabric-attached stand-alone configuration 15 zoning function with ETERNUS3000 5

V
volumes (Data ONTAP), defined 4

40

Index