christian hofstaedtler
Lessons learned with Supermicro's remote management/IPMI view

Supermicro's recent IPMI/KVM ("remote server management with graphical console") violates all good design principles and what you would expect from such a solution.

Basically, it works like this: there is some management controller on the mainboard, with it's own dedicated network port. It's got an HTTP interface for use & configuration. For use it offers basic power control (off, on, reset), a serial-over-lan transport, and a graphical console which can also provide disk services to the host (CD/ISO, USB Key, floppy).

For the basic feature set, this sounds like what you want to use.

Unfortunately Supermicro's implementation adds a great deal of obstacles which make using it nearly impossible. Here's why:

None of this does any good.

Details:

A friend pointed me to the so called "IPMIView" tool, which basically is a standalone version of the graphical console and some other bonus features. Compared to the Java applet stuff, it feels rather stable, but has the same platform limitations (i.e. Windows + "Linux" only). It appears to be available only from SM's FTP server: ftp://ftp.supermicro.com/utility/IPMIView/

Also, to compare this situation with HP: HP's "ILO 2" is very slow, went through a few firmware versions to fix rather odd bugs, but: the basic features (== what you depend on during emergencies) work and worked all the time. Their graphical console also is Java, but with no native code, and therefore works fine on a Mac and IIRC it also worked fine on ppc Linux.

Sidebar:

This has cost a client about 12 man hours. They're using Macs in the office, and those are now basically useless during emergency times.