In blade what is defined as load source or is the load source more the VIOS
now. I take it the preferred way to run blad is with XIV or DS type
storage?? Also, how doe VIOS and I5 OS work in conjunction with resource
names. Seems like from what I am reading all devices are more remotely
setup and controlled instead of centrally controlled (tape, cd-dvd, disk as
examples).

On Fri, Nov 6, 2009 at 2:13 PM,
<William.Epperson@xxxxxxxxxxxxxxxxxxxxxxxx>wrote:


It is supported using Power6 processors with i6.1 as a minimum. I'm
researching this exact scenario to migrate my existing Power5 i520 to newer
hardware so that we can look at retiring our ESS. I'll either be using the
VIOS to virtualize DS4800 or XIV storage, depending on whether we get the
XIV or not. I'm also pressing to get a newer SVC because our current SVC
is way old with 4GB cache and 2Gb ports. DS4800 and XIV have to be
presented through SVC for VIOS to work with it and supply it to i. The new
SVC also has 4 internal SSD slots and can use IBM's 146GB SSD drives.
It's a mirrored configuration across SVC's. 1 SSD in each SVC, and you can
then add 3 more options as you need more. I would then present a portion
of that SSD to i and balance data across all of my storage with i6.1.1 and
use the new dynamic balancing mechanisms being release in Dec.

One thing to consider when supplying virtual devices to anything on POWER
is that storage/disk I/O isn't all that CPU intensive, but high network
traffic IS CPU intensive. Funny how that works out. One of IBM's
trainers, in a class in Denver, said "..you may need an entire POWER6 core
to
service a single gigabit port of continuous traffic if that port is fully
utilized at or near 100%." The POWER6 520 and other stand alone servers
have an integrated virtual ethernet or host ethernet access (IVE/HEA) port
that can be shared out as hardware without needing to virtualize it under
VIOS. However if you want to be able to dynamically move your partitions
to another server those network ports will need to be virtualized under
VIOS to take advantage of live migrations. As far as I know live
migrations are still being worked on for the i. Did they get that working
yet?

Bill Epperson Jr.
Systems Communications Analyst
Memorial Health System
(719) 365-8831





Lukas Beeler <lukas.beeler@xxxxxxxxxxxxxxxx>

Sent by: midrange-l-bounces@xxxxxxxxxxxx
To

Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>

cc
11/06/2009 11:56 AM

Subject
Re: New
Blade Server and LPAR ?
Please respond to
Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>






On Fri, Nov 6, 2009 at 19:52, Vern Hamberg <vhamberg@xxxxxxxxxxx> wrote:
I know for sure that IVM is not on the i - it is in the bladecenter only.

VIOS can run natively on all Power machines, but i'm not sure if
running an IBM i partition under VIOS on a Power 520 would be a
supported scenario.

--
Read my blog at http://projectdream.org
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.