Accessing iSCSI storage
iSCSI LUs can be accessed through their targets using the Microsoft iSCSI Initiator. Discovered through iSNS or through the target portal, all iSCSI targets that are available will be displayed as available targets by the Initiator.
If its underlying volume is mounted read-only by the storage server, or if it is a snapshot copy of another LU, an iSCSI LU will also be read-only. In turn, if an LU is read-only, then any file systems contained within it will also be read-only. Clients accessing such read-only file systems will not be able to change any part of them, including file data, metadata or system files.
If Microsoft Windows clients are required to access read-only NTFS file systems over iSCSI, Microsoft Windows 2008 or Windows 2012 must be used.
Using iSNS to find iSCSI targets
Procedure
Navigate to the iSCSI Initiator Properties on your Windows system.
Open the iSCSI Initiator Properties dialog.
Select the Discovery tab.
In the iSNS Servers area, click Add to display the Add iSNS Server dialog.
Enter the IP address or DNS host name for the iSNS server.
Click OK to save the IP address or host name and return to the Discovery tab of the iSCSI Initiator Properties dialog.
If necessary, add another iSNS server.
NoteAfter the iSNS servers have been added, all available iSCSI targets that have been registered in iSNS will appear as available targets.Save your changes.
Verify your settings, and then click OK to save the iSNS servers or Cancel to decline.
Using target portals to find iSCSI targets
Procedure
Navigate to the iSCSI Initiator Properties on your Windows system.
Open the iSCSI Initiator Properties dialog.
Select the Discovery tab.
In the Target Portals area, click Add to display the Add Target Portal dialog.
Enter the file services IP address of the EVS.
Click OK to save the IP address and return to the Discovery tab of the iSCSI Initiator Properties dialog.
If necessary, add another target portal.
Save your changes.
Verify your settings, then click OK to save the list of target portals or Cancel to decline.
Accessing available iSCSI targets
To access an available iSCSI Target:
Procedure
Navigate to the iSCSI Initiator Properties on your Windows system.
Open the iSCSI Initiator Properties dialog.
Select the Targets tab.
Select a target.
Click Log On to display the Log On to Target dialog.
NoteEach logon starts an iSCSI session, and a maximum of 32 iSCSI sessions are allowed per Target.Click OK to log on to the target.
If authentication is enabled on the target, click Advanced... to open the General tab in the Advanced Settings dialog.
- Select the CHAP logon information checkbox and enter the Target secret (the password configured when the iSCSI target was created).
- If mutual authentication has been configured, select the Perform mutual authentication checkbox.
- Click OK to save the settings and return to the return to the Log On to Target dialog.
Optionally, configure multi-pathing.
If multi-pathing is supported by the Microsoft iSCSI initiator, and you want to use multiple paths to the target, fill the Enable multi-path checkbox.
To create multiple paths to the target, you must later start another session to the target.
Establish the connection.
Click OK to establish the connection to the selected target.
Verifying an active connection
Procedure
Navigate to the iSCSI Initiator Properties on your Windows system.
Open the iSCSI Initiator Properties dialog.
Select the Targets tab.
Look at the Status column for the target.
The Status column for the target should display "Connected."
Terminating an active connection
Procedure
Navigate to the iSCSI Initiator Properties on your Windows system.
Open the iSCSI Initiator Properties dialog.
Select the Targets tab.
Select the target with the connection you want to end.
Click Details to display the Target Properties dialog.
Select the session to terminate.
In the list of sessions, select the identifier for the session you want to end.
Click Log off... to terminate the session.
The initiator will attempt to close the iSCSI session if there are no applications currently using the devices.