Configuration Guide for VMware ESX Server Host Attachment

(1)

MK-98RD6716-0

8 Configuration Guide for

VMware™ ESX Server Host Attachment

Hitachi Unified Storage VM

Hitachi Virtual Storage Platform

Hitachi Universal Storage Platform V/VM

Hitachi TagmaStore

®

Universal Storage Platform

Hitachi TagmaStore

®

Network Storage Controller

F

AST

F

IND

L

INKS

Product Version

Getting Help

(2)

ii

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or

mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose

without the express written permission of Hitachi, Ltd. (hereinafter referred to as “Hitachi”) and Hitachi Data

Systems Corporation (hereinafter referred to as “Hitachi Data Systems”).

Hitachi Data Systems reserves the right to make changes to this document at any time without notice and

assumes no responsibility for its use. This document contains the most current information available at the

time of publication. When new or revised information becomes available, this entire document will be updated

and distributed to all registered users.

All of the features described in this document may not be currently available. Refer to the most recent product

announcement or contact your local Hitachi Data Systems sales office for information about feature and

product availability.

Notice: Hitachi Data Systems products and services can be ordered only under the terms and conditions of the

applicable Hitachi Data Systems agreements. The use of Hitachi Data Systems products is governed by the

terms of your agreements with Hitachi Data Systems.

Hitachi is a registered trademark of Hitachi, Ltd. in the United States and other countries. Hitachi Data

Systems is a registered trademark and service mark of Hitachi, Ltd. in the United States and other countries.

All other trademarks, service marks, and company names are properties of their respective owners.

(3)

iii

Preface... v

Intended Audience ...vi

Product Version...vi

Document Revision Level ...vi

Changes in this Revision ... vii

Referenced Documents... vii

Document Organization ... viii

Document Conventions...ix

Convention for Storage Capacity Values ...x

Accessing Product Documentation ...x

Getting Help ...xi

Comments...xi

Overview ... 1-1

About the Hitachi RAID Storage Systems...1-2

About the VMware ESX Server Platform...1-3

Installation and Configuration Roadmap...1-4

Preparing for New Device Configuration ... 2-1

Installation and Configuration Requirements...2-2

Installing the Hitachi RAID Storage System ...2-4

Configuring the Hitachi RAID Storage System ...2-5

Setting the System Option Modes ...2-5

Configuring the Ports ...2-7

Setting the Host Modes and Host Mode Options ...2-8

Configuring the Host Adapters...2-20

Settings for QLogic Adapters ...2-21

Settings for Emulex Adapters...2-21

Connecting the Storage System to the VMware Server ...2-22

(4)

iv Contents

Configuring the New Devices... 3-1

Creating the VMFS Datastores ... 3-2

Adding a Hard Disk to a Virtual Machine... 3-3

Failover and SNMP ... 4-1

Host Failover... 4-2

Path Failover... 4-3

SNMP Remote System Management... 4-4

Troubleshooting ... 5-1

General Troubleshooting ... 5-2

Calling the Hitachi Data Systems Support Center... 5-4

Specifications for Device Types... A-1

Using VMware with Hitachi RAID Storage Systems ... B-1

VMware ESX Server and VirtualCenter Compatibility ... 2

Installing and Configuring VMware... 3

Creating and Managing VMware Infrastructure Components... 4

(5)

Preface

v

Preface

This document describes and provides instructions for installing and

configuring the devices on the Hitachi RAID storage systems for operations in

a VMware™ ESX Server environment. The Hitachi RAID storage system models

include the following:

• Hitachi Unified Storage VM (HUS VM)

• Hitachi Virtual Storage Platform (VSP)

• Hitachi Universal Storage Platform V and VM (USP V/VM)

• Hitachi TagmaStore Universal Storage Platform and Network Storage

Controller (USP/NSC)

Please read this document carefully to understand how to use this product,

and maintain a copy for reference purposes.

This preface includes the following information:

Intended Audience

Product Version

Document Revision Level

Changes in this Revision

Referenced Documents

Document Organization

Document Conventions

Convention for Storage Capacity Values

Accessing Product Documentation

Getting Help

(6)

vi Preface

Intended Audience

This document is intended for system administrators, Hitachi Data Systems

representatives, and authorized service providers who are involved in

installing, configuring, and operating the Hitachi RAID storage systems.

Readers of this document should be familiar with the following:

• Data processing and RAID storage systems and their basic functions.

• The Hitachi RAID storage systems and the User and Reference Guide for

the storage systems.

• The Storage Navigator software for the Hitachi RAID storage systems and

the Storage Navigator User’s Guide.

• The VMware ESX Server operating system and the hardware hosting the

VMware Server system.

• The hardware used to attach the Hitachi RAID storage systems to the

VMware host, including fibre-channel cabling, host adapters, and switches.

Product Version

This document revision applies to the following microcode levels:

• Hitachi Unified Storage VM: 73-01-0x

• Hitachi Virtual Storage Platform: 70-03-01 or later

• Hitachi Universal Storage Platform V/VM: 60-08-02 or later

• Hitachi TagmaStore USP/NSC: 50-09-3x or later

Document Revision Level

Revision Date Description

MK-98RD6716-P August 2008 Preliminary Release

MK-98RD6716-00 October 2008 Initial release, supersedes and replaces MK-98RD6716-P MK-98RD6716-01 July 2010 Revision 1, supersedes and replaces MK-98RD6716-00 MK-98RD6716-02 October 2010 Revision 2, supersedes and replaces MK-98RD6716-01 MK-98RD6716-03 April 2011 Revision 3, supersedes and replaces MK-98RD6716-02 MK-98RD6716-04 August 2011 Revision 4, supersedes and replaces MK-98RD6716-03 MK-98RD6716-05 November 2011 Revision 5, supersedes and replaces MK-98RD6716-04 MK-98RD6716-06 December 2011 Revision 6, supersedes and replaces MK-98RD6716-05 MK-98RD6716-07 September 2012 Revision 7, supersedes and replaces MK-98RD6716-06 MK-98RD6716-08 July 2013 Revision 8, supersedes and replaces MK-98RD6716-07

(7)

Preface

vii

Changes in this Revision

• Updated the URL of the Hitachi Data Systems Portal in the Getting Help

section of the preface.

• Updated the description of host mode option (HMO) 71 (applies to HUS VM

as well as VSP) (Table 2-6).

• Fixed a typographical error in the description of system option mode 808

(Table 2-3).

Referenced Documents

Hitachi Unified Storage VM documents:

• Block Module Hardware User Guide, MK-92HM7005

• Provisioning Guide, MK-92HM7012

• Storage Navigator User Guide, MK-92HM7016

• Storage Navigator Messages, MK-92HM7017

Hitachi Virtual Storage Platform documents:

• Provisioning Guide for Open Systems, MK-90RD7022

• Storage Navigator User Guide, MK-90RD7027

• Storage Navigator Messages, MK-90RD7028

• User and Reference Guide, MK-90RD7042

• Hitachi Dynamic Link Manager™ User’s Guide for VMware, MK-92DLM130

Hitachi Universal Storage Platform V/VM documents:

• LUN Manager User’s Guide, MK-96RD615

• LUN Expansion User’s Guide, MK-96RD616

• Storage Navigator User’s Guide, MK-96RD621

• Virtual LVI/LUN and Volume Shredder User’s Guide, MK-96RD630

• Storage Navigator Messages, MK-96RD633

• User and Reference Guide, MK-96RD635

Hitachi Universal Storage Platform and Network Storage Controller documents:

• Storage Navigator Error Codes, MK-94RD202

• LUN Manager User’s Guide, MK-94RD203

• LUN Expansion and Virtual LVI/LUN User’s Guide, MK-94RD205

• Storage Navigator User’s Guide, MK-94RD206

(8)

viii Preface

Document Organization

The following table provides an overview of the contents and organization of

this document. Click the chapter title in the left column to go to that chapter.

The first page of each chapter provides links to the sections in that chapter.

Chapter Description

Chapter 1, Overview Provides an overview of the Hitachi RAID storage systems, the VMware host, and the host attachment procedure.

Chapter 2, Preparing for New

Device Configuration Describes and provides the requirements and instructions for preparing the Hitachi RAID storage system, VMware host, and other SAN components for the attachment of new storage.

Chapter 3, Configuring the

New Devices Describes and provides the requirements for configuring the new Hitachi RAID storage devices on the VMware host. Chapter 4, Failover and SNMP Provides information about configuring the Hitachi RAID storage

system for failover and SNMP.

Chapter 5, Troubleshooting Provides troubleshooting information for VMware host attachment. Appendix A, Specifications for

Device Types Provides specifications for the device emulation types in the Hitachi RAID storage systems. Appendix B, Using VMware

with Hitachi RAID Storage Systems

Contains reference information to help you implement VMware software with the Hitachi RAID storage systems.

(9)

Preface

ix

Document Conventions

This document uses the following terminology conventions:

Convention Description

Hitachi RAID storage system, storage system

Refers to all models of the Hitachi RAID storage systems unless otherwise noted.

This document uses the following typographic conventions:

Convention Description

Bold Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK.

Italic Indicates a variable, which is a placeholder for actual text provided by the user

or system. Example: copy source-file target-file

Note: Angled brackets (< >) are also used to indicate variables. screen/code Indicates text that is displayed on screen or entered by the user.

Example: # pairdisplay -g oradb

< > angled brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: # pairdisplay -g <group>

Note: Italic font is also used to indicate variables.

[ ] square brackets Indicates optional values. Example: [ a | b ] indicates that you can choose a, b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicates that you must choose either a or b.

| vertical bar Indicates that you have a choice between two or more options or arguments. Examples:

[ a | b ] indicates that you can choose a, b, or nothing. { a | b } indicates that you must choose either a or b.

This document uses the following icons to draw attention to information:

Icon Meaning Description

Note Calls attention to important or additional information.

Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively.

Caution Warns the user of adverse conditions or consequences (for example, disruptive operations).

WARNING Warns the user of severe conditions or consequences (for example, destructive operations).

(10)

x Preface

Convention for Storage Capacity Values

Physical storage capacity values (for example, disk drive capacity) are

calculated based on the following values:

Physical capacity unit Value

1 KB 1,000 (103_{) bytes} 1 MB 1,000 KB or 1,0002_bytes 1 GB 1,000 MB or 1,0003_bytes 1 TB 1,000 GB or 1,0004_bytes 1 PB 1,000 TB or 1,0005_bytes 1 EB 1,000 PB or 1,0006_bytes

Logical storage capacity values (for example, logical device capacity) are

calculated based on the following values:

Logical capacity unit Value

1 block 512 bytes 1 KB 1,024 (210_{) bytes} 1 MB 1,024 KB or 1,0242_bytes 1 GB 1,024 MB or 1,0243_bytes 1 TB 1,024 GB or 1,0244_bytes 1 PB 1,024 TB or 1,0245_bytes 1 EB 1,024 PB or 1,0246_bytes

Accessing Product Documentation

The user documentation for the Hitachi RAID storage systems is available on

the Hitachi Data Systems Portal: https://portal.hds.com. Check this site for

the most current documentation, including important updates that may have

been made after the release of the product.

(11)

Preface

xi

Getting Help

The Hitachi Data Systems customer support staff is available 24 hours a day,

seven days a week. If you need technical support, log on to the Hitachi Data

Systems Portal for contact information: https://portal.hds.com

Comments

Please send us your comments on this document: [email protected].

Include the document title, number, and revision, and refer to specific sections

and paragraphs whenever possible.

(12)

(13)

1

Overview

1-1

Overview

This chapter provides an overview of the Hitachi RAID storage systems, the

VMware host platform, and the installation and configuration activities:

About the Hitachi RAID Storage Systems

About the VMware ESX Server Platform

Installation and Configuration Roadmap

(14)

1-2 Overview

About the Hitachi RAID Storage Systems

The Hitachi RAID storage systems offer a wide range of storage and data

services, including thin provisioning with Hitachi Dynamic Provisioning™

software, application-centric storage management and logical partitioning, and

simplified and unified data replication across heterogeneous storage systems.

These storage systems are an integral part of the Services-Oriented Storage

Solutions architecture from Hitachi Data Systems, providing the foundation for

matching application requirements to different classes of storage and

delivering critical services such as:

• Business continuity services

• Content management services (search, indexing)

• Non-disruptive data migration

• Volume management across heterogeneous storage arrays

• Thin provisioning

• Security services (immutability, logging, auditing, data shredding)

• Data de-duplication

• I/O load balancing

• Data classification

• File management services

The Hitachi RAID storage systems include the following:

• Hitachi Unified Storage VM (HUS VM)

• Hitachi Virtual Storage Platform (VSP)

• Hitachi Universal Storage Platform V and VM (USP V/VM)

• Hitachi TagmaStore Universal Storage Platform and Network Storage

Controller (USP/NSC)

These storage systems provide heterogeneous connectivity to support multiple

concurrent attachment to a variety of host operating systems (OS), including

VMware

®

_{as well as Windows}

®

_{, UNIX}

®

_{, Linux}

®

_{, enabling massive consolidation}

and storage aggregation across disparate platforms. The storage systems can

operate with multi-host applications and host clusters, and are designed to

handle very large databases as well as data warehousing and data mining

applications that store and retrieve terabytes of data.

(15)

Overview

1-3

The Hitachi RAID storage systems are configured with OPEN-V logical units

(LUs) and are compatible with most fibre-channel (FC) host bus adapters

(HBAs) and fibre-channel-over-ethernet (FCoE) converged network adapters

(CNAs) (VSP only). Users can perform additional LU configuration activities

using the LUN Manager, Virtual LVI/LUN (VLL), and LUN Expansion (LUSE)

features provided by the Hitachi Storage Navigator software for the storage

systems.

For more information about storage solutions and the Hitachi RAID storage

systems, please contact your Hitachi Data Systems account team.

About the VMware ESX Server Platform

The VMware ESX Server product is a “bare-metal” hypervisor that partitions

physical servers in multiple virtual machines. Each virtual machine represents

a complete system, with processors, memory, networking, storage and BIOS.

VMware ESX Server enables multiple virtual machines to share physical

resources, run unmodified operating systems and applications, and run the

most resource-intensive applications side-by-side on the same server.

For more information about the VMware ESX Server host platform, see the

VMware user documentation, or contact VMware technical support.

(16)

1-4 Overview

Installation and Configuration Roadmap

Table 1-1 shows the activities that are performed to connect the Hitachi RAID

storage system to the VMware ESX Server host and configure the new logical

devices (LDEVs) on the storage system for operations with the VMware host.

Some activities are performed by the Hitachi Data Systems representative,

while other activities are performed by the user:

• The Hitachi Data Systems representative performs the physical installation

of the Hitachi RAID storage system and connection to the host.

• The user prepares for the installation and configures the new devices, with

assistance from the Hitachi Data Systems representative.

Table 1-1

Installation and Configuration Roadmap

Task

1. Verify that the installation and configuration requirements have been met.

2. Prepare the Hitachi RAID storage system, VMware host, and host adapters for the installation. 3. Connect the Hitachi RAID storage system to the VMware ESX Server host.

4. Configure the new devices for operation with the VMware host. 5. Create and manage the VMware infrastructure components.

(17)

2

Preparing for New Device Configuration

2-1

Preparing for New Device

Configuration

This chapter describes and provides the requirements and instructions for

preparing the Hitachi RAID storage system, VMware host, and other SAN

components for the attachment of new storage.

Installation and Configuration Requirements

Installing the Hitachi RAID Storage System

Configuring the Hitachi RAID Storage System

–

Setting the System Option Modes

–

Configuring the Ports

–

Setting the Host Modes

Configuring the Host Adapters

(18)

2-2

Preparing for New Device Configuration

Installation and Configuration Requirements

Table 2-1 lists and describes the requirements for installing and configuring

the Hitachi RAID storage system on a VMware ESX host server.

Table 2-1

Installation and Configuration Requirements

Item Requirements

Hitachi RAID

storage system The Hitachi Storage Navigator software must be installed and operational. For details, see the Storage Navigator User’s Guide for the storage system.

The Hitachi LUN Manager software on Storage Navigator must be installed and operational. You will use LUN Manager to configure the storage system.

The availability of features and devices depends on the level of microcode

installed on the Hitachi RAID storage system. VMware server

hardware Review the hardware requirements for attaching new storage to the VMware ESX Server host. For details, see the VMware user documentation.

For details about supported VMware server hardware and hardware for host

attachment (for example, cables, hubs, switches), see the Hitachi Data Systems interoperability site: http://www.hds.com/products/interoperability VMware operating

system Verify that the OS version, architecture, relevant patches, and maintenance levels are supported by the Hitachi RAID storage system. See the Hitachi Data Systems interoperability site for details about supported versions:

http://www.hds.com/products/interoperability

Verify that the VMware ESX Server host meets the latest system and software requirements for attaching new storage. For details, see the VMware ESX Server user documentation.

Verify that you have the VMware ESX Server software installation media. VAAI VMware ESX 4.1 or later is required for VAAI operations.

The Hitachi RAID storage systems (USP V/VM and later) support VMware vStorage API for Array Integration (VAAI). VAAI enables the offload of specific storage operations from the VMware ESX host to the Hitachi RAID storage system for improved performance and efficiency. These APIs, available in VMware’s vSphere 4.1, provide integration with the advanced features and capabilities of the Hitachi RAID storage systems such as thin provisioning, dynamic tiering, and storage virtualization. For details, see the following sites:

www.hds.com/go/vmware/

(19)

Preparing for New Device Configuration

2-3

Item Requirements

Host adapters

(HBAs and CNAs) Verify that the adapters are functioning properly. _{HBAs: For OM3 fiber and 200-MB/s data transfer rate, the total cable length} attached to each HBA must not exceed 500 meters (1,640 feet). Do not connect any OFC type connectors to the Hitachi RAID storage system.

CNAs (VSP only): For OM3 fiber and 10-Gb/s data transfer rate, the total

cable length attached to each CNA must not exceed 300 meters (984 feet). The “diskless” VSP model (no internal disk drives or flash drives) does not support the FCoE option.

For details about installing the adapter and using the utilities and tools for the

adapter, see the user documentation for the adapter.

The VMware ESX Server drivers are based on the Emulex-provided lpfcdd-2xx

2.01g driver. This driver has been tested with VMware ESX Server in various fabric configurations. FC-AL configurations are not supported. Point-to-point and direct connections are not supported unless otherwise noted.

For details about supported host adapters, drivers, optical cables, hubs, and switches, see the Hitachi Data Systems interoperability site:

http://www.hds.com/products/interoperability Storage area

network (SAN) A SAN is required to connect the Hitachi RAID storage system to the VMware ESX Server host. VMware does not support FC-AL and direct-connect connections to storage systems. For information about setting up storage arrays for VMware ESX Server, see the VMware user documentation.

For details about supported fibre-channel switches, topology, and firmware

versions for SAN configurations, see the Hitachi Data Systems interoperability site: http://www.hds.com/products/interoperability

(20)

2-4

Preparing for New Device Configuration

Installing the Hitachi RAID Storage System

The Hitachi RAID storage systems come with all the hardware and cabling

required for installation. The Hitachi Data Systems representative follows the

instructions and precautions in the Maintenance Manual for the storage system

when installing the product. The installation tasks include:

• Checking all specifications to ensure proper installation and configuration.

• Installing and assembling all hardware and cabling.

• Verifying that the Storage Navigator software has been installed and is

ready for use. For details, see the Storage Navigator User’s Guide for the

storage system.

• Installing and formatting the logical devices (LDEVs). The user provides the

LDEV configuration information to the Hitachi Data Systems representative,

including the number of OPEN-V devices, LUSE devices, and VLL devices.

For details see the following documents:

–

HUS VM: Provisioning Guide.

–

Hitachi VSP: Provisioning Guide for Open Systems.

–

Hitachi USP V/VM, USP/NSC: LUN Manager User’s Guide, LUN Expansion

User’s Guide, and Virtual LVI/LUN User’s Guide.

Table 2-2 describes the types of logical devices that can be configured on

the Hitachi RAID storage systems for operation with the VMware host

system. For details on the device emulation types, see Appendix A.

Table 2-2

Logical Device Types

Device Type Description

OPEN-V Devices OPEN-V logical units (LUs) are logical devices of variable sizes as defined by the user.

LUSE Devices

(OPEN-V*n) LUSE devices are LUs that are created by combining up to 36 LUs. The LUN Expansion (LUSE) software on Storage Navigator enables you to configure these devices. LUSE devices are designated as OPEN-x*n, where x is the LU type (for example, OPEN-V) and n is the number of combined devices. For example, a LUSE device created from 10 OPEN-V LUs is designated as an OPEN-V*10 device. This enables the host to access the data stored on the storage system using fewer LU numbers.

VLL Devices

(OPEN-V VLL) VLL devices are customized LUs that are configured using the Virtual LVI/LUN software on Storage Navigator. The VLL devices are configured by “slicing” a single LU into several smaller LUs that best fit your application needs to improve host access to frequently used files. VLL devices are designated as OPEN-V-CVS devices, where “CVS” stands for custom volume size.

VLL LUSE Devices

(OPEN-V*n VLL) The VLL LUSE feature allows you to combine Virtual LVI/LUN devices (instead of standard OPEN-V LUs) into LUSE devices. For example, a VLL LUSE device created by using LUSE to combine 10 OPEN-V VLL (OPEN-V-CVS) volumes into a single logical device is designated as an OPEN-V*10-CVS device.

OPEN-x Devices The OPEN-x LUs (for example, OPEN-3, OPEN-9) are logical devices of predefined sizes. The Hitachi RAID storage system supports OPEN-3, OPEN-8, OPEN-9, OPEN-E, and OPEN-L devices. For more information about these device types, contact your Hitachi Data Systems account team.

(21)

Preparing for New Device Configuration

2-5

Configuring the Hitachi RAID Storage System

Complete the following tasks to configure the Hitachi RAID storage system for

attachment to the VMware server:

• Setting the System Option Modes

• Configuring the Ports

• Setting the Host Modes and Host Mode Options

Setting the System Option Modes

To provide greater flexibility, the Hitachi RAID storage systems have additional

operational parameters called system option modes (SOMs) that allow you to

tailor the storage system to your unique operating requirements. The SOMs

are set on the service processor (SVP) by the Hitachi Data Systems

representative.

To set and manage the SOMs

1. Review the complete list of SOMs in the User and Reference Guide for your

storage system.

–

HUS VM Block Module Hardware User Guide, MK-92HM7005

–

Hitachi VSP User and Reference Guide, MK-90RD7042

–

Hitachi USP V/VM User and Reference Guide, MK-96RD635

–

Hitachi USP/NSC User and Reference Guide, MK-94RD231

2. Work with your Hitachi Data Systems team to ensure that the appropriate

SOMs for your operational environment are set on your storage system.

3. Check each new revision of the User and Reference Guide for SOM changes

that may apply to your operational environment, and contact your Hitachi

Data Systems representative as needed.

Table 2-3 lists and describes the SOMs for the VMware environment.

Note: The SOM information may have changed since this document was

published. Contact your Hitachi Data Systems representative for the latest

SOM information.

(22)

2-6

Preparing for New Device Configuration

Table 2-3

SOMs for VMware Host Attachment

SOM Category Storage System Description

808 VMware

VAAI USP V/VM: 60-08-07 or later

Used in combination with host mode option (HMO) 54 to control the ANSI version of Standard Inquiry (2 or 4). Apply this SOM when the USP V/VM is connected with VMware ESXi (5.x or later) and the VAAI function is used.

ON:

SOM 808: ON HMO 54: ON

4 is returned as the ANSI version of Standard Inquiry.

SOM 808: ON HMO 54: OFF

2 is returned as the ANSI version of Standard Inquiry. OFF (default):

SOM 808: OFF HMO 54: ON or OFF

Notes:

1. When HMO 54 is set to OFF, this SOM is disabled, and 2 is returned as the ANSI version regardless of the SOM 808 setting.

2. Since ESX/ESXi 4.1 does not refer to the ANSI version, SOM 808 and HMO 54 can be set without any effect on the ESX/ESXi 4.1 environment.

(23)

Preparing for New Device Configuration

2-7

Configuring the Ports

Before connecting the storage system to the VMware host, you need to

configure the ports on the Hitachi RAID storage system using the LUN Manager

software on Storage Navigator. For instructions on configuring the ports:

• For HUS VM, see the Provisioning Guide.

• For VSP, see the Provisioning Guide for Open Systems.

• For USP V/VM and USP/NSC, see the LUN Manager User’s Guide.

Port address. In fabric environments, the port addresses are assigned

automatically by fabric switch port number and are not controlled by the

storage system port settings. If you plan to connect different types of servers

to the storage system via the same fabric switch, use the zoning function of

the fabric switch.

Topology.

Table 2-4 list and describes the fibre parameter settings for

VMware host attachment. Select the appropriate settings for each port based

on the device to which the port is connected. Determine the topology

parameters supported by the device and port type, and set your topology

accordingly.

For the latest information about port topology configurations supported by

VMware versions and adapter/switch combinations, see the Hitachi Data

Systems interoperability site: http://www.hds.com/products/interoperability.

Note: FC topology with FCoE ports cannot be configured.

Table 2-4

Fibre Parameter Settings

Adapter Fabric Connection Parameter Supported/Not Supported

Fibre-Channel Enable FC-AL Not supported

Enable Point-to-Point Supported

Disable FC-AL Supported

Disable Point-to-Point Not supported

FCoE (VSP storage system only)

Enable FC-AL Not supported

Enable Point-to-Point Not supported

Disable FC-AL Not supported

(24)

2-8

Preparing for New Device Configuration

Setting the Host Modes and Host Mode Options

When you connect multiple server hosts of different platforms to a single port,

you must group server hosts connected to the storage system by host groups

that are segregated by platform. For example, if VMware hosts and Windows

hosts are connected to a single port, you must create a host group for each

platform, register the hosts in the appropriate host group, and then set the

host mode and host mode options for each host group.

While host groups can be created with more than one WWN, it is

recommended that you create one host group for each host adapter and name

the host group the same as the nickname for the adapter. Creating one host

group per adapter provides flexibility and is the only supported configuration

when booting hosts from a SAN. Host groups are created per VMware cluster

or per ESX host on the ports on each storage cluster that the VMware cluster

or ESX hosts can access.

Table 2-5 lists the required host modes for VMware host attachment. Table 2-6

lists the HMOs that can be used for VMware host attachment. For instructions

on creating host groups and setting host modes and HMOs, see the following

manuals:

• For HUS VM, see the Provisioning Guide.

• For VSP, see the Provisioning Guide for Open Systems.

• For USP V/VM and USP/NSC, see the LUN Manager User’s Guide.

Note: The host mode and HMO information may have changed since this

document was published. Contact your Hitachi Data Systems team for the

latest host mode and HMO information.

WARNING:

• Before setting any HMO, review its functionality carefully to determine

whether it can be used for your configuration and environment. If you have

any questions or concerns, contact your Hitachi Data Systems

representative or the Support Center.

• Changing HMOs on a Hitachi RAID storage system that is already installed

and configured is disruptive and requires the server to be rebooted.

(25)

Preparing for New Device Configuration

2-9

Table 2-5

Host Modes for VMware Operations

Storage System Host Mode Comments

HUS VM VSP USP V/VM

01[VMware] If you use host mode 01, you will not be able to create a LUSE volume using a volume to which an LU path has already been defined.

Before performing a LUSE operation on an LDEV with a path defined from a VMware host, make sure that the host mode is 21 (VMware Extension).

21[VMware Extension] Use host mode 21 if you plan to create LUSE volumes. TagmaStore

USP/NSC 0A[NetWare] Use host mode 0A[NetWare] for a USP/NSC storage system attached to a VMware host.

Table 2-6

Host Mode Options for VMware Operations

HMO Storage System Function Host Mode Comments 2 HUS VM VSP USP V/VM USP/NSC Veritas DBE+RAC

(1) The response of Test Unit Ready(TUR) for Persistent Reserve is changed.

(2) According to the SCSI-3 specification, Reservation Conflict is responded to the TUR issued via the path without

Reservation Key registered,

(3) Setting HMO 02 to ON enables the TUR to perform normally, which is issued via the path without Reservation Key registered and to which Reservation Key used to be responded.

Note: HMO 02 is required when the Veritas DBE for Oracle

RAC(I/O Fencing) function is in use.

Common Mandatory. Do not apply this option to Sun Cluster.

7 HUS VM

VSP USP V/VM

Changes the setting of whether to return the Unit Attention response when adding a LUN.

ON: Unit Attention response is returned.

OFF (default): Unit Attention response is not returned.

Sense code: REPORTED LUNS DATA HAS CHANGED

Notes:

1. Set host mode option 07 to ON when you expect the REPORTED LUNS DATA HAS CHANGED UA at SCSI path change.

2. If the Unit Attention report occurs frequently and the load on the host side becomes high, the data transfer cannot be started on the host side and timeout may occur.

3. If both HMO 07 and HMO 69 are set to ON, the UA of HMO 69 is returned to the host.

Common For VSP and HUS VM HMO 7 works regardless of the host mode setting. USP V/VM: 60-01-30-00/00 or later 13 HUS VM VSP USP V/VM USP/NSC

Provides SIM notification when the number of link failures

detected between ports exceeds the threshold. Common Optional _{Configure HMO 13} only when you are requested to do so.

(26)

2-10

Preparing for New Device Configuration

HMO Storage System Function Host Mode Comments 19 USP/NSC

only Select this HMO when registering VMware server hosts in the host group. Reduces the processing time for the reserve command during I/O processing.

Common This function is enabled by default on the HUS VM, VSP, and USP V/VM. USP/NSC: 50-07-66-00/00 or later 22 HUS VM VSP USP V/VM USP/NSC

When a reserved volume receives a Mode Sense command from a node that is not reserving this volume, the host will receive the following responses from the storage system:

ON: Normal Response.

OFF: Reservation Conflict (Default). Notes:

1. By applying HMO 22, the volume status (reserved/non-reserved) is checked more frequently (several tens of milliseconds per LU).

2. By applying HMO 22, the host OS does not receive warning messages when a Mode Select command is issued to a reserved volume.

3. There is no influence to Veritas Cluster Server software when HMO 22 is set OFF. Enable HMO 22 ON when there are numerous reservation conflicts.

4. Set HMO 22 ON when Veritas Cluster Server is connected.

Common USP V/VM: 60-02-52-00/00 or later (within 60-02-5x range) 60-03-2x-00/00 or later USP/NSC: 50-07-66-00/00 or later

24 USP/NSC 16-byte command can be used for accessing an LU larger than 2 TB.

Use this option when you want to switch the operation only for the limited extent, for example, for a certain host group.

ON: Supported (Normal end)

OFF: Not supported (ABEND) (Default) Caution: Host offline required.

Note: When system option mode (SOM) 515 is used in

combination with this HMO, SOM 515 is prioritized.

Common USP/NSC: 50-08-05-00/00 or later

39 HUS VM VSP

USP V/VM

Resets a job and returns UA to all the initiators connected to the host group where Target Reset has occurred.

ON:

Job reset range: Reset is performed to the jobs of all the Initiators connected to the host group where Target Reset has occurred.

UA set range: UA is returned to all the Initiators connected

to the host group where Target Reset has occurred.

OFF (default):

Job reset range: Reset is performed to the jobs of the

initiator that has issued Target Reset.

UA set range: UA is returned to the initiator that has issued

Target Reset.

Note: This option is used in the SVC environment, and the job

reset range and UA set range need to be controlled per host group when Target Reset has been received.

Common USP V/VM: 60-08-01-00/00 or later VSP: 70-02-03-00/00 or later

(27)

Preparing for New Device Configuration

2-11

HMO Storage System Function Host Mode Comments 41 HUS VM VSP USP V/VM

Gives priority to starting Inquiry/ Report LUN issued from the host where this option is set.

ON: Inquiry/ Report LUN is started by priority. OFF (default): The operation is the same as before.

Common USP V/VM: 60-03-24-00/00 or later

48 USP V/VM By setting this option to ON, in normal operation, the pair status of S-VOL is not changed to SSWS even when Read commands exceeding the threshold (1,000/6 min) are issued while a specific application is used.

ON: The pair status of S-VOL is not changed to SSWS if Read

commands exceeding the threshold are issued.

OFF (default): The pair status of S-VOL is changed to SSWS

if Read commands exceeding the threshold are issued.

Note:

1. Set this option to ON for the host group if the transition of the pair status to SSWS is not desired in the case that an application that issues Read commands (*1) exceeding the threshold (1,000/6 min) to S-VOL is used in HAM

environment.

*1: Currently, the vxdisksetup command of Solaris VxVM serves.

2. Even when a failure occurs in P-VOL, if this option is set to ON, which means that the pair status of S-VOL is not changed to SSWS (*2), the response time of Read command to the S-VOL whose pair status remains as Pair takes several msecs.

On the other hand, if the option is set to OFF, the response time of Read command to the S-VOL is recovered to be equal to that to P-VOL by judging that an error occurs in the P-VOL when Read commands exceeding the threshold are issued.

*2: Until the S-VOL receives a Write command, the pair status of S-VOL is not changed to SSWS.

Common USP V/VM: 60-06-10-00/10 or later (within 60-06-1x range) 60-06-21-00/00 or later

(28)

2-12

Preparing for New Device Configuration

Configuration Guide for VMware™ ESX Server Host Attachment

Selects BB_Credit value. (HMO#49: Low_bit)

ON: The subsystem operates with BB_Credit value of 80 or

255.

OFF (default): The subsystem operates with BB_Credit value

of 40 or 128.

*HMO#50/HMO#49: BB_Credit value is decided by 2 bits of the two HMO.

00: Existing mode (BB_Credit value = 40) 01: BB_Credit value = 80

10: BB_Credit value = 128 11: BB_Credit value = 255

Note: This option is applied when the two conditions below

are met:

Data frame transfer in long distance connection exceeds

the BB_Credit value.

System option mode 769 is set to OFF (retry operation is

enabled at TC/UR path creation). VSP, HUS VM:

1. When HMO 49 is set to ON, SSB log of link down is output on MCU (M-DKC) and RCU (R-DKC).

2. This HMO can work only when the micro-program supporting this function is installed on both MCU (M-DKC) and RCU (R-DKC).

3. The HMO setting is only applied to Initiator-Port and RCU Target-Port. This function is only applicable when the 8UFC or 16UFC PCB is used on RCU/MCU.

4. If this option is used, Point to Point setting is necessary. 5. When removing the 8UFC or 16UFC PCB, the operation

must be executed after setting HMO 49 to OFF.

6. If HMO 49 is set to ON while SOM 769 is ON, path creation may fail after automatic port switching.

7. Make sure to set HMO 49 from OFF to ON or from ON to OFF after the pair is suspended or when the load is low. 8. The RCU Target, which is connected with the MCU where

this mode is set to ON, cannot be used for UR.

9. This function is prepared for long distance data transfer. Therefore, if HMO49 is set to ON with distance of 0 km, a data transfer error may occur on RCU side.

USP V/VM:

1. When HMO 49 is set to ON, SSB log of link down is output on MCU (M-DKC).

3. The HMO setting is only applied to Initiator-Port. This function is only applicable when the 8US PCB is used on RCU/MCU.

4. If this option is used, Point to Point setting is necessary. 5. When removing the 8US PCB, the operation must be

executed after setting the HMO 49 to OFF.

9. This function is prepared for long distance data transfer. Therefore, if HMO49 is set to ON with distance of 0 km, a

Common VSP:

70-02-31-00/00 and higher (within 70-02-3x range) 70-02-54-00/00 or later

USP V/VM: 60-07-51-00/00 or later

(29)

Preparing for New Device Configuration

2-13

Configuration Guide for VMware™ ESX Server Host Attachment

Selects BB_Credit value. (HMO#50: High_bit)

ON: The subsystem operates with BB_Credit value of 128 or

255.

OFF (default): The subsystem operates with BB_Credit value

of 40 or 80.

*HMO#50/HMO#49: BB_Credit value is decided by 2 bits of the two HMO.

00: Existing mode (BB_Credit value = 40) 01: BB_Credit value = 80

10: BB_Credit value = 128 11: BB_Credit value = 255

Note: This option is applied when the two conditions below

are met:

Data frame transfer in long distance connection exceeds

the BB_Credit value.

System option mode 769 is set to OFF (retry operation is

enabled at TC/UR path creation). VSP, HUS VM:

4. If this option is used, Point to Point setting is necessary. 5. When removing the 8UFC or 16UFC PCB, the operation

must be executed after setting HMO 50 to OFF.

9. This function is prepared for long distance data transfer. Therefore, if HMO49 is set to ON with distance of 0 km, a data transfer error may occur on RCU side.

USP V/VM:

4. If this option is used, Point to Point setting is necessary. 5. When removing 8US PCB, the operation must be executed

after setting the HMO 50 to OFF.

9. This function is prepared for long distance data transfer. Therefore, if HMO49 is set to ON with distance of 0 km, a

Common VSP:

USP V/VM: 60-07-51-00/00 or later

(30)

2-14

Preparing for New Device Configuration

Configuration Guide for VMware™ ESX Server Host Attachment

Selects operation condition of TrueCopy.

ON: TrueCopy operates in the performance improvement

logic.

(When a WRITE command is issued, FCP_CMD/FCP_DATA is continuously issued while XFER_RDY issued from RCU side is prevented.)

OFF (default): TrueCopy operates in the existing logic. Note: This option is applied when write I/O of TrueCopy is

executed. VSP, HUS VM:

4. When removing 8UFC or 16UFC PCB, the operation must be executed after setting HMO 51 to OFF.

this mode is set to ON, cannot be used for UR. 8. When HMO51 is set to ON using RAID600 as MCU and

RAID700 as RCU, the micro-program of RAID600 must be 07-63-00/00 or higher (within 07-6x range) or 60-08-06-00/00 or higher.

9. Path attribute change (Initiator Port - RCU-Target Port, RCU-Target Port - Initiator Port) accompanied with Hyperswap is enabled after setting HMO51 to ON. If HMO51 is already set to ON on the both paths, HMO51 continues to be applied on the paths even after execution of Hyperswap.

10. In a storage system with maximum number of MPBs (8 MPBs) mounted, HMO051 may need to be used with HMO065. In this case, also see HMO 65.

USP V/VM:

4. When removing 8US PCB, the operation must be executed after setting the HMO 51 to OFF.

this mode is set to ON, cannot be used for UR. 8. When HMO51 is set to ON using RAID600 as MCU and

RAID700 as RCU, the micro-program of RAID600 must be 07-63-00/00 or higher (within 07-6x range) or 60-08-06-00/00 or higher.

9. Path attribute change (Initiator Port - RCU-Target Port,

Common VSP:

USP V/VM: 60-07-51-00/00 or later

(31)

Preparing for New Device Configuration

2-15

HMO Storage System Function Host Mode Comments

52 VSP Enables a function using HAM to transfer SCSI-2 reserve information. If using software for a cluster system that uses a SCSI-2 Reservation, set host mode option 52 on the host groups where the executing node and standby node reside.

ON: The function to transfer SCSI-2 reserve information is

enabled.

OFF (default): The function to transfer SCSI-2 reserve

information is not enabled.

Notes:

1. To use HAM to transfer SCSI-2 reserve information, the cluster middleware (alternate path) on host side must have been evaluated with the function.

2. Set this HMO to ON on both paths of P-VOL and S-VOL to use this function.

Common VSP: 70-03-01-00/00 or later

54 HUS VM VSP

USP V/VM

Enables the EXTENDED COPY (XCOPY) command.

ON: The XCOPY command can be used.

OFF (default): When the XCOPY command is received, Check

Condition is returned as an unsupported command (0x05/0x2000).

Also used in combination with system option mode (SOM) 808 to set the ANSI version of Standard Inquiry (2 or 4):

HMO 54: ON

SOM 808: ON

HMO 54: ON SOM 808: OFF

HMO 54: OFF

SOM 808: ON or OFF

Notes:

1. Set this HMO to ON only when VMWare ESX server is connected and the VAAI function is used.

2. If this HMO is not applied, the VMWare support function, Cloning file blocks, cannot be used.

3. When the Block Zero function is used in the ESXi 5 environment with RAID600 (60-08-07-00/00 and higher), make sure to set HMO 54 and SOM 808 to ON.

x01, x21 VMware ESX/ESXi 4.1 or later with vStorage API for Array Integration (VAAI) function. ESX 4.1 or later VSP: 70-01-42 or later USP V/VM: XCOPY: 60-08-01 or later SOM 808: 60-08-07 or later 57 VSP USP V/VM

Converts the sense code/key that is returned when an S-VOL is accessed. Apply this HMO when the sense code/key response needs to be converted when an old data volume of an HAM pair is accessed.

ON: Sense code/key 05/2500 (LDEV blockage) converted

from 0b/c0000 is returned when SSB=B8A0 is output.

OFF (default): Sense code/key 0b/c0000 is returned when

SSB=B8A0 is output. x01, x21 x0C, x2C ESXi 5 or later VSP: 70-02-03-00/00 or later USP V/VM: 60-08-01-00/00 or later

(32)

2-16

Preparing for New Device Configuration

HMO Storage System Function Host Mode Comments 61 HUS VM VSP

Increases Reservation Keys from 128 to 2,048.

ON: Up to 2,048 Reservation Keys can be allowed per port. OFF (default): 128 Reservation Keys can be allowed per

port.

Notes:

1. HMO 61 is applied when more than 128 Reservation Keys are required in the environment using the Persistent Reserve command.

2. When the option is set to ON, the performance of the Persistent Reserve command and read/write commands may degrade.

3. When the option is switched from ON to OFF, the expanded keys used so far become unavailable.

4. HMO61 setting can be switched from ON to OFF only when SOM864 is ON. To switch OFF from ON, make sure that there is no LU with PGR/Key registered in the target group. 5. If HMO61 is ON, the performance of Persistent Reserve

command and that of I/O for Persistent Reserve LU may degrade.

6. If a host group where HMO61 is ON is deleted and a new host group is created, HMO61 goes OFF. However, if any LU with PGR/Key registered exists in the target group, host group deletion ends abnormally. (Current spec)

7. During micro-program version downgrade, if a HMO61-caused error occurs, HMO61 needs to be set to OFF. 8. Switching HMO61 from ON to OFF while the 129th and

later reservation keys exist may cause the following adverse effects, which may result in server down. - Registered Reservation Keys become invalid.

- The above Reservation Keys suddenly become valid when the option is set to ON again.

9. The 129th and later Reservation Keys can be deleted by the following operations.

- Micro-program exchange from an unsupported version to a supported version.

- Forcible reserve cancellation.

10. HMO61 can be set to OFF in accordance with the following procedure.

Procedure 1: When neither “PGR” nor “KEY” is displayed on the LUN Status window

(1) Set SOM864 to ON (2) Set HMO61 to OFF (3) Set SOM864 to OFF

Procedure 2: When either “PGR” or “KEY” is displayed on the LUN Status window

(1) Release the “PGR” or “KEY” from the host.

(2) Confirm that neither “PGR” nor “KEY” is displayed on the LUN Status window

(3) Set SOM864 to ON. (4) Set HMO61 to OFF (5) Set SOM864 to OFF.

Common VSP: 70-02-03-00/00 or later

(33)

Preparing for New Device Configuration

2-17

Support option for vStorage APIs based on T10 standards. ON:

Standard ANSI Version of inquiry is set to “4”. XCOPY command with T10 specification is enabled.

RCR command is enabled.

The Check response is returned at pool depletion (permanent or temporary).

The Check response is returned when the warning

threshold is exceeded.

UNMAP command is enabled.

OFF (default):

Standard ANSI Version of inquiry is set to “2”. XCOPY command with T10 specification is disabled (as

unsupported command).

RCR command is disabled (as unsupported command). The Check response is not returned at pool depletion

(permanent or temporary).

The Check response is not returned when the warning threshold is exceeded.

UNMAP command is disabled (as unsupported command).

HMO 54 is used for VAAI with ESX 4.1. If HMO 54 and HMO 63 are set to ON, HMO 63 setting is prioritized.

Notes:

1. Apply this HMO when VAAI which complies with SCSI T10 is used in ESXi 5 connection.

2. When this HMO is set to ON for VMware ESXi 5, set SOM 729 to OFF (to respond with 0x7/0x2707 (SPACE ALLOCATION FAILED WRITE PROTECT) while the pool is full). If SOM 729 is set to ON, ESXi 5 may not recognize pool full and may not output the error message.

3. SCSI commands (WriteSame, ATS, XCOPY, UNMAP) issued with VAAI are available only for OPEN-V.

4. XCOPY across storage systems is not supported. To execute Cloning and Storage vMotion across storage systems when ESXi5.0 is connected, set HMO 63 to OFF.

x01, x21 VMware ESXi 5.0 or later with the VAAI function for T10.

VSP: 70-02-54 or later

(34)

2-18

Preparing for New Device Configuration

HMO Storage System Function Host Mode Comments

65 VSP Selects TrueCopy operation mode when the Round Trip function is enabled by setting HMO 051 to ON in the configuration of the maximum number of MPBs.

ON: TrueCopy is performed in enhanced performance

improvement mode of Round Trip.

OFF (default): TrueCopy is performed in existing Round Trip

mode.

Note:

1. The option is applied when response performance for an update I/O degrades while the Round Trip function is used in a configuration of the maximum number of MPBs. 2. When using the option, set HMO 51 to ON.

3. The option can work only when HMO 51 is ON. Refer to the document of HMO 51.

4. When the option is set to ON, SSB logs of link down are output on MCU (M-DKC) and RCU (R-DKC).

5. The option can work only when the micro-program supporting this function is installed on both MCU (M-DKC) and RCU (R-DKC).

6. The option setting is applied to Initiator-Port and RCU Target-Port. The function is applicable only when the PCB type of 8UFC or 16UFC is used on MCU and RCU and in the configuration with 4 sets of MPBs on MCU.

7. Setting change of the option from OFF to ON or from ON to OFF must be done after the pair is suspended or when the load is low.

8. Before downgrading the micro-program from a supported version to an unsupported version, set the option to OFF. (Micro-program exchange without setting the option to OFF is guarded. In this case, setting the option to OFF and then retry the micro-program exchange is required.)

Common 70-03-32-00/00 or later

69 VSP Enables/disables the UA response to a host when an LU whose capacity has been expanded receives a command from the host.

ON: When an LU whose capacity has been expanded receives

a command from a host, UA is returned to the host. Sense key: 0x06 (Unit Attention)

Sense code: 0x2a09 (Capacity Data Has Changed), 0x2a01 (Mode Parameters Changed)

OFF (default): When an LU whose capacity has been

expanded receives a command from a host, UA is not returned to the host.

Note:

1. The option is applied when returning UA to the host after LUSE capacity expansion is required.

2. If both HMO 7 and HMO 69 are set to ON, the UA of HMO 69 is returned to the host.

Common 70-03-36-00/00 or later

(35)

Preparing for New Device Configuration

2-19

Switches sense key/sense code returned as a response to Check Condition when a read/write I/O is received while a DP pool is blocked.

ON: The sense key/sense code returned as a response to

Check Condition when a read/write I/O is received while a DP pool is blocked is 03(MEDIUM

ERROR)/9001(VENDORUNIQUE).

OFF (default): The sense key/sense code returned as a

response to Check Condition when a read/write I/O is received while a DP pool is blocked is 0400(LOGICAL UNIT NOT

READY/CAUSE NOT REPORTABLE).

Note: This option is applied if switching sense key/sense code

returned as a response to Check Condition when a read/write I/O is received while a DP pool is blocked can prevent a device file from being blocked and therefore the extent of impact can be reduced on host side.

Common HUS VM: 73-01-31-00/00 or later VSP: 70-04-01-00/00 or later

(36)

2-20

Preparing for New Device Configuration

Configuring the Host Adapters

Before connecting the Hitachi RAID storage system to the VMware host, you

must configure the adapters (HBAs and/or CNAs) that will be connected to the

storage system. The adapters have many configuration options. The minimum

requirements for configuring host adapters on a VMware host for operation

with the Hitachi RAID storage systems are:

• Queue depth. You may need to change the queue depth value on the host

adapters connected to the Hitachi RAID storage system. If the value is too

high, I/O performance can deteriorate, and when this happens, the Hitachi

RAID storage system reports a queue full status (because the queue depth

exceeds an allowable limit). The system may not operate correctly when

the queue is full and a high value is set.

Table 2-7 specifies the queue depth requirements for the Hitachi RAID

storage systems. Set an appropriate queue depth value according to your

configuration. You can adjust the queue depth later as needed (within the

specified range) to optimize the I/O performance.

Table 2-7

Queue Depth Requirements

Parameter Required Value

Queue depth per LU ≤ 32 per LU

Queue depth per port HUS VM, VSP, USP V/VM: ≤ 2048 per port TagmaStore USP/NSC: ≤ 1024 per port

• BIOS.

Table 2-8 specifies the BIOS requirements for the Hitachi RAID

storage systems.

Table 2-8

BIOS Requirements

Parameter Required Value

Host adapter BIOS Disabled

Connection Fabric point-to-point

In addition to the queue depth and BIOS, other parameters (for example, FC,

fabric) may also need to be set. The following sections provide settings Refer

to the user documentation for the adapter to ensure that all parameters

required for your operational environment are set.

Note: Use the same settings and parameters for all host adapters connected

(37)

Preparing for New Device Configuration

2-21

Settings for QLogic Adapters

Use the setup utility for the QLogic adapter to set the required options. For

details and instructions, see the user documentation for the adapter.

Table 2-9 lists the recommended QLogic adapter settings for Hitachi RAID

storage attached to a VMware host.

For the latest information about QLogic adapters and Hitachi RAID storage

systems, see the QLogic website for Hitachi Data Systems storage:

http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/HitachiDataSys

tems.aspx?companyid=5

Table 2-9

Settings for QLogic Adapters

Parameter Setting

Host Adapter BIOS Disabled

Number of LUNs per target Determined by the number of LUNs in your configuration.

Multiple LUN support is typically for RAID arrays that use LUNs to map drives. The default is 8. If you do not need multiple LUN support, set the number of LUNs to 0.

Enable LIP reset No Enable LIP full login Yes Enable target reset Yes

Connection option Point-to-point only