An anonymous reader asks:
"I've been looking for a cost effective (ie, cheap) way to remotely administer several servers running a variety of OS's, and would like to have a solution that would allow for monitoring of the bios on startup, etc (ie, not VNC). The most appealing solution is KVM over IP, which really just means a souped up KVM switch with something like VNC running on it, unfortunately all of the solutions I've been able to find are more expensive than I can justify spending. I've played around a bit with making my own Poor man's KVM over IP; I did this by purchasing a cheap (sub $50) VGA-to-NTSC convertor, then feeding it into a video card with NTSC input (the ATI All-In-Wonder Radion), and then by logging into a machine running Windows Terminal Services I'm able to watch the reboot process. Of course, this doesn't address the mouse/keyboard issue, and the quality isn't all that great. What I'm hoping is that someone else might have a suggestion on how to do this, preferably using Linux and the least hardware necessary. Does anyone have any suggestions or insights on ways to do this?" There are pre-existing solutions, but it seems they are all kind of pricey. Can any of you suggest cheap solutions (at or below $500USD) that could handle a farm of 5-10 machines?
"Here are the three approaches I found:
ViewProxy:
They make the most economical for administration of multiple machines (by one person). Their ProxyView device plugs into your KVM just like it was a monitor/mouse/keyboard, and then does all the packetizing magic. Price is about $6k from what I can tell.
eRIC:
These are the same guys who make the Rolf (Reboot on Lan), which is pretty cool. They make a card called Eric which replaces your normal video card with their card, which has a built in ethernet connection and allows remote control. The cheapest solution at about $700 but only would allow control of the machine it's installed in.
Avocent: I think the first to introduce the whole KVM over IP solution, they have KVM's with this sort of functionality integrated. Some of their products allow multiple users to multiple machine, which is a neat feature but not needed for my applications. Their units run from $4k on up."
Slashdot Mirror
http://www.realweasel.com/intro.html
Many newer motherboards support BIOS redirection over the serial port. All of my systems (intel 440gx) supports this. It allows full remote BIOS configuration, etc. Used in conjuction with linux's serial console and sysrq over serial I find the solution works quite well.
- U
this link (which slashdot will probably munge: http://cyberguys.com/cgi-bin/sgin0101.exe?UID=2002 080514403159&GEN6=00&GEN9=5CG01&FNM=00&T1=104+1150 &UREQA=1&UREQB=2&UREQC=3&UREQD=4
or else try product # 104 1150 on http://www.cyberguys.com
it's a KVM "extender" that works over cat 5 for 500 feet. i don't know who makes it, but the cyberguys catalog had it. this plus a KVM switch on each end of your setup might be enable you to do what you want...
- Entertaining Bits from the Ancient Kernel Tree
Raritan has some nice CAT5 based KVM solutions, that work terribly well in scaling between small and large environments. However I think the price may be a bit higher then you were hoping.
A pair of Nikes cost less than $500 (but only just). That's about as close as you're gonna get.
This probably isn't exactly what you were looking for, but I would consider and maybe request an eval of VMware GSX Server or maybe even ESX Server. Both let you monitor the virtual machine over IP -- in fact, there's even a web-based administration interface. And, of course, you can watch BSODs as they happen, hit the reset button using your toolbar, and go into the BIOS setup utility remotely.
Neither is cheap (GSX is the cheaper of the two and runs $3500, $1600 academic) but if you can consolidate your boxes into one big box it might be worth it. After all, it's always good to centralize your points of failure, right?
Big thumbs up for VMware.
But given that non-PC hardware is probably not an option for you, then consider something like the RealWeasel, although I've heard mixed reports about it from those that have tried it. The online demo looks like it should at least be usable, though.
"The invisible and the non-existent look very much alike." -- Delos B. McKown
KVM over IP is going to be costly into the near future. This isn't exactly commodity hardware, so it may stay high for a looong time.
You may want to consider an alternative approach (which is what I have been doing ever since the remote KVM sticker shock faded) which obviates the need for a remote KVM at all.
For example:
1. All systems boot from custom CD-R (good for security too) which then boots the remainder off a network drive or perhaps hdd.
2. Remote power cycling (cheap, $100 for 8 ports you can controll over IP) is used to power cycle one or more machines to force a reboot.
3. If you need to reimage the OS, simply replace the OS stored on the boot server, or have the CDROM boot image reimage remotely when given a specific trigger (this is the area wide open for all kinds of solutions. Luckily, all software based using linux and cheap CDR's, network filesytems, etc)
This still has a number of drawbacks. If the machine doesnt come back, there is no remote KVM access to tell you what the bios is complaigning about (bad disk?).
The bootup process is cumbersome. I.e. you need to always boot from CDR to be able to reimage a system later (dedicated hosting) and such.
We use VNC here at work over 10/100 at those specs with no issue whatsoever. Hell, I use IBM's Desktop on Call over a 56k Connection without any fuss. Your issue is a non-issue.
I'm a writer, a poet, a genius, I know it. I don't buy software, I grow it.
http://www.minicom.com/specter.htm
. Get a Clysdale terminal server,
:)
Uh, don't you mean Cyclades? I think someone needs a beer...
I just picked up a few Compaq Remote Insight boards on ebay for about nine dollars each. Seems to be a good system as it allows remote power on and access even after a power outage thanks ot a battary backup.
"Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
Oh yeah...now I remember...I "rebooted" last month. Never again.
Just out of curiousity, what is your IP address?
- A.P.
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
Did this: Bought a Cyclades 8-port serial board and stuffed it into a P133. Load $FreeOS and $Term_Program and go at it. Keep in mind that consoled-devices that don't deal well with a serial BREAK may not like it if/when you reboot the console server box. There are usually hardware or software ways around this.
Why would you need anything more than a console? After the machine is booted up beyond the BIOS/etc, you can use the features of X or VNC to do whatever you want with a GUI. There is no need for it.
Moon Macrosystems. Sun's biggest competitor.
Namely this: There are two ways to do things: The right way, and the Slashdot way.
The Right Way involves spending a little more money up front, but its benefits are manyfold: A proven solution, vendor support, reliability, stability, and various and sundry other good things.
The Slashdot Way involves duct tape, bailing wire, and, sometimes, a 386 running RedHat. Its generally insignificant up-front savings are offset by the countless hours of configuration, tuning, tweaking, prodding, poking, and general lackluster performance of the contraption in question.
You have chosen to go The Slashdot Route. I wish you luck as you set up your TV cards and serial ports. You will need as much luck as you can get, and an awful lot of patience.
- A.P.
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
We have a semi-large farm of Windose Boxen at a lights-out colo (Frontend application servers to most of the UNIX boxen). We just picked up the Rose Electronics Ultralink for remote management. We need this so we can do remote diags, like troubleshoot hardware, view POST, etc. We have Cyclades for the *NIX boxen, and our HP Netservers have the serial 'management' console that other people are boasting about, but that just won't cut it in a real-world production environment. A Console is a Console and a serial port is a serial port.
.99a ... we had to wait about 2 months to get it, and we must have been the first guinea pig to take shipment. I'm afraid to open it up to see if there is about 35 feet of spaghetti-wire patches.
We're going to plug the Ultralink into our cascaded KVM tree and hope for the best. Initially looking at the unit, I have some gripes:
* No distributed authentication. It's gotta be local accounts. Can't hit my LDAP, NIS, NT Domain, or RADIUS servers.
* Client is a proprietary Win32 app. No JAVA, no browser. Cripes, not even ActiveX!
* Only one user at a time... including console. You have to log into the console to gain access (crappy for CEs out to fix a problem), and if the CE stays logged in, guess what? You can't access it remotely! We had to plug it into our intelligent PDU so we could remotely hard boot it if that happened.
* We have what must be version
Aside from these (minor) flaws, I think we'll be OK. Anything is better than booking a last-minute 606 mile flight to reboot a Windows box that shows 'It is now safe to power off your computer' because PCNowhere admin chose the wrong logoff choice. [don't laugh] (Although, there is Buckhead...)
How often do you really need "true console" access on a box that has no network connectivity?
I've found that having the ability to remote power cycle (preferably through an interface -- but an ISP that can get someone to the box fast can do in a $ pinch) + some remote network admin tools (VNC, Terminal Services, Telnet/SSH, etc etc) goes a *long* way.
Yes, once in a while the box crashes *so* hard that Terminal services/VNC (assuming a Windows platform) becomes useless -- time for a reboot! The only way that you can really screw yoursel is if you mess with the network settings and configure yourself off the network.
Rather than spend $$$s for that possibility, why not just pick up the phone and call some hands-on support (or if it is your datacenter.. send in the geeks)...?? If you know you are going to be messing with "dangerous" settings, you should be prepared for these sorts of possibilities anyways..
Just my $.02...
Evolution: love it or leave it
which is more than most of the "buy it off the shelf" people often have. The advantages to experimentation are many. While time savings is probably not one of them (at least in the short run) by the time the project is done, the experimenter has a better idea of how to go about getting things done than the buy-it-off-the-shelf guy.
A few years down the road and most of us will want to hire the experimenter who has tried several different OSes, hacked out a wireless network out of a couple 2-meter transceivers, set up two 486 DX66 boxes as a dedicated VPN between his bedroom and his girlfriend's house, and wired up the girl's locker room with x10. Those are the guys who can think their way through a problem rather than hitting the catalogs looking for a million dollar solution.
No one ever had to evacuate a city because the solar panels broke!
Love their attitude:
"What sucks." "How we fixed it." "Why we're swell." "Asses saved."
I know it's not exactly what the poster asked for, but I was in the same boat about 6 months ago and you can at least step through my thought processes.
Article linked here.
Secondly, if you're running like 4 TV-Cards doing realtime video (mpeg4) encoding of 4 s-vga video signals, we're talking like 60GB/sec bandwidth raw IO (per channel)! I think you would probably need SCSI for that.
Also, since the place I worked for did this with a bunch of old Sun's we had laying around, I think you would need more raw numbercrunching power than that P166 is going to provide. I swear to god, to get that type of throughput, you'll need at least a P250. You'll have difficulty overclocking your 166 to go a 250Mhz without using water-cooling.
Which is what we ended up doing on that Sun, too, btw. Man you've not played Quake Arena, till you've played it on an E450 with 24 UltraSparc2's overclocked from 450 Mhz to 600 Mhz, at first we though we would have to use liquid helium to cool the fucker.
You do, too! I've been watching your talking and typing recently. It is I who doesn't usually talk this way.We got a demo of an Avocent unit that did the same thing. It did have a centralized user database capability (unfortunately I think it was like Windows domain auth or something less flexible than RADIUS/LDAP/TACACS+).
It worked well, but REALLY expensive for a 16 port version. Expensive to the tune of around $10k for the box, the auth server module, and 2-3 client licenses. I was most turned off by the fact that the server and client software were $old $eperately, since the software is useless without the hardware.
I read a USENET post (circa 11/2001) that said the devices were buggy and the vendor was an asshole about other platform clients and future development/changes.
I think digitized video and IP KVM connectivity is probably not a fluke and represents the "future" of KVM, but vendors will need to seriously get their shit together in terms of client access and pricing otherwise computer makers are just going to crush this product with their own built-in remote management. All our HP servers have built-in serial management that can do power on/off/reboot, environment management, and text/keyboard redirection; HP and Compaq both have boards that can do it natively over IP, the *only* thing missing is the ability to do transparent video redirection. When they do that, KVM will be obsoleted by a laptop running a redirection client.
However, this doesn't make for "The Right Way". Hacking at something - figuring out how it works, seeing how you can do it better (or less expensively), and enjoying the process - is the source of solutions that Just Work.
No. Generally, in my experience, it's the source of solutions that Almost Work. Or solutions that Work Unless You Do This. Or solutions that Just Worked Last Week, What the Hell Did We Change That Broke It?
"[G]eneral lackluster performance of the contraption in question" is the result of not understanding something enough to do it well. Many off-the-shelf solutions suck - Windows 98, anyone? So do many home-brew setups. The problems doesn't come from the nature of a rig, it comes from the effort and intelligence of the creator.
No, the problem comes from the continual poor reinvention of the wheel on Ask Slashbots. In this situation, KVM-IP switches are the answer. Not a 486 with a bunch of TV cards in it. Not a rat's nest of cables. If this person worked for me and proposed this solution, I would have a hard time signing his checks from then on.
- A.p.
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"