Ibm Xiv Storage System Technical Overview: Americas Advanced Technical Support

IBM XIV™ Storage System
Technical Overview
Americas Advanced Technical Support
Alison Pate patea@us.ibm.com
Brian Sherman bsherman@ca.ibm.com
Hank Sautter sautter@us.ibm.com
Jim Sedgwick jsedgwic@us.ibm.com
© 2008 IBM Corporation

Agenda
 IBM XIV Storage System Overview and Architecture

– Hardware and Software features
– Ordering Information
– Virtualization Capabilities
– Reliability and Serviceability
 IBM XIV Software V10 Functionality

– Thin Provisioning
– Snapshot
– Synchronous Mirroring
– Data Migration
 Manageability
 Installation Planning
 ATS XIV Technical Deep Dive Session Plans
2 © 2008 IBM Corporation

IBM XIV Storage System
Overview and Architecture

IBM XIV Storage System Unique Architecture
 Virtualized grid storage:

– Data distribution across all drives
– No RAID groups to manage
 Automatic load balancing

– Consistent performance
– No manual intervention
 Thin Provisioning
 High Performance, flexible Snapshots
 Remote Replication
 Browser based management
 Built in Data migration
IBM XIV Storage

IBM XIV Storage System Grid Architecture
Host Host Host Host Host
User Switch (FC/Ethernet)
Switch 1 Switch 2

IBM XIV Storage System Hardware Platform
Machine Type: 2810-A14

 180 disks per rack
– 15 modules per rack
• 12 disks per 2U module
– 1TB 7200RPM SATA disk drives
 Single rack provides 80TB usable capacity

 120GB of system cache per rack (8GB per
module)
 Up to 24 4GB FC host ports
 6 1Gb iSCSI host ports
 3 UPS systems
IBM XIV Storage

IBM XIV Hardware System Components
 42U Rack Module 15 (Data)

Module 14 (Data)
 15 2U Modules Module 13 (Data)
Module 12 (Data)
– 9 Data Modules Module 11 (Data)
• 12 1TB SATA drives Module 10 (Data)
– 6 Data + Interface Modules Module 9 (Data + Interface)

Module 8 (Data + Interface)
• 12 1TB SATA drives Module 7 (Data + Interface)
• 2 Dual ported 4Gb FC Ethernet Switch, Maintenance
Module, Redundant PS
• 2 1Gb port for iSCSI/mgmt interface Module 6 (Data + Interface)
 1 1U Maintenance Module Module 5 (Data + Interface)

 2 Redundant power supplies Module 3 (Data)

Module 2 (Data)
 2 48 port 1GbE switches Module 1 (Data)

UPS 3
 3 UPS UPS 2
UPS 1

IBM XIV Storage System Software
Software Functions
 Thin Provisioning
 Snapshot
 Synchronous Mirroring
 Data Migration

IBM XIV Storage System Hardware Structure
 1xxx Modules  Host Attachment Cables (30meter)

– 3900 Ethernet cable
– 1100 Interface Module - Quantity 6 – 3910 Fibre cable (50 micron LC/LC)
– 1105 Data Module - Quantity 9 – 3920 Fibre cable (50 micron LC/SC)
– 1110 CoD Interface Module - Quantity 6
– 1115 CoD Data Module - Quantity 9  Attachment Indicators
– 1119 CoD 5.25TB Activation - Quantity 4 (min) – 0100 UNIX host attachment
– 0101 Linux host attachment
– 0102 Windows host attachment
 9xxx Infrastructure and Specify Features – 0103 VMWare host attachment
– 9000 Maintenance Module - Quantity 1

– 9101 Modem - Quantity 1
 Weight Reduction
– 0200 – Weight Reduction Feature
– 9800 Single phase power - Quantity 1
– Single phase line cords
• 9801 US/Canada/LA/AP line cord - Quantity 2
• 9802 US Chicago line cord - Quantity 2
• 9803 EMEA line cord - Quantity 2
• 9804 Israel line cord - Quantity 2

IBM XIV Storage System Software V10 Structure
 Base PID
– 5639-XXA: XIV software use authorizations with software maintenance
• Includes all IBM XIV Storage System Software functions
• Per Module feature
 Software Maintenance 1 Year

– 5639-XX1:
• Software Maintenance No Charge Registration
• Software Maintenance Renewal - 1 Year
– 5639-XX2: Software Maintenance After License - 1 Year
 Software Maintenance 3 Years

– 5639-XX3: Software Maintenance Registration - 3 Years
– 5639-XX4: Software Maintenance Renewal - 3 Years
– 5639-XX5: Software Maintenance After License - 3 Years

Hardware

IBM XIV Architecture: Nine Data Modules
 Contains cache, disk and any-to-any Module Module 15 (Data)
connectivity Module 14 (Data)
– 8 1GB System Cache DIMMS Module 13 (Data)
– Dual write mechanism provides cache redundancy Module 12 (Data)
• Writes completed to two different data modules cache Module 11 (Data)
– 12 1TB SATA Drives
Module 10 (Data)
– 2 1GbE ports for any to any Interface Module and Data Module
connectivity Module 9 (Data + Interface – FC / iSCSI)
Module 8 (Data + Interface – FC / iSCSI)
 Provides redundant power and cooling Ethernet Switch, Maintenance
– Two power supplies Module, Redundant PS
– Ten fans per module Module 6 (Data + Interface – FC)
Module 5 (Data + Interface – FC)
 Independent caching allows efficient performance Module 3 (Data)
Module 2 (Data)
Module 1 (Data)
 Manage data migration, rebuild and redistribution
operations UPS 3
UPS 2
UPS 1

IBM XIV Architecture: Six Data + Interface Modules
 Provides FC / iSCSI host, any-to-any Module Module 15 (Data)

connectivity, cache and disk Module 14 (Data)
– 2 Dual-port 4Gb Fibre Channel adapters
Module 13 (Data)
• Modules 4 – 9 provide FC Host Connectivity
Module 12 (Data)
– 2 Quad-port 1Gb Ethernet adapters
• Two ports for any to any Module connectivity Module 11 (Data)
• Modules 4 – 6 provide Management function Module 10 (Data)
• Modules 7 – 9 provide iSCSI Host Connectivity Module 9 (Data + Interface – FC / iSCSI)
– 12 1TB SATA Drives
– 8 1GB System Cache DIMMS
Ethernet Switch, Maintenance
 Provides redundant power and cooling Module, Redundant PS
– Two power supplies
– Ten fans per module Module 5 (Data + Interface – FC)
Module 3 (Data)
 Active-active multipath (load balancing) provided Module 2 (Data)
by the host Module 1 (Data)
UPS 3
 Each module works independently UPS 2

UPS 1

IBM XIV Architecture: Management Software
 Provides front-end for management by the user

 Out of band management over separate GbE ports
 A floating component
– One active manager and two backup
– Before the manager executes a transaction, it’s logged on backup
• If the active manager fails, backup will become active and complete the task
 Both CLI and GUI capability installed on user workstations
– GUI generates CLI commands
Interface Interface Interface

Module Module Module
Internal Switch 1 Internal Switch 2
Data module Data module Data module

IBM XIV Architecture: Three UPS Modules
Module 15 (Data)
 Maintains an internal power in the event Module 14 (Data)
of temporary failure of the external Module 13 (Data)
power supply Module 12 (Data)
Module 11 (Data)
Module 10 (Data)
 In case of continuous external power Module 9 (Data + Interface)
failure Module 8 (Data + Interface)

– UPS module complex maintains power long Ethernet Switch, Maintenance
enough to allow a safe and ordered shutdown Module, Redundant PS
 UPS complex can sustain the failure of Module 3 (Data)
one UPS unit, while protecting against Module 2 (Data)
external power disorders Module 1 (Data)
UPS 3
UPS 2
UPS 1

Capabilities
Virtualization

IBM XIV Unique Data Distribution Algorithm
 Each volume is spread across all 180 drives
 Data is divided into 1MB “partitions” and stored on the disks
 IBM XIV Storage System distribution algorithm automatically
distributes partitions across all disks in the system
Interface Interface Interface
Switching
Data Module Data Module Data Module

IBM XIV Distribution Algorithm on System Changes
 Data distribution only changes when the system changes

– Equilibrium is kept when new hardware is added
– Equilibrium is kept when old hardware is removed
– Equilibrium is kept after a hardware failure
Data Module 1 Data Module 2
Node 1 Node 2
Data Module 3
Node 3

Storage Pools
 Logical Allocation
– No disk drives, RAID groups or any other physical resources are reserved per pool
– Storage Pool size can range from as small as 17GB Decimal (16GB Binary) to as large as the entire system
 Storage Pools can always dynamically be resized

– Only limited by free space in the system or consumed space
– Resizing can be done via CLI commands or the GUI
 Storage Pools are for capacity isolation reasons, not performance

Volume Creation
 LUNs are allocated in GB or Blocks

– Minimum volume size is 17GB Decimal (16GB Binary)
– Increments are on 17GB boundaries
– Smaller units will round up to the closest 17GB
 Volumes size can be dynamically resized

– Primary and Secondary in a synchronous mirroring relationship will be resized
– Resizing a FlashCopy Source does not automatically resize the Target
 User does not plan the layout of the volumes relative to physical drive
resources

Storage Pools and Volumes Relationship
 Each volume belongs to one pool
 Volumes can be moved between pools
 New volume must be smaller than pool free space
 Volume and its Snapshots belong to a pool

– Source and Target volume(s) move together
 Consistency group must be contained in a single pool

– All volumes of the Consistency group moved together
 Snapshot space is managed per pool

Mapping Volumes to Hosts
 Used to control server access to LUNs

– LUN Maps
• Open systems server AND
• LUNs to be accessed
• Logical volumes can be added to or removed from any map dynamically
– Cluster Maps
• Grouping of several hosts together that have the same mapping to all of the
hosts
• Mapping of volumes to LUN identifiers is defined per cluster
• Applies concurrently to all the hosts in the cluster
• No way to define different mappings for different hosts belonging to the
same cluster

Capabilities
Caching Architecture

IBM XIV Storage System Cache Implementation
 Read and Write cache are implemented as part of the Data Module function
 Each module caches data that is stored on its own disks

– Read from disk to cache
– Write from cache to disks
– Send data to hosts
– Accept data from hosts
 Upon read the system performs aggressive pre-fetching
 Dual write mechanism provides cache redundancy
 IBM XIV Storage System implements 4KB cache slot

Capabilities
Reliability and Serviceability

IBM XIV Reliability - Hardware Redundancy
 Power supply redundancy

– Redundant power supplies and fans are used for each data module
– Redundant power sources and 3 UPS units support the system
– Redundant power feeds
 Internal connectivity redundancy

– Two Ethernet switches
 Full replace ability of components

– Full online replacement of redundant components
 Load balancing across all 180 disk drives

IBM XIV Reliability – Data Redundancy
 Basic scheme is mirroring and striping
 Mirroring is not on physical disk-pairs
 Each disk is made of 1MB partitions
 Each partition on the disk is mirrored on a different disk and different

Data Module
– Always mirrored on a disk which is not in the same module
 Each disk is backed-up on all other disks

IBM XIV Reliability - Global Hot Spare Storage Capacity
 Traditional approach
– Dedicated Hot spare drives
 With the IBM XIV Storage System, each disk is utilizing 85% of its space
– The system provides enough hot spare capacity to tolerate a sequence of three disk failures
and one module failure, all while still providing redundancy
 Upon a failure, the system returns to redundancy

IBM XIV Storage System Reliability Capabilities
 Optimal load balancing to reduce disk drive failures
– Reduction of disk drive stress levels for normal operation and in rebuild scenario
– No idle drives
 Aggressive phasing out of disk drives prone to failure

– Detection of early signs of disk failure, and automatic initiation of proactive rebuild process
– Self-Monitoring, Analysis and Reporting Technology (SMART) mechanism
 Scrubbing
– Early detection of media errors through background testing of disk drive blocks
– One partition is examined every second
 UPS systems extend component life

– Three UPS systems and two power sources
– Double-conversion type (AC-to-DC-to AC)
• Ensure stable current with no spikes

IBM XIV Reliability – Disk Failure Scenario
 Each of the other disks contain 1% of any other disk in other modules
 All disks start to send data to each other until the system is fully redundant
again
– Concurrently, 168 disks are reading, 179 disks are writing
 Data modules are intelligent storage systems

– Only space allocated to volume is actually being copied on the rebuild process
– Only chunks that the user has written to are actually being copies on the rebuild process
 1TB disk rebuild takes only 30 minutes when fully utilized

IBM XIV Storage System - Event Handling
 User has full control on event notification configuration

– Can be filtered according to the events’ severity and code
 Event notification can be sent via:

– Email addresses
– SMS messages
– SNMP traps
• XIV supplied MIB
– Modem
– Pre-defined destination groups
• May be comprised of a mixture of SMS cell numbers, email addresses and/or SNMP addresses
 Users may view past events using various filters

IBM XIV Storage System - Call Home Flow (initial)
Analysis and
Failure occurs Filtering at
XIV Server
Scrubbed
Event event sent
Generated to RETAIN
Customer XIV SWAT

XIV notified
notified (email team engaged
(via email)
or SNMP)
Escalation to
development

IBM XIV Storage System - Call Home Flow (ultimate)
Analysis and
Failure occurs Filtering at
XIV Server
Scrubbed
Event event sent
Generated to RETAIN
Customer SSR
XIV notified
notified (email or dispatched
(via email)
SNMP)
Escalation to Notify account
level 3 or technical
development advisor (TA)

Software

IBM XIV Storage System Software Capability
 Software Functions
– Snapshot
– Data Migration

Capabilities
Thin Provisioning

Thin Provisioning Considerations
 Advantages
– Never resize a volume
– Pay for storage only when really needed
– Never pay because of over-estimation
– Reduce power and cooling costs
– Keep users happy
 Considerations
– Used capacity must be monitored carefully
– Additional capacity must be added in time

IBM XIV Implementation of Thin Provisioning
 Thin Provisioned Storage Pools 200GB

– Soft Size – limit of total volume size for the pool
– Hard Size – limit of the physical storage available to
volumes 50GB
– Snapshot / Clones not included in the Soft size
– Each Pool is independent
20GB 20GB 20GB 20GB
 Thin Provisioned Volumes

– Soft size – volume size seen by the host
– Hard size – actual data written
– Allocations come from the associated Storage Pool

Thin Provisioning Management
 Monitoring and alerting

– Monitors storage consumption
– Notifications can be configured when space utilization exceeds a user-defined threshold
– Storage Pools are independent and do not share hard capacity
 Snapshot deletion
– Snapshots are deleted in order to provide more physical space for volumes
– Snapshot copy deletion is based on the deletion priority and creation time
 Volume locking
• After all clones are deleted
• All volumes in the Storage Pool are locked (read only or no I/O)
• Other Storage Pools are unaffected

Capabilities
Snapshot

IBM XIV Storage System Snapshot Features
 Snapshot (Clone) support Source

– Differential
– Full Copy
– Multiple Clones
 Up to 16,000 Snapshots supported
 Consistency Groups Target
 High performance with Snapshots

Redirect-on-Write (ROW)
 Redirect-on-write processing
– Each Data Module handles copy process
• Ensures consistent performance A B C D Original data
– When a write request occurs
• Data originally associated with the source
remains in place
• New data is written to a different location on Snapshot image is set
A B C D
of pointers to source
disk
data.
• After the write request is completed and
acknowledged, original data is associated Redirect on Write Modify A, D
with the Target to ensure T0 integrity
• Newly written data is associated with the A B C D A’ D’
Source
– The original data is never copied
Modified data is
written to a new
A B C D location. Snapshot
pointers still point to
original data.

Consistency Group Storage Pool
Source Target
 An application might use several volumes which depend on

S1 T1
each other
Source Target
 Need to take a consistent point-in-time snapshot of all the
volumes in the group
S2 T2
 Consistency Group is managed per storage pool

– All volumes of a Consistency Group must belong to the same Storage Pool Source Target
– All volumes must be part of the same Consistency Group
S3 T3
 Using IBM XIV Storage System, one can:
– Take a concurrent Snapshot of all volumes in a group
– Treat the group of Snapshots created as one entity Source Target
S4 T4

Capabilities
Synchronous Remote Mirroring

Synchronous Remote Mirroring Support
 Synchronous remote Mirroring Host
I/O
1 Write (channel end)
– Link Types and Distance 2 Write to secondary
• 100 km’s 3 Write acknowledged

by secondary
• Ethernet/IP/iSCSI 4 Acknowledgement
1.
• Fibre Channel (FCP) (Device end -- I/O
complete
– Replication to multiple target systems is allowed 4.
– Replication can be performed in both directions 3.
• Remote site can use the local site as a secondary
• While the Local site uses the remote site as a 2.
secondary

Synchronous Remote Mirroring Support (cont)
 Volumes are paired as Primary and Secondary
– Primary and Secondary must be the same size volume
– Secondaries are read only
– Cannot be the target of a Volume Copy or Clone restore
– Volumes in the same consistency group must be on the same target subsystem
– All Secondary volumes on a target will be consistent
– Mandatory or Best Effort mode

Synchronous Remote Mirroring States

Synchronous Remote Mirroring Operations
 Synchronized Volumes
– Remote Mirror is operational
– Deactivate Mirror is atomic
– Switch Roles is possible

Synchronous Remote Mirroring Operations (cont)
 Unsynchronized Volumes
– Caused by conditions that prevent writing to the secondary
– Change Roles is possible for recovery
– Synchronization can be initiated in either direction
 Inconsistent Volumes
– Secondary state during synchronization process
– Last Consistent snapshot preserves previous state

Synchronous Remote Mirroring Information
 More information about Remote Mirror Operations

– IBM XIV Storage System Theory of Operation
– ATS XIV “Deep Dive” sessions

Capabilities
Data Migration

IBM XIV Storage System Data Migration
 Enables the transition to an IBM XIV Storage System

– Host connects to the IBM XIV Storage System
– Data is available before the copy is complete
– Synchronizes by volume as a background process
 Hosts connect to IBM XIV Storage System as storage

– Either FC or iSCSI
 IBM XIV Storage System connects to legacy storage as a host

– Either FC or iSCSI
 Protocol connectivity does not have to be the same

 Thick to Thin provisioning

IBM XIV Storage System Data Migration (cont)
 Host I/O handling in Data Migration Host
I/O
1 Write request
– No action required by the host 2 Write to secondary

(if Source Updating)
– Data will be retrieved from the non-IBM XIV system when 3 Background Copy
needed
4 Read Request
1.
 Non-XIV System I/O Handling in Data Migration (copy if needed)
– The IBM XIV Storage System reads data sequentially by 4.

volume
3.
– Source updating IBM Other
System
• Optional source volume updating XIV
2.
• This will keep the 2 Storage systems in sync
– No Source updating
• Writes are handled only within the IBM XIV Storage
System
• The original data volumes are not changed

Capabilities
Manageability

Agenda - Manageability
 Documentation
 XCLI
– Introduction
– Installation
– Setup
– Commands
 Role Based Access Controls
– Introduction
– Roles and Permissions
– User Configurations
– User Groups
– Auditing
 GUI

IBM XIV Storage Documentation
 Available after product announce – www.ibm.com/systems/support/storage/XIV
 IBM XIV Storage System Theory of Operation
• Role-based access control
• Volumes and clones
• Host mapping to volumes
• Consistency groups
• Storage pools
• Thin provisioning
• Remote mirroring
• IP and Ethernet connectivity
• Event handling
• Data migration
 IBM XIV Storage Site Installation Requirements
• Power requirements
• Cooling requirements
• Physical space requirements
• Raised floor requirements
• Weight
• Delivery
• Physical network requirements
 XCLI User Manual
 IBM XIV Storage Host Systems Attachment Guide
 IBM XIV Storage Systems Assurance Product Review (SAPR) Guide
http://w3-03.ibm.com/support/assure/assur30i.nsf/WebIndex/SA830

XCLI Introduction
 XIV Command Line Interface (XCLI)
 XCLI commands fully support the IBM XIV Storage – superset of GUI
 Runs remotely on standalone systems
– Windows, Linux, Solaris, AIX, HP-UX, and Macs
– Install the XCLI + GUI, or just XCLI
 Communicates with XIV Storage over TCP/IP

 Uses
– Scripting lengthy, repeatable, or complex tasks
– Execute XCLI commands – single shot
– XCLI local functions
• Create configuration files
 There will be a manual – XCLI User Manual

XCLI Setup – Create a Desktop Icon to Start XCLI
 End game
xcli -u hank -p hankspw -m 149.168.100.101 user_list
- to -
xcli -c R2Waltham user_list
 Place a DOS prompt on your desktop  xcli icon
– Start/Programs/Accessories
– Right click on Command Prompt and select ‘Create Shortcut’
– Drag the shortcut icon to your desktop
– Rename it ‘xcli_admin’
 Customize xcli_admin icon
– Right click on icon and select properties
– Shortcut tab
• Target: %SystemRoot%\system32\cmd.exe /k cd C:\Documents and Settings\Administrator\My Documents\xcli && setup
• Start in: c:\Program Files\XIV\Nextra10
– Options tab
• Check QuickEdit mode
– Layout tab
• Screen buffer size
– Width: 160
• Window size
– Width: 120
– Height: 40
– Apply & OK
 Create setup.bat file in C:\Documents and Settings\Administrator\My Documents\xcli
@echo off
set XIV_CONFIG_FILE=C:\Documents and Settings\Administrator\My Documents\xcli\xcliconfigs.xml
set XIV_XCLIUSER=your_user_id
set XIV_XCLIPASSWORD=your_password
xcli -L

XCLI Setup (cont.)
default pw
 Launch the XCLI_admin icon

– Try a command
xcli -u admin -p adminadmin -m <IP Addr> user_list
Name Category Group Email Address Area Code Phone Number Access All
xiv_development xiv_development
xiv_maintenance xiv_maintenance
admin storageadmin
technician technician
 Generate a XCLI config file You choose a unique name to describe system
– Create an empty file

C:\Documents and Settings\Administrator\My Documents\xcli\xivconfigs.xml
– Create XCLI config file
xcli -f "C:\Documents and Settings\Administrator\My Documents\xcli\xivconfigs.xml" -a R2Waltham -m <IP1> [–m <IP2> [–m <IP3>]]
System Managements IPs

R2Waltham <IP1>

XCLI Setup (cont.)
 Relaunch the xcli_admin icon

xcli -c R2Waltham user_list
Name Category Group Email Address Area Code Phone Number Access
xiv_development xiv_development
xiv_maintenance xiv_maintenance
admin storageadmin
technician technician

XCLI Commands - Help
General XCLI local shell command options
xcli -h
xcli [ --file=FILE ] <-L> Lists the current configurations (name, IP addresses, active manager)
xcli [ --file=FILE ] <-a> CONFIG -m IP1 [-m IP2 [ -m IP3]] Adds a new configuration names CONFIG, with IP1,IP2 and IP3 as IP addresses of the interface modules
xcli [ --file=FILE ] <-d> CONFIG Deletes the configuration CONFIG
xcli <-h> Prints a summary of the command's options.
xcli <-v> Prints the command's version
xcli < <[ <-f ==> FILE ] -c CONFIG >| -m IP1 [-m IP2 [-m IP3]] >
[ <-l> | <-s> | <-x> ]
[ <-u ==> USER ]
[ <-p ==> PASSWORD ] Change/Delete commands ask if you are really sure
[ -y ]
[ <-t ==> field1,field2,... ] [ command [p1=v1 [p2=v2 ]...] | <-r ==> SCRIPT ]
Executes a CLI command/s on a Nextra system.
The Nextra system can be specified by either the IP addresses of its interface modules (IP1, IP2 and IP3), or by a pre-defined configuration name CONFIG.
USER is the user name. If empty, the xcli tries to get it from the environment variable NEXTRA_XCLIUSER.
PASSWORD is the command password. If empty, the xcli tries to get it from the environment variable NEXTRA_XCLIPASSWORD.
The executed command will be trailed with parameters and their values.
SCRIPT can be defined to specify the name and path to the commands file (lists commands will be executed in User Mode only).
-l Ask for result in user readable format (default)

-s Ask for result in comma separated format
-x Ask for result in XML format
-u USER Provide a user for the command
-p PASSWORD Provide a password for the command
-y Bypass warning message
-t FIELDS =<FIELDS> Provide list of columns to define the output result
The command "help command=help format=full" will show the help message of the Nextra system.
The configurations are stored in a file under the user's home directory.
A different file can be specified by -f or --file switch (applicable to configuration
creation, configration deletion, listing configurations and command execution). Alternatively,
the environment variable NEXTRA_CONFIG_FILE, if defined, determines the file's name and path.

XCLI Commands
 Help
– List all XCLI commands
xcli –c R2Waltham help
– List all XCLI commands in CSV format
xcli –c R2Waltham –s help format=full > xcli_cmds.csv
– List help on a specific command
xcli –c R2Waltham help command=vol_create
xcli -c R2Waltham help command=vol_create format=full

XCLI Scripting – Sample script
@echo off
:: Environment variables -------------------------
set myconfig=prime
set myhost=adams
set myports=10000000C941xxxx 10000000C941xxxx
set mypool=%myhost%_pool
set num_vols=16
set vol_size=17
::----------------------------------------------
set NEXTRA_XCLIUSER=tester
set NEXTRA_XCLIPASSWORD=tester’s_password
:: define the host

xcli -c %myconfig% host_define host=%myhost%
:: add the ports

FOR /D %%p in (%myports%) DO xcli -c %myconfig% host_add_port host=%myhost% fcaddress=%%p
:: create a pool
xcli -c %myconfig% pool_create pool=%mypool% size=2400 snapshot_size=600
:: create the volumes

FOR /L %%a in (1, 1, %num_vols%) DO xcli -c %myconfig% vol_create vol=%myhost%_vol%%a size=%vol_size% pool=%mypool%
:: map the volumes to the host

FOR /L %%a in (1, 1, %num_vols%) DO xcli -c %myconfig% map_vol host=%myhost% vol=%myhost%_vol%%a lun=%%a

Role-Based Access Control
Advanced and powerful access control system that specifies

defined user roles to control access. The system provides
built-in roles for access flexibility and a high level of security
defined according to predefined roles and associated tasks.
You can define users with different privilege levels.
• Customer defined user privileges • Predefined users

• Storage administrator • admin
• Application administrator ---------------------
• Read only • technician
• xiv_development
• xiv_maintenance
• R2 Documentation
• XCLI User Manual
• Theory of Operation Manual

User Roles and Permission Levels
User Role Permissions and limits Typical usage
Read Only Can only list and view system information. System operator responsible for monitoring system status and
reporting & logging messages.
Application  Create snapshots of specifically assigned Typically manage applications that run on a particular application
Administrator volumes or server. Default privileges limited to specific volumes on a server.
Typical functions:
 Map their own snapshots to specifically
assigned hosts.  Manage backup environments
 Delete their own snapshots. – Create snapshot for backups
– Map snapshot to backup server
– Delete snapshot after backup is complete
– Update snapshot for new content within a volume
 Manage software testing environment

– Create a new application instance
– Test the new application instance
Storage Has permission to perform all functions Storage managers are responsible for all administration functions.
Administrator on GUI and XCLI except:
 Only the predefined administrator,
One predefined Storage Administrator user called: admin
“admin”, can change the passwords of
other users Initial password: adminadmin

User Configuration Rules
 Create a user
– Role
• Storage Administrator
• Application Administrator
• Read Only
– Name
• Lower case
– Password
• Case sensitive
• Not shown in user lists
• Users can change their own passwords
• Change via CLI or GUI
• 6-12 characters (a-z, A-Z, 0-9)
– Email
– SMS
– access_all – application admin. user has privileges to all volumes
 32 users maximum

Application Administrator and User Groups
App
Admin
App 1
 Application Administrator Admin 2
– Create and manage snapshots Host

• Commands User
Host
– snap_group* Group 1
– snapshot*
ClusterHost
– map_vol unmap_vol Host
– vol_lock User
Host
– Typically associated with a user group Group 2
– For all volumes (access_all=yes)
Host Snap
App
 User Group Admin 3
– Application administrator(s) associated with certain host(s) or cluster(s)

– User members must be application administrators
– An application administrator can only belong to one user group
– A user group can contain up to 8 application administrator users
– Hosts and clusters can be associated with only one user group

Transaction Auditing
 Events
– Allows auditing all commands that are performed by users
• Each command generates an event in the event log
• Includes who executed the command and when
– Event Notification
• email
• SMS
 Every object that is created (volume, host, snapshot, consistency group, etc.) has
attributes which includes the user who created the object – XCLI only
xcli -c R2Waltham vol_list vol=tempvol

Name Size (GB) Master Name Consistency Group Pool Creator Used Capacity (GB)
tempvol 17 hank 0

IBM XIV Storage GUI
 A really really great GUI !!!

 Technical session in October
 Runs remotely on standalone systems
– Windows, Linux, Mac and Solaris
– Install the XCLI + GUI
 Communicates with XIV Storage over TCP/IP
 Very low bandwidth requirements
– Wireless laptop customer demo – no problem

IBM XIV Storage GUI (2)
 Probably

IBM XIV Storage GUI (3)
 Primary Icons
 System
 Monitor
 Pools
 Volumes
 Hosts and LUNs
 Remote Mirroring
 Access

Installation Planning

Agenda – Installation Planning
 Planning
– Physical Site
– System configuration
 Delivery
 Install Day Activities

Solution Assurance – Technical Delivery & Assessment
Presale and pre-install Solution Assurance TDAs (previously know as SARs) are mandatory
for all first in customer location orders
– Presale TDA… is a review of a completed solution design prior to presentation to the customer. Technical
SMEs (ATS, CSE, others qualified) who are not involved in the solution design participate to provide
guidance and determine:
• Is the proposal complete and will it work?
• Will it meet customer requirements & expectations?
– Account teams developing the proposal can refer to the Solution Assurance Product Review (SAPR) guide
as a resource to help them prepare a sound proposal.
– Pre-install TDA… takes place after the order is placed and prior to installation. Technical SMEs assist in
evaluating the planning and preparation completed by the account team and customer to insure
readiness to install, implement, and support the solution.
• Account teams utilize the SAPR guide as a planning checklist with the customer in preparation for
a successful installation
• SAPR guide checklist is used during TDA reviews – open issues are identified and actions are logged
and tracked to closure.
The IBM XIV Storage System SAPR Guide will be posted at:
– IBM: http://w3-03.ibm.com/support/assure/assur30i.nsf/WebIndex/SA830
– Partnerworld: http://partners.boulder.ibm.com/src/assur30i.nsf/WebIndex/SA830
 For more information and WW Contacts see the Solution Assurance Website:
– IBM: http://w3-03.ibm.com/support/assure/assur30i.nsf/Web/SA
– Partnerworld: http://partners.boulder.ibm.com/src/assur30i.nsf/Web/SA

Planning – Physical Site
 There will be an IBM XIV Storage Site Installation Planning Guide
 There will be a SAPR Guide 9xxx Infrastructure and Specify Features
 Power Remote support module 1 /1
9000 Maintenance module One Plant $$ $$ 1 /1

– (2x) one-phase/pole 220volt 60amp
– 7.7kW, 8.4kW peak Modem 1 /1
– US/AP connector: Hubbel HBL360P6V0 9101 Modem One Plant $$ $$ 1 /1
or equivalent
 Cooling Power indicator 1 /1
9800 Single phase power One Plant -- -- 1 /1

– 26K BTU/hr
 Raised floor Single-phase line cords 1 / 99
– Two ventilation tiles in front of Rack 9801 US/Canada/LA/AP line cord Two Both $$ -- 0 / 99
– Weight 9802 US Chicago line cord Two Both $$ -- 0 / 99
• 869 kg (1912 lbs) 9803 EMEA line cord Two Both $$ -- 0 / 99
– Cable Cutout template 9804 Israel line cord Two Both $$ -- 0 / 99
 Shipping
– Ship as one unit
– Dimensions
• 105 x 124 x 212 centimeters (41 x 49 x 84 inches)

Planning – Physical Site – Raised Floor
 Physical space
• Rack: 199.1 CM high, 109.1 cm deep, 60 cm wide; 42U
• Cooling Tiles
• Cable Cutouts
• Service Clearances

Planning – Physical Site (Cont.)
Cabling
– 3 meters slack in all cables for internal rack routing
– Cable Specs
• Ethernet
– IBM feature code 3900, 30 meters
– Management
> CAT6 or CAT5e copper Ethernet RJ-45 connectors
– iSCSI
> CAT6 copper Ethernet with RJ-45 connectors
• Fibre channel
– 50 Micron LC multi-mode 4Gb
– IBM feature code 3910 (LC-LC), 30 meters
– IBM feature code 3920 (LC-SC), 30 meters
– Infrastructure
• Management (3x)
• Remote access
– Modem – phone line
– 1 or 2 Copper gigabit Ethernet CAT6 or CAT5e with RJ-45 connectors
– Host Connections
• Fibre Channel (12x standard, up to 24x)
• iSCSI (6x)

Planning – System Configuration
Customer Network Customer IP Address Netmask Default Gateway
Interface Module 4
Interface Module 5
Interface Module 6
Primary DNS Server

Secondary DNS Server
SMTP Gateway(s)
NTP (Time Server)
SNMP Server
Time Zone
Email sender address
Remote Access / VPN IP Address Netmask Default Gateway

Remote Support Server Customer Interface
External IP address (Address exposed to Internet
(NAT?) ):
VPN software required at XIV's site
Modem Phone Number

Installation Activities – Delivery
 Delivery – US only
– Instruct customers to inspect crate
• No external damage
• Tilt and shock indicators
– Trucking company (McCollisters – US only) will uncrate
– Trucking company will wheel system to location of installation
• Clear and level path from truck to building entrance
• No steps
• Clearance for upright rack from truck to building, doors and elevators
• Instruct customers to sign for delivery AFTER all the above is completed
Blue text indicates data needs verification

Installation Activity – Install Day
Installs by SWAT thru 2008, SSRs (GTS) starting 2009
Procedure
– Level system
– Verify secure cables
– Power up
– System configuration
• 3 IP addresses
• System name
• Email
• DNS
• Time zone
• Date/Time
• NTP
• Validate remote connectivity
– Logical configuration
• LUNS, hosts, etc.
– Host attachment
– Review power-off procedures (never push the buttons !!)

Summary

IBM GTS and Storage Services
 IBM Storage Optimization, Integration, and Data Mobility Services from IBM Global
Technology Services:
– IBM Storage Optimization and Integration Services
• http://www.ibm.com/services/storageopt
– IBM Data Mobility Services
• http://www.ibm.com/services/datamobility
– For additional information or to request these services, visit
• http://www-935.ibm.com/services/us/index.wss/itservice/its/a1000416
 IBM Storage Implementation, Data Replication, and Upgrade/Migration Services from IBM
STG Lab Services
– IBM XIV Storage System Smoothstart Planning and Implementation Services
– IBM XIV Storage System Snapshot Replication Configuration Services
– IBM XIV Storage System Upgrade and Migration Services
– For additional information or to request these or other custom services:
• Send an e-mail to storsvcs@us.ibm.com
• Visit the following Web site and click on '"Contact now'" to submit your inquiry or request
– http://www.ibm.com/systems/services/labservices/labservices_storage.html

Summary
 IBM XIV Storage System Overview and Architecture

– Hardware and Software features
– Ordering Information
– Virtualization Capabilities
– Reliability and Serviceability
 IBM XIV Software V10 Functionality
– Snapshot
– Data Migration
 Manageability
 Installation Planning
 ATS XIV Deep Dive teleconference series (Sept – Nov)
– Thin provisioning
– Logical configuration concepts
– GUI
– Snapshot
– Remote Replication solutions

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.
For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml:
*, AS/400®, e business(logo)®, DBE, ESCO, eServer, FICON, IBM®, IBM (logo)®, iSeries®, MVS, OS/390®, pSeries®, RS/6000®, S/30, VM/ESA®, VSE/ESA,
WebSphere®, xSeries®, z/OS®, zSeries®, z/VM®, System i, System i5, System p, System p5, System x, System z, System z9®, BladeCenter®
The following are trademarks or registered trademarks of other companies.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
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.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce.
* All other products may be trademarks or registered trademarks of their respective companies.
Notes:
Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will
experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed.
Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here.
IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual
environmental costs and performance characteristics will vary depending on individual customer configurations and conditions.
This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without
notice. Consult your local IBM business contact for information on the product or services available in your area.
All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the 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.
Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.


Ibm Xiv Storage System Technical Overview: Americas Advanced Technical Support

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ibm Xiv Storage System Technical Overview: Americas Advanced Technical Support

Uploaded by

Copyright:

Available Formats

IBM XIV™ Storage System

© 2008 IBM Corporation

 IBM XIV Storage System Overview and Architecture

 IBM XIV Software V10 Functionality

 ATS XIV Technical Deep Dive Session Plans

2 © 2008 IBM Corporation

3 © 2008 IBM Corporation

 Virtualized grid storage:

 Automatic load balancing

IBM XIV Storage

User Switch (FC/Ethernet)

5 © 2008 IBM Corporation

Machine Type: 2810-A14

 Single rack provides 80TB usable capacity

IBM XIV Storage

 42U Rack Module 15 (Data)

– 6 Data + Interface Modules Module 9 (Data + Interface)

 1 1U Maintenance Module Module 5 (Data + Interface)

 2 Redundant power supplies Module 3 (Data)

 2 48 port 1GbE switches Module 1 (Data)

7 © 2008 IBM Corporation

8 © 2008 IBM Corporation

 1xxx Modules  Host Attachment Cables (30meter)

– 9000 Maintenance Module - Quantity 1

9 © 2008 IBM Corporation

 Software Maintenance 1 Year

 Software Maintenance 3 Years

10 © 2008 IBM Corporation

11 © 2008 IBM Corporation

12 © 2008 IBM Corporation

 Provides FC / iSCSI host, any-to-any Module Module 15 (Data)

 Each module works independently UPS 2

13 © 2008 IBM Corporation

 Provides front-end for management by the user

Interface Interface Interface

Internal Switch 1 Internal Switch 2

Data module Data module Data module

14 © 2008 IBM Corporation

 In case of continuous external power Module 9 (Data + Interface)

failure Module 8 (Data + Interface)

15 © 2008 IBM Corporation

16 © 2008 IBM Corporation

Interface Interface Interface

Data Module Data Module Data Module

17 © 2008 IBM Corporation

 Data distribution only changes when the system changes

Data Module 1 Data Module 2

18 © 2008 IBM Corporation

 Storage Pools can always dynamically be resized

 Storage Pools are for capacity isolation reasons, not performance

19 © 2008 IBM Corporation

 LUNs are allocated in GB or Blocks

 Volumes size can be dynamically resized

20 © 2008 IBM Corporation

 Each volume belongs to one pool

 Volumes can be moved between pools

 New volume must be smaller than pool free space

 Volume and its Snapshots belong to a pool

 Consistency group must be contained in a single pool

 Snapshot space is managed per pool

21 © 2008 IBM Corporation

 Used to control server access to LUNs

22 © 2008 IBM Corporation