IBM Support

How to Extract PERC Controller Log via OpenManage Server Administrator - OMSA

How To


Summary

Exporting RAID Controller Logs from OMSA

Objective

This article explains how to export RAID controller logs from OpenManage Server Administrator (OMSA) using both the graphical user interface (GUI) and the command line interface (CLI). The logs can be useful for troubleshooting and monitoring the health of the RAID controller.

Steps

Exporting RAID Controller Logs using the GUI

To export the RAID controller logs using the GUI, follow these steps:

  1. Log in to OMSA.
  2. Highlight the Controller on the left panel and click on Information/Configuration.
  3. On the next screen, scroll down to Controller Tasks and click on the drop-down menu. Select Export Log.
  4. Click on Execute.
  5. On the next screen, scroll down and click on Export Log File.
  6. The export file can be found in the following locations:
    • Linux: /var/log/lsi_Date.log
    • Windows: C:\Windows\lsi_Date.log
    • Citrix Xen Server: /var/log/lsi_Date.log
    • ESX5: /var/log/lsiexport.log

Note: Alternatively, you can use the following command via CLI: omconfig storage controller action=exportlog controller=0

Exporting RAID Controller Logs using the CLI

To export the RAID controller logs using the CLI, follow these steps:

  1. Open a Terminal (Linux) or DOS window.
  2. Enter the following command line to identify the id of the concerned controller:
omreport storage controller
Extract the log of the controller with the following command. The ID represents the identifier of the controller, e.g. 0 for PERC H700 or 1 for PERCH800. If you have only one controller in the server, you can directly enter 0:
omconfig storage controller action=exportlog controller=id

For example:

omconfig storage controller action=exportlog controller=0
The log file LSI_Date.log will be saved in the specified directory:
  • For Windows: C:\Windows
  • For Linux: /var/log

Note: The above commands work for Perc 5 i/E, Perc 6 i/E, Perc H700, Perc H800, and Perc H710 H710P.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB66","label":"Technology Lifecycle Services"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSFBM70","label":"MVS Server - Dell"},"ARM Category":[{"code":"a8m3p000000PCWcAAO","label":"MVS Server-\u003EDell x86-\u003EPoweredge Blade-\u003E10"},{"code":"a8m3p000000PCWgAAO","label":"MVS Server-\u003EDell x86-\u003EPoweredge Blade-\u003E11"},{"code":"a8m3p000000PCWhAAO","label":"MVS Server-\u003EDell x86-\u003EPoweredge Blade-\u003E12"},{"code":"a8m3p000000PCWlAAO","label":"MVS Server-\u003EDell x86-\u003EPoweredge Blade-\u003E8"},{"code":"a8m3p000000PCWmAAO","label":"MVS Server-\u003EDell x86-\u003EPoweredge Blade-\u003E9"},{"code":"a8m3p000000PCWIAA4","label":"MVS Server-\u003EDell x86-\u003EPoweredge Rack-\u003E10"},{"code":"a8m3p000000PCWJAA4","label":"MVS Server-\u003EDell x86-\u003EPoweredge Rack-\u003E11"},{"code":"a8m3p000000PCWYAA4","label":"MVS Server-\u003EDell x86-\u003EPoweredge Rack-\u003E12"},{"code":"a8m3p000000PCWjAAO","label":"MVS Server-\u003EDell x86-\u003EPoweredge Rack-\u003E8"},{"code":"a8m3p000000PCWfAAO","label":"MVS Server-\u003EDell x86-\u003EPoweredge Rack-\u003E9"},{"code":"a8m3p000000PCWMAA4","label":"MVS Server-\u003EDell x86-\u003EPoweredge Tower-\u003E10"},{"code":"a8m3p000000PCWNAA4","label":"MVS Server-\u003EDell x86-\u003EPoweredge Tower-\u003E11"},{"code":"a8m3p000000PCW5AAO","label":"MVS Server-\u003EDell x86-\u003EPoweredge Tower-\u003E12"},{"code":"a8m3p000000PCWLAA4","label":"MVS Server-\u003EDell x86-\u003EPoweredge Tower-\u003E8"},{"code":"a8m3p000000PCWPAA4","label":"MVS Server-\u003EDell x86-\u003EPoweredge Tower-\u003E9"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}]}]

Historical Number

8

Document Information

Modified date:
25 September 2025

UID

ibm17150563

Page Feedback