This section assists you in configuring your DS300 so that the host can detect the storage. Refer to the ServeRaid Manager User’s Guide for complete details. If you are here as the result of a problem, make sure that the ServeRaid Access Control List (ACL) contains the initiator iqn(s) and that logical drives have been mapped to the host.
The host may be configured with a generic NIC or an iSCSI HBA.
· If you use the IBM 4010 iSCSI HBA (IBM Option PN 73P3601), use the drivers and utilities supplied with that adapter to perform the connection to the DS300. See QLA4010 configuration.
Using Microsoft iSCSI Software Initiator
Attention: If your system has an iSCSI HBA such as IBM iSCSI server adapter, IBM Option PN 73P3601 (QLA4010C), use the drivers and management software to configure the storage. See QLA4010 configuration.
In order for the system to detect your storage follow these general steps:
1.
Start the iSCSI Initiator by
clicking on the iSCSI Initiator icon on your Desktop.
2.
Click the Initiator Settings tab
to retrieve the initiator IQN. You can copy the Initiator iSCSI name so that you
can paste it in the ServeRaid Manager. See Figure 1.
3.
From a ServeRaid Manager session, right-click the enclosure and select Configure
Enclosure from the pop-up menu. Create an array and logical drives.
4.
From the ServeRaid Manager Access
Control – Add an iSCSI Initiator dialog, assign the array to the initiator IQN.
You can now assign the logical drives to the initiator using its alias. See Figure 6 and 7.
5.
Make sure the DS300 iSCSI port
addresses have been set. See Setting up
your DS300 for network connection.
You
should have connection to your iSCSI port via a Gb switch.
6.
From the iSCSI Initiator dialog,
select the Target Portals tab and click the Add button. Enter the IP
address of the controller iSCSI port(s). Leave the Socket value at the default.
Click OK. See Figure 2.On
the Available Targets tab, you should see the IQN numbers of the inactive
device(s) from the array you created. See Figure 3.
7.
To activate the devices and
establish a session, log on to the targets. See Figure 4.
8.
You should now be able to view
the new devices in the Disk Management window in the Computer Management dialog
and create NTFS Windows volumes.
Notes:
1) The SW initiator does
not support dynamic disks.
2) The Microsoft iSCSI initiator service supports the concept of persistent targets. This means that initiators always reconnect to a target whenever the computer is rebooted. In this way the devices on the target should always be connected to the connected to the computer at all times.
3) If you encounter a situation where your computer takes a long time to display the login prompt after booting or takes a long time to login after entering your login credentials, then there may be an issue related to the Microsoft iSCSI initiator service starting. Check the system eventlog to see if there is an event “Timeout waiting for iSCSI persistently bound volumes…”. If this is the case then one or more of the persistently bound volumes did not reappear after reboot which could be due to network or target error.
Figure 1 – Initiator Settings dialog
Figure 2 – Target Portals dialog
Figure 3 – Available Targets dialog
Figure 4 – Available Targets Log On dialog
To enable the system to detect your storage, perform the following general steps:
1.
Open the SANsurfer
Control IX application on the Host that has the HBA. Click here for the
complete SANsurfer Control IX User’s Guide or check for the
latest information in the DS300
Support web site.
2.
Select the HBA Options tab and note the HBA
iSCSI Name and the HBA Alias Name. See Figure 5.
You can copy the HBA iSCSI name so that you can paste it to the ServeRaid
Manager. At this time assign the IP address to this HBA so that it is on the
same subnet as the DS300 iSCSI port.
3.
From a ServeRaid Manager session,
right-click the enclosure and select Configure Enclosure from the pop-up
menu. Create an array and logical drives.
4.
From the ServeRaid Manager Access
Control – Add an iSCSI Initiator dialog assign the array to the initiator IQN.
You can now assign the logical drives to the initiator using its alias. See Figure 6a and 7a.
5.
Make sure the DS300 iSCSI port
addresses have been set. See Setting up
your DS300 for network connection.
You should have a connection from your HBA to your iSCSI port via a Gb switch.
6. You can now connect the controller to the HBA. Select the Target Settings tab and click the + button. Enter the IP address of the controller port that this HBA can access. See Figure 8.
7.
Click Save to save the
configuration. SANSurfer Control will discover the
targets. See Figure 9.
Important: Any changes to the configuration that are made in the Target Settings tab (adding or deleting targets etc.) must be saved to take effect.
The default administrator PW for SanSurfer
Control is: config.
For security reasons you should change it immediately. See the SanSurfer Control User’s Guide for information.
8.
You should now be able to view
the new devices in the Disk Management window in the Computer Management dialog
and create NTFS Windows volumes.
Figure 5 – SANSurfer Control
HBA Options dialog
Figure 8 – SANSurfer Control
Target Settings dialog
Figure 9 – SANSurfer Control Target Settings – Target Discoveries dialog
Note: The No Connection Active state shown for 191.1.9.3 is the sendtargets connection status. After the sendtargets discovery finishes (shown as Session Active), this connection is closed.
Linux iSCSI Software
Initiator
The Linux iSCSI Software Initiator can be
downloaded from http://linux-iscsi.sourceforge.net/.
A very good guide to assist you in the installation and configuration of the
initiator can be found at http://www.cuddletech.com/articles/iscsi.