From owner-freebsd-stable@FreeBSD.ORG Tue Jan 22 17:16:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E5CDE90B; Tue, 22 Jan 2013 17:16:49 +0000 (UTC) (envelope-from sodynet1@gmail.com) Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) by mx1.freebsd.org (Postfix) with ESMTP id A34FC715; Tue, 22 Jan 2013 17:16:49 +0000 (UTC) Received: by mail-ie0-f175.google.com with SMTP id qd14so11819204ieb.6 for ; Tue, 22 Jan 2013 09:16:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=aSyed+y1c4mVcrZvvftQaRGopwBXw/6drdgqXoETXbY=; b=0vZXbgTnJkacr6yQVLS4mjMPTnG5l9Ox+MYvT+GWcATb/2u+OUh73bHYp3/0SjMMJ9 rxhAtCA3oZP2jgPt5+yxkFvC/GpdT1hBW52QsPhjuNB8bJ7AvQ0lOcdPkGTLt4ol1kxb J74bf1QFqtNWND+4Sys38ac0KF3L7S1Sg24IAYUL4vPmQs3aQaxtIpcO92IvEq6jXMtM luEWDrNIg/XdAeZxnTbPcCj7n5JMAn7JqvZkV7E6qNqdeSwcbDOTxTHUG88vz6Jxegfm 9MAZilV4U8QMuRn4964M7Uk+oDO4uIPeLhFz0xdHWYLS5bXVUqZFJrCmT7Byz6+wLb3C YMkw== MIME-Version: 1.0 X-Received: by 10.50.222.226 with SMTP id qp2mr12745969igc.103.1358875009202; Tue, 22 Jan 2013 09:16:49 -0800 (PST) Received: by 10.64.51.98 with HTTP; Tue, 22 Jan 2013 09:16:48 -0800 (PST) Received: by 10.64.51.98 with HTTP; Tue, 22 Jan 2013 09:16:48 -0800 (PST) In-Reply-To: <50FBFA2C.2010504@digiware.nl> References: <201301161513.27016.jhb@freebsd.org> <1358392725.32417.179.camel@revolution.hippie.lan> <50FBFA2C.2010504@digiware.nl> Date: Tue, 22 Jan 2013 19:16:48 +0200 Message-ID: Subject: Re: Failsafe on kernel panic From: Sami Halabi To: Willem Jan Withagen Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org, Ian Lepore X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 22 Jan 2013 17:16:50 -0000 I started investigating ipmi, so far i can configure IP from fbsd to ipmi. My question is how to access it? Can it be done inband attached to one oc the Ibm nics kn the board? or knlh out oc band? In case of oob any knows if the iLO plug is pure rj45 in ibm servers (specially x3250/3550)? Thanks in advance Sami =D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A 20 =D7=91=D7=99=D7=A0=D7=95 2013 16:0= 7, =D7=9E=D7=90=D7=AA "Willem Jan Withagen" : > On 17-1-2013 4:18, Ian Lepore wrote: > > On Wed, 2013-01-16 at 23:27 +0200, Sami Halabi wrote: > >> Thank you for your response, very helpful. > >> one question - how do i configure auto-reboot once kernel panic occurs= ? > >> > >> Sami > >> > > > > From src/sys/conf/NOTES, this may be what you're looking for... > > > > # > > # Don't enter the debugger for a panic. Intended for unattended operati= on > > # where you may want to enter the debugger from the console, but still > want > > # the machine to recover from a panic. > > # > > options KDB_UNATTENDED > > > > But I think it only has meaning if you have option KDB in effect, > > otherwise it should just reboot itself after a 15 second pause. > > Well it is not the magical fix-all solution. > > Last night I had to drive to the colo (lucky for me a 5 min drive.) > because I could not get a system to reboot/recover from a crash. > > Upon arrival the system was crashed and halted on the message: > rebooting in 15 sec. > > Which but those 15 secs are would have gone by for about 10-20 minutes. > fysically rebooting or resetting ended up in the same position: > rebooting in 15 sec. > Without ever getting to actually rebooting. > > So if I (you) have servers 2 hours away, I usually try to work on > upgrading/rebooting during business hours. And remote hands can get me > out of trouble.... > > IPMI is another nice way of getting at the server in these cases. But > that requires a lot more infra and tinkering. > > --WjW > > > >