|
Normally I do NFS within the same system.
Now that I think about it I think you did mention it could be done across
systems.
I can grasp that for Upgrades and PTF's but new system installs also? From
a single lpar system to a single lpar system? How would you configure the
NFS on the target?
Oh, now I remember; the only system which requires a line description is
the "hosting" system, the from system. All the Guesting is done via SST or
DST.
Wouldn't this require an HMC though to setup all the vswitch and stuff?
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 12/19/2017 02:25 PM
Subject: RE: Migrating extant system to new hardware
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I think you want a network install.
See:
ftp://ftp.software.ibm.com/systems/support/power/i/nfs_optical_upgrade.pdf
What Larry and I do is an option 40 from the LICPGM menu to a virtual
optical device. You can make the optical disk big enough to hold the
whole
thing or normal DVD sizes, doesn't matter. Then use that as the load
source. It'll bring over your LIC PGMs exactly like they are on the P6.
Make sure to apply all of the needed PTFs before doing the option 40.
This is fast, reasonably easy and if you have a later version of the HMC
code (8.8.6 I think) you can do the network installation from the HMC GUI.
Very cool.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jack
Woehr
Sent: Tuesday, December 19, 2017 1:08 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Migrating extant system to new hardware
It's 7.1 -> 7.1
It's from a P6 to a P8.
I'd *like *to SAVSYS to a virtual tape image, make that image the primary
load source, and install the new raw partition from the virtual image.
I'm not quite sure yet as I root through the docs if that is doable,
because
it seems the docs say that the target of the SAVSYS must itself be a
primary
load source.
On Tue, Dec 19, 2017 at 11:24 AM, Rob Berendt <rob@xxxxxxxxx> wrote:
My "favorite"? Never let the hardware get so old that it can't have
the software upgraded to a release supported on the new hardware.
Then we upgrade and test a sandbox lpar.
Then upgrade other lpars (other than production, development and their
respective HA lpars).
Then we upgrade the "target" of our HA software.
And always upgrade the "source" before your next switch.
You don't want your source to be higher than your target. You don't
want to run into objects which can't be saved to the previous release.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/19/2017 01:15 PM
Subject: Migrating extant system to new hardware
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Favorite solution paths for migrating extant system to new hardware?
- Replication suites/hardware?
- Installing OS on new LPAR and restoring a SAVSYS?
- Booting/installing from SAVSYS on tape or virtual image?
??
--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you
received this communication in error, please contact the sender and
delete/destroy all copies of this communication immediately.
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all
attachments
is for the intended recipient(s) only and may contain confidential and
privileged information. If you are not the intended recipient of this
communication, any disclosure, copying further distribution or use of this
communication is prohibited. If you received this communication in error,
please contact the sender and delete/destroy all copies of this
communication immediately.
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
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.
midrange.com
