Document Audience: | INTERNAL |
Document ID: | I1079-1 |
Title: | Fan failures on SunFire B1600 (B100s and B100x Server blades) can cause the fan speed falls below critical threshold. |
Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
Update Date: | 2004-07-20 |
------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
------------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by Sun Services)
FIN #: I1079-1
Synopsis: Fan failures on SunFire B1600 (B100s and B100x Server blades) can cause the fan speed falls below critical threshold.Create Date: Mar/30/04
SunAlert: No
Top FIN/FCO Report: No
Products Reference: Sun Fire B1600 Servers
Product Category: Server / Diag-Doc-Service
Product Affected:
Systems Affected:
-----------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- A44 ALL Sun Fire B1600 Server -
X-Options Affected:
-------------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
X7501A - - ASSY BLADE 2X512MB 30GB STLO -
X7502A - - ASSY BLADE 1X512MB 30GB STLO -
X7503A - - ASSY BLADE 2X1GB 30GB STLO -
X7511A - - SF B100x X86 Blade 512MB -
X7512A - - SF B100x X86 Blade 1GB -
X7513A - - SF B100x X86 Blade 2GB -
Parts Affected:
----------------------
Part Number Description Model
----------- ----------- -----
540-5454-06 or below ASSY BLADE 2X1GB 30GB STLO -
540-5078-06 or below ASSY BLADE 1X512MB 30GB STLO -
540-5079-06 or below ASSY BLADE 2X512MB 30GB STLO -
540-5547-03 or below ASSY BLADE 512MB 30GB SCM1P -
540-5548-03 or below ASSY BLADE 1GB 30GB SCM1P -
540-5549-03 or below ASSY BLADE 2GB 30GB SCM1P -
540-5860-03 or below ASSY GEN BLADE 0MB 30GB SCM1P -
References:
ESC: 549378 - Multiple B100S CPU fan failure.
549061 - Sun Fire B1600:CPU Fan speed below critical threshold.
547981 - SF B100 blades w/major network trbl & low fan speed.
Issue Description:
------------------------------------------------------------------------
| Change of History: |
| ================== |
| Updated Date: Jul/20/04 |
| |
| Updated Sections: Issue Descriptoin, Corrective Action |
| |
| . ISSUE DESCRIPTION: |
| Minor change at the bottom of the Issue Description due |
| to availability of the FCO A0236-1 |
| |
| . CORRECTIVE ACTION: |
| has been changed from: |
| Currently engineering is working on a fix for this fan issue, |
| which should be available in Q4FY04. Until this fix is |
| available, the field is advised to perform the following steps:|
| |
| 1. Check the console for fan speed messages similar to the |
| following; |
| |
| Nov 19 08:34:28: CRITICAL: S12: CPU Fan speed below |
| critical threshold. |
| |
| 2. If a fan speed error message has been detected, contact |
| PTS for further investigation and guidelines. When |
| contacting PTS provide the output from all of the |
| following commands: |
| |
| . showplatform -v |
| . showenvironment -v |
| . showfru s# |
| |
| PTS will analyze the outputs from these commands and assist |
| you on how to procede the impacted system running. Since |
| there has been no reported cases of a blade overheating after |
| experiencing a fan speed error message, the affected system |
| can continue running under the direction of PTS or engineering.|
| |
| To: |
| Engineering now has developed a fix for this fan issue, which |
| uses a fan from a different supplier. If the above problem |
| is encountered, FCO A0236-1 should be implemented. |
------------------------------------------------------------------------
Fan failures may occur on Sun Fire B100s and Sun Fire B100x Server
blades causing fan speed to fall below the critical threshold. When
this occurs it requires a service operation to replace the CRU
(blade). The CPU/Fans typically begin reporting fault messages between
4 to 6 months after installation.
All the Sun Fire B100s and B100x blades are susceptible to this failure
mode as the CPU cooling fan is a common part. The system will detect
the fan speed falling below the critical threshold (70% of max.) and a
warning message will be displayed. There are no specific
user/environmental conditions which contribute to this failure mode.
The following is an example of the error message that will be displayed
on the Sun Fire B1600 System Controller console, and in the Console Log
when a fan is experiences this issue.
Nov 19 08:34:28: CRITICAL: S12: CPU Fan speed below critical threshold.
Type "showenvironment -v" at the Sun Fire B1600 Shelf System
Controller Prompt. The following is an example of part of the output
including defective blades indications:
--------------------------------------------------------------
| System | Fans (RPM) | Current | Status | Warning |
|===========+=================+===========+=========+==========|
| S0 | /fan/cpu_fan | 100% | OK | 66% |
| S1 | /fan/cpu_fan | 100% | OK | 66% |
| S2 | /fan/cpu_fan | 100% | OK | 66% |
| S3 | /fan/cpu_fan | 0% | Fault | 66% |
| S4 | /fan/cpu_fan | 100% | OK | 66% |
| S5 | /fan/cpu_fan | 100% | OK | 66% |
| S6 | /fan/cpu_fan | 100% | OK | 66% |
| S7 | /fan/cpu_fan | 100% | OK | 66% |
| S8 | /fan/cpu_fan | 0% | Fault | 66% |
| S9 | /fan/cpu_fan | 100% | OK | 66% |
| S10 | /fan/cpu_fan | 100% | OK | 66% |
| S11 | /fan/cpu_fan | 100% | OK | 66% |
| S12 | /fan/cpu_fan | 100% | OK | 66% |
| S13 | /fan/cpu_fan | 0% | Fault | 66% |
| S14 | /fan/cpu_fan | 100% | OK | 66% |
| S15 | /fan/cpu_fan | 0% | Fault | 66% |
--------------------------------------------------------------
NOTE: In the example above the fans on blades S3, S8, S13 and S15 are
shown as faulty.
Collection of field failure information to quantify exposure and risk is
ongoing.
The actual cause of the fan failure remains unidentified, however, it
is believed that the fans are reporting these errors due to a defect
within the bearing mechanism on the fan. However, the fan vendor is
unable to identify what is contributing to the accelerated error rate.
Engineering has completed qualification of a fan from a second supplier
and this fan will be introduced into the product and will be made
available to the field under FCO A0236-1.
The intent of this FIN is to inform the field of this issue, and to
provide recommendations as listed in the Corrective Action section of
this document.
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
Sun Services Field Representatives who may encounter the above
mentioned issue.
Engineering now has developed a fix for this fan issue, which uses
a fan from a different supplier. If the above problem is encountered,
FCO A0236-1 should be implemented.
Comments:
None.
============================================================================
Implementation Footnote:
i) In case of MANDATORY FINs, Sun Services will attempt to contact
all affected customers to recommend implementation of the FIN.
ii) For CONTROLLED PROACTIVE FINs, Sun 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, Sun 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.central/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.central/
* From there, select the appropriate link to browse the FIN or FCO index.
Internet Access:
----------------
* Access the top level URL of https://spe.sun.com
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
--------------------------------------------------------------------------