METHOD AND SYSTEM FOR REMOTE CONFIGURATION OF MANAGED NODES

• US 20090172195A1
• Filed: 12/31/2007
• Published: 07/02/2009
• Est. Priority Date: 12/31/2007
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: RISBUD, Vinayak
• Granted Patent: US 7,930,370 B2
• Time in Patent Office: Days
• US Class Current: 709/245
• 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, 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;

listening for a second port number on the network; and

receiving a second data packet, the second data packet having the same format as the first data packet and including the second port number.

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, comprising:

sending the first data packet on the network from a client to a management server, wherein the data packet is a UUID request and the management server is listening on the first port number; and

receiving the second data packet at the client from the management server, the second data packet including a UUID assigned to the client and including the second port number.

6. The method of claim 5, wherein the second data packet is sent as a UDP broadcast and contains the client hardware address if the client has no assigned IP address, and the method comprising the client listening for the client hardware address.

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 management server is listening on the first port number; and

receiving the second data packet at the client from the management server, the second data packet including a static IP address assigned to the client and including the second port number.

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, 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 to listen for a second port number on the network and to receive a second data packet, the second data packet having the same format as the first data packet and including the second port number.

10. The system of claim 9, comprising:

a 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 10, wherein the client node is to send the first data packet on the network to the management server, the management server is to send the second data packet to the client node, 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 and contains the client hardware address if the client node has no assigned IP address, and the client node is to listen for the client hardware address.

15. The system of claim 10, 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.