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

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-Exxk
 

Applies to:

Goal

This document describes how to collect a System Controller (SC) specific Explorer. The Explorer module sf15k_sc is completely re-written, starting with Services Tool Bundle (STB) 7.3.

It needs to have environment variable EXP_SMSUSER set, see below !!

This document applies to all Sun Fire Exxk servers, and describes the usage of the sf15k_sc  module of Explorer 7.3 (as part of STB7.3) or newer.

Solution

Upgrading to STB 7.3 on  Sun Fire Exxk (Starcat) Servers System Controller (SC)

For details on how to get hold of the latest version of Services Tool Bundle (STB), how to install and how to use it, reading Oracle Services Tools Bundle (STB) - RDA/Explorer, SNEEP, ACT [ID 1153444.1]  is a good starting point. To ensure your Explorer run is using the latest available modules,  and to ensure the Explorer defaults file is usable by Explorer 7.3, be sure to have run the following commands during the installation process:

Running Explorer on  Sun Fire Exxk (Starcat) Servers System Controller (SC)

Like on any other Oracle SPARC Server, you can run Explorer on the Sun Fire Exxk System Controller (SC), which is a Solaris host itself . When you run Explorer with the option -w sf15k_sc, it will collect all Sun Fire Exxk platform specific information from the System Controller. This specific set of data will be in the sf15k sub-directory of the host's Explorer. Previous version of the sf15k_sc module (STB7.2 and earlier) did create and remove the necessary users on the SC to be able to collect all domain specific information.

Starting with STB7.3 , the sf15k_sc module no longer does create and remove these users, instead it relies on an existing user on the SC with the appropriate privileges. For Explorer to be able to successfully run the sf15k_sc module, the environment variable EXP_SMSUSER must be set with the username that has the appropriate privileges. How to set EXP_SMSUSER, and what privileges is needs, is described in How to set EXP_SMSUSER .

How to set environment variable EXP_SMSUSER

This paragraph will describe how to set the value of environment variable EXP_SMSUSER to sms-svc. 

After installing STB7.3,  you first need to run "explorer -g" to generated a defaults file that is usable by Explorer 7.3. Starting with Explorer 7.0 the package  is distributed both as a SVR4 package and as an IPS package. The standard location for the output and configuration files is as follows:

• Solaris10:
  • the default output files location is /opt/SUNWexplo/output
  • the default configuration files location is /etc/opt/SUNWexplo
• Solaris11:
  • the default output files location is /var/explorer/output
  • the default configuration files location is /etc/explorer
• throughout this document  ${XPL_ETC} will be used to indicate the location of configuration files
• throughout this document  ${XPL_OUT} will be used to indicate the location of output files

One option for setting EXP_SMSUSER , is to set its value on the shell command line, before running explorer -w sf15k_sc :

To make the settings for EXP_SMSUSER persistant, you can add a line to the file ${XPL_ETC}/default/explorer :

Bear in mind that lines in  the file ${XPL_ETC}/default/explorer are treated like lines in a shell script, if they start with # they are considered comment lines and have no effect on Explorer. For more details on Explorer, please visit the explorer manual pages. Which privileges are needed by user EXP_SMSUSER is described in What privileges does user EXP_SMSUSER need .

What privileges does user EXP_SMSUSER need

User EXP_SMSUSER is an existing SMS user, that needs to have the following privileges setup, for the sf15k_sc module to run successfully:

• user EXP_SMSUSER must be a member of the platform administrator group; this memberships is shown as platadmn
• for each domain (A-R) user EXP_SMSUSER must be a member of the domain administrator group; this membership is shown as dmn<domain_id>admn
• membership of other groups (service, operator, etc. ) is not necessary, but is also not causing any problems with the sf15k_sc module

Final observations

If you don't get this to work, make the Explorer module more verbose, by running explorer -verbose -w default,sf15k_sc. If that does not clear up any confusion, you can turn on "tracing" in two ways:

• in the file ${XPL_ETC}/rdainput.txt you can add the line RDA_XPLR_TRACE="1"
• before running the explorer command, run EXP_TRACE_RDA=1 ; export EXP_TRACE_RDA

This will cause a very,very verbose run, with a ton of output, but it will tell you exactly what happens. After activating tracing, you can run /opt/SUNWexplo/bin/explorer -verbose -w default,sf15k_sc 2>&1 | tee -a /tmp/log.txt  . All screen output will be in the specified output file, there might be a clue in the trace output just before any issue you experience.

What can go wrong ? Some example output of common mistakes that can happen ...

User EXP_SMSUSER is not set, the sf15k_sc module will not collect anything, it will result in an explorer without a sf15k directory:

User EXP_SMSUSER does not have platform administration privileges, the sf15k_sc module will not collect anything, it will result in an explorer with an empty sf15k directory:

User EXP_SMSUSER does not have domain privileges for one of more domains, for these domains the domain specific information is not collected by the sf15k_sc module, the matching ./sf15k/<domain_id> directory in the explorer output will be empty, the below output shows an Explorer collect, where EXP_SMSUSER did not have domain privileges for domain E:

You think you are running Explorer on the main SC, but in fact you are running Explorer on the spare SC. You think Explorer is broken, but it is not. Being on the spare SC, only a few commands will be completed successfully, this is how a sf15k directory looks on the spare SC:

This is how the output of a successful run looks:

 

explorer, sf15k_sc, Starcat

This solution has no attachment