Sun Fire E25K Server
 
Sun Enterprise 5500 Server
 
Sun Fire 4810 Server
 
Sun Enterprise 4000 Server
 
Sun Enterprise 5000 Server
 
Sun Enterprise 3500 Server
 
Sun Enterprise 3000 Server
 
Sun Fire 3800 Server
 
Sun Fire 15K Server
 
Sun Enterprise 6000 Server
 
Sun Netra 1290 Server
 
Sun Fire 12K Server
 
Sun Fire 6800 Server
 
Sun Fire E6900 Server
 
Sun Fire E20K Server
 
Sun Enterprise 6500 Server
 
Sun Fire V1280 Server
 
Sun Fire E2900 Server
 
Sun Fire 4800 Server
 
Sun Enterprise 4500 Server
 
Sun Fire E4900 Server
 
Sun Netra 1280 Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-Exxk
 
_Old GCS Categories>Sun Microsystems>Servers>High-End Servers
 
_Old GCS Categories>Sun Microsystems>Servers>Entry-Level Servers
 
_Old GCS Categories>Sun Microsystems>Servers>NEBS-Certified Servers
 
_Old GCS Categories>Sun Microsystems>Servers>Midrange Servers
 

Applies to:

Goal

Capturing FRUID through Oracle Explorer Data Collector seems to be somewhat of an art. FRUID capture can help Oracle 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 rather 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.

Solution

Start with a current version of Oracle Explorer Data Collector (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 Oracle Explorer Data Collector on the Main SC. SMS version 1.3 or better (the only current version is 1.6).  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.

Oracle Explorer Data Collector in this case MUST be run from a SPARC 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 at least kernel 108528-29.

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:

Oracle Explorer Data Collector 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

Please note:

Bug IDs 5084883, 4952214, and 4952341 regarding FRUID data collection via obsolete versions of Explorer.
Also note:
Document 1004866.1, How to gather 'prtfru -x' info for Sun Fire[TM] xx00 platforms without having Sun[TM] Explorer installed

FRUID capture and collection through Oracle Explorer Data Collector (Doc ID 1006441.1)
Lost documents:
Symptom Resolution < Solution: 208494 >
FAB < Solution: 201779 > "FRUID datat not being extracted by the Explorer utility on customer systems in the field."
Technical Instruction < Solution: 212493 >
On cores2 use /cores_data/local/bin/showfru to view the FRU information in human readable form.
explorer, prtfru, fruid, container, dimm, size, segment, history, cpu, speed, system_id
Previously Published As 78871

References

This solution has no attachment