Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About...

51
Pillar Axiom iSCSI Integration Guide for Windows Platforms

Transcript of Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About...

Page 1: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Pillar Axiom

iSCSI IntegrationGuide

for Windows Platforms

Page 2: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Part Number: 4420-00097-0300Pillar Axiom release 3.32011 October

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify,license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law forinteroperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it onbehalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technicaldata delivered to U.S. Government customers are "commercial computer software" or "commercial technicaldata" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplementalregulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to therestrictions and license terms set forth in the applicable Government contract, and, to the extent applicableby the terms of the Government contract, the additional rights set forth in FAR 52.227-19, CommercialComputer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA94065.

This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications thatmay create a risk of personal injury. If you use this software or hardware in dangerous applications, then youshall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure itssafe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks oftheir respective owners.

This software or hardware and documentation may provide access to or information on content, productsand services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services. OracleCorporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to youraccess to or use of third-party content, products, or services.

2

Page 3: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Copyright © 2011, Oracle et/ou ses affiliés. Tous droits réservés.

Ce logiciel et la documentation qui l’accompagne sont protégés par les lois sur la propriété intellectuelle. Ilssont concédés sous licence et soumis à des restrictions d’utilisation et de divulgation. Sauf disposition devotre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire, diffuser, modifier,breveter, transmettre, distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement, sousquelque forme et par quelque procédé que ce soit. Par ailleurs, il est interdit de procéder à toute ingénierieinverse du logiciel, de le désassembler ou de le décompiler, excepté à des fins d’interopérabilité avec deslogiciels tiers ou tel que prescrit par la loi.

Les informations fournies dans ce document sont susceptibles de modification sans préavis. Par ailleurs,Oracle Corporation ne garantit pas qu’elles soient exemptes d’erreurs et vous invite, le cas échéant, à lui enfaire part par écrit.

Si ce logiciel, ou la documentation qui l’accompagne, est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la licence de ce logiciel ou l’utilise pour le compte du Gouvernement desEtats-Unis, la notice suivante s’applique :

U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technicaldata delivered to U.S. Government customers are "commercial computer software" or "commercial technicaldata" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplementalregulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to therestrictions and license terms set forth in the applicable Government contract, and, to the extent applicableby the terms of the Government contract, the additional rights set forth in FAR 52.227-19, CommercialComputer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City,CA 94065.

Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion desinformations. Ce logiciel ou matériel n’est pas conçu ni n’est destiné à être utilisé dans des applications àrisque, notamment dans des applications pouvant causer des dommages corporels. Si vous utilisez celogiciel ou matériel dans le cadre d’applications dangereuses, il est de votre responsabilité de prendretoutes les mesures de secours, de sauvegarde, de redondance et autres mesures nécessaires à sonutilisation dans des conditions optimales de sécurité. Oracle Corporation et ses affiliés déclinent touteresponsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce typed’applications.

Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses affiliés.Tout autre nommentionné peut correspondre à des marques appartenant à d’autres propriétaires qu’Oracle.

Ce logiciel ou matériel et la documentation qui l’accompagne peuvent fournir des informations ou des liensdonnant accès à des contenus, des produits et des services émanant de tiers. Oracle Corporation et sesaffiliés déclinent toute responsabilité ou garantie expresse quant aux contenus, produits ou servicesémanant de tiers. En aucun cas, Oracle Corporation et ses affiliés ne sauraient être tenus pourresponsables des pertes subies, des coûts occasionnés ou des dommages causés par l’accès à descontenus, produits ou services tiers, ou à leur utilisation.

3

Page 4: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Table of Contents

Chapter 1 Introduction to iSCSIAbout iSCSI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8About iSCSI Host Bus Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2 Introduction to iSCSI IntegrationiSCSI Cabling Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11About Multipathing in an iSCSI Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13iSCSI Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14iSCSI for Windows Task Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 3 Install the iSCSI SoftwareSupported Windows Versions for iSCSI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Install the Microsoft iSCSI Software Initiator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 4 Configure iSCSIAbout Pillar Axiom Slammer iSCSI Port Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 19

Configure the Slammer iSCSI Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Configure iSCSI Names and Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Discover iSCSI Slammer Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Connect iSCSI Slammer Ports to the Initiator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25About Verifying iSCSI Port Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

About iSCSI LUN Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Configure an iSCSI LUN on the Pillar Axiom System. . . . . . . . . . . . . . . . . . . . . . . . 29Map iSCSI LUN to the Windows Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Recognize iSCSI LUNs on the Windows Server. . . . . . . . . . . . . . . . . . . . . . . . . . . 31

About CHAP Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Configure Unidirectional CHAP on the Pillar Axiom System. . . . . . . . . . . . . . . . . . . 33Configure Unidirectional CHAP on the iSCSI Initiator. . . . . . . . . . . . . . . . . . . . . . . . 34Configure Bidirectional CHAP on the Pillar Axiom System. . . . . . . . . . . . . . . . . . . . 36Configure Bidirectional CHAP on the iSCSI Initiator. . . . . . . . . . . . . . . . . . . . . . . . . 37

4

Page 5: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Chapter 5 Set Up and Configure iSNSAbout iSNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

About Discovery Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39About Discovery Domain Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Install Microsoft iSNS Server 3.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41About Registering iSCSI Devices with the iSNS Server. . . . . . . . . . . . . . . . . . . . . . . . . 42

Enable iSNS Server Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Register Microsoft iSCSI Software Initiators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Display Target and Initiator Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Configure Discovery Domains and Discovery Domain Sets. . . . . . . . . . . . . . . . . . . . . . 46

Create a Discovery Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Create a Discovery Domain Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Enable a Discovery Domain Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Disable the Default Discovery Domain Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

iSNS Command Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5

Page 6: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

List of Figures

Figure 1 Select iSCSI Slammer ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 2 Modify iSCSI port settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 3 iSCSI Initiator property sheet General tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Figure 4 iSCSI Initiator property sheet Discovery tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Figure 5 Advanced settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Figure 6 Create iSCSI LUNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Figure 7 iSCSI LUN recognition on the Windows server. . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Figure 8 Configure iSCSI hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Figure 9 iSCSI Initiator property sheet Targets tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 10 Log On to Target Advanced Settings dialog box. . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 11 Modify iSCSI settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 12 iSNS server in iSCSI Initiator property sheet Discovery tab. . . . . . . . . . . . . . . . . 43

Figure 13 iSNS Server property sheet General tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Figure 14 Pillar Axiom system target details in the iSNS Server property sheet. . . . . . . . . . 45

6

Page 7: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

List of Tables

Table 1 Contacts at Pillar Data Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table 2 iSCSI related documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 3 iSCSI configuration task flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Table 4 iSNS CLI sample commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

7

Page 8: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

CHAPTER 1

Introduction to iSCSI

About iSCSIThe Internet Small Computers Standard Interface (iSCSI) is an IP-based protocolfor linking data storage devices over a network and transferring data by carryingcommands over IP networks.

The iSCSI protocol uses TCP/IP to transfer SCSI commands. This enablesstorage devices to be plugged directly into Ethernet switches and appear simplyas any other Ethernet entity on the network.

An iSCSI SAN may be composed of native iSCSI initiators (such as File Servers)and iSCSI targets (such as disk arrays and tape subsystems). Unlike the FibreChannel protocol, iSCSI requires only standard Ethernet equipment to configurea SAN fabric. From a network perspective, each iSCSI node is just another hoston the IP network.

iSCSI configurations have three components:

● iSCSI target—Any device that receives iSCSI commands, such as astorage device. In an iSCSI Pillar Axiom storage system, a Pillar AxiomSlammer is considered an iSCSI target. Each iSCSI target is identified by aunique iSCSI qualified name (IQN), and each port on the Slammer isidentified by an IP address.

● iSCSI initiator—The device that initiates iSCSI communication. In an iSCSIPillar Axiom storage system, the SAN host (Microsoft Windows) isconsidered an iSCSI initiator. An iSCSI initiator can be compared to atraditional disk controller in that it communicates with the disk drives hostedby the target.

● Network—The TCP/IP network interconnects the target and the initiator.

Note: The performance of iSCSI depends on the speed of the TCP/IPnetwork.

Communication between an iSCSI initiator and an iSCSI target occurs over oneor more TCP connections. The TCP connections carry control messages, SCSIcommands, parameters, and data, all of which are encapsulated in iSCSIProtocol Data Units (PDUs). An iSCSI session is comparable to a SCSI

Chapter 1 Introduction to iSCSI

About iSCSI 8

Page 9: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

I_T nexus and is established to identify all of the TCP connections between aninitiator and a target that belong to the same I_T nexus.

Refer to Request for Comments (RFC) 3720 (http://www.rfc-archive.org/getrfc.php?rfc=4171) for complete iSCSI information.

Chapter 1 Introduction to iSCSI

About iSCSI 9

Page 10: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

About iSCSI Host Bus AdaptersiSCSI host bus adapters (HBAs) are dedicated network interface controllers thatdo onboard iSCSI processing (called a TCP Offload Engine, or TOE). iSCSIHBAs are usually abstracted by the operating system to appear as a SCSIcontroller.

When the host is operating under heavy loads, applications should benefit fromthe use of a dedicated iSCSI HBA.

Chapter 1 Introduction to iSCSI

About iSCSI Host Bus Adapters 10

Page 11: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

CHAPTER 2

Introduction to iSCSI Integration

iSCSI Cabling RequirementsThe iSCSI cabling requirements depend on the Ethernet and TCP/IP networkconfiguration. At the basic level, however, the Pillar Axiom storage system andthe Windows host must have dedicated ports assigned to the network.

1 From the Pillar Axiom storage system, connect the following iSCSI ports tothe network:

● Control unit 0 (CU0): port 0 and port 1

● Control unit 1 (CU1): port 0 and port 1

Note: The external cabling must support the speed of the connection. Forexample, a 100 Mb connection requires 100BaseT components, whereas a1 Gb connection requires 1000BaseT components.

2 Repeat Step 1 for each additional iSCSI enabled Slammer.

3 From the Windows server, connect the network ports assigned for iSCSItraffic to the network.

Chapter 2 Introduction to iSCSI Integration

iSCSI Cabling Requirements 11

Page 12: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

About Multipathing in an iSCSI ConfigurationUse the Pillar Axiom Path Manager (APM) for Windows software to configuremultipathing in your iSCSI environment.

Setting up multiple paths in an iSCSI environment involves several steps, whichare documented in the Pillar Axiom Path Manager Installation Guide and ReleaseNotes for Windows.

Important! If you use APM, you must use the multipath I/O (MPIO) that comeswith the APM software to configure multipathing.

If you do not use APM, you must create a single connection to each Slammer,and you should not select the Enable multi-path check box in the Microsoft iSCSISoftware Initiator Log On to Target dialog box.

Note: There are cases when it might be necessary to select the Enable multi-pathcheck box even if you do not have the APM software installed. For example, ifyou want to connect with both ports of a dual port NIC or dual port iSCSI HBA,you must click the Enable multi-path feature in the Microsoft iSCSI Initiator in orderto log in, even if you are not using the APM software for multi-pathing. Log in to asingle control unit (CU) iSCSI port and constrain each LUN using LUN masking,so that only a single path exists to each LUN. In this way, you are able to useboth ports (each to a separate LUN) to increase performance.

Chapter 2 Introduction to iSCSI Integration

About Multipathing in an iSCSI Configuration 12

Page 13: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Contact Information

Table 1 Contacts at Pillar Data Systems

For help with... Contact...

Error messages,usage questions, andother support issues

US and Canada: 877-4PILLAR (1-877-474-5527)

Europe: +800 PILLAR FS (+800 74 44 27 37)

Asia Pacific: +1-408-518-4515

South Africa: +0 800 980 400

Have your system serial number ready.

[email protected]

Customer support portal (https://support.pillardata.com/login.do)

Sales and generalcontact information

Company contacts (http://www.pillardata.com/company/contact)

Documentationimprovements andresources

[email protected]

Technical documents (http://www.pillardata.com/techdocs) (Log in with your username and password, andselect Documents.)

Chapter 2 Introduction to iSCSI Integration

Contact Information 13

Page 14: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

iSCSI Related DocumentationTechnical documentation (including installation, service, cabling, integration, andadministration guides) for Oracle’s Pillar Axiom 600 storage system is availablefrom several sources. The information in this document consists of Pillar Axiom-specific instructions that do not exist elsewhere. There may be cases where theinformation exists elsewhere but is changed slightly for an iSCSI configuration. Inthese cases, procedures are included for the user's convenience.

Table 2 iSCSI related documentation

Document Location of document

Pillar Axiom Path ManagerInstallation Guide and ReleaseNotes for Windows

From the Pillar web site: http://www.pillardata.com/techdocs/

Pillar Axiom Administrator’s Guide From the Pillar Axiom Storage ServicesManager:

1 Select Support > TechnicalDocumentation.

2 Select the Administrator’s Guide.

Microsoft iSCSI Software Initiator 2.x Users Guide Microsoft iSNS Server Users Guide

Microsoft Download Center (http://www.microsoft.com/downloads/)

Windows Server 2003 Deploying IPSANs with the Microsoft iSCSIArchitecture

Microsoft Download Center (http://download.microsoft.com/downloads/)

Chapter 2 Introduction to iSCSI Integration

iSCSI Related Documentation 14

Page 15: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

iSCSI for Windows Task MapFollow these steps in this order to configure an iSCSI environment on the PillarAxiom storage system and the Microsoft iSCSI Software Initiator.

Table 3 iSCSI configuration task flow

Task

Configure the Slammer iSCSI Ports on page 19.

Install the Microsoft iSCSI Software Initiator on page 17.

Download, install, and use the Pillar Axiom Path Manager (APM) software. Fordetails, see the Pillar Axiom Path Manager Installation Guide and Release Notes forWindows.

Configure iSCSI Names and Authentication on page 21.

Discover iSCSI Slammer Ports on page 23.

Connect iSCSI Slammer Ports to the Initiator on page 25.

About Verifying iSCSI Port Connections on page 27.

Configure an iSCSI LUN on the Pillar Axiom System on page 29.

Map iSCSI LUN to the Windows Server on page 30.

Recognize iSCSI LUNs on the Windows Server on page 31.

Optional:

Configure Unidirectional CHAP on the Pillar Axiom System on page 33 or Configure Bidirectional CHAP on the Pillar Axiom System on page 36.

Configure Unidirectional CHAP on the iSCSI Initiator on page 34 or ConfigureBidirectional CHAP on the iSCSI Initiator on page 37.

Chapter 2 Introduction to iSCSI Integration

iSCSI for Windows Task Map 15

Page 16: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

CHAPTER 3

Install the iSCSI Software

Supported Windows Versions for iSCSIBefore you install the Microsoft iSCSI Initiator, make sure that your Windowsversion is supported and has the latest service packs.

iSCSI is supported on all versions of Windows that support the Microsoft iSCSISoftware Initiator. Refer to the Microsoft Download page (http://www.microsoft.com/downloads/) for a complete listing.

Note: The Microsoft iSCSI Software Initiator is included in Windows Server 2008distributions. If you are using an earlier version of Windows, you will need todownload the Microsoft iSCSI Initiator from the Microsoft download page.

Chapter 3 Install the iSCSI Software

Supported Windows Versions for iSCSI 16

Page 17: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Install the Microsoft iSCSI Software InitiatorBefore you can configure your SAN for iSCSI protocol, you must install theMicrosoft iSCSI Software Initiator package. The Microsoft iSCSI Software Initiatoris included in Windows Server 2008, so Windows 2008 users do not need todownload and install the package.

Install the Microsoft iSCSI Software Initiator package on a Windows host that hasnetwork access to your Pillar Axiom iSCSI ports.

The iSCSI Software Initiator includes a property sheet graphical user interface(GUI) and an iscsicli command line interface (CLI). For more informationabout the iSCSI CLI, refer to the Microsoft iSCSI Software Initiator 2.x UsersGuide or, at a Windows command prompt, enter:

iscsicli help

1 From the Microsoft Download page (http://www.microsoft.com/downloads/),search for iSCSI Initiator and click the link that corresponds to the mostrecent version of the iSCSI Software Initiator.

2 Scroll to the Files in this Download section and choose one of:

● amd64fre.exe

● ia64fre.exe

● x86fre.exe

3 From the Microsoft Download page, you can also download the ReleaseNotes and the Microsoft iSCSI Software Initiator User's Guide (optional).

4 Click Download.

5 From the File Download - Security dialog box, click Run.

6 Follow the prompts on the Software Update Installation Wizard, acceptingthe defaults.

Make sure that:

● Initiator Service and Software Initiator are selected.

● Microsoft MPIO Multipathing Support for iSCSI is not selected.

Note: The Pillar Axiom Path Manager (APM) for Windows softwareprovides the multi-path support for your iSCSI configuration.

7 Agree to the License Agreement.

Chapter 3 Install the iSCSI Software

Install the Microsoft iSCSI Software Initiator 17

Page 18: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Result:The setup checks for your system's current setup configuration.

8 Click Finish.

Result:The Microsoft iSCSI Initiator icon is displayed on your desktop.

Chapter 3 Install the iSCSI Software

Install the Microsoft iSCSI Software Initiator 18

Page 19: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

CHAPTER 4

Configure iSCSI

About Pillar Axiom Slammer iSCSI Port ConfigurationUse the Pillar Axiom Storage Services Manager to configure the iSCSI settingson the Slammer ports. Use the Microsoft iSCSI Software Initiator to configureiSCSI port names and authentication, to discover and connect the configurediSCSI Slammer ports, and to verify that the ports are operational.

Configure the Slammer iSCSI PortsConfigure the Slammer iSCSI ports for network access using the Pillar AxiomStorage Services Manager.

The following steps provide a simplified example of how to make a directconnection between the iSCSI Slammer ports and the iSCSI initiator ports. Theexample uses manual IP assignment rather than Dynamic Host ConfigurationProtocol (DHCP), and this configuration does not use the Challenge HandshakeAuthentication Protocol (CHAP). Both DHCP and CHAP are optional.

1 Log in to the Pillar Axiom Storage Services Manager GUI.

2 Select Storage > SAN > Slammer Ports.

Chapter 4 Configure iSCSI

About Pillar Axiom Slammer iSCSI Port Configuration 19

Page 20: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Figure 1 Select iSCSI Slammer ports

3 Select a Slammer in the Slammer Ports table, and choose Modify iSCSI PortSettings from the Actions drop-down box.

Figure 2 Modify iSCSI port settings

4 Select the iSCSI Slammer port that you want to modify from the iSCSI PortSettings table, and click Modify.

Chapter 4 Configure iSCSI

About Pillar Axiom Slammer iSCSI Port Configuration 20

Page 21: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

5 Accept the default values for TCP Port Number.

6 Accept the default value for MTU (bytes).

Note: The frame size (the maximum transmission unit, or MTU) does notinclude the Ethernet header portion of the packet. If the network supportsextended Ethernet (jumbo) frames, enter an integer greater than 1500 andless than or equal to 9000. Make sure that the Pillar Axiom MTU valuematches the network MTU value. If these two values do not match, you mayexperience I/O interruptions when the client machines attempt to processpackets that are too large.

Important! Each switch in the path must be configured with this MTU value.

7 Select Manual, and assign IP addresses to each of the Slammer ports.

Tip: Although DHCP is supported, we recommend you assign the IPaddresses manually to avoid problems that could occur on the DHCP server.

8 After you configure each Slammer port, select Update.

9 When you have configured all ports, click OK.

Go on to Discover iSCSI Slammer Ports on page 23.

Configure iSCSI Names and AuthenticationYou can change the iSCSI initiator node name and assign a secret key forChallenge Handshake Authentication Protocol (CHAP) in the General tab of theMicrosoft iSCSI Software Initiator property sheet.

1 Double-click the Microsoft iSCSI Initiator desktop icon to open the iSCSIInitiator property sheet.

Chapter 4 Configure iSCSI

About Pillar Axiom Slammer iSCSI Port Configuration 21

Page 22: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Result:

Figure 3 iSCSI Initiator property sheet General tab

2 Click Change to change the iSCSI Initiator Node Name from the defaultiSCSI Qualified Name (IQN) device name displayed in the General tab.

3 Enter a new name in the Initiator Node Name Change dialog box.

Because the iSCSI device name must be globally unique, we recommendthat you not change the default iSCSI device name.

Important! Changing the Initiator Node Name may affect iSCSI SoftwareInitiator access to iSCSI targets.

4 Click OK

5 If you will be using bidirectional CHAP authentication, click Secret and entera CHAP secret for the Pillar Axiom target in the CHAP Secret Setup dialogbox.

CHAP secrets must be between 12 and 16 characters long.

Important! The CHAP secret entered here must match the CHAP secretentered for the Pillar Axiom target when bi-directional (mutual) CHAPauthentication is enabled in the Pillar Axiom Storage Services Manager.

The General tab also contains a Tunnel button used to configure Internet ProtocolSecurity (IPSec). Pillar Axiom iSCSI ports do not support IPSec, so you shouldnot configure IPSec in the iSCSI Software Initiator.

Chapter 4 Configure iSCSI

About Pillar Axiom Slammer iSCSI Port Configuration 22

Page 23: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Discover iSCSI Slammer PortsYou can use the iSCSI Initiator to discover the iSCSI Slammer port IP addresses,which have been configured on the Pillar Axiom storage system. Alternatively,you can add an iSNS server to the iSNS Servers list.

Before you can use the Microsoft iSCSI Software Initiator to discover theSlammer iSCSI ports, you must have already configured the iSCSI Slammerports using the Pillar Axiom Storage Services Manager, and you must have theiSCSI Software Initiator installed.

1 Double-click the Microsoft iSCSI Initiator desktop icon to open the iSCSIInitiator property sheet.

2 Click the Discovery tab, as shown in Figure 4: iSCSI Initiator property sheetDiscovery tab below.

The Target Portals list will be empty if no targets have been discovered yet.

Result:

Figure 4 iSCSI Initiator property sheet Discovery tab

3 Click Add under Target Portals.

Result:The Add Target Portal dialog box displays.

Chapter 4 Configure iSCSI

About Pillar Axiom Slammer iSCSI Port Configuration 23

Page 24: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

4 Enter the target IP address and TCP port number (default = 3260) of one ofthe Slammer iSCSI ports that you configured on the Pillar Axiom storagesystem.

5 Click OK.

Note: You only need to add one Target Portal. The iSCSI Software Initiatorwill discover the additional ports.

Note: The iSNS server, which automatically discovers available targets onthe network, eliminates the need to manually enter the target addresses.See About iSNS on page 39 for information.

Result:The iSCSI Software Initiator logs in to the Pillar Axiom iSCSI port to createan iSCSI discovery session. The discovery session obtains the target iSCSIdevice name as well as the IP address and TCP port number of each targetport.

● If the discovery session fails, one of the following error messagesdisplays. Take the appropriate action to correct the error.

ConnectionFailed

TCP connection to the specified IP address andTCP port number failed. This error may be theresult of another machine that is not an iSCSItarget being assigned the same IP address.Debug the connection failure using the pingcommand from a DOS command line. The hostmust be on the same subnet for the pingcommand to succeed.

AuthorizationFailure

The iSCSI Software Initiator is not authorized tolog in to the specified port (access control isenabled). Disable access control.

AuthenticationFailure

The iSCSI Software Initiator did not attempt toperform CHAP authentication, or CHAPauthentication failed. See About CHAPImplementation on page 33.

● If the discovery session succeeds, the Slammer iSCSI port informationdisplays in the Target Portals list.

Go on to Connect iSCSI Slammer Ports to the Initiator.

Chapter 4 Configure iSCSI

About Pillar Axiom Slammer iSCSI Port Configuration 24

Page 25: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Connect iSCSI Slammer Ports to the InitiatorUse the Microsoft iSCSI Software Initiator to manually create sessions thatconnect iSCSI Slammer ports to a source IP.

Before you perform this procedure, make sure the Pillar Axiom Path Manager(APM) software is installed and the iSCSI Slammer ports have been discoveredby the iSCSI Initiator. See About Multipathing in an iSCSI Configuration on page12 and Discover iSCSI Slammer Ports on page 23. If the iSCSI Initiatorsuccessfully discovered the iSCSI Slammer ports, you will see the Target namelisted in the following form:

iqn.2002-03.com.pillardata.axiom.ssn.xxxxxxxx

where xxxxxxxx is a unique identifier containing the Pillar Axiom storage systemserial number.

1 From the Pillar Axiom Storage Services Manager, note the IP addresses ofthe iSCSI Slammer ports you will connect to the iSCSI Software Initiator.

Example:For example, there will be a total of four ports if each Slammer has twocontrol units (CUs) and each CU has two iSCSI ports.

2 Click the Targets tab in the iSCSI Initiator Properties property sheet.

If you have just completed a discovery session, the discovered targetdisplays in the Targets list.

3 Select a target and click Log On.

Result:The Log On to Target dialog box displays the iSCSI device name of thePillar Axiom storage system target to which you are about to log in.

4 Select the following options:

● Automatically restore this connection when the system boots to make thesession persistent (restored across system reboots).

● Enable multi-path to enable you to create more than one session for multi-path redundancy using the Pillar Axiom Path Manager (APM) software.

5 From the Log On to Target dialog box, click Advanced to display theAdvanced Settings dialog box.

Chapter 4 Configure iSCSI

About Pillar Axiom Slammer iSCSI Port Configuration 25

Page 26: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Figure 5 Advanced settings

6 From the Local adapter list, select Microsoft iSCSI Intitator.

If an iSCSI HBA is installed in the Windows server, additional selectionsdisplay in the list.

7 Select a Source IP and the Target Portal:

● Source IP - Select the source IP you will use to create your firstsession from the drop-down list.Note: In the example shown in Figure 5: Advanced settings, there aretwo host iSCSI ports (source IPs) that will connect to four SlammeriSCSI ports.

● Target Portal - Select the first target port that you will connect to theselected source IP.Note: The IP address and TCP port number of each Slammer iSCSIport is discovered during the discovery session. The Slammer iSCSIport information can also be discovered from an iSNS server (see Enable iSNS Server Registration on page 42).Important! You cannot multi-select the Target Portal (iSCSI portaddresses). You must connect each port individually.

The Source IP and Target Portal represent the two ends of the connectionyou are creating. Each connection forms a path to the LUNs.

Chapter 4 Configure iSCSI

About Pillar Axiom Slammer iSCSI Port Configuration 26

Page 27: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

8 To enable header or data digests, select the appropriate check boxes in theCRC/Checksum section.

9 To enable iSCSI initiator (unidirectional) authentication, select CHAP logoninformation.

See Configure Unidirectional CHAP on the iSCSI Initiator on page 34 forconfiguration instructions.

10 To enable target as well as initiator (bidirectional) authentication, selectPerform mutual authentication.

See Configure Bidirectional CHAP on the Pillar Axiom System on page 36and Configure Bidirectional CHAP on the iSCSI Initiator on page 37 forconfiguration instructions.

11 Click OK to close the Advanced Settings dialog box and return to the TargetLog On dialog box.

12 Click OK to create the session.Result:The Targets tab should display Connected status for the connection.

13 Repeat Steps 3 through 12 to connect each discovered target.

About Verifying iSCSI Port ConnectionsAfter you discover the iSCSI Slammer ports and connect them to the source IPusing the Microsoft iSCSI Software Initiator, you can use the iSCSI SoftwareInitiator, the iSCSI command line interface (CLI), or the Pillar Axiom StorageServices Manager to check the connection status.

Verify Connections with the Microsoft iSCSI Software Initiator

1 Select the target name in the Target tab of the iSCSI Initiator property sheet.

2 Click Details.Result:The Target Properties dialog box displays the current sessions for the target.

3 Click Connections.Result:The Session Connections dialog box displays TCP connection details forthe iSCSI session. iSCSI sessions can have multiple TCP connections, but

Chapter 4 Configure iSCSI

About Pillar Axiom Slammer iSCSI Port Configuration 27

Page 28: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

the Pillar Axiom system supports only one TCP connection for each iSCSIsession.

4 Verify that the selected target has a Connected status.

5 Click OK.

Verify Connections with the iSCSI CLIYou can also use the iSCSI command line interface to verify iSCSI port connections.

1 At a Windows command prompt, enter iscsicli sessionlist.

Result:The output of this command provides a list of active sessions and theirconnections for all initiators.

2 Verify that a connection exists for each iSCSI port.

Verify Connections with the Pillar Axiom Storage Services Manager

1 Select Storage > SAN > Hosts.

2 Verify the following on the selected host:

● The Pillar Axiom Path Manager is communicating.

● The Host Port Status is Connected.

Tip: If the Pillar Axiom Storage Services Manager and the output of theiscsicli sessionlist command indicate that the iSCSI port is notconnected, you can check basic network connectivity with the standardping utility, using hosts on the local subnet of the Pillar Axiom iSCSIinterface. The Pillar Axiom pdscli Command Line Interface (CLI) provides arequest, PerformSANiSCSIPing, to ping for iSCSI interfaces.

To ping a host port on the local subnet of the Pillar Axiom iSCSI interface,or to ping the IP address of the gateway on the local subnet of the PillarAxiom iSCSI interface, use the pdscli PerformSANiSCSIPing request.PerformSANiSCSIPing sends a standard ICMP Echo Request (ping) fromthe iSCSI port of the Pillar Axiom storage system to check basic networkconnectivity. Refer to the Pillar Axiom CLI Reference Guide for instructions.

Chapter 4 Configure iSCSI

About Pillar Axiom Slammer iSCSI Port Configuration 28

Page 29: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

About iSCSI LUN ConfigurationWhen you configure an iSCSI LUN on the Pillar Axiom storage system, youselect the iSCSI protocol and determine which SAN host can have access to theLUN. When the configuration is complete, you can use the Windows DiskManagement utility to verify that the Windows server recognizes the iSCSI LUNsthat were mapped to it.

Configure an iSCSI LUN on the Pillar Axiom SystemWhen you configure a LUN using the Pillar Axiom Storage Services Manager,you assign it to a SAN Slammer, select which hosts have access to the LUN, andselect whether iSCSI or Fibre Channel protocol will be used to access the LUN.

1 In the Pillar Axiom Storage Services Manager, select Storage > SAN > LUNs.

2 Choose Create LUN from the Actions drop-down box.

Result:

Figure 6 Create iSCSI LUNs

3 Enter a LUN name (such as lun0).

4 From the Create LUN in list, select a volume group in which to create the LUN.

5 Assign the LUN to a SAN Slammer. Choose one of:

Chapter 4 Configure iSCSI

About iSCSI LUN Configuration 29

Page 30: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

● Auto-assign SAN Slammer to a SAN Slammer. This allows the Pilot tomove resources to the other control unit (CU) in the event of a failover,and maximizes performance by balancing the system load withexisting LUNs and filesystems.Tip: If you select this option, you can set up port masking and portmapping after you create the LUN. Select the LUN and choose ModifyLUN from the Actions drop-down box.

● Assign LUN to Slammer. Use this option when you want to access thedata from a particular port. This is known as port masking.

6 Select the Only selected hosts method to access this LUN.

Note: You will use this option to map the LUN to one or more specific SANhosts.

7 Select iSCSI as the protocol to be used to access the LUN.

8 Select the Quality of Service (QoS) tab.

9 Enter the initial size of the LUN in gigabytes.

10 Fill out the rest of the QoS fields as needed. See the Pillar AxiomAdministrator’s Guide.

11 Click OK.

Go on to Map iSCSI LUN to the Windows Server.

Map iSCSI LUN to the Windows ServerUse LUN mapping to create and modify the LUN-to-host mapping settings.

To map an iSCSI LUN to the host, you must first enable LUN mapping and selectOnly selected hosts. See Configure an iSCSI LUN on the Pillar Axiom System onpage 29.

1 In the Pillar Axiom Storage Services Manager, select Storage > SAN > LUNs.

2 Select the LUN you will map from the content pane.

3 Select Modify LUN from the Actions drop-down box.

4 Click the Mapping tab on the Modify LUN page.

5 From the Host list, select the SAN host you want to allow to access theselected LUN.

Chapter 4 Configure iSCSI

About iSCSI LUN Configuration 30

Page 31: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

This list includes recognized hosts as well as unassociated iSCSI nameswhich are hosts on the SAN network that are not using the Pillar AxiomPath Manager.

6 Select the number to assign to the LUN from the Available LUN Number drop-down list.

7 Select the ports on the Slammer control units (CUs) that you want to maskso that the LUN cannot be accessed from the specified ports (optional).

8 Click Create Map.

9 Click OK.

Recognize iSCSI LUNs on the Windows ServerDisk Management is a Windows system utility for managing disk drives and thepartitions or volumes they contain. Use the Windows Disk Management utility todetermine if the Windows server recognizes the iSCSI LUNs that were mappedto the Windows server.

1 Open the Computer Management console by right-clicking the My Computerdesktop icon and selecting Manage.

2 Click Storage > Disk Management in the left navigation pane.

3 Select Action > Rescan Disks.

4 Verify that the Windows server recognizes the iSCSI LUNs.

Result:Each LUN can now be initialized and mapped to a drive letter, as shown in Figure 7: iSCSI LUN recognition on the Windows server.

Chapter 4 Configure iSCSI

About iSCSI LUN Configuration 31

Page 32: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Figure 7 iSCSI LUN recognition on the Windows server

Chapter 4 Configure iSCSI

About iSCSI LUN Configuration 32

Page 33: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

About CHAP ImplementationiSCSI supports unidirectional and bidirectional Challenge-HandshakeAuthentication Protocol (CHAP) authentication, which provides authenticationbetween the target and the initiator.

Setting up authentication for the iSCSI devices is optional.

In a secure environment, authentication is not required because only trustedinitiators can access the targets. In a less secure environment, the target cannotdetermine if a connection request is truly from a given host, but the target canauthenticate an initiator by using CHAP.

CHAP authentication uses the notion of a challenge and response, which meansthat the target challenges the initiator to prove its identity. For the challenge andresponse method to work, the target must know the initiator's secret key, and theinitiator must be set up to respond to a challenge.

Configure Unidirectional CHAP on the Pillar Axiom SystemUnidirectional authentication enables the target to authenticate the identity of theinitiator.

Always begin CHAP configuration on the Pillar Axiom storage system. After youhave configured the iSCSI hosts in the Pillar Axiom storage system, you canconfigure the Microsoft iSCSI Software Initiator on the host side.

1 In the Pillar Axiom Storage Services Manager, select Storage > SAN > Hosts.

2 Select the host name and choose Configure iSCSI Hosts from the Actions drop-down box.

Chapter 4 Configure iSCSI

About CHAP Implementation 33

Page 34: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Result:

Figure 8 Configure iSCSI hosts

3 Select Enable Authentication.

4 Type the CHAP name.Example:iqn.1991-05.com.microsoft:myhost.

Note: The CHAP name is the iSCSI Initiator qualified name (IQN) displayedin the General tab of the iSCSI Initiator Properties sheet.

5 Enter a CHAP secret, which must be between 12 and 16 characters.Example:myH0sts3cret.

6 Retype the CHAP secret, and click OK.

Go on to Configure Unidirectional CHAP on the iSCSI Initiator.

Configure Unidirectional CHAP on the iSCSI InitiatorUse this procedure to configure the Microsoft iSCSI Software Initiator forunidirectional CHAP on the host side.

Configure CHAP for the iSCSI hosts in the Pillar Axiom storage system beforeyou configure CHAP in the iSCSI Software Initiator.

1 Select the target in the Targets tab of the iSCSI Initiator Properties sheet,and click Log On to access the storage devices for that target.

Chapter 4 Configure iSCSI

About CHAP Implementation 34

Page 35: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Figure 9 iSCSI Initiator property sheet Targets tab

2 Click Advanced in the Log On to Target dialog box.

Result:The Advanced Settings dialog box displays.

Figure 10 Log On to Target Advanced Settings dialog box

3 If not already configured, connect the targets from the Pillar Axiom storagesystem to the iSCSI Initiator by selecting the following:

Chapter 4 Configure iSCSI

About CHAP Implementation 35

Page 36: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

● Local adapter

● Source IP

● Target PortalSee Connect iSCSI Slammer Ports to the Initiator on page 25 for details.

4 Select Data digest or Header digest if desired. (Optional)

5 Select CHAP logon information.

Result:The User Name is automatically populated with the iSCSI Initiator qualifiedname (IQN).

6 Enter the Initiator CHAP secret you configured in Configure UnidirectionalCHAP on the Pillar Axiom System on page 33.

7 Clear the Perform mutual authentication check box if it is selected.

8 Click OK.

Configure Bidirectional CHAP on the Pillar Axiom SystemBidirectional CHAP adds a second level of security by providing a means for theinitiator to authenticate the identity of the target. Always begin CHAPconfiguration on the Pillar Axiom storage system.

1 Follow the steps for configuring unidirectional CHAP from the Pillar AxiomStorage Services Manager in Configure Unidirectional CHAP on the PillarAxiom System on page 33.

2 In the Pillar Axiom Storage Services Manager, select System > Global Settings> iSCSI.

3 Choose Modify iSCSI Settings from the Actions drop-down box.

Chapter 4 Configure iSCSI

About CHAP Implementation 36

Page 37: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Result:

Figure 11 Modify iSCSI settings

4 Select the Enable Header Digest or Enable Data Digest options if desired. (Optional)

5 Select Enable Bi-Directional CHAP.

6 Enter the Pillar Axiom CHAP secret, which must be between 12 and 16characters.

Example:t4rgetS3cret

7 Retype the CHAP secret, and click OK.

Go on to Configure Bidirectional CHAP on the iSCSI Initiator.

Configure Bidirectional CHAP on the iSCSI InitiatorUse this procedure to configure the Microsoft iSCSI Software Initiator forbidirectional CHAP on the host side.

Prerequisite:

Always begin bidirectional CHAP configuration on the Pillar Axiom storage system (see Configure Bidirectional CHAP on the Pillar Axiom System on page 36), and then complete theconfiguration using the Microsoft iSCSI Software Initiator.

Chapter 4 Configure iSCSI

About CHAP Implementation 37

Page 38: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

1 In the iSCSI Software Initiator General tab, enter the CHAP secret that youconfigured in Configure Bidirectional CHAP on the Pillar Axiom System onpage 36 and click OK.

In this example, the CHAP secret is targetsecret. See Configure iSCSINames and Authentication on page 21 for instructions for configuring theCHAP secret on the General tab.

2 Follow Steps 1-6 in Configure Unidirectional CHAP on the iSCSI Initiator onpage 34 to configure CHAP authentication in the Advanced Settings of theMicrosoft iSCSI Software Initiator Log On to Target dialog box.

3 Select the Perform mutual authentication option.

4 Click OK.

Chapter 4 Configure iSCSI

About CHAP Implementation 38

Page 39: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

CHAPTER 5

Set Up and Configure iSNS

About iSNSThe Internet Storage Name Service (iSNS) provides an alternative to iSCSISoftware Initiator discovery by establishing an iSNS server on your iSCSInetwork that automatically discovers iSCSI targets and initiators.

iSNS facilitates automated discovery, management, and configuration of iSCSIdevices on a TCP/IP network. iSNS provides intelligent storage discovery andmanagement services comparable to those found in Fibre Channel networks,allowing a commodity IP network to function in a capacity similar to that of astorage area network.

The iSNS feature expects all Pillar Axiom iSCSI ports to have access to thesame primary iSNS server. This rule is necessary so that all iSCSI ports canexpect the same result when querying the iSNS database for the set of initiatorsthat are members of the Pillar Axiom Discovery Domain Set.

If a Pillar Axiom iSCSI port never has access or loses access to the iSNS server,the Pillar Axiom storage system reports iSNS error events in the Pillar AxiomStorage Services Manager but continues to operate normally. At least one PillarAxiom iSCSI port must have access to the iSNS server during system startup foriSNS-based initiator access control to function correctly; otherwise, all iSCSIlogins are rejected.

Refer to Request for Comments (RFC) 4171 (http://www.rfc-archive.org/getrfc.php?rfc=4171) for complete iSNS information.

About Discovery DomainsDiscovery domains help your Internet Storage Name Service (iSNS) server keeptrack of your iSCSI initiators and targets.

Discovery domains are a security and management mechanism used toadminister access and connectivity to storage devices. A query by an iSNS clientonly returns information about objects with which it shares at least one activediscovery domain.

Chapter 5 Set Up and Configure iSNS

About iSNS 39

Page 40: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

A discovery domain is considered active if it is a member of at least one activediscovery domain set. Discovery domains that are not members of at least oneenabled discovery domain set are considered disabled. A storage node, or iSCSItarget, can be a member of one or more discovery domains. An enableddiscovery domain establishes connectivity among the storage nodes in thatdiscovery domain.

About Discovery Domain SetsA discovery domain set is a grouping of one or more discovery domains.

The discovery domain set is a container object for discovery domains. Discoverydomain sets may contain one or more discovery domains. Similarly, eachdiscovery domain can be a member of one or more discovery domain sets.Discovery domain sets are a mechanism to store coordinated sets of discoverydomain mappings in the Internet Storage Name Service (iSNS) server. Activediscovery domains are members of at least one active discovery domain set.Multiple discovery domain sets may be considered active at the same time.

Chapter 5 Set Up and Configure iSNS

About iSNS 40

Page 41: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Install Microsoft iSNS Server 3.0Install the Microsoft iSNS Server v3.0 package on a Windows server that isaccessible to all of your iSCSI initiators and targets.

Note: iSNS Server is included in Windows Server 2008 distributions. If you areusing an earlier version of Windows, you will need to download and install iSNSServer.

Refer to the Microsoft Download page (http://www.microsoft.com/downloads/) fordownload and installation instructions.

Two iSNS installation files are available from the Microsoft download page.Download the one that is appropriate for your system. Choose one of:

● iSNS-Server-3.0-ia64fre.mis - for Itanium 64-bit systems only.

● iSNS-Server-3.0-x86fre.msi - for non-Itanium 64-bit systems, and all32-bit x86 systems.

Chapter 5 Set Up and Configure iSNS

Install Microsoft iSNS Server 3.0 41

Page 42: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

About Registering iSCSI Devices with the iSNS ServerInitiators and targets must register with the Internet Storage Name Service(iSNS) server so they can be managed with discovery domains.

Enable iSNS Server RegistrationPillar Axiom iSCSI targets are registered by enabling iSNS Server Registration inthe Pillar Axiom Storage Services Manager and specifying either DHCPdiscovery of the Internet Storage Name Service (iSNS) server IP address or astatic iSNS server IP address.

1 In the Pillar Axiom Storage Services Manager, select System > Global Settings> iSCSI.

2 Select Modify iSCSI Settings from the Actions drop-down box.

3 Select Enable iSNS Server Registration.

Result:The iSNS Access Control and Server Discovery radio buttons display.

4 Select iSNS Access Control. (Optional)

5 Choose DHCP or Static for the Server Discovery method.

For DHCP discovery of the iSNS server IP address, you must use aMicrosoft DHCP server that has been configured by the Microsoft iSNSServer installer to return the server IP address using DHCP option 43 (vendor-specific) or DHCP option 83 (iSNS).

6 Click OK.

Go on to Register Microsoft iSCSI Software Initiators

Register Microsoft iSCSI Software InitiatorsRegister Microsoft iSCSI Software Initiators by adding the IP address of theInternet Storage Name Service (iSNS) server in the Discovery tab of the iSCSIInitiator Properties sheet.

1 Double-click the Microsoft iSCSI Initiator desktop icon to open the iSCSIInitiator property sheet.

Chapter 5 Set Up and Configure iSNS

About Registering iSCSI Devices with the iSNS Server 42

Page 43: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

2 Click the iSCSI Initiator Properties Discovery tab.

3 Click Add under iSNS Servers.

Result:The Add iSNS Server dialog box displays.

4 Enter the IP address of your iSNS server and click OK.

This registers the iSCSI initiator with the iSNS server.

Result:If registration is successful, the iSNS server IP address displays in theiSCSI Initiator Properties Discovery tab.

Figure 12 iSNS server in iSCSI Initiator property sheet Discovery tab

Chapter 5 Set Up and Configure iSNS

About Registering iSCSI Devices with the iSNS Server 43

Page 44: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Display Target and Initiator DetailsUse the iSNS Server control panel to display general and detailed informationabout the Pillar Axiom targets and iSCSI initiators registered with the InternetStorage Name Service (iSNS) server.

Open the iSNS Server control panel on the Windows server that is the primaryiSNS server.

1 Click the Microsoft iSNS Server desktop icon to open the iSNS Server controlpanel.

Result:The General tab of the iSNS Server property sheet displays all iSCSIinitiators and targets that are currently registered with the iSNS server.

Figure 13 iSNS Server property sheet General tab

2 Select the Pillar Axiom target and click Details.

Check the Pillar Axiom target registration details (iSCSI name, alias, entity,and portals) as well as the discovery domains of which the target is amember. By default, all registered initiators and targets are members of thedefault discovery domain (Default DD).

Chapter 5 Set Up and Configure iSNS

Display Target and Initiator Details 44

Page 45: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Result:

Figure 14 Pillar Axiom system target details in the iSNS Server property sheet

3 Select an initiator and click Details to display the initiator registration details(iSCSI name, alias, entity, and portals), as well as the discovery domains ofwhich the initiator is a member.

Chapter 5 Set Up and Configure iSNS

Display Target and Initiator Details 45

Page 46: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Configure Discovery Domains and Discovery Domain SetsYou must configure at least one discovery domain and at least one discoverydomain set, and enable the discovery domain set, to use the Pillar Axiom InternetStorage Name Service (iSNS)-based access control feature.

Create a Discovery DomainYou must configure at least one discovery domain in the iSNS Server control panel.

1 Double-click the Microsoft iSNS Server desktop icon to open the iSNS Servercontrol panel.

2 Click the Discovery Domains tab.

3 Select Choose or create a Discovery Domain from the Discovery Domain list, andclick Create.

4 Enter a name for your discovery domain (such as mylab-DD) in the CreateDiscovery Domain dialog box, and click OK.

Result:The name appears in the Discovery Domain list.

5 Select the name of the discovery domain you created in the DiscoveryDomain list.

Result:The members of the discovery domain (there will be none at first) display inthe Members list.

6 Click Add to add a member to the discovery domain.

Result:The Add registered Initiator or Target to Discovery Domain dialog boxdisplays.

7 Select an initiator or target to add to the discovery domain, and click OK.

Repeat this step for all initiators and targets to add as members of thediscovery domain.

If you enable iSNS-based access control in the Pillar Axiom Storage ServicesManager, only those initiators that are members of discovery domains of whichthe Pillar Axiom storage system is also a member will be allowed to log in to thePillar Axiom storage system.

Chapter 5 Set Up and Configure iSNS

Configure Discovery Domains and Discovery Domain Sets 46

Page 47: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Create a Discovery Domain SetAfter you have added initiators and targets to your discovery domain, you mustadd your discovery domain to a discovery domain set.

1 Double-click the Microsoft iSNS Server desktop icon to open the iSNS Servercontrol panel.

2 Click the Discovery Domain Sets tab in the iSNS Server property sheet.

3 Select Choose or create a Discovery Domain Set from the Discovery Domain Setlist.

4 Click Create.

Result:The Create Discovery Domain Set dialog box displays.

5 Enter a name for your discovery domain set (such as mylab-DiscoveryDomain Set) and click OK.

Result:The discovery domain set name displays in the Domain Discovery Set list.

6 Select the name of the discovery domain set you created.

Result:The discovery domain set members (there will be none at first) display inthe Members list.

7 Click Add to add discovery domains to the discovery domain set.

Result:The Add Discovery Domain Set Members dialog box displays a list ofavailable discovery domains.

8 Select the discovery domains to add to the discovery domain set, and clickOK.

Enable a Discovery Domain SetYour newly created discovery domain set must be enabled in order to operate.

Chapter 5 Set Up and Configure iSNS

Configure Discovery Domains and Discovery Domain Sets 47

Page 48: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

1 Double-click the Microsoft iSNS Server desktop icon to open the iSNS Servercontrol panel.

2 Click the Discovery Domain Sets tab in the iSNS Server Properties window.

3 Select the discovery domain set name in the Discovery Domain Set list.

4 Select Enable.

Disable the Default Discovery Domain SetThe iSNS Server control panel will always show a default discovery domain anddiscovery domain set (Default DD and Default DDS). The Default DD and DefaultDDS contain all registered initiators and targets.

The iSNS Server control panel will not allow the Default DD or Default DDS to bedeleted. Instead, you must disable the Default DDS in order for your newlycreated discovery domain and discovery domain set configuration to functioncorrectly. Otherwise, removing an initiator from your discovery domain will notprevent it from logging into your Pillar Axiom target because the initiator is still amember of the Default DD, and the Default DDS is still enabled.

1 Double-click the Microsoft iSNS Server desktop icon to open the iSNS Servercontrol panel.

2 Click the Discovery Domain Sets tab in the iSNS Server Properties window.

3 Select Default DDS in the Discovery Domain Set list.

4 Clear the Enable check box.

Chapter 5 Set Up and Configure iSNS

Configure Discovery Domains and Discovery Domain Sets 48

Page 49: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

iSNS Command Line InterfaceThe iSNS Command Line Interface (CLI) enables you to run Internet StorageName Service (iSNS) commands directly from a command prompt, without theiSNS Console.

In addition to the iSNS Console, the Microsoft iSNS Server v3.0 package alsoinstalls an isnscli command line tool for viewing iSNS server registrations andcreating or viewing discovery domain and discovery domain set configurations. Afew isnscli commands are described here. For more information aboutiSNSCLI commands, refer to the Microsoft iSNS Server Users Guide or, at aWindows command prompt, enter:

isnscli help

Table 4 iSNS CLI sample commands

Command Short form Description

isnscli ListNodes isnscli LN Lists all registered nodes. Anode is an iSCSI intiator ortarget.

isnscli ListAllNodesWithDetails isnscli LA Lists each node along withdetails. Essentially performsa ListNodeDetails on eachnode returned by ListNodes.

isnscliListAllDiscoveryDomainSetsWithMembers

isnscli LADDS Lists each discoverydomain set along with themembers of each set.Essentially performs aListDiscoveryDomainSetMembers on each discoverydomain set returned byListDiscoveryDomainSets.

isnscliListDiscoveryDomainNodeMembers [DD_ID]

isnscliLDDNM[DD_ID]

Lists all node members ofthe discovery domainspecified by DD_ID.

Chapter 5 Set Up and Configure iSNS

iSNS Command Line Interface 49

Page 50: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

Index

AAPM

See Pillar Axiom Path Managerauthentication

CHAP 33Bbidirectional CHAP

iSCIS Software Initiator 37Pillar Axiom system 36

Ccabling requirements 11CHAP

bidirectional configurationiSCSI Software Initiator 37Pillar Axiom system 36

definition 33unidirectional configuration

iSCSI Software Initiator 34Pillar Axiom system 33

configure iSCSI integration 15connection requirements 11contact information 13Ddiscover Slammer iSCSI port 23discovery domain

definition 39how to

create 46discovery domain set

definition 40how to

create 47disable default 48enable 47

Disk Management utilityfor LUN recognition 31

documentationMicrosoft 14related 14

Hhelp, online 13

host bus adaptersiSCSI 10

Iinitiator

definition 8how to

display details 44installation

iSCSI Software Initiator 17iSNS Server 41

iSCSIconfiguration task map 15definition 8host bus adapters 10how to

configure 15configure multipathing 12install Software Initiator 17

iSCSI CLIhow to

verify iSCSI port connection 28iSCSI LUN

how toconfigure on Pillar Axiom system 29map to Windows server on Pillar Axiom

system 30recognize on Windows server 31

QoS 29iSCSI port

cabling requirements 11how to

add to iSCSI Software Initiator 25configure on Pillar Axiom system 19discover from iSCSI Software Initiator 23verify connection from Pillar Axiom system

28verify connection with iSCSI CLI 28verify connection with iSCSI Software

Initiator 27iSCSI Software Initiator

CHAP secret 22

50

Page 51: Pillar Axiom iSCSI Integration Guide for Windows PlatformsCHAPTER 1 Introduction to iSCSI About iSCSI The Internet Small Computers Standard Interface (iSCSI) is an IP-based protocol

how toadd Slammer iSCSI ports 25configure bidirectional CHAP 37configure CHAP secret 21configure node name 21configure unidirectional CHAP 34discover Slammer iSCSI port 23install 17register iSNS 42verify iSCSI port connection 27

node name 22Windows 2008 16

iSNScommand line interface 49definition 39discovery domain 39discovery domain set 40how to

create discovery domain 46create discovery domain set 47disable default discovery domain set 48display initiator details 44display target details 44enable discovery domain set 47enable in Pillar Axiom system 42install 41register in iSCSI Software Initiator 42

MMicrosoft documentation 14multipathing 12Oonline help 13operating systems

supported 16Ppaths

multipath configuration 12Pillar Axiom Path Manager 12Pillar Axiom system

how toconfigure bidirectional CHAP 36configure iSCSI LUN 29configure Slammer iSCSI port 19configure unidirectional CHAP 33enable iSNS 42map iSCSI LUN to Windows server 30verify iSCSI port connection 28

Pillar Data Systems Web site 13product support 13QQoS

iSCSI LUN 29

Rrelated documentation 14

Ssales information 13Slammer iSCSI port

how toadd to iSCSI Software Initiator 25configure on Pillar Axiom system 19discover from iSCSI Software Initiator 23verify connection from Pillar Axiom system

28verify connection with iSCSI CLI 28verify connection with iSCSI Software

Initiator 27supported operated systems 16

Ttarget

definition 8how to

display details 44TCP/IP

used to transfer iSCSI commands 8technical support 13

Uunidirectional CHAP

iSCSI Software Initiator 34Pillar Axiom system 33

WWindows server

how torecognize iSCSI LUN 31

51