|
In order to get IBM to follow the system plan they are furnished, the
order has to have the correct feature codes on it. Since very few
partners even know they can do that it is doubtful that feature code was
on the order. Furthermore the system has to be a brand new system, not
an MES upgrade (even if the hardware is completely replaced), so I'm not
surprised the hardware layout was not to your specifications.
Since the LPAR configuration is really stored on the FSP, your best bet
is to export the system plan and then import it, but 6 LPARs does not
seem like that many to create manually. Two hours should do it and I'll
be faster in the long run by the time you get done setting up all the
virtualization anyway.
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
On 4/20/12 1:16 PM, Kirk Goins wrote:
*This message was transferred with a trial version of CommuniGate(r) Pro*pretty
Normally I work on systems with just a few ( 2 or 3 ) LPARs and it's
fast just to create the LPARs by hand. I know I could upload a sysplanbut
have never had the time to play with that.is
So we just put together a 6 LPAR box ( 1 IBM i Host and 5 IBM i Guests ).
Now I get to do its twin next week. Assuming IBM didn't follow the SPT on
the 2nd system like they didn't on the first... I was wondering if there
a way save the LPAR config data and restore it to the 2nd HMC and thenjsut
make some tweaks? Can I export the say a SYSPLAN from the HMC and import--
it into SPT?
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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.