Re: HMC code update from the grave

ohhh, i knew i was asking for a reason.
n°1 is the culprit that i have to install v6r1.2 before v7, v7 doesnt
like any fw below 240_382 or so, and v5 doesnt like anything higher
than it already has, so i have to use v6r1 to update the fw and only
then can i go to v7r3.5M4

I'll pencil n° 2 in big red letters in my procedure. It should be the
default password (i have yet to see a client that changes the hmc/asmi
password, many dont even change the DST ones).
In any case, i may end up re-partitioning the machine, since they have
2 partitions but in the time i've been in charge of maintenance, they
havent even started the second one.

Best regards and thanks!

On Wed, Feb 8, 2012 at 10:34 PM, DrFranken <midrange@xxxxxxxxxxxx> wrote:

Two things to keep in mind:

1) Watch for the relationship between the firmware and HMC. That is,
don't update the HMC too far all at once so that you loose connection to
the FSP.

-and more importantly-

2) Make sure you have the HMC access password. If you completely reload
the HMC then it will 're-introduce itself' to the FSP and the FSP will
require that password.  (Yes you can reset the FSP with the magical
switches but then it kinda forgets everything it knows.)

    - Larry "DrFranken Bolhuis"

On 2/8/2012 8:02 PM, Chris Bipes wrote:

I had to make the same upgrade a while back.  I hired an expert to do it.  He ended up wiping the HMC and discarding the backup data.  He reloaded the one server with one partition back from the service processor with no loss of production data.  Your plan sounds valid and about what we did over a fuzzy and busy year ago.

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