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

FIN #: I0754-1

Create Date: Dec/20/01

Keywords: 

Installing third-party software on the Sun Fire 15K System Controller

SunAlert: No

Top FIN/FCO Report: No

Products Reference: Sun Fire 15K System Controller

Product Category: Server / Service

Product Affected: 

Mkt_ID   Platform   Model   Description            Serial Number
------   --------   -----   -----------            -------------
  -        F15K      ALL    Sun Fire 15K Server          -


List X-Options affected.

Mkt_ID   Platform   Model   Description   Serial Number
------   --------   -----   -----------   -------------
   -        -         -        -                -

Parts Affected: 

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

References: 

DOC: 816-3266-10

URL: http://esp.west/home/projects/opensc/info.files/opensc.whitepaper.pdf
     http://sunwww.central//servers/wp/docs/opensc.pdf

Issue Description: 

The System Management Software (SMS) on the System Controller (SC)
monitors and controls the operation of a Sun Fire 15K system.
Installing additional software on the SC may adversely impact SMS's
critical mission of monitoring and controlling the Sun Fire 15K
system.

Because of this, any customer who wishes to install third-party
software on the SC must follow the procedures outlined in the "OpenSC
White Paper" (Sun p/n 816-3266-10).  The "Statement of Support" for
OpenSC, which is included in this FIN, describes the support policy for
third-party software running on the SC.

The SC boards, one of which is the "main" SC and the other is a standby
"spare", is identified on a Sun Fire 15K system with the labels "SC0"
and "SC1".

The SC boards run SMS software under the Solaris Operating Environment.
SMS software is identified by the prefix "SUNWSMS" in the package name.
To determine if SMS is installed, type the following command while
logged in to the SC:

  pkginfo | grep SUNWSMS

For example,

  # pkginfo | grep SUNWSMS

    application SUNWSMSdf  System Management Services Data Files
    application SUNWSMSjh  System Management Services On-Line Javahelp
    application SUNWSMSlp  System Management Services LPOST object files
    application SUNWSMSmn  System Management Services On-Line Manual Pages
    application SUNWSMSob  System Management Services OpenBoot PROM
    application SUNWSMSod  System Controller Open Boot Prom
    application SUNWSMSop  System Management Services Core Utilities
    application SUNWSMSpd  System Controller Power On Self Test
    application SUNWSMSpo  System Management Services POST Utilities
    application SUNWSMSpp  System Management Services picld(1M) Plug-in Module
    application SUNWSMSr   System Management Services, (Root)
    application SUNWSMSsu  System Management Services User Environment

To determine which Solaris Operating Environment (O.E.) and SMS software
version is installed on the system, run the below commands while logged
into the SC (you don't need to be root):

    $ uname -rv
    $ cat /etc/release
    $ pkginfo -l SUNWSMSr | grep VERSION

For example;

    $ uname -rv

         5.8 Generic_108528-11
	
    $ cat /etc/release

         Solaris 8 10/01 s28s_u6wos_02 SPARC
         Copyright 2001 Sun Microsystems, Inc.  All Rights Reserved.
         Assembled 29 May 2001

    $ pkginfo -l SUNWSMSr | grep VERSION

   	 VERSION:  1.2.0,REV=2001.09.04.17.02

Third-party software should not run on the SC board unless the procedures
in the "OpenSC White Paper" (Sun p/n 816-3266-10) are followed.  To detect
possible third-party (i.e., non-SMS and non-Solaris O.E.) software, use
the "ps -ef" (or similar) command to list all processes on the system.

The following long-lived processes are expected on a SC board running
Solaris O.E.  Any long-lived process not owned by user "root" or user
IDs beginning with the prefix "sms-" (for example, user "sms-pcd")
should not be there.  Other processes not in the list below may
indicate non-SMS and non-Solaris software:

  . SMS Processes (all run as UID root or a sms-* UID):

    codd, console, dca, dsmd, dxs, efe, esmd, fomd, frad, hpost hwad, kmd, 
    mand, mld, osd, pcd, setkeyswitch, ssd, tmd, and wcapp.

  . Solaris Processes (all run as UID "root"):

    /usr/lib/*, /usr/sadm/*, /usr/sbin/*, /usr/dt/bin/*, /usr/openwin/bin/*,
    dt*, mibiisa, esd (SunMC), and cst* (CST)

Failures possibly caused by third-party software running on the SC
include timeouts from SMS commands, especially setkeyswitch, moveboard,
addboard, or deleteboard.  These time-outs appear in the SMS log file
/var/opt/SUNWSMS/platform/messages, or in the domain message logs
/var/opt/SUNWSMS/platform/?/messages, where "?" is the domain letter,
uppercase A - R.

Some third-party software running on the SC board may consume too much
CPU, memory, or other computer resources, thereby hindering SMS software
from properly monitoring and controlling the Sun Fire 15K system.

Sun has tested the Sun Fire 15K System Controller with loads simulating
lightweight agents such as local backup agents and network monitoring
agents.  The following parameters were used in these tests:

   * Solaris Operating Environment Release:   8  10/01

   * System Management Software    Release:   1.1

   * Real Memory:                           256 Mbytes

   * Swap Space:                              2 Gbytes

The total real memory and swap space must meet or exceed the minimum
levels determined by the "SMS Memory Worksheet" in the OpenSC White
Paper.

Implementation: 

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

Follow the procedures outlined in the "OpenSC White Paper":

 . DOC: 816-3266-10

  For Internal Version :

    . URL: http://esp.west/home/projects/opensc/info.files/opensc.whitepaper.pdf

  For External Version:

    . URL: http://sunwww.central//servers/wp/docs/opensc.pdf 

Basically, that is:

* Estimate the amount of real memory and swap space required by your SMS and
  third-party software running on the Sun Fire 15K SC board.  This amount can
  exceed the OpenSC minimum requirements.

* Verify that your CPU utilization is not too high.

Comments: 

Statement of Support
--------------------

In order to better serve our customers, Sun is providing this support
policy with respect to executing non-System Management Software (SMS)
on the Sun Fire 15K System Controller (SC).  Applications that run on
the SC, other than the SMS software and the Solaris Operating
Environment, are considered non-SMS software.

The intent of this policy is to provide limited support for lightweight
agents such as monitoring agents, backup agents, and boot disk
management utilities.  Non-SMS software that is not specifically
required to run on the SC should not run there.  Any software that
alters or replaces the binaries required by SMS software is
specifically not supported.  This includes modifying or replacing
dynamically linked libraries.  Software that reduces SMS's reliability,
availability, or serviceability (such as the ability to install patches
or reboot the SC while domains remain in operation) is also not
supported.

Sun Fire 15K's SMS software works correctly in the test environment
described above.  Lightweight processes which are at least as
lightweight as our test load should not interfere with the Service
Processor software functionality.

If a customer believes that the aggregate of all their lightweight
agents do not violate any of the constraints above, Sun will assist
the customer in the resolution of any SMS problems which arise in
their configuration.

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

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 finfco-manager@Sun.COM
---------------------------------------------------------------------------