00 W 0188

IBM System Storage DS Storage Manager Version 10
Installation and Host Support Guide
GA32-0963-03
Note
Before using this information and the product it supports, read the information in Notices on page 269.
Twelfth Edition, June 2012

Copyright IBM Corporation 2012.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . vii
Chapter 2. The Storage Manager

interface . . . . . . . . . . . . . . 11
Tables . . . . . . . . . . . . . . . ix
Enterprise Management window . . . . . .

Using the Devices tab . . . . . . . . .
Using the Setup tab . . . . . . . . .
Subsystem Management window . . . . . .
Opening the Subsystem Management window.
Using the Summary tab . . . . . . . .
Using the Logical tab . . . . . . . . .
Using the Physical tab . . . . . . . . .
Using the Mappings tab . . . . . . . .
Using the Setup tab . . . . . . . . .
Using the Support tab . . . . . . . . .
Managing multiple software versions . . . .
About this document . . . . . . . . . xi

Related documentation . . . . . . . . .
Storage Manager documentation on the IBM
website . . . . . . . . . . . . . .
Storage Manager online help and diagnostics .
Finding Storage Manager software, controller
firmware, and readme files . . . . . . .
IBM System Storage Productivity Center . .
Essential websites for support information. .
Getting information, help, and service . . . .
Before you call . . . . . . . . . . .
Using the documentation . . . . . . . .
Software service and support . . . . . .
Hardware service and support . . . . . .
Notices and statements in this document . . .
Receiving product updates and support
notifications . . . . . . . . . . . . .
Chapter 1. Preparing for installation
. xii
. xii
. xii
.
.
.
.
xiii
xiii
xiii
xiv
. xv
. xv
. xv
. xv
. xvi
. xvi
. . 1
Introduction . . . . . . . . . . . . . .
Storage Manager software . . . . . . . . .
Storage Manager software components . . . .
Supported controller firmware . . . . . . .
Types of installation configurations . . . . . . .
Network configuration . . . . . . . . . .
Reviewing a sample network configuration . .
Setting up a management station . . . . .
Setting up a network-managed (out-of-band)
configuration . . . . . . . . . . . .
Setting up a host-agent-managed (in-band)
configuration . . . . . . . . . . . .
Direct-attached and SAN-attached configurations
Setting up a direct-attached configuration. . .
Setting up a SAN-attached configuration . . .
Setting up controller addresses for software
installation . . . . . . . . . . . . . . .
Setting up IP addresses for storage subsystem
controllers . . . . . . . . . . . . . .
Setting up an IP address with the DHCP/BOOTP
server. . . . . . . . . . . . . . . .
Identifying Ethernet MAC addresses . . . .
Assigning static TCP/IP addresses to a storage
subsystem using factory-default management port
TCP/IP address . . . . . . . . . . . .
Assigning static TCP/IP addresses storage
subsystem using an in-band management
connection . . . . . . . . . . . . . .
Assigning static TCP/IP addresses using the
storage subsystem controller serial port Service
Interface . . . . . . . . . . . . . . .
Copyright IBM Corp. 2012
1
1
2
2
2
3
3
4
4
5
5
5
5
6
6
7
7
.
.
.
.
.
.
.
.
.
.
.
.
11
12
14
14
15
16
17
18
19
20
21
21
Chapter 3. Installing Storage Manager

and Support Monitor . . . . . . . . . 23
Preinstallation requirements . . . . . . . . .
Installing the Storage Manager and Support Monitor
packages automatically with the installation wizard .
Installing Storage Manager and Support Monitor
with a console window in Linux, AIX, HP-UX,
and Solaris . . . . . . . . . . . . .
Installing Storage Manager packages manually . .
Software installation sequence . . . . . . .
Installing Storage Manager manually . . . . .
Uninstalling Storage Manager and Support Monitor
Uninstalling Storage Manager and Support
Monitor on a Windows operating system . . .
Uninstalling Storage Manager and Support
Monitor on a Linux, AIX, or Solaris operating
system . . . . . . . . . . . . . . .
Completing the Storage Manager installation . . .
Performing an automatic discovery of storage
subsystems . . . . . . . . . . . . .
Performing a manual discovery of storage
subsystems . . . . . . . . . . . . .
Setting a storage subsystem management
password . . . . . . . . . . . . . .
Naming storage subsystems . . . . . . . .
Setting alert notifications . . . . . . . . .
Managing iSCSI settings . . . . . . . . .
Changing target authentication . . . . . .
Entering mutual authentication permissions
Changing target identification . . . . . .
Changing target discovery . . . . . . .
Configuring iSCSI host ports . . . . . .
Viewing or ending an iSCSI session . . . .
Viewing iSCSI statistics . . . . . . . .
Using an iSNS server . . . . . . . . .
Using DHCP . . . . . . . . . . . .
Using supported hardware initiators . . . .
Using IPv6 . . . . . . . . . . . .
Configuring network settings for iSCSI host
attachment . . . . . . . . . . . .
23
25
27
28
29
29
30
30
30
31
31
32
32
33
33
34
35
36
36
36
36
36
36
36
36
37
37
37
iii
Configuring Maximum Transmission Unit

settings . . . . . . . . . . . .
Microsoft iSCSI Software Initiator
considerations . . . . . . . . .
Downloading controller firmware, NVSRAM,
ESM firmware . . . . . . . . . .
Determining firmware levels . . . .
Downloading controller and NVSRAM
firmware . . . . . . . . . . .
Using the IBM System Storage Controller
Firmware Upgrade Tool . . . . . .
Downloading ESM firmware . . . .
Downloading drive firmware . . . . .
Storage Manager premium features . . .
Obtaining the premium feature enable
identifier . . . . . . . . . . .
Generating the feature key file . . . .
Enabling the premium feature . . . .
Disabling premium features . . . . .
Saving the storage subsystem profile . . .
. 38
. 38
.
.
. 38
. 39
. 40
.
.
.
.
.
.
.
.
41
43
43
45
.
.
.
.
.
.
.
.
.
.
46
46
47
47
48
Chapter 4. Configuring storage . . . . 49

Storage partitioning overview . . . . . . . .
Using the Task Assistant . . . . . . . . . .
Disk drives supported by IBM System Storage DS
Storage Manager . . . . . . . . . . . .
Rules for selecting drives when creating a RAID
array . . . . . . . . . . . . . . .
Solid state drive (SSD) attributes . . . . . .
T10PI capable drive attributes . . . . . . .
Rules for enabling T10PI functions . . . .
Enabling and disabling a T10PI capable RAID
array . . . . . . . . . . . . . .
Full Disk Encryption (FDE) attributes. . . . .
Configuring disk storage . . . . . . . . . .
Creating an array . . . . . . . . . . .
Redundant array of independent disks (RAID) .
Creating a standard logical drive . . . . . .
Configuring global hot-spare drives . . . . . .
Defining a default host type . . . . . . . . .
Defining a host group . . . . . . . . . . .
Defining heterogeneous hosts . . . . . . . .
Defining the host and host ports . . . . . . .
Mapping LUNs to a storage partition. . . . . .
Mapping LUNs to a new partition. . . . . .
Adding LUNs to an existing partition . . . .
Configuring the IBM System Storage DS5100 and
DS5300 for IBM i . . . . . . . . . . . .
Configuring and using optional premium features
About FlashCopy . . . . . . . . . . .
Using VolumeCopy . . . . . . . . . . .
Using the Remote Mirror option . . . . . .
Using Full Disk Encryption . . . . . . . .
Using other features . . . . . . . . . . .
Using controller cache memory . . . . . . .
Using Persistent Reservations . . . . . . .
Using Media Scan . . . . . . . . . . .
Errors reported by Media Scan . . . . . .
Media Scan settings . . . . . . . . .
Media Scan duration . . . . . . . . .
Tuning storage subsystems . . . . . . . . .
iv
49
50
50
52
53
54
56
57
61
63
63
64
66
67
68
70
70
71
71
71
72
72
74
74
75
75
75
76
76
77
77
78
79
80
80
Maximizing throughput with load balancing .

Balancing the Fibre Channel I/O load . . .
Optimizing the I/O transfer rate . . . . .
Optimizing the I/O request rate . . . . .
Determining the I/O access pattern and I/O
size . . . . . . . . . . . . . .
Enabling write-caching . . . . . . .
Optimizing the cache-hit percentage . . .
Choosing appropriate RAID levels. . . .
Choosing an optimal logical-drive
modification priority setting . . . . . .
Choosing an optimal segment size for an
array . . . . . . . . . . . . .
Defragmenting files to minimize disk access
Using the Storage Manager command-line interface
and Script Editor . . . . . . . . . . .
Storage Manager command-line interface . .
Using the Script Editor . . . . . . . .
.
.
.
.
81
82
82
83
.
.
.
.
83
83
83
83
. 84
. 84
84
. 84
. 85
. 85
Chapter 5. Configuring hosts . . . . . 89

Booting a host operating system using SAN boot . . 89
Using multipath drivers to automatically manage
logical drive fail-over and fail-back . . . . . . 91
Using host bus adapters . . . . . . . . . 93
Understanding host bus adapters . . . . . 94
Connecting HBAs in a Fibre Channel switch
environment . . . . . . . . . . . . 94
Installing a multipath driver . . . . . . . . 95
Windows MPIO or MPIO/DSM multipath
driver . . . . . . . . . . . . . . 96
Storport Miniport HBA device driver . . . . 96
SCSIport Miniport HBA device driver . . . 96
Veritas DMP DSM driver . . . . . . . . 97
AIX multipath drivers . . . . . . . . . . 97
Linux Device Mapper Multipath driver . . . . 97
Linux RDAC (MPP) driver . . . . . . . . 104
MAC OS multipath driver . . . . . . . . 105
Veritas DMP driver . . . . . . . . . . 106
HP-UX PV-links . . . . . . . . . . . 106
Using PV-links: Method 1 . . . . . . . 106
Using PV-links: Method 2 . . . . . . . 107
HP-UX native multipathing. . . . . . . 110
Solaris failover drivers . . . . . . . . . 110
Installing the MPxIO driver . . . . . . 110
Installing the RDAC failover driver on Solaris
and modifying the configuration files . . . 116
Planning and preparing for Veritas DMP
driver installation . . . . . . . . . . 118
Identifying devices . . . . . . . . . . . 120
Using the SMdevices utility . . . . . . . 120
Using SMdevices on Windows operating
systems . . . . . . . . . . . . . 120
Using SMdevices on UNIX-type operating
systems . . . . . . . . . . . . . 121
Identifying devices on AIX hosts . . . . . . 121
Configuring devices . . . . . . . . . . . 123
Using the hot_add utility . . . . . . . . 123
Using the SMrepassist utility . . . . . . . 123
Stopping and restarting the host-agent software 124
Setting the queue depth for hdisk devices . . . 124
Calculating maximum queue depth . . . . 125
IBM System Storage DS Storage Manager Version 10: Installation and Host Support Guide
Changing the queue depth for Windows . .

Changing the queue depth for AIX . . . .
Disabling cache mirroring . . . . . . . .
Using dynamic capacity expansion and dynamic
logical drive expansion . . . . . . . . .
Veritas Storage Foundation with SUSE Linux
Enterprise Server . . . . . . . . . . .
Veritas Storage Foundation 5.0 with Red Hat
Enterprise Linux . . . . . . . . . . .
Checking LUN size . . . . . . . . . .
Redistributing logical drives . . . . . . .
Redistributing logical drives on AIX . . . .
Redistributing logical drives on HP-UX. . .
Redistributing logical drives on Solaris . . .
Replacing hot-swap HBAs . . . . . . . .
Replacing hot-swap HBAs on AIX . . . .
Replacing IBM HBAs on Linux . . . . .
Replacing a PCI hotplug HBA . . . . . .
Mapping the new WWPN to the storage
subsystem for AIX and Linux . . . . . .
Completing the HBA hot-swap procedure
Setting up details on the DS5000 storage system
and AIX host to support T10PI . . . . . . .
Set up the DS5K storage box . . . . . . .
Set up the AIX host . . . . . . . . . .
127
128
129
129
129
130
130
131
134
137
Securing a RAID array . . . . . . . . .

Unlocking disk drives . . . . . . . . .
Migrating storage subsystems (head-swap) with
FDE drives . . . . . . . . . . . . .
Erasing disk drives . . . . . . . . . .
Global hot-spare disk drives . . . . . . .
Log files . . . . . . . . . . . . . .
Frequently asked questions . . . . . . . . .
Securing arrays . . . . . . . . . . . .
Secure erase . . . . . . . . . . . . .
Local security key management . . . . . .
External security key management . . . . .
Premium features . . . . . . . . . . .
Global hot-spare drives . . . . . . . . .
Boot support . . . . . . . . . . . .
Locked and unlocked states . . . . . . .
Backup and recovery . . . . . . . . . .
Other . . . . . . . . . . . . . . .
138
138
Chapter 7. Configuring and using the

Support Monitor . . . . . . . . . . 197
125
125
126
126
127
140
140
140
Chapter 6. Working with full disk

encryption. . . . . . . . . . . . . 143
Full disk encryption . . . . . . . . . . .
Securing data against a breach . . . . . .
Choosing local or external security key
management . . . . . . . . . . . .
Using security keys . . . . . . . . . .
Changing a security key for local security
key management . . . . . . . . . .
Changing a security key for external security
key management . . . . . . . . . .
Identifying a security key file for a storage
subsystem . . . . . . . . . . . .
Unlocking secure drives in local security key
management mode . . . . . . . . .
Unlocking secure drives in external security
key management mode . . . . . . . .
Using secure erase. . . . . . . . . . .
FDE security authorizations . . . . . . .
FDE terminology . . . . . . . . . . .
Before you begin . . . . . . . . . . .
Installing and configuring the DS TKLM Proxy
Code server . . . . . . . . . . . . . .
Starting, stopping, and restarting the DS TKLM
Proxy Code server. . . . . . . . . . .
Modifying the DS TKLM Proxy Code server
configuration file . . . . . . . . . . .
Installing the DS TKLM Proxy Code. . . . .
Installing the DS TKLM Proxy Code server in
a Windows environment . . . . . . .
Installing the DS TKLM Proxy Code server in
an AIX or Linux environment . . . . . .
Configuring disk encryption with FDE drives . .
Installing FDE drives . . . . . . . . . .
Enabling premium features . . . . . . . .
144
144
145
146
148
149
149
155
156
156
157
159
159
160
161
161
165
165
165
166
166
166
The Support Monitor interface. . . . .

Scheduling collection of the support bundle
Sending the support bundle to IBM support
Collecting the support bundle manually .
Using the Support Monitor log window .
Solving Support Monitor problems . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
175
181
183
187
190
191
191
191
192
192
193
193
193
194
194
194
194
198
199
200
201
202
204
Chapter 8. Troubleshooting . . . . . 205

Critical event problem solving. .
Retrieve trace buffers . . . . .
Configuration database validation
Database save/restore . . . .
Support Monitor troubleshooting .
DS Diagnostic Data Capture (DDC)
Recovery steps . . . . . .
DDC MEL events . . . . .
Resolving disk array errors on AIX
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
205
220
221
222
223
225
226
227
227
Appendix A. Host bus adapter

settings . . . . . . . . . . . . . . 231
Adjusting HBA settings . . . . . . . . .
Accessing HBA settings through Fast!UTIL .
Default host bus adapter settings . . . . .
Advanced HBA settings . . . . . . . .
QLogic host bus adapter settings . . . . . .
JNI and QLogic host bus adapter settings . . .
JNI HBA card settings . . . . . . . .
Configuration settings for
FCE-1473/FCE-6460/FCX2-6562/FCC2-6562
FCE-1063/FCE2-1063/FCE-6410/FCE2-6410
Configuration settings for FCI-1063 . . .
Configuration settings for FC64-1063 . .
QLogic HBA settings . . . . . . . . .
.
.
.
.
.
.
.
231
231
232
232
233
239
239
. 239
.
.
.
.
240
241
242
243
Appendix B. Using a storage

subsystem with a VMware ESX Server
configuration . . . . . . . . . . . 245
Contents
Sample configuration . . . . . . . . . . .
Software requirements . . . . . . . . . .
Management station . . . . . . . . . .
Host (VMware ESX Server) . . . . . . . .
Hardware requirements . . . . . . . . . .
VMware ESX Server restrictions . . . . . . .
Other VMware ESX Server host information . . .
Configuring storage subsystems for VMware ESX
Server . . . . . . . . . . . . . . . .
Cross-connect configuration for VMware
connections . . . . . . . . . . . . .
Mapping LUNs to a storage partition on
VMware ESX Server . . . . . . . . . .
Verifying the storage configuration for VMware
245
245
246
246
246
247
248
248
vi
.
.
.
.
.
.
. 253
. 253
.
.
.
.
.
.
.
253
259
260
260
260
260
260
248
249
249
Appendix C. Using the Storage

Manager with high-availability cluster
services. . . . . . . . . . . . . . 251
General information . . . . . . . . . .
Using cluster services on AIX systems . . . .
High-Availability Cluster Multi-Processing .
Software requirements . . . . . . .
Configuration limitations . . . . . .
Other HACMP usage notes. . . . . .
Parallel System Support Programs and General
Parallel File System . . . . . . . . .
Software requirements . . . . . . .
Configuration limitations . . . . . .
Other PSSP and GPFS usage notes . . .
GPFS, PSSP, and HACMP cluster configuration
diagrams . . . . . . . . . . . . .
Using cluster services on HP-UX systems . . .
Using cluster services on Solaris systems . . .
General Solaris requirements . . . . . .
System dependencies . . . . . . . . .
Adding RDAC IDs . . . . . . . .
Single points of failure . . . . . . .
Appendix D. Viewing and setting AIX

Object Data Manager (ODM) attributes 261
Attribute definitions . . . . . . . . . . . 261
Using the lsattr command to view ODM attributes 265
Appendix E. Accessibility . . . . . . 267
251
251
251
252
252
252
Notices . . . . . . . . . . . . . . 269
. 253
. 253
Index . . . . . . . . . . . . . . . 285
Trademarks . .
Important notes
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 271
. 271
Glossary . . . . . . . . . . . . . 273
Figures
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
Sample network using network-managed and

host-agent-managed storage subsystems . . . 3
Parts of the Enterprise Management window
12
Parts of the Subsystem Management window 16
Managing iSCSI settings . . . . . . . . 35
Subsystem Management Physical tab . . . . 52
Solid state disk (SSD) display . . . . . . 54
Protection Information (P) check points
55
Non-FDE T10PI drive - properties . . . . . 56
Enabling T10 PI on a logical drive . . . . . 58
RAID drive - Protection Information (T10 PI) enabled . . . . . . . . . . . . . . 59
Example - Logical Drive 4 of RAID array 4 T10PI not enabled . . . . . . . . . . 60
Disabling T10PI . . . . . . . . . . . 61
Non-T10PI FDE drive - properties . . . . . 62
FDE capable RAID array - security details
63
Assigning a port identifier for IBM i . . . . 73
Selecting IBM i as the host type . . . . . . 74
The Script Editor window. . . . . . . . 86
Host HBA to storage subsystem controller
multipath sample configuration for all
multipath drivers except AIX fcp_array and
Solaris RDAC . . . . . . . . . . . . 92
Host HBA to storage subsystem controller
multipath sample configuration for AIX
fcp_array and Solaris RDAC multipath drivers . 93
One-to-one zoning scheme . . . . . . . 95
One-to-two zoning scheme . . . . . . . 95
Security-enabled FDE drives: With the correct
authorizations in place, the reading and
writing of data occurs in Unlocked state . . 148
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
A security-enabled FDE drive is removed

from the storage subsystem: Without correct
authorizations, a stolen FDE disk cannot be
unlocked, and the data remains encrypted . .
Changing the security key . . . . . . .
Changing the security key - Complete
Drive properties - Secure FDE drive . . . .
Select file - LockKeyID . . . . . . . .
Drive properties - Unsecured FDE drive
Secure erase process . . . . . . . . .
External security key management topology
Console area . . . . . . . . . . . .
Sample VMware ESX Server configuration
Cross-connect configuration for VMware
connections . . . . . . . . . . . .
Cluster configuration with single storage
subsystemone to four partitions. . . . .
Cluster configuration with three storage
subsystemsone partition per subsystem . .
Cluster configuration with four storage
subsystemsone partition per subsystem . .
RVSD cluster configuration with two storage
subsystemstwo partitions per subsystem. .
HACMP/GPFS cluster configuration with one
storage subsystemone partition . . . . .
HACMP/GPFS cluster configuration with
two storage subsystemstwo partitions per
subsystem . . . . . . . . . . . .
148
150
151
152
154
155
157
161
198
245
249
254
255
256
257
258
259
vii
viii
Tables
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
Data shown in the table view . . . . . . 13

Nodes on the Logical tab . . . . . . . . 17
Controller status icons . . . . . . . . . 18
Storage enclosure type icons . . . . . . . 19
Types of nodes in the Topology pane . . . . 19
Node information in the Defined Mappings
pane . . . . . . . . . . . . . . . 20
Node information by type of node . . . . . 20
Storage Monitor-compatible subsystems and
controller firmware . . . . . . . . . . 24
Installation sequence of Storage Manager
software packages . . . . . . . . . . 29
Examples of Storage Manager package install
commands . . . . . . . . . . . . . 29
Storage Manager package installation verify
commands . . . . . . . . . . . . . 30
Summary of supported drive types, interfaces
and capabilities . . . . . . . . . . . 51
Protection Information metadata (8 bytes)
55
RAID level descriptions . . . . . . . . 64
Errors discovered during a media scan
79
Performance Monitor tuning options in the
Subsystem Management window . . . . . 81
Load balancing policies supported by
operating systems . . . . . . . . . . 81
Multipath driver by operating system . . . . 91
Number of paths each multipath driver
supports by operating system . . . . . . 93
Minimum version required for each
component . . . . . . . . . . . . . 98
Attributes and parameter values in the
multipath.conf file . . . . . . . . . 102
Options and parameters for the multipath
command . . . . . . . . . . . . . 103
Troubleshooting the Device Mapper . . . . 103
Sample record of logical drive preferred and
alternate paths . . . . . . . . . . . 108
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
Security authorizations . . . . . . . .
Full disk encryption terminology . . . . .
Proxy configuration file properties . . . .
Support Monitor icons . . . . . . . .
Support Monitor messages and descriptions
Critical events . . . . . . . . . . .
Problem index . . . . . . . . . . .
Recovery Step 2. . . . . . . . . . .
Recovery Step 4. . . . . . . . . . .
Recovery Step 5. . . . . . . . . . .
DDC MEL events . . . . . . . . . .
Disk array errors . . . . . . . . . .
QLogic model QLA234x, QLA24xx, QLE2462,
QLE2460, QLE2560, QLE2562, QMI2572,
QMI3572, QMI2582 . . . . . . . . .
QLogic model QL220x (for BIOS V1.81) host
bus adapter settings by operating system . .
FCE-1473/FCE-6460/FCX2-6562/FCC2-6562 .
FCE-1063/FCE2-1063/FCE-6410/FCE2-6410 .
Configuration settings for FCI-1063 . . . .
Configuration settings for FC64-1063
Configuration settings for QL2342 . . . .
Attributes for dar devices . . . . . . .
Attributes for dac devices . . . . . . .
Attributes for hdisk devices . . . . . . .
Example 1: Displaying the attribute settings
for a dar . . . . . . . . . . . . .
for a dac . . . . . . . . . . . . .
for an hdisk . . . . . . . . . . . .
Storage Manager alternate keyboard
operations . . . . . . . . . . . .
158
159
162
199
202
205
223
226
226
226
227
227
234
237
239
240
241
242
243
261
262
263
265
265
266
268
ix
About this document

This document provides information about how to plan, install, configure, and work with the IBM
System Storage DS Storage Manager Version 10.77 or earlier, with controller firmware version upto
7.77.xx.xx. If the controller firmware version of your storage subsystem is 7.8x.xx.xx or later, refer to IBM
System Storage DS Storage Manager Version 10.8 - Installation and Host Support Guide. This document
is intended for system and storage administrators who are responsible for installing storage
administration software. To install and manage a storage subsystem with Storage Manager, you must
have knowledge of redundant array of independent disks (RAID), small computer system interface
(SCSI), Fibre Channel, and SATA technology. You must also have working knowledge of the applicable
operating systems that are used with the management software.
Note:
Note: The screenshots in the guide are illustrative and may differ from the actual UI depending on the
Storage Manager and controller firmware versions.
Throughout this document, the term Storage Manager refers to all host software release levels.
Use this document to perform the following tasks:
v Determine the hardware and software that are required to install Storage Manager.
v Integrate the necessary hardware components into your network.
v Install the Storage Manager software.
v Upgrade controller firmware, if necessary.
v Identify and use storage-management features that are unique to your installation.
Important: Check the Storage Manager readme files for any updates to the list of supported operating
systems. See Finding Storage Manager software, controller firmware, and readme files on page xiii for
more information about how to access the Storage Manager readme files on the web.
For information about terminology, see the Help section of the Storage Manager Enterprise Management
window, the Subsystem Management window, or the Glossary on page 273.
As you read this document, it is important to understand the distinction between the following two
terms:
Management station
A management station is a system that is used to manage the storage subsystem. You can attach
it to the storage subsystem in either of the following ways:
v Through a TCP/IP Ethernet connection to the controllers in the storage subsystem
v Through a TCP/IP connection to the host-agent software that is installed on a host computer,
which in turn is either directly attached to the storage subsystem through the Fibre Channel
I/O path or through a TCP/IP Ethernet connection to the controllers
Host computer
A host computer is a system that is directly attached to the storage subsystem through a Fibre
Channel I/O path. This system is used to perform the following tasks:
v Serve data (typically in the form of files) from the storage subsystem
v Function as a connection point to the storage subsystem for a remote-management station
Note:
xi
1. The terms host and host computer are used interchangeably throughout this document.
2. A host computer can also function as a management station.
Related documentation
In addition to the information in this document, the resources that are described in the following sections
are available.
Storage Manager documentation on the IBM website

The following
v IBM System
v IBM System
v IBM System
documentation is available for download (PDF) on the IBM website:

Storage DS Storage Manager Command Line Interface and Script Commands Programming Guide
Storage DS Storage Manager Copy Services User's Guide
Storage DS4000 Fibre Channel and Serial ATA Intermix Premium Feature Installation Overview
To access these documents and other IBM System Storage documentation from the IBM Support Portal,
complete the following steps.
Note: The first time that you access the IBM Support Portal, you must choose the product category,
product family, and model numbers for your storage subsystems. The next time you access the IBM
Support Portal, the products you selected initially are preloaded by the website, and only the links for
your products are displayed. To change or add to your product list, click the Manage my product lists
link.
1. Go to http://www.ibm.com/support/entry/portal.
2. Under Choose your products, expand Hardware.
3. Click System Storage > Disk systems > Mid-range disk systems (for DS4000 or DS5000 storage
subsystems) or Entry-level disk systems (for DS3000 storage subsystems), and check the box for your
storage subsystem.
4. Under Choose your task, click Documentation.
5. Under See your results, click View your page.
6. In the Product documentation box, click the link for the publication that you want to access.
Storage Manager online help and diagnostics

You can access the help systems from the Enterprise Management and Subsystem Management windows
in the Storage Manager by clicking Help on the toolbar or pressing F1.
Enterprise Management Help window
Use this online help system to learn more about working with the entire management domain.
Subsystem Management Help window
Use this online help system to learn more about managing individual storage subsystems.
After you install Storage Manager, consider installing the host bus adapter (HBA) management and
diagnostic application, if available. The QLogic SANsurfer and Emulex HBAnyware applications are
diagnostic programs that you can use to verify the status of the I/O connections before you use the
storage subsystem.
If your storage subsystem is connected to a Fibre Channel HBA in the host server in a SAN environment,
consider purchasing the IBM Tivoli Storage Manager software application for SAN management and
troubleshooting.
xii
Finding Storage Manager software, controller firmware, and readme

files
The Storage Manager software and controller firmware versions are available on the Storage Manager
DVD, and can also be downloaded from the web.
Important: Before you install Storage Manager, review the readme file. Updated readme files contain the
latest device-driver versions, firmware levels, limitations, and other information that is not found in this
document.
To find firmware and readme files on the IBM Support Portal, complete the following steps:
Note: The first time that you access the IBM Support Portal, you must choose the product category,
product family, and model numbers for your storage subsystems. The next time you access the IBM
Support Portal, the products you selected initially are preloaded by the website, and only the links for
your products are displayed. To change or add to your product list, click the Manage my product lists
link.
1. Go to http://www.ibm.com/support/entry/portal.
2. Under Choose your products, expand Hardware.
3. Click System Storage > Disk systems > Mid-range disk systems, and select the check box for your
storage subsystem.
4. Click Select OS, check the corresponding box for your operating system, and click Submit.
5. Under Choose your task, click Downloads.
6. Under See your results, click View your page.
7. In the Product documentation box, click the link for the publication that you want to access.
IBM System Storage Productivity Center

The IBM System Storage Productivity Center (SSPC) is an integrated hardware and software solution that
provides a single point of entry for managing IBM System Storage DS3000 systems, DS4000 systems,
DS5000 systems, DS8000 systems, IBM System Storage SAN Volume Controller clusters, and other
components of your data storage infrastructure. Therefore, you can use the IBM System Storage
Productivity Center to manage multiple IBM System Storage product configurations from a single
management interface.
To learn how to integrate Storage Manager with the IBM System Storage Productivity Center, see the IBM
System Storage Productivity Center Information Center at the following website:
publib.boulder.ibm.com/infocenter/tivihelp/v4r1/index.jsp
Essential websites for support information

The most up-to-date information about your IBM storage subsystems and Storage Manager, including
documentation and the most recent software, firmware, and NVSRAM downloads, can be found at the
following websites:
IBM System Storage Disk Storage Systems
Find links to software and firmware downloads, readme files, and support pages for all IBM
System Storage disk storage systems:
http://www.ibm.com/systems/support/storage/disk
About this document
xiii
IBM System Storage Interoperation Center (SSIC)

Find technical support information for your specific storage subsystem and host configuration,
including the latest firmware versions for your system, with this interactive web-based utility:
http://www.ibm.com/systems/support/storage/config/ssic
IBM DS3000, DS4000, DS5000, and BladeCenter Boot Disk System Premium Feature Activation
Activate a premium feature with this web-based utility:
http://www.ibm.com/storage/fasttkeys
IBM System Storage Productivity Center
Find the latest documentation for the IBM System Storage Productivity Center, a new system that
is designed to provide a central management console for IBM System Storage DS3000, DS4000,
DS5000, DS8000, and SAN Volume Controller:
publib.boulder.ibm.com/infocenter/tivihelp/v4r1/index.jsp
IBM System Storage Support
Find the latest support information for host operating systems, HBAs, clustering, storage area
networks (SANs), Storage Manager software and controller firmware:
www.ibm.com/systems/support/storage
Storage Area Network (SAN) Support
Find information about using SAN switches, including links to SAN documentation:
www.ibm.com/systems/support/storage/san
Support for IBM System p AIX 5L and Linux servers
Find the latest support information for System p AIX, Linux, BladeCenter, and i5/OS servers:
www.ibm.com/systems/support/supportsite.wss/brandmain?brandind=5000025
Support for IBM System x servers
Find the latest support information for System x Intel- and AMD-based servers:
http://www.ibm.com/systems/support/
System p and AIX Information Center
Find information about how to use AIX with System p and POWER servers:
publib.boulder.ibm.com/infocenter/pseries/index.jsp?
IBM System Storage products
Find information about all IBM System Storage products:
www.ibm.com/systems/storage
IBM Publications Center
Find IBM publications:
www.ibm.com/shop/publications/order/
Getting information, help, and service

If you need help, service, or technical assistance or just want more information about IBM products, you
will find a wide variety of sources available from IBM to assist you. This section contains information
about where to go for additional information about IBM and IBM products, what to do if you experience
a problem with your system, and whom to call for service, if it is necessary.
xiv
Before you call

Before you call, take these steps to try to solve the problem yourself:
v Check all cables to make sure that they are connected.
v Check the power switches to make sure that the system is turned on.
v Use the troubleshooting information in your system documentation, and use the diagnostic tools that
come with your system.
v Check for technical information, hints, tips, and new device drivers at the IBM System Storage Disk
Support website pages that are listed in this section.
v Use an IBM discussion forum on the IBM website to ask questions.
You can solve many problems without outside assistance by following the troubleshooting procedures
that IBM provides in the Storage Manager online help or in the documents that are provided with your
system and software. The information that comes with your system also describes the diagnostic tests
that you can perform. Most subsystems, operating systems, and programs come with information that
contains troubleshooting procedures and explanations of error messages and error codes. If you suspect a
software problem, see the information for the operating system or program.
Using the documentation

Information about your IBM system and preinstalled software, if any, is available in the documents that
come with your system; this includes printed books, online documents, readme files, and help files. See
the troubleshooting information in your system documentation for instructions for using the diagnostic
programs. The troubleshooting information or the diagnostic programs might tell you that you need
additional or updated device drivers or other software.
Software service and support

Through IBM Support Line, for a fee you can get telephone assistance with usage, configuration, and
software problems. For information about which products are supported by Support Line in your country
or region, go to the following website:
www.ibm.com/services/sl/products
For more information about the IBM Support Line and other IBM services, go to the following websites:
v www.ibm.com/services
v www.ibm.com/planetwide
Hardware service and support

You can receive hardware service through IBM Integrated Technology Services or through your IBM
reseller, if your reseller is authorized by IBM to provide warranty service. Go to the following website for
support telephone numbers:
www.ibm.com/planetwide
In the U.S. and Canada, hardware service and support is available 24 hours a day, 7 days a week. In the
U.K., these services are available Monday through Friday, from 9 a.m. to 6 p.m.
About this document
xv
Notices and statements in this document

This document contains the following notices, which highlight key information:
v Note: These notices provide important tips, guidance, or advice.
v Important: These notices provide information that might help you avoid inconvenient or problem
situations.
v Attention: These notices indicate possible damage to programs, devices, or data. An attention notice is
placed just before the instruction or situation in which damage could occur.
v Caution: These statements indicate situations that can be potentially hazardous to you. A caution
statement is placed just before the description of a potentially hazardous procedure step or situation.
Receiving product updates and support notifications

Download the latest versions of the following packages at the time of initial installation and when
product updates become available:
v Storage Manager host software
v Storage subsystem controller firmware
v Drive storage expansion enclosure ESM firmware
v Drive firmware
Important: Keep your systems current with the latest firmware and other product updates by subscribing
to receive support notifications. Go to the following website and click My notifications for more
information about how to register for support notifications:
http://www.ibm.com/systems/support
You can also find product updates and support notifications if you use the IBM Support Portal website
at:
http://www.ibm.com/support/entry/portal
xvi

The following information helps you to prepare for the successful installation of the Storage Manager
software.
v Storage Manager software
v Supported controller firmware on page 2
v Types of installation configurations on page 2
v Setting up controller addresses for software installation on page 6
Introduction
The IBM System Storage DS Storage Manager consists of a set of client and host tools that you can use to
manage the IBM DS3000, DS4000, and DS5000 Storage Subsystems from a management station.
The Storage Manager is supported on the following operating systems:
v AIX
v Windows 2003 and Windows 2008
v Linux (RHEL and SLES)
v HP-UX
v Solaris
The DS3000, DS4000, and DS5000 Storage Subsystems are also supported when they are attached to
NetWare, Apple Mac OS, VMware ESX Server, and System p Virtual IO Server (VIOS) hosts, as well as on
i5/OS as a guest client on VIOS. IBM does not provide host software for these operating systems. You
must install IBM DS Storage Manager on a management station which has one of the operating systems
listed above installed.
Information about i5/OS support can be found at the following website:
www.ibm.com/systems/i/os/
For additional information, see the System Storage Interoperation Center at the following website:
Storage Manager software

Storage Manager is used to configure, manage, and troubleshoot storage subsystems. It is used primarily
to configure RAID arrays and logical drives, assign logical drives to hosts, replace and rebuild failed disk
drives, expand the size of the arrays and logical drives, and convert from one RAID level to another.
Storage Manager enables troubleshooting and management tasks, such as checking the status of the
storage subsystem components, updating the firmware of the RAID controllers, and managing the storage
subsystem. Finally, the Storage Manager offers access to premium features such as FlashCopy,
VolumeCopy, and Enhanced Remote Mirroring.
For the latest firmware versions that are supported by each storage subsystem model, see the readme file
for your operating system.
Storage Manager software components

Storage Manager includes the following client software components.
Note: Storage Manager components might vary depending on the operating system. For Storage
Manager version 10.77.xx.xx and later, the Microsoft MPIO DSM installer is separate from the Storage
Manager installer that lets you install the components listed below. However, the Storage Manager
installer and the Microsoft MPIO DSM installer are bundled in a single code package. This code package
is available on the IBM support portal.
SMruntime software
Storage Manager Java compiler
SMesm software
Storage Manager ESM firmware delivery package
SMclient software
Storage Manager client package
SMagent software
Storage Manager agent package
SMutil software
Storage Manager utility package
Storage Manager Profiler Support Monitor
The Storage Manager Profiler Support Monitor tool (Support Monitor) is a component of Storage
Manager version 10.60.x5.17 and later. In addition to the Storage Manager Profiler Support
Monitor code, the Apache Tomcat web server and MySQL database software packages are
installed as part of the tool. For more information about the Support Monitor tool, see Chapter 7,
Configuring and using the Support Monitor, on page 197.
Supported controller firmware

All controller firmware versions are available at no cost on the IBM website.
To achieve the highest level of compatibility and error-free operation, make sure that the controller
firmware for your storage subsystem is the latest firmware version for the storage subsystem model.
Important: DS4000 and DS5000 storage subsystems support Storage Manager version 10.50.xx.xx and
later, and controller firmware 5.41.xx.xx and later. Controller firmware versions earlier than 5.41.xx.xx are
no longer supported on these subsystems.
For detailed information about how to download the most current firmware version level, see
Downloading controller firmware, NVSRAM, ESM firmware on page 38.
Types of installation configurations

A management station can be either of the following configurations:
Network configuration (out-of-band)
A remote system, connected to an Ethernet network, that is used to manage one or more storage
subsystems.
Direct-attached or SAN-attached configuration (in-band or out-of-band)
A host that is connected to a storage subsystem through a Fibre Channel, iSCSI, or SAS
input/output (I/O) path. This host can use either the I/O path (in-band) or its Ethernet network
ports (out-of-band).
Network configuration
Before you begin installing the Storage Manager software, make sure that the network components are set
up and operating properly and that you have all of the host and controller information that is necessary
for the correct operation of the software.
Note: When you connect the storage subsystem to an Ethernet switch, set the switch port settings to
auto-negotiate.
Figure 1. Sample network using network-managed and host-agent-managed storage subsystems
Reviewing a sample network configuration

Figure 1 shows an example of a network that contains both a network managed storage subsystem
(Network A) and a host-agent-managed storage subsystem (Network B).
Network-managed storage subsystem: Network A is a network-managed storage subsystem. Both the
management station and the storage subsystem are connected to the Ethernet network. Network A
contains the following components:
v A DHCP/BOOTP server
v A network-management station for Simple Network Management Protocol (SNMP) traps
v A host that is connected to a storage subsystem through a Fibre Channel I/O path
v A management station that is connected by an Ethernet cable to the storage subsystem controllers
Note: If the controller static TCP/IP addresses or default TCP/IP addresses are used, you do not have to
set up the DHCP/BOOTP server.
Host-agent-managed storage subsystem: Network B is a host-agent-managed storage subsystem. You can

manage the storage subsystem using the same path, fibre channel or SAS, that a host server uses to send
I/O between the host and the storage subsystem using the Storage Manager agent software that is
installed in the host server. The storage subsystem Ethernet management ports are not normally
connected to the Ethernet network.
The Storage Manager agent requires a special LUN be assigned/mapped to the host partition. This LUN
is referred to as Access or UTM LUN and is used by the Storage Manager agent and the controller to
pass management information. This LUN is automatically assigned to the host partition as LUN 31 the
first time a logical drive is assigned to a host partition. Because the LUN has reduced the maximum
number of LUN/logical drives that can be assigned to a host by one, use the storage subsystem
management GUI to unassign it if the storage subsystem is managed solely via out-of-band method.
Note: The storage subsystem can be managed in-band and out-of-band at the same time.
Network B contains the following components:
v A host that is connected to a storage subsystem through a supported I/O path
v A management station that is connected by an Ethernet cable to the host computer
Setting up a management station

The management station is the server that is responsible for managing all of, or a portion of, a storage
network. It communicates with the network management agents in the managed nodes, using a network
management protocol such as Simple Network Management Protocol (SNMP).
Storage management commands are sent to the storage subsystem controllers, where the controller
firmware validates and runs the commands and then returns status and configuration information to the
client software.
Setting up a network-managed (out-of-band) configuration

The following steps provide an overview of the tasks that are required to set up the network for
installation of a network-managed (out-of-band) configuration:
Important: A maximum of eight management stations can concurrently monitor an out-of-band-managed
storage subsystem. This limit does not apply to servers that manage the storage subsystem through the
in-band-management method.
1. Install all of the hardware components (host computers, storage subsystems, and cables) that you
want to connect to the network. For more information about installing hardware components, see the
documentation that came with the hardware components.
2. Establish a naming convention for the storage subsystems that will be connected to the network.
3. Record the storage subsystem names and management types.
6.
7.
8.
Note: Throughout the remaining steps, you must record some information for future use, such as the
hardware Ethernet and IP addresses.
Determine the hardware Ethernet MAC address for each controller in storage subsystems connected to
the network. If you are using a default controller IP address, go to step 6. Otherwise, obtain the
TCP/IP address and host name for each of the controllers in the storage subsystems on the network
from the network administrator.
Set up the DHCP/BOOTP server to provide network configuration information for a specific
controller. If you are using static controller IP addresses, skip this step.
Verify that the TCP/IP software is installed.
Set up the host or domain name server (DNS) table.
Turn on the power to the devices that are connected to the network.
4.
5.
Setting up a host-agent-managed (in-band) configuration

The following steps provide an overview of the tasks that are required to set up an installation of a
host-agent-managed (in-band) configuration:
1. Install all of the hardware components (host computers, storage subsystems, and cables) that you
want to manage. For more information about installing hardware components, see the documentation
that came with the hardware components. The host computer must have configured I/O connections
to the storage subsystem (for example, the host must have an operating system installed with the
applicable device driver for the host bus adapters).
2. Install the Storage Manager host software and the Storage Manager agent software.
3. Establish a naming convention for the storage subsystems that will be connected to the network.
4. Record the storage subsystem names and management types.
Note: Throughout the remaining steps, you must record some information for future use, such as the
hardware Ethernet and IP addresses.
5. Obtain the IP address and host name of the host computer on which the host-agent software will run
from the network administrator.
Note: SMagent is part of the Storage Manager software package and is required on the host that is
connected to the storage subsystem through any of the supported interfaces.
6. Verify that the TCP/IP software is installed.
7. Turn on the power to the devices that are connected to the network.
Note: Even though you do not connect the host and the storage subsystems management Ethernet ports
to the network, the host still uses TCP/IP to communicate with the host-agent. The host-agent
communicates with the controller over the Fibre Channel connection through the access volume.
Direct-attached and SAN-attached configurations

Storage Manager supports in-band management of storage subsystems in direct-attached configurations
or in a SAN environment through switches.
Setting up a direct-attached configuration

Important: Storage subsystems with iSCSI ports do not support direct-attached connections from the host
systems to the storage subsystem iSCSI ports.
Before you begin, verify that:
v You can connect one or two servers to the storage subsystems.
v No external switches or external Fibre Channel hubs are being used.
v Only the DS4400 and DS4500 Storage Subsystems have mini-hubs. Two-server DS4400 or DS4500
configurations require four host-side mini-hubs, with exactly one connection from each HBA to a
mini-hub.
v See the Installation and User's Guide for your storage subsystem for more information.
Complete the following steps to set up a direct-attached configuration:
1. Connect the HBAs to each controller or mini-hub port of the storage subsystem.
2. Use the Storage Manager automatic discovery feature to make sure that the storage subsystem is
discovered.
Setting up a SAN-attached configuration

A SAN-attached configuration can consist of Fibre Channel, SAS, or iSCSI connections.
If you use Fibre Channel HBAs in your SAN-attached configuration, the HBA and the storage subsystem
host port connections should be isolated in fabric zones to minimize the possible interactions between the
ports in a SAN fabric environment. Multiple storage subsystems can be configured to the same set of
HBAs through a Fibre Channel, SAS, or Ethernet switch. For more information about Fibre Channel
zoning schemes, see Connecting HBAs in a Fibre Channel switch environment on page 94. Similar
zoning schemes can be implemented with SAS and Ethernet switches also.
Attention: A single-HBA configuration can result in loss of data access in the event of a path failure. If
you have a single HBA in a SAN-attached configuration, both controllers in the storage subsystem must
be connected to the HBA through a switch, and both controllers must be within the same SAN zone as
the HBA.
Complete the following steps to set up a SAN-attached configuration:
1. Connect the HBAs to the switch or switches.
2. Connect the storage subsystems to the switch or switches.
3. Set the required zoning or VLANs on the Fibre Channel switches or Ethernet switches, if applicable.
4. Use the Storage Manager automatic discovery feature to make sure that the storage subsystem is
discovered.
Setting up controller addresses for software installation

How you plan to manage the storage subsystems determines where you must install the software
components. Before you can install software components, you must assign IP addresses for the storage
controllers.
Note:
1. The controllers must be connected to a LAN port that is set to auto-negotiate the data rate. The
controllers do not function properly when they are connected to a switch port that is set for a fixed
rate.
2. To manage storage subsystems through a firewall, configure the firewall to open port 2463 to TCP
data.
Setting up IP addresses for storage subsystem controllers

Complete the following procedures after you install SMruntime and SMclient, as described in the
installation section for your host operating system.
You must set up a DHCP or BOOTP server and network with the following components:
v A DHCP or BOOTP server
v A network-management station for Simple Network Management Protocol (SNMP) traps
Note: You can avoid DHCP/BOOTP server and network tasks by assigning static IP addresses to the
controller. If you do not want to assign static TCP/IP addresses with the Storage Manager, using the
storage subsystem default TCP/IP addresses as shown in Assigning static TCP/IP addresses to a storage
subsystem using factory-default management port TCP/IP address on page 8, establish an in-band
management connection to the storage subsystem and change the management port IP address in
Subsystem Management window.
If a controller has two management ports, the same gateway address is shared between the two ports.
The most recently obtained or supplied gateway address is used for both ports. Therefore, it is possible to
lose access on one port as a result of changing the configuration on the other port. If both ports are
manually configured, the most recently supplied gateway address will be used. If one port is manually
configured and DHCP is enabled on the other port, the most recently supplied or obtained gateway
address will be used. Generally, this is the gateway address supplied by the DHCP server unless the
manual configuration for the other port is changed. In this case, the gateway address should be set to the
value provided by the controller, which should match the gateway address obtained from the DHCP
server. If DHCP is enabled on both ports, the DHCP servers attached to the two ports should be
configured to supply the same gateway address. If the DHCP servers apply different gateway addresses,
the most recently obtained gateway address will be used for both ports.
Any changes to remote login access affect both ports. In other words, if remote login access is enabled or
disabled on one port, it is also enabled or disabled on the other port. As with the gateway address, the
most recent configuration applied for remote login applies to both ports. For example, if remote login
access is manually enabled on port 1, it will also be enabled for port 2. If a DHCP server subsequently
supplies configuration parameters for port 2 that includes disabling remote login access, it will be
disabled for both ports.
If a controller has two management ports, the two Ethernet ports must be on different subnets. If both
ports are on the same subnet, or if they have the same network address (the logical AND of the IP
address and the subnet mask), Subnet Configuration Error event notification will occur.
Setting up an IP address with the DHCP/BOOTP server

Complete the following steps to set up the DHCP/BOOTP server and network:
1. Get the MAC address from each storage subsystem controller. (See the Identifying Ethernet MAC
addresses procedure.)
2. Complete whichever of the following steps is applicable for your server:
v On a DHCP server, create a DHCP record for each of the MAC addresses. Set the lease duration to
the longest time possible.
v On a BOOTP server, edit the bootptab file to add the entries that associate the MAC address tab
with the TCP/IP address.
3. Connect the DS3000, DS4000, or DS5000 storage subsystem Ethernet ports to the network.
4. Boot the storage subsystem.
Identifying Ethernet MAC addresses

To manage your storage subsystem with the direct-management method, you must identify the hardware
Ethernet medium access control (MAC) address for each controller.
Every storage subsystem has a label with the hardware Ethernet MAC address number. The number has
the format xx.xx.xx.xx.xx.xx, where x represents a letter or a number. For example, an Ethernet MAC
address might be 00.a0.b8.20.00.d8.
Instructions and label locations for particular storage subsystems are listed in the following sections.
Identifying the Ethernet MAC addresses on a DS4800, DS5100, or DS5300 storage subsystem: The
machine type, model number, and serial number are on top of each RAID controller unit. The MAC
addresses are near the Ethernet ports on each RAID controller.
Note: You can access the controllers from the back of a DS4800, DS5100, or DS5300 chassis.
Identifying the Ethernet MAC addresses on a DS3000, DS3500, DCS3700, DS3950, DS4200, DS4700, or
DS5020 storage subsystem: The MAC addresses on these storage subsystems are near the Ethernet ports
on each RAID controller.
Note: You can access the controllers from the back of the storage subsystem chassis.
Identifying the Ethernet MAC addresses on a DS4400, or DS4500 storage subsystem: To identify the
hardware Ethernet MAC addresses for DS4400 and DS4500 storage subsystems, complete the following
steps:
1. Remove the front bezel from the storage subsystem and carefully pull the bottom of the bezel out to
release the pins. Then slide the bezel down.
2. On the front of each controller, look for a label with the hardware Ethernet MAC address. The
number is in the form xx.xx.xx.xx.xx.xx (for example, 00.a0.b8.20.00.d8).
3. Record each Ethernet MAC address.
4. To replace the bezel, slide the top edge under the lip on the chassis. Then push the bezel bottom until
the pins snap into the mounting holes.
Identifying the Ethernet MAC addresses on a DS4100, or DS4300 storage subsystem: To identify the
hardware Ethernet MAC address for machine types 3542 ( DS4100, or 1722 (DS4300), complete the
following steps:
1. Locate the Ethernet MAC address at the back of the unit, under the controller Fibre Channel host
ports. The number is in the form xx.xx.xx.xx.xx.xx (for example, 00.a0.b8.20.00.d8).
2. Record each Ethernet MAC address.
Assigning static TCP/IP addresses to a storage subsystem using

factory-default management port TCP/IP address
Complete the following steps to assign static TCP/IP addresses to the storage subsystem controllers,
using the default TCP/IP addresses that are assigned to the controllers when they are manufactured:
1. Make a direct-management connection to the storage subsystem, using the default TCP/IP addresses
for the controllers. To find the default TCP/IP addresses for your storage subsystem, see the
Installation and User's Guide that came with the hardware.
v Controller A: 192.168.128.101
v Controller B: 192.168.128.102
v Subnet Mask: 255.255.255.0
Note: For a storage subsystem that has two Ethernet ports per controller (such as the DCS3700,
DS5020, DS3500, DS5100 and DS5300), use the Ethernet port that is labeled #1. The default IP
addresses of the second Ethernet port are as follows:
v Controller A: 192.168.129.101
v Controller B: 192.168.129.102
v Subnet Mask: 255.255.255.0
2. Start SMclient. The Enterprise Management window opens.
3. In the Enterprise Management window, click the name of the default storage subsystem. The
Subsystem Management window opens.
4. In the Subsystem Management window, right-click the controller icon and select Change > Network
Configuration in the menu. The Change Network Configuration window opens.
5. In the Change Network Configuration window, click the Controller A and Controller B tabs and type
the new TCP/IP addresses in the applicable fields. Click OK.
6. Close the Subsystem Management window, wait 5 minutes, and delete the default storage subsystem
entry in the Enterprise Management window.
7. Add a new storage subsystem entry in the Enterprise Management window, using the new TCP/IP
address.
Assigning static TCP/IP addresses storage subsystem using an

in-band management connection
For a host that is connected to a storage subsystem through a Fibre Channel I/O path, complete these
steps to assign static TCP/IP addresses to the storage subsystem controllers by way of the host that has
Fibre Channel connectivity to the storage subsystem Fibre Channel host port.
To complete this procedure, you must have the following components:
Note: You cannot perform in-band management with a host that has iSCSI connections to the storage
subsystem until it is configured. Instead, use other methods in this section to assign static TCP/IP
address to the storage subsystem controller management ports.
1. Install the DS Storage Manager client software in the host, and make sure that the SMagent software
is installed and running.
2. Start the DS Storage Manager client software. The Enterprise Management window opens.
3. Add the storage subsystem to the Enterprise Management domain using the IP address of the host
that has Fibre Channel connectivity to the storage subsystem.
4. In the Enterprise Management window, click on the name of the newly-discovered storage
subsystem. The Subsystem Management window opens.
5. In the Subsystem Management window, right-click the Controller icon and select Change > Network
Configuration in the drop-down menu. The Change Network Configuration window opens.
6. In the Change Network Configuration window, click on the Controller A and Controller B tabs and
type the new TCP/IP addresses in their applicable fields.
7. Click OK.
8. Close the Subsystem Management window.
9. Wait at least five minutes.
10. Delete the existing storage subsystem entry in the Enterprise Management window.
11. If applicable, change the IP address of the Ethernet port in the management station to a value that is
on the same TCP/IP subnet as the controller Ethernet port IP addresses that you just assigned.
12. Exit DS Storage Manager.
13. Restart.
14. Make Ethernet cabling to the controller management ports.
15. Add a new storage subsystem entry in the Enterprise Management window, using the new assigned
IP addresses.
Assigning static TCP/IP addresses using the storage subsystem

controller serial port Service Interface
Note: To manage storage subsystems through a firewall, configure the firewall to open port 2463 to TCP
data.
To complete this procedure, you must have the following components:
v A null modem cable with DB-9 female connectors on both ends, used to connect the host serial port to
the controller serial port.
v A terminal emulation software application, such as Procomm or Microsoft Windows Hyperterm,
installed in the host system.
Note:
1. The terminal session setting must have these values: 38400 BAUD; 8 data bits; 1 stop bit; no parity.
2. If the controller BAUD rate setting is different from the terminal setting, send a "break" character to
cause the controller to switch to the next available BAUD rate setting. Repeat sending the "break"
character until the "Press space to set the BAUD rate" message is displayed.
v Controller firmware version 7.77.xx.xx or higher and its associated NVSRAM files installed.
Complete the following steps to view and assign new IP address to the controller management port:
1. Press Enter. If this character (->) is displayed, type Exit and press Enter. Otherwise, continue to next
step.
2. In the terminal emulator session, send the "break" character. For example, use CNTL+BREAK for
Microsoft Windows Hyperterm or ALT+B for Procomm.
3. Enter the uppercase letter S and press Enter when the following message is displayed: Press within 5
seconds: for <S> Service Interface, <BREAK> for baud rate.
4. Enter the password DSStorage (case sensitive) within 60 seconds of when this message is displayed:
Enter the password to access the Service Interface (60 second timeout).
Note: If the controller does not have controller firmware version 7.77.xx.xx or higher and its
associated NVSRAM files installed, this password will not be accepted, and you must follow one of
the two methods to change the IP configuration of controller Ethernet ports. See Assigning static
TCP/IP addresses to a storage subsystem using factory-default management port TCP/IP address on
page 8 and Assigning static TCP/IP addresses storage subsystem using an in-band management
connection on page 9 for more information.
5. Enter 1 or 2 to display or change the IP configuration when the following menu is displayed:
Service Interface Main Menu
==============================
1) Display IP Configuration
2) Change IP Configuration
3) Reset Storage Array Administrator Password
Q) Quit Menu
If option 2 is chosen, follow the prompt to set the IP configuration for the port that you selected. You
must reboot the controller for the settings to take effect.
Note: You must perform these steps on both controllers.
10
Chapter 2. The Storage Manager interface

This chapter describes the basic layout of the Storage Manager software.
Storage Manager has two windows that provide management functionality and a graphical representation
of your storage subsystems: the Enterprise Management window and the Subsystem Management
window.
Use the Enterprise Management window to add the storage subsystems that you want to manage and
monitor. Through the Enterprise Management window, you receive alert notifications of critical errors
that are affecting the storage subsystems. If you are notified in the Enterprise Management window that a
storage subsystem has a non-optimal status, you can open the Subsystem Management window for the
affected storage subsystem to see detailed information about the storage subsystem condition.
Important: Depending on your version of Storage Manager, the views, menu options, and functionality
might differ from the information that is presented in this document. For information about available
functionality, see the online help topics in your version of Storage Manager.
Enterprise Management window

The Enterprise Management window is the first window that opens when you start Storage Manager.
Use the Enterprise Management window to complete the following management tasks:
v Discover hosts and storage subsystems automatically on your local subnetwork
v Manually add and remove hosts and storage subsystems
v Monitor the health of the storage subsystems and report a high-level status with the applicable icon
v Configure alert notifications through email or Simple Network Management Protocol (SNMP) and
report critical events to the configured alert destinations
Note: A local configuration file stores all of the information about storage subsystems that you have
added and any email destinations or SNMP traps that you have configured.
v Open the applicable Subsystem Management window for a selected storage subsystem to perform
detailed configuration and management operations
v Execute scripts to perform batch management tasks on a particular storage subsystem
Note: For example, you might run scripts to create new logical drives or to download new controller
firmware. For more information about executing scripts, see the IBM System Storage DS Storage Manager
Command Line Interface and Script Commands Programming Guide or the online help topics in the
Enterprise Management window.
v Upgrade controller firmware between major controller firmware versions (for example, upgrading
controller firmware from version 6.xx.xx.xx to 7.xx.xx.xx). This functionality is the same as that of the
stand-alone IBM System Storage Controller Firmware upgrade tool. This tool is integrated into the IBM
DS Storage Manger client version 10.50.xx.xx and later.
11
Toolbar
Device tab
(icons for common commands) (storage subsystem status)
Setup tab
(shortcuts to storage
manager tasks)
Enterprise Management
window title bar
Shortcuts
to common
tasks
Status bar
Figure 2. Parts of the Enterprise Management window
Using the Devices tab

The Devices tab in the Enterprise Management window presents two views of the storage subsystems
that are managed by the management station: a tree view and a table view.
12
Tree view
The tree view provides a hierarchical view of the nodes in the storage subsystem. The tree view shows
two types of nodes:
v Discovered Storage Subsystems
v Unidentified Storage Subsystems
The Discovered Storage Subsystems node and the Unidentified Storage Subsystems node are child nodes
of the Management Station node.
The Discovered Storage Subsystems node has child nodes that represent the storage subsystems that are
currently managed by the management station. Each storage subsystem is labeled with its machine name
and is always present in the tree view. When storage subsystems and hosts with attached storage
subsystems are added to the Enterprise Management window, the storage subsystems become child
nodes of the Discovered Storage Subsystems node.
Note: If you move the mouse over the Discovered Storage Subsystems node, a tooltip appears displaying
the controller IP address.
The Unidentified Storage Subsystems node shows storage subsystems that the management station
cannot access because of network connection problems, turned off subsystem, or a non-existent name.
You can perform these actions on the nodes in the tree view:
v Double-click the Management Station node and the Discovered Storage Subsystems node to expand or
collapse the view of the child nodes.
v Double-click a storage subsystem node to launch the Subsystem Management window for that storage
subsystem.
v Right-click the Discovered Storage Subsystems node to open a menu that contains the applicable
actions for that node.
The right-click menu for the Discovered Storage Subsystems node contains these options:
v Add Storage Subsystem
v Automatic Discovery
v Configure Alerts
v Refresh
These options are also included with the other options in the Edit and Tools menu options. For more
information, see the Using the Enterprise Management window online help topic.
Table view
In the table view, each storage subsystem is a single row in the table. The columns in the table view show
data about the managed storage subsystem.
Table 1. Data shown in the table view
Column
Description
Name
The name of the managed storage subsystem

Note: If the managed storage subsystem is unnamed, the default name
is Unnamed.
Type
The type of managed storage subsystem, represented by an icon
Status
An icon and a text label that report the true status of the managed
storage subsystem
13
Table 1. Data shown in the table view (continued)

Column
Management Connections
Description
The following connection types are possible:
v Out-of-Band: this storage subsystem is an out-of-band storage
subsystem.
v In-Band: this storage subsystem is an in-band storage subsystem that
is managed through a single host.
v Out-of-Band, In-Band: this storage subsystem is a storage subsystem
that is both out-of-band and in-band.
Click Details to see more information about any of these connections.
Comment
Any comments that you have entered about the specific managed
storage subsystem
Sort the rows in the table view in ascending order or descending order by either clicking a column
heading or by selecting one of these menu options:
v View > By Name
v View > By Status
v View > By Management Connection
v View > By Comment
To change the way that managed storage subsystems appear in the table view, complete one of the
following actions:
v To show all of the known managed storage subsystems in the table view, select the Management
Station node.
v To show only that storage subsystem in the table view, select a storage subsystem node in the tree
view.
Note: Selecting an Unidentified node in the tree view shows an empty table view.
Using the Setup tab

The Enterprise Management window Setup tab is a gateway to tasks that you can perform when you set
up a storage subsystem. Use the Enterprise Management window Setup tab to perform the following
tasks:
v Add a storage subsystem
v Name or rename a storage subsystem
v Configure an alert
v Open the Subsystem Management window to manage a storage subsystem
v Upgrade controller firmware
v Open the Inherit Systems Settings window
Subsystem Management window

The Subsystem Management window is Java technology-based software that is launched from the
Enterprise Management window. Each Subsystem Management window provides management functions
for a single storage subsystem. You can have more than one Subsystem Management window open to
manage different storage subsystems. The Subsystem Management window includes the following
functions:
v Access storage subsystem options, such as locating a storage subsystem, configuring a storage
subsystem, renaming a storage subsystem, or changing a password
14
v Configure drives from your storage subsystem capacity, define hosts and host groups, and grant host
or host group access to sets of drives called storage partitions
v Monitors the health of storage subsystem components and reports a detailed status using applicable
icons
v Access the applicable recovery procedures for a failed logical component or a failed hardware
component
v View the event log for the storage subsystem
v View profile information about hardware components, such as controllers and drives and get a
physical view of the drives in the hardware enclosures
v Access controller-management options, such as changing ownership of logical drives or placing a
controller online or offline
v Access drive-management options, such as assigning hot spares and locating the drive
v Monitor storage subsystem performance
v Configure copy services like Flashcopy, VolumeCopy, and Remote Mirroring
If the storage subsystem has controller firmware version 7.70.xx.xx, its Subsystem Management window
cannot be opened unless a strong password is provided. A strong password must be between 8 and 30
characters and contain at least one number, one lower-case letter, one upper-case letter, and one
non-alphanumeric character (for example, < > ! @ + #). Spaces are not permitted, and it is case-sensitive.
In storage subsystems with controller firmware other than 7.70.xx.xx, you are prompted to provide this
password, if none is specified for the storage subsystem, whenever you attempt to open a Subsystem
Management window for this storage subsystem. IBM recommends creating a subsystem management
password to prevent unauthorized changes to the Subsystem Management configuration.
Opening the Subsystem Management window

To open a Subsystem Management window from the Enterprise Management window, perform one of
the following actions:
v Click the Devices tab, and double-click the name of the storage subsystem that you want to manage.
v Click the Devices tab, right-click the name of the storage subsystem that you want to manage, and
select Manage Storage Subsystem.
v Click the Devices tab, and select Tools > Manage Storage Subsystem.
v Click the Setup tab, and select Manage Storage Subsystem. In the Select Storage Subsystem window,
select the name of the storage subsystem that you want to manage, and click OK.
You can manage only a single storage subsystem within a Subsystem Management window. However,
you can open more than one Subsystem Management window from the Enterprise Management window
to simultaneously manage multiple storage subsystems.
The Subsystem Management window provides the following options for managing your storage
subsystem.
15
Storage
subsystem
name
Subsystem
Management
window title bar
Subsystem
Management
tabs
Toolbar
(icons for
common
commands)
Storage
subsystem
name and
status
Shortcuts
to common
tasks
Figure 3. Parts of the Subsystem Management window
Using the Summary tab

The Summary tab in the Subsystem Management window shows information about the storage
subsystem. The Summary tab also includes links to the Storage Subsystem Profile window, relevant
online help topics, and the storage concepts tutorial. The link to the Recovery Guru window is also
shown, when the storage subsystem needs attention.
On the Summary tab, you can view this information:
v
v
v
v
v
Status of the storage subsystem

Hardware components in the storage subsystem
Capacity of the storage subsystem
Hosts, the mappings, and the storage partitions in the storage subsystem
Arrays and logical drives in the storage subsystem
16
Using the Logical tab

The Logical tab provides a tree-structured view of the logical nodes. Click the plus (+) sign or the minus
(-) sign adjacent to a node to expand or collapse the view. Right-click a node to open a menu that
contains the applicable actions for that node.
Nodes on the Logical tab

The storage subsystem, or root node, has the types of child nodes that are shown in the following table.
Table 2. Nodes on the Logical tab
Child nodes of the root node
Description of the child nodes
Unconfigured Capacity
This node represents the storage subsystem capacity that is not configured
into an array.
Note: Multiple Unconfigured Capacity nodes might appear if your
storage subsystem contains mixed drive types. Each drive type has an
associated Unconfigured Capacity node shown under the Total
Unconfigured Capacity node if unassigned drives are available in the
drive enclosure.
Array
This node has two types of child nodes:

v Logical Drive: This node represents a configured and defined logical
drive. Multiple Logical Drive nodes can exist under an Array node. See
Types of logical drives for a description of these arrays.
v Free Capacity: This node represents a region of capacity that you can
use to create one or more new logical drives within the storage
subsystem. Multiple Free Capacity nodes can exist under an Array
node.
Types of logical drives

These types of logical drives appear under the Array node:
v Standard logical drives.
v Primary logical drives that participate in a mirror relationship in the primary role. Primary logical
drives are standard logical drives with a synchronized mirror relationship. The remote secondary
logical drive that is associated with the primary logical drive appears as a child node.
v Secondary logical drives appear directly under the Array node when the local storage subsystem
contains this logical drive.
Mirror repository logical drives.
Flashcopy repository logical drives.
Flashcopy logical drives are child nodes of their associated base logical drive.
Source logical drives are standard logical drives that participate in a logical drive copy relationship.
Source logical drives are used as the copy source for a target logical drive. Source logical drives accept
host I/O requests and store application data. A source logical drive can be a standard logical drive, a
snapshot logical drive, a snapshot base logical drive, or a Remote Logical Drive Mirroring primary
logical drive.
v Target logical drives are standard logical drives that participate in a logical drive copy relationship and
contain a copy of the data from the source logical drive. Target logical drives are read-only and do not
accept write requests. A target logical drive can be made from a standard logical drive, the base logical
drive of a snapshot logical drive, or a Remote Logical Drive Mirror primary logical drive. The logical
drive copy overwrites any existing logical drive data if an existing logical drive is used as a target.
v
v
v
v
17
Using the Physical tab

The Physical tab provides a view of the storage subsystem hardware components, including their status
and the hardware components that are associated with a selected node. Right-click a hardware
component to display a menu that contains the applicable actions for that component.
Controller Status
The status of each controller is indicated by an icon on the Physical tab. The following table describes the
controller icons.
Table 3. Controller status icons
Icon
Status
Online, Optimal
Offline
Data Transfer Disabled
Service Mode
Slot Empty
Needs Attention (if applicable for your hardware

model)
Suspended (if applicable for your hardware
model)
Association
v The blue association dot that is shown adjacent to a controller in the controller enclosure indicates the
current owner of a selected logical drive on the Logical tab.
v The blue association dot that is adjacent to a drive indicates that the drive is associated with a selected
logical drive on the Logical tab.
View
The View button on each enclosure shows the status of the secondary components within the enclosure.
Storage enclosures
For each storage enclosure that is attached to the storage subsystem, a storage enclosure appears on the
Physical tab.
If your storage subsystem contains mixed drive types, a drive type icon appears on the left of the storage
enclosure to indicate the type of drives in the enclosure. The following table describes the different drive
type icons that might appear.
18
Table 4. Storage enclosure type icons

Icon
Status
This storage enclosure contains only Fibre Channel drives.
This storage enclosure contains only Full Disk Encryption
(FDE) security-capable drives.
This storage enclosure contains only Serial Attached SCSI
(SAS) drives.
This storage enclosure contains only Serial ATA (SATA)
drives.
Using the Mappings tab

The Mappings tab in the Subsystem Management window contains two panes: the Topology pane and
the Defined Mappings pane.
Topology pane
The Topology pane shows a tree-structured view of logical nodes that are related to storage partitions.
Click the plus (+) sign or the minus (-) sign adjacent to a node to expand or collapse the view. You can
right-click a node to display a menu that contains the applicable actions for that node.
The storage subsystem, or the root node, has four types of child nodes.
Table 5. Types of nodes in the Topology pane
Child nodes of the root node
Undefined Mappings
Description of the child nodes

The Undefined Mappings node has one type of child node:
v Individual Undefined Mapping: Represents a logical drive with an
undefined mapping. Multiple Logical Drive nodes can exist under
an Undefined Mappings node.
Default Group
Note: If the Storage Manager Storage Partitioning premium feature is

disabled, all of the created logical drives are in the Default Group.
A Default Group node has two types of child nodes:
v Host Group: Defined host groups that are not participating in
specific mappings are listed. This node can have host child nodes,
which can have child host port nodes.
v Host: Defined hosts that are not part of a specific host group but
are part of the Default Group and are not participating in specific
mappings are listed. This node can have child host port nodes.
Host Group
A Host Group node has one type of child node:

v Host: Defined hosts that belong to this defined host group are
listed. This node can have child host port nodes.
Note: The host nodes that are child nodes of this host group can also
participate in mappings specific to the individual host rather than the
host group.
Host
A Host node has one type of child node:

v Host Ports: This node has child nodes that represent all of the host
ports or single ports on a host adapter that are associated with this
host.
19
The Storage Partition icon, when it is present in the Topology pane, indicates that a storage partition has
been defined for the Default Group, a host group, or a host. This icon also appears in the status bar when
storage partitions have been defined.
Defined Mappings pane

The Defined Mappings pane shows the mappings that are associated with a node that is selected in the
Topology pane. This information appears for a selected node.
Table 6. Node information in the Defined Mappings pane
Column name
Logical Drive name
Description
The user-supplied logical drive name.
The factory-configured access logical drive also appears in this column.
Note: An access logical drive mapping is not required for storage
subsystem with an in-band connection and might be removed.
Accessible by
The Default Group, a defined host group, or a defined host that has been
granted access to the logical drive in the mapping.
LUN
The LUN that is assigned to the specific logical drive that the host or
hosts use to access the logical drive.
Logical Drive Capacity
The logical drive capacity in units of GB.
Type
The type of logical drive: standard logical drive or snapshot logical drive.
You can right-click a logical drive name in the Defined Mappings pane to open a menu. The menu
contains options to change and remove the mappings.
The information that is shown in the Defined Mappings pane varies according to which node you select
in the Topology pane, as shown in the following table.
Table 7. Node information by type of node
Node selected
Information that appears in the Defined Mappings pane
Root (storage subsystem) node
All defined mappings.
Default Group node or any child node

of the Default Group
All mappings that are currently defined for the Default Group (if any).
Host Group node (outside of Default

Group)
All mappings that are currently defined for the Host Group.
Host node that is a child node of a Host All mappings that are currently defined for the Host Group, plus any
Group node
mappings that are specifically defined for a specific host.
HBA Host Ports node or individual host All mappings that are currently defined for the HBA host port associated
port node outside of the Default Group host.
Using the Setup tab

The Subsystem Management window Setup tab provides links to the following tasks:
v Locating the storage subsystem
v Renaming the storage subsystem
v Setting a storage subsystem password
v Configuring the storage subsystem
v Defining the hosts and host ports
v Mapping logical drives to hosts
v Saving configuration parameters in a file
20
v Configuring the Ethernet management ports

v Viewing and enabling the premium features
Click a link to open the corresponding window.
Using the Support tab

The Support tab in the Subsystem Management window provides links to these tasks:
v Recovering from a storage subsystem failure with the Recovery Guru
v Gathering support information, such as the event log and a description of the storage subsystem, to
send to a Customer and Technical Support representative
v Viewing the description of all components and properties of the storage subsystem
v Downloading the controller firmware, the NVSRAM, the drive firmware, the ESM firmware, and the
ESM configuration settings
v Viewing the event log of the storage subsystem
v Viewing the online help topics
v Viewing the version and copyright information of the storage management software
Managing multiple software versions

When you open the Subsystem Management window to manage a storage subsystem, the version of
Storage Manager software that is applicable for the version of firmware opens. For example, you can
manage two storage subsystems that use the Storage Manager software; one storage subsystem has
firmware version 6.14, and the other has firmware version 7.5x. When you open a Subsystem
Management window for one of the storage subsystems, the correct Subsystem Management window
version is used. The storage subsystem with firmware version 6.14 uses version 9.14 of the Storage
Manager software, and the storage subsystem with firmware version 7.5x uses version 10.5x of the
Storage Manager software. You can verify the version that you are currently using by clicking Help >
About in the Subsystem Management window.
21
22
Chapter 3. Installing Storage Manager and Support Monitor

This chapter describes requirements and procedures for Storage Manager software installation, including
the Support Monitor tool. The Support Monitor tool is a component of Storage Manager version
10.60.x5.17 and later. The Apache Tomcat web server and MySQL database software packages are also
installed, as a part of the Support Monitor tool.
The installation instructions consist of the following sections:
v Preinstallation requirements
v Installing the Storage Manager and Support Monitor packages automatically with the installation
wizard on page 25
v Installing Storage Manager packages manually on page 28
v Completing the Storage Manager installation on page 31
To uninstall Storage Manager and Support Monitor, see Uninstalling Storage Manager and Support
Monitor on page 30.
Attention: For cluster configurations, complete all applicable configuration procedures for each storage
subsystem before you install the Storage Manager software on a second host or cluster server.
Preinstallation requirements
This section describes the requirements that must be met before the Storage Manager software with the
Support Monitor tool can be installed.
For Storage Manager installations on UNIX, your system must have graphics capability to use the
installation wizard. If your system does not have graphics capability, you can use the shell command to
install Storage Manager without graphics. See Installing Storage Manager and Support Monitor with a
console window in Linux, AIX, HP-UX, and Solaris on page 27 for more information.
You can also skip this section and install the stand-alone host software packages by using the procedures
that are described in Installing Storage Manager packages manually on page 28. All of the packages are
included with the installation DVD.
The supported management-station operating systems for Storage Manager are:
v AIX
v Windows 7, Windows Vista, Windows XP (Service Pack 2), Windows 2008, Windows 2008 R2, and
Windows 2003
v Linux: RHEL and SLES (x86, x86_64, Linux on Power (ppc) and IA64 editions)
v HP-UX (PA-RISC and IA64 editions)
v SUN Solaris (SPARC and x86 editions)
The Support Monitor tool must be installed on the same management stations as the Storage Manager
software. The supported management station operating systems for Support Monitor are:
v Microsoft Windows 2003 (Service Pack 2), Windows 2008, Windows 2008 R2, Windows XP (Service
Pack 2), and Windows Vista (x86, x64, and IA64 editions)
v Red Hat Enterprise Linux 4 and 5 (x86, x86_64, and IA64 editions)
v SUN Solaris 10 (Sparc and x86 editions)
v IBM AIX 5.2, AIX 5.3 and AIX 6.1.
23
Important: If a MySQL database application or Apache Tomcat web server application is installed on the
management station, it must be uninstalled before the Support Monitor can be installed.
Note: With Storage Manager version 10.50.xx.xx, controller firmware 5.41.xx.xx and later are supported.
Controller firmware versions earlier than 5.41.xx.xx are no longer supported or managed.
The management station must also meet the following hardware, software, and configuration
requirements:
v Microprocessor speed of 1.6 GHz or faster.
v Minimum of 2 GB of system memory. If any other applications are installed in the management station,
additional memory might be required.
v Minimum of 1.5 GB of free disk space for the tool and for the saved support bundles.
v The TCP/IP stack must be enabled. If Support Monitor is installed, the management station Ethernet
port TCP/IP address must be static, and its Ethernet port must be on the same Ethernet subnet as the
monitored storage subsystem Ethernet management ports. DHCP server IP address is not supported. If
Support Monitor is not installed, the IP address does not have to be static.
v The following requirements apply only to the Support Monitor tool:
Make sure that your storage subsystem meets the subsystem model and controller firmware version
requirements that are listed in the following table.
Table 8. Storage Monitor-compatible subsystems and controller firmware
Storage subsystem
Storage Monitor-compatibility
Controller firmware compatibility
DS3200e
Yes (10.60.xx.xx and later)
7.35.xx.xx and later
DS3300
DS3400
DS3500
Yes
7.70.16.01 and later
DS3950
Yes
7.60.28.xx and later
DS4100
No
DS4200
Yes
DS4300
Yes
DS4400
No
DS4500
Yes
DS4700
Yes
DS4800
Yes
DS5020
Yes
DS5100
Yes
DS5300
Yes
DCS3700
Yes
7.77.14.00 and later
To use Support Monitor, one of the following web browsers must be installed:
- Internet Explorer 7.0 or later
- Netscape version 6.0 or later
- Mozilla version 1.0 or later
- Firefox version 3.0 or later
Any installed MySQL database application on the management station must be manually
uninstalled before you install the Support Monitor tool.
Any installed Apache Tomcat web server software on the management station must be manually
uninstalled before you install the Storage Manager Profiler Support Monitor tool.
24
The Support Monitor uses port 162 by default to receive event data from the server. To prevent port
conflicts with other applications running on the server, make sure that no other applications use
port 162.
Installing the Storage Manager and Support Monitor packages

automatically with the installation wizard
You can install the Storage Manager software automatically by using the Storage Manager installation
wizard, or you can install each package manually. This section describes the installation process for the
Storage Manager installation wizard.
Storage Manager version 10.60.x5.17 and later includes software for a web-based tool called Support
Monitor. The Storage Manager and Support Monitor software are both installed when you use the
installation wizard. However, the Storage Monitor and Support Monitor are installed in separate parts.
The Storage Manager Client program and other Storage Manager software components are installed first,
followed by the Storage Manager Profiler Support Monitor tool. A separate progress status bar is
displayed for each part.
Before you install the Storage Manager and Support Monitor software, read the following Important
installation notes about Support Monitor section and either the Installing Storage Manager and Support
Monitor on Windows or the Installing Storage Manager and Support Monitor on Linux, AIX, HP-UX,
or Solaris on page 26 section.
Important installation notes about Support Monitor

v The Support Monitor tool is packaged in the same SMIA installer package as the Storage Manager Host
software package. There is not a separate installer package for the Support Monitor tool.
v The Storage Manager client program must be installed with the Support Monitor tool. Support Monitor
will not run correctly without the Storage Manager client program.
v The Support Monitor tool is installed by default when either the Typical (Full Installation) or
Management installation type is selected in the Wizard Select Installation Type window. The Support
Monitor tool is not installed when the Host installation type is selected.
v If you select the Custom installation type in the wizard Select Installation Type window, the Support
Monitor tool is displayed as a selected component for installation. To install the Storage Manager
without the Support Monitor tool, clear the Support Monitor check box.
Do not install Support Monitor on more than one management station that manages the same set of
storage subsystems. To install Storage Manager on multiple management stations that manage the
same set of storage subsystems, use the custom installation type in subsequent installations of the
Storage Manager software and clear the Support Monitor check box to prevent it from being installed
on more than one management station. If the tool is installed on more than one management station,
the storage subsystem will service multiple requests daily at 2 a.m. for support bundle collection. This
might cause problems during support-bundle collection.
v If MySQL data or the Apache Tomcat web server program is installed, the Support Monitor installation
terminates and an installation error message is displayed. The Storage Manager Profiler Support
Monitor installation log is stored in the C:\Program Files...\IBM_DS directory in Windows operating
systems, or in the /opt/IBM_DS/ directory in Unix-type operating systems. The file name of the log is
IBMStorageManagerProfiler_install.log.
Installing Storage Manager and Support Monitor on Windows

If your management station has a Windows operating system, complete the following steps to install
Storage Manager (including the Support Monitor tool) with the installation wizard:
1. Download the files from the Storage Manager DVD, or from the System Storage Disk Support
website, to a directory on your system. The default drive for Windows is C.
25
2. Double-click the IBM DS Storage Manager package (or SMIA) executable icon.
3. Follow the instructions in the Installation wizard to install the Storage Manager software with the
Storage Manager Profiler Support Monitor tool. If you accept the default installation directory, the
Storage Manager Profiler Support Monitor is installed in C:\Program Files...\IBM_DS\
IBMStorageManagerProfiler Server.
4. When you select the installation type, you can choose one of the following options:
Attention: Storage Manager SMIA package version 10.77.xx.xx and later will not install the MPIO
DSM driver to support multipath in the host installation type or in the typical installation type when
the SMIA package is installed in the server version of Microsoft Windows operating systems. There is
a separate SMIA package for installing the MPIO DSM.
v Typical (Full) Installation: Installs Storage Manager software packages that are necessary for both
managing the storage subsystem from the host and providing I/O connectivity to the storage
subsystem
v Management Station: Installs the packages that are required to manage and monitor the storage
subsystem (SMclient)
v Host: Installs the packages that are required to provide I/O connectivity to the storage subsystem
(SMagent and SMutil)
v Custom: Allows you to select which packages you want to install. To install the Storage Manager
without the Support Monitor tool, select the customer installation and clear the Support Monitor
box.
5. Configure any antivirus software not to scan the MySQL directory. In Windows operating-system
environments, the directory is:
C:\Program Files...\IBM_DS\ IBMStorageManagerProfiler Server/mysql
6. Install the MPIO DSM drive as required to support multipath by double-clicking the IBM DS Storage
Manger MPIO DSM package and following the instructions in the installation wizard.
Note: This step applies to storage manager version 10.77.xx.xx and later only.
7. Click Start > All Programs > DS Storage Manager 10 client > Storage Manager 10 client to start the
Storage Manager client program. Add the storage subsystems that you want to manage and monitor
in the Enterprise Management window of the Storage Manager Client program.
During the installation, the question Automatically Start Monitor? is displayed. This refers to the
Microsoft Windows Event Monitor service. The Event Monitor must be enabled for both the automatic
ESM synchronization and the automatic support bundle collection of critical events. To enable the Event
Monitor, select Automatically Start Monitor.
The only time that you have to configure the Storage Manager Profiler Support Monitor tool is when you
want to change the support bundle collection time for the monitored storage subsystems. The Storage
Manager Profiler Support Monitor tool automatically collects the support bundles from the storage
subsystems that were added to the Enterprise Management window of the Storage Manager Client
program daily at 2 a.m.
To complete the Storage Manager installation, see Completing the Storage Manager installation on page
31.
Installing Storage Manager and Support Monitor on Linux, AIX, HP-UX, or Solaris
If your management station has a Unix-based operating system, such as Linux, AIX, HP-UX, or Solaris,
complete the following steps to install Storage Manager (including the Support Monitor tool) with the
installation wizard:
1. Download the files from the Storage Manager DVD, or from the System Storage Disk Support
website, to the root file system on your system.
2. Log in as root.
26
3. If the Storage Manager software package .bin file does not have executable permission, use the chmod
+x command to make it executable.
4. Execute the .bin file and follow the instructions in the Installation wizard to install the software.
If you accept the default installation directory, the Storage Manager Profiler Support Monitor is
installed in /opt/IBM_DS/IBMStorageManagerProfiler_Server.
When you select the installation type, you can choose one of the following options:
v Typical (Full) Installation: Installs all Storage Manager software packages that are necessary for
both managing the storage subsystem from this host and providing I/O connectivity to the storage
v Management Station: Installs the packages that are required to manage and monitor the storage
subsystem (SMruntime and SMclient)
v Host: Installs the packages that are required to provide I/O connectivity to the storage subsystem
(SMruntime, SMagent, and SMutil)
v Custom: Allows you to select which packages you want to install. To install the Storage Manager
without the Support Monitor tool, select the customer installation and clear the Support Monitor
check box.
5. Configure any antivirus software to not scan the MySQL directory. In Unix-type operating-system
environments, the directory is:
/opt/IBM_DS/IBMStorageManagerProfiler_Server/mysql
6. Type SMclient in the console window and press Enter to start the Storage Manager Client program.
Add the storage subsystems that you want to manage and monitor to the Enterprise Management
window of the Storage Manager Client program.
During the installation, the question Automatically Start Monitor? is displayed. This refers to the Event
Monitor service. The Event Monitor must be enabled for both the automatic ESM synchronization and the
automatic support bundle collection of critical events. To enable the Event Monitor, select Automatically
Start Monitor.
The only time that you have to configure the Storage Manager Profiler Support Monitor tool is when you
want to change the support bundle collection time for the monitored storage subsystems. The Storage
Manager Profiler Support Monitor tool automatically collects the support bundles from the storage
subsystems that were added to the Enterprise Management window of the Storage Manager Client
program daily at 2 a.m.
To complete the Storage Manager installation, see Completing the Storage Manager installation on page
31.
Installing Storage Manager and Support Monitor with a console

window in Linux, AIX, HP-UX, and Solaris
For a management station without a graphics adapter, the Storage Manager software package can be
installed silently with the -i silent or -i console option. This installation method can also be used in a
Windows operating-system environment.
The -i silent option causes the Storage Manager Software Installer package to be installed using the
default installer settings. The -i console option prompts the user for installed options before the
software installation starts, as the Installation wizard does. However, the prompts are displayed in
console window text instead of graphical windows.
Portions of the Storage Manager console window installation text with the -i silent and -i console
options are shown in the following example.
[usr@RHManaStation ~]# ./SMIA-LINUX-10.60.A5.17.bin -i console
Preparing to install...
Extracting the JRE from the installer archive...
27
Unpacking the JRE...

Extracting the installation resources from the installer archive...
Configuring the installer for this system environment...
Launching installer...
Preparing CONSOLE Mode Installation...
===============================================================================
Choose Locale...
---------------1->23456-
Deutsch
English
Espaol
Franais
Italiano
Portugus
(Brasil)
CHOOSE LOCALE BY NUMBER:

2
... ... ...
...
[usr@RHManaStation ~]# ./SMIA-LINUX-10.60.A5.17.bin -i silent
Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system environment...
Launching installer...
Preparing SILENT Mode Installation...
===============================================================================
IBM System Storage DS Storage Manager 10(created with InstallAnywhere by Macrovision)
-------------------------------------------------------------------------------------
===============================================================================
Installing...
------------[==================|==================|==================|==================]
[------------------|------------------|------------------|------------------]
... ... ...
Installing Storage Manager packages manually

For Unix-type operating systems such as AIX, Linux, Sun Solaris, and HP-UX, individual Storage Manger
software packages are provided. See Table 9 on page 29 for the installation sequence of each software
package.
Use the procedure in this section to manually install the Storage Manager software on a management
station. Be sure to install the packages in the correct order.
Important:
1. There is not an individual software package for the Storage Manager Support Monitor tool. If you
want to install the Support Monitor tool, you must use the Storage Manager software installer
package.
28
2. There is no manual installation option for Windows operating systems. For all installations of Storage
Manager on Windows, the individual software packages are included in a single Storage Manager
software installer.
Software installation sequence

Install the Storage Manager software packages in the sequence shown in Table 9.
Note: These packages are available for UNIX servers without a graphical user interface. Support Monitor
is not available as a stand-alone software package. See Installing Storage Manager and Support Monitor
with a console window in Linux, AIX, HP-UX, and Solaris on page 27.
Table 9. Installation sequence of Storage Manager software packages
Step
Package
SMruntime
SMesm
SMclient
SMagent
SMutil
SMclient is dependent on SMruntime, which is a Java compiler for SMclient. SMruntime must be
installed first.
Installing Storage Manager manually

Before installing the Storage Manager software, make sure that the Storage Manager files are available in
a directory on the system.
For your installation, modify the following commands as needed. No restart is required during the
installation process. The verification process returns a table that describes the software installation,
including the install package file name, version number, action, and action status.
1. Install the <SMpackage> by typing the command appropriate for your operating system.
Note: The manual install commands listed in the following table are only for UNIX-based operating
systems.
Table 10. Examples of Storage Manager package install commands
Operating system
Package name
Install command
AIX
SMruntime.AIX-10.xx.xx.xx.bff
#installp -a -d /path_name/SMruntime.AIX10.xx.xx.xx.bff SMruntime.aix.rte
HP-UX
SMruntime_10.xx.xx.xx.depot
#swinstall -s /cdrom/HP-UX/
SMruntime_10.xx.xx.xx.depot
Solaris
SMruntime-SOL-10.xx.xx.xx.pkg
#pkgadd -d path/SMruntime-SOL-10.xx.xx.xx.pkg
Linux on POWER
SMruntime-LINUX-10.xx.xx.xxx.i586.rpm
#rpm -ihv SMruntime-LINUX-10.xx.xx.xx-x.i586.rpm
2. Verify that the installation was successful by typing the command appropriate for your operating
system.
29
Table 11. Storage Manager package installation verify commands

Operating system
Verify command
AIX
# lslpp -ah <SMpackage>.aix.rte
HP-UX
# swverify -v <SMpackage>
Solaris
# pkginfo -l <SMpackage>
Linux on POWER
# rpm -qa|grep <SMpackage>
If the verification process returns an error, contact your IBM service representative.
Uninstalling Storage Manager and Support Monitor

Use the applicable procedure in this section to uninstall Support Monitor, or both the Storage Manager
and Support Monitor, on a Windows or Unix-type operating system.
Uninstalling Storage Manager and Support Monitor on a Windows

operating system
To uninstall the software on a Windows operating system, complete the following steps:
1. Open the Control Panel window.
2. If you have Windows 2003 or Windows XP, double-click Add/Remove Programs. If you have
Windows 2008, double-click Program and Features. The new window opens.
3. Select IBM DS Storage Manager Host Software version 10.xx.x5.yy, where xx and yy are the
applicable version numbers of your software.
4. Click Change/Remove and follow the instructions in the Uninstall Storage Manager 10 wizard to
uninstall only the Support Monitor tool or both the Support Monitor tool and the Storage Manager
software. The process of uninstalling the software might leave files that were created by the Storage
Manager and the Support Monitor after the installation was complete. These files might include trace
files, repository files, and other administrative files. Delete these files manually to completely remove
Storage Manager and Support Monitor.
Note: You can also uninstall the Support Monitor tool by running the uninstall.exe file in the
C:\Program Files ...\IBM_DS\IBMStorageManagerProfiler Server directory.
Uninstalling Storage Manager and Support Monitor on a Linux, AIX, or

Solaris operating system
To uninstall the software on a Unix-type operating system, complete the following steps:
1. Open the /opt/IBM_DS/Uninstall IBM System Storage DS Storage Manager 10 directory that contains
the uninstaller binary.
2. Run the script Uninstall_IBM_System_Storage_DS_Storage_Manager_10 script in the console window to
uninstall only the Support Monitor or both the Support Monitor and Storage Manager software. The
process of uninstalling the software might leave files that were not part of the original installation.
These files might include trace files, repository files, and other administrative files. Delete these files
manually to completely remove the Storage Manager and Support Monitor.
Note: You can also uninstall the Support Monitor tool by running the uninstall file in the
/opt/IBM_DS/IBM_DS\IBMStorageManagerProfiler_Server directory.
30
Completing the Storage Manager installation

This section contains procedures for using the Enterprise Management and Subsystem Management
features of the Storage Manager to complete the Storage Manager installation tasks for all host operating
systems.
To complete a Storage Manager installation, the following procedures must be performed:
v Perform an initial automatic discovery of storage subsystems
v Perform an initial manual discovery of storage subsystems
v Name the storage subsystems
v Set up alert notifications
v Configure iSCSI settings for storage subsystems with iSCSI ports
v Verify and upgrade the Controller code, ESM, and disk drive firmware to the latest version as
prescribed on the IBM support portal
v Enable Storage subsystem premium features
v Save a storage subsystem profile and support data
Each of these procedures is described in detail in the following sections.
The Enterprise Management window opens when you start the Storage Manager. You can use the
Enterprise Management window to perform the following tasks:
v Add and discover the storage subsystems
v View all storage subsystems in your management domain
v Perform batch storage subsystem management tasks with the Script Editor
Performing an automatic discovery of storage subsystems

Complete the following steps to perform an initial automatic discovery of storage subsystems:
1. For Windows operating system, click Start > All Programs > DS Storage Manager 10 Client > DS
Storage Manager 10 Client. For UNIX-type operating system, open the console window. Type
SMclient and press Enter. The Storage Manager client software starts and displays the Enterprise
Management window and the Confirm Initial Automatic Discovery window.
2. Click Yes to begin an initial automatic discovery of hosts and storage subsystems that are attached to
the local subnetwork.
After the initial automatic discovery is complete, the Enterprise Management window displays all
hosts and storage subsystems that are attached to the local subnetwork.
Note: The Enterprise Management window can take one minute or more to refresh after an initial
automatic discovery. If the storage subsystem is not discovered automatically, check the network
connections (out-of-band management) or the server HBA port to storage subsystem host port
connections. To try to add the subsystem manually, click Edit > Add Storage Subsystem.
3. Verify that each host and storage subsystem is displayed in the Enterprise Management window.
v If a host or storage subsystem is not displayed, complete the following tasks:
a. Check the hardware and hardware connections for possible problems. See the Installation, User's,
and Maintenance Guide for your storage subsystem for specific procedures.
b. See the Enterprise Management online help for additional information about discovering storage
subsystems.
c. If you are using the network-management method (commonly known as out-of-band
management), verify that all hosts and storage subsystems are connected to the same subnet
network and the gateway information is defined for the Ethernet ports. For more information
about the storage subsystem ethernet management ports, refer to Setting up IP addresses for
storage subsystem controllers on page 6. If you are using the host-agent method (commonly
31
known as in-band management), make sure that the Fibre Channel, SAS, or iSCSI connection
between the host and storage subsystems is made.
d. Make sure that all of the preparation steps for setting up the storage subsystem for a network
managed system are completed. Use the Add Device option to add the IP addresses of the
storage subsystem. Add both IP addresses of the controller; otherwise, a partially-managed
device error message is displayed when you attempt to manage the storage subsystem.
Note: To use the auto-discovery method, the storage subsystem and this host must be on the
same subnet. Otherwise, use the manual method to add a storage subsystem.
v If you are using the host-agent-management method, complete the following steps:
a. Make sure that the SMagent is installed in the host.
b. Verify that you have a Fibre Channel, SAS, or iSCSI connection from the storage subsystems to
the host on which the SMagent installed. Check the SAN switch zoning or VLAN configuration
as required.
c. Verify that all of the preparation steps are complete, and then perform the following steps:
1) Run the hot_add utility.
2) Restart the SMagent.
3) Right-click the host, and click Tools > Rescan Hosts in the Enterprise Management window.
Note: In certain situations, a storage subsystem might be duplicated in the Device tab tree view
after an automatic discovery. You can remove a duplicate storage management icon from the device
tree by using the Remove Device option in the Enterprise Management window.
4. Verify that the status of each storage subsystem is Optimal. If a device shows a status of
Unresponsive, right-click the device and select Remove Device to delete it from the management
domain. Verify that the storage subsystem is powered up and complete start-of-day process. Then use
the Add Device option to add it to the management domain again. See the Enterprise Management
window online help for instructions for removing and adding devices.
Performing a manual discovery of storage subsystems

You can add hosts or storage subsystems manually; use this option to selectively manage a group of
storage subsystems from an SMclient. You can also use this option to add devices to be managed that
were not discovered during the SMclient initial discovery.
In the Enterprise Management window, click Edit > Add Storage Subsystem. The Add New Storage
Subsystem - Manual window opens. You can add Storage subsystems for management. Refer to the
online help to know how to add subsystems.
Important:
1. When you add new storage subsystems to the existing storage subsystems in a SAN that are managed
through the host-agent software, you must stop and restart the host-agent service. When the
host-agent service restarts, the new storage subsystem is detected. Then, go to the Enterprise
Management window and click Tools > Rescan to add the new storage subsystems to the
management domain.
2. When you add new storage subsystems to existing storage subsystems that are managed using the
direct-management method, be sure to specify the IP addresses for both controllers.
Setting a storage subsystem management password

The storage subsystem management password functionality differs between certain combinations of
Storage Manager and controller firmware versions.
For Storage Manager version 10.36.xx.xx and earlier with controller firmware version 7.36.xx.xx and
earlier, you can set a password for each storage subsystem that you manage by clicking Storage
32
Subsystem > Change Password. After you set the password for each storage subsystem, you are
prompted for that password the first time you attempt a destructive operation in the Subsystem
Management window. You are prompted for the password only once during a single management
session, and the password does not time out. The password does not have password-strength
requirements.
For Storage Manager version 10.50.xx.xx and later with controller firmware version 7.50.xx.xx and later,
you are prompted with a window to set the subsystem management password every time you start the
Subsystem Management window of the storage subsystem that did not have the password set. In
addition, the password times out after a certain duration of Subsystem Management window inactivity.
The password requirement is stricter with Storage Manager version 10.70.xx.xx and later with controller
firmware version 7.70.xx.xx and later; the Subsystem Management window will not open if the password
is not set. The password must be between 8 and 30 characters and contain at least one number, one
lower-case letter, one upper-case letter, and one non-alphanumeric character (for example, < > ! @ + #).
Spaces are not permitted, and it is case-sensitive.Only storage subsystems with controller firmware
version 7.70.xx.xx and later do not allow the subsystem management window to be opened if the
subsystem management password is not set. There are no such restrictions for controller firmware
versions.
Important: Make sure that the password information is kept in a safe and accessible place. Contact IBM
technical support for help if you forget the password to the storage subsystem.
Naming storage subsystems

As you set up your network, decide on a naming convention for the storage subsystems. For example,
you might use the device type followed by the serial number: 1815 1312345 XXXX xxx xxxx. When you
install the Storage Manager software and start it for the first time, all storage subsystems in the
management domain are shown as <unnamed>. Use the Subsystem Management window to rename each
storage subsystem.
Consider the following factors when you name storage subsystems:
v
v
v
v
There is a 30-character limit. All leading and trailing spaces are deleted from the name.
Use a unique, meaningful naming scheme that is easy to understand and remember.
Avoid arbitrary names or names that might quickly lose their meaning.
The software adds the prefix Storage Subsystem when it displays storage subsystem names. For
example, if you name a storage subsystem Engineering, it is displayed as Storage Subsystem
Engineering.
To name your storage subsystems, complete the following steps:

1. In the Enterprise Management window, right-click the storage subsystem and select Rename. The
Rename Storage Subsystem window opens.
Note: If any of the hosts are running path failover drivers, update the storage subsystem name in
your path failover driver configuration file before you reboot the host system to establish
uninterrupted access to the storage subsystem.
2. Type the name of the storage subsystem and click OK.
3. Click Yes on the warning screen.
4. Repeat this procedure for each unnamed storage subsystem. For more information, see the topic about
renaming storage subsystems in the Subsystem Management window online help.
5. Proceed to Setting alert notifications.
Setting alert notifications

After you add devices to the management domain, you can set alert notifications to report critical events
on the storage subsystems. The following alert-notification options are available:
33
v Notification to a designated network-management station using Simple Network Management Protocol

(SNMP) traps
v Notification to designated email addresses
v Notification to designated alphanumeric pagers (requires separately supplied software to convert email
messages)
Note: You can monitor storage subsystems only within the management domain. If you do not install the
Event Monitor service, the Enterprise Management window must remain open. If you close the window,
you will not receive any alert notifications from the managed storage subsystems. See the Enterprise
Management window online help for additional information.
Alert notification with SNMP traps
To set up alert notification to a network-management station using SNMP traps, complete the
following steps:
1. Insert the Storage Manager DVD into the DVD drive on a network-management station. You
must set up the designated management station only once.
2. Copy the SMxx.x.MIB file from the SMxxMIB directory to the network-management station.
3. Follow the steps that are required by your network-management station to compile the
management information base (MIB) file. (For details, contact your network administrator or
see the documentation for your particular storage management product.)
Alert notification without SNMP traps
To set up alert notification without using SNMP traps, click Storage subsystem > Edit >
Configure alerts on the Enterprise Management window.
Managing iSCSI settings

Click the Setup tab in the Subsystem Management window. A window similar to the one in Figure 4 on
page 35 opens.
Note: The link to iSCSI Manage settings or Configure iSCSI Host Ports on the Subsystem Management
window is available only for storage subsystems that support an iSCSI host attachment. As of the date of
this document, the following storage subsystems support iSCSI host attachment:
v
v
v
v
v
DS3300
DS3500
DS3950
DS5020
DS5100/5300
34
Figure 4. Managing iSCSI settings
The following iSCSI options are available from the Storage Subsystem management menu and are
described in the following sections:
Note: The menu selection in these iSCSI options changes according to the version of the controller
firmware. Refer to the online help for the appropriate menu options.
v Changing target authentication
v Entering mutual authentication permissions on page 36
v
v
v
v
v
Changing target identification on page 36

Changing target discovery on page 36
Configuring iSCSI host ports on page 36
Viewing or ending an iSCSI session on page 36
Viewing iSCSI statistics on page 36
Changing target authentication

Select Change Target Authentication to specify the target Challenge Handshake Authentication Protocol
(CHAP) secret that the initiator must use during the security negotiation phase of the iSCSI login. By
default, None is selected. To change the selection, click CHAP, and then enter the CHAP secret. You can
also select the option to generate a random secret. This enables 1-way CHAP.
35
Entering mutual authentication permissions

Before you select Enter Mutual Authentication Permissions, you must define a host port for the initiator
and enable Target Authentication. After the host port is listed, select the host from the list and click Chap
Secret to specify the secret that is passed to the initiator from the target and authenticate it. This enables
Mutual CHAP (2-way).
Changing target identification

Select Change Target Identification to specify a target alias that is to be used during device discovery.
You must provide a unique name that consists of fewer than 30 characters for the target.
Note: You will connect to the target with the fully qualified IQN that is listed above the alias.
Changing target discovery

Select Change Target Discovery to perform device discovery with the iSCSI simple naming service
(iSNS). After you select this option, select the Use iSNS Server check box. You can also select whether
the iSNS server is discovered using a DHCP server on your network, and you can manually specify an
Internet Protocol version 4 (IPv4) or IPv6 address. When you click the Advanced tab, you can assign a
different TCP/IP port for your iSNS server for additional security.
Note: To provide the required port login information for correct device discovery, all iSCSI ports must be
able to communicate with the same iSNS server.
Configuring iSCSI host ports

Select Configure iSCSI Host Ports to configure all of the TCP/IP settings. You can choose to enable or
disable IPv4 and IPv6 on all of the ports. You can also statically assign IP addresses or let them be
discovered using DHCP. Under Advanced IPv4 Settings, you can assign VLAN tags (802.1Q) or set the
Ethernet priority (802.1P). Under Advanced Host Port Settings, you can specify a unique iSCSI TCP/IP
port for that target port. You can also enable jumbo frames from this option. The supported frame sizes
are 1500 and 9000.
Viewing or ending an iSCSI session

Select View/End iSCSI Sessions to view all of the connected iSCSI sessions to the target. From this page,
you can also close an existing session by forcing a target ASYNC logout of the initiator session.
Viewing iSCSI statistics

Select View iSCSI Statistics to view a list of all iSCSI session data, for example, the number of header
digest errors, the number of data digest errors, and successful protocol data unit counts. You can also set
a baseline count after a corrective action to determine whether the problem is solved.
Using an iSNS server

There are many considerations for using an iSNS server correctly. Be sure to correctly assign your iSNS
server address that is provided during the DHCP lease discovery of your initiator or target. This enables
ease of discovery when you use initiator-based solutions. If you are unable to do this and you must
manually assign the iSNS server to your software or hardware initiators, you must make sure that all of
the storage subsystem iSCSI ports and iSCSI initiators are in the same network segment (or make sure
that the routing between the separate network segments is correct). If you do not do this, you will be
unable to discover all ports during the iSCSI discovery process, and you might not be able to correctly
perform a controller or path failover.
Using DHCP
Do not use DHCP for the target portals. If you use DHCP, you must assign DHCP reservations so that
leases are maintained consistently across restarts of the storage subsystem. If static IP reservations are not
provided, the initiator ports can lose communication to the controller and might not be able to reconnect
to the device.
36
Using supported hardware initiators

Before you install and configure these adapters, ensure that you have installed the latest management
application and firmware. Then, configure each adapter one at a time. In a configuration with a
single-controller subsystem, in which iSCSI adapters and target ports are in the same network segment,
each adapter can connect to any target port. In a complex configuration, each adapter can connect to a
controller device. To ensure that failover is performed correctly, connect each iSCSI adapter in the server
in one of the following:
v - Single iSCSI adapter in the server - The iSCSI adapter port must be able to login both controller A
and B iSCSI host ports. The iSCSI port is configured as multihome with controller A and B iSCSI port
subnets.
v - Multiple iSCSI adapters in the server - Each adapter port is allowed a single path to each controller
iSCSI host ports. Each iSCSI adapter port and its associated iSCSI controller host port must be on
separate subnet from other pairs of iSCSI adapter and controller host ports
If you use a Qlogic hardware initiator adapter, complete the following steps to log in to all the available
target ports from the hardware initiator. For other hardware initiator adapters, refer to the publications of
those hardware initiator adapters for information on logging in to all the available target ports.
For the list of supported hardware initiators, go to http://www.ibm.com/systems/support/storage/
config/ssic.
To log in to all available target ports from the Qlogic hardware initiator, complete the following steps.
Note: Failure to perform the steps in the following procedure might result in path failover inconsistencies
and incorrect operation of the storage subsystem.
1. Start the SANsurfer management utility.
2. Connect to the system that is running the qlremote agent.
3. Select the adapter that you want to configure.
4.
5.
6.
7.
Select either Port 0 or Port 1 for the adapter.

Click Target Settings.
Click the plus sign (+) in the far right of the window.
Type the IPv4 or IPv6 address of the target port to which you want to connect.
8. Click OK.
9. Select Config Parameters.
10. Scroll until you see ISID. For connection 0, the last character that is listed must be 0. For connection
1, it must be 1, for connection 2, it must be 2, and so on.
11. Repeat steps 6 through 10 for each connection to the target that you want to create.
12. After all of the sessions are connected, select Save Target Settings. If you are using the QLogic iSCSI
Single-Port or Dual-Port PCIe HBA for IBM System x to support IPv6, you must allow the host bus
adapter firmware to assign the local link address.
Using IPv6
The storage subsystem iSCSI ports support the Internet Protocol version 6 (IPv6) TCP/IP. Note that only
the final four octets can be configured if you are manually assigning the local link address. The leading
four octets are fe80:0:0:0. The full IPv6 address is required when you are attempting to connect to the
target from an initiator. If you do not provide the full IPv6 address, the initiator might fail to be
connected.
Configuring network settings for iSCSI host attachment

If you use a storage subsystem that supports iSCSI host attachment in a complex network topology, you
must address a few challenges. If possible, isolate the iSCSI traffic to a dedicated network. If this is not
possible and you are using a hardware-based initiator, the Keep Alive timeout must be set to 120 seconds.
To set the Keep Alive timeout, complete the following steps:
37
1. Start the SANsurfer Management Utility and connect to the server.

2. Select the adapter and the adapter port that is to be configured.
3. Select the port options and firmware.
The default connection timeout is 60 seconds. This setting is satisfactory for simple network topologies.
However, in a more complex configuration, if a network convergence occurs and you are not using Fast
Spanning Tree and separate spanning tree domains, you might incur I/O timeouts. If you are using a
Linux iSCSI software initiator, modify the ConnFailTimeout parameter to account for the spanning tree
issue. The ConnFailTimeout value must be set to 120 seconds.
Configuring Maximum Transmission Unit settings

All devices on a link that are expected to communicate with each other (such as devices on the same
VLAN) must be configured with the same Maximum Transmission Unit (MTU) size. The MTU size is a
configuration item, or it is hard-coded in the device, and it is not negotiated between endpoints during
login or connection establishment. If a device receives a packet that is larger than the MTU size, it drops
the packet. If a router receives a packet whose size does not exceed the MTU size of the link on which it
was received but exceeds the MTU size of the forwarding link, the router either fragments the packet
(IPv4) or returns a packet too large ICMP error message. Make sure that all of the components on a
network link are using the same MTU size value.
For storage subsystems that support iSCSI, the default MTU setting is 1500 bytes. There is an option to
select 9000 bytes for jumbo frames. For end-to-end jumbo frames to work effectively, jumbo frames (large
MTU) must be enabled on all components (host, switch, routers, and targets). If jumbo frames are not
enabled on all components, one or more of the following conditions might occur:
v Frames are dropped.
v No connections are dropped because of error messages about the packet being too large.
v Jumbo frames are fragmented.
Microsoft iSCSI Software Initiator considerations

The native multipath I/O (MPIO) that is provided with the Microsoft iSCSI Software Initiator (version
2.03 or later) is not supported. You must use the DSM that is provided with Storage Manager to make
sure that failover and I/O access are correct. If the native MPIO from the Microsoft iSCSI Software
Initiator is used, it causes unwanted effects.
Downloading controller firmware, NVSRAM, ESM firmware

This section provides instructions for downloading storage subsystem controller firmware, NVSRAM,
storage enclosure ESM firmware, and drive firmware. Normally, the storage subsystem firmware
download sequence is as follows:
1. Controller firmware
2. Controller NVSRAM
3. ESM firmware
4. Drive firmware
Review the readme file that is provided with updated controller firmware, NVSRAM, ESM firmware, and
drive firmware for any necessary changes to the firmware download sequence.
Important:
1. The following procedures assume that you are using the latest controller firmware version. Access the
latest versions of storage subsystem controller firmware, NVSRAM, and storage enclosure ESM
firmware on the IBM Support Portal at http://www.ibm.com/support/entry/portal. For the most
recent Storage Manager readme files for your operating system, see Finding Storage Manager
software, controller firmware, and readme files on page xiii.
38
2. Before you upgrade a DS4800, DS4700, or a DS4200 storage subsystem to controller firmware version
07.1x.xx.xx and later from the current installed firmware version of 6.xx.xx.xx and earlier, see the
procedures in Using the IBM System Storage Controller Firmware Upgrade Tool on page 41.
3. IBM supports the storage subsystem controller and ESM firmware download with I/O, sometimes
called concurrent firmware download, with some storage subsystems. Before you proceed with
concurrent firmware download, review the readme file that is packaged with the firmware code or
your operating-system Storage Manager host software for any restrictions.
4. Suspend all I/O activity while you download firmware and NVSRAM to a storage subsystem with a
single controller. If you do not suspend I/O activity, the host server will have failed I/O requests
because you have redundant controller connections between the host server and the storage
subsystem.
5. Always check the storage subsystem controller firmware readme file for any controller firmware
dependencies and prerequisites before you apply the firmware updates to the storage subsystem.
Updating any components of the storage subsystem firmware without complying with the
dependencies and prerequisites might cause downtime (to fix the problems or recover).
6. Downgrading the controller firmware is not a supported function. This option should be used only
under the direction of IBM Support. Downgrading from 07.xx to 06.xx firmware levels is not
supported and will return an error if attempted.
If your existing controller firmware is 06.1x.xx.xx or later, you have the option to select the NVSRAM for
download at the same time that you upgrade or download the new controller firmware. Additionally,
you have the option to download the firmware and NVSRAM immediately but activate it later, when it
might be more convenient. See the online help for more information.
Note: The option to activate firmware at a later time is not supported on the DS4400 storage subsystem.
Determining firmware levels

Before you download a firmware upgrade, make sure that you know your current firmware version.
There are two different methods to determine storage subsystem, storage enclosure, drive, and ESM
firmware versions. Each method uses the Storage Manager client that manages the storage subsystem
with the attached storage enclosure.
Method one:
Go to the Subsystem Management window and select the menu option to display the storage subsystem
profile. When the Storage Subsystem Profile window opens, click the All tab and scroll through the
Profile For Storage Subsystem page to locate the following information. The Profile For Storage
Subsystem page contains all of the profile information for the entire storage subsystem, including the
firmware version numbers.
Storage subsystem controller firmware version
Firmware information types are:
v NVSRAM version
v Appware version (Appware is a reference to controller firmware.)
v Bootware version (Bootware is a reference to controller firmware.)
See the following example of profile information.
Controller in Enclosure 0, Slot A
Status: Online
Current configuration
Firmware version: 07.10.23.00.
Appware version: 07.10.23.00.
Bootware version: 07.10.23.00.
NVSRAM version: N1814D47R1010V05
Drive firmware version

See the following example of SATA drive data.
39
Product ID:
ST3750640NS
Package version:
EP58
Firmware version:
3.AEP
ATA Translator
Product ID:
Vendor:
Firmware Version:
43W9715 42D0003IBM
BR-2401-3.0
SLI
LP1158
ESM firmware version

See the following example of ESM data.
ESM card status:
Optimal
Firmware version:
9898
Configuration settings version:
FD 00.52 03/08/2007
Method two:
Complete the applicable procedure from the following options to obtain the specified firmware version.
To obtain the controller firmware version:
Right-click the Controller icon on the Physical tab of the Subsystem Management window and
select Properties. The Controller Enclosure properties window opens and displays the properties
for that controller.
You must perform this action for each controller.
To obtain the drive firmware version:
Right-click the Drive icon on the Physical tab of the Subsystem Management window and select
Properties. The Drive Properties window opens and displays the properties for that drive.
You must perform this action for each drive.
To obtain the ESM firmware version:
1. On the Physical tab of the Subsystem Management window, click the Drive Enclosure
Component icon (which is the icon farthest to the right). The Drive Enclosure Component
Information window opens.
2. Click the ESM icon in the left pane. The ESM information is displayed in the right pane of the
Drive Enclosure Component Information window.
3. Locate the firmware version of each ESM in the storage enclosure.
Downloading controller and NVSRAM firmware

Note: Perform a Collect All Support Data operation before you upgrade the controller firmware and
NVSRAM. See Critical event problem solving on page 205 for the data-collection procedures.
This section provides instructions for downloading storage subsystem controller firmware and NVSRAM.
Normally, the storage subsystem firmware download sequence starts with controller firmware, followed
by the NVSRAM, the ESM firmware, and the drive firmware.
Important: If you are upgrading from 06.xx to 07.xx, you must use the Controller Firmware Upgrade
Tool. See Using the IBM System Storage Controller Firmware Upgrade Tool on page 41. If you already
have the 07.xx firmware level, you are not required to use the Controller Firmware Upgrade Tool to
upgrade to another 07.xx level. However, the Upgrade Tool has diagnostic capabilities that might be
beneficial.
To
1.
2.
3.
40
download firmware version 06.1x.xx.xx or later, and NVSRAM, complete the following steps:
From the Enterprise Management window, select a storage subsystem.
Click Tools > Manage Device. The Subsystem Management window opens.
Click Upgrade > Controller firmware > Upgrade. The Download Firmware window opens.
Note: If the controller firmware is 7.77.xx.xx or later, the system automatically runs a pre-upgrade
check, which takes several minutes. The controller firmware upgrade proceeds only if the pre-upgrade
check is satisfactory. Storage subsystems with controller firmware versions 06.1x.xx.xx and later
support downloading of the NVSRAM file together with the firmware file. This download feature is
not supported in storage subsystems with controller firmware 05.4x.xx.xx or earlier. If your existing
controller firmware is version 05.4x.xx.xx or earlier, only a window for downloading firmware is
displayed.
4. Click Browse next to the Selected firmware file field to identify and select the file with the new
firmware.
5. Select Download NVSRAM file with firmware and click Browse next to the Selected firmware file
field to identify and select the file and identify and select the correct NVSRAM file name. Unless your
configuration has unique conditions, upgrade the NVSRAM at the same time as the controller
firmware. If you choose to transfer and activate immediately, do not select Transfer files but don't
activate them (activate later). Otherwise, select the check box to select Transfer files but don't
activate them (activate later). To activate the firmware at a later time, select the menu option to
activate the controller firmware in the Subsystem Management window.
Using the IBM System Storage Controller Firmware Upgrade Tool

The following information describes how to use the IBM System Storage Controller Firmware Upgrade
Tool to upgrade your DS4800, DS4700 or DS4200 Express controller firmware from 06.xx to 07.xx.
Important:
v Use the Controller Firmware Upgrade Tool only when you are migrating DS4800, DS4700, and DS4200
controllers from version 06.xx to version 07.xx.
v This tool is not intended for standard upgrades for controller, ESM, or drive firmware (upgrades
within the 6.xx.xx.xx code thread or 7.xx..xx.xx code thread). To perform a standard controller, ESM, or
drive-firmware upgrade, see Downloading controller firmware, NVSRAM, ESM firmware on page
38.
v With Storage Manager version 10.50 and later, the Controller Firmware Upgrade Tool has become part
of the Enterprise Management window and is no longer a separate tool. Click Tools > Upgrade
Controller Firmware to open a Controller Firmware Upgrade window.
Attention: Make sure that the firmware that you download is compatible with the Storage Manager
software that is installed on your storage subsystem. If incompatible firmware is downloaded, you might
lose access to the drives in the storage subsystem. If necessary, upgrade Storage Manager before you use
the IBM System Storage Controller Firmware Upgrade Tool.
Before you use the IBM System Storage Controller Firmware Upgrade Tool, make sure that you
understand the following guidelines.
v All data for DS4800, DS4700, and DS4200s storage subsystems must be backed up, and existing system
configurations must be saved. After the tool has completed an upgrade, controllers cannot return to
previous firmware version levels.
v You must perform the upgrade offline. You must perform the overall installation of Storage Manager
into an existing host environment online. For most failover drivers to take effect, you must reboot the
host.
v All devices must have Optimal status before you download firmware. Use the Healthcheck utility to
verify Optimal status on the devices.
v You must also check the current firmware level.
v Do not make changes to your configuration or remove drives or enclosures during the upgrade
process.
v For information about the current firmware versions, see Finding Storage Manager software, controller
firmware, and readme files on page xiii to find out how to access the most recent Storage Manager
readme files on the web.
41
Checking the device health conditions: To determine the health condition of your device, complete the
following steps:
1. From the Array Management window in the Storage Manager, right-click the storage subsystem.
Storage Manager establishes communication with each managed device and determines the current
device status.
There are six possible status conditions:
v Optimal: Every component in the managed device is in optimal working condition.
v Needs Attention: There is a problem with the managed device that requires intervention to correct
it.
v Fixing: A Needs Attention condition has been corrected, and the managed device is currently
changing to an Optimal status.
v Unresponsive: The management station cannot communicate with the device or with one controller
or both controllers in the storage subsystem.
v Contacting Device: Storage Manager is establishing contact with the device.
v Needs Upgrade: The storage subsystem is running a level of firmware that is no longer supported
by Storage Manager.
2. If the status is Needs Attention, write down the indicated condition. Contact an IBM technical support
representative for fault resolution.
Note: The Recovery Guru in Storage Manager also provides a detailed explanation of, and recovery
procedures for, the conditions.
Opening and using the Controller Firmware Upgrade Tool: To use the Controller Firmware Upgrade
Tool, click Tools > Firmware Upgrade in the Enterprise Management window. The Firmware Upgrade
window opens. The Firmware Upgrade Tool automatically completes a diagnostic check on these
subsystems to determine if they are healthy enough to perform a controller firmware upgrade.
Note:
v For any condition other than Optimal, you must contact IBM support for assistance. See Software
service and support on page xv for additional information.
v You can only upgrade from a major release to a major release (for example, 06.xx. to 07.xx) with this
tool. Do not attempt to perform this type of firmware upgrade in the Subsystem Management window.
v After you have upgraded to the 07.xx firmware level, you do not need to use the firmware upgrade
tool. Use the Subsystem Management window to perform any future firmware upgrades.
For more information about using the tool, click the Help button in the Controller Firmware Upgrade
Tool.
Adding a storage subsystem: To add a storage subsystem by using the Controller Firmware Upgrade
Tool, complete the following steps:
1. Click Add. The Select Addition Method window opens.
2. Click Automatic or Manual.
3. Click OK to begin adding storage subsystems.
4. If you want to see issues with an added storage subsystem that might impede firmware upgrading,
click View Log.
Downloading the firmware:
1. Select the storage subsystem that you want to activate. The Download button is enabled.
2. From the Enterprise Management window toolbar, click Tools > Upgrade Firmware. The Download
Firmware window opens.
3. Click Browse and select the controller firmware file that you want to download from its directory.
42
4. Click Browse and select the NVSRAM file from its directory.
5. Click OK. The firmware download begins. A status bar is displayed in the Controller Firmware
Upgrade window.
Viewing the IBM System Storage Controller Firmware Upgrade Tool log file: The Controller Firmware
Upgrade Tool log file documents any issues with the storage system that might prevent you from
updating the firmware. If you encounter any problems when you upgrade the firmware, click View Log
to open the log file. Correct the issues in the log file before you try to download the firmware again.
Downloading ESM firmware

This section provides instructions for downloading storage enclosure ESM firmware. Normally, the
storage subsystem firmware download sequence starts with the controller firmware, followed by the
NVSRAM, ESM firmware, and drive firmware.
To download the ESM firmware, complete the following steps:
1. In the System Management window, select Advanced > Maintenance > Download > ESM firmware.
The Download Environmental Card Firmware window opens.
2. Click Select All to direct the download to all storage enclosures. You can also select one storage
enclosure, or you can select multiple enclosures by pressing Ctrl while you select the enclosures.
Note: If you have selected multiple enclosures, suspend all I/O activity while the ESM firmware
downloads. If select only one storage enclosure at a time, you can download ESM firmware while the
server conducts I/O activity.
3. Click Browse to identify and select the file name of the ESM firmware file, and click Start to begin the
ESM firmware download.
4. In the Confirm Download window, type yes and click OK to start the download process.
5. After the ESM firmware download to all selected enclosures is complete, click Cancel to close the
window.
When you install a new ESM into an existing storage enclosure in a storage subsystem that supports
automatic ESM firmware synchronization, the firmware in the new ESM is synchronized automatically
with the firmware in the existing ESM. This resolves any ESM firmware mismatch conditions
automatically.
To enable automatic ESM firmware synchronization, make sure that your system meets the following
requirements:
v The Storage Manager Event Monitor must be installed and running.
v The storage subsystem must be defined in the Enterprise Management window of the Storage Manager
client (SMclient).
Note: As of the date of this document, the Storage Manager supports automatic ESM firmware
synchronization with EXP710 and EXP810 storage enclosures only. Contact IBM for information about
support for other types of storage enclosures in the future. To correct ESM firmware mismatch conditions
in storage enclosures without automatic ESM firmware synchronization support, you must download the
correct ESM firmware file with the ESM firmware download menu function in the SMclient Subsystem
Management window.
Downloading drive firmware

This section provides instructions for downloading drive firmware. Up to four different drive types can
have drive firmware updated at the same time. Drives are considered as different drive types if they
report different product IDs when an inquiry is made. See the online help for additional information.
Important:
43
1. The following procedures assume that you have the latest controller firmware version. If you have an
earlier firmware version, see Finding Storage Manager software, controller firmware, and readme
files on page xiii to obtain the applicable firmware version documentation.
2. IBM supports firmware download with I/O, sometimes referred to as concurrent firmware download.
This feature is not supported for drive firmware. You must schedule downtime for drive and ATA
translator firmware upgrade.
To download drive firmware for Storage Manager, complete the following steps:
1. Before you start the drive-firmware download process, complete the following tasks:
v Complete a full backup of all data on the drives that you select for the firmware upgrade.
v Unmount the file systems on all logical drives that access the drives that you select for the
firmware upgrade.
v Stop all I/O activity before you download drive firmware to a storage subsystem.
2. From the Enterprise Management window, select a storage subsystem.
3. On the Enterprise Management window menu bar, click Tools > Manage Device. The Subsystem
Management window opens.
4. On the Subsystem Management window menu bar, click Upgrade > Drive/ATA translator firmware
upgrade. The Download Drive Firmware wizard window opens to the Introduction page. Read the
instructions and click Next.
Note: Storage Manager offers you the option to download and update up to four different firmware
file types simultaneously.
5. Click Add to locate the server directory that contains the firmware that you plan to download.
6. Select the firmware file that you plan to download and click OK. The file is listed in the Selected
Packages window.
7. Repeat steps 5 and 6 for upto four drive types that you plan to download firmware and click Next.
Additional files are listed in the Selected Packages window.
8. Click Browse, and repeat step 7 until you have selected each firmware file that you plan to
download.
9. After you specify the firmware packages for download, click Next.
10. In the Select Drive window, click the Compatible Drives tab. The Compatible Drives page contains a
list of the drives that are compatible with the firmware package types that you selected. From that
list, select the drives to which you plan to download the drive firmware that you selected in steps 7
and 8. You can press and hold the Ctrl key while you select multiple drives individually, or you can
press and hold the Shift key while you select multiple drives that are listed in series.
Note: The firmware that you plan to download must be listed on the Compatible Drives page. If the
product ID of your drives matches the firmware type and it is not listed as compatible on the page,
contact your IBM technical support representative for additional instructions.
11. Click Finish to initiate download of the drive firmware to each compatible drive that you selected in
step 10.
12. When the Download Drive Firmware message opens with the question Do you want to continue?,
type yes and click OK to start the drive firmware download. The Download Progress window
opens. Do not intervene until the download process is completed. Each drive that is scheduled for
firmware download is designated as in progress until successful or failed.
13. If a drive is designated as failed, complete the following steps:
a. Click Save as to save the error log.
b. On the Subsystem Management window menu bar, click the menu option to display the storage
subsystem event log and complete the following tasks that are necessary to save the event log
before you contact your IBM service representative and proceed to the next step.
1) Click Select all.
44
2) Click Save the Storage Subsystem Event Log.

14. When the Close button becomes active, the drive firmware download process is complete. Click
Close to exit the Download Progress window.
15. Use either of the following procedures to determine or verify which level of drive firmware is on a
particular drive:
v Right-click the drive on the Logical or Physical page in the Subsystem Management window and
click Properties. The associated drive firmware version is listed in the drive properties table.
v Right-click Storage Subsystem > View Profile on the Logical or Physical page of the Subsystem
Management window.
Storage Manager premium features

Storage Manager supports the following premium features, which are available separately for purchase
from IBM or an IBM Business Partner:
Copy Services
The following copy services are available with Storage Manager:
v FlashCopy
v VolumeCopy
v Enhanced Remote Mirror Option
For more information about the Copy Services features, see the IBM System Storage DS Storage
Manager Copy Services User's Guide.
Storage Partitioning
Storage Partitioning is standard on all storage subsystems that are supported by DS3000, DS4000,
and DS5000 controller firmware versions. For more information about Storage Partitioning, see
the Storage partitioning overview on page 49.
FC/SATA Intermix premium feature
The IBM System Storage DS3000, DS4000, and DS5000 Fibre Channel and Serial ATA Intermix
premium feature supports the concurrent attachment of Fibre Channel and SATA storage
enclosures to a single storage subsystem controller configuration. You can use this Intermix
premium feature to create and manage distinct arrays that are built from either Fibre Channel
disks or SATA disks and allocate logical drives to the appropriate applications, using a single
storage subsystem.
For important information about using the Intermix premium feature, including configuration,
firmware versions that are required for specific Intermix configurations, and setup requirements,
see the IBM System Storage DS Storage Manager Fibre Channel and Serial ATA Intermix Premium
Feature Installation Overview. See your IBM representative or reseller for information about future
storage subsystem support for the FC/SATA Intermix premium feature.
Hardware enhancement premium features
These are the premium features that provide support for certain storage hardware configurations,
such as the following examples:
v a certain number of drive slots supported in the storage subsystems
v certain types of storage enclosures (for example, EXP810 attachment, or all eight EXP5060
attachments)
v certain types of drives (for example, solid state drives)
This premium feature category also includes the controller performance enhancement premium
feature.
Full Disk Encryption
The use of full disk encryption (FDE) secures data against threats when an FDE drive is out of its
owner's control.
45
Complete the following tasks to enable a premium feature on your storage subsystem:
v Obtaining the premium feature enable identifier
v Generating the feature key file
v Enabling the premium feature on page 47
Note: The procedure for enabling a premium feature depends on your version of the Storage Manager.
v Disabling premium features on page 47
To obtain the storage subsystem premium feature identifier string, make sure that your controller unit
and storage enclosures are connected, the power is turned on, and they are managed using the SMclient.
Obtaining the premium feature enable identifier

Each storage subsystem has its own unique premium feature enable identifier. This identifier ensures that
a particular feature key file is applicable only to that storage subsystem.
Before you obtain the feature enable identifier, complete the following prerequisites:
1. Make sure that you have available the feature activation code from the premium feature web
activation card, as well as the model, machine type, and serial number of the storage subsystem.
2. Make sure that the controller unit and storage expansion enclosures are connected, turned on, and
configured.
To obtain the feature enable identifier, complete the following steps:
1. Click Start > Programs > Storage Manager xx Client. The Enterprise Management window opens.
2. In the Enterprise Management window, double-click the storage subsystem for which you want to
enable the premium feature. The Subsystem Management window opens for the selected storage
subsystem.
3. Complete one of the following actions, depending on your version of the Storage Manager:
v If you are using Storage Manager version 9.x or earlier, click Storage Subsystem > Premium
Features > List. The List Premium Features window opens and displays the feature enable
identifier.
v If you are using Storage Manager version 10.x or later, click Storage Subsystem > Premium
Features.... The Premium Features and Feature Pack Information window opens. The feature enable
identifier is displayed at the bottom of the new window.
4. Record the feature enable identifier.
Note: To prevent a mistake when recording the feature enable identifier, copy the 32-character
identifier and paste it in the premium feature key request field.
5. Click Close to close the window.
6. Continue to Generating the feature key file.
Note: To check the status of an existing premium feature in Storage Manager version 9.x or earlier, select
Storage Subsystem > Premium Features > List from the menu.
Generating the feature key file

You can generate the feature key file with the Premium Feature Activation tool that at
http://www.ibm.com/storage/fasttkeys .
1. Complete the steps on the website.
Note: Make sure that you select the correct Premium Feature or Feature Pack after you are prompted.
The Feature key file is available for download on the webpage, and it can be emailed to you.
2. On your hard disk drive, create a new directory (for example, name the directory
FlashCopyfeaturekey).
46
3. Save the premium feature key file in the new directory.

If the premium feature key is lost, or if the premium feature identifier is changed and the premium
feature is no longer in compliance, you can request a premium feature reactivation key file at
http://www.ibm.com/storage/fasttkeys. You must have the same machine type, model, and serial
number information available that you used to generate the premium feature key files initially.
Enabling the premium feature

To enable the premium feature, follow the applicable procedure for your version of Storage Manager.
Enabling the premium feature in Storage Manager 9.x or earlier

To enable a premium feature in Storage Manager version 9.x or earlier, complete the following steps:
1. In the Subsystem Management window, click Premium Features > Enable.
2. Browse to the applicable key file in the directory that you created in the previous task, Generating
the feature key file on page 46.
3. Click OK.
4. Verify that the premium feature is enabled:
a. In the Subsystem Management window, click Storage Subsystem > Premium Features > List. The
List Premium Features window opens. The window shows the following information:
v The premium features that are enabled on the storage subsystem
v The feature enable identifier
b. Click Close to close the window.
Enabling the premium feature and feature pack in Storage Manager 10.x or later
To enable a premium feature in Storage Manager version 10.x or later, complete the following steps:
1. In the Subsystem Management window, click Storage Subsystem > Premium Features.... The
Premium Features and Feature Pack Information window opens.
2. To enable a premium feature from the list, click Enable or Use key file, depending on the version of
the controller firmware. A window opens that allows you to select the premium feature key file to
enable the premium feature. Follow the on-screen instructions.
3. Verify that the premium feature is enabled by inspecting the displayed list of premium features in the
Premium Features and Feature Pack Information window.
4. Click Close to close the Premium Features and Feature Pack Information window.
Enabling the feature pack

1. Click Change in the Premium Feature and Feature Pack Information window.
2. A window opens for you to select the feature pack key file. Select the key file and click OK.
3. Review the contents of the Feature Pack installed on storage subsystem field to verify whether the
feature pack is installed.
Important: Enabling a premium feature pack requires that the controllers be restarted. If the storage
subsystem for which the premium feature pack will be enabled is running, be sure to schedule downtime
to restart the controllers.
Disabling premium features

In normal system-operating conditions, you do not have to disable the premium features. However, if
you want to disable a premium feature, make sure that you have the key file or the premium feature
entitlement card with the premium feature activation code for generating the key file. You will need this
key file to re-enable the premium feature at a later time.
47
Note:
1. For DS3000 storage subsystems with controller firmware version 7.35 or earlier, you cannot use the
Storage Manager interface to disable a premium feature. Instead, you must use the Storage Manager
command-line (SMcli) scripts to disable the premium feature.
2. If you want to enable the premium feature in the future, you must reapply the Feature Key file for
that feature.
3. You can disable the Remote Mirror Option without deactivating the feature. If the feature is disabled
but activated, you can perform all mirroring operations on existing remote mirrors. However, when
the feature is disabled, you cannot create any new remote mirrors. For more information about
activating the Remote Mirror Option, see the IBM System Storage DS Storage Manager Copy Services
User's Guide or see Using the Activate Remote Mirroring Wizard in the Storage Manager online
help.
4. If a premium feature becomes disabled, you can access the website and repeat this process following
the re-activating premium features option.
Disabling the premium feature in Storage Manager 9.x or earlier

To disable a premium feature in Storage Manager version 9.x or earlier, complete the following steps:
1. In the Subsystem Management window, click Storage Subsystem > Premium Features > Disable. The
Disable Premium Feature window opens, which shows all of the premium features that are enabled.
2. Select one item in the list and click OK. A confirmation message states that a premium feature must
not be disabled.
3. Click Yes. The Working window opens while the feature is being disabled. When the feature has been
disabled, the Working window closes.
Disabling the premium feature in Storage Manager 10.x or later

To disable a premium feature in Storage Manager version 10.x or later, complete the following steps:
1. In the Subsystem Management window, click Storage Subsystem > Premium Features. The Premium
Features and Feature Pack Information window opens.
2. Select the premium feature that you want to disable and click Disable.
For additional assistance, contact your local IBM service provider.
Saving the storage subsystem profile

Important: You must save a storage subsystem profile whenever you modify the arrays and logical
drives in your storage subsystem. This saved profile contains detailed controller information, including
logical and physical disk configuration information, that can help you recover the configuration in the
event of a catastrophic failure. Do not save a profile for a storage subsystem on that same storage
subsystem.
To save a storage subsystem profile, select the menu option to display the subsystem profile in the
System Management window and click Save As when the Storage Subsystem Profile window opens. To
save the full profile, select the All tab. You can also select the menu option to save the support data to
collect all the various types of inventory, status, diagnostic and performance data from this storage
subsystem and save them in a single compressed file.
48
Chapter 4. Configuring storage

After Storage Manager is installed, you must configure the storage subsystem or subsystems. The
following topics in this chapter describe the tasks that are necessary for configuration:
v Storage partitioning overview
v Using the Task Assistant on page 50
v Configuring global hot-spare drives on page 67
v Configuring disk storage on page 63
v Defining a default host type on page 68
v
v
v
v
Defining a host group on page 70

Defining heterogeneous hosts on page 70
Defining the host and host ports on page 71
Mapping LUNs to a storage partition on page 71
Near the end of this chapter, the following topics provide optional information that might apply to
configuring your storage subsystems:
v Configuring the IBM System Storage DS5100 and DS5300 for IBM i on page 72
Note: This section applies only to storage configurations that use the IBM i operating system.
v Configuring and using optional premium features on page 74
Note: This section applies only to storage subsystems that have premium features.
v Using other features on page 76
v Tuning storage subsystems on page 80
Note: By default, the Setup tab in the Enterprise Management window opens first when you start
Storage Manager. See Enterprise Management window on page 11 for a detailed description of the
Enterprise Management window.
Storage partitioning overview

Before you create storage partitions, be aware of the following information:
v The Storage Manager Task Assistant provides a Storage Partitioning wizard that you can use to define
your host and host ports and map LUNs to the storage partitions. If your storage subsystem is running
controller firmware 05.xx.xx.xx, you cannot use the wizard. Both types of procedures are documented
in this section.
v These procedures assume that you have already created a physical connection between the host and
the storage subsystem controllers, and that you have also connected and zoned the switch (if
applicable). If you have not completed these connections, Storage Manager cannot list the worldwide
port names (WWPNs) or the iSCSI iqn-names of the HBAs during these procedures. In this case, you
must type the WWPNs into the applicable fields during the procedure that is described in Defining
the host and host ports on page 71.
v Create the host group at the storage subsystem level. Do not create host groups at the default group
level.
Note: If you have a DS4100 or a DS4300 configuration and partitioning is not enabled, you can use
the default host group.
49
v In case of multiple HBAs in the host connected to the storage subsystem, create a single host partition
to include all. Use the host group definition only to group a set of hosts that share the same set of
logical drives.
v In a cluster partition, perform logical drive mappings on the host group level so that all of the hosts
can recognize the same storage. In a normal partition, perform logical drive mappings on the host
level.
v To set up and assign IBM i LUNs on the DS5300 and DS5100 storage subsystems with the wizard, see
Configuring the IBM System Storage DS5100 and DS5300 for IBM i on page 72 for information
specific to IBM i configuration.
Using the Task Assistant

The Storage Manager Task Assistant provides a central location from which you can choose to perform
the most common tasks in the Enterprise Management window and in the Subsystem Management
window. You can use the Task Assistant to complete many of the procedures that are described in this
section.
Important: If you have controller firmware version 7.50 or later, the Storage Manager task descriptions
might differ slightly from the tasks in the following lists.
In the Subsystem Management window, the Task Assistant on the Setup tab (depending on the firmware
controller version) consists of shortcuts to these tasks:
v Configuring storage subsystems
v Defining hosts
v Creating a new storage partition
v Mapping additional logical drives
v Saving configurations
If there is a problem with the storage subsystem, a shortcut to the Recovery Guru is displayed. Use the
Recovery Guru to learn more about the problem and find solutions to correct the problem.
Important: If you have controller firmware version 7.50 or later, the Storage Manager procedure for
accessing the Task Assistant functionality is slightly different. There is no button and no separate window
for Task Assistant. Click the Setup tab in the Subsystem Management window to access the Task
Assistant menu in the Initial Setup Tasks window.
Note: The Task Assistant is automatically invoked every time you open the Subsystem Management
window, unless you select the Don't show the task assistant at startup again check box at the bottom of
the window.
Disk drives supported by IBM System Storage DS Storage Manager

The DS subsystem supports hard disk and solid state disk drive media types.
Depending on the models, the DS subsystem supports some or all of the following disk drive interfaces:
SATA In certain enclosures, the SATA disk drive requires an ATA translator or FC-SATA interposer that
helps you insert the drive into the drive slot with a FC connector.
Note: The SATA drives and the ATA translator or FC-SATA interposers are sold as a single
identity.
Fibre-Channel (FC)
There are no special requirements for FC drives.
50
SAS
For enclosures with FC mid plane, the SAS drive requires the FC-SAS interposer that helps you
insert into a drive slot with a FC connector. This category also includes NL SAS drives.
Note: The SAS drives and the FC-SAS interposers are sold as a single identity and is known as
FC-SAS drive.
In addition to the differences in the disk drive types and interfaces, there are few differences with respect
to the drive capabilities like T10 Protection Information (T10PI) or Full Disk Encryption/Self- Encryption
(FDE/SED) capabilities. Drive capacities are available for most of the supported drive media types, drive
interfaces, and drive capabilities. The DS subsystem does not support all types of drive media. For more
information on the type of drives available and supported for a given storage subsystem, refer to DS
subsystem RFAs. You can also refer the DS storage subsystem Installation, User's and maintenance guide
for more information on the FRU part list for the drives supported in a storage subsystem model. A
summary of supported drive type, drive interface and drive capability is shown in Table 12.
Table 12. Summary of supported drive types, interfaces and capabilities
Supported Disk
Media Type
Spinning hard disk
drives
Drive Interface
Drive capability
FDE capable
Non-FDE capable
SATA
N/A
N/A
N/A
Fibre-Channel (FC)
PI capable
Yes
Yes
Non-PI capable
Yes
Yes
PI capable
Yes
Yes
Non-PI capable
Yes
Yes
FC
Non-PI capable
N/A
Yes
SAS
Non-PI capable
N/A
Yes
NL SAS/SAS
Solid state disk drives
In the Subsystem Management, the Physical tab has a button that helps identify various drive types in a
given enclosure as shown in Figure 5 on page 52. When you click the button, all drives that meet the
button definition are highlighted in the physical view pane. In the enclosure, if all the drives meet the
button definition, the button will be disabled. For example, in Figure 5 on page 52 all the drives in
.
enclosure 3 are of FC interface, hence the Fibre Channel button is displayed as
51
Figure 5. Subsystem Management Physical tab
Rules for selecting drives when creating a RAID array

These are the things to consider when selecting drives for a RAID array
v The RAID array can be created using only drives using the same drive interface.
For example, you cannot create an RAID array with FC, SAS and SATA drives even though the SATA
and SAS drives have interposers to allow them to behave like FC drives. Also, a drive with a specific
drive interface cannot be used as a spare for drive in a RAID array with a different drive interface.
v A RAID array cannot have a combination of spinning hard disk drives and solid state drives.
v Because NL-SAS and SAS drives operate at a different rotational speeds, do not mix the NL-SAS and
SAS drives in the same RAID array. The NL-SAS operates at 7200 rpm and the SAS drives operate at
10K or 15K rpm. In a RAID array composed of SAS drives and NL-SAS drives, it is possible to use a
NL-SAS to replace a failed SAS drive or SAS drives to replace a failed NL-SAS drive.
v Do not mix drives of the same drive interface that operate at different rotational speeds in the same
RAID array. The Storage Manager GUI or SM command line interface does not prevent this
configuration. If a suitable drive is not available, the controller firmware might select an available
hot-spare drive with a different rotation speed as a spare for the failed drive. In case the hot spare
drive has a lower rotation speed, replace the failed drive as soon as possible.
52
v If a drive of required rotational speed is not available, IBM might supply a similar drive with higher
rotational speed as a replacement FRU. The performance of the array is not affected when a higher
rotational speed drive is used as a replacement.
v In a RAID array, drives of different capabilities like T10PI or FDE can mix with the drives without
these capabilities in the same RAID array only if one of the drive capabilities is not enabled for that
RAID array. For example, you can create a RAID array with both T10PI supported drives and
non-T10PI supported drives. However, the created array will not be able to operate with T10PI
functionality enabled.
v Drives with lower rotational speed can be used as spares for array with drives having higher rotational
speeds. It is recommended that you do not mix drives with different rotational speeds in the same
RAID array because the performance of an array might be degraded with lower rotation speed drives.
v Drives with different sizes can be mixed in a RAID array. However, the array will be created with all
drives having size of the smallest drive size in the RAID array.
v A RAID array with additional capabilities enabled, like FDE and T10PI, cannot have drives without the
enabled capabilities used as spares for a failed drive in the RAID array. For example, a RAID array
with T10PI and FDE enabled requires a drive that has T10PI and FDE capabilities as a hot-spare drive.
Solid state drive (SSD) attributes

Solid State drives are drives that store data in a flash memory chip instead of on rotating hard disk
surfaces resulting in faster random access write/read speeds than hard disk drives.
Because flash devices have certain write cycle count limitations, these drives contain additional spare
flash memory chips to support write cycle use during the drive warranty period. Figure 6 on page 54
shows an SSD disk drive and the percentage of the remaining spare blocks in the SSD drive. SSD is
supported with controller firmware version 7.60.xx.xx and later because it supports media scan for logical
drives in RAID arrays composed of SSD drives. However, controller firmware version 7.77.xx.xx or later
is recommended.
53
Figure 6. Solid state disk (SSD) display
T10PI capable drive attributes

T10PI capable drives support the industry standard extension T10 Protection information (T10 PI or
T10PI) specified for the SCSI protocol. T10PI standard is also referred to as T10 DIF (Data Integrity Field).
This standard is designed to provide an extra level of data integrity by safeguarding each user data block
with 8 bytes of integrity metadata while the data is transferred between the storage controller and the
T10PI-initialized disk drives. This extra level of data integrity is also extended to the server when the
storage subsystem is I/O attached to IBM Power servers running the AIX operating system. T10 PI
support within AIX operating system includes the Protection Information metadata with user data
transferred between the AIX server and the storage controller. T10PI standard is designed to provide the
user with end-to-end protection and correction against silent data corruption due to device driver errors,
filesystem errors or misdirected, lost, phantom, or torn writes.
The T10PI capable drives are initialized as Type 2 T10PI drives. These drives have 520 byte sectors
instead of the standard 512 byte sectors. The additional 8 bytes contains the Protection Information
metadata described in Table 13 on page 55, that can be used to verify the data in-flight and at rest.
54
Table 13. Protection Information metadata (8 bytes)

Byte #1
Byte #2
Byte #3
Byte #4
Byte #5
Byte #6
Byte #7
Byte #8
Logical Block Guard (2

bytes)
Logical Block Application

Tag (2 bytes)
Logical Block Reference Tag (4 bytes)
v 16-bit CRC
v May be owned by
application client
(initiator) or device
server (target)
v Protect against out-of-order and misdirected write

scenarios
v Receiver computes CRC

on received data and
compares to received
CRC
v Protect the data portion
of the sector
v Receiver optionally checks against expected value
v Checked only by the

owner
The DS storage subsystem supports the T10PI Type1 host protection scheme. Figure 7 shows where
Protection Information metadata is checked from the application in the host to the drive in the storage
subsystem.
Figure 7. Protection Information (P) check points
Figure 8 on page 56 shows the properties of a non-FDE T10PI drive in the physical view of the subsystem
management window.
55
Figure 8. Non-FDE T10PI drive - properties
Rules for enabling T10PI functions

Enable T10PI functions in a DS storage subsystem, requires that some conditions are met.
T10PI functionality supported controller firmware
The T10PI functionality is enabled by the controller firmware instead of a premium feature. The
minimum version of controller firmware that supports T10PI is 7.77.xx.xx. The only DS
subsystems that support T10PI are the DS3950, DS5020 and DS5100/DS5300. Please contact your
IBM resellers or representatives for support of T10PI on other DS storage subsystems in the
future.
Note: T10PI drives can be used in the storage subsystem with controller firmware that does not
support T10PI functionality. In such cases, the drive is treated as non-T10PI capable drives.
Fibre-Channel Host Interface Card (HIC)
The DS storage subsystem must have Fibre-Channel Host Interface card installed. Additionally,
the T10PI enabled logical drive must be mapped to a host port that is discovered through the DS
storage subsystem Fibre-Channel HIC port. For example, if the controller has a FC HIC and an
iSCSI HIC installed, the T10PI-enabled logical drives can be mapped to the host port that is
discovered through the FC HIC port only. An error will be displayed if you attempt to map a
T10PI-enabled logical drive to a host port that is discovered through the iSCSI HIC.
(For an AIX server) NVSRAM file with T10PI-enabled host type
The NVRAM files provided with the controller firmware version 7.77.xx.xx or later must be
installed in the storage subsystem. These NVSRAM files have the T10PI enable bit set in the AIX
56
and AIXAVT host type regions to extend the T10PI functionality to the server. Without this bit set
in the host type region, T10PI functionality is enabled between the subsystem controller and
drives only.
Note: Refer to the SSIC for information about the types of FC adapters supported along with the
required device driver, firmware version, and the versions of AIX operating systems that provide
T10PI support at the server.
Enabling and disabling a T10PI capable RAID array

To create a T10PI-capable RAID array, all of the drives in the RAID array must be T10PI capable.
This task assumes that you are using the subsystem management interface to define the array.
To enable T10PI capability on a RAID array:
Note: The screenshots in this section are only illustrative and may differ from the actual UI depending
on the Storage Manager and controller firmware versions.
v In the Specify Capacity/Name (Create Logical Drive) dialog click Enable T10 PI (Protection
Information) (T10 PI) on the new logical drive as shown in Figure 9 on page 58.
Note: If you create the logical drive without T10PI functionality, it cannot be converted into a
T10PI-enabled logical drive later.
57
Figure 9. Enabling T10 PI on a logical drive
Note: An additional parameter also exists on the appropriate SMcli commands to indicate whether a
logical drive is created with T10PI enabled.
Figure 10 on page 59 shows a RAID array and its logical drive that has T10PI functionality enabled.
The shield icon indicates that the array is a T10PI capable RAID array.
58
Figure 10. RAID drive - Protection Information (T10 PI) - enabled
Note: You do not have to create all logical drives in a T10PI-capable RAID array with T10PI enabled. For
example, logical drive 4 of RAID array 4 is not T10PI enabled but logical drives 2 and 5 are T10PI
enabled as shown in Figure 11 on page 60. However, because you can only enable T10PI functionality at
the time of creation, it is recommended to create a logical drive with T10PI enabled and then disable it at
later time, if necessary.
59
Figure 11. Example - Logical Drive 4 of RAID array 4 - T10PI not enabled
To disable T10PI capability for a RAID array:

v Right-click the drive that you are disabling T10PI capability and select Disable T10PI (Protection
Information) (T10PI) as shown in Figure 12 on page 61.
Notes:
There is also an SMcli command to disable T10PI capability.
Once you disable T10PI capability on a logical drive, you cannot simply enable T10 PI on the same
logical drive; you must delete the drive and recreate it with T10PI enabled.
60
Figure 12. Disabling T10PI
Full Disk Encryption (FDE) attributes

The Full Disk Encryption (FDE) or Self-encryption (SED) drives have built-in encryption mechanisms to
protect the drive information from unauthorized access from outside the DS storage subsystem.
The secured FDE/SED drive is locked when power is switched on. Unlock the drive by sending the
appropriate security key from the controller to the drive. Manage the security key locally inside the
controller or through an external key manager like IBM Tivoli Key Lifecycle Manager (TKLM). For
additional security, the drive encrypts before it is written preventing the data on the disk surface from
being scanned when the drive fails or is removed from active use. Figure 13 on page 62 shows the
properties of a non-T10PI FDE drive in the subsystem management window.
61
Figure 13. Non-T10PI FDE drive - properties
The FDE capable RAID array is shown with either the unlock icon if the array is not secured and with
the lock icon if the array is secured; as shown in Figure_10. For more information about FDE drives, see
Chapter 6, Working with full disk encryption, on page 143.
62
Figure 14. FDE capable RAID array - security details
Configuring disk storage

An array is a set of Fibre Channel, SAS, SATA, or solid state drives that are logically grouped together to
form a Redundant Array of Independent Disks (RAID). Arrays can be either standard or secured (with
full disk encryption).
Creating an array
To create an array from unconfigured capacity nodes, complete the following steps in the Subsystem
Management window:
1. Use either of the following two methods to create a new array:
v Select Total Unconfigured Capacity, and click Array > Create.
v Select and right-click Total Unconfigured Capacity, and click Create Array.
The Introduction (Create Array) window opens.
2. Click Next. The Array Name & Drive Selection (Create Array) window opens.
3. Take the applicable action for the following fields:
v Array name: Enter a name for the new array. The name can be a maximum of 30 characters.
v Drive selection: Select Automatic or Manual (Advanced).
63
Automatic
Choose from a list of automatically generated drive and capacity options. This option is
preselected by default.
Manual (Advanced)
Choose specific drives to obtain capacity for the new array.
v Click Next. The RAID Level and Capacity (Create Array) window opens.
Specify the RAID level (redundancy protection).
Select the number of drives (overall capacity) for the new array.
Click Finish. The Array Created window opens.
If you want continue the process to create a logical drive, click Yes; if you want to wait to create a
logical drive at another time, click No.
4.
5.
6.
7.
Redundant array of independent disks (RAID)

Redundant array of independent disks (RAID) is available on all operating systems and relies on a series
of configurations, called levels, to determine how user and redundancy data is written and retrieved from
the drives. The storage subsystem controller firmware supports six RAID level configurations:
v RAID-0
v RAID-1
v
v
v
v
RAID-3
RAID-5
RAID-6
RAID-10
Each level provides different performance and protection features. RAID-1, RAID-3, RAID-5, and RAID-6
write redundancy data to the drive media for fault tolerance. The redundancy data might be a copy of
the data (mirrored) or an error-correcting code that is derived from the data. If a drive fails, the
redundant data is stored on a different drive from the data that it protects. The redundant data is used to
reconstruct the drive information on a hot-spare replacement drive. RAID-1 uses mirroring for
redundancy. RAID-3, RAID-5, and RAID-6 use redundancy information, sometimes called parity, that is
constructed from the data bytes and striped along with the data on each disk.
Table 14. RAID level descriptions
RAID level
Short description
Detailed description
RAID-0
Note: RAID-0 does
not provide data
redundancy.
Non-redundant,
striping mode
RAID-0 offers simplicity, but does not provide data redundancy. A

RAID-0 array spreads data across all drives in the array. This
normally provides the best performance, but there is not any
protection against single drive failure. If one drive in the array fails,
all logical drives in the array fail. This RAID level must not be used
for high data-availability needs. RAID-0 is better for noncritical data.
64
Table 14. RAID level descriptions (continued)

RAID level
Short description
Detailed description
RAID-1 or RAID-10
Striping/Mirroring
mode
v A minimum of two drives are required for RAID-1: one for the
user data and one for the mirrored data. The DS3000, DS4000, or
DS5000 storage subsystem implementation of RAID-1 is a
combination of RAID-1 and RAID-10, depending on the number
of drives that are selected. If only two drives are selected, RAID-1
is implemented. If you select four or more drives (in multiples of
two), RAID 10 is automatically configured across the array; two
drives are dedicated to user data, and two drives are dedicated to
the mirrored data.
v RAID-1 provides high performance and the best data availability.
On a RAID-1 logical drive, data is written to two duplicate disks
simultaneously. On a RAID-10 logical drive, data is striped across
mirrored pairs.
v RAID-1 uses disk mirroring to make an exact copy of data from
one drive to another drive. If one drive fails in a RAID-1 array,
the mirrored drive takes over.
v RAID-1 and RAID-10 are costly in terms of capacity. One-half of
the drives are used for redundant data.
RAID-3
High-bandwidth
mode
v RAID-3 requires one dedicated disk in the logical drive to hold

redundancy information (parity). User data is striped across the
remaining drives.
v RAID-3 is a good choice for applications such as multimedia or
medical imaging that write and read large amounts of sequential
data. In these applications, the I/O size is large, and all drives
operate in parallel to service a single request, delivering high I/O
transfer rates.
RAID-5
High I/O mode
v RAID-5 stripes both user data and redundancy information

(parity) across all of the drives in the logical drive.
v RAID-5 uses the equivalent of one drive capacity for redundancy
information.
v RAID-5 is a good choice in multi-user environments such as
database or file-system storage, where the I/O size is small and
there is a high proportion of read activity. When the I/O size is
small and the segment size is appropriately chosen, a single read
request is retrieved from a single individual drive. The other
drives are available to concurrently service other I/O read
requests and deliver fast read I/O request rates.
RAID-6
Block-level striping
with dual distributed
parity
RAID-6 is an evolution of RAID-5 and is designed for tolerating two

simultaneous disk drive failures by storing two sets of distributed
parities:
v RAID Level 6 uses the equivalent of the capacity of two drives (in
an array) for redundancy data.
v RAID Level 6 protects against the simultaneous failure of two
drives by storing two sets of distributed parities.
Note: Not all DS storage subsystems support RAID-6. Check the
announcement letter or the Installation, User's, and Maintenance Guide
for your storage subsystem to determine whether RAID-6 and the
minimum version of controller firmware required is supported for
your storage subsystem.
Note: One array uses a single RAID level, and all redundancy data for that array is stored within the
array.
65
The capacity of the array is the aggregate capacity of the member drives, minus the capacity that is
reserved for redundancy data. The amount of capacity that is needed for redundancy depends on the
RAID level that is used.
To perform a redundancy check, click Advanced > Recovery > Check array redundancy. The redundancy
check performs one of the following actions:
v Scans the blocks in a RAID-3, RAID-5, or RAID-6 logical drive and checks the redundancy information
for each block
v Compares data blocks on RAID-1 mirrored drives
Important: When you select Check array redundancy, a warning message opens that informs you to use
the option only when you are instructed to do so by the Recovery Guru. It also informs you that if you
have to check redundancy for any reason other than recovery, you can enable redundancy checking
through Media Scan.
Creating a standard logical drive

A standard logical drive is a logical structure that is the basic structure that you create to store data on the
storage subsystem. The operating system recognizes a logical drive as a single drive. You can create a
logical drive from an array. Choose a RAID level to meet application needs for data availability and to
maximize Fibre Channel I/O performance if you have created a logical drive from an array.
Note: For cluster configurations, if you add or delete logical drives, you must make them known to both
nodes A and B.
To create a logical drive, complete the following steps in the Subsystem Management window:
1. On the Logical or Physical page of the Introduction (Create Logical Drive) window, click Free
Capacity for an array for which you want to create a new logical drive, right-click the array , and
click Create Logical Drive. Click Next.
2. In the Specify Capacity/Name (Create Logical Drive) window, specify the following parameters for
the logical drive that you are creating:
New logical drive capacity
The capacity can be the entire unconfigured capacity in an array or a portion of the array
capacity.
Units
Select GB, MB, or TB, depending upon the available capacity.
Name Type a name that is unique in the storage subsystem, up to a maximum of 30 characters.
3. Under Advanced logical drive parameters, select one of the following options:
Use recommended settings
Select this option to create the logical drive, using the storage subsystem default settings.
After you select Use recommended settings, click Next. Proceed to step 5.
Customize settings (I/O characteristics and controller ownership)
Choose this option to customize your I/O characteristics, controller ownership, and
logical-drive-to-LUN mapping settings. After you select Customize settings, click Next.
Proceed to step 4.
4. In the Advanced logical drive parameters window, specify the applicable I/O characteristics
(characteristics type, segment size, and cache read-ahead multiplier) and click Next. The Specify
Logical Drive-to-LUN Mapping (Create Logical Drive) window opens.
Note: The I/O characteristics settings can be set automatically or they can be specified manually,
according to one of the following logical drive usages: file system, database, or multimedia.
5. In the Specify Logical Drive-to-LUN Mapping (Create Logical Drive) window, specify the logical
drive-to-LUN mapping.
66
The logical drive-to-LUN mapping preference can be one of the following two settings:
Default mapping
The Automatic setting specifies that a LUN is automatically assigned to the logical drive,
using the next available LUN within the default host group. This setting grants logical drive
access to host groups or host computers that have no specific logical drive-to-LUN mappings
(those that were designated by the default host group node in the Topology view). If the
Storage Partition feature is not enabled, you must specify the Automatic setting. In addition,
you can also change the host type to match the host operating system.
6.
7.
8.
9.
10.
Map later using the Mappings View

This setting specifies that you are not going to assign a LUN to the logical drive during
creation. This setting enables you to define a specific logical drive-to-LUN mapping and
create storage partitions, using the Mappings Defined option. Specify this setting when you
enable storage partitioning.
Click Finish to create the logical drive. The Creation Successful (Create Logical Drive) window
opens.
If you want to create another logical drive, click Yes in the Creation Successful (Create Logical Drive)
window and proceed to step 9; otherwise, click No. When the Completed (Create Logical Drive)
window opens, click OK, and continue with step 10.
In the Allocate Capacity (Create Logical Drive) window, choose to create the new logical drive from
free capacity on the same array, free capacity on a different array, or from unconfigured capacity
(create a new array). Repeat the process, beginning with step 1. The Completed (Create Logical
Drive) window opens.
Click OK.
Register the logical drive with the operating system.
After you create logical drives with automatic logical drive-to-LUN mappings, follow the applicable
instructions for your operating system in Identifying devices on page 120 to discover the new logical
drive.
Configuring global hot-spare drives

You can assign available physical drives in the storage subsystem as a global hot-spare drives to keep data
available. A global hot spare contains no data and acts as a standby in case a drive fails in a RAID 1,
RAID 10, RAID 3, RAID 5, or RAID 6 arrays. If a drive in an array fails, the controllers automatically use
a hot-spare drive to replace the failed physical drive while the storage subsystem is operating. The
controller uses redundancy data to automatically reconstruct the data from the failed physical drive to the
replacement (hot-spare) drive. This is called reconstruction. The hot-spare drive adds another level of
redundancy to the storage subsystem. If a physical drive fails in the storage subsystem, the hot-spare
drive is automatically substituted without requiring a physical swap.
Assigning hot-spare drives

There are two ways to assign hot-spare drives for arrays defined in the storage subsystem:
v Automatically assign drives: If you select this option, hot-spare drives are automatically created for
the best hot-spare coverage, using the drives that are available. This option is always available.
v Manually assign individual drives: If you select this option, hot-spare drives are created out of those
drives that were previously selected on the Physical tab. This option is not available if you have not
selected any drives on the Physical tab.
If you choose to manually assign the hot-spare drives, select a drive with a capacity equal to or larger
than the total capacity of the drive that you want to cover with the hot spare. For example, if you have
an 18 GB drive with configured capacity of 8 GB, you could use a 9 GB or larger drive as a hot spare.
Generally, you must not assign a drive as a hot spare unless its capacity is equal to or greater than the
67
capacity of the largest drive in the storage subsystem. For maximum data protection, you must use only
the largest capacity drives for hot-spare drives in mixed capacity hard drive configurations. There is also
an option to manually unassign individual drives.
If a drive fails in the array, the hot spare can be substituted automatically for the failed drive without
requiring your intervention. If a hot spare is available when a drive fails, the controller uses redundancy
data to reconstruct the data onto the hot spare.
Note: Drives with different interface protocols or technologies cannot be used as hot-spares for each
other. For example, SATA drives and Fibre Channel drives cannot act as hot spares for each other.
Restoring data from hot-spare drives

After the failed drive is physically replaced, you can use either of the following options to restore the
data:
v When you have replaced the failed drive, the data from the hot spare is copied back to the replacement
drive. This action is called copyback.
v You can assign the hot spare as a permanent member of the array. Performing the copyback function is
not required for this option.
If you do not have a hot spare, you can still replace a failed drive while the array is operating. If the
drive is part of a RAID Level 1, RAID Level 3, RAID Level 5, RAID Level 6, or RAID Level 10 array, the
controller uses redundancy data to automatically reconstruct the data onto the replacement drive.
If you select Manually unassign drives, the hot-spare drives that you selected on the Physical tab are
unassigned. This option is not available if you have not selected any drives on the Physical tab.
Defining a default host type

Before you use the logical drives in a host computer, you must specify the correct host type. The host
type determines how the storage subsystem controllers work with each operating system on the hosts to
which they are connected. If all of the host computers that are connected to the same storage subsystem
are running the same operating system and you do not want to define partitioning, you can define a
default host type.
To verify the current default host type, complete the following steps:
1. In the Subsystem Management window, click Storage subsystem > View profile. A Storage
Subsystem Profile window opens.
2. Click the Mappings tab and scroll down to NVSRAM Host Type Index Definitions. The host-type
name of the index that has the word DEFAULT next to it is the default host type.
3. Click Close.
The host-type setting that you specify when you configure Storage Manager determines how the storage
subsystem controllers work with the operating systems on the connected hosts. All Fibre Channel HBA
ports that are defined with the same host type are handled in the same way by the storage subsystem
controllers. This determination is based on the specifications that are defined by the host type. Some of
the specifications that differ according to the host-type setting include the following options:
Auto Drive Transfer
Enables or disables the Auto-Logical Drive Transfer feature (ADT).
Enable Alternate Controller Reset Propagation
Determines whether the controller will propagate a Host Bus Reset, Target Reset, or Logical Unit
Reset to the other controller in a dual controller storage subsystem to support Microsoft
Clustering Services.
68
Allow Reservation on Unowned LUNs

Determines the controller response to Reservation/Release commands that are received for LUNs
that are not owned by the controller.
Sector 0 Read Handling for Unowned Logical Drives Enable Sector 0 Reads for Unowned Logical
Drives
Applies only to host types for which the ADT feature is enabled. For non-ADT hosts, this option
has no effect.
Maximum Sectors Read from Unowned Logical Drives
Specifies the maximum allowable sectors (starting from sector 0) that can be read by a controller
that does not own the addressed logical drive. The value of these bits specifies the maximum
number of additional sectors that can be read in addition to sector 0.
Reporting of Deferred Errors
Determines how the storage subsystem controller deferred errors are reported to the host.
Do Not Report Vendor Unique Unit Attention as Check Condition
Determines whether the controller reports a vendor-unique Unit Attention condition as a Check
Condition status.
World Wide Name In Standard Inquiry
Enables or disables Extended Standard Inquiry.
Ignore UTM LUN Ownership
Determines how an inquiry for the Universal Access LUN (UTM LUN) is reported. The UTM
LUN is used by Storage Manager to communicate to the storage subsystem in in-band
management configurations.
Report LUN Preferred Path in Standard Inquiry Data
Reports the LUN preferred path in bits 4 and 5 of the Standard Inquiry Data byte 6.
Enable Host support for T10PI
Enable or Disable Host support for T10PI. If disabled, the controller strips the additional 8 bytes
with T10PI information before sending data to the host.
In most storage subsystem configurations, the NVSRAM settings for each supported host type for a
particular operating-system environment are sufficient for connecting a host to the storage subsystem.
You do not have to change any of the host type settings for NVSRAM. If you think you have to change
the NVSRAM settings, contact your IBM support representative before you proceed.
To
1.
2.
3.
define a default host type, complete the following steps:

Click Storage subsystem > Change > Default host-type. The Default Host-type window opens.
From the list, select the host type.
Click OK.
Note:
In the Veritas Storage Foundation Linux environment, the default host type must be set to 13.
Host type VMWARE has been added to NVSRAM as an additional host type. DS4200 and DS4700 will
use index 21.
All other supported systems will use index 16.
Although not required, if using a Linux host type for a VMWARE host, it is recommended to move to the
VMWARE host type since any upgrading of controller firmware and NVSRAM would continue to require
running scripts, whereas using the VMWARE host type does not require running scripts.
v The controllers do not need to be rebooted after the change of host type
69
v The host will need to be rebooted

v Changing the host type should be done under low I/O conditions
Defining a host group

A host group is an entity in the Storage Partitioning topology that defines a logical collection of host
computers that require shared access to one or more logical drives. You can grant individual hosts in a
defined host group access to storage partitions, independently of the host group. You can make logical
drive-to-LUN mappings to the host group or to an individual host in a host group.
You must create the host group at the storage subsystem level; do not create host groups at the default
group level. However, you can use the default host group if you are running a storage subsystem
configuration without partitioning enabled.
To define a host group, complete the following steps:
1. Click the Mappings View tab on the Subsystem Management window.
2. In the Topology section of the Mappings View page, highlight the name of the storage subsystem, and
click Mappings > Define > Host Group.
Note: Make sure that the storage subsystem is highlighted in the left pane of the Subsystem
Management window. Do not highlight Undefined Mappings.
3. Type a name for the new host group. Click Add, and then click Close.
4. Highlight the new host group and click Mappings > Define > Host.
5. Type the name of the host to which the storage subsystem is attached. Click Add, and then click
Close.
6. Highlight the host that you just added, and then right-click and select Define Host Port.
7. Select the host port identifier (WWPN) for the first HBA (for example, 10:00:00:00:c9:24:0c:3f). If
you do not see the identifier in the host port identifier menu, you can enter it manually. Otherwise,
verify that the switch is properly zoned and cabled.
Note: If you are configuring storage for IBM i, the port is on the first adapter. IBM i requires two
adapters to make a valid configuration.
8. Change the host type and click Add.
Important: Failure to change the host type from the default might cause unwanted results. See the
Storage Manager readme file for a list of host types that you can use for each host operating system.
9. If you are configuring an additional HBA to this partition, select the host port for the next HBA, click
Add, and click Close.
Defining heterogeneous hosts

The heterogeneous hosts feature enables hosts that are running different operating systems to access a
single storage subsystem. Storage Manager supports up to 512 storage partitions on some subsystems,
which enables a multiple host-type storage subsystem to share storage capacity, consolidate storage, and
reduce storage management costs.
Host computers can run on different operating systems or variants of the same operating system. When
you define a host type in the Define New Host Port window, the heterogeneous hosts feature enables the
controllers in the storage subsystem to tailor their behavior (such as LUN reporting and error conditions)
to the needs of the operating system or variant of the host that is sending the information.
Note:
70
1. During host-port definition, you must set each host type to the applicable operating system so that
the firmware on each controller can respond correctly to the host.
2. You must enable storage partitioning, which is a premium feature. You must use the partition key that
you saved at installation or go to the IBM webpage for feature codes to reactivate and obtain a new
feature key. For more information about premium features, see Storage Manager premium features
on page 45.
Defining the host and host ports

To define the host and host ports by using the Define a host and host ports wizard, complete the
following steps:
1. In the Topology section of the Mappings view of the Subsystem Management window, right-click the
new host group and select Define Host. The Introduction (Define Host) window opens.
2. Click Next. The Specify Host Name/HBA Attribute (Define Host) window opens.
3. Type the host name in the Specify Host Name/HBA Attribute (Define Host) window. In the left panel,
select the correct WWPN of the HBA host port. Click Add.
Note: If there is not yet a physical connection between the host and the storage subsystem controllers,
the WWPNs will not be displayed. In this case, you must type the correct WWPN in the field.
4. Click Edit, and then type an alias name (for example, Port1).
5. For a configuration with two or more HBAs, repeat step 3 and step 4 for each host port that you need
to define, and then skip to step 6.
6. Click Next. The Specify Host Type window opens.
7. Select the correct host type from the menu and click Next.
Important: Failure to change the host type from the default to a specific host operating system will
cause unwanted results.
If you are configuring storage for IBM i, be sure to select IBM i from the Host type (operating
system) list.
Note: In advanced setups, a LUN 0 might be assigned to a host group or host definition that does
not allow IBM i as the host type. To fix this problem, remove the LUN 0 setting, change the operating
system to IBM i, and add the LUN that you previously removed.
The Review window opens.
8. Review the information for accuracy. Make any necessary changes, and click Next. If you want to
define another host, select Define another host. To finish, click Exit. The wizard closes.
Mapping LUNs to a storage partition

This section describes how to map LUNs to a storage partition with the following procedures:
v Mapping LUNs to a new partition
v Adding LUNs to an existing partition on page 72
Mapping LUNs to a new partition

To map LUNs to a newly created partition, complete the following steps:
1. Select the Mappings view of the Subsystem Management window.
2. In the Topology section, right-click the host on which you want to map LUNs, and select Define
Storage Partitioning. The Define Storage Partitioning window opens.
3. In the Define Storage Partitioning window, select Host, then click Next.
4. Select the logical drive by name, on the right side of the window.
5. Either accept the default LUN ID or change it, and click Add.
71
6. Repeat step 5 for each LUN that you want to map to the partition.
Note: You can also use the Storage Partitioning wizard feature of the Storage Manager Task Assistant to
map LUNs to a new storage partition.
Adding LUNs to an existing partition

To map new LUNs to an existing partition, complete the following steps. Repeat these steps for each
LUN that you want to add to the partition.
1. Click the Mappings View tab on the Subsystem Management window.
2. In the Topology section, right-click the host or host group on which you want to map LUNs, and
select Define Additional Mappings. The Define Additional Mapping window opens.
3. In the Define Additional Mapping window, select the following options, and then click Add:
v Host group or host
v Logical unit number (LUN)(0-255)
v Logical drive
Configuring the IBM System Storage DS5100 and DS5300 for IBM i
Use the information in the following sections, in combination with the Configuring disk storage on
page 63 and Defining a host group on page 70 sections, to set up and assign IBM i LUNs on the
DS5100 and DS5300 storage subsystems with the Storage Manager software.
Assigning a port identifier for IBM i

When you use the Storage Manager to enter a port identifier for IBM i, the port is on the first adapter.
IBM i requires two adapters to make a valid configuration. The following illustration shows the setup
window where you assign the port identifier.
72
Figure 15. Assigning a port identifier for IBM i
Defining IBM i as the host type

When you use the Storage Manager to define a host type, select IBM i from the Host type (operating
system) list.
Important: In advanced setups, a LUN 0 might be assigned to a host group or host definition that does
not allow IBM i as the host type. To fix this problem, remove the LUN 0 setting, change the operating
system to IBM i, and then add the LUN that you previously removed.
The following illustration shows the setup window where you define the IBM i as the host type.
73
Figure 16. Selecting IBM i as the host type
Configuring and using optional premium features

This section describes optional premium features, including FlashCopy, VolumeCopy, Remote Mirror, and
Full Disk Encryption.
Note: For more information about these optional premium features, see the IBM System Storage DS
Storage Manager Copy Services User's Guide or contact your IBM reseller or IBM marketing representative.
About FlashCopy
A FlashCopy logical drive is a logical point-in-time image of a logical drive, called a base logical drive. A
FlashCopy logical drive has the following features:
v It is created quickly and requires less disk space than an actual logical drive.
v It can be assigned a host address, so that you can perform backups with the FlashCopy logical drive
while the base logical drive is online and accessible.
v You can use the FlashCopy logical drive to perform application testing or both scenario development
and analysis. This does not affect the actual production environment.
v The maximum number of allowed FlashCopy logical drives is one-half of the total logical drives that
are supported by your controller model.
For additional information about the FlashCopy feature and how to manage FlashCopy logical drives, see
the Storage Manager Subsystem Management window online help.
Important: The FlashCopy drive cannot be added or mapped to the same server that has the base
logical drive of the FlashCopy logical drive in a Windows 2000, Windows Server 2003, or NetWare
environment. You must map the FlashCopy logical drive to another server.
74
To create a FlashCopy logical drive, complete the following steps:

1. To make sure that you have the accurate point-in-time image of the base logical drive, stop
applications and flush cache I/O to the base logical drive.
2. Open the Subsystem Management window. From the Logical page, right-click the base logical drive.
3. Select Create FlashCopy Logical Drive. The Create FlashCopy Logical Drive wizard starts.
4. Follow the on-screen instructions.
5. See the Subsystem Management window online help for instructions for adding the FlashCopy logical
drive to the host.
Using VolumeCopy
The VolumeCopy feature is a firmware-based mechanism for replicating logical drive data within a
storage subsystem. This feature is designed as a system-management tool for tasks such as relocating
data to other drives for hardware upgrades or performance management, data backup, or restoring
snapshot logical drive data. Users submit VolumeCopy requests by specifying two compatible drives. One
drive is designated as the source and the other as the target. The VolumeCopy request is persistent so that
any relevant result of the copy process can be communicated to the user. For more information about this
feature, contact your IBM reseller or marketing representative.
Using the Remote Mirror option

The Remote Mirror option is a premium feature that is used for online, real-time replication of data
between storage subsystems in different locations. In the event of a disaster or unrecoverable error at one
storage subsystem, the Remote Mirror option enables you to designate a second storage subsystem to
handle normal I/O operations. For more information about this feature, see the IBM Remote Support
Manager for Storage - Planning, Installation and User's Guide, or contact your IBM reseller or marketing
representative.
Using Full Disk Encryption

Full Disk Encryption (FDE) is a premium feature that prevents unauthorized access to the data on a drive
that is physically removed from a storage subsystem. Controllers in the storage subsystem have a security
key. Secure drives provide access to data only through a controller that has the correct security key. FDE
is a premium feature of the storage management software and must be enabled by you or your storage
vendor.
Note: Not all DS storage subsystems support FDE. Check the announcement letter or the Installation,
User's, and Maintenance Guide for your storage subsystem to determine whether FDE is supported for
your storage subsystem.
The FDE premium feature requires security-capable drives. A security-capable drive encrypts data during
write operations and decrypts data during read operations. Each security-capable drive has a unique
drive-encryption key.
When you create a secure array from security-capable drives, the drives in that array become
security-enabled. When a security-capable drive has been security-enabled, the drive requires the correct
security key to read or write the data. A security-capable drive works the same as any other drive until it
is security-enabled.
For more information about how to configure and use FDE, see Chapter 6, Working with full disk
encryption, on page 143.
75
Using other features

This section describes other features that are available in Storage Manager.
Using controller cache memory

Write caching enables the controller cache memory to store write operations from the host computer and,
as a result, improves system performance. However, a controller can fail with user data in its cache that
has not been transferred to the logical drive. Also, the cache memory can fail while it contains unwritten
data. Write-cache mirroring protects the system from either of these possibilities. Write-cache mirroring
enables cached data to be mirrored across two redundant controllers with the same cache size. The data
that is written to the cache memory of one controller is also written to the cache memory of the other
controller. That is, if one controller fails, the other controller completes all outstanding write operations.
Note: You can enable the write-cache mirroring parameter for each logical drive, but when write-cache
mirroring is enabled, half of the total cache size in each controller is reserved for mirroring the cache data
from the other controller.
To prevent data loss or damage, the controller periodically writes cache data to the logical drive. When
the cache holds a specified start percentage of unwritten data, the controller writes the cache data to the
logical drive. When the cache is flushed down to a specified stop percentage, the flush is stopped. For
example, the default start setting for a logical drive is 80% of the total cache size, and the stop setting is
20%. With these settings, the controller starts flushing the cache data when the cache reaches 80% full and
stops flushing cache data when the cache is flushed down to 20% full.
For maximum data safety, you can choose low start and stop percentages, for example, a start setting of
25% and a stop setting of 0%. However, low start and stop settings increase the chance that data that is
needed for a host computer read will not be in the cache. If sufficient data is not in the cache, the
cache-hit percentage decreases, and subsequently, the I/O request rate decreases. It also increases the
number of disk writes that are necessary to maintain the cache level, increasing system overhead and
further decreasing performance.
If a power outage occurs, data in the cache that is not written to the logical drive might be lost, even if it
is mirrored to the cache memory of both controllers. There are backup batteries in the controller enclosure
that protect the cache against power outages.
Note: The controller backup battery CRU change interval is three years from the date that the backup
battery CRU was installed for all models of the following DS4000 Storage Subsystems only: DS4100,
DS4300, and DS4400. There is no replacement interval for the cache battery backup CRU in other DS4000
Storage Subsystems.
The Storage Manager software features a battery-age clock that you can set when you replace a battery.
This clock keeps track of the age of the battery (in days) so that you know when it is time to replace the
battery.
Note:
1. For the DS4100, and DS4300 or DS4300 Turbo disk systems, the battery CRU is inside each controller
CRU.
2. For the DS4800, DS5100, and DS5300, the batteries CRU are in the interconnect-batteries CRU. Write
caching is disabled when batteries are low or discharged. If you enable a parameter called
write-caching without batteries on a logical drive, write caching continues even when the batteries
in the controller enclosure are removed.
76
Attention: For maximum data integrity, do not enable the write-caching without batteries parameter,
because data in the cache is lost during a power outage if the controller enclosure does not have working
batteries. Instead, contact IBM service to get a battery replacement as soon as possible to minimize the
time that the storage subsystem is operating with write-caching disabled.
Using Persistent Reservations

Attention: Use the Persistent Reservations option only with guidance from an IBM technical-support
representative.
Use the Persistent Reservations option to view and clear logical drive reservations and associated
registrations. Persistent reservations are configured and managed through the cluster server software and
prevent other hosts from accessing particular logical drives.
Unlike other types of reservations, a persistent reservation is used to perform the following functions:
v Reserve access across multiple host ports and provide various levels of access control
v Query the storage subsystem about registered ports and reservations
v Provide for persistence of reservations in the event of a storage system power loss
You can use the Storage Manager software to manage persistent reservations in the Subsystem
Management window. You can use the Persistent Reservation option to perform the following tasks:
v View registration and reservation information for all logical drives in the storage subsystem
v Save detailed information about logical drive reservations and registrations
v Clear all registrations and reservations for a single logical drive or for all logical drives in the storage
subsystem
For detailed procedures, see the Subsystem Management window online help. You can also manage
persistent reservations through the script engine and the command-line interface. For more information,
see the Enterprise Management window online help.
Using Media Scan

A media scan is a background process that runs on all logical drives in the storage subsystem for which it
is enabled, providing error detection on the drive media. The Media Scan feature checks the physical
disks for defects by reading the raw data from the disk and, if there are errors, writing it back. The
advantage of enabling Media Scan is that the process can find media errors before they disrupt normal
logical-drive read and write functions. The media-scan process scans all logical-drive data to verify that it
is accessible.
Note: The background media-scan operation does not scan hot-spare drives or unused optimal hard
drives (those that are not part of a defined logical drive). To perform a media-scan operation on hot
spares or unused optimal hard drives, you must convert them to logical drives at certain scheduled
intervals and then revert them back to their hot-spare or unused states after you scan them.
There are two ways in which a media scan can run:
Logical drive redundancy checks not enabled
If background Media Scan is enabled with logical drive redundancy data checks not enabled, the
storage subsystem scans all blocks in the logical drives, including the redundancy blocks, but it
does not check for the accuracy of the redundancy data.
This is the default setting when you use Storage Manager to create logical drives.
Logical drive redundancy checks enabled
If background Media Scan is enabled with logical drive redundancy data checks enabled for
77
RAID-3, RAID-5, or RAID-6 logical drives, a redundancy data check scans the data blocks,
calculates the redundancy data, and compares it to the read redundancy information for each
block. It then repairs any redundancy errors, if required. For a RAID-1 logical drive, a
redundancy data check compares data blocks on mirrored drives and corrects any data
inconsistencies.
Do not use this setting on older DS storage subsystems such as the DS4500, DS4400, DS4300, or
DS4100; redundancy checking has a negative effect on storage subsystem performance.
For newer storage subsystems, such as the DS5100, DS5300, DS5020, or DS3950, this setting does
not cause performance degradation.
When it is enabled, the media scan runs on all of the logical drives in the storage subsystem that meet
the following conditions:
v The logical drive is in an optimal status.
v There are no modification operations in progress.
v The Media Scan parameter is enabled.
Note: Media Scan must be enabled for the entire storage subsystem and enabled on each logical drive
within the storage subsystem to protect the logical drive from failure due to media errors.
Media Scan reads only data stripes, unless there is a problem. When a block in the stripe cannot be read,
the read comment is retried a certain number times. If the read continues to fail, the controller calculates
what that block must be and issues a write-with-verify command on the stripe. As the disk attempts to
complete the write command, if the block cannot be written, the drive reallocates sectors until the data
can be written. Then the drive reports a successful write and Media Scan checks it with another read.
There must not be any additional problems with the stripe. If there are additional problems, the process
repeats until there is a successful write, or until the drive is failed because of many consecutive write
failures and a hot-spare drive takes over. Repairs are made only on successful writes, and the drives are
responsible for the repairs. The controller issues only write-with-verify commands. Therefore, data stripes
can be read repeatedly and report bad sectors, but the controller calculates the missing information with
RAID.
In a dual-controller storage subsystem, there are two controllers that handle I/O (Controllers A and B).
Each logical drive that you create has a preferred controller that normally handles I/O for it. If a
controller fails, the I/O for logical drives that is owned by the failed controller fails over to the other
controller. Media Scan I/O is not impacted by a controller failure, and scanning continues on all
applicable logical drives when there is only one remaining active controller.
If a drive is failed during the media-scan process because of errors, normal reconstruction tasks are
initiated in the controller operating system, and Media Scan attempts to rebuild the array using a
hot-spare drive. While this reconstruction process occurs, no more media-scan processing is done on that
array.
Note: Because additional I/O reads are generated for media scanning, there might be a performance
impact, depending on the following factors:
v The amount of configured storage capacity in the storage subsystem. The greater the amount of
configured storage capacity in the storage subsystem, the greater the performance impact.
v The configured scan duration for the media-scan operations. The longer the scan, the lower the
performance impact.
v The status of the redundancy check option (enabled or disabled). If redundancy check is enabled, the
performance impact is greater.
Errors reported by Media Scan

The media-scan process runs continuously in the background when it is enabled. Every time a media
scan of all logical drives in a storage subsystem is completed, it restarts immediately. The media-scan
78
process discovers any errors and reports them to the storage subsystem major event log (MEL). The
following table lists the errors that are discovered during a media scan.
Table 15. Errors discovered during a media scan
Error
Description
Result
Unrecovered media error
The drive could not read the data on its

first attempt or on any subsequent
attempts.
For logical drives or arrays with

redundancy protection (RAID-1,
RAID-3 and RAID-5), data is
reconstructed, rewritten to the drive,
and verified. The error is reported to
the event log.
For logical drives or arrays without
redundancy protection (RAID-0 and
degraded RAID-1, RAID-3, RAID-5, and
RAID-6 logical drives), the error is not
corrected but is reported to the event
log.
Recovered media error
The data is rewritten to the drive and

The drive could not read the requested
data on its first attempt but succeeded on verified. The error is reported to the
event log.
a subsequent attempt.
Note: Media scan makes three attempts to
read the bad blocks.
Redundancy mismatches
The first 10 redundancy mismatches

Redundancy errors are found.
Note: This error can occur only when the that are found on a logical drive are
optional redundancy check box is selected, reported to the event log.
when the Media Scan feature is enabled,
and the logical drive or array is not
RAID-0.
Unfixable error
The data could not be read, and parity or The error is reported to the event log.
redundancy information could not be used
to regenerate it. For example, redundancy
information cannot be used to reconstruct
data on a degraded logical drive.
Media Scan settings

To maximize the protection and minimize the I/O performance impact, the storage subsystem comes
from the manufacturer with the following default Media Scan settings:
v The Media Scan option is enabled for all logical drives in the storage subsystem. Therefore, every time
a logical drive is created, it is created with the Media Scan option enabled. If you want to disable
media scanning, you must disable it manually for each logical drive.
v The media-scan duration is set to 30 days. This is the time in which the storage subsystem controllers
must complete the media scan of a logical drive. The controller uses the media-scan duration, with the
information about which logical drives must be scanned, to determine a constant rate at which to
perform the media-scan activities. The media-scan duration is maintained regardless of host I/O
activity.
Thirty days is the maximum duration setting. You must manually change this value if you want to
scan the media more frequently. This setting is applied to all logical drives in the storage subsystem.
For example, you cannot set the media-scan duration for one logical drive at two days and the
duration for other logical drives at 30 days.
v By default, the redundancy check option is not enabled on controller firmware versions earlier than
7.60.39.00. For controller firmware versions earlier than 7.60.39.00, you must manually set this option
for each of the logical drives on which you want to have redundancy data checked.
79
For controller firmware version 7.60.39.00 and later, the redundancy check option is enabled as a
default setting for any newly created logical drives. If you want an existing logical drive that was
created before version 7.60.39.00 or later was installed to have the redundancy check option enabled,
you must enable the option manually.
Without redundancy check enabled, the controller reads the data stripe to confirm that all the data can
be read. If it reads all the data, it discards the data and moves to the next stripe. When it cannot read a
block of data, it reconstructs the data from the remaining blocks and the parity block and issues a
write with verify to the block that could not be read. If the block has no data errors, Media Scan takes
the updated information and verifies that the block was fixed. If the block cannot be rewritten, the
drive allocates another block to take the data. When the data is successfully written, the controller
verifies that the block is fixed and moves to the next stripe.
Note: With redundancy check, Media Scan goes through the same process as without redundancy
check, but, in addition, the parity block is recalculated and verified. If the parity has data errors, the
parity is rewritten. The recalculation and comparison of the parity data requires additional I/O, which
can affect performance.
Important: Changes to the Media Scan settings do not go into effect until the current media-scan cycle is
completed.
To change the Media Scan settings for an entire storage subsystem, complete the following steps:
1. Select the storage subsystem entry on the Logical or Physical tab of the Subsystem Management
window.
2. Click Storage Subsystem > Change > Media Scan Settings.
To change the Media Scan settings for a logical drive, complete the following steps:
1. Select the logical drive entry on the Logical or Physical tab of the Subsystem Management window.
2. Click Storage Subsystem > Change > Media Scan Settings.
Media Scan duration

When Media Scan is enabled, a duration window is specified (in days) which indicates how long the
storage subsystem will give the media-scan process to check all applicable logical drives. The duration
window can be shortened or increased to meet the customer requirements. The shorter the duration, the
more often a drive is scanned and consequently, the more robust the situation will be. However, the more
often a drive is scanned, the higher the performance impact.
Whenever the storage subsystem has some idle time, it starts or continues media scanning operations. If
application generated disk I/O work is received, it gets priority. Therefore, the media-scan process can
slow down, speed up, or in some cases be suspended as the work demands change. If a storage
subsystem receives a great deal of application-generated disk I/O, it is possible for the Media Scan to fall
behind in its scanning. As the storage subsystem gets closer to the end of the duration window during
which it must finish the media scan, the background application starts to increase in priority (i.e. more
time is dedicated to the media-scan process). This increase in priority only increases to a certain point
because the storage subsystem priority is process application-generated disk I/O. In this case, it is
possible that the media-scan duration will be longer than the media scan duration settings.
Note: If you change the media-scan duration setting, the changes will not take effect until the current
media-scan cycle completes or the controller is reset.
Tuning storage subsystems

The information in this section describes Performance Monitor data and the tuning options that are
available in the Storage Manager to optimize storage subsystem and application performance. Use the
Subsystem Management window Performance Monitor to monitor storage subsystem performance in real
time and to save performance data to a file for later analysis. You can specify the logical drives and
80
controllers to monitor and the polling interval. You can also receive storage subsystem totals, which is
data that combines the statistics for both controllers in an active-active controller pair.
Table 16. Performance Monitor tuning options in the Subsystem Management window
Data field
Description
Total I/Os
Total I/Os that have been performed by this device since the beginning of the
polling session.
Read percentage
The percentage of total I/Os that are read operations for this device. Write
percentage is calculated as 100 minus this value.
Cache-hit percentage
The percentage of read operations that are processed with data from the cache,
rather than requiring a read from the logical drive.
Current KB per second
During the polling interval, the transfer rate is the amount of data, in KB, that is
moved through the Fibre Channel I/O path in 1 second (also called throughput).
Maximum KB per second
The maximum transfer rate that is achieved during the Performance Monitor
polling session.
Current I/O per second
The average number of I/O requests that are serviced per second during the
current polling interval (also called an I/O request rate).
Maximum I/O per second
The maximum number of I/O requests that are serviced during a 1-second
interval over the entire polling session.
Maximizing throughput with load balancing

Load balancing is the redistribution of read or write requests to maximize throughput between the server
and the storage subsystem. Load balancing is very important in high-workload settings or other settings
where consistent service levels are critical. The multipath driver balances I/O workload transparently,
without administrator intervention. Without multipath software, a server that sends I/O requests down
several paths might operate with heavy workloads on some paths while other paths are not used
efficiently.
The multipath driver determines which paths to a device are in an active state and can be used for load
balancing. The load balancing policy uses one of three algorithms: round robin, least queue depth, or least
path weight. Multiple options for setting the load balance policies enable you to optimize I/O performance
when mixed-host interfaces are configured. The load balancing policies that you can choose depend on
your operating system. Load balancing is performed on multiple paths to the same controller, but not
across both controllers.
Table 17. Load balancing policies supported by operating systems
Operating system
Multi-path driver
Load balancing policy
AIX
MPIO
Round robin, selectable path priority
Red Hat Enterprise Linux 4 Update

7
RDAC
Round robin, least queue depth
Solaris
MPxIO
Round robin
SUSE Linux Enterprise 9 Service

Pack 4
RDAC
Round robin, least queue depth
Windows
MPIO
Round robin, least queue depth, least path

weight
Round robin with subset

The round robin with subset I/O load balance policy routes I/O requests, in rotation, to each available
data path to the controller that owns the logical drives. This policy treats all paths to the controller that
owns the logical drive equally for I/O activity. Paths to the secondary controller are ignored until
81
ownership changes. The basic assumption for the round robin policy is that the data paths are equal.
With mixed host support, the data paths might have different bandwidths or different data transfer
speeds.
Least queue depth with subset

The least queue depth with subset policy is also known as the least I/Os or least requests policy. This
policy routes the next I/O request to a data path that has the fewest queued outstanding I/O requests.
For this policy, an I/O request is simply a command in the queue. The type of command or the number
of blocks that are associated with the command are not considered. The least queue depth with subset
policy treats large block requests and small block requests equally. The selected data path is one of the
paths in the path group of the controller that owns the logical drive.
Least path weight with subset

The least path weight with subset policy assigns a weight factor to each data path to a logical drive. An
I/O request is routed to the path with the lowest weight value to the controller that owns the logical
drive. If more than one data path to the logical drive has the same weight value, the round-robin with
subset path selection policy is used to route I/ O requests between the paths with the same weight value.
Balancing the Fibre Channel I/O load

The Total I/O data field in the Subsystem Management window is used for monitoring the Fibre Channel
I/O activity to a specific controller and a specific logical drive. This field helps you to identify possible
I/O hot spots.
You can identify Fibre Channel I/O patterns to the individual logical drives and compare those with the
expectations according to the application. If a controller has more I/O activity than expected, click Array
> Change Ownership to move an array to the other controller in the storage subsystem.
It is difficult to balance Fibre Channel I/O loads across controllers and logical drives because I/O loads
are constantly changing. The logical drives and the data that is accessed during the polling session
depend on which applications and users are active during that time period. It is important to monitor
performance during different time periods and gather data at regular intervals to identify performance
trends. The Performance Monitor enables you to save data to a comma-delimited text file that you can
import to a spreadsheet for further analysis.
If you notice that the workload across the storage subsystem (total Fibre Channel I/O statistic) continues
to increase over time while application performance decreases, you might have to add storage
subsystems to the enterprise.
Optimizing the I/O transfer rate

The transfer rates of the controller are determined by the application I/O size and the I/O request rate. A
small application I/O request size results in a lower transfer rate but provides a faster I/O request rate
and a shorter response time. With larger application I/O request sizes, higher throughput rates are
possible. Understanding the application I/O patterns will help you optimize the maximum I/O transfer
rates that are possible for a given storage subsystem.
One of the ways to improve the I/O transfer rate is to improve the I/O request rate. Use the
host-computer operating system utilities to gather data about I/O size to understand the maximum
possible transfer rates. Then, use the tuning options that are available in the Storage Manager to optimize
the I/O request rate to reach the maximum possible transfer rate.
82
Optimizing the I/O request rate

The I/O request rate can be affected by the following factors:
v The I/O access pattern (random or sequential) and I/O size
v The status of write-caching (enabled or disabled)
v The cache-hit percentage
v
v
v
v
v
The
The
The
The
The
RAID level
logical-drive modification priority
segment size
number of logical drives in the arrays or storage subsystem
fragmentation of files
Note: Fragmentation affects logical drives with sequential I/O access patterns, not random I/O access
patterns.
Determining the I/O access pattern and I/O size

To determine whether the I/O access has sequential characteristics, enable a conservative cache
read-ahead multiplier (for example, 4) by clicking Logical Drive > Properties. Then, examine the logical
drive cache-hit percentage to see whether it has improved. An improvement indicates that the I/O has a
sequential pattern. Use the host-computer operating-system utilities to determine the typical I/O size for
a logical drive.
Enabling write-caching
Higher I/O write rates occur when write-caching is enabled, especially for sequential I/O access patterns.
Regardless of the I/O access pattern, be sure to enable write-caching to maximize the I/O rate and
shorten the application response time.
Optimizing the cache-hit percentage

A higher cache-hit percentage is preferred for optimal application performance and is positively
correlated with the Fibre Channel I/O request rate.
If the cache-hit percentage of all logical drives is low or trending downward and less than the maximum
amount of controller cache memory is installed, you might have to install more memory.
If an individual logical drive has a low cache-hit percentage, you can enable cache read-ahead for that
logical drive. Cache read-ahead can increase the cache-hit percentage for a sequential I/O workload. If
cache read-ahead is enabled, the cache fetches more data, usually from adjacent data blocks on the drive.
In addition to the requested data, this feature increases the chance that a future request for data is
fulfilled from the cache, rather than requiring a logical drive access.
The cache read-ahead multiplier values specify the multiplier to use for determining how many
additional data blocks are read into the cache. Choosing a higher cache read-ahead multiplier can
increase the cache-hit percentage.
If you determine that the Fibre Channel I/O access pattern has sequential characteristics, set an
aggressive cache read-ahead multiplier (for example, 8). Then examine the logical-drive cache-hit
percentage to see whether it has improved. Continue to customize logical-drive cache read-ahead to
arrive at the optimal multiplier (for a random I/O pattern, the optimal multiplier is 0).
Choosing appropriate RAID levels

Use the read percentage for a logical drive to determine the application behavior. Applications with a
high read percentage perform well with RAID-5 logical drives because of the outstanding read
performance of the RAID-5 configuration.
Note: This is applicable for traditional array only.
83
Applications with a low read percentage (write-intensive) do not perform as well on RAID-5 logical
drives because of the way that a controller writes data and redundancy data to the drives in a RAID-5
logical drive. If there is a low percentage of read activity relative to write activity, you can change the
RAID level of a logical drive from RAID-5 to RAID-1 for faster performance.
Choosing an optimal logical-drive modification priority setting

The modification priority defines how much processing time is allocated for logical-drive modification
operations versus system performance. The higher the priority, the faster the logical-drive modification
operations are completed, but the more slowly the system I/O access pattern is serviced.
Logical-drive modification operations include reconstruction, copyback, initialization, media scan,
defragmentation, change of RAID level, and change of segment size. The modification priority is set for
each logical drive, using a slider bar from the Logical Drive - Properties window. There are five relative
settings on the reconstruction rate slider bar, ranging from Low to Highest. The actual speed of each
setting is determined by the controller. Choose the Low setting to maximize the Fibre Channel I/O
request rate. If the controller is idle (not servicing any I/O request rates) it ignores the individual
logical-drive rate settings and processes logical-drive modification operations as fast as possible.
Choosing an optimal segment size for an array

A segment is the amount of data, in KB, that the controller writes on a single logical drive before it writes
data on the next drive. A data block is 512 bytes of data and is the smallest unit of storage. The size of a
segment determines how many data blocks it contains. For example, an 8 KB segment holds 16 data
blocks, and a 64 KB segment holds 128 data blocks.
Important: In Storage Manager version 7.01 and 7.02, the segment size is expressed in the number of
data blocks. The segment size in the Storage Manager is expressed in KB.
When you create a logical drive, the default segment size is a good choice for the expected logical-drive
usage. To change the default segment size, click Logical Drive > Change Segment Size.
If the I/O size is larger than the segment size, increase the segment size to minimize the number of
drives that are needed to satisfy an I/O request. This technique helps even more if you have random I/O
access patterns. If you use a single logical drive for a single request, it leaves other logical drives
available to simultaneously service other requests.
When you use the logical drive in a single-user, large I/O environment such as a multimedia application,
storage performance is optimized when a single I/O request is serviced with a single array data stripe
(which is the segment size multiplied by the number of logical drives in the array that are used for I/O
requests). In this case, multiple logical drives are used for the same request, but each logical drive is
accessed only once.
Defragmenting files to minimize disk access

Each time that you access a drive to read or write a file, it results in the movement of the read/write
heads. Verify that the files on the logical drive are defragmented. When the files are defragmented, the
data blocks that make up the files are next to each other, preventing extra read or write head movement
when files are retrieved. Fragmented files decrease the performance of a logical drive with sequential I/O
access patterns.
Using the Storage Manager command-line interface and Script Editor

This section describes the Storage Manager command-line interface and the Script Editor.
84
Storage Manager command-line interface

Attention: The command-line interface (CLI) does not have any mechanisms to prevent you from
inadvertently making unwanted changes to the storage subsystem. The script commands are capable of
damaging a configuration and causing loss of data access if not used correctly. To avoid damaging effects
to your storage configuration or data, use the Storage Manager client graphical user interface (GUI) to
manage your storage subsystem configurations.
The command-line interface is a software tool that enables you to configure and monitor storage
subsystems using script commands. Using the CLI, you can run commands from an operating-system
prompt, such as the Windows command prompt, a Linux operating-system console, or a Solaris
operating-system console. You must install the IBM DS Storage Manager client to run the script
commands either through the script window, which is invoked from the IBM DS Storage Manager client
Enterprise window, or through the command-line interface using the SMcli program. The script command
engine is automatically installed as part of the IBM DS Storage Manager client installation.
Each command performs a specific action that manages a storage subsystem or returns information about
the status of a storage subsystem. You can enter individual commands, or you can run script files when
you need to perform operations more than once. For example, you can run script files when you want to
install the same configuration on several storage subsystems. With the CLI, you can load a script file from
a disk and run the script file. The CLI provides a way to run storage management commands on more
than one network storage subsystem. You can use the CLI both in installation sites and in development
environments.
For more information about the Storage Manager CLI, see the IBM System Storage DS3000, DS4000, and
DS5000 Command Line Interface and Script Commands Programming Guide.
Using the Script Editor

Instead of using the graphical user interface to perform storage subsystem management functions, a
Script Editor window is provided for running scripted management commands. If the controller firmware
version is 5.4x.xx.xx or earlier, some of the management functions in the graphical user interface are not
available through script commands. Storage Manager 10.xx, in conjunction with controller firmware
version 07.xx.xx.xx and later, provides full support of all management functions through SMcli
commands.
85
ds50_001138
Figure 17. The Script Editor window
Important: Use caution when you run the commands; the Script Editor does not prompt you for
confirmation of operations that are destructive, such as the Delete arrays and Reset Storage Subsystem
configuration commands.
Not all script commands are implemented in all versions of the controller firmware. The earlier the
firmware version, the smaller the set of available script commands. For more information about script
commands and firmware versions, see the Storage Manager Enterprise Management window.
For a list of available commands and their syntax, see the online Command Reference help.
To
1.
2.
3.
open the Script Editor, complete the following steps:

Select a storage subsystem in either the tree view or the table view of the Device tab.
Click Tools > Execute Script.
The Script Editor opens. The Script view and the Output view are presented in the window. A splitter
bar divides the window between the Script view and the Output view. Drag the splitter bar to resize
the views.
In the Script view, you can input and edit script commands. The Output view displays the results of the
operations. The Script view supports the following editing key strokes:
Ctrl+A
Selects everything in the window
Ctrl+C
Copies the marked text in the window into a Windows clipboard buffer
86
Ctrl+V
Pastes the text from the Windows clipboard buffer into the window
Ctrl+X Deletes (cuts) the marked text in the window
Ctrl+Home
Moves the cursor to the top of the script window
Ctrl+End
Moves the cursor to the bottom of the script window
The following list shows general guidelines for using the Script Editor:
v All statements must end with a semicolon (;).
v Each command and its associated primary and secondary parameters must be separated by a space.
v The Script Editor is not case-sensitive.
v Each new statement must begin on a separate line.
v Comments can be added to your scripts to make it easier for you and other users to understand the
purpose of the command statements.
The Script Editor supports the two following comment formats:
v Text contained after two forward slashes (//) until an end-of-line character is reached
For example:
//The following command assigns hot spare drives.
set drives [1,2 1,3] hotspare=true;
The comment //The following command assigns hot spare drives. is included for clarification and is
not processed by the Script Editor.
Important: You must end a comment that begins with // with an end-of-line character, which you
insert by pressing the Enter key. If the script engine does not find an end-of-line character in the script
after processing a comment, an error message displays and the script fails.
v Text contained between the /* and */ characters
For example:
/* The following command assigns hot spare drives.*/
set drives [1,2 1,3] hotspare=true;
The comment /*The following command assigns hot spare drives.*/ is included for clarification and
is not processed by the Script Editor.
Important: The comment must start with /* and end with */. If the script engine does not find both a
beginning and ending comment notation, an error message displays and the script fails.
87
88
Chapter 5. Configuring hosts

After you configure the storage subsystem or subsystems, use the information in this chapter to enable all
hosts to connect to the storage subsystems. This chapter consists of the following sections:
v Booting a host operating system using SAN boot
v Using multipath drivers to automatically manage logical drive fail-over and fail-back on page 91
v Identifying devices on page 120
v Configuring devices on page 123
Booting a host operating system using SAN boot

SAN boot is the ability to boot the host operating system from a Storage Area Network (SAN) device. In
this case, the device is a LUN from a DS3000, DS4000, or DS5000 storage subsystem. SAN boot is also
referred to as remote boot, where the boot LUN is in the storage subsystem instead of inside the server
enclosure and the server is not connected to the storage subsystem in a SAN. Rather, the connections
might be direct connections, SAS-switch connections, or iSCSI connections.
Advantages of using SAN boot include the following:
Server consolidation
Each server can boot from an image of the operating system on the SAN.
Simplified recovery from server failures
Operating-system reinstallation is not required.
Rapid disaster recovery
The storage subsystem can be replicated at a remote recovery site.
The following conditions are required for SAN boot:
v SAN configuration, zoning of boot devices, multipath configurations (if applicable)
v Single active path to boot LUN. During the installation process, only one path to the boot LUN must
be enabled before you install and enable a multipath driver.
v HBA BIOS; selectable boot, or boot BIOS, must be enabled.
To configure a storage subsystem for SAN boot, use the following guidelines:
1. Create a SAN configuration:
a. Create SAN zoning; arrange the Fibre Channel devices into logical groups over the physical
configuration of the fabric. Each device in a SAN might be placed into multiple zones.
b. Remove all paths from the server HBA ports except for one, to the boot LUN. To do this, disable
the port on the switch for the other physical paths.
2. Configure the storage subsystem:
a. Create the LUN.
b. Map the LUN to the host as LUN 0.
Note: You must know the HBA WWNN, which you can get from the HBA label.
3. Configure the HBAs for boot from SAN:
a. Verify that boot BIOS is enabled on the HBA device configured for the host.
b. When the host is starting, enter the boot BIOs for your HBA device.
89
c. Select the HBA that you want to use for SAN booting and configure the BIOS so that the boot
LUN is designated as the preferred boot device. After the storage subsystem has discovered the
HBA WWPNs, you must configure them as the HBAs to the boot LUN, using the host-mapping
procedures.
Note:
1) The HBA must be logged in to the storage subsystem. Even though no LUN will be available
yet, you can use the BIOS to discover the storage subsystem.
2) For more information, see the documentation that came with your HBA.
d. Save the changes, exit BIOS, and restart the server. The BIOS can now be used to discover the
newly configured LUN.
4. Start the installation by booting from the installation media:
a. During the installation, your operating-system media asks which drive (or LUN) you want to
perform the installation. Select the drive that corresponds to your storage subsystem device.
Note: If you are prompted during the installation for third-party device drivers, select the HBA
driver that you have available on another form of media.
b. Choose the default option for disk partitioning.
Note: Make sure that the LUN you choose is large enough for the operating system. For Linux,
and most other operating systems, 20 GB is enough for the boot device. For swap partitions, make
sure that the size is at least the size of your server physical memory.
5. Complete the installation and finish the SAN boot procedure:
a. Restart the server again, and open the boot options menu. The boot device that you set up is
ready to be used.
b. Select the option to boot from a hard disk drive/SAN, and select the HBA that is associated with
the SAN disk device on which the installation was completed. The installation boot device is now
listed in the bootable devices that are discovered on the selected HBA.
c. Select the applicable device, and boot.
d. Set the installed boot device as the default boot device for the system.
Note: This step is not required. However, the installed boot device must be the default boot
device to enable unattended reboots after this procedure is complete.
e. Linux only To complete the installation on Linux, complete the following steps:
1) Verify that the persistent binding for /var/mpp/devicemapping is up-to-date. The
/var/mpp/devicemapping file tells RDAC which storage subsystem to configure first. If
additional storage subsystems will be added to the server, the storage subsystem with the
boot/root volume must always be first in the device mapping file. To update this file, execute
the following command:
# mppUpdate
2) After you run the # mppUpdate command, cat the /var/mpp/devicemapping file with the
following command:
# cat /var/mpp/devicemapping 0:<DS4x00 SAN Boot Device>
The storage subsystem for the boot/root volume must be at entry 0. If the boot/root volume is
not at entry 0, edit the file to reorder the storage subsystem entries so that the array for the
boot/root volume is at entry 0.
3) Execute the # mppUpdate command. The installation is now complete.
Additional paths between the storage subsystem and server can now be added. If the server is going to
be used to manage the storage subsystem, the Storage Manager can now be installed on the server.
90
For additional information about using multipath drivers, see Using multipath drivers to automatically
manage logical drive fail-over and fail-back.
Using multipath drivers to automatically manage logical drive fail-over

and fail-back
Host systems that are attached to the DS3000, DS4000, or DS5000 storage subsystem for I/O activity
require a multipath driver (sometimes referred to as an RDAC or failover driver) for Fibre Channel path
redundancy. The multipath driver monitors I/O paths. If a component failure occurs in one of the Fibre
Channel paths, the multipath driver reroutes all I/O to a different path. Your multipath driver depends
on the operating system that you have installed.
In the Microsoft Windows environment another multipath driver, referred to as Windows RDAC, was
previously provided with Storage Manager host software version 9 and earlier. Support for Windows
RDAC was terminated with the release of Storage Manager host software version 10, and later in
conjunction with controller firmware version 7.xx.xx.xx and later. In addition, support for AIX fcp_array
is being phased out. AIX fcp_array users must migrate to the AIX MPIO multipath driver at the earliest
time window.
An IBM Fibre Channel host bus adapter (HBA) provides the interface between a host server and a
storage subsystem. Storage subsystem Fibre Channel HBAs are high-performance, direct-memory access,
bus-master host adapters that are designed for high-end systems. These HBAs support all Fibre Channel
peripheral devices that support private-loop, direct-attach, and fabric-loop attachment. The IBM Host
Adapter device driver enables your operating system to communicate with the Fibre Channel HBA.
Table 16 lists the multipath driver or drivers that are supported for different operating systems. Refer to
the SSIC to determine which multipath driver is supported for a certain OS version for a particular
storage subsystem model.
Table 18. Multipath driver by operating system
Operating system
Multipath driver
AIX
fcp_array (also called RDAC), MPIO, or SDDPCM
HP-UX
LVM , native multipathing, or IBM SDD
Linux
MPP (also called Linux RDAC or RDAC), Veritas DMP, or native

(in-distro) Linux Device Mapper Multipath (DM-Multipath)
Mac OS
Provided by the HBA manufacturer
NetWare
Novell MPE
Solaris
RDAC, MPxIO or Veritas DMP
SVC
SDD
VMware
NMP
Windows
MPIO DSM or Veritas DMP DSM
With the exception of Windows MPIO, multipath driver files are not included on the Storage Manager
DVD. Check the SSIC and the Storage Manager readme file for the minimum file set versions that are
required for your operating system. To learn how to find the readme files on the web, see Finding
Storage Manager software, controller firmware, and readme files on page xiii. To install the multipath
driver, follow the instructions in Installing a multipath driver on page 95.
Multipathing refers to the ability of the host to recognize multiple paths to the storage device. This is
done by using multiple HBA ports or devices within the host server that are connected to SAN fabric
switches, which are also connected to the multiple ports on the storage devices. For the storage products
91
that are referred to as DS3000, DS4000, or DS5000, these devices have two controllers within the storage
subsystem that manage and control the disk drives. These controllers behave in either active or passive
fashion. Ownership and control of a particular LUN is done by one controller. The other controller is in a
passive mode until a failure occurs, at which time the LUN ownership is transferred to that controller.
Each controller might have more than one fabric port for connectivity to the SAN fabric.
Figure 18 shows a sample multipath configuration for all supported operating systems except AIX
fcp_array and Solaris RDAC multipath configurations. Figure 19 on page 93 shows a sample multipath
configuration for the AIX fcp_array, Microsoft Windows RDAC (no longer supported), and Solaris RDAC
multipath configurations.
Server 1
HBA 1
Server 2
HBA 2
HBA 1
HBA 2
FC Switch
FC Switch
Controller A
Controller B
Storage subsystem
See Disk drives supported by IBM System Storage DS Storage Manager on page 50 for more information.
Figure 18. Host HBA to storage subsystem controller multipath sample configuration for all multipath drivers except
AIX fcp_array and Solaris RDAC
92
Server 1
HBA 1
Server 2
HBA 2
HBA 1
HBA 2
FC Switch
FC Switch
Controller A
Controller B
Storage subsystem
Figure 19. Host HBA to storage subsystem controller multipath sample configuration for AIX fcp_array and Solaris
RDAC multipath drivers
Most multipath drivers can support multiple paths. Table 19 shows the number of paths each driver can
support. Note that the AIX fcp_array and Solaris RDAC can support only two paths, one to each
controller.
Table 19. Number of paths each multipath driver supports by operating system
Driver
Number of paths
Default
AIX MPIO
Unlimited
Not applicable
AIX RDAC
Not applicable
HP-UX native
65,536
Not applicable
HP-UX PVlinks
8,192
Not applicable
Linux MPP
Unlimited
Linux Veritas DMP
Unlimited
Not applicable
Mac OS
Unlimited
Not applicable
Solaris MPxIO
Unlimited
Not applicable
Solaris RDAC
Not applicable
Solaris Veritas DMP
Unlimited
Not applicable
SVC
32
Not applicable
VMware
Unlimited - 8 or fewer for best performance
Not applicable
Windows MPIO DSM
32 paths per LUN, 16 per controller
Windows Veritas DMP DSM
Unlimited
Not applicable
Using host bus adapters

This section provides a basic overview of host bus adapters (HBAs), as well as instructions for connecting
HBAs in a Fibre Channel switch environment.
93
Understanding host bus adapters

Host bus adapters (HBAs) are used to connect servers to Fibre Channel topologies. The function of an
HBA is similar to that of network adapters used to access LAN resources. The device driver for an HBA
is typically responsible for providing support for a Fibre Channel topology, whether point-to-point, loop,
or fabric. The DS3000, DS4000, and DS5000 storage subsystems support the Fibre Channel (FC), Serial
Attached SCSI (SAS), Fibre Channel over Ethernet (FCoE) and iSCSI host bus adapters (HBAs) to connect
the host servers to the storage subsystems. These storage subsystems also support iSCSI via the regular
Ethernet NIC adapters. However, all HBAs are not supported on DS3000, DS4000, and DS5000 storage
subsystems. For detailed HBA support information, go to http://www.ibm.com/systems/support/
storage/config/ssic.
See documentation for information about HBA settings that can be customized for a certain
operating-system environment. This documentation also includes instructions about how to change these
settings. Caution should be made in changing these settings because an incorrect setting can cause
degradation in performance or intermittent failures. Also see the readme file that is included in the host
bus adapter BIOS, firmware, or device driver package for any up-to-date changes to the settings. The
tables in Appendix A, Host bus adapter settings, on page 231 show the required values of selected
settings for various HBA vendors.
Connecting HBAs in a Fibre Channel switch environment

There are two primary zoning schemes you can use when you connect Fibre Channel host bus adapters
(HBAs) in host servers to storage subsystem host ports in a Fibre Channel switch environment. In a
one-to-one zoning scheme, each HBA port is zoned to one controller host port. In a one-to-two zoning
scheme, each HBA port is zoned to two controller host ports.
As a general rule, the HBA and the storage subsystem host port connections must be zoned to minimize
the possible interactions between the ports in a SAN fabric environment. A one-to-one zoning scheme,
though not required, minimizes interactions because it connects one HBA port to just one server host
port. However, the zoning scheme you choose depends on your host-storage SAN fabric topology and
the capabilities of your Fibre Channel switches.
Depending on your host-storage SAN fabric topology Fibre Channel switch capabilities, you can
implement one of the two following zoning schemes in Figure 20 on page 95 and Figure 21 on page 95.
Note: For more information about zoning best practices and requirements, see the Fibre Channel Switch
Hardware Reference Guide or other documentation that came with the Fibre Channel switch. For links to
switch documentation on the IBM website, go to
www.ibm.com/servers/storage/support/san/index.html
94
In this zoning scheme (denoted by the translucent bar), one HBA port is zoned to one controller host port.
Server
HBA 1
HBA 2
FC Switch
FC Switch
C1
(Controller 1)
C2
(Controller 2)
Storage subsystem
Figure 20. One-to-one zoning scheme
In this zoning scheme (denoted by the translucent bars), one HBA port is zoned to two controller host ports.
Server
HBA 1
HBA 2
FC Switch
FC Switch
C1
(Controller 1)
C2
(Controller 2)
Storage subsystem
Figure 21. One-to-two zoning scheme
Installing a multipath driver

You must install a multipath driver on all hosts that are attached to your storage subsystem, regardless
whether these hosts will have multiple paths to the storage subsystem. This section describes various
multipath drivers, how to check the current multipath driver program driver version level, how to
update the multipath device driver, and how to verify that the multipath update is complete.
95
Windows MPIO or MPIO/DSM multipath driver

Overview
This multipath driver is included in the Storage Manager host software package for Windows. MPIO is a
DDK kit from Microsoft for developing code that manages multipath devices. The DDK kit contains a
core set of binary drivers that are installed with the storage subsystem Device Specific Module (DSM); the
drivers are designed to provide a transparent system architecture that relies on Microsoft Plug and Play.
These binary drivers provide LUN multipath functionality and maintain compatibility with existing
Microsoft Windows device driver stacks simultaneously. For Windows Server 2003, the MPIO is installed
with the MPIO DSM. In Windows Server 2008, only the MPIO DSM is installed because Windows 2008
comes with MPIO installed.
The MPIO driver performs the following tasks:
v Detects and claims the physical disk devices that are presented by the storage subsystems (according to
Vendor or Product ID strings) and manages the logical paths to the physical devices
v Presents a single instance of each LUN to the rest of the Windows operating system
v Provides an optional interface through WMI for use by user-mode applications
v Relies on the vendor (IBM) customized Device-Specific Module (DSM) for the following information
about storage subsystem behavior:
I/O routing information
Conditions that require a request to be retried, failed, failed over, or fail back; for example,
Vendor-Unique errors
Miscellaneous functions such as Release or Reservation commands
Multiple DSMs for different disk storage subsystems can be installed in the same host server as long as
they do not claim the same disk device.
Storport Miniport HBA device driver

For Windows operating systems, the Storage Manager provides the MPIO DSM device driver that is
based on the Microsoft Storport Miniport device driver model.
The Storport Miniport device driver model was introduced in the Microsoft Windows Server 2003 release
as a replacement for the SCSIport Miniport device driver model. It is the only supported device driver
model for Windows Server 2003 and Windows Server 2008 editions, supporting the AMD64 and EM64T
servers. It does not support the buschange=0 parameter to bypass the Microsoft Windows operating
system Plug and Play driver. Instead, it works with the Plug and Play driver to detect the removal and
insertion of devices at the Fibre Channel host bus adapter port.
Only the DS4100, DS4200, DS4300 (standard or turbo models), DS4400, DS4500, DS4700, and DS4800
storage subsystems support this Storport-based device driver. The DS4100, DS4300 (standard or turbo
models), DS4400, and DS4500 storage subsystem models must have controller firmware version 6.12.27.xx
or later.
See the Storage Manager readme file for Microsoft Windows operating systems for any other additional
requirements, such as controller firmware versions or updates.
SCSIport Miniport HBA device driver

For the Windows 2000 operating-system environment, only the device drivers based on the SCSIport
Miniport device driver (not the Storport model) are supported.
In previous SCSIport device driver releases, the buschange=0 parameter allows the RDAC multipath
driver to control and monitor device insertion and removal from the HBA port by preventing the
Microsoft Plug and Play device drive from managing the HBA port. This new SCSIport device driver
version that is used with MPIO does not support the buschange=0 parameter.
96
Important: Not all DS4000 and DS5000 controller firmware versions support this functionality. Only
DS4000 and DS5000 controller firmware versions 06.12.27.xx (and later) for DS4300 standard or turbo
models, and DS4500 storage subsystems or versions 6.16.8x.xx (and later) for DS4200, DS4700, and
DS4800 storage subsystems support the SCSIport Miniport device driver.
Before you install the device driver, check the readme file that is included in the device driver package
file, as well as the readme file included with the Storage Manager host software for Windows, to see
which device drivers and controller firmware versions are supported for DS3000, DS4000, or DS5000
storage subsystems. See Finding Storage Manager software, controller firmware, and readme files on
page xiii to learn how to access the most recent Storage Manager readme files on the web. Follow the
readme device driver installation instructions that are associated with your operating system.
Note: Read the device driver readme file for any required modifications to the default HBA BIOS and
host operating system registry settings to provide optimal performance. If you make any changes to the
HBA BIOS settings, the server must be rebooted for the changes to be enabled.
For more information, see the documentation that came with your Fibre Channel HBA.
Veritas DMP DSM driver

See the Symantec Storage Foundation for Windows documentation for instructions for installing the
Veritas DMP DSM driver at http://www.symantec.com/business/support/.
AIX multipath drivers

An AIX host system requires either the AIX Redundant Disk Array Controller (RDAC) or the MPIO
failover driver for Fibre Channel path redundancy. In supported Veritas environments, RDAC is the
supported failover driver.
The failover driver monitors I/O paths. If a component failure occurs in one of the Fibre Channel paths,
the failover driver reroutes all I/O to another path.
Note: AIX supports both Redundant Disk Array Controller (RDAC) and Multiple Path I/O. These
multipath drivers are part of the native AIX operating system. See the AIX documentation for details
about the installation of these drivers.
Linux Device Mapper Multipath driver

The Device Mapper Multipath (DMMP or DM-MP) is a generic framework for block devices provided by
the Linux operating system. It supports concatenation, striping, snapshots, mirroring, and multipathing.
The multipath function is a combination of the kernel modules and user space tools.
Important: The host on which the Linux Device Mapper multipath driver is installed should be either
Linux non-AVT/non-ADT (Linux) or LinuxCluster (LNXCLUSTER). You can verify the ADT or AVT
status in the host type information in the storage subsystem profile. The ADT or AVT status of the host,
on which the Linux Device Mapper multipath driver is installed, should be disabled.
The device mapper multipath driver:
v Provides a single block device node for a multipathed logical unit
v Ensures that I/O is re-routed to available paths in case of a path failure
v Ensures that the failed paths are revalidated as soon as possible
v
v
v
v
v
Configures multipaths to maximize performance

Reconfigures multipaths automatically when events occur
Provides DMMP features support to a newly added logical unit
Provides device name persistence for DMMP devices under /dev/mapper/
Configures multipaths automatically at an early stage of rebooting so that the OS can be installed and
rebooted on a multipathed logical unit
97
Device mapper multipath (DMMP or DM-MP) is supported on SLES11, SLES11 SP1, RHEL 6.0, RHEL 6.1
or their later versions.
Installing the Device Mapper MultiPath driver

Device mapper multipath (DMMP or DM-MP) is supported on SLES11, SLES11 SP1, RHEL 6.0, RHEL 6.1
or their later versions.
Refer to http://www.ibm.com/systems/support/storage/config/ssic for information on the
DS3000/DS5000 subsystems and controller firmware versions that are supported with DMMP.
Installing the Device Mapper MultiPath on SLES11 base

SLES 11 base operating system does not have all the packages to support device mapper for IBM DS
Storage subsystems. It is recommended that you use the most recent versions of the following
components, if available. Else, you must have at least the following component versions:
Table 20. Minimum version required for each component
Component
Minimum version
Download location
Kernel
kernel-default-2.6.27.29-0.1.1
http://download.novell.com/patch/
finder
scsi_dh_rdac driver
lsi-scsi_dh_rdac-kmp-default0.0_2.6.27.19_5-1
http://drivers.suse.com/driverprocess/pub/update/LSI/sle11/
common/x86_64/
Device Mapper library
device-mapper-1.02.27-8.6
finder
Kpartx
kpartx-0.4.8-40.6.1
finder
Multipath_tools
multipath-tools-0.4.8-40.6.1
finder
Ensure that you install all the dependent packages before continuing further. For more details, refer to the
SUSE Linux Enterprise Server 11 Installation and Administration Guide in Novel/SuSe website.
Complete the following steps to install device mapper multipath on SLES11 base:
1. Use the media supplied with the operating system vendor to complete the installation of SLES 11.
2. Download and install the errata kernel 2.6.27.29-0.1.
3. Reboot to the 2.6.27.29-0.1 kernel.
4.
5.
6.
7.
Install device-mapper-1.02.27-8.6.
Install kpartx-tools-0.4.8-40.6.1.
Install multipath-tools-0.4.8-40.6.1.
Update and configure /etc/multipath.conf. A sample file is stored at /usr/share/doc/packages/
multipath-tools/multipath.conf.synthetic. Copy and rename this file to /etc/multipath.conf.
Refer to Working with Multipath.conf file on page 99 for more details.
8. Enable multipathd service using the following command: #chkconfig multipathd on.
9. Edit the /etc/sysconfig/kernel file to add scsi_dh_rdac to the INITRD_MODULES list. This should
add the scsi_dh_rdac to initrd.
10. Install lsi-scsi_dh_rdac-kmp-default-0.0_2.6.27.19_5-1.
11. Reboot the host.
98
Installing the Device Mapper MultiPath on SLES11 sp1 or later

All the components required for DMMP are included in SUSE Linux Enterprise Server (SLES) version 11.1
sp1 installation media. By default, DMMP is disabled in SLES. Complete the following steps to enable
DMMP components on the host:
1. Use the media supplied with the operating system vendor to complete installation of SLES11 sp1.
2. Update and configure /etc/multipath.conf. A sample file is stored at /usr/share/doc/packages/
multipath-tools/multipath.conf.synthetic. Copy and rename this file to /etc/multipath.conf. Refer
to Working with Multipath.conf file for more details.
3. Enable multipathd service using the following command: #chkconfig multipathd on.
4. Edit the file /etc/sysconfig/kernel to add scsi_dh_rdac to the INITRD_MODULES list. This should
add scsi_dh_rdac to initrd.
5. Create the new initrd image using the following command: # mkinitrd -k /boot/vmlinux-$(uname
-r) -i /boot/initrd-$(uname -r)-scsi_dh -M /boot/System.map-$(uname -r)
6. Update the boot loader configuration file (grub.conf , lilo.conf, or yaboot.conf) with the newly built
initrd.
7. Reboot the host to boot with the new initrd image.
Installing the Device Mapper Multi-Path on RHEL 6.0, RHEL 6.1 or later
All the components required for DMMP are included in RHEL 6 and 6.1 installation media. By default,
DMMP is disabled. Complete the following steps to enable DMMP components on the host.
1. Use the media supplied with the operating system vendor to complete installation of RHEL 6.0, RHEL
6.1 or later.
2. Update and configure /etc/multipath.conf. A sample file is stored at /usr/share/doc/packages/
multipath-tools/multipath.conf.synthetic. Copy and rename this file to /etc/multipath.conf. Refer
to Working with Multipath.conf file for more details.
3. Enable multipathd service using the following command: #chkconfig multipathd on
4. Create an initramfs image using the scsi_dh_rdac driver:
a. Create a file scsi_dh_alua.conf in the /etc/modprobe.d/ directory.
b. In this file, add the following: alias scsi_hostadapter99 scsi_dh_rdac
5. Run the following command to create an initramfs image:#dracut -f /boot/initrd-$(uname
-r)-scsi_dh $(uname -r)
6. Update the boot loader configuration file (grub.conf , lilo.conf, or yaboot.conf) using initramfs.
7. Reboot the host to boot with the new initramfs image.
Working with Multipath.conf file

Multipath.conf is the configuration file for the multipath daemon, multipathd. This file overrides the
built-in configuration table for multipathd. Any line in the file that begins with the first non-white-space
character # is a comment line. Empty lines should be ignored.
By default, DMMP is supported on certain machine-type models of the IBM DS3000/DS5000 subsystems.
However, IBM recommends overriding the default settings using the multipath.conf file to ensure that
the DMMP settings are as under:
To set up the multipath.conf file, complete the following steps:
1. Copy the sample multipath.conf from the appropriate directory, depending on whether the Linux
operating system is Redhat RHEL or Novell SLES, to the /etc directory.
v For SLES, the file is named multipath.conf.synthetic and is stored in this directory:
/usr/share/doc/packages/multipath-tools/.
99
v For RHEL, the file is called multipath.conf.defaults and is stored in this directory:
/usr/share/doc/device-mapper-multipath-0.4.9/.
2. Rename the file multipath.conf.
3. Make the configuration changes described in this section to the new /etc/multipath.conf file. The
content of the sample multipath.conf file varies, depending on whether it is from SLES or RHEL
kernels.
Note: All entries for multipath devices are commented out initially. To uncomment, remove the first
character (#) from that section. You must uncomment the three sections - default, blacklist, and
devices.
The configuration file is divided into five sections:
defaults
Specifies all of the default values.
blacklist
Blacklists new installations. The default blacklist is listed in the commented-out section of
the/etc/multipath.conf file. Blacklist the device mapper multipath by WWID if you do not
want to use this functionality.
blacklist_exceptions
Specifies any exceptions to the items in the blacklist section.
devices
Lists all of the multipath devices with their matching vendor and product values.
multipaths
Lists all of the multipath devices with their matching WWID values.
To determine the attributes of a multipath device, check the multipaths section of the /etc/
multipath.conf file; then the devices section; and then the defaults section. Depending on the version of
the Linux kernel, the devices section of the sample multipath.conf file might already have settings
defined for your storage subsystem model product ID. All you need to do is verify that the settings
match the recommended settings listed below. Otherwise, you have to manually enter the devices settings
for your subsystem model product ID. If you have multiple storage subsystems with different product
IDs connected to the Linux host, add the device settings for each storage subsystem product ID in the
devices section of the /etc/ multipath.conf file. Sample settings for DS3500 (product ID 1746) and
DS5100/DS5300 (product ID 1818) in the devices section of the multipath.conf file in SLES operating
systems are shown below:
Note: If the Product ID exceeds four characters, use only the first four characters. In the following
example, although the Product ID is '1746 FAStT', the product is specified as '1746'. Similarly, '1818 FAStT'
is specified as '1818'.
Devices {
device {
vendor
product
path_grouping_policy
getuid_callout
path_selector
path_checker
features
hardware_handler
prio
failback
no_path_retry
rr_min_io
rr_weight
"IBM"
"1746"
group_by_prio
"/lib/udev/scsi_id -g -u -d /dev/%n"
"round-robin 0"
rdac
"2 pg_init_retries 50"
"1 rdac"
rdac
immediate
15
100
priorities
100
device {
vendor
product
getuid_callout
path_selector
path_checker
features
hardware_handler
prio
failback
no_path_retry
rr_min_io
rr_weight
"IBM"
"1818"
group_by_prio
"/lib/udev/scsi_id -g -u -d /dev/%n"
"round-robin 0"
rdac
"1 rdac"
rdac
immediate
15
100
priorities
Sample settings for DS3500 (product ID 1746) and DS5100/DS5300 (product ID 1818) in the devices
section of the multipath.conf file in RHEL operating systems are shown below:
Devices {
device {
vendor
product
getuid_callout
path_selector
path_checker
features
hardware_handler
prio
failback
no_path_retry
rr_min_io
rr_weight
"IBM"
"1746"
group_by_prio
"/lib/udev/scsi_id --whitelisted --device=/dev/%n"
"round-robin 0"
rdac
"1 rdac"
rdac
immediate
15
100
priorities
}
device {
vendor
product
getuid_callout
path_selector
path_checker
features
hardware_handler
prio
failback
no_path_retry
rr_min_io
rr_weight
"IBM"
"1818"
group_by_prio
"/lib/udev/scsi_id --whitelisted --device=/dev/%n"
"round-robin 0"
rdac
"1 rdac"
rdac
immediate
15
100
priorities
If you have Access LUN (sometimes referred to as UTM LUN) mapped to the host partitions, include an
entry in the blacklist section of the/etc/multipath.conf file, so that the file is not managed by the
DMMP. The Storage manager host software uses the Access LUN for in-band management of the storage
subsystem. The entries should follow the pattern of the following example:
blacklist {
device {
vendor "*"
product "Universal Xport"
}
101
The following table describes the attributes and values in the devices section of the /etc/multipath.conf
file.
Table 21. Attributes and parameter values in the multipath.conf file
Attribute
Parameter value
Description
group_by_prio
This attribute determines the path

grouping policy to be applied to this
specific vendor and product storage.
prio
rdac
This attribute sets the program and

arguments to determine the path
priority routine. The specified routine
should return a numeric value
specifying the relative priority of this
path. Higher numbers have a higher
priority.
getuid_callout
For SLES"/lib/udev/scsi_id -g -u
-d /dev/%n" For RHEL"/lib/udev/
scsi_id --whitelisted--device=/
dev/%n"
This attribute determines the

program and arguments to call out
and obtain a unique path identifier.
polling_interval
This attribute determines the interval

between two path checks, in seconds.
path_checker
rdac
This attribute establishes the method

used to determine the state of the
path.
path_selector
"round-robin 0"
This attribute determines the path

selector algorithm to use when there
is more than one path in a path
group.
hardware_handler
"1 rdac"
This attribute determines the

hardware handler to use for handling
device-specific knowledge.
failback
immediate
This attribute determines how the

daemon manages path group
failback. In this example, the
parameter is set to 10 seconds, so
failback occurs 10 seconds after a
device comes online. To disable the
failback, set this parameter to manual.
Set it to immediate to force failback to
occur immediately.
features
This attribute enables features. In this

example, the kernel parameter
pg_init_retries is set to 50. The
parameter pg_init_retries is used to
retry the mode select commands.
no_path_retry
30
This attribute determines the number

of retries before queuing is disabled.
Set this parameter to fail for
immediate failure (no queuing).
When this parameter is set to queue,
queuing continues indefinitely.
rr_min_io
100
The number of IO to route to a path

before switching to the next in the
same path group.
102
Table 21. Attributes and parameter values in the multipath.conf file (continued)
Attribute
Parameter value
Description
rr_weight
priorities
If set to priorities the multipath

configurator will assign path weights
as "path prio * rr_min_io"
Using the Device Mapper Devices

Multipath devices are created under the /dev/ directory with the prefix dm-. These devices are the same
as any other block devices on the host. To list all of the multipath devices, run the multipath -11
command. The following example shows system output from the multipath -11 command for one of the
multipath devices.
mpathp (3600a0b80005ab177000017544a8d6b92) dm-0 IBM, 1746
[size=5.0G][features=3 queue_if_no_path pg_init_retries
50][hwhandler=1 rdac][rw]
\_ round-robin 0 [prio=6][active]
\_ 5:0:0:0 sdc 8:32
[active][ready]
\_ round-robin 0 [prio=1][enabled]
\_ 4:0:0:0 sdb 8:16
[active][ghost]
FAStT
In the preceding example, the multipath device node for this device is /dev/mapper/mpathp and
/dev/dm-0. The following table lists some basic options and parameters for the multipath command.
Table 22. Options and parameters for the multipath command
Command
Description
multipath -h
Print usage information
multipath -11
Show the current multipath topology from all available

information (sysfs, the device mapper, path checkers, and
so on)
multipath -f map
Flush the multipath device map specified by the map

option, if the map is unused
multipath -F
Flush all unused multipath device maps
Troubleshooting the Device Mapper

Use the information in the following table to troubleshoot the Device Mapper.
Table 23. Troubleshooting the Device Mapper
Situation
Action
Check whether the multipath daemon, multipathd, is

running
At the command prompt, run the command

/etc/init.d/multipathd status
Determine why no devices are listed when you run the

multipath -11 command
At the command prompt, run the command #cat

/proc/scsi/scsi. The system output displays all of the
devices that are already discovered. Verify that the
multipath.conf file has been updated with the proper
settings.
Known Issues and Limitations

v When storage is configured with ADT/AVT mode, delays in device discovery might occur. Delays in
device discovery might result in long delays when the operating system boots.
103
v In certain error conditions with no_path_retry or queue_if_no_pathfeature enabled, applications might

hang forever. To overcome these conditions, you must enter the following command to all the affected
multipath devices: dmsetup message device 0 "fail_if_no_path" where device is the multipath device
name.
v An I/O hang might occur when a logical drive is unmapped without first deleting the DM device. This
limitation applies to only the SLES11 base. It is fixed in later versions.
v Stale entries might be noticed in multipath -ll output if the logical drives are unmapped or deleted
without first deleting the DM device and its underlying paths. This limitation applies to only the SUSE
11 base OS.
v In device mapper mode select command is issued synchronously for each LUN. With large LUN
configurations, slower failovers for DM multipath devices might occur if there is any delay in
completing of the mode select command. This limitation applies to only the SUSE 11 base OS. This has
been resolved in later versions.
v If the scsi_dh_rdac module is not included in initrd, slower device discovery might occur, and the
syslog might get populated with buffer I/O error messages.
v If the storage vendor and model are not included in scsi_dh_rdac device handler, slower device
discovery might be seen, and the syslog might get populated with buffer I/O error messages.
v Use of the DMMP and RDAC failover solutions together on the same host is not supported. Use only
one solution at a time.
Linux RDAC (MPP) driver

This section describes how to install the RDAC (MPP) driver for a Linux configuration.
Important: Before you install MPP, make sure that the partitions and LUNs are configured and assigned
and that the correct HBA driver is installed.
To install MPP, complete the following steps:
1. Download the MPP driver package from the IBM System Storage Disk support portal.
2. Create a directory on the host and download the MPP driver package to that directory.
3. Type the following command to uncompress the file:
# tar -zxvf rdac-LINUX-package_version-source.tar.gz
where package_version is the SLES or RHEL package version number. As a result, a directory called
linuxrdac-version# or linuxrdac is created.
4. Open the readme that is included in the linuxrdac-version# directory.
5. In the readme, find the instructions for building and installing the driver and complete all of the
steps.
Note: Be sure to restart the server before you proceed to the next step.
6. Type the following command to list the installed modules:
# lsmod
7. Verify that module entries are included in the following lsmod list.
Module entries for SLES or RHEL:
v mppVhba
v mppUpper
v lpfc (or qla2xxx for BladeCenter configurations)
v lpfcdfc (if ioctl module is installed)
Note: If you do not see the mpp_Vhba module, the likely cause is that the server was rebooted before
the LUNs were assigned, so the mpp_Vhba module was not installed. If this is the case, assign the
LUNs now, restart the server, and repeat this step.
104
8. Type the following command to verify the driver version:

# mppUtil -V
The Linux multipath driver version is displayed.

9. Type the following command to verify that devices are configured with the RDAC driver:
# ls -1R /proc/mpp
An output similar to the following example is displayed:

# ls -1R /proc/mpp
/proc/mpp:
total 0
dr-xr-xr-x
4 root
crwxrwxrwx
1 root
root
root
254,
0 Oct 24 02:56 DS4100-sys1

0 Oct 24 02:56 mppVBusNode
/proc/mpp/ DS4100-sys1:
total 0
dr-xr-xr-x
3 root
root
dr-xr-xr-x
3 root
root
-rw-r--r-1 root
root
-rw-r--r-1 root
root
-rw-r--r-1 root
root
-rw-r--r-1 root
root
-rw-r--r-1 root
root
-rw-r--r-1 root
root
0
0
0
0
0
0
0
0
/proc/mpp/ DS4100-sys1/controllerA:
total 0
dr-xr-xr-x
2 root
root
0 Oct 24 02:56 lpfc_h6c0t2
Oct
Oct
Oct
Oct
Oct
Oct
Oct
Oct
24
24
24
24
24
24
24
24
/proc/mpp/ DS4100-sys1/controllerA/lpfc_h6c0t2:
total 0
-rw-r--r-1 root
root
0 Oct 24
-rw-r--r-1 root
root
0 Oct 24
-rw-r--r-1 root
root
0 Oct 24
-rw-r--r-1 root
root
0 Oct 24
-rw-r--r-1 root
root
0 Oct 24
-rw-r--r-1 root
root
0 Oct 24
/proc/mpp/ DS4100-sys1/controllerB:
total 0
dr-xr-xr-x
2 root
root
02:56
02:56
02:56
02:56
02:56
02:56
02:56
02:56
02:56
02:56
02:56
02:56
02:56
02:56
controllerA
controllerB
virtualLun0
virtualLun1
virtualLun2
virtualLun3
virtualLun4
virtualLun5
LUN0
LUN1
LUN2
LUN3
LUN4
LUN5
0 Oct 24 02:56 lpfc_h5c0t0
/proc/mpp/ DS4100-sys1/controllerB/lpfc_h5c0t0:
total 0
-rw-r--r-1 root
root
0 Oct 24
-rw-r--r-1 root
root
0 Oct 24
-rw-r--r-1 root
root
0 Oct 24
-rw-r--r-1 root
root
0 Oct 24
-rw-r--r-1 root
root
0 Oct 24
-rw-r--r-1 root
root
0 Oct 24
02:56
02:56
02:56
02:56
02:56
02:56
LUN0
LUN1
LUN2
LUN3
LUN4
LUN5
Note: After you install the RDAC driver, the following commands and pages are available:
v mppUtil
v mppBusRescan
v mppUpdate
v RDAC
MAC OS multipath driver

The only supported MAC OS multipath driver is the one provided by the HBA vendor - ATTO
Corporation. For instructions to install the MAC OS multipath driver, go to the ATTO IBM Solutions
105
website. On that website, see information about installing the Celerity HBA driver and installing the
ATTO Configuration Tool in the ATTO Celerity MultiPaxath Director Installation and Operation Manual.
Important: After you configure a LUN, you must reboot your server for the LUN to be detected.
Veritas DMP driver

See the Symantec Storage Foundation for Windows documentation for instructions for installing the
Veritas DMP driver at http://www.symantec.com/business/support/.
Note: The Array Support Library (ASL) that supports DMP on the storage subsystem might have to be
loaded. The ASL might be a separate file available from Symantec, or it might be integrated with Volume
Manager, depending on the version of Storage Foundation.
HP-UX PV-links
If an HP-UX system is attached with two host bus adapters to the storage subsystem, you can establish
redundant access to storage with physical volume links (PV-links), a feature of the HP-UX operating
system. PV-links achieve access redundancy with devices that have both primary and secondary paths to
the same device.
Important:
v There are two methods for establishing redundant access to storage using PV-links:
If you have controller firmware version 07.xx.xx.xx, 06.xx.xx.xx, or 05.xx.xx.xx, use the method
described in Using PV-links: Method 1.
If you have controller firmware version 04.xx.xx.xx, use the method described in Using PV-links:
Method 2 on page 107.
v SMutil must be installed on the host for either method.
Using PV-links: Method 1

For controller firmware version 05.xx.xx.xx or later, use the following procedure to enable multipath I/O
with PV-links:
1. Run the hot_add command from HP-UX at the shell prompt. This command updates any new devices
that are created or added. A dump is generated. When the hot_add command runs, each new logical
drive that is created in the Subsystem Management window represents a disk device to the operating
system.
2. Run the SMdevices command. The system provides a dump similar to the example in the table that
follows. Notice that every logical drive and logical drive access unit has been assigned a logical unit
number (LUN). Each logical drive has two paths. Each storage subsystem controller has one logical
drive access.
/dev/rdsk/c166t0d0 [Storage Subsystem DS4000, Logical Drive Accounting, LUN 0,
Logical Drive WWN <600a0b80000f56d00000001e3eaead2b>,
Preferred Path (Controller-B): In Use]
/dev/rdsk/c166t0d1 [Storage Subsystem DS4000, Logical Drive HR, LUN 1,
Logical Drive WWN <600a0b80000f5d6c000000273eaeae30>,
Alternate Path (Controller-B): Not In Use]
/dev/rdsk/c166t0d2 [Storage Subsystem DS4000, Logical Drive Finance,
LUN 2, Logical Drive WWN <600a0b80000f5d6c000000253eaeadf8>,
/dev/rdsk/c166t0d3 [Storage Subsystem DS4000, Logical Drive Purchasing,
LUN 3, Logical Drive WWN <600a0b80000f5d6c000000243eaeadbe>,
/dev/rdsk/c166t0d4 [Storage Subsystem DS4000, Logical Drive Development,
LUN 4, Logical Drive WWN <600a0b80000f56d00000001d3eaeacef>,
Preferred Path (Controller-B): In Use]
/dev/rdsk/c166t3d7 [Storage Subsystem DS4000, Logical Drive Access, LUN 31,
Logical Drive WWN <600a0b80000f56d00000001b00000000>]
106
/dev/rdsk/c172t0d0 [Storage Subsystem DS4000, Logical

Logical Drive WWN <600a0b80000f56d00000001e3eaead2b>,
Alternate Path (Controller-A): Not In Use]
/dev/rdsk/c172t0d1 [Storage Subsystem DS4000, logical
Logical Drive WWN <600a0b80000f5d6c000000273eaeae30>,
Preferred Path (Controller-A): In Use]
Logical Drive WWN <600a0b80000f5d6c000000253eaeadf8>,
Logical Drive WWN <600a0b80000f5d6c000000243eaeadbe>,
Logical Drive WWN <600a0b80000f56d00000001d3eaeacef>,
Alternate Path (Controller-A): Not In Use]
Logical Drive WWN <600a0b80000f5d6c0000002200000000>]
Drive Accounting, LUN 0,

Drive HR, LUN 1,
Drive Finance, LUN 2,
Drive Purchasing, LUN 3,
Drive Development, LUN 4,
Drive Access, LUN 31,
Note: If you do not see the logical drives and logical drive accesses after you run the hot_add and
SMdevices commands, use the reboot command to restart the HP-UX host.
3. Determine the preferred and alternate paths for each logical drive by examining the output from the
SMdevices command, as shown in the previous example. Notice that each device is listed twice; one
instance is the preferred path and one instance is the alternate path.
Preferred path
In the following sample output, the preferred path is /dev/rdsk/c166t0d0.
/dev/rdsk/c166t0d0 [Storage Subsystem DS4000, Logical Drive
Accounting, LUN 0, Logical Drive WWN <600a0b80000f56d00000001e3eaead2b>,
Preferred Path (Controller-B):
In Use]
Alternate path
In the following sample output, the alternate path is /dev/rdsk/c172t0d0.
Accounting, LUN 0, Logical Drive WWN <600a0b80000f56d00000001e3eaead2b>,
Alternate Path (Controller-A):
NotIn Use]
Using PV-links: Method 2

For controller firmware version 4.xx.xx.xx, use the following procedures to enable multipath I/O with
PV-links:
v Determine the preferred and alternate paths
v Create the logical drives and arrays
Determining preferred and alternate paths

1. Run the hot_add command from HP-UX at the shell prompt. This command updates any new devices
that are created or added. A dump is generated. When the hot_add command runs, each new logical
drive that is created in the Subsystem Management window represents a disk device to the operating
system.
2. Run the SMdevices command. The system provides a dump similar to the following example. Notice
that every logical drive and logical drive access unit has been assigned a logical unit number (LUN).
Each logical drive has two paths. Each storage subsystem controller has one logical drive access.
Logical Drive WWN <600a0b80000f56d00000001e3eaead2b>]
Logical Drive WWN <600a0b80000f5d6c000000273eaeae30>]
Logical Drive WWN <600a0b80000f5d6c000000253eaeadf8>]
Logical Drive WWN <600a0b80000f5d6c000000243eaeadbe>]
Accounting, LUN 0,
HR, LUN 1,
Finance, LUN 2,
Purchasing, LUN 3,
Development, LUN 4,
107
Logical Drive WWN <600a0b80000f56d00000001d3eaeacef>]

/dev/rdsk/c166t3d7 [Storage Subsystem DS4000,Logical Drive Access, LUN 31,
Logical Drive WWN <600a0b80000f56d00000001e3eaead2b>]
/dev/rdsk/c172t0d1 [Storage Subsystem DS4000, logical
Logical Drive WWN <600a0b80000f5d6c000000273eaeae30>]
Logical Drive WWN <600a0b80000f5d6c000000253eaeadf8>]
Logical Drive WWN <600a0b80000f5d6c000000243eaeadbe>]
Logical Drive WWN <600a0b80000f56d00000001d3eaeacef>]
Drive Accounting, LUN 0,

Drive HR, LUN 1,
Drive Finance, LUN 2,
Drive Purchasing, LUN 3,
Drive Development, LUN 4,
Drive Access, LUN 31,
Note: If you do not see the logical drives and logical drive accesses after you run the hot_add and
SMdevices commands, use the reboot command to restart the HP-UX host.
3. Determine the preferred and alternate paths for each logical drive by examining the output from the
SMdevices command, as shown in the example in preceding example.
Notice that each device is listed twice; one instance is the preferred path and one instance is the
alternate path. Also, notice that each device has a worldwide name (WWN). Part of the WWN of each
logical drive is unique for each controller in the storage subsystem. The WWNs for the logical drive
access in the preceding example differ in only five digits, f56d0 and f5d6c.
The devices in the preceding example are viewed through the controllers c166 and c172. To determine
the preferred path of a specific logical drive that is seen by the operating system, complete the
following steps:
a. Find the WWN for each logical drive access. In this case, Logical Drive Access 1 is associated with
c166 and has the WWN of f56d0.
Logical Drive Access 2 is associated with c172 and has the WWN of f5d6c.
b. Identify the preferred device path name for the attached storage device by matching the logical
drive WWN to a logical drive access WWN. In this case, the WWN for LUN 0 is associated with
controller c166 and c172. Therefore, the preferred path for LUN 0 is /dev/rdsk/c166t0d0, which is
controller c166.
Accounting, LUN 0, Logical Drive g<600a0b80000f56d00000001e3eaead2b>]
The alternate path is /dev/rdsk/c172t0d0, which is controller c172.

Accounting, LUN 0, Logical Drive WWN <600a0b80000f56d00000001e3eaead2b>]
c. To keep a record for future reference, enter this path information for LUN 0 into a matrix (similar
to the one in Table 24).
Table 24. Sample record of logical drive preferred and alternate paths
LUN
Logical drive name
Preferred path
Alternate path
Accounting
/dev/rdsk/c166t0d0
/dev/rdsk/c172t0d0
HR
/dev/rdsk/c172t0d1
/dev/rdsk/c166t0d1
Finance
dev/rdsk/c172t0d2
/dev/rdsk/c166t0d2
Purchasing
/dev/rdsk/c172t0d3
/dev/rdsk/c166t0d3
108
Table 24. Sample record of logical drive preferred and alternate paths (continued)
LUN
Logical drive name
Preferred path
Alternate path
Development
/dev/rdsk/c166t0d4
/dev/rdsk/c172t0d4
d. Repeat step 3.a through step 3.c for each logical drive that is seen by the operating system.
Creating logical drives and arrays

After you have determined the preferred and alternate paths, and have recorded them in a matrix for
future reference, complete the following steps to create logical drives and arrays.
Important: Do not use the HP System Administration Management (SAM) application for DS3000,
DS4000, or DS5000 storage configuration; if you do, you might get unwanted results.
Note: The steps in this procedure refer to LUN 0 in Table 24 on page 108.
1. Create a physical logical drive and define the primary paths for the attached storage devices. The
primary path is the preferred path. Type the following command at the shell prompt:
#pvcreate /dev/rdsk/c166t0d0
The system confirms the creation of the new physical logical drive.
2. Create arrays.
Note: For more information about how to create arrays, see the HP-UX documentation or manpages.
a. Make a directory for the array by typing the following commands. This directory must be in the
/dev directory.
#cd /dev
#mkdir /vg1
b. Create the group special file in the /dev directory for the array by typing the following command:
#mknod /dev/vg1/group c 64 0x010000
c. Create an array and define physical logical drive names (primary link) for the attached storage
device by typing the following command:
#vgcreate /dev/vg1/ /dev/dsk/c166t0d0
d. Define the secondary path name (alternate path) for the attached-storage device by typing the
following command:
#vgextend vg1 /dev/dsk/c172t0d0
Note: You can also use the vgextend command to add storage devices to an existing array. Add
the primary path first, and then add the alternate path, as shown in the following example.
1) Add the primary path for LUN1.
2) Add the secondary path for LUN1.

3. Create logical drives. For more information, see the HP-UX documentation.
4. Create file systems for the logical drives.
5. Repeat step 1 through step 4 to create additional arrays. For more information, see the HP-UX
documentation.
6. Verify the primary (preferred) and secondary (alternate) paths for each device by typing the following
command:
#vgdisplay -v vgname
where vgname is the array name.

109
HP-UX native multipathing

Multipathing is native to HP-UX 11i v3. It is built into the mass storage subsystem, and it is available to
applications without any special configuration.
For more information about native multipathing in HP-UX 11iv3, see the documentation at
http://docs.hp.com/en/oshpux11iv3.html.
Solaris failover drivers

A failover driver monitors I/O paths. If a component failure occurs in one of the Fibre Channel paths, the
failover driver reroutes all I/O to another path.
Solaris host systems require one of the following failover drivers:
v Solaris Multiplexed I/O (MPxIO)
v RDAC
v Veritas VolumeManager with Dynamic Multipathing (DMP)
Note:
1. RDAC is not supported on Solaris 10. You must use either Solaris MPxIO or the Veritas DMP failover
driver.
2. With Solaris 10, MPxIO capability is built in. If you want to use MPxIO with previous versions of
Solaris, you must install SUN StorEdge SAN Foundation Suite.
This section includes the following procedures:
v Installing the MPxIO driver
v Installing the RDAC failover driver on Solaris and modifying the configuration files on page 116
v Planning and preparing for Veritas DMP driver installation on page 118
Installing the MPxIO driver

Multiplexed I/O (MPxIO) is a Sun Solaris multipath driver architecture. This failover driver enables
storage subsystems to be accessed through multiple host controller interfaces from a single instance of the
storage subsystem. MPxIO helps protect against storage subsystem outages that are caused by controller
failures. If one controller fails, MPxIO automatically switches to an alternate controller.
MPxIO is fully integrated within the Solaris 10 operating system. For Solaris 8 and 9 operating systems,
MPxIO is available as part of the Sun StorEdge SAN Foundation Suite and must be installed separately.
For the latest supported version of Sun StorEdge SAN Foundation Suite, the latest Solaris kernel patches,
and the most recent updates to information about using MPxIO, see the Storage Manager readme file for
Solaris. See Finding Storage Manager software, controller firmware, and readme files on page xiii for
steps to find the readme file on the web.
This section contains the following topics:
v Device name change considerations for MPxIO on page 111
v Acquiring the latest MPxIO driver version on page 111
v Enabling the MPxIO failover driver on page 111
v Disabling the MPxIO multipath driver on page 116
Note: For more information, see the Sun StorEdge SAN Foundation Software Installation Guide, Sun StorEdge
SAN Foundation Software Configuration Guide, and Sun Solaris Fibre Channel and Storage Multipathing
Administration Guide on the Sun website http://docs.sun.com.
110
Device name change considerations for MPxIO:

In the /dev and /devices trees, devices are named differently from their original names when MPxIO is
enabled. See the following examples.
Device name with MPxIO disabled:
/dev/dsk/c1t1d0s0
Device name with MPxIO enabled:

/dev/rdsk/c0t600A0B800011121800006B31452CC6A0d0s2
You must configure the applications that engage the device directly to use the new names whenever the
MPxIO configuration is enabled or disabled.
In addition, the /etc/vfstab file and the dump configuration also contain references to device names.
When you use the stmsboot command to enable or disable MPxIO, as described in the following sections,
/etc/vfstab and the dump configuration are automatically updated with the new device names.
Acquiring the latest MPxIO driver version: The method of acquiring MPxIO depends upon which
version of Solaris you have installed:
Solaris 10
MPxIO is integrated within the Solaris 10 operating system and does not have to be installed
separately. Use Solaris 10 patches to update MPxIO with Solaris 10. The patches are available at
the Sun Technical Support website http://sunsolve.sun.com.
Note: You must install the regular kernel jumbo patch, because there are dependencies between
the various patches that make up the driver stack.
Solaris 8 and 9
Because MPxIO is not included with Solaris 8 and 9, you must download the required SAN suite
(Sun StorEdge SAN Foundation Suite) from the Sun Technical Support website
http://sunsolve.sun.com. On this webpage, click SAN 4.4 release Software/Firmware Upgrades
& Documentation.
Note: Use the install_it.ksh script that is provided to install the software.
Enabling the MPxIO failover driver: This section describes how to enable MPxIO by using the
stmsboot command. In addition to enabling MPxIO, this command also updates the device names in the
/etc/vfstab file and the dump configuration files during the next reboot.
Note: In Solaris 10, the stmsboot command is used to enable or disable MPxIO on all devices.
Before you begin:
1. Install the Solaris operating system, and the latest patches.
2. Make sure that the Solaris host type was selected when the host was defined.
Enabling MPxIO on Solaris 8 and 9
1. Install the latest version of Sun StorEdge SAN Foundation Suite and required patches, using the Sun
StorEdge install_it script. For more information, see the Sun StorEdge SAN Foundation Suite x.xx
Installation Guide (where x.xx is the version of the StorEdge software).
2. Edit the /kernel/drv/scsi_vhci.conf configuration file to make sure that the VID/PID is not
specified in this file. Also, make sure that the following entries are in the file:
mpxio-disable=no;
load-balance=none;
auto-failback=enable;
111
Note: In a cluster environment where logical drives (LUNs) are shared between multiple Sun servers,
you might have to set the auto-failback parameter to disable to prevent the following phenomenon,
which can occur when one of the servers has a failed path to one of the shared LUNs.
If a host in a cluster server configuration loses a physical path to a storage subsystem controller,
LUNs that are mapped to the cluster group can periodically failover and then failback between cluster
nodes until the failed path is restored. This behavior is the result of the automatic logical drive
failback feature of the multipath driver. The cluster node with a failed path to a storage subsystem
controller issues a failover command for all LUNs that were mapped to the cluster group to the
controller that it can access. After a programmed interval, the nodes that did not have a failed path
issue a failback command for the LUNs because they can access the LUNs on both controllers. The
cluster node with the failed path is unable to access certain LUNs. This cluster node then issues a
failover command for all LUNs, which repeats the LUN failover-failback cycle.
For supported cluster services, see the System Storage Interoperation Center at www.ibm.com/
systems/support/storage/config/ssic
3. If you made any changes to the /kernel/drv/scsi_vhci.conf file in the previous step, save the file
and use the following command to restart the server:
# shutdown
g0
i6
4. If necessary, update the Fibre Channel HBA firmware.

5. Create the storage subsystem logical drives and map them to the Fibre Channel HBA ports in the Sun
servers.
Enabling MPxIO on Solaris 10
Note the following considerations for stmsboot -e [enable] -d [disable] and -u [update]:
v When you run the stmsboot command, accept the default to Reboot the system now.
v The stmsboot command saves copies of the original /kernel/drv/fp.conf and /etc/vfstab files before
it modifies them, so you can use the saved files to recover from any unexpected problems.
v Make sure that the eeprom boot device is set to boot from the current boot device.
To enable MPxIO on all Fibre Channel devices, complete the following steps:
1. Run the stmsboot -e command, and select the default [y] to restart the server:
# stmsboot -e
WARNING: This operation will require a reboot.
Do you want to continue ? [y/n] (default: y) y
The changes will come into effect after rebooting the system.
Reboot the system now ? [y/n] (default: y) y
Note: During the reboot, /etc/vfstab and the dump configuration are updated to reflect the device
name changes.
2. After the reboot, configure your applications to use new device names, as explained in Device name
change considerations for MPxIO on page 111.
3. If necessary, edit the /kernel/drv/fp.conf configuration file to verify that the following parameter is
set as follows:
mpxio-disable=no;
Edit the /kernel/drv/scsi_vhci.conf configuration file to verify that the following parameters are set
as follows:
load-balance=none;
auto-failback=enable;
4. If you made any changes to configuration files in the previous step, save the file, and use the
following command to restart the server:
112
# shutdown
-g0
-y
-i6
5. If necessary, update the Fibre Channel HBA firmware.

6. Create the storage subsystem logical drives and map them to the Fibre Channel HBA ports in the Sun
servers.
Verifying devices and configuring failover/failback path for the mapped LUNs
To verify devices and configure the failover path for the mapped LUNs, complete the following steps:
1. Use the cfgadm al command to verify the devices. Run the cfgadm al command to display
information about the host ports and their attached devices:
# cfgadm -al
Ap_Id
PCI0
PCI1
PCI2
PCI3
PCI4
PCI5
PCI6
PCI7
PCI8
c0
c0::dsk/c0t6d0
c1
c1::500000e0106fca91
c1::500000e0106fcde1
c1::500000e0106fcf31
c1::500000e0106fd061
c1::500000e0106fd7b1
c1::500000e0106fdaa1
c1::50800200001d9841
c2
c2::201400a0b811804a
c2::201400a0b8118098
c2::201700a0b8111580
c3
c3::201500a0b8118098
c3::201600a0b8111580
c3::202500a0b811804a
c4
c4::200400a0b80f1285
c4::200400a0b8127a26
c5
c5::200400a0b82643f5
c5::200500a0b80f1285
c5::200500a0b8127a26
c5::200c00a0b812dc5a
usb0/1
usb0/2
usb0/3
usb0/4
#
Type
vgs8514/hp
unknown
unknown
mult/hp
unknown
unknown
unknown
mult/hp
mult/hp
scsi-bus
CD-ROM
fc-private
disk
disk
disk
disk
disk
disk
ESI
fc-fabric
disk
disk
disk
fc-fabric
disk
disk
disk
fc-fabric
disk
disk
fc-fabric
disk
disk
disk
disk
usb-kbd
usb-mouse
unknown
unknown
Receptacle
connected
empty
empty
connected
empty
empty
empty
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
empty
empty
Occupant
configured
unconfigured
unconfigured
configured
unconfigured
unconfigured
unconfigured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
unconfigured
configured
configured
configured
configured
configured
unconfigured
unconfigured
Condition
ok
unknown
unknown
ok
unknown
unknown
unknown
ok
ok
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unusable
unusable
unusable
unknown
unusable
unusable
unusable
unknown
unknown
unusable
unknown
unknown
unknown
unusable
unknown
ok
ok
ok
ok
2. You can also display information about the attachment points on a server. In the following example,
c0 represents a fabric-connected host port, and c1 represents a private, loop-connected host port. Use
the cfgadm command to manage the device configuration on fabric-connected host ports. By default,
the device configuration on private, loop-connected host ports is managed by the Solaris host.
Note: The cfgadm -1 command displays information about Fibre Channel host ports. Also use the
cfgadm -al command to display information about Fibre Channel devices. The lines that include a
port World Wide Name (WWN) in the Ap_Id field associated with c0 represent a fabric device. Use
the cfgadm configure and cfgadm unconfigure commands to manage those devices and make them
available to Solaris hosts.
113
# cfgadm -l
Ap_Id
c0
c1
Type
fc-fabric
fc-private
Receptacle
connected
connected
Occupant
Condition
unconfigured unknown
configured
unknown
3. Configure the device using the following command:

cfgadm c configure Ap-Id
The Ap_ID parameter specifies the attachment point ID of the configured Fibre Channel devices. This
ID can be the controller number and WWN of a device (for example, c3::50020f230000591d).
See the output example in step 1. Also, see the cfgadm manpage for an explanation of attachment
points.
Note: An Ap_Id with type fc-private cannot be unconfigured. Only the type fc-fabric can be
configured and unconfigured.
4. Use the luxadm probe command to list all mapped LUNs:
# luxadm probe
luxadm probe
No Network Array enclosures found in /dev/es
Node WWN:200400a0b8111218 Device Type:Disk device
Logical Path:/dev/rdsk/c0t600A0B800011121800006ADE452CBC62d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006ADF452CBC6Ed0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AE0452CBC7Ad0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AE1452CBC88d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AE2452CBC94d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AE3452CBCA0d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AE4452CBCACd0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AE5452CBCB8d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AE6452CBCC4d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AE7452CBCD2d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AE8452CBCDEd0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AE9452CBCEAd0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AEA452CBCF8d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AEB452CBD04d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AEC452CBD10d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006AED452CBD1Ed0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006B2A452CC65Cd0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006B2B452CC666d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006B2C452CC670d0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006B2D452CC67Ad0s2
Logical Path:/dev/rdsk/c0t600A0B800011121800006B31452CC6A0d0s2
114

Logical Path:/dev/rdsk/c0t600A0B800011121800006B32452CC6ACd0s2
Logical Path:/dev/rdsk/c8t201400A0B8111218d7s2
5. You can use the luxadm display logical path command to list more details about each mapped LUN,
including the number of paths to each LUN. The following example uses a logical path from the
previous example.
# luxadm display /dev/rdsk/c0t600A0B800011121800006B31452CC6A0d0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c0t600A0B800011121800006B31452CC6A0d0s2
Vendor:
IBM
Product ID:
1742-900
Revision:
0914
Serial Num:
1T51207691
Uninitialized capacity: 1024.000 MBytes
Write Cache:
Enabled
Read Cache:
Enabled
Minimum prefetch:
0x0
Maximum prefetch:
0x0
Device Type:
Disk device
Path(s):
/dev/rdsk/c0t600A0B800011121800006B31452CC6A0d0s2
/devices/scsi_vhci/ssd@g600a0b800011121800006b31452cc6a0:c,raw
Controller
/devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0,1/fp@0,0
Device Address
201400a0b8111218,1e
Host controller port WWN
210100e08ba0fca0
Class
secondary
State
STANDBY
Controller
/devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0,1/fp@0,0
Device Address
201500a0b8111218,1e
210100e08ba0fca0
Class
primary
State
ONLINE
Controller
/devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0/fp@0,0
Device Address
201400a0b8111218,1e
210000e08b80fca0
Class
secondary
State
STANDBY
Controller
/devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0/fp@0,0
Device Address
201500a0b8111218,1e
210000e08b80fca0
Class
primary
State
ONLINE
#
Unconfiguring a failover/failback path

To unconfigure a failover/failback path, complete the following steps:
1. Before you unconfigure a fabric device, stop all activity to the device and unmount any file systems
on the fabric device (see the Solaris administration documentation for unmounting procedures).
2. Run the cfgadm -al command to display information about the host ports and their attached devices.
3. Unconfigure the LUN by running the following command:
cfgadm c unconfigure Ap-Id
Where Ap-Id is the LUN that you want to unconfigure.

4. Run the cfgadm -al command again to verify that the LUN is now unconfigured.
5. If necessary, define the file structure using the newfs command. Add entries to the /etc/vfstab file.
6. Type the following command to restart the server:
shutdown -g0 -y -i6
115
Disabling the MPxIO multipath driver: To disable the MPxIO multipath driver, take the applicable
action for your version of Solaris:
v For Solaris 10, unconfigure all devices by using the cfgadm c unconfigure AP-id Ap-id command.
Then, run the stmsboot d command, and accept the default to Reboot the system now.
v For Solaris 8 and 9, unconfigure all devices by using the cfgadm c unconfigure AP-id Ap-id
command, and edit the /kernel/drv/scsi_vhci.conf configuration file to set the value of the
mpxio-disable parameter to yes. Restart the server.
To learn how to revert the patches or use the StorEdge software, see the Sun StorEdge SAN Foundation
Installation Software Guide at http://docs.sun.com.
Installing the RDAC failover driver on Solaris and modifying the configuration files
This section describes how to install RDAC on a Solaris host.
Before you begin:
1. RDAC is supported only on Solaris 8 and 9.
2. Because you cannot run both RDAC and MPxIO, make sure that MPxIO is disabled. Check the
configuration files (/kernel/drv/scsi_vhci.conf, /kernel/drv/fp.conf, or both) and make sure that
the value of the mpxio-disable parameter to set to Yes.
3. You must install an HBA driver package before you install RDAC. If you have a SAN-attached
configuration, you must also modify the HBA configuration file before you install RDAC. If you fail
to follow the procedures in this order, problems can occur.
4. If you modify the failover settings in the HBA configuration file after you install RDAC, you must
remove the RDAC from the host.
Important: In some configurations, a patch is required for RDAC to function correctly. Before you begin
the RDAC installation, check the Storage Manager readme file for Solaris to find out whether the patch is
required for your specific configuration. You can also find the latest RDAC versions and other important
information in the readme file. For more information about how to find the readme file on the web, see
Finding Storage Manager software, controller firmware, and readme files on page xiii.
Installing the RDAC failover driver

To install the RDAC failover driver, complete the following steps:
1. Insert the Solaris installation DVD in the DVD drive.
Note: In this procedure, the installation DVD is mounted at /cdrom/SM91. Modify these commands as
needed for your installation. It can be 'cdrom' or 'dvdrom' depending on the way the disk has been
mounted.
2. Type the following command to start installing the RDAC package:
# pkgadd -d path/filename.pkg
where path/filename is the directory path and name of the package that you want to install.
The installation process begins.
Information about the packages that can be installed in the specified directory is displayed on the
command line, as in the following example:
The following packages are available:
1 RDAC
Redundant Disk Array Controller

(sparc) version number
Select package(s) you wish to process (or all to process all

packages). (default:all) [?,??,q]:
3. Type the value of the package that you are installing and press Enter. The installation process begins.
116
4. The software automatically checks for package conflicts. If any conflicts are detected, a message is
displayed that indicates that some files are already installed and are in use by another package. The
following prompt is displayed:
Do you want to install these conflicting files [y, n, ?]
Type y and press Enter. The following prompt is displayed:

This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <RDAC>
[y, n, ?]
5. Type y and press Enter. The installation process continues. When the RDAC package is successfully
installed, the following message is displayed:
Installation of <RDAC> was successful.
6. Make sure that the variables in the configuration files for the JNI adapter cards have been set to the
correct values.
7. Type the following command to restart the Solaris host:
# shutdown
-g0
-y
-i6
Modifying the configuration files

Important: Any modification to the persistent bindings in the jnic146x.conf configuration file requires
the removal of RDAC. After the RDAC is removed, you can modify the persistent bindings in the
jnic146x.conf file and then reinstall RDAC.
Complete the following steps to modify the sd.conf or jnic146x.conf files:
1. Type the following command to remove RDAC:
# pkgrm RDAC_driver_pkg_name
where RDAC_driver_pkg_name is the name of the RDAC driver package that you want to remove.
2. Type the following command to verify that the RDAC drive package is removed:
# pkginfo RDAC_driver_pkg_name
where RDAC_driver_pkg_name is the name of the RDAC driver package that you removed.
# shutdown
-g0
-y
-i6
4. Type the following command to modify persistent bindings in the sd.conf file or edit the sd.conf file:
# vi /kernel/drv/jnic146x.conf or sd.conf
5. After you have finished making changes, type the following command to save the changes:
# :wq
6. Type the following command to install the RDAC driver package:

# pkgadd -d RDAC_driver_pkg_name
where RDAC_driver_pkg_name is the name of the RDAC driver package that you want to install.
7. Type the following command to verify package installation:
# pkginfo RDAC_driver_pkg_name
where RDAC_driver_pkg_name is the name of the RDAC driver package that you installed.
# shutdown
-g0
-y
-i6
117
Note: You must restart the host after you modify the jnic146x.conf file, because the jnic146x.conf
driver is read only during the boot process. Failure to restart the host might cause some devices to be
inaccessible.
Planning and preparing for Veritas DMP driver installation

This section describes how to plan and prepare for Veritas Dynamic Multipathing (DMP) driver
installation. The Veritas DMP driver is a failover driver for Solaris hosts. The DMP failover driver is a
feature of Veritas Volume Manager, which is a component of the Storage Foundation product from
Symantec. Although RDAC allows you to have only 32 LUNs, DMP allows you to have up to 256 LUNs.
Important: This document does not describe how to install the Veritas product. For more information, see
the Symantec documentation at http://www.symantec.com/business/support/.
System requirements
Make sure that your server meets the following requirements for installing Veritas DMP:
v Solaris operating system
v Veritas Volume Manager 4.0, 4.1, 5.0, or 5.1
v Array Support Library (ASL), which enables Solaris to recognize the DS3000, DS4000, or DS5000
machine type
Note: The ASL might be a separate file that is available from Symantec, or it might be integrated with
Volume Manager, depending on the version of Storage Foundation.
Veritas DMP installation overview

Make sure that your server meets the following prerequisites for installing Veritas DMP:
v The HBAs are installed on the Solaris host.
v The parameter settings in the HBA configuration file (for example, qla2300.conf) are modified.
v In a SAN environment, bindings are configured.
v The zones are created and enabled for the Solaris partition.
v Storage is mapped to the Solaris partition.
Complete the procedures in the following order to complete the Veritas DMP installation:
1. Preparing for Veritas DMP installation
2. Installing the ASL package on page 120
Preparing for Veritas DMP installation

To prepare the host for Veritas DMP installation, complete the following steps:
1. Choose the Solaris host on which you want to install DMP.
2. Complete the following steps to manually define the targets and LUNs in the /kernel/drv/sd.conf
file:
Note: By default, the /kernel/drv/sd.conf file defines targets 0, 1, 2, and 3. LUN0 also is defined for
targets 0, 1, 2, and 3. Each target represents a controller to a storage subsystem, and each LUN
represents a logical drive. If you are adding target or LUN definitions to the /kernel/drv/sd.conf file
for an existing DMP configuration, be sure to reboot the Solaris host.
a. Type the following command to open the /kernel/drv/sd.conf file with the vi Editor:
# vi /kernel/drv/sd.conf
The file looks similar to the following example:
118
#
# Copyright (c) 1992, Sun Microsystems, Inc.
#
# ident "@(#)sd.conf 1.9 98/01/11 SMI"
name="sd" class="scsi" class_prop="atapi"
target=0 lun=0;
target=1 lun=0;
target=2 lun=0;
target=3 lun=0;
b. Use the vi Editor to add target and LUN definitions. In the following example, it is assumed that
the Solaris host is attached to one storage subsystem with three LUNs mapped to the subsystem
storage partition. In addition, the access LUN must be mapped to the partition.
#
# Copyright (c) 1992, Sun Microsystems, Inc.
#
# ident "@(#)sd.conf 1.9 98/01/11 SMI"
target=0 lun=0;
target=1 lun=0;
target=2 lun=0;
target=3 lun=0;
name="sd"
name="sd"
name="sd"
name="sd"
name="sd"
name="sd"
name="sd"
name="sd"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
target=0
target=0
target=0
target=0
target=1
target=1
target=1
target=1
lun=1;
lun=2;
lun=3;
lun=31;
lun=1;
lun=2;
lun=3;
lun=31;
c. Type the following command to save the new entries in the /kernel/drv/sd.conf file:
# :wq
3. Type the following command to verify that RDAC is not installed on the host:
# pkginfo -l RDAC
4. If RDAC is installed, type the following command to remove it:

# pkgrm RDAC
5. Verify that a host partition has been created.

Important: Set the host type to Solaris with DMP. Failure to do so results in an inability to map for
more than the RDAC limit of 32 LUNs and causes other unwanted results.
6. Make sure that all of the paths are optimal and are in a preferred path state from the SMclient.
7. Install the Veritas Storage Foundation Solaris, including Veritas Volume Manager with DMP.
119
Important: Before you install Veritas Storage Foundation Solaris with Veritas Volume Manager and
DMP, make sure that you have the required license keys. This document does not describe how to
install the Veritas product. For more information, see the Symantec documentation
athttp://www.symantec.com/business/support/.
# shutdown
-g0
-y
-i6
Installing the ASL package

If required, complete the following steps to install the ASL package.
Note: The VxVM 4.x version of the ASL package is named SMibmasl (for more information, see
http://seer.entsupport.symantec.com/docs/284913.htm). For VxVM version 5.0 and later, many ASLs are
integrated into VxVM and do not have to be installed. For VxVM version 5.0 and later, the ASL package
is named VRTSLSIasl (see http://seer.entsupport.symantec.com/docs/340469.htm). The following
example assumes that VxVM 4.x is being installed.
1. Type the following command to install the SMibmasl package:
Note: You can either select the default (all) or select option 1.
# pkgadd -d SMibmasl_pkg

# shutdown
-g0
-y
-i6
See the Symantec Veritas documentation for information about how to complete the following tasks:
v Start the Veritas Volume Manager
v Set up disk groups
v Create volumes
v Create file systems
v Mount file systems
Identifying devices
After you have installed the multipath driver or verified that the multipath driver is already installed,
use the SMdevices utility to identify a storage subsystem logical drive that is associated with an
operating-system device.
Using the SMdevices utility

The SMutil software includes a utility called SMdevices that you can use to view the storage subsystem
logical drive that is associated with a particular operating-system device name. This utility is helpful
when you want to create drive letters or partitions by using Disk Administrator.
Using SMdevices on Windows operating systems

After you create the logical drives on a storage subsystem, go to the host that is attached to that storage
subsystem, and complete the following steps to use SMdevices on Windows:
1. From a DOS or command prompt, change to the directory <installation_directory>\Util,
where installation_directory is the directory in which you installed the SMutil.
The default directory is c:\Program Files\IBM_DS4000\Util.
2. Type SMdevices and press Enter.
120
Using SMdevices on UNIX-type operating systems

You can use SMdevices to map the host-assigned device name for each LUN back to its corresponding
storage-subsystem device. In the SMdevices output, you can view the following storage-subsystem
information, as it is shown on SMclient.
Note: The examples in the list refer to the sample SMdevices output.
v Host assigned name (/dev/sdh)
v DS3000, DS4000, or DS5000 storage subsystem name (DS4500_Storage_Server-A)
v Logical drive name (Raid-5-0A)
v LUN ID (LUN 4)
v Preferred controller owner, and whether that controller is controlling the logical drive
The following example shows a sample SMdevices output for the DS4500_Storage_Server-A storage
subsystem:
# SMdevices
IBM FAStT Storage Manager Devices, Version 09.12.A5.00
Built Fri Jan 14 16:42:15 CST 2005
(C) Copyright International Business Machines Corporation,
2004 Licensed Material - Program Property of IBM. All rights reserved.
/dev/sdh (/dev/sg10) [Storage Subsystem DS4500_Storage_Server-A,
Logical Drive Raid-5-0A, LUN 4, Logical Drive ID
<600a0b80000f0fc300000044412e2dbf>, Preferred Path (Controller-A):
/dev/sdd (/dev/sg6) [Storage Subsystem DS4500_Storage_Server-A,
<600a0b80000f13ec00000016412e2e86>, Preferred Path (Controller-B):
/dev/sde (/dev/sg7) [Storage Subsystem DS4500_Storage_Server-A,
<600a0b80000f0fc30000003c412e2d59>, Preferred Path (Controller-A):
/dev/sdf (/dev/sg8) [Storage Subsystem DS4500_Storage_Server-A,
<600a0b80000f0fc30000003e412e2d79>, Preferred Path (Controller-A):
/dev/sdg (/dev/sg9) [Storage Subsystem DS4500_Storage_Server-A,
<600a0b80000f13ec00000012412e2e4c>, Preferred Path (Controller-A):
In Use]
In Use]
In Use]
In Use]
In Use]
Identifying devices on AIX hosts

The information in this section describes device discovery on AIX. For troubleshooting information about
disk array errors on AIX, see Resolving disk array errors on AIX on page 227 in Chapter 8,
Troubleshooting, on page 205.
Understanding devices on AIX hosts

The multipath driver creates the following devices that represent the storage subsystem configuration:
dar
The disk array router (dar) device represents the entire array, including the current and the
deferred paths to all LUNs (hdisks).
dac
The disk array controller (dac) devices represent a controller within the storage subsystem. There
are two dacs in the storage subsystem. With MPIO, the dac device is shown only if a UTM device
is assigned.
hdisk Each hdisk device represents an individual LUN on the array.

utm
The universal transport mechanism (utm) device is used only with in-band management
configurations, as a communication channel between the SMagent and the storage subsystem.
121
Note: The utm device might be listed in command output, regardless of whether you have an
in-band management configuration. For example, a utm might be listed when you run the lsattr
command on a dac.
Performing the initial device discovery

To perform the initial device discovery, complete the following steps:
1. Make sure that the storage subsystem has been set up, LUNs have been assigned to the host, and the
multipath driver has been installed.
2. Type the following command to probe for the new devices:
# cfgmgr -v
Note: In a SAN configuration, the devices do not log in to the SAN switch until you run the cfgmgr
command.
3. Type the following command:
# lsdev -Cc disk
4. Examine the output of the lsdev -Cc disk command to make sure that the RDAC software recognizes
the storage subsystem logical drives, as shown in the following list:
v
v
v
v
v
Each
Each
Each
Each
Each
DS4200
DS4300
DS4400
DS4500
DS4700
logical
logical
logical
logical
logical
drive
drive
drive
drive
drive
is
is
is
is
is
recognized
recognized
recognized
recognized
recognized
as
as
as
as
as
an
an
an
an
an
1814 DS4200 Disk Array Device.

1722-600 (600) Disk Array Device.
1814 DS4700 Disk Array Device.
v Each DS4800 logical drive is recognized as an 1815 DS4800 Disk Array Device.
Important: You might discover that the configuration process has created two dacs and two dars on
one storage subsystem. This situation can occur when the host is using a partition that does not have
any associated LUNs. When that happens, the system cannot associate the two dacs under the correct
dar. If there are no LUNs, the system generates two dacs as expected, but it also generates two dars.
The following list shows the most common causes:
v You create a partition and attach the LUNs to it, but you do not add the host ports to the partition.
Therefore, the host ports remain in the default partition.
v You replace one or more HBAs but do not update the worldwide name (WWN) of the partition for
the HBA.
v You switch the storage subsystem from one set of HBAs to another as part of a reconfiguration and
do not update the WWNs.
In each of these cases, resolve the problem, and run cfgmgr again. The system removes the extra dar
or moves it from the Available state to the Defined state. (If the system moves the dar into the
Defined state, you can delete it.)
Note: When you perform the initial device identification, the Object Data Manager (ODM) attributes
of each device are updated with default values. In most cases and for most configurations, the default
values are satisfactory. However, there are some values that can be modified for maximum
performance and availability. See Appendix D, Viewing and setting AIX Object Data Manager (ODM)
attributes, on page 261 for information about using the lsattr command to view attribute settings on
an AIX system.
Example of an initial discovery with MPIO

The following example shows an initial discovery with MPIO.
122
# lsdev -C |grep hdisk10

hdisk10
Available 05-08-02
MPIO Other DS4K Array Disk
# lscfg -vpl hdisk10

hdisk10 U787F.001.DPM0H2M-P1-C3-T1-W200400A0B8112AE4-L9000000000000
MPIO Other DS4K Array Disk
Manufacturer................IBM
Machine Type and Model......1814
FAStT
ROS Level and ID............30393136
Serial Number...............
Device Specific.(Z0)........0000053245004032
Device Specific.(Z1)........
# mpio_get_config -A
Storage Subsystem worldwide name: 60ab8001122ae000045f7fe33
Storage Subsystem Name = Kinks-DS-4700
hdisk
LUN #
hdisk2
1
hdisk3
2
hdisk4
3
hdisk5
4
hdisk6
5
hdisk7
6
hdisk8
7
hdisk9
8
hdisk10
9
hdisk11
10
Configuring devices
To maximize your storage subsystem performance, you can set the queue depth for your hdisks, disable
cache mirroring, use dynamic capacity and dynamic logical drive expansion (DVE), and check the size of
your LUNs.
Using the hot_add utility

The hot_add utility enables you to add new logical drives without restarting the system. The utility
registers the new logical drives with the operating system so that you can use Disk Administrator to
create partitions and add device names. The hot_add utility is part of the SMutil software package. If you
run the program twice and the new logical drives are not displayed in the Disk Administrator window,
you must either run Fibre Channel diagnostics or restart the host.
After you create logical drives on a particular storage subsystem, go to the host that is attached to that
storage subsystem and complete the following steps to use the hot_add utility:
1. From a DOS or command prompt, change to the following directory:
<installation_directory>\Util

Note: The default directory is c:\Program Files\IBM_DS4000\Util.
2. From a DOS or command prompt, type the following command:
hot_add
3. Press Enter. The new logical drives are available through the Disk Administrator.
Using the SMrepassist utility

Use the SMrepassist utility to flush cached data for a logical drive.
Important: The FlashCopy drive cannot be added or mapped to the same server that has the base logical
drive of the FlashCopy logical drive in a Windows 2000, Windows Server 2003, Windows Server 2008, or
NetWare environment. You must map the FlashCopy logical drive to another server.
123
To flush cached data in a logical drive, complete the following steps:

1. From a DOS or command prompt, change to the directory
<installation_directory>\Util

Note: The default directory is c:\Program Files\IBM_DS4000\Util.
smrepassist -f logical_drive_letter:
where logical_drive_letter is the operating-system drive letter that was assigned to the disk
partition on the logical drive.
3. Press Enter.
Stopping and restarting the host-agent software

You must stop and restart the host-agent software if you add storage subsystems to the management
domain of the host-agent software. When you restart the service, the host-agent software discovers the
new storage subsystems and adds them to the management domain.
Note: If none of the access logical drives are detected after a restart, the host-agent software stops
running automatically. Make sure that there is a Fibre Channel connection from the host to the SAN to
which the storage subsystem is connected, and restart the host or cluster node so that new
host-agent-managed storage subsystems can be discovered.
Use the applicable procedure in this section for your operating system.
Windows 2000
To stop and restart the host-agent software on Windows 2000, complete the following steps:
1. Click Start > Programs > Administrative Tools > Services. The Services window opens.
2. Right-click IBM DS Storage Manager Agent.
3. Click Restart. The Storage Manager Agent stops and then starts again.
4. Close the Services window.
Windows Server 2003 and 2008

To stop and restart the host-agent software on Windows Server 2003 and 2008, complete the following
steps:
1. Click Start > Administrative Tools > Services. The Services window opens.
2. Right-click IBM DS Storage Manager Agent.
3. Click Restart. The Storage Manager Agent stops and then starts again.
4. Close the Services window.
Setting the queue depth for hdisk devices

Setting the queue_depth attribute to the appropriate value is important for optimal system performance.
Use this setting if you have a large storage-subsystem configuration with many attached logical drives
and hosts.
This section provides methods for calculating maximum queue depth, which you can use as a guideline
to help you determine the best queue-depth setting for your configuration.
124
Calculating maximum queue depth

The formula for calculating the maximum queue depth for your system depends on which firmware
version is installed on the controller. Use one of the following formulas to calculate the maximum queue
depth for your system.
Important:
1. The maximum queue depth might not be an optimal setting in all cases. Use the maximum queue
depth as a guideline, and adjust the setting as necessary for your specific configuration.
2. In systems with one or more attached SATA devices, you might have to set the queue_depth attribute
to a lower value than the maximum queue depth.
Formulas for controller firmware version 07.10.xx.xx and later

On DS4800 and DS4700 or DS4200 storage systems that are running storage subsystem controller
firmware version 07.10.xx.xx or later, use the following formulas to determine the maximum queue
depth:
DS4800: 4096 / (number-of-hosts * LUNs-per-host ). For example, a DS4800 system with four hosts,
each with 32 LUNs, would have a maximum queue depth of 32: 4096 / ( 4 * 32 ) = 32.
DS4700 or DS4200: 2048 / (number-of-hosts * LUNs-per-host ). For example, a DS4700 system or a
DS4200 system with four hosts, either with 32 LUNs, would have a maximum queue depth of 16: 2048 /
( 4 * 32 ) = 16.
Formula for controller firmware versions 05.4x.xx.xx, or 06.1x.xx.xx to 06.6x.xx.xx

On DS4000 or DS5000 storage systems that are running storage subsystem controller firmware versions
05.4x.xx.xx, or 06.1x.xx.xx to 06.6x.xx.xx, use the following formula to determine the maximum queue
depth: 2048 / (number-of-hosts * LUNs-per-host ). For example, a system with four hosts, each with 32
LUNs, would have a maximum queue depth of 16: 2048 / ( 4 * 32 ) = 16.
Formula for controller firmware version 05.30.xx.xx

On DS4000 or DS5000 storage systems that are running storage subsystem controller firmware version
05.30.xx.xx or earlier, use the following formula to determine the maximum queue depth: 512 /
(number-of-hosts * LUNs-per-host ). For example, a system with four hosts, each with 32 LUNs, would
have a maximum queue depth of 4: 512 / ( 4 * 32 ) = 4.
Changing the queue depth for Windows

You can use the QLogic SANsurfer program to modify the Host Adapter Settings and Advanced Adapter
Settings preferences from the Windows operating-system environment. However, you must restart the
servers for the changes to take effect.
Alternatively, to change the queue-depth setting for a QLogic adapter in a Microsoft Windows
operating-system environment, you must select the Configuration Settings menu in Fast!UTIL and then
select Advanced Adapter Settings to access the Execution Throttle.
Changing the queue depth for AIX

You can change the queue_depth attribute for AIX with the chdev -l command, as shown in the following
example.
# chdev -l hdiskX -a queue_depth=y -P
where X is the name of the hdisk and y is the queue-depth setting.

Note: Use the -P flag to make the changes permanent in the Customized Devices object class.
125
Disabling cache mirroring

Attention: If you disable cache mirroring and a controller fails or power to a controller is turned off,
you might lose data. Back up all data before you disable cache mirroring.
To disable cache mirroring in Storage Manager, complete the following steps:
1. On the Logical or Physical tab of the Subsystem Management window, right-click the logical drive on
which you want to disable cache mirroring, and select Change > Cache Settings.
2. In the Change Cache Settings window, clear the Enable write caching with mirroring check box.
3. Click OK.
Note: For AIX operating systems, when a LUN is opened that is running with write cache enabled and
cache mirroring disabled, an FCP array warning message is displayed. The warning is displayed again
every 24 hours until cache mirroring is enabled again.
Using dynamic capacity expansion and dynamic logical drive

expansion
Dynamic logical drive expansion (DVE) increases the size of a logical drive. For you to perform a DVE,
free capacity must be available in the array. If there is not, you can perform a dynamic capacity
expansion (DCE) to increase the array capacity by adding drives. After you make sure that there is
sufficient free capacity within the array, you can perform a DVE operation.
Performing a dynamic capacity expansion

To increase the capacity on the array, complete the following steps to perform a DCE.
Note: For more information about this procedure, see the Storage Manager online help.
1. On the Logical or Physical tab of the Subsystem Management window, right-click an array and select
Add Free Capacity (Drives).
2. In the Add Free Capacity (Drives) window, select one or two available drives and click Add.
Performing a dynamic logical drive expansion

Before you perform a Dynamic Logical Drive Expansion(DVE), make sure that there is available free
capacity in the array. Check the Logical or Physical tab of the Subsystem Management window to check
the amount of available free capacity. If there is not enough free capacity and extra drives are available,
you can add one or more drives to the array by performing a dynamic capacity expansion (DCE)
operation before you perform the DVE operation.
Note:
1. You cannot resize the logical drive while the array is activated in classic or enhanced concurrent
mode.
2. You cannot resize the root array.
To increase the size of a logical drive, complete the following steps to perform a DVE.
Note: For more information about this procedure, see the Storage Manager online help.
1. From the Logical or Physical tab of the Subsystem Management window, right-click the logical drive
and select Increase Capacity. The Increase Logical Drive Capacity Additional Instructions window
opens.
2. Read the additional instructions and click OK. The Increase Logical Drive Capacity window opens.
126
3. Type the amount by which you want to increase the logical drive, and click OK. A clock icon is
displayed on every logical drive within the array. You must wait for the process to be completed
before you can begin any host intervention.
Note: If the storage subsystem is busy, the process might take several hours.
4. Type the following commands to rescan the logical drive on the host:
# cd /sys/block/sdXX/device
# echo 1 > rescan
where XX is the device name.

5. Check the size of the logical drive, using the procedure that is described in Checking LUN size on
page 128.
6. Remount the logical drive.
Veritas Storage Foundation with SUSE Linux Enterprise Server

Boot time is sometimes increased by LVM scanning, and Veritas Storage Foundation environment does
not require an LVM scan. Therefore, the LVM scan with SLES 10 SP2 or later must be disabled. Use the
following procedure to disable the LVM scan.
Note:
v In the Veritas Storage Foundation Linux environment, the default host type must be set to 13
(LNXCLVMWARE or LNXCLUSTER depending on the controller firmware version).
v IBM supports the DMP A/P-F ASL/APM only, not the A/P-C ASL.
v During boot, before DMP is loaded, I/O probes that go to the non-owning controller generate timeout
errors. These boot-time errors are unavoidable and not significant.
1. In the file /etc/lvm/lvm.conf, change the line filter = [ "a/.*/" ] to filter = [ "r|/dev/.*/by-path/
.*|", "r|/dev/.*/by-id/.*|", "r|/dev/sd.*|", "a/.*/" ].
2. If the root/swap is in an LVM volume, complete the following tasks:
v Add your specific device to the filter in step 1 to make sure that the appropriate volumes are
scanned.
v After you complete step 1, run mkinitrd and use the new initrd image for future boots.
Veritas Storage Foundation 5.0 with Red Hat Enterprise Linux

The following procedure is required to enable the RDAC module on RHEL 5.3 for Storage Foundation 5.0
only. The module is integrated in Storage Foundation 5.1 and later. The scsi_dh_RDAC module provides
the support for RDAC devices. It eliminates the time delay and some of the error messages during the
boot or probe process.
Note:
1. In the Veritas Storage Foundation Linux environment, the default host type must be set to 13
(LNXCLVMWARE or LNXCLUSTER depending on the controller firmware version).
2. IBM supports the DMP A/P-F ASL/APM only, not the A/P-C ASL.
3. During boot, before DMP is loaded, I/O probes that go to the non-owning controller generate timeout
errors. These boot-time errors are unavoidable and not significant.
4. The following procedure works with the IBM NVSRAM because the scsi_dh_RDAC module is
VID/PID-dependent.
Enabling the RDAC module on RHEL 5.3 for Storage Foundation 5.0
To enable the RDAC module on RHEL 5.3 for Storage Foundation 5.0, complete the following steps:
1. Disable all of the storage subsystem storage ports so that the HBA cannot detect them.
2. Install Storage Foundation.
127
3. Run mkinitrd to include the scsi_dh_rdac module:

mkinitrd $resultant_initrd_image_file $kernel_version --preload=scsi_dh_rdac
For example:
mkinitrd /boot/my_image 2.6.18-118.el5 --preload=scsi_dh_rdac
4.
5.
6.
7.
Note: The uname -r command gives the kernel version.

Change the boot loader to use the new initrd image. For IBM i and System p servers, the initrd
image name is yaboot. For System x servers, the image name is grub.
Shut down the host server.
Enable the storage subsystem so that the HBA recognizes the storage configuration.
Start the host server.
Unloading the RDAC module on RHEL 5.3 for Storage Foundation 5.0
To unload the module after the device probe and attach process, complete the following steps during the
system-boot process:
1. Create a /etc/r3.d script, as in the following example:
# vi /etc/init.d/rm_rdac
----------------------------------------------------------------------------------------## this script is used for detaching the scsi_dh_rdac module for each LUN
## this script has dependency on lsscsi command and this lsscsi should be available for this
## script to successfully execute.
#!/bin/bash
echo "detaching the scsi_dh_rdac module"
for i in /sys/block/sd*/device/dh_state
do
if [[ "`cat $i`" = "rdac" ]]
then
echo detach > $i
fi
done
modprobe -r scsi_dh_rdac
echo "detached successfully"
-----------------------------------------------------------------------------------------
2. Insert the script at the correct location under /etc/rc3.d, before the VCS VxFen Driver startup script
(the VxFen Driver default start script is /etc/rc2.d/S68vxfen). If the system is not running VCS,
insert the script after the /etc/rc3.d/S50vxvm-recover script.
# ln -s /etc/init.d/rm_rdac /etc/rc.d/rc3.d/S57rm_rdac
# ln -s /etc/init.d/rm_rdac /etc/rc.d/rc5.d/S57rm_rdac
Checking LUN size

To check the size of a LUN in AIX, complete the following steps:
1. Type the following commands:
#cd /sys/block/sdXX
# cat size
where XX is the device name. A number is displayed, as in the following example:

8388608
2. Multiply this number by 512 (bytes) to calculate the size of the LUN, as shown in the following
example:
8388608 * 512 = 4294967296 (~ 4GB)
In the example, the LUN size is approximately 4 GB.
128
Redistributing logical drives

In a failover condition where logical drives have failed over to their secondary controller path, some
configurations require a manual intervention to move these drives back after the error has been resolved.
The need for this intervention depends on the host multipath driver that is installed and whether ADT
(Auto Drive Transfer) is enabled. By default, ADT is disabled in AIX and Windows, but their multipath
drivers can automatically recover. By default, ADT is enabled in Linux, but the MPP driver can do the
same automatic recover; ADT must be disabled if you use that driver.
To redistribute logical drives manually to their preferred paths in the Subsystem Management window,
click Advanced > Recovery > Redistribute Logical Drives.
To redistribute logical drives on AIX, HP-UX, or Solaris, complete the applicable procedure in this section.
Redistributing logical drives on AIX

If you enabled autorecovery on the AIX host, you do not have to redistribute logical drives manually
after a controller failover. However, if you have a heterogeneous host environment, you might have to
redistribute logical drives manually. Hosts that do not support some form of autorecovery, or AIX hosts
in which autorecovery is disabled, do not automatically redirect logical drives to the preferred paths.
For troubleshooting information about disk array errors on AIX, see Resolving disk array errors on AIX
on page 227 in Chapter 8, Troubleshooting, on page 205.
Complete the following steps to manually redistribute logical drives to their paths:
1. Repair or replace any faulty components. For more information, see the Installation, User's, and
Maintenance Guide that came with the storage subsystem.
2. In the Subsystem Management window, click Advanced > Recovery > Redistribute Logical Drives to
redistribute logical drives to their preferred paths.
Note: If a large number of LUNs are configured on the storage subsystem, the redistribution of the
logical drives might take 60 minutes or longer.
3. Run the fget_config command to verify the active paths, as shown in the following example.
# fget_config -l dar0
dac0 ACTIVE dac1 ACTIVE
dac0-hdisk1
dac0-hdisk2
dac0-hdisk3
dac1-hdisk4
dac1-hdisk5
dac1-hdisk6
dac1-hdisk7
dac0-hdisk8
Redistributing logical drives on HP-UX

Auto Drive Transfer (ADT) is enabled, by default, on HP-UX hosts. If a failure occurs that initiates a
controller failover, ADT redirects I/O to the available controller. ADT does not require manual
redistribution.
Important: If a failure occurs in a heterogeneous host environment, the HP-UX host with ADT enabled
automatically redistributes its LUNs when the path becomes available. However, you must redistribute
logical drives manually on any host in which ADT is not enabled. Failure to do so leaves the storage
subsystem in a Needs Attention state, because hosts that do not support ADT and hosts in which ADT is
disabled do not automatically redirect I/O to the preferred controller. In this case, the Storage Manager
Recovery Guru indicate which host platform is associated with the LUN that is in a failover state.
129
Note: DS5000 storage subsystems are not ALUA-compliant. DS5000 subsystems have Target Port Group
Support (TPGS), which is a similar SCSI protocol that directs I/O to preferred ports. For HP-UX 11.31, the
default HP-UX host type must be changed to the TPGS host type HPXTPGS.
To
1.
2.
3.
turn on TPGS support and change the host type, complete the following steps:
Change the operating-system type for the DS5000 storage subsystem from HPUX to HPXTPGS.
Change the load balancing to Default, round-robin.
Verify that the changes are correct. The following example shows one of the LUNs that has the correct
four active paths and four standby paths.
# scsimgr get_info all_lpt -D /dev/rdisk/asm1ai|grep -e STATUS -e Open close state
STATUS INFORMATION
Open close state
STATUS INFORMATION
Open close state
STATUS INFORMATION
Open close state
STATUS INFORMATION
Open close state
STATUS INFORMATION
Open close state
STATUS INFORMATION
Open close state
STATUS INFORMATION
Open close state
STATUS INFORMATION
Open close state
FOR LUN PATH : lunpath306

= ACTIVE
= STANDBY
= STANDBY
= ACTIVE
= ACTIVE
= ACTIVE
= STANDBY
= STANDBY
4. Use the SAN Fibre Channel switch-monitoring tools to verify that the I/O loads are distributed
properly.
Redistributing logical drives on Solaris

If you select Solaris as the host type when you define the host and host port, Auto Drive Transfer (ADT)
is disabled on Solaris hosts. In this case, if a failure occurs that initiates a controller failover, you must
redistribute logical drives to their preferred paths manually.
To redistribute logical drives to their preferred paths manually, complete the following steps:
1. Repair or replace any faulty components. For more information, see the Installation, User's and
Maintenance Guide that came with the storage subsystem.
2. In the Subsystem Management window, click Advanced > Recovery > Redistribute Logical Drives to
redistribute logical drives to their preferred paths.
Replacing hot-swap HBAs

Attention: If you do not follow this procedure as it is documented here, data availability might be lost.
You must read and understand all of the steps in this section before you begin the HBA hot-swap
procedure.
This section describes the procedure for hot-swapping Fibre Channel host bus adapters (HBAs) on a
System p server.
The following list provides an overview of this section:
v Replacing hot-swap HBAs on AIX on page 131
v Replacing IBM HBAs on Linux on page 134
v Replacing a PCI hotplug HBA on page 137
v Mapping the new WWPN to the storage subsystem for AIX and Linux on page 138
v Completing the HBA hot-swap procedure on page 138
130
Replacing hot-swap HBAs on AIX

Attention:
Any deviations from these notes and procedures might cause a loss of data availability.
Review the following list of issues and restrictions before you perform a hot-swap operation for AIX.
v The autorecovery attribute of the dar must be set to no. Autorecovery is a dynamically set feature that
can be turned back on after the hot-swap procedure is complete. Failure to disable autorecovery mode
during a hot-swap procedure can cause loss of access to data.
v Do not redistribute logical drives to the preferred path until you verify that the HBA replacement
succeeded and that the subsequent configuration was performed correctly. If you redistribute the
logical drives before you verify that the hot swap and configuration were successful can cause a loss of
access to data.
v The only supported hot-swap scenario involves the replacement of a defective HBA with the same
HBA model, and in the same PCI slot. Do not insert the defective HBA into any other system, even if
the HBA is found not to be defective. Always return the HBA to IBM.
Important: As of the date of this document, no other variations of replacement scenarios are
supported.
v Hot swap is not supported in single-HBA configurations.
Preparing for the HBA hot swap on AIX:
To prepare for the hot swap, complete the following procedures:
Collecting system data
To collect data from the system, complete the following steps:
# lsdev -C |grep fcs
The output is similar to the following example.

fcs0
fcs1
Available 17-08
Available 1A-08
FC Adapter
FC Adapter

# lsdev -C |grep dac
The output is similar to the following example.

dac0
dac1
Available 17-08-02
Available 1A-08-02
1815
1815
DS4800 Disk Array Controller

DS4800 Disk Array Controller
3. Type the following command for each of the fcs devices:

# lscfg -vpl fcsX
where X is the number of the fcs device. The output looks similar to the following example.
lscfg -vpl fcs0
fcs0
U0.1-P1-I1/Q1
FC Adapter
Part Number.................09P5079
EC Level....................A
Serial Number...............1C21908D10
Manufacturer................001C
Feature Code/Marketing ID...2765
FRU Number..................09P5080
Network Address.............10000000C92D2981
ROS Level and ID............02C03951
Device Specific.(Z0)........2002606D
Device Specific.(Z1)........00000000
131
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Specific.(Z2)........00000000
Specific.(Z3)........03000909
Specific.(Z4)........FF401210
Specific.(Z5)........02C03951
Specific.(Z6)........06433951
Specific.(Z7)........07433951
Specific.(Z8)........20000000C92D2981
Specific.(Z9)........CS3.91A1
Specific.(ZA)........C1D3.91A1
Specific.(ZB)........C2D3.91A1
Specific.(YL)........U0.1-P1-I1/Q1
PLATFORM SPECIFIC
Name: Fibre Channel
Model: LP9002
Node: Fibre Channel@1
Device Type: fcp
Physical Location: U0.1-P1-I1/Q1

# lsdev -C |grep dar
The output looks similar to the following example.

# dar0
dar1
Available
Available
1815
1815
DS4800 Disk Array Router

DS4800 Disk Array Router
5. Type the following command to list the attributes of each dar found on the system:
# lsattr -El darX
where X is the number of the dar. The output looks similar to the following example.
lsattr -El dar0
act_controller
all_controller
held_in_reset
load_balancing
autorecovery
hlthchk_freq
aen_freq
balance_freq
fast_write_ok
cache_size
switch_retries
dac0,dac2
dac0,dac2
none
no
no
600
600
600
yes
1024
5
Active Controllers
Available Controllers
Held-in-reset controller
Dynamic Load Balancing
Autorecover after failure is corrected
Health check frequency in seconds
Polled AEN frequency in seconds
Dynamic Load Balancing frequency in seconds
Fast Write available
Cache size for both controllers
Number of times to retry failed switches
False
False
True
True
True
True
True
True
False
False
True
Verifying that autorecovery is disabled

Before you perform the hot swap, complete the following steps to make sure that autorecovery is
disabled on every dar that is involved with the HBA that you want to hot swap:
1. Type the following command to identify all of the dacs that are involved with the HBA:
# lsdev -C|grep 11-08

# lsdev -C|grep 11-08
fcs0
Available 11-08
fscsi0
Available 11-08-01
dac0
Available 11-08-01
hdisk1
Available 11-08-01
hdisk3
Available 11-08-01
hdisk5
Available 11-08-01
hdisk7
Available 11-08-01
hdisk8
Available 11-08-01
132
FC Adapter
FC SCSI I/O Controller Protocol Device
1742
(700) Disk Array Controller
1742
(700) Disk Array Device
1742
1742
1742
1742
2. Check the lsattr command output that you collected in step 5 of the procedure Collecting system
data on page 131. In the lsattr output, identify the dars that list the dacs that you identified in step
1 of this procedure.
3. Type the following command for each dar that you identified in step 2:
#
lsattr -El darX |grep autorecovery
where X is the number of the dar. The output looks similar to the following example.
# lsattr -El dar0 |grep autorecovery
autorecovery
no
True
4. In the lsattr command output, verify that the second word is no. If the second word is yes,
autorecovery is currently enabled.
Important: For each dar on which autorecovery is enabled, you must disable it by setting the
autorecovery ODM attribute to no. See Using the lsattr command to view ODM attributes on page
265 to learn how to change attribute settings. Do not proceed with the hot-swap procedure until you
complete this step and verify that autorecovery is disabled.
Replacing the hot-swap HBA:
Attention: If you do not follow this procedure as documented here, data availability might be lost. You
must read and understand all of the steps in this section before you begin the HBA hot-swap procedure.
To replace the hot-swap HBA, complete the following steps:
1. Type the following command to put the HBA that you want to replace into the Defined state:
# rmdev -Rl fcsX
where X is the number of the HBA. The output is similar to the following example.
rmdev -Rl fcs0
fcnet0 Defined
dac0 Defined
fscsi0 Defined
fcs0 Defined
For Linux operating systems, type the following command to identify the PCI hotplug slot:
# drslot_chrp_pci -i -s
slot-name
where slot-name is the name of the slot for the HBA that you are replacing, for example,
U7879.001.DQD014E-P1-C3.
The LED at slot slot-name flashes, and the following message is displayed.
The visual indicator for the specified
PCI slot has been set to the identify
state. Press Enter to continue or
enter x to exit.
2. In the AIX smit menu, initiate the process that is required for the HBA hot swap by clicking smit >
Devices > PC Hot Plug Manager > Replace/Remove a PCI Hot Plug Adapter.
3. In the Replace/Remove a PCI Hot Plug Adapter window, select the targeted HBA. A window opens
and displays instructions for replacing the HBA.
4. Follow the smit instructions to replace the HBA.
Note: Do not reinstall the Fibre Channel cable at this time.
5. If the steps in this procedure are completed successfully up to this point, you get the following
results:
v The defective HBA is removed from the system.
v The replacement FC HBA is turned on.
133
v The associated fcsX device is in the Defined state.

Before you continue, verify that these results have been obtained.
6. Install the Fibre Channel loop on the replacement HBA.
7. Type the following command to put the HBA into the Active state:
# cfgmgr
Note: The new HBA is placed in the default group. If hdisks are assigned to the default group, the
HBA generates a new dar and dac, which causes a split. Issue the rmdev command to remove the
new dar and dac after you map the WWPN.
8. Type the following command to verify that the fcs device is now available:
9. Type the following command to verify or upgrade the firmware on the replacement HBA to the
correct level:
# lscfg -vpl fcsX
where X is the number of the fcs.

10. Record the 16-digit number that is associated with Network Address, as it was displayed in the
output of the command that you used in step 9. This network address number is used in the next
procedure, Mapping the new WWPN to the storage subsystem for AIX and Linux on page 138.
11. Type the following command to put the HBA back into the Defined state:
# rmdev -Rl fcsX
After you complete this procedure, continue to Mapping the new WWPN to the storage subsystem for
AIX and Linux on page 138.
Replacing IBM HBAs on Linux

This section provides requirements and procedures for replacing IBM host bus adapters in System p
servers, using PCI hotplug tools.
Preparing for the IBM HBA hot swap on Linux: To prepare for the hot swap, complete the following
procedures:
Verifying the PCI hotplug tools
Make sure that the following tools are installed in the /usr/sbin directory:
v
v
lsslot
drslot_chrp_pci
If these tools are not installed, complete the following steps to install them:
1. Make sure that rdist-6.1.5-792.1 and compat-2004.7.1-1.2 are installed from the SLES 9 media.
2. To find the PCI Hotplug Tools rpm files, go to http://www14.software.ibm.com/webapp/set2/sas/f/
lopdiags/.
3. On the website, select the applicable link for your operating system. Download and install the
following rpm files:
v librtas-1.3.1-0.ppc64.rpm
v rpa-pci-hotplug-1.0-29.ppc64.rpm
4. Type the following command to install each rpm file:
# rpm -Uvh <filename>.rpm
where <filename> is the name of the rpm file.
134
Verifying that the PCI core is installed

The PCI core must be installed on the system. Type the following command to verify that it is installed:
# ls -l /sys/bus/pci/slots
If the PCI core is installed, the output looks similar to the following example:
elm17c224:/usr/sbin # ls -l /sys/bus/pci/slots
total 0
drwxr-xr-x 8 root root 0 Sep 6 04:29 .
drwxr-xr-x 5 root root 0 Sep 6 04:29 ..
drwxr-xr-x 2 root root 0 Sep 6 04:29 0000:00:02.0
drwxr-xr-x 2 root root 0 Sep 6 04:29 control
If the /sys/bus/pci/slots directory does not exist, the PCI core is not installed.
Verifying that the rpaphp driver is installed
The rpaphp driver must be installed on the system. Type the following command to verify that it is
installed:
ls -l /sys/bus/pci/slots/*
If the rpaphp driver is installed, the output looks similar to the following example:
elm17c224:/usr/sbin # ls -l /sys/bus/pci/slots/*
/sys/bus/pci/slots/0000:00:02.0:
total 0
drwxr-xr-x 2 root root
0 Sep 6 04:29 .
drwxr-xr-x 8 root root
0 Sep 6 04:29 ..
-r--r--r-- 1 root root 4096 Sep 6 04:29 adapter
-rw-r--r-- 1 root root 4096 Sep 6 04:29 attention
-r--r--r-- 1 root root 4096 Sep 6 04:29 max_bus_speed
-r--r--r-- 1 root root 4096 Sep 6 04:29 phy_location
-rw-r--r-- 1 root root 4096 Sep 6 04:29 power
Using the lsslot tool to list slot information: Before you replace an HBA by using PCI hotplug, you can
use the lsslot tool to list information about the I/O slots. This section describes how to use lsslot and
provides examples. Use the lsslot tool according to the following guidelines.
Syntax for the lsslot tool
The lsslot syntax is shown in the following example.
lsslot [ -c slot | -c pci [ -a | -o]] [ -s drc-name ] [ -F delimiter ]
Options for the lsslot tool

The lsslot options are shown in the following list:
No options
Displays all DR slots
-c slot Displays all DR slots
-c pci
Displays all PCI hotplug slots
-c pci -a
Displays all available (empty) PCI hotplug slots
135
-c pci -o
Displays all occupied PCI hotplug slots
Uses delimiter to delimit columns
-F
Listing PCI hotplug slots with the lsslot command

This section shows the command lines that you can use to list all PCI hotplug slots, all empty PCI
hotplug slots, or all occupied PCI hotplug slots. You can also view detailed information about a PCI
hotplug device.
Note: In the Device(s) columns of the command-line outputs, the PCI devices in the slots are listed in the
following format: xxxx:yy:zz.t (for example, 0001:58:01.1).
Type the following command to list all PCI hotplug slots:
# lsslot -c pci -a
The resulting output looks similar to the following example.

# Slot
Description
U7879.001.DQD014E-P1-C1 PCI-X capable,
0001:58:01.1
64
64
64
64
64
64
bit,
bit,
bit,
bit,
bit,
bit,
133MHz
133MHz
133MHz
133MHz
133MHz
133MHz
slot
slot
slot
slot
slot
slot
Device(s)
Empty
0002:58:01.0
0001:40:01.0
Empty
Empty
0001:58:01.0
Type the following command to list all empty PCI hotplug slots:
# lsslot -c pci -a

# Slot
Description
U7879.001.DQD014E-P1-C1 PCI-X capable, 64 bit, 133MHz slot
Device(s)
Empty
Empty
Empty
Type the following command to list all occupied PCI hotplug slots:
# lsslot -c pci -o

# Slot
Description
0001:58:01.1
Device(s)
0002:58:01.0
0001:40:01.0
0001:58:01.0
To see detailed information about a PCI hotplug device, complete the following steps:
1. Select a device number from the output of # lsslot -c pci -o, as seen in the preceding output
example.
2. Type the following command to show detailed information about the device:
# lspci | grep xxxx:yy:zz.t
where xxxx:yy:zz.t is the number of the PCI hotplug device. The resulting output looks similar to
the following example.
0001:40:01.0 Ethernet controller: Intel Corp. 82545EM Gigabit
Ethernet Controller (Copper) (rev 01)
136
Replacing a PCI hotplug HBA

Complete the following procedures to replace a PCI hotplug HBA by using the drslot_chrp_pci
command.
Attention: Before you remove the HBA, you must remove the Fibre Channel cable that is attached to the
HBA. The Fibre Channel cable must remain unattached for at least 5 minutes to make sure that all I/O
activity is transferred to the alternate path. Failure to remove the Fibre Channel cable can cause
unwanted results.
Note: In these procedures, the variable slot-name refers to the slot that contains the HBA that you are
replacing.
1. Type the following command to identify the PCI hotplug slot:
# drslot_chrp_pci -i -s
slot-name
where slot-name is the name of the slot for the HBA that you are replacing, for example,
U7879.001.DQD014E-P1-C3.
The LED at slot slot-name begins flashing, and the following message is displayed.
enter x to exit.
2. Hot unplug, or remove, the HBA from the slot:

a. Remove the Fibre Channel cable that is connected to the HBA, and wait for failover to be
completed.
b. After failover is complete, type the following command:
# drslot_chrp_pci -r -s
slot-name
The following message is displayed.

enter x to exit.
c. Press Enter. The following message is displayed.

PCI slot has been set to the action state.
Remove the PCI card from the identified slot
and press Enter to continue.
d. Press Enter.
e. Physically remove the HBA from the slot.
f. Type the following command to verify that the slot is empty:
# lsslot -c pci -s
slot-name
If the slot is empty, the resulting output looks similar to the following example.
# Slot
Description
Device(s)
Empty
3. To hot plug the HBA into the slot, complete the following steps:
a. Type the following command:
# drslot_chrp_pci -a -s
slot-name
The following message is displayed.

enter x to exit.
137
b. Press Enter. The following message is displayed.

PCI slot has been set to the action state.
Insert the PCI card into the identified slot,
connect any devices to be configured
and press Enter to continue. Enter x to exit.
c. Insert the new HBA into the slot.

d. Type the following command to verify that the slot is no longer empty:
# lsslot -c pci -s
slot-name
If the slot is not empty, the resulting output looks similar to the following example.
# Slot
Description
Device(s)
0001:40:01.0
Mapping the new WWPN to the storage subsystem for AIX and Linux
For each storage subsystem that is affected by the hot swap, complete the following steps to map the
worldwide port name (WWPN) of the HBA to the storage subsystem:
1. Start the Storage Manager and open the Subsystem Management window.
2. On the Mappings tab of the Subsystem Management window, click Mappings > Show All Host Port
Information. The Host Port Information window opens.
3. Find the entry in the Host Port Information window that matches the WWPN of the defective HBA
(the HBA that you removed), and record the alias name. Then, close the Host Port Information
window.
4. On the Mappings tab, select the alias name of the HBA host port that you just recorded.
5. Click Mappings > Replace Host Port. The Replace Host Port window opens.
6. In the Replace Host Port window, verify that the current HBA Host Port Identifier, which is listed at
the top of the window, matches the WWPN of the HBA that you removed.
7. Type the 16-digit WWPN, without the colon (:), of the replacement HBA in the New Identifier field,
and click OK.
After you complete these steps, continue to Completing the HBA hot-swap procedure.
Completing the HBA hot-swap procedure

To finish the HBA hot-swap procedure, complete the applicable procedure in this section for either AIX or
Linux.
Completing the HBA hot-swap procedure on AIX

1. Remove the Fibre Channel loopback plug, and insert the Fibre Channel cable that was previously
attached to the HBA that you removed.
Note: Skip the following step if the HBA is directly attached to the storage subsystem or if the Fibre
Channel switch zoning is based on port numbers instead of WWPNs. If you do have to modify the
zoning, failure to correctly do so will prevent the HBA from accessing the storage subsystem.
2. If an HBA is attached to a Fibre Channel switch and the zoning is based on WWPN, modify the
zoning information to replace the WWPN of the former HBA with the WWPN of the replacement
HBA.
Note: Skip the following step if the HBA is directly attached to the storage subsystem or if the Fibre
Channel switch zoning is based on port numbers instead of WWPNs. If you do have to modify the
zoning, failure to correctly do so will prevent the HBA from accessing the storage subsystem.
138
HBA.
5. Run the cfgmgr command to enable the HBA to register its WWPN in the Fibre Channel switch.
6. Type the following commands to verify that the replaced fcsX device and its associated dacs are
placed in the Available state:
lsdev -C |grep dac
7. Type the following command to verify that no additional dars have been created and that the
expected dars are in the Available state.
Note: With MPIO, the only time you have a dac device is when the UTM LUN is assigned.
# lsdev -C |grep dar
Attention: The presence of additional dars in the lsdev output indicates a configuration problem. If
this occurs, do not continue this procedure until you correct the problem. Otherwise, data
availability might be lost.
8. For each dar, type the following command to verify that affected dar attributes indicate the presence
of two active dacs:
# lsattr -El darX|grep act_controller
where X is the number of the dar.

lsattr -El dar0|grep act_controller
act_controller dac0,dac2 Active Controllers
False
Attention: If two dacs are not reported for each affected dar, data availability might be lost. Do not
continue this procedure if two dacs are not reported for each dar. Correct the problem before you
continue.
9. Redistribute volumes manually to preferred paths.
10. Verify that disks stay on the preferred path with one or both of the following methods:
Using the AIX system
Run the mpio_get_config -Av command, and verify that drives are on the expected path.
Using Storage Manager
In the Enterprise Management window, verify that the storage subsystems are in Optimal
state. If they are not in Optimal state, make sure that any drives that are part of the
subsystems that are involved with the hot-swap process are not listed in the Recovery Guru.
11. If necessary, enable autorecovery of the affected dars. See Appendix D, Viewing and setting AIX
Object Data Manager (ODM) attributes, on page 261 to learn how to change attribute settings.
The Fibre Channel HBA hot swap is now complete.
Completing the HBA hot-swap procedure on Linux

HBA.
Note: Skip this step if the HBA is directly attached to the storage subsystem or if the Fibre Channel
switch zoning is based on port numbers instead of WWPNs. If you do have to modify the zoning,
failure to correctly do so will prevent the HBA from accessing the storage subsystem.
139
3. If RDAC is installed, type the following command to recognize the new HBA:
# mppBusRescan
The Fibre Channel HBA hot swap is now complete.
Setting up details on the DS5000 storage system and AIX host to

support T10PI
You must set up your DS5000 storage system and AIX host to support T10PI functionality from the AIX
host to the drives in the DS5000 storage subsystem using these steps.
Set up the DS5K storage box

1. Upgrade the DS5000 storage system with the firmware that supports T10PI.
2. Create and export logical unit numbers (LUNs) that support T10PI.
Note: To perform this step, you must have disks that support T10PI. These disks are generally
pre-initialized to 520-byte blocks. See T10PI capable drive attributes on page 54 for more
information.
Set up the AIX host

Note: You should use SSIC to check for supported HBAs, HBA driver and firmware version, and your
AIX operating version, along with any applicable patches.
1. Install the AIX 61 TL6 SP5 or AIX 71 TL0 SP3. The AIX machine should have at least one 8Gb PCIe
FC adapter (feature code 5735 or 5273) with the latest firmware that supports T10PI. It should at least
have version df1000f114108a03.200305. The AIX diag utility can be used to download 8Gb PCIe FC
adapter (feature code 5735 or 5273) firmware.
v The 2 port 8Gb PCIe Fibre Channel Adapted must be used.
v 200307 level of firmware or higher is required.
v Feature code 5735 or low profile feature code 5273 required.
v No support on Power Blades.
v To download the adapter firmware, use the diag -T download -d fcs# command, where # is the fcs
device number
v To find the current firmware version on the Coho adapter, use the lsmcode -cd fcs# or lscfg -vl
fcs# commands
2. Enable protection on the 8Gb PCIe FC adapter (feature code 5735 or 5273) (DIF_enabled attribute of
fcs device).
v To enable protection on FC adapter, use the chdev -l fcs# -a DIF_enabled=yes command can be
used.
v You can also use the smit fcsa command can also be used to enable/disable protection on fcs#
Note: To disable protection on FC adapter, use the chdev -l fcs# -a DIF_enabled=no.
3. Ensure that you update the firmware as specified in step 1 and perform step 2 on all the 8Gb PCIe FC
adapters (feature code 5735 or 5273) from which the disk has paths.
a. Use the lspath -l hdisk# command to find the FC adapters in the paths of a disk. This will show
the fscsi# devices (FC protocol devices).
b. Use the lsdev -l fscsi# -F'name parent' command to find the parent of an fscsi# device.
c. Enable protection.
4. Use the chdev -l hdisk# -a DIF_protection=yes command to enable T10 protection on a disk. The
disk must support "Type 1" T10 protection.
140
Note: You can also use the smit disk command to enable/disable protection on hdisk#.
Note: You can use the chdev -l hdisk# -a DIF_protection=no command to disable T10 protection on
a disk.
5. Use the lsattr -El hdisk# command to check the current value of this attribute after enabling
protection. If at least one path does not support protection, then protection can't be enabled on the
disk. If this attribute has a values of "unsupported," it means that:
v some or all paths to disk won't support protection OR
v the disk does not support protection
hdisk2 has three paths. These three paths are from fcs0, fcs2 and fcs3. You want to enable protection on
these adapters. To do this:
1. Upgrade the firmware on all the fcs devices mentioned above. All of them must be 8Gb PCIe FC
adapters (feature code 5735 or 5273).
2. Un-configure the child devices (fscsi0, fscsi2 and fscsi3).
3. Enable protection on fcs0, fcs2 and fcs3 adapters using the chdev command (chdev -l fcs0 -a
DIF_enabled=yes).
4. Run cfgmgr so that all the devices will come into available state.
5. Use chdev command on hdisk2 to enable or disable protection (chdev -l hdisk2 -a
DIF_protection=yes). If the disk supports protection and all paths support protection, the attribute
value will be set to "yes". Otherwise, it will be set to "unsupported".
Note: If the attribute value is set to "unsupported", check all paths (all fcs adapter attributes) and
check to see if the protection is enabled on the LUN when it is created on the DS5000 storage. In
some cases, the attribute on the fcs adapter may show "yes" but it may not be supported due to an
old 8Gb PCIe FC adapter (feature code 5735 or 5273) firmware that does not support T10 protection
(BlockGuard feature).
141
142
Chapter 6. Working with full disk encryption

This chapter describes the capabilities and advantages of full disk encryption (FDE) disk drives and how
to implement security on FDE-compatible storage subsystems that are equipped with FDE disks.
In addition to the information in this chapter, the IBM Full Disk Encryption Best Practices document
describes best practices for maintaining security on a storage subsystem that is equipped with FDE
drives. To access this document, go to http://www-947.ibm.com/support/entry/portal/
docdisplay?lndocid=MIGR-5081492&brandind=5000028, or complete the following steps:
1. Go to the IBM Support Portal at http://www.ibm.com/support/entry/portal.
2. In the Search within all of support & downloads field at the bottom of the webpage, type FDE and
press Enter.
3. In the list of search results, click the IBM Full Disk Encryption Best Practices - IBM System Storage
link.
4. Click the link to the PDF file to open or download the IBM Full Disk Encryption Best Practices
document.
Note: The screenshots in this section are only illustrative and may differ from the actual UI depending
on the Storage Manager and controller firmware versions.
The following topics are addressed in this chapter:
v Full disk encryption on page 144
1. Securing data against a breach on page 144
2. Choosing local or external security key management on page 145
3.
4.
5.
6.
7.
Using security keys on page 146

Using secure erase on page 156
FDE security authorizations on page 157
FDE terminology on page 159
v Installing and configuring the DS TKLM Proxy Code server on page 160
1. Modifying the DS TKLM Proxy Code server configuration file on page 161
2. Installing the DS TKLM Proxy Code on page 165
v Configuring disk encryption with FDE drives on page 166
1. Installing FDE drives on page 166
2. Enabling premium features on page 166
3. Securing a RAID array on page 175
4. Unlocking disk drives on page 181
5. Migrating storage subsystems (head-swap) with FDE drives on page 183
6. Erasing disk drives on page 187
7. Global hot-spare disk drives on page 190
8. Log files on page 191
v Frequently asked questions on page 191
Note: Not all IBM DS storage subsystems support FDE. See the documentation that came with your
storage subsystem for information about FDE compatibility.
143
Full disk encryption

The information in this section provides an overview of how FDE works. Subsequent sections in this
chapter describe how to configure disk encryption, using internal security key management, and using
external security key management.
The use of full disk encryption (FDE) secures data against threats when an FDE drive is out of its owner's
control. FDE drives do not protect data from threats that occur within the data center or on the network.
If an attacker gains access to a server and can access an unlocked drive, the attacker can read the clear
text that comes from the drive. Remember that drive-level encryption technology does not replace the
access controls of the data center; rather, it complements them.
Full disk encryption (FDE) disk drives enable you to reduce the security vulnerabilities of stored data.
FDE disk drives that adhere to the Trusted Storage Group (TCG) enterprise security subsystem class
specification are National Security Agency qualified and provide security with government-grade
encryption.
Note: No single security implementation can effectively secure all levels of data from all threats.
Different technologies are required to protect data that is stored on hard disk drives from different
threats. FDE drives protect the security of stored data through the following methods:
Securing data against a breach
If an unauthorized user gains possession of a disk drive that contains encrypted data, or the
drive is removed from the data center or power is turned off, the data is protected.
Using secure erase
Secure erase provides fast, permanent erasure of data on drives that are planned for reuse or
disposal.
Securing data against a breach

Drives with full disk encryption technology are security capable. Each FDE drive comes from the factory
in Security Capable (security disabled) state. In this state, FDE drives behave exactly as non-FDE drives.
The data that is stored on them is not protected when the drives are removed from the storage
subsystem. You can move them from one storage subsystem to another without unlocking them with a
security key file. They can also be used as part of a RAID array that is composed of non-encrypting
(non-FDE) disks. However, a RAID array that is composed of Security Capable FDE and non-FDE drives
cannot be converted into a secured RAID array at a later time, leaving the data on the FDE drives
unprotected if they are removed from the storage subsystem.
The IBM storage subsystem controllers can apply security to every FDE drive in a RAID array that is
composed entirely of FDE drives. Depending on the security key management method that you use (local
or external), the controller firmware either creates a security key or obtains a security key from the
external key manager, such as the IBM Tivoli Key Lifecycle Manager software. After the firmware has the
security key, it activates the encryption function of the drive, which causes each FDE disk drive to
generate a random encryption key that is embedded on the disk.
When security is enabled, the FDE drive automatically executes full disk encryption for write and read
operations. When a write operation is performed, clear text enters the disk and is encrypted before it is
written to the media, using the disk encryption key. When a read operation is performed, encrypted data
that is read from the media is decrypted before it leaves the drive.
During normal operation, whether the FDE drive is in Security Capable or Security Enabled state, it
behaves the same as a non-encrypting disk to the storage subsystem. A security-enabled FDE drive is
constantly encrypting data. Disk encryption cannot be accidentally turned off. The disk encryption key is
generated by the drive itself, is stored on the disk, never leaves the disk, and is unique to that drive
144
alone. To ensure that security is never compromised, an encrypted version of the encryption key is stored
only on the disk drive. Because the disk encryption key never leaves the disk, you might not have to
periodically change the encryption key, the way a user might periodically change the operating-system
password.
Choosing local or external security key management

There are two methods for managing the security key for your storage subsystem: local and external
security key management.
Local security key management

With local security key management, the security key is created and contained in the storage subsystem
controller. Local security key management does not require additional software. To move secured drives
from one storage subsystem to another, you must use the saved security key file from the original storage
subsystem to unlock the drives.
Note: Local security key management requires controller firmware version 7.50.xx.xx or later.
To
1.
2.
3.
enable local security key management, complete the following tasks:

Upgrade the controller firmware to version 7.50.xx.xx or later.
Follow the FDE premium feature web-activation instructions.
Use Storage Manager to command the storage subsystem controller to create the security key.
External security key management

Instead of using a security key created by the storage subsystem controller, external security key
management uses a central key location on your network to manage keys for different storage
subsystems. External security key management is facilitated by external key license manager software,
such as IBM Tivoli Key Lifecycle Manager (TKLM). If you do not already have this software, you must
purchase it, install it, and configure the proxy server.
With external security key management, the controllers obtain the security key from the external security
key management source. This key is then obfuscated in the controller volatile memory for future use, as
long as the storage subsystem power is turned on. This key is erased from volatile memory when the
storage subsystem power is turned off. Because the key is not stored in the storage subsystem, the
storage subsystem must have a non-FDE drive in the configuration to boot successfully; it then requests
the security key from the external key management server to unlock the FDE drives.
This method provides a common and consistent key management interface; the external key license
manager software also manages security keys for other storage hardware, such as secured tape drives.
You do not have to access a saved security key file to move secured drives from one storage subsystem to
a second storage subsystem. Rather, the external key license manager software supplies the security key
that unlocks the drives automatically, if the second storage subsystem is connected to the key license
manager when the drives are inserted.
To enable external security key management, complete the following tasks:
1. Upgrade the controller firmware to version 7.70.xx.xx or later. Follow the FDE premium feature
web-activation instructions to enable both the FDE and External Key Management premium features.
2. Install and configure the external key license manager software. See the documentation that came
with the software for more information.
3. Install and configure the DS TKLM Proxy Code.
4. Configure the external key management software to receive an external key request.
145
5. Use Storage Manager to command the storage subsystem controller to request the security key from
the external key license manager, instead of generating a local security key.
6. Configure the external key license manager software to accept an external key request.
Important:
1. Tivoli Key Lifecycle Manager is the only external security key management software that is supported
on IBM DS storage subsystems.
2. External security key management requires controller firmware version 7.70.xx.xx or later.
3. Make sure that at least one non-FDE drive is installed in the storage subsystem when you use
external security key management. Otherwise, if the storage subsystem power is turned off and then
on again, the storage subsystem might require that you supply the security key from the saved file
manually to unlock the secured FDE drives and complete the boot process.
Using security keys

With full disk encryption, the process of securing a drive consists of enabling security on the storage
subsystem and then securing the specific security-capable RAID arrays where the data is stored.
The process for generating a security key depends on the type of security key management method that
you use. Enabling security on the storage subsystem is a one-time process, unless the you decide at a
later date to change the security key or change the method of key management. Separate security keys
are not required for each individual drive, even though each FDE drive has its own unique encryption
key. To enable security on the storage subsystem, you must purchase FDE drive options and an IBM DS
Disk Encryption premium feature key and enable the feature in the storage subsystem, using the
instructions that come with the premium feature key entitlement kit.
After the security key is created by the controllers, or is obtained from the external key management
software, an encrypted version of the security key is obfuscated in the storage subsystem and cannot be
viewed directly.
After you create the security key in the storage subsystem, you are asked to save the encrypted version of
the security key in a backup security key file at a location that you specify. Make sure that you protect
the security key file and its associated pass phrase. In addition to the saved location that you specify, the
storage manager also saves a copy of the file in the default location ...\IBM_DS\client\data\
securityLockKey in a Microsoft Windows environment or in /var/opt/SM/securityLockkey in AIX, Linux,
Solaris, and HP-UX environments.
With the local security key management method, you are prompted for the security key identifier and
pass-phrase. This security key identifier is appended with the storage subsystem worldwide identifier to
help you identify the storage subsystem to which the security key is associated. With the external security
key management method, you are prompted only for the pass-phrase. The controller uses the storage
subsystem world-wide identifier to identify the storage subsystem to which the security key file is
associated.
The security key file contains the encrypted security key and the security key identifier. You must
provide the pass phrase during the save security key operation. The pass phrase is not stored anywhere
in the storage subsystem or in the security key file. The controller uses the pass phrase to encrypt the
security key before it exports the security key to the security key file. The security key identifier is stored
in the security key file so that you can identify the storage subsystem to which the security key file is
associated. Make sure that you protect the security key file and its associated pass phrase, because these
two pieces of information can be used to unlock secured FDE drives.
To decrypt the security key in the security key file, you must provide the same pass phrase that was
entered when the security key file was generated. The drive then determines whether its security key and
146
the security key that was provided by the storage subsystem are the same. If they are the same, data can
be read from and written to the security-enabled FDE drives.
Attention: The pass phrase is used only to protect the security key in the security key file. Anyone who
can access the Subsystem Management window can save a copy of the security key file with a new pass
phrase. Set a storage subsystem password for each storage subsystem that requires you to provide a
password when any configuration changes are made, including creating and changing the security key.
See Setting a storage subsystem management password on page 32 for instructions for setting the
storage subsystem password.
If you use local security key management, the security key file provides protection against a corrupted
security key or the failure of both controllers in the storage subsystem. The security key file is also
needed to unlock security-enabled FDE drives when they are moved from one storage subsystem to
another. In these cases, the security-enabled FDE drives remain locked until the drives are unlocked by
the security key that is stored in the security key file. To decrypt the security key in the security key file,
you must provide the same pass phrase that was entered when the security key file was generated. The
drive then determines whether its security key and the security key that was provided by the storage
subsystem are the same. If they are the same, data can be read from and written to the security-enabled
FDE drives.
If you use external security key management, the security key file provides protection in the following
situations:
1. If communication is lost to either the proxy server or the external key license servers when the
controller unlocks the secured FDE drives
2. If the secured FDE drives are moved to or from a storage subsystem that is not managed by the same
external key license manager
3. If drives must be unlocked after the power cycle of a storage subsystem configuration that has only
secured FDE drives and no unsecured FDE or non-FDE drives in the configuration
After the storage subsystem controller creates the security key, the RAID arrays can be changed from a
state of Security Capable to a state of Security Enabled. The Security Enabled state requires the RAID
array FDE drives to be unlocked after power to the drive is turned on using the security key to access the
data that is stored on the drives. Whenever power is applied to the drives in a RAID array, the drives are
all placed in Security Locked state. They are unlocked only during drive initialization with the storage
subsystem security key. The Security Unlocked state makes the drives accessible for the read and write
activities. After they are unlocked, the drives remain unlocked until the power is removed from the
drives, the drives are removed and reinserted in the drive bays, or the storage subsystem power is
cycled.
After a drive is secured, the drive becomes locked if power is turned off or if it is removed. The
encryption key within that drive will not encrypt or decrypt data, making the drive unreadable until it is
unlocked by the controllers.
147
Figure 22. Security-enabled FDE drives: With the correct authorizations in place, the reading and writing of data
occurs in Unlocked state
After authentications are established and security is enabled on a storage subsystem, the encryption of
write operations and decryption of read operations that takes place inside the FDE drive are not apparent
to the user or to the DS5000 storage subsystem controllers. However, if a secured drive is lost, removed,
or stolen, the drive becomes locked, and the data that is stored on the disk remains encrypted and
unreadable. Because an unauthorized user does not have the security key file and pass phrase, gaining
access to the stored data is impossible.
Figure 23. A security-enabled FDE drive is removed from the storage subsystem: Without correct authorizations, a
stolen FDE disk cannot be unlocked, and the data remains encrypted
Changing a security key for local security key management

The process for changing a security key depends on the type of security key management method that
you use. The information in this section describes changing a security key in a local security key
management configuration.
148
When you change a security key, a new security key is generated by the storage subsystem controller
firmware. The new security key is obfuscated in the storage subsystem, and you cannot see the security
key directly. The new security key replaces the previous key that is used to unlock the security-enabled
FDE drives in the storage subsystem. The controller negotiates with all of the security-enabled FDE drives
for the new key. With controller firmware versions 7.50.xx.xx and 7.60.xx.xx, an n-1 version of the security
key is also stored in the storage subsystem for protection in case something prevents the controllers from
completing the negotiation of the new security key with the security-enabled FDE drives (for example,
loss of storage subsystem power during the key change process). If this happens, you must change the
security key so that only one version of the security key is used to unlock drives in a storage subsystem.
The n-1 key version is stored in the storage subsystem only. It cannot be changed directly or exported to
a security key file.
Note: The n-1 key is not stored in the storage subsystem with controller firmware version 7.70.xx.xx or
later.
A backup copy of the security key file is always generated when you change a security key, and must be
stored on some other storage medium in case of controller failure, or for transfer to another storage
subsystem. You participate in creation of the security key identifier, the pass phrase, and the security key
file name and location when you change the security key. The pass phrase is not stored anywhere in the
storage subsystem or in the security file. The controller uses the pass phrase to encrypt the security key
before it exports the security key to the security key file.
Changing a security key for external security key management

The information in this section describes changing a security key in an external security key management
configuration.
When you change the security key, the storage subsystem controller contacts the external key license
manager for a new security key. Then, it the negotiates the new security key with the security-enabled
FDE drives. The new key is not obfuscated inside the controller. You are prompted to save the key in a
security key file. The pass phrase and the security key file name and location are required to back up the
security key. The pass phrase is not stored anywhere in the storage subsystem or in the security key file.
The controller uses the pass phrase to encrypt the security key before it exports the security key to the
security key file.
Identifying a security key file for a storage subsystem

For additional protection, the security key that is used to unlock FDE drives is not visible to the user. The
security key identifier helps you identify which security key file is associated with each storage
subsystem. With the local security key management method, you can provide a value of up to 189
alphanumeric characters. This value is linked with the storage subsystem worldwide identifier and a
random number to form the security key identifier. In the external security key management method, you
are not asked to provide a value that is used as part of the security key identifier. You can view the
security key identifier during operations that involve the drive security key file, such as creating or
changing the security key.
Figure 24 on page 150 shows an example of the security key identifier field when you are performing a
change security key operation.
Note: With external security key management, the security key identifier cannot be modified by the user
as it can with local security key management.
149
Figure 24. Changing the security key
The Change Security Key Complete window shows that the security key identifier that was written to the
security key file has a random number appended to the security key identifier you entered in Figure 24
and the storage subsystem worldwide identifier. Figure 25 on page 151 shows an example of the random
number part of the security key identifier.
150
Figure 25. Changing the security key - Complete
The Security key identifier field in the FDE Drive Properties window includes a random number that is
generated by the controller when you create or change the security key. Figure 26 on page 152 shows an
example of the random number. The random number is currently prefixed with 27000000. If all of the
secured FDE drives in the storage subsystem have the same value in the security key identifier field, they
can be unlocked by the same security key identifier.
Note: The Security Capable and Secure fields in the Drive Properties window show whether the drive is
secure capable and whether it is in Secure (Yes) or Unsecured (No) state.
151
Figure 26. Drive properties - Secure FDE drive
Figure 27 on page 154 shows an example of the security key identifier that is displayed in the File
information field when you select a security key back up file to unlock the secured drives in the storage
subsystem. The security key identifier or LockKeyID, shown in the file information field, contains the
152
characters that you entered in the security key identifier field when you created or changed the security
key along with the storage subsystem worldwide identifier and the randomly-generated number that
appears in the security key identifier of all secured FDE drives. This information is delimited by a colon
(:). For example LockKeyID
Passw0rdplus3:600a0b800029ece6000000004a2d0880:600a0b800029ed8a00001aef4a2e4a73
contains the following information:
v The security key identifier that you specified, for example Passw0rdplus3
Note: With external security key management, the security key identifier cannot be modified by the
user as it can with local security key management. Therefore, this information will not be shown.
v The storage subsystem worldwide identifier, for example 600a0b800029ece6000000004a2d0880
v A randomly-generated number 600a0b800029ed8a00001aef4a2e4a73
153
Figure 27. Select file - LockKeyID
Figure 28 on page 155 shows an example of the drive properties for an unsecured FDE drive. Note that
the security key identifier field for an unsecured FDE drive is populated with zeros. Note also that the
Security Capable field value is yes and the Secure field value is no, indicating that this is a security
capable but unsecured FDE drive.
154
Figure 28. Drive properties - Unsecured FDE drive
Unlocking secure drives in local security key management mode

You can export a RAID array with its security-enabled FDE drives to a different storage subsystem. After
you install those drives in the new storage subsystem, you must unlock the security-enabled FDE drives
155
before data can be read from or written to the drives. The security key on the new storage subsystem will
be different and will not unlock the drives. You must supply the security key from a security key file that
you saved from the original storage subsystem. In addition, you must provide the pass phrase that was
used to encrypt the security key to extract the security key from the security key file. After you unlock
the drives with the security key in the security key file, the controller negotiates the existing security key
for these drives so that only one version of the security key is used to unlock drives in a storage
subsystem.
You do not have to provide the security key file to unlock the security-enabled drives in a storage
subsystem every time the storage subsystem power is cycled or the drives are removed and reinserted in
the same storage subsystem, because the controllers always keep a copy of the current and previous (n-1)
values of the security key to unlock these drives. However, if the drives are removed from the storage
subsystem and the security key is changed more than two times in the same storage subsystem, the
controllers will not have the security key to unlock the drives when they are reinserted in the same
storage subsystem.
Attention: Always back up the data in the storage subsystem to secured tape to prevent loss of data
due to malicious acts, natural disasters, abnormal hardware failures, or loss of the FDE security key.
Unlocking secure drives in external security key management mode

You can export a RAID array with its security-enabled FDE drives to a different storage subsystem. If the
drives are moving to another subsystem that is managed by the same external key license manager as the
original subsystem, you do not have to provide the saved security key file to unlock the drives.
After you unlock the drives with the security key in the security key file, the controller negotiates the
existing security key for these drives so that only one version of the security key is used to unlock drives
in a storage subsystem. Otherwise, you must supply the security key from a security key file that you
saved from the original storage subsystem. You must also provide the pass phrase that was used to
encrypt the security key to extract the security key from the security key file. After you unlock the drives
with the security key in the security key file, the controller negotiates the existing security key for these
drives so that only one version of the security key is used to unlock drives in a storage subsystem.
Note: You must export the array from the original subsystem before you move the FDE drives; the array
is required to configure the drives for removal and update the subsystem configuration.
If the subsystem configuration does not have any unsecured drives or non-FDE drives, you must provide
the security key from a security key file that you saved from the original storage subsystem when the
power to the new subsystem is turned on. If the subsystem configuration has optimal unsecured or
non-FDE drives, the subsystem will start up and connect with the external security key manager to
obtain the key that unlocks the secured FDE drives.
Attention: Always back up the data in the storage subsystem to secured tape to prevent loss of data
due to malicious acts, natural disasters, abnormal hardware failures, or loss of the FDE security key.
Using secure erase

Secure erase protects FDE drives from security threats when they are eventually retired, returned,
discarded, or re-purposed. As these drives are moved from the data center or reused, it is critical that the
data on the disks be permanently erased and not vulnerable to recovery. Discarded drives might still
have residual data that can be reconstructed by an unauthorized user. Secure erase protects against this
threat by cryptographically erasing the data.
The traditional methods that are used to permanently erase data often prove to be expensive and slow
and might not provide the highest level of data erasure. Traditional methods might also put the drives
beyond your control and therefore subject to a data breach. Secure erase provides the following
advantages compared to traditional methods:
156
v Immediate, cryptographic data erasure

v Lower overall costs
v A higher level of media sanitation, in accordance with the National Institute of Standard and
Technology (NIST)
Attention: Secure-erase operations are not reversible. All data on the drive will be permanently erased
when a secure-erase action is performed. Make sure that the data on the drive is backed up or
expendable.
Secure erase with FDE drives allows for immediate erasure of data without requiring that the drive be
removed from the data center. With just a few clicks, you can quickly reuse or discard a drive. With
secure erase, you can erase drives and use them again. This eliminates the need to destroy a drive, yet
still secures warranty and expired lease returns and enables you to reuse drives securely. According to
the NIST, secure erase is considered a type of data purging, which is regarded as a higher level of data
sanitation than traditional methods.
Secure erase prompts the FDE drive to permanently erase the current encryption key and replace it with
a new randomly-generated encryption key within the drive. The drive encryption key is used to encode
and decode all data on the disk. After the encryption key is changed, any data that was previously
written to the disk becomes unintelligible. Data that was encrypted with the previous encryption key is
unintelligible when it is decrypted with the new encryption key. This includes all bits, headers, and
directories. The data is completely and permanently inaccessible.
Figure 29. Secure erase process
FDE security authorizations

The following table identifies and describes the authorization parameters that are used to implement
security on FDE-compatible storage subsystems.
157
Table 25. Security authorizations

Where is it located and
managed?
Parameter
Description
Encryption key
The encryption key is used to Is stored on and is managed

encrypt and decrypt data on by the FDE disk drive:
the FDE disk drive.
v It is never transferred from
the drive.
v Each drive has its own
unique encryption key.
How is it generated?
The encryption key is
generated when the drive is
manufactured and then
regenerated at the customer
site (by a command from the
controller to the drive) to
ensure that the key was not
compromised prior to use.
Security key
The security key is needed to

unlock the encryption key for
encrypting and decrypting to
occur. One security key is
created for all FDE drives on
the storage subsystem. The
security is sometimes
referred to as the lock key.
Is stored on and is managed

by the controller. A single
security key is synchronized
for all controllers in a storage
subsystem.
Security key
identifier
The security key identifier is

paired with the security key
to help you remember which
key to use for secure
operations. With local
security key management
only, you have the option to
provide up to 189
alphanumeric characters that
are linked to the storage
subsystem-generated security
key identifier.
The security key identifier is

stored in a special area of the
disk:
Pass phrase
The pass phrase is used to

encrypt the security key and
the security key identifier.
The pass phrase is a
user-specified alphanumeric
character string, eight
characters minimum, 32
characters maximum. It must
contain at least one number,
one lowercase letter, one
uppercase letter, and one
nonalphanumeric character
(such as <, >, &, @, +, or -).
Spaces are not allowed, and
it is case-sensitive.
User-specified alphanumeric
character string.
character string, not stored
anywhere on the storage
subsystem or in the security
key file. The pass phrase is
used to encrypt the security
key when it is exported in the
security key file. It is also used
to decrypt the key in the
security file when it is used to
import security-enable FDE
drives into a storage
subsystem.
Security key file
File where the security key

File name and location are
identifier is saved along with determined by the
the encrypted security key.
administrator. In addition to
the administrator-specified
location, the storage manager
also saves a copy of the
security key backup file in the
default location. See the IBM
Full Disk Encryption Best
Practices document for more
information.
158
The security key is generated

by the storage subsystem and
is encrypted and hidden in the
storage subsystem.
character string (local security
key management only). The
v Can always be read from the storage subsystem adds the
storage subsystem worldwide
disk
identifier and a randomly
v Can be written to the disk
generated number to the
only if security has been
characters that are entered.
enabled and the drive is
unlocked
Generated by the storage

subsystem after you initiate a
create security key, change
security key, or save security
key operation.
FDE terminology
The following table defines FDE terminology that is used throughout this chapter.
Table 26. Full disk encryption terminology
Term
Description
FDE
Full disk encryption, a custom chip or ASIC (application specific integrated circuit) on
the disk drive that requires a security key to allow encryption and decryption to begin.
FDE disk drives encrypt all the data on the disk. The secured drive requires that a
security key be supplied before read or write operations can occur. The encryption and
decryption of data is processed entirely by the drive and are not apparent to the storage
subsystem.
Secure erase
Permanent destruction of data by changing the drive encryption key. After secure erase,
data that was previously written to the disk becomes unintelligible. This feature takes
advantage of FDE disk security capabilities to erase data by changing the encryption
key to a randomly generated value. Because the encryption key never leaves the drive,
this provides a secure erase. After secure erase, the drive becomes unlocked, allowing
anyone to read or write to the disk. Secure erase is sometimes referred to as drive
reprovisioning.
Local key management
A key management method that uses a security key created and contained in the storage
subsystem controller. To move secured drives from one storage subsystem to another,
you must use the saved security key file from the original storage subsystem to unlock
the drives. The security key is obfuscated and stored in the storage subsystem when the
power is turned off.
Note: Local security key management requires controller firmware version 7.50.xx.xx or
later.
External key
management
A key management method that uses a central key location on your network (one or
more servers external to a storage subsystem) to manage keys for different storage
devices. A proxy server must facilitate the request for and acceptance of a security key.
The security key is not stored in the storage subsystem when the power is turned off.
Note:
1. External security key management requires dedicated software, such as IBM Tivoli
Key Lifecycle Manager (TKLM).
2. External security key management requires controller firmware version 7.70.xx.xx or
later.
Locked
The state that a security-enabled FDE drive enters when it has been removed from and
then reinserted in the storage subsystem, or when the storage subsystem powered off.
When storage subsystem power is restored, the drive remains in the Locked state. Data
cannot be written to or read from a locked disk until it is unlocked by the controller,
using the security key. If the controller does not have the security key, the security key
file and its pass phrase are required to unlock the drives for read and write operations.
Repurposing/
Reprovisioning
Changing a drive from being in Secured state to Unsecured state so that the drive can
be reused. Reprovisioning the drive is accomplished by secure erase.
Secure array
An array on security-enabled FDE drives.
Security-capable drive
An FDE drive that is capable of encryption but is in Unsecured state (security not
enabled).
Security-enabled drive
An FDE drive with security enabled. The security-enabled FDE drive must be unlocked
using the security key after power to the drive is turned on and before read or write
operations can occur.
Unlocked
The state of a security-enabled FDE drive in which data on the disk is accessible for
read and write operations.
Before you begin

If you use external security key management, you must complete the following procedures:
159
1. Install and configure the external key license manager software, IBM Tivoli Key Lifecycle Manager
(TKLM). See the documentation that came with the software for more information.
2. Download the DS TKLM Proxy Code from the IBM Support Portal at http://www.ibm.com/support/
entry/portal.
3. Install and configure the DS TKLM Proxy Code. See Installing and configuring the DS TKLM Proxy
Code server.
4. Enable the Full Disk Encryption and External Key Management premium features in Storage Manager.
See Enabling premium features on page 166.
5. Configure TKLM and the storage subsystems for the DS TKLM proxy and create external key
management security authorizations. See Creating security authorizations using external security key
management on page 170 in Enabling premium features on page 166.
If you prefer to use local security key management, begin with the information in Configuring disk
encryption with FDE drives on page 166.
Installing and configuring the DS TKLM Proxy Code server

This section describes the procedures that are required to install the DS TKLM Proxy Code server. The DS
TKLM Proxy Code supports the following operating systems:
v AIX 5.x
v AIX 6.x
v Red Hat Enterprise Linux 4.x
v
v
v
v
v
v
Red Hat Enterprise Linux 5.5

SUSE Linux Enterprise Server 10.3
SUSE Linux Enterprise Server 11
Windows 2008 R2
Windows 2008 Service Pack 2
Windows 2008 Standard Edition
v Windows 2008 Enterprise Edition

Important: Any environmental or configuration change that might affect the DS TKLM Proxy Code
server requires that you restart the server. For example, a Storage Manager controller swap, the issuing of
the sysWipe command, or a change to the IP address would require that the DS TKLM Proxy Code
server be reconfigured and restarted. In addition, a change to the security key identifier, such as
swapping the Storage Manager controller or issuing the sysWipe command, requires that TKLM be
modified to recognize the new security key identifier as defined in Creating security authorizations
using external security key management on page 170. See Starting, stopping, and restarting the DS
TKLM Proxy Code server on page 161 for more information.
The following diagram illustrates the relationships between the components of an external security key
management configuration.
Note:
1. A maximum of four storage subsystem controllers can be monitored by one proxy server.
2. A maximum of four TKLM servers can be connected to one proxy server.
160
Storage subsystem 1
controller
TKLM server 1
Storage subsystem 2
controller
Proxy polls
controllers for keys
Storage subsystem 3
controller
Proxy request keys

from TKLM servers
TKLM server 2
Proxy server
TKLM servers send
keys to proxy
Storage subsystem 4
controller
TKLM server 3
TKLM server 4
Figure 30. External security key management topology
To establish an external security key management configuration, download the DS TKLM Proxy Code
from the IBM Support Portal at http://www.ibm.com/support/entry/portal and complete the following
procedures:
1. Modifying the DS TKLM Proxy Code server configuration file
2. Installing the DS TKLM Proxy Code on page 165
Important: You must complete the procedures in order. Make sure that the IBM Tivoli Key Lifecycle
Manager (TKLM) software is installed. See the documentation that came with the software for more
information.
Starting, stopping, and restarting the DS TKLM Proxy Code server

Any environmental or configuration changes that might affect the proxy (for example, network changes)
require the proxy to be restarted. The following utilities are available.
For AIX:
start_DS_TKLM_Proxy_Code_AIX.sh
stop_DS_TKLM_Proxy_Code_AIX.sh
restart_DS_TKLM_Proxy_Code_AIX.sh
For Linux:
start_DS_TKLM_Proxy_Code_Linux.sh
stop_DS_TKLM_Proxy_Code_Linux.sh
restart_DS_TKLM_Proxy_Code_Linux.sh
The stop_DS_TKLM_Proxy_Code_*.sh script will remove the entry from /etc/inittab and end the
processes.
Modifying the DS TKLM Proxy Code server configuration file

The configuration file for the proxy is DS_TKLM_Proxy_Code.config. The configuration file name, as well as
the parameters and their definitions, are the same for all supported operating systems (Windows, AIX,
and Linux). However, the format of some of the parameter values are different in Windows and AIX or
Linux.
161
The method of creating and editing the configuration file in Windows is different from the method in AIX
or Linux. With Windows, you must create DS_TKLM_Proxy_Code.config manually, using the template
included in the DS_TKLM_Proxy_Code_Windows*.zip file. The definitions for parameters must be assigned
before the proxy can be installed.
Important: If you are working in a Windows operating-system environment, you must create and modify
the configuration file before you install the DS TKLM Proxy Code server.
With AIX and Linux, DS_TKLM_Proxy_Code.config is created and parameter definitions are assigned
during the installation. You must assign definitions for the configuration file parameters when you are
prompted.
The definition of each parameter is explained in the following table.
Table 27. Proxy configuration file properties
Property name
Description
Example
LogLevel
This property specifies one of the following four levels

for logging:
LogLevel = debug
v UserInfo: basic information about events

v UserWarning: warning information about a potential
problem
v UserError: error information about a system failure,
the proxy server exits
v Debug: information useful for debugging, such as
string lengths and property values on different
positions
DebugPath
This property specifies the location of the debug file. You AIX or Linux example:
must provide a path in your file system that can either
be a path relative to the directory /DS_TKLM_Proxy_Code/ DebugPath = ./Log/Debug/debug.log
bin or an absolute path.
Windows example:
Note: Make sure that you have read and write
permissions for the path directory.
DebugPath = .\Log\Debug\debug.log
AuditPath
This property specifies the location of the audit file. You

must provide a path in your file system that can either
be a path relative to the directory /DS_TKLM_Proxy_Code/
bin or an absolute path.
Note: Make sure that you have read and write
permissions for the path directory.
ThresholdSize
162
AIX or Linux example:

AuditPath = ./Log/Audit/audit.log
Windows example:
AuditPath = .\Log\Audit\audit.log
This property specifies the maximum size of each log file Threshold size = 100000000000
in bytes. If the size threshold is reached, a new file is
created with same file name as the original file name
with the numbers 01 added at the end. If the new log file
reaches the size threshold, the original file is overwritten.
Note: If you decide later to increase the threshold size,
delete the existing log files. Otherwise, the proxy will
write log information in the old files if the new size
threshold is larger than the old size threshold.
Table 27. Proxy configuration file properties (continued)

Property name
Description
Example
Keyinformation
Path
This property specifies the location of the security

certificate file (matched with the file specified in
KeyPassword property). Enter a path in your file system
that can be either relative to /DS_TKLM_Proxy_Code/bin or
an absolute path. Make sure that the path adheres to
conventions for directory specification for Windows or
AIX and Linux, and make sure that the directory and file
that you specify exist.
Note: This property refers to the security certificate file
and password you received in an email after you enabled
the External Key Management premium feature. If you
do not receive the security certificate file or if you no
longer have the file, you can request another file and
password by using the key reactivation process on the
IBM Premium Features website.
AIX or Linux example:
This property specifies the password for the security

certificate (matched with file specified in the
KeyinformationPath property), and will be obfuscated
after reading occurs. If the password must be changed
after it has been obfuscated, you must first delete the
KeyPasswordHex property value and restart the proxy
server. Otherwise, the new password is ignored.
Note: This property refers to the security certificate file
and password you received in an email after you enabled
the External Key Management premium feature. If you
do not receive the security certificate file or if you no
longer have the file, you can request another file and
password by using the key reactivation process on the
IBM Premium Features website.
Example of KeyPassword property

before the first reading occurs:
KeyPassword
KeyinformationPath =
./CertFile/ibmproxycert.p12
Windows example:
KeyinformationPath =
.\CertFile\ibmproxycert.p12
KeyPassword = password
Example of KeyPassword property
after first reading occurs and the
password is obfuscated:
KeyPasswordHex = 47558BADDI3321FC
KeyPassword = ********
163
Table 27. Proxy configuration file properties (continued)

Property name
Description
Example
SYMServer.x
The term SYMServer refers to a storage subsystem and its

controllers.
Note: A maximum of four storage subsystem controllers
can be monitored by one proxy server.This property
specifies information about every storage subsystem, or
Symbol-Server (SYMServer.1 - SYMServer.n) in your
configuration. Each SYMServer requires two controller IP
addresses, two ports (2463), one SSID, one password
indicator, and one password. Therefore, each SYMServer
property value must match the pattern in the following
format. The variables are italicized:
Example before the first time the

configuration file is read:
SYMSERVER.x = Controller A IP address , Controller

B IP address , port number , port number ,
SSID , password indicator , password
SYMServer.1 = 9.37.117.35 ,
9.37.117.36 , 2463 , 2463
,600A0B8000339848000000004B72851F,
false, SymPasswd
Example after the first time the
configuration file is read:
SYMServer.1 = 9.37.117.35 ,
9.37.117.36 , 2463 , 2463 ,
600A0B8000339848000000004B72851F,
true , 6408D5D0C596979894AA8F
The password indicator must be set to false if the

password is provided in clear text and true if the
password is obfuscated. The password is used to manage
the storage subsystem. The password will be obfuscated
automatically and stored in an encrypted format by the
proxy after reading occurs.
In this property, you can use spaces between each part of
the value. The SSID has to be a hexadecimal value. The
proxy compares the SSID from the
DS_TKLM_Proxy_Code.config file to the SSID that it
retrieves from the storage subsystem. If they are not
equal, the proxy will stop monitoring the storage
subsystem.
Note: You must obtain the SSID for the storage
subsystem from the Storage Manager Storage Subsystem
Profile window.
TKLMServer.x
TKLMServer.1 = 9.41.18.161 , 3801

This property specifies information about every TKLM
server in your configuration.
Note: A maximum of four TKLM servers can be
connected to one proxy server.Each TKLM server has one
IP address and one port, so each TKLM server property
value must match the pattern in the following format.
The variables are italicized:
TKLMServer.x = IP address , port number
In this property, you can use spaces between each part of
the value. If you do not enter a value for this property,
the proxy server uses the default value (localhost, 3801).
The port number is found on the Key Serving Ports
window in the Tivoli Lifecycle Key Manager software.
TcpTimeout
This property specifies the length of the timeout period

for a TCP connection to the servers, in seconds.
TcpTimeout = 1000
RpcTimeout
This property specifies the length of the timeout period

for remote procedure calls on servers, in seconds.
RpcTimeout = 10
TimeBetweenSymbolServerQueries
This property specifies a waiting period between

proxy-server checks of the attention state, in seconds.
TimeBetweenSymbolServerQueries = 10
164
Installing the DS TKLM Proxy Code

To install the DS TKLM Proxy Code for use with external security key management, complete one of the
following procedures. For a Windows environment, see Installing the DS TKLM Proxy Code server in a
Windows environment. For an AIX or Linux environment, see Installing the DS TKLM Proxy Code
server in an AIX or Linux environment.
Installing the DS TKLM Proxy Code server in a Windows environment

To install the proxy for a Windows environment, complete the following steps:
1. Go to the IBM Support Portal at http://www.ibm.com/support/entry/portal and download the
applicable file for your version of Windows from the Downloads and fixes area of the portal. The file
name is similar to DS_TKLM_Proxy_Code-Windows-V*.zip.
2. Extract the compressed files to a local directory (for example, c:\DS_TKLM_Proxy_Code).
3. Make sure that the DS_TKLM_Proxy_Code.config file has been modified (see Modifying the DS TKLM
Proxy Code server configuration file on page 161 for the properties that must be modified).
4. Make sure that the certificate file, obtained from IBM and specified in the KeyInformationPath
property in the configuration file, exists before you start the proxy server.
Note: If a DS_TKLM_Proxy_Code_WinService.exe - Application Error message is displayed, you
might have to download and install the Microsoft Visual C++ Redistributable Package. For the
package that is compatible with Windows 2008, go to http://www.microsoft.com/downloads/
details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en.
5. In a DOS prompt window, type the following command: DS_TKLM_Proxy_Code_WinService.exe -i. The
proxy is added to the Services window. To start the proxy, click Start in the Services window.
Note: To uninstall the proxy, open a DOS prompt window and type and execute the following command:
DS_TKLM_Proxy_Code_WinService.exe -u. Restart Windows.
Installing the DS TKLM Proxy Code server in an AIX or Linux environment

The DS TKLM Proxy Code is packaged in RPM format for AIX or Linux (RedHat and SUSE). To install
the proxy server in an AIX or Linux environment, complete the following steps:
1. Go to the IBM Support Portal at http://www.ibm.com/support/entry/portal and download the
applicable file for your operating system version from the Downloads and fixes area of the portal. For
example, the file name for AIX might be DS_TKLM_Proxy_Code-AIX-V2.01_90.70.G0.04.ppc.rpm, and
the file name for Linux might be DS_TKLM_Proxy_Code-Linux-V2.01_90.70.G0.04.i386.rpm.
165
Note: Be sure to download the correct file for your operating system. The operating system is a part
of the RPM file name.
2. Use rpm commands to extract the downloaded file and begin the installation process. For example:
rpm -ivh nodeps DS_TKLM_Proxy_Code-AIX-V1_.ppc.rpm
Note: The -nodeps part of the command is required only for AIX installations.
When you execute the RPM command, you create symbolic links, specify the location of the certificate
file that is provided by IBM, create a backup of /etc/inittab, and provide the path to use when you
execute the installation script.
3. After you execute the RPM command, run the installation script (/DS_TKLM_Proxy_Code/bin/
install.sh).
4. When you are prompted, enter all of the configuration file properties. See Modifying the DS TKLM
Proxy Code server configuration file on page 161 for a description of the properties and their values.
To configure TKLM and storage subsystems for the proxy, and to create external key management
security authorizations, continue to Creating security authorizations using external security key
management on page 170 in Enabling premium features.
Configuring disk encryption with FDE drives

This section provides the procedures for enabling FDE and creating secure arrays on the storage
subsystem. To configure disk encryption with FDE disks, perform the following tasks:
1. Install the FDE drives (see Installing FDE drives).
2. Enable the Full Disk Encryption premium feature (see Enabling premium features).
3. Create an array and enable array security (see Securing a RAID array on page 175).
A security-enabled FDE drive becomes locked when its power is turned off or when it is removed from
the storage subsystem. To unlock a locked drive, see Unlocking disk drives on page 181.
In some storage subsystems, drives can be migrated as a complete array into another storage subsystem.
To migrate a secure array, see Migrating storage subsystems (head-swap) with FDE drives on page 183.
Installing FDE drives

This section lists the FDE disk drives that FDE-compatible IBM DS storage subsystems support, as of the
date of this document. See the IBM System Storage DS3000, DS4000, or DS5000 Hard Drive and Storage
Expansion Enclosure Installation and Migration Guide and the DS5000 Interoperability Guide for installation
procedures and the most up-to-date support information.
The FDE drives that are supported by an IBM DS storage subsystem are specified in the announcement
letters for that particular storage subsystem. You can also contact your IBM reseller or IBM marketing
representative for more information about compatible FDE drives for your storage subsystem.
Note: If the FDE drive is in Security Enabled state and you do not want to preserve the data on the
drive, perform a secure erase on each drive before you use it as part of a new RAID array. Secure erase
forces the drive to generate a new encryption key, places the drive in Unsecured state, and ensures that
any data that was previously stored on the disk is erased. See Using secure erase on page 156 for more
information.
Enabling premium features

The FDE premium feature must be enabled on the storage subsystem, using the instructions that come
with the IBM DS Disk Encryption premium feature key entitlement kit. To verify that full disk encryption
is enabled, on the Setup page, select View/Enable Premium Features. In the Premium Features and
166
Feature Pack Information window, Full Disk Encryption: Enabled and External Key Management:
Enabled indicates that the FDE premium feature is enabled.
Important: External key management requires a security certificate file and its password. The file and
password are emailed to you after you enable the External Key Management premium feature. When you
enable the External Key Management premium feature at the IBM Premium Feature website, you must
provide a valid email address in the fields shown in the following image. Otherwise, you are prompted
to enter your email address after you click Continue.
It might take up to a day to receive the security certificate file and password. If you do not receive the
file or if you no longer have the email with the file, you can request another file and password by using
the key reactivation process on the IBM Premium Features website. For more information about the
security certificate file and configuring the KeyinformationPath and KeyPassword properties (Windows
operating systems only), see Modifying the DS TKLM Proxy Code server configuration file on page
161.
Note:
1. For subsystems with controller firmware version 7.60.xx.xx and earlier, the notification might read
Drive Security: Enabled.
2. The External Key Management premium feature will not be available if the controller firmware
version is earlier than 7.60.xx.xx.
3. For storage subsystems with controller firmware version 7.50.xx.xx and 7.60.xx.xx that already have
the FDE premium feature enabled, upgrading to controller firmware version 7.70.xx.xx or later will
not enable the External Key Management premium feature. You must reactivate the FDE key at the
IBM premium feature website to enable both Full Disk Encryption and External Key Management
premium features.
167
4. All FDE premium feature enablement key files generated after November, 2010, consist of two keys:
one for the Full Disk Encryption premium feature and one for the External Key Management
premium feature. Upgrade the controller firmware to version 7.70.xx.xx or later before you apply the
keys.
5. The FDE premium feature supports external security key management at no additional cost. The only
requirements are that the controller firmware is version 7.70.xx.xx or later and the premium feature
must be activated or reactivated at the IBM premium feature key website after November, 2010.
However, you must purchase external key license management software (such as TKLM).
If you enable the FDE feature after November, 2010, for a storage subsystem with controller firmware
7.70.xx.xx or later, External Key Management: Enabled and Full Disk Encryption: Enabled are displayed
in the Premium Features and Feature Pack Information window.
Enabling full disk encryption includes creating the security authorizations that you will need later to
unlock a secured FDE drive that has been turned off or removed from the storage subsystem. These
authorizations include the security key identifier, a pass phrase, and the security key file. The security
authorizations apply to all the FDE drives within the storage subsystem and are critical if a drive must be
unlocked after the power is turned on.
The process for creating security authorizations depends on the method of key management you use. See
the applicable section for local or external security key management.
Creating security authorizations using local security key management

To create the security authorizations for full disk encryption using local key management, complete the
following steps. For external key management security authorizations, see Creating security
authorizations using external security key management on page 170.
1. From the Storage Manager Subsystem Management window, click Storage Subsystem, click Drive
Security, and click Create Security Key.
168
2. Enter a security key identifier, the security key file name and location, and a pass phrase in the Create
Security Key window:
v Security key identifier: The security key identifier is paired with the storage subsystem worldwide
identifier and a randomly generated number and is used to uniquely identify the security key file.
The security key identifier can be left blank or can be up to 189 characters.
v Pass phrase: The pass phrase is used to decrypt the security key when it is read from the security
key file. Enter and record the pass phrase at this time. Confirm the pass phrase.
v Security key backup file: Click Browse next to the file name to select the security key file name
and location, or enter the value directly in the field. Click Create Key.
Note: Save the security key file to a safe location. The best practice is to store the security key file
with your key management policies. It is important to record and remember where this file is
stored because the security key file is required when a drive is moved from one storage subsystem
to another or when both controllers in a storage subsystem are replaced at the same time.
3. In the Create Security Key Complete window, record the security key identifier and the security key
file name; then, click OK. The authorizations that are required to enable security on FDE drive in the
169
storage subsystem are now in place. These authorizations are synchronized between both controllers
in the storage subsystem. With these authorizations in place, arrays on the FDE drives in the storage
subsystem can be secured.
Attention: For greater security, store more than one copy of the pass phrase and security key file. Do
not specify the default security file directory as the location to store your copy of the security key file.
If you specify the default directory as the location to save the security key file, only one copy of the
security key file will be saved. Do not store the security key file in a logical drive that is mapped
from the same storage subsystem. See the IBM Full Disk Encryption Best Practices document for more
information.
Creating security authorizations using external security key management

Important:
Before you can create the security authorizations for full disk encryption with external key management,
you must complete the procedures in Installing and configuring the DS TKLM Proxy Code server on
page 160.
After the Tivoli Key Lifecycle Manager (TKLM) is installed, it must be configured to service key requests
from the DS TKLM Proxy Code server. To configure TKLM, complete the following steps:
1. Open TKLM and log in with the TKLAdmin ID.
2. Click click here to create the master keystore. The Keystore settings window is displayed.
3. Type and retype the password for the keystore. Keep the default values for the other keystore
settings, and click OK.
170
4. Click the Welcome link on the left side of the window. The Welcome window opens.
5. In the Key and Device Management box, select DS5000 from the Manage keys and devices menu,
and click Go. The Key and Device Management window opens.
171
6. When the Confirm prompt is displayed, click Cancel.

7. In the drop-down menu at the bottom of the window, select Hold new device requests pending my
approval.
8. Open Storage Manager, log in, and open the Subsystem Management window for the storage
subsystem that you are configuring.
9. Click Storage Subsystem > Drive Security > Security Key Management > External.
Note: If the External Key Management premium feature is not enabled, the menu option Security
Key Management is not displayed when you click Storage Subsystem > Drive Security.
172
10. When you are prompted with the Confirm Security Key Management window, type yes and click
OK.
11. When you are prompted, save a copy of the security key. Enter the pass phrase, file name, and file
location, and click OK. The controller attempts to contact the external key manager for the security
key. If it fails, the following message is displayed:
12. Return to the TKLM application and click the Pending devices link in the Action Items box.
173
The Pending Device Request window opens.

13. Select the device in the list and click Accept. The Accept Device Request window opens.
14. Click Accept on the Accept Device Request window.
174
The TKLM server is now ready to send keys to the DS TKLM Proxy Code server.
Securing a RAID array

An array is secured when the FDE drives in the array are security enabled. The FDE drives in a secured
array become locked if their power is turned off or if they are removed from the storage subsystem.
All drives in the array must be security-capable FDE drives with security not enabled. The array must
not contain any FlashCopy base logical disks or FlashCopy repository logical disks. Base logical disks and
FlashCopy logical disks can be written to the disks only after security is enabled.
To create a RAID array and then secure it, complete the following steps:
1. Create a RAID array from the FDE drives that are available in the storage subsystem and then secure
it. From the Setup page, click Configure Storage Subsystem.
175
2. In the Select Configuration Task window, click Manual (advanced), click Create arrays and logical
drives, and then click OK.
3. In the Create Arrays and Logical Drives window, select Create a new array using unconfigured
capacity. If other (non-FDE) drive types are also installed in the DS5000, be sure to select only Fibre
Channel FDE drives. Click Next to continue.
176
4. Use the Create Array wizard to create the array. Click Next to continue.
5. In the Array Name & Drive Selection window, enter an array name (for example, Secure_Array_1).
Note that the Create a secure array check box has been preselected in this window. Clear the Create
a secure array check box and select Manual (Advanced) under Disk selection choices. Click Next to
continue.
Note: The Create a secure array check box is displayed and selected only if the full disk encryption
premium feature is enabled. If you select this check box when you create an array, the array that is
created will be secured, and the Manual (Advanced) option is not needed to secure the array.
177
6. Configure drives for the array in the Manual Drive Selection window:
a. Select a RAID level (for example, RAID 5).
b. From the Unselected drives list, select the security-capable drives that you want to use and click
Add to add them to the Selected drives list (for example, select the disk drives in slots 2 through
6 from storage expansion enclosure 8).
c. Click Calculate Capacity to calculate the total capacity of the selected drives.
d. Click Finish to complete the array.
Note: These drives are not yet secure. They are secured later in the process.
7. In the Array Created window, click OK to acknowledge successful creation of the array.
178
8. When the wizard prompts you to create logical drives in the array, use the wizard to create the
logical drives. After the logical drives are created, continue to the next step. See Chapter 4,
Configuring storage, on page 49 for more information about creating logical drives.
9. Secure the array that you have created:
a. In the Subsystem Management window, click the Logical/Physical tab.
Note: The blue dots below the disk icons on the right side of the window indicate which disks
compose the array.
b. To enable security on the array, right-click the array name; then, click Secure Drives.
179
c. In the Confirm Array Drive Security window, click Yes to secure the array.
Note:
1) If you move a drive to a separate storage subsystem or if you change the security key more
than two times in the current storage subsystem while the drive is removed from the storage
subsystem, you must provide the pass phrase, the security key, and the security key file to
unlock the drive and make the data readable.
2) After an array is secured, the only way to remove security is to delete the array. You can
make a VolumeCopy of the array and save it to other disks so that the data can continue to
be accessed.
10. In the Subsystem Management window, click the Logical/Physical tab, and note that the array is
secured, as indicated by the lock symbol to the left of the array name.
180
Unlocking disk drives

A security-enabled FDE drive becomes locked when its power is turned off or when it is removed from
the storage subsystem. This is an important feature of storage subsystem disk encryption and FDE drives;
the locked state makes the data unreadable to unauthorized users.
Important: If the storage subsystem is in external key management mode and there is not an optimal
non-FDE or unsecured FDE drive in the subsystem configuration, you must provide the backup security
file and its associated pass phrase to unlock the drives for the storage subsystem to boot successfully.
The conditions that cause an FDE drive to become locked vary, depending on the type of security key
management that you use. With local security key management, the key is stored inside the controller.
Because the controllers always keep a copy of the current and the previous security key, the security key
file is not needed every time the storage subsystem power is cycled or a drive is removed and reinserted
in the same storage subsystem. However, if a drive is moved to another storage subsystem, or if the
security key in the same storage subsystem is changed more than two times while the drive is removed
from the storage subsystem, the pass phrase and security file are required to unlock the drive.
Note: Security-enabled FDE drives remain unlocked during firmware updates or while components are
replaced. The only time these drives are locked is when they are turned off or removed from the storage
subsystem.
With external security key management, the external key manager application supplies the security key to
unlock a drive that has been moved from the original subsystem to a new subsystem, provided that the
new subsystem is accessible to the application. The new subsystem must be connected to the external key
manager application to unlock the drive that was moved. If communication between the external key
manager application and the storage subsystem is disrupted, the drives cannot be unlocked until
communication is re-established, or until the drives are unlocked with the backup security key file.
To unlock a locked FDE drive with the backup security key file, complete the following steps:
1. In the Subsystem Management window, click the Logical/Physical tab.
181
2. Right-click the drives that you want to unlock; then, click Unlock.
Note: If you want to unlock multiple drives, you only have to select one drive. The Storage Manager
automatically lists all of the drives that are locked in the storage subsystem and checks each drive
against the supplied security key file to determine whether it can use the key in the security key file.
3. In the Unlock Drives window, the locked drives that you selected are listed. To unlock these drives,
select the security key file, enter the pass phrase, and then click Unlock. The storage subsystem uses
182
the pass phrase to decrypt the security key from the security key file. The storage subsystem then
compares the decrypted security key to the security key on the drive and unlocks all the drives for
which the security key matches.
Note: The authentication process occurs only when the drive is in Locked state because the drive was
powered on after a power-down event. It does not repeat with each read and write operation.
4. In the Unlock Drives Complete window, click OK to confirm that the drives are unlocked. The
unlocked drives are now ready to be imported.
Migrating storage subsystems (head-swap) with FDE drives

With an FDE-compatible storage subsystem, you can migrate drives as a complete storage subsystem into
another FDE-compatible storage subsystem with existing disk group migration techniques. User data
remains intact on the disks because configuration metadata is stored on every drive in the storage
subsystem. FDE security-enabled drives can also be migrated and remain secure with a few additional
steps that are described in this section.
Note:
1. The following procedure describes only the additional data migration steps that are required for
secure arrays. For complete information and procedures, see the IBM System Storage DS3000, DS4000,
or DS5000 Hard Drive and Storage Expansion Enclosure Installation and Migration Guide.
2. The following data migration steps also apply when you replace both controllers in the storage
subsystem. All drives in that storage subsystem must be included. Partial migrations are not
183
supported when you replace both controllers. A security file is necessary in this case; you might not
have management access to the storage subsystem to export the current security key if both of the
controllers must be replaced.
1. Save the security key that is used to unlock the drives in the existing storage subsystem in a security
key file before you remove the drives from the existing storage subsystem. After you export the
security key, pass phrase, and security key file, the security key file can be transferred from one
storage subsystem to another.
a. In the Subsystem Management window, click Storage Subsystem, click Drive Security, and click
Save Security Key File.
b. In the Save Security Key File - Enter Pass Phrase window, select a file save location, and enter and
confirm the pass phrase; then, click Save.
184
c. Export the defined arrays in the original storage subsystem.

d. Turn off the subsystem power and replace the old storage subsystem controller enclosure with the
new controller enclosure.
e. Turn on the power to the new storage subsystem.
2. After you replace the existing storage subsystem controller enclosure with a new controller enclosure,
unlock the security-enabled FDE drives before you import the RAID arrays:
a. Click the Logical/Physical tab in the Subsystem Management window.
b. Right-click the drives that you want to unlock; then, click Unlock.
Note: The Full Disk Encryption premium feature might be incompliant. Generate the new FDE
premium feature key file to enable the storage subsystem FDE functionality.
185
c. Select the security key file for the selected drives and enter the pass phrase that you entered when
saving the security key back up file; then, click Unlock.
186
Erasing disk drives

Attention: All data on the disk will be permanently erased when the secure-erase operation is completed
on a security-enabled FDE drive. Do not perform this action unless you are sure that you want to erase
the data.
Secure erase provides a higher level of data erasure than other traditional methods. When you initiate
secure erase with the Storage Manager, a command is sent to the FDE drive to perform a cryptographic
erase. A cryptographic erase erases the existing data encryption key and then generates a new encryption
key inside the drive, making it impossible to decrypt the data. After the encryption key is changed, any
data that was written to the disk that was encrypted with the previous encryption key is unintelligible.
This includes all bits, headers, and directories.
After secure erase takes place on the drive, the following actions occur:
v The data becomes completely and permanently inaccessible, and the drive returns to the original
factory state.
v Drive security becomes disabled and must be re-enabled if it is required.
Before you initiate secure erase, the security-enabled FDE drive must be unlocked, and the array that it is
assigned to must be deleted.
Attention: You must back up the data in the security-enabled FDE drives to other drives or to secure
tape before you secure erase an FDE drive if you want to access the data at a later time. All data on the
disk will be permanently erased when the secure-erase operation is completed on a security-enabled FDE
drive. Do not perform this action unless you are sure that you want to erase the data. The improper use
of secure erase will result in lost data.
187
1. Before the drives can be secure erased, you must delete the RAID array that the drives are associated
with and return the drives to Unassigned status:
a. Click the Logical/Physical tab in the Subsystem Management window.
b. Right-click the array name; then, click Delete.
c. When you are prompted to select the array that you want to delete, click the array name and click
Delete.
d. To confirm that you want to delete the array, enter yes in the field and click OK.
188
e. Wait for the array deletion process to be completed. When you receive the confirmation Processed
1 of array(s) Complete, click OK.
2. Click the Logical/Physical tab in the Subsystem Management window.
3. Select the drive on which you want to perform a secure erase. You can select more than one drive to
be erased by holding down the Ctrl key. In the top menu bar, click Drive; then, click Secure Erase.
189
4. To confirm that you want to permanently erase all data on the disk, enter yes in the field and click
OK. These drives can now be repurposed or discarded.
Global hot-spare disk drives

If a disk drive fails in a FDE-compatible storage subsystem, the controller uses redundant data to
reconstruct the data on the failed drive on a global hot-spare drive. The global hot-spare drive is
automatically substituted for the failed drive without intervention. When the failed drive is eventually
replaced, the data from the hot-spare drive is copied back to the replacement drive.
Hot-spare drives must meet the array hot-spare requirements. The following drive types are required for
hot-spare drives when secure-capable arrays are configured. If a drive does fail, the Storage Manager
automatically determines which hot-spare drive to substitute according to the type of the failed drive.
v For an array that has secured FDE drives, the hot-spare drive must be an unsecured FDE drive of the
same or greater capacity. After the unsecured FDE hot-spare drive is used as a spare for a failed drive
in the secured RAID array, it is security enabled.
v In an array that has FDE drives that are not secured, the hot-spare drive can be either an unsecured
FDE drive or a non-FDE drive.
Note: If an unsecured FDE hot-spare drive was used as a spare for a non-secured FDE array and the
array was secured after the data was copied back, the unsecured FDE hot-spare drive remains unsecured,
exposing the data in the drive if it is removed from the storage subsystem.
190
An unconfigured secured FDE drive cannot be used as a global hot-spare drive. If a global hot spare is a
secured FDE drive, it can be used as a spare drive only in secured arrays. If a global hot-spare drive is an
unsecured FDE drive, it can be used as a spare drive in secured or unsecured arrays with FDE drives, or
as a spare drive in arrays with non-FDE drives. You must secure erase the FDE drive to change it to
Unsecured state before it can be used as a global hot-spare drive. The following error message is
generated if you assign an unconfigured secured FDE drive as a global hot spare.
Return code: Error 2 - The operation cannot complete because either (1) the current state of a
component does not allow the operation to be completed, (2) the operation has been disabled in
NVSRAM (example, you are modifying media scan parameters when that option (offset 0x31, bit 5)
is disabled), or (3) there is a problem with the storage subsystem. Please check your storage
subsystem and its various components for possible problems and then retry the
operation.Operation when error occurred: PROC_assignSpecificDrivesAsHotSpares
When a global hot-spare drive is used as a spare for a failed drive in a secure array, it becomes a secure
FDE drive and remains secure provided that it is a spare in the secure array. After the failed drive in the
secure array is replaced and the data in the global hot-spare drive is copied back to the replaced drive,
the global hot-spare drive is automatically reprovisioned by the controllers to become an unsecured FDE
global hot-spare drive.
As a best practice in a mixed disk environment that includes non-security-capable SATA drives,
non-security-capable Fibre Channel drives, and FDE Fibre Channel drives (with security enabled or not
enabled), use at least one type of global hot-spare drive (FDE Fibre Channel and a SATA drive) at the
largest capacity within the array. If a secure-capable FDE Fibre Channel and a SATA hot-spare drive are
included, all arrays are protected.
Follow the standard hot-spare drive configuration guidelines in Configuring global hot-spare drives on
page 67). Hot-spare configuration guidelines are the same for FDE drives.
Log files
The Storage Manager major events log (MEL) includes messages that describe any security changes that
are made in the storage subsystem.
Frequently asked questions

This section lists frequently asked questions about FDE. The questions and answers are organized in the
following categories:
v
v
v
v
v
Securing arrays
Secure erase on page 192
Local security key management on page 192
External security key management on page 193
Premium features on page 193
v Global hot-spare drives on page 193

v Boot support on page 194
v Locked and unlocked states on page 194
v Backup and recovery on page 194
v Other on page 194
Securing arrays
v Can I change an unsecured array with FDE drives to a secured array?
191
Yes. The steps to complete this process are described in Securing a RAID array on page 175. The
DS5000 Encryption feature must be enabled and the security key file and pass phrase already
established. See Enabling premium features on page 166 for more information.
v When I enable security on an array, will the data that was previously written to that array be lost or
erased?
No. Unless you perform a secure erase on the array disk drives, this data remains intact.
v Can I change a secured array with FDE drives to an unsecured array?
No. This is not a supported option. After an unsecured array is changed to a secure array, you
cannot change it back to an unsecured array without destroying the data in the security-enabled
FDE drives. Use VolumeCopy to copy the secure data to an unsecured array, or back up the data to
a secured tape. If you VolumeCopy the secure data to an unsecured array, you must physically
secure the drives. Then you must delete the original array and secure erase the array drives. Create
a new unsecured array with these drives and use VolumeCopy to copy the data back to the original
drives, or restore the data from secure tape.
v If I have an array with FDE drives that is secured, can I create another array that uses these same
drives and not enable security? Does the storage subsystem have a control so that this does not occur?
No. These are not supported functions. Any logical drive that is part of an array must be secured,
because the drives on which it is stored are security enabled.
v When a secure array is deleted, does disk security remain enabled?
Yes. The only way to disable security is to perform a secure erase or reprovision the drives.
v If I create a new array on a set of unassigned/unconfigured security-enabled FDE disks, will they
automatically become secure?
Yes.
Secure erase
v With secure erase, what can I erase, an individual drive or an array?
Secure erase is performed on an individual drive. You cannot erase a secured drive that is part of an
array; you must first delete the array. After the array is deleted and the drives become unassigned,
you can erase multiple disks in the same operation by holding the Ctrl key while you select the
drives that are to be secure erased.
v If I want to use only the secure erase feature, do I still have to set up a security key identifier and pass
phrase?
Yes. The full disk encryption feature must be enabled before you can use secure erase.
v After secure erase is performed on a drive, is security enabled or disabled on that drive?
The drive is returned to Secure Capable (unsecured) state after a secure erase. Security is disabled
on the drive.
v If I inadvertently secure erase a drive, is it possible to recover the data in the drive?
No. After a drive is secure erased, the data in the drive is not recoverable. You must recover the lost
data from a backup copy. Back up the data in secure drives before you secure erase the drives.
Local security key management

v Can I get to the security keys through the Storage Manager or controller?
No. The security key is obfuscated in the storage subsystem. Only an encrypted version of the key
can be exported to a security key file, using the save security key operation. The actual security key
is not available for viewing. Implement prudent security features for the storage subsystem. The
Storage Manager forces a strong password, but administrator access must have stringent controls in
place.
v If I lose a drive that is unlocked or security disabled, can that data be accessed even though the data is
encrypted?
192
Yes. Because security has not been enabled on the drive, it remains unlocked, and the data is
accessible.
v If my security key falls into the wrong hands, can I change it without losing my data?
Yes. The drive can be re-keyed, using the procedure to change the security key.
External security key management

v How is external security key management different from local security key management?
Instead of using a security key that is housed and obfuscated in a storage subsystem controller,
external security key management uses a central key location on your network to manage keys for
different storage subsystems. External security key management is facilitated by external key license
manager software, such as IBM Tivoli Key Lifecycle Manager (TKLM). If you do not already have
this software, you must purchase it, install it, and configure the proxy server to set up external
security key management.
v Do I need access to the saved security file when I move secured drives from one storage subsystem to
another?
No. If the new storage subsystem is connected and recognized by the proxy server and the external
key management software, the software provides the security key to unlock the drive automatically.
v Why does the storage subsystem require that I manually supply the security key from the saved
security file after I cycled the power to the subsystem?
The subsystem does not have at least one installed non-FDE drive.
Premium features
v How do I make sure that my mirrored data is secure? What is a best practice for protecting data at the
remote site?
Secure your data with security-enabled FDE drives at both the primary and secondary sites. Also,
you must make sure that the data is protected while it is being transferred between the primary and
secondary sites.
v Can I use VolumeCopy to copy a secured logical unit number to a unsecured one? If so, what prevents
someone from doing that first and then stealing the unsecured copy?
Yes. To prevent someone from stealing the data with this method, implement prudent security
features for the DS5000 storage subsystem. The Storage Manager forces a strong password, but
administrator access must also have stringent controls in place.
v Can FlashCopy and VolumeCopy data be secured?
Yes. For FlashCopy, the FlashCopy repository logical drive must be secured if the target FlashCopy
data is secured. The Storage Manager enforces this rule. Similarly, if the source array of the
VolumeCopy pair is secured, the target array of the VolumeCopy pair must also be secured.
Global hot-spare drives

v
Can I use an unconfigured FDE drive as a global hot-spare drive?
Yes, but only if the drive is unsecured (security not enabled). Check the status of the unconfigured
FDE drive. If the drive is secure, it must be secure erased or reprovisioned before you can use it as a
global hot-spare drive.
v If the hot-spare drive in a secured array is an unsecured FDE drive, does this drive automatically
become secured when a secured FDE drive fails and that data is written to the hot-spare drive?
Yes. When the failed drive is removed from the RAID group, a rebuild is automatically started to
the hot-spare drive. Security is enabled on the hot-spare drive before the rebuild is started. A rebuild
cannot be started to a non-FDE drive for a secure array. After the failed drive in the secured array is
replaced and the data in the global hot-spare drive is copied back to the replaced drive, the global
hot-spare drive is automatically reprovisioned by the controllers to become an unsecured FDE global
hot-spare drive.
193
Boot support
v Is there a special process for booting from a security-enabled drive?
No. The only requirement is that the storage subsystem must be running (which is required in any
booting process).
v Are FDE drives susceptible to cold boot attacks?
No. This issue applies more to the server side, because an individual can create a boot image to gain
access to the server. This does not apply to FDE drives. FDE drives do not use the type of memory
that is susceptible to a cold boot attack.
Locked and unlocked states

v When does a security-enabled drive go into Locked state?
The drive becomes locked whenever the disk is powered off. When the FDE drive is turned off or
disconnected, it automatically locks down the data on the disk.
Backup and recovery

v How can I make sure that my archived data is secure?
Securing archived data is beyond the scope of this document. See the Storage Networking Interface
Association (SNIA) guidelines for secure tape backup. For specific references, see the IBM Full Disk
Encryption Best Practices document. To access this document on the IBM website, go to
http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5081492
&brandind=5000028, or complete the following steps:
2. In the Search within all of support & downloads field at the bottom of the webpage, type FDE
and press Enter.
3. In the list of search results, click the IBM Full Disk Encryption Best Practices - IBM System
Storage link.
document.
Other
v Is DACstore information still written to the disk?
Yes. However, if the drive is secured, it must be unlocked by the controller before the DACstore
information can be read. In the rare event that the controller security key is corrupted or both
controllers are replaced, a security key file must be used to unlock the drive.
v Is data on the controllers cache secure with FDE and IBM Disk Encryption? If not, are there any best
practices here?
No. This is a security issue of physical access to the hardware. The administrator must have physical
control and security of the storage subsystem itself.
v If I have secure-capable disks but have not purchased the IBM Disk Encryption premium feature key,
can I still recognize secure-capable disks from the user interface?
Yes. This information is available from several windows in the Storage Manager interface.
v What about data classification?
See the SNIA best practices for more information about data classification. For specific references,
see the IBM Full Disk Encryption Best Practices document. To access this document on the IBM
website, go to http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5081492
&brandind=5000028, or complete the following steps:
2. In the Search within all of support & downloads field at the bottom of the webpage, type FDE
and press Enter.
194
3. In the list of search results, click the IBM Full Disk Encryption Best Practices - IBM System
Storage link.
document.
v Can I use both FDE and non-FDE drives if I do not secure the drives?
Yes. However, using both FDE and non-FDE drives is not a cost-effective use of FDE drives. An
array with both FDE and non-FDE drives cannot be converted into a secure array at a later time.
v Do FDE disk drives have lower usable capacity because the data is encrypted or because capacity is
needed for the encryption engine and keys?
No. There is no capacity difference between non-FDE and FDE disk drives (1 GB unencrypted = 1
GB encrypted).
195
196
Chapter 7. Configuring and using the Support Monitor

The Storage Manager Profiler Support Monitor tool, also referred to as Support Monitor, is a component of
the IBM Storage Manager upto version 10.77.xx.xx. In addition to the Storage Manager Profiler Support
Monitor code, the Apache Tomcat web server and MySQL database software packages are installed as
part of the tool.
If you call IBM support with a critical-event problem, the Storage Manager Profiler Support Monitor tool
ensures that IBM support can get the information that they need about the state of a storage subsystem
prior to the storage subsystem critical event.
The Support Monitor tool performs the following functions:
v Is automatically installed as part of the Storage Manager installation.
v Automatically collects the support bundle through the computer TCP connection. The default is to
collect the support bundle daily at 2 a.m. The support data bundle is a compressed file of the following
items:
Collect all support data (CASD) bundle
Storage subsystem configuration file
SOC counts
RLS counts
ESM state capture
v Automatically manages the collected support bundles. It saves only the last five collected support data
bundles and deletes older support data bundles.
v Provides a web-based interface for selecting the applicable support data bundle to send to IBM
support.
Note: No user configuration or interaction is required unless you want to change the default operating
behavior of the Support Monitor tool.
Use the information in this chapter to configure and use the Support Monitor. See Chapter 3, Installing
Storage Manager and Support Monitor, on page 23 for information about installing and the Support
Monitor tool.
This chapter contains the following topics:
v
v
v
v
v
The Support Monitor interface on page 198

Scheduling collection of the support bundle on page 199
Sending the support bundle to IBM support on page 200
Collecting the support bundle manually on page 201
Using the Support Monitor log window on page 202
v Support Monitor troubleshooting on page 223

For more information about solving problems with the Support Monitor, see Support Monitor
troubleshooting on page 223 in Chapter 8, Troubleshooting, on page 205.
197
The Support Monitor interface

The Support Monitor web interface is described in the following sections. The web interface consists of
the following two components:
v Console area on the right side of the window
v Icons in the Support Monitor web interface
Note: The images in this section might differ slightly from what you see in the window.
Console area
The console area of the Support Monitor interface shows the primary content for the function or item that
you select in the navigation tree.
Figure 31. Console area
198
Icons
The meanings of the Support Monitor icons are described in the following table.
Table 28. Support Monitor icons
Icon
Icon meaning and function

The last support data collection was successful, or the
resource is operational.
The last support data collection was unsuccessful, or the
resource is not operational.
The support data for this resource has not yet been
collected.
Click to schedule support data collection.
Click to send the support data.
Click to initiate support data collection for a storage
subsystem immediately.
The software cannot collect support data for this
resource.
Scheduling collection of the support bundle

Use the information in this section to change the time and frequency of the support bundle collection
schedule.
You can set the support bundle collection frequency to never, daily, weekly, or monthly. You also can
specify the time of day that the support bundle is collected. The support bundle must be collected only
when the storage subsystems are not undergoing heavy usage or performing critical tasks.
If there are multiple storage subsystems in the monitored list, the collection schedule must be modified to
stagger the support bundle collection events among the monitored storage subsystems. Limit the number
of simultaneous support bundle collections to a maximum of three storage subsystems. Depending on the
complexity of the storage subsystem configuration, the controller workloads, the Ethernet network
activities during the time of the support bundle collection, and the size of the captured logs, it might take
30 minutes or more to collect the support bundle for a given storage subsystem. During operating
conditions when the hosts have light I/O workloads, the time that is required to collect the support
bundle data for a storage subsystem is between 5 and 10 minutes.
To save disk space, the Support Monitor keeps only the last five support bundles that are collected for
each storage subsystem. This value cannot be changed. To prevent the support bundles from being
deleted, you must copy them to a different directory from the support bundle saved directory. If the
Storage Manger software was installed to use the default directory, this directory is C:\Program Files
...\IBM_DS\IBMStorageManagerProfiler Server\support in Windows operating-system environments. In
Unix-type operating-system environments, this directory is /opt/IBM_DS/
IBMStorageManagerProfiler_Server/support.
To configure the support bundle collection schedule, complete the following steps:
) for the storage subsystem schedule that you want to change. The
1. Click the Calendar icon (
Schedule Support Data Collection window opens.
2. Click the button for the applicable collection frequency.
199
3. Select the time setting for the collection.

4. Click Save to save the schedule settings.
Sending the support bundle to IBM support

If you experience storage subsystem problems, IBM might request to have the collected support bundles
sent to IBM support for troubleshooting.
To send one or more support bundles to IBM support, complete the following steps:
) for the storage subsystem support bundle that you want to send. The
1. Click the Envelope icon (
Send Support Data window, similar to the following illustration, opens.
Note: If the email server information has not been entered on the Server page in the Administration
menu of the Support Monitor interface, the Server Setup window opens, similar to the one in the
following illustration. Enter the settings for the email server and user email address in the E-mail
Server and E-mail From fields, and click Save.
200
2. In the Send Support Data window, select one or more SOC and RLS change log files, as requested by
IBM support, from the Available area and click the right arrow to move the selected support bundle
to the Selected area. To move all of the available support bundles to the Selected area, click the
double right arrow. If necessary, click the left arrow or double left arrow to move one or all of the
support bundles in the Selected area back to the Available area.
3. Enter the Problem Management Record (PMR) number and the email address that were provided to
you by the IBM support representative. To find the phone number for your country, go to
http://www.ibm.com/planetwide/.
4. Type your email address in the cc field so that a copy of the same email that is sent to IBM support is
also sent to you for your records.
5. In the Details area, type any information that might help IBM support identify the source of the
email. For example, type the PMR number, company information, contact name, telephone number,
and a one-line summary of the problem.
6. Click Send to send the support data bundle to IBM support.
Collecting the support bundle manually

You can use the Support Monitor to manually collect a support bundle for a storage subsystem.
) for the
To collect a support bundle manually for a storage subsystem, click the Life Preserver icon (
storage subsystem. A message opens that states that the support bundle will be collected in the
background. The Last Collection column is automatically updated when the operation is completed.
201
Using the Support Monitor log window

To view the running log of the Storage Manager Profiler Support Monitor log, click the View button on
the upper right corner of the Support Monitor window. A View Module Log File window with the name
mod.sys.support.Support is displayed in the Existing Modules field. In this window, you can specify the
number of log entries to display (up to 1,000 lines) and the frequency of the data refresh.
See the following table for more information about the messages that you might see in the Support
Monitor log window.
Table 29. Support Monitor messages and descriptions
Message type
Message text and description
Support Monitor module online
intializing <num> DeviceClients

This message shows the number of storage subsystems
being monitored plus one more for Support Monitor.
DeviceClient created:
deviceType--><type>
deviceIdent--><id>
status--><status>
After the client is created, this variable logs information
about each storage subsystem.
attempting to start <num> DeviceClients
This message shows that each device client was started
and initialized using the initializing DeviceClients
command.
not starting DeviceClient (<deviceClient name>)since
status is set to <status>
This message shows that when the status is anything
other than online, the client does not start.
Registration
This message appears when a storage subsystem monitor
registration key is created for Support Monitor. The
module status is set to online, and the registration key is
created for the Support Monitor device to register with
the Storage Manager Profiler server.
Support Monitor module offline
stopping <num> DeviceClients

This message appears when the configuration file is
updated with new storage subsystem information, and
the module is temporarily placed offline. The module
then returns to online status to refresh the information.
<id> supportinfo - stopping ClientProxy
This message shows that a specific client is stopped.
Discovery
Discovery (<id>)
This message appears when the device id is assigned
from the Storage Manager Profiler server.
202
Table 29. Support Monitor messages and descriptions (continued)

Message type
General discovery messages
discovery(<id>): discovering arrays/smtp on <time>

sec intervals
This message shows that the discovery data is
established on a scheduled frequency.
discovery(<id>): discovering arrays/smtp from
on-demand request
This message shows that the discovery data is
established through a user-initiated action.
discovery(<id>): discovering process completed in
<time> secs
This message indicates that the discovery process is
complete.
Storage subsystem discovery
Storage subsystem discovery discovery(<id>): new

array discovered-->Name: <arrayName>, IP 1: <ip of
controller 1>, IP 2: <ip of controller 2>
This message shows that the storage subsystem is added
to the Enterprise Management window of the Storage
Manager client program.
discovery(<id>): no new arrays discovered
This message appears when the discovery is initiated but
no new storage subsystems are found.
discovery(<id>): unmanaged array detected-->Name:
<arrayName>, IP 1: <ip of controller 1>, IP 2: <ip
of controller 2>
This message shows that the storage subsystem is
removed from the Enterprise Management window of
the Storage Manager client program.
discovery(<id>): no unmanaged arrays detected
This message appears when the discovery is initiated,
but no storage subsystems are removed from the
Enterprise Management window of the Storage Manager
client program.
SMTP discovery
discovery(<id>): discovered smtp server info (<smtp

server>) and email from info (<email from>)
This message shows that the SMTP server information
and the email address is parsed from the Storage
Manager client program.
203
Table 29. Support Monitor messages and descriptions (continued)

Message type
Support bundle collection retry related message
<array name> stopping periodic support capture,

since previous <num> attempts have failed
If the scheduled support bundle collection failed num"
times for storage subsystem "array name", the Support
Monitor will stop attempting to collect the support
bundle collection for that storage subsystem.
<array name> retrying support capture since last
attempt failed. Retry attempt <num> of <num>
This message appears when a scheduled capture fails for
storage subsystem "array name" after retrying num
times.
Scheduled support bundle collection message
<array name> started periodic support data Capture

This message appears when a scheduled data collection
is started.
On-demand support bundle collection message
<array name> started on-demand support data Capture

This message appears when a user-initiated data
collection is started.
Solving Support Monitor problems

For more information about solving problems with the Support Monitor, see Support Monitor
troubleshooting on page 223 in Chapter 8, Troubleshooting, on page 205.
204
Chapter 8. Troubleshooting
Use the information in this chapter to diagnose and solve problems related to Storage Manager. For
information about getting help, service, or other technical assistance, see Getting information, help, and
service on page xiv.
The following topics are covered in this chapter:
v Critical event problem solving
v Support Monitor troubleshooting on page 223
v DS Diagnostic Data Capture (DDC) on page 225
v Resolving disk array errors on AIX on page 227
Critical event problem solving

When a critical event occurs, it is logged in the event log and sent to any email and SNMP trap
destinations that are configured. The critical event type and the sense key, ASC, and ASCQ data are
shown in the event log details.
If a critical event occurs and you plan to call IBM support, you can use the Customer Support Bundle
feature to gather and package various pieces of data that can aid in remote troubleshooting. To use the
Customer Support Bundle feature, complete the following steps:
1. From the Subsystem Management window of the logical drive that is exhibiting problems, click
Advanced > Troubleshooting > Advanced > Collect All Support Data. The Collect All Support Data
window opens.
2. Type the name of the file where you want to save the collected data or browse to select the file. Click
Start.
Note: It takes several minutes for the compressed file to be created, depending on the amount of data
that is to be collected.
3. When the process is complete, you can send the compressed file electronically to IBM support for
troubleshooting.
Table 30 provides more information about events with a critical priority, as shown in the Subsystem
Management window event log.
Table 30. Critical events
Critical event number
Sense key/ASC/ASCQ
Critical event description and required action
Event 1001 - Channel failed
6/3F/C3
Description: The controller failed a channel and cannot

access drives on this channel anymore. The FRU group
qualifier (byte 26) in the sense data indicates the relative
channel number of the failed channel. Typically, this
condition is caused by a drive that is ignoring the SCSI
protocol on one of the controller destination channels.
The controller fails a channel if it issued a reset on a
channel and continues to see the drives ignore the SCSI
Bus Reset on this channel.
Action: Start the Recovery Guru to access the Failed
Drive SCSI Channel recovery procedure. Contact IBM
support to complete this procedure.
205
Table 30. Critical events (continued)

Sense key/ASC/ASCQ
Event 1010 - Impending

drive failure (PFA) detected
6/5D/80
Description: A drive has reported that a failure

prediction threshold has been exceeded. This indicates
that the drive might fail within 24 hours.
Action: Start the Recovery Guru and click the Impending
Drive Failure recovery procedure. Follow the instructions
to correct the failure.
Event 1015 - Incorrect mode 6/3F/BD

parameters set on drive
Description: The controller is unable to query the drive

for its current critical mode page settings or is unable to
change these settings to the correct setting. This indicates
that the Qerr bit is set incorrectly on the drive specified
in the FRU field of the Request Sense data.
Action: The controller has not failed yet. Contact IBM
support for the instructions to recover from this critical
event.
Event 1207 - Fibre Channel

link errors - threshold
exceeded
None
Description: Invalid characters have been detected in the

Fibre Channel signal. Possible causes for the error are a
degraded laser in a gigabit interface converter (GBIC) or
media interface adapter, damaged or faulty Fibre Channel
cables, or poor cable connections between components on
the loop.
Action: In the main Subsystem Management window,
click Help Recovery Procedures. Click Fibre Channel
Link Errors Threshold Exceeded for more information
about recovering from this failure.
Event 1208 - Data rate

negotiation failed
None
Description: The controller cannot auto-negotiate the

transfer link rates. The controller considers the link to be
down until negotiation is attempted at controller
start-of-day or when a signal is detected after a loss of
signal.
Action: Start the Recovery Guru to access the Data Rate
Negotiation Failed recovery procedure and follow the
instructions to correct the failure.
Event 1209 - Drive channel

set to Degraded
None
Description: A drive channel status was set to Degraded

because of excessive I/O errors or because a technical
support representative advised the array administrator to
manually set the drive channel status for diagnostic or
other support reasons.
Action: Start the Recovery Guru to access the Degraded
Drive Channel recovery procedure and follow the
Event 150E - Controller

loopback diagnostics failed
None
Description: The controller cannot initialize the

drive-side Fibre Channel loops. A diagnostic routine has
been run and has identified a controller problem, and the
controller has been placed offline. This event occurs only
on certain controller models.
Action: Start the Recovery Guru to access the Offline
Controller recovery procedure and follow the instructions
to replace the controller.
206

Sense key/ASC/ASCQ
Event 150F - Channel

miswire
None
Description: Two or more drive channels are connected

to the same Fibre Channel loop. This can cause the
storage subsystem to behave unpredictably.
Action: Start the Recovery Guru to access the Channel
Miswire recovery procedure and follow the instructions
Event 1510 - ESM blade

miswire
None
Description: Two ESM blades in the same storage

expansion enclosure are connected to the same Fibre
Channel loop. A level of redundancy has been lost, and
the I/O performance for this storage expansion enclosure
is reduced.
Action: Start the Recovery Guru to access the ESM blade
Miswire recovery procedure and follow the instructions
Event 1513 - Individual

Drive - Degraded Path
None
Description: The specified drive channel is experiencing

intermittent errors along the path to a single drive or to
several drives.
Action: Start the Recovery Guru to access the Individual
Drive - Degraded Path recovery procedure and follow the
instructions to recover from this failure.
Event 1600 - Uncertified

drive detected
None
Description: An uncertified drive has been inserted into

the storage subsystem.
Action: Start the Recovery Guru to access the Uncertified
Drive recovery procedure and follow the instructions to
recover from this failure.
Event 1601 - Reserved

blocks on ATA drives
cannot be discovered
None
Event 200A - Data/parity

mismatch detected on
logical drive
None
Description: Reserved blocks on the ATA drives are not

recognized.
Action: Contact IBM support for instructions for
recovering from this event.
Description: A media scan operation has detected
inconsistencies between a portion of the data blocks on
the logical drive and the associated parity blocks. User
data in this portion of the logical drive might have been
lost.
Action: Select an application-specific tool (if available) to
verify that the data is correct on the logical drive. If no
such tool is available, or if problems with the user data
are reported, restore the entire logical drive contents from
the most recent backup, if the data is critical.
Event 202E - Read drive

error during interrupted
write
3/11/8A
Description: A media error has occurred on a read

operation during interrupted write processing.
Action: Start the Recovery Guru to access the
Unrecovered Interrupted Write recovery procedure.
Contact IBM support to complete this procedure.
207

Sense key/ASC/ASCQ
Event 2109 - Controller

cache not enabled - cache
sizes do not match
6/A1/00
Description: The controller cannot enable mirroring if the

alternative controller cache size of both controllers is not
the same. Verify that the cache size for both controllers is
the same.
Action: Contact IBM support for the instructions for
recovering from this failure.
Event 210C - Controller

cache battery failed
6/0C/80
Description: The controller has detected that the battery

is not physically present, is fully discharged, or has
reached its expiration date.
Battery CRU recovery procedure and follow the
Event 210E - Controller

cache memory recovery
failed after power cycle or
reset
6/0C/81

cache memory initialization
failed
6/40/81
Description: Recovery from a data-cache error was

unsuccessful. User data might have been lost.
Description: The controller has detected the failure of an
internal controller component (RAID buffer). The internal
controller component failure might have been detected
during operation or during an on-board diagnostic
routine.

cache battery nearing
expiration
6/3F/D9
Event 211B - Batteries

present but NVSRAM
configured for no batteries
None
Description: The cache battery is within six weeks of its

expiration.
Action: Start the Recovery Guru to access the Battery
Nearing Expiration recovery procedure and follow the
Description: A battery is present in the storage
subsystem, but the NVSRAM is set to not include
batteries.
Action: Contact your IBM technical support
representative for the instructions to recover from this
failure.
Event 2229 - Drive failed by None

controller
Description: The controller failed a drive because of a

problem with the drive.
Action: Start the Recovery Guru to access the Drive
Failed by Controller procedure and follow the
Event 222D - Drive

manually failed
208
6/3F/87
Description: The drive was manually failed by a user.

Manually Failed procedure and follow the instructions to
correct the failure.

Sense key/ASC/ASCQ
Event 2247 - Data lost on

the logical drive during
unrecovered interrupted
write
6/3F/EB
Description: An error has occurred during interrupted

write processing during the start-of-day routine, which
caused the logical drive to go into a failed state.
Event 2248 - Drive failed write failure
6/3F/80

Unrecovered Interrupted Write recovery procedure and
follow the instructions to correct the failure. Contact IBM
support to complete this procedure.
Description: The drive failed during a write command.
The drive is marked Failed.
Action: Start the Recovery Guru and follow the
Event 2249 - Drive capacity

less than minimum
6/3F/8B
Description: During drive replacement, the capacity of

the new drive is not large enough to support all the
logical drives that must be reconstructed on it.
Action: Replace the drive with a larger capacity drive.
Event 224A - Drive has

wrong block size
6/3F/8C
Description: The drive block size does not match that of

the other drives in the logical drive. The drive is marked
Failed.
Event 224B - Drive failed initialization failure
6/3F/86
Description: The drive failed from either a Format Unit

command or a Write operation (issued when a logical
drive was initialized). The drive is marked Failed.
Event 224D - Drive failed no response at start of day
6/3F/85
Description: The drive failed a Read Capacity or Read

command during the start-of-day routine. The controller
is unable to read the configuration information that is
stored on the drive. The drive is marked Failed.
Event 224E - Drive failed 6/3F/82

initialization/reconstruction
failure
Description: The previously failed drive is marked Failed

because of one of the following reasons:
v The drive failed a Format Unit command that was
issued to it
v The reconstruction on the drive failed because the
controller was unable to restore it (for example,
because of an error that occurred on another drive that
was required for reconstruction).
209

Sense key/ASC/ASCQ
Event 2250 - Logical drive

failure
6/3F/E0
Description: The controller has marked the logical drive

Failed. User data and redundancy (parity) can no longer
be maintained. The most likely cause is the failure of a
single drive in nonredundant configurations or a
nonredundant second drive in a configuration that is
protected by one drive.
Logical Drive Failure recovery procedure and follow the
Event 2251 - Drive failed reconstruction failure
6/3F/8E
Description: A drive failed because of a reconstruction

failure during the start-of-day routine.
Event 2252 - Drive marked

offline during interrupted
write
6/3F/98
Description: An error has occurred during interrupted

write processing, which caused the logical drive to be
marked Failed. Drives in the array that did not
experience the read error go into the Offline state and log
this error.
Unrecovered Interrupted Write recovery procedure.
Contact IBM support to complete this procedure.
Event 2254 - Redundancy

(parity) and data mismatch
is detected
6/8E/01
Description: The controller detected inconsistent

redundancy (parity) or data during a parity verification.
6/91/3B
definition incompatible with
ALT mode - ALT disabled
Note: This event is not
applicable for the DS4800.
Description: Auto-LUN transfer (ALT) works only with

arrays in which only one logical drive is defined.
Currently, there are arrays in the storage subsystem in
which more than one logical drive is defined; therefore,
ALT mode has been disabled. The controller operates in
normal redundant controller mode, and if there is a
problem, it transfers all logical drives on an array instead
of transferring individual logical drives.
Event 2260 - Uncertified

drive
ASC/ASCQ: None
Description: A drive in the storage subsystem is

uncertified.
Action: Start the Recovery Guru to access the Uncertified
Drive recovery procedure.
Event 2602 - Automatic

controller firmware
synchronization failed
02/04/81
Description: The versions of firmware on the redundant

controllers are not the same because the automatic
controller firmware synchronization failed. Controllers
with an incompatible version of the firmware might
cause unexpected results.
Action: Try the firmware download again. If the problem
remains, contact IBM support.
210

Sense key/ASC/ASCQ
Event 2801 - Storage

subsystem running on
uninterruptible power
supply battery
6/3F/C8
Description: The uninterruptible power supply has

indicated that ac power is no longer present and the
uninterruptible power supply has switched to standby
power. There is no immediate cause for concern, but you
must save your data frequently, in case the battery is
suddenly depleted.
Action: Start the Recovery Guru and click the Lost AC
Power recovery procedure. Follow the instructions to
Event 2803 - Uninterruptible 6/3F/C9

power supply battery - two
minutes to failure

indicated that its standby power supply is nearing
depletion.
Action: Take actions to stop I/O activity to the controller.
Normally, the controller changes from a write-back
caching mode to a write-through mode.
Event 2804 - Uninterruptible None

power supply battery failed
Description: The uninterruptible power supply battery

has failed.
Event 2807 - Environmental

service module failed
None
Event 2808 - storage

expansion enclosure ID not
unique
6/98/01
Description: An ESM has failed.

Action: Start the Recovery Guru and click the Failed
Environmental Service Module CRU recovery procedure.
Follow the instructions to correct the failure.
Description: The controller has determined that there are
multiple storage expansion enclosures with the same ID
selected. Verify that each storage expansion enclosure has
a unique ID setting.
Action: Start the Recovery Guru and click the Enclosure
ID Conflict recovery procedure. Follow the instructions to
Event 280A - Controller

enclosure component
missing
6/3F/C7
Description: A component other than a controller is

missing in the controller enclosure (for example, a fan,
power supply, or battery). The FRU codes indicate the
faulty component.
Event 280B - Controller

enclosure component failed
6/3F/C7
Description: A component other than a controller has

failed in the controller enclosure (for example, a fan,
power supply, battery), or an over-temperature condition
has occurred. The FRU codes indicate the faulty
component.
211

Sense key/ASC/ASCQ
Event 280D - Drive storage

expansion enclosures
component failed
6/3F/C7
Description: A component other than a drive has failed

in the storage expansion enclosure (for example, a fan,
power supply, or battery), or an over-temperature
condition has occurred. The FRU codes indicate the
faulty component.
Event 280E - Standby power 6/3F/CA

supply not fully charged

indicated that its standby power supply is not at full
capacity.
Action: Check the uninterruptible power supply to make
sure that the standby power source (battery) is in
working condition.
Event 280F - Environmental

service module - loss of
communication
6/E0/20
Description: Communication has been lost to one of the

dual ESM CRUs in a storage expansion enclosure. The
storage expansion enclosure has only one available I/O
path.
Event 2813 - Minihub CRU

failed
6/3F/C7
Description: Communication with the minihub CRU has

been lost. This might be the result of a minihub CRU
failure, a controller failure, or a failure in an internal
backplane communications board. If there is only one
minihub failure, the storage subsystem is still operational,
but a second minihub failure might cause the failure of
the affected enclosures.
Event 2815 - GBIC failed
None
Description: A gigabit interface converter (GBIC) on

either the controller enclosure or the storage expansion
enclosure has failed. If there is only one GBIC failure, the
storage subsystem is still operational, but a second GBIC
failure might cause the failure of the affected enclosures.

expansion enclosure ID
conflict - duplicate IDs
across storage expansion
enclosures
6/98/01

expansion enclosure ID
mismatch - duplicate IDs in
the same storage expansion
enclosure
6/98/02
212
Description: Two or more storage expansion enclosures

are using the same enclosure identification number.
Description: A storage expansion enclosure in the storage
subsystem contains ESMs with different enclosure
identification numbers.

Sense key/ASC/ASCQ
Event 281B - Nominal

temperature exceeded
6/98/03
Description: The nominal temperature of the enclosure

has been exceeded. Either a fan has failed or the
temperature of the room is too high. If the temperature of
the enclosure continues to rise, the affected enclosure
might automatically shut down. Fix the problem
immediately, before it becomes more serious. The
automatic shutdown conditions depend on the model of
the enclosure.
Event 281C- Maximum

temperature exceeded
6/3F/C6
Description: The maximum temperature of the enclosure

has been exceeded. Either a fan has failed or the
temperature of the room is too high. This condition is
critical and might cause the enclosure to shut down if
you do not fix the problem immediately. The automatic
shutdown conditions depend on the model of the
enclosure.
Event 281D - Temperature

sensor removed
6/98/03
Description: A fan CRU that contains a temperature

sensor has been removed from the storage subsystem.
Action: Replace the CRU as soon as possible. Start the
Recovery Guru, click the Failed or Removed Fan CRU
recovery procedure, and follow the instructions to correct
the failure.
Event 281E - Environmental 6/98/03

service module firmware
mismatch

subsystem contains ESMs with different versions of
firmware. ESMs in the same storage expansion enclosure
must have the same version firmware. If you do not have
a replacement service monitor, call IBM support to
perform the firmware download.
Action: Start the Recovery Guru and click the
Environmental Service Module Firmware Version
Mismatch recovery procedure. Follow the instructions to
Event 2821 - Incompatible

Minihub
None
Description: An incompatible minihub blade has been

detected in the controller enclosure.
Action: Start the Recovery Guru and click the
Incompatible minihub blade recovery procedure. Follow
the instructions to correct the failure.
Event 2823 - Drive bypassed None
Description: The ESM has reported that the drive has

been bypassed to maintain the integrity of the Fibre
Channel loop.
Action: Start the Recovery Guru to access the By-Passed
Drive recovery procedure and follow the instructions to
recover from this failure.
213

Sense key/ASC/ASCQ
Event 2827 - Controller was

inadvertently replaced with
an ESM
None
Description: A controller blade was inadvertently

replaced with an ESM blade.
Action: Replace the ESM blade with the controller blade
as soon as possible.
Event 2828 - Unsupported

None
storage expansion enclosure
selected
Description: Your storage subsystem contains one or

more unsupported storage expansion enclosures. If all of
your storage expansion enclosures are being detected as
being unsupported, you might have a problem with an
NVSRAM configuration file or you might have the
wrong version of firmware. This error condition will
cause the drives in the unsupported storage expansion
enclosures to be locked out, which can cause the defined
arrays or logical drives to fail.
Action: If there are array or logical drive failures, call
IBM support for the recovery procedure. Otherwise, Start
the Recovery Guru to access the Unsupported Drive
Enclosure recovery procedure and follow the instructions
to recover from this failure.

redundancy lost
6/E0/20
Description: Communication has been lost between the

two controllers through one of the drive loops (channels).
Action: Start the Recovery Guru and determine whether
other loss of redundancy problems are being reported. If
other problems are being reported, fix those first. If
redundancy problems continue to be reported, contact
IBM support.
Event 282B - storage

expansion enclosure path
redundancy lost
6/E0/20
Description: A storage expansion enclosure with

redundant drive loops (channels) has lost communication
through one of its loops. The storage expansion enclosure
has only one loop that is available for I/O. Correct this
failure as soon as possible. Although the storage
subsystem is still operational, a level of path redundancy
has been lost. If the remaining drive loop fails, all I/O to
that storage expansion enclosure fails.
Action: Start the Recovery Guru and click the Drive Loss of Path Redundancy recovery procedure. Follow the
Event 282D - Drive path

redundancy lost
6/E0/20
Description: A communication path with a drive has

been lost. Correct this failure as soon as possible. The
drive is still operational, but a level of path redundancy
has been lost. If the other port on the drive or any other
component fails on the working channel, the drive fails.
Action: Start the Recovery Guru and click the Drive Loss of Path Redundancy recovery procedure. Follow the
214

Sense key/ASC/ASCQ
Event 282F - Incompatible

version of ESM firmware
detected
None

subsystem contains ESM blades with different firmware
versions. This error might also be reported if a storage
expansion enclosure in the storage subsystem contains
ESM blades with different hardware.
Action: Start the Recovery Guru to access the ESM blade
Firmware Version Mismatch recovery procedure and
follow the instructions to recover from this failure.
Event 2830 - Mixed drive

types not supported
None
Description: The storage subsystem currently contains

drives of different drive technologies, such as Fibre
Channel (FC) and Serial ATA (SATA). Mixing different
drive technologies is not supported on this storage
subsystem.
Action: Select the Recovery Guru to access the Mixed
Drive Types Not Supported recovery procedure and
Event 2835 - Drive storage

expansion enclosures not
cabled together
ASC/ASCQ: None
Description: There are drive storage expansion

enclosures in the storage subsystem that are not cabled
correctly; they have ESM blades that must be cabled
together sequentially.
Enclosures Not Cabled Together recovery procedure and

ownership changed due to
failover
None
Description: The multipath driver software has changed

ownership of the logical drives to the other controller
because it could not access the logical drives on the
particular path.
Action: Start the Recovery Guru and click the Logical
Drive Not on Preferred Path recovery procedure. Follow

not on preferred path
None
Description: The controller that is listed in the Recovery

Guru area cannot be accessed. Any logical drives for
which this controller is assigned as their preferred path
will be moved to the non-preferred path (alternative
controller).
Drive Not on Preferred Path recovery procedure. Follow
Event 5005 - Place controller None

offline
Description: The controller is placed offline. This might

be caused by the controller failing a diagnostic test. (The
diagnostics are initiated internally by the controller or by
the Controller Run Diagnostics menu option.) Or the
controller is manually placed Offline using the Controller
Place Offline menu option.
Action: Start the Recovery Guru and click the Offline
Controller recovery procedure. Follow the instructions to
replace the controller.
215

Sense key/ASC/ASCQ
Event 502F - Missing logical None

drive deleted

Description: The storage subsystem has detected that the
drives that are associated with a logical drive are no
longer accessible. This can be the result of removing all
the drives that are associated with an array or a loss of
power to one or more storage expansion enclosures.
Action: Start the Recovery Guru and click the Missing
Logical Drive recovery procedure. Follow the instructions
Event 5038 - Controller in

lockout mode
None
Description: Both controllers have been placed in lockout

mode for 10 minutes because password authentication
failures have exceeded 10 attempts within a 10-minute
period. During the lockout period, both controllers will
deny all authentication requests. When the 10-minute
lockout expires, the controller resets the total
authentication failure counter and unlocks itself.
Action: Wait 10 minutes and try to enter the password
again.
Event 5040 - Place controller None

in service mode
Description: The controller was manually placed in

service mode for diagnostic or recovery reasons.
Action: Start the Recovery Guru to access the Controller
in Service Mode recovery procedure. Use this procedure
to place the controller back online.
Event 5405 - Gold Key mismatched settings
ASC/ASCQ: None
Description: Each controller in the controller pair has a

different NVSRAM bit setting that determines whether
the controller is subject to Gold Key restrictions.
Action: This event might be generated if IBM storage
subsystem controllers or drives are inadvertently
swapped with non-IBM controllers or drives. This critical
event does not apply to the IBM DS3000, DS4000, or
DS5000 storage subsystem configuration. Contact IBM
support for the recovery procedure.
Event 5406 - Mixed drive

types - mismatched settings
ASC/ASCQ: None
Description: Each controller in the controller pair has a

different setting for the NVSRAM bit that controls
whether Mixed Drive Types is a premium feature.
Action: Start the Recovery Guru to access the Mixed
Drive Types - Mismatched Settings recovery procedure
and follow the instructions to correct this controller
condition.
Event 5602 - This controller

alternate failed - timeout
waiting for results
None
Description: This controller initiated diagnostics on the

alternative controller but did not receive a reply that
indicates that the diagnostics were completed. The
alternative controller in this pair has been placed offline.
216

Sense key/ASC/ASCQ
Event 560B - CtlrDiag task

cannot obtain Mode Select
lock
None
Description: This controller is attempting to run

diagnostics and could not secure the test area from other
storage subsystem operations. The diagnostics were
canceled.
Event 560C - CtlrDiag task

on controller alternate
cannot obtain Mode
None
Description: The alternative controller in this pair is

attempting to run diagnostics and could not secure the
test area from other storage subsystem operations. The
diagnostics were canceled.
Event 560D - Diagnostics

None
read test failed on controller
Description: While the controller was running

diagnostics, it detected that the information that was
received does not match the expected return for the test.
This might indicate that I/O is not being completed or
that there is a mismatch in the data that is being read.
The controller is placed offline as a result of this failure.
Event 560E - This controller

alternate failed diagnostics
read test
None
Description: While the alternative for this controller was

running diagnostics, it detected that the information that
was received does not match the expected return for the
test. This might indicate that I/O is not being completed
or that there is a mismatch in the data that is being read.
The alternative controller in this pair is placed offline.
Event 560F - Diagnostics

write test failed on
controller
None

running diagnostics, it was unable to write data to the
test area. This might indicate that I/O is not being
completed or that there is a mismatch in the data that is
being written. The controller is placed offline.
Event 5610 - This controller

alternate failed diagnostics
write test
None

running diagnostics, it was unable to write data to the
test area. This might indicate that I/O is not being
completed or that there is a mismatch in the data that is
being written. The alternative controller in this pair is
placed offline.
217

Sense key/ASC/ASCQ
Event 5616 - Diagnostics

rejected - configuration
error on controller
None
Description: The alternative for this controller is

attempting to run diagnostics and could not create the
test area that is necessary for the completion of the tests.
The diagnostics were canceled.
Event 5617 - Diagnostics

rejected - configuration
error on controller alternate
None
Description: The alternative for this controller is

attempting to run diagnostics and could not create the
test area that is necessary for the completion of the tests.
The diagnostics were canceled.
Event 6101 - Internal

configuration database full
None
Description: Because of the amount of data that is

required to store certain configuration data, the
maximum number of logical drives has been
underestimated. One or both of the following types of
data might have caused the internal configuration
database to become full:
v FlashCopy logical drive configuration data
v Global/Metro remote mirror configuration data
Action: To recover from this event, you can delete one or
more FlashCopy logical drives from your storage
subsystem, or you can remove one or more remote
mirror relationships.
Event 6107 - The alternate

for the controller is
nonfunctional and is being
held in reset
None
Event 6200 - FlashCopy

repository logical drive
threshold exceeded
None
Description: A controller in the storage subsystem has

detected that its alternative controller is nonfunctional
because of hardware problems and must be replaced.
Action: Start the Recovery Guru to access the Offline
Controller recovery procedure and follow the instructions
to recover from this failure.
Description: The FlashCopy repository logical drive
capacity has exceeded a warning threshold level. If the
capacity of the FlashCopy repository logical drive
becomes full, its associated FlashCopy logical drive can
fail. This is the last warning that you receive before the
FlashCopy repository logical drive becomes full.
Action: Start the Recovery Guru and click the FlashCopy
Repository Logical Drive Threshold Exceeded recovery
procedure. Follow the instructions to correct this failure.
Event 6201 - FlashCopy

repository logical drive full
None
Description: All of the available capacity on the

FlashCopy repository logical drive has been used. The
failure policy of the FlashCopy repository logical drive
determines what happens when the FlashCopy repository
logical drive becomes full. The failure policy can be set to
either fail the FlashCopy logical drive (default setting) or
fail incoming I/Os to the base logical drive.
Action: Start the Recovery Guru and click the FlashCopy
Repository Logical Drive Capacity - Full recovery
procedure. Follow the instructions to correct this failure.
218

Sense key/ASC/ASCQ
Event 6202 - Failed

FlashCopy logical drive
None
Description: Either the FlashCopy repository logical

drive that is associated with the FlashCopy logical drive
is full or its associated base or FlashCopy repository
logical drives have failed because of one or more drive
failures on their arrays.
Action: Start the Recovery Guru and click the Failed
FlashCopy Logical Drive recovery procedure. Follow the
instructions to correct this failure.
Event 6400 - Dual primary

logical drive
None
Description: Both logical drives have been promoted to

primary logical drives after a forced role reversal. This
event might be reported when the controller resets or
when a cable from an array to a Fibre Channel switch is
reinserted after it was removed and the other logical
drive was promoted to a primary logical drive.
Action: Start the Recovery Guru and click the Dual
Primary Logical Drive Conflict recovery procedure.
Follow the instructions to correct this failure.
Event 6401 - Dual

secondary logical drive
None
Description: Both logical drives in the remote mirror

have been demoted to secondary logical drives after a
forced role reversal. This event might could be reported
when the controller resets or when a cable from an array
to a Fibre Channel switch is reinserted after it was
removed and the other logical drive was promoted to a
secondary logical drive.
Action: Start the Recovery Guru and click the Dual
Secondary Logical Drive Conflict recovery procedure.
Follow the instructions to correct this failure.
Event 6402 - Mirror data

unsynchronized
Not recorded with event
Description: This might occur because of I/O errors, but

other events can be associated with it. A Needs Attention
icon is displayed on both the primary and secondary
storage subsystems of the remote mirror.
Action: Start the Recovery Guru and click the Mirror
Data Unsynchronized recovery procedure. Follow the
instructions to correct this failure.
Event 6503 - Remote logical

drive link down
None
Description: This event is triggered when a cable

between one array and its peer has been disconnected,
the Fibre Channel switch has failed, or the peer array has
reset. This error might cause the Mirror Data
Unsynchronized, event 6402. The affected remote logical
drive displays an Unresponsive icon, and this state is
selected in the tooltip when you pass your cursor over
the logical drive.
Action: Start the Recovery Guru and click the Mirror
Communication Error - Unable to Contact Logical Drive
recovery procedure. Follow the instructions to correct this
failure.
219

Sense key/ASC/ASCQ
Event 6505 - WWN change

failed
None
Description: Mirroring causes a WWN change to be

communicated between arrays. Failure of a WWN change
is caused by non-I/O communication errors between one
array, on which the WWN has changed, and a peer array.
(The array WWN is the unique name that is used to
locate an array on a fiber network. When both controllers
in an array are replaced, the array WWN changes). The
affected remote logical drive displays an Unresponsive
icon and this state is selected in the tooltip when you
pass your cursor over the logical drive.
Action: Start the Recovery Guru and click the Unable to
Update Remote Mirror recovery procedure. Follow the
instructions to correct this failure. The only solution to
this problem is to delete the remote mirror and then to
establish another one.

copy operation failed
None
Description: A logical drive copy operation with a status

of In Progress has failed. This failure can be caused by a
read error on the source logical drive, a write error on
the target logical drive, or a failure that occurred on the
storage subsystem that affects the source logical drive or
target logical drive.
Drive Copy Operation Failed recovery procedure. Follow
the instructions to correct this failure.
None
Event 6700 - Unreadable
sector(s) detected - data loss
occurred
Description: Unreadable sectors have been detected on

one or more logical drives, and data loss has occurred.
Event 6703 - Overflow in

unreadable sector database
Description: The Unreadable Sectors log has been filled

to its maximum capacity.
None
Action: Start the Recovery Guru to access the Unreadable

Sectors Detected recovery procedure and follow the
instructions for recovering from this failure.
Action: Select the Recovery Guru to access the

Unreadable Sectors Log Full recovery procedure and
follow the instructions for recovering from this failure.
Retrieve trace buffers

Binary trace buffers provide data over a longer period of time than previous dqprint text in
stateCaptureData.txt.
Advanced troubleshooting and support data are collected in binary format and must be parsed by IBM
Support. They are a part of the Collect All Support Data (CASD) support bundle (traceBuffers.zip).
Usage in the CLi:
start controller [both] trace dataType=all forceFlush=FALSE file="C:\TBTest2.zip";
220
Configuration database validation

Version 10.77 adds a new Configuration Database Diagnostic feature.
To perform the validation manually, select a controller on the Physical Tab, then select Advanced >
Troubleshooting > Run Diagnostics > Configuration Database.
An automatic database check will be performed before the controller firmware download is started
through the EMW, SubSystem Managment Window, or CLI.
If validation fails, a zip file is created containing a text file with a description of the error and a DQ file
for troubleshooting.
Validation failure MEL event:
Event Name: Raw data retrieve structure inconsistency detected
Type: 3408
Component Type: Controller
New CLI command:start storageSubsystem configDbDiagnostic;
221
Database save/restore
Storage Monitor Service automatically saves the configuration DB from a subsystem, and an existing
configuration DB can be restored as well.
Save
Storage Monitor Service automatically saves the configuration DB from a subsystem and saves the file in
"...client\data\monitor\dbcapture" if there is a DB change AND 125 minutes have passed since
previous capture.
When a subsystem is added to a newly installed HSW, the first DB is captured.
All captured DB files are zipped and named as follows: RetrievedRecords_SSID_Date_Time.dbm.
Example: RetrievedRecords_60080e500017b8de000000004be47b12_2010_08_20_14_48_27.dbm
CLI can be used to save a DB manually by using the command save storageSubsystem dbmDatabase
file="C:\path\filename.zip"
Restore
An existing configuration DB can be restored to recover systems that have lost their configuration or their
configuration was removed to recover from failure.
It restores portions of the database containing:
v Lun and array configuration
v Lun WWNs
v Controller WWNs
v premium features
v mappings
It excludes:
v MEL
v UTM
v cache
222
Duration: up to 45 minutes
The user must have a Validator String to restore the configuration DB. To obtain the validator, send the
config DB zip file and the system profile to IBM support. IBM support generates the validator string
based on the information that you provide.
Load configuration database

To
1.
2.
3.
load the configuration database, do the following:

Open the *.key file sent via e-mail in a text editor.
Record the string. Example: 8bbaadfa7375cb4dfcc81c15bde30ad32d814c09
Stop the IO to the subsystem
4. Set one of the controllers offline via the GUI

5. The restore is done using the CLI command load storageSubsystem dbmDatabase
file="C:\path\filename.zip" validator="8bbaadfa7375cb4dfcc81c15bde30ad32d814c09";
Support Monitor troubleshooting

This section contains information to help you solve some of the problems you might have with your
software. Table 31 contains problem descriptions, possible problem causes, and suggested actions. Use
this information, in addition to the Storage Manager Recovery Guru in the Subsystem Management
window, to solve problems with your software.
Always use the Storage Manager client to diagnose storage subsystem problems and component failures
and find solutions to problems that have definite symptoms.
Table 31. Problem index
Problem
Possible cause
Possible solution
Data is not being collected

on monitored subsystems
There is a problem with the

Storage Manager client TCP
connection. The operation of
Storage Monitor is dependent
on the Storage Manager client
TCP connection.
Make sure that Storage Manager is able to access data

from the storage subsystem.
A Storage Manager client

Make sure that the client is active and running.
session is not running. A
Storage Manager client session
must be active and running
when you use Storage Monitor.
A user has disabled data
collection for the storage
subsystem.
Open the Support Monitor console and make sure

that support data collection was not disabled for the
storage subsystem in question.
223
Table 31. Problem index (continued)

Problem
Possible cause
Possible solution
A networked storage
subsystem is not in the list
of monitored storage
subsystems.
The missing storage subsystem Re-scan for devices in the Storage Monitor window.
has not been detected by the
software.
Storage Monitor has not been
configured with unique names
for each storage subsystem.
Make sure that all storage subsystems have unique

names in the Storage Manager Enterprise
Management window.
Too many storage subsystems

are defined in the Storage
Manager Enterprise
Management window.
The data collection process of the Storage Monitor is

multi-threaded, with a polling mechanism in place to
find the maximum number of storage subsystems at
predefined timing intervals. The polling mechanism is
not sequential.
For example, if the upper limit of storage subsystems
from which the Storage Monitor can find data is 20,
and 60 storage subsystems are defined, 20 threads are
gathered immediately while the data from the
remaining 40 storage subsystems are gathered only as
resources become available.
The application will not

start.
A user stopped one or more

services manually.
Make sure that all of the required services started.

In a Windows operating system, click Administrative
Tools > Computer Management > Services
(Start/Stop), and make sure that the following services
were started:
v ProfilerCollector
v ProfilerMaintenance
v ProfilerEventReceiver
v ProfilerPoller
v ProfilerWebserver (Tomcat Apache)
v MySQL
In a Unix operating system, run the
/etc/init.d/profiler start command to start the
application, or run the /etc/init.d/profiler stop
command to stop the application.
Email notifications are not

working correctly.
Email notifications are not

configured correctly.
Make sure that email notifications meet the following

conditions:
v SMTP server is set up correctly.
v SMTP server is operational.
v The connection from the Storage Monitor server to
the SMTP server is operational.
The Support Monitor cannot An existing MySQL database

Review the installation log for the possible causes of
be installed.
or Apache web server software errors and correct them as required.
was not removed before the
installation of Storage Manager
and the Support Monitor, or
there is not enough space on
the hard disk drive to install
the Storage Manager and the
Support Monitor.
224
Table 31. Problem index (continued)

Problem
Possible cause
Possible solution
The Support Monitor

console is not responding
There are network problems, or Complete the following steps:

the IP address of the
v Check for network problems.
management station was
v Check the current IP address of the management
changed.
station on which the Support Monitor is installed. If
it is different from the IP address that was
established when the Support Monitor was installed
and configured, you must either change the IP back
to the one that was configured initially or remove
and reinstall the Support Monitor software.
The Support Monitor

prompts for your UserID
and Password
This is erroneous. The system

is not designed to prompt for
your UserID and Password.
Enter admin as the UserID and admin as the

password or remove and reinstall the Storage
Manager client and Support Monitor.
DS Diagnostic Data Capture (DDC)

The DDC function was implemented to assist IBM support in collecting data for troubleshooting unusual
controller-firmware events.
Note: This function is not implemented with controller firmware code versions that are earlier than the
06.12.27.xx level.
Under rare circumstances, an internal controller error can force a routine to perform the Diagnostic Data
Capture (DDC) function. When this occurs, a red stop sign next to the name of the storage subsystem
that has the error (is in a non-optimal state) is displayed in the Enterprise Management window. After
you open the Subsystem Management window for that storage subsystem, you can click the Recovery
Guru. The Recovery Guru shows what the issue is, as does the MEL (Storage Manager Major Events
Log). See DDC MEL events on page 227 for more information about the MEL.
When the DDC function is implemented, the storage subsystem status changes from Optimal to Needs
Attention due to DDC. This occurs under the following conditions:
v The controllers in the storage subsystem detect unusual events such as Master Abort (because of a bad
address that is accessed by the Fibre Channel chip, resulting in a PCI bus error).
v The controller is not able to process host I/O requests for an extended period of time (several minutes).
v The destination device number registry is corrupted.
v An EDC (error detection code) error is returned by the disk drives.
v A quiescence failure occurred in the logical drive that is owned by the alternative controller.
v The records that are related to Storage Partition Management are corrupted.
When the Needs Attention due to DDC flag is set, it is persistent across the power-cycle and controller
reboot, provided that the controller cache batteries are sufficiently charged. In addition, data that reflects
the state of the storage subsystem controllers at the moment that the unusual event occurred is collected
and saved until you retrieve it. To clear the Needs Attention due to DDC flag and to retrieve the saved
diagnostic data, see Recovery steps on page 226.
Because the current DDC function implementation holds the DDC data for only one unusual event at a
time until the DDC data is saved, the SMcli commands must be performed as soon as possible whenever
the Needs Attention due to DDC error occurs, so that the controllers can be ready for capturing data for
any other unusual events. Until the diagnostic data is saved and the Needs Attention due to DDC flag is
cleared, any occurrences of other unusual events do not trigger the controller to capture diagnostic data
for those events. An unusual event invokes a DDC trigger if a previous DDC trigger is at least 48 hours
225
old you have successfully retrieved the previous DDC information. In addition, DDC information is
available only if a controller is online. A controller that is in service or lock-down mode does not trigger a
DDC event. After you collect the DDC data, contact IBM support to report the problem and get assistance
with troubleshooting the condition.
Recovery steps
To perform the DDC recovery process, complete the following steps:
1. Open either the Script Editor from the Enterprise Management window or the command-line interface
(CLI).
Note: See the online help in the Enterprise Management window for more information about the
syntax of these commands.
2. Follow the instructions in the following table, depending on whether you want to save the diagnostic
data.
Table 32. Recovery Step 2
If...
Then...
You want to save the diagnostic data
Go to step 3.
You do not want to save the diagnostic data
Go to step 5.
3. Type
save storageSubsystem diagnosticData file="filename ";
where filename is the location and name of the file that will be saved. The file is initialized as a .zip
file.
Note: The esm parameter of the command syntax is not supported.
4. Follow the instructions in the following table to work with the diagnostic data.
If...
Then...
No error was returned
Go to step 6.
An error was returned
If...
Then...
The error message indicates that

there was a problem saving the data.
Wait 2 minutes, and restart step 3.
The error message indicates that

there was a problem resetting the
data.
Wait 2 minutes, and go to step 5.
5. Type
reset storageSubsystem diagnosticData;
If...
Then...
No error was returned
Go to step 6.
An error was returned
Wait 2 minutes and then run the command again. The

controllers might need additional time to update the
status.
Note: Another error might occur if the diagnostic data
status has already been reset. Go to step 6.
6. Click Recheck to run the Recovery Guru again. The failure is no longer displayed in the Summary
area.
226
After this process has been completed, the DDC message is removed automatically, and a recheck of the
Recovery Guru shows no entries for DDC capture. If for some reason the data has not been removed, the
Recovery Guru provides an example of how to clear the DDC information without saving the data. To
complete the preceding procedure in the script editor, type
reset storageSubsystem diagnosticData;
DDC MEL events

When the Diagnostic Data Capture action is triggered by an unusual event, one or more of the following
events are posted in the storage subsystem event logs, depending on the user actions.
Table 35. DDC MEL events
Event number
Description
Priority
Explanation
0x6900
Diagnostic Data is
available.
Critical
This is logged when an unusual controller event

triggers the DDC function to store Diagnostic
Data.
0x6901
Diagnostic Data
retrieval operation
started.
Informational
This is logged when the user runs the SMcli

command to retrieve and save the Diagnostic
Data, as described in step 3 in Recovery steps
on page 226.
0x6902
Diagnostic Data
retrieval operation
completed.
Informational
This is logged when the Diagnostic Data

retrieval and save completes.
0x6903
Diagnostic Data
Needs Attention
status/flag cleared.
Informational
This is logged when the user resets the Needs

Attention due to DDC flag with the SMcli
command, or when the Diagnostic Data retrieval
and save completes successfully when initiated
by the user with the save storageSubsystem
diagnosticData SMcli command.
Resolving disk array errors on AIX

This section describes the disk array errors that might be reported in the AIX error log. You can view the
AIX error log by using the errpt -a command. You can also check the Storage Manager Major Event log
(MEL) to find out whether there is any correlation between the host, SAN, and storage subsystem.
You might have to validate your configuration or replace defective hardware to correct the situation.
Note: For more troubleshooting information, see the Installation, User's, and Maintenance Guide that came
with your storage subsystem.
Table 36. Disk array errors
Error
number Error name
Error type
Error description
FCP_ARRAY_ERR1
ARRAY OPERATION ERROR
A permanent hardware error involving the

disk array media occurred.
FCP_ARRAY_ERR2
A permanent hardware error occurred.
FCP_ARRAY_ERR3
A permanent error was detected by the array

adapter.
FCP_ARRAY_ERR4
A temporary error occurred within the array,

communications, or adapter.
FCP_ARRAY_ERR5
UNDETERMINED ERROR
An undetermined error occurred.
227
Table 36. Disk array errors (continued)

Error
number Error name
Error type
Error description
FCP_ARRAY_ERR6
SUBSYSTEM COMPONENT
FAILURE
A degradation condition other than a disk

drive occurred.
FCP_ARRAY_ERR7
CONTROLLER HEALTH
CHECK FAILURE
A health check on the passive controller

failed.
FCP_ARRAY_ERR8
ARRAY CONTROLLER
SWITCH
One array controller became unavailable, so

I/O moved to the other controller.
FCP_ARRAY_ERR9
ARRAY CONTROLLER
SWITCH FAILURE
An array controller switch failed.
10
FCP_ARRAY_ERR10
ARRAY CONFIGURATION
CHANGED
A logical unit was moved from one controller

to the other (most likely by the action of an
alternative host).
11
FCP_ARRAY_ERR11
IMPROPER DRIVE TYPE FOR

DUAL ACTIVE MODE
This error is not possible on the 2102 array

and exists for historical purposes only.
FCP_ARRAY_ERR11 might be reused for a
different error in the future.
12
FCP_ARRAY_ERR12
POLLED AEN FAILURE
An automatic error notification failed.
13
FCP_ARRAY_ERR13
ARRAY INTER-CONTROLLER
COMMUNICATION FAILURE
The controllers are unable to communicate

with each other. This error might occur if one
of the controllers is rebooted while the error
log is being generated. However, it might also
indicate a problem with the Fibre Channel
connections.
14
FCP_ARRAY_ERR14
ARRAY DRIVE FAILURE
A serious or unrecoverable error was detected

on a physical disk within the storage
subsystem. A system engineer might be able
to obtain the exact cause from an analysis of
the sense data.
15
FCP_ARRAY_ERR15
CACHE BATTERY LOW/DATA

LOSS POSSIBLE
If a controller card is replaced, the cache

batteries might be drained. It can take two
days for the cache batteries to be recharged.
During this time, errors are logged in the
error log. Do not replace the controller.
16
FCP_ARRAY_ERR16
CACHE BATTERY CHARGE

BELOW 87.5%
If a controller card is replaced, the cache

batteries might be drained. It can take two
days for the cache batteries to be recharged.
During this time, errors are logged in the
error log. Do not replace the controller.
17
FCP_ARRAY_ERR17
WORLDWIDE NAME
CHANGED
A controller has changed worldwide names.

This error might be caused if you replace the
controller without placing it in the reset state
first, or if you change the cabling and a
different controller with the same SCSI ID is
on the loop.
18
FCP_ARRAY_ERR18
RESERVATION CONFLICT
An operation failed because the disk array

logical drive (LUN) is reserved by another
host.
19
FCP_ARRAY_ERR19
SNAPSHOT VOLUME
REPOSITORY FULL
The repository capacity limit was reached. To

resolve this error, increase the repository
capacity.
228

Error
number Error name
Error type
Error description
20
FCP_ARRAY_ERR20
SNAPSHOT OPERATION
STOPPED BY ADMIN
The FlashCopy (snapshot) operation was

disabled or stopped. To resolve this error,
re-create the FlashCopy.
21
FCP_ARRAY_ERR21
SNAPSHOT REPOSITORY
METADATA ERROR
There was a problem with the metadata of

the FlashCopy (snapshot) repository during
the FlashCopy operation. To resolve this error,
re-create the FlashCopy.
22
FCP_ARRAY_ERR22
REMOTE VOL MIRRORING:

ILLEGAL I/O ORIGIN
The primary logical drive received I/O from

a remote array, or the secondary logical drive
received I/O from a source other than the
primary logical drive. To resolve this error,
try the operation again.
23
FCP_ARRAY_ERR23
SNAPSHOT OPERATION NOT

ALLOWED
The repository capacity limit was reached, so

the FlashCopy (snapshot) operation failed. To
resolve this error, delete or re-create the
FlashCopy.
24
FCP_ARRAY_ERR24
SNAPSHOT VOLUME
REPOSITORY FULL
The repository-capacity limit was reached. To

resolve this error, delete or re-create the
FlashCopy (snapshot).
25
FCP_ARRAY_ERR25
CACHED DATA WILL BE LOST This message is a warning that a disk array
IF CONTROLLER FAILS
logical drive (LUN) is running with write
cache enabled and cache mirroring disabled.
The warning is displayed when the LUN is
opened, and it is displayed again every 24
hours until cache mirroring is enabled again.
If a controller fails, or if power to the
controller is turned off while the LUN is
running in this mode, data that is in the write
cache (but not written to the physical disk
media) might be lost. This can cause
corrupted files, file systems, or databases.
26
FCP_ARRAY_ERR26
LOGICAL VOLUME IS WRITE

PROTECTED
The status of the logical drive is read-only.

The probable reason is that it is a secondary
logical drive of a FlashCopy, VolumeCopy, or
remote mirror pair. Determine which
relationship applies to the logical drive.
v For FlashCopy, a status of read-only on the
secondary logical drive usually indicates
that the repository is full.
v For VolumeCopy, both the primary and
secondary logical drives are read-only
during the copy operation. The secondary
logical drive is read-only when the copy
operation is stopped and the copy pair has
not been deleted.
v For remote mirroring, the secondary logical
drive is always read-only, provided that the
mirror is active.
229

Error
number Error name
27
FCP_ARRAY_ERR27
Error type
Error description
SINGLE CONTROLLER
RESTARTED
The storage subsystem is operating as a

single controller, and an error was repaired.
The error might be caused by a
communication or hardware problem, or it
might occur because a LUN was moved to a
controller that does not have a path to the
current host.
If this is a dual-controller storage subsystem,
find the reason that the storage subsystem is
operating in single-controller mode, and
resolve the problem. Possible reasons include
the following causes:
v An HBA, switch port, switch, storage
subsystem port or storage subsystem
controller was unavailable during the last
system restart or the last time the cfgmgr
command was run.
v You removed a path (dac) as part of a Fibre
Channel adapter hot-swap operation.
28
FCP_ARRAY_ERR28
SINGLE CONTROLLER
RESTART FAILURE
The storage subsystem is operating as a

single controller, and the error has not been
repaired. There is a problem with the path
between this host and the storage subsystem
or with the storage subsystem itself. The host
has attempted to communicate with the
storage subsystem, and that communication
has failed.
If the number of retries that is specified in the
ODM attribute switch_retries is reached, the
I/O is failed back to the user.
Repair the error. Then, if this is a
dual-controller storage subsystem, find the
reason that the storage subsystem is
operating in single-controller mode, and
resolve that problem. Possible reasons include
the following causes:
v An HBA, switch port, switch, storage
subsystem port or storage subsystem
controller was unavailable during the last
system restart or the last time the cfgmgr
command was run.
v You removed a path (dac) as part of a Fibre
Channel adapter hot-swap operation.
A new errorlog DISK_ERR7 has been created to notify that a path has been designated as failed because
of a predetermined number of IO errors that occurred on the path. This is normally preceded with other
error logs that represent the actual error that occurred on the path.
230
Appendix A. Host bus adapter settings

This chapter covers the default settings for a variety of host bus adapters (HBAs) suitable for use with
DS3000, DS4000, and DS5000 storage subsystems for Windows, Linux on Intel, VMware ESX, and
NetWare operating systems. All other operating systems and platforms must use the default values. See
the applicable product documentation for more information.
See the readme file that is included in the Fibre Channel host bus adapter BIOS or device driver package
for any up-to-date changes to the settings.
An HBA is used to connect servers to Fibre Channel topologies. Its function is similar to that provided by
network adapters to access LAN resources. The device driver for an HBA is typically responsible for
providing support for a Fibre Channel topology, whether point-to-point, loop, or fabric.
Important: IBM supports the coexistence of DS3000, DS4000, and DS5000 storage subsystems in the
same server, using the same HBAs, only if the application can accommodate the common set of device
and multipath driver time-out settings. The common set of time-out settings consists of the longest
settings that are published in this section for the DS3000, DS4000, and DS5000 storage subsystems. If
this is not possible, and if the multipath driver allows for it, the use of mixed DS3000, DS4000, and
DS5000 storage subsystems can still be achieved if the HBAs that you use for DS3000 subsystems are
different than the ones that you use for DS4000 or DS5000 storage subsystems. Otherwise, the
coexistence of DS3000, DS4000, and DS5000 storage subsystems in the same server is not possible.
See the latest IBM DS controller firmware and Storage Manager readme files for any restrictions on the
coexistence of DS3000, DS4000, and DS5000 storage subsystems in the same server. For detailed HBA
support information, see www.ibm.com/systems/support/storage/config/ssic.
Adjusting HBA settings

It is often necessary to adjust the settings of your HBA to match the capabilities of your device. This
section describes how to access those settings to make the necessary adjustments.
Accessing HBA settings through Fast!UTIL

The Fast!UTIL feature provides access to host bus adapter settings. To access this feature, press Alt+Q or
Ctrl+Q during BIOS initialization. It might take a few seconds for the Fast!UTIL menu to be displayed. If
more than one adapter is installed, Fast!UTIL prompts you to select an adapter to configure. After you
change adapter settings, Fast!UTIL restarts the server to load the new parameters. After you enter
Fast!UTIL, the following selections are available on the Fast!UTIL Options menu:
v Configuration Settings
v Loopback Test
v Select Host Adapter
You can also access the host bus adapter settings through the Configuration Settings menu in Fast!UTIL;
then, select Adapter Settings or Advanced Adapter Settings.
Note: Alternatively, you can also use the QLogic SANsurfer program to modify the Host adapter
settings and Advanced adapter settings preferences from the Microsoft Windows operating-system
environment. You must restart the servers for the changes to become effective.
231
Default host bus adapter settings

Access the host bus adapter settings through the Configuration Settings menu in Fast!UTIL and select
Adapter Settings. The default host bus adapter settings for the FC2-133 HBA are as follows:
Host Adapter BIOS
When this setting is Disabled, the ROM BIOS on the FC2-133 HBA is disabled, and space
becomes available in upper memory. This setting must be Enabled if you are booting from a Fibre
Channel disk drive that is attached to the FC2-133 adapter. The default is Disabled.
Frame Size
This setting specifies the maximum frame length that is supported by the FC2-133 HBA. The
default size is 2048, which provides maximum performance for F-Port (point-to-point)
connections.
Loop Reset Delay
After resetting the loop the firmware refrains from initiating any loop activity for the number of
seconds that is specified in this setting. The default is 5 seconds.
Adapter Hard Loop ID
This setting forces the adapter to attempt to use the ID that is specified in the Hard Loop ID
setting. The default is Enabled.
Hard Loop ID
If the Adapter Hard Loop ID setting is Enabled, the adapter attempts to use the ID that is
specified in this setting. The default ID is 125. Set this ID to a unique value from 0-125 if there is
more than one adapter that is connected to an FC-AL loop and the Adapter Hard Loop ID setting
is Enabled.
Spin Up Delay
When this bit is set, the BIOS waits up to 5 minutes to find the first drive. The default setting is
Disabled.
Connection Options
This setting defines the type of connection (loop or point-to-point) or connection preference. The
default is 2, which is loop preferred unless point-to-point.
Fibre Channel Tape Support
This setting enables FCP-2 recovery. The default is Enabled. Change this setting to Disabled if the
HBA is not connected to a tape device.
Data Rate
This setting determines the data rate. When this setting is 0, the FC2-133 HBA runs at 1 Gbps.
When this setting is 1, the FC2-133 HBA runs at 2 Gbps. When this setting is 2, Fast!UTIL
determines what rate your system can accommodate and sets the rate accordingly. The default is
2 (auto-configure).
Advanced HBA settings

Access the following advanced host bus adapter settings through the Configuration Settings menu in
Fast!UTIL and select Advanced Adapter Settings. The default settings for the FC2-133 HBA are as
follows:
Execution Throttle
This setting specifies the maximum number of commands that execute on any one port. When a
port execution throttle is reached, no new commands are executed until the current command is
finished. The valid options for this setting are 1-256. The default is 255.
LUNs per Target
This setting specifies the number of LUNs per target. Multiple LUN support is typically for
redundant array of independent disks (RAID) systems that use LUNs to map drives. The default
232
is 0. For host operating systems other than Microsoft Windows, you might have to change this
setting to a value other 0 to allow the host to see more than one logical drive from the storage
subsystem.
Enable LIP Reset
This setting determines the type of loop initialization process (LIP) reset that is used when the
operating system initiates a bus reset routine. When this setting is Yes, the driver initiates a global
LIP reset to clear the target device reservations. When this setting is no, the driver initiates a
global LIP reset with full login. The default is No.
Enable LIP Full Login
This setting instructs the ISP chip to log in, again, to all ports after any LIP. The default is Yes.
Enable Target Reset
This setting enables the drivers to issue a Target Reset command to all devices on the loop when
a SCSI Bus Reset command is issued. The default is Yes.
Login Retry Count
This setting specifies the number of times that the software tries to log in to a device. The default
is 30 retries.
Port Down Retry Count
This setting specifies the number of seconds that elapse before the software retries a command to
a port returning port down status. The default is 30 seconds. For the Microsoft Windows servers
in MSCS configuration, the Port Down Retry Count BIOS parameter must be changed from the
default of 30 to 70.
Link Down Timeout
This setting specifies the number of seconds that the software waits for a link down to come up.
The default is 60 seconds.
Extended Error Logging
This setting provides additional error and debug information to the operating system. When it is
enabled, events are logged in the Windows NT Event Viewer. The default is Disabled.
RIO Operation Mode
This setting specifies the reduced interrupt operation (RIO) modes, if supported by the software
driver. RIO modes allow posting multiple command completions in a single interrupt. The
default is 0.
Interrupt Delay Timer
This setting contains the value (in 100-microsecond increments) used by a timer to set the wait
time between accessing (DMA) a set of handles and generating an interrupt. The default is 0.
QLogic host bus adapter settings

Important: IBM supports the coexistence of DS3000, DS4000, and DS5000 storage subsystems in the
same server, using the same HBAs, only if the application can accommodate the common set of device
and multipath driver time-out settings. The common set of time-out settings consists of the longest
settings that are published in this section for the DS3000, DS4000, and DS5000 storage subsystems. If
this is not possible, and if the multipath driver allows for it, the use of mixed DS3000, DS4000, and
DS5000 storage subsystems can still be achieved if the HBAs that you use for DS3000 subsystems are
different than the ones that you use for DS4000 or DS5000 storage subsystems. Otherwise, the
coexistence of DS3000, DS4000, and DS5000 storage subsystems in the same server is not possible.
See the latest IBM DS controller firmware and Storage Manager readme files for any restrictions on the
coexistence of DS3000, DS4000, and DS5000 storage subsystems in the same server. For detailed HBA
support information, see www.ibm.com/systems/support/storage/config/ssic.
233
Note: The BIOS settings in the Windows column are the default values that are set when the adapters are
ordered from IBM as IBM FC-2 (QLA2310), FC2-133 (QLA2340) and single-port and dual-port 4 Gbps
(QLx2460 and QLx2462) Fibre Channel host bus adapters. If the adapters are not from IBM, the default
BIOS might not be the same as those defined in the Microsoft Windows column. There is one exception:
the default setting for Fibre Channel tape support is enabled.
Table 37 shows the default settings for IBM Fibre Channel FC-2 and FC2-133 (QLogic adapter models
QLA2310 and QLA2340) host bus adapter settings (for BIOS V1.35 and later) by operating system as well
as the default registry settings for Microsoft Windows operating systems. DS3000, DS4000, or DS5000
products require BIOS V1.43 or later for these adapters. In addition, these settings are also the default
BIOS settings for the newer DS3000, DS4000, or DS5000 4 Gbps single and dual-port host bus adapters
(QLogic adapter models QLx2460 and QLx2462). The 4 Gbps host bus adapter BIOS version is 1.12 or
later. See the applicable readme file for the latest updates to these values.
Table 37. QLogic model QLA234x, QLA24xx, QLE2462, QLE2460, QLE2560, QLE2562, QMI2572, QMI3572,
QMI2582
Item
Default
Windows
2003 and
Windows Windows
2000
2008
VMware
LINUX
MPP
Solaris
LINUX
DMMP
NetWare
BIOS settings
Host Adapter settings
Host Adapter BIOS
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
2048
2048
2048
2048
2048
2048
2048
2048
Disabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
1251
1251
1251
1251
1251
1251
1251
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Frame Size
Loop Reset Delay
(only for arbitrated
loop topology).
Hard Loop ID (must
be unique for each
HBA) (only for
arbitrated loop
topology).
Spin-up Delay
Connect Options
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled3
Disabled
Disabled
2 (Auto)
2 (Auto)
2 (Auto)
2 (Auto)
2 (Auto)
2 (Auto)
2 (Auto)
Execution Throttle
16
256
256
256
256
256
256
256
LUNs per Target
32
Enable LIP Reset
No
No
No
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Enable Target Reset
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Login Retry Count
30
30
30
30
30
30
30
Port Down Retry

Count (5.30 controller
firmware and earlier)
30
30
30
30
12
12
70
Fibre Channel Tape

Support
Data Rate
Advance Adapter Settings
234
QMI2582 (continued)
Item
Default
VMware
Windows
2003 and
Windows Windows
2000
2008
Solaris
LINUX
MPP
LINUX
DMMP
NetWare
DS3K: 144
DS4K/5K:
702
70
DS3K: 70
DS4K5K:
35
10
70
DS3K:144 DS3K:144
DS4K/
DS4K/5K:
5K: 60
60
60
DS3K:144
DS4K/
5K: 60
NA
60
Disabled
Disabled
Disabled
Disabled
Disabled
256
256
256
256
256
256
256
256
>4 GB Addressing
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Drivers Load RISC

Code
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enable Database
Updates
No
No
No
No
No
No
No
No
Disable Database Load
No
No
No
No
No
No
No
No
Fast Command Posting
Disabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Port Down Retry

Count
70
Link Down Timeout
30
60
Disabled
Disabled
Disabled
RIO Operation Mode
Extended Error
Logging
IOCB Allocation
DS3K:
144
DS4K/
5K: 702
Extended Firmware Settings (1.34 and Earlier)

Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
RIO Operation Mode
Connection Options
Class 2 Service
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
ACK0
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Fibre Channel Tape

Support
Enabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Fibre Channel Confirm
Enabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Command Reference
Number
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Read Transfer Ready
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Response Timer
2 (Auto)
2 (Auto)
2 (Auto)
2 (Auto)
2 (Auto)
2 (Auto)
2 (Auto)
Extended Control
Block
Data Rate
5
REGISTRY SETTINGS
(HKEY_LOCAL_MACHINESystemCurrentControlSetServicesQL2300ParametersDevice)
LargeLuns
MaximumSGList
N/A
N/A
N/A
N/A
N/A
N/A
0x21
0xff
0xff
0xff
N/A
N/A
N/A
N/A
235
QMI2582 (continued)
Item
Default
VMware
Windows
2003 and
Windows Windows
2000
2008
Solaris
LINUX
MPP
LINUX
DMMP
NetWare
O/S REGISTRY SETTINGS

(HKEY_LOCAL_MACHINESystemCurrentControlSetServicesQL2300ParametersDevice) under
DriverParameter variable.
Note:
1. Prior to QLogic driver versions 9.1.x.x, the variable name used was DriverParameters instead of DriverParameter.
2. DriverParameter is of type REG_SZ and the following parameters are added to the DriverParameters string. Do not
create a separate key for each of the parameters.
UseSameNN
N/A
N/A
N/A
N/A
BusChange (SCSIPort
Miniport 9.0.1.60 and
earlier does not apply
to 9.1.1.11 and newer)
N/A
N/A
N/A
N/A
N/A
0x3C
0x78
DS3K:
xA0
DS4K/
5K: x78
DS3K:
xA0
DS4K/5K:
x78
N/A
N/A
N/A
N/A
TimeOutValue 4
(REG_DWORD)
REGISTRY SETTINGS5
(HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices<FAILOVER>parameters: Where
<FAILOVER>=Rdacdisk for MPPor RDAC installations or <FAILOVER>=mppdsm, ds4dsm, md3dsm, sx3dsm,
csmdsm, or tpsdsm for MPIO installations. Mppdsm is for the generic version, your installation could be
different.)
SynchTimeOut
(REG_DWORD)
0x78
N/A
DS3K:
xA0
DS4K/
5K: x78
DS3K:
xA0
DS4K/5K:
x78
DisableLunRebalance
(Only applies to
cluster configurations.
Firmware version
6.xx.xx.xx and later.)
0x00
N/A
0x03
0x03
236
QMI2582 (continued)
Item
Default
VMware
Windows
2003 and
Windows Windows
2000
2008
Solaris
LINUX
MPP
LINUX
DMMP
NetWare
SuSE 7.3 specific modifications:

v Offset 0x11 in the Linux region (6) of the array controller NVSRAM must be changed from the default of 0x20 to
0x7f. The following command can be run from the script engine:
Set controller[a] HOSTNVSRAMByte[6,0x11]=0x7f;
Set controller[b] HOSTNVSRAMByte[6,0x11]=0x7f;
v The QLogic driver source must be modified to reflect the symbolic link used by SuSE.
vi makefile
find OSVER and change it from OSVER=linux-2.4 to OSVER=linux
Save and quit
Red Hat Linux Advanced Server 2.1 / SuSE Linux Enterprise Server 8.0 (6.x series failover driver [with no RDAC]
only). Append the following to the HBA driver option string in the /etc/modules.conf file: ql2xretrycount=60
ql2xsuspendcount=40
If you are running the QLogic Inbox driver, the string options qla2xxx qlport_down_retry=144 (PB1-3) or options
qla2xxx qlport_down_retry=70 (PB4-6) must be added in /etc/modprobe.conf (for RHEL) or /etc/
modprobe.conf.local (for SLES). For all prior (RH3/4 SLES8/9) Linux versions (and out-of-box drivers), the string
options qla2xxx qlport_down_retry=72 (PB1-3) or options qla2xxx qlport_down_retry=35 (PB4-6) must be added
instead.
Note:
1. This setting must be changed to a unique AL-PA value if there is more than one Fibre Channel device in the
FC-AL loop.
2. For larger configurations with heavy I/O loads or in a Microsoft cluster service (MSCS) environment, this value
might be increased.
3. Change this setting to Enabled or Supported when the HBA is connected to a tape device only. Set it to Disabled
when you connect to a DS3000, DS4000, or DS5000 storage subsystem.
4. In certain storage subsystem maximum configuration installations, you might have to set the TimeOutValue to 120
(decimal). Changing this value to a higher value might affect your application especially when it requires the disk
I/O completion acknowledgement within a certain amount of time.
5. You can access registry settings by clicking Start, select Run..., type regedit into the Open: field, and then click
OK.
Attention: Exercise caution when you change the Windows registry. If you change the wrong registry entry or
make an incorrect entry for a setting, you can cause an error that prevents your server from booting or operating
correctly.
Note: The BIOS settings under the Windows column are the default values that are set when the
adapters are ordered from IBM as IBM Fibre Channel host bus adapters. If the adapters are not from
IBM, the default BIOS might not be the same as the ones that are defined in the Microsoft Windows
column. There is one exception: the default setting for Fibre Channel tape support is enabled.
Table 38 shows the default settings for various IBM DS3000, DS4000, or DS5000 Fibre Channel host bus
adapters (QLogic adapter QL220x) models (for BIOS V1.81) by operating system. See the applicable
readme file for the latest updates to these values.
Table 38. QLogic model QL220x (for BIOS V1.81) host bus adapter settings by operating system
Item
Windows
NT
Linux
NetWare
2000 / Server 2003

237
Table 38. QLogic model QL220x (for BIOS V1.81) host bus adapter settings by operating system (continued)
BIOS settings
Host Adapter settings
Disabled
Disabled
Disabled
Disabled
2048
2048
2048
2048
Enabled
Enabled
Enabled
Enabled
Hard Loop ID (must be

unique for each HBA)
1251
1251
1251
1251
Disabled
Disabled
Disabled
Disabled
256
256
256
256
Disabled
Disabled
Disabled
Disabled
LUNs per Target
32
Enable LIP Reset
No
No
No
No
Yes
Yes
Yes
Yes
Enable Target Reset
Yes
Yes
Yes
Yes
Login Retry Count
30
30
30
30
Port Down Retry Count
30
30
12
302
IOCB Allocation
256
256
256
256
Disabled
Disabled
Disabled
Disabled
Enabled
Enabled
Enabled
Enabled
RIO Operation Mode
Connection Options
Class 2 Service
Disabled
Disabled
Disabled
Disabled
ACK0
Disabled
Host Adapter BIOS

Frame Size
Loop Reset Delay
Spin Up Delay
Advanced adapter settings
Execution Throttle
>4 Gbyte Addressing
Extended Error Logging

Extended Firmware Settings
Extended Control Block
Fibre Channel Tape Support
Supported
Disabled
3
Supported
Disabled
3
Supported
Disabled
3
Supported3
Fibre Channel Confirm
Disabled
Disabled
Disabled
Disabled
Command Reference Number
Disabled
Disabled
Disabled
Disabled
Read Transfer Ready
Disabled
Disabled
Disabled
Disabled
Response Timer
Interrupt Delay Time
4
Registry settings (HKEY_LOCAL_MACHINE System CurrentControlSet Services QL2200 Parameters

Device)
1
LargeLuns
MaximumSGList
0x21
0x21
Registry settings (HKEY_LOCAL_MACHINE System CurrentControlSet Services Disk)

TimeOutValue4
(REG_DWORD)
0x3C
0x3C
Registry settings4 (HKEY_LOCAL_MACHINE System CurrentControlSet Services QL2200 Parameters

Device) under the DriverParameter variable
BusChange
238
Table 38. QLogic model QL220x (for BIOS V1.81) host bus adapter settings by operating system (continued)
Note:
1. This setting must be changed to a unique AL-PA value if there is more than one Fibre Channel device in the
FC-AL loop.
2. For larger configurations with heavy I/O loads, change this value to 70.
3. Change this setting to Enable or Supported when the HBA is connected to a tape device only. Set it to Disabled
when you connect to DS3000, DS4000, or DS5000 Storage Subsystem.
4. To access registry settings, click Start, select Run, type regedit into the Open field, and then click OK.
Attention: Exercise caution when you change the Windows registry. If you change the wrong registry entry or
make an incorrect entry for a setting, you can cause an error that prevents your server from booting or operating
correctly.
JNI and QLogic host bus adapter settings

The following tables detail settings for the various host bus adapters (HBA) for Sun Solaris.
Note: JNI host bus adapters are supported only on Solaris 8 and 9. They are not supported on Solaris 10.
JNI HBA card settings

The JNI cards are not Plug and Play with autoconfiguration. Instead, you might have to change the
settings or bindings.
Configuration settings for FCE-1473/FCE-6460/FCX2-6562/FCC2-6562

JNI host bus adapters models FCE-1473, FCE-6460, FCX2-6562, and FCC2-6562 are supported with all
currently supported levels of storage subsystem controller firmware.
Important: For each setting that is listed in Table 39, you must uncomment the line. This is true both for
default settings and for settings that you must change.
Table 39. Configuration settings for FCE-1473/FCE-6460/FCX2-6562/FCC2-6562
Original value
New value
FcLoopEnabled = 1
FcLoopEnabled = 0 (for non-loop; auto-topology)
FcLoopEnabled = 1 (for loop)
FcFabricEnabled = 0
FcFabricEnabled = 0 (for non-fabric; auto-topology)
FcFabricEnabled = 1 (for fabric)
FcEngHeartbeatInterval = 5
Same as original value (in seconds)
FcLinkUpRecoveryTime =
1000
Same as original value (in milliseconds)
BusRetryDelay = 5000
TargetOfflineEnable = 1
TargetOfflineEnable = 0 (Disable)
TargetOfflineEnable = 1 (Enable)
FailoverDelay = 30;
FailoverDelay = 60 (in seconds)
FailoverDelayFcTape = 300
Same as original value (seconds)
TimeoutResetEnable = 0
Same as original value
QfullRetryCount = 5
QfullRetryDelay = 5000
239
Table 39. Configuration settings for FCE-1473/FCE-6460/FCX2-6562/FCC2-6562 (continued)

Original value
New value
LunRecoveryInterval = 50
FcLinkSpeed = 3
JNICreationDelay = 1
JNICreationDelay = 10 (in seconds)
FlogiRetryCount = 3
FcFlogiTimeout = 10
PlogiRetryCount = 3
PlogiControlSeconds = 30
LunDiscoveryMethod = 1
Same as original value (LUN reporting)
CmdTaskAttr = 0
CmdTaskAttr = 0 (Simple Queue)
CmdTaskAttr = 1 (Untagged)
automap = 0
automap = 1 (Enable)
FclpEnable = 1
FclpEnable = 0 (Disable)
OverrunFailoverCount = 0
PlogiRetryTime = 50
SwitchGidPtSyncEnable = 0
target_throttle = 256
lun_throttle = 64
Add these settings.
target0_hba = jnic146x0;
target0_wwpn = <controller wwpn>
target1_wwpn = <controller wwpn>
Note: You might have to run the /etc/raid/bin/genjniconf reconfigure script from the Solaris shell:
# /etc/raid/bin/genjniconf
Configuration settings for FCE-1063/FCE2-1063/FCE-6410/FCE2-6410

JNI host bus adapter models FCE-1063, FCE2-1063, FCE-6410, and FCE2-6410 are supported with all
currently supported levels of storage subsystem controller firmware.
Note: For each setting that is listed in Table 40, you must uncomment the line. This is true both for
Table 40. Configuration settings for FCE-1063/FCE2-1063/FCE-6410/FCE2-6410
Original value
New value
FcLoopEnabled = 1
FcLoopEnabled = 0 (for non-Loop)
FcLoopEnabled = 1 (for Loop)
FcFabricEnabled = 0
FcFabricEnabled = 0 (for non-fabric)
FcFabricEnabled = 1 (for fabric)
FcPortCfgEnable = 1
FcPortCfgEnable = 0 (port reconfiguration not required)
FcPortCfgEnable = 1 (port reconfiguration required)
FcEngHeartbeatInterval = 5
240
Table 40. Configuration settings for FCE-1063/FCE2-1063/FCE-6410/FCE2-6410 (continued)

Original value
New value
FcLrrTimeout = 100
FcLinkUpRecoverTime =
1000
BusyRetryDelay = 5000
FailoverDelay = 30;
FailoverDelay = 60;
TimeoutResetEnable = 0
QfullRetryCount = 5
QfullRetryDelay = 5000
loRecoveryDelay = 50
JniCreationDelay = 5;
JniCreationDelay = 10;
FlogiRetryCount = 3
PlogiRetryCount = 5
FcEmIdEndTcbTimeCount =
1533
target_throttle = 256
Same as original value (default throttle for all targets)
lun_throttle = 64
Same as original value (default throttle for all LUNs)
automap = 0
automap = 0 (persistence binding)
automap = 1 (automapping)
Add these settings.
target0_wwpn = controller wwpn
target1_wwpn = controller wwpn
v You might have to run the /etc/raid/bin/genjniconf reconfigure script from the Solaris shell:
v Set portEnabled = 1; only when you see JNI cards entering non-participating mode in the
/var/adm/messages file. Under that condition, complete the following steps:
1. Set FcPortCfgEnabled = 1;
2. Restart the host.
3. Set FcPortCfgEnabled = 0;
4. Restart the host again.
When you have done so, check /var/adm/messages to make sure that it sets the JNI cards to Fabric
or Loop mode.
Configuration settings for FCI-1063

JNI host bus adapter model FCI-1063 is supported only in storage subsystem configurations with
controller firmware version 05.4x.xx.xx or earlier.
Note: For each setting that is listed in Table 41, you must uncomment the line. This is true both for
Table 41. Configuration settings for FCI-1063
Original value
New value
scsi_initiator_id = 0x7d
241
Table 41. Configuration settings for FCI-1063 (continued)

Original value
New value
fca_nport = 0;
fca_nport = 1 (for the fabric) / fca_nport = 0 (for the loop)
public_loop = 0
target_controllers = 126
ip_disable = 1;
ip_compliant = 0
qfull_retry_interval = 0
qfull_retry_interval = 1000
failover = 30;
failover = 60 (in seconds)
failover_extension = 0
recovery_attempts - 5
class2_enable = 0
fca_heartbeat = 0
reset_glm = 0
timeout_reset_enable = 0
busy_retry_delay= 100;
link_recovery_delay = 1000;
Same as original value. (in milliseconds)
scsi_probe_delay = 500;
scsi_probe_delay = 5000 (in milliseconds; 10 milliseconds resolution)
def_hba_binding = fca-pci*;
def_hba_binding = nonjni; (for binding)
def_hba_binding = fcaw; (for non-binding)
def_wwnn_binding = $xxxxxx
def_wwnn_binding = xxxxxx
def_wwpn_binding = $xxxxxx
Same as the original entry
fca_verbose = 1
Same as the original entry
Will be added by reconfigure script
name=fca-pci parent=physical path unit-address=#
target0_hba=fca-pci0 target0_wwpn=controller wwpn;
name=fca-pci parent=physical pathunit-address=#
target0_hba=fca-pci1 target0_wwpn= controller wwpn;
Note: You might have to run the /etc/raid/bin/genjniconf reconfigure script from the Solaris shell:
Configuration settings for FC64-1063

JNI host bus adapter model FC64-1063 is supported only in storage subsystem configurations with
controller firmware version 05.4x.xx.xx, or earlier.
Important: For each setting that is listed in Table 42, you must uncomment the line. This is true both for
Table 42. Configuration settings for FC64-1063
Original value
New value
fca_nport = 0;
fca_nport =1;
ip_disable = 0;
ip_disable=1;
failover = 0;
failover =30;
242
Table 42. Configuration settings for FC64-1063 (continued)

Original value
New value
busy_retry_delay = 5000;
busy_retry_delay = 5000;
def_hba_binding = fcaw*;
Direct attached configurations:
def_hba_binding = fcaw*;
SAN-attached configurations:
def_hba_binding = nonJNI;
def_wwnn_binding = $xxxxxx def_wwnn_bindindef_hba_ binding = nonjni; g = xxxxxx
def_wwnn_binding = $xxxxxx Same as the original entry
Will be added by reconfigure
script
name=fcaw parent=<physical path>unit-address=<#>

script
target0_hba=fcaw0 target0_wwpn=<controller wwpn>;

script
name=fcaw parent=<physical path>unit-address=<#>

script
target0_hba=fcaw0 target0_wwpn= <controller wwpn>;
Note: You might have to run the /etc/raid/bin/genscsiconf reconfigure script from the shell prompt:
# /etc/raid/bin/genscsiconf
QLogic HBA settings

The QLogic HBAs are not Plug and Play with autoconfiguration. Instead, you must change the settings or
bindings, as described in Table 43.
Note: In Table 43, the HBA is identified as hba0. However, you must modify the settings on both QLogic
HBAs: hba0 and hba1.
When you modify the settings on hba1, use the same values that are listed in the table, but change all
instances of hba0 to hba1, as shown in the following example.
HBA
Original value
New value
hba0
hba0-execution-throttle=16;
hba1
In the vi Editor, uncomment and modify the loop attributes of each QLogic HBA, using the values that
are specified in Table 43.
Table 43. Configuration settings for QL2342
Original value
New value
Comments
max-frame-length=2048;
max-frame-length=2048
Use the default
execution-throttle=16;
execution-throttle=255;
Change
login-retry-count=8;
login-retry-count=30;
Change
enable-adapter-hard-loop-ID=0;
enable-adapter-hard-loop-ID=1;
Change
243
Table 43. Configuration settings for QL2342 (continued)

Original value
New value
Comments
adapter-hard-loop-ID=0;
adapter-hard-loop-ID=0;
Must be a unique number
enable-LIP-reset=0;
enable-LIP-reset=0;
Use the default
hba0-enable-LIP-full-login=1;
hba0-enable-LIP-full-login=1;
Use the default
enable-target-reset=0;
enable-target-reset=0;
Use the default
reset-delay=5
reset-delay=8
Change
port-down-retry-count=8;
port-down-retry-count=70;
Change
maximum-luns-per-target=8;
maximum-luns-per-target=0;
Change
connection-options=2;
connection-options=2;
Use the default
fc-tape=1;
fc-tape=0;
Change
loop-reset-delay = 5;
loop-reset-delay = 8;
Change
> gbyte-addressing = disabled;
> gbyte-addressing = enabled;
Change
link-down-timeout = 30;
link-down-timeout = 60;
Change
244
Appendix B. Using a storage subsystem with a VMware ESX

Server configuration
The Storage Manager software is not currently available for VMware ESX Server operating systems.
Therefore, to manage DS3000, DS4000, and DS5000 storage subsystems with your VMware ESX Server
host, you must install the Storage Manager client software (SMclient) on a Windows or Linux
management station. This can be the same workstation that you use for the browser-based VMware ESX
Server Management Interface.
For additional information about using a DS3000, DS4000, or DS5000 storage subsystem with a VMware
ESX Server host, see VMware ESX Server restrictions on page 247.
You can also see the System Storage Interoperation Center at the following website:
www.ibm.com/systems/support/storage/config/ssic
Sample configuration
Figure 32 shows a sample VMware ESX Server configuration.
Ethernet
Management station
ESX server
Fibre-channel
I/O path
Ethernet
Controller
Controller
Storage subsystems
SJ001150
Figure 32. Sample VMware ESX Server configuration
Software requirements
This section describes the software that is required to use a VMware ESX Server host operating system
with a DS3000, DS4000, or DS5000 storage subsystem.
245
Management station
The following software is required for the Windows or Linux management station:
1. SM Runtime (Linux only)
2. SMclient (Linux and Windows)
Host (VMware ESX Server)

The following software is required for VMware ESX Server:
v VMware ESX Server (with DS3000, DS4000, or DS5000 controller firmware version 07.1x.xx.xx)
v VMware ESX Server-supplied driver for the Fibre Channel HBAs
v VMware ESX Server-supplied QLogic driver failover setup
v VMware ESX Server Tools (installed on all virtual machines using DS3000, DS4000 or DS5000 logical
drives)
Earlier versions of VMware ESX Server:
1. VMware ESX Server 2.1 was supported with DS4000 and DS5000 controller firmware version
06.12.xx.xx only.
2. VMware ESX Server 2.0 was supported with DS4000 and DS5000 controller firmware version
05.xx.xx.xx only.
Guest OS Clustering: If you intend to create a Guest OS cluster configuration, you must use Microsoft
Cluster Services software, in addition to the host software requirements listed in this section.
VMWare Host Clustering: VMware ESX Server 2.5 and higher comes with a Distributed Resource
Scheduler and high availability for clustering, which allows you to aggregate several hosts' resources into
one resource pool. (A DRS cluster is implicitly a resource pool.)
For information about Windows clustering with VMware ESX Server, see the ESX Server 2.5 Installation
Guide at the following website: http://www.vmware.com/support/pubs/.
Hardware requirements
You can use VMware ESX Server host servers with the following types of storage subsystems and storage
expansion enclosures. For additional information, see the System Storage Interoperation Center at the
following website:
Note: For general storage subsystem requirements, see Chapter 1, Preparing for installation, on page 1.
DS5000 Storage Subsystems
v DS5300
v DS5100
DS4000 Storage Subsystems
v DS4100 (Dual-controller units only)
v DS4200
v DS4300 (Dual-controller and Turbo units only)
v DS4400
v DS4500
v DS4700
246
v DS4800
DS5000 storage expansion enclosures
v EXP5000
DS4000 storage expansion enclosures
v EXP100
v EXP420 ( with DS4200 only)
v
v
v
v
EXP500
EXP700
EXP710
EXP810
VMware ESX Server restrictions

SAN and connectivity restrictions:
v VMware ESX Server hosts support host-agent (out-of-band) managed storage subsystem
configurations only. Direct-attached (in-band) management configurations are not supported.
v VMware ESX Server hosts can support multiple host bus adapters (HBAs) and DS3000, DS4000,
and DS5000 devices. However, there is a restriction on the number of HBAs that can be
connected to a single storage subsystem. You can configure up to two HBAs per partition and
up to two partitions per storage subsystem. Additional HBAs can be added for additional
storage subsystems and other SAN devices, up to the limits of your specific storage subsystem
platform.
v When you are using two HBAs in one VMware ESX Server, LUN numbers must be the same
for each HBA attached to the storage subsystem.
v Single HBA configurations are allowed, but each single HBA configuration requires that both
controllers in the storage subsystem be connected to the HBA through a switch. If they are
connected through a switch, both controllers must be within the same SAN zone as the HBA.
Attention: A single HBA configuration might result in loss of data access in the event of a path
failure.
v Single-switch configurations are allowed, but each HBA and storage subsystem controller
combination must be in a separate SAN zone.
v Other storage devices, such as tape devices or other disk storage, must be connected through
separate HBAs and SAN zones.
Partitioning restrictions:
v The maximum number of partitions per VMware ESX Server host, per storage subsystem, is
two.
v
All logical drives that are configured for VMware ESX Server must be mapped to an VMware
ESX Server host group.
Note: VMware ESX server-specific host type is not available for DS3000, DS4000, or DS5000
storage subsystems if the controller firmware version is earlier than 7.70.xx.xx. Use
LNXCLVMWARE host type for your VMware hosts and host groups. If you are using the
default host group, make sure that the default host type is LNXCLVMWARE. DS Storage
subsystems with controller firmware version 7.70.xx.xx or later have a VMware ESX
server-specific host type defined, named VMWARE. VMWARE should be used as the host type
of the VMWare hosts and host group.
v In a DS4100 storage subsystem configuration, you must initially assign the LUNs to Controller
A, on the lowest-numbered HBA. After the LUNs are initialized, you can change the path to
Controller B. (This restriction will be corrected in a future release of ESX Server.)
Appendix B. Using a storage subsystem with a VMware ESX Server configuration
247
v Assign LUNs to the ESX Server starting with LUN number 0.

v Do not map an access (UTM) LUN to any of the ESX Server hosts or host groups. Access
(UTM) LUNs are used only with in-band managed storage subsystem configurations, which
VMware ESX Server does not support at this time.
Failover restrictions:
v You must use the VMware ESX Server failover driver for multipath configurations. Other
failover drivers (such as RDAC) are not supported in VMware ESX Server configurations.
v The default failover policy for all storage subsystems is now MRU (most recently used).
v Use the LNXCLVMWARE (if the controller firmware is earlier than 7.70.xx.xx) or VMWARE (if
the controller firmware is 7.70.xx.xx or later) host type in VMware ESX Server configurations
(2.0 and higher). The LNXCLVMWARE or VMWARE host type automatically disables Auto
Drive Transfer (ADT).
Interoperability restrictions:
v DS4100 and DS4300 single-controller storage subsystems are not supported with VMware ESX
Server hosts. (DS4100 and DS4300 dual-controller storage subsystems are supported.)
v EXP700 storage expansion enclosures are not supported with DS4800storage subsystems. You
must upgrade to EXP710 storage expansion enclosures.
Other restrictions:
v Dynamic Logical Drive Expansion (DVE) is not supported for VMFS-formatted LUNs on
VMware ESX server operating system earlier than 2.5.x. For information about availability of
DS Copy Service features that are supported VMware ESX Server 2.5 Server and higher
configurations, contact your IBM support representative.
v Do not boot your system from a SATA device.
Other VMware ESX Server host information

For more information about setting up your VMware ESX Server host, see the documentation and readme
files that are maintained at the following website:
www.vmware.com/support/pubs/
For information about installing a VMware ESX Server operating system on an IBM server, see the IBM
support website at:
www-03.ibm.com/systems/i/advantages/integratedserver/vmware/
Configuring storage subsystems for VMware ESX Server

Before you can configure a storage subsystem, you must physically configure the host server, SAN fabric,
and storage subsystem controllers; assign initial IP addresses to the controllers; and install SMclient on
the Windows or Linux management station. See Chapter 4, Configuring storage, on page 49 for storage
subsystem configuration procedures.
Cross-connect configuration for VMware connections

A cross-connect Storage Area Network (SAN) configuration is required when VMware hosts are
connected to a DS3000, DS4000, or DS5000 storage subsystem. Each Host Bus Adapter (HBA) in a
VMware host must have a path to each of the controllers in the storage subsystem. Figure 33 on page 249
shows the cross connections for VMware server configurations.
248
Server 1
HBA 1
Server 2
HBA 2
HBA 1
HBA 2
FC Switch
FC Switch
Controller A
Controller B
Storage subsystem
Figure 33. Cross-connect configuration for VMware connections
Mapping LUNs to a storage partition on VMware ESX Server

See Mapping LUNs to a storage partition on page 71 for procedures that describe how to map the
LUNs to a partition. This section contains notes about LUN mapping that are specific to VMware ESX
Servers.
When you map you LUNs on VMware ESX Server, note the following:
v Map the LUNs using consecutive numbers, starting with LUN 0. For example, map LUNs to numbers
0; 1; 2; 3; 4; 5; and so on, without skipping any numbers.
v On each partition, you must map a LUN 0.
v If your configuration does not require LUN sharing (single or multiple independent ESX Servers, local
virtual cluster), each logical drive must be mapped either directly to a host, or to a host group with a
single host as a member.
v LUN sharing across multiple ESX servers is only supported when you are configuring VMotion
enabled hosts or Microsoft Cluster nodes. On LUNs that are mapped to multiple ESX Servers, you
must change the access mode to Shared.
You can map the LUNs to a host group for the ESX Servers, so they will be available to all members of
the host group. For additional information on Windows Clustering with ESX Server, see the ESX
Installation Guide at the following website:
www.vmware.com/support/pubs/
Verifying the storage configuration for VMware

Complete the following steps to verify that your storage subsystem is set up correctly and that you can
see the storage subsystem:
1. Start the server.
2. After QLogic BIOS initialization, press Ctrl+Q to enter the Fast!UTIL setup program.
3. Select the first host bus adapter that is displayed on the Fast!UTIL screen.
4. Select Host Adapter Settings, and press Enter.
Appendix B. Using a storage subsystem with a VMware ESX Server configuration
249
5. Select Scan Fibre Devices and press Enter. The resulting output is similar to the following:
ID
128
129
130
131
132
133
134
135
No
No
No
No
No
No
Scan Fibre Channel Loop

Vendor
Product
Rev
Port Name
No device present
0520
IBM
1742
0520 200400A0b00F0A16 610C00
device present
device present
device present
device present
device present
device present
Port ID
Note: Depending on how the configuration is cabled, you might see multiple instances.
If you do not see a storage subsystem controller, verify the cabling, switch zoning, and LUN mapping.
250
Appendix C. Using the Storage Manager with high-availability

cluster services
The high-availability clustering services provided by the Storage Manager allow application services to
continue when a hardware or software failure occurs. This system protects you from software failures as
well as from the failure of a CPU, disk, or LAN component. If a component fails, its redundant partner
component takes over cluster services and coordinates the transfer between components.
General information
This document does not describe how to install or configure cluster services. See the documentation that
is provided with your cluster service products for this information.
Important: The information in this document might not include up-to-date cluster software version
levels.
For the latest requirements and user information about using the Storage Manager with cluster services,
see the readme file that is located on the Storage Manager DVD for your host operating system, or check
the most recent readme files online.
See Finding Storage Manager software, controller firmware, and readme files on page xiii for
instructions on finding the readme files online.
You can also find more information on the System Storage Interoperation Center, which is maintained at
the following website:
Using cluster services on AIX systems

The following sections contain general hardware requirements and additional information about cluster
services.
Important: The information in this document might not show up-to-date cluster software version levels.
Check the Storage Manager readme file for AIX for up-to-date information about clustering requirements.
See Finding Storage Manager software, controller firmware, and readme files on page xiii for
instructions on finding the readme file on the web.
You can also see the following web sites for the most current information about AIX and clustering:
publib.boulder.ibm.com/infocenter/clresctr/index.jsp
High-Availability Cluster Multi-Processing

This section contains general requirements and usage notes for High Availability Cluster Multi-Processing
(HACMP) support with the Storage Manager.
251
For the latest supported HACMP versions, see the System Storage Interoperation Center at the following
website:
Configuration limitations
The following limitations apply to HACMP configurations:
v HACMP C-SPOC cannot be used to add a DS3000, DS4000, or DS5000 disk to AIX using the Add a Disk
to the Cluster facility.
v HACMP C-SPOC does not support enhanced concurrent mode arrays.
v Single-HBA configurations are allowed, but each single-HBA configuration requires that both
controllers in the storage subsystem be connected to a switch, within the same SAN zone as the HBA.
Attention: Although single-HBA configurations are supported, do not use them in HACMP
environments because they introduce a single point-of-failure in the storage I/O path.
v Use switched fabric connections between the host nodes and the storage subsystem. Direct attachment
from the host nodes to the storage subsystem in an HACMP environment is supported only if all the
following restrictions and limitations are met:
Only dual-controller DS3000, DS4000, or DS5000 storage subsystem versions are supported for direct
attachment in a high-availability configuration.
The AIX operating system must be version 05.2 or later.
The HACMP clustering software must be version 05.1 or later.
All host nodes that are directly attached to the storage subsystem must be part of the same HACMP
cluster.
All logical drives (LUNs) that are surfaced by the storage subsystem are part of one or more
enhanced concurrent mode arrays.
The array varyon is in the active state only on the host node that owns the HACMP non-concurrent
resource group (which contains the enhanced concurrent mode array or arrays). For all other host
nodes in the HACMP cluster, the enhanced concurrent mode array varyon is in the passive state.
Direct operations on the logical drives in the enhanced concurrent mode arrays cannot be
performed, from any host nodes in the HACMP cluster, if the operations bypass the Logical
VolumeManager (LVM) layer of the AIX operating system. For example, you cannot use a DD
command while logged in as the root user.
Each host node in the HACMP cluster must have two Fibre Channel connections to the storage
subsystem. One direct Fibre Channel connection must be to controller A in the storage subsystem,
and the other direct Fibre Channel connection must be to controller B in the storage subsystem.
You can directly attach a maximum of two host nodes in an HACMP cluster to a dual-controller
version of a DS4100 or DS4300 storage subsystem.
You can directly attach a maximum of two host nodes in an HACMP cluster to a storage subsystem.
Each host node must have two direct Fibre Channel connections to the storage subsystem.
Note: In a DS3000, DS4000, or DS5000 storage subsystem, the two direct Fibre Channel connections
from each host node must be to independent minihubs. Therefore, this configuration requires that
four host minihubs (feature code 3507) be installed in the DS3000, DS4000, or DS5000 storage
subsystemtwo host minihubs for each host node in the HACMP cluster.
Other HACMP usage notes

The following notations are specific to HACMP environments:
252
v HACMP clusters can support from two to 32 servers on each DS3000, DS4000, and DS5000 storage
subsystem partition. If you run this kind of environment, be sure to read and understand the AIX
device drivers queue depth settings that are described in Setting the queue depth for hdisk devices
on page 124.
v You can attach non-clustered AIX hosts to a storage subsystem that is running the Storage Manager
and is attached to an HACMP cluster. However, you must configure the non-clustered AIX hosts on
separate host partitions on the storage subsystem.
Parallel System Support Programs and General Parallel File System

This section contains general requirements and usage notes for Parallel System Support Programs (PSSP)
and General Parallel File System (GPFS) support with the Storage Manager.
For the latest supported PSSP and GPFS versions, see the System Storage Interoperation Center at the
following website:
Configuration limitations
The following limitations apply to PSSP and GPFS configurations:
v Direct connection is not allowed between the host node and a DS3000, DS4000, or DS5000 storage
subsystem. Only switched fabric connection is allowed.
v RVSD clusters can support up to two IBM Virtual Shared Disk and RVSD servers for each storage
subsystem partition.
v Single node quorum is not supported in a dual-node GPFS cluster with DS3000, DS4000, or DS5000
disks in the configuration.
v Heterogeneous configurations are not supported.
Other PSSP and GPFS usage notes

In GPFS file systems, the following DS3000, DS4000, and DS5000 storage subsystem cache settings are
supported:
v Read cache enabled or disabled
v Write cache enabled or disabled
v Cache mirroring enabled or disabled (depending upon the write cache mirroring setting)
The performance benefits of read or write caching depends on the application.
GPFS, PSSP, and HACMP cluster configuration diagrams

The diagrams in this section show both the preferred and failover paths from an HBA pair to a given
logical drive or set of logical drives.
A preferred path to a logical drive is determined when the logical drive is created and distributed across
a storage subsystem controller. The controller to which it is assigned determines which path is preferred
or active for I/O transfer. Logical drives can, and in most cases must, be assigned to both controllers,
balancing the I/O load across HBAs and storage subsystem controllers.
Figure 34 on page 254 shows a cluster configuration that contains a single DS storage subsystem, with
one to four partitions.
Appendix C. Using the Storage Manager with high-availability cluster services
253
Preferred
Failover
RVSD Cluster
FCHA0 FC
VSD 1
FCHA1 FC
Server
pair
1
DS4000 Storage Server

Fabric zone 1
Partition 1
FC
SW
WWPN-1A
LUN 0
WWPN-1B
LUN 31
CTLR A
WWPN-2A
WWPN-1A
WWPN-2A
WWPN-1B
WWPN-2B
Port 0
FCHA0 FC
Port 1
VSD 2
FCHA1 FC
WWPN-2B
Partition 2
Fabric zone 4
FCHA0 FC
VSD 7
Server
pair
4
Partition 3
FC fabric 5
FC
SW
WWPN-7A
CTLR B
FCHA1 FC
WWPN-7B
Port 0
WWPN-8A
Port 1
Partition 4
LUN 1
FCHA0 FC
VSD 8
LUN 31
WWPN-7A
WWPN-8A
WWPN-7B
WWPN-8B
FCHA1 FC
WWPN-8B
FC fabric 8
SJ001031
Figure 34. Cluster configuration with single storage subsystemone to four partitions
Figure 35 on page 255 shows a cluster configuration that contains three DS storage subsystems, with one
partition on each storage subsystem.
254
Preferred
Failover
Port 0 CTLR A
Partition 1
Fabric zone 1
FC
SW
Port 1
Port 0 CTLR B
LUN 0
LUN 31
RVSD Cluster
WWPN-1A
WWPN-1A
WWPN-2A
WWPN-1B
WWPN-2B
Port 1
FCHA0 FC
VSD 1
Port 0 CTLR A
FCHA1 FC
WWPN-1B
WWPN-2A
Port 1
Port 0 CTLR B
FCHA0 FC
FCHA1 FC
LUN 0
LUN 31
Fabric zone 2
FC
SW
VSD 2
Partition 1
WWPN-1A
WWPN-2A
WWPN-1B
WWPN-2B
Port 1
WWPN-1B

Port 0 CTLR A
Partition 1
Port 1
Port 0 CTLR B
LUN 0
LUN 31
WWPN-1A
WWPN-2B
WWPN-1B
WWPN-2B
Port 1
SJ001032
Figure 35. Cluster configuration with three storage subsystemsone partition per subsystem
Figure 36 on page 256 shows a cluster configuration that contains four DS storage subsystems, with one
partition on each storage subsystem.
255
Preferred
Failover
DS4000 Storage Server #1
Port 0 CTLR A
Partition 1
Port 1
Port 0 CTLR B
RVSD Cluster
FC
WWPN-1A
WWPN-1B FC
WWPN-1C FC
WWPN-1D FC

Port 0 CTLR A
Partition 1
Port 1
VSD 2
WWPN-1A
WWPN-1B
WWPN-1C
WWPN-1D
LUN 31
Port 1
FC
SW
Fabric zone 1
VSD 1
LUN 0
Port 0 CTLR B
FC
LUN 0
LUN 31
FC
FC
WWPN-1A
WWPN-2A
WWPN-1B
WWPN-2B
WWPN-1A
WWPN-2A
WWPN-1B
WWPN-2B
Port 1
FC
FC
SW
Fabric zone 2
Port 0 CTLR A
Partition 1
Port 1
Port 0 CTLR B
LUN 0
LUN 31
WWPN-1C
WWPN-2C
WWPN-1D
WWPN-2D
Port 1

Port 0 CTLR A
Partition 1
Port 1
Port 0 CTLR B
LUN 0
LUN 31
Port 1
WWPN-1C
WWPN-2C
WWPN-1D
WWPN-2D
SJ001033
Figure 36. Cluster configuration with four storage subsystemsone partition per subsystem
Figure 37 on page 257 shows a cluster configuration that contains two DS storage subsystems, with two
partitions on each storage subsystem.
256
Preferred
Failover
FC
SW
Fabric zone 1
LUN 0
RVSD Cluster
Port 0 CTLR B
FC
Partition 2
FC
Port 1
FC
LUN 0
FC
VSD 2
FC
Fabric zone 2
FC
FC
Fabric zone 3
LUN 31
WWPN-1A
WWPN-2A
WWPN-1C
WWPN-2C
WWPN-1B
WWPN-2B
WWPN-1D
WWPN-2D
FC
FC
SW
WWPN-2A
WWPN-2B
WWPN-2C
WWPN-2D
LUN 31
Port 1
VSD 1
WWPN-1A
WWPN-1B
WWPN-1C
WWPN-1D
Partition 1
Port 0 CTLR A
Partition 1
Port 0 CTLR A
LUN 0
LUN 31
Port 1
Port 0 CTLR B
Port 1
Partition 2
LUN 0
LUN 31
WWPN-1A
WWPN-2A
WWPN-1C
WWPN-2C
WWPN-1B
WWPN-2B
WWPN-1D
WWPN-2D
Fabric zone 4
SJ001034
Figure 37. RVSD cluster configuration with two storage subsystemstwo partitions per subsystem
Figure 38 on page 258 shows an HACMP/GPFS cluster configuration that contains a single DS storage
subsystem, with one partition.
257
WWPN-1A
HACMP/GPFS Cluster
Preferred
Failover
WWPN-1B
Fabric zone 1
WWPN-2A
FC
SW
Svr 1
Svr 2
CTLR A
WWPN-2B
WWPN-3A
Svr 3
Primary:
WWPN-1A
WWPN-2A
WWPN-3A
WWPN-4A
.
.
.
WWPN-32A
Partition 1
WWPN-3B
Svr 4
LUN 0
Fabric zone 2
WWPN-4B
Port 1
WWPN-32A
LUN 31
CTLR B
FC
SW
WWPN-4A
Failover:
WWPN-1B
WWPN-2B
WWPN-3B
WWPN-4B
.
.
.
WWPN-32B
Svr 32
WWPN-32B
SJ001035
Figure 38. HACMP/GPFS cluster configuration with one storage subsystemone partition
Figure 39 on page 259 shows an HACMP/GPFS cluster configuration that contains two DS storage
subsystems, with two partitions on each storage subsystem.
258
Preferred
Failover
HACMP/GPFS Cluster
FC
Partition 1
FC
FC
Svr 2
WWPN-2A
WWPN-2B
WWPN-2C
WWPN-2D
Fabric zone 1
Port 0
FC
SW
WWPN-1A
WWPN-1B
WWPN-1C
WWPN-1D
FC
Port 1
CTLR A
LUN 0
FC
CTLR B
FC
FC
Port 0
FC
Port 1
Partition 2
LUN 0
Svr 3
FC
FC
FC
LUN 31
Fabric zone 2
FC
Partition 1
CTLR A
Port 0
LUN 0
Port 1
CTLR B
WWPN-32A
WWPN-32B
WWPN-32C
WWPN-32D
Fabric zone 4
LUN 31
Partition 2
Port 0
Svr 32
WWPN-1B
WWPN-2B
WWPN-3B
WWPN-32B
WWPN-1D
WWPN-2D
WWPN-3D
WWPN-32D
Fabric zone 3
FC
SW
WWPN-3A
WWPN-3B
WWPN-3C
WWPN-3D
LUN 31
WWPN-1A
WWPN-2A
WWPN-3A
WWPN-32A
WWPN-1C
WWPN-2C
WWPN-3C
WWPN-32C
Port 1
FC
LUN 0
FC
FC
LUN 31
WWPN-1A
WWPN-2A
WWPN-3A
WWPN-32A
WWPN-1C
WWPN-2C
WWPN-3C
WWPN-32C
WWPN-1B
WWPN-2B
WWPN-3B
WWPN-32B
WWPN-1D
WWPN-2D
WWPN-3D
WWPN-32D
FC
SJ001036
Svr 1
Figure 39. HACMP/GPFS cluster configuration with two storage subsystemstwo partitions per subsystem
Using cluster services on HP-UX systems

The information in this document might not show up-to-date cluster software version levels. Check the
Storage Manager readme file for HP-UX for up-to-date information about clustering requirements. See
Finding Storage Manager software, controller firmware, and readme files on page xiii for instructions
on finding the readme file online.
You can choose among many configurations when you set up clustering on an HP-UX system. A
minimum configuration consists of two servers that are configured with both a primary and two standby
LANs to establish a heartbeat LAN.
Provide Fibre Channel connections to the storage subsystem through two switches that provide the
necessary redundant data path for the hosts. Make sure that each server has two HP Tachyon host bus
adapters.
259
Using cluster services on Solaris systems

The following sections contain general hardware requirements and additional information about cluster
services.
Important: The information in this document might not show up-to-date cluster software version levels.
Check the Storage Manager readme file for Solaris for up-to-date information about clustering
requirements, including the latest supported versions of Veritas Cluster Server. See Finding Storage
Manager software, controller firmware, and readme files on page xiii for instructions on finding the
readme file online.
General Solaris requirements

Each Solaris system in the cluster requires the following hardware:
v At least three Ethernet ports:
Two for the private network connections
At least one for the public network connection
v Two Fibre Channel host bus adapters for connection to the storage subsystem
v A SCSI connection for operating system disks
v Each Veritas Cluster Server system requires at least 128 MB of RAM and 35 MB of free disk space
System dependencies
This section provides information about RDAC IDs and single points of failure.
Adding RDAC IDs

You can add up to eight additional IDs to the /etc/symsm/rmparams file. Complete the following steps to
add them:
1. Open the /etc/symsm/rmparams file in the vi Editor by typing the following command:
# vi /etc/symsm/rmparams
2. Modify the Rdac_HotAddIDs line as follows:

Rdac_HotAddIDs:0:1:2:3:4:5:6:7:8
3. Save and close the /etc/symsm/rmparams file.
Single points of failure

When setting up cluster services, it is important to eliminate single points of failure because a single
point of failure makes a cluster only as strong as its weakest component. Set up the storage subsystem for
shared storage; for example, all the nodes in the cluster must recognize the same storage and the host
types must be set correctly.
260
Appendix D. Viewing and setting AIX Object Data Manager

(ODM) attributes
Some of the ODM attributes are for information purposes only. These information-only attributes show
how the storage subsystem is configured or its current state. You can modify other attributes using SMIT
or with the UNIX chdev -p command.
Attribute definitions
The following tables list definitions and values of the ODM attributes for dars, dacs and hdisks:
v Table 44: Attributes for dar devices
v Table 45 on page 262: Attributes for dac devices
v Table 46 on page 263: Attributes for hdisk devices
Note:
1. Attributes with True in the Changeable column can be modified from their default settings.
2. Attributes with False in the Changeable column are for informational or state purposes only.
However, some attributes with False in the Changeable column can be modified using the Storage
Manager.
3. The lsattr -El (uppercase E, lowercase L) command is another way to determine which attributes
can be modified. Attributes that can be modified display True in the last column of the lsattr -El
output. You can also display the default values with the lsattr -Dl command.
Table 44. Attributes for dar devices
Attribute
Definition
Changeable (T/F)
Possible value
act_controller
List of controllers in the

active state at the time of
configuration.
False
Set at configuration time by

the RDAC software.
all_controller
List of controllers that

False
comprise this array; usually
there are two dac devices.

the RDAC software.
held_in_reset
Name of the controller that True

was in the held-in-reset
state at the time of
configuration, or none if no
controllers were in that
state.

the RDAC software. Must
not be changed.
load_balancing
Indicator that shows

whether load balancing is
enabled (yes) or disabled
(no); see the definition of
the balance_freq attribute for
more information.
True
Yes or No.
Attention: You must only
set the load_balancing
attribute to yes in
single-host configurations.
autorecovery

whether the device returns
the array to dual-active
mode when it detects
proper operation of both
paths and controllers (yes)
or not (no).
True
Yes or No. See restrictions

on use.
261
Table 44. Attributes for dar devices (continued)

Attribute
Definition
Changeable (T/F)
Possible value
hlthchk_freq
Number that specifies how

often health checks are
performed, in seconds.
True
1 - 9999. Must not be

changed.
aen_freq

often polled AEN checks
are performed, in seconds.
True

changed.
balance_freq
If load_balancing is enabled, True

number that specifies how
often the system performs
load-balancing on the array,
in seconds.
1 - 9999 - Must not be

changed.
fast_write_ok

whether fast-write
write-caching is available
for this system (yes) or not
(no).
False
Yes or No. State of the

storage subsystem
configuration.
cache_size
Cache size for both

controllers, in megabytes; 0
if the sizes do not match.
False
512 or 1024. Set by the

storage subsystem.
switch_retries

many times to retry failed
switches, in integers.
True
0 - 255.
Default: 5
For most configurations, the
default is the best setting. If
you are using HACMP, it
can be helpful to set the
value to 0.
Attention: You cannot use
concurrent firmware
download if you change the
default setting.
Table 45. Attributes for dac devices

Attribute
Definition
passive_control

False
whether this controller was
in passive state at the time
of configuration (yes) or not
(no).
Yes or No. State of the storage

subsystem configuration.
alt_held_reset

whether the alternate
controller was in the
held-in-reset state at the
time of configuration (yes)
or not (no).
False
Yes or No. State of the storage

subsystem configuration.
controller_SN
Serial number of this

controller.
False
Set by the storage subsystem.
ctrl_type
Type of array to which this

controller belongs.
False
1742, 1722, 1742-900. Set by the

storage subsystem.
cache_size
Cache size of this controller, False

in megabytes.
262
Changeable (T/F)
Possible value
512, 1024. Set by the storage

subsystem.
Table 45. Attributes for dac devices (continued)

Attribute
Definition
Changeable (T/F)
Possible value
scsi_id
SCSI identifier of this

controller.
False
Set by SAN, reported by AIX.
lun_id
Logical unit number of this

controller.
False
utm_lun_id
Logical unit number of this False

controller, or none if UTM
(access logical drives) is not
enabled.
0 - 31. Set by the Storage Manager.
node_name
Name of the Fibre Channel

node.
False
location
User-defined location label

for this controller; the
system does not use this
value.
True
Set by the Storage Manager.
ww_name
Fibre Channel worldwide

name of this controller.
False
GLM_type
GLM type used for this

controller.
False
High or Low. Set by the storage

subsystem.
Table 46. Attributes for hdisk devices

Attribute
Definition
Changeable (T/F)
Possible value
pvid
AIX physical volume

False
identifier, or none if not set.
Set by AIX.
q_type
Queueing type for this

device; must be set to
simple.
False
Set by AIX. Must be

simple.
queue_depth
Number that specifies the

depth of the queue based
on system configuration;
reduce this number if the
array is returning a BUSY
status on a consistent basis.
True
1 - 64
Note: See Setting the
queue depth for hdisk
devices on page 124 for
important information
about setting this attribute.
PR_key_value
Required only if the device

supports any of the
persistent reserve policies.
This attribute is used to
distinguish between
different hosts.
True
1-64, or None.
Note: You must set this
attribute to non-zero before
the reserve_policy attribute
is set.
reserve_policy
Persistent reserve policy,

which defines whether a
reservation methodology is
employed when the device
is opened.
True
no_reserve
PR_shared,
PR_exclusive, or
single_path
max_transfer
True
Maximum transfer size is
the largest transfer size that
can be used in sending I/O.
Numeric value;
Default = 1 MB
Note: Usually unnecessary
to change default, unless
very large I/Os require
increasing the value.
Appendix D. Viewing and setting AIX Object Data Manager (ODM) attributes
263
Table 46. Attributes for hdisk devices (continued)

Attribute
Definition
Changeable (T/F)
Possible value
write_cache
False
whether write-caching is
enabled on this device (yes)
or not (no); see the
definition of the
cache_method attribute for
more information.
Yes or No.
size
Size of this logical drive.
False
Set by the storage

subsystem.
raid_level

RAID level of this device.
False
0, 1, 3, 5. Set by the Storage

Manager.
rw_timeout

read/write timeout value
for each read/write
command to this array, in
seconds; usually set to 30.
True

changed from default.
reassign_to

timeout value for FC
reassign operations, in
seconds; usually set to 120.
True

changed from default.
scsi_id
SCSI identifier at the time

of configuration.
False
Set by SAN, reported by

AIX.
lun_id
Logical unit number of this

device.
False
0 - 255. Set by the Storage

Manager.
cache_method
If write_cache is enabled, the False

write-caching method of
this array; set to one of the
following:
Default, fast_write,
fast_load, fw_unavail,
fl_unavail.
v default. Default mode;

the word "default" is not
seen if write_cache is set
to yes.
v fast_write. Fast-write
(battery-backed, mirrored
write-cache) mode.
v fw_unavail. Fast-write
mode was specified but
could not be enabled;
write-caching is not in
use.
v fast_load. Fast-load
(non-battery-backed,
non-mirrored
write-cache) mode.
v fl_unavail. Fast-load
mode was specified but
could not be enabled.
prefetch_mult
264
Number of blocks to be
prefetched into read cache
for each block read.
False
0 - 100.
Table 46. Attributes for hdisk devices (continued)

Attribute
Definition
Changeable (T/F)
Possible value
ieee_volname
IEEE unique logical drive

name identifier for this
logical drive.
False
Set by the storage

subsystem.
Using the lsattr command to view ODM attributes

To view the Object Data Manager (ODM) attribute settings for dars, dacs, and hdisks, use the lsattr
command, as follows:
v To view the default settings, type lsattr -Dl.
v To view the attributes that are currently set on the system, type lsattr -El.
The lsattr -El output examples shown in Table 47, Table 48, and Table 49 on page 266, display the ODM
attribute settings for a dar, a dac and an hdisk.
Table 47. Example 1: Displaying the attribute settings for a dar
# lsattr -El dar0
act_controller dac0,dac1
aen_freq
600
all_controller dac0,dac1
autorecovery
no
balance_freq
600
cache_size
128
fast_write_ok yes
held_in_reset none
hlthchk_freq
600
load_balancing no
switch_retries 5
Active Controllers
Polled AEN frequency in seconds
Available Controllers
Dynamic Load Balancing frequency in seconds
Cache size for both controllers
Fast Write available
Held-in-reset controller
Health check frequency in seconds
Dynamic Load Balancing
Number of times to retry failed switches
False
True
False
True
True
False
False
True
True
True
True
Table 48. Example 2: Displaying the attribute settings for a dac

# lsattr -El dac0
GLM_type
low
alt_held_reset no
cache_size
128
controller_SN
1T24594458
ctrl_type
1722-600
location
lun_id
0x0
node_name
0x200200a0b80f14af
passive_control no
scsi_id
0x11000
utm_lun_id
0x001f000000000000
ww_name
0x200200a0b80f14b0
GLM type
Alternate held in reset
Cache Size in MBytes
Controller serial number
Controller Type
Location Label
Logical Unit Number
FC Node Name
Passive controller
SCSI ID
Logical Unit Number
World Wide Name
False
False
False
False
False
True
False
False
False
False
False
False
Note: Running the # lsattr -Rl <device> -a <attribute> command, will show allowable values for the
specified attribute and is an hdisk attribute list when using MPIO.
Note: In Table 49 on page 266, the ieee_volname and lun_id attribute values are shown abbreviated. An
actual output would show the values in their entirety.
Appendix D. Viewing and setting AIX Object Data Manager (ODM) attributes
265
Table 49. Example 3: Displaying the attribute settings for an hdisk

lsattr -El hdisk174
cache_method
fast_write
ieee_volname
600A0B8...1063F7076A7
lun_id
0x0069...000000
prefetch_mult 12
pvid
none
q_type
simple
queue_depth
2
raid_level
5
reassign_to
120
reserve_lock
yes
rw_timeout
30
scsi_id
0x11f00
size
2048
write_cache
yes
266
Write Caching method

False
IEEE Unique volume name
False
Logical Unit Number
False
Multiple of blocks to prefetch on read False
Physical volume identifier
False
Queuing Type
False
Queue Depth
True
RAID Level
False
Reassign Timeout value
True
RESERVE device on open
True
Read/Write Timeout value
True
SCSI ID
False
Size in Mbytes
False
Write Caching enabled
False
Appendix E. Accessibility
The information in this appendix describes documentation accessibility and accessibility features in
Storage Manager.
Document format
The publications for this product are in Adobe Portable Document Format (PDF) and must be compliant
with accessibility standards. If you experience difficulties when you use the PDF files and want to request
a web-based format or accessible PDF document for a publication, direct your mail to the following
address:
Information Development
IBM Corporation
205/A015
3039 E. Cornwallis Road
P.O. Box 12195
Research Triangle Park, North Carolina 27709-2195
U.S.A.
In the request, be sure to include the publication part number and title.
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.
Accessibility features in Storage Manager

This section provides information about alternate keyboard navigation, which is a Storage Manager
accessibility feature. Accessibility features help a user who has a physical disability, such as restricted
mobility or limited vision, to use software products successfully.
With the alternate keyboard operations that are described in this section, you can use keys or key
combinations to perform Storage Manager tasks and initiate many menu actions that can also be done
with a mouse.
Note: In addition to the keyboard operations that are described in this section, the Storage Manager
version 9.14 - 10.10 (and later) software installation packages for Windows include a screen reader
software interface.
To enable the screen reader, select Custom Installation when using the installation wizard to install
Storage Manager 9.14 - 10.10 (or later) on a Windows host/management station. Then, in the Select
Product Features window, select Java Access Bridge, in addition to the other required host software
components.
Table 50 on page 268 defines the keyboard operations that enable you to navigate, select, or activate user
interface components. The following terms are used in the table:
v Navigate means to move the input focus from one user interface component to another.
v Select means to choose one or more components, typically for a subsequent action.
v Activate means to carry out the action of a particular component.
Note: In general, navigation between components requires the following keys:
v Tab - Moves keyboard focus to the next component or to the first member of the next group of
components
267
v Shift-Tab - Moves keyboard focus to the previous component or to the first component in the previous
group of components
v Arrow keys - Move keyboard focus within the individual components of a group of components
Table 50. Storage Manager alternate keyboard operations
Short cut
Action
F1
Open the Help.
F10
Move keyboard focus to main menu bar and post first menu; use the
arrow keys to navigate through the available options.
Alt+F4
Close the management window.
Alt+F6
Move keyboard focus between dialogs (non-modal) and between

management windows.
Alt+ underlined letter
Access menu items, buttons, and other interface components with the
keys associated with the underlined letters.
For the menu options, select the Alt + underlined letter combination to
access a main menu, and then select the underlined letter to access the
individual menu item.
For other interface components, use the Alt + underlined letter
combination.
Ctrl+F1
Display or conceal a tool tip when keyboard focus is on the toolbar.
Spacebar
Select an item or activate a hyperlink.
Ctrl+Spacebar
(Contiguous/Non-contiguous)
AMW Logical/Physical View
Select multiple drives in the Physical View.

To select multiple drives, select one drive by pressing Spacebar, and
then press Tab to switch focus to the next drive you want to select;
press Ctrl+Spacebar to select the drive.
If you press Spacebar alone when multiple drives are selected then all
selections are removed.
Use the Ctrl+Spacebar combination to deselect a drive when multiple
drives are selected.
This behavior is the same for contiguous and non-contiguous selection
of drives.
End, Page Down
Move keyboard focus to the last item in the list.
Esc
Close the current dialog. Does not require keyboard focus.
Home, Page Up
Move keyboard focus to the first item in the list.
Shift+Tab
Move keyboard focus through components in the reverse direction.
Ctrl+Tab
Move keyboard focus from a table to the next user interface component.
Tab
Navigate keyboard focus between components or select a hyperlink.
Down arrow
Move keyboard focus down one item in the list.
Left arrow
Move keyboard focus to the left.
Right arrow
Move keyboard focus to the right.
Up arrow
Move keyboard focus up one item in the list.
268
Notices
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 give 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.
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:
269
IBM Corporation
Almaden Research
650 Harry Road
Bldg 80, D3-304, Department 277
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.
All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without
notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to change before the
products described become available.
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.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs
in any form without payment to IBM, for the purposes of developing, using, marketing or distributing
application programs conforming to the application programming interface for the operating platform for
which the sample programs are written. These examples have not been thoroughly tested under all
conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these
programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
Each copy or any portion of these sample programs or any derivative work, must include a copyright
notice as follows:
(your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs.
270
Copyright IBM Corp. _enter the year or years_.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked
terms are marked on their first occurrence in this information with a trademark symbol ( or ), these
symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information
was published. Such trademarks may also be registered or common law trademarks in other countries.
A current list of IBM trademarks is available on the web at http://www.ibm.com/legal/copytrade.shtml.
The following terms are trademarks of International Business Machines Corporation in the United States,
other countries, or both:
IBM
AIX
eServer
FlashCopy
Netfinity
POWER
Series p
RS/6000
TotalStorage
Adobe and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in
the United States and/or other countries.
Intel, Intel Xeon, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or
its subsidiaries in the United States and other countries.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc., in the United States, other
countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, and Windows NT are 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.
Other company, product, or service names may be trademarks or service marks of others.
Important notes
Processor speed indicates the internal clock speed of the microprocessor; other factors also affect
application performance.
This product is not intended to be connected directly or indirectly by any means whatsoever to interfaces
of public telecommunications networks.
CD or DVD drive speed is the variable read rate. Actual speeds vary and are often less than the possible
maximum.
Notices
271
When referring to processor storage, real and virtual storage, or channel volume, KB stands for 1024
bytes, MB stands for 1,048,576 bytes, and GB stands for 1,073,741,824 bytes.
When referring to hard disk drive capacity or communications volume, MB stands for 1,000,000 bytes,
and GB stands for 1,000,000,000 bytes. Total user-accessible capacity can vary depending on operating
environments.
Maximum internal hard disk drive capacities assume the replacement of any standard hard disk drives
and population of all hard disk drive bays with the largest currently supported drives that are available
from IBM.
Maximum memory might require replacement of the standard memory with an optional memory
module.
IBM makes no representation or warranties regarding non-IBM products and services that are
ServerProven, including but not limited to the implied warranties of merchantability and fitness for a
particular purpose. These products are offered and warranted solely by third parties.
IBM makes no representations or warranties with respect to non-IBM products. Support (if any) for the
non-IBM products is provided by the third party, not IBM.
Some software might differ from its retail version (if available) and might not include user manuals or all
program functionality.
272
Glossary
This glossary provides definitions for the
terminology and abbreviations used in IBM
System Storage publications.
(PCI) bus. AGP reduces the overall cost of

creating high-end graphics subsystems
with existing system memory.
If you do not find the term you are looking for,

see the IBM Glossary of Computing Terms located at
the following website:
access logical drive

A logical drive that allows the host-agent
to communicate with the controllers in
the storage subsystem.
http://www.ibm.com/ibm/terminology
adapter
This glossary also includes terms and definitions

from:
v Information Technology Vocabulary by
Subcommittee 1, Joint Technical Committee 1,
of the International Organization for
Standardization and the International
Electrotechnical Commission (ISO/IEC
JTC1/SC1). Definitions are identified by the
symbol (I) after the definition; definitions taken
from draft international standards, committee
drafts, and working papers by ISO/IEC
JTC1/SC1 are identified by the symbol (T) after
the definition, indicating that final agreement
has not yet been reached among the
participating National Bodies of SC1.
v IBM Glossary of Computing Terms. New York:
McGraw-Hill, 1994.
The following cross-reference conventions are
used in this glossary:
See
Refers you to (a) a term that is the

expanded form of an abbreviation or
acronym, or (b) a synonym or more
preferred term.
See also
Refers you to a related term.
Abstract Windowing Toolkit (AWT)
In Java programming, a collection of GUI
components that were implemented using
native-platform versions of the
components. These components provide
that subset of functionality which is
common to all operating system
environments.
accelerated graphics port (AGP)
A bus specification that gives low-cost 3D
graphics cards faster access to main
memory on personal computers than the
usual peripheral component interconnect
A printed circuit assembly that transmits

user data input/output (I/O) between the
internal bus of the host system and the
external Fibre Channel (FC) link and vice
versa. Also called an I/O adapter, host
adapter, or FC adapter.
advanced technology (AT) bus architecture
A bus standard for IBM compatibles. It
extends the XT bus architecture to 16 bits
and also allows for bus mastering,
although only the first 16 MB of main
memory are available for direct access.
agent
A server program that receives virtual

connections from the network manager
(the client program) in a Simple Network
Management Protocol-Transmission
Control Protocol/Internet Protocol
(SNMP-TCP/IP) network-managing
environment.
AGP
See accelerated graphics port.
AL_PA
See arbitrated loop physical address.
arbitrated loop
One of three existing Fibre Channel
topologies, in which 2 - 126 ports are
interconnected serially in a single loop
circuit. Access to the Fibre Channel
Arbitrated Loop (FC-AL) is controlled by
an arbitration scheme. The FC-AL
topology supports all classes of service
and guarantees in-order delivery of FC
frames when the originator and responder
are on the same FC-AL. The default
topology for the disk array is arbitrated
loop. An arbitrated loop is sometimes
referred to as a Stealth Mode.
arbitrated loop physical address (AL_PA)
An 8-bit value used to identify a
273
participating device in an arbitrated loop.

A loop can have one or more AL_PAs.
array
A collection of Fibre Channel or SATA

hard drives that are logically grouped
together. All the drives in the array are
assigned the same RAID level. An array is
sometimes referred to as a "RAID set." See
also redundant array of independent disks
(RAID), RAID level.
asynchronous write mode

In remote mirroring, an option that allows
the primary controller to return a write
I/O request completion to the host server
before data has been successfully written
by the secondary controller. See also
synchronous write mode, remote mirroring,
Global Copy,Global Mirroring.
AT
See advanced technology (AT) bus

architecture.
ATA
See AT-attached.
AT-attached
Peripheral devices that are compatible
with the original IBM AT computer
standard in which signals on a 40-pin
AT-attached (ATA) ribbon cable followed
the timings and constraints of the
Industry Standard Architecture (ISA)
system bus on the IBM PC AT computer.
Equivalent to integrated drive electronics
(IDE).
Auto Drive Transfer (ADT)
A function that provides automatic
failover in case of controller failure on a
storage subsystem.
ADT
See Auto Drive Transfer .
AWT
See Abstract Windowing Toolkit.
Basic Input/Output System (BIOS)

The code that controls basic hardware
operations, such as interactions with
diskette drives, hard disk drives, and the
keyboard.
BIOS
See basic input/output system.
BOOTP
See bootstrap protocol.
Bootstrap Protocol (BOOTP)
A protocol that allows a client to find
both its Internet Protocol (IP) address and
the name of a file from a server on the
network.
274
bridge A storage area network (SAN) device that

provides physical and transport
conversion, such as Fibre Channel to
small computer system interface (SCSI)
bridge.
bridge group
A bridge and the collection of devices
connected to it.
broadcast
The simultaneous transmission of data to
more than one destination.
cathode ray tube (CRT)
A display device in which controlled
electron beams are used to display
alphanumeric or graphical data on an
electroluminescent screen.
client
A software program or computer that

requests services from a server. Multiple
clients can share access to a common
server.
command
A statement used to initiate an action or
start a service. A command consists of the
command name abbreviation, and its
parameters and flags if applicable. A
command can be issued by typing it on a
command line or selecting it from a
menu.
community string
The name of a community contained in
each Simple Network Management
Protocol (SNMP) message.
concurrent download
A method of downloading and installing
firmware that does not require the user to
stop I/O to the controllers during the
process.
CRC
See cyclic redundancy check.
CRT
See cathode ray tube.
CRU
See customer replaceable unit.
customer replaceable unit (CRU)

An assembly or part that a customer can
replace. Contrast with field replaceable unit
(FRU).
cyclic redundancy check (CRC)
(1) A redundancy check in which the
check key is generated by a cyclic
algorithm. (2) An error detection
technique performed at both the sending
and receiving stations.
dac
See disk array controller.
dar
See disk array router.
domain
The most significant byte in the node port
(N_port) identifier for the Fibre Channel
(FC) device. It is not used in the Fibre
Channel-small computer system interface
(FC-SCSI) hardware path ID. It is required
to be the same for all SCSI targets
logically connected to an FC adapter.
DASD
See direct access storage device.
data striping
Storage process in which information is
split into blocks (a fixed amount of data)
and the blocks are written to (or read
from) a series of disks in parallel.
default host group
A logical collection of discovered host
ports, defined host computers, and
defined host groups in the
storage-partition topology that fulfill the
following requirements:
v Are not involved in specific logical
drive-to-LUN mappings
v Share access to logical drives with
default logical drive-to-LUN mappings
device type
Identifier used to place devices in the
physical map, such as the switch, hub, or
storage.
DHCP See Dynamic Host Configuration Protocol.
direct access storage device (DASD)
A device in which access time is
effectively independent of the location of
the data. Information is entered and
retrieved without reference to previously
accessed data. (For example, a disk drive
is a DASD, in contrast with a tape drive,
which stores data as a linear sequence.)
DASDs include both fixed and removable
storage devices.
direct memory access (DMA)
The transfer of data between memory and
an input/output (I/O) device without
processor intervention.
disk array controller (dac)
The device, such as a Redundant Array of
Independent Disks (RAID), that manages
one or more disk arrays and provides
functions. See also disk array router.
disk array router (dar)
A router that represents an entire array,
including current and deferred paths to
all logical unit numbers (LUNs) (hdisks
on AIX). See also disk array controller.
drive channels
The DS4200, DS4700, and DS4800
subsystems use dual-port drive channels
that, from the physical point of view, are
connected in the same way as two drive
loops. However, from the point of view of
the number of drives and enclosures, they
are treated as a single drive loop instead
of two different drive loops. A group of
storage expansion enclosures are
connected to the DS3000 or DS4000
storage subsystems using a drive channel
from each controller. This pair of drive
channels is referred to as a redundant
drive channel pair.
drive loops
A drive loop consists of one channel from
each controller combined to form one pair
of redundant drive channels or a
redundant drive loop. Each drive loop is
associated with two ports. (There are two
drive channels and four associated ports
per controller.) For the DS4800, drive
loops are more commonly referred to as
drive channels. See drive channels.
DRAM
See dynamic random access memory.
Dynamic Host Configuration Protocol (DHCP)
A communications protocol that is used to
centrally manage configuration
information. For example, DHCP
automatically assigns IP addresses to
computers in a network.
dynamic random access memory (DRAM)
Storage in which the cells require
repetitive application of control signals to
retain stored data.
ECC
See error correction code.
EEPROM
See electrically erasable programmable
read-only memory.
EISA
See Extended Industry Standard Architecture.
DMA See direct memory access.
Glossary
275
electrically erasable programmable read-only

memory (EEPROM)
A type of memory chip which can retain
its contents without consistent electrical
power. Unlike the PROM which can be
programmed only once, the EEPROM can
be erased electrically. Because it can only
be reprogrammed a limited number of
times before it wears out, it is appropriate
for storing small amounts of data that are
changed infrequently.
electrostatic discharge (ESD)
The flow of current that results when
objects that have a static charge come into
close enough proximity to discharge.
environmental service module (ESM) canister
A component in a storage expansion
enclosure that monitors the environmental
condition of the components in that
enclosure. Not all storage subsystems
have ESM canisters.
E_port See expansion port.
error correction coding (ECC)
A code appended to a data block that has
the capability to detect and correct
multiple bit errors within the block. Most
ECCs are characterized by the maximum
number of errors they can detect and
correct.
ESD
See electrostatic discharge.
ESM canister
See environmental service module canister.
automatic ESM firmware synchronization
When you install a new ESM into an
existing storage expansion enclosure in a
DS3000 or DS4000 storage subsystem that
supports automatic ESM firmware
synchronization, the firmware in the new
ESM is automatically synchronized with
the firmware in the existing ESM.
EXP
See storage expansion enclosure.
expansion port (E_port)

In the building of a larger switch fabric, a
port used as an inter-switch expansion
port to connect to the E_port of another
switch.
Extended Industry Standard Architecture (EISA)
The PC bus standard that extends the AT
bus (ISA bus) to 32 bits and provides
support for bus master. It was announced
in 1988 as a 32-bit alternative to the Micro
276
Channel that would preserve investment

in existing boards. PC and AT adapters
(ISA adapters) can plug into an EISA bus.
See also Industry Standard Architecture.
fabric A Fibre Channel entity which
interconnects and facilitates logins of
N_ports attached to it. The fabric is
responsible for routing frames between
source and destination N_ports using
address information in the frame header.
A fabric can be as simple as a
point-to-point channel between two
N-ports, or as complex as a frame-routing
switch that provides multiple and
redundant internal pathways within the
fabric between F_ports.
fabric port (F_port)
In a fabric, an access point for connecting
a user's N_port. An F_port facilitates
N_port logins to the fabric from nodes
connected to the fabric. An F_port is
addressable by the N_port connected to it.
See also fabric.
FC
See Fibre Channel.
FC-AL See arbitrated loop.

feature enable identifier
A unique identifier for the storage
subsystem, which is used in the process
of generating a premium feature key. See
also premium feature key.
Fibre Channel (FC)
A technology for transmitting data
between computer devices. It is especially
suited for attaching computer servers to
shared storage devices and for
interconnecting storage controllers and
drives. FC supports point-to-point,
arbitrated loop, and switched topologies.
Fibre Channel Arbitrated Loop (FC-AL)
See arbitrated loop.
Fibre Channel Protocol (FCP) for small computer
system interface (SCSI)
A high-level Fibre Channel mapping layer
(FC-4) that uses lower-level Fibre Channel
(FC-PH) services to transmit SCSI
commands, data, and status information
between a SCSI initiator and a SCSI target
across the FC link with FC frame and
sequence formats.
field replaceable unit (FRU)
An assembly that is replaced in its
entirety when any one of its components

fails. In some cases, a field replaceable
unit might contain other field replaceable
units. Contrast with customer replaceable
unit (CRU).
FlashCopy
An optional feature of the Storage System
DS family that can make an instant copy
of data, that is, a point-in-time copy of a
logical drive.
F_port See fabric port.
FRU
See field replaceable unit.
GBIC See gigabit interface converter

gigabit interface converter (GBIC)
An encoding/decoding device that is a
class-1 laser component assembly with
transmitting and receiving receptacles that
connect to fiber-optic cables. GBICs
perform a serial optical-to-electrical and
electrical-to-optical conversion of the
signal. The GBICs in the switch can be
hot-swapped. See also small form-factor
pluggable.
Global Copy
Refers to a remote logical drive mirror
pair that is set up using asynchronous
write mode without the write consistency
group option. This is also referred to as
"Asynchronous Mirroring without
Consistency Group." Global Copy does
not make sure that write requests to
multiple primary logical drives are
carried out in the same order on the
secondary logical drives as they are on
the primary logical drives. If it is critical
that writes to the primary logical drives
are carried out in the same order in the
appropriate secondary logical drives,
Global Mirroring must be used instead of
Global Copy. See also asynchronous write
mode, Global Mirroring, remote mirroring,
Metro Mirroring.
Global Mirror
An optional capability of the remote
mirror and copy feature that provides a
two-site extended-distance remote copy.
Data that is written by the host to the
storage unit at the local site is
automatically maintained at the remote
site. See also asynchronous write mode,
Global Copy, remote mirroring, Metro
Mirroring.
graphical user interface (GUI)

A type of computer interface that presents
a visual metaphor of a real-world scene,
often of a desktop, by combining
high-resolution graphics, pointing devices,
menu bars and other menus, overlapping
windows, icons and the object-action
relationship.
GUI
See graphical user interface.
HBA
See host bus adapter.
hdisk An AIX term representing a logical unit

number (LUN) on an array.
heterogeneous host environment
A host system in which multiple host
servers, which use different operating
systems with their own unique disk
storage subsystem settings, connect to the
same storage subsystem at the same time.
See also host.
host
A system that is directly attached to the

storage subsystem through a Fibre
Channel input/output (I/O) path. This
system is used to serve data (typically in
the form of files) from the storage
subsystem. A system can be both a
management station and a host
simultaneously.
host bus adapter (HBA)

An interface card that connects a host
bus, such as a peripheral component
interconnect (PCI) bus, to the storage area
network.
host computer
See host.
host group
An entity in the storage partition
topology that defines a logical collection
of host computers that require shared
access to one or more logical drives.
host port
Ports that physically reside on the host
adapters and are automatically discovered
by the Storage Manager software. To give
a host computer access to a partition, its
associated host ports must be defined.
hot-swap
Pertaining to a device that is capable of
being replaced while the system is on.
hub
In a network, a point at which circuits are

either connected or switched. For
Glossary
277
example, in a star network, the hub is the

central node; in a star/ring network, it is
the location of wiring concentrators.
IBMSAN driver
The device driver that is used in a Novell
NetWare environment to provide
multipath input/output (I/O) support to
the storage controller.
IC
See integrated circuit.
IDE
See integrated drive electronics.
in-band
Transmission of management protocol
over the Fibre Channel transport.
Industry Standard Architecture (ISA)
Unofficial name for the bus architecture of
the IBM PC/XT personal computer. This
bus design included expansion slots for
plugging in various adapter boards. Early
versions had an 8-bit data path, later
expanded to 16 bits. The "Extended
Industry Standard Architecture" (EISA)
further expanded the data path to 32 bits.
See also Extended Industry Standard
Architecture.
initial program load (IPL)
The process that loads the system
programs from the system auxiliary
storage, checks the system hardware, and
prepares the system for user operations.
Also referred to as a system restart,
system startup, and boot.
integrated circuit (IC)
A microelectronic semiconductor device
that consists of many interconnected
transistors and other components. ICs are
constructed on a small rectangle cut from
a silicon crystal or other semiconductor
material. The small size of these circuits
allows high speed, low power dissipation,
and reduced manufacturing cost
compared with board-level integration.
Also known as a chip.
integrated drive electronics (IDE)
A disk drive interface based on the 16-bit
IBM personal computer Industry Standard
Architecture (ISA) in which the controller
electronics reside on the drive itself,
eliminating the need for a separate
adapter card. Also known as an
Advanced Technology Attachment
Interface (ATA).
278
Internet Protocol (IP)

A protocol that routes data through a
network or interconnected networks. IP
acts as an intermediary between the
higher protocol layers and the physical
network.
Internet Protocol (IP) address
A unique address for a device or logical
unit on a network that uses the IP
standard. For example, 9.67.97.103 is an IP
address.
interrupt request (IRQ)
An input found on a processor that
causes it to suspend normal instruction
execution temporarily and to start
executing an interrupt handler routine.
IP
See Internet Protocol.
IPL
See initial program load.
IRQ
See interrupt request.
ISA
See Industry Standard Architecture.
Java runtime environment (JRE)

A subset of a Java developer kit that
contains the core executable programs
and files that constitute the standard Java
platform. The JRE includes the Java
virtual machine (JVM), core classes, and
supporting files.
JRE
See Java Runtime Environment.
label
A discovered or user-entered property

value that is displayed underneath each
device in the Physical and Data Path
maps.
LAN
See local area network.
LBA
See logical block address.
local area network (LAN)

A network that connects several devices
in a limited area (such as a single
building or campus) and that can be
connected to a larger network.
logical block address (LBA)
The address of a logical block. Logical
block addresses are typically used in host'
I/O commands. The SCSI disk command
protocol, for example, uses logical block
addresses.
logical partition (LPAR)
A subset of a single system that contains
resources (processors, memory, and
input/output devices). A logical partition
operates as an independent system. If

hardware requirements are met, multiple
logical partitions can exist within a
system.
A fixed-size portion of a logical drive. A
logical partition is the same size as the
physical partitions in its array. Unless the
logical drive of which it is a part is
mirrored, each logical partition
corresponds to, and its contents are stored
on, a single physical partition.
One to three physical partitions (copies).
The number of logical partitions within a
logical drive is variable.
logical unit number (LUN)
In the Small Computer System Interface
(SCSI) standard, a unique identifier used
to differentiate devices, each of which is a
logical unit (LU).
loop address
The unique ID of a node in Fibre Channel
loop topology sometimes referred to as a
loop ID.
loop group
A collection of storage area network
(SAN) devices that are interconnected
serially in a single loop circuit.
loop port
A port used to connect a node to a Fibre
Channel Arbitrated Loop (FC-AL).
LPAR See logical partition.
LUN
See logical unit number.
MAC
See medium access control.
Management Information Base (MIB)

In the Simple Network Management
Protocol (SNMP), a database of objects
that can be queried or set by a network
management system.
A definition for management information
that specifies the information available
from a host or gateway and the
operations allowed.
management station
A system that is used to manage the
storage subsystem. A management station
does not need to be attached to the
storage subsystem through the Fibre
Channel input/output (I/O) path.
man page
In UNIX systems, one page of online
documentation. Each UNIX command,
utility, and library function has an
associated man page.
MCA
See micro channel architecture.
media scan
A media scan is a background process
that runs on all logical drives in the
storage subsystem for which it has been
enabled, providing error detection on the
drive media. The media scan process
scans all logical drive data to verify that it
can be accessed, and optionally scans the
logical drive redundancy information.
Media Access Control (MAC)
In networking, the lower of two sublayers
of the Open Systems Interconnection
model data link layer. The MAC sublayer
handles access to shared media, such as
whether token passing or contention will
be used.
metro mirror
A function of the remote mirror and copy
feature that constantly updates a
secondary copy of a logical drive to
match changes made to a source logical
drive. See also remote mirroring, Global
Mirroring.
MIB
See management information base.
Micro Channel architecture (MCA)

The rules that define how subsystems and
adapters use the Micro Channel bus in a
computer. MCA defines the services that
each subsystem can or must provide.
Microsoft Cluster Server (MSCS)
A technology that provides high
availability by grouping computers into
MSCS clusters. If one of the computers in
the cluster hits any one of a range of
problems, MSCS shuts down the
disrupted application in an orderly
manner, transfers its state data to another
computer in the cluster, and re-initiates
the application there.
mini hub
An interface card or port device that
receives short-wave fiber channel GBICs
or SFPs. These devices enable redundant
Fibre Channel connections from the host
computers, either directly or through a
Fibre Channel switch or managed hub,
Glossary
279
over optical fiber cables to the DS3000

and DS4000 Storage Server controllers.
Each DS3000 and DS4000 controller is
responsible for two mini hubs. Each mini
hub has two ports. Four host ports (two
on each controller) provide a cluster
solution without use of a switch. Two
host-side mini hubs are shipped as
standard. See also host port, gigabit
interface converter (GBIC), small form-factor
pluggable (SFP).
mirroring
A fault-tolerance technique in which
information on a hard disk is duplicated
on additional hard disks. See also remote
mirroring.
model The model identification that is assigned
to a device by its manufacturer.
MSCS See Microsoft Cluster Server.
network management station (NMS)
Protocol (SNMP), a station that runs
management application programs that
monitor and control network elements.
NMI
See non-maskable interrupt.
NMS
See network management station.
non-maskable interrupt (NMI)

A hardware interrupt that another service
request cannot overrule (mask). An NMI
bypasses and takes priority over interrupt
requests generated by software, the
keyboard, and other such devices and is
issued to the microprocessor only in
disastrous circumstances, such as severe
memory errors or impending power
failures.
A physical device that allows for the
transmission of data within a network.
node
node port (N_port)

A Fibre Channel defined hardware entity
that performs data communications over
the Fibre Channel link. It is identifiable by
a unique worldwide name. It can act as
an originator or a responder.
nonvolatile storage (NVS)
A storage device whose contents are not
lost when power is cut off.
N_port
NVSRAM
Nonvolatile storage random access
memory. See nonvolatile storage.
Object Data Manager (ODM)
An AIX proprietary storage mechanism
for ASCII stanza files that are edited as
part of configuring a drive into the
kernel.
ODM See Object Data Manager.
out-of-band
Transmission of management protocols
outside of the Fibre Channel network,
typically over Ethernet.
partitioning
See storage partition.
parity check
A test to determine whether the number
of ones (or zeros) in an array of binary
digits is odd or even.
A mathematical operation on the
numerical representation of the
information communicated between two
pieces. For example, if parity is odd, any
character represented by an even number
has a bit added to it, making it odd, and
an information receiver checks that each
unit of information has an odd value.
PCI local bus
See peripheral component interconnect local
bus.
PDF
See portable document format.
performance event
Event related to thresholds set on storage
area network (SAN) performance.
Peripheral Component Interconnect local bus
(PCI local bus)
A local bus for PCs, from Intel, that
provides a high-speed data path between
the CPU and up to 10 peripherals (video,
disk, network, and so on). The PCI bus
coexists in the PC with the Industry
Standard Architecture (ISA) or Extended
Industry Standard Architecture (EISA)
bus. ISA and EISA boards plug into an IA
or EISA slot, while high-speed PCI
controllers plug into a PCI slot. See also
Industry Standard Architecture, Extended
Industry Standard Architecture.
See node port.

NVS
280
See nonvolatile storage.

polling delay
The time in seconds between successive
discovery processes during which
discovery is inactive.
port
A part of the system unit or remote

controller to which cables for external
devices (such as display stations,
terminals, printers, switches, or external
storage units) are attached. The port is an
access point for data entry or exit. A
device can contain one or more ports.
portable document format (PDF)

A standard specified by Adobe Systems,
Incorporated, for the electronic
distribution of documents. PDF files are
compact; can be distributed globally via
e-mail, the Web, intranets, CD-ROM or
DVD-ROM; and can be viewed with the
Acrobat Reader.
premium feature key
A file that the storage subsystem
controller uses to enable an authorized
premium feature. The file contains the
feature enable identifier of the storage
subsystem for which the premium feature
is authorized, and data about the
premium feature. See also feature enable
identifier.
private loop
A Fibre Channel Arbitrated Loop (FC-AL)
with no fabric attachment. See also
arbitrated loop.
program temporary fix (PTF)
For System i, System p, and System z
products, a fix that is tested by IBM and
is made available to all customers.
PTF
See program temporary fix.
RAID See redundant array of independent disks

(RAID).
RAID level
An array RAID level is a number that
refers to the method used to achieve
redundancy and fault tolerance in the
array. See also array, redundant array of
independent disks (RAID).
RAID set
See array.
RAM
See random access memory.
random access memory (RAM)

Computer memory in which any storage
location can be accessed directly. Contrast
with DASD.
RDAC
See redundant disk array controller.
read-only memory (ROM)
Memory in which stored data cannot be
changed by the user except under special
conditions.
recoverable virtual shared disk (RVSD)
A virtual shared disk on a server node
configured to provide continuous access
to data and file systems in a cluster.
Redundant Array of Independent Disks (RAID)
A collection of two or more physical disk
drives (or an array) that present to the
host an image of one or more logical disk
drives. In the event of a physical device
failure, the data can be read or
regenerated from the other disk drives in
the array due to data redundancy. See
also array, parity check, mirroring, RAID
level, striping.
redundant disk array controller (RDAC)
In hardware, a redundant set of
controllers (either active/passive or
active/active).
In software, a layer that manages the
input/output (I/O) through the active
controller during normal operation and
transparently reroutes I/Os to the other
controller in the redundant set if a
controller or I/O path fails.
remote mirroring
Online, real-time replication of data
between storage subsystems that are
maintained on separate media. The
Enhanced Remote Mirror Option is a
premium feature that provides support
for remote mirroring. See also Global
Mirroring, Metro Mirroring.
ROM
See read-only memory.
router A computer that determines the path of

network traffic flow. The path selection is
made from several paths based on
information obtained from specific
protocols, algorithms that attempt to
identify the shortest or best path, and
other criteria such as metrics or
protocol-specific destination addresses.
Glossary
281
RVSD See recoverable virtual shared disk.

SAI
See Storage Subsystem Identifier.
SA Identifier
See storage subsystem Identifier.
SAN
See storage area network.
SATA See serial ATA.

scope
SCSI
Defines a group of controllers by their

Internet Protocol (IP) addresses. A scope
must be created and defined so that
dynamic IP addresses can be assigned to
controllers on the network.
See small computer system interface.
segmented loop port (SL_port)

A port that allows division of a Fibre
Channel private loop into multiple
segments. Each segment can pass frames
around as an independent loop and can
connect through the fabric to other
segments of the same loop.
sense data
Data sent with a negative response,
indicating the reason for the response.
Data describing an I/O error. Sense data
is presented to a host system in response
to a sense request command.
serial ATA
The standard for a high-speed alternative
to small computer system interface (SCSI)
hard drives. The SATA-1 standard is
equivalent in performance to a 10 000
RPM SCSI drive.
Serial Storage Architecture (SSA)
An American National Standards Institute
(ANSI) standard, implemented by IBM,
for a high-speed serial interface that
provides point-to-point connection for
peripherals, such as storage subsystems.
SSA, which is compatible with small
computer system interface (SCSI) devices,
allows full-duplex packet multiplexed
serial data transfers at rates of 20 Mbps in
each direction.
server A software program or a computer that
provides services to other software
programs or other computers.
server/device events
Events that occur on the server or a
designated device that meet criteria that
the user sets.
282
SFP
See small form-factor pluggable.
Simple Network Management Protocol (SNMP)

A set of protocols for monitoring systems
and devices in complex networks.
Information about managed devices is
defined and stored in a Management
Information Base (MIB).
SL_port
See segmented loop port.
SMagent
The Storage Manager optional Java-based
host-agent software, which can be used
on Microsoft Windows, Novell NetWare,
AIX, HP-UX, Solaris, and Linux on
POWER host systems to manage storage
subsystems through the host Fibre
Channel connection.
SMclient
The Storage Manager client software,
which is a Java-based graphical user
interface (GUI) that is used to configure,
manage, and troubleshoot storage servers
and storage expansion enclosures in a
storage subsystem. SMclient can be used
on a host system or on a management
station.
SMruntime
A Java compiler for the SMclient.
SMutil
The Storage Manager utility software that
is used on Microsoft Windows, AIX,
HP-UX, Solaris, and Linux on POWER
host systems to register and map new
logical drives to the operating system. In
Microsoft Windows, it also contains a
utility to flush the cached data of the
operating system for a particular drive
before creating a FlashCopy.
Small Computer System Interface (SCSI)
An ANSI-standard electronic interface
that allows personal computers to
communicate with peripheral hardware,
such as disk drives, tape drives, CD-ROM
or DVD-ROM drives, printers, and
scanners faster and more flexibly than
previous interfaces.
A standard hardware interface that
enables a variety of peripheral devices to
communicate with one another.
small form-factor pluggable (SFP)
An optical transceiver that is used to
convert signals between optical fiber

cables and switches. An SFP is smaller
than a gigabit interface converter (GBIC).
See also gigabit interface converter.
SNMP
See Simple Network Management Protocol
and SNMPv1.
SNMP trap event
An event notification sent by the SNMP
agent that identifies conditions, such as
thresholds, that exceed a predetermined
value. See also Simple Network
Management Protocol.
SNMPv1
The original standard for SNMP is now
referred to as SNMPv1, as opposed to
SNMPv2, a revision of SNMP. See also
Simple Network Management Protocol.
SRAM
See static random access memory.
SSA
system unit to provide additional storage

and processing capacity.
storage partition
Storage subsystem logical drives that are
visible to a host computer or are shared
among host computers that are part of a
host group.
storage partition topology
In the Storage Manager client, the
Topology view of the Mappings window
displays the default host group, the
defined host group, the host computer,
and host-port nodes. The host port, host
computer, and host group topological
elements must be defined to grant access
to host computers and host groups using
logical drive-to-LUN mappings.
striping
See data striping.
subnet
A network divided into smaller
independent subgroups, which still are
interconnected.
See serial storage architecture.
static random access memory (SRAM)

Random access memory based on the
logic circuit know as flip-flop. It is called
static because it retains a value as long as
power is supplied, unlike dynamic
random access memory (DRAM), which
must be regularly refreshed. It is however,
still volatile, meaning that it can lose its
contents when the power is turned off.
storage area network (SAN)
A dedicated storage network tailored to a
specific environment, combining servers,
storage products, networking products,
software, and services. See also fabric.
Storage Subsystem Identifier (SAI or SA
Identifier)
The Storage Subsystem Identifier is the
identification value used by the Storage
Manager host software (SMClient) to
uniquely identify each managed storage
server. The Storage Manager SMClient
program maintains Storage Subsystem
Identifier records of previously-discovered
storage servers in the host resident file,
which allows it to retain discovery
information in a persistent fashion.
storage expansion enclosure (EXP), or storage
enclosure
A feature that can be connected to a
sweep method
A method of sending Simple Network
Management Protocol (SNMP) requests
for information to all the devices on a
subnet by sending the request to every
device in the network.
switch A Fibre Channel device that provides full
bandwidth per port and high-speed
routing of data with link-level addressing.
switch group
A switch and the collection of devices
connected to it that are not in other
groups.
switch zoning
See zoning.
synchronous write mode
In remote mirroring, an option that
requires the primary controller to wait for
the acknowledgment of a write operation
from the secondary controller before
returning a write I/O request completion
to the host. See also asynchronous write
mode, remote mirroring, Metro Mirroring.
system name
Device name assigned by the vendor
third-party software.
TCP
See Transmission Control Protocol.

Glossary
283
TCP/IP
See Transmission Control Protocol/Internet
Protocol.
terminate and stay resident program (TSR
program)
A program that installs part of itself as an
extension of DOS when it is executed.
topology
The physical or logical mapping of the
location of networking components or
nodes within a network. Common
network topologies include bus, ring, star,
and tree. The three Fibre Channel
topologies are fabric, arbitrated loop, and
point-to-point. The default topology for
the disk array is arbitrated loop.
TL_port
See translated loop port.
transceiver
In communications, the device that
connects the transceiver cable to the
Ethernet coaxial cable. The transceiver is
used to transmit and receive data.
Transceiver is an abbreviation of
transmitter-receiver.
translated loop port (TL_port)
A port that connects to a private loop and
allows connectivity between the private
loop devices and off loop devices (devices
not connected to that particular TL_port).
Transmission Control Protocol (TCP)
A communication protocol used in the
Internet and in any network that follows
the Internet Engineering Task Force (IETF)
standards for internetwork protocol. TCP
provides a reliable host-to-host protocol in
packet-switched communication networks
and in interconnected systems of such
networks.
Transmission Control Protocol/Internet Protocol
(TCP/IP)
A set of communication protocols that
provide peer-to-peer connectivity
functions for both local and wide-area
networks.
trap
284

Protocol (SNMP), a message sent by a
managed node (agent function) to a
management station to report an
exception condition.
trap recipient
Receiver of a forwarded Simple Network
Management Protocol (SNMP) trap.
Specifically, a trap receiver is defined by
an Internet Protocol (IP) address and port
to which traps are sent. Presumably, the
actual recipient is a software application
running at the IP address and listening to
the port.
TSR program
See terminate and stay resident program.
uninterruptible power supply
A source of power from a battery
installed between the commercial power
and the system that keeps the system
running, if a commercial power failure
occurs, until it can complete an orderly
end to system processing.
user action events
Actions that the user takes, such as
changes in the storage area network
(SAN), changed settings, and so on.
worldwide port name (WWPN)
A unique 64-bit identifier associated with
a switch. The WWPN is assigned in an
implementation-independent and
protocol-independent manner.
worldwide name (WWN)
A 64-bit, unsigned, unique name identifier
that is assigned to each Fibre Channel
port.
WORM
See write-once read-many.
Write Once Read Many (WORM)
Any type of storage medium to which
data can be written only a single time, but
can be read from any number of times.
After the data is recorded, it cannot be
altered.
WWN See worldwide name.
zoning
In Fibre Channel environments, the
grouping of multiple ports to form a
virtual, private, storage network. Ports
that are members of a zone can
communicate with each other, but are
isolated from ports in other zones.
A function that allows segmentation of
nodes by address, name, or physical port
and is provided by fabric switches or
hubs.
Index
A
access volumes 5, 263

accessibility
document 267
Storage Manager features 267
adapter
See HBAs
ADT 129, 130
AIX 97
cluster services 251
error log 227
FCP disk array errors 227
HBA hot swap, completing the 138
HBA hot swap, preparing for 131
hot-swap HBA, replacing 133
logical drives, redistributing 129
mapping new WWPNs to storage
subsystems 138
Object Data Manager (ODM)
attributes
dac devices 261
dar devices 261
definitions 261
hdisk devices 261
lsattr command 265
viewing and setting 261
AIX host
support xiv
AIX multipath drivers 97
alert notifications, setting 33
arrays 64
creating 63
definition 63
attributes
dac 265
dar 265
hdisk 124, 265
LUN 124, 265
automatic ESM firmware synchronization
defined 43
Event Monitor requirement 43
automatic host discovery 31
automatic storage subsystem
discovery 31
autorecovery
verifying disabled state before HBA
hot swap on AIX 131
cache hit
optimizing 83
percentage 83
cache mirroring 229, 253
cache mirroring, disabling 126
cache read-ahead, choosing a
multiplier 83
CHAP 35, 36
cluster services
AIX requirements 253
HACMP ES and ESCRM 251
cluster services, high-availability
AIX 251
AIX requirements 252
HP-UX requirements 259
MC/Service Guard 259
PSSP with GPFS 253
Solaris 260
Solaris requirements 260
system dependencies 251
clustering
VMware ESX Server
configuration 246
command-line interface (CLI) 84
comments, Script Editor 85
components, Storage Manager
software 2, 29
concurrent firmware download 38, 43
configuration 4, 5, 161, 170
device driver, Linux DM-Multipath
driver 97
devices 123
direct-attached 2, 5
DS TKLM Proxy Code server, starting,
stopping, and restarting 161
DS TKLM Proxy Code, for external
security key management 160
FDE drives 166
GPFS, PSSP, and HACMP
clusters 253
HBAs 231
hosts 89
hot-spare drives 67
IBM i 72
iSCSI host ports 36
iSCSI settings 34
MTU 38
network 2, 3
network example 3
network settings for iSCSI host
attachment 37
recovery 63
SAN-attached 2, 5
storage subsystem passwords 32
storage subsystems 5
types 2
configuration types
Storage Manager installation 2
controller cache memory 76
B
background media scan
BIOS
settings 231
BOOTP server
sample network 3
BOOTP servers
sample network 6
77
controller firmware
downloading 38, 40
firmware
downloading 40
Controller Firmware Upgrade Tool
device health, checking 42
firmware, downloading 42
log file, viewing 43
opening 42
overview 41
storage subsystems, adding 42
using 42
controllers
addresses 6
dar 121
disk array 121
IP addresses 6
transfer rate, optimizing 82
copy services 45
cross connections
VMware ESX Server 248
D
dac
and RDAC 121
attributes 265
dar
and RDAC 121
attributes 265
data
collecting before HBA hot swap on
AIX 131
files, defragmenting 84
optimal segment size, choosing 84
redundancy 64
securing with FDE 144
DCE 126
DDC
See Diagnostic Data Capture
default host types, defining and
verifying 68
device drivers
description 91
DMP, installing 118
downloading latest versions xi, xiii
failover 91
HBAs 96
Linux DM-Multipath driver 97
multipath 91
installing 95
RDAC 91, 110
RDAC failover driver on Solaris 116
SCSIport Miniport 96
Storport Miniport 96
Veritas DMP DSM 97
with HACMP cluster 253
Device Specific Module
See DSM
devices
adding 32
285
devices (continued)
configuring 123
identification 122
identifying 120
setting alert notifications 33
Devices tab
See Enterprise Management window
DHCP server
sample network 3
DHCP servers
sample network 6
DHCP, using 36
Diagnostic Data Capture
MEL events 227
Recovery Guru 225, 227
recovery steps 226
Script Editor 225
direct-attached configuration
setting IP addresses 6
direct-attached configurations
setting up 5
discovery, automatic storage
subsystem 31
disk access, minimizing 84
disk array controller
See dac
disk array router
See dar
disk drives
FDE 144
FDE hot-spare 190
FDE, configuring 166
FDE, erasing 187
FDE, installing 166
FDE, migrating 183
FDE, secure erase 156
FDE, unlocking (external) 156
FDE, unlocking (local and
external) 181
FDE, unlocking (local) 155
hot spares, assigning 67
hot spares, configuring 67
hot spares, restoring data from 67
DMP 110
planning for installation 118
preparing for installation 118
DMP drivers 106
DMP DSM driver 97
documentation
about xi
accessibility 267
documents xiii
FDE best practices 194
notices xvi
related documentation resources xii
statements xvi
Storage Manager xii
Sun Solaris 110
Sun StorEdge 116
Symantec 97, 118
using xv
Veritas 97, 118
VMware 248
websites xii, xiii
drive firmware
downloading 43
levels, determining 39, 40
286
drivers xiii
See also device drivers
rpaphp 134
drives
See disk drives
DS TKLM Proxy Code server,
restarting 161
DS TKLM Proxy Code server, supported
operating systems 160
DS TKLM Proxy Code, configuring for
external security key management 170
DS TKLM Proxy Code, for external
DSM 96
DVE 126
Dynamic Capacity Expansion
See DCE
Dynamic Logical Drive Expansion
See DVE
Dynamic Multipathing (DMP)
See also DMP
description 110
E
Enterprise Management window
alert notifications 33
Devices tab 12
elements 11
online help xii
Setup tab 14
table view description 12
tree view description 12
Enterprise Management Window
adding devices 32
errors
FCP disk array 227
errors, media scan 78
ESM firmware
automatic ESM firmware
download 43
automatic ESM firmware
synchronization 43
downloading 38, 43
Ethernet
Solaris requirements, cluster
services 260
Ethernet MAC addresses
See MAC addresses
events
DDC MEL 227
events, critical
descriptions of 205
numbers 205
required actions 205
solving problems 205
external security key management 145,
149, 156, 160, 161, 165, 170
configuring 170
DS TKLM Proxy Code server 165
F
fabric switch environments
94
failover driver
description 91
MPxIO 111
failure support
DMP driver 110
MPxIO 110
RDAC driver 110
redistributing logical drives 129, 130
Fast!UTIL 231
FC/SATA Intermix premium feature 45
FCP disk array errors 227
FDE 75, 143
arrays, securing 191
backup and recovery 194
best practices 194
boot support 194
disk drives 144
disk drives, configuring 166
disk drives, erasing 187
disk drives, installing 166
disk drives, migrating 183
disk drives, unlocking (local and
external) 181
enabling 166
external security key
management 145, 193
frequently asked questions 191
hot-spare disk drives 190
hot-spare drives 193
key management method, choosing
a 145
local security key management 145,
192
log files 191
RAID arrays, securing 175
secure drives, unlocking
(external) 156
secure drives, unlocking (local) 155
secure erase 192
secure erase, using 156
securing data against a breach 144
security authorizations 157
security key identifier 149
security key management, FDE 145
security keys
creating 146
obtaining 145, 146
using 146
security keys, changing
(external) 149
security keys, changing (local) 148
security keys, creating 146
security keys, obtaining 145
states, locked and unlocked 194
terminology 159
understanding 144
using with other premium
features 193
feature enable identifier 46
feature key file 46
features
Fast!UTIL 231
features, premium
See premium features
Fibre Channel
HBAs in a switch environment 94
Fibre Channel I/O

cache-hit percentage 83
load balancing 82
Fibre Channel switch zoning 94
files, defragmenting 84
firmware
controller xiii
downloading 38, 43
downloading with I/O 43
obtaining xiii
supported by Storage Manager 2
versions 2
FlashCopy 74
disk array error messages (AIX) 229
Frequently asked questions, other 194
full disk encryption
See FDE
G
General Parallel File System (GPFS)
glossary 273
GPFS 253
253
H
HACMP 251
using 252
hardware
Ethernet address 4, 5
service and support xv
VMware ESX Server
requirements 246
hardware initiators, iSCSI 37
HBAs
advanced settings 232
connecting an a Fibre Channel switch
environment 94
default settings 232
device drivers 96
Fibre Channel switch
environment 94
hot swap, completing 138
hot-swap on Linux, preparing
for 134
hot-swap, replacing 130
hot-swap, replacing for AIX and
Linux 133
hot-swap, replacing on AIX 131
in a direct-attached configuration 5
in a SAN-attached configuration 5
JNI settings 239
JNI settings on Solaris 239
on Linux, replacing 134
overview 93
PCI hotplug, replacing 137
QLogic settings 233, 243
settings 231
using 93
hdisk
attributes 124, 265
queue depth, setting 124
hdisks
verification 122
head-swap, FDE storage subsystems 183
help
obtaining xiv, xv
websites xiii
help, online xii
heterogeneous environment 70
High Availability Cluster
Multi-Processing
See HACMP
host bus adapters
See HBAs
HBAs
setting host ports 49
Solaris
QLogic settings 243
host computers
See hosts
host groups
defining 49, 70
host ports
defining 71
definition 71
host ports, iSCSI 36
host types
defining default 68
verifying 68
host-agent software
stopping and restarting 124
host-agent-managed configuration 5
host-agent-managed, setting up 5
host-agent-management method
UTM device 121
hosts xi
AIX, devices on 121
automatic discovery 31
configuring 89
defining 71
heterogeneous 70
IBM i 72, 73
iSCSI 37
manual discovery 32
pre-installation tasks 4, 5
hot_add utility 123
hot-spare
FDE disk drives 190
hot-spare drives 67
hot-swap HBAs
See HBAs, hot-swap
HP-UX
cluster services, high-availability
requirements 259
multipath I/O with PV-links 106, 107
native multipathing 110
PV-links 106, 107
I
I/O
access pattern 83
request rate optimizing 83
size 83
write-caching 83
I/O access pattern and I/O size
I/O activity, monitoring 91
I/O data field 81, 82
83
I/O request rate

optimizing 83
I/O transfer rate, optimizing 82
IBM i
configuring 72
defining as the host type 73
port identifier 72
IBM Power systems 72
IBM Support Line xv
IBM System Storage Controller Firmware
Upgrade Tool
See Controller Firmware Upgrade Tool
IBM System Storage Productivity
Center xiii
IBM Tivoli Key Lifecycle Manager 145,
170
DS TKLM Proxy Code server
configuration file, modifying 161
DS TKLM Proxy Code,
configuring 170
DS TKLM Proxy Code, installing 165
for external security key management,
configuring 160
icons, Support Monitor 198
important notices 271
in-band configuration
See host-agent-managed configuration
installation 165
completion procedures 31
configuration types 2
DS TKLM Proxy Code on Windows,
for external security key
management 165
FDE drives 166
multipath drivers 95
network configuration 3
preparing for 1
proxy on AIX or Linux, for external
sequence of 29
Storage Manager 23
Storage Manager, automatic 25
Storage Manager, manual 28, 29
Support Monitor 23
Support Monitor, automatic 25
Support Monitor, console window 27
VMware ESX Server
configuration 245
Intel and AMD-based host
support xiv
interface, Support Monitor 198
introduction
Storage Manager 1
IP address
IPv6 37
IP addresses 6
IPv6 37
iSCSI
host ports 34
host ports, configuring 36
iSNS server, using 36
mutual authentication permissions,
entering 36
network settings 37
session, viewing or ending 36
settings, managing 34
Index
287
iSCSI (continued)
software initiator considerations,
Microsoft 38
statistics, viewing 36
supported hardware initiators,
using 37
target authentication, changing 35
target discovery, changing 36
target identification, changing 36
iSNS server, using 36
J
JNI
HBA settings 239
HBA settings on Solaris
239
K
keys, security (FDE)
See FDE
L
least path weight policy 81
least queue depth policy 81
Linux
DCE 126
DVE 126
HBA hot swap, completing the 138
HBAs, preparing for hot swap 134
hot-swap HBA, replacing 133
mapping new WWPNs to storage
subsystems 138
replacing HBAs 134
RHEL 5.3, with Veritas Storage
Foundation 5.0 127
SUSE, with Veritas Storage
Foundation 127
Linux DM-Multipath driver 97
Linux host
support xiv
Linux MPP drivers 104
load balancing 261
load_balancing attribute 261, 262
local security key management 146, 148,
155
LockKeyID, FDE 149
log files 202, 205
major events log 191
security changes 191
logical drives 5, 263
configuration 67
creating 63, 66
creating from free or unconfigured
capacity 63
definition 63
expected usage 67
identifying 120
modification priority setting 84
redistributing 129, 130
Logical tab
See Subsystem Management window
lsslot tool 135
LUNs
adding to an existing partition 71, 72
288
LUNs (continued)
attributes 124, 265
checking size 128
mapping to a new partition 71
mapping to a partition on VMware
ESX Server 249
M
MAC addresses
identifying 7
MAC OS 105
management stations xi
compatible configuration types 2
description 1, 4
manual discovery 32
Mappings tab
Maximum Transmission Unit
See MTU
MC/Service Guard 259
Media Scan 77
changing settings 77
duration 80
errors reported 78
overview 77
performance impact 78
settings 79
medical imaging applications 65
Medium Access Control (MAC) address
See MAC addresses
MEL
security changes 191
messages
Support Monitor 202
Microsoft iSCSI Software Initiator 38
Microsoft Windows MPIO 96
Microsoft Windows MPIO/DSM 96
Minihubs 5
modifying the proxy configuration file for
external security key management 161
MPIO 122
MPP drivers 104
MPxIO 110
device names, changing 111
devices, verifying 111
driver, disabling 116
failover driver, enabling 111
failover path, configuring 111
failover path, unconfiguring 111
latest driver version, acquiring 111
MTU
settings 38
multi-user environments 65
multimedia applications 65
multipath driver 105
description 91
multipath drivers 97, 104, 120
installing 95
multipathing 38, 95, 110
DMP, installing on Solaris 118
MPxIO, using with Solaris 110
native, on HP-UX 110
PV-links, using on HP-UX 106, 107
RDAC failover driver on Solaris 116
multipathing (continued)
redistributing logical drives on
AIX 129
HP-UX 129
Solaris 130
Multiplexed I/O (MPxIO)
See MPxIO
mutual authentication permissions,
entering for iSCSI 36
My Support xvi
N
names, storage subsystem 33
network installation, preparing 3
network-managed configuration 4
network-managed, setting up 4
networks
configuration example 3
general configuration 3
iSCSI settings 37
notes, important 271
notices xvi
general 269
notifications
to alphanumeric pagers 33
to email 33
using SNMP traps 33
NVSRAM firmware
downloading 38, 40
O
Object Data Manager (ODM) attributes
definitions 261
initial device identification 122
operating system
requirements 23
operating systems
booting with SAN boot 89
DS TKLM Proxy Code 160
Solaris 111
supported for Storage Manager 1
Other frequently asked questions 194
out-of-band configuration
See network-managed configuration
P
packages, Storage Manager software
29
Parallel System Support Programs
(PSSP) 253
parity 64
partitioning 49
passwords, setting 32
PCI core 134
PCI Hotplug 135
PCI hotplug HBAs 137
PCI Hotplug tools 134
PCI slot information 135
performance
ODM attribute settings and 124
Performance Monitor 80
2,
Persistent Reservations 77
Physical tab
policies, load-balancing
least path weight policy 81
least queue depth policy 81
round robin policy 81
premium features 45
configuring 74
descriptions of 45
disabling 47
enabling 46, 47
FDE 143
FDE and FlashCopy 193
FDE and VolumeCopy 193
FDE, enabling 166
feature enable identifier 46
feature key file 46
FlashCopy 74
Full Disk Encryption
See FDE
key 75
Remote Mirror Option 75
storage partitioning 49, 70
using 74
VolumeCopy 75
prerequisites
HP-UX
cluster services,
high-availability 259
prerequisites, Storage Manager client
software 29
problem solving, critical events 205
problems, solving 205
products, developed 269
profile, storage subsystem 48
proxy, installing on AIX or Linux 165
proxy, installing on Windows 165
proxy, uninstalling on Windows 165
PSSP 253
PV-links
See HP-UX
Q
QLogic
HBA settings 231, 233, 239, 243
settings 243
QLogic SANsurfer xii
queue depth
changing for AIX 125
changing for Windows 125
maximum, calculating 125
queue depth, setting 124
R
RAID
application behavior, by level 83
choosing levels 83
data redundancy 64
levels 64
securing arrays with FDE 175
RAID level
application behavior 66
choosing 66
RAID level (continued)

configurations 64
RAID-0
described 64
drive failure consequences 64
RAID-1
described 65
RAID-3
described 65
RAID-5
described 65
RAID-6
dual distributed parity 65
RDAC
IDs, adding 260
IDs, cluster services 260
RDAC driver
description 91
RDAC drivers
configuration files, modifying 116
description 110
Solaris, installing on 116
readme
obtaining files xiii
Recovery Guru
Diagnostic Data Capture 225
remote boot
See SAN boot
Remote Mirror Option 75
requirements
HP-UX
cluster services,
high-availability 259
operating system 23
Storage Manager client software 29
resources
documents xiii
round robin policy 81
S
SAN boot
configuring hosts 89
requirements 89
SAN-attached configuration
setting up 5
schedule support bundle collection 199
Script Editor
using 85
window 85
SCSIport Miniport 96, 97
secure erase, FDE 156
security authorizations, FDE 157
security keys
changing (external) 149
changing (local) 148
creating 146
identifier 149
using to unlock FDE drives 181
security keys, FDE
See FDE
service
requesting xiv
services offered in the U.S.A. 269

session, iSCSI 36
settings
advanced HBA 232
HBA 231
HBA default 232
media scan 79
modification priority 84
MTU 38
Setup tab
Enterprise Management window 14
Subsystem Management window 20
Simple Network Management Protocol
(SNMP) traps
See also SNMP traps
SNMP traps 3
SMagent
software installation sequence 29
SMclient
SMdevices utility
on Unix-type operating systems 121
on Windows 120
using 120
SMrepassist utility 123
SMruntime
SMutil
SNMP traps 3, 6, 33
software
key license management 145
multipath drivers 91
RDAC package 110
service and support xv
setting up controller addresses 6
Storage Manager components 2, 29
VMware ESX Server
requirements 245
software versions, multiple
Solaris
cluster services requirements 260
cluster services, high-availability 260
Veritas 118
SSPC xiv
SSPC (System Storage Productivity
Center) xiii
statements xvi
statistics, iSCSI 36
storage area network (SAN)
configuration 5
technical support web site xiv
Storage Manager 76, 77
accessibility 267
command-line interface 84
Controller Firmware Upgrade Tool
using the tool 41
description 1
Enterprise Management window 11
event log 205
installation 31
installation sequence 29
installation wizard 25
installing for use with IBM System
Storage Productivity Center xiii
Index
289
Storage Manager (continued)

interface elements 11
interface elements, Storage
Manager 11
manual installation 28, 29
obtaining software xiii
other features 76
premium features 45, 74
problems, solving 205
Script Editor 84
setting up controller addresses 6
software components 2, 29
Subsystem Management window 14
Support Monitor 197
supported operating systems 1
Task Assistant 50
troubleshooting 205
uninstalling 30
uninstalling on Linux, AIX, or
Solaris 30
uninstalling on Windows 30
version 10.5x drive firmware
download 43
versions 2
Storage Manager software
new terminology xi
storage partitioning 45, 70
and host groups 49
storage subsystem
adding 124
firmware levels, determining 39, 40
profile, saving 48
VMware ESX Server
configuration 245
storage subsystem, for external security
key management 170
storage subsystems
configuring for external key
management 170
for external security key management,
configuring 160
initial automatic discovery 31
introduction 1
IP addresses 6
manual discovery 32
mapping new WWPNs for AIX and
Linux 138
naming 33
setting passwords 32
static TCP/IP addresses 8
tuning 80, 81, 82, 83, 84
tuning options available 80
Storport Miniport 96
Subsystem Management window
elements 14, 15
event log 205
Logical tab 17
Mappings tab 19
multiple software versions 21
online help xii
opening 15
Physical tab 18
Setup tab 20
Summary tab 16
Support tab 21
290
Summary tab
support
multipath driver 91
notifications xvi
obtaining xiv, xv
using Storage Manager to send
support bundles 200
websites xiii, xvi
support bundles
collecting manually 201
scheduling collection 199
sending to IBM Support 200
Support Monitor
configuring 197
console area 198
enterprise status 198
icons 198
installation with a console
window 27
installation wizard 25
interface 198
log window 202
messages 202
sending support bundles 200
solving problems 223
support bundle collection
schedule 199
support bundles 201
troubleshooting 223
uninstalling 30
uninstalling on Linux, AIX, or
Solaris 30
uninstalling on Windows 30
using 197
Support Monitor log window, using 202
support notifications xvi
receiving xvi
Support tab
switch
technical support website xiv
switch environment 94
switches
in a SAN-attached configuration 5
zoning 5
System p host
support xiv
System Storage Interoperation Center
(SSIC) xiv
System Storage Productivity Center xiii
System Storage Productivity Center
(SSPC) xiv
System x host
support xiv
T
target authentication, changing for
iSCSI 35
target discovery, changing for iSCSI
target identification, changing for
iSCSI 36
Task Assistant
description 50
shortcuts 50
36
TCP/IP
IPv6 37
TCP/IP addresses, static
assigning to storage subsystems 8
terminology xi
terminology, FDE 159
Tivoli Key Lifecycle Manager
See IBM Tivoli Key Lifecycle Manager
TKLM
See IBM Tivoli Key Lifecycle Manager
tools
lsslot 135
PCI Hotplug 134
Support Monitor 197
trademarks 271
transfer rate 80
troubleshooting 205
critical events 205
Support Monitor 223
U
uninstallation
DS TKLM Proxy Code on Windows,
for external security key
management 165
Storage Manager 30
Support Monitor 30
universal transport mechanism
See UTM device
updates
receiving xvi
updates (product updates) xvi
utilities
hot_add 123
SMdevices 120
SMrepassist 123
UTM device 121
V
Veritas 97
DMP 118
Dynamic Multipathing (DMP) 110
File System 118
Storage Foundation 127
Storage Foundation 5.0 127
VolumeManager 110, 118
Veritas DMP drivers 106
Veritas DMP DSM 97
Veritas Storage Foundation
LVM scan, disabling for SUSE Linux
Enterprise Server 127
RDAC module, enabling on RHEL for
Storage Foundation 5.0 127
Veritas Storage Foundation 5.0
RDAC module, enabling 127
RDAC module, unloading 127
cross connections 248
mapping LUNs to a partition 249
VolumeCopy 75
W
Web sites
AIX xiv
SAN support xiv
websites
documentation xii
FDE best practices 194
IBM publications center xiv
IBM System Storage product
information xiv
list xiii
notification xvi
premium feature activation xiv
services xv
Solaris failover driver 118
SSIC xiv
support xv, xvi
switch support xiv
System p xiv
System Storage Productivity Center
(SSPC) xiv
System x xiv
VMware 248
window
Script Editor 85
worldwide port name
See WWPN
write-caching
enabling 83
WWPN
mapping to storage subsystem on AIX
and Linux 138
Z
zoning 94
zoning switches
Index
291
292

Part Number: 00W0188
GA32-0963-03
(1P) P/N: 00W0188
Printed in USA

00 W 0188

Uploaded by

Copyright:

Available Formats

00 W 0188

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

00 W 0188

Uploaded by

Copyright:

Available Formats

IBM System Storage DS Storage Manager Version 10

Installation and Host Support Guide

Twelfth Edition, June 2012

Chapter 2. The Storage Manager

Enterprise Management window . . . . . .

About this document . . . . . . . . . xi

Chapter 1. Preparing for installation

Copyright IBM Corp. 2012

Chapter 3. Installing Storage Manager

Configuring Maximum Transmission Unit

Chapter 4. Configuring storage . . . . 49

Maximizing throughput with load balancing .

Chapter 5. Configuring hosts . . . . . 89

Changing the queue depth for Windows . .

Securing a RAID array . . . . . . . . .

Chapter 7. Configuring and using the

Chapter 6. Working with full disk

The Support Monitor interface. . . . .

Chapter 8. Troubleshooting . . . . . 205

Appendix A. Host bus adapter

Appendix B. Using a storage

Appendix C. Using the Storage

Appendix D. Viewing and setting AIX

Appendix E. Accessibility . . . . . . 267

Sample network using network-managed and

Copyright IBM Corp. 2012

A security-enabled FDE drive is removed

Data shown in the table view . . . . . . 13

Copyright IBM Corp. 2012

About this document

Storage Manager documentation on the IBM website

documentation is available for download (PDF) on the IBM website:

Storage Manager online help and diagnostics

Finding Storage Manager software, controller firmware, and readme

IBM System Storage Productivity Center

Essential websites for support information

About this document

IBM System Storage Interoperation Center (SSIC)

Getting information, help, and service

Before you call

Using the documentation

Software service and support

Hardware service and support

About this document

Notices and statements in this document

Receiving product updates and support notifications

Chapter 1. Preparing for installation

Storage Manager software

Copyright IBM Corp. 2012

Storage Manager software components

Supported controller firmware

Types of installation configurations

Figure 1. Sample network using network-managed and host-agent-managed storage subsystems

Reviewing a sample network configuration

Chapter 1. Preparing for installation

Host-agent-managed storage subsystem: Network B is a host-agent-managed storage subsystem. You can

Setting up a management station

Setting up a network-managed (out-of-band) configuration

Setting up a host-agent-managed (in-band) configuration