Contidos dentroLocalizar Mais DocumentaçãoDestaques de Recursos de Suporte | Fazer download desta apostila em PDF (530 KB)
Frequently Asked QuestionsThis document provides answers to questions about SunTM Explorer. Note – Sun Explorer includes some third-party redistributable software. Please read the Chapter 1, Sun Explorer Third Party License Agreement, in Sun Explorer Third Party License Agreement to learn about the terms and conditions under which this software is included and is available for use. The following books contain additional information about Sun Explorer: For questions about Sun Explorer, contact the explorer@sun.com alias. About Sun Explorer Downloading and Installing Sun Explorer
Using Sun Explorer
Getting Additional Information About Sun ExplorerQuestion:What is Sun Explorer? Answer:Sun Explorer is a data collection tool. The tool comprises shell scripts and a few binary executables. Question:What architecture or machines does Sun Explorer run on? Answer:Sun Explorer currently runs on SolarisTM SPARC® and Solaris x86 architectures. Question:What's changed since the last version of Sun Explorer? Answer:See the CHANGES file in the explorer_install_dir/doc directory, which describes all the changes since the last release of Sun Explorer. Question:What scripts and commands does Sun Explorer run? Answer:This varies from version to version. Most of the scripts that Sun Explorer runs are located in the explorer_install_dir/tools/ directory. You can get a list of all the collected files and executed commands if you specify the following option on the command line:
The resulting file contains the list of all files and commands collected by each Sun Explorer module. For more information, see Chapter 3, Sun Explorer Commands, in Sun Explorer User’s Guide. Question:Does Sun Explorer support command-line arguments? Answer:Yes. Sun Explorer supports many command-line arguments. To find out what arguments the current version of Sun Explorer supports, consult the man page:
More information is available in the README.man file, which is located at:
Downloading and Installing Sun ExplorerQuestion:How do I get Sun Explorer? Answer:The Sun Explorer is distributed on the Services Tools Bundle (STB) and is made available via its download link. Use the following procedure to download the latest Services Tools Bundle:
How do I install Sun Explorer? Answer:See the installation procedures in Chapter 1, Sun Explorer How-To’s (FTP, NFS, Installation, Upgrade), in Sun Explorer User’s Guide. Question:How much space does the target Sun Explorer output directory require? Answer:The target directory for Sun Explorer output must satisfy at least one of the following conditions, or else Sun Explorer will not run:
Do I have to delete and re-install the SUNWexplo and SUNWexplu packages to update Sun Explorer to the latest version? Answer:It depends whether you are updating the Image Packaging System (IPS) format of Explorer.
Is there a way to install one copy of Sun Explorer and share it among all my systems? Answer:Yes. Install Sun Explorer on an NFS-exportable file system and mount that file system on the other systems on which you want to run Sun Explorer. You need to create a defaults file for each system on which you will be running Sun Explorer. Create one file with the common information in it, and make copies for each system on which you want to run Sun Explorer. The best approach would be to use the host ID in the file name for the defaults file. For each defaults file, enter the machine-specific information. (The defaults file is easy to read and follow.) If any of the client systems run Solaris 7 or older, make sure the NFS installation used the EXP_NFS_DEPLOY option. See How to Install Sun Explorer Manually in Sun Explorer User’s Guide When you are ready, you can run Sun Explorer on each of the systems by using the following syntax along with any other options you want to use:
Sun Explorer can also be run using cron as long as the NFS mount is accessible when the cron job runs. See How to Run Explorer With NFS in Sun Explorer User’s Guide. You can also specify serial numbers and platform names for all systems in one defaults file. See the description of the EXP_SERIAL_hostid variable in the explorer(4) manual page. Question:How do I opt-out of the Service Tag Module ? Answer:Run explorer as ./explorer -w \!servicetags Question:Can Explorer be installed via Jumpstart successfully? Answer:Yes, Explorer can be installed via Jumpstart successfully. However, during the Jumpstart installation some system resources, like crontab, are not available. In such cases appropriate warning message will be displayed on the console. In case of 'crontab' example, Explorer installation will throw the following message to the console: 'Cron process is not running hence skipping cron related operations' Using Sun ExplorerQuestion:How do I mask my IP addresses? Answer:Sun Explorer 3.5 and later releases allow for the masking of IPv4 addresses. Sun Explorer 4.3 and later releases allow for the masking of IPv6 addresses. To mask IP addresses, use the following commands:
What's that “defaults” file and can I get rid of it? Answer:The defaults file (/etc/opt/SUNWexplo/default/explorer) is used to gather customer information. This file is created during the installation of package SUNWexplo before the Sun Explorer 4.3 release. After Sun Explorer 4.3, the defaults file is created and updated by the explorer -g command. Sun Explorer cannot run without the defaults file, and the version of the defaults file must match the version of the package. The file is used to provide valuable information so that the Sun Explorer data can be retrieved more easily by Field Engineers and System Support Engineers. The defaults file should not be removed. Sun Explorer notifies you when fields are missing from the defaults file. More information on the defaults file format is available in the explorer(4) man page.
My machine locks up when running a script. How do I disable the script? Answer:Because Sun Explorer can stress the system, it might uncover an operating system bug. In this case, you can disable a module temporarily or permanently.
Is there a way to improve Sun Explorer's run time? Answer:Sun Explorer's run time is a function of the server it is running on. Servers with many disks run substantially longer than servers with a small number of disks. Servers under a heavy load also run longer than servers with lighter I/O. Sun Explorer allows individual data gathering modules to be excluded or groups of modules to be excluded. For data gathering on a scheduled (weekly) basis, if possible, exclude the network and storage modules:
See Sun Explorer Modules in Sun Explorer User’s Guide to determine which modules will be skipped. Question:Why does the t3 module run so long? Answer:The t3 script checks each disk to determine if it is a SUN-T3 model. This check takes longer on servers with a large number of disks than on servers with a small number of disks. This check is done even if no SUN-T3 disks are attached to the server. If the server does not have any SUN-T3 disks attached, this module can be excluded from the Sun Explorer runs as follows:
Why does the t3extended module run so long? Answer:The t3extended script logs in to the T3 array for each command. No alternative other than streaming four to six commands per telnet session is provided. For servers with a large number of T3 arrays attached, this process takes a considerable amount of time. If possible, avoid running the t3extended module as part of the scheduled (weekly) Sun Explorer run as follows:
Why is Greenwich Mean Time (GMT) used by Sun Explorer and included in the Sun Explorer output file name? Answer:Sun Explorer uses the GMT time format to allow processing of Sun Explorer files from all over the world. Using one time format allows Sun to know exactly when each Sun Explorer process was run without performing time conversions. Converting the time would require that the Sun Explorer output file be parsed and the TZ variable extracted. Question:How will my Sun Explorer data be used? Answer:Information gathered from customer machines is transmitted to Sun and stored to enable faster, more effective diagnosis and customer support. The data is also reviewed in the aggregate, without reference to individual customers, for planning future offerings and enhancements. Question:Is my Sun Explorer data safe and secure? Answer:Data can be transmitted using the secure Net Connect transport (encrypted) or via the HTTPS Sun Explorer upload tool (see How do I submit my Sun Explorer output to Sun?). Once the data is received, Sun protects it to the same high standards it applies to its own information resources. Data storage machines are tightly secured and both physical and electronic access to the machines is restricted to approved support personnel only. Removal or sharing of any data outside of Sun is not permitted by Sun's Data Stewardship policies. Only internal Sun employees and approved contractors can access the stored Sun Explorer data, which is controlled by Sun's internal network-access control policy. Question:I have tools that use the Sun Explorer output. The format of the output has changed. Why? Answer:The output format from Sun Explorer is based largely upon the output from system commands. If those commands have different output when a new version or bug fix comes out, then the Sun Explorer output will also change. Question:How do I submit my Sun Explorer output to Sun? Answer:Sun Explorer output can be submitted to the proactive database using HTTPS, email, or FTP. For HTTPS transfer, there are two methods:
For email transfer, use one of the following email addresses:
For FTP transfer, see How do I use FTP to transfer my Sun Explorer output? You can also use multiple transport options with explorer, for example:
Is proxy support available when I configure Sun Explorer to send its output automatically by way of HTTPS? Answer:Yes. Sun Explorer 5.5 and later uses curl for HTTPS upload support. The HTTPS_PROXY environment variable allows curl to use a proxy server. The following example shows how to use the HTTPS_PROXY environment variable:
Explorer 5.7 and later enables you to run the Explorer -g command that asks for proxy server information so you no longer need to set HTTPS_PROXY yourself. For more information about curl, see http://curl.haxx.se/docs/manpage.html#ENVIRONMENT. Question:How do I use FTP to transfer my Sun Explorer output? Answer:To configure Sun Explorer to use FTP as a transport, the /.netrc file needs to be created and populated with the destination site. The /.netrc file should be mode 600 (-rw-------). Here is an example entry:
For destination sites, see How to Use FTP to Submit Sun Explorer Files in Sun Explorer User’s Guide. The following command transfers the explorer output using FTP:
Is there a way for me to run an analysis on the Sun Explorer output myself? Answer:Analysis reports for Sun Explorer submitted through Sun Net Connect can be obtained with Sun System Analysis, which is a for-fee service. For Platinum contracts, subscription to Sun System Analysis is included into the contract. Regular Sun Explorer analysis is also done as a part of Sun Preventive Services program. Results from Sun Explorer submissions can also be obtained from your local Field Engineer or System Support Engineer. You can also view the raw text files, which are located at:
What is munpack and why do I need it? Answer:The munpack utility is a freeware utility used to decode MIME messages. Because Sun Explorer can come in multiple parts, a tool is needed to put the MIME messages together into the original explorer tar file. The munpack utility is available for download at ftp://ftp.andrew.cmu.edu/pub/mpack/. Question:I received Sun Explorer output in multiple parts. How do I get the tar file? Answer:Sun Explorer 3.5 and later splits large Sun Explorer outputs into multiple parts to pass through mail servers with size limits. Instructions for dtmail:
Instructions for other mail readers:
What is causing my email submission of Sun Explorer output to be rejected by Sun external mail servers? Answer:While there a several possible causes, one possibility is a reverse-lookup failure. All email directed to Sun is reverse-address checked. If the sender's return address is not a valid, reachable address, the email is rejected. Before sending an email, verify that your return email address can be accessed externally. Question:How do I add or edit a Sun Explorer cronjob? Answer:Run the explorer -gcommand to add or edit a Sun Explorer cronjob. When prompted about whether you want to schedule running Sun Explorer in cron, answer yes. You can choose to schedule running Sun Explorer on a weekly basis or on a monthly basis. Sun Explorer adds an entry in the root crontab file. The following are example crontab entries:
To modify an entry, use the crontab (1) command. Question:How do I delete a Sun Explorer cronjob? Answer:Sun Explorer version 5.4 to 5.13 deletes any crontab entry that contains trailing comment #SUNWexplo during removal of Explorer. Moreover, it deletes old cron entry when you run explorer -g and opt to not schedule the cron job. Explorer 6.0 onwards asks you if you want to save the cron entry for future use during cron entry creation. If you opt to save it, Explorer leaves the cron entry commented out during removal; otherwise, it removes the entry. Explorer looks for the exact executable with full path to identify the cron entry, instead of the trailing comment #SUNWexplo. Question:How can I set up Sun Explorer to run weekly, but send a copy of the summary information only to myself? Answer:Modify the superuser's crontab entry with any of the following options (that is, explorer -E myaddress@mycompany.com).
How can I run a particular module or group in interactive mode? Answer:To run an individual module in interactive mode, use -w <module name>. To run a group in interactive mode, specify the keyword interactive with the group alias. Note – Interactive mode can be used only if the configuration file (*input.txt) does not contain information. Question: How do I run all the modules? Answer:Use the explorer -w all command. Question:Where can I find the output of an IPS command, pkg info -l? Answer:The output can be found in the <explorer output directory>/patch+pkg/pkg_info-l.out file. Question:How do I run Explorer in OpenSolaris? Answer:In OpenSolaris, Explorer is packaged and installed differently than on other operating systems; however, the commands and various options used to run Explorer remain the same. Question:Is there a way to push Explorer images in the destination specified by supportfiles.sun.com? Answer:Yes, by using the -hd option:
Can Explorer be installed in alternate path and still be used? Answer:To use Explorer from an alternate path, complete the following steps. For detailed information about installing and using Explorer in an alternate path, see How to Use Explorer from an Alternate Path in Sun Explorer User’s Guide.
Can I install Explorer in pkg(5) form? Answer:Explorer supports pkg (5) standard of packaging mechanism from 6.0 onwards and can be installed using STB for OpenSolaris bundles. Question:What happens to the legacy packaging mechanism (SVR4) followed by Explorer? Will Explorer be still available in that form? Answer:In addition to being delivered in pkg(5) form, Explorer will continue to be delivered as an SVR4 package. Question:Can I get an on-disk distribution of Explorer in pkg(5) form? Answer:No. pkg(5) or the Image Packaging System (IPS) does not support on-disk distribution of packages at this time. Explorer must be published first to a Depot server and must be installed from there using the STB for OpenSolaris bundle. Question:Does pkg uninstall SUNWexplo/SUNWexplu for Image Packaging System (IPS) do the same as pkgrm SUNWexplo/SUNWexplu does in SVR4? Answer:No, IPS packaging mechanism does not support or invoke any script during pkg uninstall, so pkg uninstall cannot remove the cron job for Explorer automatically. A new command line option, explorer -clean has been provided to uninstall Explorer pkg(5), remove all traces of Explorer including configuration files and cron entry. This command should be run to remove the application completely. For upgrading to a higher version of Explorer pkg(5), removal of configuration files and cron entry are not required. Question:Does Explorer collect write cache status data? Answer:No, starting from 6.1 Explorer does not collect write cache status data. Though the write cache status data is important in the diagnosis of data integrity and performance issues, it causes unwanted failover behavior in some Veritas DMP configurations. Hence, this function collect_writecache has been commented out. If this data is important in some user specific need, you can collect the write cache status data by un-commenting the function call, collect_writecache in the disks module located under tools/disks. Question:What should I do if Explorer fails to capture ILOM snapshot data on T5120/T5140/T5220/T5240 systems? Answer:Explorer needs a user with admin privileges in order to connect to ILOM to execute snapshot command. For information on how to create such user in ILOM kindly refer to "Managing User Accounts" section of "Integrated Lights Out Manager (ILOM) Administration Guide Question:Can explorer handle output files that are of 2GB or more in size? Answer:Yes, Explorer 6.3 and higher versions bundle large file aware gzip binary (gzip 1.3.9). This gzip binary is capable of handling large files that contains 2GB or more data. Note – If system already has a gzip installed, the bundled gzip utility will not be installed on the host. Question: I have the most recent version of Explorer installed on my system. The rprtfru output (prtfru_-x.out) on my system shows "unrecognized value" for some vendors. Why? Answer:Explorer 6.3 has updated the bundled rprtfru binary. It recognizes all of the vendors who are listed in the recent libfrureg.so.1 library. rprtfru will not detect other unregistered vendors and will thus tag them as 'unrecognized value'. Question:Can I run Explorer on sparc 7 machine? Answer:Explorer 6.3 (and higher) does not support sparc 7. However you can run explorer by installing gzip on your system. Question:Why is the 'System Type' field in the Explorer README file is empty on my machine? Answer:You are probably running explorer X86 9 or below. smbios command output, which explorer uses for parsing system type, may return empty string in these architectures. Question:have read that explorer now has its own module for collecting serial number. What is the module and where is this serial number stored? Answer:Explorer 6.3 and higher versions has a new module 'platform_serial' which attempts gathering serial data from various data sources. The output is stored in sysconfig/platform_serial file on the explorer output directory. Question:Serial number collected by explorer 'platform_serial' module is different from that in Explorer README. Why is that so? Answer:The README file and the platform_serial module have their own data sources from where explorer attempts to gather serial number. During certain scenarios these sources can contain different serial data and hence the difference. Most of the time, the data collected by 'platform_serial' module will be the latest and correct one. There is already a Change Request in Explorer to make the serial data consistent between the README and platform_serial files. It will be fixed in the future release of Explorer. Getting Additional InformationQuestion:Where are the Sun Explorer man pages? Answer:Sun Explorer's man pages are located in explorer_install_dir/man. A summary of Sun Explorer's man pages is in explorer_install_dir/doc/README.man. To view the man pages, use the following commands:
Where can I submit my questions about Sun Explorer? Answer:For questions about Sun Explorer, contact the explorer@sun.com alias. |
||||||||||||||||