Root-cause approach to problem diagnosis in data networks

• US 6,701,459 B2
• Filed: 12/27/2000
• Issued: 03/02/2004
• Est. Priority Date: 12/27/2000
• Status: Active Grant

• Current Assignee: eG Innovations Pte Ltd.
• Original Assignee: eG Innovations Pte Ltd.
• Inventors: Vaidhinathan, Balamurugan, Ramanathan, Srinivas
• Primary Examiner(s): LE, DIEU MINH T
• Application Number:
  US09/750,890
• Publication Number:
  US 20020083371A1
• Time in Patent Office: 1,161 Days
• Field of Search: 714/37, 714/4, 714/38, 714/39, 714/47, 709/223, 709/224, 709/229, 709/230
• US Class Current: 714/37
• CPC Class Codes: G06F 11/2294 by remote test

Abstract

A method of monitoring a data network includes storing topology information that identifies interconnections and interdependencies among network components, as well as links between websites and the components. Each component is also mapped to relevant protocol layers of a hierarchy of protocol layers that are ranked according to dependencies among the protocol layers in implementing functions. Network test measurements are also mapped to the appropriate protocol layers. Based upon the topology information and the various forms of mapping information, a user is able to navigate through a web-based user interface to determine root causes of network problems. Alternatively, an automated correlation process may be used to prioritize alerts of network problems, so that the root cause can be more easily ascertained.

Claims

1. A method of monitoring a data network comprising the steps of:

storing network topology information that specifies interconnections and interdependencies among components of said data network;

defining a hierarchy of protocol layers on a basis of dependencies among said protocol layers in implementing functions utilizing said components of said data network;

associating each said protocol layer with each said component on which implementations of said functions are related, thereby associating at least some of said components with a plurality of said protocol layers;

identifying tests from which measurements are indications of health within said data network;

associating said measurements with said protocol layers on a basis of relationships between said measurements and said protocol layers; and

ascertaining health of said data network, including identifying present health conditions of said protocol layers and said components on a basis of associations between said measurements and said protocol layers and on a basis of associations between said protocol layers and said components.

2. The method of claim 1 wherein said step of storing network topology information includes generating information that is representative of a physical topology and logical topologies of said data network, said physical topology being a configuration of physical connections among said components and including cause-and-effect relationships of health conditions among said components, said logical topologies including a mapping of individual websites to each said components for which said individual website is dependent for support of said individual website.

3. The method of claim 1 wherein said step of defining said hierarchy of protocol layers includes positioning a sequence of (1) a web server layer, (2) a website layer and (3) a web transaction layer in an ascending order in which higher levels in said ascending order are dependent upon support by lower levels.

4. The method of claim 1 wherein said step of associating each said protocol layer with each said component includes identifying said functions with specific said protocol layers and includes mapping each said protocol layer to specific said components which execute said functions identified with said protocol layer.

5. The method of claim 4 wherein said step of associating said measurements with said protocol layers includes mapping individual said measurements to specific said protocol layers which are mapped to specific said components, such that a particular said measurement that is determined to be undesirable is indicative of a lack of health for each said component and each said protocol layer to which said particular measurement is mapped.

6. The method of claim 5 wherein said step of ascertaining said health of said data network includes enabling a web-based user interface that displays health conditions of said components and said protocol layers mapped to said components on a basis of said measurements that are mapped to said protocol layers.

7. The method of claim 5 wherein said step of ascertaining said health of said data network includes enabling an automated correlation process which generates alerts of said lack of health in response to correlating measurements that are undesirable to components and protocol layers to which said measurements are mapped.

8. The method of claim 7 wherein said step of enabling said automated correlation process includes providing prioritization of said alerts on a basis of identifying a root cause of a problem that resulted in one or more said measurements being determined to be undesirable.

9. The method of claim 8 wherein said step of enabling said automated correlation process includes generating an alert for each said measurement that is determined to be undesirable and includes indicating the priority of said alerts in a representation of said alerts to a user.

10. The method of claim 9 wherein said step of enabling said automated correlation process includes representing said alerts as a web-based user interface that displays health conditions of said components and said protocol layers.

11. A method of monitoring a data network comprising the steps of:

mapping interconnections among components of said data network, thereby defining a physical topology;

mapping websites available via said data network to said components which support said websites, thereby defining logical topologies;

mapping functionalities of said data network to said components which enable said functionalities, including ranking said functionalities on a basis of functionality-to-functionality dependencies for implementation, thereby defining a layer hierarchy;

mapping each said component to each said functionality which said component is enabled to implement, thereby defining component-to-functionality mapping information;

mapping each of a plurality of test measurements to each said functionality for which said each test measurement is indicative of the operating state of said functionality as applied to one of said components, thereby defining measurement-to-functionality mapping information; and

enabling identifications of causes of network problems based on utilizing (1) said physical topology, (2) said logical topologies, (3) said layer hierarchy, (4) said component-to-functionality mapping information and (5) said measurement-to-functionality mapping information.

12. The method of claim 11 wherein said step of enabling identifications of causes includes providing a web-based user interface that enables navigation through information indicative of present operating states of said components, present operating states of said websites, present operating states of said functionalities as mapped to said components and present states of said measurements.

13. The method of claim 11 wherein said step of enabling identifications of causes includes providing an automated process of detecting said network problems and prioritizing said network problems on a basis of said layer hierarchy and said physical and logical topologies.

14. The method of claim 13 further comprising a step of generating alerts that are responsive to prioritization of said network problems.

15. The method of claim 11 further comprising a step of mapping transactions available via said websites to those websites through which said transactions are available.

16. A method of monitoring a data network comprising the steps of:

storing first mapping information that is representative of a physical topology of network components;

storing second mapping information that is representative of a logical topology of transaction-related network access points;

storing third mapping information that is representative of network protocol layers;

storing fourth mapping information that is representative of which of said network protocol layers are implemented using which of said network components;

storing fifth mapping information that is representative of which network tests provide measurements that are indicative of states of which protocol layers in which components; and

enabling detection of network problems using said first, second, third, fourth and fifth mapping information.

17. The method of claim 16 wherein said step of storing said second mapping information includes identifying websites as said transaction-related network access points and includes mapping transactions to said websites at which said transactions are available.

18. The method of claim 16 wherein said step of storing said third mapping information includes identifying a hierarchy of said network protocol layers on a basis of dependencies of said network protocol layers.

19. The method of claim 16 wherein said step of enabling detection includes providing a web-based user interface that allows navigation through said first, second, third, fourth and fifth mapping information.

20. The method of claim 16 wherein said step of enabling detection includes providing an automated process that prioritizes said network problems and generates alerts that are responsive to prioritization.