Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-77-1302382.1
Update Date:2011-03-11
Keywords:

Solution Type  Sun Alert Sure

Solution  1302382.1 :   Sun Blade T6340 May Power Off During SP Reset With Voltage Threshold Reached  


Related Items
  • Solaris SPARC Operating System
  •  
  • Sun Blade T6340 Server Module
  •  
Related Categories
  • GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
  •  
  • GCS>Sun Microsystems>Sun Alert>Release Phase>Workaround
  •  




In this Document
  Description
  Likelihood of Occurrence
  Possible Symptoms
  Workaround or Resolution
  Modification History


Applies to:

Sun Blade T6340 Server Module - Version: Not Applicable and later   [Release: N/A and later ]
Solaris SPARC Operating System - Version: 10 10/09 U8 and later    [Release: 10.0 and later]
Information in this document applies to any platform.
__________________


__________________

Date of Workaround Release: 09-Mar-2011
___________________________________

Description


Sun Blade T6340 host could be powered off unexpectedly during ILOM SP reset, caused by a voltage threshold being reached.

Likelihood of Occurrence


This issue can occur on the following platforms:
  • Sun Blade T6340 with Firmware version up to and including 7.3.0.c
Notes:

1. No other systems or blades are affected by this issue.

2. Contributing to the cause of this issue (as described in CR 7023504), ILOM falls back to using default thresholds from the sensor xml files for 1.1V rails. The values recorded in these files are lower than what they should be and need to be adjusted.

To determine the Firmware version on the T6340, the following command can be used:
sc> showhost
Sun System Firmware 7.2.8 2010/03/15 10:43
...
...
sc>

Possible Symptoms


Should the described issue occur, the following error messages will be seen in the SP (Service Processor/ILOM) event logs:
sc> showlogs -v
Feb 27 02:08:17: IPMI    |minor   : "ID =   1d : 02/27/2011 : 02:08:17 :
Voltage : /MB/CMP1/V_+1V1 : Upper Non-critical going high : reading 1.25 >= threshold 1.20 Volts"
Feb 27 02:08:22: IPMI    |minor   : "ID =   1e : 02/27/2011 : 02:08:19 :
Voltage : /MB/CMP0/V_+1V1 : Upper Non-critical going high : reading 1.25 >= threshold 1.20 Volts"
Feb 27 02:08:22: IPMI    |major   : "ID =   1f : 02/27/2011 : 02:08:22 :
Voltage : /MB/CMP1/V_+1V1 : Upper Critical going high : reading 1.25 >= threshold 1.23 Volts"

Workaround or Resolution


The following is the only known workaround at this time, which requires downtime to be scheduled:

Reset the SP when the host OS is not running i.e: host is brought to standby first in this state. In this case there are no voltages to monitor and therefore no incorrect action will be taken.

Note: Although downtime may not be desirable, it is being suggested to avoid the potential of an unplanned outage.

Modification History


Date of Workaround Release: 09-Mar-2011

Internal Comments:
-
Note:
Specific Product and Platform choices have been added to this
Sun Alert to conform with and enable MOS Hot Topics delivery.
(for this doc: Solaris SPARC Operating Systems)
If you have any questions about these items, please email:
sunalertpublication_us@oracle.com

Please send technical questions to the following email:
sunalertpublication_us@oracle.com
and copy the Responsible Engineer listed
Internal Contributor/Submitter: Chuck.Forgues@oracle.com
Internal Eng Responsible Engineer: David.Rudy@oracle.com,
Asim.Salam@oracle.com, Paul.Capewell@oracle.com
Internal Services Knowledge Analyst: david.mariotto@oracle.com
Internal Eng Business Unit Group: Systems Group
SVS (SPARC Volume Systems)
Internal Escalation ID:  3-3067747787

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback