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



Bernd,

I would disagree with your reply.

The HMC is not OS Managed. The FSP is OS Managed.

In my note, I said that there is no need to IPL the server at all
when you upgrade the HMC.

OS Managed is wrong for a machine connected to an HMC.

If you change this (FSP) from OS Managed to HMC Managed, then you
can do a non-distruptive (NO IPL Required) if you update from 01SF240_219 to
01SF240_320.

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bernd Schaefers
Sent: Monday, August 27, 2007 2:21 PM
To: Midrange Systems Technical Discussion
Subject: Re: V5R4M0 upgrade - HMC as well?

Hi Pete,

With OS managed HMC you need a server IPL to update the FSP, not a simple
pwrdwnsys for applying PTFs.

Bernd

----- Original Message -----
From: "Pete Massiello" <pmassiello-ml@xxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, August 27, 2007 7:44 PM
Subject: RE: V5R4M0 upgrade - HMC as well?


Everyone who owns an HMC should take a look at this. This is a potential
problem that is about to cause havoc.

Do you see that the customer has an HMC, but the firmware update policy is
set to OS Managed. So this means when he applies PTFs it will update the
FSP. Now if these are two releases (HMC and FSP) that can't communicate he
will have a problem. The policy should be set to HMC Managed, so that you
can control when the HMC and FSP get updated. I believe right now that
HMC
4.3 is not a supported combination with FSP 01SF240.

The good news is you can update the HMC without taking the system down.
Upgrades will take about at most 60 to 90 minutes, and you will have to
get
to 6.1.2 and then to 7.3.1 (Two upgrades). Don't forget to save to
Upgrade
Data to DVD.

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Monday, August 27, 2007 12:15 PM
To: Midrange Systems Technical Discussion
Subject: Re: V5R4M0 upgrade - HMC as well?

Thanks. Pete had given me good counsel on this.

Pete or Rob, any WAG on the time required to move an old HMC version to
the latest and greatest? Biggest concern is the amount of time the
System i would be down. I plan to take care of the HMC upgrade first,
let the dust settle, and then go to V5R4M0. As a quick refresher the
HMC version info is:

V 4.0
Release 3.3
HMC Build level 20050114.1
MH00224
Backup/Restore fix level (02-17-2005)

FLASHLEVELS in SST show:

LS Flash Sync Enabled.
OS MANAGED
Base Level:

Side Date/Time MI Keyword PTFs (V5R3M0)
------------- ------------- ---------- -------------
Memory 20060505/1020 SF240_219 MH00678
Flash P 20050311/1416 SF225_096 MH00248
Flash T 20060505/1020 SF240_219 MH00678
Load Source A 20050311/1416 SF225_096 MH00248
Load Source B 20060505/1020 SF240_219 MH00678


Thanks,

Pete Helgren

rob@xxxxxxxxx wrote:
There was a most recent discussion on this. I was pointed to an
excellent

cross reference.

Keep in mind that there are three things to keep in mind:
- Version of HMC code.
- Version of FSP code. (FSP is like the old controlling partition.)
- Version of i5/os.

This reference tells you what is supported with what. In our case we had
to upgrade our HMC from V5.? to the last version of V6 currently
available. Then we upgraded our FSP code. Then we finished upgrading
our

HMC to V7.


https://www14.software.ibm.com/webapp/set2/sas/f/power5cm/supportedcode.html

Viewing existing firmware levels:


http://publib.boulder.ibm.com/infocenter/eserver/v1r3s/topic/ipha5/viewexist
level.htm

Rob Berendt

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





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


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.484 / Virus Database: 269.12.9/975 - Release Date: 26.08.2007
21:34




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.