From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 19:21:18 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 06FEFE35 for ; Wed, 19 Nov 2014 19:21:18 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D10D7780 for ; Wed, 19 Nov 2014 19:21:17 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A25EFB93E; Wed, 19 Nov 2014 14:21:16 -0500 (EST) From: John Baldwin To: Andreas Nilsson Subject: Re: SuperMicro IPMI/SOL and ipmitool troubles Date: Wed, 19 Nov 2014 14:05:16 -0500 Message-ID: <3870083.h75yLjv6As@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-PRERELEASE; KDE/4.14.2; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 19 Nov 2014 14:21:16 -0500 (EST) Cc: Daniel O'Connor , FreeBSD Stable Mailing List , Dmitry Morozovsky X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2014 19:21:18 -0000 On Wednesday, November 19, 2014 05:02:49 PM Andreas Nilsson wrote: > On Wed, Nov 19, 2014 at 3:28 PM, Andreas Nilsson wrote: > > On Fri, Nov 14, 2014 at 7:30 PM, Dmitry Morozovsky wrote: > >> Daniel, > >> > >> nice to see you here too ;) > >> > >> On Fri, 14 Nov 2014, Daniel O'Connor wrote: > >> > On 12 Nov 2014, at 19:43, Andreas Nilsson wrote: > >> > > unclear is the word for it :) And thanks for looking into this. > >> > >> ipmi/ilo is > >> > >> > > important on a server os. > >> > >> > > I found a reference to it in a ML post: > >> http://lists.freebsd.org/pipermail/freebsd-stable/2013-February/072464.ht > >> ml > >> > >> > I started that thread :) > >> > I did get it working on the hardware I was using (Supermicro X9SCL-F > >> > >> and X8SIL-F) > >> > >> > I used the following BIOS settings > >> > > >> > ? Remote Access - Enabled > >> > ? Serial Port Number - COM3 > >> > ? Serial Port Mode - 115200, 8, n, 1 > >> > ? Flow Control - Hardware > >> > ? Redirection After BIOS POST - Always > >> > ? Terminal Type - VT100 > >> > ? VT-UTF8 Combo Key Support - Disabled > >> > ? Sredir Memory Display Delay - No Delay > >> > > >> > And the following in loader.conf > >> > # Give preference to VGA console > >> > console="vidconsole,comconsole" > >> > # Uncomment below and comment above to give serial console preference > >> > #console="comconsole,vidconsole" > >> > comconsole_speed="115200" > >> > boot_multicons="YES" > >> > hint.uart.0.flags="0x0" > >> > hint.uart.2.at="isa" > >> > hint.uart.2.port="0x3E8" > >> > hint.uart.2.flags="0x30" > >> > > >> > And this in /etc/ttys > >> > # IPMI console > >> > # Note: The Java console viewer doesn't seem to be very smart as it > >> > >> doesn't > >> > >> > # properly support VT100 > >> > cuau2 "/usr/libexec/getty 3wire.115200" vt100 on secure > >> > > >> > I could then access it using ipmitool like so > >> > ipmitool -H remoteip -U ADMIN -I lanplus sol activate > >> > [login] > >> > export TERM=xterm > >> > > >> > Note that I wanted vidconsole by default because mostly the systems > >> > >> were used by people local to them, however we could break into the loader > >> and type 'set console=comconsole,vidconsole? and then get everything over > >> the serial console for remote trouble shooting. > >> > >> > You may also wish to check the IPMI configuration via the web interface > >> > >> - by default it will failover to port 0 and it has terrible default > >> passwords. I changed the passwords and forced it to use the dedicated > >> IPMI > >> port even if nothing was connected to it. > >> > >> Well, I'm almost done with most of our SM server, even concentrated > >> console on > >> our console server with such a simple config: > >> > >> ---- 8< ---- > >> # ipmi/sol console template > >> default ipmi { > >> > >> master localhost; > >> type exec; > >> exec /usr/local/bin/ipmitool -f /usr/local/etc/ipmi-pass -U > >> > >> root -I lanplus -H %.int sol activate; > >> > >> execsubst %=cs; > >> #idletimeout 6h; > >> > >> break 0 { string "~B"; } > >> > >> } > >> > >> console gwn1 { include ipmi; } > >> console gwn2 { include ipmi; } > >> console gwn3 { include ipmi; } > >> console gwn4 { include ipmi; } > >> console gwn5 { include ipmi; } > >> console gwn6 { include ipmi; } > >> console gwn7 { include ipmi; } > >> console gwn8 { include ipmi; } > >> > >> console gwc2 { include ipmi; } > >> ---- 8< ---- > >> > >> This has console logging (including possible panics) as a surplus > >> > >> -- > >> Sincerely, > >> D.Marck [DM5020, MCK-RIPE, DM3-RIPN] > >> [ FreeBSD committer: marck@FreeBSD.org ] > >> ------------------------------------------------------------------------ > >> *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** > >> ------------------------------------------------------------------------ > > > > Hello again, > > > > Searching on hw.uart.console, I found: > > http://lists.freebsd.org/pipermail/svn-src-head/2013-February/044641.html > > , a very enlightening thread. > > > > Basically: "ohh, you want to use something other than COM1 and tried to > > get away with just changing hint.uart stuff, which has worked for a while, > > ha, no way..." No heads up, nothing. > > > > Sorry to say jhb@ but is not a rare case. It is if not the default, a > > very common setup on every HP server with iLO, and it holds for most all > > OOB style serial emulation I have ever had the (dis)pleasure of working > > with. This was done _specifically_ so you could use non-COM1 for both loader and kernel with one thing to change. That is, you don't use hint.uart.X.flags after this. I have used this with many SuperMicro servers that use COM2 and COM3 because I wanted the entire path (boot loader and kernel) to work, not the kernel only. Having only the kernel means I can't break into the loader prompt to boot a different kernel, single user, etc. To clarify, are you using _different_ serial ports for the loader vs the kernel? That is the use case I considered to be rare. Every single server I have ever worked with (though not iLO, mostly Dell and SuperMicro) uses the same COM port for serial redirection rather for SOL or via actual cables. I've yet to use a system that, for example, used COM1 for the loader and COM2 for the kernel. You are saying that every HP server uses COM1 for the loader and COM2 for the kernel? -- John Baldwin