similar to: LSI driver and SSD status error in IPMI

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

Hi, I am getting the following error on server Cisco UCS C200 M2 running FreeBSD 8.3 amd64 Oct 31 02:15:22 ucs200 kernel: ACPI Error: No handler for Region [POWS] (0xffffff000994f380) [IPMI] (20101013/evregion-487) Oct 31 02:15:22 ucs200 kernel: ACPI Error: Region IPMI(0x7) has no handler (20101013/exfldio-382) Oct 31 02:15:22 ucs200 kernel: ACPI Error: Method parse/execution failed

Hi folks, We experiencing some difficulties in getting IPMI to work on RHEL 6 running as Guest using KVM. We have verified that IPMI works on RHEL 6 if installed on bare metal. Is this a known issue? Can anyone please suggest a fix or work-around for this problem? *RHEL 6 as guest os with kvm on RHEL 6 as host os -- doesn't work* RHEL 6 (client) on bare metal (i.e., the above mentioned host

On 11/11/2013 05:38 PM, Andrew J. Schorr wrote: > Hi, > > I hope somebody can help me with this problem. I don't know whether > it's a problem with my configuration or a bug or feature in extlinux. > I am using an IPMI 2.0 serial-over-lan console to connect to a system > with an Intel S3200SHL motherboard. The first line of my extlinux.conf > file looks like this:

On 11/12/2013 01:22 PM, Andrew J. Schorr wrote: > Hi, > > Thanks for your help. > > On Mon, Nov 11, 2013 at 08:00:47PM -0800, H. Peter Anvin wrote: >> There is no reason by Syslinux would reboot the system on a serial >> disconnect. There could be a bug, of course; now, Syslinux 4.05 is >> pretty old so unless you can reproduce this on a current version that

On Tue, Nov 12, 2013 at 5:20 PM, Andrew J. Schorr <aschorr at telemetry-investments.com> wrote: > Hi, > > On Tue, Nov 12, 2013 at 01:41:29PM -0800, H. Peter Anvin wrote: >> On 11/12/2013 01:22 PM, Andrew J. Schorr wrote: >> > I am using 4.05 because that's what's packaged in the latest Fedora >> > release (Fedora 19 in my case). I wonder why they are

On 11/14/2013 03:39 AM, Gene Cumm wrote: > On Tue, Nov 12, 2013 at 5:20 PM, Andrew J. Schorr > <aschorr at telemetry-investments.com> wrote: >> Hi, >> >> On Tue, Nov 12, 2013 at 01:41:29PM -0800, H. Peter Anvin wrote: >>> On 11/12/2013 01:22 PM, Andrew J. Schorr wrote: >>>> I am using 4.05 because that's what's packaged in the latest

I have this happening in Ubuntu precise also. When I upgraded from 12.04.1 to 12.04.4 it looks like my ipmi/serial/hvc0 console stopped working and the last message is: (XEN) Platform timer is 14.318MHz HPET From /etc/default/grub: GRUB_DEFAULT="Xen 4.1-amd64" GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo

Control: tag -1 moreinfo ISTR various supermicro fixes as well as serial stuff etc over the last few years. Please could you test with the Xen 4.4 currenty in Jessie? Ian.

Hi all, I am implementing two node cluster , but the hardware they given me contains only the Base Board Management controller (BMC) . Also I HEARD SOME BMC wont support power fencing, how can i check my There is no management port like HP ILO or Dell DRAC for cluster fencing . This hardware belongs to the vendor HCL. For BMC Configuration they are providing the exe setup file for windows to

Hi all, I've got a Portwell NANO-6060 board I am testing out for potential use in a project of ours. One of the nice features of this board, beyond nice NICs, is that it has a hardware watchdog timer. The problem is that I don't get a /dev/watchdog device file. I know the hardware works, because when I enable it in BIOS, the box will reboot after the timer expires. However,

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

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

On 2016-09-17, Alice Wonder <alice at domblogger.net> wrote: > > 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.

On 2016-09-18, Boris Epstein <borepstein at gmail.com> wrote: > 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 -- kkeller at

On 2016-09-18, Alice Wonder <alice at domblogger.net> wrote: > > 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

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

Once upon a time, mark <m.roth at 5-cent.us> said: > This is that system with the missing management port, and I'm still > fighting it. Everything *looks* right: > > 3: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UP group default qlen 1000 > link/ether 00:25:90:0a:42:87 brd ff:ff:ff:ff:ff:ff > inet 192.168.0.100/24 brd

Hallo, this happens using freeipmi here on Centos 7 [root at srvdockerndxx etc]# ipmi-sensors Caching SDR repository information: /root/.freeipmi/sdr-cache/sdr-cache-srvdockerndxx.localhost ipmi_sdr_cache_create: internal IPMI error [root at srvdockerndxx etc]# The problem: It is my first try to use freeipmi. The goal is to use it with check-mk to monitor the system. Has anyone a good

On Sat, Sep 17, 2016 at 6:25 AM, Alice Wonder <alice at domblogger.net> wrote: > 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