Configuration Guide for Microsoft Windows Host Attachment

Transcription

1 Configuration Guide for Microsoft Windows Host Attachment Hitachi Unified Storage VM Hitachi Virtual Storage Platform Hitachi Universal Storage Platform V/VM FASTFIND LINKS Contents Product Version Getting Help MK-96RD639-10

2 Hitachi, Ltd. All rights reserved. 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. Microsoft product screen shots are reprinted with permission from Microsoft Corporation. ii

3 Contents 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 About the Hitachi RAID Storage Systems Device Types Host Attachment Roadmap Installing the Storage System Requirements Preparing for Host Attachment Installing the Hitachi RAID Storage System Hardware Setting the System Option Modes Installing the LUN Manager Software Setting the Host Modes Setting the Host Mode Options Configuring the Fibre-Channel Ports Port Address Considerations for Fabric Environments Loop ID Conflicts Connecting to the Windows Host Contents iii

4 Disk Number Assignments Configuring the Host Adapters Verifying the Disk and Device Parameters Verifying the Disk I/O Timeout Value (TOV) Verifying the Queue Depth Configuring the New Disk Devices Writing the Signatures Creating and Formatting the Partitions Verifying File System Operations Verifying Auto-Mount Changing the Enable Write Caching Option Failover and SNMP Operations Host Failover Path Failover Windows 2008 MPIO Configuration Procedure Enabling MultiPath IO SNMP Remote System Management Troubleshooting General Troubleshooting Calling the Hitachi Data Systems Support Center SCSI TID Maps for FC Adapters... A-1 Creating an Online LUSE Volume... B-1 Acronyms and Abbreviations iv Contents

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 Comments Preface v

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 x or later. Hitachi Virtual Storage Platform microcode x or later. Hitachi Universal Storage Platform V/VM microcode or later. Document Revision Level Revision Date Description MK-96RD639-P February 2007 Preliminary Release MK-96RD May 2007 Initial Release, supersedes and replaces MK-96RD639-P MK-96RD September 2007 Revision 1, supersedes and replaces MK-96RD MK-96RD May 2008 Revision 2, supersedes and replaces MK-96RD MK-96RD August 2008 Revision 3, supersedes and replaces MK-96RD MK-96RD November 2009 Revision 4, supersedes and replaces MK-96RD MK-96RD January 2010 Revision 5, supersedes and replaces MK-96RD MK-96RD October 2010 Revision 6, supersedes and replaces MK-96RD MK-96RD May 2011 Revision 7, supersedes and replaces MK-96RD MK-96RD November 2011 Revision 8, supersedes and replaces MK-96RD MK-96RD July 2013 Revision 10, supersedes and replaces MK-96RD vi Preface

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 Hitachi Dynamic Link Manager for Windows User s Guide, MK-92DLM129 Preface vii

8 Document Conventions This document uses the following terminology conventions: Convention Hitachi RAID storage system, storage system Description Refers to all models of the Hitachi RAID storage systems unless otherwise noted. This document uses the following typographic conventions: Convention Bold Italic monospace Indicates the following: Description 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. 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. 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. viii Preface

9 This document uses the following icons to draw attention to information: Icon Meaning Description Tip Important Provides helpful information, guidelines, or suggestions for performing tasks more effectively. Provides information that is essential to the completion of a task. Caution WARNING Failure to take or avoid a specified action can result in adverse conditions or consequences (for example, loss of access to data). 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 (10 3 ) bytes 1 MB 1,000 KB or 1,000 2 bytes 1 GB 1,000 MB or 1,000 3 bytes 1 TB 1,000 GB or 1,000 4 bytes 1 PB 1,000 TB or 1,000 5 bytes 1 EB 1,000 PB or 1,000 6 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 (2 10 ) bytes 1 MB 1,024 KB or 1,024 2 bytes 1 GB 1,024 MB or 1,024 3 bytes 1 TB 1,024 GB or 1,024 4 bytes 1 PB 1,024 TB or 1,024 5 bytes 1 EB 1,024 PB or 1,024 6 bytes Preface ix

10 Accessing Product Documentation Getting Help Comments The user documentation for the Hitachi RAID storage systems is available on the Hitachi Data Systems Portal: Check this site for the most current documentation, including important updates that may have been made after the release of the product. 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: 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! x Preface

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 Host Attachment Roadmap Introduction 1-1

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. 1-2 Introduction

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 Device Type OPEN-V Devices OPEN-x Devices LUSE Devices (OPEN-x*n) VLL Devices (OPEN-x VLL) VLL LUSE Devices (OPEN-x*n VLL) FX Devices (3390-3A/B/C, OPEN-x-FXoto) Logical Devices Supported by the Hitachi RAID storage systems Description OPEN-V logical units (LUs) are disk devices (VLL-based volumes) that do not have a predefined size. 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 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 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 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). 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 B devices are write-protected from Windows host access. The Hitachi RAID storage system rejects all Windows host write operations (including fibre-channel adapters) for B devices. The A/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. Introduction 1-3

14 Table 1-2 Device Specifications 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 OPEN-8 SCSI disk OPEN OPEN-9 SCSI disk OPEN OPEN-E SCSI disk OPEN-E OPEN-L SCSI disk OPEN-L OPEN-3*n SCSI disk OPEN-3*n *n 3338*n *n OPEN-8*n SCSI disk OPEN-8*n *n 9966*n *n OPEN-9*n SCSI disk OPEN-9*n *n 10016*n *n OPEN-E*n SCSI disk OPEN-E*n *n 19759*n *n OPEN-L*n SCSI disk OPEN-L*n *n 49439*n *n OPEN-3 VLL SCSI disk OPEN-3-CVS Note 5 Note Note 7 OPEN-8 VLL SCSI disk OPEN-8-CVS Note 5 Note Note 7 OPEN-9 VLL SCSI disk OPEN-9-CVS Note 5 Note Note 7 OPEN-E VLL SCSI disk OPEN-E-CVS Note 5 Note Note 7 OPEN-V VLL SCSI disk OPEN-V Note 5 Note Note 7 OPEN-3*n VLL SCSI disk OPEN-3*n-CVS Note 5 Note Note 7 OPEN-8*n VLL SCSI disk OPEN-8*n-CVS Note 5 Note Note 7 OPEN-9*n VLL SCSI disk OPEN-9*n-CVS Note 5 Note Note 7 OPEN-E*n VLL SCSI disk OPEN-E*n-CVS Note 5 Note Note 7 OPEN-V*n VLL SCSI disk OPEN-V*n Note 5 Note Note A FX otm/mto A B FXmto B C FXotm OP-C C FX OPEN-3 FXoto OPEN A VLL FX otm/mto A-CVS Note 5 Note Note B VLL FXmto B-CVS Note 5 Note Note C VLL FXotm OP-C C-CVS Note 5 Note Note 7 FX OPEN-3 VLL FXoto OPEN-3-CVS Note 5 Note Note Introduction

15 Notes 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 = or 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) = 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 = /720 = = 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 = = 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 = /720 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 = = 54 4 = 216 Number of data cylinders for a A/C = # of cylinders = (number of cylinders) + 9 Number of data cylinders for a B VLL volume = # of cylinders = (number of cylinders) 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. Introduction 1-5

16 Table 1-3 Volume Usage for Device Categories Category Device Type Volume Usage SCSI Disk FX OPEN-x, OPEN-x VLL, OPEN-x*n LUSE, OPEN-x*n VLL LUSE A/B/C A/B/C VLL OPEN-x for FXoto, OPEN-x VLL for FXoto File System or Raw Device (for example, some applications use raw devices) Raw Device 1-6 Introduction

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 Step Host Attachment Roadmap 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. 8. Change the Enable Write Caching on Disk option. Introduction 1-7

18 1-8 Introduction

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 Verifying the Disk and Device Parameters Installing the Storage System 2-1

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 Hitachi RAID storage system Windows server or workstation Windows operating system Fibre-channel HBAs Fibre-channel over ethernet CNAs Setup utilities and tools for host adapters FC and FCoE drivers Description 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. Refer to the Microsoft user documentation for PC server hardware requirements. Please refer to the Hitachi Data Systems interoperability matrix for specific support information for the Windows operating system: 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: 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: Refer to the documentation for your host adapter for information about installing and using the setup utilities and tools. Do not install/load the drivers yet. When instructed in this guide to install the drives for your host adapter, refer to the documentation for your adapter. 2-2 Installing the Storage System

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. Installing the Storage System 2-3

22 Setting the System Option Modes 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-96RD 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 Provisioning Guide or the LUN Manager User s Guide for the storage system. 2-4 Installing the Storage System

23 Setting the Host Modes 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. Installing the Storage System 2-5

24 Setting the Host Mode Options 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 Host mode Comments 2 HUS VM Veritas DBE+RAC Common Mandatory. VSP USP V/VM (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, Do not apply this option to Sun Cluster. (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. 6 HUS VM Parameter Setting Failure for TPRLO. x0c, x2c Optional VSP Select HMO 6 when all of the following conditions are satisfied: USP V/VM 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. 2-6 Installing the Storage System

25 HMO Storage System Function Host mode Comments 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. Common VSP, HUS VM: HMO 07 works (ON) regardless of the host mode setting. USP V/VM: /00 or later. 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. 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. Common USP V/VM: /00 or later (within x range) OFF: Reservation Conflict (Default). Notes: x-00/00 or later 1. By applying HMO 22, the volume status (reserved/nonreserved) 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. Installing the Storage System 2-7

26 HMO Storage System Function Host mode Comments 39 HUS VM VSP USP V/VM 40 HUS VM VSP USP V/VM 41 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. 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. 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: /00 or later VSP: /00 or later x0c, x2c USP V/VM: /00 or later Common USP V/VM: /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: /00 or later 2-8 Installing the Storage System

27 HMO Storage System Function Host mode Comments 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: /10 or later (within x range) /00 or later Installing the Storage System 2-9

28 HMO Storage System Function Host mode Comments 49 HUS VM 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 = : 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. 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. Common VSP: /00 and higher (within x range) /00 or later USP V/VM: /00 or later 2-10 Installing the Storage System

29 HMO Storage System Function Host mode Comments 50 HUS VM 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 = : 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: 1. When HMO 50 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 (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. 6. If HMO 50 is set to ON while SOM 769 is ON, path creation may fail after automatic port switching. 7. Make sure to set HMO 50 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 50 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 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. 6. If HMO 50 is set to ON while SOM 769 is ON, path creation may fail after automatic port switching. 7. Make sure to set HMO 50 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. Common VSP: /00 and higher (within x range) /00 or later USP V/VM: /00 or later Installing the Storage System 2-11

30 HMO Storage System Function Host mode Comments 51 HUS VM 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: 1. When HMO 51 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 (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. 5. If HMO 51 is set to ON while SOM 769 is ON, path creation may fail after automatic port switching. 6. Make sure to set HMO 51 from OFF to ON or from ON to OFF after the pair is suspended or when the load is low. 7. The RCU Target, which is connected with the MCU where 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 /00 or higher (within x range) or /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: 1. When HMO 51 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 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. 5. If HMO 51 is set to ON while SOM 769 is ON, path creation may fail after automatic port switching. 6. Make sure to set HMO 51 from OFF to ON or from ON to OFF after the pair is suspended or when the load is low. 7. The RCU Target, which is connected with the MCU where 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 RAID600 microcode must be /00 or higher (within x range) or /00 or higher. Common VSP: /00 and higher (within x range) /00 or later USP V/VM: /00 or later 2-12 Installing the Storage System

31 HMO Storage System Function Host mode Comments 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. 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: /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: /00 or later USP V/VM: /00 or later Installing the Storage System 2-13

32 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: /00 or later 2-14 Installing the Storage System

33 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 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.) 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 /00 or later Common /00 or later Installing the Storage System 2-15

34 HMO Storage System Function Host mode Comments 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. Common /00 or later 73 HUS VM VSP Enables new functions for Dynamic Provisioning with Windows Server 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 /00: 0xFFFFFFFF For /00 and later: 0x (*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 x0c, x2c HUS VM: DKCMAIN /00 and higher VSP: DKCMAIN /00 or later 2-16 Installing the Storage System

35 Configuring the Fibre-Channel Ports 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. Installing the Storage System 2-17

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. 1Table 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 Installing the Storage System

37 Table 2-4 Available AL-PA Values EF CD B A 25 E8 CC B E4 CB AE 90 6E F E2 CA AD 8F 6D E E1 C9 AC 88 6C D E0 C7 AB 84 6B 4E 33 1B DC C6 AA 82 6A 4D DA C5 A C D9 C3 A B 2E 10 D6 BC A6 7C 66 4A 2D 0F D5 BA A5 7A C 08 D4 B9 A B 04 D3 B6 9F 76 5C 46 2A 02 D2 B5 9E 75 5A D1 B4 9D CE B3 9B C 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). Installing the Storage System 2-19

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. 1Table 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 2. Shut down the Windows system 3. Connect the Hitachi RAID storage system 4. Define LUN security if connected to a fabric 5. Power on the Windows system 6. Verify new device recognition, and record the disk numbers 7. Boot the Windows system Hitachi Data Systems representative User Hitachi Data Systems representative User User User User Confirm that the status of the host adapters and LDEVs is NORMAL. 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. 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. 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). 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. 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) Installing the Storage System

39 Adaptec AHA-2944 Ultra/Ultra W Bios v Adaptec, Inc. All Rights Reserved <<<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 A Hard Disk 6 LUN: 7 HITACHI A 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 : : Figure 2-2 Recording the Disk Numbers for the New Devices Installing the Storage System 2-21

40 Disk Number Assignments 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 Installing the Storage System

41 Table 2-6 Sample SCSI Device Information Worksheet LDEV (CU:LDEV) LU Type VLL (MB) Device Number Bus Number Path 1 Alternate Paths 0:00 TID: 0:01 TID: 0:02 TID: 0:03 TID: 0:04 TID: 0:05 TID: 0:06 TID: 0:07 TID: 0:08 TID: 0:09 TID: 0:0a TID: 0:0b TID: 0:0c TID: 0:0d TID: 0:0e TID: 0:0f TID: 0:10 TID: and so on TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: TID: Installing the Storage System 2-23

42 Configuring the Host Adapters Use the setup utilities to configure the host bus adapters (HBAs) and converged network adapters (CNAs) connected to the Hitachi RAID storage system. The host adapters have many configuration options. This section provides the minimum requirements for configuring the host adapters for operation with the Hitachi RAID storage system. For information about other requirements, refer to the documentation for your adapter or contact the vendor. The minimum requirements for the Hitachi RAID storage system are: I/O timeout value (TOV). The disk I/O timeout value (TOV) requirement for the Hitachi RAID storage system is 60 seconds (0x3c hex). Queue depth. 1Table 2-7 specifies the queue depth requirements for Hitachi RAID storage system devices. You can adjust the queue depth for the devices later as needed (within the specified range) to optimize the I/O performance of the devices. BIOS. The BIOS may need to be disabled to prevent the system from trying to boot from the storage system. Use the same settings and device parameters for all devices on the Hitachi RAID storage system. Several other parameters (for example, FC fabric) may also need to be set. Refer to the user documentation for the host adapter to determine whether other options are required to meet your operational requirements. Table 2-7 Queue Depth Requirements Parameter IOCB Allocation (queue depth) per LU IOCB Allocation (queue depth) per port (MAXTAGS) Required Value 32 per LU 2048 per port The following sample instructions describe how to set the required parameters for an Emulex host adapter using the Emulex OneCommand Manager Tool. For other adapters, refer to the user documentation for the adapter. WARNING: If the adapter does not have a setup utility, or if the setup utility does not provide access to the required parameters, it may be necessary to edit the Windows registry to set these values. If this is the case, you must ask your Hitachi Data Systems representative for assistance. Changes made to the registry without the direct assistance of Hitachi Data Systems may jeopardize the proper operation of your Windows system and are the sole responsibility of the user Installing the Storage System

43 To set the queue depth and other device parameters using the setup utility for the adapter (Emulex shown): 1. Set the queue depth (QueueDepth) using the OneCommand Manager Tool as shown in Figure For the SCSI Port Driver, set the value of LinkTimeOut to 60. Figure 2-3 shows the default value of Verify all other required settings for your environment (for example, support for more than eight LUNs per target ID). Refer to the user documentation for the adapter as needed. 4. Save your changes, and exit the utility. If you need to change any settings, reboot the Windows system, and use the setup utility again. Figure 2-3 Setting the Queue Depth and Device Parameters Using Emulex OneCommand Manager Tool Installing the Storage System 2-25

44 Verifying the Disk and Device Parameters After you configure the ports and host adapters, verify the disk I/O timeout value, queue depth, and other required parameters such as fabric support. Verifying the Disk I/O Timeout Value (TOV) The disk I/O TOV parameter, which applies to all SCSI disk devices attached to the Windows system, must be set to 60 seconds. The default setting is hexadecimal 0x3c (decimal 60). WARNING: The following procedure is intended for the system administrator with the assistance of the Hitachi Data Systems representative. Use the Registry Editor with extreme caution. Do not change the system registry without the direct assistance of Hitachi Data Systems. For information and instructions about the registry, refer to the online help for the Registry Editor. To verify the disk I/O TOV using the Registry Editor: 1. Start the Windows Registry Editor: click Start, click Run, and enter regedt32 in the Run dialog box. 2. Go to HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Disk to display the disk parameters. 3. Verify that the TimeOutValue disk parameter is set to 60 seconds (0x3c), as shown in Figure Verify other required settings for your operational environment (for example, FC fabric support). Refer to the user documentation for the adapter as needed. 5. Exit the Registry Editor. 6. If you need to change any settings, reboot the Windows system, and use the setup utility for the adapter to change the settings. If you are not able to change the settings using the setup utility, ask your Hitachi Data Systems representative for assistance 2-26 Installing the Storage System

45 . Figure 2-4 Verifying the Disk I/O TOV Using the Registry Editor Installing the Storage System 2-27

46 Verifying the Queue Depth The queue depth requirements for the devices are specified in 1Table 2-7. The following sample instructions describe how to verify the queue depth for a QLogic HBA using the Registry Editor. WARNING: The following procedure is intended for the system administrator with the assistance of the Hitachi Data Systems representative. Use the Registry Editor with extreme caution. Do not change the system registry without the direct assistance of Hitachi Data Systems. For information and instructions about the registry, refer to the online help for the Registry Editor. To verify the queue depth and other device parameters using the Registry Editor: 1. Start the Windows Registry Editor: click Start, click Run, and enter regedt32 in the Run dialog box. 2. Go to HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services ql2200 (or 2300) Parameters Device to display the device parameters for the QLogic HBA (see Figure 2-5). 3. Verify that the queue depth value in DriverParameter meets the requirements for the Hitachi RAID storage system (see 1Table 2-7). 4. If connected to a fabric switch, make sure FabricSupported=1 appears in DriverParameter. 5. Verify other required settings for your environment (for example, support for more than eight LUNs per target ID). Refer to the HBA documentation as needed. 6. Make sure the device parameters are the same for all devices on the Hitachi RAID storage system. 7. Exit the Registry Editor. 8. If you need to change any settings, reboot the Windows system, and use the HBA setup utility to change the settings. If you are not able to change the settings using the HBA utility, ask your Hitachi Data Systems representative for assistance Installing the Storage System

47 Figure 2-5 Verifying the Queue Depth Using the Registry Editor Installing the Storage System 2-29

48 2-30 Installing the Storage System

49 3 Configuring the New Disk Devices This chapter describes how to configure the new disk devices. The topics in this chapter are: Writing the Signatures Creating and Formatting the Partitions Verifying File System Operations Verifying Auto-Mount Changing the Enable Write Caching Option Notes: The logical devices on the Hitachi RAID storage system are defined to the host as SCSI disk devices, even though the interface is fibre channel. Do not create partitions on the FX devices. If the FX devices will be used in the MSCS environment, you must write a signature on each FX device. If not, do not write a signature. For information about the FC AL-PA to SCSI TID mapping, see Appendix A: SCSI TID Maps for FC Adapters. Online LUSE expansion: data migration is not needed for OPEN-V (required for other LU types). A host reboot is not required for Windows. For more information, see your Hitachi Data Systems representative. Configuring the New Disk Devices 3-1

50 Writing the Signatures The first step when configuring new devices is to write a signature on each device using the Windows Disk Management. You must write a signature on each SCSI disk device to enable the Windows system to vary the device online. For MSCS environments, you must also write signatures on the FX and other raw devices. The 32-bit signature identifies the disk to the Windows system. If the disk s TID or LUN is changed, or if the disk is moved to a different controller, the Disk Management and Windows fault-tolerant driver will continue to recognize it. Note: Microsoft Windows assigns 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 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 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 Hitachi RAID storage system start at 41 To write the signatures on the new disk devices (see Figure 3-1): 1. Click the Start button, point to Programs, point to Administrative Tools (Computer Management), and click Disk Management to start the Disk Manager. Initialization takes a few seconds. 2. When the Disk Management notifies you that one or more disks have been added, click OK to allow the system configuration to be updated. Note: If you removed any disks, the Disk Management will also notify you at this time. 3. The Disk Management displays each new device by disk number and asks if you want to write a signature on the disk (see 1Figure 3-2). You may only write a signature once on each device. Refer to your completed SCSI Path Worksheet (see 1Table 2-6) to verify the device type for each disk number. For all SCSI disk devices, click OK to write a signature. For FX devices without MSCS, click No. For FX devices with MSCS, click Yes and observe this warning: WARNING: After a signature has been written on an FX device, there is no way to distinguish the FX device from a SCSI disk device. Use extreme caution to not accidentally partition and format an FX device. This will overwrite any data on the FX device and prevent the FX software from accessing the device. 3-2 Configuring the New Disk Devices

51 4. After you write or decline to write a signature on each new device, the Disk Management window displays the devices by disk number (see Figure 3-1). The total capacity and free space is displayed for each disk device with a signature. Configuration information not available indicates no signature. For directions on creating partitions on the new SCSI disk devices, see Creating and Formatting the Partitions to create. Figure 3-1 Disk Management Window Showing New Devices Note: In the example in the figure above, disk 0 is the local disk, disk 1 is an OPEN-3 device, disk 2 is an OPEN-3 device, and disk 3 is an OPEN-3 device. Configuring the New Disk Devices 3-3

52 Figure 3-2 Writing the Signatures 3-4 Configuring the New Disk Devices

53 Creating and Formatting the Partitions After write signatures on the new devices, create and format the partitions on the new SCSI disk devices. Use your completed SCSI Device Worksheet (see 1Table 2-6) as needed to verify disk numbers and device types. Dynamic Disk is supported with no restrictions for the Hitachi RAID storage system connected to the Windows operating system. For more information, refer to the Microsoft Windows online help. Note: Do not partition or create a file system on a device which will be used as a raw device (for example, some database applications use raw devices). All FX devices are raw devices. To create and format partitions on the new SCSI disk devices: 1. On the Disk Management window, select the unallocated area for the SCSI disk you want to partition, click the Action menu, and then click Create Partition to launch the New Partition Wizard. 2. When the Select Partition Type dialog box appears (see Figure 3-3), select the desired type of partition and click Next. Note: The Hitachi RAID storage systems do not support Stripe Set Volume with parity. 3. When the Specify Partition Size dialog box appears (see Figure 3-4), specify the desired partition size. If the size is greater than 1024 MB, you will be asked to confirm the new partition. Click Next. 4. When the Assign Drive Letter or Path dialog box appears (see Figure 3-5), select a drive letter or path, or specify no drive letter or drive path. Click Next. 5. When the Format Partition dialog box appears (see Figure 3-6), click Format this partition with the following settings and select the following options: File System: Select NTFS (enables the Windows system to write to the disk). Allocation unit size: Default. Do not change this entry. Volume label: Enter a volume label, or leave this field blank for no label. Format Options: Select Perform a Quick Format to decrease the time required to format the partition. Select Enable file and folder compression only if you want to enable compression. Configuring the New Disk Devices 3-5

54 6. Select Next to format the partition as specified. When the format warning appears (this new format will erase all existing data on disk), click OK to continue. The Format dialog box shows the progress of the format partition operation. 7. When the format operation is complete, click OK. The New Partition Wizard displays the new partition (see Figure 3-7). Click Finish to close the New Partition Wizard. 8. Verify that the Disk Management window shows the correct file system (NTFS) for the formatted partition (see 2Figure 3-8). The word Healthy indicates that the partition has been created and formatted successfully. 9. Repeat steps 1 through 8 for each new SCSI disk device. When you finish creating and formatting partitions, exit the Disk Management. When the disk configuration change message appears, click Yes to save your changes. Note: Be sure to make your new Emergency Repair Disk using RDISK.EXE. Figure 3-3 New Partition Wizard Dialog Box 3-6 Configuring the New Disk Devices

55 Figure 3-4 Specifying the Partition Size Figure 3-5 Assigning the Drive Letter or Path Configuring the New Disk Devices 3-7

56 Figure 3-6 Formatting the Partition Figure 3-7 Successful Formatting Confirmation Dialog Box 3-8 Configuring the New Disk Devices

57 Figure 3-8 Verifying the Formatted Partition Configuring the New Disk Devices 3-9

58 Verifying File System Operations After you create and format the partitions, verify that the file system is operating properly on each new SCSI disk device. The file system enables the Windows host to access the devices. You can verify file system operation easily by copying a file onto each new device. If the file is copied successfully, this verifies that the file system is operating properly and that Windows can access the new device. Note: Do not perform this procedure for FX and other raw devices. Instead, use the FX File Conversion Utility (FCU) or File Access Library (FAL) to access the FX devices. To verify file system operations for the new SCSI disk devices: 1. From the Windows desktop, double-click My Computer to display all connected devices. All newly partitioned disks appear in this window (see 2Figure 3-9). 2. Select the device you want to verify, then display its Properties using either of the following methods: On the File menu, click Properties. Right-click and select Properties. 3. On the Properties dialog box (see 2Figure 3-10), verify that the following properties are correct: Label (optional) Type Capacity File system 4. Copy a small file to the new device. 5. Display the contents of the new device to be sure the copy operation completed successfully (see 2Figure 3-11). The copied file should appear with the correct file size. If desired, compare the copied file with the original file to verify no differences. 6. Delete the copied file from the new device, and verify the file was deleted successfully. 7. Repeat steps 2 through 6 for each new SCSI disk device Configuring the New Disk Devices

59 Figure 3-9 Displaying the Connected Devices Note: In the example above, (E:) and (F:) are the new devices. Configuring the New Disk Devices 3-11

60 Figure 3-10 Verifying the New Device Properties Figure 3-11 Verifying the File Copy Operation 3-12 Configuring the New Disk Devices

61 Verifying Auto-Mount The last step in configuring the new devices is to verify that all new devices are mounted automatically at system boot-up. To verify auto-mount of the new devices: 1. Shut down and then restart the Windows system. 2. Open My Computer and verify that all new SCSI disk devices are displayed. 3. Verify that the Windows host can access each new device by repeating the procedure in Verifying File System Operations: a. Verify the device properties for each new device (see Figure 3-10). b. Copy a file to each new device to be sure the devices are working properly (see Figure 3-11). Configuring the New Disk Devices 3-13

62 Changing the Enable Write Caching Option The Enable Write Cache option has no effect on the cache algorithm when used with HDS storage systems and is not related to any internal Windows server caching. Microsoft and Hitachi Data Systems both recommend that you enable this option because it will provide a small improvement to Microsoft error reporting. To enable or disable the setting Enable write caching on the disk: 1. Right-click My Computer. 2. Click Manage. 3. Click Device Manager. 4. Click the plus sign (+) next to Disk Drives. A list of all the disk drives appears. 5. Double-click the first HDS system disk drive. 6. Click the Policies or Disk Properties tab. 7. If Enable write caching on the disk is enabled, a check mark appears next to it. To disable this option, clear the check mark (see Figure 3-12). If the Enable Write Cache option is grayed-out, this option is disabled. 8. Repeat this procedure for all additional HDS system disks Configuring the New Disk Devices

63 Figure 3-12 Example of the Enable Write Caching on the Disk Option Being Disabled Configuring the New Disk Devices 3-15

64 3-16 Configuring the New Disk Devices

65 4 Failover and SNMP Operations The Hitachi RAID storage systems support industry-standard products and functions that provide host and application failover, I/O path failover, and logical volume management (LVM). The Hitachi RAID storage systems also support the industry-standard simple network management protocol (SNMP) for remote system management from the UNIX/PC server host. SNMP is used to transport management information between the storage system and the SNMP manager on the host. The SNMP agent sends status information to the hosts when requested by the host or when a significant event occurs. This chapter describes how failover and SNMP operations are supported on the Hitachi RAID storage system. Host Failover Path Failover Windows 2008 MPIO Configuration Procedure SNMP Remote System Management Note: The user is responsible for configuring the failover and SNMP management software on the UNIX/PC server host. For assistance with failover and SNMP configuration on the host, refer to the user documentation, or contact the vendor s technical support. Failover and SNMP Operations 4-1

66 Host Failover The Hitachi RAID storage systems support the MSCS host failover feature of the Windows operating system. Note: To configure an MSCS environment via a fabric switch, use zoning functionality per each host bus adapter. When Hitachi RAID storage system devices operate in an MSCS environment, write signatures on the devices (see Writing the Signatures). For MSCS operations, allow the Windows Disk Management to write a signature on all SCSI disk devices and all FX devices (for example, A/B/C, OPEN-3 for FXoto). After device configuration is complete, configure the MSCS software to recognize the newly attached devices on the Hitachi RAID storage system. For assistance with MSCS operations, refer to the Microsoft user documentation or contact Microsoft customer support. Note about cluster shared volume: When cluster shared volume (CSV) is used in the Hyper-V+MSFC environment, each node always registers one unique PGR Key in each LU. The number of PGR keys is calculated is as follows: Number of PGR keys/port = (number of nodes) (number of LUs) = Reservation keys per port available for Hitachi RAID storage system In the case of shared LU other than CSV, one unique PGR Key is usually registered in each LU by the owner node. When failover occurs, for example due to node power loss, another PGR key is temporarily added in each LU (max 32 LUs concurrently). The number of PGR keys is calculated as follows: Number of PGR keys/port = (number of nodes) (number of LUs) 128 CSV is available in Windows 2008 R2 or later. 4-2 Failover and SNMP Operations

67 Path Failover The Hitachi RAID storage systems support the Hitachi Dynamic Link Manager path failover and load balancing product for the Windows operating system. After you complete device configuration as described in Chapter 3: Configuring the New Disk Devices, configure the Hitachi Dynamic Link Manager as needed to recognize the newly attached devices on the Hitachi RAID storage system. For assistance with Hitachi Dynamic Link Manager, refer to the Hitachi Dynamic Link Manager User s Guide (MK-92DLM129) or contact your Hitachi Data Systems representative. Failover and SNMP Operations 4-3

68 Windows 2008 MPIO Configuration Procedure Enabling MultiPath IO The following procedure enables and configures the MultiPath IO (Input/Output) feature of the Windows Server Manager for HDS storage systems. 1. Launch Server Manager, and open the Administrator Tools menu. 2. Select Diagnostics, and then open Device Manager window (see Figure 4-1) and verify that HITACHI OPEN-x SCSI Disk Device is displayed as having n LDEV x 2 paths=2n devices. Figure 4-1 Device Manager Window 4-4 Failover and SNMP Operations

69 3. From Server Manager, select Features and click Add Features (see Figure 4-2. Figure 4-2 Selecting the Add Features Window 4. In the Select Features window (see Figure 4-3) select Multipath I/O and Click Next If the Cluster option is selected, Multipath I/O and Failover Clustering must be selected. Figure 4-3 Selecting MPIO Features Failover and SNMP Operations 4-5

70 5. Confirm the installed content (Mutlipath I/O) and Click Install to start the installation (see Figure 4-4). Figure 4-4 Starting the Installation 6. When the Installation Results window appears (see Figure 4-5), review and confirm (if successful) by clicking Close. Figure 4-5 Successful Installation Notice 4-6 Failover and SNMP Operations

71 Note: If the system notice in Figure 4-6 appears, restart the server. Figure 4-6 Restart Server Notice 7. To launch MPIO, select Start, then from the Control Panel (Figure 4-7, double-click the MPIO icon. Figure 4-7 Launching the MPIO driver Failover and SNMP Operations 4-7

72 8. On the MPIO Properties window (see Figure 4-8), select the MPIO-ed Devices tab, select the device to add, and click Add. Figure 4-8 MPIO Properties Tab Window 9. When the Add MPIO Support window (see Figure 4-9) opens, enter HITACHI OPEN-, and click OK. Figure 4-9 Add MPIO Support Window 4-8 Failover and SNMP Operations

73 10. When the Reboot Required message appears (see Figure 4-10), click Yes. Figure 4-10 Reboot Required Window 11. After the reboot, go to Server Manager, select Diagnostics and in the Device Manager window (Figure 4-11) and verify that HITACHI OPEN-x Multi-Path Disk Device is displayed correctly. Figure 4-11 Device Manager Window Failover and SNMP Operations 4-9

74 12. To set the Balance Policy, select the device and right-click to access its properties window (see Figure 4-12). Select Round Robin for each LU. This policy setting is selectable on a per device basis. Figure 4-12 Setting Load Balance Policy This completes enabling and configuring the MPIO feature Failover and SNMP Operations

75 SNMP Remote System Management SNMP is a part of the TCP/IP protocol suite that supports maintenance functions for storage and communication devices. The Hitachi RAID storage systems use SNMP to transfer status and management commands to the SNMP Manager on the UNIX/PC server host (see Figure 4-13). When the SNMP manager requests status information or when a service information message (SIM) occurs, the SNMP agent on the storage system notifies the SNMP manager on the UNIX/PC server. Notification of error conditions is made in real time, providing the UNIX/PC server user with the same level of monitoring and support available to the mainframe user. The SIM reporting via SNMP enables the user to monitor the Hitachi RAID storage system from the UNIX/PC server host. When a SIM occurs, the SNMP agent on the Hitachi RAID storage system initiates trap operations, which alert the SNMP manager of the SIM condition. The SNMP manager receives the SIM traps from the SNMP agent, and can request information from the SNMP agent at any time. Note: The user is responsible for configuring the SNMP manager on the Windows host. For assistance with SNMP manager configuration on the Windows host, refer to the user documentation, or contact the vendor s technical support. Hitachi RAID storage system SIM Private LAN SNMP Manager Error Info. Public LAN Service Processor UNIX/PC Server Figure 4-13 SNMP Environment Failover and SNMP Operations 4-11

76 4-12 Failover and SNMP Operations

77 5 Troubleshooting This chapter provides troubleshooting information for Windows host attachment and includes instructions for calling technical support. General Troubleshooting Calling the Hitachi Data Systems Support Center Troubleshooting 5-1

78 General Troubleshooting Table 5-1 lists potential error conditions that may occur during installation of new storage and provides instructions for resolving the conditions. If you cannot resolve an error condition, contact your Hitachi Data Systems representative, or call the Hitachi Data Systems Support Center for assistance (see Calling Hitachi Data Systems Support Center for instructions). For troubleshooting information for the Hitachi RAID storage system, see the User and Reference Guide for the storage system (for example, Hitachi Virtual Storage Platform User and Reference Guide). For troubleshooting information for Hitachi Storage Navigator, see the Storage Navigator User Guide for the storage system (for example, Hitachi Virtual Storage Platform Storage Navigator User Guide). For information on errors messages displayed by Storage Navigator, see the Storage Navigator Messages document for the storage system (for example, Hitachi Virtual Storage Platform Storage Navigator Messages). Table 5-1 Troubleshooting Error Condition The devices are not recognized by the system. The Windows system does not reboot properly after hard shutdown. Recommended Action Be sure the READY indicator lights on the storage system are ON. Be sure the fibre cables are correctly installed and firmly connected. If the Windows system is powered off unexpectedly (without the normal shutdown process), wait three minutes before restarting the Windows system. This lets the storage system s internal time-out process to purge all queued commands so the storage system is available (not busy) during system startup. If the Windows system is restarted too soon, the storage system tries to process the queued commands and the Windows system will not reboot successfully. 5-2 Troubleshooting

79 Calling the Hitachi Data Systems Support Center If you need to call the Hitachi Data Systems Support Center, please gather as much information about the problem as possible, including: The circumstances surrounding the error or failure. The content of any error messages displayed on the host systems. The content of any error messages displayed on Storage Navigator. The service information messages (SIMs), including reference codes and severity levels, displayed by Storage Navigator. 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: Troubleshooting 5-3

80 5-4 Troubleshooting

81 A SCSI TID Maps for FC Adapters When an arbitrated loop (AL) is established or re-established, the port addresses are assigned automatically to prevent duplicate target IDs (TID). When using the SCSI over fibre-channel protocol (FCP), TIDs are no longer needed. SCSI is a bus-oriented protocol requiring each device to have a unique address since all commands go to all devices. For fibre channel, the AL-PA is used instead of the TID to direct packets to the desired destination. Unlike traditional SCSI, once control of the loop is acquired, a point-to-point connection is established from the initiator to the target. To enable transparent use of FCP, the Windows operating system maps a TID to each AL-PA. Tables A-1 and A-2 identify the fixed mappings between the bus/tid/lun addresses assigned by Windows and the FC native addresses (AL_PA/SEL_ID) for the host adapters. There are two potential mappings depending on the value of the ScanDown registry parameter: For ScanDown = 0 (default) see Table A-1. For ScanDown = 1 see Table A-2. Note: When Hitachi RAID storage system devices and other types of devices are connected in the same arbitrated loop, the mappings defined in Tables A-1 and A-2 cannot be guaranteed. Note: The Emulex driver emulates six SCSI buses per adapter to map all 126 possible AL-PAs to target IDs. The first bus (bus 0) is a dummy bus. SCSI TID Maps for FC Adapters A-1

82 Table A-1 SCSI TID Map for Emulex FC Adapter (ScanDown=0) Bus # TID LUN AL_PA SEL_ID Bus # TID LUN AL_PA SEL_ID Bus # TID LUN AL_PA SEL_ID x01 0x7D 2 0 0x43 0x5E 1 0x02 0x7C 1 0x45 0x5D 2 0x04 0x7B 2 0x46 0x5C 3 0x08 0x7A 3 0x47 0x5B 4 0x0F 0x79 4 0x49 0x5A 5 0x10 0x78 5 0x4A 0x59 6 0x17 0x77 6 0x4B 0x58 7 0x18 0x76 7 0x4C 0x57 8 0x1B 0x75 8 0x4D 0x56 9 0x1D 0x74 9 0x4E 0x x1E 0x x51 0x x1F 0x x52 0x x23 0x x53 0x x25 0x x54 0x x26 0x6F 14 0x55 0x x27 0x6E 15 0x56 0x4F 16 0x29 0x6D 16 0x59 0x4E 17 0x2A 0x6C 17 0x5A 0x4D 18 0x2B 0x6B 18 0x5C 0x4C 19 0x2C 0x6A 19 0x63 0x4B 20 0x2D 0x x65 0x4A 21 0x2E 0x x66 0x x31 0x x67 0x x32 0x x69 0x x33 0x x6A 0x x34 0x x6B 0x x35 0x x6C 0x x36 0x x6D 0x x39 0x x6E 0x x3A 0x x71 0x x3C 0x5F 30 0x72 0x A-2 SCSI TID Maps for FC Adapters

83 SCSI TID Maps for FC Adapter A-3 Table A-1 SCSI TID Map for Emulex FC Adapter (ScanDown=0) (continued) Bus # TID LUN AL_PA SEL_ID Bus # TID LUN AL_PA SEL_ID Bus # TID LUN AL_PA SEL_ID x73 0x74 0x75 0x76 0x79 0x7A 0x7C 0x80 0x81 0x82 0x84 0x88 0x8F 0x90 0x97 0x98 0x9B 0x9D 0x9E 0x9F 0xA3 0xA5 0xA6 0xA7 0xA9 0xAA 0xAB 0xAC 0xAD 0xAE 0xB1 0x3F 0x3E 0x3D 0x3C 0x3B 0x3A 0x39 0x38 0x37 0x36 0x35 0x34 0x33 0x32 0x31 0x30 0x2F 0x2E 0x2D 0x2C 0x2B 0x2A 0x29 0x28 0x27 0x26 0x25 0x24 0x23 0x22 0x xB2 0xB3 0xB4 0xB5 0xB6 0xB9 0xBA 0xBC 0xC3 0xC5 0xC6 0xC7 0xC9 0xCA 0xCB 0xCC 0xCD 0xCE 0xD1 0xD2 0xD3 0xD4 0xD5 0xD6 0xD9 0xDA 0xDC 0xE0 0xE1 0xE2 0xE4 0x20 0x1F 0x1E 0x1D 0x1C 0x1B 0x1A 0x19 0x18 0x17 0x16 0x15 0x14 0x13 0x12 0x11 0x10 0x0F 0x0E 0x0D 0x0C 0x0B 0x0A 0x09 0x08 0x07 0x06 0x05 0x04 0x03 0x xE8 0xEF 0x01 0x00

84 Table A-2 SCSI TID Map for Emulex FC Adapter (ScanDown=1) Bus # TID LUN AL_PA SEL_ID Bus # TID LUN AL_PA SEL_ID Bus # TID LUN AL_PA SEL_ID xEF 0x xB3 0x1F 1 0xE8 0x01 1 0xB2 0x20 2 0xE4 0x02 2 0xB1 0x21 3 0xE2 0x03 3 0xAE 0x22 4 0xE1 0x04 4 0xAD 0x23 5 0xE0 0x05 5 0xAC 0x24 6 0xDC 0x06 6 0xAB 0x25 7 0xDA 0x07 7 0xAA 0x26 8 0xD9 0x08 8 0xA9 0x27 9 0xD6 0x09 9 0xA7 0x xD5 0x0A 10 0xA6 0x xD4 0x0B 11 0xA5 0x2A 12 0xD3 0x0C 12 0xA3 0x2B 13 0xD2 0x0D 13 0x9F 0x2C 14 0xD1 0x0E 14 0x9E 0x2D 15 0xCE 0x0F 15 0x9D 0x2E 16 0xCD 0x x9B 0x2F 17 0xCC 0x x98 0x xCB 0x x97 0x xCA 0x x90 0x xC9 0x x8F 0x xC7 0x x88 0x xC6 0x x84 0x xC5 0x x82 0x xC3 0x x81 0x xBC 0x x80 0x xBA 0x1A 26 0x7C 0x xB9 0x1B 27 0x7A 0x3A 28 0xB6 0x1C 28 0x79 0x3B 29 0xB5 0x1D 29 0x76 0x3C 30 0xB4 0x1E 30 0x75 0x3D A-4 SCSI TID Maps for FC Adapters

85 SCSI TID Maps for FC Adapter A-5 Table A-2 SCSI TID Map for Emulex FC Adapter (ScanDown=1) (continued) Bus # TID LUN AL_PA SEL_ID Bus # TID LUN AL_PA SEL_ID Bus # TID LUN AL_PA SEL_ID x74 0x73 0x72 0x71 0x6E 0x6D 0x6C 0x6B 0x6A 0x69 0x67 0x66 0x65 0x63 0x5C 0x5A 0x59 0x56 0x55 0x54 0x53 0x52 0x51 0x4E 0x4D 0x4C 0x4B 0x4A 0x49 0x47 0x46 0x3E 0x3F 0x40 0x41 0x42 0x43 0x44 0x45 0x46 0x47 0x48 0x49 0x4A 0x4B 0x4C 0x4D 0x4E 0x4F 0x50 0x51 0x52 0x53 0x54 0x55 0x56 0x57 0x58 0x59 0x5A 0x5B 0x5C x45 0x43 0x3C 0x3A 0x39 0x36 0x35 0x34 0x33 0x32 0x31 0x2E 0x2D 0x2C 0x2B 0x2A 0x29 0x27 0x26 0x25 0x23 0x1F 0x1E 0x1D 0x1B 0x18 0x17 0x10 0x0F 0x08 0x04 0x5D 0x5E 0x5F 0x60 0x61 0x62 0x63 0x64 0x65 0x66 0x67 0x68 0x69 0x6A 0x6B 0x6C 0x6D 0x6E 0x6F 0x70 0x71 0x72 0x73 0x74 0x75 0x76 0x77 0x78 0x79 0x7A 0x7B x02 0x01 0x7C 0x7D

86 A-6 SCSI TID Maps for FC Adapters

87 B Creating an Online LUSE Volume This appendix explains how to safely expand a LUSE volume in an online Windows operating system using Storage Navigator. Note: It is recommended that you stop all I/O activity if possible before you perform an online LUSE expansion. For the instructions below, the following applies: LDEV # = 0:32 Mount point = i capacity = 40 MB Complete the following steps: 1. Right click My Computer, and then select Manage. 2. From the pull down menu, select Disk Management to confirm that Disk I is mounted and that Disk 12 is on this system. Disk 12 is the disk that will be expanded. Creating an Online LUSE Volume B-1

88 Figure B-1 Selecting the Manage Command B-2 Creating an Online LUSE Volume

89 3. Right click on the disk number and select Properties to obtain more detailed information. In this example, detailed information for Disk 13 is displayed. Figure B-2 Viewing Disk Properties Creating an Online LUSE Volume B-3

90 4. Start Storage Navigator. Figure B-3 Storage Navigator Screen 5. From the vertical menu bar on the left side of the window, select the LUN Expansion icon: 6. In the LDEV Information pane on the left side of the window, open a CU folder and select an LDEV. 7. Enable Write privileges by clicking the pen icon in the top-right corner: 8. Using the Select an LDEV drop-down list, select an LDEV. The free LDEVs appear in the Free LDEVs area at the bottom right of the page and the LDEV you selected appears in the Expanded LDEVs list. B-4 Creating an Online LUSE Volume

91 Figure B-4 Adding LDEVs 9. In the Free LDEVs area, click an LDEV and click the Add button to move the selected LDEV to the Expanded LDEVs list. Repeat this step for each additional LDEV you want to add. Note: To select multiple LDEVs that are next to each other, click the first LDEV you want to add; then hold down the Shift key and select the last LDEV. All the LDEVs between the first and last ones you selected are selected. If the LDEVs are not adjacent, select the first LDEV you want to add; then hold down the Ctrl key and select each additional LDEV you want to add. 10. Click the Set button. The following message appears: 11. Click the OK button to continue. Creating an Online LUSE Volume B-5

92 12. Click the Apply button. The following message appears: 13. Click the OK button to apply. The following message appears: 14. Click the OK button to remove the message. You have just created the online LUSE. B-6 Creating an Online LUSE Volume

93 The next step is to use DISKPART to configure Windows host to recognize the expanded LDEV. 1. Return to the Windows Computer Management application. 2. Select Action from the Menu bar, then select Rescan from the Action subfunctions to refresh the display. After this is done, you will see that the mounted volume I:\ (disk 12) is expanded from 40 MB to 80 MB. At this point, however, the newly added disk is not yet formatted. You now must use Diskpart to combine the new partition. Figure B-5 Example of a Mounted Volume that has been Expanded Note: Before using Diskpart, please read all applicable instructions. 3. From a command prompt, enter Diskpart and press Enter. 4. At the DISKPART> prompt enter list disk and press Enter. A list of disks appears. 5. When you have identified the disk to be expanded (Disk 1 in this example), enter select disk=1 (for this example) and press Enter. Disk 1 is now the selected disk on which the operations will be performed. Creating an Online LUSE Volume B-7

94 Figure B-6 Selecting a Disk to be Expanded a. At the DISKPART> prompt enter detail disk and press Enter. Disk details will be shown. b. Select the volume to be used. For this example, enter select volume = 4 and press Enter. Figure B-7 Selecting a Volume B-8 Creating an Online LUSE Volume

95 c. At the DISKPART> prompt, enter extend and press Enter to combine the available volumes for the selected disk into a single partition. d. Enter detail disk at the DISKPART> prompt and press Enter to verify that the size is 68G. Creating an Online LUSE Volume B-9

96 B-10 Creating an Online LUSE Volume

97 Acronyms and Abbreviations AL AL-PA blk CNA CVS DP FAL FC FCoE FCP FCU FX GB Gbps HBA HDLM HDP HUS VM I/O KB LU LUN LUSE LVI LVM MB MPE MSCS OFC arbitrated loop arbitrated loop physical address block converged network adapter custom volume size Hitachi Dynamic Provisioning File Access Library fibre-channel fibre-channel over ethernet fibre-channel protocol file conversion utility Hitachi Cross-OS File Exchange gigabyte gigabits per second host bus adapter Hitachi Dynamic Link Manager Hitachi Dynamic Provisioning Hitachi Unified Storage VM input/output kilobyte logical unit logical unit number LUN Expansion logical volume image Logical Volume Manager megabyte maximum number of physical extents Microsoft Cluster Server open fibre control Acronyms and Abbreviations Acronyms-1

98 PA PC PP RAID SCSI SIM SNMP TB TID TOV USP V USP VM VLL VSP WWN physical address personal computer physical partition redundant array of independent disks small computer system interface service information message simple network management protocol terabyte target ID time-out value Hitachi Universal Storage Platform V Hitachi Universal Storage Platform VM Virtual LVI/LUN Hitachi Virtual Storage Platform worldwide name Acronyms-2 Acronyms and Abbreviations

99

100 Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California U.S.A. Regional Contact Information Americas Europe, Middle East, and Africa +44 (0) Asia Pacific MK-96RD639-10