From owner-freebsd-stable@FreeBSD.ORG Tue Mar 6 00:07:40 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7A78916A401 for ; Tue, 6 Mar 2007 00:07:40 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from alnrmhc11.comcast.net (alnrmhc11.comcast.net [204.127.225.91]) by mx1.freebsd.org (Postfix) with ESMTP id 5403E13C471 for ; Tue, 6 Mar 2007 00:07:40 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-71-198-0-135.hsd1.ca.comcast.net[71.198.0.135]) by comcast.net (alnrmhc11) with ESMTP id <20070305235547b1100a5feke>; Mon, 5 Mar 2007 23:55:47 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E33E81FA03D; Mon, 5 Mar 2007 15:55:35 -0800 (PST) Date: Mon, 5 Mar 2007 15:55:35 -0800 From: Jeremy Chadwick To: Artem Kuchin Message-ID: <20070305235535.GA23583@icarus.home.lan> Mail-Followup-To: Artem Kuchin , stable@freebsd.org References: <20070305193022.GM10453@deviant.kiev.zoral.com.ua> <000b01c75f6b$594c23d0$0c00a8c0@Artem> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000b01c75f6b$594c23d0$0c00a8c0@Artem> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: stable@freebsd.org Subject: Re: Boot prompt for Intel AMT X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2007 00:07:40 -0000 On Tue, Mar 06, 2007 at 12:15:04AM +0300, Artem Kuchin wrote: > The othe question, is there such technology for Supermicro mainboards? Yes, Supermicro makes IPMI add-on cards (they require IPMI capability on the mainboard, however). Be warned about these cards, however. A friend of mine at Yahoo! has encountered a major BIOS/IPMI oversight, where in the case that the IPMI event log becomes full, the system BIOS upon boot will _require_ someone hit F1 to continue on the console, until the IPMI history is cleared. Ultimately this requires someone to go to the datacenter and manually hit F1 on the console, clear the IPMI log, and let the machine boot up. Wonderful oversight. Yes, there are IPMI management utilities for some OSes, but many of them are closed-source, only work on certain versions of the OS, or for the open-source ones do not let you control/monitor as much as you would under the native utility from the vendor. Now it seems more and more problems are coming to light with vendor IPMI implementations (Broadcom's pseudo-iLO causes ARP storms because there is no dedicated NIC for iLO and the NIC technically has two MAC addresses, Supermicro's IPMI and the event log problem, yadda yadda.) Seems to me the only vendors who got this right were 1) HP/Compaq with their true iLO/iLO2, and 2) Sun. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |