Re: Firmware Upgrades before ML upgrade?

Our shop being what it is, we schedule both firmware and ML at the same
time due to maintenance window constraints. Usually we do the ML and
then the firmware which equates to only one reboot if all goes well.

You might find others who will say this is a bad practice since you are
changing many things at one time, how do you go back... Well first we
validate everything in our QA/Test/Dev environments allowing for burn
in. Secondly, MKSYSBs and machines with the ability to boot/store
different versions of the firmware are also a big help.

Always being as current as we can does have great benefits when dealing
with support !

My $.02 and I'll bet there will be conflicting ideas which is great !

Lamar

-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@xxxxxxxxxxxxx] On Behalf Of
John F Riordan
Sent: Thursday, February 09, 2006 9:34 AM
To: aix-l@xxxxxxxxxxxxx
Subject: Firmware Upgrades before ML upgrade?

Hello All,

I have to upgrade all my servers to the latest ML release. In the past
I
have never had any issues with this. However, the last time I did a ML
upgrade I had to install the latest firmware level for that particular
machine. ( This was after the machine would not boot with the ML
installed)
With this said, would you recommend installing the latest firmware on
servers before upgrading the OS to the latest ML release? In the past,
the
practice here was to install such updates only when needed.

I have a few machines to do...

p650, Current AIX 5.2 ML-04 ( 5 LPARS)
7026-6H1 Current AIX 5.1 ML-05
7026-B80, Current AIX 5.1 ML-05
7026-B80, Current AIX 5.2 ML-06
7026-H80 Current AIX 5.1 ML-04
7026-H50 Current AIX 5.1 ML-04
7025-F80 Current AIX 5.1 ML-04
7025-F40 Current AIX 5.1 ML-04

Thanks in advance,
John

John Riordan
Unix Systems Administrator
...........and lots of other stuff.
CSC / Bath Iron Works
Bath, Maine
207.442.1094 -Office
207.649.2694 -Cell



------------------------------------------------------------------------
----------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written
agreement or government initiative expressly permitting the use of
e-mail
for such purpose.
------------------------------------------------------------------------
----------------


Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.

Relevant Pages