New! View global litigation for patent families

US20030009559A1 - Network system and method of distributing accesses to a plurality of server apparatus in the network system - Google Patents

Network system and method of distributing accesses to a plurality of server apparatus in the network system Download PDF

Info

Publication number
US20030009559A1
US20030009559A1 US10189468 US18946802A US20030009559A1 US 20030009559 A1 US20030009559 A1 US 20030009559A1 US 10189468 US10189468 US 10189468 US 18946802 A US18946802 A US 18946802A US 20030009559 A1 US20030009559 A1 US 20030009559A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
apparatus
load
balancing
access
servers
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10189468
Inventor
Naoya Ikeda
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/02Communication control; Communication processing contains provisionally no documents
    • H04L29/06Communication control; Communication processing contains provisionally no documents characterised by a protocol
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/1002Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers, e.g. load balancing
    • H04L67/1004Server selection in load balancing
    • H04L67/1023Server selection in load balancing based on other criteria, e.g. hash applied to IP address, specific algorithms or cost
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/02Communication control; Communication processing contains provisionally no documents
    • H04L29/06Communication control; Communication processing contains provisionally no documents characterised by a protocol
    • H04L29/0602Protocols characterised by their application
    • H04L29/06047Protocols for client-server architecture
    • H04L2029/06054Access to distributed or replicated servers, e.g. using brokers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/1002Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers, e.g. load balancing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/1002Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers, e.g. load balancing
    • H04L67/1004Server selection in load balancing
    • H04L67/1017Server selection in load balancing based on a round robin mechanism

Abstract

A network system includes a plurality of servers, a plurality of load balancing apparatus and at least one routing apparatus. Each load balancing apparatus is connected to two or more servers of a plurality of servers. Each routing apparatus is connected to two or more load balancing apparatus of a plurality of load balancing apparatus and to a network. Each routing apparatus receives an access packet for a plurality of server apparatus from the network and forwards the access packet so received to an arbitrary one of the two or more load balancing apparatus connected to the routing apparatus. Each load balancing apparatus receives an access packet from each routing apparatus and transfers it to an arbitrary server among the two or more servers connected thereto.

Description

    BACKGROUND OF THE INVENTION
  • [0001]
    This invention relates to a load balancing method. More particularly, this invention relates to a load balancing method that makes it possible to distribute accesses to a plurality of Web servers of an information service site having one domain name (host name) through an Internet, or the like.
  • [0002]
    Recently, a variety of Internet services including EC (electronic commerce) have been drastically increasing in addition to utilization of Web accesses. Also, a phenomenon occurs in which traffic to a Web server of a specific site providing an information service sporadically increases. Therefore, providers providing the Internet services such as data centers and ASP (Application Service Providers) are required to provide services at a higher speed with higher reliability. A technology for distributing a traffic load to a specific site is known as a technology that can secure reliability and safety of the Web system.
  • [0003]
    In the technology of this kind, sites having the same domain name and providing the same service have a plurality of Web servers. The technology distributes the accesses to this site to a plurality of servers by using a load balancing apparatus and a DNS (Domain Name System) server. Incidentally, the DNS server is a server that converts the domain name designated from a client to a corresponding IP (Internet Protocol) address. Such a technology is disclosed in JP-A-2001-117897 and JP-A-2000-132524, for example.
  • [0004]
    Another technology uses the load balancing apparatus in combination with the DNS server. In this technology, a plurality of load balancing apparatus is provided to a plurality of Web servers of sites executing the same service. A route to each load balancing apparatus is selected on the basis of the IP address notified from the DNS server to the client.
  • SUMMARY OF THE INVENTION
  • [0005]
    According to the former technology, the load balancing apparatus can uniformly distribute the accesses (traffics) from the client, and has therefore the advance that it can avoid a bottleneck and can reduce the traffic load. However, the function of the load balancing apparatus itself has become higher and higher in recent years and the function itself has got diversified. Therefore, when the number of Web servers to which the load is to be distributed becomes great, the load balancing apparatus fails to exhibit sufficient performance.
  • [0006]
    The latter technology can switch the route to one load balancing apparatus to the route of another by using the DNS server when any fault occurs in the route to one load balancing apparatus. However, this technology needs a switching time of dozens of seconds (approximately 40 seconds) from detection of the fault to switching of the routes, and is not free from the problem that high-speed performance and high reliability get deteriorated.
  • [0007]
    This invention provides a load balancing method that solves the problems of the prior art technologies described above, can reduce the load to the load balancing apparatus to the Web server inside the site and can switch at a high speed the route even when any fault occurs in the route to one load balancing apparatus.
  • [0008]
    According to the invention, a network system includes a plurality of servers, a plurality of load balancing apparatus and at least one routing apparatus. Each load balancing apparatus is connected to two or more servers among a plurality of servers. Each routing apparatus is connected to two or more load balancing apparatus among a plurality of load balancing apparatus and is also connected to a network. Each routing apparatus receives an access packet from the network to a plurality of servers and forwards the access packet so received to an arbitrary load balancing apparatus among the two or load balancing apparatus connected to the routing apparatus. Each load balancing apparatus receives the access packet from each routing apparatus and transfers it to an arbitrary server among the two or more servers connected thereto.
  • [0009]
    In this network system, each routing apparatus forwards and distributes a plurality of access packets received from the network system to a plurality of load balancing apparatus. Each load balancing apparatus distributes and transfers a plurality of access packets forwarded to each load balancing apparatus to a plurality of servers.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0010]
    [0010]FIG. 1 shows a construction of a network system according to Embodiment 1 of the invention;
  • [0011]
    [0011]FIG. 2 shows a concrete example of setting of addresses in each apparatus;
  • [0012]
    [0012]FIG. 3 shows another concrete example of the network system; and
  • [0013]
    [0013]FIG. 4 shows a mode of fragmentation of an IPv4 packet.
  • DESCRIPTION OF THE EMBODIMENTS
  • [0014]
    Embodiments of the invention will be explained in detail with reference to the accompanying drawings.
  • [0015]
    [0015]FIG. 1 shows an overall construction of a network according to Embodiment 1. FIG. 2 shows a concrete example of setting of addresses in each apparatus.
  • [0016]
    As shown in FIG. 1, the network according to Embodiment 1 includes a plurality of client terminals 11, a DNS server 12, a site 10 and a network such as the Internet 13 to which these constituent apparatus are connected. A personal computer PC for receiving an information service, or the like, constitutes each client terminal 11. The client terminal 11 issues an access (packet) to the site 10. The DNS server 12 converts a domain name (host name) transmitted by the client terminal 11 for receiving the information service of the site 11 to an IP address of a Web server inside the site 10 and outputs this IP address.
  • [0017]
    The site 10 has a network system for executing the information service. The network system of the site 10 includes a router 14, load balancing apparatus A15 and B16 and a plurality of Web servers 17 a to 17 d. The router 14 establishes connection with the Internet 13. The router 14 receives the access issued from the client terminal 11 from the Internet 13 and transfers the access to the load balancing apparatus A15 and B16. The load balancing apparatus A15 and B16 execute load balancing of the access transferred from the router 14 to a plurality of Web servers. These Web servers 17 a to 17 d are respectively connected to the load balancing apparatus A15 and B16. All of them have the same construction and execute the same information service.
  • [0018]
    Incidentally, FIG. 1 shows two load balancing apparatus connected to the router and two Web servers connected to each load balancing apparatus. However, the number of the load balancing apparatus connected to the router and the number of Web servers connected to each load balancing apparatus may be greater than two.
  • [0019]
    In the network system having the construction described above, when two or more different routes exist to the same destination (specific network and server in this case), the router 14 has the function of distributing and transferring the access (packet) to the destination through each route. When the apparatus to which the access is to be next transferred (here, the router and the load balancing apparatus) is different for each route, the router 14 can distribute the access to each apparatus of the transfer destination due to this function. In FIG. 1, for example, the same virtual IP address “192.168.100.10” is set to the Web servers 17 a to 17 d. Therefore, the router 14 recognizes the Web servers 17 a to 17 d as the same destination. In this case, there are a route passing through the load balancing apparatus A15 and a route passing through the load balancing apparatus B16 between the router 14 and the Web servers 17 a to 17 d. Therefore, due to the function described above, the router 14 can dispersedly transfer the access to the Web servers 17 a to 17 d to the load balancing apparatus A15 and to the load balancing apparatus B16 through the respective routes. According to this function, further, the router 14 calculates a hash value from the address information contained in the access received in accordance with a certain hash function. The router 14 associates in advance each load balancing apparatus with each has value. The router 14 transfers the access it receives to the load balancing apparatus with which the calculated hash value is associated.
  • [0020]
    Each of the load balancing apparatus A15, B16 has a virtual LAN function and allocates the access to each Web server 17 a, 17 b and 17 c, 17 d by round robin scheduling.
  • [0021]
    In consequence, the network system of the site 10 can uniformly allocate a large number of accesses inputted to the router 14 to the Web servers 17 a to 17 d. Eventually, the site 10 can cope with a sporadic increase of the traffic and can continue the service without deteriorating high-speed performance and high reliability. When any fault develops between the router and the load balancing apparatus, hardware processing by the router can instantaneously switch the route to the other load balancing apparatus side.
  • [0022]
    Next, a concrete example of address setting to each apparatus and its operation example will be explained with reference to FIG. 2.
  • [0023]
    The network construction shown in FIG. 2 is fundamentally the same as the construction shown in FIG. 1. However, two client terminals 11 are connected to a hub 11′. The hub 11′ is connected to the router 14 through the Internet not shown in the drawing. In this FIG. 2, a domain name of the site 10 is www.hitachi-datacenter.co.jp. A network address of the network between the load balancing apparatus A15 and the router 14 is “192.168.252/24”. A host address of an interface on the router 14 side of the load balancing apparatus AlS is “253”. Therefore, an IP address of an interface on the side of the load balancing apparatus AlS is “192.168.252.253”. Similarly, a network address of a network between the load balancing apparatus B16 and the router 14 is “192.168.251/24”. A host address of an interface on the router 14 side of the load balancing apparatus B16 is “253”. The load balancing apparatus A15 sets VLAN (Virtual LAN) on at least the side of the Web servers 17 a and 17 b. The load balancing apparatus B16, too, sets VLAN (Virtual LAN) on at least the side of the Web servers 17 c and 17 d. In the VLAN that are respectively set on the sides of the Web servers 17 c and 17 d and the Web servers 17 c and 17 d, the load balancing apparatus A15 and B16 set the same virtual IP address (hereinafter called “VIP”), that is, 192.168.100.10 in the embodiment shown in the drawing. Therefore, the Web servers 17 a to 17 d are all identified (represented) by the same VIP and are recognized as one Web server by the client terminals and the DNS server. The DNS server 12 associates the VIP with the domain name www.hitachi-datacenter.co.jp.
  • [0024]
    Incidentally, the network address of each VLAN between the load balancing apparatus A15 and the Web servers 17 a and 17 b and between the load balancing apparatus B16 and the Web servers 17 c and 17 d is “192.168.100/24” in FIG. 2. Host addresses “1”, “2”, “3” and “4” are respectively set to the Web servers 17 a, 17 b, 17 c and 17 d. Therefore, the load balancing apparatus A15 identifies the Web server 17 a by the IP address “192.168.100.1” and the Web server 17 b by the IP address “192.168.100.2”. Similarly, the load balancing apparatus B16 identifies the Web server 17 c by the IP address “192.168.100.1” and the Web server 17 d by the IP address “192.168.100.2”.
  • [0025]
    A host address of the interface of the router 14 on the client terminal side, a host address of the interface on the DNS server 12 side, a host address of the interface on the side of the load balancing apparatus A15 and a host address of the interface on the side of the load balancing apparatus B16 are all “254”. A network address of the network between the router 14 and the DNS server 12 is “192.168.254/24” and a network address of the network between the router 14 and the client terminal 11 is “192.168.250/24”. A host address of each client terminal 11 is “1” and “2”.
  • [0026]
    An operation example of each apparatus shown in FIG. 2 will be explained.
  • [0027]
    To begin with, a user using the client terminal 11 desires to gain access to the site 10 and inputs the domain name www.hltachi-datacenter.co.jp of the site 10 to the client terminal 11. The client terminal 11 inquires the DNS server 12 of the IP address corresponding to this domain name. The DNS server 12 holds the domain name of the site in association with VIP “192.168.100.10” as described above and notifies the client terminal 11 of this VIP. The client terminal 11 issues an access to the Web servers 17 a to 17 d of the site 10 by using VIP so notified as a destination address. The router 14 of the site 10 receives this access through the Internet. Due to the function described above, the router 14 recognizes that two routes exist for the access to the destination (or two load balancing apparatuses for transferring the access exist). The router 14 calculates the hash value from the information of the destination address (VIP) and the transmitting address (IP address of the client terminal) contained in the access received in accordance with a hash function that is determined in advance. Since the router 14 has in advance a table for associating the load balancing apparatus (route) to which the access is to be transferred with each hash value, the router 14 looks up the table and decides the load balancing apparatus (route) to which the access received is to be transferred. The router 14 transfers the access to the load balancing apparatus so decided, for example, the load balancing apparatus A15. The router 14 executes this processing whenever it receives the access to the Web servers 17 a to 17 d and transfers the access to each load balancing apparatus A15 or B16. The load balancing apparatus A15 or B16 receives the access and recognizes that this access is addressed to the Web servers 17 a to 17 d. The load balancing apparatus A15 or B16 transfers the access to the two Web servers connected to each load balancing apparatus by round robin scheduling. Therefore, the Web servers 17 a and 17 b connected to the load balancing apparatus A15, for example, alternately receive the access. This also holds true of the Web servers 17 c and 17 d connected to the load balancing apparatus B16.
  • [0028]
    In this way, the router 14 allocates the access issued from the client terminal 11 to the two load balancing apparatus A15 and B16, and each load balancing apparatus A15, B16 allocates the access to the two Web servers 17 a and 17 b or 17 c and 17 d.
  • [0029]
    Because setting of the address, or the like, is made to each constituent apparatus of the network system of the site 10 as described above, the router 14 and each load balancing apparatus A15, B16 allocate the access. Therefore, the access can be distributed substantially uniformly to a plurality of Web servers inside the system.
  • [0030]
    [0030]FIG. 3 shows another structural example of the network system. Reference numerals used in FIG. 3 are the same as those used in FIG. 1.
  • [0031]
    The system construction shown in FIG. 3 is the same as that of FIG. 1. The router in the network system shown in FIG. 1 has the function of distributing and transferring the access to the same destination to two or more different routes. In the network system shown in FIG. 3, on the other hand, the router has a policy routing function, and distributes and transfers the access by this function. Originally, the router selects an optimal route of the network on the basis of the destination address of the IP packet and forwards the packet. On the other hand, the policy routing function represents a function of the router for selecting the forward route on the basis of information other than the destination address of the packet, such as a port number of the TCP port, that is, the kind of an application.
  • [0032]
    Therefore, the router 14 decides the selected route on the basis of the kind of the access issued from the client terminal 11 (the kind of the application used). For this reason, the Web servers disposed inside the site 10, too, are so grouped as to correspond to the access kind.
  • [0033]
    For example, the access issued from the client terminal 11 includes an ordinary HTTP (Hyper Text Transfer Protocol) access and an HTTPS access generated by ciphering the ordinary HTTP access by using an SSL (Security Sockets Layer) to exchange information calling for security. FIG. 3 shows the mode in which these two kinds of accesses are issued from the client terminal 11.
  • [0034]
    The Web servers 17 a and 17 b among the WEB servers 17 a to 17 d are so set as to process the HTTP access and the Web servers 17 c and 17 d are so set as to process the HTTPS access. The Web servers 17 c and 17 d receive the access from the load balancing apparatus B16 and the Web servers 17 a and 17 b receive the access from the load balancing apparatus A15.
  • [0035]
    The client terminal 11 issues the HTTP access when the user desires to check the information provided by the site 10, for example. When the user desires to purchase the goods provided by the site 10 and to transmit information calling for security such as a credit card number, the client terminal issues the HTTPS access. Various kinds of information (conditions) for policy routing are set in advance to the router 14. The information contains a plurality of access kinds and routes (apparatus to which the access is to be transferred) corresponding to the access kinds. For example, the HTTP access and the route 1) (load balancing apparatus A15) are associated with each other and are set to the router 14. Similarly, the HTTPS access and the route 2) are associated with each other and are set to the router 14. The route 1) is the route for forwarding the access to the Web server 17 a or 17 b through the load balancing apparatus A15. The route 2) is the route for forwarding the access to the Web server 17 c or 17 d through the load balancing apparatus B165. The information is registered to a table held by the router 14, for example. Receiving the access from the client terminal 11, the router 14 looks up the information about the application contained in the access such as a port number of the TCP port and recognizes the kind of the access. In the embodiment shown in FIG. 3, the router 14 recognizes whether the access it receives is the HTTP access or the HTTPS access. The router 14 selects the route 1) in accordance with a set condition when the access is the HTTP access and selects the route 2) when the access is the HTTPS access. In consequence, the router 14 forwards the HTTP access to the load balancing device and the HTTPS access to the load balancing apparatus B16.
  • [0036]
    As described above, each load balancing apparatus A15, B16 receives the access and transfers the access to two Web servers connected thereto by round robin scheduling.
  • [0037]
    Consequently, the router 14 allocates the access issued from the client terminal 11 in accordance with its kind to the two load balancing apparatus A15 and B16. Further, each load balancing apparatus A15, B16 allocates the access to the two Web servers 17 a, 17 b or 17 c, 17 d.
  • [0038]
    Incidentally, the address of each apparatus in the network system shown in FIG. 3 may well be the same as the address shown in FIG. 2.
  • [0039]
    The frequency (proportion) of issuance of the different kinds of accesses issued from the client terminal is mutually different. Therefore, the proportion of the number of sets of the Web servers for processing the respective kind of accesses is changed in accordance with the issuance frequency of various kinds of accesses. When the issuance ratio of the HTTP access to the HTTPS access is 3:1, for example, the number of sets of the Web servers for processing the HTTP access is 3 and the number of sets of the Web servers for processing the HTTPS access is 1. In this case, the Web servers 17 a to 17 c are connected to the load balancing device A15 and the Web server 17 d is connected to the load balancing apparatus B16. Since the site 10 is constituted in this way, it becomes possible to constitute a system in which an access can be more uniformly distributed to a plurality of Web servers.
  • [0040]
    As described above, the route is decided for each kind of the access. Therefore, the output interface of the router 14 can be fixedly allocated to each kind of access issued from the client terminal. In this case, the router 14 transmits each kind of access from the output interface decided for each kind.
  • [0041]
    In the network system shown in FIGS. 1 to 3, the router 14 and the load balancing apparatus A15 and B16 hierachically distribute the load. Generally, the router can forward (process) at a high speed an access. On the other hand, the transfer rate (processing speed) of the load balancing apparatus is lower (slower) than that of the router. Therefore, when the router 14 forwards the access to a specific load balancing appliance without distributing it, for example, the transfer rate of the access to the load balancing apparatus may be higher than the access processing speed by the load balancing apparatus. In such a case, the accesses stay in the load balancing apparatus. In other words, the load balancing apparatus becomes a bottleneck. On the other hand, when the router 14 distributes and forwards the access to two or more load balancing apparatus, the access forwarded to each load balancing apparatus is not greater than ½ of the access processed by the router 14. Consequently, even when the line speed on the input side (client terminal side) of the router 14 is extremely high such as dozens of Gb/sec, the router 14 distributes the access sent through the line to each load balancing apparatus and the access does not stay inside one load balancing apparatus. The amount of the accesses processed in a certain unit time by all the load balancing apparatus is naturally greater than the amount of the accesses processed by one load balancing apparatus. Therefore, the site 10 can more efficiently process the accesses and can cope with a higher-speed input line.
  • [0042]
    In the network system described above, the router and the load balancing apparatus distribute the load in two stages. However, the network system may well be constituted by routers and load balancing apparatus respectively connected in multiple stages. In this case, because the routers and the load balancing apparatus hierachically connected distribute the load, load balancing is conducted in multiple stages. It is possible, for example, to distribute the load in three stages by the routers connected in two stages and the load balancing apparatus in one stage.
  • [0043]
    Incidentally, the router 14, the load balancing apparatus 15 and 16 and the Web server 17 constituting the network system of the site 10 may be installed in the same place such as in the same building or in a specific area, or may be respectively installed in mutually different places such as in different areas or at remote points. Various communication lines connect these constituent apparatus to one another.
  • [0044]
    Therefore, it is possible to arrange a plurality of Web servers of the site 10 in geographically remote places. Even when a disaster occurs in a specific area, the site 10 can keep the operation by utilizing the Web servers and other apparatuses installed in other areas and reliability of the site can be improved.
  • [0045]
    In the network described above, the 32-bit IP address is set to each apparatus as shown in FIG. 2. In other words, this network employs IPv4 (Internet Protocol version 4) as the communication protocol. However, this network can also employ IPv6 (Internet Protocol version 6) as the communication protocol.
  • [0046]
    The merits acquired when the network employs IPv6 will be explained.
  • [0047]
    The specification of IPv4 permits a router existing in a line to fragment a packet. FIG. 4 shows a mode in which the IPv4 packet is fragmented. The IPv4 packet 100 includes an IP header 101, a layer 4 header such as a TCP header and a payload (data) 103 as shown in the drawing. When the router fragments this IPv4 packet 100, the IPv4 packet is fragmented into two or more IPv4 packets. In FIG. 2, the IPv4 packet 100 is shown fragmented into two IPv4 packets 100 a and 100 b. In this case, the router regards the layer 4 header 102 and the payload 103 as one payload (data) by putting them together, and fragments it into two or more payloads. The first payload among the payloads so fragmented contains the layer 4 header 102 and a part of the payload 103 fragmented into two or more payloads. The first IPv4 packet 100 a among the IPv4 packets fragmented by the router contains the first payload. Therefore, the IPv4 packet 100 a includes the IP header 101, the layer header 102 and the payload 103 a as shown in FIG. 4.
  • [0048]
    On the other hand, the second IPv4 packet 100 b et seq. contains only one of the payloads 103 fragmented. Therefore, the IPv4 packet 100 b includes the IP header 101 and the payload 103 b. The layer 4 header is not included in the IPv4 packet 100 b.
  • [0049]
    When the router 14 of the site 10 distributes a plurality of IPv4 packets so fragmented to the load balancing devices by using the policy routing function, the following problems may occur.
  • [0050]
    It will be assumed, for example, that the router 14 receives the first IPv4 packet 100 a of the IPv4 packets fragmented. The router 14 analyzes the port number of the TCP port of the layer 4 header 102 contained in the IPv4 packet 100 a, for example. The router 14 then recognizes from this port number that the packet corresponds to the HTTP address, for example, and forwards it to the load balancing apparatus 15. Next, it will be assumed that the router 14 receives the second IPv4 packet et seg of the IPv4 packets fragmented. The router 14 likewise attempts to analyze the content of the layer 4 header but cannot correctly analyze it because the IPv4 packet 100 does not contain the layer 4 header. Therefore, there is the possibility that the router 14 fails to correctly forward this packet.
  • [0051]
    In contrast, the specification of IPv6 inhibits fragmentation by a router existing in a line. Generally, a terminal corresponding to IPv6 knows in advance a maximum packet length that can be transmitted, and the specification inhibits fragmentation in the line. Therefore, the problems that might occur during the forward of the IPv4 packet described above do not occur in the forward of the IPv6 packet. In other words, in the network employing IPv6, the router can more flexibly distribute the load.
  • [0052]
    As explained above, the router inside the site allocates the access sent from the client terminal to a plurality of load balancing apparatus and the load to the individual load balancing devices can be reduced. When any fault occurs in the route to one load balancing apparatus, the router can quickly switch the route to another route.
  • [0053]
    It should be further understood by those skilled in the art that although the foregoing description has been made on embodiments of the invention, the invention is not limited thereto and various changes and modifications may be made without departing from the spirit of the invention and the scope of the appended claims.

Claims (19)

    What is claimed is:
  1. 1. A network system comprising:
    a plurality of servers;
    a plurality of load balancing apparatus, each of said load balancing apparatus being connected to two or more of said plurality of servers, receiving an access packet to said plurality of servers and transferring said access packet received to an arbitrary server among said two or more servers connected thereto; and
    at least one routing apparatus connected respectively to said two or more load balancing apparatus among said plurality of load balancing apparatus, and connected to a network, said routing apparatus receiving an access packet to said plurality of servers from said network and forwarding said access packet received to an arbitrary load balancing apparatus among said two or more load balancing apparatus connected thereto.
  2. 2. A network system according to claim 1, wherein each of said load balancing apparatus serially transfers said access packet it receives to each of said two or more servers.
  3. 3. A network system according to claim 1, wherein said routing apparatus stores in advance an arbitrary hash value in association with each of said two or more load balancing apparatus, calculates the hash value by using address information contained in said access packet it receives, and selects said load balancing apparatus associated with the hash value.
  4. 4. A network system according to claim 1, wherein said routing apparatus stores in advance an access kind in association with each of said two or more load balancing apparatus, judges the access kind from header information contained in said access packet it receives, and selects said load balancing apparatus associated with the access kind.
  5. 5. A network system according to claim 1, wherein the same address is set to said plurality of servers, and said routing apparatus receives a plurality of access packets containing said address as a destination address from said network, and distributes and forwards said plurality of access packets to said two or more load balancing apparatus.
  6. 6. A network system according to claim 1, wherein each of said load balancing apparatus has a function of setting VLAN to at least said server connected thereto, and said routing apparatus receives a plurality of access packets containing said address as a destination address from said network, and distributes and forwards said plurality of access packets to said two or more load balancing apparatus.
  7. 7. A network system according to claim 3, wherein said routing apparatus calculates a hash value by using a destination address and a source address contained in said access packet.
  8. 8. A network system according to claim 4, wherein said routing apparatus judges the access kind from a port number of a TCP port of header information contained in said access packet.
  9. 9. A network system according to claim 4, wherein said plurality of servers contain two or more servers for processing either one kind of access and two or more servers for processing the other one kind of access, each of said load balancing apparatus is connected to said two or more servers for processing the same kind of accesses, and said routing apparatus stores a kind of access in association with said load balancing apparatus to which said servers for processing said kind of access are connected.
  10. 10. A method of distributing a plurality of access packets received from a network to a plurality of servers in a network system, said network system including a plurality of servers, a plurality of load balancing apparatus respectively connected to two or more servers among said plurality of servers and at least one routing apparatus connected to said two or more load balancing apparatus of said plurality of load balancing apparatus and to said network, said method comprising the steps of:
    receiving from said network a plurality of access packets containing an address set in common for said plurality of servers as a destination address by said routing apparatus;
    selecting in each of said routing apparatus a load balancing device to be forwarded from among said two or more load balancing apparatus for each of said access packets received, forwarding each of said access packets, and distributing and forwarding said plurality of access packets to said two or more load balancing apparatus;
    receiving each of said access packets by each of said load balancing apparatus; and
    selecting an arbitrary server from among said two or more servers for each of said access packets received by each of said load balancing apparatus, and transferring said access packet to distribute and transfer said plurality of access packets to said two or more servers.
  11. 11. A distributing method according to claim 10, wherein said step of selecting said server by each of said load balancing apparatus serially selects said two or more servers.
  12. 12. A distributing method according to claim 10, wherein said step of selecting said load balancing apparatus by each of said routing apparatus associates in advance an arbitrary hash value with each of said two or more load balancing apparatus by each of said routing apparatus, calculates the hash value by using address information contained in each of said access packets, and selects said load balancing apparatus associated with the hash value.
  13. 13. A distributing method according to claim 10, wherein said step of selecting said load balancing apparatus by each of said routing apparatus associates in advance a kind of access with each of said two or more load balancing apparatus by each of said routing apparatus, judges the kind of access from header information contained in each of said access packets and selects said load balancing apparatus associated with the kind of access.
  14. 14. A distributing method according to claim 10, which further comprises the step of setting VLAN on the server side by each of said load balancing apparatus, and setting the same address to said respective VLAN to set the same address to said plurality of servers.
  15. 15. A method of processing an access request packet in an information service site, said information service site including a plurality of servers, a plurality of load balancing apparatus respectively connected to two more of said plurality of servers, and at least one routing apparatus connected to said two or more load balancing apparatus among said plurality of load balancing apparatus and to a network, for receiving access request packets transmitted from a plurality of client devices through said network and providing services to said plurality of client devices, said processing method comprising the steps of:
    setting the same address for said plurality of servers;
    receiving a plurality of access request packets containing said address as a destination address from said network by said routing apparatus;
    selecting said load balancing apparatus to be forwarded from said two or more load balancing apparatus for each of said access request packets so received, and forwarding each of said access request packets by said routing apparatus;
    receiving each of said access request packets by each of said load balancing apparatus;
    selecting an arbitrary server from said two or more servers for each access request packet so received by each of said load balancing apparatus, and transferring said access request packet; and
    receiving and processing each of said access request packet by each of said servers.
  16. 16. A processing method according to claim 15, wherein said step of selecting said servers in each of said load balancing apparatus serially selects said two or more servers.
  17. 17. A processing method according to claim 15, wherein said step of selecting said load balancing apparatus by each of said load balancing apparatus associates in advance an arbitrary hash value with each of said two or more load balancing apparatus in each of said routing apparatus, calculates the hash value by using address information contained in each of said access request packets and selects said load balancing apparatus associated with the hash value.
  18. 18. A processing method according to claim 15, wherein said step of selecting said servers in each of said load balancing apparatus associates in advance an access kind with each of said two or more load balancing apparatus, judges the access kind from header information contained in each of said access request packets, and selects said load balancing apparatus associated with the access kind.
  19. 19. A processing method according to claim 15, wherein said step of setting the same address for said plurality of servers sets VLAN on the server side by each of said load balancing apparatus, and sets the same address to each of said VLAN.
US10189468 2001-07-09 2002-07-08 Network system and method of distributing accesses to a plurality of server apparatus in the network system Abandoned US20030009559A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2001-208181 2001-07-09
JP2001208181 2001-07-09

Publications (1)

Publication Number Publication Date
US20030009559A1 true true US20030009559A1 (en) 2003-01-09

Family

ID=19044054

Family Applications (1)

Application Number Title Priority Date Filing Date
US10189468 Abandoned US20030009559A1 (en) 2001-07-09 2002-07-08 Network system and method of distributing accesses to a plurality of server apparatus in the network system

Country Status (1)

Country Link
US (1) US20030009559A1 (en)

Cited By (56)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030108052A1 (en) * 2001-12-06 2003-06-12 Rumiko Inoue Server load sharing system
US20040075626A1 (en) * 2002-07-23 2004-04-22 Jun-Young Lee Device and method for driving plasma display panel
US20040117476A1 (en) * 2002-12-17 2004-06-17 Doug Steele Method and system for performing load balancing across control planes in a data center
US20040193388A1 (en) * 2003-03-06 2004-09-30 Geoffrey Outhred Design time validation of systems
US20040268358A1 (en) * 2003-06-30 2004-12-30 Microsoft Corporation Network load balancing with host status information
US20040264481A1 (en) * 2003-06-30 2004-12-30 Darling Christopher L. Network load balancing with traffic routing
US20040267920A1 (en) * 2003-06-30 2004-12-30 Aamer Hydrie Flexible network load balancing
US20040268357A1 (en) * 2003-06-30 2004-12-30 Joy Joseph M. Network load balancing with session information
US20050055435A1 (en) * 2003-06-30 2005-03-10 Abolade Gbadegesin Network load balancing with connection manipulation
US20050091078A1 (en) * 2000-10-24 2005-04-28 Microsoft Corporation System and method for distributed management of shared computers
US20050125212A1 (en) * 2000-10-24 2005-06-09 Microsoft Corporation System and method for designing a logical model of a distributed computer system and deploying physical resources according to the logical model
US20050138626A1 (en) * 2003-12-17 2005-06-23 Akihisa Nagami Traffic control apparatus and service system using the same
US20060013147A1 (en) * 2004-05-03 2006-01-19 Level 3 Communications, Inc. Registration redirect server
WO2006072114A2 (en) 2004-12-31 2006-07-06 Level 3 Communications, Inc. Geo-locating load balancing
US20060195698A1 (en) * 2005-02-25 2006-08-31 Microsoft Corporation Receive side scaling with cryptographically secure hashing
US20060209787A1 (en) * 2005-03-15 2006-09-21 Fujitsu Limited Load distributing apparatus and load distributing method
US20060271341A1 (en) * 2003-03-06 2006-11-30 Microsoft Corporation Architecture for distributed computing system and automated design, deployment, and management of distributed applications
US20070006218A1 (en) * 2005-06-29 2007-01-04 Microsoft Corporation Model-based virtual system provisioning
US20070016393A1 (en) * 2005-06-29 2007-01-18 Microsoft Corporation Model-based propagation of attributes
US20070112847A1 (en) * 2005-11-02 2007-05-17 Microsoft Corporation Modeling IT operations/policies
US20070192477A1 (en) * 2002-09-11 2007-08-16 Bellsouth Intellectual Property Corporation Application services gateway
US20080016153A1 (en) * 1996-06-12 2008-01-17 Mount Hamilton Partners, Llc System and Method for Generating a Modified Web Page by Inline Code Insertion in Response to an Information Request From a Client Computer
US20080059214A1 (en) * 2003-03-06 2008-03-06 Microsoft Corporation Model-Based Policy Application
US20080256083A1 (en) * 2007-04-10 2008-10-16 Apertio Limited Alias hiding in network data repositories
US20080253403A1 (en) * 2007-04-10 2008-10-16 Apertio Limited Nomadic subscriber data system
US20080256082A1 (en) * 2007-04-10 2008-10-16 Apertio Limited Data access in distributed server systems
US20080256020A1 (en) * 2007-04-10 2008-10-16 Apertio Limited Variant entries in network data repositories
US20080273461A1 (en) * 2005-03-29 2008-11-06 International Business Machines Corporation Network system, traffic balancing method, network monitoring device and host
US20080288622A1 (en) * 2007-05-18 2008-11-20 Microsoft Corporation Managing Server Farms
US20090006047A1 (en) * 2007-06-26 2009-01-01 Microsoft Corporation Real-Time Rendering of Light-Scattering Media
WO2010019629A2 (en) * 2008-08-11 2010-02-18 Microsoft Corporation Distributed load balancer
US7669235B2 (en) 2004-04-30 2010-02-23 Microsoft Corporation Secure domain join for computing devices
US7684964B2 (en) 2003-03-06 2010-03-23 Microsoft Corporation Model and system state synchronization
US7778422B2 (en) 2004-02-27 2010-08-17 Microsoft Corporation Security associations for devices
US7797147B2 (en) 2005-04-15 2010-09-14 Microsoft Corporation Model-based system monitoring
US7802144B2 (en) 2005-04-15 2010-09-21 Microsoft Corporation Model-based system monitoring
US20100248683A1 (en) * 2004-12-09 2010-09-30 Level 3 Communications, Inc. Systems and Methods for Third Party Emergency Call Termination
WO2010138936A3 (en) * 2009-05-28 2011-03-03 Microsoft Corporation Load balancing across layer-2 domains
US20110149737A1 (en) * 2009-12-23 2011-06-23 Manikam Muthiah Systems and methods for managing spillover limits in a multi-core system
US20110153831A1 (en) * 2009-12-23 2011-06-23 Rishi Mutnuru Systems and methods for mixed mode of ipv6 and ipv4 dns of global server load balancing
US20110161500A1 (en) * 2009-12-23 2011-06-30 Sreedhar Yengalasetti Systems and methods for managing ports for rtsp across cores in a multi-core system
US20110283013A1 (en) * 2010-05-14 2011-11-17 Grosser Donald B Methods, systems, and computer readable media for stateless load balancing of network traffic flows
US20130132532A1 (en) * 2011-11-15 2013-05-23 Nicira, Inc. Load balancing and destination network address translation middleboxes
US8489728B2 (en) 2005-04-15 2013-07-16 Microsoft Corporation Model-based system monitoring
US8768350B2 (en) 2004-12-09 2014-07-01 Level 3 Communications, Llc Systems and methods for locating endpoints in a communication network
US20140310391A1 (en) * 2013-04-16 2014-10-16 Amazon Technologies, Inc. Multipath routing in a distributed load balancer
US20140334497A1 (en) * 2011-11-30 2014-11-13 Murata Machinery, Ltd. Relay server and relay communication system
US20150058853A1 (en) * 2009-12-02 2015-02-26 Vmware, Inc. Central switch for coupling virtual desktops to peripheral devices
US8996614B2 (en) * 2011-02-09 2015-03-31 Citrix Systems, Inc. Systems and methods for nTier cache redirection
US9130765B1 (en) * 1996-06-12 2015-09-08 Michael Carringer System and method for generating a modified web page by inline code insertion in response to an information request from a client computer
CN105308929A (en) * 2013-04-16 2016-02-03 亚马逊科技公司 Distribute the load balancer
CN105308931A (en) * 2013-04-16 2016-02-03 亚马逊科技公司 Asymmetric packet flow in a distributed load balancer
US9391716B2 (en) 2010-04-05 2016-07-12 Microsoft Technology Licensing, Llc Data center using wireless communication
US9497039B2 (en) 2009-05-28 2016-11-15 Microsoft Technology Licensing, Llc Agile data center network architecture
US9838482B1 (en) * 2014-12-18 2017-12-05 Amazon Technologies, Inc. Maintaining client/server session affinity through load balancers
US9843557B2 (en) 2004-12-09 2017-12-12 Level 3 Communications, Llc Systems and methods for dynamically registering endpoints in a network

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6259705B1 (en) * 1997-09-22 2001-07-10 Fujitsu Limited Network service server load balancing device, network service server load balancing method and computer-readable storage medium recorded with network service server load balancing program
US20010034792A1 (en) * 2000-03-10 2001-10-25 Swildens Eric Sven-Johan Decrypting load balancing array system
US6490632B1 (en) * 1999-03-18 2002-12-03 3Com Corporation High performance load balancing and fail over support of internet protocol exchange traffic over multiple network interface cards
US20030005116A1 (en) * 2001-06-28 2003-01-02 Chase Jeffrey Scott Method, system and computer program product for hierarchical load balancing
US6580715B1 (en) * 1998-05-04 2003-06-17 Hewlett-Packard Development Company, L.P. Load balancing switch protocols
US6671259B1 (en) * 1999-03-30 2003-12-30 Fujitsu Limited Method and system for wide area network load balancing
US6725253B1 (en) * 1999-10-14 2004-04-20 Fujitsu Limited Load balancing system
US6888797B1 (en) * 1999-05-05 2005-05-03 Lucent Technologies Inc. Hashing-based network load balancing
US6970932B1 (en) * 1999-12-14 2005-11-29 Microsoft Corporation Non-delegable client requests to servers storing local information only
US6987763B2 (en) * 2000-05-04 2006-01-17 Comverse Ltd. Load balancing
US7082122B2 (en) * 2001-12-24 2006-07-25 Innomedia Pte Ltd. Method and system for connecting to a proxy server with the lowest workload through a load balancing proxy server

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6259705B1 (en) * 1997-09-22 2001-07-10 Fujitsu Limited Network service server load balancing device, network service server load balancing method and computer-readable storage medium recorded with network service server load balancing program
US6580715B1 (en) * 1998-05-04 2003-06-17 Hewlett-Packard Development Company, L.P. Load balancing switch protocols
US6490632B1 (en) * 1999-03-18 2002-12-03 3Com Corporation High performance load balancing and fail over support of internet protocol exchange traffic over multiple network interface cards
US6671259B1 (en) * 1999-03-30 2003-12-30 Fujitsu Limited Method and system for wide area network load balancing
US6888797B1 (en) * 1999-05-05 2005-05-03 Lucent Technologies Inc. Hashing-based network load balancing
US6725253B1 (en) * 1999-10-14 2004-04-20 Fujitsu Limited Load balancing system
US6970932B1 (en) * 1999-12-14 2005-11-29 Microsoft Corporation Non-delegable client requests to servers storing local information only
US20010034792A1 (en) * 2000-03-10 2001-10-25 Swildens Eric Sven-Johan Decrypting load balancing array system
US6987763B2 (en) * 2000-05-04 2006-01-17 Comverse Ltd. Load balancing
US20030005116A1 (en) * 2001-06-28 2003-01-02 Chase Jeffrey Scott Method, system and computer program product for hierarchical load balancing
US7082122B2 (en) * 2001-12-24 2006-07-25 Innomedia Pte Ltd. Method and system for connecting to a proxy server with the lowest workload through a load balancing proxy server

Cited By (100)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8601050B2 (en) 1996-06-12 2013-12-03 Michael Carringer System and method for generating a modified web page by inline code insertion in response to an information request from a client computer
US20080016153A1 (en) * 1996-06-12 2008-01-17 Mount Hamilton Partners, Llc System and Method for Generating a Modified Web Page by Inline Code Insertion in Response to an Information Request From a Client Computer
US9130765B1 (en) * 1996-06-12 2015-09-08 Michael Carringer System and method for generating a modified web page by inline code insertion in response to an information request from a client computer
US9021023B2 (en) 1996-06-12 2015-04-28 Smooth Ride, Series 53 Of Allied Security Trust I System and method for generating a modified web page by inline code insertion in response to an information request from a client computer
US20050125212A1 (en) * 2000-10-24 2005-06-09 Microsoft Corporation System and method for designing a logical model of a distributed computer system and deploying physical resources according to the logical model
US20050097097A1 (en) * 2000-10-24 2005-05-05 Microsoft Corporation System and method for distributed management of shared computers
US20050091078A1 (en) * 2000-10-24 2005-04-28 Microsoft Corporation System and method for distributed management of shared computers
US7711121B2 (en) 2000-10-24 2010-05-04 Microsoft Corporation System and method for distributed management of shared computers
US7739380B2 (en) 2000-10-24 2010-06-15 Microsoft Corporation System and method for distributed management of shared computers
US7379458B2 (en) 2001-12-06 2008-05-27 Fujitsu Limited Server load sharing system
US20030108052A1 (en) * 2001-12-06 2003-06-12 Rumiko Inoue Server load sharing system
US20040075626A1 (en) * 2002-07-23 2004-04-22 Jun-Young Lee Device and method for driving plasma display panel
US8060557B2 (en) * 2002-09-11 2011-11-15 At&T Intellectual Property I, Lp Application services gateway
US20070192477A1 (en) * 2002-09-11 2007-08-16 Bellsouth Intellectual Property Corporation Application services gateway
US20040117476A1 (en) * 2002-12-17 2004-06-17 Doug Steele Method and system for performing load balancing across control planes in a data center
US7933983B2 (en) * 2002-12-17 2011-04-26 Hewlett-Packard Development Company, L.P. Method and system for performing load balancing across control planes in a data center
US7890951B2 (en) 2003-03-06 2011-02-15 Microsoft Corporation Model-based provisioning of test environments
US7886041B2 (en) 2003-03-06 2011-02-08 Microsoft Corporation Design time validation of systems
US20060271341A1 (en) * 2003-03-06 2006-11-30 Microsoft Corporation Architecture for distributed computing system and automated design, deployment, and management of distributed applications
US7792931B2 (en) 2003-03-06 2010-09-07 Microsoft Corporation Model-based system provisioning
US20060037002A1 (en) * 2003-03-06 2006-02-16 Microsoft Corporation Model-based provisioning of test environments
US8122106B2 (en) 2003-03-06 2012-02-21 Microsoft Corporation Integrating design, deployment, and management phases for systems
US20040193388A1 (en) * 2003-03-06 2004-09-30 Geoffrey Outhred Design time validation of systems
US7689676B2 (en) 2003-03-06 2010-03-30 Microsoft Corporation Model-based policy application
US7684964B2 (en) 2003-03-06 2010-03-23 Microsoft Corporation Model and system state synchronization
US20080059214A1 (en) * 2003-03-06 2008-03-06 Microsoft Corporation Model-Based Policy Application
US7890543B2 (en) 2003-03-06 2011-02-15 Microsoft Corporation Architecture for distributed computing system and automated design, deployment, and management of distributed applications
US20040264481A1 (en) * 2003-06-30 2004-12-30 Darling Christopher L. Network load balancing with traffic routing
US20050055435A1 (en) * 2003-06-30 2005-03-10 Abolade Gbadegesin Network load balancing with connection manipulation
US20040267920A1 (en) * 2003-06-30 2004-12-30 Aamer Hydrie Flexible network load balancing
US20040268357A1 (en) * 2003-06-30 2004-12-30 Joy Joseph M. Network load balancing with session information
US20040268358A1 (en) * 2003-06-30 2004-12-30 Microsoft Corporation Network load balancing with host status information
US7590736B2 (en) * 2003-06-30 2009-09-15 Microsoft Corporation Flexible network load balancing
US20050138626A1 (en) * 2003-12-17 2005-06-23 Akihisa Nagami Traffic control apparatus and service system using the same
US7778422B2 (en) 2004-02-27 2010-08-17 Microsoft Corporation Security associations for devices
US7669235B2 (en) 2004-04-30 2010-02-23 Microsoft Corporation Secure domain join for computing devices
US9088599B2 (en) 2004-05-03 2015-07-21 Level 3 Communications, Llc Registration redirect server
US20060013147A1 (en) * 2004-05-03 2006-01-19 Level 3 Communications, Inc. Registration redirect server
US8089972B2 (en) * 2004-05-03 2012-01-03 Level 3 Communications, Llc Registration redirect server
US8768350B2 (en) 2004-12-09 2014-07-01 Level 3 Communications, Llc Systems and methods for locating endpoints in a communication network
US9843557B2 (en) 2004-12-09 2017-12-12 Level 3 Communications, Llc Systems and methods for dynamically registering endpoints in a network
US9020105B2 (en) 2004-12-09 2015-04-28 Level 3 Communications, Llc Systems and methods for third party emergency call termination
US20100248683A1 (en) * 2004-12-09 2010-09-30 Level 3 Communications, Inc. Systems and Methods for Third Party Emergency Call Termination
EP1839178A2 (en) * 2004-12-31 2007-10-03 Level 3 Communications, Inc. Geo-locating load balancing
WO2006072114A2 (en) 2004-12-31 2006-07-06 Level 3 Communications, Inc. Geo-locating load balancing
EP1839178A4 (en) * 2004-12-31 2013-10-23 Level 3 Communications Llc Geo-locating load balancing
US7765405B2 (en) * 2005-02-25 2010-07-27 Microsoft Corporation Receive side scaling with cryptographically secure hashing
US20060195698A1 (en) * 2005-02-25 2006-08-31 Microsoft Corporation Receive side scaling with cryptographically secure hashing
US7864750B2 (en) 2005-03-15 2011-01-04 Fujitsu Limited Load distributing apparatus and load distributing method
US20060209787A1 (en) * 2005-03-15 2006-09-21 Fujitsu Limited Load distributing apparatus and load distributing method
US8194553B2 (en) 2005-03-29 2012-06-05 International Business Machines Corporation Network system, traffic balancing method, network monitoring device and host
US20080273461A1 (en) * 2005-03-29 2008-11-06 International Business Machines Corporation Network system, traffic balancing method, network monitoring device and host
US7802144B2 (en) 2005-04-15 2010-09-21 Microsoft Corporation Model-based system monitoring
US7797147B2 (en) 2005-04-15 2010-09-14 Microsoft Corporation Model-based system monitoring
US8489728B2 (en) 2005-04-15 2013-07-16 Microsoft Corporation Model-based system monitoring
US20070006218A1 (en) * 2005-06-29 2007-01-04 Microsoft Corporation Model-based virtual system provisioning
US8549513B2 (en) 2005-06-29 2013-10-01 Microsoft Corporation Model-based virtual system provisioning
US9317270B2 (en) 2005-06-29 2016-04-19 Microsoft Technology Licensing, Llc Model-based virtual system provisioning
US9811368B2 (en) 2005-06-29 2017-11-07 Microsoft Technology Licensing, Llc Model-based virtual system provisioning
US20070016393A1 (en) * 2005-06-29 2007-01-18 Microsoft Corporation Model-based propagation of attributes
US20070112847A1 (en) * 2005-11-02 2007-05-17 Microsoft Corporation Modeling IT operations/policies
US7941309B2 (en) 2005-11-02 2011-05-10 Microsoft Corporation Modeling IT operations/policies
US20080256083A1 (en) * 2007-04-10 2008-10-16 Apertio Limited Alias hiding in network data repositories
US20080253403A1 (en) * 2007-04-10 2008-10-16 Apertio Limited Nomadic subscriber data system
US20080256082A1 (en) * 2007-04-10 2008-10-16 Apertio Limited Data access in distributed server systems
US8402147B2 (en) 2007-04-10 2013-03-19 Apertio Limited Nomadic subscriber data system
US20080256020A1 (en) * 2007-04-10 2008-10-16 Apertio Limited Variant entries in network data repositories
US9112873B2 (en) 2007-04-10 2015-08-18 Apertio Limited Alias hiding in network data repositories
US8140676B2 (en) * 2007-04-10 2012-03-20 Apertio Limited Data access in distributed server systems
US8782085B2 (en) 2007-04-10 2014-07-15 Apertio Limited Variant entries in network data repositories
US8996572B2 (en) 2007-04-10 2015-03-31 Apertio Limited Variant entries in network data repositories
US20080288622A1 (en) * 2007-05-18 2008-11-20 Microsoft Corporation Managing Server Farms
US8190403B2 (en) 2007-06-26 2012-05-29 Microsoft Corporation Real-time rendering of light-scattering media
US20090006047A1 (en) * 2007-06-26 2009-01-01 Microsoft Corporation Real-Time Rendering of Light-Scattering Media
WO2010019629A2 (en) * 2008-08-11 2010-02-18 Microsoft Corporation Distributed load balancer
WO2010019629A3 (en) * 2008-08-11 2010-06-10 Microsoft Corporation Distributed load balancer
US9497039B2 (en) 2009-05-28 2016-11-15 Microsoft Technology Licensing, Llc Agile data center network architecture
WO2010138936A3 (en) * 2009-05-28 2011-03-03 Microsoft Corporation Load balancing across layer-2 domains
US20150058853A1 (en) * 2009-12-02 2015-02-26 Vmware, Inc. Central switch for coupling virtual desktops to peripheral devices
US9639386B2 (en) * 2009-12-02 2017-05-02 Vmware, Inc. Central switch for coupling virtual desktops to peripheral devices
US8825859B2 (en) * 2009-12-23 2014-09-02 Citrix Systems, Inc. System and methods for mixed mode of IPv6 and IPv4 DNS of global server load balancing
US20110161500A1 (en) * 2009-12-23 2011-06-30 Sreedhar Yengalasetti Systems and methods for managing ports for rtsp across cores in a multi-core system
US20110153831A1 (en) * 2009-12-23 2011-06-23 Rishi Mutnuru Systems and methods for mixed mode of ipv6 and ipv4 dns of global server load balancing
US20110149737A1 (en) * 2009-12-23 2011-06-23 Manikam Muthiah Systems and methods for managing spillover limits in a multi-core system
US8635344B2 (en) 2009-12-23 2014-01-21 Citrix Systems, Inc. Systems and methods for managing ports for RTSP across cores in a multi-core system
US9407679B2 (en) 2009-12-23 2016-08-02 Citrix Systems, Inc. Systems and methods for managing ports for RTSP across cores in a multi-core system
US9098335B2 (en) 2009-12-23 2015-08-04 Citrix Systems, Inc. Systems and methods for managing spillover limits in a multi-core system
US9391716B2 (en) 2010-04-05 2016-07-12 Microsoft Technology Licensing, Llc Data center using wireless communication
US20110283013A1 (en) * 2010-05-14 2011-11-17 Grosser Donald B Methods, systems, and computer readable media for stateless load balancing of network traffic flows
US8499093B2 (en) * 2010-05-14 2013-07-30 Extreme Networks, Inc. Methods, systems, and computer readable media for stateless load balancing of network traffic flows
CN103155500A (en) * 2010-05-14 2013-06-12 极进网络公司 Methods, systems, and computer readable media for stateless load balancing of network traffic flows
US8996614B2 (en) * 2011-02-09 2015-03-31 Citrix Systems, Inc. Systems and methods for nTier cache redirection
US20130132532A1 (en) * 2011-11-15 2013-05-23 Nicira, Inc. Load balancing and destination network address translation middleboxes
US9385990B2 (en) * 2011-11-30 2016-07-05 Murata Machinery, Ltd. Relay server and relay communication system
US20140334497A1 (en) * 2011-11-30 2014-11-13 Murata Machinery, Ltd. Relay server and relay communication system
US20140310391A1 (en) * 2013-04-16 2014-10-16 Amazon Technologies, Inc. Multipath routing in a distributed load balancer
CN105308929A (en) * 2013-04-16 2016-02-03 亚马逊科技公司 Distribute the load balancer
CN105264865A (en) * 2013-04-16 2016-01-20 亚马逊科技公司 Multipath routing in a distributed load balancer
CN105308931A (en) * 2013-04-16 2016-02-03 亚马逊科技公司 Asymmetric packet flow in a distributed load balancer
US9838482B1 (en) * 2014-12-18 2017-12-05 Amazon Technologies, Inc. Maintaining client/server session affinity through load balancers

Similar Documents

Publication Publication Date Title
US7035281B1 (en) Wireless provisioning device
US8116307B1 (en) Packet structure for mirrored traffic flow
US6101549A (en) Proxy-based reservation of network resources
US7003555B1 (en) Apparatus and method for domain name resolution
US6650641B1 (en) Network address translation using a forwarding agent
US6628654B1 (en) Dispatching packets from a forwarding agent using tag switching
US7102996B1 (en) Method and system for scaling network traffic managers
US20040177158A1 (en) Network address translation techniques for selective network traffic diversion
US7454489B2 (en) System and method for accessing clusters of servers from the internet network
US6970445B2 (en) Methods and apparatus for supporting session signaling and mobility management in a communications system
US6665304B2 (en) Method and apparatus for providing an integrated cluster alias address
US7328237B1 (en) Technique for improving load balancing of traffic in a data network using source-side related information
US20030055971A1 (en) Providing load balancing in delivering rich media
US7318100B2 (en) Cooperative proxy auto-discovery and connection interception
US7290050B1 (en) Transparent load balancer for network connections
US7379458B2 (en) Server load sharing system
US6829654B1 (en) Apparatus and method for virtual edge placement of web sites
US20050083955A1 (en) Methods and apparatus to support routing of information
US6977896B1 (en) IP communications network system and QoS guaranteeing apparatus
US7480737B2 (en) Technique for addressing a cluster of network servers
US20020176427A1 (en) Gateway apparatus with LAC function
US20030016679A1 (en) Method and apparatus to perform network routing
US20090262741A1 (en) Transparent Provisioning of Services Over a Network
US6327626B1 (en) Method and apparatus for MSS spoofing
US20020010792A1 (en) Method and system for improving network performance by utilizing path selection, path activation, and profiles

Legal Events

Date Code Title Description
AS Assignment

Owner name: HITACHI, LTD., JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:IKEDA, NAOYA;REEL/FRAME:013259/0809

Effective date: 20020821