ISCSI Whitepaper For Ix Series

WHITE PAPER
CONFIGURING iSCSI ON THE IOMEGA ®
STORCENTER PRO ix4-200r NAS SERVER

TM
AND HOW TO SET UP iSCSI SOFTWARE INITIATORS ON

WINDOWS®, LINUXTM, MAC®, & VMWARETM ESX PLATFORMS
Introduction 2
Terminology 2
Restrictions 3
iSCSI target configuration 3
Enabling iSCSI service 3
Configuring discovery methods 4
Determining authentication 5
Creating an iSCSI LUN 6
iSCSI initiator configuration on Windows 8
iSCSI initiator configuration on Linux 18
iSCSI initiator configuration on Mac 25
iSCSI initiator configuration on VMware ESX 30
iSCSI connection using StorCenter Manager 31
SUMMER 2009
STORCENTER IX4-200r NAS WITH VMWARE ESX SERVER 3.5
INTRODUCTION
Iomega StorCenter ix4-200r is both NAS and IP SAN storage device designed to serve small- and medium-sized
businesses that look for great reliability, ease of use, and ease of management characteristics. This document is
intended for system administrators who plan to store data on iSCSI logical units (LUNs) provided by a StorCenter ix4-
200r NAS server.
iSCSI (Internet Small Computer Systems Interface) is a transport protocol for sending SCSI packets over a TCP/IP
network. iSCSI initiators and targets are the key components in an iSCSI architecture. Initiators and targets are either
software or hardware devices that package and transfer SCSI information over an IP network. An iSCSI initiator
encapsulates SCSI commands, data, and status information in iSCSI packets and sends the packets to an iSCSI target
that resides on a storage device.
This document describes how to configure and manage iSCSI targets and LUNs on a StorCenter ix4-200r storage
server and how to configure iSCSI initiators on a Windows or Linux host system.
TERMINOLOGY
t CHAP: Challenge Handshake Authentication Protocol. Access control protocol for secure authentication using
shared passwords called secrets.
t Digest: iSCSI protocol error-checking method used to verify the integrity of an iSCSI packet header (header digest) or
payload data (data digest) using a checksum.
t iSCSI: Internet Small Computer System Interface. A protocol for sending SCSI packets over a TCP/IP network.
t iSNS: Internet Storage Name Service. Discovery and naming protocol designed to facilitate the automated discovery,
management, and configuration of iSCSI and Fibre Channel Protocol (FCP) devices on a TCP/IP network.
t iSCSI host: computer hosting an iSCSI initiator.
t iSCSI initiator: iSCSI endpoint, identified by a unique iSCSI name, which begins an iSCSI session by issuing a
command to the other endpoint (the target).
t IQN: iSCSI Qualified Name. Naming standard supported by the iSCSI protocol. IQN names are globally unique and
in the form of “iqn,” followed by a date and a reversed domain name.
t iSCSI target: iSCSI endpoint, identified by a unique iSCSI name, which executes commands issued by the iSCSI initiator.
t LU: Logical Unit. For iSCSI on an Iomega ix4-200r server, a logical unit is an iSCSI software feature that processes
SCSI commands, such as reading from and writing to storage media. From an iSCSI host perspective, a logical unit
appears as a disk device.
t LUN: Logical Unit Number. Identifying number of a SCSI or iSCSI object that processes SCSI commands. The LUN
is the last part of the SCSI address for a SCSI object. The LUN is an ID for the logical unit, but the term is often used
to refer to the logical unit itself.
White Paper 2
t LUN mask: A set of access permissions that identify which iSCSI initiator can access specific LUNs on a target.
t SCSI: Small Computer System Interface. Standard set of protocols for host computers communicating with attached
peripherals.
RESTRICTIONS
The following restrictions and limitations apply in the latest Lifeline 2.0 firmware release. They may be removed in
future releases without advance notice.
w The StorCenter ix4-200r supports a total of 32 iSCSI targets per device.
w Each iSCSI target on the StorCenter ix4-200r contains only one iSCSI LUN.
w The StorCenter ix4-200r does not support iSCSI digests.
w Each iSCSI session on the Iomega ix4-200r allows only one connection.
w Microsoft Multipath I/O (MPIO) is not currently supported by a StorCenter ix4-200r target.
w iSCSI snapshot and replication are not currently supported on a StorCenter ix4-200r.
w No Microsoft Volume Shadow Copy Service (VSS) provider is available on the StorCenter ix4-200r.
iSCSI TARGET CONFIGURATION

Enabling iSCSI service
iSCSI service is disabled on the StorCenter ix4-200r by default. To enable the service, go to Settings > iSCSI:
Figure 1: Enable iSCSI service
White Paper 3
Configuring target discovery methods
The StorCenter ix4-200r supports two ways of target discovery: the SendTargets command and using the Internet
Storage Name Service (iSNS) server. SendTargets is the simple and default discovery method; it requires an initiator to
know the IP address and port number of the target. The port number used is 3260, the default port defined in the
iSCSI protocol.
To utilize the iSNS method, go to Settings > iSCSI (Figure 1). From there, you can choose to use either a local iSNS
server integrated within your device, or you can specify the host name or IP address of an external iSNS server. When
using the built-in iSNS server, the server’s host name and IP address are the Iomega device name and IP address
respectively.
Enabling iSNS discovery does not preempt the SendTargets discovery method; both will be available. The Microsoft
iSCSI Initiator supports both discovery methods. However, the Open-iSCSI initiator and globalSAN iSCSI initiator
mentioned in this document do not support the iSNS discovery method.
Note: when using the SendTargets method, the IP address of a target is required. By default, the StorCenter ix4-200r
device assigns device IP dynamically using the DHCP protocol. To prevent the initiator from losing discovered targets
due to the Iomega device IP change, you should assign a static IP address to the Iomega device instead. To assign a
static IP, go to Settings > Network Services > Network Settings.
Figure 2 Assign a static IP address to the device
White Paper 4
Determining the target authentication mechanism

Independent from target discovery, the authentication mechanism determines how an iSCSI initiator logs on to a
target on the StorCenter ix4-200r device. Three authentication mechanisms are offered on the device:
w Mutual Challenge-handshake Authentication Protocol (CHAP): this is a global setting available from the Settings >
iSCSI page. You need to specify a CHAP secret if you choose this method. This is the device secret and must be the
same as specified in an initiator’s Mutual CHAP setting for the initiator to be able to log on.
Figure 3 Enable Mutual CHAP
w One-way CHAP: there is no setting for this option on the device. The user account that is granted access to an iSCSI
drive is needed during authentication. In this case, the CHAP name is the user name, and the target CHAP secret is
the user password. This is true whether the user account is in workgroup mode or Active Directory mode.
w Unsecured: when a drive is created but not secured, there is no CHAP authentication required. Any initiator can
access the target without authentication.
On the StorCenter ix4-200r, when a new iSCSI drive is created on the device, a single-drive target is created
automatically with the drive. If the drive is not secured, then the corresponding target will not require authentication
even if the global Mutual CHAP is enabled. If the drive is secured instead, then the corresponding target will use
Mutual CHAP if it is set, otherwise, the target will use one-way CHAP.
Note that an iSCSI initiator requires the CHAP secret length to be 12-16 characters if IPSec is not used. Therefore, you
should specify a CHAP secret within this range on your Mutual CHAP setting. In the case of one-way CHAP and the
user password is not within this range, you should pad the password with “*” to make it 12 characters long, or on the
other hand, truncate the password to 16 characters long in the initiator as the target CHAP secret.
White Paper 5
Note: In this white paper, the Mutual CHAP device secret is set to abcdefghijkl.
Creating an iSCSI LUN
To create an ISCSI LUN, go to Shared Storage and click Add:
Figure 4: Create an iSCSI drive
1. Select iSCSI Drive as the Shared Storage type.

2. Enter a name for the drive to be created.
3. Specify the size of the drive no less than 0.1GB.
4. By default Enable Security is checked to allow user access controls on the drive. If you uncheck this setting, the Next
button changes to Apply, and clicking it completes the creation of the iSCSI drive.
5. Click Next to configure user access control. All user accounts on the device, either created locally in the
WORKGROUP mode or imported from the Active Directory, can be specified with either read/write or no access to the
drive.
White Paper 6
Figure 5 Secure an iSCSI drive

6. Click Apply to complete the creation of the drive. A confirmation page is displayed:
Figure 6 Confirm a drive creation
7. Click OK to go back to the list of Shared Storage on the device, the newly created drive is listed. You can click
the icon to view the drive information, the icon to modify the drive, or the icon to delete the drive.
White Paper 7
Figure 7 List an iSCSI drive
Note: In this white paper, for demonstration purpose, the admin user account is granted read/write access to the drive.
The account’s password is set to 12345678. Since the account password is less than 12 characters long, you need to
pad it with * to make the target secret 12345678**** in initiators.
iSCSI INITIATOR CONFIGURATION ON WINDOWS
Installing the Microsoft iSCSI software initiator

For Windows Server 2008 servers, you do not need to download and install the iSCSI initiator software. The operating
system includes the iSCSI initiator software. For Windows Server 2003, Windows 2000, and Windows XP:
1. Go to http://www.microsoft.com and download the Microsoft iSCSI Software Initiator; the latest version is 2.08
published on Dec. 18, 2008.
2. Select and download the appropriate file, based on whether your system is x86, x64, or Itanium 64 architecture.
3. Run the executable to install the software initiator.
White Paper 8
Figure 8 Install Microsoft iSCSI initiator
Configuring the initiator

The software initiator needs to be configured before it connects to the StorCenter ix4-200r iSCSI storage.
1. Run the Microsoft iSCSI Initiator to bring up the configuration interface.
Figure 9 Run MS initiator
White Paper 9
2. If Mutual CHAP is enabled on the Iomega NAS device, click Secret to enter the device secret abcdefghijkl set
on the Iomega device.
Figure 10 Enter device secret
3. Click the Discovery tab to specify target discovery methods.

a. If using the SendTargets method, click Add below the Target Portals pane to enter the hostname or IP address of the
Iomega NAS device and the port number used for iSCSI service.
Figure 11 Specify SendTargets discovery
b. If using the iSNS method, click Add below the iSNS Servers pane to enter the hostname or IP address of the iSNS
server to be used. In our example, the device built-in iSNS server is used, so the IP address of the Iomega device is
entered.
Figure 12 Specify iSNS server
White Paper 10
4. After either the SendTargets information or iSNS server is specified, click the Targets tab to see the list of
targets available on the Iomega NAS device. The iSCSI drive created previously should be there with the status being
Inactive.
Figure 13 Select the iSCSI target
Connecting to an iSCSI target

After the iSCSI target is discovered, the initiator needs to log on before the drive provided by the target can be used.
The initiator will need to authenticate during logon according to the authentication mechanism set on the Iomega
device.
1. Select the target to connect, and click Log On.

2. Check Automatically restore this connection when the system boots so that the initiator automatically logs on to the
target every time the host reboots.
White Paper 11
Figure 14 Restore iSCSI connection automatically
a. If the iSCSI drive is not secured on the Iomega NAS device, click OK to log on to the target.
b. If the iSCSI drive is secured on the Iomega device, click Advanced to specify CHAP information. Check CHAP logon
information, and enter admin as the CHAP user name. Since the account password 12345678 is less than 12
characters long, you need to pad it with * to make the target secret 12345678****.
Figure 15 Specify CHAP logon information
c. If Mutual CHAP is enabled on the Iomega device, check Perform mutual authentication.
White Paper 12
3. Click OK to complete the logon process, the status of the target should now show as Connected.
Figure 16 Connect to the target
4. The target is a Persistent Target that the initiator will attempt to reconnect each time the computer is rebooted.
Figure 17 Show persistent targets
White Paper 13
Creating a disk
After the iSCSI initiator has logged on successfully, you can use the Microsoft Disk Management snap-in to locate the
iSCSI drive presented by the target and manage the drive.
1. Run compmgmt.msc to bring up Computer Management, and select Disk Management in the console tree.
Figure 18 Run Disk Management
2. The Iomega iSCSI drive will be displayed with the status being Unknown and Not Initialized. Select the drive, and
choose Action > All Tasks > Initialize Disk to initialize the drive.
Figure 19 Initialize the drive
3. Click OK and the disk status should be changed to Basic and Online. The disk is now available for use.
White Paper 14
4. Select the Unallocated disk, choose Action > All Tasks > New Partition to create a partition on the disk. The New
Partition Wizard is run.
5. Choose the type of partition you want to create.
Figure 20 Choose the partition type
6. Specify the partition size.
Figure 21 Specify the partition size
White Paper 15
7. Assign a drive letter to the partition.
Figure 22 Assign a drive letter
8. Format the partition to FAT, FAT32, or NTFS.
Figure 23 Format the partition
9. The iSCSI drive on the Iomega device is now ready to use on the host just like a local hard disk.
White Paper 16
Figure 24 Complete disk management

Logging off an iSCSI target
To log off and remove a specific target on the Iomega storage device, you must use the Microsoft iSCSI Initiator again.
Ensure that there is no active I/O to the iSCSI drive from the host, otherwise, you risk data integrity being
compromised.
1. Run the Microsoft iSCSI Initiator to bring up the configuration interface.

2. Go to Targets and select the target to be logged off, then click Details.
Figure 25 Log off a target
White Paper 17
3. Check the target identifier and click Log off and then click OK. The target status changes to Inactive and the iSCSI
drive is no longer available to the host.
iSCSI INITIATOR CONFIGURATION ON LINUX

There are a few iSCSI software initiators for the Linux platform. In theory, as long as an initiator implements the iSCSI
protocol correctly, it should be able to connect successfully to a target on the StorCenter ix4-200r. The Open-iSCSI
initiator is a popular choice in the Linux community, and is the only Linux iSCSI software initiator that has been
qualified by Iomega.
Installing the Open-iSCSI software initiator

The Open-iSCSI software initiator is bundled in the latest releases of Redhat and SuSE Linux servers. If your Linux
installation does not contain the initiator, you can either go to your Linux vendor’s web site or the Open-iSCSI
(http://www.open-iscsi.org) web site to download the package for installation.
Starting the Open-iSCSI software initiator

The Open-iSCSI persistent configuration is implemented as a DBM database and contains two tables: discovery and
node. These iSCSI database tables are typically located in /var/lib/open-iscsi/ on SuSE and /var/lib/iscsi/ on RedHat.
1. For an existing StorCenter ix4-200r storage device with initiator CHAP already configured, stop the iSCSI service on
the Linux host.
RedHat:
/etc/init.d/iscsi stop
SuSE:
/etc/init.d/open-iscsi stop
2. Set the run levels for the iSCSI service to start automatically on reboot and shutdown:
RedHat:
chkconfig --level 345 iscsid on
SuSE:
chkconfig –s open-iscsi 345
chkconifg –s open-iscsi on
3. Start the iSCSI service.

RedHat:
/etc/init.d/iscsi start
SuSE:
/etc/init.d/open-iscsi start
White Paper 18

Before you discover and connect to a target, please make sure you configure the CHAP authentication settings. If the
target is not secured, you can skip this section.
Note: the settings in the iscsid.conf file are global to the initiator. It means that the initiator will try to connect to all
iSCSI targets using these settings by default. However, you can specify these settings using Open-iSCSI commands for
an individual target connection. Please skip this section if you do not want to set these variables globally.
1. Open the /etc/iscsi/iscsid.conf file on RedHat or /etc/iscsid.conf file on SuSE with vi or another editor.
2. Uncomment (remove the # symbol) before the following variable settings and enter the values accordingly:
node.startup = automatic
node.session.auth.authmethod = CHAP
node.session.auth.username = admin
node.session.auth.password = 12345678****
3. If Mutual CHAP is enabled on the Iomega device, set the following variables:
node.session.auth.username_in = iscsi
node.session.auth.password_in = abcdefghijkl

The Open-iSCSI initiator command iscsiadm is used to administer iSCSI connections. The command is normally
placed in the /sbin directory.
1. Run the following command to discover targets available on the StorCenter ix4-200r. The command will return a list
of targets.
# iscsiadm –m discovery –t sendtargets –p 10.6.126.153:3260
10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.WLKLUN2
10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.W2K3LUN
10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.RepliStorLUN
10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.W2K8LUN
10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.XPLUN
10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN
10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.EXCHANGELUN
10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.ESXLUN
10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.EXCHANGELOG
White Paper 19
2. Skip to step 5 if the target is not secured.
3. Run the following commands to specify CHAP settings for the target if you haven’t set the global settings previously
in iscsid.conf.
# iscsiadm -m node -T iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN -p 10.6.126.153 --op update -n
node.session.auth.authmethod -v CHAP
node.session.auth.username -v admin
node.session.auth.password -v 12345678****
4. If Mutual CHAP is enabled on the Iomega device, run the following commands if you haven’t set the global settings
previously in iscsid.conf.
node.session.auth.username_in -v iscsi
node.session.auth.password_in -v abcdefghijkl
5. Run the following command to automatically restore the iSCSI connection to the target each time the host is
rebooted if you haven’t set the global setting previously in iscsid.conf.
# iscsiadm -m node -T iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN -p 10.6.126.153 --op update -n node.startup
-v automatic
6. Run the following command to log on to the target.

# iscsiadm -m node -T iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN -p 10.6.126.153:3260 –l
If you are running SuSE 10 or higher, you can alternatively use the YaST utility.
1. Open the YaST utility.
2. Select Network Services > iSCSI Initiator > iSCSI Initiator Overview.
Figure 26 Open YaST iSCSI initiator tool
White Paper 20
3. In the Connected Targets tab, click Add to discover targets.
Figure 27 Discover targets in the YaST iSCSI initiator tool
4. Click Next and all the targets on the Iomega device are listed.
Figure 28 Display targets in the YaST iSCSI initiator tool
5. Select the target to log on and click Connect. If the target is not secured, check No Authentication and proceed.
White Paper 21
6. If the target is secured, enter the Username and Password for Outgoing Authentication as admin and 12345678****
respectively. If Mutual CHAP is enabled on the Iomega device, enter the Username and Password for Incoming
Authentication as iscsi and abcdefghijkl respectively.
Figure 29 Specify CHAP authentication in the YaST iSCSI initiator tool
7. The target is logged on and the status should change to True.
Figure 30 Log on to a target in the YaST iSCSI initiator tool
White Paper 22
8. Click Next and change the start-up mode from manual to automatic by clicking the Toggle Start-Up button.
Figure 31 Change start-up mode in YaST iSCSI initiator tool
Creating a disk
After the iSCSI initiator has logged on successfully, you can use the Linux fdisk utility to manage the iSCSI drive.
1. A new SCSI drive is listed in the directory /dev after the iSCSI target logon. However, the device will not always have
the same name each time the host is booted. Run the following command to find out which device is the iSCSI drive:
# ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root 9 May 29 19:04 ip-10.6.126.153:3260-iscsi-iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN ->
../../sdb
lrwxrwxrwx 1 root root 9 May 28 23:55 pci-0000:00:07.1-ide-0:0 -> ../../hda
lrwxrwxrwx 1 root root 9 May 28 23:55 pci-0000:00:10.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 May 28 23:55 pci-0000:00:10.0-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 May 28 23:55 pci-0000:00:10.0-scsi-0:0:0:0-part2 -> ../../sda2
2. From the return you can see the iSCSI drive on the Iomega NAS device is mapped to /dev/sdb. Run the following
command to create a partition on the disk.
# fdisk /dev/sdb
White Paper 23
3. At the prompt, enter n to create a new partition, and use the default values to create a primary partition.
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-261, default 1): 1
Last cylinder or +size or +sizeM or +sizeK (1-261, default 261): 261
4. At the prompt, enter w to save the partition.

Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.

Syncing disks.
5. Create a file system in the partition. You can create any type of file system supported on Linux. In this white paper,
ext3 is chosen as the example.
# /sbin/mkfs.ext3 /dev/sdb1
6. vi or use another editor to open /etc/fstab and add an entry in the mount table.
/dev/sdb1 /iomega_iscsi ext3 _netdev 00
7. Create a directory as the file system mount point, and mount the newly created file system.
# mkdir /iomega_iscsi
# mount /iomega_iscsi

To log off and remove a specific target on the Iomega NAS storage device, you can use the Open-iSCSI command
again. Ensure that there is no active I/O to the iSCSI drive from the host, otherwise, you risk data integrity being
compromised.
1. Run the following command to log out the target.
# iscsiadm -m node -T iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN -p 10.6.126.153:3260 –u
2. Alternatively, if you are running SuSE 10 or higher, go to YaST and click Log Out as shown in Figure 30.
White Paper 24
iSCSI INITIATOR CONFIGURATION ON MAC

There are a few iSCSI software initiators for the Mac OS X platform. In theory, as long as an initiator implements the
iSCSI protocol correctly, it should be able to connect to a target on the StorCenter ix4-200r successfully. The globalSAN
iSCSI Initiator is a popular choice in the Mac community and is the only Mac iSCSI software initiator that has been
qualified by Iomega.
Installing the globalSAN software initiator

1. Go to http://wwww.studionetworksolutions.com and download the globalSAN iSCSI initiator.
2. Run the installation package.
3. After installation is done, restart the host.

The software initiator needs to be configured before it connects to the StorCenter ix4-200r iSCSI storage.
1. Run the globalSAN iSCSI initiator in System Preferences.
Figure 32 Run globalSAN initiator
2. Click + in the Portals tab to add the Iomega device.
Figure 33 Add a portal in globalSAN
White Paper 25
3. Enter the IP address and port number.
Figure 34 Enter iSCSI server address
4. Click OK and the list of targets on the Iomega NAS device is displayed in the Targets tab.
Figure 35 List targets in the globalSAN initiator
White Paper 26

After the iSCSI target is discovered, the initiator needs to log on before the drive provided by the target can be used.
The initiator will need to authenticate during logon according to the authentication mechanism set on the Iomega
device.
1. Select the target to connect, check Persistent so that the initiator automatically logs on to the target every time the
host reboots. Then click Connected.
a. If the target is not secured, click Connect to proceed.
b. If the target is secured, check Use CHAP Login Information and enter admin and 12345678**** in the User Name
and Target Secret fields, respectively.
c. If Mutual CHAP is enabled on the Iomega device, enter abcdefghijkl in the Initiator Secret field.
Figure 36 Configure CHAP in globalSAN initiator
2. Click Connect to proceed. The first time you log on to the target, a popup message is shown to remind you the disk
is not initialized.
White Paper 27
Figure 37 Connect to the target
Creating a disk
1. Click Initialize in Figure 36 to bring up the Disk Utility.
Figure 38 Initialize the iSCSI drive
White Paper 28
2. Go to the Partition tab, select 1 Partition in the Volume Scheme dropdown list, enter a name for the partition to be
created, and select the file system format for the partition.
Figure 39 Format the iSCSI drive
3. Click Apply to create the partition. The disk is now ready for use.
Figure 40 Disk ready for use

To log off and remove a specific target on the Iomega storage device, you must use the globalSAN iSCSI software
initiator again. Ensure that there is no active I/O to the iSCSI drive from the host, otherwise, you risk data integrity
being compromised.
1. Select the disk named Iomega-iSCSI and eject it.

2. Go to the globalSAN initiator, select the target to be logged off, and click Connected.
3. Click Disconnect in the popup window.
White Paper 29
Figure 41 Disconnect a target
iSCSI INITIATOR CONFIGURATION ON VMWARE ESX

VMware ESX Server can use iSCSI drives to create VMFS datastores or present the drives as Raw Device Mapping
(RDM) disks to guest virtual machines directly. For details about how to configure iSCSI on VMware ESX Server 3.5,
refer to the document StorCenter ix4-200r with VMware ESX Server White Paper on http://www.iomega.com/nas.
Note: VMware ESX Server 3.5 does not explicitly support Mutual CHAP authentication. To use iSCSI on the StorCenter
ix4-200r, do not enable Mutual CHAP on the Iomega device.
VMware ESX Server 4.0 adds support for Mutual CHAP. Follow the steps below to configure CHAP authentication. The
rest of the iSCSI configuration process remains the same as on VMware ESX Server 3.5.
1. Click CHAP on the General tab of the iSCSI Initiator Properties.
Figure 42 Specify CHAP configuration on VMware ESX 4.0
White Paper 30
2. Select Required from the Select option in the CHAP pane, then enter admin and 12345678**** for the Name and
Secret, respectively.
3. Select Required from Select option in the Mutual CHAP pane, then enter iscsi and abcdefghijkl for the Name and
Secret, respectively.
Figure 43 Configure Mutual CHAP on VMware ESX 4.0
iSCSI INITIATOR CONFIGURATION USING THE IOMEGA STORCENTER MANAGER

To simplify use of iSCSI, the Iomega StorCenter Manager that comes with your Iomega NAS device has the iSCSI
initiator support built-in for the Windows platform. With this support, you can manage an iSCSI drive from within the
StorCenter Manager. However, you must first install the Microsoft iSCSI Initiator on your machine, the client software
calls APIs of the initiator to perform tasks including logon, mapping, formatting, etc. Note that only a user account
with Administrator privileges can use this feature.
To install the Microsoft iSCSI Initiator, refer to section Installing the Microsoft iSCSI software initiator in this document.
After the Microsoft initiator is installed, a new connect icon displays next to the iSCSI drive on the Shared Storage
page. You click this icon to connect the iSCSI drive..
White Paper 31
Figure 44 Manage iSCSI from client software
1. Click the icon, The Connect iSCSI Drive page opens. Specify the drive letter to use.
Figure 45 Specify connection information
2. If Mutual CHAP is enabled on the Iomega device, the Device Secret field will display. Enter the secret abcdefjhijkl.
Because you are logged in to the StorCenter Manager as the Admin user, the software knows the CHAP user name and
secret. There is no need to supply the initiator CHAP information here.
White Paper 32
3. Check Format Using and select either NTFS or FAT32 to format the iSCSI drive.
4. Click Apply. Upon completion, the client software formats the iSCSI drive in the background, and when done,
presents the drive to the host just like a local hard disk mounted at the drive letter you specified. The flag turns
into .
Figure 46 Connect an iSCSI drive with client software
5. To disconnect the drive from the host, click from the client software.
©2009 Iomega Corporation. All rights reserved. Iomega, StorCenter, and the stylized “i” logo are either registered trademarks or trademarks of Iomega Corporation in the United States and/or other countries. EMC, Lifeline, and Retrospect are registered trademarks of
EMC Corporation in the U.S. and/or other countries. VMware is a registered trademark of VMware, Inc. Linux is a registered trademark of Linus Torvalds. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries. Macintosh and Mac are either registered trademarks or trademarks of Apple Computer Inc. in the United States and/or other countries. Certain other product names, brand names and company names may be trademarks or designations or their
respective owners. Iomega's specific customer support policies (including fees for services) and procedures change as technology and market conditions dictate. Product in photos may vary slightly from product in package. Product capacities are specified in gigabytes
(GB), where 1GB = 1,000,000,000 Bytes. To obtain information about Iomega’s current policies please visit Iomega at www.iomega.com or call 1-888-4iomega (1-888-446-6342). iSWP-0909-01

ISCSI Whitepaper For Ix Series

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ISCSI Whitepaper For Ix Series

Hochgeladen von

Copyright:

Verfügbare Formate

WHITE PAPER

CONFIGURING iSCSI ON THE IOMEGA ®

STORCENTER PRO ix4-200r NAS SERVER

AND HOW TO SET UP iSCSI SOFTWARE INITIATORS ON

iSCSI TARGET CONFIGURATION

Figure 1: Enable iSCSI service

Configuring target discovery methods

Figure 2 Assign a static IP address to the device

Determining the target authentication mechanism

Figure 3 Enable Mutual CHAP

Creating an iSCSI LUN

To create an ISCSI LUN, go to Shared Storage and click Add:

Figure 4: Create an iSCSI drive

1. Select iSCSI Drive as the Shared Storage type.

Figure 5 Secure an iSCSI drive

Figure 6 Confirm a drive creation

Figure 7 List an iSCSI drive

iSCSI INITIATOR CONFIGURATION ON WINDOWS

Installing the Microsoft iSCSI software initiator

Figure 8 Install Microsoft iSCSI initiator

Configuring the initiator

Figure 9 Run MS initiator

Figure 10 Enter device secret

3. Click the Discovery tab to specify target discovery methods.

Figure 11 Specify SendTargets discovery

Figure 12 Specify iSNS server

Figure 13 Select the iSCSI target

Connecting to an iSCSI target

1. Select the target to connect, and click Log On.

Figure 14 Restore iSCSI connection automatically

Figure 15 Specify CHAP logon information

Figure 16 Connect to the target

Figure 17 Show persistent targets

Figure 18 Run Disk Management

Figure 19 Initialize the drive

Figure 20 Choose the partition type

6. Specify the partition size.

Figure 21 Specify the partition size

7. Assign a drive letter to the partition.

Figure 22 Assign a drive letter

8. Format the partition to FAT, FAT32, or NTFS.

Figure 23 Format the partition

Figure 24 Complete disk management

1. Run the Microsoft iSCSI Initiator to bring up the configuration interface.

Figure 25 Log off a target

iSCSI INITIATOR CONFIGURATION ON LINUX

Installing the Open-iSCSI software initiator

Starting the Open-iSCSI software initiator

3. Start the iSCSI service.

Configuring the initiator

Connecting to an iSCSI target

2. Skip to step 5 if the target is not secured.

6. Run the following command to log on to the target.

Figure 26 Open YaST iSCSI initiator tool

3. In the Connected Targets tab, click Add to discover targets.

Figure 27 Discover targets in the YaST iSCSI initiator tool

Figure 28 Display targets in the YaST iSCSI initiator tool

Figure 29 Specify CHAP authentication in the YaST iSCSI initiator tool

7. The target is logged on and the status should change to True.

Figure 30 Log on to a target in the YaST iSCSI initiator tool

Figure 31 Change start-up mode in YaST iSCSI initiator tool

4. At the prompt, enter w to save the partition.

Calling ioctl() to re-read partition table.