|Publication number||US5511191 A|
|Application number||US 08/447,835|
|Publication date||Apr 23, 1996|
|Filing date||May 23, 1995|
|Priority date||Feb 5, 1993|
|Also published as||DE69410304D1, DE69410304T2, EP0609990A2, EP0609990A3, EP0609990B1|
|Publication number||08447835, 447835, US 5511191 A, US 5511191A, US-A-5511191, US5511191 A, US5511191A|
|Inventors||Marcus J. de Leeuw van Weenen, Kevin Glynn, Gareth I. Jenkins|
|Original Assignee||International Computers Limited|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (15), Non-Patent Citations (2), Referenced by (36), Classifications (19), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a continuation of application Ser. No. 189,042, filed Jan. 31, 1994, now abandoned.
This invention relates to data processing systems. More specifically, the invention is concerned with management of a data processing system comprising a large number of managed objects. The invention is particularly, although not exclusively, applicable to a distributed data processing network comprising a number of individual end-systems, each of which comprises a number of managed objects.
By a managed object is meant an object that is required to be managed by an operator or system administrator. Such managed objects may include, for example, individual processing elements, file systems, communications facilities, database services, and so on.
A problem with such a system is that the operator's view of the system can be very complex, and the operator requires a considerable degree of skill to monitor and to react to events in the system.
The object of the present invention is to provide a means for reducing such problems.
According to the invention there is provided a data processing system comprising:
(a) a plurality of managed objects,
(b) means for monitoring the status of the managed objects,
(c) means for defining a plurality of composite managed objects each including a plurality of said managed objects and/or composite managed objects as members, and
(d) means for setting the status of said composite managed objects by aggregating the status of all the members of each composite managed object.
It will be seen that, by aggregating the status of individual objects, the operator's view of the system is simplified, and hence the task of managing the system is made easier.
FIG. 1 is a schematic diagram of a data processing system including a number of managed objects and composite managed objects.
FIG. 2 is a block diagram showing the mechanism within the system for collecting and aggregating the status of managed objects.
FIG. 3 is a flow chart showing the status aggregation mechanism in more detail.
One data processing system in accordance with the invention will now be described by way of example with reference to the accompanying drawings.
Referring to FIG. 1, the data processing system comprises the following managed objects: data processing elements 10, a file system 11, a communications facility 12, a power supply 13, database services 14 and databases 15.
In this example, each of these managed objects has associated with it an operational status and an administrative status. However, it should be noted that in other embodiments of the invention, other status types may be defined.
The operational status has one of the following values: unknown, disabled, no heartbeat, no report, no control, enabled, busy, active. The administrative status has one of the following values: unknown, locked, shutting down, unlocked.
These managed objects are combined, from the operator's point of view, into composite managed objects. Thus, the processors 10, file system 11, communications facility 12 and power supply 13 are combined to form a composite managed object referred to as the host computer 16. The database services 14 and databases 15 are combined to form a set of composite managed objects referred to as database installations 17. The host computer 16 and database installations 17 are in turn, combined to form a composite managed object referred to as the database server 18, which represents the operator's top-level view of the system.
Each composite managed object has operational and administrative status values which are formed, as will be described, by aggregation of the status values of its members, ie the managed objects (or composite managed objects) from which it is formed.
Referring now to FIG. 2, this shows how the status values of the managed objects are collected, aggregated and displayed.
In this figure, the managed objects 10-15 of FIG. 1 are represented as a set of managed objects 20. The status values of these objects are collected by a status collection function 21, and are recorded in a status database 22. The status collection function 21 uses a configuration file 23 which holds the identities of all the managed objects in the system.
When the system is started up, the status collection function 21 polls all the managed objects 20 identified in the configuration file, and obtains their current status values. These status values are recorded in the status database 22. Subsequently, whenever one of the managed objects 20 changes its status, it sends a change of status message to the status collection function, which then updates the status database accordingly.
The status database 22 also holds status values for the composite managed objects 16-18. A status aggregation function 24 calculates the status values for these composite managed objects, according to a set of aggregation rules held in a rules database 25. This status aggregation is performed whenever the status collection function updates the status of any member of a composite managed object.
A status monitoring and display function 26 accesses the status database, in response to commands from the system operator, and displays the status of the managed objects or composite managed objects. The system operator can choose to view the status at any selected level: for example, the operator will normally view only the status of the highest-level composite managed object (ie the database server 18 in FIG. 1), and will selectively view the status of the lower-level objects only if more detailed information is required about the system.
The aggregation rules, in this example, consist of a set of threshold values for each composite managed object. Each set contains threshold values for the unknown, disabled, no heartbeat, no report, no control, enabled, busy and active operational states, and for the unknown, locked, shutting down and unlocked administrative states. Each composite managed object has its own separate set of threshold values associated with it.
Referring to FIG. 3, this shows the operation of the status aggregation function 24 in more detail. As mentioned above, this function 24 is called whenever the status of a member of a composite managed object is changed.
The status aggregation function first accesses the rules database 25 to obtain the threshold values for the composite managed object in question.
A set of status counts, one corresponding to each possible status value, is created and initialised to zero.
The function then accesses the configuration file 23 to obtain the identities of the members of that composite managed object.
The status of each member of the composite managed object is then retrieved from the status database, and the appropriate status counts are incremented. For example, if the member has operational status "busy", then the "busy" status count is incremented by one.
Each status count is then converted into a percentage value, by dividing it by the total number of members in the composite object and multiplying the result by 100.
The operational status of the composite managed object is then set by means of the procedure as defined by the following pseudo-code:
______________________________________/* set operational status */if disabled count exceeds disabled threshold set operation status to disabledelse if no-- heartbeat count plus disabled count exceeds no-- heartbeat threshold set operational status to no-- heartbeatelse if no-- report count plus no-- heartbeat count plus disabled count exceeds no-- report threshold set operational status to no-- reportelse if no-- control count plus no-- report count plus no-- heartbeat count plus disabled count exceeds no-- control threshold set operational status to no-- controlelse if enabled count plus no-- control count plus no-- report count plus no-- heartbeat count plus disabled count exceeds enabled threshold set operational status to enabledelse if busy count exceeds busy threshold set operational status to busyelse if active count exceeds active threshold set operational status to activeelse set operational status to unknown______________________________________
Thus, it can be seen that the possible status values are considered in a fixed order of precedence. At each step, if the percentage of members with a particular status exceeds the relevant threshold value, the composite managed object is set to that status. If the threshold value is not exceeded for the disabled, no heartbeat, no report or no control status, the percentage of members with that status is carried forward and added to next status percentage before comparison with the threshold.
The administrative status of the composite managed object is then set by means of the procedure as defined by the following pseudo-code.
______________________________________/* set administrative status */If locked count exceeds locked threshold set status to locked;Else if shutting-- down count exceeds shutting-- downthreshold set status to shutting-- downElse if unlocked count exceeds unlocked threshold set status to unlockedElse set status to unknown;______________________________________
Finally, the status database 22 is updated with the new status values for the composite managed object.
By varying the threshold values, different aggregation rules can be specified, so that it is possible to vary the ay in which the status values are aggregated according to the user's requirements or preferences. Other aggregation functions may also be employed, and, if desired, a different aggregation function may be used for each managed object.
It should be noted that the data processing system described above may be linked to other data processing systems (not shown) to form a distributed data processing network. The status aggregation technique described above can be used to make up composite managed objects from managed objects that are physically situated anywhere within such a distributed network.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4644532 *||Jun 10, 1985||Feb 17, 1987||International Business Machines Corporation||Automatic update of topology in a hybrid network|
|US4849879 *||Sep 2, 1986||Jul 18, 1989||Digital Equipment Corp||Data processor performance advisor|
|US4918602 *||Jul 15, 1987||Apr 17, 1990||Computer Associates International, Inc.||Data processing system and method|
|US5001628 *||Sep 1, 1989||Mar 19, 1991||International Business Machines Corporation||Single system image uniquely defining an environment for each user in a data processing system|
|US5007017 *||Apr 6, 1987||Apr 9, 1991||Hitachi, Ltd.||Method and apparatus for data communication through composite network|
|US5128878 *||Nov 28, 1990||Jul 7, 1992||Micron Technology, Inc.||Remote plotting of integrated circuit layout in a network computer-aided design system|
|US5163131 *||Sep 8, 1989||Nov 10, 1992||Auspex Systems, Inc.||Parallel i/o network file server architecture|
|US5218697 *||Apr 18, 1990||Jun 8, 1993||Microsoft Corporation||Method and system for networking computers having varying file architectures|
|US5220596 *||May 30, 1991||Jun 15, 1993||Rolm Systems||Method and apparatus for propagating a network profile|
|US5287453 *||Sep 18, 1990||Feb 15, 1994||Bull Hn Information Systems, Inc.||Fast remote file access facility for distributing file access requests in a closely coupled computer system|
|US5317568 *||Apr 11, 1991||May 31, 1994||Galileo International Partnership||Method and apparatus for managing and facilitating communications in a distributed hetergeneous network|
|US5323393 *||Nov 18, 1992||Jun 21, 1994||Canon Information Systems, Inc.||Method and apparatus for obtaining and for controlling the status of a networked peripheral|
|EP0259224A2 *||Aug 31, 1987||Mar 9, 1988||Digital Equipment Corporation||Method for performance evaluation of a data processor system|
|EP0474059A2 *||Aug 21, 1991||Mar 11, 1992||International Business Machines Corporation||User interface for operating a computer processor|
|WO1992005485A2 *||Sep 17, 1991||Apr 2, 1992||Cabletron Systems, Inc.||Network management system using model-based intelligence|
|1||Joyce et al., "Monitoring Distributed Systems", ACM Transactions On Computer Systems, vol. 5, No. 2, May, 1987, pp. 121-150.|
|2||*||Joyce et al., Monitoring Distributed Systems , ACM Transactions On Computer Systems, vol. 5, No. 2, May, 1987, pp. 121 150.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US5668944 *||Sep 6, 1994||Sep 16, 1997||International Business Machines Corporation||Method and system for providing performance diagnosis of a computer system|
|US5768614 *||Feb 16, 1996||Jun 16, 1998||Fujitsu Limited||Monitored state display unit for monitoring state change of various events occurring on communication network|
|US5815652 *||May 30, 1996||Sep 29, 1998||Hitachi, Ltd.||Computer management system|
|US5953715 *||Nov 3, 1997||Sep 14, 1999||International Business Machines Corporation||Utilizing pseudotables as a method and mechanism providing database monitor information|
|US5963961 *||Nov 25, 1997||Oct 5, 1999||International Business Machines Corporation||Database reconstruction using embedded database backup codes|
|US6044476 *||Aug 31, 1998||Mar 28, 2000||Hitachi, Ltd.||Computer management system|
|US6393472||Dec 9, 1998||May 21, 2002||At&T Corp.||Automatic aggregation of network management information in spatial, temporal and functional forms|
|US6513047 *||Sep 4, 1997||Jan 28, 2003||Sun Microsystems, Inc.||Management of user-definable databases|
|US6862736 *||Feb 13, 2002||Mar 1, 2005||Microsoft Corporation||Object manager for common information model|
|US7089451||Jan 30, 2001||Aug 8, 2006||Hitachi, Ltd.||Computer management system|
|US7203864 *||Jun 25, 2004||Apr 10, 2007||Hewlett-Packard Development Company, L.P.||Method and system for clustering computers into peer groups and comparing individual computers to their peers|
|US7337155 *||Mar 6, 2003||Feb 26, 2008||Fuji Xerox Co., Ltd.||Communication analysis apparatus|
|US7380249||Mar 1, 2005||May 27, 2008||Microsoft Corporation||Object manager for common information model|
|US7383552||Dec 3, 2004||Jun 3, 2008||Microsoft Corporation||Object manager for common information model|
|US7584382 *||Aug 13, 2004||Sep 1, 2009||Microsoft Corporation||Method and system for troubleshooting a misconfiguration of a computer system based on configurations of other computer systems|
|US7856100||Dec 19, 2005||Dec 21, 2010||Microsoft Corporation||Privacy-preserving data aggregation using homomorphic encryption|
|US7890807||Jun 13, 2007||Feb 15, 2011||Microsoft Corporation||Method and system for troubleshooting a misconfiguration of a computer system based on configurations of other computer systems|
|US7962571||Mar 7, 2008||Jun 14, 2011||Microsoft Corporation||Method and system for collecting information from computer systems based on a trusted relationship|
|US7987160 *||Jan 30, 2006||Jul 26, 2011||Microsoft Corporation||Status tool to expose metadata read and write queues|
|US8375007||Jun 21, 2011||Feb 12, 2013||Microsoft Corporation||Status tool to expose metadata read and write queues|
|US8677319||Jul 25, 2006||Mar 18, 2014||International Business Machines Corporation||Computer method and system for composite state management of software change requests|
|US9342696||Aug 31, 2011||May 17, 2016||International Business Machines Corporation||Attesting use of an interactive component during a boot process|
|US9489232||Sep 20, 2011||Nov 8, 2016||International Business Machines Corporation||Techniques for attesting data processing systems|
|US20020107872 *||Feb 13, 2002||Aug 8, 2002||Irena Hudis||Object manager for common information model|
|US20040083389 *||Mar 6, 2003||Apr 29, 2004||Fuji Xerox Co., Ltd.||Communication analysis apparatus|
|US20050188268 *||Aug 13, 2004||Aug 25, 2005||Microsoft Corporation||Method and system for troubleshooting a misconfiguration of a computer system based on configurations of other computer systems|
|US20050289071 *||Jun 25, 2004||Dec 29, 2005||Goin Todd M||Method and system for clustering computers into peer groups and comparing individual computers to their peers|
|US20060011292 *||Sep 19, 2005||Jan 19, 2006||Lee Sang S||Apparatus and method for manufacturing liquid crystal display devices, method for using the apparatus, and device produced by the method|
|US20070140479 *||Dec 19, 2005||Jun 21, 2007||Microsoft Corporation||Privacy-preserving data aggregation using homomorphic encryption|
|US20070179973 *||Jan 30, 2006||Aug 2, 2007||Microsoft Corporation||Status tool to expose metadata read and write queues|
|US20070208582 *||Mar 2, 2006||Sep 6, 2007||International Business Machines Corporation||Method, system, and program product for providing an aggregated view|
|US20070300103 *||Jun 13, 2007||Dec 27, 2007||Microsoft Corporation|
|US20080046876 *||Jul 25, 2006||Feb 21, 2008||Clemm Geoffrey M||Computer Method and System for Composite State Management of Software Change Requests|
|US20080313632 *||Jun 13, 2007||Dec 18, 2008||Apurva Kumar||Methods, devices, and products for providing access to system-administration functions of a computer or related resources|
|WO1997050023A1 *||Jun 24, 1997||Dec 31, 1997||Dsc Communications A/S||A method and a system for detecting and indicating the states of a process system|
|WO2012065774A1 *||Sep 20, 2011||May 24, 2012||International Business Machines Corporation||A method for attesting a plurality of data processing systems|
|U.S. Classification||707/822, 714/E11.179, 714/E11.189, 714/E11.202, 707/999.1, 707/999.2, 714/47.2|
|International Classification||G06F11/34, G06F11/32, G06F11/30|
|Cooperative Classification||G06F11/3082, G06F11/3055, G06F11/34, G06F11/3495, G06F2201/81, G06F11/32|
|European Classification||G06F11/30, G06F11/34T12, G06F11/34|
|Sep 23, 1999||FPAY||Fee payment|
Year of fee payment: 4
|Nov 12, 2003||REMI||Maintenance fee reminder mailed|
|Apr 23, 2004||LAPS||Lapse for failure to pay maintenance fees|
|Jun 22, 2004||FP||Expired due to failure to pay maintenance fee|
Effective date: 20040423