Method for interrogating and proliferating a rack name in a rack of servers

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

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Cartes, Andrew C., Autor, Jeffrey S., Jones, Kevin M., Sanders, Michael C.
• Application Number:
  US09/965,893
• Publication Number:
  US 20030065751A1
• Time in Patent Office: Days
• US Class Current: 709/220
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/5038 for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
• CPC Class Codes: H04L 61/5046 Resolving address allocation conflicts; Testing of addresses testing when self-assigning an address H04L61/5092

Abstract

A method for propagating a rack name within a computer server rack. The rack comprises a plurality of server and/or power supply chassis, each with its own chassis controller. The name of the rack is stored in memory in each chassis controller. Rack names are propagated by requesting a rack name or receiving a command to set the rack name at each controller. The rack name is assigned to the rack via manual input through an external port in any of the servers. If a controller receives a rack name from this external port, this rack name is used. If the name comes from another controller and there is no existing name, the new name is accepted. If the new name differs from an existing rack name, the controller issues a naming conflict message and raises a conflict flag.

Claims

1. A computer server rack, comprising:

a plurality of modular server chassis configured to hold a plurality of computer servers, each chassis comprising a chassis controller having a processor and a memory, and

an internal communications bus coupling each of the chassis controllers;

wherein the chassis controllers transmit and receive a server rack name on the internal communications bus; and

wherein the name of the rack is stored in the memory in each chassis controller.

2. The server rack of claim 1 further comprising at least one modular power supply chassis configured to hold a plurality of power supplies and further comprising a chassis controller having a processor and a memory.

3. The server rack of claim 1 further comprising an external port in at least one of the computer servers;

wherein the rack name is assigned to the rack via manual input through the external port.

4. The server rack of claim 3 wherein each chassis controller further comprises a conflict flag;

wherein if a controller receives a rack name from the internal communications bus that differs from the rack name stored in memory, the controller issues a naming conflict message and changes the position of the conflict flag.

5. The server rack of claim 4 wherein the conflict flag is a bit field in the chassis controller.

6. The server rack of claim 4 wherein the naming conflict message is warning to a server administrator.

7. The server rack of claim 1 wherein;

the memory in which the rack name is stored is flash memory.

8. A chassis controller deployable in a server rack comprising:

a processor;

a system memory;

a flash memory;

an internal bus port through which the controller may communicate with other controllers;

a device bus port through which the controller may communicate with other devices in the same chassis;

wherein the name of the rack in which the chassis is disposed is stored in flash memory.

9. The chassis controller of claim 8 wherein:

if the controller receives a rack name from the device bus, the new name is written to flash memory.

10. The chassis controller of claim 9 wherein:

the controller receives a rack name from the internal bus, the new name is compared with the rack name in flash memory to check for name conflicts.

11. The chassis controller of claim 10 further comprising:

if the controller receives a conflict message from the internal bus, the existing name in flash memory is invalidated.

12. A method of propagating a rack name within a server rack, comprising:

receiving a request to set the rack name at one of a plurality of chassis controllers; and

determining if the rack name was received from a transmitting chassis controllers along an internal bus or from an external port;

wherein if the rack name was received from an external port, setting the rack name within the chassis controller.

13. The method of claim 12, wherein:

if the rack name is received from the internal bus, determining whether the transmitting chassis controller is authorized to issue the request to the receiving chassis controller; and

if the transmitting chassis controller is authorized to issue the request, setting the rack name within the receiving chassis controller

14. The method of claim 13, wherein:

if the transmitting chassis controller is not authorized to issue the request, issuing a security alert.

15. The method of claim 13, further comprising:

forwarding the new rack name along the internal bus to another of the plurality of chassis controllers.

16. The method of claim 13, further comprising:

clearing any naming conflict flags after setting the new rack name.

17. A method of propagating a rack name within a server rack, comprising:

issuing a request for a rack name from a first to a second of a plurality of chassis controllers; and

receiving a response from the second chassis controller at the first chassis controller; and

determining whether the first chassis controller has an existing rack name;

wherein if no existing rack name exists and the response includes a new rack name, setting the rack name within the first chassis controller.

18. The method of claim 17, wherein:

if an existing rack name matches the rack name received from the second chassis controller, keeping the rack name within the first chassis controller.

19. The method of claim 17, wherein:

if an existing rack name does not match the rack name received from the second chassis controller, raising a name conflict flag and reporting the naming conflict to a system administrator.

20. The method of claim 17, wherein:

if the first chassis controller has an existing rack name and if the response from the second chassis controller does not include a rack name nor a naming conflict flag, propagating the internal rack name to other chassis controllers.

21. The method of claim 17, wherein:

if the response from the second chassis controller includes a naming conflict flag, raising a naming conflict flag.

22. A method of propagating a rack name within an electronics rack, comprising:

receiving a request to set the rack name at one of a plurality of peer controllers; and

determining if the rack name was received from a transmitting peer controllers along an internal bus or from an external port;

wherein if the rack name was received from an external port, setting the rack name within the peer controller.

23. The method of claim 22, wherein:

if the rack name is received from the internal bus, determining whether the transmitting peer controller is authorized to issue the request to the receiving peer controller; and

if the transmitting peer controller is authorized to issue the request, setting the rack name within the receiving peer controller

24. The method of claim 23, wherein:

if the transmitting peer controller is not authorized to issue the request, issuing a security alert.

25. The method of claim 23, further comprising:

forwarding the new rack name along the internal bus to another of the plurality of peer controllers.

26. The method of claim 23, further comprising:

clearing any naming conflict flags after setting the new rack name.

27. A method of propagating a rack name within an electronics rack, comprising:

issuing a request for a rack name from a first to a second of a plurality of peer controllers; and

receiving a response from the second peer controller at the first peer controller; and

determining whether the first peer controller has an existing rack name;

wherein if no existing rack name exists and the response includes a new rack name, setting the rack name within the first peer controller.

28. The method of claim 27, wherein:

if an existing rack name matches the rack name received from the second peer controller, keeping the rack name within the first peer controller.

29. The method of claim 27, wherein:

if an existing rack name does not match the rack name received from the second peer controller, raising a name conflict flag and reporting the naming conflict to a system administrator.

30. The method of claim 27, wherein:

if the first peer controller has an existing rack name and if the response from the second peer controller does not include a rack name nor a naming conflict flag, propagating the internal rack name to other peer controllers.

31. The method of claim 27, wherein:

if the response from the second peer controller includes a naming conflict flag, raising a naming conflict flag.

32. An electronics rack, comprising:

a plurality of modular devices, each device including a peer controller comprising a processor and a memory; and

an internal communications bus coupling each of the peer controllers;

wherein the peer controllers transmit and receive a server rack name on the internal communications bus.

33. The electronics rack of claim 32 wherein:

the name of the rack is stored in the memory in each peer controller.

34. The electronics rack of claim 33 further comprising an external port in at least one of the peer controllers;

wherein the rack name is assigned to the rack via manual input through the external port.

35. The electronics rack of claim 34 wherein each peer controller further comprises a conflict flag;

wherein if a peer controller receives a rack name from the internal communications bus that differs from the rack name stored in local memory, the peer controller issues a naming conflict message and changes the position of the conflict flag.