How to export the RAID log with OpenManage Server Administrator (OMSA)

How to export the RAID log with OpenManage Server Administrator (OMSA)


OMSA - Open Manage Server Administrator

How to export the RAID log

In case of any troubleshooting, with or without the technical support, it is really useful and in some cases essential for finding the failure.
Note: To prevent any issue regarding the export of the log, please set your browser language to English. Otherwise you may end up in a white page (see Figure 1).


Error with foreign browser language
Figure 1: Error with foreign browser language

First open OMSA and log in. Now navigate to Storage. The function to export the log is found in the dropdown list "Available Task".

Storage Overview
Figure 2: Storage Overview

Task: Export Log
Figure 3: Task: Export Log

After selecting "Export Log ..." click Execute, the next page shows the export information. It shows where the file finally is saved.

Log - hostname and destination
Figure 4: Log - hostname and destination

Finally click Export Log File - we're done for now.

Now we have exported the log, and we know where it is saved, but what shall we do next? - Right, we need to connect to the server.
There are different ways to get the file. The easiest way - in my opinion - is a Windows Remote Desktop Connection.

Remote Desktop Connection with the host server
Figure 5: Remote Desktop Connection with the host server

On the host server navigate to the destination what was shown in OMSA - C:\Windows - and search for a file that looks like this lsi_<Month und Day>. In my example the files name is lsi_0305.

Log at host server in C:\Windows
Figure 6: Log at host server in C:\Windows

Finally - the exported RAID-Log.

the RAID-Log
Figure 7: The RAID-Log

We can now share, export or send the file - for any further troubleshooting purposes.




Article ID: SLN311082

Last Date Modified: 08/13/2018 08:00 AM


Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.