SEO

#1 (**permalink**) 01-05-2008, 06:18 AM

Hey All,

I'm trying to understand the proper steps to take to "back out" of a
sysem firmware/microcode update. Does one need to just update_flash
the file containing the last level of microcode? What can be done if
this file is not available/archived?

#2 (**permalink**) 01-05-2008, 06:18 AM

On what platform and what type of firmware (system or adapter) you are trying
to back out? And what is that you don't like with that f/w?

Michael

On Wed, 13 Apr 2005, cdwells wrote:

c > Date: 13 Apr 2005 09:54:50 -0700
c > From: cdwells <cdwells@blueone.net>
c > Newsgroups: comp.unix.aix
c > Subject: Backing out of system firmware updates
c >
c > Hey All,
c >
c > I'm trying to understand the proper steps to take to "back out" of a
c > sysem firmware/microcode update. Does one need to just update_flash
c > the file containing the last level of microcode? What can be done if
c > this file is not available/archived?
c >
c >

#3 (**permalink**) 01-05-2008, 06:18 AM

Sorry - this was actually a hypothetical question I guess. We are
running 7026-B80s and I refer specifically to system and service
processor firmware.

I am just curious - in the event of a problem incurred by the new
firmware level - how should one go about "backing out" of the update/

#4 (**permalink**) 01-05-2008, 06:18 AM

Sorry - this was actually a hypothetical question I guess. We are
running 7026-B80s and I refer specifically to system and service
processor firmware.

I am just curious - in the event of a problem incurred by the new
firmware level - how should one go about "backing out" of the update/

The procedure is discussed in detail for each firmware level you might
download. This includes how to handle the diskettes, or your previous
XXXXX.img files should a restore be necessary.

There is normally an apply/restore section for:
command line method
Update Flash Diagnostic Service Aid method
Service Processor Menu method

I have never had a firmware or service processor firmware
failure/corruption during my 9+ years with AIX. The failures I have
heard about normally resulted from a lack of patience.

On my systems checkpoints 99FF and 99FD alternately appear while the
update occurs. Be PATIENT... and you should be ok

#5 (**permalink**) 01-05-2008, 06:18 AM

Biggest tip if one fails: don't reboot!

If it goes sufficiently bad, IBM will need to come on-site.

If you don't reboot and retry application with either existing or new
version, may be enough to fix it.

-Dan

#6 (**permalink**) 01-05-2008, 06:19 AM

"cdwells" <cdwells@blueone.net> wrote in message news:<1113418086.044202.78230@f14g2000cwb.googlegr oups.com>...
> Sorry - this was actually a hypothetical question I guess. We are
> running 7026-B80s and I refer specifically to system and service
> processor firmware.
>
> I am just curious - in the event of a problem incurred by the new
> firmware level - how should one go about "backing out" of the update/

The firmware when newly loaded goes in as a temporary copy. There is a
permanent version =whcih is the one you had before the update. You can
toggle between the 2 versions -and overwrite either of them -but at
least 1 must be valid for you to get into the system on a reboot.

regards
-kamal

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode