Vs Implement

Data ONTAP 8.1 V-Series SystemsImplementation Guide for Third-partyStorage

NetApp, Inc.495 East Java DriveSunnyvale, CA 94089 USATelephone: +1 (408) 822-6000Fax: +1 (408) 822-4501Support telephone: +1 (888) 4-NETAPPDocumentation comments: [email protected] Web: http://www.netapp.com

Part number: 215-06259_A0Processed: Tuesday August 23 2011 07:23:09

Release Candidate Documentation—25 August 2011

Contents Subject to Change

Contents

Understanding V-Series and Third-party Storage Implementation ....... 5EMC CLARiiON .......................................................................................... 7

Requirements for configuring EMC CLARiiON arrays with V-Series systems ........ 7

Supported configurations for EMC CLARiiON arrays ............................................... 8

EMC Symmetrix ......................................................................................... 11Requirements for configuring EMC Symmetrix arrays with V-Series systems ....... 11

Supported configurations for EMC Symmetrix storage arrays ................................. 13

Fujitsu ETERNUS ...................................................................................... 17Requirements for configuring Fujitsu ETERNUS storage arrays with V-Series

systems ................................................................................................................ 17

Supported configurations for Fujitsu ETERNUS storage arrays .............................. 19

Hitachi ......................................................................................................... 25Requirements for configuring Hitachi arrays with V-Series systems ....................... 25

Supported configurations for Hitachi storage arrays ................................................. 26

HP EVA ....................................................................................................... 31Requirements for configuring HP EVA storage arrays with V-Series systems ........ 31

Supported configurations for HP EVA storage arrays .............................................. 32

HP XP .......................................................................................................... 35Requirements for configuring HP XP arrays with V-Series systems ........................ 35

Supported configurations for HP XP storage arrays ................................................. 36

IBM .............................................................................................................. 41Requirements for configuring IBM arrays with V-Series ......................................... 41

Supported configurations for IBM storage arrays ..................................................... 42

IBM XIV ...................................................................................................... 49Requirements for configuring IBM XIV storage arrays with V-Series systems ....... 49

Supported configurations for IBM XIV storage arrays ............................................. 49

3PAR ............................................................................................................ 51Requirements for configuring 3PAR arrays with V-Series systems ......................... 51

Supported configurations for 3PAR storage arrays ................................................... 51

Copyright information ............................................................................... 55Trademark information ............................................................................. 57How to send your comments ...................................................................... 59

Table of Contents | 3



Index ............................................................................................................. 61

4 | Data ONTAP 8.1 V-Series Systems Implementation Guide for Third-party Storage



Understanding V-Series and Third-party StorageImplementation

V-Series systems are deployed with a variety of third-party storage arrays. Each supported storagearray has different configuration requirements and supports only certain configurations.

Array configuration requirements

Each third-party storage array might have configuration requirements that must be met in order forthe array to work with the V-Series system. These configuration requirements could include thefollowing:

• Identifying the host name of the V-Series system.• Defining the initiator type that the array is connecting to• Setting failover modes• Setting host and LUN group information• Defining the array port configuration

Supported configurations

Each V-Series deployment with a third-party array is limited to the types of configuration that itsupports. When determining the configuration to implement, you need to answer the followingquestions:

• Which configurations are supported for my third-party array?• Will it be a fabric-attached configuration?• Will it be a direct-attached configuration?• How much storage will be available to the V-Series system?.• Whether the configuration will include a standalone V-Series system, an HA pair, or a

MetroCluster configuration?• Will it be a Cluster-Mode configuration?

Qualification of components in your deployment

The V-Series Support Matrix provides the latest information on hardware models and firmwareversions of switch and storage array products that are currently qualified for use with V-Seriessystems. Not all Data ONTAP releases support the same features, configurations, storage arraymodels, and V-Series models.

The following information in the matrix will help you during the system configuration:

• Whether your V-Series model is supported in the Data ONTAP release that you plan to run.• The maximum and minimum system capacity limits for your V-Series model.

5



• If you want to deploy a MetroCluster, whether MetroCluster is supported for your storage array.• The LUN sizes supported in your configuration.• Whether multiple LUN groups are supported for your storage array.• Which storage array firmware versions are supported.• Whether your storage array supports non-disruptive (live) upgrade of the controller firmware.

Use of Advanced Features with Storage Arrays

V-Series does not support third-party array advanced features unless otherwise specified in the V-Series Support Matrix.

Detailed information about the planning and installation process

The V-Series Installation Requirements and Reference Guide provides an overview of the V-Seriessystem technology and a detailed description of planning and requirements, including the following:

• Supported methods of connection• Pathing requirements and examples• Provisioning array LUNs• LUN security methods• Zoning recommendations• Installation and configuration examples• Installation verification examples

Related information

Data ONTAP documentation on NOW — now.netapp.com/NOW/knowledge/docs/ontap/ontap_index.shtmlV-Series Support Matrix — now.netapp.com/NOW/knowledge/docs/ontap/ ontap_index.shtml




http://now.netapp.com/NOW/knowledge/docs/ontap/ontap_index.shtml



EMC CLARiiON

There are requirements that must be met when configuring storage arrays to interoperate with V-Series systems. These requirements include setting configuration parameters on storage arrays anddeploying only supported configurations.

Requirements for configuring EMC CLARiiON arrays with V-Series systems

Each EMC CLARiiON storage array has required configuration parameters that must be set in orderto successfully interoperate with V-Series systems.

Configuration Requirements

Configuration parameters that must be set on the storage array are listed in the following table:

Parameter Setting

Initiator type CLARiiON Open

Array Com Path Enabled

Failover mode 1

Unit serial number LUN

Host Name User supplied host name and port number.

IP address Unique fake IP address. Be sure that you havenot entered this IP address anywhere else in thestorage array configuration and that it is not anIP address that is present on the network.

Notes on Storage Groups

The EMC CLARiiON CX series of shared storage arrays use Storage Groups to control access todata. A storage group is one or more LUNs within the storage array that can be accessed only by thehost or hosts that you associate with the array LUNs. Each host can see only the array LUNs in thestorage group with which it is associated. Therefore, a host cannot access or modify data in arrayLUNs that are not part of its storage group. The Access Logix software, which runs on each CXseries storage array, enforces the host-to-storage group permissions.

All the V-Series systems in the same neighborhood must be in the same storage group.

7



Supported configurations for EMC CLARiiON arraysOnly specific configurations of EMC CLARiiON storage arrays deployed with V-Series systems aresupported.

Two-port fabric-attached stand-alone configuration

The following illustration shows a fabric-attached configuration with a stand-alone V-Series system.Two ports provide access to array LUNs on the storage array.

vs1

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

Storagearray

LUN group

Switch 1 Switch 2

Two-port fabric-attached HA pair

The following illustration shows a fabric-attached HA pair with two ports providing access to asingle LUN group on the storage array.




vs1 vs2

LUN group

Storagearray

0a 0b 0c 0d 0a 0b 0c 0d

Four ports on a single LUN group

The following illustration shows a fabric-attached HA pair in which the V-Series nodes access asingle LUN group through four ports on the storage array.

Storage

0a 0b 0c 0d 0a 0b 0c 0d

LUNs

Four ports on two LUN groups

The following illustration shows a fabric-attached stand-alone V-Series system accessing two LUNgroups. Each LUN group is accessed through two ports.

EMC CLARiiON | 9



vs1

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

Storagearray

LUN group

LUN group




EMC Symmetrix

There are requirements that must be met when configuring storage arrays to interoperate with V-Series systems running Data ONTAP software. These requirements include setting configurationparameters on storage arrays and deploying only supported configurations.

Requirements for configuring EMC Symmetrix arrays with V-Series systems

Each EMC Symmetrix storage array has required configuration parameters that must be set in orderto successfully interoperate with V-Series systems.

Host Channel Director Port Configuration Requirements

Port configuration requirements are described in the following table:

Parameter (names may differ between GUIand CLI)

Setting

Common SN (Common Serial Number or C-bitparameter)

Enable

PP (Point-to-Point parameter) Enable

SC3 (SCSI-3) Enable

SPC-2 (SCS2_Protocol_version, SCSI PrimaryCommand 2 parameter, or "Allow inquiry datato be compiled to the standard")

Enable (Contains the second-generationdefinition of the basic commands for all SCSIdevices.)

UWN (Unique World Wide Name) Enable

Host Configuration requirements

Host configuration requirements are provided in the following table:

Parameter Setting

Host Type Format Server

SCSI3_persist_reserv (Persistent Reservations) On

11



Notes on LUN security

To eliminate the possibility of a non V-Series system overwriting DMX array LUNs owned by a V-Series system, or the reverse, you must present the DMX logical devices through the host (channel)director ports in one of the following ways:

• Present only the DMX logical devices for V-Series on specific DMX host (channel) director portsthat are dedicated to V-Series use.

• Use LUN masking to associate all DMX logical devices to all host (channel) director ports, butallow only the V-Series FC initiator ports to see the LUNs for V-Series.

Attention:

Do not present the VCMDB to all hosts by default. Configure the global setting to restrictvisibility to the VCMDB unless it has been specifically made visible to a particular host.

If you are setting up a configuration in which you are using multiple array LUN groups for V-Series, set up a separate "host group" for each group of LUNs for V-Series.

Caution about using the VCMDB LUN

For VCMDB (Volume Configuration Management DataBase) to be enabled, the VCMDB LUN mustexist. The VCMDB LUN is a "command" type LUN, not a storage LUN. VCMDB is typicallymapped 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 amessage that the VCMDB LUN is less than the minimum size required, and it marks the VCMDBLUN 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 theV-Series system. V-Seriessystem cannot use a gatekeeper LUN. You cannot assign the gatekeeper LUN to the V-Series systemwith the disk assign command.

Note: A gatekeeper is a Symmetrix logical device, accessible by a host, through which SYMAPIor the ControlCenter agent communicates with the storage array.




Supported configurations for EMC Symmetrix storagearrays

Only specific configurations of EMC Symmetrix storage arrays deployed with V-Series systems aresupported.



vs1

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

Storagearray

LUN group

Switch 1 Switch 2



EMC Symmetrix | 13



vs1

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

Storagearray

LUN group

LUN group

Eight ports on two LUN groups

The following example shows a fabric-attached HA pair with two LUN groups. Each LUN group isaccessed through four array ports.




Storage array

vs1

0a 0b 0c 0d

vs2

0a 0b 0c 0d

LUNs

LUNs

EMC Symmetrix | 15



Fujitsu ETERNUS


Requirements for configuring Fujitsu ETERNUS storagearrays with V-Series systems

Each Fujitsu ETERNUS storage array has required configuration parameters that must be set in orderto successfully interoperate with V-Series systems.

Configuration requirements for DX400, and DX8000

For the V-Series system to operate with the DX400 and DX8000 arrays you need to create a newHost Response Pattern and set the parameters as required by the V-Series system. Fujitsu providesHost Response Pattern#00, which is read-only.

The Host Response Profile differs depending on the storage array firmware version. Select the HostResponse Profile that matches your storage array firmware.

Configuration requirements for DX8400

Host Response Profile specification for DX8400 settings are provided in the following table:

Parameter Setting

Host Response Name Name (V-Series system name)

Command Time-out Interval Standard (25 seconds)

Data Transfer Timer 10 Seconds (default)

Load Balance Response Unit Attention

Byte-0 Inquiry Response No Conversions (default)

Inquiry VPD ID Type Type1 + Type3 (default)

Inquiry Standard Data Version Version 05 (default)

Reservation Conflict Response for Test UnitReady

Normal Response (default)

Asymmetric / Symmetric Logical Unit Access Active/Active (default)

Host Specific Mode Normal Mode (default)

17



Parameter Setting

LUN Mapping Changes No Report (default)

LUN Capacity Expansion No Report (default)

Vendor Unique Sense Code No report (default)

Sense Code Conversion Pattern No Conversion (default)

Configuration requirements for DX400

Host Response Profile specification for DX400 settings are provided in the following table:

Parameter Setting

Host Response Name Name (V-Series system name)

Byte-0 of Inquiry response No conversion (Default)

Inquiry VPD ID Type Type 1 + Type 3

Inquiry Standard Data Version Default (Version 05)

Command Timeout Interval Default (25 sec)

Load Balance Response Default (Unit Attention)

Reservation Conflict Response for Test UnitReady

Default (Normal)

Change Volume Mapping Default (No Report)

Volume Capacity Expansion Default (No Report)

Vendor Unique Sense Code Default (No Report)

Host Specific Mode Default (Normal)

Asymmetric/Symmetric Logical Unit Access Default (Active/Active)

Sense Data Conversion Default (no conversion)




Supported configurations for Fujitsu ETERNUS storagearrays

Only specific configurations of Fujitsu ETERNUS storage arrays deployed with V-Series systems aresupported.


The following illustration shows a fabric-attached configuration for a stand-alone V-Series system.Two ports provide access to array LUNs on the storage array.

vs1

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

Storagearray

LUN group

Switch 1 Switch 2


The following illustration shows a fabric-attached HA pair with two ports providing access to arrayLUNs on the storage array.

Fujitsu ETERNUS | 19



vs1 vs2

LUN group

Storagearray

0a 0b 0c 0d 0a 0b 0c 0d

Two ports on two LUN groups

The following illustration shows a fabric-attached HA pair in which the V-Series nodes access arrayLUNs through four ports on the storage array. Each LUN group is accessed through two ports.




Storage array

vs1

0a 0b 0c 0d

vs2

0a 0b 0c 0d

LUNs

LUNs


The following illustration shows a fabric-attached HA pair in which the V-Series nodes access arrayLUNs through four ports on the storage array.




Storage

0a 0b 0c 0d 0a 0b 0c 0d

LUNs

Fabric-attached configuration that optimizes performance

The following example shows a fabric-attached HA pair with two LUN groups. Each LUN group isaccessed through four array ports.




Storage array

vs1

0a 0b 0c 0d

vs2

0a 0b 0c 0d

LUNs

LUNs




Hitachi


Requirements for configuring Hitachi arrays with V-Seriessystems

There are required system parameters that you must set and considerations to keep in mind whenconfiguring a storage array to interoperate with a V-Series system.

Required system parameters for USP-V and VSP arrays

System parameter settings are provided in the following table:

Parameter Setting

Host type standard or 00

Required system parameters for AMS 200, 500, 1000, 2x00 arrays


Parameter Setting

Mapping mode Enabled

Host group security Enabled

Product ID DF600F

Notes on array LUN formatting

The following notes apply to formatting array LUNS:

• Use quick formatting• Online formatting takes the array LUN that is being formatted completely offline, and the array

LUN does not respond to any SCSI commands.Formatting is performed on one array LUN at a time until all array LUNs are formatted.

• Offline formatting takes the entire storage array offline and the storage array does not respond toany SCSI commands.The array LUNs are formatted six at a time per controller until the formatting is complete.The storage array does not respond until all formatting is complete.

25



• If you are creating array LUNs (for any host) after initial V-Series system setup and you are usingoffline formatting, the V-Series system will panic.Any array LUNs that are mapped to the V-Series system, including array LUNs in the rootvolume, become unavailable until formatting is complete.

Requirements for using disks external to the array

V-Series supports the same storage arrays behind the USP-V and VSP arrays that Hitachi supports(that is, disks external to the array). V-Series assumes that the configuration between the storagearray and the external disks behind it is correct.

Restrictions and best practices recommendations for a deployment with Hitachi storage arrays usingexternal disks are:

• All root volumes and spare core LUNs must be on the storage array (on internal disks).• Do not mix array LUNs from external and internal disks in the same Data ONTAP aggregate.• Do not mix SATA and FC drives in the same aggregate.• There cannot be more than two paths to an array LUN on the external disks from the V-Series

system through the storage array to the external disks.• Checksums:

• Block (BCS) or Zoned (ZCS) for LUNs from drives internal to array.• Block (BCS) only for LUNs from external drives behind the storage array.

Supported configurations for Hitachi storage arraysOnly a specific number of configurations of Hitachi storage arrays deployed with V-Series systemsare supported.






vs1

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

Storagearray

LUN group

Switch 1 Switch 2

Two-port fabric-attached HA Pair


vs1 vs2

LUN group

Storagearray

0a 0b 0c 0d 0a 0b 0c 0d



Hitachi | 27



vs1

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

Storagearray

LUN group

LUN group

Four ports on single LUN group

The following illustration shows a fabric-attached HA pair in which the V-Series nodes access asingle LUN group through four ports on the storage array.

Storage

0a 0b 0c 0d 0a 0b 0c 0d

LUNs

Direct-attached configurations

The following example configurations show direct-attached deployments. Direct-attachedconfigurations are no longer recommended for new deployments. These configurations are shown asa reference for configurations that may already exist in the field.




Not all array models are supported in direct-attached configurations. See the V-Series Support Matrixfor restrictions.

Two-port direct-attached stand-alone configuration

The following illustration shows a direct-attached configuration for a stand-alone V-Series system.Two ports provide access to array LUNs on the storage array.

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

Storagearray

LUN group

Four-port direct-attached HA pair configuration

The following illustration shows a direct-attached HA pair with four ports providing access to arrayLUNs on the storage array.

Hitachi | 29



Storagearray

vs1 vs2

0a 0b 0c 0d 0a 0b 0c 0d

LUN group




HP EVA


Requirements for configuring HP EVA storage arrays with V-Series systems


Required system parameters for HP EVA storage arrays


Parameter Setting

Redundancy All raid levels except RAID0

Preferred path/mode No preference (default)

Host type SUN Solaris

Requirements for multiple array LUN groups

• Switch zoning must define which target ports the V-Series system initiator ports use to accesseach array LUN group.

• You use Hosts to define which array LUN groups are presented to each V-Series system initiatorport.

• Each array LUN group requires one initiator port pair for each V-Series system.

Requirements for configuring the HP Storage Management Server

Sharing V-Series initiator ports and EVA Storage Management Server initiator ports with commonEVA target ports causes compatibility issues in V-Series systems. These issues are seen due to thedifferent host settings for the V-Series and the EVA Storage Management Server initiator ports.

HP recommends that any EVA Storage Management Server that resides in a fabric be configured in aseparate zone from all operating systems.

31



Supported configurations for HP EVA storage arraysOnly a specific number of configurations of HP EVA storage arrays deployed with V-Series systemsare supported.



vs1 vs2

LUN group

Storagearray

0a 0b 0c 0d 0a 0b 0c 0d






vs1

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

Storagearray

LUN group

LUN group

Four ports on each LUN group

The following illustration shows a fabric-attached HA pair with two LUN groups. Each LUN groupis accessed through four array ports.

HP EVA | 33



Storage array

vs1

0a 0b 0c 0d

vs2

0a 0b 0c 0d

LUNs

LUNs




HP XP


Requirements for configuring HP XP arrays with V-Seriessystems

Each HP XP storage array has required configuration parameters that must be set in order tosuccessfully interoperate with V-Series systems.

Required system parameter for HP XP24000 and XP20000

Parameter Setting

Mapping mode Enabled

Host group security Enabled

Product ID DF600F

Host Type Standard or 00

Requirements for using disks external to the XP24000 and XP20000 arrays

V-Series supports the same storage arrays behind the XP24000, XP20000 that HP supports (that is,disks external to the array). V-Series assumes that the configuration between the storage array andthe external disks behind it is correct.

Restrictions and best practices recommendations for a deployment with HP XP storage arrays usingexternal disks are:

• All root volumes and spare core LUNs must be on the storage array (on internal disks).• Do not mix array LUNs from external and internal disks in the same Data ONTAP aggregate.• Do not mix SATA and FC drives in the same aggregate.• There cannot be more than two paths to an array LUN on the external disks from the V-Series

system through the storage array to the external disks.• Checksums:

• Block (BCS) or Zoned (ZCS) for LUNs from drives internal to array.• Block (BCS) only for LUNs from external drives behind the storage array.

35



Notes on configuring ports for all HP XP models

• Only one host group per port is supported.• A host group must include all ports of the V-Series systems in a V-Series neighborhood.

Supported configurations for HP XP storage arraysOnly a specific number of configurations of HP XP storage arrays deployed with V-Series systemsare supported.



vs1

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

Storagearray

LUN group

Switch 1 Switch 2


The following illustration shows a fabric-attached HA pair with two ports providing access to asingle LUN group on the storage array.




vs1 vs2

LUN group

Storagearray

0a 0b 0c 0d 0a 0b 0c 0d


The following illustration shows a configuration with a stand-alone V-Series system. One V-Seriesport pair accesses array LUNs in one LUN group on the storage array and a different V-Series portpair accesses array LUNs in a different array LUN group on the storage array.

vs1

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

Storagearray

LUN group

LUN group

HP XP | 37



Direct-attached configurations

The following example configurations show direct-attached deployments. Direct-attachedconfigurations are no longer recommended for new deployments. These configurations are shown asa reference for configurations that may already exist in the field.




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

Storagearray

LUN group

Four-port direct-attached HA pair

The following illustration shows a direct-attached HA pair with four ports providing access to asingle LUN group on the storage array.




Storagearray

vs1 vs2

0a 0b 0c 0d 0a 0b 0c 0d

LUN group

HP XP | 39



IBM


Requirements for configuring IBM arrays with V-SeriesThere are required system parameters that you must set and considerations to keep in mind whenconfiguring a storage array to interoperate with a V-Series system.

Configuration requirements for DS8xxx storage arrays


Parameter Setting

Host type nseries

Notes on DS8xxx configurations

Consider the following notes when configuring your system:

• Use a single volume group for each LUN group on a DS8xxx storage array to guarantee theDS8xxx array LUNs are consistently presented to all V-Series system initiators that access them.If array LUNs are not consistently presented there is a potential for data corruption.

• When setting up the DS8300 9A2 LPAR (system logical partition) model to interact with V-Series systems, ensure that you set up access to each array LUN so that the redundant paths areboth accessing the same LPAR.

• The number of array LUNs on the DS8xxx storage array that can be allocated to the V-Seriessystem is 256 array LUNs per host group regardless of the number of array LUNS that the V-Series system or the DS8xxx supports. This is a V-Series limitation with DS8xxx storage arrays.

• Multiple LUN group requirements are as follows:

• Switch zoning must define which target ports the V-Series systemFC initiator ports use toaccess each LUN group.

• Volume groups must define which LUN groups are presented to each V-Series systeminitiator port.

• One initiator port pair for each V-Series system system is required for each LUN group.

Configuration requirements for DS3950 and DS5xxx storage arrays


41



Parameter Setting

Host type AIX

Notes on DS3950 and DS5xxx configurations

Multiple LUN group requirements are as follows:

• Switch zoning must define which target ports the V-Series FC initiator ports use to access eachLUN group.

• The host group must define which LUN groups are presented to each V-Series initiator port.• One initiator port pair is required for each LUN group.• All target ports on a controller accessing an individual LUN group must be accessed through the

same switch.

Supported configurations for IBM storage arraysOnly a specific number of configurations of IBM storage arrays deployed with V-Series systems aresupported.



vs1

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

Storagearray

LUN group

Switch 1 Switch 2






vs1 vs2

LUN group

Storagearray

0a 0b 0c 0d 0a 0b 0c 0d


The following illustration shows a configuration with a fabric-attached HA pair accessing two LUNgroups with each LUN group accessed through two ports on the storage array.

IBM | 43



Storage array

vs1

0a 0b 0c 0d

vs2

0a 0b 0c 0d

LUNs

LUNs


The following illustration shows a fabric-attached HA pair in which the V-Series nodes access arrayLUNs through four ports on the storage array. In this configuration, there is a straight connectionfrom the storage array to the switch.




Storage array

vs1

0a 0b 0c 0d

vs2

0a 0b 0c 0d

LUNs

LUNs



IBM | 45



Storage

0a 0b 0c 0d 0a 0b 0c 0d

LUNs

Direct attached configurations

The following example configurations show direct-attached deployments. Direct-attachedconfigurations are no longer recommended for new deployments. These configurations are show as areference for configurations that may already exist in the field.







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

Storagearray

LUN group

Two-port direct-attached HA pair configuration

The following illustration shows a direct-attached HA pair with two ports providing access to arrayLUNs on the storage array.

Storagearray

vs1 vs2

0a 0b 0c 0d 0a 0b 0c 0d

LUN group

IBM | 47



IBM XIV


Requirements for configuring IBM XIV storage arrays with V-Series systems

There are required system parameters that you must set and considerations to keep in mind whenconfiguring an XIV storage array to interoperate with a V-Series system.

Required system parameter settings


Parameter Setting

Type Default

Host User supplied host name

Cluster User supplied cluster name

Supported configurations for IBM XIV storage arraysOnly a specific number of configurations of IBM XIV storage arrays deployed with V-Series systemsare supported.



49



Storage

0a 0b 0c 0d 0a 0b 0c 0d

LUNs

Note:

You can use a single port from 4 different interface modules, instead of 2 ports from 2 interfacemodules, to create a similar configuration.




3PAR


Requirements for configuring 3PAR arrays with V-Seriessystems


Required 3PAR system parameters

For 3PAR arrays with firmware version 2.3.1 and later, the required host persona value must be set tothe following value:

Connection type Host persona

Direct Connect 10

Fabric attached 10

For 3PAR arrays with firmware version 2.2.x, the required port persona value must be set to thefollowing value:

Connection type Port persona

Direct Connect 18

Fabric attached 19

Supported configurations for 3PAR storage arraysOnly a specific number of configurations of 3PAR storage arrays deployed with V-Series systems aresupported.



51



Storage

0a 0b 0c 0d 0a 0b 0c 0d

LUNs

Direct attached configurations

The following example configuration shows a direct-attached deployment. Direct-attachedconfigurations are no longer recommended for new deployments. These configurations are show as areference for configurations that may already exist in the field.







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

Storagearray

LUN group

3PAR | 53



Copyright information

Copyright © 1994–2011 NetApp, Inc. All rights reserved. Printed in the U.S.A.

No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in anelectronic retrieval system—without prior written permission of the copyright owner.

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

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED 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 notconvey a license under any patent rights, trademark rights, or any other intellectual property rights ofNetApp.

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

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

55



Trademark information

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri,ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, CampaignExpress, ComplianceClock, Cryptainer, CryptoShred, Data ONTAP, DataFabric, DataFort, Decru,Decru DataFort, DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful,gFiler, Go further, faster, Imagine Virtually Anything, Lifetime Key Management, LockVault,Manage ONTAP, MetroCluster, MultiStore, NearStore, NetCache, NOW (NetApp on the Web),Onaro, OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX, SANscreen,SANshare, SANtricity, SecureAdmin, SecureShare, Select, Service Builder, Shadow Tape,Simplicity, Simulate ONTAP, SnapCopy, SnapDirector, SnapDrive, SnapFilter, SnapLock,SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot,SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror,Tech OnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager, VPolicy, WAFL,Web Filer, and XBB are trademarks or registered trademarks of NetApp, Inc. in the United States,other countries, or both.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. A complete and current list ofother IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.

Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/orother countries. Microsoft is a registered trademark and Windows Media is a trademark of MicrosoftCorporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer,RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, andSureStream 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 andshould be treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.

57



http://www.ibm.com/legal/copytrade.shtml

How to send your comments

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

Your feedback is important in helping us to provide the most accurate and high-quality information.If you have suggestions for improving this document, send us your comments by e-mail to [email protected]. To help us direct your comments to the correct division, include in thesubject line the product name, version, and operating system.

You can also contact us in the following ways:

• NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089• Telephone: +1 (408) 822-6000• Fax: +1 (408) 822-4501• Support Telephone: +1 (888) 4-NETAPP

59



mailto:[email protected]

Index2xxx storage array requirements

Hitachi 25, 263PAR

configuration requirements 51fabric-attached configurations 51, 52required system parameters 51standalone configurations 51, 52supported configurations 51, 52

95xxV storage array requirementsHitachi 25, 26

99xx storage array requirementsHitachi 25, 26

A

AMS storage array requirementsHitachi 25, 26

C

configuration requirements3PAR 51EMC CLARiiON 7EMC Symmetrix 11, 12Fujitsu ETERNUS DX400 17, 18Fujitsu ETERNUS DX8000 17, 18Hitachi 25, 26HP XPi 35, 36IBM 41, 42, 49

D

DS4xxx storage arraysconfiguration requirements 41, 42

DS8xxx storage arraysconfiguration requirements 41, 42

E

EMC CLARiiONconfiguration requirements 7fabric-attached configurations 8, 9supported configurations 8, 9using ports in a host group 7

using storage groups 7EMC Symmetrix

configuration requirements 11, 12parameters to set a host 11, 12parameters to set logical devices

LUN access control requirements 11, 12supported storage array configurations 13, 14

F

fabric-attached configurations3PAR 51, 52Fujitsu ETERNUS 19–22Hitachi 26–29HP EVA 32, 33HP XPIBM XIV 49

Fujitsu ETERNUS DX400configuration requirements 17, 18

Fujitsu ETERNUS DX8000configuration requirements 17, 18

Fujitsu ETERNUS storage arraysfabric-attached configurations 19–22HA pair configurations 19–22supported configurations 19–22

Fujitsu ETERNUS3000configuration requirements 17, 18

H

HA configurationsHP XP

HA pair configurationsFujitsu ETERNUS 19–22

Hitachi99xx storage arrays

2xxx storage arrays 25, 26configuration requirements95xxV storage arrays

AMS storage arrays 25, 26fabric-attached configurations 26–29standalone configurations 26–29supported configurations 26–29

host limits 49HP EVA

configuration requirements 31fabric-attached configurations 32, 33

Index | 61



required system parametershost limits 31

requirements for multiple array LUN groups 31standalone configurations 32, 33supported configurations 32, 33

HP XPconfiguration requirements

HP XP XPnnnnn storage arrays 35, 36fabric-attached configurationsHA configurationsstandalone configurationssupported configurations

HP XP XPnnnn storage array requirementsHP XP 35, 36

HP XP XPnnnnn storage array requirementsHP XP 35, 36

IIBM

configuration requirements 41, 42DS4xxx storage arrays

DS5xxx storage arraysDS8xxx storage arrays

ESS storage arrays 41, 42supported configurations 42–47

IBM XIVconfiguration requirements 49fabric-attached configurations 49required system parameters 49standalone configurations 49supported configurations 49

Index Term 25, 26

R

required system parameters3PAR 51host persona 51IBM XIV 49port persona 51

S

standalone configurations3PAR 51, 52Hitachi 26–29HP EVA 32, 33HP XPIBM 42–47IBM XIV 49

storage arraysFujitsu ETERNUS 19–22

supported configurations3PAR 51, 52EMC CLARiiON 8, 9Fujitsu ENTERNUS 19–22HiP XPHitachi 26–29HP EVA 32, 33IBM 42–47IBM XIV 49




Vs Implement

Documents

Transcript of Vs Implement