Document Audience:INTERNAL
Document ID:I0767-1
Title:Environmental thresholds for the Sun Fire 15K with SMS 1.1 must be manually tuned
Copyright Notice:Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved
Update Date:2002-02-08

---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                            FIELD INFORMATION NOTICE
                  (For Authorized Distribution by SunService)
FIN #: I0767-1
Synopsis: Environmental thresholds for the Sun Fire 15K with SMS 1.1 must be manually tuned
Create Date: Feb/08/02
Keywords: 

Environmental thresholds for the Sun Fire 15K with SMS 1.1 must be manually tuned

SunAlert: No
Top FIN/FCO Report: Yes
Products Reference: Sun Fire 15000
Product Category: Server / Service
Product Affected: 
Systems Affected
----------------
Mkt_ID   Platform   Model   Description      Serial Number
------   --------   -----   -----------      -------------
  -        F15K      ALL    Sun Fire 15K           -


X-Options affected:
-------------------
Mkt_ID   Platform   Model   Description      Serial Number
------   --------   -----   -----------      -------------
  -         -         -          -                 -
Parts Affected: 
Part Number   Description   Model
-----------   -----------   -----
     -             -          -
References: 
BugId: 4520740 - esmd most follow latest env. doc. changes.
Issue Description: 
The Sun Fire 15K may get false warning messages about overtemp conditions
when the processors are actually within an acceptable temperature range.

The Sun Fire 15K platform with SMS 1.1 has a software packaging issue
in that the tuning file cannot be patched, and must therefore be adjusted
manually and periodically to update environmental thresholds.  If this
manual tuning is not done, customers experience these false overtemp
warning messages.  All Sun Fire 15K installations running SMS 1.1 are
affected.  This packaging issue has been corrected in SMS 1.2.   

The environmental thresholds of the Sun Fire 15K platform are controlled
via the esmd_tuning.txt file on the System Controller.  As engineering
continues honing the thresholds for the system, changes to the tuning file
will be necessary.  Engineering has performed a thermal recharacterization
of the Sun Fire 15K platform and has determined that the old warning level
for processor temperature was too low.

SMS 1.2 is scheduled for shipment at the same time as Solaris 8 Update
7 in February 2002.  Until that time, field personnel must manually tune
environmental parameters for customers that have SMS 1 installed.  Please
see specific details for doing this in the Corrective Action.
Implementation: 
---
        |   |   MANDATORY (Fully Pro-Active)
         ---    
         
  
         ---
        | X |   CONTROLLED PRO-ACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        |   |   REACTIVE (As Required)
         ---
Corrective Action: 
The following recommendation is provided as a guideline for authorized
Enterprise Services Field Representatives who may encounter the above
mentioned problem.   

Adjust the values for 'cpub_proc_high_warn' and 'mxtb_proc_high_warn'
from 80.0 to 85.0 in the /etc/opt/SUNWSMS/SMS1.1/config/esmd_tuning.txt
file.  The final entries read:

	cpub_proc_high_warn = 85.0
	mxtb_proc_high_warn = 85.0

This must be done on both the MAIN and SPARE SCs.  Once the tuning file
is updated, esmd must be restarted on the MAIN SC.

	# pkill esmd

Messages similar to the following are written to the platform
message log:

    ssd[14644]: [1312 3878876615310193 ERR StartupManager.cc 2581] 
	        software component failed: name=esmd
    ssd[14644]: [1304 3878876626197554 NOTICE StartupManager.cc 2330] 
	        software component start-up initiated: name=esmd

This shows that esmd was killed and the SMS software restarted
the daemon.
Comments: 
None.

--------------------------------------------------------------------------
Implementation Footnote: 
I)   In case of MANDATORY FINs, Enterprise Services will attempt to    
     contact all affected customers to recommend implementation of 
     the FIN. 
   
ii)  For CONTROLLED PROACTIVE FINs, Enterprise 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, Enterprise 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.ebay/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.Corp/

* From there, select the appropriate link to browse the FIN or FCO index.

Supporting Documents:
---------------------
* Supporting documents for FIN/FCOs can be found on Edist.  Edist can be 
  accessed internally at the following URL: http://edist.corp/.
  
* From there, follow the hyperlink path of "Enterprise Services Documenta- 
  tion" and click on "FIN & FCO attachments", then choose the appropriate   
  folder, FIN or FCO.  This will display supporting directories/files for 
  FINs or FCOs.
   
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to [email protected]
--------------------------------------------------------------------------
Statusactive