Download ppt - Slide 1 - common.es

Transcript
Page 1: Slide 1 - common.es

© 2008 IBM Corporation

IBM Power Systems

i5/OS V6R1 Virtual Client Partitions VIOS, Blades and DS4000 Storage

Page 2: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

2

Agenda

Overview: Virtualization enhancements for i5/OS

i5/OS host & i5/OS client

VIOS host, i5/OS client & DS4000 attachment

Page 3: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

3

Virtualization Enhancements for i5/OS

Page 4: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

4

i5/OS Virtual Client Partitions

i5/OS-based Virtualization– i5/OS partition uses I/O resources from another i5/OS

partition– Eliminates requirement to buy adapters and disk drives

for each i5/OS partition– Supports simple creation of additional partitions …. e.g.,

for test and development– Requires POWER6 systems with i5/OS V6R1– PowerVM not required– Can mix virtual and direct I/O in client

Platform support– All POWER6 System i models* (non-blade)

Storage support– Determined by host i5/OS partition (SAN, EXP24,

integrated disk)

LPAR management– HMC

i5/OS

Hypervisor

i5/OS

POWER6

* All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Page 5: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

5

PowerVM Virtualization

i5/OSVIOS

Hypervisor

POWER6

VIOS-Based Virtualization– i5/OS partition uses I/O resources from Virtual I/O

Server (VIOS)

– VIOS is included with PowerVM Standard and Enterprise Edition

– VIOS also provides virtualization for AIX and Linux partitions

– Requires POWER6 systems with i5/OS V6R1

Platform support– All POWER6 System i models

– POWER6 Blade models

Storage support– Enables attachment to DS4700 y DS4800

– Models DS8000 (via Blade only)

LPAR management– HMC or IVM*

* 570 and 595 systems require an HMC

Page 6: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

6

* 570 and 595 systems require an HMC

Tool that runs in VIOS partition for creating and managing partitions

Provides an alternative to HMC for LPAR management*

Requires VIOS to own i5/OS I/O resources

Included with PowerVM Standard Edition

Requires POWER6 processor-based systems with i5/OS V6R1

Integrated Virtualization Manager (IVM)

Page 7: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

7

Browser-based interface, supports Mozilla Firefox and Internet Explorer

Performs LPAR and virtualization management on POWER6 blade

Integrated Virtualization Manager

Page 8: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

8

IVM Example: Create i5/OS Partition

Fewer steps than HMC

IVM uses several defaults

Virtual I/O resources only

Page 9: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

9

IVM Example: i5/OS Partition Properties

Load source and alternate IPL devices default to virtual Changes are always DLPAR changes (when possible) Virtual disk assigned to i5/OS by selecting available hdisk, then clicking OK (all available hdisks are assigned in this example)

Page 10: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

10

Virtualization Scenarios

+ + +Host LPAR

Client LPAR

POWER6 system

HMC

Hardware platform: POWER6 System i (not POWER6 blade) Host LPAR: i5/OS LPAR management: HMC Storage: Any supported by i5/OS host

Hardware platform: POWER6 System i Host LPAR: VIOS LPAR management: HMC Storage: DS4000 (not DS8000)

+ + +VIOS Host

LPARClient LPAR

POWER6 system

HMC

+DS4000

Hardware platform: POWER6 blade Host LPAR: VIOS LPAR management: IVM (part of VIOS) Storage: Fibre Channel or SAS* (SOD)

+

VIOS + IVM

Client LPAR

+

POWER6 Blade

FC or SAS

+

* All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Page 11: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

11

i5/OS Client with i5/OS Host

Page 12: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

12

i5/OS V6R1 Host and Client Partitions: Overview

i5/OS Host

Virtual SCSI connection

i5/OS Client

FC 5294

EXP24

DS8000

DVD

DDxx

NW

SS

TG

s

DDxx

OPTxxDVD

OPTxx

IVE Virtual LAN connection

CMNxx

Requirements– POWER6 hardware

– V6R1 on host and client

– PowerVM not required

DASD– Hardware assigned to host LPAR in

HMC

– DASD can be integrated or SAN

– DASD virtualized as NWSSTG objects

Optical– DVD drive in host LPAR virtualized

directly (OPTxx)

Networking– Network adapter (such as IVE) and

Virtual Ethernet adapter in host LPAR

– Virtual Ethernet adapter in client LPAR

Virtualization of Tape Devices is not supported

Page 13: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

13

Host LPAR Configuration – HMC

Virtual SCSI server adapter

At least 1 required per client LPAR, but more possible

Configured to connect to specific adapter ID on client LPAR

Page 14: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

14

Client LPAR Configuration – HMC

Virtual SCSI client adapter

DASD and optical are accessible through the same VSCSI client adapter

By using multiple adapters, a virtual client LPAR can use DASD from multiple hosts

Page 15: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

15

Client LPAR Configuration – Load Source Both B- and D-mode IPL

devices are set to virtual SCSI client adapters

When installing virtual client LPAR, D-mode IPL is performed from DVD drive in host LPAR

LIC and OS are installed on NWSSTG (Network server storage space) objects

Page 16: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

16

Host LPAR Configuration – i5/OS View

Virtual SCSI server adapter in i5/OS (290B device)

Page 17: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

17

Host LPAR Configuration – Storage Spaces

Storage space objects in host LPAR

Each NWSSTG is a DDxx in client LPAR

Page 18: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

18

Host LPAR Configuration – Storage Spaces

Creating a storage space

Identical to creating a storage space for AIX or Linux client today

Page 19: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

19

Host LPAR Configuration – NWSDs

WRKCFGSTS *NWS provides list of NWSD (Network Server Description) objects

Each client LPAR has at least 1 NWSD associated with it

NWSD provides link between storage space object and VSCSI adapters

Page 20: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

20

Installing Client Partition from IMGCLG

An image catalog can be used to install multiple virtual client LPARs or PTFs

Page 21: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

21

Client LPAR Configuration – Configured DASD

Virtual client LPAR’s System ASP with 4 virtual disks (storage spaces)

Page 22: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

22

Backups for i5/OS V6R1 Client with i5/OS Host

Simplest approach is to use Dynamic LPAR (DLPAR) resource movement and switch physical tape adapter to client LPAR

– Mixing of virtual and direct resources in client is supported

– DLPAR movement of resources can be scheduled in the HMC

For full-system backup, the client storage spaces can be saved on the host i5/OS partition

– Similar to AIX and Linux client partitions

– File-level backup is not supported

– Storage spaces can be restored on another i5/OS V6R1 host

– Storage spaces can be located in IASP, Flash Copy can be used on IASP

Page 23: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

23

i5/OS Client with VIOS Host and DS4000 Attachment

Page 24: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

24

System i VIOS – Virtual I/O Server Partition

VIOS Host

AIXorLinux

I5/OSPhysical

DiskPhysical

DiskPhysical

DiskPhysical

DiskPhysical

Disk

Pool of physical I/O resources to share between logical partitions on the system

Creating more logical partitions than there are I/O slots or physical devices available

AIX, Linux Client Partitions

Now 5/OS Clients Partitions

Dedicated partition for VIOS

Virtual SCSI for Disk (VSCSI)

Virtual Networking for LAN adapters (SEA = Shared Ethernet adapters)

Implemented via SW in a Logical Partition

Managed by HMC/IVM

Page 25: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

25

i5/OS V6R1 Client + VIOS Host + DS4000

VIOS Host

Virtual SCSI connection

i5/OS Client

DS4700DS4800

DVD

hdiskX LUNs DDxx

/dev/cd0DVD

OPTxx

IVEVirtual LAN connection

CMNxx

DASD– Hardware assigned to

VIOS LPAR in HMC

– Each SAN LUN virtualized directly to i5/OS client

– LUNs are 512B open storage

Optical– DVD drive in VIOS

virtualized directly (OPTxx)

Networking– i5/OS client LPAR is

assigned a Virtual Ethernet adapter

– VIOS uses virtual Ethernet bridge to connect VLAN and physical LAN

SEA

System i POWER6 platform or JS22 Blade

Page 26: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

26

VIOS Storage Connectivity Big Picture

POWERHypervisor

AIX or Linux

VIOS Partition

Physical Fibre

ChannelAdapter

Virtual SCSI

Server Adapter

Virtual SCSI Client

Adapter

i5/OS

Virtual SCSI Client

Adapter

Physical Fiber

ChannelAdapter

Virtual SCSI

Server Adapter

DS4700DS4800

SVC

SAN

Fibre Channel

SAN

Not supportedWith i5/OS

Page 27: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

27

520 sector to 512 sector change

i5/OS traditionally have been 520 byte sectors

Now ONLY with i5/OS clients using VIOS we have 512 byte sectors

This is not supported for direct FC attach to i5/OS

SLIC knows whether the disk is 520 or 512– Decision is made as the disk units enlist to the i5/OS

520 sectors fit on 8 pages

512 sectors fit on 9 pages– SLIC simply reads 9x 512 byte data sectors for every 8 actual sectors

– 9th page needed for the extra 8 bytes

– This may cause some performance impact

Page 28: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

28

Requirements and Support for i5/OS + VIOS + DS4000

Server Side– i5/OS cannot connect directly to DS4000– POWER6 hardware is required– VIOS 1.5 with Fix Pack 10.1 or later is required– i5/OS V6R1 or later is required

Attached Storage– Only DS4700 and DS4800

– Only Fibre Channel drives are supported– For both POWER6 Blade and other POWER6 System i models

– DS8100 and DS8300 are supported only in the POWER blade environment– Not for other POWER6 System i models

– SAN Volume Controller (SVC) is not supported by i5/OS – Directly or through VIOS

– DS4000 FlashCopy– Not currently supported, testing underway

System Storage Manager– Initially: System Manager 6.6.0.x is supported– Later: System Manager 10.10.x will be supported 

Page 29: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

29

The DS4000 Family

DS4200(follow-on to DS4100)

DS4700(follow-on to DS4300)

DS4800(follow-on to DS4500)

Machine/Models 1814-7Vx 1814-70x,-72x 1814-80x,-82x,-84x,-86x

Enclosures Control Unit + 6 EXP810 Control Unit + 6 EXP810 Control Unit + 14 EXP810

…Control Unit (no drives) +

Up to 14 expansion units

…Control Unit +

up to 6 expansion units

…Control Unit +

up to 6 expansion units

Supported on i5/OS on Power 6 via VIOS

Page 30: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

30

The DS4000 Family

DS4200(follow-on to DS4100)

DS4700(follow-on to DS4300)

DS4800(follow-on to DS4500)

Machine/Models 1814-7Vx 1814-70x,-72x 1814-80x,-82x,-84x,-86x

Drive Types SATA only** not supported for i5/OS

SATA or FC** only Fibre Channel for i5/OS

SATA or FC** only Fibre Channel for i5/OS

Max Physical Drives 112 drives 112 drives 224 drives

Max Logical Drives (LUNs) 1024 1024 2048

Total Disk - SATA - Fibre

84-112 TB 84-112 TB 168-224 TB

n/a 33-112 TB 67-224 TB

Performance - MB/sec

- Disk IO/s

- - Cache Disk IO/s

990 MB/sec 990 MB/sec 1240-1600 MB/sec

11,200 io/sec 44,000 io/sec 62,000-86,000 io/sec

120,000 io/sec 120,000 io/sec 375,000-575,000 io/sec

Cache 2 GB Mdl 70: 2 GB, Mdl 72: 4 GB Mdl 80/82: 4 GB

Mdl 84: 8 GB, Mdl 86 – 16 GB

Max DS4K Partitions 128 128 512

RAID levels 0,1,3,5,7 0,1,3,5,7 0,1,3,5,7

RAID 6 with SM 10.10 RAID 6 with SM 10.10 (no RAID-6)

Supported on i5/OS on Power 6 via VIOS

Page 31: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

31

The System Manager GUI Interface – Create a LUN

1) Choose the DS4000 to Use

2) Choose to Create LUNs

3) Choose automatic or manual configuration

4) Check the parameters

5) Tadaa!

Page 32: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

32

Planning i5/OS clients via VIOS to DS4700/DS4800

Configurations– Fiber channel adapters are 4GB and 2GB

– 4GB is recommended

Modeling and sizing– You must use Disk Magic

– VIOS disk information is taken into account within Disk magic

– Performance Considerations

Planning– Check the i5/OS Virtualization and DS4000 Read-me Firsthttp://www-3.ibm.com/systems/i/os/i_virtualization_and_ds4000_readme.pdf

Page 33: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

33

DS4000 Sizing with Disk MagicPerformance Tools Reports

Workload Estimator Input

Manual Input of Disk Workload

1) Gather Input Data 2) Start Disk Magic 3) Read in or Key in Base System Data 4) Create the Base System Model

To get your Copy of Disk Magic:• Go to System Sales or Partnerworld Website• Search on “Disk Magic”

Page 34: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

34

DS4000 Sizing with Disk Magic

2 x RAID 1073 GB disks

0

0.5

1

1.5

2

2.5

Base Internal 10K rpm 73GB RAID 10 15K rpm 73GB RAID 10

Configurations

Re

sp

on

se

Tim

e C

om

po

ne

nts

in m

s

Wait time (ms)

Service Time (ms)

2 x RAID 10 ranks 73GB disks

1

1.5

2

2.5

3

3.5

4

4.5

567 767 967 1167 1367 1567 1767 1967 2167

I/O Rate (I/Os per second)

Serv

ice T

ime in

ms (iS

eri

es)

10K rpm

15K rpm

Performance Tools Reports

Workload Estimator Input

Manual Input of Disk Workload

1) Gather Input Data 2) Start Disk Magic 3) Read in or Key in Base System Data 4) Create the Base System Model

5) Describe Proposed Hardware 6) “Solve” the Model 7) Print Results – Reports + Graphs showing Response Time + Growth Projections

To get your Copy of Disk Magic:• Go to System Sales or Partnerworld Website• Search on “Disk Magic”

Page 35: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

35

DS4000 Performance on System i – DS4000 SetupDS4000 Setup

• Set up RAID as close to the physical drive as possible (ie on the DS4000)

• Make a reasonable number of LUNs, sized for 1-2 LUNs per DDM

• Make symmetrical configurations• Uniform LUN size• RAID sets all the same size• RAID sets balanced across enclosures

• Avoid sharing physical disks between i5/OS hosts

• Create a separate VIOS for every 3 Power 6 processors or so

For details, see Chapter 14.5 of the i5/OS Performance Capabilities Reference Manual (PCRM) at:http://publib.boulder.ibm.com/infocenter/systems/scope/i5os/index.jsp?topic=/books/sc410607.pdf

DS4000System Manager

RemoteSupport Manager

Page 36: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

36

DS4000 Performance on System i – VIOS Setup

VIOS Setup

• Avoid VIOS volume groups – they add overhead without any benefit for our platform. Use commands to set the volume indentifier instead

• Max 16 virtual disks on a virtual SCSI adapter

• Use dedicated vs shared processors on VIOS if possible

• VIOS appears to need 1-2 GB of memory for a 1-CPU VIOS partition, more if virtual LAN is in use

For details, see Chapter 14.5 of the i5/OS Performance Capabilities Reference Manual (PCRM) at:http://publib.boulder.ibm.com/infocenter/systems/scope/i5os/index.jsp?topic=/books/sc410607.pdf

Page 37: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

37

DS4000 Performance on System i – System i Setup

If you need the best performance possible:

• Consider

• Integrated disk first

• Native external disk next (DS6K/DS8K attached via 4 Gbit fibre)

• VIOS configurations last – throughput is OK but response time can be hard to control

• Choose RAID-1 or RAID-10 over RAID-5

i5/OS Setup

• Separate Journal Receivers from Databases – put them on separate DDMs and separate DS4K controllers if possible

For details, see Chapter 14.5 of the i5/OS Performance Capabilities Reference Manual (PCRM) at:http://publib.boulder.ibm.com/infocenter/systems/scope/i5os/index.jsp?topic=/books/sc410607.pdf

Page 38: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

38

VIOS Configuration

Partition type is VIOS (not AIX)

Physical storage adapter assigned to VIOS

At least one Virtual SCSI adapter pair (server-client) exists per i5/OS client

Detailed VIOS information in APV Operations Guide (

https://www.ibm.com/servers/resourcelink/lib03030.nsf/pages/AdvancedPowerVirtualizationOperationsGuide)

Page 39: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

39

VIOS Installation

Install similar to AIX

Use HMC console and DVD drive or Network Install Manager (NIM) server

Detailed VIOS information in APV Operations Guide (

https://www.ibm.com/servers/resourcelink/lib03030.nsf/pages/AdvancedPowerVirtualizationOperationsGuide)

Page 40: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

40

VIOS Virtual Resource Configuration

Once physical devices are available in VIOS, they can be configured as virtual resources for client partitions

– Example: physical LUN hdiskX can be mapped as virtual disk for i5/OS by creating a virtual target device (vtscsiX)

VIOS command line is used– Telnet to VIOS; default administrator ID is padmin

VIOS command examples– lsdev: shows physical and virtual devices– cfgdev: discovers newly added devices (such as new LUNs)– mkvdev: creates virtual devices to make resources available to

client partitions

VIOS commands to virtualize resources are well documented– IBM Systems Information Center

(http://publib.boulder.ibm.com/infocenter/systems/scope/hw/index.jsp?topic=/iphb1/iphb1_vios_commandslist.htm)

– APV Operations Guide (

https://www.ibm.com/servers/resourcelink/lib03030.nsf/pages/AdvancedPowerVirtualizationOperationsGuide

Page 41: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

41

i5/OS Client HMC Configuration

Virtual SCSI client adapter

DASD and optical are accessible through the same VSCSI client adapter

By using multiple adapters, a virtual client LPAR can use DASD from multiple hosts

Page 42: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

42

i5/OS View of VIOS Resources

Virtual storage IOA is the VSCSI client adapter

Disk units are virtual target devices mapped to LUNs in VIOS

Page 43: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

43

i5/OS View of VIOS/DS4K LUNs

Serial # comes from VIOS

Type is always “6B22”

Any LUN Size is acceptable – no need to match integrated drive sizes

Virtual disks (LUNs) from VIOS initially show as non-configured drives (DDxx)

Virtual disks have been added to ASP1 in this example

Page 44: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

44

Backups for i5/OS as Client of VIOS

Simplest approach is to use Dynamic LPAR (DLPAR) resource movement and switch physical tape adapter to i5/OS client

– Mixing of virtual and direct resources in i5/OS client is supported– Does not apply to POWER blade environment

– DLPAR movement of resources can be scheduled in the HMC

Other backup solutions exist– i5/OS save to virtual tape IMGCLG; FTP IMGCLG files to another i5/OS partition

– i5/OS save to virtual optical IMGCLG, FTP images to VIOS or another i5/OS

– i5/OS save to file-backed virtual optical in VIOS; VIOS TSM client save over network

– i5/OS save to file-backed virtual optical in VIOS; FlashCopy VIOS virtual media LUNs and attach to 2nd VIOS

– FlashCopy (full copy) VIOS LUNs assigned to i5/OS; bring up separate i5/OS partition under VIOS from copy

– Replicate VIOS LUNs assigned to i5/OS; bring up separate i5/OS partition under VIOS from copy

Page 45: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

45

vSCSI Target Device

FC or SCSI

vSCSIServerAdapter

vSCSIClientAdapter

disk

Power6 Hypervisor

I5 partition Virtual IO server

Adapter

Disk driver

DS4700/4800

VIOS HA Considerations

NO High Availability solution

I5/OS partition depend on VIOS partition availability & DS4000

Page 46: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

46

FC or SCSI Device

vSCSI Target Device

vSCSIServer

vSCSIClient

disk

Power6 Hypervisor

I5 partition Virtual IO server

Adapter

Disk driver

DS4700/4800

Virtual IO server

vSCSI Target Device

Adapter

Disk driver

disk

vSCSIClient

vSCSIServer

i5Mirorring

VIOS HA Considerations

I5/OS disk in mirroring for i5/OS protection

I5/OS partition not dependent from a VIOS

Single Point of failure is system i & DS4000

Page 47: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

47

FC or SCSI

vSCSI Target Device

vSCSIServer

vSCSIClient

disk

Power6 Hypervisor

I5 partition Virtual IO server

Adapter

Disk driver

DS4700/4800

Virtual IO server

vSCSI Target Device

Adapter

Disk driver

disk

vSCSIClient

vSCSIServer

FC or SCSI

DS4700/4800

Adapter

Disk driver

Adapter

Disk driver

Multi-path Driver

Multi-path Driver

i5Mirorring

VIOS HA Considerations

I5/OS mirroring with one disk of the disk pair on a DS4000 and the other disk on another DS4000

No replication between DS4000 Avoid Single point of Failure for the DS4000

Page 48: Slide 1 - common.es

IBM Power Systems

© 2008 IBM Corporation

48

More Information

APV Operations Guide (VIOS information)– https://www.ibm.com/servers/resourcelink/lib03030.nsf/pages/AdvancedPowerVirtualizationOperatio

nsGuide

i5/OS Virtual Client Partitions and DS4000 Storage Read-me First document

– Scheduled for availability by 3/21, URL not available yet

Performance Capability Reference manual (Chapter 14)– http://publib.boulder.ibm.com/infocenter/systems/scope/i5os/index.jsp?topic=/books/s

c410607.pdf

Redbook IBM System Storage DS4000 and Storage Manager V10.10

– http://www.redbooks.ibm.com/redpieces/abstracts/sg247010.html?Open

VIOS datasheet (VIOS support only, refer to this presentation for i5/OS + VIOS support)

– http://www14.software.ibm.com/webapp/set2/sas/f/vios/documentation/datasheet.html


Recommended