- System configuration
- Vital product data, firmware, and UEFI configuration
DSA Portable creates a DSA log, which is a chronologically ordered merge of
the system-event log (as the IPMI event log), the integrated management
module (IMM) event log (as the ASM event log), and the operating-system
event logs. You can send the DSA log as a file to IBM Support (when
requested by IBM Support) or view the information as a text file or HTML
file.
Note: Use the latest available version of DSA to make sure you are using the
most recent configuration data. For documentation and download information
for DSA, see http://www.ibm.com/systems/management.
For additional information, see “IBM Dynamic System Analysis” on page 136
and Appendix C, “DSA diagnostic test results,” on page 515.
– DSA Preboot
DSA Preboot diagnostic program is stored in the integrated USB memory on
the server. DSA Preboot collects and analyzes system information to aid in
diagnosing server problems, as well as offering a rich set of diagnostic tests of
the major components of the server. DSA Preboot collects the following
information about the server:
- Drive health information
- Event logs for ServeRAID controllers and service processors
- Installed hardware, including PCI and USB information
- Light path diagnostics status
- Microprocessor, input/output hub, and UEFI error logs
- Network interfaces and settings
- RAID controller configuration
- Service processor (integrated management module) status and
configuration
- System configuration
- Vital product data, firmware, and UEFI configuration
DSA Preboot also provides diagnostics for the following system components
(when they are installed):
1. Emulex network adapter
2. IMM I2C bus
3. Light path diagnostics panel
4. Memory modules
5. Microprocessors
6. Optical devices (CD or DVD)
7. SAS or SATA drives
See “Running DSA Preboot diagnostic programs” on page 138 for more
information on running the DSA Preboot program on the server.
v Troubleshooting by symptom
These tables list problem symptoms and actions to correct the problems. See
“Troubleshooting by symptom” on page 140 for more information.
Chapter 4. Troubleshooting 125
To Next Page
Loading...
Need help?
General
