storwize family software v7.1 technical update

Advanced Technical Skills (ATS) North America

© 2013 IBM Corporation

Storwize Family Software V7.1 Technical Update

Bill Wiegand – Storage ATS [email protected] Watson – Storage ATS [email protected]

mailto:[email protected]



© 2013 IBM Corporation2

Storwize Family Software

Storwize V3500(China only)

Storwize V7000

Storwize V7000 Unified

Storwize V3700

Flex System V7000

SAN Volume Controller

Comprehensive range of virtualized storage systems• One code base on all platforms• One set of functions (selectively licensed)• One client experience



Agenda

Storwize Family Software Enhancements

– Increases to some limits

– New hardware features

– Miscellaneous

Storwize V3700 Specific Enhancements

– New drive features

– New Premium Features

– New Licensing

3



Increased Number of Host Objects

Increase number of host objects per I/O group from 256 to 512 and per cluster limit from 1024 to 2048

– To get to more then 512 total for cluster you must assign hosts to specific I/O groups vs the default which is assignment to all I/O groups

The increased host objects can be used for any host type subject to limit restrictions for that host type. e.g. iSCSI names/IQNs (iSCSI Qualified Names)

– iSCSI hosts are limited by sessions which relate to paths per volume so less hosts are supported with iSCSI then FC or FCoE assuming more then one path is configured per volume mapped to an iSCSI host

4



Increased Number of Host WWPNs

Increase the officially supported number of host WWPNs per I/O group to 2048 and per cluster to 8192

– Benefits AIX LPM configurations and environments using NPIV to map volumes to virtual WWPNs

V6.4.x and earlier software versions are limited to 512 host WWPNs per I/O group and 2048 host WWPNs per cluster.

– Via SCORE we are approving per iogrp/cluster limits of 2048/8192

This increase applies to native FC and/or FCoE WWPNs

5



Increased Number of Volumes per Host

Increase volumes per host from 512 to 2048

Increase in volumes per host is available to any host operating system, subject to that host’s OS limits

– Increase in volumes per host is applicable to FC and FCoE host attachment types

– Does not apply to iSCSI attached servers/hosts

No change in the overall host volume mapping limit per cluster that is currently 20,000

– E.g. Ten hosts with 2048 volumes mapped to each would exceed the overall limit

6



Node Max LUNs per Host Limit

Hosts/ IO Group

SVC 8F2 512 256

SVC 8F4 512 256

SVC 8G4 512 256

SVC 8A4 512 256

SVC CF8 2048 512

SVC CG8 2048 512

Storwize V3700/3500

512 256

Storwize V7000 2048 512

Flex System V7000 2048 512 Clusters with mixed node types have the lowest limit for all I/O groups

7

Limits Tied to Specific Model Types



New Drives

New 4TB NL_SAS 7.2K RPM 3.5” LFF drive supported on Storwize V7000 2076-x12 LFF enclosures only

– Not currently supported on Storwize V3700/3500 models

Supported with Flex System V7000 when using external expansion enclosure model 2076-212 connected to the Flex System V7000 control enclosure

New 1.2TB SAS 10K RPM 2.5” SFF drive supported on Storwize V7000, Storwize V3700/3500 and Flex System V7000 SFF enclosures

– For Storwize V3700/3500 LFF control or expansion enclosures this 2.5” drive is available on a LFF carrier as is the 2.5” SAS 15K RPM 300GB drive and the 2.5” SAS 10K RPM 900GB drive

8



Second FC HBA Feature Code Available

Second 4 port FC HBA was introduced with V6.4.1.4 as iRPQ

– HBA only available for 2145-CG8 node only

Now this HBA is available as a feature code on all new orders of 2145-CG8 nodes

All 8 ports may be used/zoned for host I/O– Host multipathing supports maximum of 8 paths per volume with 4 paths

recommended per volume

Additional ports can be dedicated for local node-to-node I/O– local_fc_port_mask

Additional ports can be dedicated for replication between sites– remote_fc_port_mask

No GUI support in this release for port masking nor is port status information available in the GUI

9



Eight Fibre Channel Ports

External storage controllers may only be zoned with the following FC ports– FC ports 1-6 as viewed from rear of node and reading left to right

– FC ports 1-4 and the two optional FCoE ports on a SVC node

– An error is reported if ports 7-8 are zoned with a storage controller and no MDisks will be discovered via these ports but FC login will still occur

10



Eight Fibre Channel Ports

A node may have up to 16 logins active (unmasked) to any other node in the cluster or to a remote cluster

– Any combination of node-to-node zoning that results in 16 active node logins or less is supported• If >16 active logins from any one node to any other node are received a node error 888

is entered in the event/error log

11



New CLI Fields: lssystem, sainfo lsservicestatus

lssystem

or

sainfo lsservicestatus

..

local_fc_port_mask 000000..0000000000000001111

partner_fc_port_mask 000000..0000000000011110000

..(output shortened, normally 64 bits)

This indicates that:

– fc_io_port_id 1, 2, 3 and 4 are allowed to run node-to-node traffic

– fc_io_port_id 5, 6 ,7 and 8 are allowed to run remote copy traffic

13



New CLI options: chsystem

svctask chsystem -localfcportmask 11

This will result in the local mask being set to 62 0's and two 1's

– 0…00000011

This indicates that FC port id’s 1 and 2 are capable of local node communication and all node-to-node traffic will occur over these connections

– Helpful with SVC stretch cluster configurations with ISLs

svctask chsystem -partnerfcportmask 110000

This will result in the partner mask being set to 60 0's and two 1’s

– 0…00110000

This indicates that FC port id’s 5 and 6 are capable of remote node communication and all site-to-site replication traffic will occur over these connections

– Can configure different port mask for various systems in a partnership

14



Switching between MM, GM and GM w/ChgVols

If all systems are running V7.1.0 or later Storwize Family Software, customers will be able to change between Metro Mirror and Global Mirror, with or without change volumes, and a full resync of all data from the primary volume to the secondary volume is not required

– The relationship or consistency group needs to be in the stopped state before changing the mode of operation

– If customers change from GM w/ChgVols to Metro Mirror, then Metro Mirror can still have change volumes associated with the relationships just as we have done to date with regular GM • Allows for changing between modes easily if desired

Storwize V3700 now supports remote copy so we can replicate between any combination of the following:

– SVC, Storwize V7000, Flex System V7000 and Storwize V3700

15



Easy Tier and RtC

V7.1.x now allows Easy Tier to migrate extents between tiers on compressed volumes within the hybrid storage pool – Previously a compressed volume in an Easy Tier pool was allowed, but no

movement of extents was performed on the compressed volumes

Easy Tier only considers read I/Os for compressed volumes when determining the heat of extents– All other volume types consider reads and writes

There are RtC performance enhancements in the V7.1 software, so for customers interested in using compression upgrading to V7.1 is recommended– Note that current RtC users can not upgrade to V7.1, but a point

release is forthcoming to allow an upgrade with existing compressed volumes

16



AIX Direct Host Attach

V6.4 introduced support for hosts to direct attach to Storwize V7000 and Storwize V3700– This support was explicitly excluded for AIX

With the GA of V7.1 AIX is still not supported initially, but a follow-on point release will provide support in the near future– Most likely with 4Gb HBAs only, support matrix/SSIC should provide

the details so watch this space

– Most likely will support only native AIXPCM multipath driver not SDDPCM but this could change

– When supported, probably with V7.1.0.2, then check support matrix for HBA and driver information• http://www-03.ibm.com/systems/support/storage/ssic/interoperability.wss

17

http://www-03.ibm.com/systems/support/storage/ssic/interoperability.wss



Upgrade to V7.1.x

V6.1.0.0 is the oldest level you can upgrade from so customers running V5.1.x will need to upgrade twice to get to V7.1.x

If compressed volumes are configured on system then you can not currently upgrade to V7.1 unless you migrate all compressed volumes to non-compressed first

– Upgrade test utility will catch this issue and there is notice of this restriction posted at download site

– Will be addressed with a future point release of V7.1 ASAP

18



New Utility for Upgrading Drive Firmware

Drive firmware upgrades prior to the release of this utility were done non-disruptively but one drive at a time using the CLI and it was a manual process

The utility is available at the support portal download site where customers normally access software

19



Upgrading Drive Firmware Using the Utility

Usage:– Upload the utility package to the configuration node

• scp IBM_INSTALL_driveUpgrade_<version> <user>@<cluster_ip>:/upgrade/

– Install the utility package on the configuration node • applysoftware –file IBM_INSTALL_driveUpgrade_<version>

– This does not reboot any nodes– If the configuration node would fail over during the process, the

utility package will have to be reinstalled on the new configuration node

– Upload the drive bundle to the configuration node• scp IBM<product>_DRIVE_<version> <user>@<cluster_ip>:/upgrade/

– Run the utility package to install the firmware on selected drives or to install on all drives use:• utilitydriveupgrade -drivemodel ALL -filename

IBM2076_DRIVE_20110928

20



RtC license is on a per-enclosure basis and prior to V7.1.x there was no monitoring of this licensing

V7.1.0 adds policing of the license whenever new compressed volume copies are created

Using “mkvdisk” and “addvdiskcopy” now give a warning if RtC license is not configured; however, the system will still create the volume or volume copy

The “rmvdisk” and “rmvdiskcopy” may also return the warning if the license is still exceeded

Policing of RtC License for Flex/Storwize V7000Policing of RtC License for Flex/Storwize V7000

21



CLI help changes

New “man” and equivalent “help” command gives the full help for a command> help lsmdisk lsmdisk

The lsmdisk command returns a concise list or a detailed view of managed disks (MDisks) visible to the cluster. It can also list detailed information about a single MDisk.

…

New “help” command on its own gives one-liners> help

addhostiogrp - Maps I/O groups to a host object.

addhostport - Adds worldwide port names (WWPNs) or iSCSI names to a host object.

addmdisk - Adds managed disks to a storage pool.

addnode - Adds a new (candidate) node canister to an existing system. ...

22



CLI help changes

New “-?” or equivalent “-h” switch gives syntax> svcinfo lsnode -?

Syntax

>>- lsnode | lsnodecanister ------------------------------------>

>--+--------------------------------+-- --+----------+-- ------->

'- -filtervalue -- attrib=value -' '- -nohdr -'

>--+-----------------------+-- -- --+-----------------+--------->

'- -delim -- delimiter -' '- -filtervalue? -'

>--+---------------+-------------------------------------------><

+- object_id ---+

'- object_name -'

For more details type 'help lsnode'

23



FYI – IBM i Native Attach of SVC/Storwize Family

IBM POWER7 and POWER7+ systems

IBM SVC and Storwize V7000, V3700, V3500 running V6.4.1.4 or later Storwize Family Software

Load source support included

Full use of PowerHA – Metro, Global, and LUN level switching

IBM i 7.1 native support with Technology Refresh 6 + PTFs MF56600, MF56753, MF56854

IBM i 6.1 and 7.1 virtual clients of IBM i 7.1 partitions

4 Gb and 8 Gb FC adapters for fabric attach

4 Gb FC adapters for direct attach (feature codes 5774 or 5276)

Check SSIC and developerWorks for specific configuration details

IBM Storwize V7000 IBM Storwize V3700

24



For SAN attach each port will log into one port on each node – Recommend zoning 1 host HBA port to

one port from each node canister

Direct fibre channel attach is supported

Variable sized LUN support– Recommend 80 GB on the

SVC/V7000/V3700 as the minimum size• Remember 11% is lost to 9th sector due to

512/520 byte block conversion

– Use of less than six volumes is not recommended as more targets is better

Recommend formatting volume before assigning to IBM i host

FYI – IBM i Native Attach of SVC/Storwize Family

25



FYI – iRPQ Available for SVC with RtC

iRPQ 8S1296 (chubby node) requires SVC V6.4.1.4 and currently cannot upgrade to V7.1, should be fixed in next point release coming soon

– Optional 2nd 6 core CPU and additional 24GB of cache● Only supported in 6 core CPU CG8 models, not early 4 core CG8 models

– Only for use with Real-time Compression (RtC)● Today with 6 core CPU at creation of first compressed volume 4 cores and 2GB

of memory are reserved for RtC use only Leaves 2 cores and 22GB of memory for regular I/O and advanced functions

● With addition of iRPQ 8S1296: Eight cores and 24GB of memory will be allocated to RtC Four cores and 24GB of memory will be allocated to regular I/O and advanced

functions which is what is normally available in a CG8 node

26



FYI – FlashSystem 7xx/8xx Support

V7.1 provides general support of the IBM FlashSystem 7xx/8xx storage system with SVC and the Storwize Family without the need for a SCORE

– SCORE still required for V6.4.x and earlier software levels

– There is a special version of V6.4.1.4 with an iFIX to correctly recognize the FlashSystem when SVC and Storwize/Flex System V7000 discover the system• V6.4.1.5 is on the horizon to address this issue for V6.4.1 without need for iFIX

Issue is during blue wash of TMS RAMSAN and name change to FlashSystem we changed the VPD thus when virtualization layer discovers the storage system we don’t know what it is and default to generic controller which is not a supported controller type

– Again fixed with V7.1, V6.4.1.4 with iFIX and shortly with V6.4.1.5

27



What’s new with the Storwize V3700?

Al Watson – Storage ATS [email protected]




Agenda

New Hardware

New Premium Features

Licensing



Hardware Updates



New Drives

Size Type

146GB/300GB 2.5” 15K HDD

300GB/600GB/900GB/1.2TB* 2.5” 10K HDD

500GB/1TB 2.5” 7.2K Nearline HDD

300GB* 3.5” 15K HDD

900GB*/1.2TB* 3.5” 10K HDD

2TB/3TB 3.5” 7.2K Nearline HDD

200GB/400GB 2.5” SDD

Notes: Only V3700 drives can be used in V3700 enclosure

Drive types can be mixed within an enclosure



SAS Host Attachment

Supported on V3500 and V3700 only with internal SAS ports on the control canister.

New HIC (Host Interface Card) add-on available for V3700 only.

Interoperability:– Direct attach ONLY

– No support for SAS Switches or Expanders.

– Supported Host types:• SLES 10.4, SLES 11.1, SLES11.2, RH5.8, RH6.1, • W2008_R2_SP1, W2008_SP2, W2012• VM4.1, VM5.0, VM5.1 (with 7.1.0.1 ptf).

– Not supported on AIX

32



Additional SAS Host Interface Card

SAS+FC 1 SAS

Expansion Port (port 4)

3 SAS Host Ports

4 FC Ports

SAS+SAS 1 SAS

Expansion Port (port 4)

7 SAS Host Ports

0 FC ports

33



SAS Host Attachment – Typical Configurations

34



New GUI Create SAS Host

35



New GUI Create SAS Host (Cont’d)

36



SAS Host Attachment - New Command lines

lsportsas - extended adding more fields, example:>lsportsas

id port_id port_speed node_id node_name WWPN status switch_WWPN attachment type

0 1 3Gb 1 node1 500507680140004A offline enclosure enclosure

1 2 6Gb 1 node1 500507680150004A online 5001234567892000 switch host

4 1 3Gb 2 node2 50050768014051E5 online host host

5 2 3Gb 2 node2 50050768015051E5 offline_unconfigured none none

lssasportcandidate - NEW CLI>lssasportcandidate

sas_WWPN200600A0B813B7AC200600A0B813B7AD

lsfcportcandidate - NEW CLI

(replaces lshbaportcandidate, which is removed from documentation but retained for backwards compatibility)

>lsfcportcandidate

fc_WWPN

200600A0B813B7AC

200600A0B813B7AD

37



SAS Host Attachment - New Command lines

lshost - extended adding SAS WWPN concise>lshost 0

id 0name host0port_count 10type genericmask 1111111111111111111111111111111111111111111111111111111111111111iogrp_count 4status offlineSAS_WWPN 1000000000000009node_logged_in_count 0state offlineSAS_WWPN 1000000000000008node_logged_in_count 0state offline

mkhost and addhostport and rmhostport. Add -saswwpn and rename -hbawwpn to fcwwpn

>mkhost -saswwpn 210100E08B251DD4:210100F08C262DD8

>mkhost -fcwwpn 210100E08B251EE6:210100F08C262EE7

>addhostport -saswwpn 210100E08B251DD4 host1

>addhostport -fcwwpn 210100E08B251EE6 host1

(-hbawwpn is removed from documentation, retained for backwards compatibility)

38



SAS Host Events and Node Errors

New events and error codes for new hardware (non-fatal): Node error 715

– Fewer SAS host ports operational - Some or All Ports Are Offline

Node error 717 – SAS host ports operating at reduced speed

Event 987108 – Additional SAS host ports connected - When new ports connected.

Update error code 1669 (Event 010100)– SAS host port has unsupported device attached– Change DMP

New Error Code 1667 (and DMP)– Host ports Offline - One or mode connections lost

New Error Code 1668 (and DMP)• Host ports Degraded - One or more lanes in 4 lane PHY not functioning or

incorrect speed

39



Features



Standard Features which don’t require a license

Expansion enclosures– Up to four expansions can be added at any point to increase the storage capabilities

of the system

– Both 2.5 and 3.5 expansions can be mixed as needed

Thin provisioning– Space-Efficient Volumes

Volume Mirroring– Use for ease of migrating volumes from one storage pool to another and when

migrating data into the V3700 from an external storage system

FlashCopy– Maximum of 64 targets allowed without license

– When the number of mappings created has reached the limit the user will be unable to create any further flash copy mappings

SAS Host attachment– With three standard ports on the each control canister

– Plus the optional four port SAS HIC card

41



Advanced Features which can be licensed

Turbo mode– Removes CPU-throttling to increase performance

Easy-Tier– Allows the proper usage of shared storage pools with HDD and SSD mdisk for

high usage access to be mapped to the SSD mdisk for best performance

– Profiling of access patterns to Storage Pools. A plan gets sent back to the user for their perusal. The license would turn this on or off.

Metro Mirror and Global Mirror– Provides remote replication for both Metro and Global environments utilizing both

synchronous and asynchronous mirroring, including low-bandwidth support feature with change volumes.

– Same limits as V7000 when licensed

FlashCopy– A license for full FlashCopy support for up to 2040 targets can be purchased.

• The user may not revoke the flash copy license whilst the number of targets exceeds the limits. Deactivation will fail with an appropriate message informing the user to decrease the number to 64 or less.

42



Features which are not available for the entry level

Real-time Compression

Virtualization of external storage systems– Only supported for migration of data using image mode with external storage

volumes

System clustering– The V3700 supports only one I/O group in its configuration

43



Advanced Features

Easy Tier– Provides support for HDD and SSD shared storage pools to provide

high performance tiering of data

Metro and Global Mirroring support– Mirroring of volumes from and to another V3700, SVC, V7000 and Flex

System V7000

FlashCopy– Maximum of 64 targets allowed without license– When the number of mappings created has reached the limit the

user will be unable to create any further flash copy mappings

44



Feature Licensing



Motivation for licensing

Different platforms have different needs– SVC and V7000 are mid-range products with some standard and advanced

features (Easy Tier, Copy Services, RTC, etc…) which the V3700 may or may not need to make use of

– V3500/V3700 are entry-level products

– All have the same software but we need them to behave differently

– Allow V3700 to license some features

Enforcement of licenses on entry-level products

Allows customers to try features on entry-level products for a short period before buying

Changes currently apply to V3700 only

46



Licensing scheme

Is honour-based system for SVC/V7000– On SVC and V7000, customer uses “svctask chlicense” to tell the system what

license they have purchased

– Part of the EZSetup GUI

– Sold by Capacity-based for SVC, or enclosure-based for V7000

– Software warns when license is 90%-used and exceeded with CLI errors and errors in event log but doesn’t disable features

Prior to Release 2 there were no advanced features for V3500/V3700

Now:

With Release 2 (V7.1) we have advanced features which require license keys for the system to make use of them

– One time charge for each feature that covers entire system no matter how many enclosures in system

47



Licensing terminology

Authorization Code – String sent to customer and combined with Machine Signature to create

License Key

License Key– String input into a specific system that enables a feature

License File– File containing one or more License Key

Locking Out– Ability to disable features even if a valid License Key is entered

Trial License– Temporary or partial license for a feature– May be limited by either the length of time the feature is available for, or by

limiting the number of times the feature can be exploited.

Machine Signature– Machine-specific string which can be combined with Authorization Code to

create a License Key

48



Features with trial periods available

Easy-Tier– 90-day trial– Trial covers both the measurement capability and the implementation of Easy-Tier– On expiration of the trial period, all of Easy-Tier's profiling will cease and no

relocation of data will occur, but the data will stay intact as it is defined for continued use

– If the customer does not opt to purchase the license for Easy Tier, it is assumed that the SSD mdisk will be deleted from the storage pool and redefined to their own storage pool for other dedicated usage rather then left in the current pool as shared mdisks

Remote Copy – 90-day trial– On expiration of the trial period, all existing relationships and partnerships will stop– The consistency of the remote copy will not change from this point

Turbo Mode – 90-day trial– On expiration of the trial period, CPUs are clocked back down to the standard speed

49



State machine for licenses

50



Querying the Machine Signature

Used to get the Machine Signature to be combined with he Authorization code to give a License key

New “machine_signature” field for the existing “lsenclosure” query In both full and concise views Examples> lsenclosure

id status type … machine_signature

1 online control … 0123-4567-89AB-CDEF

> lsenclosure 1

id:1

Status online

Type control

.

.

.

machine_signature 0123-4567-89AB-CDEF

51



Licensed Function Activation Overview

IBM Manufacturing Client DSFA web site

(Data Storage Feature Activation)

https://www-03.ibm.com/storage/dsfa/home.wss

• Validate machine information• Decrypt / validate Authorization Code• Generate and display License Key • Optional download function (XML file)• Record information in database

• Place licensed function order• Ship unique Licensed Function

Authorization document for each function ordered

• Access Storwize GUI• Obtain machine information

• Access DSFA web site• Enter machine information

• Machine type• Serial number• Machine Signature

• Enter Authorization Code

• Download License Key from DSFA• Enter License Key into GUI to

technically activate function

Notes:• Process flow is the same whether

function is ordered with machine, separately from machine, or as MES for an installed machine.

• The Authorization Code is a “voucher” with a single use, unique encrypted value. It is not associated with any machine until the “activation” process has been completed.

• “Automatic activation” is the preferred method if the machine is connected to the Internet

• “Manual activation” is used if the machine is not connected to the Internet (dark data center)

• DSFA web site: www.ibm.com/storage/dsfa

• Receive Authorization document

• Access Storwize GUI• Enter Authorization Code

• GUI sends request to DSFA• Machine type• Machine serial number• Machine Signature• Authorization Code

• Validate machine information• Decrypt / validate Authorization Code• Generate and return License Key • Record information in database

API• GUI receives License Key• GUI applies License Key to

technically activate function

Either

Ma

nu

al a

cti

vati

on

Automatic activation

API

52





Querying available features

lsfeature – NEW CLI

> lsfeature

id name state license_key trial_expiration_date

0 turbo_performancetrial_available 20130201

1 easy_tier trial_active 20130101

2 flashcopy_upgrade active 0123-4567-89AB-CDEF

3 remote_mirroring trial_expired 20130201

53



Activating features

Used to activate a feature on the storage system using a license key or keyfile or t0 activate a trial period of a feature

activatefeature – NEW CLI

svctask activatefeature (-trial <feature_id or feature_name>

| -licensekey <key> | -licensekeyfile <filepath>)

– feature_id and feature_name as for lsfeature

– licensekeyfile <- HOW CREATED?

Examples>svctask activatefeature -trial 1 Activation of a trial is a one time

operation. Are you sure you wish to continue? Yes

>svctask activatefeature -licensekey 0123-4567-89AB-CDEF

>svctask activatefeature -licensekeyfile /tmp/keyfile.xml

54



Deactivating features

Used to deactivate a feature on the storage system or terminate a trial period of a feature

deactivatefeature – NEW CLI

svctask deactivatefeature <feature_id | feature_name>

– feature_id and feature_name as for lsfeature

Example> svctask deactivatefeature -feature 1 You are removing the ability to

use a feature of this system. Are you sure you wish to continue? Y

55



License errors in the event log

New errors– 009189 SS_EID_IC_LICENSE_TRIAL_EXPIRED

– 009193 SS_EID_IC_LICENSE_TRIAL_EXPIRES_45_DAYS




All auto-fixed by different expiry warning or by activatelicense

56



DMP actions for error event

DMPs for expiry warnings and errors will all prompt for installing license key

If trial has expired or feature has been deactivated, DMP will perform appropriate clean-up actions, e.g.– removing MM/GM partnerships and relationships

– removing SSD arrays for EasyTier

DMP will contain information about how to contact IBM to purchase a license

57



GUI

58



GUI

59



GUI

60



GUI

61



The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:IBM, IBM Logo, on demand business logo, Enterprise Storage Server, xSeries, BladeCenter, eServer, ServeRAID andFlashCopy, System Storage, Tivoli, Easy Tier, Active Cloud EngineThe following are trademarks or registered trademarks of other companies.Intel is a trademark of the Intel Corporation in the United States and other countries.Java and all Java-related trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries.Lotus, Notes, and Domino are trademarks or registered trademarks of Lotus Development Corporation.Linux is a registered trademark of Linus Torvalds.Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation.SET and Secure Electronic Transaction are trademarks owned by SET Secure Electronic Transaction LLC.UNIX is a registered trademark of The Open Group in the United States and other countries.Storwize and the Storwize logo are trademarks or registered trademarks of Storwize Inc., an IBM Company.

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

The information on the new products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new products is for informational purposes only and may not be incorporated into any contract. The information on the new products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion.

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.

This presentation and the claims outlined in it were reviewed for compliance with US law. Adaptations of these claims for use in other geographies must be reviewed by the local country counsel for compliance with local laws.

Legal Information and Trademarks

storwize family software v7.1 technical update

Technology

host increase volumes

number of host wwpns

number of host objects

increased host objects

host type subject

fcoe host attachment

storwize v37003500

ibm corporation new