[Ipmitool-devel] Preserving SEL date/time stamps across a clear event

[Brad Willson]

Hi,


The objective here is to save the SEL to a file before an event that clears it, then repopulate it from the saved file then continue logging events from that point on with appropriate date/time stamps. The problem (perceived) is that ipmitool sel add file resets previously recorded date/time stamps to the current date and time effectively debasing the integrity of the log.


ipmitool version 1.8.15

Steps to reproduce:

ipmitool sel list
a | 02/29/2016 | 22:06:33 | Event Logging Disabled #0x8c | Log area reset/cleared | Asserted
b | 02/29/2016 | 22:19:42 | Other Units-based Sensor #0xa0 | State Asserted | Asserted
c | 02/29/2016 | 22:19:43 | System Boot Initiated #0x87 | System Restart | Asserted
d | 02/29/2016 | 22:20:06 | System Event #0x8e | Timestamp Clock Sync | Asserted
e | 02/29/2016 | 22:20:08 | System Event #0x8e | Timestamp Clock Sync | Asserted
f | 02/29/2016 | 22:20:51 | System Event #0x8f | OEM System boot event | Asserted
10 | 02/29/2016 | 22:21:01 | System ACPI Power State #0x88 | S0/G0: working | Asserted

ipmitool sel clear
Clearing SEL. Please allow a few seconds to erase.

ipmitool sel add sel_save
0 | Pre-Init |0000000000| Event Logging Disabled #0x8c | Log area reset/cleared | Asserted
0 | Pre-Init |0000000000| Other Units-based Sensor #0xa0 | State Asserted | Asserted
0 | Pre-Init |0000000000| System Boot Initiated #0x87 | System Restart | Asserted
0 | Pre-Init |0000000000| System Event #0x8e | Timestamp Clock Sync | Asserted
0 | Pre-Init |0000000000| System Event #0x8e | Timestamp Clock Sync | Asserted
0 | Pre-Init |0000000000| System Event #0x8f | OEM System boot event | Asserted
0 | Pre-Init |0000000000| System ACPI Power State #0x88 | S0/G0: working | Asserted

ipmitool sel list
11 | 02/29/2016 | 22:22:37 | Event Logging Disabled #0x8c | Log area reset/cleared | Asserted
12 | 02/29/2016 | 22:22:48 | Event Logging Disabled #0x8c | Log area reset/cleared | Asserted
13 | 02/29/2016 | 22:22:48 | Other Units-based Sensor #0xa0 | State Asserted | Asserted
14 | 02/29/2016 | 22:22:48 | System Boot Initiated #0x87 | System Restart | Asserted
15 | 02/29/2016 | 22:22:48 | System Event #0x8e | Timestamp Clock Sync | Asserted
16 | 02/29/2016 | 22:22:48 | System Event #0x8e | Timestamp Clock Sync | Asserted
17 | 02/29/2016 | 22:22:48 | System Event #0x8f | OEM System boot event | Asserted
18 | 02/29/2016 | 22:22:48 | System ACPI Power State #0x88 | S0/G0: working | Asserted

This smells like a bug to me but I wanted to check with the experts before I proceed.

Thank you,
Brad

[Brad Willson]

Changing this up a little, reading the man page one might think 'sel readraw file' would inject entries into the SEL with time stamps intact but that is not the case. Is there a method to inject events into the SEL, to basically restore from a previously saved raw dump?


Thank you,

Brad

________________________________
From: Brad Willson <***@synnex.com>
Sent: Monday, February 29, 2016 4:14 PM
To: ipmitool-***@lists.sourceforge.net
Subject: [Ipmitool-devel] Preserving SEL date/time stamps across a clear event


Hi,


The objective here is to save the SEL to a file before an event that clears it, then repopulate it from the saved file then continue logging events from that point on with appropriate date/time stamps. The problem (perceived) is that ipmitool sel add file resets previously recorded date/time stamps to the current date and time effectively debasing the integrity of the log.


ipmitool version 1.8.15

Steps to reproduce:

ipmitool sel list
a | 02/29/2016 | 22:06:33 | Event Logging Disabled #0x8c | Log area reset/cleared | Asserted
b | 02/29/2016 | 22:19:42 | Other Units-based Sensor #0xa0 | State Asserted | Asserted
c | 02/29/2016 | 22:19:43 | System Boot Initiated #0x87 | System Restart | Asserted
d | 02/29/2016 | 22:20:06 | System Event #0x8e | Timestamp Clock Sync | Asserted
e | 02/29/2016 | 22:20:08 | System Event #0x8e | Timestamp Clock Sync | Asserted
f | 02/29/2016 | 22:20:51 | System Event #0x8f | OEM System boot event | Asserted
10 | 02/29/2016 | 22:21:01 | System ACPI Power State #0x88 | S0/G0: working | Asserted

ipmitool sel clear
Clearing SEL. Please allow a few seconds to erase.

ipmitool sel add sel_save
0 | Pre-Init |0000000000| Event Logging Disabled #0x8c | Log area reset/cleared | Asserted
0 | Pre-Init |0000000000| Other Units-based Sensor #0xa0 | State Asserted | Asserted
0 | Pre-Init |0000000000| System Boot Initiated #0x87 | System Restart | Asserted
0 | Pre-Init |0000000000| System Event #0x8e | Timestamp Clock Sync | Asserted
0 | Pre-Init |0000000000| System Event #0x8e | Timestamp Clock Sync | Asserted
0 | Pre-Init |0000000000| System Event #0x8f | OEM System boot event | Asserted
0 | Pre-Init |0000000000| System ACPI Power State #0x88 | S0/G0: working | Asserted

ipmitool sel list
11 | 02/29/2016 | 22:22:37 | Event Logging Disabled #0x8c | Log area reset/cleared | Asserted
12 | 02/29/2016 | 22:22:48 | Event Logging Disabled #0x8c | Log area reset/cleared | Asserted
13 | 02/29/2016 | 22:22:48 | Other Units-based Sensor #0xa0 | State Asserted | Asserted
14 | 02/29/2016 | 22:22:48 | System Boot Initiated #0x87 | System Restart | Asserted
15 | 02/29/2016 | 22:22:48 | System Event #0x8e | Timestamp Clock Sync | Asserted
16 | 02/29/2016 | 22:22:48 | System Event #0x8e | Timestamp Clock Sync | Asserted
17 | 02/29/2016 | 22:22:48 | System Event #0x8f | OEM System boot event | Asserted
18 | 02/29/2016 | 22:22:48 | System ACPI Power State #0x88 | S0/G0: working | Asserted

This smells like a bug to me but I wanted to check with the experts before I proceed.

Thank you,
Brad

[Zdenek Styblik]

On Tue, Mar 1, 2016 at 7:51 PM, Brad Willson <***@synnex.com> wrote:
> Changing this up a little, reading the man page one might think 'sel readraw
> file' would inject entries into the SEL with time stamps intact but that is
> not the case. Is there a method to inject events into the SEL, to basically
> restore from a previously saved raw dump?

Hello,

looking at the source code, I see that timestamp is not being set(and
not being saved either!). However, that's all I can tell you.
I guess you could inject SEL entries as a raw commands, but it might
be ... difficult.

Best regards,
Z.

--
Zdenek Styblik
email: ***@gmail.com
jabber: ***@gmail.com


>
>
> Thank you,
>
> Brad
>
>
> ________________________________
> From: Brad Willson <***@synnex.com>
> Sent: Monday, February 29, 2016 4:14 PM
> To: ipmitool-***@lists.sourceforge.net
> Subject: [Ipmitool-devel] Preserving SEL date/time stamps across a clear
> event
>
>
> Hi,
>
>
> The objective here is to save the SEL to a file before an event that clears
> it, then repopulate it from the saved file then continue logging events from
> that point on with appropriate date/time stamps. The problem (perceived) is
> that ipmitool sel add file resets previously recorded date/time stamps to
> the current date and time effectively debasing the integrity of the log.
>
>
> ipmitool version 1.8.15
>
> Steps to reproduce:
>
> ipmitool sel list
> a | 02/29/2016 | 22:06:33 | Event Logging Disabled #0x8c | Log area
> reset/cleared | Asserted
> b | 02/29/2016 | 22:19:42 | Other Units-based Sensor #0xa0 | State
> Asserted | Asserted
> c | 02/29/2016 | 22:19:43 | System Boot Initiated #0x87 | System Restart
> | Asserted
> d | 02/29/2016 | 22:20:06 | System Event #0x8e | Timestamp Clock Sync |
> Asserted
> e | 02/29/2016 | 22:20:08 | System Event #0x8e | Timestamp Clock Sync |
> Asserted
> f | 02/29/2016 | 22:20:51 | System Event #0x8f | OEM System boot event |
> Asserted
> 10 | 02/29/2016 | 22:21:01 | System ACPI Power State #0x88 | S0/G0:
> working | Asserted
>
> ipmitool sel clear
> Clearing SEL. Please allow a few seconds to erase.
>
> ipmitool sel add sel_save
> 0 | Pre-Init |0000000000| Event Logging Disabled #0x8c | Log area
> reset/cleared | Asserted
> 0 | Pre-Init |0000000000| Other Units-based Sensor #0xa0 | State
> Asserted | Asserted
> 0 | Pre-Init |0000000000| System Boot Initiated #0x87 | System Restart
> | Asserted
> 0 | Pre-Init |0000000000| System Event #0x8e | Timestamp Clock Sync |
> Asserted
> 0 | Pre-Init |0000000000| System Event #0x8e | Timestamp Clock Sync |
> Asserted
> 0 | Pre-Init |0000000000| System Event #0x8f | OEM System boot event |
> Asserted
> 0 | Pre-Init |0000000000| System ACPI Power State #0x88 | S0/G0:
> working | Asserted
>
> ipmitool sel list
> 11 | 02/29/2016 | 22:22:37 | Event Logging Disabled #0x8c | Log area
> reset/cleared | Asserted
> 12 | 02/29/2016 | 22:22:48 | Event Logging Disabled #0x8c | Log area
> reset/cleared | Asserted
> 13 | 02/29/2016 | 22:22:48 | Other Units-based Sensor #0xa0 | State
> Asserted | Asserted
> 14 | 02/29/2016 | 22:22:48 | System Boot Initiated #0x87 | System Restart
> | Asserted
> 15 | 02/29/2016 | 22:22:48 | System Event #0x8e | Timestamp Clock Sync |
> Asserted
> 16 | 02/29/2016 | 22:22:48 | System Event #0x8e | Timestamp Clock Sync |
> Asserted
> 17 | 02/29/2016 | 22:22:48 | System Event #0x8f | OEM System boot event |
> Asserted
> 18 | 02/29/2016 | 22:22:48 | System ACPI Power State #0x88 | S0/G0:
> working | Asserted
>
> This smells like a bug to me but I wanted to check with the experts before I
> proceed.
>
> Thank you,
> Brad
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Ipmitool-devel mailing list
> Ipmitool-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
>

[Liebig, Holger]

Hi Brad,



Short answer: not possible

Long answer (quote from the IPMI Spec. Section 31.6 Add SEL Entry Command):

…

Records are added on after the last record in the SEL. The SEL Device adds
the timestamp according to the SEL Record Type (see 31.6.1, SEL Record Type
Ranges, following) when it creates the record. Thus, in some cases the
timestamp bytes in the record data are ignored. However, ‘dummy’ timestamp
bytes must still be present in the data.



Holger



From: Brad Willson [mailto:***@synnex.com]
Sent: Tuesday, March 01, 2016 7:51 PM
To: ipmitool-***@lists.sourceforge.net
Subject: Re: [Ipmitool-devel] Preserving SEL date/time stamps across a clear
event



Changing this up a little, reading the man page one might think 'sel readraw
file' would inject entries into the SEL with time stamps intact but that is
not the case. Is there a method to inject events into the SEL, to basically
restore from a previously saved raw dump?



Thank you,

Brad



_____

From: Brad Willson <***@synnex.com>
Sent: Monday, February 29, 2016 4:14 PM
To: ipmitool-***@lists.sourceforge.net
Subject: [Ipmitool-devel] Preserving SEL date/time stamps across a clear
event



Hi,



The objective here is to save the SEL to a file before an event that clears
it, then repopulate it from the saved file then continue logging events from
that point on with appropriate date/time stamps. The problem (perceived) is
that ipmitool sel add file resets previously recorded date/time stamps to
the current date and time effectively debasing the integrity of the log.



ipmitool version 1.8.15



Steps to reproduce:



ipmitool sel list

a | 02/29/2016 | 22:06:33 | Event Logging Disabled #0x8c | Log area
reset/cleared | Asserted

b | 02/29/2016 | 22:19:42 | Other Units-based Sensor #0xa0 | State
Asserted | Asserted

c | 02/29/2016 | 22:19:43 | System Boot Initiated #0x87 | System Restart
| Asserted

d | 02/29/2016 | 22:20:06 | System Event #0x8e | Timestamp Clock Sync |
Asserted

e | 02/29/2016 | 22:20:08 | System Event #0x8e | Timestamp Clock Sync |
Asserted

f | 02/29/2016 | 22:20:51 | System Event #0x8f | OEM System boot event |
Asserted

10 | 02/29/2016 | 22:21:01 | System ACPI Power State #0x88 | S0/G0:
working | Asserted



ipmitool sel clear

Clearing SEL. Please allow a few seconds to erase.



ipmitool sel add sel_save

0 | Pre-Init |0000000000| Event Logging Disabled #0x8c | Log area
reset/cleared | Asserted

0 | Pre-Init |0000000000| Other Units-based Sensor #0xa0 | State
Asserted | Asserted

0 | Pre-Init |0000000000| System Boot Initiated #0x87 | System Restart
| Asserted

0 | Pre-Init |0000000000| System Event #0x8e | Timestamp Clock Sync |
Asserted

0 | Pre-Init |0000000000| System Event #0x8e | Timestamp Clock Sync |
Asserted

0 | Pre-Init |0000000000| System Event #0x8f | OEM System boot event |
Asserted

0 | Pre-Init |0000000000| System ACPI Power State #0x88 | S0/G0:
working | Asserted



ipmitool sel list

11 | 02/29/2016 | 22:22:37 | Event Logging Disabled #0x8c | Log area
reset/cleared | Asserted

12 | 02/29/2016 | 22:22:48 | Event Logging Disabled #0x8c | Log area
reset/cleared | Asserted

13 | 02/29/2016 | 22:22:48 | Other Units-based Sensor #0xa0 | State
Asserted | Asserted

14 | 02/29/2016 | 22:22:48 | System Boot Initiated #0x87 | System Restart
| Asserted

15 | 02/29/2016 | 22:22:48 | System Event #0x8e | Timestamp Clock Sync |
Asserted

16 | 02/29/2016 | 22:22:48 | System Event #0x8e | Timestamp Clock Sync |
Asserted

17 | 02/29/2016 | 22:22:48 | System Event #0x8f | OEM System boot event |
Asserted

18 | 02/29/2016 | 22:22:48 | System ACPI Power State #0x88 | S0/G0:
working | Asserted



This smells like a bug to me but I wanted to check with the experts before I
proceed.



Thank you,

Brad

[Brad Willson]

Hi Holger and Zdenek,


Thank you both for the guidance! I've pulled ipmi-intelligent-platform-mgt-interface-spec-2nd-gen-v2-0-spec-update.pdf for future reference.


Cheers,

Brad

________________________________
From: Liebig, Holger <***@ts.fujitsu.com>
Sent: Tuesday, March 1, 2016 11:00 PM
To: Brad Willson; ipmitool-***@lists.sourceforge.net
Subject: RE: [Ipmitool-devel] Preserving SEL date/time stamps across a clear event


Hi Brad,



Short answer: not possible

Long answer (quote from the IPMI Spec. Section 31.6 Add SEL Entry Command):

…

Records are added on after the last record in the SEL. The SEL Device adds the timestamp according to the SEL Record Type (see 31.6.1, SEL Record Type Ranges, following) when it creates the record. Thus, in some cases the timestamp bytes in the record data are ignored. However, ‘dummy’ timestamp bytes must still be present in the data.



Holger



From: Brad Willson [mailto:***@synnex.com]
Sent: Tuesday, March 01, 2016 7:51 PM
To: ipmitool-***@lists.sourceforge.net
Subject: Re: [Ipmitool-devel] Preserving SEL date/time stamps across a clear event



Changing this up a little, reading the man page one might think 'sel readraw file' would inject entries into the SEL with time stamps intact but that is not the case. Is there a method to inject events into the SEL, to basically restore from a previously saved raw dump?



Thank you,

Brad



________________________________

From: Brad Willson <***@synnex.com<mailto:***@synnex.com>>
Sent: Monday, February 29, 2016 4:14 PM
To: ipmitool-***@lists.sourceforge.net<mailto:ipmitool-***@lists.sourceforge.net>
Subject: [Ipmitool-devel] Preserving SEL date/time stamps across a clear event



Hi,



The objective here is to save the SEL to a file before an event that clears it, then repopulate it from the saved file then continue logging events from that point on with appropriate date/time stamps. The problem (perceived) is that ipmitool sel add file resets previously recorded date/time stamps to the current date and time effectively debasing the integrity of the log.



ipmitool version 1.8.15



Steps to reproduce:



ipmitool sel list

a | 02/29/2016 | 22:06:33 | Event Logging Disabled #0x8c | Log area reset/cleared | Asserted

b | 02/29/2016 | 22:19:42 | Other Units-based Sensor #0xa0 | State Asserted | Asserted

c | 02/29/2016 | 22:19:43 | System Boot Initiated #0x87 | System Restart | Asserted

d | 02/29/2016 | 22:20:06 | System Event #0x8e | Timestamp Clock Sync | Asserted

e | 02/29/2016 | 22:20:08 | System Event #0x8e | Timestamp Clock Sync | Asserted

f | 02/29/2016 | 22:20:51 | System Event #0x8f | OEM System boot event | Asserted

10 | 02/29/2016 | 22:21:01 | System ACPI Power State #0x88 | S0/G0: working | Asserted



ipmitool sel clear

Clearing SEL. Please allow a few seconds to erase.



ipmitool sel add sel_save

0 | Pre-Init |0000000000| Event Logging Disabled #0x8c | Log area reset/cleared | Asserted

0 | Pre-Init |0000000000| Other Units-based Sensor #0xa0 | State Asserted | Asserted

0 | Pre-Init |0000000000| System Boot Initiated #0x87 | System Restart | Asserted

0 | Pre-Init |0000000000| System Event #0x8e | Timestamp Clock Sync | Asserted

0 | Pre-Init |0000000000| System Event #0x8e | Timestamp Clock Sync | Asserted

0 | Pre-Init |0000000000| System Event #0x8f | OEM System boot event | Asserted

0 | Pre-Init |0000000000| System ACPI Power State #0x88 | S0/G0: working | Asserted



ipmitool sel list

11 | 02/29/2016 | 22:22:37 | Event Logging Disabled #0x8c | Log area reset/cleared | Asserted

12 | 02/29/2016 | 22:22:48 | Event Logging Disabled #0x8c | Log area reset/cleared | Asserted

13 | 02/29/2016 | 22:22:48 | Other Units-based Sensor #0xa0 | State Asserted | Asserted

14 | 02/29/2016 | 22:22:48 | System Boot Initiated #0x87 | System Restart | Asserted

15 | 02/29/2016 | 22:22:48 | System Event #0x8e | Timestamp Clock Sync | Asserted

16 | 02/29/2016 | 22:22:48 | System Event #0x8e | Timestamp Clock Sync | Asserted

17 | 02/29/2016 | 22:22:48 | System Event #0x8f | OEM System boot event | Asserted

18 | 02/29/2016 | 22:22:48 | System ACPI Power State #0x88 | S0/G0: working | Asserted



This smells like a bug to me but I wanted to check with the experts before I proceed.



Thank you,

Brad