|
Amen to that Glenn !
I mean I have upgrade a ton of models and I was surprised that this thing
came in that way and with NOTHING loaded software-wise. But I learned how to do that :-)
Chuck
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Glenn Ericson Sent: Thursday, November 13, 2003 2:04 PM To: Midrange Systems Technical Discussion; 'Midrange Systems Technical Discussion' Subject: RE: LPAR Question
Only if you are super lucky or drunk are they in the feature card right slots or DASD for that matter
THINK NO SOFTWARE INSTALLED NO HDWE in the proper locations and no partitions created..
this comes from your preorder planing and the rules say it should pass systems assurance for LPAR
A simple wrong or slightly incorrect assumption could cost an additional $20k - $25K to correct.
I watched one of our potential clients shift to anther BP thinking he would cut costs . He took an early planning config and changed the rules switched to a BP that did not now LPAR who made minor adjustments [ per standard configuration rules] and the thing failed very BADLY. BP thought just adding the LPAR feature code handled all his problems. How wrong he was!!! It was a long time before it was corrected and someone was contracted to install it for the BP & this client.
So Chuck you are right you have to know what you are doing up front and why.
At 12:52 PM 11/13/2003 -0500, Chuck Lewis wrote: >Andy, very good points ! > >We replaced a 620 with an 810 LPAR system several months ago. WHAT a >learning experience. Like you said, planning is SO important and if you are >only going to do it once, you can probably find better uses of your time. >Once it is up and running, understand the operational stuff, etc. We had our >BP config and order it and IBM set it up. And there were still little issues >(nothing major). But it was DEFINTITELY more involved than I had ever >imagined before I got into to it. Lot of stuff to pull together. The thing, >I naively I guess, figured was that the box(s) would come with everything in >the correct slot - WRONG :-) My "assumption" was that since the configurator >mapped this all out, Rochester would follow that too. Wrong on my part ?:-) >You definitely need knowledge early in the process and that makes it hard to >justify that time if you are only doing it once and not making a job of it. > >Chuck > > >-----Original Message----- >From: midrange-l-bounces@xxxxxxxxxxxx >[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Andy Nolen-Parkhouse >Sent: Thursday, November 13, 2003 12:18 PM >To: 'Midrange Systems Technical Discussion' >Subject: RE: LPAR Question > >Mark, > >I'm one of those who recommend expert business partners for LPAR. I used to >configure and install LPAR boxes for a business partner so I'll give it a >stab. The heavy lifting in an LPAR configuration is not in running it but >ordering the correct hardware. If you're technically competent, familiar >with work management, and study the documentation; then I don't doubt that >you'll do well. But if you've never used IBM's configuration tools and >aren't familiar with the hardware requirements for an LPAR box, then you're >better off getting an expert opinion. > >On most standard single-partition boxes, you just say how many drives of >what capacity, how many NIC's, and so on. Things can fall together fairly >well and most business partners can configure the machine appropriately. >When you get into partitions, you as a customer need to know the hardware >requirements for each partition and the person that does the configuration >needs to be able to translate that into hardware. Generally the entire >system is planned with the location of each card mapped out, which partition >each card is assigned to, and which cards are shared between partitions. > >It gets rather complicated. I've met people who ordered their own box with >the intent of implementing LPAR (they didn't tell the BP), but when push >came to shove, they didn't have a CD-ROM drive in the appropriate partition >to load the OS. So unless you want to do a lot of homework for something >you're only going to do once, you're probably better off ordering from >someone with experience or using a consultant to verify your configuration. > >Also, when you order a machine with the intent of LPAR, the factory will >install all of the hardware, but the cards and drives will need to be >rearranged to their proper locations, then you do a scratch install in each >partition. Depending on how you fell about shoving around hardware and >loading operating systems, you may want experienced help for this also. > >I'm sure that you'll be able to figure out how to run the thing Mark, the >documentation is pretty good - it's in the ordering and the installation >where additional help can be required. > >Kind Regards, >Andy Nolen-Parkhouse > > > On Behalf Of Mark Phippard > > Subject: LPAR Question > > > > I have an LPAR question for you BP's and experts on the list. I have seen > > messages about how you should work with an experienced BP to do your > > configs etc... My question is that only necessary in a "real world" > > situation or is it always necessary because LPAR is so complicated? I can > > see where if I had 2 or 3 locations running on LPAR and they all needed > > backups etc. that there would be hardware issues to consider, but that is > > not our situation. > > > > We want to replace a pure QA box with something like a Model 800 or 810, > > but we would like to LPAR that box so that we can do stuff like load beta > > releases of OS/400 on the second partition and also just so that we can do > > more testing of our products in an LPAR environment. This box doesn't > > really "matter". We would not be doing much for backups or other things, > > we just want to be able to do the LPAR. Is this something where we can > > just do it ourselves or do we really need to plan for it? > > > > We do our boxes on lease through PartnerWorld, but we can contract with a > > local BP on services if it is necessary. > > > > Thanks > > > > >_______________________________________________ >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. _______________________________________________ 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-2025 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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.