All, I recently discovered that the in band ipmitool OpenIPMI Interface did now work as I expected when I attempted to specify different local IPMB address via the -m switch.
My expectation was that local system interface would be used with the address I specified on the command line, but instead ipmitool attempted to bridge my request because the interface target address was 0x20 and my specified address via -m was not 0x20. I tracked the issue down to the fact that bridging will occur in the OpenIPMI interface whenever there is a non zero target address and the target address is not equal to the interface address. I believe this logic is reasonable, but I think the intent was that the target address would always be zero unless it was specified on the command line with the -t option (in which case you want bridging). The problem I am seeing crops up because the OpenIPMI interface in ipmitool initializes both the target address and the interface address to 0x20 instead of only initializing the interface address to 0x20 and setting the target address to zero. Does anyone happen to know whether my interpretation of intended usages for -m and -t are correct? Thanks in Advance, Jim -- -- Jim Mankovich | jm...@hp.com -- ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
