|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: IT Resource Center (support_feedback_at_us-support2-mail.external.hp.com)
Date: Sun Nov 03 2002 - 06:13:03 CST
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly all firmware patch digest
Created: Sun Nov 3 6:05:06 EST 2002
Table of Contents:
Document ID Title
--------------- -----------
PF_CHARGSPC0210 rp24xx revision B GSP firmware C.02.10
PF_CCANGSPB0215 A6696B GSP firmware B.02.15
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PF_CHARGSPC0210
Date Loaded: 20021029
Title: rp24xx revision B GSP firmware C.02.10
Patch Name: PF_CHARGSPC0210
Patch Description: rp24xx revision B GSP firmware C.02.10
Creation Date: 02/10/15
Post Date: 02/10/29
Products:
A6889A rp2430 server
A6890A rp2470 server
Status: General Release
Critical: No
Category Tags:
defect_repair hardware_enablement enhancement
general_release
Path Name: /firmware_patches/hp/cpu/PF_CHARGSPC0210
Symptoms:
PF_CHARGSPC0210:
The following enhancements and fixes are included in
GSP firmware revision C.02.10
Corrected an issue with the firmware update process that
prevents some systems from updating.
Updating to GSP firmware revision C.02.10 requires
updating to an update only image first. The update only
image has no functionality other than to update to Revision
C.02.10.
PF_CHARGSPC0209:
The following enhancement and fixes are included in GSP
firmware revision C.02.09
Console context has been removed from the firmware.
PF_CHARGSPC0208:
The following enhancement and fixes are included in GSP
firmware revision C.02.08
1.A user joining a mirrored GSP session can inadvertently
complete another user's command.
When two (or more) users are mirroring in Console mode
now only one user will have write
capability at a time. Messages have been included to let
users know how to get ownership (write capability) to the
console when they need to have write capability.
Users who do not have Console Write Ownership will not be
able to type anything until the user requests (and is
granted) Console Write Ownership. The user needs to type
in ^Ecf (that is, hold control key down while typing
'e', release the control key for the 'c' & 'f') to be able
to write while in console mode.
The last 20 lines of text from the console log are now
output to serve as context. Modem and telnet also print the
last 20 lines of text from the console log when joining a
unix console session.The context will also print when
returning from the SE and CSP commands.
2.Added SSL authentication to the web access.
3.In previous versions of GSP firmware the LAN connection
was reset after 1 minute of inactivity. When the LAN port
is connected to various switches this reset was seen as an
error by the switch and created a log entry in the switch.
Firmware revision C.02.08 pings the gateway and subnet
prior to resetting the LAN port.
4.Added a warning to notify the user in the LC and LS
commands that having port 23 selected as the web port will
disable encryption regardless of the security setting
in the SO command.
5.Added a warning message after 3 failed attempts or the
default set with the SO command that the Web Console
connection has been closed.
6.With previous versions of GSP firmware when a MUX is
attached to the UPS port and there was communication on
the port the console would hang and require the system
to be rebooted. Firmware revision C.02.08 corrects this
problem.
7.With Previous versions of GSP firmware when a UPS was
connected to the UPS port an HPMC Would occur when the
GSP was reset with the "XD R" command, an stty reset
command or by pushing the reset button. Firmware revision
C.02.08 corrects this problem.
8. HP has identified a problem on the GSP, which manifests
itself in a number of different ways. Each symptom is
listed below separately in order to facilitate matching
the symptoms to problems experienced. The cause of these
symptoms is fixed with firmware revision C.02.08.
PDC Chassis Code 2083
Intermittent Alert Level 4 events occurring during power
on Selftest/PDC Initialization on L-Series systems with
the A6696B (Maestro GSP). The Alert Level 4 error would
look similar to this:
--------------------------------------------------------
SYSTEM NAME:
DATE: 11/29/2001 TIME: 16:22:52
ALERT LEVEL: 4 = Unexpected configuration change detected
REASON FOR ALERT
SOURCE: 8 = I/O
SOURCE DETAIL: 3 = local bus adapter SOURCE ID: FF
PROBLEM DETAIL: 3 = function failure
LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH OFF OFF OFF ON
LED State: Running non-OS code. (i.e. Boot or Diagnostics)
0x2000004383FF2083 000000FF FF05FF83 - type 4 = Physical
Location
0x5800084383FF2083 0000650A 1D101634 - type 11 =Timestamp
11/29/2001 16:22:52
---------------------------------------------------------
The most significant "signature" of this Alert/GSP Error
is the chassis code ending in "2083" (e.g.
0x2000004383FF2083). This chassis code is associated
with a PDC Selftest Entry Point of
"CC_IO_PM_NOT_RESPONDING_ERROR". Typically associated
with this Alert would be a "power off" of a PCI I/O slot
- with the I/O slot associated with the HPA address
correlating to the HPA address of the "Physical Location"
field of this chassis code.
EMS Event Code 32
The main symptom is the following EMS error event which
instructs the customer to reset the GSP or replace the
system board. This EMS error may be a recurring event
(in the worst case being logged once daily).
The EMS error will show up with this wording:
>---- Event Monitoring Service Event Notification ----<
Notification Time: Sun Dec 16 17:46:54 2001
niscit sent Event Monitor notification information:
/system/events/core_hw/core_hw is >= 3.
Its current value is SERIOUS(4).
Event data from monitor:
Event Time..........: Sun Dec 16 17:46:54 2001
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 32
System..............: niscit
EMS Event Code 31 or 36
An EMS error event similar to the one below which
instructs the customer to reset the GSP or replace the
Platform Monitor or System Board. Note that you
will receive an EMS 36 event for a system with a
"platform monitor" (A-class and L-class) and an EMS
event 31 for a system with a "power monitor" (N-class)
>---- Event Monitoring Service Event Notification ----<
Event Notification Time: Thu Feb 7 06:06:02 2002
jmcdb2 sent Event Monitor notification information:
/system/events/core_hw/core_hw is >= 1.
Its current value is SERIOUS(4).
Event data from monitor:
Event Time..........: Thu Feb 7 06:06:02 2002
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 36
System..............: jmcdb2
PDC 14c0 Chassis Code
Intermittent Alert Level 6 GSP errors similar to the one
below:
--------------------------------------------------------
SYSTEM NAME:
DATE: 01/29/2002 TIME: 09:47:14
ALERT LEVEL: 6 = Boot possible, pending failure - action
required
SOURCE: 8 = I/O
SOURCE DETAIL: 9 = serial SOURCE ID: 0
PROBLEM DETAIL: 3 = functional failure
CALLER ACTIVITY: 1 = test STATUS: 0
CALLER SUBACTIVITY: 4C = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING
ENTITY ID: 00
0x00000063890014C0 00000000 00000000 type 0 = Data Field
Unused
0x58000863890014C0 00006600 1D092F0E type 11 = Timestamp
01/29/2002 09:47:14
----------------------------------------------------------
Note! This same GSP Alert (14c0) message can also be
generated when the system console path is set ncorrectly.
The console path for the Maestro (A6696B) GSP is 0/0/4/1.
The console path for the Tosca (A6696A) GSP is 0/0/4/0.
If you experience this problem, verify the correct
console path setting first
Orphan Log Entries
One or more GSP Alert Level 12 events similar to the one
below:
--------------------------------------------------------
SYSTEM NAME:
DATE: 02/12/2002 TIME: 11:10:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: A = orphan log entry follows
CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 00 = unspecified
REPORTING ENTITY TYPE: 1 = service processor REPORTING
ENTITY ID: 00
0x581008CA11002000 00006601 0C0B0A28 type 11 = Timestamp
02/12/2002 11:10:40
Corrupt Log Entries
One or more GSP Alert Level 12 events similar to the one
below:
--------------------------------------------------------
SYSTEM NAME:
DATE: 02/12/2002 TIME: 11:10:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: A = corrupt log entries
CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 00 = unspecified
REPORTING ENTITY TYPE: 1 = service processor REPORTING
ENTITY ID: 00
0x581008CA11002000 00006601 0C0B0A28 type 11 = Timestamp
02/12/2002 11:10:40
Alert 10/2020 Chassis Code
Intermittent GSP Alert Level 10 errors when rebooting the
system multiple times (e.g. running a continuous power
on/off test that reboots the system over and over). The
GSP Alert will appear like this:
--------------------------------------------------------
Log Entry # 0 :
SYSTEM NAME: uninitialized
DATE: 02/05/2002 TIME: 06:38:50
ALERT LEVEL: 10 = Boot possible, functionality lost
SOURCE: 3 = PDH
SOURCE DETAIL: 6 = interconnect medium SOURCE ID: 0
PROBLEM DETAIL: 3 = non-responding, may need GSP reset.
CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 02 = platform internal interconnect
REPORTING ENTITY TYPE: 1 = service processor REPORTING
ENTITY ID: 00
0x581008A336002020 00006601 05062632 type 11 = Timestamp
02/05/2002
Alert 8/2030 Chassis Code
Intermittent GSP Alert Level 8 Error Log entries similar
to one or more of the events below. Note that the main
footprint signature in these GSP errors is a chassis
code ending in "2030" and unusual ACSII messages.
--------------------------------------------------------
SYSTEM NAME:
DATE: 02/17/2002 TIME: 19:46:53
ALERT LEVEL: 8 = Boot Possible, performance impaired
SOURCE: 6 = platform
SOURCE DETAIL: 6 = service processor SOURCE ID: 0
PROBLEM DETAIL: 1 = selftest result
CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 03 = console
REPORTING ENTITY TYPE: 1 = service processor REPORTING
ENTITY ID: 00
0x7010028166002030 0B0010FF 00000000 type 14 = Problem
Detail
0x4810028166002030 53415332 52616C70 type 9 = ASCII
Message SAS2Ralp
0x4810028166002030 7372632F 4C4F4765 type 9 = ASCII
Message src/LOGe
0x7010028166002030 0106013C 60000013 type 14 = Problem
Detail
0x58100A8166002030 00006601 11132E35 type 11 = Timestamp
02/17/2002 19:46:53
Defect Description:
PF_CHARGSPC0210:
- See Symptoms.
PF_CHARGSPC0209:
- See Symptoms.
PF_CHARGSPC0208:
- See Sypmtoms.
Enhancement:
No (superseded patches contained enhancements)
PF_CHARGSPC0208:
Added SSL authentication to the web access.
SR:
0000000000
Patch Files:
./C.02.10/C0210.bin
./C.02.10/Resources.out
./C.02.10/gsp_a_upg.cnf
./C.02.10/gsp_upg.cnf
./C.02.10/version.dat
./UpdateOnly/UpdateOnly2.bin
./UpdateOnly/gsp_a_upg.cnf
./UpdateOnly/gsp_upg.cnf
./UpdateOnly/mp_upg.cnf
cksum(1) Output:
1982365865 2069008 ./C.02.10/C0210.bin
1537136308 504267 ./C.02.10/Resources.out
613869172 200 ./C.02.10/gsp_a_upg.cnf
613869172 200 ./C.02.10/gsp_upg.cnf
4278717776 16 ./C.02.10/version.dat
3208707489 447192 ./UpdateOnly/UpdateOnly2.bin
1177153808 97 ./UpdateOnly/gsp_a_upg.cnf
1177153808 97 ./UpdateOnly/gsp_upg.cnf
1177153808 97 ./UpdateOnly/mp_upg.cnf
Patch Conflicts: None
Patch Dependencies:
s800: 11.00: PHNE_27393 PHCO_27370
s800: 11.11: PHNE_26326 PHCO_27243
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PF_CHARGSPC0208 PF_CHARGSPC0209
Equivalent Patches: None
Patch Package Size: 1565 KBytes
Installation Instructions:
Please review all instructions and the "Hewlett-Packard
Support Tool License Terms" or your Hewlett-Packard support
terms and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
NOTE: It is important that you read and understand these
instructions completely before you begin. This can
determine your success in completing the Firmware update.
The Firmware update take no more than 5 minutes.
* * * * * * * * PREINSTALLATION ACTIVITIES * * * * * * * * * * * * * *
1. Insure operating system patches are installed to change the device
drivers prior to installing the firmware upgrade. These patches will
be required for any future releases of firmware. The list below
shows the patches required for 11.11 and 11.00
11.00
Console Driver Patch PHNE_27393
INSF Patch PHCO_27370
11.11
Console Driver Patch PHNE_26326
INSF Patch PHCO_27243
2. Stop any process communicating with the UPS port.
* * * * * * * * POST INSTALLATION ACTIVITIES * * * * * * * * * * * *
1. Shutdown the operating system.
2. Remove power to the system.
* * * * * * * * VERIFYING CURRENT REVISION OF FIRMWARE * * * * * * * *
1. telnet into the GSP.
2. logon to the GSP.
3. Type <CNTRL>ecf.
4. Type <CNTRL>b.
5. Type he
If the Revision number of the currently installed firmware is not
C.02.10 then install new firmware.
* * * * * * * * * * UNPACKING THE FIRMWARE * * * * * * * * * * * * * *
1. FTP "PF_CHARGSPC0210.tar.gz" to an empty directory.
2. Use the "gunzip" to unzip the patch.
# gunzip PF_CHARGSPC0210.tar.gz
3. Use the "tar" command to extract the firmware files
# tar -xvf PF_CHARGSPC0210.tar
x UpdateOnly/UpdateOnly2.bin, 447192 bytes, 874 tape blocks
x UpdateOnly/gsp_a_upg.cnf, 97 bytes, 1 tape blocks
x UpdateOnly/gsp_upg.cnf, 97 bytes, 1 tape blocks
x UpdateOnly/mp_upg.cnf, 97 bytes, 1 tape blocks
x C.02.10/C0210.bin, 2069008 bytes, 4042 tape blocks
x C.02.10/Resources.out, 504267 bytes, 985 tape blocks
x C.02.10/gsp_a_upg.cnf, 200 bytes, 1 tape blocks
x C.02.10/gsp_upg.cnf, 200 bytes, 1 tape blocks
x C.02.10/version.dat, 16 bytes, 1 tape blocks
4. Verify the checksum of the files in the C.02.10 directory
using the "cksum" command. Results of the command should be
equal to the following ouput.
# cksum ./C.02.10/*
1982365865 2069008 ./C.02.10/C0210.bin
1537136308 504267 ./C.02.10/Resources.out
613869172 200 ./C.02.10/gsp_a_upg.cnf
613869172 200 ./C.02.10/gsp_upg.cnf
4278717776 16 ./C.02.10/version.dat
5. Verify the checksum of the files in the UpdateOnly directory
using the "cksum" command. Results of the command should be
equal to the following ouput.
# cksum ./UpdateOnly/*
3208707489 447192 ./UpdateOnly/UpdateOnly2.bin
1177153808 97 ./UpdateOnly/gsp_a_upg.cnf
1177153808 97 ./UpdateOnly/gsp_upg.cnf
1177153808 97 ./UpdateOnly/mp_upg.cnf
* * * * * * * * * * * FIRMWARE UPDATE PROCEDURE * * * * * * * * * * *
To update the firmware on the GSP, perform the following steps:
FTP the files to a system with the core I/O lan on the same subnet as the
GSP
1. Access the GSP using the ctrl+b command from the local console keyboard.
2. Ping the LAN where the GSP files are located via the XD command item #3
(LAN access PING)
-----------------------------------------------------------------------------
GSP> xd
XD
Non destructive tests :
1. Parameters checksum
2. I2C access (get Power Monitor status)
3. LAN access (PING)
4. Modem selftests
5. Secondary I2C access (get System status)
Type R to reset the GSP or [Q] to quit the diagnostic menu.
-> Choice: 3
3
Enter IP Address: 192.151.11.37/or your system (core I/O) LAN address
This test must pass on the server being used to supply the update files.
--------------------------------------------------------------------------------
3. Reset the GSP via the XD command (use the R option). This will free up any
unallocated memory for the GSP update.
--------------------------------------------------------------------------------
GSP> xd
XD
Non destructive tests :
1. Parameters checksum
2. I2C access (get Power Monitor status)
3. LAN access (PING)
4. Modem selftests
5. Secondary I2C access (get System status)
Type R to reset the GSP or [Q] to quit the diagnostic menu.
-> Choice: r
r
The GSP is now being reset...
--------------------------------------------------------------------------------
4. Select the GSP command XU. This command activates the upgrade mode.
Update the GSP firmware to the UpdateOnly2 firmware image in the
./UpdateOnly directory.
--------------------------------------------------------------------------------
GSP> xu
XU
This command activates the upgrade mode. All connections will be closed,the session
will be aborted and the modem connection will be dropped immediately, web and
telnet connections will be dropped upon completion. Please, confirm your intention
to activate the upgrade mode (Y/[N]) : y
y
Enter source system IP address: 192.151.11.37/or your system (core I/O) LAN address
15.8.149.21
Enter file path: path on your system used to ftp files IE:/tmp/GSP
Do you wish to use the default login: anonymous / GSP
hp.com (Y/[N]) :
y (if using docs.hp.com)
n (if using local server and local server login is needed).
IE: if root then supply root password
GSP> xu
-> GSP firmware upgrade in progress.
Retrieved an upgrade file sucessfully.
Programming ROM. Percent Complete: 100.
Retrieved an upgrade file sucessfully.
Programming ROM. Percent Complete: 100.
-> GSP firmware upgrade complete - Web and telnet connections will
be dropped. GSP will now reset....
Service Processor login:
Service Processor password:
--------------------------------------------------------------------------------
5. Repeat the firmware update process using the C.02.10 image in the
./C.02.10 directory
--------------------------------------------------------------------------------
1. Access the GSP using the ctrl+b command from the local console keyboard.
2. Ping the LAN where the GSP files are located via the XD command item #3
(LAN access PING)
-----------------------------------------------------------------------------
GSP> xd
XD
Non destructive tests :
1. Parameters checksum
2. I2C access (get Power Monitor status)
3. LAN access (PING)
4. Modem selftests
5. Secondary I2C access (get System status)
Type R to reset the GSP or [Q] to quit the diagnostic menu.
-> Choice: 3
3
Enter IP Address: 192.151.11.37/or your system (core I/O) LAN address
This test must pass on the server being used to supply the update files.
--------------------------------------------------------------------------------
6. Reset the GSP via the XD command (use the R option). This will free up any
unallocated memory for the GSP update.
--------------------------------------------------------------------------------
GSP> xd
XD
Non destructive tests :
1. Parameters checksum
2. I2C access (get Power Monitor status)
3. LAN access (PING)
4. Modem selftests
5. Secondary I2C access (get System status)
Type R to reset the GSP or [Q] to quit the diagnostic menu.
-> Choice: r
r
The GSP is now being reset...
--------------------------------------------------------------------------------
7. Select the GSP command XU. This command activates the upgrade mode.
Update the GSP firmware to the C.02.10 firmware image.
--------------------------------------------------------------------------------
GSP> xu
XU
This command activates the upgrade mode. All connections will be closed,the sess
ion
will be aborted and the modem connection will be dropped immediately, web and
telnet connections will be dropped upon completion. Please, confirm your intenti
on
to activate the upgrade mode (Y/[N]) : y
y
Enter source system IP address: 192.151.11.37/or your system (core I/O) LAN addr
ess
15.8.149.21
Enter file path: path on your system used to ftp files IE:/tmp/GSP
Do you wish to use the default login: anonymous / GSPhp.com (Y/[N]) :
y (if using docs.hp.com)
n (if using local server and local server login is needed).
IE: if root then supply root password
GSP> xu
-> GSP firmware upgrade in progressM-^E.
Retrieved an upgrade file sucessfully.
Programming ROM. Percent Complete: 100.
Retrieved an upgrade file sucessfully.
Programming ROM. Percent Complete: 100.
-> GSP firmware upgrade complete - Web and telnet connections will
be dropped. GSP will now reset....
Service Processor login:
Service Processor password:
After the GSP reset, use the HE command to ensure the firmware update was succes
sful.
--------------------------------------------------------------------------------
* * * * * * * * * * * * * * END OF UPDATE * * * * * * * * * * * * * *
-----End of Document ID: PF_CHARGSPC0210-------------------------------------
Document ID: PF_CCANGSPB0215
Date Loaded: 20021029
Title: A6696B GSP firmware B.02.15
Patch Name: PF_CCANGSPB0215
Patch Description: A6696B GSP firmware B.02.15
Creation Date: 02/10/15
Post Date: 02/10/29
Products:
A6144A HP9000 L3000 Enterprise Server
A6144B HP9000 L3000 Enterprise Server
A6696B L-Class revision B GSP
A3639C HP9000 N4000 Enterprise Server
A6797B HP9000 L1500 Enterprise Server
Status: General Release
Critical: No
Category Tags:
defect_repair hardware_enablement enhancement
general_release
Path Name: /firmware_patches/hp/cpu/PF_CCANGSPB0215
Symptoms:
PF_CCANGSPB0215:
The Following enhancement and fixes are included in GSP
firmware revision B.02.15
Corrected an issue with the firmware update process that
prevents some systems from updating.
Updating to GSP firmware revision B.02.15 requires
updating to an update only image first. The update only
image has no functionality other than to update to Revision
B.02.15.
PF_CCANGSPB0214:
The Following enhancement and fixes are included in GSP
firmware revision B.02.14
The console context feature has been removed.
PF_CCANGSPB0213:
The following enhancement and fixes are included in GSP
firmware revision B.02.13
1.A user joining a mirrored GSP session can inadvertently
complete another user's command.
When two (or more) users are mirroring in Console mode
now only one user will have write
capability at a time. Messages have been included to let
users know how to get ownership (write capability) to the
console when they need to have write capability.
Users who do not have Console Write Ownership will not be
able to type anything until the user requests (and is
granted) Console Write Ownership. The user needs to type
in ^Ecf (that is, hold control key down while typing
'e', release the control key for the 'c' & 'f') to be able
to write while in console mode.
The last 20 lines of text from the console log are now
output to serve as context. Modem and telnet also print the
last 20 lines of text from the console log when joining a
unix console session.The context will also print when
returning from the SE and CSP commands.
2.Added SSL authentication to the web access.
3.Allow the LAN speed to be forced to either 10BT Full
Duplex or 10BT Half Duplex.
4.In previous versions of GSP firmware the LAN connection
was reset after 1 minute of inactivity. When the LAN port
is connected to various switches this reset was seen as an
error by the switch and created a log entry in the switch.
Firmware revision B.02.13 pings the gateway and subnet
prior to resetting the LAN port.
5.Added a warning to notify the user in the LC and LS
commands that having port 23 selected as the web port will
disable encryption regardless of the security setting
in the SO command.
6.Added a warning message after 3 failed attempts or the
default set with the SO command that the Web Console
connection has been closed.
7.With previous versions of GSP firmware when a MUX is
attached to the UPS port and there was communication on
the port the console would hang and require the system
to be rebooted. Firmware revision B.02.13 corrects this
problem.
8.With Previous versions of GSP firmware when a UPS was
connected to the UPS port an HPMC Would occur when the
GSP was reset with the "XD R" command, an stty reset
command or by pushing the reset button. Firmware revision
B.02.13 corrects this problem.
9. HP has identified a problem on the GSP, which manifests
itself in a number of different ways. Each symptom is
listed below separately in order to facilitate matching
the symptoms to problems experienced. The cause of these
symptoms is fixed with firmware revision B.02.13.
PDC Chassis Code 2083
Intermittent Alert Level 4 events occurring during power
on Selftest/PDC Initialization on L-Series systems with
the A6696B (Maestro GSP). The Alert Level 4 error would
look similar to this:
--------------------------------------------------------
SYSTEM NAME:
DATE: 11/29/2001 TIME: 16:22:52
ALERT LEVEL: 4 = Unexpected configuration change detected
REASON FOR ALERT
SOURCE: 8 = I/O
SOURCE DETAIL: 3 = local bus adapter SOURCE ID: FF
PROBLEM DETAIL: 3 = function failure
LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH OFF OFF OFF ON
LED State: Running non-OS code. (i.e. Boot or Diagnostics)
0x2000004383FF2083 000000FF FF05FF83 - type 4 = Physical
Location
0x5800084383FF2083 0000650A 1D101634 - type 11 =Timestamp
11/29/2001 16:22:52
---------------------------------------------------------
The most significant "signature" of this Alert/GSP Error
is the chassis code ending in "2083" (e.g.
0x2000004383FF2083). This chassis code is associated
with a PDC Selftest Entry Point of
"CC_IO_PM_NOT_RESPONDING_ERROR". Typically associated
with this Alert would be a "power off" of a PCI I/O slot
- with the I/O slot associated with the HPA address
correlating to the HPA address of the "Physical Location"
field of this chassis code.
EMS Event Code 32
The main symptom is the following EMS error event which
instructs the customer to reset the GSP or replace the
system board. This EMS error may be a recurring event
(in the worst case being logged once daily).
The EMS error will show up with this wording:
>---- Event Monitoring Service Event Notification ----<
Notification Time: Sun Dec 16 17:46:54 2001
niscit sent Event Monitor notification information:
/system/events/core_hw/core_hw is >= 3.
Its current value is SERIOUS(4).
Event data from monitor:
Event Time..........: Sun Dec 16 17:46:54 2001
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 32
System..............: niscit
EMS Event Code 31 or 36
An EMS error event similar to the one below which
instructs the customer to reset the GSP or replace the
Platform Monitor or System Board. Note that you
will receive an EMS 36 event for a system with a
"platform monitor" (A-class and L-class) and an EMS
event 31 for a system with a "power monitor" (N-class)
>---- Event Monitoring Service Event Notification ----<
Event Notification Time: Thu Feb 7 06:06:02 2002
jmcdb2 sent Event Monitor notification information:
/system/events/core_hw/core_hw is >= 1.
Its current value is SERIOUS(4).
Event data from monitor:
Event Time..........: Thu Feb 7 06:06:02 2002
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 36
System..............: jmcdb2
PDC 14c0 Chassis Code
Intermittent Alert Level 6 GSP errors similar to the one
below:
--------------------------------------------------------
SYSTEM NAME:
DATE: 01/29/2002 TIME: 09:47:14
ALERT LEVEL: 6 = Boot possible, pending failure - action
required
SOURCE: 8 = I/O
SOURCE DETAIL: 9 = serial SOURCE ID: 0
PROBLEM DETAIL: 3 = functional failure
CALLER ACTIVITY: 1 = test STATUS: 0
CALLER SUBACTIVITY: 4C = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING
ENTITY ID: 00
0x00000063890014C0 00000000 00000000 type 0 = Data Field
Unused
0x58000863890014C0 00006600 1D092F0E type 11 = Timestamp
01/29/2002 09:47:14
----------------------------------------------------------
Note! This same GSP Alert (14c0) message can also be
generated when the system console path is set ncorrectly.
The console path for the Maestro (A6696B) GSP is 0/0/4/1.
The console path for the Tosca (A6696A) GSP is 0/0/4/0.
If you experience this problem, verify the correct
console path setting first
Orphan Log Entries
One or more GSP Alert Level 12 events similar to the one
below:
--------------------------------------------------------
SYSTEM NAME:
DATE: 02/12/2002 TIME: 11:10:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: A = orphan log entry follows
CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 00 = unspecified
REPORTING ENTITY TYPE: 1 = service processor REPORTING
ENTITY ID: 00
0x581008CA11002000 00006601 0C0B0A28 type 11 = Timestamp
02/12/2002 11:10:40
Corrupt Log Entries
One or more GSP Alert Level 12 events similar to the one
below:
--------------------------------------------------------
SYSTEM NAME:
DATE: 02/12/2002 TIME: 11:10:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: A = corrupt log entries
CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 00 = unspecified
REPORTING ENTITY TYPE: 1 = service processor REPORTING
ENTITY ID: 00
0x581008CA11002000 00006601 0C0B0A28 type 11 = Timestamp
02/12/2002 11:10:40
Alert 10/2020 Chassis Code
Intermittent GSP Alert Level 10 errors when rebooting the
system multiple times (e.g. running a continuous power
on/off test that reboots the system over and over). The
GSP Alert will appear like this:
--------------------------------------------------------
Log Entry # 0 :
SYSTEM NAME: uninitialized
DATE: 02/05/2002 TIME: 06:38:50
ALERT LEVEL: 10 = Boot possible, functionality lost
SOURCE: 3 = PDH
SOURCE DETAIL: 6 = interconnect medium SOURCE ID: 0
PROBLEM DETAIL: 3 = non-responding, may need GSP reset.
CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 02 = platform internal interconnect
REPORTING ENTITY TYPE: 1 = service processor REPORTING
ENTITY ID: 00
0x581008A336002020 00006601 05062632 type 11 = Timestamp
02/05/2002
Alert 8/2030 Chassis Code
Intermittent GSP Alert Level 8 Error Log entries similar
to one or more of the events below. Note that the main
footprint signature in these GSP errors is a chassis
code ending in "2030" and unusual ACSII messages.
--------------------------------------------------------
SYSTEM NAME:
DATE: 02/17/2002 TIME: 19:46:53
ALERT LEVEL: 8 = Boot Possible, performance impaired
SOURCE: 6 = platform
SOURCE DETAIL: 6 = service processor SOURCE ID: 0
PROBLEM DETAIL: 1 = selftest result
CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 03 = console
REPORTING ENTITY TYPE: 1 = service processor REPORTING
ENTITY ID: 00
0x7010028166002030 0B0010FF 00000000 type 14 = Problem
Detail
0x4810028166002030 53415332 52616C70 type 9 = ASCII
Message SAS2Ralp
0x4810028166002030 7372632F 4C4F4765 type 9 = ASCII
Message src/LOGe
0x7010028166002030 0106013C 60000013 type 14 = Problem
Detail
0x58100A8166002030 00006601 11132E35 type 11 = Timestamp
02/17/2002 19:46:53
Defect Description:
PF_CCANGSPB0215:
- See Symptoms.
PF_CCANGSPB0214:
- See Symptoms.
PF_CCANGSPB0213:
- See Sypmtoms.
Enhancement:
No (superseded patches contained enhancements)
PF_CCANGSPB0213:
Added SSL authentication to the web access.
SR:
0000000000
Patch Files:
./B.02.15/B0215.bin
./B.02.15/Resources.out
./B.02.15/gsp_upg.cnf
./B.02.15/version.dat
./UpdateOnly/UpdateOnly2.bin
./UpdateOnly/gsp_a_upg.cnf
./UpdateOnly/gsp_upg.cnf
./UpdateOnly/mp_upg.cnf
cksum(1) Output:
177286403 2071288 ./B.02.15/B0215.bin
1537136308 504267 ./B.02.15/Resources.out
1550611892 200 ./B.02.15/gsp_upg.cnf
4278717776 16 ./B.02.15/version.dat
3208707489 447192 ./UpdateOnly/UpdateOnly2.bin
1177153808 97 ./UpdateOnly/gsp_a_upg.cnf
1177153808 97 ./UpdateOnly/gsp_upg.cnf
1177153808 97 ./UpdateOnly/mp_upg.cnf
Patch Conflicts: None
Patch Dependencies:
s800: 11.00: PHNE_27393 PHCO_27370
s800: 11.11: PHNE_26326 PHCO_27243
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PF_CCANGSPB0213 PF_CCANGSPB0214
Equivalent Patches: None
Patch Package Size: 1566 KBytes
Installation Instructions:
Please review all instructions and the "Hewlett-Packard
Support Tool License Terms" or your Hewlett-Packard support
terms and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
NOTE: It is important that you read and understand these
instructions completely before you begin. This can
determine your success in completing the Firmware update.
The Firmware update take no more than 5 minutes.
* * * * * * * * PREINSTALLATION ACTIVITIES * * * * * * * * * * * * * *
1. Insure operating system patches are installed to change the device
drivers prior to installing the firmware upgrade. These patches will
be required for any future releases of firmware. The list below
shows the patches required for 11.11 and 11.00
11.00
Console Driver Patch PHNE_27393
INSF Patch PHCO_27370
11.11
Console Driver Patch PHNE_26326
INSF Patch PHCO_27243
2. Stop any process communicating with the UPS port.
* * * * * * * * POST INSTALLATION ACTIVITIES * * * * * * * * * * * *
1. Shutdown the operating system.
2. Remove power to the system.
* * * * * * * * VERIFYING CURRENT REVISION OF FIRMWARE * * * * * * * *
1. telnet into the GSP.
2. logon to the GSP.
3. Type <CNTRL>ecf.
4. Type <CNTRL>b.
5. Type he
If the Revision number of the currently installed firmware is not
B.02.15 then install new firmware.
* * * * * * * * * * UNPACKING THE FIRMWARE * * * * * * * * * * * * * *
1. FTP "PF_CCANGSPB0215.tar.gz" to an empty directory.
2. Use the "gunzip" to unzip the patch.
# gunzip PF_CCANGSPB0215.tar.gz
3. Use the "tar" command to extract the firmware files
# tar -xvf PF_CCANGSPB0215.tar
x UpdateOnly/UpdateOnly2.bin, 447192 bytes, 874 tape blocks
x UpdateOnly/gsp_a_upg.cnf, 97 bytes, 1 tape blocks
x UpdateOnly/gsp_upg.cnf, 97 bytes, 1 tape blocks
x UpdateOnly/mp_upg.cnf, 97 bytes, 1 tape blocks
x B.02.15/B0215.bin, 2071288 bytes, 4046 tape blocks
x B.02.15/Resources.out, 504267 bytes, 985 tape blocks
x B.02.15/gsp_upg.cnf, 200 bytes, 1 tape blocks
x B.02.15/version.dat, 16 bytes, 1 tape blocks
4. Verify the checksum of the files in the B.02.15 directory
using the "cksum" command. Results of the command should be
equal to the following ouput.
# cksum ./B.02.15/*
177286403 2071288 ./B.02.15/B0215.bin
1537136308 504267 ./B.02.15/Resources.out
1550611892 200 ./B.02.15/gsp_upg.cnf
4278717776 16 ./B.02.15/version.dat
5. Verify the checksum of the files in the UpdateOnly directory
using the "cksum" command. Results of the command should be
equal to the following ouput.
# cksum ./UpdateOnly/*
3208707489 447192 ./UpdateOnly/UpdateOnly2.bin
1177153808 97 ./UpdateOnly/gsp_a_upg.cnf
1177153808 97 ./UpdateOnly/gsp_upg.cnf
1177153808 97 ./UpdateOnly/mp_upg.cnf
* * * * * * * * * * * FIRMWARE UPDATE PROCEDURE * * * * * * * * * * *
To update the firmware on the GSP, perform the following steps:
FTP the files to a system with the core I/O lan on the same subnet as the
GSP
1. Access the GSP using the ctrl+b command from the local console keyboard.
2. Ping the LAN where the GSP files are located via the XD command item #3
(LAN access PING)
-----------------------------------------------------------------------------
GSP> xd
XD
Non destructive tests :
1. Parameters checksum
2. I2C access (get Power Monitor status)
3. LAN access (PING)
4. Modem selftests
5. Secondary I2C access (get System status)
Type R to reset the GSP or [Q] to quit the diagnostic menu.
-> Choice: 3
3
Enter IP Address: 192.151.11.37/or your system (core I/O) LAN address
This test must pass on the server being used to supply the update files.
--------------------------------------------------------------------------------
3. Reset the GSP via the XD command (use the R option). This will free up any
unallocated memory for the GSP update.
--------------------------------------------------------------------------------
GSP> xd
XD
Non destructive tests :
1. Parameters checksum
2. I2C access (get Power Monitor status)
3. LAN access (PING)
4. Modem selftests
5. Secondary I2C access (get System status)
Type R to reset the GSP or [Q] to quit the diagnostic menu.
-> Choice: r
r
The GSP is now being reset...
--------------------------------------------------------------------------------
4. Select the GSP command XU. This command activates the upgrade mode.
Update the GSP firmware to the UpdateOnly2 firmware image in the
./UpdateOnly directory.
--------------------------------------------------------------------------------
GSP> xu
XU
This command activates the upgrade mode. All connections will be closed,the sess
ion
will be aborted and the modem connection will be dropped immediately, web and
telnet connections will be dropped upon completion. Please, confirm your intenti
on
to activate the upgrade mode (Y/[N]) : y
y
Enter source system IP address: 192.151.11.37/or your system (core I/O) LAN addr
ess
15.8.149.21
Enter file path: path on your system used to ftp files IE:/tmp/GSP
Do you wish to use the default login: anonymous / GSPhp.com (Y/[N]) :
y (if using docs.hp.com)
n (if using local server and local server login is needed).
IE: if root then supply root password
GSP> xu
-> GSP firmware upgrade in progressM-^E.
Retrieved an upgrade file sucessfully.
Programming ROM. Percent Complete: 100.
Retrieved an upgrade file sucessfully.
Programming ROM. Percent Complete: 100.
-> GSP firmware upgrade complete - Web and telnet connections will
be dropped. GSP will now reset....
Service Processor login:
Service Processor password:
--------------------------------------------------------------------------------
5. Repeat the firmware update process using the B.02.15 image in the
./B.02.15 directory
--------------------------------------------------------------------------------
1. Access the GSP using the ctrl+b command from the local console keyboard.
2. Ping the LAN where the GSP files are located via the XD command item #3
(LAN access PING)
-----------------------------------------------------------------------------
GSP> xd
XD
Non destructive tests :
1. Parameters checksum
2. I2C access (get Power Monitor status)
3. LAN access (PING)
4. Modem selftests
5. Secondary I2C access (get System status)
Type R to reset the GSP or [Q] to quit the diagnostic menu.
-> Choice: 3
3
Enter IP Address: 192.151.11.37/or your system (core I/O) LAN address
This test must pass on the server being used to supply the update files.
--------------------------------------------------------------------------------
6. Reset the GSP via the XD command (use the R option). This will free up any
unallocated memory for the GSP update.
--------------------------------------------------------------------------------
GSP> xd
XD
Non destructive tests :
1. Parameters checksum
2. I2C access (get Power Monitor status)
3. LAN access (PING)
4. Modem selftests
5. Secondary I2C access (get System status)
Type R to reset the GSP or [Q] to quit the diagnostic menu.
-> Choice: r
r
The GSP is now being reset...
--------------------------------------------------------------------------------
7. Select the GSP command XU. This command activates the upgrade mode.
Update the GSP firmware to the B.02.15 firmware image.
--------------------------------------------------------------------------------
GSP> xu
XU
This command activates the upgrade mode. All connections will be closed,the sess
ion
will be aborted and the modem connection will be dropped immediately, web and
telnet connections will be dropped upon completion. Please, confirm your intenti
on
to activate the upgrade mode (Y/[N]) : y
y
Enter source system IP address: 192.151.11.37/or your system (core I/O) LAN addr
ess
15.8.149.21
Enter file path: path on your system used to ftp files IE:/tmp/GSP
Do you wish to use the default login: anonymous / GSPhp.com (Y/[N]) :
y (if using docs.hp.com)
n (if using local server and local server login is needed).
IE: if root then supply root password
GSP> xu
-> GSP firmware upgrade in progressM-^E.
Retrieved an upgrade file sucessfully.
Programming ROM. Percent Complete: 100.
Retrieved an upgrade file sucessfully.
Programming ROM. Percent Complete: 100.
-> GSP firmware upgrade complete - Web and telnet connections will
be dropped. GSP will now reset....
Service Processor login:
Service Processor password:
After the GSP reset, use the HE command to ensure the firmware update was succes
sful.
--------------------------------------------------------------------------------
* * * * * * * * * * * * * * END OF UPDATE * * * * * * * * * * * * * *
-----End of Document ID: PF_CCANGSPB0215-------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]