ipmiutil-3.0.0 is released

The ipmiutil-3.0.0 release is now posted to sourceforge at http://ipmiutil.sourceforge.net
Details from the ChangeLog below.

08/15/2016 ARCress ipmiutil-3.0.0 changes
util/ipmicmd.h - define RT_OEMIU as 0xDB
util/ipmicmd.c - if ERR_LAN_V2 set driver before open_lan2
util/isel.c - add -i for RT_OEMIU 0xDB events
util/ievents.c - interpret RT_OEMIU 0xDB events
util/oem_supermicro.c - interpret SMC OEM 0xC8 events,
interpret SMC HDD sensors differently,
add factory defaults option
doc/ipmiutil.spec - put so.1 in base, so in devel
util/ipmiutil.mak - add LF_LANPLUS to DLL
util/oem_intel.c/h - add support for Kontron CG2300/Grantley (gdicaire)
util/ialarms.c - add support for Kontron CG2300/Grantley (gdicaire)
util/isensor.c - add support for Kontron CG2300/Grantley (gdicaire)
util/ihealth.c - add support for Intel S2600/Grantley (arcress)
util/iconfig.c - add SMC lanport save/restore
Makefile.am - clean up .deps directories in make tarball
ipmiutil-3.0.0 contains:
ipmiutil (ipmiutil) ver 3.00
...(various subcommands) ver 3.00
ifwum (ipmiutil fwum) ver 1.3
ihpm (ipmiutil hpm) ver 1.09
idiscover (ipmiutil discover) ver 1.11
ipmi_port (ipmi_port) ver 1.4

[mark winter]

Is it possible to capture the Serial-Over-Lan output to a file? Windows Command Prompt do not have support for large number of lines.

[Andy Cress]

Yes, both the input file and output file can be specified with ipmiutil sol.
-i file Input script file
-o file Output trace file
With -i this can be a way to automate some repeated tasks, if desired.

[mark winter]

The -o option is what i exactly need. Thanks.

ipmiutil is crashing initially on less and vi - until i set the term to vt100 from vt220. But with vt100 "less" command is not playing up nicely - it is not showing the search text high lights, scrolls using arrow keys/even enter key is not good. Is it possible to support "vt220"?.

Also it disconnects frequently, is there any option like "usesolkeepalive" in ipmitool?.

[Andy Cress]

The ipmiutil sol session uses a 30-second keepalive by default. You can change the interval with -k if you want.

The vt100/vt220 issue is probably related to how the BIOS/firmware format the serial console.
Note the comments in the isol man page or UserGuide about -r for raw output (relates to ANSI vs. VT100 serial console configuration).