iscsi wp 0211

IOMEGA ISCSI SETUP GUIDEThis white paper describes how to configure iSCSI on an Iomega StorCenterTM network storage

device and how to set up iSCSI software initiators on the Windows, Linux, Mac, and VMware

ESX platforms.

WHITE PAPER

JANUARY 2011

ISCSI INITIATOR CONFIGURATION ON LINUX 20Installing the Open-iSCSI software initiator 20Starting the Open-iSCSI software initiator 20Configuring the initiator 20Connecting to an iSCSI target 21Creating a disk 26Logging off an iSCSI target 27

ISCSI INITIATOR CONFIGURATION ON MAC 27Installing the globalSAN software initiator 27Configuring the initiator 27Connecting to an iSCSI target 29Creating a disk 31Logging off an iSCSI target 32

ISCSI INITIATOR CONFIGURATION ON VMWARE ESX 33

ISCSI CONNECTION USING THE IOMEGA STORCENTER MANAGER 34

INTRODUCTION 2

TERMINOLOGY 2

RESTRICTIONS 3

ISCSI TARGET CONFIGURATION 3Enabling iSCSI service 3Configuring target discovery methods 4Determining the target authentication mechanism 5Creating an iSCSI LUN 6

ISCSI INITIATOR CONFIGURATION ON WINDOWS 10Installing the Microsoft iSCSI software initiator 10Configuring the initiator 11Connecting to an iSCSI target 13Creating a disk 16Logging off an iSCSI target 19

INTRODUCTIONIomega StorCenter is both a NAS and IP SAN storage device designed to serve small- and medium-sizedbusinesses looking for great reliability, ease of use, and ease of management. This document is intended forsystem administrators who plan to store data on iSCSI logical units (LUNs) provided by an Iomega StorCenter.

iSCSI (Internet Small Computer Systems Interface) is a transport protocol for sending SCSI packets over aTCP/IP network. iSCSI initiators and targets are the key components in an iSCSI architecture. Initiators andtargets 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 thepackets to an iSCSI target that resides on a storage device.

This document describes how to configure and manage iSCSI targets and LUNs on an Iomega StorCenternetwork storage device and how to configure iSCSI initiators on a Windows or Linux host system.

TERMINOLOGYCHAP: Challenge Handshake Authentication Protocol. Access control protocol for secure authentication usingshared passwords called secrets.

Digest: iSCSI protocol error-checking method used to verify the integrity of an iSCSI packet header (header digest) orpayload data (data digest) using a checksum.

iSCSI: Internet Small Computer System Interface. A protocol for sending SCSI packets over a TCP/IP network.

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.

iSCSI host: Computer hosting an iSCSI initiator.

iSCSI initiator: iSCSI endpoint, identified by a unique iSCSI name, which begins an iSCSI session by issuing a commandto the other endpoint (the target).

IQN: iSCSI Qualified Name. Naming standard supported by the iSCSI protocol. IQN names are globally unique and inthe form of iqn, followed by a date and a reversed domain name.

iSCSI target: iSCSI endpoint, identified by a unique iSCSI name, which executes commands issued by the iSCSI initiator.

LU: Logical Unit. For iSCSI on an Iomega StorCenter, a logical unit is an iSCSI software feature that processes SCSIcommands, such as reading from and writing to storage media. From an iSCSI host perspective, a logical unit appearsas a disk device.

LUN: Logical Unit Number. Identifying number of a SCSI or iSCSI object that processes SCSI commands. The LUN isthe 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 torefer to the logical unit itself.

LUN mask: A set of access permissions that identify which iSCSI initiator can access specific LUNs on a target.

SCSI: Small Computer System Interface. Standard set of protocols for host computers communicating withattached peripherals.

White Paper 2

IOMEGA ISCSI SETUP GUIDE

RESTRICTIONSThe following restrictions and limitations apply in the latest LifeLine firmware release. They may be removed infuture releases without advance notice.

The Iomega StorCenter ix2-200, ix4-200d , and ix4-200r supports a total of 32 iSCSI targets per device.The Iomega StorCenter ix12-300r supports a total of 256 iSCSI targets per device.

Each iSCSI target on the Iomega StorCenter contains only one iSCSI LUN.

The Iomega StorCenter devices do not support iSCSI digests.

Each iSCSI session on the Iomega StorCenter device allows only one connection.

Microsoft Windows 2008 and 2008 R2 Clusters are currently not supported by an Iomega StorCenter target.Windows 2003 Clusters are supported.

iSCSI snapshot and replication are not currently supported on an Iomega StorCenter.

No Microsoft Volume Shadow Copy Service (VSS) provider is available on the Iomega StorCenter.

ISCSI TARGET CONFIGURATIONEnabling iSCSI serviceiSCSI service is disabled on the Iomega StorCenter by default. To enable the service, go to Settings > iSCSI:

Figure 1 Enable iSCSI service

White Paper 3


Configuring target discovery methodsThe Iomega StorCenter supports two ways of target discovery: the SendTargets command and using the InternetStorage Name Service (iSNS) server. SendTargets is the simple and default discovery method; it requires aninitiator to know the IP address and port number of the target. The port number used is 3260, the default portdefined in the iSCSI protocol.

To utilize the iSNS method, go to Settings > iSCSI (Figure 1). From there, you can choose to use either a localiSNS server integrated within your device, or you can specify the host name or IP address of an external iSNSserver. When using the built-in iSNS server, the servers host name and IP address are the Iomega device nameand IP address, respectively.

Enabling iSNS discovery does not preempt the SendTargets discovery method; both will be available. TheMicrosoft iSCSI Initiator supports both discovery methods. However, the Open-iSCSI initiator and globalSANiSCSI 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 IomegaStorCenter device assigns device IP dynamically using the DHCP protocol. To prevent the initiator from losingdiscovered targets due to the Iomega StorCenter device IP change, you should assign a static IP address to theIomega StorCenter 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 mechanismIndependent from target discovery, the authentication mechanism determines how an iSCSI initiator logs onto a target on the Iomega StorCenter device. Three authentication mechanisms are offered on the device: 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 secretand must be the same as specified in an initiators Mutual CHAP setting for the initiator to be able to log on.

Figure 3 Enable Mutual CHAP

One-way CHAP: there is no setting for this option on the device. The user account that is granted access toan iSCSI drive is needed during authentication. In this case, the CHAP name is the user name, and thetarget CHAP secret is the user password. This is true whether the user account is in workgroup mode orActive Directory mode.

Unsecured: when a drive is created but not secured, there is no CHAP authentication required. Any initiatorcan access the target without authentication.

When a new iSCSI drive is created on the Iomega StorCenter device, a single-drive target is createdautomatically with the drive. If the drive is not secured, then the corresponding target will not requireauthentication even if the global Mutual CHAP is enabled. If the drive is secured instead, then thecorresponding target will use Mutual CHAP if it is set, otherwise, the target will use one-way CHAP.

White Paper 5


White Paper 6

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 ofone-way CHAP and the user password is not within this range, you should pad the password with * to makeit 12 characters long, or on the other hand, truncate the password to 16 characters long in the initiator as thetarget CHAP secret.

Note: In this white paper, the Mutual CHAP device secret is set to abcdefghijkl.

Creating an iSCSI LUNStarting with Release 2.6.17.27268 of LifeLine on the Iomega StorCenter ix12-300r there are two options to createan iSCSI LUN:

1. Volume-based iSCSI LUN

2. File-based iSCSI LUN

To create a volume-based iSCSI LUN you first create a new Storage Pool. Go to Settings > Storage Pools:

Figure 4 Storage Pools


White Paper 7

To add a new Storage Pool, click on the plus sign The Add Storage Pool popup opens.

Figure 5 Add Storage Pool

1. Enter a name for the pool.

2. To change the protection, choose a value from the drop-down menu:

3. Check Enable periodic consistency check to enable a monthly parity or mirror consistency check. The checkhelps prevent a single drive failure from becoming a two-drive failure, resulting in data loss. The check runs forseveral hours and can affect performance of the Iomega StorCenter device. If you do not want to run the check,uncheck this option.

4. Check Use to create volume-based iSCSI drives. Notice, that the Use as default folder location checkbox willdisappear. After the Storage Pool is created, you cannot modify this option, and no folders can be added to it.

5. Select the checkbox of the drive you want to add to the pool. All drives in a pool must be the same size.

6. Click Apply to add the new Storage Pool. The new Storage Pool displays in a table on the Storage Pools page.

The iSCSI LUN is created after the Storage Pool.


Drive Protection

Mirror (RAID 10)

Parity (RAID 5)

Double Parity (RAID 6)

None

Description

Uses half of the storage space for protection, leaving half for actual data.

Uses one drive for protection.

Combines six or more drives in a way that protects data against loss of any two drives.

Turns off data protection and leaves your data vulnerable to data loss.

White Paper 8

The procedures for creating volume-based and file-based iSCSI LUNs are the same, the only difference is whichtype of storage pool is used. The next step shows how to create a volume-based iSCSI LUN by using the newly-created storage pool.

Go to Shared Storage and click Add:

Figure 6 Create an iSCSI drive

1. Select iSCSI Drive as the Shared Storage type.

2. Enter a name for the drive to be created.

3. Select the new iSCSI pool as the Storage Pool to create a volume-based iSCSI LUN. You can also select aStorage Pool containing Shared Folders to create a file-based iSCSI LUN.

4. Specify the size of the drive no less than 0.1GB.

5. Enable security is checked by default 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.


White Paper 9

Click Next to configure user access control. All user accounts on the device, either created locally in the WORKGROUPmode or imported from the Active Directory, can be specified with either read/write or no access to the drive.

Figure 7 Secure an iSCSI drive

1. Click Apply to complete the creation of the drive. A confirmation page displays:

Figure 8 Confirm a drive creation


2. Click OK to return to the list of Shared Storage on the device. The newly created drive is listed. You can clickthe icon to view the drive information, the icon to modify the drive, or the icon to delete the drive.

The volume-based iSCSI LUN DemoLUN is part of the dedicated iSCSI Storage Pool iSCSI-Pool, while the file-basediSCSI LUN XenTest1 is part of the Storage Pool SP0, which also contains the Shared Volumes Backup, Documents,and others.

Figure 9 List an iSCSI drive

Note: In this white paper, for demonstration purposes, the admin user account is granted read/write access to thedrive. The account password is set to 12345678. Since the account password is less than 12 characters in length,pad it with * to make the target secret 12345678**** in initiators.

ISCSI INITIATOR CONFIGURATION ON WINDOWSInstalling the Microsoft iSCSI software initiatorFor Windows Server 2008 servers, you do not need to download and install the iSCSI initiator software. The operatingsystem includes the iSCSI initiator software. For Windows Server 2003, Windows 2000, and Windows XP:

1. Go to http://www.microsoft.com and download the latest version of the Microsoft iSCSI Software Initiator.

2. Select and download the appropriate file, based on whether your system is x86, x64, or Itanium 64 architecture.

White Paper 10


White Paper 11

3. Run the executable to install the software initiator.

Figure 10 Install Microsoft iSCSI initiator

Configuring the initiatorThe software initiator needs to be configured before it connects to the Iomega StorCenter iSCSI storage.

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

Figure 11 Run MS initiator


White Paper 12

2. If Mutual CHAP is enabled on the Iomega NAS device, click Secret to enter the device secret abcdefghijkl seton the Iomega device.

Figure 12 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 addressof the Iomega NAS device and the port number used for iSCSI service.

Figure 13 Specify SendTargets discovery

b. If using the iSNS method, click Add below the iSNS Servers pane to enter the hostname or IP address of theiSNS server to be used. In our example, the device built-in iSNS server is used, so the IP address of the Iomegadevice is entered.

Figure 14 Specify iSNS server


White Paper 13

4. After either the SendTargets information or iSNS server is specified, click the Targets tab to see the list of targetsavailable on the Iomega NAS device. The iSCSI drive created previously should be there with the status being Inactive.

Figure 15 Select the iSCSI target

Connecting to an iSCSI targetAfter the iSCSI target is discovered, the initiator needs to log on before the drive provided by the target can be used. Theinitiator 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.


White Paper 14

2. Check Automatically restore this connection when the system boots so that the initiator automatically logs onto the target every time the host reboots.

Figure 16 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 CHAPlogon information, and enter admin as the CHAP user name. Since the account password 12345678 is less than12 characters in length, pad it with * to make the target secret 12345678****.

Figure 17 Specify CHAP logon information

c. If Mutual CHAP is enabled on the Iomega device, check Perform mutual authentication.


White Paper 15

3. Click OK to complete the logon process. The status of the target should now show as Connected.

Figure 18 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 19 Show persistent targets


White Paper 16

Creating a diskAfter the iSCSI initiator has logged on successfully, you can use the Microsoft Disk Management snap-in to locatethe 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 20 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 21 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 17

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 22 Choose the partition type

6. Specify the partition size.

Figure 23 Specify the partition size


White Paper 18


7. Assign a drive letter to the partition.

Figure 24 Assign a drive letter

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

Figure 25 Format the partition

White Paper 19

MANAGING IOMEGA IX12-300R NETWORK STORAGE ARRAY FOR WINDOWS USER ACCESS

9. The iSCSI drive on the Iomega device is now ready to use on the host just like a local hard disk.

Figure 26 Complete disk management

Logging off an iSCSI targetTo 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 27 Log off a target

3. Check the target identifier and click Log off and then click OK. The target status changes to Inactive, and theiSCSI drive is no longer available to the host.

White Paper 20


ISCSI INITIATOR CONFIGURATION ON LINUXThere are a few iSCSI software initiators for the Linux platform. In theory, as long as an initiator implements theiSCSI protocol correctly, it should be able to connect successfully to a target on the Iomega StorCenter. TheOpen-iSCSI initiator is a popular choice in the Linux community, and is the only Linux iSCSI software initiatorthat has been qualified by Iomega.

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

Starting the Open-iSCSI software initiatorThe Open-iSCSI persistent configuration is implemented as a DBM database and contains two tables discoveryand node. These iSCSI database tables are typically located in /var/lib/open-iscsi/ on SuSE and /var/lib/iscsi/ onRedHat. 1. For an existing Iomega StorCenter storage device with initiator CHAP already configured, stop the iSCSI serviceon 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 345chkconifg s open-iscsi on

3. Start the iSCSI service.

RedHat:/etc/init.d/iscsi start

SuSE:/etc/init.d/open-iscsi start

Configuring the initiatorBefore you discover and connect to a target, please make sure you configure the CHAP authentication settings. Ifthe target is not secured, you can skip this section.

White Paper 21

MANAGING IOMEGA IX12-300R NETWORK STORAGE ARRAY FOR WINDOWS USER ACCESS

Note: the settings in the iscsid.conf file are global to the initiator. It means that the initiator will try to connect to alliSCSI targets using these settings by default. However, you can specify these settings using Open-iSCSI commandsfor 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

Connecting to an iSCSI targetThe Open-iSCSI initiator command iscsiadm is used to administer iSCSI connections. The command is normallyplaced in the /sbin directory.

1. Run the following command to discover targets available on the Iomega StorCenter. The command will returna 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.WLKLUN210.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.W2K3LUN10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.RepliStorLUN10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.W2K8LUN10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.XPLUN10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.WLKLUN310.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.EXCHANGELUN10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.WLKLUN110.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.ESXLUN10.6.126.153:3260,1 iqn.1992-04.com.emc:ix4-200r.rtpsoho1.EXCHANGELOG

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

White Paper 22


3. Run the following commands to specify CHAP settings for the target if you havent set the global settingspreviously in iscsid.conf.

# iscsiadm -m node -T iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN -p 10.6.126.153 --op update -nnode.session.auth.authmethod -v CHAP

# iscsiadm -m node -T iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN -p 10.6.126.153 --op update -nnode.session.auth.username -v admin

# iscsiadm -m node -T iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN -p 10.6.126.153 --op update -nnode.session.auth.password -v 12345678****

4. If Mutual CHAP is enabled on the Iomega device, run the following commands if you havent set the globalsettings previously in iscsid.conf.

# iscsiadm -m node -T iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN -p 10.6.126.153 --op update -nnode.session.auth.username_in -v iscsi

# iscsiadm -m node -T iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN -p 10.6.126.153 --op update -nnode.session.auth.password_in -v abcdefghijkl

5. Run the following command to automatically restore the iSCSI connection to the target each time the host isrebooted if you havent 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 -nnode.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

White Paper 23


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 28 Open YaST iSCSI initiator tool

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

Figure 29 Discover targets in the YaST iSCSI initiator tool


4. Click Next and all the targets on the Iomega device are listed.

Figure 30 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.

6. If the target is secured, enter the Username and Password for Outgoing Authentication as admin and12345678**** respectively. If Mutual CHAP is enabled on the Iomega device, enter the Username and Passwordfor Incoming Authentication as iscsi and abcdefghijkl, respectively.

Figure 31 Specify CHAP authentication in the YaST iSCSI initiator tool

White Paper 24


White Paper 25

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

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

8. Click Next and change the start-up mode from manual to automatic by clicking the Toggle Start-Up button.

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


White Paper 26

Creating a diskAfter 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 havethe 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 0lrwxrwxrwx 1 root root 9 May 29 19:04 ip-10.6.126.153:3260-iscsi-iqn.1992-04.com.emc:ix4-200r.rtpsoho1.DemoLUN -> ../../sdblrwxrwxrwx 1 root root 9 May 28 23:55 pci-0000:00:07.1-ide-0:0 -> ../../hdalrwxrwxrwx 1 root root 9 May 28 23:55 pci-0000:00:10.0-scsi-0:0:0:0 -> ../../sdalrwxrwxrwx 1 root root 10 May 28 23:55 pci-0000:00:10.0-scsi-0:0:0:0-part1 -> ../../sda1lrwxrwxrwx 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 thefollowing command to create a partition on the disk.

# fdisk /dev/sdb

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): nCommand action

e extendedp primary partition (1-4)

pPartition number (1-4): 1First cylinder (1-261, default 1): 1Last 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): wThe 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 whitepaper, ext3 is chosen as the example.

# /sbin/mkfs.ext3 /dev/sdb1


White Paper 27

6. vi or use another editor to open /etc/fstab and add an entry in the mount table.

/dev/sdb1 /iomega_iscsi ext3 _netdev 0 0

7. Create a directory as the file system mount point, and mount the newly created file system.

# mkdir /iomega_iscsi# mount /iomega_iscsi

Logging off an iSCSI targetTo log off and remove a specific target on the Iomega NAS storage device, you can use the Open-iSCSI commandagain. Ensure that there is no active I/O to the iSCSI drive from the host, otherwise, you risk data integrity beingcompromised.

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 33.

ISCSI INITIATOR CONFIGURATION ON MACThere are a few iSCSI software initiators for the Mac OS X platform. In theory, as long as an initiator implementsthe iSCSI protocol correctly, it should be able to connect to a target on the Iomega StorCenter successfully. TheglobalSAN iSCSI Initiator is a popular choice in the Mac community and is the only Mac iSCSI software initiatorthat has been qualified by Iomega.

Installing the globalSAN software initiator1. 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.

Configuring the initiatorThe software initiator needs to be configured before it connects to the Iomega StorCenter iSCSI storage.

1. Run the globalSAN iSCSI initiator in System Preferences.

Figure 34 Run globalSAN initiator


White Paper 28

2. Click + in the Portals tab to add the Iomega StorCenter device.

Figure 35 Add a portal in globalSAN

3. Enter the IP address and port number.

Figure 36 Enter iSCSI server address


White Paper 29

4. Click OK and the list of targets on the Iomega NAS device is displayed in the Targets tab.

Figure 37 List targets in the globalSAN initiator

Connecting to an iSCSI targetAfter the iSCSI target is discovered, the initiator needs to log on before the drive provided by the target can beused. The initiator will need to authenticate during logon according to the authentication mechanism set on theIomega device.

1. Select the target to connect, check Persistent so that the initiator automatically logs on to the target every timethe 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.


White Paper 30

2. Click Connect to proceed. The first time you log on to the target, a popup message is shown to remind you thedisk is not initialized.

Figure 38 Configure CHAP in globalSAN initiator

Creating a disk1. Click Initialize in Figure 39 to bring up the Disk Utility.

Figure 39 Connect to the target


White Paper 31

2. Go to the Partition tab, select 1 Partition in the Volume Scheme dropdown list, enter a name for the partitionto be created, and select the file system format for the partition.

Figure 40 Initialize the iSCSI drive

Figure 41 Format the iSCSI drive

Figure 42 Disk ready for use

3. Click Apply to create the partition. The disk is now ready for use.


White Paper 32

Logging off an iSCSI targetTo log off and remove a specific target on the Iomega storage device, you must use the globalSAN iSCSI softwareinitiator again. Ensure that there is no active I/O to the iSCSI drive from the host, otherwise, you risk dataintegrity 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.

Figure 43 Disconnect a target

ISCSI INITIATOR CONFIGURATION ON VMWARE ESXVMware 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 theIomega StorCenter, do not enable Mutual CHAP on the Iomega device.


White Paper 33

VMware ESX Server 4.0 adds support for Mutual CHAP. Follow the steps below to configure CHAPauthentication. 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 44 Specify CHAP configuration on VMware ESX 4.0

2. Select Required from the Select option in the CHAP pane, then enter admin and 12345678**** for the Nameand Secret, respectively.

3. Select Required from Select option in the Mutual CHAP pane, then enter iscsi and abcdefghijkl for the Nameand Secret, respectively.


White Paper 34

Figure 45 Configure Mutual CHAP on VMware ESX 4.0

ISCSI CONNECTION USING THE IOMEGA STORCENTER MANAGERTo simplify use of iSCSI, the Iomega StorCenter Manager that comes with your Iomega NAS device has the iSCSIinitiator support built-in for the Windows platform. With this support, you can manage an iSCSI drive from withinthe StorCenter Manager. However, you must first install the Microsoft iSCSI Initiator on your machine, the clientsoftware calls APIs of the initiator to perform tasks including logon, mapping, formatting, etc. Note that only auser 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 SharedStorage page. You click this icon to connect the iSCSI drive.


White Paper 35

Figure 46 Manage iSCSI from client software

1. Click the icon, The Connect iSCSI Drive page opens. Specify the drive letter to use.

Figure 47 Specify connection information


2. If Mutual CHAP is enabled on the Iomega device, the Device Secret field will display. Enter the secretabcdefjhijkl. Because you are logged in to the StorCenter Manager as the Admin user, the software knows theCHAP user name and secret. There is no need to supply the initiator CHAP information here.

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 turnsinto .

Figure 48 Connect an iSCSI drive with client software

5. To disconnect the drive from the host, click from the client software.

2011 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 and Lifeline are registered trademarks of EMCCorporation in the U.S. and/or other countries. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Certain other product names, brand names and company names may be trade-marks 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 capaci-ties are specified in gigabytes (GB), where 1GB = 1,000,000,000 Bytes. To obtain information about Iomegas current policies please visit Iomega at www.iomega.com or call 1-888-4iomega (1-888-446-6342). iSCSWP-0211-03

iscsi wp 0211

Documents

configuration of iscsi

iscsi initiators

iscsi packets

iscsi host

iscsi service

iscsi endpoint

iscsi targets

unique iscsi