I am a newbie when it comes to colo but I am getting ready to colo my first server with my local ISP. I will be shipping it out tomorrow but I need to know if I need to send out a keyboard along with it to avoid a keyboard error during boot up? This will be a used strictly as a game server and I have everything set up and tested it out locally but when I disconnect the keyboard the server hangs because of a keyboard error. Any help would be appreciated.

Thanks

You should be able to change this in your BIOS (unless it's a desktop or some desktop based motherboards). If not, then you should send the keyboard.

In the last years I haven't seen a BIOS without the option to ignore keyboard errors.
Otherwise you would get an error "no keyboard found - press F1 to continue" :)

Every ISP or host I know of has keyboards, and something they often call a "crash cart". If it needs to be booted or rebooted, they should be able to handle it. If you have an old, extra keyboard, it doesn't hurt to throw it in though.

Every ISP or host I know of has keyboards, and something they often call a "crash cart". If it needs to be booted or rebooted, they should be able to handle it. If you have an old, extra keyboard, it doesn't hurt to throw it in though.The problem is that when we do a reboot, we don't normally hook up a KVM to the server/computer. We just flip the switch :)

Wow, you should be more prepared! I'm just giving you a hard time. I suppose if you run into any systems like that, that you can make sure they send in a keyboard though... definitely not something you want to find out at 2 AM when everyone's closed and you don't have one. However, one keyboard and an adapter (depending if you need one) and you've got a solution, so...

Originally posted by RackMy.com
The problem is that when we do a reboot, we don't normally hook up a KVM to the server/computer. We just flip the switch :)

I was working with someone that had a Sun Fire 3800, which was being used as an Oracle database server. The server became unreachable, and so they called the data center to have it rebooted. The ops guy, trying to be proactive, decided he was going to reboot the server before he called the customer from the rack. The 3800's do not have a power button, so he pulled the power cord out of the back, counted 10, and plugged it back in.

He spent the next six hours trying to restore the database he had corrupted :D.

He spent the next six hours trying to restore the database he had corrupted Been there, done that. :)