|Oracle® Explorer Data Collector User's Guide
Release 6.9 for Oracle Solaris
Part Number E21076-05
|PDF · Mobi · ePub|
This section provides information about the changes made in Oracle Explorer Data Collector Release 6.9, including a description of the new features, a description of the modified features, and a list of the defects and requests for enhancement (RFEs) implemented in the tool.
Note:Oracle Explorer Data Collector includes some third-party redistributable software. Please read the third-party license readme to learn about the terms and conditions under which this software is included and is available for use.
For installation and download information, see "Oracle Explorer Data Collector Installation".
The following notices apply to Oracle Explorer Data Collector Release 6.9:
Solaris 8 and 9 Operating System (Solaris OS) patch requirements. On Sun Fire 15K platforms, you must apply the following patches to run the fru script:
Solaris 8 OS, at least patch 110460-23 or 108528-29
Solaris 9 OS, at least patch 112959-01
Oracle Explorer and shared storage: Running Oracle Explorer and RAID Manager (RM) diagnostic commands simultaneously can cause controllers to go offline. Furthermore, running Oracle Explorer, healthck, drivutil, or other diagnostic commands simultaneously on host servers that share Oracle StorEdge A1000, A3x00, or A3500FC storage devices can cause data corruption.
You can collect information from shared disk storage without causing a problem by running Oracle Explorer from only one server host. Alternatively, you can run Oracle Explorer from more than one host server as long as you run Oracle Explorer from each host server at staggered times.
To configure Oracle Explorer data collection from multiple host servers at staggered times, run the following command on each server and then, when prompted, enter different values for the time when Oracle Explorer should run: explorer -g
A third option is to not include Oracle Explorer storage modules when you run Oracle Explorer on servers that share disks. To exclude storage modules from one of the host servers, run Oracle Explorer with the -w command-line option in one of the following ways:
For sh or ksh: -w !storage
For csh or bash: -w \!storage
Use of SSH with the Oracle Explorer scextended module. Before you can collect information from a Sun Fire midframe system controller, you must manually accept the SSH host key from the system controller. To accept the SSH host key, use SSH to login to the system controller (as superuser) from the system that is collecting data.
Space characters in passwords. Any space characters are supported in interactive mode for most modules collecting data from external systems (exceptions: ipmiextended, ilomextended). For automated collection using *input.txt files, space characters can be used in the middle of passwords for most modules (exceptions: sanextended, b1600extended, b1600switch). Leading/trailing spaces in passwords are not supported in any *input.txt files.
For some of the Explorer modules Explorer uses the Remote Diagnostic Agent (RDA). So, to collect all Explorer information it is mandatory to install RDA. Note that the Services Tool Bunlde (STB) bundles the installation of RDA and Explorer.
The following are some of the new features available in Oracle Explorer Data Collector Release 6.9:
The following Oracle Explorer modules were improved:
The following bugs and requests for enhancement (RFEs) are implemented in Oracle Explorer Data Collector Release 6.9:
|Oracle Bug 12327367||
|Remove e-mail transport option to submit data to 'email@example.com' alias|
|Oracle Bug 12921378||RAIDmanager||Need to gather LSI RAID logs and status on X2 (X4170) with MEGACLI|
|Oracle Bug 12932049||ipmi||LED status i snot reported if system has firmware of V3.0.X.X|
|Oracle Bug 12976289||sysconfig||Add output of
|Oracle Bug 13251012||ndd||Protocol SCTP does not have same level of support as TCP or UDP in Explorer|
|Oracle Bug 13359629||etc||