Ss 481 Stud

IBM TotalStorage DS8000
and DS6000 Implementation

Workshop for Open Systems
(Course Code SS48)
Student Notebook
ERC 1.0
IBM Certified Course Material

V3.1.0.1
cover
Front cover
Student Notebook
August 2005 Edition
The information contained in this document has not been submitted to any formal IBM test and is distributed on an as is basis without
any warranty either express or implied. The use of this information or the implementation of any of these techniques is a customer
responsibility and depends on the customers ability to evaluate and integrate them into the customers operational environment. While
each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will
result elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk.
Copyright International Business Machines Corporation 2005. All rights reserved.
This document may not be reproduced in whole or in part without the prior written permission of IBM.
Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.
Trademarks
IBM is a registered trademark of International Business Machines Corporation.
The following are trademarks of International Business Machines Corporation in the United
States, or other countries, or both:
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product and service names may be trademarks or service marks of others.
AIX DB2 eServer
Enterprise Storage Server ESCON FICON
FlashCopy HACMP Hypervisor
i5/OS iSeries OS/400
POWER POWER5 PowerPC
Predictive Failure Analysis pSeries RS/6000
TotalStorage Virtualization Engine xSeries
z/OS zSeries
Student Notebook
V3.1.0.1
TOC
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Copyright IBM Corp. 2005 Contents iii
Contents
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Course Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Unit 1. DS8000 Hardware Components and Architecture . . . . . . . . . . . . . . . . . . 1-1
Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.1 DS8000 Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Topic: DS8000 Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
DS8000 Series Models (2107) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
DS8000 Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
DS8000 Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Interfaces to DS8000 (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Interfaces to DS8000 (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
IBM TotalStorage Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
DS8000 Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Host Connectivity: IBM Subsystem Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
DS8000 Enhancements At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
DS8000 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
1.2 DS8000 Hardware Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Topic: DS8000 Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
DS8000: Primary Frame Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
DS8000 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
DS8000 Hardware Components Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
DS8000 Processor Complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
DS8000 Processor Complex: Power5 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
DS8000 Processor Complex PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
DS8000 Processor Complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
DS8000 Persistent Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
DS8000 I/O Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
RIO-G and I/O Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
DS8000 RIO-G Port: Layout Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
Bus Interconnect Performance Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
DS8000 Host Adapters HA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
Host Adapter with Four Fibre Channel Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
DS8000 FCP/FICON Host Adapters: HA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
DS8000 FICON/FCP Host Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
DS8000 Device Adapter DA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37
Fibre Channel Device Adapters with Two Gbps Ports . . . . . . . . . . . . . . . . . . . . . 1-38
DS8000 Device Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
DS8000 RAID Device Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
RAID and Logical Volume Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41
DS8000 Storage Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
Student Notebook
iv DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
16 Drive Disk Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-43
DS8000 Switched FC-AL Disk Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-44
DS8000 and DS6000 Switched FC-AL/FC-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-45
Switched FC-AL Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-46
DS8000: Storage Enclosure and DA Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-47
DS8000 Storage Enclosure and DA Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-48
1.3 DS8000 Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
Topic: DS8000 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-50
DS8000: Primary Frame Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-51
DS8000 Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-52
IBM TotalStorage DS8100 (2-Way) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-53
DS8300 (4-Way with Two Expansion Frames) . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-54
DS8100 (Model 921) - 2-way . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-55
DS8300 (Models 922 and 9A2) - 4-way . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-56
DS8000 Storage Enclosure Connectivity (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . .1-57
DS8000 Storage Enclosure Connectivity (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . .1-58
DS8000 2 way - Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-59
DS8000 4 way - Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-60
1.4 DS8000 Cache Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61
Topic: DS8000 Cache Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-62
Sequential Prefetching in Adaptive Replacement Cache (SARC) . . . . . . . . . . . . .1-63
DS8000 and DS6000 Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-64
DS8000 and DS6000 Caching Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-65
1.5 DS8000 RAS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-67
Topic: DS8000 RAS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-68
DS8000 Hardware Components Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-69
Processor Complex RAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-70
Hypervisor Storage Image Independence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-71
Server RAS (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-72
Server RAS (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-73
Server Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-74
NVS Recovery After Complete Power Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-75
Host Connection Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-76
Whats New with SDD 1.6.0.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-77
Disk Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-78
Disk Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-79
Power and Cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-81
Microcode Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-82
Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-83
Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-85
Unit 2. DS8000 Virtualization Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
2.1 Physical Configuration Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Topic: Physical Configuration Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Physical Configuration Concepts: Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
DS8000 / DS6000 - Storage Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
Student Notebook
V3.1.0.1
TOC
Copyright IBM Corp. 2005 Contents v
Storage Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
DS8000 Switched Loop Layout in an Enclosure Pair . . . . . . . . . . . . . . . . . . . . . . . 2-9
DS8000 Array Across Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
DS6000 Physical Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
DS6000 Array Sites on Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
DS8000 Creating an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Array Site Configurations: DS8000 Eight DDMs/Array with Arrays Across Loops 2-14
DS8000 AAL Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Sparing Rules (DS8000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Sparing Example 1 - RAID 5: DS8000 All Same Capacity, Same RPM . . . . . . . . 2-17
Sparing Example 2 - RAID 10: DS8000 All Arrays Same Capacity and Same RPM
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Sparing Example 3 DS8000 RAID 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
DS6000 Creating an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
DS6000: Four DDM Arrays (Not at GA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Arrays: Eight DDM Arrays On Loop for DS6000 . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Two Array Sites Configurations: DS6000 Eight DDMs/Array with Arrays on Loop 2-23
One Array Site Configurations: DS6000 (After GA) Four DDMs/Array with Arrays on
Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Sparing Rules (DS6000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Sparing Example 1 - RAID 5: DS6000 All Same Capacity, Same RPM . . . . . . . . 2-26
Sparing Example 2 - RAID 10: DS6000 All Same Capacity, Same RPM . . . . . . . 2-27
Sparing Example 3 - RAID 5: DS6000 All Same RPM . . . . . . . . . . . . . . . . . . . . . 2-28
Sparing Example 4 RAID 5: DS6000 Different Size and RPM . . . . . . . . . . . . . . 2-29
Capacity Magic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Floating Spare Rules (DS6000 and DS8000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
DS8000/DS6000: Forming a Rank (Example, FB with 1 GB Extents) . . . . . . . . . 2-33
DS6000/DS8000 Extent Pool Concept Summary . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
Device Configuration Extent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Extents / Extent Pools Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Extent Pools Example in a Mixed CKD and FB Environment . . . . . . . . . . . . . . . . 2-37
Logical Volume Concept (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Logical Volume Concept (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Virtualization Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
I/O Ports (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
I/O Ports (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
Volume Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Volume Groups and Host Attachment (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
Volume Groups and Host Attachment (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Hosts and Volume Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
2.2 Logical Configuration Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
Topic: Logical Configuration Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Physical Infrastructure Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
LSS / LCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
LSS Groups and LSS Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
LSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Student Notebook
vi DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
Address Group (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-55
Address Group (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-56
LSS and Address Group Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-57
Logical Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-58
Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-59
Logical Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-60
Virtualization Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-61
Extent Pools (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-62
Extent Pools (2 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-63
Extent Pools (3 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-64
Extent Pools (4 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-65
Volumes (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-66
Volumes (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-67
Volumes (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-68
Volume Groups (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-69
Volume Groups (2 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-70
Volume Groups (3 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-71
DS6800 LSS Dual Pathed Host (Recommended) . . . . . . . . . . . . . . . . . . . . . . . . .2-72
Volume Groups (4 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-73
Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-76
Unit 3. DS8000 Command Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
3.1 Introduction and Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Topic: DS CLI Introduction and Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
DS Command Line Interface (CLI) Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
Whats New? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
Supported DS CLI Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
DSCLI Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10
DSCLI Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
Management Consoles: HMC / SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12
DS CLI Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13
DS6000 Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14
3.2 DSCLI Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Topic: DS CLI Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16
DS CLI Installation (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17
DS CLI Installation (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18
Unzipped DSCLI CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19
DSCLI - Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20
Starting DSCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21
DSCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22
DS CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23
DSCLI Profile File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-24
DSCLI Profile File Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-25
3.3 DSCLI Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Topic: DSCLI Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28
Student Notebook
V3.1.0.1
TOC
Copyright IBM Corp. 2005 Contents vii
Three Ways to Use DSCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
DSCLI Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
DSCLI DSCLI Script Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
3.4 Configuration Process using DSCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Topic: Configuration Process using DSCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
DS8000/DS6000 - Storage Virtualization Overview . . . . . . . . . . . . . . . . . . . . . . . 3-35
Storage Hierarchy Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Physical Infrastructure Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Initial Configuration Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
DS CLI User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
DSCLI User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
New DSCLI Password Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
3.5 DSCLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Topic: DSCLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
DSCLI Command Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
DSCLI Flag Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Command Flag Parameters or Profile File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
DS CLI Command Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
List and Show Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
Getting Help with DSCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Object ID Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Infrastructure IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
Object IDs (1 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Object IDs (2 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Object IDs (3 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Object IDs (4 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Object IDs (5 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57
1750 Host IOPORT Port Numbers from DS CLI . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Sample CLI Configuration Script (1 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
Unit 4. DS6000 Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.1 DS6000 Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Topic: DS6000 Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
DS6000 Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
DS6000 Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
DS6000 Model EX1 Hardware Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Disk Enclosure Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
DS6800 Model 1750-EX1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Disk Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.2 DS6000 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Topic: DS6000 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Student Notebook
viii DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
DS6000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17
DS6800 with One Expansion Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-18
DS6000 Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-19
Sequential Prefetching in Adaptive Replacement Cache (SARC) . . . . . . . . . . . . .4-20
Disk Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-22
Four Data Paths To Every Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-23
Components Architecture (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-24
Components Architecture (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-25
DS6000 Host and Device Adapter Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-26
DS6000 Device Adapter Ports for Disk Enclosure EX1 . . . . . . . . . . . . . . . . . . . . .4-27
DS6000 Switched Disk Expansion (13 Max) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-28
DS6000 RAID Array Supported Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . .4-29
Preferred Path What Is It? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-30
DS6800 LSS Single Pathed Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32
4.3 DS6000 Reliability, Availability Serviceability . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Topic: DS6000 Reliability, Availability, Serviceability . . . . . . . . . . . . . . . . . . . . . . .4-34
High Availability and Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-35
Server Failover and Failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-37
NVS Recovery After Complete Power Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-38
Major Components BBUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-39
Serviceability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-40
DS6000 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-41
Light Path Diagnostics In MR 1750 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-42
DS6000 Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-43
Rear Panel Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-44
DS6000 Maintenance and Support: Call Home and Remote Support . . . . . . . . . .4-45
Logs: Realtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-46
Log Display: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-47
4.4 DS6000 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Topic: DS6000 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-50
DS6000 Installability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-51
Installation Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-52
Storage Management Console (SMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-54
DS Storage Manager Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . .4-55
DS6000 SMC Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-56
HA with Storage Management Console (SMC) . . . . . . . . . . . . . . . . . . . . . . . . . . .4-57
Installing Storage and Server Enclosures in a Rack . . . . . . . . . . . . . . . . . . . . . . . .4-58
DS6000 Server Enclosure Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . .4-59
Connect Power Cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-60
Connect Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-61
Connect Storage Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-62
Setting the IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-63
Disk Storage Feature Activation (DSFA) is a Customer Web Application . . . . . . .4-64
Starting DSFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-65
License Activation (Enter 32-Digit Code) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-66
DS6000 - Select DS6000 Series Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-67
Student Notebook
V3.1.0.1
TOC
Copyright IBM Corp. 2005 Contents ix
DS6000 - View Feature Activation Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Storage Complex Real-Time Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
Storage Unit - Real-time Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70
Assign the Storage Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
Storage Unit Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
DFSA Feature Activation Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73
Update Activation Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Enter Customer Account Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75
Enter Customer Shipping Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
Enter Customer Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77
Set up Call Home Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Update DS6000 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
Activate Remote Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
View Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
Volume Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
Unit 5. DS8000 Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.1 DS8000 Storage Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
DS8000 Management Console Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
DS8000 Management Console Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
DS8000 MC Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
DS8000 MC and a Pair of Ethernet Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
DS8000 MC and Ethernet Switches Plugging (Back View) . . . . . . . . . . . . . . . . . . . 5-9
DS8000 MC Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
DS8000 and DS6000 Remote Access Features . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
DS8000 MC Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
DS8000 MC Network Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Redundant DS8000 MC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
DS8000 MC User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
DS6000 and DS8000 Remote Support through VPN . . . . . . . . . . . . . . . . . . . . . . 5-16
How Virtual Private Network (VPN) Operates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
DS8000 MC Remote Service Security (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
DS8000 MC Remote Service Security (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
MC Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
DS8000 MC Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Unit 6. DS8000 Storage Manager GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6.1 DS Storage Manager GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Topic: DS Storage Manager GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
DS Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
DS8000 Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
DS Storage Manager Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Student Notebook
x DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
DS Storage Manager Realtime Manager - DS8000 . . . . . . . . . . . . . . . . . . . . . . . . .6-9
DS Storage Manager Simulated Manager DS8000 . . . . . . . . . . . . . . . . . . . . . . .6-10
DS Storage Manager Realtime and Simulated Managers DS6000 . . . . . . . . . . .6-11
DS Storage Manager and DS CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12
Realtime versus Simulated Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . .6-13
Exporting Logical Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14
Unlock Admin Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-15
6.2 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Topic: Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-18
DS Storage Manager Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . .6-19
DS Storage Manager Supported Client Browsers . . . . . . . . . . . . . . . . . . . . . . . . .6-20
DS8000 Storage Manager Installation Process (1 of 7) . . . . . . . . . . . . . . . . . . . . .6-21
6.3 Activating Keys and Storage Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
Topic: Activating Keys and Storage Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-30
Storage Image (DS8000*) Apply Activation Keys . . . . . . . . . . . . . . . . . . . . . . . .6-31
Storage Image (DS8000*) - Apply Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .6-32
Apply Configuration Select Application Method . . . . . . . . . . . . . . . . . . . . . . . . . .6-33
Apply Configuration Select Storage Complex . . . . . . . . . . . . . . . . . . . . . . . . . . .6-34
Apply Configuration - Authenticate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-35
Apply Configuration Select Storage Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-36
Manage Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-37
User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-38
Add User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-39
6.4 Architecture and Logical Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . 6-41
Topic: Logical Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-42
Recommended Logical Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-43
DS Storage Manager Signon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-44
DS Storage Manager Welcome Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-45
Import Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-46
Create Storage Complex (DS8000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-47
Create Storage Complex Define Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-48
Create Storage Unit General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-49
Create Storage Unit - Specify DDMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-50
Create Storage Unit - Define Licensed Function . . . . . . . . . . . . . . . . . . . . . . . . . .6-51
Create Storage Unit - Define Licensed Function (Details) . . . . . . . . . . . . . . . . . . .6-52
Create Storage Unit - Specify I/O Adapters (DS8000*) . . . . . . . . . . . . . . . . . . . . .6-53
Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-54
Finish Creating the Storage Complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-55
Import Storage Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-56
Add Imported Storage Unit to Complex (DS8000) . . . . . . . . . . . . . . . . . . . . . . . . .6-57
Long Running Task Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-58
Student Notebook
V3.1.0.1
TOC
Copyright IBM Corp. 2005 Contents xi
Create Host System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59
Create Host System General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-60
Create Host System Define Host Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
Host Attachment Identifier Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-62
Create Host System - Specify WWPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63
Create Host System - Specify Storage Image (DS8000*) . . . . . . . . . . . . . . . . . . . 6-64
Create Host System Specify Storage Image Parameters . . . . . . . . . . . . . . . . . 6-65
Format I/O Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66
Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-67
Host Attachment Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-68
Create Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69
Create Array Definition Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-70
Create Array - Auto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-71
Add Arrays to Ranks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-72
Create Array - Custom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-73
Create Extent Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74
Create Extent Pool Auto (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-75
Create Extent Pool - Auto (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-76
Create Extent Pool Reserve Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77
Create Extent Pool - Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-78
Create Extent Pool - Custom Define Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 6-79
Create Extent Pool Custom Select Ranks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80
Create FB Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-81
Create FB Volume Select Extent Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-82
Create FB Volume Define Volume Characteristics . . . . . . . . . . . . . . . . . . . . . . 6-83
Create FB Volume Define Volume Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84
Create FB Volume Create Volume Nicknames . . . . . . . . . . . . . . . . . . . . . . . . . 6-85
Create FB Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86
Create FB Volume Group Define Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-87
Create FB Volume Group Select Host Attachments . . . . . . . . . . . . . . . . . . . . . 6-88
Create FB Volume Group Select Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-89
Help for Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-90
DS Storage Manager Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-91
6.5 Summary of Logical Configuration Differences. . . . . . . . . . . . . . . . . . . . . . . . . 6-93
Topic: Summary of Logical Configuration Differences . . . . . . . . . . . . . . . . . . . . . 6-94
Summary of Logical Configuration Differences (1 of 2) . . . . . . . . . . . . . . . . . . . . . 6-95
Summary of Logical Configuration Differences (2 of 2) . . . . . . . . . . . . . . . . . . . . . 6-96
DS8000/DS6000 and ESS Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-97
DS Storage Manager Logical Configuration Summary . . . . . . . . . . . . . . . . . . . . . 6-98
Express Configuration (DS6000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-99
Express Configuration Volume Creation Open Systems . . . . . . . . . . . . . . . . . 6-100
Express Configuration - Volume Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-102
Express Configuration - Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-103
Express Configuration - Host Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-104
Express Configuration - Host Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-105
Express Configuration -- Host WWPNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106
Express Configuration -- Assign Host to Volume Group . . . . . . . . . . . . . . . . . . . 6-107
Student Notebook
xii DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
Other Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-108
Storage Image (DS8000*) Apply Activation Keys . . . . . . . . . . . . . . . . . . . . . . .6-109
Storage Image (DS8000*) - Apply Configuration . . . . . . . . . . . . . . . . . . . . . . . . .6-110
Apply Configuration Select Application Method . . . . . . . . . . . . . . . . . . . . . . . . .6-111
Apply Configuration Select Storage Complex . . . . . . . . . . . . . . . . . . . . . . . . . .6-112
Apply Configuration - Authenticate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-113
Apply Configuration Select Storage Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-114
Manage Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-115
User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-116
Add User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-117
Help for Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-118
Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-120
Unit 7. DS8000 and DS6000 Performance, TPC and Productivity Data Center Utility
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2
7.1 DS8000 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Topic: DS8000 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4
Host Adapter Performance - Single Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5
Maximum Total System IOPS/sec, Open and z/OS . . . . . . . . . . . . . . . . . . . . . . . . .7-6
Sequential Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-7
Total Disk System Sequential Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8
z/OS Cache Standard Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9
Open Systems 70/30/50 Workload ESS 800 and DS8100 . . . . . . . . . . . . . . . . . . .7-10
Global Mirror Write Overhead for Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11
ESS 800 PPRC versus DS8000 Global Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-12
FlashCopy Performance Improvements with DS8000 . . . . . . . . . . . . . . . . . . . . . .7-13
7.2 DS6000 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Topic: DS6000 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16
How Migrating to DS6800 Might Affect Hit Ratios . . . . . . . . . . . . . . . . . . . . . . . . .7-17
Cache Read Hit Performance - 512 Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-18
Cache Read Hit Performance - 64 KB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-19
DS6800 Cache Read Hit Performance (Max IOPs) . . . . . . . . . . . . . . . . . . . . . . . .7-20
DS6800 Cache Read Hit Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-21
DS6800 OLTP Workloads (RAID5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-22
DS6800 4 KB Read Miss Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-23
Full Box 64 KB Sequential Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-24
Single Stream 64 KB Sequential Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-25
7.3 TotalStorage Productivity Center (TPC) and Productivity Data Center Utility (PDCU)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Topic: TotalStorage Productivity Center (TPC) and Productivity Data Center Utility
(PDCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-28
Storage Infrastructure Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-29
Overview of TPC V2R3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-30
The Performance Data Collection Utility (PDCU) . . . . . . . . . . . . . . . . . . . . . . . . . .7-31
PDCU Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-32
PDCU - Supported Platforms and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-33
Student Notebook
V3.1.0.1
TOC
Copyright IBM Corp. 2005 Contents xiii
PDCU Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Configuring and Running PDCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
Where the PDCU Data is Stored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
PDCU Sample Configuration Data Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
PDCU Script Invocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
The Report Generator Example Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
Port Performance Data Collected via PDCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Rank Performance Data Collected via PDCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
Volume Performance Data Collected via PDCU . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Volume Performance Data Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
Port Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49
Rank Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
Volume Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51
PDCU Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52
PDCU Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53
Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-55
Unit 8. DS Copy Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
8.1 Advanced Copy Services Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Topic: Local Flash Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
FlashCopy Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
FlashCopy NOCOPY to COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Persistent Flash Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Multiple Relationship FlashCopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Incremental FlashCopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
FlashCopy Consistency Group Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
8.2 Remote Mirror and Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Topic: Remote Mirror and Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Disk Storage Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Metro Mirror (Synchronous PPRC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Global Copy (PPRC XD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
FlashCopy on Remote Mirror and Copy Primary . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
IBM TotalStorage Metro Mirror / Global Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
PPRC Global Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
PPRC Global Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
PPRC-XD Normal Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
PPRC Async Increment Pending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
PPRC Async Run Consistency Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Back to Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
8.3 Advanced Copy Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Topic: Advanced Copy Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
Advanced Copy Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
IBM TotalStorage Metro/Global Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28
Statement of Direction: Metro/Global Copy Enhancement . . . . . . . . . . . . . . . . . . 8-29
DS8000 LPAR and Copy Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
License for FlashCopy (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
Student Notebook
xiv DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
License for FlashCopy (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-32
Licence for Remote Mirror Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-33
8.4 DSCLI for Copy Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
Topic: DS CLI for Copy Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-36
Whats New? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-37
ESS Copy Services Command Flow with CS CLI . . . . . . . . . . . . . . . . . . . . . . . . .8-38
DS8000 Copy Services Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-39
DS8000 CLI Copy Services Command Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-40
DS6000 CLI Copy Services Command Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-41
CLI Copy Services Coexistence for ESS and DS . . . . . . . . . . . . . . . . . . . . . . . . . .8-42
DS CLI Copy Services Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-43
DS CLI FlashCopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-44
DS CLI PPRC - Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-45
DS CLI PPRC Global Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-46
DS CLI PPRC - Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-47
DS CLI Clearvol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-48
DS CLI PPRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-49
8.5 DS Storage Manager for Copy Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-51
Topic: DS Storage Manager Copy Services GUI . . . . . . . . . . . . . . . . . . . . . . . . . .8-52
DS Storage Manager Copy Services GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-53
GUI Create FlashCopy Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-54
GUI FlashCopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-55
GUI Select FlashCopy Options (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-56
GUI Select FlashCopy Options (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-57
Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-58
GUI LSS Copy Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-59
Metro Mirror Real-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-60
DS8000 GUI Copy Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-61
Communicate with ESS Copy Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-62
Create FlashCopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-63
Create a FlashCopy Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-64
Select a Source Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-65
ESS Copy Services CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-66
DSCLI Copy Services Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-67
Make a FlashCopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-68
List Established FlashCopies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-69
Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-71
Unit 9. DS Host Attachment Consideration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2
9.1 AIX Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Topics: AIX Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4
DS8000 and DS6000 AIX Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5
IBM pSeries and RS/6000 Servers - AIX (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6
IBM pSeries and RS/6000 Servers - AIX (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . .9-7
Checking AIX Code Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-8
Remove 2105 Fileset (1 of 9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9
Student Notebook
V3.1.0.1
TOC
Copyright IBM Corp. 2005 Contents xv
Remove 2105 Fileset (2 of 9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
FileSet and MP SDD Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
MP SDD Installation (1 of 7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Discover WWN of FC HBAs (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
Now You Go to the DS6000 (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33
Host Attachment (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
LUN Creation (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
LUN Creation (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
On AIX Server After CFGMGR - No Connection to the Switch . . . . . . . . . . . . . . . 9-39
On AIX Server After GFGMGR - Connection to the Switch . . . . . . . . . . . . . . . . . 9-40
On AIX Server After CFGMGR - Connection to the Switch and to the DS6000 . . 9-41
After CFGMGR (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-42
After CFGMGR (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-43
After CFGMGR (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-44
After Creation of VG and FS (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-45
9.2 Windows Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49
Topics: Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-50
Windows Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-51
Intel-Based Servers - Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-52
Windows Disk Management (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
Windows Disk Management (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-54
Student Notebook
xvi DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
Volume Group on DS6000 (1 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-58
Host System on DS6000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-64
Host System - General Host Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-65
Host System - Define Host Ports (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-66
Host System - Define Host Ports (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-67
Host System - Define Host WWPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-68
Host System - Specify Storage Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-69
Host System - Specify Storage Units Parameters . . . . . . . . . . . . . . . . . . . . . . . . .9-70
Host System - Storage Units Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-71
Host System - Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-72
Host System on DS6000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-73
After SDD Install on Windows 2000 (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-74
After SDD Install on Windows 2000 (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-75
After Rescan or Reboot (1 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-76
9.3 Linux Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-83
Topics: Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-84
Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-85
Servers LINUX RH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-86
Firmware Checking (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-87
Checking of Number of LUNs (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-90
Checking of Number of LUNs (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-91
Rebuild the RAM-Disk (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-92
Rebuild the RAM-Disk (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-93
Now You Go to the DS6000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-94
Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-95
Host Attachment (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-96
Host Attachment (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-97
LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-98
MP SDD Installation (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-99
MP SDD Installation (2 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-100
Check LUN Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-103
Determine if Module qla2300 is Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-104
Unload Module qla2300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-105
Student Notebook
V3.1.0.1
TOC
Copyright IBM Corp. 2005 Contents xvii
Reload Module for qla2300 in Order to Discover New LUNs . . . . . . . . . . . . . . . 9-106
The LUNs Are Not Seen by SDD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-107
The LUNs Are Seen by SDD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-108
Add a New Partition to Linux with the LUN from DS6000 (1 of 2) . . . . . . . . . . . . 9-109
Add a New Partition to Linux with the LUN from DS6000 (2 of 2) . . . . . . . . . . . . 9-110
Create a Filesystem (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-111
Create a Filesystem (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-112
Mount the Filesystem /PSSCeduc1 (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-113
Mount the Filesystem /PSSCeduc1 (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-114
9.4 iSeries Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-115
Topics: iSeries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-116
iSeries Servers OS/400 and i5/OS (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-117
iSeries Servers OS/400 and i5/OS (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-118
DS6000 Connection to iSeries Systems: Step by Step Commands . . . . . . . . . . 9-119
iSeries Host Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-120
iSeries Volume Group Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-121
iSeries Volume Group Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-122
iSeries Volume Group Creation: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-123
Volume Group Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-124
Host Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-125
Creation of iSeries Protected Volumes on the DS6000 . . . . . . . . . . . . . . . . . . . 9-126
DS6000 Volumes View from the iSeries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-127
Creation of iSeries Unprotected Volumes on the DS6000 . . . . . . . . . . . . . . . . . 9-128
Volume Group Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-129
DS6000 Volumes Usage in iSeries Disk Pools (1 of 4) . . . . . . . . . . . . . . . . . . . . 9-130
Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-135
Appendix A. DS8000 LPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Appendix B. DS8000 Layout and Cabling Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Appendix C. Checkpoint Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Student Notebook
xviii DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
Student Notebook
Copyright IBM Corp. 2005 Trademarks xix
V3.1.0.1
TMK
Trademarks
The reader should recognize that the following terms, which appear in the content of this
training document, are official trademarks of IBM or other companies:
IBM is a registered trademark of International Business Machines Corporation.
The following are trademarks of International Business Machines Corporation in the United
States, or other countries, or both:
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product and service names may be trademarks or service marks of others.
AIX DB2 eServer
Enterprise Storage Server ESCON FICON
FlashCopy HACMP Hypervisor
i5/OS iSeries OS/400
POWER POWER5 PowerPC
Predictive Failure Analysis pSeries RS/6000
TotalStorage Virtualization Engine xSeries
z/OS zSeries
Student Notebook
xx DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
Student Notebook
Copyright IBM Corp. 2005 Course Description xxi
V3.1.0.1
pref
Course Description
IBM TotalStorage DS8000 and DS6000 Implementation Workshop for
Open Systems
Duration: 3 days
Purpose
To learn the DS6000/DS8000 storage subsystem and its hardware
components and logical structure for Open systems hosts. The
students configure hosts and fixed-block LUNs for the DS8000 storage
subsystem using a DS8000 Storage Manager GUI, and review the
DSCLI interface for scripting configuration functions. Configuration can
be handled online or offline, with import and export capabilities for
configuration files created in the offline configuration simulator. This
course introduces the DS8000 and its hardware components, and
teaches the students the process of configuring the subsystem using
the DS8000 GUI or DSCLI interfaces. The DS6000 differences are
covered in the class, but most of the labs focus on the DS8000 SM
and DSCLI.
Audience
Information Technology (IT) storage administrators responsible for the
implementation of storage resources in a SAN environment with
hardware solutions an operating systems.
Prerequisites
SN70 Introduction to Storage Area Networks
SS05 Introduction to Data Storage Systems
An understanding of zSeries storage and open system operating
systems
Objectives
After completing this course, you should be able to:
Describe the hardware components of the IBM TotalStorage
DS6000/DS8000
Describe the architecture of the IBM TotalStorage DS6000/DS8000
Student Notebook
xxii DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
Describe the hardware installation and cabling of the
DS6000/DS8000
Describe the DSCLI interface installation and setup
Describe the DSCLI interface commands and how to use them
Describe the DS Storage Management GUI interface installation
and setup
Describe the DS Storage Management GUI and how to use the
panels to configure the DS6000 subsystem for Open Systems
hosts
Describe the zSeries Host Attachment considerations for the
DS6000/DS8000
Describe the use of the SM GUI and DSCLI for Copy Services
Describe how to access target volumes in Open Systems hosts
Describe the use of scripts and additional programs for managing
Copy Services
Describe the high-level management interfaces for DS6000
Describe maintenance and support of the DS6000
Describe the customer maintenance and CRU replacement
procedures
Curriculum relationship
This course is part of the Storage Networking curriculum. A basic
understanding of file systems as used in the Open Systems
environment is also a prerequisite. A possible corequisite or follow-on
course is SN82 - Planning and Implementing the SAN Volume
Controller. Other courses in this curriculum group are:
SN70 - Introduction to Storage Area Networks
SS05 - Introduction to Data Storage Systems
SS58 - Planning and Implementing the IBM TotalStorage DS6000
for zSeries
SS59 - Planning and Implementing the IBM TotalStorage DS8000
for zSeries
Student Notebook
Copyright IBM Corp. 2005 Agenda xxiii
V3.1.0.1
pref
Agenda
Day 1
Welcome
Unit 1 - DS8000 Hardware Components and Architecture
Unit 2 - DS8000 Virtualization Concepts
Unit 3 - DS8000 Command Line Interface
Labs: DSCLI Hands-on Labs
Day 2
Unit 4 - DS6000 Hardware Architecture
Unit 5 - DS8000 Hardware Management Console
Unit 6 - DS8000 Storage Manager GUI
Labs: DS Storage Manager GUI Hands-on Labs
Day 3
Unit 7 - DS8000 and DS6000 Performance, TPC and Productivity Data
Center Utility
Unit 8 - DS Copy Services
Unit 9 - DS Host Attachment Consideration
AIX, Windows, Linux, iSeries
Optional Lab: GUI and DSCLI and Q and A
Student Notebook
xxiv DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
Student Notebook
Copyright IBM Corp. 2005 Unit 1. DS8000 Hardware Components and Architecture 1-1
V3.1.0.1
Uempty
Unit 1. DS8000 Hardware Components and
Architecture
What This Unit Is About
The DS8000 storage subsystem is the next generation of storage and
provides RAID-5 or RAID-10 storage arrays attached to a scalable
state-of-the-art processor with variable cache memory and persistent
fast-write cache. Power5 1.9 GHz processors process instructions and
move data through the subsystem at almost six times the rate of the
current ESS storage subsystems. The user can configure the storage
subsystem using a GUI-based interface or a DSCLI interface, and
configuration can be handled online or offline, with import and export
capabilities for configuration files created in the offline configuration
simulator. This unit introduces the DS8000 and its hardware
components and architecture. We look at the different models and
expansion units, and overview the features and components of the
subsystems.
What You Should Be Able to Do
After completing this unit, you should be able to:
Describe the IBM DS8000 highlights
Describe the IBM DS8000 hardware components
Describe the IBM DS8000 architecture
Describe the IBM DS8000 Sequential Prefetching in Adaptive
Replacement Cache (SARC) management
Describe the IBM DS8000 RAS features
Describe the IBM DS8000 layout and cabling rules
References
SG24-6452 IBM TotalStorage DS8000 Series Architecture and
Concepts
SC24-7623 IBM TotalStorage: DS8000 users Guide
GC26-0495 IBM TotalStorage DS8000 Introduction and Planning
Guide
SY27-7641 IBM TotalStorage DS8000 Installation Guide
Student Notebook
1-2 DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
SC26-7628 IBM TotalStorage DS8000 Host Attachment Guide
SC26-xxxx IBM TotalStorage DS8000 Command Line User's
Guide
Http://www.storage.ibm.com/ess
http://www.snia.org
Storage Network Industry Association (SNIA)
http://www.fibrechannel.org
Fibre Channel Industry Association (FCIA)
http://www.t11.org
Technical Committee T11 for device interface of
NCITS (National Committee for Information
Technology Standards)
Student Notebook
V3.1.0.1
Uempty
Figure 1-1. Unit Objectives SS481.0
Notes:
Copyright IBM Corporation 2005
Unit Objectives
Describe the IBM DS8000 SARC cache management
Student Notebook
Student Notebook
V3.1.0.1
Uempty 1.1 DS8000 Highlights
Student Notebook
Figure 1-2. Topic: DS8000 Highlights SS481.0
Notes:
Topic: DS8000 Highlights
DS8000 Highlights
DS8000 Hardware Components
DS8000 Architecture
DS8000 Cache Management
DS8000 RAS Features
Student Notebook
V3.1.0.1
Uempty
Figure 1-3. DS8000 Series Models (2107) SS481.0
Notes:
The DS8000 storage subsystem is the next generation of storage, and provides RAID-5 or
RAID-10 storage arrays attached to a scalable state-of-the art Power 5 processors with
variable cache memory and persistent fast-write cache. Power5 1.9 Ghz processors
process instructions, and move data through the subsystem at almost six times the rate of
the current ESS storage subsystems. The user can configure the storage subsystem using
a GUI-based interface or a CLI interface, and configuration can be handled online or offline,
with import and export capabilities for configuration files created in the offline configuration
simulator. This unit introduces the DS8000 and its hardware components and architecture.
We look at the different models and expansion units, and overview the features and
components of the subsystems.
DS8000 Series Models (2107)
Are:
High Performance
High-capacity series of disk storage
Designed to support continuous operations
Redundancy
Hot replacement / updates
Uses IBM POWER5 server technology
That is integrated with the IBM Virtualization Engine technology
Consist of
Storage unit
One or two (recommended) Management Consoles (MC)
Graphic User Interface (GUI) or Command Line Interface (CLI)
allows
Performing logical configurations and copy services management
functions
For high-availability, hardware components are redundant
Student Notebook
Figure 1-4. DS8000 Models SS481.0
Notes:
There are three models of the DS8000 available to customers. The DS8100 model 921
provides a 2-way 1.5 Ghz Power5 SMP processor and disk storage up to 115 TB. It can
address 255 LSSs and 65280 devices, and supports Open Systems LUNs in sizes which
can span over multiple arrays, and 3390 devices ranging in size from a single cylinder up to
65520 cylinders in size. It supports fibre channel attachment to SAN environments and
supports mainframe PAVs, Multiple Allegiance and I/O priority queuing along with all of the
Copy Services functions. The DS8300 provides a 4-way Power5 1.9 Ghz SMP processor
and disk storage up to 192 TB.
DS8000 Models
DS8100 (Model 921)
Processor Complex
Dual
Two-way
Up to one expansion frame
DS8300 (Models 922 and 9A2)
Processor Complex
Dual
Four-way
Up to two expansion frames
Model 9A2 supports two IBM TotalStorage System
Logical Partitions (LPAR) in one storage unit
Expansion frame Model 92E attaches to 921 and 922
Expansion frame Model 9AE attaches to 9A2
Student Notebook
V3.1.0.1
Uempty
Figure 1-5. DS8000 Hardware Overview SS481.0
Notes:
The DS8100 provides a 2-way SMP processor and cache memory from 16 to 128 GB. It
can house from 2 to 16 FC or ESCON adapters providing 8 to 64 2 GB FCP/FICON ports
or 4 to 32 ESCON ports. The base frame, pictured here, can house up to 128 DDMs, and a
single expansion frame can add 256 more DDMs for a total of 384 for the DS8100 model
921 and a Model 92E expansion frame. This provides disk storage up to 115 TB. It can
address 255 LSSs and 65280 devices and supports 3390 devices up to 65520 cylinders in
size. It supports PAVs, Multiple Allegiance and I/O priority queueing along with all the of
Copy Services functions. The DS8300 provides a 4-way SMP processor, and can house
from 2 to 32 FC or ESCON adapters providing 8 to 128 2 Gb FCP/FICON ports or 4 to 64
ESCON ports. The base frame, pictured here, can house up to 128 DDMs and two 92E
expansion frames can add 512 more DDMs for a total of 640 for the DS8300 model 922,
and two Model 92E expansion frames providing disk storage up to 192 TB.
2-Way (Model 8100)
Two dual processor servers
Up to 128 GB Cache
8 to 64 2 Gb FC/FICON 4 to 32 ESCON ports
16 to 384 HDD
Intermixable 73 GB 15,000 rpm, 146/300 GB 10,000 rpm
Physical capacity from 1.1 TB up to 115 TB
(384 x 300 GB DDMs)
4-Way (Model 8300)
Two four processor servers
Up to 256 GB Cache
8 to 128 2 Gb FC/FICON 4 to 64 ESCON ports
16 to 640 HDD
Intermixable 73 GB 15,000 rpm, 146/300 GB 10,000 rpm
Physical capacity from 1.1 TB up to 192 TB
(640 x 300 GB DDMs)
DS8000 Hardware Overview
Student Notebook
Figure 1-6. Interfaces to DS8000 (1 of 2) SS481.0
Notes:
The interfaces used to monitor and configure the DS8000 consist of a Web-based GUI and
a command-line interface. The DS8000 Storage Manager can be used either in Real-time
(online) or Simulated (offline) mode. Either mode is used to manipulate the storage
configuration process for a DS8000, defining CKD or fixed block (FB) storage, or it may be
used to modify an existing configuration.
The Simulated Manager which can preconfigure new configurations or modify existing
configurations, is to be exported to the DS8000 at a later time. For example, the Simulated
Manager could be used to execute or modify changes at an off-peak hour. Normally, a user
would access either Real-time or Simulated interfaces through the DS8000, Storage
Hardware Management Console (S-HMC), which is an integrated component of the
DS8000 base frame. However, the DS8000 Storage Manager can be installed on a user
workstation and used in a no-attach offline mode using the simulated Storage Manager. In
this way, users can prepare configurations to download to the DS8000 or just use the
simulated mode SM to learn about the GUI interface and become familiar with its operation.
Interfaces to DS8000 (1 of 2)
IBM TotalStorage DS Storage Manager (DS-SM: Web based)
Program Interface to perform logical configurations and copy services
management functions
Installed via GUI (graphical mode) or as an unattended (silent mode)
Accessed through Web browser
Offers:
Simulated Configuration (offline)
Create / Modify / Save logical config when disconnected
Apply them to a network attached storage unit
Real-time Configuration (online)
Logical configuration and Copy Services to a network attached storage unit
Both
DS command-line interface (CLI: Script based)
OPEN hosts invoke and manage FlashCopy, Metro and Global Mirror
functions
Batch processes and scripts
Check storage unit configuration and perform specific application functions
For example:
Check and verify storage unit configuration
Check current copy services config used by storage unit
Create new logical storage and copy-services config settings
Modify / delete logical storage and copy-services config settings
Student Notebook
V3.1.0.1
Uempty
The IBM TotalStorage DS Command-Line Interface (the DS CLI) is a software package that
allows open systems hosts to invoke and manage Copy Services functions as well as to
configure and manage all storage units in a storage complex. The DS CLI is a full-function
command set.
Student Notebook
Figure 1-7. Interfaces to DS8000 (2 of 2) SS481.0
Notes:
A common Application Programming Interface is also provided for use with storage
resource management program such as SRM or TPC.
Interfaces to DS8000 (2 of 2)
DS Open application programming interface (API)
Nonproprietary storage management client application supporting
Routine LUN management activities (creation, mapping, masking)
Creation / Deletion RAID5 and RAID10 volume spaces
Copy services functions: FlashCopy, PPRC
Helps to integrate configuration management support into existing
storage resource management (SRM) applications
Enables automation of configuration management through
customer-written applications
Complements the use of Web-based DS-SM and script-based DS-CLI
Implemented through IBM TotalStorage Common Information Model
(CIM) Agent
Middleware application providing CIM-compliant interface
DS Open API uses CIM technology to manage proprietary devices as
open system devices through storage management applications
DS Open API allows these applications to communicate with a storage
unit
DS API used by TPC for Disk
Student Notebook
V3.1.0.1
Uempty
Figure 1-8. IBM TotalStorage Management Console SS481.0
Notes:
The S-HMC is used to perform configuration, management, and maintenance activities on
the DS8000. It can be ordered to be located either physically inside the base frame or
externally for mounting in a customer-supplied rack.
If the S-HMC is not operational then it is not possible to perform maintenance, power the
DS8000 up or down, or perform Copy Services tasks, such as the establishment of
FlashCopies. It is thus recommended to order two management consoles to act as a
redundant pair.
IBM TotalStorage Management Console
Focal point for
Configuration, Copy Services, Maintenance
Dedicated workstation installed inside DS8000
Is the eServer Power5 HMC and can be also called S-HMC on
DS8000
Automatic monitoring the state of system
Notify user and IBM when service is required (Call Home)
Can also be connected to network
Enabling centralized management through CLI or API scenarios
External management console (optional)
For redundancy with high availability
Called SMC on DS6000
Student Notebook
Figure 1-9. DS8000 Data Flow SS481.0
Notes:
Redundancy in the DS8000 servers allows data to be written into cache and persistent
memory of the two servers so that I/Os can be completed and hosts can be released prior
to destaging data to disk arrays. This improves write performance and also provides
redundancy for failover conditions.
DS8000 Data Flow
The normal flow of data for a
write is the following :
1. Data is written to cache
memory in the owning
server.
2. Data is written to NVS
memory of the alternate
server.
3. The write is reported to the
attached host as having
been completed.
4. The write is destaged from
the cache memory to
disk.
5. The write is then discarded
from the NVS memory of
the alternate server.
Server 0 Server 1
Cache
memory
for even
LSSs
NVS
for odd
LSSs
NVS
for even
LSSs
Cache
memory
for odd
LSSs
Student Notebook
V3.1.0.1
Uempty
Figure 1-10. Host Connectivity: IBM Subsystem Device Driver SS481.0
Notes:
For Open Systems hosts a multipath driver is provided for use in load balancing and
multipath operation which is fairly common today for disk access. SDD version 1.6.x.x. is
provided for the DS6000 and DS8000, and supports most of the common OSs. It can be
installed with RDAC for the DS4000 servers as long as each product manages separate
HBAs. If third-party multipath drivers or volume managers are used, they supersede the
need to install the SDD package.
Host Connectivity:
IBM Subsystem Device Driver
SDD provides the following functions:
Enhanced data availability
Automatic path failover
Dynamic I/O load-balancing across multiple
paths
Path selection policies for the host system
Concurrent download of licensed machine code
With DS6000 and DS8000, SDD is supported on
the following OS:
Windows
Netware
AIX
HP-UX
SUN Solaris
Linux
Can coexist with RDAC (DS4000 multipath driver)
on most OS as long they manage separate HBAs
Cannot be used with most other multipath drivers
(that is, Vertias, PV-Links, Powerpath)
DS6000
Server
Device Driver
IBM Subsystem
Device Driver
SCSI
Student Notebook
Figure 1-11. DS8000 Enhancements At a Glance SS481.0
Notes:
Looking at the DS8000 at a glance, there are many reasons why this product is state of the
art in disk storage. The new hardware and internal components provide an increase every
area of the subsystem making it one of the fastest storage processing subsystems
available. Increased logical addressing provides 16 times the number of available
addresses, and increased connectivity allows connections to many host environments and
large SAN installations. The new GUI and CLI interfaces are some of the most robust and
functional interfaces in the market, and have adopted a standard look and feel to other IBM
TotalStorage products. Major enhancements in the volume administration from the ESS
make the DS8000 more flexible and easier to configure than any other storage subsystem.
All of these things improve the Total Cost of Ownership or TCO to the customer.
DS8000 Enhancements At a Glance
Hardware new everything
Processors, adapters, internal paths,
frames
Increased management flexibility via storage
system LPARS
Enhanced Performance
Faster or more of almost everything
New patent pending cache algorithms
Extended logical device addressing
Up to 256 logical subsystems (LSS) with
virtualized assignment of physical capacity to
LSSs
Up to 65,280 logical volumes
Extended Connectivity
Up to 128 host ports (FC or Ficon)
Or 64 ESCON host ports
Up to 510 FCP logins per port and 8,192 per
storage LPAR
Up to 512 FICON logical paths per logical
control unit image and 128,000 per storage
facility image
Up to 256 FICON logical path groups per
control unit image
Up to 2,048 FICON logical paths per port
Improved volume management
Nondisruptive volume add and delete
Up to 65,280 volumes assigned to up to 256
Logical Subsystems (LSSs); an array can
contain volumes for multiple LSSs
Larger LUNs (over 2 TB)
64,000 cylinder (55.6 GB) zSeries
volumes
Improved Administration
Online and offline configuration capability
using a Web-based graphical user interface
(GUI)
Ease-of-use improvements (compared to the
ESS Specialist)
Command-line interface (CLI) supports
control of copy services without
dependencies on GUI-created tasks
Even more attractive Total Cost of
Ownership
More flexible feature licensing
Four-year standard warranty period
Larger capacity volumes supported
Increased opportunities for consolidation
Student Notebook
V3.1.0.1
Uempty
Figure 1-12. DS8000 Overview SS481.0
Notes:
Here is a chart which maps the features of the DS8000 according to the various models
that are available.
2-way
(Base Frame
Only)
2-way
+
Expansion
Frame
4-way or LPAR
(Base Frame
Only)
4-way or LPAR
+
Expansion Frame
4-way or LPAR
+
Two Expansion
Frames
Processor
- pSeries Squadron Power5
2-way
1.5 GHz
2-way
1.5 GHz
4-way
1.9 GHz
4-way
1.9 GHz
4-way
1.9 GHz
Cache 16 to 128 GB 16 to 128 GB 32 to 256 GB 32 to 256 GB 32 to 256 GB
Expansion Rack Yes (1) -- Yes (1 or 2) -- --
Host Adapters
- per HA: 4-port FC / FICON (2 Gb)
- per HA: 2-port ESCON
2 to 16 (example,
8 to 64 FC /
FICON ports)
2 to 16 2 to 16 2 to 32 2 to 32
Device Adapters
2 to 8 (example,
1-4 FCALs)
2 to 8 2 to 8 2 to 16 2 to 16
Drives
- 73 GB (15 K rpm)
- 146 GB (10 K rpm)
- 300 GB (10 K rpm)
16 to 128
(Increments of
16)
16 to 384
(Increments of 16)
16 to 128
(Increments of
16)
16 to 384
(Increments of 16)
16 to 640
(Increments of 16)
Physical Capacity 1.1 to 38.4 TB 1.1 to 115 TB 1.1 to 38.4 TB 1.1 to 115 TB 1.1 to 192 TB
Power Three-Phase Three-Phase Three-Phase Three-Phase Three-Phase
Dimensions
-Height x Width x Depth
- Footprint
76 x 33.25 x 43 in
9.93 sq. ft.
76 x 66.5 x 43 in
19.86 sq. ft.
76 x 33.25 x 43 in
9.93 sq. ft.
76 x 66.5 x 43 in
19.86 sq. ft.
76 x 99.75 x 43 in
29.79 sq. ft.
DS8000 Overview
Student Notebook
Student Notebook
V3.1.0.1
Uempty 1.2 DS8000 Hardware Components
Student Notebook
Figure 1-13. Topic: DS8000 Hardware Components SS481.0
Notes:
Topic: DS8000 Hardware Components
DS8000 Highlights
DS8000 Architecture
DS8000 RAS Features
Student Notebook
V3.1.0.1
Uempty
Figure 1-14. DS8000: Primary Frame Topology SS481.0
Notes:
Here are the front view and the back view of the DS8000 Model 921 or 922 primary frame
or base frame. The frame houses the processors, power supplies, host and device
adapters. It also provides a 19-inch rack for up to eight disk enclosures or up to 128 DDMs.
Additional DDMs can be added via expansion frames as well as additional adapters. The
processor complex is a pair of Power5 p570 servers, and can be 2-way or 4-way
processors. One of the primary advantages of the p5 is the LPAR capability using the
4-way processor. The DS8000 can be split into two distinct logical partitions. One of the
2-way processors and half the device and host adapters can be physically allocated to
each LPAR. This unique design allows two completely separate versions of LIC to be
loaded in each LPAR.
DS8000: Primary Frame Topology
Front Rear
Dense HDD Packaging
16 drives per pack
Dual FC-AL Loop Switches
Point to Point Isolation
Two Simultaneous
Operations per loop
Storage Hardware
Maintenance Console
Processor Complex
IBM eServer p5 570
Dual 2-way or Dual 4-way
4 I/O Enclosure Bays
Each bay supports
4 Host Adapters and
2 Device Adapters
Standard 19in rack
mounting space
Redundant
Power
BBU:
Battery
Backup
Units
Host Adapter
4 FCP/FICON Ports
or 2 ESCON Ports
Device Adapter
4 FC-AL Ports
Student Notebook
Figure 1-15. DS8000 Terminology SS481.0
Notes:
The group of DS8000 Storage servers it manages is called a Storage Complex and each
frame is called a Storage Unit. Each Storage Unit has two pSeries p5 570 servers, and this
is called the processor complex. When using the Storage Unit in LPAR mode, the
resources of the Storage Unit can be divided into two logical partitions called LPARs. A
Storage Server is the software that is used to control the LPAR. The two LPARs create a
Storage Image and each Storage Server has a Storage Image ID associated with it.
DS8000 Terminology
Storage Complex
A group of DS8000s managed by a
single Management Console
Storage Unit
A single DS8000 including expansion frames
Processor Complex
One P5-570 pSeries server
Two processor complexes form a
redundant pair
Divided in one LPAR (models 921 or 922) or
two LPARs (model 9A2)
Storage Server
The Software that uses an LPAR
Has access to a percentage of resources available on the Processor Complex for the
LPAR
At GA, this percentage is 50% (model 9A2) or 100 % (models 921 or 922)
Storage Facility Image (SFI)
Union of two LPARs, one from each Processor Complex
Each LPAR hosts one Storage Server
Processor
complex 0
Processor
complex 1
Storage
facility
image 1
Server 0
Storage
facility
image 2
Server 0
Server 1
Server 1
LPARs
LPARs
Student Notebook
V3.1.0.1
Uempty
Figure 1-16. DS8000 Hardware Components Detail SS481.0
Notes:
The RIO-G is the backbone of the DS and connects the storage servers to the hosts and to
the disk enclosures via device adapter pairs. DA pairs are used from two different RIO-G
bays to form a loop between the servers and the device adapters which then connect to the
disk enclosures.
DS8000 Hardware Components Detail
HA
DA
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Module
RIO-G Module
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Interconnect
I/O enclosure
4 HAs
2 DAs
2 Gbps Fibre Channel ports
RIO-G Module
POWER5 2-way SMP
Processor
Memory
Processor
L1,2
Memory
L3
Memory
L1,2
Memory
POWER5 2-way SMP
Memory
L3
Memory
RIO-G Module
Processor
Processor
L1,2
Memory
L1,2
Memory
Server 1
Server 0
Processor Complex
Processor Complex
Student Notebook
Figure 1-17. DS8000 Processor Complex SS481.0
Notes:
The processor complex is connected to the storage using a high-speed I/O bay called the
RIO-G. It contains host adapters and device adapters.
DS8000 Processor Complex
HA
DA
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Module
RIO-G Module
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Interconnect
I/O enclosure
4 HAs
2 DAs
RIO-G Module
POWER5 2-way SMP
Processor
Memory
Processor
L1,2
Memory
L3
Memory
L1,2
Memory
POWER5 2-way SMP
Memory
L3
Memory
RIO-G Module
Processor
Processor
L1,2
Memory
L1,2
Memory
Server 1
Server 0
Processor Complex
Processor Complex
Student Notebook
V3.1.0.1
Uempty
Figure 1-18. DS8000 Processor Complex: Power5 Server SS481.0
Notes:
For storage processing we can get by with 2-way and 4-way. In todays data processing
environments there is no need to go further because nobody requires that kind of speed,
however, as the need arises in the future, IBM is well positioned to provide a processor to
meet the requirements.
DS8000 Processor Complex : Power5 Server
Processor
Adapter Adapter
Adapter Adapter
To host servers
S
t
o
r
a
g
e

s
e
r
v
e
r
RIO-G Module
POWER5 2-way SMP
Processor
Processor
L1,2
Memory
L1,2
Memory
Memory
L3
Memory
Processor
The CEC enclosures in the Model 921 each have one processor card (2-way)
The CEC enclosures in the Model 922 and 9A2 each have two processor cards
(4-Way)
CEC: Computer Electronic Complex
The CEC Enclosures contain components such as the processor cards, cache memory,
and the CEC hard drives
Student Notebook
Figure 1-19. DS8000 Processor Complex PC SS481.0
Notes:
The Power5 processors in the Model 921 are a 2-way 1.5 Ghz compared to a 4-way
600Mhz in an ESS-800. The 922 uses a 1.9 Ghz 4-way processor and provides 6x
performance of an ESS-800
The 4-way processor in a 922 can be split at the factory and divided into two LPARs,
creating a Model 9A2 and physically splitting the resources of the DS8300 into two logical
partitions. Each partition has access to a pair of 2-way processors, two of the RIO-G bays
and half the host and device adapters. The disk enclosures are divided between the
LPARs. As far as we know this LPAR split is only done at the factory, and is not available as
a field upgrade yet.
DS8000 Processor Complex PC
IBM eServer pSeries POWER5 Servers
2-way 1.5 GHz (3X an ESS 800)
4-way 1.9 GHz (6X an ESS 800)
The POWER5 processor supports logical partitioning
The p5 hardware and Hypervisor manage the real-to-virtual
memory mapping to provide robust isolation between LPARs
IBM has been doing LPARs for 20 years in mainframes and 3 years
in pSeries
At GA LPARs are split 50-50, so:
A 4-way has two processors to one LPAR and two processors to
the other LPAR
Post GA, 25-75 possible
LPARs only possible in the 4-way P5s (RIO-G can't be shared in
2-way)
Cache memory from 16 GB-256 GB
Persistent Memory 1 GB to 8 GB dependent on cache size
Battery backed for backup to internal disk (4 GB per server)
Student Notebook
V3.1.0.1
Uempty
Figure 1-20. DS8000 Processor Complex SS481.0
Notes:
The Power5 processor is pictured above. The Model 921 has the RIO-G ports on the
motherboard, but lacks the second set which are provided in the 922 and 9A2 via a RIO-G
card which is installed in one of the PCI-X slots. The processor complex also houses disks
for the AIX kernel and storage for backing the persistent memory for fast write cache.
DS8000 Processor Complex
power supply 2
power supply 1
power supply 1 power supply 2
PCI-X slots
RIO-G ports
PCI-X adapters
with blind swap
mechanism
RIO-G ports
processor cards
disk drive bays
DVD rom drives
operator panel
Front View
Rear view
Student Notebook
Figure 1-21. DS8000 Persistent Memory SS481.0
Notes:
Persistent memory is the cache memory allocated for fast write operations and, like NVS in
the ESS, it is protected from failures and backed by disk and battery power in case of
failures in the processor complex or cache. The batteries in the DS8000 hold up the disks
in the CEC until the persistent memory can be offloaded to them in the event of a power
failure or cache problem.
DS8000 Persistent Memory
The 2107 does not use NVS cards, NVS batteries, or NVS battery
chargers
Data that would have been stored in the 2105 NVS cards resides in
the 2107 CEC cache memory
A part of the system cache is configured to function as NVS
storage
If the 2107 has pinned data in cache, it is written to an extra set of
four disk drives located in each of the CEC enclosures
Six disk drives total in each CEC:
2 for LIC (LVM Mirrored AIX 5.2 + DS8000 code)
4 for pinned data and other CEC functions
During the recovery process the pinned data can be restored from
the extra set of CEC disk drives just like it would have been from the
NVS cards on the ESS 800
Student Notebook
V3.1.0.1
Uempty
Figure 1-22. DS8000 I/O Enclosure SS481.0
Notes:
All base models contain I/O enclosures and adapters. The I/O enclosures hold the
adapters and provide connectivity between the adapters and the processors. Device
adapters and host adapters are installed in the I/O enclosure. Each I/O enclosure has six
slots. Each slot supports PCI-X adapters running at 64 bit, 133 Mhz. Slots 3 and 6 are used
for the device adapters. The remaining slots are available to install up to four host adapters
per I/O enclosure.
DS8000 I/O Enclosure
HA
DA
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Module
RIO-G Module
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Interconnect
I/O enclosure
4 HAs
2 DAs
RIO-G Module
POWER5 2-way SMP
Processor
Memory
Processor
L1,2
Memory
L3
Memory
L1,2
Memory
POWER5 2-way SMP
Memory
L3
Memory
RIO-G Module
Processor
Processor
L1,2
Memory
L1,2
Memory
Server 1
Server 0
Processor Complex
Processor Complex
Student Notebook
Figure 1-23. RIO-G and I/O Enclosures SS481.0
Notes:
The I/O enclosures hold the adapters and provide connectivity between the adapters and
the cache memory over the RIO-G internal bus.
Each adapter has its own PowerPC processor which handles I/O operations independently
from the CEC. Host adapters provide FCP connection to attached servers or FICON
attached mainframe hosts. Device adapters provide connection to the disk enclosures and
the CEC. Internally, the RIO-G bay is connected to the CEC on a high-speed internal bus.
SPCN ports access the RIO-G bay for control and monitoring. The device adapter in each
RIO-G is one half of a DA pair, and is connected through the disk enclosures to the other
DA to form the FC-AL loop.
RIO-G and I/O Enclosures
Also called I/O Drawers
6 PCI-X slots : 3,3 V, 133 MHz blind swap
Hot-plug:
Four port Host Adapters cards with four
ports each:
FCP or FICON adapters ports
Two Device Adapter cards with four ports
each:
4 FC-AL ports per card
2 FC-AL loops per card
Access to cache via RIO-G internal Bus
Each adapter has it's own PowerPC processor
Owned by processors in LPAR
SPCN : System Power Control Network
Used to control and monitor the status of the
power and cooling within the I/O Enclosure.
Cabled as a loop between the different I/O
Enclosures
Student Notebook
V3.1.0.1
Uempty
Figure 1-24. DS8000 RIO-G Port: Layout Example SS481.0
Notes:
Each RIO-G port from the CEC connects to the I/O enclosure, and it connects to a second
I/O enclosure, and then to the other CEC and back again. The 921 has one loop available,
and the 922 and 9A2 have two loops available.
DS8000 RIO-G Port: Layout Example
Up to 4 I/O Enclosures in the
same RIO-G loop
Up to 20 I/O Enclosures to
the P5-570 system.
Processor
Complex 0
RIO-G ports
Processor
Complex 1
RIO-G ports
I/O enclosure I/O enclosure
Loop 0
Loop 1
Up to four I/O enclosures
in the same RIO-G loop
Up to 20 I/O enclosures to
the P5-570 system.
Each RIO-G port can operate at 1 GHz in bidirectional mode and is capable of passing data in
each direction on each cycle of the port. Maximum data rate per I/O enclosure: 4 GB/s.
It is designed as a high-performance self-healing interconnect. The p5-570 provides two external
RIO-G ports, and an adapter card adds two more. Two ports on each processor complex form a
loop.
Figure shows an illustration of how the RIO-G cabling is laid out in a DS8000 that has eight I/O
drawers. This would only occur if an expansion frame were installed. The DS8000 RIO-G cabling
varies based on the model.
Student Notebook
Figure 1-25. Bus Interconnect Performance Comparison SS481.0
Notes:
The ESS employed a Common Parts Interconnect bus architecture which was a switch
fabric that connected the HA to the processor bays. The ESS has one 500 Mhz link that
can provide around 550 MB/sec bandwidth to the servers at maximum throughput. The
RIO-G has no CPI switch, but uses 2 133 Mhz 64bit PCI-X buses and 4 -1 Ghz links to the
CECs and provides 2000 MB/second per loop. Each 2-way can connect to a RIO-G loop
and provide three times the performance and bandwidth of the ESS-800. With a 922 and
4-way processors the DS8300 Model 922 can provide six times the bandwidth of the
ESS-800.
Bus Interconnect Performance Comparison
Model 800 CPI/RIO
(4) host bay, (4) host adapters
per bay, (8) CPI buses
CPI bus 32-bit/66 MHz,
connects to EADS
(3) EADS per cluster share (2)
66 MHz/64-bit PHBs PCI
buses
Connects to RIO bus (1 bi-di
link in use per cluster @ 500
MHz 1-byte wide)
Max effective bandwidth: 550
MB/SEC for box (275
MB/SEC bi-di on each RIO
bus in each cluster)
DS8000 RIO-G
(4) I/O Enclosures per RIO-G
loop, (6) host/device adapters
per drawer
No CPI
(2) EADS-X per I/O Enclosure
with (2) 64-bit/133 MHz PHBs
PCI-X buses
Connects to RIO-G bus (4
bi-di links per RIO-G loop @
1 GHz 1-byte wide)
Max effective bandwidth:
2000 MB/SEC per RIO-G
loop, 1 loop per 2-way SMP
(500 MB/SEC bi-di on each of
the 4 RIO-G links)
Student Notebook
V3.1.0.1
Uempty
Figure 1-26. DS8000 Host Adapters HA SS481.0
Notes:
The DS8000 supports two types of host adapters: ESCON and Fibre Channel/FICON. It
does not support SCSI adapters.
The ESCON adapter in the DS8000 is a dual ported host adapter for connection to older
zSeries hosts that do not support FICON. The ports on the ESCON card use the MT-RJ
type connector.
DS8000 Host Adapters HA
HA
DA
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Module
RIO-G Module
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Interconnect
I/O enclosure
4 HAs
2 DAs
RIO-G Module
POWER5 2-way SMP
Processor
Memory
Processor
L1,2
Memory
L3
Memory
L1,2
Memory
POWER5 2-way SMP
Memory
L3
Memory
RIO-G Module
Processor
Processor
L1,2
Memory
L1,2
Memory
Server 1
Server 0
Processor Complex
Processor Complex
Student Notebook
Figure 1-27. Host Adapter with Four Fibre Channel Ports SS481.0
Notes:
Each DS8000 Fibre Channel card offers four 2 Gbps Fibre Channel ports. The cable
connector required to attach to this card is an LC type. Each port independently
auto-negotiates to either 2 Gbps or 1 Gbps link speed. Each of the four ports on one
DS8000 adapter can also independently be either Fibre Channel protocol (FCP) or FICON,
though the ports are initially defined as switched point to point FCP.
Each HA has four ports and each port can address 16384 devices so the card can address
4 X 16384 or 65280 devices which is the maximum a DS8000 can address.
The DS8100 has 4 RIO-G bays with 4 HA cards each or 16 HAs, the 922 has 8 RIO-G bays
X 4 cards each or 32 HAs.
Host Adapter with Four Fibre Channel Ports
Processor
Adapter Adapter
Adapter Adapter
To host servers
S
t
o
r
a
g
e

s
e
r
v
e
r Memory
PowerPC
Fibre Channel
Protocol Proc
HA
Fibre Channel
Protocol Proc
Processor
Configured as FCP or FICON each
More FICON logical paths:
ESS (1024) versus DS8000(2048)
One FICON channel addresses
16384 devices
One HA card covers all the 65,280
devices that an DS8000 supports
Up to 16 HA into a DS8100 or 32
HA into a DS8300
16 FICON channel ports to each
single device
Current zSeries Channel
subsystems limited to eight
channel paths per device
Front End of
128 ports for DS8300 (8 times
ESS)
64 ports for DS8100 (4 times
ESS)
Student Notebook
V3.1.0.1
Uempty
Figure 1-28. DS8000 FCP/FICON Host Adapters: HA SS481.0
Notes:
The definition of the I/O ports is done when the host connection is defined and a WWPN is
assigned to the card. The WWPN is not detected from the SAN like it was from the ESS, so
these must be entered by hand and errors could occur here.
DS8000 FCP/FICON Host Adapters: HA
Four LC 2 Gb FC ports
Auto-negotiates to 1 Gbps or 2 Gbps
Each port independently auto-negotiates to either 2 Gbps or 1
Gbps link speed.
Can be independently configured to FCP or FICON protocols
The personality of the port is changeable via the DS Storage
Management tools (GUI or CLI).
Ports cannot operate as FCP and FICON simultaneously
FCP port can be long wave or short wave
Short wave ports support a distance of 300 m (non-repeated)
Long wave ports support a distance of 10 km (non-repeated)
Student Notebook
Figure 1-29. DS8000 FICON/FCP Host Adapter SS481.0
Notes:
The card itself is PCI-X 64 Bit 133 MHz. The card is driven by a new high function, high
performance ASIC. To ensure maximum data integrity, it supports metadata creation and
checking. Each Fibre Channel port supports a maximum of 509 host login IDs. This allows
for the creation of very large storage area networks (SANs).
QDR
QDR
PPC
750GX
Flash
Buffer
Data Protection
Data Mover
ASIC
Protocol
Chipset
Processor
Data Mover
1 GHz
PCI-X 64-bit 133 MHz
Fibre Channel
Protocol
Engine
Fibre Channel
Protocol
Engine
Four 2 Gbps Fibre Channel Ports
New High Function/High Performance
ASIC
Metadata Creation/Checking
Configured at port level Fibre or
FICON
SW or LW
DS8000 FICON/FCP Host Adapter
Student Notebook
V3.1.0.1
Uempty
Figure 1-30. DS8000 Device Adapter DA SS481.0
Notes:
Each DS8000 device adapter (DA) card offers four 2 Gbps FC-AL ports. These ports are
used to connect the processor complexes to the disk enclosures. The adapter is
responsible for managing, monitoring, and rebuilding the RAID arrays. The adapter
provides remarkable performance thanks to a new high-function/high-performance ASIC.
DS8000 Device Adapter DA
HA
DA
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Module
RIO-G Module
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Interconnect
I/O enclosure
4 HAs
2 DAs
RIO-G Module
POWER5 2-way SMP
Processor
Memory
Processor
L1,2
Memory
L3
Memory
L1,2
Memory
POWER5 2-way SMP
Memory
L3
Memory
RIO-G Module
Processor
Processor
L1,2
Memory
L1,2
Memory
Server 1
Server 0
Processor Complex
Processor Complex
Student Notebook
Figure 1-31. Fibre Channel Device Adapters with Two Gbps Ports SS481.0
Notes:
Each DS8000 device adapter provide the RAID support for disk enclosures to support
RAID 5 and RAID 10. The DAs have there own processors and much higher bandwidth
than in the ESS. We also use AAL (Array Across Loops) to provide higher redundancy and
throughput.
Fibre Channel Device
Adapters with Two Gbps Ports
DA perform RAID Logic
Offload Servers of that workload
Each port has up to five times the
throughput of a previous SSA
based DA ports
DS8000 AAL (Array Across
Loops) :
RAID-5 or RAID-10 eight DDMs
spread over two loops
Processor
Adapter Adapter
Adapter Adapter
To host servers
S
t
o
r
a
g
e
s
e
r
v
e
r
Memory PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
DA
Processor
Student Notebook
V3.1.0.1
Uempty
Figure 1-32. DS8000 Device Adapters SS481.0
Notes:
The DS8000 device adapters operate in a FC-AL loop connected to a switched disk
enclosure. This provides a point-to-point connection for each DDM which are dual-ported
drives.
DS8000 Device Adapters
FC-AL Switched Fabric
FC-AL dual ported drives are connected to FC switch in the Disk
Enclosure backplane
Two FC-AL loops connect Disk Enclosures to Device Adapters
Array across loops is standard configuration option in DS8000
Two simultaneous I/O ops per FC-AL connection possible.
Switched FC-AL or SBOD (switched bunch of disks) used for
back-end access
Device Adapters are attached to a FC Switch with the enclosure
Four paths to each drive: 2 FC-AL loops X dual port access
Device Adapters support RAID-5 or RAID-10
Student Notebook
Figure 1-33. DS8000 RAID Device Adapter SS481.0
Notes:
The adapter provides remarkable performance thanks to a new high function/high
performance ASIC.
This ASIC is on each DA card and handles RAID functions and I/O requests. Each card
has four FCP ports which connect either one or two loops to the RIO-G bays.
PCI-X 64 Bit 133 MHz
Buffer
RAID -
Data Protection -
Data Mover
ASIC
Protocol
Chipset
Processor
Data Mover
500 MHz
NVRAM SDRAM
PPC
750FX
Bridge
F
i
b
r
e

C
h
a
n
n
e
l

P
r
o
t
o
c
o
l

E
n
g
i
n
e
F
i
b
r
e

C
h
a
n
n
e
l

P
r
o
t
o
c
o
l

E
n
g
i
n
e
Four 2 Gbps Fibre Channel Ports
New High Function/High Performance ASIC
Metadata Checking
DS8000 RAID Device Adapter
Student Notebook
V3.1.0.1
Uempty
Figure 1-34. RAID and Logical Volume Comparison SS481.0
Notes:
Each DS8000 supports RAID 5 or RAID 10 arrays, but in, addition, supports the individual
creation and deletion of logical volumes. This means that now we can delete a single
volume in a DS6000 or DS8000 and not have to re-format the entire array.
RAID and Logical Volume Comparison
Model 800
RAID-5 (7 or 8 DDMs)
RAID-10 (6 or 8 DDMs)
Logical volume on exactly 1
rank
DS8000
RAID-5, RAID-10 (same as ESS
800)
Logical volume segmentation
allows for chunks of volumes to be
spread across several ranks
(Similar to AIX Logical Volume
Manager large granularity striping -
improves IO load across arrays)
Post GA: Homogeneous Multi-array
ranks (similar to LVM small
granularity striping - improves
single stream sequential and IO
load across arrays)
Student Notebook
Figure 1-35. DS8000 Storage Enclosures SS481.0
Notes:
Each DS8000 frame contains either 8 or 16 disk enclosures depending on whether it is a
base or expansion frame. Half of the disk enclosures are accessed from the front of the
frame, and half from the rear. Each DS8000 disk enclosure contains a total of 16 DDMs or
dummy carriers.
DS8000 Storage Enclosures
Enclosure hold 16 DDMs
Dual ported FC-AL DDMs
73, 146, or 300 GB DDMs
10 or 15 K RPM
Drives can be added in groups of
8 drives by DS8000 storage enclosure
Enclosures act as a FC switch
connecting drive using point to point
connections
The picture above depicts four
simultaneous and independent
switched connections, one from
each device adapter port.
Student Notebook
V3.1.0.1
Uempty
Figure 1-36. 16 Drive Disk Enclosure SS481.0
Notes:
Each DS8000 disk enclosure contains a total of 16 DDMs and a controller card to connect
it to the DAs.
16 Drive Disk Enclosure
Backplane
Control card
Disk
Top Half of Disk Enclosure: 8 Disks
in two rows of four disks each
Bottom Half of Disk Enclosure: 8
Disks in two rows of four disks each
Backplane
Control card
Disk
Top Half of Disk Enclosure: 8 Disks
in two rows of four disks each
Bottom Half of Disk Enclosure: 8
Disks in two rows of four disks each
DS8000: Disk enclosures installed in pairs -> one in front & one in back
Student Notebook
Figure 1-37. DS8000 Switched FC-AL Disk Subsystem SS481.0
Notes:
Each DS8000 disk enclosure is a switch which accepts the DDMs and provides a switched
bunch of disks or (SBOD) to the DA which connects to the enclosure using FC-AL protocol.
The switched part of the disk enclosure allows for better fault isolation and diagnostic
information to be gathered, and provides a high-speed connections to the disks using 2 Gb
Fibre Channel technology instead of SSA160.
DS8000 Switched FC-AL Disk Subsystem
Processor
Adapter Adapter
Memory Processor
Adapter Adapter
To host servers
S
t
o
r
a
g
e

s
e
r
v
e
r
oo o
Fibre Channel switch
16 DDM
Processor
Adapter Adapter
Memory Processor
To storage servers
H
o
s
t

s
e
r
v
e
r
Student Notebook
V3.1.0.1
Uempty
Figure 1-38. DS8000 and DS6000 Switched FC-AL/FC-AL SS481.0
Notes:
The disk enclosures operate on a FC-AL loop, and normally that would give the impression
that only one I/O at a time was possible. However, switched FC-AL provides better access
and has faster arbitration since each connection is done as a point-to-point connection.
Since only one disk is present, it wins the arbitration scheme by default, and then can
provide a full 2 Gb/sec. The other benefit over FC-AL is the RAS characteristics for fault
isolation. FC-AL is traditional difficult when it comes to detecting errors on the loop and
which drive is responsible. With switched FC-AL and PtP connection it is relatively simple
to isolate the failure when it occurs since there is only one drive connected per interface.
DS8000 and DS6000 Switched FC-AL/FC-AL
server 0
device
adapter
Fibre channel switch
server 1
device
adapter
Switched connections
FC-AL
Loop supports only one
operation at a time
Arbitration of competition
Intermittent failure issues
Increasing time as number
of devices grows
Switched FC-AL
Drives attached in
point-to-point connection
Faster arbitration
message processing
200 MB/sec external
transfer rate
Improved RAS
Switch detects individual
failures
Intermittent / Permanent
Student Notebook
Figure 1-39. Switched FC-AL Advantages SS481.0
Notes:
So the disk enclosure provides the switch and the switch provides better throughput, better
fault isolation, higher speeds, and better redundancy.
Switched FC-AL Advantages
DS6000 and DS8000 use switched FC-AL technology to link the device adapter (DA) pairs and the
DDMs.
Switched FC-AL uses the standard FC-AL protocol, but the physical implementation is different
The key features of switched FC-AL technology are:
Standard FC-AL communication protocol from DA to DDMs
Direct point to point links are established between DA and DDM :
No arbitration and no performance degradation
Isolation capabilities in case of DDM failures, provides easy problem determination
Predictive failure statistics
Simplified expansion: no cable rerouting required when adding another disk enclosure
The DS8000 architecture employs dual redundant switched FC-AL access to each of the disk
enclosures.
The key benefits of doing this are:
Two independent switched networks to access the disk enclosures
Four access paths to each DDM
Each device adapter port operates independently
Double the bandwidth over traditional FC-AL loop implementations
Each DDM is attached to two separate Fibre Channel switches.
This means that with two device adapters, we have four 2 Gb/sec effective data paths to each disk.
When a connection is made between the device adapter and a disk, the connection is a switched
connection, that uses arbitrated loop protocol.
This means that a mini-loop is created between the device adapter and the disk.
Four simultaneous and independent connections, one from each device adapter port.
Student Notebook
V3.1.0.1
Uempty
Figure 1-40. DS8000: Storage Enclosure and DA Cabling SS481.0
Notes:
Each DS8000 disk enclosure is connected to a DA pair. The disk enclosures are attached
in pairs with one mega-pack placed in front and one in the rear. Each DA pair receives four
disk enclosures before the next DA pair is used. DA pairs are selected in sequence of
installation, which is not numerical in order. DA pair 2 is installed first, then 0, then
depending on the Model either 3,1 for a 921 or 6,4 for a 922. Cabling is also done
differently on LPAR machines Model 9A2 because the RIO-G bays are split between the
LPARs.
DS8000: Storage Enclosure and DA Cabling
o o o
20 port switch
20 port switch
16 DDM
RIO-G Module
RIO-G Module
o o o
20 port switch
20 port switch
16 DDM
DA
RIO-G Interconnect
DA
RIO-G Module
POWER5 2-way SMP
Processor
Memory
Processor
L1,2
Memory
L3
Memory
L1,2
Memory
POWER5 2-way SMP
Memory
L3
Memory
RIO-GModule
Processor
Processor
L1,2
Memory
L1,2
Memory
FC-AL Switched
FC-AL dual ported drives
2 FC-AL Loops
2 I/Os per FC-AL connection
4 paths to each drive
(2 loops x dual port access)
Student Notebook
Figure 1-41. DS8000 Storage Enclosure and DA Cabling SS481.0
Notes:
For a more detailed look at how the switched disk architecture expands in the DS8000 you
should refer to the figure above. It depicts how each DS8000 device adapter connects to
two disk networks called loops. Expansion is achieved by adding enclosures to the
expansion ports of each switch. Each loop can potentially have up to six enclosures, but
this varies depending on machine model and DA pair number. The front enclosures are
those that are physically located at the front of the machine. The rear enclosures are
located at the rear of the machine.
DS8000 Storage Enclosure and DA Cabling
Device Adapter pair
Student Notebook
V3.1.0.1
Uempty 1.3 DS8000 Architecture
Student Notebook
Figure 1-42. Topic: DS8000 Architecture SS481.0
Notes:
Lets take a more detailed look at the architecture of the DS8000.
Topic: DS8000 Architecture
DS8000 Highlights
DS8000 Architecture
DS8000 RAS Features
Student Notebook
V3.1.0.1
Uempty
Figure 1-43. DS8000: Primary Frame Topology SS481.0
Notes:
The left-hand side of the base frame (viewed from the front of the machine) is the frame
power area. Only the base frame contains rack power control cards (RPC) to control power
sequencing for the storage unit. It also contains a fan sense card to monitor the fans in that
frame. The base frame contains two primary power supplies (PPSs) to convert input AC
into DC power. The power area also contains two or three battery backup units (BBUs)
depending on the model and configuration.
Front Rear
Dense HDD Packaging
16 drives per pack
128 drives in rack
Dual FC-AL Loop Switches
Point to Point Isolation
Two Simultaneous
Operations per loop
Storage Hardware
Maintenance Console
Configuration
Guided Maintenance/Call Home
Supports Multiple Systems
IBM eServer p5 570
Dual 2-way or Dual 4-way
4 I/O <enclosure Bays
Each bay supports
4 Host Adapters and
2 Device Adapters
Standard 19in rack
mounting space
Redundant
Power
BBU:
Battery
Backup
Units
Host Adapter
4 FCP/FICON Ports
or 2 ESCON Ports
Device Adapter
4 FC-AL Ports
DS8000: Primary Frame Topology
Student Notebook
Figure 1-44. DS8000 Frames SS481.0
Notes:
In addition to the processors, the base frame can contain up to eight disk enclosures. Each
of them can contain up to 16 disk drives. In a maximum configuration, the base frame can
hold 128 disk drives. Above the disk enclosures are cooling fans located in a cooling
plenum.
In the 922, the expansion frame can contain, in addition to the 16 disk enclosures, four
more I/O enclosures which doubles the number of HAs and DAs available. I/O enclosures
are only included in the first expansion frame of the 922 or 9A2 models.
DS8000 Frames
Base Frame :
The base frame contains two processor complexes : eServer p5 570 servers
Each of them contains the processor and memory that drive all functions
within the DS8000.
The base frame can contain up to eight disk enclosures, each can contain up
to 16 disk drives.
In a maximum configuration, the base frame can hold 128 disk drives.
The base frame contains four I/O enclosures.
I/O enclosures provide connectivity between the adapters and the
processors.
The adapters contained in the I/O enclosures can be either device or host
adapters (DAs or HAs)
The communication path used for adapter to processor complex
communication is the RIO-G loop.
Expansion Frames :
Each expansion frame can hold up to 16 disk enclosures which contain the
disk drives.
In a maximum configuration, an expansion frame can hold 256 disk drives.
Expansion frames can contain four I/O enclosures and adapters if they are
the first expansion frame that is attached to either a model 922 or a model 9A2
Student Notebook
V3.1.0.1
Uempty
Figure 1-45. IBM TotalStorage DS8100 (2-Way) SS481.0
Notes:
The base frame contains up to 128 DDMs, the two processor bays, 4 RIO-G bays, and an
internal HMC console with screen, keyboard, and server for the HMC. Users connect
directly to the HMC to have outside network access to the DS8000. Without that
connection, configuration function can only take place using the HMC. More later on the
use of the HMC.
IBM TotalStorage DS8100 (2-Way)
Power Supplies
Batteries
I/O Drawers
IBM eServer pSeries
POWER5 Servers
Up to 128 Disks
HMC
Student Notebook
Figure 1-46. DS8300 (4-Way with Two Expansion Frames) SS481.0
Notes:
The base frame and up to two expansion frames make up the DS8000 Storage Unit.
Pictured above is a fully populated DS8300, with two expansion frames, eight RIO-G bays,
and 40 disk enclosures or 640 DDMs.
DS8300 (4-Way with Two Expansion Frames)
Up to 640 Disks
I/O Drawers Batteries
Power Supplies
p5 (POWER5) Servers
HMC
Student Notebook
V3.1.0.1
Uempty
Figure 1-47. DS8100 (Model 921) - 2-way SS481.0
Notes:
The base frame of the Model 921 has 2 CECs, 4 RIO-G bays with 16 Has, 8 DAs or 4 DA
pairs, 0,1,2,3. This allows you to connect either 4 or 8 disk enclosures to each DA pair for
384 DDMs.
Up to 16 Host Adapters (HA)
FCP/FICON HA: 4 independent ports
ESCON HA: 2 ports
Up to 4 Device Adapter (DA) pairs
DA pairs 0 / 1 / 2 / 3
Automatically configured from DDMs
Maximum configuration (384 DDMs)
DA pair 0 = 128 DDMs
DA pair 1 = 64 DDMs
DA pair 2 = 128 DDMs
DA pair 3 = 64 DDMs
Balanced configuration at 256 DDMs,
that is, 64 DDMs per DA pair
DA (card) plugging order : 2 / 0 / 3 / 1
b
0/1 1/0
3/2 2/3
2
2
0
0
3
3
1
1
2
2
0
0
C0
C1
DS8100 (Model 921) - 2-way
Student Notebook
Figure 1-48. DS8300 (Models 922 and 9A2) - 4-way SS481.0
Notes:
The base frame of the Model 922 or 9A2 has 2 CECs, 8 RIO-G bays with 32 HAs, a 16 DAs
or 8 DA pairs, 0-7. This allows you to connect either 4 or 8 disk enclosures to each DA pair
for 640 DDMs.
DS8300 (Models 922 and 9A2) - 4-way
Up to 32 Host Adapters
FCP/FICON HA: 4
independent ports
ESCON HA: 2 ports
Up to 8 DA pairs
DA pairs 0 to 7
Automatically configured
from DDMs
Max configuration (640 DDMs)
DA pairs 1, 3-7 = 64
DDMs
DA pairs 2, 0 = 128
DDMs
Balanced configuration at
512 DDMs, i.e., 64 DDMs
per DA pair
DA (card) pair plugging
order :
2 / 0 / 6 / 4 / 7 / 5 / 3 / 1
b b
0/1 1/0
3/2 2/3
2
2
0
0
6
6
4
4
7
7
5
5
3
3
1
1
2
2
0
0
4/5
5/4
7/6 6/7
C0
C1
Student Notebook
V3.1.0.1
Uempty
Figure 1-49. DS8000 Storage Enclosure Connectivity (1 of 2) SS481.0
Notes:
The device and host adapters operate on a high bandwidth fault-tolerant interconnect
known as the RIO-G. The RIO-G design allows the sharing of host adapters between
servers and offers exceptional performance and reliability.
In the diagram above, you can use the colors as indicators of how the DS8000 hardware is
shared between the servers (the cross hatched color is green and the lighter color is
yellow). On the left-hand side, the green server is running on the left-hand processor
complex. The green server uses the N-way SMP of the complex to perform its operations.
It records its write data and caches its read data in the volatile memory of the left-hand
complex. For fast write data it has a persistent memory area on the right-hand processor
complex. To access the disk arrays under its management (the disks also being pictured in
green), it has its own device adapter (again in green). The yellow server on the right
operates in an identical fashion. The host adapters (in dark red) are deliberately not colored
green or yellow because they are shared between both servers.
DS8000 Storage Enclosure
Connectivity (1 of 2)
SAN fabric
host adapter
host adapter
Persistent memory
Volatile
memory
N-way
SMP
Persistent memory
Volatile
memory
N-way
SMP
RIO-G
Complex 0
Complex 1
RIO-G
device adapter device adapter
F
i
b
r
e

c
h
a
n
n
e
l

s
w
i
t
c
h
FRONT storage
enclosure with
16 dual ported DDMs
REAR storage
enclosure with
16 DDMs
F
i
b
r
e

c
h
a
n
n
e
l

s
w
i
t
c
h
F
i
b
r
e

c
h
a
n
n
e
l

s
w
i
t
c
h
F
i
b
r
e

c
h
a
n
n
e
l

s
w
i
t
c
h
Device Adapter Pair
22 ports FC Switches
(2 in each Storage Enclosure)
Student Notebook
Figure 1-50. DS8000 Storage Enclosure Connectivity (2 of 2) SS481.0
Notes:
Each DS8000 disk enclosure is connected to a DA pair. The disk enclosures are attached
in pairs with one mega-pack placed in front and one in the rear. Each DA pair receives four
disk enclosures before the next DA pair is used. DA pairs are selected in sequence of
installation, which is not numerical in order. DA pair 2 is installed first, then 0, then 6,4 for a
922. Cabling is done differently on LPAR machines Model 9A2 because the RIO-G bays
are split between the LPARs.
DS8000 Storage Enclosure
Connectivity (2 of 2)
o o o
20 port switch
20 port switch
16 DDM
RIO-G Module
RIO-G Module
o o o
20 port switch
20 port switch
16 DDM
DA
RIO-G Interconnect
DA
RIO-G Module
POWER5 2-way SMP
Processor
Memory
Processor
L1,2
Memory
L3
Memory
L1,2
Memory
POWER5 2-way SMP
Memory
L3
Memory
RIO-G Module
Processor
Processor
L1,2
Memory
L1,2
Memory
Note that DA and HA
positions in I/O enclosures
are shown to suit
the intention of the figure
Student Notebook
V3.1.0.1
Uempty
Figure 1-51. DS8000 2 way - Data Flow SS481.0
Notes:
When a write is issued to a volume, this write normally gets directed to the server that owns
this volume. The data flow is that the write is placed into the cache memory of the owning
server. The write data is also placed into the persistent memory of the alternate server.
Data is then written to the disk and discarded from the persistent memory. Data remain in
cache for some amount of time, but if not used is replaced by other data for more recent
I/Os.
Memory DIMMs
Memory DIMMs
P5
L3
Cache
Memory DIMMs
Memory DIMMs
P5
L3
Cache
FICON, ESCON, Fiber Channel links
Host
2-way P5 570 Server 2-way P5 570 Server
RIO-2 Interconnect
RAID Device Adapter
Host Adapter
I/O Drawer
2 Gb FC-AL links
Switched FC-AL Disk Packs
RIO-2:
1 GHz, Byte-wide, Full duplex per link
Non-Arbitrated, Spatial Reuse
Cache Coherent
Hardware fault detection, retry and reconfiguration
DS8000 - 2 way - Data Flow
Student Notebook
Figure 1-52. DS8000 4 way - Data Flow SS481.0
Notes:
When a write is issued to a volume, this write normally gets directed to the server that owns
this volume. The data flow is that the write is placed into the cache memory of the owning
server. The write data is also placed into the persistent memory of the alternate server.
Data is then written to the disk and discarded from the persistent memory. Data remain in
cache for some amount of time, but if not used is replaced by other data for more recent
I/Os.
Host
4-way P5 570 Server

Memory DIMMs
Memory DIMMs
P5
L3
Cache
Memory DIMMs
Memory DIMMs
P5
L3
Cache
4-way P5 570 Server
Memory DIMMs
Memory DIMMs
P5
L3
Cache
Memory DIMMs
Memory DIMMs
P5
L3
Cache
RIO-2 Interconnect
RIO-2 Interconnect
DS8000 - 4 way - Data Flow
Student Notebook
V3.1.0.1
Uempty 1.4 DS8000 Cache Management
Student Notebook
Figure 1-53. Topic: DS8000 Cache Management SS481.0
Notes:
Topic: DS8000 Cache Management
DS8000 Highlights
DS8000 Architecture
DS8000 RAS Features
Student Notebook
V3.1.0.1
Uempty
Figure 1-54. Sequential Prefetching in Adaptive Replacement Cache (SARC) SS481.0
Notes:
SARC or Sequential Pre-fetching and Adaptive Replacement Cache is IBMs newest cache
management algorithm to effectively use the cache memory of the DS8000 to its best
advantage.
Sequential Prefetching in Adaptive
Replacement Cache (SARC)
SARC basically attempts to determine four things:
When data is copied into the cache
Which data is copied into the cache
Which data is evicted when the cache becomes full
How does the algorithm dynamically adapt to different
workloads
SARC uses:
Demand paging for all standard disk I/O
Sequential pre-fetch for sequential I/O patterns
Student Notebook
Figure 1-55. DS8000 and DS6000 Caching SS481.0
Notes:
The adaptive replacement cache is a self-tuning, low-overhead algorithm that responds
online to changing access patterns. ARC continually balances between the currency and
frequency features of the workload, demonstrating that adaptation eliminates the need for
the workload-specific pretuning that plagued many previous proposals to improve LRU.
ARCs online adaptation likely has benefits for real-life workloads due to their richness and
variability with time.
DS8000 and DS6000 Caching
Best caching algorithms in industry
Over 20 years experience
Simplified Adaptive Replacement Cache (SARC)
Self-Learning algorithms
Adaptively and dynamically learn what data should be
stored in Cache based upon the recent access and
frequency needs of the Hosts
Adaptive Replacement Cache
Most advanced and sophisticated algorithms to
determine what data in Cache is removed to
accommodate newer data
Prefetching
Predictive algorithm to anticipate data prior to a host
request and loads it into Cache
Benefits
Leading performance
Been proven to improve Cache hit by up to 100% over
previous IBM caching algorithms and improve I/O
response time by 25%
More efficient use of Cache
Intelligent caching algorithm profiles Host access
patterns to determine what data is stored
Need less Cache than competitors
Benefits of adaptive replacement caching
Nimrod Megiddo and Dharmendra S. Modha, "Outperforming LRU with an Adaptive Replacement Cache Algorithm," IEEE Computer, pp. 4-11, April 2004.
Lower cache-to-backstore ratios with outstanding service times
0
0.2
0.4
0.6
0.8
1
0 64 128 192 256
Cache Size (GB)
C
a
c
h
e

H
i
t

R
a
t
i
o
z/OS
Open
Student Notebook
V3.1.0.1
Uempty
Figure 1-56. DS8000 and DS6000 Caching Considerations SS481.0
Notes:
The data is written into the cache memory of the owning server. The write data is also
placed into the persistent memory of the alternate server. SARC is a self-tuning algorithm
and responds well to changing conditions in workload.
DS8000 and DS6000 Caching Considerations
The self-tuning, low-overhead, scan-resistant adaptive replacement cache algorithm outperforms the
least-recently-used algorithm by dynamically responding to changing access patterns and
continually balancing between workload recently and frequency features.

The adaptive replacement cache is a self-tuning, low-overhead algorithm that responds online to changing
access patterns. ARC continually balances between the recency and frequency features of the workload,
demonstrating that adaptation eliminates the need for the workload-specific pretuning that plagued many
previous proposals to improve LRU.
ARCs online adaptation likely has benefits for real-life workloads due to their richness and variability with
time. These workloads can contain long sequential I/Os or moving hot spots, changing frequency and
scale of temporal locality and fluctuating between stable, repeating access patterns and patterns with
transient clustered references.

Like LRU, ARC is easy to implement, and its running time per request is essentially independent of the cache
size.

A real-life implementation revealed that ARC has a low space overhead 0.75 percent of the cache size.
Also, unlike LRU, ARC is scan resistant in that it allows one-time sequential requests to pass through
without polluting the cache or flushing pages that have temporal locality.
Likewise, ARC also effectively handles long periods of low temporal locality. ARC leads to substantial
performance gains in terms of an improved hit ratio compared with LRU for a wide range of cache sizes.
ARC replacement policy functions online and is completely self-tuning. Because ARC maintains no frequency
counts, unlike LFU and FBR, it does not suffer from periodic rescaling requirements. Also, unlike LIRS,
ARC does not require potentially unbounded space overhead. Finally, ARC, 2Q, LIRS, and FBR have
constant-time implementation complexity while LFU, LRU-2, and LRFU have logarithmic implementation
complexity.
Student Notebook
Student Notebook
V3.1.0.1
Uempty 1.5 DS8000 RAS Features
Student Notebook
Figure 1-57. Topic: DS8000 RAS Features SS481.0
Notes:
RAS is Reliability, Accessibility and Serviceability.
Topic: DS8000 RAS Features
DS8000 Highlights
DS8000 Architecture
DS8000 RAS Features
Student Notebook
V3.1.0.1
Uempty
Figure 1-58. DS8000 Hardware Components Detail SS481.0
Notes:
Lets review the hardware components again.
DS8000 Hardware Components Detail
HA
DA
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Module
RIO-G Module
PowerPC
Fibre Channel
Protocol Proc
Fibre Channel
Protocol Proc
RIO-G Interconnect
I/O enclosure
4 HAs
DA
RIO-G Module
POWER5 2-way SMP
Processor
Memory
Processor
L1,2
Memory
L3
Memory
L1,2
Memory
POWER5 2-way SMP
Memory
L3
Memory
RIO-G Module
Processor
Processor
L1,2
Memory
L1,2
Memory
Server 1
Server 0
Student Notebook
Figure 1-59. Processor Complex RAS SS481.0
Notes:
First Fault Data Capture is a RAS feature that allows easy diagnoses of problems. The
system is self-monitoring and redundant which means less down-time. Most maintenance
functions can be done concurrently.
Processor Complex RAS
Processor complex has the same RAS features of the P5-570 which
is an integral part of the DS8000 architecture.
IBM Server p5 system main RAS features:
First Failure Data Capture
Boot process and Operating System monitoring
Environmental monitoring
Self-healing
Memory reliability, Fault tolerant an Integrity
Error Checking Correction (ECC)
Memory scrubbing and thresholding
N+1 redundancy
Resource deallocation
Concurrent maintenance
Student Notebook
V3.1.0.1
Uempty
Figure 1-60. Hypervisor Storage Image Independence SS481.0
Notes:
A logical partition (LPAR) is a set of resources on a processor complex that supply enough
hardware to support the ability to boot and run an operating system (which we call a
server).
The LPARs created on a DS8000 processor complex are used to form storage images.
These LPARs share not only the common hardware on the processor complex, including
CPUs, memory, internal SCSI disks and other media bays (such as DVD-RAM), but also
hardware common between the two processor complexes. This hardware includes such
things as the I/O enclosures and the adapters installed within them.
Hypervisor - Storage Image Independence
LPARs created on a DS8000 processor complex are used to form
storage images.
These LPARs share:
Common hardware on the processor complex: CPUs memory,
internal SCSI disks and other media bays (such as DVD-RAM), but
also
Hardware common between the two processor complexes: I/O
enclosures and the adapters installed within them.
The mechanism used to share the resources between the LPARs
is the hypervisor
I/O Enclosures:
Use N+1 power and cooling
Use hop-swap PCI-X adapters in blind-swap hot-plug cassette
Can be replaced concurrently
Each slot can be independently powered on/off
I/O Enclosure connected to each Processor complex through two
redundant RIO-G loops
If a resource is not accessible from one server, requests can be
routed to the other server to be sent out on an alternate RIO-G port.
Student Notebook
Figure 1-61. Server RAS (1 of 2) SS481.0
Notes:
The p5 570 is an integral part of the DS8000 architecture. It is designed to provide an
extensive set of reliability, availability, and serviceability (RAS) features that include
improved fault isolation, recovery from errors without stopping the processor complex,
avoidance of recurring failures, and predictive failure analysis.
Server RAS (1 of 2)
The DS8000 employs similar methodology to the
ESS to provide data integrity when performing
write operations and server failover.
Meta data check: The metadata is checked by various
internal components to validate the integrity of the data as it
moves throughout the disk system or sent back to the host.
Server failover and fail back:
LSS and server affinity:
LSS with even number have an affinity with server 0
LSS with odd number have an affinity with server 1
When a host operating system issues a write to a logical
volume, the DS8000 host adapter directs that write to the
server that owns the LSS to which that logical volume is a
member.
Student Notebook
V3.1.0.1
Uempty
Figure 1-62. Server RAS (2 of 2) SS481.0
Notes:
To understand the process of server failover and fail-back, we have to understand the
logical construction of the DS8000. In short, to create logical volumes on the DS8000, we
work through the following constructs:
We start with DDMs that are installed into pre-defined array sites.
These array sites are used to form RAID-5 or RAID-10 arrays.
These RAID arrays then become members of a rank.
Each rank then becomes a member of an extent pool. Each extent pool has an affinity
to either server 0 or server 1. Each extent pool is either open systems FB (fixed block)
or zSeries CKD (count key data).
Within each extent pool we create logical volumes, which for open systems are called
LUNs and for zSeries, 3390 volumes. LUN stands for logical unit number, which is used
for SCSI addressing. Each logical volume belongs to a logical subsystem (LSS).
Server RAS (2 of 2)
Under normal operation, both DS8000 servers are actively
processing I/O requests
Each write is placed into the cache memory of the server
owning the volume and also into the NVS memory of the
alternate server.
Failover: In case of one server failure, the remaining
server is able to take over all of its functions
RAID arrays which are connected both servers, can be accessed
from the Device adapters of the remaining server.
Since the DS8000 has only one copy of data in cache of
remaining server, it now takes the following mechanism:
It de-stages the contents of its NVS to the disk subsystem.
The NVS and cache of remaining server are divided in two, half
for the odd LSSs and half for the even LSSs.
Remaining server now begins processing the writes (and
reads) for all the LSSs.
Failback: When the failed server has been repaired, fail
back process is activated
It completes in less than eight seconds and is invisible to the
attached hosts.
Student Notebook
Figure 1-63. Server Failover SS481.0
Notes:
To understand the process of server failover and fail-back, the figure above illustrates how
the cache memory of server 0 is used for all logical volumes that are members of the even
LSSs. Likewise, the cache memory of server 1 supports all logical volumes that are
members of odd LSSs. But for every write that gets placed into cache, another copy gets
placed into the NVS memory located in the alternate server.
Server Failover
Normal flow of data for a write :
1. Data is written to cache memory in
the owning server.
2. Data is written to NVS memory of
the alternate server.
3. The write is reported to the
attached host as having been
completed.
4. The write is destaged from the
cache memory to disk.
5. The write is then discarded from the
NVS memory of the alternate server.
After a failover, remaining server is
processing all I/Os with cache and
NVS divided by two, one for odd LSSs
and one for even LSSs.
Server 0 Server 1
Cache
memory
for even
LSSs
NVS
for odd
LSSs
NVS
for even
LSSs
Cache
memory
for odd
LSSs
Server 0 Server 1
Cache
memory
for even
LSSs
NVS
for odd
LSSs
Failover
NVS
for
even
LSSs
Cache
for
odd
LSSs
Cache
for
even
LSSs
NVS
for
odd
LSSs
Student Notebook
V3.1.0.1
Uempty
Figure 1-64. NVS Recovery After Complete Power Loss SS481.0
Notes:
During normal operation, the DS8000 preserves fast writes using the persistent copy in the
alternate server. To ensure these fast writes are not lost, the DS8000 contains battery
backup units (BBUs). If all the batteries were to fail (which is extremely unlikely since the
batteries are in an N+1 redundant configuration), the DS8000 would lose this protection
and consequently that DS8000 would take all servers offline. If power is lost to a single
primary power supply this does not affect the ability of the other power supply to keep all
batteries charged, so all servers would remain online.
NVS Recovery After Complete Power Loss
DS8000
Batteries Backup Units (BBUs)
Both power supplies stopped
Batteries not used to keep disks spinning
Scenario at power off
All HA I/O blocked
Each server copies NVS data to internal
disk
Two copies per server
When copy process complete, each server
shuts down AIX
When AIX shutdown complete for both
servers (or time out expires), the
DS8000 is powered down
Scenario at power on
Processor complexes power-on and
perform power on self test
Each server boots up
During Boot, server detects NVS data on
its disks and destage it to FC-AL
disks
When battery units reach a certain level of
charge, the servers come online
NVS contents preserved indefinitely
Note: The servers will not come online until
the batteries are fully charged
DS6000
Preserves contents of controller memory for
at least 72 hours
Designed to be replaced every four years
Preserve all data in memory while input
power is not available
When power becomes available again
DS6800 controllers boot up
But leave the NVS portion of controller
memory untouched
During init process, NVS data area
examined
If any undestaged write data is found, it is
destaged to disk prior to the
controller coming online
NVS contents preserved 72 hours (like ESS)
Student Notebook
Figure 1-65. Host Connection Availability SS481.0
Notes:
It is always preferable that hosts that access the DS8000 have at least two connections to
separate host ports in separate host adapters on separate I/O enclosures.
Each attached host operating system now requires a mechanism to allow it to manage
multiple paths to the same device, and to preferably load balance these requests. Also,
when a failure occurs on one redundant path, then the attached host must have a
mechanism to allow it to detect that one path is gone and route all I/O requests for those
logical devices to an alternative path. SDD is provided for the DS6000 and DS8000 and
can be used on ESS and SVC as well.
Host Connection Availability
On DS8000 host adapters are shared between the servers.
Unlike the DS6000 which use the concept of preferred path.
It is preferable for hosts to have at least two connections
to separate host adapters in separate I/O enclosures:
This configuration allows the host to survive a hardware failure on any
component on either path.
This is also important because during a microcode update, an I/O
enclosure may need to be taken offline.
Multi-pathing softwares:
Subsystem Device Driver (SDD) is able to manage both path failover
and preferred path determination.
SDD is usable with ESS800, DS6000, DS8000 or SVC.
Student Notebook
V3.1.0.1
Uempty
Figure 1-66. Whats New with SDD 1.6.0.x SS481.0
Notes:
SDD 1.6.0.x is provided for use with the DS6000 or DS8000, but is not required if other
multipath software is being used. A new level of SDD is available for the DS6000, and
DS8000 and servers currently using SDD for the ESS have to be upgraded to support the
DSxxxx.
Whats New with SDD 1.6.0.x
Support for the DS8000, DS6000 and preferred path
AIX:
Support for AIX 5.3
SDDPCM:
Support for dynamically changing the device algorithm
Support for dynamically changing the device hcheck_interval
Support for dynamically changing the device hcheck_mode
Support for the persistent reserve commands
HP-UX:
Support for HP-UX 11i V2
HP-UX 11.0 32-bit kernel is no longer supported
Linux:
Addition of Linux remote boot support
Support for SuSE SLES9
Support for Red Hat Enterprise Linux 3.0 64-bit
Support for IBM eServer 325 on Red Hat EL 3.0 and United Linux
1.0 (SuSE SLES8)
Windows 2000:
Support for load balancing in a clustering environment
Remote boot support for Windows 2000 using an Emulex HBA
Windows Server 2003:
Support for load balancing in a clustering environment
Remote boot support for Windows Server 2003 32-bit using an
Emulex HBA
Remote boot support for Windows Server 2003 64-bit using a
QLogic HBA
Student Notebook
Figure 1-67. Disk Subsystem SS481.0
Notes:
The DS8000 series supports RAID-5 arrays. RAID-5 is a method of spreading volume data
plus parity data across multiple disk drives. RAID-5 provides faster performance by striping
data across a defined set of DDMs. Data protection is provided by the generation of parity
information for every stripe of data. If an array member fails, then its contents can be
regenerated by using the parity data.
RAID-10 is not as commonly used as RAID-5, mainly because more raw disk capacity is
needed for every GB of effective capacity.
When the array sites are created on a DS8000, the DS8000 microcode determines which
sites contain spares. The first four array sites normally each contribute one spare to the DA
pair, with two spares being placed on each loop. In general, each device adapter pair thus
has access to four spares.
The DS8000 implements a smart floating technique for spare DDMs. On an ESS 800, the
spare floats. This means that when a DDM fails and the data it contained is rebuilt onto a
spare, then when the disk is replaced, the replacement disk becomes the spare.
Disk Subsystem
RAID5 and RAID10
RAID5 : 7+P or 6+P+S
RAID10 : 2x4 or 2x3 + 2S
DS8000 Doesnt support NON-Raid configurations (JBODs)
Spare disks creation:
A minimum of one spare is created for each array site defined until
the following conditions are met:
A minimum of four spares per DA pair.
A minimum of four spares of the largest capacity array site on the
DA pair.
A minimum of two spares of capacity and RPM greater than or
equal to the fastest array site of any given capacity on the DA
pair.
Floating spare:
The DS8000 microcode may choose to migrate a new spare disks to
a more optimum position to better balance the spares across the
DA pairs, the loops and the enclosures.
(useful after a drive replacement that became a spare drive).
Student Notebook
V3.1.0.1
Uempty
Figure 1-68. Disk Subsystem SS481.0
Notes:
Replacement of a failed drive does not affect the operation of the DS8000 because the
drives are fully hot pluggable. Due to the fact that each disk plugs into a switch, there is no
loop break associated with the removal or replacement of a disk. In addition there is no
potentially disruptive loop initialization process.
The drives used in the DS8000 incorporate Predictive Failure Analysis (PFA) and can
anticipate certain forms of failures by keeping internal statistics of read and write errors. If
the error rates exceed predetermined threshold values, the drive will be nominated for
replacement.
The DS8000 periodically reads all sectors on a disk. This is designed to occur without any
interference with application performance. If ECC-correctable bad bits are identified, the
bits are corrected immediately by the DS8000.
Each DDM in the DS8000 is attached to two 20-port SAN switches. These switches are
built into the disk enclosure controller cards. The figure above illustrates the redundancy
features of the DS8000 switched disk architecture. Each disk has two separate
Disk Subsystem
Hot pluggable DDMs
Predictive Failure Analysis (PFA)
Failures anticipation
Disk Scrubbing
All disk sectors periodically read and bad bits corrected.
Each DDM attached to two FC switches
Each disk has two separate connections on the backplane.
Each DA has a connection to the two switches
Midplane
to next expansion
enclosure
Server 1
device adapter
Server 0
device adapter
Storage enclosure backplane
to next expansion
enclosure
Student Notebook
connections to the backplane. This allows it to be simultaneously attached to both
switches.
Student Notebook
V3.1.0.1
Uempty
Figure 1-69. Power and Cooling SS481.0
Notes:
The DS8000 has completely redundant power and cooling. Every power supply and
cooling fan in the DS8000 operates in what is known as N+1 mode. This means that there
is always at least one more power supply, cooling fan, or battery than is required for normal
operation. In most cases this simply means duplication.
Power and Cooling
Completely redundant power and cooling in N+1
mode
Battery Backup Units (BBU)
Used for NVS (part of the servers memory)
Can be replaced concurrently
Rack Power Control cards (RPC)
Two RPC cards for redundancy
Each card can control power of an entire DS8000
Power fluctuation protections
DS8000 tolerate a momentary power interruption for
approximately 30 ms
After that time, servers start copying content of NVS to
internal SCSCI disks
Student Notebook
Figure 1-70. Microcode Update SS481.0
Notes:
The DS8000 contains many discrete redundant components. Most of these components
have firmware that can be updated. This includes the processor complexes, device
adapters, and host adapters. Each DS8000 server also has an operating system (AIX) and
Licensed Internal Code (LIC) that can be updated. As IBM continues to develop and
improve the DS8000, new releases of firmware and LIC become available to offer
improvements in both function and reliability.
Microcode Update
Concurrent code update
Management console can hold six different versions of code
Each server can hold three different versions of code
Installation process:
Internal Management Console (MC) code update
New DS8000 LIC downloaded on the Internal MC
LIC uploaded from MC to each DS8000 server internal storage
New firmwares can be loaded from MC directly into each devices,
May require server reboot with failover of it Logical Subsystems to the
other server
Update of servers operating system and LIC
Each server updated one at a time with failover of it Logical Subsystems
to the other server
Host adapters firmware update
Each adapter impacted less than 2,5 s which should not affect
connectivity
Longer interruption managed by hosts mulit-pathing softwares.
Student Notebook
V3.1.0.1
Uempty
Figure 1-71. Management Console SS481.0
Notes:
The DS8000 management network consists of redundant Ethernet switches and redundant
Storage Hardware Management (S-HMC) consoles.
Management Console
Redundant Ethernet switches
Each switch used in a separate Ethernet network with
non-routable private IP addresses assigned in networks
172.16/16 and 172.17/16
Redundant Management Console
Each DS8000 can be connected via the redundant Ethernet
switches to both Management console
Student Notebook
Checkpoint
Exercise -- Unit 1 Checkpoint
1. T/F The DS8000 can be equipped with 2-way or 4-way PowerPC
processors and provide redundant control of the storage arrays
2. T/F The DS8000 Model 922 provides the capability to divide the
cluster into logical partitions called LPARs, which divides the
hardware components into two separate controller which can
operate independently.
3. T/F The DS8000 System has scalable I/O bays which adds
front-end host adapters and back-end device adapters plus internal
bus bandwidth contained within each bay.
4. The DS8000 System supports the following disk devices.
a. 2 Gb 73 GB 15 K disk drives
b. 2 Gb 146 GB 10 K disk drives
c. 2 Gb 300 GB 10 K disk drives
d. All of the above
5. T/F The DS8000 System can be configured offline using a
Simulated DS Storage Manager interface.
Student Notebook
V3.1.0.1
Uempty
Figure 1-72. Unit Summary SS481.0
Notes:
Unit Summary
Having completed this unit, you should be able to:
Describe the IBM DS8000 SARC cache management
Student Notebook
Student Notebook
Copyright IBM Corp. 2005 Unit 2. DS8000 Virtualization Concepts 2-1
V3.1.0.1
Uempty
Unit 2. DS8000 Virtualization Concepts
The DS6000/DS8000 storage subsystem uses some new terms and
concepts to define arrays and logical volumes for host systems. This
unit looks at these new terms and concepts so the students can
understand the process required to create logical volumes and
connect them to a host system.
Describe the new terms and concepts related to physical and
logical configuration
Describe the creation of arrays from arraysites
Describe the creation of ranks and extent pools
Describe the definition of logical volumes for Open Systems hosts
Describe the process of defining a host attachment and configuring
DS I/O ports.
Describe process of creating a volume group
How You Will Check Your Progress
Accountability:
Checkpoint
References
Concepts
SC24-7623 IBM TotalStorage: DS8000 User's Guide
Guide
Student Notebook
Notes:
Unit Objectives
Describe the storage virtualization terms
Describe the physical configuration concepts: Definitions
Describe the logical configuration concepts: Definitions
Describe the logical address groups and addressing
Describe the logical subsystems in the DS6000/DS8000
Describe the logical device definitions in the DS6000/DS8000
Student Notebook
V3.1.0.1
Uempty 2.1 Physical Configuration Concepts
Student Notebook
Figure 2-2. Topic: Physical Configuration Concepts SS481.0
Notes:
This unit discusses the virtualization and logical mapping of the DS8000 and DS6000.
IBM MOP Products and Solutions Support Center
Physical Configuration Concepts: Definitions
Array Site
Array
Rank
Extent Pool
Logical Volume
Volume Group
Host Attachment
Logical Configuration Concepts: Definitions
Storage-Plex, Storage Facility Image
Address Group
LSS / LCU
Logical Device
Topic: Physical Configuration Concepts
Student Notebook
V3.1.0.1
Uempty
Figure 2-3. Physical Configuration Concepts: Definitions SS481.0
Notes:
Virtualization is the abstraction
process going from the DDM physical
disk drives to a logical volume that
the hosts and servers see as if it were
a physical disk.
Student Notebook
Figure 2-4. DS8000 / DS6000 - Storage Hierarchy SS481.0
Notes:
Each array site consists of eight DDMs in a DS8000. Four DDMs are taken from the front
enclosure in an enclosure pair, and four are taken from the rear enclosure in the pair. This
means that when a RAID array is created on the array site, half of the array is on each
enclosure.
Because the front enclosures are on one switched FC-AL loop, and the rear enclosures are
on a second switched FC-AL loop, this splits the array across two loops. This is called array
across loops (AAL). The DS6000 does not employ AAL, but places its disks on the same
FC-AL loop.
Array sites can be configured into arrays using RAID 5 or RAID 10 configuration for
redundancy. Spares are automatically set aside by the DS8000, so that two spares are
available on each FC-AL loop. If there are multiple disk enclosures having different sizes of
disk, more spares may be reserved for each size.
In the ESS, an array was automatically placed into a rank and formatted for the CKD or FB
as selected by the user. The DS8000 allows the user to perform this action as a separate
step, and supports ranks which have multiple arrays at some point. In the DS8000, the
Extent
Pool
Rank
{r}
Array
[a]
Array Site
Disk
RAID 5 RAID 10
6+P+S 3x2+2S
7+P 4x2
[ ] [ ]

1-N ranks in Extent Pool
Associated with server0 or server1
All Extents are same Type
CKD or FB
Same RAID recommended
Same DDM RPM recommended
1,2*,4*,8* Arrays per rank
Rank Divided into N Fixed Sized Extents CKD
(3390 Mod1) or FB (1 GB)

DS8000 one array site used to construct one
RAID Array (8 DDMs)
DS8000 Two array sites used to construct one
RAID Array (8 DDMs)
DS6000 (post GA) one 4 DDM array site used
to construct one Array (4 DDMs)
Logical grouping of four disks (DS6000) or eight
disks (DS8000) of same speed and capacity
Individual DDMs: 73, 146, 300 GB
Post GA
For DS8000
{[a]} {[a],[a],[a],[a]}
Extent Pool
{r}
{r}. . .{r} s
DS8000 / DS6000 - Storage Hierarchy
Student Notebook
V3.1.0.1
Uempty
format of the array is not determined when the RAID level is set, but when the rank is
formed, the storage type of CKD or FB determines the array format.
Extent pools determine the server affinity and creates a pool of extents of a certain format
CKD or FB. Multiple ranks can be entered into an Extent Pool and volumes are allocated
contiguously in one rank unless there are not enough extents, then they span to another
rank if available in the pool. CKD extents are 1113 cylinders or a 3390-1 size and Open
system FB extents are 1 GB binary or 230.
Student Notebook
Figure 2-5. Storage Hierarchy SS481.0
Notes:
Volumes or LUNs are made up of extents from the extent pool. Volumes can be made in
many sizes, but extents are fixed to 1 GB or 1113 cylinders, so space is wasted if volumes
are not defined on an extent boundary. Currently, there are some issues with volume sizes
for open systems LUNs in terms of the compatibility with the ESS.
Volume Groups are a way of doing LUN masking for the DS8000. It is similar to LUN
partitioning of the DS4000. A volume group is a combination of a set of LUNs and a host
attachment. These two items create a volume group and allow the host, which is an object
in the host definition along with its ports, to connect to the host to the DS8000.
Volumes or LUNs
Made up of extents from one extent pool
Min size 0.1 GB or 1 cylinder
Max size 2 TB (FB) 56 GB(CKD)
Can be larger than one rank if more than one
rank in pool
Associated with LSS during configuration
Volume Group
Contains LUNs and host attachments -- FB LUN
masking
One host attachment (one port or port group) can
be member of only one volume group
One volume can be member of multiple volume
groups
Multiple hosts (even different open systems server
types) can be member of the same volume group
Host
Multiple server ports can be specified (in one or
more groups) in one host definition
AIX host port
iSeries host
port group
AIX host port
FB
FB
FB (i)
FB
FB
FB
Storage Hierarchy
Student Notebook
V3.1.0.1
Uempty
Figure 2-6. DS8000 Switched Loop Layout in an Enclosure Pair SS481.0
Notes:
An array site is a group of eight DDMs. What DDMs make up an array site is
pre-determined by the DS8000, but note that there is no pre-determined server affinity for
array sites. The DDMs selected for an array site are chosen from two disk enclosures on
different loops, so the configuration is by default AAL or Array Across Loops.
Each array site consists of eight DDMs
from the same enclosure pair
Four DDMs are taken from the front disk
enclosure in an enclosure pair
Four are taken from the rear disk
enclosure in the pair
When a RAID array is created on the
array site, half of the array is on each
disk enclosure
Front enclosures are on one switched loop
Rear enclosures are on the second
switched loop
This splits the array across two
loops
This is called array across loops (AAL)
To make the diagrams clearer, only 16 DDMs are shown, 8 in each disk enclosure
When fully populated there would be16 DDMs in each disk enclosure
Regardless, the diagram represents a valid configuration
Front enclosure
Rear enclosure
Device adapter pair
Server
0
device
adapter
loop 0
loop 1
Server
1
device
adapter
loop 0
loop 1
3
Fibre channel switch 1
4
There are two separate
switches in each enclosure.
2
DS8000 Switched Loop Layout
in an Enclosure Pair
Student Notebook
Figure 2-7. DS8000 Array Across Loops SS481.0
Notes:
As you can see from the picture above, the array sites span loops. Four DDMs are taken
from loop 1 and another four DDMs are taken from loop 2. Array sites are the building
blocks used to define arrays.
Server
0
device
adapter
loop 0
loop 1
Server
1
device
adapter
loop 0
loop 1
3
Fibre channel switch 1
4
There are two separate
switches in each enclosure.
2
Array site 0 Array site 1
Array site 0 (the green disks) uses the four
left-hand DDMs in each enclosure
Array site 1 (the yellow disks), uses the four
right-hand DDMs in each enclosure
When an array is created on each array site, half
of the array is placed on each loop
If the disk enclosures were fully populated with
(16) DDMs, there would be four array sites
DS8000 Array Across Loops
Student Notebook
V3.1.0.1
Uempty
Figure 2-8. DS6000 Physical Layout SS481.0
Notes:
The storage enclosure pair is connected to the servers from the RIO-G bays using the
device adapters. DA pair 2 connects to the first pair of disk enclosures. If more disk
enclosures are added, the loop is extended from the outports of the first two disk
enclosures to the second pair.
Device Adapter
S
e
r
v
e
r
0
S
e
r
v
e
r
1
S
t
o
r
a
g
e

e
n
c
l
o
s
u
r
e

p
a
i
r
Switched loop 1
Switches
Device Adapter
Switched loop 2
Inter-server communication
DS6000 Physical Layout
Student Notebook
Figure 2-9. DS6000 Array Sites on Loop SS481.0
Notes:
The array site on the DS6000 is just four disks and they are not selected across the FC-AL
loop as they are in the DS8000, so the array site is on the same loop. The array site is also
only four disks.
An array site is a group of
four DDMs
DDMs selected for an
array site are chosen
from the same disk
enclosure string
All DDMs in an array site
are of the same type
(capacity and RPM)
Arrays are created from
one (not at GA) or two
array sites
Array
Site 1
Array
Site 2
Switches
Loop 1 Loop 2
DS6000 Array Sites on Loop
Student Notebook
V3.1.0.1
Uempty
Figure 2-10. DS8000 Creating an Array SS481.0
Notes:
According to the DS8000 sparing algorithm, from zero to two spares may be taken from the
array site. An array is formed using one array site and while the array could be accessed by
each adapter of the device adapter pair, it is managed by one device adapter.
Which adapter and which server manages this array are defined later in the configuration
path.
D1, D2, D3, and so on, stand for the set of data contained on one disk within a stripe on the
array. If, for example 1 GB of data is written, it is distributed across all the disks of the array.
An array is created from one array site.
Forming an array means defining it for a
specific RAID type
In the DS8000 current implementation, one
array is defined using one array site
According to the DS8000 sparing
algorithm, from zero to two spares may be
taken from the array site
An array is formed using one array site and
while the array could be accessed by each
adapter of the device adapter pair, it is
managed by one device adapter
Which adapter and which server manages
this array are defined later in the
configuration path
D1, D2, D3, and so on, stand for the set of
data contained on one disk within a stripe on
the array
If, for example 1 GB of data is written, it is
distributed across all the disks of the array

Array
Site
RAID
Array
Spare
Data
Data
Data
Data
Data
Data
Parity
Creation of
an array
D1 D7 D13 ...
D2 D8 D14 ...
D3 D9 D15 ...
D4 D10 D16 ...
D5 D11 P ...
D6 P D17 ...
P D12 D18 ...
Spare
DS8000 Creating an Array
Student Notebook
Figure 2-11. Array Site Configurations: DS8000 Eight DDMs/Array with Arrays Across Loops SS481.0
Notes:
The array site can be made into arrays of RAID 5 or RAID 10. In the DS8000 there are
eight disks, so the RAID 5 arrays can be 6+P+S or 7+P arrays. RAID 10 arrays can be
3+3+2S or 4+4 arrays.
Array Site
RAID 5
6 + P + S
7 + P
RAID 10
3x2 + 2S
4x2
D D D D
D
D
D
D
D D D D
D D D D
A B C D
a b c d
A B C S
a b c S
3x2 + 2S
4x2
A B C D
E F G S
A B C D
E F G H
7 + P 6 + P + S
Array Site Configurations: DS8000
Eight DDMs/Array with Arrays Across Loops
Student Notebook
V3.1.0.1
Uempty
Figure 2-12. DS8000 AAL Benefits SS481.0
Notes:
The AAL configuration was implemented in the ESS-800 to improve performance. In the
DS8000 it is a default. Writes are spread across two different loops and I/Os are done
concurrently, improving the performance for the write. Parallel reads can also be done
across the loops.
AAL is used to increase performance.
When the device adapter writes a stripe of data to a RAID-5 array,
it sends half of the write to each switched loop.
By splitting the workload in this manner, each loop is worked
evenly, which improves performance.
If RAID-10 is used, two RAID-0 arrays are created.
Each loop hosts one RAID-0 array.
When servicing read I/O, half of the reads can be sent to each loop,
again improving performance by balancing workload.
DS8000 AAL Benefits
Student Notebook
Figure 2-13. Sparing Rules (DS8000) SS481.0
Notes:
The sparing rules say there must be two spares available of each loop, so since each DA
Pair has two loops so there must be four spares per DA pair, however, if there are different
sizes of disks in the disk enclosures, then you must have two spares for each disk size.
Array Sites have attributes of
Capacity
Rpm
A minimum of one spare is required for each Array Site defined
until the following conditions are met
Minimum of four spares per DA pair
The spares are balanced between the two device interfaces
Minimum four spares of the largest capacity Array Site on the DA
pair
The spares are balanced between the two device interfaces
Minimum two spares of capacity and rpm greater than or equal to
the fastest Array Site of any given capacity on the DA pair
Spares are balanced between the two device interfaces
All spares are available to all Array Sites on that DA pair
Order of installation will influence the number of spares
Sparing Rules (DS8000)
Student Notebook
V3.1.0.1
Uempty
Figure 2-14. Sparing Example 1 - RAID 5: DS8000 All Same Capacity, Same RPM SS481.0
Notes:
Assumes all devices same capacity and same RPM
- Two spares per loop and two spares in each Array Group
- Additional RAID 5 arrays are 7 + P
- Any added RAID 10 arrays are 4x2
All spares available to all arrays on DA pair
1
2 3
4
DA
DA
6 + P
Array
6 + P
Array
6 + P
Array
6 + P
Array
Sparing Example 1 RAID 5: DS8000
All Same Capacity, Same RPM
Student Notebook
Figure 2-15. Sparing Example 2 - RAID 10: DS8000 All Arrays Same Capacity and Same RPM SS481.0
Notes:
- Two spares per loop and two spares in each Array Group
- Additional RAID 10 arrays are 4x2
- Any added RAID 5 arrays are 7 + P
All spares available to all arrays on DA pair
1
2
3
4
DA
DA
3x2 + 2S
Array
4x2
Array
4x2
Array
3x2 + 2S
Array
All Arrays Same Capacity and Same RPM
Student Notebook
V3.1.0.1
Uempty
Figure 2-16. Sparing Example 3 DS8000 RAID 5 SS481.0
Notes:
Assumes all devices same RPM
- Two spares per loop and two spares in each array group
- Additional 146 GB RAID arrays are 7 + P (RAID 5) or 4x2 (RAID 10)
Minimum four pares of the largest capacity array Site on the DA pair
Next two 300 GB arrays are also 6 + P (if RAID _______________
- If the next 300 GB array configured is RAID 10, then that array will be 3x2 and any
additional 300 GB arrays on this DA pair do not have spares
All spares available to all arrays on the DA pair
1
2
3
4
DA
DA
6 + P
Array
6 + P
Array
6 + P
Array
6 + P
Array
6
5
6 + P
Array
6 + P
Array
300 GB
300 GB 146 GB
146 GB
146 GB
146 GB
Sparing Example 3 DS8000 RAID 5
First Four arrays 146 GB and next Two arrays 300 GB (same RPM)
Student Notebook
Figure 2-17. DS6000 Creating an Array SS481.0
Notes:
An array is formed using one or two array sites and while the array could be accessed by
each adapter of the device adapter pair, it is managed by one device adapter. Which
adapter and which server manage this array are defined later in the configuration path.
D1, D2, D3, and so on, stand for the set of data contained on one disk within a stripe on the
array. If, for example, 1 GB of data is written, it is distributed across all the disks of the
array.
Arrays are created from one or two array
sites
Forming an array means defining it for a
specific RAID type
According to the DS6000 sparing
algorithm, up to two spares may be
taken from the array sites used to
construct the array on each device
interface (loop)
An array is formed using one or two array
sites and while the array could be
accessed by each adapter of the device
adapter pair, it is managed by one device
adapter
Which adapter and which server
manage this array are defined later in
the configuration path
D1, D2, D3, and so on, stand for the set of
data contained on one disk within a stripe
on the array
If, for example, 1 GB of data is written, it is
distributed across all the disks of the array
Array Site 1
RAID
Array
Spare
Data
Data
Data
Data
Data
Data
Parity
Creation of
an array
D1 D7 D13 ...
D2 D8 D14 ...
D3 D9 D15 ...
D4 D10 D16 ...
D5 D11 P ...
D6 P D17 ...
P D12 D18 ...
Array Site 2
DS6000 Creating an Array
Student Notebook
V3.1.0.1
Uempty
Figure 2-18. DS6000: Four DDM Arrays (Not at GA) SS481.0
Notes:
...
...
DA DA
(Device
Adapter)
(Device
Adapter)
Array Site Two Array Sites
DDMs
DDM = Disk Drive Module
1 Array Site = 4 DDMs
Array Site
Two Array Sites
1 Raid Array = 4 DDMs
DS6000: Four DDM Arrays (Not at GA)
Student Notebook
Figure 2-19. Arrays: Eight DDM Arrays On Loop for DS6000 SS481.0
Notes:
...
...
DA DA
(Device
Adapter)
(Device
Adapter)
Array Site Two Array Sites
DDMs
1 Array Site = 4 DDMs
Array Site
TwoArray Sites
1 Raid Array = 8 DDMs
Arrays: Eight DDM Arrays On Loop for DS6000
Student Notebook
V3.1.0.1
Uempty
Figure 2-20. Two Array Sites Configurations: DS6000 Eight DDMs/Array with Arrays on Loop SS481.0
Notes:
2 Array Sites
RAID 5
6 + P + S
7 + P
RAID 10
3x2 + 2S
4x2
D D D D D
D
D
D
D D D D
A B C D a b c d
A B C S a b c S
3x2 + 2S
4x2
A B C D E F G S A B C D E F G H
7 + P
6 + P + S
D D D D
Two Array Sites Configurations: DS6000
Eight DDMs/Array with Arrays on Loop
Student Notebook
Figure 2-21. One Array Site Configurations: DS6000 (After GA) Four DDMs/Array with Arrays on Loop SS481.0
Notes:
1 Array Site
RAID 5
2 + P + S
3 + P
RAID 10
2 x 2
RAID 1*
1 x 2 + 2S
D D D D
A B a b
2 x 2
A B C S
A B C D
3 + P 2 + P + S
D D D D
A a S S
1 x 2 + 2S
* Only created by the microcode when spares are required
and is still treated as a RAID 10, that is, this is not a
RAID option for the user
One Array Site Configurations: DS6000 (After
GA) Four DDMs/Array with Arrays on Loop
Student Notebook
V3.1.0.1
Uempty
Figure 2-22. Sparing Rules (DS6000) SS481.0
Notes:
Array Sites have attributes of
Capacity
RPM
A minimum of one spare is required for each Array Site defined
until the following conditions are met
Minimum of four spares per DA pair1 spare per Dpair(dual)nterface
Minimum two spares of the largest capacity Array Site on the DA
pair1 spare per DA pair (dual) interface
Order of installation will influence the number of spares
Sparing Rules (DS6000)
Student Notebook
Notes:
DA
1
6 + P
7 + P
2
6 + P
7 + P
Server Enclosure
DA
1
6 + P
7 + P
2
6 + P
7 + P
Exp Enclosure 1 Exp Enclosure 3

Exp Enclosure 2
Assumes all devices same capacity and same rpm
On a DS6800 there are up to two spares on each loop
Additional RAID arrays have no spare (RAID 5: 7+P, RAID 10: 4 x 2)
All spares available to all arrays on the fabric
Student Notebook
V3.1.0.1
Uempty
Notes:
DA
DA
1
3 x 2
4 x 2
2
4 x 2
4 x 2
Server Enclosure
1
3 x 2
4 x 2
2
4 x 2
4 x 2
Exp Enclosure 1 Exp Enclosure 3

Exp Enclosure 2
On a DS6800 there are up to two spares on each loop
Additional RAID arrays have no spare (RAID 5: 7+P, RAID 10: 4 x 2)
All spares available to all arrays on the loop
Student Notebook
Figure 2-25. Sparing Example 3 - RAID 5: DS6000 All Same RPM SS481.0
Notes:
DA DA
1
6 + P 6 + P
2
6 + P 6 + P
Server Enclosure (146 GB)

1
6 + P
6 + P
2
6 + P
6 + P
Exp Enclosure 1 (146 GB) Exp Enclosure 3 (300 GB)

Exp Enclosure 2 (300 GB)
1
1
2
2
Assumes all devices same rpm
Minimum two spares of the largest capacity Array Site on each loop
First two enclosures (server and Exp 1) needs two spare disks each
And next two enclosures (Exp2 and Exp3) also needs two spare disks each
(because of larger capacity)
If installation sequence is reversed, next two enclosures does not need spare disks
All Same RPM
Student Notebook
V3.1.0.1
Uempty
Figure 2-26. Sparing Example 4 RAID 5: DS6000 Different Size and RPM SS481.0
Notes:
DA
DA
1
6 + P 6 + P
2
6 + P 6 + P
Server Enclosure (146 GB)

1
6 + P
6 + P
2
6 + P
6 + P
Exp Enclosure 1 (146 GB) Exp Enclosure 3 (73 GB)

Exp Enclosure 2 (73 GB)
1
1
2
2
Minimum two spares of the largest capacity Array Site on each loop
First two enclosures (server and Exp 1) needs two spare disks each
And next two enclosures (Exp2 and Exp3) also needs two spare disks each
(because of faster rpm)
Even if installation sequence is reversed, next two enclosures need spare disks
(because of larger capacity)
Different Size and RPM
(First two arrays 145 GB (10,000 RPM) and next two arrays 73 GB
(15,000 RPM)
Student Notebook
Figure 2-27. Capacity Magic SS481.0
Notes:
Capacity magic provides a
graphical interface to easily
configure more complex
configurations with multiple
storage requirements
Capacity Magic
Student Notebook
V3.1.0.1
Uempty
Figure 2-28. Floating Spare Rules (DS6000 and DS8000) SS481.0
Notes:
The DS microcode may choose to allow the hot spare to remain where it has been moved,
but it may instead choose to move the spare to a more optimum position. This is done to
better balance the spares across the DA pairs and enclosures. It may be preferable that a
DDM that is currently in use as an array member, be converted to a spare:
A smart process may be used to ensure that the larger or higher RPM DDMs act as
spares. This is preferable because if we were to rebuild the contents of a 73 GB DDM
onto a 146 GB DDM, then approximately half of the 146 GB DDM would be wasted
since that space is not needed. The problem here is that the failed 73 GB DDM is
replaced with a new 73 GB DDM. So the DS microcode most likely migrates the data on
the 146 GB DDM onto the recently replaced 73 GB DDM. When this process
completes, the 73 GB DDM rejoins the array and the 146 GB becomes the spare again.
If we fail a 10,000 RPM DDM onto a 15,000 RPM DDM. While this means that the data
has now moved to a faster DDM, the replacement DDM is the same as the failed DDM.
This means the spare is now a 10,000 RPM DDM. This could result in a 15,000 RPM
DDM being spared onto a 10,000 RPM DDM. This is not desirable. Again a smart
The DS6000 and DS8000 implement a smart floating technique for
spare DDMs. When a spare floats, this means that when a DDM fails
and the data it contained is rebuilt onto a spare, then the disk is
replaced, and the replacement disk becomes the spare. The data is
not copied back to the original position which the failed DDM.
The DS microcode may choose to allow the hot spare to remain where
it has been moved, but it may instead choose to move the spare to a
more optimum position. This is done to better balance the spares
across the DA pairs and enclosures. It may be preferable that a DDM
that is currently in use as an array member be converted to a spare.
Floating Spare Rules (DS6000 and DS8000)
Student Notebook
failback of the spare is performed once a suitable replacement DDM has been made
available.
Student Notebook
V3.1.0.1
Uempty
Figure 2-29. DS8000/DS6000: Forming a Rank (Example, FB with 1 GB Extents) SS481.0
Notes:
Process of forming a rank:
The array is formatted for either FB (open systems) or CKD (zSeries) data. This determines
the size of the set of data contained on one disk within a stripe on the array.
The capacity of the array is subdivided into equal sized partitions, called extents. The
extent size depends on the extent type, FB or CKD
CKD rank: 1 3390-1 (1113 cyl)
FB rank: 1 binary GB
One extent is the minimum physical allocation unit when a LUN or CKD volume is created.
However, if the defined capacity is not an integral multiple of the capacity of one extent, the
unused capacity in the last extent is wasted. For instance, on a 1 cylinder CKD volume
definition, 1113 cylinders (1 extent) are allocated and 1112 cylinders would be wasted.
When a new rank is defined, its name is chosen
by the DS Storage Manager
For example: R1, R2, or R3, and so on
You have to add an array to a rank
In the current DS8000 implementation, a rank
is built using just one array
Process of forming a rank:
The array is formatted for either FB (open
systems) or CKD (zSeries) data. This
determines the size of the set of data
contained on one disk within a stripe on the
array.
The capacity of the array is subdivided into
equal sized partitions, called extents. The
extent size depends on the extent type, FB or
CKD
CKD rank: 1 3390-1 (1113 cyl)
FB rank: 1 binary GB
One extent is the minimum physical allocation
unit when a LUN or CKD volume is created
However, if the defined capacity is not an
integral multiple of the capacity of one extent,
the unused capacity in the last extent is
wasted
For instance, on a 1 cylinder CKD volume
definition, 1113 cylinders (1 extent) is
allocated and 1112 cylinders would be wasted
FB Rank
of 1GB
extents
Creation of
a Rank
D1 D7 D13 ...
D2 D8 D14 ...
D3 D9 D15 ...
D4 D10 D16 ...
D5 D11 P ...
D6 P D17 ...
P D12 D18 ...
RAID
Array
Spare
Data
Data
Data
Data
Data
Data
Parity
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
1GB 1GB 1GB 1GB
DS8000 / DS6000: Forming a Rank
(Example: FB with 1 GB Extents)
Student Notebook
Figure 2-30. DS6000/DS8000 Extent Pool Concept Summary SS481.0
Notes:
An extent pool is a logical construct to aggregate the extents from a set of ranks to form a domain for
extent allocation to a logical volume
Same RAID type and the same disk RPM characteristics
So that the extents in the extent pool have homogeneous characteristics
No predefined affinity of ranks or arrays to a storage server
The affinity of the rank (and it's associated array) to a given server is determined at the
point it is assigned to an extent pool
When assigned to extent pools ranks are organized in two rank groups:
Rank group 0 is controlled by server 0
Rank group 1 is controlled by server 1
One or more ranks with the same extent type can be assigned to an extent pool
One rank can be assigned to only one extent pool.
There can be as many extent pools as there are ranks.
At least two extent pools (one per server to balance the activity) of each type
CKD or FB
Additional extent pools may be used to segregate ranks with different DDM types
One Extent pool per rank (recommendation)
Extent Pool
DS6000/DS8000 Extent
Pool Concept Summary
Student Notebook
V3.1.0.1
Uempty
Figure 2-31. Device Configuration Extent SS481.0
Notes:
CKD
FB CKD Extent pools
Ranks
Arrays
RAID5
15K rpm
RAID5
15k rpm
RAID10
15k rpm
RAID5
10k rpm
RAID5
10k rpm
Array Sites
Rank group 0 associated
with Server 0 Rank group 0 associated
with server 0
Multiple ranks allowed per extent pool
Post GA can have multiple
arrays per rank
Device Configuration Extent
Student Notebook
Figure 2-32. Extents / Extent Pools Example SS481.0
Notes:
CKD
FB
Extent Pools
Ranks
73 GB 10k
FB Extent =1 GB
16 K logical tracks
CKD Extent = 3390 mod 1 (.94 GB)
16,695 logical tracks (1113 cylinders)
Extents
73 GB 10k 146 GB 10k
Extents / Extent Pools Example
Student Notebook
V3.1.0.1
Uempty
Figure 2-33. Extent Pools Example in a Mixed CKD and FB Environment SS481.0
Notes:
1GB
FB
1GB
FB
1GB
FB
1GB
FB
S
e
r
v
e
r
0
1113
Cyl.
CKD
1113
Cyl.
CKD
1113
Cyl.
CKD
1113
Cyl.
CKD
S
e
r
v
e
r
1
1113
Cyl.
CKD
1113
Cyl.
CKD
1113
Cyl.
CKD
1113
Cyl.
CKD
Extent Pool CKD0 Extent Pool CKD1
Extent Pool FBtest
Extent Pool FBprod
1113
Cyl.
CKD
1113
Cyl.
CKD
1113
Cyl.
CKD
1113
Cyl.
CKD
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
1GB
FB
Extent Pools Example in a
Mixed CKD and FB Environment
Student Notebook
Figure 2-34. Logical Volume Concept (1 of 2) SS481.0
Notes:
Made up of an ordered set of extents from one extent
pool
Min size: 1 extent 1 GB(FB) Mod1(CKD)
Max size: 2 TB(FB) 56 GB(CKD)
Can span more than 1 rank if more than 1 rank in pool
Max total number of volumes (CKD + FB)
DS6000: 8192
DS8000: 65280
Can be individually deleted
Assigned to Volume Group
CKD FB
Ranks
73 GB
10k
Extents
73 GB
10k
146 GB
10k
Extent Pools
Logical Volume Concept (1 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 2-35. Logical Volume Concept (2 of 2) SS481.0
Notes:
Current algorithm uses available extents within one rank
Unless there are not enough free extents available in that rank but free
extents exist within another rank of the same extent pool.
Unused and allocated tracks cannot be used by any other logical
volume
For CKD use a 1113 (or better: 3339) multiple of cylinders to avoid waste
Defined volumes can be dynamically removed and redefined with
different size without affecting any other logical volume
Unallocated (removed) extents become unallocated extents in that extent
pool and are immediately available for reuse as required after cleaning
Cleaning is a background process
Statement Of Direction for dynamic expansion, online data relocation,
virtual capacity over provisioning, space efficient FlashCopy requiring
minimal reserved target capacity
Logical Volume Concept (2 of 2)
Student Notebook
Figure 2-36. Virtualization Benefits SS481.0
Notes:
Unlike the current systems where all of the storage associated with a LUN or volume must
contiguously reside in a singe RAID rank, in the new systems, storage for the LUNs and
volumes are allocated in units of 1 GB of space. A 32 GB LUN would be made up of 32 of
these units. There is no requirement that the units all reside next to one another in a RAID
rank. They can even reside on different RAID ranks. This new approach makes several
new features possible.
A volume or LUN can be striped across even more disks as well as for the first time, more
RAID adapters, providing more performance and more skew balancing than ever before.
We can now delete a LUN or volume and reclaim the space without affecting the other
LUNs or volumes on the same RAID ranks.
In the future, this approach allows us to:
Expand existing LUNs
Take a FlashCopy of a LUN or Volume without have to dedicate enough storage to hold
the full copy. This is known as space efficient FlashCopy.
Extent Pools
Physical storage is abstracted from the user
Capacity from RAID Arrays are virtualized into
discrete blocks of storage, Extents
Pools can be customizable by
Disks
Drive speeds performance
Capacity size
RAID level for performance
Performance
Utilization
Volume/LUN flexibility
Are formed by joining extents available from
an Extent Pool
LUN sizes are not limited by Array size
LUNs can be larger than array sizes
Data Protection
Eliminates data loss during array and LUN
expansion activities (SOD)
Does not require complex procedures to
reconfigure Arrays/Disk Groups to grow LUNs
beyond the constraints of a single array/disk
group (SOD)
RAID 5 Array
RAID 5 Array
RAID 10 Array
RAID 10 Array
RAID 5 Extent Pool
RAID 10 Extent Pool
Physical Configuration
RAID 5 Extent Pool
RAID 10 Extent Pool
LUN 1 (RAID 5)
LUN 2 (RAID 5)
LUN 3 (RAID 5)
LUN 4 (RAID 10)
LUN 5 (RAID 10)
LUN 6 (RAID 10)
Logical Configuration
Virtualization Benefits
Student Notebook
V3.1.0.1
Uempty
Enable over-provisioning. In over-provisioning, the storage administrator will allocate
say, 100 GB LUNs to each of 100 users (10 TB total), knowing that although each user
asked for 100 GBs, most use only a fraction of the space. In the storage system,
although each LUN appears as being 100 GB to the host, only a few GB (say 2 GB) are
allocated to each of the LUNs. As the individual user's demands grow beyond the 2 GB,
the system automatically expands the LUN by adding another 1 GB unit of space. In
this way, the system administrator can meet the actual user needs for storage with a
much smaller amount of real storage and do so without having to have detailed
knowledge, both on his part and his users part of actual requirements.
As far as RAID is concerned, we still support RAID 5 and RAID 10 with RAID ranks of 7+P,
6+P+S for RAID 5 and 4x4 and 3x3+2S for RAID 10 in the DS8000 and DS6000. Post GA
we also support RAID ranks based on four drives rather than eight for the DS6000 (for
example, 3+P and 2x2). Unlike the Shark where arrays across loops is an option, in the
DS8000 and DS6000, a given RAID rank is striped across all four ports of the RAID
adapter. (Remember, as discussed above, a LUN can be striped across multiple RAID
ranks and adapters as well.
Student Notebook
Figure 2-37. Hosts SS481.0
Notes:
HBAs are identified to the DS8000 in a host attachment construct that specifies the HBAs
World Wide Port Names (WWPNs). A set of host ports can be associated through a port
group attribute that allows a set of HBAs to be managed collectively. This port group is
referred to as host attachment within the GUI.
A given host attachment can be associated with only one volume group. Each host
attachment can be associated with a volume group to define which LUNs that HBA is
allowed to access. Multiple host attachments can share the same volume group. The host
attachment may also specify a port mask that controls which DS8000 I/O ports the HBA is
allowed to log in to. Whichever ports the HBA logs in on, it sees the same volume group
that is defined in the host attachment associated with this HBA.
The maximum number of host attachments on a DS8000 is 8192.
Multiple server ports can be specified (in one or
more groups) in one host definition
Four host attachments are shown in example on
top
Two host attachments with two ports each are
shown in example in middle
One host attachment with four ports is shown in
example on bottom
Recommend grouping all ports for a server for
convenience
Specific host attachment can be in only one
volume group
Host attachments can access specific disk
subsystem I/O ports or all valid I/O ports
Recommend allowing access to all valid disk
subsystem I/O ports for convenience
Replace Access control by host by port for
ESS
pSeries1
pSeries1
pSeries1
Hosts
Student Notebook
V3.1.0.1
Uempty
Figure 2-38. I/O Ports (1 of 2) SS481.0
Notes:
The DS8000 supports ESCON or Fibre Channel cards, ESCON cards have two ports per
card. Fibre Channel cards have four ports each and can be configured for FICON or FCP.
Ports are configured independently and each port can be either FCP or FICON.
ESCON ports (DS8000)
Two per adapter
Note: ESCON is limited to 16 LSSs
FCP/FICON capable ports
Each of the four ports on one DS8000
adapter or one DS6000 controller card can
be either FCP or FICON
No independent configuration step required
Ports initially defined as FC-SW
FICON ports will be configured automatically
based on FICON host definition
Hosts must access an adapter on each
server on DS6000 for availability
Storage
Enclosure
I/O Drawer
RIO 1
I/O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/O Drawer
RIO 0
I/O Drawer
RIO 0
I/O Ports (1 of 2)
Student Notebook
Figure 2-39. I/O Ports (2 of 2) SS481.0
Notes:
The DS8000 has several models. The Model 921 has four I/O enclosures and 16 FC cards
so 64 FCP/FICON ports are available. If ESCON cards are installed, since they only have
two ports per card there are 32 ESCON ports available.
The Model 922 has 8 I/O enclosures and 32 FC cards so 128 FCP/FICON ports are
available. If ESCON cards are installed, since they only have two ports per card there are
64 ESCON ports available.
The DS6000 has eight FCP/FICON ports and does not support ESCON.
Maximum number of ports
DS8000 921
64 FCP/FICON
32 ESCON
DS8000 922
128 FCP/FICON
64 ESCON
DS6000
8 FCP/FICON
Maximum number of logins
DS8000 -- 509 per port, 8,000 total
DS6800 -- 256 Per port, 1,000 total
Storage
Enclosure
I/O Drawer
RIO 1
I/O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/O Drawer
RIO 0
I/O Drawer
RIO 0
I/O Ports (2 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 2-40. Volume Groups SS481.0
Notes:
A volume group is a named construct that defines a set of logical volumes. When used in
conjunction with CKD hosts, there is a default volume group that contains all CKD volumes
and any CKD host that logs into a FICON I/O port has access to the volumes in this volume
group. CKD logical volumes are automatically added to this volume group when they are
created and automatically removed from this volume group when they are deleted.
When used in conjunction with Open Systems hosts, a host attachment object that
identifies the HBA is linked to a specific volume group. The user must define the volume
group by indicating which fixed block logical volumes are to be placed in the volume group.
Logical volumes may be added to or removed from any volume group dynamically.
There are two types of volume groups used with Open Systems hosts and the type
determines how the logical volume number is converted to a host addressable LUN_ID on
the Fibre Channel SCSI interface. A map volume group type is used in conjunction with FC
SCSI.
Maps LUNs to server ports or port groups
FB LUN masking
LUN masking at VG level, not LUN level
Specific host attachment can be in only one
volume group
Options for shared access
Place hosts in separate volume groups and
shared volumes in multiple volume groups
Place shared volumes and multiple hosts in
single volume group
One Host port/port group can be member
of one volume group
One Volume can be member of more than
one volume group
More than one host (even different open
systems server types) can be member of
one volume group
Maximum number of volume groups
DS8000: 8320
DS6000: 1040
AIX host port
iSeries host
port group
AIX host port
FB
FB
FB (i)
FB
FB
FB
Volume Groups
Student Notebook
Figure 2-41. Volume Groups and Host Attachment (1 of 2) SS481.0
Notes:
The rules say that a host attachment can only be in one volume group. So, in the left
example, the host attachment is accessing Volume Group X so it can not be part of VG Y.
All the volumes that need to access Host A must be in the same group.
Specific host attachment can be in only one volume group
Host attachment
Server A
Volume Group X
1
2
3
Volume Group Y
4
5
6
Host attachment
Server A
Volume Group X
1
2
3
4
5
6
Volume Groups and Host Attachment (1 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 2-42. Volume Groups and Host Attachment (2 of 2) SS481.0
Notes:
The rules say that more than one host attachment can be in one volume group. So, in the
left example, the host attachment is accessing Volume Group X, and Host B is accessing
Volume Group Y or you can one volume group and have both hosts access it. So, volumes
can be in more than one volume group.
Options for shared access
Place hosts in separate volume groups and shared volumes in multiple
volume groups
Place shared volumes and multiple hosts in single volume group
Host attachment
Server A
Volume Group X
1
2
3
Host attachment
Server B
Volume Group X
1
2
3
Host attachment
Server B
Volume Group Y
1
2
3
Host attachment
Server A
OR
Volume Groups and Host Attachment (2 of 2)
Student Notebook
Figure 2-43. Hosts and Volume Groups SS481.0
Notes:
As long as the rules about hosts only being part of one volume group are being followed
there is no reason why the volume groups can not overlap. Here Host System A has
attachment to Volume Group 1 and 2 and Host System B has attachment to Volume Group
3, even though Volume Groups 2 and 3 overlap, this attachment is allowed.
Specific host attachment can be in only one volume group
Multiple hosts (even different open systems host types) can be
in one volume group, but recommend one host per volume
group for convenience
If shared access to volumes is required, put the shared volumes
into multiple volume groups (for example, LUN 1 below)
xSeries2
Volume Group 2
1
pSeries1
Volume Group 1
1
Hosts and Volume Groups
Student Notebook
V3.1.0.1
Uempty 2.2 Logical Configuration Concepts
Student Notebook
Figure 2-44. Topic: Logical Configuration Concepts SS481.0
Notes:
Array Site
Array
Rank
Extent Pool
Logical Volume
Volume Group
Host Attachment
Logical Configuration Concepts: Definitions
Storage-Plex, Storage Facility Image
Address Group
LSS / LCU
Logical Device
Topic: Logical Configuration Concepts
Student Notebook
V3.1.0.1
Uempty
Figure 2-45. Physical Infrastructure Hierarchy SS481.0
Notes:
Storage Complex
One or multiple physical
storage subsystems
Central management point
Storage Unit (Storage facility)
Single physical storage
subsystem
Storage Image (DS8000)
Single logical storage
subsystem
LPAR System
Disks
I / O Drawer
RI O 1
I / O Drawer
RI O 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I / O Drawer
RI O 0
I / O Drawer
RI O 0
Shark
I mage 0
(LPAR 0)
Shark
I mage 0
(LPAR 0)
Shark
I mage 1
(LPAR 1)
Shark
I mage 1
(LPAR 1)
Storage
Enclosure
I/O Drawer
RIO 1
I /O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I /O Drawer
RIO 0
I/O Drawer
RIO 0
or
Single LPAR
Resources
LPAR System
Disks
I/O Drawer
RIO 1
I/O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/O Drawer
RIO 0
I/O Drawer
RIO 0
Shark
Image 0
(LPAR 0)
Shark
Image 0
(LPAR 0)
Shark
Image 1
(LPAR 1)
Shark
Image 1
(LPAR 1)
LPAR System
Disks
I/O Drawer
RIO 1
I/O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/O Drawer
RIO 0
I/O Drawer
RIO 0
Shark
Image 0
(LPAR 0)
Shark
Image 0
(LPAR 0)
Shark
Image 1
(LPAR 1)
Shark
Image 1
(LPAR 1)
LPARSystem
Disks
I/ODrawer
RIO1
I/ODrawer
RIO1
CEC1
CEC0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/ODrawer
RIO0
I/ODrawer
RIO0
Shark
Image0
(LPAR0)
Shark
Image0
(LPAR0)
Shark
Image1
(LPAR1)
Shark
Image1
(LPAR1)
Physical Infrastructure Hierarchy
Student Notebook
Figure 2-46. LSS / LCU SS481.0
Notes:
The LSS and LCU are basically the same. In the mainframe the LSS of the ESS or DS8000
maps one to one with the LCU or Logical Control Unit of the 3990-6. Each LCU can have
256 addresses and in the ESS you were limited to 16 LCUs. The DS8000 now has 255
LSSs so you could define 255 LCUs giving the user a much larger pool of addresses
available.
For Open System we also have 255 LSSs if not used by the Mainframe. One restriction is
that once a CKD volume is defined in a address group of 16 LCUs then all LSSs in that
address group have to be used for CKD volumes. Likewise, if a FB volume is created in a
LSS, all volumes in that LSS and the other 15 LSSs in that address group must be FB
LUNs.
Logical grouping of volumes
Maximum of 256 volumes in
LSS
LSS configured as either FB
or CKD
CKD during LCU
creation
FB during volume
creation
Predetermined association
with Server0 or Server1
Even LSSs associated
with Server0
Odd LSSs associated with
Server1
Determines addressing,
address group, and PAVs
Used for copy services
PPRC paths and consistency
group properties/timeouts
LSS X'17'
DB2
LSS X'18'
DB2-test
Physical Drives Logical Volumes Physical Drives
x'1703'
x'1701'
x'1702'
x'1801'
x'1800'
LSS / LCU
Student Notebook
V3.1.0.1
Uempty
Figure 2-47. LSS Groups and LSS Domain SS481.0
Notes:
LSS Domain
1-256 devices
One LSS can be less than one Array Site to multiple Array Sites
Extents from multiple array sites
Multiple LSSs are allowed per Array Site
There are two LSS Groups
LSS Group 0
contains all even LSSs
LSS Group 1
contains all odd LSSs
Associated with each LSS Group
LSS Group 0
DA Group 0 -- device adapters managed by Server 0 (one DA from each pair of
DAs)
Rank Group 0 -- ranks managed by device adapters in DA Group 0
LSS Group 1
Rank Group 1 -- ranks managed by device adapters in DA Group 1
DA Group 1 -- device adapters managed by Server 1 (one DA from each pair of
DAs)
LSS Groups and LSS Domain
Student Notebook
Figure 2-48. LSS SS481.0
Notes:
A logical subsystem (LSS) is another logical construct. It groups logical volumes, LUNs, in
groups of up to 256 logical volumes.
On an ESS there was a fixed association between logical subsystems (and their
associated logical volumes) and device adapters (and their associated ranks). The
association of an 8-pack to a device adapter determined what LSS numbers could be
chosen for a volume. On an ESS up to 16 LSSs could be defined depending on the
physical configuration of device adapters and arrays.
On the DS8000, there is no fixed binding between any rank and any logical subsystem.
The capacity of one or more ranks can be aggregated into an extent pool and logical
volumes configured in that extent pool are not bound to any specific rank. Different logical
volumes on the same logical subsystem can be configured in different extent pools.
No predetermined relation to physical ranks
No predetermined relation to extent pools
(except even / odd)
One LSS can contain volumes from different extent pools (even/odd)
One extent pool can contain volumes that are in different LSSs
But from same LSS group (even or odd)
Many-many relationship
One LCU can contain CKD volumes of different types (3390 M3s
and M9s
Ext Pool 6 > Server 0 Ext Pool 3 > Server 1
Rank3
Ext Pool 5 > Server 1
LSS
2
2
1
3
7
4
1
2
2
2
1
3
7
4
1
2
2
3
1
0
7
5
0
1
2
3
1
0
7
5
0
1
Rank1
2
3
1
1
7
5
0
2
2
3
1
1
7
5
0
2
Rank2
Student Notebook
V3.1.0.1
Uempty
Figure 2-49. Address Group (1 of 2) SS481.0
Notes:
Address groups are created automatically when the first LSS associated with the address
group is created, and deleted automatically when the last LSS in the address group is
deleted.
LSSs are either CKD LSSs or FB LSSs. All devices in an LSS must be either CKD or FB.
This restriction goes even further. LSSs are grouped into address groups of 16 LSSs. LSSs
are numbered x'ab', where a is the address group and b denotes an LSS within the address
group. So, for example x'10' to x'1F' are LSSs in address group 1.
All LSSs within one address group have to be of the same type, CKD or FB. The first LSS
defined in an address group fixes the type of that address group.
zSeries clients that still want to use ESCON to attach hosts to the DS8000 should be aware
of the fact that ESCON supports only the 16 LSSs of address group 0 (LSS x'00' to x'0F').
Therefore, this address group should be reserved for ESCON-attached CKD devices, in
this case, and not used as FB LSSs.
At GA one Storage Facility can have up to eight
Address Groups (DS8000)
Post GA this is increased to 16 Address Groups
Address Groups are number from X'0' to X'7' (at
GA)
Will be X'0' to X'F' at sometime after initial GA (this is the
architected limit)
Each Address Group has up to 16 Logical
Subsystems
Logical Subsystems are numbered according to the parent
Address Group
X'a0' to X'aF', where a = Address Group number, that is, X'0' to X'7'
Each Logical Subsystem can have up to 256
devices
As in the past, Parallel Access Devices also count towards this
256 maximum
(255 LSSs) * (256 logical devices) = 65280
An entire Address Group (all 16 LSSs) will be either FB
or CKD
16 LSSs * 256 logical volumes = 4,000 logical volumes
Either all CKD logical Volumes or all FB logical volumes
DS6000 Two Address Groups
8,000 logical volumes
Address Group
LSS a0 LSS aF
...
... ...
00 00 FF FF
a = Address Group number
Address Group range:
X'0' to X'7' (GA)
X'0' to X'F' (post GA)
Volumes
Volumes
Address Group (1 of 2)
Student Notebook
Figure 2-50. Address Group (2 of 2) SS481.0
Notes:
The chart above shows the concept of LSSs and address groups. The LUN identifications
x'gabb' are composed of the address group x'g', and the LSS number within the address
group x'a, and the position of the LUN within the LSS x'bb'. For example, LUN x'2101'
denotes the second (x'01') LUN in LSS x'21' of address group 2.
LSSs numbers are pre-grouped in groups of 16 to make up an address group
LSS 00-0F, 10-1F, 20-2F, etc.
Entire address group (all 16 LSSs) will be either FB or CKD
Volume 1E01 belongs to LSS E of Address Group 1
Address group X'2x': FB
Address group X'1x' CKD
Extent Pool FB-2
LSS X'10'
LSS X'12'
LSS X'14'
LSS X'16'
LSS X'18'
LSS X'1A'
LSS X'1C'
LSS X'1E'
LSS X'20'
LSS X'22'
LSS X'24'
LSS X'26'
LSS X'28'
LSS X'2A'
LSS X'2C'
LSS X'2E'
LSS X'11'
LSS X'13'
LSS X'15'
LSS X'17'
LSS X'19'
LSS X'1B'
LSS X'1D'
LSS X'21'
LSS X'1F'
LSS X'23'
LSS X'25'
LSS X'27'
LSS X'29'
LSS X'2B'
S
e
r
v
e
r
0
Extent Pool CKD-1
Rank-a
Rank-b
Extent Pool FB-1
Rank-c
Rank-d
LSS X'2D'
S
e
r
v
e
r
1
Extent Pool CKD-2
Rank-w
Rank-x
Extent Pool FB-2
Rank-y
Rank-z
X'1E00'
X'1E01'
X'2800'
X'1500'
X'1D00'
X'2100'
Volume ID
X'2101'
LSS X'2F'
Address Group (2 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 2-51. LSS and Address Group Considerations SS481.0
Notes:
The number of LSSs or LCU has been expanded in the DS8000. Each Address Group is a
set of 16 LSSs and 4096 volume addresses. An entire address group must be either CKD
or FB. Defining a single volume to an address group sets the entire group to that type.
Address group assignment is not explicitly configured
LSSs are pre-grouped into address groups
One address group has 4096 addresses
LSS definition results in address group assignment
CKD LCU creation
FB volume creation
Creation of first LCU (or first FB volume on first LSS to be configured) in
address group determines whether all 16 LCUs/LSSs in address group are
CKD (or all 16 are FB)
First LCU/LSS created is not necessarily lowest-numbered
If no LSSs/LCUs existed in address group 2 (LSSs 20-2F) and if FB
volume 2310 was created, LSS 23 would be FB and address group 2
(LSSs 20-2F) would be FB
If no LSSs/LCUs existed in address group 2 and LCU 23 was created,
address group 2 (LSSs 20-2F) would be CKD
ESCON attachments must use address group 0 (LSSs 00-0F)
LSS and Address Group Considerations
Student Notebook
Figure 2-52. Logical Addressing SS481.0
Notes:
The chart above is the complete addressing range for the DS8000. The only restrictions
are that address group zero is the only one that can be used for ESCON attached volumes
for mainframe hosts and the last address group XF only has 15 LSSs and the last LSS
XFF is reserved and can not be used for volume addressing.
Logical Addressing
Address Group Logical Subsystems Volume Addresses Number of Addresses
X'0' x'00-0F' X'0000-0FFF' 4096
X'1' x'10-1F' X'1000-1FFFF' 4096
X'2' x'20-2F' X'2000-2FFF' 4096
X'3 x'30-3F' X'3000-3FFF' 4096
X'4' x'40-4F' X'4000-4FFF' 4096
X'5' x'50-5F' X'5000-5FFF' 4096
X'6' x'60-6F' X'6000-6FFF' 4096
X'7' x'70-7F' X'7000-7FFF' 4096
X'8' x'80-8F' X'8000-8FFF' 4096
X'9' x'90-9F' X'9000-9FFF' 4096
X'A' x'A0-AF' X'A000-AFFF' 4096
X'B' x'B0-BF' X'B000-BFFF' 4096
X'C' x'C0-CF' X'C000-CFFF' 4096
X'D' x'D0-DF' X'D000-DFFF' 4096
X'E' x'E0-EF' X'E000-EFFF' 4096
X'F' x'F0-FE' X'F000-FEFF' 3840
-------------
Total Addresses 65280
LSS X'FF' reserved for system internal use.
DS8000 allows 255 LSSs, 255 X 256 = 65280
Student Notebook
V3.1.0.1
Uempty
Figure 2-53. Device Configuration SS481.0
Notes:
The addressing for the DS8000 allows for more flexibility and means that volumes in an
LSS or LCU can exist in more than one Extent Pool and be spread around in the arrays and
ranks of the DS8000 storage, unlike the ESS where all the volumes in an LCU or LSS were
associated with a DA and therefore limited to the arrays connected to that DA. If a user
wants to have a contiguous set of addresses for a application, but would like those volumes
to be spread around on different arrays and accessed by different DA pairs and different
servers, this is now possible.
Logical devices
LSS
CKD FB CKD
Extent pools
Address group
00 02
CKD address group FB Address group
10 12
LSS group 0
Device extents taken from single extent pool
Devices in LSS can be from
multiple extent pools
Extent pool can contain devices
from multiple LSS
FB and CKD devices use
different extent pools
Device Configuration
Student Notebook
Figure 2-54. Logical Configuration Overview SS481.0
Notes:
CKD FB CKD Extent pools
Ranks
Logical devices
Rank group 0 Rank group 1
00 01
address group 0 - CKD
11
LSS
address group 1 - FB
22
address group 2 - CKD
Address groups
LSS group 0
LSS group 1
Logical Configuration Overview
Student Notebook
V3.1.0.1
Uempty
Figure 2-55. Virtualization Hierarchy SS481.0
Notes:
OK, here is the order we do things.
S
e
r
v
e
r
0
Array
Site
RAID
Array
Spare
Data
Data
Data
Data
Data
Data
Parity
Rank
Type FB
1

G
B

F
B
1

G
B

F
B
1

G
B

F
B
1

G
B

F
B
1

G
B

F
B
1

G
B

F
B
1

G
B

F
B
1

G
B

F
B
1

G
B

F
B
Extent
Pool
Logical
Volume
LSS
FB
Address
Group
X'2x' FB
4096
addresses
LSS X'27'
X'3x' CKD
4096
addresses
Volume
Group
Host
Attachment
Virtualization Hierarchy
Student Notebook
Figure 2-56. Extent Pools (1 of 4) SS481.0
Notes:
How should the extent pools be used? Extent pools are the basis for allocation of the
LUNs, so you can separate the disk resources by RAID type or speed or even application
requirements.
User-configured to be either CKD or
FB
Optionally could also be separated by
Device type (Size/speed of DDMs)
RAID type
Application
Contain one or more ranks divided into
fixed-size extents
CKD 3390 Mod1 (0.94 GB decimal)
FB 1 GB (binary)
Contain one or more LUNs/volumes
No fixed relationship between LSSs and ranks
Volumes on one rank in one pool can be in
multiple LSSs
Two LSSs in the example (LSS 23 and
LSS 75, both odd)
ALvv
A : Address group
AL: LSS Number
vv: Volume
Extent Pools (1 of 4)
2
3
1
0
7
5
0
1
Extent Pool 3
Rank1
2
3
1
0
7
5
0
1
2
3
1
0
7
5
0
1
Extent Pool 3
Rank1
Student Notebook
V3.1.0.1
Uempty
Notes:
The important thing about the extent pool is that this is where the server affinity is defined.
The ranks are assigned to an extent pool and thereby pick up the affinity to a server. All
volumes allocated from the extent pool are serviced by the Server which is associated with
the extent pool.
Extent pool is assigned to Server 0
or Server 1 during configuration
(server affinity)
By user during custom configuration
By algorithm during auto or express
configuration
Server1 in the example
Indicated by odd-numbered LSSs
Ranks inherit server affinity from extent
pool
2
3
1
0
7
5
0
1
Extent Pool 3
Rank1
2
3
1
0
7
5
0
1
2
3
1
0
7
5
0
1
Extent Pool 3
Rank1
Student Notebook
Notes:
The maximum number of extent pools you can have is the same as the number of ranks.
Maximum of n pools where n is the number
of ranks in subsystem
8 pools/8 ranks in the example
Minimum of two pools to utilize subsystem
Server 0 and Server 1
Balance ranks between servers
Two Configuration options
Each extent pool has only 1 rank
Provides user controlled performance
management
Requires balancing of activity across extent pools
More extent pools to manage
Multiple ranks in each extent pool
Provides easier space management
One rank per pool does not constrain addresses
Volumes on one rank in one pool can be in multiple LSSs
Volumes on different ranks in different pools can be in the same LSS (limited by odd/even server affinity)
Ext. Pool 5
Rank 5
Ext. Pool 1
Rank 1
Ext. Pool 3
Rank 3
Ext. Pool 7
Rank 7
Ext. Pool 4
Rank 4
Ext. Pool 0
Rank 0
Ext. Pool 2
Rank 2
Ext. Pool 6
Rank 6

Ext. Pool 5
Rank 5
Ext. Pool 1
Rank 1
Ext. Pool 3
Rank 3
Ext. Pool 7
Rank 7
Ext. Pool 4
Rank 4
Ext. Pool 0
Rank 0
Ext. Pool 2
Rank 2
Ext. Pool 6
Rank 6
Ext. Pool 5
Rank 5
Ext. Pool 5
Rank 5
Ext. Pool 1
Rank 1
Ext. Pool 1
Rank 1
Ext. Pool 3
Rank 3
Ext. Pool 3
Rank 3
Ext. Pool 7
Rank 7
Ext. Pool 7
Rank 7
Ext. Pool 4
Rank 4
Ext. Pool 4
Rank 4
Ext. Pool 0
Rank 0
Ext. Pool 0
Rank 0
Ext. Pool 2
Rank 2
Ext. Pool 2
Rank 2
Ext. Pool 6
Rank 6
Ext. Pool 6
Rank 6

Student Notebook
V3.1.0.1
Uempty
Notes:
New ranks can be added, but to remove a rank from a extent pool, no volumes can be
assigned to it.
Rank can be added to extent pool at any time
Rank can be removed from extent pool if no extents on rank
are currently assigned to LUNs/volumes
Volumes/LUNs do not stripe across all ranks in extent pool
Thresholds
Warning of space utilization
Reserve space option
Volumes cannot be created in reserved space until space is
explicitly released
Student Notebook
Figure 2-60. Volumes (1 of 3) SS481.0
Notes:
The only way that LUNs will span an extent pool is if the LUN size overflows the extent pool
and forces it to go the next array. Another mechanism for controlling that is the reserved
space parameter, which is used when the extent pool is created. If it is set fairly high then,
overflows to the next rank happen sooner.
One logical volume is made up of extents from one extent pool
Typically made up of extents from one rank unless LUN size is
larger than one rank
Volume/LUN not striped across all ranks in extent pool
A specific volume is in one LSS
Multiple volumes in one extent pool or on one rank can be in
the same or different LSSs
Multiple volumes in different extent pools and on different
ranks can be in the same LSS
Volumes (1 of 3)
2
3
1
0
7
5
0
1
Extent Pool 3
2
3
1
3
7
5
1
2
Extent Pool 5
2
3
1
0
7
5
0
1
Extent Pool 3
2
3
1
0
7
5
0
1
2
3
1
0
7
5
0
1
Extent Pool 3
2
3
1
3
7
5
1
2
Extent Pool 5
2
3
1
3
7
5
1
2
2
3
1
3
7
5
1
2
Extent Pool 5
Student Notebook
V3.1.0.1
Uempty
Notes:
This chart gives some guidelines on allocating volumes. There is some values which are
denied due to incompatibility with ESS volumes and PPRC concerns for use as source and
targets. A list of valid LUN sizes has been published.
Volumes/LUNs can be specified in binary GB, decimal GB or number of
blocks
Underlying allocation is 1 extent so potential for wasted space
Device size flexible, increased logical volume size:
Volume can be larger than one rank (if more than one rank in extent pool)
CKD -- Mod1 to 56 GB (65,536 cylinders, with appropriate software support)
FB -- 1 GB to 2 TB
iSeries (8.56, 17.54, 35.1, 70.56, 141.12, 282.25)
Recommend twice number of LUNs as DDMs (LUNsize = 1/2 DDMsize)
73 GB DDMs => 35.1 GB LUNs
Available capacity for logical volumes depends on
Spares
RAID type
Number of ranks
Extent allocation
Volume/LUN size efficiency
Volumes can be deleted and extents reused
Volumes (2 of 3)
Student Notebook
Notes:
This describes how volumes are created and associated with the LSS or LCU. LSSs are
associated with a server so even LSS are for server 0 and odd LSS for Server 1. If you
have an FB rank in an extent pool for Server 1 and you try to allocate an FB volume using
an even LSS number, this fails if there are no FB extent pools associated with server 0.
Associated with a single LSS association by address
For CKD, LSS created during LCU creation
For FB, LSS created (selected) during volume creation
Volume number 2E3B
Address Group 2
LSS 2E
Volume 3B
Maximum number of volumes/LUNs
DS8000 65280
DS6000 8192 (8192 max CKD if no FB; 8192 max FB if no CKD; 4096 max
CKD/4096 max FB if mixed)
Potentially member of multiple volume groups
For attachment to multiple systems
Nicknames generate sequence via alphabetic prefix and numeric suffix
Volumes (3 of 3)
Student Notebook
V3.1.0.1
Uempty
Figure 2-63. Volume Groups (1 of 4) SS481.0
Notes:
The volume group is how we perform LUN Masking for the DS8000. The Volume Group is
a combination of host attachment definition and a set of volumes to connect to the host.
There are some rules about volume groups which must be observed. A host attachment
can only be in one volume group, but volumes can be in more than one volume group and
even several volume groups at the same time.
FB LUN masking
Contains one or more LUNs and one or more host attachments
A specific host attachment can be in only one volume group
Attachments from multiple hosts (even different open systems
host types) are allowed in the same volume group
Recommend one host per volume group with shared LUNs in
multiple volume groups
Specific LUN can be in more than one volume group
Allows LUN sharing (for example, LUN1 in example below)
Volume Group 1 Volume Group 2
Volume Groups (1 of 4)
pSeries1
Volume Group 1
1
xSeries1
Volume Group 2
1
pSeries1
Volume Group 1
1
pSeries1
Volume Group 1
11
xSeries1
Volume Group 2
1
xSeries1
Volume Group 2
11
Student Notebook
Notes:
The volume groups define a host partition much like the DS4000 Storage manager does. It
allows one to place host ports and a set of volumes into a group that associates these
resources.
Volumes from different LSSs and different extent pools can be
in one volume group (Volume Group 1 below)
Volumes from the same LSS and/or same extent pool can be in
different volume groups (7512, 7515)
2
2
1
0
7
4
0
1
2
2
1
0
7
4
0
1
Extent Pool 4 Extent Pool 5
Volume Group 1
Volume Group 2
2
3
1
3
7
5
1
2
7
5
1
5
Student Notebook
V3.1.0.1
Uempty
Notes:
You can have multiple hosts in a volume group which facilitates HACMP or clustering. Also,
for sharing for SANFS user pool volumes.
Attachments from multiple hosts (even different open systems
host types) can be in the same volume group
Recommend one host per volume group with shared
volumes in multiple volume groups
Default volume groups are automatically created
All FB 512 (open systems) same addressing mode:
Mask Report LUNs (64,000 max)
Map 256 Poll LUNs (256 max)
All FB 520 (iSeries)
All CKD
Maximum of 8320 volume groups for DS8000 1040 DS6000
Student Notebook
Figure 2-66. DS6800 LSS Dual Pathed Host (Recommended) SS481.0
Notes:
It is recommended that multipath connections from the host be used for redundancy.
DS6800 LSS Dual Pathed Host
(Recommended)
Student Notebook
V3.1.0.1
Uempty
Notes:
The DS6000 does preferred path instead of multipath operations. SDD for DS6000 now
supports the preferred path operations.
Preferred Path implementation in DS6000
Performance benefit to minimizing cross-cluster communications
Systems which support preferred path can prioritize the use of the
preferred path.
For example SDD automatically detects the preferred path and
prioritizes its use.
SDD datapath query device - l displays the preferred path
For systems which dont support preferred path - map LUNs to
host adapters (or groups) on the same cluster for best
performance but be aware that cluster failure may impact
data availability.
DS6000 only
Student Notebook
Notes:
The dual paths are split across the two RIO-G bays.
(Recommended)
Student Notebook
V3.1.0.1
Uempty Checkpoint
1. The grouping of disks for use by the DS8000 storage subsystem is
called an:
a. Array
b. Disk Group
c. Array Site
d. Volume Group
2. T/F The DS8000 places each array into a rank to define the format
of the array.
3. T/F The extent pool defines the RAID type which is used in the
arrays.
4. T/F The minimum number of extent pools to define in the DS8000
or DS6000 is two, or one for each server.
Student Notebook
Notes:
Unit Summary
Describe the storage virtualization terms
Describe the physical configuration concepts: Definitions
Describe the logical configuration concepts: Definitions
Describe the logical address groups and addressing
Describe the logical subsystems in the DS6000/DS8000
Describe the logical device definitions in the DS6000/DS8000
Student Notebook
Copyright IBM Corp. 2005 Unit 3. DS8000 Command Line Interface 3-1
V3.1.0.1
Uempty
Unit 3. DS8000 Command Line Interface
The DS8000 Command Line Interface is customer-installable software
used for configuration of the DS8000 Storage Subsystem. This
software allows the user to issue commands from a workstation or
HMC console and get immediate responses to queries about the
configuration or to perform configuration functions. The DSCLI also
provides primary support for the Copy Services functions provided by
the DS8000 subsystem.
Describe the installation of the DS8000 Command Line Interface
Describe the requirements to install the DSCLI
Understand how to access the DSCLI
Describe list and show commands of the DSCLI
Describe configuring array sites, arrays, ranks, and extent pools
Assigning ranks to extent pools
Defining LCUs and CKD logical volumes
Describe configuring FICON host attachments
Accountability:
Checkpoint
Lab exercises
References
Concepts
SC24-7623 IBM TotalStorage: DS8000 Users Guide
Guide
Student Notebook
SC26-7625 IBM TotalStorage DS8000 Command Line User's
Guide
Student Notebook
V3.1.0.1
Uempty
Notes:
Unit Objectives
Describe the IBM DS6000/DS8000 Command Line Interface
Describe the installation of the DSCLI
Describe how to access the DSCLI
Describe the dscli.profile and how to use them
Describe the userid and password definitions
Describe the DSCLI commands and usage
Student Notebook
Student Notebook
V3.1.0.1
Uempty 3.1 Introduction and Architecture
Student Notebook
Figure 3-2. Topic: DS CLI Introduction and Architecture SS481.0
Notes:
Topic: DS CLI Introduction and Architecture
DSCLI Introduction and Architecture
DSCLI Installation
DSCLI Modes
Configuration Process using DSCLI
DSCLI Commands
Student Notebook
V3.1.0.1
Uempty
Figure 3-3. DS Command Line Interface (CLI) Introduction SS481.0
Notes:
DS Command-Line Interface The IBM TotalStorage DS Command-Line Interface (CLI)
helps enable open systems hosts to configure the DS8000 or DS6000 storage units and
invoke and manage FlashCopy and Metro and Global Mirror functions through batch
processes and scripts.
DS Command Line Interface (CLI) Introduction
Provides a full-function command set to:
Create new logical storage and Copy Services configuration
settings
Modify or delete logical storage and Copy Services
configuration settings
Check and verify your storage unit configuration
Check the current Copy Services configuration that is used by
the storage unit
The following codes are delivered with the DS6000/DS8000 hardware:
Microcode CD
CLI CD
SDD CD
SMC software CD
The DSCLI can be installed on a workstation and on the servers
Student Notebook
Figure 3-4. Whats New? SS481.0
Notes:
The DSCLI is a robust set of commands which controls the configuration and Copy
Services functions of the DS6000 and DS8000 products. It is install on a customers
workstation in much the same way as the ESS CLI code, however, it does not
communicate with the DS8000 servers directly. Instead it interacts with the Hardware
management Console and, if the request requires information from the DS8000, the HMC
gets that information form the DS Storage Manager Server and then responds to the
DSCLI with the output. Unlike the ESS CLI, you are not in direct communication with the
Storage Unit cluster server. Also, the DS Copy Services CLI is much more robust and the
idea of producing tasks using the GUI is completely replaced with a set of commands for
every DS Copy Services function. In addition, it is no longer possible to perform a Copy
Services function from the GUI and save it as a task to be run at a later time, so with no
task save functions the GUI becomes a one-time shot type of interface. Automation of
Copy Services focuses on script building using the DSCLI commands for Copy Services.
Whats New?
The new DS CLI replaces the CS CLI and ESS CLI
Provides new functions to dynamically create and manage
FlashCopy and PPRC relationships without any use of a GUI
Allows a PPRC relationship between 2105 and the DS8000 and
DS6000
Enables dynamic FlashCopy and PPRC relationships on ESS 800
storage servers
Prior to DS CLI it was required to create a task using the GUI
interface and then saving it
DS CLI commands can be saved as scripts which significantly
reduces the time to create, edit and verify their content
Uses a consistent syntax with other IBM TotalStorage products now
and in the future
All of the function available to the GUI is also available via the DS
CLI
Student Notebook
V3.1.0.1
Uempty
Figure 3-5. Supported DS CLI Platforms SS481.0
Notes:
This chart lists the host platforms that supports the DSCLI. The DSCLI CD contains a
wizard install program for each platform type and this can be executed using a
Windows-type GUI or command line silent mode install.
Supported DS CLI Platforms
Java 1.4.1 must be installed.
The DS Command-Line Interface (CLI) can be installed on
the following operating systems:
AIX 5.1, 5.2, 5.3
HP-UX 11i v1, v2
HP Tru64 version 5.1, 5.1A
Linux (RedHat 3.0 Advanced Server (AS) and Enterprise
Server (ES)
SuSE Linux SLES 8, SLES 9, SuSE 8, SuSE 9)
Novell Netware 6.5
Open VMS 7.3-1, 7.3-2
Sun Solaris 7, 8, 9
Windows 2000, Windows Datacenter, and Windows 2003
Student Notebook
Figure 3-6. DSCLI Considerations SS481.0
Notes:
The DSCLI can be installed on a host with the ESS CLI without causing any problems,
however, the DS6000 and DS8000 have different DSCLI programs and although similar,
they can not be installed on the same machine. For most commands you can use the
DS8000 DSCLI for most DS6000 commands and would only be left with a few specialized
commands that would not be available.
DSCLI Considerations
Same DSCLI code for DS8000 and DS6000 (and
ESS 800 copy services)
DSCLI and ESSCLI may be installed on the same
machine
Help does not indicate which DSCLI commands are
supported by which machine type (DS8000,
DS6000, ESS800)
LUN sizes now specified in binary GB, decimal GB or
blocks
Student Notebook
V3.1.0.1
Uempty
Figure 3-7. DSCLI Architecture SS481.0
Notes:
Since the HMC sits between the host DSCLI and the server, it interprets the commands
and sends on those that need information from the DS8000. Not all requests are
synchronized, which means that a completion request means the command has been
issued, not that it has completed. The user may have to wait for asynchronous operation to
complete before moving on to the next command. Some queries may give input back to
indicate if it is OK to proceed. Scripting large configurations may be difficult due to this
async operational status.
DSCLI Architecture
DSCLI operations are directed to the HMC/SMC
Need compatibility and communication between DSCLI,
Master Console (HMC/SMC) and storage network interfaces
HMC/SMC handles some requests locally (for example,
lsuser, lssi, lssu)
HMC/SMC passes some requests to storage (for example,
lsarray)
DSCLI issues requests asynchronously
This presents challenges for scripting
More than one request per DSCLI command is possible
May receive success message while work still in progress
May receive timeout message while work still in progress
Output of list and show commands may not represent work
in progress
Student Notebook
Figure 3-8. Management Consoles: HMC / SMC SS481.0
Notes:
The HMC is the internal Master Console on the DS8000 and you can also have an external
Storage - Hardware Management Console. The DS6000 does not have any space with its
small cabinet to house an HMC, so the SMC is the only Management Console available. If
that lack of redundancy is a concern, then install a second SMC as a redundant backup.
Management Consoles: HMC / SMC
Two different names to distinguish between DS8000 and DS6000
consoles
HMC (or S-HMC)
DS8000 Hardware Management Console
Internal and Optional External HMC
SMC
DS6000 Full Management Console
Includes DS6000 DS Storage Manager
Also includes additional utility functions to permit remote support,
including Putty and VPN Client
Student Notebook
V3.1.0.1
Uempty
Figure 3-9. DS CLI Architecture SS481.0
Notes:
The DSCLI contains a DS Network Interface client component that talks to the DS Network
Interface Server on the HMC to communicate with the DS8000.
DS CLI Architecture
DSCLI
Customer
Workstation
Network
Interface
Client
Network
Interface
Server
Network
Interface
Client
GUI Server
Browser
SMC/HMC
Storage
Network Interface
Student Notebook
Figure 3-10. DS6000 Data Flow SS481.0
Notes:
The Host operating system can contain files that act as scripts that have just DSCLI
commands in them or actual UNIX shell scripts that contain shell script statements
wrapped around single shot DSCLI commands. The script is invoked by starting the DSCLI
in interactive mode and calling a script file as input to the command stream. The other
mode would be to start a shell script and call a single shot DSCLI command in the shell
script stream. The command is executed and control is returned to the shell script.
Commands are sent to the HMC or SMC via the IP network and is received by the Network
Interface Server and then command are sent to the CLI interface in the controller of the
DS6000 or the server in the DS8000. Command output is returned to the DSCLI client and
displayed to the user.
DS6000 Data Flow
Open systems
host
Network interface
ESS CLI software DS CLI software
CLI script
Controller 1
Controller 2
DS6000
CLI interface CLI interface
DS Storage
Management PC
CLI
interpreter
Network interface
Student Notebook
V3.1.0.1
Uempty 3.2 DSCLI Installation
Student Notebook
Figure 3-11. Topic: DS CLI Installation SS481.0
Notes:
Topic: DS CLI Installation
DSCLI Installation
DSCLI Modes
DSCLI Commands
Student Notebook
V3.1.0.1
Uempty
Figure 3-12. DS CLI Installation (1 of 2) SS481.0
Notes:
The DSCLI requires Java 1.4.1. or 1.4.2 and the package is installed in c:\progrram
Files\IBM\dscli on Windows and /opt/ibm/dscli on UNIX platforms. The Java library can be
called from the subdirectories of the DSCLI or an alternate place using the CLI.CFG file. In
order to run command or script from other directories, update pathing variables in
/etc/environment or environmental variable in the Properties folder of My Computer on
Windows.
DS CLI Installation (1 of 2)
Java-based graphical installer for Windows and UNIX platforms
Java 1.4.1 required
Can run in console mode (-console)
Part of DS microcode package
Still strong version dependencies
Run
Windows: dscli.exe
UNIX: ./dscli in /opt/ibm/dscli
Must be root
Student Notebook
Figure 3-13. DS CLI Installation (2 of 2) SS481.0
Notes:
If you need to de-install the DSCLI, remove the program from Control panel Add/Remove
Programs and then go delete the DSCLI folder from the c:\Program Files\IBM directory. If
you have saved scripts or profiles in this directory or the profile subdirectory, then make
sure you copy that stuff off somewhere else before you delete the DSCLI directory or you
lose all your scripts and profiles.
DS CLI Installation (2 of 2)
Default user: admin, password admin
Default install directory
Windows -- C:\Program Files\IBM\dscli
UNIX -- /opt/ibm/dscli
Upgrading/removing/reinstalling DSCLI
Remove DSCLI folder
C:\Program Files\IBM\dscli
Student Notebook
V3.1.0.1
Uempty
Figure 3-14. Unzipped DSCLI CD SS481.0
Notes:
This is the CD with the DSCLI code on it and to install for Windows you run the
Setupwin32.exe file. For other platforms, run the appropriate shell script or bin file on that
platform.
Unzipped DSCLI CD
Student Notebook
Figure 3-15. DSCLI - Directory SS481.0
Notes:
The default directory is displayed, you can change it if you want. Click Next.
DSCLI - Directory
Student Notebook
V3.1.0.1
Uempty
Figure 3-16. Starting DSCLI SS481.0
Notes:
Once you finish you have a DSCLI command window on your Desktop, but you could start
it from the install directory too.
Starting DSCLI
Student Notebook
Figure 3-17. DSCLI SS481.0
Notes:
Now normally, the DSCLI would not understand where the DS8000 or DS6000 is located or
where the HMC is, so you must tell it. Enter the IP address of the HMC when prompted and
the IP of the secondary S-HMC when prompted and the userid and password of the
Network Interface server and your into the DSCLI.
Now, that seems like a lot of things to input so there must be a better way. OK, so there is a
profile called dscli.profile
DSCLI
C:\Program Files\ibm\dscli>dscli
Enter the primary management console IP address: 127.0.0.1
Enter the secondary management console IP address: 127.0.0.1
Enter your username: admin
Enter your password:
Date/Time: July 10, 2005 2:29:22 PM MDT IBM DSCLI Version: 5.0.3.194 DS:
IBM.2107-AZ00041
dscli> lssu
Date/Time: July 10, 2005 2:29:36 PM MDT IBM DSCLI Version: 5.0.3.194
Name ID Model WWNN pw state
==========================================================================
DS8300 Storage Facility3B IBM.2107-AZ00040 922 0000000000000000 On
dscli>

Student Notebook
V3.1.0.1
Uempty
Figure 3-18. DS CLI Configuration SS481.0
Notes:
The dscli.profile is located in the profile subdirectory of the DSCLI install directory. It may
contain the HMC IP addresses and device ID as well as a password file or pwfile located in
a local directory where it was created. The profile supplies input to the DSCLI so you dont
have too.
DS CLI Configuration
DS CLI profile
Default: /opt/ibm/dscli/profile/dscli.profile
C:\Program Files\IBM\dscli\profile\dscli.profile
Created at installation
Invoked at DSCLI startup
Contains
Address of S- HMC
Storage Image ID
User information
Password files
Encrypted userid and password
Generated with mkuser command
Stored in /opt/ibm/dscli/security/<S-HMC
IP>/<file_name>
Note: -cfg flag can be used on dscli command to invoke profile
other than default
Student Notebook
Figure 3-19. DSCLI Profile File SS481.0
Notes:
The dscli.profile provides input to the DSCLI in place of the user entering it manually.
DSCLI Profile File
DSCLI profile file is the place to specify values for flags that are
needed for many commands
HMC/SMC IP addresses
hmc1
hmc2
Storage image ID
devid
Eliminates need to specify dev on many commands
Userid and password
pwfile
Profile points to password file (pwfile) containing encrypted
userid and password
Timeout for network interface client/server communication
Timeout
Default is 420 seconds
Other values (see following charts)
If a profile is in use, flag values included on a command can be
used to override values from profile file
Student Notebook
V3.1.0.1
Uempty
Figure 3-20. DSCLI Profile File Example SS481.0
Notes:
This is the dscli.profile default profile. You can make other profiles too, but they will have
different names. These can be called using the cfg option of the DSCLI command.

# DS CLI Profile
#
#
# Management Console/Node IP Address(es)
# hmc1 and hmc2 are equivalent to -hmc1 and -hmc2 command options.
#hmc1: 127.0.0.1
#hmc2: 127.0.0.1
#
# Default target Storage Image ID
# "devid" and "remotedevid" are equivalent to
# "-dev storage_image_ID" and "-remotedev storeage_image_ID" command options,
respectively.
#devid: IBM.2107-AZ12341
#remotedevid: IBM.2107-AZ12341
#
# locale
# Default locale is based on user environment.
#locale: en
# Timeout value of client/server synchronous communication in second.
# DSCLI command timeout value may be longer than client/server communication
# timeout value since multiple requests may be made by one DSCLI command
# The number of the requests made to server depends on DSCLI commands.
# The default timeout value is 420 seconds.
#timeout 420
dscli.profile

Student Notebook
Student Notebook
V3.1.0.1
Uempty 3.3 DSCLI Modes
Student Notebook
Figure 3-21. Topic: DSCLI Modes SS481.0
Notes:
Topic: DSCLI Modes
DSCLI Installation
DSCLI Modes
DSCLI Commands
Student Notebook
V3.1.0.1
Uempty
Figure 3-22. Three Ways to Use DSCLI SS481.0
Notes:
There are three modes of command input. There is single shot mode where control is
returned to the command line. Interactive mode where control is returned to the DSCLI
command mode and script mode which execute commands from a script.
Single-Shot Mode:
The user specifies the CLI program and command to execute
at the shell prompt:
shell> dscli lsvolgrp -dev IBM.2107-1300861
Interactive Mode:
The user starts the CLI program and then specifies
commands at the program prompt.
Script Mode:
The user starts the CLI program and specifies a file
containing commands to run:
shell> dscli -script ~/bin/volumegroupcreation
Three Ways to Use DSCLI
Student Notebook
Figure 3-23. DSCLI Interactive Mode SS481.0
Notes:
The DSCLI command starts the command-line interface (CLI) program. You can use this
command to run DSCLI commands in interactive mode, to run a single command, or to run
a set of commands from a script.
Example This command invokes the CLI in interactive mode:
>dscli
The startup screen:
Welcome to the DS Command-Line Interface Interactive program. Type help to retrieve
a list of available program commands. Type quit to exit interactive mode. Tip: Use set
output to set output options that will apply during the length of your session in
interactive mode. Enter HMC IP Address: xxxxxx MC IP Address is set to xxxxx
DSCLI Interactive Mode
dscli command
Student Notebook
V3.1.0.1
Uempty
Figure 3-24. DSCLI DSCLI Script Mode SS481.0
Notes:
These scripts are really just a set of DSCLI commands in a file and as such the DSCLI
does not accept any shell script commands inside a script executed from the single shot or
interactive mode. If you wish to return control to the shell script environment after the
command completed, then you must execute the commands in single shot mode within the
script.
DSCLI DSCLI Script Mode
DSCLI scripts are not shell scripts!
DSCLI scripts are files with lists of DSCLI commands and
comments (prefixed by #) only
DSCLI scripts may be called by shell scripts
Output is returned to screen, or may be piped to a file
DSCLI reads script file one line at a time
Exits DSCLI at completion of DSCLI script or on failure
Use DSCLI profile file
Student Notebook
Student Notebook
V3.1.0.1
Uempty 3.4 Configuration Process using DSCLI
Student Notebook
Figure 3-25. Topic: Configuration Process using DSCLI SS481.0
Notes:
Topic: Configuration Process Using DSCLI
DSCLI Installation
DSCLI Modes
DSCLI Commands
Student Notebook
V3.1.0.1
Uempty
Figure 3-26. DS8000/DS6000 - Storage Virtualization Overview SS481.0
Notes:
The constructs for DS8000 virtualization start at the physical disks which are grouped into
array sites, then formed into arrays, formatted into extents placed into ranks, and finally,
ranks grouped into extent pools. Volumes are allocated from extents from the extent pools
and can be deleted. The extents are returned to the extent pool.
Extent
Pool
Rank
{r}
Array
[a]
Array Site
Disk
RAID 5 RAID 10
6+P+S 3x2+2S
7+P 4x2
[ ] [ ]

1-N Ranks in Extent Pool
Associated with server0 or server1
All Extents are same Type
CKD or FB
Same RAID recommended
Same DDM RPM recommended
1,2*,4*,8* Arrays per Rank
Rank Divided into N Fixed Sized Extents CKD (Mod1) or
FB (1 GB)

DS8000/DS6000 one Array Site used to construct one
Array (8 DDMs)
DS6000 (1Q05) one 4 DDM Array Site used to
construct one Array (4 DDMs)
Spare Policy Enforced
RAID5 or RAID10
Logical Grouping of 8 Disks of same speed and capacity
(1Q05: 4 disks for DS6000)
Individual DDMs: 73, 146, 300 GB
Post GA For DS8000
{[a]} {[a],[a],[a],[a]}
Extent Pool
{r}
{r}. . .{r}
s
DS8000/DS6000 -
Storage Virtualization Overview
Student Notebook
Figure 3-27. Storage Hierarchy Summary SS481.0
Notes:
The volumes are logical volumes or LUNs made up of a group of extents from the extent
pool. Extents are allocated contiguously from the first rank in the extent pool and if there is
more than one rank, volumes can span across from one rank to the next. If there are not
enough extents in the extent pool to satisfy the request, then it fails.
The volume group is a set of volumes which are connected to a set of host attachments
and form the volume group. This is the way in which the D8000 does LUN masking.
Storage Hierarchy Summary
Volumes or LUNs
Made up of extents from one extent pool
Min size 0.1 GB or 1 cylinder
Max size 2 TB (FB) 56 GB(CKD)
Can be larger than one rank if more
than one rank in pool
Associated with LSS during configuration
Volume Group
Contains LUNs and host attachments -- FB
LUN masking
One host attachment (one port or port group)
can be member of only one volume group
One volume can be member of multiple
volume groups
Multiple hosts (even different open systems
server types) can be member of the same
volume group
AIX host port
iSeries host
port group
AIX host port
FB
FB
FB (i)
FB
FB
FB
Student Notebook
V3.1.0.1
Uempty
Figure 3-28. Physical Infrastructure Hierarchy SS481.0
Notes:
These are the high-level hardware terms. The complex is the set of storage units managed
by an HMC; the storage image is a logical partition of the storage units.
Physical Infrastructure Hierarchy
Storage Complex
One or multiple physical
storage subsystems
Storage Unit (Storage facility)
Single physical storage
subsystem
Storage Image (DS8000)
Single logical storage
subsystem
LPAR System
Disks
I/O Drawer
RIO 1
I/O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/O Drawer
RIO 0
I/O Drawer
RIO 0
Shark
Image 0
(LPAR 0)
Shark
Image 0
(LPAR 0)
Shark
Image 1
(LPAR 1)
Shark
Image 1
(LPAR 1)
Storage
Enclosure
I/O Drawer
RIO 1
I/O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/O Drawer
RIO 0
I/O Drawer
RIO 0
Single LPAR
Resources
LPAR System
Disks
I/O Drawer
RIO 1
I/O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/O Drawer
RIO 0
I/O Drawer
RIO 0
Shark
Image 0
(LPAR 0)
Shark
Image 0
(LPAR 0)
Shark
Image 1
(LPAR 1)
Shark
Image 1
(LPAR 1)
Student Notebook
Figure 3-29. Initial Configuration Prerequisites SS481.0
Notes:
These are operations which must be done prior to defining the arrays and volumes.
Initial Configuration Prerequisites
DS6000
Define users
Assign Storage Unit
Configure Storage Unit
Apply Keys
DS8000
Apply license keys
Student Notebook
V3.1.0.1
Uempty
Figure 3-30. DS CLI User Management SS481.0
Notes:
The users of the DSCLI and the Storage Manager are defined to the Network Interface and
authorized at logon. There are several groups of users with different authority levels.
DS CLI User Management
Users are members of groups with different authorizations
Only members of admin group can manage users
Each user can have a password file
CLI and SM users are identical
CLI users are not S-HMC users
Student Notebook
Figure 3-31. DSCLI User Groups SS481.0
Notes:
These are the user groups. Admin can do everything, monitor can just view things.
DSCLI User Groups
Groups define allowed functions
No access
Default if no other group specified
monitor
List and show commands
op_copy_services
Monitor plus copy services
op_storage
Monitor and copy services plus storage complex, storage
facility, storage image, array, rank, extent pools, ioports
op_volume
Monitor plus logical volumes, hosts, host ports, logical
subsystems and volume groups
service (DS6000)
Monitor plus DS6000 service functions
admin
User may be in multiple groups
Separate groups by commas on mkuser, chuser
Student Notebook
V3.1.0.1
Uempty
Figure 3-32. New DSCLI Password Rules SS481.0
Notes:
Passwords expire the first time they are used the user must change their password before
they can enter any command. The chuser command is used to perform that change.
Password expires after three failed attempts. You can modify that with the chpass
command.
Password must be six characters minimum, five letters and one number which can not be
at the beginning or end. The password passw0rd is a good example of what is a valid
password.
New DSCLI Password Rules
Initial passwords expire immediately
This applies to default userid (admin) as well as userids you
create
You can log on, but get an authorized message as soon as you
try to issue a command
After three failed logon attempts, userid is locked out
Showpass and chpass can be used to change defaults for
expiration and failed login limits (for all passwords)
Initial password for admin userid is admin
Need to change immediately to avoid lockout
Administrator can change a password, but cannot
retrieve a password
Student Notebook
Student Notebook
V3.1.0.1
Uempty 3.5 DSCLI Commands
Student Notebook
Figure 3-33. Topic: DSCLI Commands SS481.0
Notes:
Topic: DSCLI Commands
DSCLI Installation
DSCLI Modes
DSCLI Commands
Student Notebook
V3.1.0.1
Uempty
Figure 3-34. DSCLI Command Considerations SS481.0
Notes:
The commands are case sensitive. Ranges are allowed on many commands.
DSCLI Command Considerations
Case-insensitive
Except for nicknames
Multiple operations on single command
Specify multiple IDs separated by blanks
commas for volume group or host connections,
keys, user groups
Specify range
IDs separated by hyphen
Multiple ranges
Separated by blanks
Volume group or host connection ranges
separated by commas
Student Notebook
Figure 3-35. DSCLI Flag Parameters SS481.0
Notes:
The parms are entered with a keyword flag and the parm.
DSCLI Flag Parameters
dscli command name flag flag parameter command parameter
Not positional
Flag parameters required for all commands if not using profile file
-hmc1
-hmc2
-user
-passwd
dscli mkextpool hmc1 9.82.22.112 hmc2 9.82.22.112 user
admin -passwd tucs0n -dev IBM.2107-7506571 rankgrp 1 stgtype
fb
-hmc1, -hmc2, -user and -passwd are flag parameters required for
all commands
If not entered on command, DSCLI prompts for these
Not required if specified in profile file
Student Notebook
V3.1.0.1
Uempty
Figure 3-36. Command Flag Parameters or Profile File SS481.0
Notes:
If you dont have a profile defined or if it does not specify this DS8000, then you have to
supply the parms for many things that are usually handled through the profile.
-fullid fully-qualified ID including storage image ID
-hmc1 ip of HMC/SMC (or ESS 800 copy services server)
-hmc2 ip of HMC/SMC (or ESS 800 copy services server)
-user network interface userid
-passwdnetwork interface password for userid
(pwfile in profile file)
-dev Storage Image ID
(devid in profile file)
-remotedevfor Copy Services
(remotedevid in profile file)
-v verbose
Command Flag Parameters or Profile File
Student Notebook
Figure 3-37. DS CLI Command Types SS481.0
Notes:
These are types of commands. List, show are monitor commands, mk ch and rm are admin
commands.
DS CLI Command Types
Framework command
CLI security and information commands
Application key and version commands
Storage complex configuration commands
Storage unit configuration commands
Storage image configuration commands
Host connection configuration commands
Storage configuration commands
Copy services commands
Student Notebook
V3.1.0.1
Uempty
Figure 3-38. List and Show Considerations SS481.0
Notes:
Examples of list and show commands.
List and Show Considerations
To see which volumes are on a rank:
Display extent pool associated with a rank
lsrank or showrank
Display volumes associated with this extent pool
lsckdvol extpool
lsfbvol extpool
showckdvol
showfbvol
Student Notebook
Figure 3-39. Getting Help with DSCLI SS481.0
Notes:
This help command can be useful for the new user. Just type the command with no parms
to get the syntax help.
Getting Help with DSCLI
Error message and command syntax
dscli commandname (or commandname in DSCLI interactive mode)
Man page with syntax and examples
dscli commandname help (or h or -?) or dscli help commandname
Command with syntax information
dscli help l commandname
List of DSCLI commands
dscli help (or help in DSCLI interactive mode)
Command with brief description
dscli help s commandname
Help for DSCLI is also available in DS Storage Manager Info Center
Student Notebook
V3.1.0.1
Uempty
Figure 3-40. Object ID Considerations SS481.0
Notes:
The object IDs are used for many of the mk commands.
Object ID Considerations
Object IDs are required as command input by DSCLI
Some objects have IDs which are assigned depending on number of
similar objects created/deleted
Order of creation
Extent pool
Array
Rank
Hostconnection (definition of one Host Bus Adapter)
Volume Group (with some IDs reserved)
When an object is deleted, that ID is freed up and will be used for the
next object created
LCUs, volumes and port groups have IDs as specified
Student Notebook
Figure 3-41. Infrastructure IDs SS481.0
Notes:
The Storage Unit has an ID which is the machine manufacturer IBM the Model 2107 and
the serial 7516546. Serial is XXYYYYY, where XX is Manufacturing location and YYYYY is
the serial number.
Infrastructure IDs
Storage Complex
Identified by SMC IP address (for
example, 9.82.22.112)
Storage Unit
IBM.1750-13AAVCA
Used on showsu command
Storage Image
IBM.1750-13AAVCA (same as Storage
Unit above)
Used as dev parameter in many
commands
Also required without the dev flag in a
few commands
Signature
a608-c4f3-0052-cd88 (2107 and 1750
have same format)
LPAR System
Disks
I/O Drawer
RIO 1
I/O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/O Drawer
RIO 0
I/O Drawer
RIO 0
Shark
Image 0
(LPAR 0)
Shark
Image 0
(LPAR 0)
Shark
Image 1
(LPAR 1)
Shark
Image 1
(LPAR 1)
LPAR System
Disks
I/O Drawer
RIO 1
I/O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/O Drawer
RIO 0
I/O Drawer
RIO 0
Shark
Image 0
(LPAR 0)
Shark
Image 0
(LPAR 0)
Shark
Image 1
(LPAR 1)
Shark
Image 1
(LPAR 1)
LPAR System
Disks
I/O Drawer
RIO 1
I/O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/O Drawer
RIO 0
I/O Drawer
RIO 0
Shark
Image 0
(LPAR 0)
Shark
Image 0
(LPAR 0)
Shark
Image 1
(LPAR 1)
Shark
Image 1
(LPAR 1)
LPAR System
Disks
I/O Drawer
RIO 1
I/O Drawer
RIO 1
CEC 1
CEC 0
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
Storage
Enclosure
I/O Drawer
RIO 0
I/O Drawer
RIO 0
Shark
Image 0
(LPAR 0)
Shark
Image 0
(LPAR 0)
Shark
Image 1
(LPAR 1)
Shark
Image 1
(LPAR 1)
Student Notebook
V3.1.0.1
Uempty
Figure 3-42. Object IDs (1 of 5) SS481.0
Notes:
The object IDs are used to configure logical configuration components.
Object IDs (1 of 5)
Arraysite
S1-Sx
Extent Pool
P0-Px (In order of creation)
Array
A0-Axxxx (In order of creation)
Rank
R0-Rx (In order of creation)
Student Notebook
Notes:
This is the LCU or LSS format. The LCU, or Logical Control Unit is a zSeries object used to
identify the 3990 control unit and is required for zSeries addressing. The LSS is an object
for Open Systems and defines the logical subsystem for the Open System host. LSS has
association with the extent pool which ties it to a server of the DS8000.
Object IDs (2 of 5)
LCU/LSS
00-xy
x = Address group
DS8000 x = 0-7
DS6000 x = 0-1
2/25 GA
y=x0-xf
LCU is CKD only
LSS is FB only
Even LSSs/LCUs are available for extent pools
associated with Server0
Odd LSSs/LCUs are available for extent pools
associated with Server1
Student Notebook
V3.1.0.1
Uempty
Notes:
The Volume IDs are LSS and volume address. LSSs are divided into address groups of 0
to F, and LSS of 0 to F, and volumes are numbered from 00 to FF.
Object IDs (3 of 5)
Volumes
0000-xyzz
x=address group
0-7 (DS8000)
0-1 (DS6000)
2/25 GA
y= x0 xf
z=x00 xff
Volume IDs also apply to PAVs
Student Notebook
Notes:
Host connection ports have a 4-digit number to identify the port. Volume groups are from
V11-Vxx but V0-V9 are reserved.
Object IDs (4 of 5)
Host connections
0000-xxxx (In order of creation)
Portgrp
0-very large (decimal 999,999,999)
Volume group
V11-Vxx (with the exception of V20 and V30)
V0-V9 are reserved for 2/25 release
V10, V20, V30 are default volume groups
In order of creation
Student Notebook
V3.1.0.1
Uempty
Notes:
This is the I/O port definitions.
Object IDs (5 of 5)
I/O ports
Iwxyz (RICT)
w= frame
0-2 (DS8000)
0 (DS6000)
x= enclosure
0-3 (DS8000)
0-1 (DS6000)
y= card
0,1,3 or 4 (DS8000)
0-1 (DS6000)
z= port
0-3 top to bottom (DS8000 FICON/FCP)
0-3 left to right (DS6000 FICON/FCP)
0-1 top to bottom (DS8000 ESCON)
I0000-I2343 (DS8000)
I0000-I0003 and I0100-I0103 (DS6000)
Student Notebook
Figure 3-47. 1750 Host IOPORT Port Numbers from DS CLI SS481.0
Notes:
The 1750 has similar port definitions.
1750 Host IOPORT Port Numbers from DS CLI
Port 0 Port 1 Port 2 Port 3
I0000 I0000
Server 0
I0001 I0001 I0002 I0002 I0003 I0003
Port 0 Port 1 Port 2 Port 3
I0100 I0100
Server 1
I0101 I0101 I0102 I0102 I0103 I0103
A port ID is prefixed with letter I
Consists of four hexadecimal
characters in the format EEAP:
EE is Server number
00 01 for 1750
A is the adapter number
Specified as 0, 1, 2, 3 for 1750
P is the port number (0 - 3)
Student Notebook
V3.1.0.1
Uempty
Figure 3-48. Sample CLI Configuration Script (1 of 5) SS481.0
Notes:
Sample CLI Configuration Script (1 of 5)
## Description :
# This CLI script creates,
# 32 CKD volumes on LCU 02
# 32 CKD volumes on LCU 04
# 64 FB volumes on LSS 11
# # Prerequisite :
# o CLI version ?
# o ESSNIClient 0824
# o Initial Configuration
# - The target storage facility image is "IBM.2107-921-9999999"
# - No volumes exist
# - No LCUs or LSSs exist
# - No ranks exist
# - No arrays exist
# - No extent pools exist
# - Array site S1 and S2 are unassigned#
Student Notebook
Notes:
# Created resources :
# - 1 CKD extent pool named "ckd_ext_pool0" in rank group 0 : P0
# - 1 FB extent pool named "fb_ext_pool1" in rank group 1 : P1
# - 2 RAID 5 arrays : A0, A1
# - 2 ranks : R0, R1
# - 2 LCU : 02, 04
# - 4 LSS : 11, 13, 15, 17
# - 64 CKD volumes with 1000 cylinders in extent pool P0 :0200-021F, 0400-041F
# - 256 FB volumes with 1000 cylinders in extent pool P1 :1100-113F, 1300-133F,
1500-153F, 1700-173F
# - 1 SCSI-Map 256 volume group : V11?
# - 5 SCSI host ports :
# Reference :
# - Section 12.0. Use Case Scenarios, "Command-Line User Interface Design for
IBM TotalStorage 2107 Enterprise Storage server, Version 4.0"
Student Notebook
V3.1.0.1
Uempty
Notes:
Make the extent pools and put the ranks into the pools.
# FB Volumes
# Make an FB extent pool (P1 will be created)
mkextpool -dev IBM.2107-921-9999999 -rankgrp 1 -stgtype fb fb_ext_pool1
# Make an array (A1 will be created)
mkarray -dev IBM.2107-921-9999999 -raidtype 5 S2
# Make a rank (R1 will be created)
mkrank -dev IBM.2107-921-9999999 -array A1 -stgtype fb
# Wait until the rank status becomes 'Unassigned'. (Issue "lsrank -dev
IBM.2107-921-9999999" to get the rank status.)
# Assign R1 to P1
chrank -extpool P1 -dev IBM.2107-921-9999999 R1
Student Notebook
Notes:
Make the volumes.
# Make 64 FB volumes (1100-113F will be created)
mkfbvol -dev IBM.2107-921-9999999 -extpool P1 -cap 2097152 -name fb_vol_#h -qty 64 1100
# Make a SCSI-Map 256 volume group and assign all the volumes to it (V11 is created?)
mkvolgrp -dev IBM.2107-921-9999999 -lun256 -vol "1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 110A
110B 110C 110D 110E 110F 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 111A 111B 111C 111D 111E
111F 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 112A 112B 112C 112D 112E 112F 1130 1131 1132
1133 1134 1135 1136 1137 1138 1139 113A 113B 113C 113D 113E 113F 1300 1301 1302
1303 1304 1305 1306 1307 1308 1309 130A 130B 130C 130D 130E 130F 1310 1311 1312 1313 1314 1315 1316
1317 1318 1319 131A 131B 131C 131D 131E 131F 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 132A
132B 132C 132D 132E 132F 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 133A 133B 133C 133D 133E
133F 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 150A 150B 150C 150D 150E 150F 1510 1511 1512
1513 1514 1515 1516 1517 1518 1519 151A 151B 151C 151D 151E 151F 1520 1521 1522 1523 1524 1525 1526
1527 1528 1529 152A 152B 152C 152D 152E 152F 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 153A
153B 153C 153D 153E 153F 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 170A 170B 170C 170D 170E
170F 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 171A 171B 171C 171D 171E 171F 1720 1721 1722
1723 1724 1725 1726 1727 1728 1729 172A 172B 172C 172D 172E 172F 1730 1731 1732 1733 1734 1735 1736
1737 1738 1739 173A 173B 173C 173D 173E 173F" fbvgname1
Student Notebook
V3.1.0.1
Uempty
Notes:
Make the host connections and volume groups.
# Configure fibre channel I/O ports
# Note: Issue "lsioport -dev IBM.2107-921-9999999" to get the I/O ports to configure.
setioport -topology scsi-fcp IBM.2107-921-9999999/I0020
setioport -topology fc-al IBM.2107-921-9999999/I0021
# Make SCSI host ports and assign a volume group to them.
# Note-1: These commands assume that V11 was created by mkvolgrp command above.
# Note-2: 'prof0' should be replaced by a valid port profile name.
mkhostconnect -dev IBM.2107-921-9999999 -lun256 -wwname 10000000C93742A7 -profile
prof0 -volgrp V11 fcs0
mkhostconnect -dev IBM.2107-921-9999999 -lun256 -wwname 10000000C93743AA
-profile prof0 -volgrp V11 fcs1
mkhostconnect -dev IBM.2107-921-9999999 -lun256 -wwname 10000000C9370261 -profile
mkhostconnect -dev IBM.2107-921-9999999 -lun256 -wwname 10000000C9374779 -profile
mkhostconnect -dev IBM.2107-921-9999999 -lun256 -wwname 10000000C93702CA
-profile prof0 -volgrp V11 fcs4
Student Notebook
Checkpoint
1. T/F The DS8000 is a CLI interface that must be installed on a
customer workstation or used from the DS8000 Master Console.
2. T/F The DS8000 CLI can be online or offline.
3. T/F The DS8000 CLI can create configuration files which can be
downloaded to the DS8000 subsystem and used to configure the
DS8000.
4. T/F The DS8000 CLI supports Copy Services commands to allow
users to automate their FlashCopy or Metro Mirror copies.
5. T/F The DS8000 CLI can be used to configure a DS8000 or a
DS6000
Student Notebook
V3.1.0.1
Uempty
Notes:
Unit Summary
Describe the IBM DS6000/DS8000 Command Line Interface
Describe the installation of the DSCLI
Describe how to access the DSCLI
Describe the dscli.profile and how to use them
Describe the userid and password definitions
Describe the DSCLI commands and usage
Student Notebook
Student Notebook
Copyright IBM Corp. 2005 Unit 4. DS6000 Hardware Architecture 4-1
V3.1.0.1
Uempty
Unit 4. DS6000 Hardware Architecture
The DS6000 storage subsystem is the next generation of storage, and
provides RAID-5 or RAID-10 storage arrays attached to a scalable
state-of-the art processor with variable cache memory and persistent
fast-write cache. The user can configure the storage subsystem using
a GUI-based interface or a DSCLI interface, and configuration can be
handled online or offline, with import and export capabilities for
configuration files created in the offline configuration simulator. This
unit introduces the DS6000 and its hardware components and
architecture. We look at the physical hardware and discuss the
installation and cabling of the unit by the customer.
Describe the components of the DS6000 model 1750 and 1750
EX1
Describe the disk drive packaging that can be installed into
DS6000
Identify the types of host adapters that can be used with the
DS6000
Identify the back-end switched FC-AL interface that are used with
the DS6000
Identify the size of cache and persistent memory that is used with
the DS6000
Identify the redundancy options and failover capabilities used with
DS6000
Accountability:
Checkpoint
Student Notebook
References
Concepts
Guide
GC27-7678 IBM TotalStorage DS6000 Installation,
Troubleshooting and Recovery Guide
GC26-7680 IBM TotalStorage DS6000 Host Attachment Guide
GC26-7681 IBM TotalStorage DS6000 Command Line User's
Guide
Student Notebook
V3.1.0.1
Uempty
Notes:
Unit Objectives
Identify the components and features of the IBM TotalStorage
DS6000 Storage Server
Understand the IBM TotalStorage DS6000 architecture
Explain the IBM TotalStorage DS6000 reliability, availability, and
serviceability
Identify the IBM TotalStorage DS6000 installation process
Explain the IBM TotalStorage DS6000 licenses
Student Notebook
Student Notebook
V3.1.0.1
Uempty 4.1 DS6000 Highlights
Student Notebook
Figure 4-2. Topic: DS6000 Highlights SS481.0
Notes:
DS6000 Highlights
DS6000 Architecture
DS6000 Reliability, Availability,
Serviceability
DS6000 Installation
Topic: DS6000 Highlights
Student Notebook
V3.1.0.1
Uempty
Figure 4-3. DS6000 Highlights SS481.0
Notes:
IBM TotalStorage systems are based on a server architecture. At the core of the DS6800
controller unit are two active/active RAID controllers based on IBMs industry leading
PowerPC architecture. By employing a server architecture with standard hardware
components, IBMs storage division can always take advantage of the best of breed
components developed by other IBM divisions. The customer gets the benefit of a very cost
efficient and high performing storage system.
The DS6800 utilizes two 64-bit PowerPC 750GX 1 GHz processors for the storage server
and the host adapters, respectively, and another PowerPC 750FX 500 MHz processor for
the device adapter on each controller card. The DS6800 is equipped with 2 GB memory in
each controller card, adding up to 4 GB. Some part of the memory is used for the operating
system and another part in each controller card acts as persistent memory but most of the
memory is used as cache. This design to use processor memory makes cache accesses
very fast.
DS6000 Highlights
Connects to multiple platforms
AIX, Windows, SUN, HP, Linux, SGI, z/OS,
zLinux, OS/400, Solaris, and so forth
Built with latest technology
Switched FC-AL disk, PowerPC processors
Linux kernel, no LPAR capabilities
Two PowerPC 750GX 1 GHz symmetric
multiprocessors
One PowerPC 750FX processor per RAID
adapter
2 Gb SW FCP or FICON adapters
2 GB Cache per controller
High availability via automatic failover
IBM TotalStorage DS Copy Services
FlashCopy
Metro Mirror - Peer-to-peer remote copy
Global Copy - PPRC-XD
Global Mirror - Async PPRC
IBM TotalStorage DS Storage Manager
IBM TotalStorage TPC
Four year warranty
Student Notebook
Figure 4-4. DS6000 Rear View SS481.0
Notes:
DS6800 (Model 1750-511) The DS6800 offer the following features:
Two FC controller cards
Linux Kernel OS
PowerPC 750GX 1 GHz processor v 4 GB of cache
Two battery backup units (one per each controller card)
Two AC/DC power supplies with imbedded enclosure cooling units
Eight 2 Gb/sec. device ports
Connectivity with the availability of two to eight fibre channel/FICON host ports. The host
ports auto-negotiate to either 2 Gbps or 1 Gbps link speeds.
The two in ports on the left are the switch ports that connect either to the server enclosure
(to either the disk exp loop or the disk control loop) or to the out ports of a previous
expansion enclosure.
Power Supply
Power Supply
Battery backup Units
Lower RAID Controller
Upper RAID Controller
Rear Display Panel
DS6000 Rear View
Student Notebook
V3.1.0.1
Uempty
The two out ports on the right (in light blue boxes) are the switch ports that attach to the in
ports of the next expansion enclosure. If there are no extra expansion enclosures then they
are not used.
Student Notebook
Figure 4-5. DS6000 Model EX1 Hardware Structure SS481.0
Notes:
The Model EX1 contains four 16 DDMs and connects to the 1750-511 using SFPs and FC
cables. The expansion unit has eight SFPs shipped standard with it, four SFPs for the
control unit and four for the expansion enclosure. The two controllers provide two FC-AL
loops, and the first disk enclosure is in the 1750-511 itself and is located on Loop 0. The
first Expansion unit connects to the control unit on Loop 1 and the third also on Loop 1, and
then alternates between Loop 0 and Loop 1. The ports to connect Loop 0 are expansion
enclosure ports and just extend the FC-AL loop, because there is already an internal
enclosure on Loop 0.
The expansion enclosures are also shipped with eight SFPs and has an internal FC switch
to implement the switched FC-AL attachment the same as the DS8000. Four SFPs are
inputs from the controller or a previous EX1, and the other four SFPs are four out ports to
the next EX1. You can connect six EX1 SBOD units to Loop 0, and seven EX1s to Loop 1
for a total of 14 enclosures of 16 DDMs or 224 DDMs. This gives the user a maximum of
67.2 TB of storage with 300 GB DDMs.
Model EX1 Expansion Enclosure
Four 16 FC-AL DDMs
Expansion Enclosures
First expansion enclosure has eight
SFPs shipped standard with it (four
for control unit and four for expansion
enclosure)
Expansion enclosure has eight
SFPs shipped standard with it (four
for current expansion unit and four for
new expansion unit)
Shortwave connectivity
Expansion enclosure ships with
eight SFPs
DS6000 Model EX1 Hardware Structure
Student Notebook
V3.1.0.1
Uempty
Figure 4-6. Disk Enclosure Rear View SS481.0
Notes:
DS6000 expansion enclosure (Model 1750-EX1) The DS6000 expansion enclosure
contains the following features:
Two expansion controller cards.
Each controller card provides the following:
- Two 2 Gb/sec. inbound ports
- Two 2 Gb/sec. outbound ports
One FC switch per controller card
Controller disk enclosure that holds up to 16 FC DDMs or dummy carriers.
Two AC/DC power supplies with imbedded enclosure cooling units
Supports attachment to DS6800 Model 1750-511
IN
OUT
Next expansion enclosure
Server enclosure or
previous expansion enclosure
Two expansion controller cards
including:
One FC switch / controller
4x2 Gb/s ports/controller
Up to 16 DDMs
4 x 2Gb/s ports
4 x 2Gb/s ports
Disk Enclosure Rear View
Student Notebook
The DS6000 expansion enclosure is a 3 EIA self-contained unit that can be mounted in a
standard 19-inch rack. The front of the enclosure contains the docking sites where you can
install up to 16 DDMs.
Student Notebook
V3.1.0.1
Uempty
Figure 4-7. DS6800 Model 1750-EX1 SS481.0
Notes:
The DS6000s all look the same from the front, however from the back the 1750-511 has the
controller cards where the EX1 just have the SBOD cards. Each EX1 or 511 have two
power supplies and require two power cords. Also Ethernet connections to the 511 are
required for access by the SMC.
Front View
Rear Views
4 to 16 DDMs or Dummy carriers
1 Front Display panel
Same for 511 or EX1
2 RAID controllers + expansion ports
2 Power Supplies
2 RAID controllers + expansion ports
2 Power Supplies
2 RAID controllers + Host ports
1 ethernet port +
4 device expansion ports
2 Power Supplies
511
EX1
EX1
DS6800 - Model 1750-EX1
4 to 16 DDMs or Dummy carriers
One Front Display panel
Same for 511 or EX1
Two RAID controllers + expansion
ports
Two Power supplies
Two RAID controllers + expansion
ports
Two Power supplies
Two RAID controllers + Host ports
One Ethernet port +
Four Device expansion ports
Two Power supplies
Student Notebook
Figure 4-8. Disk Capacities SS481.0
Notes:
The capacities of the storage on the DS6000 are shown above. Storage capacity from 1.17
TB up to 67.2 TB is possible.
Disk Capacities
Model With 73 GB
DDMs
with 146 GB
DDMs
with 300 GB
DDMs
1750-511
(16 DDMs)
1.17 TB 2.34 TB 4.80 TB
1750-511+ 6 EX1
(112 DDMs)
8.18 TB 16.35 TB 33.60 TB
1750-511 + 13 EX1
(224 DDMs)
16.35 TB 32.70 TB 67.20 TB
Student Notebook
V3.1.0.1
Uempty 4.2 DS6000 Architecture
Student Notebook
Figure 4-9. Topic: DS6000 Architecture SS481.0
Notes:
DS6000 Highlights
DS6000 Architecture
Serviceability
DS6000 Installation
Topic: DS6000 Architecture
Student Notebook
V3.1.0.1
Uempty
Figure 4-10. DS6000 SS481.0
Notes:
When a host performs a read I/O, the controllers fetch the data from the disk arrays via the
high-performance switched disk architecture. The data is then cached in volatile memory in
case it is required again. Part of the cache is reserved for use as persistent memory and is
used to store write data from the alternate controller and is backed by batteries in case of
power failure or controller failover. Persistent memory takes the place of NVS card used in
the ESS-800.
The controllers attempt to anticipate future reads by the SARC caching algorithm
(sequential prefetching in adaptive replacement cache). Data is held in cache as long as
possible using this smart algorithm. If a cache hit occurs where requested data is already in
cache, then the host does not have to wait for it to be read from the disks. The DS6800 has
4 GB of cache memory.
8 2Gbit FCP/FICON Ports
8 2Gb FC-AL Ports
4 GB Cache
Attaches up to 224 disks
13 expansion drawers
DS6000
Midplane
QDR
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
SDRAM
NVRAM
PPC
750FX
Bridge
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
QDR
Comp
Flash
Enet
Hint
Bridge
SDRAM
PPC
750GX
Flash
Buffer RAID -
Data Protection -
Data Mover
ASIC
PPC
750GX
Data Protection
Data Mover
ASIC
Switch
SES
QDR
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
SDRAM
NVRAM
PPC
750FX
Bridge
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
QDR
Comp
Flash
Enet
Hint
Bridge
SDRAM
PPC
750GX
Flash
Buffer RAID -
Data Protection -
Data Mover
ASIC
PPC
750GX
Data Protection
Data Mover
ASIC
Switch
SES
Midplane Midplane
QDR QDR
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
SDRAM SDRAM
NVRAM
PPC
750FX
Bridge
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
QDR QDR
Comp
Flash
Enet
Hint
Bridge
SDRAM SDRAM
PPC
750GX
PPC
750GX
PPC
750GX
Flash Flash
Buffer RAID -
Data Protection -
Data Mover
ASIC
PPC
750GX
PPC
750GX
Data Protection
Data Mover
ASIC
Switch
SES
QDR
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
SDRAM
NVRAM
PPC
750FX
Bridge
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
QDR
Comp
Flash
Enet
Hint
Bridge
SDRAM
PPC
750GX
Flash
Buffer RAID -
Data Protection -
Data Mover
ASIC
PPC
750GX
Data Protection
Data Mover
ASIC
Switch
SES
QDR
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
SDRAM
NVRAM
PPC
750FX
Bridge
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
QDR
Comp
Flash
Enet
Hint
Bridge
SDRAM
PPC
750GX
Flash
Buffer RAID -
Data Protection -
Data Mover
ASIC
PPC
750GX
Data Protection
Data Mover
ASIC
QDR QDR
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
SDRAM SDRAM
NVRAM
PPC
750FX
Bridge NVRAM
PPC
750FX
Bridge
Fibre Channel
Protocol Engine
Fibre Channel
Protocol Engine
QDR QDR
Comp
Flash
Enet
Hint
Bridge
SDRAM
Comp
Flash
Enet
Hint
Bridge
SDRAM SDRAM
PPC
750GX
PPC
750GX
PPC
750GX
Flash Flash
Buffer RAID -
Data Protection -
Data Mover
ASIC
Buffer RAID -
Data Protection -
Data Mover
ASIC
Buffer RAID -
Data Protection -
Data Mover
ASIC
PPC
750GX
PPC
750GX
Data Protection
Data Mover
ASIC
Data Protection
Data Mover
ASIC
Switch
SES
Student Notebook
Figure 4-11. DS6800 with One Expansion Enclosure SS481.0
Notes:
The DS6800 controller is only half the DS68000 frame. On the other side of the mid-plane
are a FC Switched disk enclosure and 16 DDMs. These are internally attached to the
controllers on FC-AL Loop 0 and cross-connected to each controller for redundancy and
failover capabilities. Additional disk enclosures can be attached to either Loop 0 or Loop 1
via the device adapter ports on the controllers. Up to six disk enclosure EX1 expansion
frames can be added to Loop 0 and seven disk enclosure EX1 expansion frames can be
attached to Loop 1.
Card 1
Controller
chipset
Host adapter
chipset
Power PC
memory
Processor
Persistent
Volatile
chipset
Device adapter
Card 0
Controller
chipset
Host adapter
chipset
Power PC
memory
Processor
Persistent
Volatile
chipset
Device adapter
oo o
oo o
Server enclosure
Expansion enclosure
16 DDM
16 DDM
To next
switch
Server 1 Server 0
Interconnect
2 FC Controller
Cards (DAs)
Four 2Gb/sec ports
to switched FC
attached devices
Base Enclosure
with 4 -16 DDMs
0-13 Expansion
Enclosures with
4-16 DDMs
2 x 1 - 4 2Gb HA
ports
LW / SW
1 or 2 Gb/sec
auto-negotiate
DS6800 with One Expansion Enclosure
Student Notebook
V3.1.0.1
Uempty
Figure 4-12. DS6000 Code SS481.0
Notes:
The code used to implement the DS6000 is similar in many ways to the DS8000. The major
differences are that no LPAR function is implemented and the operating system is an
imbedded Linux instead of AIX for the DS8000. The DS6000 Storage Manager GUI uses
the ICAT Standard and although similar does have additional functions for customer
maintenance. Although similar in look and feel it is a different product from the DS8000
Storage manager and the two product cannot be installed together on one workstation.
Also, for Windows XP, Service pack 2 is required for the DS6000 Storage manager and
only SP1 is required for the DS8000 Storage Manager. It may be easier to place the
DS6000 Storage Manager on a Windows 2000 workstation with SP4 installed. The DSCLI
code is also similar but a different package, and although the DSCLI for the DS8000 works
for most of the configuration commands, it lacks some specialized DS6000 commands.
DS6000 Code
Student Notebook
Figure 4-13. Sequential Prefetching in Adaptive Replacement Cache (SARC) SS481.0
Notes:
DS8000/DS6000 Caching Considerations
The self-tuning, low-overhead, scan-resistant adaptive replacement cache algorithm
outperforms the least recently used algorithm by dynamically responding to changing
access patterns and continually balancing between workload currency and frequency
features.
The adaptive replacement cache is a self-tuning, low-overhead algorithm that responds
online to changing access patterns. ARC continually balances between the currency and
frequency features of the workload, demonstrating that adaptation eliminates the need for
the workload-specific pretuning that plagued many previous proposals to improve LRU.
ARCs online adaptation likely has benefits for real-life workloads due to their richness and
variability with time. These workloads can contain long sequential I/Os or moving hot spots,
changing frequency and scale of temporal locality and fluctuating between stable,
repeating access patterns and patterns with transient clustered references.
SARC basically attempts to determine four things:
When data is copied into the cache.
Which data is copied into the cache.
Which data is evicted when the cache becomes full.
How does the algorithm dynamically adapt to different workloads
SARC uses:
Demand paging for all standard disk I/O
Sequential pre-fetch for sequential I/O patterns
Sequential Prefetching in Adaptive
Replacement Cache (SARC)
Student Notebook
V3.1.0.1
Uempty
Like LRU, ARC is easy to implement, and its running time per request is essentially
independent of the cache size.
A real-life implementation revealed that ARC has a low space overhead0.75 percent of
the cache size. Also, unlike LRU, ARC is scan resistant in that it allows one-time sequential
requests to pass through without polluting the cache or flushing pages that have temporal
locality.
Likewise, ARC also effectively handles long periods of low temporal locality. ARC leads to
substantial performance gains in terms of an improved hit ratio compared with LRU for a
wide range of cache sizes.
ARC replacement policy functions online and is completely self-tuning. Because ARC
maintains no frequency counts, unlike LFU and FBR, it does not suffer from periodic
rescaling requirements. Also, unlike LIRS, ARC does not require potentially unbounded
space overhead. Finally, ARC, 2Q, LIRS, and FBR have constant-time implementation
complexity while LFU, LRU-2, and LRFU have logarithmic implementation complexity.
Student Notebook
Figure 4-14. Disk Enclosure SS481.0
Notes:
In the DS6000, the switch chipset is completely integrated into the controllers. Each
controller contains one switch. Note, however, that the switch chipset itself is completely
separate from the controller chipset. In the picture above each DDM is depicted as being
attached to two separate Fibre Channel switches. This means that with two RAID
controllers, we have four effective data paths to each disk, each path operating at 2
Gb/sec.
When a connection is made between the device adapter and a disk, the connection is a
switched connection that uses arbitrated loop protocol. This means that a mini-loop is
created between the device adapter and the disk.
Dual ported drives
4 Paths to each drive
Uses switched FC-AL protocol to access to DDMs
Direct point-to-point connection from DA to each DDM
Improved RAS and error detection
Easy problem determination
Easier expansion capabilities
Base Enclosure with 4 -16 DDMs
0-13 Expansion Enclosures with 4-16 DDMs
Disk Enclosure
Student Notebook
V3.1.0.1
Uempty
Figure 4-15. Four Data Paths To Every Disk SS481.0
Notes:
The main problems with standard FC-AL access to DDMs are:
The full loop is required to participate in data transfer. Full discovery of the loop via LIP
(loop initialization protocol) is required before any data transfer. Loop stability can be
affected by DDM failures.
In the event of a disk failure, it can be difficult to identify the cause of a loop breakage,
leading to complex problem determination.
There is a performance drop off when the number of devices in the loop increases. To
expand the loop it is normally necessary to partially open it. If mistakes are made, a
complete loop outage can result.
Multiple Storage Ports Connections
RAID Controller Card has connections to
each Fibre Channel switch
Fibre Channel Switches
FC Switch 1
Connects RAID Controller 1 and 2 to
Disk Port 1
FC switch 2
Connects RAID Controller 1 and 2 to
Disk Port 2
Protects against single or multiple
failures
Cable
RAID Controller Card
Port
Or, combination of failures
Use alternate path
Fibre
Channel
Switch
1
Fibre
Channel
Switch
2
1
2
Path 1
Path 3 Path 2
Path 4
Four Data Paths to Every Disk
Student Notebook
Figure 4-16. Components Architecture (1 of 2) SS481.0
Notes:
When a host performs a read I/O, the controllers fetch the data from the disk arrays via the
high-performance switched disk architecture. The data is then cached in volatile memory in
case it is required again. The controllers attempt to anticipate future reads by an algorithm
known as SARC (sequential prefetching in adaptive replacement cache). Data is held in
cache as long as possible using this smart algorithm. If a cache hit occurs where requested
data is already in cache, then the host does not have to wait for it to be read from the disks.
Components Architecture (1 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 4-17. Components Architecture (2 of 2) SS481.0
Notes:
The DS6000 has an internal disk enclosure, so the internal connection to the two
controllers has already been made. When attaching new disk enclosures to Loop 0 shown
above on the top of the diagram, you just need to directly connect out to in ports to the
second enclosure on loop 0. On Loop 1, however, see the bottom of the chart. The initial
connection must be cross-connected to the two controllers for redundancy and pathing.
Components Architecture (2 of 2)
16+2+2 switch
1
16
F
C

s
w
i
t
c
h
F
C

s
w
i
t
c
h
16
1
F
C

s
w
i
t
c
h
F
C

s
w
i
t
c
h
Controller 0
16
1
F
C

s
w
i
t
c
h
F
C

s
w
i
t
c
h
1
16
F
C

s
w
i
t
c
h
F
C

s
w
i
t
c
h
Controller 1
First
expansion
enclosure
Up to 16 DDMs
per enclosure
Third
expansion
enclosure
OUT ports to next enclosure
OUT ports to next enclosure
Cables between
enclosures
Fibre channel
switches
Server
enclosure
Second
expansion
enclosure
L
o
o
p

1
S
e
v
e
n

e
n
c
l
o
s
u
r
e
s

m
a
x
i
m
u
m

p
e
r

l
o
o
p
L
o
o
p

0
S
e
v
e
n

e
n
c
l
o
s
u
r
e
s

m
a
x
i
m
u
m

p
e
r

l
o
o
p
Internal
connections
through
midplane
Raid controller
DISK
CONTROL
ports
RAID controller
DISK EXP ports
Student Notebook
Figure 4-18. DS6000 Host and Device Adapter Ports SS481.0
Notes:
The DS6800 controller card is pictured above. On the left-hand side, surrounded by light
and dark blue boxes (for readers seeing this in black and white, they appear to be light and
dark grey), are the disk expansion and disk control ports respectively. These ports are used
to attach up to a total of 13 expansion enclosures to the server enclosure.
Controller 0
Controller 1
host ports
expansion ports
Ethernet ports
host ports
expansion ports
Power and Fault
indicators
LOOP 0 LOOP 1
DS6000 Host and Device Adapter Ports
Student Notebook
V3.1.0.1
Uempty
Figure 4-19. DS6000 Device Adapter Ports for Disk Enclosure EX1 SS481.0
Notes:
Above, the server enclosure has two expansion enclosures attached to the disk expansion
loop (loop 0). The server enclosure itself is the first enclosure on loop 0. The upper
controller in the server enclosure is cabled to the upper SBOD card in the expansion
enclosure. The lower controller is cabled to the lower SBOD card. In each case cables run
from the disk expansion ports to the in ports of the SBOD card. A second expansion
enclosure has been added by running cables from the out ports on the first expansion
enclosure to the in ports on the second expansion enclosure. At the bottom of the diagram,
dotted lines indicate the potential cabling to add more expansion enclosures to that loop.
IN
OUT
Next expansion enclosure
Server enclosure or
previous expansion enclosure
DS6000 Device Adapter
Ports for Disk Enclosure EX1
Student Notebook
Figure 4-20. DS6000 Switched Disk Expansion (13 Max) SS481.0
Notes:
For a more detailed look at how the switched disk architecture expands in the DS6000,
refer to the figure above. It depicts how the DS6000 is divided into two disk loops. The
server enclosure (which contains the first 16 DDMs) is on loop 0. The first expansion
enclosure is placed on loop 1. This allows for the best performance since we are now using
all four ports on the device adapter chipset. Expansion is achieved by adding expansion
enclosures onto each loop, until each loop has seven enclosures (for a total of 224 DDMs).
The server enclosure is the first enclosure on loop 0, which is why we can only add a total
of 13 expansion enclosures.
DS6000 Switched Disk Expansion (13 Max)
1
16
F
C

s
w
i
t
c
h
F
C

s
w
i
t
c
h
1
16
F
C

s
w
i
t
c
h
F
C

s
w
i
t
c
h
16
1
F
C

s
w
i
t
c
h
F
C

s
w
i
t
c
h
16
1
F
C

s
w
i
t
c
h
F
C

s
w
i
t
c
h
Controller 0
16
1
F
C

s
w
i
t
c
h
F
C

s
w
i
t
c
h
1
16
F
C

s
w
i
t
c
h
F
C

s
w
i
t
c
h
Controller 1
L
o
o
p

1
L
o
o
p

0
First
expansion
enclosure
Server
enclosure
Raid controller
disk control
ports
Raid controller
disk exp ports
Cables between
enclosures
Up to 16 DDMs
per enclosure
Third
expansion
enclosure
Fifth
expansion
enclosure
Second
expansion
enclosure
Fourth
expansion
enclosure
You can configure an
intermix
configuration
in a DS6800
73 GB, 15k rpm
DDMs
145 GB, 10k
rpm DDMs
300 GB, 10k
rpm DDMs
EXP 1
EXP 5
EXP 3
Student Notebook
V3.1.0.1
Uempty
Figure 4-21. DS6000 RAID Array Supported Configurations SS481.0
Notes:
RAID-5 Implementation in the DS6000
In a DS6000, the array site is a group of four disks instead of eight disks as in the DS8000.
A RAID-5 array built on one array site contains either three disks or four disks, depending
on whether the array site chosen had a pre-allocated spare. A three-disk array effectively
uses one disk for parity, so it is referred to as a 2+P array (where the P stands for parity).
The reason only three disks are available to a 2+P array is that the fourth disk in the array
site used to build the array, was used as a spare. This can be referred to as a 2+P+S array
site (where the S stands for spare). A four-disk array also effectively uses one disk for
parity, so it is referred to as a 3+P array. In a DS6000, a RAID-5 array built on two array
sites contains either seven disks or eight disks, again depending on whether the array sites
chosen had pre-allocated spares. A seven-disk array effectively uses one disk for parity, so
it is referred to as a 6+P array (where the P stands for parity). The reason only seven-disks
are available to a 6+P array is that the eighth disk in the two array sites used to build an
array was already a spare. This is referred to as a 6+P+S array site (where the S stands for
spare). An eight-disk array also effectively uses one disk for parity, so it is referred to as a
7+P array.
Controller A or B Loop0
RAID5 using four DDMs Arrays
Array Site1 (drives 1-4) 2+P+S
Array Site2 (drives 5-8) 2+P+S
Array Site3 (drives 9-12) 3+P
Array Site4 (drives 13-16) 3+P
All other Loop0 Array Sites are 3+P for the same drive size and speed. If the drive
size or speed changes the DS6000 creates two spares for the new drives.
RAID5 using eight DDMs Arrays
Array Site1 + Array Site2 (drives 1-8) 6+P+S
Array Site3 + Array Site4 (drives 9-16) 6+P+S
All other Loop0 Array Sites are 7+P for the same drive size and speed. If the drive
RAID10 using four DDMs Arrays
Array Site1 (drives 1-4) 1+1+2S - Still treated by DS6000 as RAID10
All other Loop0 Array Sites are 2+2 for the same drive size and speed. If the drive
RAID10 using eight DDMs Arrays
Array Site1 (drives 1-8) 3+3+2S
All other Loop0 Array Sites are 4+2 for the same drive size and speed. If the drive
size or4 speed changes the DS6000 creates two spares for the new drives.
Controller A or B Loop1
Same rules as Loop 0 above
DS6000 RAID Array Supported Configurations
Student Notebook
Figure 4-22. Preferred Path What Is It? SS481.0
Notes:
Unlike the DS8000 or the ESS 800, the DS6800 uses the concept of preferred path, since
the host adapters are integrated into the controller hardware rather than in separate I/O
bays. What this means is that the attached host systems must be aware that it is
preferential to direct I/O to a particular controller. If an I/O request for a particular LUN is
delivered to a host adapter located in the non-owning controller, that controller uses an
internal data bus to route the request to the owning controller. This reroute of the I/O
request has a performance cost, but does not affect the reliability or availability of the
DS6800.
Storage Management Attributes of System
Affinity of Logical Storage Management
Data Storage primarily managed by owning Cluster Node
Host IO requests are managed by the owning cluster node
System Hardware Architecture
Host Adapter is tightly integrated with Cluster Node
Server Function Processor
Host Adapter Function Processor
Cache Memory
Host IO Requests
To Owning Cluster Node
Managed Locally
The Preferred Path
To Non Owning Cluster Node
Require Traversal of Internal Fabric (PCI-X Bus)
Preferred Path - What Is It?
Student Notebook
V3.1.0.1
Uempty
Notes:
For best reliability and performance, it is recommended that each attached host has two
connections, one to each controller as depicted in the figure above. This allows it to
maintain connection to the DS6800 through both controller failure and HBA or HA (host
adapter) failure.
(Recommended)
Student Notebook
Figure 4-24. DS6800 LSS Single Pathed Host SS481.0
Notes:
If a host were to only have a single path to a DS6800, as depicted above, then it would still
be able to access volumes belonging to all LSSs, but I/O for odd LSS volumes would use
the internal data path between the controllers. However, if controller 0 were to have a
hardware failure, then all connectivity would be lost. Within the figure itself, an HP is a host
port (a fibre port located in the DS6800 controller card), a DA is two device adapter ports
(also located on the DS6800 controller card), and an HBA is a host bus adapter (a Fibre
Channel card located in the attached host).
Inter controller data path
HBA
Single pathed host
Controller 0
HP HP HP HP
DA
Even LSS
Logical
Volumes
Odd LSS
Logical
Volumes
Controller 1
HP HP HP HP
DA
DS6800 LSS Single Pathed Host
Student Notebook
V3.1.0.1
Uempty 4.3 DS6000 Reliability, Availability Serviceability
Student Notebook
Figure 4-25. Topic: DS6000 Reliability, Availability, Serviceability SS481.0
Notes:
DS6000 Highlights
DS6000 Architecture
Serviceability
DS6000 Installation
Topic: DS6000 Reliability,
Availability, Serviceability
Student Notebook
V3.1.0.1
Uempty
Figure 4-26. High Availability and Scalability SS481.0
Notes:
Every four or eight drives form a RAID array and you can choose between RAID-5 and
RAID-10. The configuration process enforces that at least two spare drives are defined on
each loop. In case of a disk drive failure or even when the DS6000s predictive failure
analysis comes to the conclusion that a disk drive might fail soon, the data of the failing
disk is reconstructed on the spare disk. More spare drives might be assigned if you have
drives of mixed capacity and speed. The mix of different capacities and speeds is not
available at general availability, but at a later time.
There are four paths to each disk drive. Using Predictive Failure Analysis, the DS6000 can
identify a failing drive and replace it with a spare drive without customer interaction.
Spare drives
The configuration process when forming RAID-5 or RAID-10 arrays requires that two global
spares are defined in the DS6800 controller enclosure. If you have expansion enclosures,
the first enclosure has another two global spares. More spares could be assigned when
drive groups with larger capacity drives are added.
Redundant and hot-swappable
components
Non-disruptive upgrades and
configuration changes
Switch fabric in disk expansion units
Four data paths to each drive
Preferred path I/O
End to end data checking
Predictive failure analysis for HDDs
Designed for dynamic configuration
changes
Add disk drives
Add storage expansion units
Scale capacity to over 67 TBs
Note: At GA the minimum configuration is eight HDDs and upgrades can be ordered in eight drive increments.
Four HDD minimum configuration and increments are targeted to be available in 1Q05.
High Availability and Scalability
Student Notebook
Predictive Failure Analysis
The DS6800 uses the well-known (xSeries and ESS) Predictive Failure Analysis (PFA) to
monitor the operations of its drives. PFA takes preemptive and automatic actions before
critical drive failures occur. This functionality is based on a policy-based disk
responsiveness threshold and takes the disk drive offline. The content of the failing drive is
reconstructed from data and parity information of the other RAID array drives on the global
spare disk drive.
While doing so, service alerts are invoked, the failed disk is identified with Light Path
indicators and an alert message pop-up occurs on the management server.
The first and the third array sites created on each loop, each contribute one DDM to be a
spare. So at least two spares are created per loop, which serve up to seven enclosures,
depending on the disk intermix.
Spare creation
There are four array sites in each enclosure of the DS6000. The first and third array sites
created on each loop are used to supply spares. This normally means that two spares are
created in the server enclosure and two spares in the first expansion enclosure. Spares are
created as the array sites are created, which occurs when the DDMs are installed. After
four spares have been created for the entire storage unit, no more spares are normally
needed.
Where DDMs with different sizes, but the same RPM, exist in the complex, the spares are
taken from the array sites with the larger sized DDMs. This means in most cases the
DS6000 continues to have only four spares for the entire complex regardless of DDM size
intermix.
Disk scrubbing
The DS6000 periodically reads all sectors on a disk. This is designed to occur without any
interference to application performance. If ECC-correctable bad bits are identified, the bits
are corrected immediately by the DS6000. This reduces the possibility of multiple bad bits
accumulating in a sector beyond the ability of ECC to correct them. If a sector contains data
that is beyond ECC's ability to correct, then RAID is used to regenerate the data and write
a new copy onto a spare sector on the disk. The scrubbing process applies to both array
members and spare DDMs.
Student Notebook
V3.1.0.1
Uempty
Figure 4-27. Server Failover and Failback SS481.0
Notes:
Failover
Server Failover and Failback
Student Notebook
Figure 4-28. NVS Recovery After Complete Power Loss SS481.0
Notes:
The DS6000 is equipped with two BBUs and two power supplies. This provides
redundancy in case of either an external power failure or an internal power subsystem
failure. The DS6000 is able to control the state of the power supplies in the expansion
enclosures via in-band commands sent through the device adapter Fibre Channel
connections.
In the event of a BBU failure, the RAID controller that relies on that BBU for data protection
will remove itself from service and go offline until its BBU is fully charged. If both BBUs
were to fail, then the entire system would have to go offline until the problem is corrected.
This possibility is highly unlikely.
All power components are hot pluggable and can usually be replaced without employing
the DS Storage Manager GUI.
DS8000
Scenario at power off
All HA I/O blocked
Each server fcopies NVS data to internal
disk
Two copies per server
When copy process complete, each
server shuts down AIX
When AIX shutdown completes for both
servers (or time out expires), the
DS8000 is powered down
Scenario at power on
Processor complexes power-on and
perform power on self test
Each server boots up
During Boot, server detects NVS data on
its disks and destage it to FC-AL disks
When battery units reach a certain level
of charge, the servers come online.
NVS contents preserved indefinitely
DS6000
Preserves contents of controller memory for
at least 72 hours
Designed to be replaced every four years
Preserve all data in memory while input
power is not available
When power becomes available again
DS6800 controllers boot up
But leave the NVS portion of controller
memory untouched
During init process, NVS data area
examined
If any undestaged write data is found, it
is destaged to disk prior to the controller
coming online
NVS contents preserved 72 hours (like
ESS)
NVS Recovery After Complete Power Loss
Student Notebook
V3.1.0.1
Uempty
Figure 4-29. Major Components BBUs SS481.0
Notes:
The BBUs provides battery backup for the cache-persistent memory for 72 hours in case of
power failure.
Battery BackUp Units (BBUs)
Battery Units provide power in event of loss of AC Power
Affinity to specific RAID Controller Card
Capacity Designed to Holdup All Memory on Each RAID Controller
Card
72-Hour Backup Window
Guaranteed during 4
th
year of operation
New Design
Architecture similar to ESS model 800 NVS battery units
Major Components - BBUs
Student Notebook
Figure 4-30. Serviceability SS481.0
Notes:
The DS6000 uses a light path guidance strategy that allows the user in many cases to both
detect and repair a failure without using a GUI. However, if desired, guided maintenance in
the form of a GUI with animation is also available. This is done by using the DS Storage
Manager GUI. Most parts can be replaced without this GUI, though this may not always be
the case depending on what parts have failed and the failure mode of those parts.
Intuitive status indicators on front and rear panels
Light Path Diagnostics
Call home
Remote management
Customer replaceable components
Manage multiple IBM TotalStorage products through IBM
TotalStorage Productivity Center (TPC)
Serviceability
Student Notebook
V3.1.0.1
Uempty
Figure 4-31. DS6000 Diagnostics SS481.0
Notes:
Within all IBM machines, spare parts are divided into two categories: CRU parts (customer
replaceable units) and FRU parts (field replaceable units). If a part is designated a CRU,
this implies that it can be safely and easily replaced by an end user with few or no tools. If a
part is designated a FRU, then this implies that the spare part needs to be replaced by an
IBM Service Representative. Within CRU parts, there are currently two tiers: Tier 1 CRUs
are relatively easy to replace, while Tier 2 CRUs are generally more expensive parts or
parts that require more skill to replace.
Tier 1 CRU parts:
Battery backup units
Cables - Ethernet, serial, fibre optic, and power
Disk drive modules
Operator panels - front and rear display
Power supplies
RAID controller and SBOD controller cards
SFPs (2 Gbps small form factor pluggable fibre optic
Rear Display Panel
RAID Controller
Battery
RAID Controller
Service Card
Power Supply and Cooling
I B M
Rear View
Front View
Front Display Panel
DS6000 Diagnostics
Student Notebook
Figure 4-32. Light Path Diagnostics In MR 1750 SS481.0
Notes:
An example of the use of the light path guided repair is a disk failure. The user sees that
the System Alert Indicator is on, and that a DDM fault indicator is also lit. They refer to the
Service Card shipped with the DS6000 (refer to location of Service Card on previous slide),
and using the simple replacement instructions detailed there, they remove and replace the
failed DDM with a new one. After replacing the DDM, the System Alert Indicator is turned
off automatically.
Front Display Panel
Rear Display Panel
Primary and Secondary Indicators
Condition indicators and CRU location
Identify
Blue Light - Identify all elements, enclosures group
together to form in one system
Blue Beacon Summary rack-level identification
System Alert
System Attention
Consistent with xSeries light path
Many CRUs can be replaced using light path only
(no GUI)
System Power
System Identity
System Alert
System Attention
Data in Cache on Battery
Fault on Rear
Fault in External Enclosure
Rear Display Panel
Front Display Panel
Light Path Diagnostics in MR 1750
Student Notebook
V3.1.0.1
Uempty
Figure 4-33. DS6000 Rear Panel SS481.0
Notes:
System Information (amber): Normally off. If it is on solid, then an error has occurred that
cannot be fixed by light path diagnostics. To turn this light off you need to use the GUI to
correct the error condition. This may be as little as to just view the error log.
Lightpath IDENTIFY Switch (blue): The lower of the two blue buttons you push this
button to activate the system identify indicator
Lightpath REMIND Switch (blue): The upper of the two blue buttons; you push this button
to re-activate the light path remind. This allows you to identify a failed component that
requires replacement.
Rack identify connector: Allow a user to attach the enclosure to SServer rack identifier
hardware. This allows you to identify in which rack a particular DS6000 storage or
expansion enclosure is located.
CRU Fault on Rear/Front (amber): Normally off. If it is on solid then a fault has occurred
within a CRU in the rear /front of the enclosure and can be repaired using the light path
indicators.
System Information (amber): Normally off. If it is on solid, then an error has occurred that cannot be
fixed by light path diagnostics. To turn this light off you need to use the GUI to correct the error
condition. This may be as little as to just view the error log.
Lightpath IDENTIFY Switch (blue): The lower of the two blue buttons, you push this button to activate
the system identify indicator.
Lightpath REMIND Switch (blue): The upper of the two blue buttons; you push this button to
reactivate the light path remind. This allows you to identify a failed component that requires
replacement.
Rack identify connector: Allow a user to attach the enclosure to eServer rack identifier hardware. This
allows you to identify in which rack a particular DS6000 storage or expansion enclosure is located.
CRU Fault on Rear/Front (amber): Normally off. If it is on solid then a fault has occurred within a CRU
in the rear /front of the enclosure and can be repaired using the light path indicators.
DS6000 Rear Panel
Student Notebook
Figure 4-34. Rear Panel Indicators SS481.0
Notes:
The DS6000 controller cards have fault and power indicators to alert the user to a fault in
the controller or a power problem or Ethernet connectivity.
Enclosure panel
RAID controller card
Server Enclosure Rear
Power
Status
Service
Fault
Host
Port Activity / Service Fault
Device
Ethernet Port Status /
Activity
Expansion
Light Path Diagnostics for a disk: System Alert
Indicator and DDM Fault indicator
Rear Panel Indicators
Student Notebook
V3.1.0.1
Uempty
Figure 4-35. DS6000 Maintenance and Support: Call Home and Remote Support SS481.0
Notes:
Remote support
Problem notification:
Light Path Diagnostics and Controls, or Alert Message on the Management Server
Message sent to IBM technical support
IBM can:
Contact customer to provide assistance
Remotely access management server
- If customer allows access through firewall, customer initiates remote support from
Management GUI
Assistance is provided by:
Service technicians provide the resolution procedures for customer execution
Service personnel remotely login to the customers management server
- Interacts with the storage system through the management GUI and takes
appropriate actions to resolve system issue
Call home
Enables IBM to have accurate
system configuration
information
Weekly heartbeat
Configuration data stored for
support assistance (State save,
PE Package)
Remote support
Immediate problem notification
to IBM
Interactive problem assistance
Parts ordering
Software updates
Internet
Firewall
Firewall
DS6000
Management
Server
Mail
Server
DS6000
Mail
Server
DS6000 Maintenance and Support:
Call Home and Remote Support
Student Notebook
Figure 4-36. Logs: Realtime SS481.0
Notes:
The DS6000 Storage Manager provides access using the GUI and users can view several
logs for alerts, audit trails, events and user access.
Severity
All
Attention
Event
Heartbeat
Problem
Test
Status
All
Open
Closed
Logs: Real-time
Student Notebook
V3.1.0.1
Uempty
Figure 4-37. Log Display: Example SS481.0
Notes:
The Logs on the DS6000 can be view from the DS6000 Storage Manager. From the
System Information Panel various logs can be selected and viewed.
Select Action
View Details
Close
Create test
Table Actions
Show Filter Row
Clear all filters
Edit sort
Clears all sorts
Log Display: Example
Student Notebook
Student Notebook
V3.1.0.1
Uempty 4.4 DS6000 Installation
Student Notebook
Figure 4-38. Topic: DS6000 Installation SS481.0
Notes:
DS6000 Highlights
DS6000 Architecture
Serviceability
DS6000 Installation
Topic: DS6000 Installation
Student Notebook
V3.1.0.1
Uempty
Figure 4-39. DS6000 Installability SS481.0
Notes:
The successful installation of a DS6000 requires careful planning. The main considerations
when planning for the physical installation of a new DS6000 are the following:
Floor loading
Floor space
Electrical power
Operating environment
Cooling
Management console
Host attachment and cabling
Network and SAN considerations
Always refer to the most recent information for physical planning in the IBM TotalStorage
DS6000 Introduction and Planning Guide, GC26-7679.
Designed for customer install
Simplified GUI
Remote configuration
Easy installation wizards
DS6000 Installability
Student Notebook
Figure 4-40. Installation Planning SS481.0
Notes:
To install a DS6000 in your environment you have to plan for the Ethernet infrastructure
that the DS6000 has to be connected to. You have to provide some TCP/IP addresses and
you need an Ethernet switch or some free ports on a existing switch.
This following settings are required connect the DS6000 series to a network:
Controller card IP address
You must provide a dotted decimal address that you assign to each storage server
controller card in the DS6800. Since there are two controllers, you need two TCP/IP
addresses.
DS Storage Manager IP address
You need another TCP/IP address for the computer where you run the DS Storage
Manager.
Gateway
DS6800
User provided
Ethernet switch
Intranet Internet
call home
DS Storage Manager software
on user provided
DS management console
IP-1
(server0)
IP-2
(server1)
IP-3
Administrator accessing
DS Storage Manager
Installation Planning
Student Notebook
V3.1.0.1
Uempty
Provide the dotted decimal or symbolic name address of the gateway (for example,
9.123.123.123 or sanjosegate).
Subnet mask
Provide the dotted decimal address of the subnet (network) mask.
Primary domain name server (DNS)
Provide the Host name and IP address if you are using a domain name server.
Alternate domain name server (DNS)
You can optionally provide an alternate DNS.
Simple Network Management Protocol (SNMP) destination
Student Notebook
Figure 4-41. Storage Management Console (SMC) SS481.0
Notes:
Network considerations:
MC is a firewall/proxy for incoming traffic
No IP forwarding, no gateway functionality
Many standard services (telnet, ftp, ) do not exist
VPN (point-to-point) from MC to IBM over internet, or modem. If Internet, firewall ports
to open:
- 500 udp
- 500 esp (VPN)
- 4500 udp
- Destination 207.25.252.196 192.42.160.16 207.25.252.198
No TCPIP connection from the outside into the MC, except via the VPN
ASCII Modem dial-in can be used to initiate VPN TCPIP call back
Customer supplied PC
1.4 GHz Pentium 4
256 KB cache
256 MB Memory
1 GB disk space for the storage management software
1 GB work space per managed Integrated TAID Controller (IRC)
IP Network connectivity to each RAID Controller Card
IP Network connectivity to external network (Call Home and Remote Support)
Serial connectivity to your storage unit
Supported Browsers
Internet Explorer 6.x
Opera 7.23
Netscape 6.2
Netscape 7.x
DS Storage Manager is web-based (HTML) graphical user interface (GUI)
Online configuration management support.
Online configuration, copy services, and CLI are available via a Web browser interface installed
on the DS storage management console
Required for configuration, problem reporting, and maintenance
Supports multiple DS6000s
Customer Download Code to SMC
Customer Uses SMC GUI to push code to the DS6000
Customer Activates code on DS6000
Storage Management Console (SMC)
Student Notebook
V3.1.0.1
Uempty
Figure 4-42. DS Storage Manager Supported Operating Systems SS481.0
Notes:
The support for the Storage Manager is as shown above. Windows XP requires SP2 which
may not be readily available.
RedHat Advanced Server 2.1 on Intel (DS8000 only)
Windows 2000 Server SP4
Windows 2000 Advanced Server SP4
Windows 2000 Professional SP4
Windows XP Professional SP1, SP1a (Offline only)
Windows XP Professional SP2
Windows 2003 Server Standard and Enterprise
DS Storage Manager
Supported Operating Systems
Student Notebook
Figure 4-43. DS6000 SMC Network Topology SS481.0
Notes:
In order to use remote service support, the user must allow a VPN connection. If the user
decides to ask IBM for help, and IBM needs to access the DS6000 remotely, then the user
must provide connectivity from the DS Management Console to an IBM service support
center. The DS Management Console must be connected to the DS6000 to enable IBM to
access the DS6000 over this network to analyze the error condition.
DS6000 series
SMC
Client's Ethernet switch
Customer
network
Internet
Firewall
To IBM Remote
Support
DS6000 SMC - Network Topology
Student Notebook
V3.1.0.1
Uempty
Figure 4-44. HA with Storage Management Console (SMC) SS481.0
Notes:
Connectivity to the DS6000 series from the DS Management Console is needed to perform
configuration updates to the DS6000 series. Connectivity to both DS6800 controllers is
required to activate updates.
The figure above illustrates the DS Management console, optionally connected to the
DS6000 by redundant Ethernet switches, but redundant switches are not a requirement.
The switches must be part of the same subnet so that the controllers in the DS6000 can
communicate with each other through the Ethernet.
Primary DS6000 series
DS Management Console
Secondary DS6000 series
Ethernet switch
Alternate DS Management Console
Alternate Ethernet switch
inter-switch link
HA with Storage Management Console (SMC)
Student Notebook
Figure 4-45. Installing Storage and Server Enclosures in a Rack SS481.0
Notes:
Remove the hardware resources. This section provides resource removal instructions. The
purpose of resource removal is to minimize the weight of the DS6000 before you install it in
the rack. However, if you have three people available to lift and install the DS6000 in a
rack, you might not find it necessary to remove the resources before installation. If this is
the case, you can skip the resource removal instructions provided in this section.
Position the rack
Airflow is front to back
Install the support rails
Remove the CRUs and front display panel
Disk drive modules
Power Supplies
Rear display panel
Battery backup units
Servers cards
Install server enclosure and storage enclosures in the rack
Replace the CRUs and front display panel
Install the host systems and I/O adapters
Supported host adapters and drivers, go to the interoperability matrix.
http://www-1.ibm.com/servers/storage/disk/ds6000/interop.html
Fibre Channel host bus adapters supported fibre channel HBAs, firmware
and device information.
http://knowledge.storage.ibm.com/HBA/HBASearchTool.
Installing Storage and
Server Enclosures in a Rack
Student Notebook
V3.1.0.1
Uempty
Figure 4-46. DS6000 Server Enclosure Connection Diagram SS481.0
Notes:
This graphic shows an overview of all of the connections in the server enclosure.
Power supply connector
Power control switch
Disk Exp Port 0
Disk Exp Port 1
Disk Ctlr Port 0
Disk Ctlr Port 1
Ethernet port
SES serial port
SMP serial port
Host Port 0
Host Port 1
Host Port 2
Host Port 3
DS6000 Server Enclosure Connection Diagram
Student Notebook
Figure 4-47. Connect Power Cords SS481.0
Notes:
The power supplies are redundant and requires two separate power sources for
redundancy. A UPS is recommended for area where power fluctuations are typical.
Each IRC or SBOD uses two standard power cords
Right and left power cord to different PDUs
To maintain power redundancy, make sure that each rack PDU
is connected to separate independent external power circuit
Your power cords are you on/off switch
Connect Power Cords
Student Notebook
V3.1.0.1
Uempty
Figure 4-48. Connect Hosts SS481.0
Notes:
The host connections are FCP LC connectors and can be routed to a SAN switch or
directly connected to a host.
Install an SFP in a host port on the 511 processor card
In pairs by type (LW or SW)
Server 0
Server 1
Connect Hosts
Student Notebook
Figure 4-49. Connect Storage Enclosures SS481.0
Notes:
The storage disk enclosures can be connected to increase the amount of storage available.
The are two FC-AL loops and Loop 0 begins internally with the 16 DDMs in the 1750-511
and can be connected to six more expansion disk enclosures. Loop 1 is a separate FC-AL
loop and can be connected to seven disk enclosures.
Recommended sequence for adding storage enclosures is to alternate each
storage enclosure between Loop 0 and Loop 1, starting with Loop 1.
First storage enclosure would be on Loop 1 (up to 7 Enclosures)
Second storage enclosure would be on Loop 0 (Up to six EX1s)
Total of 13 storage enclosures
Loop 0 and Loop1 have different physical cabling connections from IRC to
SBOD

EX1 #13
EX1 #1
EX1 #3
EX1 #5

EX1 #12
EX1 #2
EX1 #4
16
Internal
Disks
Connect Storage Enclosures
Student Notebook
V3.1.0.1
Uempty
Figure 4-50. Setting the IP Address SS481.0
Notes:
The initial network IP address is set using a serial port and a Null modem cable to a
workstation and using Netterm or hyperterm to access the DS6000 and set the IP address.
Use a terminal emulator to connect to
the server enclosure through the serial
port located on the processor card.
Remote connection setting
Remote connection value
Bits per second 38400
Data bits 8
Parity None
Stop bits 1
Flow control Hardware
Logon: Guest Password: Guest
Select: Configure network parameters
from the Main Menu
To set the IP address:
Use static IP address
Set the IP address for this node
Set the IP address for other node
Set Network mask for this node
Set network mask for other node
Select Back to Network Configuration.
Select Back to Main Menu.
Select Apply changes and exit
Setting the IP Address
Student Notebook
Figure 4-51. Disk Storage Feature Activation (DSFA) is a Customer Web Application SS481.0
Notes:
The DFSA Web site is used to obtain license keys.
Management of Licensed Features and Activation is
a customer function
DSFA is designed to help customers accomplish
this
Access is at http://www.ibm.com/storage/dsfa
Used to retrieve 32-digit Feature Activation Code
for DS6000 and DS8000 licensed functions
That is, OEL, PTC, RMC, RMZ, or PAV
xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx
Used to manage Licensed Functions on DS6000
and DS8000
Examples of when Feature Activation codes are
needed
Prior to first configuration or
When capacity is added to the license
or
When deactivating a license or
If reallocation of function authorizations
between images of LPAR models

Disk Storage Feature Activation (DSFA) is a
Customer Web Application
Student Notebook
V3.1.0.1
Uempty
Figure 4-52. Starting DSFA SS481.0
Notes:
Starting DSFA
Three pieces of information needed from DS Storage Manager
From Manage Hardware => Storage Unit => Properties =>
General
Model Number (921,922,9A2,511)
Machine Serial Number (Last seven digits of MTS field)
Machine Signature (all 16 digits) xxxx-xxxx-xxxx-xxxx
Connect to the DSFA Application at
http://www.ibm.com/storage/dsfa
DS6000
Always provide the DS6000 Order Confirmation Code from the
Product Order Reference Document shipped with the product or MES
Student Notebook
Figure 4-53. License Activation (Enter 32-Digit Code) SS481.0
Notes:
Activation Code can be imported into DS Manager
Downloaded to PC from DSFA Web Application
Uploaded to DS Manager
From hard drive or diskette (or whatever)
Manage Hardware => Storage Images => Apply Activation Codes
=> Import Codes; then select file
Activation Code can be entered into DS Manager
xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx
License Activation (Enter 32-Digit Code)
Student Notebook
V3.1.0.1
Uempty
Figure 4-54. DS6000 - Select DS6000 Series Machine SS481.0
Notes:
DS6000 - Select DS6000 Series Machine
Student Notebook
Figure 4-55. DS6000 - View Feature Activation Details SS481.0
Notes:
DS6000 - View Feature Activation Details
Student Notebook
V3.1.0.1
Uempty
Figure 4-56. Storage Complex Real-Time Functions SS481.0
Notes:
This Select Action box displays the function which are available in the Real-time Storage
Manager GUI for the DS6000. These functions are not seen in the DS80000 GUI because
most of these functions are part of the HMC function performed by the CE, but for a
DS6000, the customer would be handling the maintenance of the DS6000.
The Setup of the Storage Complex, which is the SMC and its connected DS6000 Storage
Units and the assignment of the DS6000 Storage Unit are required to get the Storage Unit
machine signatures from the GUI using the Storage Unit Properties. This data is needed to
get the License Keys from the DFSA Web site.
Storage Complex Real-time Functions
Student Notebook
Figure 4-57. Storage Unit - Real-time Functions SS481.0
Notes:
This Select Action box displays the function which are available in the Real-time Storage
Manager GUI for the DS6000. These functions are not seen in the DS80000 GUI because
most of these functions are part of the HMC function performed by the CE, but for a
DS6000, the customer would be handling the maintenance of the DS6000.
There are many functions in the Storage Unit screen to assist the customer in maintaining
the DS6000. A performance measure, a contact info setup, problem determination info,
status and firmware updates.
Storage Unit - Real-time Functions
Student Notebook
V3.1.0.1
Uempty
Figure 4-58. Assign the Storage Unit SS481.0
Notes:
This Assign Storage Unit is something that needs to be done to get to the Storage Unit
Properties. The Properties is where the Storage Unit machine Signature is located. This
field is required to access the DFSA Web site for license keys.
Assign the Storage Unit
Student Notebook
Figure 4-59. Storage Unit Properties SS481.0
Notes:
The Storage Unit Properties is where the Storage Unit machine Signature is located. This
field is required to access the DFSA Web site for license keys.
Storage Unit Properties
Student Notebook
V3.1.0.1
Uempty
Figure 4-60. DFSA Feature Activation Web Site SS481.0
Notes:
DFSA Feature Activation Web Site
Student Notebook
Figure 4-61. Update Activation Codes SS481.0
Notes:
The DFSA Web site is access for the license keys. These can be copied or downloaded
and placed into the field of the screen shown above. Each field activate one of the features
purchased. OEL, is for configuration, PTC is for FlashCopy, Remote Copy is PPRC and
PAV is for z/OS Parallel Access Volume support.
Update Activation Codes
Student Notebook
V3.1.0.1
Uempty
Figure 4-62. Enter Customer Account Information SS481.0
Notes:
This screen is allows the customer to enter contact information needed for IBM Support to
work with the customer.
Enter Customer Account Information
Student Notebook
Figure 4-63. Enter Customer Shipping Information SS481.0
Notes:
This screen allows the customer to enter contact information needed for IBM Support to
Enter Customer Shipping Information
Student Notebook
V3.1.0.1
Uempty
Figure 4-64. Enter Customer Contact Information SS481.0
Notes:
This screen allows the customer to enter contact information needed for IBM Support to
Enter Customer Contact Information
Student Notebook
Figure 4-65. Set up Call Home Function SS481.0
Notes:
This is the Call home function setup.
Set up Call Home Function
Student Notebook
V3.1.0.1
Uempty
Figure 4-66. Update DS6000 Firmware SS481.0
Notes:
This is the firmware update function setup.
Update DS6000 Firmware
Student Notebook
Figure 4-67. Activate Remote Support SS481.0
Notes:
This is the remote support connection setup.
Activate Remote Support
Student Notebook
V3.1.0.1
Uempty
Figure 4-68. View Performance Reports SS481.0
Notes:
This is the Performance Reports function of the DS6000 GUI.
View Performance Reports
Student Notebook
Figure 4-69. Volume Performance Reports SS481.0
Notes:
This is the Volume Performance Reports are displayed as part of the DS6000 GUI.
Volume Performance Reports
Student Notebook
V3.1.0.1
Uempty Checkpoint
1. T/F The DS6000 is equipped with a pair of 2-way PowerPC
processors and provides redundant control of the storage arrays
cluster into Logical Partitions called LPARs which divides the
hardware components into two separate controller which can
3. T/F The DS6000 System uses switched FC-AL disk enclosures
which improves disk performance and error detection capabilities.
4. The DS6000 System supports the following disk devices.
a. 2 Gb 73 GB 15,000 disk drives
b. 2 Gb 146 GB 10,000 disk drives
c. 2 Gb 300 GB 10,000 disk drives
d. All of the above
5. T/F The DS6000 System can be configured offline using a
Simulated DS6000 Storage Manager interface.
Student Notebook
Notes:
Unit Summary
Identify the components and features of the IBM TotalStorage
DS6000 Storage Server
Understand the IBM TotalStorage DS6000 architecture
Explain the IBM TotalStorage DS6000 reliability, availability, and
serviceability
Identify the IBM TotalStorage DS6000 installation process
Explain the IBM TotalStorage DS6000 licenses
Student Notebook
Copyright IBM Corp. 2005 Unit 5. DS8000 Hardware Management Console 5-1
V3.1.0.1
Uempty
Unit 5. DS8000 Hardware Management Console
The DS8000 Hardware Manager Console is the focal point of external
communications with the DS8000 subsystem. This unit discusses the
setup and use of the HMC or external S-HMC.
Describe the DS8000 Hardware Management Console
Describe Network configuration setup
Understand how use the VPN connections to the HMC
Accountability:
Checkpoint
References
Concepts
Guide
Student Notebook
Notes:
Unit Objectives
Describe the DS6000/DS8000 Storage Manager installation
Describe how to access the Storage Manager
Describe the simulated mode of the Storage Manager
Describe how to define the physical hardware using the simulated
manager
Describe how to define arrays, ranks and extent pools
Describe how to define volumes, host connections and volume
groups
Student Notebook
V3.1.0.1
Uempty 5.1 DS8000 Storage Management Console
Student Notebook
Figure 5-2. DS8000 Management Console Overview SS481.0
Notes:
The S-HMC feature looks similar to a laptop. It consists of a workstation processor,
keyboard, monitor, modem, and Ethernet cables. The S-HMC is a closed system
appliance.
TotalStorage Management Console : MC
Other possible names : HMC or S-HMC
On DS6000 : SMC
Storage Management Console is the focal point for configuration, copy
services management, and maintenance activities.
Dedicated workstation physically located (installed) inside your DS8100
and DS8300 and can automatically monitor the state of your system,
notifying you and IBM when service is required.
The Management Console can also be connected to your network to
enable centralized management of your system using the IBM
TotalStorage DS Command-Line Interface or storage management
software that uses the IBM TotalStorage DS Open API.
An external Management Console is available as a optional feature and
can be used as a redundant management console for environments with
high-availability requirements.
Internal Management Console feature code :1100
External Management Console feature code 1110
DS8000 Management Console Overview
Student Notebook
V3.1.0.1
Uempty
Figure 5-3. DS8000 Management Console Features SS481.0
Notes:
IBM Service personnel located outside of the customer facility log in to the S-HMC to
provide service and support. The methods available for IBM to connect to the S-HMC are
configured by the IBM SSR at the direction of the customer, and may include dial-up only
access or access through the high-speed Internet connection.
The DS Storage Manager on the internal S-HMC provides only real-time configuration, as
opposed to offline configuration. The user may also opt to install an additional DS Storage
Manager on the users own workstation. With this DS Management Console, the user is
able to perform both online and offline configurations. In order to perform online
configuration the users workstation must be connected to the S-HMC that is connected to
the DS8000.
DS8000 Management Console Multiple Functions:
Local Service
Interface for local service personnel
Remote Service
Call home and call back
Storage Facility Configuration
LPAR Management (HMC)
Supports logical storage configuration via preinstalled
TotalStorage DS Storage Manager in online mode only
Network Interface Server for logical configuration and invocation of
advanced Copy Services functions
Service appliance (closed system)
Connection to Storage Facility (DS8000) through redundant private
Ethernet networks only
DS8000 Management Console Features
Student Notebook
Figure 5-4. Hardware Management Console SS481.0
Notes:
The S-HMC is a closed system appliance. Each DS8000 has an internal S-HMC (feature
code 1100) in the base frame, together with a pair of Ethernet switches installed and cabled
to the processor complex or external S-HMC, or both. It is a focal point with multiple
functions such as:
Storage configuration
LPAR management
Advanced Copy Services invocations
Interface for local service personnel
Remote service and support
N
o
n
-
V
o
l
a
t
i
l
e

R
A
M
POWER5 Hypervisor
Partition 1
Unassigned
Resources
LPAR
Allocation
Tables
AIX AIX
Processors
Mem Regions
I/O Slots
Partition 2
Status
Command/Response
Virtual Consoles
Ethernet
Service
Processor
Perm Temp
HMC HMC
P5 HMC Features:
Logical partition configuration
Dynamic logical partitioning
Capacity and resource management
System status
HMC management
Service functions (microcode
update,)
Remote HMC interface
Hardware Management Console
Student Notebook
V3.1.0.1
Uempty
Figure 5-5. DS8000 MC Network Configuration SS481.0
Notes:
The customer Ethernet port indicated is the primary port to be used to connect to the
customer network. The empty Ethernet port is normally not used. Corresponding private
Ethernet ports of the external S-HMC (FC1110) would be plugged into port 2 of the
switches.
Storage Management Console network consists of:
Redundant private Ethernet networks for connection to the Storage
Facilities
Customer network configured to allow access from the HMC to IBM
through a secure Virtual Private Network (VPN)
Call home to IBM Services is possible through Dial-up or Internet
connections VPNs
Dial-up or Internet connection VPNs is also available for IBM service
to provide Remote Service and Support
Recommended configuration is to connect MC to customers public
network for support
Support will use WebSM GUI for all service actions
Downloading of problem determination data favors the use of a
high speed network
Network connectivity and remote support is managed by the HMC
DS8000 MC - Network Configuration
Student Notebook
Figure 5-6. DS8000 MC and a Pair of Ethernet Switches SS481.0
Notes:
DS8000 MC and a Pair of Ethernet Switches
Every DS8000 base frame comes with a pair of Ethernet switches installed and
cabled to the processor complex.
The MC has:
Two built-in Ethernet ports - the MC private Ethernet ports shown are
configured into Port 1 of each Ethernet switch to form the private DS8000
networks
One dual-port Ethernet PCI adapter
One PCI modem for asynchronous call home support
The customer Ethernet port indicated is the primary port to be used to connect to
the customer network.
The empty Ethernet port is normally not used.
Corresponding private Ethernet ports of the external MC (FC1110) would be
plugged into port 2 of the switches as shown into next foil.
To interconnect two DS8000 base frames, FC1190 would provide a pair of 31
meter Ethernet cables to connect from port 16 of each switch in the second base
frame into port 15 of the first frame.
If the second MC is installed in the second DS8000, it would remain plugged
into port 1 of its Ethernet switches.
Student Notebook
V3.1.0.1
Uempty
Figure 5-7. DS8000 MC and Ethernet Switches Plugging (Back View) SS481.0
Notes:
Shown is the back of a single SMC and a pair of Ethernet switches.
Every DS8000 base frame comes with a pair of Ethernet switches installed and cabled
to the processor complex.
The SMC has two built-in Ethernet ports, one dual-port Ethernet PCI adapter, and one
PCI modem for asynchronous call home support.
The SMC private Ethernet ports shown are configured into Port 1 of each Ethernet
switch to form the private DS8000 networks.
The customer Ethernet port indicated is the primary port to be used to connect to the
customer network.
The empty Ethernet port is normally not used.
PCI
Modem
DS8000 MC and Ethernet
Switches Plugging (Back View)
Student Notebook
Figure 5-8. DS8000 MC Network Topology SS481.0
Notes:
The diagram above shows a typical redundant S-HMC configuration. In this configuration,
we have DS8000 Subsystems with internal S-HMC and, via the customer network (external
S-HMC), connected to the network. These two networks are the private Ethernet networks
of the DS8000. MC are also connected to the customers network by way of the customer
Ethernet ports on the pair of Ethernet switches that are installed at installation time.
Remote access via VPN may also be set up for IBM Remote support access if required.
Customer
Network
Customer
Network
Internet
Internet
IBM
Network
IBM
Network
DS8000 Subsystems
MC
Integrated
Firewall
Proxy
Opt. Firewall
provided by
customer
Redundant
Ethernet
Fabric
eth
eth
eth
modem
DMZ
DMZ
MC : Hardware Management Console
DMZ: Demilitarized Zone
VPN: Virtual Private Network
eth: Ethernet Port
VPN
VPN
IBM Remote Support
Infrastructure
DS8000 MC Network Topology
Student Notebook
V3.1.0.1
Uempty
Figure 5-9. DS8000 and DS6000 Remote Access Features SS481.0
Notes:
Call home is the capability of the S-HMC to contact IBM support services to report a
problem. This is referred to as call home for service. The S-HMC also provides
machine-reported product data (MRPD) information to IBM by way of the call home facility.
The MRPD information includes installed hardware, configurations, and features. The
storage plex uses the call home method to send heartbeat information to IBM and by doing
this, ensures that the S-HMC is able to initiate a call home to IBM in the case of an error.
Remote access is required when the local service personnel cannot correct problems with
the storage plex, and IBM product engineer assistance is required to resolve the problems.
In this case, the S-HMC initiates a call home for service, and IBM support service initiates a
remote access session.
Call Home : Automatic Problem Reporting
IBM DS6000 and DS8000 are designed with a Call Home function
In the event of a failure, the Call Home function generates a
trouble ticket with the IBM support organization
IBM support determines the failing component and dispatches a
customer engineer with the replacement part
Remote Service and Support
With remote support enabled, IBM technical support can log into
the management console to troubleshoot a problem, view logs,
dumps, and traces interactively
This can reduce lag time to send such information to IBM and can
shorten problem determination time
In the case of complex problems, IBM technical support teams
can engage a specialist quickly to resolve the problems as quickly
as possible
DS8000 and DS6000 Remote Access Features
Student Notebook
Figure 5-10. DS8000 MC Network Topology SS481.0
Notes:
In order to connect the S-HMC to your network, you need the following network
information:
One IP address per S-HMC. With an external S-HMC, you need two IP addresses.
Host names for the S-HMCs (for example, MC1 and MC2).
Domain name for the S-HMC (for example, us.ibm.com).
Whether you use local time or a different time zone.
TCP/IP interface network mask (for example, 255.255.254.0).
If you plan to use a Domain Name Server (DNS) to resolve network names, you need
the IP address of your DNS server and the name of your DNS. You may have more than
one DNS.
To connect the MC, need following network information
One IP address per MC
With external MC, need two IP-addresses
Host names for the MCs: MC1 and MC2
Domain name for the MC: us.ibm.com
Whether you use local time or a different time zone
TCP/IP interface network mask: 255.255.254.0
With Domain Name Server (DNS) - more than one DNS
allowed
IP address of your DNS
Name of your DNS
DS8000 MC Network Topology
Student Notebook
V3.1.0.1
Uempty
Figure 5-11. DS8000 MC Network Considerations SS481.0
Notes:
Allowing access between the Internet and computers in a customer network brings valid
security concerns which need to be addressed. IBM has taken the steps necessary to
provide secure network access for the S-HMC. Even after securing access to the S-HMC,
there are additional levels of security built into the Service applications available on the
S-HMC. In the following sections we discuss the security protection securing access to the
S-HMC from the Internet, and then we describe the internal security of the S-HMC itself.
MC is a firewall/proxy for incoming traffic
No IP forwarding, no gateway functionality
Many standard services (telnet, ftp, ) do not exist
VPN (point-to-point) from MC to IBM over Internet or modem
VPN employs IPSec with triple DES Encryption algorithm (164-bit)
If Internet, firewall ports to open:
500 udp
500 esp (VPN)
4500 udp
Destination 207.25.252.196 192.42.160.16 207.25.252.198
No TCP/IP connection from the outside into the MC
ASCII Modem dial-in can be used to initiate VPN TCPIP call back
DS8000 MC - Network Considerations
Student Notebook
Figure 5-12. Redundant DS8000 MC SS481.0
Notes:
The best option is to have a redundant SMC for maintenance and configuration. The HMC
or external SMC is the only interface for service and configuration. If there is a problem with
the HMC, then no access is possible unless a remote SMC is set up.
Redundant MCs are recommended to avoid a potential single
point of failure
MC is the only service interface available
MC is the interface for performing configuration changes and
for supporting Open Copy Services operations
Option 1: FC1100 (Internal MC) and FC1110 (External MC)
FC1110 ships with 31 meter Ethernet cables
External MC is equivalent hardware to the Internal MC and is
to be installed in customer-supplied 19-inch rack (1U
server/1U display)
Option 2: FC1100 in each of two separate DS8000 base frames,
along with one FC1190 (31 meter Ethernet cables) to interconnect
the frames
At GA, a single MC (or a pair in a redundant configuration)
supports a maximum of two DS8000s
Redundant DS8000 MC
Student Notebook
V3.1.0.1
Uempty
Figure 5-13. DS8000 MC User Management SS481.0
Notes:
The HMC has predefined userids and new IDs can not be added. User password can be
changed by IBM support personnel, but the HMC is not intended for customer access or
use. Users are authenticated for use. User root is locked so that access level is not
allowed. User activity is logged and logs can be viewed with the DS8000 Storage Manager.
Predefined users, no new users can be added
User passwords can be changed by IBM support personnel
Users with higher privileges are protected by a challenge
authentication scheme
User root is locked
User activity logging
Auditing
DS8000 MC - User Management
Student Notebook
Figure 5-14. DS6000 and DS8000 Remote Support through VPN SS481.0
Notes:
Remote access is allowed via internet or dial-up. Internet VPN connection is preferred for
obvious reasons of speed and access.
IBM DS family of storage products is designed to reduce TCO
Automatic problem reporting to IBM support organizations
capability to troubleshoot failures remotely.
To accomplish this, IBM has implemented a Virtual Private Network (VPN)
capability intended to provide customers with a secure link
The DS8000 allows for call home and remote support by Internet or dial up
It is faster and easier for IBM service to support the DS8000 if the Internet
connection is used
IBM has taken many measures to provide a secure link using a Virtual Private
Network (VPN)
We would like our customers to use the Internet connection as much as possible
The DS6000 allows for call home and remote support by Internet connection
only
The same measures used for the DS8000 have been implemented in the DS6000
as well
We should encourage our customers to use this connection to help IBM provide
excellent support
DS6000 and DS8000
Remote Support through VPN
Student Notebook
V3.1.0.1
Uempty
Figure 5-15. How Virtual Private Network (VPN) Operates SS481.0
Notes:
This connection is through a high-speed Ethernet connection that can be configured
through a secure virtual private network (VPN) Internet connection to ensure authentication
and data encryption. IBM has chosen to use a graphical interface (WebSM) for servicing
the storage facility, and for the problem determination activity logs, error logs, and
diagnostic dumps that may be required for effective problem resolution. These logs can be
significant in size. For this reason, a high-speed connection would be the ideal
infrastructure for effective support services.
A remote connection can be configured to meet the following customer requirements:
Allow call on error (machine-detected)
Allow connection for a few days (customer-initiated)
Allow remote error investigation (Service-initiated)
The VPN server is located behind IBM firewall, which is designed to be
secure
The VPN client is located behind the customer firewall
The customer has control over opening a connection to access the client
Neither IBM technical support nor non-authorized personnel can access the
client without customers permission
The VPN Server security complies with IBM corporate security standards
ITCS104
This is an IBM internal security measure for all IBM secure data.
VPN
Gateway
RS3
IBM Support
VPN Tunnel
Firewall
DS-6000
SMC
Firewall
Customer Site IBM Site
Call home
Remote support
How Virtual Private Network (VPN) Operates
Student Notebook
Figure 5-16. DS8000 MC Remote Service Security (1 of 2) SS481.0
Notes:
During the installation process at the customer site, the IBM SSR connects to the IBM
Service organization, by way of modem, Internet connection, or the SSRs MOST portable
console, and transmits the public key for the installed console to a database maintained
within the IBM secure network. Whenever IBM Service requires access to the console
located at the customer site, the IBM personnel have to retrieve the console-specific public
key from the database and use this key to establish the communication session needed for
service.
WebSM (AIX) over VPN for graphical user interface
Server authentication via private/public key :
Each MC generates a certificate based on the private key that the
MC will use for Secure Sockets Layer (SSL) based encryption
and decryption.
The IBM SSR transmit the certificate for the installed MC to a
database maintained within the IBM secure network.
IBM personnel then retrieve the MC-specific certificate from the
database and use this key to establish the communication
session with the MC needed service.
SSH over VPN for command line access :
Secure Shell (SSH) is used for command line access from a
remote IBM location.
The SSH daemon on the MC accepts client connections only if an
IBM VPN is up, and a Product Engineer is currently logged on to
the MC.
SSH client authentication is done through a private/public key
algorithm.
DS8000 MC - Remote Service Security (1 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 5-17. DS8000 MC Remote Service Security (2 of 2) SS481.0
Notes:
The first security measure that is employed to protect the console is to only allow network
sessions or conversations to be initiated from the console itself. This means that there are
no applications running on the console that are listening on TCP/IP ports to establish a
session. If a session is needed from the console to enable a service action, an IBM Service
representative may initiate this session by dialing into the console using the modem, and
requesting that the console establish the session. This session is only initiated to one of the
defined TCP/IP addresses which represent the IBM Service centers.
VPN sessions initiated from the MC :
No application listening on TCP/IP ports on the MC
If a session is needed from the MC to enable a service action, an
IBM Service representative may initiate this session by dialing into
the MC via the modem, and requesting that the MC establish the
session.
MC always establishes that session to the defined IBM TCP/IP
addresses, not to another server or workstation
Only active when specific conditions are met
Except for SSH, no other standard services over remote
connection
Remote connection options can be configured to meet
customer requirements
Allow call on error (machine detected)
Allow connection for a few days (customer initiated)
Allow remote error investigation (Service initiated)
DS8000 MC - Remote Service Security (2 of 2)
Student Notebook
Figure 5-18. MC Network Topology SS481.0
Notes:
The figure above shows a typical redundant S-HMC configuration. In this configuration, we
have MC1 (internal S-HMC) and MC2 (external S-HMC) connected to the 172.16-BLACK
network and the 172.16-GRAY network. These two networks are the private Ethernet
networks of the DS8000. MC1 and MC2 are also connected to the customers network by
way of the customer Ethernet ports on the pair of Ethernet switches that are installed at
installation time.
MC - Network Topology
C
u
s
t
o
m
e
r
N
e
t
w
o
r
k
FSP
SFI Complex 0
SFI Complex 1
FSP
Processor Complex 0
Processor Complex 1
Storage
Facility
Image
(SFI)
FSP
SFI Complex 0
SFI Complex 1
FSP
Processor Complex 0
Processor Complex 1
Storage
Facility
Image
(SFI)
IBM
network
IBM
network
IBM eCare
Call Home
Remote Support
Storage Facility #2
Storage Facility #1
S
M
C

1

N
e
N
e
VPN over
modem
VPN over
modem
Internet
Internet
Customer
network
Customer
network
S
M
C

2

FSP: Functional Service Processor
firewall
firewall
firewall
Student Notebook
V3.1.0.1
Uempty
Figure 5-19. DS8000 MC Summary SS481.0
Notes:
The SMC is the central point of control and at least one HMC is required for each DS8000.
The DS6000 has no internal HMC so a SMC is required for DS6000 management.
The Storage Management Console is the central point of
control for service, configuration, and Advanced Copy Services
functions
At least one MC is required for each Storage Plex
Two MCs are recommended to eliminate a potential single
point of failure
DS8000 MC Summary
Student Notebook
Checkpoint
1. T/F The DS6000 is equipped with a pair of 2-way PowerPC
processors and provides redundant control of the storage arrays.
cluster into logical partitions called LPARs which divides the
hardware components into two separate controllers which can
3. T/F The DS6000 system uses switched FC-AL disk enclosures
which improves disk performance and error-detection capabilities.
Student Notebook
V3.1.0.1
Uempty
Notes:
Unit Summary
Having completing this unit, you should be able to:
Describe the DS6000/DS8000 Storage Manager installation
Describe how to access the Storage Manager
Describe the simulated mode of the Storage Manager
Describe how to define the physical hardware using the simulated
manager
Describe how to define arrays, ranks and extent pools
Describe how to define volumes, host connections and volume
groups
Student Notebook
Student Notebook
Copyright IBM Corp. 2005 Unit 6. DS8000 Storage Manager GUI 6-1
V3.1.0.1
Uempty
Unit 6. DS8000 Storage Manager GUI
The DS8000 Storage Manager is customer-installable software used
for configuration of the DS8000 Storage Subsystem.
Describe the installation of the DS8000 Storage Manager
Describe real-time mode and simulation mode
Understand how to access the DS Storage Manager GUI
Describe configuring the storage units, images and complexes
Describe configuring arrays sites, arrays, ranks, and extent pools
Describe the configuration of FB logical volumes and volume
groups
Describe configuring host attachments
Describe the use of the DS Information Center
Accountability:
Checkpoint questions
Lab Exercises
References
Concepts
Guide
Student Notebook
Notes:
Unit Objectives
Describe the DS6000/DS8000 Hardware Management Console
Describe the internal Ethernet switches in the DS8000 storage unit
Describe how to access the setup of the HMC
Describe the network topology
Describe the VPN consideration and setup
Describe the network restrictions when access the HMC or the
DS8000 storage servers
Student Notebook
V3.1.0.1
Uempty 6.1 DS Storage Manager GUI
Student Notebook
Figure 6-2. Topic: DS Storage Manager GUI SS481.0
Notes:
DS Storage Manager GUI
DS Storage Manager Installation
Requirements
DS Storage Manager GUI Activating Keys
and Storage Unit
DS Storage Manager Architecture and
Logical Configuration Steps
Summary of Logical Configuration
Differences
Topic: DS Storage Manager GUI
Student Notebook
V3.1.0.1
Uempty
Figure 6-3. DS Storage Manager SS481.0
Notes:
The DS8000 Storage Manager comes in two parts. A Real-time Manager which talks
directly to the DS8000 and runs on the HMC. To run in real-time mode from a customer
workstation, use a Web browser to access the DS Storage Manager GUI through the DS
Network Interface Server.
The DS8000 Storage Manager also offers a Simulated Mode GUI which can be run from an
External SMC or customer workstation. This allows the user to create an offline
configuration and EXPORT it as an XML file or apply it to the Real-Time SM. You can also
IMPORT the real-time configuration to the Simulated Mode GUI to add hosts or volume
groups and then apply that to the DS8000.
Two interfaces/modes of operation
Realtime (online)
Internal DS MC (DS8000 only)
Customer DS MC (DS6000 only)
External customer workstation (DS8000 and DS6000)
Simulated (offline)
Customer DS MC (DS6000 only)
External customer workstation (DS8000 and DS6000)
Can be independently installed
Can install one, or the other, or both on customer or workstation
If both are installed, they are integrated into the same interface
DS8000 Internal DS MC supports realtime manager only
DS6000 Customer DS MC supports both realtime and simulated
managers
Both realtime and simulated interfaces have same look and feel
DS6000 and DS8000 Storage Managers have same look and
feel
DS Storage Manager
Student Notebook
Figure 6-4. DS8000 Management Console SS481.0
Notes:
The DS8000 comes with an internal HMC which in located just above the processor
complex in the base frame. It consists of a monitor, keyboard and HMC server which is
connected directly to the processor complex through two internal network Ethernet
switches. The HMC has two connections, one to each network switch, and they in turn
connect to p5 570 servers. There are two Ethernet connections from each Ethernet switch
to each server, and on a 9A2 if the server is LPARed, then there is a connection for each
LPAR. The Internal Management Console is the same as the pSeries Management
Console, and you can run the Real-Time DS Storage Manager directly from the HMC or
you can run it remotely using a Web browser. To run the DS Storage Manager directly, log
on to the HMC with the default user hscroot and password abc23. The user can change
this password and add user accounts. Right-click the HMC screen and select Net then
browser to access the DS Storage Manager. Log in using admin/admin and you are
required to change the password before you can use the DS Storage Manager interface.
Supports logical storage configuration via preinstalled TotalStorage DS Storage Manager in
online mode only.
DS Storage Mgr
Customer UI Customer UI
Remote
Services
ESS
Master Console
IBM TotalStorage
DS Storage Manager
DS8000 Internal
Management Console
Remote
Services
System and
Partition
Management
Service
Service
Storage
Facility RAS
pSeries HMC
System and
Partition
Management
ESS (AIX )
ESS RAS
ESS
Configuration
Copy Services
Network Interface
Server
DS8000 Management Console
Student Notebook
V3.1.0.1
Uempty
Network Interface Server for logical storage configuration and invocation of Advanced
Copy Services functions
Service appliance (closed system)
Connection to DS8000 through Ethernet only
This graphic shows the function of the ESS interfaces and how they have been applied to
the DS8000.
The ESS Specialist used a browser interface directly to an internal web server that ran in
the cluster under the AIX OS. This function has been replaced by a DS Network Interface
Server. This runs as part of the DS Storage Manager.
Student Notebook
Figure 6-5. DS Storage Manager Architecture SS481.0
Notes:
The IBM TotalStorage DS Storage Manager is a program interface that is used to perform
logical configuration and copy services management functions of the DS6000 and DS8000
It can be accessed from any location that has a network access using a Web browser.
Enter the URL of the DS Management Console:
http://DS MC IP Addr:8451/DS8000 for a DS8000
https://DS MC IP Addr:8452/DS8000 for a DS8000
or
http://DS MC IP Addr:8451/DS6000 for a DS6000
https://DS MC IP Addr:8452/DS6000 for a DS6000
Network
Server
Network
Client
GUI Server
Browser 1
Storage
DS Storage Manager :
WebSphere Application Server
+ DS Storage Manager GUI
+ Network client
DS Network Interface
Server
DS Storage Manager Architecture
Student Notebook
V3.1.0.1
Uempty
Figure 6-6. DS Storage Manager Realtime Manager - DS8000 SS481.0
Notes:
The real-time manager runs in the internal Management Console via an internal browser,
and can be run remotely using only a browser. The real-time manager talks directly to the
DS8000 server using the DS Storage Manager Server, and is connected to the servers
from the HMC by Ethernet connections using internal Ethernet Switches located in the
DS8000 base frame.
External users of the DS Storage Manager connect to this network on an Ethernet port on
the HMC server, and do not connect to the internal switches. A secondary Management
Console can connect to the internal switches, or a second DS8000s internal HMC can
cross connect to these switches to provide redundant HMCs, which is recommended.
The HMC is the focal point for all service and customer access for configuration and setup.
Browser 2
Browser 3
GUI Server
Network
Server
Network
Client
GUI Server
Browser 1
Network
Client
Customer Workstation
(to Realtime Manager on
DS8000 Internal DS MC)
with Realtime Manager
Internal DS
Management Console
(DS8000 only)
Storage
To use the Realtime
configurator, you need to have
access to the Internal
Management Console
DS Storage Manager
Realtime Manager - DS8000
Student Notebook
Figure 6-7. DS Storage Manager Simulated Manager DS8000 SS481.0
Notes:
The DS8000 Storage Manager has two modes of operation. To run the Simulated Manager
the user must install the DS8000 Storage Manager Simulated Mode Console on their
workstation. The Internal HMC does not have a simulated mode manager to access. If an
external HMC is installed, the user has the option of installing the real-time and simulated
mode function on this console. Then either function can be accessed using a Web browser.
Using the Simulated Manager it is possible to import a configuration from the DS8000,
modify it, and then apply these changes back to the DS8000. This may be easier than
trying to perform these changes in real-time mode, especially if mistakes are made during
the process.
with Simulated Manager
Network
Server
Storage
Browser
GUI Server
Network
Client
Network
Server
DS Storage Manager
Realtime Manager - DS8000
Local
Copy
of
Configuration
(database)
1
2
Internal
DS MC
(DS8000 only)

Student Notebook
V3.1.0.1
Uempty
Figure 6-8. DS Storage Manager Realtime and Simulated Managers DS6000 SS481.0
Notes:
Both the Real-time and Simulated mode Storage Managers can be installed, but only the
HMC on an external SMC connected to the DS8000 Internal switches can communicate
directly to the DS8000.
Browser
Network
Server
Network
Client
GUI Server
Browser
Storage
Customer DS MC
With Both Managers
Local
Copy
of
Configuration
(database)
Import/Apply Configuration
DS Storage Manager Realtime
and Simulated Managers - DS6000
Student Notebook
Figure 6-9. DS Storage Manager and DS CLI SS481.0
Notes:
The DSCLI is the command line interface and it can be installed on any customer
workstation or laptop. It just requires access to the network and the HMC to run CLI
commands to configure the DS8000. The DS8000 CLI can be installed together with the
ESS CLI, but not with the DS6000 CLI.
The DS600 CLI and the DS8000 CLI are different software programs, but very similar. In
many cases one of these interfaces can be used to configure either the DS6000 or the
DS8000, but some commands for the DS6000 for customer maintenance and
troubleshooting are not present in the DS8000 DSCLI, so this program should be available
from some workstation if needed.
DSCLI
Customer
Workstation
Network
Interface
Client
Network
Server
Network
Client
GUI Server
Browser 1
Storage
DS Management Console
DS Storage Manager and DS CLI
Student Notebook
V3.1.0.1
Uempty
Figure 6-10. Realtime versus Simulated Configuration Options SS481.0
Notes:
The DS Storage Manager is required to add DS8000 or DS6000 Storage Units to the
Storage Complex. The Storage Complex is the group of DS units being managed by one
DS Storage Manager. Until a unit is added to the complex, you can not issue commands to
this unit. You also need to use the DS Storage Manager to apply the license keys for the
features you ordered.
Once these things are complete you can use the DS Storage Manager or the DSCLI to
configure the physical or logical storage on the DS8000 or DS6000.
The Simulated Manager allows you to import configurations from:
The DS8000 hardware
The DS6000 hardware
An exported XML file
An e-Config .crf file from the IBM sales e-Config tool
Realtime Manager only
Add/Remove Storage Complex (DS8000)
Apply Activation Keys to Storage Image (DS8000)
Assign Storage Unit (DS6000) DS MC to DS6000 communication
Configure Storage Unit (DS6000)-- date/time and license keys
Define Peer (DS6000) Redundant DS MC
User Administration
Systems Management (DS6000)
Simulated Manager only
Manage Configuration Files
Import/Create/Delete Storage Complex
Import/Create/Delete Storage Unit
Apply Configuration
Copy/Paste Storage Unit, Storage Image (DS8000)
Realtime versus Simulated
Configuration Options
Student Notebook
Figure 6-11. Exporting Logical Configuration Information SS481.0
Notes:
DS Storage Manager functions include an option to:
Print
Download in spreadsheet format
Invoke the browsers save as dialogue
Physical and logical configuration created in simulated mode
or imported (retrieved) from the storage unit can be used for
Backup
Cloning
Exporting Logical Configuration Information
Student Notebook
V3.1.0.1
Uempty
Figure 6-12. Unlock Admin Password SS481.0
Notes:
If you lock the password of the admin account or other user account, you have to unlock
that account before you can log in. You have to sign on with the new admin account
password that was created. The DSCLI program asks you to change this password the first
time you log on. This does not work if admin is the only userid you have defined.
You can also run the securityRecoveryUtility.bat -r in the c:\Program
Files\IBM\dsniserver\bin directory to reset the admin password back to the default of
admin. The DS Network Server must be stopped to run this command.
After three unsuccessful attempts with the wrong password,
the account is locked.
If the Admin account is involved, the administrator must use
the security recovery utility tool.
The script resides in the following directories, depending on
where the DS Storage Manager is installed:
On an HMC, the directory is: /opt/essni/bin/
On a Windows operating system, the directory is:
C:\Program Files\ IBM\dsniserver\bin\
Type the script name, securityRecoveryUtility.bat -r and press the
Enter key. The script runs and the Admin account is unlocked.
Unlock Admin Password
Student Notebook
Student Notebook
V3.1.0.1
Uempty 6.2 Installation Requirements
Student Notebook
Figure 6-13. Topic: Installation Requirements SS481.0
Notes:
Topic: Installation Requirements
Requirements
DS Storage Manager GUI Activating
Keys and Storage Unit
Differences
Student Notebook
V3.1.0.1
Uempty
Figure 6-14. DS Storage Manager Supported Operating Systems SS481.0
Notes:
These are the supported platforms for the DS8000 Storage Manager. If you are running
Windows XP SP1, that works but you cannot run the real-time monitor from that
workstation; only the browser is supported.
RedHat Advanced Server 2.1 on Intel (DS8000 only)
Windows 2000 Server SP4
Windows 2000 Advanced Server SP4
Windows 2000 Professional SP4
Windows XP Professional SP1, SP1a (Offline only)
Windows XP Professional SP2
Windows 2003 Server Standard and Enterprise
DS Storage Manager
Supported Operating Systems
Student Notebook
Figure 6-15. DS Storage Manager Supported Client Browsers SS481.0
Notes:
These are the supported browsers. Others may work, but are not supported if you have
problems.
Microsoft IE 6
Netscape 6.2
Netscape 7
DS Storage Manager
Supported Client Browsers
Student Notebook
V3.1.0.1
Uempty
Figure 6-16. DS8000 Storage Manager Installation Process (1 of 7) SS481.0
Notes:
The DS Storage Manager can be installed on a customer workstation but is not required to
run the configuration tool. You may want to have the offline simulated mode for practice.
This is what we use in class for labs.
Installation by a wizard
DS8000 Storage Manager
Installation Process (1 of 7)
Student Notebook
Notes:
The ports are listed. You can change them if they conflict with something you already are
using.
Specify the destination directory :
Accept default location : C:\Program Files\IBM\DS8000StorageManager
Specify Hostname and TCP ports for the server
Accept default values.
Student Notebook
V3.1.0.1
Uempty
Notes:
This panel requires some passwords for key and trust file authorization. Just select a
password. You are never asked to enter it so it does not matter what it is.
Specify Key file and Trust File password
Student Notebook
Notes:
Enter location and company information.
Specify other information for certificates generation
Student Notebook
V3.1.0.1
Uempty
Notes:
Verify and click Next.
Once all information has been provided, installation can start
Student Notebook
Notes:
The DS Network Interface and DS Storage Manager are installed as services. Verify that
they start.
At the and of the installation, verify
that the following services have
been started:
IBM DS Network Interface server
IBM WebSphere Application
Server V5 DS Storage Manager
Student Notebook
V3.1.0.1
Uempty
Notes:
OK, its installed, lets start it. The DSNI and DSSM should be running, but if not you can
start them from the Start - Programs - DS Network Interface Server and DS Storage
Manager Server.
At the end of the installation, check the postinstallation.txt file :
To stop or restart the DS Network Interface servers from the Windows
Programs list:
From the windows system where you installed the DS Storage
Manager :
1. Click Start.
2. Select Programs to display the programs list.
3. Open IBM TotalStorage DS Network Interface Server menu
4. Click Stop or Start for the action that you want to complete.
Starting the DS8000 Storage Manager from Windows system where you
installed the DS Storage Manager :
1. Click Start.
2. Click Programs.
3. Open IBM TotalStorage Manager DS Storage Manager Server
menu:
4. Click Stop or Start for the action you want to complete.
Then, you can start DS8000 Storage Manager GUI from your default
browser :
URL : http://localhost:8451/DS8000
or : https://localhost:8452/DS8000
When you start the DS8000 Storage Manager, the IBM TotalStorage
DS8000 Signon window is displayed.
Enter the user name and password to access the program.
The default user name and password is admin
Network
Server
Network
Client
GUI Server
Browser 1
Storage
Student Notebook
Student Notebook
V3.1.0.1
Uempty 6.3 Activating Keys and Storage Unit
Student Notebook
Figure 6-23. Topic: Activating Keys and Storage Unit SS481.0
Notes:
Topic: Activating Keys and Storage Unit
Requirements
Differences
Student Notebook
V3.1.0.1
Uempty
Figure 6-24. Storage Image (DS8000*) Apply Activation Keys SS481.0
Notes:
The DS8000 must have its activation keys downloaded and installed in order to use any of
the features that were ordered by the user. This is done a little differently in the DS6000
GUI than here as there is no storage image concept in the DS6000.
Realtime mode only
Next step -- enter keys for operating environment and advanced functions,
or import .xml file previously downloaded from DSFA Web site
*For DS6000, apply keys to Storage Unit (Configure Storage Unit)
Storage Image (DS8000*) -
Apply Activation Keys
Student Notebook
Figure 6-25. Storage Image (DS8000*) - Apply Configuration SS481.0
Notes:
To apply a configuration from the DS8000 SM, use the Storage Images panel and select
Apply Configuration from the Actions menu.
Simulated mode only
Logical configuration created offline is applied via the network
*For DS6000, apply configuration to Storage Unit
Apply Configuration
Student Notebook
V3.1.0.1
Uempty
Figure 6-26. Apply Configuration Select Application Method SS481.0
Notes:
This is how to apply a configuration from an outside source, or you can just create it
real-time using the GUI. We do that next.
Apply Configuration -
Select Application Method
Student Notebook
Figure 6-27. Apply Configuration Select Storage Complex SS481.0
Notes:
Here is a list of the storage complexes if we have more than one. Select it and click Next.
Apply Configuration - Select Storage Complex
Student Notebook
V3.1.0.1
Uempty
Figure 6-28. Apply Configuration - Authenticate SS481.0
Notes:
Enter the IP address of the HMC for the storage complex and the current admin userid and
password and click Next.
Apply Configuration - Authenticate
Student Notebook
Figure 6-29. Apply Configuration Select Storage Unit SS481.0
Notes:
Select the storage unit to download the code to, then click Next. You get to verify what you
are about to do and click Finish.
Next step -- select storage image (DS8000)
Logical configuration activation is complete!
Apply Configuration Select Storage Unit
Student Notebook
V3.1.0.1
Uempty
Figure 6-30. Manage Configuration Files SS481.0
Notes:
This is the panel for configuration file management. You can IMPORT files or EXPORT files
from this panel. EXPORTED files are in XML format and can be viewed with a browser and
edited, but be cautious about editing the files. You could cause the configuration not to
work at all.
Student Notebook
Figure 6-31. User Administration SS481.0
Notes:
This is the User administration screen. You can create new users for admin, configuration,
copy services or just monitor operations.
User Administration
Student Notebook
V3.1.0.1
Uempty
Figure 6-32. Add User SS481.0
Notes:
This is where you can create a new user from the GUI. There are several levels of
authorization including admin, configuration, backup, copy services, and monitor. Each
user is created with a temporary one-time password that must be changed the first time
you log into the DS Storage Manager. The new passwords have several requirements.
They must have five alpha letters and one or more numbers, but numbers can not be at the
beginning or the end. So, something like passw0rd would be valid, but mike01 would not.
Add User
Student Notebook
Student Notebook
V3.1.0.1
Uempty 6.4 Architecture and Logical Configuration Steps
Student Notebook
Figure 6-33. Topic: Logical Configuration Steps SS481.0
Notes:
Topic: Logical Configuration Steps
Requirements
Differences
Student Notebook
V3.1.0.1
Uempty
Figure 6-34. Recommended Logical Configuration Steps SS481.0
Notes:
Here is the logical configuration steps process. When you run in simulated mode you must
define the hardware you want to work with as you have no way to determine hardware
configuration unless you import a configuration from a real DS8000. So, we define the
Storage Complex and Storage Units and the number of DDMs or disk enclosures.
Recommended Logical Configuration Steps
Student Notebook
Figure 6-35. DS Storage Manager Signon SS481.0
Notes:
This is the logon screen for the GUI.
URL : http://localhost:8451/DS8000
or : https://localhost:8452/DS8000
Log as admin/admin (default password has to be changed at fist login).
Same look and feel for Real-time and Simulated Managers
Same look and feel for DS6000 and DS8000
DS Storage Manager Signon
Student Notebook
V3.1.0.1
Uempty
Figure 6-36. DS Storage Manager Welcome Panel SS481.0
Notes:
DS Storage Manager Welcome Panel
Student Notebook
Figure 6-37. Import Configuration File SS481.0
Notes:
This simulated mode GUI allows the user to IMPORT a configuration from the real-time
manager.
Imports xml file from a previously created configuration
Import Configuration File
Student Notebook
V3.1.0.1
Uempty
Figure 6-38. Create Storage Complex (DS8000) SS481.0
Notes:
When you work with a simulated configuration, unless you IMPORT an existing
configuration, you are not aware of any hardware, so you must create it yourself. The
simulated mode GUI allows you to create the hardware configuration you wish to work with.
If you are trying to emulate a DS8000 you have ordered, then it is very important to do this
step accurately. If you are loading a configuration for practice, then it does not matter what
you select.
Simulated mode only
Settings can affect all subsystems in complex
Not required for realtime management from SMC
Optional
Create Storage Complex (DS8000)
Student Notebook
Figure 6-39. Create Storage Complex Define Properties SS481.0
Notes:
The name is optional, but it is a good idea to name the complex and give it a short
description. There is no storage unit yet, so click the button at the bottom to create it.
Nickname
Description
Select or create
storage unit
Create Storage Complex - Define Properties
Student Notebook
V3.1.0.1
Uempty
Figure 6-40. Create Storage Unit General Information SS481.0
Notes:
Here you actually get to select the hardware. Select the model and give it a nickname.
There is no Storage Complex yet, because we did not finish it, so just click Next at this
point.
Create Storage Unit - General Information
Simulated mode only
Select machine type/model; enter nickname and description
Creates storage image (DS8000)
Student Notebook
Figure 6-41. Create Storage Unit - Specify DDMs SS481.0
Notes:
This selects the number of DDM packs and the size. These are the 16 disk storage
enclosures. You must select and even number and click Add to add them to the storage
unit.
Create Storage Unit - Specify DDMs
Student Notebook
V3.1.0.1
Uempty
Figure 6-42. Create Storage Unit - Define Licensed Function SS481.0
Notes:
If you have ordered features for FlashCopy or PPRC, you must select the size of the
licenses you have or specify everything if you are just practicing.
Licensed function by capacity
Create Storage Unit -
Define Licensed Function
Student Notebook
Figure 6-43. Create Storage Unit - Define Licensed Function (Details) SS481.0
Notes:
The features dont have to be for all storage. If they are not, select the storage they apply
to. Click OK.
Licensed function by storage type (FB, CKD or All)
Define Licensed Function (Details)
Student Notebook
V3.1.0.1
Uempty
Figure 6-44. Create Storage Unit - Specify I/O Adapters (DS8000*) SS481.0
Notes:
Select the number of host adapters you have ordered or wish to work with.
Specify I/O Adapters (DS8000*)
If necessary, FICON/FCP adapter protocol is configured during host
definition
Storage image automatically created (DS8000)
*Storage unit adapter specification unnecessary for DS6000
Student Notebook
Figure 6-45. Verification SS481.0
Notes:
Verify the storage hardware you have defined. Click Finish to define the storage unit. But
you are not done; see next slide.
Verification
Student Notebook
V3.1.0.1
Uempty
Figure 6-46. Finish Creating the Storage Complex SS481.0
Notes:
The GUI returns you to the Storage Complex Creation panel.
Add the storage unit to the storage complex, click next verify the storage complex
information and click Finish to define the storage complex. Now you can start creating
arrays and ranks and volumes.
Finish Creating the Storage Complex
Student Notebook
Figure 6-47. Import Storage Unit SS481.0
Notes:
The other way you can do hardware definition is to import a configuration from an existing
DS8000 or an econfig .crf file from a sales order.
Import Storage Unit
Simulated mode only
Import order data file (cfg file from econfig)
Next step -- browse for local file on workstation
Creates storage image (DS8000)
Student Notebook
V3.1.0.1
Uempty
Figure 6-48. Add Imported Storage Unit to Complex (DS8000) SS481.0
Notes:
Add this storage unit to the complex and click Next.
Add Imported Storage
Unit to Complex (DS8000)
MODIFY complex to add imported storage unit
Student Notebook
Figure 6-49. Long Running Task Monitor SS481.0
Notes:
Some tasks take a long time to run. You can monitor these tasks with the long-running task
monitor screen.
Long Running Task Monitor
Student Notebook
V3.1.0.1
Uempty
Figure 6-50. Create Host System SS481.0
Notes:
Now that you have a hardware configuration, you can create hosts and volumes to use.
Start by creating a host system you wish to attach.
Server with one or more HBA/WWPN attachments
Default definition for Anonymous ESCON Host allows ESCON access
(DS8000 only)
One user-created host definition is required for FICON access
Create Host System
Student Notebook
Figure 6-51. Create Host System General Information SS481.0
Notes:
Select the host type and give it a nickname and description.
Select type, enter nickname and description
Create Host System - General Information
Student Notebook
V3.1.0.1
Uempty
Figure 6-52. Create Host System Define Host Ports SS481.0
Notes:
Specify the number of ports that are used to connect the system. These can be grouped if
they are always used together. This makes them into a port group which can be added to a
host attachment. You can also select the box to identify the WWPNs for the ports.
Create Host System - Define Host Ports
Enter quantity, select protocol
Options to group and to define WWPNs
Iterative for multiple ports
Student Notebook
Figure 6-53. Host Attachment Identifier Example SS481.0
Notes:
The host attachment IDs created.
Host_6|pSeries|FcSf(2)_0
Host_6 - Nickname (default)
pSeries - host type
FcSf - FC-Switched
(2) - two HBAs in a port group
_0 - first definition with these characteristics
This identifier represents one host attachment
Limited to a single volume group
Host Attachment Identifier Example
Student Notebook
V3.1.0.1
Uempty
Figure 6-54. Create Host System - Specify WWPN SS481.0
Notes:
The WWPNs can be added in this panel. The DS8000 does not discover WWPNs that are
attached, so it is best to display the WWPN from the host or FC switch GUI and paste it into
the box.
Optional WWPNs can be selected later using the real-time manager
Create Host System - Specify WWPN
Student Notebook
Figure 6-55. Create Host System - Specify Storage Image (DS8000*) SS481.0
Notes:
Add the storage image to the host definition. Single host definitions can be applied to
multiple subsystems.
*Note: Storage image actions applies to the storage unit for DS6000.
Iterative for multiple storage images (DS8000)
Single host definition can be applied to multiple subsystems
Note: Storage image actions apply to the storage unit for DS6000
Create Host System -
Specify Storage Image (DS8000*)
Student Notebook
V3.1.0.1
Uempty
Figure 6-56. Create Host System Specify Storage Image Parameters SS481.0
Notes:
The port must be configured to be used in a host attachment, so select the Configure I/O
ports and set them to Scsi_Fcp for Open systems. The host attachment can be used as
part of a volume group, if volumes exist, but at this point we have not defined the volumes
yet, so just select the configured ports and apply them to the host attachment definition.
If ports unconfigured must
configure before
assignment to host
attachment
Select host attachment and
allow access to storage I/O
ports
Option to select or create
volume group for host
attachment
Create Host System -
Specify Storage Image Parameters
Student Notebook
Figure 6-57. Format I/O Ports SS481.0
Notes:
Select the ports you wish to configure and the type of FcSf for switched fabric.
Format I/O Ports
Student Notebook
V3.1.0.1
Uempty
Figure 6-58. Warning SS481.0
Notes:
Click Continue.
Warning
Student Notebook
Figure 6-59. Host Attachment Selection SS481.0
Notes:
Verify that the ports you selected have been configured with the correct attachment type.
Host Attachment Selection
Student Notebook
V3.1.0.1
Uempty
Figure 6-60. Create Array SS481.0
Notes:
OK, so now we can create an array. Select Configure Storage and Arrays. If there are none
displayed, go to the Actions menu and select Create, and click Go.
Eight DDMs in a RAID5 or RAID10 array
DS8000 one array site (eight DDMs)
DS6000 two array sites (four DDMs each)
Create Array
Student Notebook
Figure 6-61. Create Array Definition Method SS481.0
Notes:
You can do this manually or automatically. If all the arrays are to be the same then use
automatic. You are asked to select the quantity of arrays you wish to create. An array is
created from an array site which already exists. They are groups of eight disks selected
from two different disk enclosures, one from the front on one FC-AL loop and one from the
rear on the other FC-AL loop. Arrays are therefore configured as arrays across loops or
AAL by default. You do not have a choice in the drives that are selected as the array site.
Two methods auto or custom
Create Array Definition Method
Student Notebook
V3.1.0.1
Uempty
Figure 6-62. Create Array - Auto SS481.0
Notes:
Choose the RAID type for the array. This is all that is set at this time. The format of the
array, FB or CKD comes later. Click Next. You can choose RAID 5 or RAID 10.
Specify quantity of arrays by drive types
Select RAID type
Algorithm chooses array site
Create Array - Auto
Student Notebook
Figure 6-63. Add Arrays to Ranks SS481.0
Notes:
This is where you can choose the format. The arrays are placed in ranks. This is a new
step, because in the ESS the format was done at the same time. Check the box and click
Next. Verify the option and click Finish, and your arrays and ranks are created. If you dont
check the box then the create ranks step must be done separately.
One RAID array becomes one CKD or FB rank
Optional ranks can be created at another time
Add Arrays to Ranks
Student Notebook
V3.1.0.1
Uempty
Figure 6-64. Create Array - Custom SS481.0
Notes:
Back at the Custom array creation, you have to choose your arrays sites manually. Click
Next.
Select RAID type
Select array sites
Next step -- option to add arrays to ranks
Create Array - Custom
Student Notebook
Figure 6-65. Create Extent Pool SS481.0
Notes:
The extent pool is where we get server affinity. In the ESS, server affinity was already
established by the hardware location. Even arrays were served by Cluster 1 and odd arrays
were served by Cluster 2. In the DS8000, any array can be serviced by any server, so be
careful. It is possible to configure the DS8000 so that all arrays are being accessed by only
one of the servers and the other server is idle. This is not a good idea.
Create Extent Pool
Student Notebook
V3.1.0.1
Uempty
Figure 6-66. Create Extent Pool Auto (1 of 2) SS481.0
Notes:
The extent pool definition has two methods as well. The automatic method creates two
extent pools and place even ranks in extent pool 0 and odd ranks in extent pool 1. This may
have a negative result when defining volumes as many ranks are not used unless all the
storage is defined. We recommend that the extent pools be defined manually for this
reason. Also, when using the GUI, the ranks are selected and assigned to the extent pool
as part of the creation of the extent pool. If you configure using the DSCLI the process is
different from that once the extent pools are created. You must assign the ranks to them
using a different command called chrank.
Two methods auto or custom
Auto
User specifies storage type, RAID type and amount of space
Algorithm selects ranks and server
Create Extent Pool - Auto (1 of 2)
Student Notebook
Figure 6-67. Create Extent Pool - Auto (2 of 2) SS481.0
Notes:
This is where you can define the parameters for your extent pool. An extent pool name is
optional, but gives you a better idea what kind of storage it contains if you work out a
naming convention. Storage type, RAID type, and RPM may be factors that you would want
to be aware of when selecting a pool to allocate a volume. You may want to select the
specific ranks to place in the extent pool, so leave the box unchecked at the bottom of the
screen.
Specify nickname, storage type, RAID type, amount of storage
Create Extent Pool - Auto (2 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 6-68. Create Extent Pool Reserve Storage SS481.0
Notes:
The reserved storage is an optional parameter that reserves a percentage of the extent
pool.
Option to reserve a percentage of storage in the extent pool
Create Extent Pool - Reserve Storage
Student Notebook
Figure 6-69. Create Extent Pool - Verification SS481.0
Notes:
Verify that the extent pool is set up the way you desire. Click Finish to complete the
definition.
All tasks allows verification before committing changes
Create Extent Pool - Verification
Student Notebook
V3.1.0.1
Uempty
Figure 6-70. Create Extent Pool - Custom Define Properties SS481.0
Notes:
This is the custom define. Select the other server. You want to make sure you have extent
pools for both servers to distribute the workload.
Custom
Select Server 0 or Server 1
Select ranks (on next panel)
Create Extent Pool - Custom Define Properties
Student Notebook
Figure 6-71. Create Extent Pool Custom Select Ranks SS481.0
Notes:
This panel allows you to select the ranks you want to use in each extent pool.
Next step -- option to reserve storage
Create Extent Pool - Custom Select Ranks
Student Notebook
V3.1.0.1
Uempty
Figure 6-72. Create FB Volume SS481.0
Notes:
This panel is for defining volumes. The minimum LUN size is 1 GB, but the storage
manager allocates an extent for the volume. To keep from wasting space, allocate volumes
of even GB boundaries to use an even number of extents.
Min LUN size 0.1 GB
Min allocation remains one extent
Max LUN size 2 TB
LUN can be larger than rank size if multiple ranks in extent pool
iSeries -- 8.56, 17.54, 35.1, 70.56, 141.12, 282.25
Create FB Volume
Student Notebook
Figure 6-73. Create FB Volume Select Extent Pool SS481.0
Notes:
Under the Simulated Manager, expand the Open Systems section and click Volumes. Click
Create from the Select Action pull-down and click Go. Follow the panel directions with each
advancing window. Choose the extent pool from which you wish to configure the volumes
and click Next.
Only odd or even LSSs are available depending on extent pool selection
(due to extent pool server affinity)
Create FB Volume Select Extent Pool
Student Notebook
V3.1.0.1
Uempty
Figure 6-74. Create FB Volume Define Volume Characteristics SS481.0
Notes:
You can select the volume RAID type and storage type and even add the volume to a
volume group if one exists. Click Next when you are ready to continue.
Volume type
Open systems, iSeries protected, iSeries unprotected
Optionally select volume group or create new group
Create FB Volume -
Define Volume Characteristics
Student Notebook
Figure 6-75. Create FB Volume Define Volume Properties SS481.0
Notes:
The volume can be made in any LSS. Even LSS requires an extent pool from server 0 and
odd LSS requires Server 1. Select the quantity and size of the volumes. The volume is
created in binary GB and can be any valid size from .1 GB to 2 TBs, depending on host
requirements. Volume can only be made as large as the number of extents in the FB extent
pool, however, you can place multiple ranks into an extent pool to provide enough extent
for a large volume. Extents are currently not striped across multiple ranks in an extent pool,
but allocated sequentially from the first rank to the last rank.
Quantity and size
Only odd LSSs shown due to extent pool association with server 1
LSS selection creates FB LSS and determines addressing
Create FB Volume - Define Volume Properties
Student Notebook
V3.1.0.1
Uempty
Figure 6-76. Create FB Volume Create Volume Nicknames SS481.0
Notes:
This panel allows the user to define a set of nicknames for the volumes. This is for
reporting purposes and to help identify the volume use. Nicknames could have
associations with the applications that run on them.
Optionally generate sequence based on prefix and/or suffix
Create FB Volume - Create Volume Nicknames
Student Notebook
Figure 6-77. Create FB Volume Group SS481.0
Notes:
Many times a set of volumes is defined for a particular host or application. When using
these volumes, they are always connected together to the same host or group of hosts.
Leaving out a volume would cause problems, so it is desired to keep this group of volumes
together at all times.
The volume group is used to achieve this in the configuration of the DS8000. Create a
volume group and add volumes to the group. Optionally add the host connection to the
same group, and you have a performed what has also been called LUN masking or
LUN/Host partitioning.
New method of LUN masking
Maps LUNs and host attachments (HBAs)
Create FB Volume Group
Student Notebook
V3.1.0.1
Uempty
Figure 6-78. Create FB Volume Group Define Properties SS481.0
Notes:
This panel lets you define the volume group properties and host type.
Limits allowed host types
Same blocksize and addressing mode
Create FB Volume Group - Define Properties
Student Notebook
Figure 6-79. Create FB Volume Group Select Host Attachments SS481.0
Notes:
The host attachment can be defined to be associated with the group of volumes which
attach to it. This creates an association with the volumes and the host ports connecting
them together.
Limited by allowed host types specified in previous step
and host definitions created earlier
Optional may be defined later

Create FB Volume Group -
Select Host Attachments
Student Notebook
V3.1.0.1
Uempty
Figure 6-80. Create FB Volume Group Select Volumes SS481.0
Notes:
In this panel you get to select the volumes that are part of the volume group.
Compatible with host types specified in volume group properties
(Status information available in realtime mode only)
Create FB Volume Group - Select Volumes
Student Notebook
Figure 6-81. Help for Arrays SS481.0
Notes:
This is the DS8000 Information Center GUI. It can be launched separately and is very
detailed. It has many of the user manuals in full text in the contents.
Help for Arrays
Student Notebook
V3.1.0.1
Uempty
Figure 6-82. DS Storage Manager Summary SS481.0
Notes:
This is the Welcome screen and entry panel for the DS8000 Storage Manager, although
the DS6000 Storage Manager would look the same and has the same look and feel.
Easy-to-use, powerful and flexible
Wizards, Filters, Sorts, Hyperlinks, Copy/Paste
Includes optional automated methods
Similar look and feel for both DS6000 and DS8000
Similar look and feel for both realtime and simulated modes
DS Storage Manager Summary
Student Notebook
Student Notebook
V3.1.0.1
Uempty 6.5 Summary of Logical Configuration Differences
Student Notebook
Figure 6-83. Topic: Summary of Logical Configuration Differences SS481.0
Notes:
Requirements
Differences
Topic: Summary of Logical
Configuration Differences
Student Notebook
V3.1.0.1
Uempty
Figure 6-84. Summary of Logical Configuration Differences (1 of 2) SS481.0
Notes:
These are the major difference between the DS8000 and DS6000 Storage Manager
functions.
IBM TotalStorage DS8000 Storage Manager only
Internal DS MC
ESCON
Storage Image (LPAR)
Storage I/O adapter specification (for example, SW, LW, ESCON)
during Create Storage Unit
User-defined storage complex
Storage complex nickname
Summary of Logical
Configuration Differences (1 of 2)
Student Notebook
Figure 6-85. Summary of Logical Configuration Differences (2 of 2) SS481.0
Notes:
The DS6000 must have the Storage unit assigned to be able to retrieve the Machine
signature and activate the license keys required to install the unit and get thing working.
This function can only be done using the GUI, the DSCLI has no command for this
operation.
The DS6000 has no internal management console, so the SMC software must be installed
on an external workstation and if redundancy is required, then it should be installed on two
workstations and you can define an alternate SMC.
The DS6000 has an express configuration mode that simplifies the configuration of storage
and LUNs if the customer wants to get up and running quickly and has no particular
requirements other than to define some LUNs to use for hosts.
The DS6000 has two controllers and you can mirror the cache from server0 to server 1.
IBM TotalStorage DS6000 Storage Manager only
Assign Storage Unit
Set up communication between DS MC and DS6000
Define peer
Redundant DS MC
Express Configuration
Open systems, iSeries, zSeries
Mirrored write cache
Enabled by default
Can be disabled during standard open systems LUN creation
Required for iSeries LUNs (enabled by default and cant be disabled)
Configure date/time and notifications
Summary of Logical
Configuration Differences (2 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 6-86. DS8000/DS6000 and ESS Differences SS481.0
Notes:
These are is some of the differences between the ESS and the DS8000.
The obvious things are the increased number of LSS and volume addressing and the new
terms such as ranks and extent pools. Users can delete volumes dynamically, which was
not possible with the ESS. Also, you can mix 3380 and 3390 volumes in a CKD extent pool.
Thats huge, because in the ESS you had to define a entire array to the 3380 devices.
You can also group ports together and have that as one unit to deal with a host.
The other major difference is the graphical interface is not as graphical as the ESS
Specialist. The newness of the interface and for those familiar with the ESS Specialist, it
may not seem as intuitive.
There is offline configuration and upload and download of configuration files. This is not
available in the ESS Copy Services, although not as graphical in nature it has a much more
productive set of commands and functions.
LSS changes
Increased numbers of LSSs
No predetermined relation to ranks
Extent pools (Ranks, LSSs, volumes)
Server affinity (Server0 or Server1)
Can include both 3380s and 3390s
Volume changes
Increased numbers of volumes
Increased volume size (can be larger than a rank)
Dynamic Volume Deletion
Nicknames
Volume groups (Host attachments, volumes)
LUN masking
LUN sharing
Host port grouping
Offline configuration (initial configuration and modifications)
Configuration backup and cloning
Multiple Storage Images in a single Storage Unit
User roles
DS8000/DS6000 and ESS Differences
Student Notebook
Figure 6-87. DS Storage Manager Logical Configuration Summary SS481.0
Notes:
These are some of the new capabilities.
New capabilities
Increased number of logical volumes
More LSSs/LCUs -- no longer tied to single rank
Increased logical volume size
Not limited by rank size
Volumes can be individually deleted
Configuration can be downloaded in spreadsheet format
More granularity of user roles
Nicknames
Realtime and Simulated
Important planning considerations
LSSs
Extent Pools
Volume sizes
Volume Groups
DS Storage Manager
Logical Configuration Summary
Student Notebook
V3.1.0.1
Uempty
Figure 6-88. Express Configuration (DS6000) SS481.0
Notes:
This is the Express Configuration wizard that saves you a lot of time.
Create volumes and volume groups
Open systems
iSeries
zSeries includes LCU
Define hosts and assign to volume groups
Arrays, ranks, extent pools will be automatically created
Express Configuration (DS6000)
Student Notebook
Figure 6-89. Express Configuration Volume Creation Open Systems SS481.0
Notes:
Select RAID type
Either 5 or 10
Amount of Unused Storage to Configure
A pull-down list: 100%, 75%, 50%, 25%.
User Defined: users specifies GBs to configure
Volume Size
The user selects the size they would like each volume to be, and the system computes
the number of volumes
The smallest volume size is one GB
Volume Quantity
When selected, the user can type in the number of volumes they wish to create
System can automatically calculate quantity based upon previous selections
Select RAID type
Either 5 or 10
Amount of Unused Storage to
Configure
A pull-down list: 100%, 75%, 50%,
25%.
User Defined: users specifies GBs to
configure
Volume Size
The user selects the size they would
like each volume to be, and the system
computes the number of volumes
The smallest volume size is one GB
Volume Quantity
When selected, the user can type in the
number of volumes they wish to create
System can automatically calculate
quantity based upon previous
selections
Create Host (optional)
Checkbox, if selected, takes the user to
the Host Creation Wizard after Volume
Creation is complete
Express Configuration
Volume Creation - Open Systems
Student Notebook
V3.1.0.1
Uempty
Create Host (optional)
Checkbox, if selected, takes the user to the Host Creation Wizard after volume creation
is complete.
Student Notebook
Figure 6-90. Express Configuration - Volume Naming SS481.0
Notes:
Set the nicknames for the volumes to be created.
Express Configuration - Volume Naming
Student Notebook
V3.1.0.1
Uempty
Figure 6-91. Express Configuration - Volume Group SS481.0
Notes:
Add the volumes to the volume groups.
Express Configuration - Volume Group
Student Notebook
Figure 6-92. Express Configuration - Host Creation SS481.0
Notes:
Define the host attachments.
Host type
Nickname
Description
Express Configuration - Host Creation
Student Notebook
V3.1.0.1
Uempty
Figure 6-93. Express Configuration - Host Ports SS481.0
Notes:
Define the host ports.
HBA quantity
HBA protocol
Fibre channel switched
Fibre channel arbitrated loop
Option to group ports
Express Configuration - Host Ports
Student Notebook
Figure 6-94. Express Configuration -- Host WWPNs SS481.0
Notes:
Define the WWPNs for the host ports.
Express Configuration - Host WWPNs
Student Notebook
V3.1.0.1
Uempty
Figure 6-95. Express Configuration -- Assign Host to Volume Group SS481.0
Notes:
This panel has Open and iSeries-only volume input controls which allow the user to map
the earlier defined volume group to the newly created host attachment. The user needs to
select the option to map the host attachment to volume group, then select Next. Volume
and host attachment information is given.
Open and iSeries hosts only
Allows host mapping to previously defined volume group
Express Configuration -
Assign Host to Volume Group
Student Notebook
Figure 6-96. Other Configuration Tasks SS481.0
Notes:
License activation keys (obtained from DSFA Web site)
Apply configuration from simulated configurator
User administration
Other Configuration Tasks
Student Notebook
V3.1.0.1
Uempty
Figure 6-97. Storage Image (DS8000*) Apply Activation Keys SS481.0
Notes:
Apply Activation Keys
Real-time mode only
Next step -- enter keys for operating environment and advanced
functions, or import .xml file previously downloaded from DSFA Web
site
*For DS6000, apply keys to Storage Unit (Configure Storage Unit)
Student Notebook
Figure 6-98. Storage Image (DS8000*) - Apply Configuration SS481.0
Notes:
Apply Configuration
Simulated mode only
Logical configuration created offline is applied via the network
*For DS6000, apply configuration to Storage Unit
Student Notebook
V3.1.0.1
Uempty
Figure 6-99. Apply Configuration Select Application Method SS481.0
Notes:
Apply Configuration -
Select Application Method
Student Notebook
Figure 6-100. Apply Configuration Select Storage Complex SS481.0
Notes:
Apply Configuration - Select Storage Complex
Student Notebook
V3.1.0.1
Uempty
Figure 6-101. Apply Configuration - Authenticate SS481.0
Notes:
Apply Configuration - Authenticate
Student Notebook
Figure 6-102. Apply Configuration Select Storage Unit SS481.0
Notes:
Apply Configuration - Select Storage Unit
Next step -- select storage image (DS8000)
Logical configuration activation is complete!
Student Notebook
V3.1.0.1
Uempty
Figure 6-103. Manage Configuration Files SS481.0
Notes:
Student Notebook
Figure 6-104. User Administration SS481.0
Notes:
User Administration
Student Notebook
V3.1.0.1
Uempty
Figure 6-105. Add User SS481.0
Notes:
Add User
Student Notebook
Figure 6-106. Help for Arrays SS481.0
Notes:
Help for Arrays
Student Notebook
V3.1.0.1
Uempty Checkpoint
Exercise -- Unit 6 - Checkpoint
1. T/F The DS8000 is a GUI interface that must be installed on a
customer workstation to use the 0DS800 Storage Manager
2. T/F The DS8000 Storage Manager can be online or offline.
3. T/F The DS8000 Storage Manager can create configuration files
which can be downloaded to the DS8000 subsystem and used to
configure the DS8000.
4. T/F The DS8000 Storage manager is the only way available to
configure the DS8000.
5. T/F The DS8000 Storage Manager is a common software package
for both the DS6000 and the DS8000 Storage Subsystems.
Student Notebook
Notes:
Unit Summary
Describe the DS6000/DS8000 Hardware Management Console
Describe the internal Ethernet switches in the DS8000 storage unit
Describe how to access the setup of the HMC
Describe the network topology
Describe the VPN consideration and setup
Describe the network restrictions when access the HMC or the
DS8000 storage servers
Student Notebook
Copyright IBM Corp. 2005 Unit 7. DS8000 and DS6000 Performance, TPC and Productivity Data 7-1
V3.1.0.1
Uempty
Unit 7. DS8000 and DS6000 Performance, TPC and
Productivity Data Center Utility
The throughput provided by the new DS8000 series is intended to
enable customers to configure large storage systems without limited
throughput capabilities. As a point of comparison, the DS8100 can
provide up to three times the throughput of the IBM TotalStorage
Enterprise Storage Server (ESS) Model 800, and the DS8300 can
provide up to seven times the Model 800' throughput, depending on
workload. This can enable customers to consider consolidating as
many as 16 Model 800, or similar, storage systems into a single
storage system. For customers who have concerns about running both
test and production applications in the same system, or perhaps z/OS
and open systems applications together, certain configurations of the
DS8300 offer the capability to partition the storage system into two
Storage System LPARs. This can allow isolation and protection of
mission-critical workloads within the same physical DS8300.
Previously, the only way to accomplish this was through the
implementation of multiple physical storage arrays, raising the
possibility of significantly greater costs.
Describe the current measured DS8000 performance charts
Describe the purpose of the TotalStorage Productivity Center TPC
2.3
Be able to install and use the PDCU Data Collection Utility
- Performance Data Collection Utility (PDCU)
- Installation and use
- Reports
Accountability:
Checkpoint
Student Notebook
Notes:
The objectives unit gives you an overview of the performance numbers for a DS8000 and
DS6000 and a look at how to collect performance information using a PDCU data collection
tool for TPC.
Unit Objectives
After completing this unit, you should be able to understand:
Current measured DS8000 performance charts
The TotalStorage Productivity Center
TPC 2.3
Performance Data Collection Utility (PDCU)
Installation and use
Reports
Student Notebook
V3.1.0.1
Uempty 7.1 DS8000 Performance
Student Notebook
Figure 7-2. Topic: DS8000 Performance SS481.0
Notes:
Topic: DS8000 Performance
DS8000 Performance
DS6000 Performance
TotalStorage Productivity Center (TPC) and
Productivity Data Center Utility (PDCU)
Student Notebook
V3.1.0.1
Uempty
Figure 7-3. Host Adapter Performance - Single Port SS481.0
Notes:
Each of the hardware components was designed or selected to support dramatically
improved bandwidth. For example, the improvement in single port random throughput is
demonstrated above. The Fibre Channel per-port random throughput doubles that of the
ESS 800. Note that in today's marketplace, many enterprise disk storage systems handle
only 17,000 to 18,000 ops/sec, whereas a single port with the new DS8300 can handle
38,000.
Host Adapter Performance - Single Port
- Near linear scaling to four ports / host adapter
17500
38000
0
10
20
30
40
T
h
o
u
s
a
n
d
s
ESS 800
DS8100
4 K ops/sec per host port
145
206
0
50
100
150
200
250
M
B
/
s
e
c
ESS 800
DS8100
Sequential throughput per
host port
DS8300
Figure 1
Figure 2
Student Notebook
Figure 7-4. Maximum Total System IOPS/sec, Open and z/OS SS481.0
Notes:
Recognizing that 100% cache read hits is not a real-life production workload, it can still be
a useful indicator of overheads, front-end and cache efficiency. The DS8300 scales up to
128 Fibre Channel or FICON ports, yielding total box maximum throughput of 3.4 million
IOPS/sec; in the graph above. This is roughly a 34-fold increase for open systems
attachment over the ESS 800.
Consider Figure 3, which shows maximum RAID array bandwidth for simultaneous multiple
open sequential streams. Figure 4 shows maximum RAID array bandwidth for
simultaneous multiple z/OS sequential streams.
105000
3400000
0
1
2
3
4
M
i
l
l
i
o
n
s
ESS 800
DS8300
Max IOPS/sec open
68500
236500
0
50
100
150
200
250
T
h
o
u
s
a
n
d
s
ESS 800
DS8300
Max IOPS/sec zOS
Maximum Total System
IOPS/sec, Open and z/OS
Figure 3
Figure 4
Student Notebook
V3.1.0.1
Uempty
Figure 7-5. Sequential Bandwidth SS481.0
Notes:
The maximum RAID array bandwidth nearly touches 250 MB/sec, which is a threefold
increase compared to the ESS Model 800 and its competitors. So, the DS8000 can provide
substantially greater throughput for a single logical volume or LUN, meaning that a single
logical volume or LUN can sustain far greater demand while maintaining good
performance. In Figure 6 the z/OS single stream bandwidth is also three times that of the
ESS Model 800.
S
e
q

R
e
a
d
S
e
q

W
r
i
t
e
0
50
100
150
200
250
300
M
B
/
s
e
cM800 no AAL
M800 AAL
DS8100
Single array bandwidth
Multiple streams
43
142
0
50
100
150
T
h
r
o
u
g
h
p
u
t

(
M
B
/
s
e
c
)
ESS 800
DS8100
Single stream bandwidth
z/OS QSAM Bufno=5 Read
Sequential Bandwidth
-- 4X array bandwidth improvement!
Figure 5
Figure 6
Student Notebook
Figure 7-6. Total Disk System Sequential Bandwidth SS481.0
Notes:
Figure 7 indicates total disk system sequential bandwidth for the DS8100, the two-way
model, compared to its predecessor the ESS 800. The DS8100 achieves essentially 2
GB/sec, a more than threefold increase compared to the ESS 800. Sequential bandwidth is
the most frequent limit to growing a disk system' capacity, and this robust throughput
enables a user to configure a DS8100 with 20 TB of physical disk capacity and potentially
much more with proper workload evaluation and capacity planning. The hardware
infrastructure for the DS8300 doubles most of the components for the DS8100, with two
switched fibre interconnects rather than one. This supports double the total system
sequential throughput. A rule of thumb for the DS8000 is that the sequential bandwidth is
the same number in GB/sec as the number of the processors; that is, the 2-way delivers 2
GB/sec, the 4-way 4 GB/sec, and so forth. IBM has previewed plans to introduce an 8-way
machine with 8 GB/sec total sequential throughput in 2005. Since IBM currently delivers a
64-way POWER5 processor, IBM can scale these machines far greater than the current
customer demand for throughput in a single footprint.
Read BW Write BW
0
500
1000
1500
2000
M
B
/
s
e
c
ESS 800 DS8100
Total Disk System Sequential Bandwidth
Figure 7
Student Notebook
V3.1.0.1
Uempty
Figure 7-7. z/OS Cache Standard Workload SS481.0
Notes:
For many customers database workloads are their most important, representing their most
critical data vital to their business operations. For understanding the performance of such
workloads with the DS8000 we present the cache standard workload for z/OS and
70/30/50, an open systems OLTP benchmark. Those workloads are described below.
Figure 8 compares the performance of the ESS 800 with turbo 2 option implemented, the
DS8100, and the DS8300 for the cache standard workload. Cache standard workloads in
this example are 73% read hit ratio with around a 3:1 read-to-write ratio, and a 4 KB
average transfer size.
0 10000 20000 30000 40000 50000 60000
SIOs/sec
0
5
10
15
(
m
s
)
R
e
s
p
o
n
s
e

T
i
m
e
ESS 800 128 15K
DS8100 128 10K
DS8300 256 10K
z/OS Cache Standard Workload
Figure 8
Student Notebook
Figure 7-8. Open Systems 70/30/50 Workload ESS 800 and DS8100 SS481.0
Notes:
Figure 9 shows a graph of a similar study, the 70/30/50 workload run in an AIX (that is,
UNIX-based) environment. Workload is again 30% write and but only 50% RHR.
0 10000 20000 30000 40000
(IO/sec)
Throughput
0
5
10
15
(
m
s
)
R
e
s
p
o
n
s
e

T
i
m
e
ESS 800 128 10K
ESS 800 128 15K
DS8100 128 10K
Open Systems 70/30/50
Workload ESS 800 and DS8100
Figure 9
Student Notebook
V3.1.0.1
Uempty
Figure 7-9. Global Mirror Write Overhead for Transfer SS481.0
Notes:
Figure 13 demonstrates how IBM has improved PPRC overheads over successive
generations of disk storage system. The bars represent PPRC write overhead added in (as
disconnect time) for the transfer to secondary at campus distances.
This quite simply yields synchronous remote copy performance second to none. Even with
the ESS 800, some Metro Mirror customers experience average response time for
production database workloads of 800 microseconds (0.8 ms). With the DS8000 that has
the potential to improve more, yielding even faster transaction response time.
4
5.5
1.3
1.15
0.8
0.53
0.38
RAMAC
RVA
ESS F20 ESCON
ESS F20 FICON
ESS 800 ESCON
ESS 800 FICON
DS8100
0
2
4
6
D
i
s
c

t
i
m
e

(
m
s
)
Global Mirror Write Overhead for Transfer
4 K write hit
Figure 13
Student Notebook
Figure 7-10. ESS 800 PPRC versus DS8000 Global Mirror SS481.0
Notes:
The Global Mirror performance has always been a hindering factor to customers because
of the potential performance hit that would be taken to implement the Metro Mirror function
also called PPRC-Sync into the production workload. Figure 14 compares the performance
response times of the ESS-800 Turbo with FCP links to the DS8100 with FCP links at 0 km
and 303 km. Truly, the lines on this chart would indicate that the differences are minimal
and running this type of function in production environments is not going to severely hold
up production workloads as have previous implementations of this technology.
0 8000 16000 24000 32000 40000 48000
(IO/sec)
Throughput
0
2
4
6
8
10
12
14
(
m
s
)
R
e
s
p
o
n
s
e

T
i
m
e

Turbo II Base (No PPRC)
Turbo II (2) FCP Links, 0 km
Turbo II (2) FCP Links, 303 km
DS8100 (2) FCP Links, 0 km
DS8100 Base (No PPRC)
DS8100 (2) FCP CN2000, 303 km
8 FICON Express 2 Gb/sec Host Attach
Cache Standard Workload: R/W = 3, RHR = 0.74, Dstg. = 11.6%, Xfer = 4 KB
128 DDMs RAID 5 - 3 PAV Aliases/Base
z/OS Cache Standard Workload
ESS 800 PPRC versus DS8000 Global Mirror
Figure 14
Student Notebook
V3.1.0.1
Uempty
Figure 7-11. FlashCopy Performance Improvements with DS8000 SS481.0
Notes:
Faster microprocessors in the device adapters and greater back-end bandwidth contribute
to significant FlashCopy performance improvements. Establish times, already quick with
the ESS 800, are cut in half migrating to the DS8100, and the background copy data rate is
nearly tripled.
7
1.2
0.6
0
1
2
3
4
5
6
7
8
(
S
e
c
)
E
l
a
p
s
e
d

T
i
m
e
FC V1
FC V2
DS8100
Elapsed Time
Establish 256 3390-3 vols
15.7
34.5
104
0
20
40
60
80
100
120
M
B
/
s
e
c
Background Copy Datarate
Single Volume Copy
FlashCopy Performance
Improvements with DS8000
Figure 15
Figure 16
Student Notebook
Student Notebook
V3.1.0.1
Uempty 7.2 DS6000 Performance
Student Notebook
Figure 7-12. Topic: DS6000 Performance SS481.0
Notes:
Topic: DS6000 Performance
DS8000 Performance
DS6000 Performance
Student Notebook
V3.1.0.1
Uempty
Figure 7-13. How Migrating to DS6800 Might Affect Hit Ratios SS481.0
Notes:
One possible consequence of migrating to the DS6800 from an ESS-800 would be a lower
cache hit ratio, especially if the cache size in the ESS-800 is much larger than the 4 GB in
the DS6800. The chart above shows the drop in cache hit ratios if the ESS-800 had 16 GB
of cache and the workload was migrated to the DS6800.
16 * 73
GB
59% 5.8 K
(HDD)
ESS 800 RHR
16 GB cache
DS6800 RHR
4 GB cache
0.95 0.90
0.90 0.80
0.80 0.60
0.70 0.40
Configuration: num
of drives *
Cache-to-backstore
ratio
Hit Ratio / Max IO
(Lim)
32 * 146
GB
.0007 22% 8.4 K
(HDD) 32 * 73
GB
.0014 43% 10.2 K
(HDD) .0028
How Migrating to DS6800
Might Affect Hit Ratios
Student Notebook
Figure 7-14. Cache Read Hit Performance - 512 Byte SS481.0
Notes:
The cache hit performance of the DS6800 displays exceptionally good performance in
comparison to several other subsystems of similar size and configuration. In the chart
above, the DS6800 is compared to an EMC CX700 and a DS4500 or FastT900, and an
ESS-750 when doing small block I/Os. The DS6800 is five-fold better than the ESS, three
times that of the DS4500, and almost twice the performance of the EMC CX700.
Cached Reads - 512 bytes
0
50
100
150
200
250
300
350
(
K
I
O
P
s
)
T
h
r
o
u
g
h
p
u
t
DS6800
ESS 750
DS4500
EMC CX700
Cache Read Hit Performance - 512 Byte
Student Notebook
V3.1.0.1
Uempty
Figure 7-15. Cache Read Hit Performance - 64 KB SS481.0
Notes:
For larger blocks the DS6800 still displays the best performance, but the others
subsystems, particularly the EMC, much better. This is a true throughput chart. Unlike the
last, this is big block, 64 KB transfers, and we are measuring throughput of cached reads of
these large data blocks so we get to see how the DS6800 stacks up against the ESS and
DS4500.
Cache Read Hit Performance - 64 KB
Cached Reads - 64 KB
0
500
1000
1500
2000
T
h
r
o
u
g
h
p
u
t

(
M
B
/
s
e
c
)
DS6800
ESS 750
DS4500
EMC CX700
Student Notebook
Figure 7-16. DS6800 Cache Read Hit Performance (Max IOPs) SS481.0
Notes:
322724
319910
275925
512 byte 2KB 4KB
0
50000
100000
150000
200000
250000
300000
350000
(
I
O
/
s
e
c
)
T
h
r
o
u
g
h
p
u
t
1 Port
2 Port
4 Port
8 Port
DS6800 Cache Read
Hit Performance (Max IOPs)
Student Notebook
V3.1.0.1
Uempty
Figure 7-17. DS6800 Cache Read Hit Response Time SS481.0
Notes:
The chart above shows the DS6800 does get a little better response time for small or large
blocks than the ESS.
0.2
0.23
0.68
0.3
0.34
1
512 byte 4KB 64KB
0
0.2
0.4
0.6
0.8
1
1.2
(
m
s
)
R
e
s
p
o
n
s
e

T
i
m
e
ESS 750
DS6800
DS6800 Cache Read Hit Response Time
Student Notebook
Figure 7-18. DS6800 OLTP Workloads (RAID5) SS481.0
Notes:
The response time of the ESS 750 is compared to the DS6800 for OLTP processing a
typical 70/30/50 workload. The systems are pretty similar until about 7000 I/Os per second
and then the ESS gets lower response times.
DS6800 OLTP Workloads (RAID5)
0 2000 4000 6000 8000 10000 12000
(IO/sec)
Throughput
0
1
2
3
4
5
6
7
8
9
10
(
m
s
)
R
e
s
p
o
n
s
e

T
i
m
e
ESS 750 70/30/50
DS6800 70/30/50
Note: ESS 750 results used 72.8 GB 15 KRPM disks for comparison purposes only.
This is not a supported configuration on the ESS 750.
64 x 73 GB 15 KRPM Disks (8 Ranks)
Student Notebook
V3.1.0.1
Uempty
Figure 7-19. DS6800 4 KB Read Miss Performance SS481.0
Notes:
The chart above supports the idea that more is better. More ranks, more disks, better
performance. Somewhat predictable, but the chart does illustrate the point.
1886
3486
5271
7092
0 1000 2000 3000 4000 5000 6000 7000 8000 9000
(IO/sec)
Throughput
0
10
20
30
40
50
60
(
m
s
)
R
e
s
p
o
n
s
e

T
i
m
e
1 Rank
2 Ranks
3 Ranks
4 ranks
DS6800 4 KB Read Miss Performance
Student Notebook
Figure 7-20. Full Box 64 KB Sequential Performance SS481.0
Notes:
Again, more is better. The DS4500 with 96 disks does better than the DS6800 with 16.
However, the DS6800 does outperform the ESS-750 with seven 8-packs or 56 DDMs.
The internal bandwidth of the DS6800 does well on big blocks and sequential workloads.
Seq. Rd from Disk Seq. Wr. to Disk
0
100
200
300
400
500
600
(
M
B
/
s
e
c
)
T
h
r
o
u
g
h
p
u
t
DS6800 (16 disks)
ESS 750 (56 disks)
DS4500 (96 disks)
Notes:
All writes are mirrored in cache
Number of disks listed does not include spare disks
Full Box 64 KB Sequential Performance
Student Notebook
V3.1.0.1
Uempty
Figure 7-21. Single Stream 64 KB Sequential Performance SS481.0
Notes:
Now the single stream rate shows the effect of the switched FC DDMs over SSA in the
ESS-750 or FC-AL in the DS4500. Sequential read is over 80 MB/sec from a single disk
and 50 MB/sec on writes.
Seq. Rd from Disk - 1 Stream Seq. Wr. to Disk - 1 Stream
0
10
20
30
40
50
60
70
80
90
(
M
B
/
s
e
c
)
T
h
r
o
u
g
h
p
u
t
DS6800
ESS 750
DS4500
Single Stream 64 KB Sequential Performance
Student Notebook
Student Notebook
V3.1.0.1
Uempty 7.3 TotalStorage Productivity Center (TPC) and Productivity
Data Center Utility (PDCU)
Student Notebook
Figure 7-22. Topic: TotalStorage Productivity Center (TPC) and Productivity Data Center Utility (PDCU) SS481.0
Notes:
The TotalStorage Productivity Center is in the process of being upgraded to support the
DS8000. In the interim, there is a utility which can be used to manually collect performance
data and produce report to help measure the performance of the DS8000.
Topic: TotalStorage Productivity Center (TPC)
and Productivity Data Center Utility (PDCU)
DS8000 Performance
DS6000 Performance
Student Notebook
V3.1.0.1
Uempty
Figure 7-23. Storage Infrastructure Management SS481.0
Notes:
The TPC product is an IBM product which is designed to help manage the storage and
SAN infrastructure and provide reporting and monitoring capability for users of IBM and
non-IBM products. The diagram above gives us an idea of the three major components of
TPC which the Productivity Center for Data is the replacement for the current ESS Expert.
ESS Expert
TotalStorage Productivity Center
Standard Edition
Version 2 Release 3
Productivity
Center for
Data
Productivity
Center for
Fabric
Productivity
Center for
Disk
ESS
ESS DS8000 DS6000 DS4000
Integrating storage management to provide a single point of control
SVC
Storage Infrastructure Management
Managing IBM TotalStorage DS Family
Student Notebook
Figure 7-24. Overview of TPC V2R3 SS481.0
Notes:
The Productivity Center for Data is the replacement for the TotalStorage ESS Expert. This
product has been in development and, support for the ESS, and is currently being
developed for the DS6000 and DS8000. During the interim to its release a component of
TPC is being used to collect data from DS6000 and DS8000 for performance reporting. We
look at this utility called PDCU in this section.
Theme 1: Provide management support for DS8000 and DS6000
Productivity center for data
Discovery and asset/capacity reporting
Productivity center for fabric
Unique ICONs for DS8000 and DS6000
Launch DS Storage Manager UI
Topology views for SAN fabric, LUNs, hosts
Productivity center for disk
Discovery and performance management
Device management
Theme 2: Productivity center for replication support for
TotalStorage
Significant improvements in scalability, removal of current
limitations
Ability to manage ESS model 800 attached to z/OS
Support for ESS model 800 and SAN volume controller FlashCopy
and Metro Mirror administration and management of copy sessions
Overview of TPC V2R3
Student Notebook
V3.1.0.1
Uempty
Figure 7-25. The Performance Data Collection Utility (PDCU) SS481.0
Notes:
The Performance Data Collection Utility (PDCU) can be used to gather and output basic
configuration information and performance statistics for the IBM DS8000 and DS6000
model storage devices.
This information is gathered by connecting to the DS Network Interface running on the
DS8000 HMC or DS6000.
A tactical offering for early adopters of DS8000 and DS6000
Collects performance metrics for offline analysis
Quickly available for customer usage during DS8000 and DS6000
implementation and rollouts
Sample Excel macro provided to map the data
Strategic solution is TPC standard edition
Productivity center for disk
Graphical performance management (gauges, thresholds)
Supports ESS model 800, DS8000, DS6000 and SVC
Storage configuration (including zoning, LUN allocation)
Productivity center for data
Asset and capacity reporting
File systems and database management
Chargeback capability
The Performance Data
Collection Utility (PDCU)
Student Notebook
Figure 7-26. PDCU Scope SS481.0
Notes:
PDCU is used to collect data for performance report for one DS6000 or one DS8000 at a
time.
Performance data collection utility for DS8000 and DS6000
Support one DS8000 and DS6000 at a time
Can run multiple instances of the utility to allow monitoring of multiple (at least
three fully configured) DS8000 and DS6000 devices
Parameters and documentation supports multiple data files
PDCU has a command line interface
Consistent with the SSG command line interface guidelines,
Allows output to be written or piped to a file or another process
Provides the following command line features:
Comma separated value output (to standard out only)
Interval between retrievals (default being only one retrieval)
Duration over which retrievals should be performed
Header lines preceding each set of lines for an element
Element type code as first item in each output line
Support for z/OS - and open- attached DS8000 and DS6000
Designed to support a future migration tool that allows the collected data to be
imported into the TPC performance database. This implies the data format is
consistent with the MDM PM data.
PDCU Scope
Student Notebook
V3.1.0.1
Uempty
Figure 7-27. PDCU - Supported Platforms and Storage SS481.0
Notes:
PDCU runs on the following platforms (please make sure you have downloaded PDCU for
the correct platform):
Windows NT, Windows 2000, Windows 2003, Windows XP
Red Hat Linux Advanced Server 2.1, 3.0
AIX 5
PDCU - Supported Platforms and Storage
PDCU supports both the DS8000 and DS6000
Note microcode levels will need to be at specific levels
PDCU supports both open and fixed volumes
PDCU has been built and tested on the following systems:
Windows NT, Windows 2000, Windows 2003, Windows XP
Red Hat Linux Advanced Server 2.1, 3.0
AIX 5
Student Notebook
Figure 7-28. PDCU Installation SS481.0
Notes:
To install PDCU, extract the files from the archive. A new directory named PerfUtil should
be created. PDCU does not need to be installed as Administrator on Windows or as root on
Linux and AIX.
Windows only:
Do not install PDCU into a path that contains the character sequence pd. Doing so may
result in an error message about the UTE.dll.
PDCU Installation
The installation process is the essence of simplicity:
Download appropriate zip (or equivalent) file for machine on
which PDCU is to be installed.
Extract the file to desired location.
Please note that there is one Windows caveat: Do not install
PDCU into a path that contains the character sequence pd. Doing
so may result in an error message about the UTE.dll.
Student Notebook
V3.1.0.1
Uempty
Figure 7-29. Configuring and Running PDCU SS481.0
Notes:
Edit the file sample_script.txt, included with PDCU, so it contains the information necessary
to connect to your DS device: the DS Network Interface IP address or hostname,
username, and password; and the DS device ID.
On Windows, run this command:
perfcollectcli -script sample_script.txt > output.txt
On Linux or AIX, run this command:
perfcollectcli.sh -script sample_script.txt > output.txt.
Configuring and Running PDCU
Before it can collection performance statistics, PDCU must be
provided with information about the DS via the adddsserver
command:
perfcollectcli adddsserver svr DS_IP usr username passwd
password DS_ID
Once configured all that remains is to start collecting performance
data
perfcollectcli startdscollection i interval d duration DS_ID
Note: PDCU writes all configuration and statistic information to
standard out so this output should be piped to a file if the client
wishes to actually use it ( > filename.txt in Windows)
Alternatively, a quick-start script is provided which, once edited to
have the correct DS information, issues both of the above
commands
Student Notebook
Figure 7-30. Where the PDCU Data is Stored SS481.0
Notes:
The data can be output put to a flat .txt file or .csv file for use in a XCEL spread sheet.
PDCU data is NOT stored by default, but is rather sent to standard
out. If the data needs to be stored (as is likely) the user should
redirect standard out to a file.
PDCU log information (including, in debug mode, raw counter
values from ESSNI) is stored in perfcollectcli.log
Where the PDCU Data is Stored
Student Notebook
V3.1.0.1
Uempty
Figure 7-31. PDCU Sample Configuration Data Output SS481.0
Notes:
The following is an example of the PDCU output, with field descriptions instead of actual
data. Abbreviations follow the IEC international standard (for example, 1 GB = 10^9 B =
1,000,000,000 B). See the NIST reference on SI binary prefixes at this URL for details.
http://physics.nist.gov/cuu/Units/binary.html
Performance Data Collection
---------------------------
DS Device ID: IBM.2107.7503001
Data Collection Start: 2005-01-21 12:58:11 PST
Data Collection Frequency: 5 minutes
Data Collection Duration: 1 hour
IBM Performance Data Collection Utility version 1.0.0
PDCU Sample Configuration Data Output
Student Notebook
Configuration Data
------------------
Machine Type: 2107
Model Number: 922
Cache Memory: not available at this time.
NVS Memory: not available at this time.
Port Level Configuration
------------------------
Port ID - Unique identifier of the HBA in hex.
Location - Location of the port.
Type - Port type: ESCON, FC-LW, FC-SW, or UNKNOWN.
Speed (Gbps)- The port speed in Gbps.
WWPN - The world-wide port name for the FC port in hex.
Topology - The FC port topology: FC-AL, FCP, FICON, FCP/FICON, or UNKNOWN.
Rank Level Configuration
------------------------
Rank ID - Unique identifier of the rank in hex.
Pool ID - Unique identifier of the rank's extent pool in hex.
Extent Type - Extent type: FB or CKD.
Capacity - Total rank capacity in GB.
RAID - RAID level: RAID-5, RAID-10, or UNKNOWN.
Num Arrays - The number of arrays configured for this rank.
RPM - The minimum RPM of all rank disks.
Size - The minimum capacity of all rank disks in GB.
Volume Level Configuration
--------------------------
Volume ID - Unique identifier of the volume in hex.
Volume SN - Serial number. The VOLSER for CKD or the SCSI LUN for FB.
Nickname - User-specified volume nickname.
LSS - The LSS of the volume in hex.
Student Notebook
V3.1.0.1
Uempty
Figure 7-32. PDCU Script Invocation SS481.0
Notes:
Above is an example of the Quick Start script Invocation. The PDCU package comes with a
script, and with minimal modifications it can be made ready to start the collection.
PDCU Script Invocation
Student Notebook
Figure 7-33. The Report Generator Example Macro SS481.0
Notes:
There is a report macro being developed for XCEL reporting. This macro takes the output
of the PDCU data collection process and turns it into some XCEL graphs which can be
displayed or printed.
PDCU
File
Macro
(1) Collect Performance Data
(2) Import into Spreadsheet
(3) Port, Rank and Volume
Reports Generated
The Report Generator - Example Macro
Packaged with PDCU is an
example Excel macro for
importing a file with stored PDCU
output, performing some basic
calculations, and then generating
some basic graphs.
Flat file created by PDCU is
imported into Excel spreadsheet
via example macro
Reports are generated
Port reports
Rank reports
Volume reports
Customization can be done on
the reports
Visual Basic experience required
Runs on Excel 2002
Student Notebook
V3.1.0.1
Uempty
Figure 7-34. Port Performance Data Collected via PDCU SS481.0
Notes:
Port-Level Statistics
Interval Start: 2005-01-21 12:58:21 PST
Interval End: 2005-01-21 01:03:21 PST
Interval Length: 300 seconds
---------------------
Port ID - Unique identifier of the HBA in hex.
Speed (Gbps) - The port speed in Gbps.
I/O Rate - Average number of I/O operations per second.
Data Rate - Average transfer rate in KBps.
Avg Xfer Size - Average transfer size in KB.
Avg Resp Time - Average I/O response time in milliseconds.
FB Read I/Os - Number of FCP read operations.
FB Write I/Os - Number of FCP write operations.
FB KBs Read - Number of KBs read via FCP.
FB KBs Written - Number of KBs written via FCP.
Interval Length- Interval length truncated to the second.
PPRC Accum Send Time- Total time spent on PPRC write in
milliseconds.
PPRC Accum Recv Time- Total time spent on PPRC read in milliseconds.
CKD KBs Written- Number of KBs written via FICON. CKD KBs Read- Number of KBs read via FICON.
CKD Accum Write Time- Total time spent on FICON write in
milliseconds.
CKD Accum Read Time- Total time spent on FICON read in milliseconds.
PPRC Write I/Os- Number of PPRC write operations. PPRC Read I/Os- Number of PPRC read operations.
PPRC KBs Written- Number of KBs written for PPRC activity. PPRC KBs Read- Number of KBs read for PPRC activity.
CKD Write I/Os- Number of FICON write operations. CKD Read I/Os- Number of FICON read operations.
FB Accum Write Time- Total time spent on FCP write in
milliseconds.
FB Accum Read Time- Total time spent on FCP read in milliseconds.
FB KBs Written- Number of KBs written via FCP. FB KBs Read- Number of KBs read via FCP.
FB Write I/Os- Number of FCP write operations. FB Read I/Os- Number of FCP read operations.
Avg Resp Time- Average I/O response time in milliseconds. Avg Xfer Size- Average transfer size in KB
Data Rate- Average transfer rate in KBps I/O Rate- Average number of I/O operations per second.
Speed (Gbps)- The port speed in Gbps. Port ID- Unique identifier of the HBA in hex
Port Performance Data Collected via PDCU
Student Notebook
FB Accum Read Time - Total time spent on FCP read in milliseconds.
FB Accum Write Time - Total time spent on FCP write in milliseconds.
CKD Read I/Os - Number of FICON read operations.
CKD Write I/Os - Number of FICON write operations.
CKD KBs Read - Number of KBs read via FICON.
CKD KBs Written - Number of KBs written via FICON.
CKD Accum Read Time - Total time spent on FICON read in milliseconds.
CKD Accum Write Time - Total time spent on FICON write in milliseconds.
PPRC Read I/Os - Number of PPRC read operations.
PPRC Write I/Os - Number of PPRC write operations.
PPRC KBs Read - Number of KBs read for PPRC activity.
PPRC KBs Written - Number of KBs written for PPRC activity.
PPRC Accum Recv Time - Total time spent on PPRC read in milliseconds.
PPRC Accum Send Time - Total time spent on PPRC write in milliseconds.
Interval Length - Interval length truncated to the second.
Student Notebook
V3.1.0.1
Uempty
Figure 7-35. Rank Performance Data Collected via PDCU SS481.0
Notes:
Rank-Level Statistics
Interval End: 2005-01-21 01:03:21 PST
---------------------
Rank ID - Unique identifier of the rank in hex.
RAID Type - RAID type: RAID-5, RAID-10, or UNKNOWN.
Num of Arrays - Number of arrays configured for the rank.
Read I/O Rate - Average number of read I/O operations per second.
Write I/O Rate - Average number of write I/O operations per second.
Read Data Rate - Average read transfer rate in KBps.
Write Data Rate - Average write transfer rate in KBps.
Avg Read Xfer Size - Average read transfer size in KB.
Avg Write Xfer Size - Average write transfer size in KB.
Avg Read Resp Time - Average read response time in milliseconds.
Accum Read Time- Total time spent reading in milliseconds. KBs Written- Number of KBs written.
Interval Length- Interval length truncated to the second. Accum Write Time- Total time spent writing in milliseconds.
KBs Read- Number of KBs read. Write I/Os- Number of write I/O operations
Read I/Os- Number of read I/O operations. Avg Write Resp Time- Average write response time in
milliseconds
Avg Read Resp Time- Average read response time in
milliseconds.
Avg Write Xfer Size- Average write transfer size in KB
Avg Read Xfer Size- Average read transfer size in KB. Write Data Rate- Average write transfer rate in KBps
Read Data Rate- Average read transfer rate in KBps. Write I/O Rate- Average number of write I/O operations per
second
Read I/O Rate- Average number of read I/O operations per
second.
Num of Arrays- Number of arrays configured for the rank.
RAID Type- RAID type: RAID-5, RAID-10, or UNKNOWN. Rank ID- Unique identifier of the rank in hex.
Rank Performance Data Collected via PDCU
Student Notebook
Avg Write Resp Time - Average write response time in milliseconds.
Read I/Os - Number of read I/O operations.
Write I/Os - Number of write I/O operations.
KBs Read - Number of KBs read.
KBs Written - Number of KBs written.
Accum Read Time - Total time spent reading in milliseconds.
Accum Write Time - Total time spent writing in milliseconds.
Student Notebook
V3.1.0.1
Uempty
Figure 7-36. Volume Performance Data Collected via PDCU SS481.0
Notes:
Volume-Level Statistics
Interval End: 2005-01-21 01:03:21 PST
-----------------------
Volume ID - Unique identifier of the volume in hex.
I/O Rate - Average number of I/O operations per second.
Data Rate - Average transfer rate in KBps.
Avg Xfer Size - Average transfer size in KB.
Avg Resp Time - Average response time in milliseconds.
Delayed I/O Perc - Percentage of DASD Fast Write requests delayed due to NVS
full conditions.
Total Hit Perc - Cache hit percentage.
Read Hit Perc - Read cache hit percentage.
Write Hit Perc - Write cache hit percentage.
Non-seq Disk->Cache Ops- Number of disk to cache transfers
for non-sequential I/O operations.
Accum Write Time- Total time spent writing in milliseconds.
Non-seq DFW I/Os- Number of normal DASD Fast Write
requests.
NVS Allocs- Number of NVS space allocations.
Cache->Disk Ops- Number of cache to disk transfers for all I/O
operations.
Seq Disk->Cache Ops - Number of disk to cache transfers
for sequential I/O operations
NVS Delayed DFW I/Os- Number of DASD Fast Write
requests delayed due to NVS space constraints.
Seq DFW I/Os- Number of sequential DASD Fast Write
requests.
KBs Read- Number of KBs read. Seq Write Hits- Number of cache hits for sequential write
operations
Accum Read Time- Total time spent reading in milliseconds. KBs Written- Number of KBs written.
Seq Read Hits- Number of cache hits for sequential read
operations.
Non-seq Write Hits- Number of cache hits for normal write
operations
Non-seq Read Hits- Number of cache hits for normal read
operations.
Seq Write I/Os- Number of sequential write operations
Seq Read I/Os- Number of sequential read operations. Non-seq Write I/Os- Number of normal write operations.
Non-seq Read I/Os- Number of normal read operations. Write Hit Perc- Write cache hit percentage
Read Hit Perc- Read cache hit percentage. Total Hit Perc- Cache hit percentage.
Delayed I/O Perc- Percentage of DASD Fast Write requests
delayed due to NVS full conditions.
Avg Resp Time- Average response time in milliseconds.
Avg Xfer Size- Average transfer size in KB. Data Rate- Average transfer rate in KBps.
I/O Rate- Average number of I/O operations per second. Volume ID- Unique identifier of the volume in hex.
Volume Performance Data Collected via PDCU
Student Notebook
Non-seq Read I/Os - Number of normal read operations.
Non-seq Write I/Os - Number of normal write operations.
Seq Read I/Os - Number of sequential read operations.
Seq Write I/Os - Number of sequential write operations.
Non-seq Read Hits - Number of cache hits for normal read operations.
Non-seq Write Hits - Number of cache hits for normal write operations.
Seq Read Hits - Number of cache hits for sequential read operations.
Seq Write Hits - Number of cache hits for sequential write operations.
KBs Read - Number of KBs read.
KBs Written - Number of KBs written.
Accum Read Time - Total time spent reading in milliseconds.
Accum Write Time - Total time spent writing in milliseconds.
Non-seq Disk->Cache Ops- Number of disk to cache transfers for non-sequential I/O
operations.
Student Notebook
V3.1.0.1
Uempty
Figure 7-37. Volume Performance Data Collected SS481.0
Notes:
Seq Disk->Cache Ops - Number of disk to cache transfers for sequential I/O
operations.
Cache->Disk Ops - Number of cache to disk transfers for all I/O operations.
NVS Allocs - Number of NVS space allocations.
Non-seq DFW I/Os - Number of normal DASD Fast Write requests.
Seq DFW I/Os - Number of sequential DASD Fast Write requests.
NVS Delayed DFW I/Os - Number of DASD Fast Write requests delayed due to NVS
space constraints.
Cache Delayed I/Os - Number of I/O requests delayed due to cache space
constraints.
Rec Mode Read I/Os - Number of record mode read I/O requests.
Rec Mode Read Hits - Number of record mode cache hits.
CC/XRC Trks Read - Number of tracks read from the Concurrent Copy or XRC
Solidify.
CC/XRC Contam Writes - Number of contaminating writes for Concurrent Copy or XRC
operations.
Backend Data Xfer Time- Total time spent on lower interface I/O
activity.
Cache Bypass Write I/Os- Number of Bypass Cache requests.
Interval Length- Interval length truncated to the second.
Backend Accum Read Time- Total time spent reading from
physical arrays in milliseconds.
Backend KBs Written- Number of KBs written to physical
arrays.
ICL Read I/Os- Number of Inhibit Cache Loading requests. Backend Accum Write Time- Total time spent writing from
physical arrays in milliseconds.
Backend KBs Read- Number of KBs read from physical arrays. Backend Write Ops- Number of physical array write operations.
Backend Read Ops- Number of physical array read operations. Irreg Trk Acc Hits- Number of cache hits for irregular track
access requests.
Irreg Trk Acc- Number of irregular track access requests. CFW Write Hits- Number of cache hits for Cache Fast Write
write requests.
CFW Read Hits- Number of cache hits for Cache Fast Write read
requests.
CFW Write I/Os- Number of Cache Fast Write write requests
CFW Read I/Os- Number of Cache Fast Write read requests. Quick Write Prom- Number of quick write promote operations.
PPRC Trk Xfers- Number of full or partial tracks transferred to
the secondary device of a PPRC pair.
CC/XRC Contam Writes- Number of contaminating writes for
Concurrent Copy or XRC operations.
CC/XRC Trks Read- Number of tracks read from the Concurrent
Copy or XRC Sidefile.
Rec Mode Read Hits- Number of record mode cache hits.
Rec Mode Read I/Os- Number of record mode read I/O requests. Cache Delayed I/Os- Number of I/O requests delayed due to
cache space constraints.
Volume Performance Data Collected
Student Notebook
PPRC Trk Xfers - Number of full or partial tracks transferred to the secondary
device of a PPRC pair.
Quick Write Prom - Number of quick write promote operations.
CFW Read I/Os - Number of Cache Fast Write read requests.
CFW Write I/Os - Number of Cache Fast Write write requests.
CFW Read Hits - Number of cache hits for Cache Fast Write read requests.
CFW Write Hits - Number of cache hits for Cache Fast Write write requests.
Irreg Trk Acc - Number of irregular track access requests.
Irreg Trk Acc Hits - Number of cache hits for irregular track access requests.
Backend Read Ops - Number of physical array read operations.
Backend Write Ops - Number of physical array write operations.
Backend KBs Read - Number of KBs read from physical arrays.
Backend KBs Written - Number of KBs written to physical arrays.
Backend Accum Read Time- Total time spent reading from physical arrays in milliseconds.
Backend Accum Write Time - Total time spent writing from physical arrays in milliseconds.
ICL Read I/Os - Number of Inhibit Cache Loading requests.
Cache Bypass Write I/Os - Number of Bypass Cache requests.
Backend Data Xfer Time - Total time spent on lower interface I/O activity.
Student Notebook
V3.1.0.1
Uempty
Figure 7-38. Port Reports SS481.0
Notes:
The port report list the five most active ports on the subsystem in terms of I/O rate, transfer
rate, and response time.
The five ports with the highest total I/O rate (I/O operations per
second)
The five ports with the highest total transfer rate (MBs per sec)
The five ports with the highest average response time
(milliseconds per I/O operation)
Port Reports
Student Notebook
Figure 7-39. Rank Reports SS481.0
Notes:
The rank report lists the five most active ranks on the subsystem in terms of I/O rate,
transfer rate, and response time.
The five ranks with the highest
total I/O rate (I/O operations
per sec)
total transfer rate (MBs per
sec)
average response time
(millisecs per I/O op)
Rank Reports
0
0.5
1
1.5
2
2.5
01/14/20
05
01:26:24
01/14/20
05
01:40:48
01/14/20
05
01:55:12
01/14/20
05
02:09:36
01/14/20
05
02:24:00
01/14/20
05
02:38:24
01/14/20
05
02:52:48
Time
T
o
t
a
l

I
/
O

R
a
t
e
IBM.2107-7502301/R0
IBM.2107-7502301/R1
IBM.2107-7502301/R2
IBM.2107-7502301/R3
0
20
40
60
80
100
120
140
01/14/20
05
01:26:24
01/14/20
05
01:40:48
01/14/20
05
01:55:12
01/14/20
05
02:09:36
01/14/20
05
02:24:00
01/14/20
05
02:38:24
01/14/20
05
02:52:48
Time
T
o
t
a
l

D
a
t
a

R
a
t
e
IBM.2107-7502301/R0
IBM.2107-7502301/R1
IBM.2107-7502301/R2
IBM.2107-7502301/R3
0
10
20
30
40
50
60
70
80
90
01/14/20
05
01:26:24
01/14/20
05
01:40:48
01/14/20
05
01:55:12
01/14/20
05
02:09:36
01/14/20
05
02:24:00
01/14/20
05
02:38:24
01/14/20
05
02:52:48
Time
A
v
e
r
a
g
e

R
e
s
p
o
n
s
e

T
i
m
e
IBM.2107-7502301/R0
IBM.2107-7502301/R1
IBM.2107-7502301/R2
IBM.2107-7502301/R3
Student Notebook
V3.1.0.1
Uempty
Figure 7-40. Volume Reports SS481.0
Notes:
The volumes report looks at different I/O types such as reads and write, both sequential
and random, and cache hit ratios for the volumes. These can point out hot volumes and
could lead to volume or data movement to do tuning. However, with the I/O capability and
bandwidth displayed in earlier performance charts, tuning may not be necessary, at least
initially.
0
20
40
60
80
100
120
140
160
01/14/2
005
01:26:2
4
01/14/2
005
01:40:4
8
01/14/2
005
01:55:1
2
01/14/2
005
02:09:3
6
01/14/2
005
02:24:0
0
01/14/2
005
02:38:2
4
01/14/2
005
02:52:4
8
Time
N
o
r
m
a
l

R
e
a
d

I
/
O

R
a
t
e
IBM.2107-7502301/0000
IBM.2107-7502301/1014
IBM.2107-7502301/1016
IBM.2107-7502301/1015
IBM.2107-7502301/1013
0
10
20
30
40
50
60
70
80
01/14/2
005
01:26:2
4
01/14/2
005
01:40:4
8
01/14/2
005
01:55:1
2
01/14/2
005
02:09:3
6
01/14/2
005
02:24:0
0
01/14/2
005
02:38:2
4
01/14/2
005
02:52:4
8
Time
N
o
r
m
a
l

W
r
i
t
e

I
/
O

R
a
t
e
IBM.2107-7502301/1013
IBM.2107-7502301/101a
IBM.2107-7502301/1016
IBM.2107-7502301/1015
IBM.2107-7502301/1014
0
1000
2000
3000
4000
5000
6000
7000
8000
01/14/2
005
01:26:2
4
01/14/2
005
01:40:4
8
01/14/2
005
01:55:1
2
01/14/2
005
02:09:3
6
01/14/2
005
02:24:0
0
01/14/2
005
02:38:2
4
01/14/2
005
02:52:4
8
Time
N
V
S

D
e
l
a
y
e
d

D
F
W

I
/
O
s
IBM.2107-7502301/1014
IBM.2107-7502301/1015
IBM.2107-7502301/1016
IBM.2107-7502301/1013
IBM.2107-7502301/1018
Volume Reports
The five volumes with the highest normal
read I/O rate (I/O operations per second)
The five volumes with the highest normal
write I/O rate (I/O operations per second)
The five volumes with the highest sequential
read I/O rate (I/O operations per second)
The five volumes with the highest sequential
write I/O rate (I/O operations per second)
The five volumes with the lowest read cache
hit ratio
The five volumes with the lowest write cache
hit ratio
The five volumes with the highest
cache-to-disk transfers (number of track
transfers)
The five volumes with the highest
disk-to-cache transfers (number of track
transfers)
The five volumes with the highest NVS
delayed requests (number of track transfers)
Student Notebook
Figure 7-41. PDCU Documentation SS481.0
Notes:
The PDCU package comes with a readme file that documents the functions and how to use
the PDCU.
PDCU Documentation
PDCU comes with a README file which provides basic
documentation which provides basic installation, usage, and
statistics-gathered information.
Also discusses how to create customized reports
A sample MS Excel macro is available to illustrate one method of
performing analysis and graph generation with PDCU data.
Student Notebook
V3.1.0.1
Uempty
Figure 7-42. PDCU Summary SS481.0
Notes:
PDCU Summary
Availability Outlook: 3/2005
Provide performance data collection utility for DS8000 and DS6000
Include a CLI interface
Support all available DS8000 and DS6000 performance data
Volume, rank, IO port (extend pool not needed)
Support monitoring one DS8000 and DS6000
Support monitoring multiple DS8000 and DS6000 devices via multiple instances
of the utility
Support monitoring at least three fully configured DS8000 and DS6000 from
one server (assuming three instances of the tool are running)
Support for z/OS and open attached DS8000 and DS6000
Simple install and execution
Can be scheduled
The utility should be able to be invoked/scheduled by system services (that is,
Windows Scheduler, Linux CRON)
Data output is documented
Includes sample reports
Student Notebook
Checkpoint
1. T/F The PDCU is a performance data collection utility used to
collect raw data from a DS6000 or DS8000 system.
2. T/F The PDCU utility has a GUI and a Command Line Interface.
3. T/F The output of the PDCU data collection can be loaded into a
spreadsheet for processing and reporting graphs.
4. T/F The report generated by PDCU excel graphs can report on
volume usage and identify potential problem areas.
Student Notebook
V3.1.0.1
Uempty
Notes:
Having completed this unit, you should be able to understand:
The TotalStorage Productivity Center
TPC 2.3
Performance Data Collection Utility (PDCU)
Installation and use
Reports
Unit Summary
Student Notebook
Student Notebook
Copyright IBM Corp. 2005 Unit 8. DS Copy Services 8-1
V3.1.0.1
Uempty
Unit 8. DS Copy Services
The DS6000/DS8000 storage subsystem uses the Copy Services
functions currently implemented in the ESS subsystems. This unit
discusses the Copy Services function of FlashCopy, Metro Mirror,
Global Copy and Global Mirror and how these functions work. In
addition, the unit overviews the GUI and DSCLI interfaces to these
functions and discuses migration from the ESS Copy Services
environment to the DS Copy Services environment.
Discuss the IBM TotalStorage DS Copy Services functions
available for Open systems
Describe the concepts of Metro Mirror, Global Copy,
Discuss Global Copy versus Global Mirror
Describe the Remote Mirror Paths using FCP links
Review the user interfaces for IBM TotalStorage DS8000 Copy
Services:
DS8000 Copy Services GUI interface
DSCLI commands
References
Concepts
SC24-7623 IBM TotalStorage: DS8000 Users Guide
Guide
Guide
Student Notebook
Notes:
Unit Objectives
Describe the IBM DS8000 Copy Services
Describe the FlashCopy functions
Describe the Remote Mirror functions
Describe the DS8000 Storage Manager GUI Copy Services
Describe the IBM DS8000 CLI for Copy Services
Describe the migration from ESS to DS8000 Copy Services
Student Notebook
V3.1.0.1
Uempty 8.1 Advanced Copy Services Review
Student Notebook
Figure 8-2. Topic: Local Flash Copy SS481.0
Notes:
Topic: Local Flash Copy
Review of the Advanced Copy Services
Local Flash Copy
Remote Mirror and Copy
Advanced Copy Services for DS6000 and
DS8000
IBM TotalStorage DS CLI for Copy
Services
DS Storage Manager Copy Services GUI
Student Notebook
V3.1.0.1
Uempty
Figure 8-3. FlashCopy Implementation SS481.0
Notes:
There are three types of access to the volume. First, if a background copy is being done
and the data has been copied to the target, then any I/Os to that data on either the source
or target volume are handled as normal I/O to that volume. Second, if a read is to be done
to the target and the data has not been moved yet, then that block is accessed from the
source volume for that I/O. Third, if updates occur on either volume below the copy line,
then a Copy on Demand operation moves the block to be accessed to the target before any
updates can occur. If an application wants to update the target before the source data has
been copied to the target, the data is first read from the source, written to the target, then
updated by the application. The target volumes bitmap is updated to indicate that the copy
has been made.
Copy data command issued
Copy immediately available
Read and write to both source and
copy possible
Write
Read
When copy is complete,
relationship between
source and target ends
Time
Optional background copy
Source
Target
FlashCopy Implementation
Student Notebook
Figure 8-4. FlashCopy NOCOPY to COPY SS481.0
Notes:
If the Background COPY option is used, then this is all copied eventually, but tracks
needed for update immediately after the relationship has started may need to be copied on
demand to the target so the source tracks can be changed.
NOPCOPY is used where there is no long-term requirement to access the volume, say for
a backup to tape.
COPY is used when there is a long-term need to access the target volume, such as testing
or development.
Source Target
Time
Write Read
BACKGROUND COPY
FlashCopy command issued
with NOCOPY
Change BACKGROUND from
NOCOPY to COPY
relationship between source
and target ends
FlashCopy NOCOPY to COPY
Student Notebook
V3.1.0.1
Uempty
Figure 8-5. Persistent Flash Copy SS481.0
Notes:
The FlashCopy relationship normally ends when the background copy is complete. This
destroys the bit maps being used to track changes. If the relationship needs to be
maintained or if the user wants to be able to verify that a FlashCopy relationship exists,
then the persistent FlashCopy is used to keep the relationship active even though the data
has been moved.
Source Target
Time
FlashCopy command
issued with COPY and
PERSISTENT
relationship between source
and target persists
Explicitly withdraw the
relationship
Source Target
Source Target
Persistent FlashCopy
Student Notebook
Figure 8-6. Multiple Relationship FlashCopy SS481.0In
Notes:
A target track cannot have more than one source track. For example, if full volume
FlashCopy were performed, a data set FlashCopy to that volume would not be possible
until the full volume relationship is withdrawn. But, two data set FlashCopy operations can
be performed to the same target volume as long as the target track (extent) is not already
in a relationship. The FlashCopy succeeds since the tracks for the target data sets are on
different extents on the target volume.
One-to-many
(multitarget)
A volume can participate in multiple FlashCopy relationships
One source to many targets
A source can have up to 12 targets
A target can only have one source
A target cannot be a source at the same time
A volume, LUN, or data set can be only a source or target at any given time
However, data set source and target can reside within a single volume
Increased flexibility
Improved capacity management and utilization
Multiple Relationship FlashCopy
Student Notebook
V3.1.0.1
Uempty
Figure 8-7. Incremental FlashCopy SS481.0
Notes:
Source A to target B - this has to be established with the BACKGROUND(COPY) option
and persistent relationship.
A and B are both updated - independent of each of the volumes, updates are written to
volume A and to volume B indicated through a circle and a rectangle within the extent.
Resynchronize B with A - When resynchronizing B with A the changed rectangle will be
overridden by its original content and the changes made to A indicated through the circle is
also copied to B.
It is also possible to reverse this incremental refresh and resynchronize A with B instead of
the previous resynchronize step.
Establish Copy A
to B
Both A and B get
updated
Resynchronize: B
becomes an exact copy
of newest updates in A
again
source
A
Reverse restore: A
becomes an exact
copy of newest
updates in B
target
B
or
Change recording tracks changes made to
source and target volumes after establish of
FlashCopy relationship
Use in conjunction with background copy
and persistent relationship options
Supported only at full volume/ LUN level
There can only be one incremental
relation per volume but can coexist with
other non-incremental relationships
During refresh:
Only changed data is copied from the
source to the target
Source and target volumes can be
reversed
Source volume (previously the target)
refreshes the target volume (previously
the source) with only changed data
Background copy must complete first
Increased flexibility
Faster completion time for physical copy
Incremental FlashCopy
Student Notebook
Figure 8-8. FlashCopy Consistency Group Support SS481.0
Notes:
The FlashCopy function has added consistency groups. This means that you can freeze
volumes in an LSS and perform FlashCopies on them, and then release the volumes with a
consistency group-formed function. During the freeze, I/Os are queued so that the volumes
can quiesce and be at the same point in time. The FlashCopy is issued against all the
volumes that need to be consistent in time, and then I/O can be restarted. This means that
applications do not have to be stopped or quiesced if you are using a freeze consistency
group approach. Once the FlashCopies are established you need to issue the Consistency
Group Created task immediately to restart the I/O processing. Failure to do this causes the
application to be hung and eventually fail with timeouts.
FlashCopy S1 to T1
Writes cannot proceed on S1
Any writes occurring on S2-S4 are not
dependent writes
FlashCopy S2 to T2
Writes cannot proceed on S1 or S2
Any writes occurring on S3-S4 are not
dependent writes
FlashCopy S3 to T3 and S4 to T4
T1-T4 contain a consistent copy
Issue Consistency Group Created
Writes may proceed to S1-S4.
T4
T3
T2
T1
S4
S3
S2
S1
Hold off initiation / completion
of write I/O to the source
volumes until FlashCopy
establish is completed
Select source and target
volumes with freeze option
Create Consistency Group
Created tasks to allow
resumption of I/O
One per LSS
Enables creation of a
consistent point-in-time copy
across multiple volumes with
minimum host impact
Target of each source volume
are within one ESS but source
volumes within a consistency
group can span ESSs
Source volumes can span
multiple CS-Web domains if
using CLI scripts
FlashCopy Consistency Group Support
Student Notebook
V3.1.0.1
Uempty 8.2 Remote Mirror and Copy
Student Notebook
Figure 8-9. Topic: Remote Mirror and Copy SS481.0
Notes:
Topic: Remote Mirror and Copy
Local Flash Copy
DS8000
Services
Student Notebook
V3.1.0.1
Uempty
Figure 8-10. Disk Storage Mirroring SS481.0
Notes:
Metro Mirror and Global Copy are volume copy functions that allow a remote storage
device, such as a DS8000, DS6000 or ESS connected to a local DS8000 to mirror volume
across FCP links to a remote data center. The mirrored volumes are kept in continuous
update mode, so every primary volume I/O is written to the local and remote volume. An
asynchronous mode called Global Copy is used for environment where the remote site is
too far away to use the Metro Mirror, which is limited to approximately 300 km.
To use Global Copy, a user must have a way of creating a consistent copy using a
procedure which stops updates while synchronizing the primary and secondary volumes.
A third function Global Mirror is the newest function and replaces most global copy or
cascaded functions.
Leading solution : performance, and
scalabilit for disk mirroring
Disk Mirroring solutions for ESS and DS
Metro Mirror (Synchronous PPRC)
Global Mirror (Asynchronous PPRC)
Metro Mirror/Global Copy (Asynchronous
Cascading PPRC)
Global Copy (PPRC Extended Distance)
Primary Site
(PPRC primary)
Metro
Mirror
Secondary Site
(PPRC secondary)
Global Mirror
Global Copy
FlashCopy
Global Copy
Primary Site
(PPRC primary)
Metro
Mirror
Intermediate Site
(PPRC
secondary/primary)
FlashCopy
Remote Site
(with 'safety copy')
Disk Storage Mirroring
Student Notebook
Figure 8-11. Metro Mirror (Synchronous PPRC) SS481.0
Notes:
The metro mirror or synchronous PPRC is a function designed for DR. It has distance
limitations and adds performance delays into applications using the volumes that use this
function, but it provides a remote copy that is synchronized I/O for I/O, so if you have a
problem at the production site, you can suspend and switch to the secondary volumes and
they are ready to go with no forward recovery required.
Server
DS
primary
DS
secondary
1 4
3
2
PPRC
Distant synchronous copy
Updates secured both on primary and secondary
before host receives completion of the IO
Volume level
Up to 103 km
Invoked by
GUI Copy services
CLI (open systems)
TSO commands
Automated by
Scripts (open)
GDPS or other (zOS)
Support of Consistency Groups
Write to primary volume.
The primary initiates an I/O to the secondary
to transfer the data.
Secondary indicates to the primary that the
write is complete.
Primary acknowledges to the application
system that the write is complete.
Metro Mirror (Synchronous PPRC)
Student Notebook
V3.1.0.1
Uempty
Figure 8-12. Global Copy (PPRC XD) SS481.0
Notes:
The global copy is just a long distance copy. There is no guarantee of consistency so its no
good for DR, but if the data is idle or static it works fine to copy it to a remote location. If you
are copying active data, then you have a problem. To get any kind of volume time
consistency, you must synchronize the volumes and get a copy at the point they are
synchronized. You did not have to do that with metro mirror because they were always
synchronized.
Server
Server
DS
primary
ESS
secondary
1 2
3
PPRC
XD
Updated tracks are sent periodically
Write to primary volume.
Primary acknowledges to the application
system that the write is complete.
At some later time:
The primary initiates an I/O to the secondary to
transfer the data.
Secondary indicates to the primary that the
write is complete.
Primary resets indication of modified track.
Global Copy (PPRC XD)
Distant asynchronous copy
Host receives completion when
update is secured on the primary
Modified tracks are sent to the
secondary asynchronously
Less bandwidth required
Continental distances
No or little impact on the primary
response time
Invoked by
GUI Copy Server
CLI (open systems)
TSO commands
Automated by
Scripts (open)
GDPS or other (z/OS)
Can be switched to synchronous
PPRC
Student Notebook
Figure 8-13. FlashCopy on Remote Mirror and Copy Primary SS481.0
Notes:
Here is another approach. Take a FlashCopy of your production volumes while quiesced
and create your consistent copy at the production site, now Global Copy the static target
volumes to the remote site.
PPRC
Primary Volume
PPRC
Secondary Volume
PPRC relation
FlashCopy to
PPRC Primary
Volume
FlashCopy
Source Volume
FlashCopy
Target Volume
FlashCopy on Remote Mirror
and Copy Primary
Student Notebook
V3.1.0.1
Uempty
Figure 8-14. IBM TotalStorage Metro Mirror / Global Copy SS481.0
Notes:
This is another flavor which gives you a local synchronous copy and a remote XD copy. It
might be easier to sync the remote mirror if all you have to suspend is the link to the
production secondary. At least then you dont have to stop the production applications.
Three sites cascading
A secondary can be a primary of another PPRC
relationship
Automated via GDPS
Enables a consistent copy at long distance
Only one copy on the intermediate site
Server
DS
primary
DS
secondary
primary
1 4
3
2
PPRC
DS
secondary
PPRC
XD
Synchronous to XD (typical usage)
Synchronous to Synchronous
XD to XD
NOT XD to Synchronous
IBM TotalStorage Metro Mirror / Global Copy
Student Notebook
Figure 8-15. PPRC Global Mirror SS481.0
Notes:
This is the newest function in the Copy Services Suite. It uses the global copy and
FlashCopy functions and adds session management to create consistency groups in
cycles, and send them to the remote secondary. Each time the remote secondary is
synchronized, a FlashCopy is taken to capture the consistent volumes. The cycle is very
quick, so every 3-5 seconds you get a consistent copy. Now if there is a problem, you take
the last good copy and recover. Its only 3 or 4 seconds old so not much forward recovery
to do, but there is some, so you cant just assume it good and go with it. You may lose three
or four transactions or more, and depending on your business, those could be important
transactions, so apply what logs you have and get those updates applied and youre good
to go.
PPRC-XD OVER
LONG DISTANCE
CHAN EXT
Incremental
FlashCopy
0
1
0
1
0
0
0
1
0
0
0
0
1
0
REMOTE
APPLICATION
HOSTS
0
1
0
1
0
0
0
1
0
0
0
0
1
0
Change
Recording
bitmap
Out of
Sync
bitmap
PPRC 'A'
PRIMARY
CHAN EXT
PRIMARY
APPLICATION
HOSTS
PPRC B
Secondary and FC
Source
FC C
Target
Local Site Remote Site
PPRC Extended Distance (PPRC-XD) from local to remote site
Automatic periodic consistent copies created at remote site
Volume A uses change recording bitmap while consistency group is created
All data sent to remote and inband FlashCopy at remote creates consistent data
on volume C
Designed to adjusts to peak workloads without impacting primary application
PPRC Global Mirror
Student Notebook
V3.1.0.1
Uempty
Figure 8-16. PPRC Global Mirror SS481.0
Notes:
The global mirror function uses the existing global copy and FlashCopy to set up a
long-distance copy, and a means of capturing that copy periodically to a tertiary volume.
Now all that is needed is a way of creating consistency, and you have a mechanism to
create a long-distance mirroring function. The global mirror function adds a session
manager that allows groups of LSSs to create consistency groups using the same I/O
queue full or long busy, and then release groups of consistency blocks one at a time to the
secondary volumes. Once there, a fast in-band FlashCopy is issued, and the consistent
volumes are captured to the tertiary volumes. The cycle of consistency creation is done
every 3-5 seconds or as specified by the customer.
Global Mirror is Host independent (z/OS, UNIX, ...)
So far, up to eight ESSs in the same Consistency Group
No specific software required
Based on PPRC-XD and FlashCopy IBM technologies
Gives users the guarantee that remote images are consistent
Cycle is 3 to 5 seconds for Data RPO (Recovery Point Objective)
Coordination Time around 1 ms every 3 to 5 seconds
Very low impact on write response times at Primary Site
High scalability for Data Image Copy at Remote Site (swap of FlashCopy
targets)
K7
Primary
Volume
Vol.
FC
Image
Vol.
XD
A B C D
Sequence of Flashcopies from B :
C C C C D C C C C C C C C C
Swap of
"changed
bitmap" every
3 5 seconds
PPRC Global Mirror
Student Notebook
Figure 8-17. PPRC-XD Normal Operations SS481.0
Notes:
A primary LUN or hdisk is copied to a remote DS at another site. The volumes are non-
synchronous and track a sent to the remote DS subsystems as applications process the
primary disk. Tracks are not sent in order of I/Os, and they are not time stamped. A bit map
is used to determine if a track or block has changed, and if so, the changed block is sent to
the secondary subsystem.
Local Site
(Primary)
Remote Site
(Secondary)
Channel
Extender Channel
Extender
PPRC-XD
Long Distance
Remote PPRC Pair
1. We are in normal PPRC-XD mode
2. Writes are being sent to the remote
site via the normal PPRC-XD
methods
Host I/O
I/O to be sent to Secondary
OOS
Out of Sync
Bit Map
Phase 0:
PPRC XD mode : write updates are
continuously sent to
the secondary site volumes
The secondary volumes are not in a
consistent state
PPRC-XD Normal Operations
Student Notebook
V3.1.0.1
Uempty
Figure 8-18. PPRC Async Increment Pending SS481.0
Notes:
The PPRC-XD uses a change recording bitmap or CR. For global mirror the CR is updated
and the I/O is paused to allow the master LSS to coordinate the consistency group across
all subordinate LSSs. A timer is set and is released when the master has created the
consistency group.
Local Site
(Primary )
Remote Site
(Secondary )
Channel
Extender Channel
Extender
PPRC XD
Long Distance
Remote PPRC Pair
State: Increment Pending
Start Increment Command
3. State: Increment Pending
2. Pause incoming I/O and create CR Bitmaps.
4. Set Timer and wait for Run command
1. Primary accepts Start Increment command
CR
Change
Recording
Bit Map
I/O to be sent to Secondary
Phase 1:
When Increment Pending begins, all writes to
the source volume are paused for a brief period
of time (1 to 3 ms).
During this time the master ESS coordinates the
Consistency Group n across the subordinates.
OOS
Out of Sync
Bit Map
PPRC Async Increment Pending
Student Notebook
Figure 8-19. PPRC Async Run Consistency Group SS481.0
Notes:
The primary LSS or master LSS accepts the Run command and the CR bitmap is moved to
the OOS bitmap. The state of the operation changes to Consistency Group in Progress.
The OOS bitmap is referenced and all blocks are drained to the secondary volumes. New
writes are allowed to proceed and update the CR bitmap, and are part of the next
consistency group. These are logged into the CR bitmap, and held until the previous OOS
bitmap is drained to the secondary.
State:
Consistency Group in Progress
Local Site
(Primary)
Remote Site
(Secondary)
Channel
Extender Channel
Extender
PPRC XD
Long Distance
Remote PPRC Pair
Run Command
2. State: Consistency Group in Progress
3. Host I/O is resumed. Changes only logged
in CR Bitmaps.
4. OOS continues to drain to the remote site
via the PPRC XD link.
1. Primary accepts Run command
Host I/O
5. Wait for Increment Complete (Maximum
Increment Timer)
New Host I/O
Phase 2:
Once the coordination of the consistency group is
complete, host writes resume and all data (NOT full
tracks) in the consistency group is transmitted to
the secondary volumes (draining process).
New write updates are part of the next n+1
consistency group, and are logged in a new
Change Recording Bit map.
New write updates are not sent to secondary
volumes as long as modified tracks before the
Increment Pending (Consistency Group n) are
currently drained.
CR
Change
Recording
Bit Map
OOS
Out of Sync
Bit Map
PPRC Async Run Consistency Group
Student Notebook
V3.1.0.1
Uempty
Figure 8-20. Back to Normal SS481.0
Notes:
The external source waits for the OOS to drain the data to the remote site, and then issues
in-band FlashCopy commands with
NOCOPY,INCR,CHGREC,PERSISTENT,INHIBITWRT. The Primary receives an Increment
Complete message when the FlashCopies are done. The Next Increment is set and the CR
bit map is moved to the Out-of-Sync bitmap or OOS and the next drain is started to the
secondary volumes. Writes are released, the CR is updated and waits for the next Run
command to begin the cycle again.
Local Site
(Primary)
Remote Site
(Secondary)
Channel
Extender Channel
Extender
PPRC XD
Long Distance
Remote PPRC Pair
Increment Complete
2. External source starts FlashCopy commands on
Remote site with no BG copy.
3. Primary receives Increment Complete when
FlashCopy commands are done.
4. The CR and OOS bitmaps are merged
1. External source queries and waits for OOS to finish
draining to remote site
State: Normal
Host I/O
5. State: Normal (PPRC-XD Mode, Host I/O
is buffered in the OOS again)
New Host I/O
Phase 3:
When the drain process is complete, the
secondary volumes are automatically copied
via the IBM FlashCopy function in order to
form a Consistency Group.
Master receives Increment Complete from
each secondary ESS when FlashCopies are
done. At this point we have returned to the
PPRC-XD state and the cycle repeats
indefinitely.
OOS
Out of Sync
Bit Map
CR
Change
Recording
Bit Map
Back to Normal
Student Notebook
Student Notebook
V3.1.0.1
Uempty 8.3 Advanced Copy Services
Student Notebook
Figure 8-21. Topic: Advanced Copy Services SS481.0
Notes:
Topic: Advanced Copy Services
Local Flash Copy
DS8000
Services
Student Notebook
V3.1.0.1
Uempty
Figure 8-22. Advanced Copy Services SS481.0
Notes:
Advanced Copy Services functions available on the ESS 800
are all available on the DS8000 (except for IBM TotalStorage
Metro/Global Copy) and on the DS6000 (except for IBM
TotalStorage Metro/Global Copy and IBM TotalStorage z/OS
Global Mirror (XRC))
IBM TotalStorage FlashCopy
GUI does not support Consistency Groups
PPRC
Must use FCP PPRC links
GUI does not support FREEZE/RUN
Functions invoked via DS CLI or for a one time event the GUI
Tasks can not be saved using the new GUI
Advanced Copy Services
Student Notebook
Figure 8-23. IBM TotalStorage Metro/Global Copy SS481.0
Notes:
The Copy Services that are available for the DS8000 are FlashCopy and Metro Mirror.
There is intention to support Global Copy and Global Mirror, but those are not available yet
(5/10/05).
2003 IBM Corporation
DS8000 DS6000 Technical Overview Workshop Unit 08 Copy Services | 2005 IBM Corporation
Original support (not available on the DS8000 or DS6000)
Concept
PPRC secondary volume serves as PPRC primary volume for
another PPRC relationship
Same secondary volume serves as both target and source
Intended benefit
Long distance remote copy solution for zSeries and open
systems data with the performance impact of only a short
distance Metro Mirror
Remote Pairs
Host I/O
Secondary Primary Secondary
Primary
Local Pairs
Intermediate
Site
Remote
Site
Local
Site
Global Copy
IBM TotalStorage Metro/Global Copy
Student Notebook
V3.1.0.1
Uempty
Figure 8-24. Statement of Direction: Metro/Global Copy Enhancement SS481.0
Notes:
The cascaded PPRC function is not supported for the DS8000, but in the ESS, it allows a
three-volume cascade to be set up, where the second volume is a secondary and a primary
at the same time.
Enhancement (to be available on DS8000 and DS6000)
Allow intermediate site to use Global Mirror to the remote site
Provides data consistency in the event both the local and intermediate
sites are lost in a disaster
Remote Pairs
Host I/O
Secondary Primary Secondary
Primary
Local Pairs
Intermediate
Site
Remote
Site
Local
Site
Global Mirror
FlashCopy
target
FC
Statement of Direction:
Metro/Global Copy Enhancement
Student Notebook
Figure 8-25. DS8000 LPAR and Copy Services SS481.0
Notes:
The FlashCopy function can only operate to volumes on extent pools that belong to the
LPAR. Volumes on the other LPAR are not available for FlashCopy, however, the PPRC
function can be used to mirror to a volume in the other LPAR.
LPAR 1 LPAR 2
PPRC
Primary
PPRC
Primary
PPRC
Secondary
PPRC
Secondary
FlashCopy
Source
FlashCopy
Source
FlashCopy
Target
FlashCopy
Target
X
FlashCopy within an LPAR
PPRC within an LPAR or across LPARs
DS8000 LPAR and Copy Services
Student Notebook
V3.1.0.1
Uempty
Figure 8-26. License for FlashCopy (1 of 2) SS481.0
Notes:
The scope of the license describes the intended use for the function. If All storage is
specified, then both CKD and FB volumes can be FlashCopied, but if one or the other is
specified, then only LSSs in that mode can be used and only up to that amount.
License for FlashCopy (1 of 2)
user data
plus FC
data up to
20 TB FB
DS8000 with 45 TB disk capacity in total, 45 TB FlashCopy
authorization, 45 TB of OEL Licensed function and license scope
of ALL
user data
plus FC
data up to
25 TB CKD
User FlashCopies
up to 25 TB of CKD
20 TB (FB) +
25 TB (CKD) +
--------
45 TB total capacity
--------
I want to
FlashCopy 10 TB
of FB and 12 TB
of CKD.
Important - If user changes license scope
from ALL to FB or CKD an IML is required
User FlashCopies
up to 20 TB of FB

User has 20 TB of FB data and has 25 TB of CKD data
allocated. The user has to purchase a Point-in-Time
function equal to the total of both the FB and CKD
capacity, that is 20 TB (FB) + 25 TB (CKD) equals
45 TB.
solution
FC - FlashCopy
Student Notebook
Figure 8-27. License for FlashCopy (2 of 2) SS481.0
Notes:
In the example above, if the FlashCopy license is bought only for CKD storage, then no FB
FlashCopies will be allowed and then only up to 25 TB of storage.
License for FlashCopy (2 of 2)
20 TB
FB
DS8000 with 45 TB disk capacity in total,
25 TB of CKD FlashCopy authorization with
license scope of CKD,
45 TB of OEL Licensed function
25 TB
CKD
User cannot FlashCopy
any FB
User authorize to
FlashCopy
up to 25 TB
20 TB (FB) +
25 TB (CKD) +
--------
45 TB total capacity
--------
Student Notebook
V3.1.0.1
Uempty
Figure 8-28. Licence for Remote Mirror Copy SS481.0
Notes:
The remote mirror can be licensed in much the same way, either for all storage or for just
FB or CKD storage.
License for Remote Mirror Copy
Primary DS8000 with 45 TB disk capacity in total, Secondary
DS8000 with 45 TB disk capacity, 45 TB Remote Mirror Copy
authorization for primary DS8000 and 45 TB Remote Mirror Copy
for secondary DS8000, 45 TB of OEL Licensed function for primary
DS8000 and 45 TB of OEL Licensed function for secondary
DS8000. The license scope may be FB and CKD or ALL
20 TB FB
user data
25 TB CKD
user data
20 TB FB
user data
25 TB CKD
user data
Metro Mirror
Primary DS8000 Secondary DS8000
Student Notebook
Student Notebook
V3.1.0.1
Uempty 8.4 DSCLI for Copy Services
Student Notebook
Figure 8-29. Topic: DS CLI for Copy Services SS481.0
Notes:
Topic: DS CLI for Copy Services
Local Flash Copy
DS8000
Services
Student Notebook
V3.1.0.1
Uempty
Figure 8-30. Whats New? SS481.0
Notes:
Probably the biggest change to Copy Services from the ESS to the DS8000 is the use of
the DSCLI. In the ESS, all functions had to be implemented using the ESS Specialist Copy
Services GUI, and saving those functions as tasks which could be automated using
reExecuteTask.sh.
Now in the DS6000 and DS8000 the only way to automate Copy Services is using the
DSCLI. The GUI can no longer be used create tasks, so although it can be used to create a
FlashCopy or a Remote Copy relationships, it has little use for automation.
The new DS CLI replaces the CS CLI and ESS CLI
Provides new functions to dynamically create and manage
FlashCopy and PPRC relationships without any use of a GUI
Allows a PPRC relationship between 2105 and the DS8000 and
DS6000
Enables dynamic FlashCopy and PPRC relationships on ESS
800 storage servers
Prior to DS CLI it was required to create a task using the GUI
interface and then saving it
DS CLI commands can be saved as scripts which significantly
reduces the time to create, edit and verify their content
Uses a consistent syntax with other IBM TotalStorage products
now and in the future
All of the function available to the GUI is also available via the
DS CLI
Whats New?
Student Notebook
Figure 8-31. ESS Copy Services Command Flow with CS CLI SS481.0
Notes:
The ESSCLI is installed on the host system and communicates directly with the ESS
cluster servers over the IP network. The ESSCLI has a network component that
communicates to a CS client interface and the Copy Services Server in one of two defined
Copy Services Servers in a CS Server Group.
Open systems
host
Network interface
ESS CLI software ESS CS CLI software
CLI script
Cluster 1
CS Server A
CS Client
Cluster 2
ESS 800
CS Client
CS Server B
ESS Copy Services
Command Flow with CS CLI
Student Notebook
V3.1.0.1
Uempty
Figure 8-32. DS8000 Copy Services Components SS481.0
Notes:
The DSCLI is also installed on a customer host system along with other software such as
the DS Storage Manager and the DS API, and uses the network interface client to
communicate with the network interface server in the HMC or external S-HMC. These
consoles are connected to the DS8000 processor complex via internal Ethernet switches
located in the DS8000 base frame.
DS8000 Copy Services Components
Customer
Network
DS8000
Processor
Complex 0
DS Storage
Manager
DS CLI
DS API
S-HMC 1
(internal)
(S-HMC 2)
(external)
Ethernet
Switch 2
Ethernet
Switch 1
Processor
Complex 1
Student Notebook
Figure 8-33. DS8000 CLI Copy Services Command Flow SS481.0
Notes:
The DSCLI can communicate with both the DS8000 or the ESS using the network interface
which is basically the same component in both systems. A portion of the DSCLI commands
and all of the Copy Services commands can be issued to an ESS running 2.4.0.x code to
either of the two Copy Services Servers or to the DS8000 through the HMC network
interface server.
Open systems
host
Network interface
CLI script
Cluster 1
CS Server A
CS Client
Cluster 2
ESS 800
CS Client
CS Server B
Server 0 Server 1
DS8000
Storage HMC
CLI
interpreter
Dual
internal
network
interfaces
External
network
interface
DS8000 CLI Copy Services Command Flow
Student Notebook
V3.1.0.1
Uempty
Figure 8-34. DS6000 CLI Copy Services Command Flow SS481.0
Notes:
The DSCLI can communicate with both the DS6000 through the SMC and its network
interface server. The network interface can then communicate commands directly to the
DS6000 command line interface for execution.
Open systems
host
Network interface
CLI script
Controller 1 Controller 2
DS6000
DS Storage
Management PC
CLI
interpreter
Network interface
DS6000 CLI Copy Services Command Flow
Student Notebook
Figure 8-35. CLI Copy Services Coexistence for ESS and DS SS481.0
Notes:
Since both the ESSCLI and the DSCLI can be loaded and run at the same time on a host
system, you can still use the existing task and scripts for the ESS, and at the same time
issue DSCLI commands and script to the DS6000 or DS8000 via the HMC.
Open systems
host
Network interface
ESS CLI software ESS CLI software
Cluster 1
Infoserver
Cluster 2
ESS 800
Infoserver
Server 0 Server 1
DS8000
DS CLI software
DS8000 tasks ESS 800 tasks
Open systems
host
Network interface
ESS CLI software ESS CLI software
Cluster 1
Infoserver
Cluster 2
ESS 800
Infoserver
Server 0 Server 1
DS8000
DS CLI software
DS8000 tasks ESS 800 tasks
Storage HMC
CLI
interpreter
Dual
internal
network
interfaces
External
network
interface
CLI Copy Services
Coexistence for ESS and DS
Student Notebook
V3.1.0.1
Uempty
Figure 8-36. DS CLI Copy Services Commands SS481.0
Notes:
The DSCLI can be used to invoke all of the PPRC and FlashCopy functions.
DS CLI can be used to invoke:
FlashCopy
PPRC
IBM TotalStorage Metro Mirror
Synchronous PPRC
IBM TotalStorage Global Copy
PPRC-XD
IBM TotalStorage Global Mirror
Asynchronous PPRC
DS CLI Copy Services Commands
Student Notebook
Figure 8-37. DS CLI FlashCopy SS481.0
Notes:
The mkflash command is the basic FlashCopy function. You can start FlashCopies or stop
them with rmflash and list current relationships with lsflash. The chflash allows changing
the options on an existing relationship.
mkflash
Establish FlashCopy pairs
-wait (respond when background copy complete)
-restore
lsflash
List FlashCopy relationships with status information
activecp filter or actcpy status indicates background copy active
Outsynctrks status reports out of sync tracks
chflash
Modify FlashCopy relationship
-Refreshtgt (starts background copy, withdraws at end)
rmflash
Withdraw FlashCopy relationship
-Refreshtgt (starts background copy, withdraws at end)
DS CLI FlashCopy
Student Notebook
V3.1.0.1
Uempty
Figure 8-38. DS CLI PPRC - Paths SS481.0
Notes:
The PPRC function can also be invoked using the DSCLI. The PPRC function requires
paths be established to the secondary LSS from the primary LSS. These path commands
control that function.
lsavailpprcport
List FCP ports available for PPRC path definition
Port id (Ixxxx) identifies enclosure, adapter, port
mkpprcpath
Establish PPRC path
chpprcpath
Modify PPRC path
freezeconsistgrp resetconsistgrp
lspprcpath
List PPRC paths with status
rmpprcpath
Delete PPRC path
DS CLI PPRC - Paths
Student Notebook
Figure 8-39. DS CLI PPRC Global Mirror SS481.0
Notes:
The mksession command defines a global mirror session and can be used to add volumes
to it. It also, chsession can be used to add more volumes at a later time. The mkasyncpprc,
stpasynpprc, showasyncpprc or chasyncpprc start, stop, change, suspend a defined global
mirror session.
LSS/LCU session (consistency group)
mksession (define, open and add volumes)
chsession (add/remove vols)
rmsession (close session)
Async process session
mkasyncpprc (start or resume async process)
showasyncpprc (display async status)
chasyncpprc (pause async process)
stopasyncpprc (terminate async process)
DS CLI PPRC - Global Mirror
Student Notebook
V3.1.0.1
Uempty
Figure 8-40. DS CLI PPRC - Pairs SS481.0
Notes:
The mkpprc, rmpprc, lspprc and chpprc can start and stop or change PPRC relationships,
such as metro mirror or global copy. These commands must also be used to set up the
basic PPRC-XD functions used for the global mirror sessions.
mkpprc
Establish/re-establish PPRC pair
-wait (respond when full duplex)
lspprc
List PPRC relationships and status (for example, copy pending,
full duplex, suspended)
chpprc
Modify PPRC relationship
-type sync or XD
-resync (failback)
-reversecp (failover)
-wait (respond when full duplex)
rmpprc
Suspend or terminate PPRC pair
type suspend or break
DS CLI PPRC - Pairs
Student Notebook
Figure 8-41. DS CLI Clearvol SS481.0
Notes:
The clearvol is a new command that is useful for clearing any existing relationships from a
volume.
clearvol command
The clearvol command clears Copy Services relationships for a
base logical volume
PPRC primary/secondary relationships
FlashCopy source/target relationships
DS CLI Clearvol
Student Notebook
V3.1.0.1
Uempty
Figure 8-42. DS CLI PPRC SS481.0
Notes:
The CLI Migration is a task that is performed to move ESSCLI tasks to the DSCLI scripts.
The process of migrating to a DS8000 for Copy Services from an ESS that is heavily
involved in Copy Services PPRC or FlashCopy or both requires that the tasks saved in the
ESS Specialist CS task list be translated and converted to DSCLI command strings. These
DSCLI commands can then be placed into files and saved as DSCLI scripts which can be
run in much the same way the ESS tasks were run from shell scripts to automate the Copy
Services functions.
DS8000/DS6000 can have PPRC relationships with ESS 800
Invoked with DS CLI
ESS 800 must be at LIC 2.4.x or higher
ESS 800 Copy Services cannot create tasks that include
DS8000/DS6000 boxes
DS CLI can be used for ESS 800 copy services but not ESS 800
configuration
Removes the need to define tasks on the ESS!
Use one of the Copy Services Servers (A or B) IP addresses
instead of the management console address as you would
for the DS8000/DS6000
PPRC source has to be in the same Copy Services Domain as the
server but the target does not need to be within the same domain
ESS where you wish to perform FlashCopy must be a client of the
server
DS CLI PPRC
Student Notebook
Student Notebook
V3.1.0.1
Uempty 8.5 DS Storage Manager for Copy Services
Student Notebook
Figure 8-43. Topic: DS Storage Manager Copy Services GUI SS481.0
Notes:
Topic: DS Storage Manager Copy Services GUI
Local Flash Copy
DS8000
Services
Student Notebook
V3.1.0.1
Uempty
Figure 8-44. DS Storage Manager Copy Services GUI SS481.0
Notes:
The GUI real-time has a Copy Services interface.
Student Notebook
Figure 8-45. GUI Create FlashCopy Pairs SS481.0
Notes:
The GUI is limited it its scope of operation. It may be a good testing tool, but little more.
Define relationship types
Single source/single target
Single source/multiple targets
Select source volumes
Select target volumes
GUI Create FlashCopy Pairs
Student Notebook
V3.1.0.1
Uempty
Figure 8-46. GUI FlashCopy SS481.0
Notes:
The FlashCopy GUI allows the user to select a single source and single target and
establish a FlashCopy relationship.
GUI FlashCopy
Student Notebook
Figure 8-47. GUI Select FlashCopy Options (1 of 2) SS481.0
Notes:
The options of FlashCopy are available except the consistency group options.
Common options
Persistent
Initiate background copy
Enable change recording
Permit if target is online
Establish target on existing PPRC source
Advanced options
Inhibit writes to source
Inhibit writes to target
Allow target to be restored to pre-FlashCopy state (revertible)
Sequence number
GUI Select FlashCopy Options (1 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 8-48. GUI Select FlashCopy Options (2 of 2) SS481.0
Notes:
These options can be selected after the initial options.
Options available after selecting a common or advanced option
Refresh target volumes (incremental)
Displayed when objects have persistent and change recording
Reverse relationship (incremental)
Displayed when objects have persistent and change recording
Commit changes
Displayed when objects had the target to be restored to
pre-FlashCopy state selected
Discard Changes
Displayed when objects had the target to be restored to
pre-FlashCopy state selected
GUI Select FlashCopy Options (2 of 2)
Student Notebook
Figure 8-49. Paths SS481.0
Notes:
The GUI displays the result in a list of FlashCopy relationships.
2003 IBM Corporation
Paths
Student Notebook
V3.1.0.1
Uempty
Figure 8-50. GUI LSS Copy Options SS481.0
Notes:
The GUI allows us to set up XRC timeouts and consistency groups.
Concurrent copy timeout
z/OS Global Mirror (XRC) timeout
Critical mode enabled
Consistency group timeout enabled
When true, a primary logical device on this logical subsystem in
an LSS consistency group becomes long busy after reporting an
error condition that causes metro mirror suspension until either a
consistency group created operation is performed or until the
extended long busy timeout has elapsed.
When false, a logical device on this logical subsystem does not
become long busy after reporting an error that causes a metro
mirror suspension.
Consistency group timeout
Default is 120 seconds
GUI LSS Copy Options
Student Notebook
Figure 8-51. Metro Mirror Real-time SS481.0
Notes:
The GUI panel to create a PPRC path. To create a new path, select Action Create and click
Go. You are directed through a wizard to select the source and target LSS and the I/O port
connected to the source LSS. The wizard allows you to select the PPRC options and then
Verify your settings and Finish to create the path. Paths must be created before volume
pairs can be created.
Metro Mirror Real-time
Student Notebook
V3.1.0.1
Uempty
Figure 8-52. DS8000 GUI Copy Services SS481.0
Notes:
The DS8000 GUI Copy Services GUI can be used to execute Copy Services function in
single shot mode. There is currently no ability to save GUI tasks and execute them as was
the case in the ESS Copy Services Web interface. So, automation of the Copy Service
functions is primarily done using the DSCLI.
DS8000 GUI Copy Services
Student Notebook
Figure 8-53. Communicate with ESS Copy Services SS481.0
Notes:
To communicate with ESS Copy Services domain, the user must define the Copy Services
Servers of the Copy Services domain. The GUI provides a panel to perform this definition.
Once defined, the DS8000 can participate in the ESS Copy Services domain functions.
Communicate with ESS Copy Services
Student Notebook
V3.1.0.1
Uempty
Figure 8-54. Create FlashCopy SS481.0
Notes:
To create a FlashCopy using the GUI, select the Copy Services menu and select the
FlashCopy function. A panel is displayed and the user can select the Create action to
create a FlashCopy.
The panel wizard continues and walks the user through the process of selecting a source
volume and target volume for the FlashCopy.
Create FlashCopy
Student Notebook
Figure 8-55. Create a FlashCopy Wizard SS481.0
Notes:
The create a FlashCopy wizard walks the user through the process of creating a
FlashCopy of a source volume.
Create a FlashCopy Wizard
Student Notebook
V3.1.0.1
Uempty
Figure 8-56. Select a Source Volume SS481.0
Notes:
The user is given a list of source volumes and is asked to select a source volume for the
FlashCopy. Click next and you are given a list of target volumes.
Select a Source Volume
Student Notebook
Figure 8-57. ESS Copy Services CLI Commands SS481.0
Notes:
The CLI commands supported allow you to test the ESS Copy Services connection, query
volumes or PPRC initialization, or prime the CS Server with disk names. No tasks can be
created with the CLI. The tasks must be created using the graphical interface, and then
they can be executed using the rsExecuteTask command. The CLI includes IBM Java 1.1.8
or higher for Windows, AIX and Sun. Other platforms must get it separately to use the CLI.
In contrast, the DSCLI has a very robust set of commands for Copy Services.
ESS Copy Services CLI Commands
rsExecuteTask
Executes one or more saved tasks
Tasks can perform any PPRC or FlashCopy function
Tasks run in parallel
rsQuery
Obtains status of volumes and paths
rsQueryComplete
Queries for the completion of PPRC copy initialization
rsList2105s
Lists the mapping between host disk drive name (for example, hdisk) to ESS
LUN serial number
rsPrimeServer
Loads rsList2105s output into ESS Copy Services server
Makes Copy Services server easier to use (can use host names to identify
volumes)
rsTestConnection
A debugging tool to test communication to the ESS Copy Services server
Student Notebook
V3.1.0.1
Uempty
Figure 8-58. DSCLI Copy Services Commands SS481.0
Notes:
You can easily upgrade your system to use DS CLI by following the remove and install
procedures put in place for DS CLI. However, there are some things that you need to
consider before making this upgrade. The DS CLI is designed to support the following
features that exist on the IBM TotalStorage Enterprise Storage Server (ESS) Models 750
and 800:
A Copy Services domain, configured as part of the IBM TotalStorage Enterprise Storage
Server (ESS) Models 750 and 800.
FlashCopy Version 2 and PPRC Version 2 licenses that are available on the ESS.
However, the DS CLI is not designed to support the CLI scripts that you have written for
these features without modification.
FlashCopy Commands PPRC Commands
commitflash failoverpprc
commitremoteflash freezepprc
incflash lspprcpath
incremoteflash lsavailpprcport
lsflash mkgmir
lsremoteflash mkpprcpath
mkflash mkesconpprcpath
mkremoteflash mkpprc
reverseflash pausegmir
reverseremoteflash pausegmi
revertflash resumegmir
revertremoteflash resumepprc
rmflash rmgmir
rmremoteflash rmpprc
setremoteflashrev rmpprcpath
setflashrevertible unfreezepprc
unfreezeflash
DSCLI Copy Services Commands
Student Notebook
Figure 8-59. Make a FlashCopy SS481.0
Notes:
In the display above, a FlashCopy command is issued and the resulting output is displayed
showing that the command was successful. As you can see, you can specify one or more
volume pairs in these commands.
This mkflash command also sets up an incremental FlashCopy because of the -record and
-persist options that are set with the command.
Make a FlashCopy
dscli>mkflash -dev IBM.2107-75FA120 0010:0210 -record -persist 0010:0210 0011:0211 0012:02120013:0213
0014:0214
Date/Time: Fri Feb 25 12:23:49 PST 2002 DS CLI Version: 5.0.1.126 DS: IBM.2107-75FA120
FlashCopy pair 0010:0210 successfully created.
Student Notebook
V3.1.0.1
Uempty
Figure 8-60. List Established FlashCopies SS481.0
Notes:
This command lists the options for FlashCopies.
List Established FlashCopies
dscli>lsflash -l -dev IBM.2107-75FA120 0010:0210
Date/Time: Fri Feb 25 12:27:49 PST 2002 DS CLI Version: 5.0.1.126 DS: IBM.2107-75FA120
ID 0010:0210
SrcLSS 00
Sequence 10
Num Timeout 120
Active Copy Recording Disabled
Persistent Disabled
Revertible Disabled
Source Disabled
Write Enabled Target Enabled
Write Enabled Disabled
Background Copy Disabled
Out Of Sync Tracks 0
Date Created 02/25/2005 12:23:49
Date Synced 02/25/2005 12:23:50
Student Notebook
Checkpoint
1. T/F The DS8000 supports all of the ESS Copy Services features.
2. T/F The DS8000 Metro Mirror can be connected to a ESS as a
secondary subsystem for Remote Copies
3. T/F The DS6000 support PPRC over ESCON channels with an
ESS subsystem.
4. T/F The DS8000 CLI supports Copy Services commands to allow
users to automate their FlashCopy or Metro Mirror copies.
5. T/F The DS8000 Storage Manager can be used to automate
DS8000 Copy Services.
Student Notebook
V3.1.0.1
Uempty
Notes:
Unit Summary
Describe the IBM DS8000 Copy Services
Describe the FlashCopy functions
Describe the Remote Mirror functions
Describe the DS8000 Storage Manager GUI Copy Services
Describe the IBM DS8000 CLI for Copy Services
Describe the migration from ESS to DS8000 Copy Services
Student Notebook
Student Notebook
Copyright IBM Corp. 2005 Unit 9. DS Host Attachment Consideration 9-1
V3.1.0.1
Uempty
Unit 9. DS Host Attachment Consideration
The DS6000/DS8000 storage subsystem allows you to create logical
volumes and attach them to hosts. This unit looks at considerations for
attachment to host systems, including multipath drivers, host setup
requirements, and examples of LUN creation and attachment to a
host.
Describe the host attachment consideration for pSeries hosts
Describe the host attachment consideration for Windows hosts
Describe the host attachment consideration for Linux hosts
Describe the host attachment consideration for iSeries hosts
Accountability:
Checkpoint
Machine exercises
References
Concepts
Guide
SC26-7628 IBM TotalStorage DS8000 Host Attachment Guide
Student Notebook
Notes:
Unit Objectives
Describe the pSeries host attachment considerations
Describe the Windows host attachment considerations
Describe the Linux host attachment considerations
Describe the iSeries host attachment considerations
Student Notebook
V3.1.0.1
Uempty 9.1 AIX Support
Student Notebook
Figure 9-2. Topics: AIX Support SS481.0
Notes:
Topics: AIX Support
AIX Support
Windows Support
Linux Support
iSeries Support
Student Notebook
V3.1.0.1
Uempty
Figure 9-3. DS8000 and DS6000 AIX Support SS481.0
Notes:
IBM MOP Product and Solution Support Center
Support
Configuration
AIX server
Checking of code level
Installing SDD and DSXXXX Fileset
Replace 2105 fileset
Discover WWN of FC HBA
DS6000
Volume group configuration
Host attachment configuration
LUN creation
AIX server
Cfgmgr
DS8000 and DS6000 AIX Support
Student Notebook
Figure 9-4. IBM pSeries and RS/6000 Servers - AIX (1 of 2) SS481.0
Notes:
Supported FC adapters:
The following fibre-channel adapters are supported for RS/6000
or pSeries host systems:
Feature code 6228
Feature code 6239
Feature code 5716
Host Attachment scripts:
Two different Host Attachment scripts for AIX:
Attachment script to be used with SDD
Attachment script to be used with MPIO
Verification:
Use command lsdev Cc disk to verify that DS6000 or DS8000
volumes are correctly recognized on the AIX host:
Example: lsdev -Cc disk | grep 2107
hdisk3 Available 30-68-01 IBM FC 2107
IBM pSeries and RS/6000 Servers - AIX (1 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 9-5. IBM pSeries and RS/6000 Servers - AIX (2 of 2) SS481.0
Notes:
Supported multipath software:
IBM SDD 1.6.0 for AIX 5.1 ML7, 5.2 ML5 and 5.3 ML1
AIX MPIO for AIX 5.2 ML5 and 5.3 ML1
Boot support:
DS8000 and DS6000 are supported as boot devices for AIX hosts
that support fibre channel boot capabilities.
IBM pSeries and RS/6000 Servers - AIX (2 of 2)
Student Notebook
Figure 9-6. Checking AIX Code Level SS481.0
Notes:
The fibre channel adapters can be listed using the lsdev command. Use the Cc option and
grep the adapters for the string fcs.
Checking AIX Code Level
Student Notebook
V3.1.0.1
Uempty
Figure 9-7. Remove 2105 Fileset (1 of 9) SS481.0
Notes:
If the server has never been attached to an IBM ESS then, we can proceed with the
installation of the new 2107 device driver and SDD, but if it has been configured with ESS
volumes the old SDD and the devices.fcp.ibm.2105.rt must be removed first. Unmount all
filesystems on ESS disks, vary the volume groups offline, and export the file systems.
All devices of the ESS and the dpo device of the SDD driver must be removed with rmdev.
List the devices currently in use.
Remove 2105 Fileset (1 of 9)
Student Notebook
Notes:
List the software installed using lslpp and list the hdisks using lsdev. First rmdev the dpo
device of SDD. Make sure any filesystems on these LUNS are unmounted and the volume
groups are offline. You can export the volume groups too. If you need the data on these
volumes it is OK, you can import them again once the new device driver and SDD are
installed.
Student Notebook
V3.1.0.1
Uempty
Notes:
Remove the hdisks with rmdev l hdisk# -d for each device, also delete the vpath devices
with rmdev l vpath# -d. Make sure all the devices are gone by doing a lsdev Cc disk.
Only the internal HDD should remain. Do an lsvg and only rootvg should remain unless
there are filesystems on non-ESS disks.
Student Notebook
Notes:
Remove the fibre channel adapters too.
Student Notebook
V3.1.0.1
Uempty
Notes:
Go into smit and Software, -> Utilities -> Remove installed software. Find the
devices.fcp.disk.ibm2105.rte and remove it from the system. Also find the SDD software
and dremove it too.
Student Notebook
Notes:
Select the fileset and continue.
Student Notebook
V3.1.0.1
Uempty
Notes:
Make sure the preview option is no. If set to yes, the uninstall does not occur.
Student Notebook
Notes:
The ibm2105.rte files are removed; verify it from the output.
Student Notebook
V3.1.0.1
Uempty
Notes:
Run cfgmgr and verify that only internal disks remain.
Student Notebook
Figure 9-16. FileSet and MP SDD Installation SS481.0
Notes:
Lets install the new device driver and SDD. The user does have an option to use mpio if
running AIX 5.2 or 5.3
The new filesets provide a standard device driver which is generic and supports either ESS
2105 or DS6000 1750 or DS8000 2107 devices. And the SDD component at 1.6.0.2.
http://www-1.ibm.com/support/docview.wss?rs=540andcontext=ST52G7anddc=D400andq1=ESS+scriptanduid=ssg1S4000106andloc=en_USandcs=utf-8andlang=en
devices.fcp.disk.ibm.rte
http://www-1.ibm.com/support/docview.wss?rs=540andcontext=ST52G7anddc=D430anduid=ssg1S4000065andloc=en_USandcs=utf-8andlang=en
Platform AIX 5.2 SDD v1.6.0.2
FileSet and MP SDD Installation
Student Notebook
V3.1.0.1
Uempty
Figure 9-17. MP SDD Installation (1 of 7) SS481.0
Notes:
MP SDD Installation (1 of 7)
Student Notebook
Notes:
Unpack the device driver and SDD using tar with the xvf options.
Student Notebook
V3.1.0.1
Uempty
Notes:
Create a .toc file. This may or may not be necessary as the installation process usually
does this.
Student Notebook
Notes:
Call smit software install for latest available software.
Student Notebook
V3.1.0.1
Uempty
Notes:
Select the device driver fileset, both the device driver and SDD are installed.
Student Notebook
Notes:
Run the install and verify the OK result.
Student Notebook
V3.1.0.1
Uempty
Notes:
List the result and verify the install.
Student Notebook
Figure 9-24. Discover WWN of FC HBAs (1 of 3) SS481.0
Notes:
Now lets go discover the devices again using the new drivers and SDD.
Check the fibre cards.
Discover WWN of FC HBAs (1 of 3)
Student Notebook
V3.1.0.1
Uempty
Notes:
List the fcs0 and fcs1 to get the WWN of the adapters.
Student Notebook
Notes:
List the WWN of fcs1.
Student Notebook
V3.1.0.1
Uempty
Figure 9-27. Now You Go to the DS6000 (1 of 4) SS481.0
Notes:
Now let go define the disk in the DS6000.
Log on to the DSCLI. If you have not installed it yet, then get the CD containing the code
and install the AIX version on the system. It is not a smooth installation, but a bin file that
can run in silent mode if being done from a telnet session.
Now You Go to the DS6000 (1 of 4)
Student Notebook
Notes:
Verify that you have arrays and ranks and FB extent pools for open system volumes.
Student Notebook
V3.1.0.1
Uempty
Notes:
OK, looks like we have the extent pools we need to create volumes. If not, back up and
make them now, then we can proceed.
Student Notebook
Notes:
List the hostconnections defined and the current volume groups. We do not have anything
here for AIX so we have to create one.
Student Notebook
V3.1.0.1
Uempty
Figure 9-31. Volume Group SS481.0
Notes:
Lets make a volume group.
We make a volume group with the type scsimask with a name of VG_AIX_Server.
Volume Group
Student Notebook
Figure 9-32. Host Attachment (1 of 3) SS481.0
Notes:
Make two hostconnections using the WWNs of the adapters on the AIX server using VG4
we just defined and the I/O ports that they connect into on the DS6000. List them and verify
that they are correct.
Host Attachment (1 of 3)
Student Notebook
V3.1.0.1
Uempty
Notes:
We are just listing the hosttype scsimask to show what host types it includes. pSeries is
what we want, so this is correct.
Student Notebook
Notes:
These are the I/O ports definitions.
I/O ports
lwxyz (RICT)
w=frame
0-2 (DS8000)
0 (DS6000)
x=enclosure
0-7 (DS8000)
0-1 (DS6000)
y=card
0, 1, 3, or 4 (DS8000)
0-1 (DS6000)
z=port
0-3 top to bottom (DS8000 FICON/FCP)
0-3 left to right (DS6000 FICON/FCP)
0-1 top to bottom (DS8000 ESCON)
I0000-I2343 (DS8000)
I0000-I0003 and I0100-I0103 (DS6000)
Student Notebook
V3.1.0.1
Uempty
Figure 9-35. LUN Creation (1 of 2) SS481.0
Notes:
List the devices already defined.
LUN Creation (1 of 2)
Student Notebook
Figure 9-36. LUN Creation (2 of 2) SS481.0
Notes:
Make an FB volume, or two or three, depending on what you need.
LUN Creation (2 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 9-37. On AIX Server After CFGMGR - No Connection to the Switch SS481.0
Notes:
Run cfgmgr.
Oops, no connection to the ESS so we cant see the LUNs.
The FC HBA is not connected to the switch
On AIX Server After CFGMGR -
No Connection to the Switch
Student Notebook
Figure 9-38. On AIX Server After GFGMGR - Connection to the Switch SS481.0
Notes:
OK, we fixed the problem and rerun cfgmgr; now the adapter is showing up.
The FC HBA is connected to the switch
The FC HBA is connected to the switch
Connection to the Switch
Student Notebook
V3.1.0.1
Uempty
Figure 9-39. On AIX Server After CFGMGR - Connection to the Switch and to the DS6000 SS481.0
Notes:
Lets see if the LUN is there.
Connection to the Switch and to the DS6000
Student Notebook
Figure 9-40. After CFGMGR (1 of 3) SS481.0
Notes:
Yes, a couple of new devices and a vpath device, so SDD is working.
After CFGMGR (1 of 3)
Student Notebook
V3.1.0.1
Uempty
Notes:
Do an lsdev and the devices display as 1750 disks from the DS6000.
Student Notebook
Notes:
Query the device using SDDs datapath command.
Student Notebook
V3.1.0.1
Uempty
Figure 9-43. After Creation of VG and FS (1 of 3) SS481.0
Notes:
OK, the volume is there, so we made a volume group, logical volume, and a filesystem
using smit, and now we can display the results. Display the volume info with lspv or lscfg.
After Creation of VG and FS (1 of 3)
Student Notebook
Notes:
The volume group DS6KFS shows up in the lsvg and a df k shows us a filesystem
mounted on the mount point by the same name. Done.
Student Notebook
V3.1.0.1
Uempty
Notes:
The device is defined and shows as a device with two paths on fscsi0 and fscsi1. It is
device 1203 on the DS6000 13AAY2A.
Student Notebook
Student Notebook
V3.1.0.1
Uempty 9.2 Windows Support
Student Notebook
Figure 9-46. Topics: Windows SS481.0
Notes:
The DS6000 or DS8000 can configure volumes for Windows servers. This section covers
Windows setup and configuration considerations.
Topics: Windows
AIX Support
Windows Support
Linux Support
iSeries Support
Student Notebook
V3.1.0.1
Uempty
Figure 9-47. Windows Support SS481.0
Notes:
The Windows servers uses SDD for multipathing support.
Support
Configuration
Windows 2000 server
Installing SDD and DSXXXX Fileset
DS6K
LUN creation
Windows 2000 server
Rescan or reboot
Windows Support
Student Notebook
Figure 9-48. Intel-Based Servers - Windows SS481.0
Notes:
Support is provided for multipath access and boot support, but applications using the DS
API may only run on Windows 2000.
Supported multipath softwares:
SDD is available for MS Windows 2000 and MS Windows Server
2003
SDD does not support I/O Load balancing with Windows 2000
cluster configurations (MSCS)
Boot support:
DS8000 and DS6000 are supported as boot devices on MS
Windows 2000 (32-bit) or MS Windows Server 2003 (32-bit or
64-bit) servers that support Fibre Channel boot capabilities.
Restrictions:
DS API is only available for MS Windows 2000
Intel-Based Servers - Windows
Student Notebook
V3.1.0.1
Uempty
Figure 9-49. Windows Disk Management (1 of 2) SS481.0
Notes:
We start with a Windows server with nothing attached but the C drive.
Windows Disk Management (1 of 2)
Student Notebook
Figure 9-50. Windows Disk Management (2 of 2) SS481.0
Notes:
Windows Disk Management (2 of 2)
Student Notebook
V3.1.0.1
Uempty
Notes:
Go to the Web site and get the SDD or get it from the CD.
Web site:
www-.ibm.com/support/docview.wss?rs=540andcontext=ST52G7anddc=D430anduid=ssg1S4000054andloc=en_USandcs=utf-8andlang=en
Student Notebook
Notes:
Expand the file and run the setup.exe to install the product.
Student Notebook
V3.1.0.1
Uempty
Notes:
Reboot after the installation to finish.
Student Notebook
Figure 9-54. Volume Group on DS6000 (1 of 6) SS481.0
Notes:
Create a DS6000 or DS8000 volume group to connect the volumes to the host connection.
Create a volume group using the GUI or the DSCLI.
Volume Group on DS6000 (1 of 6)
Student Notebook
V3.1.0.1
Uempty
Notes:
Select the volume group type. Note that many hosts share this type and are selected as
well. Thats OK, there is no difference, they all use Map 256 as their addressing mode.
Student Notebook
Notes:
Now we need to associate a host attachment with the volumes.
Student Notebook
V3.1.0.1
Uempty
Notes:
Select the volumes for the volume group.
Student Notebook
Notes:
Verify the volume group properties.
Student Notebook
V3.1.0.1
Uempty
Notes:
The volume group has been successfully added.
Student Notebook
Figure 9-60. Host System on DS6000 SS481.0
Notes:
We are going to create a host system.
Host System on DS6000
Student Notebook
V3.1.0.1
Uempty
Figure 9-61. Host System - General Host Information SS481.0
Notes:
Select the host system type and assign a nickname.
Host System - General Host Information
Student Notebook
Figure 9-62. Host System - Define Host Ports (1 of 2) SS481.0
Notes:
Define the host attachments for the host.
Host System - Define Host Ports (1 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 9-63. Host System - Define Host Ports (2 of 2) SS481.0
Notes:
Add the fibre channel attachment.
Host System - Define Host Ports (2 of 2)
Student Notebook
Figure 9-64. Host System - Define Host WWPN SS481.0
Notes:
Specify the WWPN for the ports of this host.
Host System - Define Host WWPN
Student Notebook
V3.1.0.1
Uempty
Figure 9-65. Host System - Specify Storage Units SS481.0
Notes:
Specify the storage unit the host is attached to.
Host System - Specify Storage Units
Student Notebook
Figure 9-66. Host System - Specify Storage Units Parameters SS481.0
Notes:
Specify the volume group the host is associated with.
Host System -
Specify Storage Units Parameters
Student Notebook
V3.1.0.1
Uempty
Figure 9-67. Host System - Storage Units Parameters SS481.0
Notes:
Specify the host ports the host connects to on the DS6000.
Host System - Storage Units Parameters
Student Notebook
Figure 9-68. Host System - Verification SS481.0
Notes:
Verify the parameters for the host attachment.
Host System - Verification
Student Notebook
V3.1.0.1
Uempty
Figure 9-69. Host System on DS6000 SS481.0
Notes:
View the results. The server Host_Win2k has been added to the storage unit.
Host System on DS6000
Student Notebook
Figure 9-70. After SDD Install on Windows 2000 (1 of 2) SS481.0
Notes:
After SDD Install on Windows 2000 (1 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 9-71. After SDD Install on Windows 2000 (2 of 2) SS481.0
Notes:
After SDD Install on Windows 2000 (2 of 2)
Student Notebook
Figure 9-72. After Rescan or Reboot (1 of 6) SS481.0
Notes:
Lets see what happens after the volumes have been added.
This display shows the new volume, Disk 1 on the Disk Administrator.
After Rescan or Reboot (1 of 6)
Student Notebook
V3.1.0.1
Uempty
Notes:
Here is the E drive added to the system.
Student Notebook
Notes:
Here are the properties of the new drive added to the Windows system.
Student Notebook
V3.1.0.1
Uempty
Notes:
Here is the SDD display of the volume and it paths over the two HBAs. Currently we only
have the device attached to one controller so the I/O is done over that path unless there is
a failure, in which case the other adapter is used. The DS6000 runs in a failover mode
instead of load balancing, so we see all of the I/O for a single LUN over one path. To load
balance we must attach LUNs to each adapter as its preferred path.
Student Notebook
Notes:
Here are the volumes defined for the Windows system.
Student Notebook
V3.1.0.1
Uempty
Notes:
Here is another SDD display after a second volume was added and attached to the other
path.
Due to controller
failover
LSS 13
LSS 12
Student Notebook
Student Notebook
V3.1.0.1
Uempty 9.3 Linux Support
Student Notebook
Figure 9-78. Topics: Linux SS481.0
Notes:
The DS6000 or DS8000 can configure volumes for Windows servers. This section covers
Linux setup and configuration considerations.
Topics: Linux
AIX Support
Windows Support
Linux Support
iSeries Support
Student Notebook
V3.1.0.1
Uempty
Figure 9-79. Agenda SS481.0
Notes:
The configuration of LUNs for the Linux platforms consists of:
Verifying the code levels,
Discovering the HBAs
Installing SDD for multi-path access
Configuring the volume groups and
Configuring the host attachments for Linux
Discovering the LUNs from the DS6000 or DS8000
Support
Configuration
Linux server
Checking of code level
Installing SDD
DS6000
LUN creation
Linux server
modprobe and scsi_scan
Agenda
Student Notebook
Figure 9-80. Servers LINUX RH SS481.0
Notes:
Lets check the level of the Linux OS and look at the FC HBAs we have installed.
The uname command displays the Linux system and its current level.
Servers - LINUX RH
Student Notebook
V3.1.0.1
Uempty
Figure 9-81. Firmware Checking (1 of 3) SS481.0
Notes:
The firmware level of the HBAs is contained in files located under the adapter type in the
/proc/scsi directory. First cd to the /proc/scsi directory and list the files looking for the Qlogic
adapter. We see a qla2300 2Gb FC adapter, so cd into that directory and list the files. The
1 and 2 files are what we are looking for.
Firmware Checking (1 of 3)
Student Notebook
Notes:
Cat the contents of 1 and 2 to see the information related to the firmware levels of the
cards. Verify that with the FC interoperability matrix from IBM and make sure you have the
recommended levels.
Student Notebook
V3.1.0.1
Uempty
Notes:
Cat the 2 file as well.
Student Notebook
Figure 9-84. Checking of Number of LUNs (1 of 2) SS481.0
Notes:
Lets check the LUNs.
The modules.conf contains information about the adapters.
Checking of Number of LUNs (1 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 9-85. Checking of Number of LUNs (2 of 2) SS481.0
Notes:
The RAM-disk should be rebuilt to configure the new adapter information so that it remains
loaded even after a reboot. Make a copy of the old RAM-disk image first.
Checking of Number of LUNs (2 of 2)
Student Notebook
Figure 9-86. Rebuild the RAM-Disk (1 of 2) SS481.0
Notes:
Now rename the file to a .sav copy and then issue the mkinitrd command.
Rebuild the RAM-Disk (1 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 9-87. Rebuild the RAM-Disk (2 of 2) SS481.0
Notes:
Now reboot.
Rebuild the RAM-Disk (2 of 2)
Student Notebook
Figure 9-88. Now You Go to the DS6000 SS481.0
Notes:
Now we are going to make sure we have the Linux host and volumes configured in the
DS6000.
Do a lsvolgrp and an lshostconnect to see if the host is defined and if a volumegroup for the
Linux host exists. It does. The volume group V6 is listed and two Linux hosts with IDs 0005
and 0006 are there.
Now You Go to the DS6000
Student Notebook
V3.1.0.1
Uempty
Figure 9-89. Volume Group SS481.0
Notes:
Show the volume group V6, which was the Linux Volume Group.
Volume Group
Student Notebook
Notes:
Show the host connections 0005 and 0006, which is the Linux host.
Student Notebook
V3.1.0.1
Uempty
Notes:
List the FB volumes we have and note the volume 1204. This volume does nicely.
Student Notebook
Figure 9-92. LUN SS481.0
Notes:
Show the attributes of the LUN 1204 using the showfbvol command.
LUN
Student Notebook
V3.1.0.1
Uempty
Notes:
Lets install SDD for our multipath driver.
The CD contains a version of SDD for the Linux host platform. We install version 1.6.0.2
www-1.ibm.com/support/docview.wss?rs=540andcontext=ST52G7anddc=D430anduid=ssg1S4000065andloc=en_USandcs=utf-8andlang=en
Platform Linux SDD v1.6.0.2
Student Notebook
Notes:
List the files, for SDD the file is IBMsdd-1.6.0.1-3.i686.rhel3.rpm.
Student Notebook
V3.1.0.1
Uempty
Notes:
Install the file.
Student Notebook
Notes:
List the result.
Student Notebook
V3.1.0.1
Uempty
Figure 9-97. Check LUN Availability SS481.0
Notes:
Check for LUNs, oops we dont see any yet. Why not? Well, we installed SDD but we have
not started or configured the LUNs yet, so lets do that.
Check LUN Availability
Student Notebook
Figure 9-98. Determine if Module qla2300 is Installed SS481.0
Notes:
List the modules; we use qla2300.
Determine if Module qla2300 is Installed
Student Notebook
V3.1.0.1
Uempty
Figure 9-99. Unload Module qla2300 SS481.0
Notes:
Issue a modprobe command with qla2300.
Unload Module qla2300
Student Notebook
Figure 9-100. Reload Module for qla2300 in Order to Discover New LUNs SS481.0
Notes:
Now cat the scsi devices and we have some LUNs. The two at the bottom are from the
DS6000 which is a 1750500 device. We saw the device two times because of the two
adapters.
Reload Module for qla2300 in Order to
Discover New LUNs
Student Notebook
V3.1.0.1
Uempty
Figure 9-101. The LUNs Are Not Seen by SDD SS481.0
Notes:
Issue a datapath query device command. Well, no devices found, guess we are not there
yet, so issue sdd start and then cfgvpath.
The LUNs Are Not Seen by SDD
Student Notebook
Figure 9-102. The LUNs Are Seen by SDD SS481.0
Notes:
Now do the datapath query device. That looks better. Now we see the device 1204 on
DS6000 13AAY2A. The device is identified as vpatha and it has two paths 0 and 1. Notice
the device is seen as two scsi devices sdb and sdc. If we do an lsvpcfg we get information
about the device.
The LUNs Are Seen by SDD
Student Notebook
V3.1.0.1
Uempty
Figure 9-103. Add a New Partition to Linux with the LUN from DS6000 (1 of 2) SS481.0
Notes:
Lets format the device for use using fdisk. The m option prints the menu and then you can
use the n option to add a new partition.
Add a New Partition to Linux with the LUN
from DS6000 (1 of 2)
Student Notebook
Figure 9-104. Add a New Partition to Linux with the LUN from DS6000 (2 of 2) SS481.0
Notes:
Select a p Primary partition and a number 1 for the partition number. Lets just use the
whole disk so enter 1 as the start and 1024 as the end, and then w write it to the disk. OK,
so we formatted the disk.
Add a New Partition to Linux with the LUN
from DS6000 (2 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 9-105. Create a Filesystem (1 of 2) SS481.0
Notes:
Now we can make a filesystem on the disk. Use the mkfs command as shown to create a
filesystem on device /dev/vpatha. Remember not to use the other scsi devices /dev/sdb or
/dev/sdc or you wont get the multipath/failover operations that you most likely want and
SDD provides, but only if you use the SDD pseudo device vpatha. Remember that the
DS6000 uses a preferred path access which the new SDD supports for the 1750, so it is
not like the load balancing of the ESS or the DS8000.
Create a Filesystem (1 of 2)
Student Notebook
Figure 9-106. Create a Filesystem (2 of 2) SS481.0
Notes:
OK, so query the adapter and see the results. The device was selected over one of the two
paths, not both. This is because the DS6000 works with a preferred path or failover type of
multipath access, so both paths to the device are not used, but if a failover occurs, then the
second path 0 takes over.
Create a Filesystem (2 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 9-107. Mount the Filesystem /PSSCeduc1 (1 of 2) SS481.0
Notes:
Mount the filesystem we created on /PSSCeduc1. OK, we are done.
Mount the Filesystem /PSSCeduc1 (1 of 2)
Student Notebook
Figure 9-108. Mount the Filesystem /PSSCeduc1 (2 of 2) SS481.0
Notes:
There it is; we have a DS6000 LUN attached to the Linux host.
Mount the Filesystem /PSSCeduc1 (2 of 2)
Student Notebook
V3.1.0.1
Uempty 9.4 iSeries Support
Student Notebook
Figure 9-109. Topics: iSeries SS481.0
Notes:
Topics: iSeries
AIX Support
Windows Support
Linux Support
iSeries Support
Student Notebook
V3.1.0.1
Uempty
Figure 9-110. iSeries Servers OS/400 and i5/OS (1 of 2) SS481.0
Notes:
Supported FC adapters:
The following fibre-channel adapters are supported for iSeries systems running
OS/400 or i5/OS:
2766 2 Gigabit Fibre Channel Disk Controller PCI
2787 2 Gigabit Fibre Channel Disk Controller PCI-X
Each adapter requires its own dedicated IO processor
Supported multipath software:
SDD is not available for iSeries servers
Multipath support is provided only in i5/OS V5R3 or higher
With an i5/OS V5R3 system, a Volume can be shared by multiple
fibre-channel adapters if they are within the same i5/OS LPAR
iSeries Volumes
1 to 32 LUNs for each attachment to an IBM iSeries fibre-channel adapter
DS6000 LUNs are identified as storage unit device type 1750 on the iSeries
hosts
DS8000 LUNs are identified as storage unit device type 2107 on the iSeries
hosts
iSeries LUNs can only be created with the following predefined sizes:
8.5 GB, 17.5 GB , 35.1 GB , 70.5 GB , 141.1 GB or 282.2 GB
iSeries Servers - OS/400 and i5/OS (1 of 2)
Student Notebook
Figure 9-111. iSeries Servers OS/400 and i5/OS (2 of 2) SS481.0
Notes:
Boot support :
DS8000 and DS6000 are NOT supported as boot devices for
iSeries hosts
Restrictions and limitations :
0 to 32 LUNs per target (FC adapter)
!! iSeries supports only homogeneous SAN environment (only
iSeries initiators): All Hosts systems within an IBM iSeries
zone must be IBM iSeries systems
DS Application program Interface (DS API / CIM Agent) is not
available for iSeries servers
iSeries Servers - OS/400 and i5/OS (2 of 2)
Student Notebook
V3.1.0.1
Uempty
Figure 9-112. DS6000 Connection to iSeries Systems: Step by Step Commands SS481.0
Notes:
The next slides describe the different operation that have been
performed to define an iSeries host on the DS6000 and use its
volumes
Major DS6000 commands are provided either in graphical mode
or command line mode
Different screen captures are also copied from different program
to show how the DS6000 volumes are seen and used form the
iSeries host
DS6000 Connection to iSeries Systems:
Step by Step Commands
Student Notebook
Figure 9-113. iSeries Host Definition SS481.0
Notes:
From the GUI, define first an iSeries host named Host-iSeries with one FC switched attachment
iSeries Host Definition
Student Notebook
V3.1.0.1
Uempty
Figure 9-114. iSeries Volume Group Creation SS481.0
Notes:
From the GUI, then define a Volume Group for iSeries host named VG-iSeries
iSeries Volume Group Creation
Student Notebook
Figure 9-115. iSeries Volume Group Creation SS481.0
Notes:
And add the iSeries FC host attachment to the Volume Group
iSeries Volume Group Creation
Student Notebook
V3.1.0.1
Uempty
Figure 9-116. iSeries Volume Group Creation: Summary SS481.0
Notes:
iSeries Volume Group Creation: Summary
Student Notebook
Figure 9-117. Volume Group Verification SS481.0
Notes:
Volume Group verification from the CLI : VG-iSeries has ID V5
Volume Group Verification
Student Notebook
V3.1.0.1
Uempty
Figure 9-118. Host Verification SS481.0
Notes:
Host verification from the CLI with commands lshostconnect and showhostconnect:
Host-iSeries has ID 0004, is assigned to VG V5 and attached to the DS6000 by FC ports
I0000 and I0100
Host Verification
Student Notebook
Figure 9-119. Creation of iSeries Protected Volumes on the DS6000 SS481.0
Notes:
Creation of 2x 8 GB Protected OS400 Volumes (type A01) into the iSeries Volume Group
VG-iSeries
Verification: We see the new volumes with ID 1400 and 1401
Creation of iSeries Protected
Volumes on the DS6000
Student Notebook
V3.1.0.1
Uempty
Figure 9-120. DS6000 Volumes View from the iSeries SS481.0
Notes:
Two new disks appear on the list of disks displayed by the WRKDSKSTS command.
Disk type is 1750 for DS6000.
DS6000 Volumes View from the iSeries
Student Notebook
Figure 9-121. Creation of iSeries Unprotected Volumes on the DS6000 SS481.0
Notes:
Creation of 2x 8 GB Unprotected OS/400 Volumes (type A81) into the iSeries Volume Group
VG-iSeries
Verification: We see the new volumes with ID 1500 and 1501
Creation of iSeries Unprotected
Volumes on the DS6000
Student Notebook
V3.1.0.1
Uempty
Figure 9-122. Volume Group Verification SS481.0
Notes:
Verification: From command showvolgrp, we see that Volume Group VG-iSeries
Include now the 4 Volumes 1400, 1401, 1500 and 1501
Volume Group Verification
Student Notebook
Figure 9-123. DS6000 Volumes Usage in iSeries Disk Pools (1 of 4) SS481.0
Notes:
The 2 Protected disks have been added to a disk pool (2) and are usable.
Two new unprotected disks appear but are not yet configured.
DS6000 Volumes Usage in
iSeries Disk Pools (1 of 4)
Student Notebook
V3.1.0.1
Uempty
Notes:
Add now the two unprotected disks to a new disk pool.
Student Notebook
Notes:
Verification: The two unprotected disks have been added to the new disk pool.
They are still unprotected and the mirroring will have to be started.
Student Notebook
V3.1.0.1
Uempty
Notes:
Disk pool usage test : To use the new disk pool, just create the objects in the asp (or disk
pool) 2 or 3
Student Notebook
Checkpoint
Exercise - Unit 9 Checkpoint
1. T/F The DS8000 requires a new fileset for the 2107 devices to
attach to a pSeries system.
2. T/F The DS8000 MPIO multipath driver can be used instead of the
SDD multipath driver on the AIX platforms.
3. T/F The DS8000 SDD software replace the current ESS SDD
package and supports both products.
4. T/F For systems using other multipath drivers such as Veritas, SDD
is not required.
Student Notebook
V3.1.0.1
Uempty
Notes:
Unit Summary
Describe the pSeries host attachment considerations
Describe the Windows host attachment considerations
Describe the Linux host attachment considerations
Describe the iSeries host attachment considerations
Student Notebook
Student Notebook
Copyright IBM Corp. 2005 Appendix A. DS8000 LPAR A-1
V3.1.0.1
Uempty
Appendix A. DS8000 LPAR
Student Notebook
A-2 DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
Figure A-1. DS8300 Logical Partitions: Terminology SS481.0
Notes:
LPAR is one component of the POWER5 system technology that is part of the IBM
Virtualization Engine.
Using IBM Virtualization Engine technology, selected models of the DS8000 series can be
used as a single, large storage system, or can be used as multiple storage systems with
logical partitioning (LPAR) capabilities. IBM LPAR technology, which is unique in the
storage industry, allows the resources of the storage system to be allocated into separate
logical storage system partitions, each of which is totally independent and isolated.
Virtualization Engine (VE) delivers the capabilities to simplify the infrastructure by allowing
the management of heterogeneous partitions/servers on a single system.
DS8300 Logical Partitions: Terminology
Partitions
When a multiprocessor computer is subdivided into multiple,
independent operating system images.
Resources
Resources are defined as a systems processors, memory, and
I/O slots. I/O slots can be populated by different adapters, such as
Ethernet, SCSI, Fibre Channel or other device controllers.
Logical Partitioning (LPAR)
A logical partition uses hardware and firmware to logically
partition the resources on a system.
LPARs logically separate the operating system images, so there
is not a dependency on the hardware building blocks.
Student Notebook
V3.1.0.1
Uempty
Figure A-2. Server LPAR Concept Overview SS481.0
Notes:
Resources are defined as a systems processors, memory, and I/O slots. I/O slots can be
populated by different adapters, such as Ethernet, SCSI, Fibre Channel or other device
controllers. A disk is allocated to a partition by assigning it the I/O slot that contains the
disks controller.
An LPAR
Uses hardware and firmware to logically partition resources
Is a subset of logical resources that is capable of supporting an operating
system
Consists of CPUs, memory, and I/O slots that are a subset of the pool of
available resources within a system
Very flexible granularity according to AIX level (5.2, 5.3, and so forth)
No need to conform to physical boundaries of building blocks
In an LPAR
An operating system instance runs with dedicated (AIX 5.2) or shared (AIX 5.3)
resources: processors, memory, and I/O slots
These resources are assigned to the logical partition
The total amount of assignable resources is limited by the physically installed
resources in the system
LPARs provide
Isolation between LPARs to prevent unauthorized access between partition
boundaries
Fault isolation such that one LPARs operations do not interfere with the
operation of other LPARs
Support for multiple independent workloads, different operating systems,
operating system levels, applications, and so forth
Server LPAR Concept Overview
Student Notebook
Figure A-3. Potential Applications in Storage System LPARs SS481.0
Notes:
Generally, production and test environments should be isolated from each other. Without
partitioning, the only practical way of performing application development and testing is to
purchase additional hardware and software.
Partitioning is a way to set aside a portion of the system resources to use for testing new
versions of applications and operating systems, while the production environment
continues to run. This eliminates the need for additional servers dedicated to testing, and
provides more confidence that the test versions migrate smoothly into production because
they are tested on the production hardware system.
2-way P5 570 Server

Memory DIMMs
Memory DIMMs
P5
L3 Cache
Memory DIMMs
Memory DIMMs
P5
L3 Cache
2-way P5 570 Server
Memory DIMMs
Memory DIMMs
P5
Memory DIMMs
Memory DIMMs
P5
L3 Cache
L3 Cache
2-way P5 570 Server

Memory DIMMs
Memory DIMMs
P5
L3 Cache
Memory DIMMs
Memory DIMMs
P5
L3 Cache
2-way P5 570 Server
Memory DIMMs
Memory DIMMs
P5
Memory DIMMs
Memory DIMMs
P5
L3 Cache
L3 Cache
Potential Applications
in Storage System LPARs
Integrated File Systems
SFS
NAS
Others
Additional Storage Protocols / Interfaces
iSCSI gateway
Object Server
Database Acceleration/Offload
DB2 (Health check, multilevel security, DB
reorgs, image copies, HSM)
Oracle
Backup / Recovery
TSM, Legato, Veritas, others
Disk to Tape offload
Integrated Domain-Specific Apps
Reference Data
Medical Imaging
Integrated Functions
ESSNet
SVC
Delayed RPO
Student Notebook
V3.1.0.1
Uempty
Figure A-4. Logical Partition Illustration SS481.0
Notes:
In the DS8300 Model 9A2 each processor complex has four processors and up to 128 GB
memory. Initially there is also a 50/50 split for processor and memory allocation.
Therefore, every LPAR has two processors, so every storage facility image has four
processors.
The memory limit depends on the total amount of available memory in the whole system.
Logical Partition Illustration
Processor
Cache
Processor
Cache
Processor
Cache
Processor
Cache
Processor
Cache
Processor
Cache
Memory
I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O
HMC: hardware management console
Logical
Partition 0
Logical Partition 1
Logical Partition 2
Student Notebook
Figure A-5. LPAR Protection in IBM POWER5 Hardware SS481.0
Notes:
This is a fairly technical chart that shows how the hardware and firmware mechanisms
work to ensure that operating systems running in different partitions can't interfere with
each other.
This example shows resources owned by two partitions, in red and blue.
Virtual addresses in the processors are translated by page tables into addresses into real
memory, and only the Hypervisor is allowed to change those tables. There are several
Hypervisor calls that the operating system uses to request new pages and delete old ones.
Each partition also needs some amount of real address memory, starting at address 0.
Since the partitions can't really all have access to address 0, there is a special register in
the processor that gets automatically added to all real address requests. That way, each
operating system thinks it has an address 0, but in fact that address range can be
redirected anywhere in physical memory.
For I/O devices that do DMA, there is an equivalent translation method called Translation
Control Entries that is also controlled by the Hypervisor. This is controlled at an I/O adapter
Hypervisor-
Controlled
TCE Tables
For DMA
B
u
s

A
d
d
r
e
s
s
e
s
B
u
s

A
d
d
r
e
s
s
e
s
B
u
s

A
d
d
r
e
s
s
e
s
B
u
s

A
d
d
r
e
s
s
e
s
Physical
Memory
Partition 1
I/O Slot
I/O Slot
I/O Slot
I/O Slot
Partition 2
I/O Slot
I/O Slot
Proc
Proc
Proc
Proc
Proc
Partition 1
Partition 2
V
i
r
t
u
a
l

A
d
d
r
e
s
s
e
s
V
i
r
t
u
a
l

A
d
d
r
e
s
s
e
s
V
i
r
t
u
a
l

A
d
d
r
e
s
s
e
s
V
i
r
t
u
a
l

A
d
d
r
e
s
s
e
s
Hypervisor-
Controlled
Page Tables
N
N
N
0
0
0
Real Addresses
Real Addresses
{
{
Addr N Addr N
Addr 0 Addr 0
I/O Load/Store
I/O Load/Store
Proc
The Hardware and Hypervisor manage the real to virtual memory mapping
to provide robust isolation between partitions
PHYP
LPAR Protection in IBM POWER5 Hardware
Proc
Student Notebook
V3.1.0.1
Uempty
slot level. When a device tries to transfer data into or out of memory, this mechanism
ensures that it can only access memory that is valid for that partition.
Lastly, the processors have to read and write registers in the I/O devices to set up I/O
operations. Access to those address spaces are also controlled through the virtual-to-real
translation in the page tables.
Student Notebook
Figure A-6. LPAR Applied to Storage Facility Images (SFI) SS481.0
Notes:
The DS8300 series incorporates two SServer p5 570s. We call each of these a processor
complex. Each processor complex supports one or more LPARs. Currently each processor
complex on the DS8300 is divided into two LPARs. An LPAR is a set of resources on a
processor complex that support the execution of an operating system. The storage facility
image is built from a pair of LPARs, one on each processor complex.
LPAR Applied to Storage Facility Images (SFI)

DS8300
Two eServers P5 570
Processor complex
Each processor complex
supports one or more LPARs
Currently, each processor
complex divided into two
LPARs
An LPAR in a Processor
Complex
Set of resources to support exec
of an operating system
The Storage Facility Image
(SFI)
Built from a pair of LPARs
One of each processor complex
Each image can run it own level
of microcode
Each Storage image has a
unique ID and arrays
connected
Note: An LPAR in a processor
complex is not the same as a
SFI in the DS8300
LPAR02
Processor
complex 0
Processor
complex 1
Storage
Facility
Image 1
Storage
Facility
Image 2
LPAR01 LPAR11
LPAR12
LPARxy
x=Processor complex number
y=Storage facility number
Student Notebook
V3.1.0.1
Uempty
Figure A-7. Basic Storage SS481.0
Notes:
The DS8000 base frame contains two processor complexes. The Model 921 has 2-way
processors while the Model 922 and Model 9A2 have 4-way processors. (2-way means
that each processor complex has two CPUs, while 4-way means that each processor
complex has four CPUs.) For the purpose of using LPARs the 2-way processor can not be
split up, but the 4-way processor can be split across the LPARs.
Basic Storage
This is a big picture look at a basic
Storage Subsystem
There are Host Adapters that
communicate with the Host Systems
and the CECs
There are CECs with the
processors, memory, and
microcode that control everything
There are Device Adapters that
communicate with the CECs and the
DDMs
And DDMs to write and read the
hosts data
Student Notebook
Figure A-8. Model 921 or 922 Single Storage Facility Image SS481.0
Notes:
A Model 922 supports one storage facility image or one LPAR. The storage unit is the
same, but a single Image is created owning all the resources and having a storage image
ID. If the storage unit has a serial number of IBM.2107-1300230, then the storage facility
image ID is IBM.2107-1300231.
Model 921 or 922 Single Storage Facility Image
This is a big picture look at a 2107 model
921 or 922 that support one Storage
Facility Image
There are all the same basic components
as the previous page
But the 2107 is different because each of
the 2107 CECs are running one LPAR
(Logical Partition)

Both of the LPARs (one in each CEC) work
together to create a single Storage Facility
Image

Basically the Host Systems would see a
single storage subsystem similar to the
previous page
Student Notebook
V3.1.0.1
Uempty
Figure A-9. DS8000 Model 9A2 LPARs SS481.0
Notes:
The management of the resource allocation between LPARs on a pSeries is done via the
Storage Hardware Management Console (S-HMC). Because the DS8300 Model 9A2
provides a fixed split between the two storage facility images, there is no management or
configuration necessary via the S-HMC. The DS8300 comes preconfigured with all
required LPAR resources assigned to either storage facility image.
If the Storage Unit has a serial number of IBM.2107-1300230, then the Storage Facility
Image 1 ID is IBM.2107-1300231 and Storage Facility Image 2 is IBM.2107-1300232.
DS8000 Model 9A2 LPARs
The model 9A2 supports dual
(two) Storage Facility Images
on one base rack and its
expansion racks
The CECs run two LPARs
(Logical Partitions) that create
two separate 2107 storage
facility images
Each image has its own Host
Adapters
Each image has its own
Device Adapters
And each image has its own
DDMs
From a host system point of
view this looks like two 2107
images
Student Notebook
Figure A-10. DS8300 Architecture with LPAR SS481.0
Notes:
The figure above shows the split of all available resources between the two storage facility
images. Each storage facility image has 50% of all available resources.
First application of the
pSeries Virtualization Engine
technology in DS8000
partitions the subsystem into
two virtual storage system
images
Split processors, cache,
adapters and disks between
images
Robust isolation between
images via hardware and
POWER hypervisor firmware
Each storage subsystem
LPAR can run its own level of
microcode
Delivered AS IS, no need using
the MC to configure
DS8300 Architecture with LPAR
Host
Adapters
Fault Tolerant Switch Fabric
Host
Adapters
Host
Adapters
Host
Adapters
Host
Adapters
Host
Adapters
LPAR
Image1
LPAR
Image2
LPAR
Image2
LPAR
Image1
RAID
Adapters
RAID
Adapters
RAID
Adapters
RAID
Adapters
Student Notebook
V3.1.0.1
Uempty
Figure A-11. DS8300 Example of Storage Facility Images SS481.0
Notes:
Each storage facility image has access to:
50 percent of the processors
50 percent of the processor memory
1 loop of the RIO-G interconnection
Up to 16 host adapters (four I/O drawers with up to four host adapters)
From 16 to 320 disk drives (up to 96 TB of capacity)
DS8300 Example of Storage Facility Images
LUN0
LUN1
LUN2
3390-3
3390-3
System 1
Open System
System 2
zSeries
DS8300 Model 9A2
(Physical Capacity: 30TB)
Storage Facility Image 1
Capacity: 20 TB Fixed Block (FB)
LIC level: A
License function: Point-in-time Copy
License feature: FlashCopy
Capacity: 10 TB Count Key Data (CKD)
LIC level: B
License function: no Copy function
License feature: no Copy feature
Student Notebook
Figure A-12. DS8300 Resource Allocation Example SS481.0
Notes:
In this section we explain which hardware resources are required to build a storage facility
image.
DS8300 Resource Allocation Example
S-HMC
Processor complex 1 Processor complex 0 Processor complex 0
Processors 2 Processors
Memory
2 Processors
Memory
I/O drawer
0
HA DA HA HA HA DA
Processors 2 Processors
Memory
RIO-G interface
SCSI controller
Ethernet-Port
RIO-G interface
RIO-G interface
I/O drawer
1
HA DA HA HA HA DA
2 Processors
Memory
Ethernet-Port
RIO-G interface
Ethernet-Port
SCSI controller
RIO-G interface
RIO-G interface
Ethernet-Port
SCSI controller
RIO-G interface
RIO-G interface
Ethernet-Port
SCSI controller
RIO-G interface
RIO-G interface
RIO-G interface
SCSI controller
Ethernet-Port
RIO-G interface
RIO-G interface
I/O drawer
3
HA DA HA HA HA DA
I/O drawer
2
HA DA HA HA HA DA
C
D
/
D
V
D
C
D
/
D
V
D
boot data data boot data data
A A'
B B'
C C'
D D'
Student Notebook
V3.1.0.1
Uempty
Figure A-13. Storage Facility Virtualization SS481.0
Notes:
A Storage Facility image is a virtual storage subsystem with it own copy of Licensed
Internal Code (LIC) which consists of the AIX kernel and the functional code.
Both Storage Facility images share the physical hardware and the LPAR hypervisor
manages this sharing of the hardware.
Storage Facility Virtualization
RIO-G
Processor Processor
Memory Memory
I/O I/O
RIO-G
Processor Processor
Memory Memory
I/O I/O
RIO-G
Processor Processor
Memory Memory
I/O I/O
LIC LIC LIC LIC
LPAR Hypervisor
Storage Facility image 1 Storage Facility image 2
Physical
view:
physical
storage unit
Logical
view:
virtual
Storage
Facility
images
takes part of takes part of
takes part of
Student Notebook
Figure A-14. DS8300 SFIs and Copy Services SS481.0
Notes:
The Copy Services features are installed separately on each LPAR.
DS8300 SFIs and Copy Services
Remote Mirroring and Copy (PPRC) within a Storage Facility Image or
across Storage Facility Images
FlashCopy within a Storage Facility Image only
PPRC
Primary
PPRC
Primary
PPRC
Secondary
PPRC
Secondary
FlashCopy
Source
FlashCopy
Source
FlashCopy
Target
FlashCopy
Target

PPRC
Primary
PPRC
Primary
PPRC
Secondary
PPRC
Secondary
FlashCopy
Source
FlashCopy
Source
FlashCopy
Target
FlashCopy
Target

Student Notebook
Copyright IBM Corp. 2005 Appendix B. DS8000 Layout and Cabling Rules B-1
V3.1.0.1
AP
Appendix B. DS8000 Layout and Cabling Rules
Student Notebook
B-2 DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
Figure B-1. Topic: DS8000 Layout and Cabling Rules SS481.0
Notes:
The DS8000 I/O enclosures and cabling rules.
Topic: DS8000 Layout and Cabling Rules
DS8000 Highlights
DS8000 Hardware components
DS8000 Architecture
DS8000 RAS Features
DS8000 Layout and cabling rules
Supplemental Information
Ordering Considerations
Student Notebook
V3.1.0.1
AP
Figure B-2. I/O Enclosure Numbers SS481.0
Notes:
The DS8000 has up to eight I/O enclosures or RIO-G bays. Four are in the base frame and
four are in the first expansion frame of the model 922 or 9A2.
I/O Enclosure Numbers
5 4
6 7
Expansion Frame
(front view)
1 0
2 3
Complex 1
Base Frame
(front view)
Complex 0
4 5
7 6
Expansion Frame
(rear view)
I/O enclosure numbers
Front view
0 1
3 2
Complex 1
Base Frame
(rear view)
Complex 0
The numbers in the I/O enclosures pictured above
are the I/O enclosure numbers.
They are used in the RIO-G loop diagrams
shown on the following pages.
Refer back to the above diagrams to see where
the enclosures are physically located.
I/O enclosure numbers
Rear view
The I/O enclosure numbers do not change with
each model, unlike the way the RIO-G loops
are wired.
All further diagrams in this presentation are
from the front view of the DS8000.
Even numbered I/O enclosures are always cabled closer to server 0.
Odd numbered I/O enclosures are always cabled closer to server 1.
Student Notebook
Figure B-3. Model 921 Two I/O Enclosures SS481.0
Notes:
The DS8000 model 921 can only support one RIO-G loop with either two or four I/O
enclosures attached. Currently, there is no supported configuration with only two I/O
enclosures.
Model 921 Two I/O Enclosures
Server 0
(EVEN LSS)
RIO-G ports
Server 1
(ODD LSS)
RIO-G ports
I/O enclosure 3
I/O enclosure 2
Loop 0
This configuration will not be available at GA.
( At GA a model 921 will always ship with four I/O enclosures).
Student Notebook
V3.1.0.1
AP
Figure B-4. Model 921 Four I/O Enclosures SS481.0
Notes:
The DS8000 model 921 can support one RIO-G loop with four I/O enclosures attached.
There is one set of RIO-G ports on the model 921 and they form a loop with four I/O
enclosures. The enclosures can have four Has each and two DAs each.
Model 921 Four I/O Enclosures
Server 0
(EVEN LSS)
RIO-G ports
Server 1
(ODD LSS)
RIO-G ports
I/O enclosure 0 I/O enclosure 3
Loop 0
Four enclosures is the maximum number
for a model 921.
Student Notebook
Figure B-5. Model 922 Four I/O Enclosures SS481.0
Notes:
The DS8000 model 922 can support two RIO-G loops with four or eight I/O enclosures
attached. The second set of four RIO-G bays are housed in the 92E expansion unit.
Model 922 Four I/O Enclosures
Server 0
EVEN LSSs
RIO-G ports
Server 1
ODD LSSs
RIO-G ports
I/O enclosure 0
I/O enclosure 1
I/O enclosure 2
I/O enclosure 3
Loop 0
Loop 1
A model 922 has extra hardware to support a second RIO-G loop
In this configuration.
On Loop 0 on 921
Student Notebook
V3.1.0.1
AP
Figure B-6. Model 922 Eight I/O Enclosures SS481.0
Notes:
The DS8000 model 922 with eight RIO-G bays gives the maximum performance and
throughput.
Model 922 Eight I/O Enclosures
Loop 0
Server 0
EVEN LSSs
RIO-G ports
Server 1
ODD LSSs
RIO-G ports
I/O enclosure 1
I/O enclosure 2
Loop 1
I/O enclosure 5
I/O enclosure 6
Eight enclosures is the maximum number for a model 922.
More enclosures need more RIO-G ports.
To get more RIO-G ports we need more processor complexes.
Student Notebook
Figure B-7. Model 9A2 Four I/O Enclosures SS481.0
Notes:
The DS8000 model 9A2 supports two RIO-G loop with two I/O enclosures attached, but the
LPAR capability of the 9A2 splits the bays and assigns two of them to each LPAR. This is
depicted by the colors in the slide above.
Model 9A2 Four I/O Enclosures
Server 0
EVEN LSSs
(two instances)
RIO-G ports
Server 1
ODD LSSs
(two instances)
RIO-G ports
I/O enclosure 0
I/O enclosure 3
I/O enclosure 2
I/O enclosure 1
Loop 0
Loop 1
Loop 1 belongs to SFI 2
The 9A2 is split into two storage facility images (SFIs).
Each SFI controls one RIO-G loop and all the enclosures and adapters on that loop.
Resources cannot be shared between SFIs.
!!! Opposite / 922
Different
Student Notebook
V3.1.0.1
AP
Figure B-8. Model 9A2 Eight I/O Enclosures SS481.0
Notes:
The DS8000 model 9A2 supports two RIO-G loops with either four I/O enclosures
attached, but the LPAR capability of the 9A2 splits the bays and assigns four of them to
each LPAR.
Model 9A2 Eight I/O Enclosures
Loop 0
RIO-G ports
RIO-G ports
I/O enclosure 3
I/O enclosure 2
Loop 1
I/O enclosure 7
I/O enclosure 6
Server 0
EVEN LSSs
(two instances)
Server 1
ODD LSSs
(two instances)
The 9A2 is split into two storage facility images (SFIs).
Each SFI controls one RIO-G loop and all the enclosures and adapters on that loop.
Resources cannot be shared between SFIs.
!!! Opposite / 922
Student Notebook
Figure B-9. Example Model 921 - Four DA Pairs: Plug Order SS481.0
Notes:
You can put 4 disk enclosures of 16 DDMs on each DA pair so that provides 8 x 16 DDMs
or 128 disks. That fills the 921 base frame. To attach more disks we need to have an
Expansion 92E frame and one or two more DA pairs in the four I/O enclosures.
Lets add the disk enclosure pairs one at a time. Can you predict where the next one will be
attached?
Server 0 Server 0
DA Pair
Server 1
I/O Enclosure 2
3 2
I/O Enclosure 2
3 2
I/O Enclosure 3
2 3
I/O Enclosure 3
2 3 2 3
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
DA pair 2 DA pair 2 DA pair 3 DA pair 3
I/O Enclosure 0
1 0
I/O Enclosure 0
1 0
I/O Enclosure 1
0 1
I/O Enclosure 1
0 1 0 1
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
0
15
0
15
Front Rear
0
15
0
15
0
15
0
15
00
15 15
0
15
0
15
00
15 15
Front Rear
DA pair 0 DA pair 0 DA pair 1 DA pair 1
Add Expansion Frame
Base Frame Full : 128 DDMs
Model 921 Full : 384 DDMs
RIO-G loop 0
Example - Model 921 - Four DA Pairs: Plug
Order
Student Notebook
Copyright IBM Corp. 2005 Appendix C. Checkpoint Solutions C-1
V3.1.0.1
AP
Appendix C. Checkpoint Solutions
Unit 1
1. False, the DS8000 uses Power5 processors.
2. True, the LPAR function is a feature of the Power5 processor and
the Model 922 can be split into two LPARs.
3. True, the RIO-G bays are a high bandwidth I/O enclosure which
connect hosts and backend storage the processor complex.
4. D, all of the above
5. True, the DS8000 Storage Manager supports offline configuration.
Unit 2
1. C, the disk groups are called array sites in the DS8000.
2. True, the rank define the disk format of CKD or FB.
3. False, the extent pool defines the server affinity and pools the
ranks into groups for logical volume definition.
4. True, users should define one extent pool for each server.
Unit 3
1. True, the DSCLI is an installable package for host servers.
2. False, the DSCLI must access the DS6000 or DS8000 HMC to
perform its functions.
3. False, the DSCLI is an installable package for the DS6000 or
DS80000, it manages the hardware real-time and has no off-line
capability. It does not allow XML files to be imported or exported.
4. True, the DSCLI is the primary Copy Services interface for the
DS6000 or DS8000
5. True, the DSCLI can be used to configure either a DS6000 or
DS8000.
Unit 4
1. True, the DS6000 uses PowerPC 2-way processors.
2. False, the LPAR function is a feature of the Power5 processor in
the DS8000 but not the DS6000. The Model 511 cannot be split
into LPARs.
Student Notebook
C-2 DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
connect hosts and backend storage the processor complex.
4. D, all of the above
5. True, the DS6000 Storage Manager supports offline configuration.
Unit 5
1. True, the DS6000 uses PowerPC 2-way processors.
2. False, the LPAR function is a feature of the Power5 processor in
the DS8000, but not the DS6000. The Model 511 cannot be split
into LPARs.
connect hosts and backend storage.
Unit 6
1. False, the DS8000 GUI can be accessed with a Web browser.
2. True, the DS8000 Storage Manager has a Real-Time and an
off-line GUI interface.
3. True, the DS8000 Storage Manager can Export XML file which can
also be downloaded and applied to the real hardware
configuration.
4. False, there is also a Command Line Interface.
5. False, the DS6000 has it's won separate DS6000 Storage
Manager software package.
Unit 7
1. True, PDCU is a subset of the TPC for disk and can be used as a
raw data collection tool for the DS products until TPC for disk
supports the DS products.
2. False, the PDCU only supports a CLI.
3. True, Excel Macros are to be provided for use with PDCU.
4. True, Excel Macros identify most active or highest rate of access
and would be useful in identifying problems.
Unit 8
1. True, the DS8000 supports all of the Copy Services functions
Student Notebook
Copyright IBM Corp. 2005 Appendix C. Checkpoint Solutions C-3
V3.1.0.1
AP
2. True, the DS8000 and ESS support compatible Remote Mirror
functions and can operate as primary or secondary subsystems in
the Metro Mirror Copy.
3. False, the DS6000 does not support ESCON interfaces.
4. True, the DSCLI is the primary Copy Services interface for the
DS6000 or DS8000
5. False, the DS8000 Storage Manager can only execute single shot
Copy Services functions.
Unit 9
1. True, the pSeries systems requires the IBM 2107 fileset prior to
accessing LUNs on these systems.
2. True, the pSeries systems may choose to use the MPIO driver
instead of SDD.
3. True, the DS8000 provides SDD for multipath operation and
support the DS6000, DS8000, SVC, and ESS systems.
4. True, the SDD driver is not required if other multipath drivers are in
place.
Student Notebook
C-4 DS8000 and DS6000 for Open Systems Copyright IBM Corp. 2005
V3.1.0.1
backpg
Back page

Ss 481 Stud

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ss 481 Stud

Загружено:

Авторское право:

Доступные форматы

IBM TotalStorage DS8000

and DS6000 Implementation

4-way P5 570 Server

Exp Enclosure 1 Exp Enclosure 3

Exp Enclosure 1 Exp Enclosure 3

Server Enclosure (146 GB)

Exp Enclosure 1 (146 GB) Exp Enclosure 3 (300 GB)

Server Enclosure (146 GB)

Exp Enclosure 1 (146 GB) Exp Enclosure 3 (73 GB)

2-way P5 570 Server

2-way P5 570 Server

Storage Facility Image 1

Вам также может понравиться