It's entirely possible there is another issue for your systems I never
encountered before or a bug in the workaround code. If you could send
the --debug output, that'd be great.
As for your second question, there are a number of "checks" that I do
more stringently than in ipmitool, leading to the need for workarounds
in FreeIPMI than in ipmitool. Ipmitool also elects to "hide"
workarounds in its tools more often, instead of making the user put them
on the command line. Pros and cons of both approaches, I don't think
either of us is right or wrong.
On Mon, 2009-06-08 at 17:43 +0100, Dave Love wrote:
> I tried `bmc-info -D LAN_2_0 -W sun20' on x4100s with both ILOM 1.0 and
> 184.108.40.206 (the latest as of a few months ago). It gives `password
> invalid' in both cases. (With LAN, -W endianseq works with both the 1.0
> and 2.0 ILOMs, but it doesn't help with LAN_2_0.)
> Is --debug output the right thing to send? I could also send -v output
> from ipmitool, which works. [Is it known how ipmitool gets away without
> workarounds specified?]
> Freeipmi-devel mailing list
> http:// lists.gnu.org/mailman/listinfo/freeipmi-devel
High Performance Systems Division
Lawrence Livermore National Laboratory
Freeipmi-devel mailing list