Date: Wed, 2 Mar 2011 16:10:09 -0800 From: Nerius Landys <nlandys@gmail.com> To: Maxim Khitrov <max@mxcrypt.com> Cc: David Brodbeck <gull@gull.us>, freebsd-questions@freebsd.org Subject: Re: Finish upgrading remote server without physically being there? Message-ID: <AANLkTimFGN72u1NVc74=c0DS-eNQHj-iSCAKFz51rZGj@mail.gmail.com> In-Reply-To: <AANLkTikj7-wXv3vErm6oOOXvPZEPCaqVEjnHWfycin7z@mail.gmail.com> References: <AANLkTin39JjTsts2WwgDUV2QfZL745D0P3DqTkko8TFq@mail.gmail.com> <4D6E6B16.7010508@my.gd> <AANLkTin7sHXsLwBBUmHinDaB3FLOH25_CDy4v82gKFjw@mail.gmail.com> <AANLkTikq1-CKnwHRahTE%2BTa5KLP=8qpUG8WzBrpP=d8n@mail.gmail.com> <AANLkTikFNnV-V82Ucncy_cM0VwiNif6r8DHB9DfMDNvC@mail.gmail.com> <AANLkTi=5YXqgyy_%2BSMdYof3Y3neaatoC7C0sb-tdhxkX@mail.gmail.com> <AANLkTikj7-wXv3vErm6oOOXvPZEPCaqVEjnHWfycin7z@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I just got a new Supermicro Atom board a few days ago (X7SPA-HF-D525). > It has a Nuvoton BMC chip that is attached to LAN1 and provides IPMI > and KVM-over-IP functionality. The chip gets its own IP address > (separate from em0 in FreeBSD) and is powered whenever the power cord > is plugged-in. > > As a result, you have some really useful functionality such as power > control (turn the server on/off remotely), access to sensors (MB & CPU > temperatures, voltages, chassis intrusion), text console, and KVM > console. > > KVM console is accessed using a Java application that has to be > installed on the client. It's pretty much identical to having a > physical monitor and keyboard attached, in that you can control the > system from the moment that it turns on, including going into BIOS. > The only glitch I found so far is that the connection freezes for a > few seconds while FreeBSD initializes em0 during boot. After that > everything is fine. That's really neat. How do you configure the LAN on that chip? For example, how do you specify the IP address, gateway, netmask, etc? Is this done in the BIOS? So you would normally have at least 2 IPs for the server - one for em0 and one for the special chip? Is this a separate ethernet jack? Also, what about being more vulnerable - I mean, it's an added way of compromising your system, right? Getting in through the KVM-over-IP?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimFGN72u1NVc74=c0DS-eNQHj-iSCAKFz51rZGj>