IPMI reporting memory errors, logging now disabled...

Fred Skrotzki fskrotzki at textwise.com
Tue Apr 18 12:09:08 CDT 2006


omsa does not run on the 1425's.  If all I need to do is clear the logs
that I can do via a ipmi command.  I'd prefer not though and just
re-enable the logging so I have a running record of the issue to send to
support.

  _____  

From: Jon Etkins [mailto:jetkins at austinlogistics.com] 
Sent: Tuesday, April 18, 2006 12:51 PM
To: Fred Skrotzki; linux-poweredge at dell.com
Subject: RE: IPMI reporting memory errors, logging now disabled...


OMSA should show you the DIMM details, and will also allow you to clear
the log (and thus re-enable logging)
 


Jon Etkins
Network & IT Administrator
Austin Logistics, Incorporated
(512) 651-5641
www.AustinLogistics.com <http://www.austinlogistics.com/> 
 

 

  _____  

From: linux-poweredge-bounces at dell.com
[mailto:linux-poweredge-bounces at dell.com] On Behalf Of Fred Skrotzki
Sent: Tuesday, April 18, 2006 11:47 AM
To: linux-poweredge at dell.com
Subject: IPMI reporting memory errors, logging now disabled...


in reviewing our ipmi error logs I noticed this series of messages from
one of our 1425sc servers
 
SEL Record ID          : 0017
 Record Type           : 02
 Timestamp             : 04/08/2006 05:08:38
 Generator ID          : 00b1
 EvM Revision          : 04
 Sensor Type           : Memory
 Sensor Number         : 01
 Event Type            : Sensor-specific Discrete
 Event Direction       : Assertion Event
 Event Data            : a0f201
 Description           : Correctable ECC
 
SEL Record ID          : 0018
 Record Type           : 02
 Timestamp             : 04/08/2006 05:08:38
 Generator ID          : 00b1
 EvM Revision          : 04
 Sensor Type           : Memory
 Sensor Number         : 01
 Event Type            : Sensor-specific Discrete
 Event Direction       : Assertion Event
 Event Data            : a0f201
 Description           : Correctable ECC
 
SEL Record ID          : 0019
 Record Type           : 02
 Timestamp             : 04/08/2006 05:08:38
 Generator ID          : 00b1
 EvM Revision          : 04
 Sensor Type           : Memory
 Sensor Number         : 01
 Event Type            : Sensor-specific Discrete
 Event Direction       : Assertion Event
 Event Data            : a0f201
 Description           : Correctable ECC
 
SEL Record ID          : 001a
 Record Type           : 02
 Timestamp             : 04/08/2006 05:08:38
 Generator ID          : 00b1
 EvM Revision          : 04
 Sensor Type           : Memory
 Sensor Number         : 01
 Event Type            : Sensor-specific Discrete
 Event Direction       : Assertion Event
 Event Data            : a0f201
 Description           : Correctable ECC
 
SEL Record ID          : 001b
 Record Type           : 02
 Timestamp             : 04/08/2006 05:08:39
 Generator ID          : 00b1
 EvM Revision          : 04
 Sensor Type           : Memory
 Sensor Number         : 01
 Event Type            : Sensor-specific Discrete
 Event Direction       : Assertion Event
 Event Data            : a0f201
 Description           : Correctable ECC
 
SEL Record ID          : 001c
 Record Type           : 02
 Timestamp             : 04/08/2006 05:08:39
 Generator ID          : 00b1
 EvM Revision          : 04
 Sensor Type           : Memory
 Sensor Number         : 01
 Event Type            : Sensor-specific Discrete
 Event Direction       : Assertion Event
 Event Data            : a0f201
 Description           : Correctable ECC
 
SEL Record ID          : 001d
 Record Type           : 02
 Timestamp             : 04/08/2006 05:08:39
 Generator ID          : 00b1
 EvM Revision          : 04
 Sensor Type           : Event Logging Disabled
 Sensor Number         : 06
 Event Type            : Sensor-specific Discrete
 Event Direction       : Assertion Event
 Event Data            : 00ffff
 Description           : Correctable memory error logging disabled
 
 
Ok I'm figuring I have a bad memory Dim.  But I need to know if this was
a one time event or still continuing.  So how do I re-enable logging?
Also is there a way to determine which Dim was causing this error so I
can just replace it...  It is a Production server so I can't take it
down for hours to run memtest86 on it.
 
 

 

  _____  

CONFIDENTIALITY NOTICE 
The information contained in and transmitted with this email, including
any attachments, is confidential and/or proprietary information of
Austin Logistics Incorporated, and is intended only for a specific
addressee or addressees. If there is an agreement concerning the
treatment of confidential or proprietary information in force between
Austin Logistics Incorporated and the recipient, this message and any
attachments shall be treated as confidential in accordance with the
terms of such agreement. Any dissemination, distribution, copying, or
use of the information contained in and transmitted with this email by
or to anyone other than the intended recipient or such recipient's
authorized agent is unauthorized and strictly prohibited. If you have
received this email in error, please notify the sender by email
immediately and then delete it along with any attachments.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20060418/135e4fb6/attachment.htm 


More information about the Linux-PowerEdge mailing list