Cisco MDS 9120, MDS 9124, MDS 9140, MDS 9216, MDS 9216A Configuration Manual

...

Download

HP StorageWorks

C-Series iSCSI conﬁguration guide

Part number: AA-RW7PE-TE

Fourth edition: December 2006

Legal and notice information

Conﬁdential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and

12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation.

Adobe and Acrobat are trademarks of Adobe Systems Incorporated.

Java is a US trademark of Sun Microsystems, Inc.

Oracle is a registered US trademark of Oracle Corporation, Redwood City, California.

Linux is a U.S. registered trademark of Linus Torvalds.

UNIX is a registered trademark of The Open Group.

2006- Hewlett-Packard Development Company, L.P.

Contents

Aboutthisguide....................................... 9

Conﬁgurationguideinformation.............................. 9

Intendedaudience.................................... 9

Relateddocumentation.................................. 9

Using the C- Series IP Storage Ser vices Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and

MDS9216iswitchinaniSCSIenvironment .......................... 10

iSCSIprotocoloverview................................. 10

iSCSIinaSAN .................................... 10

Typicalnetworkstructure .............................. 10

iSCSIInitiator................................... 10

IPnetwork .................................... 10

C-Series IP Storage Services Modu les (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and

MDS9216iswitch................................. 11

FibreChannelSAN ................................ 12

iSCSIhardwareandsoftwaresupport............................. 12

Storagearrays .................................... 12

FibreChannelswitches................................. 13

OperatingsystemsoftwareandiSCSIInitiatorsupport.................... 13

C-Seriesmanagementsoftware ............................. 13

HPnetworkteaming .................................. 13

Networkinterfacecontrollers(NIC)............................ 13

Multi-pathing ..................................... 13

C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2) and MDS

9216i conﬁgurationconstraints ............................... 14

C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Ser vices Module (14/2) and MDS

9216iconstraints ................................... 14

iSCSIhostconstraints.................................. 14

FibreChannelswitchandfabricconstraints ........................ 14

ConﬁguringSANswithC-SeriesswitchesandiSCSIinaWindowsenvironment........... 14

Enabling iSCSI on the C-Series IP Storage Services Modules (IPS-4, IPS-8), M ulti-protocol Services

Module(14/2),andMDS9216iswitch ......................... 15

EnablingtheiSCSIinterface............................. 15

ConﬁguringtheGigabitEthernetinterface....................... 15

PresentingiSCSIhostsasvirtualFibreChannelhosts .................... 16

Transparentmodestaticmapping .......................... 16

InstallinganiSCSIInitiatoronaWindowsserver...................... 16

HP conﬁgurationutilityfornetworkinterfacecards ................... 16

Setup ...................................... 16

Conﬁguringtransparentmodestaticmapping ..................... 19

ZoningtheiSCSIInitiatorWWPNwithFibreChannelstorageWWPN ............ 20

CreatinganiSCSIhost................................. 21

ConﬁguringiSCSIstorageontheEVAcontroller .................... 21

InitialiSCSIInitiatorEVAlogin............................ 21

InstallingtheEVACCLDriversontheiSCSIinitiator................... 24

PresentingEVALUNstotheiSCSIinitiator....................... 25

CreatingLUNsforassignmenttothenewhost ....................... 26

Conﬁguring SANs with C-Series switches, iSCSI, and multi-path access to EVA4000/6000/8000 storage

inaWindowsenvironment ................................. 30

Softwareconstraints .................................. 30

InstallingtheMicrosoftiSCSIInitiator........................... 31

C-Series iSCSI 3

Setup ...................................... 31

EnablingiSCSIontheC-Seriesswitch........................... 31

EnablingtheiSCSIinterface............................. 32

ConﬁguringtheGigabitEthernetinterface....................... 32

Testingconnectivity .................................. 33

PresentingiSCSIhostsasvirtualFibreChannelhosts .................... 33

Host side: iSCSI Initiator conﬁguration ........................ 33

C-Series switch side: c on ﬁguringtransparent-modestaticmapping ............ 35

ZoningtheiSCSIInitiatorandFibreChannelstorageWWPNs................ 36

Creatingzones .................................. 36

Virtualtargeting.................................. 37

CreatinganiSCSIhost................................. 38

InitialiSCSIInitiatorEVAlogin............................ 38

InstallingtheEVACCLDriverontheiSCSIInitiator ................... 40

PresentingEVALUNstotheiSCSIInitiator....................... 40

SettingMPIOloadbalancingpolicy ......................... 41

Conﬁguringp-ClassBladeserversinaniSCSIenvironment.................. 42

Conﬁguringp-ClassBladeCGESMserverenclosureinterconnects............. 42

Conﬁguringp-ClassBladeGbE2serverenclosureinterconnects.............. 45

Conﬁguringp-ClassBladeservernetworksettings ................... 48

Figures

1 2

3 4

5 6 7

9 10 11 12 13

14 15 16

17 18 19 20 21 22 23 24 25 26 27 28

29 30 31 32 33 34 35 36 37 38 39 40 41 42

..TypicalIP/FCnetworkstructure.......................... 11

..IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2 ), and MDS

9216iswitchmap................................ 12

..MicrosoftiSCSIInitiatoricon........................... 17

..iSCSIInitiatorPropertieswindow ......................... 17

..AddTargetPortalwindow............................ 17

..iSCSIInitiatorProperties—TargetPortals ...................... 18

..IPiSCSIwindow—Initiatorstab.......................... 18

..IPiSCSIwindow—Settingtransparentmodestaticmapping.............. 19

..C-SeriesZonecontainingiSCSIInitiatorwithsingleHSVport ............. 21

..Availabletargets—Inactivestatus......................... 22

..LogOntoTarget—Setpersistenttarget ...................... 23

..Availabletargetswindow—Connectedstatus.................... 23

..ActiveSessionstab—Connectedstatus....................... 24

..HostFolder—Addhost ............................. 25

..AddaHostwindow .............................. 26

..Hostsfolder—HostProperties........................... 26

..VirtualDisk—FolderProperties.......................... 27

..CreateaVdiskFamilywindow,Page1 ...................... 27

..CreateaVdiskFamilywindow,Page2 ...................... 28

..VdiskActiveMemberProperties ......................... 28

..iSCSIInitiatorProperties—SessionDetails ..................... 29

..WindowsDiskManagement........................... 29

..Multi-pathediSCSIsetup............................. 30

..Enablingmulti-pathingsupportforiSCSI...................... 31

..iSCSIInitiatorPropertieswindow ......................... 33

..AddTargetPortalwindow............................ 34

..BothC-Seriesswitchesaretargetportals...................... 35

..IPiSCSIwindow ................................ 35

..DiscoveryDynamiccheckbox .......................... 36

..Node Address Persistent and N ode Address System Assigned check boxes . . . . . . . 36

..iSCSIInitiatorzonedwithanEVAstorageport ................... 37

..TheTargetstab................................. 37

..CreateiSCSITargetswindow........................... 38

..Virtual targets deﬁnedforhost .......................... 39

..LogOntoTargetwindow ............................ 39

..Bothportspresentedtothehost.......................... 40

..Rescanningdisks................................ 41

..SelectingLoadBalancePolicy .......................... 42

..VerifyingC-SeriesiSCSIsessions ......................... 42

..Switchwebpage................................ 44

..Disablingaport ................................ 45

..Interconnecttelnetsession ............................ 45

C-Series iSCSI

..BBImainwindow................................ 46

..SwitchPortsiconlocation ............................ 46

..Disablingaport ................................ 47

..SwitchPortsDashboard............................. 48

..AssigningastaticIPtoanetworkinterface..................... 49

Tables

..C-SeriesiSCSIlimits............................... 14

.. iSCSIhostlimitsforWindows2003 ....................... 14

C-Series iSCSI

About this guide

This guide describes the basic setup and conﬁguration for iSCSI using the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), or MDS 9216i Fibre Channel switch.

This section describes the following topics:

•Conﬁguration guide information

• Intended audience

• Related documentation

Conﬁguratio

n guide information

This guide co

• Using the C-Series IP Storage Services Modules, Multi-Protocol Services Module and MDS 9216i switch

• H ardware an

•Conﬁguration constraints

•Conﬁguring C-Series IP Storage Services Modules, Multi-protocol Services Module and MDS 9216i swit

vers the following topics:

d software support

ch in an HP Fibre Channel SAN

Intended audience

This document is intended for customers who have purchased an IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), or MDS 9216i switch and are planning to use the iSCSI functionality in these products.

This document assumes a thorough understanding of HP Fibre Channel storage networking products, including Fibre Channel switches and storage, as well as a basic understanding of TCP/IP networking.

Related documentation

Refer to

• Cisco® MDS 9000 Family Command Reference Guide

• Cisco MDS 9000 Family Fabric Manager Conﬁguration Guide

• Cisco MD

the following Cisco documentation for more information:

S 9000 Family Software Conﬁguration Guide

onal documentation is available at the following HP web site:

Additi

/h18006.www1.hp.com/storage/saninfrastructure.html

ttp:/

On the H

P Storage SAN Infrastructure webpage, scroll to the C-Series Fabric section.

C-Series iSCSI 9

Using the C-Seri

es IP Storage Services Modules (IPS-4, IPS-8), Multi-protoco switch in an iSC

l Services Module (14/2), and MDS 9216i

SI environment

iSCSI protocol overview

iSCSI is a SCSI transport protocol for mapping of block-oriented storage data over TCP/IP networks through iSCSI protocol data units (PDUs). The iSCSI protocol enables universal access to storage devices and storage area networks (SANs) over standard Ethernet-based TCP/IP networks. These networks m ay be dedicated networks or may be shared with traditional Ethernet applications. IP LAN/WAN routers and switches can b e used to extend the IP storage net work to a wide area of applications such as synchronous and asynchronous remote disk copy or tape backup and restore.

iSCSI in a SAN

Although th discusses t Storage Se

Typical network structure

When you add iSCSI to a large SAN, you must conﬁgure and manage two data protocols: TCP/IP and Fibre Channel. IP hosts with iSCSI initiators access C-Series IP Services through an IP network connected to the C-Series Gigabit Ethernet (GbE) interface. The C-Series IP Services access Fibre Channel storage devices connected to the Fibre Channel interfaces through the FC ports within the C-Series chassis or through the FC ports of the IP switch. Figure 1 shows a typical IP/Fibre Channel network.

e iSCSI protocol is written as a complete data transport from host to storage, this guide only

he current H P suppor ted topology of iSCSI hosts to Fibre Channel storage using the C-Series I P

rvices Modules (IPS-4, IPS-8) , Multi-protocol Services Module (14/2), and the 9216i switch.

iSCSI In

itiator

With the IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Modu le ( 1 4/2 ), and MDS 9216i switch, the IP host uses an iSCSI initiator to enable target resource recognition and a t tachment. The C-Se number the HP F directly connected to the SAN.

LUN setup and LUN masking can now be conﬁgured with this WWPN. The iSCSI Initiator then sees these storage resources (LUNs) as if they were local drives attached directly to the server.

IP network

The I P network is the infrastructure used to transfer data between the iSCSI Initiator and the C-Series IP Services via TCP/IP. LA N switches tend to be Ethernet-based, supporting speeds from 10 Mb/s to 10 Gb/s, using copper and optical interfaces ranging in size from a few ports to hundreds of ports.

LAN switches typically support TCP/IP and other protocols, including TCP/UDP, IPX, and AppleTalk.

Other features found in many LAN switches include support for voice-over-IP (VoIP), quality of service (QoS), bandwidth management and reporting, multi-cast and jumbo frames. With the advent of SCSI storage data now being transferred within an IP network, it is important to recognize and understand the level of service necessary to avoid loss of data.

Part of the appeal that iSCSI brings to the storage market is low cost, standardized network adapters and topology hardware, in addition to years of expertise developed i n deploying these networks. However, it should be stressed that existing networks must be evaluated for suitability regarding their capacity to support iSCSI storage. In any deployment, HP recommends using a dedicated Gigabit Ethernet network bet ween iSCSI Initiators and the C-Series I P Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), or MDS 9216i switch. This ensures adequate performance as

ries IP Services connect directly to HP’s Fibre Channel SAN storage via an IP–to–worldwide port

(WWPN) translation provided by the C-Series IP Services. With this transparent SCSI forwarding,

ibre Channel SAN Storage recognizes this WWPN as it would from any Fibre Channel HBA

well as helping to provide data security. An alternative is to use IPSec to secure the connection, although therewillbeaperformanceimpact.

Client, Host, or

iSCSI Initiator

has the ‘iSCSI Initiator’

loaded on it to enable

Target Resource Recognition & Attachment. Storage Target Resources

(LUNs) appear as if they are local drives attached

directly to the system.

iSCSI

Initiator

iSCSI

Initiator

Network

Networ

iSCSI

Initiator

C-Series IP Storage Services Modules, 14/2 Multi-protocol

Services Module and MDS 9216i

1. Defines Client Access.

2. Defines Paths to Targets.

3. Converts Ethernet IP to FC Protocol and Vice Versa.

4. Provides Target Addressing.

Fibre Channel

MDS Switch

Fabric

MDS Switch

SAN Storage

has the LUNs (resources)

configured without ANY

special drivers, firmware,

or protocols.

FCFC

HP Fibre Channel

Storage

Figure 1 Typical IP/FC network structure

C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i switch

P Storage Services M odu les (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and the MDS

The I 9216i switch provide IP hosts access to Fibre Channel storage devices. The IP host sends SCSI commands encapsulated in iSCSI protocol data units (PDUs) to a C-Series IP por t over a TCP/IP connection. At this point, the SCSI commands are transferred from a n IP network into a Fibre Channel network and

warded to the intended target. Figure 2 illustrates an IP Storage Services Modules (IPS-4, IPS-8),

for

ti-protocol Ser vices Module (14 /2), and MDS 9216i switch network.

Mul

C-Series iSCSI

Figure 2 IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), an d M

In conjunction with presenting Fibre Channel targets to iSCSI hosts, the IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2) and MDS 9216i switch present each iSCSI host as a Fibre Channel host (in transparent mode), that is, as a host bus ad apter ( H BA) to the Fibre Channel storage device. The storage device responds to each IP host as if it were a Fibre Channel host connected to the Fibre Channel network

DS 9216i switch map

Fibre Channel SAN

A SAN is a dedicated, centrally managed, secure information infrastructure, which enables any-to-any interconnection of servers and storage. SANs are built to incorporate the best of both storage and networking interfaces: fast and efﬁcient communications optimized for movement of large amounts of data, but with access to a wide range of other servers and storage devices on the network.

The C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i switch are suppor ted on any currently suppor ted HP infrastructure C-Series switch fabric.

iSCSI h ardware and software support

This section lists the HP-supported hardware, drivers, and operating systems that are compatible with the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2) and MDS 9216i switch within an iSCSI environment. For further information regarding speciﬁcversionandﬁrmware information, refer to the C-Series IP Storage Services Module, 14/2 Multiprotocol Services Module, and MDS 9216i switch support tables, which can be downloaded from the following HP web site:

ttp://www.hp.com/support/manuals

In the Storage section, select the SAN Infrastructure link. Go to the C-Series section and select the link for the Cisco MDS9216i Multilayer Fabric Switch.

Storage arrays

The following HP storage array products are supported by iSCSI initiators connected to the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2) and MDS 9216i switch:

• RA/MA8000

• ESA/EMA12000

• EM A16000

• EVA3000, EVA5000

• EVA4000, EVA6000, EVA8000

• MSA1000, MSA1500

• VA7100, VA7110, VA7400, VA7410

• XP48, XP128, XP512, XP1024, XP12000, XP10000

Fibre Channel switches

The C-Series IP S are suppor ted w

• MDS 9216, MDS 9216A, MDS 9216i Multilayer Fabric Switches

• MDS 9506, MDS 9509, MDS 9513 Multilayer Director Switches

NOTE:

The MDS 9216i s

torage Services Modules (IPS-4, IPS-8), and Multi–protocol Services Module (14/2)

ith the following HP C-Series Product Line switches:

witch contains two embedded IP ports.

Operating system software and iSCSI Initiator support

Refer to the HP StorageWorks C-Series iSCSI support tables located at:

ttp://www.hp.com/support/manuals

In the Storage section, select the SAN Infrastructure link. Go to the C-Series section and select the link for the Cisco MDS9216i Multilayer Fabric Switch.

C-Series management software

The following management software is supported:

• Cisco Fabric Manager

• Cisco Device Manager

• CLI

HP network teaming

HP NIC teaming is supported with the Windows operating system only.

Network interface controllers (NIC)

All NICs supported by HP are supported for this product. For optimal performance, HP recommends that Gigabit Ethernet NICs be used.

Multi-pathing

Multi-pathing is supported on EVA4000/6000/8000 only in a Windows environment using the Microsoft Multipath I/O driver (MPIO), supported with iSCSI. Without multi-path capabilities, the iSCSI initiator can only access one path of the storage controllers, which disables controller failover protection.

C-Series iSCSI 13

C-Series IP Stor

age Services Modules (IPS-4, IPS-8), Multi-protoco conﬁguration c

l Services M odule (14/2) and MDS 9216i

onstraints

C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2) and MDS 9216i constraints

Table 1 C-Se ries i SCSI limits

iSCSI component Maximum

iSCSI host connections per port

Active LUNs per port

Number of Initiator/Targets (IT) Nexus per port

Number of active LUNs per IT Nexus

Number of IT Nexus/LUNs combinations per port

Examples of maximum conﬁgurations for IT Nexus:

• 200 iSCSI initiators each connected to one target (storage controller port)

• 100 iSCSI initiators each connected to two targets

• 50 iSCSI initiators each connected to two targets and 100 iSCSI initiators each connected to

one target

200

256

1200

iSCSI host constraints

Table 2 iSCSI host limits for Windows 2003

iSCSI host component

Targets accessed per host

LUNs per target

Maximum

255

Fibre Channel switch and fabric constraints

The C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i switch are s upported on any currently supported HP Infrastructure C-Series switch fabric. For the latest HP Infrastructure switch topologies and fabric rules, refer to the HP StorageWorks SAN design reference guide, which can be downloaded from the following web site:

ttp://h18000.www1.hp.com/products/storageworks/san/documentation.html

Conﬁguring SANs with C-Series switches and iSCSI in a Windows environment

To conﬁgure the C-Series IP Storage Ser vices Modules (IPS-4, IPS-8), M ulti-protocol Services Module (14/2)andMDS9216iswitchinanHPFibreChannelSAN:

1. Enable iSCSI on the C-Series switch

2. PresentiSCSIhostsasvirtualFChosts

3. Install the Microsoft iSCSI initiator

4. Zone the iSCSI initiator WWPN with Fibre Channel storage WWPN

5. Create an iSCSI host

These procedures are described in the following sections. They enable you to quickly set up a basic connection between an iSCSI server and Fibre Channel storage. For advanced conﬁguration parameters such as CHAP, V RRP, or VSANs, refer to the appropriate Cisco technical manuals and your iSCSI Initiator documentation.

NOTE:

This section uses Microsoft Windows in examples where host software is conﬁgured for iSCSI. To conﬁgure iSCSI for other operating systems, consult the host software documentation. The i SCSI conﬁguration procedures for C-Series products are independent of the host operating system.

Enabling iSCSI on the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Ser vices Module (14/2), and MDS 9216i switch

To conﬁgure the iSCSI feature, you must explicitly enable iSCSI on the required switches in the fabric. By default, this feature is disabled in all switches in the C-Series family.

The conﬁguration and veriﬁcation commands for the iSCSI feature are available only when iSCSI is enabled o n a switch. When you disable iSCSI, all related conﬁgurations are automatically discarded.

To enable iSCSI on any participating switch using CLI:

1. Enter conﬁguration mode: switch# config t

2. Enable iSCSI on the switch: switch# iscsi enable

To disable iSCSI on any participating switch using CLI: switch# no iscsi enable

Enabling the iSCSI interface

Before iSCSI processing begins on any physical Gigabit Ethernet interface, you must enable the corresponding iSCSI interface.

To enable an iSCSI interface:

1. Create and enable the required Gigabit Ethernet interface (slot 2, p ort 2) :

switch# config terminal switch(config)# interface gigabitethernet 2/1 switch(config-if)# no shutdown

2. Create and enable the required iSCSI interface:

switch(config-if)# exit switch(config)# interface iscsi 2/1 switch(config-if)# no shutdown

Conﬁguring the Gigabit Ethernet interface

iSCSI relies on TCP/IP for network connectivity. On each C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i switch, connectivity is provided in the form of Gigabit Ethernet interfaces that are appropriately conﬁ gured.

NOTE:

Gigabit Ethernet ports on any C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i switch should not be conﬁgured in the same Ethernet broadcast domain as the management Ethernet port. HP recommends that you conﬁgure them in a different broadcast domain, either by using separate standalone hubs or switches or by using separate VLANs.

C-Series iSCSI

To conﬁgure IP for subse quent use by iSCSI initiators:

1. Enter conﬁguration mode: switch# config terminal

2. Enter the interface conﬁguration mode on the Gigabit Ethernet interface (slot 2, port 2) :

switch(config)# interface gigabitethernet 2/2

3. Enter the IP address (33.33.33.170) and subnet mask (255.255.255.0) for the Gigabit Ethernet

interface: switch(config-if)# ip address 33.33.33.170 255.255.255.0

4. Enable the interface: switch(config-if)# no shutdown

Presenting iSCSI hosts as virtual Fibre Channel hosts

Because you are converting SCSI commands to and from an iSCSI IP server to Fibre Channel storage, the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i sw Storage recognizes.

The IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i switch have two modes to present iSCSI hosts in the Fibre Channel fabric: transparent mode and proxy initiator mode. HP recommends the use of transparent mode as described in this guide.

The beneﬁtoftransparentmodeisthatitallowsaﬁner level of access control conﬁguration. In transparent mode, each iSCSI host is presented as one virtual Fibre Channel host on the Fibre Channel fabric. Because o can have

Transparent mode static mapping

itch must map the ISCSI server’s IP address to a unique WWP N that the Fibre Channel

f the one-to-one mapping of IP-to-WWPN translation from iSCSI to Fibre Channel, each host

different zoning in the Fibre Channel SAN or LUN access control on the Fibre Channel storage.

The C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i switch have two modes of mapping IP addresses: transparent-mode dynamic mapping and transparent-mode static mapping. Because the Microsoft iSCSI Initiator does not support Dynamic partitions, you must conﬁgure using transparent mode static mapping. Static mapping must be enabled for each iSCSI Initiator to guarantee persistent LUN mapping from the HP Fibre Channel controller to the iSCSI Initiator. See Conﬁguring transparent mode static mapping for instructions.

Installing an iSCSI Initiator on a Windows server

TheIPhostoriSCSIInitiatorusestheMicrosoftiSCSIInitiatortoenabletargetresourcerecognitionand attachment to the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i switch over IP. The Microsoft iSCSI Initiator is conﬁgured with the Gigabit Ethernet IP address of each iSCSI interface running on the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i to which the host is to transport SCSI

uests and responses. The iSCSI Initiator sees the storage resources (LUNs) as if they were local

req drives at tached directly to the server.

HP conﬁguration utility for network interface cards

With HP ProLiant servers, an iSCSI Initiator may use multiple NIC cards with HP teaming enabled for failover. The term team refers to the concept of multiple network adapters working together as a single network adapter, commonly referred to as a virtual network adapter.

tup

ownload the iSCSI Initiator from Microsoft's download page, a nd follow the installation instructions.

he download includes copying the user guide to your local disk. You can refer to the user guide in

:\Program Files\Microsoft iSCSI Initiator\uguide.doc for further information.

he ﬁrst use of the Microsoft iSCSI initiator, requires a manual log in to the Available Targets. After the

T Available Target logins are completed with the Restore Connection but ton enabled, the iSCSI Initiator automatically logs in whenever the server powers up or reboots.

During setup, the install procedure places a Microsoft iSCSI Initiator icon (Figure 3)ontheserver desktop as well as in the control panel. The Microsoft iSCSI Initiator also has a CLI. Refer to the user guide for more information.

Figure 3 Microsoft iSCSI Initiator icon

To install the Microsoft iSCSI Initiator:

1. Double-click the Microsoft iSCSI Initiator icon to open the iSCSI Initiator P roperties window

(Figure 4).

Figure 4 iSCSI Initiator Propert ies wind ow

2. Click Add to add the IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module

(14/2),, or MDS 9216i switch iSCSI Ethernet address to the initiator.

The Add Target Portal window appears (Figure 5).

NOTE:

This example uses the GbE address (33.33.33.170).

Figure 5 Add Target Portal window

3. Enter the appropriate information in the following boxes:

•IPaddressorDNSname

C-Series iSCSI

•Socket

4. Click OK.

The I P address is added to the Available Portals list (Figure 6).

The iSCSI Initiator connects to the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2),, or MDS 9216i switch.

TheC-SeriesIPStorageServicesModules(IPS-4,IPS-8),Multi-protocolServicesModule(14/2),or MDS 9216i switch generates a unique WWPN for the iSCSI initiator’s IP address.

Figure 6 i

SCSI Initiator Properties—Target Portals

You can verify the iSCSI connection and WWPN mapping on the IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and M DS 9216i switch two ways:

• With the Device Manager GUI:

Select IP > iSCSI. The IP iSCSI window appears (Figure 7).

Figure 7 IP iSCSI window—Initiators tab

• With the CLI:

Enter the show iSCSI initiator command.

Example:

MDS9216i# show iscsi initiator iSCSI Node name is iqn.1991-05.com.microsoft:w2k3x03.sanbox.com

Initiator ip addr (s): 33.33.33.143 iSCSI alias name: Node WWN is 21:0f:00:0d:ec:0d:2c:42 (dynamic) Member of vsans: 1 Number of Virtual n_ports: 1

Virtual Port WWN is 21:0e:00:0d:ec:0d:2c:42 (dynamic) Interface iSCSI 1/1, Portal group tag: 0x0 VSAN ID 1, FCID 0x7e0015

IMPORTANT:

By default, transparent mode mapping is set to mode mapping must be set to the HP Fibre Channel controller to the iSCSI Initiator.

Static

for each iSCSI Initiator to guarantee persistent LUN mapping from

Conﬁguring transparent mode static mapping

The C-Series IP Storage Services Modules (IPS-4, IPS-8), M ulti-protocol Services Module (14/2), and MDS 9216i switch have two modes of mapping IP addresses:

• Transparent mode dynamic mapping

• Transparent mod e static mapping

Dynamic

when the initiator entry is created. Transparent

You must enable static mapping for each iSCSI Initiator to guarantee persistent LUN mapping from the HP Fibre Channel storage controller. There are two ways to enable static mapping:

• With the Device Manager GUI:

1. Select IP > iSCSI from the Device Manager tool bar.

The IP iSCSI window appears (Figure 8).

Figure 8 IP iSCSI window—Setting transparent mode static mapping

2. Clear the Dynamic check box.

3. Select the Persistent check box.

4. Select the System Assign ed check box.

5. Click Apply.

6. Close the IP iSCSI window.

C-Series iSCSI 19

7. Select Admin > Save Conﬁguration from the D evice Manager tool bar.

• With the CLI:

1. Enter the show iscsi initiator command to view the iSCSI initiators.

Example:

MDS9216i# show iscsi initiato r iSCSI Node name is iqn.1991-05.com.microsoft:w2k3x03.sanbox.com Initiator ip addr (s): 33.33.33.143 iSCSI alias name: Node WWN is 21:0f:00:0d:ec:0d:2c:42 (dynamic) Member of vsans: 1 Number of Virtual n_ports: 1 Virtual Port WWN is 21:0e:00:0d:ec:0d:2c:42 (dynamic) Interface iSCSI 1/1, Portal group tag: 0x0 VSAN ID 1, FCID 0x7e0015

2. Use the config terminal command to change the iSCSI Initiator entry from Dynamic to

Persistent. You can change either the iSCSI qualiﬁed name (IQN) or the IP address.

Example:

MDS9216i# conﬁgterminal

• MDS9216i#(conﬁg) iscsi save-initiator name iqn.1991-05.com.microsoft:w2k3x03.san-

box.com

• MDS9216i#(conﬁg) iscsi save-initiator ip-address 33.33.33.143

3. Enter the show iscsi initiator command to verify the change:

Zoning th

At this point we have a unique WWPN that acts as a virtual Fibre Channel host available on the Fibre Channel SAN. This unique WWPN can be zoned with Fibre Channel storage as if it were a Fibre Channel

NOTE:

This section uses a n Enterprise Virtual Array as a n example to conﬁgure iSCSI. Consult the appropriate documentation for the storage array that is actually used.

Example:

MDS9216i# show iscsi initiator

iSCSI Node name is iqn.1991-05.com.microsoft:w2k3x03.sanbox.com

Initiator ip addr (s): 33.33.33.143 iSCSI alias name: Node WWN is 21:0f:00:0d:ec:0d:2c:42 (configured)

Member of vsans: 1 Number of Virtual n_ports: 1

Virtual Port WWN is 21:0e:00:0d:ec:0d:2c:42 (configured) Interface iSCSI 1/1, Portal group tag: 0x0

VSAN ID 1, FCID 0x7e0015

4. Enter the save run start command to save the conﬁguration.

Example:

MDS9216i# save run start

e iSCSI Initiator WWPN with Fibre Channel storage WWPN

HBA.

You can use either Fabric Manager or the switch CLI to create and modify SAN zones. As a best practice of SAN management, HP recommends that you create separate iSCSI zones that contain the iSCSI WWPNs and the storage WWPNs it will access. Refer to the Cisco conﬁguration documentation to create, modify, or activate SAN zones.

NOTE:

HP does not support multi-pathing software installed on non-Windows iSCSI initiators connected to the C-Series IP Storage Services Modules (IPS-4, IPS-8), Mu lti-protocol Services Module (14/2), or MDS 9216i switch. iSCSI initiators can be zoned with only a single WWPN from the HP storage controller.

Figure 9 shows an example of an iSCSI initiator, W2KX03 (33.33.33.143), zoned with a single port

from an EVA named HSV04, in a zone named iSCSI-HSV04-ONE-PORT.

When the new zone is activated, the iSCSI Initiator can log in to the storage controller.

Figure 9 C- Series Zone containing iSCSI Initiator with single HSV port

Creating an iSCSI host

Conﬁguring iSCSI storage on the EVA controller

During initial setup, the iSCSI Initiator must log in to the storage controller before the EVA can recognize the iSCSI initiator’s WWPN. You can set the controller port as a Persistent Target which will permit the iSCSI Initiator to reconnect to the storage controller after a power cycle or reboot.

CAUTION:

FailuretoenablePersistentTargetduringcontroller login prohibits the iSCSI I nitiator from accessing storage automatically after a power cycle or reboot, requiring another login to the storage controller.

Initial iSCSI Initiator EVA login

1. From

the the Microsoft iSCSI Initiator Properties window's Available Targets tab, click Refresh.

C-Series iSCSI 21

The iSCSI Initiator rescans the connection to the storage port. Upon successful rescan, the iqn of the storage controller port appears under Name with a status of Inactive (Figure 10).

Figure 10 Available targets—Inactive status

2. Select the storage controller Name and then click Log On.

The Log On to Target window appears (Figure 11).

Figure 11 Log On to Target—Set persistent target

3. Select the Automatically restore this connection when the system boots check box to ensure that the

controller port is enabled as a persistent target.

4. Click OK.

The Available Target window shows the status for the storage controller iqn as Connected (Figure 12).

Figure 12 Available targets window—C onnected status

5. Click the Active Sessions tab to verify the connection to the EVA.

The storage controller session Status appears as Connected (Figure 13).

C-Series iSCSI 23

Figure 13 Active Sessions tab—C o nn ected sta tus

Installing the EVA CCL Drivers on the iSCSI initiator

At this point, the Windows New Hardware Found Wizard may appear, because the EVA (Command Console LUN) CCL was discovered by the operating system. This Wizard requires the following two ﬁles:

• The EVA CCL driver—HsgCCL.inf

• The Windows security ﬁle—HsgCCL.cat

These ﬁles are located on the Windows EVA Platform Kit CD. The Windows EVA Platform Kit can also be downloaded from the HP web site:

ttp://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?locBasepartNum=co-

17666-2

CAUTION:

Do not install the Windows EVA Platform Kit on the iSCSI server. Only extract the necessary ﬁles to complete the EVA CCL Driver installation.

The following procedure is the same if you are loading the ﬁles from the CD or downloading from the web site. To extract the HsgCCL.inf, and HsgCCL.cat ﬁles:

1. Copy the HP Package ﬁle \Setups\cp003937.exe to a temporary location on the iSCSI server.

2. Double click cp003937.exe tostarttheHPPackageSetup.

The HP Package Setup Window appears.

3. Click Extract.

4. Select or create a temporary folder, and then click OK.

All ﬁles in the package are copied to the speciﬁed folder.

5. Resume the Windows Found New Hardware Wizard.

When prompted, point it to the temporary folder where the driver and security ﬁle reside.

Follow the instructions provided by the wizard .

Presenting EVA LUNs to the iSCSI in itiator

After the iSCSI Initiator connects to the EVA controller, the EVA recognizes the iSCSI Initiator WWPN that was mapped from the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2),, or MDS 9216i switch as if it were a Fibre Channel HBA. The EVA can use the iSCSI Initiator WWPN to create a

NOTE:

This section describes conﬁguring LUNs on an EVA. For conﬁguring LUNs on other storage products, refer to the procedures described i n the product documentation.

The EVA is managed and conﬁgured with Command View EVA.

To create an EVA host entry:

1. Select the Storage Array icon and click the Hosts folder (Figure 14).

host entry and present LUNs to the host entry.

Figure 14 Host Folder—Add host

2. Click Add host.

The Add a Host window appears (Figure 15).

C-Series iSCSI 25

Figure15AddaHostwindow

3. Enter information into the following boxes:

•Hostname

•PortWWName

•HostOS

4. Click Add host.

ThenewPortWWNameisaddedtothePortWWNamelist.

The host name appears in the Hosts folder (Figure 16).

Figure 16 Hosts folder—Host Properties

Creati

ng LUNs for assignment to the new host

ate LUNs:

To cre

1. Select the Storage Array icon a nd click on the Virtual Disks folder (Figure 17).

Figure 17 Virtual Disk—Folder Properties

2. Click Create Vdisk.

The Create a Vdisk Family window appears (Figure 18).

Figure 18 Create a Vdisk Family window, Page 1

NOTE:

The example in Figure 18 shows an example of creating a 4 GB Raid, 5 LUN and presenting it to the EVA iSCSI Initiator Host Entry W2K3X03.

3. Enter the information for the new vdisk in the following boxes:

•Vdiskname

•Size

•WriteCachepolicy

• Read Cache policy

• Present to host

• Preferred path/mode

Select the appropriate redundancy

C-Series iSCSI 27

4. Click Next step.

The next Create a Vdisk Family window appears (Figure 19).

Figure 19 Create a Vdisk Family window, Page 2

5. Enter a number in the Available LUN for this host box.

The LUN is sent to the iSCSI host.

6. Click Finish.

7. Repeat the procedure to create additional LUNs as needed.

ThenewLUNsarelistedundertheVirtualDisksfolder(Figure 20).

Figure 20 Vdisk Active Member Properties

The new LUN is available to the iSCSI Initiator. To verify the availability of the LUN:

1. Return to the Microsoft iSCSI Initiator Properties window.

2. Click Active Sessions.

3. Select the appropriate Session Name, and then click Details.

The LUN appears in the Session Details list (Figure 21).

NOTE:

The EVA CCL appears as an Unavailable device.

Figure 21 iSCSI Initiator Properties — S ession Details

Under Windows Disk Management, the LUNs appear as initialized partitions (Figure 22). You can conﬁgure the disk partition like any other disk partition available to the operating system.

NOTE:

The Microsoft iSCSI Initiator does not support dynamic partitions.

Figure 22 Windows Disk Management

C-Series iSCSI 29

Conﬁguring SAN

swithC-Seriesswitches,iSCSI,and

multi-path acc

ess to EVA4000/6000/8000 storage in a

Windows envir

To conﬁgure iSCSI in a Windows environment that includes multi-pathing and EVA storage:

"Install the M

"Enable iSCSI on the C-Series switch"onpage31

"Test connectivity" on page 33

"Present iSCSI

"Zone the iSCSI Initiator and Fibre Channel storage WWPNs" on page 36

"Creating an iSCSI host" on page 38

7. "Conﬁguringp-ClassBladeserversforiSCSI" on page 42

These p rocedures are described in the following sections. They enable you to quickly set up a basic multi-path connection between a Windows iSCSI host and Fibre Channel storage .

Be sure to verify that your planned multi-path iSCSI solution conforms to the rules in the Operating

system const

NOTE:

HP recommends using GbE NICs and IP switches in an iSCSI environment.

For advanced conﬁguration parameters with CHAP, VRRP, or VSANs, see the appropriate Cisco documentation and the iSCSI Initiator documentation. For more information about p-Class Blade server setup and conﬁguration, c onsult the p-Class Blade server documentation.

raints, page 30 section.

onment

icrosoft iSCSI Initiator" on page 31

hosts as virtual Fibre Channel hosts"onpage33

Figure 23 Multi-pathed iSCSI setup

Software constraints

The following are not supported:

• HP Secure Path for MSA1000/1500, RA/MA8000, EMA/ESA12000, EVA3000/5000, VA, XP

• HP Auto Path for XP/VA

• All non-HP multi-pathing products except for Microsoft MPIO for Windows

Installing the Microsoft iSCSI Initiator

The IP host uses its NICs and the Microsoft iSCSI Initiator to enable iSCSI. The Microsoft iSCSI Initiator is conﬁgured with

Setup

Uninstall any installed version of the Microsoft Initiator before installing the current version. Download the iSCSI Initiator and User’s Guide (uguide.doc) from the Microsoft web site (search for “iSCSI” at www.micr osoft.com) and follow the installation instructions. See "Install the Microsoft iSCSI

initiator" on page 16“ for more information.

In the Software Update Installation Wizard, at the Installation Options screen (Figure 24), select Microsoft MPIO M ultipat hing Support for iSCSI. By default this value is disabled.

the GbE address of each iSCSI interface that the host will access.

Figure 24 Enabling multi-pathing support for iSCSI

A Microsoft iSCSI Initiator icon is placed on the server desk top and in the control panel. See the Microsoft user guide for more information.

Enabling iSCSI on the C-Series switch

To enable the iSCSI feature, you must explicitly enable iSCSI on all switches connected to the iSCSI

ators. By default, this feature is disabled on all C-Series switches.

Initi

In the example, the subnets of the switches match the static I Ps assigned to the two NICs in the blade server. One switch has an IP address of 20.20.20.1 for its GigE port, a nd the other switch has an IP address of 20.20.21.1 for its GigE port.

C-Series iSCSI 31

The conﬁguration and veriﬁcation commands for the iSCSI feature are available when iSCSI is enabled on the switch. When you disable iSCSI, all associated c onﬁgurations are automatically discarded.

To use the CLI to enable iSCSI on a C-Series switch:

1. Enter conﬁguration mode:

switch # conﬁgterminal

2. Enable iSCSI on the switch:

switch (config) # iscsi enable switch (config) # exit

Enabling the iSCSI interface

You must enable the iSCSI interface before trafﬁccanﬂow on the GbE inter face. To enable an iSCSI interface:

1. Create and enable the GbE interface:

switch # conﬁgterminal switch (config) # interface gigabitethernet 2/1 switch (conf

2. Create and enable the iSCSI interface:

switch (config-if) # exit switch (con switch (config-if) # no shutdown

ig-if) # no shutdown

fig) # interface iscsi 2/1

Conﬁguring the Gigabit Ethernet interface

iSCSI uses TCP/IP for network connectivity. On each iSCSI-enabled C-Series switch, GbE interfaces provide connectivity.

NOTE:

GbE ports on any C-Series switch with the IP Storage Services Modules (IPS-4, IPS-8), Multi–protocol Services Module (14/2), or C-Series 9216i switch, should reside in a different Ethernet broadcast domain from the management Ethernet port. HP strongly recommends that you use separate standalone network hubs or switches, or separate VLANs, to conﬁgure the broadcast domains.

To conﬁgure the IP interface for subsequent use by iSCSI Initiators:

1. Enter switch conﬁguration mode:

switch # conﬁgterminal

2. Enter interface conﬁguration mode on the GbE interface:

switch (config) # interface gigabitethernet 2/1

3. Enter the IP address (20.20.20.1) and subnet mask (255.255.255.0) for the GbE interface:

switch (config-if) # ip address 20.20.20.1 255.255.255.0

4. Enable the interface:

switch (config-if) # no shutdown switch (config-if) # exit switch (config) # exit

5. Complete steps 1 through 4 for both C-Series GbE ports.

Testing connect

ivity

To test connect and the switche respective IP

ivity, issue the ping command from the host (ping the C-Series Fibre Channel switches)

s (ping the server’s two IP addresses). If host and switches are able to ping each other’s

addresses you can proceed with the ﬁnal steps.

Presenting iSCSI hosts as virtual Fibre Channel hosts

After establishing IP connectivity, you must conﬁgure the host and switches for iSCSI discovery and login.

Host side: iSCSI Initiator conﬁguration

You must specify the iSCSI targets that the host will access.

1. Double-click the Microsoft iSCSI Initiator icon to open the iSCSI Initiator Properties window

(Figure 25).

Figure 25 iSCS I Initia tor Properties window

2. On the Discovery Tab, click Add under Target Portals.

The Ad

d Target Portal window opens (Figure 26).

C-Series iSCSI 33

Figure 26 Add Target Portal window

3. Enter the IP address or DNS name of the ﬁrst conﬁgured iSCSI GbE port.

4. Click OK.

5. Repeat steps 2 through 4 using the IP address or DNS

name of the second conﬁgured iSCSI GbE port. The IP addresses are now added to the list of Target Portals

(Figure 27).

The iSCSI Initiator has connected to the iSCSI-enabled C-Series switch. The switch generates a unique virtual WWPN for the iSCSI Initiator’s IP address.

Figure 2

7BothC-Seriesswitchesaretargetportals

C-Series switch side: conﬁguring transparent-mode static mapping

The iSCSI-enabled C-Series switches have two modes of mapping IP a ddresses:

• Transparent-mode dynamic mapping

• Transparent-mode static mapping

You must enable static mapping for each iSCSI Initiator for persistent LUN mapping from the Fibre Channel storage controller.

1. Using the Cisco Device Manager, select IP > iSCSI from the menu bar.

The IP iSCSI window opens (Figure 28).

Figure 28 IP iSCSI window

2. Clear the Discovery Dynamic check box (Figure 29).

C-Series iSCSI 35

Figure 29 Discovery D ynamic check box

3. Select the N ode Address Persistent check box (Figure 30).

4. Select the N

Figure 30 Node Ad dress Persistent and Node Address System Assigned check boxes

5. Click Apply.

6. Close the IP iSCSI window.

7. Select Admin > Save Conﬁguration from the Device Manager menu bar.

8. Conﬁgure transparent-mode static mapping on both iSCSI-enabled C-Series switches.

ode Address System A ssigned check box (Figure 30).

Zoning the iSCSI Initiator and Fibre Channel storage W WPNs

The unique WWPN of the iSCSI Initiator acts as a virtual Fibre Channel host available on the Fibre Channel SAN. The WWPN is zoned with Fibre Channel storage as if it were a Fibre Channel HBA.

Creating zones

Use either the Fabric Manager or the switch CLI to create and modify SAN zones. HP recommends creating separate iSCSI zones that contain the iSCSI WWPNs and the storage WWPNs that they access. See the Cisco conﬁguration documentation for information on creating, modifying, or activating SAN zones. Figure 31 shows an iSCSI Initiator zoned with an Enterprise Virtual Array storage port.

Figure31iSCSIInitiatorzonedwithanEVAstorageport

Virtual targ

Before the i C-Series Fibre Channel switch in the iSCSI window.

1. Using the Cisco Device Manager, select IP > iSCSI from the Device Manager menu bar.

2. Click the Targets tab (Figure 32).

3. Click

eting

SCSI Initiator can lo g in to the storage controller, you must create virtual targets on each

The IP iSCSI

Figure 32 The Targets tab

Create. The Create iSCSI Targets window opens (Figure 33).

window opens (Figure 28).

4. In the Create iSCSI Targets window, enter a name for the iSCSI Name box.

5. Select the target storage port from the Port WWN list.

6. Under Initiator Access, select an Initiator. Select All if the list is empty.

7. Under Advertised Interfaces, select the por t connected to the host iSCSI Initiator.

C-Series iSCSI 37

Figure 33 Create iSCS I Targets window

8. Click Create.

9. Select Admin > Save Conﬁguration from the Device Manager menu bar.

Repeat all of the above steps for the other C-Series switch.

The iSCSI-enabled C-Series Fibre Channel switch setup is now complete.

Creating an iSCSI host

The host iSCSI Initiator must log in to the EVA storage controller before LUNs may be created.

Initial iSCSI Initiator EVA login

The iSCSI Initiator must log in to the storage controller so that the EVA storage controller can recognize the iSCSI Initiator’s WWPN. By setting the controller port as a persistent target, the iSCSI Initiator will reconnect to the storage controller after a power cycle or reboot.

1. From the Microsoft iSCSI Initiator Properties window’s Targets tab, click Refresh (Figure 34).

Thetwovirtualtargetsarelisted(oneforeachC-Seriesswitch).

Figure 3

4 Virtual targets deﬁ ned for host

2. Select a target and click Log On….

The Log On to Target window opens (Figure 35).

Figure 35 Log On to Target window

3. Select the Automatically restore this connecti on when the system boots and the Enable multi-path

check boxes to ensure that the controller port is enabled as a persistent target and is able to utilize multi-pathing (Figure 35).

4. Click OK.

5. Repeat Steps 2 through 4 for all available virtual targets.

The Targets tab should now display the status for both storage controllers as Connected (Figure 34).

C-Series iSCSI 39

Installing the E

With the targets connected to the iSCSI host, Windows discovers the EVA Command Console LUN (CCL). The New Hardware Found Wizard opens and installs the driver. This Wizard requires the following two ﬁ

• sacd.inf – EVA CCL driver

• sacd.cat – Windows Security File

These ﬁles are l HBA smar t component ﬁles are available on the HP web site.

CAUTION:

Do not install the smart component ﬁle on the host server. Only extract the ﬁles necessary to complete the EVA CCL driver

The following procedure is the same if you are downloading the ﬁles from a CD or the web site. To extract the sacd.inf and sacd.cat ﬁles:

1. Copy the HP Package ﬁle \Setups\cp005301.exe to a temporary location on the iSCSI server.

2. Double click the cp005301.exe ﬁle icon to start the HP Package Setup.

3. Click Extract.

4. Select or create a temporary folder, and then click OK.Allﬁles in the package are copied to

the speciﬁed folder.

5. Resume the Windows Found New Hardware Wizard. When prompted, specify the temporary

folder where the driver and security ﬁles reside. Follow the wizard instructions.

V A CCL Driver on the iSCSI Initiator

les:

ocated in the sm a rt component ﬁle provided with any Fibre Channel HBA. Fibre Channel

installation.

Presenting EVA LUNs to the iSCSI Initiator

After the iSCSI Initiator connects to the EVA controller, the controller recognizes the iSCSI Initiator WWPN as if it were a Fibre Channel HBA. The EVA controller can use the iSCSI Initiator WWPN to create ahostentryandpresentLUNstothehostentry.

Use Command View EVA to manage and conﬁgure the EVA. For help with Command View, please refer to the Command View EVA User Guide and related do cumentation.

1. In Command View, be sure to include both ports for proper multi-pathing support when adding

ahost(Figure 36).

Figure 36 Bo th ports presented to the host

2. After conﬁguring virtual disks and assigning them to the iSCSI Initiator return to the iSCSI host

server and select Rescan Disks in the Computer Management window (Figure 37).

Figure 37 Rescanning disks

Setting MPIO load balancing policy

You must specify how the iSCSI targets will manage and share network trafﬁc for the host. For bo th targets:

1. Open the Microsoft iSCSI Initiator Properties window.

2. Click the Targets tab.

3. Select a target and click Details.

A Target Properties window opens.

4. Click the Devices tab.

5. Select the appropriate device and click Advanced.

A Device Details window opens.

6. Select a load balance policy from the list (Figure 38).

C-Series iSCSI

Figure 38 S electing Load Bal ance Policy

7. Repeat steps 3 through 6 for the other target.

8. On the iSCSI-enabled C-Series Fibre Channel switch in the IP > iSCSI window, click the Session

rs tab to verify C-Series iSCSI sessions (Figure 39).

Initiato

Figure 39 Verifying C-Series iSCSI sessions

Conﬁguring p-Class Blade servers in an iSCSI environment

This section describes the procedures to prepare a p-Class Blade server for inclusion in an iSCSI environment. Each Blade server enclosure has a pair of network interconnects located at the left most and right most positions in the enclosure. They transmit and receive all Ethernet and Fibre Channel signals between installed Blade ser vers. The interconnect modules are b ased on either the Cisco Gigabit Ethernet Switch Module (CGESM) or the Gibabit Ethernet 2 (GbE2) standards.

Conﬁguring p-Class Blade CGESM server enclosure interconnects

This section describes a conﬁguration example using CGESM interconnects. For details on the conﬁguration or installation of the interconnects, see the speciﬁc Blade server documentation.

Setup

If you are not using DHCP, follow the setup instructions in the Cisco Gigabit Ethernet Switch Module for HP p-Class BladeSystem Software Conﬁguration Guide, to assign the CGESM an IP address. Use a web browser to access the conﬁguration management and operation features at http://10.10.10.168:80, where 80 is the default port number.. Use the web interface to disable the cross connection (XConnects) (ports 17 and 18) a nd to ensure a ll ports are in the same VLAN.

Disabling the cross connection ports

With XConnects between Interconnect A and Interconnect B, the multi-path solution may use loops established at the interconnect switching level. To avoid this, disable the XConnects. Each interconnect model has different XConnect ports. Some interconnects don’t enable these ports by default. The following procedure assumes the use of CGESM. See the interconnect documentation for more information.

1. Log in to the ﬁrst interconnect on the web switch web page at http://10.10.10.168:80.

2. Click the Conﬁguration link in the left frame of the web page.(Figure 40).

C-Series iSCSI

Figure

40 Switch web pa ge

3. Click ’Port Settings’.

4. Disable port 17 and port 18 (Figure 41).

Figure 41 Di

5. Click Submit (Figure 41).

Verifying VLAN settings

After disabling the XConnects, verify that each port used in the iSCSI setup is enabled and is par t ofthesameVLAN.Toverify:

1. From Windows Star t, select Run.

2. Enter “telnet” in the Run dialog box.

3. Log in to Interconnect A or B and run the command “show vlan” (Figure 42).

NOTE:

All ports are members of the same VLAN and are in VLAN 1 by default.

Verify the VLAN settings for Interconnects A and B.

sabling a port

Figure 42 Interconnect telnet session

Conﬁguring p-Class Blade GbE2 server enclosure interconnects

This section describes a conﬁguration example using GbE2 interconnects. For details on the conﬁguration or installation of the interconnects, see the speciﬁc Blade server documentation.

Setup

Using the setup instructions in the HP ProLiant BL p-Class GbE2 Interconnect Switch Application Guide, enable the B rowser-Based Interface (BB I ). Access the conﬁguration management and operation features of the switch through the BBI and your Web browser. Use the web interface to disable the cross connection

C-Series iSCSI

(XConnects) (ports 17 and 18) and to ensure all por ts are in the same VLAN. For information on the BBI see the HP ProLiant BL p-Class GbE2 Interconnect Switch Browser-based Interface Reference Guide.

Disabling the cross connection ports

With XConnects

between Interconnect A and Interconnect B, the multi-path solution may use loops established at the interconnect switching level. To avoid this disable the XConnects. Each interconnect model has different XConnect ports. Some interconnects don’t enable these ports by default. The following procedure uses the GbE2. See the interconnect documentation for more information.

1. Log in to the ﬁrst interconnect through the BBI.

2. Click the CON

FIGURE tab on the BBI main window (Figure 43).

Figure 43 BBI main window

3. Click the folder icon next to p-Class GbE2 Switch.

4. Navigate to the Switch Ports icon in the Switch folder (Figure 44).

Figure 44 Switch Ports icon locat ion

5. Disable Switch Port State for ports 17 and 18 (Figure 45).

Figure 45 D

6. Click Apply and then click Save.

Verifying VLAN settings

After disabling the XConnects, verify that each port used in the iSCSI setup is enabled and is par t of the sameVLAN.Todothis,clickDASHBOARD at the top of the BBI main window and navigate to Switch >> Switch Ports (Figure 46). Ports 1 to 12, 22, and 24 are operational and enabled.

NOTE:

AllportsaremembersofthesameVLAN(PVID1).

Verify the VLAN settings for Interconnects A and B.

isabling a port

C-Series iSCSI

Figure 46 Switch Ports Dashboard

Conﬁguring p-Class Blade server network settings

Depending on the model, each p-Class Blade server has two or four network interfaces. These interfaces are split between Interconnect A and Interconnect B. To ensure proper multi-path setup, one interface from each interconnect is assigned a unique static IP address. In this example, 20.20.20.230 is the IP address for one network interface, and 20.20.21.230 is the IP address for the other network interface (Figure 47).

Figure 47 Assigning a static IP to a network interface

C-Series iSCSI

Cisco MDS 9120, MDS 9124, MDS 9140, MDS 9216, MDS 9216A Configuration Manual

Specifications and Main Features

Frequently Asked Questions

User Manual