Fault event management using fault monitoring points

• US 6,832,341 B1
• Filed: 09/23/1999
• Issued: 12/14/2004
• Est. Priority Date: 09/23/1999
• Status: Expired due to Term

• Current Assignee: ServiceNow Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Vijayan, Geetha
• Primary Examiner(s): Baderman, Scott
• Assistant Examiner(s): Damiano, Anne L.
• Application Number:
  US09/404,273
• Time in Patent Office: 1,909 Days
• Field of Search: 714/43, 714/4, 714/47, 709/318, 709/224
• US Class Current: 714/43
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/2294 by remote test

Abstract

A method for monitoring faults within a computer network. In a preferred embodiment, an event, a host, and a fault monitoring point triplet are received from a monitored network device. A database of valid fault monitoring points is consulted to determine the validity of the event, host, and fault monitoring point triplet received. Responsive to a determination that the event, host, and fault monitoring point triplet received are valid, the appropriate party to notify and the appropriate message to send are determined. The appropriate party is then sent a message alerting them to the network problem. Different parties may be notified depending on the nature of the event or on the location of the event. Furthermore, a new network device may be added without taking down the fault monitoring system by merely adding to the database of valid fault monitoring points a new fault monitoring point corresponding to the added network device.

Claims

1. A method of managing a computer network, comprising the steps of:

receiving event information, wherein the event information includes an event and a hostname;

responsive to a determination that the event information includes a fault monitoring point, correlating the event, the hostname, and the fault monitoring point to determine a responsible party;

notifying the responsible party of the event; and

responsive to a determination that no fault monitoring point was received, providing a default fault monitoring point.

2. The method as recited in claim 1, further comprising waiting a period of time after receiving the first event information before notifying said responsible party.

3. The method as recited in claim 2, wherein

said event information is a first event information,

said event is a first event,

said hostname is a first hostname, and

said fault monitoring point is a first fault monitoring point, and further comprising

receiving a second event information during said period of time, wherein said second event information includes a second event, a second hostname, and a second fault monitoring point; and

responsive to a determination that said second hostname is the same as said first hostname, said first fault monitoring point is the same as said second fault monitoring point, and said second event is a cancellation of said first event, refraining from notifying said responsible party.

4. A system for managing a computer network, comprising:

means for receiving event information, wherein the event information includes an event and a hostname;

means, responsive to a determination that the event information includes a fault monitoring point, for correlating the event, the hostname, and the fault monitoring point to determine a responsible party;

means for notifying the responsible party of the event; and

means, responsive to a determination that no fault monitoring point was received, for providing a default fault monitoring point.

5. The system as recited in claim 4, further comprising means for waiting a period of time after receiving the first event information before notifying said responsible party.

6. The system as recited in claim 5, wherein

said event information is a first event information,

said event is a first event,

said hostname is a first hostname, and

said fault monitoring point is a first fault monitoring point, and further comprising

means for receiving a second event information during said period of time, wherein said second event information includes a second event, a second hostname, and a second fault monitoring point; and

responsive to a determination that said second hostname is the same as said first hostname, said first fault monitoring point is the same as said second fault monitoring point, and said second event is a cancellation of said first event, refraining from notifying said responsible party.

7. A computer program product in computer readable media for use in a data processing system, for managing a computer network, comprising:

first instructions for receiving event information, wherein the event information includes an event and a hostname;

second instructions, responsive to a determination that the event information includes a fault monitoring point, for correlating the event, the hostname, and the fault monitoring point to determine a responsible party;

third instructions for notifying the responsible party of the event; and

fourth instructions, responsive to a determination that no fault monitoring point was received, for providing a default fault monitoring point.

8. The computer program product as recited in claim 7, further comprising instructions for waiting a period of time after receiving the first event information before notifying said responsible party.

9. The computer program product as recited in claim 8, wherein

said event information is a first event information,

said event is a first event,

said hostname is a first hostname, and

said fault monitoring point is a first fault monitoring point, and further comprising

instructions for receiving a second event information during said period of time, wherein said second event information includes a second event, a second hostname, and a second fault monitoring point; and responsive to a determination that said second hostname is the same as said first hostname, said first fault monitoring point is the same as said second fault monitoring point, and said second event is a cancellation of said first event, refraining from notifying said responsible party.