Obtaining FRU Data information from a Sun Fire[TM] 3800, 4800, 4810, 6800, E4900 or E6900 Server

Asset ID:	1-71-1009290.1
Update Date:	2017-06-06
Keywords:

Solution Type Technical Instruction Sure

Solution 1009290.1 : Obtaining FRU Data information from a Sun Fire[TM] 3800, 4800, 4810, 6800, E4900 or E6900 Server

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
All Platforms

Goal

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in an appropriate
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.
or
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.

Solution

Oracle Explorer Data Collector

Explorer is a common tool used to obtain all sorts of data from Sun systems. If properly run it will also obtain FRU data which may be requested by the services team. The latest Explorer packages can be downloaded from the Oracle Services Tools Bundle for Sun Systems web site. The website also contains detailed information as to how to install, run, obtain the data, among other information. See also Document 1312847.1 for information on the Oracle Explorer Data Collector.

To obtain the FRU data with Explorer it is necessary to make certain that the machine which is going to collect the data is on the same private network as the system controller(s) to be polled.

If the machine has been properly configured, it should have a loghost. This would be an ideal data collection machine. Alternately, if a loghost has not been configured it may be possible to run the explorer from any Solaris machine with Explorer packages installed residing on the same private network as the System Controller being polled. Explorer's fru option cannot run unless the scextended option is also run and it will require the password for the console.

Example:
```
# ping 123.45.67.890
123.45.67.890 is alive   <<< ping should be successful on the machine you wish to run explorer on. 
```

Run the Explorer (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 provides recommended instructions).
If the default parameter is prefixed with ! It will reduce the size of the collected explorer file and the run-time. The use of !default prevents the explorer from capturing internal data from the loghost/domain while collecting scextended data.

If the explorer is being collected for extensive troubleshooting all data collection may be required and a parameter of default may be necessary without the ! prefix.

Example:

# /opt/SUNWexplo/bin/explorer -w !default,scextended,fru
Nov 28 10:48:07 hostname[7276] explorer: explorer ID: 
   explorer.80fb1234.hostname-2009.11.28.16.48
Nov 28 10:48:07 hostname[7276] patch: RUNNING
Nov 28 10:48:08 hostname[7276] pkg: RUNNING
Nov 28 10:48:19 hostname[7276] sysconfig: RUNNING
Nov 28 10:50:21 hostname[7276] sysconfig: exited: AP not installed
Nov 28 10:50:22 hostname[7276] fru: RUNNING
Nov 28 10:50:24 hostname[7276] scextended: RUNNING You will be prompted for a System Controller name.   If the hostname cannot be resolved, you will have to  use the IP address. To avoid site specific network configuration issues, Oracle suggests using the I.P. Address instead of the hostname as shown below.

Type return to end the list.
Please enter the name of the SC: 123.45.67.890
Please enter the SC platform password for 123.45.67.890: Password
Please enter the name of the SC: 
Nov 28 11:26:37 hostname[7276] explorer: data collection complete
Nov 28 11:26:40 hostname[7276] explorer: removing previous explorers
   from /opt/SUNWexplo/output
Nov 28 11:26:41 hostname[7276] explorer: Explorer finished

Explorer, when it is finished running will create a directory with all files created under it and a gzip compressed data file.

# ls /opt/SUNWexplo/output
explorer.80fb1234.hostname-2009.11.28.16.48
explorer.80fb1234.hostname-2009.11.28.16.48.tar.gz <

If you cd into the explorer directory tree there should be a prtfru_x.out file located in one of two locations.
- On Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, E6900 it should be in /explorer_name/sc/sc_name_or_ip/prtfru_-x.out

Regardless of the system type, if this file exists (like in the examples below), the explorer run was successful:
```
# ls /explorer.80fb2543.hostname-2004.09.28.16.48/sc/172.20.10.195
prtfru_-x.err     showcomponent_-d_a.out     showdate_-v_-d_a.out
prtfru_-x.out     showcomponent_-d_b.out     showdate_-v_-d_b.out
......

The prtfru_-x.out file is the one we're interested in.
```

If this file exists please forward the gzip'ed file in our example:
```
explorer.80fb1234.hostname-2009.11.28.16.48.tar.gz
```

**The prtfru Utility**

Like Explorer, this utility should be run from a Solaris workstation located on the same private network as the System Controller (SC) to be polled. The advantage to the utility is its ability to access FRU data from SCs without logging in to them. The utility uses a Java Remote Method Invocation (RMI) in read-only mode to collect FRU information from a Sun Fire Midrange Server Service Processor. The utility does not access or return any Solaris or any active process data on any configured domain. This RMI interface is used by Sun specific products: Sun Management Center (SunMC) and Explorer (rprtfru) to securely gather data.

The following message in the example below may be displayed :

# ./prtfru_sg -b 123.45.67.890  <# ./prtfru_sg[42]: getopts: b bad option(s)

usage: prtfru_sg <SC> [<SC> ...]
       prtfru_sg -f <batchfile>

       <SC>     Hostname or IP address of a Sun Fire SC
       <batchfile> File containing one <SC> per line

This error message will occur and is normal for this utility.
It refers to an option not selected to create a batch file containing System Controller IP address's.

**The prtfru package is available for your use as an attachment to this article.**

It is suggested that you utilize Explorer for capturing this data, but the package has been made available to you in this form if required/desired.

Example of prtfru utility in use

The untarred package will have the executable script in its the top level directory

# ls sg_prtfru <sg_prtfru.tar

# cd  sg_prtfru<# ls
java            
prtfru_sg  <Executable Script 
bin       
lib

# ./prtfru_sg -b 123.45.67.890  <# ./prtfru_sg[42]: getopts: b bad option(s)

usage: prtfru_sg <SC> [<SC> ...]
       prtfru_sg -f <batchfile>

       <SC>     Hostname or IP address of a Sun Fire SC
       <batchfile> File containing one <SC> per line

# ./prtfru_sg 123.45.67.890
Collecting data for 1 host:
  123.45.67.890
Contacting "123.45.67.890"...
Contacted "123.45.67.890" successfully
Collecting FRUID Data from "123.45.67.890".  (This may take several minutes)

FRUID Data Collection done.
********************************************
Refer to 123.45.67.890_result for the output.
********************************************

Checking the collected data.

# ls
java            
123.45.67.890_result  < bin                                   lib prtfru_sg terminator#

Please send the *_ result file to the engineer requesting the data.

Attachments

This solution has no attachment