Deciding redistribution servers by hop count

• US 20070074198A1
• Filed: 08/31/2005
• Published: 03/29/2007
• Est. Priority Date: 08/31/2005
• Status: Abandoned Application

• Current Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Gassoway, Paul, Gargiulo, John
• Application Number:
  US11/218,263
• Publication Number:
  US 20070074198A1
• Time in Patent Office: Days
• US Class Current: 717/168
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A system and method are provided for updating software on a client computer including accessing a list of available redistribution servers in a network wherein each redistribution server includes particular software for download. A hop count is determined between a client computer and a plurality of the redistribution servers on the list of available redistribution servers, and the software is requested from a redistribution server with the lowest determined hop count.

Claims

1. A method of updating software on a client computer, comprising:

accessing a list of available redistribution servers in a network, wherein each redistribution server includes particular software for download;

determining a hop count between a client computer and a plurality of the redistribution servers on the list of available redistribution servers; and

requesting the software from a redistribution server with the lowest determined hop count.

2. The method of claim 1, wherein determining the hop count between the client computer and the plurality of the redistribution servers on the list of available redistribution servers comprises:

repeating the following for each of the plurality of the redistribution servers;

repeating the following until the redistribution server acknowledges receipt of a packet;

sending the packet to the redistribution server requesting that the redistribution server acknowledge receipt of the packet; and

incrementing a time-to-live parameter of the packet in response to a delivery failure notification from an intermediate network component; and

associating the redistribution server with the time-to-live parameter, the time-to-live parameter corresponding to the hop count between the client computer and the redistribution server.

3. The method of claim 2, further comprising:

compiling a list of the redistribution servers and their associated hop counts; and

making the list of the redistribution servers and their associated hop counts available to a plurality of clients in a subnet of the network.

4. The method of claim 3, wherein the compiling is accomplished by the client computer.

5. The method of claim 3, wherein the compiling is accomplished by an administration server that is responsible for the subnet.

6. The method of claim 2, wherein the packet is an ICMP echo request PING packet.

7. The method of claim 1, wherein the software includes virus signature files.

8. A method of updating software on a network, comprising:

accessing a list of subnets, the subnets including at least one client computer;

accessing a list of redistribution servers available to each subnet;

directing a first client computer on at least one subnet to determine a first hop count between the first client computer and a first redistribution server available to the at least one subnet;

directing the first client computer on the at least one subnet to determine a second hop count between the first client computer and a second redistribution server available to the at least one subnet; and

compiling a table associating the first redistribution server with the first hop count and associating the second redistribution server with the second hop count.

9. The method of claim 8, further comprising communicating the table to a plurality of client computers on the at least one subnet.

10. The method of claim 8, further comprising:

receiving a request at an administration server from a second client computer of the at least one subnet for an identifier of the redistribution server available to the at least one subnet that has the lowest hop count; and

providing to the second client computer of the at least one subnet an identifier of the redistribution server available to the at least one subnet that has the lowest hop count.

11. The method of claim 8, wherein directing the first client computer on the at least one subnet to determine the first hop count between the first client computer and the first redistribution server available to the at least one subnet comprises:

repeating the following until the first redistribution server acknowledges receipt of a packet;

sending the packet to the first redistribution server requesting that the first redistribution server acknowledge receipt of the packet; and

incrementing a time-to-live parameter of the packet in response to a delivery failure notification from an intermediate network component; and

associating the first redistribution server with the time-to-live parameter, the time-to-live parameter corresponding to the hop count between the first client computer and the first redistribution server.

12. The method of claim 8, further comprising repeating the following for each of a plurality of subnets on the list of subnets:

directing a client computer in a subnet of the plurality of subnets to determine a first hop count between the client computer and a first redistribution server available to the subnet of the plurality of subnets;

directing the client computer in the subnet of the plurality of subnets to determine a second hop count between the client computer and a second redistribution server available to the subnet of the plurality of subnets; and

compiling a table associating the first redistribution server with the first hop count and associating the second redistribution server with the second hop count.

13. The method of claim 8, further comprising:

accessing the table to determine a redistribution server available to the at least one subnet that has the lowest hop count; and

requesting software from the redistribution server available to the at least one subnet that has the lowest hop count.

14. The method of claim 13, wherein the software includes virus signature files.

15. A network for updating software on a client computer, comprising:

a plurality of redistribution servers, each redistribution server including particular software for download; and

at least one client computer operable to;

determine a hop count between the client computer and each of the plurality of redistribution servers; and

request the software from the one of the plurality of redistribution servers with the lowest determined hop count.

16. The network of claim 15, wherein the client computer operable to determine the hop count between the client computer and the plurality of redistribution servers comprises the client computer operable to:

repeat the following for each of the plurality of the redistribution servers;

repeat the following until the redistribution server acknowledges receipt of a packet;

send the packet to the redistribution server and request that the redistribution server acknowledge receipt of the packet; and

increment a time-to-live parameter of the packet in response to a delivery failure notification from an intermediate network component; and

associate the redistribution server with the time-to-live parameter, the time-to-live parameter corresponding to the hop count between the client computer and the redistribution server.

17. The network of claim 16, further comprising a hop count table listing the plurality of redistribution servers and their associated hop counts, the hop count table being available to a plurality of client computers in a subnet of the network.

18. The network of claim 17, wherein the hop count table resides on one of the plurality of client computers in the subnet of the network.

19. The network of claim 17, wherein the hop count table resides on an administration server that is responsible for the subnet of the network.

20. The network of claim 16, wherein the packet is an ICMP echo request PING packet.

21. The network of claim 15, wherein the software includes virus signature files.

22. A system for updating software on a network, comprising:

a plurality of subnets, each of the plurality of subnets including at least one client computer;

a list of redistribution servers available to each subnet;

an administration server coupled to the plurality of subnets and operable to;

direct a first client computer on one of the plurality of subnets to determine a first hop count between the first client computer and a first redistribution server available to the one of the plurality of subnets;

direct the first client computer to determine a second hop count between the first client computer and a second redistribution server available to the one of the plurality of subnets; and

compile a subnet table associating the first redistribution server with the first hop count and associating the second redistribution server with the second hop count.

23. The system of claim 22, further comprising communicating the table to a plurality of client computers on the one of the plurality of subnets.

24. The system of claim 22, further comprising the administration server further operable to:

receive a request from a second client computer on the one of the plurality of subnets for an identifier of a redistribution server available to the one of the plurality of subnets that has the lowest hop count; and

provide to the second client computer an identifier of the redistribution server available to the one of the plurality of subnets that has the lowest hop count.

25. The system of claim 22, wherein the administration server operable to direct the first client computer on one of the plurality of subnets to determine the first hop count between the first client computer and the first redistribution server available to the one of the plurality of subnets comprises:

repeating the following until the first redistribution server acknowledges receipt of a packet;

sending the packet to the first redistribution server requesting that the first redistribution server acknowledge receipt of the packet; and

incrementing a time-to-live parameter of the packet in response to a delivery failure notification from an intermediate network component; and

associating the first redistribution server with the time-to-live parameter, the time-to-live parameter corresponding to the hop count between the first client computer and the first redistribution server.

26. The system of claim 22, wherein the first client computer is further operable to:

access the subnet table to determine a redistribution server available to the one of the plurality of subnets that has the lowest hop count; and

request software from the redistribution server available to one of the plurality of subnets that has the lowest hop count.

27. The system of claim 26, wherein the software includes virus signature files.