Hi all,
I have some trouble with the use of Cipher Suite IDs for
IPMI lanplus connection.
On some systems, specially Supermicro systems, I can't use
any Cipher ID except -C 0
Lan configuration of this server running IPMI 2.0 is:
RMCP+ Cipher Suites : 0,1,2,3,6,7,8,11,12
Cipher Suite Priv Max
Hi Mirko,
I agree with you and I included this interface check removal
in my patch proposal titled "Patch proposal for sensors
owned by satellite controllers".
Moreover, can anyone tell me in which case the interface name
(intf->name) is set to "ipmb".
Bernard.
> -Message d'origine-
>
Did you try 'ipmitool -S file exec cmdfile'
Bernard
> -Message d'origine-
> De : Mark Seger [mailto:[EMAIL PROTECTED]
> Envoyé : 26 November 2008 15:19
> À : Isabelle, Francois
> Cc : ipmitool-devel@lists.sourceforge.net; Carol Hebert
> Objet : Re: [Ipmitool-devel] Optimizing the use o
Hi All,
The "ipmitool chassis status" returns bad "Front Panel Button
disable/enable status".
The reason is the use of erroneous mask values.
The attached patch fixes this problem.
Bernard MANJOU
diff -Naur ipmitool-1.8.10/lib/ipmi_chassis.c
ipmitool-1.8.10_patc
"Bull Company" },
{ 0x , NULL },
};
Thanks,
=======
Bernard MANJOU
System Software Development R&D
phone : +33 (0) 1 30 80 73 50
mailto:[EMAIL PROTECTED]
Bull, Architect of an Open World TM
http:
correspond to
a timestamp equal to 0, which is not the final timestamp
of this event that appears correctly on an "ipmitool sel
list" command.
Hope this help you
Bernard.
> -Message d'origine-
> De : Carol Hebert [mailto:[EMAIL PROTECTED]
> Envoyé
elta_hour=lt_hour - gt_hour;
+ if ( (lt_year > gt_year) || ((lt_year == gt_year) &&
(lt_yday > gt_yday)) )
+ delta_hour += 24;
+ if ( (lt_year < gt_year) || ((lt_year == gt_year) &&
(lt_yday < gt_yday)) )
+ delta_hour
7, Ben Bloom describes an issue he's seeing
> getting sensor readings on a non-ipmb implementation. Ben,
> did Holger's 11/4 workaround suggestion help?
>
> http://sourceforge.net/mailarchive/message.php?msg_name=BE5503
2BAC1C8441B01E9EF7CE57CC20A8EDCE%40OREXCHANGE01.radisys.com
fru ..." commands with fru_id argument.
If you agree with this analysis, my feeling is that an optional
argument (ie:called "owner_id"), set by default to 0x20, should be
added to ipmitool commands with fru_id or sensor_id argument, and
this "owner_id" parameter should be adde
assumes timestamp is specified in UTC time before
converting it in Local time for display.
The problem occurs when sel time has been set in local time
(compliantly to IPMI spec) by an external tool.
May be my understanding of IPMI spec is wrong?
In the other case, should not Ipmitool
be added to
ipmi_sdr_find_sdr_byid()
and all calling codes should also be modified.)
===
Bernard MANJOU
System Software Development R&D
phone : +33 (0) 1 30 80 73 50
mailto:[EMAIL PROTECTED]
Bull, Architect of an Open Worl
if ((1 << (evt->offset - 8)) & state2) {
+ if ((1 << (evt->offset - 8)) & (state2 & 0x7f)) {
if (evt->desc) {
v[i], NULL, 0);
- wdata[i-2] = val;
+ wdata[wsize] = val;
wsize++;
}
Thanks,
Bernard MANJOU
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Stud
free_space =
- (sdr_repository_info.free_space[0] << 8) |
- sdr_repository_info.free_space[1];
+ (sdr_repository_info.free_space[1] << 8) |
+ sdr_repository_info.free_space[0];
printf("Free Space : ");
switc
Hi all,
IPMI spec 2.0 specifies that "Timestamps used for SDR and SEL records
are assumed to be specified in local time".
But "ipmitool sel set time" command sets the IPMI SEL clock with GMT
time and all SDR and SEL ipmitool commands assumed IPMI timestamps
to be in GMT time.
Is ipmitool correct
15 matches
Mail list logo
