CN108055203B - Equivalent routing load sharing method and device - Google Patents

Equivalent routing load sharing method and device Download PDF

Info

Publication number
CN108055203B
CN108055203B CN201711432093.5A CN201711432093A CN108055203B CN 108055203 B CN108055203 B CN 108055203B CN 201711432093 A CN201711432093 A CN 201711432093A CN 108055203 B CN108055203 B CN 108055203B
Authority
CN
China
Prior art keywords
interface
equivalent
weight interval
bandwidth
difference
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
Application number
CN201711432093.5A
Other languages
Chinese (zh)
Other versions
CN108055203A (en
Inventor
房立明
孙艳杰
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.)
Hangzhou DPtech Information Technology Co Ltd
Original Assignee
Hangzhou DPTech Technologies Co 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
Application filed by Hangzhou DPTech Technologies Co Ltd filed Critical Hangzhou DPTech Technologies Co Ltd
Priority to CN201711432093.5A priority Critical patent/CN108055203B/en
Publication of CN108055203A publication Critical patent/CN108055203A/en
Application granted granted Critical
Publication of CN108055203B publication Critical patent/CN108055203B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/12Shortest path evaluation
    • H04L45/125Shortest path evaluation based on throughput or bandwidth
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/70Routing based on monitoring results
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/12Avoiding congestion; Recovering from congestion
    • H04L47/125Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application discloses an equivalent routing load sharing method and device, wherein the method comprises the following steps: calculating the residual bandwidth of each interface in real time; determining whether to trigger updating of the weight interval of the equivalent route corresponding to each interface; if yes, updating the weight interval of the equivalent route corresponding to each interface based on the residual bandwidth of each interface; and when the received message hits a plurality of equivalent routes, carrying out flow load sharing based on the updated weight interval of the equivalent routes. The method and the device can achieve the effect of fully utilizing bandwidth resources.

Description

Equivalent routing load sharing method and device
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for sharing an equivalent routing load.
Background
With the development of network technology, people gradually adopt a multi-egress link to replace an original single-egress link in a network, so that the problem of network service interruption caused by a fault of the single-egress link is solved, and the reliability of the network service is ensured to a certain extent. In the network, a plurality of lines leading to the same destination and having the same cost are equivalent routes, and the equivalent routes share traffic leading to the same destination. However, the traffic shared between the equivalent routes is unbalanced, which may cause the traffic borne by the partial equivalent routes to be too much and reach the upper limit of the bandwidth, and the traffic borne by the partial equivalent routes is less and waste the bandwidth. That is, the method using the multi-egress link faces the problem of how the equivalent route realizes load sharing by routing the load.
In the prior art, equivalent routing load sharing is realized by selecting a route through a load, and a mainstream method adopts a quintuple-based flow-by-flow load sharing mode. Wherein, the quintuple refers to five important identifiers in network transmission: source IP, destination IP, source port, destination port, and protocol. The quintuple flow-by-flow load sharing can be divided into source address sharing, destination address sharing, common sharing of the source address and the destination address, common sharing of the source address, the destination address, the source port and the destination port, and the core principles of the flow-by-flow load sharing modes are basically consistent. First, a total weight value is set and a weight section is assigned to each equivalent route. Secondly, selecting a flow-by-flow load sharing mode, extracting flow-by-flow load sharing data corresponding to network flow to calculate a 32-bit hash value, and performing remainder calculation on the hash value and a set total value of a weight interval to obtain a remainder. And finally, selecting the corresponding interface of the equivalent route corresponding to the weight interval according to the weight interval hit by the remainder for carrying out flow transmission.
However, the prior art has the problems that in practical application, the traffic of each service flow may have different sizes, the flow-by-flow load sharing mode cannot fully utilize bandwidth resources, and the network service may be affected because the traffic actually transmitted by the interface exceeds a threshold. Therefore, it is necessary to research an equivalent routing load sharing method that can fully utilize bandwidth resources.
Disclosure of Invention
The application provides an equivalent routing load sharing method, which is applied to network forwarding equipment and comprises the following steps:
calculating the residual bandwidth of each interface in real time;
determining whether updating of the weight interval of the equivalent route corresponding to each interface is triggered;
if yes, updating the weight interval of the equivalent route corresponding to each interface based on the residual bandwidth of each interface; and the number of the first and second groups,
and when the received message hits a plurality of equivalent routes, carrying out flow load sharing based on the updated weight interval of the equivalent route.
Optionally, the calculating the remaining bandwidth of each interface includes:
calculating a first difference value between the data flow sent in unit time of each interface and an uplink flow threshold corresponding to each interface; calculating a second difference value between the data flow received in unit time of each interface and a downlink flow threshold corresponding to each interface;
determining whether the first difference is greater than the second difference;
if the first difference is larger than the second difference, taking the second difference as the residual bandwidth of the corresponding interface; and otherwise, taking the first difference as the residual bandwidth of the interface.
Optionally, the determining whether to trigger updating of the weight interval of the equivalent route corresponding to each interface includes:
when detecting that the duration of the residual bandwidth of any one of the interfaces is lower than the standard bandwidth threshold reaches a preset threshold, triggering to update the weight interval of the equivalent route corresponding to the interface;
or the like, or, alternatively,
and periodically triggering the updating of the weight intervals of the equivalent routes corresponding to the interfaces based on the preset interval time.
Optionally, if it is detected that the duration of the remaining bandwidth of each interface is lower than the standard bandwidth threshold reaches a preset threshold, triggering to update the weight interval of the equivalent route corresponding to the interface, including:
and when detecting that the duration of the residual bandwidth of any interface in the interfaces is lower than the standard bandwidth threshold reaches a preset threshold, setting the weight interval of the equivalent route corresponding to the interface to be 0, and triggering to update the weight interval of the equivalent route corresponding to the interface when the residual bandwidth of the interface is not lower than the standard bandwidth threshold.
Optionally, the load sharing based on the updated weight intervals of the equivalent routes includes:
extracting address information based on the selected load sharing mode and calculating to obtain a hash value;
the Hash value and the total weight value are subjected to complementation to obtain a remainder;
and selecting a corresponding interface of the equivalent route corresponding to the weight interval based on the weight interval of the remainder hit.
The present application further provides an equivalent routing load sharing apparatus, which is applied to a network forwarding device, and the apparatus includes:
the computing module is used for computing the residual bandwidth of each interface in real time;
the judging module is used for determining whether to trigger updating of the weight interval of the equivalent route corresponding to each interface;
the updating module is used for updating the weight interval of the equivalent route corresponding to each interface based on the residual bandwidth of each interface if the updating is triggered; and the number of the first and second groups,
and the sharing module is used for sharing the flow load based on the updated weight interval of the equivalent route when the received message hits a plurality of equivalent routes.
Optionally, the calculation module is specifically configured to:
calculating a first difference value between the data flow sent in unit time of each interface and an uplink flow threshold corresponding to each interface; calculating a second difference value between the data flow received in unit time of each interface and a downlink flow threshold corresponding to each interface;
determining whether the first difference is greater than the second difference;
if the first difference is larger than the second difference, taking the second difference as the residual bandwidth of the corresponding interface; and otherwise, taking the first difference as the residual bandwidth of the interface.
Optionally, the determining module is specifically configured to:
when detecting that the duration of the residual bandwidth of any one of the interfaces is lower than the standard bandwidth threshold reaches a preset threshold, triggering to update the weight interval of the equivalent route corresponding to the interface;
or the like, or, alternatively,
and periodically triggering the updating of the weight intervals of the equivalent routes corresponding to the interfaces based on the preset interval time.
Optionally, the determining module is further configured to:
and when detecting that the duration of the residual bandwidth of any interface in the interfaces is lower than the standard bandwidth threshold reaches a preset threshold, setting the weight interval of the equivalent route corresponding to the interface to be 0, and triggering to update the weight interval of the equivalent route corresponding to the interface when the residual bandwidth of the interface is not lower than the standard bandwidth threshold.
Optionally, the sharing module is specifically configured to:
extracting address information based on the selected load sharing mode and calculating to obtain a hash value;
the Hash value and the total weight value are subjected to complementation to obtain a remainder;
and selecting a corresponding interface of the equivalent route corresponding to the weight interval based on the weight interval of the remainder hit.
In the method, the residual bandwidth of each interface is calculated in real time, and whether the updating of the weight interval of the equivalent route corresponding to each interface is triggered or not is determined; if yes, updating the weight interval of the equivalent route corresponding to each interface based on the residual bandwidth of each interface; and when the received message hits a plurality of equivalent routes, carrying out flow load sharing based on the updated weight interval of the equivalent routes.
Because the weight interval of the equivalent route corresponding to each interface is updated based on the residual bandwidth of each interface, the dynamic update of the weight interval can be realized according to the actual condition of each interface, thereby achieving the effect of fully utilizing bandwidth resources.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings according to the drawings.
FIG. 1 is a networking diagram for implementing equal cost routing load sharing;
fig. 2 is a networking diagram for implementing equivalent routing load sharing according to an embodiment of the present application;
fig. 3 is a flowchart of an equivalent routing load sharing method according to an embodiment of the present application;
FIG. 4 is a table of a residual bandwidth algorithm according to an embodiment of the present application;
fig. 5 is a logic block diagram of an equivalent routing load sharing apparatus according to an embodiment of the present application;
fig. 6 is a hardware structure diagram of a network forwarding device carrying the equivalent routing load sharing apparatus according to an embodiment of the present application.
Detailed Description
In the prior art, if a common network forwarding device is used to implement load sharing of an equivalent route, the mainstream method is to use a flow-by-flow load sharing mode based on quintuple. Wherein, the quintuple refers to five important identifiers in network transmission: source address, destination address, source port, destination port, and protocol. Correspondingly, the specific load sharing mode can be divided into source address sharing, destination address sharing, sharing of the source address and the destination address, sharing of the source address, the destination address, the source port and the destination port, and the core principle of the load sharing mode is basically consistent.
The following takes sharing of the source address and the destination address together as an example, and specifically describes the implementation of load sharing of the equivalent route. First, a total weight value is set, and each equivalent route is assigned a weight section by weight. And secondly, extracting address information based on the selected load sharing mode, calculating to obtain a hash value, and carrying out complementation on the hash value and the total value of the set weight interval to obtain a remainder. Finally, selecting the corresponding interface of the equivalent route corresponding to the weight interval according to the weight interval hit by the remainder for carrying out flow transmission; wherein, the equivalent routes have one-to-one corresponding interfaces.
The equivalent route refers to a plurality of route table entries which are present in the network forwarding equipment and are destined to the same destination address and have the same cost, and the route table entries are equivalent routes; wherein, the plurality of equivalent routes can carry out traffic load sharing on the traffic to the same destination address.
The weight section is a section for representing the weight assignment of each equivalent route. For example, route a and route B are equivalent routes, and if the weight assignment of route a and route B is 1:2 and the total weight value is set to 3000, the weight interval corresponding to route a may be set to [0-1000], and the weight interval corresponding to route B may be set to [0-3000 ].
However, in this method, the traffic of each service flow may be different in size, and the flow-by-flow load sharing mode cannot fully utilize bandwidth resources, and there may be a case where the network service is affected because the traffic actually transmitted by the interface exceeds a threshold.
In the prior art, dedicated load sharing equipment may also be used to implement load sharing of an equivalent route, please refer to fig. 1, where fig. 1 is a networking diagram for implementing load sharing of an equivalent route. The dedicated load sharing device is deployed in the network of the operator a and the network of the operator B, the host a, the host B and the host C are connected to the dedicated load sharing device, the line 1 and the line 2 are equivalent routes, and the line 3 and the line 4 are equivalent routes. At this time, if the host a needs to access the network service of the operator a, the dedicated load sharing device first selects the operator line and then performs load sharing. However, this method requires replacing network devices, which results in waste of infrastructure resources.
In view of the above consideration, the present application provides an equivalent routing load sharing method, which calculates the residual bandwidth of each interface in real time, and determines whether to trigger updating of the weight interval of the equivalent routing corresponding to each interface; if yes, updating the weight interval of the equivalent route corresponding to each interface based on the residual bandwidth of each interface; and when the received message hits a plurality of equivalent routes, carrying out flow load sharing based on the updated weight interval of the equivalent routes.
On one hand, the weight interval of the equivalent route corresponding to each interface is updated based on the residual bandwidth of each interface, so that the dynamic update of the weight interval can be realized according to the actual condition of each interface, and the effect of fully utilizing bandwidth resources is achieved.
On the other hand, referring to fig. 2, after the common network forwarding device carries the logic algorithm corresponding to the equivalent routing load sharing method, dynamic load sharing can be implemented, thereby implementing the function of the conventional dedicated load sharing device.
The present application is described below with reference to specific embodiments and specific application scenarios.
Referring to fig. 3, fig. 3 is a flowchart illustrating an equivalent routing load sharing method according to an embodiment of the present application, applied to a network forwarding device, for performing the following steps:
s101, calculating the residual bandwidth of each interface in real time;
s102, determining whether updating of the weight interval of the equivalent route corresponding to each interface is triggered;
s103, if yes, updating the weight interval of the equivalent route corresponding to each interface based on the residual bandwidth of each interface;
and S104, when the received message hits a plurality of equivalent routes, carrying out flow load sharing based on the updated weight interval of the equivalent route.
The network forwarding device may include a general forwarding device that is not dedicated for load sharing; for example, the forwarding device may be a general-purpose forwarding device such as a router or a switch deployed in an operator network; wherein, the capability of the general forwarding device in load sharing is not as good as that of the special load balancer.
In this example, it is necessary to count the data traffic and the receiving traffic sent by each interface in a unit time, and then calculate the remaining bandwidth of each interface based on the remaining bandwidth algorithm.
The function of traffic statistics may be realized by the network forwarding device through its own function, or may be realized by an external device having a traffic statistics function.
In an embodiment shown, the algorithm may specifically include: the network forwarding equipment calculates a first difference value between data flow sent by each interface in unit time and an uplink flow threshold corresponding to each interface; calculating a second difference value between the data flow received in unit time of each interface and a downlink flow threshold corresponding to each interface; determining whether the first difference is greater than the second difference; if the first difference is larger than the second difference, taking the second difference as the residual bandwidth of the corresponding interface; and otherwise, taking the first difference as the residual bandwidth of the interface.
For example, in practical application, please refer to fig. 4, the network forwarding device adopts three interfaces to implement the technical solution of this example, which are respectively named as interface 1, interface 2, and interface 3, and counts the data traffic sent and received by each interface per second; each interface has its own uplink traffic threshold and downlink traffic threshold. Specifically, with 1 second as a unit time, the interface 1 sends 20MB of data traffic and receives 40MB of data traffic within the unit time, and if the uplink traffic threshold of the interface 1 is 100MB and the downlink traffic threshold is also 100MB, the first difference is 80MB, the second difference is 60MB, and it can be determined that the remaining bandwidth of the interface 1 is 60 MB. The other interfaces adopt the same method to calculate the residual bandwidth.
In this example, after the residual bandwidth is obtained through calculation, if the network forwarding device detects that the duration of the residual bandwidth of any one of the interfaces, which is lower than the standard bandwidth threshold, reaches the preset threshold, the updating of the weight interval of the equivalent route corresponding to the interface is triggered. It can be understood that the standard bandwidth threshold may be adjusted according to an actual application scenario, and the preset threshold of the duration may also be set according to an actual requirement.
For example, the standard bandwidth threshold is set to 5MB, the preset threshold of the duration is set to 5 seconds, and if the network forwarding device detects that the duration of the residual bandwidth in the interface 1 is less than 5MB and reaches 5 seconds, the updating of the weight interval of the equivalent route corresponding to the interface 1 is triggered.
In this way, the updating of the weight interval is triggered only if the duration of the remaining bandwidth below the standard bandwidth threshold reaches a preset threshold. That is, when the bandwidth fluctuates for a short time, the remaining bandwidth is lower than the standard bandwidth threshold in a short time, and the weight update is not triggered, so that the resources can be saved.
In an embodiment shown in the present invention, if the network forwarding device detects that the duration of the residual bandwidth of any one of the interfaces being lower than the standard bandwidth threshold reaches the preset threshold, the weight interval of the equivalent route corresponding to the interface is set to 0, and when the residual bandwidth of the interface is not lower than the standard bandwidth threshold, the weight interval of the equivalent route corresponding to the interface is triggered to be updated.
By the method, when the duration of the residual bandwidth of any interface lower than the standard bandwidth threshold reaches the preset threshold, the weight interval of the equivalent route corresponding to the interface is set to 0, so that the equivalent route can be stopped from being used, the interface has sufficient time to release the cache, and the subsequent reuse is facilitated.
In another illustrated embodiment, the network forwarding device periodically triggers updating of the weight intervals of the equivalent routes corresponding to the interfaces based on a preset interval duration. The interval duration can be adjusted according to actual requirements; for example, an overload condition to the interface is not noticed for a certain period of time, and the interval duration may be set to a larger value; if an overload situation of the interface is in mind for a certain period of time, i.e. it is necessary to deal with the overload situation of the interface as soon as possible, the interval duration may be set to a smaller value.
With this embodiment, when determining whether to trigger the weight interval update, it is not necessary to pay attention to the situation of the remaining bandwidth, but it is only necessary to periodically trigger the weight interval update according to the set interval duration.
In this example, if it is determined that the update of the weight section is triggered, the weight section of the equivalent route corresponding to each interface is updated based on the remaining bandwidth of each interface. For example, for the aforementioned interface 1, interface 2, and interface 3, the following results are obtained within a certain 1 second for the remaining bandwidth of each interface: the interface 1 residual bandwidth is 20MB, the interface 2 residual bandwidth is 40MB, the interface 3 residual bandwidth is 20MB, the total weight value is 4000, then the weight interval is set according to the proportion of the residual bandwidth of each interface, the weight interval of the equivalent route corresponding to the interface 1 can be set to be 0-1000, the weight interval of the equivalent route corresponding to the interface 2 can be set to be 0-3000, and the weight interval of the equivalent route corresponding to the interface 3 can be set to be 0-4000.
In this example, if the message received by the network forwarding device hits multiple equivalent routes, the network forwarding device extracts the address information based on the selected load sharing mode and calculates to obtain a hash value; wherein the selected load sharing mode may be: sharing a source address, sharing a destination address, sharing the source address and the destination address together, and sharing the source address, the destination address, a source port and a destination port together. It is to be understood that the load sharing manner is not limited to the above. Meanwhile, the core principles of different load sharing modes are approximately the same, and the difference has no influence on the implementation of the technical scheme.
For example, the description is made with the source address and the destination address shared together. The network forwarding equipment extracts the source address and the destination address in the message and carries out 32-bit hash value calculation.
In this example, after the 32-bit hash value is obtained by calculation, the hash value is complemented with the total weight value to obtain a remainder, and a corresponding interface of the equivalent route corresponding to the weight interval is selected based on the weight interval hit by the remainder.
For example, if the obtained remainder hits the weight interval [0-1000], selecting the interface 1 to forward the message; if the obtained remainder hits the weight interval [0-3000], selecting an interface 2 to forward the message; if the obtained remainder hits the weight interval [0-4000], selecting the interface 3 to forward the message.
In this embodiment, the remaining bandwidth of each interface is calculated, and whether to trigger updating of the weight interval of the equivalent route corresponding to each interface is determined; if yes, updating the weight interval of the equivalent route corresponding to each interface based on the residual bandwidth of each interface; and when the received message hits a plurality of equivalent routes, carrying out flow load sharing based on the updated weight interval of the equivalent routes.
On one hand, the weight interval of the equivalent route corresponding to each interface is updated based on the residual bandwidth of each interface, so that the dynamic update of the weight interval can be realized according to the actual condition of each interface, and the effect of fully utilizing bandwidth resources is achieved.
On the other hand, after the common network forwarding device carries the logic algorithm corresponding to the equivalent routing load sharing method, dynamic load sharing can be realized, thereby realizing the function of the traditional special load sharing device.
Corresponding to the method embodiment, the application also provides an embodiment of the device.
Referring to fig. 5, fig. 5 is a diagram illustrating an equivalent routing load sharing apparatus 20 according to an embodiment of the present application, applied to a network forwarding device; referring to fig. 6, the hardware architecture related to the network forwarding device carrying the equivalent routing load sharing apparatus 20 generally includes a CPU, a memory, a nonvolatile memory, a network interface, an internal bus, and the like; taking a software implementation as an example, the equivalent routing load sharing apparatus 20 may be generally understood as a computer program loaded in a memory, and a logic apparatus formed by combining software and hardware after a CPU runs, where the equivalent routing load sharing apparatus 20 includes:
a calculating module 201, configured to calculate the remaining bandwidth of each interface in fact;
a judging module 202, configured to determine whether updating of a weight interval of an equivalent route corresponding to each interface is triggered;
an updating module 203, configured to update the weight interval of the equivalent route corresponding to each interface based on the remaining bandwidth of each interface if the updating is triggered; and the number of the first and second groups,
the sharing module 204 is configured to, when the received packet hits multiple equivalent routes, perform traffic load sharing based on the updated weight interval of the equivalent route.
In this example, the calculation module is specifically configured to:
calculating a first difference value between the data flow sent in unit time of each interface and an uplink flow threshold corresponding to each interface; calculating a second difference value between the data flow received in unit time of each interface and a downlink flow threshold corresponding to each interface;
determining whether the first difference is greater than the second difference;
if the first difference is larger than the second difference, taking the second difference as the residual bandwidth of the corresponding interface; and otherwise, taking the first difference as the residual bandwidth of the interface.
In this example, the determining module is specifically configured to:
when detecting that the duration of the residual bandwidth of any one of the interfaces is lower than the standard bandwidth threshold reaches a preset threshold, triggering to update the weight interval of the equivalent route corresponding to the interface;
or the like, or, alternatively,
and periodically triggering the updating of the weight intervals of the equivalent routes corresponding to the interfaces based on the preset interval time.
In this example, the determining module is further configured to:
and when detecting that the duration of the residual bandwidth of any interface in the interfaces is lower than the standard bandwidth threshold reaches a preset threshold, setting the weight interval of the equivalent route corresponding to the interface to be 0, and triggering to update the weight interval of the equivalent route corresponding to the interface when the residual bandwidth of the interface is not lower than the standard bandwidth threshold.
In this example, the sharing module is specifically configured to:
extracting address information based on the selected load sharing mode and calculating to obtain a hash value;
the Hash value and the total weight value are subjected to complementation to obtain a remainder;
and selecting a corresponding interface of the equivalent route corresponding to the weight interval based on the weight interval of the remainder hit.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims (8)

1. An equivalent routing load sharing method is characterized by comprising the following steps:
calculating the residual bandwidth of each interface in real time;
determining whether updating of the weight interval of the equivalent route corresponding to each interface is triggered;
if yes, updating the weight interval of the equivalent route corresponding to each interface based on the residual bandwidth of each interface; and the number of the first and second groups,
when a plurality of equivalent routes are hit by a received message, carrying out flow load sharing based on the updated weight interval of the equivalent routes;
wherein, the determining whether to trigger updating of the weight interval of the equivalent route corresponding to each interface includes:
and triggering to update the weight interval of the equivalent route corresponding to the interface when detecting that the duration of the residual bandwidth of any one of the interfaces is lower than the standard bandwidth threshold reaches a preset threshold.
2. The method of claim 1, wherein the calculating the remaining bandwidth of each interface comprises:
calculating a first difference value between the data flow sent in unit time of each interface and an uplink flow threshold corresponding to each interface; calculating a second difference value between the data flow received in unit time of each interface and a downlink flow threshold corresponding to each interface;
determining whether the first difference is greater than the second difference;
if the first difference is larger than the second difference, taking the second difference as the residual bandwidth of the corresponding interface; and otherwise, taking the first difference as the residual bandwidth of the interface.
3. The method according to claim 1, wherein the triggering of updating the weight interval of the equivalent route corresponding to each interface when detecting that the duration of the remaining bandwidth of each interface below the standard bandwidth threshold reaches a preset threshold includes:
and when detecting that the duration of the residual bandwidth of any interface in the interfaces is lower than the standard bandwidth threshold reaches a preset threshold, setting the weight interval of the equivalent route corresponding to the interface to be 0, and triggering to update the weight interval of the equivalent route corresponding to the interface when the residual bandwidth of the interface is not lower than the standard bandwidth threshold.
4. The method according to claim 1, wherein the performing load sharing based on the updated weight intervals of the equivalent routes includes:
extracting address information based on the selected load sharing mode and calculating to obtain a hash value;
the Hash value and the total weight value are subjected to complementation to obtain a remainder;
and selecting a corresponding interface of the equivalent route corresponding to the weight interval based on the weight interval of the remainder hit.
5. An equivalent routing load sharing apparatus, comprising:
the computing module is used for computing the residual bandwidth of each interface in real time;
the judging module is used for determining whether to trigger updating of the weight interval of the equivalent route corresponding to each interface;
the updating module is used for updating the weight interval of the equivalent route corresponding to each interface based on the residual bandwidth of each interface if the updating is triggered; and the number of the first and second groups,
the sharing module is used for sharing the flow load based on the updated weight interval of the equivalent route when the received message hits a plurality of equivalent routes; the judgment module is specifically configured to:
and triggering to update the weight interval of the equivalent route corresponding to the interface when detecting that the duration of the residual bandwidth of any one of the interfaces is lower than the standard bandwidth threshold reaches a preset threshold.
6. The apparatus of claim 5, wherein the computing module is specifically configured to:
calculating a first difference value between the data flow sent in unit time of each interface and an uplink flow threshold corresponding to each interface; calculating a second difference value between the data flow received in unit time of each interface and a downlink flow threshold corresponding to each interface;
determining whether the first difference is greater than the second difference;
if the first difference is larger than the second difference, taking the second difference as the residual bandwidth of the corresponding interface; and otherwise, taking the first difference as the residual bandwidth of the interface.
7. The apparatus of claim 5, wherein the determining module is further configured to:
and when detecting that the duration of the residual bandwidth of any interface in the interfaces is lower than the standard bandwidth threshold reaches a preset threshold, setting the weight interval of the equivalent route corresponding to the interface to be 0, and triggering to update the weight interval of the equivalent route corresponding to the interface when the residual bandwidth of the interface is not lower than the standard bandwidth threshold.
8. The apparatus of claim 5, wherein the sharing module is specifically configured to:
extracting address information based on the selected load sharing mode and calculating to obtain a hash value;
the Hash value and the total weight value are subjected to complementation to obtain a remainder;
and selecting a corresponding interface of the equivalent route corresponding to the weight interval based on the weight interval of the remainder hit.
CN201711432093.5A 2017-12-26 2017-12-26 Equivalent routing load sharing method and device Active CN108055203B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711432093.5A CN108055203B (en) 2017-12-26 2017-12-26 Equivalent routing load sharing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711432093.5A CN108055203B (en) 2017-12-26 2017-12-26 Equivalent routing load sharing method and device

Publications (2)

Publication Number Publication Date
CN108055203A CN108055203A (en) 2018-05-18
CN108055203B true CN108055203B (en) 2020-10-02

Family

ID=62127902

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711432093.5A Active CN108055203B (en) 2017-12-26 2017-12-26 Equivalent routing load sharing method and device

Country Status (1)

Country Link
CN (1) CN108055203B (en)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108055203B (en) * 2017-12-26 2020-10-02 杭州迪普科技股份有限公司 Equivalent routing load sharing method and device
CN109361603B (en) * 2018-11-26 2021-03-23 浪潮思科网络科技有限公司 Method and system for dynamically adjusting equivalent path flow based on programmable switching chip
CN109450807B (en) * 2018-11-28 2022-02-22 迈普通信技术股份有限公司 Interface selection method and communication equipment
CN112087376B (en) * 2019-06-14 2023-03-14 中兴通讯股份有限公司 Load sharing method and device
CN110417654A (en) * 2019-07-30 2019-11-05 杭州迪普科技股份有限公司 The optimization method and device of minimum discharge link scheduling algorithm
CN110768917B (en) * 2019-10-31 2021-09-21 杭州迪普科技股份有限公司 Message transmission method and device
CN113595915B (en) * 2020-04-30 2024-09-27 华为技术有限公司 Method for forwarding message and related equipment
CN113746734B (en) * 2021-07-30 2023-04-28 苏州浪潮智能科技有限公司 Traffic forwarding method, device, equipment and medium
CN113806083B (en) * 2021-09-06 2023-07-25 杭州迪普科技股份有限公司 Method and device for processing aggregate flow data
CN113992596A (en) * 2021-10-18 2022-01-28 北京沃东天骏信息技术有限公司 Interface current limiting method, device, equipment, system and storage medium

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7299019B1 (en) * 2001-04-02 2007-11-20 At&T Bls Intellectual Property, Inc. Cellular handoff based on traffic load sharing
CN101184049A (en) * 2007-12-12 2008-05-21 中兴通讯股份有限公司 Dynamic load sharing method and system
CN103281253A (en) * 2013-05-27 2013-09-04 杭州华三通信技术有限公司 Load sharing method of non-equivalent route and equipment
CN106332141A (en) * 2016-09-13 2017-01-11 杭州华三通信技术有限公司 Flow load sharing method and flow load sharing device
CN106533940A (en) * 2016-10-25 2017-03-22 上海斐讯数据通信技术有限公司 SDN-based equivalent route Hash routing method, apparatus and system
CN108055203A (en) * 2017-12-26 2018-05-18 杭州迪普科技股份有限公司 A kind of equivalent route load sharing method and device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1697815A4 (en) * 2003-11-20 2008-05-14 Tekelec Us Methods and systems for message transfer part (mtp) load sharing using mtp load sharing groups

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7299019B1 (en) * 2001-04-02 2007-11-20 At&T Bls Intellectual Property, Inc. Cellular handoff based on traffic load sharing
CN101184049A (en) * 2007-12-12 2008-05-21 中兴通讯股份有限公司 Dynamic load sharing method and system
CN103281253A (en) * 2013-05-27 2013-09-04 杭州华三通信技术有限公司 Load sharing method of non-equivalent route and equipment
CN106332141A (en) * 2016-09-13 2017-01-11 杭州华三通信技术有限公司 Flow load sharing method and flow load sharing device
CN106533940A (en) * 2016-10-25 2017-03-22 上海斐讯数据通信技术有限公司 SDN-based equivalent route Hash routing method, apparatus and system
CN108055203A (en) * 2017-12-26 2018-05-18 杭州迪普科技股份有限公司 A kind of equivalent route load sharing method and device

Also Published As

Publication number Publication date
CN108055203A (en) 2018-05-18

Similar Documents

Publication Publication Date Title
CN108055203B (en) Equivalent routing load sharing method and device
US8842536B2 (en) Ingress rate limiting
US11032205B2 (en) Flow control method and switching device
CN108476177B (en) Apparatus, and associated method, for supporting a data plane for handling functional scalability
CN111385121B (en) Transmission method of operation administration maintenance (iOAM) message and corresponding device
WO2017035717A1 (en) Distributed denial of service attack detection method and associated device
CN103384252B (en) The method and apparatus of preventing network equipment from attacking, the network equipment
US20140043965A1 (en) Network apparatus, communication system, abnormal traffic detection method, and program
CN103281257B (en) A kind of protocol message processing method and equipment
US10216780B2 (en) Method and apparatus for table aging in a network switch
CN111181850B (en) Data packet flooding suppression method, device and equipment and computer storage medium
CN112753198B (en) Load balancing and message reordering method and device in network
US20140201354A1 (en) Network traffic debugger
CN101699795B (en) Message congestion processing method and system
US20170048149A1 (en) Determining a load distribution for data units at a packet inspection device
CN109802894B (en) Flow control method and device
CN109379246B (en) Memory detection method and device
CN107948157A (en) A kind of message processing method and device
CN103067197B (en) The method of the dynamic loop detection of gateway device, protection and static loop detection
CN103338158A (en) GOOSE message transmission delay jitter suppression method
CN110677358A (en) Message processing method and network equipment
CN112702226B (en) Loop detection method, device, equipment and computer readable storage medium
CN108156247B (en) Data communication method, device, system, terminal and readable storage medium
CN107995199A (en) The port speed constraint method and device of the network equipment
CN103078799B (en) The processing method of neighbor entry and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20210616

Address after: 310051 05, room A, 11 floor, Chung Cai mansion, 68 Tong Xing Road, Binjiang District, Hangzhou, Zhejiang.

Patentee after: Hangzhou Dip Information Technology Co.,Ltd.

Address before: 6 / F, Zhongcai building, 68 Tonghe Road, Binjiang District, Hangzhou City, Zhejiang Province

Patentee before: Hangzhou DPtech Technologies Co.,Ltd.