Method and device for realizing load sharing

CN119071232AActive Publication Date: 2024-12-03NEW H3C TECH CO LTD
View PDF 12 Cites 0 Cited by

Patent Information

Application Number
CN202411047225.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-31
Publication Date
2024-12-03
Estimated Expiration
2044-07-31

AI Technical Summary

Technical Problem

In the complex scenario of multiple incoming ports and multiple outgoing ports, it is difficult for the prior art to realize sequential forwarding of data packets and load balancing, resulting in network congestion and unbalanced load sharing.

Method used

By configuring the outgoing port group and the incoming port group, the load sharing value (LBN value) of each outgoing port corresponds to the incoming port, an equivalent routing group is generated, and the LBN value of each outgoing port of the outgoing port group is sorted, and the outgoing port will be sorted based on the LBN value of each outgoing port of the outgoing port group will be output. Each outgoing port of the port group is set in turn as the next hop entry of the equivalent routing group to ensure that the packet is sent through the fixed outgoing port.

Benefits of technology

The one-to-one correspondence between the incoming port group and the outgoing port group is realized, avoiding the same service flow packets sent through different outgoing ports, ensuring load balancing and network stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071232A_ABST
    Figure CN119071232A_ABST
Patent Text Reader

Abstract

The invention provides a method and equipment for realizing load sharing. The load sharing method comprises the following steps: configuring an output port group; configuring an ingress port group; wherein the number of the inlet ports of the inlet port group is equal to the number of the outlet ports of the outlet port group; configuring a load sharing value LBN value for each output port of the output port group; and setting the LBN value of each output port as the LBN value mapped to the input port. It is ensured that the backbone node sends the message through a fixed output port based on an input port where the message arrives; therefore, the message is sent through the fixed output port according to the LBN value of the input port.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to communication technology, and specifically to a method and device for implementing load sharing. Background Art

[0002] AI (artificial intelligence) intelligent computing networks often encounter complex scenarios with multiple input ports and multiple output ports. In such scenarios, we hope to evenly distribute traffic with the same destination address from multiple input ports to multiple output ports while maintaining the order of data packets, that is, forwarding them flow by flow. However, in actual environments, traffic from multiple input ports often converges to one output port, while there is no traffic on other output ports, resulting in unbalanced load sharing and network congestion.

[0003] LBN (Load Balance Number) is a network-level load balancing technology that forms a mapping relationship between an equal-cost routing group and one or more ingress port groups on a network device. The traffic from multiple ingress ports of each port group is accurately load-balanced to different egress ports of the port group to improve network throughput.

[0004] However, the order of the outbound ports of the equal-cost next hop of the equal-cost routing group is not fixed, and the order of the outbound ports of the next hop of the equal-cost routing group may change due to the network environment. The network device calculates the hash value based on the LBN value of the inbound port of the message, and then sends the message through the down-adjusted outbound port corresponding to the calculated hash value. After the order of the outbound ports of the next hop of the equal-cost routing group changes, if there is no routing failure in the equal-cost routing group, the messages of the same service flow arrive at the same inbound port of the inbound port group and cannot be forwarded along the original path. Summary of the invention

[0005] The purpose of the present application is to provide a method and device for implementing load sharing, which ensures that the backbone node sends the message through a fixed egress port based on the ingress port where the message arrives.

[0006] To achieve the above-mentioned objectives, the present application provides a method for implementing load sharing, the method comprising: configuring an egress port group; configuring an ingress port group; wherein the number of ingress ports of the ingress port group is equal to the number of egress ports of the egress port group; configuring a load sharing numerical LBN value for each egress port of the egress port group; and setting the LBN value of each egress port to the LBN value of the mapped ingress port.

[0007] To achieve the above-mentioned purpose, the present application also provides a device for implementing load sharing, which at least includes a processor, a memory, and a switching chip connected by a bus; the processor performs the following operations by running the processor executable instructions in the memory; generates an equivalent routing group to reach the target IP address; finds that the egress port group contains each next-hop egress port of the equivalent routing group; based on the LBN value sorting of each egress port of the egress port group, each egress port of the egress port group is set in turn as the egress port of M next-hop table entries of the equivalent routing group; wherein M=2 N ; M, N are positive integers and M is greater than the number of output ports.

[0008] The beneficial effect of the present application is to achieve a one-to-one correspondence between the ingress port and the egress port between the ingress port group and the egress port group; the message is sent through a fixed egress port based on the LBN of the ingress port, thereby avoiding the message of the same business flow arriving at the same ingress port of the ingress port group and being sent through different egress ports. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A flow chart of an embodiment of a method for implementing load sharing provided in the present application;

[0010] Figure 2 A schematic diagram of a load sharing link for backbone nodes in an intelligent computing network provided in an embodiment of the present application;

[0011] Figure 3 for Figure 2 Schematic diagram of the egress port group and ingress port group of the configured load sharing value of the backbone node;

[0012] Figure 4 for Figure 2 Schematic diagram of the next hop table entry of the equal-cost multi-path group configured in the backbone node;

[0013] Figure 5 for Figure 2 Schematic diagram of load sharing achieved by backbone nodes;

[0014] Figure 6 for Figure 2 Schematic diagram of the next hop table entry for the configuration faulty route of the backbone node;

[0015] Figure 7A-7B A schematic diagram of a backbone node distributing the message load of a failed route to other next hops;

[0016] Figure 8 A schematic diagram of an embodiment of a device for implementing load sharing provided in the present application. DETAILED DESCRIPTION

[0017] The present invention will be described in detail with multiple examples shown in multiple figures. In the following detailed description, multiple specific details are used to provide a comprehensive understanding of the present application. Known methods, steps, components and circuits are not described in detail in the examples to avoid making these examples difficult to understand.

[0018] Among the terms used, the term "include" means including but not limited to; the term "contain" means including but not limited to; the terms "above", "within" and "below" are inclusive of the number; the terms "greater than" and "less than" are exclusive of the number. The term "based on" means based on at least a part thereof.

[0019] Figure 1 The flowchart of the method embodiment for implementing load sharing provided by the present application is shown; the method comprises:

[0020] Step 101, configure the egress port group;

[0021] Step 102, configuring an ingress port group and the number of ingress ports of the ingress port group is equal to the number of egress ports of the egress port group;

[0022] Step 103, configuring a load sharing value LBN value for each egress port of the egress port group;

[0023] Step 104, setting the LBN value of each egress port to the LBN value of the mapped ingress port.

[0024] Figure 1 The beneficial effect of the embodiment is that the backbone node sorts each next-hop egress port of the equal-cost routing group according to the LBN value of each egress port of the egress port group, ensuring that the order of the next-hop egress ports of the equal-cost routing group does not change, and ensuring that when no routing failure occurs in the equal-cost routing group, the message is forwarded along the original path.

[0025] Figure 2 A schematic diagram of the load sharing link of leaf nodes in the intelligent computing network provided in an embodiment of the present application. Figure 2 In the figure, the backbone nodes Spine 11-14 and the leaf nodes Leaf 1 and Leaf 2 are all Layer 3 switching devices; spine 11 is connected to leaf 1 through four links connected by ports porta, port b, port c, and port d; spine 11 is connected to leaf 2 through four links connected by ports port w, port x, port y, and port z.

[0026] The way in which spine12-14 connects leaf1 and leaf2 is the same as spine11; for the convenience of illustration, in the embodiment of the present application, the four physical links of spine12, spine13, and spine14 connected to leaf1 are respectively labeled L1, L3, and L5; the four physical links of spine12, spine13, and spine14 connected to leaf2 are respectively labeled L2, L4, and L6.

[0027] This application uses spine11 to illustrate the setting of egress port groups, ingress port groups, identification of egress port groups associated with equal-cost routing groups, next-hop port sorting of equal-cost routing groups, and load sharing forwarding.

[0028] Figure 3 for Figure 2 Schematic diagram of the egress port group and ingress port group for configuring load sharing values ​​of the backbone node.

[0029] Spine11 sets the outbound ports of outbound port group 31 to include port w, port x, port y, and port z.

[0030] Spine11 sets the LBN values ​​of the outbound ports port w, port x, port y, and port z to LBN0, LBN1, LBN2, and LBN3 respectively.

[0031] Spine11 sets the LBN values ​​of the ingress ports port a, port b, port c, and port d mapped to the egress ports port w, port x, port y, and port z to LBN0, LBN1, LBN2, and LBN3 respectively.

[0032] Egress port group 31 is configured on Spine11 first, and then ingress port group 32 containing the same number of ingress ports is configured.

[0033] The ingress port group 32 and the egress port group 31 set in Spine11 are used to evenly load-share the upstream traffic from leaf1 on the equal-cost multipaths to leaf2.

[0034] Spine11 can also set another pair of egress port groups and ingress port groups to evenly load-share the upstream traffic from leaf2 on equal-cost multipaths to leaf1.

[0035] Figure 4 for Figure 2 Schematic diagram of the next hop table entry of the equal-cost multi-path group configured in the backbone node;

[0036] Spine11 receives the routes of server s2 from the four paths connected to ports port w, port x, port y, and port z, and generates the routing table entries shown in Table 1.

[0037] Prefix / Mask Next hop Outgoing port 11.1.1.11 / 32 11.1.1.1 port z 11.1.1.11 / 32 11.1.1.1 port y 11.1.1.11 / 32 11.1.1.1 port x 11.1.1.11 / 32 11.1.1.1 port w

[0038] Table 1

[0039] According to the routing table entries shown in Table 1, Spine11 reaches the four identical next hops 11.1.1.1 of the IP address 11.1.1.11 of server s2, namely leaf2.

[0040] The four equal-cost routes of Spine11 form equal-cost route group ECMP 33.

[0041] Spine11 finds the egress port group 31 that contains the four next-hop egress ports port z, port y, port x, and port w of the equal-cost routing group ECMP 41.

[0042] Spine11 sorts the four next-hop egress ports of equal-cost routing group ECMP 33 as port w, port x, port y, and port z according to the LBN values ​​of each egress port of egress port group 31: LBN0, LBN1, LBN2, and LBN3; in this way, the order of the next-hop egress ports of the equal-cost routing group does not change.

[0043] Spine11 records the Layer 3 forwarding entry of IP address 11.1.1.11 / 32 in the Layer 3 forwarding table; the next hop of the Layer 3 forwarding entry is ECMP41.

[0044] Spine11 sets each egress port port w, port x, port y, and port z of the egress port group 31 as the egress port of the 32 next-hop table entries of the equal-cost routing group 41 in turn.

[0045] In this application, the number of next hop table entries of the equal-cost routing group of Spine11 is M=2 N ; M, N are positive integers and the number M of next hop table entries of the equal-cost routing group of Spine11 is greater than the number of egress ports in the egress port group 31. This embodiment takes 32 full-spec next hop table entries as an example to illustrate the method of ensuring that the position of the egress port of the normal route remains unchanged when a routing failure occurs.

[0046] Figure 5 for Figure 2 Schematic diagram of load sharing achieved by backbone nodes;

[0047] Spine11 receives packet 501 through ingress port a of ingress port group 32, and finds the next hop ECMP41 based on the destination IP address 11.1.1.11. Spine11 calculates the hash value as hash 0 based on the LBN value LBN0 of ingress port a and the number of members 4 of egress port group 31 associated with ECMP41, and selects egress port w of hash 0 from the 32 next hop table entries of ECMP41. Spine11 re-encapsulates the Ethernet header for packet 501 based on the MAC address of egress port w as the source MAC address and the MAC address of the next hop 11.1.1.1 of egress port w as the destination MAC address. Spine11 sends the re-encapsulated packet 501 through egress port w.

[0048] Spine11 receives packet 502 through ingress port port b of ingress port group 32, and finds the next hop ECMP41 based on the destination IP address 11.1.1.11. Spine11 calculates the hash value as hash 1 based on the LBN value LBN1 of ingress port port b and the number of members 4 of egress port group 31 associated with ECMP41, and selects the egress port port x of hash 1 from the 32 next hop table entries of ECMP41. Spine11 re-encapsulates the Ethernet header for packet 502 based on the MAC address of egress port port x as the source MAC address and the MAC address of the next hop 11.1.1.1 of egress port port x as the destination MAC address. Spine11 sends the re-encapsulated packet 502 through egress port port x.

[0049] Spine11 receives packet 503 through ingress port c of ingress port group 32, and finds the next hop ECMP41 based on the destination IP address 11.1.1.11. Spine11 calculates the hash value as hash 2 based on the LBN value LBN2 of ingress port port b and the number of members 4 of egress port group 31 associated with ECMP41, and selects egress port port y of hash2 from the 32 next hop table entries of ECMP41. Spine11 uses the MAC address of egress port port y as the source MAC address and the MAC address of the next hop 11.1.1.1 of egress port port y as the destination MAC address; and re-encapsulates the Ethernet header for packet 503. Spine11 sends the re-encapsulated packet 503 through egress port port y.

[0050] Spine11 receives packet 504 through ingress port port d of ingress port group 32, and finds the next hop ECMP41 based on the destination IP address 11.1.1.11. Spine11 calculates the hash value as hash 3 based on the LBN value LBN3 of ingress port port b and the number of members 4 of egress port group 31 associated with ECMP41, and selects egress port port z of hash 3 from the 32 next hop table entries of ECMP41. Spine11 uses the MAC address of egress port port z as the source MAC address and the MAC address of the next hop 11.1.1.1 of egress port port z as the destination MAC address; and re-encapsulates the Ethernet header for packet 504. Spine11 sends the re-encapsulated packet 504 through egress port port z.

[0051] Figure 6 for Figure 2 Schematic diagram of the next hop table entry for the configuration faulty route of the backbone node;

[0052] The route from port 2 of Spine11 to leaf2 fails. The route from Spine11 to server s2 is updated, as shown in Table 2.

[0053] Prefix / Mask Next hop Outgoing port 11.1.1.11 / 32 11.1.1.1 port z 11.1.1.11 / 32 11.1.1.1 port y 11.1.1.11 / 32 11.1.1.1 port x

[0054] Table 2

[0055] Spine11 updates the equal-cost routing group ECMP 41 to three next hops 11.1.1.1 according to the routing table entries shown in Table 2. Spine11 finds that the three next hops of ECMP41, port z, port y, and port x, belong to the egress port group 31.

[0056] Spine11 compares the three next-hop egress ports of the equal-cost routing group ECMP 41 with the egress port of the egress port group 31, and identifies that the failed next-hop egress port of the egress port group 31 is port w.

[0057] Spine11 identifies the ingress port port a mapped to the faulty egress port port w, and sets an ACL (Access Control List) entry for the ingress port port a; the matching items are port a and ECMP 41, and the action item is to allow forwarding. The packets received by the ingress port port a are load-balanced through the equal-cost routing group 41. By configuring a forwarding entry for port a, the LBN function from the ingress port port a to the egress port port w of the faulty route is invalidated, and the packets received by the ingress port port a are borne by the equal-cost multi-path group that reaches the destination IP.

[0058] Figure 7A-7B A schematic diagram of a backbone node distributing the message load of a failed route to other next hops;

[0059] Fig. 7A In the figure, Spine11 receives packet 701 through ingress port port b of ingress port group 32, and finds the next hop ECMP41 based on the destination IP address 11.1.1.11. Spine11 calculates the hash value as hash 1 based on the LBN value LBN1 of ingress port port b of packet 701 and the number of members 4 of egress port group 31 associated with ECMP41. Spine11 selects egress port port x of hash1 from the 32 next hop table entries of ECMP41; based on the MAC address of egress port port x as the source MAC address and the MAC address of the next hop 11.1.1.1 of egress port port x as the destination MAC address, the Ethernet header of packet 701 is re-encapsulated. Spine11 sends the re-encapsulated packet 701 through egress port port x.

[0060] Spine11 receives packet 702 through ingress port c of ingress port group 32; based on the destination IP address 11.1.1.11, it finds that the next hop is ECMP41. Spine11 calculates the hash value as hash 2 based on the LBN value LBN2 of ingress port port b and the number of members 4 of egress port group 31 associated with ECMP41, and selects egress port port y of hash2 from the 32 next hop table entries of ECMP41. Spine11 re-encapsulates the Ethernet header for packet 702 based on the MAC address of egress port port y as the source MAC address and the MAC address of the next hop 11.1.1.1 of egress port port y as the destination MAC address. Spine11 sends the re-encapsulated packet 702 through egress port port y.

[0061] Spine11 receives packet 703 through ingress port port d of ingress port group 32, and finds the next hop ECMP41 based on the destination IP address 11.1.1.11. Spine11 calculates the hash value as hash 3 based on the LBN value LBN3 of ingress port port b and the number of members 4 of egress port group 31 associated with ECMP41, and selects egress port port z of hash 3 from the 32 next hop table entries of ECMP41. Spine11 re-encapsulates the Ethernet header for packet 703 based on the MAC address of egress port port z as the source MAC address and the MAC address of the next hop 11.1.1.1 of egress port port z as the destination MAC address. Spine11 sends the re-encapsulated packet 703 through egress port port z.

[0062] Figure 7B In the figure, Spine11 receives packet 704 through ingress port port a of ingress port group 32, and finds the next hop ECMP41 according to the destination IP address 11.1.1.11. Spine11 obtains the hash factor from packet 704; modulo the obtained hash factor and the number of next hops of ECMP41, 32, to calculate the hash value, and selects the egress port corresponding to the hash value from the 32 next hop table entries of ECMP41. Spine11 uses the MAC address of the next hop 11.1.1.1 of the egress port as the destination MAC address; and re-encapsulates the Ethernet header for packet 704. Spine11 sends the re-encapsulated packet 704 through egress port port z. Since Spine11 replaces the egress port port w of the faulty route of ECMP41 with the egress ports x, y, and z of the next hop of the equal-cost route in turn, the packet 703 received through ingress port port2 is evenly load-shared by the next hop of the equal-cost route.

[0063] When the path from port 2 of spine11 to leaf2 is restored, the routing table 2 of spine11 to server s2 is updated to the route shown in Table 1; spine11 follows Figure 4 Set the next hop table entry for ECMP41 as shown; spine11 follows Figure 5 In the manner shown, the traffic sent to the server s2 is evenly load-shared again on the four egress ports port w, x, y, and z of the egress port group 31 of the LBN.

[0064] Figure 8A schematic diagram of an embodiment of a device for implementing load sharing provided by the present application. Device 80 includes at least a processor, a memory, and a switching chip connected by a bus; the processor performs the following operations by running the processor executable instructions in the memory; generates an equal-cost routing group to the target IP address; finds that the egress port group includes each next-hop egress port of the equal-cost routing group; sorts each egress port of the egress port group based on the LBN value of each egress port of the egress port group, and sets each egress port of the egress port group in turn as the egress port of the M next-hop table entries of the equal-cost routing group; wherein M=2N; M, N are positive integers and M is greater than the number of egress ports.

[0065] The processor further performs the following operations by running the processor executable instructions in the memory: generating an equal-cost routing group to the target IP address; finding that the egress port group includes each next-hop egress port of the equal-cost routing group; sorting based on the LBN value of each egress port of the egress port group, and setting each egress port of the egress port group as the egress port of M next-hop table entries of the equal-cost routing group in turn; wherein M=2N; M, N are positive integers and M is greater than the number of egress ports.

[0066] The processor further performs the following operations by running the processor executable instructions in the memory: receiving a message through one of the ingress ports of the ingress port group; finding an equal-cost routing group according to the destination IP address of the message; calculating a hash value according to the LBN value of the ingress port at which the message arrives and the number of members of the egress port group; selecting an egress port of the next hop table entry of the equal-cost routing group corresponding to the hash value; re-encapsulating an Ethernet header for the message based on the MAC address of the selected egress port; and sending the re-encapsulated message through the selected egress port.

[0067] The processor also performs the following operations by running the processor executable instructions in the memory: searching for an inbound port with the same LBN value based on the LBN value of the outbound port of the next hop of the faulty route of the target IP address; configuring a forwarding table entry for the inbound port found through load sharing by an equal-cost routing group; and replacing the outbound port of the next hop of the faulty route in the M next hop table entries with the outbound port of the next hop of the normal route of the equal-cost routing group in turn according to the above-mentioned order.

[0068] The processor further performs the following operations by running the processor executable instructions in the memory: refreshing the equivalent route group based on the next hop of the restored route of the target IP address; finding that the egress port group includes each next hop egress port of the equivalent route group after the restored route; finding the ingress port with the same LBN value according to the LBN value of the next hop egress port of the restored route; deleting the forwarding table entry of the found ingress port; and setting each egress port of the egress port group as the egress port of M next hop table entries in turn based on the above sorting.

[0069] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for implementing load sharing, characterized in that: The method comprises, Configure the egress port group; Configure an ingress port group; wherein the number of ingress ports in the ingress port group is equal to the number of egress ports in the egress port group; Configure a load sharing value LBN value for each egress port of the egress port group; The LBN value of each egress port is set to the LBN value mapped to the ingress port.

2. The method according to claim 1, characterized in that The method further comprises, Generate an equal-cost routing group to the target IP address; Finding that the egress port group includes each next-hop egress port of the equal-cost routing group; Based on the LBN value sorting of each egress port of the egress port group, each egress port of the egress port group is set in turn as the egress port of the M next hop table entries of the equal-cost routing group; wherein M=2 N ; M and N are positive integers and M is greater than the number of the output ports.

3. The method according to claim 1, characterized in that The method further comprises, Receiving a message through one of the ingress ports of the ingress port group; Find the equal-cost routing group according to the destination IP address of the message; Calculate a hash value based on the LBN value of the ingress port where the message arrives and the number of members of the egress port group; Selecting an egress port of the next hop table entry of the equal-cost routing group corresponding to the hash value; Re-encapsulating the Ethernet header for the message based on the MAC address of the selected outbound port; The re-encapsulated message is sent through the selected egress port.

4. The method according to claim 1, characterized in that: The method comprises, Searching for an inbound port with the same LBN value based on the LBN value of the outbound port of the next hop of the faulty route of the target IP address; Configuring a forwarding table entry for the found inbound port through load sharing by the equal-cost routing group; The egress ports of the next hops of the faulty routes in the M next hop table entries are replaced in turn with the egress ports of the next hops of the normal routes of the equal-cost routing group according to the order.

5. The method according to claim 1, characterized in that The method comprises, Refresh the equal-cost routing group based on the next hop of the recovery route of the target IP address; Find out that the egress port group includes each next-hop egress port of the equal-cost routing group after the routing is restored; According to the LBN value of the egress port of the next hop of the recovery route, find the ingress port with the same LBN value; Deleting the forwarding table entry of the found inbound port; Based on the sorting, each egress port of the egress port group is set in turn as an egress port of the M next hop table entries.

6. A device for implementing load sharing, characterized in that: The device at least includes a processor, a memory, and a switching chip connected via a bus; the processor performs the following operations by running processor executable instructions in the memory; Generate an equal-cost routing group to the target IP address; Finding that the egress port group includes each next-hop egress port of the equal-cost routing group; Based on the LBN value sorting of each egress port of the egress port group, each egress port of the egress port group is set in turn as the egress port of the M next hop table entries of the equal-cost routing group; wherein M=2 N ; M and N are positive integers and M is greater than the number of the output ports.

7. The device according to claim 6, characterized in that The processor further performs the following operations by executing the processor executable instructions in the memory; Generate an equal-cost routing group to the target IP address; Finding that the egress port group includes each next-hop egress port of the equal-cost routing group; Based on the LBN value sorting of each egress port of the egress port group, each egress port of the egress port group is set in turn as the egress port of the M next hop table entries of the equal-cost routing group; wherein M=2 N ; M and N are positive integers and M is greater than the number of the output ports.

8. The device according to claim 6, characterized in that The processor further performs the following operations by executing the processor executable instructions in the memory; Receiving a message through one of the ingress ports of the ingress port group; Find the equal-cost routing group according to the destination IP address of the message; Calculate a hash value based on the LBN value of the ingress port where the message arrives and the number of members of the egress port group; Selecting an egress port of the next hop table entry of the equal-cost routing group corresponding to the hash value; Re-encapsulating the Ethernet header for the message based on the MAC address of the selected outbound port; The re-encapsulated message is sent through the selected egress port.

9. The device according to claim 6, characterized in that The processor further performs the following operations by executing the processor executable instructions in the memory; Searching for an inbound port with the same LBN value based on the LBN value of the outbound port of the next hop of the faulty route of the target IP address; Configuring a forwarding table entry for the found inbound port through load sharing by the equal-cost routing group; The egress ports of the next hops of the faulty routes in the M next hop table entries are replaced in turn with the egress ports of the next hops of the normal routes of the equal-cost routing group according to the order.

10. The device according to claim 6, characterized in that The processor further performs the following operations by executing the processor executable instructions in the memory; Refresh the equal-cost routing group based on the next hop of the recovery route of the target IP address; Find out that the egress port group includes each next-hop egress port of the equal-cost routing group after the routing is restored; According to the LBN value of the egress port of the next hop of the recovery route, find the ingress port with the same LBN value; Deleting the forwarding table entry of the found inbound port; Based on the sorting, each egress port of the egress port group is set in turn as an egress port of the M next hop table entries.

Citation Information

Patent Citations

  • Virtual local network-based data exchanging method and equipment

    CN101022392A

  • Method for implementing load sharing among flow analysis servers and shunting equipment

    CN101335709A

  • Method for implementing server load balancing and a three-layer switchboard

    CN101404619A

  • Load sharing method and system for IPSEC (Internet Protocol Security) data message

    CN102647345A

  • Method and system for load sharing

    CN102647348A