Modular server architecture with high-availability management capability

• US 20030069953A1
• Filed: 09/28/2001
• Published: 04/10/2003
• Est. Priority Date: 09/28/2001
• Status: Abandoned Application

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Varley, Jason, Bottom, David A.
• Application Number:
  US09/966,830
• Publication Number:
  US 20030069953A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/0836 to enhance reliability, e.g. reduce downtime
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/16 Threshold monitoring

Abstract

A system, apparatus, and method are provided for nonstop management of a modular server architecture to achieve high-availability. According to one embodiment of the present invention, a server in the chassis is automatically elected as a managing server or active server to host system management. The active server runs service for all servers operating in the chassis. Upon failure of the managing server, such as when not meeting a certain predetermined criteria, another server is reelected as active server to replace the previous active server to continue with the nonstop management of the chassis and remaining servers.

Claims

1. A method comprising:

electing a first server as active manager server, wherein the first server resides in a chassis; and

electing a second server as the active manager server to replace the first server as the active manager server when the first server is to be replaced, wherein the second server resides in the chassis.

2. The method of claim 1, wherein the election is performed based on a predetermined criteria, wherein the predetermined criteria comprises electing a server with the lowest IP address as the active manager server.

3. The method of claim 1, further comprising:

extracting health metrics and performance metrics, wherein the health metrics and performance metrics are dynamic;

replicating the health metrics and performance metrics, wherein the replicating the health metrics and performance metrics is performed periodically; and

dynamically updating a database populated with the health metrics and performance metrics.

4. The method of claim 3, wherein the health metrics are server-based.

5. The method of claim 3, wherein the health metrics comprise tracking power levels and temperature levels based on predetermined thresholds.

6. The method of claim 3, wherein the performance metrics comprise operating system-based metrics, kernel-based metrics, and server-based metrics.

7. The method of claim 3, wherein the performance metrics comprise tracking CPU utilization and memory utilization based on the predetermined thresholds.

8. The method of claim 3, further comprises an alert mechanism to alert whenever the health metrics or the performance metrics violate the predetermined thresholds.

9. The method of claim 3, further comprising replicating identification information, wherein the identification information is static.

10. A high-availability management system comprising:

a chassis comprising a plurality of slots;

a plurality of server modules coupled with the plurality of slots, wherein a first server module of the plurality of server modules is elected an active manager server.

11. The high-availability management system of claim 10, further comprising a database coupled to the chassis for storing information regarding chassis identification, slot identification, and server module type.

12. The high-availability management system of claim 10, wherein the first server module of the plurality of server modules is elected the active manager server based on a predetermined criteria.

13. The high-availability management system of claim 10, wherein a second server module of the plurality of server modules is elected the active manager server, based on the predetermined criteria, to replace the first server module as the active manager server when the first server module is to be replaced.

14. The high-availability management system of claim 10, wherein the election of the first server module as the active manager server is performed by middleware, wherein the middleware is a software.

15. The high-availability management system of claim 13, wherein the election of the second server module as the active manager server is performed by the middleware, wherein the middleware is a software.

16. The high-availability management system of claim 10, wherein the first server module is elected from a group comprising servers, telephone line cards, and power substations.

17. A method of uninterrupted management using sticky identification comprising:

assigning a chassis identification to a chassis coupled to a computer, wherein the chassis comprises a slot;

assigning a slot identification to the slot based on the slot'"'"'s location in the chassis; and

assigning a server module type to the slot based on the chassis identification and the slot identification, wherein the server module type indicates server module characteristics.

18. The method of uninterrupted management using sticky identification of claim 17, further comprising retaining the server module characteristics corresponding to the server module type.

19. The method of uninterrupted management using sticky identification of claim 17, further comprising:

removing a first server module from the slot;

coupling a second server module to the slot; and

managing the second server module based on the server module characteristics corresponding to the server module type, wherein the managing the second server module is performed without updating a network management system.

20. The method of uninterrupted management using sticky identification of claim 17, further comprising:

assigning a user-defined chassis identification;

assigning a user-defined slot identification;

assigning a user-defined module identification; and

retaining the user-defined chassis identification and the user-defined slot identification and the user-defined module identification.

21. A machine-readable medium having stored thereon data representing sequences of instructions, the sequences of instructions which, when executed by a processor, cause the processor to:

elect a first server as active manager server, wherein the first server resides in a chassis; and

elect a second server as the active manager server to replace the first server as the active manager server when the first server is to be replaced, wherein the second server resides in the chassis.

22. The machine-readable of claim 21, wherein the election is performed based on a predetermined criteria, wherein the predetermined criteria comprises electing a server with the lowest IP address as the active manager server.

23. A machine-readable medium of claim 21, wherein the sequences of instructions which, when executed by a processor, further cause the processor to:

extract health metrics and performance metrics, wherein the health metrics and performance metrics are dynamic;

replicate the health metrics and performance metrics, wherein the replicating the health metrics and performance metrics is performed periodically; and

dynamically update a database populated with the health metrics and performance metrics.

24. A machine-readable medium having stored thereon data representing sequences of instructions, the sequences of instructions which, when executed by a processor, cause the processor to:

assign a chassis identification to a chassis coupled to a computer, wherein the chassis comprises a slot;

assign a slot identification to the slot based on the slot'"'"'s location in the chassis; and

assign a server module type to the slot based on the chassis identification and the slot identification, wherein the server module type indicates server module characteristics.

25. The machine-readable medium of claim 24, wherein the sequences of instructions which, when executed by a processor, further cause the processor to retain the server module characteristics corresponding to the server module type.

26. The machine-readable medium of claim 24, wherein the sequences of instructions which, when executed by a processor, further cause the processor to:

remove a first server module from the slot;

couple a second server module to the slot; and

manage the second server module based on the server module characteristics corresponding to the server module type, wherein the managing the second server module is performed without updating a network management system.