| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||||||||||||||||||||
Solution Type Predictive Self-Healing Sure Solution 1597728.1 : How to investigate the Auto Service Request "ASR: Probable power supply failure (PS ) or AC input not present" for Sun Fire V210/V215/V240/V245/V440/V445 Server
In this Document
Applies to:Sun Fire V440 ServerSun Fire V210 Server Sun Fire V245 Server Sun Fire V240 Server Sun Fire V215 Server Information in this document applies to any platform. PurposeThis article describes activity required by a System Administrator to verify whether action has to be taken on a reported loss of input power. SunMC Event 1.3.6.1.4.1.42.2.12.2.2.1.1.10.2.2.1.1.6 ScopeThis document is intended for System Administrators and support personnel. DetailsAuto Service Request (ASR) provides automatic processing of failure detection telemetry and SR creation for certain Oracle systems. See http://www.oracle.com/asr for more information on ASR. Description of the eventPower supply events can be either transient or persistent. They can be generated by external changes and actions most notably by the removal of AC from a power supply. Additional checks need to be performed in order to understand the cause of this event received by ASR. How to verify if there is a genuine Power Supply issuePhysical checksPlease check the power feeds for the system's PSUs
Software checksPlease run /usr/sbin/prtdiag -v on the Solaris command line. Please compare the relevant parts of the output to the examples provided below. If all Fault LEDs are OFF, and all PSUs show NO_FAULT, then the fault is most likely transient and can be ignored for now. Otherwise please collect and upload an Explorer as outlined in "What data is needed in order to troubleshoot my software or hardware problem?". Example Sun Fire V440 (PS1 faulty)explorer.83ac8d7b.wmit1d-2013.10.20.01.30 0418AD2222 3-8033717701 Output of prtdiag -v: Sep 27 03:04:48 oursystem rmclomv: [ID 474711 kern.error] PSU @ PS1 has FAILED. Example entry in /var/adm/messages: Sep 27 03:04:48 oursystem rmclomv: [ID 474711 kern.error] PSU @ PS1 has FAILED.
$ grep PS mess* |tr -s " "|cut -d: -f2,5,6|cut -d" " -f1,2,7-255|sort -M|uniq -c
83 Sep 20 PSU @ PS1 has FAILED. 96 Sep 21 PSU @ PS1 has FAILED. 96 Sep 22 PSU @ PS1 has FAILED. 96 Sep 23 PSU @ PS1 has FAILED. 96 Sep 24 PSU @ PS1 has FAILED.
Example Sun Fire V210 (PS0 faulty)explorer.83574f25.beuu12-2013.08.04.07.56 TM40352387 3-7635601541 Output of prtdiag -v: System Configuration: Sun Microsystems sun4u Sun Fire V210 System clock frequency: 167 MHZ Memory size: 1GB ... -------------------------------------------------- Led State: -------------------------------------------------- Location Led State Color -------------------------------------------------- ... PS0 ACT off green PS0 SERVICE on amber PS0 OK2RM off blue ... ------------------------------------------------------------------- Temperature sensors: ------------------------------------------------------------------- Location Sensor Temperature Lo LoWarn HiWarn Hi Status ------------------------------------------------------------------- ... PS0 FF_OT - - - - - okay ------------------------------------------------------------------------ Voltage sensors: ------------------------------------------------------------------------ Location Sensor Voltage Lo LoWarn HiWarn Hi Status ------------------------------------------------------------------------ ... PS0 FF_UV - - - - - okay PS0 FF_OV - - - - - okay PS0 P_PWR - - - - - okay ---------------------------------------------------------------------- Current sensors: ---------------------------------------------------------------------- Location Sensor Current Lo LoWarn HiWarn Hi Status ---------------------------------------------------------------------- MB FF_SCSI - - - - - okay PS0 FF_OC - - - - - okay ======== FRU Status ========= ------------------------- Fru Operational Status: ------------------------- Location Status ------------------------- MB/SC okay PS0 faulty ...
Example entry in /var/adm/messages: Aug 4 03:00:41 oursystem rmclomv: [ID 474711 kern.error] PSU @ PS0 has FAULTED.
.../messages $ grep PS mess* |tr -s " "|cut -d: -f2,5,6|cut -d" " -f1,2,7-255|sort -M|uniq -c
94 Jul 10 PSU @ PS0 has FAULTED. 95 Jul 11 PSU @ PS0 has FAULTED. 95 Jul 12 PSU @ PS0 has FAULTED. 95 Jul 13 PSU @ PS0 has FAULTED. 94 Jul 14 PSU @ PS0 has FAULTED.
References<NOTE:1019144.1> - Data Requirements reference: What data is needed in order to troubleshoot my software or hardware problem?<NOTE:1547088.2> - How to Upload Files to Oracle Support <NOTE:1010045.1> - Troubleshooting Power Supply failures on V210/V240/V215/V245/V440/V445, T1000/T2000, V480/V490/V880/V890 servers <NOTE:1271047.1> - Sun Fire V440 Power Supply Installation and Removal:ATR:782:1 [Video] <NOTE:1504290.1> - How to identify a PSU fault in a Sun Fire V440 server. <NOTE:1006640.1> - How To Get Explorer To Collect ALOM Data on V125/V210/V215/V240/V245/V440/V445 and Netra 210/240 <NOTE:1006990.1> - Oracle Explorer Data Collector Implementation Best Practice <NOTE:1153444.1> - Oracle Services Tools Bundle (STB) - RDA/Explorer, SNEEP, ACT Attachments This solution has no attachment |
||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||