+++ This bug was initially created as a clone of Bug #470031 +++ Description of problem: ipmitool is missing the possibility of determining the settings that were set by the "sol payload enable/disable" command Version-Release number of selected component (if applicable): 1.8.10 How reproducible: always Steps to Reproduce: 1. ipmitool sol payload enable 1 1 2. ipmitool sol payload get 1 1 Actual results: [root@tornado ~]# ipmitool sol payload enable 1 1 [root@tornado ~]# ipmitool sol payload get 1 1 SOL Commands: info [<channel number>] set <parameter> <value> [channel] payload <enable|disable> [channel] [userid] activate [<usesolforkeepalive|nokeepalive>] deactivate looptest [<loop times>] [<loop interval(in ms)>] Expected results: [root@tornado ~]# ipmitool sol payload enable 1 1 Enabling SOL payload for user 1 on channel 1 [root@tornado ~]# ipmitool sol payload get 1 1 SOL payload for user 1 on channel 1 is ENABLED Additional info: this was an additional issue raised in bug #224142, see the end of the comment #12 to that bug, but it was not fixed as it was not a subject of that bug see IPMI spec chapter 24.7
patch sent upstream: https://sourceforge.net/mailarchive/forum.php?thread_name=4966001C.9070304%40redhat.com&forum_name=ipmitool-devel
Only important issues like performance and security are fixed in RHEL 4.9 and later. This bug does not meet necessary criteria and is therefore closed.