DS8000 Implemetation Workshop

IBM STG Lab Service Storage, GCG
DS8000 Implementation Workshop
Instructor: Yan Ting
1 2014 IBM Corporation

Lesson Overview
This course gives an overview of IBM DS8000 concepts and architecture, introduces
the features and advanced functions of the IBM DS8000 seriestaking the latest
Description
model of DS8870 storage system as example , for students to better understand the
Implementation of DS8000 logical configuration and advanced function.
After completing this course, you should be able to:
Describe the DS8000 hardware components and architecture
Describe the virtualization concept of DS8000
Objective
Use DS CLI and DS Storage Manager GUI to configure DS8000
Assess usage scenarios for DS8000 Easy Tier
Assess usage scenarios for DS8000 Flash Copy
Assess usage scenarios for DS8000 Remote Mirror
Individuals who are interesting in DS8000 or planning to implement DS8000

Audience
configuration or advanced functions.

Agenda
Day 1 (9:00 - 17:00) Day 3 (9:00 - 12:00)

DS8000 overview and DS8870 introduce Copy Services Concept
DS8000 Architecture and Hardware Flash Copy Overview
DS8000 RAS Flash Copy Example
DS8000 Virtualization Concepts Metro Mirror Overview
Metro Mirror Operation examples
Day 2 (9:00 - 17:00) Global Mirror Overview
DS8000 Logical Configuration planning DS8000 Monitoring With TPC 5.2
DS8000 Configuration-GUI
DS8000 Configuration-Command Line
DS8000 DSCLI Logical Configuration Examples
Easy Tier Introduction and Implementation
Easy Tier example

Chapter 1:
DS8000 overview and DS8870 introduce

1.1 Positioning the IBM System Storage DS family

1.2 IBM DS8000 for open systems

1.3 5th-generation DS8000 enterprise disk system
Building on a market-proven, reliable code base!
94% of the same proven microcode
2004 2006 2009 2010 2012 2014
POWER5 POWER5+ POWER6 POWER6+ POWER7 POWER7+
DS8300 DS8700 DS8800 DS8870 DS8870

DS8300
Turbo

1.4 DS8000 Enterprise Disk Systems Hardware Evolution
DS81/8300 DS8700 DS8800 DS8870
Disk: FC FC SAS SAS
Power: Bulk Bulk Bulk DC-UPS
CEC: p5/p5 p6 p6+ p7(p7+)
IO Bay: RIOG PCIE PCIE PCIE
Incremental changes between versions maximizes quality

1.5 DS8000 Functional Summary by Release
Note: not all enhancements are included 4-2010 5-2011 4-2012
Easy Tier Easy Tier2 Encryption for
2004 10-2006 Thin Provisioning IO Priority SSD and NL-SAS
255 LCUs Supported HyperPAV 10-2008 Quick Init Manager (open) Easy Tier4
RAID5/RAID10 HMC CIM Agent zHPF 600GB 15K Resource 400GB SSD
RMC/zGM/PTC/PAV Enterprise Choice zMGM Incremental 2TB nearline SATA Groups Thin
7-2009
64K Logical Volumes (extended) warranty Resync Multiple GM sessions New GUI Provisioning for
2-2008 Thin Provisioning
2GB FCP/FICON 16TB LUN all copy services
DS8000 M/T intermix Quick init
73/146/300GB DDs New Business
Extended Distance zHPF Multi-track
Class option
FICON support
1.0 2.0 2.4 3.0 3.1 4.0 4.1 4.2 4.3 5.0 5.1 6.0 6.1 6.2 6.3 7.0
2006 11-2011 11-2012

2007 5-2008 10-2009 10-2010
Turbo Models with 3TB nearline SAS DS8870 with
SSPC Support (new) Extended Address 2-2009 DS8700 with DS8800
Power5+ Addl expansion Power 7
Storage Pool Striping Volumes Solid State Drives Power6 controller Power6+
500GB FATA nearline frame and 1,536 controller
Space Efficient Variable LPAR 1 TB SATA PCI-E internal All 2.5 SAS-2
4GB FCP/FICON drives Increased
FlashCopy IPv6 Intelligent Write fabric drives
Flexible Warranties Easy Tier3 Cache / NVS
Dynamic Volume Cache Increased 8GB HA and DA
(242x) I/O Priority Manager All FDE drives
Expansion Full Disk Encryption Cache/NVS
zOS Synergy Items (CKD) RoHS 2014
3rd & 4th expansion (FDE)
zHPF QSAM BSAM Energy savings
frames Remote pair
BPAM
FlashCopy
1 TB EAV
DB2 list pre-fetch
DS8100 / DS8300 includes all functional enhancements up to R4.3 optimizer
DS8700 / DS8800 include all functional enhancements up to R6.2

1.7 Performance Improvements with Power 7
DS8300 DS8700 DS8800 DS8870 (R7) Increase Increase Increase

(R4.3) (R5) (R6) P7 16-core vs. vs. vs.
P5+ 4-core P6 4-core P6+ 4-core DS8300 DS8700 DS8800
Seq. Read (GB/s) 3.9 9.7 11.8 21.0 5.4x 2.2x 1.8x
Seq. Write (GB/s) 2.2 4.7 6.7 11.0 5.0x 2.3x 1.6x
DB z/OS (K IOPS) 165 201 204 640 3.9x 3.2x 3.1x
DB Open (K IOPS) 165 191 198 550 3.3x 2.9x 2.8x
DS8300 DS8870
Turbo

1.8 DS8870 Processor Configurations
Total System
Active Processor Total Active Expansion
Processor Feature Code Memory /
System Class Configuration per Cores per Frames
Cards per CEC Persistent
CEC DS8870 Supported
16 GB/1 GB
Business Class 2 cores 1 x 4 core #4401 4 cores None
32 GB/1 GB
4 cores 1 x 4 core #4402 8 cores 64 GB/2 GB None
128 GB/4 GB 02
8 cores 2 x 4 core #4403 16 cores
Enterprise Class The DS8870 is available in the following options: 256 GB/8 GB 03
DS8870 Model 961 Enterprise (standard) Class 512 GB/16 GB 03
16 cores 2 x 8 core #4404 32 cores
1024 GB /32 GB 03

1.9 DS8870 Business Class and Enterprise Class Configuration Options
Model Processors Physical Capacity Disk Drives System Host Adapters 9xE Attach
per CEC (max.) (max.) Memory (max.)
Business Class
961 2-core 216 TB 144 16/32 4 0
Enterprise Class
961 4-core 360 TB 240 64 8 0

961 8-core 2,304 TB 1536 128/256 16 0-3
961 16-core 2,304 TB 1536 512/1024 16 0-3
First Expansion Frame
96E N/A 504 TB 336 N/A 8 N/A
Second/Third Expansion Frame
96E N/A 720 TB 480 N/A N/A N/A

1.10 DS8870 maximum configuration option of four frames
DS8870 models 961/96E maximum configuration with 1536 drives

Chapter 2:
DS8000 Architecture and Hardware

2.1 DS8000 Model 961 Overview
Disk Enclosures
Hardware Management Console
POWER7+ processor-based servers
I/O Enclosures
Direct Current Uninterruptible Power

Supply(DC-UPS) power supplies e I/O enclosures
Rack Power Control (RPC) adapters

2.2 DS8000 Hardware Architecture
Three-Tier Cooperative Processing Architecture
Max 128 Ports
Front-End Host Host Host Host Host Host

Adapters Adapters Adapters Adapters Adapters Adapters
Max 16-way,
512G Cache per CEC
High Bandwidth, Fault Tolerant Interconnect
Enterprise N-way Cache memory N-way
Cache memory
Controller SMP SMP
Hardware Persistent memory Persistent memory
Back-End
RAID RAID
Adapters Adapters
Max 8 x DA Pairs

2.3 Disk Drives
The DS8870 supports the following disk types:

SAS Enterprise disks (all disks that are spinning at 15 K or 10 K rpm)
SAS solid-state (SSD) flash disks (all flash memory with no moving parts)
SAS Nearline disks (all disks thatare spinning at 7200 rpm)

2.4 Storage enclosure
Each disk is an industry-standard serial-

attached SCSI (SAS) disk. The disks
can be the following 2.5-inch Small
Form Factor or 3.5-inch Large Form
Factor disks:
SFF disks: This size allows 24 disk
drives to be installed in each storage
enclosure
LFF disks: This size allows 12 disk
drives to be installed in each storage
enclosure

2.5 Storage facility processor complex
Consists of two Power 7(7+) servers(CEC: central

electronics complex)
Available with dual 2-core, dual 4-core, dual 8-core,
or dual 16-core processors
Uses the PCIe paths through the I/O enclosures to
provide a communication path between the CECs

2.6 DS8000 I/O Enclosure
DS8000 support maximum 8 I/O enclosures
Each enclosure has 4 slots to plug 2xHA(slot 1,4) and 2xDA(slot 3,6)

2.7 Host Adapters
DS8000 supports up to two FC or FICON HAs per

I/O enclosure
Four or eight ports and support 2-Gbps, 4-Gbps, or 8-
Gbps full-duplex data transfer
Contains a maximum of 64 host adapter ports for

single rack
Up to 128 host adapter ports with first expansion rack

DS8800 and DS8870 Base Frame Host I/O Port Assignments (4 I/O Enclosures)
(Rear View)
C1 C2 C3 C4 C5 C6 C1 C2 C3 C4 C5 C6
Port 0 (T0) I0000 000 I0030 030 I0100 080 I0130 0B0
Port 1 (T1) I0001 004 I0031 034 I0101 084 I0131 0B4
Port 2 (T2) I0002 008 I0032 038 I0102 088 I0132 0B8
Port 3 (T3) I0003 00C Device I0033 03C Device I0103 08C Device I0133 0BC Device
Port 4 (T4) I0004 400 Adapter I0034 430 Adapter I0104 480 Adapter I0134 4B0 Adapter
Port 5 (T5) I0005 404 I0035 434 I0105 484 I0135 4B4
Port 6 (T6) I0006 408 I0036 438 I0106 488 I0136 4B8
Port 7 (T7) I0007 40C I0037 43C I0107 48C I0137 4BC
Slot 0 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 0 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5
Enclosure 0 (XI1) Enclosure 1 (XI2)

Install (4a) (2a) (2b) (4b)
Sequence (3a) (1a) (1b) (3b)
C1 C2 C3 C4 C5 C6 C1 C2 C3 C4 C5 C6
Port 0 (T0) I0200 100 I0230 130 I0300 180 I0330 1B0
Port 1 (T1) I0201 104 I0231 134 I0301 184 I0331 1B4
Port 2 (T2) I0202 108 I0232 138 I0302 188 I0332 1B8
I0204 500 Adapter I0234 530 Adapter I0304 580 Adapter I0334 5B0 Adapter
Port 4 (T4)
Port 5 (T5) I0205 504 I0235 534 I0305 584 I0335 5B4
Port 6 (T6) I0206 508 I0236 538 I0306 588 I0336 5B8
Port 7 (T7) I0207 50C I0237 53C I0307 58C I0337 5BC

WWPN shown in Yellow RACK 1 (BASE FRAME)
Note: The DS8800/DS8870 supports both 4 port and 8 port host adapter cards. Four port cards include only the first 4 ports (Ixx04-Ixx07 do not exist).
22
2014 IBM Corporation
22
DS8800 and DS8870 Expansion Frame Host I/O Port Assignments
(Rear View)
C1 C2 C3 C4 C5 C6 C1 C2 C3 C4 C5 C6
Port 0 (T0) I0400 200 I0430 230 I0500 280 I0530 2B0
Port 1 (T1) I0401 204 I0431 234 I0501 284 I0531 2B4
Port 2 (T2) I0402 208 I0432 238 I0502 288 I0532 2B8
Port 4 (T4) I0404 600 Adapter I0434 630 Adapter I0504 680 Adapter I0534 6B0 Adapter
Port 5 (T5) I0405 604 I0435 634 I0505 684 I0535 6B4
Port 6 (T6) I0406 608 I0436 638 I0506 688 I0536 6B8
Port 7 (T7) I0407 60C I0437 63C I0507 68C I0537 6BC

Install (4a) (2a) (2b) (4b)
Sequence (3a) (1a) (1b) (3b)
C1 C2 C3 C4 C5 C6 C1 C2 C3 C4 C5 C6
Port 0 (T0) I0600 300 I0630 330 I0700 380 I0730 3B0
Port 1 (T1) I0601 304 I0631 334 I0701 384 I0731 3B4
Port 2 (T2) I0602 308 I0632 338 I0702 388 I0732 3B8
I0604 700 Adapter I0634 730 Adapter I0704 780 Adapter I0734 7B0 Adapter
Port 4 (T4)
Port 5 (T5) I0605 704 I0635 734 I0705 784 I0735 7B4
Port 6 (T6) I0606 708 I0636 738 I0706 788 I0736 7B8
Port 7 (T7) I0607 70C I0637 73C I0707 78C I0737 7BC

WWPN shown in Yellow RACK 2 (EXPANSION FRAME)
Note: The DS8800 and DS8870 supports both 4 port and 8 port host adapter cards. Four port cards include only the first 4 ports (Ixx04-Ixx07 do not exist).
23
23
2.8 Device Adapters IO Bay
DA DA
IO Bay
DA DA
HA HA HA
Device adapters connect the I/O
2L
2L
2R
2R
1R 1L
enclosures in the processors to the disk
1R 1L
drives
Device adapters perform all RAID
functions and rebuilds in the event of a
drive failure
Device Adapters are configured in
active/active pairs that provide redundant Gigapack Gigapack
access to drives
IC Card
IC Card
IC Card
IC Card

RAID levels supported by these device
adapters include RAID-5, RAID-6 and
RAID-10
Gigapack Gigapack
Allow for two concurrent read operations
IC Card
IC Card
IC Card
IC Card

and two concurrent write operations at the
same time
Device adapters on DS8800 are 8
Gigapack Gigapack
Gb/second Fibre Channel
IC Card
IC Card
IC Card
IC Card

Gigapack Gigapack
IC Card
IC Card
IC Card
IC Card

2.8 Storage Enclosure to DA-Pair Relationships
240 drives 336 drives 480 drives 480 drives DA

2a2 7a2 3a3 5a4 Interface
2b2 7b2 3b3 5b4
1a1 4a2 0a3 1a4
1b1 4b2 0b3
3a1 6a2 1b4
2a3 3a4
3b1 6b2 2b3
0a1 5a1 3b4
7a3 0a4
0b1 5b1 7b3
2a1 7a1 0b4
4a3 2a4
2b1 7b1 4b3
4a1 2b4
6a3 7a4
4b1 6b3
6a1 7b4
5a2 4a4
6b1 5b2 4b4
1a2 6a4
1b2 6b4
3a2 5a3
3b2 5b3
0a2 1a3
0b2 1b3
B A

2.9 Switched Fiber Channel Arbitrated Loop (FC-AL)
The DS8870 architecture uses dual redundant switched FC-AL access to
each of the storage enclosures. This configuration features the following key
benefits:
Two independent switched FC-AL networks provide high performance
connections to disk
Four access paths are available to each DDM
Each DA port operates independently
Double the bandwidth over traditional FC-AL loop implementations

2.10 Arrays across loops (1 of 2)

2.10 Arrays across loops (2 of 2)
AAL is used to increase performance
RAID 5, it sends half of the write to each switched loop.
RAID 10two RAID 0 arrays are created. When servicing read I/O, half of the reads
can be sent to each loop

2.11 DS8000 HMC
The DS8870 HMC provides the following management interfaces:
DS Storage Manager graphical user interface (GUI)
Data storage command-line interface (DS CLI)
DS Open application programming interface (DS Open API)
Web-based user interface (WebUI)

2.12 Management Console Network
Each processor complex

includes connections to each
switch to allow each server to
access both private networks.

2.13 Management Console Network
Login HMC : User/Password: CE/serv1cece

Chapter 3:
DS8000 RAS (Reliability, Availability, Serviceability)

3.1 CEC RAS (1 of 2)
Data is written to cache memory in
the owning server.
Data is written to NVS memory of the
alternate server.
The write is reported to the attached
host as having been completed.
The write is destaged from the cache
memory to disk.
The write is discarded from the NVS
memory of the alternate server.

3.1 CEC RAS (2 of 2)
It destages the contents of its

NVS to the disk subsystem.
The NVS and cache of server
1 are divided in two, half for
the odd LSSs and half for the
even LSSs.
Server 1 now begins
processing the writes (and
reads) for all the LSSs.

3.3 Power loss and restored
When an on-battery condition shutdown begins, the following events occur:

1. All host adapter I/O is blocked.
2. Each CEC begins copying its NVS data to internal disk (not the storage DDMs).
3. When the copy process is complete, each CEC shuts down.
4. When shut down in each CEC is complete, the DS8000 is powered down.
After the DS8870 is powered on, the following events occur:

1. When the CECs power-on, PHYP loads and power-on self-test (POST) runs at this time.
2. Each CEC begins the IML(initial machine load ).
3. At an early stage in the IML process, the CEC detects NVS data on its internal disks
and begins to restore the data to destage it to the storage DDMs.
4. IML will pause for the battery units to reach a certain level of charge, the CECs come
online and begin to process host I/O. This prevents a subsequent loss of input power
resulting in a loss of data

3.4 Host connectivity: IBM SDD and MPIO
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 DS8000, SDD is supported on the following
operating systems:
Windows
NetWare
AIX
HP-UX
Sun Solaris
Linux
SDD can coexist with RDAC (DS4000 multipath
driver) on most operating systems as long they
manage separate HBAs.
SDD cannot be used with most other multipath
drivers (in other words, Veritas, PV-Links,
Powerpath)
MPIO 2.1.0 Path Control Module (PCM) is also supported for
AIX 5.2 ML5 (or later) and AIX 5.3 ML1(or later).
Warning: Default MPIO is not supported: sddpcm file sets are required.

3.5 Host connection availability (1 of 2)
Best practice for host connectivity :
hosts that access the DS8870 have at least two connections to host ports on
separate host adapters in separate I/O enclosures.

3.5 Host connection availability (2 of 2)
Each Volume is owned either CEC0 or CEC1

Host adapters on DS8000 can be access 1000 1100
by CECs concurrently
I/O to a volume can load balance between
HA ports, not between CECs

3.6 Data Flow between DA and Enclosures
Up to 4 Gigapacks can be supported per dual loop
Each DA Pairs can support 8 Gigapacks
8 DA Pairs can support 64 Gigapacks, 1,536 Drives
FC to SAS transformation is performed by FCIC
Gigapack Enclosures
8Gbps Fibre Channel Debug Ports

Interface Card 1 8Gbps Fibre Channel Debug Ports
Interface Card 1
Optical Connections Optical Connections
SFP SFP SFP SFP
8Gbps FC 8Gbps FC 8Gbps FC 8Gbps FC
SFP SFP
SFP
SFP
ASIC SFP
ASIC SFP
SFP Flash Flash

Device SFP Processor
SRAM
Processor
SRAM
6 Gbps SAS 6 Gbps SAS
Adapter AC/DC AC/DC
Power Supply Power Supply
SFP
SAS SAS ..24.. SAS SAS SAS SAS ..24.. SAS SAS
SFP AC/DC AC/DC
Device SFP
SFP
Power Supply Power Supply
Adapter 6 Gbps SAS
Processor
SRAM
Flash
6 Gbps SAS
Processor
SRAM
Flash
SFP
ASIC SFP SFP
ASIC SFP
8Gbps FC 8Gbps FC 8Gbps FC 8Gbps FC
SFP SFP SFP SFP
Debug Ports Interface Card 2 Debug Ports Interface Card 2

Chapter 4:
DS8000 Virtualization Concept

4.1 DS8000 Storage Hierarchy (1 of 2)
Disk
Individual DDMs
Array Sites(Sx)
Logical Grouping of 8 DDMs of same speed and
capacity
Array(Ax)
One 8-DDM Array Sites used to construct one RAID5, RAID5 or RAID-6 or RAID10
RAID-6 or RAID10 array
Ranks(Rx)
One Array becomes one CKD or FB Rank

CKD or FB
Available space in rank divided into extents
An extent is the minimum allocation unit when a LUN
or CKD volume is created (FB = 1GB, CKD = 1113
cylinders)
Extent Pools(Px)
1-N Ranks form an Extent Pool
Min of 2 pools1 each for server0 and server1 Extent
Max of 1 pool for each rank Pool
All Extents in a Pool are same storage type (CKD/FB);
same RAID recommended
Associated with server0 or server1

4.2 DS8000 Storage Hierarchy (2 of 2)

4.3 Array Site
Logical Grouping of disks 300G 300G 300G 300G
fixed 8 disks
same capacity and speed 300G 300G 300G 300G
across two enclosures and two loops(AAL)

DS8000 array site
Created after initialization, with installation
order, not DA
Associate with Array, affinity with DA pair

4.4 Creating an Array

44
4.5 Array
D D D D
Array is build on an Array Site D D P S
RAID5 RAID5 6+P+S
6+P
7+P D D D D
Parity is striped across all disks in array but consumes capacity
equivalent to one disk D D D P
RAID5 array performs better for sequential write RAID5 7+P
RAID 6 D D D P
6+P+Q D D D Q
5+P+Q+Spare RAID6 6+P+Q
RAID10 D D D S
3+3 D D P Q
4+4
RAID6 5+P+Q+S
RAID10 array performs better for random write
RAID5 and RAID10 arrays perform equally for read
D D D S
D D D S
Sparing RAID10 3+3+2S
Arrays without spares may mean better potential random
performance
Minimum of 4 spares per DA (64 or 128 disks) (single disk type) D D D D
D D D D
RAID10 4+4
4.6 Sparing example 1: DS8000 RAID 5 with all same capacity, and
same rpm

4.7 Sparing example 1: DS8000 RAID 10 with all arrays same capacity
and same rpm

4.8 Sparing example 3: DS8000 RAID 5 with first four arrays
146 GB and next two arrays 300 GB (same rpm)

4.9 Capacity Magic

4.10 RANK
Built on array, one-to-one relationship between an array and a rank
With CKD or FB storage type defined
Ranks are divided into extents
Units of space for volume creation
CKD rank
Extents equivalent to a 3390M1
1113 cylinders or .94GB
FB rank
1GB extents

4.11 DS8000 Logical Storage Status and Related Information
Get the status or information from CLI and GUI
Term Type State Usage Associate
Disk ddm nl normal unassigned dapair

ent not_normal unconfigured enclosure
ssd spare arsite
not_spare
array_member
ArraySite arraysite N/A assigned dapair
unassigned array
unavailable
initializing
Array array 5/6/10 normal assigned dapair
degraded unassigned rank
readonly unavailable
failed
repairing
inaccessible
Rank rank 5/6/10 normal extpool
normal
fb/ckd degraded
unassigned
readonly
reserved
failed
depopulating
repairing
configuring
inaccessible
unassignedreserved
depopulationerr
configerr
deconfiguring
deconfigerr
configpending
configpendingerr
Configoutofsyncerr

4.12 DS8000 Logical Storage Related CLI Command
Term of logical storage
List Create Change Show Delete
Disk lsddm N/A N/A N/A N/A
ArraySite lsarraysite N/A N/A showarraysite N/A
Array lsarray mkarray N/A showarray rmarray
Rank lsrank mkrank chrank showrank rmrank

4.13 Extent pool concept summary
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
An extent pool has a server affinity (server 0 or server 1)
But 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 Extent

Extent
Rank group 1 is controlled by server 1 Pool
Pool
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

Copyright IBM Corporation 2009
4.14 Device configuration: Extent
Multiple ranks allowed per extent pool
Extent pools
List of storage CKD FB CKD
extents 1GB each
Ranks
Choice between
FB and CKD
Arrays
Choice between RAID 5 RAID 5 RAID 10 RAID 5 RAID 5
Raid 5 or 10 10k rpm 10k rpm 15k rpm 15k rpm 15K rpm
Array Sites
4 disks from front
4 disks from back
Rank group 1
Rank group 0 associated associated with server 1
with server 0

4.15 Extent pools example in a mixed CKD and FB environment

4.16 Logical volume concept (1 of 4)
Made up of an ordered set of extents from one

extent pool
Min size: One extent : 1GB (FB) Mod 1(CKD)
Max size: 16TB (FB) 233GB (CKD)
Can span more than one rank if more than one rank in
pool
Max total number of volumes (CKD + FB)

DS8000: 65280 (64K-256)
Can be individually deleted

Extents
Will be assigned to volume group for LUN

mapping Extent Pools CKD FB
Ranks 73GB 10k 73GB 10k 146GB 10k

4.17 Logical volume concept (2 of 4):
RAID Array 0
Volume 2501 Extent 0
RAID Array 2
RAID Array 4
Extents striped across multiple RAID arrays

Improves volume throughput for many workloads
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
Dynamic expansion and online data relocation are available
Plan for virtual capacity over provisioning in future release
An LSS is a logical storage subsystem.

It is mainly used in copy services to stop all volumes for one
application in one command.
X Y AB
ADDRESS GROUP LSS Logical
(CKD or FB) Volumes
Max = 16 per
Max = 16 Address Group 0 to F Max = 256 / LSS
0 to F : 255 LSS 00 to FF
LSS
LSS X00, X02, X04, up to XFE even > Server 0
LSS LSS X01, X03, X05, up to XFD odd > Server 1
Max = 255
00 to FE

4.20 Logical Volumes
Fixed Block LUNs(Open/AS400)
Composed of one or more 1 GB extents from an extent pool
>LUNs cannot span multiple extent pools
>LUNs can have extents from different ranks within the same extent pool
>LUNs can online migrate between extent pools
>LUNs can have a maximum size of 16 TB(2T for CS)
Considerations
When creating FB LUNs, create LUNs that are a multiple of 1 GB to
avoid spatial waste
Volume ID
User specifies 4-digit hex volume ID which includes address group,
LCU/LSS and device ID:
xyzz
x=Address Group
xy=LCU/LSS
Even LCU/LSSs are available for Server0 extent pools
Odd LCU/LSSs are available for Server1 extent pools
zz=device ID
Volume size does not necessarily affect performance
Volume has three storage allocation methods
Standard, ESE, TSE

4.21 Standard Logical Volume (LV)
Standard LV consists of 1 to N Real Extents
Each Extent contains Extent Data and Extent
Metadata
Each LV Extent is mapped to a Real Extent on a
Real Rank
All Extents allocated to a LV come from one Extent
Pool
FB Extent = 1024 MB Extent Data
Less 4.5MB Extent Metadata
CKD Extent = 1113 Cylinders Extent Data
Less 64 cylinders Extent Metadata

4.22 Track Space Efficient Volume
TSE
Storage allocated in track(64 KB for open systems LUNs or 57 KB for CKD volumes) increments
Storage obtained from Repository
Repository uses extents obtained from extent pool
Intended to be used as FlashCopy targets

4.23 Extent Space Efficient Volume
ESE
Storage allocated in extent increments
Storage obtained directly from extent pool
Only FB volumes can be set up as ESE volumes
Support copy services, both of Volumes must be ESE form
Quick Initialization has a little performance degrade if sequential write i/o is intensity

4.24 Storage Pool Striping (aka Rotate Extents)
Storage Pool Striping is an algorithm choice for

volume creation which allows for better backend
disk utilization
Volumes are created by allocating one Extent
from available Ranks in an Extent Pool, in a
round-robin fashion
The next volume will be started from an extent on

the next rank in the round-robin rotation
Additional ranks can be added to the extent pool
as needed
Rebalance within homogeneous pool is support
with ET enable

4.25 Extent allocated Sequentially (aka Rotate volumes)
All extents are taken from the same rank until there are enough extents for the
requested volume size or the rank is full
If more than one volume is created in one operation, the allocation for each volume
starts in another rank
The rotate volume is not allowed if one extent pool is composed of SSD disks and
has a space efficient repository or virtual capacity configured

4.27 Double striping issue
It is possible to use striping methods on the host; for example, LVM or VDisk striping on SAN
Volume Controller. in a worst case scenario, all of these extents are on the same rank, which could
make this rank a hotspot.
While plan to double stripe,

the stripe size should be
different from the DS8000
extent size or identical to the
DS8000 extent size!

4.28 Logical subsystem (1 of 2)
Logical grouping of volumes

Max of 256 volumes in LSS Physical Drives
Logical Volumes
LSS configured as either FB or
CKD LSS X'17'
CKD: During LCU creation DB2
FB: During volume creation
x'1701'
Predetermined association with x'1702'
server 0 or server 1:
x'1703'
Even LSSs associated with server
0
Odd LSSs associated with server LSS X'18'
1 DB2-test
Determines addressing, x'1800'
address group, and PAVs x'1801'
Used for copy services PPRC
paths, and consistency group
properties/timeouts
4.28 Logical subsystem (2 of 2)
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)

.4.29 Address group
LSSs numbers are pre-grouped in to groups of 16 to make up an address group

LSS 00-0F, 10-1F, 20-2F, and so on
Entire address group (all 16 LSSs) will be either FB or CKD (at creation of first LCU or
volume)
Volume 1E01 belongs to LSS E of address group 1
69 Copyright IBM Corporation 2009
4.30 DS8000: Logical volume addressing
Address Logical Logical Logical

Group Volume Subsystem Device
Numbers Number Number
X'0' X'0000' - X'0FFF' X'00' - X'0F' X'00' - X'FF' ESCON
X'1' X'1000' - X'1FFF' X'10' - X'1F' X'00' - X'FF'
X'2' X'2000' - X'2FFF' X'20' - X'2F' X'00' - X'FF'
X'3' X'3000' - X'3FFF' X'30' - X'3F' X'00' - X'FF'
X'4' X'4000' - X'4FFF' X'40' - X'4F' X'00' - X'FF'
X'5' X'5000' - X'5FFF' X'50' - X'5F' X'00' - X'FF'
X'6' X'6000' - X'6FFF' X'60' - X'6F' X'00' - X'FF'
X'7' X'7000' - X'7FFF' X'70' - X'7F' X'00' - X'FF'
X'8' X'8000' - X'8FFF' X'80' - X'8F' X'00' - X'FF'
X'9' X'9000' - X'9FFF' X'90' - X'9F' X'00' - X'FF'
X'A' X'A000' - X'AFFF' X'A0' - X'AF' X'00' - X'FF'
X'B' X'B000' - X'BFFF' X'B0' - X'BF' X'00' - X'FF'
X'C' X'C000' - X'CFFF' X'C0' - X'CF' X'00' - X'FF'
X'D' X'D000' - X'DFFF' X'D0' - X'DF' X'00' - X'FF'
X'E' X'E000' - X'EFFF' X'E0' - X'EF' X'00' - X'FF'
X'F' X'F000' - X'FEFF' X'F0' - X'FE' X'00' - X'FF'
Note: Logical Subsystem X'FF' reserved for internal Storage Facility use

4.31 LSS and address group considerations
Address group assignment is not explicitly configured
LSSs are pre-grouped into address groups
One address group has 4096 addresses (for volumes)
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 will determine 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 all 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)

4.32 LSS options for Copy Services
Consistency groups based on LSS
Consistency group properties and timeouts specified by LSS
For FB LSSs, properties and timeouts are defined on path creation
(in GUI)
Flexible LSS formation (across ranks or extent pools) allows

consistency groups to be application-based

4.33 Hosts attachments
Multiple server ports can be specified (in one or more
groups) in one host definition System p1
Four host attachments are shown in example on
top
Two host attachments with two ports 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 System p1
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 System p1

4.34 Volume groups
Map LUNs to server ports or port groups

FB LUN masking
LUN masking at volume group 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

4.35 Volume groups and host attachment (1 of 2)
Host attachment Host attachment

Server A Server A
5
4 6
Volume Group X Volume Group Y Volume Group X
1 3 4 6 1 3
2 5 2
Specific host attachment can be in only one volume group

4.35 Volume groups and host attachment (2 of 2)
Host attachment Host attachment Host attachment Host attachment

Server A Server B Server A Server B
Volume Group X Volume Group Y Volume Group X

OR
1 3 1 3 1 3
2 2 2
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
4.36 Volume groups: Host is one WWPN
Host System A Host System B Host System C

Host Attachment Host Attachment Host Attachment Host Attachment
WWPN WWPN WWPN WWPN WWPN WWPN WWPN WWPN
It is possible to have
several Host Attachments
associated to one Volume
Group.
But we do recommend,
1 4 5 7 For management
to associate only one Host
attachment to each Volume
Group
2 3 6 8
Volume Group 1 Volume Group 2 Volume Group 3

4.37 Volume Groups and Hosts
Volume Group is responsible for grouping volumes in one unit

Volume can be associated with multiple volume groups as needed to support
application requirements
Common to share volumes among clustered servers
A host is defined by its world-wide port name (WWPN), multiple hosts in a cluster can
be managed by the same portgrp number for flexible management
Hosts must contain at least one WWPN and many servers attached to DS8000s have
multiple hosts
Multiple host ports are balanced using MPIO, SDDPCM or other 3rd multipath
software.
Volumes are assigned to the host by connecting the volume group to the host
Example:
Name ID WWPN HostType Profile portgrp volgrpID ESSIOport
=====================================================================================================
p740p1 0000 10000000C9D58D0C pSeries IBM pSeries - AIX 0 V0 all

4.38 Example Host Attachment & Volume Groups
Example 1:
Hosts using the same shared WWPN-1 WWPN-2
WWPN-1 WWPN-2
LUNs in a cluster.
Host: Volume Group:DBVG
Host:
Prod1 Prod2
Example 2:
A portion of LUNs are shared.
Others are used as dedicated.
WWPN-3 WWPN-4 Volume Group:

FSVG
WWPN-1 WWPN-2 WWPN-1 WWPN-2

Shared LUNs
Host: Host:
Prod1 Prod2
Volume Group: Volume Group:
DBVG1 DBVG2

4.39 DS8000 Volumes and Mapping Related CLI Command
Term of Logical Components
List Create Change Manage Show Delete
Volume lsfbvol mkfbvol chfbvol managefbvol showfbvol rmfbvol

lsckdvol mkckdvol chckdvol manageckdvol showckdvol rmckdvol
Extpool lsextpool mkextpool chextpool N/A showextpool rmextpool
Volgrp lsvolgrp mkvolgrp chvolgrp N/A showvolgrp rmvolgrp
Hostconnect lshostconnect mkhostconnect chhostconnect managehostconnect N/A rmhostconnect

lsportprof

4.40 Benefits of Storage Virtualization
Extent pools used to create FB and CKD volumes

Virtualization provides the capability to
Enable storage pool striping
Dynamically add and remove volumes
Dynamic volume expansion
Dynamic extent pool merging using Easy Tier
Dynamic volume relocation using Easy Tier
Dynamically rebalance hot spots within homogeneous pools
Thin provisioning
Allocations from extent pool in 1 GB increments
Reclaim unused space with host support *

*DS8870 with Symantec SF will support unused space reclamation

4.41 Virtualization hierarchy summary

Chapter 5:
DS8000 Logical Configuration Planning

5.1 Information collection
Application information collection
Application type?
Capacity?
Striped in application level?
Performance?
OS information collection
OS type and level?
Multipath software and version?
HBA ?
Striped in file system level?
LUN information collection
Size?
Shared?
Type?
SAN environment information collection

5.2 DS8000 Configuration guideline ( 1 of 2)
Following general guidelines when storage is configured in DS8000:
To achieve a well-balanced load distribution, use at least two extent pools.
The first volume in an address group determines the type of the address group (all CKD
or all FB).
Volumes of one LCU/LSS can be allocated on multiple extent pools.
An extent pool should contain only ranks with similar characteristics (for example,
Redundant Array of Independent Disks( (RAID) level, disk type). Exceptions apply to
hybrid pools.
Ranks in one extent pool should belong to separate device adapters (DAs).
Assign multiple ranks to extent pools to take advantage of Storage Pool Striping.

5.2 DS8000 Configuration guideline (2 of 2)
FB:
Create a volume group for each server unless logical unit number (LUN) sharing is
required.
Assign the volume group for one server to all its host connections.
If LUN sharing is required, the following options are available
Create one volume group for each server. The advantage of this option is that you can
assign private and shared volumes to a host.
Create one common volume group for all servers. Place the shared volumes in the
volume group and assign it to the host connections.
I/O ports:
Distribute host connections of each type (FICON and FCP) evenly across the I/O
enclosure.
A port can be configured to be FICON or Fibre Channel Protocol (FCP).
Ensure that each host is connected to at least two different host adapters in two
different I/O enclosures for redundancy.

5.3 Obtaining activation codes (1 of 2)
At a computer with an Internet connection and a browser,
connect to the IBM Disk storage feature activation (DSFA)
Web site at http://www.ibm.com/storage/dsfa.

5.3 Obtaining activation codes (2 of 2)

5.4 Manage activations

5.5 Importing activation codes

5.6 Applying activation codes (1 of 2)

5.6 Applying activation codes (2 of 2)

5.7 DS8000 Configuration flow
Install license
Create arrays Create ranks
keys
Create Create a
Create volumes extpool,assign repository for
for open ranks to extent Space Efficient
systems pool volumes
Create volume
Create host
group,assign Configure I/O
connections for
volumes to ports open systems
volume group

Chapter 6:
Configuration by using the DS Storage Manager GUI

6.1 Accessing the DS GUI
You can access the DS GUI

in any of the following ways:
From a browser that is
connected to the HMC
From Tivoli Storage
Productivity Center on a
workstation that is connected
to the HMC
From a browser that is
connected to Tivoli Storage
Productivity Center on any
server
By using Microsoft
Windows Remote Desktop

6.2 the DS GUI through LDAP Authentication
Tivoli Storage Productivity Center connects to two HMCs that are managing two
DS8000 storage complexes.

6.3 Accessing the DS GUI directly through a browser
To connect to the DS Storage Manager GUI, enter the following URL in a supported
browser:
https://<HMC-IP>:8452/DS8000
Supported browser:
Mozilla Firefox 17 ESR
Microsoft Internet Explorer 9

6.4 DS GUI Overview window

6.5 GUI window layout

6.6 DS GUI navigation pane
Home:
Getting Started
System Status
Monitor:
Tasks
Pools:
Internal Storage
Volumes:
FB Volumes
Volume Groups
Count key data (CKD) logical
control units (LCUs) and Volume
Hosts:
Hosts
Copy Services:
FlashCopy
Metro Mirror/Global Copy
Global Mirror
Mirroring Connectivity
Access:
Users
Remote Authentication
Resource Groups
Configuration:
Encryption Key Servers
Encryption Groups
6.7 User management for the DS GUI (1 of 2)

6.8 User management for the DS GUI (2 of 2)
Add User (the DS CLI equivalent is mkuser)

Modify User (the DS CLI equivalent is chuser)
Lock or Unlock User: The choice toggles (the DS CLI equivalent is chuser)
Delete User (the DS CLI equivalent is rmuser)
Password Settings (the DS CLI equivalent is chpass)

6.9 Defining a storage complex (1 of 2)
In the navigation pane of the DS GUI, hover over Home and click System Status.
The System Status window opens

6.9 Defining a storage complex (2 of 2)
Enter the IP address of the HMC that belongs to the storage complex that you want to
add. Click OK to continue.

6.10 Creating arrays (1 of 4)
In the navigation pane, hover over Pools and click Internal Storage. The Internal
Storage window displays

Click the Array Sites tab to check the storage that is available to create the array
Click the Properties under the Action drop-down menu to check detail status of arraysite.

6.10 Creating arrays ( 3 of 4)
Click the Arrays tab in the Manage Internal Storage window and click Create Arrays in
the Action drop-down menu

After Clicked the OK, Create array verification window is displayed, Click
Create All once you decide to continue with the proposed configuration.

6.11 Creating ranks (1 of 2)
Click the Ranks tab to start working with ranks. Select Create Ranksfrom the Action drop-
down menu

6.11 Creating ranks (2 of 2)
Click OK to continueThe Create rank verification window is displayed
Click Create All after you decide to continue with the proposed configuration.

6.12 Creating extent pools 1 of 3)
Click Create Extent Pools from the Action drop-down menu

The Create New Extent Pools window opens:

Click OK to continueThe Create extent pool verification window is displayed
Click Create All after you decide to continue with the proposed configuration.

6.13 Configuring I/O ports (1 of 2)
1. Hover over the Home icon and select System Status. The System Status window opens.
2. Select the storage image for which you want to configure the ports and, from the
Action drop-down menu, click Storage Image -> Configure I/O ports

6.13 Configuring I/O ports (2 of 2)
3. The Configure I/O Ports window opens, you select the ports that you want to format
and then click the wanted port format (FcSf, FC-AL, or FICON) from the Action drop-
down menu

6.13 Configuring logical host systems (1 of 4)
1. Hover over Hosts and click Hosts. The Host connections summary open:

2. The resulting window guides you through the steps required to create a host
configuration, beginning with the Define Host Ports window

After the host entry is added into the table, you can manually add a description of
each host. After you enter the necessary information, click Next, The Map Host Ports to
a Volume Group window opens:
Click Next after you select the appropriate option

The Define I/O Ports window opens (If you select Map to an existing volume group)
After the I/O ports are defined, click Next. The Verification window opens,click Finish to create the host
system

6.14 Creating fixed block volumes ( 1 of 5)
1. Hover over Volumes and select FB Volumes. The FB Volumes summary window
opens,

2. If you have more than one storage image, you must select the appropriate image.
In the Tasks area at the bottom of the window, click Create new volumes

3. To ensure a balanced
configuration, select extent
pools in pairs (one from each
server). Click Next to continue.

4.Click OK to continue. The Create Volumes window opens, click Next to continue

You need to select how volumes will be assigned to an LSS. You can choose Automatic, Manual (Fill), or
Manual (Group):
Automatic means the system assigns the volumes to LSSs for you.
Manual (Fill) means the system fills the first LSS selected before filling the next one.
Manual (Group) means to select one or more LSSs to assign volume addresses to and the system will spread
the volumes across all the LSSs that are selected.
Click Finish.

6.15 Creating volume groups (1 of 2)
1. Point to Volumes and select Volume Groups. The Volume Groups window opens.
2. To create a volume group, select Create from the Action drop-down menu

6.15 Creating volume groups ( 2 of 2)
Click Nextto open the Verification window:

Chapter 7:
Configuration with the DS Command-Line Interface

7.1 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 (such as lsuser, lssi, lssu)
HMC/SMC passes some requests to storage (such as lsarray)

7.2 DSCLI installation main concern
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

7.3 Find DSCLI and verify the dependencies
Go to the IBM Web site dedicated to storage:

http://www-03.ibm.com/systems/storage/

7.4 Select the right DSCLI version

7.5 DSCLI installation wizard (1 of 5)





7.6 DSCLI documentation
Read this documentation!

7.7 Starting DSCLI
R2 Screen

7.8 DSCLI 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 file or username and password)
Password files
Encrypted userid and password
Generated with mkuser and managepwfile commands
Stored in /opt/ibm/dscli/security/<S-HMC IP>/<file_name>
Note: -cfg flag can be used with dscli command to invoke

profile other than default
7.9 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
Userid and password
Profile can point to password file (pwfile) containing encrypted userid and
password
Profile can point directly to username and password
Timeout for network interface client/server communication
Default is 420 seconds
Other values (see following slides)
If a profile is in use, flag values included on a command can be

used to override values from profile file
7.10 DSCLI profile file example
DS CLI Profile
# indicates a comment
#
#
# Management Console/Node IP Address(es)
# hmc1 and hmc2 are equivalent to -hmc1 and -hmc2 command options.
hmc1: 9.82.22.112
hmc2: 9.82.22.112
#
# Password filename
# The password file can be generated using mkuser command.
#
pwfile: rmmadmin
#
# Default tat Storage Image ID
# "devid" and "remotedevid" are equivalent to
# "-dev storage_image_ID" and "-remotedev storeage_image_ID" command options,
respectively.
devid: IBM.2107-7506571
#remotedevid: IBM.2107-AZ12341
#
# locale
# Default locale is based on user environment.
#locale: en
# Timeout value of client/server syncronous 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

7.11 Three ways to use DSCLI
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

7.12 DSCLI interactive mode
dscli command

7.13 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 files one line at a time
Script exits DSCLI at completion or on failure
Scripts use DSCLI profile file

7.14 DSCLI script mode, a sample (1 of 2)
############ dscli script ####################

#script name is
C:/easydscli/projects/MONTPELLIER/inventory.scr
#created 2008/3/5 8:32:2
############ dscli script ####################
ver -l
lsserver -l
lsddm -l -state not_normal IBM.2107-75BV321
lskey IBM.2107-75BV321
lsrank -l
lsfbvol -l
lshostconnect -l
lsvolgrp -l

7.14 DSCLI script mode, a sample (2 of 2)
dscli -script
C:/easydscli/projects/MONTPELLIER/inventory.scr
-cfg C:\Progra~1\IBM\dscli\profile\MOP_EDUC2.profile
Gives the full result in 15 seconds

Date/Time: May 28, 2008 11:07:49 AM PDT IBM DSCLI Version: 5.3.1.101
DSCLI 5.3.1.101
StorageManager 6.1.3.20071026.1
================Version=================
Storage Image LMC
==========================
IBM.2107-75BV321 5.3.1.104
Date/Time: May 28, 2008 11:07:54 AM PDT IBM DSCLI Version: 5.3.1.101
ID Image ID Image Name Power Control SFI State LIC Version OS Version
Bundle Version
============================================================================
=============
00 1 SF75BV320ESS01 0 online 5.3.1.104 - -
01 1 SF75BV320ESS11 0 online 5.3.1.104

7.15 Classic command names
To create : mkXYZ. mkfbvol
To display showXYZ showfbvol
To list lsXYZ lsfbvol
To change: chXYZ chfbvol
To delete rmXYZ rmfbvol

7.16 Flags, parameters, and targets
Flags modify the command

Flag parameters provide information that is required to
implement the command modification that is specified by a
flag.
For example here: extpool is the flag, and P1 is the
parameter. At the end of the command, 1100-110F is the
target.
mkfbvol -extpool P1 -type ds -cap 20 -name 'DB' 1100-110F
This command will create 16 volumes, 20 GB each with the

name DB
To get the full list of flags and parameters, type
mkfbvol -help
7.17 Command flag parameters
-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 userid
(username in profile file or pwfile)
-passwd password for userid
(password in profile file or pwfile)
-dev Storage Image ID
(devid in profile file)
-remotedev for Copy Services
(remotedevid in profile file)
-v verbose

7.18 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

7.19 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

7.20 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 errors:

helpmsg CMUN00018E
Help for DSCLI is also available in DS Storage Manager Information

Center
7.21 Initial configuration prerequisites
DS8000
Define users
Apply keys
Verify DS8000 hardware
Configure storage unit in the storage facility image (SFI)
Verify array site
Create arrays
Create ranks
Create pool
Create volume groups
Create volume
Create host connect with WWPN
Assign volume groups to host

7.22 DSCLI 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 GUI users are identical
CLI users are not S-HMC users

7.23 DSCLI user groups
Groups define allowed functions (same as for GUI)

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 (DS8000)
Monitor plus DS8000 service functions
admin
User may be in multiple groups
Separate groups by commas on mkuser, chuser

7.24 DSCLI (and GUI) logical configuration user group roles

7.25 DSCLI password rules
Initial passwords expire immediately

This applies to default userid (admin) as well as userids you create
You will be able to log on, but will get an authorized message as
soon as you try to issue a command
By default, 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
chpass -expire 365 -fail 0

7.26 Create users/list users
dscli mkuser -pw psa406coupe -group admin SS49Team2 -
cfg "C:\Program
Files\IBM\dscli\profile\MOP_EDUC2.profile"
Date/Time: September 15, 2008 8:57:43 AM PDT IBM DSCLI
Version: 5.3.1.101
CMUC00133I mkuser: User SS49Team2 successfully
created.
dscli lsuser -cfg "C:\Program

Date/Time: September 15, 2008 8:58:32 AM PDT IBM DSCLI
Version: 5.3.1.101
Name Group State
======================
SS49Team1 admin active
Team1 admin active
Team2 admin active

7.27 Chuser: Lock and unlock
dscli chuser -lock SS49Team2 -cfg "C:\Program

CMUC00134I chuser: User SS49Team2 successfully
modified.
dscli lsuser -cfg "C:\Program

Name Group State
======================
SS49Team2 admin locked
Team1 admin active
dscli chuser -unlock SS49Team2 -cfg "C:\P

CMUC00134I chuser: User SS49Team2 successfully
modified
7.28 Obtain machine serial number and signature
dscli lssi -l -cfg

C:\Progra~1\IBM\dscli\profile\MOP_EDUC2.profile
Date/Time: May 28, 2008 11:20:37 AM PDT IBM DSCLI
Name ID Storage Unit Model WWNN
State ESSNet Volume Group desc
=================================
- IBM.2107-75BV321 IBM.2107-75BV320 931
dscli showsi IBM.2107-75BV321 -cfg
Date/Time: May 28, 2008 11:22:37 AM PDT IBM DSCLI
-
desc -
ID IBM.2107-75BV321
Storage Unit IBM.2107-75BV320
Model 931
WWNN 5005076307FFC348
Signature 4f62-2d28-38d9-70a5

7.29 Steps to apply keys
Obtain 16-digit Feature Activation Code(s)

Use DSCLI to obtain:
Machine serial number
Last 7 digits of MTS field. Note: For DS8000, this is the storage unit ID,
ending in 0
Machine signature (all 16 digits)
Go to DSFA Web application
http://www.ibm.com/storage/dsfa
Create an xml file or manually write down keys
Apply keys
applykey - key xxxxxxxxx,yyyyyy,zzzzzz SFI
or
applykey - file storage image ID
-key
Keys separated by commas
-file
xml file containing keys, for example:
applykey -file C:\2107_75BV321.xml IBM.2107-75BV321
7.30 Verify your license keys before starting
dscli lskey IBM.2107-75BV321 -cfg
Date/Time: May 28, 2008 11:26:26 AM PDT IBM DSCLI Version:
5.3.1.101 DS: IBM.2107-75BV321
Activation Key Authorization Level (TB) Scope
============================================================
Global mirror (GM) 50.6 All
IBM FlashCopy SE 50.6 All
IBM HyperPAV On CKD
Metro mirror (MM) 50.6 All
Metro/Global mirror (MGM) 50.6 All
Operating environment (OEL) 50.6 All
Parallel access volumes (PAV) 50.6 CKD
Point in time copy (PTC) 50.6 All
RMZ Resync 50.6 CKD
Remote mirror for z/OS (RMZ) 50.6 CKD

7.31 DSCLI logical configuration commands
Connection configuration commands

I/O port, host connection
Storage configuration commands

Array site, array, rank, extent pool, LCU, LSS, volume, volume group,
address group

7.32 DSCLI Copy Services commands
DS CLI can be used to invoke:

FlashCopy
Peer-to-Peer Remote Copy (PPRC)
IBM System Storage Metro Mirror
Synchronous PPRC
IBM System Storage Global Copy
PPRC-XD
IBM System Storage Global Mirror
Asynchronous PPRC
IBM System Storage Metro Mirror - Global Copy
Cascading

7.34 Initial logical configuration steps
1. Create extent pools

2. Create arrays
3. Create ranks
4. Add ranks to extent pools
<<End of first step>>
1. Create FB volumes (creates LSS automatically)
2. Create FB volume groups and assign volumes
3. Configure I/O ports
4. Create open systems host connections and assign to FB
volume groups
5. Verify using lshostvol command

7.35 Why P2 is your pool ID
Previously, other pools were defined.

dscli lsextpool -l -cfg "C:\Programa Files\IBM\dscli\
profile\MOP_EDUC2"
Name ID stgtype rankgrp
=======================
Extpool_CKD0 P0 ckd 0
Extpool_CKD1 P1 ckd 1
ExtPool_Team4 P4 fb 0
P2 is the first available ID. P3 and the next one

will be P8
7.36 Creating extend pools
########################### dscli script ####################
#script name is
#C:/course_management/projects/MONTPELLIER/mkpool16R5.scr
#created 2008/2/14 13:15:36
########################### dscli script ####################
lsextpool -l
mkextpool -rankgrp 0 -stgtype fb pool0
mkextpool -rankgrp 0 -stgtype ckd pool14
mkextpool -rankgrp 1 -stgtype ckd pool15
lsextpool -l
7.37 Creating arrays
########################### dscli script ####################
#script name is
C:/course_management/projects/MONTPELLIER/mkarray16R5.scr
#created 2008/2/14 13:15:36
#script automatically generated
########################### dscli script ####################
lsarraysite
lsarray -l
mkarray -raidtype 5 -arsite S1 -wait
lsarray -l
7.38 Creating ranks
########################### dscli script ####################
#script name is
C:/course_management/projects/MONTPELLIER/mkrank16R5.scr
#created 2008/2/14 13:15:36
#script automatically generated
########################### dscli script ####################
lsarray -l
lsrank -l
mkrank -array A0 -stgtype fb -extpool P0 -wait
mkrank -array A14 -stgtype ckd -extpool P6 -wait
mkrank -array A15 -stgtype ckd -extpool P7 -wait
lsrank -l
7.39 Creating volumes
dscli lsrank -l -cfg "C:\Program Files\IBM\dscli\profile\MOP_EDUC2.profile"
Date/Time: May 28, 2008 12:05:45 PM PDT IBM DSCLI Version: 5.3.1.101 DS: IBM.2107-
75BV321
ID Group State datastate Array RAIDtype extpoolID e
R0 0 Normal Normal A0 5 P2
R2 0 Normal Normal A2 5 P2
dscli mkfbvol -extpool P2 -type ds -cap 20 -name 'courtox' --
-sam standard -eam rotateexts 8200-820A -cfg "C:\Program
Date/Time: May 28, 2008 12:09:30 PM PDT IBM DSCLI Version:
5.3.1.101 DS: IBM.2107-75BV321
CMUC00025I mkfbvol: FB volume 8200 successfully created.
CMUC00025I mkfbvol: FB volume 820A successfully created.
Date/Time: 05 28, 2008 12:09:53
Execution time : 25 Seconds.
7.40 Verify your volumes
dscli lsfbvol -lss 82 -cfg "C:\Program Files\IBM\dscli\profile\MOP_EDUC2.profile"
Date/Time: May 28, 2008 12:14:37 PM PDT IBM DSCLI Version: 5.3.1.101 DS: IBM.2107-75BV321
Name ID accstate datastate configstate deviceMTM datatype extpool cap (2^30B) cap (10^9B) cap
==============================================================================
courtox 8200 Online Normal Normal 2107-900 FB 512 P2 20.0 - 41943040
courtox 820A Online Normal Normal 2107-900 FB 512 P2 20.0 - 41943040
Date/Time: 05 28, 2008 12:14:43
Execution time : 7 Seconds.

7.41 Location of the extent of these volumes
dscli showfbvol -rank 8200 -cfg "C:\Program
Date/Time: May 28, 2008 12:16:37 PM PDT IBM DSCLI Version: 5.3.1.101 DS:
IBM.2107-75BV321
Name courtox
ID 8200
accstate Online
datastate Normal
configstate Normal
deviceMTM 2107-900
datatype FB 512
addrgrp 8
extpool P2
exts 20
captype DS
cap (2^30B) 20.0
cap (10^9B) -
cap (blocks) 41943040
volgrp -
ranks 2
dbexts 0
sam Standard
repcapalloc -
eam rotateexts
reqcap (blocks) 41943040
==============Rank extents==============
rank extents
============
R0 10
R2 10
172 Copyright IBM Corporation 2009 2014 IBM Corporation
7.42 Checkpoint
1. T/F. The DS8000 is a CLI interface that must be installed on a

customer workstation.
2. T/F. The DS8000 CLI can be run online or offline.
3. T/F. The DS8000 CLI can create configuration xml 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.

7.43 Checkpoint solutions
1. True. The DSCLI is an installable package.
2. False. The DSCLI must access the DS8000 S-HMC to perform its
functions.
3. False. The DSCLI is an installable package for the DS8000. It

manages the hardware real-time and has no offline 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.

Chapter 8:
Logical Configuration Examples

8.1 Examples
List DDMs
dscli> lsddm -dapair 0 IBM.2107-75TY901
ID DA Pair dkcap (10^9B) dkuse arsite State
===============================================================================
IBM.2107-D01-08XJS/R1-P1-D1 0 300.0 array member S3 Normal
IBM.2107-D01-08XJS/R1-P1-D15 0 300.0 spare required S3 Normal
IBM.2107-D01-092P5/R1-P1-D12 0 300.0 unconfigured S2 Failed
List Array Site

dscli> lsarraysite -l
arsite DA Pair dkcap (10^9B) diskrpm State Array diskclass encrypt
=========================================================================
S1 0 300.0 15000 Assigned A0 ENT unsupported
S69 6 146.0 65000 Assigned A68 SSD unsupported

8.2 Creating Array
Create Array
mkarray -dev storage_image_ID -raidtype [5 | 6 | 10] -arsite array_site
dscli> mkarray -raidtype 10 arsite S1
List Array
dscli> lsarray -l
Array State Data RAIDtype arsite Rank DA Pair DDMcap (10^9B) diskclass encrypt
=====================================================================================
A0 Assigned Normal 10 (4x2) S1 R0 0 300.0 ENT unsupported
A1 Assigned Normal 10 (3x2+2S) S2 R1 0 300.0 ENT unsupported
A72 Assigned Normal 5 (6+P+S) S74 R70 4 146.0 SSD unsupported

8.3 Creating Rank
Create Rank
mkrank -dev storage_image_ID -array array_id stgtype [fb | ckd] -extpool extpool_id
dscli> mkrank array a0 stgtype fb S1
List Rank
dscli>lsrank
ID Group State datastate Array RAIDtype extpoolID extpoolnam stgtype exts usedexts encryptgrp
=====================================================================================
R0 0 Normal Normal A0 10 P0 cmcc_archive fb 1054 30 -
Change Rank
dscli>chrank unassign extpool extpool_id
Show Rank
dscli> showrank r0
ID R0
Array A0
RAIDtype 10
extpoolID P0
extpoolnam cmcc_archive
-------->volumes on rank
volumes 7201
stgtype fb
exts 1054
usedexts 30
widearrays 1
nararrays 0
trksize 128
strpsize 512
strpesize 0
extsize 16384
migrating(in) 0
migrating(out) 0

8.4 Example of Creating Extpool and Volume
Create Extpool
dscli>mkextpool -rankgrp 0|1 -stgtype fb|ckd exttent_pool_name
List Extpool
dscli>lsextpool
Name ID stgtype rankgrp status availstor (2^30B) %allocated available reserved numvols
=====================================================================================
cmcc_archive P0 fb 0 below 1024 2 1024 0 1
Creating Volume
>mkfbvol [ { -t10dif|-os400 A01|A81|A02|A82|A04|A84|A05|A85|A06|A86|A07|A87 } ] -extpool extentpool_ID -cap
capacity -type blocks|ess|ds -name volume_name -volgrp volume_group_id -eam [rotatevols|rotateexts] -sam
[standard|tse|ese] Volume_ID
List Volume
>lsfbvol -datatype [512 | 512t | 520p | 520u] extpool extpool_id -lss lss_id volgrp volgrp_id eam [legacy |
rotatevols |rotateexts | managed] volume_id
dscli> lsfbvol
Name ID accstate datastate configstate deviceMTM datatype extpool cap (2^30B) cap (10^9B) cap (blocks)
=====================================================================================
DIF 0801 Online Normal Normal 2107-900 FB 512T P0 10.0 - 20971520
Vol 0600 Online Normal Normal 2107-900 FB 512 P6 50.0 - 104857600
S01 3209 Online Normal Normal 2107-A02 FB 520P P18 16.3 17.5 34275328

8.5 Example of Creating Volgrp
Create Volgrp
mkvolgrp -hosttype hostType -volume volume Volume_Group_Name
List Volgrp
dscli> lsvolgrp -l
Name ID Type
====================================================
DS8KPerf V0 SCSI Mask
I7202VG V1 OS400 Mask
Change Volgrp
chvolgrp -name new_Volume_Group_name -action [add|remove|replace] -volume volume _id
Volume_Group_ID
Show Volgrp
dscli> showvolgrp v16
Name Reclam_VG
ID V16
Type SCSI Mask
Vols 4000 4001 4002 4003 4004 4100 4101 4102 4103 4104

8.6 Example of Creating Hostconnect
List hosttype
dscli> lsportprof IBM.2107-75TY901
Profile AddrDiscovery LBS
==========================================================
IBM iSeries - OS/400 reportLUN 520
IBM pSeries - AIX reportLUN 512
IBM pSeries - AIX with Powerswap support reportLUN 512
San Volume Controller reportLUN 512
VMWare LUNPolling 512
HP - HP/UX reportLUN 512
Apple - OSX LUNPolling 512
IBM zSeries - zLinux reportLUN 512
SUN - Solaris LUNPolling 512
Intel - Linux RHEL LUNPolling 512
Intel - Windows 2008 LUNPolling 512
Create hostconnect
mkhostconnect wwpn wwpn volgrp volgrp_id -profile port_profile_name --ioport port_ID Host_name
List hostconnect
Name ID WWPN HostType Profile portgrp volgrpID ESSIOport
==========================================================================================
SVC_N1P3 0019 500507680110C441 SVC San Volume Controller 0 V8 all
TYF_FCS2 0021 C05076EA2D000EB0 zLinux IBM zSeries - zLinux 0 V17 all
Ora_fcs2 000C 10000000C9CC666E pSeries IBM pSeries - AIX 0 V4 all
PWRVMi 0064 C0507602773F002A iSeries IBM iSeries - OS/400 0 V35 all
VMware_H1 0025 10000000C9DD291F - VMWare 0 V14 all
zBX_FCS0 003A 21000024FF3891C4 LinuxRHEL Intel - Linux RHEL 0 V8 all

Chapter 9:
Easy Tier Introduction and Implementation

9.1 Overview
Easy Tier provides automatic volume management capabilities

Sub-volume drive tiering
Manual command based volume relocation
Automated drive utilization balancing to remove hot spots or populate new, empty ranks
Easy Tier provides

A command line interface and a GUI for setup and management
Storage Tier Advisor Tool (STAT) for I/O analysis and projected benefits
Easy Tier is a licensed advanced function for the DS8700/DS8800

No charge but you still have to order the feature and activate the license
Supported by all server platforms with no additional software or host configuration
No license is required to monitor and run STAT tool

9.2 Easy Tier Data Collection
Easy Tier regularly collects backend performance data for each extent on the
DS8000 every 5 minutes
Not host I/O
This activity is broken down by reads and writes & large I/O and small I/O for
the analysis code to evaluate which data should be moved
Large I/Os are those which are basically a full track in size
Easy Tier only considers the small I/O when looking at prioritizing the extents
to be moved.
Any tracks that are staged as full tracks in track mode for read misses
will therefore not be considered in this decision criteria.
Large I/Os are considered to evaluate whether ranks or device adapters may
become overloaded by moving extents to SSDs.

9.3 Easy Tier Versions
Easy Tier 1 (DS8700 R5.1)
Automated cross-tier performance management for SSD/HDD hybrid pools
Manual mode management support for dynamic extent pool merge and dynamic
volume relocation
Easy Tier 2 (DS8700/DS8800 R6.1)
Automated cross-tier performance or storage economics management for
hybrid pools with any 2 tiers (SSD/ENT, SSD/NL or ENT/NL)
Automated intra-tier performance management (auto-rebalance)
in hybrid pools
Manual mode management support for rank depopulation and optimized volume
restriping within non-managed pools (manual volume rebalance)
Easy Tier 3 (DS8700/DS8800 R6.2)
Automated cross-tier performance and storage economics management for hybrid
pools with 3 tiers (SSD/ENT/NL)
Automated intra-tier performance management in both hybrid (multi-tier) as well as
homogenous (single tier) pools (auto-rebalance)
Thin Provisioning support for Extent Space Efficient (ESE) Volumes
Easy Tier 4 (DS8700/DS8800 R6.3 / DS8870 R7.0)
Support for encryption capable environments
DS8800 and DS8870 has FDE capable SSD and nearline

9.4 Operating Modes
Easy Tier Automatic Mode

Promote/demote extents (sub-volume) within tiers of disk in same extent pool
Requires multitier or hybrid extent pool to promote/demote
Homogeneous pool rebalancing
Balances the load on the ranks within a given tier in an extent pool
Rebalance the workload when ranks (extents) are added to the extent pool
Easy Tier Manual Mode

Dynamic volume relocation
Dynamic extent pool merge
Rank depopulation
Restripe a volume within the same pool

9.6 Easy Tier - Data Relocation Options
Manual Mode (Volume Level) and Automatic Mode (Extent Level)
SSD Rank Pools Enterprise Pools Nearline Pools
Merged Pool
(Two or three tiers)
Manual Mode
Volume Based Data Relocation
Automatic Mode
Extent Level Data Relocation
Automatic extent level data relocation enabled in a Merged Extent Pool

9.6 Easy Tier Automatic Mode Promotion/Demotion
Mixed Technology Extent Pool
Higher Performance Tier Ranks

Logical Volume
Hot Extents
Extent Virtualization
Migrate Up
Cold Extents
Migrate Down
Lower Performance Tier Ranks

9.7 Auto Rebalance
Managed Extent Pool
Extents moved between ranks
of the same tier to balance
workload Enterprise Rank
Balances rank skew due to
Workload
Change in resources
Proactively avoids hot spots Cold Extents Hot Extents
Migrate Up
Eliminates need to manually Migrate Down
re-stripe extents
Begins after 6 hours by default Extents migrated to
balance workload
across ranks
1
2
Rank 1 Rank 2 Rank 3

Nearline Ranks

9.8 Disk Tiers
DS8700 DS8800 DS8870

Tier 0 Tier 0
Tier 0
Solid-state drives (SSD) Solid-state drives (SSD)
Solid-state drives (SSD)
73 GB 300 GB
400 GB
146 GB 400 GB
FDE drives
600 GB FDE drives
Tier 1 Tier 1
Tier 1
SAS Enterprise drives
Fibre Channel Enterprise SAS Enterprise drives
drives 146 GB/15K 146 GB/15K
146 GB/15K 300 GB/15K 300 GB/15K
600 GB/10K
450 GB/15K 600 GB/10K
900 GB/10K
600 GB/15K 900 GB/10K
FDE drives
FDE drives FDE drives
Tier 2 Tier 2 Tier 2
SATA nearline drives SAS nearline drives SAS nearline drives
3 TB/7.2K
2 TB/7.2K 3 TB/7.2K
FDE drives FDE drives

9.9 Easy Tier Auto Mode Extent Migration Types
Auto
Rebalance
Highest
SSD SSD SSD

Performance
Tier
RANK 1 RANK 2 RANK n Promote & Swap
SSD Auto Move hot data to higher performing tiers.
Warm Rebalance
Promote Swap
Demote
Warm Demote
Prevent performance overload of a tier.
Higher ENT HDD
ENT HDD ENT HDD
Performance
RANK 1 RANK 2 ... RANK n
Tier
ENT Cold Demote

Identify coldest data and move it to lower
Warm Cold
tier.
Promote Swap
Demote Demote
Auto-Rebalance
Lower
Re-distribute extents within a tier to
Performance
NL HDD RANK
1
NL HDD RANK
2 ...
NL HDD RANK
m
balance utilization across ranks for
Tier
maximum performance.
NL Move and swap capability
Auto Rebalance
Migrations only happen

between adjacent tiers

9.10 Easy Tier Manual Mode Overview
Easy Tier Manual Mode allows a user to perform the following actions:
Dynamic Volume Migration
User can change a logical volumes storage technology by dynamically
relocating between extent pools
User can change a logical volumes extent allocation algorithm (EAM)
(e.g. can re-rotate extents within the target extent pool)
Dynamic Extent Pool Merge
User can merge two existing extent pools without moving data
Consolidate extent pools with equivalent disks
Merge extent pools with to create a mixed technology extent pool for Automatic
Mode
Rank Depopulation
Storage Administrator can ask that a rank be removed from an extent pool
Automatic, non-disruptive and transparent to host access, the used extents will
be reallocated to other ranks in the pool and rank freed
Manual Volume Rebalance
Redistributes a volumes extents within a non-managed single-tier pool
Same pool and can change EAM

9.11 Dynamic Volume Relocation
Before Volume Migration
1004
Rank 0 Rank 2 Rank 4 Rank 10 Rank 12 Rank 14
Extent Pool 0 Extent Pool 10
managefbvol action migstart eam rotateexts p10 1004

After Volume Migration
1004

9.12 Dynamic Extent Pool Merge process
Before Extent Pool Merge
chextpool merge p10 p0

After Extent Pool Merge
Extent Pool 0

9.13 Rank Depopulation
Before Rank Depopulation
Extent Pool 0
chrank unassign r2
After Rank Depopulation
Extent Pool 0 Unassigned

9.14 Manual Volume Rebalance
Before Manual Volume Rebalance
1004
Extent Pool 0
managefbvol -action migstart 1000-101a

After Manual Volume Rebalance
1004
Extent Pool 0

9.15 Easy Tier Manual Mode Summary
Migrate Volume (Target Extent Pool, Extent Allocation Method)

Can specify current extent pool or another extent pool
Can specify extent allocation method (rotate volumes or rotate extents)
Pause/Resume Volume Migration
Pause puts volume in migration paused configuration state and stops initiation of any new
extent migrations on a volume
Resume puts volume in migrating configured state and continues migration
Cancel Volume Migration
Nullifies volume migration if it has not started and puts volume in normal configuration state
Stops volume migration if it has started and puts volume in migration cancelled
configuration state. Can request migrate volume to source or target extent pool to retry.
Merge Extent Pool
Moves all volumes in the source extent pool to the target extent pool
Deletes source extent pool if merge is successful
Rank Depopulation
Can use Easy Tier to depopulate a rank and remove from an extent pool
Automatic, non-disruptive and transparent to host access

Chapter 10:
Easy Tier Examples

10.1 Dynamic Volume Relocation
dscli> showfbvol 100b
Name Mig_Vol01
ID 100B
configstate Normal
extpool P2
exts 10
ranks 2
realextents 10
migrating 0
migratingfrom -
dscli> managefbvol -action migstart -extpool p4 100b
dscli> showfbvol 100b dscli> showfbvol 100b

Name Mig_Vol01 Name Mig_Vol01
ID 100B ID 100B
configstate Migrating configstate Normal
extpool P4 extpool P4
exts 10 exts 10
ranks 3 ranks 8
realextents 10 realextents 10
migrating 9 migrating 0
migratingfrom P2 migratingfrom -
dscli> lsfbvol 100b

==============================================================================================
Mig_Vol01 100B Online Normal Normal 2107-900 FB 512 P4 10.0 - 20971520

10.2 Extent Pools Merge
Create two pools belong to even server
dscli> mkextpool -rankgrp 0 -stgtype fb Merg01_Pool
dscli> mkextpool -rankgrp 0 -stgtype fb Merg02_Pool
Add one rank to each of pool
dscli> chrank -extpool p6 r2
dscli> chrank -extpool p8 r8
Create one volume on each of pool
dscli> mkfbvol -extpool p6 -cap 10 -type ds -name Merg01_Vol 100a
dscli> mkfbvol -extpool p8 -cap 10 -type ds -name Merg02_Vol 120a
dscli> lsextpool
=============================================================================================
Merg01_Pool P6 fb 0 below 375 2 375 0 1
Merge pools
dscli> chextpool -merge p6 p8
dscli> lsextpool
=============================================================================================

10.3 Manual Volume Rebalance
Create a volume 100c on extpool P4, cross one rank
dscli> mkfbvol -extpool p4 -cap 10 -type ds -eam rotatevols -name MVR_Vol01 100c
dscli> showfbvol 100c
Name MVR_Vol01
extpool P4
exts 10
ranks 1
eam rotatevols
realextents 10
Run managefbvol to rebalance volume 100c, make volume 100c cross 8 ranks
dscli> managefbvol -eam rotateexts -action migstart 100c
dscli> showfbvol 100c dscli> showfbvol 100c

Name MVR_Vol01 Name MVR_Vol01
ID 100C ID 100C
configstate Migrating configstate Normal
extpool P4 extpool P4
exts 10 exts 10
ranks 3 ranks 8
eam rotateexts eam rotateexts
realextents 10 realextents 10
migrating 6 migrating 0
migratingfrom P4 migratingfrom -
Migrating Migrate complete

10.4 Rank Depopulation
dscli> mkfbvol -extpool p8 -cap 24 -type ds -name Rank_Depop 100e
dscli> lsrank -extpool p8
ID Group State datastate Array RAIDtype extpoolID stgtype
==========================================================
R2 0 Normal Normal A2 10 P8 fb
R8 0 Normal Normal A8 10 P8 fb
dscli> showrank r8
extpoolID P8
extpoolnam Merg02_Pool
volumes 100E
exts 385
usedexts 12
migrating(in) 0
migrating(out) 0
dscli> chrank -unassign r8
dscli> showrank r8 dscli> showrank r2
ID R8 ID R2
State Depopulating State Normal
extpoolID P8 extpoolID P8
extpoolnam Merg02_Pool extpoolnam Merg02_Pool
volumes 100E volumes 100E
usedexts 12 usedexts 24
migrating(in) 0 migrating(in) 12
migrating(out) 12 migrating(out) 0

10.5 Storage Tier Advisor Tool(STAT)
dscli> offloadfile -etdata c:\temp

CMUC00428I offloadfile: The etdata file has been offloaded to c:\temp\SF75TV180ESS01_heat.data.
CMUC00428I offloadfile: The etdata file has been offloaded to c:\temp\SF75TV180ESS11_heat.data.

10.5 STAT
Example Output files of the stat command

STAT>stat -o report SF75TV180ESS01_heat.data SF75TV180ESS11_heat.data
CMUA00019I The STAT.exe command has completed.
STAT>dir report
Directory of C:\Program Files\IBM\STAT62\report
14.12.2011 15:51 <DIR> Data_files
29.09.2011 16:13 1 244 index.html

10.6 STAT REPOT

10.6 STAT REPOT

Chapter 11:
Copy Services Concepts

11.1 Storage Replication and Mirroring
FlashCopy internal replication
Internal point in time copy, Full volume copy, Data set Level copy
Remote mirroring external replication (two/three sites)

Global Copy: Asynchronous copy, unlimited distance
Metro Mirror: Synchronous copy, up to 300 KM between sites,
remote site data currency, consistency groups
A Global Mirror: Asynchronous copy, unlimited distance, remote
B
site near-data currency, consistency groups
z/OS Global Mirror: XRC - optimized for z/OS (SDM),
asynchronous copy, unlimited distance, remote site near-data
A B currency
Metro/Global Mirror: three-box cascade with A-to-B synchronous +
B-to-C asynchronous
z/OS Metro/Global Mirror: three-box multi-target A-to-B
synchronous + B-to-C asynchronous with z/OS Global Mirror
M/GM

11.2 Copy Services management interfaces
You control and manage the DS8000 Copy Services functions by using the following
interfaces:
DS Storage Manager, the GUI of the DS8000 (DS GUI).
DS Command-Line Interface (DS CLI), which provides a set command that cover all Copy
Service functions and options.
Tivoli Storage Productivity Center for Replication, with which you manage large Copy
Services implementations easily and provides data consistency across multiple systems.
Tivoli Storage Productivity Center for Replication is now part of Tivoli Productivity Center
5.1 and IBM SmartCloud Virtual Storage Center.
DS Open Application Programming Interface (DS Open API).

Chapter 12:
FlashCopy Overview

12.1 FlashCopy Functions Overview
Point in Time copy
Near-instantaneous (logical) internal disk copy
Can establish logical copy in seconds
Source and target quickly usable for full read/write
Features:
Full volume FlashCopy (with or without Background Copy)
Incremental FlashCopy
Consistency Group FlashCopy
Fast Reverse Restore
Multiple Relationships
Space Efficient FlashCopy( FlashCopy SE)
Target volume can be a Metro Mirror/Global Copy primary volume
Working Scenarios
Fast backup of data
Test/Query
Temporary snapshot/ data validation /golden copy
Limitation
One source to 12 targets
Only one of relationships can be an incremental

12.2 How does FlashCopy work
Request copy from source to target
FlashCopy relationship created between the volumes
Target is available for processing once the relationship
is created
BACKGROUND COPY
Tracks are copied from the source to the target
Attempts to read/write data already copied proceed as
FlashCopy Read
normal
Attempts to read a target track not already copied
intercepted and data obtained from source
Attempts to write a source track not already copied
intercepted and source track copied to target before
update occurs
BACKGROUND NOCOPY
Attempts to read a target track not copied intercepted FlashCopy Write
and data obtained from source

Attempts to write a source track not copied intercepted
and source track copied to target before update occurs

12.3 FlashCopy Implementation BACKGROUND COPY
DSCLI
mkflash dev storage_image_id cp source_volume_ID:target_volume_ID
Time Source Target
Copy data command issued
Copy immediately available
Source Writes Target
Read and write to both source

and target possible
BACKGROUND COPY When copy is complete,

relationship between source
and target ends

12.4 FlashCopy Implementation BACKGROUND NOCOPY
DSCLI
mkflash dev storage_image_id nocp source_volume_ID:target_volume_ID
Time
Source Target Copy data command issued
Copy immediately available
Read and write to both source

Source Writes Target and target possible
Relationship between source

and target exists until
BACKGROUND NOCOPY withdrawn or all tracks copied

12.5 FlashCopy NOCOPY to COPY
DSCLI
rmflash dev storage_image_id cp source_volume_ID:target_volume_ID
Time
Source Target
FlashCopy command
issued with NOCPY
BACKGROUND NOCOPY Change BACKGROUND

from NOCOPY to COPY
Source Target
When BACKGROUND
COPY is complete,
relationship is withdrawn
BACKGROUND COPY

12.6 Incremental FlashCopy
Change Recording keeps track of changes made to source and target volumes
after establishment of FlashCopy relationship
Use Change Recording along with BACKGROUND COPY and PERSISTENT
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:
To maintain the incremental relationship, specify Change Recording on
each incremental FlashCopy
Only changed data is copied in the background
Previous increment BACKGROUND COPY does not have to complete before
new increment is taken if the FlashCopy is in the same direction
A new FlashCopy increment can be performed in the reverse direction
Previous incremental BACKGROUND COPY going in the opposite direction
must complete before performing an incremental in the other direction

12.7 Consistency Group FlashCopy
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 command allows 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 is within one physical disk subsystem but source
volumes within a consistency group can span physical disk subsystems

12.8 FlashCopy CLI Command Summary
Create FlashCopy
mkflash -tgtse, -cp, -nocp, -freeze, -record, -persist source_id:target_id
List FlashCopy
lsflash
Resync FlashCopy
resyncflash source_id:target_id
FlashCopy Consistent Group
unfreezeflash
Reverse FlashCopy
reverseflash
Remove FlashCopy
rmflash

Chapter 13:
FlashCopy Operation Examples

13.1 Test Data Prepare
Create VG/LV/FS on host
# mkvg S s 256 y fcvg hdisk2
# mklv t jfs2 y fclv fcvg 38 hdisk2
# smitty crfs, use inline log
#lspv
hdisk2 00f74e92626b6200 fcvg active
# lsvg -l fcvg
fcvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
fclv jfs2 38 38 1 open/syncd /fcfs
# df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/fclv 9.50 7.18 25% 5 1% /fcfs
# ls -la /fcfs
total 4789600
-rw-r--r-- 1 root system 2452264960 Jan 22 07:28 t01.tar

13.2 Examples 1-Create FlashCopy
Create a FlashCopy
Incremental FlashCopy, with CG option
dscli> lsfbvol -lss 13
=============================================================================================
Jun_FCS01 1301 Online Normal Normal 2107-900 FB 512 P3 10.0 - 20971520
Jun_FCT01 1302 Online Normal Normal 2107-900 FB 512 P3 10.0 - 20971520
dscli> mkflash -record -cp freeze 1301:1302

CMUC00137I mkflash: FlashCopy pair 1301:1302 successfully created.
dscli>unfreezeflash 13
CMUC00172I unfreezeflash: FlashCopy consistency group for logical subsystem 13 successfully reset
dscli> lsflash 1301

ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
==================================================================================================================
1301:1302 10 0 60 EnabledEnabled Enabled Disabled Enabled Enabled Enabled

13.3 Restore data with reverse FlashCopy
Change data on source Volume
# ls -la /fcfs
total 4790008
-rw-r--r-- 1 root system 204800 Jan 22 07:42 lvmt.log
Restore data from FlashCopy target

umount fs, varyoffvg on host
dscli> reverseflash -record 1301:1302
CMUC00169I reverseflash: FlashCopy volume pair 1301:1302 successfully reversed.
dscli> lsflash 1301
==================================================================================================================
1302:1301 10 0 60 DisabledEnabled Enabled Disabled Enabled Enabled Enabled
varyonvg, mount fs on host to validate data whether are restored

# ls -la /fcfs
total 4789600

13.4 Resynchronize FlashCopy
Change data on source Volume
# ls -la /fcfs
total 4790008
Resynchronize FlashCopy
dscli> resyncflash -record 1301:1302
CMUC00168I resyncflash: FlashCopy volume pair 1301:1302 successfully resynchronized.
Mapping FlashCopy target to host for validation
# lspv
hdisk2 00f74e92626b6200 fcvg
# rmdev -l hdisk2
hdisk2 Defined
#varyonvg fcvg ; mount /fcfs
Replaying log for /dev/fclv.
# ls -la /fcfs
total 4790008

13.5 Create FlashCopy-GUI Demo
Select FlashCopy from Copy Services menu
Select Create
Select FC Volume pair and options
1
3
2

13.6 Resynchronize FlashCopy
Resync FlashCopy
dscli> resyncflash -record -tgtse -cp 1000:1200

13.7 Reverse FlashCopy
Reverse FlashCopy
dscli> reverseflash -record -tgtse 1000:1201
CMUC00169I reverseflash: FlashCopy volume pair 1000:1201 successfully reversed..
dscli> lsflash 1000
==================================================================================================================
1201:1000 12 0 60 Disabled Enabled Enabled Disabled Enabled Enabled Disabled

13.8 Create FlashCopy with TPC-R
(1)Create FlashCopy Session
(2)Choose options

13.9 Create FlashCopy with TPC-R ---Continued
(3)Select storage box
(4)Add copyset
Source Target

13.10 Create FlashCopy with TPC-R ---Continued
(5)Initial FlashCopy
Before FlashCopy
After FlashCopy

Chapter 14:
Metro Mirror Overview

14.1 Metro Mirror Overview
Storage hardware based synchronous mirroring solution
Application independent
Some performance impact to write I/O (e.g. 1ms per 100kms)
Utilizes pre-deposit write capability to minimize protocol overhead
Established at a disk level
A 2 site solution
Metro distance
300 KM without an RPQ
Provides an RPO of 0
Requires automation such as TPC-R or GDPS to ensure consistency
Enables HyperSwap for z/OS and AIX
Disaster protection for all IBM supported platforms
Other potential uses:
Data migration/movement between devices
Data workload migration to alternate site
Insure that there are enough ports and cache for Metro Mirror
Model with Disk Magic

14.2 Typical DS8000 Metro Mirror Configurations
Metro Mirror within a single DS8000

Fibrechannel loopback
Typically used only for testing
Metro Mirror between 2 DS8000s in the

same physical location
Provides high or continuous availability
Clustering
Protection from hardware failure
Leverage HyperSwap
Also may be used for planned outages
Maintenance
Site A Site B Metro Mirror between 2 DS8000s in a

metro region
Protects against local datacenter disaster
300km standard support
Additional distance via RPQ

14.3 DS8000 Metro Mirror - Supported Configurations
One local system to multiple remote systems

Fan out
Usage examples -
Smaller systems at remote site
Multiple active sites with different amounts of capacity
available
Multiple local systems to one remote system
Fan in performance analysis recommended
Usage example subset of capacity on multiple primary
systems is replicated to a single remote system
Simultaneous bi-directional between systems
Different volumes
Usage example 2 active sites
A DS8000 may contain source and target volumes for
multiple Metro Mirror consistency groups

14.4 How Does DS8000 Metro Mirror Work?
Write to primary volume
The primary DS8000 initiates an I/O to the

secondary DS8000 to transfer the data
Host I/O
1 Secondary indicates to the primary that the
write is complete
4
2
Primary acknowledges to the application system
that the write is complete
P S
3

14.5 DS8000 Metro Mirror Considerations
Secondary volume must be off-line to all attached systems

One-to-one volume relationship
Logical paths have to be established between Logical Subsystems
DS8000 only support fibre (FCP) links
FCP links are bidirectional
Up to 8 links per LSS
More than 8 links per physical subsystem is allowed
Up to 4 LSS secondaries can be connected to a primary LSS
A secondary LSS can be connected to as many primary LSS systems as links are
available
Consistency group on the establish path commands
Automation can issue FREEZE commands to all of the LSSs that have dependent
data with the LSS that lost communication
Returning ELB or I/O queue full causes the next dependent write to NOT be issued
maintaining the order of the dependent writes
After all of the FREEZE commands have been issued, RUN commands can be
issued to the LSSs to resume, otherwise the ELB or I/O queue full will be returned
for a default of 2 minutes

14.6 DS8000 Remote Mirror Port Assignment Best Practices
Isolate host connections from remote copy connections (MM, GM, zGM, GC and
MGM) on a host adapter basis
Size the number of host adapters needed based on expected aggregate
maximum bandwidth and maximum IOPS (use Disk Magic or other common
sizing methods based on actual or expected workload)
When possible, isolate asynchronous from synchronous copy connections on a
host adapter basis

Chapter 15:
Metro Mirror Operation Examples

15.1 Metro Mirror Setup Procedures
(1) Query PPRC source and target devid/wwnn
dscli> lssi
Name ID Storage Unit Model WWNN State ESSNet
==============================================================================
DS8800-05 IBM.2107-75XP411 IBM.2107-75XP410 951 500507630BFFC4C8 Online Enabled
(2) Query available PPRC ports
dscli> lsavailpprcport -remotedev IBM.2107-75XP411 -remotewwnn 500507630BFFC4C8 15:13
Local Port Attached Port Type
=============================
I0100 I0230 FCP
I0230 I0300 FCP
(3) Define PPRC path
dscli> mkpprcpath -remotedev IBM.2107-75XP411 -remotewwnn 500507630BFFC4C8 -srclss 15 -tgtlss 13 I0100:I0230
dscli> lspprcpath 15
Src Tgt State SS Port Attached Port Tgt WWNN
=========================================================
15 13 Success FF15 I0100 I0230 500507630BFFC4C8
(4) Create PPRC pair
dscli> mkpprc -remotedev IBM.2107-75XP411 -type mmir 1502:1302
dscli> lspprc 1502 //use l to view Out of Sync Tracks
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
========================================================================================
1502:1302 Full Duplex - Metro Mirror 15 60 Disabled Invalid
dscli> lspprc 1302
1502:1302 Target Full Duplex - Metro Mirror 15 60 Disabled Invalid

15.2 Failover/Failback Procedure
List test data on Primary storage
#lspv
hdisk2 00f74e92626b6200 fcvg active
# ls -la /fcfs
total 4789600
Failover and Failback procedure

15.3 Failover to Secondary Storage
Stop FS and varyoffvg on host side
Failover volumes on Secondary storage
dscli>freezepprc -remotedev IBM.2107-75XP411 15:13
dscli>unfreezepprc -remotedev IBM.2107-75XP411 15:13
dscli> failoverpprc -remotedev IBM.2107-75XP411 -type mmir 1302:1502
CMUC00196I failoverpprc: Remote Mirror and Copy pair 1302:1502 successfully reversed.
dscli> lspprc 1302
========================================================================================
1302:1502 Suspended Host Source Metro Mirror 13 60 Disabled Invalid
Mapping PPRC target volume on Secondary storage to host for data validation
# lspv
# rmdev -l hdisk2
hdisk2 Defined
# ls -la /fcfs
total 4790008

15.4 Failback to Primary Storage
Change test data on secondary storage
# ls -la /fcfs
total 4790008
Create failback PPRC path

dscli> mkpprcpath -remotedev IBM.2107-75XP411 -remotewwnn 500507630BFFC4C8 -srclss 13 -tgtlss 15 I0230:I0100
dscli> lspprcpath 13
Src Tgt State SS Port Attached Port Tgt WWNN
=========================================================
13 15 Success FF15 I0230 I0100 500507630BFFC4C8
Umount FS, varyoffvg on host side
Failback PPRC pair on secondary storage to resync data to primary storage
dscli> failbackpprc -remotedev IBM.2107-75XP411 -type mmir 1302:1502
CMUC00197I failbackpprc: Remote Mirror and Copy pair 1302:1502 successfully failed back.
dscli> lspprc 1302
========================================================================================
dscli>lspprc 1502

15.5 Failover to Primary Storage
Failover volumes on Primary storage
dscli>freezepprc -remotedev IBM.2107-75XP411 13:15
dscli>unfreezepprc -remotedev IBM.2107-75XP411 13:15
dscli> failoverpprc -remotedev IBM.2107-75XP411 -type mmir 1502:1302
CMUC00196I failoverpprc: Remote Mirror and Copy pair 1502:1302 successfully reversed.
dscli> lspprc 1502
========================================================================================
1502:1302 Suspended Host Source Metro Mirror 15 60 Disabled Invalid
dscli> lspprc 1302
1302:1502 Suspended Freeze Metro Mirror 13 60 Disabled Invalid
Data validation
# lspv
# rmdev -l hdisk3
hdisk3 Defined
# ls -la /fcfs
total 4790008

15.6 Failback to Primary Storage
Failback PPRC pair on Primary storage to resync data to secondary storage
dscli> failbackpprc -remotedev IBM.2107-75XP411 -type mmir 1502:1302
CMUC00197I failbackpprc: Remote Mirror and Copy pair 1502:1302 successfully failed back.
dscli> lspprc 1502
========================================================================================
dscli> lspprc 1302

15.7 Metro Mirror Failover/Failback GUI Demo
Create Metro Mirror Session

Define site
Add copyset

Start initial copy

Failover to Secondary storage
Suspend session
Suspend
Recover session
Recover

Failback on Secondary storage

Failover to Primary Storage
Suspend
Recover
Recover

Failback on Primary storage

Chapter 16:
Global Mirror Overview

16.1 What is DS8000 Global Mirror?
Storage hardware asynchronous mirroring solution with data consistency
Minimal impact to the production write I/Os
Unlimited distance
Reduced (less than peak bandwidth) network bandwidth requirements
Peer-to-peer data copy mechanism is Global Copy
Consistency Group formation mechanism is FlashCopy
Application independent
Multiple Session support introduced with R5.1
A 2 site Disaster Recovery replication solution
Integrated solution using 3 volumes
A (local) B (remote) C (journal can be thinly provisioned)
Or 4 copies (D copy for testing without impacting active mirroring)
Very little data loss (Recovery Point Objective (RPO))
Single digit seconds (typically 3-5 seconds)
Scalable
Consistency maintained across multiple subsystems
Up to a 16 physical subsystems in any combination
Ex. 3 primary subsystems and 5 secondary subsystems
16.2 DS8000 Global Mirror Basic Concept
Concept:
Global Copy is used to transmit data to remote site
FlashCopy is used to journal consistent data as updates are made to the Global
Copy secondary volume (B volume)
Data is consistent at remote site using asynchronous data transfer
Intended benefit:
Long distance, no application impact (adjusts to peak workloads automatically),
small RPO, remote copy solution for zSeries and Open Systems data, and
consistency across multiple subsystems
Volume A
FlashCopy
(record, nocopy, persistent, inhibit target write)
Host
I/O Primary Secondary Tertiary
(Asynchronous)
Local Global Copy Volume B
Remote Volume C
Site Site

16.3 Maintaining Consistency DS8000 Global Mirror
Coordination Time momentarily pauses application writes (fraction of millisecond to few
milliseconds)
Consistency maintained by not returning CE/DE or I/O Complete during coordination phase
Not returning CE/DE or I/O complete causes next dependent write to NOT be issued which
maintains order of the dependent writes
Consistency group is NOT specified on the establish path command
Loss of communication will NOT cause ELB I/O Queue Full to be returned for writes
FREEZE command can be used to suspend pairs after Global Mirror session is paused
but ELB or I/O Queue Full will NOT be returned for writes to LSSs
New updates saved in Change Recording bitmap
Creates point in time consistency group across all primary subsystems (in OOS bitmap)
Restart application writes and drain of point in time consistent data recorded in OOS to
remote site
After all consistent data has been copied to secondary (A>B), FlashCopy all data to tertiaries
(B>C)
Restart Global Copy data transfer from primary
Automatically repeat sequence when CG Interval Time elapses
FlashCopy Relationships
Coordinate Drain Time being established
CG Interval Time local units
... ... ... ...

Coordination
Time Let CG data drain to remote
Record new writes in bitmaps All FlashCopy Relationships
but do not copy to remote established
Global Copy continually cycles through
volume bitmaps copying changed data to
remote mirror volumes

16.4 Tunable (input parameters) Use the Defaults
Maximum Coordination Time
Maximum allowed pause of production write updates for the Consistency Group coordination
action
i.e., when the Master coordinates the formation of the Consistency Group with all
Subordinates
When coordination is completed, writes are allowed to continue
Default = 50 milliseconds {Range: 0 to 65535 ms (65+ seconds)}
If the coordination time is exceeded, coordination is stopped and all writes are allowed to
continue
Design point is 2-3 ms
Maximum Drain Time
Maximum CG drain time in seconds before failing (terminating) current drain activity
Default = 30 seconds {Range: 0 to 65535 (just over 18 hours)}
Data rate is monitored by Global Mirror and if it is determined that the data can be drained
within the Maximum Drain Time, a new CG will be formed and the drain will be attempted. If
Drain Time is exceeded, monitor mode will be reentered and this process will be continued for
8 hours.
If no CG is formed in 8 hours, a CG formation will be forced.
Consistency Group Interval Time
Time to wait before again starting the next consistency group formation process
Default = 0 seconds {Range = 0 to 65535 seconds (just over 18 hours)}

16.5 DS8000 Global Mirror Collision Avoidance
Global mirror locks tracks in consistency group (CG) on primary DS8000 at end
of CG formation window
Need to get remaining CG tracks to secondary for CG closure
Host writes to CG track are held while track is locked
Host may notice increased response time (e.g. 1 ms -> 100 ms)
if collision occurs
With R6.2, if host write collides with locked CG track

Host adapter will copy CG track data to side file and then allow
host write to complete
Side file can grow up to 5% of cache
If exceeds 5% of cache, abort the current CG formation
If abort five times in a row, allow collisions for one CG

16.6 FlashCopy SE and Global Mirror Considerations
When planning to use FlashCopy SE with GM, the following rules of thumb may
be applied to ensure that GM performance is not negatively affected:
For a single RAID array, the maximum write throughput should not exceed 20
MB/sec or 300 IO/sec
For a single extent pool of four or more RAID arrays, the maximum write
throughput should not exceed 80 MB/sec or 1200 IO/sec
The anticipated peak write throughput to the primary DS8000 volumes should not
exceed the available link bandwidth for any significant time interval.
Performance is slightly better with DS8700/DS8800 but these recommendations
are still reasonable for DS8700/DS8800

Chapter 17:
DS8000 Monitoring With TPC 5.2

17.1 TPC5.2 function Introduction (1 of 2)
Performance monitor
Optimization
Easy tier
Thin provisioning
Performance reporting

17.2 TPC5.2 function Introduction (1 of 2)
Vmware information
management
Storage device
management
Host management
Volume management
Performance data
collection

17.3 DS8000 monitoring with TPC (1 of 3



17.6 DS8000 performance reporting





17.7 Self-define DS8000 Sample reports

17.7 Self-define DS8000 Sample reports

DS8000 Implemetation Workshop

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

DS8000 Implemetation Workshop

Transféré par

Droits d'auteur :

Formats disponibles

IBM STG Lab Service Storage, GCG

DS8000 Implementation Workshop

Instructor: Yan Ting

1 2014 IBM Corporation

Individuals who are interesting in DS8000 or planning to implement DS8000

2 2014 IBM Corporation

Day 1 (9:00 - 17:00) Day 3 (9:00 - 12:00)

3 2014 IBM Corporation

4 2014 IBM Corporation

5 2014 IBM Corporation

6 2014 IBM Corporation

2004 2006 2009 2010 2012 2014

POWER5 POWER5+ POWER6 POWER6+ POWER7 POWER7+

DS8300 DS8700 DS8800 DS8870 DS8870

7 2014 IBM Corporation

DS81/8300 DS8700 DS8800 DS8870

Disk: FC FC SAS SAS

Power: Bulk Bulk Bulk DC-UPS

CEC: p5/p5 p6 p6+ p7(p7+)

IO Bay: RIOG PCIE PCIE PCIE

Incremental changes between versions maximizes quality

8 2014 IBM Corporation

2006 11-2011 11-2012

9 2014 IBM Corporation

DS8300 DS8700 DS8800 DS8870 (R7) Increase Increase Increase

10 2014 IBM Corporation

4 cores 1 x 4 core #4402 8 cores 64 GB/2 GB None

11 2014 IBM Corporation

961 4-core 360 TB 240 64 8 0

96E N/A 720 TB 480 N/A N/A N/A

12 2014 IBM Corporation

DS8870 models 961/96E maximum configuration with 1536 drives

13 2014 IBM Corporation

14 2014 IBM Corporation

Hardware Management Console

POWER7+ processor-based servers

Direct Current Uninterruptible Power

15 2014 IBM Corporation

Max 128 Ports

Front-End Host Host Host Host Host Host

Hardware Persistent memory Persistent memory

16 2014 IBM Corporation

The DS8870 supports the following disk types:

17 2014 IBM Corporation

Each disk is an industry-standard serial-

18 2014 IBM Corporation

Consists of two Power 7(7+) servers(CEC: central

19 2014 IBM Corporation

20 2014 IBM Corporation

DS8000 supports up to two FC or FICON HAs per

Contains a maximum of 64 host adapter ports for

21 2014 IBM Corporation

Enclosure 0 (XI1) Enclosure 1 (XI2)

Enclosure 2 (XI3) Enclosure 3 (XI4)

Enclosure 4 (XI1) Enclosure 5 (XI2)

Enclosure 6 (XI3) Enclosure 7 (XI4)

240 drives 336 drives 480 drives 480 drives DA

2013 IBM Corporation

26 2014 IBM Corporation

27 2014 IBM Corporation

28 2014 IBM Corporation

29 2014 IBM Corporation

Each processor complex

30 2014 IBM Corporation