IBM Storage and Technology Group
IBM Americas ATS
DS8000 Release 4.2
Technical Announcement Teleconference
February 26th 2009
Alison Pate - patea@us.ibm.com
IBM Americas Advanced Technical Support
© 2009 IBM Corporation
IBM Storage and Technology Group
Agenda
 Announcement Overview/Ordering – Dave Heggen
 Encryption – Bob Kern
 FlashCopy/PPRC – Hank Sautter
 SSD – Charlie Burger
 SATA – Paul Spagnolo
 CLI/GUI enhancements – Paul Spagnolo
 LDAP – Brian Sherman
 Performance – Lee La Frese/Carlos Pratt
 Questions and Answers
2
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Release 4.2
Product Announcement
Overview and Ordering Information
IBM Advanced Technical Support – Americas
Dave Heggen – DHEGGEN@US.IBM.COM
© 2009 IBM Corporation
IBM Storage and Technology Group
Announcement Summary
 DS8000 R4.2 Announcement Date 2/10/2009
 DS8000 R4.2 Generally Available 3/6/2009 (exceptions noted)
– 6 new disk options
• Full Disk Encryption (FDE) for 146, 300, and 450 GB DDMs
• Solid State Drives (SSD) for 73 and 146 GB DDMs
• 1 TB 7.2K RPM SATA
– Remote Pair FlashCopy
– Intelligent Write Caching
 New DS8000s with R4 do not need #180x for TPC-R
– IP v6 is supported on current TPC-R releases
 DS6000 support for System i IOPless adapter for improved
performance
4
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 OEL Family Releases
4.2
4.1
4.0
3.1
3.0
2.4
2.0
1
5
•Solid State Drives (new) •1 TB SATA
•Full Disk Encrypt (new)
•Remote pair FC/ IC Writes
•zHPF
•zGM Incremental Recovery
•450GB DDMs
•Extended Address Volumes
•RAID 6
•IP v6
•SSPC Support (upgr)
•DS8000 M/T Intermix
•SSPC Support (new)
•Storage Pool Striping
•FC Space Eff
•Dynamic Volume Expansion
•HyperPAV
•HMC CIM Agent
•3rd and 4th expansion frame
•Turbo Models
•500 GB FATA Drives
•4GB FCP/FICON
•242x Machine Types

255 LCUs supported
•2GB FCP/FICON

64K Logical Volumes
•RMC/zGM/PTC/PAV

RAID5/RAID10
•73/146/300GB DDMs
October
September
October September
2004
2006
2007
•Synergy Items
2008
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 – R4.2 Announcement Summary

Announcing new features codes for 2107 (IBM Announcement 109-119)
– 1TB SATA Disk Drives

Announcing new features codes for 242x (IBM Announcement 109-120)
–
–
–
–
–
–
–
Full Disk Encryption (146, 300, 450 GB) 15,000 rpm Fibre Channel Disk Drives
Encryption Drive Set Support (#1751)
SSD (73, 146 GB) ~150,000 rpm Disk Drives (April 24th GA)
1TB SATA Disk Drives
Laptop Management Console
DoD Indicator
Release 4.2 Bundle Family

Announcing new functions for all M/Ts (no new feature codes):
– Intelligent Write Caching
– Remote Pair FlashCopy (April 24th GA)

Lab Based Services Availability (no new feature codes):
– Encryption Certification/Activation Service
•

Required/Waived for Activation of Licensed Feature for Encryption
No Withdrawals with this release
6
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 – R4.2 Feature Code Details

1 TB 7.2K rpm SATA Disk Drives
–
Optional chargeable features available on all DS8000 M/Ts and Models
–
Intended to increase total capacity on the DS8000, and intended for archival environments
–
Limitations – Reduced Usable capacity, RAID 6/10 Only, Not intended for SELFC repository data
–
Feature Codes #28x6, 28x7
–
Hardware / Software requirements
•

SSD (73, 146 GB) Disk Drives
–
Optional chargeable features available on all 242x M/Ts and Models
–
Intended for high performance and business critical environments
–
Limitations – raid 5
–
–
•
•
931 System Max # of drives reduced to 256
932/9B2 System Max # of drives reduced to 512
•
Plant Only
Feature Codes #6xx6
Hardware / Software requirements
•

Licensed Machine Code (LMC) level 5.4.2xx.xx (bundle version 64.2.xx.xx), or later
Laptop Management Console
–
Optional chargeable features available on 242x 931, 932, 9B2 Models
–
Replaces prior management console features for systems requiring encryption
–
Limitations – No intermix with System x based HMC systems, Only attached to encryption systems at GA
–
Feature Codes #112x, #113x …recommended HMC features for all new DS8000s
–
Hardware / Software requirements
•
7
Licensed Machine Code (LMC) level 5.4.2xx.xx (bundle version 64.2.xx.xx), or later
Licensed Machine Code (LMC) level 5.4.2xx.xx (bundle version 64.2.xx.xx), or later
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 – R4.2 Feature Code Details
 Full Disk Encryption (146, 300, 450 GB) 15000 rpm disk drive sets
– Optional chargeable features available on all 242x M/Ts and Models
– Intended for secure business critical environments
– Limitations
•
Co-req of Encryption Drive Set Support (FC #175x), no drive intermix with any other drive type
– Feature Codes #5xxx (plant/field to allow MES of drives to systems with encryption support already
installed)
– Hardware / Software requirements
•
Licensed Machine Code (LMC) level 5.4.2xx.xx (bundle version 64.2.xx.xx), or later
•
Tivoli Key Lifecycle Manager Version 1
–
•
•
>
>
Configuration must be certified by Lab Based Services
Dedicated Isolated Key Server + Key Server (minimum 2)
Independent server + any other supported TKLM configuration
Encryption configurations MUST BE ACTIVATED IN THE FIELD (License Key)
Encryption configurations MUST BE REVIEWED BY LAB BASED SERVICES
 Encryption Drive Set Support
– Optional chargeable features available on all 242x M/Ts and Models
– Provides support for encryption drives, all specific hardware
– Limitations – Plant Only
– Feature Codes #175x
– Hardware / Software requirements
•
Licensed Machine Code (LMC) level 5.4.2xx.xx (bundle version 64.2.xx.xx), or later
8
© 2009 IBM Corporation
IBM Storage and Technology Group
Encryption TKLM Requirements
TIVOLI KEY LIFECYCLE MANAGER PLANNING
 The DS8000 series supports:
– IBM Tivoli Key Lifecycle Manager V1.0,
• 5724-T60 1.0.0 IBM Tivoli Key Lifecycle Manager
• 5608-A91 1.0.0 IBM Tivoli Key Lifecycle Manager (distributed for non-Passport
Advantage)
– IBM Tivoli Key Lifecycle Manager for z/OS V1.0
• 1 5698-B35
1.0.0 IBM Tivoli Key Lifecycle Manager for z/OS
 Isolated key servers
– Ordered with feature number 0021, (Machine type 2805 Model MC3) will have a
Linux operating system and TKLM software pre-installed.
• Customers will need to acquire a TKLM license for use of the TKLM software,
• Ordered separately from the standalone server hardware.
 FULL DISK Encryption Activation is a customer responsibility. IBM Full Disk Encryption
offerings must be activated prior to use. This activation is part of the installation and
configuration steps required for use of the technology. This installation and activation
review is performed by the IBM Systems and Technology Lab Services group.
• To order: Send email to storsvcs@us.ibm.com
9
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Disk Features Summary
Fibre Channel SATA
SSD
DDMs/FDE
73GB
60x6
146GB
21xy/50xy
300GB
23xy/51xy
450GB
26xy/52xy
500GB (FATA)
25xy
1TB
61x6
28xy
x = 1 – Single Image, 2 – Set A, 3 – Set B
y = 6 non-COD, 7 - COD
10
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 – R4.2 Feature Code Details
 DoD Indicator
– Optional features available on 242x A frames
– Indicates DoD order for label attachment
– Feature Codes #0020
 Initial Capacity Indicator
– E-config selected, not significant
 Release 4.2 Bundle Family
– Optional features available on all 242x M/Ts and Models
– Selects R4.2 microcode for function that requires new level microcode
– Limitations – none
– Feature Codes #1702
– Hardware / Software requirements
•
11
Provides Licensed Machine Code (LMC) level 5.4.2xx.xx (bundle version 64.2.xx.xx),
or later
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 – Function Details
 New functions for all M/Ts (no new feature codes):
– Intelligent Write Caching
• New performance algorithm to maximize our cache
performance
– Remote Pair FlashCopy
• Improves DR configuration of FlashCopy and Metro Mirror
configurations
 Lab Services Availability (no new feature codes):
– Encryption Certification/Activation Service
• Provides ability to activate encryption on supported DS8000
systems, while certifying correct configuration of key management
software.
– Customer can waive service
12
© 2009 IBM Corporation
IBM Storage and Technology Group
R4.2 Planned Availability Dates
 Announce Date Feb 10, 2009
 Planned Availability Date (all features/functions):
– March 6, 2009 Plant and Field
•
•
•
•
•
1TB SATA Disk Drives
Laptop Management Console
Intelligent Write Caching
DoD Indicator
FDE Disk Sets
– March 6, 2009
•
Encrypted Drive Set Support (Plant Only, 242x only at this time)
– April 24th
•
•
SSD disk drive sets (Plant Only, 242x only at this time)
Remote Pair FlashCopy (Plant/Field)
 MES Planned Availability Date (all features/functions):
– March 6, 2009:
•
•
1 TB 7,200 rpm SATA disk drive MESs (all DS8000 Machine Types)
Full Disk Encryption disk drive MESs
(242x Machine Types only)
–
13
Encryption enabled systems only
© 2009 IBM Corporation
IBM Storage and Technology Group
Two possible New 242x Configurations for #1702
 DS8000 Option 1
– SSD/ENTERPRISE/SATA DDM Features
• limit of 128 SSD DDMs/8 features per DA, 2 features optimal
• SSD feature order will require i-Listed RPQ
– 112x/113x HMC (recommended option)
 DS8000 Option 2
– Full Disk Encryption ( FDE DDM feature(s) and #1751)
• FDE feature order will require i-Listed RPQ 8S1028
– 112x/113x required option, Recommend 2 HMCs
– TKLM (2 instances), Feature 0021 for Independent Server
– Lab Services Review
i-Listed RPQs used for review notifications
14
© 2009 IBM Corporation
IBM Storage and Technology Group
Innovation that matters
IBM Americas ATS
DS8000 R4.2 Disk Encryption
February 26, 2009
Bob Kern
bobkern@us.ibm.com
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM DS8000 Disk Encryption R4.2 LIC

New DS8000 hardware w/Full Disk Encryption (FDE Feature)
– 146 GB / 15K RPM
– 300 GB / 15K RPM
– 450 GB / 15K RPM

Customer data at rest is encrypted
– Data at rest = data on any disk or in any persistent memory

Customer data in flight is not encrypted
– Data in flight = on I/O interfaces or in dynamic memories (Cache, NVS)

Uses Encrypting Disk
– Encryption hardware in disk (AES 128)
– Runs at full data rate
– 146/300/450 GBs 15K RPM

Integrated with Tivoli Key Lifecycle Manager (TKLM)
– DS8000 network attachment to TKLM (TCP/IP)
– DS8000 automatically communicates with TKLM when configuring encryption group or at power on to
obtain necessary encryption keys to access customer data

Supports cryptographic erasure data (change of encryption key)

Key attack vectors being addressed:
 Disk removed (repair, or stolen)
 Box removed (retire, or stolen)

16
IBM procedure to sign a Customer Agreement and to activate Encryption function on each SFI
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM DS8000 Disk Encryption Release 1
– One Encryption Group per Storage Facility Image (One Key on TKLM)
– No intermix of encrypting and non-encrypting DDMs
– New factory order only, no field MES to add encryption to existing non-encrypting machines only
to add encryption capacity to an encryption capable machines.
– Entire storage facility image is either all encrypted or all not encrypted - selected when configure
first rank
Encryption
Group 1/0
Encrypted
Logical Volumes in
Encryption Group 1
Non-Encrypted Logical Volumes
Non-Encrypting Extent Pools
Encrypting Extent Pools
R1
R2
R3
Rn
R5
Encrypting Ranks
A1
A2
A3
An
Encrypting Arrays
……
Encrypting Disks
17
R6
R7
Rm
Non-Encrypting Ranks
A5
A6
A7
Am
Non-Encrypting Arrays
…..……
Non-Encrypting Disks
© 2009 IBM Corporation
IBM Storage and Technology Group
Encrypting Disks on DS8000
 All data on disk is encrypted
– One or more data bands on disk
– Each data band has an encryption key
• Data is always encrypted on write and decrypted on read
• Encryption key is wrapped with access credential and maintained within the disk
• Establishing a new encryption key causes cryptographic erasure
 Access to data requires authentication
– Each data band can be locked with an access credential
• Access credential established by TKLM when band is locked
• Access credential converted to a secure hash and maintained within the disk
• Re-authentication required on locked band after disk power loss
– Bands with “encrypted customer data” are locked by DS8000 before any customer
data is stored on band
– Bands with “unencrypted customer data” are not locked by DS8000
 Encrypting disks have band encryption key set, band unlocked, and data preinitialized at factory so do not have to ‘re-initialize’ when band is locked
18
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Encryption Network Environment
User
Configure Rank(s)
(and lock bands)
3
DSGUI / DS-CLI
Configure TKLM Ports 2
DS8000
Encryption Group
StoragePlex
DS8000 Storage Facility
Storage Facility Image
SFI Server StoragePlex
SFI Server
HMC
Dual HMCs
Recommended
HMC
Customer Network
Get New Data Key
TKLM GUI
Configure TKLM
Devices & Key
Labels
User
19
Key Lifecycle Manager
1
Cryto-Services
Key-Store
Up to 4 Redundant TKLM
IP/Ports Supported
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Data Encryption Management Overview
1.
Customer configures one or more storage facility images on TKLM
2.
Customer Configures one or more key labels on TKLM
3.
Customer configures one or more TKLM IP ports on DS8000 (up to 4 TKLM ports)
4.
Customer configures one encryption group on each Storage Facility Image.


5.
Customer configures one or more encryption capable ranks in an extent pool that is
configured for encryption group.

6.
7.
Data for these logical volumes is stored on encrypting disks that have locked data
bands
Deleting a rank causes SFI to reset the encryption key on the disks in the rank causing
cryptographic erasure.

20
Ranks and extent pools have an encryption group attribute:
Encryption Group 0
designates No Encryption
Encryption Group 1,
designates Encryption
DS8000 locks data bands on encryption disks that are configured in an extent pool
that is configured for encryption group 1
Customer configures logical volumes in the extent pool

8.
Customer provides a key label for an encryption group
DS8000 communicates with TKLM to get necessary keys to manage each encryption
group
Disks are reinitialized whenever a rank is deleted (encrypting or non-encrypting)
Copy services functions are performed in the clear – encryption does not affect
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Tivoli Key Lifecycle Manager (TKLM)

The TKLM works with IBM encryption-enabled storage components in generating,
protecting, storing and maintaining encryption keys that are used to encrypt information
being written to and decrypt information being read from storage media.

TKLM executes in the IBM Java run time environment and it uses IBM Java security
components for the cryptographic capabilities used.

Supported Operating Systems
–
–
–
–
–
–

- 32 bit
- 32 bit
- 64 bit
- 32 bit
(TKLM hosted in the System Services
Runtime Environment for z/OS)
Provide a Graphical User Interface
 Initial configuration wizards
Easy backup and restore of TKLM files
–

- 64 bit
Designed to be Easy to use


AIX 5.3 and 6.1
Red Hat AS 4.0 x86
Suse Linux 9.0 and 10 x86
Solaris 10 Sparc
Windows Server 2003
z/OS V1 R9
One button, single jar file
Lifecycle functions
–
Notification of certificate expiry
– Automated rotation of groups of keys

21
Same TKLM can be used with IBM DS8000 and IBM Tape
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Data Encryption Release 1 Summary
 Requires DS8000 R4.2 LIC and TKLM
– Initial release requires all disks encryption capable
– Enterprise Class Disk Features Supported
 Entire Storage Facility is ‘encryption-capable’ or not ‘encryption
capable’.
 Each Storage Facility Image on encryption-capable Storage Facility can
be independently enabled or disabled for encryption.
 TKLM unwraps single key stored on DS8000 to unlock the entire
Storage Facility Image.
– DS8000 MUST be connected to at least 2 TKLM Servers.
– One of the two TKLM servers must be dedicated/isolated.
 Designed to address situations where single disks are removed for repair,
and where the entire Storage Facility Image is discontinued or re-purposed
22
© 2009 IBM Corporation
IBM Storage and Technology Group
Innovation that matters
Remote Pair FlashCopy
Hank Sautter
sautter@us.ibm.com
© 2009 IBM Corporation
IBM Storage and Technology Group
Agenda
 Remote Pair Flash Copy
–Features and
Requirements
–How it Works
• Establish
• Withdraw
• Options
–FlashCopy Query
24
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy
Features and
Requirements
25
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy - Features
 Improved FlashCopy function for Metro Mirror
Volumes
– Useful for full volume FlashCopy (FB & CKD)
– Dataset FlashCopy for z/OS
 Preserves full duplex
– Hyperswap enabled state preserved for z/OS
 No additional link bandwidth needed
– FlashCopy commands are sent to the remote site - not the data
26
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy – Features (cont)
 Software support
– TSO FCESTABL
– ANTRQST FCESTABLISH
– ICKDSF FLASHCPY ESTABLISH
– DSS COPY, CONSOLIDATE, DEFRAG, Virtual
Concurrent Copy
– HSM FRBACKUP, FRRECOV
– ISMF panels for DSS and ICKDSF
– DS8000 DSCLI
27
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy - Requirements
 Remote pairs must be in Full Duplex state
– Source and Target are Metro Mirror Pairs
 Secondary of FLC source and target are in the
same subsystem
– For best performance they should be in the same
cluster as well
 Local or remote targets may not be Space Efficient
volumes
 No cascading configurations MGM / MGC (target
volumes)
28
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy
How it Works
29
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy - Establish
Local Storage Server
Remote Storage Server
– Hyperswap
enabled
2. Establish
1. full duplex
Local A
Remote A
FlashCopy
Local B
Remote B
3. full duplex
2. FlashCopy Establish
– To MM Primary
Metro
Mirror
FlashCopy
1. Full Duplex State
– Establish
command sent to
remote
3. Remains Full Duplex
– No pprc data
transmission is
required
– Hyperswap
enabled
30
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy - Withdraw
Local Storage Server
Remote Storage Server
– Hyperswap enabled
2. Withdraw
1. full duplex
Local A
Remote A
FlashCopy
Local B
Remote B
3. full duplex
2. FlashCopy Withdraw
– To MM Primary
Metro
Mirror
FlashCopy
1. Full Duplex State
– Withdraw command
sent to remote
3. Remains Full Duplex
– Hyperswap enabled
– Background Copy
options:
•
•
31
Force No – BG Copy
Force Yes – no BG Copy
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy - options
 FlashCopy Remote Pair Establish Options
– None – Use “old way” (primary goes duplex pending, and transfers all target
tracks)
– Preferred – Use Remote Pair FlashCopy if possible, otherwise use the “old
way”
– Required – Fail FLC establish if it does not meet the requirements for
Remote pair FlashCopy (do not cause the FLC target to become duplex
pending).
 FlashCopy Remote Pair Withdraw Options
– ICKDSF – Force
Default is initiate Background copy on withdraw
– TSO / DSS / ANTRQST– Force is the default
– DSCLI -cprm
no other option
Background copy initiated (Default fail withdraw)
 PPRC Query Changes
– PPRC Query shows force withdraw option was initiated
– New status codes – Suspend reason -- if establish FlashCopy at remote fails
32
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy
FlashCopy Query
33
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy – Query ICKDSF
 FlashCopy Query
– ICKDSF FlashCopy Query will have a new PM column
FLASHCOPY RELATIONS INFORMATION TABLE
ADDRESSED VOLUME CU SERIAL NUMBER: 0000001711
+--------------------------------------------------------------------------------------------------------------------+
|
ADDRESSED VOLUME INFORMATION
|
PARTNER |
|-------------------------------------------------------------------------------------------------------|
VOLUME
|
|FLASHCPY|
| | |
|
|
| |
|
| |
| | START OF EXTENT | # CONTIG | # TRACKS |
|
|
|
INFO
|
|SEQUENCE|
| | |
|
|
| |
|
| |
| |-----------------| TRKS IN | YET TO |
|
|
|------------|
|NUMBER |R/T|R|FV|BCE|BCP|CRA|VR|SWI|TWP|P|SEVI|PM| SOURCE | TARGET | EXTENT | BE COPIED|SSID|LSS|CCA|SSID|LSS|CCA|
|--------+---+-+--+---+---+---+--+---+---+-+----+--+--------+--------+----------+----------+----+---+---|----+---+---|
|00000000|SRC|F| T| T | F | F | F| F | F |F|FFFF| N|00000000|00000000|
50085 |
50085 |BF62| 19|21 |BF99| 1A|28 |
+--------------------------------------------------------------------------------------------------------------------+
LEGEND
PM
N
P
R
S
U
34
=
=
=
=
=
=
PRESERVE MIRROR RELATIONSHIP INFORMATION LEGEND:
NOT A MIRRORED RELATIONSHIP
MIRRORED RELATIONSHIP, PREFERRED SPECIFIED
MIRRORED RELATIONSHIP, REQUIRED SPECIFIED
REMOTE MIRRORED RELATIONSHIP AT PPRC SECONDARY
MIRRORED RELATIONSHIP UNDETERMINED
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy – Query TSO
 FlashCopy Query
– TSO FCQUERY SHOWRELS
• New Display relationships option:
ANTF0421I FCQUERY Relations – 1
DEVN SSID LSS CCA CU
SERIAL
ACT MAX XC PC CC RV SE SEQNUM
0000 1111 22 33 AAAA 000000044444 555 666 N N N N NN 77777777
RELATIONSHIP DETAIL STARTING TRACK: aaaaaaaa
DEVICE LONG BUSY FOR CG: bbb WRITE INHIBITED: ccc
---------------------------------------------------PARTNER
SOURCE
TARGET
S F C C P C T S F P
LSS CCA SSID START
START
O V O A R R W E S M
--- --- ---- -------- -------- - - - - - - - - - dd ee ffff gggggggg hhhhhhhh i j k l m n o p q r
NO. OF TRACKS: ssssssssss TRACKS TO COPY: tttttttttt
ESTABL: yyyy/mm/dd hh:mm:ss LAST INCR: yyyy/mm/dd hh:mm:ss
dd ee ffff gggggggg hhhhhhhh i j k l m n o p q r
NO. OF TRACKS: ssssssssss TRACKS TO COPY: tttttttttt
ESTABL: yyyy/mm/dd hh:mm:ss LAST INCR: N/A
dd ee ffff gggggggg hhhhhhhh i j k l m n o p q r
NO. OF TRACKS: ssssssssss TRACKS TO COPY: tttttttttt
ESTABL: yyyy/mm/dd hh:mm:ss LAST INCR: N/A
35
© 2009 IBM Corporation
IBM Storage and Technology Group
Innovation that matters
DS8000 Solid State Drives
Charlie Burger
cwburger@us.ibm.com
© 2009 IBM Corporation
IBM Storage and Technology Group
Agenda
 IBM DS8000 Solid State Drive (SSD)
–What are Solid State Drives?
–Solid State Drive Considerations
–SSD Reliability, Power, Heat
–SSD Endurance
–SSD Recommended Use
–SSD Performance
–SSD Awareness
–Integrated Tooling
–Addendum
37
© 2009 IBM Corporation
IBM Storage and Technology Group
What are Solid State Drives?
 Not Magnetic
 Not Optical
 Semiconductor (NAND flash)
– Electronically erasable medium
– Random access
– No mechanical read/write interface
(arm/head)
– No rotating parts
 Packaged with interface just like HDD
and function just like HDD
38
© 2009 IBM Corporation
IBM Storage and Technology Group
Solid State Drive Considerations
 DDM Install Groups
– 73 GB – 16 drives
– 146 GB – 16 drives
 Max 128 SSD per DA
– Use 16 SSDs per DA for performance
– Max of 256 drives including SSD for Model 931
• Max number of drives possible not recommended for performance for 931
– Max of 512 drives including SSD for Models 932 and 9B2
• Consider performance accelerator feature
• Max number of drives possible not recommended for performance for either 932 and 9B2
 DS8000 systems with SSD drives installed will have no 3rd or 4th expansion frames
 RAID-5 only
– FB or CKD
 Factory only for this release
 RPQ to review configuration
39
© 2009 IBM Corporation
IBM Storage and Technology Group
SSD Reliability, Power, Heat
 Absence of mechanical moving parts
– Significantly more reliable
• Used in military applications
• Used in extreme temperatures (hot/cold)
 Green
– Power
• Fraction of power consumed
– Heat
• Fraction of heat dissipated
40
© 2009 IBM Corporation
IBM Storage and Technology Group
SSD Endurance
 Flash program/erase cycles are cumulatively destructive
 Current commercial NAND flash varieties
– Single level cell (SLC)  105 writes/cell (our SSD is SLC)
– Multi level cell (MLC)  [ 104 writes/cell (Cameras, iPods,
etc.)
 Coping strategies
– Wear leveling, over-provisioning, bad block management, ECC,
compression, write elimination, …
 Data stored remain valid for 10 yr without power
41
© 2009 IBM Corporation
IBM Storage and Technology Group
SSD Recommended Use
 Best suited for cache-unfriendly data
– Random read access, high performance data sets
• Both FB and CKD environments
42
© 2009 IBM Corporation
IBM Storage and Technology Group
SSD Performance
 DS8K HDD RAID-5 (8x 15K 300GB)
– Throughput: 399MB/s (R), 335MB/s (W)
– IOPS: 1.9K (R), 0.5K (W)
 DS8K SSD RAID-5 (8x 73GB)
– Throughput: 400MB/s (R), 365MB/s (W)
– IOPS: 21.3K (R), 5.8K (W)
Note the performance improvement for IOPs on SSD!
43
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 SSD Performance Testing
DB2
for
z/OS
DB2 Sync I/Os Running on z/OS
DB2 Synch I/O Wait Time
(Microseconds)
10000
8000
6000
4000
2000
0
44
8000
Faster
Transactions
Up to 8x!
229
290
739
3860
838
© 2009 IBM Corporation
IBM Storage and Technology Group
SSD Awareness
 SMS volume selection will recognize volumes backed by SSD
– Policies implemented by ACS routines can direct allocations to SSD
• Consider using a Storage Group with only SSD
 New fields for SMF type 42 subtype 5 and 6 records
• Average read disconnect time per data set
• Total number of read operations to the data set
 DEVSERV QDASD
– Displays device attributes with new ATTR keyword
ds qd,d300,attr
IEE459I 16.59.01 DEVSERV QDASD 613
C
UNIT VOLSER SCUTYPE DEVTYPE
CYL SSID SCU-SERIAL DEV-SERIAL EFC
ATTRIBUTE/FEATURE
YES/NO ATTRIBUTE/FEATURE
YES/NO
D300 TK9085 2107921 2107900 65520 2401 0175-02411 0175-02411 *OK
SOLID STATE DRIVES
Y
ENCRYPTION
N
 DEVTYPE macro
– With INFO=DASD, indicates if a volume is backed by solid state drives
45
© 2009 IBM Corporation
IBM Storage and Technology Group
Integrated Tooling
 DB2 Online Reorg
– Allows non-disruptive migration of data to SSD technology
 Omegamon XE
– Will identify datasets and volumes that will benefit from migration to SSD
– Integrate new instrumentation for Read-Only DISC time
– Cache Statistics
 SoftTek Data Mobility Console
– Analyze SMF data in real time
– Seamless integration into data migration tools
• TDMF
• LDMF
46
© 2009 IBM Corporation
IBM Storage and Technology Group
1 TB SATA Drive
Paul Spagnolo
pgspagn@us.ibm.com
© 2009 IBM Corporation
47
IBM Storage and Technology Group
1 TB SATA 7200 RPM Drive Support
 New 1 TB SATA drives will become
available on March 6, 2009
 Enabled through new feature code
specifications in megapack (16)
drive increments (see following
chart for list of feature codes)
 Scales DS8000 to 1,024 TB physical
capacity when fully populated with
all 1 TB SATA drives (5 frames)
 All models of the DS8000 family are
supported (2107, 2421, 2422, 2423
and 2424)
48
© 2009 IBM Corporation
IBM Storage and Technology Group
When to Consider SATA
 Tier-1 Storage
– When looking for low cost per gigabyte with lower expectations of
performance
– Streaming applications where transfer rate is more important than
seek times
– Applications with low IOPS performance requirements
 Tier-2 Storage
– Disk based near-line storage between disk and tape
– Disaster recovery target for remote replication
– Fixed content / Managed Retention data
– Temporary work space for short-term processing
– Consolidation of tier-2 subsystems
49
© 2009 IBM Corporation
IBM Storage and Technology Group
New Feature Codes
 FC #2816 – 1 TB 7200 RPM SATA drive set
 FC #2817 – 1 TB 7200 RPM SATA standby COD drive set
 FC #2826 – 1 TB 7200 RPM SATA LPAR A drive set
 FC #2836 – 1 TB 7200 RPM SATA LPAR B drive set
 FC #2827 – 1 TB 7200 RPM SATA LPAR A standby COD drive set
 FC #2837 – 1 TB 7200 RPM SATA LPAR B standby COD drive set
 Available for both factory (new builds) and field upgrades (MES)
at GA
50
© 2009 IBM Corporation
IBM Storage and Technology Group
SATA Drive Requirements and Limitations
 1 TB SATA drives will require at a minimum licensed machine code
(LMC) level 5.4.2xx.xxx (bundle version 64.2.xx.xx)
 Only RAID-6 or RAID-10 will support the SATA drives
– No RAID-5 support at GA
– RPQs for RAID-5 support must be submitted through normal
channels
– RAID-6 requires DA-2 device adapters
 Not intended for Space Efficient FlashCopy repository because of
the lower performance and reliability characteristics
 A SATA drive will not be used as a spare for FC or FATA drives
– Performance of the entire array would be degraded
51
© 2009 IBM Corporation
IBM Storage and Technology Group
SATA Design Architecture
 SATA architecture uses a 512 byte physical sector size
 DS8000 device adapters require 524 bytes sector size
 SATA uses a different protocol compared to fibre channel
 IBM elected to utilize a bridge card
•
•
•
•
•
52
Translates fibre channel protocol to SATA protocol and vice versa
Bridge card is an Emulex BRG436-I
Connects to Hitachi Gemini-K 1 TB SATA drive
Requires padding to align blocks to sector size
Each SATA drive has its own dedicated bridge card
© 2009 IBM Corporation
IBM Storage and Technology Group
Fibre Channel / SATA Bridge
DS8000 Device
Adapter Communicates
via Fibre Channel
Protocol
Emulex BRG436-I Bridge
Translates Fibre Channel
Protocol to SATA Protocol and
vice versa.
FC
53
Gemini-K Drive
Communicates via
SATA Protocol
SATA
© 2009 IBM Corporation
IBM Storage and Technology Group
Sector Mapping Capacity Tradeoff
 Reduced disk capacity due to extra padding added
on every alignment unit. The estimated loss of
disk capacity is as follows:
– 128 block alignment – 0% capacity loss
– 64 block alignment – 0.76% capacity loss
– 32 block alignment – 0.76% capacity loss
– 16 block alignment – 3.68% capacity loss
– 8 block alignment – 9.03% capacity loss
 DS8000 will utilize a 8/9 sector remapping
– Every 524 byte block aligns at 512 byte sector
boundary on every 8 logical blocks due to padding
54
© 2009 IBM Corporation
IBM Storage and Technology Group
Sector Remapping – High Capacity (128/131)
(not chosen)
The diagram below illustrates the sector remapping done by
existing Emulex Bridge, allowing for maximum disk capacity.
0
0
1
1
2
2
127
130
128
131
129
132
255
261
256
262
524B
Logical
Blocks
512B
Physical
Sectors
524 byte logical block aligns at 512 byte sector boundary on
every 128 logical blocks. The write transfer length needs to
be 128 logical blocks(or multiple of 128) and starting at an
aligned LBA, to avoid read-modify-write operation.
55
© 2009 IBM Corporation
IBM Storage and Technology Group
Sector Remapping – Higher Performance At
Lower Alignment Units (8/9)
(chosen)
The diagram below illustrates the sector remapping for higher
performance via alignment unit length of 8 logical blocks.
0
0
1
1
2
2
7
8
8
9
9
10
15
17
524B logical block aligns at 512B sector boundary on every 8
logical blocks, due to the padding. Read-modify-write
operation is avoided for writes with transfer lengths of 8
logical blocks (or multiple of 8) and starting at an aligned
LBA.
56
16
18
524B
Logical
Blocks
512B
Physical
Sectors
Padding introduced
in every 9th physcial
sector to force
alignment for 8
logical blocks.
© 2009 IBM Corporation
IBM Storage and Technology Group
Sector Remapping
 Higher performance (8/9) remapping was chosen
over higher capacity (128/131).
 Results in significantly higher write performance
 However 1 TB SATA drives will have about 900 GB
of usable capacity
 Formatted arrays are quite large
57
© 2009 IBM Corporation
IBM Storage and Technology Group
SATA Array Usable Extents (Decimal GB)
RAID Type
FB
FB
CKD
CKD
Extent
Count
Decimal
GB
Extent
Count
Decimal GB
RAID-5*
(6+p)
4886
5246.30
5472
5176.54
RAID-5*
(7+p)
5695
6114.95
6380
6035.52
RAID-6
(5+p+q)
3976
4269.20
4456
4215.40
RAID-6
(6+p+q)
4784
5136.78
5361
5071.54
RAID-10
(3x3)
2442
2622.08
2735
2587.33
RAID-10
(4x4)
3258
3498.25
3647
3450.08
FB extents are 1 GB
CKD extents are 1113 cylinders
* RAID-5 is not generally available
58
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8300 Raid 6 CKD Effective Capacity in 1000s of 3390-1 extents
Disk
146 GB
300 GB
450 GB
1TB
Feature EffCap PhyCap EffCap PhyCap EffCap PhyCap EffCap
Disk
146 GB
300 GB
450 GB
1 TB
PhyCap Feature EffCap PhyCap EffCap PhyCap EffCap PhyCap EffCap
PhyCap
1
1.42
2.34
2.88
4.8
4.33
7.2
8.91
16
33
51.79
77.09
105.13
158.4
157.85
237.6
324.87
528
2
2.84
4.67
5.77
9.6
8.66
14.4
17.82
32
34
53.5
79.42
108.6
163.2
163.06
244.8
335.59
544
3
4.55
7.01
9.24
14.4
13.87
21.6
28.55
48
35
55.21
81.76
112.07
168
168.27
252
346.31
560
4
6.26
9.34
12.71
19.2
19.08
28.8
39.27
64
36
56.92
84.1
115.54
172.8
173.48
259.2
357.03
576
5
7.68
11.68
15.59
24
23.41
36
48.18
80
37
58.63
86.43
119.01
177.6
178.69
266.4
367.75
592
6
9.1
14.02
18.48
28.8
27.74
43.2
57.09
96
38
60.34
88.77
122.48
182.4
183.9
273.6
378.48
608
7
10.81
16.35
21.95
33.6
32.95
50.4
67.81
112
39
62.05
91.1
125.95
187.2
189.11
280.8
389.2
624
8
12.52
18.69
25.42
38.4
38.16
57.6
78.54
128
40
63.76
93.44
129.42
192
194.32
288
399.92
640
9
13.94
21.02
28.3
43.2
42.49
64.8
87.45
144
41
65.47
95.78
132.89
196.8
199.53
295.2
410.64
656
10
15.36
23.36
31.18
48
46.82
72
96.36
160
42
67.18
98.11
136.36
201.6
204.74
302.4
421.36
672
11
17.07
25.7
34.65
52.8
52.03
79.2
107.08
176
43
68.89
100.45
139.83
206.4
209.95
309.6
432.09
688
12
18.78
28.03
38.12
57.6
57.24
86.4
117.8
192
44
70.6
102.78
143.3
211.2
215.16
316.8
442.81
704
13
20.2
30.37
41.01
62.4
61.57
93.6
126.72
208
45
72.31
105.12
146.77
216
220.37
324
453.53
720
14
21.62
32.7
43.89
67.2
65.9
100.8
135.63
224
46
74.02
107.46
150.24
220.8
225.58
331.2
464.25
736
15
23.33
35.04
47.36
72
71.11
108
146.35
240
47
75.73
109.79
153.71
225.6
230.79
338.4
474.97
752
16
25.04
37.38
50.83
76.8
76.32
115.2
157.07
256
48
77.44
112.13
157.18
230.4
236
345.6
485.7
768
17
26.46
39.71
53.72
81.6
80.65
122.4
165.98
272
49
79.15
114.46
160.65
235.2
241.21
352.8
496.42
784
18
27.88
42.05
56.6
86.4
84.98
129.6
174.9
288
50
80.86
116.8
164.12
240
246.42
360
507.14
800
19
29.59
44.38
60.07
91.2
90.19
136.8
185.62
304
51
82.57
119.14
167.59
244.8
251.63
367.2
517.86
816
20
31.3
46.72
63.54
96
95.4
144
196.34
320
52
84.28
121.47
171.06
249.6
256.84
374.4
528.58
832
21
32.72
49.06
66.42
100.8
99.73
151.2
205.25
336
53
85.99
123.81
174.53
254.4
262.05
381.6
539.31
848
22
34.14
51.39
69.31
105.6
104.06
158.4
214.16
352
54
87.7
126.14
178
259.2
267.26
388.8
550.03
864
23
35.85
53.73
72.78
110.4
109.27
165.6
224.89
368
55
89.41
128.48
181.47
264
272.47
396
560.75
880
24
37.56
56.06
76.25
115.2
114.48
172.8
235.61
384
56
91.12
130.82
184.94
268.8
277.68
403.2
571.47
896
25
38.98
58.4
79.13
120
118.81
180
244.52
400
57
92.83
133.15
188.41
273.6
282.89
410.4
582.19
912
26
40.4
60.74
82.02
124.8
123.14
187.2
253.43
416
58
94.54
135.49
191.88
278.4
288.1
417.6
592.92
928
27
42.11
63.07
85.49
129.6
128.35
194.4
264.15
432
59
96.25
137.82
195.35
283.2
293.31
424.8
603.64
944
28
43.82
65.41
88.96
134.4
133.56
201.6
274.88
448
60
97.96
140.16
198.82
288
298.52
432
614.36
960
29
45.24
67.74
91.84
139.2
137.89
208.8
283.79
464
61
99.67
142.5
202.29
292.8
303.73
439.2
625.08
976
30
46.66
70.08
94.72
144
142.22
216
292.7
480
62
101.38
144.83
205.76
297.6
308.94
446.4
635.8
992
31
48.37
72.42
98.19
148.8
147.43
223.2
303.42
496
63
103.09
147.17
209.23
302.4
314.15
453.6
646.53
1008
50.08
74.75
101.66
153.6
152.64
230.4
314.14
512
104.8
149.5
212.7
307.2
319.36
460.8
657.25
1024
32
64
See Techdocs PRS1101 for complete listing of all RAID formats
59
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8300 Raid 6 FB Effective Capacity in Binary TB
Disk
146 GB
300 GB
450 GB
1 TB
Feature EffCap PhyCap EffCap PhyCap EffCap PhyCap EffCap
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Disk
146 GB
300 GB
450 GB
1 TB
PhyCap Feature EffCap PhyCap EffCap PhyCap EffCap PhyCap EffCap
1.24
2.34
2.51
4.8
3.77
7.2
7.77
16
2.48
4.67
5.03
9.6
7.55
14.4
15.53
32
3.97
7.01
8.05
14.4
12.09
21.6
24.88
48
5.46
9.34
11.08
19.2
16.63
28.8
34.22
64
6.7
11.68
13.59
24
20.4
36
41.99
80
7.93
14.02
16.11
28.8
24.18
43.2
49.75
96
9.42
16.35
19.13
33.6
28.72
50.4
59.1
112
10.91
18.69
22.16
38.4
33.26
57.6
68.44
128
12.15
21.02
24.67
43.2
37.03
64.8
76.21
144
13.39
23.36
27.18
48
40.81
72
83.97
160
14.88
25.7
30.21
52.8
45.35
79.2
93.32
176
16.37
28.03
33.24
57.6
49.89
86.4
102.66
192
17.61
30.37
35.75
62.4
53.66
93.6
110.43
208
18.85
32.7
38.26
67.2
57.44
100.8
118.19
224
20.34
35.04
41.29
72
61.98
108
127.54
240
21.83
37.38
44.31
76.8
66.52
115.2
136.88
256
23.07
39.71
46.83
81.6
70.29
122.4
144.65
272
24.31
42.05
49.34
86.4
74.07
129.6
152.41
288
25.8
44.38
52.37
91.2
78.61
136.8
161.76
304
27.29
46.72
55.39
96
83.15
144
171.1
320
28.52
49.06
57.91
100.8
86.92
151.2
178.87
336
29.76
51.39
60.42
105.6
90.69
158.4
186.63
352
31.25
53.73
63.45
110.4
95.24
165.6
195.98
368
32.74
56.06
66.47
115.2
99.78
172.8
205.32
384
33.98
58.4
68.99
120
103.55
180
213.09
400
35.22
60.74
71.5
124.8
107.32
187.2
220.85
416
36.71
63.07
74.52
129.6
111.87
194.4
230.2
432
38.2
65.41
77.55
134.4
116.41
201.6
239.54
448
39.44
67.74
80.06
139.2
120.18
208.8
247.31
464
40.68
70.08
82.58
144
123.95
216
255.07
480
42.17
72.42
85.6
148.8
128.5
223.2
264.42
496
43.66
74.75
88.63
153.6
133.04
230.4
273.76
512
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
PhyCap
45.15
77.09
91.65
158.4
137.58
237.6
283.1
528
46.64
79.42
94.68
163.2
142.12
244.8
292.45
544
48.13
81.76
97.7
168
146.66
252
301.79
560
49.62
84.1
100.73
172.8
151.2
259.2
311.14
576
51.11
86.43
103.76
177.6
155.74
266.4
320.48
592
52.6
88.77
106.78
182.4
160.28
273.6
329.83
608
54.09
91.1
109.81
187.2
164.82
280.8
339.17
624
55.58
93.44
112.83
192
169.37
288
348.51
640
57.07
95.78
115.86
196.8
173.91
295.2
357.86
656
58.56
98.11
118.88
201.6
178.45
302.4
367.2
672
60.05
100.45
121.91
206.4
182.99
309.6
376.55
688
61.54
102.78
124.93
211.2
187.53
316.8
385.89
704
63.03
105.12
127.96
216
192.07
324
395.23
720
64.52
107.46
130.99
220.8
196.61
331.2
404.58
736
66.01
109.79
134.01
225.6
201.15
338.4
413.92
752
67.5
112.13
137.04
230.4
205.7
345.6
423.27
768
68.99
114.46
140.06
235.2
210.24
352.8
432.61
784
70.48
116.8
143.09
240
214.78
360
441.95
800
71.97
119.14
146.11
244.8
219.32
367.2
451.3
816
73.46
121.47
149.14
249.6
223.86
374.4
460.64
832
74.95
123.81
152.16
254.4
228.4
381.6
469.99
848
76.44
126.14
155.19
259.2
232.94
388.8
479.33
864
77.93
128.48
158.22
264
237.48
396
488.68
880
79.42
130.82
161.24
268.8
242.02
403.2
498.02
896
80.92
133.15
164.27
273.6
246.57
410.4
507.36
912
82.41
135.49
167.29
278.4
251.11
417.6
516.71
928
83.9
137.82
170.32
283.2
255.65
424.8
526.05
944
85.39
140.16
173.34
288
260.19
432
535.4
960
86.88
142.5
176.37
292.8
264.73
439.2
544.74
976
88.37
144.83
179.39
297.6
269.27
446.4
554.08
992
89.86
147.17
182.42
302.4
273.81
453.6
563.43
1008
91.35
149.5
185.44
307.2
278.35
460.8
572.77
1024
64
See Techdocs PRS1101 for complete listing of all RAID formats
60
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8300 Raid 6 CKD Effective Capacity in Decimal TB
Disk
146 GB
300 GB
450GB
Feature EffCap PhyCap EffCap PhyCap EffCap
1TB
PhyCap EffCap
Disk
146 GB
300 GB
450 GB
1TB
PhyCap Feature EffCap PhyCap EffCap PhyCap EffCap PhyCap EffCap
PhyCap
1
1.34
2.34
2.73
4.8
4.1
7.2
8.43
16
33
48.99
77.09
99.46
158.4
149.33
237.6
307.32
528
2
2.69
4.67
5.46
9.6
8.19
14.4
16.86
32
34
50.61
79.42
102.74
163.2
154.25
244.8
317.47
544
3
4.3
7.01
8.74
14.4
13.12
21.6
27
48
35
52.23
81.76
106.02
168
159.18
252
327.61
560
4
5.92
9.34
12.02
19.2
18.05
28.8
37.15
64
36
53.85
84.1
109.3
172.8
164.11
259.2
337.75
576
5
7.27
11.68
14.75
24
22.15
36
45.58
80
37
55.46
86.43
112.59
177.6
169.04
266.4
347.9
592
6
8.61
14.02
17.48
28.8
26.24
43.2
54.01
96
38
57.08
88.77
115.87
182.4
173.97
273.6
358.04
608
7
10.23
16.35
20.76
33.6
31.17
50.4
64.15
112
39
58.7
91.1
119.15
187.2
178.9
280.8
368.18
624
8
11.84
18.69
24.04
38.4
36.1
57.6
74.3
128
40
60.32
93.44
122.44
192
183.83
288
378.32
640
9
13.19
21.02
26.77
43.2
40.2
64.8
82.73
144
41
61.93
95.78
125.72
196.8
188.76
295.2
388.47
656
10
14.53
23.36
29.5
48
44.29
72
91.16
160
42
63.55
98.11
129
201.6
193.68
302.4
398.61
672
11
16.15
25.7
32.78
52.8
49.22
79.2
101.3
176
43
65.17
100.45
132.28
206.4
198.61
309.6
408.75
688
12
17.77
28.03
36.07
57.6
54.15
86.4
111.44
192
44
66.79
102.78
135.57
211.2
203.54
316.8
418.9
704
13
19.11
30.37
38.79
62.4
58.25
93.6
119.87
208
45
68.41
105.12
138.85
216
208.47
324
429.04
720
14
20.45
32.7
41.52
67.2
62.34
100.8
128.3
224
46
70.02
107.46
142.13
220.8
213.4
331.2
439.18
736
15
22.07
35.04
44.8
72
67.27
108
138.45
240
47
71.64
109.79
145.41
225.6
218.33
338.4
449.33
752
16
23.69
37.38
48.09
76.8
72.2
115.2
148.59
256
48
73.26
112.13
148.7
230.4
223.26
345.6
459.47
768
17
25.03
39.71
50.82
81.6
76.29
122.4
157.02
272
49
74.88
114.46
151.98
235.2
228.18
352.8
469.61
784
18
26.37
42.05
53.54
86.4
80.39
129.6
165.45
288
50
76.49
116.8
155.26
240
233.11
360
479.75
800
19
27.99
44.38
56.83
91.2
85.32
136.8
175.59
304
51
78.11
119.14
158.54
244.8
238.04
367.2
489.9
816
20
29.61
46.72
60.11
96
90.25
144
185.74
320
52
79.73
121.47
161.83
249.6
242.97
374.4
500.04
832
21
30.95
49.06
62.84
100.8
94.34
151.2
194.17
336
53
81.35
123.81
165.11
254.4
247.9
381.6
510.18
848
22
32.3
51.39
65.57
105.6
98.44
158.4
202.6
352
54
82.96
126.14
168.39
259.2
252.83
388.8
520.33
864
23
33.91
53.73
68.85
110.4
103.37
165.6
212.74
368
55
84.58
128.48
171.67
264
257.76
396
530.47
880
24
35.53
56.06
72.13
115.2
108.3
172.8
222.89
384
56
86.2
130.82
174.96
268.8
262.69
403.2
540.61
896
25
36.88
58.4
74.86
120
112.39
180
231.32
400
57
87.82
133.15
178.24
273.6
267.61
410.4
550.76
912
26
38.22
60.74
77.59
124.8
116.49
187.2
239.75
416
58
89.43
135.49
181.52
278.4
272.54
417.6
560.9
928
27
39.84
63.07
80.87
129.6
121.42
194.4
249.89
432
59
91.05
137.82
184.8
283.2
277.47
424.8
571.04
944
28
41.45
65.41
84.15
134.4
126.35
201.6
260.03
448
60
92.67
140.16
188.09
288
282.4
432
581.18
960
29
42.8
67.74
86.88
139.2
130.44
208.8
268.46
464
61
94.29
142.5
191.37
292.8
287.33
439.2
591.33
976
30
44.14
70.08
89.61
144
134.54
216
276.89
480
62
95.91
144.83
194.65
297.6
292.26
446.4
601.47
992
31
45.76
72.42
92.89
148.8
139.47
223.2
287.04
496
63
97.52
147.17
197.94
302.4
297.19
453.6
611.61
1008
47.38
74.75
96.17
153.6
144.4
230.4
297.18
512
99.14
149.5
201.22
307.2
302.11
460.8
621.76
1024
32
64
See Techdocs PRS1101 for complete listing of all RAID formats
61
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8300 Raid 6 FB Effective Capacity in Decimal TB
Disk
146 GB
300 GB
450 GB
1TB
Feature EffCap PhyCap EffCap PhyCap EffCap PhyCap EffCap
Disk
146 GB
300 GB
450 GB
1TB
PhyCap Feature EffCap PhyCap EffCap PhyCap EffCap PhyCap EffCap
PhyCap
1
1.36
2.34
2.76
4.8
4.15
7.2
8.54
16
33
49.64
77.09
100.77
158.4
151.26
237.6
311.25
528
2
2.72
4.67
5.53
9.6
8.3
14.4
17.08
32
34
51.28
79.42
104.09
163.2
156.25
244.8
321.53
544
3
4.36
7.01
8.85
14.4
13.29
21.6
27.35
48
35
52.91
81.76
107.42
168
161.24
252
331.8
560
4
6
9.34
12.18
19.2
18.28
28.8
37.62
64
36
54.55
84.1
110.75
172.8
166.23
259.2
342.07
576
5
7.36
11.68
14.94
24
22.43
36
46.16
80
37
56.19
86.43
114.07
177.6
171.23
266.4
352.35
592
6
8.72
14.02
17.71
28.8
26.58
43.2
54.7
96
38
57.83
88.77
117.4
182.4
176.22
273.6
362.62
608
7
10.36
16.35
21.03
33.6
31.57
50.4
64.97
112
39
59.47
91.1
120.72
187.2
181.21
280.8
372.89
624
8
12
18.69
24.36
38.4
36.57
57.6
75.24
128
40
61.11
93.44
124.05
192
186.21
288
383.16
640
9
13.36
21.02
27.12
43.2
40.71
64.8
83.78
144
41
62.74
95.78
127.38
196.8
191.2
295.2
393.44
656
10
14.72
23.36
29.89
48
44.86
72
92.32
160
42
64.38
98.11
130.7
201.6
196.19
302.4
403.71
672
11
16.36
25.7
33.21
52.8
49.86
79.2
102.59
176
43
66.02
100.45
134.03
206.4
201.18
309.6
413.98
688
12
18
28.03
36.54
57.6
54.85
86.4
112.87
192
44
67.66
102.78
137.36
211.2
206.18
316.8
424.26
704
13
19.36
30.37
39.3
62.4
59
93.6
121.41
208
45
69.3
105.12
140.68
216
211.17
324
434.53
720
14
20.72
32.7
42.07
67.2
63.15
100.8
129.94
224
46
70.94
107.46
144.01
220.8
216.16
331.2
444.8
736
15
22.36
35.04
45.39
72
68.14
108
140.22
240
47
72.58
109.79
147.34
225.6
221.15
338.4
455.08
752
16
24
37.38
48.72
76.8
73.13
115.2
150.49
256
48
74.21
112.13
150.66
230.4
226.15
345.6
465.35
768
17
25.36
39.71
51.48
81.6
77.28
122.4
159.03
272
49
75.85
114.46
153.99
235.2
231.14
352.8
475.62
784
18
26.72
42.05
54.25
86.4
81.43
129.6
167.57
288
50
77.49
116.8
157.31
240
236.13
360
485.9
800
19
28.36
44.38
57.57
91.2
86.42
136.8
177.84
304
51
79.13
119.14
160.64
244.8
241.13
367.2
496.17
816
20
30
46.72
60.9
96
91.41
144
188.11
320
52
80.77
121.47
163.97
249.6
246.12
374.4
506.44
832
21
31.36
49.06
63.66
100.8
95.56
151.2
196.65
336
53
82.41
123.81
167.29
254.4
251.11
381.6
516.72
848
22
32.72
51.39
66.43
105.6
99.71
158.4
205.19
352
54
84.04
126.14
170.62
259.2
256.1
388.8
526.99
864
23
34.36
53.73
69.75
110.4
104.71
165.6
215.46
368
55
85.68
128.48
173.95
264
261.1
396
537.26
880
24
36
56.06
73.08
115.2
109.7
172.8
225.73
384
56
87.32
130.82
177.27
268.8
266.09
403.2
547.54
896
25
37.36
58.4
75.84
120
113.85
180
234.27
400
57
88.96
133.15
180.6
273.6
271.08
410.4
557.81
912
26
38.72
60.74
78.61
124.8
118
187.2
242.81
416
58
90.6
135.49
183.92
278.4
276.07
417.6
568.08
928
27
40.36
63.07
81.93
129.6
122.99
194.4
253.08
432
59
92.24
137.82
187.25
283.2
281.07
424.8
578.35
944
28
42
65.41
85.26
134.4
127.98
201.6
263.36
448
60
93.88
140.16
190.58
288
286.06
432
588.63
960
29
43.36
67.74
88.02
139.2
132.13
208.8
271.9
464
61
95.51
142.5
193.9
292.8
291.05
439.2
598.9
976
97.15
144.83
197.23
297.6
296.04
446.4
609.17
992
98.79
147.17
200.56
302.4
301.04
453.6
619.45
1008
100.43
149.5
203.88
307.2
306.03
460.8
629.72
1024
30
44.72
70.08
90.79
144
136.28
216
280.43
480
62
31
46.36
72.42
94.11
148.8
141.27
223.2
290.71
496
63
48
74.75
97.44
153.6
146.26
230.4
300.98
512
32
64
See Techdocs PRS1101 for complete listing of all RAID formats
62
© 2009 IBM Corporation
IBM Storage and Technology Group
Intermix of 1 TB SATA Drives
 The same rules governing intermix of Fibre Channel
and FATA drives apply to SATA drives
 Intermix of Fibre Channel, FATA or SATA drives on the
same DA pair is allowed.
 1 TB SATA drive can not be used as a spare in the event
of a failure of FC or FATA drive
 If a spare occurs, the rank will take on the attributes of
the slowest drive in the rank (no change in how this
operates)
 Neither Fibre Channel nor FATA drive can serve as a
spare for the 1 TB SATA drives due to their smaller size
63
© 2009 IBM Corporation
IBM Storage and Technology Group
GUI/CLI Changes
64
© 2009 IBM Corporation
IBM Storage and Technology Group
Major GUI Changes
 Encryption
– Manage encryption key servers
– Manage encryption groups (extent pools)
 Complete revision to create and maintain volumes
– Create multiple LCUs, LSSs and volumes (several new wizards)
– New preview panel to review before create process
– Improvements for large table scrolling
– Performance improvements
– New open systems explorer to see relationships between servers and
volumes
 Support for LDAP functionality
 DSCLI
– Update to support new R4.2 functions
– Installer changes from InstallShield to InstallAnywhere
– New platform OS support
– Additional performance statistics with showioport -metrics
65
© 2009 IBM Corporation
IBM Storage and Technology Group
Innovation that matters
IBM Americas ATS
DS8000 R4.2 LDAP Overview
Brian Sherman
Americas Storage ATS
bsherman@ca.ibm.com
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Authentication Today - Pre-LDAP / R4.2
 All Authentication requests from DSGUI (and other Clients)
managed by Authentication client / server
 Authentication server on the HMC maintains a local security
repository (includes users/role mapping)
 Access to DS8000 only permitted to Authenticated Users
67
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Authentication Support for LDAP in R4.2
Auth
Auth
68
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Release 4.2 Authentication
 Authentication Policy:
– Defines the criteria / mechanism used to perform authentication
– Multiple authentication policies can be defined
– Only one active authentication policy
 Authentication Policy types:
– Basic Authentication policy
• Same as Pre R4.2 (Authorized users assigned to pre-defined DS8000
User Groups)
• Also commonly called Default or Local policy
– Storage Authentication Service (a.k.a. SAS) policy
• This is the policy type for LDAP. Need to map External users and/or user
groups to DS8000 User groups in the policy definition
69
© 2009 IBM Corporation
IBM Storage and Technology Group
Steps for LDAP Implementation
 TPC / SSPC Steps
– Configure Access to LDAP Repository
– Extract certificate
– Create a truststore
 DS8000 Steps
– Create an SAS Authentication policy with information collected
from TPC and LDAP Server
– Test the SAS policy using a valid LDAP user mapped to a
DS8000 User role in the policy
– Activate the SAS policy using a valid LDAP user mapped to
the DS8000 Administrative User role in the policy
70
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 LDAP Recommendations
 Recommendations
– If using SAS authentication, use multiple SSPCs / instances of TPC4.1 and
LDAP
•
If only using a single instance and it goes down, customers cannot logon to DS8000
– Must fix SSPC/TPC4.1, or Call IBM Service to reset authentication back to Basic
– If using SAS authentication, map groups not users
•
Users can be added/removed without changing any policies
– Do not modify the active policy
•
Copy the active policy, make changes to it, test it, then activate it
– Maintain consistency of policies on multiple DS8000s
•
•
•
•
Can use GUI to copy one policy to multiple DS8000s
Can create the same copy on multiple DS8000s at the same time
DSCLI only copies policies to same DS8000
Can use scripts to make same change with the DSCLI on multiple DS8000s
– dscli –hmc1 ds8k_A … chauthpol –activate … myPolicy
– dscli –hmc1 ds8k_B … chauthpol –activate … myPolicy
– dscli –hmc1 ds8k_C … chauthpol –activate … myPolicy
71
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 LDAP Support Requirements
 DS8000 with R4.2 LIC
– Includes DSCLI and GUI support
 TPC4.1
– SSPC future release will include TPC4.1
– Any or other supported TPC server
• http://www01.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1003119
– Preview announce on 02/09
• planned announcement 04/07 with GA 04/10
 Planned Supported LDAP Servers
– IBM Directory Server
– MS Active Directory
– Sun One
72
© 2009 IBM Corporation
IBM Storage and Technology Group
Backup Material
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM Remote Pair FlashCopy
Addendum
74
© 2009 IBM Corporation
IBM Storage and Technology Group
DFSMSdss FlashCopy Commands
>>--+-----------------------------------------------------------|------><
|
|
|------FCTOPPRCPrimary--|-------------------------------|---|
|
|
|
|--PresMirNone---|
|
|
|-----PMN--------|
|
|-----(--|----------------|--)--|
|--PresMirPref---|
|-----PMP--------|
|--PresMirReq----|
|-----PMR--------|
COPY FULL INDD(DASDI1) OUTDD(DASDO1) ADMIN DUMPCONDITIONING
DEBUG(FRMSG(DTL)) FCTOPPRCP(PMP)
75
© 2009 IBM Corporation
IBM Storage and Technology Group
DFSMSdss ADRUFO Parameter List
ADRUFO parameter list is used in the interface between DFSMSdss and
the installation-wide options exit routine (ADRUIXIT), and between DFSMSdss
and the user interaction module (UIM). New bits will be defined in the
ADRUFO mapping macro for the new
FCTOPPRCPRIMARY(PRESMIRREQ|PRESMIRPREF|PRESMIRNONE) keyword:
1. Define new fields, UFO8FLGS, at offset 33 (X’21’) in the
UFOFUNCT mapping.
2. Define the UFOPMREQ bit in UFO8FLGS flags for the new
FCTOPPRCPRIMARY(PRESMIRREQ) option.
3. Define the UFOPMPRE bit in UFO8FLGS flags for the new
FCTOPPRCPRIMARY(PRESMIRPREF) option.
4. Define the UFOPMNON bit in UFO8FLGS flags for the new
FCTOPPRCPRIMARY(PRESMIRNONE) option.
76
© 2009 IBM Corporation
IBM Storage and Technology Group
DFSMSdss Virtual Concurrent Copy (VCC)
ALLOWPPRCONWSDS(YES|NO|PMREQ|PMPREF)
In z/OS 1.10 Virtual Concurrent Copy using FlashCopy function was added.
As part of this function, the ability to use a working space dataset (WSDS) allocated
on a PPRC primary device was enabled using a value in the ANTMIN00 member of
PARMLIB. In order to allow the FlashCopy function within VCC to use a WSDS allocated
on a PPRC primary device, ALLOWPPRCONWSDS(YES) must be specified.
77
© 2009 IBM Corporation
IBM Storage and Technology Group
ICKDSF FlashCopy Commands
PRESERVEMIRROR(REQUIRED|PREFERRED| NO)
FLASHCPY ESTABLISH DDNAME(ddname) TARGETVOL(lss,cca,cuuu)
TGTOKASPPRCPRIM(YES) PRESERVEMIRROR(PREFERRED)
FORCE(NO|YES)
FLASHCPY WITHDRAW DDNAME(ddname) TARGETVOL(lss,cca,cuuu) FORCE(YES)
78
© 2009 IBM Corporation
IBM Storage and Technology Group
ICKDSF FlashCopy Query
FLASHCOPY RELATIONS INFORMATION TABLE
ADDRESSED VOLUME CU SERIAL NUMBER: 0000001711
+--------------------------------------------------------------------------------------------------------------------+
|
ADDRESSED VOLUME INFORMATION
|
PARTNER |
|-------------------------------------------------------------------------------------------------------|
VOLUME
|
|FLASHCPY|
| | |
|
|
| |
|
| |
| | START OF EXTENT | # CONTIG | # TRACKS |
|
|
|
INFO
|
|SEQUENCE|
| | |
|
|
| |
|
| |
| |-----------------| TRKS IN | YET TO |
|
|
|------------|
|NUMBER |R/T|R|FV|BCE|BCP|CRA|VR|SWI|TWP|P|SEVI|PM| SOURCE | TARGET | EXTENT | BE COPIED|SSID|LSS|CCA|SSID|LSS|CCA|
|--------+---+-+--+---+---+---+--+---+---+-+----+--+--------+--------+----------+----------+----+---+---|----+---+---|
|00000000|SRC|F| T| T | F | F | F| F | F |F|FFFF| N|00000000|00000000|
50085 |
50085 |BF62| 19|21 |BF99| 1A|28 |
+--------------------------------------------------------------------------------------------------------------------+
LEGEND
R/T = FLASHCOPY RELATIONSHIP TYPE OF ADDRESSED VOLUME (SRC = SOURCE, TGT = TARGET)
R
= REVERTIBLE (TRUE | FALSE)
FV
= FULL VOLUME RELATION (TRUE | FALSE)
BCE = BACKGROUND COPY ENABLED (TRUE | FALSE)
BCP = BACKGROUND COPY IN PROGRESS (TRUE | FALSE)
CRA = CHANGE RECORDING ACTIVE (TRUE | FALSE)
VR
= VALIDATION REQUIRED (T|F), REPORTED INFORMATION NOT CURRENT AND MAY NOT ACCURATE
SWI = SOURCE EXTENT WRITE INHIBITED (TRUE | FALSE | TFR = WRITE INHIBITED DUE TO FULL REPOSITORY)
TWP = TARGET EXTENT WRITE PROTECTED (TRUE | FALSE)
P
= EXTENTS IN PERSISTENT RELATION (TRUE | FALSE)
SEVI = SPACE EFFICIENT VOLUME INFORMATION LEGEND:
S = VOLUME QUERIED IS SPACE EFFICIENT (TRUE | FALSE)
E = TARGET VOLUME IS SPACE EFFICIENT (TRUE | FALSE) WILL BE FALSE IF VOLUME QUERIED IS A TARGET
V = FLASHCOPY RELATION WILL BE FAILED IF TARGET IS OUT OF SPACE (TRUE | FALSE)
I = FLASHCOPY RELATION IS IN A FAILED STATE (TRUE | FALSE)
PM
= PRESERVE MIRROR RELATIONSHIP INFORMATION LEGEND:
N = NOT A MIRRORED RELATIONSHIP
P = MIRRORED RELATIONSHIP, PREFERRED SPECIFIED
R = MIRRORED RELATIONSHIP, REQUIRED SPECIFIED
S = REMOTE MIRRORED RELATIONSHIP AT PPRC SECONDARY
U = MIRRORED RELATIONSHIP UNDETERMINED
N/A = NOT AVAILABLE
79
© 2009 IBM Corporation
IBM Storage and Technology Group
TSO FlashCopy Commands
PRESERVEMIRROR(REQUIRED|PREFERRED| NO)
FCESTABL SDEVN(X’uadd’) TDEVN(X’uadd’) MODE(NOCOPY) PRESERVEMIRROR(PREFERRED)
For FCWITHDR, SDM will automatically set the force bit on the withdraw CCW,
indicating that if the relationship is a mirrored relation, the withdraw should be
immediate. This will also cause a bit to be set for the target PPRC pair,
indicating that it was previously the target of a preserve mirror relationship that
was withdrawn.
FCWITHDR SDEVN(X’uadd’) TDEVN(X’uadd’)
80
© 2009 IBM Corporation
IBM Storage and Technology Group
TSO FlashCopy Query
SHOWRELS(1-9999|ALL| NO)
STARTADDR(trkaddr)
ANTF0421I FCQUERY Relations – 1
DEVN SSID LSS CCA CU
SERIAL
ACT MAX XC PC CC RV SE SEQNUM
0000 1111 22 33 AAAA 000000044444 555 666 N N N N NN 77777777
RELATIONSHIP DETAIL STARTING TRACK: aaaaaaaa
DEVICE LONG BUSY FOR CG: bbb WRITE INHIBITED: ccc
---------------------------------------------------PARTNER
SOURCE
TARGET
S F C C P C T S F P
LSS CCA SSID START
START
O V O A R R W E S M
--- --- ---- -------- -------- - - - - - - - - - dd ee ffff gggggggg hhhhhhhh i j k l m n o p q r
NO. OF TRACKS: ssssssssss TRACKS TO COPY: tttttttttt
ESTABL: yyyy/mm/dd hh:mm:ss LAST INCR: yyyy/mm/dd hh:mm:ss
dd ee ffff gggggggg hhhhhhhh i j k l m n o p q r
NO. OF TRACKS: ssssssssss TRACKS TO COPY: tttttttttt
ESTABL: yyyy/mm/dd hh:mm:ss LAST INCR: N/A
dd ee ffff gggggggg hhhhhhhh i j k l m n o p q r
NO. OF TRACKS: ssssssssss TRACKS TO COPY: tttttttttt
ESTABL: yyyy/mm/dd hh:mm:ss LAST INCR: N/A
81
© 2009 IBM Corporation
IBM Storage and Technology Group
TSO PPRC CQUERY
************** PPRC REMOTE COPY CQUERY - VOLUME ********************
*
(PRIMARY)
(SECONDARY) *
*
SSID CCA LSS SSID CCA LSS*
*DEVICE
LEVEL
STATE
PATH STATUS SERIALÄ
SERIALÄ
*
*------ --------- ---------- ----------- ----------------- *
* BD00 PRIMARY.. SUSPEND.PM
ACTIVE..
2BE0 00 E0
0123 18 03 *
*
CRIT(NO).......
CGRPLB(NO). 0000000BHYR1 000000027449*
or
************** PPRC REMOTE COPY CQUERY - VOLUME ********************
*
(PRIMARY)
(SECONDARY) *
*
SSID CCA LSS SSID CCA LSS*
*DEVICE
LEVEL
STATE
PATH STATUS SERIALÄ
SERIALÄ
*
*------ --------- ---------- ----------- ----------------- *
* BD00 PRIMARY.. DUPLEX..
ACTIVE..
2BE0 00 E0
0123 18 03 *
*
CRIT(NO).......
CGRPLB(NO). 0000000BHYR1 000000027449*
*
INCRES(NO).
AUTORESYNC(NO)
*
*PAIR WAS THE TARGET OF A WITHDRAWN PRESERVE MIRROR RELATION
*
82
© 2009 IBM Corporation
IBM Storage and Technology Group
ANTRQST FlashCopy Command
The new keyword for the ANTRQST REQUEST=FCESTABLISH is:
PRESMIR=REQ|PREF| NO
The new keyword for the ANTRQST REQUEST=QFRVOLS is:
PRESMIR=NO|PREF|REQ
83
© 2009 IBM Corporation
IBM Storage and Technology Group
DFSMShsm FRBACKUP
>>───┬─────────────────────────────────────────────────────┬────────────────>
└─ALLOWPPRCP──(──┬──┤ A ├──────┬────────────┬─────┬─)─┘
│
└───┤ B ├────┘
│
│
│
└──┤ B ├──────┬────────────┬─────┘
└───┤ A ├────┘
A:
├────FRBACKUP────(─┬─────NO────────────────────────┬─)───────────┤
└─┬─┬─PRESERVEMIRRORNO─┬────────┤
│ ├─PMNO─────────────┤
│
│ └─YES──────────────┘
│
├─┬─PRESERVEMIRRORPREFERRED─┬─┤
│ └─PMPREF──────────────────┘ │
└─┬─PRESERVEMIRRORREQUIRED─┬──┘
└─PMREQ──────────────────┘
B:
├────FRRECOV─────(─┬─────NO────────────────────────┬─)───────────┤
├─┬─┬─PRESERVEMIRRORNO─┬────────┤
│ ├─PMNO─────────────┤
│
│ └─YES──────────────┘
│
├─┬─PRESERVEMIRRORPREFERRED─┬─┤
│ └─PMPREF──────────────────┘ │
└─┬─PRESERVEMIRRORREQUIRED─┬──┘
└─PMREQ──────────────────┘
FRBACKUP ALLOWPPRCP(FRBACKUP(PMREQ | PMPREF | PMNO | NO) FRRECOV(PMREQ | PMPREF | PMNO | NO))
84
© 2009 IBM Corporation
IBM Storage and Technology Group
DFSMShsm FRRECOV
>>───┬─────────────────────────────────────────────────┬──────────────────>
└─ALLOWPPRCP──(─┬───NO────────────────────────┬─)─┘
├─┬─PRESERVEMIRRORNO─┬────────┤
│ ├─PMNO─────────────┤
│
│ └─YES──────────────┘
│
├─┬─PRESERVEMIRRORPREFERRED─┬─┤
│ └─PMPREF──────────────────┘ │
└─┬─PRESERVEMIRRORREQUIRED─┬──┘
└─PMREQ──────────────────┘
FRRECOV ALLOWPPRCP(PMREQ | PMPREF | PMNO | NO)
85
© 2009 IBM Corporation
IBM Storage and Technology Group
DS CLI Remote Pair FlashCopy
 -pmir flag added to mkflash/resyncflash/reverseflash
– pmir parameter requires one of three values:
•
•
•
no – Do not create a Remote Pair FlashCopy
preferred – Create remote FLC, may go Duplex Pending
required – Create remote FLC, but no Duplex Pending
– If –pmir is not specified, behavior defaults to no
 Both lsflash/lsremoteflash display a new “Pmir” column with –l parameter
– The Pmir column has five values:
•
•
•
•
•
86
No – The -pmir parameter was not specified
Preferred – The –pmir parameter was specified and will preserve the target Metro Mirror relationship’s
“Full Duplex” state if possible
Required – The –pmir parameter was specified and will preserve the target Metro Mirror relationship’s
“Full Duplex” state
Remote – The –pmir parameter was specified on a different FLC relationship and this FLC relationship is
the remote pair FLC that was established automatically
Unknown – The Remote Pair Copy status can not be determined due to a conflict in the source and/or
target Metro Mirror status
© 2009 IBM Corporation
IBM Storage and Technology Group
DS CLI Remote Pair FlashCopy
 Normally, removing the FLC relationship on the Metro Mirror Primary volumes
will automatically remove the remote FLC relationship on the Secondary Metro
Mirror volumes
 If there are communications problems, however, the remote FLC relationship on
the Secondary Metro Mirror volumes may not be removed
 Normally, using rmflash on a FLC relationship with a Remote Pair Copy status of
‘Remote’ will fail, leaving the FLC relationship intact
 The rmflash command added an optional –cprm parameter to solve this problem
 The cprm stands for Initiate Background Copy and Terminate Relationship
 Using rmflash on a FLC relationship with a Remote Pair Copy status of ‘Remote’
and the new –cprm parameter will behave as follows:
– If specified on a non-persistent FLC, the -cprm parameter will do the following:
•
•
Copy any remaining tracks from the source volume to the target volume
Terminate the FlashCopy relationship
– If specified on a persistent FLC, the -cprm parameter will do the following:
•
•
•
87
Change the FLC relationship from persistent to non-persistent
Copy any remaining tracks from the source volume to the target volume
Terminate the FlashCopy relationship
© 2009 IBM Corporation
IBM Storage and Technology Group
Remote Pair FlashCopy Do’s and Don’ts


88
Remote Pair FlashCopy operations can be full volume or dataset (track) level. Remote Pair
FlashCopy can be used in combination with the following:
–
Incremental FlashCopy (unless the request is attempting to take an increment using preserve mirror on
a relationship that was established without preserve mirror)
–
copy, nocopy, or nocopy to copy
–
FlashCopy Consistency Groups
–
Fixed Block
Remote Pair FlashCopy cannot be used in combination with the following:
–
Commit
–
Revert
–
Fast Reverse Restore
–
Global Mirror
–
Global Copy
–
Existing copy services conflicts still apply (the remote target cannot be a source, local B cannot be an
XRC primary, etc.)
–
PPRC Incremental Resynchronization started on the PPRC primary that is the target of the relationship.
–
Taking an incremental on an existing incremental relationship that is not a preserve mirror relationship.
–
Cascading PPRC (Metro/Global Mirror or Metro/Global Copy)
–
Space Efficient Volumes
© 2009 IBM Corporation
IBM Storage and Technology Group
Remote Pair FlashCopy Operation Requirements
 Both Local A and Local B must be Metro Mirror primary
devices in full duplex mode with links established and
available
 Remote A and Remote B must reside in the same Storage
Facility Image (SFI)
 The required microcode level must be installed in both the
local and the remote storage control units
89
© 2009 IBM Corporation
IBM Storage and Technology Group
Remote Pair FlashCopy and SMS Volume Selection
 CASE A) Volume is non-FR capable. This case will be handled as before. If FAST REPLICATION was
REQUIRED then this volume is rejected. If FAST REPLICATION was PREFERRED then this volume is
ranked lower than a FR capable volume. The associated message text in the volume entry may be
externalized in the IGD17268I or IGD17279I message.
 CASE B) Volume is FR capable.
– PRESERVE MIRROR was either not specified or specified as NO. This case will be handled as before.
The volume will be eligible for volume selection and will be ranked higher than a similar non-FR
capable volume.
– PRESERVE MIRROR was specified as PREFERRED. This case will also be handled as before. The
‘preserve mirror’ capability of this volume will be IGNORED. The volume will be eligible for volume
selection and will be ranked higher than a similar non-FR capable volume.
– PRESERVE MIRROR was specified as REQUIRED. This volume will be considered eligible for volume
selection if any one of the following conditions is met.
•
•
•
Volume is marked PRESERVE MIRROR capable
VOLUME is marked NOT PRESERVE MIRROR capable because it is not a PPRC volume
VOLUME is marked NOT PRESERVE MIRROR capable because it does not have the new feature installed
The volume will be REJECTED if none of the above conditions are met. The message text
associated with a rejected volume will be preserved in an internal table that also includes a
count of the number of volumes rejected for each particular reason. The count and the
message text may be externalized in a IGD17268I or IGD17279I message.
90
© 2009 IBM Corporation
IBM Storage and Technology Group
ISMF and Remote Pair FlashCopy
Changes will be made in the DFSMSdss/ISMF line operators to support 3
new values for the keyword FCTOPPRCPrimary :
1. PresMirNo
2. PresMirPref
3. PresMirReq.
Updates are made to COPY, CONSOLIDate and DEFRAG in the volume application.
91
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM FlashCopy
Previous Implementation - Establish
Local Storage Server
Remote Storage Server
1. Full Duplex State
•
Local A
z/OS Hyperswap enabled
2. FlashCopy Establish
Metro
Mirror
FlashCopy
•
To MM Primary
•
Remote out-of-sync
3. Duplex Pending
1. full duplex
Local B
Remote B
3. duplex
pending
•
Copy FlashCopy Tracks to
remote
•
Hyperswap disabled until
full duplex
2. Establish
92
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM FlashCopy
Previous Implementation - Withdraw
Local Storage Server
Remote Storage Server
1. Full Duplex State
•
Local A
Hyperswap enabled
2. FlashCopy Withdraw
Metro
Mirror
FlashCopy
•
To MM Primary
•
Remote out-of-sync
3. Duplex Pending
1. full duplex
Local B
Remote B
3. duplex
pending
2. Withdraw
93
•
Restore tracks not
copied A B
•
Copy FlashCopy
Tracks to remote
•
Hyperswap disabled
until full duplex
© 2009 IBM Corporation
IBM Storage and Technology Group
IBM DS8000 Solid State Drives
Addendum
94
© 2009 IBM Corporation
IBM Storage and Technology Group
DFSMS Solid State Device Support
 Dependencies:
– DS8000 SSD microcode and hardware
 Behavioral Changes:
– New I/O statistics in SMF records can help customer to
identify good candidates for placement on SSD drives
– Users can exploit performance advantages of SSD
drives using SMS policy for storage management
– DEVSERV command and DEVTYPE macro identify
volumes backed by SSD
95
© 2009 IBM Corporation
IBM Storage and Technology Group
System Managed Storage
SMS
SC
DC
MC
Logical
User
SG
Physical
Non-Cache
CACHE
Storage
Administrator
Data
ACS
Storage
 User specified criteria via
– Data Class (DC)
– Storage Class (SC)
– Management Class (MC)
– Storage Group (SG)
 User control via ACS routines
 Provides base for functional support
96
© 2009 IBM Corporation
IBM Storage and Technology Group
Defining Data Set Service Levels
97
© 2009 IBM Corporation
IBM Storage and Technology Group
System Managed Storage - SSD
SMS
SC
DC
MC
Logical
User
SG
CACHE
CACHE
Solid State Device
Storage
Administrator
Data
98
Physical
ACS
Storage
© 2009 IBM Corporation
IBM Storage and Technology Group
Storage Class
 Performance Objectives
– Direct bias
– Direct millisecond response
– Initial access response
– Sequential millisecond response
– Sustained data rate
 Availability Objectives
– Accessibility
– Availability
– Guaranteed space
– Guaranteed synchronous write
 Coupling Facility Caching Attributes
– Coupling facility cache set name
– Coupling facility direct weight
– Coupling facility sequential weight
99
© 2009 IBM Corporation
IBM Storage and Technology Group
DFSMS Policy Based Storage Management
 DFSMS maintains a table for each supported device
of performance capabilities
– Each entry is in units of millisecond response time (MSR)
– A set of MSR values is assigned for random access read and
writes, and sequential reads and writes.
– Separate MSR values are provided for cache access and disk
access
– DFSMS takes the MSR values (0 to 999) provided by each
device table and inserts each into one of 28 discrete bands.
– When a data set allocation request is made, SMS attempts to
match the requesting MSR of the storage class associated with
the data set with one of the 28 MSR bands.
100
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Policy Based Storage Management for SSD
 New MSR value for cache read and native read for volumes backed by
SSD
 All other MSR values remain the same as 2107 HDD
 How to favor to SSD Selection over non-SSD
– Assign a storage class with Direct MSR of 1, DIRECT Bias of R
(and not specify any values for sequential MSR or sequential Bias).
 To direct storage allocation away from SSD, specify:
– DIRECT MSR = 6, DIRECT BIAS = R
 Or, create a Storage Group consisting of only SSD backed
volumes
101
© 2009 IBM Corporation
IBM Storage and Technology Group
When are ACS Routines Invoked for Data Sets?
 &ACSENVIR
– ALLOC
default)
for new data set allocations (this is the
– ALLOCTST for a pre-allocation or allocation test
environment.
– CONVERT for data set convert in place operations
– RECALL
for data set recall operations
– RECOVER for data set recover operations
– RENAME
102
for data set alter rename operations
© 2009 IBM Corporation
IBM Storage and Technology Group
Other DFSMS Changes for SSD

DEVSERV QDASD
– Displays device attributes with new ATTR keyword
ds qd,d300,attr
IEE459I 16.59.01 DEVSERV QDASD 613
C
UNIT VOLSER SCUTYPE DEVTYPE
CYL SSID SCU-SERIAL DEV-SERIAL
EFC
ATTRIBUTE/FEATURE
YES/NO ATTRIBUTE/FEATURE
YES/NO
D300 TK9085 2107921 2107900 65520 2401 0175-02411 0175-02411 *OK
SOLID STATE DRIVES
Y
ENCRYPTION
N

DEVTYPE macro
– With INFO=DASD, indicates if a volume is backed by solid
state drives
103
© 2009 IBM Corporation
IBM Storage and Technology Group
DFSMS Externals for SSD Support
 Vendor exposure/utilization:
– No changes needed to benefit from improved performance
 Communications to other z/OS platform products and/or vendors:
– IGWSMF macro (new I/O statistics added to SMF record 42
subtypes 5 & 6)
– DEVTYPE macro (identifying SSD)
 Publication Changes: distributed in R10 refresh
–
–
–
–
104
DFSMS Storage Admin Reference SC26-7402
z/OS MVS System Management Facilities (SMF) SA22-7630
z/OS MVS System Commands SA22-7627-18
z/OS MVS System Messages VOL 7 (IEB-IEE) SA22-7637-16
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Authentication Policies and
Implementation Steps
105
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Basic Authentication Policy
 Features:
– Only one instance
– Cannot be copied or deleted
– Legacy User Administration
 Actions:
– Activate Authentication policy
– Test Authentication policy
– Properties
106
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Storage Authentication Service Policy
 Features:
– Uses a proxy to contact the external repository (for example: LDAP Server)
– Proxy used is a Tivoli Component (Embedded Security Services a.k.a.
Authentication Service) – is part of TPC 4.1
– Multiple instances of SAS policies supported, but only 1 active at a time
 Actions:
– Create a SAS policy
– Activate Authentication policy
– Test Authentication policy
– Delete Authentication policy
– Copy Authentication policy
– Properties
107
© 2009 IBM Corporation
IBM Storage and Technology Group
Information Required for SAS Policy
 Authentication Service URL
– https://<tpc_server_host>:16311/TokenService/services/Trust
– Example: https://mdm-b26w2k3.storage.usca.ibm.com:16311/TokenService/services/Tru
st
 Authentication Service Client User ID/Pwd
– Example: TPCSuperUser, DSUser, etc
 Truststore file with Certificate for SSL/Pwd
 LDAP users and/or user groups to map to DS8000 User
Roles
108
© 2009 IBM Corporation
IBM Storage and Technology Group
SSPC (TPC) Steps for LDAP Authentication
1. Configure access to LDAP repository
2. Extract Certificate
– Used for securing communication between
Authentication Client on HMC and
Authentication Service (server component)
on SSPC
3. Create a truststore which includes the
certificate from #2
109
© 2009 IBM Corporation
IBM Storage and Technology Group
TPC Step 1 – Configure Access to LDAP Repository
TIP UI
110
© 2009 IBM Corporation
IBM Storage and Technology Group
TPC Step 2 – Extract certificate
This certificate is needed for securing SSL communication between the
Authentication client (on HMC) and server component of Authentication
service (on SSPC)
111
TIP UI
© 2009 IBM Corporation
IBM Storage and Technology Group
TPC Step 3 – Create a truststore
Launch the ikeyMan tool
(included with TPC)
TIP UI
Provide the name and
location of the file to
be generated
112
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Step 1 – Create an SAS policy – GUI panel 1 –
Authentication Service
113
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Step 1 – Create an SAS policy – GUI panel 2 Truststore
114
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Step 1 – Create an SAS policy – GUI Panel 3 LDAP Users Map to Role
115
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Step 2 – Test the SAS policy
116

Provide a valid LDAP User ID and Password

User ID must already be mapped to a valid DS8000 user
role in the SAS policy
© 2009 IBM Corporation
IBM Storage and Technology Group
DS8000 Step 3 – Activate the SAS policy
117

Provide a valid LDAP User ID

User ID must be mapped to DS8000 Administrator User role
© 2009 IBM Corporation
IBM Storage and Technology Group
Additional DS8000 GUI
Screenshots
118
© 2009 IBM Corporation
IBM Storage and Technology Group
Main User Administration Page
119
© 2009 IBM Corporation
IBM Storage and Technology Group
Main User Administration Page – with actions
120
© 2009 IBM Corporation
IBM Storage and Technology Group
Manage Authentication Policy – Lists all policies on the
selected storage complex(es)
121
© 2009 IBM Corporation
IBM Storage and Technology Group
Manage Authentication Policy – Actions for Basic (nonLDAP) policy type
122
© 2009 IBM Corporation
IBM Storage and Technology Group
Basic Authentication Properties
123
© 2009 IBM Corporation
IBM Storage and Technology Group
Basic Authentication Properties – Actions – Launches
panels similar to what is in current DS8K GUI
124
© 2009 IBM Corporation
IBM Storage and Technology Group
Basic Authentication Properties – Add User
125
© 2009 IBM Corporation
IBM Storage and Technology Group
Manage Authentication Policy – Actions for SAS
(LDAP) policy type
126
© 2009 IBM Corporation
IBM Storage and Technology Group
SAS Properties
127
© 2009 IBM Corporation
IBM Storage and Technology Group
SAS Copy Authentication Policy
 Copy function allows a SAS policy to be copied onto the
same storage complex, or onto one or more other storage
complexes
 The target storage complexes are the same ones as
selected from the storage complex list on the main user
administration page
 Copy function copies all aspects of the SAS policy,
including the truststore, making it very simple to activate
the same SAS policy on other complexes.
– User only has to copy the policy and then activate it
(assuming the additional complexes have connectivity to the
same SSPC)
128
© 2009 IBM Corporation
IBM Storage and Technology Group
SAS Copy Authentication Policy
129
© 2009 IBM Corporation
IBM Storage and Technology Group
Additional TPC Screen Shots
130
© 2009 IBM Corporation
IBM Storage and Technology Group
TPC Install Panels for LDAP Info - 1
131
© 2009 IBM Corporation
IBM Storage and Technology Group
TPC Install Panels for LDAP Info - 2
132
© 2009 IBM Corporation
IBM Storage and Technology Group
TPC Install for LDAP Info - 3
133
© 2009 IBM Corporation
IBM Storage and Technology Group
TPC Install Panels for LDAP Info - 4
134
© 2009 IBM Corporation
IBM Storage and Technology Group
Disclaimers
Copyright © 2009 by International Business Machines Corporation.
No part of this document may be reproduced or transmitted in any form without written permission from IBM Corporation.
Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This information could
include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or programs(s) at any time
without notice.
Unless otherwise note, the performance data contained herein was obtained in a controlled, isolated environment. Actual results that may be obtained in
other operating environments may vary significantly. While IBM has reviewed each item for accuracy in a specific situation, there is no guarantee that the
same or similar results will be obtained elsewhere. Other data may have been obtained from publicly available documents or sources. In such cases,
IBM has endeavored to provide comparable measurements for systems being compared.
References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services
available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this document is not intended to state or
imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM’s intellectually property rights, may be
used instead. It is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program or service.
The information provided in this document is distributed "AS IS" without any warranty, either express or implied. IBM EXPRESSLY DISCLAIMS any
warranties of merchantability, fitness for a particular purpose OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM
products are warranted according to the terms and conditions of the agreements (e.g., IBM Customer Agreement, Statement of Limited Warranty,
International Program License Agreement, etc.) under which they are provided. IBM is not responsible for the performance or interoperability of any nonIBM products discussed herein.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available
sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other
claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights.
Inquiries regarding patent or copyright licenses should be made, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
135
© 2009 IBM Corporation
IBM Storage and Technology Group
Trademarks
The following terms are trademarks or registered trademarks of the IBM Corporation in either the United
States, other countries or both.
IBM, S/390, ES/3090, ES/9000, AS/400, RS/6000, MVS/ESA, OS/390, VM/ESA, VSE, TPF, OS/2, OS/400,
AIX,, FlashCopy, z/VM, z/OS, POWER5, POWER5+, DB2, Universal Database
DFSMS/MVS, DFSMS/VM, , DFSMSdfp, DFSMSdss, DFSMShsm, DFSMSrmm, BladeCenter,
FICON, ESCON, TotalStorage, Enterprise Storage Server, iSeries, pSeries, xSeries, zSeries, System z,
System z9, System i, System i5, System p, System p5, System x, System Storage
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other
countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel
SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its
subsidiaries in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
136
© 2009 IBM Corporation