HP LeftHand SAN Solutions Support Document - Application Notes - Best Practices for Enabling Microsoft Windows with SAN/iQ®

Table Of Contents
18
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. Select the “Automatically restore this connection when the system
boot” check box. This checkbox will insure that the volume automatically
connects upon host server reboot.
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.
Next, click on the Advance button. This will bring up the Advanced Settings
window. Under the General tab, click the “CHAP logon information” check
box, and fill in the CHAP name and Target secret information, and click OK.
Click OK in the Log On to Target window, and in the iSCSI Initiators
Properties windows. The volume should now show as Connected.
To view the details about the newly established volume, and trace the volume
from the SAN to the server, select the volume then click the Details button –
this will bring up the Target Properties window. Next, click the Devices tab
then the Advanced button. This will bring up the Device Details screen shown
on page 9 above, which shows the disk number assigned to the volume by the
host system, as seen under Disk Management. Use this as needed to trace
volumes from the SAN to the server.
Note: the device details will not appear until after the volume has been
initialized (formatted, etc.) on the host system.
Next, go to the Disk Management utility and format the volume for use as a
locally attached Basic Disk.
Finally, set the service dependency and bind the volumes through the iSCSI
initiator (See Section 7).
Note: This is a critical step to prevent applications from trying to start
prior to their volumes being present. Performing this step will delay
the start of applications until their bound volumes are present.