× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yea, some bad things can happen if you have two HMCs at different levels,
(not that I've ever tried it......... but only once)

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Tuesday, December 30, 2014 3:11 PM
To: Midrange Systems Technical Discussion
Subject: Re: Replacing an HMC Question

Agree with Jim.

Bonus is if you have only one HMC then you avoid the issue of the HMCs not
being at the same level. Once you connect a newer (software level) HMC you
never want to touch that machine with an older one again.

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 12/29/2014 4:53 PM, Jim Oberholtzer wrote:

Rob's correct. Remember the FSP keeps a copy of the partition
information so just connecting to the system will bring that in.

If you have more than a dozen user profiles to recreate, then you
could save the upgrade data to a USB. Then on the new HMC you'll have
to issue the Restore Upgrade Data command (from the command line) then
reboot. It will pull in all the users, networking info etc. If you
want both HMCs to run, then after the backup of the upgrade data, change
the IP address of the old
HMC before starting the new one. If you plug them into HMC1 and HMC2 on
the back of the system unit, then you'll have to know those addresses
as well.

Less than a dozen user profiles? Just recreate them, it's way faster
than the restore upgrade data route.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Monday, December 29, 2014 3:26 PM
To: Midrange Systems Technical Discussion
Subject: Re: Replacing an HMC Question

When I got my replacement HMC's all I did was tell it to go find the
existing Power machines and add them in. That's kind of high level
but I think you get the gist of it. Granted, I did go in and reset up
the service, networking, etc. But since I wanted to run them both to
verify that they both worked it wasn't a bad idea anyway, and give
them different IP addresses.


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: Kirk Goins <kirkgoins@xxxxxxxxx>
To: Midrange-L <midrange-l@xxxxxxxxxxxx>
Date: 12/29/2014 04:13 PM
Subject: Replacing an HMC Question
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



So my new HMC has arrived ( still waiting on my Power8 ) and am
planning my migration. So Current HMC is running 7.7.5, the new will
have 8.1.
Assuming
things like Firmware is correct on all the attached Managed Systems,
can I do something along the lines of Backup Critical Console Data to
a USB Shutdown the HMC and replace with the new one in the rack?
Boot the new and Restore the Console Dataand be pretty much ready to go?

Do I need to run the Startup/Setup Wizard or will those things be in
the console data?

Asking here as IBM says they have no record of my M/T Serial number. I
guess it is stuck in Customs.

Thanks in advance.

--
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 ...

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.