Distributed computer system with network and resource status monitoring

• US 5,109,486 A
• Filed: 01/06/1989
• Issued: 04/28/1992
• Est. Priority Date: 01/06/1989
• Status: Expired due to Term

• Current Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Seymour, Leslie G.
• Primary Examiner(s): Kriess, Kevin A.
• Application Number:
  US07/294,037
• Time in Patent Office: 1,208 Days
• Field of Search: 364/200 MS File, 364/900 MS File
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 15/17356 Indirect interconnection networks

Abstract

A requesting manager sends a message to its local configuration processor requesting notice of status changes in a general or particular, resource or node. The configuration manager establishes a record in its status monitoring file containing the information from the requesting process'"'"' message. The configuration manager receives messages: from remote configuration managers or local resource managers regarding resource status changes; and from its local network interface module regarding node changes. The configuration manager then compares these status change notifications with the records in its status monitoring file. If there is a match, the configuration manager sends a message to the requesting process reporting the status change. The status changes that are reported may be limited by the requesting process by specifying a particular status change, a particular resource, or other option.

Claims

1. In a distributed data processing system having a plurality of interconnected nodes with each node comprising a configuration manager, said system having a process and a resource at the same or separated nodes and a resource manager at the node containing said resource, said process communicating by means of messages, a method by which said process monitors the status of said resource comprising the steps of:

submitting a monitoring request message from said process to the configuration manager in the node containing said resource, said message requesting the status of said resource and comprising the name or identification number of said resource and a reply option directing one of an immediate reply and a synchronized reply;

establishing a record of said monitoring request in memory by means of said configuration manager;

receiving in said configuration manager a report from said resource manager of a status change of said resource; and

reporting said status change of said resource to said process by said configuration manager;

2. The method of claim 1 wherein said monitoring request further comprises a hold option directing said configuration manager to continue monitoring said resource after said status change of said resource has been reported.

3. The method of claim 1 wherein said monitoring request further comprises:

a connector option specifically identifying a single resource to be monitored; and

a code option to direct said configuration manager to only report a specific status change of said resource.

5. The method of claim 1 wherein said monitoring request further comprises a matching option requiring a resource definition for said status change report received by said configuration manager match said matching option before said status change is reported to said process.

6. The method of claim 1 wherein said monitoring request further comprises an originator option which requires that a status report received by said configuration manager be transmitted from a particular process.

7. The method of claim 1 further comprising the steps of canceling said monitoring request after reporting said status change to said process.

4. The method of claim 4 wherein said monitoring request further comprises an of option to direct said configuration manager to only report a status change of said resource where said status of said resource moves off of said specific status identified by said code option.

8. In a distributed data processing system having a plurality of interconnected nodes with each node comprising a configuration manager and a network interface module, said system having a process and a resource at the same or separate nodes, said process communicating by means of messages, a method by which said process monitors the status of said resource comprising the steps of:

submitting a monitoring request from said process to the configuration manager in the node containing said resource requesting the status of said resource, said request comprising the name or identification number of said resource and a reply option directing one of an immediate reply and a synchronized reply;

establishing a file in memory by means of said configuration manager receiving said monitoring request;

sending to said configuration manager a report from said network interface module of status change of a node;

searching said file to determine if said resource being monitored resided on said node; and

reporting said status change of said resource to said process if said resource resides on said node.

9. The method of claim 8 wherein said monitoring request further comprises a hold option directing said configuration manager to continue monitoring said resource after said status change of said resource has been reported.

10. The method of claim 8 wherein said monitoring request further comprises:

a connector option specifically identifying a single resource to be monitored; and

a code option to direct said configuration manager to only report a specific status change of said resource.

11. The method of claim 10 wherein said monitoring request further comprises an off option to direct said configuration manager to only report a status change of said resource where said status of said resource moves off of said specific status identified by said code option.

12. The method of claim 8 wherein said monitoring request further comprises a matching option requiring a resource definition for said status change report received by said configuration manager match said matching option before said status change is reported to said process.

13. The method of claim 8 wherein said monitoring request further comprises an originator option which requires that a status report received by said configuration manager be transmitted from a particular process.

14. The method of claim 8 further comprising the steps of cancelling said monitoring request after reporting said status change to said process.

15. In a distributed data processing system having a plurality of interconnected nodes with each node comprising a configuration manager and a network interface module, said system comprising a process, said process communicating by means of messages, a method by which said process monitors the status of a node comprising the steps of:

submitting a monitoring request to said configuration manager from said process requesting the status of said node;

establishing a record in memory by means of said configuration manager which received said monitoring request;

receiving a report from said network interface module of a status change of said node; and

reporting said status change of said node to said process by means of said configuration manager.

16. The method of claim 15 wherein said monitoring request comprises one of a name and an identification number of said node.

17. The method of claim 15 wherein said monitoring request comprises a code option to direct said configuration manager to only report a specific status change of said node.

18. The method of claim 17 wherein said monitoring request further comprises an off option to direct said configuration manager to only report a status change of said node where said status of said node moves off to said specific status identified by said code option.

19. The method of claim 15 wherein said monitoring request comprises a reply option directing one of an immediate reply and a synchronized reply.

20. The method of claim 15 wherein said monitoring request comprises a hold option directing said configuration manager to continue monitoring said node status after said status change of said node has been reported.

21. The method of claim 15 further comprising the step of canceling said monitoring request after reporting said status change to said process.

22. In a distributed data processing system having a plurality of interconnected nodes with each node comprising a configuration manager and a network interface module, said system having a process and a resource at the same or separate nodes, said process communicating by means of messages, a method by which said process monitors the status of said resource comprising the steps of:

sending a request message from said process to the node containing said resource, said message requesting said node to monitor said resource;

communicating said request message in said system through a logical communication ring if said request message contains a resource connector and said resource is remote from the node containing said process;

sending a message to said process indicating a bad request if said request message contains a resource connector and said resource is not a remote resource and said resource is not a valid local resource;

establishing a request record in memory does not contain a resource connector or if said resource is a valid local resource;

establishing a request record in memory for a node having a nodename if said request message is anode status request comprising said nodename;

deleting from memory the request record for said resource if said request message is a request to cancel monitoring of said resource; and

sending a reply to said process from said configuration manager if said request message specifies a reply.

23. The method of claim 22 wherein said step of establishing a request record for the node, at which said configuration manager is located, is performed by a service process comprising the steps of:

receiving said request message;

transmitting said request message in said logical communication ring if said message was not from said logical communication ring and is not from a remote node;

rejecting said request message as illegal if said message is not from said logical communication ring and is a message from a remote node;

rejecting said request message as illegal if said message is from a broken logical communication ring;

retransmitting said request message in said logical communication ring if said message is from said logical communication ring, is not from a broken logical communication ring, and a previous ring is lost due to node death;

inserting a host identification and a host name in said request message if said message is from said logical communication ring, is not from a broken logical communication ring and said previous ring is not lost due to node death, and said node has a matching nodename;

forwarding said request message in said logical communication ring if said message is from said logical communication ring, is not from a broken logical communication ring and said previous ring is not lost due to node death, and said logical communication ring has not been completed; and

establishing a request record, by means of said configuration manager, for each of said host identification contained in said message if said message is from said logical communication ring, is not from a broken logical communication ring and said previous ring is not lost due to node death, and said logical communication ring has been completed.

24. In a distributed data processing system having a plurality of interconnected nodes with each node comprising a configuration manager and a network interface module, said system having a process and a resource handles the reply to its request for the status of said resource comprising the steps of:

receiving a status message from the configuration manager at the node containing said resource;

exiting said process if said status message contains an illegal node status notification;

determining a new status rom said status message if said status message refers to a valid resource definition;

generating a node startup message if said new status indicates a first connection of a node after node startup;

circulating said status message in a logical communication ring of said system;

notify each process having a matching status request record on said process'"'"'s configuration manager;

storing said new status code in said matching status request record if said matching status request record is retained; and

updating a list of status request records if said status message indicates a connection or a disconnection of a node in said system;

25. The method of claim 24 wherein said step of updating a list of status request records comprises the steps of:

locating a status request record in a list of records stored in memory at the node containing said process;

marking said status request record as disconnected if said request is transparent and a node disconnection of said node containing said resource being monitored by said status request record is reported by said status message;

clearing a node disconnection mark from a status request record if said status message indicates a node reconnection of said node containing said resource being monitored by said status request record;

establishing a request record in said memory for a resource contained on a new node if said status message indicates a node with a new host identification is connected to said system and said resource is being otherwise monitored; and

removing said status request record from said memory if said status message indicates a disconnected node with a new nodename.

26. In a distributed data processing system having a plurality of interconnected nodes with each node comprising a configuration manager and a network interface module, said system having a process and a resource at the same or separate nodes, said process communicating by means of messages, a method by which a service process circulates a status message in said system by means of logical communication ring comprising the steps of:

receiving a status message from the configuration manager at the node containing said resource;

releasing said status message if said logical communication ring is broken or if said message is from a remote node and said message was in said logical communication ring and said logical communication ring has not been completed;

recirculating said status message if a previous ring was lost due to node death;

starting said status message in said logical communication ring if said status message has not been released or recirculated and said logical communication ring has not been completed;

inserting a host identification and host nodename and forwarding said status message in said logical communication ring if said status message has not been released or recirculated and said status message reports a new node connection;

forwarding said status message in said logical communication ring if said status message has not been released or recirculated and said status message does not report a new node connection;

notifying each process having a matching status request record and updating a list of status request records if said logical ring has been completed and there is a new node connection is said system;

notifying said system of a new master node status if said logical ring has been completed, a new node connection in said system is reported, and said status message does not contain a host identification; and

releasing said message following said steps of notifying each process or notifying said system of a new master node status.