Hi Duncan, I've run into an issue when setting SOL configuration parameters (I noticed it when setting volatile and non-volatile bitrates). After the (recursive) call to ipmi_sol_set_param() to issue the set-in-progress/set-in-progress, there's a (recursive) call for set-in-progress/write-commit.
As the IPMI spec states, write-commit is optional and only used if a rollback has been implemented and will return an error code if it's not supported. And as a comment in the ipmitool code suggests, because it's optional, it's okay if the write-commit fails. Nevertheless, the response back to the user after running "sol set <param>" suggests that the command they issued failed: "Error setting SOL parameter 'set-in-progress': Invalid data field in request" In the example of bit-rate setting, a user could see via a quick check using "sol info" that the command indeed succeeded but unless they thought to check, they'd most probably assume the command just failed. Am I just plain doing something wrong or is there a way to make this response more user-friendly -- like maybe adding a check in ipmi_sol_set_param() to determine whether it was a write-commit that failed before issuing the error message (i.e., in most, if not all cases, let write-commit silently fail)? Thanks much for your help, Carol Hebert ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
