While trying to upgrade the HMC from version 5.2.1 to version 6.0.1
the HMC completely appears to have bit the dust. I completed the
upgrade steps from IBM but when I rebooted the HMC it comes up with an
error stating that the install is not complete and the HMC cannot be
used until it has been rebooted, then it states that the HMC will be
rebooted and the cycle continues.

Does anyone know if I just recover from the 5.2.1 CDs that came with
it, if all my existing LPAR configurations will be pulled? I know
user information and extra profiles will be gone, but I just wanted to
confirm that it will not affect currently running systems.

Any help is appreciated.

bscottberg wrote:
> While trying to upgrade the HMC from version 5.2.1 to version 6.0.1
> the HMC completely appears to have bit the dust. I completed the
> upgrade steps from IBM but when I rebooted the HMC it comes up with an
> error stating that the install is not complete and the HMC cannot be
> used until it has been rebooted, then it states that the HMC will be
> rebooted and the cycle continues.
>
> Does anyone know if I just recover from the 5.2.1 CDs that came with
> it, if all my existing LPAR configurations will be pulled? I know
> user information and extra profiles will be gone, but I just wanted to
> confirm that it will not affect currently running systems.
>
> Any help is appreciated.
>
Whatever you do, do not power any of the systems on that HMC off! Just
thought I should throw that in there.

If you install the original cd, it will pull all of the LPAR information
from the running system. It is really nice to have 2 HMC's for this
type of scenario, but as long as you don't power anything off, you
should be fine once you get the HMC back up. I had to do this once to
an HMC that was attached to a p690, and the HMC was down for a week.
Not the best practice, but you have to do what you have to do. After I
installed the right code on the HMC, it queried the hardware and pulled
back all of the LPAR info.

bscottberg wrote:
> While trying to upgrade the HMC from version 5.2.1 to version 6.0.1
> the HMC completely appears to have bit the dust. I completed the
> upgrade steps from IBM but when I rebooted the HMC it comes up with an
> error stating that the install is not complete and the HMC cannot be
> used until it has been rebooted, then it states that the HMC will be
> rebooted and the cycle continues.
>
> Does anyone know if I just recover from the 5.2.1 CDs that came with
> it, if all my existing LPAR configurations will be pulled? I know
> user information and extra profiles will be gone, but I just wanted to
> confirm that it will not affect currently running systems.
>
> Any help is appreciated.
>

the lpar configuration and partition profiles are stored on the managed
system. When you attach a newly installed HMC, you can scan the private
network for managed systems. However, upon first connection, you will
need the password of the hmc user, to authenticate yourself/your hmc to
the managed systems' service-processor. In case you have lost the PW,
IBM can generate a master PW thats valid for your machine for one day
and send a service person to enter it (youre not getting a chance for
reverse-engineering).

Regards,
Joachim Gann

On Jun 10, 3:27 am, Joachim Gann <joachim.g...@gmail.com> wrote:
> bscottberg wrote:
> > While trying to upgrade the HMC from version 5.2.1 to version 6.0.1
> > the HMC completely appears to have bit the dust. I completed the
> > upgrade steps from IBM but when I rebooted the HMC it comes up with an
> > error stating that the install is not complete and the HMC cannot be
> > used until it has been rebooted, then it states that the HMC will be
> > rebooted and the cycle continues.
>
> > Does anyone know if I just recover from the 5.2.1 CDs that came with
> > it, if all my existing LPAR configurations will be pulled? I know
> > user information and extra profiles will be gone, but I just wanted to
> > confirm that it will not affect currently running systems.
>
> > Any help is appreciated.
>
> the lpar configuration and partition profiles are stored on the managed
> system. When you attach a newly installed HMC, you can scan the private
> network for managed systems. However, upon first connection, you will
> need the password of the hmc user, to authenticate yourself/your hmc to
> the managed systems' service-processor. In case you have lost the PW,
> IBM can generate a master PW thats valid for your machine for one day
> and send a service person to enter it (youre not getting a chance for
> reverse-engineering).
>
> Regards,
> Joachim Gann

Thanks for the info..... However which password are you referring
too, the ASMI password for each of the managed systems? or the
standard hscroot HMC account? or is this a different one all together.

bscottberg wrote:
> On Jun 10, 3:27 am, Joachim Gann <joachim.g...@gmail.com> wrote:
>> bscottberg wrote:
>>> While trying to upgrade the HMC from version 5.2.1 to version 6.0.1
>>> the HMC completely appears to have bit the dust. I completed the
>>> upgrade steps from IBM but when I rebooted the HMC it comes up with an
>>> error stating that the install is not complete and the HMC cannot be
>>> used until it has been rebooted, then it states that the HMC will be
>>> rebooted and the cycle continues.
>>> Does anyone know if I just recover from the 5.2.1 CDs that came with
>>> it, if all my existing LPAR configurations will be pulled? I know
>>> user information and extra profiles will be gone, but I just wanted to
>>> confirm that it will not affect currently running systems.
>>> Any help is appreciated.
>> the lpar configuration and partition profiles are stored on the managed
>> system. When you attach a newly installed HMC, you can scan the private
>> network for managed systems. However, upon first connection, you will
>> need the password of the hmc user, to authenticate yourself/your hmc to
>> the managed systems' service-processor. In case you have lost the PW,
>> IBM can generate a master PW thats valid for your machine for one day
>> and send a service person to enter it (youre not getting a chance for
>> reverse-engineering).
>>
>> Regards,
>> Joachim Gann
>
> Thanks for the info..... However which password are you referring
> too, the ASMI password for each of the managed systems? or the
> standard hscroot HMC account? or is this a different one all together.
>

Hi,

yes I refer to the ASM- or CEC-User "hmc". There are 3 users (admin,
general, hmc). HMC uses the "hmc" user and the password you entered upon
first connection to the managed system to authentify itself to the
ASMI/Service Processor/HMC port firmware of the managed system. HMC
stores this PW, so you only need to enter it once. If you connect a new
or freshly installed HMC, you will need to re-enter this PW for each
managed system.

Regards
Joachim Gann

On Jun 10, 1:12 pm, Joachim Gann <joachim.g...@gmail.com> wrote:
> bscottberg wrote:
> > On Jun 10, 3:27 am, Joachim Gann <joachim.g...@gmail.com> wrote:
> >> bscottberg wrote:
> >>> While trying to upgrade the HMC from version 5.2.1 to version 6.0.1
> >>> the HMC completely appears to have bit the dust. I completed the
> >>> upgrade steps from IBM but when I rebooted the HMC it comes up with an
> >>> error stating that the install is not complete and the HMC cannot be
> >>> used until it has been rebooted, then it states that the HMC will be
> >>> rebooted and the cycle continues.
> >>> Does anyone know if I just recover from the 5.2.1 CDs that came with
> >>> it, if all my existing LPAR configurations will be pulled? I know
> >>> user information and extra profiles will be gone, but I just wanted to
> >>> confirm that it will not affect currently running systems.
> >>> Any help is appreciated.
> >> the lpar configuration and partition profiles are stored on the managed
> >> system. When you attach a newly installed HMC, you can scan the private
> >> network for managed systems. However, upon first connection, you will
> >> need the password of the hmc user, to authenticate yourself/your hmc to
> >> the managed systems' service-processor. In case you have lost the PW,
> >> IBM can generate a master PW thats valid for your machine for one day
> >> and send a service person to enter it (youre not getting a chance for
> >> reverse-engineering).
>
> >> Regards,
> >> Joachim Gann
>
> > Thanks for the info..... However which password are you referring
> > too, the ASMI password for each of the managed systems? or the
> > standard hscroot HMC account? or is this a different one all together.
>
> Hi,
>
> yes I refer to the ASM- or CEC-User "hmc". There are 3 users (admin,
> general, hmc). HMC uses the "hmc" user and the password you entered upon
> first connection to the managed system to authentify itself to the
> ASMI/Service Processor/HMC port firmware of the managed system. HMC
> stores this PW, so you only need to enter it once. If you connect a new
> or freshly installed HMC, you will need to re-enter this PW for each
> managed system.
>
> Regards
> Joachim Gann- Hide quoted text -
>
> - Show quoted text -

Everything came up just fine this morning. I will have to a little
bit of the security configuration changes we had in place but in the
end not nearly as big of a disaster as I originally feared. Thanks
again for all your help!!!