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
56
correct IQN number is entered for the authentication group, and that the
Virtual IP address of the SAN/iQ cluster is configured properly, and is
entered in the Discovery tab of the initiator.
For further information on this, please see the applicable article on
Enabling LeftHand SAN Volumes, referenced at the end of this document.
4 Select the Automatically restore this connection when the system boots
check box, then click OK.
Note: DO NOT select the “Enable Multi-path” checkbox unless you are
using the LeftHand Networks DSM for MPIO to enable multiple SAN
network cards in the host server. See Section 3 for more details.)
Method 2: Using the iSCSI Command Line Interface
1 Click Start and select Run from the menu.
2 Type cmd in the Open field and click OK.
3 At the command prompt, type the following command, and press ENTER:
iscsicli persistentlogintarget <target_iqn> T * * * * * * * * * * * * * * * 0
Note: <target_iqn> is the IQN name of the target. This can be
gathered under “Target Information” when the volume is selected
in the Centralized Management Console.
Note: Type “T * * * * * * * * * * * * * * * 0” exactly as it appears, with
15 (*) characters, and spaces between each character.
4 Type exit to close the command window.
Verify Persistence Settings
1 Open Control Panel and double-click the iSCSI Initiator.
2 Select the Persistent Targets tab and confirm that the volume name /
Target IQN is included in the list.
Binding Volumes with the Microsoft™ ISCSI Initiator
Note: Binding the volumes always needs to be the final step in this
process. If you do these steps out order, or if you add subsequent servers
or volumes, bind the volumes again as a final step, otherwise the
volumes may not be available after the server reboot.
Once iSCSI Dependencies and Persistent Logons are configured and
connectivity with the host server is established and confirmed, the final step
is to bind the volumes in the iSCSI initiator.
To bind volumes, choose one of the following methods: