Installing Celerra ISCSI Host Components 5.6

7/25/2019 Installing Celerra ISCSI Host Components 5.6

1/74

1 of 7

Contents

Introduction to EMC Celerra iSCSI host components . . . . . . . . . . . . . . . .3Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Caution and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Celerra iSCSI host component concepts . . . . . . . . . . . . . . . . . . . . . . . . . .7Celerra VSS Provider for iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

CBMCLI commands for Linux hosts. . . . . . . . . . . . . . . . . . . . . . . . . . .8

System requirements for Celerra iSCSI host components . . . . . . . . . . . . 9EMC E-Lab Interoperability Navigator . . . . . . . . . . . . . . . . . . . . . . . . .9

Planning considerations for Celerra iSCSI host components. . . . . . . . .10User interface choices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Roadmap for Celerra iSCSI host components . . . . . . . . . . . . . . . . . . . . .12Installing Celerra host components for Windows . . . . . . . . . . . . . . . . . . 13

Install Celerra VSS Provider for iSCSI . . . . . . . . . . . . . . . . . . . . . . . .13

Setting up the Microsoft iSCSI Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . .16Task 1: Install the Microsoft iSCSI Initiator . . . . . . . . . . . . . . . . . . . .17

Task 2: Register the initiator name with the Windows Registry . . .18Task 3: Adjust the MaxRequestHoldTime parameter . . . . . . . . . . . . 19

Task 4: (Optional) Configure the CHAP secret for reverse

authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Task 5: Configure iSCSI discovery on the initiator . . . . . . . . . . . . . .21

Task 6: Log in to the iSCSI target . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Configuring iSCSI LUNs as disk drives in Windows . . . . . . . . . . . . . . . .25Task 1: Enable automounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Task 2: Determine disk and LUN numbers. . . . . . . . . . . . . . . . . . . . .26

Task 3: Configure volumes on iSCSI LUNs . . . . . . . . . . . . . . . . . . . .27

Task 4: Bind volumes in the iSCSI initiator . . . . . . . . . . . . . . . . . . . .29

Task 5: Make the Exchange service dependent on iSCSI service . .30

Using Celerra iSCSI host components for Windows . . . . . . . . . . . . . . . .31Stopping and starting Celerra VSS Provider for iSCSI . . . . . . . . . . .31

Using Celerra VSS Provider for iSCSI with backup applications. . .32

Installing Celerra iSCSI host components for Linux . . . . . . . . . . . . . . . .34Install the CBMCLI package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Set up the Linux iSCSI initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Configure CHAP authentication for CBMCLI operations. . . . . . . . . . . . .36Configure iSCSI LUNs as disk drives in Linux . . . . . . . . . . . . . . . . . . . . . 37Using Celerra iSCSI host components for Linux . . . . . . . . . . . . . . . . . . .40

Installing Celerra iSCSI Host Components

P/N 300-004-154Rev A01

Version 5.6March 2008


2/74

Installing Celerra iSCSI Host ComponentVersion 5.62 of 74

Using CBMCLI commands on a Linux host . . . . . . . . . . . . . . . . . . . .40

cbm_iscsi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

cbm_replicate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

cbm_security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

lnstalling Celerra host components for AIX . . . . . . . . . . . . . . . . . . . . . . . 57Install Celerra AIX support software. . . . . . . . . . . . . . . . . . . . . . . . . .57

Set up the IBM AIX iSCSI initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Configure iSCSI LUNs as disk drives in AIX . . . . . . . . . . . . . . . . . . . . . . .59Troubleshooting Celerra iSCSI host component problems. . . . . . . . . . .60

Technical support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

iSCSI session troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

VSS Provider troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

CBMCLI troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Known problems and limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Error messages for Celerra iSCSI host components . . . . . . . . . . . . . . . . 65iSCSI initiator error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Celerra VSS Provider for iSCSI error messages . . . . . . . . . . . . . . . .65

General Windows iSCSI error messages . . . . . . . . . . . . . . . . . . . . . .68

CBMCLI command error messages . . . . . . . . . . . . . . . . . . . . . . . . . .68

Related information for iSCSI host components . . . . . . . . . . . . . . . . . . .70Customer training programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71


3/74

3 of 7Version 5.6Installing Celerra iSCSI Host Components

Introduction to EMC Celerra iSCSI host components

EMCCelerraiSCSI host components are services and applications that run on

an iSCSI host and interoperate with iSCSI targets on a Celerra Network Server.

This document is part of the Celerra Network Server information set and is intended

for administrators who plan to use iSCSI applications to store and back up data on

Celerra iSCSI logical units (LUNs).This document provides instructions for installing Celerra iSCSI services and

applications on iSCSI host systems, and for installing and configuring the iSCSI

initiator and configuring iSCSI devices as local drives.

This document provides limited information about iSCSI targets on the server.

Configuring iSCSI Targets on Celerraprovides detailed information including iSCSI

concepts and terminology.

Terminology

The Celerra Glossaryprovides an extensive list of Celerra terminology.

Challenge Handshake Authentication Protocol (CHAP):An access control protocolfor secure authentication using shared passwords called secrets.

demote: To unmount a snapshot from an iSCSI LUN. Upon demotion, the LUN is

inaccessible and changes made to the LUN while in a promoted state are lost.

disk device:A physical disk or logical device in a storage subsystem viewed by

client systems as a physical disk.

Internet SCSI (iSCSI):A protocol for sending SCSI packets over TCP/IP networks.

Internet Storage Name Service (iSNS):A 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 qualified name (IQN):A naming standard supported by the iSCSI protocol.

IQN names are globally unique and in the form of iqn.followed by a date and areversed domain name.

iSCSI host:A computer hosting an iSCSI initiator.

iSCSI initiator:An iSCSI endpoint, identified by a unique iSCSI name, which begins

an iSCSI session by issuing a command to the other endpoint (the target).

iSCSI LUN:A Celerra iSCSI software feature that processes SCSI commands such

as reading from and writing to storage media.

iSCSI session: The relationship between two iSCSI endpoints (the initiator and the

target) over a group of TCP connections.

iSCSI target:An iSCSI endpoint, identified by a unique iSCSI name, which executes

commands issued by the iSCSI initiator.

logical unit number (LUN): The 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.
http://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/mergedprojects/Glossary/index.htmhttp://localhost/var/www/apps/conversion/mergedprojects/Glossary/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htm


4/74

Installing Celerra iSCSI Host Component4 of 74 Version 5.6

logical volume: Logical devices aggregated and managed at a higher level by a

volume manager.

LUN mask:A set of access permissions that identify which iSCSI initiators can

access specific LUNs on a SCSI or iSCSI target.

network portal:A component that listens for and is capable of accepting iSCSI

connections within a given iSCSI session. A network portal for an iSCSI initiator is

identified by its IP address. A network portal for an iSCSI target is identified by its IP

address, listening port, and group tag.

production logical unit (PLU):An iSCSI LUN that serves as a primary storage

device. A PLU can be configured as a disk device through an iSCSI initiator.

promote: To mount a snapshot to an iSCSI LUN so it can be configured as a disk

device through an iSCSI initiator.

SCSI: Small computer system interface. The standard set of protocols for host

computers communicating with attached peripherals.

shadow copy:A point-in-time copy created through the Microsoft Volume Shadow

Copy Service (VSS).

SLU (snapshot logical unit):A snapshot promoted to logical unit status andconfigurable as a disk device through an iSCSI initiator.

snapshot:A generic term for a point-in-time copy of data.

Volume Shadow Copy Service (VSS):A Windows service and architecture that

coordinates various components to create consistent point-in-time copies of data

called shadow copies.

VSS provider:A component in the VSS architecture that creates and maintains

shadow copies.


5/74


Restrictions

The following restrictions and limitations affect Celerra iSCSI host components.

Dynamic disks

The Celerra iSCSI host components do not support configuring iSCSI LUNs as

dynamic disks. The Microsoft iSCSI Software Initiator does not currently support

dynamic disks.

In the future, if the Microsoft Windows iSCSI Software Initiator supports dynamic

disks, you must transport the shadow copies of dynamic disk LUNs to different

hosts for use. This is because Celerra support for dynamic disks cannot

accommodate LUNs with duplicate signatures and configuration database

contents. When transporting dynamic disk LUNs to a new host, the receiving host

must have at least one dynamic disk.

Celerra VSS Provider for iSCSI

Celerra VSS Provider for iSCSI does not support:

Microsoft Windows Shadow Copy for Shared Folders. Importing shadow copies to clustered servers. Although you can create shadow

copies in a Microsoft Cluster Server (MSCS) environment, importing shadow

copies is not supported because of a Microsoft restriction. Importing shadow

copies to remote hosts is an advanced VSS feature called Shadow Copy

Transport, which requires a hardware VSS provider, such as Celerra VSS

Provider for iSCSI, and a third-party VSS requestor that supports Shadow Copy

Transport.

"Shadow copy transport" on page 8provides more information about this VSS

feature.

To use Shadow Copy Transport to back up data on a cluster, you must transport

and import shadow copies to a nonclustered backup server.

Celerra VSS Provider for iSCSI supports differential shadow copies, but not plex

shadow copies.

Replication Manager

For information about restrictions, consult the EMC Replication Manager Product

Guide, which is available from the EMC Powerlinkwebsite at

http://Powerlink.EMC.com.

Microsoft NTBackup

The Microsoft NTBackup utility does not support VSS backups for Microsoft

Exchange Server. The utility supports only simple recovery types for VSS backupsof SQL Server databases.

Support for Terminal Services and Remote Desktop

On Windows Server 2003 platforms, EMC supports the use of Microsoft Terminal

Services only in console mode with the Celerra iSCSI host components.
http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/


6/74


Because Terminal Services on Windows 2000 does not include a console mode, do

not use Terminal Services with Windows 2000.

However, because of the following known problems with regular mode Terminal

Services, you should use console mode Terminal Services with the Celerra iSCSI

host components:

After the initiator logs in to an iSCSI target, the iSCSI LUNs do not appear in the

Windows Disk Management tool until you log out and then log back in to theTerminal Services session.

Promoted snapshots/shadow copies do not appear in the Disk Management

tool or Explorer until you restart the Terminal Services session.

To run Terminal Services in console mode:

1. From the Startmenu, select Run.

2. In the Rundialog box, typemstsc /console, and then click OK.

iSCSI LUNs with Linux

When using 64-bit Red Hat Linux 3.x, the software iSCSI initiator sometimes cannot

discover LUNs numbered 128 or higher. The server uses those numbers forpromoted snapshot LUNs. As a workaround, either promote snapshots to a 32-bit

Linux workstation or upgrade to 64-bit Red Hat Linux 4.x.

Caution and warnings

If the following information is unclear, contact an EMC Customer Support

Representative for assistance:

The nas_fsck command should not be run on file systems with iSCSI LUNs

unless absolutely necessary. If you need to run nas_fsck on a file system with

iSCSI LUNs, log out the iSCSI initiators connected to the LUNs. Failure to

disconnect iSCSI initiators before running nas_fsck might result in data loss.

Remounting an iSCSI file system is normally prevented, but can be forced by

using the server_mount command with the -Force option. An iSCSI file system

should not be remounted unless necessary. To remount an iSCSI file system,

log out the iSCSI initiators connected to LUNs on the file system. Failure to

disconnect the iSCSI initiators before remounting the file system might result in

data loss.

iSCSI snapshots are not intended for use as mirrors, for disaster recovery, or for

high-availability. Because iSCSI snapshots are derived from realtime data on

iSCSI LUNs, snapshots can become inaccessible (not readable) if the

production LUN becomes inaccessible. Only snapshots saved to an alternative

storage location can be used for disaster recovery.


7/74


Celerra iSCSI host component concepts

Celerra iSCSI (Internet SCSI) host components are services and applications that

run on an iSCSI host and provide additional capabilities for applications that store

data on Celerra iSCSI LUNs.

Current Celerra iSCSI host components include:

"Celerra VSS Provider for iSCSI" on page 7for Windows

"CBMCLI commands for Linux hosts" on page 8for Linux

Celerra VSS Provider for iSCSI

Celerra VSS Provider for iSCSI runs as a Windows service and provides the

interface between the Microsoft Volume Shadow Copy Service (VSS) and the iSCSI

snapshot capabilities of the Celerra Network Server. Celerra VSS Provider for

iSCSI enables VSS requestor applications, such as VSS-enabled backup

applications, to make shadow copies of Celerra iSCSI LUNs.

Microsoft VSSVSS provides the backup framework for Windows Server 2003 and enables the

creation of shadow copiespoint-in-time copies of data. VSS integrates with

front-end applications so they can create and access shadow copies.

Shadow copies are:

Read-only by default

Limited to 512 shadow copies per volume

The VSS architecture includes VSS providers. A VSS provider creates and

maintains shadow copies and acts as the interface to point-in-time imaging

capabilities either on a storage platform (hardware-based provider) or in a host

operating system (software-based provider).

Celerra VSS Provider for iSCSI is a hardware-based provider that works directly

with iSCSI LUNs on the server and the VSS service on Windows Server 2003 to

provide consistent shadow copy creation and addressing.

Because Celerra VSS Provider is a hardware-based provider that works on the

storage array, it reduces the load on the CPU and memory of the iSCSI host. It is

also more efficient in an environment where shadow copies of multiple volumes

must be taken simultaneously.

The Microsoft website provides more information about VSS and VSS components.

Types of shadow copiesVSS produces two types of shadow copies:

Plex copies Shadow copies initially created by mirroring. A plex copy is a

special case of shadow copy data that represents a shadow copy without the

need for the original volume data.

Differential copies Shadow copies created by saving only the differences

from the original volumes.


8/74


Celerra VSS Provider for iSCSI supports only differential shadow copies.

Shadow copy backups

You can use VSS shadow copies to back up data on an iSCSI host system. The

benefits of shadow copy backups are:

You can back up open files.

You can copy application data without stopping the application or restrictinguser access.

Shadow copy backups are available only on Windows Server 2003 and require a

VSS provider (such as Celerra VSS Provider for iSCSI) and a backup application

that supports VSS (such as EMC NetWorker7.1 or Veritas Backup Exec 9.1).

Shadow copy transport

If using a hardware VSS provider, such as Celerra VSS Provider for iSCSI, you can

create transportable shadow copies to import to other servers for:

Data mining Make the data in a production database available to other

applications by using a shadow copy of the database with those applications.

Backup Instead of overloading a production server with backup traffic, move

a shadow copy of a database to another server, and then back up the shadow

copy instead of the production database.

Simulation testing Quickly set up sandbox environments for testing

purposes by moving a shadow copy of the production database to another

server. By running test applications against the shadow copy, you do not modify

or destroy the original production data.

Data recovery Keep shadow copies of production data for quick restores.

Because making shadow copies is quick and nondisruptive, shadow copies

complement tape-based recovery solutions.

Transportable shadow copies are available only with Windows Server 2003Enterprise or Datacenter editions.

CBMCLI commands for Linux hosts

The CBMCLI (Celerra Block Management Command Line Interface) package

provides commands that can be run on a Linux host to manage snapshots of iSCSI

LUNs on a Celerra Network Server and to manage remote replication of those

snapshots.

This package includes these CLI commands for the Linux host:

cbm_iscsi

cbm_replicate

cbm_security


9/74


System requirements for Celerra iSCSI host

components

Table 1 on page 9describes the software, hardware, network, and storage

configurations required for usingCelerra iSCSI host components.

The EMC Replication Manager Product Guideprovides information about

requirements and restrictions for using RM.

EMC E-Lab Interoperability Navigator

The EMC E-LabInteroperability Navigator is a searchable, web-based application

that provides access to EMC interoperability support matrices. It is available on theEMC Powerlink website at http://Powerlink.EMC.com. After logging in to Powerlink,

go to Support> Interoperability and Product Lifecycle Information > E-Lab

Interoperability Navigator.

Table 1 System requirements for Celerra iSCSI host components

Software For Celerra VSS Provider for iSCSI:

Celerra Network Server version 5.5 or later

A system running Windows Server 2003 with Service Pack 1, Standard1,Enterprise, or Datacenter Edition

A number of Microsoft hotfixes must be applied to the Windows iSCSI host to

correct problems with VSS. The Celerra Network Server Release Noteslist the

required hotfixes.

For CBMCLI commands:

Celerra Network Server version 5.5.27 or later

Linux kernel 2.4: iSCSI initiator version 3.6.3 or later

Linux kernel 2.6: iSCSI initiator version 4.0.1.11 or later

Hardware initiators are not supported.

For IBM AIX support:

AIX 5.2 or 5.3

Hardware initiators are not supported.

The EMC Host Connectivity Guide for IBM AIX, which is available on Powerlink,

provides additional information.

Hardware No specific hardware requirements.

Network An Ethernet 10/100/1000 network with one or more iSCSI hosts configured with

the most recent version of the Microsoft iSCSI Software Initiator.

Storage No specific storage requirements.

1. VSS Shadow Copy Transport is unavailable on Windows Server 2003 Standard edition.
http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/


10/74


Planning considerations for Celerra iSCSI host

components

These guidelines apply when using iSCSI on the Celerra Network Server.

Network

To achieve the best performance when using the servers iSCSI feature, use

iSCSI in a LAN environment and, if possible, on a local subnet. To achieve

maximum throughput, use iSCSI on a private network. The Microsoft website

provides recommendations for Microsoft Exchange requirements with iSCSI.

File system

A file system with iSCSI LUNs should be dedicated to iSCSI and not used for

other purposes. For example, an iSCSI file system should not be exported

through a CIFS share or NFS export.

All space on the file system should be available to iSCSI because, in addition to

the space taken by LUNs, iSCSI snapshots require additional space.

Configuring iSCSI Targets on Celerra provides guidelines for determining thesize requirements for file systems when using iSCSI snapshots or VSS shadow

copies.

You must routinely monitor the amount of free space on the iSCSI file system.

Without enough free space, you cannot take or promote iSCSI snapshots.

Monitoring file system usage is crucial when using virtually provisioned LUNs.

To help in monitoring the space usage for a file system, you can use Celerra

Manager to set a high water mark or warning alert condition.

Because the file system extension process can be time-consuming, set a

conservative high water mark to allow enough time for the extension.

iSCSI LUNs Create iSCSI LUNs for your application by using the information in Configuring

iSCSI Targets on Celerra. Be sure the target includes a LUN mask that enables

the appropriate iSCSI initiator to access those LUNs.

Backup

For disaster recovery, take snapshots of iSCSI LUNs, and then copy the

snapshots to an alternative storage location. The iSCSI snapshots alone do not

provide a disaster recovery solution.

Celerra iSCSI does not support Network Data Management Protocol (NDMP)

backups. To back up the contents of a Celerra iSCSI LUN, follow these

guidelines:

For Windows Server 2003: Use a Windows host-side backup utility, such as

a VSS-compliant backup application, to copy data from the iSCSI LUN.

For Windows 2000 Server: Take an iSCSI snapshot of the LUN, promote the

snapshot, and use a host-side backup application to copy data from the

promoted snapshot to an alternative storage location.
http://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htm


11/74


User interface choices

This document describes how to install the Celerra iSCSI host components on a

Windows iSCSI host system by using the Microsoft Windows operating system or

on a Linux or AIX host by using the command line interface.


12/74


Roadmap for Celerra iSCSI host components

Management tasks for Windows hosts:

"Installing Celerra host components for Windows" on page 13

"Setting up the Microsoft iSCSI Initiator" on page 16

"Configuring iSCSI LUNs as disk drives in Windows" on page 25

"Using Celerra iSCSI host components for Windows" on page 31

Management tasks for Linux hosts:

"Installing Celerra iSCSI host components for Linux" on page 34

"Set up the Linux iSCSI initiator" on page 35

"Configure CHAP authentication for CBMCLI operations" on page 36

"Configure iSCSI LUNs as disk drives in Linux" on page 37

"Using Celerra iSCSI host components for Linux" on page 40

Management tasks for AIX hosts:

"lnstalling Celerra host components for AIX" on page 57

"Set up the IBM AIX iSCSI initiator" on page 58

"Troubleshooting Celerra iSCSI host component problems" on page 60


13/74


Installing Celerra host components for Windows

For Windows hosts, the Celerra iSCSI host components include Celerra VSS

Provider for iSCSI

Install Celerra VSS Provider for iSCSI

Use this procedure to install Celerra VSS Provider for iSCSI on a host system.

Step Action

1. Log in to the system through an account with administrator privileges.

2. Insert the Celerra iSCSI Target SoftwareCD into a CD-ROM drive.

3. From the CD, run the application:

EMCVSSPack

After the installation files are unpacked, the Welcome to the InstallShield Wizarddialog

box appears.


14/74


4. Click Next.

The License Agreementdialog box appears.

5. If the terms are agreeable, select I accept the terms in the license agreement, and then

click Next.

The Customer Informationdialog box appears.

Step Action


15/74


6. To permit anyone logging in to the system to use the Celerra iSCSI host components, click

Nextto accept the default values.

The Setup Typedialog box appears.

7. To complete the installation:

a. Be sure the Completeoption is selected, and then click Next.

b. In the Ready to Install the Programdialog box, click Install.

c. In the InstallShield Wizard Completed dialog box, click Finish.

The files are installed to the directory:

C:\Program Files\EMC\Celerra VSS Provider

Step Action


16/74


Setting up the Microsoft iSCSI Initiator

Perform this series of tasks. The Microsoft iSCSI Software Initiator User Guide,

which is installed with the Microsoft iSCSI Initiator, provides detailed configuration

information.

1. "Install the Microsoft iSCSI Initiator" on page 17

2. "Register the initiator name with the Windows Registry" on page 18

3. "Adjust the MaxRequestHoldTime parameter" on page 19

4. "(Optional) Configure the CHAP secret for reverse authentication" on page 20

5. "Configure iSCSI discovery on the initiator" on page 21

6. "Log in to the iSCSI target" on page 23


17/74


Task 1: Install the Microsoft iSCSI Initiator

To connect to the iSCSI targets on a server, the iSCSI host system requires an

iSCSI initiator. Celerra iSCSI supports the Microsoft iSCSI Software Initiator.

Step Action

1. Download the latest Microsoft iSCSI Software Initiator.

To locate the latest initiator, go to the Microsoft website and search for iSCSI initiator.

2. Run the initiator executable.

The Welcome to Microsoft iSCSI Initiator Setup Wizarddialog box appears.

3. Click Next.

4. In the Select Installation Folderdialog box, select Everyone, and then do one of the

following:

To accept the default installation folder, click Next.

To use another folder for installation, click Browseto locate the folder, and then click

Next.

5. In the Confirm Installationdialog box, click Next.

6. In the License Agreementdialog box, selectI Agree, and then click Next.

7. In the Microsoft iSCSI Installation Programdialog box, click OKto install the complete

iSCSI initiator.

8. In the End User License Agreementdialog box, click Agreeto accept the terms of the

license agreement.

9. To complete the installation:a. Click OKto close the installation confirmation message.

b. At the Microsoft iSCSI Initiator Informationdialog box, click Next.

c. At the Installation Completedialog box, click Close.


18/74


Task 2: Register the initiator name with the WindowsRegistry

Complete this procedure for each iSCSI initiator that needs to connect to a Celerra

Network Server. If the initiators iSCSI Qualified Name (IQN) is not written to the

Windows Registry, iSCSI-aware applications might not find the initiators IQN.

Step Action

1. Open the Microsoft iSCSI Initiator.

2. On the Generaltab, click Change.

3. In the Initiator Node Name Changewindow, leave the displayed initiator name

unchanged. Click OK.

This procedure converts uppercase characters in the IQN to lowercase. The Celerra

Network Server supports only lowercase IQNs.


19/74


Task 3: Adjust the MaxRequestHoldTime parameter

If an iSCSI LUN goes offline while a snapshot of it is being taken, an error (delayed

write failure) occurs. To avoid this error, adjust the value of the Windows

MaxRequestHoldTime parameter for the Microsoft iSCSI Initiator.

Before adjusting the parameter

CAUTION

Incorrectly modifying the Registry can cause serious system-wide problems that

might require you to reinstall the system. Use this tool at your own risk.

Adjusting the MaxRequestHoldTime parameter

Step Action

1. Run the Windows Registry Editor(regedit.exe).

2. Go to the key:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}

3. Locate the entry for the Microsoft iSCSI Initiator driver, which is an expandable folder that

contains a subfolder named Parameters. Click the Parametersfolder.

4. In the Parametersfolder, right-click MaxRequestHoldTimeand select Modify.

5. In the Edit DWORD Valuewindow, change the value of MaxRequestHoldTimefrom 60to 600 (decimal) or from 3c to 258 (hexadecimal), and then click OK.

6. Quit the Registry Editor.


20/74


Task 4: (Optional) Configure the CHAP secret for reverseauthentication

To use reverse authentication for iSCSI sessions, you must configure the iSCSI

initiator with a CHAP secret.

Before configuring the CHAP secret

CHAP provides a method for iSCSI initiators and targets to authenticate one

another by exchanging a shared secret or password. Because the secret is shared

between the initiator and target, configure the same secret on both. The initiator

and target systems maintain databases of CHAP entries:

With regular CHAP, the target challenges the initiator for a CHAP secret.

With reverse authentication the initiator challenges the target for a secret.

The Microsoft iSCSI initiator supports only one secret per initiator.

By default, targets on the server do not require CHAP authentication. Depending on

your organizations needs, you might want to require CHAP authentication. You can

enable CHAP authentication at two different points of the iSCSI login:

Discovery authentication: CHAP authentication is required before the initiator

can contact the server to establish a discovery session during which the initiator

tries to discover available targets. If discovery authentication is enabled on the

iSCSI target, you need to define the CHAP secret when configuring iSCSI

discovery.

Task 5: "Configure iSCSI discovery on the initiator" on page 21provides the

procedure.

Session authentication: CHAP authentication is required before the initiator can

establish a regular iSCSI session with the target. If session authentication is

enabled on the server, the initiator must provide the CHAP secret when logging

in to the iSCSI target.

Task 6: "Log in to the iSCSI target" on page 23provides the procedure.

Configuring iSCSI Targets on Celerraprovides instructions for enabling and

configuring CHAP authentication on the server.

Configuring the CHAP secret

Step Action

1. In the Microsoft iSCSI Initiator, click the Generaltab.

2. Click Secret.

3. In the CHAP Secret Setupwindow, type a CHAP secret of 12 to 16 characters.

Or to clear the secret, click Reset.

4. Click OK.
http://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htm


21/74


Task 5: Configure iSCSI discovery on the initiator

Before it can establish a session with a target, the initiator must discover where

targets are located and the names of the targets available to it. To obtain this

information, the initiator uses the iSCSI discovery process.

Before configuring iSCSI discovery

The server supports two types of iSCSI discovery:

SendTargets discovery: You manually configure the initiator with a targets

network portal (IP address and portal number). The initiator uses the portal to

discover all the targets accessible from that portal.

iSNS discovery: The initiator queries the iSNS server where all iSCSI initiators

and targets register themselves. The iSNS server returns a list of available

targets.

The initiator can use one or both types. The following topics provide instructions for

configuring the initiator to use these discovery methods.

Configuring iSCSI Targets on Celerraprovides more information about iSCSI

discovery.

Configuring iSCSI discovery

Step Action

1. Select the type of discovery to configure:

To configure SendTargets discovery, go to step 2.

To configure iSNS discovery, go to step 10.

2. In the Microsoft iSCSI Initiator, click the Discovery tab.

3. In the Target Portalssection, click Add.

4. In the Add Target Portaldialog box, type the IP address of the targets network portal. If

the target uses a port other than 3260 (the default), type that port number in the Portfield.

To ensure that the network is available, be sure to pingthe targets IP address beforeconfiguring it in the iSCSI initiator. If the server is unavailable, or if you enter a invalid IP

address, you receive the error Connection Failed.

5. Do you want to use forward CHAP authentication (where the target challenges the

initiator)?

If YES, continue with step 6.

If NO, go to step 8.

CHAP authentication is optional only if the target does not require it. If the target requiresauthentication and you do not configure a forward CHAP secret on the initiator, the initiator

cannot log in to the target. If the target does not require CHAP authentication, but the

initiator offers it, the target complies with the initiators request. Configuring iSCSI Targets

on Celerraprovides more information about enabling CHAP authentication.

6. In the Add Target Portalscreen, click Advanced.
http://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htm


22/74


7. In the Advanced Settingsdialog box, do the following to enter the CHAP secret:

a. Select CHAP logon information.

b. In the Target secretfield, type the secret you configured for the iSCSI target.

Microsoft supports CHAP secrets of 12 to 16 characters only.

c. If you also want the initiator to authenticate the target for iSCSI discovery, select

Perform mutual authentication. The optional task "Configuring the CHAP secret" onpage 20provides instructions for configuring reverse authentication on the initiator.

d. Click OK.

8. Click OK.

9. To configure iSNS discovery, continue with step 10.


11. In the iSNS Servers section, click Add.

12. In the Add iSNS Serverdialog box, type the IP address or fully-qualified domain name of

the iSNS server, and then click OK.


14. In the iSNS Servers section, click Add.

15. In the Add iSNS Serverdialog box, type the IP address or fully-qualified domain name of

the iSNS server, and then click OK.

Step Action


23/74


Task 6: Log in to the iSCSI target

After you configure the initiator with the targets network portal or the iSNS server s

IP address, a list of available targets appears on the initiators Targets tab. To

access the targets LUNs, the initiator must log in to the target.

Step Action

1. In the Microsoft iSCSI Initiator, click the Targetstab.

The list of available targets appears.

2. Select the target, and then click Log On.

The Log On to Targetdialog box appears.

3. (Optional) If the target requires CHAP authentication, click Advanced.

In the Advanced Settingsdialog box, do the following to enter the CHAP secret:

a. Select CHAP logon information.

b. In the Target secretfield, type the secret configured for the target. (Microsoftsupports CHAP secrets of 12 to 16 characters.)

c. If you want the initiator to authenticate the target, select Perform mutualauthentication. "Configuring the CHAP secret" on page 20provides instructions forconfiguring reverse authentication on the initiator.

d. Click OK.

4. In the Log On to Targetdialog box, select Automatically restore this connection

when the system boots, and then click OK.

The initiator connects to the target.

5. To get information about the new session, right-click the target, and then select Details.

The Target Propertiesdialog box appears.


24/74


6. Click the Sessionstab.

7. To end one or more sessions, select the checkbox for each, and then click Log off.

Step Action


25/74


Configuring iSCSI LUNs as disk drives in Windows

After the initiator logs in to a target, each of the targets LUNs to which the initiator

has access appears as an unknown disk in the Windows Disk Management tool.

Perform this series of tasks to configure an iSCSI LUN as an accessible disk in

Windows:

1. "Enable automounting" on page 25

2. "Determine disk and LUN numbers" on page 26

3. "Configure volumes on iSCSI LUNs" on page 27

4. "Bind volumes in the iSCSI initiator" on page 29

5. "Make the Exchange service dependent on iSCSI service" on page 30(for

Microsoft Exchange Servers only on Microsoft Windows Server 2003 with

Microsoft iSCSI Software Initiator 1.06)

Task 1: Enable automounting

If you enable automounting, Windows systems assign a drive letter to new volumesand to promoted snapshots. Automounting is disabled by default, requiring you to

use the Disk Management tool to assign drive letters.

After enabling automountingThe promote operation exports a snapshot through an iSCSI LUN to a specified

initiator and does not mount the snapshot's volume or assign a drive letter to that

volume. Windows can be configured to perform these operations, but they are not

guaranteed to occur and should not be expected. In addition, Windows supports

only 26 drive letters (A: through Z:). If you promote a snapshot to a client where all

drive letters are in use, Windows does not assign a drive letter.

Step Action

1. Open a command prompt on the server.

2. Type:

mountvol /e


26/74


Task 2: Determine disk and LUN numbers

Using the iSCSI initiator, you can see the LUN number associated with each disk

number.

Before determining disk and LUN numbers

When working with the Windows Disk Management tool, note the difference

between Windows disk numbers and iSCSI LUN numbers.

The LUN number is assigned on the server when the LUN is created. The disk

number is assigned by the Windows host system when the Microsoft iSCSI Initiator

logs in to the target and finds accessible LUNs. The LUN number and the disk

number are assigned independently and are not derived from one another.

Determining disk and LUN numbers

After determining disk and LUN numbers

In addition, an iSCSI LUN, when partitioned and formatted through the Windows

Disk Management tool, can be assigned an available drive letter. For a given LUN,

its drive letter, disk number, and LUN number are independent.

The disk number of a LUN might change after system restart or after logging out

from and logging in to a target. This behavior should not affect Microsoft Exchange

because Exchange uses logical drive mappings, not physical disk numbers.

Because disk numbers can change, be sure to change the default volume label

(New Volume) to a descriptive label when you format a new iSCSI LUN in the Disk

Management tool.

Step Action

1. Open the Microsoft iSCSI Initiator, and then click the Targetstab.

2. Select the target, and then click Details.

3. In the Target Propertieswindow, click the Devicestab.

4. Select the device (disk), and then click Advanced.

The Device Detailswindow shows the disk number and the corresponding LUN number.


27/74


Task 3: Configure volumes on iSCSI LUNs

The configuration process initializes the disk, creates a partition, formats a volume

on the partition, and mounts the partition on a drive letter.

Before configuring volumes on iSCSI LUNs

When you open the Windows Disk Management tool, the Initialize and Convert Disk

Wizard opens if any disk is unformatted. Use the wizard only to initialize the disks.

Do not select any iSCSI disk for conversion. The Microsoft iSCSI Initiator does not

support dynamic disks.

Configuring volumes on iSCSI LUNs

Step Action

1. Open the Microsoft Disk Management tool by doing the following:

a. Click Start, point to Settings, and then click Control Panel.

b. In the Control Panelwindow, double-click Administrative Tools.

c. In the Administrative Toolswindow, double-click Computer Management.

d. In the Computer Managementwindow, expand the Storagefolder, and then clickDisk Management.

The new iSCSI LUNs to which the initiator is connected appear as unallocated disks.

2. Right-click the new (unallocated) disk and select Initialize Disk.


28/74


3. In the Initialize Disk dialog box, select the disk to initialize, and then click OK.

The disk description changes from Unknown to Basic.

4. Right-click the unallocated space and select New Partition.

The New Partition Wizardstarts.

Do not format more than one iSCSI LUN at a time. Otherwise, some of the volumes might

become write-protected so they cannot be formatted.

5. Follow the instructions in the wizard to create a partition on the new disk.

The Celerra iSCSI host components require the logical volume to use a one-to-one

configuration in which this partition is the only partition on the disk. You can use any

available format on the partition. For convenience when working with multiple iSCSI disks,

replace the generic volume label (New Volume) with a descriptive label.

The disk is formatted and assigned the volume label and drive letter you specified. The

iSCSI disk now appears as a local disk from Windows Explorer.

6. Close the Disk Management tool.

Step Action


29/74


Task 4: Bind volumes in the iSCSI initiator

Whenever the system restarts, it pauses until all bound volumes are available.

Binding volumes is essential when using an application such as Microsoft

Exchange, which can fail if the volumes containing its databases are unavailable.

Before binding volumes in the iSCSI initiator

To bind volumes on a target, the target must be on the persistent target list. To place

a target on that list, select the option Automatically restore this connection

when the system bootswhen logging in to the target. Task 6: "Log in to the iSCSI

target" on page 23provides more information.

The binding operation marks all volumes on iSCSI LUNs, including any promoted

snapshot LUNs (SLUs). Because SLUs are typically mounted for temporary use, do

not bind volumes while SLUs are mounted on the system.

Binding volumes in the iSCSI initiator

Step Action

1. Open the Microsoft iSCSI Initiator.

2. Click the Bound Volumes/Devicestab.

3. Click Bind All.

The initiator marks all volumes created by using iSCSI disks.

If you make any volume changes (repartition or reformatting), repeat this procedure to

update the bound volume list.


30/74


Task 5: Make the Exchange service dependent on iSCSIservice

(For Microsoft iSCSI Software Initiator 1.06 only.) Any application that requires

iSCSI LUNs to be available when it starts, such as Exchange with storage groups

on iSCSI LUNs, should be made dependent on the iSCSI service.

Before making the Exchange service dependent on iSCSI service

CAUTION

Incorrectly modifying the Registry can cause serious system-wide problems that

might require you to reinstall the system. Use this tool at your own risk.

Making the Exchange service dependent on iSCSI service

Step Action

1. Run the Windows Registry Editor (regedit.exe).

2. Locate the key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\DependOnService

3. Right-click the key and select Modify.

4. In the Edit Multi-Stringwindow, add the following value to the DependOnServicekey:msiscsi

CAUTION

Do not alter any other value stored in this key.

5. Click OK.


31/74


Using Celerra iSCSI host components for Windows

The following topics provide instructions for accessing and using the Celerra iSCSI

host components for Windows:

"Stopping and starting Celerra VSS Provider for iSCSI" on page 31

"Using Celerra VSS Provider for iSCSI with backup applications" on page 32

Stopping and starting Celerra VSS Provider for iSCSI

Celerra VSS Provider for iSCSI runs as a Windows service and is enabled by

default. You can stop and start this component from the Windows Services

administrative tool.


32/74


Using Celerra VSS Provider for iSCSI with backupapplications

Celerra VSS Provider for iSCSI has been tested with EMC NetWorker and a

number of third-party backup applications to ensure compatibility. The E-Lab

Interoperability Navigator lists supported third-party backup applications and the

appropriate versions.

In some cases, hotfixes and/or patches must be applied to the application. The

Celerra Network Server Release Notesprovide the latest information.

To use Celerra VSS Provider for iSCSI to perform VSS backups with backup

applications, the data must be stored on iSCSI LUNs on the server. Microsoft

Exchange storage groups, mailboxes, and SQL Server databases must reside on

Celerra iSCSI devices.

The following topics provide brief usage notes on performing VSS backups with

currently supported applications. For complete instructions, consult the vendors

documentation for that application.

EMC NetWorker

Table 2 on page 32provides usage notes for performing VSS backups with

NetWorker.

Table 2 VSS backups with EMC NetWorker

To back up Use Note

Microsoft Exchange

Server storage groups

NetWorker VSS User Data:

Microsoft Exchange Writer

NetWorker uses VSS to back up

and recover all Microsoft Exchange

Server and SQL Server databases

at once. NetWorker does not

currently support the backup and

recovery of individual databases orstorage groups.

For more information, consult the

NetWorker documentation on

Powerlink.

SQL Server databases NetWorker VSS SYSTEM

services: MSDEWriter

Volumes VSS commands in the Save

Operations dialog box to

enforce VSS backups on the

clients and/or server

If a VSS client license is present,

NetWorker backs up volumes by

using VSS. If VSS fails, NetWorker

typically uses legacy backup

methods.

Enforcing VSS backups causes

NetWorker to use VSS only. If VSS

fails, the specified drive is notbacked up.



controlling VSS backups from

either the client or server.
http://powerlink.emc.com/http://powerlink.emc.com/


33/74


Veritas Backup Exec

Table 3 on page 33provides usage notes for performing VSS backups with Veritas

Backup Exec.

Veritas NetBackup

Table 4 on page 33provides usage notes for performing VSS backups with Veritas

NetBackup.

Table 3 VSS backups with Veritas Backup Exec

To back up Use Note

Microsoft Exchange


Veritas Backup Execs

Shadow Copy Components

Exchange Server Writer



Powerlink.

SQL Server databases Veritas Backup Execs

Shadow Copy Components

SQL Server Writer

Volumes Veritas Backup Execs

Advanced Open File Options -

Microsoft Volume Shadow

Copy Service

Configure VSS backups on

individual jobs or as the default for

all volume backup jobs.


Veritas Backup Execdocumentation on the Advanced

Open File Option.

Table 4 VSS backups with Veritas NetBackup

To back up Use

Microsoft Exchange


For VSS Client configuration: Set the Master ServerProperties-Client Attributes for Windows Open File Backup and setthe Snapshot Provider to VSS.

For VSS Policy configuration: Set Policy Attributes for SnapshotBackups and set the Snapshot Method to VSS.

For more information, consult the Veritas NetBackup documentation

on the Microsoft Volume Shadow Copy Service and Advanced

Snapshot Option.

SQL Server databases

Volumes
http://powerlink.emc.com/http://powerlink.emc.com/


34/74


Installing Celerra iSCSI host components for Linux

For Linux hosts, the Celerra iSCSI host components include the CBMCLI package

of commands for managing snapshots.

Table 5 on page 34lists the available packages.

Install the CBMCLI package

Use RPM to install the CBMCLI package.

Table 5 CBMCLI packages

Package For

cbm-.rh32.i386.rpm 32-bit hardware with Red Hat Linux

cbm-.suse.i386.rpm 32-bit hardware with SUSE Linux

cbm-.rh64.x86_64.rpm 64-bit hardware with Red Hat or SUSE Linux

where is the version number of the package (for example, 1.8.22)

The 32-bit packages can be installed on a 64-bit machine with the appropriate Linux distribution.

Step Action

1. Log in to the Linux host through an account with administrator privileges.

2. Insert the Celerra iSCSI Target SoftwareCD.

3. Mount the CD.Example:

mkdir /mnt/cbmclimount -o ro,loop /root/EMC_ISCSI_UTILS_1_8_22D.iso /mnt/cbmclicd /mnt/cbmclicd linux

4. Install the package by using RPM.

rpm -i

where:

= CBMCLI package (listed in Table 5 on page 34)

Example:

rpm -i cbm-1.8.22.rh32.i386.rpm


35/74


Set up the Linux iSCSI initiator

The iSCSI initiator is included with the Linux operating system. Use the following

procedure to enable the Linux host to discover iSCSI targets on the Celerra

Network Server.

Step Action

1. On the Linux host, determine the IQN of the iSCSI initiator by opening the file

/etc/initiatorname.iscsi

and looking for the line that begins with InitiatorName=.

For example:

InitiatorName=iqn.1987-05.com.cisco:01.2e798796a1c

Do not use the iscsi-inamecommand to get the initiator name.

2. Using a text editor, open the file /etc/iscsi.conf.

3. Add the following line to the file:

DiscoveryAddress=where:

= IP address of the Data Mover where the iSCSI target resides

Example:

DiscoveryAddress=10.173.0.10

4. Close the file and save the changes.

5. Stop and then restart the iSCSI service by typing the following commands:

# /etc/init.d/iscsi stopStopping iscsid: [OK]# /etc/init.d/iscsi startChecking iscsi config: [OK]

Loading iscsi driver: [OK]mknod: /dev/iscsict: File existsStarting iscsid: [OK]


36/74


Configure CHAP authentication for CBMCLI

operations

The Linux host and Celerra Network Server use CHAP authentication for snapshot

and replication operations performed through the CBMCLI commands (described in

"Using CBMCLI commands on a Linux host" on page 40). For each Linux user who

will use CBMCLI commands, you must configure a shared secret on the Linux hostand the Data Mover where the iSCSI LUNs reside.

Step Action

1. On the Control Station, use this command syntax:

server_security { | ALL} -add-policychap-name

where:

= name of the Data Mover (or use keywordALLfor all Data Movers) = Linux username

Example:

$ server_security server_2 -add -policy chap -name root

2. When prompted, type the CHAP secret for this Linux user.

The secret must be a minimum of 12 and a maximum of 255 characters.

Example:

server_2 :Enter Secret:***************done

3. On the Linux host, use the following command syntax from the local system administrator

or root account:

cbm_security --create

where: = existing username on the Linux host

Example:

# cbm_security --create root

Detailed information about this command appears in the "cbm_security" on page 55.

4. When prompted, type the same secret that was given for this user on the Control Station.

Example:

Please enter chap secret: ***************done

5. Repeat steps 1through 4for each Linux user who will connect to the Celerra iSCSI target.


37/74


Configure iSCSI LUNs as disk drives in Linux

Use this procedure to set up Celerra iSCSI LUNs as disk drives on the Linux host.

Step Action

1. Check the output from the messages file to ensure that the iSCSI service has started.# tail -f /var/log/messages

Sample output:

Feb 16 10:20:24 localhost kernel: Attached scsi generic sg7 atscsi2, channel 0, id 0, lun 130, type 0Feb 16 10:20:24 localhost kernel: Vendor: EMC Model:Celerra iSCSI Rev: 0001Feb 16 10:20:25 localhost kernel: Type: Direct-AccessANSI SCSI revision: 05Feb 16 10:20:25 localhost kernel: SCSI device sdm: 209715200512-byte hdwr sectors (107374 MB)Feb 16 10:20:25 localhost kernel: SCSI device sdm: drive cache:write throughFeb 16 10:20:25 localhost kernel: SCSI device sdm: 209715200512-byte hdwr sectors (107374 MB)Feb 16 10:20:25 localhost kernel: SCSI device sdm: drive cache:write throughFeb 16 10:20:25 localhost kernel: sdm: sdm1Feb 16 10:20:25 localhost kernel: Attached scsi disk sdm at scsi2,channel 0, id 0, lun 131Feb 16 10:20:25 localhost kernel: Attached scsi generic sg8 atscsi2, channel 0, id 0, lun 131, type 0

2. To get a list of the iSCSI targets that are connected to the Linux host, type:

# iscsi-ls

Sample output for a target:

TARGET NAME : iqn.1992-05.com.emc:apm000432002250000-3

TARGET ALIAS : dm2_iscsi_t1HOST ID : 1BUS ID : 0TARGET ID : 0TARGET ADDRESS : 172.24.101.124:3260,1SESSION STATUS : ESTABLISHED AT Sat Sep 16 09:39:36 EDT 2006SESSION ID : ISID 00023d000001 TSIH 3


38/74


3. To get a list of the iSCSI LUNs, type:

#more /proc/scsi/scsi

Sample output:

Attached devices:Host: scsi0 Channel: 00 Id: 00 Lun: 00

Vendor: VMware Model: Virtual disk Rev: 1.0Type: Direct-Access ANSI SCSI revision: 02Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: EMC Model: Celerra iSCSI Rev: 0001 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 00 Lun: 128 Vendor: EMC Model: Celerra iSCSI Rev: 0001 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 00 Lun: 129 Vendor: EMC Model: Celerra iSCSI Rev: 0001 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 00 Lun: 130 Vendor: EMC Model: Celerra iSCSI Rev: 0001 Type: Direct-Access ANSI SCSI revision: 05

Host: scsi1 Channel: 00 Id: 00 Lun: 131 Vendor: EMC Model: Celerra iSCSI Rev: 0001 Type: Direct-Access ANSI SCSI revision: 05

If an expected LUN does not appear in the listing, be sure the LUN has a LUN mask that

allows access by this iSCSI initiator. Configuring iSCSI Targets on Celerraprovides

instructions for creating LUN masks.

4. To partition the iSCSI disk on the Linux host, type:

# fdisk /dev/sdh

Sample output:

Device contains neither a valid DOS partition table, nor Sun, SGIor OSF disklabelBuilding a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previouscontent won't be recoverable.

The number of cylinders for this disk is set to 13054.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:1) software that runs at boot time (e.g., old versions of LILO)2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)Warning: invalid flag 0x0000 of partition table 4 will be correctedby w(rite)

Step Action
http://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htmhttp://localhost/var/www/apps/conversion/tmp/ConfiguringiSCSI/index.htm


39/74


5. At the prompt

Command (m for help):

type the following sequence of commands:

Command (m for help): n (Add a new partition)

Command action e extended p primary partition (1-4)pPartition number (1-4): 1First cylinder (1-13054, default 1): 1Using default value 1Last cylinder or +size or +sizeM or +sizeK (1-13054, default13054):Using default value 13054

Command (m for help):w (Write table to disk and exit)The partition table has been altered!

Calling ioctl() to re-read partition table.Syncing disks.

Step Action


40/74


Using Celerra iSCSI host components for Linux

The topic "Using CBMCLI commands on a Linux host" on page 40provides

instructions for accessing and using the Celerra iSCSI host components for Linux.

Using CBMCLI commands on a Linux host

The root user on the Linux host must use the cbm_security command to create user

credentials that authorize users to run the cbm_iscsi and cbm_replicate commands.

Command syntax conventions

This document uses the following syntax conventions for CBMCLI commands

issued on the Linux host. These conventions, shown in Table 6 on page 40, differ

slightly from those used for Control Station CLI commands.

Table 6 CBMCLI command syntax conventions (page 1 of 2)

Convention Description

Courier typeface Courier typeface indicates command names, option names (alsocalled switches or flags), keywords, and variables.

boldface Boldface indicates an item that is typed exactly as shown,including lower- and uppercase usage.

< > Angle brackets indicate a variable for which a value must besupplied.

Do not type the brackets.

When providing a string value for an argument, enclose the string

in quotation marks if it includes a space character.

| The vertical bar means or and separates alternatives. Use onlyone of them.

{ } Curly brackets surround a required entry. If alternatives appearwithin curly brackets, one of the enclosed items must be specified

on the command line.


[ ] Square brackets surround an optional entry.



41/74


The following pages describe the CBMCLI commands.

--option-o-o|--option

Double dashes precede an option.

A single dash precedes an abbreviated option.

An option that has an abbreviated form is shown as paired

alternatives in the command syntax (without brackets). Either form

may be used. If no abbreviated form is shown, you must type the

full option name with double dashes.

The abbreviation is typically, but not always, the first letter of the

option name, for example:

-d|--delete-n|--dsnap

Some abbreviated options differ only by case, for example:

-d|--delete-D|--demote

Abbreviations are command-specific. The same abbreviation can

equate to different options in different commands, for example:

-s|--snap (in cbm_iscsi)-s|--session (in cbm_replicate)

-s|--secret (in cbm_security)

Table 6 CBMCLI command syntax conventions (page 2 of 2)

Convention Description


42/74


43/74


-s|--snap{|}-i|--info[--get_data]

Returns information about the specified

snapshot.

If included, --get_dataalso returns anycomment text or binary data associated with the

snapshot.

-s|--snap{|}-c|--create[--set_data]

Creates a snapshot of the specified iSCSI LUN.

To associate a comment with the snapshot,

include --set_datawith a maximum of 4096bytes.

-s|--snap{|}-m|--modify--set_data

Changes the comment text or binary data

associated with the specified snapshot,

replacing it with the provided comment text.

-s|--snap{|}-d|--delete{ | ALL}

Deletes the specified snapshot (or all snapshots

if keywordALLis used).

-s|--snap{|}-r|--restore

Restores the data content of the specifiedsnapshot to the production LUN. The device

must be unmounted before the restore

operation.

This operation performs a fast (destructive)

restore. The specified snapshot is preserved,

but all newer snapshots are deleted.

-s|--snap{|}-p|--promote[--mask]

Promotes the specified snapshot.

By default the LUN mask allows the iSCSI

initiator on the local Linux host to access the

LUN. To allow access by a different initiator,

include --maskwith that initiators IQN.

-s|--snap{|}-D|--demote[--noforce]

Demotes the specified snapshot LUN.

If included, --noforcecauses the commandto fail if an iSCSI initiator is using the promoted

LUN.

When demoted, the LUN becomes inaccessible

and any data written to the LUN while it was

promoted is lost.

-v|--version[--ip]

Displays the version number of the CBMCLI

package.

If included, --ipalso returns the versionnumber of the operating system on the

specified Data Mover.

-?|--help Displays command option information.

Option Description


44/74


Example #1

To list all Celerra iSCSI LUNs accessible to the iSCSI initiator from the Celerra

target, type:

$ cbm_iscsi --dev --list

Device: /dev/sdcMount point = not mounted

PLU name = fs56_T3_LUN0_APM00043200225_0000 Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Target LUN = 0Device: /dev/sdd

Partition = /dev/sdd1, Mount point = /lun4 PLU name = fs59_T3_LUN2_APM00043200225_0000 Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Target LUN = 2Device: /dev/sde

Mount point = not mounted PLU name = fs62_T3_LUN5_APM00043200225_0000 Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Target LUN = 5Device: /dev/sdf

Mount point = not mounted PLU name = fs67_T3_LUN10_APM00043200225_0000 Target IQN = iqn.1992-05.com.emc:apm000432002250000-3

Target LUN = 10Device: /dev/sdgMount point = not mounted

PLU name = fs157_T3_LUN100_APM00043200225_0000 Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Target LUN = 100Device: /dev/sdh (snap) Mount point = not mounted Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt027.tws Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Target LUN = 128Device: /dev/sdi (snap) Mount point = not mounted Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt028.tws Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Target LUN = 129Device: /dev/sdk (snap)

Mount point = not mounted Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt015.tws Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Target LUN = 130Device: /dev/sdn (snap) Mount point = not mounted Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt029.tws Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Target LUN = 131Device: /dev/sdo (snap) Partition = /dev/sdo1, Mount point = /snap6 Snap name = fs67_T3_LUN10_APM00043200225_0000.ckpt000.tws Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Target LUN = 132Device: /dev/sdp (snap) Mount point = not mounted Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt030.tws

Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Target LUN = 133Device: /dev/sdq (snap) Mount point = not mounted Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt031.tws Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Target LUN = 134


45/74


Example #2

To get information about an iSCSI LUN, type:

$ cbm_iscsi --dev --info /dev/sdh

Device: /dev/sdh (snap) Mount point = not mounted Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt027.tws Target IQN = iqn.1992-05.com.emc:apm000432002250000-3

Volume size = 107374182400 (bytes) PLU Name = fs56_T3_LUN0_APM00043200225_0000 Destructive restore = yes Create time = Tue Sep 19 14:36:36 2006 Promoted = yes Target LUN = 128

Example #3

To list the snapshots of an iSCSI LUN, type:

$ cbm_iscsi --snap/dev/sdc--list

Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt031 Promoted = yes Create time = Mon Oct 2 13:19:55 2006

Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt030 Promoted = yes Create time = Thu Sep 28 11:24:36 2006Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt029 Promoted = yes Create time = Tue Sep 19 14:43:13 2006Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt028 Promoted = yes Create time = Tue Sep 19 14:39:41 2006Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt027 Promoted = yes Create time = Tue Sep 19 14:34:20 2006

Example #4

To get information about a snapshot of an iSCSI LUN, including any associated

comment text, type:$ cbm_iscsi --snap /dev/sdc--info fs56_T3_LUN0_APM00043200225_0000.ckpt031 --get_data

Snap name = fs56_T3_LUN0_APM00043200225_0000.ckpt031 Target IQN = iqn.1992-05.com.emc:apm000432002250000-3 Volume size = 107374182400 (bytes) PLU Name = fs56_T3_LUN0_APM00043200225_0000 Destructive restore = yes Create time = Mon Oct 2 13:19:55 2006 Promoted = yes Target LUN = 134 ACL count (host IQNs) = 1 iqn.1987-05.com.cisco:01.2e798796a1c Application data length = 0 Application data =

Example #5

To create a snapshot of an iSCSI LUN, type:

$ cbm_iscsi --snap/dev/sdd--create

Creating a new snapshot... done.Snap name = fs59_T3_LUN2_APM00043200225_0000.ckpt002Application label = cbm_iscsi


46/74


Example #6

To modify the comment text associated with a snapshot, type:

$ cbm_iscsi --snap/dev/sdd--modify fs59_T3_LUN2_APM00043200225_0000.ckpt002--set_dataPre-upgrade Q12007

Modifying application data... done.

Example #7

To delete a snapshot of an iSCSI LUN, type:

$ cbm_iscsi --snap/dev/sdd--delete fs59_T3_LUN2_APM00043200225_0000.ckpt002

Deleting snap... done.

Example #8

To restore a production LUN with the content of a snapshot, type:

$ cbm_iscsi --snap/dev/sdk--restore fs56_T3_LUN0_APM00043200225_0000.ckpt015.tws

Warning: Fast/destructive restore.All newer snaps will be deleted after restore, and all new data on allpartitions on this LUN, if any, will be lost (y|n)?yRestoring snap... done.

Example #9

To promote a snapshot, type:

$ cbm_iscsi --snap/dev/sdd--promotefs59_T3_LUN2_APM00043200225_0000.ckpt002

Promoting snap... done.

Example #10

To demote a snapshot, type:

$ cbm_iscsi --snap/dev/sdd--demotefs59_T3_LUN2_APM00043200225_0000.ckpt002

Please make sure that the promoted device is not mounted.All the data written to the promoted LUN will be lost!Do you want to continue (y|n)yDemoting snap... done.

Example #11

To get the version number for the CBMCLI package and for the operating system

on the Data Mover with the IP address 172.24.101.124, type:

$ cbm_iscsi --version --ip 172.24.101.124

cbm_iscsi: version: 1.7.6DART version: T5.5.76.0 (172.24.101.124)


47/74


cbm_replicate

Manages replication of snapshots of a production LUN on a Celerra target to a

remote destination.

Synopsis

Description

Use this command to do the following:

Create a replication session between Celerra source and destination iSCSI

LUNs.

Initiate or cancel replication.

List, modify, or delete replication sessions.

Promote, demote, delete, or list snapshots on the destination. Modify comment text associated with a snapshot.

Restore a production LUN with data from a replicated snapshot.

The destination iSCSI LUN must be read-only and the same size as the source.

cbm_replicate{ --dev{|}

{ -s|--session

{ -l|--list[--dest_ip]| -i|--info{|id=}| -c|--create--alias --dest_ip

--dest_name [--dest_target][--dest_lun] --label[--snap_name]

| -m|--modify {|id=}{[--dest_ip] [--label]}

| -d|--delete{|id=}[--delete_dest_snaps] }

| -n|--dsnap{|id=}

{ -l|--list| -i|--info [--get_data]| -c|--create[--set_data]| -t|--transfer [--set_data]| -C|--cancel [--delete_local]| -m|--modify --set_data| -d|--delete| -r|--restore| -p|--promote [--mask]| -D|--demote [--noforce] }

}

| -v|--version| -?|--help }


48/74


Option Description

--dev{|} Specifies the device name or mount pointof a production iSCSI LUN.

-s|--session

--list|-l[--dest_ip]

Lists the replication sessions for the

specified iSCSI LUN.

If included, --dest_ipreturns sessioninformation only for the specified

destination Data Mover.

-s|--session-i|--info{|id=}

Returns detailed information about the

replication session identified by its session

ID or user-defined alias.


49/74


-s|--session-c|--create--alias--dest_ip--dest_name[--dest_target]

[--dest_lun]--label[--snap_name]

Creates a replication session between a

source iSCSI LUN and a destination iSCSI

LUN.

--aliasspecifies a session identifier(maximum of 256 characters). For a new

session, provide an alias name andinclude --dest_target, --dest_lun,and --label. The same alias can besupplied in subsequent commands to use

the same destination target, LUN, and

session label without specifying those

options.

--dest_ipspecifies the IP address ofthe destination Data Mover.

--dest_namespecifies the name of thedestination Celerra iSCSI target as

defined through the nas_celcommandon the Control Station when setting up

interconnect security between the source

and destination Celerra systems. For

loopback replication, use the name

local.

--dest_targetspecifies the IQN of thedestination iSCSI target when creating a

new session alias. Omit this option when

using an existing session alias.

--dest_lunspecifies the number of theiSCSI LUN on the destination target when

creating a new session alias. Omit this

option when using an existing session

alias.

--labelspecifies an application label

(maximum of 256 characters) for thereplication session. The label is typically

used to identify the application that

performs the replication.

If included, --snap_namespecifies anexisting local snapshot to be transferred to

the destination. Because this operation

synchronous, the command responds

after data transfer is complete.

-s|--session-m|--modify {|id=}{[--dest_ip]

[--label]}

Modifies parameters associated with the

replication session identified by its session

ID or user-defined alias. At least one of the

following options must be included.If included, --dest_ipspecifies the IPaddress for a new destination Data Mover.

If included, --labelspecifies a newapplication label (maximum of 256

characters) for the replication session.

Option Description


50/74


-s|--session-d|--delete{|id=}[--delete_dest_snaps]

Deletes a replication session identified by

its session ID or user-defined alias.

Any data transfer in progress terminates

immediately. All associated resources on

both sides are released.

This is the only action that can beperformed after a fatal error occurs during

a replication session.

If included, --delete_dest_snapsdeletes all remote snapshots of the

destination LUN.

-n|--dsnap{|id=}-l|--list

Lists the snapshots transferred to the

destination for the specified replication

session.

-n|--dsnap{|id=}-i|--info

[--get_data]

Returns information about a destination

snapshot.

If included, --get_datadisplays anyUTF-8 compliant comment text associated

with the snapshot. (Binary data is not

shown.)

-n|--dsnap{|id=}-c|--create[--set_data]

Creates a snapshot of the source iSCSI

LUN and transfers the data to the

destination.

If included, --set_dataassociates thesupplied comment text (a maximum of

4096 bytes) with the snapshot.

-n|--dsnap{|id=}

-t|--transfer[--set_data]

Transfers an existing local snapshot of the

source iSCSI LUN to the destination.

If included, --set_dataassociates thesupplied comment text (a maximum of

4096 bytes) with the snapshot.

-n|--dsnap{|id=}-C|--cancel[--delete_local]

Cancels creation of a destination snapshot

if data transfer is not complete. All

changes made to the destination LUN

during data transfer are undone.

If data transfer has already completed, the

replicated snapshot on the destination is

preserved.

If included, --delete_localdeletes the

local snapshot after the cancel operationcompletes successfully.

-n|--dsnap{|id=}-m|--modify--set_data

Associates the supplied comment text (a

maximum of 4096 bytes) with the

destination snapshot, replacing any

existing comment text or binary data.

Option Description


51/74


Example #1

To list replication sessions, type:

$ cbm_replicate--dev/dev/sde--session--listProduction device = /dev/sdeSession count = 1Session[0]: Replication alias = Job3 Session ID =fs59_T3_LUN2_APM00043200225_0000_fs61_T3_LUN4_APM00043200225_0000 Destination IQN = iqn.1992-05.com.emc:apm000432002250000-3 Destination LUN = 4 Destination IP = 127.0.0.1 Session label = label3

Example #2

To get information about a replication session, type:

-n|--dsnap{|id=}-d|--delete

Deletes a replicated snapshot on the

destination.

-n|--dsnap{|id=}-r|--restore

Restores the source production LUN by

using the content of the specified

snapshot on the destination. The devicemust be unmounted before the restore

operation.

-n|--dsnap{|id=}-p|--promote[--mask]

Promotes a snapshot on the destination.

The promoted LUN is attached to the

same target.

By default the LUN mask allows the iSCSI

initiator on the local Linux host to access

the LUN. To allow access by a different

initiator, include --maskand specify theIQN of the initiator.

-n|--dsnap{|id=}-D|--demote[--noforce]

Demotes a previously promoted snapshoton the destination Data Mover.

If included, --noforcecauses thecommand to fail if the promoted snapshot

is in use by an iSCSI initiator.

After demotion, the LUN is no longer

accessible. Any data written to the LUN

while it was promoted is lost.

-v|--version[--ip]

Displays the version number of the

CBMCLI package.

If included, --ipalso returns the versionnumber of the operating system running

on the specified Data Mover.

-?|--help Displays command option information.

Option Description


52/74


$ cbm_replicate--dev/dev/sde--session--infoJob3

Session attributes: Session ID =fs59_T3_LUN2_APM00043200225_0000_fs61_T3_LUN4_APM00043200225_0000 Replication alias = Job3 Session label = Label3 Session state = WaitingForRequest Source IQN = iqn.1992-05.com.emc:apm000432002250000-3 Source LUN = 2

Destination IQN = iqn.1992-05.com.emc:apm000432002250000-3 Destination LUN = 4 Progress = 0% Source status = WaitingForRequest Source IP = 127.0.0.1 Destination IP = 127.0.0.1 Latest snap created on destination =fs61_T3_LUN4_APM00043200225_0000.ckpt000

Snap in transfer = noneNumber of outstanding snaps marked for replication = 0

Example #3

To create a replication session without transferring a snapshot, type:

$ cbm_replicate--dev/dev/sdb--session--create--aliasJob4--dest_ip127.0.0.1--dest_namelocal

--labelLabel4

Validating destination... done.Configuring the replication session... done.Session Info: Replication alias = Job4 Session ID =fs56_T3_LUN0_APM00043200225_0000_fs63_T3_LUN6_APM00043200225_0000 Destination IQN = iqn.1992-05.com.emc:apm000432002250000-3 Destination LUN = 6

Example #4

To modify a replication session, type:

$ cbm_replicate--dev/dev/sde--session--modifyJob4

--label Session4Modifying the replication session... done.


53/74


Example #5

To delete a replication session, type:

$ cbm_replicate--dev/dev/sde--session--deleteJob4

Deleting the replication session with 0 destination snaps... done.

Example #6

To list destination snapshots, type:

$ cbm_replicate--dev/dev/sdc--dsnapfs59_T3_LUN2_APM00043200225_0000_fs61_T3_LUN4_APM00043200225_0000--list

Destination snaps count = 1Snap name = fs61_T3_LUN4_APM00043200225_0000.ckpt000 Promoted = no Create time = Mon Oct 2 14:32:17 2006

Example #7

To get information about a destination snapshot, type:

$ cbm_replicate--dev/dev/sdc--dsnapfs59_T3_LUN2_APM00043200225_0000_fs61_T3_LUN4_APM00043200225_0000--info fs61_T3_LUN4_APM00043200225_0000.ckpt000

Snap name = fs61_T3_LUN4_APM00043200225_0000.ckpt000 Volume size = 107374182400 (bytes) PLU Name = fs61_T3_LUN4_APM00043200225_0000 Destructive restore = yes Create time = Mon Oct 2 14:32:17 2006 Promoted = no

Example #8

To create a destination snapshot, type:

$ cbm_replicate--dev/dev/sdb1--dsnapJob4--create

Created local snap = fs56_T3_LUN0_APM00043200225_0000.ckpt033Transferring this snap to the destination DM... Progress=0% Progress=100% (transfer completed)Created destination snap = fs63_T3_LUN6_APM00043200225_0000.ckpt001

Example #9

To transfer a local snapshot to the destination, type:

$ cbm_replicate--dev/dev/sdb--dsnapJob4--transfer fs59_T3_LUN0_APM00043200225_0000.ckpt006

Progress=0% Progress=100% (transfer completed)Created destination snap = fs63_T3_LUN6_APM00043200225_0000.ckpt000Setting destination data =

Example #10

To cancel creation of a destination snapshot, type:

$ cbm_replicate--dev/dev/sdc--dsnapJob4--cancelufs1_snap1

Canceling the snap transfer... done.


54/74


Example #11

To modify the comment text associated with a destination snapshot, type:

$ cbm_replicate--dev/dev/sdc--dsnapJob4--modifyufs2_snap1--set_dataDaily backup

Modifying destination app_data... done.

Example #12

To delete a destination snapshot, type:

$ cbm

Installing Celerra ISCSI Host Components 5.6

Documents

Transcript of Installing Celerra ISCSI Host Components 5.6