Asset ID: |
1-72-2032313.1 |
Update Date: | 2018-05-24 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2032313.1
:
T5440 Will Not Power Up with a MEM(X) disabled
Related Items |
- Sun SPARC Enterprise T5440 Server
|
Related Categories |
- PLA-Support>Sun Systems>SPARC>CMT>SN-SPARC: T5xx0
|
In this Document
Created from <SR 3-11044514170>
Applies to:
Sun SPARC Enterprise T5440 Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
T5440 will not power up
-> show faulty
Target | Property | Value
--------------------+------------------------+---------------------------------
/SP/faultmgmt/0 | fru | /SYS
/SP/faultmgmt/0/ | timestamp | Jul 12 02:32:18
/SP/faultmgmt/0/ | sp_detected_fault | Poweron failed: suspect | components: MEM2
Looking at the ILOM logs a MEM(X) :
6725 Sun Jul 12 02:19:04 2015 Chassis Log major Power cycling Host System. Please wait.
6724 Sun Jul 12 02:19:04 2015 Fault Fault critical SP detected fault at time Sun Jul 12 02:19:04 2015. Host Power Failure: MB_DC_POK Fault
6723 Sun Jul 12 02:19:00 2015 Chassis Log major Power system fault detected at /SYS/MB/MEM2/DVRM_FBD: status 0x4
6722 Sun Jul 12 02:18:59 2015 Chassis Log major /SYS/MB/MEM2/DVRM_FBD/OOV_+1V8: asserted failure
6721 Sun Jul 12 02:18:54 2015 Chassis Log major Host has been powered on
6720 Sun Jul 12 02:18:53 2015 Fault Repair minor SP detected fault cleared at time Sun Jul 12 02:18:53 2015. Poweron failed: suspect components: MEM2
6719 Sun Jul 12 02:18:52 2015 Chassis Log major System power on has been requested via power button.
6718 Fri Jul 10 10:38:18 2015 Audit Log minor root : Set : object = "/SYS/power_state" : value = "on" : success
6717 Fri Jul 10 10:38:18 2015 Fault Fault critical SP detected fault at time Fri Jul 10 10:38:18 2015. Poweron failed: suspect components: MEM2
6716 Fri Jul 10 10:38:18 2015 Chassis Log major MEM2 failed to assert POK
6715 Fri Jul 10 10:37:18 2015 Chassis Log critical Host has been powered off
6714 Fri Jul 10 10:37:18 2015 Chassis Log critical Jul 10 10:37:18 FATAL: The HOST Processor has a configuration error, forcing a power-down
6713 Fri Jul 10 10:37:18 2015 Chassis Log critical Jul 10 10:37:18 FATAL: Polling POK Status Time Out: 0xbf
6708 Fri Jul 10 10:04:07 2015 Audit Log minor root : Set : object = "/SYS/power_state" : value = "on" : success
6707 Fri Jul 10 10:04:07 2015 Fault Fault critical SP detected fault at time Fri Jul 10 10:04:07 2015. Poweron failed: suspect components: MEM2
6706 Fri Jul 10 10:04:07 2015 Chassis Log major MEM2 failed to assert POK
6705 Fri Jul 10 10:03:07 2015 Chassis Log critical Host has been powered off
6704 Fri Jul 10 10:03:07 2015 Chassis Log critical Jul 10 10:03:07 FATAL: The HOST Processor has a configuration error, forcing a power-down
6703 Fri Jul 10 10:03:07 2015 Chassis Log critical Jul 10 10:03:07 FATAL: Polling POK Status Time Out: 0xbf
Cause
may vary between firmware and HW issues
Solution
1.- Check your level of firmware
-> version
sysfw_version = Sun System Firmware 7.2.10.a 2010/10/08 16:40
if your version is below 7.4.4.f, upgrade the firmware to the latest 147311-09
-Clear the FMA faults(Doc ID 1004229.1)
-Clear and enable the component that is reported on show faulty
-> set /SYS/<COMPONENT_PATH> clear_fault_action=true
-> set /SYS/<COMPONENT_PATH> component_state=enabled
Example (MEM2):
-> set /SYS/MB/MEM2 clear_fault_action=true
-> set /SYS/MB/MEM2 component_state=enabled
-restart the system
-> reset /SYS
If it fails proceed with the next step.
2.- Open an SR with Oracle Support to review the logs from the system and determine the cause of it.
In order to save time you can upload with the creation of the SR a snapshot.
For more information on how to collect a snapshot and an explorer please see Troubleshooting data needed for T5xx0 servers (Doc ID 1475104.1)
if firmware level is recent replace the faulted MEM(X)
References
<NOTE:1631469.1> - T5120/T5220/T5140/T5240/Netra T5220/Netra T5440 won't power on due to FATAL: Polling POK Status Time Out problem
Attachments
This solution has no attachment