Professional Documents
Culture Documents
Agenda
Flex System Hardware Overview SAS Networking Clustering and Network Integration Management Virtualization Overview Array Configuration Advanced Functions
The Flex System V7000 Storage node fits within the Flex Enterprise chassis to provide integrated storage and servers in a single package
Runs the exact same software as the Storwize V7000 and SAN Volume Controller (SVC)
The host attachment networks must always be configured in 2 pairs when used with the Flex System V7000 A reliable power supply source and cooling
Control Enclosure
Expansion Enclosure
5 2013 IBM Corporation
Internal Components
HIC card 2 FC or 10gigE Full Wide Node Canisters HIC card 1 10gigE only
Drive Options
The following drives are supported in the Flex System V7000:
2.5" 10k SAS HDD, 300GB (Seagate / Hitachi) 2.5" 10k SAS HDD, 600GB (Seagate / Hitachi) 2.5" 10k SAS HDD, 900GB (Seagate / Hitachi) 2.5" NL SAS, 500GB (Seagate) 2.5" NL SAS, 1TB (Seagate) 2.5" 15k SAS, 146GB (Seagate) 2.5" 15k SAS, 300GB (Seagate) 2.5" SSD SAS, 200GB (Hitachi) 2.5" SSD SAS, 400GB (Hitachi)
LFF 3.5 NL_SAS drives in 2/3/4TB capacities are available by using Storwize V7000 expansion enclosures
One internal 10/100/1000 Mb/s Ethernet for management (no iSCSI) One external 6 Gb/s SAS wide port (24Gb aggregate) and usage optional Two external USB Ports (not used for normal operation) One Battery
SAS Networking
10
11
12
The control enclosure MUST be cabled with Flex System V7000 expansion enclosures before the Storwize V7000 expansion enclosures All Flex System V7000 expansion enclosures must be in the same Flex Enterprise chassis as control enclosure
13 2013 IBM Corporation
Flexible Configuration
Integrated into the Flex Enterprise chassis
Flex Chassis
Storage ITE Dual Controller Storage ITE JBOD Storage ITE JBOD
Flex Chassis
15
Cluster
Expand
Expand
An I/O Group is a control enclosure and its associated SAS attached expansion enclosures Clustered system can consist of 2-4 I/O Groups Scale capacity/throughput 4x
Up 960 internal drives in 40 enclosures within two 42U racks
No interconnection of SAS chains between control enclosures as control enclosures communicate via FC Expansion Enclosures Expansion Enclosures Expansion Enclosures
Non-disruptive upgrades
From smallest to largest configurations Purchase hardware only when you need it
No extra feature to order and no extra charge for a clustered system
Cluster
An I/O Group is a control enclosure and its associated SAS connected expansion enclosures
16 2013 IBM Corporation
Virtualize external storage arrays behind Flex System V7000 for even greater capacity and throughput
Recommended FC connectivity is via a FC top of rack switch or via an existing Brocade/Cisco FC SAN
Can interconnect FC switch modules in Flex Enterprise chassis via ISls if desired in lieu of using a TOR switch
17
18
All FCoE traffic via mid-plane to integrated switch Easily integrated into customer FC SAN
Virtualize other FC storage via FCoE connection
Black line is FCOE Red line is Fibre Channel Green line is Ethernet
LOM or CN4054 (pNIC, vNIC mode) Flex System V7000 Storwize V7000 FCoE
19
Management
20
Storage Node 01
21
Insert Flex System V7000 Node Wait 5 minutes for power up Use chassis map task to launch browser to Easy Setup Wizard
22
23
23
24
24
25
Virtualization Overview
26
Servers
Servers
Servers
External Array
Internal
Increases disk utilization and reduces hot spots Improves administrative productivity by up to 2X
External
External arrays inherit all Storwize V7000 functions Extends life of existing storage arrays Optional feature
Migrate
Migrate data from external LUNs to Flex System V7000 Thin or fully provisioned target volumes Included at no cost for 45 days from migration start
27
Control enclosure with 2 node canisters (NC) makes up an I/O Group and owns given volumes
Volumes NC NC
NC
Control Enclosure
Control Enclosure
Control Enclosure
Control Enclosure
28
Control Enclosure
Control Enclosure
29
Volumes
Storage Pool
30
Managed Disks
The basic unit of storage in the Flex System V7000 is the managed disk or MDisk for short A managed disk must be protected by RAID to prevent loss of the entire storage pool In Flex System V7000 we can have two different types: Internal Array MDisk The internal RAID implementation inside the system takes drives and builds a RAID array with protection against drive failures External SAN attached MDisk An external storage system provides the RAID function and presents a Logical Unit (LU) to the Flex System V7000
31
Storage Pools
A storage pool is a collection of managed disks The primary property of a storage pool is the extent size which by default using the GUI is 256MB
This extent size is the smallest unit of allocation from the pool
When you add managed disks to a pool they should have similar performance characteristics:
Same RAID level Roughly the same number of drives per array Same drive type (SAS, NL SAS, SSD except if using Easy Tier) Similar performance characteristics for external storage system MDisks
This is because data from each volume will be spread across all MDisks in the pool, so the volume will perform approximately at the speed of the slowest MDisk in the pool
The exception to this rule is that if using Easy Tier you can have 2 different tiers of storage in the same pool but the MDisks within the tiers should still have the same performance characteristics
32
Volumes
A1 A2 A3 A4 A5 A6 A7 A8 A9 B1 B2 B3 B4 B5 B6 B7 B8 C1 C2 C3 C4 C5 C6 C7 C8
Volumes Managed Disks Volume A
A1 A5 A9 B4 B8
A2 A6 B1 B5 C1
A3 A7 B2 B6
A4 A8 B3 B7
When the managed disks are added into storage pools, the managed disks are split into chunks of storage known as extents The size of these extents is a property of the storage pool Default is 256MB Whenever you create a new volume you must pick a single storage pool to provide the physical capacity By default the created volume will stripe all of its data across all the managed disks in the storage pool as shown on the left diagram Thin provisioned volumes consume extents only as actual data is written to disk
Storage Pool
33 2013 IBM Corporation
Array Configuration
34
The Flex System V7000 system will contain a number of drive objects, but these drives cannot be directly added to storage pools The drives need to be included in a Redundant Array of Independent Disks (RAID) to provide protection against the failure of individual drives
35
35
More details about the what the RAID levels actually mean is available at URL below:
http://en.wikipedia.org/wiki/RAID
36
36
In Flex System V7000 a RAID Array is created at the point that you add the array into the storage pool When the array is created a managed disk also called a MDisk is created the full useable capacity of the array Wizards and Presets are available to suggest configurations to users based on the hardware attached to the system If the MDisk built on internal storage is ever removed from the pool, then the array and the associated managed disk is unconfigured Drives go back to candidate status to be used to create another array
37
37
A one click GUI setup exists to configure all drives into RAID arrays
Solid state drives will be configured as RAID 1 with 2 members and 1 spare SAS drives will be configured as RAID 5 with 8 members and 1 spare Near line SAS drives will be configured as RAID 6 with 12 members and 1 spare
38
38
39
39
40
40
41
41
The spare system will prefer best possible match based on the following parameters:
Technology type
SAS vs SSD vs. NL-SAS
Speed/RPM Capacity
42
42
Advanced Function
43
FlashCopy Included
Allows use of FlashCopy function with internal Flex System V7000 volumes as well as external storage under Flex System V7000 management FlashCopy Manager optionally available to help automate function
44
Compression Optional
Allows for in-band compression of data to minimize use of physical capacity
Questions?
45 2013 IBM Corporation
47
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both.
Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. Those trademarks followed by are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States.
48