Re: HMC code update from the grave -- MIDRANGE-L

Roberto,

Check to see if the firmware is HMC managed or not. If not, it should be. That is one of Larry's big landmines to step on. If the FSP firmware is OS managed, a set of PTFs could upgrade it and clobber your HMC connectivity without you planning and/or knowing about it. That could wind up with an unhappy series of events until the HMC is updated.

The fact that you were surprised about the firmware level leads me to wonder how that is set up.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 2/10/2012 12:28 PM, Roberto José Etcheverry Romero wrote:

In the end the hmc was at v6r1.3. I could swear the gui was not like
that in v6r1, but version 6 release 1.3 is what "about" tells me.
I'll just install the pre v7 efixes, check the asmi password and
proceed onwards to v7.
FSP was at 240_382, seems somebody other than me had already upgraded
the fw, maybe ibm back when it was under contract...
in any case, thanks all for the advice.

Best Regards,

Roberto

On Thu, Feb 9, 2012 at 10:23 AM,<rob@xxxxxxxxx> wrote:

> Hey, we keep it right there on the post it note by the hmc. We figure,
> hey, it's a card access room and it's only hmc/fsp stuff. Not like we
> keep qsecofr or some such thing on a post it note. Data's secure and
> we're only opening ourselves to a DOS attack. But if they can get into
> the machine room a few yanks on some network and/or power cables is a much
> simpler DOS attack.
>
>
> Rob Berendt
> --
> 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@xxxxxxxxxx>
> To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>,
> Date: 02/09/2012 08:20 AM
> Subject: Re: HMC code update from the grave
> Sent by:midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> One way to ensure you know the HMC password is to go into the ASMI from
> the HMC and change it BEFORE you do anything else. That has saved my
> backside a time or two since customers rarely know what the CE or
> installer set it to in the first place. Then if they think they know,
> it's almost always not correct. Customers with legislative
> constraints, or that have a full time administration staff usually know
> the password and it's correct.
>
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
>
>
> On 2/8/2012 7:34 PM, DrFranken 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.

>>> >

>> --

> --