Secure network identity distribution

• US 7,181,543 B2
• Filed: 06/14/2002
• Issued: 02/20/2007
• Est. Priority Date: 08/10/2001
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Mayhead, Martin P., King, James E.
• Primary Examiner(s): Walsh; John B.
• Application Number:
  US10/171,818
• Publication Number:
  US 20030030990A1
• Time in Patent Office: 1,712 Days
• Field of Search: None
• US Class Current: 709/250
• CPC Class Codes: G06F 1/183 Internal mounting support structures, e.g. for printed circuit boards, internal connecting means for buses G06F13/409
• CPC Class Codes: G06F 1/187 Mounting of fixed and removable disk drives
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/55 Detecting local intrusion or implementing counter-measures
• CPC Class Codes: G06F 21/629 to features or functions of an application
• CPC Class Codes: G06F 2221/2119 Authenticating web pages, e.g. with suspicious links
• CPC Class Codes: G06F 2221/2137 Time limited access, e.g. to a computer or data
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 2221/2149 Restricted operating environment
• CPC Class Codes: G11B 33/128 of the plurality of recording/reproducing devices, e.g. disk drives, onto a chassis
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H05K 7/1425 of standardised dimensions, e.g. 19"-subrack
• CPC Class Codes: H05K 7/1489 characterized by the mounting of blades therein, e.g. brackets, rails, trays H05K7/1491 takes precedence

Abstract

Network identities for components (e.g., server blades) of a multi-domain computer system (e.g., a server blade system) are stored in a connection framework (e.g., a carrier for the server blades) and copies thereof are stored in two or more support units (e.g., service processors for the carrier). These multiple copies can then be used to ensure the integrity of network identities that are allocated to the system units by the support units.

Claims

1. A computer system configured to connect to a network, the computer system comprising:

a connection framework configured to receive at least two field replaceable support units and at least one field replaceable system unit;

wherein the connection framework is configured to store a set of network identities for at least predetermined ones of the field replaceable units;

wherein each field replaceable support unit is configured to store a copy of the set of network identities for at least predetermined ones of the field replaceable units; and

wherein, where a first one of the field replaceable support units is operable in the connection framework and a second field replaceable support units is powered up, the first field replaceable support unit is configured to determine whether the network identities stored in the second field replaceable support unit are equivalent to the network identities stored in the connection framework.

2. The computer system of claim 1, wherein, where the first field replaceable support unit determines that the network identities stored in the connection framework are equivalent to those stored in itself, but are not equivalent to those stored in the second field replaceable support unit, then it is operable to cause the network identities stored in the connection framework to be copied to the second field replaceable storage unit.

3. The computer system of claim 1, wherein, where the first field replaceable support unit determines that the network identities stored in the connection framework are equivalent to those stored in itself, but are not equivalent to those stored in the second field replaceable support unit, then it is operable to copy the network identities stored in itself to the second field replaceable storage unit.

4. The computer system of claim 1, wherein, where the first field replaceable support unit determines that the network identities stored in the connection framework are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in itself, then it is operable to cause the network identities stored in the connection framework to be copied to itself.

5. The computer system of claim 1, wherein, where the first field replaceable support unit determines that the network identities stored in the connection framework are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in itself, then it is operable to cause the network identities stored in the second field replaceable storage unit to be copied to itself.

6. The computer system of claim 1, wherein, where the first field replaceable support unit determines that the network identities stored in itself are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in the connection framework, then it is operable to cause the network identities stored in itself to be copied to the connection framework.

7. The computer system of claim 1, wherein, where the first field replaceable support unit determines that the network identities stored in itself are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in the connection framework, then it is operable to cause the network identities stored in the second field replaceable support unit to be copied to the connection framework.

8. The computer system of claim 1, wherein, where the first field replaceable support unit determines that the network identities stored in each of itself, the second field replaceable support unit and the connection framework are not equivalent to each other, then it is operable to cause the network identities stored in the connection framework to be copied to itself and to the second field replaceable support unit.

9. The computer system of claim 1, wherein the connection framework forms a carrier for the field replaceable units.

10. The computer system of claim 9, wherein the carrier is a rack mountable shelf.

11. The computer system of claim 1, wherein the computer system is a high density server system and said at least one field replaceable system unit is a blade server.

12. The computer system of claim 1, wherein the field replaceable support unit is a service processor.

13. The computer system of claim 1, wherein the field replaceable support unit is configured as a combined switch and service processor module.

14. A method of connecting a computer system to a networks wherein the computer system includes a connection framework for receiving at least two field replaceable support units and at least one field replaceable system unit, the method comprising:

storing a set of network identities for at least predetermined ones of the field replaceable units in the connection framework;

storing, in said field replaceable support units, a copy of the set of network identities for at least predetermined ones of the field replaceable units; and

where a first one of the field replaceable support units is operable in the connection framework and a second field replaceable support units is powered up, determining whether the network identities stored in the second field replaceable support unit are equivalent to the network identities stored in the connection framework.

15. The method of claim 14, further comprising, where the network identities stored in the connection framework are equivalent to those stored in the first field replaceable support unit, but are not equivalent to those stored in the second field replaceable support unit, copying the network identities stored in the connection framework to the second field replaceable storage unit.

16. The method of claim 14, further comprising, where the network identities stored in the connection framework are equivalent to those stored in the first field replaceable support unit, but are not equivalent to those stored in the second field replaceable support unit, copying the network identities stored in the first field replaceable support unit to the second field replaceable storage unit.

17. The method of claim 14, comprising, where the network identities stored in the connection framework are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in the first field replaceable support unit, copying the network identities stored in the connection framework to the first field replaceable support unit.

18. The method of claim 14, comprising, where the network identities stored in the connection framework are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in the first field replaceable support unit, copying the identities stored in the second field replaceable storage unit to the first field replaceable support unit.

19. The method of claim 14, comprising, where the network identities stored in the first field replaceable support unit are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in the connection framework, copying the network identities stored in the first field replaceable support unit to the connection framework.

20. The method of claim 14, wherein, where the network identities stored in the first field replaceable support unit are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in the connection framework, copying the network identities stored in the second field replaceable support unit to the connection framework.

21. The method of claim 14, wherein, where the network identities stored in each of the first field replaceable support unit, the second field replaceable support unit and the connection framework are not equivalent to each other, copying the network identities stored in the connection framework to the first field replaceable support unit and to the second field replaceable support unit.

22. A blade server system configured to connect to a network, the blade server system comprising:

a carrier configured to receive a plurality of field replaceable units;

a first field replaceable support unit and a second field replaceable support unit received in the carrier; and

one or more field replaceable server blades received in the carrier;

wherein the carrier is configured to store a set of network identities for at least predetermined ones of the field replaceable units;

wherein each field replaceable support unit is configured to store a copy of the set of network identities for at least predetermined ones of the field replaceable units; and

wherein, in response to powering up the second field replaceable support unit, the first field replaceable support unit is configured to determine whether the network identities stored in the field replaceable support units are equivalent to the network identities stored in the carrier.

23. The blade server system of claim 22, wherein, where the first field replaceable support unit determines that the network identities stored in the connection framework are equivalent to those stored in itself, but are not equivalent to those stored in the second field replaceable support unit, then it is operable to cause the network identities stored in the connection framework to be copied to the second field replaceable storage unit.

24. The blade server system of claim 22, wherein, where the first field replaceable support unit determines that the network identities stored in the connection framework are equivalent to those stored in itself, but are not equivalent to those stored in the second field replaceable support unit, then it is operable to copy the network identities stored in itself to the second field replaceable storage unit.

25. The blade server system of claim 22, wherein, where the first field replaceable support unit determines that the network identities stored in the connection framework are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in itself, then it is operable to cause the network identities stored in the connection framework to be copied to itself.

26. The blade server system of claim 22, wherein, where the first field replaceable support unit determines that the network identities stored in the connection framework are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in itself, then it is operable to cause the network identities stored in the second field replaceable storage unit to be copied to itself.

27. The blade server system of claim 22, wherein, where the first field replaceable support unit determines that the network identities stored in itself are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in the connection framework, then it is operable to cause the network identities stored in itself to be copied to the connection framework.

28. The blade server system of claim 22, wherein, where the first field replaceable support unit determines that the network identities stored in itself are equivalent to those stored in the second field replaceable support unit, but are not equivalent to those stored in the connection framework, then it is operable to cause the network identities stored in the second field replaceable support unit to be copied to the connection framework.

29. The blade server system of claim 22, wherein, where the first field replaceable support unit determines that the network identities stored in each of itself, the second field replaceable support unit and the connection framework are not equivalent to each other, then it is operable to cause the network identities stored in the connection framework to be copied to itself and to the second field replaceable support unit.

30. The blade server system of claim 22, wherein the carrier is a rack mountable shelf.

31. The blade server system of claim 22, wherein the field replaceable support unit is a service processor.

32. The blade server system of claim 22, wherein the field replaceable support unit is configured as a combined switch and service processor module.

33. A computer system configured to connect to a network, the computer system comprising:

a connection framework configured to receive a plurality of field replaceable units;

a first field replaceable support unit and a second field replaceable support unit received in the connection framework; and

one or more field replaceable system units received in the connection framework;

wherein the connection framework is configured to store a set of network identities for at least predetermined ones of the field replaceable units;

wherein each field replaceable support unit is configured to store a copy of the set of network identities for at least predetermined ones of the field replaceable units; and

wherein, in response to powering up the second field replaceable support unit, the first field replaceable support unit is configured to determine whether the network identities stored in the field replaceable support units are equivalent to the network identities stored in the connection framework.