Method and apparatus for exchanging configuration information between nodes operating in a master-slave configuration

• US 7,353,259 B1
• Filed: 04/22/2002
• Issued: 04/01/2008
• Est. Priority Date: 03/07/2002
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Johnson, Craig A., Teske, Donald W., Bakke, Mark A., Muchow, James D.
• Primary Examiner(s): Vaughn; William
• Assistant Examiner(s): SHAW, PELING ANDY
• Application Number:
  US10/128,657
• Time in Patent Office: 2,171 Days
• Field of Search: 709/208, 709/209, 709/223, 709/224, 714/4, 714 11- 13
• US Class Current: 709/208
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0724 in a multiprocessor or a multi-core unit multiprocessors per se G06F15/80
• CPC Class Codes: G06F 11/0757 by exceeding a time limit, i.e. time-out, e.g. watchdogs
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality
• CPC Class Codes: G06F 11/202 where processing functionality is redundant redundant communication control functionality G06F11/2005, redundant storage control functionality G06F11/2089
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 2209/505 Clust
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/5061 Partitioning or combining of resources
• CPC Class Codes: H04L 41/0266 using meta-data, objects or commands for formatting management information, e.g. using eXtensible markup language [XML]
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/0869 Validating the configuration within one network element
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A node, within a networked computer system, is capable of supporting communications with other nodes relating to operating multiple application instances in a master-slave configuration. Each node periodically generates and sends a Heartbeat message that indicates the operational status and configuration information for one or more application instances being managed by the node. When a node receives a Heartbeat message from a remote node, it determines whether new configuration information should be obtained for each of the application instances the node is managing, and establishes a connection with a remote node that can access the new configuration information. The connection is an HTTP connection, in one embodiment. The node then requests and receives that new configuration information from the remote node. In one embodiment, the new configuration information is received in an XML format.

Claims

1. A method for maintaining configuration information at a first node, wherein the first node is connected by one or more networks to one or more other nodes which operate in a master-slave configuration, the method comprising:

determining with a multiple instance heartbeat message including multiple configuration identifier fields whether configuration information for an application instance being managed by the first node is current, wherein the application instance is operating on the first node in at least one of a master and a slave configuration;

if the configuration information at the first node is not current, establishing a Hyper-Text Transfer Protocol (HTTP) connection with a remote node of the one or more other nodes from which updated configuration information can be obtained;

requesting the updated configuration information from the remote node; and

receiving the updated configuration information, the updated configuration information including a configuration identifier and providing data for operation of the application instance.

2. The method as claimed in claim 1, wherein determining whether the configuration information is current comprises:

receiving the multiple instance heartbeat message, which includes a configuration identifier field associated with the application instance;

comparing a first configuration identifier within the configuration identifier field with a stored configuration identifier that identifies current configuration information being used by the first node for the application instance; and

if the first configuration identifier identifies a different version of configuration information than the stored configuration identifier, determining that the configuration information is not current.

3. The method as claimed in claim 1, wherein determining whether the configuration information is current comprises:

receiving the multiple instance heartbeat message, wherein each of the multiple configuration identifier fields is associated with one of multiple application instances being managed by the first node in the master-slave configuration;

comparing a first configuration identifier within one of the multiple configuration identifier fields with a stored configuration identifier that identifies current configuration information being used by the first node for the application instance; and

if the first configuration identifier identifies a different version of configuration information than the stored configuration identifier, determining that the configuration information is not current.

4. The method as claimed in claim 1, wherein establishing the HTTP connection comprises establishing an HTTP over Secure Sockets Layer (SSL) connection.

5. The method as claimed in claim 1, wherein establishing the HTTP connection comprises establishing an HTTP over Transport Layer Security (TLS) connection.

6. The method as claimed in claim 1, wherein receiving the updated configuration information comprises receiving the updated configuration information in a self-describing structured text format.

7. The method as claimed in claim 6, wherein receiving the updated configuration information comprises receiving the updated configuration information in an Extensible Markup Language (XML) format.

8. The method as claimed in claim 2, further comprising:

storing the updated configuration information; and

changing the stored configuration identifier for the application instance to the first configuration identifier.

9. A node within a computer system which operates in a master-slave configuration, the node comprising:

at least one processor that determines with a multiple instance heartbeat message including multiple configuration identifier fields whether configuration information for an application instance being managed by the node is current, and if not, establishes a Hyper-Text Transfer Protocol (HTTP) connection with a remote node from which updated configuration information can be obtained, requests the updated configuration information from the remote node, and receives the updated configuration information, the updated configuration information including a configuration identifier and providing data for operation of the application instance; and

at least one interface to at least one external network, which supports establishment of the connection with the remote node.

10. The node as claimed in claim 9, wherein the at least one processor establishes the HTTP connection by establishing an HTTP over Secure Sockets Layer (SSL) connection.

11. The node as claimed in claim 9, wherein the at least one processor establishes the HTTP connection by establishing an HTTP over Transport Layer Security (TLS) connection.

12. The node as claimed in claim 9, wherein the at least one processor receives the updated configuration information by receiving the updated configuration information in a self-describing structured text format.

13. The node as claimed in claim 12, wherein the at least one processor receives the updated configuration information by receiving the updated configuration information in an Extensible Markup Language (XML) format.

14. A computer readable medium having computer executable instructions stored thereon to maintain configuration information by a first node, wherein the first node is connected by one or more networks to one or more other nodes which operate in a master-slave configuration, the instructions which, when executed by a computer, cause the computer to:

determine with a multiple instance heartbeat message including multiple configuration identifier fields whether configuration information for an application instance being managed by the node is current, wherein the application instance is operating on the first node in at least one of a master and a slave configuration;

if not, establish a Hyper-Text Transfer Protocol (HTTP) connection with a remote node from which updated configuration information can be obtained;

request the updated configuration information from the remote node; and

receive the updated configuration information, the updated configuration information including a configuration identifier and providing data for operation of the application instance.

15. The computer readable medium as claimed in claim 14, wherein establishing the HTTP connection comprises establishing an HTTP over Secure Sockets Layer (SSL) connection.

16. The computer readable medium as claimed in claim 14, wherein establishing the HTTP connection comprises establishing an HTTP over Transport Layer Security (TLS) connection.

17. The computer readable medium as claimed in claim 14, wherein receiving the updated configuration information comprises receiving the updated configuration information in a self-describing structured text format.

18. The computer readable medium as claimed in claim 17, wherein receiving the updated configuration information comprises receiving the updated configuration information in an Extensible Markup Language (XML) format.

19. A node within a computer system which operates in a master-slave configuration, the node comprising:

means for processing, which determines with a multiple instance heartbeat message including multiple configuration identifier fields whether configuration information for an application instance being managed by the node is current, and if not, establishes a Hyper-Text Transfer Protocol (HTTP) connection with a remote node from which updated configuration information can be obtained, requests the updated configuration information from the remote node, and receives the updated configuration information, the updated configuration information including a configuration identifier and providing data for operation of the application instance; and

means for interfacing with at least one external network, which supports establishment of the connection with the remote node.

20. The node as claimed in claim 19, wherein the means for processing establishes the HTTP connection by establishing an HTTP over Secure Sockets Layer (SSL) connection.

21. The node as claimed in claim 19, wherein the means for processing establishes the HTTP connection by establishing an HTTP over Transport Layer Security (TLS) connection.

22. The node as claimed in claim 19, wherein the means for processing receives the updated configuration information by receiving the updated configuration information in a self-describing structured text format.

23. The node as claimed in claim 22, wherein the means for processing receives the updated configuration information by receiving the updated configuration information in an Extensible Markup Language (XML) format.