IBM XIV Host Attachment Guide

IBM XIV Host Attachment Kit
Version 1.10.0
Host Attachment Guide
GA32-1060-05
Note
Before using this document and the product it supports, read the information in “Notices” on page 75.
Edition notice
Publication number: GA32-1060-05. This publication applies to version 1.10.0 of the IBM XIV Host Attachment Kit
and to all subsequent releases and modifications until otherwise indicated in a newer publication.
© Copyright IBM Corporation 2009, 2012.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Summary of changes . . . . . .
Who should use this guide . . . .
Conventions used in this guide . . .
Related documentation . . . . .
Getting information, help, and service
Ordering publications. . . . . .
Sending your comments . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. xi
. xi
. xi
. . . . . . . . . . . . . . . . . . . . . . . . . . xii
. . . . . . . . . . . . . . . . . . . . . . . . . . xiii
. . . . . . . . . . . . . . . . . . . . . . . . . . xiii
. . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Why use the host attachment kit?
Connectivity types . . . . .
Concept diagram . . . . . .
Compatibility and requirements .
The workflow . . . . . . .
Download site . . . . . . .
Before you proceed . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
1
1
2
2
3
3
Chapter 2. Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Stage 1: Physically connecting the host to the XIV storage system. . . . .
Option 1: Using Fibre Channel (FC) connections . . . . . . . . .
Option 2: Using iSCSI connections . . . . . . . . . . . . . .
Stage 2: Setting connectivity parameters . . . . . . . . . . . . .
Overview of Fibre Channel zoning . . . . . . . . . . . . . .
Identifying and checking Fibre Channel ports on the XIV storage system .
Overview of iSCSI settings . . . . . . . . . . . . . . . .
Configuring iSCSI ports on the XIV storage system . . . . . . . .
Using CHAP authentication for iSCSI connectivity . . . . . . . .
Stage 3: Preparing the host . . . . . . . . . . . . . . . . .
Validating the system requirements . . . . . . . . . . . . .
Validating your admin user privileges . . . . . . . . . . . .
Optional: booting the operating system from a storage area network (SAN)
Preparing AIX hosts (if applicable) . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
6
7
8
8
9
11
12
14
15
15
16
17
17
Chapter 3. Software installation . . . . . . . . . . . . . . . . . . . . . . . . . 19
Option 1: Performing a clean local installation . . . .
Installing on AIX, HP-UX, Linux, or Solaris. . . .
Installing on Windows Server . . . . . . . .
Option 2: Upgrading from a previous local installation .
Option 3: Using the portable package without installing
Using a mounted network drive . . . . . . .
Using a portable USB flash drive . . . . . . .
Removing the Host Attachment Kit software . . . .
Detaching the host and uninstalling the software . .
Uninstalling the software without detaching the host
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
20
20
21
24
25
25
26
26
26
27
Chapter 4. Single host attachment . . . . . . . . . . . . . . . . . . . . . . . . 29
Stage 1: Using the CLI attachment utility (xiv_attach) . . . .
Stage 2: Defining the host on the XIV storage system (optional) .
Defining a host from the XIV GUI . . . . . . . . . .
© Copyright IBM Corp. 2009, 2012
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 29
. 33
. 33
iii
Defining a host from the XCLI . . . .
Adding ports to a host . . . . . .
Stage 3: Mapping XIV volumes to the host .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 35
. 35
. 36
Chapter 5. Cluster host attachment . . . . . . . . . . . . . . . . . . . . . . . 39
Cluster installation prerequisites . . . . . . . . .
Stage 1: Defining the cluster on the XIV storage system .
Defining a cluster from the XIV GUI . . . . . . .
Defining a cluster from the XCLI . . . . . . . .
Stage 2: Mapping XIV volumes to the cluster . . . . .
Mapping shared volumes to all the hosts in a cluster .
Mapping private volumes to a specific host in a cluster.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
40
40
41
43
43
43
44
Chapter 6. Additional tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Displaying information of connected XIV systems . . . .
Displaying volume and additional information . . . . .
Displaying XIV and non-XIV volumes . . . . . . .
Displaying additional information . . . . . . . . .
Setting Fibre Channel connectivity parameters . . . . . .
Setting iSCSI connectivity parameters. . . . . . . . .
Displaying information about host configuration changes . .
Displaying information for xiv_fc_admin or xiv_iscsi_admin
Displaying information when working with xiv_attach . .
Performing diagnostics . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
48
50
50
51
52
54
56
56
57
58
Chapter 7. Best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Recommended operating system settings . . . . . .
Monitoring host connectivity from the XIV GUI and XCLI.
Monitoring from the XIV GUI . . . . . . . . .
Monitoring from the XCLI . . . . . . . . . .
Using the rescan (-R) option after new volumes are mapped
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
61
61
61
62
62
Chapter 8. Summary of changes applied on the host . . . . . . . . . . . . . . . . 65
Changes applied on a Linux host . .
Multipath configuration . . . .
Multipath service(s) . . . . .
iSCSI daemon configuration . . .
iSCSI initiator name . . . . .
iSCSI service . . . . . . . .
Changes applied on a Windows Server
Removal of previous HAK versions
LUN0 device driver . . . . .
Disk timeout setting . . . . .
iSCSI service . . . . . . . .
XIV MPIO Load Balancing service .
XIV MPIO Load Balancing agent .
Built-in MPIO feature . . . . .
DSM driver . . . . . . . .
Persistent reservation key. . . .
. .
. .
. .
. .
. .
. .
host
. .
. .
. .
. .
. .
. .
. .
. .
. .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
65
65
66
66
66
66
66
67
67
67
67
68
68
68
68
68
Chapter 9. XIV and VMware ESX or ESXi hosts . . . . . . . . . . . . . . . . . . 69
Choosing ESX configurations .
Fibre Channel SAN zoning . .
iSCSI target discovery . . . .
Multipathing and load balancing
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
69
69
70
71
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Trademarks .
iv
.
.
.
.
.
.
.
IBM XIV Host Attachment Guide
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 77
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Contents
v
vi
IBM XIV Host Attachment Guide
Figures
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
A host connected to the IBM XIV Storage System . . .
The workflow . . . . . . . . . . . . . . .
Preparation . . . . . . . . . . . . . . . .
Fibre Channel host connectivity . . . . . . . . .
iSCSI host connectivity . . . . . . . . . . . .
FC zoning: single initiator with multiple targets . . . .
Backview arrow in the XIV GUI. . . . . . . . .
Viewing FC port details . . . . . . . . . . .
XIV GUI - Hosts and Clusters - iSCSI Connectivity . .
XIV GUI - iSCSI connectivity table . . . . . . . .
XIV GUI - Define IP Interface - iSCSI . . . . . . .
Software installation . . . . . . . . . . . .
Installation Wizard - Ready to install the program . .
Single host attachment . . . . . . . . . . . .
XIV GUI - Hosts and Clusters . . . . . . . . .
XIV GUI - Hosts and Clusters table . . . . . . .
XIV GUI - Add host dialog box . . . . . . . . .
XIV GUI - Add Port dialog box . . . . . . . . .
XIV GUI - Modifying LUN Mapping to a host . . . .
XIV GUI - Modifying LUN Mapping . . . . . . .
Cluster host attachment . . . . . . . . . . .
A cluster connected to the IBM XIV Storage Systems . .
Add Cluster dialog box . . . . . . . . . . .
XIV GUI - Cluster added to the Hosts and Clusters table
XIV GUI - Add to Cluster . . . . . . . . . . .
XIV GUI - Add Host(s) to Cluster dialog box . . . .
XIV GUI - Host added to a cluster . . . . . . . .
XIV GUI - Modify LUN Mapping to a cluster . . . .
XIV GUI - Modify LUN Mapping . . . . . . . .
Right-clicking a specific host of a cluster . . . . . .
Additional tasks . . . . . . . . . . . . . .
XIV GUI - Hosts Connectivity . . . . . . . . .
XIV GUI - Hosts Connectivity table . . . . . . .
SAN Fibre Channel zoning layout . . . . . . . .
Connecting ESX servers over iSCSI. . . . . . . .
© Copyright IBM Corp. 2009, 2012
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2
. 3
. 5
. 6
. 7
. 9
. 10
. 11
. 13
. 13
. 13
. 19
. 23
. 29
. 34
. 34
. 34
. 35
. 36
. 37
. 39
. 40
. 41
. 41
. 42
. 42
. 43
. 44
. 44
. 45
. 47
. 62
. 62
. 70
. 71
vii
viii
IBM XIV Host Attachment Guide
Tables
1.
2.
3.
4.
5.
6.
7.
8.
9.
Summary of changes in the Host Attachment Guide publications .
Primary settings for proper iSCSI connectivity . . . . . . .
Optional CLI arguments for unattended (silent) installation . .
Optional arguments for xiv_syslist . . . . . . . . . .
Optional arguments for xiv_devlist . . . . . . . . . .
Arguments for xiv_fc_admin . . . . . . . . . . . . .
Arguments for xiv_iscsi_admin. . . . . . . . . . . .
ESX configurations . . . . . . . . . . . . . . . .
Initiators and targets in the SAN Fibre Channel zoning layout .
© Copyright IBM Corp. 2009, 2012
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. xi
. 12
. 24
. 49
. 51
. 53
. 55
. 69
. 70
ix
x
IBM XIV Host Attachment Guide
About this guide
This guide describes how to prepare for, install, and use the IBM® XIV® Host
Attachment Kit (HAK).
Summary of changes
This topic provides a summary of changes made in the different publications of
this document.
Table 1. Summary of changes in the Host Attachment Guide publications
Publication
Changes
GA32-1060-00
A brand new and unified guide that covers version 1.7.0 of the
IBM XIV Host Attachment Kit and all the supported operating
systems.
GA32-1060-01
Updates, fixes, and enhancements for version 1.7.1 of the IBM
XIV Host Attachment Kit.
GA32-1060-02
v Conversion to a DITA-based guide and changing the look
and feel of the guide.
v Updates for version 1.8.0 of the IBM XIV Host Attachment
Kit.
GA32-1060-03
v Editorial fixes.
v The OS logos are replaced with generic OS cues.
GA32-1060-04
Updates and fixes for version 1.9.0 of the IBM XIV Host
Attachment Kit.
GA32-1060-05 (this
publication)
Updates and fixes for version 1.10.0 of the IBM XIV Host
Attachment Kit.
Who should use this guide
This guide is intended for system administrators who are familiar with the IBM®
XIV Storage System and with the specific operating system that is used on their
host(s).
Conventions used in this guide
The following notices are used to highlight key information in this guide.
Note: These notices provide important tips, guidance, or advice.
Important: These notices provide information or advice that might help you avoid
inconvenient or difficult situations.
Attention: These notices indicate possible damage to programs, devices, or data.
An attention notice appears before the instruction or situation in which damage
can occur.
© Copyright IBM Corp. 2009, 2012
xi
AIX users
Note: These notices provide information that is
relevant only to the IBM AIX® operating system.
HP-UX users
Note: These notices provide information that is
relevant only to the HP UNIX operating system.
Linux users
Note: These notices provide information that is
relevant only to the Linux operating system.
Solaris users
Note: These notices provide information that is
relevant only to the Oracle Solaris operating
system.
Windows Server users
Note: These notices provide information that is
relevant only to the Microsoft Windows Server
operating system.
Related documentation
You can find additional information and publications related to the IBM XIV Host
Attachment Kit on the following web addresses.
v IBM XIV Host Attachment Kit, Release Notes®, available under Host connectivity
on the IBM Storage Host Software Solutions Information Center
(publib.boulder.ibm.com/infocenter/strhosts/ic/index.jsp)
v IBM XIV Storage System – Product Overview, Planning Guide, available under
Publications on the IBM XIV Storage System Information Center
(publib.boulder.ibm.com/infocenter/ibmxiv/r2/index.jsp)
Depending on the operating system you are using on the host, refer to the
following publications and information sources.
Operating system
Related publications and information sources
AIX
IBM Power Systems™ software website for AIX
(www.ibm.com/systems/power/software/aix)
HP-UX
HP-UX 11i website (h71028.www7.hp.com/enterprise/us/en/os/
hpux11i-overview.html)
Linux
v IBM and Linux website (www.ibm.com/linux)
v Linux by RedHat (www.redhat.com/rhel)
v Linux by SUSE (www.suse.com)
xii
IBM XIV Host Attachment Guide
Operating system
Related publications and information sources
Solaris
v Oracle Solaris Patching Documentation Center
(www.oracle.com/technetwork/systems/patches/solaris)
v Oracle Solaris documentation (www.oracle.com/technetwork/
documentation/index.html#sys_sw)
v Oracle Solaris Online Forum (www.oracle.com/us/products/
servers-storage/solaris)
Windows Server
v Microsoft TechNet website for Windows Server
(technet.microsoft.com/en-us/windowsserver)
v Microsoft Windows Server TechCenter (technet.microsoft.com/
en-us/library/bb625087.aspx)
Getting information, help, and service
If you need help, service, technical assistance, or want more information about IBM
products, you can find various sources to assist you. You can view the following
websites to get information about IBM products and services and to find the latest
technical information and support.
v IBM website (ibm.com®)
v IBM Support Portal website (www.ibm.com/storage/support)
v IBM Directory of Worldwide Contacts website (www.ibm.com/planetwide)
Ordering publications
The IBM Publications Center is a worldwide central repository for IBM product
publications and marketing material.
The IBM Publications Center website (www.ibm.com/shop/publications/order/)
offers customized search functions to help you find the publications that you need.
Some publications are available for you to view or download at no charge. You can
also order publications. The publications center displays prices in your local
currency.
Sending your comments
Your feedback is important in helping to provide the most accurate and highest
quality information.
Procedure
To submit any comments about this guide or any other IBM Storage Host Software
documentation:
v Go to the online feedback form (http://pic.dhe.ibm.com/infocenter/strhosts/ic/
topic/com.ibm.help.strghosts.doc/icfeedback.htm). You can use this form to
enter and submit comments.
v You can send your comments by email to starpubs@us.ibm.com. Be sure to
include the following information:
– Exact publication title and version
– Publication form number (for example: GC00-1111-22)
– Page, table, or illustration numbers that you are commenting on
– A detailed description of any information that should be changed
About this guide
xiii
Note: When you send information to IBM, you grant IBM a nonexclusive right
to use or distribute the information in any way it believes appropriate without
incurring any obligation to you.
xiv
IBM XIV Host Attachment Guide
Chapter 1. Introduction
The IBM XIV Host Attachment Kit (HAK) is a software pack that simplifies the
task of connecting a host computer to the IBM XIV Storage System.
The HAK provides a set of command-line interface (CLI) tools that help you
perform different host-side tasks, such as: detect any physically connected XIV
storage system (single system or multiple systems), detect XIV volumes, define the
host on the XIV storage system, run diagnostics, and apply best practice native
multipath connectivity configuration on the host.
After the host connection is established, XIV storage volumes can be mapped to
the host without any additional configuration, and can be accessed and used from
the host for a range of storage operations.
Why use the host attachment kit?
Host I/O operations must be equitably distributed among the XIV interface
modules.
Although the IBM XIV Storage System distributes the traffic between its I/O and
data modules, it is the responsibility of the storage administrator to ensure that
host I/O operations are equitably distributed among the XIV interface modules.
This workload balance must be monitored and assessed over time when host
traffic patterns change.
Accordingly, each host must be properly configured before it can perform I/O
operations on the IBM XIV Storage System, and the HAK provides the host
administrator with all the required tools for automatic and simpler host
configuration. In addition, the HAK facilitates the monitoring and management of
XIV-based storage volumes from the host.
Connectivity types
You can connect hosts to the IBM XIV Storage System using Fibre Channel (FC) or
iSCSI connections, depending on the following conditions:
v The operating system used on the host. Some operating systems support only a
specific connection type (for more information, refer to the HAK release notes
issued for the operating system).
v The connectivity hardware that is installed or available on the host. FC
connectivity requires a host bus adapter (HBA), and iSCSI connectivity requires
an Ethernet or Gigabit Ethernet port.
Concept diagram
Refer to the following graphic illustration to better grasp the concept of host
connection.
Figure 1 on page 2 illustrates how a host on which the HAK is installed connects
over Fibre Channel (FC) or iSCSI to the IBM XIV Storage System. The host may be
using IBM AIX, HP UNIX, Linux, Oracle Solaris, or Microsoft Windows Server as
its operating system, which can either be installed locally or booted from a storage
© Copyright IBM Corp. 2009, 2012
1
area network (SAN). The HAK helps detect the XIV storage system, as well as any
volume that is available for use by the host.
Figure 1. A host connected to the IBM XIV Storage System
Note: Starting from version 1.7.0, the HAK does not have to be locally installed on the host.
For more information, refer to Chapter 3, “Software installation,” on page 19.
Compatibility and requirements
For the complete and up-to-date information about the compatibility and
requirements of the IBM XIV Host Attachment Kit, refer to the latest release notes
issued for the HAK version and the specific operating system that you are using.
You can obtain the latest release notes on the IBM Storage Host Software Solutions
Information Center (publib.boulder.ibm.com/infocenter/strhosts/ic/index.jsp).
The workflow
The workflow includes preparation, installation, host attachment, and additional
tasks.
2
IBM XIV Host Attachment Guide
Each stage in this workflow has its own chapter in this guide, as illustrated in
Figure 2.
Figure 2. The workflow
Download site
The IBM XIV Host Attachment Kit is available for download from the IBM Fix
Central (www.ibm.com/support/fixcentral).
Before you proceed
Before you proceed to the Preparation stage in the workflow, you must have access
to a workstation on which your preferred IBM XIV Storage System management
software is locally installed or accessible via a remote connection.
You can manage the IBM XIV Storage System using the XIV GUI (graphical user
interface) or XIV CLI (command-line interface; also referred to as XCLI).
For additional assistance and more information on how to obtain, install, and use
the IBM XIV Storage System management software, refer to the IBM XIV Storage
System Information Center (publib.boulder.ibm.com/infocenter/ibmxiv/r2).
Chapter 1. Introduction
3
4
IBM XIV Host Attachment Guide
Chapter 2. Preparation
Before you can install and use the IBM XIV Host Attachment Kit, preparation
actions may be required.
Figure 3. Preparation
The following preparation stages are required:
v Stage 1: Physically connecting the host to the XIV storage system
v Stage 2: Setting connectivity parameters
v Stage 3: Preparing the host
Note: Perform these preparation stages only once per host or cluster. If you have
already performed these preparation stages, skip to Chapter 3, “Software
installation,” on page 19.
Stage 1: Physically connecting the host to the XIV storage system
Any host on which you intend to use the HAK must be physically connected to
the XIV storage system.
Depending on the hardware configuration and the operating system that is used
on the host, use one of the following options to physically connect your host to the
XIV storage system:
v Option 1: Using Fibre Channel (FC) connections
v Option 2: Using iSCSI connections
Attention: Although you can use both FC and iSCSI to connect different hosts to
the same IBM XIV storage system, use only one connection type per single host or
cluster to avoid possible issues.
© Copyright IBM Corp. 2009, 2012
5
Option 1: Using Fibre Channel (FC) connections
The Fibre Channel (FC) protocol (FCP) is used to establish connectivity over FC
infrastructure.
Hosts can be connected to the XIV storage system via a private FC storage fabric,
through an FC switch (not via a direct connection).
For the physical connection on the host side, install at least one host bus adapter
(HBA) on the host. The HBA provides physical FC ports to which you can connect
FC cables. The IBM XIV Host Attachment Kit supports different HBA brands and
types. For the latest support information and compatibility matrix, refer to the IBM
System Storage® Interoperation Center website (www.ibm.com/systems/support/
storage/config/ssic).
Note:
v Fibre Channel is supported by all the operating systems for which the Host
Attachment Kit is released (AIX, HP-UX, Linux, Solaris, or Windows Server).
v For best performance, install the latest firmware and drivers for the HBAs that
are in use. The HBA vendor should provide the latest firmware and drivers.
Figure 3 illustrates how a single host is connected to the IBM XIV Storage System
using an FC switch and FC connections (FCP stands for Fibre Channel Protocol).
Figure 4. Fibre Channel host connectivity
Important: A high availability (HA) configuration is the best practice for FC
connectivity. For best performance, use a dedicated FC connectivity infrastructure.
For additional information on how to physically connect your host(s) to the XIV
storage system over Fibre Channel, refer to the following documents:
6
IBM XIV Host Attachment Guide
v Network requirements chapter in IBM XIV Planning Guide, available on the IBM
XIV Storage System Information Center (publib.boulder.ibm.com/infocenter/
ibmxiv/r2).
v IBM XIV Storage System – Host Attachment and Interoperability
(www.redbooks.ibm.com/abstracts/sg247904.html), available on the IBM Storage
Redbooks® website (www.redbooks.ibm.com/redbooks.nsf/portals/storage).
Option 2: Using iSCSI connections
The iSCSI protocol is used to establish connectivity over Ethernet infrastructure.
Hosts can be connected to the XIV storage system via a private Ethernet-based
LAN or WAN, through an Ethernet switch (not via a direct connection).
AIX users
Note: The IBM XIV Host Attachment Kit for AIX
does not support iSCSI connectivity. Only FC
connectivity is supported on AIX (see Option 1:
Using FC connections).
HP-UX users
Note: The IBM XIV Host Attachment Kit for
HP-UX does not support iSCSI connectivity. Only
FC connectivity is supported on HP-UX (see
Option 1: Using FC connections).
Figure 4 illustrates how a single host is connected to the IBM XIV Storage System
using an Ethernet switch and Gigabit Ethernet (GbE) connections.
Figure 5. iSCSI host connectivity
Important: A high availability (HA) configuration is the best practice for iSCSI
connectivity. For best performance, use a dedicated iSCSI connectivity
infrastructure.
Chapter 2. Preparation
7
For additional information on how to physically connect your host(s) to the XIV
storage system over Ethernet-based networks, refer to the following documents:
v Network requirements chapter in IBM XIV Planning Guide, available on the IBM
XIV Storage System Information Center (http://publib.boulder.ibm.com/
infocenter/ibmxiv/r2).
v IBM XIV Storage System – Host Attachment and Interoperability
(www.redbooks.ibm.com/abstracts/sg247904.html), available on the IBM Storage
Redbooks website (www.redbooks.ibm.com/redbooks.nsf/portals/storage).
Stage 2: Setting connectivity parameters
After you physically connect your host or cluster to the IBM XIV Storage System,
you must ensure that the connection type (FC or iSCSI) is properly defined on the
XIV storage system.
Depending on the connection type that you are using, refer to the following
subsections:
v Overview of Fibre Channel zoning
v Identifying and checking Fibre Channel ports on the XIV storage system
v Overview of iSCSI settings
v Configuring iSCSI ports on the XIV storage system
Overview of Fibre Channel zoning
Zoning is a connection isolation technique that is required when connecting hosts
with the XIV storage system over Fibre Channel SAN.
Zoning achieves the following:
v Creates a barrier between different network environments. Only the members of
the same zone can communicate within that zone, and all external
communications are blocked.
v Isolates any single host bus adapter (HBA) for security and reliability reasons.
v Allows finer segmentation of the switched fabric.
With proper zoning, you can avoid the following situations:
v HBAs of different vendors operate differently upon error recovery. This may
impact other hosts connected to the same switch if those are not isolated
through zoning.
v Any change in the SAN fabric, such as a change caused by a server restart or a
new product being added to the SAN – triggers a registered state change
notification (RSCN). An RSCN requires any change-aware device to
acknowledge the change while interrupting its own traffic flow.
The most secure zoning is to have zones that consist of a single initiator and
multiple targets, as illustrated in Figure 6 on page 9 (see zones 1, 2, 3, and 4).
8
IBM XIV Host Attachment Guide
Figure 6. FC zoning: single initiator with multiple targets
Attention: Do not configure more than 24 logical paths per host, as this may
impact overall stability. There is no advantage in configuring more than 24 logical
paths.
For additional information about zoning, refer to IBM XIV Storage System – Host
Attachment and Interoperability (www.redbooks.ibm.com/abstracts/sg247904.html),
available on the IBM Storage Redbooks website (www.redbooks.ibm.com/
redbooks.nsf/portals/storage).
Identifying and checking Fibre Channel ports on the XIV
storage system
Before you can set the FC zoning for your hosts and XIV storage system (see
Overview of Fibre Channel zoning), the FC ports on the XIV storage system must
be identified.
Fibre Channel ports are identified by their World Wide Port Name (WWPN).
Use the XIV GUI or the XCLI (XIV CLI) to determine the FC port WWPNs, and
also to check that the FC ports are set up correctly.
To identify the FC ports from the XIV GUI:
1. Log in to the IBM XIV GUI management application and zoom into the IBM
XIV Storage System that you want to configure.
2. From the main view of an IBM XIV Storage System, click the Backview arrow
at the bottom of the IBM XIV Storage System to reveal the patch panel on the
back.
Chapter 2. Preparation
9
Figure 7. Backview arrow in the XIV GUI
The back patch panel is displayed.
3. Move the mouse pointer over any particular FC port to reveal the port details,
including the WWPN.
10
IBM XIV Host Attachment Guide
Figure 8. Viewing FC port details
Alternatively, to identify the FC ports from the XIV CLI (XCLI), enter the following
command:
fc_port_list [ module=ComponentId | fcport=ComponentId ]
Note:
v The WWPNs of an IBM XIV Storage System are static. The last two digits of the
WWPN indicate from which module and port the WWPN came.
v By default, port number 4 of each interface module is configured as an initiator.
Overview of iSCSI settings
The IBM XIV Storage System acts as a Transmission Control Protocol (TCP) server
for iSCSI connections.
All iSCSI packets are routed through the Ethernet port from which the iSCSI
connection was initiated.
AIX users
Note: The IBM XIV Host Attachment Kit for AIX
does not support iSCSI connectivity. Only FC
connectivity is supported on AIX (see Overview of
Fibre Channel zoning).
Chapter 2. Preparation
11
HP-UX users
Note: The IBM XIV Host Attachment Kit for
HP-UX does not support iSCSI connectivity. Only
FC connectivity is supported on HP-UX (see
Overview of Fibre Channel zoning).
The following table specifies the primary settings that must be configured on the
IBM XIV Storage System for proper iSCSI connectivity with the host.
Table 2. Primary settings for proper iSCSI connectivity
Setting type
Configuration on the XIV storage system
iSCSI qualified name
(IQN)
Required for each host that uses iSCSI to connect to the XIV
storage system. The IQN uniquely identifies the different
entities that utilize iSCSI on the IP network, and enables the
operation of the iSCSI initiator.
The IQN of the IBM XIV Storage System is a preconfigured
factory setting that cannot be changed.
IP interface
iSCSI uses IP-based communication. On the IBM XIV Storage
System, each iSCSI port is defined as an IP interface with its
own IP address. Alternatively, the ports can be bundled
(bonded) for load balancing to a single logical iSCSI port with
a single IP address.
By default, six iSCSI target ports are predefined on the XIV
storage system to serve hosts over iSCSI.
Default gateway IP
address
Required if the connected hosts do not reside on the same
Layer-2 subnet.
Maximum transmission
unit (MTU)
Required if your network supports an MTU that is larger than
the standard one. The MTU default value is 1,536 bytes and
the maximum value is 8,192 bytes.
You should specify the largest possible MTU. If supported by
the switches and routers, use up to 8,192 bytes.
Configuring iSCSI ports on the XIV storage system
Perform the following procedure to configure iSCSI ports on the XIV storage
system from the XIV GUI.
Procedure
1. Log in to the IBM XIV GUI management application and zoom into the IBM
XIV Storage System that you want to configure.
2. Move the mouse over the Hosts and Clusters icon and then click iSCSI
Connectivity.
12
IBM XIV Host Attachment Guide
Figure 9. XIV GUI - Hosts and Clusters - iSCSI Connectivity
The iSCSI Connectivity table is displayed.
Figure 10. XIV GUI - iSCSI connectivity table
3. Click the Define button located at the top of the window. The Define IP
Interface – iSCSI dialog box is displayed.
Figure 11. XIV GUI - Define IP Interface - iSCSI
4. Fill in the following fields (for more information, see Table 2 on page 12):
Chapter 2. Preparation
13
v Name – Name of the iSCSI interface.
v Address – IP address of the iSCSI interface.
v Netmask – Enter the netmask address, or select an existing one from the list
box.
v Default Gateway – If needed, enter the IP address of the default gateway.
v MTU – Maximum transmission unit. The default is 4500; change this value
only if needed.
v Module – Select the physical module on which the iSCSi interface should be
set.
v Port Number – Select the physical port number on the previously selected
physical module.
Note: All devices in a network must use the same MTU. If in doubt, set MTU to
1500, because 1500 is the default value for Gigabit Ethernet. Performance might be
impacted if the MTU is set incorrectly.
5. Click Define. The iSCSI interface is set. Alternatively, you can use the following
XCLI command to create a new IP interface for iSCSI:
ipinterface_create ipinterface=IPInterfaceName
address=IPaddress netmask=NetworkMask
[ gateway=DefaultGateway ] [ mtu=MTU ] module=ComponentId ports=P1[,P2]
For more information about the ipinterface command, refer to the IBM XIV
XCLI Reference Guide, available on the IBM XIV Storage System Information
Center (publib.boulder.ibm.com/infocenter/ibmxiv/r2).
Using CHAP authentication for iSCSI connectivity
The IBM XIV Storage System supports industry-standard unidirectional iSCSI
CHAP authentication, allowing identity validation of the iSCSI initiator that
attempts to log in to the XIV storage system.
Important: CHAP authentication pre-configuration on the XIV storage system is
defined per individual host. There is no global CHAP configuration that can apply
to multiple hosts. By default, hosts are defined without CHAP authentication.
To set up CHAP authentication for a host, you must configure the following two
parameters on the XIV storage system:
v CHAP name – The username that the host must use for CHAP authentication.
v CHAP secret – The password that the host must use for CHAP authentication.
CHAP name and secret parameter guidelines
The following guidelines apply to the CHAP name and secret parameters:
v The CHAP secret must contain 96 bits to 128 bits (12 to 16 ASCII characters).
v Both the CHAP name and CHAP secret must be set together if CHAP
authentication is to be used. Authentication will not work if only one parameter
(name or secret) is defined.
14
IBM XIV Host Attachment Guide
XCLI commands for configuring CHAP authentication
Use the following XCLI commands to configure CHAP authentication.
To define a new host with CHAP parameters:
host_define host=[hostName] iscsi_chap_name=[chapName]
iscsi_chap_secret=[chapSecret]
Alternatively, if the host already exists:
host_update host=[hostName] iscsi_chap_name=[chapName]
iscsi_chap_secret=[chapSecret]
To clear the CHAP parameters (if no longer needed):
host_update host=[hostName] iscsi_chap_name= iscsi_chap_secret=
Note:
v For information about how to define the CHAP authentication using the XIV
GUI, see “Defining a host from the XIV GUI” on page 33.
v For information about how to use the CHAP name and secret when creating a
new iSCSI target on the host, see “Setting iSCSI connectivity parameters” on
page 54.
Stage 3: Preparing the host
Prepare your host for attachment as necessary.
The host preparation stage includes the following tasks:
v Validating the system requirements
v Validating your admin user privileges
v Optional: booting the operating system from a storage area network (SAN)
v Preparing AIX hosts (if applicable)
Validating the system requirements
Each operating system requires different validations.
Before installing the Host Attachment Kit (HAK) on the host, verify that the
installed operating system meets the requirements specified in the Compatibility and
requirements section of the latest release notes issued for the HAK version you are
using.
Chapter 2. Preparation
15
Windows Server users
Important:
v Refer to the latest release notes for a list of
Microsoft Hotfixes that must be installed
manually prior to installing the HAK.
v Ensure that Microsoft iSCSI Initiator (version
2.08 or later) is installed with the following
components:
– Initiator software and service – included in
Windows Server 2008 or later.
– Microsoft MPIO multipathing support for
iSCSI – in Windows Server 2008 or later,
MPIO should be installed from the Server
Manager.
Linux users
Important: Refer to the latest release notes for a
list of the iSCSI or Fibre Channel components that
must be installed on your Linux operating system.
AIX users
Important:
v The bos.adt.libm package must be installed on
the host. For more information, refer to the IBM
Fileset information website
(https://www-304.ibm.com/support/
docview.wss?uid=isg1fileset-1318926131).
v To avoid possible host reboots and downtime
when using the HAK, it is recommended to
always use the latest AIX TL update on the host.
These AIX updates have native support for the
XIV storage system. For more information, refer
to the release notes.
Validating your admin user privileges
You must perform the HAK installation and all other kit operations with root or
administrator user privileges on the host.
Before installing and using the HAK, make sure that your user name and
password enable you to log in with all the required privileges.
Windows Server users
Important: If User Account Control is enabled on
Windows Server 2008 or Windows Server 2008 R2,
you must run all CLI commands as an
administrator. To bypass the account control
limitations, go to the C:\WINDOWS\System32
directory, right-click cmd.exe, and then select Run
as Administrator.
16
IBM XIV Host Attachment Guide
Optional: booting the operating system from a storage area
network (SAN)
The host operating system (OS) can be booted from a local disk installation or from
a remote storage area network (SAN).
To learn how to boot the OS from an XIV-based SAN, refer to IBM XIV Storage
System – Host Attachment and Interoperability (www.redbooks.ibm.com/abstracts/
sg247904.html), available on the IBM Storage Redbooks website
(www.redbooks.ibm.com/redbooks.nsf/portals/storage).
Preparing AIX hosts (if applicable)
Refer to this section if you intend to use the built-in multipathing application
(MPIO) of an old AIX version.
Note: This section is relevant only to AIX users
who use:
v AIX 5.3 TL07-10 or earlier
v AIX 6.1 TL00-03 or earlier
Skip this section if you are using a different
operating system on the host.
The AIX versions detailed in the note above require pre-configuration before you
can use the xiv_attach utility (for more information about xiv_attach, see
Chapter 4, “Single host attachment,” on page 29).
Note: To avoid the need for pre-configuration, use the latest TL and service pack
on your AIX host. The latest AIX updates have native support for the IBM XIV
storage system. For more information, refer to the release notes.
To determine if your AIX version requires pre-configuration, run the following
command:
manage_disk_drivers -l
If the command output includes 2810XIV, your AIX host can identify XIV
automatically. If the command returns empty output or output that does not
include 2810, pre-configuration is required for your AIX version.
Refer to the following subsections for pre-configuring:
v “Queue depth”
v “Load balancing for Round-robin” on page 18
v “Multipathing” on page 18
Queue depth
The queue depth default value for TL10 and TL03 is 32; the default value for
previous AIX versions is 1.
export XIV_DEF_QD=32
Chapter 2. Preparation
17
Load balancing for Round-robin
Load balancing for Round-robin applies only for AIX managed multipathing.
By default, the package configures multipathing to work in Round-robin mode for
TL10 and TL03 and fail_over mode for previous versions. You can change the
multipathing mode to failover-only:
export XIV_DEF_ALGO=fail_over
If you define failover_only, only one path is used for any given hard disk. For
TLs earlier than 10 and 03 respectively, failover is the only method by which you
can use queue depths higher than 1.
Multipathing
If you are using a version of AIX that does not automatically identify the XIV
storage system and you want to use third-party multipathing software to manage
the system, you must set the following environment variable before you run the
xiv_attach utility:
export XIV_NOMP=yes
In versions later than AIX 5.3 TL10 or AIX 6.1 TL03, you must run the following
command to use a third party multipathing solution:
manage_disk_drivers -d 2810XIV -o AIX_non_MPIO
Note:
v The third party multipathing application must be supported by the XIV storage
system.
v The disks may be detected as 'IBM 2810XIV Non-MPIO Fibre Channel Disk' and
may not be compatible with multipathing as a result.
v If a real volume is not assigned to LUN 0, it is not multipathed and it may be
detected as 'IBM 2810XIV-LUN-0 Fibre Channel Array Controller'.
18
IBM XIV Host Attachment Guide
Chapter 3. Software installation
After the preparation stages are complete, you can begin the software installation
on the host.
Figure 12. Software installation
The software installation package includes the following components:
v IBM XIV Host Attachment Kit – includes the following command-line interface
(CLI) utilities:
– xiv_attach
– xiv_devlist
– xiv_syslist
– xiv_fc_admin and xiv_iscsi_admin (xiv_iscsi_admin is not supported on AIX
and HP-UX)
– xiv_detach (applicable to Windows Server only)
– xiv_diag
v IBM Storage Solutions External Runtime Components – Starting from version
1.7.0, these components (previously named "XPyV") are integrated within the
HAK code, rather than installed separately.
The following options are available for the Host Attachment Kit (HAK) software
installation:
v Option 1: Performing a clean local installation
v Option 2: Upgrading from a previous local installation
v Option 3: Using the portable package without installing
For information about how to remove the host attachment kit, see “Removing the
Host Attachment Kit software” on page 26.
© Copyright IBM Corp. 2009, 2012
19
Option 1: Performing a clean local installation
You can perform a clean local installation on any new host that has no previous
HAK installations, or on any existing host from which the previous HAK
installation has been completely removed.
Note: On new hosts, it is recommended to always install the latest available HAK
package, rather than installing an old version and then upgrading to the newer
HAK package.
Important: Refer to the latest release notes for up-to-date information regarding
compatibility, limitations, and requirements.
Depending on the operating system used on the host, refer to one of the following
sections:
v “Installing on AIX, HP-UX, Linux, or Solaris”
v “Installing on Windows Server” on page 21
Installing on AIX, HP-UX, Linux, or Solaris
This section describes the procedure to install the Host Attachment Kit on AIX,
HP-UX, Linux, or Solaris.
Procedure
Perform the following procedure to install the Host Attachment Kit on AIX,
HP-UX, Linux, or Solaris, using the native command prompt interface.
AIX users
Attention:
v Running the installation package removes any
customized settings for AIX hard disk devices
that correspond to XIV disks.
v For the virtual I/O server configuration, the
installation uses the oem_setup_env environment.
1. Copy the HAK installation package file to a local folder on the host.
2. Extract the installation package file (* stands for the OS and architecture
package):
# gunzip –c IBM_XIV_Host_Attachment_Kit_1.10.0-*.tar.gz | tar xvf –
3. Go to the extracted directory (referred to as <HAK extracted directory> below)
and then run install.sh to start the installer:
# cd <HAK extracted directory>
# ./install.sh
The installer welcome message is displayed:
20
IBM XIV Host Attachment Guide
Welcome to the XIV Host Attachment Kit installer.
Would you like to proceed and install the Host Attachment Kit? [y/n]:
4. Enter yes (or y) to begin the installation. The following is an example of the
displayed output:
Please wait while the installer validates your existing configuration...
--------------------------------------------------------------Please wait, the Host Attachment is being installed...
---------------------------------------------------------------
Note: The installation directory is: /opt/xiv/host_attach
When the installation is complete, the following prompt is displayed:
Installation successful.
--------------------------------------------------------------The IBM XIV Host Attachment Kit includes the following utilities:
xiv_attach: Interactive wizard that configures the host and verifies its configuration
for connectivity with the IBM XIV Storage System.
xiv_devlist: Lists of all XIV volumes that are mapped to the host, with general info
about non-XIV volumes.
xiv_syslist: Lists all XIV storage systems that are detected by the host.
xiv_diag: Performs complete diagnostics of the host and its connectivity with the
IBM XIV Storage System, and saves the information to a file.
xiv_fc_admin: Allows you to perform different administrative operations for
FC-connected hosts and XIV storage systems.
xiv_iscsi_admin: Allows you to perform different administrative operations for
iSCSI-connected hosts and XIV storage systems.
--------------------------------------------------------------Refer to the IBM XIV Host Attachment Guide for information on how to configure this
host.
AIX users
Note: Following the package installation, XIV
disks are multipathed and detected by the lsdev
command as: IBM 2810XIV Fibre Channel Disks. If
a real volume is not assigned to LUN0, it is not
multipathed and it may be detected as: IBM
2810XIV-LUN-0 Fibre Channel Array Controller.
Installing on Windows Server
This section describes the procedure of installing the Host Attachment Kit on
Windows Server.
The HAK installation package for Windows Server provides an installation wizard
that helps you install all the required files on the host, including some required
system updates (for more information, refer to the latest release notes).
Chapter 3. Software installation
21
Windows Server users
Note: When installing the HAK in cluster
environments: To install the HAK in Microsoft
Cluster Server (MSCS) 2003 or Windows Failover
Clustering 2008 environments, you must first
install the HAK on the passive nodes. After a
successful installation on these nodes, you can
perform failover of the resources to the nodes on
which the HAK is already installed. You can then
install the HAK on the remaining nodes.
Windows Server users
Note: When installing the HAK on hosts with
existing multipath solutions: The Veritas Storage
Foundation Dynamic Multipathing (DMP) does not
rely on the native multipath I/O (MPIO)
capabilities of the Windows Server operating
system. Instead, it provides its own custom
multipath I/O solution. Because these two
solutions cannot co-exist on the same host,
perform the following procedure if you intend to
use the Veritas solution:
1. Install the Veritas Storage Foundation package.
2. Restart the host.
3. Install the IBM XIV Host Attachment Kit.
If the version of the Veritas Storage Foundation
that you are using does not support the IBM
XIV Storage System, install the Device Driver
Installation Package 1 (DDI-1) for Veritas
Storage Foundation 5.1. This update supports
the IBM XIV Storage System.
Perform the following procedure to install the HAK from the Windows GUI.
1. Copy the HAK installation package file
(IBM_XIV_Host_Attachment_Kit_1.10.0*_for_Windows*.exe) that matches your
Windows Server architecture (x86 or x64) to a local folder.
2. Extract the files from the zip file and then run the setup executable. The HAK
Installation Wizard starts and then the Welcome panel is displayed.
3. Click Next. The Ready to Install the Program panel is displayed.
22
IBM XIV Host Attachment Guide
Figure 13. Installation Wizard - Ready to install the program
4. Click Install. The installation starts.
Note: The installation directory is: C:\Program Files\XIV\host_attach
5. When the installation completes, click Finish. The IBM XIV Host Attachment
Kit is added to the list of installed Windows programs.
Installing from the Windows command prompt interface
If you prefer using CLI for the installation, you can use the Windows command
prompt program (cmd.exe) to run the HAK setup executable. In addition, you can
use this method to install the HAK with verbose logging and in different levels of
unattended installation modes.
If you want to run the CLI setup with verbose logging (creates a local log file), run
the installation executable in its folder location as follows:
<IBM_XIV_Host_Attachment_Kit_1.10.0*_for_Windows*.exe> v”/l*vx setup.log”
Note: The /l*vx argument is part of the Microsoft Windows Installer
(msiexec.exe) syntax for verbose output. For more information, refer to the
Microsoft MSDN Library website (msdn.microsoft.com/en-US/library/ee251019
%28v=BTS.10%29.aspx).
Installing in unattended (silent) mode
If you want to run the installation in unattended (silent) mode to eliminate user
interaction during the installation, run the installation executable in its folder
location as follows:
Chapter 3. Software installation
23
<IBM_XIV_Host_Attachment_Kit_1.10.0*_for_Windows*.exe> /s /v”/qn”
If needed, you can replace or add arguments as detailed in Table 3.
Table 3. Optional CLI arguments for unattended (silent) installation
Argument
Use after <XIV_host_attachment_windows*.exe> to:
/q
Install in silent mode.
/qn
See no user prompt during the installation.
/qb
See only basic user prompt during the installation.
/qr
See reduced user prompt during the installation.
/qf
See the entire user prompt during the installation. This is
the default option.
/norestart
Prevent any host restart after the installation.
/promptrestart
Prompt before any host restart during or after the
installation.
/forcerestart
Force a restart of the host after the installation.
Option 2: Upgrading from a previous local installation
You may have a previous HAK version that you may want to upgrade.
If a previous version of the HAK is already locally installed on the host, extract the
new installation package and run the new installation file (install.sh on AIX,
HP-UX, Linux, and Solaris; setup executable on Windows) to start the upgrade
procedure. The installer automatically updates and replaces all the existing HAK
files on the host.
Note: Unless specified otherwise in the release notes, you do not have to uninstall
the previous version, and there is no need to detach the host from the XIV storage
system prior to the upgrade.
Important: You must run the xiv_attach command after any upgrade (for more
information, see “Stage 1: Using the CLI attachment utility (xiv_attach)” on page
29).
If you are upgrading in a command prompt (CLI) environment, the following
message is displayed:
Please wait while the installer validates your existing configuration...
-----------------------------------------------------------------------NOTICE: Another version of Host Attachment Kit is already installed.
The installer will replace the currently installed version.
Would you like to replace the installed Host Attachment Kit? [y/n]:
24
IBM XIV Host Attachment Guide
Windows users
Attention: If you are upgrading a Microsoft
Cluster Server (MSCS) cluster, move all resources
to unused nodes before the upgrade, so that the
passive nodes are upgraded first.
Option 3: Using the portable package without installing
The portable package allows you to use the IBM XIV Host Attachment Kit "out of
the box", without having to locally install the HAK utilities on the host.
You can run all HAK utilities from a shared network drive or from a portable USB
flash drive onto which the portable HAK package has already been extracted or
installed.
Note: Any locally installed HAK package becomes a portable HAK package when
it is copied or moved from its original directory (host_attach) to a different
directory.
Important:
v Before using the portable package, make sure that all the latest operating system
(OS) updates or hotfixes have been installed. You can use the xiv_fc_admin -V
or xiv_iscsi_admin -V commands to verify this and be notified if any OS
component is missing. The xiv_attach, xiv_fc_admin -C, and xiv_iscsi_admin
-C commands automatically install missing updates, but you may have to install
additional updates manually.
v For more information about these commands, see Chapter 6, “Additional tasks,”
on page 47.
v For more information about the required OS updates or hot fixes, refer to the
latest release notes.
Refer to one of the following subsections for more information:
v “Using a mounted network drive”
v “Using a portable USB flash drive” on page 26
Using a mounted network drive
This section describes how to use the HAK from a mounted network drive.
Procedure
To use the portable HAK package from a network drive:
1. Extract the files from <HAK_build_name>_Portable.tar.gz (for AIX, HP-UX,
Linux, Solaris) or <HAK_build_name>_Portable.zip (for Windows) into a shared
folder on a network drive.
2. Mount the shared folder to each host computer on which you intend to use the
HAK, so that the folder would be recognized and accessible as a network drive.
You can now use the IBM XIV Host Attachment Kit on any host to which the
network drive is mounted.
Chapter 3. Software installation
25
Note: Whenever a newer HAK version is installed on the network drive, all hosts
to which that network drive was mounted have immediate and direct access to the
new HAK version.
Using a portable USB flash drive
This section describes how to use the portable HAK package from a USB flash
drive.
Procedure
To use the portable HAK package from a USB flash drive ("Disk On Key"):
1. Extract the files from <HAK_build_name>_Portable.tar.gz (for AIX, HP-UX,
Linux, Solaris) or <HAK_build_name>_Portable.zip (for Windows) into a folder
on the USB flash drive.
2. Plug the USB flash drive into any host on which you want to use the IBM XIV
Host Attachment Kit, and then run any HAK utility from the plugged-in drive.
Removing the Host Attachment Kit software
Use the appropriate software removal method when needed.
If the Host Attachment Kit (HAK) is locally installed on the host (as opposed to a
portable HAK package), you can uninstall the kit in one of the following methods:
v Detaching the host and uninstalling the software – applicable to Windows Server
only.
v Uninstalling the software without detaching the host
Attention: Portable HAK packages do not require the uninstallation procedure.
You can delete the portable HAK directory (on the network drive or the USB flash
drive) to uninstall it. For more information about the portable HAK, see “Option 3:
Using the portable package without installing” on page 25.
Detaching the host and uninstalling the software
This section describes when and how to use the xiv_detach utility on Windows
Server.
About this task
Note: This section is relevant to Windows Server
users only. If you are using a different operating
system, see “Uninstalling the software without
detaching the host” on page 27.
If you want to completely disconnect a Windows Server host from the XIV storage
system prior to the removal of the HAK software, use the xiv_detach utility to
remove all XIV multipathing settings from the host.
26
IBM XIV Host Attachment Guide
Important: Always perform the xiv_detach operation and uninstall the HAK
before upgrading the operating system (not before upgrading the HAK). After the
operating system has been upgraded, you can reinstall the HAK and reattach the
host.
Procedure
Perform the following procedure to detach the host from the XIV storage system,
and then uninstall the HAK.
1. Run the xiv_detach command and enter yes (or y) when prompted to confirm
the detachment operation, as shown in the following example:
> xiv_detach
Welcome to the XIV Host Detachment wizard, version 1.10.0.
This wizard will assist you in detaching this host from the XIV system.
This wizard will unconfigure this host for XIV connectivity.
The host will not work properly with XIV devices until it is reconfigured.
Are you sure you would like to continue? [default: no]: yes
The connectivity type choice message is displayed.
Please choose a connectivity type, [f]c / [i]scsi :
2. Choose the connectivity type for which you want to remove all multipathing to
the XIV storage system: f for Fibre Channel or i for iSCSI. The detachment
confirmation message is displayed.
If you still have XIV volumes mapped to this host, it is recommended that you unmap
them now before unconfiguring the host.
Do you want to continue with unconfiguring the host? [default: no]: yes
3. Enter yes (or y) to start the detachment.
Please wait while the host is being unconfigured...
The host is now being unconfigured for the XIV system.
The XIV host attachment wizard successfully detached this host.
4. When the detachment is complete, go to Control Panel > Programs > Programs
and Features, select the IBM XIV Host Attachment Kit from the list of installed
programs, and then click Change. The uninstallation wizard guides you
through the remaining uninstallation steps.
Note: The uninstall command removes the following components:
v IBM Storage Solutions External Runtime Components
v IBM XIV Host Attachment Kit tools
Uninstalling the software without detaching the host
The regular uninstallation removes the locally installed HAK software without
detaching the host, keeping all multipathing connections to the XIV storage system.
Chapter 3. Software installation
27
Attention: Portable HAK packages do not require the uninstallation procedure.
You can delete the portable HAK directory (on the network drive or the USB flash
drive) to uninstall it. For more information about the portable HAK, see the
previous section.
To uninstall the HAK software from an AIX, HP-UX, Linux, or Solaris host, run the
following command:
# /opt/xiv/host_attach/bin/uninstall
Note: The uninstall command removes the following components:
v IBM Storage Solutions External Runtime Components
v IBM XIV Host Attachment Kit tools
28
IBM XIV Host Attachment Guide
Chapter 4. Single host attachment
Refer to this information when you are ready to attach your host to the IBM XIV
Storage System.
Figure 14. Single host attachment
The attachment of a single host includes the following stages:
v Stage 1: Using the CLI attachment utility (xiv_attach)
v Stage 2: Defining the host on the XIV storage system (if applicable)
v Stage 3: Mapping XIV volumes to the host
Stage 1: Using the CLI attachment utility (xiv_attach)
The Host Attachment Kit provides an interactive command-line utility, xiv_attach,
which locally configures and defines the host on the IBM XIV Storage System.
Procedure
When you are ready to start the host attachment, perform the following procedure.
1. Start a command prompt program on the host.
Windows Server 2008 or 2008 R2 users
Important: To bypass the account control
limitations, start the command prompt program as
follows: go to C:\WINDOWS\System32, right-click
cmd.exe, and then select Run as Administrator.
© Copyright IBM Corp. 2009, 2012
29
2. Enter xiv_attach. The Host Attachment Wizard welcome message is displayed.
Welcome to the XIV Host Attachment wizard, version 1.10.0.
This wizard will assist you to attach this host to the XIV system.
The wizard will now validate host configuration for the XIV system.
Press [ENTER] to proceed.
Note: You can run xiv_attach in verbosity mode using the -i or --verbose
argument, as explained in “Displaying information when working with xiv_attach”
on page 57.
3. Press Enter. The connectivity type choice message is displayed.
Please choose a connectivity type, [f]c / [i]scsi :
4. Enter the first letter of the connectivity type that the host uses to connect to the
XIV storage system: f for Fibre Channel or i for iSCSI. The following message is
displayed:
Please wait while the wizard validates your existing configuration...
v If you chose iSCSI, the following verification results are displayed (in this
Linux-specific example, all verification results are OK):
Verifying
Verifying
Verifying
Verifying
Verifying
Multipath configuration - multipath.conf
Multipath service(s)
iSCSI initiator name - initiatorname.iscsi
iSCSI daemon configuration - iscsid.conf
iSCSI service
OK
OK
OK
OK
OK
v If you chose FC, the following verification results are displayed (in this
Linux-specific example, all verification results are OK):
Verifying Multipath configuration - multipath.conf
Verifying Multipath service(s)
OK
OK
Important:
v Depending on the host configuration and installed components, you may be
requested to restart the host. In such a case, restart the host and then run
xiv_attach again.
v If the result of any verification is ’NOT OK’, the Host Attachment Wizard
requests your permission to continue:
The wizard needs to configure this host for the XIV storage system.
Do you want to proceed? [default: yes ]:
The wizard then automatically performs the required configuration and notifies
you about any task being performed. For example, when the multipath services
are being configured, the following prompt is displayed:
Configuring Multipath service(s)...
30
IBM XIV Host Attachment Guide
Linux users
Note: When you run xiv_attach, the Linux
multipath.conf file is automatically modified.
Although this modification has been fully tested
and is not known to cause conflicts or errors, the
original file is automatically backed up to the
/backups folder in the Host Attachment Kit
directory (default: /opt/xiv/host_attach/backups).
Solaris users
Important: The HAK wizard scans for existing
dynamic multipathing solutions. Valid solutions
for the Solaris operating system are Solaris
Multiplexed I/O (MPxIO) or Veritas Dynamic
Multipathing (VxDMP).
If VxDMP is already installed and configured on
the host, it is preferred over MPxIO and the
following message is displayed:
Notice: VxDMP is available and
will be used as the DMP software.
If VxDMP is installed but cannot be used, the
wizard prompts you to use MPxIO and the
following message is displayed:
Warning: VxDMP is available
but is not usable: VxDMP is not enabled.
Would you like to proceed to use
MPxIO multipathing? [default: no]:
Windows users
Note: Windows Server hotfixes are automatically
installed upon the first use of xiv_attach on the
host. For more information about the automatically
installed hotfixes (Microsoft KBs), refer to the IBM
XIV Host Attachment Kit release notes for
Windows.
5. After the host information is collected and analyzed, the following message is
displayed if any host configuration is necessary:
The wizard needs to configure this host for the XIV storage system.
Do you want to proceed? [default: yes ]:
Enter y to continue.
6. Based on the chosen connectivity type, the wizard offers to attach the host to
new storage arrays as follows:
v For Fibre Channel (FC) connectivity, the wizard displays the world-wide port
names (WWPNs) of all Fibre Channel HBAs that you can zone. Press Enter
to proceed.
Chapter 4. Single host attachment
31
Please zone this host and add its WWPNs with the XIV storage system:
21:00:00:24:ff:25:4f:fc: [QLOGIC]: N/A
21:00:00:24:ff:25:4f:fd: [QLOGIC]: N/A
Press [ENTER] to proceed.
v For iSCSI connectivity, you are asked if you want to discover new iSCSI
targets. Enter yes (or y) to start. You are then asked to enter the iSCSI IP
addresses and CHAP authentication details if these are predefined for the
host on the XIV storage system.
Would you like to discover a new iSCSI target? [default: yes]:
Please enter an XIV iSCSI discovery address (iSCSI interface):
Is this host defined in the XIV system to use CHAP? [default: no]:
Enter CHAP name:
Enter CHAP secret:
7. After the connectivity parameters are set, the wizard prompts you to start
scanning for storage devices. Enter yes (or y) to start the scanning.
Would you like to rescan for new storage devices now? [default: yes]:
The following message is displayed:
Please wait while rescanning for storage devices...
The host attachment wizard scans for physically connected XIV storage systems
and displays a list of the detected XIV storage systems (arrays), as shown in the
following example:
The host is connected to the following XIV storage arrays:
Serial
Version Host Defined Ports Defined Protocol
MN65009
11.1.0.0 Yes
All
iSCSI
MN65003
10.2.2.0 Yes
All
iSCSI
MN65004
10.2.4.2 Yes
All
iSCSI
Host Name(s)
rhel5.6-64-hak
rhel5.6-64-hak
rhel5.6-64-hak
v If the host is already defined on all the detected XIV storage systems, press
Enter to exit the host attachment wizard.
This host is defined on all FC-attached XIV storage arrays.
Press [ENTER} to proceed.
The IBM XIV host attachment wizard has successfully configured this host.
Press [ENTER} to exit.
v If the host is not defined on all the detected XIV storage systems, the wizard
asks you whether you want to define the host on these systems. Enter the
requested details as prompted:
Do you want to define this host on these systems now? [default: yes ]: yes
Please enter a name for this host [default: localhost.localdomain ]: <host name>
Please enter a username for system MN00022 : [default: admin ]: <admin user name>
Please enter the password of user admin for system MN00022:
Connecting to the storage array...
Press [ENTER] to proceed.
The IBM XIV host attachment wizard has successfully configured this host.
Press [ENTER} to exit.
32
IBM XIV Host Attachment Guide
Stage 2: Defining the host on the XIV storage system (optional)
If needed (see the following notes), you can manually define the host on the IBM
XIV Storage System.
AIX users
Important: This stage is mandatory for
non-updated AIX versions that do not support
automatic host definition on the XIV storage
system. For more information about the required
AIX updates, refer to the release notes. However, if
your host uses the most updated version, this
stage is optional.
HP-UX, Linux, Solaris and Windows users
Note: This stage is optional for HP-UX, Linux,
Solaris, and Windows Server hosts.
If the xiv_attach automatic host definitions were
sufficient for your uses, skip to “Stage 3: Mapping
XIV volumes to the host” on page 36.
Depending on your satisfaction (and the host operating system; AIX or other) from
the automatic host configuration performed by the xiv_attach utility (see “Stage 1:
Using the CLI attachment utility (xiv_attach)” on page 29), you can manually
define the host on the XIV system using the XIV management GUI or the XIV CLI
(XCLI), as described in the following subsections:
v “Defining a host from the XIV GUI”
v “Defining a host from the XCLI” on page 35
v “Adding ports to a host” on page 35
Defining a host from the XIV GUI
This section applies if you want to use the XIV GUI for defining a host.
Procedure
Perform the following procedure to configure a host from the XIV GUI.
1. Log in to the IBM XIV GUI management application and zoom into the IBM
XIV Storage System that you want to configure.
2. Move the mouse over the Hosts and Clusters icon and then click Hosts and
Clusters.
Chapter 4. Single host attachment
33
Figure 15. XIV GUI - Hosts and Clusters
The Hosts and Clusters table is displayed.
Figure 16. XIV GUI - Hosts and Clusters table
Note: If the host already appears on the list, you can right-click its name and
then select Edit to edit its details.
3. Click the Add Host button located at the top of the window. The Add Host
dialog box is displayed.
Figure 17. XIV GUI - Add host dialog box
4. Enter the following host details:
v Name – Name of the host.
34
IBM XIV Host Attachment Guide
v Cluster – If the host is a member of a cluster, select the cluster name from
the drop down list. Otherwise, leave the None default selection.
v Type – Select the host type from the drop down list.
v CHAP Name – If you want the host to use CHAP authentication over iSCSI
for this host (not applicable for AIX), enter the CHAP name. Otherwise, leave
this field blank.
v CHAP Secret – If a CHAP name was entered above, enter the CHAP secret.
Otherwise, leave this field blank.
5. Click Add. The host definition is added to the XIV storage system.
Defining a host from the XCLI
If you want to define a host from the XIV CLI (XCLI) rather than from the XIV
GUI, use the following commands.
v To list a specific host or all hosts:
host_list [host=HostName]
v To define a new host and connect it to the XIV storage system:
host_define host=HostName [cluster=ClusterName]
For more detailed information about host definition XCLI commands, refer to the
IBM XIV XCLI Reference Guide, available on the IBM XIV Storage System
Information Center (publib.boulder.ibm.com/infocenter/ibmxiv/r2).
Adding ports to a host
After the host is defined on the XIV storage system, it requires port definitions.
Procedure
If no ports have been defined for the host, perform the following procedure to add
iSCSI or FC ports.
1. On the Hosts and Clusters table (see Figure 16 on page 34), right-click the host
and select Add Port. The Add Port dialog box is displayed.
Figure 18. XIV GUI - Add Port dialog box
2. From the Port Type drop down list, select FC or iSCSI to define the port type.
3. Depending on the selected port type, set the port name as follows:
Chapter 4. Single host attachment
35
v For an FC port – Select the World Wide Port Name (WWPN) of the port
from the drop down list.
v For an iSCSI port – Enter the iSCSI Qualified Name (IQN) of the port.
4. Click Add. The port definition is added to the host.
Stage 3: Mapping XIV volumes to the host
After the xiv_attach utility has detected the XIV arrays, and after the host has
been defined on these arrays, you can use the XIV management GUI to map
volumes (LUNs) to the host.
Procedure
Perform the following procedure to map one or more volumes to the host.
1. On the Hosts and Clusters table (see Figure 16 on page 34), right-click the host
to which you want to map volumes, and then select Modify LUN Mapping.
Figure 19. XIV GUI - Modifying LUN Mapping to a host
The LUN mapping table is displayed.
2. Select one or more volumes that you want to map to the host, and then click
Map.
36
IBM XIV Host Attachment Guide
Figure 20. XIV GUI - Modifying LUN Mapping
The volume mapping is complete.
Chapter 4. Single host attachment
37
38
IBM XIV Host Attachment Guide
Chapter 5. Cluster host attachment
Refer to this information if you want to attach a cluster of hosts (as opposed to a
single host) to the IBM XIV Storage System.
Figure 21. Cluster host attachment
Attaching a group of hosts (see Figure 22 on page 40) requires different
prerequisites and a different host attachment procedure. This includes:
v Cluster installation prerequisites
v Stage 1: Defining the cluster on the XIV storage system
v Stage 2: Mapping XIV volumes to the cluster
© Copyright IBM Corp. 2009, 2012
39
Figure 22. A cluster connected to the IBM XIV Storage Systems
Cluster installation prerequisites
Install or mount the Host Attachment Kit (HAK) software on all cluster nodes. If
you are creating a new cluster, you can install the HAK simultaneously.
Procedure
If you are attaching an existing cluster to an IBM XIV Storage System, install the
HAK on the cluster nodes in the following manner:
1. Install the HAK on the passive nodes first.
2. Perform failover of the cluster groups and resources from the active nodes to
the passive nodes on which you have installed the HAK.
3. Install the HAK on the remaining nodes.
Stage 1: Defining the cluster on the XIV storage system
All hosts that belong to a cluster must be defined on the XIV storage system side
as cluster members.
Use either the XIV GUI or the XIV CLI (XCLI) to define cluster hosts, as explained
in the following sections:
40
IBM XIV Host Attachment Guide
v “Defining a cluster from the XIV GUI”
v “Defining a cluster from the XCLI” on page 43
Defining a cluster from the XIV GUI
This section describes how to define a cluster from the XIV GUI.
Procedure
1. Log in to the IBM XIV GUI management application and zoom into the IBM
XIV Storage System that you want to configure.
2. Move the mouse over the Hosts and Clusters icon and then click Hosts and
Clusters (see Figure 15 on page 34). The Hosts and Clusters table appears (see
Figure 16 on page 34).
3. Click the Add Cluster button located at the top of the window. The Add
Cluster dialog box is displayed.
Figure 23. Add Cluster dialog box
4. Enter the following cluster details:
v Name – Name of the cluster.
v Type – Select the cluster type from the drop-down list.
5. Click Add. The cluster is added to the Hosts and Clusters table.
Figure 24. XIV GUI - Cluster added to the Hosts and Clusters table
6. On the Standalone Hosts list, right-click a host that you want to add to the
cluster, and then select Add to Cluster.
Chapter 5. Cluster host attachment
41
Figure 25. XIV GUI - Add to Cluster
Note: You can select more than one host by pressing CTRL on your keyboard and
clicking the hosts that you want to add. After selecting multiple hosts, right-click
the yellow selection area to add all selected hosts to the cluster.
The Add Host(s) to Cluster dialog box appears.
Figure 26. XIV GUI - Add Host(s) to Cluster dialog box
7. From the drop-down list, select the name of the cluster to which you want to
add the selected host(s), and then click Add. All selected hosts are added to the
cluster.
42
IBM XIV Host Attachment Guide
Figure 27. XIV GUI - Host added to a cluster
Defining a cluster from the XCLI
If you want to define a cluster from the XIV CLI (XCLI) rather than from the XIV
GUI, use the following commands.
v To create a new cluster:
cluster_create cluster=ClusterName
v To add an existing host to a cluster:
cluster_add_host cluster=ClusterName host=HostName map=<cluster|host>
v To list existing clusters:
cluster_list [cluster=ClusterName]
For more detailed information about cluster definition XCLI commands, refer to
the IBM XIV XCLI Reference Guide, available on the IBM XIV Storage System
Information Center (publib.boulder.ibm.com/infocenter/ibmxiv/r2).
Stage 2: Mapping XIV volumes to the cluster
XIV volumes must be manually mapped to the cluster.
Two different volume types can be mapped to a cluster:
v Shared volumes – Mapped to all the nodes (hosts) in the cluster. Shared
volumes are typically used in clustered application environments.
v Private volumes – Mapped to a specific node (host) in the cluster. Private
volumes are required in environments in which a specific cluster node requires
exclusive access to a volume. For example, in environments that utilize boot
volumes, each cluster node requires exclusive access to a specific boot volume,
so that other cluster nodes would not corrupt the operating system on that boot
volume. In these environments, map a different private boot volume to each
host, and map the shared volumes to the entire cluster.
Depending on the volume type that you want to map to the cluster, refer to one of
the following sections:
v “Mapping shared volumes to all the hosts in a cluster”
v “Mapping private volumes to a specific host in a cluster” on page 44
Mapping shared volumes to all the hosts in a cluster
This section describes how to map shared volumes to all the hosts in a cluster.
Chapter 5. Cluster host attachment
43
Procedure
1. On the Hosts and Clusters table (see Figure 24 on page 41), right-click the
cluster to which you want to map volumes, and then select Modify LUN
Mapping.
Figure 28. XIV GUI - Modify LUN Mapping to a cluster
2. Select one or more volumes that you want to map to the cluster, and then click
Map.
The volume mapping is complete.
Figure 29. XIV GUI - Modify LUN Mapping
Mapping private volumes to a specific host in a cluster
This section describes how to map private volumes to a specific host in a cluster.
To map a volume exclusively to a specific host of a cluster, right-click the host
name on the list of clustered hosts.
44
IBM XIV Host Attachment Guide
Figure 30. Right-clicking a specific host of a cluster
The rest of the private volume mapping is performed in the same manner as in
shared volume mapping (see Figure 29 on page 44).
Note: After mapping private volumes to a host of a cluster, the private mapping is
labeled in the mapped volumes list as Private Mapping.
Chapter 5. Cluster host attachment
45
46
IBM XIV Host Attachment Guide
Chapter 6. Additional tasks
Refer to this information to learn about useful tools that are included in the IBM
XIV Host Attachment Kit.
Figure 31. Additional tasks
After your host or cluster has been successfully attached to the IBM XIV Storage
System, you can perform different administrative operations on the host by using
the Host Attachment Kit (HAK) utilities.
These operations include the following optional tasks:
v Displaying information of connected XIV systems
Displaying volume and additional information
Setting Fibre Channel connectivity parameters
Setting iSCSI connectivity parameters
Displaying information about host configuration changes – applicable only to
Linux and Windows Server
v Performing diagnostics
v
v
v
v
AIX users
Important: To avoid host reboots and downtime
when using the FC configuration command
(xiv_fc_admin -C), it is recommended to always
use the latest AIX TL update and service pack (SP)
on the host. The latest AIX updates have native
support for the XIV storage system. For more
information, refer to the release notes.
© Copyright IBM Corp. 2009, 2012
47
Displaying information of connected XIV systems
If you want to display the details of all XIV storage systems that are currently
detected as physically connected to the host, use the xiv_syslist command.
The listed XIV systems may be ones to which the host is already attached, or ones
to which the host is not yet attached (for example, if new systems were added
recently).
Note: XIV systems to which the host is not yet attached are detected by
xiv_syslist as long as the FC or iSCSI connectivity was properly set. For more
information about how to properly set the FC or iSCSI connectivity between the
host and the XIV system, refer to Chapter 2, “Preparation,” on page 5.
The following example shows the default xiv_syslist output format for two XIV
systems that are connected to the host:
xiv_syslist
This host is connected to the following XIV storage arrays:
System Name: XIV Main1A
--------------System Details:
--------------System Serial Number: MN00001
System Version: 10.2.4.e
Management IPv4 Addresses: 10.100.155.200
------------Connectivity:
------------Connectivity Type: iSCSI
System iSCSI Targets: Module 8
---------------Host Definition:
---------------Host Defined: Yes
Host Name Defined: john1
Number of Host Ports Defined: All
System Name: XIV Main1B
--------------System Details:
--------------System Serial Number: MN00002
System Version: 10.2.4.e
Management IPv4 Addresses: 2.100.155.250, 3.100.155.250, 4.100.155.250
------------Connectivity:
------------Connectivity Type: iSCSI
System iSCSI Targets: Module 7, Module 8, Module 9
---------------Host Definition:
---------------Host Defined: Yes
Host Name Defined: john2
Number of Host Ports Defined: All
The displayed details of any detected XIV system include:
48
IBM XIV Host Attachment Guide
v System name – Name of the XIV system.
v System details – System-specific details, including:
– System serial number – Serial number of the XIV system.
– System version – Microcode version of the XIV system.
– Management IPv4 addresses (displayed if IPv4 is used) – The IPv4
address(es) through which the XIV system is accessed and managed.
v Connectivity – Connectivity information, including:
– Connectivity type – Type of connectivity that is used to connect to the XIV
system: FC or iSCSI.
– System FC targets (displayed if FC is used) – Lists the specific XIV modules
and FC port numbers with which FC connectivity is established.
– System iSCSI targets (displayed if iSCSI is used) – Lists the specific XIV
modules with which iSCSI connectivity is established.
v Host definition – Information regarding this host as defined on the XIV system,
including:
– Host defined – Indicates with ’Yes’ or ’No’ whether the host is defined on the
XIV system. If your host was properly attached to the XIV system, the
indication should be ’Yes’.
– Host name defined (displayed if the host is defined) – Name of the host as
defined on the XIV system.
– Number of host ports defined – Number of host ports that are defined on
the XIV system. If all host ports are defined, the output is ’All’.
If you want to display only specific XIV system details in CSV or XML format, or
if you want to save the information to a CSV or an XML file, add the required
arguments after the xiv_syslist command, as detailed in Table 4.
Note: The customized output of xiv_syslist (using the -o argument, as detailed
in the following table) is not available in regular screen view. You must specify
either CSV or XML as the output format.
Important: All command arguments are case-sensitive.
Table 4. Optional arguments for xiv_syslist
Short-form argument
Long-form argument
Use after xiv_syslist to:
-t csv
--out csv
-t xml
--out xml
Display the xiv_syslist information on the screen
(without saving to a file), in either CSV or XML format
(as specified).
-f <file name>
-t csv
-t xml
--file <file name>
--out csv
--out xml
Save the xiv_syslist information to a file.
The name of the file must be typed after the -f or
--file argument, and should be followed by the -t or
--out argument that determines the file format: CSV or
XML.
For example:
xiv_syslist -f <file name> -t csv
Chapter 6. Additional tasks
49
Table 4. Optional arguments for xiv_syslist (continued)
Short-form argument
Long-form argument
Use after xiv_syslist to:
-t <csv or xml>
--out <csv or xml>
And then:
And then:
Display specific details depending on the parameter(s)
typed after the -o argument.
-o system_name
--options
-o system_serial_number
(followed by a
specific field)
-o system version
Important: The -o or --options argument must follow
the -t or --out argument (specifying CSV or XML).
The specific details are as previously described in this
topic, and are referred to in the command line as
"fields":
v System name (system_name)
-o management_ipv4_addresses
v System serial number (system_serial_number)
-o host_defined
v System version (system_version)
-o number_of_host_ports_defined
v Management IPv4 addresses
(management_ipv4_addresses).
-o connectivity_type
v Host defined (host_defined)
-o system_fc_targets
v Number of host ports defined
(number_of_host_ports_defined)
-o system_iscsi_targets
v Connectivity type (connectivity_type)
-o host_name_defined
v System FC targets (xiv_id)
v System iSCSI targets (xiv_host)
-o all
v Host name defined (host_name_defined)
v All (all) – Use this parameter if you want to display
all the details, including the ones that are not relevant
and normally not displayed in the default on-screen
xiv_syslist output.
If you want the customized output to include more than
one specific detail, specify the fields after the -o
argument, and use a comma without a space between
each field name.
For example:
xiv_syslist -t csv -o system_name,system_serial_number
-h
--help
Display usage format help information that is specific to
xiv_syslist.
Displaying volume and additional information
Use the xiv_devlist utility to display volume and additional information.
The following usage options are available:
v Displaying XIV and non-XIV volumes
v Displaying additional information
Displaying XIV and non-XIV volumes
You can use xiv_devlist to display the details of all XIV volumes that are mapped
to the host, as well as non-XIV devices (volume mapping information for non-XIV
devices is not available).
The following is an example of the displayed output when using xiv_devlist:
50
IBM XIV Host Attachment Guide
xiv_devlist
XIV Devices
--------------------------------------------------------------------------Device
Size (GB) Paths Vol Name Vol Id XIV Id XIV Host
--------------------------------------------------------------------------/dev/mapper/m 17.2
1/1
assafW2.K8 4
MN65015 ronend-suse11
patha
-64
--------------------------------------------------------------------------Non-XIV Devices
-------------------------Device
Size (GB) Paths
-------------------------/dev/sda 8.6
N/A
--------------------------
The default xiv_devlist output displays the following information in columns:
v Device – Name of each detected volume.
v Size (GB) – Total capacity of each detected volume, in gigabytes. You can
change the size unit with the -u argument, as explained in Table 5
v Paths – Active vs. total available communication paths.
v Volume name – Name of each detected XIV volume.
v Volume ID – ID number of each detected XIV volume.
v XIV ID – ID of each detected XIV storage device.
v XIV host – Name of this host as defined on each detected XIV storage device.
Note: To refresh the displayed information, use the xiv_fc_admin -R or
xiv_iscsi_admin -R command to rescan for storage devices. Then, run xiv_devlist
again.
Displaying additional information
You can use xiv_devlist to display additional information by adding different
optional arguments after the command.
The following table summarizes the different arguments and their use.
Important: All command arguments are case-sensitive.
Table 5. Optional arguments for xiv_devlist
Short-form argument
Long-form argument
Use after xiv_devlist to:
-V
--version
Display the Host Attachment Kit version number.
-x
--xiv-only
Display only the XIV devices, as opposed to displaying all
devices when the -x or --xiv-only argument is not used.
-m auto
--multipath auto
-m native
--multipath native
Choose the multipath method by which the xiv_devlist
information should be retrieved, depending on the parameter
name typed after the -m or --multipath argument.
-m veritas
--multipath veritas
The possible multipath methods are:
v Auto (auto) – automatically chosen by the HAK.
v Native (native) – native to the host operating system.
v Veritas (veritas) – compatible with Symantec Veritas.
Chapter 6. Additional tasks
51
Table 5. Optional arguments for xiv_devlist (continued)
Short-form argument
Long-form argument
Use after xiv_devlist to:
-o device
--options device
Display different details depending on the parameter name
typed after the -o or --options argument. These details are:
-o size
--options size
v Device (device) – Name of each detected volume.
-o serial
--options serial
v Size (size) – Total capacity of each detected volume.
-o lun
--options lun
-o multipath
--options multipath
v Multipath (multipath) – Active vs. total available paths.
-o vendor
--options vendor
v Vendor (vendor) – Vendor name of each detected storage
device.
-o vol_name
--options vol_name
v Volume name (vol_name) – Name of each detected volume.
-o vol_id
--options vol_id
-o xiv_id
--options xiv_id
-o xiv_host
--options xiv_host
-u MB
--size-unit MB
-u GB
--size-unit GB
Display the total storage capacity of each XIV volume and all
non-XIV volumes together, in a particular size unit, as specified
by the parameter typed after the -u or --size-unit argument.
-u TB
--size-unit TB
The possible size units are: MB, GB, TB, MiB, GiB, or TiB.
-u MiB
--size-unit MiB
-u GiB
--size-unit GiB
-u TiB
--size-unit TiB
v Serial (serial) – Serial number of each detected volume.
v LUN (lun) – Logical unit number of each detected volume.
v Volume ID (vol_id) – ID number of each detected volume.
v XIV ID (xiv_id) – ID of each detected XIV storage system.
v XIV host (xiv_host) – Name of this host as defined on each
detected XIV storage system.
Display the XIV volume and machine IDs in hexadecimal base.
-H
-f <file name>
-t csv
-t xml
--file <file name>
--out csv
--out xml
Save the xiv_devlist information to a file.
The name of the file must be typed after the -f or --file
argument, and should be followed by the -t or --out argument
that determines the file format: CSV or XML.
For example:
xiv_devlist -f file_name -t csv
Display the xiv_devlist information on the screen (without
saving to a file), in either CSV or XML format (as specified).
-t csv
--out csv
-t xml
--out xml
-h
--help
Display usage format help information that is specific to
xiv_devlist.
-l
--list
Display all the information field types that are available for
xiv_devlist.
Setting Fibre Channel connectivity parameters
The xiv_fc_admin utility allows you to perform different administrative operations
for FC-connected hosts and XIV storage systems.
Any operation performed with xiv_fc_admin requires a specific command
argument, as detailed in Table 6 on page 53.
52
IBM XIV Host Attachment Guide
Important: All command arguments are case-sensitive.
AIX users
Attention:
If you are using:
v AIX 5.3 that is older than TL11
v AIX 6.1 that is older than TL4
You must reboot the host after using xiv_fc_admin
-C.
Table 6. Arguments for xiv_fc_admin
Short-form
argument
Long-form
argument
-P
--print
Display the world-wide port number (WWPN) of the host bus adapters
(HBAs) that are installed on this host.
-L
--list
Display the details of all XIV storage systems that are currently attached
via Fibre Channel. These details include:
Use after xiv_fc_admin to:
v Serial – Serial number of each XIV storage system.
v Version – Microcode version of each XIV storage system.
v Host defined – Indicates whether this host is defined on each of the
listed XIV storage systems.
v Ports defined – Indicates which FC ports are defined on each of the
listed XIV storage systems.
v Protocol – The communication protocol used with each XIV storage
system (only FC protocol connections are listed when using
xiv_fc_admin).
v Host name(s) – Name of this host as defined on each of the listed XIV
storage systems.
Note: To display more detailed information about connected XIV
storage systems, use the xiv_syslist command. For more information,
see “Displaying information of connected XIV systems” on page 48.
-D
-u
-p
-H
-S
--define
<user name>
<password>
<hostname>
<serial>
(followed by the
sub-arguments)
Define this host on a specific XIV storage system, as detailed by the
sub-arguments and parameters that you type after the -D or --define
argument. The sub-arguments are:
v User name (–u) – User name for accessing the XIV storage system on
which the host should be defined.
v Password (–p) – Password for accessing the XIV storage system on
which the host should be defined.
v Hostname (–H) – Name of this host to be defined on the XIV storage
system. This sub-argument is optional. If not specified, the operating
system's hostname is used by default.
v Serial (–S) – Serial number of the specific XIV storage system on
which this host should be defined. Use the xiv_syslist command to
display the serial numbers of all connected XIV systems.
-R
--rescan
Rescan and detect all FC-connected storage systems.
Important: Always use xiv_fc_admin -R after new LUNs are added on
the XIV storage system (if FC connectivity is used).
Chapter 6. Additional tasks
53
Table 6. Arguments for xiv_fc_admin (continued)
Short-form
argument
Long-form
argument
-C
--configure
Use after xiv_fc_admin to:
Check whether this host is properly configured for FC host attachment,
and automatically perform any required configuration. The following is
an example of the displayed output when using xiv_fc_admin -C on a
Linux host:
udev multipath rules...
multipath.conf...
multipathd service...
OK
OK
OK
-V
--verify
Verify the host configuration tasks.
-b
--build
Display the HAK build number.
-v
--version
Display the HAK version number.
Note: You can use this argument with xiv_attach as well.
-i
--verbose
Display detailed information about the changes performed on the host
by xiv_fc_admin, without carrying out the command. For more
information, see “Displaying information about host configuration
changes” on page 56.
-h
--help
Display usage format help information that is specific to xiv_fc_admin.
Note: You can use this argument with xiv_attach as well.
Setting iSCSI connectivity parameters
The xiv_iscsi_admin utility allows you to perform different administrative
operations for iSCSI-connected hosts and XIV storage systems.
AIX users
Note: Because the IBM XIV Host Attachment Kit
for AIX does not support iSCSI connectivity, refer
to “Setting Fibre Channel connectivity parameters”
on page 52.
HP-UX users
Note: Because the IBM XIV Host Attachment Kit
for HP-UX does not support iSCSI connectivity,
refer to “Setting Fibre Channel connectivity
parameters” on page 52.
Any operation performed with xiv_iscsi_admin requires a specific command
argument, as detailed in Table 7 on page 55.
Important: All command arguments are case-sensitive.
54
IBM XIV Host Attachment Guide
Table 7. Arguments for xiv_iscsi_admin
Short-form
argument
Long-form
argument
-c <IP address>
--configure
[-n <CHAP name>]
[-s <CHAP secret>] (followed by the IP
address and CHAP
sub-arguments if
needed)
Use after xiv_iscsi_admin to:
Connect to a new iSCSI target, specified by IP interface address that you
type after the -c (small-cap c) or --configure argument.
In addition, if CHAP authentication was defined for the iSCSI target (for
more information, see “Using CHAP authentication for iSCSI
connectivity” on page 14), use the following sub-arguments (do not use
if CHAP authentication was not defined):
v CHAP name (-n) – The CHAP authentication name.
v CHAP secret (-s) – The CHAP authentication secret.
-d <IP address>
--disconnect
Disconnect an iSCSI target, specified by IP interface address that you
type after the -d or --disconnect argument.
-P
--print
Display the iSCSI initiator name and alias name.
-L
--list
Display the details of all XIV storage systems that are currently attached
via iSCSI. These details include:
v Serial – Serial number of each XIV storage system.
v Version – Microcode version of each XIV storage system.
v Host defined – Indicates whether this host is defined on each of the
listed XIV storage systems.
v Ports defined – Indicates which iSCSI ports are defined on each of the
listed XIV storage systems.
v Protocol – The communication protocol used with each XIV storage
system (only iSCSI protocol connections are listed when using
xiv_iscsi_admin).
v Host name(s) – Name of this host as defined on each of the listed XIV
storage systems.
Note: To display more detailed information about connected XIV
storage systems, use the xiv_syslist command. For more information,
see “Displaying information of connected XIV systems” on page 48.
-D
-u
-p
-H
-S
--define
<user name>
<password>
<hostname>
<serial>
Define this host on a specific XIV storage system, as detailed by the
sub-arguments and parameters that you type after the -D or --define
argument. The sub-arguments are:
v User name (–u) – User name for accessing the XIV storage system on
which the host should be defined.
v Password (–p) – Password for accessing the XIV storage system on
which the host should be defined.
v Hostname (–H) – Name of this host to be defined on the XIV storage
system. This sub-argument is optional. If not specified, the operating
system's hostname is used by default.
v Serial (–S) – Serial number of the specific XIV storage system on
which this host should be defined. Use the xiv_syslist command to
display the serial numbers of all connected XIV systems.
-R
--rescan
Rescan and detect all iSCSI-connected storage systems.
Important: Always use xiv_iscsi_admin -R after new LUNs are added
on the XIV storage system (if iSCSI connectivity is used).
Chapter 6. Additional tasks
55
Table 7. Arguments for xiv_iscsi_admin (continued)
Short-form
argument
Long-form
argument
-C
--connect
Use after xiv_iscsi_admin to:
Check whether this host is properly configured for iSCSI host
attachment, and automatically perform any required configuration.
The following is an example of the displayed output when using
xiv_iscsi_admin -C (capital C) on a Linux host:
udev multipath rules...
multipath.conf...
multipathd service...
iSCSI initiator configuration...
/etc/iscsid.conf file...
iscsi service...
OK
OK
OK
OK
OK
OK
-V
--verify
Verify the host configuration tasks.
-b
--build
Display the HAK build number.
-v
--version
Display the HAK version number.
Note: You can use this argument with xiv_attach as well.
-i
--verbose
Display detailed information about the changes performed on the host
by xiv_iscsi_admin, without carrying out the command. For more
information, see “Displaying information about host configuration
changes.”
-h
--help
Display usage format help information that is specific to
xiv_iscsi_admin.
Note: You can use this argument with xiv_attach as well.
Displaying information about host configuration changes
This section describes the use and output of the -i or --verbose command
argument, when used with HAK commands on Linux or Windows Server hosts.
Note: This section is relevant to Linux and
Windows Server users only.
If you want to display a detailed description of the configuration changes that are
to be performed when running the xiv_attach, xiv_fc_admin, and
xiv_iscsi_admin commands, use the -i or --verbose argument after the
command, as described in the following sections:
v “Displaying information for xiv_fc_admin or xiv_iscsi_admin”
v “Displaying information when working with xiv_attach” on page 57
For a summary of all possible configuration changes on the host, refer to
Chapter 8, “Summary of changes applied on the host,” on page 65.
Displaying information for xiv_fc_admin or xiv_iscsi_admin
When using the -i or --verbose argument after xiv_fc_admin or xiv_iscsi_admin,
the details of the host configuration actions that these commands perform are
displayed, but these actions are not carried out.
56
IBM XIV Host Attachment Guide
You can review the displayed information and then decide whether you want to
use the xiv_fc_admin --configure or xiv_iscsi_admin --configure commands on
the host (for more information about the --configure argument, see Table 6 on
page 53 and Table 7 on page 55).
The following example shows the displayed information for xiv_fc_admin on a
Linux host:
xiv_fc_admin --verbose
Multipath configuration - multipath.conf
===========================================================================
The multipath configuration file (/etc/multipath.conf) is updated as follows:
- The IBM XIV device is added/updated in the devices section, along with its
recommended parameters.
- Any blacklisting of the IBM XIV device is removed.
Before applying these changes, a backup copy of the original multipath.conf
file is saved in <HAK_dir>/backup.
On RHEL 6.3 or later, the device-mapper-multipath package already includes the
required IBM XIV values, so the multipath.conf file is not modified.
Multipath service(s)
===========================================================================
The multipath service ("multipathd") is enabled on run levels 3, 4, and 5,
and started automatically if not currently running.
On SLES, the ’boot.multipath’ service is enabled on the ’boot’ run level.
For more information about the configuration operations on the host per HAK
command and operating system, see Chapter 8, “Summary of changes applied on
the host,” on page 65.
Displaying information when working with xiv_attach
When using the -i or --verbose argument after xiv_attach, information about
pending host configuration changes is displayed, followed by a confirmation
prompt.
The configuration changes are carried out only after your confirmation.
The following example shows the displayed information for xiv_attach on a
Windows Server 2003 host that uses iSCSI connectivity:
Chapter 6. Additional tasks
57
xiv_attach --verbose
Previous HAK versions
=====================
All previous versions of the IBM XIV Host Attachment Kit are removed from the
Windows registry, and all previous versions of Python are removed from ’pythonpath’.
LUN0 device driver
==================
The LUN0 device driver is installed to enable display of XIV storage systems in
the list of recognized devices.
Disk timeout setting
====================
The value of the ’TimeOutValue’ key in the Windows Server registry is set to 60.
The key is located on the following path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk
iSCSI service
=============
The ’Microsoft Software iSCSI Initiator’ service is set to start automatically upon
boot, and set to be started manually upon the first use.
DSM Driver
==========
The IBM XIV DSM driver is installed to enable multipathing with XIV storage systems.
Persistent reservation key
==========================
A persistent reservation key is set so that a Round-Robin MPIO policy could be used
when using the IBM Storage Enabler for Windows Failover Clustering.
For more information about the configuration operations on the host per HAK
command and operating system, see Chapter 8, “Summary of changes applied on
the host,” on page 65.
Performing diagnostics
Whenever you want to perform complete diagnostics of your host and its
connectivity with the IBM XIV Storage System, run the xiv_diag utility.
The gathered information is saved to a file that you can review locally or send to
customer support whenever further assistance is needed.
Note: The gathered information should be interpreted and analyzed by an IBM
XIV professional. The information saved in the file does not include any analysis of
the gathered information.
The following is an example of the displayed output when using xiv_diag:
xiv_diag
Welcome to the XIV diagnostics tool, version 1.10.0.
This tool will gather essential support information from this host.
Please type in a path to place the xiv_diag file in [default: /tmp]:
When prompted to type a folder path, either press Enter to generate the report file
in the default folder (/tmp in Linux as shown in the example above), or enter a
different path.
58
IBM XIV Host Attachment Guide
Alternatively, you can use the -p or --path argument right after the xiv_diag
command, and then enter the folder path. This eliminates the need for entering the
folder path in a second step. For example:
# xiv_diag -p /var/log/
After the path is set, the information gathering starts and you can view its progress
as shown in the following Linux-specific example (the output varies depending on
the host operating system and HAK version):
Creating archive xiv_diag-results_2011-8-30_18-13-51
INFO: Gathering HAK version...
INFO: Gathering lsb_release -a...
INFO: Gathering xiv_devlist...
INFO: Gathering xiv_fc_admin –L...
INFO: Gathering xiv_fc_admin –V...
INFO: Gathering xiv_fc_admin –P...
INFO: Gathering xiv_iscsi_admin –L...
INFO: Gathering xiv_iscsi_admin –V...
INFO: Gathering xiv_iscsi_admin –P...
INFO: Gathering multipath...
INFO: Gathering ls scsi devices...
INFO: Gathering fdisk –l...
INFO: Gathering modinfo qla2xxx...
INFO: Gathering modinfo qla4xxx...
INFO: Gathering modinfo bfa...
INFO: Gathering modinfo lpfc...
INFO: Gathering df...
INFO: Gathering uname -a...
INFO: Gathering dmidecode...
INFO: Gathering rpm -qa...
INFO: Gathering ifconfig -a...
INFO: Gathering inquiry.py...
INFO: Gathering List disks in /dev directory...
INFO: Gathering /etc/fstab...
INFO: Gathering /var/lib/multipath/bindings...
INFO: Gathering /etc/multipath/bindings...
INFO: Gathering /etc/initiatorname.iscsi...
INFO: Gathering /etc/iscsi/initiatorname.iscsi...
INFO: Gathering /etc/iscsi.conf...
INFO: Gathering /etc/iscsid.conf...
INFO: Gathering /etc/iscsi/iscsid.conf...
INFO: Gathering multipath.conf...
INFO: Gathering mtab...
INFO: Gathering /etc/issue...
INFO: Gathering /etc/redhat-release...
INFO: Gathering build-revision file...
INFO: Gathering /sys directory...
INFO: Gathering /etc/udev directory...
INFO: Gathering /proc directory...
INFO: Gathering /etc/iscsi directory...
INFO: Gathering /var/lib/iscsi directory...
INFO: Gathering /var/log/messages logs...
INFO: Gathering /var/log/boot logs...
INFO: Gathering host_attach logs...
INFO: Gathering xiv_devlist logs...
INFO: Closing xiv_diag archive file...
Deleting temporary directory...
INFO: Gathering is now complete.
INFO: You can now send /tmp/xiv_diag-results_2011-8-30_18-13-51.tar.gz
IBM XIV Support for review and further assistance.
INFO: Exiting.
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
DONE
to
Note: Gathered information items are marked as 'DONE'. Some items may be
skipped and marked as 'SKIPPED' due to technical incompatibilities with the host
operating system, or due to other technical reasons.
Chapter 6. Additional tasks
59
60
IBM XIV Host Attachment Guide
Chapter 7. Best practices
There are a few best practices that you can apply when using the IBM XIV Host
Attachment Kit, as described in the following sections.
v “Recommended operating system settings”
v “Monitoring host connectivity from the XIV GUI and XCLI”
v “Using the rescan (-R) option after new volumes are mapped” on page 62
Recommended operating system settings
Each operating system and CPU architecture has different settings that work best
for host connectivity and performance with the XIV storage system.
If you are a host administrator, consult with your storage administrator for setting
up the best-suited host configuration in your specific production environment.
For detailed information about recommended settings refer to IBM XIV Storage
System – Host Attachment and Interoperability (www.redbooks.ibm.com/abstracts/
sg247904.html), available on the IBM Storage Redbooks website
(www.redbooks.ibm.com/redbooks.nsf/portals/storage).
Monitoring host connectivity from the XIV GUI and XCLI
Constant host connectivity is crucial for hosts that work with the IBM XIV Storage
System.
To ensure that your host is properly connected to the XIV storage system, you can
monitor the connectivity of attached hosts in real time from either the XIV GUI or
XIV CLI (XCLI).
Monitoring from the XIV GUI
This section describes how to use the XIV GUI for monitoring.
Procedure
1. Log in to the IBM XIV GUI management application and zoom into the IBM
XIV Storage System to which the host is connected.
2. Move the mouse over the Hosts and Clusters icon and then click Hosts
Connectivity.
© Copyright IBM Corp. 2009, 2012
61
Figure 32. XIV GUI - Hosts Connectivity
The Hosts Connectivity table is displayed.
Figure 33. XIV GUI - Hosts Connectivity table
Monitoring from the XCLI
If you want to monitor the host connectivity from the XCLI rather than from the
XIV GUI, use the following commands.
v List FC and iSCSI connectivity of a host:
host_connectivity_list [ host=HostName | fc_host_port=WWPN ]
[module=ComponentId | fcport=ComponentId ]
v List the status and configuration of the XIV system's FC ports:
fc_port_list [ module=ComponentId | fcport=ComponentId ]
For more detailed information about XCLI commands, refer to the IBM XIV XCLI
Reference Guide, available on the IBM XIV Storage System Information Center
(publib.boulder.ibm.com/infocenter/ibmxiv/r2).
Using the rescan (-R) option after new volumes are mapped
In a typical environment, new storage volumes may be created on a regular basis.
As a best practice and to avoid missing new volumes, always use the
xiv_iscsi_admin -R or xiv_fc_admin -R command (depending on the connectivity
type) to rescan for volumes after new volumes are mapped to the host (for more
62
IBM XIV Host Attachment Guide
information, see “Stage 3: Mapping XIV volumes to the host” on page 36, “Setting
Fibre Channel connectivity parameters” on page 52, and “Setting iSCSI
connectivity parameters” on page 54).
Chapter 7. Best practices
63
64
IBM XIV Host Attachment Guide
Chapter 8. Summary of changes applied on the host
Different changes are applied on the host when you perform different Host
Attachment Kit operations.
This includes:
v Changes applied on a Linux host
v Changes applied on a Windows Server host
Changes applied on a Linux host
Note: This section and the following subsections
apply to Linux users only.
Depending on the Host Attachment Kit operations that you perform on the Linux
host, the following changes may be applied on it:
v Multipath configuration
v
v
v
v
Multipath service(s)
iSCSI daemon configuration
iSCSI initiator name
iSCSI service
Multipath configuration
Note: This subsection applies to the xiv_fc_admin, xiv_iscsi_admin, and
xiv_attach commands when used on a Linux host.
The multipath configuration file (/etc/multipath.conf) is updated as follows:
v The IBM XIV device is added/updated in the devices section, along with its
recommended settings and parameters:
path_checker tur
The SCSI Test Unit Ready CDB is called for checking if path is up.
no_path_retry queue
Perform queue if all paths are down.
rr_min_io 15
Minimum I/Os before performing round-robin.
path_grouping_policy multibus
All paths should be used equally.
path_selector "round-robin 0"
Default round-robin behavior is set to 0.
v Any blacklisting of the IBM XIV device is removed.
Before applying these multipath configuration changes, a backup copy of the
original multipath.conf file is saved in <HAK_dir>/backup.
© Copyright IBM Corp. 2009, 2012
65
Note: New from Version 1.10.0, beginning at RHEL 6.3, the device-mappermultipath (version 0.4.9, release 56) includes XIV defaults. If this version is
detected, the multipath.conf is left untouched. If there is no multipath.conf file, one
is created (using /sbin/mpathconf --enable) since it is needed to run multipath
tool.
Multipath service(s)
Note: This subsection applies to the xiv_fc_admin, xiv_iscsi_admin, and
xiv_attach commands when used on a Linux host.
The multipath service ("multipathd") is enabled on run levels 3, 4, and 5, and
started automatically if not currently running.
On SLES, the boot.multipath service is enabled on the 'boot' run level.
iSCSI daemon configuration
Note: This subsection applies to the xiv_iscsi_admin and xiv_attach commands
when used on a Linux host and over iSCSI.
The iSCSI daemon configuration file (/etc/iscsid.conf or /etc/iscsi/
iscsid.conf) is updated with the default values. The full list of values can be
found in: <HAK_dir>/etc/linux/iscsi.conf
A backup copy of the original iscsid.conf is saved in <HAK_dir>/backup.
iSCSI initiator name
Note: This subsection applies to the xiv_iscsi_admin and xiv_attach commands
when used on a Linux host and over iSCSI.
A random IQN is generated and placed in: /etc/[iscsi/]initiatorname.iscsi
If the initiatorname.iscsi file already exists and contains an IQN, it is not
modified. The random IQN is generated by the native Linux iscsi-name tool.
iSCSI service
Note: This subsection applies to the xiv_iscsi_admin and xiv_attach commands
when used on a Linux host and over iSCSI.
The iSCSI service is enabled on run levels 3, 4, and 5, and started automatically if
not currently running. The service name is iscsi on RHEL, and open-iscsion
SLES.
Changes applied on a Windows Server host
Note: This section and the following subsections
apply to Windows Server users only.
66
IBM XIV Host Attachment Guide
Depending on the Host Attachment Kit operations that you perform on the
Windows Server host, the following changes may be applied on it:
v Removal of previous HAK versions
v LUN0 device driver
v Disk timeout setting
v iSCSI service
v XIV MPIO Load Balancing service
v XIV MPIO Load Balancing agent
v Built-in MPIO feature
v DSM driver
v Persistent reservation key
Removal of previous HAK versions
Note: This subsection applies to Windows Server 2003, Windows Server 2008, and
Windows Server 2008 R2.
All previous versions of the IBM XIV Host Attachment Kit are removed from the
Windows registry, and all previous versions of Python are removed from
pythonpath.
LUN0 device driver
Note: This subsection applies to Windows Server 2003, Windows Server 2008, and
Windows Server 2008 R2.
The LUN0 device driver is installed to enable display of XIV storage systems in the
list of recognized devices.
Disk timeout setting
Note: This subsection applies to Windows Server 2003, Windows Server 2008, and
Windows Server 2008 R2.
The value of the TimeOutValue key in the Windows Server registry is set to 60. The
key is located on the following path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk
iSCSI service
Note: This subsection applies to Windows Server 2003, Windows Server 2008, and
Windows Server 2008 R2.
The Microsoft Software iSCSI Initiator service is set to start automatically upon
boot, and set to be started manually upon the first use.
Chapter 8. Summary of changes applied on the host
67
XIV MPIO Load Balancing service
Note: This subsection applies to Windows Server 2008 and Windows Server 2008
R2.
Any instance of the MPIO load balancing service is traced, stopped, and removed
– as part of removing the deprecated XIV MPIO load balancing.
XIV MPIO Load Balancing agent
Note: This subsection applies to Windows Server 2008 and Windows Server 2008
R2.
Any instance of the MPIO load balancing agent is traced, stopped, and removed –
as part of removing the deprecated XIV MPIO load balancing.
Built-in MPIO feature
Note: This subsection applies to Windows Server 2008 and Windows Server 2008
R2.
The built-in Microsoft Windows MPIO feature is installed and then enabled for
XIV devices.
DSM driver
Note: This subsection applies to Windows Server 2003.
The IBM XIV DSM driver is installed to enable multipathing with XIV storage
systems.
Persistent reservation key
Note: This subsection applies to Windows Server 2003.
A persistent reservation key is set so that a Round-robin MPIO policy could be
used when using the IBM Storage Enabler for Windows Failover Clustering.
68
IBM XIV Host Attachment Guide
Chapter 9. XIV and VMware ESX or ESXi hosts
The following reference information is relevant only to VMware hosts and not
related to the IBM XIV Host Attachment Kit solution.
Attention: This chapter provides reference information about how to physically
connect ESX or ESXi hosts to the IBM XIV Storage System. However, the Host
Attachment Kit software solution is not available for VMware ESX or ESXi
hosts, and cannot be used with these hosts.
For information about IBM Storage host software solutions for VMware platforms,
refer to the IBM Storage Host Software Solutions Information Center
(publib.boulder.ibm.com/infocenter/strhosts/ic/index.jsp).
Choosing ESX configurations
The following table details the supported connectivity types and host bus adapter
(HBA) brands that are supported by ESX or ESXi platforms.
Table 8. ESX configurations
VMware server platform
Connectivity type
HBA brand
ESX or ESXi 3.5
Fibre Channel (FC)
v QLogic
v Emulex
ESX or ESXi 4.x
iSCSI*
VMware iSCSI Software
Initiator
Fibre Channel (FC)
v QLogic
v Emulex
iSCSI*
v VMware iSCSI Software
Initiator
v Hardware-dependent
iSCSI Initiator (for ESX or
ESXi 4.1 only)
Important: iSCSI connectivity for VMware ESX is supported with XIV microcode
version 10.2.4 or later.
For the latest support information and compatibility matrix, refer to the IBM
System Storage Interoperation Center (www.ibm.com/systems/support/storage/
config/ssic).
For best performance, install the latest firmware and drivers for the HBAs that are
in use. The HBA vendor should provide the latest firmware and drivers.
Fibre Channel SAN zoning
SAN Fibre Channel zoning defines devices within a zone, so that it isolates devices
inside a zone from devices outside the zone.
© Copyright IBM Corp. 2009, 2012
69
FC zoning is generally a good practice and a requirement when connecting an ESX
with multiple paths to the IBM XIV storage array.
SAN zoning should be set as a Single Initiator Zoning layout. Set a single Initiator
(ESX HBA port) per SAN zone. Figure 34 shows two clustered ESX servers are
attached to an XIV storage system over multiple FC paths.
Figure 34. SAN Fibre Channel zoning layout
The following table specifies the devices that are hidden from each other:
Table 9. Initiators and targets in the SAN Fibre Channel zoning layout
Zone name
Initiator
Targets
Zone 1
ESX1_Port0
XIV_Module4_Port1
XIV_Module6_Port1
Zone 2
ESX1_Port1
XIV_Module4_Port3
XIV_Module6_Port3
Zone 3
ESX1_Port0
XIV_Module4_Port1
XIV_Module6_Port1
Zone 4
ESX1_Port1
XIV_Module4_Port3
XIV_Module6_Port3
iSCSI target discovery
Part of the iSCSI protocol is discovering which targets are accessible to the initiator.
VMware iSCSI software initiator offers two methods to discover iSCSI targets:
v Send Targets (Dynamic Discovery) – When using the send targets method, the
software iSCSI initiator is given one IP address or a list of IP addresses. The
initiator then queries each address for available iSCSI targets.
70
IBM XIV Host Attachment Guide
v Static Discovery – When using the static discovery method, each iSCSI target's IP
address needs to be added manually to the initiator's target list. Static discovery
cannot be configured when using VMware iSCSI software Initiator on ESX 3.5.
When connecting an ESX server to IBM XIV using iSCSI, connect at least two NICs
to at least two interface modules, resulting in a minimum of four paths for each
LUN.
Figure 35 shows two ESX servers that are connected to an IBM XIV system. Each
iSCSI initiator has three iSCSI interfaces defined using the Send Targets method,
resulting in six available paths for each LUN.
Figure 35. Connecting ESX servers over iSCSI
Multipathing and load balancing
VMware ESX servers provide an I/O multipathing driver that can be used for
redundancy and for I/O load balancing between paths.
IBM XIV is a fully symmetrical Active-Active storage array, in which all LUNs are
serviced through all storage ports concurrently. As of microcode version 10.2.1, it is
presented to ESX 4.x as an Asymmetrical Logical Unit Access (ALUA) array.
However, this does not affect performance or create additional management
overhead. Because the ESX considers all of the paths to IBM XIV as optimized, no
additional configuration is needed.
Choosing a multipathing policy
ESX multipathing supports the following path policies:
v Fixed – Always use the preferred path to the disk. If the preferred path is not
available, an alternate path to the disk is used. When the preferred path is
restored, an automatic failback to preferred path occurs.
v Fixed AP (in ESX 4.1 only) – Identified as VMW_PSP_FIXED_AP in the GUI,
this extends the Fixed policy to support ALUA arrays. The VM kernel selects the
Chapter 9. XIV and VMware ESX or ESXi hosts
71
preferred path, if the preferred path is not available, an alternate path to the disk
is used. When the preferred path is restored, an automatic failback to the
preferred path occurs.
v Most Recently Used – Use the path most recently used while the path is
available. Whenever a path failure occurs, an alternate path is used. There is no
automatic failback to the original path.
v Round Robin (experimental in ESX 3.5) – Multiple disk paths are used and
balanced using an automatic rotation mechanism.
Use the Round Robin policy when connecting ESX 4.x to IBM XIV. The default
multipathing policy in ESX 4.x for ALUA Active/Active arrays is Most Recently
Used. Use the Fixed policy (default chosen by ESX 3.5 for Active/Active arrays)
when connecting ESX 3.5 to IBM XIV.
ESX 4.x multipathing configuration
Note: Run the following CLI commands using the ESX Console, vSphere RCLI or
the VMware Management Assistant (vMA). The use of the Tech Support Mode
console on ESXi is not recommended by VMware. Therefore, the vMA or vSphere
RCLI should be used for ESXi. For more information about these tools, refer to the
VMware documentation website (www.vmware.com/support/pubs).
The default path selection policy in ESX 4.x for Active/Active ALUA arrays is
Most Recently Used. This should be changed to Round Robin, which is the
recommended policy for ESX 4.x with IBM XIV. Use the following command to
change the default multipathing policy (this will only affect newly added LUNs.
Existing LUNs will have to be changed via vSphere Client or RCLI):
For IBM XIV systems with microcode version 10.2.1 and above:
esxcli nmp satp setdefaultpsp --satp VMW_SATP_ALUA --psp VMW_PSP_RR
For IBM XIV systems with microcode versions prior to 10.2.1:
esxcli nmp satp setdefaultpsp --satp VMW_SATP_DEFAULT_AA --psp VMW_PSP_RR
Attention: The following modification can cause a slight increase in the CPU
usage of the ESX host. If you do not need to change the default values, or if you
are unsure about any of the procedures below, keep the default values.
By default, the Round Robin policy switches to a different path after 1000 I/Ops.
Lowering this value can, in some scenarios, drastically increase storage
performance in terms of latency, MBps and I/Ops. To increase storage throughput,
you can change the value from 1000 to a lower value. When using IBM XIV, the
recommended value is 10. You can change this value by using the following
command for each device:
esxcli nmp roundrobin setconfig --type "iops" --iops=10
--device <device identifier>
Use the following command to issue a loop of the previous command for each XIV
LUN attached to the ESX server:
72
IBM XIV Host Attachment Guide
for i in `ls /vmfs/devices/disks/ | grep eui.001738* | grep -v :` ;
do esxcli nmp roundrobin setconfig --type "iops" --iops=10
--device $i ; done
Important: In ESX 4.0 versions prior to ESX 4.0 Update 2, the I/Ops value is not
retained once the ESX server is rebooted, resulting in a random I/Ops value being
assigned. To avoid this issue, either upgrade to ESX 4.0 Update 2 (or later), or add
the above line to the/etc/rc.local configuration file (to define the loop).
ESX 3.5 multipathing configuration
ESX 3.5 multipathing policies do not support automatic path balancing in a
production environment. However, you can tweak ‘preferred paths’ for LUNs to
achieve good-path load balancing.
The Fixed multipathing policy automatically selects the first available path as the
preferred path for the LUN. To spread I/O load efficiently, specify different
preferred paths for different LUNs, thus effectively utilizing multiple paths
comprised of different components (HBAs, switches, and storage ports).
Contact your IBM XIV Support representative to obtain a script that can balance
the preferred paths automatically and assist you in this task.
For more information, refer to the Fibre Channel SAN Configuration Guide on the
VMware documentation website (www.vmware.com/support/pubs).
Chapter 9. XIV and VMware ESX or ESXi hosts
73
74
IBM XIV Host Attachment Guide
Notices
These legal notices pertain to IBM Storage Host Software Solutions product
documentation.
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte character set (DBCS) information,
contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
© Copyright IBM Corp. 2009, 2012
75
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Attn: Office of Legal Counsel
650 Harry Road
San Jose, CA 95120-6099
U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
76
IBM XIV Host Attachment Guide
Trademarks
IBM, the IBM logo, ibm.com, AIX, and the AIX logo are trademarks or registered
trademarks of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be trademarks of
IBM or other companies. A current list of IBM trademarks is available on the
Copyright and trademark information website (www.ibm.com/legal/us/en/
copytrade.shtml).
HP, HP-UX, and HP UNIX are trademarks or registered trademarks of Hewlett
Packard Company in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or
both.
Oracle and Solaris are trademarks or registered trademarks of Oracle and/or its
affiliates.
Microsoft, Windows Server, Windows, and the Windows logo are trademarks or
registered trademarks of Microsoft Corporation in the United States, other
countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Veritas is a trademark or registered trademark of Symantec Corporation in the
United States and other countries.
VMware, ESX, and ESXi are trademarks or registered trademarks of VMware
Corporation in the United States and other countries.
Other product and service names might be trademarks of IBM or other companies.
Notices
77
78
IBM XIV Host Attachment Guide
Index
A
H
O
add ports to a host 35
admin user privileges
user privileges 16
AIX
installing 20
HAK installation package
upgrade 24
host attachment kit 1
host changes 65
host configuration
display changes 56
host connectivity
monitoring
XCLI 61, 62
XIV GUI 61
host definition 33
host preparation 15
HP-UX
installing 20
operating system settings 61
optional host definition 33
B
best practices
61
C
changes applied on host 65
choosing ESX configurations 69
CLI attachment utility 29
cluster
defining from the XIV GUI 41
cluster definition via XCLI 43
cluster host attachment 39, 43
defining the cluster on XIV 40
map private volumes to a specific host
in a cluster 44
map shared volumes to all hosts in a
cluster 44
map XIV volumes to cluster 43
cluster installation
prerequisites 40
compatibility 2
concept diagram 1
configuration changes 47
connectivity parameters 8
connectivity types 1
define a host 33
XCLI 35
XIV GUI 33
detach the host 26
devices 50
diagnostics 58
disk on key 26
display non-XIV volumes
display XIV volumes 50
download site 3
installation 19
installation package
installing on Windows 21
introduction 1
iSCSI
daemon configuration 66
initiator name 66
service 66
iSCSI connections 7
iSCSI connectivity
CHAP authentication 14
iSCSI ports
configure on XIV storage system
iSCSI settings 11
iSCSI target discovery 70
25
R
I
Linux
installing 20
Linux host
changes applied 65
load balancing 68, 71
local installation
performing 20
2
S
single host attachment 29
Solaris
installing 20
storage area network
boot from SAN 17
systems list 48
T
troubleshooting
58
12
U
uninstall
software removal 26
without detaching the host
uninstall the software 26
28
V
VMware 69
volume mapping
rescan (-R) option
62
50
E
ESX hosts 71
ESX or ESXi hosts
permissions 16
portable HAK package
USB flash drive 26
portable package
using without installing
requirements
L
D
P
M
W
map XIV volumes 36
multipath configuration 65
multipath service(s) 66
Multipathing 71
why 1
Windows Server host
changes applied 66
built-in MPIO feature 68
disk timeout setting 67
DSM driver 68
iSCSI service 67
persistent reservation key 68
removal of previous HAK
versions 67
XIV MPIO Load Balancing
agent 68
69
N
F
Fibre Channel (FC) connections 6
Fibre Channel SAN zoning 70
Fibre Channel zoning
zoning 8
© Copyright IBM Corp. 2009, 2012
network drive 25
non-XIV volumes 50
79
Windows Server host (continued)
changes applied (continued)
XIV MPIO Load Balancing
service 68
workflow 3
X
XCLI 35
xiv_attach 29
xiv_devlist 47, 50
display additional information
xiv_diag 47, 58
xiv_fc_admin 47, 57
xiv_iscsi_admin 47, 57
xiv_syslist 47, 48
80
51
IBM XIV Host Attachment Guide
Printed in USA
GA32-1060-05