SYSTEM AND METHOD FOR PERFORMANCE PROBLEM LOCALIZATION

• US 20080140817A1
• Filed: 12/06/2006
• Published: 06/12/2008
• Est. Priority Date: 12/06/2006
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Agarwal, Manoj K., Gupta, Manish, Sachindran, Narendran
• Application Number:
  US11/567,240
• Publication Number:
  US 20080140817A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0677 Localisation of faults
• CPC Class Codes: H04L 41/147 for predicting network behaviour
• CPC Class Codes: H04L 41/16 using machine learning or artificial intelligence
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 43/091 Measuring contribution of individual network components to actual service level
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A method and a system for resolving problems in an enterprise system which contains a plurality of servers forming a cluster coupled via a network. A central controller is configured to monitor and control the plurality of servers in the cluster. The central controller is configured to poll the plurality of servers based on pre-defined rules and identify an alarm pattern in the cluster. The alarm pattern is associated with one of the servers in the cluster and a possible root cause is identified by the central controller with labeled alarm pattern in a repository and a possible solution is recommended to overcome the identified problem that has been associated with the alarm pattern. Information in the repository is adapted based on feedback about the real root cause obtained from the administrator.

Claims

1. A method for localization of performance problems in an enterprise system comprising a plurality of servers forming a cluster and providing possible root causes, the method comprises:

monitoring the servers in the cluster, wherein monitoring the plurality of servers in the cluster further comprising;

polling the plurality of server in the cluster based on pre-defined rules; and

identifying the alarm pattern with the at least one server in the cluster;

receiving an alarm pattern and a server identification of the server(s) at a central controller;

assigning a list of root causes for the alarm pattern received in order of relevance;

selecting the most relevant root cause from the list of root cause(s) based on an administrator feedback; and

updating the repository with the alarm pattern and the assigned root cause label,

presenting the received alarm pattern to the administrator, wherein the received alarm pattern is associated with a faulty server(s);

fetching a list of possible root cause(s) associated with a alarm pattern in a repository, wherein the alarm patterns in the repository are labeled alarm patterns;

presenting the administrator with a list of possible root cause(s) in an order of relevance, wherein the order of relevance is determined from a computed score;

matching the received alarm patterns with the list of possible root cause(s) that are fetched from the repository,

associating possible root cause(s) with the faulty server(s); and

displaying the faulty server(s) identity with the most likely root cause for the alarm pattern

wherein presenting the list of possible root cause, matching the alarm patterns, assigning a root cause and updating the repository is performed without any human intervention,

wherein assigning the list of root cause(s) further comprises;

assigning a new root cause label for the alarm pattern when the received alarm pattern is not recorded present in the repository based on the administrator feedback, and

wherein recommending at least one root cause in order of relevance comprises computing a score;

2-16. -16. (canceled)