Unsolved
This post is more than 5 years old
1 Rookie
•
47 Posts
0
195738
September 16th, 2008 22:00
PE1650: How do I clear the IPMI System Event Log?
I have a PowerEdge 1650 on which I am trying to run memory diagnostics. By default, the memory diagnostic program, mpmemory.exe, searches the system event log as its first test. On this particular 1650, the message, "The event log has overflowed and needs to be cleared" appears and memory diagnostics exits. (There is also a message which reads, "No existing memory related problems were found." Probably because no memory diagnostics actually ran.)
I have tried to run memory diagnostics manually with the various /t switches, but not matter which ones I tell mpmemory to run, it starts with the event log scan, and then fails. This happens even if I don't indicate that I want the event log scan to run. It just does . . . every time. It seems to be genetic to mpmemory.
How do I get past this? Do I need to clear the server's event log? If so, how do I do that?
Update: When I run Dell diagnostics on Custom Test: System Management: IPMI: IPMI System Even Log Check, the test passes but with the message, "WARNING System Event Log is Full." So, I'm stymied. I have to clear this log but cannot figure out how.
Other info:
(1) There is no OS on this server.
(2) There is no Dell utility partition on the server's hard drive. I wiped the disk.
(3) I downloaded the latest diagnostics from Dell's website. It is running mpmemory V1064.
(4) It appears to have a DRAC or ERA/O installed, but I don't see a configuration screen during boot or in the BIOS, and, if I plug that port into a switch, none of its connectivity LEDs light up.


Larry Mateo
1 Rookie
•
47 Posts
0
September 17th, 2008 18:00
Here's the solution to my problem:
This document explains how to clear system logs: http://support.dell.com/support/topics/global.aspx/support/dsn/document?c=us&l=en&s=gen&docid=2F3292A7757843FAB033D6A60258F9FA&journalid=571460B19996E649E040AE0AB7E1457E&Query=RFNFVA==&SystemID=PWE_PNT_PIII_1650&ServiceTag=&contenttype=-1&os=-1&component=-1&lang=-1&doclang=en&toggle=false#2
There are three methods:
(1) Via a DRAC or ERA connection.
(2) Using the Dell DSET utility. DSET means Dell System e-Support Tool. It may be found under the "Drivers and Downloads" web page for the server. Select "Systems Management" and then "System E-Support Tool."
(3) Using OpenManage Server Administrator (OMSA). This is found on the "Systems Management" CD that comes with the server. If you no longer have the CD, you may download an ISO from the "Drivers and Downloads" web page.
(2) and (3) require Windows or Linux to be installed on the server. I installed Windows 2000 and its current patch. I then installed DSET. Unfortunately, DSET wouldn't run without OMSA being installed, so I had to install that too. After that, it was an easy thing to delete the system log using DSET. Memory diagnostics now runs perfectly.
Update: September 23, 2008: I came across a fourth way to clear the log while researching a similar problem on a PowerEdge 1850 server. There is a program called bmccfg.exe that can be used to clear the log. The instructions I came across refer to the log as the "Embedded Server Management (ESM) Log." I'm assuming that it's the same as the IPMI System Event Log.
The instructions are as follows:
(1) Download and extract the Dell OpenManage Deployment Toolkit.
(2) Copy the \Dell\Toolkit\Tools\bmccfg.exe file to a floppy.
(3) Run it as follows: bmccfg --clearsel
(Be sure to type two dashes before clearsel.)
This will clear the log.
Update: September 23, 2008: Downloaded and extracted the OpenManage Deployment Toolkit for the PowerEdge 1850. There is no bmccfg.exe file to be found.
Update: September 23, 2008: Came across mention of another utility that can clear the ESM log--log2txt.exe, but it won't work on an 1850. http://support.dell.com/support/topics/global.aspx/support/dsn/document?c=us&l=en&s=gen&docid=2F3292A7757843FAB033D6A60258F9FA&journalid=57503A0F03FF2380E040AE0AB5E14379&Query=Ym1jY2Zn&SystemID=PWE_PNT_P3C_2500&ServiceTag=&contenttype=-1&os=-1&component=-1&lang=-1&doclang=en&toggle=false
Update: September 24, 2008: Version 1.4 of the OpenManage Deployment Toolkit may be found here:
I downloaded and extracted it. It contains bmccfg.exe. I'll try it this upcoming weekend.