CN102571998B - Network system and method of address resolution - Google Patents
Network system and method of address resolution Download PDFInfo
- Publication number
- CN102571998B CN102571998B CN201010612114.3A CN201010612114A CN102571998B CN 102571998 B CN102571998 B CN 102571998B CN 201010612114 A CN201010612114 A CN 201010612114A CN 102571998 B CN102571998 B CN 102571998B
- Authority
- CN
- China
- Prior art keywords
- fictitious host
- host computer
- conducting state
- address
- source terminal
- 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.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
- H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/58—Association of routers
- H04L45/586—Association of routers of virtual routers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
A network system and a method of address resolution are provided. The network system includes a network, a plurality of virtual machines, a routing module and a path directory module. Each virtual machine includes an internet protocol (IP) address and N media access control (MAC) addresses, so as to connect the network through N transmission routes. The routing module detects and calculates states of the transmission routes. The path directory module receives and decodes an address resolution protocol (ARP) request presented by at least one source virtual machine to reply path information, which includes N MAC addresses corresponding to an IP address of a destination virtual machine and states of the N transmission routes. Thus, the virtual machines present the ARP request without broadcast, so that the problem of network congestion is solved.
Description
Technical field
The disclosure relates to a kind of network system and address resolution method.
Background technology
In the field such as network service and information transmission, many enterprises (such as company, government bodies, research institution etc.) are provided with many property server (such as the webserver, search server, mail server etc.) respectively according to its remote service provided (or can be described as cloud service), and set up one or more fictitious host computer (virtual machine, VM) on the server to strengthen its function.In order to the running load of load remote service, many enterprises adopt multiple servers and virtual region network (Virtual Local Area Network is called for short VLAN) technology to share running load, to cause the corresponding lifting of the quantity of server.By this, in order to reduce the operation costs of burden, these enterprises just wish the data center (data center) becoming can manage concentratedly by these Server Consolidations, and are integrated the cost overhead reducing server admin and bring by application program or hardware resource.
On the other hand, in Ethernet agreement, source terminal main frame need by address resolution protocol (Address Resolution Protocol when transmission packet information, ARP agreement) broadcast ARP request (ARP request) in the same network segment, use internet protocol address (the Internet Protocol Address utilizing destination main frame, be called for short IP address) inquire about Media Access Control address (the Media Access Control Address of destination main frame, be called for short MAC Address), use and ensure carrying out smoothly of packet communication.
But the server of data center in the same network segment is easily in ten thousand, if multiple host during broadcast ARP request, just may cause network to be jammed in this network segment.Therefore, in the data in heart network, how utilizing the IP address transition of destination main frame to be corresponding MAC Address, and avoid network to be jammed simultaneously, is current problem still to be solved.
Summary of the invention
The disclosure provides a kind of network system, it utilizes route directory module to focus on the address resolution request of fictitious host computer, use the function of address resolution protocol, exempt the problem that network is jammed, also fictitious host computer can be made to change immediately to backup path when the delivering path of current use is interrupted or is excessively jammed, use duration data transmission and do not need to re-start address resolution.
On the other hand, the disclosure provides a kind of address resolution method, it utilizes route directory module to focus on the address resolution request of fictitious host computer, use the function of address resolution protocol, exempt the problem that network is jammed, also fictitious host computer can be made to change immediately to backup path when the delivering path of current use is interrupted or is excessively jammed, use duration data transmission and do not need to re-start address resolution.
The disclosure proposes a kind of network system, includes network, multiple fictitious host computer, routing module and route directory module.Each fictitious host computer comprises procotol (IP) address and N number of medium access control (MAC) address, uses and is connected to network by N number of delivering path, and N is positive integer and N > 1.Routing module can detect and the conducting state of delivering path in computing network system.Route directory module can record the result of calculation of the internet protocol address of fictitious host computer, corresponding Media Access Control address and routing module, and route directory module can receive and the address resolution request that proposes of at least one source terminal fictitious host computer of decoding, and uses return path information.Above-mentioned routing information includes the conducting state of N number of Media Access Control address corresponding to the internet protocol address of destination fictitious host computer and N number of delivering path thereof.
In an embodiment of the present disclosure, above-mentioned route directory module can transmit a time stab to each source terminal fictitious host computer in time returning this routing information, and use after time stab lost efficacy, source terminal fictitious host computer will remove above-mentioned routing information.
From another angle, the disclosure proposes a kind of address resolution method, comprise the following steps: to set multiple fictitious host computer, each fictitious host computer all includes an internet protocol address and N number of Media Access Control address, uses and is connected to network by N number of delivering path.In addition, detect and obtain the conducting state of delivering path.Further, the conducting state of the internet protocol address of fictitious host computer, corresponding N number of Media Access Control address and delivering path is recorded.And, receive and the address resolution request that proposes of at least one source terminal fictitious host computer of decoding, use passback one routing information.Above-mentioned routing information then includes the conducting state of N number of Media Access Control address corresponding to the internet protocol address of destination fictitious host computer and N number of delivering path thereof.
Based on above-mentioned, the fictitious host computer of disclosure embodiment directly can propose address resolution request to path catalogue module, need not broadcast, used the function of address resolution protocol in the network segment, and exempts the problem that network is jammed.On the other hand, the route directory module of the present embodiment can within the valid period of time stab proactive notification fictitious host computer to upgrade the conducting state of delivering path, thus fictitious host computer is changed to backup path immediately when the delivering path of current use is interrupted or is excessively jammed, use duration data transmission and do not need to re-start address resolution.
For above-mentioned feature and advantage of the present disclosure can be become apparent, special embodiment below, and coordinate accompanying drawing to be described in detail below.
Accompanying drawing explanation
Fig. 1 is the schematic diagram of the network system according to the disclosure first embodiment.
Fig. 2 is list and the partial schematic diagram of network system according to the disclosure first embodiment.
Fig. 3 is the flow chart of the address resolution method according to the disclosure first embodiment.
Fig. 4 is that source terminal fictitious host computer and route directory module carry out the list after address resolution and schematic diagram.
Fig. 5 is the list of transmission path P2 when being interrupted and schematic diagram.
Fig. 6 is the partial schematic diagram of the network system according to the disclosure second embodiment.
Fig. 7 is the path list of the network system according to the disclosure second embodiment.
[main element symbol description]
100,600: network system
110: network
120: routing module
130: route directory module
PM, PM1 ~ PM7: entity host (Physical machine)
SW, SW11 ~ SW31: switch
P1 ~ P6: transmission path
R1 ~ R2: delivering path
IP_1 ~ IP_2:IP address
MAC_11 ~ MAC_22:MAC address
T: conducting state
F: broken string state
G1 ~ G3: group
S310 ~ S390: step
Embodiment
With detailed reference to one exemplary embodiment of the present disclosure, the example of described one exemplary embodiment is described in the accompanying drawings.In addition, all may part, in drawings and the embodiments, use the identical or similar portions of the element/component/symbology of identical label.
Fig. 1 is the schematic diagram of the network system 100 according to the disclosure first embodiment.As shown in Figure 1, network system 100 can be used as the data center network (data center network) formed with entity host PM and interior fictitious host computer VM thereof, but this network system 100 should be applied in the network architecture of other types according to its design requirement by application the present embodiment person.Network system 100 comprises network 110, entity host PM, routing module 120 and route directory module 130.The present embodiment utilizes the second layer (Layer 2) network equipment (such as switch SW, but be not limited in this) network 110 (topology of the present embodiment is not limited in this) of composition tree topology (tree topology), and network 110 has a up link (uplink) uses and carry out transfer of data with other network systems.
Each entity host (physical machine) PM of Fig. 1 can be considered different property server, and have the fictitious host computer VM that one or more does not wait according to the service content provided, the fictitious host computer VM quantity comprised in the middle of each entity host PM is fixed with application the present embodiment person.Each fictitious host computer VM has 1 procotol (IP) address and N number of medium access control (MAC) address, make it be connected to switch SW in network 110 respectively by N number of delivering path TR, N is positive integer and N > 1.For example, as shown in Figure 1, entity host PM has 4 delivering path TR, and (that is N equals 4, but be not limited in this) to be connected to network 110, therefore the fictitious host computer VM in it also can possess maximum 4 delivering path TR to be connected to network 110, and each delivering path TR is all to having a MAC Address to carry out transfer of data.
In the present embodiment, routing module 120 is using the second layer (Layer 2) routing server (Routing server) as its implementation.Routing module 120 couples with all switch SW phases in network 110, make it detect and obtain transmission situation and the conducting state of all delivering path TR in network system 100, comprise between switch SW and switch SW and the transmission state of switch SW and entity host PM, use the grouping bang path unifiedly calculating each fictitious host computer VM, and the conducting state of all delivering path TR of dynamic conditioning.Based on above-mentioned teaching, those skilled in the art should know the implementation of routing module 120 voluntarily by inference, do not repeat them here.Route directory module 130 in the present embodiment then using LIST SERVER (Directory server) as implementation, it can record the result of calculation of the IP address of fictitious host computer VM, corresponding N number of MAC Address and routing module 120, and these finish messages are become path list.
In this, focusing on of disclosure embodiment, when not making fictitious host computer VM propose address resolution request (ARP request) with the forms of broadcasting, the interception of the address resolution request of all fictitious host computer VM is also pointed to route directory module 130 by the present embodiment again, and utilize route directory module 130 to focus on the address resolution request of all fictitious host computer VM, use the function of address resolution protocol, and the problem that network is jammed can have been exempted.
On the other hand, route directory module 130 responds in (ARP response) conducting state of N number of MAC Address corresponding to the IP address giving destination fictitious host computer and delivering path corresponding to these MAC Address in address resolution, and fictitious host computer can be made to have the selection of multiple delivering path.In addition, delivering path state change time (such as delivering path be interrupted or load excessive, but not as limit), route directory module 130 will proactive notification fictitious host computer VM to upgrade the conducting state of delivering path, thus fictitious host computer VM can be changed to backup path immediately when the delivering path of current use is interrupted or is excessively jammed, use and continue carry out transfer of data and do not need to re-start address resolution.
Furthermore, please refer to Fig. 2 and Fig. 3, Fig. 2 is the partial schematic diagram of the network system 100 according to the disclosure first embodiment, and Fig. 3 is the flow chart of the address resolution method according to the disclosure first embodiment.For the purpose of simplifying the description, Fig. 2 only illustrates switch SW11 ~ SW22, routing module 120 and the route directory module 130 in entity host PM1 and PM2, network 110.
Please also refer to Fig. 2 and Fig. 3, in step S310, first network system 100 sets the source terminal fictitious host computer SVM being positioned at entity host PM1 and the destination fictitious host computer DVM being positioned at entity host PM2.Fictitious host computer SVM includes 1 IP address ip _ 1 and 2 MAC Address MAC_11, MAC_12, and fictitious host computer DVM also includes 1 IP address ip _ 2 and 2 MAC Address MAC_21, MAC_22, by this, fictitious host computer SVM and DVM is connected to network 110 by 2 different delivering path R1 ~ R2 (that is N equals 2).Those skilled in the art should know, though the present embodiment has the MAC Address of 2 delivering paths and correspondence as an example with each fictitious host computer, may extend to each fictitious host computer yet and have multiple delivering path, the disclosure should as limit.In view of this, as shown in Figure 2, if when source terminal fictitious host computer SVM carries out transfer of data to destination fictitious host computer DVM, grouping can be transmitted via delivering path R1 (delivering path R1 is path P 1, P2 and P3 via switch SW11, SW12) or delivering path R2 (delivering path R2 is path P 4, P5 and P6 via switch SW21, SW22).
What illustrate is, address cache list is had in each fictitious host computer VM (such as source terminal fictitious host computer SVM and destination fictitious host computer DVM), store other known service in this address cache list or carried out the IP address of the fictitious host computer VM linked up and the MAC Address of correspondence, that uses minimizing address resolution protocol carries out number of times.In other embodiments, fictitious host computer VM also can obtain IP address and the MAC Address thereof of the particular virtual main frame VM of conventional service from route directory module 130.In order to the present embodiment is described, the IP address of destination fictitious host computer DVM is only known at this hypothesis source terminal fictitious host computer SVM, but there is no the MAC Address of the other side, therefore still need the MAC Address being obtained destination fictitious host computer DVM by address resolution protocol and route directory module 130.
Then, in step s 320, switch SW11 ~ SW22 that routing module 120 utilizes network 110 all, to detect the transmission situation of every paths P1 ~ P6, uses the conducting state obtaining all delivering path R1 ~ R2.Afterwards, enter step S330, the conducting state of the IP address ip _ 1 ~ IP_2 of all fictitious host computers, Media Access Control address MAC_11 ~ MAC_22 and delivering path R1 ~ R2 is recorded in route directory module 130 by network system 100, to form the path list (as shown shown in (1) in Fig. 2) of data structure.
At this, MAC Address of the delivering path in the list of path corresponding to IP address and conducting state thereof are referred to as the routing information of IP address, (MAC_21, T, MAC_22, the T) that such as will show in (1) corresponding to IP address field IP_2 is called the routing information of IP address ip _ 2, uses simplified characterization.Special instruction, " T " in table (1) conducting state hurdle represents that its delivering path R1 or R2 is conducting state, and " F " then represents that delivering path R1 or R2 is broken string state.By this, the IP address of all fictitious host computers and the routing information of correspondence are just all organized in the list of path by route directory module 130, have used the preparation before address resolution.
When source terminal fictitious host computer SVM (being positioned at entity host PM1) wants to transmit grouping to destination fictitious host computer DVM (being positioned at entity host PM2), and the address cache list of source terminal fictitious host computer SVM is not when having the routing information of IP address ip _ 2 of destination fictitious host computer DVM, just address resolution request is sent to path catalogue module 130.Address resolution request planted agent includes IP address ip _ 2 of destination fictitious host computer DVM, or other information can tabled look-up to the path list of path catalogue module 130.Disclosure embodiment is not limited to only table look-up to path list with IP address, and the information such as the identification code of destination fictitious host computer DVM also can be utilized to table look-up, and the disclosure should not be limited to this.
Next, when step S340, route directory module 130 receives and the address resolution request of the source terminal fictitious host computer SVM that decodes, then IP address ip _ 2 pair path list (that is table (1)) is utilized to table look-up, to obtain the routing information of also IP address back IP_2 to source terminal fictitious host computer SVM.On the other hand, because the routing information of address cache list need with the routing information unification in the path list of route directory module 130 in source terminal fictitious host computer SVM, but the information of path list dynamically will change with the conducting situation of delivering path, therefore the present embodiment adopts time stab (timestamp) to enable routing information consistent.
Specifically, in step S340, time stab (time stab is set to 3 seconds by the present embodiment, but is not limited in this) is passed to source terminal fictitious host computer SVM in the lump with the routing information of IP address ip _ 2.The time length of time stab can mutually be coordinated by route directory module 130 and source terminal fictitious host computer SVM and be set up, or stipulated according to the stability of delivering path, the service item of source terminal fictitious host computer SVM etc. by route directory module 130, the disclosure should as limit.
Then, be that source terminal fictitious host computer SVM and route directory module 130 carry out the list after address resolution and schematic diagram referring to Fig. 3 and Fig. 4, Fig. 4.In step S350, the time stab during address resolution is responded by source terminal fictitious host computer SVM and the routing information of IP address ip _ 2 are recorded in the cache list of address, as shown in the table (2) of Fig. 4.On the other hand, route directory module 130 is that the identification code of entity host PM1 corresponding for source terminal fictitious host computer SVM and time stab are recorded in (as shown in the table (3) of Fig. 1) in the list of path, to learn the fictitious host computer VM within the time stab valid period by this by the mode extending field.
By this, (be also in 3 seconds) within the valid period of time stab, if the conducting state of delivering path R1 ~ R2 is all without change, and under this path data is all effective situation, grouping just can be passed to destination fictitious host computer DVM by source terminal fictitious host computer SVM.Relatively, if before time stab lost efficacy, when the conducting state of delivering path R1 ~ R2 occurs to change (when such as transmission path P2 is interrupted), just step S360 is entered by step S350, route directory module 130 carrys out proactive notification source terminal fictitious host computer SVM according to the conducting state after routing module 120 change, uses the conducting state dynamically updating delivering path in routing information.
This citing with description of step S360, Fig. 5 be transmission path P2 be interrupted time list and schematic diagram.As shown in Figure 5, when transmission path P2 interrupts, switch SW11 just can notify routing module 120 immediately.Routing module 120 utilizes the route operation method of its inside known, once transmission path P2 interrupts, delivering path R1 just interrupts in the lump, and the routing information of delivering path R1 and R2 was just for losing efficacy.Therefore, routing module 120, just by the interrupting information notification path catalogue module 130 of delivering path R1, uses the path list (as shown in the table (5) of Fig. 5) upgrading route directory module 130.In other words, when above-mentioned routing information lost efficacy, the conducting state of delivering path R1 was just labeled as the broken string state " F " of Fig. 5 table (5) by routing module 120 by conducting state " T ".
Next, the entity host PM1 identification code of the entity host identification code field that route directory module 130 utilizes list rear, path to extend, use the source terminal fictitious host computer SVM in proactive notification entity host PM1, and make source terminal fictitious host computer SVM its address cache list is updated to the table (4) of Fig. 5 by the table (2) of Fig. 4.By this, source terminal fictitious host computer SVM just can utilize rapidly another MAC Address MAC_22 and delivering path R2 to continue transmission information, thus does not need to re-start address resolution.
And in other embodiments, if when delivering path R1 is conducting state by state reparation of breaking, the routing information of delivering path R1 is just converted to effectively by inefficacy.Therefore, routing module 120 just can by the conducting state notification path catalogue module 130 of delivering path R1.The source terminal fictitious host computer SVM of route directory module 130 just in proactive notification entity host PM1, uses the address cache list upgrading source terminal fictitious host computer SVM.By this, source terminal fictitious host computer SVM just can select the best transmission approach between destination fictitious host computer DVM in delivering path R1 and R2.
On the other hand, go back to the step S370 of Fig. 3, within the valid period of time stab, because destination fictitious host computer DVM because fictitious host computer migration (VM migration) or other factors, thus may cause the routing information mistake of source terminal fictitious host computer SVM and grouping correctly cannot be sent to destination fictitious host computer DVM (being also called that routing information is invalid).By this, when before time stab lost efficacy, routing information becomes invalid, just need to re-start step S340 to re-start address resolution action.
If after time stab lost efficacy, the conducting state of delivering path R1 ~ R2 there is no change, and path data is in effective situation, just from step S350 through step S370 to enter step S380, the routing information of IP address ip _ 2 in the cache list of address just can be deleted by source terminal fictitious host computer SVM, and the time stab of the entity host identification code at list rear, path and inefficacy is also deleted by route directory module 390 in step S390.In view of this, if source terminal fictitious host computer SVM continues transmission information, just need to re-start address resolution action, use and enable the routing information of address cache list and path list consistent.
Whether the routing module 120 of disclosure embodiment only might not adjust the conducting state of delivering path according to the interruption of transmission path, also can carry out the conducting state of dynamic conditioning delivering path according to the inline load of transmission path.In other embodiments, when the inline load of transmission path is greater than load threshold time, the delivering path conducting state comprising this transmission path just can be labeled as broken string by routing module 120, again via route directory module 130 proactive notification fictitious host computer VM, fictitious host computer VM can be added to utilize another delivering path to carry out transmission of information, reaches the function recalculating load balance (load balance recalculation) by this.
In addition, due to source terminal fictitious host computer SVM can time stab lost efficacy after by routing information delete, if but the information required time transmitted is greater than time stab time, fictitious host computer just needs to re-start address resolution action.By this, when source terminal fictitious host computer SVM terminates in a upper time stab and again proposes same address resolution request, the route directory module 130 of the present embodiment will extend the effective time of next time stab (in the present embodiment, the effective time of time stab just doubles by route directory module, but be not limited in this), use the validity increasing routing information.
Relatively, when routing information lost efficacy (when holding fictitious host computer DVM to carry out fictitious host computer migration for the purpose of in the present embodiment before a upper time stab terminates, but be not limited in this), and when source terminal fictitious host computer SVM proposes same address resolution request again (that is the step S370 of Fig. 3 is to step S340), the probability that expression destination fictitious host computer DVM carries out fictitious host computer migration is higher, therefore route directory module 130 just can shorten the effective time of next time stab (in the present embodiment, the effective time of time stab reduces by half by route directory module, but be not limited in this), use continuous updating routing information.
Moreover, path list due to route directory module 130 must be positioned at the entity host identification code of all fictitious host computers of time stab valid period at list rear, path record, the present embodiment carrys out the cache field after realizing route list to link list data structure.But connect list data structure and have two shortcomings, first is along with accumulated time, the time stab needing to be recorded in entity host identification code in data structure and correspondence gets more and more, and cache field is also thereupon increasing.In the data center network of fictitious host computer with 1,000,000, therefore link list data structure will grow up huge, (the list rear, path of the present embodiment extends at most 20 groups of cache fields to make server memory be difficult to load, but be not limited in this), as shown in the table (6) of Fig. 6 and Fig. 7, Fig. 6 is the partial schematic diagram of the network system 600 according to the disclosure second embodiment, and Fig. 7 is the path list of the network system according to the disclosure second embodiment.Another shortcoming is then when delivering path is invalid, and route directory module 130 needs to issue a separate notice all entity host in cache field, and this action needs a lot of time, and wastes the frequency range of data center network.
The entity host be positioned under same switch is divided into same a group (such as the entity host PM1 ~ PM3 under switch SW11 to be divided into group G1 by disclosure embodiment, entity host PM3 ~ PM5 under switch SW12 is divided into group G2, and the entity host PM6 ~ PM7 under switch SW13 is divided into group G3).Then, the extension field at its list rear, path carries out whole also (shown to table (7) by the table (6) of Fig. 7) by route directory module 130, by in same row and be that the entity host identification code of same a group replaces with this group of corresponding switch ip address, whole and the IP address of switch SW11 for table (7) of the identification code such as showing fictitious host computer PM1 and PM2 of (6), the identification code will show fictitious host computer PM3 and PM5 of (6) is whole and be the IP address of the switch SW12 showing (7).By this, route directory module 130 just can utilize switch SW11 and SW12 to broadcast the entity host PM1 ~ PM3 under it and PM3 ~ PM5, uses proactive notification fictitious host computer to upgrade the conducting state of delivering path.Other thin portion flow processs of the present embodiment comprise in the above-described embodiments, therefore do not repeat them here.
In sum, disclosure embodiment utilizes route directory module 130 to focus on the address resolution request of all fictitious host computer VM, has used the function of address resolution protocol, and can exempt the problem that network is jammed.On the other hand, the route directory module 130 of the present embodiment can proactive notification fictitious host computer VM to upgrade the conducting state of delivering path, thus fictitious host computer VM can be changed to backup path immediately when the delivering path of current use is interrupted or is excessively jammed, use duration data transmission and do not need to re-start address resolution.
Although the disclosure with embodiment openly as above; so itself and be not used to limit the disclosure; those skilled in the art are not departing from spirit and scope of the present disclosure, and when doing a little change and retouching, therefore protection range of the present disclosure is when being as the criterion depending on the appended claims person of defining.
Claims (19)
1. a network system, comprising:
One network;
Multiple fictitious host computer, each fictitious host computer comprises a procotol IP address and N number of Media Access Control address, uses and is connected to this network by N number of delivering path, and wherein N is positive integer and N>1;
One routing module, in order to detect and to calculate the conducting state of these delivering paths; And
One route directory module, in order to record this internet protocol address of these fictitious host computers, corresponding N number of Media Access Control address and the result of calculation of this routing module, and this route directory module receives and at least one source terminal fictitious host computer of decoding one of to propose address resolution request, use passback one routing information, wherein this routing information comprises the conducting state of N number of Media Access Control address corresponding to this internet protocol address of a destination fictitious host computer and N number of delivering path thereof, this source terminal fictitious host computer be these fictitious host computers one of them, and this destination fictitious host computer is these fictitious host computers wherein another,
Wherein this route directory module transmits a time stab to each source terminal fictitious host computer in time returning this routing information, and wherein this source terminal fictitious host computer was after this time stab lost efficacy, and removed this routing information,
A wherein entity host identification code at this each source terminal fictitious host computer place of route directory module record and this time stab of correspondence, and after this time stab lost efficacy, remove this time stab of this entity host identification code and correspondence,
Wherein when these delivering paths conducting state change and this time stab not yet lost efficacy time, this each source terminal fictitious host computer of route directory module proactive notification is to upgrade the conducting state of the N number of delivering path in this routing information.
2. network system as claimed in claim 1, wherein this routing module detects and carrys out the conducting state of these delivering paths of dynamic conditioning according to the transmission situation of these delivering paths.
3. network system as claimed in claim 2, wherein the conducting state of these delivering paths interrupted is labeled as broken string state by this routing module, and the conducting state of these delivering paths of conducting is labeled as conducting state.
4. network system as claimed in claim 2, the conducting state that wherein inline load is greater than these delivering paths of a threshold value by this routing module is labeled as broken string state, and conducting state inline load being less than these delivering paths of this threshold value is labeled as conducting state.
5. network system as claimed in claim 2, wherein this routing module was when this routing information lost efficacy, and the conducting state of these corresponding for this routing information delivering paths is labeled as broken string state.
6. network system as claimed in claim 1, wherein when this source terminal fictitious host computer terminates in a upper time stab and again proposes this address resolution request, this route directory module extends the effective time of next time stab.
7. network system as claimed in claim 1, wherein when this routing information lost efficacy before a upper time stab terminates, and when this source terminal fictitious host computer proposes this address resolution request again, this route directory module shortens the effective time of next time stab.
8. network system as claimed in claim 1, wherein this network also comprises multiple switch, and these fictitious host computers under same switch are divided into same a group, and an internet protocol address of this switch corresponding to this route directory module record this group of fictitious host computers is to replace these entity host identification codes of these source terminal fictitious host computers of same group, with broadcasted by this switch and the conducting state upgrading the N number of delivering path in this routing information to these fictitious host computers with group.
9. network system as claimed in claim 1, wherein each fictitious host computer has an address cache list, in order to store other known service or to have carried out these routing informations of these fictitious host computers of linking up.
10. an address resolution method, comprising:
Set multiple fictitious host computer, wherein each fictitious host computer comprises an internet protocol address and N number of Media Access Control address, uses and is connected to a network by N number of delivering path, and N is positive integer and N>1;
Detect and obtain the conducting state of these delivering paths;
Record the conducting state of this internet protocol address of these fictitious host computers, corresponding N number of Media Access Control address and these delivering paths; And
Receive and the address resolution request that proposes of at least one source terminal fictitious host computer of decoding, use passback one routing information, wherein this routing information comprises the conducting state of N number of Media Access Control address corresponding to this internet protocol address of a destination fictitious host computer and N number of delivering path thereof, this source terminal fictitious host computer be these fictitious host computers one of them, and this destination fictitious host computer is these fictitious host computers wherein another
When returning this routing information, transmit a time stab to each source terminal fictitious host computer, wherein this source terminal fictitious host computer was after this time stab lost efficacy, and removed this routing information,
Record an entity host identification code at each source terminal fictitious host computer place and the time stab of correspondence, and after this time stab lost efficacy, remove the time stab of this entity host identification code and correspondence,
When the conducting state of these delivering paths changes and this time stab not yet lost efficacy, proactive notification also upgrades the conducting state of the N number of delivering path in this routing information.
11. address resolution methods as claimed in claim 10, detect and the conducting state obtaining these delivering paths also comprises:
Detect and carry out the conducting state of these delivering paths of dynamic conditioning according to the transmission situation of these delivering paths.
12. address resolution methods as claimed in claim 11, wherein the conducting state of these delivering paths of dynamic conditioning also comprises:
The conducting state of these delivering paths of line failure is labeled as broken string, and the conducting state of these delivering paths successful for line is labeled as conducting.
13. address resolution methods as claimed in claim 11, wherein the conducting state of these delivering paths of dynamic conditioning also comprises:
Conducting state inline load being greater than these delivering paths of a threshold value is labeled as broken string, and conducting state inline load being less than these delivering paths of this threshold value is labeled as conducting.
14. address resolution methods as claimed in claim 11, wherein the conducting state of these delivering paths of dynamic conditioning also comprises:
When this routing information lost efficacy, the conducting state of these corresponding for this routing information delivering paths was labeled as broken string.
15. address resolution methods as claimed in claim 10, also comprise:
When this source terminal fictitious host computer terminates in a upper time stab and again proposes this address resolution request, extend the effective time of next time stab.
16. address resolution methods as claimed in claim 10, also comprise:
When this routing information lost efficacy before a upper time stab terminates, and when this source terminal fictitious host computer proposes this address resolution request again, shorten the effective time of next time stab.
17. address resolution methods as claimed in claim 10, wherein this network also comprises multiple switch, and these fictitious host computers under same switch are divided into same a group, and the internet protocol address recording this switch corresponding to this group of fictitious host computer is to replace these entity host identification codes of this source terminal fictitious host computer of same group, with broadcasted by this switch and the conducting state upgrading the N number of delivering path in this routing information to these fictitious host computers with group.
18. address resolution methods as claimed in claim 10, wherein each fictitious host computer has an address cache list, in order to store other known service or to have carried out these routing informations of these fictitious host computers of linking up.
19. 1 kinds of network systems, comprising:
One network;
Multiple fictitious host computer, each fictitious host computer comprises an internet protocol address and N number of Media Access Control address, uses and is connected to this network by N number of delivering path, and wherein N is positive integer and N>1;
Multiple switch, is arranged in this network, and these fictitious host computers wherein under same switch are same a group;
One routing module, in order to detect and to calculate the conducting state of these delivering paths; And
One route directory module, in order to receive and at least one source terminal fictitious host computer of decoding one of to propose address resolution request, use the entity host identification code that records this source terminal fictitious host computer place and return a routing information, wherein this routing information comprises the conducting state of N number of Media Access Control address corresponding to this internet protocol address of a destination fictitious host computer and N number of delivering path thereof, wherein
When these source terminal fictitious host computers are positioned at same a group, an internet protocol address of this switch that this route directory module record this group is corresponding to replace these entity host identification codes of these source terminal fictitious host computers of this group,
Wherein this route directory module records an entity host identification code and a time stab at each source terminal fictitious host computer place in time returning this routing information, and transmit this time stab to this source terminal fictitious host computer, wherein after this time stab lost efficacy, each source terminal fictitious host computer removes this routing information, and this entity host identification code of this route directory module removal and this time stab
Wherein when these delivering paths conducting state change and this time stab not yet lost efficacy time, this this switch corresponding to this time stab of route directory module proactive notification, uses and upgrades should these routing informations of this group of source terminal fictitious host computers of switch.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US12/968,286 US8521884B2 (en) | 2010-12-15 | 2010-12-15 | Network system and method of address resolution |
| US12/968,286 | 2010-12-15 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102571998A CN102571998A (en) | 2012-07-11 |
| CN102571998B true CN102571998B (en) | 2014-12-24 |
Family
ID=46235921
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010612114.3A Active CN102571998B (en) | 2010-12-15 | 2010-12-29 | Network system and method of address resolution |
Country Status (3)
| Country | Link |
|---|---|
| US (1) | US8521884B2 (en) |
| CN (1) | CN102571998B (en) |
| TW (1) | TWI441499B (en) |
Families Citing this family (86)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9716672B2 (en) | 2010-05-28 | 2017-07-25 | Brocade Communications Systems, Inc. | Distributed configuration management for virtual cluster switching |
| US9769016B2 (en) | 2010-06-07 | 2017-09-19 | Brocade Communications Systems, Inc. | Advanced link tracking for virtual cluster switching |
| US9461840B2 (en) | 2010-06-02 | 2016-10-04 | Brocade Communications Systems, Inc. | Port profile management for virtual cluster switching |
| US8989186B2 (en) | 2010-06-08 | 2015-03-24 | Brocade Communication Systems, Inc. | Virtual port grouping for virtual cluster switching |
| US8867552B2 (en) | 2010-05-03 | 2014-10-21 | Brocade Communications Systems, Inc. | Virtual cluster switching |
| US9270486B2 (en) | 2010-06-07 | 2016-02-23 | Brocade Communications Systems, Inc. | Name services for virtual cluster switching |
| US9001824B2 (en) | 2010-05-18 | 2015-04-07 | Brocade Communication Systems, Inc. | Fabric formation for virtual cluster switching |
| US9246703B2 (en) | 2010-06-08 | 2016-01-26 | Brocade Communications Systems, Inc. | Remote port mirroring |
| US9628293B2 (en) | 2010-06-08 | 2017-04-18 | Brocade Communications Systems, Inc. | Network layer multicasting in trill networks |
| US9608833B2 (en) | 2010-06-08 | 2017-03-28 | Brocade Communications Systems, Inc. | Supporting multiple multicast trees in trill networks |
| US9806906B2 (en) | 2010-06-08 | 2017-10-31 | Brocade Communications Systems, Inc. | Flooding packets on a per-virtual-network basis |
| US9807031B2 (en) | 2010-07-16 | 2017-10-31 | Brocade Communications Systems, Inc. | System and method for network configuration |
| DE102010052394B4 (en) * | 2010-11-24 | 2019-01-03 | Kuka Roboter Gmbh | Robot system with a robot and two alternately connectable with these devices and methods for changing these facilities |
| US9270572B2 (en) | 2011-05-02 | 2016-02-23 | Brocade Communications Systems Inc. | Layer-3 support in TRILL networks |
| US8948056B2 (en) | 2011-06-28 | 2015-02-03 | Brocade Communication Systems, Inc. | Spanning-tree based loop detection for an ethernet fabric switch |
| US9401861B2 (en) | 2011-06-28 | 2016-07-26 | Brocade Communications Systems, Inc. | Scalable MAC address distribution in an Ethernet fabric switch |
| US9736085B2 (en) | 2011-08-29 | 2017-08-15 | Brocade Communications Systems, Inc. | End-to end lossless Ethernet in Ethernet fabric |
| US9590820B1 (en) * | 2011-09-02 | 2017-03-07 | Juniper Networks, Inc. | Methods and apparatus for improving load balancing in overlay networks |
| US8798086B2 (en) * | 2011-09-23 | 2014-08-05 | Alcatel Lucent | Time-preserved transmissions in asynchronous virtual machine replication |
| US9699117B2 (en) | 2011-11-08 | 2017-07-04 | Brocade Communications Systems, Inc. | Integrated fibre channel support in an ethernet fabric switch |
| US9450870B2 (en) | 2011-11-10 | 2016-09-20 | Brocade Communications Systems, Inc. | System and method for flow management in software-defined networks |
| US8995272B2 (en) | 2012-01-26 | 2015-03-31 | Brocade Communication Systems, Inc. | Link aggregation in software-defined networks |
| US9742693B2 (en) | 2012-02-27 | 2017-08-22 | Brocade Communications Systems, Inc. | Dynamic service insertion in a fabric switch |
| US9154416B2 (en) | 2012-03-22 | 2015-10-06 | Brocade Communications Systems, Inc. | Overlay tunnel in a fabric switch |
| US9374301B2 (en) | 2012-05-18 | 2016-06-21 | Brocade Communications Systems, Inc. | Network feedback in software-defined networks |
| US10277464B2 (en) | 2012-05-22 | 2019-04-30 | Arris Enterprises Llc | Client auto-configuration in a multi-switch link aggregation |
| CN104272668B (en) | 2012-05-23 | 2018-05-22 | 博科通讯系统有限公司 | Layer 3 covers gateway |
| TWI470550B (en) * | 2012-06-26 | 2015-01-21 | Wistron Corp | Communication method of virtual machines and server-end system |
| US9602430B2 (en) | 2012-08-21 | 2017-03-21 | Brocade Communications Systems, Inc. | Global VLANs for fabric switches |
| CN103795815A (en) * | 2012-10-29 | 2014-05-14 | 英业达科技有限公司 | Network communication system and network communication method |
| US9401872B2 (en) | 2012-11-16 | 2016-07-26 | Brocade Communications Systems, Inc. | Virtual link aggregations across multiple fabric switches |
| US9413691B2 (en) | 2013-01-11 | 2016-08-09 | Brocade Communications Systems, Inc. | MAC address synchronization in a fabric switch |
| US9548926B2 (en) | 2013-01-11 | 2017-01-17 | Brocade Communications Systems, Inc. | Multicast traffic load balancing over virtual link aggregation |
| US9350680B2 (en) | 2013-01-11 | 2016-05-24 | Brocade Communications Systems, Inc. | Protection switching over a virtual link aggregation |
| US10180851B2 (en) * | 2013-01-14 | 2019-01-15 | Cisco Technology, Inc. | Detection of unauthorized use of virtual resources |
| US9565113B2 (en) | 2013-01-15 | 2017-02-07 | Brocade Communications Systems, Inc. | Adaptive link aggregation and virtual link aggregation |
| KR101978173B1 (en) | 2013-01-18 | 2019-05-14 | 삼성전자주식회사 | Method of transmitting data packet by contents provider in a content centric network and the contents provider |
| US9565099B2 (en) | 2013-03-01 | 2017-02-07 | Brocade Communications Systems, Inc. | Spanning tree in fabric switches |
| WO2014145750A1 (en) | 2013-03-15 | 2014-09-18 | Brocade Communications Systems, Inc. | Scalable gateways for a fabric switch |
| US9699001B2 (en) | 2013-06-10 | 2017-07-04 | Brocade Communications Systems, Inc. | Scalable and segregated network virtualization |
| US9565028B2 (en) | 2013-06-10 | 2017-02-07 | Brocade Communications Systems, Inc. | Ingress switch multicast distribution in a fabric switch |
| CN104426816B (en) * | 2013-08-19 | 2018-08-21 | 华为技术有限公司 | A kind of virtual machine communication method and device |
| US9531676B2 (en) | 2013-08-26 | 2016-12-27 | Nicira, Inc. | Proxy methods for suppressing broadcast traffic in a network |
| US9806949B2 (en) | 2013-09-06 | 2017-10-31 | Brocade Communications Systems, Inc. | Transparent interconnection of Ethernet fabric switches |
| EP2854377B1 (en) * | 2013-09-27 | 2016-07-13 | Alcatel Lucent | A method for centralized address resolution |
| US10904201B1 (en) * | 2013-10-11 | 2021-01-26 | Cisco Technology, Inc. | Updating distributed caches in network devices in the event of virtual machine changes in a virtualized network environment |
| US9977685B2 (en) * | 2013-10-13 | 2018-05-22 | Nicira, Inc. | Configuration of logical router |
| US9912612B2 (en) * | 2013-10-28 | 2018-03-06 | Brocade Communications Systems LLC | Extended ethernet fabric switches |
| US9548873B2 (en) | 2014-02-10 | 2017-01-17 | Brocade Communications Systems, Inc. | Virtual extensible LAN tunnel keepalives |
| US10581758B2 (en) | 2014-03-19 | 2020-03-03 | Avago Technologies International Sales Pte. Limited | Distributed hot standby links for vLAG |
| US10476698B2 (en) | 2014-03-20 | 2019-11-12 | Avago Technologies International Sales Pte. Limited | Redundent virtual link aggregation group |
| US9893988B2 (en) | 2014-03-27 | 2018-02-13 | Nicira, Inc. | Address resolution using multiple designated instances of a logical router |
| US9413644B2 (en) | 2014-03-27 | 2016-08-09 | Nicira, Inc. | Ingress ECMP in virtual distributed routing environment |
| US10063473B2 (en) | 2014-04-30 | 2018-08-28 | Brocade Communications Systems LLC | Method and system for facilitating switch virtualization in a network of interconnected switches |
| US9800471B2 (en) | 2014-05-13 | 2017-10-24 | Brocade Communications Systems, Inc. | Network extension groups of global VLANs in a fabric switch |
| US10616108B2 (en) | 2014-07-29 | 2020-04-07 | Avago Technologies International Sales Pte. Limited | Scalable MAC address virtualization |
| US9544219B2 (en) | 2014-07-31 | 2017-01-10 | Brocade Communications Systems, Inc. | Global VLAN services |
| US9807007B2 (en) | 2014-08-11 | 2017-10-31 | Brocade Communications Systems, Inc. | Progressive MAC address learning |
| US9768980B2 (en) | 2014-09-30 | 2017-09-19 | Nicira, Inc. | Virtual distributed bridging |
| US10511458B2 (en) | 2014-09-30 | 2019-12-17 | Nicira, Inc. | Virtual distributed bridging |
| US10250443B2 (en) | 2014-09-30 | 2019-04-02 | Nicira, Inc. | Using physical location to modify behavior of a distributed virtual network element |
| US10020960B2 (en) | 2014-09-30 | 2018-07-10 | Nicira, Inc. | Virtual distributed bridging |
| US9524173B2 (en) | 2014-10-09 | 2016-12-20 | Brocade Communications Systems, Inc. | Fast reboot for a switch |
| US9699029B2 (en) | 2014-10-10 | 2017-07-04 | Brocade Communications Systems, Inc. | Distributed configuration management in a switch group |
| US9628407B2 (en) | 2014-12-31 | 2017-04-18 | Brocade Communications Systems, Inc. | Multiple software versions in a switch group |
| US9626255B2 (en) | 2014-12-31 | 2017-04-18 | Brocade Communications Systems, Inc. | Online restoration of a switch snapshot |
| US10003552B2 (en) | 2015-01-05 | 2018-06-19 | Brocade Communications Systems, Llc. | Distributed bidirectional forwarding detection protocol (D-BFD) for cluster of interconnected switches |
| US9942097B2 (en) | 2015-01-05 | 2018-04-10 | Brocade Communications Systems LLC | Power management in a network of interconnected switches |
| US9807005B2 (en) | 2015-03-17 | 2017-10-31 | Brocade Communications Systems, Inc. | Multi-fabric manager |
| US10038592B2 (en) | 2015-03-17 | 2018-07-31 | Brocade Communications Systems LLC | Identifier assignment to a new switch in a switch group |
| US9680965B2 (en) * | 2015-04-01 | 2017-06-13 | Alcatel-Lucent Usa Inc. | Software upgrades for offline charging systems within a network |
| US10579406B2 (en) | 2015-04-08 | 2020-03-03 | Avago Technologies International Sales Pte. Limited | Dynamic orchestration of overlay tunnels |
| US10225184B2 (en) | 2015-06-30 | 2019-03-05 | Nicira, Inc. | Redirecting traffic in a virtual distributed router environment |
| US10439929B2 (en) | 2015-07-31 | 2019-10-08 | Avago Technologies International Sales Pte. Limited | Graceful recovery of a multicast-enabled switch |
| US10171303B2 (en) | 2015-09-16 | 2019-01-01 | Avago Technologies International Sales Pte. Limited | IP-based interconnection of switches with a logical chassis |
| US9912614B2 (en) | 2015-12-07 | 2018-03-06 | Brocade Communications Systems LLC | Interconnection of switches based on hierarchical overlay tunneling |
| US9846602B2 (en) * | 2016-02-12 | 2017-12-19 | International Business Machines Corporation | Migration of a logical partition or virtual machine with inactive input/output hosting server |
| CN107317694B (en) * | 2016-04-27 | 2020-06-19 | 深信服科技股份有限公司 | Link detection method and terminal for standby machines in cluster |
| US10237090B2 (en) | 2016-10-28 | 2019-03-19 | Avago Technologies International Sales Pte. Limited | Rule-based network identifier mapping |
| US11063886B2 (en) * | 2016-12-08 | 2021-07-13 | Vado Security Technologies Ltd | System and method for directing data packets by a virtual switch over a unidirectional medium |
| CN107395401B (en) * | 2017-07-04 | 2021-02-19 | 华南师范大学 | Multi-component application cloud deployment method based on network communication domain and resource balance |
| US10374827B2 (en) | 2017-11-14 | 2019-08-06 | Nicira, Inc. | Identifier that maps to different networks at different datacenters |
| US10511459B2 (en) | 2017-11-14 | 2019-12-17 | Nicira, Inc. | Selection of managed forwarding element for bridge spanning multiple datacenters |
| CN111431763B (en) * | 2020-03-18 | 2021-07-27 | 紫光云技术有限公司 | Connectivity detection method for SDN controller |
| US11496437B2 (en) | 2020-04-06 | 2022-11-08 | Vmware, Inc. | Selective ARP proxy |
| US11805101B2 (en) | 2021-04-06 | 2023-10-31 | Vmware, Inc. | Secured suppression of address discovery messages |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1972230A (en) * | 2006-11-09 | 2007-05-30 | 杭州华为三康技术有限公司 | A broadcasting method and access controller for wireless LAN address resolution protocol |
| CN101098292A (en) * | 2006-06-29 | 2008-01-02 | 中兴通讯股份有限公司 | Method for reducing user address analysis protocol broadcast on access equipment |
| US7616561B1 (en) * | 2005-01-19 | 2009-11-10 | Juniper Networks, Inc. | Systems and methods for routing data in a communications network |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5809233A (en) * | 1995-12-05 | 1998-09-15 | Lucent Technologies Inc. | Method of mapping from ATMARP to NHRP |
| JP3603524B2 (en) | 1997-02-05 | 2004-12-22 | 株式会社日立製作所 | Networking method |
| US7180887B1 (en) | 2002-01-04 | 2007-02-20 | Radisys Patent Properties | Routing and forwarding table management for network processor architectures |
| US7415028B1 (en) | 2003-02-11 | 2008-08-19 | Network Equipment Technologies, Inc. | Method and system for optimizing routing table changes due to ARP cache invalidation in routers with split plane architecture |
| TWI310265B (en) | 2003-06-13 | 2009-05-21 | Ind Tech Res Inst | Gain amplifier with dc offset cancellation circuit |
| US7533255B1 (en) * | 2003-07-11 | 2009-05-12 | Cisco Technology, Inc. | Method and apparatus for restricting address resolution protocol table updates |
| US7593346B2 (en) | 2003-07-31 | 2009-09-22 | Cisco Technology, Inc. | Distributing and balancing traffic flow in a virtual gateway |
| KR100811727B1 (en) * | 2004-01-09 | 2008-03-11 | 닛본 덴끼 가부시끼가이샤 | Load distributing method, node, and record medium readable by computer recorded control program |
| US20060224886A1 (en) * | 2005-04-05 | 2006-10-05 | Cohen Donald N | System for finding potential origins of spoofed internet protocol attack traffic |
| JP5068056B2 (en) | 2006-10-11 | 2012-11-07 | 株式会社日立製作所 | Failure recovery method, computer system and management server |
| CN101682544B (en) * | 2007-04-13 | 2013-10-16 | 惠普开发有限公司 | Apparatus and methods for adaptive throttling of traffic across multiple network nodes |
| US7751329B2 (en) | 2007-10-03 | 2010-07-06 | Avaya Inc. | Providing an abstraction layer in a cluster switch that includes plural switches |
| US9817695B2 (en) * | 2009-04-01 | 2017-11-14 | Vmware, Inc. | Method and system for migrating processes between virtual machines |
| US8705513B2 (en) * | 2009-12-15 | 2014-04-22 | At&T Intellectual Property I, L.P. | Methods and apparatus to communicatively couple virtual private networks to virtual machines within distributive computing networks |
-
2010
- 2010-12-15 US US12/968,286 patent/US8521884B2/en active Active
- 2010-12-22 TW TW099145271A patent/TWI441499B/en active
- 2010-12-29 CN CN201010612114.3A patent/CN102571998B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7616561B1 (en) * | 2005-01-19 | 2009-11-10 | Juniper Networks, Inc. | Systems and methods for routing data in a communications network |
| CN101098292A (en) * | 2006-06-29 | 2008-01-02 | 中兴通讯股份有限公司 | Method for reducing user address analysis protocol broadcast on access equipment |
| CN1972230A (en) * | 2006-11-09 | 2007-05-30 | 杭州华为三康技术有限公司 | A broadcasting method and access controller for wireless LAN address resolution protocol |
Also Published As
| Publication number | Publication date |
|---|---|
| US20120158997A1 (en) | 2012-06-21 |
| TW201225611A (en) | 2012-06-16 |
| CN102571998A (en) | 2012-07-11 |
| TWI441499B (en) | 2014-06-11 |
| US8521884B2 (en) | 2013-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102571998B (en) | Network system and method of address resolution | |
| CN101133605B (en) | Performing extended lookups on MAC-based tables | |
| CN101404619B (en) | Method for implementing server load balancing and a three-layer switchboard | |
| US8718061B2 (en) | Data center network system and packet forwarding method thereof | |
| CN101656765B (en) | Address mapping system and data transmission method of identifier/locator separation network | |
| CN102474467B (en) | Server-side load balancing using parent-child link aggregation groups | |
| EP2863614B1 (en) | Method and apparatus for a named data network within an autonomous system | |
| CN102014043B (en) | Address mapping system, data transmission method and address mapping maintenance method | |
| CN108259347B (en) | Message transmission method and device | |
| CN104901997A (en) | System and method for direct storage access in a content-centric network | |
| CN101764751A (en) | Method, system and equipment for forwarding roaming messages for wireless user terminal travelling across VLAN | |
| CN102394944B (en) | Method and equipment for correcting IP (Internet Protocol) address in Web access | |
| CN103634214B (en) | A kind of routing iinformation generation method and device | |
| CN102088448B (en) | Transmitting method of Internet protocol (IP) message and boundary tunnel router | |
| CN101932065B (en) | Method for discovering distributed satellite network resources | |
| US11050655B2 (en) | Route information distribution through cloud controller | |
| CN113839862B (en) | Method, system, terminal and storage medium for synchronizing ARP information between MCLAG neighbors | |
| CN108600099A (en) | A kind of message forwarding method, device and Leaf equipment | |
| CN118264617B (en) | Method, system, equipment and storage medium for transmitting data of overlay network | |
| CN101803289B (en) | Fitness based routing | |
| CN103037360A (en) | Mapping request response, information acquiring method and relevant devices based on locator identifier split protocol (LISP) | |
| US10855572B2 (en) | Area abstraction extensions to routing protocols | |
| CN110851275B (en) | Load transfer method and device of routing node | |
| CN102938704A (en) | Access management method, device and system | |
| CN106101201A (en) | Based on the expansible Anycast method and system redirected and rewrite in a kind of NDN |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |