IBM Enterprise torage erver for OpenVM 26. DECU ymposium, Bonn 2003: 2C02 Torsten Rothenwaldt IBM Germany Agenda! E architecture! Hardware overview; E as eascape storage server! Component details and configuration options! Copy services! FlashCopy! PPRC! Management interfaces! OpenVM as host system! upported configurations! OpenVM-specific guidelines! Copy ervices CLI for OpenVM
E Model 800 Hardware ummary "Disk 8-Packs #A-Box: 16 8-packs #B-Box: 32 8-packs 18.2 / 36.4 / 72.8 GB (10 k / 15 k RPM) 145.6 GB (10 k RPM) #55.9 (44.0) TB #64 non-arbitrated back end paths (A) "MP / Cache #tandard (4 CPUs) and Turbo (6 CPUs) options #64 GB cache #2 GB NV "Host Bays / Adapters #Up to 16 host adapters in 4 bays 2 Gb FC / FICON ECON CI "Power ystem $Three-phase power $8.5 kw with battery $Mirrored power for each electronics drawer (6 supplies per side) High-Level Design Overview Host Adapters N-way MP RAID Adapters Host Adapters Volatile memory Persistent memory Host Adapters Common Parts Interconnect Volatile memory Persistent memory Host Host Adapters Adapters N-way MP RAID Adapters! eascape architecture! nap-in building blocks:! peries server with PowerPC processors! A PCI RAID adapters! A disk enclosures %Design based on best IBM technologies developed by many laboratories
E as eascape torage erver! MP PowerPC processors %!Upgrade options!tability under high workload! erver PCI architecture %!erver path handling!independent back-end! 64-bit O on internal HDD %!Address space, scheduling!maintenance, features! Common Parts Interconnect %!Transparent multipathing!flexible adapter options! Based on standard peries %!Cache design! Cluster architecture %!Entry configuration!floor space!power and cooling Processing Clusters and Caches Cache Cluster 1 NV NV Cluster 2 Cache! 4 or 6 PowerPC per cluster! Up to 32 GB ECC cache per cluster (non-shared)! Managed in 4 kb segments! Adaptive algorithm based on statistics! NV (1 GB per cluster) stores a second copy of write data from the other cluster (for 72 hours)! Managed in 4 kb segments by LRU algorithm
Disk Eight-Packs, Device Adapters and Loops 18 GB 36 GB 72 GB 3+3+2 4+4 3+3+2 4+4 6+P+ 6+P+ DA DA RAID 10 RAID 10 RAID 5! 2 A loops per device adapter; up to 48 disks per loop! Arrays configured in ranks (= pair of eight-packs of same HDD type)! RAID-5 or RAID-10 or mix per rank; RAID processing by adapter! Mix of different eight-pack types per loop! Two floating hot-spare HDDs per capacity per loop RAID Array Capacities RAID 5 Array DDMs in 8-Pack Physical Capacity Effective Capacity Effective Capacity (6 + P + ) (7 + P) 18.2 GB 145.6 GB 105.20 GB 122.74 GB 36.4 GB 291.2 GB 210.45 GB 245.53 GB 72.8 GB 582.4 GB 420.92 GB 491.08 GB 145.6 GB 1164.8 GB 841.84 GB 982.16 GB RAID 10 Array DDMs in 8-Pack Physical Capacity Effective Capacity Effective Capacity (3 + 3 + 2) (4 + 4) 18.2 GB 145.6 GB 52.50 GB 70.00 GB 36.4 GB 291.2 GB 105.12 GB 140.16 GB 72.8 GB 582.4 GB 210.39 GB 280.52 GB 145.6 GB 1164.8 GB 420.78 GB 561.04 GB
Rank Configuration in E pecialist GUI Host Adapters! 16 adapters in 4 bays: any combination of cards! Fibre Channel (1 port per adapter, auto speed detection 1 Gb / 2 Gb, longwave or short-wave option)! FICON (1 port per adapter, auto speed detection 1 Gb / 2 Gb)! ECON (2 ports per adapter)! CI (2 ports per adapter, Differential Fast Wide 40 MB)! Fibre Channel implementation:! WWID-based LUN masking, virtual LUN assignment! Any host may access all adapters or can be restricted to some adapters! Host path switch does not change E-internal paths
Copy ervices: FlashCopy Time ource Target Copy data command issued Copy target is available immediately Write Read Read and write to both source and copy target possible Optional background copy When background copy is complete, relationship between source and target ends! Volume-level point-in-time copy! With or without creation of full copy Copy ervices: Peer-to-Peer Remote Copy 4 1 2 3! Volume-level synchronous remote copy (up to 103 km)! XD option (non-synchronous) for long distance! Warning: Host-configured PPRC targets are always visible!! Warning: Allow target mount only with PPRC uspend, please!
Management Interfaces! E Management tation (Linux-based, up to 8 E)! Web user interfaces:! pecialist (default; all configuration tasks)! Expert (optional; performance, asset, capacity management)! Command Line:! torage Management CLI! Copy ervices CLI! API (NIA Bluefin CIM agent)! Modem (call-home, remote service access) Tru64 and OpenVM upport! Minimum versions for Tru64:! CI: V4.0D (KZPBA-CB), AE V1.6, TruCluster 5.0A! FC: V4.0F (KGPA-BC, KGPA-CA), AE 1.6, TruCluster 5.0A! Minimum versions for OpenVM:! CI: V6.2-1H3 (KZPBA-CB; no allocation class support)! FC: V7.2-1 (KGPA-CA; KGPA-DA soon; no FC-AL support)! No VAX support! No restrictions with respect to clustering or copy services.! For E model and LIC requirements see interoperability matrix. (special requests via RPQ)
OpenVM FC Volume Configuration! OpenVM unit number (UDID) implemented as internal ACII label! Access via torage Management CLI OpenVM Unit Number OpenVM devices $1$DGA2001, $1$DGA2002, $1$DGA2003, $1$DGA2004
OpenVM I/O pecifics! Exclusive E adapters required for OpenVM! OpenVM FC driver cannot handle Abort Task equence sent at failover or quiesce points (volume remains in MountVerify)! E adapter suppresses ABT when configured for OpenVM! Any non-openvm access resets to default! Command Communication LUN (CCL)! OpenVM considers LUN 0 as CCL (independent on UDID)! Recommendation: small dummy LUN (UDID % device $1$GGAn)! MOUNT/HADOW=(...)/OVERRIDE=NO_FORCED_ERROR! hadow driver uses CI commands READL/WRITEL with intentionally incorrect ECC to emulate Digital torage Architecture bad block handling! Can cause significant performance degration and wrong error counts! ame disk geometry on different E models Copy ervices CLI for OpenVM! OpenVM native software package:! Registered OpenVM facility with unique status codes! Distribution kit creates PCI$DETINATION:[IBM2105...]! Command images, JRE, command help, message help! DCL procedures for startup/shutdown, login, IVP, re-linking! Features:! Displays mapping of OpenVM unit numbers and E volumes! Tests connection to E copy services server! Manages host view of volumes in E copy services server! Queries status of volumes! Executes copy services tasks! Monitors completion status of copy services tasks
Copy ervices CLI Example: rslist2105s VM1$ show device gga! LUN 0 considered by OpenVM as CCL Device Device Error Name tatus Count $1$GGA1000: Online 0 VM1$ show device dga! AllocationClass=1 automatically Device Device Error Volume Free Trans Mnt Name tatus Count Label Blocks Count Cnt $1$DGA1001: (VM1) Mounted 0 QUORUM 1952886 1 1 $1$DGA1002: (VM1) Mounted 0 V73_COMMON 1067115 357 1 $1$DGA1003: (VM1) Online 0 $1$DGA1004: (VM1) Online 0 $1$DGA1005: (VM1) Online 0 VM1$ rslist2105s! Tool from E Copy ervices CLI disk name 2105 serial number ------------ ------------------ _$1$DGA1001 00C22399! Format of E volume numbers: _$1$DGA1002 00D22399! 1-3 = E-internal volume id _$1$DGA1003 00E22399! 4-8 = E serial number _$1$DGA1004 00F22399 _$1$DGA1005 01022399 VM1$ More Information! E Documentation et http://www.storage.ibm.com/hardsoft/products/ess/ess.htm! Planning Guide! Host Attachment Guide, Interoperability Matrix! User s Guide, Web Interface User s Guide, CLI User s Guide! IBM Redbooks http://www.redbooks.ibm.com/! G24-6424 IBM Enterprise torage erver Model 800! G24-5757 E Copy ervices for Open ystems
Disclaimers Product data is accurate as of initial publication and is subject to change without notice. No part of this presentation may be reproduced or transmitted in any form without written permission from IBM Corporation. References in this document to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM program product in this document is not intended to state or imply that only IBM's program product may be used. Any functionally equivalent program may be used instead. Future plans and announcements are subject to change. The information provided in this document has not been submitted to any formal IBM test and is distributed "As Is" basis without any warranty either express or implied. The ue of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer's ability to evaluate and integrate them into their operating environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk. Trademarks The following terms are trademarks or registered trademarks of the IBM Corporation in either the United tates, other countries or both. IBM, /390, E/3090, E/9000, A/400, R/6000, MV/EA, O/390, VM/EA, VE, TPF, O/2, O/400, AIX, DFM/MV, DFM/VM, ADTAR Distributed torage Manager, DFMdfp, DFMdss, DFMhsm, DFMrmm, FICON, ECON, Magstar, eascape, Totaltorage, Enterprise torage erver, ieries, peries, xeries, zeries Windows NT is a registered trademark of Microsoft Corporation. Other company, product, and service names mentioned may be trademarks or registered trademarks of their respective companies.