Document Audience: | INTERNAL |
Document ID: | I0783-1 |
Title: | Sun Fire 15K System Controllers shipped between Aug/13/2001 and Jan/03/2002 (inclusive) may not have the appropriate Solaris FRU ID packages installed |
Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
Update Date: | 2002-03-05 |
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
FIN #: I0783-1
Synopsis: Sun Fire 15K System Controllers shipped between Aug/13/2001 and Jan/03/2002 (inclusive) may not have the appropriate Solaris FRU ID packages installedCreate Date: Mar/05/02
Keywords:
Sun Fire 15K System Controllers shipped between Aug/13/2001 and Jan/03/2002 (inclusive) may not have the appropriate Solaris FRU ID packages installed
SunAlert: No
Top FIN/FCO Report: No
Products Reference: Solaris FRU ID packages on Sun Fire 15K SC
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
----------- -------------------- -----
501-5121-10 System Control Board Sun Fire 15K -
References:
N/A
Issue Description:
Sun Fire 15K systems shipped between August 13, 2001 and January
3, 2002 (inclusive) may not have the appropriate Solaris FRU ID
packages installed on the System Controllers. Affected system
controllers are missing the following packages:
SUNWfruid SUNWfruip.u SUNWfruix
SUNWpiclh SUNWpiclr SUNWpiclu
SUNWpiclx
The end result is that attempts to run the 'prtfru' utility fail.
There could be various reasons why prtfru might fail. Here is
a failure example with SMS stopped:
xc17p13-sc0:sms-svc:26> prtfru
Failed to get frutree root node, libfru: IO error
xc17p13-sc0:sms-svc:27>
The full pathname for 'prtfru' can be found by running the following
command:
xc17p13-sc0:sms-svc:1> which prtfru
/usr/sbin/prtfru
xc17p13-sc0:sms-svc:2>
The 'prtfru' utility will be present if S8U6 is installed. Hence, no
special/extra packages are needed. This is true provided the full
installation of Solaris is done. What was occurring in Operations (and
the reason for the FIN) is that the packages containing 'prtfru' and the
appropriate libraries were being skipped.
This issue was caused by a change to the software load in Sun
Manufacturing, which removed some of the packages from the download
image. The software load process was corrected in Manufacturing on
January 3,2002 to include the necessary FRU ID packages.
In order to resolve this issue, System Controllers must be manually
checked to confirm if the appropriate packages are loaded. Please
follow the procedure shown below.
Implementation:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
Corrective Action:
An Authorized Enterprise Services Field Service Representative may avoid
the above mentioned problems by following the recommendations as shown
below.
On each System Controller, perform the following steps as root:
1. Check which FRU ID packages are installed
# pkginfo | grep SUNWfru
system SUNWfruid FRU ID Utility and Library (Usr)
system SUNWfruip FRU ID Platform Modules (Usr)
system SUNWfruix FRU ID Library (64-bit)
# pkginfo | grep SUNWpicl
system SUNWpiclh PICL Header Files (Usr)
system SUNWpiclr PICL Framework (Root)
system SUNWpiclu PICL Libraries, and Plugin Modules (Usr)
system SUNWpiclx PICL Libraries (64-bit)
2. If NONE of the above packages are displayed, proceed to Step 4.
No installed packages is typical of the problematic System
Controlled shipped out of Sun Manufacturing.
If SOME, but not all, of the above packages are displayed,
proceed to Step 3.
If ALL of the above packages are displayed, the FRU ID packages
are installed correctly. Proceed to Step 7.
3. Stop the picld daemon and uninstall the FRU ID packages in the
order below. Uninstall only those packages displayed in Step 1.
# /etc/init.d/picld stop
# pkgrm \
Answer 'y' to any pkgrm queries.
4. Mount the Solaris 8 10/01 CD on the System Controller and
install the FRU ID packages in the order below.
# cd /Solaris_8/Product
# pkgadd -d . SUNWpiclr SUNWpiclu SUNWpiclx SUNWpiclh \
SUNWfruid SUNWfruip.u SUNWfruix
Answer 'y' to any pkgadd queries.
5. Check for/apply any fru/picld patches from SunSolve. Note that
a patch may require a reboot. See the patch READMEs for details.
6. Start the picld daemon.
# /etc/init.d/picld start
7. Confirm that prtfru is operating correctly.
# prtfru `prtfru -cl | grep container | head -1 | awk '{print $1}'`
<...output...>
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]
--------------------------------------------------------------------------