I have debugged the GUID generated by BMC, the GUID format can be parsed ok according IPMI spec, but maybe the format is wrong with "mc guid" and "pef info". The field "node" is printed to time according to IPMI spec table 20-10.
And also, the timestamp is wrong. UUID UTC base time is October 15, 1582. Unix base time is January 1, 1970. Besides, it is wrong that ipmitool just use "time_low" to generate time.
Attached the logs:
BMC System GUID debug:
time_low: 6e4dcc5e
time_mid: bfde
timeHigh_Ver: 1000
clockSeq_Res: 03e7
NodeID: bc0000000000
BMC Device GUID debug:
time_low: 6e504a1a
time_mid: bfde
timeHigh_Ver: 1000
clockSeq_Res: 03e7
NodeID: bc0000000000
root@bmcfw:/home/fred# ipmitool -I lanplus -H 10.204.29.169 -U admin -P admin raw 6 8
bc 00 00 00 00 00 e7 03 00 10 de bf 1a 4a 50 6e
root@bmcfw:/home/fred# ipmitool -I lanplus -H 10.204.29.169 -U admin -P admin raw 6 0x37
bc 00 00 00 00 00 e7 03 00 10 de bf 5e cc 4d 6e
root@bmcfw:/home/fred# ipmitool -I lanplus -H 10.204.29.169 -U admin -P admin mc guid
System GUID : 000000bc-0000-03e7-0010-debf5ecc4d6e
Timestamp : 01/01/1970 08:03:08
root@bmcfw:/home/fred# ipmitool -I lanplus -H 10.204.29.169 -U admin -P admin pef info
0x51 | 40 | 60 | bc000000-0000-e703-0010-debf5ecc4d6e | Alert,Power-off,Reset,Power-cycle,OEM-defined,Diagnostic-interrupt
Thank you for the report. This seems to be correct. Feel free to provide a patch.
Z.
The print order of ipmitool System GUID does not follow IPMI2.0 spec and UUID format difined by https://tools.ietf.org/rfc/rfc4122, the following is the patch(based on ipmitool-1.8.18).
Result:
ipmitool raw 0x6 0x8
31 5e 37 76 b6 32 d7 b2 e0 3b c3 20 a6 f6 a0 d0
ipmitool mc guid
System GUID : d0a0f6a6-20c3-3be0-b2d7-32b676375e31
Timestamp : 12/01/2080 00:30:30
Last edit: Fred 2017-08-10