Server chronicles - KVM <-> IP on old System76

One of the things I would like to have in the renewed server is the capability to remote access it for monitor or emergency repairs or, like now, for a rebuilding, without the need to be physically present in the "server room" (in my case the garage) to connect a keyboard and monitor to the console.
This article is about the introduction and hardware settings, another one will discuss the installation and use.

Note !

This article was written thinking to the old System76 server that didn't have a full KVM.
The new server used, an HP ProLiant DL360, has fully KVM capability (iLO 4).
This article remains here only for reference.

KVM concept

The typical solution to handle remotely a server, is using a KVM extender.

KVM stands for Keyboard, Video, Mouse and is an appliance that allows to control these three components remotely.

There are KVM switch to connect a monitor and keyboard to different computers, KVM extenders to bring a keyboard/video/mouse remotely, KIVM <-> USB to use a computer via USB to remotely control another one and KVM <-> IP that allow to control a computer remotely using an intranet, or if you are crazy enough, internet.

In my case the choice is between a KVM extender and a KVM <-> IP.
The criteria to decide are :

• logistic
• price
• features 

A KVM extender is typically based on two unit, a transmitter to be connected to the server to control, and a receiver, to be connected to a keyboard/video/mouse.

The pro of this solution is typically the price.  Is possible to find very good extender below 100$, however the cons are the need to wire a dedicated cable between the two units and the need to have a dedicated monitor and keyboard somewhere.

I want to be able to use any existing computer in my network to control the console server and I can't easily wire another cable, it imply tear down walls again, I did that 14 years ago and it was a mess.

So the ideal solution for me is the KVM <-> IP.

The cons of this solution is the price !

A decent commercial KVM <-> IP, assuming to find one without going on specific markets, starts around 500$ !!!

True, usually they allow to connect more servers (a minimum of 8) and they are designed to be installed in a server farm, thus the capability to mounted in a rack.

Unless to be lucky to find some old unit on eBay or in some flea market, buy a commercial solution is probably not worth.

Another choice is  the DIY market  and in the end I did find only one project that is feasible : the PiKVM project.

A Raspberry Pi with a dedicated interface transformed in a KVM <-> PI with very interesting characteristics, like the possibility to use a web page or a VNC connection to control the console of the server.

The price is not low but surely lower if compared to a  commercial KVM solution.

Finding some components around can be built for about 150$.

Buying everything from scratch at the full price would be less than 300$, surely is expensive so in the end is matter of commodity.

But fortunately the server is coming with already installed a KVM <-> IP interface : the Integrated BMC Web Console

System76 server BMC WebConsole

Exploring the BIOS settings for updates I noticed settings for remote Ethernet interfaces at BIOS level and I did enabled one to see .. and voila', a full fledged KVM with diagnostic and KVM capability !

With this interface I can turn on/off the server and monitor all the hardware and even do some BIOS settings !

For the KVM functionality however is missing a small component that enable that :

An AXXRMM 4 LITE 2 -  REMOTE MGMT MODULE

As soon as it will arrive I will see if the full KVM capability come alive !

Installation

The only hardware installation is for the AXXRMM 4 lite 2 module.
Other than that is enough to enable the Ethernet interface for the BMC access.

The interface can be set static or via DHCP and I choose a static local access, it will be accessed only via local network.

The problem

Of course it was too good to be true to just buy and add the little module and have the full KVM enabled.

After spending some time looking for the module and ordered, when it arrived I did re-open the server to locate the connector.

But the connector was not there !
Or better, there was the PLACE for the connector but not connector.

The location on the motherboard

This could it means two things :

1. the motherboard just don't have populate the connector for an easy cheap way to force the user to upgrade to different mobo
   
   or
   
   
2. the motherboard miss more components than just the connector

The only way to discover that was of course to connect the module to the motherboard and see what happens.
So first thing was to retrieve a connector.
Measured the module connector and basically the need is for a 2x4 SMD male (pin) 1.27 mm pitch connector.

Did search on Mouser and Digikey but no big offer and what I did find required lot of time to receive.
Luckily I did find on Amazon a 2x80 pin SMD 1.27 mm pitch header that can be trimmed.

The 2x80 SMD 1.27 mm pitch header

The final connector 2x4

Solved the problem, I did solder the connector on the motherboard (VERY VERY difficult) and finally tested the module !
Useless to say ... is NOT working.

Actually the hardware diagnostic report a problem on the field BMC FW Health.
A warning is issued : "Sensor has failed and may not be providing a valid reading"

Basically the motherboard is telling me that is unable to access the AXXRMM module, I guess because some glue logic to handle the module is missing as well as the connector.

The situation thus is that I can not have the full native KVM from the server, only the power/diagnostic control, that is not bad.

For the KVM I need to work on another solution. 

Resources

• Intel - Intel motherboard used in the server 
• Intel - Integrated BMC Web Console
• PiKVM - PiKVM project