|
Besides LPAR, you need an HMC for *ANY system that is CUoD. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Glenn Ericson <Glenn-Ericson@at t.net> To Sent by: Midrange Systems Technical midrange-l-bounce Discussion s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>, "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx> 05/18/2004 12:39 cc PM Subject RE: I5 vs. 810 Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> If there is NO LPAR then you do not need the HMC. At 10:25 AM 5/18/2004 -0500, Ingvaldson, Scott wrote: >The i5 HMC is an ethernet attached (private network) laptop running >Linux/"subset of AIX" depending on who you talk to. The biggest drawback I >saw was that (unlike using Ops Nav) you can configure an LPAR that cannot be >IPLed using the HMC. > >If you are not using LPAR the 810 should be good enough, though it will >likely have a somewhat shorter service life. I know that 810 memory prices >have also been cut but not sure how they compare to i5 memory. > >In short, an 810 will not have the learning curve that an i5 will have. If >you don't have a business requirement for the i5 features and you don't have >the time for testing the 810 should work fine. > >BTW, if all you want to do is set up guest Linux LPARs an 810 will handle >that just fine. > >Regards, > >Scott Ingvaldson >iSeries System Administrator >GuideOne Insurance Group > >-----Original Message----- >date: Tue, 18 May 2004 10:20:07 -0400 (EDT) >from: Don <dr2@xxxxxxxxxxxx> >subject: Re: I5 vs. 810 > >On Tue, 18 May 2004 Jan.Rockstedt@xxxxxxxxxxxx wrote: > > > i5 = no primary partition with LPAR > >Jan, I'm hearing you need an attached PC to config it...I'll be getting >more details next week... > >Don in DC > >This message and accompanying documents are covered by the Electronic >Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information >intended for the specified individual(s) only. This information is >confidential. If you are not the intended recipient or an agent responsible >for delivering it to the intended recipient, you are hereby notified that >you have received this document in error and that any review, dissemination, >copying, or the taking of any action based on the contents of this >information is strictly prohibited. If you have received this communication >in error, please notify us immediately by e-mail, and delete the original >message. > >_______________________________________________ >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 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.