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

12
Next create a New Authentication Group. Select the Tasks option from the
menu bar, go to Authentication Group, and select New Authentication Group.
Click on the iSCSI tab, click the “Allow access via iSCSI” check box. Best
practice is to also select the “Load Balancing” check box. To confirm that your
iSCSI initiator is Load Balancing compliant, select the information on
compliant initiators link. Select the “CHAP not required” option and fill in the
initiator node name (see section below for using CHAP). The initiator node
name can be retrieved from the Microsoft™ iSCSI initiator of the specified
server, on the initiator General tab. Copy and paste the iqn name into the
Authentication Group dialog.
Note: The initiator node name must be unique in the SAN, take
precautions if changing.
Next, from the Volume List drop down box, select the volume list to associate
with this Authentication Group.
Note: With the exception of Microsoft™ Clusters, to eliminate the
possibility of data corruption, it is recommended to avoid allowing
write access to a given volume by more than one host server. Thus, take
caution when creating volume lists and authentication groups to
ensure each volume is accessible by only one host server.