From: Joe Brancaleone (joe@nitech.com)
Date: Wed Jan 21 2004 - 17:22:53 EST
Dear list,
We purchased hardware components in order to upgrade an older L1500 to
an L3000 (new CPU's, memory carrier, motherboard, disk drive backplane,
pci IO board, new sheet metal, etc. etc.), which is something I haven't
had to do before. After the meticulous hardware swapping, the server was
rendered unbootable with software errors. After replacing all the old
equipment and booting successfully, we saw that the hardware enablement
patches were so old (June 2001) it would not support this hardware
upgrade. The documentation states Sep. 2001 is the absolute earliest
hardware enablement release which supports this particular upgrade. Big
mistake for not checking on this ahead of time.
Well we then performed the Sep. 2003 HW enablement patch update, but
booting back into the OS was again unsuccessful, with Software Level
Alerts in the GSP error log such as these before it forced reboot:
> ************* SYSTEM ALERT **************
> SYSTEM NAME: uninitialized
> DATE: 01/07/2004 TIME: 04:54:21
> ALERT LEVEL: 12 = Software failure
> REASON FOR ALERT
> SOURCE: 1 = processor
> SOURCE DETAIL: 1 = processor general SOURCE ID: 0
> PROBLEM DETAIL: 0 = no problem detail
> LEDs: RUN ATTENTION FAULT REMOTE POWER
> FLASH FLASH OFF ON ON
> 0xF8E000C01100B800 00000000 0000B800 - type 31 = legacy PA HEX
> chassis-code
> 0x58E008C01100B800 00006800 07043615 - type 11 = Timestamp 01/07/2004
> 04:54:21
> ************* SYSTEM ALERT **************
> SYSTEM NAME: uninitialized
> DATE: 01/07/2004 TIME: 04:54:21
> ALERT LEVEL: 12 = Software failure
> REASON FOR ALERT
> SOURCE: 1 = processor
> SOURCE DETAIL: 1 = processor general SOURCE ID: 0
> PROBLEM DETAIL: 0 = no problem detail
> LEDs: RUN ATTENTION FAULT REMOTE POWER
> OFF FLASH OFF ON ON
> 0xA0E000C01100B000 00000000 000005E9 - type 20 = major change in
> system state
> 0x58E008C01100B000 00006800 07043615 - type 11 = Timestamp 01/07/2004
> 04:54:21
I had to boot to the old vmunix.prev kernel and uninstall the HW
Enablement bundle in order to make the server bootable again.
Why would the HW enablement bundle cause the kernel to be unbootable?
Does something else need updating first on this old system? Another
patch bundle before the HW Enablement patch bundle? Is a system firmware
update or GSP firmware update necessary first of all? Is there a
document that more fully explains the sequence of updates neccessary?
It's difficult to keep doing the trial and error method when all we have
are after hours for server downtime.
The system's Firmware Version is 41.39, GSP Firmware Revision is A.01.06
Thanks in advance.
joe
--
Joe Brancaleone
Support Technician
_______________
Nitech
35 Musick
Irvine Ca. 92618
Phn: 1-888-264-8324
Fax: 949-586-5234
Email: joe@nitech.com
http://www.nitech.com
Mission Statement:
Nitech is a leader in data management. Our extensive knowledge in both Unix and NT allows us to provide competitive data storage, networking and computing solutions.
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:38 EDT