Distributed service subsystem protocol for distributed network management

• US 6,119,159 A
• Filed: 09/09/1997
• Issued: 09/12/2000
• Est. Priority Date: 09/09/1997
• Status: Expired due to Term

• Current Assignee: Teradata US, Inc. (Teradata Corporation)
• Original Assignee: NCR Corporation
• Inventors: Bruno, Gregory Du Vall, Muller, P. Keith, Chow, Kit Man, Meyer, Michael William, Tseng, Weinan William
• Primary Examiner(s): Rinehart, Mark H.
• Application Number:
  US08/926,147
• Time in Patent Office: 1,099 Days
• Field of Search: 709/224, 709/226, 709/223, 709/201, 709/220, 370/254, 370/257, 370/463
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3058 Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations thermal management in cooling arrangements of a computing system G06F1/206
• CPC Class Codes: H04L 41/042 comprising distributed management centres cooperatively managing the network

Abstract

A distributed service subsystem comprises one or more cabinets containing one or more computer systems, one or more administration consoles for controlling the computer systems in the cabinets, and a network interconnecting the administration consoles and the cabinets. Each of the cabinets includes a cabinet module interface controller (CMIC) coupled to and controlling one or more chassis management boards (CMBs). The CMBs are each adapted to communicate with one or more managed components in the cabinet through a component specific interface.

Claims

1. A method of distributing service subsystem messages in a network, comprising:

(a) controlling one or more Complexes, residing in one or more of the Cabinets containing one or mor Managed Components of one or more Computer Systems, from one or more Administration Consoles interconnected with the Cabinets by a Systems Management Network;

(1) each Complex being a collection of related Managed Components and a set of the Cabinets being grouped into a combination of one or more interconnected Complexes,

(2) each Cabinet including a Cabinet Module Interface Controller (CMIC) coupled to one or more Chassis Management Boards (CMBs), wherein the CMIC and CMBs each comprise embedded controllers that are configured in a hierarchy within the Cabinet,

(3) each CMB being separate from but adapted to communicate with one or more of the Managed Components through a specific interface to the Managed Component, thereby precluding the need for the Managed Components themselves to adapt to the Distributed Service Subsystem, and

(4) each CMIC offloading management functions from the Administration Console coupled thereto by the Systems Management Network, and isolating the CMBs and Managed Components of a Cabinet from the rest of the Distributed Service Subsystem;

(b) formatting a message in one or more of the Administration Consoles, wherein the message includes a header having one or more fields selected from a group comprising a version number, offset, event type, length of data portion of message, complex identifier, complex type, sequence number, source IP address, timestamp, cabinet number, system number, and severity level; and

(c) transmitting the formatted message from the Administration Console to one or more of the CMICs.

2. The method of claim 1 above, further comprising:

(d) formatting a message in one or more of the CMICs, wherein the message includes a header having one or more fields selected from a group comprising a version number, offset, event type, length of data portion of message, complex identifier, complex type, sequence number, source IP address, timestamp, cabinet number, system number, and severity level; and

(e) transmitting the formatted message from the CMIC to one or more of the Administration Consoles.

3. The method of claim 1 above, further comprising the step of offloading management functions required of the Administration Console to the CMICs.

4. The method of claim 1 above, wherein the offloading step further comprises the step of offloading and distributing management functions required of the Administration Console to the CMICs and CMBs by issuing management commands on the Systems Management Network to the CMICs.

5. The method of claim 1 above, further comprising the step of receiving command information from the Administration Console to control the Managed Components in the Cabinet.

6. The method of claim 5 above, further comprising the step of converting the command information into a component specific language, and then routing the command information to the CMBs specified by the command information.

7. The method of claim 1 above, wherein the event type identifies one or more messages selected from a group comprising a critical event message, informational event message, command event message, command completion event message, acknowledgement message, and heartbeat message.

8. The method of claim 1 above, wherein the Administration Consoles and CMICs can be either sending agents or listening agents.

9. The method of claim 8 above, further comprising the step of routing command information to one or more listening agents using one or more communications methods selected from a group comprising pointcast, broadcast, and multicast communications.

10. The method of claim 8 above, further comprising the step of distributing a message from the sending agent to all interested listening agents without identifying the listening agents.

11. The method of claim 8 above, further comprising the step of alerting the listening agents whenever an important message is received.

12. The method of claim 8 above, further comprising the step of controlling system management by placement of the listening agents.

13. The method of claim 12 above, further comprising the step of placing the listening agents onto dedicated processing nodes connected to the network, thereby isolating resource-intensive features.

14. A Distributed Service Subsystem for managing one or more Computer Systems, comprising:

(a) one or more Complexes, residing in one or more of the Cabinets containing one or more Managed Components of one or more Computer Systems, from one or more Administration Consoles interconnected with the Cabinets by a Systems Management Network,

(1) each Complex being a collection of related Managed Components and a set of the Cabinets being grouped into a combination of one or more interconnected Complexes,

(2) each Cabinet including a Cabinet Module Interface Controller (CMIC) coupled to one or more Chassis Management Boards (CMBs), wherein the CMIC and CMBs each comprise embedded controllers that are configured in a hierarchy within the Cabinet,

(3) each CMB being separate from but adapted to communicate with one or more of the Managed Components through a specific interface to the Managed Component, thereby precluding the need for the Managed Components themselves to adapt to the Distributed Service Subsystem, and

(4) each CMIC offloading management functions from the Administration Console coupled thereto by the Systems Management Network, and isolating the CMBs and Managed Components of a Cabinet from the rest of the Distributed Service Subsystem;

(b) wherein the Administration Consoles and the CMICs each comprise agents for formatting a message including a header having one or more fields selected from a group comprising a version number, offset, event type, length, complex identifier, complex type, sequence number, source IP address, timestamp, cabinet number, system number, severity, and data portion, and for transmitting the formatted message to another agent connected to the network.