Method and system for remote configuration of managed nodes

• US 7,930,370 B2
• Filed: 12/31/2007
• Issued: 04/19/2011
• Est. Priority Date: 12/31/2007
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Risbud, Vinayak
• Primary Examiner(s): SALAD, ABDULLAHI ELMI
• Application Number:
  US11/967,823
• Publication Number:
  US 20090172195A1
• Time in Patent Office: 1,205 Days
• Field of Search: 703220-223, 703/245, 703227-228
• US Class Current: 709/220
• CPC Class Codes: H04L 61/5046 Resolving address allocation conflicts; Testing of addresses testing when self-assigning an address H04L61/5092
• 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/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168

Abstract

A method and system may send a first data packet on a network from a client node to a management server. The first data packet may be formatted to include a client Internet Protocol (IP) address field, a Universally Unique Identifier (UUID) request flag, a client UUID field, a client hardware address, and a first port number. The client node may listen for a second port number on the network and may receive a second data packet. The second data packet may have the same format as the first data packet and may include the second port number.

Claims

1. A method comprising:

sending a first data packet on a network from a client to a management server, the data packet formatted to include at least a client Internet Protocol (IP) address field, a Universally Unique Identifier (UUID) request flag, a client UUID field, a client hardware address, and a first port number, wherein the management server is listening on a first port corresponding to the first port number;

listening at the client on a second port corresponding with a second port number on the network for the client hardware address; and

receiving at the client a second data packet from the management server, the second data packet containing the second port number and the client hardware address if the client has no assigned IP address.

2. The method of claim 1, wherein the client IP address field is set to 0.0.0.0.

3. The method of claim 1, wherein the first and second data packets are sent as Universal Datagram Protocol (UDP) packets.

4. The method of claim 1, wherein the first and second data packets have a Remote Configuration Protocol (RCP) format.

5. The method of claim 1:

wherein the first data packet is a UUID request; and

the second data packet includes a UUID assigned to the client.

6. The method of claim 5, wherein the second data packet is sent as a Universal Datagram Protocol (UDP) broadcast.

7. The method of claim 1, comprising:

sending the first data packet on the network from a client to a management server, wherein the first data packet is a static IP address request; and

the second data packet including a static IP address assigned to the client.

8. The method of claim 1, comprising:

sending the first data packet on the network from a management server to a plurality of clients, wherein the data packet is an IP address conflict resolution request, the IP address conflict resolution request containing at least a UUID of a client with a conflicted IP address, and wherein the plurality of clients are listening on the second port number;

receiving the second data packet at the management server from the client with the conflicted IP address, wherein the second data packet is a static IP address request, and wherein the second data packet includes the first port number; and

sending a third data packet on the network from the management server to the client with the conflicted IP address, the third data packet including a static IP address assigned to the client and including the second port number.

9. A system, comprising:

a client node connected to a network to send a first data packet on the network to a management server, the data packet formatted to include at least a client Internet Protocol (IP) address field, a Universally Unique Identifier (UUID) request flag, a client UUID field, a client hardware address, and a first port number, the client node to listen on a second port corresponding to a second port number on the network for the client hardware address and to receive a second data packet from the management server, the second data packet containing the second port number and the client hardware address if the client has no assigned IP address, wherein the management server is listening on a first port assigned to the first port number.

10. The system of claim 9, comprising:

the management server connected to the network to send the second data packet and to listen for the first port number.

11. The system of claim 9, wherein the first and second data packets are sent as Universal Datagram Protocol (UDP) packets.

12. The system of claim 9, wherein the first and second data packets have a Remote Configuration Protocol (RCP) format.

13. The system of claim 9, wherein the the first data packet is a UUID request, and the second data packet includes at least a UUID assigned to the client.

14. The system of claim 13, wherein the second data packet is sent as a UDP broadcast.

15. The system of claim 9, wherein the first data packet is a static IP address request, and the second data packet includes a static IP address assigned to the client node.