| Document Audience: | INTERNAL |
| Document ID: | I0847-1 |
| Title: | Sun Fire 15K/12K failure logs must be returned |
| Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
| Update Date: | 2003-08-27 |
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)FIN #: I0847-1
Synopsis: Sun Fire 15K/12K failure logs must be returnedCreate Date: Jun/28/02
Keywords:
Sun Fire 15K/12K failure logs must be returned
SunAlert: No
Top FIN/FCO Report: No
Products Reference: Sun Fire 12K/15K
Product Category: Server / Service
Product Affected:
Systems Affected:
-----------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- F12K - Sun Fire 12000 -
- F15K - Sun Fire 15000 -
X-Options Affected:
-------------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- - - - -
Parts Affected:
Part Number Description Model
----------- ----------- -----
300-1413-08 Power Supply, 48v -
370-4055-06 Power Chassis -
501-4936-11 Logic Centerplane -
501-5121-13 System Controller Board -
501-5179-19 Expander Board -
501-5183-07 Power Centerplane -
501-5271-05 Fan Backplane -
501-5378-17 Centerplane Support Board -
501-5397-11 HsPCI Board -
501-5418-07 SC Peripheral Board -
501-5473-13 Nordica Board (CP1500) -
501-5599-07 3.3v Cassette -
501-5600-07 5.0v Cassette -
540-3883-03 Frame Manager -
540-4050-08 Fan Tray -
540-5051-03 CPU Board -
540-5052-03 CPU Board -
540-5799-04 CPU Board -
References:
N/A
Issue Description:
The F15K and F12K products have been designed to produce various
failure files (Domainstop/Recordstop, POST, Message, Console)
when a failure occurs. These files are necessary to successfully
debug and repair field returned F15K and F12K FRUs. If these files
are not provided, there is significant risk of returning incorrectly
repaired FRUs back into inventory, or having to scrap parts since they
cannot be diagnosed and repaired.
For all F15K/F12K Boards
------------------------
If the failure occurred prior to power-on, no files will be available.
It is only necessary to provide a complete description of the failure
symptom on the Defective Material Tag (DMT).
All SMS message files must be provided for any failure during "Set Key
Switch" (poweron, HPOST, OBP or Boot) or while running the customer
application.
The last three POST files, and the last three Domainstop or
Recordstop files, must be provided for any failure during HPOST,
OBP or Boot, or while running the customer application.
The Console Log files (all) must be provided for any failure
during OBP, or Boot, or while running the customer application.
For the F15K/F12K Power Supply, Fan Tray and Frame Manager:
-----------------------------------------------------------
Only provide the Message Files for any failure.
For the F15K/F12K Power Centerplane, Fan Backplane and Power Chassis:
------------------------------------------------------------
It is only necessary to provide a complete description of the
failure symptom on the Defective Material Tag (DMT).
This matrix summarizes the failure file requirements:
----------------------------------------------------------------------------
| FRU | WHEN FAILURE |DESCRIBE| PROVIDE | PROVIDE |PROVIDE LAST |PROVIDE|
| TYPE | OCCURS |FAILURE | MESSAGE |LAST THREE|THREE D-STOP,|CONSOLE|
| | | ON DMT | FILES |POST FILES|R-STOP FILES | LOG |
|========+================+========+=========+==========+=============+=======|
| Board |Prior to power- | X | | | | |
| |on | | | | | |
|--------+----------------+--------+---------+----------+-------------+-------|
| |During "Set Key | | | | | |
| Board |Switch", during | X | X | | | |
| |poweron | | | | | |
|--------+----------------+--------+---------+----------+-------------+-------|
| |During "Set Key | | | | | |
| Board |Switch", during | X | X | X | X | |
| |HPOST | | | | | |
|--------+----------------+--------+---------+----------+-------------+-------|
| |During "Set Key | | | | | |
| Board |Switch", during | X | X | X | X | X |
| |OBP, BOOT or | | | | | |
| |customer app. | | | | | |
|--------+----------------+--------+---------+----------+-------------+-------|
| Power | | | | | | |
| Supply,| | | | | | |
| Fan | Anytime | X | X | | | |
| Tray, | | | | | | |
| Frame | | | | | | |
| Manager| | | | | | |
|--------+----------------+--------+---------+----------+-------------+-------|
| Power | | | | | | |
| C/P, | | | | | | |
| Fan | Anytime | X | | | | |
| C/P, | | | | | | |
| Power | | | | | | |
|Chassis | | | | | | |
-----------------------------------------------------------------------------
The failure files are located in the following directories on
the F15K and F12K:
.SMS Message Files:
/var/opt/SUNWSMS/SMS/adm/platform/messages*
. POST Files:
/var/opt/SUNWSMS/SMS/adm//post/post
. Domainstop and Recordstop Files:
/var/opt/SUNWSMS/SMS/adm//dump/*
. Console Log Files:
/var/opt/SUNWSMS/SMS/adm//console
Please see the Corrective Action section below for instructions for
returning any failure files.Implementation:
---
| | MANDATORY (Fully Proactive)
---
---
| | CONTROLLED PROACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---Corrective Action:
The following recommendation is provided as a guideline for authorized
Enterprise Services Field Representatives who may encounter the above
mentioned problem.
When returning F15K and F12K FRUs which have functionally failed,
the appropriate files must be captured and sent to this alias:
[email protected]
Disregard early revisions of the F15K/F12K DMT (Defective Material
Tag) which indicate the files should be sent to SunSolve.
If you have any questions about these requirements, send an email
to [email protected].Comments:
None
============================================================================
Implementation Footnote:
i) In case of MANDATORY FINs, Enterprise Services will attempt to
contact all affected customers to recommend implementation of
the FIN.
ii) For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical
support teams will recommend implementation of the FIN (to their
respective accounts), at the convenience of the customer.
iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the
need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network
browser as follows:
SunWeb Access:
--------------
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Corp/
* From there, select the appropriate link to browse the FIN or FCO index.
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to [email protected]
--------------------------------------------------------------------------