×
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.
I just uncovered that I can't upgrade my HMC from Version 7.7.8 to
Version 8.8.1 because it does not allow my HMC to manage my Power5
server (which has two partitions)
It looks like I could upgrade the HMC from Version 7.7.8 to 7.7.9 but I
wonder if it's prudent. I don't know if the upgrade will gain me
anything but headaches as I must do it remotely and the instructions
warn it will mess up remote access.
So, I have my HMC now frozen in time, and my Power5 is also frozen at
v5r4 and v5r3, but I do have a Power7 also managed by the HMC. It's
currently at v7r1 TR7.
My plan was to upgrade my v7r1 partition to the latest TR (which I
believe is TR12? Anybody?) and then create a new partition on the
Power7 to install v7r3.
I have to maintain OS versions to support clients and I'm thinking this
is the best way to do it and still get the latest version of OS to test
our stuff on (and learn new stuff).
But now I'm wondering what the HMC version limitations will have on my
OS upgrade plans.
Is there ever a requirement that the HMC be at a certain version to
manage a server at a certain OS level?
That is, can my frozen in time HMC still manage my Power7?
For instance, can the HMC create the new partition I was planning? Can
the HMC be used to update the firmware on my Power7? (My HMC is set to
do the server firmware update from the HMC).
Would I have to change that HMC server update setting (and must that
setting be the same for all servers the HMC manages?)
Insight or suggestions would be welcome.
Best Regards,
Thomas Garvey
On 6/6/2016 7:00 PM, Rob Berendt wrote:
Make sure that your firmware doesn't get out of support also.
Once we were WAY behind on HMC. We had to upgrade HMC, upgrade firmware,
upgrade HMC, upgrade firmware, repeat until current.
>From that same link:
HMC and Server Firmware Upgrade Paths
The design goal is that a HMC can, at a minimum, connect to and
perform a server firmware upgrade on any supported server that has a
server firmware level that matches or is an earlier level then the HMC. In
general, upgrade the HMC first, then upgrade the server firmware to a
supported level soon after the HMC upgrade. Always check the HMC and
server firmware release notes (readmes) for the release specific
exceptions or special instructions.
***Click here*** for a complete list of supported combinations of HMC V7
and V8 code levels and server firmware levels.
Rob Berendt
midrange.com
