Sun Fire 6800 Server
 
Sun Fire E6900 Server
 
Sun Fire 4800 Server
 
Sun Fire E4900 Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-x8x0/Ex900
 
_Old GCS Categories>Sun Microsystems>Servers>Midrange Servers
 

Applies to:

Goal

System Controllers on Sun Fire[TM] 4[89]00-6[89]00 platforms employing ScApp firmware revision 5.20.X may encounter the following symptoms when initiating keyswitch operations:

This document address how to fix this issue

Fix

This issue can occur in the following releases :

• Sun Fire 4800/6800 E4900/E6900 with firmware 5.20.0 / RTOS 45 (patch 114527-01) or greater

To identify the current System Controller firmware version, use the "showsc -v" command from the platform shell.


The primary suspect candidate originating the above ScApp logs is a condition whereby the serial ID read off the Seprom differs from
the serial ID read from JTAG ..
i.e., Seprom's serial no. is not equal to JTAG serial no.

Considerations:

1. Although the ScApp platform logs flagged the 'need' to update cpu speed property via the ScApp engineering mode command sepromupdate,
    it is consistently observed from the output reported off ScApp platform shell's "showboards -v" command that the speed properties
    of the system board concerned was in fact as expected :


    i.e.,

    "showboards -v" correctly reports SB4's resident CPUs' speed properties :

    /N0/SB4/P0 2.3 UltraSPARC-IV, 1200MHz, 16M ECache
    /N0/SB4/P1 2.3 UltraSPARC-IV, 1200MHz, 16M ECache
    /N0/SB4/P2 2.3 UltraSPARC-IV, 1200MHz, 16M ECache
    /N0/SB4/P3 2.3 UltraSPARC-IV, 1200MHz, 16M ECache


2. The system boards flagged by ScApp for "CPU Serial number mismatch" are likely to SBs based on the USIV or USIV+ CPU procs


3. A large number of such "CPU Serial number mismatch" events are in fact transient in nature : i.e,
    Upon a power-cycle to the system board concerned ( i.e., keyswitch off / on to the domain ), the same "CPU Serial number mismatch"
    error condition is no longer reproducable.
    In fact, for the majority of such cases, the same "CPU Serial number mismatch" condition cannot be reliably reproduced on platforms
    which had previously logged the same messages to the ScApp platform logs .



In conclusion, a consistently reproducable "CPU Serial number mismatch" error condition
( i.e., error is persistent through multiple keyswitch operations ) could indicate an inconsistency between the serial number
programmed to JTAG vs that defined in the Seprom.
This serial ID inconsistency could potentially affect the way ScApp interprets CPU core voltage settings for the CPUs flagged for the
"CPU Serial number mismatch" condition and will very likely warrant the system board's replacement.

Hence, if the error is consistently reproducible after several keyswitch, replace the SB.

Note: the sepromupdate command in the error is available in escalation mode. Anyway it will not work and will give an error

Product
Sun Fire 6800 Server
Sun Fire E6900 Server
Sun Fire E4900 Server
Sun Fire 4800 Server

See CR 6505783

This solution has no attachment