Obtaining FRU Data information from a Sun Fire[TM] 3800, 4800, 4810, 6800, E4900 or E6900 Server
Last updated on JUNE 06, 2017
Applies to:Sun Fire E6900 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun Fire 3800 Server - Version Not Applicable and later
Sun Fire 4810 Server - Version All Versions and later
Sun Fire 4800 Server - Version Not Applicable and later
Sun Fire E4900 Server - Version Not Applicable and later
My Oracle Support Community - Oracle Sun Technologies Community.
Service personnel may request FRUdata information when troubleshooting server issues. This type of information contains the revision level, configuration and history of all the parts installed in a server. This document is intended to be a security and technical reference for anyone tasked with retrieving this type of data.
NOTE: This document is applicable to the Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, E6900. Though Sun Fire[TM] v1280, E2900, n1280, and n1290 are similar due to a few architectural differences the prtfru utility included in Solaris is able to collect prtfru data. When Sun Fire[TM] v1280, E2900, n1280, and n1290 prtfru data is collected it should be found in /explorer_file_name/fru/prtfru_-x.out
There are two procedures which can be used to obtain the FRU data:
- Oracle Explorer Data Collector.
- The prtfru command utility.
We will cover the description and the use of both methods. The scope of this document is meant to cover only FRU data collection with these utilities. If data collection is required for analysis of a system problem, see Sun Fire[TM] v1280, 3800, 4800, 4810, 6800, E2900, E4900, E6900 and Netra[TM] 1280, 2900 servers: How to collect scextended or 1280extended Explorer (Doc ID 1019066.1) for instructions on how to proceed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms