---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                            FIELD INFORMATION NOTICE
                  (For Authorized Distribution by SunService)

FIN #: I0781-1

Create Date: Mar/01/02

Keywords: 

Upgrades to the factory installed SMS software on Sun Fire 15K systems might overwrite the Capacity On Demand blacklist file

SunAlert: No

Top FIN/FCO Report: Yes

Products Reference: COD CPUs for Sun Fire 15K

Product Category: Server / Service

Product Affected: 

Systems Affected
----------------  
Mkt_ID     Platform   Model   Description                    Serial Number
------     --------   -----   -----------                    -------------
  -          F15K      ALL    Sun Fire 15000                       -
 

X-Options Affected:
-------------------
Mkt_ID   Platform   Model   Description   Serial Number
------   --------   -----   -----------   -------------
  -         -         -          -              -

Parts Affected: 

Part Number   Description   Model
-----------   -----------   -----
     -             -          -

References: 

URL:  http//docs.sun.com
      ftp://192.18.99.138/816-4009-10/816-4009-10.pdf

Issue Description: 

When Sun Fire 15K SMS software is upgraded in the field, the blacklist
file for Capacity On Demand (COD) 1.1 software might become corrupted.
Without a good blacklist file, COD will not function and customers will
be able to use all installed processors in the system without RTU
licenses.  This results in a loss of revenue to Sun.
 
Capacity On Demand (COD) is the ability to increase CPU capacity when
needed for higher workloads.  This is accomplished by requiring
customers to purchase a Right-To-Use license for each CPU/Memory Board
processor.  

A problem occurs with upgrades to the SMS software when COD 1.1 is
running.  COD 1.1 provides two factory installed CPU/Memory Boards with
4 processors each in slots 16 and 17.  This early version of COD
disables these processors at the factory with the use of a blacklist
file.  If this file is overwritten during an SMS upgrade, all the COD
processors become enabled by default.  The RTU cost is about $26,000 per
processor so the revenue loss could be up to $208,000 per system. 
     
The System Controller 'showcomponent' command can be used to verify the 
platform blacklist file for the current blacklisted components.  Here's
a sample output from 'showcomponent':

    sc% showcomponent

        Component PROC at SB16/P0 is disabled: 
        Component PROC at SB16/P1 is disabled: 
        Component PROC at SB16/P2 is disabled: 
        Component PROC at SB16/P3 is disabled: 

The 'showcodusage' command shows the usage of currently installed RTU 
licenses.  

Example output:

   sc% showcodusage

    -------------------------------------------------------------------
   | Resource | In Use | Installed | Licensed | Status                 |
   |==========|========|===========|==========|========================|
   |   PROC   |    2   |     4     |    4     | OK: 2 available        |
   |   PROC   |    6   |     8     |    4     | HEADROOM: 2 in use     |
    -------------------------------------------------------------------

NOTE: Normally, only one line will be seen.  Above example shows multiple
      lines diplayed for the PROC resource to illustrate the different
      possible values.  The actual command will display only one line
      for the PROC resource.  In line 1, 2 CPUs are in use, 4 are 
      installed and 4 are licensed, so the customer is in alignment 
      with their agreement.  In line 2, 6 are in use, 8 are installed, 
      but only 4 are licensed so the customer is using his headroom option.  
      Headroom allows the customer to use extra capacity until they can 
      purchase a license.  There is no license checking in COD 1.1 so the 
      customer can use the headroom without time limit violations. 
     
The platform blacklist file on the system controller must be backed up
prior to installing any upgrades to the SMS factory installed
software.  Newly installed upgrades will change any modifications that
have been made to the platform blacklist file on the system.  If the
system blacklist is modified from factory settings, unlicensed COD
processors will be enabled and the customer will gain resources for
which they have not paid.
   
COD 1.1 is an interim release and will be replaced by COD 2.0.  Sun
Fire 15K systems are scheduled to ship with COD 2.0 later this year
(Q1FY03).  Version 2.0 will control the use of CPU/Memory boards by not
allowing the user to turn on processors without a license.

Implementation: 

---
        |   |   MANDATORY (Fully Proactive)
         ---    
         
  
         ---
        | X |   CONTROLLED PROACTIVE (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.

1) When installing or upgrading SMS software, first save a backup copy of 
   the COD 1.1 blacklist file.  The original file is located at:

          /etc/opt/SUNWSMS/SMS/config/platform/blacklist

2) At system installation, or when there is a question about the number
   of licensed processors:

   a. Determine the number of licensed processors for a particular system 
      with the following command:
   
          sc% showcodusage

   b. View the platform blacklist file ('showcomponent') and disable all 
      COD processors ('disablecomponent') for which the customer does not 
      have an RTU.  Reference the Sun Fire 15K System Capacity On Demand 1.1 
      Installation Guide (816-4009-10) for specific details for this 
      procedure at:  
      
         http://docs.sun.com/  (search for "816-4009-10")

Comments: 

============================================================================

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.
  
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to [email protected]
--------------------------------------------------------------------------