Menu
▾
▴
ipmitool-devel — IPMItool developers list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(30) |
Feb
(4) |
Mar
(52) |
Apr
(27) |
May
(15) |
Jun
(33) |
Jul
(32) |
Aug
(48) |
Sep
(25) |
Oct
(28) |
Nov
(22) |
Dec
(16) |
| 2005 |
Jan
(22) |
Feb
(72) |
Mar
(29) |
Apr
(35) |
May
(22) |
Jun
(20) |
Jul
(23) |
Aug
(28) |
Sep
(7) |
Oct
(11) |
Nov
(33) |
Dec
(32) |
| 2006 |
Jan
(55) |
Feb
(34) |
Mar
(50) |
Apr
(29) |
May
(33) |
Jun
(19) |
Jul
(37) |
Aug
(46) |
Sep
(100) |
Oct
(38) |
Nov
(54) |
Dec
(38) |
| 2007 |
Jan
(34) |
Feb
(63) |
Mar
(37) |
Apr
(40) |
May
(41) |
Jun
(21) |
Jul
(27) |
Aug
(39) |
Sep
(38) |
Oct
(24) |
Nov
(42) |
Dec
(35) |
| 2008 |
Jan
(8) |
Feb
(26) |
Mar
(18) |
Apr
(24) |
May
(24) |
Jun
(43) |
Jul
(46) |
Aug
(35) |
Sep
(7) |
Oct
(21) |
Nov
(24) |
Dec
(21) |
| 2009 |
Jan
(51) |
Feb
(21) |
Mar
(31) |
Apr
(27) |
May
(23) |
Jun
(31) |
Jul
(35) |
Aug
(22) |
Sep
(14) |
Oct
(12) |
Nov
(24) |
Dec
(15) |
| 2010 |
Jan
(8) |
Feb
(53) |
Mar
(61) |
Apr
(11) |
May
(11) |
Jun
(5) |
Jul
(9) |
Aug
(14) |
Sep
(18) |
Oct
(19) |
Nov
(5) |
Dec
(11) |
| 2011 |
Jan
(38) |
Feb
(22) |
Mar
(22) |
Apr
(14) |
May
(6) |
Jun
(6) |
Jul
(5) |
Aug
(10) |
Sep
(40) |
Oct
(23) |
Nov
(17) |
Dec
(26) |
| 2012 |
Jan
(34) |
Feb
(54) |
Mar
(13) |
Apr
(74) |
May
(45) |
Jun
(8) |
Jul
(23) |
Aug
(30) |
Sep
(46) |
Oct
(30) |
Nov
(35) |
Dec
(8) |
| 2013 |
Jan
(43) |
Feb
(38) |
Mar
(118) |
Apr
(131) |
May
(35) |
Jun
(7) |
Jul
(57) |
Aug
(36) |
Sep
(22) |
Oct
(5) |
Nov
(14) |
Dec
(17) |
| 2014 |
Jan
(38) |
Feb
(20) |
Mar
(31) |
Apr
(16) |
May
(20) |
Jun
(2) |
Jul
(9) |
Aug
(16) |
Sep
(6) |
Oct
(3) |
Nov
(8) |
Dec
(4) |
| 2015 |
Jan
|
Feb
(23) |
Mar
(6) |
Apr
(7) |
May
|
Jun
|
Jul
(1) |
Aug
(19) |
Sep
(8) |
Oct
|
Nov
|
Dec
(10) |
| 2016 |
Jan
(2) |
Feb
(2) |
Mar
(16) |
Apr
(10) |
May
|
Jun
(5) |
Jul
(7) |
Aug
(11) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2017 |
Jan
(8) |
Feb
(16) |
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
| 2018 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
(8) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2019 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Pete <pj...@gm...> - 2025-05-22 20:22:45
|
I found a known bug entry. https://bugs.gentoo.org/706870 Dig through the comments and see if you can follow along. Typically, you need the source then patch it accordingly and rebuild. Patch: https://706870.bugs.gentoo.org/attachment.cgi?id=649446 Hope that helps. I'm long gone from ipmitool land but am apparently still on this list :) --Pete On Thu, May 22, 2025 at 3:58 PM Tony Lonsinger <tl...@my...> wrote: > Hello, > > I am hoping the list is still monitored and someone might be able to > assist me. I recently purchased a used 2U Intel Rr2000 server and ran into > an issue when attempting to update its bios. After a bit of research I > found the following on Intel's website. > > > https://www.intel.com/content/www/us/en/support/articles/000058730/server-products/server-boards.html > > This knowledge base article describes the issue I am running into and it > advised me to download the latest ipmitool. After downloading the tool and > running configure when I then run make I it errors out with the following. > Unfortunately I am now getting a little further beyond what I am familiar > with and am not able to decipher what it's getting hung on. > > /bin/bash ../libtool --silent --tag=CC --mode=link gcc -g -O2 -Wall > -Wextra -std=gnu99 -pedantic -Wformat -Wformat-nonliteral -o ipmitool > ipmitool.o ipmishell.o ../lib/libipmitool.la plugins/libintf.la > /usr/bin/ld: > ../lib/.libs/libipmitool.a(ipmi_hpmfwupg.o):/home/tlons/Downloads/ipmitool-1.8.18/lib/../include/ipmitool/ipmi_hpmfwupg.h:803: > multiple definition of `gVersionInfo'; > ipmitool.o:/home/tlons/Downloads/ipmitool-1.8.18/src/../include/ipmitool/ipmi_hpmfwupg.h:803: > first defined here > collect2: error: ld returned 1 exit status > make[3]: *** [Makefile:536: ipmitool] Error 1 > make[3]: Leaving directory '/home/tlons/Downloads/ipmitool-1.8.18/src' > make[2]: *** [Makefile:582: all-recursive] Error 1 > make[2]: Leaving directory '/home/tlons/Downloads/ipmitool-1.8.18/src' > make[1]: *** [Makefile:457: all-recursive] Error 1 > make[1]: Leaving directory '/home/tlons/Downloads/ipmitool-1.8.18' > make: *** [Makefile:388: all] Error 2 > > I am hoping someone might be able to give me a bit of direction to at > least get the ipmitool working so I can then attempt to make the needed > changes to the BCM on the board. > > Thanks in advance to anyone who is able to assist. > > -Tony > > _______________________________________________ > Ipmitool-devel mailing list > Ipm...@li... > https://lists.sourceforge.net/lists/listinfo/ipmitool-devel > |
|
From: Tony L. <tl...@my...> - 2025-05-22 19:57:15
|
Hello, I am hoping the list is still monitored and someone might be able to assist me. I recently purchased a used 2U Intel Rr2000 server and ran into an issue when attempting to update its bios. After a bit of research I found the following on Intel's website. https://www.intel.com/content/www/us/en/support/articles/000058730/server-products/server-boards.html This knowledge base article describes the issue I am running into and it advised me to download the latest ipmitool. After downloading the tool and running configure when I then run make I it errors out with the following. Unfortunately I am now getting a little further beyond what I am familiar with and am not able to decipher what it's getting hung on. /bin/bash ../libtool --silent --tag=CC --mode=link gcc -g -O2 -Wall -Wextra -std=gnu99 -pedantic -Wformat -Wformat-nonliteral -o ipmitool ipmitool.o ipmishell.o ../lib/libipmitool.la plugins/libintf.la /usr/bin/ld: ../lib/.libs/libipmitool.a(ipmi_hpmfwupg.o):/home/tlons/Downloads/ipmitool-1.8.18/lib/../include/ipmitool/ipmi_hpmfwupg.h:803: multiple definition of `gVersionInfo'; ipmitool.o:/home/tlons/Downloads/ipmitool-1.8.18/src/../include/ipmitool/ipmi_hpmfwupg.h:803: first defined here collect2: error: ld returned 1 exit status make[3]: *** [Makefile:536: ipmitool] Error 1 make[3]: Leaving directory '/home/tlons/Downloads/ipmitool-1.8.18/src' make[2]: *** [Makefile:582: all-recursive] Error 1 make[2]: Leaving directory '/home/tlons/Downloads/ipmitool-1.8.18/src' make[1]: *** [Makefile:457: all-recursive] Error 1 make[1]: Leaving directory '/home/tlons/Downloads/ipmitool-1.8.18' make: *** [Makefile:388: all] Error 2 I am hoping someone might be able to give me a bit of direction to at least get the ipmitool working so I can then attempt to make the needed changes to the BCM on the board. Thanks in advance to anyone who is able to assist. -Tony |
|
From: Mitchell A. <mit...@ca...> - 2024-12-05 16:43:45
|
Hi, We've been waiting for this patch (https://codeberg.org/IPMITool/ipmitool/pulls/39) to receive a response for several months - would it be possible for someone to review it? Thanks in advance, -- Mitchell Augustin Software Engineer - Ubuntu Partner Engineering |
|
From: Amir B. <ami...@en...> - 2024-05-07 14:16:38
|
Hi, We are developing a switch system, called 320G3UVPX, which contains an IPMI feature, using IPMB (I2C), according to VITA 46.11 standard. Us a ChMC, we are using ELMA (Samway) card – Link<http://www.samwayelectronic.com/product.php?id=24&l=en>. The last email is the last response we received from ELMA support. We have a mismatch between the information via the RS-232 Serial_COM interface (ELMA CLI) and the ETH interface (ipmitool CLI). * Serial_COM: As we can see, our card manages to respond valid data. [cid:image003.png@01DAA0A2.3C5B3F50] * ETH (ipmitool): As we can see, our card responds with invalid data. When I monitor SDA and SCL (IPMB signals) by Scope, I see the same behavior as I request SDRs data on the ELMA interface. [cid:image016.png@01DAA0A2.3C5B3F50] I’m trying to understand where the problem is in the response of SDRs information. I will appreciate your help. Best Regards, Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Friday, April 26, 2024 13:16 To: Amir Berger <ami...@en...<mailto:ami...@en...>> Cc: Chen Alon <che...@en...<mailto:che...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, Answer: In this case, the command is sent from ipmitool and when the -t 0x88 option is used the response message is coming directly from their board . Ipmitool is a third party software and I don't know how the parsing is implemented. Our board is not involved in any way in this data transfer so unfortunately there isn't anything we can help with. My assumption is that the response they send out is somehow out of spec, but as the data is not parsed by our software there is no way we could say what is wrong. Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Amir Berger <ami...@en...<mailto:ami...@en...>> Sent: Wednesday, April 24, 2024 5:00 PM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Chen Alon <che...@en...<mailto:che...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Jonathan, After comparing and using the sample SDR file (ChMC_SDR_ChassisFRU1.sdr) that came with the "SDR Complier" application, I still couldn't figure out what was wrong with our SDR data. The specific SDRs I modified are VS1 Amir1, VS Amir2, ANALOG T2. The only thing that has changed is the status sensor from "disabled" to "no reading": [cid:image016.png@01DAA0A2.3C5B3F50] Note that from the Console communication, Serial_COM, I still got a good response to the "sensor 0x88" command, no matter what changes I made to the SDRs. Please help me run some sensor with "SDR Complier" application, so that I can understand what the main problem is. I will appreciate it. Thanks, and Happy holiday 😊 Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Monday, March 4, 2024 10:56 To: Amir Berger <ami...@en...<mailto:ami...@en...>> Cc: Chen Alon <che...@en...<mailto:che...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, Answer: I don't think ipmitool has a bug. My guess is that there is a problem on IPMC which confuses ipmitool. We have tried to make the Chassis Manager software more tolerant to problems and this might be the reason why it works. Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Amir Berger <ami...@en...<mailto:ami...@en...>> Sent: Sunday, March 3, 2024 9:52 AM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Chen Alon <che...@en...<mailto:che...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Jonathan, I think it's a great long-term idea that we'll consider. But for the short term, I think we'll still stick with our FPGA implementation. Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Sunday, March 3, 2024 09:46 To: Amir Berger <ami...@en...<mailto:ami...@en...>> Cc: Chen Alon <che...@en...<mailto:che...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, Why are you developing one? We are offering the license + yearly updates. Or a by chip installation (and then you are up to date with each purchase batch). I think our offering is really cheap. We also offer porting our software to other FPGA / CPLD if this is the issue. There will be yearly updates – and you will have to update your code all the time. Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Amir Berger <ami...@en...<mailto:ami...@en...>> Sent: Sunday, March 3, 2024 9:38 AM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Chen Alon <che...@en...<mailto:che...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Jonathan, The IPMC architecture on our side is developed by us in FPGA, according to the VITA 46.11 standard. So, the conclusion that the ipmitool contains a bug? I think if there was a problem on our side, we would also see invalid data via Serial-COM communication. Best Regards, Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Thursday, February 29, 2024 14:17 To: Amir Berger <ami...@en...<mailto:ami...@en...>> Cc: Chen Alon <che...@en...<mailto:che...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, The Chassis Manager is just forwarding the messages sent by ipmitool to the IPMC. It has nothing to do with this problem. It is between ipmitool and IPMC. On IPMC is our software? Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Amir Berger <ami...@en...<mailto:ami...@en...>> Sent: Wednesday, February 28, 2024 3:04 PM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Chen Alon <che...@en...<mailto:che...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Jonathen, I have a mismatch in the response of the SDRs (sensors) data between Serial-COM and ETH communication: * Serial-COM: After “sensor 0x88” command is sent, I get the response normally: [cid:image003.png@01DAA0A2.3C5B3F50] * ETH: After “ipmitool -H 192.168.1.8 -U admin -P ADMIN -t 0x88 sdr list” command is sent, I get the response cyclically until I stop the terminal (Ctrl+C): [cid:image018.png@01DAA0A2.3C5B3F50] The same behavior also in response to the “ipmitool -H 192.168.1.8 -U admin -P ADMIN -t 0x88 sensor list” command: [cid:image019.png@01DAA0A2.3C5B3F50] Best Regards, Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Wednesday, February 14, 2024 16:45 To: Amir Berger <ami...@en...<mailto:ami...@en...>> Cc: Chen Alon <che...@en...<mailto:che...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, Answer: I am not sure I understand the problem/question. I think we speak about he new chassis manager SMW20A102. The "sendipmb" command is not present any more in this product because it conflicts with firewall. It is a way to send raw commands to any chassis manager using ipmitool "raw" command example: ipmitool -H 192.168.0.101 -U admin -P ADMIN -t 0x82 raw 6 1 This is Get Device Id: NetFn=6(app) and command =1 0x82 is target card IPMB address Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Amir Berger <ami...@en...<mailto:ami...@en...>> Sent: Wednesday, February 14, 2024 3:24 PM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Chen Alon <che...@en...<mailto:che...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Jonathen, Thanks for the new FW version! Now we don't have the last error ("Warning! FRU loading canceled for 0x84 FRU id 0! ERROR - Cannot get fru header!".) Is it possible to send IPMI requests manually in this version? Specifically, the Tier-2 mandatory commands. We have a problem with one of the customers. The customer uses their dedicated ChMC, and integration with our system disables the bus (IPMB). My goal is to send all Tier-2 mandatory commands to our system in order to verify the integrity of our system. Best Regards, Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Amir Berger Sent: Wednesday, February 7, 2024 11:08 To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hey Jonathan, Please send us the new FW version again. [cid:image020.png@01DAA0A2.3C5B3F50] Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Tuesday, January 16, 2024 18:02 To: Amir Berger <ami...@en...<mailto:ami...@en...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, Since I can’t send you a zip file: https://drive.google.com/file/d/1SpcuCJl6aL_O_kiTs-Bdyy6h4Hm5iBlb/view?usp=drive_link Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Jonathan Levinboim Sent: Tuesday, January 16, 2024 5:58 PM To: 'Amir Berger' <ami...@en...<mailto:ami...@en...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, See instructions: I have attached a firmware update. Please ask the customer to test with this version and if the problem persists to capture a log when failure occurs. The log should be captured from power until error occurs. It could be captured with commands: "logout" admin:ADMIN "debug echo 1" "saveenv" power OFF/ON ... later, after error occured "debug echo 1" (to turn off messages) "dir" "fru" "debug" "bit" To permanently disable IPMB message printing: "debug echo 1" "saveenv" Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Amir Berger <ami...@en...<mailto:ami...@en...>> Sent: Sunday, January 14, 2024 10:11 AM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Jonathan, I would appreciate an answer please. Best Regards, Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Thursday, December 28, 2023 10:28 To: Amir Berger <ami...@en...<mailto:ami...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, Support answer: We are already on vacation until January 8th. I will look into this when we are back in the office. I wish you Happy New Year! I guess we have to wait now. Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Amir Berger <ami...@en...<mailto:ami...@en...>> Sent: Sunday, December 24, 2023 2:37 PM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Jonathan, I suggest in your next version that you print something like "Fine" in such a situation. In my opinion, not printing data looks like a bug. Currently, I’m connected to a set-up that contains 2 of our cards (320G3UVPX) with IPMB communication. [cid:image021.png@01DAA0A2.3C5B3F50] After 3-4 power cycles, I get this message - "Warning! FRU loading canceled for 0x84 FRU id 0! ERROR - Cannot get fru header!". Only when I perform the following actions, I manage to reset the fault, until next time. 1. Turns off the entire setup. 2. Disconnects the IPMB Plug. 3. Turns on the entire set-up. 4. Sends to the ShMC “fru refresh”. 5. Turns off the entire setup. 6. Connects the IPMB Plug. 7. Turns on the entire set-up. 8. Sends the following commands and sees valid responses – “fru”, “fruinfo 0x82”, “fruinfo 0x84”, “sensor 0x82”, “sensor 0x84”. Note - even after the fault appears, only the response to the "fruinfo 0x84" command doesn’t respond well. All other commands above respond well. [cid:image022.png@01DAA0A2.3C5B3F50] Best Regards, Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Wednesday, December 20, 2023 11:42 To: Amir Berger <ami...@en...<mailto:ami...@en...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, The Chassis Manager prints nothing if there is no temperature event on an IPMC. It looks good. Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Amir Berger <ami...@en...<mailto:ami...@en...>> Sent: Monday, December 18, 2023 5:25 PM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Jonathan, After fixing some code issues, we were left with one problem with the FRU temperature sensor (Sensor Mandatory) indication. As you can see in the screenshot above, there isn’t value under “FRU Temp”. [cid:image023.png@01DAA0A2.3C5B3F50] I follow the instructions in “Table 10.2.5-1 Get Sensor Reading (FRU Temperature Sensor)” in VITA 46.11 DOC P.206. Only when I simulate a static value under Byte #4 (Bits 0 to 5), for example b“100000”, I see the relevant text, In this case - “Temp at or above upper non-recoverable,”. [cid:image024.png@01DAA0A2.3C5B3F50] What should the ShMC print if this byte value is x”00”? Best Regards, Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Amir Berger Sent: Sunday, December 10, 2023 17:41 To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>>; Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Jonathan, I didn’t get the attachment. @Asaf Kaspi<mailto:asa...@en...> – Please send to Jonathan an FTP. Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Sunday, December 10, 2023 15:13 To: Amir Berger <ami...@en...<mailto:ami...@en...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, Please confirm you got my last email and attachment. If not – send me an FTP Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Jonathan Levinboim Sent: Sunday, December 10, 2023 3:14 PM To: 'Amir Berger' <ami...@en...<mailto:ami...@en...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, Support answer (on a Sunday …) The "sendipmb" command was removed because it was not compliant with the new firewall/bridged-firewall introduced with VITA46.11-2022 version. Also: We made a software update that should fix the Node Busy issue. Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Amir Berger <ami...@en...<mailto:ami...@en...>> Sent: Sunday, December 10, 2023 11:03 AM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Jonathan, Can you bring back the "sendipmb" command? Looks like you disabled it in the current version. for example: [A black screen with white text Description automatically generated] In addition, I think there is an incompatibility between the current PDF from the site (Attached), contains CLI commands, and the commands I see through the "help" command. Best Regards, Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Wednesday, November 29, 2023 09:49 To: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Cc: Amir Berger <ami...@en...<mailto:ami...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Asaf, Support answer: It looks like the card plugged in slot 1 responds with Completion Code 0xC0 =Node Busy. The Chassis Manager tries 5 times and give up. We will update the software to check again after some time and never give up for Node Busy. Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Sent: Tuesday, November 28, 2023 1:48 PM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Amir Berger <ami...@en...<mailto:ami...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Thank you I'm not sure which of the connector is B and which is A, so there are two repeated tests here, each time a different connect From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Tuesday, November 28, 2023 1:14 PM To: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Cc: Amir Berger <ami...@en...<mailto:ami...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Asaf, Support answer: Isuspect there is a problem with I2C communication on IPMB. After board in slot 1 (address 0x82) boots up you can try command "sensor 0x82" to read the sensors. This will show if IPMB communication works. Please repet the test bellow: start Chassis manager with IPMB diconected, type "debug echo 1" and connect IPMB. The Chassis Manager will print all IPMI messages on CLI. Please send that log to me. Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Sent: Tuesday, November 28, 2023 1:04 PM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Amir Berger <ami...@en...<mailto:ami...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions אני לא רואה תשובה ... From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Tuesday, November 28, 2023 1:01 PM To: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Cc: Amir Berger <ami...@en...<mailto:ami...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Asaf, Support answer: Thanks I have a POWER board in the system and our board which address 0x82. I did a little experiment that might give you some information. * I turned on the system without the communication connection (-IPMI). * I did a "FRU" read. * After my system boot I connected the communication connector. * then there was a detection our board and an error-"ERROR - Cannot get fru header!". * I did a "FRU" read again. [cid:image026.png@01DAA0A2.3C5B3F50] What can cause this? In addition, there is no response to the "FRU REFRESH" command I would appreciate your consideration Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Sent: Sunday, November 26, 2023 1:00 PM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Dana Erez <Dan...@el...<mailto:Dan...@el...>>; Amir Berger <ami...@en...<mailto:ami...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions תודה לך בוצע אך אני רואה כמו קודם שגיאה שאני לא ממש יודע איך להתיחס [cid:image027.png@01DAA0A2.3C5B3F50] זאת מערכת שעבדנו איתה בעבר ולא ראינו תגובות כאלו. מה אתה מבין מזה? תודה מראש אסף From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Sunday, 26 November 2023 11:22 To: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Cc: Dana Erez <Dan...@el...<mailto:Dan...@el...>>; Amir Berger <ami...@en...<mailto:ami...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Please ask the customer to update the fiormware on Chassis Manager to the latest revision attached. The procedure is bellow: 1. Logout 2. Login with admin credentials (login:admin, pass:ADMIN 3. Send “reboot -b” command 4. Stop the bootloader countdown by pressing “x” 5. Send “xmodem firmware” command and select the update firm (*.firm) file 6. After transfer is complete, send “reboot” command. שולח לך Drive לגוגל. Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Sent: Sunday, November 26, 2023 11:11 AM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Dana Erez <Dan...@el...<mailto:Dan...@el...>>; Amir Berger <ami...@en...<mailto:ami...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions שלח לי לפרטי asi...@gm...<mailto:asi...@gm...> ושמור על אצמך From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Sunday, 26 November 2023 11:10 To: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Cc: Dana Erez <Dan...@el...<mailto:Dan...@el...>>; Amir Berger <ami...@en...<mailto:ami...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions הי אסף, אני במילואים מאז השבת. הקבצים אצלי, אנא שלחו לי FTP, או כל דרך לשלוח לכם את החומר. בברכה, Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Asaf Kaspi <asa...@en...<mailto:asa...@en...>> Sent: Sunday, November 26, 2023 9:23 AM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Dana Erez <Dan...@el...<mailto:Dan...@el...>>; Amir Berger <ami...@en...<mailto:ami...@en...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions יונתן שלום לך שמי כספי אסף ואני עובד עם אמיר על הפרוייקט הנ"ל. לא קיבלנו את הקבצים אשמח שנחשוב על דרך אחרת להעברת הקבצים. אם נוח לך לקפוץ למשרדנו, ברמת גן, ולתת לנו יד לזרז תהליכים זה בכלל יעזור לנו. יום טוב כספי אסף Asaf Kaspi Firmware Design Team Leader, Communications Division Enercon Technologies Ltd. T: +972-7-33879463 | Cell: +972-52-4800732 asa...@en...<mailto:asa...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [image001.jpg] [A black and blue background with a circle Description automatically generated] From: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Sent: Friday, 24 November 2023 8:06 To: Amir Berger <ami...@en...<mailto:ami...@en...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>>; Dana Erez <Dan...@el...<mailto:Dan...@el...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, I sent you an email with 3 file. Please confirm you got it. Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Jonathan Levinboim Sent: Friday, November 24, 2023 8:05 AM To: Amir Berger <ami...@en...<mailto:ami...@en...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>>; Dana Erez <Dan...@el...<mailto:Dan...@el...>> Subject: RE: ShMC with VPX Carrier - Compatibility issue between versions Hi Amir, Please find attached a firmware update (version 1, build 45) for the chassis manager along with the user manual where you’ll find information regarding update procedure (section 11/11.2). Also attached you have a getting started pack with all the instructions and files needed to configure and start using the chassis manager. We will also send you all GUI software needed for generating configuration files in a follow-up email; the files are “.jar” and are usually blocked by antiviruses so we will upload them on a cloud and send you a link where you’ll be able to download them. If you don’t get the follow up email soon after this one, it means your antivirus has blocked the link also. Let us know then and we’ll figure something up together. I hope this email will reach you Best Regards, Reply from Jonathan Levinboim jl...@el...<mailto:jl...@el...> | Mobile: +972-52-530 5025 From: Amir Berger <ami...@en...<mailto:ami...@en...>> Sent: Thursday, November 23, 2023 4:28 PM To: Jonathan Levinboim <Jon...@el...<mailto:Jon...@el...>> Cc: Asaf Kaspi <asa...@en...<mailto:asa...@en...>>; Dana Erez <Dan...@el...<mailto:Dan...@el...>> Subject: ShMC with VPX Carrier - Compatibility issue between versions Hey Jonathan, Following to our conversation, We got a new ShMC with these versions: * Firmware: ChMC VPX IMXRT Rev 1.0 b 37. * CORE: VPX RTOS Core Tier3 b 12. I don’t remember the full details, but our last ShMC was Tier2. Now, we have a problem where we connect our card, which contains an IPM_Controller architecture, with the same FW version that previously worked with the last ShMC (Tier2) and with the new one (Tier3) it doesn’t work. I have read the PDF files according to this link<http://www.samwayelectronic.com/product.php?id=24&l=en> and didn’t find a configuration command for the ShMC that could help me. I would appreciate your help. Best regards, Amir Berger FPGA Engineer Enercon Technologies Ltd. T: +972-3-387-9424 | Cell: +972-50-230-7302 ami...@en...<mailto:ami...@en...> | www.enercon.co.il<http://www.enercon.co.il/> [cid:image017.png@01DAA0A2.3C5B3F50] |
|
From: Al C. <ch...@ll...> - 2023-12-01 00:48:24
|
Hi, (I would have created a github issue but the "create an issue" button isn't there. Not sure if there was a recent permissions change or something.) Was helping a user with an issue in FreeIPMI https://savannah.gnu.org/support/index.php?110963 where ipmitool was outputting some fan RPMs but FreeIPMI was not. FreeIPMI reports errors from the system when sensors are read. After looking into it, I believe there is a bug in ipmitool. In `ipmi_sdr_read_sensor_value()` we have ``` if (rsp->ccode) { if ( !((sr.full && rsp->ccode == 0xcb) || (sr.compact && rsp->ccode == 0xcd)) ) { lprintf(LOG_DEBUG, "Error reading sensor %s (#%02x): %s", sr.s_id, sensor->keys.sensor_num, val2str(rsp->ccode, completion_code_vals)); } return &sr; } ``` It appears that if a response has a non-zero completion code, optionally output some debugging and then return the sensor reading data structure back to the caller. In `ipmi_sdr_print_sensor_fc()` we have the call ``` sr = ipmi_sdr_read_sensor_value(intf, sensor, sdr_record_type, 2); if (!sr) return -1; ``` So if a response has a non-zero completion code when reading a sensor, we know the sensor reading struct will be returned non-NULL. So I think the code in `ipmi_sdr_print_sensor_fc()` will continue on its way outputting things assuming the sensor reading was successful, even if it was not. Al -- Al Chu Livermore Computing Lawrence Livermore National Laboratory |
|
From: Paul N. <ma...@pa...> - 2023-06-01 14:37:51
|
Hello,
I am using ipmitool on openSUSE Leap 15.4, details about version below.
The ipmievd service fails since upgrade from Leap 15.1.
It seems, ipmievd ignores the command line option pidfile:
-
# ipmievd -vv sel daemon pidfile=/run/custompidfile.pid
ipmievd version 1.8.18
Loading IANA PEN Registry...
Using ipmi device 0
Set IPMB address to 0x20
Iana: 674
Running Get PICMG Properties my_addr 0x20, transit 0, target 0
Error response 0xc1 from Get PICMG Properties
Running Get VSO Capabilities my_addr 0x20, transit 0, target 0
Invalid completion code received: Invalid command
Acquire IPMB address
Discovered IPMB address 0x0
Interface address: my_addr 0x20 transit 0:0 target 0x20:0 ipmb_target 0
ipmievd: using pidfile /run/ipmievd.pid0
Using ipmi device 0
Set IPMB address to 0x20
-
this causes my systemd service to fail, because the configured pidfile
is not being found:
-
# systemctl status ipmievd
× ipmievd.service - Ipmievd Daemon
Loaded: loaded (/usr/lib/systemd/system/ipmievd.service; enabled;
vendor preset: disabled)
Active: failed (Result: timeout) since Thu 2023-06-01 13:52:39
CEST; 2h 24min ago
Process: 16701 ExecStart=/usr/sbin/ipmievd $IPMIEVD_OPTIONS
(code=exited, status=0/SUCCESS)
Jun 01 13:51:09 theta systemd[1]: Starting Ipmievd Daemon...
Jun 01 13:51:09 theta systemd[1]: ipmievd.service: Can't open PID file
/run/ipmievd.pid (yet?) after start: Operation not permitted
Jun 01 13:51:09 theta ipmievd[16702]: Reading sensors...
Jun 01 13:51:10 theta ipmievd[16702]: Waiting for events...
Jun 01 13:52:39 theta systemd[1]: ipmievd.service: start operation timed
out. Terminating.
Jun 01 13:52:39 theta systemd[1]: ipmievd.service: Failed with result
'timeout'.
Jun 01 13:52:39 theta systemd[1]: Failed to start Ipmievd Daemon.
-
pidfile is being created as default /run/ipmievd.pid0 despite it's
configured otherwise:
-
# cat /usr/lib/systemd/system/ipmievd.service
[Unit]
Description=Ipmievd Daemon
After=syslog.target
After=ipmi.service
[Service]
EnvironmentFile=-/etc/ipmievd
ExecStart=/usr/sbin/ipmievd $IPMIEVD_OPTIONS
Type=forking
PIDFile=/run/ipmievd.pid
[Install]
WantedBy=multi-user.target
# cat /etc/ipmievd
IPMIEVD_OPTIONS="sel daemon pidfile=/run/ipmievd.pid"
-
and finally versions:
-
# ipmievd -V
ipmievd version 1.8.18
# zypper if ipmitool
Information for package ipmitool:
---------------------------------
Repository : openSUSE_main
Name : ipmitool
Version : 1.8.18.238.gb7adc1d-150400.1.14
Arch : x86_64
Vendor : SUSE LLC <https://www.suse.com/>
Installed Size : 5.8 MiB
Installed : Yes
Status : up-to-date
Source package : ipmitool-1.8.18.238.gb7adc1d-150400.1.14.src
Upstream URL : https://github.com/ipmitool/ipmitool
Summary : Utility for IPMI Control
-
what's wrong?
thank you, kind regards
Paul Neuwirth
|
|
From: Alexander A. <ale...@am...> - 2023-05-16 09:04:21
|
Dear friends! I'm happy to announce that the project has found a new home at https://codeberg.org/IPMITool/ipmitool Hopefully, CodeBerg will be less hostile for open-source projects than GitHub revealed itself to be. You're all welcome at the new site. Unfortunately, as I have no ability to log into GitHub, I couldn't import the existing tickets and pull requests, and all the links to them in the repository commit log on CodeBerg are now broken. Please file any new problems at the new project home. Sincerely, Alexander Amelkin |
|
From: Alexander A. <a.a...@ya...> - 2023-03-07 08:43:30
|
Sorry to say, but on March 1st without any prior notice or any explanation whatsoever, GitHub has suspended my personal account and made orphan all the projects that I owned / maintained. That includes ipmitool and frugen. This mailing list and the old sourceforge project page are the only means of communication with you that I have left. I am currently searching for a way to unblock my GitHub or (less preferably) migrate ipmitool once again to another less hostile service. Thank you. Sincerely, Alexander Amelkin |
|
From: Alexander A. <a.a...@ya...> - 2019-01-25 17:43:59
|
23.01.2019 17:30, Josef Moellers wrote: > Hi, > > I'm co-maintainer/-bugowner of ipmitool within SUSE. > > I was playing around with the static code analysis tool "cppcheck" and > let it loose on the ipmitool sources. > > "Cppcheck" reported two errors in lib/ipmi_hpmfwupg.c: > > 1) In line 1401 it complained about a "resource leak": the file > pImageFile is not closed. This would be trivial to fix: just insert > fclose(pImageFile) just before the "return". > > 2) In line 2307 it complained about uninitialized variables (timeoutSec1 > and timeoutSec2) which are indeed used uninitialized if rc != > HPMFWUPG_SUCCESS in the condition of the if-statement above the while-loop. > While pondering over this, I was wondering if there was a bigger > problem: that the while-loop should actually be inside the body of the > if-statement and not outside, as it is now! Josef, thank you for your help and for the pull requests that you've created. Just for the reference that other readers could use, the mentioned issues have been all fixed in https://github.com/ipmitool/ipmitool/pull/93 Alexander. |
|
From: Josef M. <jmo...@su...> - 2019-01-23 14:30:18
|
Hi, I'm co-maintainer/-bugowner of ipmitool within SUSE. I was playing around with the static code analysis tool "cppcheck" and let it loose on the ipmitool sources. "Cppcheck" reported two errors in lib/ipmi_hpmfwupg.c: 1) In line 1401 it complained about a "resource leak": the file pImageFile is not closed. This would be trivial to fix: just insert fclose(pImageFile) just before the "return". 2) In line 2307 it complained about uninitialized variables (timeoutSec1 and timeoutSec2) which are indeed used uninitialized if rc != HPMFWUPG_SUCCESS in the condition of the if-statement above the while-loop. While pondering over this, I was wondering if there was a bigger problem: that the while-loop should actually be inside the body of the if-statement and not outside, as it is now! Can you please look at the latter? I would prepare a pull request fixing both issues but would like to see the fix for the second issue. Thanks, Josef |
|
From: Alexander A. <a.a...@ya...> - 2018-11-21 12:23:25
|
You may try to use `ipmitool i2c` but you will need to know the i2c bus number for PMBus and you will have to manually construct the PMBus request and parse the response. The request to read the output power, for example, may look like this: ``` $ ipmitool i2c bus=3 0x78 2 0x96 ``` That means "send command 0x96 (READ_POUT) to device at i2c address 0x78 on bus 3, and read back 2 bytes of response". You will then have to decode the response yourself according to PMBus specification. WBR, Alexander. 21.11.2018 11:11, Stefan K wrote: > > Hello, > > > > SuperMicro use for the JBODs on other Hardware an PMBus to query the PSU, so far as I can see it is only possible with the SuperMicro tool, is it possible to get this information via ipmitool? > > The information from the SMCIPMITool looks like: > > > > [SlaveAddress = 78h] [Module 1] Item | Value ---- | ----- Status | [ON 02h](02h) Input Voltage | 231.25 V Input Current | 0.51 A Main Output Voltage | 12.23 V Main Output Current | 7.82 A Temperature 1 | 34C/93F Temperature 2 | 41C/106F Fan 1 | 4736 RPM Fan 2 | 0 RPM Main Output Power | 97 W Input Power | 116 W PMBus Revision | 0x22 PWS Serial Number | > P1K03AG25RB0234 PWS Module Number | PWS-1K03A-1R PWS Revision | REV1.2 [SlaveAddress = 7Ah] [Module 2] Item | Value ---- | ----- Status | [ON 02h](02h) Input Voltage | 234.5 V Input Current | 0.57 A Main Output Voltage | 12.22 V Main Output Current | 9.43 A Temperature 1 | 34C/93F Temperature 2 | 44C/111F Fan 1 | 3808 RPM Fan 2 | 0 RPM Main Output Power | 114 W > Input Power | 129 W PMBus Revision | 0x22 PWS Serial Number | P1K03AG25RB0238 PWS Module Number | PWS-1K03A-1R PWS Revision | REV1.2 Interesting for is the Temperature and Input/Output Power. > > > > thanks in advance! > > > > best regards > > Stefan > > > > > > _______________________________________________ > Ipmitool-devel mailing list > Ipm...@li... > https://lists.sourceforge.net/lists/listinfo/ipmitool-devel |
|
From: Stefan K <sha...@gm...> - 2018-11-21 08:11:27
|
Hello, SuperMicro use for the JBODs on other Hardware an PMBus to query the PSU, so far as I can see it is only possible with the SuperMicro tool, is it possible to get this information via ipmitool? The information from the SMCIPMITool looks like: [SlaveAddress = 78h] [Module 1] Interesting for is the Temperature and Input/Output Power. thanks in advance! best regards Stefan |
|
From: Alexander A. <a.a...@ya...> - 2018-08-06 14:54:50
|
02.08.2018 10:48, hol...@ts... wrote: > To complicate things regarding the IPMI GUID more: > Microsoft SCVMM (System Center Virtual Machine Manager) - if I recall > correctly - expects the binary output of the IPMI Get System GUID in (native > RFC4122???) format for technical reasons unknown to me. This is used for bare > metal server discovery and deployment. > > That's why we ended up making this configurable in our BMC's. The user can > select between IPMI compatibility and SCVMM/SMBIOS 2.6 compatibility and the > binary response of the Get System GUID is reversed or not. Other BMC vendors > might have different OEM specific solutions for this. Holger, thank your for this information. Based on it I've decided to implement it in a configurable way in ipmitool as well. I'm also adding a default automatic detection of encoding based on GUID version field and on timestamp validity for version 1 GUIDs. Please take a look at branch "bugfix/25" on github and give it a try with your systems. Everyone else is also welcome to try this code with your systems before I merge it. WBR, Alexander. |
|
From: <hol...@ts...> - 2018-08-02 08:01:19
|
To complicate things regarding the IPMI GUID more: Microsoft SCVMM (System Center Virtual Machine Manager) - if I recall correctly - expects the binary output of the IPMI Get System GUID in (native RFC4122???) format for technical reasons unknown to me. This is used for bare metal server discovery and deployment. That's why we ended up making this configurable in our BMC's. The user can select between IPMI compatibility and SCVMM/SMBIOS 2.6 compatibility and the binary response of the Get System GUID is reversed or not. Other BMC vendors might have different OEM specific solutions for this. Some background information: https://blogs.technet.microsoft.com/privatecloud/2013/02/22/bare-metal-deploy-through-vmm-powershell-part-1/ http://www.miru.ch/when-scvmm-baremetal-host-deployment-fails-at-early-stages/ Holger -----Original Message----- From: Alexander Amelkin <a.a...@ya...> Sent: Friday, July 27, 2018 3:32 PM To: ipm...@li... Subject: [Ipmitool-devel] GUID decoding. Hi all! I'd like to invite anyone using BMC GUIDs to look at https://github.com/ipmitool/ipmitool/issues/25 and comment there. WBR, Alexander. |
|
From: Alexander A. <a.a...@ya...> - 2018-07-27 19:27:44
|
Hi all! I'd like to invite anyone using BMC GUIDs to look at https://github.com/ipmitool/ipmitool/issues/25 and comment there. WBR, Alexander. |
|
From: <hol...@ts...> - 2018-06-15 07:45:31
|
As Alexander already pointed out you did not provide the actual command how you set the SEL time. You can try the following command instead which will not execute the code path described below. ipmitool sel set time now Based on your information this would be my guess of what happens: 'date --utc' returns GMT/UTC time and is your input to the 'set sel time' command. This is parsed with strptime() which returns a struct tm based on the provided string, so this will also match the original GMT/UTC time and not local time. Then tm.tm_isdst is set to -1 and the struct tm passed to mktime() which will try to determine if DST is in effect based on the local timezone information of your host. My guess is that this not only sets the DST flag but also adjusts the time offset based on your local timezone information (hence the 3 hour difference result) Original discussion see (they used a simpler time sting as input without timezone information and discussed about tm.tm_isdst being set to 'random' values) <https://sourceforge.net/p/ipmitool/bugs/109/> https://sourceforge.net/p/ipmitool/bugs/109/ Some notes: The IPMI SEL time is supposed to be in local time for historical reasons (see timestamp format definition in the IPMI spec). Setting it to UTC might not be what you want to do in the first place. Also there is no real timezone information in IPMI, you just can set an UTC offset with optional IPMI commands but have to take care of switching to/from DST manually. Also this might depend on the BMC RTC, some systems share this with the main system RTC others have a separate chip for the BMC. The main system's RTC depends on the running O/S, Windows typically sets the RTC to local time while Linux sets it to UTC on x86 based hardware (I know you are running on mips64). So if the RTC is shared between your BMC and the host this has also side effects. Holger From: Anusha K <anu...@gm...> Sent: Wednesday, June 6, 2018 9:07 AM To: ipm...@li... Subject: [Ipmitool-devel] ipmitool get sel time out of sync Hi, We are trying booting a mips64 architecture board(octeon) and upgraded ipmitool from 1.8.9 to 1.8.18 version. We find that after NPT sync, date and ipmitool get sel time are not inline. Before upgrade: # ipmitool -V ipmitool version 1.8.9 #ipmitool sel time get 06/04/2018 07:35:47 # date --utc Mon Jun 4 07:35:50 UTC 2018 After upgrade: # ipmitool -V ipmitool version 1.8.18 #date --utc Mon Jun 4 07:35:50 UTC 2018 # ipmitool sel time get 06/04/2018 04:36:19 There is a 3 hours difference. When the board boots, we use ipmitool sel time get command to configure the time before NTP synchronization, which is failing with this new version. Is there any bug/fix specific to this. Please let me know if you need more information. Regards, Anusha |
|
From: Alexander A. <a.a...@ya...> - 2018-06-07 10:01:26
|
Hi, Anusha! 06.06.2018 10:07, Anusha K wrote: > We are trying booting a mips64 architecture board(octeon) and upgraded > ipmitool from 1.8.9 to 1.8.18 version. We find that after NPT sync, > date and ipmitool get sel time are not inline. > > Before upgrade: > > # ipmitool -V > > ipmitool version 1.8.9 > > #ipmitool sel time get > > 06/04/2018 07:35:47 > > # date --utc > > Mon Jun 4 07:35:50 UTC 2018 > > > After upgrade: > > # ipmitool -V > ipmitool version 1.8.18 > > #date --utc > Mon Jun 4 *07:35:50* UTC 2018 > > # ipmitool sel time get > 06/04/2018 *04:36:19* > ** > *There is a 3 hours difference.* > ** > When the board boots, we use ipmitool sel time get command to > configure the time before NTP synchronization, which is failing with > this new version. Is there any bug/fix specific to this. > > Please let me know if you need more information. I don't see any `ipmitool sel time set` commands in your log. Did you do NTP sync on both sides? I'm puzzled with the 29 second difference between the command outputs in the "after upgrade" log. Is this just due to a delay between execution of `date --utc` and `ipmitool sel time get` commands, or is it another part of the supposed bug? Between 1.8.9 and 1.8.18 there have been only three changes related to these two tickets that explicitly touched the `sel time` facility in ipmitool: https://sourceforge.net/p/ipmitool/bugs/109/ https://sourceforge.net/p/ipmitool/bugs/437/ You can browse the git log yourself to check. If you believe there is a bug, you're welcome to create a ticket on GitHub (https://github.com/ipmitool/ipmitool), to identify the commit that introduced the bug, and even to possibly fix it and create a pull request with GitHub. Alexander. |
|
From: Anusha K <anu...@gm...> - 2018-06-06 07:07:12
|
Hi, We are trying booting a mips64 architecture board(octeon) and upgraded ipmitool from 1.8.9 to 1.8.18 version. We find that after NPT sync, date and ipmitool get sel time are not inline. Before upgrade: # ipmitool -V ipmitool version 1.8.9 #ipmitool sel time get 06/04/2018 07:35:47 # date --utc Mon Jun 4 07:35:50 UTC 2018 After upgrade: # ipmitool -V ipmitool version 1.8.18 #date --utc Mon Jun 4 *07:35:50* UTC 2018 # ipmitool sel time get 06/04/2018 *04:36:19* *There is a 3 hours difference.* When the board boots, we use ipmitool sel time get command to configure the time before NTP synchronization, which is failing with this new version. Is there any bug/fix specific to this. Please let me know if you need more information. Regards, Anusha |
|
From: Alexander A. <a.a...@ya...> - 2018-04-09 17:58:14
|
For anyone having problems with the git protocol, here are some useful links: The new project home page: https://github.com/ipmitool/ipmitool The new anonymous https URL for `git clone`: https://github.com/ipmitool/ipmitool.git Hope it works for everyone. 09.04.2018 18:08, Alexander Amelkin wrote: > > Ok. The migration has happened. The sources are now on GitHub, the web > links on SourceForge has been updated accordingly and the old > repository on SourceForge has been wiped except for README for > everyone using it to notice the change. > > Please update your local repos for a new remote: > > ``` > git remote add gh gi...@gi...:/ipmitool/ipmitool.git > git remote remove origin > git remote rename gh origin > git branch --set-upstream-to=origin/master > ``` > > Please do not use the old Tickets system on SourceForge, use GitHub > issues instead. > > With best regards, > Alexander > > > 04.04.2018 12:39, Alexander Amelkin wrote: >> Hello everybody! >> >> As I've started administering ipmitool project recently, I've noticed >> that SourceForge is extremely inconvenient in terms of code review, and, >> what is more important, unstable. I encounter extremely slow git >> operations, now and then I see in browser that "repository metadata is >> not available", I've seen server errors when accessing pull requests, >> and so on. >> >> I start thinking about migrating the project to GitHub that is much more >> stable and provides better development and code reviewing tools. However >> I may be missing something about convenience of SourceForge for users, >> so I would like to hear any opinions against migration in general or >> against GitHub in particular. >> >> Alexander. >> >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> >> >> _______________________________________________ >> Ipmitool-devel mailing list >> Ipm...@li... >> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Ipmitool-devel mailing list > Ipm...@li... > https://lists.sourceforge.net/lists/listinfo/ipmitool-devel |
|
From: Alexander A. <a.a...@ya...> - 2018-04-09 15:08:24
|
Ok. The migration has happened. The sources are now on GitHub, the web links on SourceForge has been updated accordingly and the old repository on SourceForge has been wiped except for README for everyone using it to notice the change. Please update your local repos for a new remote: ``` git remote add gh gi...@gi...:/ipmitool/ipmitool.git git remote remove origin git remote rename gh origin git branch --set-upstream-to=origin/master ``` Please do not use the old Tickets system on SourceForge, use GitHub issues instead. With best regards, Alexander 04.04.2018 12:39, Alexander Amelkin wrote: > Hello everybody! > > As I've started administering ipmitool project recently, I've noticed > that SourceForge is extremely inconvenient in terms of code review, and, > what is more important, unstable. I encounter extremely slow git > operations, now and then I see in browser that "repository metadata is > not available", I've seen server errors when accessing pull requests, > and so on. > > I start thinking about migrating the project to GitHub that is much more > stable and provides better development and code reviewing tools. However > I may be missing something about convenience of SourceForge for users, > so I would like to hear any opinions against migration in general or > against GitHub in particular. > > Alexander. > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Ipmitool-devel mailing list > Ipm...@li... > https://lists.sourceforge.net/lists/listinfo/ipmitool-devel |
|
From: Vasant H. <heg...@li...> - 2018-04-07 12:09:17
|
On 04/06/2018 06:36 PM, Alexander Amelkin wrote: > 06.04.2018 12:49, Vasant Hegde wrote: >> On 04/04/2018 03:09 PM, Alexander Amelkin wrote: >>> Hello everybody! >>> >>> As I've started administering ipmitool project recently, I've noticed >>> that SourceForge is extremely inconvenient in terms of code review, and, >>> what is more important, unstable. I encounter extremely slow git >>> operations, now and then I see in browser that "repository metadata is >>> not available", I've seen server errors when accessing pull requests, >>> and so on. >>> >>> I start thinking about migrating the project to GitHub that is much more >>> stable and provides better development and code reviewing tools. However >>> I may be missing something about convenience of SourceForge for users, >>> so I would like to hear any opinions against migration in general or >>> against GitHub in particular. >> >> Good move. >> >> AFAIK github doesn't provide mailing list facility. So do you want to >> keep existing mailing list -OR- switch to pull request method for >> submitting patches/questions? > > Thanks for this point. Personally I think that mailing lists are an > inconvenient outdated technology if used for patches and their I still use this outdated technology in many projects ;-) But I've no objection to move to github. > discussion. I prefer bugtrackers (github issues, sourceforge tickets, > whatever). Pull requests are good, but patches attached to issues are > fine as well. > > Anyway, I wasn't planning to shut down the mailing lists as it is a good > means of communication on common topics like this. The idea was to move > source code and bug tracking to github, leaving it integrated with > sourceforge so that users would still be able to find the project the > usual way, take releases from sourceforge if they prefer, and use > mailing lists if they want to. I just want to make development easier. > Alternatively you can consider uptingte sourceforge repo with something like "source code moved to github". Having stuff in two places invites complication. But its your choice. I'm fine with either approach. Finally whatever you decide please make necessary updates to README file. Not that people (like me) reads README.. but at least you can point people to README :-) -Vasant |
|
From: Al C. <ch...@ll...> - 2018-04-06 16:19:48
|
> Anyway, I wasn't planning to shut down the mailing lists as it is a > good > means of communication on common topics like this. The idea was to > move > source code and bug tracking to github, leaving it integrated with > sourceforge so that users would still be able to find the project the > usual way, take releases from sourceforge if they prefer, and use > mailing lists if they want to. I just want to make development > easier. Just a comment. I assumed "Migrate to Github" meant "everything gets moved" kind of thing. I think having two locations be "valid" is confusing. One idea, which is what I did for FreeIPMI, is I made a mirror of the repo on github for my own personal development. I clearly indicate its a mirror, indicate I am the maintainer and willing to accept pull requests, but the main stuff is elsewhere. Al On Fri, 2018-04-06 at 16:06 +0300, Alexander Amelkin wrote: > 06.04.2018 12:49, Vasant Hegde wrote: > > On 04/04/2018 03:09 PM, Alexander Amelkin wrote: > > > Hello everybody! > > > > > > As I've started administering ipmitool project recently, I've > > > noticed > > > that SourceForge is extremely inconvenient in terms of code > > > review, and, > > > what is more important, unstable. I encounter extremely slow git > > > operations, now and then I see in browser that "repository > > > metadata is > > > not available", I've seen server errors when accessing pull > > > requests, > > > and so on. > > > > > > I start thinking about migrating the project to GitHub that is > > > much more > > > stable and provides better development and code reviewing tools. > > > However > > > I may be missing something about convenience of SourceForge for > > > users, > > > so I would like to hear any opinions against migration in general > > > or > > > against GitHub in particular. > > > > Good move. > > > > AFAIK github doesn't provide mailing list facility. So do you want > > to > > keep existing mailing list -OR- switch to pull request method for > > submitting patches/questions? > > Thanks for this point. Personally I think that mailing lists are an > inconvenient outdated technology if used for patches and their > discussion. I prefer bugtrackers (github issues, sourceforge tickets, > whatever). Pull requests are good, but patches attached to issues are > fine as well. > > Anyway, I wasn't planning to shut down the mailing lists as it is a > good > means of communication on common topics like this. The idea was to > move > source code and bug tracking to github, leaving it integrated with > sourceforge so that users would still be able to find the project the > usual way, take releases from sourceforge if they prefer, and use > mailing lists if they want to. I just want to make development > easier. > > With best regards, > Alexander. > > > ------------------------------------------------------------------- > ----------- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Ipmitool-devel mailing list > Ipm...@li... > https://lists.sourceforge.net/lists/listinfo/ipmitool-devel |
|
From: Alexander A. <a.a...@ya...> - 2018-04-06 13:06:42
|
06.04.2018 12:49, Vasant Hegde wrote: > On 04/04/2018 03:09 PM, Alexander Amelkin wrote: >> Hello everybody! >> >> As I've started administering ipmitool project recently, I've noticed >> that SourceForge is extremely inconvenient in terms of code review, and, >> what is more important, unstable. I encounter extremely slow git >> operations, now and then I see in browser that "repository metadata is >> not available", I've seen server errors when accessing pull requests, >> and so on. >> >> I start thinking about migrating the project to GitHub that is much more >> stable and provides better development and code reviewing tools. However >> I may be missing something about convenience of SourceForge for users, >> so I would like to hear any opinions against migration in general or >> against GitHub in particular. > > Good move. > > AFAIK github doesn't provide mailing list facility. So do you want to > keep existing mailing list -OR- switch to pull request method for > submitting patches/questions? Thanks for this point. Personally I think that mailing lists are an inconvenient outdated technology if used for patches and their discussion. I prefer bugtrackers (github issues, sourceforge tickets, whatever). Pull requests are good, but patches attached to issues are fine as well. Anyway, I wasn't planning to shut down the mailing lists as it is a good means of communication on common topics like this. The idea was to move source code and bug tracking to github, leaving it integrated with sourceforge so that users would still be able to find the project the usual way, take releases from sourceforge if they prefer, and use mailing lists if they want to. I just want to make development easier. With best regards, Alexander. |
|
From: Vasant H. <heg...@li...> - 2018-04-06 12:37:56
|
On 04/04/2018 03:09 PM, Alexander Amelkin wrote: > Hello everybody! > > As I've started administering ipmitool project recently, I've noticed > that SourceForge is extremely inconvenient in terms of code review, and, > what is more important, unstable. I encounter extremely slow git > operations, now and then I see in browser that "repository metadata is > not available", I've seen server errors when accessing pull requests, > and so on. > > I start thinking about migrating the project to GitHub that is much more > stable and provides better development and code reviewing tools. However > I may be missing something about convenience of SourceForge for users, > so I would like to hear any opinions against migration in general or > against GitHub in particular. Good move. AFAIK github doesn't provide mailing list facility. So do you want to keep existing mailing list -OR- switch to pull request method for submitting patches/questions? -Vasant |
|
From: Vernon M. <ver...@li...> - 2018-04-04 16:57:10
|
On 04-Apr-2018 12:39 PM, Alexander Amelkin wrote: >Hello everybody! > >As I've started administering ipmitool project recently, I've noticed >that SourceForge is extremely inconvenient in terms of code review, and, >what is more important, unstable. I encounter extremely slow git >operations, now and then I see in browser that "repository metadata is >not available", I've seen server errors when accessing pull requests, >and so on. > >I start thinking about migrating the project to GitHub that is much more >stable and provides better development and code reviewing tools. However >I may be missing something about convenience of SourceForge for users, >so I would like to hear any opinions against migration in general or >against GitHub in particular. I think this is a welcome change. I have found the same issues with sourceforge and don't think that it really has much to offer that github does not. And github seems to be a much better and responsive server. --Vernon |
86 messages has been excluded from this view by a project administrator.
