This bug has been copied from bug #826027 and has been proposed to be backported to 6.3 z-stream (EUS).
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: In the previous ipmitool update, new options '-R' and '-N' were added to adjust retransmission rate of outgoing IPMI requests over lan and lanplus interfaces. Implementation of these options set wrong default value of retransmission timeout and outgoing request timed out prematurely. This update fixes the default timeout value and ipmitool without '-N' option retransmits outgoing IPMI requests as in previous versions.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -In the previous ipmitool update, new options '-R' and '-N' were added to adjust retransmission rate of outgoing IPMI requests over lan and lanplus interfaces. Implementation of these options set wrong default value of retransmission timeout and outgoing request timed out prematurely. This update fixes the default timeout value and ipmitool without '-N' option retransmits outgoing IPMI requests as in previous versions.+In the previous ipmitool update, new options '-R' and '-N' were added to adjust retransmission rate of outgoing IPMI requests over lan and lanplus interfaces. Implementation of these options set wrong default value of retransmission timeout and outgoing request timed out prematurely. In addition, in some corner cases, ipmitool could segfault when the timeout occurred. This update fixes the default timeout value and ipmitool without '-N' option retransmits outgoing IPMI requests as in previous versions.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0999.html