Post on 03-Jun-2018
8/11/2019 3par RedHat 45 Implementation Guide
1/132
3PAR Confidential
3PAR RedHat 4 & 5 and OEL
(Oracle Enterprise Linux)Implementation Guide
3PAR, Inc.
4209 Technology Drive
Fremont, CA 94538 USA
Part No. 320-200268 Rev A
December 2010
8/11/2019 3par RedHat 45 Implementation Guide
2/132
3PAR Confidential
Revision NoticeThis is the first release of this manual. A complete revision history is provided at the end of this document.
Changes
The material in this document is for information only and is subject to change without notice. While reasonable efforts have beenmade in the preparation of this document to assure its accuracy, 3PAR Inc. assumes no liability resulting from errors or omissions in
this document or from the use of the information contained herein.
3PAR reserves the right to make changes in the product design without reservation and without notification to its users.
Updates to the Documentation at 3PAR CentralAny updates to this document, or to other 3PAR technical documents, can be found by logging in to 3PAR Centrals Document
Control System from 3PARs Support page at http://support.3PAR.com.
3PAR Technical Support and Services
Contact your local service provider for technical support and services at: http://www.3PAR.com/services.html.
Sales and Ordering InformationFor sales and ordering information, contact:
3PAR Inc.
4209 Technology Drive
Fremont, CA 94538 USA
Telephone: 510-413-5999
Fax: 510-413-5699
Email: salesinfo@3PAR.com
Reader Comments and SuggestionsPlease email your comments and suggestions about this document to ReaderComments@3PAR.com.
Copyrights 2010 3PAR Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of 3PAR Inc.,
4245 Technology Drive, Fremont, CA 94538. By way of exception to the foregoing, the user may print one copy of electronic material
for personal use only.
Trademarks3PAR, InServ, InForm, InSpire and Serving Information are registered trademarks of 3PAR Inc.
Intel and Pentium are registered trademarks of Intel Corporation.
Linux is a registered trademark of Linus Torvalds.
RedHat is a registered trademark of RedHat, Inc.
SuSE is a registered trademark of Novell, Inc.
Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation.
Oracle is a registered trademark of Oracle Corporation.
Sun, Solaris, and Java are trademarks of Sun Microsystems, Inc.
UNIX is a registered trademark of The Open Group.
All other trademarks and registered trademarks are owned by their respective owners.
8/11/2019 3par RedHat 45 Implementation Guide
3/132
3PAR ConfidentialiiiTable of Contents
3PAR RedHat 4 and RedHat 5 Implementation Guide
Table of Contents
1 Introduction
1.1 Supported Configurations
1.2
1.2 InForm OS Upgrade Considerations
1.2
1.3 Audience
1.2
1.4 Related Documentation
1.3
1.5 Organization
1.4
1.6 Typographical Conventions
1.5
1.7 Advisories
1.6
2 Configuring the InServ Storage Server for Fibre Channel
2.1 Configuring the InServ Storage Server Running InForm OS 2.3.X
2.2
2.1.1 Configuring Ports for a Direct Connection 2.2
2.1.2 Configuring Ports for a Fabric Connection 2.3
2.1.3 Creating the Host Definition 2.5
2.2 Configuring the InServ Storage Server Running InForm OS 2.2.X
2.6
2.2.1 Configuring Ports for a Direct Connection 2.6
2.2.2 Configuring Ports for a Fabric Connection 2.6
2.2.3 Creating the Host Definition 2.7
2.3 Connecting the InServ Storage Server to the Host
2.8
8/11/2019 3par RedHat 45 Implementation Guide
4/132
iv Table of Contents
3PAR Confidential
3PAR RedHat 4 and RedHat 5 Implementation Guide
2.4 Setting Up and Zoning the Fabric
2.8
2.4.1 Configuration Guidelines for Fabric Vendors 2.9
2.4.2 Target Port Limits and Specifications 2.102.4.3 Configuration Diagrams for Zoning 2.10
3 Configuring the InServ Storage Server for iSCSI
3.1 Configuring Ports for an iSCSI Connection
3.1
3.2 Creating the iSCSI Host Definition
3.3
4 Connecting a Host Server with Fibre Channel
4.1 Checking the Host for Required Packages
4.2
4.2 Installing the Emulex HBA
4.2
4.2.1 Building the Emulex Driver 4.3
4.2.2 Modifying the etc/modprobe.conf file and Building the Ramdisk 4.4
4.3 Installing the QLogic HBA
4.8
4.3.1 Building the QLogic Driver 4.8
4.3.2 Modifying the /etc/modprobe.conf file and Building the Ramdisk 4.9
4.4 Setting the SCSI Timeout
4.12
4.4.1 Using UDEV Rules to Set the SCSI Timeout 4.13
4.4.2 Using QLogic Scripts to Set the SCSI Timeout 4.154.4.3 Using Emulex Scripts to Set the SCSI Timeout 4.16
4.5 Setting Up Multipathing Software
4.18
4.5.1 Setting Up Device Mapper 4.18
4.5.2 Setting Up Veritas DMP Multipathing 4.22
4.5.3 Installing the 3PAR Host Explorer Package 4.24
5 Connecting a Host Server with iSCSI
5.1 Setting Up the Ethernet Switch and Network Interface Card
5.2
5.2 Configuring RedHat 4 for iSCSI
5.2
5.2.1 Installing iSCSI on RedHat 4 5.2
5.2.2 Setting Up iSCSI for RedHat 4 5.3
5.2.3 Configuring RedHat 4 iSCSI Settings with Device Mapper Multipathing 5.4
8/11/2019 3par RedHat 45 Implementation Guide
5/132
vTable of Contents
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
5.2.4 Starting the iSCSI Daemon for RedHat 4 5.5
5.3 Configuring RedHat 5 for iSCSI
5.6
5.3.1 Installing iSCSI on RedHat 5 5.65.3.2 Setting Up iSCSI for RedHat 5 5.6
5.3.3 Configuring RedHat 5 iSCSI Settings with Device Mapper Multipathing 5.9
5.3.4 Starting the iSCSI Daemon for RedHat 5 5.10
5.3.5 Creating the iSCSI Connection in RedHat 5 Using the iscsiadm Command 5.11
5.4 Configuring CHAP for the iSCSI Host
5.14
5.4.1 Setting the Host CHAP Authentication on the InServ Storage Server 5.14
5.4.2 Setting Up the Bidirectional CHAP on the InServ Storage Server 5.17
6 Allocating Storage for Access by the RedHat Host
6.1 Creating Storage on the InServ Storage Server
6.2
6.1.1 Creating Virtual Volumes 6.2
6.1.2 Creating Thin Provisioned Volumes 6.3
6.2 Exporting LUNs to the Host
6.3
6.3 Restrictions on Volume Size and Number
6.5
6.4 Discovering Devices with an Emulex HBA
6.6
6.4.1 Scan Methods for LUN Discovery 6.6
6.4.2 Verifying Devices Found by the Host Using the Emulex HBA 6.7
6.5 Discovering Devices with a QLogic HBA
6.9
6.5.1 Scan Methods for LUN Discovery 6.9
6.5.2 Verifying Devices Found by the Host Using the QLogic HBA 6.12
6.6 Discovering Devices with an iSCSI Connection
6.14
6.6.1 Discovering Devices with RedHat 4 6.14
6.6.2 Discovering Devices with RedHat 5 6.15
7 Modifying 3PAR Devices on the Host Server
7.1 Creating Device Mapper Devices
7.1
7.2 Displaying Detailed Device Mapper Node Information
7.5
7.3 Partitioning Device Mapper Nodes
7.6
8/11/2019 3par RedHat 45 Implementation Guide
6/132
vi Table of Contents
3PAR Confidential
3PAR RedHat 4 and RedHat 5 Implementation Guide
7.4 Creating Veritas Volume Manager Devices
7.8
7.5 Removing a Storage Volume from the Host
7.9
8 Booting the Host from the InServ Storage Server
8.1 Inserv Storage Server Setup Requirements
8.1
8.2 RedHat Host HBA BIOS Setup Considerations
8.2
8.2.1 Booting from the InServ Storage Server Using QLogic HBAs 8.2
8.2.2 Booting from the InServ Storage Server Using Emulex HBAs 8.3
8.3 Installation from RedHat 5 Linux CDs
8.4
8.4 Modifying the /etc/multipath.conf file
8.5
8.5 Changing the Emulex HBA Inbox Driver Parameters
8.6
8.6 Installing the New QLogic Driver
8.6
9 Using Veritas Cluster Servers
10 Using RedHat Xen Virtualization
11 Using RedHat Cluster Services
12 Using RedHat KVM Hypervisor
A RedHat iscsiadm Utility Usage
B Setting up the NVRAM and BIOS with QLogic HBA
C Configuring the QLogic HBA Using the SCLI Utility
RH Revision History
8/11/2019 3par RedHat 45 Implementation Guide
7/132
3PAR RedHat 4 and RedHat 5 Implementation Guide
1.1Introduction3PAR Confidential
1
Introduction
In this chapter
1.3 Audience 1.2
1.4 Related Documentation 1.3
1.5 Organization 1.4
1.6 Typographical Conventions 1.5
1.7 Advisories 1.6
This implementation guide provides the information you need to configure a 3PARInServ
Storage Server with RedHat 4 and RedHat 5. General information is also provided on the basic
steps required to allocate storage on the InServ Storage Server that can then be accessed by
the RedHat host.
The information contained in this implementation guide is the outcome of careful testing of
the 3PAR InServ Storage Server with as many representative hardware and software
configurations as possible.
REQUIRED: For predictable performance and results with your
3PAR InServ Storage Server, the information in this guide must be used in concert
with the documentation set provided by 3PAR for the InServ Storage Server and
the documentation provided by the vendor for their respective products.
8/11/2019 3par RedHat 45 Implementation Guide
8/132
1.2 Supported Configurations
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
1.1 Supported Configurations
The following types of host connections are supported between the InServ Storage Server and
hosts running Linux OS:
Fibre Channel
iSCSI
For complete details on supported host configurations, consult the latest 3PAR InForm
Configuration Matrix that is available on DCS.
1.2 InForm OS Upgrade Considerations
Refer to the InForm OS Upgrade Pre-Planning Guide for information and planning of an online
InForm OS upgrade.
1.3 Audience
This implementation guide is intended for system and storage administrators who monitor and
direct system configurations and resource allocation for 3PAR InServ Storage Servers. The tasks
described in this manual assume that the administrator is familiar with RedHat 4/RedHat 5 and
the 3PAR Inform OS. Although this guide attempts to provide the basic information that is
required to establish communications between the InServ Storage Server and the RedHat host,
and to allocate the required storage for a given configuration, the appropriate 3PAR
documentation must be consulted in conjunction with the RedHat host and HBA vendor
documentation for specific details and procedures.
NOTE: This Implementation Guide does NOT intend to reproduce any third-party
product documentation. For details about devices such as host servers, HBAs,
fabric and Ethernet switches, and non-3PAR software management tools, consult
the appropriate third-party documentation.
8/11/2019 3par RedHat 45 Implementation Guide
9/132
1.3Related Documentation
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
1.4 Related Documentation
The following documents also provide information related to InServ Storage Servers and theInForm Operating System:
For information about Read the
Specific platforms supported 3PAR InForm Configuration
Matrix
CLI commands and their usage InForm OS Command Line
Interface Reference
Using the InForm Management
Console to configure and
administer InServ Storage Servers
3PAR InForm OS Management
Console Online Help
InServ Storage Server concepts
and terminology
3PAR InForm OS Concepts Guide
Determining InServ Storage
Server hardware specifications,
installation considerations,
power requirements, networkingoptions, and cabling
3PARInServ S-Class/T-Class
Storage Server Physical Planning
Manualor the 3PARInServ E-
Class/F-Class Storage ServerPlanning Manual
Identifying storage server
components and detailed alert
information
3PAR InForm OS Messages and
Operators Guide
Using 3PAR Remote Copy 3PAR Remote Copy Users Guide
Using 3PAR CIM 3PAR CIM API Programming
Reference
8/11/2019 3par RedHat 45 Implementation Guide
10/132
1.4 Organization
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
1.5 Organization
This guide is organized as follows:
Chapter 1, Introduction(this chapter), provides an overview of this guide, including
information on audience, related documentation, and typographical conventions.
Chapter 2, Configuring the InServ Storage Server for Fibre Channel, provides instructions
for configuring the InServ Storage Server for a Fibre Channel connection.
Chapter 3, Configuring the InServ Storage Server for iSCSI. provides instructions forconfiguring the InServ Storage Server for an iSCSI connection.
Chapter 4, Connecting a Host Server with Fibre Channel, provides instructions for preparing
the RedHat host for connection to the InServ Storage Server over a Fibre Channel network.
Chapter 5, Connecting a Host Server with iSCSI, provides instructions for preparing the
RedHat host server for connection to the InServ Storage Server over an iSCSI network.
Chapter 6,Allocating Storage for Access by the RedHat Host, provides instructions for
creating storage on the InServ Storage Server, exporting LUNs to the RedHat host, and
performing LUN discovery from the RedHat host server.
Chapter 7, Modifying 3PAR Devices on the Host Server, provides instructions for modifying
3PAR devices on a RedHat host with a Fibre Channel or iSCSI connection.
Chapter 8, Booting the Host from the InServ Storage Server, provides instructions forconfiguring a RedHat host for booting from the InServ Storage Server.
Chapter 9, Using Veritas Cluster Servers, indicates support and where to find for
configuring the Veritas Cluster Server with RedHat host.
Chapter 10, Using RedHat Xen Virtualization, indicates support for the RedHat host for use
as virtual machine (Xen).
Chapter 11, Using RedHat Cluster Services, indicates support for the RedHat Cluster
Services.
Chapter 12, Using RedHat KVM Hypervisor, indicates support for using the RedHat host as a
Kernel Virtual Machine (KVM).
Appendix A, RedHat iscsiadm Utility Usage, provides examples of iscsiadm commands.
Appendix B, Setting up the NVRAM and BIOS with QLogic HBA, provides instructions for
setting NVRAM BIOS for the QLogic HBA.
8/11/2019 3par RedHat 45 Implementation Guide
11/132
8/11/2019 3par RedHat 45 Implementation Guide
12/132
1.6 Advisories
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
1.7 Advisories
To avoid injury to people or damage to data and equipment, be sure to observe the cautionsand warnings in this guide.Always be careful when handling any electrical equipment.
NOTE: Notes are reminders, tips, or suggestions that supplement the procedures
included in this guide.
CAUTION: Cautions alert you to actions that can cause damage to equipment,
software, or data.
REQUIRED: Requirements signify procedures that must be followed as directed in
order to achieve a functional and supported implementation based on testing at
3PAR.
WARNING: Warnings alert you to actions that can cause injury to people or
irreversible damage to data or the operating system.
8/11/2019 3par RedHat 45 Implementation Guide
13/132
3PAR RedHat 4 and RedHat 5 Implementation Guide
2.1Configuring the InServ Storage Server for Fibre Channel3PAR Confidential
2Configuring the InServ
Storage Server for Fibre
Channel
In this chapter2.1 Configuring the InServ Storage Server Running InForm OS 2.3.X 2.2
2.1.1 Configuring Ports for a Direct Connection 2.2
2.1.2 Configuring Ports for a Fabric Connection 2.3
2.1.3 Creating the Host Definition 2.5
2.2 Configuring the InServ Storage Server Running InForm OS 2.2.X 2.6
2.2.1 Configuring Ports for a Direct Connection 2.6
2.2.2 Configuring Ports for a Fabric Connection 2.6
2.2.3 Creating the Host Definition 2.7
2.3 Connecting the InServ Storage Server to the Host 2.8
2.4 Setting Up and Zoning the Fabric 2.8
2.4.1 Configuration Guidelines for Fabric Vendors 2.9
2.4.2 Target Port Limits and Specifications 2.10
2.4.3 Configuration Diagrams for Zoning 2.10
8/11/2019 3par RedHat 45 Implementation Guide
14/132
2.2 Configuring the InServ Storage Server Running InForm OS 2.3.X
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
This chapter describes how to establish a connection between InServ Storage Server and
RedHat host using Fibre Channel and how to set up the fabric when running InForm OS 2.3.X
and InForm OS 2.2.X. For information on setting up the physical connection for a particular
InServ Storage Server, see the appropriate 3PAR installation manual.
2.1 Configuring the InServ Storage Server Running InForm OS 2.3.X
This section describes how to configure InServ Storage Server running InForm OS 2.3.X.
2.1.1 Configuring Ports for a Direct Connection
To configure InServ Storage Server ports for a direct connection to the RedHat host, complete
the following steps:
1 To set up the InServ Storage Server ports for a direct connection, issue the following set of
commands with the appropriate parameters for each direct connect port:
a cont rol por t of f l i ne [ node: sl ot : por t ]
b cont rol por t conf i g host ct l oop [ node: sl ot : por t ]
where - ct l oopspecifies a direct connection.
c cont rol por t r st [ node: sl ot : por t ]
Example:
REQUIRED: If you are setting up a fabric along with your installation of the
InServ Storage Server, consult2.4 Setting Up and Zoning the Fabricon page 2.8
before configuring or connecting your InServ Storage Server.
REQUIRED: The following setup must be completed before connecting the InServ
Storage Server port to a device.
# cont rol port of f l i ne 1: 5: 1# cont rol por t conf i g host - ct l oop 1: 5: 1# cont rol port rst 1: 5: 1
8/11/2019 3par RedHat 45 Implementation Guide
15/132
8/11/2019 3par RedHat 45 Implementation Guide
16/132
2.4 Configuring the InServ Storage Server Running InForm OS 2.3.X
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
2 If the port has NOT been configured, take the port offline before configuring it for
connection to a host server. To take the port offline, issue the CLI command cont r ol por t
of f l i ne [node: sl ot : port ] .
3 To configure the port to the host server, issue cont r ol por t conf i g host ct
poi nt [ node: sl ot : por t ] , where - ct poi nt indicates that the connection type
specified is a fabric connection.
4 Reset the port by issuing the cont r ol por t r st [ node: sl ot : por t ] command.
#showport -par
N: S: P Connmode ConnType CfgRate MaxRate Cl ass2 Uni qNodeWwn VCN I ntCoal
0: 0:1 di sk l oop auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed0: 0:2 di sk l oop auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed0: 0:3 di sk l oop auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed0: 0:4 di sk l oop auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed0: 4:1 host poi nt auto 4Gbps di sabl ed di sabl ed di sabl ed enabl ed0: 4:2 host poi nt auto 4Gbps di sabl ed di sabl ed di sabl ed enabl ed0: 5:1 host poi nt auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed0: 5:2 host l oop auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed0: 5:3 host poi nt auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed0: 5:4 host l oop auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed1: 0:1 di sk l oop auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed1: 0:2 di sk l oop auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed1: 0:3 di sk l oop auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed1: 0:4 di sk l oop auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed1: 2:1 host poi nt auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed1: 2:2 host l oop auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed1: 4:1 host poi nt auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed1: 4:2 host poi nt auto 2Gbps di sabl ed di sabl ed di sabl ed enabl ed1:5:1 host point auto 4Gbps disabled disabled disabled enabled
1: 5:2 host l oop auto 4Gbps di sabl ed di sabl ed di sabl ed enabl ed1: 5:3 host l oop auto 4Gbps di sabl ed di sabl ed di sabl ed enabl ed1: 5:4 host l oop auto 4Gbps di sabl ed di sabl ed di sabl ed enabl ed
# cont rol port of f l i ne 1: 5: 1
# cont rol por t conf i g host ct poi nt 1: 5: 1
# cont rol port rst 1: 5: 1
8/11/2019 3par RedHat 45 Implementation Guide
17/132
2.5Configuring the InServ Storage Server Running InForm OS 2.3.X
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
2.1.3 Creating the Host Definition
Before connecting the RedHat host to the InServ Storage Server, create a host definition that
specifies a valid host persona for each InServ Storage Server that is to be connected to a host
HBA port through a fabric or a direct connection.
1 To create host definitions, issue the cr eatehost [ opt i ons]
[ . . . ] command. For example:
2 To verify that the host has been created, issue the showhost command.
# cr eatehost - per sona 1 r edhathost 1122334455667788 1122334455667799
Set t i ng def aul t host persona 1 ( Gener i c)
# showhostI d Name Persona - WWN/ i SCSI _Name- Por t6 redhat host Gener i c 1122334455667788 - - -
1122334455667799 - - -
NOTE: 3PAR recommends Host persona 1 for hosts running RHEL 4 update 6 and
above RHEL 5.0 and above to enable Host_Explorer functionality.
However, host persona 6 is automatically assigned following a rolling upgrade
from 2.2x. If appropriate, you can change host persona 6 after an upgrade tohost persona 1.
Host Persona 1 enables two functional features: Host_Explorer, which requires the
SESLun element of host persona 1, and the UARepLun, which notifies the host of
newly exported vLUNs and should trigger a LUN discovery request on the host,
making the vLUN automatically available. Currently, none of the supported RHEL
versions use the UARepLun, so you must manually scan the newly exported vLUNs.
NOTE: See the 3PAR InForm OS Command Line Referenceor the IMC help for
complete details on using the cont r ol por t , creat ehost and showhost
commands.
8/11/2019 3par RedHat 45 Implementation Guide
18/132
2.6 Configuring the InServ Storage Server Running InForm OS 2.2.X
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
2.2 Configuring the InServ Storage Server Running InForm OS 2.2.X
This section describes how to configure InServ Storage Server running OS 2.2.X.
2.2.1 Configuring Ports for a Direct Connection
To configure the InServ Storage Server ports for a direct connection, complete the following
steps.
1 Set each InServ Storage Server port to port personality 1 by issuing cont rol por t persona
1 , where is the port location, expressed as node:slot:port.
2 Issue cont rol por t vcn di sabl e - f .
3 Verify that each port has the appropriate personality defined:
2.2.2 Configuring Ports for a Fabric Connection
To configure the InServ Storage Server ports for a fabric connection, complete the following
steps.
1 Set each storage server port that will connect to a fabric to port persona 7 by issuing
cont rol port persona 7 , where is the port location, expressed as
node:slot:port.
2 Issue cont rol por t vcn di sabl e - f for each port.
3 Verify each port has the appropriate persona defined:
REQUIRED: The following setup must be completed before connecting the InServ
Storage Server port to a device.
# showport - parN: S: P ConnTypeCf gRat eCl ass2 VCN - - - - - - - - - - - Persona- - - - - - - - - - - - I nt Coal4: 0: 2 l oop aut o di sabl e di sabl e *( 1) g_ven, g_hba, g_os, 0, DC enabl ed
# showport -parN: S: P ConnType Cf gRat e Cl ass2 VCN - - - - - - - - - - - Persona- - - - - - - - - - - - I nt Coal4: 0: 2 poi nt aut o di sabl e di sabl e *( 7) g_ven, g_hba, g_os, 0, FA enabl ed
3PAR R dH t 4 d R dH t 5 I l t ti G id
8/11/2019 3par RedHat 45 Implementation Guide
19/132
2.7Configuring the InServ Storage Server Running InForm OS 2.2.X
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
2.2.3 Creating the Host Definition
Before connecting the RedHat host to the InServ Storage Server, create a host definition that
specifies a valid host persona for each InServ Storage Server that is to be connected to a host
HBA port through a fabric or a direct connection.
1 To create host definitions on the InServ Storage Server, issue creat ehost [ opt i ons]
[ ] .
2 To verify the host definition, issue showhost :
# cr eatehost redhathost 1122334455667788 1122334455667799
# showhost2 redhat host 1122334455667788 4: 0: 1
1122334455667799 5: 0: 1
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
20/132
2.8 Connecting the InServ Storage Server to the Host
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
2.3 Connecting the InServ Storage Server to the Host
During this stage connect the InServ Storage Server to the host server directly or to the fabric.This set of tasks includes physically cabling the InServ Storage Server to the host server or
fabric.
2.4 Setting Up and Zoning the Fabric
Fabric zoning controls which devices have access to each other on the fabric. The required useof single initiator to single target zoning isolates the host server and InServ Storage Server
ports from Registered State Change Notifications (RSCNs) that are irrelevant to these ports.
You can set up fabric zoning by associating the device World Wide Names (WWNs) or ports
with specified zones in the fabric. Although you can use either the WWN or the port zoning
methods with the InServ Storage Server, the WWN zoning method is recommended because
the zone survives the changes of ports when cables are reconnected on a fabric.
Use the methods provided by the switch vendor to create relationships between host server
HBA ports and storage server ports before you connect the host server HBA ports or InServ
Storage Server ports to the fabric.
After connecting each host server HBA port and InServ Storage Server port to the fabric(s),
verify the switch and zone configurations using the InForm CLI showhost command, to ensure
that each initiator is zoned with the correct target.
In the following explanations an initiator port (initiator for short) refers to a host server HBA
port and a target port (target for short) refers to an InServ Storage Server HBA port.
REQUIRED: When you establish zoning with the InServ Storage Server, there must
only be a single initiator zoned with a single target. If an issue occurs usinganother zoning approach, 3PAR may require that you implement this zoning
approach as part of troubleshooting and/or corrective action.
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
21/132
2.9Setting Up and Zoning the Fabric
3PAR RedHat 4 and RedHat 5 Implementation Guide
3PAR Confidential
2.4.1 Configuration Guidelines for Fabric Vendors
Use the following fabric vendor guidelines before configuring ports on fabric(s) to which the
InServ Storage Server connects.
Brocade switch ports that connect to a host server HBA port or to an InServ Storage Server
port should be set to their default mode. On Brocade 3xxx switches running Brocade
firmware 3.0.2 or later, verify that each switch port is in the correct mode using the Brocade
telnet interface and the por t cf gshowcommand as follows:
McData switch or director ports should be in their default modes as type GX-Portwith a
speed setting of Negotiate.
Cisco switch ports that connect to InServ Storage Server ports or host HBA ports should be
set to AdminMode = FXand AdminSpeed = auto port, with the speed set to auto
negotiate.
QLogic switch ports should be set to port type GL-portand port speed auto-detect.
QLogic switch ports that connect to the InServ Storage Server should be set to I/O Stream
Guard disableor auto, but never enable.
brocade2_1: admi n> port cf gshow
Port s 0 1 2 3 4 5 6 7- - - - - - - - - - - - - - - - - +- - +- - +- - +- - +- - - - +- - +- - +- -
Speed AN AN AN AN AN AN AN AN
Trunk Por t ON ON ON ON ON ON ON ON
Locked L_Por t . . . . . . . . . . . . . . . .
Locked G_Port . . . . . . . . . . . . . . . .
Di sabl ed E_Por t . . . . . . . . . . . . . . . .
where AN: Aut oNegot i at e, . . : OFF, ??: I NVALI D.
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
22/132
2.10 Setting Up and Zoning the Fabric
p
3PAR Confidential
2.4.2 Target Port Limits and Specifications
To avoid overwhelming a target port and ensure continuous I/O operations, refer to the
following limitations on a target port:
Maximum of 64 host server ports per InServ Storage Server port, with a maximum total of
1,024 host server ports per InServ Storage Server.
I/O queue depth on each InServ Storage Server HBA model as follows:
QLogic 2G: 497
LSI 2G: 510
Emulex 4G: 959
3PAR HBA 4G: 1638
The I/O queues are shared among the connected host server HBA ports on a first-come,
first-served basis
When all queues are in use and a host HBA port tries to initiate I/O, it receives a targetqueue full response from the InServ Storage Server port. This condition can result in erratic
I/O performance on each host server. If this condition occurs, each host server should be
throttled so that it cannot overrun the InServ Storage Server port's queues when all host
servers are delivering their maximum number of I/O requests.
2.4.3 Configuration Diagrams for Zoning
This section describes various zoning configurations.
NOTE: When host server ports can access multiple targets on fabric zones, the
assigned target number assigned by the host driver for each discovered target can
change when the host server is booted and some targets are not present in the
zone. This situation may change the device node access point for devices during a
host server reboot. This issue can occur with any fabric-connected storage, and is
not specific to the InServ Storage Server.
NOTE: In the examples in the following sections, a fabric can be one or more Fibre
Channel switches or directors.
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
23/132
2.11Setting Up and Zoning the Fabric3PAR Confidential
2.4.3.1 Single Initiator to Single Target Zoning No Fan-In No Fan-Out
With a single initiator to single target zoning, in a no fan-in, no fan-out configuration, each
HBA port is connected to only one InServ Storage Server port, as shown in Figure 2-1.
Figure 2-1. Single Initiator to Single Target Zoning No Fan-In/No Fan-Out
0004_IG_R1
Node 0 Node 1
Host Server A Host Server B
InServ
Fabric Fabric
A single initiator to
a single target in a zone
to target port
(InServ)
to initiator port
(host)
port
port
Zone
3PAR RedHat 4 and RedHat 5 Implementation Guide
http://-/?-http://-/?-8/11/2019 3par RedHat 45 Implementation Guide
24/132
2.12 Setting Up and Zoning the Fabric3PAR Confidential
2.4.3.2 Single Initiator to Single Target Zoning with Fan-Out from One
InServ Storage Server Port to Multiple Host Server Ports
With single initiator to single target zoning, in a fan-out configuration, the InServ Storage
Server port is connected to more that one host port, as shown in Figure 2-2.
Figure 2-2. Single Initiator to Single Target Zoning with Fan-Out
NOTE: A maximum of 64 host server ports can fan-out from a single
InServ Storage Server port.
0003_IG_R1
Node 0 Node 1
Host Server A Host Server B
InServ
FabricFabric
3PAR RedHat 4 and RedHat 5 Implementation Guide
http://-/?-http://-/?-8/11/2019 3par RedHat 45 Implementation Guide
25/132
2.13Setting Up and Zoning the Fabric3PAR Confidential
2.4.3.3 Single Initiator to Single Target Zoning with Fan-In from Multiple
InServ Storage Server Ports to One Host Server Port
With single initiator to single target zoning, in a fan-in configuration a host server port
connects to many InServ Storage Server ports, as shown in Figure 2-3.
Figure 2-3. Single Initiator to Single Host Target Zoning with Fan-In
0002_IG_R1
Node 0 Node 1
Host Server
InServ
Fabric Fabric
NOTE: A maximum of four InServ Storage Server ports can fan-in to a single host
server port.
http://-/?-http://-/?-8/11/2019 3par RedHat 45 Implementation Guide
26/132
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
27/132
2.15Setting Up and Zoning the Fabric3PAR Confidential
2.4.3.5 Non-Compliant Zoning Examples
In the following example, the zoning rule of one initiator zoned to one target is not respected,
as shown in Figure 2-5.
Figure 2-5. Non-Compliant Zoning
0001_IG_R1
Node 0
No zoning
Node 1
Host Server A
Fabric A
Host Server B
CB
A
Multiple initiators to a single targetB
Single initiator to multiple targetsC
InServ
Non-Compliant Zoning
Fabric
3PAR RedHat 4 and RedHat 5 Implementation Guide
http://-/?-http://-/?-8/11/2019 3par RedHat 45 Implementation Guide
28/132
2.16 Setting Up and Zoning the Fabric3PAR Confidential
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
29/132
3.1Configuring the InServ Storage Server for iSCSI3PAR Confidential
3Configuring the InServ
Storage Server for iSCSI
In this chapter
3.1 Configuring Ports for an iSCSI Connection 3.1
3.2 Creating the iSCSI Host Definition 3.3
3.1 Configuring Ports for an iSCSI Connection
To configure an iSCSI target port on the InServ Storage Server for connection to an iSCSI
Initiator, complete the following steps:
1 Check the current settings of the iSCSI ports by issuing showpor t - i scsi .
2 Set up the IP address and netmask address of the iSCSI target ports by issuing
cont r ol i scsi por t addr [ - f ] node: sl ot : por t .
# showpor t - i scsiN: S: P State I PAddr Netmask Gateway TPGT MTU Rat e DHCP i SNS_Pr i mi SNS_Sec i SNS_Por t0: 3: 1 off l i ne 0. 0. 0. 0 0. 0. 0. 0 0. 0. 0. 0 31 1500 n/ a 0 0. 0. 0. 0 0. 0. 0. 0 32050: 3:2 l oss_sync 0.0. 0.0 0. 0. 0.0 0. 0.0. 0 32 1500 n/ a 0 0. 0. 0. 0 0. 0.0. 0 32051: 3: 1 off l i ne 0. 0. 0. 0 0. 0. 0. 0 0. 0. 0. 0 131 1500 n/ a 0 0. 0. 0. 0 0. 0. 0. 0 32051: 3:2 l oss_sync 0.0. 0.0 0.0. 0.0 0. 0.0. 0 132 1500 n/a 0 0. 0. 0. 0 0. 0.0. 0 3205
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4
# cont rol i scsi por t addr 10. 100. 0. 101 255. 0. 0. 0 - f 0: 3: 1
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
30/132
3.2 Configuring Ports for an iSCSI Connection3PAR Confidential
3 Verify the changed settings by issuing showpor t - i scsi .
4 Issue the pi ngcommand to verify that the Ethernet switch ports where the InServ iSCSI
target ports and iSCSI Initiator host connect are visible to each other.
# showpor t - i scsiN: S: P State I PAddr Netmask Gateway TPGT MTU Rat e DHCP i SNS_Pr i mi SNS_Sec i SNS_Por t0:3:1 ready 10. 100.0.101 255.0.0.0 0.0.0.0 31 1500 1Gbps 0 0.0.0.0 0.0.0.0 32050: 3:2 l oss_sync 0. 0.0. 0 0. 0.0.0 0.0. 0. 0 32 1500 n/ a 0 0. 0. 0. 0 0.0. 0. 0 32051:3:1 ready 10. 101.0.201 255.0.0.0 0.0.0.0 131 1500 1Gbps 0 0.0.0.0 0.0.0.0 32051: 3:2 l oss_sync 0. 0.0. 0 0. 0.0.0 0.0. 0. 0 132 1500 n/ a 0 0. 0. 0. 0 0.0. 0. 0 3205- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
31/132
3.3Creating the iSCSI Host Definition3PAR Confidential
3.2 Creating the iSCSI Host Definition
This section describes how to create an iSCSI host definition.
1 You can verify that the iSCSI Initiator is connected to the iSCSI target port by using the CLI
showhost command.
2 Create an iSCSI host definition entry by using the CLI creat ehost - i scsi
command. For example:
NOTE: You must configure the InServ iSCSI target port(s) and establish an iSCSI
Initiator connection/session with the iSCSI target port from the host to be able to
create a host definition entry. For details, see 5.3.5 Creating the iSCSI Connection
in RedHat 5 Using the iscsiadm Commandon page 5.11.
# showhostI d Name Persona - - - - - - - - - - WWN/ i SCSI _Name- - - - - - - - - - - Por t- - i qn. 1994- 05. com. redhat: a3df 53b0a32d 0: 3: 1
i qn. 1994- 05. com. redhat : a3df 53b0a32d 1: 3: 1
NOTE: 3PAR requires Host persona 1 for hosts running RHEL 4 update 6 and
above RHEL 5.0 and above to enable Host_Explorer functionality.
However, host persona 6 is automatically assigned following a rolling upgrade
from 2.2x. It is required to change host persona 6 after an upgrade to hostpersona 1.
Host Persona 1 enables two functional features: Host_Explorer, which requires the
SESLun element of host persona 1, and the UARepLun, which notifies the host of
newly exported vLUNs and should trigger a LUN discovery request on the host,
making the vLUN automatically available. Currently, none of the supported RHEL
versions use the UARepLun, so you must manually scan the newly exported vLUNs.
# creat ehost - i scsi redhat host i qn. 1994- 05. com. redhat : a3df 53b0a32dSet t i ng def aul t host persona 1 ( Gener i c)
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
32/132
3.4 Creating the iSCSI Host Definition3PAR Confidential
3 Verify that the host entry has been created.
Example of showhost output for InServ Storage Server running OS 2.2.X:
NOTE: For RedHat 4, you can get the iSCSI initiator name from /etc/
i ni t i atorname:
# cat / et c/ i ni t i at orname. i scsiI ni t i atorName=i qn. 1987- 05. com. ci sco: 01. 4766d09183f 3
# showhostI d Name Persona - - - - - - - - - - WWN/ i SCSI _Name- - - - - - - - - - - Por t
0 redhathost Generi c i qn. 1994- 05. com. redhat: a3df 53b0a32d 0: 3: 1 i qn. 1994- 05. com. redhat: a3df 53b0a32d 1: 3: 1
NOTE: For Inserv running OS 2.2.X, the output of showhost appears differently
since there are no Persona fields.
# showhostI d Name -- - - - - - - - - - WWN/ i SCSI _Name- - - - - - - - - - - - Por t0 l i nux i qn. 1994- 05. com. r edhat : a3df 53b0a32d 0: 3: 1
i qn. 1994- 05. com. redhat: a3df 53b0a32d 1: 3: 1
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
33/132
4.1Connecting a Host Server with Fibre Channel3PAR Confidential
4Connecting a Host Server
with Fibre Channel
In this chapter
4.1 Checking the Host for Required Packages 4.2
4.2 Installing the Emulex HBA 4.2
4.2.1 Building the Emulex Driver 4.3
4.2.2 Modifying the etc/modprobe.conf file and Building the Ramdisk 4.4
4.3 Installing the QLogic HBA 4.7
4.3.1 Building the QLogic Driver 4.7
4.3.2 Modifying the /etc/modprobe.conf file and Building the Ramdisk 4.8
4.4 Setting the SCSI Timeout 4.12
4.4.1 Using UDEV Rules to Set the SCSI Timeout 4.13
4.4.2 Using QLogic Scripts to Set the SCSI Timeout 4.15
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
34/132
4.2 Checking the Host for Required Packages3PAR Confidential
4.5 Setting Up Multipathing Software 4.18
4.5.1 Setting Up Device Mapper 4.18
4.5.2 Setting Up Veritas DMP Multipathing 4.22
4.5.3 Installing the 3PAR Host Explorer Package 4.24
This chapter describes the tasks necessary for connecting the host to Fibre Channel. When tasks
are specific to the version of the RedHat OS, headings refer to RedHat 4 or RedHat 5.
4.1 Checking the Host for Required PackagesIf you are installing and building the Emulex driver, make sure the Developmental Tool
package that contains the gcc compiler is installed on the RedHat server. If not, install them
from the RedHat installation CD. After installation, verify the following gcc packages were
installed. Some gcc packages may not be needed.
The following example shows gcc compilers installed for RedHat 4 Update 6 Li nux.
4.2 Installing the Emulex HBA
Install the Emulex host bus adapter(s) in the host server according to the documentationprovided with the HBAs and host server.
# rpm -qa | grep gcc
gcc- j ava- 3. 4. 6- 9
gcc- 3. 4. 6- 9
compat- gcc- 32- c++- 3. 2. 3- 47. 3
gcc- c++- 3. 4. 6- 9
compat - l i bgcc- 296- 2. 96- 132. 7. 2
l i bgcc- 3. 4. 6- 9gcc-g77- 3. 4. 6- 9
l i bgcc- 3. 4. 6- 9
3PAR RedHat 4 and RedHat 5 Implementation Guide
4 2 1 B ildi th E l D i
8/11/2019 3par RedHat 45 Implementation Guide
35/132
4.3Installing the Emulex HBA3PAR Confidential
4.2.1 Building the Emulex Driver
If you are installing the Emulex driver instead of using the in-box Emulex driver that was
already installed by the RedHat installation, follow these steps:
1 Download the driver package from www.emulex.com and extract the driver contents by
issuing t ar xvzf l pf c__dr i ver _ki t - . t ar . gz.
Example:
2 Change to the driver source directory by issuing cd l pf c_
_dr i ver _ki t - . For example:
3 Run the l pf c- i nstal l script that builds and installs the l pf cdriver. Check the installed
README for more details.
# . / l pf c- i nstal l
The script performs the following:
a The driver source is installed at / usr/ src/l pf c from the installed rpm packages
l pf cdr i ver - _. For example:
b The l pf cdriver parameters are added to / etc/ modpr obe. conf.
NOTE: Use this section only if you are installing and building the Emulex driver. If
you are using the Emulex driver that was installed by the RedHat installation, skip
to 4.2.2 Modifying the etc/modprobe.conf file and Building the Ramdiskon
page 4.4.
# tar xvfz lpfc_2.6_driver_kit-8.0.16.40-2.tar.gz
l pf c_2. 6_dr i ver_ki t - 8. 0. 16. 40- 2/
l pf c_2. 6_dr i ver_ki t - 8. 0. 16. 40- 2/ l pf cdr i ver_2. 6- 8. 0. 16. 40- 1. noarch. r pml pf c_2. 6_dri ver_ki t - 8. 0. 16. 40- 2/ l pf c-i nstal l
l pf c_2. 6_dr i ver_ki t - 8. 0. 16. 40- 2/ README
l pf c_2. 6_dri ver_ki t - 8. 0. 16. 40- 2/ el xl pf c
# cd l pf c_2. 6_dr i ver _ki t - 8. 0. 16. 40- 2
# ls /usr/src/lpfc/lpfcdriver*
l pf cdr i ver - 2. 6- 8. 0. 16. 40- 2
3PAR RedHat 4 and RedHat 5 Implementation Guide
c The newly built Emulex driver l pf c ko is copied to / l i b/ modul es/ /
8/11/2019 3par RedHat 45 Implementation Guide
36/132
4.4 Installing the Emulex HBA3PAR Confidential
c The newly built Emulex driver l pf c. kois copied to / l i b/ modul es/ /
kernel / dri vers/ scsi / l pf c. The current l pf cdriver is saved at / usr/ src/l pf c/
savedf i l es.
d A new ramdisk is created and the currently running ramdisk is copied as / boot /i ni t rd- . i mg.
The items in bold were added by the l pf c- i nstal l script to the / etc/ modpr obe. conf
configuration file for a dual ported HBA:
4.2.2 Modifying the etc/modprobe.conf file and Building the Ramdisk
This section describes how to modify the etc/modprobe.conf file to set Emulex HBA parameters
and build the ramdisk.
1 Before building the ramdisk, add the following HBA parameters to the
/ etc/ modpr obe. conffile depending on your version of RedHat. These HBA options
settings are required for desired multipath failover/failback operation:
CAUTION: The new Ramdisk is always created with the name i ni t rd- . i mg. Edit the boot loader to add the correct ramdisk name.
Example: For kernel =2. 6. 18- 53. el 5, the ramdisk created by the
script will be initrd.2. 6. 18- 53. el 5. i mg.
NOTE: There are number of Emulex driver parameters that can be changed by
modifying the / etc/ modpr obe. confconfiguration file that enables these
driver parameter values when the drivers are loaded during boot up. Only the
parameters affecting the InServ Storage Server are discussed here.
# cat /etc/modprobe.conf
al i as et h0 e1000
al i as et h1 e1000
al i as scsi _host adapt er mpt base
al i as scsi _host adapt er1 mpt scsi h
al i as usb- cont rol l er ehci - hcd
al i as usb- cont rol l er 1 uhci - hcd
alias scsi_hostadapter2 lpfc
alias scsi_hostadapter3 lpfc
8/11/2019 3par RedHat 45 Implementation Guide
37/132
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
38/132
4.6 Installing the Emulex HBA3PAR Confidential
4 Rebuild the ramdisk image using the mki ni t r dcommand:
# / sbi n/ mki ni t rd - v - f / boot /
The following example shows a ramdisk build:
REQUIRED: Storage Administrators should carefully consider the number of hosts
connected to an InServ Storage Server port and the number of LUN exports for
calculating the throttling configuration values. Performance degradation andSCSI timeout issues will result if the values are set too low.
NOTE: The ramdisk image needs to be rebuilt for any changes made to / et c/
modprobe. confto be effective. The system will pick up the ramdisk changes on
bootup.
# /sbin/mkinitrd -v -f /boot/initrd-2.6.18-53.el5.img 2.6.18-53.el5Creat i ng i ni t ramf s
Looki ng f or deps of modul e scsi _mod
Looki ng f or deps of modul e sd_mod scsi _mod
Looki ng f or deps of modul e scsi _t ranspor t _spi : scsi _mod
. . .
copy f rom`/ l i b/ modul es/ 2. 6. 18- 8. el 5/ kernel / dr i vers/ scsi /
scsi _t ranspor t _f c. ko'
[ el f 64- x86- 64] t o `/ t mp/ i ni t rd. l 13681/ l i b/ scsi _t ranspor t _f c. ko' [ el f 64- x86-64]
copy f rom`/ l i b/ modul es/ 2. 6. 18- 8. el 5/ kernel / dri vers/ scsi / l pf c/ l pf c. ko'
[ el f 64-
x86- 64] t o `/ t mp/ i ni t rd. l 13681/ l i b/ l pf c. ko' [ el f 64- x86- 64]
. . .
Loadi ng modul e j bd
Loadi ng modul e ext 3
Loadi ng modul e scsi _modLoadi ng modul e scsi _mod wi t h opt i ons max_l uns=256
Loadi ng modul e sd_mod
Loadi ng modul e mptbase
Loadi ng modul e mptscsi h
Loadi ng modul e scsi _t ranspor t _f c
Loadi ng modul e l pf c wi t h opt i ons l pf c_t opol ogy=0x02 l pf c_devl oss_t mo=1
3PAR RedHat 4 and RedHat 5 Implementation Guide
5 Check the contents of the / et c/ grub. confor / boot / gr ub/ gr ub. confwith grub as
8/11/2019 3par RedHat 45 Implementation Guide
39/132
4.7Installing the QLogic HBA3PAR Confidential
/ / g / / g / g g
the bootloader so that the i ni t r dmaps to the correct ramdisk image.
4.3 Installing the QLogic HBA
Install the QLogic host bus adapter(s) in the host server based on the documentation provided
with the HBAs and host server.
4.3.1 Building the QLogic Driver
If you are building the QLogic driver, follow these steps:
1 Download the driver package (SANsurfer Linux Installer for RedHat Enterprise Linux kernel)
from www.qlogic.com and extract the driver contents. The example below demonstrates
this step:
Follow the provided README to build the driver.
# t ar xvf z
# vi /etc/grub.confdef aul t =
t i meout =5
hi ddenmenuf
t i t l e RedHat Ent erpr i se Li nux Server ( 2. 6. 18- 8. el 5)
root ( hd0, 2)
kernel / boot / vml i nuz- 2. 6. 18- 8. el 5 ro root =LABEL=/ rhgb qui et
i ni t rd / boot / i ni t rd- 2. 6. 18- 8. el 5. i mg
NOTE: If you are using the in-box QLogic driver by the RedHat host installation,
skip this section and go to section 4.3.2 Modifying the /etc/modprobe.conf file
and Building the Ramdiskon page 4.8
3PAR RedHat 4 and RedHat 5 Implementation Guide
For example:
8/11/2019 3par RedHat 45 Implementation Guide
40/132
4.8 Installing the QLogic HBA3PAR Confidential
2 Go to the driver installation directory by issuing the following command:
# cd ql af c- l i nux- - i nstal l
For example:
3 Run the script:
# . /ql i nstal l - i - dp
This script will perform the following:
a Modifies the contents of / etc/ modpr obe. conf.
b Copies the QLogic source to / usr/ sr c/ ql ogi c, builds the QLogic driver and copies
the QLogic drivers to / l i b/ modul es/ `uname - r `/ kernel / dr i ver s/ scsi /
ql a2xxx.
c Builds the ramdisk image using the default ramdisk image name.
d Copies all the old contents before overwriting to /usr/ src/ ql ogi c/
/ backup.
4.3.2 Modifying the /etc/modprobe.conf file and Building the Ramdisk
# tar xvfz qlafc-linux-8.01.07.15-2-install.tgz
ql af c-l i nux- 8. 01. 07. 15- 2- i nstal l /
ql af c- l i nux- 8. 01. 07. 15- 2- i nstal l / set _dr i ver _param
. . . . . . . . . . . . . . . . .
ql af c- l i nux- 8. 01. 07. 15- 2- i nstal l / ql i nstal l
ql af c- l i nux- 8. 01. 07. 15- 2- i nstal l / ql - pci . i ds
# cd ql af c- l i nux- 8. 01. 07. 15- 2- i nstal l
NOTE: If you are using the QLogic driver that was installed during the OS
installation (inbox driver), steps 1 and 2 will not be necessary. Start at step 3.
3PAR RedHat 4 and RedHat 5 Implementation Guide
1 Identify the contents added by the installer to / etc/ modprobe. conf. The following
8/11/2019 3par RedHat 45 Implementation Guide
41/132
4.9Installing the QLogic HBA3PAR Confidential
output is the result of testing based on the QLA23XX, QLE23XX, QLE24XX, and QLE25XX
cards in the system.
2 Modify the contents of / etc/ modprobe. confto remove the boldface items above.
# cat /etc/modprobe.conf
alias scsi_hostadapter qla2xxx_conf
al i as scsi _host adapt er1 ql a2xxx
al i as scsi _host adapt er2 ql a2300
al i as scsi _host adapt er3 ql a2322
al i as scsi _host adapt er4 ql a2400
al i as scsi _host adapt er5 ql a6312
opt i ons scsi _mod max_l uns=256opt i ons ql a2xxx ql 2xf ai l over=0 Conf i gRequi red=0
i nstal l
ql a2xxx
/ sbi n/ modprobe qla2xxx_conf; / sbi n/ modprobe - - i gnore- i nstal l
ql a2xxx
remove ql a2xxx / sbi n/ modpr obe - r - - f i r st - t i me - - i gnore- remove ql a2xxx && {
/
sbin/modprobe -r --ignore-remove qla2xxx_conf; }
8/11/2019 3par RedHat 45 Implementation Guide
42/132
3PAR RedHat 4 and RedHat 5 Implementation Guide
In the following example, the output shows the / et c/ modpr obe. confwhen the
l d h
8/11/2019 3par RedHat 45 Implementation Guide
43/132
4.11Installing the QLogic HBA3PAR Confidential
ql2xmaxqdepth is set to 16.
4 Rebuild the ramdisk image after the /etc/modprobe.conf file entries are modified.
5 To make the changes, you can issue the mki ni t r dcommand or use the QLogic driver
script.
# mki ni t rd - f - v / boot/ i ni t rd- . i mg .
For example:
6 Perform one of the two following actions to verify that all the required drivers are added
to the ramdisk image:
# cat /etc/modprobe.conf
al i as scsi _host adapt er1 ql a2xxx
al i as scsi _host adapt er2 ql a2300
al i as scsi _host adapt er3 ql a2322
al i as scsi _host adapt er4 ql a2400
al i as scsi _host adapt er5 ql a6312
opt i ons scsi _mod max_l uns=256
opt i ons ql a2xxx ql port _down_r etr y=1 ql 2xf ai l over=0 ql 2xmaxqdept h=16
Conf i gRequi red=0i nstal l ql a2xxx / sbi n/ modprobe - - i gnore- i nstal l ql a2xxx
remove qla2xxx /sbin/modprobe -r --first-time --ignore-remove qla2xxx
REQUIRED: Storage Administrators should carefully consider the number of hosts
connected to an InServ Storage Server port and the number of LUN exports for
calculating the throttling configuration values. Performance degradation andSCSI timeout issues will result if the values are set too low.
# mki ni t rd - f - v / boot / i ni t rd- 2. 6. 18- 53. el 5. i mg 2. 6. 18- 53. el 5
3PAR RedHat 4 and RedHat 5 Implementation Guide
Check the verbose output. For example:
8/11/2019 3par RedHat 45 Implementation Guide
44/132
4.12 Setting the SCSI Timeout3PAR Confidential
Use the QLogic installer script to rebuild the ramdisk image. The backup ramdisk will be
stored at / usr / src/ ql ogi c/ / backup.
# . / ql i nstal l -br
7 Check the contents of the / et c/ grub. confor / boot / gr ub/ gr ub. confwith grub as
the bootloader so that the i ni t r dmaps to the correct ramdisk image.
4.4 Setting the SCSI Timeout
The SCSI timeout needs to be set at 60 seconds in order for the InServ Storage Server to
operate properly with RedHat servers. Use the following guidelines depending on your version
of RedHat:
RedHat 5the SCSI timeout value is already set to the default value of 60 seconds and does
NOT need to be changed.
RedHat 4the SCSI timeout value is 30 seconds and needs to be changed to 60 seconds.
Creat i ng i ni t ramf s
. . . .
. . . .
Looki ng f or deps of modul e scsi _mod
Looki ng f or deps of modul e sd_mod: scsi _mod
. . . .
. . . .
Looki ng f or deps of modul e ql a2xxx: i nt ermodul e scsi _mod
Looki ng for deps of modul e i nt ermodul e
. . . .
. . . .
# vi / et c/ grub. conf
def aul t =
t i meout =5
hi ddenmenu
t i t l e RedHat Ent erpr i se Li nux Server ( kernel name)root ( hd0, 0)
kernel / ro r oot =LABEL=/ rhgb qui et
i ni t rd /
8/11/2019 3par RedHat 45 Implementation Guide
45/132
3PAR RedHat 4 and RedHat 5 Implementation Guide
REQUIRED M k th i b k b t th t li i th
8/11/2019 3par RedHat 45 Implementation Guide
46/132
4.14 Setting the SCSI Timeout3PAR Confidential
The udevrule number 56_3par _t i meout . r ul esshould follow after the 50- udev. r ul es.
Change the udevrule number accordingly.
The 56_3par _t i meout . r ul esis selected based on the test system configuration. See 4.4.1
Using UDEV Rules to Set the SCSI Timeouton page 4.13to verify that the
56_3par_t i meout . r ul esudevrule is working.
4.4.1.1 Verifying the SCSI Timeout Settings
Verify the udevrules setting after the 3PAR storage volumes have been exported to the host
For details, seeAllocating Storage for Access by the RedHat Hoston page 6.1.
# udevi nf o - a - p / sys/ bl ock/ sdx
For example:
You can also verify the SCSI timeout settings as following:
cat / sys/ cl ass/ scsi _host / host*/ devi ce/ */ */ t i meout
For RedHat 5 using Emulex HBAs, verify using the following:
cat / sys/ cl ass/ scsi _host / host*/ devi ce/ */ */ */ t i meout
If the udev rule is created after the host sees InServ Storage Server volumes, execute the
udevstar t command, which runs the udevrules on all devices and sets the timeout to 60.
The time it takes for the udevst art command to complete is based on the number of devices
and I/O throughput, so the recommendation is to run the command during non-peak activity.
# udevst ar t
Reboot of host starts the udevrule by default.
REQUIRED: Make sure there is no break between the two lines in the
56_3par_t i meout . r ul es.
# l s / et c/udev/ rul es. d/
. . . . .
40- mul t i pat h. rul es
50- udev. rul es
51- by- i d. rul es
56- 3par - t i meout . rul es
# udevi nf o -a -p / sys/bl ock/ sdn | grep t i meout SYSFS{t i meout}="60"
3PAR RedHat 4 and RedHat 5 Implementation Guide
4.4.2 Using QLogic Scripts to Set the SCSI Timeout
8/11/2019 3par RedHat 45 Implementation Guide
47/132
4.15Setting the SCSI Timeout3PAR Confidential
The following script changes the SCSI timeout value to 60 seconds for LUNs discovered by each
of the QLogic HBA ports. Use this script if you are running Remote Copy.
If you have implemented the timeout value change using the udevmethod, then do not use
this script.
When you run the script, the SCSI timeout value for each of the current LUNs discovered will be
changed immediately. However, when rebooting the server, the timeout value will revert to
the default value of 30 seconds.
The following example shows the content for Scri pt ql _ch_scsi _t i meout . sh:
You can have this script run during the OS boot up sequence by adding the contents of the
script into the / etc/ rc. l ocal file. Make sure / et c/ rc. l ocal file has the permissions
values set to 777.
ql ogi cname="/ sys/ cl ass/ scsi _host "
t i meout=60
l s $ql ogi cname | grep "[ 0- 9] [ 0- 9] *" | whi l e read l i ne
do
f name=${ql ogi cname}/ $l i ne
cur r = pwd`
cd $f namef i nd . - f ol l ow - name "t i meout " | grep - v "gener i c" | whi l e read l i ne2
do
vendorcheck= cat ${l i ne2%t i meout }vendor | grep - c "3PARdat a"`
i f [ $vendorcheck - gt 0 ] ; t hen
echo "modi f yi ng f i l e: [ $f name$l i ne2] "
echo "$t i meout " > $l i ne2
f i
donecd $curr
done
8/11/2019 3par RedHat 45 Implementation Guide
48/132
3PAR RedHat 4 and RedHat 5 Implementation Guide
The SCSI instance number is 2 and target is 0 from the above output:
8/11/2019 3par RedHat 45 Implementation Guide
49/132
4.17Setting the SCSI Timeout3PAR Confidential
You can also manually change the timeout value using the following commands:
# cd / sys/ cl ass/ scsi _host / host2/ devi ce/ t arget 2: 0: 0/ 2: 0: 0: 0
# echo 60 > t i meout
# cat t i meout
60
The set _t ar get _t i meout script needs to be executed for all the SCSI instances of l pf cj
driver; if the operation if performed manually, the command needs to be executed for all the
devices.
# . / set _t arget _t i meout 2 0 60modi f yi ng devi ce / sys/ cl ass/ scsi _devi ce/ 2: 0: 0: 0/ devi ce
f ound t i meout at val ue 30new t i meout val ue i s 60modi f yi ng devi ce / sys/ cl ass/ scsi _devi ce/ 2: 0: 0: 1/ devi cef ound t i meout at val ue 30new t i meout val ue i s 60. . .
NOTE: If the Emulex driver is unloaded and reloaded for any reason, the timeout
setting will reset to the default setting of 30 seconds for all Emulex attached
devices. If this occurs, set the timeout value back to 60 seconds using any of the
described methods. This is not applicable if the timeout is changed using the
udevrule.
3PAR RedHat 4 and RedHat 5 Implementation Guide
4 5 Setting Up Multipathing Software
8/11/2019 3par RedHat 45 Implementation Guide
50/132
4.18 Setting Up Multipathing Software3PAR Confidential
4.5 Setting Up Multipathing Software
3PAR supports the following multipath solutions for RedHat:
Device mapper.
VERITAS Volume Manager.
4.5.1 Setting Up Device Mapper
In RedHat 5.4, multipath tools are installed by default. Prior to RedHat 5.4, multipath tools are
not installed during the default OS installation, so you need to install device mapper from the
RedHat installation CDs, as demonstrated in the following example.
Check for installed device mapper packages by issuing r pm- qa| gr ep devi ce-mapper:
You can use the following commands to configure multipath devices:
mul t i pathinspects Linux devices to see if there are multiple paths to the same device and
communicates to the kernel device mapper to set up a device map (dm) device for the
device and is responsible for the path coalescing and device map creation.
The mul t i pat hddaemon checks path health and will reconfigure the multipath map
whenever a path comes up or goes down so as to maintain correctly the path mapping
state.
kpar t xreads partition tables on specified devices and creates device maps over partition
segments that are detected.
Device Mapper also depends on the udevand sysf suti l sfilesystem packages. udevis a
user space process which dynamically manages the creation of devices under the / dev/
# mount - ro / dev/ cdr om/ mnt / cdrom
# cd / mnt/ cdrom/ RedHat/ RPMS
# rpm- i hv - - percent devi ce- mapper - mul t i pat h- 0. 4. 5- 31. el 4. x86_64. rpm
# umount / mnt / cdrom
# rpm -qa|grep device-mapper
devi ce- mapper - 1. 02. 25- 2. el 4
devi ce- mapper - mul t i path- 0. 4. 5- 31. el 4
devi ce- mapper - 1. 02. 25- 2. el 4
3PAR RedHat 4 and RedHat 5 Implementation Guide
filesystem. The sysf suti l spackage exports the view of the system hardware configuration
to udevuserspace process for device node creation. These packages must be present on the
8/11/2019 3par RedHat 45 Implementation Guide
51/132
4.19Setting Up Multipathing Software3PAR Confidential
system.
For example:
In RedHat 5.4, the following packages appear after installation:
If / usr is a separate partition and is not part of the root (/) partition in the installed RedHat
Operating System, then copy the shared library l i bsysf s. soand create the required
sysml i nksfrom the / usr / l i bdirectory to the / l i bdirectory.
The following examples show partitions for 32-bit and 64-bit operating systems:
On a 32-bit installed operating System:
# cp / usr/ l i b/ l i bsysf s. so. 1. 0. 2 / l i b/
# l n - s / l i b/ l i bsysfs. so. 1. 0. 2 / l i b/ l i bsysf s. so. 1
# l n - s / l i b/ l i bsysfs. so. 1 / l i b/ l i bsysf s. so
On 64-bit installed operating System:
# cp / usr/ l i b64/ l i bsysfs. so. 1. 0. 2 / l i b64/
# l n - s / l i b64/ l i bsysfs. so. 1. 0. 2 / l i b64/ l i bsysfs. so. 1
# l n - s / l i b64/ l i bsysfs. so. 1 / l i b64/ l i bsysfs. so
# rpm- qa | grep udev
udev- 039- 10. 19. el 4
# rpm- qa | grep sysf s
sysf sut i l s- devel - 1. 2. 0- 1
sysfsut i l s-1. 2. 0- 1
# rpm- qa | grep udevudev- 095- 14. 21. el 5
# rpm- qa | grep sysf s
l i bsysfs- 2. 0. 0- 6sysfsut i l s-2. 0. 0- 6
3PAR RedHat 4 and RedHat 5 Implementation Guide
CAUTION: If / usr is a separate partition, there will be a system hang during
8/11/2019 3par RedHat 45 Implementation Guide
52/132
4.20 Setting Up Multipathing Software3PAR Confidential
4.5.1.1 Modifying the /etc/multipath.conf File
The / et c/ mul t i pat h. conffile is used by device mapper where the multipathing
parameters have been set. The default installed / et c/ mul t i path. conffile must be edited
with the following changes for a minimum configuration connecting to a 3PAR array. Entrieslisted in multipath.conf override the default kernel parameters for dm-multipath. In general,
the kernel defaults are sufficient with the exception of the devices entries for 3PAR. In the
specific case of booting the host from an InServ Storage Server volume (a.k.a, SAN boot), there
are additional defaults entries required:
1 Remove or comment out all entries in the / et c/ mul t i path. conffile except for the
devices section of devices currently in use.
2 Edit the devices structure to add entries for 3PAR array and remove other product entries
that are not needed.
bootup when multipath starts and cannot find the shared library
l i bsysf s. so. 1 because / usr partition gets mounted at the later stage of theboot process. So, copying the shared library l i bsysf s. so. 1to / l i bdirectory
will resolve the issue.
NOTE: The sysfsut i l s-xxpackage contains the l i bsysfs. so. 1library. If
any upgrades are made to this package, the new library file should be copied overto the / l i bdirectory.
NOTE: Refer to Chapter 8, Booting the Host from the InServ Storage Serverfor
SAN boot requirements. Refer to RedHat documentation of DM Multipath
Configuration and Administration for additional options in mul t i path. conf
entries.
3PAR RedHat 4 and RedHat 5 Implementation Guide
After all of the edits are made, the relevant sections of / et c/ mul t i pat h. confshould
appear as follows:
8/11/2019 3par RedHat 45 Implementation Guide
53/132
4.21Setting Up Multipathing Software3PAR Confidential
4.5.1.2 Enabling Multipath
Perform the following actions to enable multipath.
1 Invoke the mul t i pat hcommand for any name changes to be effective.
2 Verify that the mul t i pathd daemon is enabled by the rc script to run on every host boot
up. The following output shows that it is enabled for run-level 3, 4 and 5. Enable it
appropriately for your configuration:
3 Check that the appropriate rc scripts have been created for each run level. The startnumber(s) may not match those shown here.
# cat / et c/ mul t i pat h. conf
devi ces {
devi ce {
vendor "3PARdat a"
product "VV"
pol l i ng_i nt erval 5
no_path_r etry 12
f eat ures "0"
hardware_handl er "0"
path_groupi ng_pol i cy mul t i bus
pat h_sel ect or "r ound- robi n 0"
r r _wei ght uni f orm
r r _mi n_i o 100
path_checker t ur
f ai l back i mmedi ate
}
}
# chkconf i g - - l i st mul t i pat hd
mul t i pat hd 0: of f 1: of f 2: of f 3: on 4: on 5: on 6: of f
# l s / et c/ rc3. d/ *mul t i *
/ et c/ r c3. d/ S13mul t i pathd
# l s / et c/ rc5. d/ *mul t i *
/ et c/ r c5. d/ S13mul t i pathd
3PAR RedHat 4 and RedHat 5 Implementation Guide
You can also use the chkconf i gcommand to enable multipathing:
# chkconf i g mul t i pathd on
8/11/2019 3par RedHat 45 Implementation Guide
54/132
4.22 Setting Up Multipathing Software3PAR Confidential
4.5.2 Setting Up Veritas DMP Multipathing
For Active/Active multi-path load balancing and failover, install VERITAS Storage Foundation
and High Availability Software, following the instructions given in the VERITAS Volume
Manager Installation Guide and Administrator Guideavailable from www.VERITAS.com.
When installing the VERITAS Volume Manager, the following VERITAS driver Modules and file
system modules are included:
It is required to have the Veritas Array Support Library (ASL) for 3PAR InServ Storage Server
installed on the RedHat host if you are using a Veritas Storage Foundation version prior to
5.0mp3. To obtain the Veritas Array Support Library (ASL) for 3PAR InServ Storage Server,
complete the following tasks:
1 Download the latest Veritas Array Support Library (ASL) for 3PAR InServ Storage Server
from the http://support.veritas.com site.
2 Under the volume manager for Unix product, search for 3PAR and select the ASL (Array
Support Library) for 3PAR InServ Storage Server on Volume Manager of the version to be
used (or later) for Linux and install it on the host.
NOTE: If using the QLogic HBA, the QLogic Non-Failover Driver should have been
installed for VERITAS DMP support. Device Mapper (DM) or multipath modules
should not be configured if VERITAS DMP is used for multipathing.
/ l i b/ modul es/ / ver i t as/ vxvm/ dmpaaa. ko
/ l i b/ modul es/ / veri t as/ vxvm/ dmpaa. ko / l i b/ modul es// ver i t as/ vxvm/ dmpapf . ko
/ l i b/ modul es/ / ver i t as/ vxvm/ dmpapg. ko
/ l i b/ modul es/ / veri t as/ vxvm/ dmpj bod. ko / l i b/ modul es/
/ ver i t as/ vxvm/ vxdmp. ko
/ l i b/ modul es/ / ver i t as/ vxvm/ vxi o. ko
/ l i b/ modul es/ / veri t as/ vxvm/ vxspec. ko
/ l i b/ modul es/ / ver i t as/ vxf s/ f dd. ko
/ l i b/ modul es/ / ver i t as/ vxf s/ vxf s. ko/ l i b/ modul es/ / ver i t as/ vxf s/ vxpor t al . ko
3PAR RedHat 4 and RedHat 5 Implementation Guide
3 To install the ASL, the Veritas vxconf i gddaemon must be running. Running vxi nstal l
will start the daemon. Once you install the ASL package, you must run the vxdct l enable
command to claim the disk array as a 3PAR array
8/11/2019 3par RedHat 45 Implementation Guide
55/132
4.23Setting Up Multipathing Software3PAR Confidential
command to claim the disk array as a 3PAR array.
4 Configure the VERITAS vxdmpdriver to manage the InServ Storage Server paths providingpath failure management and dynamic load balancing.
5 To confirm the VERITAS vxdmpdriver has registered and claimed the 3PAR InServ storage
server, issue the following VERITAS command:
If you are using the Veritas Storage Foundation version 5.0mp3 or higher, then you do notneed to install the ASL (Array Support Library) for the InServ Storage Server. To verify that the
InServ Storage Server is recognized and supported by the installation, run the following
command:
However, if the output does not show the InServ Storage Server, perform the following step tohave the storage server added as a 3PARDATA device:
# vxddl admaddsupport al l
# vxddladm listsupport libname=libvx3par.so
ATTR_NAME ATTR_VALUE
=======================================================================
LI BNAME l i bvx3par. so
VI D 3PARdata
PI D VV
ARRAY_TYPE A/ A
ARRAY_NAME 3PARDATA
# vxddladm listsupport libname=libvx3par.so
ATTR_NAME ATTR_VALUE
=======================================================================LI BNAME l i bvx3par. so
VI D 3PARdata
PI D VV
ARRAY_TYPE A/ A
ARRAY_NAME 3PARDATA
3PAR RedHat 4 and RedHat 5 Implementation Guide
Then verify the InServ Storage Server is supported, as shown in the following example.
# vxddladm listsupport libname=libvx3par.so
8/11/2019 3par RedHat 45 Implementation Guide
56/132
4.24 Setting Up Multipathing Software3PAR Confidential
4.5.3 Installing the 3PAR Host Explorer Package
With InForm OS 2.3.1, the Host Explorer daemon running on the RedHat server to send
information about the host configuration to a 3PAR InServ over the Fibre Channel link is
available. For installation and activation of this package, please refer to 3PAR Host Explorer
Users Guidein DCS.
# pp p
ATTR_NAME ATTR_VALUE
=======================================================================LI BNAME l i bvx3par. soVI D 3PARdataPI D VVARRAY_TYPE A/ AARRAY_NAME 3PARDATA
WARNING: If the ARRAY_NAME is not designated as 3PARDATA, the
multipathing layer may not discover devices correctly.
3PAR RedHat 4 and RedHat 5 Implementation Guide
8/11/2019 3par RedHat 45 Implementation Guide
57/132
5.1Connecting a Host Server with iSCSI3PAR Confidential
5Connecting a Host Server
with iSCSI
In this chapter
5.1 Setting Up the Ethernet Switch and Network Interface Card 5.2
5.2 Configuring RedHat 4 for iSCSI 5.2
5.2.1 Installing iSCSI on RedHat 4 5.2
5.2.2 Setting Up iSCSI for RedHat 4 5.3
5.2.3 Configuring RedHat 4 iSCSI Settings with Device Mapper Multipathing 5.4
5.2.4 Starting the iSCSI Daemon for RedHat 4 5.5
5.3 Configuring RedHat 5 for iSCSI 5.6
5.3.1 Installing iSCSI on RedHat 5 5.6
5.3.2 Setting Up iSCSI for RedHat 5 5.6
5.3.3 Configuring RedHat 5 iSCSI Settings with Device Mapper Multipathing 5.9
5.3.4 Starting the iSCSI Daemon for RedHat 5 5.10
5.3.5 Creating the iSCSI Connection in RedHat 5 Using the iscsiadm Command 5.11
3PAR RedHat 4 and RedHat 5 Implementation Guide
5.4 Configuring CHAP for the iSCSI Host 5.14
5.4.1 Setting the Host CHAP Authentication on the InServ Storage Server 5.14
8/11/2019 3par RedHat 45 Implementation Guide
58/132
5.2 Setting Up the Ethernet Switch and Network Interface Card3PAR Confidential
5.4.2 Setting Up the Bidirectional CHAP on the InServ Storage Server 5.17
5.1 Setting Up the Ethernet Switch and Network Interface Card
Connect the Linux host Ethernet cable and the InServ iSCSI target ports Ethernet cables to the
Ethernet switches.
If you are using VLANs, make sure that the switch ports which connect to the InServ iSCSItarget ports and iSCSI Initiator ports reside in the same VLANs and/or that you can route the
iSCSI traffic between the iSCSI Initiator ports and the InServ iSCSI target ports. Once the iSCSI
Initiator and InServ iSCSI target ports are configured and connected to the switch, you can use
the pi ngcommand on the iSCSI Initiator host to make sure it sees the InServ iSCSI target ports.
The procedures in this chapter assumes the you have completed the following tasks:
Set up and configuration of the host Network Interface Card (NIC) that will be used by the
iSCSI Initiator software to connect to the InServ iSCSI target ports.
Installation of the iSCSI Initiator software package.
5.2 Configuring RedHat 4 for iSCSI
This section discusses the necessary tasks for setting up iSCSI for RedHat 4.
5.2.1 Installing iSCSI on RedHat 4
Install the iSCSI initiator software package if it has not been installed. The software package
can be installed from the respective Service Pack distribution CDs of your RedHat 4 OS version
using the RPM tool.
NOTE: Ethernet switch VLANs and routing setup and configuration is beyond thescope of this document. Please consult your switch manufacturer's Guide for
instructions of how to setup VLANs and routing.
3PAR RedHat 4 and RedHat 5 Implementation Guide
5.2.2 Setting Up iSCSI for RedHat 4
Complete the following steps to setup the RedHat 4 iSCSI host:
8/11/2019 3par RedHat 45 Implementation Guide
59/132
5.3Configuring RedHat 4 for iSCSI3PAR Confidential
1 Check state of the iSCSI service run level information with the chkconf i gcommand.
# chkconf i g - - l i st | grep i scsi
i scsi 0: of f 1: of f 2: of f 3: of f 4: of f 5: of f 6: of f
2 Check your system run level.
# runl evel
N 5
3 Configure the iSCSI service run level the same as your system run level and verify that the
setting for the run level has changed. Now, every time you boot up the system, the iSCSIservice will run.
# chkconf i g - - l evel 5 i scsi on
# chkconf i g - - l i st | grep i scsi
i scsi 0: of f 1: of f 2: on 3: on 4: on 5: on 6: of f
4 Edit the / et c/ i scsi . conffile and at the end of the file add the following lines to
configure the InServ iSCSI target port to connect to. In this example we are adding an iSCSI
target port with an IP address of 10.0.0.10 and 10.0.0.20
ConnFai l Ti meout =10
Di scoveryAddress=10. 0. 0. 10
Di scoveryAddress=10. 0. 0. 20
5 Reload the iscsi service:
# / etc/ i ni t . d/ i scsi r el oad
/ etc/ i ni t . d/ i scsi rel oad
6 Make sure that the mul t i pat hddaemon is not running. If it is, you can stop it by running
the script / et c/ i ni t . d/ mul t i pat hd stop.
# / et c/ i ni t . d/ mul t i pat hd stat us
mul t i pat hd i s st opped
NOTE: Dynamic Driver Reconfiguration: Configuration changes can be made to
the iSCSI driver without having to stop it or to reboot the host system. To
dynamically change the configuration of the driver, insert the /etc/init.d/iscsi
reload to the /etc/iscsi.conf file. This will cause the iSCSI daemon to re-read the
iscsi.conf file and to create any new Discovery Address connections it finds. Those
discovery sessions will then discover targets and create new target connections.
3PAR RedHat 4 and RedHat 5 Implementation Guide
7 Verify that the module i scsi _sf net is not loaded.
# l smod | grep i scsi _sf net
8 Connect to the InServ iSCSI target port by running the script / etc/ i ni t . d/ i scsi that
8/11/2019 3par RedHat 45 Implementation Guide
60/132
5.4 Configuring RedHat 4 for iSCSI3PAR Confidential
loads the module i scsi _sf net and starts the iSCSI daemon.# / etc/ i ni t . d/ i scsi star tChecki ng i scsi conf i g: [ OK ]
Loadi ng i scsi dr i ver : [ OK ]
St ar t i ng i scsi d: [ OK ]
9 Verify that the module i scsi _sf net has been loaded.
# l smod | grep i scsi _sf net
i scsi _sf net 96093 26scsi _t ranspor t _i scsi 14017 1 i scsi _sf net
scsi _mod 145297 7
i scsi _sf net , l pf c, l i bat a, cci ss, ql a2xxx, scsi _t ranspor t _f c, sd_mod
5.2.3 Configuring RedHat 4 iSCSI Settings with Device Mapper Multipathing
The / et c/ mul t i pat h. conffile is used by device mapper where the multipathing
parameters have been set. The default installed / et c/ mul t i path. conffile must be editedwith the following changes for a minimum configuration connecting to a 3PAR array. Entries
listed in mul t i pat h. confoverride the default kernel parameters for dm- mul t i path.
In general, the kernel defaults are sufficient with the exception of the devices entries for 3PAR.
1 Remove or comment out all entries in the / et c/ mul t i path. conffile except for the
devices section of devices currently in use.
2 Edit the devices structure to add entries for 3PAR array and remove other product entries
that are not needed.
NOTE: Refer to RedHat documentation of DM Multipath Configuration and
Administration for additional options in mul t i pat h. confentries.
NOTE: Refer to 4.5.1 Setting Up Device Mapperon page 4.18for the installation
of the device mapper rpm packages.
3PAR RedHat 4 and RedHat 5 Implementation Guide
3 Verify that /etc/multipath.conf file contains the following content:
# cat / et c/ mul t i path. confdevi ces {
8/11/2019 3par RedHat 45 Implementation Guide
61/132
5.5Configuring RedHat 4 for iSCSI3PAR Confidential
4 Run the mul t i pathcommand for any name changes to be effective.
5 Verify that the mul t i pathddaemon is enabled by the rc script to run on every host bootup.
The following output shows that it is enabled for run-level 3, 4 and 5. Enable it appropriately
for your configuration.
6 Check that the appropriate rc scripts have been created for each run level. The start
numbers may not match those shown here.
Alternatively, you can use the chkconf i gcommand to enable multipathing if it is not
enabled:
# chkconf i g mul t i pathd on
devi ces {
devi ce { vendor "3PARdata" product "VV" pol l i ng_i nterval 5 no_path_r etr y 12 f eatures "0" hardware_handl er "0" path_groupi ng_pol i cy mul t i bus path_sel ector "r ound- robi n 0" r r _wei ght uni f orm
rr _mi n_i o 100 path_checker t ur f ai l back i mmedi ate }}
# chkconf i g - - l i st mul t i pat hdmul t i pat hd 0: of f 1: of f 2: of f 3: on 4: on 5: on 6: of f
# l s / et c/ rc3. d/ *mul t i */ et c/ r c3. d/ S13mul t i pathd# l s / et c/ rc5. d/ *mul t i *
/ et c/ r c5. d/ S13mul t i pathd
3PAR RedHat 4 and RedHat 5 Implementation Guide
5.2.4 Starting the iSCSI Daemon for RedHat 4
Complete the following steps to start the iSCSI daemon for the host running RedHat 4.
8/11/2019 3par RedHat 45 Implementation Guide
62/132
5.6 Configuring RedHat 4 for iSCSI3PAR Confidential
1 Remove and reload the i scsi _sf net driver with the rc script.
# / etc/ i ni t . d/ i scsi r estart
St oppi ng i scsi d: [ OK ]Removi ng i scsi dr i ver : [ OK ]
Checki ng i scsi conf i g: [ OK ]
Loadi ng i scsi dr i ver : [ OK ]
St ar t i ng i scsi d: [ OK ]
# i s c s i - l s
2 Check to see if the i scsi ddaemon is running by using the script / etc/ i ni t . d/ i scsi
status.
# / etc/ i ni t . d/ i scsi status
i scsi d ( pi d 30532 30529) i s r unni ng. . .
If the daemon is running, stop it with the script / etc/ i ni t . d/ i scsi stop.
# / etc/ i ni t . d/ i scsi stop
St oppi ng i scsi d: [ OK ]Removi ng i scsi dr i ver : [ OK ]
If the i scsi ddaemon in not running, start it with the script / etc/ i ni t . d/ i scsi to
establish an iSCSI connection to the iSCSI target ports.
# / etc/ i ni t . d/ i scsi star t
Checki ng i scsi conf i g: [ OK ]
Loadi ng i scsi dr i ver : [ OK ]
St ar t i ng i scsi d: [ OK ]
NOTE: Since volumes are exported to the host for the first time after the iSCSI
driver has been loaded with the rc script, you must remove and reload the iscsi
driver to discover the volumes being exported.
3PAR RedHat 4 and RedHat 5 Implementation Guide
5.3 Configuring RedHat 5 for iSCSI
8/11/2019 3par RedHat 45 Implementation Guide
63/132
5.7Configuring RedHat 5 for iSCSI3PAR Confidential
5.3.1 Installing iSCSI on RedHat 5iSCSI is installed through the i scsi - i ni t i ator -ut i l sdriver and rpm package by default
during the RedHat installation. There are a couple of ways to configure and start i scsi -
i ni t i ator - ut i l s on RedHat: either by using the various i scsi - i ni t i ator - ut i l s
available from the CLI or through the UI.
In this document, we will be referencing the i scsi - i ni t i ator -ut i l sfrom the CLI. The
i scsi admutility is a command-line tool that allows discovery and login to iSCSI targets. Thistool also provides access and management of the open- i scsi database. The following steps
are required to discover LUNs:
1 Discover targets at a given IP address.
2 Establish iSCSI login with node record id found in the discovery process.
3 Record iSCSI session statistics information.
5.3.2 Setting Up iSCSI for RedHat 5
You can adjust the iSCSI timers for better SAN performance. iSCSI timers and session
parameters are specified in / etc/ i scsi / i scsi d. conffile.
The r epl acement _t i meout iSCSI timeout parameter prevents I/O errors from propagating to
the application by controlling how long the iSCSI layer should wait for a timed-out path/session to reestablish itself before failing any commands on it. The default
r epl acement _t i meout value is 120 seconds.
To adjust replacement_timeout, complete the following steps:
1 Open / etc/ i scsi / i scsi d. confand edit the following line:
node. sessi on. t i meo. repl acement _t i meout = [ repl acement_t i meout ]
2 Set this parameter to 5 seconds for a faster failover.
node. sessi on. t i meo. repl acement _t i meout = 5
3 Change the time interval to wait for a connection before sending a pi ng.
node.conn[0].timeo.noop_out_interval = [repl acement _t i meout ]
This allows connections that were broken to be re-established before a pi ngis sent out (in
case of a bad cable or a broken Ethernet link).
3PAR RedHat 4 and RedHat 5 Implementation Guide
4 Set this parameter to 10 seconds for a ping to succeed after a connection is made.
node. conn[ 0] . t i meo. noop_out _i nt erval = 10
5 To set the host log into the iSCSI nodes every time the iSCSI daemon is started or the host is
b t d dit th iSCSI fi ti i / et c/ i scsi / i scsi d conf d h th
8/11/2019 3par RedHat 45 Implementation Guide
64/132
5.8 Configuring RedHat 5 for iSCSI3PAR Confidential
rebooted, edit the iSCSI configuration in / et c/ i scsi / i scsi d. confand change the
values of the following default settings:
node. st ar t up = aut omat i c
node. conn[ 0] . st art up = aut omat i c
6 Check the state of the iscsi service run level with the chkconf i gcommand:
# chkconf i g - - l i st | grep i scsi
i scsi 0: of f 1: of f 2: of f 3: of f 4: of f 5: of f 6: of f
i scsi d 0: of f 1: of f 2: of f 3: on 4: on 5: on 6: of f
7 Verify that Run l evel 5is turned on. If not turned on, issue the following commands:
# chkconf i g i scsi on# chkconf i g - - l i st| grep i scsi
i scsi 0: of f 1: of f 2: on 3: on 4: on 5: on 6: of f
i scsi d 0: of f 1: of f 2: of f 3: on 4: on 5: on 6: of f
8 To prevent one host from using up all the I/O buffers, you will need to throttle the host I/O
by reducing the node.session.cmds_maxand node. sessi on. queue_dept hvalues.
The following values were determined based on the multihost-to-single InServ Storage Serverport testing completed at the 3PAR test labs and may require further tuning for your particular
configuration.
node. sessi on. cmds_max = 32
node. sessi on. queue_dept h = 8
9 As an option, you can also enable the Header and Data Digest for error handling and
recovery within the connection.
NOTE: The node. conn[0] .startup variable is optional and not define