Date: Wed, 19 Nov 2014 11:41:10 -0500 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Andreas Nilsson <andrnils@gmail.com> Cc: Daniel O'Connor <doconnor@gsoft.com.au>, FreeBSD Stable Mailing List <freebsd-stable@freebsd.org>, Dmitry Morozovsky <marck@rinet.ru>, John Baldwin <jhb@freebsd.org> Subject: Re: SuperMicro IPMI/SOL and ipmitool troubles Message-ID: <9CC9B190-9645-4AE3-B3CF-3C38386D1601@gromit.dlib.vt.edu> In-Reply-To: <CAPS9%2BSuCLE9kVPA-RNMHfziJYXAL1ivkV-B8wa64athYdDb38A@mail.gmail.com> References: <alpine.BSF.2.00.1411112022500.25949@woozle.rinet.ru> <3C955A8F-9D1A-463B-BB9A-256C36BF0D4C@gromit.dlib.vt.edu> <alpine.BSF.2.00.1411112226450.25949@woozle.rinet.ru> <CAPS9%2BSuvWq1vtBw8K3J5NRs30272MV7EgkFMT57A=FspeZvCbQ@mail.gmail.com> <CAPS9%2BSv4kNjR=69kWEf8zhAXGBpRYmULZm8AnFxSscBiw2wwiw@mail.gmail.com> <CAPS9%2BSu970ukYwbYcfzrrC=hMnT61CQzYRd-6RaoLiW42BK4Dw@mail.gmail.com> <alpine.BSF.2.00.1411120417590.25949@woozle.rinet.ru> <CAPS9%2BStJU-_vTKNd54C6R91rs=5Lr5gM9PGu-hCrRpZb0pjEFg@mail.gmail.com> <D912F65F-70A1-492A-B0F2-84D62AFEA7BC@gsoft.com.au> <alpine.BSF.2.00.1411142127550.2113@woozle.rinet.ru> <CAPS9%2BSujGtrQ%2Bw=5jCBqV1vv_ZFZ5qkhjfGQUwc5n0sfjPCvnQ@mail.gmail.com> <CAPS9%2BSuCLE9kVPA-RNMHfziJYXAL1ivkV-B8wa64athYdDb38A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 19, 2014, at 11:02 AM, Andreas Nilsson <andrnils@gmail.com> = wrote: > On Wed, Nov 19, 2014 at 3:28 PM, Andreas Nilsson <andrnils@gmail.com> = wrote: >=20 >>=20 >>=20 >> On Fri, Nov 14, 2014 at 7:30 PM, Dmitry Morozovsky <marck@rinet.ru> = wrote: >>=20 >>> Daniel, >>>=20 >>> nice to see you here too ;) >>>=20 >>> On Fri, 14 Nov 2014, Daniel O'Connor wrote: >>>=20 >>>>=20 >>>> On 12 Nov 2014, at 19:43, Andreas Nilsson <andrnils@gmail.com> = wrote: >>>>> unclear is the word for it :) And thanks for looking into this. >>> ipmi/ilo is >>>>> important on a server os. >>>>>=20 >>>>> I found a reference to it in a ML post: >>>>>=20 >>> = http://lists.freebsd.org/pipermail/freebsd-stable/2013-February/072464.htm= l >>>>=20 >>>> I started that thread :) >>>> I did get it working on the hardware I was using (Supermicro = X9SCL-F >>> and X8SIL-F) >>>>=20 >>>> 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 >>>>=20 >>>> And the following in loader.conf >>>> # Give preference to VGA console >>>> console=3D"vidconsole,comconsole" >>>> # Uncomment below and comment above to give serial console = preference >>>> #console=3D"comconsole,vidconsole" >>>> comconsole_speed=3D"115200" >>>> boot_multicons=3D"YES" >>>> hint.uart.0.flags=3D"0x0" >>>> hint.uart.2.at=3D"isa" >>>> hint.uart.2.port=3D"0x3E8" >>>> hint.uart.2.flags=3D"0x30" >>>>=20 >>>> 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 >>>>=20 >>>> I could then access it using ipmitool like so >>>> ipmitool -H remoteip -U ADMIN -I lanplus sol activate >>>> [login] >>>> export TERM=3Dxterm >>>>=20 >>>> 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=3Dcomconsole,vidconsole? and then get = everything over >>> the serial console for remote trouble shooting. >>>>=20 >>>> 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. >>>=20 >>> Well, I'm almost done with most of our SM server, even concentrated >>> console on >>> our console server with such a simple config: >>>=20 >>> ---- 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 %=3Dcs; >>> #idletimeout 6h; >>>=20 >>> break 0 { string "~B"; } >>> } >>>=20 >>> 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; } >>>=20 >>> console gwc2 { include ipmi; } >>> ---- 8< ---- >>>=20 >>> This has console logging (including possible panics) as a surplus >>>=20 >>> -- >>> Sincerely, >>> D.Marck [DM5020, MCK-RIPE, = DM3-RIPN] >>> [ FreeBSD committer: = marck@FreeBSD.org ] >>> = ------------------------------------------------------------------------ >>> *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru = *** >>> = ------------------------------------------------------------------------ >>>=20 >>=20 >> Hello again, >>=20 >> Searching on hw.uart.console, I found: >> = http://lists.freebsd.org/pipermail/svn-src-head/2013-February/044641.html >> , a very enlightening thread. >>=20 >> 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. >>=20 >> 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. >>=20 >> Best regards >> Andreas >>=20 >>=20 >>=20 > More fun stuff: > On the supermicro machine it is not working to use comconsole_port, as = it > seems to switch, "redirect after boot" I guess. >=20 > Specifying hw.uart.console=3D"br:9600" works though, but how to = specify that > via comconsole_port? (hint, do not put comconsole_port=3D"" in = loader.conf) In my experience it can be confusing to determine which COM port the = server is actually using for SOL. On multiple different Supermicro = servers, I've found the BIOS differs as to how SOL is set up. OFten, = you can't explicitly assign the COM port in the SOL setup. I've also = found it rare that the BIOS is explicit as to which COM port is being = used for SOL. I've had servers that use COM1, others that use COM2, and = others that use COM3. That makes setting comconsole_port somewhat a = process of trial and error, at least that's what I've found... Cheers, Paul.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9CC9B190-9645-4AE3-B3CF-3C38386D1601>