IP Library Granted Patent US 6,986,076
Granted Patent B1
US 6,986,076 · App. 10/156,486 · Granted Jan 10, 2006

Proactive method for ensuring availability in a clustered system

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 6,986,076
App. No.
10/156,486
Granted
Jan 10, 2006
Kind
B1
Abstract

The method of the present invention is useful in a computer system including at least two server nodes, each of which can execute clustered server software. The program executes a method for monitoring failure situations to reduce downtime. The method includes the step of detecting an event causing one of the failure situations, and then the method determines if the event affects one of the server nodes. If it is determined the event does affect one of the server nodes, the method then determines if the event exceeds a threshold value. If it is determined the event exceeds a threshold value, the method executes a proactive failover. If the event is not specific to a cluster node, but indicates an impending or actual failure of the cluster software, the method identifies and initiates an appropriate action to fix the condition or provide a workaround (if available) that will preempt an impending failure of the cluster system or would enable a restarting of a failed cluster software.

Claims (36)

1. In a computer system including at least two server nodes, each of which can execute clustered server software, a method for monitoring failure situations to reduce downtime, said method comprising the steps of:

(a) detecting an event causing one of said failure situations;

(b) determining if said event affects one of said server nodes, and if so;

(c) determining if said event exceeds a threshold value, and if so;

(d) executing a proactive failover;

(e) determining if said event does not affect one of said server nodes, and if so;

(f) determining if said event affects the condition of the cluster service, and if so;

(g) identifying and initiating an appropriate action to fix said condition or provide a workaround that will preempt an impending failure of the cluster system, or restart a failed cluster system.

2. The method as in claim 1 wherein said threshold value is selected by a user to represent unacceptable server conditions.

3. The method as in claim 1 wherein said step (a) of detecting said event includes the steps of:

(a1) listening for an SNMP event;

(a2) listening for an event log event.

4. The method as in claim 3 wherein said step (a1) of listening for said SNMP event includes the steps of:

(a1a) determining if SNMP service software is installed, and if so;

(a1b) determining if SNMP agent software is installed, and if so;

(a1c) initiating a thread to receive and process SNMP traps.

5. The method as in claim 4 wherein it is determined in step (a1a) that said SNMP service software is not installed, then further comprising the step of:

(a1a1) creating a notification to install said SNMP service software.

6. The method as in claim 4 wherein it is determined in step (a1b) that said SNMP agent software is not installed, then further comprising the step of:

(a2b1) creating a notification to install said SNMP agent software.

7. In a computer system including at least two server nodes, each of which can execute clustered server software, a method for monitoring failure situations to reduce downtime, said method comprising the steps of:

(a) detecting an event causing one of said failure situations said detecting including the steps of:

(a1) listening for a Simple Network Management Protocol (SNMP) event;

(a2) listening for an event log event; wherein said step (a2) for listening for said event log event further includes the steps of:

(a2a) opening a connection to a Windows Management Instrumentation (WMI) service;

(a2b) subscribing to receive event log messages from said WMI service;

(b) determining if said event affects one of said server nodes, and if so;

(c) determining if said event exceeds a threshold value, and if so;

(d) executing a proactive failover.

8. The method as in claim 7 wherein said step (c), of determining if said event exceeds a threshold value, further includes the steps of:

(c1) ensuring said node affected by said event owns a cluster group;

(c2) ensuring there is a remaining node to failover to;

(c3) ensuring said remaining node is clear of critical events.

9. The method as in claim 7 wherein said step (d) of executing a proactive failover includes the steps of:

(d1) initiating a failover process for each cluster group in an offline state;

(d2) logging the result for each of said failover processes.

Assignments (11)
RELEASE OF SECURITY INTEREST Recorded Nov 9, 2017
From: WELLS FARGO BANK, NATIONAL ASSOCIATION (SUCCESSOR TO GENERAL ELECTRIC CAPITAL CORPORATION)
To: UNISYS CORPORATION
Reel/Frame 044416/0358 →
CHANGE OF NAME Recorded Oct 5, 2017
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 044127/0735 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 17, 2012
From: UNISYS CORPORATION
To: GOOGLE INC.
Reel/Frame 028060/0908 →
RELEASE OF SECURITY INTEREST Recorded Feb 29, 2012
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: UNISYS CORPORATION
Reel/Frame 027784/0777 →
RELEASE OF SECURITY INTEREST Recorded Feb 29, 2012
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: UNISYS CORPORATION
Reel/Frame 027784/0530 →
RELEASE OF SECURITY INTEREST Recorded Feb 29, 2012
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: UNISYS CORPORATION
Reel/Frame 027784/0701 →
SECURITY AGREEMENT Recorded Jun 27, 2011
From: UNISYS CORPORATION
To: GENERAL ELECTRIC CAPITAL CORPORATION, AS AGENT
Reel/Frame 026509/0001 →
PATENT SECURITY AGREEMENT (JUNIOR LIEN) Recorded Oct 13, 2009
From: UNISYS CORPORATION
To: DEUTSCHE BANK TRUST COMPANY AMERICAS, AS COLLATERAL TRUSTEE
Reel/Frame 023364/0098 →
PATENT SECURITY AGREEMENT (PRIORITY LIEN) Recorded Oct 12, 2009
From: UNISYS CORPORATION
To: DEUTSCHE BANK TRUST COMPANY AMERICAS, AS COLLATERAL TRUSTEE
Reel/Frame 023355/0001 →
RELEASE BY SECURED PARTY Recorded Sep 14, 2009
From: CITIBANK, N.A.
To: UNISYS CORPORATION; UNISYS HOLDING CORPORATION
Reel/Frame 023263/0631 →
RELEASE BY SECURED PARTY Recorded Jul 31, 2009
From: CITIBANK, N.A.
To: UNISYS CORPORATION; UNISYS HOLDING CORPORATION
Reel/Frame 023312/0044 →