Exporting the Controller Log File
Does my controller support this feature? See Supported features.
The Export Log task exports the controller log to a text file. This log provides detailed information about the controller activities and can be useful for troubleshooting.
On a system running Microsoft Windows, the log file is exported to the windows or winnt directory. On a system running Linux, the log file is exported to the /var/log directory.
Depending on the controller, the log file name is afa_mmdd.log or lsi_mmdd.log or lsiexport.log, where <mmdd> is the month and date.
For PERC 12 and later controllers, the Export Log file name format is snapdump_<ctrl ID><snap dump ID><snap dump time stamp>.zip. On the VMware ESXi operating system, Storage Management stores the exported snapdump logs on a persistent scratch location. The persistent scratch location /scratch/log stores the snapdump log files, and the /var/log contains a link to the log file. If a persistent scratch location on the ESXi host is not properly configured, then VMware ESXi may experience intermittent issues due to lack of storage. For more information, see Creating a persistent scratch location.
NOTE: For PERC 12 and later controllers, the Export Log task may take longer time than expected, depending on the number of snap dump files on the controller. The
Export Log task is disabled when the log collection task runs in the background.
|
NOTE: For PERC 12 and later controllers, it is recommended to provide ten minutes duration between two snapdump log collections. If the
Export Log task is performed consecutively within ten minutes, and then a new log file may not be generated.
|
NOTE: In the VMware ESXi environment, only one log file is created (lsiexport.log). If the file exists, exporting the log file overwrites the existing log file.
|
NOTE: Controllers without cache cannot store logs and export log files.
|