Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1006441.1
Update Date:2010-05-18
Keywords:

Solution Type  Technical Instruction Sure

Solution  1006441.1 :   FRUID capture and collection through Sun Explorer  


Related Items
  • Sun Enterprise 3000 Server
  •  
  • Sun Enterprise 4500 Server
  •  
  • Sun Fire E6900 Server
  •  
  • Sun Enterprise 5500 Server
  •  
  • Sun Fire E25K Server
  •  
  • Sun Enterprise 4000 Server
  •  
  • Sun Enterprise 5000 Server
  •  
  • Sun Enterprise 6000 Server
  •  
  • Sun Fire E20K Server
  •  
  • Sun Enterprise 3500 Server
  •  
  • Sun Fire 3800 Server
  •  
  • Sun Fire 6800 Server
  •  
  • Sun Netra 1280 Server
  •  
  • Sun Enterprise 6500 Server
  •  
  • Sun Fire E4900 Server
  •  
  • Sun Fire 12K Server
  •  
  • Sun Fire 4800 Server
  •  
  • Sun Fire V1280 Server
  •  
  • Sun Fire E2900 Server
  •  
  • Sun Fire 15K Server
  •  
  • Sun Netra 1290 Server
  •  
  • Sun Fire 4810 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>High-End Servers
  •  
  • GCS>Sun Microsystems>Servers>Entry-Level Servers
  •  
  • GCS>Sun Microsystems>Servers>Midrange Servers
  •  
  • GCS>Sun Microsystems>Servers>NEBS-Certified Servers
  •  

PreviouslyPublishedAs
209030


Description
Capturing FRUID through Sun Explorer[TM] seems to be somewhat of an art. FRUID capture can help Sun identify issues from known FRU's that are affected by a Sun Alert or an FCO.

FRUID stands for "Field Replaceable Unit IDentification", i.e. data kept in a memory chip on the replaceable parts to record a part's history of installations and faults.

Capture rate is incredibly low for systems capable of gathering FRUID. Here are some tips and tricks to gather the FRUID output when running Sun Explorer. FRUID is available on High End Sun Fire[TM] 12K/15K/E20K/E25K Servers, Midrange Sun Fire[TM] x800/Ex900 Servers and all other Ultra Sparc III or better systems.


This document has become obsolete for all properly maintained installations. It is here for older, not properly maintained installations and because it is linked from other documents.


Steps to Follow
Start with a current version of Sun Explorer (5.13 or better). This system should be running Solaris[TM] 8 with kernel 108528-29 as a minimum or Solaris[TM] 9 or better.

Sun Fire 12K/15K/E20K/E25K Servers:

Run Sun Explorer on the Main SC. SMS version 1.3 or better (the only current version is 1.6).
Sun Explorer captures FRUID data for these systems by default.
To collect FRUID data only, run as root:

#/opt/SUNWexplo/bin/explorer -w fru

Look for the following file to be several MB in size.
"<explorer_location>/fru/prtfru_-x.out"

If the file "<explorer_location>/fru/prtfru_-x.err" exists, you may have an issue as well. If the file "prtfru_-x.out" is still several MB in size then this is usually OK.

Sun Fire x800/Ex900 Servers:

You need to run "scextended" for Sun Fire x800/Ex900 Servers to gather FRUID data. Run as root:

#/opt/SUNWexplo/bin/explorer -w all #works if "scinput.txt" file is ready

or

#/opt/SUNWexplo/bin/explorer -w scextended #works if "scinput.txt" file is not populated.

Sun Explorer in this case MUST be run from a system that has network access to the SC for each Sun Fire x800/Ex900 Server. This system should be running a minimum of Solaris 8 with kernel 108528-29 as a minimum.

Look for the following file with the second field being the name of the main SC:
"<explorer_location>/sc/<SC name>/prtfru_-x.out"

If the file " <explorer_location>/sc/<SC name>/prtfru_-x.err" exists, you may have an issue as well. If the file "prtfru_-x.out" is still several MB in size then this is usually OK.

Other Ultra Sparc III or better systems:

Sun Explorer automatically captures FRUID for these systems unless you turn off the collection. Run as root:
#/opt/SUNWexplo/bin/explorer -w fru

Look for the following file:
<explorer_location>/fru/prtfru_-x.out

If this file exists, you may have an issue as well. If previous file is still larger in size then, this is usually OK.
<explorer_location>/fru/prtfru_-x.err



Product
Sun Fire E20K Server
Sun Fire E25K Server
Sun Fire 12K Server
Sun Fire 15K Server

Internal Comments
Please note:

Bug IDs 5084883, 4952214, and 4952341 regarding FRUID data collection via obsolete versions of Explorer.


Also note:
Technical Instruction <Document: 1004866.1>

Symptom Resolution < Solution: 208494 >

FAB < Solution: 201779 >

Technical Instruction < Solution: 212493 >

http://dragnet.central converts the xml to html for each host with valid fruid output. Whenever the server type is a link the fruid html is available.


explorer, prtfru, fruid, container, dimm, size, segment, history, cpu, speed, system_id
Previously Published As
78871

Change History
Date: 2008-12-31
User Name: Cootware
Action: Tech review ok

Date: 2008-01-08
User Name: 95826
Action: Update Canceled
Comment: *** Restored Published Content *** canceling update to allow migration to IBIS

Version: 0
Date: 2008-01-08
User Name: 95826
Action: Reassign
Comment: reassigning document to release it in order to allow migration to IBIS
Version: 0
Date: 2005-02-11
User Name: 35516
Action: Update Started
Comment: correcting infos regarding scinput.txt

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback