Method and apparatus for distributed systems management

• US 7,430,594 B2
• Filed: 01/23/2002
• Issued: 09/30/2008
• Est. Priority Date: 01/26/2001
• Status: Expired due to Term

• Current Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Krupczak, Robert
• Primary Examiner(s): Vaughn, Jr.; William C.
• Assistant Examiner(s): Serrao; Ranodhi N
• Application Number:
  US10/055,426
• Publication Number:
  US 20020147764A1
• Time in Patent Office: 2,442 Days
• Field of Search: 709/202, 709/224, 709/223
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information

Abstract

A method and system for managing a distributed computing system relying on the discovery and analysis of dependency data. The implemented system and method utilizes an agent that can detect dependency configuration data stored on network management elements to determine the relationship of elements within the distributed system. Further included is a particular embodiment that displays a root managed device a root distance from a border and displays a non-root managed device having a dependency relationship with the root managed device a predetermined distance from the border that is greater than the root distance.

Claims

1. A computer-based method for communicating dependency data specifying dependency relationships between networked resources, including:

monitoring a first managed networked resource via a software agent executing on the first managed networked resource, wherein the software agent is managed by a software manager executing remotely from the first managed networked resource;

collecting, by the software agent executing on the first managed networked resource, configuration data describing the first managed networked resource;

extracting, by the software agent executing on the first managed networked resource, dependency data from the configuration data, the dependency data specifying either provider or consumer dependency relationships between the first managed networked resource and one or more other managed networked resources, wherein said provider dependency relationship indicates that a first problem at the first managed networked resource will propagate to the one or more other managed networked resources, and said consumer dependency relationship indicates that a second problem at the one or more other managed networked resources will propagate to the first managed networked resource;

generating, at the first managed networked resource, a table that includes the extracted dependency data, wherein the table is stored separate from other configuration data associated with the first managed networked resource that has been collected by the software agent;

offering access to the extracted dependency data in the table generated at the first managed networked resource, the access being offered via a dependency interface of the software agent executing on the first managed networked resource, the dependency interface being an interface for a distributed systems management protocol; and

communicating the dependency data from the software agent to the software manager.

2. The method of claim 1, further including:

collecting dependency data from a plurality of networked resources including the first managed networked resource; and

storing the dependency data in a repository centralized within a distributed systems management environment, wherein the centralized repository is stored in the software manager of the distributed systems management environment separately from other configuration data associated with the plurality of networked resources.

3. The method of claim 1, where the distributed systems management protocol is an open standard.

4. The method of claim 3, wherein offering access includes the software manager communicating across a network with the software agent using the distributed systems management protocol.

5. The method of claim 4, wherein the software agent communicates with the software manager using the distributed systems management protocol to raise a trap based on the dependency data included in the table.

6. The method of claim 1, where the distributed systems management protocol is SNMP.

7. A computer-based method for distributed systems management, including:

monitoring a first managed network device with a first software agent executing on the first managed network device, wherein the software agent is managed by a software manager executing remotely from the first managed network device;

collecting, by the software agent executing on the first network device, configuration data describing the first managed network device;

gathering, by the first software agent executing on the first managed network device, dependency data describing either a provider or a consumer dependency relationship between the first managed network device and one or more other network devices, wherein said provider dependency relationship indicates that a first problem at the first managed network device will propagate to the one or more other network devices, and said consumer dependency relationship indicates that a second problem at the one or more other network devices will propagate to the first managed network device;

communicating, by the first software agent executing on the first managed network device, the dependency data gathered by the first software agent to the software manager;

processing, by the software manager, the gathered dependency data obtained from the first software agent to determine whether either the provider or the consumer dependency relationship exists between the first managed network—

device and a second network device; and

initiating, by the software manager, a second software agent if either the provider or the consumer dependency relationship exists between the first managed network device and the second network device, wherein the second software agent executes on and monitors the second network device.

8. The method of claim 7, further comprising:

adding the second software agent to an active agent list by the software manager, the active agent list maintained at the software manager; and

classifying, by the software manager, the second network device as a second managed network device managed by the software manager.

9. The method of claim 7, further comprising:

determining, by the software manager, whether the second network device is a device that is managed by the software manager;

initiating, by the software manager, a second software agent on the second network device if either the provider or the consumer dependency relationship exists between the first managed network device and a second network device and if the second network device is a device that is not managed by the software manager.

10. The method of claim 9, wherein the determining whether the second network device is a device managed by the software manager comprises determining whether the second software agent executing on the second network device is included in an active agent list maintained by the software manager.

11. A computer-based method for collecting dependency data specifying dependency relationships between networked resources, the method including:

monitoring a plurality of managed networked resources via a software agent executing on each of the managed networked resources, wherein the plurality of software agents are managed by a software manager executing remotely from the plurality of managed networked resources;

gathering, by the plurality of software agents executing on the plurality of managed networked resources, configuration data describing the plurality of networked resources;

extracting, by the plurality of software agents, dependency data from the gathered configuration data, the dependency data including data specifying either provider or consumer dependency relationships associated with the plurality of managed networked resources, wherein said provider dependency relationship indicates that a first problem at a first managed networked resource will propagate to a second networked resource, and said consumer dependency relationship indicates that a second problem at the second networked resource will propagate to the first managed networked resource;

communicating the dependency data extracted by the plurality of software agents from the plurality of software agents to the software manager;

adding at least a portion of the dependency data extracted by the plurality of software agents to a central repository managed by the software manager, wherein the portion of the dependency data added to the central repository is stored in the central repository separately from other configuration data;

processing, by the software manager, the extracted dependency data obtained from the plurality of software agents to determine whether either the provider or the consumer dependency relationships exist between at least one of the plurality of managed networked resources and one or more additional networked resources not included in the plurality of managed networked resources; and

initiating, by the software manager, management of the one or more additional networked resources not included in the plurality of managed networked resources if either the provider or the consumer dependency relationships exist between at least one of the plurality of managed networked resources and the one or more additional networked resources.

12. The method of claim 11, wherein the software manager offers a client application access to the central repository, the access offered using a distributed systems management protocol.

13. The method of claim 12, wherein the distributed systems management protocol is SNMP.

14. The method of claim 11, wherein initiating, by the software manager, management of the one or more additional networked resources further comprising:

initiating, by the software manager, one or more additional software agents at the one or more additional networked resources if either the provider or the consumer dependency relationships exist between at least one of the plurality of managed networked resources and the one or more additional networked resources, wherein each of the one or more additional software agents execute on and monitor the corresponding one or more additional networked resources;

adding the one or more additional software agents to an active agent list by the software manager, the active agent list maintained at the software manager; and

classifying, by the software manager, the one or more additional networked resources as one or more additional managed networked resources managed by the software manager.

15. An article comprising a machine-readable storage medium that stores executable instructions to communicate dependency data specifying dependency relationships between networked resources, the instructions causing a machine to:

monitor a first managed networked resource via a software agent executing on the first managed networked resource, wherein the software agent is managed by a software manager executing remotely from the first managed networked resource;

collect, by the software agent executing on the first managed networked resource, configuration data describing the first managed networked resource;

extract, by the software agent, dependency data from the configuration data, the dependency data specifying either provider or consumer dependency relationships between the first managed networked resource and the one or more other managed networked resources, wherein said provider dependency relationship indicates that a first problem at the first managed networked resource will propagate to the one or more other managed networked resources, and said consumer dependency relationship indicates that a second problem at the one or more other managed networked resources will propagate to the first managed networked resource;

generate, at the first managed networked resource, a table that includes the extracted dependency data, wherein the table is stored separate from other configuration data associated with the first managed networked resource that has been collected by the software agent;

offer access to the extracted dependency data in the table generated at the first managed networked resource, the access being offered via a dependency interface of the software agent executing on the first managed networked resource, the dependency interface being an interface for a distributed systems management protocol; and

communicate the dependency data from the software agent to the software manager.

16. The article of claim 15, further including instructions causing the machine to:

collect dependency data from a plurality of networked resources including the first networked resource; and

store the dependency data in a repository centralized within the software manager of a distributed systems management environment, wherein the centralized repository is stored in the software manager of the distributed systems management environment separately from other configuration data associated with the plurality of networked resources.

17. An article comprising a machine-readable storage medium that stores executable instructions to manage distributed systems, the instructions causing a machine to:

monitor a first managed network device with a first software agent executing on the first managed network device, wherein the software agent is managed by a software manager executing remotely from the first managed network device;

collect, by the software agent executing on the first managed network device, configuration data describing the first managed network device;

gather, by the first software agent, dependency data describing either a provider or a consumer dependency relationship between the first managed network device and one or more other network devices, wherein said provider dependency relationship indicates that a first problem at the first managed network device will propagate to the one or more network devices, and said consumer dependency relationship indicates that a second problem at the one or more network devices will propagate to the first managed network device;

communicate, by the first software agent executing on the first managed network device, the dependency data gathered by the first software agent to the software manager;

process, by the software manager, the gathered dependency data obtained from the first software agent to determine whether either the provider or the consumer dependency relationship exists between the first managed network device and a second network device; and

initiate, by the software manager, a second software agent if either the provider or the consumer dependency relationship exists between the first managed network device and a the second network device, wherein the second software agent executes on and monitors the second network device.