NEOHAPSIS - Peace of Mind Through Integrity and Insight

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com

Neohapsis > Archives > HP/HP-UX Digests> 2003-q2

all firmware patch digest

From: IT Resource Center (support_feedbackus-support2-mail.external.hp.com)
Date: Sun May 25 2003 - 07:19:08 CDT

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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:

http://support.itrc.hp.com/

   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:

http://support.itrc.hp.com/

   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 May 25 7:05:02 EDT 2003

Table of Contents:

Document ID Title
--------------- -----------
PF_CCANGSPB0220 A6696B GSP firmware B.02.20
PF_CHARGSPC0214 rp24xx revision B GSP firmware C.02.14

The documents are listed below.
-------------------------------------------------------------------------------

Document ID: PF_CCANGSPB0220
Date Loaded: 20030519
Title: A6696B GSP firmware B.02.20

Patch Name: PF_CCANGSPB0220

Patch Description: A6696B GSP firmware B.02.20

Creation Date: 02/11/15

Post Date: 03/05/19

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_CCANGSPB0220

Symptoms:
        PF_CCANGSPB0220:
        The Following enhancement and fixes are included in GSP
        firmware revision B.02.20

        ************************************************************
        The Java plug-in 1.4x is not supported with Web Access. Java
        plug-in 1.3x is supportted.
        ************************************************************

1- Run LED is displayed OFF after "System Boot detected"

In previous revisions of gsp firmware the front panel RUN
led did not always flash and would instead appear to be off.

        The following is the correct display from the Vitual Font
        Panel.
        ********** VIRTUAL FRONT PANEL **********
        System Boot detected
        *****************************************
        LEDs: RUN ATTENTION FAULT REMOTE POWER

        The following is a sample incorrect display from the Virtual
        Front Panel.
        ********** VIRTUAL FRONT PANEL **********
        System Boot detected
        *****************************************
        LEDs: RUN ATTENTION FAULT REMOTE POWER
               OFF FLASH OFF ON ON

B.02.20 has been modified to correct this issue.

2 - LAN hangs when gateway address matches GSP's own IP
address.

        In previous revisionss of GSP firmware When GSP's gateway
        address and ip address matched and the LAN hung the firmware
        pinged the gateway address to dectect if a real hang
        occured. If the gateway and ip addresses were the same, the
        ping always return OK status incorrectly indicating that
        the LAN is active. As a result the LAN would not
        reinitialize, leaving the LAN indefinitely in a hang state.

        B.02.20 firmware checks the gateway IP is checked against
        the GSP IP before attempting to ping gateway. If the gateway
        and IP match then the broadcast address is pinged instead.

3 - GSP denies CTRL-Ecf access

        During extremely high traffic on the I2C bus CTRL-Ecf did
        not work properly and Write access to the GSP would not
        be granted.The serial port connection continued to work and
        the OS was not affected. This issue was corrected with GSP
        firmware revision B.02.20.

4 - Data aborts caused by CRC invalid Voice packets.

        In previous revisions of GSP firmware the checksum
        verication result on i2c Voice messages is ignored when
        returning to upper level calling routines. If the length
        byte in the Voice message is corrupted this will result
        later in a data abort, when the message is copied to a
        secondary location for processing. The following is a
        sample error chassis code:

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 proc REPORTING ID: 00

        0x7010028166002030 0B0010FF 00000000 type 14
        0x4810028166002030 63436870 6C615266 type 9 fRalphCc
        0x4810028166002030 65474F4C 2F637273 type 9 src/LOGe
        0x7010028166002030 0102476C 60000013 type 14
        0x58100A8166002030 00006504 02143B2F type 11

GSP fimrware revision B.02.20 checks the message type and
length of incoming I2C packets to prevent the issue.

5 - Local port dropping characters on input

        Previous revisions of GSP firmware dropped characters during
        heavy input. To eliminate the issue GSP firmware revision
        B.02.20 establishes a pacing scheme based on hardware timers
        preventing the issue.

6 - Added support for SNMP.

        PF_CCANGSPB0217:
        The Following enhancement and fixes are included in GSP
        firmware revision B.02.17

        In previous revisions of GSP frimware the modem did not
        consistently connect. After multiple connection the GSP
        would not recognize the carrier. GSP firmware revision
        B.02.20 corrects this problem.

        Long packets on the I2C bus potentially causing system
        shutdown. The following information describes the issue in
        detail.

        Problem Details
        ************************************************************
        1) Sudden and unexpected system reboots. Depending on the
        setting of the Autoboot flag, the system will either reboot
        to HP-UX or will reset to Boot Command Handler (BCH) for no
        apparent reason. There will be nothing in the
        /var/tombstones directory (e.g. no HPMC events), no evidence
        of an OS panic or any core files showing a panic core dump,
        nothing in the OS logs (e.g. dmesg, syslog, shutdown logs,
        etc.), and nothing obvious in the GSP's Error or Activity
        Logs showing the reason for the reboot event(s).

        2) Sudden and unexpected DC Power system shutdowns. In this
        case, the main customer symptom will be that the system is
        "hung" or non-responsive. The front panel "Power" LED will
        be flashing GREEN - indicating that the system is running on
        DC Standby voltages. Recycling the front DC Power Switch to
        off and on positions will restore the DC power and the
        system will reboot normally. Alternatively, turning the DC
        power back on via the GSP's "PC" command will also typically
        restore the DC power and will allow the system to reboot.
        Again, there will not be any GSP Errors showing the apparent
        reason for the DC power subsystem shutting down.

        Problem symptoms
        ************************************************************
        The best way to explain how to determine that your N or
        L-Class system is indeed experiencing this problem is to
        describe when it is NOT experiencing this problem.

        1) The system will typically NOT be experiencing a "solid"
        problem. In other words, it will typically NOT be rebooting
        every time the OS is booted or reboot very frequently after
        the OS is fully operational.

2) The system will typically NOT shutdown to DC standby
voltages and refuse to power back on or remain powered on.

        3) There will NOT be any obvious DC Power problems logged
        in the GSP Error Logs (i.e. there will NOT be any Alert
        Level 14 error events due to Undervoltage or Overvoltage
        failures).

        4) There will NOT be any obvious reasons in the GSP Error
        Logs or Activity Logs indicating any reason for the system
        to reboot (e.g. no Alert Level 12 "panics", or any HPMC
        events logged). Note: There MAY be alerts that look like
        the following events - which are due to a Transfer of
        Control (TOC) operation being performed and these log
        entries are not to be confused with actual HPMC events. A
        TOC event should NOT be considered the root cause of this
        unexpected reboot problem.

Typical "TOC" GSP events:
************************************************************

        0 PDC 0,0,0 *2 12/09/2002 18:14:41
        Log Entry 0: 12/09/2002 18:14:41
        Alert Level 2: Non-urgent alert or error; Keyword:
        Status: 2
        Logged by system firmware 0 during machine check subAct. 51
        0x0000022000ff6512 0x0000000000000000
        0x58000a2000ff6512 0x0000660909120e29

        1 PDC 0,0,0 *2 12/09/2002 18:14:41
        Log Entry 1: 12/09/2002 18:14:41
        Alert Level 2: Non-urgent alert or error; Keyword:
        Status: 2
        Logged by system firmware 0 during machine check subAct. 53
        0x0000032000ff6532 0x0000000000000000
        0x58000b2000ff6532 0x0000660909120e29

        Typical L3000 GSP Chassis Code "Footprints"
        ************************************************************
        What WILL typically be logged by the GSP MAY differ between
        N-Class and L-Class systems. A typical L3000 failure
        signature may look like this in the GSP Activity Logs:

        Log Entry # 0 :
        SYSTEM NAME: HP000001
        DATE: 12/19/2002 TIME: 14:01:41
        ALERT LEVEL: 1 = Information only, no action required
        SOURCE: 1 = processor
        SOURCE DETAIL: 1 = processor general SOURCE ID: 0
        PROBLEM DETAIL: 0 = no problem detail
        CALLER ACTIVITY: C = system initialization STATUS: 0
        CALLER SUBACTIVITY: 00 = implementation dependent
        REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
        0xA0E000101100C000 00000000 000007E1
        0x58E008101100C000 00006608 130E0129

        Log Entry # 1 :
        SYSTEM NAME: HP000001
        DATE: 12/19/2002 TIME: 13:57:20
        ALERT LEVEL: 1 = Information only, no action required
        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 ENTITY ID: 00
        0xF010011166002030 00000000 00000000
        0x5810091166002030 00006608 130D3914

        Log Entry # 2 :
        SYSTEM NAME: HP000001
        DATE: 12/19/2002 TIME: 13:57:20
        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 ID: 00
        0x581008A336002020 00006608 130D3914

        ************************************************************
        This appears to show an Alert Level 10 "Platform Medium Not
        Responding" followed by a GSP Selftest Reset followed by a
        "Major Change In System State" due to HPUX Initialization.

        In some cases, the error only shows up as the following GSP
        Chassis Code sequence - which simply shows the system
        rebooting:
        ************************************************************

        0 PDC 0,0,0 1 12/09/2002.20:30:32
        Log Entry 0: 12/09/2002.20:30:32
        Alert Level 1: Forward progress, no failure; Keyword:
        Platform 0 ; Status: 0
        Logged by firmware 0 during configuration subActivity 6f
        System state change: Booting

        LEDs : RUN: FLASHING green; ATTENTION: OFF yellow;
                                                STOP: RESERVED red
        0xa0000310600026f0 0x0000000000000710
        0x58000b10600026f0 0x0000660909111e20

        1 PDC 0,0,0 1 12/09/2002.20:30:32
        Log Entry 1: 12/09/2002.20:30:32
        Alert Level 1: Forward progress, no failure; Keyword:
        Processor 0 installed; Status: 2
        Logged by system firmware 0 during test subActivity 0
        0x0000051c11001002 0x0000000000000000
        0x58000d1c11001002 0x0000660909111e20

************************************************************
Typical N4000/rp7400 GSP Chassis Code "Footprint"

        The N4000/rp7400 system's GSP Logs typically only shows the
        following entries:
        ************************************************************

        0 HPUX 0,0,1 *13 12/04/2002 14:54:19
        Log Entry 0: 12/04/2002 14:54:19
        Alert Level 13: System hang detected; Keyword:
        Processor 0 timeout; Status: 0
        Logged by HP-UX 1 during display_activity update subAct 0
        Activity Level/Timeout: 0% / Timer expired
        0x78e017d41100f000 0x0000000300000000
        0x58e01fd41100f000 0x00006609040e3613

        1 PDC 0,0,1 1 12/04/2002 14:59:21
        Log Entry 1: 12/04/2002 14:59:21
        Alert Level 1: Forward progress, no failure; Keyword:
        Platform 0 ; Status: 0
        Logged by firmware 1 during configuration subActivity 6f
        System state change: Booting
        LEDs : RUN: FLASHING green; ATTENTION: OFF yellow;
                                                STOP: RESERVED red
        0xa0001710600026f0 0x0000000000000710
        0x58001f10600026f0 0x00006609040e3b15

        2 PDC 0,0,1 1 12/04/2002 14:59:22
        Log Entry 2: 12/04/2002 14:59:22
        Alert Level 1: Forward progress, no failure; Keyword:
        Processor 0 deinstalled; Status: 2
        Logged by system firmware 1 during test subActivity 0
        0x0000151d11001002 0x0000000000000000
        0x58001d1d11001002 0x00006609040e3b16

        ************************************************************
        Another possible chassis code "footprint" would be this
        Alert Level 13 Error:
        ************************************************************
        Log Entry # 5 :
        SYSTEM NAME: HP000001
        DATE: 12/15/2002 TIME: 06:06:48
        ALERT LEVEL: 13 = System hang detected via timer popping

        SOURCE: 6 = platform
        SOURCE DETAIL: 7 = power monitor SOURCE ID: 0
        PROBLEM DETAIL: 4 = internal failure

        CALLER ACTIVITY: 1 = initialization STATUS: F
        CALLER SUBACTIVITY: 01 = self
        REPORTING ENTITY TYPE: 2 = power monitor ID: 00

0x002000D46700101F 00000000 00000000
0x582008D46700101F 00006608 0F060630

************************************************************

        There may or may not always be an Alert Level 13 event
        logged and in those cases the only typical indication of the
        reboot condition will typically be the Alert Level 1 "System
        stage change: Booting" logged by "system firmware" as is
        shown in log event #1 above.

        In many cases where there is nothing very obvious in the GSP
        Error or Activity Logs,there might be a bit more information
        in the OS Chassis Code Logs. These logs can be gathered in 2
        ways:

        1) Via the "cclogview" utility. This utility, if it is
        installed on the system, will format the OS Chassis Code
        logs into English and the output can be redirected to an
        ASCII file for analysis or emailing as follows:

" cclogview /var/stm/logs/os/ccerrlog > test"
[you can substitute any desired filename for "test" here]

        2) Via STM's (CSTM or MSTM or XSTM) LOGTOOL "Chassis / View
        Error Log" utility. When using LOGTOOL to gather this data,
        be sure to specify "DETAILS" to get the detailed chassis
        code data.

        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.20/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.20/2002 19:46:53

Defect Description:
PF_CCANGSPB0220:
- See Symptoms.

PF_CCANGSPB0217:
- See Symptoms.

PF_CCANGSPB0215:
- See Symptoms.

PF_CCANGSPB0214:
- See Symptoms.

PF_CCANGSPB0213:
- See Sypmtoms.

Enhancement:
        Yes
        PF_CCANGSPB0220:
        - See Symptoms.

SR:
0000000000

Patch Files:
        B0220.bin
        Resources.out
        gsp_upg.cnf
        version.dat

cksum(1) Output:
        863102829 2175924 B0220.bin
        1537136308 504267 Resources.out
        3789819483 200 gsp_upg.cnf
        4278717776 16 version.dat

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 PF_CCANGSPB0215 PF_CCANGSPB0217

Equivalent Patches: None

Patch Package Size: 1173 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.

                Warning:If the currently installed firmware is older than
                B.02.15 then updating to GSP firmware revision B.02.20
                requires updating to B.02.15 first. B.02.15 is located at
                the following URL:
                ftp://us-ffs.external.hp.com/superseded_patches
                        /firmware_patches/hp/cpu/PF_CCANGSPB0215.tar.gz

The Firmware update take no more than 5 minutes.

* * * * * * * * 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.20 then install new firmware.

* * * * * * * * * * UNPACKING THE FIRMWARE * * * * * * * * * * * * * *

1. FTP "PF_CCANGSPB0220.tar.gz" to an empty directory.

2. Use the "gunzip" to unzip the patch.

# gunzip PF_CCANGSPB0220.tar.gz

3. Use the "tar" command to extract the firmware files

                # tar -xvf *tar
                x B0220.bin, 2175924 bytes, 4250 tape blocks
                x Resources.out, 504267 bytes, 985 tape blocks
                x gsp_upg.cnf, 200 bytes, 1 tape blocks
                x version.dat, 16 bytes, 1 tape blocks

                   4. Verify the checksum of the files in the temporary directory
                       using the "cksum" command. Results of the command should be
                       equal to the following ouput.

                        # cksum *
                        863102829 2175924 B0220.bin
                        1537136308 504267 Resources.out
                        3789819483 200 gsp_upg.cnf
                        4278717776 16 version.dat

        * * * * * * * * * * * 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

        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

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 B.02.20 firmware image.
        --------------------------------------------------------------------------------
        GSP> 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

        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.

-> GSP firmware upgrade complete - Web and telnet connections will
be dropped. GSP will now reset....

Service Processor login:
Service Processor password:

* * * * * * * * * * * * * * END OF UPDATE * * * * * * * * * * * * * *
-----End of Document ID: PF_CCANGSPB0220-------------------------------------

Document ID: PF_CHARGSPC0214
Date Loaded: 20030519
Title: rp24xx revision B GSP firmware C.02.14

Patch Name: PF_CHARGSPC0214

Patch Description: rp24xx revision B GSP firmware C.02.14

Creation Date: 03/05/01

Post Date: 03/05/19

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_CHARGSPC0214

Symptoms:
        PF_CHARGSPC0214:
        The Following enhancement and fixes are included in GSP
        firmware revision C.02.14

1- Run LED is displayed OFF after "System Boot detected"

In previous revisions of gsp firmware the front panel RUN
led did not always flash and would instead appear to be off.

C.02.14 has been modified to correct this issue.

2 - LAN hangs when gateway address matches GSP's own IP
address.

        C.02.14 firmware checks the gateway IP is checked against
        the GSP IP before attempting to ping gateway. If the gateway
        and IP match then the broadcast address is pinged instead.

3 - GSP denies CTRL-Ecf access

4 - Data aborts caused by CRC invalid Voice packets.

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 proc ID: 00

GSP fimrware revision C.02.14 checks the message type and
length of incoming I2C packets to prevent the issue.

5 - Local port dropping characters on input

        Previous revisions of GSP firmware dropped characters during
        heavy input. To eliminate the issue GSP firmware revision
        C.02.14 establishes a pacing scheme based on hardware timers
        preventing the issue.

6 - Added support for SNMP.

        PF_CHARGSPC0212:
        The following enhancements and fixes are included in
        GSP firmware revision C.02.12

        In previous revisions of GSP frimware the modem did not
        consistently connect. After multiple connection the GSP
        would not recognize the carrier. GSP firmware revision
        C.02.12 corrects this problem.

        Long packets on the I2C bus potentially causing system
        shutdown. The following information describes the issue in
        detail.

2) The system will typically NOT shutdown to DC standby
voltages and refuse to power back on or remain powered on.

Typical "TOC" GSP events:
************************************************************

        0 PDC 0,0,0 1 12/09/2002 17:30:32
        Log Entry 0: 12/09/2002 17:30:32
        Alert Level 1: Forward progress, no failure; Keyword:
        Platform 0 ; Status: 0
        Logged by firmware 0 during configuration subActivity 6f
        System state change: Booting

        1 PDC 0,0,0 1 12/09/2002 17:30:32
        Log Entry 1: 12/09/2002 17:30:32
        Alert Level 1: Forward progress, no failure; Keyword:
        Processor 0 installed; Status: 2
        Logged by system firmware 0 during test subActivity 0
        0x0000051c11001002 0x0000000000000000
        0x58000d1c11001002 0x0000660909111e20

************************************************************
Typical N4000/rp7400 GSP Chassis Code "Footprint"

        The N4000/rp7400 system's GSP Logs typically only shows the
        following entries:
        ************************************************************

        SOURCE: 6 = platform
        SOURCE DETAIL: 7 = power monitor SOURCE ID: 0
        PROBLEM DETAIL: 4 = internal failure

        CALLER ACTIVITY: 1 = initialization STATUS: F
        CALLER SUBACTIVITY: 01 = self
        REPORTING ENTITY TYPE: 2 = power monitor ID: 00

0x002000D46700101F 00000000 00000000
0x582008D46700101F 00006608 0F060630

************************************************************

" cclogview /var/stm/logs/os/ccerrlog > test"
[you can substitute any desired filename for "test" here]

        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.

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

LED State: Running non-OS code. (i.e. Boot or Diagnostics)
0x2000004383FF2083 000000FF FF05FF83 - type 4 = Physical

EMS Event Code 32

>---- 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

>---- 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).

PDC 14c0 Chassis Code

Intermittent Alert Level 6 GSP errors similar to the one
below:

Orphan Log Entries

One or more GSP Alert Level 12 events similar to the one
below:

        --------------------------------------------------------
        SYSTEM NAME:
        DATE: 02.14/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.14/2002 11:10:40

Corrupt Log Entries

One or more GSP Alert Level 12 events similar to the one
below:

        --------------------------------------------------------
        SYSTEM NAME:
        DATE: 02.14/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.14/2002 11:10:40

Alert 10/2020 Chassis Code

        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

        --------------------------------------------------------
        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_CHARGSPC0214:
- See Symptoms.

PF_CHARGSPC0212:
- See Symptoms.

PF_CHARGSPC0210:
- See Symptoms.

PF_CHARGSPC0209:
- See Symptoms.

PF_CHARGSPC0208:
- See Sypmtoms.

Enhancement:
        Yes
        PF_CHARGSPC0214:
        - See Symptoms.

SR:
0000000000

Patch Files:
        C0214.bin
        Resources.out
        gsp_a_upg.cnf
        version.dat

cksum(1) Output:
        3495409698 2173644 C0214.bin
        1537136308 504267 Resources.out
        2488838608 200 gsp_a_upg.cnf
        4278717776 16 version.dat

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 PF_CHARGSPC0210 PF_CHARGSPC0212

Equivalent Patches: None

Patch Package Size: 1172 KBytes

                Warning:If the currently installed firmware is older than
                C.02.10 then updating to GSP firmware revision C.02.14
                requires updating to C.02.10 first. C.02.10 is located at
                the following URL:
                ftp://us-ffs.external.hp.com/superseded_patches
                        /firmware_patches/hp/cpu/PF_CHARGSPC0210.tar.gz

The Firmware update take no more than 5 minutes.

* * * * * * * * 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.14 then install new firmware.

* * * * * * * * * * UNPACKING THE FIRMWARE * * * * * * * * * * * * * *

1. FTP "PF_CHARGSPC0214.tar.gz" to an empty directory.

2. Use the "gunzip" to unzip the patch.

# gunzip PF_CHARGSPC0214.tar.gz

3. Use the "tar" command to extract the firmware files

                # tar -xvf *tar
                x C0214.bin, 2173644 bytes, 4246 tape blocks
                x Resources.out, 504267 bytes, 985 tape blocks
                x gsp_a_upg.cnf, 200 bytes, 1 tape blocks
                x version.dat, 16 bytes, 1 tape blocks

                   4. Verify the checksum of the files in the temporary directory
                       using the "cksum" command. Results of the command should be
                       equal to the following ouput.

                        # cksum *
                        3495409698 2173644 C0214.bin
                        1537136308 504267 Resources.out
                        2488838608 200 gsp_a_upg.cnf
                        4278717776 16 version.dat

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.
--------------------------------------------------------------------------------

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 C.02.10 firmware.
        --------------------------------------------------------------------------------
        GSP> 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

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

GSP> xu

-> GSP firmware upgrade in progress.

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:

* * * * * * * * * * * * * * END OF UPDATE * * * * * * * * * * * * * *
-----End of Document ID: PF_CHARGSPC0214-------------------------------------

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]