WO2020156355A1

WO2020156355A1 - Load sharing method, device, system, single board and storage medium

Info

Publication number: WO2020156355A1
Application number: PCT/CN2020/073377
Authority: WO
Inventors: 刘新菊
Original assignee: 中兴通讯股份有限公司
Priority date: 2019-01-29
Filing date: 2020-01-21
Publication date: 2020-08-06
Also published as: CN111491334A; CN111491334B

Abstract

The present document discloses a load sharing method, device, system, a single board and a storage medium, wherein the method comprises: at least one of a first single board and a second single board receives a service message, and the first single board and the second single board are mutually active and standby single boards; in response to determining that the service message is a non-BUM message, load sharing and corresponding forwarding are performed by the link where the first single board is located and the link where the second single board is located.

Description

Load sharing method, device, system, single board and storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office with an application number of 201910085733.2 on January 29, 2019. The entire content of this application is incorporated into this application by reference.

Technical field

The present disclosure relates to link aggregation load sharing technologies, for example, to a load sharing method, device, system, single board, and storage medium.

Background technique

With the development of the 5th generation wireless systems (5G) network, new requirements have been put forward for bandwidth, delay, and service forwarding capabilities. At present, the multi-chassislinkaggregationgroup (MC-LAG) supports the aggregation of Ethernet links of two subracks to form a link aggregation group across subracks, which provides links and subrack-level masters for services.备protection.

Among the related technologies, the cross-subrack channel protection technology only realizes the cross-subrack active and standby protection of services. That is, under normal circumstances, the services are only forwarded on the main link and the main device. When the main node device board detects the client side ( Customer Edge, CE) When the transmission quality and link status are abnormal, the equipment board of the master node switches the customer service to the board of the standby node through the cross-subrack aggregation group. Although the service can be protected in this way, the service can only be forwarded from one of the main link or the backup link, and the service load sharing cannot be realized, and the bandwidth of the cross-subrack aggregation group is not fully utilized.

Summary of the invention

The embodiment of the present invention provides a load sharing method, device, system, single board and storage medium.

The technical solution of the embodiment of the present invention is realized as follows:

The embodiment of the present application provides a load sharing method, including:

At least one of the first single board and the second single board receives service packets, and the first single board and the second single board are each other as a master and backup board;

In response to determining that the service message is a non-broadcast, unknown unicast, multicast (Broadcast, Unknown unicast, Multicast, BUM) message, the link where the first board is located and the chain where the second board is located Load sharing and corresponding forwarding.

An embodiment of the present application provides a load sharing system, including a first single board and a second single board that are mutually active and standby single boards, and at least one of the first single board and the second single board is configured to: receive Service message; the link where the first single board is located and the link where the second single board is located are set to: in response to determining that the service message is a non-BUM message, load sharing and corresponding forwarding are performed.

The embodiment of the present application provides a single board, including a load sharing module and a message processing module. The load sharing module is configured to receive service messages; the message processing module is configured to respond to determining the service messages. For non-BUM messages, load sharing and corresponding forwarding are performed by the link where the single board is located and the link where the other single board that is the active and standby single board with the single board is located.

An embodiment of the present application provides a load sharing device, including a processor and a memory for storing a computer program that can run on the processor. When the processor is used to run the computer program, any implementation of the application is executed. The load sharing method described in the example.

An embodiment of the present application provides a storage medium in which executable instructions are stored, and the executable instructions are executed by a processor to implement the load sharing method described in any embodiment of the present application.

Description of the drawings

Figure 1 is a schematic diagram of the architecture of a load sharing system in related technologies;

2 is a schematic diagram of the architecture of a load sharing system in an embodiment of the application;

FIG. 3 is a schematic flowchart of a load sharing method in an embodiment of this application;

4 is a schematic diagram of the forwarding process of the load sharing method in an embodiment of the application using a known unicast service as an example;

FIG. 5 is a schematic diagram of the forwarding process of the load sharing method in an embodiment of the present application using an upstream known unicast service as an example;

6 is a schematic flowchart of a load sharing method in another embodiment of this application;

FIG. 7 is a schematic diagram of the forwarding process of the load sharing method in an embodiment of the application, where the main board receives the uplink BUM message as an example;

FIG. 8 is a schematic diagram of the forwarding process of the load sharing method in an embodiment of the application, taking the standby board receiving the uplink BUM message as an example;

FIG. 9 is a schematic diagram of the forwarding process of the load sharing method in an embodiment of the application, taking the main board receiving downlink BUM packets as an example;

FIG. 10 is a schematic diagram of the forwarding process of the load sharing method in an embodiment of the application, taking the standby board receiving the downlink BUM message as an example;

FIG. 11 is a schematic diagram of a forwarding process in which the load sharing method in an embodiment of the application adopts the combination of cross-subrack aggregation group and Ethernet multi-environment protection technology;

FIG. 12 is a schematic structural diagram of a load sharing system in another embodiment of the application;

FIG. 13 is a schematic structural diagram of a single board in an embodiment of the application;

14 is a schematic structural diagram of a load sharing device in an embodiment of the application;

15 is a schematic flowchart of a load sharing method in an optional embodiment of the application, taking a known unicast packet scenario as an example;

FIG. 16 is a schematic flowchart of a load sharing method using the upstream BUM message scenario as an example in an optional embodiment of the application;

FIG. 17 is a schematic flowchart of a load sharing method using the following BUM message scenario as an example in an optional embodiment of the application.

detailed description

The technical solution of the present invention will be further described in detail below in conjunction with the drawings and specific embodiments of the specification.

In the following description, the expression "some embodiments" is involved, which describes a subset of all possible embodiments, but it should be understood that "some embodiments" may be the same subset or different subsets of all possible embodiments , And can be combined with each other without conflict.

Before further describing this application in detail, the terms and terms involved in the embodiments of the present invention will be described. The terms and terms involved in the embodiments of the present invention are applicable to the following explanations.

1) MC-LAG, also known as a link aggregation group between multiple subracks, refers to the aggregation of two corresponding ports on two identical single boards into a protection group to realize the protection of inter-board ports. One access device can simultaneously access two upstream physical devices through the link bundle formed by the cross-subrack aggregation group. Single boards are combined by subracks as units. A subracks can carry multiple different types of boards, and a network element device can include one or more subracks.

2) BUM message refers to Broadcast broadcast message, Unknown unicast unknown unicast message, Multicast multicast message.

3). Aggregation group ports, also known as ethernet channels, refer to combining a group of physical ports as a logical channel, that is, a channel-group.

Among the related technologies, the cross-subrack channel protection technology only realizes the cross-subrack active and standby protection of services, that is, under normal circumstances, services are only forwarded on the main link and the main device. Refer to Figure 1. When the master node equipment board detects that the client-side transmission quality and link status are abnormal, the board switches the client-side business to the standby node's single board through the cross-subrack aggregation group. Service protection, but the service can only be forwarded from the main or backup link, and the bandwidth of the cross-subrack aggregation group cannot be fully utilized.

The inventor of the present application discovered in research that the load sharing protection mode can be set for the cross-sub-rack aggregation group, and the load sharing method of the client side business is realized through the cross-sub-rack aggregation group. The main and backup links work at the same time. The use of link bandwidth on the network.

In one embodiment, in the method of implementing load sharing for client-side services through cross-subrack aggregation groups, for BUM messages, rules are set to limit the uplink BUM message capabilities of the primary and backup links, which can avoid BUM messages. On the client side, the messages form a ring between the main and backup boards, so as to ensure the bandwidth utilization and forwarding capacity of the network during the balanced forwarding process of BUM messages through the two links of the main and backup at the same time.

Please refer to FIG. 2, which is a schematic structural diagram of a load sharing system provided by an embodiment of the application. The system includes a first single board and a second single board that are mutually active and standby. In the embodiments of the present application, the first single board and the second single board that are the main and standby boards each other refer to two boards of the same type that together form a cross-subrack aggregation group. The first single board and the second single board The configuration can be the same. According to the configuration information of the aggregation group, the first board can be optionally configured as the main board and the second board can be configured as the backup board; or the second board can be optionally configured according to the aggregation group configuration information. The board is configured as the main board, and the first board is configured as the backup board. For ease of description and understanding, the following uses the main board A as the first board and the standby board B as the second board as an example. The single-board interconnection port L1 of the first single board and the single-board interconnection port L1 of the second single board are interconnected. The upstream forwarding port C2 of the first board and the upstream forwarding port C2 of the second board are associated with the aggregation group port C1 on the client side to form a cross-subrack aggregation group. The first board and the second board share the load of incoming services through the cross-subrack aggregation group, so that the incoming service packets (ie, downstream packets) from the client side are balanced by the first and second boards It is forwarded to the network side locally, and the service messages (that is, uplink messages) that enter the network side are forwarded to the client side in a balanced manner by the first single board and the second single board.

Please refer to FIG. 3, which is a schematic flowchart of a load sharing method provided by an embodiment of this application, which can be applied to the load sharing system shown in FIG. 1, and the method includes the following steps.

Step 101: At least one of a first single board and a second single board receives a service message, and the first single board and the second single board are each other as a master and a backup board.

Here, the first single board and the second single board are mutually active and standby single boards refer to that the first single board and the second single board are two single boards of the same type that together form a cross-subrack aggregation group, which can be the master single board. The board is the first single board and the backup single board is the second single board; or the main single board is the second single board and the backup single board is the first single board. At least one of the first single board and the second single board receives service packets, which means that the first single board and the second single board receive service packets separately, or the first single board and the second single board jointly receive service packets. Different actual scenes of the text.

Step 103: In response to determining that the service message is a non-BUM message, load sharing and corresponding forwarding are performed by the link where the first board is located and the link where the second board is located.

Here, non-BUM messages refer to other types of messages except BUM (that is, broadcast messages, unknown unicast messages, and multicast messages), for example, known unicast messages. Load sharing and corresponding forwarding are performed by the link where the first board is located and the link where the second board is located, that is, the service is formed by the link where the first board is located and the link where the second board is located. The main and backup links are forwarded in a balanced manner at the same time, thus making full use of the link bandwidth on the network.

Refer to Figure 4, taking the first and second boards receiving downlink packets from the client side as an example. When the downlink packets are known unicast packets, they directly pass through the link and the first board where the first board is located. The link where the second board is located performs load sharing, and after reaching the first board and the second board, forwarding is performed according to the destination Media Access Control (MAC) address. Please refer to Figure 5, and then take the first and second boards receiving upstream packets from the network side as an example. When the upstream packets are known unicast packets, the first and second boards directly Forwarding is performed according to the destination MAC address, load sharing is performed through the link where the first board is located and the link where the second board is located, and forwarded to the client side.

In the foregoing embodiment of the present application, at least one of the first single board and the second single board receives a service message, and in response to determining that the service message is a non-BUM message, the link and Load sharing and corresponding forwarding are performed on the link where the second single board is located. In this way, the load sharing and forwarding of packets through the first board and the second board solves the problem that the related technology can only be forwarded through one of the links of the active and standby boards, and the link bandwidth cannot be fully utilized. Bandwidth utilization is higher.

In some embodiments, referring to FIG. 6, the load sharing method may further include the following steps.

Step 105: In response to determining that the service message is a BUM message, restrict the uplink BUM message capability of at least one of the first single board and the second single board according to a setting rule, by restricting the uplink BUM message The first single board and the second single board after the message capability perform corresponding forwarding.

Here, BUM message refers to Broadcast broadcast message, unknown unicast unknown unicast message, and multicast multicast message. When the service message is a BUM message, the BUM message will be broadcast between the first board and the second board. Take the downstream BUM message from the client side as an example, the downstream BUM of the first board The message may return to the client side again through the second board, causing the BUM message to form a loop between the first board, the second board and the client side. Restricting the uplink BUM message capability of at least one of the first board and the second board according to the set rules may mean prohibiting the BUM of the first board or the second board according to the forwarding situation of the BUM message Message reporting capability, or limit the reporting capability of the first board and the second board to the BUM message forwarded by the opposite end, by restricting the upstream BUM message capability of the first board and the second board The single board performs corresponding forwarding, so as to avoid the problem of BUM packets forming a loop between the first single board, the second single board, and the client side.

In the embodiment of the present application, when the service message is a BUM message, the first board and the second board restrict the uplink BUM of at least one of the first board and the second board according to the set rules. After the message capability, the corresponding forwarding can be carried out, so as to avoid the problem of BUM messages forming a loop between the first board, the second board and the client side, and improve the communication between the first board and the second board. Forwarding ability.

In some embodiments, the step 105 may include the following steps.

The second board disables the uplink BUM message function.

In response to determining that the service message is an uplink BUM message, report the received uplink BUM message from the first board to the client side.

Here, disabling the upstream BUM message function of the second board refers to prohibiting the upstream forwarding port C2 of the second board from reporting the BUM message. In this way, when the service packets received by the first and second boards are upstream BUM packets from the network side, the second board forwards the received upstream BUM packets from the board interconnection port L1 to For the first board, the first board reports the received uplink BUM message to the client side.

Refer to Figure 7. Take the first board receiving the upstream packet from the network side as an example. When the upstream packet is a BUM packet, the first board will receive the upstream BUM packet through the upstream forwarding port C2. Normal forwarding, but when the BUM message passes through the upstream forwarding port C2 of the second board, it will be blocked, thereby ensuring that the upstream BUM message can only be reported to the client side through the upstream forwarding port C2 of the first board. Please refer to Figure 8, and take the second board receiving the upstream packet from the network side as an example. When the upstream packet is a BUM packet, the second board receives the upstream BUM packet directly and forwards it normally. When BUM packets pass through the upstream forwarding port C2 of the second board, they will be blocked. The BUM packets that need to be upstreamed to the client side can only be forwarded through the upstream forwarding port C2 of the first board. In this way, the first board can be guaranteed. Only one node of the single board and the second single board forwards the upstream BUM message to the client side at the same time to prevent the upstream BUM message from forming a loop.

In the foregoing embodiment of the present application, when the service message is an uplink BUM message, restricting the uplink BUM message capability of at least one of the first board and the second board according to the setting rule means prohibiting the second board. The upstream forwarding port C2 of the single board is capable of reporting BUM messages, so as to ensure that only one node on the first and second boards at the same time forwards upstream BUM messages to the client side, preventing upstream BUM messages from forming a loop.

In some embodiments, the reporting of the received uplink BUM message from the first board to the client side may include the following steps.

The second single board adds a designated tag to the received uplink BUM message to obtain an uplink forwarded BUM message, and forwards the uplink forwarded BUM message to the first single board.

The first single board reports the received uplink BUM message and the received uplink forwarded BUM message forwarded by the second single board to the client side.

Here, the designated label can refer to the virtual local area network (Virtual Local Area Network, vlan) mark set between the first board and the second board in the cross-subrack aggregation group. The vlan mark is added in front of the BUM message to facilitate The first board distinguishes the upstream forwarded BUM message forwarded by the second board from the upstream BUM message received by the local end.

In the above-mentioned embodiment of this application, the second board disables the upstream BUM message function. The second board adds the vlan tag to the upstream BUM message received to form an upstream forwarding BUM message and forwards it to the first board. The board forwards the upstream BUM message and the upstream BUM message received by the local end to the client side, so as to ensure that the upstream BUM message can only be sent to the client side through the upstream forwarding port C2 of the first board to avoid upstream BUM. Messages are looped.

The reporting of the received uplink BUM message from the first board to the client side may include the following steps.

When the link where the first single board is located fails, the second single board enables the uplink BUM message function.

The second single board reports the received uplink BUM message and the received uplink forwarded BUM message forwarded by the first single board to the client side.

Here, the failure of the link where the first board is located refers to a situation where the link where the first board is located cannot perform normal service forwarding. When the link where the first board is located fails, the second board will switch from disabling the upstream BUM message function to enabling the upstream BUM message function, and switch the business of the link where the first board is located to the second board On the link, the second single board reports the received uplink BUM message and the received uplink forwarded BUM message forwarded by the first single board to the client side, thus realizing the service protection function. In the above-mentioned embodiments of this application, compared with the traditional protection mode, the load sharing and forwarding mode of the first board and the second board is adopted to realize the balanced sharing and forwarding of service protection. When one of the links fails, It can also switch service messages to the normal link, realizing service protection, and improving the bandwidth utilization, forwarding capability and reliability of service transmission in different application scenarios without increasing costs.

In some embodiments, the step 105 may include the following steps.

In response to determining that the service message is an uplink BUM message, the first single board and the second single board report the uplink BUM message received by the local end to the client side, and forward the received opposite end The upstream forwarded BUM packet is discarded.

Here, restricting the uplink BUM message capability of at least one of the first board and the second board according to the setting rule refers to restricting the BUM message forwarded by the first board and the second board to the opposite end Reporting ability. When it is determined that the service message is an upstream BUM message, the first board reports the upstream BUM message received by the local end to the client side, and the upstream forwarded BUM message forwarded by the received second board passes through the upstream forwarding port C2 is discarded. The second board reports the upstream BUM message received by the local end to the client side, and discards the upstream forwarded BUM message forwarded by the first board when passing through the upstream forwarding port C2. It can be ensured that the same upstream BUM message can only be sent to the client side through the upstream forwarding port C2 of one of the first board and the second board, so as to prevent the upstream BUM message from forming a loop.

In some embodiments, the first single board and the second single board report the uplink BUM message received by the local end to the client side, and discard the received uplink forwarded BUM message forwarded by the opposite end. Including the following steps.

The first board reports the uplink BUM message received by the local end to the client side, adds the first label to the received uplink BUM message to obtain the uplink forwarded BUM message, and forwards the uplink BUM message Forward to the second board.

The second board reports the uplink BUM message received by the local end to the client side, adds the second label to the received uplink BUM message to obtain the uplink forwarded BUM message, and forwards the uplink BUM message Forward to the first board.

The first single board and the second single board respectively discard the received uplink forwarding BUM messages forwarded by the opposite end at their respective uplink forwarding ports.

Here, in order to facilitate the first board to distinguish between the upstream BUM message received by the local end and the upstream forwarded BUM message forwarded by the second board, the first board adds the first label to the received upstream BUM message and forwards it to The second board. In the same way, in order for the second board to distinguish between the upstream BUM message received by the local end and the upstream forwarded BUM message forwarded by the first board, the second board adds a second label to the received upstream BUM message and forwards it to The first board. The first board discards the received upstream forwarding BUM packet forwarded by the second board when it passes through the upstream forwarding port C2, and the second board discards the upstream forwarding BUM packet received by the first board forwarded by the upstream Discard when forwarding port C2. In this way, it can be ensured that the same upstream BUM message can only be sent to the client side through the upstream forwarding port C2 of one of the first board and the second board, so as to prevent the upstream BUM message from forming a loop.

In some embodiments, the step 105 may include the following steps.

The second board disables the uplink BUM message function.

In response to determining that the service message is a downlink BUM message, the second board adds a designated tag to the received downlink BUM message to obtain a downlink forwarded BUM message, and forwards the downlink forwarded BUM message to all For the first single board, the first single board discards the received downstream forwarding BUM message forwarded by the second single board at the upstream forwarding port of the first single board.

Here, restricting the uplink BUM message capability of at least one of the first single board and the second single board according to the setting rule refers to prohibiting the uplink forwarding port C2 of the second single board from reporting the BUM message capability. The designated label can refer to the VLAN tag set between the first board and the second board in the cross-subrack aggregation group. By adding the VLAN tag in front of the BUM message, the first board can be distinguished from the second board. The forwarded downlink forwarding BUM message and the downlink BUM message received by the local end. In order to prevent the second board from forwarding the received downstream BUM packets from the client side to the first board, it will be forwarded and forwarded back to the client side through the upstream forwarding port C2 of the first board. When the downstream BUM message is forwarded to the first board, a designated label is added, so that the first board discards the received downstream forwarded BUM message forwarded by the second board at the upstream forwarding port.

Refer to Figure 9. Take the first board receiving the downstream message from the customer side (CE) as an example. When the downstream message is a BUM message, the first board directly performs normal forwarding, and the first board will The received downstream BUM message is forwarded to the second board. When the downstream BUM message passes through the upstream forwarding port C2 of the second board, it will be blocked. This ensures that the downstream BUM message received from the first board The message will not be uploaded and forwarded back to the CE, avoiding the looping of downstream BUM messages. Refer to Figure 10, taking the second board receiving the downstream message from the client side as an example. When the downstream message is a BUM message, the second board performs normal forwarding and adds a designated label to the downstream BUM message Then, it is forwarded to the first board through the board interconnection port L1. After the first board receives the downstream forwarded BUM message with the specified label, it forwards the downstream forwarded BUM message to the upstream forwarding port C2. The downstream BUM packets are forwarded normally through the upstream forwarding port C2 of the first board. This ensures that the downstream BUM packets received from the second board will not be forwarded and forwarded back to the CE , To avoid the loop of downlink BUM messages.

In the above-mentioned embodiment of this application, when at least one of the first board and the second board receives a service message and determines that the service message is a downlink BUM message entered by the client, the second board will receive the downlink BUM The message is forwarded to the network side, and the received downstream BUM message is added with a specified label to form a downstream forwarded BUM message, and then forwarded to the first board through the board interconnection port L1, and the downstream forwarded BUM message passes through the first board When the upstream forwarding port C2 is discarded. In this way, the downlink BUM message can be prevented from returning to the client side again via the uplink forwarding port C2 of the first board, and the loop of the downlink BUM message can be avoided.

In some embodiments, the step 105 may include the following steps.

In response to determining that the service message is a downlink BUM message, the first single board and the second single board respectively forward the received downlink BUM message to the network side, and forward the received downlink BUM message to the network side. Downlink forwarding BUM packets are discarded at their respective upstream forwarding ports.

Here, restricting the uplink BUM message capability of at least one of the first board and the second board according to the setting rule refers to restricting the BUM message forwarded by the first board and the second board to the opposite end Reporting ability. When it is determined that the service packet is a downlink BUM packet, the first board forwards the downlink BUM packet received at the local end to the network side, and the received downlink forwarded BUM packet forwarded by the second board passes the uplink forwarding port When discarding at C2, the second single board forwards the downstream BUM message received by the local end to the network side, and discards the received downstream forwarded BUM message forwarded by the first single board when passing through the upstream forwarding port C2. In this way, it can be ensured that after the downlink BUM packets are forwarded by the load sharing of the first and second boards, they will not be forwarded and forwarded back to the client side through the upstream forwarding port C2 of the opposite end, which will cause the BUM packets to become a ring. This solves the problem of BUM message looping, and improves the bandwidth utilization, forwarding capability and reliability of service transmission.

In some embodiments, the step of discarding the received downlink forwarding BUM message of the opposite end at the respective uplink forwarding port may include the following steps.

The first single board adds a first label to the received downlink BUM message to obtain a downlink forwarded BUM message, and forwards the downlink forwarded BUM message to the second single board, and the second single board The received downstream forwarding BUM message forwarded by the first single board is discarded at the upstream forwarding port of the second single board.

The second single board adds a second label to the received downlink BUM message to obtain a downlink forwarded BUM message, and forwards the downlink forwarded BUM message to the first single board, and the first single board will The received downstream forwarding BUM message forwarded by the second single board is discarded at the upstream forwarding port of the first single board.

Here, in order to facilitate the first board to distinguish between the downstream BUM message received by the local end and the downstream forwarded BUM message forwarded by the second board, the first board adds the first label to the received downstream BUM message and forwards it to The second board. In the same way, in order for the second board to distinguish between the downstream BUM packets received at the local end and the downstream forwarded BUM packets forwarded by the first board, the second board adds a second label to the received downstream BUM packets and forwards them to The first board. The first board discards the received downstream forwarded BUM packets forwarded by the second board when passing through the upstream forwarding port C2, and the second board discards the received downstream forwarded BUM packets forwarded by the first board through the upstream Discard when forwarding port C2. In this way, it can be ensured that after the downlink BUM packets are forwarded by the load sharing of the first and second boards, they will not be forwarded and forwarded back to the client side through the upstream forwarding port C2 of the opposite end, which will cause the BUM packets to become a ring. The problem of BUM packet looping is solved.

In some embodiments, please refer to FIG. 6 again. In step 101, before at least one of the first board and the second board receives a service packet, the method may further include the following steps.

Step 1021: Obtain aggregation group configuration information.

Step 1022: According to the aggregation group configuration information, respectively associate the upstream forwarding port of the first board with the client-side aggregation group port, and the upstream forwarding port of the second board with the client-side aggregation group port. The ports are associated to form a cross-subrack aggregation group, and the cross-subrack aggregation group is configured to perform load sharing through the associated aggregation group ports.

Here, the aggregation group configuration information can be configured on the management side of the network. By obtaining the aggregation group configuration information, two cascaded boards or devices can be configured as active and standby, and the uplink forwarding ports of the two boards can be associated with the aggregation group ports on the client side to form a cross-subrack aggregation group. Obtaining aggregation group configuration information can also include: creating a vlan mark between the active and standby nodes, marking forwarding BUM packets, and blocking the associated aggregation group port of the standby board, that is, the upstream BUM forwarding function of the upstream forwarding port C2, to ensure Only one of the active and standby nodes can forward the BUM message upstream. In this way, when the uplink and downlink services pass through the cross-subrack aggregation group, the active and standby links where the two single boards are located can perform load sharing and forwarding according to the set rules, thereby improving link bandwidth utilization and service forwarding capabilities.

In some embodiments, the load sharing method may further include the following steps.

Acquire a master node selection instruction based on the third single board communicatively connected with the first single board and the fourth single board communicatively connected with the second single board.

The master node is determined according to the master node selection instruction, and the link between the master node and the nodes adjacent to the master node is set as a low-power lossy network routing protocol (Routing Protocol for Low Power and Lossy Network) (LLN), RPL) link.

Here, ring network protection is established on the first single board, the second single board, and the third single board and the fourth single board communicatively connected to the first single board and the second single board. By obtaining the master node selection instruction based on the third single board and the fourth single board, the master node is selected and determined on the ring network, and the link between the master node and the node adjacent to the master node is set to RPL link. When the link is not faulty, in order to ensure that the business is not ringed, the RPL link is in a blocked state, and the link is detected by the Connectivity Fault Management (cfm). When there is an alarm ( When SystemFault, SF), the RPL link is set to the forwarding state, the ring network is switched, and the ring network protection is generated.

Referring to Figure 11, a ring network protection is established between the third board C and the fourth board D and the main board A and the backup board B. In the direction of the east and west ports of the ring network, select the fourth board D as the master node, and set the link between the fourth board D and the standby board B as the RPL link. When the link does not fail, the RPL link is in a blocked state to ensure that the business does not form a loop. Use cfm to detect the link. When an SF alarm occurs, the RPL link is set to the forwarding state, the ring network is switched, and the ring network protection is generated.

In the above-mentioned embodiments of this application, MC-LAG and Ethernet Ring Protection Switching (ERPS) are combined to implement a load sharing method to ensure that services are not looped in the ring network architecture. Normally, services Load sharing is carried out across subrack aggregation groups, and forwarding is performed on the main and backup links at the same time, which greatly improves bandwidth utilization and forwarding capabilities. Moreover, when any one of the links fails, the cross-subrack aggregation group will promptly switch the service of the failed link to another normal link, thereby achieving service protection. When the failed link recovers, the service continues to perform load sharing through the active and standby links.

The first board and the second board, which are the main and backup boards for each other, mean that the first board is the main board and the second board is the backup board; or the first board is the backup board and the second board is the backup board. The board is the main board. Refer to Figure 12, taking the first board as the main board A and the second board as the backup board B as an example, the link where the first board is located is the main link, and the link where the second board is located is the backup link The upstream forwarding port C2 of the first single board and the upstream forwarding port C2 of the second single board are associated with the aggregation group port C1 on the client side to form a cross-subrack aggregation group. When the load sharing system performs service transmission and reception, the first single board and the second single board identify the type of service message, and when it is determined that the service message is a non-BUM message, the link and The link where the second single board is located performs load sharing and corresponding forwarding, so that the first single board and the second single board complete cross-board aggregation service forwarding, and the primary link and the backup link jointly implement the load sharing of the active and standby links.

In some embodiments, at least one of the first single board and the second single board is further configured to: in response to determining that the service message is a BUM message, restrict the respective uplink BUM message according to a setting rule Ability, to limit the uplink BUM message capability and forward accordingly.

Here, please refer to FIG. 12 again to restrict the upstream BUM message capability of at least one of the first board and the second board according to the setting rule, which is to prohibit the BUM message of the upstream forwarding port of the second board. Take the message reporting capability as an example. The second board adds a vlan tag to the received upstream BUM message and forwards it to the first board so that the first board can recognize the upstream forwarded BUM message forwarded by the second board. Report to the client through the upstream forwarding port C2 of the first board; and the second board adds a vlan tag to the received downstream BUM message and forwards it to the first board so that the first board can identify the second board After the forwarded downlink forwarding BUM message, it is discarded at the uplink forwarding port C2 of the first board. By disabling the reporting capability of the BUM message of its upstream forwarding port by the second single board and adding a vlan tag to the BUM message and forwarding it to the first single board, BUM message processing is realized and the problem of BUM message looping is avoided.

In some embodiments, the second board is set to disable the uplink BUM message function.

The first single board and the second single board are set to: in response to determining that the service packet is an uplink BUM packet, report the received uplink BUM packet from the first single board to the client side .

In some embodiments, the second board is configured to: disable the uplink BUM message function; in response to determining that the service message is a downlink BUM message, add a designated tag to the received downlink BUM message Obtain a downlink forwarded BUM message, and forward the downlink forwarded BUM message to the first board. The first single board is configured to discard the received downlink forwarding BUM message forwarded by the second single board at the uplink forwarding port of the first single board.

In some embodiments, the second board is further configured to enable the uplink BUM message function when the link where the first board is located fails.

In some embodiments, the first single board and the second single board are configured as:

In response to determining that the service message is an uplink BUM message, report the uplink BUM message received by the local end to the client side, and discard the received uplink forwarded BUM message forwarded by the opposite end; and/or

In response to determining that the service message is a downlink BUM message, the downlink BUM message received by the local end is forwarded to the network side, and the downlink forwarded BUM message forwarded by the opposite end is received at the respective uplink forwarding port throw away.

Here, restricting the upstream BUM message capability of at least one of the first board and the second board according to the setting rule refers to restricting the upstream forwarding port pair of the first board and the second board to receive Reporting capability of BUM packets forwarded by the peer. Assign and configure designated labels between the board interconnection ports of the first board and the second board. For example, the first board adds the first label to the BUM message and forwards it to the second board, and the second board sends the BUM message to the second board. The message is forwarded to the first board after adding the second label. The first label and the second label can be different vlan labels, so that the first board and the second board can identify the received BUM message forwarded by the opposite end Then discard it at the upstream forwarding port C2. Through the first single board and the second single board respectively restricting the ability of its upstream forwarding port to report the received BUM message of the opposite end, BUM message processing is realized, and the problem of BUM message looping is avoided.

In some embodiments, the first single board and the second single board are further configured to: obtain aggregation group configuration information; according to the aggregation group configuration information, the first single board transfers the first single board The uplink forwarding port of the second single board is associated with the aggregation group port on the client side, and the second single board associates the uplink forwarding port of the second single board with the aggregation group port to form a cross-subrack aggregation group. The rack aggregation group is configured to perform load sharing through the associated aggregation group ports.

In the above-mentioned embodiment of the present application, when the load sharing system determines that the service packet is a non-BUM packet through the first board and the second board, the link between the first board and the chain where the second board is located Load sharing and corresponding forwarding. In this way, the first single board and the second single board forward packets through load sharing, which solves the problem that the related technology can only be forwarded through one of the links of the active and standby single boards, thereby achieving higher bandwidth utilization. When the first board and the second board determine that the service message is a BUM message, the first board and the second board restrict at least one of the first board and the second board according to the set rule The upstream BUM message capability is then forwarded accordingly. In this way, the problem of BUM messages forming a loop between the first board, the second board and the client side can be avoided, and the first board and the second board can be improved. 2. The forwarding capability of the single board.

Referring to FIG. 13, an embodiment of the present invention also provides a single board, including a load sharing module 21 and a message processing module 23. The load sharing module 21 is configured to receive service messages; the message processing module 23, In response to determining that the service message is a non-BUM message, load sharing and corresponding forwarding are performed by the link where the single board is located and the link where the other single board that is the master and backup board is mutually active with the single board .

It should be noted that the single board may refer to the first single board described in any embodiment of the present application, and the other single board that is the active and standby single board with the single board refers to any implementation of the present application The second single board in the example; the opposite is true, the single board can also refer to the second single board described in any of the embodiments of the present application, and it is the primary and standby board of the single board. The other board refers to the first board described in any embodiment of the present application, and is not limited herein.

In some embodiments, the message processing module 23 is further configured to, in response to determining that the service message is a BUM message, limit the uplink BUM message capability of the board according to a setting rule, and based on the restriction The single board after the uplink BUM message capability and the other single board perform corresponding forwarding.

In some embodiments, the message processing module 23 is further configured to prohibit the upstream BUM message function of the upstream forwarding port of the board; in response to determining that the service message is an upstream BUM message, it will receive Add a specified label to the upstream BUM message to obtain the upstream forwarded BUM message, and forward the upstream forwarded BUM message to the other single board, and the other single board forwards the upstream forwarded BUM message to the Report to the client at the upstream forwarding port of the other board; or, in response to determining that the service message is a downstream BUM message, add the designated label to the received downstream BUM message to obtain a downstream forwarded BUM message And forward the downstream forwarded BUM message to the another single board, and the other single board discards the downstream forwarded BUM message at the upstream forwarding port of the other single board.

In some embodiments, the message processing module 23 is further configured to enable the uplink BUM message function of the uplink forwarding port of the single board when the link where the other single board is located fails.

In some embodiments, the message processing module 23 is further configured to, in response to determining that the service message is an uplink BUM message, report the received uplink BUM message to the client side, and send the received uplink BUM message. Adding a specified label to the message to obtain an upstream forwarding BUM message, forwarding the upstream forwarding BUM message to the other single board, and discarding the received upstream forwarding BUM message forwarded by the other single board; Or, in response to determining that the service message is a downlink BUM message, forward the received downlink BUM message to the network side, add a designated label to the received downlink BUM message to obtain a downlink forwarded BUM message, and transfer all The downstream forwarded BUM message is forwarded to the other single board, and the received downstream forwarded BUM message of the other single board is discarded at the upstream forwarding port of the single board.

In some embodiments, the load sharing module 21 is further configured to obtain aggregation group configuration information, associate the uplink forwarding port of the board with the aggregation group port on the client side according to the aggregation group configuration information, and form a cross-connect Subrack aggregation group.

When the single board provided in the above embodiment implements the load sharing method, only the division of the above multiple program modules is used as an example. In actual applications, the above steps can be allocated to different program modules to complete according to needs, that is, The internal structure of the program for the single board to implement the load sharing method is divided into different program modules to complete all or part of the processing described above.

For example, the message processing module 23 may include a BUM message processing module and a message forwarding module. The BUM message processing module includes a tag creation unit, a message judgment unit, and a BUM message processing unit. The tag creation unit It is set to create a special tag vlan between the active and standby boards, which is used to identify the BUM packets transmitted between the active and standby boards. The message judging unit is set to judge the received messages by the active and standby nodes, and distinguish between known unicast and BUM messages. The BUM message processing unit is configured to turn off the upstream BUM function of the upstream forwarding port of the backup board, the downstream BUM message received by the main board is forwarded normally, and the downstream BUM message received by the backup board is marked The vlan label is forwarded to the main single board for forwarding. For upstream BUM packets, the main single board directly forwards it normally after receiving it, and the standby single board also forwards it normally after receiving it, but the upstream forwarding port of the standby single board does not forward it. The message forwarding module includes a downlink known unicast message forwarding unit, a downlink BUM message forwarding unit, an uplink known unicast message forwarding unit, and an uplink BUM message forwarding unit. The known downlink unicast message forwarding unit is set to directly perform the forwarding according to the destination MAC address after load sharing through the active and standby links. The downlink BUM message forwarding unit is configured to directly forward the downlink BUM message received by the main single board, and the uplink forwarding port of the standby single board does not forward the BUM message; Downlink BUM packets are forwarded to the main single board after adding a vlan label, and other ports perform normal forwarding. After the main single board receives a vlan-labeled packet, it does not forward to the upstream forwarding port, but other ports perform normal forwarding. . The uplink known unicast message forwarding unit is configured to forward the known uplink unicast messages directly according to the destination MAC address after load sharing through the active and standby links. The upstream BUM message forwarding unit is set to perform normal forwarding directly after receiving the upstream BUM message on the active and standby single board, and the upstream forwarding port of the standby single board does not perform upload forwarding. The above-mentioned division of multiple program modules is only used for illustration.

In addition, the single board provided in the foregoing embodiment and the load sharing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, and will not be repeated here.

The embodiment of the present invention also provides a load sharing device. The load sharing device may belong to one or more single boards in the network. Please refer to FIG. 14. The load sharing device includes a processor 201 and a processor for storing 201 is a storage medium 202 of a computer program running on it. The processor 201 is configured to execute the steps of the load sharing method provided in any embodiment of the present application when running the computer program. Here, the processor 201 and the storage medium 202 do not mean that the corresponding number is one, but may be one or more. The storage medium 202 may store an operating system and a load sharing device for implementing the load sharing method provided in the embodiment of the present invention. The processor 201 is used to improve calculation and control capabilities and support the operation of the entire server.

The embodiment of the present invention also provides a storage medium, for example, including a memory storing a computer program, and the computer program can be executed by a processor to complete the steps of the load sharing method provided in any embodiment of the present application. The storage medium can be Ferroelectric Random Access Memory (FRAM), Read-Only Memory (ROM), Programmable Read-Only Memory (PROM), erasable and programmable Read-only memory (Erasable Programmable Read-Only Memory, EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory (Flash Memory), magnetic surface memory, optical disk, or optical disk only CD-ROM (Compact Disc Read-Only Memory) and other memories; it can also be a variety of devices including one or any combination of the foregoing memories.

In the load sharing method, device, system, single board, and storage medium provided in the foregoing embodiments, at least one of the first single board and the second single board receives a service packet, and responds to determining that the service packet is a non-BUM packet In the text, load sharing and corresponding forwarding are performed by the link where the first single board is located and the link where the second single board is located. In this way, the load sharing and forwarding of packets by the first single board and the second single board solves the problem that the related technology can only be forwarded through one of the links of the active and standby single boards, thereby achieving higher bandwidth utilization.

In order to be able to further understand the implementation process of the load sharing method provided by the embodiments of the present application, the load sharing methods in different scenarios of known unicast packet, uplink BUM packet, and downlink BUM packet transmission are exemplified below. . Referring to FIG. 15, taking a known unicast message scenario as an example, the load sharing method includes the following steps.

Step S11, at least one of the main single board and the standby single board receives a known unicast message.

Step S12: Determine that the known unicast message is an uplink message or a downlink message.

When it is determined to be a known downlink unicast message, steps S131 to S133 are executed; when it is determined to be an uplink known unicast message, steps S141 to S143 are executed.

Step S131: When it is determined that it is a known downlink unicast message, the active and standby links perform load sharing and forward them to the active and standby boards.

In step S132, the active and standby single boards forward according to the destination MAC address of the known unicast message.

Step S133: When one of the active and standby links fails, the service of the failed link is switched to the normal link for forwarding.

Step S141: When it is determined that it is an uplink known unicast message, the active and standby single boards forward it according to the destination MAC address.

Step S142, the services that reach the client side are load-shared by the active and standby links.

Step S143: When one of the active and standby links fails, the service of the failed link is switched to the normal link for forwarding.

In the foregoing embodiment of the present application, when the active and standby single boards determine that the service message is a known unicast message, the active and standby links perform load sharing and corresponding forwarding. In this way, the active and standby boards are used to forward packets through load sharing, which solves the problem that the related technology can only forward through one of the links of the active and standby boards but cannot effectively use the network bandwidth, and the bandwidth utilization is higher.

It should be noted that, before step S11 is performed, the load sharing method further includes the steps of acquiring configuration information, and forming a cross-subrack aggregation group according to the configuration information. The acquiring configuration information and forming a cross-subrack aggregation group based on the configuration information may include: creating an aggregation group port on the client-side device CE to achieve service load sharing; configuring the aggregation group port on the CE device, which can be configured as static or as required Manual aggregation group; establish MC-LAG on the first board and the second board, board A is the main board, board B is the backup board, and the upstream forwarding port C2 of the main board A and the backup board B For the aggregation group port associated with the aggregation group port on the client side, port L1 is the board interconnection port, and the protection mode selects load sharing; the upstream forwarding port C2 on the standby board prohibits the BUM message sending function; the main board A and Configure the designated vlan label between the standby single board B; establish the service on the entire network, and add all the relevant device ports of the single board to the service.

Referring to FIG. 16, the above BUM message scenario is taken as an example, and the load sharing method may include the following steps.

Step S21, at least one of the main single board and the standby single board receives an uplink BUM message.

Step S22: Determine that the uplink BUM message is received by the master board or the backup board.

When the master board receives the upstream BUM message, step S231 is executed; when the backup board receives the upstream BUM message, steps S241 to S242 are executed.

In step S231, the main single board directly forwards the received uplink BUM message normally.

In step S241, the standby single board prohibits the ability of its upstream forwarding port to report the BUM message, and normally forwards the received upstream BUM message.

In step S242, the standby single board tags and forwards the received uplink BUM message to the main single board, and reports to the client side through the uplink forwarding port of the main single board.

In the above-mentioned embodiment of this application, when the active and standby boards determine that the service message is an upstream BUM message, the standby board prevents the upstream forwarding port from reporting BUM messages to ensure that there is only one node in the active and standby boards at the same time Forwarding the upstream BUM message to the client side prevents the upstream BUM message from forming a loop. On the basis of ensuring the bandwidth utilization of the main board single board, the forwarding capability of the active and standby boards is improved. It should be noted that in this embodiment, restricting the upstream BUM message capability of at least one of the first board and the second board according to the setting rules is to prohibit the upstream forwarding port C2 of the standby board. Take the reporting capability of BUM packets as an example. By disabling the reporting capability of BUM packets on the upstream forwarding port C2 of the backup board, the backup board does not need to perform the load sharing and forwarding of upstream BUM packets. The upstream BUM messages received by the single board are distinguished, and the main single board can forward it normally. In this way, the first single board and the second single board can greatly simplify the way of forwarding BUM packets and avoid the problem of BUM packets forming a loop.

Referring to FIG. 17, the following BUM message scenario is taken as an example, and the load sharing method may include the following steps.

Step S31, at least one of the main single board and the standby single board receives the downlink BUM message.

Step S22: It is determined that the downlink BUM message is received by the master board or the backup board.

When the master single board receives the downlink BUM message, steps S331 to S332 are executed; when the slave single board receives the downlink BUM message, steps S341 to S342 are executed.

Step S331: When the main single board receives the downlink BUM message, the main single board directly forwards the received downlink BUM message normally.

In step S332, the main single board normally forwards the downlink BUM message carrying the vlan tag and forwarded by the main single board on other ports except the uplink forwarding port C2.

Step S341: The standby single board forwards the received downlink BUM message on other ports except the single board interconnection port L1 normally, and adds the vlan tag to the downstream BUM message and forwards it to the single board interconnection port L1. Main board.

In step S342, the standby single board prohibits its upstream forwarding port C2 from reporting the BUM message, and the received downstream BUM message forwarded by the primary single board is discarded at its upstream forwarding port C2.

In the above-mentioned embodiment of this application, when the active and standby boards determine that the service message is a downlink BUM message, the standby board prevents the upstream forwarding port from reporting the BUM message to ensure that the standby board is forwarded to the main board. Downlink BUM packets will not be forwarded and sent back to the client side through the upstream forwarding port of the main board to prevent the downstream BUM packets from forming a loop. On the basis of ensuring the bandwidth utilization of the main board, the forwarding of the main and standby boards is improved. ability. It should be noted that in this embodiment, restricting the upstream BUM message capability of at least one of the first board and the second board according to the setting rules is to prohibit the upstream forwarding port C2 of the standby board. Take the reporting capability of BUM packets as an example. By disabling the reporting capability of BUM packets on the upstream forwarding port C2 of the backup board, when performing business load sharing and forwarding, the backup board can only add designated labels for the downstream BUM packets and forward them To the main single board, and the main single board recognizes the downstream BUM packet forwarded by the standby single board and discards it at the upstream forwarding port C2. In other scenarios, the main single board can forward it normally. In this way, the first single board and the second single board can greatly simplify the way of forwarding BUM packets and avoid the problem of BUM packets forming a loop.

Claims

A load sharing method includes:

At least one of the first single board and the second single board receives a service message, wherein the first single board and the second single board are each other as a master and a backup board;

In response to determining that the service message is a non-broadcast, unknown unicast, or multicast BUM message, load sharing and corresponding forwarding are performed by the link where the first board is located and the link where the second board is located.
The method of claim 1, further comprising:

In response to determining that the service message is a BUM message, restrict the uplink BUM message capability of at least one of the first single board and the second single board according to the setting rule, and limit the uplink BUM message capability The subsequent first single board and the second single board perform corresponding forwarding.
The method according to claim 2, wherein, in response to determining that the service message is a BUM message, the uplink BUM of at least one of the first single board and the second single board is restricted according to a set rule The message capability, the corresponding forwarding of the first board and the second board after limiting the upstream BUM message capability, includes:

Disabling the uplink BUM message function on the second board;

In response to determining that the service message is an uplink BUM message, report the received uplink BUM message from the first board to the client side.
The method according to claim 3, wherein the reporting the received uplink BUM message from the first board to the client side comprises:

Adding a designated tag to the received uplink BUM message by the second single board to obtain an uplink forwarding BUM message, and forwarding the uplink forwarding BUM message to the first single board;

The first single board reports the received uplink BUM message and the received uplink forwarded BUM message forwarded by the second single board to the client side.
The method according to claim 4, wherein the reporting the received uplink BUM message from the first board to the client side further comprises:

In the case that the link where the first single board is located fails, the second single board enables the uplink BUM message function;

The second single board reports the received uplink BUM message and the received uplink forwarded BUM message forwarded by the first single board to the client side.
The method according to claim 2, wherein, in response to determining that the service message is a BUM message, the uplink BUM of at least one of the first single board and the second single board is restricted according to a set rule The message capability, the corresponding forwarding of the first board and the second board after limiting the upstream BUM message capability, includes:

In response to determining that the service message is an uplink BUM message, the first single board and the second single board report the uplink BUM message received by the local end to the client side, and forward the received opposite end The upstream forwarded BUM packet is discarded.
The method according to claim 6, wherein the first single board and the second single board report the uplink BUM message received at the local end to the client side, and forward the received uplink BUM message forwarded by the opposite end BUM packets are discarded, including:

The first board reports the uplink BUM message received by the local end to the client side, adds the first label to the received uplink BUM message to obtain the uplink forwarded BUM message, and forwards the uplink BUM message Forward to the second board;

The second board reports the uplink BUM message received by the local end to the client side, adds the second label to the received uplink BUM message to obtain the uplink forwarded BUM message, and forwards the uplink BUM message Forward to the first board;

The first single board and the second single board respectively discard the received uplink forwarding BUM messages forwarded by the opposite end at their respective uplink forwarding ports.
The method according to claim 2, wherein, in response to determining that the service message is a BUM message, the uplink BUM of at least one of the first single board and the second single board is restricted according to a set rule The message capability, the corresponding forwarding of the first board and the second board after limiting the upstream BUM message capability, includes:

Disabling the uplink BUM message function on the second board;

In response to determining that the service message is a downlink BUM message, the second board adds a designated tag to the received downlink BUM message to obtain a downlink forwarded BUM message, and forwards the downlink forwarded BUM message to all For the first single board, the first single board discards the received downstream forwarding BUM message forwarded by the second single board at the upstream forwarding port of the first single board.
The method according to claim 2, wherein, in response to determining that the service message is a BUM message, the uplink BUM of at least one of the first single board and the second single board is restricted according to a set rule The message capability, the corresponding forwarding of the first board and the second board after limiting the upstream BUM message capability, includes:

In response to determining that the service message is a downlink BUM message, the first single board and the second single board respectively forward the received downlink BUM message to the network side, and forward the received downlink BUM message to the network side. Downlink forwarding BUM packets are discarded at their respective upstream forwarding ports.
The method according to claim 9, wherein the discarding the received downlink forwarding BUM message forwarded by the opposite end at the respective uplink forwarding port comprises:

The first single board adds a first label to the received downlink BUM message to obtain a downlink forwarded BUM message, and forwards the downlink forwarded BUM message to the second single board, and the second single board The received downstream forwarding BUM message forwarded by the first single board is discarded at the upstream forwarding port of the second single board;

The second single board adds a second label to the received downlink BUM message to obtain a downlink forwarded BUM message, and forwards the downlink forwarded BUM message to the first single board, and the first single board will The received downstream forwarding BUM message forwarded by the second single board is discarded at the upstream forwarding port of the first single board.
The method according to any one of claims 1 to 10, wherein before at least one of the first single board and the second single board receives a service message, the method further comprises:

Obtain aggregation group configuration information;

According to the aggregation group configuration information, respectively associating the uplink forwarding port of the first single board with the aggregation group port on the client side, and the uplink forwarding port of the second single board with the aggregation group port on the client side, respectively, And form a cross-sub-rack aggregation group, where the cross-sub-rack aggregation group is configured to perform load sharing through the associated aggregation group ports.
The method according to any one of claims 1 to 10, wherein:

Acquiring a master node selection instruction based on a third single board communicatively connected with the first single board and a fourth single board communicatively connected with the second single board;

The master node is determined according to the master node selection instruction, and the link between the master node and a node adjacent to the master node is set as a low-power lossy network routing protocol RPL link.
A load sharing system includes a first single board and a second single board that are mutually active and standby boards, wherein,

At least one of the first single board and the second single board is configured to receive service packets;

The link where the first single board is located and the link where the second single board is located are set to: in response to determining that the service message is a non-broadcast, unknown unicast, or multicast BUM message, perform load sharing and corresponding forwarding .
The system of claim 13, wherein:

At least one of the first single board and the second single board is further configured to: in response to determining that the service message is a BUM message, restrict the respective upstream BUM message capabilities according to a setting rule, and restrict the upstream After the BUM message is capable, it will be forwarded accordingly.
The system of claim 14, wherein:

The second board is set to: disable the uplink BUM message function;

The first single board and the second single board are set to: in response to determining that the service packet is an uplink BUM packet, report the received uplink BUM packet from the first single board to the client side .
The system of claim 14, wherein:

The second board is set to: disable the uplink BUM message function; in response to determining that the service message is a downlink BUM message, add a designated label to the received downlink BUM message to obtain a downlink forwarded BUM message , And forward the downlink forwarding BUM message to the first board;

The first single board is configured to discard the received downlink forwarding BUM message forwarded by the second single board at the uplink forwarding port of the first single board.
The system according to claim 15 or 16, wherein:

The second single board is further configured to enable the uplink BUM message function in the case that the link where the first single board is located fails.
The system according to claim 14, wherein the first single board and the second single board are configured as:

In response to determining that the service message is an uplink BUM message, report the uplink BUM message received by the local end to the client side, and discard the received uplink forwarded BUM message forwarded by the opposite end; and/or

In response to determining that the service message is a downlink BUM message, the downlink BUM message received by the local end is forwarded to the network side, and the downlink forwarded BUM message forwarded by the opposite end is received at the respective uplink forwarding port throw away.
The system according to claim 13, wherein the first single board and the second single board are further configured as:

Obtain aggregation group configuration information;

According to the aggregation group configuration information, the first single board connects the upstream forwarding port of the first single board to the client-side aggregation group port, and the second single board connects the upstream forwarding port of the second single board It is associated with the port of the aggregation group and forms a cross-sub-rack aggregation group, wherein the cross-sub-rack aggregation group is configured to perform load sharing through the associated port of the aggregation group.
A single board includes a load sharing module and a message processing module, in which,

The load sharing module is configured to receive service messages;

The message processing module is configured to respond to determining that the service message is a non-broadcast, unknown unicast, or multicast BUM message, and the link where the single board is located and the single board are mutually active and standby. The link on which the other board of the board is located performs load sharing and corresponding forwarding.
The single board according to claim 20, wherein:

The message processing module is further configured to, in response to determining that the service message is a BUM message, limit the uplink BUM message capability of the board according to a setting rule, and based on the limitation of the uplink BUM message capability The single board and the other single board perform corresponding forwarding.
The single board according to claim 20, wherein:

The message processing module is also set to prohibit the upstream BUM message function of the upstream forwarding port of the single board; in response to determining that the service message is an upstream BUM message, add a specified upstream BUM message to the received upstream BUM message The label obtains the upstream forwarded BUM message, and forwards the upstream forwarded BUM message to the other single board, and the other single board forwards the upstream forwarded BUM message to the upstream of the other single board Report to the client at the forwarding port; or, in response to determining that the service message is a downlink BUM message, add the designated label to the received downlink BUM message to obtain a downlink forwarded BUM message, and forward the downlink The BUM message is forwarded to the other single board, and the other single board discards the downstream forwarded BUM message at the upstream forwarding port of the other single board.
The single board according to claim 22, wherein:

The message processing module is further configured to enable the uplink BUM message function of the uplink forwarding port of the single board in the case that the link where the other single board is located fails.
The single board according to claim 20, wherein:

The message processing module is further configured to, in response to determining that the service message is an uplink BUM message, report the received uplink BUM message to the client side, and add a designated tag to the received uplink BUM message to obtain the uplink Forward the BUM message, and forward the upstream forwarded BUM message to the other single board, and discard the received upstream forwarded BUM message forwarded by the other single board; or, in response to determining the The service message is a downlink BUM message, forward the received downlink BUM message to the network side, add the designated label to the received downlink BUM message to obtain a downlink forwarded BUM message, and forward the downlink BUM message The message is forwarded to the other single board, and the received downstream forwarding BUM message forwarded by the other single board is discarded at the upstream forwarding port of the single board.
The single board according to any one of claims 20 to 24, wherein:

The load sharing module is further configured to obtain aggregation group configuration information, associate the uplink forwarding port of the single board with the aggregation group port on the client side according to the aggregation group configuration information, and form a cross-subrack aggregation group.
A load sharing device includes a processor and a memory for storing a computer program that can run on the processor; wherein,

When the processor is used to run the computer program, it executes the load sharing method according to any one of claims 1 to 12.
A storage medium, wherein executable instructions are stored in the storage medium, and when the executable instructions are executed by a processor, the load sharing method according to any one of claims 1 to 12 is implemented.