Request for Price Quotations (RPQ)
If a desired configuration is not represented in this document, a RPQ should be submitted to IBM to request approval. To submit a RPQ, contact your local IBM Storage Specialist or Business Partner.

Whats New

This version is dated February 27, 2008 and has been updated as noted below. It replaces the version dated February 6, 2007. Unless stated otherwise, these items are recommended with DS8000 LMC level 5.3.0xx.xx, bundle version 63.0.xx.xx, or later.
Operating Systems, Path Management, and Clustering Microsoft Windows 2008 Standard, Enterprise and Datacenter (without Hyper V) SDD DSM available for Microsoft Windows 2008 Standard, Enterprise and Datacenter (without Hyper V)

Page 2

DS8000 SERIES INTEROPERABILITY SUMMARY
For convenience, the following tables summarize the interoperable environments and configurations for the DS8000 series. Refer to the individual server pages for additional information, including prerequisites and limitations. Table 1: Open Systems
DS Command Line Interface (DS CLI) DS8300 Model 9A2 & Turbo Model 9B2 DS8100 Model 921 & Turbo Model 931 DS8300 Model 922 & Turbo Model 932 Subsystem Device Driver (SDD)
Fujitsu Primepower Hewlett-Packard (HPUX) Hewlett-Packard AlphaServer (OpenVMS) Hewlett-Packard AlphaServer (Tru64 UNIX) IBM System i (AIX) IBM System i (OS/400, i5/OS) IBM System i (Linux) IBM System p (i5/OS) IBM System p (Linux) IBM System p, RS/6000, and Cluster 1600 (AIX) Linux (x86, x64, EM64, AMD64, iA64) Intel Servers (NetWare) AMD & Intel Servers (VMware) Windows (x86, x64, EM64, AMD64, iA64) Apple Macintosh (OSX) SGI Origin Servers (IRIX) Sun (Solaris)
DS Application Program Interface (API)

SAN Boot Support

Fibre Channel

Clustering

Page 3

Table 2: IBM System z

Fibre Channel Protocol (FCP)
DS8300 Model 9A2 & Turbo Model 9B2
DS8100 Model 921 & Turbo Model 931

Remote Mirror and Copy Solutions
The DS8000 series supports several hardware-based remote mirror and copy solutions. They are optional capabilities of the DS8000 series and are available with the remote mirror and copy features on the DS8000 series. IBM supports the following remote mirror and copy solutions. Refer to Table 3 for DS8000 series model support and prerequisites. IBM System Storage Metro Mirror Metro Mirror is designed to provide real time mirroring between two systems that can be located up to 300 km from each other. It is a synchronous copy solution where write operations are completed on both copies (local and remote site) before they are considered to be done. Extending distances beyond 300 km is also possible. However, due to network configuration variability, the customer must work with the channel extender vendor to determine the appropriate configuration to meet their performance requirements. IBM support approval for these longer distances can be requested by submitting a Request for Price Quotation (RPQ). The RPQ should include information on distance between sites, the channel extension technology, the type of telecom line, the amount of network bandwidth, the DS8100 or DS8300 system capacity, and a general description of the workload. IBM System Storage Global Copy Global Copy is a non-synchronous long-distance copy option for data migration and backup. With a non-synchronous operation, the distance between the primary and secondary DS8000 series system will have only a minimal effect on the application response time. Therefore, Global Copy can operate at very long distances. IBM System Storage Global Mirror Global Mirror is a high performance, asynchronous remote-mirroring copy solution. It is designed to provide a two-site disaster recovery and backup solution at virtually unlimited distances. Since the distance between the primary and secondary DS8000 series system has little impact to host applications at the primary site, the remote site can be located at distances from the local site well beyond those supported with Metro Mirror. The distances are typically limited only by the capabilities of the network and channel extension technologies.
IBM System Storage Metro/Global Mirror (MGM)
The Metro and Global Mirror function utilizes synchronous mirroring (Metro Mirror), from a local A- site to a metro distance B-site and asynchronous mirroring (Global Mirror) from an intermediate B-site to a remote C-site. This function, referred to as Metro/Global Mirror, is designed to provide planned and unplanned outage three-site enterprise disk data replication - which can help meet rigorous three-site business resiliency needs of the enterprise data center. Metro/Global Mirror can support synchronous replication at distances up to 303 KM using IBM System Storage Metro Mirror, and can maintain the asynchronous third site for out of region recovery, at a data currency that can be within 3-5 seconds (bandwidth permitting), using IBM System Storage Global Mirror.

Nortel OM3500

Requires firmware level 3.2.1 Maximum distance is 300 km February 27, 2008 DS8000 series Interoperability Matrix Page 10
HEWLETT-PACKARD SERVERS HP-UX
Servers HP Server rp2400 series rp3400 series rp4400 series rp5400 series rp7400 series rp8400 series Superdome HP 9000 Enterprise Servers K-Class L-Class N-Class V-Class Operating Systems HP-UX 11i @ PVLINKS MC/Serviceguard 11.12, 11.13, and 11.14 11iv2 (11.23) PVLINKS MC/Serviceguard 11.16 11iv3 (11.31) MC/Serviceguard 11.17
Host Adapters Hewlett-Packard A5158A A6685A A6795A A6826A A9782A A9784A AB378A AB379A
Fabric Support Cisco MDS 9020, 9120, 9124, 9140 MDS 9216, 9216A, 9216I MDS 9506, 9509, 9513 MDS 9134, 9222i CNT (Inrange) FC/9000-64, -128, - 256 2042-N16 IBM 2005 Model B16, B32, B64, B5K 2005 Models H08, H16, RModel E12, Models 12E, 16E, Models 32E, 432
Itanium II Servers rx1600 series rx2600 series rx4600 series rx5600 series rx7600 series rx8600 series Superdome
2027 Models 140, Models R04, R16, Model NModel AModels F16, FModel MModel MModel MModels S08, SModel F08

McDATA

ED-5000 ES-3016, ES-3032 Intrepid 6064, 6140 Sphereon 3216, 3232 4300, 4500
Supported with K-Class servers only. RPQ required for HPUX 11iv3 support. February 27, 2008 DS8000 series Interoperability Matrix Page 11

General notes:

This Interoperability file will be sunsetting, please begin to use and familiarize yourself with the System Storage Interoperation Center (SSIC): http://www.ibm.com/servers/storage/support/config/ess/index.jsp
DS Open API (CIM Agent): Not available for HP-UX. DS CLI: Available for HP-UX 11i, 11iV2 and 11iV3. SDD: Available for HP-UX 11i and 11iV2. Available for MC/Serviceguard. Multi-path support is natively available in HP-UX (PVLINKS) for HP-UX 11i and 11iv2. Multi-Path for HP-UX 11iv3 is natively supported with the Operating System. SAN Boot not supported HPUX 11iV3 is not supported with SDD.

Page 12

HEWLETT-PACKARD SERVERS OPENVMS
Servers AlphaServer 4000, 4000A 4100 8200, 8400 DS10, DS20, DS20E ES40, ES45, ES47, ES80 GS60, GS60E, GS140 GS80, GS160, GS320 GS1280 Itanium Server RX2600 RX7620
Operating Systems OpenVMS 7.3 7.3-1 7.3-2 8.2 OpenVMS itanium 8.2, 8.2.1
Host Adapters StorageWorks KGPSA-CA (FCA2354) KGPSA-DA (FCA2384) KGPSA-EA FCA 2684
Fabric Support IBM 2109 Model FModel FModels S08 and SModel F08
Itanium servers require 8.2 Operating System and above. February 27, 2008 DS8000 series Interoperability Matrix Page 13
HEWLETT-PACKARD SERVERS - OPENVMS
DS Open API (CIM Agent): Not available for HP OpenVMS. DS CLI: Available for HP OpenVMS. SDD: Not available for HP OpenVMS.

Page 14

HEWLETT-PACKARD SERVERS TRU64 UNIX
Servers AlphaServer 2100 4000, 4000A 4100 8200, 8400 DS10, DS20, DS20E ES40, ES45, ES47, ES80 GS60, GS60E, GS140 GS80, GS160, GS320 GS1280 Operating Systems Tru64 UNIX 5.0A TruCluster 5.0A 5.1 TruCluster 5.1 5.1A TruCluster 5.1A 5.1B TruCluster 5.1B 5.1B3 TruCluster 5.1B3 5.1B4 TruCluster 5.1B4 Host Adapters StorageWorks KGPSA-CA (FCA2354) KGPSA-DA (FCA2384) KGPSA-EA Fabric Support IBM 2109 Model FModel FModels S08, SModel F08

Page 15

This Interoperability file will be sunsetting, please begin to use and familiarize yourself with the System Storage Interoperation Center (SSIC): http://www.ibm.com/servers/storage/support/config/ess/index.jsp DS Open API (CIM Agent): Not available for HP Tru64 UNIX. DS CLI: Available for HP Tru64 UNIX. SDD: Not available for HP Tru64 UNIX. Multi-path support is natively available in Tru64 UNIX.
SAN Boot support: The DS8000 can be used as a boot device on servers running Tru64 UNIX 5.0A and 5.1. Refer to the IBM System Storage DS8000 Host Systems Attachment Guide for additional information.

Page 16

IBM SYSTEM I SERVERS
Servers System i 270 820, 830, 840 800, 810, 825, 870, 890 System i5 520, 550, 570, 595 System i (POWER6) 570 (9406-MMA)

Operating Systems AIX

Host Adapters System i FC 0611 FC 0612 FC 0625 FC 0626 FC 0629 FC 0646 FC 2766 FC 2787 FC 5759 FC 5760
Fabric Support Cisco MDS 9020, 9120, 9124, 9140 MDS 9216, 9216A, 9216I MDS 9506, 9509, 9513 MDS 9134, 9222i CNT (Inrange) FC/9000-64, -128,-256 2042-N16 IBM 2005 Model B16, B32, B64, B5K 2005 Models H08, H16, RModels E12, 224
Version 5 5.2 ML5 5.3 ML1 OS/400 Version 5 V5R2 i5/OS Version 5 V5R3 V5R4 V5R4 M5 Red Hat Enterprise Linux 3 U7, UU2, U3, 4.4, 4.5, 4.6 5, 5.1 SUSE

1, 2 1, 2

2026 Models 12E, 16E, Models 32E, Models 140, Models R04, R16, Model NModel AModel FModel FModel M12, M14, MModels S08, SModel F08 McDATA Intrepid 6064, 6140 Sphereon 3216, 3232 4300, 4500
SLES 9 SP2, SP3 Linux Enterprise 10, SP1
Linux is supported on the System i5 only. Refer to the following link for details on Linux kernel levels: http://www.ibm.com/support/docview.wss?rs=540&context=ST52G7&dc=D430&uid=ssg1S4000107&loc=en_US&cs=utf-8&lang=en\
AIX 5.2 ML5 (or later), 5.3 ML1 (or later) and Linux supported with System i5. Host adapter 5760 requires i5/OS V5R3 or V5R4 and above and Host adapter 5759 requires Linux or AIX partitions only on Regatta and System i5 servers. 5 Requires Operating System i5/0S V5R4m5 February 27, 2008 DS8000 series Interoperability Matrix Page 17
DS Open API (CIM Agent): DS CLI: Available for System i AIX, OS/400 V5R2, i5/OS V5R3, and V5R4 platforms. Not available.
SAN Boot support: SDD: Not available. Multipath support is provided in i5/OS V5R3. Available when running the System i5 platforms with supported AIX, SUSE SLES 9, 10, Red Hat Enterprise Linux 3, 4 (32-bit, x64-bit) operating systems. Requires IOP 2847 and V5R3 M5 or later for i5servers. See the IBM System i Redbook for more information.

Device Mapper Multipath (DMM): Available for SUSE Linux Enterprise 10 and Red Hat RHEL 5. For more information, refer to: http://www.ibm.com/support/docview.wss?rs=540&context=ST52G7&dc=D430&uid=ssg1S4000107&loc=en_US&cs=utf8&lang=en#DM
SAN Boot Support: The DS8100 and DS8300 models are supported as a boot device on System i5 platforms that support Fibre Channel boot capability. SAN Boot Support is available for AIX and Linux operating systems with SDD. Refer to the IBM System Storage DS8000 Host Systems Attachment Guide for additional information.
Path Control Module (SDDPCM): Available for System i5 platforms running AIX 5.2 ML5 (or later) and AIX 5.3 ML1 (or later) with latest released maintenance levels. (Default PCM not supported).

Page 18

IBM SYSTEM P AND RS/6000 SERVERS
Servers System p 610 Models 6C1, 6EModels 6C3, 6EModels 6F0, 6FModels 6C4, 6EModel BModel 6MModel Models 6H0, 6H1, 6MModel Model SModel 681 System p5 A50, 510, 520, 550, 560, 570, 590, 595 710, 720 System p (POWER6)
Host Adapters System p and RS/6000 FC 1905 FC 1910 FC 1957 FC 1977 FC 5716 FC 5758 FC 5759 FC 5773 FC 5774 FC 6228 FC 6239

Fabric Support Cisco

5.1 ML7 VERITAS Volume Manager with DMP 4, VERITAS Cluster Server 4, 5.2 ML5 VERITAS Volume Manager with DMP 4, 5, VERITAS Cluster Server 4, 5, SFRAC 5.0 5.3 ML1 VERITAS Volume Manager with DMP 4, 5, VERITAS Cluster Server 4, 5, SFRAC 5.0 6.1 SP2
MDS 9020, 9120, 9124, 9140 MDS 9216, 9216A, 9216I MDS 9506, 9509, 9513 MDS 9134, 9222i CNT (Inrange) FC/9000-64, -128, -256 2042-N16 IBM 2005 Models B16, B32, B64, B5K 2005 Models H08, H16, RModels E12, 224

BladeCenter

2026 Models 12E, 16E, Models 32E, Models 140, Models R04, R16, Model NModel AModels F16, FModels M12, M14, MModels S08, SModel F08 IBM BladeCenter
System p570 (9117-MMA) IBM BladeCenter
HACMP 5.1.0, 5.2.0, 5.3.0, 5.4 i5/OS
IBM 13N2203 26R0884 39Y9186 48P7061
BladeCenter JS1 BladeCenter JS21 8844, BladeCenter JSRS/6000 7013: S70, S7A 7015: S70, S7A 7017: S70, S7A, S80 7025: F50, F80, H70 7026: H50, H70, H80, M80 7043: 270 7044: 170, 270

V5R3, V5R4 IBM Virtual I/O Server (VIOS) 1.1 Red Hat Enterprise Linux 3 U7, UVxVM/VCS 5.U2, U3, 4.4, 4.5, 4,6 5, 5.1 SUSE
P/N 02R9080 P/N 48P7062 McDATA ED-5000 ES-3016, ES-3032 Intrepid 6064, 6140 Sphereon 3216, 3232 4300, 4500
SLES 8 @ SLES 9 SP2, SPVxVM/VCS 5.0 Linux Enterprise 10, SP1
BladeCenter is supported with AIX 5.2 ML5 (or later), and Linux operating systems only. For more information on BladeCenter SAN support, refer to the following website: http://www.ibm.com/servers/eserver/serverproven/compat/us/ Supports the IP Storage Service Module for iSCSI on Cisco MDS fabric products. Refer to the following link for more details: ftp://service.boulder.ibm.com/storage/san/cisco/ipStorServMod.pdf The POWER6 IBM System p and JS22 are supported with the following: AIX 5.2 ML10, AIX 5.3 ML6, AIX 6.1 SP2, Linux SLES 10 sp1, Red Hat 4.5, 4.6 and 5.1. Refer to the following link for details on Linux kernel levels: http://www.ibm.com/support/docview.wss?rs=540&context=ST52G7&dc=D430&uid=ssg1S4000107&loc=en_US&cs=utf-8&lang=en\ Refer to the most current APARs for AIX 5.2 ML5 (or later) and AIX 5.3 ML1 (or later). Refer to the following link for details on IBM VIOS: http://www14.software.ibm.com/webapp/set2/sas/f/vios/home.html The i5/OS operating systems are only supported with System p5 servers, and System i host adapter FC2787. Fencing is currently not supported. February 27, 2008 DS8000 series Interoperability Matrix Page 19

General Notes:

DS Open API (CIM Agent): Available for AIX 5.1 ML7 (or later). DS CLI: Available for AIX 5.1 ML7 (or later), 5.2 ML5 (or later), 5.3 ML1 (or later), 6.2 sp2, HACMP 5.1.0, 5.2.0, 5.3.0, and 5.4.0, and i5/OS operating systems. DS Copy Services: HACMP running with Remote Mirror and Copy functions (including HACMP-XD) is supported. SDD: Available for AIX 5.1 ML7 (or later), 5.2 ML5 (or later), 5.3 ML1 (or later) and 6.2 sp2. Available for SUSE SLES 8, SLES 9, Red Hat RHEL 3, and 4 (32-bit and x64-bit). Available for HACMP-XD Not available with i5/OS operating systems. Available for coexistence with Veritas Volume Mgr 4.0 with AIX 5.2 and 5.3
Device Mapper Multipath (DMM): Available for SUSE Linux Enterprise 10 and Red Hat RHEL 5 and above. For more information, refer to: http://www.ibm.com/support/docview.wss?rs=540&context=ST52G7&dc=D430&uid=ssg1S4000107&loc=en_US&cs=utf8&lang=en#DM
SAN Boot support: The DS8100 and DS8300 models are supported as a boot device on System p, and RS/6000 servers that support Fibre Channel boot capability. Boot Support is available for AIX and Linux operating systems with SDD. Boot support is not available for SDD with BladeCenter JS20. Refer to the IBM System Storage DS8000 Host Systems Attachment Guide for additional information.

Path Control Module (SDDPCM): Available for AIX 5.2 ML5 (or later), AIX 5.3 ML1 (or later) and AIX 6 sp2 with latest released maintenance levels.

Page 20

Table 5: AIX and HACMP Support Matrix
DS8100 Model 921 & Turbo Model 931 AIX 5.1 ML7 with HACMP 5.1.0 DS8300 Model 922 & Turbo Model 932 DS8300 Model 9A2 & Turbo Model 9B2 SDD SDD PCM --
AIX 5.2 ML5 with HACMP 5.1.0
AIX 5.1 ML7 with HACMP 5.2.0
AIX 5.2 ML5 with HACMP 5.2.0
AIX 5.2 ML5 with HACMP 5.4
AIX 5.3 ML1 with HACMP 5.2.0
AIX 5.2 ML7 with HACMP 5.3.0
AIX 5.3 ML3 with HACMP 5.3.0
AIX 5.3 ML3 with HACMP 5.4.0
AIX 6.1 SP2 with HACMP 5.3.0
AIX 6.1 SP2 with HACMP 5.4.1
Table 6: AIX Clustering for System p servers
DS8100 Model 921 & Turbo Model 931 AIX 5.1 ML7 with: PSSP 3.4, 3.5 GPFS 2.2 AIX 5.2 ML5 with: GPFS 2.2, 2.3 or 3.1 RVSD 3.5 or 4.1 AIX 5.3 ML1 with: CSM 1.3.n GPFS 2.3 or 3.1 RVSD 4.1 AIX 6.1 SP2 with CSM 1.7.0.1

SDD PCM

Enhanced concurrent mode volume groups only. HACMP-XD is not supported with SDD PCM. February 27, 2008 DS8000 series Interoperability Matrix Page 21

IBM CLUSTER 1600 SERVERS

Servers System p 610 Models 6C1, 6EModels 6C3, 6EModels 6F0, 6FModels 6C4, 6EModel BModel 6MModel Models 6H0, 6H1, 6MModel Model SModel 681 IBM 2005 Models B16, B32, B64, B5K 2005 Models H08, H16, RModels E12, Models 12E, 16E, Models 32E, Models 140, Models R04, R16, Model NModel AModels F16, FModel M12, M14, MModels S08, SModel F08 McDATA ED-5000 ES-3016, ES-3032 Intrepid 6064, 6140 Sphereon 3216, 3232 4300, 4500 Operating Systems AIX
Host Adapters IBM RS/6000 FC 5716 FC 5758 FC 5759 FC 6228 FC 6239
Fabric Support Cisco MDS 9020, 9120, 9124, 9140 MDS 9216, 9216A, 9216I MDS 9506, 9509, 9513 MDS 9134, 9222i CNT (Inrange) FC/9000-64, -128, -256 2042-N16
Version 5 5.1 ML7 5.2 ML5 5.3 ML1
Refer to the most current APARs for AIX 5.2 ML5 (or later) and AIX 5.3 ML1 (or later). February 27, 2008 DS8000 series Interoperability Matrix Page 22

This Interoperability file will be sunsetting, please begin to use and familiarize yourself with the System Storage Interoperation Center (SSIC): http://www.ibm.com/servers/storage/support/config/ess/index.jsp DS Open API (CIM Agent): Available for AIX 5.1 ML7 (or later). DS CLI: Available for AIX 5.1 ML7 (or later), 5.2 ML5 (or later) and 5.3 ML1 (or later). SDD: Available for AIX 5.1 ML7 (or later), 5.2 ML5 (or later), and 5.3 ML1 (or later)

SAN Boot support:

The DS8100 and DS8300 are supported as a boot device on IBM Cluster 1600 servers that support Fibre Channel boot capability. Refer to the IBM System Storage DS8000 Host Systems Attachment Guide for additional information.
Path Control Module (SDDPCM): Available for AIX 5.1 ML7 (or later), 5.2 ML5 (or later), and 5.3 ML1 (or later. MPIO with latest released maintenance levels.

Page 23

Table 7: AIX Clustering for IBM Cluster 1600 Servers
DS8100 Model 921 & Turbo Model 931 AIX 5.1 ML7 with: GPFS 2.2 PSSP 3.4 RVSD 3.5 AIX 5.2 ML5 with: GPFS 2.2, 2.3 or 3.1 PSSP3.4, 3.5 RVSD 3.5 or 4.1 AIX 5.3 ML1 with: GPFS 2.3 or 3.1 CSM 1.3.n RVSD 4.1 AIX 6.2 SP2 with: CSM 1.7.0.1

SDDPCM

Page 24
IBM SYSTEM Z AND S/390 SERVERS
Servers System z z800 IBM 2066 System z z890 IBM 2086 System z z900 and z990 IBM 2064 IBM 2084 z9 BC IBM 2096 z9 EC IBM 2094 S/390 Parallel Enterprise Server IBM 9672 Generation 3 IBM 9672 Generation 4 IBM 9672 Generation 5 IBM 9672 Generation 6 ES/9000 IBM 9021 IBM 9121 IBM 9221 ES/3090 IBM 3090 S/390 Multiprise 3000 Enterprise Server IBM 7060 S/390 Multiprise 2000 Enterprise Server IBM 2003 Red Hat Enterprise Linux 3 and above 4 U2, U3, and above SUSE SLES 8 and above SLES 9 SP2, SP3 and above SLES 10, SP1 and above Transaction Processing Facility (TPF) Version 4 Release 1 VSE/ESA Version 2 Release 7@ z/VSE Version 3 Release 1 Version 4 Release 1 z/VM Version 4 Release 4 Version 5 Release 1 Version 5 Release 2 Version 5 Release 3
Operating Systems z/OS Version 1 Release 4 Version 1 Release 5 Version 1 Release 6 Version 1 Release 7 Version 1 Release 8 Version 1 Release 9 z/OS.e Version 1 Release 4 Version 1 Release 5 Version 1 Release 6 Version 1 Release 7 Version 1 Release 8 Version 1 Release 9
Host Adapters All ESCON host adapter features offered on the servers are supported.
Fabric Support IBM 9032 Model Model Model 005
z990 requires driver level 55. February 27, 2008 DS8000 series Interoperability Matrix Page 25
Servers System z z800 IBM 2066 System z z890 IBM 2086 System z z900 and z990 IBM 2064 IBM 2084 z9 BC IBM 2096 z9 EC IBM 2094 S/390 Parallel Enterprise Server IBM 9672 Generation 5 IBM 9672 Generation 6 z/VM Version 4 Release 4 Version 5 Release 1 Version 5 Release 2 Version 5 Release 3 z/VSE Version 3 Release 1 Version 4 Release 1 VSE/ESA Version 2 Release 7@ Transaction Processing Facility (TPF) Version 4 Release 1 Red Hat Enterprise Linux 3 and above 4 U2, U3, U4, U5 and above 5.1 SUSE SLES 8 and above SLES 9 SP2, SP3 and above SLES 10, SP1 and above McDATA ED-5000 Intrepid 6064, 6140 Sphereon 3232

Host Adapters System z FC 2315 FC 2318 FC 2319 FC 2320 FC 3319 FC 3320 FC 3321 FC 3322 FC 3323 FC 3324 S/390 FC 2314 FC 2316
Fabric Support Cisco MDS 9216 MDS 9506, 9509, 9513 MDS 9134, 9222i CNT (Inrange) FC/9000-64, -128, -256 2042-N16 IBM 2005 Model B32, BModels 32E, Models 140, Models R16, Model NModel FModel M12, M14, M48
FC 3319 and FC 3320 Host Adapters are supported only on the IBM System z 890 and IBM System z 990 Servers. z990 requires driver level 55. February 27, 2008 DS8000 series Interoperability Matrix Page 26
Servers System z z800 IBM 2066 System z z890 IBM 2086 System z z900 and z990 IBM 2064 IBM 2084 z9 BC IBM 2096 z9 EC IBM 2094
Operating Systems z/VM Version 4 Release 4 Version 5 Release 1 Version 5 Release 2 Version 5 Release 3 z/VSE Version 3 Release 1 Version 3 Release 1.1 Version 4 Release 1 Red Hat Enterprise Linux 4.4, 4.5 and above SUSE SLES 8 Submarine and above SLES 9, SP2, SP3 and above SLES 10 SP1 and above
Host Adapters System z FC 2315 FC 2318 FC 2319 FC 2320 FC 3319 FC 3320 FC 3321 FC 3322 FC 3324
Fabric Support Cisco MDS 9216, 9216A, 9216I MDS 9506, 9509, 9513 MDS 9134, 9222i CNT (Inrange) FC/9000-64, -128, -256 2042-N16 IBM 2005 Models B16, B32, B64, B5K 2005 Models H08, H16, RModels 32E, Model NModel FModels S08, S16 McDATA Intrepid 6064
FC 3319 and FC 3320 Host Adapters are supported only on the IBM System z 890 and IBM System z 990 Servers. z990 requires driver level 55. February 27, 2008 DS8000 series Interoperability Matrix Page 27
DS Open API (CIM Agent): Not available for System z. DS CLI: Not available for System z. Fibre Channel Protocol (FCP): Multi-path support is available with LVM. Multi-path support for RHEL 4.4 and above, RHEL 5.1 and above, SLES 9 sp3 and above, and SLES 10 sp1 and above are all available with DMM.

Page 28

This page is intentionally left blank.

Page 29

SUN SERVERS
Servers Enterprise 220R, 250, 420R, 450 3000, 4000, 5000, 6000 3500, 4500, 5500, Netra 1125 SPARCcenter / SPARCserver 1000, 1000E 2000, 2000E Sun Fire V120, V210, V240, V250 V280R V440, V480, V490 V880, V890, V4800, 4810, 6800, 6900 12000, 15000 E20K, E25K E2900,E4900, E6900 T1000, T2000 Ultra 1, 2, 5, 10, 20, 30, 60, 80 Opteron
Operating Systems Solaris 8 Sun Cluster 3.MPxIO 4.4.2 thru 4.4.VERITAS Volume Manager with DMP 3.5, 4.0 MP2, 4.1 VERITAS Cluster Server 3.5, 4.0, 4.1 9

Host Adapters AMCC/JNI

Fabric Support Cisco MDS 9020, 9120, 9124, 9140 MDS 9216, 9216A, 9216I MDS 9506, 9509, 9513 MDS 9134, 9222i
FCX-6562 / FCX2-6562 FCE-1473-N FCE-6460-N Emulex LP9002L / LP9002DC LP9002S LP9402DC LP9802 LP10000 / LP10000DC LP11000 LP11002 QLogic QLA2310F/QLA2310FL
CNT (Inrange) FC/9000-64, -128, -256 2042-N16 IBM 2005 Models B16, B32, B64, B5K 2005 Models H08, H16, RModels E12, Models 12E, 16E, Models 32E, Models 140, Models R04, R16, Model NModel AModels F16, F32

Sun Cluster 3.MPxIO 4.4.2 thru 4.4.VERITAS Volume Manager with DMP 3.5, 4.0 MP2, 4.1, 5.0 VERITAS Cluster Server 3.5, 4.0, 4.1, 5.0 SF RAC 4.1, 5.0 10, u1, u2, u3
QLA2340/L / QLA2342/L QLA2460 QLA2462 Sun 6727A 6757A 6767A (SG-XPCI1FC-QF2) 6768A (SG-XPCI2FC-QF2) 6799A SG-XPCI1FC-EM2 SG-XPCI1FC-EM4-Z SG-XPCI2FC-EM2 SG-XPCI2FC-EM4-Z SG-XPCI1FC-QL2 SG-XPCI1FC-QF4 SG-XPCI2FC-QF2-Z SG-XPCI2FC-QF4

Sun Cluster 3.1, 3.2

MPxIO (Driver Bundled with OS) 4.1, 5.0 VERITAS Cluster Server 4.1, 5.0 SF RAC 4.1, 5.0
VERITAS Volume Manager with DMP
2109 Model M12, M14, MModels S08, SModel F08 McDATA ED 5000 ES-3016, ES-3032 Intrepid 6064, 6140 Sphereon 3216, 3232 4300, 4500
x4100, x4200, x4600 V20z & V40z
The Sun filesystem requires patch 113454-14.
MPxIO is supported with the Sun host adapters as well as generic adapter as supported by Sun. MPxIO 4.4.9 is not supported. MPxIO 4.4.10 and 4.4.11 are required for 4 node support. Not interoperable with DS8100 or DS8300 Fibre Channel ports shared with remote mirror and copy configurations. CDSDisk is supported with VERITAS VxVM 4.0 maintenance pack 2, or contact VERITAS Support for latest Hot Fix. Sun Solaris 10 is not supported with AMCC / JNI host adapters. Sun Solaris 10 OS support with Host Adapters LP10000DC and QLA2462 only. Sun Cluster 3.2 is supported with 2 thru 4 nodes. A SCSI-3 reservation is recommended. February 27, 2008 DS8000 series Interoperability Matrix Page 30
DS Open API (CIM Agent): Not available for Solaris. DS CLI: Available for Solaris 8, 9, and 10. SAN Boot is supported with Solaris 8, 9 and 10. SDD: Available for Solaris 8, 9, and 10 Available for Solaris 10 with Opteron x64 Servers Available to coexist with Veritas Volume Manager 4.1 for Solaris 9 and 10 Solaris 10 Container not supported. SDD is not supported in Sun Cluster environments. SDD does not support Sun adapters. SDD is not supported with SAN Boot.

Page 31

X86 BASED SERVERS NETWARE
Servers Intel Pentium II Xeon and above 1.5 Ghz or faster processors 512 MB RAM or higher IBM BladeCenter HSHSHS21 XM 7995 HSLS20 LSLSIBM System x Servers 100 206/206m 225/226 235/260/3800 306/306m 335/336 345/346 360/365 366/3850 440/445 450/455 460/3950/3950E

IBM BladeCenter HSHSHS21 XM 7995 HSLSLSLS41 7972
IBM 13N2203 26K4841 26R0884 26R0890 39Y9186 39Y9306 41Y8527 48P7061 Emulex LP1005DC 43W6859 Emulex LP9402DC LP9802 LP9002 / LP9002DC LP10000 / LP10000DC LP11000 / LPE11002 LPE11000 / LPE11002 IBM Netfinity / System x P/N 19K1246 P/N 24P0960 QLogic QLA2310F / QLA2310FL QLA2340/L / QLA2342/L QLA2460 / QLA2462 QLE2460 / QLE2462
VMware guest support Windows 2000 Windows 2003 R2 SUSE SLES 8, 9, 10 Red Hat Enterprise Linux 2.1, 3, 4

IBM System x Servers

100, 206, 206m, 225, 226, 235, 236, 255, 260, 306, 325, 326, 326m, 335, 336, 345, 346, 360, 365, 366, 440, 445, 450, 455, 460, 3105, 3200, 3250, 3400, 3455, 3500, 3550, 3650, 3655, 3755, 3800, 3850, 3950, 3950E,
For more information on server minimum requirements, refer to: http://www.vmware.com/products/server/esx_specs.html For more information on VMware guest support, refer to: http://www.vmware.com/support/pubs/vi_pubs.html Supported via RPQ only. For information on OS and HBA support, refer to the following link: http://www.ibm.com/servers/eserver/serverproven/compat/us/ Requires VMWare ESX 3.0 and above For the official support date for this release, check the VMware Website. February 27, 2008 DS8000 series Interoperability Matrix Page 34
DS Open API (CIM Agent): Not available with VMware. DS CLI: Available for VMware 3.n.n. SDD: Not available for VMware. SAN Boot is supported with ESX 2.5.n and ESX 3.n

Page 35

X86, EM64T, IA64, AND AMD64 BASED SERVERS - LINUX
Servers Intel Pentium II Xeon and above 1.5 Ghz or faster processors 512 MB RAM or higher AMD Chipset
Operating Systems Red Hat Enterprise Linux 2.U6, U7, U8 VERITAS Volume Manager with DMP 4.0 MP2, 4.1 4.0 MP2, 4.1
1.6 GHz or faster 512 MB RAM or higher IBM BladeCenter HSHS21 XM 7995 HSLSLSLSIBM System x Servers

VERITAS Cluster Server

4 (AS, ES) U2, U3, 4.4, 4.5, 4.6 VERITAS Volume Manager with DMP 4.1 , 5.0 VERITAS Cluster Server 4.1 , 5.0 5, 5.1 SUSE
IBM 13N2203 26K4841 26R0884 26R0890 39Y9186 39Y9306 41Y8527 48P7061 Emulex LP1005DC 43W6859 Emulex LP9002L / LP9002DC LP9402DC LP9802 LP10000/LP10000DC LP11000 (IBM P/N 42D0405) LP11002 (IBM P/N 42D0407) LPE11000 (IBM P/N 42C2069) LPE11002 (IBM P/N 42C2071) IBM Netfinity/ System x P/N 19K1246 P/N 24P0960 P/N 39M5894 P/N 39M5895 QLogic
MDS 9020, 9120, 9124, 9140 MDS 9216, 9216A, 9216I MDS 9506, 9509, 9513 MDS 9134, 9222i CNT (Inrange) FC/9000-64, -128, -256 2042-N16 IBM 2005 Models B16, B32, B64, B5K 2005 Models H08, H16, RModels E12, Models 12E, 16E, Models 32E, Models 140, Models R04, R16, Model NModel A16, F16, FModel M12, M14, MModels S08, SModel F08 IBM BladeCenter P/N 02R9080 P/N 26K5601 , 26K6477 P/N 26R0881 P/N 32R1790, 32R1812 P/N 32R1813, 32R1833 P/N 39Y9208, 39Y9280 P/N 39Y9284 P/N 43W6723 P/N 48P7062 P/N 90P0165 McDATA ED-5000, ES-3016, ES-3032 Intrepid 6064, 6140 Sphereon 3216, 3232 4300, 4500

Page 51

APPENDIX C: SAN FABRIC PRODUCTS
Fibre Channel / FICON Intermix
The DS8000 series supports Fibre Channel / FICON intermix. With intermix, both FCP (Fibre Channel Protocol) and FICON upper level protocols can be supported within the same director when deployed independently by port. For specific support, implementation details and operational information for using intermix, refer to the Fibre Channel Director websites. Table 11: SAN Fabric Products
Product Cisco MDS 9120 Cisco MDS 9124 Cisco MDS 9134 Cisco MDS 9140 Cisco MDS 9216 Cisco MDS 9216A Cisco MDS 9216i Cisco MDS 9222i Cisco MDS 9506 Cisco MDS 9509 Cisco MDS 9509 Cisco MDS 9513 CNT (INRANGE) FC/9000-64 CNT (INRANGE) FC/9000-128 CNT (INRANGE) FC/9000-256 CNT UMD IBM 2005 Model B16 IBM 2005 Model B32 IBM 2005 Model B64 IBM 2005 Model H08 IBM 2005 Model H16 IBM 2005 Model R18 IBM 2026 Model 12E IBM 2026 Model 16E IBM 2026 Model 416 IBM 2026 Model 32E IBM 2026 Model 432 IBM 2026 Model 224 IBM 2026 Model E12 IBM 2027 Model 140 IBM 2027 Model 232 IBM 2027 Model 256 IBM 2027 Model R04 IBM 2027 Model R16 February 27, 2008 P/N 2027140 P/N 2027232 SAN256M SAN04M-R SAN16M-R SAN432M-2 P/N 2026224 SAN416M-2 IBM Machine Type and Model or Part Number IBM 2061 Model 020 IBM 2053 Model 424 IBM 2053 Model 434/S34 IBM 2061 Model 040 IBM 2062 Model D01 IBM 2062 D1A / IBM 2054 D1A IBM 2062 D1H / IBM 2054 D1H IBM 2054 Model E01 IBM 2062 Models D04 / T04 IBM 2062 Models D07 / T07 IBM 2054 E07 IBM 2054 E11 / IBM 2062 E11 IBM 2042 Model 001 IBM 2042 Model 128 IBM 2042 Model 256 IBM 2042 Model N16 2005B16 P/N 2005B32 P/N 2005B64 P/N 2005H08 P/N 2005H16 2005R18 Description Cisco 9120 Multilayer Fabric Switch (2Gb, 20-port) Cisco 9124 Multilayer Fabric Switch (4Gb, 24-port) Cisco 9134 Multilayer Fabric Switch (4Gb, 32-port) Cisco 9140 Multilayer Fabric Switch (2Gb, 40-port) Cisco 9216 Multilayer Fabric Switch (2Gb, 48-port) Cisco 9216A Multilayer Fabric Switch (2Gb, multi-port) Cisco 9216I Multilayer Fabric Switch (2Gb, multi-port) Cisco 9222I Multilayer Fabric Switch (4 GB, 18/4 ports FCP/IP) Cisco 9506 Mulilayer Director (2Gb, 128-port) Cisco 9509 Multilayer Director (2Gb, 224-port) Cisco 9509 Multilayer Director (4Gb, 224-port) Cisco 9513 Multilayer Director (4Gb, from 12 to 528 ports) CNT (INRANGE) FC/9000 Fibre Channel Director (2Gb, 64-port) CNT (INRANGE) FC/9000 Fibre Channel Director (2Gb, 128-port) CNT (INRANGE) FC/9000 Fibre Channel Director (2Gb, 256-port) CNT Ultranet Multi-service Director (2Gb, 256-port) IBM TotalStorage SAN16B (4Gb, 8-, 12- & 16- port) IBM TotalStorage SAN32B-2 (4Gb, 32-port) IBM System Storage SAN Switch (4Gb 32, 48, and 64 ports) IBM TotalStorage SAN Switch H08 (2Gb, 8-port) IBM TotalStorage SAN Switch H16 (2Gb, 16-port) IBM System Storage SAN Router SAN18B-R (4Gb, 16ports, GbE 2 ports) IBM TotalStorage SAN Switch HVEC Model (4Gb, 12-port) IBM TotalStorage SAN Switch HVEC Model (4Gb, 16-port) IBM TotalStorage SAN Switch (4Gb, 16-port) IBM TotalStorage SAN Switch HVEC Model (4Gb, 32-port) IBM TotalStorage SAN Switch (4Gb, 32-port) IBM TotalStorage SAN24M-1 (2Gb, 24-port) IBM TotalStorage SAN12 (2 Gb, 12-port) IBM TotalStorage SAN140M (2/4 Gb, 140-port) IBM TotalStorage SAN32M-1 (2Gb, 32-port) IBM TotalStorage SAN256M (10Gb ISL capable, 2/4 GB 256 port) IBM SAN router 4 ports (iFCP x2 and iSCSI x2) IBM SAN Router 12 + 4 ports DS8000 series Interoperability Matrix Page 52

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. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol ( or ), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks might 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 the International Business Machines Corporation in the United States, other countries, or both:
AIX BladeCenter CICS DB2 developerWorks DS4000 DS6000 DS8000 Dynamic Infrastructure ECKD Enterprise Storage Server FICON FlashCopy GPFS HyperSwap i5/OS IBM IMS iSeries MVS Parallel Sysplex Power Architecture POWER Hypervisor Power Systems POWER5 POWER6+ POWER6 POWER7 PowerHA PowerVM POWER pSeries Redbooks Redpaper Redbooks (logo) Resource Link Resource Measurement Facility RMF Smarter Planet System i System p System Storage DS System Storage System z10 System z TDMF Tivoli TotalStorage WebSphere z/OS z/VM z/VSE z10 z9 zSeries
The following terms are trademarks of other companies: Disk Magic, and the IntelliMagic logo are trademarks of IntelliMagic BV in the United States, other countries, or both. Snapshot, and the NetApp logo are trademarks or registered trademarks of NetApp, Inc. in the U.S. and other countries. Novell, SUSE, the Novell logo, and the N logo are registered trademarks of Novell, Inc. in the United States and other countries. Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation and/or its affiliates. QLogic, and the QLogic logo are registered trademarks of QLogic Corporation. SANblade is a registered trademark in the United States. Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Itanium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names might be trademarks or service marks of others.

Preface

This IBM Redbooks publication addresses host attachment and interoperability considerations for the IBM System Storage DS8000 series. Within this book, you can find information about the most popular host operating systems platforms, including Windows, AIX, VIOS, Linux, Solaris, HP-UX and the IBM z/OS. The topics covered in this book target administrators or other technical personnel with working knowledge of storage systems and a general understanding of open systems. You can use this book as guidance when installing, attaching, and configuring System Storage DS8000. The practical, usage-oriented guidance provided in this book complements the IBM System Storage DS8000 Host Systems Attachment Guide, SC26-7917.

Chapter 3. Virtual I/O Server considerations
Optical DVD-RAM backed by file Tape devices with virtual tape support that enables serial sharing of selected SAS tape devices Figure 3-2 shows virtual SCSI emulation on a VIOS server.
Figure 3-2 VSCSI emulation on VIOS
When using virtual SCSI emulation on the VIOS with DS8000 storage system volumes, all the DS8000 volumes that are to be used as backing devices for the client partitions have to be mapped directly to the VIOS partition using the WWPNs of the physical Fibre Channel adapters in the VIOS partition. You can find the WWPNs of the VIOS Fibre Channel adapters using the lsdev -dev fcsX -vpd command for the particular adapter (X=0, 1, 2, and so on), in the VIOS, as shown in Example 3-1.
Example 3-1 List WWPNs o the Fibre Channel adapters in the Virtual I/O Server $ lsdev -SA -l fcs* | while read a b; do echo $a $(lsdev -dev $a -vpd | grep Network); done fcs0 Network Address.10000000C9836A8A fcs1 Network Address.10000000C9836A8B
To assign volumes to the VIOS on the DS8000 storage system, complete the following steps: 1. Create DS8000 volume group for the volumes accessed by the VIOS using the mkvolgrp command with hosttype pSeries parameter. 2. Create DS8000 host connections for the Fibre Channel adapters in VIOS using the mkhostconnect command with hosttype pSeries parameter and an unused port group, for example, port group 60, to group multiple host connections of the same host or hosts, which share the same volumes together. 3. Create and assign DS8000 volumes to the DS8000 volume group using the mkfbvol command. Example 3-2 on page 35 shows use of extent pools P8 and P9 as storage pools and volume IDs from the logical subsystem (LSS) 60 / rank group 0 and LSS 61 / rank group 1. 4. Assign DS8000 volume group to DS8000 host definition for the VIOS using the managehostconnect command.
Example 3-2 shows the output when you create a host attachment and assign DS8000 volumes to VIOS.
Example 3-2 Creating a host attachment and assigning DS8000 volumes to VIOS dscli> mkvolgrp -hosttype pSeries p570_vio1 CMUC00030I mkvolgrp: Volume group V15 successfully created. dscli> mkhostconnect -wwname 10000000C9836A8A -hosttype pSeries -portgrp 60 p570_vio1_0 CMUC00012I mkhostconnect: Host connection 0019 successfully created. dscli> mkhostconnect -wwname 10000000C9836A8B -hosttype pSeries -portgrp 60 p570_vio1_1 CMUC00012I mkhostconnect: Host connection 001A successfully created. dscli> mkfbvol -cap CMUC00025I mkfbvol: CMUC00025I mkfbvol: CMUC00025I mkfbvol: CMUC00025I mkfbvol: CMUC00025I mkfbvol: dscli> mkfbvol -cap CMUC00025I mkfbvol: CMUC00025I mkfbvol: CMUC00025I mkfbvol: CMUC00025I mkfbvol: CMUC00025I mkfbvol: 50 FB FB FB FB FB 50 FB FB FB FB FB -extpool p8 volume 6000 volume 6001 volume 6002 volume 6003 volume 6004 -extpool p9 volume 6100 volume 6101 volume 6102 volume 6103 volume 6104 -name p570_vio1 -volgrp v15 6000-6004 successfully created. successfully created. successfully created. successfully created. successfully created. -name p570_vio1 -volgrp v15 6100-6104 successfully created. successfully created. successfully created. successfully created. successfully created.

retry_timeout rw_timeout scbsy_dly scsi_id start_timeout unique_id ww_name
20 0xc0d200B75TV181600007210790003IBMfcp 0x500507630a0b029f
Retry Timeout READ/WRITE time out value delay in seconds for SCSI BUSY SCSI ID START unit time out value Device Unique Identification FC World Wide Name
True True True False True False False
When using a redundant dual VIOS setup with DS8000 devices as virtual SCSI backing devices and native AIX MPIO in the client partition, see the setup recommendations for virtual SCSI redundancy in PowerVM Virtualization on IBM System p: Introduction and Configuration Fourth Edition, SG24-7940. An overview of recommended MPIO settings in the VIOS partition and AIX client partition is shown in Figure 4-2 on page 51. In a dual VIOS setup where the same DS8000 volume is assigned to both VIOS partitions and mapped as backing device to the same client partition, you must set the reserve_policy attribute on the device to no_reserve, which is already the default for DS8000 devices with SDDPCM installed. Also, the recommended AIX MPIO device attributes algorithm (load_balance), hcheck_mode (nonactive) and hcheck_interval (60 seconds) are already set by default for DS8000 devices with current SDDPCM releases. For dual VIOS setups, change the default values of the attributes fc_err_recov and dyntrk of the Fibre Channel adapters child device, fscsiX, to the settings shown in Example 3-11 on both virtual I/O servers.
Example 3-11 Changing the fscsi attributes in a dual VIOS setup
$ chdev -dev fscsi0 -attr fc_err_recov=fast_fail dyntrk=yes -perm fscsi0 changed Changing the fc_err_recov attribute to fast_fail will fail any I/Os immediately, if the adapter detects a link event, such as a lost link between a storage device and a switch. The fast_fail setting is only recommended for dual VIOS configurations. Setting the dyntrk attribute to yes enables the VIOS to allow cabling changes in the SAN. Both virtual I/O servers need to be rebooted for these changed attributes to take effect. Applying changes: Changes applied with the chdev command and the -perm option require a restart to become effective.
3.3 Using NPIV with IBM VIOS and DS8000
VIOS 2.1 release with fix pack FP20.1 (or later) introduced virtual Fibre Channel capabilities, NPIV, to IBM Power Systems, considerably extending the virtualization capabilities and enabling innovative solutions with IBM Power Systems and SAN storage. NPIV is a standardized method for virtualizing a physical Fibre Channel port. The PowerVM implementation of NPIV enables POWER lLPARs to have virtual Fibre Channel adapters, each with a dedicated WWPN.
With NPIV and unique WWPNs, a system partition has its own identity in the SAN with direct access to both disk and tape SAN storage devices, as shown in Figure 3-4. It is supported, for example, with the IBM 8 Gbps Fibre Channel HBA #5735.

Example 4-1 List WWPNs of the Fibre Channel adapters in an AIX partition
# lsdev -SA -l "fcs*" fcs0 Available 00-08 fcs1 Available 00-09 fcs2 Available 10-T1 fcs3 Available 11-T1
FC Adapter FC Adapter Virtual Fibre Channel Client Adapter Virtual Fibre Channel Client Adapter
# lsdev -SA -l "fcs*"|while read a b; do echo $a $(lscfg -vl $a|grep Net); done fcs0 Network Address.10000000C9702268 fcs1 Network Address.10000000C9702269 fcs2 Network Address.C050760035A80142 fcs3 Network Address.C050760035A80144 Example 4-1 shows two physical fcs0, fcs1 and two virtual fcs2, fcs3 Fibre Channel adapters in the AIX partition. Alternatively, if you have SDD or SDDPCM already installed on your machine (see 4.3, Multipathing with AIX on page 53 for details), you can use either the datapath or the pcmpath command to get the list of WWPNs. Both commands use the same syntax. Example 4-2 shows a list of WWPNs after using the pcmpath command.
Example 4-2 SDD WWPN query
# pcmpath query Adapter Name fscsi0 fscsi1 fscsi2 fscsi3
wwpn PortWWN 10000000C9702268 10000000C9702269 C050760035A80142 C050760035A80144
Complete the following steps on the DS8000 storage system to directly assign volumes to an AIX partition using Fibre Channel adapters: 1. Create a DS8000 volume group for the volumes accessed by the AIX server using the mkvolgrp command with hosttype pSeries. 2. Create DS8000 host connections for the Fibre Channel adapters in the AIX server using the mkhostconnect command with hosttype pSeries and an unused port group port group 61 to group multiple host connections of the same host or hosts sharing the same volumes. This simplifies connection management later. Also you can assign a volume group to a host connection definition at this time, or do it later using managehostconnect command. 3. Create and assign DS8000 volumes to DS8000 volume group using the mkfbvol command or later using chvolgrp command. Example 4-3 on page 47 shows these examples: extent pools P8 and P9 as storage pools and volume IDs from LSS of 60 per rank group 0, and LSS 61 per rank group 1. 4. Assign DS8000 volume group to DS8000 host definition for the AIX server using the managehostconnect command if not already done with mkhostconnect command.

Figure 4-2 Recommended MPIO attributes for DS8000 devices in a dual VIOS setup
Using the default attributes for MPIO multipathing of the virtual SCSI disk devices in the AIX client partition, as shown in Example 4-6 on page 49, set the hcheck_interval from 0
(disabled) to a recommended value of 60 seconds on the client partition in a dual VIOS setup, as shown in Example 4-10, so that the path status is updated automatically. The hcheck_interval attribute defines how often the health check is performed. The attribute hcheck_mode is set to the recommended value of nonactive by default, which means that health check commands are sent down all paths that have no active I/O, including paths with a state of failed. In that case, after one VIOS fails and then comes back, manually set the path as available. Changing hcheck_interval is recommended for all virtual SCSI hdisk devices, as shown in Example 4-10.
Example 4-10 Changing the hcheck_interval to 60 seconds for a Virtual SCSI Disk
# chdev -l hdisk2 -a hcheck_interval=60 -P hdisk2 changed The hcheck_interval must never be set lower than the read or write time-out value of the underlying physical disk on the VIOS, which is 60 seconds for a DS8000 volume being used as backing device with SDDPCM (see Example 3-10 on page 40). Otherwise, if the Fibre Channel adapter has an error, there will be new health check requests sent before the running ones time out and this can lead to an adapter failure condition. Set attribute: Set the hcheck_interval attribute value to 60. Also, as shown in Example 4-6 on page 49, the default queue depth of a virtual SCSI disk device is set to 3. When a DS8000 volume is used as backing device on the VIOS with a default queue depth of 20, as shown in Example 3-10 on page 40, with SDDPCM, consider increasing the queue depth of the virtual SCSI disk device to the same value shown in Example 4-11 for best performance. With 512 command elements on the virtual SCSI client adapter (vscsiX) of which 2 are used by the adapter, 3 are reserved for each VSCSI LUN for error recovery, and the rest are used for I/O requests, you cannot configure more than 22 DS8000 LUNs as backing devices for a given VSCSI adapter pair, when using a queue depth of 20 for the virtual SCSI disk device.

5.2.4 Checking attached volumes
The easiest method to check for DS8000 volumes attached to the Linux system is to use the lsscsi command, as shown in Example 5-12.
Example 5-12 Listing attached SCSI devices
x3650lab9:~ # lsscsi [0:0:0:0] disk [2:0:0:0] cd/dvd [3:0:0:0] disk [3:0:0:1] disk [3:0:0:2] disk [3:0:0:3] disk [3:0:1:0] disk [3:0:1:1] disk [3:0:1:2] disk [3:0:1:3] disk [4:0:0:0] disk [4:0:0:1] disk [4:0:0:2] disk [4:0:0:3] disk [4:0:1:0] disk [4:0:1:1] disk [4:0:1:2] disk [4:0:1:3] disk
ServeRA MATSHITA IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
Drive 1 V1.0 UJDA770 DVD/CDRW 1.24 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288 2107900.288
/dev/sda /dev/sr0 /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdk /dev/sdl /dev/sdm /dev/sdn /dev/sdo /dev/sdp /dev/sdq
Example 5-12 on page 73 shows that Linux recognized 16 DS8000 devices. By viewing the SCSI addresses in the first column, you can determine that there actually are four DS8000 volumes, each connected through four paths. Linux creates a SCSI disk device for each of the paths. Red Hat Enterprise Linux installer: The Red Hat Enterprise Linux installer does not install lsscsi by default. It is shipped with the distribution, but must be selected for installation.
5.2.5 Linux SCSI addressing
The quadruple in the first column of the lsscsi output is the internal Linux SCSI address. It is, for historical reasons, constructed like a traditional parallel SCSI address. It consists of four fields: HBA ID. Each HBA in the system, be it parallel SCSI, FC, or even a SCSI emulator, gets a host adapter instance when it is initiated. Channel ID. This ID is always zero. It was formerly used as an identifier for the channel in multiplexed parallel SCSI HBAs. Target ID. For parallel SCSI, this is the real target ID; the one set through a jumper on the disk drive. For Fibre Channel, it represents a remote port that is connected to the HBA. With it, you can distinguish between multiple paths and between multiple storage systems. LUN. This is rarely used in parallel SCSI. In Fibre Channel, they are used to represent a single volume that a storage system offers to the host. The LUN is assigned by the storage system. Figure 5-1 illustrates how the SCSI addresses are generated.
Figure 5-1 Understanding the composition of Linux internal SCSI addresses

Mounted on / /devices /system/contract /proc /etc/mnttab /etc/svc/volatile /system/object /dev/fd /tmp /var/run /dev/vx/dmp /dev/vx/rdmp /export/home /03461 /20781
To expand the volume on the DS8000, use the chfbvol command, as shown in Example 6-13.
Example 6-13 Expanding a volume
dscli> chfbvol -cap Date/Time: October 18, 2007 1:10:52 PM CEST IBM DSCLI Version: 5.3.0.991 DS: IBM.2107-7520781 CMUC00332W chfbvol: Some host operating systems do not support changing the volume size. Are you sure that you want to resize the volume? [y/n]: y CMUC00026I chfbvol: FB volume 4704 successfully modified. The new capacity must be larger than the previous one; you cannot shrink the volume. To check that the volume has been expanded, use the lsfbvol command, as shown in Example 6-14.
Example 6-14 lsfbvol after expansion
dscli> lsfbvol 4704 Date/Time: November 7, 2007 11:05:15 PM CET IBM DSCLI Version: 5.3.0.991 DS: IBM.2107-7520781 Name ID accstate datastate configstate deviceMTM datatype extpool cap (2^30B) cap (10^9B) cap (blocks) ================================================================================================================== ITSO_v880_Online Normal Normal 2107-900 FB 512 P53 18.0 37748736
In Example 6-14, the volume 4704 has been expanded to 18 GB in capacity. To see the changed size of the volume on the Solaris host after the expansion, use the luxadm command (Example 6-15).
Example 6-15 luxadm output after volume expansion
bash-3.00# luxadm display /dev/rdsk/c2t50050763030CC1A5d0s2 DEVICE PROPERTIES for disk: /dev/rdsk/c2t50050763030CC1A5d0s2 Status(Port A): O.K. Vendor: IBM Product ID: 2107900 WWN(Node): 5005076303ffc1a5 WWN(Port A): 50050763030cc1a5 Revision:.991 Serial Num: 75207814704 Unformatted capacity: 18432.000 MBytes Write Cache: Enabled Read Cache: Enabled Minimum prefetch: 0x0 Maximum prefetch: 0x16 Device Type: Disk device Path(s): /dev/rdsk/c2t50050763030CC1A5d0s2 /devices/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50050763030cc1a5,0:c,raw /dev/rdsk/c3t50050763031CC1A5d0s2 /devices/pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w50050763031cc1a5,0:c,raw
The disk now has a capacity of 18 GB. To use the additional capacity, issue the vxdisk resize command, as shown in Example 6-16.
Example 6-16 VxVM commands after volume expansion bash-3.00# vxdisk resize IBM_DS8x001_0 bash-3.00# vxdisk list IBM_DS8x001_0 Device: IBM_DS8x001_0 devicetag: IBM_DS8x001_0 type: auto hostid: v880 disk: name=IBM_DS8x001_0 id=1194446100.17.v880 group: name=20781_dg id=1194447491.20.v880 info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2 flags: online ready private autoconfig autoimport imported pubpaths: block=/dev/vx/dmp/IBM_DS8x001_0s2 char=/dev/vx/rdmp/IBM_DS8x001_0s2 guid: {fbdbfe12-1dd1-11b2-af7c-0003ba43fdc1} udid: IBM%5F2107%5F7520781%5F6005076303FFC1A50000000000004704 site: version: 3.1 iosize: min=512 (Bytes) max=2048 (blocks) public: slice=2 offset=65792 len=37677568 disk_offset=0 private: slice=2 offset=256 len=65536 disk_offset=0 update: time=1194473744 seqno=0.16 ssb: actual_seqno=0.0 headers: configs: count=1 len=48144 logs: count=1 len=7296 Defined regions: config priv 000048-000239[000192]: copy=01 offset=000000 enabled config priv 000256-048207[047952]: copy=01 offset=000192 enabled log priv 048208-055503[007296]: copy=01 offset=000000 enabled lockrgn priv 055504-055647[000144]: part=00 offset=000000 Multipathing information: numpaths: 2 c2t50050763030CC1A5d0s2 state=enabled c3t50050763031CC1A5d0s2 state=enabled

AVAILABLE DISK SELECTIONS: 0. c0t0d0 <FUJITSU-MAW3073NC-3701 cyl 24345 alt 2 hd 8 sec 737> /pci@83,4000/FJSV,ulsa@2,1/sd@0,0 1. c1t0d0 <FUJITSU-MAW3073NC-3701 cyl 24345 alt 2 hd 8 sec 737> /pci@83,4000/FJSV,ulsa@2/sd@0,0 2. c3t500507630A03029Fd0 <IBM-2107900-.268 cyl 4367 alt 2 hd 30 sec 64> /pci@80,2000/emlx@2/fp@0,0/ssd@w500507630a03029f,0 3. c3t500507630A03029Fd1 <IBM-2107900-.268 cyl 8736 alt 2 hd 30 sec 64> /pci@80,2000/emlx@2/fp@0,0/ssd@w500507630a03029f,1 4. c3t500507630A03029Fd2 <IBM-2107900-.268 cyl 17918 alt 2 hd 64 sec 256> /pci@80,2000/emlx@2/fp@0,0/ssd@w500507630a03029f,2 5. c4t500507630A00029Fd0 <IBM-2107900-.268 cyl 4367 alt 2 hd 30 sec 64> /pci@80,2000/emlx@1/fp@0,0/ssd@w500507630a00029f,0 6. c4t500507630A00029Fd1 <IBM-2107900-.268 cyl 8736 alt 2 hd 30 sec 64> /pci@80,2000/emlx@1/fp@0,0/ssd@w500507630a00029f,1 7. c4t500507630A00029Fd2 <IBM-2107900-.268 cyl 17918 alt 2 hd 64 sec 256> /pci@80,2000/emlx@1/fp@0,0/ssd@w500507630a00029f,2 3. Customize /kernel/drv/scsi_vhci.conf, as shown in Example 6-25.
Example 6-25 Customizing /kernel/drv/scsi_vhci.conf
bash-3.00# more /kernel/drv/scsi_vhci.conf # # Copyright 2004 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # #pragma ident "@(#)scsi_vhci.conf 1.9 04/08/26 SMI" # name="scsi_vhci" class="root"; # # Load balancing global configuration: setting load-balance="none" will cause # all I/O to a given device (which supports multipath I/O) to occur via one # path. Setting load-balance="round-robin" will cause each path to the device # to be used in turn. # load-balance="round-robin"; # # Automatic failback configuration # possible values are auto-failback="enable" or auto-failback="disable" auto-failback="enable"; # # For enabling MPxIO support for 3rd party symmetric device need an # entry similar to following in this file. Just replace the "SUN SENA" # part with the Vendor ID/Product ID for the device, exactly as reported by # Inquiry cmd. # # device-type-scsi-options-list = device-type-scsi-options-list = # "SUN SENA", "symmetric-option"; "IBM 2109700", "symmetric-option"; # 120
# symmetric-option = 0x1000000; symmetric-option = 0x1000000; 4. Enter the stmsboot -e command to reactivate MPxIO, as shown in Example 6-26.
Example 6-26 Reactivating MPxIO

Chapter 7. HP-UX considerations
The HP-UX device file for the HBA is a required parameter. , shows the N_port Port World Wide Name and that the HBAs are dual port devices, therefore, you see two WWPNs for each HBA.
7.5 Configuring the HP-UX host for the DS8000
To configure a server on the DS8000, define a host connection using the DS GUI or the DS CLI. The hosttype parameter is required for this definition. Predefined, hosttype HP, automatically configures the DS8000 to present the DS8000 volumes in an HP-UX preferred method. For HP-UX server attachment to DS8000, LUN IDs greater than x'3FFF' are not supported, see page 124. When you create or assign LUNs and volumes, only LUN and volume IDs less than x'3FFF' are recognized. This limits the maximum number of volumes that are allowed for HP host types to 16384. With HP-UX 11i v3, HP introduced several major changes, especially in the I/O area, such as: Persistent device special files (DSFs) are created independently from the underlying hardware path information and the number of physical paths to a device. The generic syntax of a persistent DSF for a LUN is /dev/(r)disk/diskN, with N being the device instance number, for example, /dev/(r)disk/disk14. This kind of representation scheme is called agile view. The older format for device special file names, such as /dev/(r)dsk/c12t0d1, is still available and is called legacy DSF in HP-UX 11iv3. Accordingly, this representation is called legacy view. After you configure the volumes on the DS8000, connect your host to the fabric, then discover the devices by using the ioscan command. Example 7-3 shows that the DS8000 devices have been discovered successfully, but the devices cannot be used, because no special device file is available.
Example 7-3 Discovered DS8000 devices without a special device file # ioscan -fnC disk Class I H/W Path Driver S/W State H/W Type Description ======================================================================= disk 2 0/0/3/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C /dev/dsk/c0t0d0 /dev/rdsk/c0t0d0 disk 0 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 146 GMAT3147NC /dev/dsk/c2t0d0 /dev/rdsk/c2t0d0. disk 7 0/2/1/0.71.10.0.46.0.1 sdisk CLAIMED DEVICE IBM 2107900 disk 8 0/2/1/0.71.42.0.46.0.1 sdisk CLAIMED DEVICE IBM 2107900 disk 6 0/2/1/0.71.51.0.46.0.1 sdisk CLAIMED DEVICE IBM 2107900 disk 11 0/5/1/0.73.10.0.46.0.1 sdisk CLAIMED DEVICE IBM 2107900 disk 9 0/5/1/0.73.42.0.46.0.1 sdisk CLAIMED DEVICE IBM 2107900 disk 10 0/5/1/0.73.51.0.46.0.1 sdisk CLAIMED DEVICE IBM 2107900

Exclude disks from hot-relocation use? [y,n,q,?] (default: n) A new disk group will be created named dg01 and the selected disks will be added to the disk group with default disk names. c10t6d0 c10t6d1 Continue with operation? [y,n,q,?] (default: y) Do you want to use the default layout for all disks being initialized? [y,n,q,?] (default: y) n Do you want to use the same layout for all disks being initialized?
[y,n,q,?] (default: y) Enter the desired format [cdsdisk,hpdisk,q,?] (default: cdsdisk) Enter the desired format [cdsdisk,hpdisk,q,?] (default: cdsdisk) Enter desired private region length [<privlen>,q,?] (default: 1024) Initializing device c10t6d0. Initializing device c10t6d1. VxVM NOTICE V-5-2-120 Creating a new disk group named dg01 containing the disk device c10t6d0 with the name dg0101. VxVM NOTICE V-5-2-88 Adding disk device c10t6d1 to disk group dg01 with disk name dg0102. Add or initialize other disks? [y,n,q,?] (default: n) # vxdisk list DEVICE TYPE c2t0d0 auto:none c2t1d0 auto:none c10t0d1 auto:none c10t6d0 auto:hpdisk c10t6d1 auto:hpdisk c10t6d2 auto:none n hpdisk hpdisk

DISK dg0101 dg0102 -

GROUP dg01 dg01 -

invalid invalid invalid

invalid
The graphical equivalent for the vxdiskadm utility is the VERITAS Enterprise Administrator (VEA). Figure 7-1 shows the presentation of disks, using this GUI. After creating the disk groups and the VxVM disks, create file systems and mount them, as shown in Figure 7-1.
Figure 7-1 Disk presentation by VERITAS Enterprise Administrator

7.8 Working with LUNs

This topic provides considerations for expanding LUNs, and working with large LUNs.

7.8.1 Expanding LUNs

Assuming the creation of a volume group (vg01), as described in and a logical volume called (r)lvol1, Example 7-10 shows how to setup vg01.
Example 7-10 Inquiring the volume group
# vgdisplay -v vg01 --- Volume groups --VG Name VG Write Access VG Status Max LV Cur LV Open LV Max PV Cur PV Act PV Max PE per PV
/dev/vg01 read/write available 8000
VGDA PE Size (Mbytes) Total PE Alloc PE Free PE Total PVG Total Spare PVs Total Spare PVs in use --- Logical volumes --LV Name LV Status LV Size (Mbytes) Current LE Allocated PE Used PV --- Physical volumes --PV Name PV Status Total PE Free PE Autoswitch
/dev/vg01/lvol1 available/syncd 3000 1
/dev/disk/disk14 available On
Example 7-11 shows the layout of the physical volume that is the underlying device in vg01.
Example 7-11 Inquiring the physical volume

Device 3

and and and and
Initialize system Recover Configuration Restore Disk Unit Data Upgrade Load Source
Figure 9-36 Installing Licensed Internal Code and initialize system
9.7.1 Boot from SAN and cloning
When booting from SAN support, you can take advantage of certain advanced features available with the DS8000 series and copy services functions. These functions provide the ability to perform a rapid copy of the data held on DS8000 LUNs. Therefore, when you have a system that only has external LUNs with no internal drives, you are able to create a clone of your system. Important: For the instances in this topic, a clone is a copy of a system that only uses external LUNs. Boot, or IPL, from SAN, is therefore a prerequisite for this function.

Why consider cloning

By using the cloning capability, you can create a complete copy of your entire system in minutes. You can then use this copy in any way you want, for example, you can use it to minimize your backup windows, or protect yourself from a failure during an upgrade, or even use it as a fast way to provide yourself with a backup or test system. You can do all of these tasks using cloning with minimal impact to your production operations.

When to use cloning

You need enough free capacity on your external storage unit to accommodate the clone. If Metro Mirror or Global Mirror are used, you need enough bandwidth on the links between the DS8000 primary and secondary site.
Consider that the copy services need enough resources on the primary and secondary DS8000 to ensure that there will be only a minimal performance impact on the production IBM i system. Do not attach a clone to your network, until you have resolved any potential conflicts that the clone has with the parent system.

9.8 Migrating

For many System i clients, migrating to the DS8000 is best achieved using traditional save and restore techniques. However, there are several alternatives you might want to consider, such as 9.8.1, Metro Mirror and Global Copy on page 185, or 9.8.2, IBM i data migration on page 185.
9.8.1 Metro Mirror and Global Copy
Depending on the existing configuration, it might be possible to use Metro Mirror or Global Copy to migrate from an IBM TotalStorage Enterprise Storage Server (ESS) or any other DS8000 family model to a newer DS8000 model, or any combination of external storage units that support Metro Mirror and Global Copy. For more information about Metro Mirror and Global Copy, see IBM System Storage DS8000: Copy Services in Open Environments, SG24-6788. You can use DS8000 copy services for migration when the IBM i has the load source unit and all the other disks on a DS8000, and you plan to migrate the IBM i workload to another DS8000 on 1000 km remote location, with the two storage systems connected through dark fiber. To do this, you must establish a Global Copy relationship with IBM i LUNs at the remote DS8000. When ready to migrate to the remote site, you must also do a complete shutdown of the IBM i to ensure all data is written to disk, and wait until Global Copy transfers all the updates to the remote DS8000 with no out of synch tracks. Additionally, unassign the DS8000 LUNs on local site and assign the DS8000 LUNs to the remote IBM i LPAR. After the IPL of the IBM i, the new DS8000 LUNs are recognized by IBM i.

Scalability enhancements that provide additional performance improvements by: Bypassing dynamic pathing validation in channel recovery for reduced recovery I/Os. Reducing elapsed time by reducing the wait time in channel path recovery.

Large volume support

As storage facilities tend to expand to larger capacities, the UCBs 64 K limitation is approaching at a rapid rate. Therefore, large volume support must be planned for. Support has been enhanced to expand volumes to cylinders, using existing 16-bit cylinder addressing. This is often referred to as 64 K cylinder volumes. Components and products that previously shipped with cylinders, now also support cylinders, such as: Direct access device space management (DADSM) or common volume table of contents (VTOC) access facility (CVAF) DFSMS functional component (DFSMSdss) ICKDSF a device support facility Data Facility Sort (DFSORT) a high-speed data-processing utility Checkpoint restart processing now supports a checkpoint data set that resides partially or wholly above the cylinder boundary. With logical volumes (LVs), the VTOC has the potential to grow large. Callers such as DFSMSdss have to read the entire VTOC to find the last allocated data set control block (DSCB). In cases where the VTOC is large, you can experience performance degradation. An interface is implemented to return the highly allocated DSCB on volumes initialized with an indexed VTOC. DFSMSdss uses this interface to limit VTOC searches and to improve performance. The VTOC has to be within the first 64 K-1 tracks, but the index can be anywhere on the volume.

Extended address volumes

With LVs support, it is possible to address a capacity of up to 3.964 PB, where 64 K subchannels multiplied by 55.6 GB per volume, equals to 3.64 PB. To accommodate the needs of installations that require super large volumes, IBM has developed an volume, an extended address volume (EAV) called the 3390 Model A, shown in Figure 10-1.
cylinder-managed space Cylinders > 65,520

track-managed space

Cylinders < or = 65,520
Figure 10-1 Entire new EAV
For the 3390 Model A, support has been enhanced to expand the volumes to cylinders, using 28-bit cylinder addressing, which currently has a limit of 256 M tracks. The existing CCHH track address became CCCCcccH x, where the cylinder address is cccCCCC x and the head address is H x, H=0-14. EAV: Starting with EAV, there is a partial change from track to cylinder addressing. The partial change from track to cylinder addressing creates two address areas on EAV volumes: Track managed space is the area on an EAV located within the first cylinders. Using the 16-bit cylinder addressing enables a theoretical maximum address of cylinders. In order to allocate more cylinders, you need to have a new format to address the area of more than cylinders. With 16-bit cylinder numbers, the existing track address format is CCCCHHHH: The 16-bit track number is represented with HHHH. The 16-bit track cylinder is represented with CCCC. Cylinder managed space is the area on an EAV located before the first cylinders. This space is allocated in multicylinder units (MCU), which have a size of 21cylinders. To address the extended capacity on an EAV, the new cylinder-track address format for 28-bit cylinder numbers is CCCCcccH: The H represents a 4-bit track number from zero to 14. The high order 12 bits of a 28-bit cylinder number is represented with ccc. The low order 16 bits of a 28-bit cylinder number is represented with CCCC. Components and products, such as DADSM/CVAF, DFSMSdss, ICKDSF, and DFSORT, also now support cylinders. Consider the following examples: DS8000 and z/OS limit CKD EAV volume size: For 3390 Model A, one to cylinders or about 223 GB of addressable storage. For 3390 Model A, up to 236 times the size of 3390 Model 1, which is four times the size as with LV. Configuration granularity: For 1 cylinder boundary sizes, 1 to cylinders For 1113 cylinders boundary sizes; 56,763 (51 x 1113) to (236 x 1113) cylinders The size of an existing Model 3/9/A volume can be increased to its maximum supported size using dynamic volume expansion. This can be done with the DS CLI command, as shown in Example 10-1.

Read availability mask support
Dynamic channel path identifier management (DCM) provides you with the ability to define a pool of channels that is managed by the system. The channels are added and deleted from control units based on workload importance and availability needs. DCM attempts to avoid single points of failure when adding or deleting a managed channel by not selecting an interface on the control unit on the same I/O card.
Initial program load enhancements
During the IPL sequence, the channel subsystem selects a channel path to read from the system residence volume SYSRES device. Certain types of I/O errors on a channel path cause the IPL to fail even though there are alternate channel paths that might work. For example, consider a situation where you have a bad switch link on the first path but good links on the other paths. In this case, you cannot IPL, because the same faulty path is always chosen. The channel subsystem and z/OS are enhanced to retry I/O over an alternate channel path. This circumvents IPL failures that are caused by the selection of the same faulty path to read from the SYSRES device.

DS8000 device definition

To exploit the increase in the number of LSSs that can be added in the DS8000 (255 LSSs), the unit must be defined as 2107 in the HCD or input/output configuration program. The host supports 255 logical control units when the DS8000 is defined as UNIT=2107. You must install the appropriate software to support this setup. If you do not have the required software support installed, you can define the DS8000 as UNIT=2105, but then, only the 16 logical control units (LCUs) of address group 0 can be used. Starting with z9-109 processors, you can define an additional subchannel set with ID 1, class 1 (SS 1) on top of the existing subchannel set class 0 (SS 0) in a channel subsystem. With this additional subchannel set, you can configure more than 2 x 63 K devices for a channel subsystem. With z/OS V1.7+, you can define PAV alias devices of type 3380A and 3390A, of the DS8000 (2107) DASD control units to SS 1. Device numbers can be duplicated across channel subsystems and subchannel sets.
Read control unit and device recognition for DS8000
The host system informs the attached DS8000 of its capabilities, so that it supports native DS8000 control unit and devices. The DS8000 then only returns information that is supported by the attached host system, using the self-description data, such as read data characteristics, sense ID, and read configuration data. The following commands display device type 2107 in their output: DEVSERV QDASD and PATHS command responses IDCAMS LISTDATA COUNTS, DSTATUS, STATUS, and IDCAMS SETCACHE