Understanding The Diagnostics Collection Process - Dell DR4000 Administrator's Manual

FILE LOCATION: C:\Users\bruce_wylie\Desktop\Dell
Docs\~Sidewinder_Docs_DR4000\FRAME_Conversion_DR4000_AdminGuide\~DR4000_AG_F
The Diagnostics service works by collecting all the system-related information
that could help when diagnosing a problem or error condition in the system.
For more information about diagnostics log file bundles, see "About the
Diagnostics Page and Options" on page 76.
Diagnostics runs as a service during system startup, and this process listens
for incoming requests. There are two modes in which the diagnostics
collection process is started:
• Admin-Generated mode: when a DR4000 CLI or DR4000 GUI request
is made by the administrator (and the default reason that is listed is
admin-generated).
Auto-Generated mode: when a process or service failure is reported, the
•
DR4000 system starts collecting system-related information. After it
completes the auto-generated collection, it generates a system event.
When a log directory exceeds the maximum storage capacity, the oldest logs
are automatically deleted. The DR4000 system GUI lets you download and
save diagnostics log files to other systems on your network.
For more information, see "Downloading Diagnostics Log Files" on page 76,
and "Generating a Diagnostics Log File" on page 77.
NOTE:
When you generate a diagnostics log file bundle, it contains all of the
DR4000 system information that may be needed when contacting Dell Support for
technical assistance.
The diagnostics log file bundle collects the same type of hardware, storage,
and operating system information as is collected when using the Dell System
E-Support Tool (DSET) from the system using the DR4000 system CLI
commands (diagnostics --collect --dset).
The DSET-based information that gets collected for the system can be used
by Dell Support to troubleshoot or evaluate your DR4000 system.

Understanding the Diagnostics Collection Process

The Diagnostics service collection tool process observes the following
guidelines:
• System triggers cause the automatic diagnostic log collection of system
status for any system process or service failures.
• All automatic diagnostic collection requests are queued and executed
sequentially.
D E L L C O N F I D E N T I A L – P R E L I M I N A R Y 1 / 1 0 / 1 2 - F O R P R O O F O N LY
Troubleshooting and Maintenance
113