Hey Nicolas, Entering section `Alert_Policy_2' Comment on line 2 Parsed `Alert_Policy_2:Policy_Type=Always_Send_To_This_Destination' Comment on line 4 Parsed `Alert_Policy_2:Policy_Enabled=Yes' Comment on line 6 Parsed `Alert_Policy_2:Policy_Number=2' Comment on line 8 Parsed `Alert_Policy_2:Destination_Selector=1' Comment on line 10 Parsed `Alert_Policy_2:Channel_Number=2' Comment on line 12 Parsed `Alert_Policy_2:Alert_String_Set_Selector=1' Comment on line 14 Parsed `Alert_Policy_2:Event_Specific_Alert_String=No' Leaving section `Alert_Policy_2' ===================================================== Set PEF Configuration Parameters Request ===================================================== [ 12h] = cmd[ 8b] [ 9h] = parameter_selector[ 7b] [ 0h] = reserved1[ 1b] [ 2h] = alert_policy_entry_number[ 7b] [ 0h] = reserved2[ 1b] [ 0h] = policy_number.policy_type[ 3b] [ 0h] = policy_number.enabled[ 1b] [ 0h] = policy_number.policy_number[ 4b] [ 0h] = channel_destination.destination_selector[ 4b] [ 0h] = channel_destination.channel_number[ 4b] [ 0h] = alert_string_key.alert_string_set_selector[ 7b] [ 0h] = alert_string_key.event_specific_alert_string[ 1b] ===================================================== Set PEF Configuration Parameters Response ===================================================== [ 12h] = cmd[ 8b] [ CCh] = comp_code[ 8b] ipmi_cmd_set_pef_configuration_parameters_alert_policy_table: bad completion code: request data/parameter invalid ERROR: Failed to commit `Alert_Policy_2:Policy_Type'
Hmmmm ... I'm wondering if it's complaining that the channel number is 0. Lets try a trick. Can you reorder your alert_policy_2 config to list "channel number" first in the Alert_Policy_2 block? In general, try re-ordering them around and see if it helps (from your debug I assume you had tried to config only Alert_Policy_2 at the time). If that is the issue, I can add a workaround for your motherboard. The core issue (which I've hit with multiple vendors) is that it is possible for the default config on the motherboard to be an "illegal" config. So when the user tries to change only 1 sub-field for that area, how are they supposed to know that a part they aren't interested is configured illegally. Al P.S. If moving them fields around makes it work, PLMK what fields and then PLMK the vendor and motherboard, so I can document it. On Thu, 2009-10-29 at 14:07 +0100, Moerman Nicolas wrote: > Hello Al, > > > > I meet a problem to commit settings into the PEF, specialy a policy. > > The amazing thing is that it worked but now it isn't anymore. I've got > a "ERROR: Failed to commit". > > I think my syntax is OK, these problems appeared since my BMC reset > test , I think… > > > > Maybe an optin has been reset and i don't remmerber what and where. > > I join the debug output of my command and the conf file. > > I hope you will have an idea about what's happen. > > thanks > > > > > > > ______________________________________________________________________________ > > Nicolas MOERMAN > > Technical Operations > > Tel : +33 (0)3 20 60 79 48 > > > ATOS WORLDLINE > Z.I A Rue dela Pointe 59113 SECLIN > > www.*atosworldline.com > > Atos Worldline is an Atos Origin Company: www.*atosorigin.com > > > > > > > > > > > ______________________________________________________________________ > > Ce message et les pièces jointes sont confidentiels et réservés à > l'usage exclusif de ses destinataires. Il peut également être protégé > par le secret professionnel. Si vous recevez ce message par erreur, > merci d'en avertir immédiatement l'expéditeur et de le détruire. > L'intégrité du message ne pouvant être assurée sur Internet, la > responsabilité du groupe Atos Origin ne pourra être recherchée quant > au contenu de ce message. Bien que les meilleurs efforts soient faits > pour maintenir cette transmission exempte de tout virus, l'expéditeur > ne donne aucune garantie à cet égard et sa responsabilité ne saurait > être recherchée pour tout dommage résultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive > this e-mail in error, please notify the sender immediately and destroy > it. As its integrity cannot be secured on the Internet, the Atos > Origin group liability cannot be triggered for the message content. > Although the sender endeavours to maintain a computer virus-free > network, the sender does not warrant that this transmission is > virus-free and will not be liable for any damages resulting from any > virus transmitted. -- Albert Chu ch...@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list Freeipmi-users@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-users
