From owner-freebsd-proliant@FreeBSD.ORG Fri Jul 14 07:50:33 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B80BA16A4DD for ; Fri, 14 Jul 2006 07:50:33 +0000 (UTC) (envelope-from elakin@infohell.net) Received: from ra.infohell.net (ra.infohell.net [207.234.145.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F4C543D55 for ; Fri, 14 Jul 2006 07:50:32 +0000 (GMT) (envelope-from elakin@infohell.net) Received: from isis.infohell.net (c-67-168-25-26.hsd1.wa.comcast.net [67.168.25.26]) by ra.infohell.net (8.13.1/8.13.1) with ESMTP id k6E7oUnR000508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 14 Jul 2006 00:50:31 -0700 Received: by isis.infohell.net (Postfix, from userid 501) id E664039AF0F; Fri, 14 Jul 2006 00:50:25 -0700 (PDT) Date: Fri, 14 Jul 2006 00:50:25 -0700 From: Eric Lakin To: freebsd-proliant@freebsd.org Message-ID: <20060714075025.GC13818@isis.infohell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Disclaimer: Yow! I said THAT?!? Subject: FreeBSD deactivates Shared-network iLo X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: elakin@infohell.net List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 07:50:33 -0000 Greetings all, I'm trying to setup the iLo on a DL360 G4 running FreeBSD 6.1. I'd like to use the "Shared-network" option, which allows the iLo to be accessible over the hosts primary NIC rather than a dedicated NIC. Unfortunately, just after the kernel starts loading, the iLo stops responding - to pings, ssh. FreeBSD continues to boot normally. As soon as FreeBSD is shutdown (shutdown -p), the iLo immediately begins responding again to pings & ssh. I've also loaded a test instance of Linux on this server, and running Linux doesn't seem to adversely affect the shared-network iLo. Any ideas what's causing the shared-net iLo to freeze up, and what can be done (short of running linux or using the dedicated iLo network port) to fix this behaviour? -- You are in a maze of twisty little email threads, all alike [ elakin@infohell.net | elakin@comcast.net ] ## set vi:nowrap tw=72