problem downloading Firmware

[a***@yahoo.com]

I am having problems downloading firmware from the IBM site. If someone
else could test I would appreciate it. I am trying to download the
SF235_160 (RPM) package from the following site:

http://techsupport.services.ibm.com/server/mdownload

According the the instructions after I click the RPM link I should get
a license agreement, and I do. After I agree I should get file download
window for the 01SF235_160_160.rpm package. I do not get this. I get
01SF235_160_160.htm which is a HTML document.

This downloads fine. Unfortunately this is a 22k html document, and not
the .rpm firmware package I need to install to update my firmware.

This could be part of our corporate "lockdown" settings for the
browser, or an error on the IBM site. I'm not sure which.

Thanks in advance.

Don

[Frank Fegert]

Post by a***@yahoo.com
I am having problems downloading firmware from the IBM site. If someone
else could test I would appreciate it. I am trying to download the
http://techsupport.services.ibm.com/server/mdownload
According the the instructions after I click the RPM link I should get
a license agreement, and I do. After I agree I should get file download
window for the 01SF235_160_160.rpm package. I do not get this. I get
01SF235_160_160.htm which is a HTML document.
This downloads fine. Unfortunately this is a 22k html document, and not
the .rpm firmware package I need to install to update my firmware.
This could be part of our corporate "lockdown" settings for the
browser, or an error on the IBM site. I'm not sure which.

Seems to be. Works fine from here (direct internet connect).

Regards,

Frank

[[e-mail]]

Works fine. I just downloaded and burned to a CD for myself.

[a***@yahoo.com]

Post by ***@gmail.com
Works fine. I just downloaded and burned to a CD for myself.

Thanks to all who tested.

Duh..... I realized my system did not know how to handle a .rpm MIME
type.
(Windoze..... did not handle .rpm so attempted to save as .html)

Added .rpm to file types as UNKNOWN........ download works fine now.

[v***@gmail.com]

Download BOTH filese to your local host which runs ftp server, use ftp
method instead. All this network admins paranoya with proxy that and
proxy this doesn't help at all with setting up automated update and
such...

[a***@yahoo.com]

Post by v***@gmail.com
Download BOTH filese to your local host which runs ftp server, use ftp
method instead. All this network admins paranoya with proxy that and
proxy this doesn't help at all with setting up automated update and
such...

The way I read it, both files are necessary only if a CD-ROM is being
created. Correct?
Note: If your HMC is not internet connected you will need to download
the new firmware level to a CD-ROM or ftp server.

If you are using a CD-ROM, download the individual .rpm and .xml files
from this location to an ftp server or a CD-ROM (both files are
required). Make sure the file names have the format 01SF2xx_yyy_zzz,
with an extention of .rpm and .xml before copying them to an ftp server
or CD-ROM. If using a CD-ROM you then copy the .rpm and .xml files to
the CD using a local CD-ROM burner utility.


Because of the comma, I'm treating it as an "if then" condition
applying to CD-ROM. Again, in the last sentence, if sounds like a
if/then condition applying to CD-ROM.

I do not have a HMC on my system, and am applying directly from
/tmp/fwupdate.
Have you expierenced something different?? Please advise.

Thanks in advance

Don

[v***@gmail.com]

Assuming you have p5 system that isn't partitioned and running only
default partition with AIX loaded you need to download RPM file to your
system, then unpack it using rpm -Uhv <filename.rpm> command so your
/tmp/fwupdate contain that 01SF235_160_160 file, then

# cd /tmp/fwupdate
# ls
01SF235_160_160

/usr/lpp/diagnostics/bin/update_flash -f 01SF235_160_160

During the server firmware installation process, reference codes
CA2799FD and CA2799FF are alternately displayed on the control panel.
After the installation is complete, the system is automatically powered
off and powered on.

After system is power on
lsattr -El sys0 -a fwversion -F value

this one should match the name of the fwleve.file you've loaded in
prev.step ( without last 160 )

or
lsmcode

[Alex Fassas]

We have been fighting errors ever since we tried to 'update_flash -f
01SF235_160_160'. The P5 520 appeared to flash upgrade OK.

Upon reboot the Control Panel hung at 0727 (this was a Function 11
display; maps to SRC101-0727), apparently something about 'failed to
configure unknown async device'. We were able to powerdown system via
the Control Panel. On next Power On / boot cycle, the system started
to boot from the T-side firmware and switched to the P-side during the
boot process. We are also getting errors in our error log: A7001152,
B181300A (w/ possible FRU's FSPSP04 FSPSP06).

The system seems to boot fine from the old P-side copy of firmware
SF222_074, but it still throws errors in log as mentioned above. We
can 'reject flash upgrade' and get things back to normal.

We double checked the downloaded firmware 01SF235_160_160.rpm for size
and checksum; all was fine there. We tried to flash_update a 2nd time
with the same results.

We have no HMC and have not been able to setup our AMSI as of yet (our
System software provider has configured and changed the password; we
are asking them for this). We do have a graphics console. We are
running AIX 5.3.0 ML 03.

Any help appreciated.

Alex Fassas

[a***@yahoo.com]

Post by Alex Fassas
We have been fighting errors ever since we tried to 'update_flash -f
01SF235_160_160'. The P5 520 appeared to flash upgrade OK.
Upon reboot the Control Panel hung at 0727 (this was a Function 11
display; maps to SRC101-0727), apparently something about 'failed to
configure unknown async device'. We were able to powerdown system via
the Control Panel. On next Power On / boot cycle, the system started
to boot from the T-side firmware and switched to the P-side during the
boot process. We are also getting errors in our error log: A7001152,
B181300A (w/ possible FRU's FSPSP04 FSPSP06).
The system seems to boot fine from the old P-side copy of firmware
SF222_074, but it still throws errors in log as mentioned above. We
can 'reject flash upgrade' and get things back to normal.
We double checked the downloaded firmware 01SF235_160_160.rpm for size
and checksum; all was fine there. We tried to flash_update a 2nd time
with the same results.
We have no HMC and have not been able to setup our AMSI as of yet (our
System software provider has configured and changed the password; we
are asking them for this). We do have a graphics console. We are
running AIX 5.3.0 ML 03.
Any help appreciated.
Alex Fassas

Alex, I upgraded our p5 520 this Tuesday with no problems. Our
environments are similar (see earlier post) except we are at Aix 5.3
ML2 (going to ML3 next week, providing no problems with firmware)

One question. Are you using the CD-ROM you talked about burning in an
earlier post?
If so, you need both the .rpm and .xml files on your CD. If ftp is used
only the .rpm file is required. Read the "Description" document, and
the links referenced in it, carefully.

Our p5 520 no HMC, came right up with no problems on the control panel
or in the error log.

[Alex Fassas]

Still no go on the CD-ROM (DVD-RAM drive).

We are trying to get everything patched up to the latest on the system
before declaring service call (as the first question by IBM service is
"Are you at the latest versions of firmware for system and devices and
latest release, maint. level, and fixes for AIX?). Short answer, we
used ftp to put the rpm and the xml file in the /tmp/fwupdate
directory, then ran the 'rpm -Uvh --ignoreos 01SF235_160_160.rpm' from
that directory.

I am wondering if the early P5 520 Service Processor FRU's can be buggy
about being flashed. I have read in IBM service docs, that if you have
tried repeatedly to flash the system firmware, that the next step is to
replace the FRU SVCPROC.
ie.
http://publib.boulder.ibm.com/infocenter/eserver/v1r3s/topic/iphau/fruliccode.htm

Having fun here in Kentucky.
Alex Fassas

[a***@yahoo.com]

Post by Alex Fassas
Still no go on the CD-ROM (DVD-RAM drive).
We are trying to get everything patched up to the latest on the system
before declaring service call (as the first question by IBM service is
"Are you at the latest versions of firmware for system and devices and
latest release, maint. level, and fixes for AIX?). Short answer, we
used ftp to put the rpm and the xml file in the /tmp/fwupdate
directory, then ran the 'rpm -Uvh --ignoreos 01SF235_160_160.rpm' from
that directory.
I am wondering if the early P5 520 Service Processor FRU's can be buggy
about being flashed. I have read in IBM service docs, that if you have
tried repeatedly to flash the system firmware, that the next step is to
replace the FRU SVCPROC.
ie.
http://publib.boulder.ibm.com/infocenter/eserver/v1r3s/topic/iphau/fruliccode.htm
Having fun here in Kentucky.
Alex Fassas

Hmm.... similar to what I did, except I did nothing with the .xml file
(didn't even download).
Followed these instuctions:

http://publib.boulder.ibm.com/infocenter/eserver/v1r3s/index.jsp?topic=/ipha5/fix_serv_firm_kick.htm

We took delivery of our p5 520 in April of this year. It shipped with
SF225_096 already on it.

Don

(also in Kentucky (Louisville))

[Alex Fassas]

Our p5 520 was built / AIX installed on 1/10/05. It shipped with
SF220_074 system firmware & AIX 5.3.0L ML 00. Do you suppose there are
issues with making such a large jump in firmware levels?

We now are upto AIX 5.3.0L ML03 w/ fixes current through 11/10/05. We
updated SCSI adapter firmware to sisscsia0!44415255.050A006a from
original. And we were hoping to update the system firmware to the
latest SF235_160 in hopes of taking care of 2 gotchas (aka "issues")
with our current system.

Gotcha # 1is the external SCSI Quantum/Certance/Seagate (read non-IBM)
DDS4 4mm tape drive. It is attached on SCSI channel 1 (of 0 and 1) of
the internal dual channel U-320 SCSI adapter (we didn't need a second
4-pack hard drive bay). Anyway this tape drive will throw a SCSI Error
upon system boot. We have to reset the SCSI bus for that device ( a
small piece of C code compiled for this that we run from /etc/inittab)
or else power cycle the tape drive after sys boot, to get it to work.
The tape drive works fine once AIX can talk to it after sys boot.

The 2nd Gotcha is that we never tried writing to the Slimline IDE
DVD-RAM IBM FC5751 until November, 2005. And we are having issues
there. BTW, our DVD-RAM info is:
# lscfg -vl cd0
cd0 U787A.001.DPM03RF-P4-D2 IDE DVD-RAM Drive

Manufacturer................IBM
Machine Type and Model......RMBO0020501
ROS Level and ID............H106
Device Specific.(Z0)........058002028F000030
Part Number.................97P3692
EC Level....................H64088
FRU Number..................97P3693

Is this the same as your (***@yahoo.com) DVD-RAM drive?

In regards to my previous postings about the firmware upgrade not
taking and throwing errors. Hooray! I was able to gain access to the
ASMI via the serial port and configure the ASMI for Web access just
fine.

I found an interesting setting that most likely caused my initial
problem with updating the system firmware. From ASMI the 'System
Configuration' -> 'Firmware Update Policy' was set to 'HMC'. Since we
do not have an HMC, I changed this to the only other setting of
'Operating System' and 'saved settings'. I then did the following
'diag' -> 'task selection' -> 'Update and manage System Flash' ->
'Reject the Temporary Image' (which showed as version .}oH00000 anyway,
so I didn't trust it).

After getting both T & P firmware images to SF222_074 again, then
attempted to 'update_flash -f 01SF235_160_160. All appeared to go
well, except the server did a continuous cycle of reboots for 6 or 7
times before finally stopping with being booted from the P-side (old
version) of the firmware, with errors and platform dumps errors in the
log. Oh, the T-side version is showing .}oH00000 . Other than the
numerous reboots, the result of the attempted firmware upgrade is about
the same.

I think its time for an excorcist to make a house call in regards to
the firmware upgrade.

Any thoughts on the DVD-RAM version or model as a source of that device
being seen as 'write protected' would be appreciated (sorry, I know
that issue was brought up in another thread).

Alex Fassas
Richmond, Kentucky

[a***@yahoo.com]

Post by Alex Fassas
Our p5 520 was built / AIX installed on 1/10/05. It shipped with
SF220_074 system firmware & AIX 5.3.0L ML 00. Do you suppose there are
issues with making such a large jump in firmware levels?
We now are upto AIX 5.3.0L ML03 w/ fixes current through 11/10/05. We
updated SCSI adapter firmware to sisscsia0!44415255.050A006a from
original. And we were hoping to update the system firmware to the
latest SF235_160 in hopes of taking care of 2 gotchas (aka "issues")
with our current system.
Gotcha # 1is the external SCSI Quantum/Certance/Seagate (read non-IBM)
DDS4 4mm tape drive. It is attached on SCSI channel 1 (of 0 and 1) of
the internal dual channel U-320 SCSI adapter (we didn't need a second
4-pack hard drive bay). Anyway this tape drive will throw a SCSI Error
upon system boot. We have to reset the SCSI bus for that device ( a
small piece of C code compiled for this that we run from /etc/inittab)
or else power cycle the tape drive after sys boot, to get it to work.
The tape drive works fine once AIX can talk to it after sys boot.
The 2nd Gotcha is that we never tried writing to the Slimline IDE
DVD-RAM IBM FC5751 until November, 2005. And we are having issues
# lscfg -vl cd0
cd0 U787A.001.DPM03RF-P4-D2 IDE DVD-RAM Drive
Manufacturer................IBM
Machine Type and Model......RMBO0020501
ROS Level and ID............H106
Device Specific.(Z0)........058002028F000030
Part Number.................97P3692
EC Level....................H64088
FRU Number..................97P3693

Yes it looks the same as yours. Mine is:

lscfg -vl cd0
cd0 U787A.001.DPM0Y6V-P4-D2 IDE DVD-RAM Drive

Manufacturer................IBM
Machine Type and Model......RMBO0020501
ROS Level and ID............H106
Device Specific.(Z0)........058002028F000030
Part Number.................97P3692
EC Level....................H64088
FRU Number..................97P3693


Don

Post by Alex Fassas
In regards to my previous postings about the firmware upgrade not
taking and throwing errors. Hooray! I was able to gain access to the
ASMI via the serial port and configure the ASMI for Web access just
fine.
I found an interesting setting that most likely caused my initial
problem with updating the system firmware. From ASMI the 'System
Configuration' -> 'Firmware Update Policy' was set to 'HMC'. Since we
do not have an HMC, I changed this to the only other setting of
'Operating System' and 'saved settings'. I then did the following
'diag' -> 'task selection' -> 'Update and manage System Flash' ->
'Reject the Temporary Image' (which showed as version .}oH00000 anyway,
so I didn't trust it).
After getting both T & P firmware images to SF222_074 again, then
attempted to 'update_flash -f 01SF235_160_160. All appeared to go
well, except the server did a continuous cycle of reboots for 6 or 7
times before finally stopping with being booted from the P-side (old
version) of the firmware, with errors and platform dumps errors in the
log. Oh, the T-side version is showing .}oH00000 . Other than the
numerous reboots, the result of the attempted firmware upgrade is about
the same.
I think its time for an excorcist to make a house call in regards to
the firmware upgrade.
Any thoughts on the DVD-RAM version or model as a source of that device
being seen as 'write protected' would be appreciated (sorry, I know
that issue was brought up in another thread).
Alex Fassas
Richmond, Kentucky

[Alex Fassas]

Eureka!!

We have finally gotten our p5 520 upgraded to system firmware
SF235_160.

The problem the entire time was having a system that would IPL cleanly
in the first place. ie. We had an issue mentioned earlier with a 'SCSI
Bus Error' at boot time. This is due to a non-IBM external SCSI tape
drive. Apparently, any error message during the firmware upgrade
process and first IPL is seen as a 'No Go' for completing the upgrade
and the routine IPL's from the old (P-side) firmware and marks the
T-side firmware version as unusable (ie. version # .}oH00000) . We
powered off the tape drive, IPL'ed cleanly, then began the
'update_flash' routine. All went according to the documentation this
time.

Sadly, even after having all firmware and AIX OS to the latest levels,
we still have a FC5751 DVD-RAM drive that says the media is '
write-protected'. The error messages say to try a new media, so I am
going to breakdown and order the IBM part # media, even though the
Maxell part # I am using is approved and being used by others.

Thanks for all of the help.

Alex Fassas