RE: [Freeipmi-devel] Re: SEL datestamp 01-Jan-1970?

2009-02-18 Thread Andy Cress
0.66, you should upgrade to that. Andy -Original Message- From: Won De Erick [mailto:won.der...@yahoo.com] Sent: Tuesday, February 17, 2009 8:57 PM To: Andy Cress; ch...@llnl.gov Cc: freeipmi-devel@gnu.org; freeipmi-us...@gnu.org Subject: RE: [Freeipmi-devel] Re: SEL datestamp 01-Jan

[Freeipmi-devel] [bug #24300] ipmiconsole cannot connect to various Intel servers

2009-10-06 Thread Andy Cress
Follow-up Comment #6, bug #24300 (project freeipmi): How did this get changed from Open with BMC Error to fixed, without code changes being implemented? ___ Reply to this item at: http://savannah.gnu.org/bugs/?24300

RE: [Freeipmi-devel] 64-bit issues with OpenIPMI driver on FreeBSD-7.2

2009-12-04 Thread Andy Cress
Mark, There is definitely an interface incompatibility between the FreeBSD ipmi driver and the Linux OpenIPMI driver. The same code to talk to /dev/ipmi0 on Linux does not work on FreeBSD (either 32-bit or 64-bit). I haven't diagnosed why exactly, but the ipmi_req size is a start. If we had

RE: [Freeipmi-devel] 64-bit issues with OpenIPMI driver on FreeBSD-7.2

2009-12-28 Thread Andy Cress
=users.sourceforge@gnu.org [mailto:freeipmi-devel-bounces+arcress=users.sourceforge@gnu.org] On Behalf Of Andy Cress Sent: Friday, December 04, 2009 9:47 AM To: ch...@llnl.gov; Mark Lokowich Cc: freeipmi-devel@gnu.org Subject: RE: [Freeipmi-devel] 64-bit issues with OpenIPMI driver on FreeBSD-7.2 Mark

RE: [Freeipmi-devel] Intel SR2500 ipmi-sensors

2010-09-01 Thread Andy Cress
-devel-bounces+aray=niksun@gnu.org [mailto:freeipmi- devel-bounces+aray=niksun@gnu.org] On Behalf Of Anand Babu Periasamy Sent: Tuesday, August 31, 2010 9:06 PM To: freeipmi-devel@gnu.org Subject: Re: [Freeipmi-devel] Intel SR2500 ipmi-sensors On 08/31/2010 01:09 PM, Andy Cress

RE: [Freeipmi-devel] HP Proliant DL360 G4 - Email found in subject

2010-09-15 Thread Andy Cress
iLO is based on IPMI (HP was one of the 4 collaborators in writing the spec), but there are extensions and changes to the interfaces for HP stuff. Andy -Original Message- From: freeipmi-devel-bounces+arcress=users.sourceforge@gnu.org

Re: [Freeipmi-devel] Issue with Supermicro X8SIL

2011-08-29 Thread Andy Cress
Hmmm. AFAIK, the 47488 IANA number was assigned to WinBond, so I believe the firmware vendor should be WinBond, but the system vendor in this case is SuperMicro, using the WinBond BMC. SuperMicro has used 4 different BMC vendors over time, by my count. However, the iana.org site has not

Re: [Freeipmi-devel] FreeIPMI on windows

2011-12-07 Thread Andy Cress
Arnaud, There are binary packages available for Windows of ipmiutil, built with each release, see http://ipmiutil.sourceforge.net. It has all of the IPMI features that you see in freeipmi. It is currently not packaged in an MSI, but will be soon. Andy From:

Re: [Freeipmi-devel] FreeIPMI on windows

2011-12-16 Thread Andy Cress
Arnaud, The ipmiutil-2.8.0 release did go out today with the MSI, see http://ipmiutil.sf.net And the Linux -devel package is included as well. Andy ---previously:--- thanks for this info. do you have any approx. timeline for the MSI? A: Plan is later this month (Dec) for

Re: [Freeipmi-devel] clean exit of external process whenconmand shuts down

2012-01-16 Thread Andy Cress
Brian, I ran across another BMC firmware a while ago that had a broken concept of SOL deactivate also, requiring the deactivate to be hooked to the (probably now defunct) user session that did the SOL activate. Until the firmware allows any admin-privileged IPMI user to deactivate SOL, the

Re: [Freeipmi-devel] ipmi configuration security best practices

2013-02-19 Thread Andy Cress
Dan, RE 5. 20-character passwords This assumes that all deployed platforms are IPMI 2.0, since IPMI 1.5 platforms only support 16-character passwords. There are still some IPMI 1.5 platforms in use out there. RE 12. Disable gratuitous ARP replies The description here is a bit off. There are

Re: [Freeipmi-devel] Sensor thresholds and sensor capabilities bits

2013-07-02 Thread Andy Cress
Holger, By all means it should adhere to the spec, but I'm confused as to how this 11b value got introduced, when it should have been correct when read from the vendor-supplied SDRs? Was this value written when setting a threshold perhaps? If so, it seems that the value should have been passed

Re: [Freeipmi-devel] bad sensor name when using entity-sensor-names

2013-07-19 Thread Andy Cress
Al, IMO, the entity name+num and the sensor name should be separate fields so that this is not so confusing, i.e. insert a '|' delimiter between the two. Andy On Fri, Jul 19, 2013 at 2:16 PM, Hank Bruning h...@jblade.com wrote: As usual Albert is correct. The root cause of this is IPMI. Note

Re: [Freeipmi-devel] [SPAM] - RE: Retrieving BIOS information via IPMI - Email found in subject

2014-01-09 Thread Andy Cress
Hmmm. I didn't know that. So in this case the SuperMicro BIOS has opened a proprietary conduit via the IPMI firmware. And the commands are then passed via IPMI LAN to the BIOS (in main memory) which has access to the data and responds. I guess the elaborate key mechanism is more for licensing

Re: [Freeipmi-devel] internal IPMI error on successful ipmi_cmd_dcmi_set_asset_tag

2015-07-27 Thread Andy Cress
Yes, SuperMicro firmware is IPMI-lite. It does the basics, but compliance is not adhered to strictly. On Jul 28, 2015 3:21 AM, Albert Chu ch...@llnl.gov wrote: Hey Curtis, I believe I have a fix in this branch if you could try it out. svn co

Re: [Freeipmi-devel] RE : Ipmiping bug Centos 7.1.1503

2016-01-04 Thread Andy Cress
Be sure that you type the dash '-'. I see that frequently mangled by email clients with cut/paste. Just a thought. Andy On Mon, Jan 4, 2016 at 3:21 PM, Soufiane Benkhalifa wrote: > Hi, > I've already tried with a version for Centos 7 but didn't work. > I then

Re: ipmi-oem Supermicro get-power-supply-status issue

2020-08-27 Thread Andy Cress
Quite so. SuperMicro is slow to give firmware fixes, but having the latest available firmware helps. On Thu, Aug 27, 2020 at 2:08 PM Al Chu wrote: > On Thu, 2020-08-27 at 14:04 -0400, Andrew Orme wrote: > > Indeed. Seems to run fine on our other systems running the same exact > > hardware.