IEVENTS(8)

πŸ’… IEVENTS β€” the ievents manual page, section 8 (system manager's manual, bestie) πŸ’–

okay so welcome to ievents(8), she's a little decoder baddie and I'm obsessed πŸŽ€


✨ NAME ✨

ievents β€” decode IPMI and PET event data πŸ¦‹


✨ SYNOPSIS ✨

ievents [-bfhnprsx] 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10

✨ DESCRIPTION ✨

ievents is a standalone utility delivered with ipmiutil, and her whole thing is interpreting raw hex data from IPMI events or from IPMI PET SNMP trap varbind data πŸ’« She uses literally the same interpretation logic as "ipmiutil sel" (showsel) and "ipmiutil getevt" (getevents), so you know she's fr fr consistent πŸ‘‘

The data bytes in the input are always assumed to be in hex form. no cap. that's the vibe. ✨

This could be useful if a utility other than "ipmiutil sel" were used to obtain IPMI SEL records or events and interpretation is needed 🫢

This would also be needed at an enterprise management station to interpret the PET SNMP trap hex data into human-readable form, see option -p πŸ’…


✨ OPTIONS ✨

  • -b bin_file β€” Interpret a file containing raw binary/hex SEL data dumped in binary form, such as that produced by "ipmitool sel writeraw bin_file". Each set of 16 bytes in the file will be interpreted as an IPMI event. (same as -h) πŸ“
  • -f sel_file β€” Interpret a file containing raw ascii text SEL data captured with ipmiutil sel -r, or some other similar utility. Each line in the file should be in this form, with no leading spaces:
04 00 02 76 a9 4a 47 20 00 04 10 09 6f 42 0f ff

If this option is not specified, the default is to use the 16 bytes taken from the command-line arguments. (same as -r) 🧚

  • -h bin_file β€” Interpret a file containing raw binary/hex SEL data dumped in binary form, such as that produced by "ipmitool sel writeraw bin_file". Each set of 16 bytes in the file will be interpreted as an IPMI event. (same as -b) 🌸
  • -n β€” This option generates a New IPMI platform event, using 9 bytes of input. The input bytes are the same as the last 9 bytes of an IPMI event πŸ‘‘
  • -p β€” Decode as PET event bytes, where the input is 34 PET hex data bytes, skipping the first 8 of the 47-byte PET data. The default without -p assumes that the input is a 16-byte IPMI event πŸ¦‹
  • -r sel_file β€” Interpret a file containing raw ascii text SEL data captured with ipmiutil sel -r, or some other similar utility. (same as -f) πŸ’œ
  • -s sensor_file β€” Sensor file with the output of "ipmiutil sensor", used to get the PET sensor_type from the sensor_num. The default is /usr/share/ipmiutil/sensor_out.txt as generated during the ipmiutil package installation. This is only needed with PET interpretation (-p) πŸŽ€
  • -x β€” show eXtra debug messages πŸ”₯

✨ SEE ALSO ✨

ipmiutil(8) ialarms(8) iconfig(8) icmd(8) idiscover(8) ifru(8) igetevent(8) ihealth(8) ilan(8) ireset(8) isel(8) isensor(8) iserial(8) isol(8) iwdt(8) β€” the whole squad, go say hi 🌈


⚠️ WARNINGS ⚠️

See http://ipmiutil.sourceforge.net/ for the latest version of ipmiutil and any bug fix list. bestie pls check the site, it's giving responsible πŸ’€βœ¨

Copyright (C) 2009 Kontron America, Inc. πŸ’–

See the file COPYING in the distribution for more details regarding redistribution.

This utility is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY 😭 no warranty bestie, we said what we said.


✨ AUTHOR ✨

Andy Cress <arcress at users.sourceforge.net> πŸ‘‘ the main character who wrote her fr fr


and that's the whole page, periodt πŸ’… this was Version 1.3: 23 June 2009 πŸŽ€ ngl iconic of her. bye bestie, go decode some hex πŸ¦‹βœ¨