T1000故障-请大家帮忙看看，谢谢！
T1000故障-请大家帮忙看看，谢谢！现在有一台T1000报黄灯，但是系统运行正常，个人感觉是PS或者MB问题，请大家帮忙判断一下，非常感谢！下面是收集的一些信息：
root@sunt1000-4 # prtdiag -v|more
System Configuration:Sun Microsystemssun4v Sun Fire(TM) T1000
System clock frequency: 200 MHz
Memory size: 16376 Megabytes
========================= CPUs ===============================================
CPU CPU
Location CPU Freq Implementation Mask
------------ ----- -------- ------------------- -----
MB/CMP0/P0 0 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P1 1 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P2 2 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P3 3 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P4 4 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P5 5 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P6 6 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P7 7 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P8 8 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P9 9 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P1010 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P1111 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P1212 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P1313 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P1414 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P1515 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P1616 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P1717 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P1818 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P1919 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P2020 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P2121 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P2222 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P2323 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P2424 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P2525 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P2626 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P2727 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P2828 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P2929 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P3030 1000 MHz SUNW,UltraSPARC-T1
MB/CMP0/P3131 1000 MHz SUNW,UltraSPARC-T1
========================= IO Configuration =========================
IO
Location TypeSlot Path Name
Model
----------- ----- ---- --------------------------------------------- -----------
-------------- ---------
MB/PCIE0 PCIE 0 /pci@780/SUNW,qlc@0 SUNW,qlc-
pciex1077,2432QLE2462
MB/PCIE0 PCIE 0 /pci@780/SUNW,qlc@0,1 SUNW,qlc-
pciex1077,2432QLE2462
MB/NET0 PCIE MB /pci@7c0/pci@0/network@4 networ
k-pci14e4,1668
MB/NET1 PCIE MB /pci@7c0/pci@0/network@4,1 networ
k-pci14e4,1668
MB/NET2 PCIX MB /pci@7c0/pci@0/pci@8/network@1 networ
k-pci108e,1648
MB/NET3 PCIX MB /pci@7c0/pci@0/pci@8/network@1,1 networ
k-pci108e,1648
MB/PCIX PCIX MB /pci@7c0/pci@0/pci@8/scsi@2 s
csi-pci1000,50LSI,1064
========================= HW Revisions =======================================
System PROM revisions:
----------------------
OBP 4.23.4 2006/08/04 20:45
IO ASIC revisions:
------------------
Location Path Device
Revision
-------------------- --------------------------------------------- -------------
----------------- ---------
MB/IO-BRIDGE /pci@780 SU
NW,sun4v-pci 0
MB/SAS-SATA-HBA /pci@7c0 SU
NW,sun4v-pci 0
MB/SAS-SATA-HBA /pci@7c0/pci@0 pcie
x1166,103.b5 181
MB/SAS-SATA-HBA /pci@7c0/pci@0/pci@8 pc
i1166,104.b4 180
MB/GBE0 /pci@7c0/pci@0/network@4 pci14e4,1668.
108e.1668.a3 163
MB/GBE0 /pci@7c0/pci@0/network@4,1 pci14e4,1668.
108e.1668.a3 163
MB/GBE1 /pci@7c0/pci@0/pci@8/network@1 pci14e4,1648.
108e.1648.10 16
MB/GBE1 /pci@7c0/pci@0/pci@8/network@1,1 pci14e4,1648.
108e.1648.10 16
MB/SAS-SATA-HBA /pci@7c0/pci@0/pci@8/scsi@2 pci1000,50
.1000.3020.2 2
root@sunt1000-4 #
====================================================================
sc> showenvironment
=============== Environmental Status ===============
--------------------------------------------------------------------------------
System Temperatures (Temperatures in Celsius):
--------------------------------------------------------------------------------
Sensor StatusTemp LowHard LowSoft LowWarn HighWarn HighSoft HighHard
--------------------------------------------------------------------------------
MB/T_AMB OK 27 -10 -5 0 45 50 55
MB/CMP0/T_TCOREOK 41 -10 -5 0 85 90 95
MB/CMP0/T_BCOREOK 41 -10 -5 0 85 90 95
MB/IOB/T_CORE OK 41 -10 -5 0 95 100 105
--------------------------------------------------------
System Indicator Status:
--------------------------------------------------------
SYS/LOCATE SYS/SERVICE SYS/ACT
OFF ON ON
--------------------------------------------------------
----------------------------------------------------------
Fans (Speeds Revolution Per Minute):
----------------------------------------------------------
Sensor Status Speed Warn Low
----------------------------------------------------------
FT0/F0 OK 8776 2240 1920
FT0/F1 OK 8776 2240 1920
FT0/F2 OK 8776 2240 1920
FT0/F3 OK 8776 2240 1920
--------------------------------------------------------------------------------
Voltage sensors (in Volts):
--------------------------------------------------------------------------------
Sensor Status Voltage LowSoft LowWarn HighWarn HighSoft
--------------------------------------------------------------------------------
MB/V_VCORE OK 1.30 1.20 1.24 1.36 1.39
MB/V_VMEM OK 1.79 1.69 1.72 1.87 1.90
MB/V_VTT OK 0.89 0.84 0.86 0.93 0.95
MB/V_+1V2 OK 1.18 1.09 1.11 1.28 1.30
MB/V_+1V5 OK 1.48 1.36 1.39 1.60 1.63
MB/V_+2V5 OK 2.49 2.27 2.32 2.67 2.72
MB/V_+3V3 OK 3.27 3.06 3.10 3.49 3.53
MB/V_+5V OK 4.99 4.55 4.65 5.35 5.45
MB/V_+12V OK 11.93 10.92 11.16 12.84 13.08
MB/V_+3V3STBY WARNING 3.22 3.16 3.23 3.43 3.49
-----------------------------------------------------------
System Load (in amps):
-----------------------------------------------------------
Sensor Status Load Warn Shutdown
-----------------------------------------------------------
MB/I_VCORE OK 19.680 80.000 88.000
MB/I_VMEM OK 8.160 60.000 66.000
-----------------------------------------------------------
----------------------
Current sensors:
----------------------
Sensor Status
----------------------
MB/BAT/V_BAT OK
------------------------------------------------------------------------------
Power Supplies:
------------------------------------------------------------------------------
SupplyStatus UnderspeedOvertempOvervoltUndervoltOvercurrent
------------------------------------------------------------------------------
PS0 OK OFF OFF OFF OFF OFF
sc>
sc> showfaults -v
Last POST run: WED APR 21 02:27:22 2010
POST status: Passed all devices
ID Time FRU Fault
0 AUG 09 04:55:55 MB VOLTAGE_SENSOR at MB/V_+3V3STBY has exceeded low warning threshold.
sc>
===============================================================
sc> showfaults -v
Last POST run: WED APR 21 02:27:22 2010
POST status: Passed all devices
ID Time FRU Fault
0 AUG 09 04:55:55 MB VOLTAGE_SENSOR at MB/V_+3V3STBY has exceeded low warning threshold.
sc>
sc> showfru
FRU_PROM at MB/SEEPROM
SEGMENT: SD
/ManR
/ManR/UNIX_Timestamp32: SAT OCT 28 08:31:12 2006
/ManR/Description: ASSY,Sun-Fire-T1000,Motherboard
/ManR/Manufacture Location:Sriracha,Chonburi,Thailand
/ManR/Sun Part No: 5017302
/ManR/Sun Serial No: EM08DJ
/ManR/Vendor: Celestica
/ManR/Initial HW Dash Level: 09
/ManR/Initial HW Rev Level:50
/ManR/Shortname: T1000_MB
/SpecPartNo: 885-0505-10
SEGMENT: FL
/Configured_LevelR
/Configured_LevelR/UNIX_Timestamp32: SAT OCT 28 08:31:12 2006
/Configured_LevelR/Sun_Part_No: 5411035
/Configured_LevelR/Configured_Serial_No: E804BV
/Configured_LevelR/HW_Dash_Level: 05
SEGMENT: FD
/ECO_CurrentR
/ECO_CurrentR/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/ECO_CurrentR/Firmware_Revision:
/ECO_CurrentR/Hardware_Revision:
/ECO_CurrentR/HW_Dash_Level:
/Customer_DataR
/Customer_DataR/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/Customer_DataR/Cust_Data:
/InstallationR (1 iterations)
/InstallationR
/InstallationR/UNIX_Timestamp32: MON APR 09 04:40:55 2007
/InstallationR/Fru_Path: MB/SEEPROM
/InstallationR/Parent_Part_No:
/InstallationR/Parent_Serial_No:
/InstallationR/Parent_Dash_Level:
/InstallationR/System_Id: 0643NNE05E H8447de5c
/InstallationR/System_Tz:
/InstallationR/Geo_North:
/InstallationR/Geo_East:
/InstallationR/Geo_Alt:
/InstallationR/Geo_Location:
/Status_EventsR (1 iterations)
/Status_EventsR
/Status_EventsR/UNIX_Timestamp32: MON AUG 09 04:55:55 2010
/Status_EventsR/Old_Status: 0x00 (OK)
/Status_EventsR/New_Status: 0x40 (MAINTENANCE REQUIRED)
/Status_EventsR/Initiator: 0xCA (SCAPP)
/Status_EventsR/Component: 0x00
/Status_EventsR/Message: VOLTAGE_SENSOR at MB/V_+3V3STBY has exceeded low warning threshold.
SEGMENT: PE
/Power_EventsR (50 iterations)
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON JUL 02 13:22:49 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: FRI JUL 06 03:35:39 2007
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: FRI JUL 06 03:35:41 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: SUN JUL 08 06:37:21 2007
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: SUN JUL 08 06:37:23 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON JUL 09 05:53:33 2007
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON JUL 09 05:53:35 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: TUE JUL 10 18:09:58 2007
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: TUE JUL 10 18:10:00 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: THU JUL 12 06:53:29 2007
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: THU JUL 12 06:53:31 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: THU JUL 12 07:25:19 2007
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: THU JUL 12 07:25:21 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: THU JUL 12 07:46:49 2007
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: THU JUL 12 07:46:51 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: THU JUL 12 11:21:15 2007
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: THU JUL 12 11:21:17 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: WED NOV 07 09:27:32 2007
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: WED NOV 07 09:27:34 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: WED NOV 07 09:49:24 2007
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: WED NOV 07 09:49:26 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: WED NOV 07 10:04:01 2007
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: WED NOV 07 10:04:03 2007
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: SUN JAN 20 10:29:58 2008
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: SUN JAN 20 10:30:00 2008
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON JAN 21 00:54:54 2008
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON JAN 21 00:55:14 2008
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON JAN 21 01:00:13 2008
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON JAN 21 01:00:15 2008
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON JAN 21 09:50:46 2008
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON JAN 21 10:17:50 2008
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON JAN 21 10:22:33 2008
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON JAN 21 10:22:35 2008
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: TUE JUN 24 16:19:06 2008
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: TUE JUN 24 16:19:08 2008
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: TUE JUN 24 19:14:34 2008
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: TUE JUN 24 19:14:36 2008
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: TUE JUN 24 19:35:01 2008
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: TUE JUN 24 19:35:03 2008
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: TUE JUN 24 20:22:48 2008
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: TUE JUN 24 20:22:50 2008
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: FRI OCT 24 13:14:44 2008
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: FRI OCT 24 13:45:53 2008
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: FRI OCT 24 13:50:35 2008
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: FRI OCT 24 13:50:37 2008
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: MON APR 05 22:41:08 2010
/Power_EventsR/power_event: still_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: WED APR 21 02:22:44 2010
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: WED APR 21 02:27:27 2010
/Power_EventsR/power_event: power_off
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: WED APR 21 02:27:29 2010
/Power_EventsR/power_event: power_on
/Power_EventsR
/Power_EventsR/UNIX_Timestamp32: TUE AUG 09 03:53:02 2011
/Power_EventsR/power_event: still_on
SEGMENT: PS
/Power_SummaryR
/Power_SummaryR/UNIX_Timestamp32: TUE AUG 09 03:53:02 2011
/Power_SummaryR/Total_Time_On: 2256857
/Power_SummaryR/Total_Power_Ons: 60
/Power_SummaryR/Total_Power_Offs: 58
SEGMENT: TH
/Temperature_HistoryR
/Temperature_HistoryR/UNIX_Timestamp32: TUE AUG 09 07:02:50 2011
/Temperature_HistoryR/Sensor: 0
/Temperature_HistoryR/Lowest: 16
/Temperature_HistoryR/Highest: 34
/Temperature_HistoryR/Latest: 27
/Temperature_HistoryR/Histogram:
/Temperature_HistoryR/Histogram: 2736
/Temperature_HistoryR/Histogram: 34877
/Temperature_HistoryR/Histogram: 3
/Temperature_HistoryR/Histogram: 0
/Temperature_HistoryR/Histogram: 0
/Temperature_HistoryR/Histogram: 0
/Temperature_HistoryR/Histogram: 0
/Temperature_HistoryR/Histogram: 0
/Temperature_HistoryR/Histogram: 0
/Temperature_HistoryR/Histogram: 0
SEGMENT: ST
/Status_Proxy1R/
/Status_Proxy1R/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/Status_Proxy1R/version: 0x00
/Status_Proxy1R/StatusMap31: 0x00000000000000000000000000000000000000000000000000000000000000
/Status_CurrentR/
/Status_CurrentR/UNIX_Timestamp32: MON AUG 09 04:55:55 2010
/Status_CurrentR/status: 0x40 (MAINTENANCE REQUIRED) Asset ID: 1-73-1019858.1
Update Date: 2011-05-20
Keywords:
--------------------------------------------------------------------------------
Solution TypeFAB (standard) Sure
Solution1019858.1 : A small number of Sun Fire T1000 and SPARC Enterprise T1000 systems may experience a 3.3V Standby low voltage warning and/or soft shutdown.
Related Items
Sun SPARC Enterprise T1000 Server Sun Fire T1000 Server
Related Categories
GCS>Sun Microsystems>Sun FAB>Hardware Remediation>Reactive
PreviouslyPublishedAs
247687
Bug Id:
Product
Sun Fire T1000 Server
Sun SPARC Enterprise T1000 Server
Date of Resolved Release
15-Dec-2008
T1000 systems may experience a 3.3V Standby low voltage warning (see details below).
Affected Parts:
300-1799-03 (or below) Power Supply Unit, Type A207, 300W
Impact
A small number of Sun Fire T1000 and SPARC Enterprise T1000 systems can experience 3.3V Standby low voltage SC warning and/or soft shutdown, as shown in SUNBUG 6667834. The affected systems can report approximately one failure per day.
Contributing Factors
Sun Fire T1000 or SPARC Enterprise T1000 systems with Power Supply part number 300-1799-03 (or below) can be affected by this issue.
Symptoms
The affected Sun Fire T1000 systems will report the following messages:
"SC Alert: VOLTAGE_SENSOR at MB/V_+3V3STBY has exceeded low warning threshold"
"SC Alert: VOLTAGE_SENSOR at MB/V_+3V3STBY has exceeded low soft shutdown threshold"
The affected system will then shutdown.
Root Cause
This issue is due to the degradation that might develop over time on the connector between the PSU and Motherboard, and causes the +3.3V STBY output to drop below the 3.23V software warning threshold.To correct this issue the previous 3.33V setpoint was increased to 3.38V, to prevent the low voltage warnings and soft shutdown.
This change has been incorporated in the 300-1799-04 power supply via ECO# WO_39464 as of July 7, 2008 to address this issue.
This is neither a safety nor a product quality issue so it doesn't meet purge criteria and therefore there will be no purge. Essentially the FRUID reads -03 level but the FRU is actually a -04, has all the fixes of the -04 and physically is labeled -04 on the FRU barcode label (physical label).
In case one of the affected -04 PSUs is ordered as a field replacement, and as a fix for the 3.3V standby issue in SUNBUG 6667834, the only corrective action needed is to apply the procedure in this Field Action Bulletin (FAB).
These units are actually 300-1799-04 PSUs and as such, the -04 power supply requires the motherboard FRUID update procedure in documented in this FAB. So this FAB still applies, even though field may be mislead to believe it doesn't due to the PSU incorrect FRU-ID 'label' of 300-1799-03.
Corrective Action
Workaround:
No workaround available - see the resolution section below.
Resolution:
Upon failure due to this issue only replace the 300-1799-03 (or below) with 300-1799-04 (or above) by following the below guidelines.
The -04 power supply requires adjustment of the high-voltage warning level in FRUID prom on the motherboard.Installing the power supply without changing the FRUID will cause high voltage warning, which will go away when the FRUID gets updated.
For systems shipped with -04 power supply the FRUID has been updated in manufacturing.The FRUID update procedure should ONLY be used as a part of the PSU replacement in field, and should only be done by a qualified Sun engineer.
This procedure and the FRUID images are provided by TSC/engineering and are available via the below (internal only) URL:
http://panacea.uk.oracle.com/twiki/bin/view/Products/SF_T1000_FRUID
Note: The -04 power supply is the fix ONLY for systems that are experiencing a 3.3V Standby low voltage warning and/or soft shutdown.
Note: PSUs with date codes ranging from xx0838 to xx0902 (ignore the first two characters), have been built with incorrect FRU-ID label of 300-1799-03, but are functionally equivalent to a 300-1799-04 and as such, can be used to fix the issue in the FAB (SUNBUG 6667834) since the -04 PSU is not affected.
For more details on how to identify the affected -04 parts, reference the below URL;
http://pts-platform/twiki/pub/Products/ProdIssuesSunFireT1000/mb_fab_update
Note to Authorized Service Partners:
Sun Authorized Service Partners may contact Sun Services or their Sun Services Representative to receive FAB related information.
Identification of Affected Parts (how to):
Visually inspect the Power Supply:
300-1799-03 (or below) are suspect (review Contributing Factors section above). 300-1799-04 (or above) are not affected.
300-1799-04 power supplies with incorrect FRUID label of 300-1799-03 are also NOT affected. In case one of these -04 PSUs is ordered as a field replacement and as a fix for the 3.3V standby issue, per SUNBUG 6667834, this -04 power supply requires the motherboard FRUID update procedure described earlier in this FAB. This procedure still applies even though field may be mislead to believe it doesn't due to the PSUs incorrect FRU-ID 'label' of 300-1799-03.
Comments
This issue has been evaluated and determined not to meet FCO criteria as it is only expected to impact a small number of systems based on a very low failure rate associated with this issue.
References:
BugID: 6667834
ECO: WO_39464
PITT :2459
For information about FAB documents, its release processes, implementation strategies and billing information, go to the following URL:
http://tns.central/fab
For Sun Authorized Service Providers go to:
http://tns.central/SPE/fab/
In addition to the above you may email:
FAB-Manager@sun.com
Modification @ History
Changes since initial Publication.
09-Mar-2009
Added paragraph to Contributing Factors section explaining how some -04 PSUs have incorrect FRU-ID of -03.Also added link for more information and the associated PITT in the References section.
Internal Contributor/submitter
Dencho.Kojucharov@Sun.COM
Internal Eng Responsible Engineer
Michael.Coulter@Sun.COM Responsible Manager: Steve.Doherty@Sun.COM
Internal Services Knowledge Engineer
Joe.Davis@Sun.COM
Internal Eng Business Unit Group
SSG WGS (Workgroup Systems)
Internal Sun Alert & FAB Admin Info
11-Dec-2008: Completed initial draft and sent to Extended Review.
15-Dec-2008: Resolved all feedback and sent to Publish.
24-Nov-2009: Corrected Product Name to swoRDFish inconsistency.
Attachments
This solution has no attachment
Copyright © 2011 Sun Microsystems, Inc.All rights reserved.
Feedback 电池电压有问题，可以换主板。 可以先更换电池 多谢二位！ 学习了 :luya:我也来学一把 同来学一把 换了后，有好吗？
页:
[1]