Re: [CentOS] IPMI ??
On Sun, September 18, 2016 19:08, Keith Keller wrote: > > Make sure you do not allow the IPMI's IP to be accessible > on a public network. Either keep the IP on a private network > (better), keep the IP firewalled to only certain IPs, > or change the admin password from the default. In order of importance: 1. ALWAYS change the administrative account credentials from their defaults to something reasonably difficult to infer. Supermicro allows one to select the user name of the administrative account in addition to setting the password. Change both. 2. Always restrict access to IPMI from specific source addresses. If you need to obtain access from from a different point of origin then set up one or more of the hosts having a permitted IP as an sshd/vpn service in advance and relay to the IPMI port from there. 3. Firewall any IPMI IP addresses at the gateway for all protocols and prevent any direct access to it whatsoever from the internet. 4. Where feasible place all IPMI IP addresses on their own private IP network ([192.168.X.0/24] or similar) and set up the gateway router internal interface to suit. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI ??
On 9/18/2016 4:03 PM, Keith Keller wrote: On 2016-09-18, Boris Epsteinwrote: >Is there a little setup display right on the box? Just asking because I >have seen that on some boxes. You mean for configuring the IPMI interface? I've never seen that but it sounds very cool. Do you have specific references for systems which you've seen that on? the SUpermicro IPMI's I've used, you'd configure from linux after installing ipmitools and starting the ipmi service. # ipmitool mc status Invalid mc/bmc command: status MC Commands: reset guid info watchdog selftest getenables setenables
Re: [CentOS] IPMI ??
On 09/18/2016 04:08 PM, Keith Keller wrote: Make sure you do not allow the IPMI's IP to be accessible on a public network. Either keep the IP on a private network (better), keep the IP firewalled to only certain IPs, or change the admin password from the default. --keith What I had toyed with doing was setting up a switch just for the IPMI with an ethernet jack above my breakfast far (this pc will be installed on other side of breakfast bar) - no connection even to it even from my LAN. -- -=- Sent my from my laptop, may not be able to respond timely ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI ??
Keith, I am sorry, unfortunately I don't remember model numbers. Those were Dell boxes as far as I remember. Boris. On Sun, Sep 18, 2016 at 7:03 PM, Keith Keller < kkel...@wombat.san-francisco.ca.us> wrote: > On 2016-09-18, Boris Epsteinwrote: > > Is there a little setup display right on the box? Just asking because I > > have seen that on some boxes. > > You mean for configuring the IPMI interface? I've never seen that but > it sounds very cool. Do you have specific references for systems which > you've seen that on? > > --keith > > -- > kkel...@wombat.san-francisco.ca.us > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI ??
On 2016-09-18, Alice Wonderwrote: > > But for now via VGA cable it is all working. > > Once I'm back home and this server is set up where it goes, I'll try > playing with non-browser IPMI tools and see what it is all about. Now that you have a console, you can use the *ipmi tools to assign an IP address to the IPMI interface yourself, then use the Supermicro Java GUI to get to it from anywhere on the same network. It's a great feature to have even if it's not your preferred method to get to the console, because at least it's a backup method (and might be handy for helping you test your video card). Make sure you do not allow the IPMI's IP to be accessible on a public network. Either keep the IP on a private network (better), keep the IP firewalled to only certain IPs, or change the admin password from the default. --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI ??
On 2016-09-18, Boris Epsteinwrote: > Is there a little setup display right on the box? Just asking because I > have seen that on some boxes. You mean for configuring the IPMI interface? I've never seen that but it sounds very cool. Do you have specific references for systems which you've seen that on? --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI ??
Is there a little setup display right on the box? Just asking because I have seen that on some boxes. Cheers, Boris. On Sun, Sep 18, 2016 at 12:15 AM, Keith Keller < kkel...@wombat.san-francisco.ca.us> wrote: > On 2016-09-17, Alice Wonderwrote: > > > > Okay if it requires DHCP this might be out, I'm currently out of town > > watching my brothers (various disabilities) while parents are on much > > needed vacation. Don't have easy physical access to the router, would > > have to take out stuff in front of it. Was hoping crossover ethernet > > would work. > > It probably would, but you still need some way to assign an IP address > to the IPMI interface (it probably doesn't have one out of the box). > But from your laptop you can run a DHCP server which would then assign > an IP to the IPMI interface. > > The IPMI might self-assign if it can't find a DHCP server, but in my > memory (which might be faulty) it doesn't do this. > > If for some reason Java doesn't work from your browser, Supermicro also > distributes a Java GUI tool for interacting with Supermicro IPMI > interfaces. It also supports a subnet scanner, so you don't need to > know the IP that gets assigned. Look for IPMIview here: > > http://www.supermicro.com/products/nfo/IPMI.cfm > > It's not a great tool but it works well enough for console access. > > --keith > > -- > kkel...@wombat.san-francisco.ca.us > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI ??
On 09/17/2016 09:15 PM, Keith Keller wrote: On 2016-09-17, Alice Wonderwrote: Okay if it requires DHCP this might be out, I'm currently out of town watching my brothers (various disabilities) while parents are on much needed vacation. Don't have easy physical access to the router, would have to take out stuff in front of it. Was hoping crossover ethernet would work. It probably would, but you still need some way to assign an IP address to the IPMI interface (it probably doesn't have one out of the box). But from your laptop you can run a DHCP server which would then assign an IP to the IPMI interface. The IPMI might self-assign if it can't find a DHCP server, but in my memory (which might be faulty) it doesn't do this. If for some reason Java doesn't work from your browser, Supermicro also distributes a Java GUI tool for interacting with Supermicro IPMI interfaces. It also supports a subnet scanner, so you don't need to know the IP that gets assigned. Look for IPMIview here: I bought a VGA capable. I don't yet know if the video card is bad or the board just can't use it, I'll find that out later. But for now via VGA cable it is all working. For what's worth, removing both flash and java capabilities from my browser was the second best thing I ever did (privacy badger the best), don't want to re-install either. Once I'm back home and this server is set up where it goes, I'll try playing with non-browser IPMI tools and see what it is all about. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI ??
On 18/09/16 12:15 AM, Keith Keller wrote: > On 2016-09-17, Alice Wonderwrote: >> >> Okay if it requires DHCP this might be out, I'm currently out of town >> watching my brothers (various disabilities) while parents are on much >> needed vacation. Don't have easy physical access to the router, would >> have to take out stuff in front of it. Was hoping crossover ethernet >> would work. > > It probably would, but you still need some way to assign an IP address > to the IPMI interface (it probably doesn't have one out of the box). > But from your laptop you can run a DHCP server which would then assign > an IP to the IPMI interface. > > The IPMI might self-assign if it can't find a DHCP server, but in my > memory (which might be faulty) it doesn't do this. > > If for some reason Java doesn't work from your browser, Supermicro also > distributes a Java GUI tool for interacting with Supermicro IPMI > interfaces. It also supports a subnet scanner, so you don't need to > know the IP that gets assigned. Look for IPMIview here: > > http://www.supermicro.com/products/nfo/IPMI.cfm > > It's not a great tool but it works well enough for console access. > > --keith I have a section on using and configuring IPMI in EL6 from the command line. Might be of use to some here: https://alteeve.ca/w/AN!Cluster_Tutorial_2#What_is_IPMI -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI ??
On 2016-09-17, Alice Wonderwrote: > > Okay if it requires DHCP this might be out, I'm currently out of town > watching my brothers (various disabilities) while parents are on much > needed vacation. Don't have easy physical access to the router, would > have to take out stuff in front of it. Was hoping crossover ethernet > would work. It probably would, but you still need some way to assign an IP address to the IPMI interface (it probably doesn't have one out of the box). But from your laptop you can run a DHCP server which would then assign an IP to the IPMI interface. The IPMI might self-assign if it can't find a DHCP server, but in my memory (which might be faulty) it doesn't do this. If for some reason Java doesn't work from your browser, Supermicro also distributes a Java GUI tool for interacting with Supermicro IPMI interfaces. It also supports a subnet scanner, so you don't need to know the IP that gets assigned. Look for IPMIview here: http://www.supermicro.com/products/nfo/IPMI.cfm It's not a great tool but it works well enough for console access. --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI ??
On 9/17/2016 3:25 AM, Alice Wonder wrote: Never used IPMI in my life and while I thought it was cool when I heard about it, had no plans to. Just built a home server (while out of town) using a SUPERMICRO MBD-X10SLM+-F-O I put an nVidia 405 based video card in it but it may be bad. When I power it on, I get some beeps but they are different than the no memory beeps (I intentionally powered on w/o memory to hear those) and I think what may be happening is normal boot process but no video simply because the card (bought used) may be bad. Before I go and try to find a retailer that still carries VGA cables, is there a way via the boards IPMI interface (it has ethernet port just for that) to connect from my CentOS 7 laptop and see if the machine is normally powering on? I saw some IPMI packages exist for CentOS 7 but I don't know if this is what they are for. And it seems there are OpenIPMI and freeimpi packages. Are those just different ways of doing same thing or do they serve different purposes? the supermicro IPMI has a webserver, you can connect to it with a web browser, and can do remote console, remote media... the remote console requires java support in your web browser. -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI ??
On 09/17/2016 04:11 AM, Mauricio Tavares wrote: On Sat, Sep 17, 2016 at 6:25 AM, Alice Wonderwrote: Never used IPMI in my life and while I thought it was cool when I heard about it, had no plans to. Under many different names (Sun called it LOM; I forgot IBM's name), this has been out there for a while. And it is IMHO the best way to deal with servers. My normal server installing procedure is: 1. slap server wherever it will reside 2. Run the power cords 3. Run the ethernet cords for both normal use and IPMI. I'd probably be mindful of which vlans each cable goes to. 4. Fire computer up 5. Connect to the IPMI ethernet port using openipmi/whatever; by default it is generally setup to do dhcp. 6. Through ipmi, configure server's bios/raid/whatever and then boot it, feeding an ISO with the OS of choice through ipmi. Good time to do any server bios upgrade too. 7. Don't forget to change IPMI PW! Okay if it requires DHCP this might be out, I'm currently out of town watching my brothers (various disabilities) while parents are on much needed vacation. Don't have easy physical access to the router, would have to take out stuff in front of it. Was hoping crossover ethernet would work. Connect both to a switch attached to your dhcp server (or make laptop provide that to ipmi) and then connect from laptop to ipmi and go do your thing. Video cards are for desktops. Server room I agree, home server it really makes it easy to have several terminal windows open at same time and even launch a browser to troubleshoot something without needing to ssh in from another box. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI ??
On Sat, Sep 17, 2016 at 6:25 AM, Alice Wonderwrote: > Never used IPMI in my life and while I thought it was cool when I heard > about it, had no plans to. > Under many different names (Sun called it LOM; I forgot IBM's name), this has been out there for a while. And it is IMHO the best way to deal with servers. My normal server installing procedure is: 1. slap server wherever it will reside 2. Run the power cords 3. Run the ethernet cords for both normal use and IPMI. I'd probably be mindful of which vlans each cable goes to. 4. Fire computer up 5. Connect to the IPMI ethernet port using openipmi/whatever; by default it is generally setup to do dhcp. 6. Through ipmi, configure server's bios/raid/whatever and then boot it, feeding an ISO with the OS of choice through ipmi. Good time to do any server bios upgrade too. 7. Don't forget to change IPMI PW! > Just built a home server (while out of town) using a SUPERMICRO > MBD-X10SLM+-F-O > > I put an nVidia 405 based video card in it but it may be bad. > > When I power it on, I get some beeps but they are different than the no > memory beeps (I intentionally powered on w/o memory to hear those) and I > think what may be happening is normal boot process but no video simply > because the card (bought used) may be bad. > > Before I go and try to find a retailer that still carries VGA cables, is > there a way via the boards IPMI interface (it has ethernet port just for > that) to connect from my CentOS 7 laptop and see if the machine is normally > powering on? > Connect both to a switch attached to your dhcp server (or make laptop provide that to ipmi) and then connect from laptop to ipmi and go do your thing. Video cards are for desktops. > I saw some IPMI packages exist for CentOS 7 but I don't know if this is what > they are for. > > And it seems there are OpenIPMI and freeimpi packages. Are those just > different ways of doing same thing or do they serve different purposes? > Personally I do not think the supermicro box cares. IPMI is a standard. Whichever you use should provide a way to send out (remote) commands and then have a console so you can install thingies in the server. With that said, I have used openipmi myself; you do want the ipmitool, which is a package. Sample commands (lookup to see what they do. Notice I am using default l/p): ipmitool -I lan -H 192.168.21.125 -U ADMIN -P ADMIN sel ipmitool -I lanplus -H 192.168.21.125 -U ADMIN -P ADMIN mc reset cold ipmitool -I lanplus -H 192.168.21.112 -U ADMIN -P ADMIN mc info References I have used: http://wiki.hetzner.de/index.php/IPMI/en http://lists.us.dell.com/pipermail/linux-poweredge/2007-January/029190.html > Thanks. > > > > > -- > -=- > Sent my from my laptop, may not be able to respond timely > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] IPMI ??
Never used IPMI in my life and while I thought it was cool when I heard about it, had no plans to. Just built a home server (while out of town) using a SUPERMICRO MBD-X10SLM+-F-O I put an nVidia 405 based video card in it but it may be bad. When I power it on, I get some beeps but they are different than the no memory beeps (I intentionally powered on w/o memory to hear those) and I think what may be happening is normal boot process but no video simply because the card (bought used) may be bad. Before I go and try to find a retailer that still carries VGA cables, is there a way via the boards IPMI interface (it has ethernet port just for that) to connect from my CentOS 7 laptop and see if the machine is normally powering on? I saw some IPMI packages exist for CentOS 7 but I don't know if this is what they are for. And it seems there are OpenIPMI and freeimpi packages. Are those just different ways of doing same thing or do they serve different purposes? Thanks. -- -=- Sent my from my laptop, may not be able to respond timely ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI/BMC/BIOS
On Thu, 2 Jul 2015 10:11:09 + (UTC) Chris Olson chris_e_ol...@yahoo.com wrote: ... My initial recommendation was to use a totally separate network for any service processors +1 for this. We typically put all management ports for a 'system/project' on a sep. non-routed eth. segment to which only the, for the 'system/project', designated management servers can connect. It is probably a good idea to consider random ethernet connected 'things' as soft security wise and not suitable for the big bad internet... As for bios/firmware on servers the best one can do is to use non-deprecated hardware from responsible vendors and keep up to date with their sec. info and update promptly when required. /Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] IPMI/BMC/BIOS
We have recently been asked to evaluate some computing machinery for a new project. This particular end user has very limited experience with the stated security requirements in a lights-out environment. Their primary work (as well as mine) in the past has been with very small, simple networks of desktop machines and a few servers with extremely limited access. For the most part, their admins haverefused to use any maintenance connectivity to servers other thanthe primary serial ports. There is a concern about system security primarily driven by recent information searches performed by end user admins and included below. IPMI/BMC Security Issues https://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface http://www.google.com Search: IPMI Security Holes -- Hits: 14,500 http://www.google.com Search: IPMI BMC Security Holes -- Hits: 4950 BIOS Security Issues https://en.wikipedia.org/wiki/BIOS http://www.google.com Search: BIOS Security Holes -- Hits: 342,000 My initial recommendation was to use a totally separate network for any service processors within the servers that implement IPMI/BMC capabilities. This has been standard practice in most systems I have worked on in the past, and has allowed certification with essentially no problems. The BIOS concern seems to be another issue to be addressed separately. Any connectivity and access to a system brings security issues. The list from these searches is huge. Are there specific things that must always be addressed for system security besides keeping junior admins off the server supporting the maintenance network? Thanks in advance for any feedback and best regards. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI/BMC/BIOS
On Thu, Jul 02, 2015 at 12:30:47PM -0400, Paul Heinlein wrote: If your admins are comfortable with serial consoles, a concentrator like those available from Digi or WTI can offer fairly robust access controls; they can also be set to honor SSH keys rather than passwords, which may help increase security. I've used those for devices that were fairly dumb, but for servers it can be nicely cheaper to use serial-over-ipmi plus conman for that purpose. It's necessary to log and monitor the serial consoles, there are a variety of OOPses and BUGs and whatnot that only appear there. I've been using 'conman' for this purpose. I totally agree with you about having a separate admin-only network. It's not that expensive to build one up using dumb switches. -- greg ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI/BMC/BIOS
On Thu, 2 Jul 2015, Chris Olson wrote: We have recently been asked to evaluate some computing machinery for a new project. This particular end user has very limited experience with the stated security requirements in a lights-out environment. Their primary work (as well as mine) in the past has been with very small, simple networks of desktop machines and a few servers with extremely limited access. For the most part, their admins haverefused to use any maintenance connectivity to servers other than the primary serial ports. There is a concern about system security primarily driven by recent information searches performed by end user admins and included below. [...snip...] My initial recommendation was to use a totally separate network for any service processors within the servers that implement IPMI/BMC capabilities. This has been standard practice in most systems I have worked on in the past, and has allowed certification with essentially no problems. The BIOS concern seems to be another issue to be addressed separately. +1 to network separation for OOB management. I assume you mean non-routable LAN, but that segment's connectivity is an interesting question in itself. I like having access to management consoles via VPN, but others dislike any off-LAN access whatsoever. If your admins are comfortable with serial consoles, a concentrator like those available from Digi or WTI can offer fairly robust access controls; they can also be set to honor SSH keys rather than passwords, which may help increase security. WTI: https://www.wti.com/c-4-console-server.aspx Digi: http://www.digi.com/products/consoleservers/ I've had an easier time working with the Digi firmware, but either will do the job. -- Paul Heinlein heinl...@madboa.com http://www.madboa.com/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPMI/BMC/BIOS
https://lwn.net/Articles/630778/ I think you definitely want this stuff as far away from the regular LAN, let alone the Internet, as possible. Chris Murphy ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ipmi regression in 4.5?
On Tue, Jun 26, 2007 at 11:31:47AM +1000, Gavin Carr wrote: I have created an updated SRPM which reverses that part of the Woodcrest fixes that affect these Dells - if you are interested, the SRPM is at: ftp://ftp.moving-picture.com/private/OpenIPMI-1.4.14-1.4E.17a.src.rpm Fantastic - thanks for your explanation and the SRPM James. For the record, James appears to be completely correct and his SRPM fixes my problems here on CentOS 4.5 - woohoo! His patch also applies cleanly to the current CentOS 5 package and fixes the problem there as well - a patched SRPM is available here for anyone else experiencing the problem: http://www.openfusion.com.au/labs/dist/OpenIPMI-2.0.6-5.of.el5.3a.src.rpm (and binary packages are in http://www.openfusion.com.au/mrepo/). I've also reported the problem upstream: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245677 Cheers, Gavin ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ipmi regression in 4.5?
Gavin Carr wrote: On Thu, Jun 21, 2007 at 10:13:56AM +0100, James Pearson wrote: Gavin Carr wrote: I've been monitoring CPU temperature on a few Dell SC1435s running CentOS4 via OpenIPMI and 'ipmitool sdr'. It's been working very nicely, but the upgrade to 4.5 not so long ago seems to have broken something: # ipmitool sdr type Temperature Temp | 01h | ns | 3.1 | Disabled Planar Temp | 04h | ok | 7.1 | 30 degrees C Temp Interface | 53h | ns | 7.1 | Disabled The disabled sensors above used to work fine, and there have been no config changes or bios upgrades or anything. All machines affected post 4.5. I had a similar problem with Dell boxes when I went from ipmitool v1.8.8 to v1.8.9 - see the thread starting at: http://www.mail-archive.com/[EMAIL PROTECTED]/msg00468.html It looks like the patch for ipmitool in the CentOS 4.5 OpenIPMI SRPM i.e. ipmitool-1.8.8-disabled-sensor.patch is the cause of this issue ... the comment is the change log is: - Added patch to fix sensors problems on Woodcrest (#228679) I guess you could rebuild the OpenIPMI without that patch Thanks for the input James. That does seem a similar problem, but it's specific to those Intel chipsets, but the looks. The SC1435s we're I'm seeing the problem are AMDs. Another interesting datapoint I've discovered is that the versions of OpenIPMI only changed at the release level: CentOS 4.4: 1.4.14-1.4E.13 CentOS 4.5: 1.4.14-1.4E.17 so I'm starting to wonder if it's perhaps a kernel change. In addition, I've now verified that the sensors are behaving similarly on CentOS 5. The ipmitool-1.8.8-disabled-sensor.patch may well be to fix Woodcrest specific issues - but it also removes part of the code that affects temperature readings on (some?) Dells ... I'm not an expert on IPMI, but the code that patch did remove, looks a bit hacky (may be that is why it was removed?) - however, one side effect of this is to prevent some temperature reading on SC1435s and may be other Dell hardware. I have no idea if the 'real' issue is with ipmitool or the Dell hardware. However, if you rebuild OpenIPMI without that patch, then ipmitool will work as before when reading temperatures on SC1435s It is not a kernel issue - you get the same problem using ipmitool talking over the lanplus interface (which goes nowhere near the kernel). The simple work around is to use ipmitool from the CentOS 4.4 RPM (as the only change to ipmitool between 4.4 and 4.5 were the Woodcrest fixes). I have created an updated SRPM which reverses that part of the Woodcrest fixes that affect these Dells - if you are interested, the SRPM is at: ftp://ftp.moving-picture.com/private/OpenIPMI-1.4.14-1.4E.17a.src.rpm I haven't use CentOS 5 in anger (yet), but I guess the issue is the same. James Pearson ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ipmi regression in 4.5?
Gavin Carr wrote: I've been monitoring CPU temperature on a few Dell SC1435s running CentOS4 via OpenIPMI and 'ipmitool sdr'. It's been working very nicely, but the upgrade to 4.5 not so long ago seems to have broken something: # ipmitool sdr type Temperature Temp | 01h | ns | 3.1 | Disabled Planar Temp | 04h | ok | 7.1 | 30 degrees C Temp Interface | 53h | ns | 7.1 | Disabled The disabled sensors above used to work fine, and there have been no config changes or bios upgrades or anything. All machines affected post 4.5. I had a similar problem with Dell boxes when I went from ipmitool v1.8.8 to v1.8.9 - see the thread starting at: http://www.mail-archive.com/[EMAIL PROTECTED]/msg00468.html It looks like the patch for ipmitool in the CentOS 4.5 OpenIPMI SRPM i.e. ipmitool-1.8.8-disabled-sensor.patch is the cause of this issue ... the comment is the change log is: - Added patch to fix sensors problems on Woodcrest (#228679) I guess you could rebuild the OpenIPMI without that patch James Pearson ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ipmi regression in 4.5?
On Thu, Jun 21, 2007 at 10:13:56AM +0100, James Pearson wrote: Gavin Carr wrote: I've been monitoring CPU temperature on a few Dell SC1435s running CentOS4 via OpenIPMI and 'ipmitool sdr'. It's been working very nicely, but the upgrade to 4.5 not so long ago seems to have broken something: # ipmitool sdr type Temperature Temp | 01h | ns | 3.1 | Disabled Planar Temp | 04h | ok | 7.1 | 30 degrees C Temp Interface | 53h | ns | 7.1 | Disabled The disabled sensors above used to work fine, and there have been no config changes or bios upgrades or anything. All machines affected post 4.5. I had a similar problem with Dell boxes when I went from ipmitool v1.8.8 to v1.8.9 - see the thread starting at: http://www.mail-archive.com/[EMAIL PROTECTED]/msg00468.html It looks like the patch for ipmitool in the CentOS 4.5 OpenIPMI SRPM i.e. ipmitool-1.8.8-disabled-sensor.patch is the cause of this issue ... the comment is the change log is: - Added patch to fix sensors problems on Woodcrest (#228679) I guess you could rebuild the OpenIPMI without that patch Thanks for the input James. That does seem a similar problem, but it's specific to those Intel chipsets, but the looks. The SC1435s we're I'm seeing the problem are AMDs. Another interesting datapoint I've discovered is that the versions of OpenIPMI only changed at the release level: CentOS 4.4: 1.4.14-1.4E.13 CentOS 4.5: 1.4.14-1.4E.17 so I'm starting to wonder if it's perhaps a kernel change. In addition, I've now verified that the sensors are behaving similarly on CentOS 5. Any other suggestions? Cheers, Gavin ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] ipmi regression in 4.5?
I've been monitoring CPU temperature on a few Dell SC1435s running CentOS4 via OpenIPMI and 'ipmitool sdr'. It's been working very nicely, but the upgrade to 4.5 not so long ago seems to have broken something: # ipmitool sdr type Temperature Temp | 01h | ns | 3.1 | Disabled Planar Temp | 04h | ok | 7.1 | 30 degrees C Temp Interface | 53h | ns | 7.1 | Disabled The disabled sensors above used to work fine, and there have been no config changes or bios upgrades or anything. All machines affected post 4.5. Any suggestions? Cheers, Gavin ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos