Re: HMC/FSP upgrade questions....

I just went through this recently on a box that had not been upgraded in
quite some time. I had to go from v6.1.1 to v7.3.4 and do the disrubtive
FSP upgrade. The whole process to get to 7.3.4 took about 3 hours. The FSP
upgrade took about an hour. Make sure you have the correct service packs
prior to moving forward.

On Thu, Sep 10, 2009 at 2:17 AM, Pete Massiello
<pmassiello-ml@xxxxxxxxxxxx>wrote:

You can upgrade from SF240_320 to SF240_358 concurrently (you know this
because of 320 is greater than 201), as I have done this many times. You
can also upgrade your HMC without affecting the operations of your i5
(unless you are using it as a console, then you will just lose the console
function during the upgrade until the HMC is back up. .

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120

Add iTech Solutionw on LinkedIn:
http://www.linkedin.com/groups?gid=2206093





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of bll1981
Sent: Wednesday, September 09, 2009 5:08 PM
To: midrange-l@xxxxxxxxxxxx
Subject: HMC/FSP upgrade questions....

All,

We are planning an upgrade to our HMC code & FSP firmware. Since this is
something that's done once in a blue moon, need some advice relative to the
"disruptiveness" or lack thereof relative to this procedure. I have read
much of the available documentation IBM released, and find it confusing, so
please no references that aren't explicit. (I say confusing because some
IBM'ers I have spoken to say disruptive, but the information from fix
central copied below, says otherwise. Notice how it directly references p5
but not i5. This bothered me as well.)

Environment:
9406-570 (dual service processors)
HMC - 6.1.3
FSP level - SF240-320-201

Targeted upgrade:
HMC - 7.3.4 with latest service packs
FSP - SF240-358-201

Obviously I know there are some HMC recycles involved, but I am only
concerned with managed system disruptions. Those that have done upgrades of
this nature please chime in. Thanks

3.0 Firmware Information and DescriptionIBM introduced the Concurrent
Firmware Maintenance (CFM) function on p5 systems in system firmware level
SF230_126_120, which was released on June 16, 2005. This function supports
nondisruptive system firmware service packs to be applied to the system
concurrently (without requiring an IPL to activate changes).
For systems that are not managed by an HMC, the installation of system
firmware is always disruptive.
Note: The concurrent levels of system firmware may, on occasion, contain
fixes that are known as deferred. These deferred fixes can be installed
concurrently, but will not be activated until the next IPL. Deferred
fixes,
if any, will be identified in the "Firmware Update Descriptions" table of
this document. For deferred fixes within a service pack, only the fixes in
the service pack which cannot be concurrently activated are deferred.
Use the following example as a reference to determine whether your
installation will be concurrent or disruptive.
Note: The file names and service pack levels used in the following
examples
are for clarification only, and are not
necessarily levels that have been, or will be released.
System firmware file naming convention:
01SFXXX_YYY_ZZZ
* XXX is the release level
* YYY is the service pack level
* ZZZ is the last disruptive service pack level NOTE: Values of
service pack and last disruptive service pack level (YYY and ZZZ) are only
unique within
a release level (XXX). For example, 01SF235_250_120 and 01SF240_250_200
are
different service packs.
An installation is disruptive if:
* The release levels (XXX) are different. Example:
Currently installed release is SF225, new release is SF230
* The service pack level (YYY) and the last disruptive service pack
level (ZZZ) are equal. Example: SF230_120_120 is
disruptive,
no matter what level of SF230 is currently
installed on the system
* The service pack level (YYY) currently installed on the system is
lower than the last disruptive service pack level (ZZZ) of the service pack
to be installed. Example: Currently installed service
pack
is SF230_120_120 and
new service pack is SF230_152_130
An installation is concurrent if:
* The release level (XXX) is the same.
* The service pack level (YYY) is the same or higher than the
service pack level currently installed on your system.
Example: Currently installed service pack is SF230_126_120,
new service pack is SF230_143_120.
--
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.