Virtual Console KVM?

[Chapbass]

Hey all, not quite sure where to put this, but I'm guessing more people in the networking subforum may have experience similar to this.


Heres, my issue: I have a remote datacenter (which isn't too far, but regardless) that I would like to have remote console access to. Now, I have a server over there that is strictly dedicated to management only. My question is this:

Is there a way I can use that as a springboard for a software style console KVM?

I'm thinking similar to the way ESX/vsphere handles virtual machines...you can go into the VIClient, open the console, and see everything from POST all the way to bootup and everything else.

I know I could shell out some cash for an IP KVM and do it that way, but is there a way I can do it for cheaper through some fancy software? I'm trying to figure out how it would do it with connectivity, but not sure whats out there.

This making any sense?

Thanks!

Edit: The things I would need to connect are a few IBM servers and possibly a Barracuda spam filter and/or Sonicwall CDP.

 

[Jamsan]

Unfortunately, the only two options I know of cost money.

1 - IP KVM. You've already mentioned you want to avoid this route if possible (due to cost I'm guessing).

2 - IBM Remote Supervisor Adapter - Similar to HP's iLO, Dell DRAC, etc. - it's a dedicated NIC on the server that allows for out of band management of the system (i.e. BIOS level / pre-boot access to the system). If you've only need to gain access to a few servers, this option would be more cost effective than an IP KVM (For Dell's, these are typically around $150 or so per server).

For the spam filter and NAS - if there's a console port on them, I'd cable them directly to a server's serial port and access using your favorite program.

 

[Nothinman]

Why do you need console access? Wouldn't RDP, ssh, etc be good enough?

 

[Jamsan]

Why do you need console access? Wouldn't RDP, ssh, etc be good enough?

In the event the server blue screens / hangs, need to make BIOS changes, etc. Anything that needs to be done to a server outside of the OS.

 

[Nothinman]

In the event the server blue screens / hangs, need to make BIOS changes, etc. Anything that needs to be done to a server outside of the OS.

But those are extremely rare occurrences and it sounds like he would rather drive over to the datacenter than buy an IP KVM or similar.

 

[Chapbass]

But those are extremely rare occurrences and it sounds like he would rather drive over to the datacenter than buy an IP KVM or similar.

Well, its at the request of my boss, but hes right, it would be for BIOS things, etc.


Can you get into the command line for ESX remotely? I didn't think so, but if you can that'd help...maybe though ssh?

EDIT: And yeah, we already have RDP and VNC to all of the servers within their OSes, so thats not a big deal.

 

[Emulex]

seems like the cost of the oob management is more than your time and gas money? that is a poor choice my friend

 

[Chapbass]

I would agree, which is why I was asking in the first place if there was a cheaper alternative.

Gonna talk with them on monday to see if they have other planned uses for this.

 

[Nothinman]

Well, its at the request of my boss, but hes right, it would be for BIOS things, etc.


Can you get into the command line for ESX remotely? I didn't think so, but if you can that'd help...maybe though ssh?

EDIT: And yeah, we already have RDP and VNC to all of the servers within their OSes, so thats not a big deal.

Did you order all of the servers without iLO or DRAC cards? If so then you'll need to order a bunch now or get something more generic like an IP KVM, there's really no way around it. Get a couple of quotes and present them to him with numbers for the cost of you having to drive down there and do the work on-site. If you get mileage and other expenses mention that as well. He may still opt to risk having to pay you instead since that should be a very rare occurrence, but that's his call.

 

[Chapbass]

Did you order all of the servers without iLO or DRAC cards? If so then you'll need to order a bunch now or get something more generic like an IP KVM, there's really no way around it. Get a couple of quotes and present them to him with numbers for the cost of you having to drive down there and do the work on-site. If you get mileage and other expenses mention that as well. He may still opt to risk having to pay you instead since that should be a very rare occurrence, but that's his call.

We didn't order any remote mgmt cards as at the time of ordering they were in our in-house DC. Since then, theyve been moved, soooo yeah.

Who knows, I'll talk with him in a few hours and we'll see what happens.

 

[cmetz]

Chapbass, it basically comes down to this: does your company want to play this the professional way, or the amateur way?

The professional way: you buy servers with integrated management and IP KVM capability, you put those management NICs on their own LAN segment, and you have a VPN and maybe even a dial-up connection into that back-net. You'll also typically put a serial terminal server on there and connect all your network gear's management interfaces to that, and you'll also typically put a remote switched PDU on there. Using such a scenario, you can do software/OS level debugging, rescue, and re-install from your remote office location. You would only need to physically go to the data center in case of a hardware failure. (if you want to get really professional, you can design things with redundancy and spares so even that doesn't need to happen in order to get running again)

The amateur way: you accept that there's going to be downtime and drive to the data center.

I can tell you from lots of experience that there's really not an in-between state. If you don't spend the money and design for professional remote management, you will have the downtime and you will have to physically go there. It's really a business decision.

 

[Emulex]

ILO are not cards - they are standard on every server and bladesystem now. you can buy fake? keys off ebay for $20

lo100 the same. they just share the management with the existing nic(s) instead of a dedicated nic. but you can vlan it .

 

[talion83]

Well, its at the request of my boss, but hes right, it would be for BIOS things, etc.


Can you get into the command line for ESX remotely? I didn't think so, but if you can that'd help...maybe though ssh?

EDIT: And yeah, we already have RDP and VNC to all of the servers within their OSes, so thats not a big deal.

Thought I would drop back on this - yes you can putty/SSH into an ESX host. If you ever need to contact VMWare support you will normally find that you need to do this in order to do any sort of true troubleshooting.

Google 'Putty' and you will find a free ssh program(s). You will need to configure an account with SSH access. I recommend using a regular account to gain SSH and then needing to use 'su -' to change to root credentials (rather than giving Root direct SSH that is).
--------------

If you don't want to spend the money to get both network KVM and remote management cards I would suggest at least doing the KVM. A 16 port should run around $3000-$4000, a bit less if you need 8.

 

[cmetz]

Emulex, the lo100 have software issues with some OSs, they do some things related to NIC (PHY?) chip initialization and hand-off that if your OS doesn't do the right thing, the management doesn't work right and badness ensues.

Also, putting the OOB management on the same physical link as the in-band OS network connection is a security fail.