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
14
5 Click OK
6 This establishes communication between the SAN and the target server.
Mounting a Volume to a Server
Select the Targets tab in the iSCSI initiator to view the targets.
Note: You will only see the volumes for which you have created a
volume list and authentication group. If you do not see your volumes
listed, first click on the Refresh button, then check the volume list,
authentication group and Virtual IP address configurations.
Locate the first volume you wish to connect to the server machine, it will be in
an Inactive state, and select Log On. This will bring up the Log On to Target
window. Click on the Automatically Reconnect at reboot box and select OK.
This checkbox will insure that the volume automatically connects upon host
server reboot. The volume should now show as Connected.