The best bet is a single user/single server KVM over IP unit, which is essentially a bridge between Ethernet and a Keyboard/Video/Mouse set.

by jdray

Two choices: first, an IP KVM installed in each rack. But you still have to address the power switch and media. Another poster mentioned PXE booting. It works, but takes effort to build all the different images you want to have handy, and what do you do for a hung box 1,000 miles away? Or once you address the power question, the NIC is bad?

Second: IBM (and others) offer remote systems management cards that not only give you full remote KVM on the server the card is installed in, but they also give you access to the system power and screen captures of blue screens that may have occured before the server rebooted itself to recover. They can also present virtual floppy and CD-ROM drives to their host servers. Finally, if you don't want to run 10/100 and do IP allocations for each management card, you can daisy chain up to 24 servers together over RS-485 and use any one of them as a gateway to the IP network.

One IP address. Full remote KVM access to up to 24 servers at a time. Access to the system power. Access to screenshots of blue screens that may have tripped a reboot. Full hardware and software alert forwarding directly handled by the gateway card or passed on to enterprise systems management environments via numerous methods. Virtual floppy and CD-ROM drives. If you still absolutely insist on going onsite to the box, you can sit at a desk in the corner and get an IP.

by LinuxHam

The issue with network-based server management is that it isn't suitable for a large data center. For instance, a typical webhosting setup might have a couple hundred (or thousand) servers - the ideal target for remote management, because it's wildly impractical/impossible to put them all on KVMs. Each server will have one NIC for the "public" network, the one connected to the Internet. To help lock down remote access for SSH etc., you will also have a private network. We're already up to two distinct networks here, you'll note. Now add a third one for management, which incidentally is also going to require DHCP. The cost for building yet another discrete internal network - and managing it! - is going to be nontrivial. It's usually cheaper, and about as effective, to buy a couple cheap-ass carts and put monitors and keyboards on them. It means your NOC staff has to get off their asses every now and then, but… Is sparing them that really worth the $10k+ it will probably cost in network hardware (not to mention cabling nightmares)?

Serial consoles are great, but not for PCs. In a big DC, you will not have the root password to every server. You will be logging in via some special authentication mechanism like SecurID and then doing sudo su (or just ssh public keys). So getting a login prompt is not going to be helpful; you'll have to reboot the server. On real Unix hardware, you can usually do this by sending a hardware break and typing "reboot" (or similar). This will work even if the OS is crashed or thrashing or whatever. On a PC, no dice, because it's purely the software which handles the serial connection. So you have to hit the reset button, which will probably solve whatever issue was going on anyway (while simultaneously destroying any in-memory logs of what the cause might have been).

For us, in our DC with about 5000 servers, the worst servers to manage are actually the real Unix hardware, but that's only because we have just the one laptop (and because the Unix servers are all disasters held together by spit and baling wire, but that's another story). Also the laptop sucks ass and keeps breaking because it's 6 years old and has been dropped several times. That's something else to keep in mind if you're looking for a laptop-based solution: People Will Drop It. Not only that, if they have to step away from the server for a second, the laptop will get left on the floor, where some unwary soul will step on it or wheel a crash cart over it. Laptops are expensive, even secondhand. A crummy 15" CRT and keyboard will set you back $100, if that, and if they're on a cart that can be wheeled around they won't get dropped (often). Just make sure to buy monitors with fully-removable video and power cords, so when someone wheels the cart off without unplugging it you won't wreck the server's video connector and pull the PDC out of the rack.

by ctr2sprt

If we can't ssh to computers or telnet to equipment (switches, etc) we have an OpenBSD laptop which we can use as a console via a serial cable and kermit. That's assuming a unixish system, though. If you're only running Windows on servers then why not install TightVNC and control it from your desktop?

by grub

KVM over IP ? - I think some one has already mentioned this previously, however, they mentioned the plugin card variety. You can also purchase a stand alone box, similar to a regular KVM, however, it routes the Keyboard, Video and Mouse via IP to any machine that is network capable. The client is supplied either as a windows binary or as a Java applet (when you browse to the maintenance webpage. You can, in theory use a wireless PDA or laptop with a java enabled web browser to connect directly and control these devices.

by farzadb82

documented on: 2008-05-21