Browse Prior Art Database

Fail-Safe Mechanism to Remotely Re-Boot a Server

IP.com Disclosure Number: IPCOM000130719D
Original Publication Date: 2005-Nov-02
Included in the Prior Art Database: 2005-Nov-02
Document File: 1 page(s) / 46K

Publishing Venue

IBM

Abstract

Fail-Safe Mechanism to Remotely Re-Boot a Server

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 56% of the total text.

Page 1 of 1

Fail-Safe Mechanism to Remotely Re -Boot a Server

There are times when a Server has to be remotely cold re-booted, i.e. "power cycled". This is needed when a "warm" re-boot, or a re-boot done from the O/S with the power on does not work. If the system "hangs" or fails to restart normally due to a software issue, someone will need to physically go to the machine and shut the power off then on again. Several solutions exist in the industry that provide remote server control, however they typically have nontrivial costs and connectivity requirements.

Many control devices require a network connection and communication stack (e.g. TCP/IP) to implement a remote control function, and may not have security components available due to the cost of this infrastructure. This leaves these devices vulnerable to the many well-known means of network attacks present today. Alternatively, the solution described here could use a local connection, such as a USB or serial connection, similar to that used by many Uninterrupted Power Supply (UPS) devices to communicate power problems to the server. Using a secure connection to the server through software such as IBM Desktop OnCall, Microsoft Remote Desktop Connection, or other similar means, the operator can safely control server functions and issue the necessary commands to perform these actions on the server without connecting directly to the power control box.

Server

UPS

Power

USB/Serial communication

 Running On Backup Power

The sol...