freeipmi-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Freeipmi-users] "Connection timed out" error


From: Davidson Mike
Subject: [Freeipmi-users] "Connection timed out" error
Date: Tue, 22 May 2007 21:14:40 -0400

I'm a newbie to the world of IPMI and remote management and am trying to evaluate FreeIPMI vs ipmitool. I've downloaded, built and installed FreeIPMI v0.3.3 and ipmitool v1.8.9 on a Fedora Core 5 linux box. I've been able to successfully query an HP Proliant DL 145 server (which supports IPMI 2.0) for a variety of information over the server's BMC LAN interface using ipmitool. However, when using the FreeIPMI tools (such as ipmi-sensors) I keep getting the following error:

$ sudo ipmi-sensors -D lan -h 192.168.43.133 -u admin -p admin
ipmi_open_outofband(): Connection timed out

I've tried using the '-vv' verbose option but I'm not seeing anything useful.

Just for comparison, here's the result when I use ipmitool:

$ ipmitool -I lanplus -H 192.168.43.133 -U admin -P admin sensor
ACPI STATE | 0x0 | discrete | 0x0100| na | na | na | na | na | na CPU0 Pres | 0x1 | discrete | 0x0200| na | na | na | na | na | na CPU1 Pres | 0x0 | discrete | 0x0100| na | na | na | na | na | na CPU0 TEMP | 35.000 | degrees C | ok | na | 10.000 | na | 66.000 | 68.000 | na CPU1 TEMP | na | degrees C | na | na | 10.000 | na | 66.000 | 68.000 | na SYS TEMP | 23.000 | degrees C | ok | na | 10.000 | na | 43.000 | 45.000 | na CPU FAN1 | 6000.000 | RPM | ok | na | 3500.000 | 4000.000 | na | na | na CPU FAN2 | 6000.000 | RPM | ok | na | 3500.000 | 4000.000 | na | na | na CPU FAN3 | 6000.000 | RPM | ok | na | 3500.000 | 4000.000 | na | na | na
....


Not sure what I'm doing wrong...I've been through the man pages for the various FreeIPMI utilities and nothing is jumping out at me. If anyone can shed any light on what to try next I'd very much appreciate it.

Btw, the 'ipmipower', 'ipmiping' and 'rmcpping' utilities all work...I'm able to remotely power the machine on and off. So I'm guessing this might be some kind of configuration/authentication issue since only the commands that don't require credentials appear to work. May just be a conincidence.

Thanks in advance.

Mike




reply via email to

[Prev in Thread] Current Thread [Next in Thread]