The IPMI specification mandates that sessions time out after 60 seconds if no RMCP UDP packets are not received by the server. Most of the IPMI libraries and tools send a Get Device ID or some other IPMI command to keep the sessions alive. Hemi does it this way. http://www.jblade.com/JbDoc2/products/hemi/hemiCX/doc/programmers/HemiCxRmcpSession.html
Changing a password should take less than 5 seconds so it's likely there is some other problem. Is it possible the RMCP session you are using does not have or has not elevated is permission to the IPMI level of administrator ? Most vendors implement either a web or Command line interface to change account names or passwords. Hank Bruning On Sat, Dec 13, 2014 at 11:38 AM, jbd <j...@jbdenis.net> wrote: > > Hi, > > I'm trying to remotely change the password of a (unique) user : > > $ ipmi-config --commit -h hostname -u MYUSER -p CURRENT_PASSWORD -e > User2:Password=NEW_PASSWORD > ipmi_cmd_set_user_password: session timeout > > The new password is working though : > > $ ipmi-config --checkout -h hostname -u MYUSER -p NEW_PASSWORD -S Lan_Conf > > Is there some way not having this session timeout ? If not, what would > be the good way to remotely change a password ? > > Thank you ! > > Jean-Baptiste > > > > _______________________________________________ > Freeipmi-users mailing list > Freeipmi-users@gnu.org > https://lists.gnu.org/mailman/listinfo/freeipmi-users > _______________________________________________ Freeipmi-users mailing list Freeipmi-users@gnu.org https://lists.gnu.org/mailman/listinfo/freeipmi-users
