Configuration Guide for Microsoft Windows Host Attachment

(1)

Configuration Guide for Microsoft

®

Windows

®

_{Host Attachment}

Hitachi Unified Storage VM

Hitachi Virtual Storage Platform

Hitachi Universal Storage Platform V/VM

F

ASTF

IND L

INKS

Product Version

Getting Help

(2)

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)

Preface... v

Intended Audience ...vi

Product Version...vi

Document Revision Level ...vi

Source Documents for this Revision ... vii

Changes in this Revision ... vii

Referenced Documents... vii

Document Conventions... viii

Convention for Storage Capacity Values ... ix

Accessing Product Documentation ...x

Getting Help ...x

Comments...x

Introduction... 1-1

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

Device Types ...1-3

Host Attachment Roadmap ...1-7

Installing the Storage System ... 2-1

Requirements ...2-2

Preparing for Host Attachment ...2-3

Installing the Hitachi RAID Storage System Hardware...2-3

Setting the System Option Modes ...2-4

Installing the LUN Manager Software ...2-4

Setting the Host Modes ...2-5

Setting the Host Mode Options ...2-6

Configuring the Fibre-Channel Ports ...2-17

Port Address Considerations for Fabric Environments ...2-18

Loop ID Conflicts ...2-19

Connecting to the Windows Host ...2-20

(4)

Configuring the Host Adapters ... 2-24

Verifying the Disk and Device Parameters... 2-26

Verifying the Disk I/O Timeout Value (TOV) ... 2-26

Verifying the Queue Depth ... 2-28

Configuring the New Disk Devices... 3-1

Writing the Signatures ... 3-2

Creating and Formatting the Partitions ... 3-5

Verifying File System Operations... 3-10

Verifying Auto-Mount ... 3-13

Changing the Enable Write Caching Option... 3-14

Failover and SNMP Operations... 4-1

Host Failover... 4-2

Path Failover... 4-3

Windows 2008 MPIO Configuration Procedure ... 4-4

Enabling MultiPath IO... 4-4

SNMP Remote System Management... 4-11

Troubleshooting ... 5-1

General Troubleshooting ... 5-2

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

SCSI TID Maps for FC Adapters ... A-1

Creating an Online LUSE Volume ... B-1

Acronyms and Abbreviations

(5)

Preface

This document describes and provides instructions for installing and

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

a Microsoft

®

_Windows

®

_{environment. The Hitachi RAID storage system models}

include the Hitachi Unified Storage VM (HUS VM), Hitachi Virtual Storage

Platform (VSP), and the Hitachi Universal Storage Platform V and Hitachi

Universal Storage Platform VM (USP V/VM).

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 Conventions

Convention for Storage Capacity Values

Getting Help

(6)

Intended Audience

This document is intended for system administrators, Hitachi Data Systems

representatives, and authorized service providers who install, configure, and

operate 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 system and the User and Reference Guide for the

storage system.

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

the Storage Navigator User Guide.

• The Microsoft Windows operating system and the hardware hosting the

Microsoft Windows system.

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

Microsoft Windows host, including fibre-channel cabling, host bus adapters

(HBAs), switches, and hubs.

Product Version

This document revision applies to the following microcode levels:

• Hitachi Unified Storage VM microcode 73-02-0x or later.

• Hitachi Virtual Storage Platform microcode 70-05-1x or later.

• Hitachi Universal Storage Platform V/VM microcode 60-08-01 or later.

Document Revision Level

Revision Date Description

MK-96RD639-P February 2007 Preliminary Release

MK-96RD639-00 May 2007 Initial Release, supersedes and replaces MK-96RD639-P MK-96RD639-01 September 2007 Revision 1, supersedes and replaces MK-96RD639-00 MK-96RD639-02 May 2008 Revision 2, supersedes and replaces MK-96RD639-01 MK-96RD639-03 August 2008 Revision 3, supersedes and replaces MK-96RD639-02 MK-96RD639-04 November 2009 Revision 4, supersedes and replaces MK-96RD639-03 MK-96RD639-05 January 2010 Revision 5, supersedes and replaces MK-96RD639-04 MK-96RD639-06 October 2010 Revision 6, supersedes and replaces MK-96RD639-05 MK-96RD639-07 May 2011 Revision 7, supersedes and replaces MK-96RD639-06 MK-96RD639-08 November 2011 Revision 8, supersedes and replaces MK-96RD639-07 MK-96RD639-10 July 2013 Revision 10, supersedes and replaces MK-96RD639-09

(7)

Changes in this Revision

• Added new host mode option 73 for Dynamic Provisioning with Windows

Server 2012 (

Table 2-2

).

Referenced Documents

Hitachi Unified Storage VM documents:

• User and Reference 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 Universal Storage Platform V/VM documents:

• Storage Navigator Messages, MK-96RD613

• 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

• User and Reference Guide, MK-96RD635

• Hitachi Cross-OS File Exchange User’s Guide, MK-96RD647

(8)

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 the following:

Text in a window or dialog box, such as menus, menu options,buttons, and

labels. Example: On the Add Pair dialog box, click OK.

Text appearing on screen or entered by the user. Example: The -split option. The name of a directory, folder, or file. Example: The horcm.conf file.

Italic Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file

Note: Angle brackets (< >) are also used to indicate variables.

monospace Indicates text that is displayed on screen or entered by the user.

Example: # pairdisplay -g oradb

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

Note: Italic 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.

(9)

Icon Meaning Description

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

Important Provides information that is essential to the completion of a task. Caution Failure to take or avoid a specified action can result in adverse

conditions or consequences (for example, loss of access to data). WARNING Failure to take or avoid a specified action can result in severe conditions

or consequences (for example, loss of data).

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

(10)

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.

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 and number, including the revision level (for

example, -07), and refer to specific sections and paragraphs whenever

possible. All comments become the property of Hitachi Data Systems.

Thank you!

(11)

1

Introduction

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

host attachment:

About the Hitachi RAID Storage Systems

Device Types

(12)

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 provide heterogeneous connectivity to

support multiple concurrent attachment to a variety of host operating systems,

including Windows

®

_{as well as VMware™, UNIX}

®

_{, Linux}

®

_{, and mainframe}

servers, 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.

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 FC-over-ethernet (FCoE) converged network adapters (CNAs).

Users can perform additional LU configuration activities using the LUN

Manager, Virtual LVI/LUN (VLL), and LUN Expansion (LUSE) features provided

by the Storage Navigator software, which is the primary user interface for the

storage systems.

For further information about storage solutions and the Hitachi RAID storage

systems, please contact your Hitachi Data Systems account team.

(13)

Device Types

Table 1-1

describes the types of logical devices (volumes) that can be installed

and configured for operation with the Hitachi RAID storage system on a

Microsoft Windows operating system.

Table 1-2

lists the specifications for

devices supported by the Hitachi RAID storage system. Logical devices are

defined to the host as SCSI disk devices, even though the interface is fibre

channel. For information about configuring devices other than OPEN-V, contact

your Hitachi Data Systems representative.

The sector size for the devices is 512 bytes.

Table 1-1

Logical Devices Supported by the Hitachi RAID storage systems

Device Type Description

OPEN-V Devices OPEN-V logical units (LUs) are disk devices (VLL-based volumes) that do not have a predefined size.

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

LUSE Devices

(OPEN-x*n) LUSE devices are combined LUs that can be from 2 to 36 times larger than standard OPEN-x LUs. Using LUN Expansion (LUSE) remote console software, you can configure these custom-size devices. LUSE devices are designated as OPEN-x*n, where x is the LU type (for example, OPEN-9*n) and 2< n < 36). For example, a LUSE device created from 10 OPEN-3 LUs is designated as an OPEN-3*10 disk device. This lets the host combine logical devices and access the data stored on the Hitachi RAID storage system using fewer LU numbers.

VLL Devices

(OPEN-x VLL) VLL devices are custom-size LUs that are smaller than standard OPEN-x LUs. Using Virtual LVI/LUN remote console software, you can configure VLL devices by “slicing” a single LU into several smaller LUs that best fit your application needs to improve host access to frequently used files. The product name for the OPEN-x VLL devices is OPEN-x-CVS (CVS stands for custom volume size). The OPEN-L LU type does not support Virtual LVI/LUN.

VLL LUSE Devices

(OPEN-x*n VLL) VLL LUSE devices combine Virtual LVI/LUN devices (instead of standard OPEN-x LUs) into LUSE devices. Use the Virtual LVI/LUN feature to create custom-size devices, then use the LUSE feature to combine the VLL devices. You can combine from 2 to 36 VLL devices into one VLL LUSE device. For example, an OPEN-3 LUSE volume created from a0 OPEN-3 VLL volumes is designated as an OPEN-3*10 VLL device (product name OPEN-3*10-CVS).

FX Devices (3390-3A/B/C, OPEN-x-FXoto)

The Hitachi Cross-OS File Exchange (FX) feature allows you to share data across mainframe, UNIX, and PC server platforms using special multiplatform volumes. The VLL feature can be applied to FX devices for maximum flexibility in volume size.

FX devices are not SCSI disk devices, and must be installed and accessed as raw devices. Windows hosts must use FX to access the FX devices as raw devices (no file system, no mount operation).

The 3390-3B devices are write-protected from Windows host access. The Hitachi RAID storage system rejects all Windows host write operations (including fibre-channel adapters) for 3390-3B devices.

The 3390-3A/C and OPEN-x-FXoto devices are not write-protected for Windows host access. Do not execute any write operations on these devices. Do not create a partition or file system on these devices. This will overwrite data on the FX device and prevent the FX software from accessing the device.

For more information about FX, see the Hitachi Cross-OS File Exchange User’s Guide, or contact your Hitachi Data Systems account team.

(14)

Device Type (Note 1) Category (Note 2) Product Name (Note 3) # of Blocks (512 B/blk) # of Cylinders # of Heads # of Sectors per Track Capacity (MB) (Note 4)

OPEN-3 SCSI disk OPEN-3 4806720 3338 15 96 2347

OPEN-8 SCSI disk OPEN-8 14351040 9966 15 96 7007 OPEN-9 SCSI disk OPEN-9 14423040 10016 15 96 7042 OPEN-E SCSI disk OPEN-E 28452960 19759 15 96 13893 OPEN-L SCSI disk OPEN-L 71192160 49439 15 96 34761 OPEN-3*n SCSI disk OPEN-3*n 4806720*n 3338*n 15 96 2347*n OPEN-8*n SCSI disk OPEN-8*n 14351040*n 9966*n 15 96 7007*n OPEN-9*n SCSI disk OPEN-9*n 14423040*n 10016*n 15 96 7042*n OPEN-E*n SCSI disk OPEN-E*n 28452960*n 19759*n 15 96 13893*n OPEN-L*n SCSI disk OPEN-L*n 71192160*n 49439*n 15 96 34761*n OPEN-3 VLL SCSI disk OPEN-3-CVS Note 5 Note 6 15 96 Note 7

OPEN-8 VLL SCSI disk OPEN-8-CVS Note 5 Note 6 15 96 Note 7 OPEN-9 VLL SCSI disk OPEN-9-CVS Note 5 Note 6 15 96 Note 7 OPEN-E VLL SCSI disk OPEN-E-CVS Note 5 Note 6 15 96 Note 7 OPEN-V VLL SCSI disk OPEN-V Note 5 Note 6 15 128 Note 7 OPEN-3*n VLL SCSI disk OPEN-3*n-CVS Note 5 Note 6 15 96 Note 7 OPEN-8*n VLL SCSI disk OPEN-8*n-CVS Note 5 Note 6 15 96 Note 7 OPEN-9*n VLL SCSI disk OPEN-9*n-CVS Note 5 Note 6 15 96 Note 7 OPEN-E*n VLL SCSI disk OPEN-E*n-CVS Note 5 Note 6 15 96 Note 7 OPEN-V*n VLL SCSI disk OPEN-V*n Note 5 Note 6 15 128 Note 7 3390-3A FX otm/mto 3390-3A 5820300 3345 15 116 2844

3390-3B FXmto 3390-3B 5816820 3343 15 116 2844

3390-3C FXotm OP-C-3390-3C 5820300 3345 15 116 2844 FX OPEN-3 FXoto OPEN-3 4806720 3338 15 96 2347

3390-3A VLL FX otm/mto 3390-3A-CVS Note 5 Note 6 15 116 Note 7 3390-3B VLL FXmto 3390-3B-CVS Note 5 Note 6 15 116 Note 7 3390-3C VLL FXotm OP-C-3390-3C-CVS Note 5 Note 6 15 116 Note 7 FX OPEN-3 VLL FXoto OPEN-3-CVS Note 5 Note 6 15 96 Note 7

(15)

1. The availability of specific device types depends on the storage system model and the level of microcode installed on the storage system.

2. The category of a device (SCSI disk or FX) determines its volume usage. Table 1-3 below shows the volume usage for SCSI disk and FX devices.

The SCSI disk devices (OPEN-V, VLL, LUSE, and VLL LUSE) are usually formatted with file systems for Windows

operations.

The FX devices (3390-3A/B/C, and OPEN-x-FXoto) must be installed as raw devices and can only be accessed using

the FX software. Do not partition or create a file system on any device used for FX operations. Do not write a signature on an FX device unless used in an MSCS environment.

3. The command device (used for Command Control Interface (CCI) operations) is distinguished by –CM on the product name (for example, OPEN-3-CM, OPEN-3-CVS-CM). The product name for VLL devices is OPEN-x-CVS, where CVS = custom volume size.

4. This capacity is the maximum size which can be entered using the lvcreate command. The device capacity can sometimes be changed by the BIOS or host bus adapter. Also, different capacities may be due to variations such as 1 MB = 10002_{or 1024}2_bytes.

5. The number of blocks for a VLL volume is calculated as follows:

# of blocks = (# of data cylinders) × (# of heads) × (# of sectors per track) The number of sectors per track is 128 for OPEN-V and 96 for the other emulation types. Example: For an OPEN-3 VLL volume with capacity = 37 MB:

# of blocks = (53 cylinders – see Note 3) × (15 heads) × (96 sectors per track) = 76320

6. The number of data cylinders for a Virtual LVI/LUN volume is calculated as follows (↑…↑ means that the value should be rounded up to the next integer):

Number of data cylinders for OPEN-x VLL volume (except for OPEN-V) =

# of cylinders = ↑ (capacity (MB) × 1024/720 ↑ Example: For OPEN-3 VLL volume with capacity = 37 MB: # of cylinders = ↑37 × 1024/720↑ = ↑52.62↑ = 53 cylinders

Number of data cylinders for an OPEN-V VLL volume =

# of cylinders = ↑ (capacity (MB) specified by user) × 16/15 ↑ Example: For OPEN-V VLL volume with capacity = 50 MB:

# of cylinders = ↑50 × 16/15↑ = ↑53.33↑ = 54 cylinders

Number of data cylinders for a VLL LUSE volume (except for OPEN-V) =

# of cylinders = ↑ (capacity (MB) × 1024/720 ↑ × n

Example: For OPEN-3 VLL LUSE volume with capacity = 37 MB and n = 4: # of cylinders = ↑37 × 1024/720↑ × 4 = ↑52.62↑ × 4 = 53 × 4 = 212

Number of data cylinders for an OPEN-V VLL LUSE volume =

# of cylinders = ↑ (capacity (MB) specified by user) × 16/15 ↑ × n Example: For OPEN-V VLL LUSE volume with capacity = 50 MB and n = 4: # of cylinders = ↑50 × 16/15↑ × 4 = ↑53.33↑× 4 = 54 × 4 = 216

Number of data cylinders for a 3390-3A/C =

# of cylinders = (number of cylinders) + 9

Number of data cylinders for a 3390-3B VLL volume =

# of cylinders = (number of cylinders) + 7

7. The size of an OPEN-x VLL volume is specified by capacity in MB, not number of cylinders. The size of an OPEN-V VLL volume can be specified by capacity in MB or number of cylinders. The user specifies the volume size using the Virtual LVI/LUN software.

(16)

Category Device Type Volume Usage SCSI Disk OPEN-x, OPEN-x VLL, OPEN-x*n LUSE,

OPEN-x*n VLL LUSE File System or Raw Device (for example, some applications use raw devices)

FX 3390-3A/B/C 3390-3A/B/C VLL

OPEN-x for FXoto, OPEN-x VLL for FXoto

Raw Device

(17)

Host Attachment Roadmap

The steps in

Table 1-4

outline the general process for attaching the Hitachi

RAID storage system to a Microsoft Windows host server.

Table 1-4

Host Attachment Roadmap

Step Task

1. Verify that the host to which you are attaching the Hitachi RAID storage system meets the requirements.

2. Prepare the Hitachi RAID storage system for host attachment. 3. Connect the Hitachi RAID storage system to the Windows host. 4. Configure the host adapters (HBAs and CNAs).

5. Verify disk and device parameters.

6. Write the signatures and create and format the partitions on the new disk devices. 7. Verify file system operations and auto-mount of the new logical devices.

(18)

(19)

2

Installing the Storage System

This chapter describes how to install the Hitachi RAID storage system on a

Microsoft Windows operating system:

Requirements

Preparing for Host Attachment

Connecting to the Windows Host

Configuring the

(20)

Requirements

Table 2-1

lists and describes the requirements for installing the Hitachi RAID

storage system on the Windows operating system.

Table 2-1

Requirements

Requirements Description

Hitachi RAID storage

system The availability of features and devices depends on the level of microcode installed on the Hitachi RAID storage system. The LUN Manager software on Storage Navigator is used to configure the fibre-channel ports.

Windows server or

workstation Refer to the Microsoft user documentation for PC server hardware requirements. Windows operating

system Please refer to the Hitachi Data Systems interoperability matrix for specific support information for the Windows operating system:

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

Fibre-channel HBAs The Hitachi RAID storage system supports fibre-channel HBAs equipped as follows:

8-Gbps fibre-channel interface, including shortwave non-OFC (open fibre

control) optical interface and multimode optical cables with LC connectors.

4 Gbps FC interface, including shortwave non-OFC optical interface and

multimode optical cables with LC connectors.

2 Gbps FC interface, including shortwave non-OFC optical interface and multimode optical cables with LC connectors.

1 Gbps FC interface, including shortwave non-OFC optical interface and multimode optical cables with SC connectors.

If a switch or HBA with a 1 Gbps transfer rate is used, configure the device to use a fixed 1 Gbps setting instead of Auto Negotiation. Otherwise, it may prevent a connection from being established.

However, the transfer speed of CHF port cannot be set as 1 Gbps when the CHF is 8US/8UFC/16UFC. Therefore 1 Gbps HBA and switch cannot be connected.

Do not connect OFC-type fibre-channel interfaces to the Hitachi RAID storage system.

For information about supported fibre-channel adapters, cables, hubs, and switches, refer to the Hitachi Data Systems interoperability matrix:

Fibre-channel over

ethernet CNAs The Hitachi Virtual Storage Platform supports FCoE CNAs equipped as follows: _{10 Gbps fibre-channel over Ethernet interface, including shortwave} non-OFC (open fibre control) optical interface and multimode optical cables with LC connectors.

For information about supported CNAs, cables, hubs, and switches, refer to the Hitachi Data Systems interoperability matrix:

Setup utilities and

tools for host adapters Refer to the documentation for your host adapter for information about installing and using the setup utilities and tools. FC and FCoE drivers Do not install/load the drivers yet. When instructed in this guide to install the

(21)

Preparing for Host Attachment

This section describes the tasks that must be performed before attaching the

Hitachi RAID storage system to the host:

• Installing the Hitachi RAID Storage System Hardware

• Setting the System Option Modes

• Installing the LUN Manager Software

• Setting the Host Mode Options

• Configuring the Fibre-Channel Ports

Installing the Hitachi RAID Storage System Hardware

The Hitachi Data Systems representative performs the hardware installation by

following the precautions and procedures in the Maintenance Manual for the

storage system.

Hardware installation activities include:

• Assembling all hardware and cabling.

• Installing and formatting the logical devices (LDEVs). Be sure to obtain the

desired LDEV configuration information from the user, including the desired

number of OPEN-x, LUSE, VLL, VLL LUSE, and multiplatform (FX) devices.

• Installing fibre-channel HBAs/FCoE CNAs and cabling. The total fibre 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.

–

Do not connect/disconnect fibre-channel cabling that is being actively

used for I/O. This can cause the Windows system to hang.

–

Always confirm that the devices on the fibre cable are offline before

connecting/disconnecting the fibre cable.

• Configuring the fibre port topology. The fibre topology parameters for each

fibre-channel port on the storage system depend on the type of device to

which the port is connected, and the type of port. Determine the topology

parameters supported by the device, and set your topology accordingly

(see

Configuring the USP V/VM Fibre-Channel Ports

).

Before starting the installation, check all specifications to ensure proper

installation and configuration.

(22)

To provide greater flexibility and enable the Hitachi RAID storage system to be

tailored to unique customer operating requirements, additional operational

parameters called “system option modes” are available. At installation, the

system option modes are set to their default values. The system option modes

are set on the service processor (SVP) and can only be changed by the Hitachi

Data Systems representative.

To ensure that the appropriate system option modes are set:

1. Review the system option modes for your storage system model. The

system option modes are listed and described in the User and Reference

Guide for your storage system model:

–

HUS VM User and Reference Guide, MK-92HM7005

–

Hitachi VSP User and Reference Guide, MK-90RD7042

–

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

2. Discuss the system option modes with your Hitachi Data Systems

representative, and ask the representative to set the system option modes

that apply to your configuration and environment.

Installing the LUN Manager Software

The LUN Manager software on Storage Navigator is used to configure the

fibre-channel ports on the Hitachi RAID storage system. The user or Hitachi

Data Systems representative installs the LUN Manager software.

For instructions on installing LUN Manager, see the Storage Navigator User

Guide for the storage system. For instructions on using LUN Manager, see the

(23)

You can connect multiple server hosts of different platforms to a single port,

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

groups, which are segregated by platform. For example, if both Windows and

VMware hosts are connected to a single port, you must first create a separate

host group for each platform, and then register the hosts to the corresponding

host group. When you create a host group, you need to set the host mode and

host mode options for the group.

Use Storage Navigator to create host groups, register hosts in host groups,

and set host modes and host mode options. For instructions see the

Provisioning Guide or the LUN Manager User’s Guide.

The required host mode for Windows is 0C Windows or 2C Windows

Extension. Do not select a host mode other than 0C or 2C for Windows.

Either setting is required to support MSCS failover and to recognize more than

eight LUs.

If you plan to create LUSE volumes, use host mode 2C Windows Extension.

If you plan to create a LUSE volume using a volume to which an LU path has

already been defined, you must use host mode 2C Windows Extension.

WARNING: Changing host modes on a Hitachi RAID storage system that is

already installed and configured is disruptive and requires the server to be

rebooted.

(24)

When each new host group is added, the storage administrator must make

sure that the host mode options (HMOs) are set for all host groups connected

to Windows hosts.

Table 2-2

lists and describes the HMOs that can be used for

Windows operations. Use the LUN Manager software on Storage Navigator to

set the HMOs.

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.

Table 2-2

Host Mode Options for Windows Operations

HMO Storage

System Function mode Host Comments

2 HUS VM

VSP USP V/VM

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.

6 HUS VM

VSP USP V/VM

Parameter Setting Failure for TPRLO.

Select HMO 6 when all of the following conditions are satisfied:

You are using the Emulex®_{host bus adapter and mini-port} driver, and

You specify TPRLO=2 for the host bus adaptor mini-port driver.

(25)

System mode

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 VSP, HUS VM: HMO 07 works (ON) regardless of the host mode setting. USP V/VM: 60-01-30-00/00 or later. 13 HUS VM VSP USP V/VM

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.

22 HUS VM VSP

USP V/VM

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

(26)

System mode 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 40 HUS VM VSP USP V/VM

Controls whether UA is returned to the host when a command from the host is received for an LU whose capacity has been expanded.

ON: When a command from the host is received for an LU whose capacity has been expanded, UA is returned to the host. OFF (default): When a command from the host is received for an LU whose capacity has been expanded, UA is not returned to the host.

Note: This option is applied when UA returning to the host is required after the DP-VOL capacity is expanded.

x0C, x2C USP V/VM: 60-03-24-00/00 or later 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

42 USP V/VM Controls the behavior when CHA PCI is accessed from MP and when the status is busy.

ON: The PCI retry is not returned, and the PCI bus is occupied. OFF (default): The PCI retry is returned.

Note: When IBM Z10 Linux is connected, set this mode to ON. In other cases, set the mode to OFF.

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

(27)

System mode 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)

VSP USP V/VM

Selects BB_Credit value. (HMO#49: Low_bit) ON: BB_Credit value of 80 or 255.

OFF (default): BB_Credit value of 40 or 128.

*HMO50/HMO49: BB_Credit value is decided by 2 bits of the two HMOs.

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

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

Note: Apply this HMO 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 works only when the microprogram supporting this function is installed on both MCU and RCU.

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).

2. This HMO works only when the microprogram supporting this function is installed on both MCU (M-DKC) and RCU (R-DKC). 3. The HMO setting is applied to Initiator-Port. This function is

applicable only 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.

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)

VSP USP V/VM

Selects BB_Credit value. (HMO#50: High_bit) ON: BB_Credit value of 128 or 255.

OFF (default): 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: Apply this option when 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:

2. This HMO works only when the microprogram 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 50 to OFF.

USP V/VM:

2. This HMO works only when the microprogram supporting this function is installed on both MCU (M-DKC) and RCU (R-DKC). 3. The HMO setting is 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 8US PCB, the operation must be executed

after setting the HMO 50 to OFF.

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

(30)

VSP USP V/VM

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: Apply this option when TrueCopy write I/O is executed. VSP, HUS VM:

2. This HMO works only when the microprogram 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. When removing 8UFC or 16UFC PCB, the operation must be executed after setting HMO 51 to OFF.

8. When HMO51 is set to ON using RAID600 as MCU and RAID700 as RCU, the micro-program of RAID600 must be 60-07-63-00/00 or higher (within 60-07-6x range) or 60-08-06-00/00 or higher.

9. Path attribute change (Initiator Port - 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:

2. This HMO works only when the microprogram supporting this function is installed on both MCU (M-DKC) and RCU (R-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. When removing 8US PCB, the operation must be executed after setting the HMO 51 to OFF.

8. When HMO51 is set to ON using RAID600 as MCU and RAID700 as RCU, the RAID600 microcode must be 60-07-63-00/00 or higher (within 60-07-6x range) or 60-08-06-00/00 or higher. 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

(31)

System mode 51 9. Path attribute change (Initiator Port - 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.

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

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. x0C, x2C, x01, x21 ESXi 5 or later _VSP: 70-02-03-00/00 or later USP V/VM: 60-08-01-00/00 or later

(32)

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)

System mode 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.

(34)

System mode 71 VSP 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.

73 HUS VM VSP

Enables new functions for Dynamic Provisioning with Windows Server 2012.

Mode 73 = ON:

- LOG SENSE command is enabled. - UNMAP command is enabled.

- MAXIMUM UNMAP LBA COUNT value of Inquiry Page B0h - RAID700:

For versions earlier than 70-05-17-00/00: 0xFFFFFFFF For 70-05-17-00/00 and later: 0x00000200 (*1) - SNSkey/code of check condition due to pool full status (permanent or temporary) is switched.

- Check condition for warning of threshold exceedance is responded.

(*1) By setting MAXIMUM UNMAP LBA COUNT value of Inquiry Page B0h to 0x0200, the maximum range that can be specified by one UNMAP command can be limited to 0x0200 (= 256 KB). This can reduce the processing time and the impact on other host I/Os by the UNMAP command.

Mode 73 = OFF (default):

- LOG SENSE command is disabled (regarded as unsupported command).

- UNMAP command is disabled (regarded as unsupported command).

- Inquiry Page B0h is not supported.

- SNSkey/code of check condition due to pool full status (permanent or temporary) is not switched.

- Check condition for warning of exceeding threshold is not responded.

Note: Apply this option when Dynamic Provisioning is used with Windows Server 2012. x0C, x2C HUS VM: DKCMAIN 73-02-01-00/00 and higher VSP: DKCMAIN 70-05-02-00/00 or later

(35)

The LUN Manager software is used to configure the fibre-channel ports with

the appropriate fibre parameters. You select the appropriate settings for each

fibre-channel port based on the device to which the port is connected.

Determine the topology parameters supported by the device, and set your

topology accordingly.

Figure 2-1

shows the LUN Manager window for defining port parameters, and

Table 2-3

explains the settings on the window.

Table 2-3

Fibre Parameter Settings

Fabric Connection Provides

Enable FC-AL FL-port (Fabric port) Not supported on FCoE Enable Point-to-Point F-port (Fabric port)

FCoE is available only on this setting Disable FC-AL NL-port (Private arbitrated loop)

Not supported on FCoE Disable Point-to-Point Not supported

Not supported on FCoE

Note:

• If you plan to connect different types of servers to the a Hitachi RAID

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

fabric switch.

• Contact Hitachi Data Systems for information about port topology

configurations supported by adapter/switch combinations. Not all switches

support F-port connection.

(36)

Figure 2-1

Setting FC Port Parameters (USP V/VM shown)

Port Address Considerations for Fabric Environments

In fabric environments, port addresses are assigned automatically by fabric

switch port number and are not controlled by the port settings on the storage

system. In arbitrated loop environments, the port addresses are set by

entering an AL-PA (arbitrated-loop physical address, or loop ID). See

Appendix

A: SCSI TID Maps for FC Adapters

for a description of the AL-PA-to-TID

translation.

1

Table 2-4

shows the available AL-PA values ranging from 01 to EF.

Fibre-channel protocol uses the AL-PAs to communicate on the fibre-channel

link, but the software driver of the platform host adapter translates the AL-PA

value assigned to the port to a SCSI TID.

(37)

EF CD B2 98 72 55 3A 25 E8 CC B1 97 71 54 39 23 E4 CB AE 90 6E 53 36 1F E2 CA AD 8F 6D 52 35 1E E1 C9 AC 88 6C 51 34 1D E0 C7 AB 84 6B 4E 33 1B DC C6 AA 82 6A 4D 32 18 DA C5 A9 81 69 4C 31 17 D9 C3 A7 80 67 4B 2E 10 D6 BC A6 7C 66 4A 2D 0F D5 BA A5 7A 65 49 2C 08 D4 B9 A3 79 63 47 2B 04 D3 B6 9F 76 5C 46 2A 02 D2 B5 9E 75 5A 45 29 01 D1 B4 9D 74 59 43 27 CE B3 9B 73 56 3C 26

Loop ID Conflicts

The Microsoft Windows operating system assigns port addresses from lowest

(01) to highest (EF). To avoid loop ID conflict, assign the port addresses from

highest to lowest (that is, starting at EF). The AL-PAs should be unique for

each device on the loop to avoid conflicts. Do not use more than one port

address with the same TID in same loop (for example, addresses EF and CD

both have TID 0).

(38)

Connecting to the Windows Host

After you have prepared the hardware and software on the storage system

and the host adapters, you can connect the Hitachi RAID storage system to

the Windows system.

1

Table 2-5

summarizes the steps for connecting a Hitachi RAID storage system

to a Windows host. Some steps are performed by the Hitachi Data Systems

representative, while others are performed by the user.

Table 2-5

Connecting the Hitachi RAID storage system to a Windows Host

Step Activity Performed by Description

1. Verify storage

system installation Hitachi Data Systems representative Confirm that the status of the host adapters and LDEVs is NORMAL. 2. Shut down the

Windows system User Power off the Windows system before connecting the Hitachi RAID storage system.

Shut down the Windows system.

Power off all peripheral devices except for the Hitachi RAID storage system.

Power off the host system. You are now ready to connect the

Hitachi RAID storage system. 3. Connect the Hitachi

RAID storage system

Hitachi Data Systems

representative Install fibre-channel/FCoE cables between the storage system and the Windows system. Follow all precautions and procedures in the Maintenance Manual for the storage system. Check all specifications to ensure proper installation and configuration. 4. Define LUN security

if connected to a fabric

User If the storage system is connected to a fabric, control access to the storage system before you power on Windows to avoid failures on other systems connected to the same fabric. Use any method to ensure that Windows sees only the LUs it owns (for example, LUN Security, set HBAs/CNAs to not automap LUNs, switch zoning). Refer to the LUN Manager User’s Guide (MK-96RD615).

5. Power on the

Windows system User Power on the Windows system after connecting the Hitachi RAID storage system:

Power on the Windows system display.

Power on all peripheral devices. The Hitachi RAID storage system should be on, and the fibre-channel ports should be configured. If the fibre ports are configured after the Windows system is powered on, restart the system to have the new devices recognized.

Confirm the ready status of all peripheral devices, including

the Hitachi RAID storage system.

Power on the Windows system. 6. Verify new device

recognition, and record the disk numbers

User When the adapter connected to the storage system shows the new devices (see Figure 2-2), pause the screen and record the disk number for each new device on your SCSI Device

worksheet (see Table 2-6). You will need this information when you write signatures on the devices (see Writing the

Signatures). 7. Boot the Windows

(39)

<<<Press <CTRL><A> for SCSISelect™ Utility>>> SCSI ID:0

LUN: 0 HITACHI OPEN-9 Hard Disk 0 Å Disk numbers may not start

at 0.

LUN: 1 HITACHI OPEN-9 Hard Disk 1 LUN: 2 HITACHI OPEN-3 Hard Disk 2 LUN: 3 HITACHI OPEN-3 Hard Disk 3 LUN: 4 HITACHI OPEN-3 Hard Disk 4 LUN: 5 HITACHI OPEN-9 Hard Disk 5 LUN: 6 HITACHI 3390-3A Hard Disk 6 LUN: 7 HITACHI 3390-3A Hard Disk 7 SCSI ID:1

LUN: 0 HITACHI OPEN-3 Hard Disk 8 LUN: 1 HITACHI OPEN-3 Hard Disk 9 LUN: 2 HITACHI OPEN-3 Hard Disk 10 :

:

(40)

The Windows system assigns the disk numbers sequentially starting with the

local disks and then by adapter, and by TID/LUN. If the Hitachi RAID storage

system is attached to the first adapter (displayed first during system start-up),

the disk numbers for the new devices will start at 1 (the local disk is 0). If the

Hitachi RAID storage system is not attached to the first adapter, the disk

numbers for the new devices will start at the next available disk number. For

example, if 40 disks are attached to the first adapter (disks 1–40) and the

Hitachi RAID storage system is attached to the second adapter, the disk

numbers for the storage system will start at 41.

Note: When disk devices are added to or removed from the Windows system,

the disk numbers are reassigned automatically. For the FX devices, be sure to

update your FX volume definition file (datasetmount.dat) with the new disk

numbers.

(41)

LDEV (CU:LDEV) LU Type VLL (MB) Device Number Bus Number

Path 1 Alternate Paths

0:00 TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:01 TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:02 TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:03 TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:04 TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:05 TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:06 TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:07 TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:08 TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:09 TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:0a TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:0b TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:0c TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:0d TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:0e TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:0f TID:____ LUN:____ TID:____ LUN:____ TID:____ LUN:____ 0:10 TID:____

LUN:____

TID:____

LUN:____

TID:____

LUN:____

and so on…

Configuration Guide for Microsoft Windows Host Attachment