Document Audience:INTERNAL
Document ID:I0885-1
Title:SunVTS releases prior to 5.1 may not run tests on all CPUs in Sun Fire 12K/15K domains.
Copyright Notice:Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved
Update Date:2002-11-26

---------------------------------------------------------
            - Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                        FIELD INFORMATION NOTICE
               (For Authorized Distribution by SunService)
FIN #: I0885-1
Synopsis: SunVTS releases prior to 5.1 may not run tests on all CPUs in Sun Fire 12K/15K domains.
Create Date: Oct/04/02
SunAlert: No
Top FIN/FCO Report: No
Products Reference: SunVTS on Sun Fire 12K/15K
Product Category: Server / Service
Product Affected: 
Systems Affected:
-----------------  
Mkt_ID      Platform     Model      Description      Serial Number
------      --------     -----      -----------      -------------
  -           F12K        ALL       Sun Fire 12K           -
  -           F15K        ALL       Sun Fire 15K           -


X-Options Affected:
-------------------
Mkt_ID       Platform    Model      Description      Serial Number
------       --------    -----      -----------      -------------
  -             -          -             -                 -
Parts Affected: 
Part Number      Description        Model
-----------      -----------        -----
     -                -               -
References: 
BugId:   4641737 - cputest missing if cpu-id >= 128.
Issue Description: 
SunVTS releases prior to 5.1 may not run CPU tests on Sun Fire 12K/15K
domains.  If a domain does not contain at least one System Board in
slots 0-3, 'cputest' will not execute on processors in that domain.
SunVTS is the primary hardware diagnostic tool used by service
personnel.  The inability to run 'cputest' prevents complete hardware
diagnostics from being run on Sun Fire 12K/15K domains.  It is possible
that bad hardware may not be detected.

This issue can occur on any Sun Fire 12K/15K server where the version
of SunVTS is lower than 5.1 and no System Boards for a domain reside in
slots 0-3.  The SMS 'showboards' command will display the slots where a
domain's boards reside..  To determine the SunVTS version for a domain,
use the 'pkginfo' command.

	# pkginfo -l SUNWvts
   	PKGINST:  SUNWvts
           NAME:  SunVTS
       CATEGORY:  system
           ARCH:  sparc
        VERSION:  5.1,REV=08.02.06.27,OE=5.8,5.9
        
The VTS log data will show whether or not 'cputest' has been run on a
domain's CPUs.  The VTS log data is available in
/var/opt/SUNWvts/logs/sunvts.info.  The log snippet below shows an
example in which 'cputest' was run on cpu-unit0.

09/09/02 13:47:35 pumba SunVTS5.1: VTSID 7005 vtsk.INFO : *Stop all tests*
 System Passes: 1, Cumulative Errors: 0, Elapsed Test Time: 000:06:00
 cpu-unit0(cputest)       passes: 1      errors: 0     
 cpu-unit0(iutest)        passes: 9      errors: 0     
 cpu-unit0(iutest).1      passes: 9      errors: 0     
 cpu-unit0(fputest)       passes: 9      errors: 0     
 cpu-unit0(fputest).1     passes: 8      errors: 0            

A bug exists in SunVTS releases prior to 5.1 that prevents the tests
from being run on Safari Agent IDs greater than 128.  On F12/15K
systems, this means that a domain must contain at least one System
Board (CPU or MCPU) in slots 0-3 for 'cputest' to execute.  When
'cputest' is available for selection, it can be run on all processors
in the domain.

For example:

  Domain processor boards: SB0 SB5 SB6 SB7
   'cputest' may be selected and run.  It will execute on _all_ processors
   on SB0, SB5, SB6, and SB7.

  Domain processor boards: SB9 SB10 SB11
   'cputest' cannot be selected or run.

Bug 4641737 exists in versions of SunVTS prior to release 5.1.  The bug
prevents CPUs with Safari Agent IDs greater than 128 from running
'cputest' from either the TTY or CDE user interfaces.  It is possible
to workaround the bug by including a System Board in slots 0 through 3
(see below).

This issue has been fixed in Sun VTS version 5.1.
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
Sun Services Field Representatives.

1. All Sun Fire 12K/15K domains running Solaris 8 Update 7 and above 
   (including all Solaris 9 releases) should install SunVTS release 5.1 
   or later.  

   The VTS packages (SUNWvts SUNWvtsmn SUNWvtsx) are available on the
   Solaris 9 Update 1 CD or may be downloaded from the internal
   engineering home page at:

       http://diagnosis.eng/sunvts/sunvts_download.shtml

   Installation instructions are available at the site.

   If the customer is running Solaris 8 Update 6, it is recommended to
   upgrade to Solaris 8 Update 7 or later.  SunVTS 5.1 can then be
   installed.
   
OR

2. Customers who are unable to upgrade from Solaris 8 Update 6 may need
   to take special measures to run 'cputest' on their domains.  If the 
   domain contains any System Board in slots 0 through 3, no action is
   required.  VTS 4.6 will suffice.  If the domain does not contain a
   System Board in slots 0 through 3 then one will need to be
   temporarily assigned in order to run 'cputest' on release 4.6 of
   VTS.  This will require domain downtime, since dynamic
   reconfiguration is not available on Solaris 8 Update 6.  An example
   overview of the process is shown below.  Note: The example assumes
   SB0 is available for use by domain A.

   % setkeyswitch -d A off
   % addboard -d A -c assign SB0
   % setkeyswitch -d A on

   Run VTS 4.6 tests on booted domain.

   % setkeyswitch -d A off
   % deleteboard SB0
   % setkeyswitch -d A on
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.

Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to [email protected]
--------------------------------------------------------------------------
Statusactive