HP LeftHand SAN Solutions Support Document - Application Notes - Best Practices for Enabling Microsoft Windows with SAN/iQ®
Table Of Contents
- Application Notes Best Practices for Enabling Microsoft Windows with SANiQ
- Contents
- 1 Chapter: Enabling LeftHand SAN volumes with the Microsoft™ iSCSI 2.0x Initiator
- 2 Chapter: Finding the iSCSI Initiator Version
- 3 Chapter: LeftHand Networks and Microsoft™ MPIO Support
- 4 Chapter: Expanding a Windows Volume on the SAN
- 5 Chapter: Shrinking a Windows Volume on the SAN
- 6 Chapter: Setting the Windows Disk Partition Offset for Optimal Performance
- 7 Chapter: Ensure That Application Resources on iSCSI Volumes Come Online After a Server Reboot
- 8 Chapter: Microsoft™ iSCSI Initiator Session Timeout Setting
- 9 Chapter: Measuring Performance in a Windows Environment
- Overview
- Using Windows Performance Monitor to Measure SAN Performance
- Setting up Windows Performance Monitor
- Saving a Performance Monitor Log for Analysis
- Monitoring More Than One Server Simultaneously
- Scheduling Performance Data Collection
- Using IOMeter as a SAN Benchmark Tool
- Configuring the ISCSI Volume
- Configuring IOMeter
- Configuring IOMeter Access Specification for each Test
- Running the Test
- Interpreting Results
- Access Specifications to Run
- 10 Chapter: Frequently Asked Questions

9
1 Chapter: Enabling LeftHand SAN volumes with
the Microsoft™ iSCSI 2.0x Initiator
Overview
The basic steps to connect a volume from the SAN to a server are below;
kdetailed information follows in later sections:
1 Assign the SAN/iQ cluster a Virtual IP Address (VIP), accomplished under
the Edit Cluster task options.
2 Install the iSCSI initiator (Before installing the Microsoft™ iSCSI
initiator, see section 3 below)
3 Create the volume on the SAN
4 Create a Volume List which contains all the volumes that will mount to a
particular server
5 Create an Authentication Group for the specified host server and
associate it with the appropriate Volume List
a Group should be for iSCSI volumes only
b Group will need either the IQN of the server or CHAP information. If
you are using CHAP see CHAP section below
6 In the iSCSI initiator, enter the Target Portal address. This is the Virtual
IP Address assigned above
a The host must be configured and the Authentication Group must be
created prior to the host being able to see it’s volumes on the SAN.
7 Logon/Connect the volume as persistent in the iSCSI initiator. Format
the volume
8 Set the service dependencies
9 Bind the volumes through the iSCSI initiator