Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, and E6900 servers: How to run scextended Oracle Explorer Data Collector

Asset ID:	1-71-1011830.1
Update Date:	2011-05-23
Keywords:

Solution Type Technical Instruction Sure

Solution 1011830.1 : Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, and E6900 servers: How to run scextended Oracle Explorer Data Collector

Applies to:

Sun Fire 3800 Server - Version: Not Applicable and later   [Release: N/A and later ]
Sun Fire 4800 Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Fire 4810 Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Fire E6900 Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Fire 6800 Server - Version: Not Applicable and later    [Release: N/A and later]
All Platforms

Goal

This document describes how to run an scextended Oracle Explorer Data Collector on Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, and E6900 servers.

NOTE: This document does not cover Sun Fire[TM] 12K, 15K, E20K, or E25K servers.

Running scextended Oracle Explorer Data Collector on one of the Sun Fire[TM] systems listed in this document will collect information from the System Controllers (SCs).

The SCs have access to the hardware level error and configuration information.
The SC has a limited amount of memory to store error logs. The logs are lost if the SC is rebooted or power-cycled, so a loghost needs to be setup to prevent the loss of critical fault information which might be unavailable if an SC is reset or rebooted.

See Document 1008676.1 Best Practices' and configuring loghost on Sun Fire[TM] 3800,4800,4900,6800,and E6900 servers.

NOTES:

scextended explorer has to be run on a system that is able to telnet or ssh into the SC, preferably from the loghost.
Frequently, the domain(s) and the SCs are not on the same network. When this occurs, you might need to collect Oracle Explorer Data Collector data from the domain and scextended Oracle Explorer Data Collector information from the loghost for troubleshooting purposes.
Oracle Explorer Data Collector 5.7 is the suggested minimum for this server type because it collects the most SC information and is available for download from http://www.oracle.com/us/support/systems/premier/services-tools-bundle-sun-systems-163717.html

Solution

To run an scextended Oracle Explorer Data Collector, remember to perform the following from a system with telnet or ssh access to the SCs.

1) As the root user, run the following command:

 # /opt/SUNWexplo/bin/explorer -w default,scextended,fru

default - Runs the default Oracle Explorer Data Collector data collection modules on the system, if you only require SC info, omit this option.
scextended - Runs the SC data collection module.
fru - Causes the scextended module to also collect prtfru_-x.out which includes part number and serial number information as well as some very useful component history information. The fru option is enabled by default on Oracle Explorer Data Collector 5.0 and above.

2) When Oracle Explorer Data Collector reaches the scextended module you will be asked to enter the hostname of the SC.

Sep 16 11:12:03 wibble[3853] scextended: RUNNING
   You will be prompted for a System Controller name.
   If hostname cannot be resolved, please use IP address.
   Type return to end the list.

Please enter the name of the SC: host-sc0

3) You will then be required to enter the SC password.

Please enter the SC platform password for host-sc0:
     If there is no password for the SC, just press the Return key.

4) Once the data collection has completed for that SC you will be prompted to enter the name of the next SC (if there is one).

Please enter the name of the SC:
    If you do not want to collect data from another SC just press the Return key.

NOTE: No messages are output to the console during the scextended data collection, if you need to confirm data is being collected check for new files being created or updated in the /opt/SUNWexplo/output/explorer.../sc/ directory.

5) If you need to collect data from a larger number of SCs:

This can be done from a single Oracle Explorer Data Collector run. Add the SC hostnames and passwords to /etc/opt/SUNWexplo/scinput.txt file on the loghost or admin workstation (if it is able to telnet or ssh to all hosts).

Example /etc/opt/SUNWexplo/scinput.txt file:
# Input file for extended data collection
# Format is HOST PASSWORD
hostone-sc0 pa55w0rd
hosttwo-sc0 s3cur3

NOTE: If the scinput.txt file has entries the scextended module will not prompt for additional input when you execute it.

See Document 1002383.1 Oracle Explorer Data Collector for more information.
To view a Video Tutorial on how to execute scextended Oracle Explorer Data Collector on this type of system see How to collect scextended or 1280extended Explorer on Sun Fire[TM] v1280, 3800, 4800, 4810, 6800, E2900, E4900, E6900 and Netra[TM] 1280, 2900 servers.

Internal Comments
Additional References:

TSC Tools page: http://panacea.uk.oracle.com/twiki/bin/view/Tools/AllTools
Findaft: http://panacea.uk.oracle.com/twiki/bin/view/Tools/ToolPageFindaft
FindUE: http://panacea.uk.oracle.com/twiki/bin/view/Tools/ToolPageFindUE
Showfru: http://panacea.uk.oracle.com/twiki/bin/view/Tools/ToolPageShowfru
FindFMA: http://panacea.uk.oracle.com/twiki/bin/view/Tools/ToolPageFindfma

Information on collecting prtfru output from SCs without using Oracle Explorer Data Collector is detailed in:
Obtaining FRU Data information from a Sun Fire[TM] 3800/48X0/6800/4900/6900 Server
How to gather 'prtfru -x' info for Sun Fire[TM] xx00 platforms without having Sun[TM] Explorer installed

Previously Published As 44503

Attachments

This solution has no attachment