From owner-freebsd-questions@FreeBSD.ORG Wed May 17 12:40:16 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4BAE16A42F for ; Wed, 17 May 2006 12:40:16 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 411D343D46 for ; Wed, 17 May 2006 12:40:16 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from vanquish.pgh.priv.collaborativefusion.com (vanquish.pgh.priv.collaborativefusion.com [192.168.2.61]) (AUTH: PLAIN wmoran, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Wed, 17 May 2006 08:40:15 -0400 id 00056405.446B19AF.0000C202 Date: Wed, 17 May 2006 08:40:14 -0400 From: Bill Moran To: Jason Lixfeld Message-Id: <20060517084014.2ae43ecf.wmoran@collaborativefusion.com> In-Reply-To: References: <4F6E19E5-CB85-40E8-8E00-42EDCD9483F2@lixfeld.ca> <20060516130121.1660ab5d.wmoran@collaborativefusion.com> Organization: Collaborative Fusion X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.17; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Questions about monitoring Dell servers X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 May 2006 12:40:21 -0000 On Tue, 16 May 2006 19:15:06 -0400 Jason Lixfeld wrote: > > On 16-May-06, at 1:01 PM, Bill Moran wrote: > > > DRAC is irrelevant to FreeBSD. Configure it in the BIOS (give it an > > IP and the like) and you can use a web browser to get a console > > window. > > (True console, so that you can access the BIOS during boot and > > everything). > > I can configure an IP address on the BMC, but that's obviously > different than the DRAC. Before, when I tried to configure an IP on > the BMC, I couldn't see any IP info for it at all in the system. > Couldn't ping it, couldn't see a mac address for it, nothing so I > wasn't sure if the BMC networking portion would work without the DRAC > or not. BMC == IPMI, correct? IPMI and DRAC are separate and independent. I don't think you can use the same IP address for both, although I've never tried. I don't think Dell's BMC responds to pings, but I could be wrong. If, by saying "in the system" you mean that you're checking ifconfig, then you're not _going_ to see it there, as the hardware handles it and FreeBSD is unaware that it's going on. > > Install ipmitool and use it to access IPMI over the network. > > I tried that too, but based on above, I couldn't get the BMC to be > seen on the network. Sounds like a more Dell-specific issue to me. Work within their framework (I think they have Windows-based tools) until you can contact IPMI via the network, then I'm betting you'll be able to contact it with ipmitool. > > We have a central machine that monitors all our servers via a Nagios > > plugin to ipmitool. I can't offer any advice on getting OpenIPMI > > working. > > Is there a particular benefit to OpenIPMI vs. FreeIPMI? I have no idea. We don't use either. > I'm still a little fuzzy on the IP capabilities of IPMI vs DRAC. There really is no "vs.". Both IPMI and DRAC are accessible over an IP network. During the BIOS boot, you'll have menus available for configuring both. You can enable one, the other, or both, or neither. They are two different technologies intended to serve two different purposes, but there is some overlap in their capabilities. DRAC provides a web interface for monitoring and control. DRAC includes a console over IP feature that is probably its greatest strength. IPMI is it's own protocol, thus anyone with an itching can write a client to access the IPMI data or send IPMI commands. IPMI doesn't have console capability. Both allow monitoring of hardware sensors. -- Bill Moran Collaborative Fusion Inc.