I’m spoiled. Really, really spoiled. I have a test lab full of servers to play with about thirty paces away from my office. Most of them have KVM over IP on a daughtercard. When I need to jam an OS on a server or manage to lock myself out by screwing up a network config, do you think I stand up and take a short walk? Nope. I fire up the KVM/IP and take care of business from my comfy office chair.
Let’s see how old the audience is. Raise your hand if you ever had to yell into a phone telling a datacenter tech what to type.
“'S' as in Sam, 'H' as in Harry, 'O' as in Oscar, 'W' as in Wally, SPACE, 'D' as in David, 'E' as in Edward, 'V' as in Victor, 'I' as in Isabel, 'C' as in Charlie, 'E' as in Edward, ENTER” (extra credit to whoever can name the OS without using a search engine or reading ahead).
For some of you this is a recent event, but there will come a day when our IT generation can regale the youngsters with stories of “When I first started in IT, we didn’t have this fancy KVM stuff you kids have today…”.
KVM over IP isn’t exactly brand new. It has been around for a few years starting with external devices hanging off the back of the server. But it is becoming much more common to find daughtercards from your favorite motherboard manufacturer with this capability. The motherboard suppliers have already added other server control technologies like IPMI and iAMT to the motherboard. I wonder how long until KVM over IP makes the jump from the optional daughtercard to coming standard on the motherboard? I’ll bet we’ll see it before you can spell VMS.