Power6 Virtual Io

Advanced Virtual I/O Server Configurations

César Diniz MacielConsulting IT Specialist – IBM US

Agenda

Virtual Optical Devices, Virtual Optical Media, File-backed Devices Shared Ethernet Adapter (SEA) Failover SEA over Host Ethernet Adapter (HEA) Live Partition Mobility configuration Virtual Tape N-Port ID Virtualization (NPIV) Heterogeneous Multipathing Active Memory Sharing

Progression of Virtual Storage Devices on VIOS

The ability to share virtual SCSI disks backed by a Physical Volume (PV) or a Logical Volume (LV) has been available from the beginning.

VIO server 1.2 gave the ability to share the CDROM drive with client LPARs through Virtual Optical devices.

With VIO server 1.5, the ability to create “file-backed” virtual devices in addition to virtual SCSI devices backed by a PV or LV

Using the cpvdi command a virtual device image can now be copied from one virtual target device (VTD) to a different VTD. This feature was added under VIO 1.5.2.1-FP11.1.

Power Systems Virtual Optical Device padmin user commands in VIO server

$ lsdev -type opticalname status descriptioncd0 Available SATA DVD-ROM Drive

$ mkvdev –vdev cd0 –vadapter vhost3vtopt0 available

$ lsmap -vadapter vhost0SVSA Physloc Client Partition ID--------------- ------------------------------------------- ----------vhost0 U9111.520.10C1C1C-V1-C13 0x00000000

VTD vtopt0LUN 0x8100000000000000Backing device cd0Physloc U787A.001.DNZ00ZE-P4-D3

Power Systems Virtual Optical Device

Backing device(disk, lv, file or media)

Client connection - Option One

On old client# lsdev –Cl cd0 –F parentvscsi2# rmdev –R vscsi2

On new client# cfgmgr

Client Side - Virtual Optical Device First AIX client LPAR to activate will show new vscsi adapter and cd0 available

# lsdev -Cs vscsicd0 Available Virtual SCSI Optical Served by VIO Serverhdisk0 Available Virtual SCSI Disk Drive

# lsdev -Cs vscsi -F "name physloc“cd0 U9111.520.10C1C1C-V3-C2-T1-L810000000000hdisk0 U9111.520.10C1C1C-V3-C31-T1-L810000000000

# lsdev -Cc adapterent0 Available Virtual I/O Ethernet Adapter (l-lan)vsa0 Available LPAR Virtual Serial Adaptervscsi0 Available Virtual SCSI Client Adaptervscsi1 Available Virtual SCSI Client Adaptervscsi2 Available Virtual SCSI Client Adapter

Subsequent AIX client LPARs activate, but only show vscsi adapter Defined, and no optical device

# lsdev -Cc adapterent0 Available Virtual I/O Ethernet Adapter (l-lan)vsa0 Available LPAR Virtual Serial Adaptervscsi0 Available Virtual SCSI Client Adaptervscsi1 Available Virtual SCSI Client Adaptervscsi2 Defined Virtual SCSI Client Adapter

This client’s adapter will NOT configure while another client is connected to the server adapter

# cfgmgr -vl vscsi2…Method error (/usr/lib/methods/cfg_vclient -l vscsi2 ): 0514-040 Error initializing a device into the kernel.

Client Side - Virtual Optical Device

To release the optical device from owning LPAR

# lsdev –Cl cd0 –F parentvscsi2

# rmdev –R vscsi2cd0 defined

Now, cfgmgr in the receiving LPAR

Client Side - Virtual Optical Device

Client connection - Option Two

Move from the VIO server$ rmdev –dev vtopt0$ mkvdev –vdev cd0 \–vadapter vhost#(where vhost# isthe VSCSI adapterfor the clientPartition)

Virtual Optical Media

File-backed device that works like an optical device (think of it as an ISO image).

With read-only virtual media the same virtual optical device can be presented to multiple client partitions simultaneously

You could easily boot from and install partitions remotely without having the need to swap out physical CD/DVDs or setup Network Installation Manager (NIM) server. It is also easier to boot a partition into maintenance mode to repair problems

Easier to maintain a complete library of all the software needed for the managed system. Various software packages as well as all the necessary software levels to support each partition

Client partitions could use blank file-backed virtual optical media for backup purposes (read/write devices)

These file-backed optical devices could then be backed up from on the VIO server to other types of media (tape, physical CD/DVD, TSM server, etc.)

Virtual Optical Media

Create an ISO file from CDROM$ mkvopt -name dvd.AIX_6.1.iso -dev cd0 -ro

You choose the name for this file, so make it meaningful Creates an ISO image from the media in /dev/cd0

After the .iso file is in your /var/vio/VMLibrary directory, run: $ mkvdev -fbo -vadapter vhost# vtopt0 Available

Replace vhost# with your Virtual SCSI server adapter name. This mkvdev command creates your virtual optical target device.

$ loadopt -vtd vtopt0 –disk dvd.AIX_6.1.iso The loadopt command loads vtopt0 with your ISO image Replace “dvd.AIX_6.1.iso” with your meaningful filename

Converting between backing devices - cpvdi

New command added at VIO 1.5.2.1-FP-11.1$ cpvdi -src input_disk_image -dst output_disk_image [-isp input_storage_pool] [-osp output_storage_pool] [-overwrite] [-unconfigure] [-f] [-progress]

The cpvdi command copies a block device image, which can be either a logical or physical volume, a file-backed device, or a file on another existing disk.

This command is NOT used to move data between non-virtualized disks and virtualized disks.

Starting from scratch on the VIO server

$ mksp lv-storage-pool hdisk4lv-storage-pool0516-1254 mkvg: Changing the PVID in the ODM.$ lspvNAME PVID VG STATUShdisk0 00c23c9f9e9e1909 rootvg activehdisk1 00c23c9fa415621f clientvg activehdisk2 00c23c9f2fbda0b4 clientvg activehdisk3 00c23c9ffbf3c991 Nonehdisk4 00c23c9f20c41ad6 lv-storage-pool active$ mksp -fb file-storage-pl -sp lv-storage-pool -size 1Gfile-storage-plFile system created successfully.1040148 kilobytes total disk space.New File System size is 2097152$ lsspPool Size(mb) Free(mb) Alloc Size(mb) BDs Typerootvg 69888 49408 128 0 LVPOOLclientvg 139776 102912 64 3 LVPOOLlv-storage-pool 69888 67840 64 1 LVPOOLfile-storage-pl 1016 1015 64 0 FBPOOL$ dfFilesystem 512-blocks Free %Used Iused %Iused Mounted on/dev/hd4 524288 455864 14% 2293 5% //dev/hd2 5242880 936112 83% 51854 32% /usr/dev/hd9var 1310720 1181296 10% 474 1% /var/dev/hd3 4718592 4558112 4% 384 1% /tmp/dev/hd1 20971520 9927544 53% 1374 1% /home/proc - - - - - /proc/dev/hd10opt 3407872 2538704 26% 10562 4% /opt/dev/file-storage-pl 2097152 2079792 1% 4 1% /var/vio/storagepools/file-storage-pl

Creating a new Virtual Media Repository

$ mkrep -sp lv-storage-pool -size 500MVirtual Media Repository CreatedRepository created within "VMLibrary_LV" logical volume$ lsspPool Size(mb) Free(mb) Alloc Size(mb) BDs Typerootvg 69888 49408 128 0 LVPOOLclientvg 139776 102912 64 3 LVPOOLlv-storage-pool 69888 67328 64 1 LVPOOLfile-storage-pl 1016 1005 64 1 FBPOOLVMLibrary_LV 508 507 64 0 FBPOOL$ lsvoptVTD Media Size(mb)vtopt0 No Media n/a$ lsmap –vadapter vhost0SVSA Physloc Client Partition ID--------------- -------------------------------------------- ------------------vhost0 U9117.MMA.1023C9F-V2-C11 0x00000004

VTD vt_ec04Status AvailableLUN 0x8100000000000000Backing device client2lvPhysloc

VTD vtopt0Status AvailableLUN 0x8200000000000000Backing devicePhysloc$ mkvopt -name vio-1-5-expansion.iso -file /var/vio/storagepools/file-storage-pl/vio-1-5-expansion.iso -ro

Seeing the image on the client LPAR

$ lsmap -all | moreSVSA Physloc Client Partition ID--------------- -------------------------------------------- ------------------vhost0 U9117.MMA.1023C9F-V2-C11 0x00000004

VTD vt_ec04Status AvailableLUN 0x8100000000000000Backing device client2lvPhysloc

VTD vtopt0Status AvailableLUN 0x8200000000000000Backing device /var/vio/VMLibrary/vio-1-5-expansion.isoPhyslocFrom the client LPAR:root@ec04 / # cfgmgrroot@ec04 / # lsdev -Cc cdromcd0 Available Virtual SCSI Optical Served by VIO Serverroot@ec04 / # mount -v cdrfs -o ro /dev/cd0 /cdromroot@ec04 / # dfFilesystem 512-blocks Free %Used Iused %Iused Mounted on/dev/hd4 98304 49488 50% 1982 9% //dev/hd2 2490368 88936 97% 23302 8% /usr/dev/hd9var 65536 31584 52% 494 7% /var/dev/hd3 229376 126928 45% 64 1% /tmp/dev/hd1 65536 63368 4% 20 1% /home/proc - - - - - /proc/dev/hd10opt 229376 35272 85% 2937 11% /opt/dev/cd0 19724 0 100% 4931 100% /cdrom

Agenda


Shared Ethernet Adapter

Physical access shared by multiple networks

Physical access can be a single adapter or an aggregate of adapters (EtherChannel/Link Aggregation)

Shared Ethernet operates at layer 2 Virtual Ethernet MAC visible to outside systems Broadcast/Multicast support

Create the Shared Ethernet Adapter (SEA)

Create the Shared Ethernet Adapter (SEA)$ mkvdev -sea ent3 -vadapter ent2 -default ent2 -defaultid 1ent4 Availableen4et4

Untagged (PVID 1)VID 100

Client 1 Client 2VIOS 1

PVID1

ent0(Vir)

en0(if)

ent1(Vir)

en1(if)

PVID100

ent0(Vir)

en0(if)

ent1(Vir)

en1(if)

PVID1

VID100

ent0(Phy)

ent4(SEA)

ent2(Vir)

en4(if)

ent1(Phy)

ent3(LA)

PVID1

PVID100

SharedEthernetAdapter

Shared Ethernet Adapter Failover

VIOS feature (indepentent of the client partition)

Provides a backup adapter for the SEA, with active monitoring. Virtual Ethernet Control Channel between the two VIOS.

No load balancing; only the primary SEA is active. Traffic flows through secondary SEA only when primary SEA fails.

No configuration required on the client partition; everything is done on the two VIOS.

Can be used with Etherchannel/802.3ad devices.

Configured with the mkvdev command on both VIOS.

VIOS 1

EnetPCI

VIOS 2

EnetPCI

Primary

Client

Backup

VirtEnet

SEA SEA

POWER5 Server

VIOS 1

EnetPCI

VIOS 2

EnetPCI

Shared Ethernet Adapter Failover, Dual VIOS

Complexity Specialized setup confined to VIOS

Resilience Protection against single VIOS / switch port /

switch / Ethernet adapter failure Throughput / Scalability

Cannot do load-sharing between primary and backup SEA (backup SEA is idle until needed).

SEA failure initiated by: Backup SEA detects the active SEA has failed. Active SEA detects a loss of the physical link Manual failover by putting SEA in standby mode Active SEA cannot ping a given IP address.

Notes Requires VIOS V1.2 and SF235 platform firmware Can be used on any type of client (AIX, Linux, I (on

POWER6) Outside traffic may be tagged

Primary

Client

Backup

VirtEnet

SEA SEA

Control Channel

Tips and considerations when using SEA and SEA Failover SEA

Make sure there is no IP configured on either the physical Ethernet interface or the virtual interface that will be part of the SEA prior to performing the SEA configuration.

You can optionally configure an IP address on the new SEA interface after the configuration is done.

SEA failover If you have multiple SEAs configured on each of the VIO servers, then for

each SEA pair, you need to configure a separate control channel with a unique PVID on the system.

Make sure you configure the SEA failover adapter (on the second VIOS) at the same time you configure the primary adapter.

Agenda


24

Virtualization: HEA Logical Port Concept

Logical L2 switch

Physical Port

Logical Ports

Partition PartitionPartition

HEA

To a LPAR, a HEA logical port appears as a generic Ethernet interface With its own resources and MAC

address Sharing bandwidth w/ other logical ports

defined on same physical port

Logical ports are allocated to partitions Each Logical Port can be owned by a

separate LPAR A Partition can own multiple Logical

Ports Only one Logical Port per Physical Port

per partition

One Logical Layer 2 switch per Physical port

25

Virtualization: SEA and HEA

I/O HostingPartition

PHYP

Linux iOS AIX

Virtual Ethernet Switch

Packet Forwarder

Virtual Ethernet

Driver

Virtual Ethernet

Driver

Virtual Ethernet

Driver

Virtual Ethernet and SEA

...considerationsƒ Adapter sharing with Native Performanceƒ Removes SW forwarding overheadƒ LPAR mobility

PHYP

Linux iOS AIX

Ethernet

Driver

Ethernet

Driver

Ethernet

Driver

HEA

HEA

Ethernet adapterNetwor

k

10 Gbps are likely to be shared by multiple partitions....Remove SW Forwarder bottleneck

26

When might you use SEA over IVE

When the number of Ethernet adapters needed on a single partition is more than the number of physical ports available on the HEA(s)

If the number of LPARs sharing a physical port exceeds the number of LHEA ports available

Depends on the type of daughter card and the MCS value

If you anticipate a future need for more adapters than you have LHEA ports (LP-HEA) available

Very small amount of memory on LPAR Each LP-HEA needs around 102 MB system memory

Some situations you might consider using a combination of SEA, IVE, and/or dedicated Ethernet adapters

27

Considerations when using HEA on VIO When the VIO server uses the HEA as a SEA you must set the VIO server

as a promiscuous LPAR for that LHEA

When in promiscuous mode there is only one LP-HEA per physical port

The promiscuous LPAR receives all unicast, multicast, and broadcast network traffic from the physical network.

Always use flow control, and the large_send parameter for all Gigabit and 10 Gbit Ethernet adapters, and large_receive parameter when using a 10Gbit Ethernet adapter (VIOS 1.5.1.1) to increase performance

28

Promiscuous Mode

Agenda


Live Partition Mobility concepts

Mover service partitions (MSP) Mover service partitions (MSP) is an attribute of the Virtual I/O Server

partition. It enables the specified Virtual I/O Server partition to allow the functionality that asynchronously extracts, transports, and installs partition state. Two mover service partitions are involved in an active partition migration: one on the source system, the other on the destination system. Mover service partitions are not used for inactive migrations.

Virtual asynchronous services interface (VASI) The source and destination mover service partitions use this virtual

device to communicate with the POWER hypervisor to gain access to partition state. The VASI device is included on the Virtual I/O Server, but is only used when the server is declared as a mover service partition.

Partition Migration moves Active and Inactive LPAR

Inactive Partition Migration Inactive Partition Migration transfers a partition that is logically

‘powered off’ (not running) from one system to another. Subject to fewer compatibility restrictions than active partition

migration because the OS goes through the boot process on the destination.

Provides some ease of migration from systems prior to those enabled for active migration.

Active Partition Migration Active Partition Migration is the actual movement of a running LPAR

from one physical machine to another without disrupting* the operation of the OS and applications running in that LPAR.

Applicability Workload consolidation (e.g. many to one) Workload balancing (e.g. move to larger system) Workload migration to newer systems Planned CEC outages for maintenance/upgrades Impending CEC outages (e.g. hardware warning received)

Supported by all POWER6-based servers

Requisites

The mobile partition’s network and disk access must be virtualized using one or more Virtual I/O Servers. The Virtual I/O Servers on both systems must have a shared Ethernet

adapter configured to bridge to the same Ethernet network used by the mobile partition

The Virtual I/O Servers on both systems must be capable of providing virtual access to all disk resources the mobile partition is using.

The disks used by the mobile partition must be accessed through virtual SCSI and/or virtual Fibre Channel-based mapping

Normal Running Pre-Migration(Disk I/O Shown)

Source Partition

Ded. Adapt DD

VSCSI Client DD

VIOS(VSCSI, VLAN, MSP)

VSCSI Server

Ded Adapt

DD


VSCSI Server

Ded Adapt

DD

PHYPPHYPDed

Adapter

PHYPPHYPDed

AdapterDed

Adapter

SAN

Disks

Ded Adapter

LAN

Create Target Partition

Source Partition

VSCSI Client DD


VSCI Server

Ded Adapt

DD


VSCI Server

Ded Adapt

DD

PHYPPHYPDed

Adapter

PHYPPHYPDed

AdapterDed

Adapter

SAN

Ded Adapter

Target Partition

Disks

LAN

Source Partition

Transfer Partition State

VSCSI Client DD


VSCI Server

Ded Adapt

DD


VSCI Server

Ded Adapt

DD

PHYPPHYPDed

Adapter

PHYPPHYPDed

AdapterDed

Adapter

SAN

Ded Adapter

Target Partition

Disks

Target PartitionTarget PartitionSource PartitionSource Partition

VSCSI Client DD

LAN

Source Partition

Transfer VIO to Target

VSCSI Client DD


VSCI Server

Ded Adapt

DD


VSCI Server

Ded Adapt

DD

PHYPPHYPDed

Adapter

PHYPPHYPDed

AdapterDed

Adapter

SAN

Ded Adapter

Target Partition

Disks


VSCSI Client DD

LAN

Source Partition

Re-Attach Dedicated Adapters(via DLPAR)

VSCSI Client DD


VSCI Server

Ded Adapt

DD


VSCI Server

Ded Adapt

DD

PHYPPHYPDed

Adapter

PHYPPHYPDed

AdapterDed

Adapter

SAN

Ded Adapter

Target Partition

Disks


VSCSI Client DD

Ded. Adapt DD

LAN

Clean Up Unused Resources

VSCSI Client DD


VSCI Server

Ded Adapt

DD


VSCI Server

Ded Adapt

DD

PHYPPHYPDed

Adapter

PHYPPHYPDed

AdapterDed

Adapter

SAN

Ded Adapter

Disks

Target PartitionSource Partition

VSCSI Client DD

Ded. Adapt DD

LAN

Devices not supported for LPM

IVE Virtual Optical Device Virtual Optical Media OS installed on internal disks OS installed on logical volumes or file-backed devices Virtual Tape

Agenda


VIOS Virtual Tape Support

Enables client partitions to directly access selected SAS tape devices, sharing resources and simplifying backup & restore operations SAS adapter is owned by VIOS partition Included with PowerVM Express, Standard, or Enterprise Edition Supports AIX 5.3 & 6.1 partitions and IBM i 6.1 partitions POWER6 processor-based systems

Power Hypervisor

VIOS

Virtual SCSI AdapterSAS Adapter Virtual SCSI Adapter

Tape drives supported• DAT72: Feature Code 5907• DAT160: Feature Code 5619• HH LTO4: Feature Code 5746

VIOS Virtual Tape Support

Virtual tape device created and managed the same way as a virtual disk mkvdev -vdev TargetDevice –vadapter VirtualSCSIServerAdapter

lsdev -virtual returns results similar to the following:name status description

vhost3 Available Virtual SCSI Server Adapter

vsa0 Available LPAR Virtual Serial Adapter

vtscsi0 Available Virtual Target Device - Logical Volume

vttape0 Available Virtual Target Device - Tape On the client partition, simply run cfgmgr to configure the virtual tape Device can be used as a regular tape, for data and OS backup and restore, including

booting from media. Automated tape libraries are not supported.

Agenda


NPIV

N_Port ID Virtualization (NPIV) provides direct Fibre Channel connections from client partitions to SAN resources , simplifying SAN management Fibre Channel Host Bus Adapter is owned by VIOS partition Supported with PowerVM Express, Standard, and Enterprise Edition Supports AIX 5.3 and AIX 6.1 partitions Power 520, 550, 560, and 570, with an 8 GB PCIe Fibre Channel Adapter

Statement of Direction IBM intends to support N_Port ID Virtualization (NPIV) on the POWER6

processor-based Power 595, BladeCenter JS12, and BladeCenter JS22 in 2009.

IBM intends to support NPIV with IBM i and Linux environments in 2009.

Power Hypervisor

VIOS

Virtual FC AdapterFC Adapter Virtual FC Adapter

Enables use of existing storage management tools Simplifies storage provisioning (i.e. zoning, LUN masking)Enables access to SAN devices including tape libraries

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

NPIV details

�VIOS V2.1 (PowerVM Express, Standard, and Enterprise) �Client OS support: AIX(5.3, 6.1); later in 2009, Linux and IBM i �POWER6 only; Blade and High-End support in 2009 �8 Gigabit PCI Express Dual Port Fibre Channel Adapter �Compatible with Live Partition Mobility (LPM) �VIO servers can support NPIV and vSCSI simultaneously �Clients can support NPIV, vSCSI and dedicated Fibre Channel

simultaneously �HMC-managed and IVM-managed servers �Unique Worldwide Port Name (WWPN) generation (allocated

in pairs)

DS8000 EMC

VIOS

Virtual SCSI

FC Adapters

SAN

generic scsi disk

generic scsi disk

Current Virtual SCSI model

Virt

ualiz

eddi

sks

FC

Ada

pter

EMCDS8000

VIOS

Virtual FC

FC Adapters

SAN

EMCDS8000

N-Port ID Virtualization

Shar

edFC

Ada

pter

POWER6POWER5 or POWER6

NPIV Simplifies SAN Management

AIX AIX

Dis

ks

Partition SAN access through NPIV

SAN Switch requirements

Only the first SAN switch attached to the Fibre Channel adapter needs to be NPIV capable

• Other switches in the environment do not need to be NPIV capable

• Not all ports on the switch need to be configured for NPIV, just the one which the adapter will use

�Check with your storage vendor to make sure the switch is NPIV capable

� Order and install the latest available firmware for your SAN switch

Create a Virtual Fibre Channel Adapter

Client/server relationship similar to Virtual SCSI VSCSI Server on the VIOS, client on the client partition VFC Server on the VIOS, VFC client on the client partition

Mapping the adapter

vfcmap – binding the VFC Server to the Fibre Channel Port vfcmap -help

Usage: vfcmap -vadapter VFCServerAdapter -fcp FCPName

Maps the Virtual Fibre Channel Adapter to the physical Fibre Channel Port -vadapter Specifies the virtual server adapter. -fcp Specifies the physical Fibre Channel Port Example: vfcmap –vadapter vfchost0 –f

After mapping done, running cfgmgr on the client partitions to configure SAN devices Before this step, zoning (if used) must be done on the switches. Virtual

adapter WWPN can be obtained on the HMC.

WWPN for the Virtual Adapter

Agenda


Dynamic Heterogeneous Multi-Path I/O Delivers flexibility for Live Partition Mobility environments Provides efficient path redundancy to SAN resources

Supported between virtual NPIV and physical Fibre Channel Adapters

AIX 5.3 and 6.1 partitions POWER6 processor-based servers

Power Hypervisor

VIOS

FC AdapterVirtual FC AdapterFC Adapter

Power Hypervisor

VIOS

FC AdapterVirtual FC AdapterFC Adapter

1) Real adapter

2) Virtual adapter to prepare for mobility

3) Partition moves via virtual adapter 4) Real adapter

NPIV NPIV

Agenda


PowerVM Active Memory™ Sharing

Active Memory Sharing will intelligently flow memory from one partition to another for increased utilization and flexibility of memory usage.

Memory virtualization enhancement for Power Systems Memory dynamically allocated based on partition’s workload demands Contents of memory written to a paging device Improves memory utilization

Extends Power Systems Virtualization Leadership Capabilities not provided by Sun and HP virtualization offerings

Designed for partitions with variable memory requirements Low average memory requirements Active/inactive environments Workloads that peak at different times across the partitions

Available with PowerVM Enterprise Edition AIX 6.1, Linux and i 6.1 partitions that use VIOS and shared processors POWER6 processor-based systems

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

Active Memory Sharing Enables Higher Memory Utilization

Partitions with dedicated memory Memory is allocated to partitions As workload demands change,

memory remains dedicated Memory allocation is not optimized

to workload

0

5

10

15

20

25

Partition 3Partition 2Partition 1

0

5

10

15

20

25

Partition 3Partition 2Partition 1

Time

Time

Mem

ory

(GB)

Mem

ory

Usa

ge (G

B)

Partitions with shared memory Memory is allocated to shared pool Memory is used by partition that

needs it enabling more throughput Higher memory utilization

Memory requirementsMemory allocation

Active Memory Sharing Examples

Around the World Partitions support workloads with

memory demands that peak at different times

0

5

10

15

NightDay

0

5

10

15

AsiaAmericasEurope

Time

Time

Mem

ory

Usa

ge (G

B)M

emor

y U

sage

(GB)

Day and Night Partitions support day time web

applications and night time batch

Infrequent use Large number of partitions with

sporadic use

0

5

10

15#10 #9 #8 #7 #6 #5 #4 #3 #2 #1

Time

Mem

ory

Usa

ge (G

B)

When not to use AMS

High Performance Computing (HPC) applications that has high and constant memory usage Crash analysis, CFD, etc

Databases that have fixed buffer cache allocation Generally use all the available memory on the partition, and buffer cache

paging is undesirable Realtime, fixed response-time type of applications

Predictability is key, so resources should not be shared

59

References

Using File-Backed Virtual SCSI Devices, by Janel Barfield http://www.ibmsystemsmag.com/aix/februarymarch09/tipstechniques/24273p1.aspx

Configuring Shared Ethernet Adapter Failover http://techsupport.services.ibm.com/server/vios/documentation/SEA_final.pdf

Integrated Virtual Ethernet Adapter Technical Overview and Introduction http://www.redbooks.ibm.com/abstracts/redp4340.html

IBM PowerVM Live Partition Mobility http://www.redbooks.ibm.com/abstracts/sg247460.html

Power Systems Virtual I/O Server http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/iphb1/iphb1.pdf

http://www.ibmsystemsmag.com/aix/februarymarch09/tipstechniques/24273p1.aspx

http://www.redbooks.ibm.com/abstracts/redp4340.html

http://www.redbooks.ibm.com/abstracts/sg247460.html

forotecnicoargentina.com/facebook

Gracias

César Diniz [email protected]

Power6 Virtual Io

Documents

Transcript of Power6 Virtual Io