Advanced Technical Sales Support (ATS) North America

Accelerate with ATS:

SVC/Storwize Family
IP Replication

Bill Wiegand – ATS

Consulting I/T Specialist
Storage Virtualization

3/25/2014 © 2014 IBM Corporation

Platform for Remote Copy Services

Single point for copy services Use to meet business needs

 Asynchronous remote copy/Global Mirror  Disaster recovery up to 8000KM
 Synchronous remote copy/Metro Mirror  Business Continuance less then 300KM

Storage Storage
Network Network

Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs

Node Node Node Node Node Node Node Node Node Node Node Node Node Node Node Node

Managed Disks Managed Disks

2
Replication Options
 A remote copy relationship consists of two volumes
– A Primary and a Secondary volume
• Also referred to as master and auxiliary volumes
 Synchronous MM provides zero data loss
 There are two options for configuring asynchronous GM
– Traditional GM with non-configurable RPO of a couple seconds
– GM with change volumes with configurable RPO
 Storage administrator can change between any 3 modes easily

3
Metro Mirror

Production host

Host I/O

Primary
Metro Mirror relationship Secondary
volume volume

 Host write received at both local and remote system before returning write complete to host
 80ms roundtrip latency maximum
 Bandwidth sized for peak write data rate of all primary volumes
 Zero RPO

4
Traditional Global Mirror

Production host

Host I/O

Primary
Global Mirror relationship Secondary
volume volume

 Dependent writes to primary sent with sequence number to secondary site to ensure they
are applied in the same order ensuring consistency at DR site at all times
 80ms roundtrip latency maximum
 Bandwidth sized for peak change rates
 RPO seconds and non-configurable

5
Global Mirror with Change Volumes

Production host

Host I/O

Primary
Global Mirror relationship Secondary
volume volume

Change Change
volume volume
FlashCopy FlashCopy
Mapping mapping
 Copy all data from primary volume to secondary volume at point-in-time of when GM relationship
initially started
 Change volumes hold point-in-time copy of data that changes during cycling mode
– Uses FlashCopy function under the covers
 80ms roundtrip latency maximum
 Bandwidth sized based on RPO desired
 RPO can be configured from minutes to hours
 Will fluctuate depending on bandwidth available and data change rate
6
SVC/Storwize Remote Copy pre-V7.2 Primary
Volume

 Remote Copy:
– Fibre Channel infrastructure required

 Remote Copy via Ethernet:

– Expensive FCIP router required
– Complex system management
Fibre Channel over
 Discovery of remote cluster Fibre Channel Eternet -FCIP
or
– Performed by Fibre Channel name server
– Remote Cluster automatically visible
• Appropriate zoning required
• Dedicated ports recommended

Secondary
Volume
7
Native IP Remote Copy Primary
Volume
 Enables use of 1Gbit or 10Gbit Ethernet connections
using TCPIP without the need for fibre channel or FCIP
routers for replication
– Supports all remote copy modes – MM and GM
• GM with Change Volumes preferred mode
– Covered by normal remote copy license
• It is not a new replication offering, but rather a new transport
versus using a fibre channel network
 Configuration:
– Automatic path/session configuration via discovery of
remote cluster using IP management addresses of both Ethernet
systems in the IP remote copy partnership
– Configure IP partnership using either 1Gbit or 10Gbit
Ethernet ports but not both at same time
– Currently cannot switch speeds anywhere in end-to-end
link other then WAN
• E.g. cannot connect 10Gbit port to 10Gbit switch and then
connect 1Gbit out that 10Gbit switch to WAN
• E.g All 10Gbit->WAN<-10Gbit or 1Gbit->WAN<-1Gbit
– CHAP-based authentication supported
 Includes Bridgeworks SANSlide IP network Secondary
optimization technology built into V7.2 Volume
8
IP replication – SANSlide optimization (1/5)

Recap: Fibre Channel over Long distance:

 Buffer to Buffer credits

– B2B credits are used as a flow control method by Fibre Channel technology and represent the
number of frames a port can store
→ Provides best performance

 B2B Calculation depends on link speed and distance

– Number of multiple frames parallel in flight increase equivalent to the link speed

BUT:
- B2B credits are not available in IP, IP must wait for package acknowledge before sending the next
package

-> SANSlide optimizes the connection using multiple, parallel virtual connections that share the same IP
links and addresses

9
Bridgeworks SANSlide optimization (2/5)

(Figure from REDP5023)

 With TCP/IP, information transfer slows the further you go
 IO transfer:
– Source: Send package, wait for acknowldge
– Target: Wait for package, acknowledge the received package to the Source
– Source: Wait for acknowledge, Send the next package after receiving previous acknowledgement
 System is waiting most of the time

10
Bridgeworks SANSlide optimization (3/5)

Latency in standard IP network (1Gb link speed):

• depends on the routing infrastructure
• depends on distance

Latency = Round Trip Time (RTT) for a single packet set

Source: IBM Redpaper REDP5023

11
Bridgeworks SANSlide Optimization (4/5)

(Figure from REDP5023)

 Enhanced parallelism by using multiple virtual connections (VC) that share the same IP links
and addresses:
– When waiting for one VC’s ACK, it sends more packets across other VCs
– If packets are lost from any VC, data will be retransmitted
– Artificial Intelligence engine adjusts number of VCs, receive window size, and packet
size as appropriate to maintain optimum utilization/performance of the links

12
Bridgeworks SANSlide Optimization (5/5)

Latency in IP network (1Gb link speed):

depends on the routing infrastructure
depends on distance

Latency = Round Trip Time (RTT) for a single packet set

Source: IBM Redpaper REDP5023

13
Native IP Remote Copy – IP Partnership Requirements

 If you use IP replication, you must meet the following requirements:

– TCP ports 3260 and 3265 are used by systems for IP partnership communications
• These ports must be open on any firewalls
• Port 3260 is the port used by the systems to initially discover each other
• Port 3265 is for the actual IP Replication sessions used to transmit data
– The maximum supported round-trip latency between sites is 80 ms for a 1 Gbps link
– The maximum supported round-trip latency between sites is 10ms for a 10 Gbps link
– The recommended method of replication is Global Mirror with Change Volumes
– The inter-cluster heartbeat traffic consumes 1 Mbps per link
– The minimum bandwidth requirement for an inter-cluster link is 10 Mbps
 Maximum throughput is currently restricted based on use of 1gigE or 10gigE ports
– One 1gigE port could do up to 110 MBytes/s ( 190 MBytes/s bidirectional )
– Two 1gigE ports could do 220 MBytes/s ( 325 MBytes/s bidirectional )
– One 10gigE ports could do up to 190 MBytes/s ( Bidirectional not tested )
– Two 10gigE ports could do up to 300 MBytes/s ( 325 MBytes/s bidirectional)

14
 Demo

15
Native IP Remote Copy – Bandwidth Setting

 Bandwidth setting definition has changed:

– Previously this bandwidth setting default was 50 MBytes and meant that was the
maximum transfer rate from primary to secondary site for initial sync/resyncs of volumes
– “Link bandwidth” setting is now configured using Mbits not MBytes and you set this to what
the communication link actually can sustain or what is actually allocated for replication
– “Background copy rate” setting is now a percentage of the “link bandwidth” and
determines the bandwidth available for for initial sync and resyncs or for GM w/chgvols
16
Single physical link with active/standby ports
Cluster A – Site 1

1
A1 B1

1 1
A2 B2

Cluster B – Site 2

 Remote copy port group = Set of local and remote Ethernet ports and associated TCP/IP
addresses available to establish a session over the IP link(s)
– Path will be established between IP addresses (local + remote) when IP partnership first configured
– Minimum: 1 local + 1 remote port in the same remote copy port group
– Recommended to cover node failures: For single I/O Group
• 2 local + 2 remote ports in the same remote copy port group

17
One link – One I/O Group

1 1
Primary H1 M1 Secondary
Volume Volume

Remote Copy Port Group 1

1 1
H2 M2

Site 1 Site 2

 Either Ethernet port 1 or 2 on a node/node canister can be configured for IP replication but
not both
 The remote copy port group on each system includes two IP address, one from each node,
and when initially configured the system will establish which one from each site is used
– This pairing can not be chosen or changed by an administrator
– In this example H1 and M2 have established a session
 If H1 node fails then the session between H1 and M2 fails and the system automatically
establishes another session between H2 and either M1 or M2
– The IP address used for replication on H1 does not failover to H2

18
One link – Two I/O Groups

1 1
H1 M1 Secondary
Volume

Remote Copy Port Group 1

1 1
H2 M2

I/O is
forwarded
from H4 to
H1 1 1
H3 M3

1 1
Primary H4 M4
Volume
Site 1 Site 2

 The remote copy port group on each system includes four IP address, one from each node,
and when initially configured the system will establish which one from each site is used
 If H1 node fails then the session between H1 and M2 fails and the system automatically
establishes another session between H2, H3 or H4 and M1, M2, M3 or M4
19
One link – More than two I/O Groups
1 1
H1 M1

Remote Copy Port Group 1

1 1
H2 M2

I/O is
forwarded 1 1
from H6 to H3 M3
H1

1 1
H4 M4

I/O is
forwarded
NOTE: Nodes H5/6 and M5/6 do from M4 to
M6
H5 not have IP addresses configured M5
as the limit currently is that only
the Ethernet ports of 2 I/O Groups
can be configured with IP
Primary H6 M6 Secondary
Volume addresses and included in remote Volume
copy port groups
20
Site 1 Site 2
Dual physical links with all ports active and no standby ports

1 2
A1 B1
Link 1

1
A2 B2
2 Link 2

Cluster A – Site 1 Cluster B – Site 2

 Remote copy port group setup for dual redundant links:

– Port group 1: two IP addresses, each on a different node in different system (green)
– Port group 2: two IP addresses, each on a different node in different system (orange)
 Maximum of 2 simultaneous IP replication sessions at any time
– Only one active per node, so in this configuration if node A1 would fail then Link 1 would
no longer be available and only link 2 would be active
• Result is loss of half of the bandwidth available for replication
• If bandwidth sizing dictates dual links required and if one link fails resulting in MM or
regular GM not able to operate properly, recommendation is to have 2 I/O Groups at
each site to allow the failed link to restart on other nodes available in systems
21
Two Links – One I/O Group and one port per node

1 2
Primary H1 M1 Secondary
Volume Remote Copy Port Group 1 Volume

2 1
H2 M2
Remote Copy Port Group 2

Site 1 Site 2

 Again maximum of 2 simultaneous IP replication sessions at any time

– Only one active per node so in this example if node M2 would fail then Link 1 would no
longer be available and only link 2 would be active
• Result is loss of half of the bandwidth available for replication

22
Two Links – Two I/O Groups and one port per node

1 2
Primary H1 M1
Volume Remote Copy Port Group 1

I/O is
1
H2 2 forwarded
Remote Copy Port Group 2 M2 from M1 or
M2 to M3

1 2
H3 M3 Secondary
Volume

2 1
H4 M4
Site 1
Site 2

 Each remote copy port group on each system includes two IP address, one from I/O Group
in this example, and when initially configured the system will establish the pairings used
 If H1 node fails then the session between H1 and M2 fails and the system automatically
establishes another session between H3 and either M2 or M4 since they are all in the same
remote copy port group with H1
23
Native IP Remote Copy – Configuration Steps using CLI

Main differences between IP and FC/FCoE remote copy partnerships:

– FC/FCoE remote clusters are discovered automatically via Fabric Name Service
lspartnershipcandidate can be used before creating partnerships
– IP remote clusters are discovered by IP addresses in mkippartnership command
– FC/FCoE partnerships establish all-to-all active paths (limited only by zoning)
– IP partnerships establish active/standby paths in 1 or 2 remote copy port groups
1. Set optional CHAP secret in both clusters
chsystem [–rcauthmethod none|chap] [-chapsecret string] ...
2. Configure remote copy port groups in both clusters
cfgportip –node node [–remotecopy portgroupid]
[-remotecopy_6 portgroupid]
[–host y|n] [–host_6 y|n] ... port_id
3. Create partnership
mkippartnership –type ipv4|ipv6 –clusterip ipaddr
[-chapsecret string] –linkbandwidthmbits mbitps
[-backgroundcopyrate percentage]

24
Native IP Remote Copy – Miscellaneous Information
 Cannot today non-disruptively switch from a FC partnership to an IP partnership
– Must delete relationships and delete partnership and start over basically
– If currently replicating over FC and can take outage on hosts replicating volumes, we
have a method using –sync flag on “mkrcrelationship”
 SANSlide – What it does and doesn’t do:
– It optimizes link utilization, but not latency
– It uses standard TCP/IP – no UDP
– It doesn’t do any encryption, compression or de-duplication
• Submit SCORE if looking for Riverbed etc. support
 Only two systems can be in one IP Replication partnership
– Can do A->B partnership
– Cannot do A->B->C->D or A/B/C->D
 A system can be in an IP partnership with one other system and in FC partnership
with others
– So we could do A->B using IP replication and B->C->D using FC replication
– Still a maximum of 4 systems in partnership with each other
 FC replication and IP replication can be used with any combination of SVC and
Storwize systems all running V7.2

25
Native IP Remote Copy – Best Practices

 Configure two physical links between sites for redundancy and to provide greater
bandwidth, if needed, between the two systems
– A minimum of 4 nodes at each site is required for dual redundant IP links to work across
a node failure at either site today
– With a 2 node system at each site, in the event of a node failure, one link will be lost
 Dedicate Ethernet ports for replication if possible
– Recommendation is to not use a port for both replication and iSCSI host access
– Ok to use 1gigE port for both replication and system management
 Multi-protocol partnerships are not supported
– Do not configure an additional FC/FCoE partnership between two systems if an IP
partnership already exists between them
 Configure CHAP secret based authentication for added security

26
Native IP Remote Copy – Best Practices

 If you choose to use compression and IP partnership in the same system, there
are some hardware upgrades or configuration choices that may help increase IP
partnership performance:
– If you choose to create an IP partnership on a SVC or Storwize V7000 system that has
compressed volumes, and you have multiple I/O groups, then configure ports for the IP
partnership in I/O groups that do not contain compressed volumes
– If you require more than a 100 MBps throughput per inter-site link with IP replication on a
node using compression, consider virtualizing the system with 2145-CG8 nodes that
include an iRPQ 8S1296 hardware upgrade (Chubbie node)
 Note that when replicating compressed volumes the data is not in a compressed
format when sent over the link to the DR system

27
Native IP Remote Copy

 IP Partnership Requirements – from InfoCenter for V7.2

– You can only create IP partnerships between two systems
– A system can only be part of one IP partnership
– You can create IP partnerships between any two Storwize products on the same layer
• In other words, both systems must be at the storage layer or both systems must be at the
replication layer
– You cannot use link-local addressing
– NAT not supported
– If you use IPv4 addressing, the management IP addresses on both systems must be
IPv4-compliant and these addresses must have connectivity with each other
– If you use IPv6 addressing, the management IP addresses on both systems must be
IPv6-compliant and these addresses must have connectivity with each other
– If your system has IPv4 and IPv6 addressing on the ports, you must configure all
Remote Copy links between the local and remote site using only one of those
addressing schemes
– You can configure ports from at most two I/O groups from each system for an IP
partnership

28
Native IP Remote Copy

 IP Partnership Requirements - continued

– If your system has 10 Gbps and 1 Gbps Ethernet ports, you must configure all Remote
Copy links between the local and remote site using only one of those speeds
• E.g. End-to-end must be all 1 Gbps or 10Gbps, no intermixing of speeds
– A cluster can have simultaneous partnerships over FC and IP but with separate systems
– The IP partner systems must not be visible to each other over Fiber Channel or Fiber
Channel over Ethernet (FCoE) connections
• Fibre Channel/FCoE ports of either clusters should not be listed as parameters to the svcinfo
lsfabric command
– Clusters configured in active IP partnerships, should not be zoned with each other for
Fibre Channel /FCoE
– iSCSI Hosts can access volumes over IP ports participating in an IP partnership,
although this may result in an impact on performance and not recommended
– VLAN tagging of the IP addresses configured for Remote Copy is not supported
– If you have one inter-site link, configure one Remote Copy port group
– If you have two inter-site links, you must configure separate Remote Copy port groups
• One for each link to be able to utilize both links bandwidth
– No more than two inter-site links/Remote Copy port groups are supported today

29
Native IP Remote Copy

 IP Partnership Requirements - continued

– If you have one Remote Copy port group, then configure one port from each node in one
I/O group in that Remote Copy port group
– For systems with more than one I/O group, ports from a second I/O group can be added
to the Remote Copy port group
– If you have two Remote Copy port groups and just a single I/O group, then on each
system configure one port from one node in the first Remote Copy port group, and then
a port from the other node in the second Remote Copy port group
– For systems with more than one I/O group, ports from a second I/O group can be added
to each of the two Remote Copy port groups
– A node can have only one port configured in an IP partnership
– If you connect systems by directly attaching them without switches, then you must have
only two direct-attach links, and both direct-attach links must be on the same I/O group.
You should use two port groups where a port group should only contain the two ports
that are directly linked

30
 Storwize Family of Products

GM Update

31
Optimize Global Mirror writes on secondary system
 Strict serialization in the secondary system turned out as the limiting factor for
high bandwidth Global Mirror throughput environments
 V7.2 optimizes GM processing in second site to allow more parallelism
– Secondary nodes store replication writes in new redundant non-volatile cache
– Information about this cache content is shared between nodes
– Nodes intelligently apply these batches in parallel as soon as possible
 What we need to know:
– No changes in Global Mirror commands or management
– Must stop all Global Mirror relationships before upgrading to V7.2
• Check provided by svcupgradetest utility
• Metro Mirror and Global Mirror w/chgvols relationships are fine to be left running
 Results in 3x amount of writes sustained on secondary system volumes used in
regular GM relationships
– Does not apply to GM w/chgvols or Metro Mirror

32
SVC to Storwize V7000 Remote Copy

 V6.3 introduced a new cluster property called “layer”

– SVC is always in “replication layer” mode
– Storwize V7000 is either in “replication layer” mode or “storage layer”
mode
• Storwize V7000 is in “storage layer” mode by default
 Allows SVC to virtualize the system
• Switch to “replication layer” using “svctask chcluster -layer replication”
 Allows SVC to see Storwize as a peer system and replicate between them
Can only be changed via CLI
 “Replication layer” clusters can use storage layer clusters as storage
systems to virtualize
– With V6.4 and later you can now virtualize a Storwize V7000, V5000 or
V3700 with layer=storage behind another Storwize V7000, V5000 or
V3700 with layer=replication
Remote Copy – Configuration Example

FC_partnership_1 IP_partnership_2

SVC V7.2 SVC V7.2 SWV7K V7.2

Cluster A Cluster B Cluster C Layer = replication

Replication layer
Storage layer

IP_partnership_1 FC_partnership_2

SWV5K V7.2 SWV7K V7.2 SWV3700 V7.2

Cluster E Layer = storage Cluster D Layer = storage Cluster F Layer = storage
Summary

 IP replication is a very powerful new feature which:

– Is easy to setup
– Is very relialable
– Creates an IP partnership between two systems
– Provides high throughput over Ethernet network
– Requires no additional licenses

 IP replication requires:
– 1Gbit or 10Gbit LAN infrastructure
– Some additional CPU power
– Some additional fibre channel bandwidth

 We recommend a straight forward setup:

– Two active Ethernet links with two port groups to provide link fail over capabilities
– At least two I/O groups to provide full IP replication bandwidth if one component is offline

35
36
 Advanced Technical Skills (ATS) North America

Accelerate with ATS Storage Webinars

The Free IBM Storage Technical Webinar Series Continues in 2014...

ATS Technical Experts cover a variety of Storage topics

Audience: Clients who either currently have IBM Storage products or are
considering acquiring IBM Storage products. Business Partners and
IBMers are also welcome.
Send Ideas for future topics to
2013 Webinars: patea@us.ibm.com
Jan 15 - TPC Performance Management Jul 11 - IBM Tivoli Storage Productivity Center - Replication
Feb 27 - XIV Technical update Management
Mar 11 - LTFS Library Edition Overview and Demonstration Jul 18 - TS3310 Tape Library Update and Demonstration
Apr 18 - Understanding and Analyzing TS7700 Performance Aug 1 - Disk Options for IBM I
May 29 - Using IBM FlashSystem™ to Achieve Extreme Aug 27 - Tape Options for IBM I
Performance, IBM MicroLatency™, Macro Efficiency and Sep 24 - New Hardware Extensions for SVC CG8 Nodes
Enterprise Reliability Nov 6 – NSeries Technical Update
Jun 25 - Linear Tape File System (LTFS) Enterprise Edition Nov 12 – XIV Storage System Update
Jun 27- DS8870 7.1 Update” Nov 21 – TKLM Technical Update & Demo
Dec 5 – IBM Storwize V7000 Unified: Asynchronous Replication
Upcoming 2014 Webinars: and Active Cloud Engine Global
Jan 16 - Linear Tape File System - Enterprise Edition- New Enhancements
Jan 23 – IBM B-type/Brocade SAN Switch Advanced Features
Feb 11 – z/OS with DS8870 Synergy - HyperPAV, zHPF and I/O Priority Manager
Mar 25 – SVC/Storwize Family IP Replication
Apr 22 – Storwize V5000 - Overview, Capabilities & Product Positioning
How to sign up? To automatically receive announcements of the Accelerate with ATS Storage webinar series, Clients,
Business Partners or IBMers can send an email to accelerate-join@hursley.ibm.com
Information, schedules, and recordings of previous webinars are located in the Accelerate with ATS blog
https://www.ibm.com/developerworks/mydeveloperworks/blogs/accelerate/?lang=en

37 © 2012 IBM Corporation

 Advanced Technical Skills (ATS) North America

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® , XIV

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 Usages 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.

38 © 2012 IBM Corporation

 Advanced Technical Skills (ATS) North America

Disclaimer
Copyright © 2012 by International Business Machines Corporation.

This publication is provided “AS IS.” IBM product information is subject to change without notice.

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. 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 INFRINGEMENT. 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.

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.

IBM makes no representations or warranties, expressed or implied, regarding non-IBM products and services, including those designated as
ServerProven.

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 future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives
only. Contact your local IBM office or IBM authorized reseller for the full text of the specific Statement of Direction.

39 © 2012 IBM Corporation