Hello, Guy,
I guess there was some race between my authorization in the
tcpdump-workers mailing list and my first mail.
Here is the meta-data structure:
Offset Size Description
-----------------------------------------------------------
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.
-----------------------------------------------------------
1 4 Timestamp (seconds part), little endian
-----------------------------------------------------------
5 2 Timestamp (milliseconds part in the range 0 to 999),
little endian
-----------------------------------------------------------
7 1 Trace Data Type(IPMI Channel Protocol Type)
See IPMI 2.0 Table 6-2, “Channel Protocol Type
Numbers”.
The following values are defined in the IPMI 2.0
specification:
00h - n/a
01h - IPMB-1.0
02h - ICMB-1.0
03h - reserved
04h - IPMI-SMBus
05h - KCS
06h - SMIC
07h - BT-10
08h - BT-15
09h - TMode
1Ch-1Fh – OEM Protocol 1 through 4
All other - reserved
-----------------------------------------------------------
8 2 Additional Protocol-specific data, little endian
Additional data. Depends on the IPMI Channel
Protocol Type for this packet.
For protocol = IPMB-1.0
Byte 1
[7] - Direction
0 – From IPM Controller to target device.
1 – From target device to IPM Controller.
[6] – Redundant channel indicator. When IPMI
Channel does not support
redundancy, 0 must be returned.
0 – First channel. (IPMB-A in the case of redundant
IPMB-0)
1 – Second channel. (IPMB-B in the case of
redundant IPMB-0)
[5:0] – Radial IPMB Link Number (0 if IPMB is
bussed), see below.
Byte 2
[7:0] – Reserved.
NOTE: For the IPMB-1.0 protocol, the connection
topology can be either
radial or bused. In the case of a radial topology,
each IPMB device (or
possibly group of IPMB devices) is connected with a
radial hub via a
separate link. If an IPMB radial hub is traced, the
number of the link over
which the packet is sent or received is included in
byte 1 of the additional
data.
For Host-Interface (KCS, SMIC, BT-10, BT15)
Byte 1
[7] - Direction
0 – From IPM Controller to host.
1 – From host to IPM Controller.
[6:0] – Reserved.
Byte 2
[7:0] – Reserved.
-----------------------------------------------------------
10 1 Size of subpacket data.
-----------------------------------------------------------
11 N Data bytes.
-----------------------------------------------------------
Regards,
Dmitry
09.05.2014 1:47, Guy Harris пишет:
On May 8, 2014, at 9:07 AM, Dmitry <d-bazhe...@yandex.ru> wrote:
Can I expect any reply (better positive :)) regarding my question?
You can't expect a reply until people see your message. :-)
Your original message never arrived in my mailbox, and may never have made it
to the list (moderation?), so I didn't see anything until today.
If more details are required in order to get progress on the request, I can
submit them.
Looking forward for any comments.
Regards,
Dmitry
06.05.2014 14:05, Dmitry пишет:
Hello, PCAP library maintainers,
Please, reserve a DLT_ number for IPMI message trace captures used by the
Pigeon Point Systems ipmb_traced utility.
The ipmb_traced utility is capable to capture IPMI traces from several IPMI
channels simultaneously. The traced IPMI channels may have different messaging
protocols.
The captured data includes meta-data which describes each trace packet: which
channel the packet is from, its direction, protocol format, and other
characteristics.
Please give a detailed description of the meta-data format, with the byte order
of multi-byte integral-valued fields specified.
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
