tcpdump mailing list archives

Re: DLT_ reserve request for IPMI trace captures


From: Guy Harris <guy () alum mit edu>
Date: Sat, 7 Jun 2014 13:17:17 -0700


On May 27, 2014, at 8:52 PM, Dmitry <d-bazhenov () yandex ru> wrote:

28.05.2014 3:24, Guy Harris пишет:

So are you saying that the packet data, starting with the Trace Data Block Type byte, is in the format specified in 
some part of HPM.2?

Correct. It is specified in the Table 3-20 "Trace Data Block Format" of the HPM.2 specification

OK, so all we would need to say on http://www.tcpdump.org/linktypes.html would be:

        LINKTYPE_whatever       {number}        DLT_whatever    Trace data blocks, as specified by Table 3-20 "Trace 
Data Block Format" in the PICMG HPM.2 specification

with "PICMG HPM.2 specification" linking to http://www.picmg.org/v2internal/specifications2.cfm?thetype=One&thebusid=12 
(that being the closest thing we can provide to a link to the spec)?

And a trace data block begins with

  0        1     Trace Data Block Type
                 [7:6] Reserved
                 [5:4] Packet Type
                 0 – IPMI Trace Packet Data.
                 1 - Channel State Change Notification.
                 2 - Embedded ASCII message.
                 3 - Reserved.
                 [3:0] – IPMI Channel Number being traced.

and the HPM.2 spec describes the format of IPMI Trace Packet Data (either directly or by referring to IPMI specs), the 
format of Channel State Change Notifications, and the format of embedded ASCII messages?

Correct?

Also, are the time stamps in pcap records or pcap-ng packet blocks significant, given that the trace blocks contain 
their own time stamps?
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

Current thread: