Asset ID: |
1-71-1431330.1 |
Update Date: | 2018-03-23 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1431330.1
:
How to Collect Operating System Data to Troubleshoot Oracle X86 Platforms
Related Items |
- Sun Fire X4150 Server
- Sun Blade X6450 Server Module
- Sun Fire X2200 M2 Server
- Sun Fire X4540 Server
- Sun Fire V20z Server
- Sun Fire X4440 Server
- Sun Blade X6240 Server Module
- Sun Fire X4200 Server
- Sun Fire X4275 Server
- Sun Blade X6220 Server Module
- Sun Fire X4250 Server
- Sun Blade X6270 Server Module
- Sun Blade X6440 Server Module
- Sun Fire X4240 Server
- Sun Fire X4140 Server
- Sun Fire X2270 Server
- Sun Fire X4470 Server
- Sun Fire X2250 Server
- Sun Fire X4170 Server
- Sun Fire V40z Server
- Sun Blade X6250 Server Module
- Sun Blade X6275 Server Module
- Sun Fire X2100 M2 Server
- Sun Fire X4640 Server
- Sun Blade X6420 Server Module
- Sun Fire X4600 Server
- Sun Fire X4270 Server
- Sun Fire X4100 Server
- Sun Fire X4170 M2 Server
- Sun Fire X4450 Server
- Sun Fire X4500 Server
- Sun Fire X4800 Server
- Sun Fire X2100 Server
|
Related Categories |
- PLA-Support>Sun Systems>x86>Server>SN-x64: MISC-SERVER
- _Old GCS Categories>Sun Microsystems>Servers>x64 Servers
|
In this Document
Applies to:
Sun Fire X4540 Server - Version Not Applicable and later
Sun Fire X4140 Server - Version Not Applicable and later
Sun Fire X4170 M2 Server - Version Not Applicable and later
Sun Fire X2250 Server - Version Not Applicable and later
Sun Fire X4150 Server - Version Not Applicable and later
Information in this document applies to any platform.
Goal
Collect Operating System Data to Troubleshoot x86 Platforms.
Solution
Check platform health at Operating System levelOracle x86 systems support Oracle Solaris™, Red Hat Enterprise Linux, SuSE Enterprise Linux and the Windows operating system.
When troubleshooting an issue on these platforms it can be useful to verify if any hardware or software issue has been reported at O/S level and if platform related patches are up-to-date.
The following O/S specific commands are tools that collects information about each operating system, such as what kernel is running, currently loaded drivers, configuration files, log files, etc. Each of these tools must be collected as root, the output archive will be generated under /tmp
Generate an Oracle Explorer Data Collector Utility output with the command:
# /opt/SUNWexplo/bin/explorer
Oracle Explorer software is a support tool used to collect pertinent data from a system running the Oracle Solaris™ Operating System. Oracle engineers use Explorer to describe a system's configuration or to troubleshoot a problem.
Oracle Explorer is part of the STB (Services Tools Bundle) that can be downloaded from My Oracle Support (MOS):
http://support.oracle.com -> Search for "Services Tools Bundle" in the upper right Global search box
More details about Oracle Explorer, Services Tools Bundel and available options:
Oracle Services Tools Bundle (STB) - RDA/Explorer, SNEEP, ACT (Doc ID 1153444.1)
Execute SuSE Linux Enterprise Server supportconfig utility:
# supportconfig
For more options refer to the manual pages:
# man supportconfig
Execute Red Hat Enterprise Linux sosreport utility/:
# sosreport
For Red Hat Enterprise Linux 4.5 and earlier use sysreport instead.
Refer to the manual pages for more options:
# man sosreport
Execute VMware vm-support utility:
# /usr/bin/vm-support
For more information refer to VMware knowledge document:
Collecting diagnostic information for VMware Server
kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1967
Windows MPS Report utility
Download and install the MPS_REPORTS utility from the Microsoft Download Center:
https://www.microsoft.com/en-us/download/default.aspx
Core dump generation
To troubleshoot a system hang and define if the problem is hardware or software related it is recommended to collect a crash dump. Instructions on how to configure and initiate forced crash dumps for Solaris are described in the following MOS document:
Solaris[TM] Operating System: How to force a kernel core dump on an x86 system (Doc ID 1003085.1)
Some Oracle x86 platforms have an NMI switch at the back of the system that generates an interruption to stop the Operating System and force a core dump. The NMI interruption can be generated as follow:
- Pressing the NMI physical button at the back of the server
- Using the ILOM web GUI "Generate NMI" button located under the diagnostic tab
- Executing the command below at ILOM prompt:
-> /HOST generate_host_nmi=true
Note that NMI data collection must be configured to collect a core dump in case of interruption. Refer to your Operating System documentation if required.
To assist with possible system hang refer to the following document:
How to check if your x86 platform "system hang" actually is a system hang (DocID 1012991.1)
Caution: Before reviewing O/S related data it is also recommended to verify if the Operating System installed is supported or certified for this particular Oracle x86 Server to avoid any driver or compatibility issue.
For other Operating Systems refer to the third-party support vendor to get the procedure about how to collect a crash dump.
References
<NOTE:1003085.1> - Solaris[TM] Operating System: How to force a kernel core dump on an x86 or x64 system
<NOTE:1010057.1> - How to gather information on SuSE Linux Enterprise Systems
<NOTE:1010058.1> - How to Gather Information on Red Hat Enterprise Linux Systems
<NOTE:1010936.1> - Microsoft Windows and Linux operating systems: How to obtain troubleshooting information
<NOTE:1012991.1> - How to Check if your Oracle X86 platform "system hang" Actually is a System Hang
<NOTE:1312847.1> - Oracle Explorer Data Collector Resource Center
Attachments
This solution has no attachment