CN111491334B

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

Info

Publication number: CN111491334B
Application number: CN201910085733.2A
Authority: CN
Inventors: 刘新菊
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2019-01-29
Filing date: 2019-01-29
Publication date: 2021-05-25
Anticipated expiration: 2039-01-29
Also published as: WO2020156355A1; CN111491334A

Abstract

The embodiment of the invention discloses a load sharing method, a device, a system, a single board and a storage medium, wherein the method comprises the following steps: the first single board and/or the second single board receives the service message; the first single board and the second single board are main and standby single boards; and when the service message is determined to be a non-BUM message, carrying out load sharing and corresponding forwarding 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

Technical Field

The present invention relates to a link aggregation load sharing technology, and in particular, to a load sharing method, apparatus, system, board, and storage medium.

Background

With the development of 5G networks, new requirements are put forward for bandwidth, time delay, service forwarding capability, and the like, and at present, a multi-chassis link aggregation group (mclag) supports aggregation of ethernet links of two sub-chassis together to form a link aggregation group across sub-chassis, so as to provide link and sub-chassis level active/standby protection for services.

In the related technology, the cross-subframe channel protection technology only realizes the cross-subframe active/standby protection of the service, that is, the service is only forwarded on the main link and the main device under the normal condition. When the single board of the main node device detects that the transmission quality and the link state of the client side are abnormal, the single board switches the client service to the single board of the standby node through the cross-subframe aggregation group, so that although service protection can be performed, the service can only be forwarded from the main or standby link, service load sharing cannot be realized, and the bandwidth of the cross-subframe aggregation group is not fully utilized.

Disclosure of Invention

In order to solve the existing technical problem, embodiments of the present invention provide a load sharing method, apparatus, system, board, and storage medium with higher bandwidth utilization and better forwarding capability.

In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:

in a first aspect of the embodiments of the present application, a load sharing method is provided, including: the first single board and/or the second single board receives the service message; the first single board and the second single board are main and standby single boards; and when the service message is determined to be a non-BUM message, carrying out load sharing and corresponding forwarding by the link where the first single board is located and the link where the second single board is located.

In a second aspect of the embodiments of the present application, a load sharing system is provided, where the load sharing system includes a first board and a second board that are a main board and a standby board, and the system includes: the first single board and/or the second single board receive a service message; and when the service message is determined to be a non-BUM message, carrying out load sharing and corresponding forwarding by the link where the first single board is located and the link where the second single board is located.

A third aspect of the present embodiment provides a board, including a load sharing module and a message processing module, where the load sharing module is configured to receive a service message; the message processing module is configured to, when determining that the service message is a non-BUM message, perform load sharing and corresponding forwarding on a link where the board is located and a link where another board that is a primary/standby board with the board is located.

In a fourth aspect of the embodiments of the present application, there is provided a load sharing apparatus, including a processor and a memory for storing a computer program capable of running on the processor; the processor is configured to execute the load sharing method according to any embodiment of the present application when the processor runs the computer program.

In a fifth aspect of the embodiments of the present application, a storage medium is provided, where executable instructions are stored in the storage medium, and when executed by a processor, the executable instructions implement the load sharing method according to any embodiment of the present application.

In the load sharing method, apparatus, system, board and storage medium provided in the foregoing embodiments, the first board and/or the second board receives the service packet, and when it is determined that the service packet is a non-BUM packet, the link where the first board is located and the link where the second board is located perform load sharing and corresponding forwarding, so that the problem that forwarding can only be performed through one link of the active and standby boards in the prior art is solved by forwarding the packet through load sharing by the first board and the second board, and thus the bandwidth utilization rate is higher.

Drawings

Fig. 1 is a schematic diagram of a load sharing system in the related art;

fig. 2 is a schematic diagram of an architecture of a load sharing system according to an embodiment of the present application;

fig. 3 is a schematic flowchart illustrating a load sharing method according to an embodiment of the present application;

fig. 4 is a schematic diagram of a forwarding flow of a load sharing method in an embodiment of the present application, taking downlink known unicast service as an example;

fig. 5 is a schematic diagram of a forwarding flow of a load sharing method in an embodiment of the present application, taking an uplink known unicast service as an example; (ii) a

Fig. 6 is a flowchart illustrating a load sharing method according to another embodiment of the present application;

fig. 7 is a schematic diagram of a forwarding flow of a load sharing method in an embodiment of the present application, taking receiving an uplink BUM message by a main board as an example;

fig. 8 is a schematic diagram of a forwarding flow of a load sharing method in an embodiment of the present application, taking a standby board to receive an uplink BUM message as an example;

fig. 9 is a schematic diagram of a forwarding flow of a load sharing method in an embodiment of the present application, taking a main single board receiving a downlink BUM message as an example;

fig. 10 is a schematic diagram of a forwarding flow, in which a standby board receives a downlink BUM message as an example, in a load sharing method in an embodiment of the present application;

fig. 11 is a schematic diagram of a forwarding flow in which a load sharing method in an embodiment of the present application adopts a combination of a sub-frame aggregation group and an ethernet multi-ring protection technology;

FIG. 12 is a block diagram of a load sharing system according to another embodiment of the present application;

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

fig. 14 is a schematic structural diagram of a load sharing device according to an embodiment of the present application;

fig. 15 is a schematic flowchart of a load sharing method, which takes a known unicast message scenario as an example, in an alternative embodiment of the present application;

fig. 16 is a schematic flowchart of a load sharing method, which is exemplified by an uplink BUM message scenario, in an alternative embodiment of the present application;

fig. 17 is a flowchart illustrating a load sharing method, which is exemplified by a downlink BUM message scenario, in an alternative embodiment of the present application.

Detailed Description

The technical scheme of the invention is further elaborated by combining the drawings and the specific embodiments in the specification. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

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

Before further detailed description of the present invention, terms and expressions referred to in the embodiments of the present invention are described, and the terms and expressions referred to in the embodiments of the present invention are applicable to the following explanations.

1) A multi-chassis link aggregation group (mclag), also called a link aggregation group between multiple chassis, refers to that two corresponding ports distributed on two same boards are aggregated into a protection group, so as to realize the protection of ports between boards. One access device can simultaneously access two upstream physical devices through link bundles formed by spanning the sub-frame aggregation groups. The single boards are combined by taking the sub-frame as a unit, one sub-frame can carry a plurality of single boards of different types, and one network element device can comprise one or more sub-frames.

2) The BUM message refers to a Broadcast message, an Unknown unicast message, and a Multicast message.

3) An aggregation group port, also called an ethernet channel, refers to a group of physical ports that are combined together to form a logical channel, i.e., a channel-group.

In the related art, the existing sub-frame-crossing channel protection technology only realizes sub-frame-crossing active/standby protection of a service, that is, the service is only forwarded on a main link and main equipment under a normal condition. Referring to fig. 1, when a single board of a main node device detects that transmission quality and link status of a client side are abnormal, the single board switches a service of the client side to a single board of a standby node through a cross-subrack aggregation group, so that although service protection can be performed, the service can only be forwarded from a main or standby link, and bandwidth of the cross-subrack aggregation group cannot be fully utilized.

In order to solve the above problems, the inventors of the present application have found in research that a load sharing protection mode may be set for a sub-rack-spanning aggregation group, and a method for implementing load sharing for a client side service by the sub-rack-spanning aggregation group, in which a main link and a standby link operate simultaneously, fully utilize a link bandwidth on a network.

Further, in the method for implementing load sharing for the client side service by the cross-subrack aggregation group, the uplink BUM message capability of the main link and the standby link is limited by setting a rule for the BUM message, so that the ring formation of the BUM message between the client side and the main and standby boards can be avoided, and the bandwidth utilization rate and the forwarding capability of the network in the process of forwarding the BUM message through the main link and the standby link in a balanced manner at the same time are ensured.

Referring to fig. 2, a schematic diagram of an architecture of a load sharing system according to an embodiment of the present application includes a first board and a second board that are mutually a primary board and a backup board. In the embodiment of the present application, a first board and a second board that are a master board and a standby board respectively refer to two boards of the same type that together form a span subframe aggregation group, and the first board and the second board may have the same configuration, and according to the aggregation group configuration information, the first board may be selectively configured as the master board and the second board may be configured as the standby board; or, the second board may be selectively configured as the main board and the first board may be configured as the standby board according to the aggregation group configuration information. For convenience of description and understanding, the main board a is taken as a first board, and the standby board B is taken as a second board. The board interconnection port L1 of the first board and the board interconnection port L1 of the second board are interconnected. The uplink forwarding port C2 of the first board and the uplink forwarding port C2 of the second board are associated with the aggregation group port C1 of the client side to form a cross-subrack aggregation group. The first single board and the second single board share the load of the incoming service through the cross sub-frame aggregation group, so that the service message (namely, the downlink message) entering from the client side is transmitted to the network side by the first single board and the second single board in a balanced manner, and the service message (namely, the uplink message) entering from the network side is transmitted to the client side by the first single board and the second single board in a balanced manner.

Referring to fig. 3, a schematic flow chart of a load sharing method according to an embodiment of the present application is shown, which can be applied to the load sharing system shown in fig. 1, and the method includes the following steps:

step 101, a first single board and/or a second single board receives a service message; the first single board and the second single board are main and standby single boards;

here, the first single board and the second single board are mutually a master single board and a standby single board, that is, the first single board and the second single board are two same types of single boards which together form a span subframe aggregation group, where the master single board may be the first single board, and the standby single board may be the second single board; or the main veneer may be the second veneer and the standby veneer may be the first veneer. The receiving of the service message by the first board and/or the second board means that the different actual scenarios include that the first board and the second board receive the service message respectively, or that the first board and the second board receive the service message together.

Step 103, when determining that the service message is a non-BUM message, performing load sharing and corresponding forwarding by the link where the first board is located and the link where the second board is located.

Here, a non-BUM packet refers to other types of packets besides BUM (i.e. broadcast packet, unknown unicast packet, multicast packet), such as known unicast packet. The link where the first board is located and the link where the second board is located perform corresponding forwarding for load sharing, that is, the service is forwarded in a balanced manner through a main link and a standby link which are formed by the link where the first board is located and the link where the second board is located, so that the link bandwidth on the network is fully utilized.

Referring to fig. 4, taking the case that the first board and the second board receive the downlink packet that enters from the client side (CE) as an example, when the downlink packet is a known unicast packet, the load is directly shared by the link where the first board is located and the link where the second board is located, and the downlink packet is forwarded according to the destination MAC address after reaching the first board and the second board. Referring to fig. 5, taking the case that the first board and the second board receive the uplink packet entering from the network side as an example, when the uplink packet is the known unicast packet, the first board and the second board directly forward according to the destination MAC address, and perform load sharing and forward to the client side through the link where the first board is located and the link where the second board is located.

In the above embodiment of the present application, a first board and/or a second board receives a service packet, and when it is determined that the service packet is a non-BUM packet, a link where the first board is located and a link where the second board is located perform load sharing and corresponding forwarding; therefore, by forwarding the message through load sharing by the first single board and the second single board, the problem that the bandwidth of a link cannot be fully utilized because the message can be forwarded only through one link of the main single board and the standby single board in the prior art is solved, and the bandwidth utilization rate is higher.

In some embodiments, referring to fig. 6, the load sharing method further includes:

step 105, when it is determined that the service packet is a BUM packet, limiting an uplink BUM packet capability of at least one of the first board and the second board according to a set rule, and performing corresponding forwarding through the first board and the second board after the uplink BUM packet capability limitation.

Here, the BUM packet refers to a Broadcast packet, an unknown unicast packet, and a multicast packet. When the service message is a BUM message, the BUM message is broadcasted between the first board and the second board, and taking a downlink BUM message entering from the client side as an example, the downlink BUM message of the first board may return to the client side again through the second board, so that the BUM message forms a ring among the first board, the second board and the client side. The limiting of the uplink BUM message capability of at least one of the first board and the second board according to the setting rule may refer to prohibiting a BUM message reporting capability of the first board or the second board according to a forwarding condition of the BUM message, or limiting a reporting capability of the first board and the second board for a BUM message forwarded by an opposite terminal, and performing corresponding forwarding on the first board and the second board after the uplink BUM message capability limitation, so that a problem of looping of the BUM message among the first board, the second board and the client side can be avoided.

In this embodiment of the present application, when the service packet is a BUM packet, the first board and the second board perform corresponding forwarding after limiting the uplink BUM packet capability of at least one of the first board and the second board according to a set rule, so as to avoid the problem of looping the BUM packet between the first board, the second board, and the client side, and improve the forwarding capabilities of the first board and the second board.

In some embodiments, the step 105 comprises:

the second single board forbids the function of the uplink BUM message;

and when the service message is determined to be an uplink BUM message, reporting the received uplink BUM message to a client side by the first single board.

Here, the disabling of the uplink BUM message function by the second board means disabling the reporting capability of the BUM message by the uplink forwarding port C2 of the second board. Thus, when the service messages received by the first board and the second board are uplink BUM messages from the network side, the second board forwards the received uplink BUM messages to the first board from the board interconnection port L1, and the first board reports the received uplink BUM messages to the client side.

Referring to fig. 7, taking the case that the first board receives an uplink packet entering from the network side as an example, when the uplink packet is a BUM packet, the first board forwards the received uplink BUM packet normally through the uplink forwarding port C2, and when the BUM packet passes through the uplink forwarding port C2 of the second board, the BUM packet is blocked, so that the uplink BUM packet is ensured to be reported to the client side only through the uplink forwarding port C1 of the first board. Referring to fig. 8, taking the example that the second board receives the uplink message entering from the network side as an example, when the uplink message is the BUM message, the second board receives the uplink BUM message and directly performs normal forwarding, and when the BUM message passes through the uplink forwarding port C2 of the second board, the BUM message is blocked, and the BUM message that needs to be uplinked to the client side can only be forwarded through the uplink forwarding port C2 of the first board, so that it can be ensured that only one node of the first board and the second board forwards the uplink BUM message to the client side at the same time, and ring formation of the uplink BUM message is prevented.

In the above embodiment of the present application, when the service packet is an uplink BUM packet, limiting the uplink BUM packet capability of at least one of the first board and the second board according to the set rule means prohibiting the uplink forwarding port C2 of the second board from performing the reporting capability of the BUM packet, so as to ensure that only one node of the first board and the second board forwards the uplink BUM packet to the client side at the same time, and prevent the uplink BUM packet from looping.

In some embodiments, the reporting, by the first board, the received uplink BUM packet to the client side includes:

the second single board adds a specified label to the received uplink BUM message and forwards the uplink BUM message to the first single board;

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

Here, the designated label may be a Virtual Local Area Network (vlan) mark that is set between the first board and the second board in the cross-subrack aggregation group, and the vlan mark is added in front of the BUM message, so that the first board can distinguish the uplink forwarding BUM message forwarded by the second board from the uplink BUM message received by the Local terminal.

In the above embodiment of the present application, the second board disables the function of the uplink BUM packet, the second board adds a vlan tag to the received uplink BUM packet to form an uplink forwarding BUM packet and forwards the uplink forwarding BUM packet to the first board, and the first board reports the uplink forwarding BUM packet and the uplink BUM packet received by the local terminal to the client side, so that it is ensured that the uplink BUM packet can only be sent to the client side through the uplink forwarding port C2 of the first board, and looping of the uplink BUM packet is avoided.

Wherein, reporting the received uplink BUM message to the client side by the first board comprises:

when the link where the first single board is located is in fault, the second single board starts the uplink BUM message function;

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

Here, the failure of the link where the first board is located refers to a situation that the link where the first board is located cannot perform normal service forwarding. When the link where the first single board is located is in fault, the second single board switches the function of forbidding the uplink BUM message to the function of starting the uplink BUM message, switches the service of the link where the first single board is located to the link where the second single board is located, and reports the received uplink BUM message and the received uplink forwarding BUM message forwarded by the first single board to the client side through the second single board, so that the service protection function is realized. In the above embodiment of the present application, compared with a traditional protection mode, a forwarding manner of load sharing of the first board and the second board is adopted, so as to implement balanced sharing and forwarding of service protection, and when one of the links fails, the service packet can be switched to a normal link, so as to implement service protection, and on the premise of not increasing cost, the bandwidth utilization rate, forwarding capability and reliability of service transmission are improved in different application scenarios.

In some embodiments, the step 105 comprises:

when the service message is determined to be an uplink BUM message, the first single board and the second single board report the uplink BUM message received by the local terminal to the client side, and discard the received uplink forwarding BUM message of the opposite terminal.

Here, limiting the uplink BUM message capability of at least one of the first board and the second board according to the setting rule means limiting the reporting capability of the BUM message forwarded by the first board and the second board to the opposite terminal. When the service message is determined to be an uplink BUM message, the first board reports the uplink BUM message received by the home terminal to the client side, and discards the uplink forwarding BUM message forwarded by the second board when passing through the uplink forwarding port C2, the second board reports the uplink BUM message received by the home terminal to the client side, and discards the uplink forwarding BUM message forwarded by the first board when passing through the uplink forwarding port C2, so that the same uplink BUM message can be ensured to be only sent to the client side through the uplink forwarding port C2 of one of the first board and the second board, and looping of the uplink BUM message is avoided.

The reporting, by the first board and the second board, the uplink BUM packet received by the home terminal to the client side, and discarding the received uplink forwarding BUM packet of the opposite terminal includes:

the first single board reports the uplink BUM message received by the home terminal to the client side, adds a first label to the received uplink BUM message and forwards the uplink BUM message to the second single board;

the second single board reports the uplink BUM message received by the home terminal to the client side, adds a second label to the received uplink BUM message and forwards the uplink BUM message to the first single board;

and the first single board and the second single board respectively discard the received uplink forwarding BUM message of the opposite terminal at an uplink forwarding port.

Here, in order to facilitate the first board to distinguish the uplink BUM message received by the home terminal from the uplink forwarding BUM message forwarded by the second board, the first board adds a first tag to the received uplink BUM message and forwards the uplink BUM message to the second board; in a similar way, in order for the second board to distinguish the uplink BUM message received by the home terminal from the uplink forwarding BUM message forwarded by the first board, the second board adds a second label to the received uplink BUM message and forwards the uplink BUM message to the first board; the first board discards the received uplink forwarding BUM message forwarded by the second board when passing through the uplink forwarding port C2, and the second board discards the received uplink forwarding BUM message forwarded by the first board when passing through the uplink forwarding port C2, so that it can be ensured that the same uplink BUM message can only be sent to the client side through the uplink forwarding port C2 of one of the first board and the second board, thereby avoiding looping of the uplink BUM message.

In some embodiments, the step 105 comprises:

the second single board forbids the function of the uplink BUM message;

when the service message is determined to be a downlink BUM message, the second single board forwards the received downlink BUM message to the first single board after adding a specified label, and the first single board discards the received downlink forwarding BUM message forwarded by the second single board at an uplink forwarding port.

Here, limiting 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 uplink forwarding port C2 of the second board from reporting the BUM message capability. The designated label may be a Virtual Local Area Network (vlan) mark disposed between the first board and the second board in the cross-subrack aggregation group, and the vlan mark is added in front of the BUM message, so that the first board can distinguish the downlink forwarding BUM message forwarded by the second board from the downlink BUM message received by the Local terminal. In order to avoid that the second board transmits the received downlink BUM message entering from the client side to the first board, and then the downlink BUM message is transmitted back to the client side through the uplink forwarding port C2 of the first board, the second board adds a designated label when transmitting the downlink BUM message to the first board, so that the first board discards the received downlink forwarding BUM message transmitted by the second board at the uplink forwarding port.

Referring to fig. 9, taking an example that a first board receives a downlink packet entering from a client side (CE), when the downlink packet is a BUM packet, the first board directly performs normal forwarding, where the first board forwards the received downlink BUM packet to a second board, and when the downlink BUM packet passes through an uplink forwarding port C2 of the second board, the downlink BUM packet is blocked, so that it is ensured that the downlink BUM packet received from the first board is not forwarded back to the CE any more, and looping of the downlink BUM packet is avoided. Referring to fig. 10, taking the example that the second board receives the downlink packet entering from the client side, when the downlink packet is the BUM packet, the second board performs normal forwarding, adds a specific label to the downlink BUM packet, and forwards the downlink BUM packet to the first board through the board interconnection port L1, after the first board receives the downlink forwarding BUM packet added with the specific label, the first board performs normal forwarding on the downlink forwarding BUM packet at the other ports except the uplink forwarding port C2, and the downlink forwarding BUM packet is discarded through the uplink forwarding port C2 of the first board, so that it is ensured that the downlink BUM packet received from the second board is not forwarded back to the CE any more, and looping of the downlink BUM packet is avoided.

In the above embodiment of the present application, when the first board and/or the second board receives the service packet and determines that the service packet is a downlink BUM packet entered from the client side, the second board forwards the received downlink BUM packet to the network side, and adds a specific tag to the received downlink BUM packet to form a downlink forwarding BUM packet, and forwards the downlink forwarding BUM packet to the first board through the board interconnection port L1, and the downlink forwarding BUM packet is discarded when passing through the uplink forwarding port C2 of the first board, so that the downlink BUM packet can be prevented from returning to the client side again through the uplink forwarding port C2 of the first board, and looping of the downlink BUM packet is avoided.

In some embodiments, the step 105 comprises:

when determining that the service packet is a downlink BUM packet, the first board and the second board respectively forward the received downlink BUM packet to a network side, and discard the received downlink forwarding BUM packet of the opposite end at an uplink forwarding port.

Here, limiting the uplink BUM message capability of at least one of the first board and the second board according to the setting rule means limiting the reporting capability of the BUM message forwarded by the first board and the second board to the opposite terminal. When the service message is determined to be a downlink BUM message, the first board forwards the downlink BUM message received by the local terminal to the network side, and discards the downlink forwarding BUM message forwarded by the second board when passing through the uplink forwarding port C2, the second board forwards the downlink BUM message received by the local terminal to the network side, and discards the downlink forwarding BUM message forwarded by the first board when passing through the uplink forwarding port C2, so that it can be ensured that the downlink BUM message is forwarded back to the client side through the uplink forwarding port C2 of the opposite terminal after the downlink BUM message is correspondingly forwarded by load sharing through the first board and the second board, which results in ring formation of the BUM message, thereby avoiding the problem of ring formation of the BUM message, and improving the bandwidth utilization rate, forwarding capability and reliability of service transmission.

Wherein, the discarding the received downlink forwarding BUM message of the opposite terminal at the uplink forwarding port includes:

the first single board adds a first label to the received downlink BUM message and forwards the downlink BUM message to the second single board, and the second single board discards the received downlink forwarding BUM message of the first single board at an uplink forwarding port;

the second board adds a second label to the received downlink BUM message and forwards the downlink BUM message to the first board, and the first board discards the received downlink forwarding BUM message of the second board at an uplink forwarding port.

Here, in order to facilitate the first board to distinguish the downlink BUM message received by the home terminal from the downlink forwarding BUM message forwarded by the second board, the first board adds a first tag to the received downlink BUM message and forwards the downlink BUM message to the second board; in a similar way, in order for the second board to distinguish the downlink BUM message received by the home terminal from the downlink forwarding BUM message forwarded by the first board, the second board adds a second label to the received downlink BUM message and forwards the second label to the first board; the first board discards the received downlink forwarding BUM message forwarded by the second board when passing through the uplink forwarding port C2, and the second board discards the received downlink forwarding BUM message forwarded by the first board when passing through the uplink forwarding port C2, so that it can be ensured that the downlink BUM message is not forwarded back to the client side via the uplink forwarding port C2 of the opposite end to cause the ring formation of the BUM message after the downlink BUM message is correspondingly forwarded through load sharing by the first board and the second board, and the problem of the ring formation of the BUM message is avoided.

In some embodiments, referring to fig. 6 again, before the step 101, before the first board and/or the second board receives the service packet, the method includes:

step 1021, acquiring configuration information of the aggregation group;

step 1022, associating the uplink forwarding port of the first board, the uplink forwarding port of the second board, and the aggregation group port of the client side to form a sub-chassis aggregation group according to the aggregation group configuration information, where the sub-chassis aggregation group is configured to perform load sharing through the associated aggregation group ports.

Here, the aggregation group configuration information may be configured by being on the management side of the network. By obtaining the aggregation group configuration information, the two cascaded boards or devices can be configured as a master board and a slave board, and the uplink forwarding ports of the two boards are associated with the aggregation group port of the client side to form a cross-subrack aggregation group. Wherein the obtaining of the aggregation group configuration information may further include: and creating a vlan mark between the main node and the standby node, marking the forwarding BUM message, and blocking an associated aggregation group port of the standby board, namely an uplink BUM forwarding function of an uplink forwarding port C2, so as to ensure that only one node in the main node and the standby node can forward the BUM message in an uplink manner. Therefore, when the uplink and downlink services pass through the cross-subframe aggregation group, the load is shared and forwarded through the main and standby links where the two single boards are respectively located according to the set rule, and the bandwidth utilization rate and the service forwarding capacity of the links are improved.

In some embodiments, the load sharing method further comprises:

acquiring a main node selection instruction based on a third single board and a fourth single board which are respectively in communication connection with the first single board and the second single board;

and determining a main node according to the main node selection instruction, and setting a link between the main node and a node adjacent to the main node as an 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 which are in communication connection with the first single board and the second single board respectively. The method comprises the steps of selecting and determining a main node on a ring network by obtaining a main node selection instruction based on a third single board and a fourth single board, and setting a link between the main node and a node adjacent to the main node as a low power consumption lossy network Routing Protocol (RPL) link. When no Fault occurs in the link, in order to ensure that the service does not form a ring, the RPL link is in a blocking state, the link is detected by using connection Fault Management (cfm), and when an alarm (System Fault, SF) that the site cannot be connected on the bus occurs, the RPL link is set to be in a forwarding state, the ring network is switched, and ring network protection is generated.

Referring to fig. 11, ring network protection is established between the third board C and the fourth board D, the main board a, and the standby board B. And in the east-west port direction of the ring network, selecting a fourth single board D as a main node, and setting a link between the fourth single board D and the standby single board B as an RPL link. When the link fails, the RPL link is in a blocking state, and service is ensured not to be looped. The cfm is used for detecting the link, when SF alarm occurs, the RPL link is set to be in a forwarding state, the looped network is switched, and looped network protection is generated.

In the above embodiment of the present application, mctag and ethernet multi-ring protection technology (ERPS) are combined to implement a load sharing method, so as to ensure that a service does not form a ring in a ring networking architecture, and under a normal condition, the service performs load sharing through a cross-subframe aggregation group, and is forwarded on a main link and a standby link at the same time, thereby greatly improving bandwidth utilization and forwarding capability. Moreover, when any one link fails, the cross-subrack aggregation group can timely switch the service of the failed link to another normal link, thereby achieving the service protection. When the fault link is recovered, the service continues to share the load through the main link and the standby link.

In another aspect of the present embodiment, a load sharing system is provided, including a first board and a second board that are a master board and a standby board, where the first board and/or the second board receive a service packet; and when the service message is determined to be a non-BUM message, carrying out load sharing and corresponding forwarding by the link where the first single board is located and the link where the second single board is located.

The first single board and the second single board which are mutually a main single board and a standby single board mean that the first single board is the main single board and the second single board is the standby single board; or the first single board is a standby single board and the second single board is a main single board. Referring to fig. 12, taking a first board as a main board a and a second board as a standby board B as an example, a link where the first board is located is a main link, a link where the second board is located is a standby link, and an uplink forwarding port C2 of the first board and an uplink forwarding port C2 of the second board are associated with an aggregation group port C1 of a client side to form a cross-subrack aggregation group. When the load sharing system receives and transmits a service, the first single board and the second single board identify the type of a service message, and when the service message is determined to be a non-BUM message, the first single board and the second single board perform load sharing and corresponding forwarding, so that the first single board and the second single board complete cross-board aggregation service forwarding, and a main link and a standby link realize load sharing of a main link and a standby link together.

In some embodiments, when the first board and the second board determine that the service packet is a BUM packet, the first board and the second board limit an uplink BUM packet capability of at least one of the first board and the second board according to a set rule, and perform corresponding forwarding through the first board and the second board after the uplink BUM packet capability limitation.

Here, please refer to fig. 12 again, taking the example that the uplink BUM message capability of at least one of the first board and the second board is limited according to the setting rule, and the reporting capability of the BUM message of the uplink forwarding port of the second board is prohibited, the second board adds a vlan tag to the received uplink BUM message and forwards the uplink BUM message to the first board, so that the first board recognizes the uplink forwarding BUM message forwarded by the second board and reports the uplink forwarded BUM message to the client side through the uplink forwarding port C2 of the first board; and the second board adds a vlan tag to the received downlink BUM message and forwards the downlink BUM message to the first board, so that the first board can discard the downlink forwarding BUM message forwarded by the second board at the uplink forwarding port C2 of the first board after identifying the downlink forwarding BUM message forwarded by the second board. The second single board forbids the reporting capability of the BUM message of the uplink forwarding port of the second single board, adds a vlan tag to the BUM message and forwards the BUM message to the first single board, so that the BUM message processing is realized, and the problem of ring formation of the BUM message is avoided.

In some embodiments, when the service packet is determined to be a BUM packet, limiting, according to a set rule, an uplink BUM packet capability of at least one of the first board and the second board, and performing corresponding forwarding through the first board and the second board after the uplink BUM packet capability limitation includes:

the second single board forbids the function of the uplink BUM message;

and when the service message is determined to be an uplink BUM message, the first single board and the second single board report the received uplink BUM message to a client side through the first single board.

the second single board forbids the function of the uplink BUM message;

when determining that the service packet is a downlink BUM packet, the second board adds an assigned label to the received downlink BUM packet and forwards the downlink BUM packet to the first board, and the first board discards the received downlink forwarding BUM packet of the second board at an uplink forwarding port.

In some embodiments, the load sharing system further comprises:

and when the link where the first single board is located fails, the second single board starts the uplink BUM message function.

when the service message is determined to be an uplink BUM message, the first single board and the second single board report the uplink BUM message received by the local terminal to the client side, and discard the received uplink forwarding BUM message of the opposite terminal; or

When determining that the service packet is a downlink BUM packet, the first board and the second board forward the received downlink BUM packet to a network side, and discard the received downlink forwarding BUM packet of the opposite end at an uplink forwarding port.

Here, limiting the uplink BUM message capability of at least one of the first board and the second board according to the setting rule means limiting the reporting capability of the uplink forwarding ports of the first board and the second board to the received BUM message forwarded by the opposite terminal. If the first board adds a first label to the BUM message and forwards the BUM message to the second board, and the second board adds a second label to the BUM message and forwards the BUM message to the first board, the first label and the second label may be different vlan labels, so that the first board and the second board may identify the received BUM message forwarded by the opposite terminal and discard the BUM message at the upstream forwarding port C2. The first single board and the second single board respectively limit the reporting capability of the uplink forwarding port of the first single board and the second single board to the received BUM message of the opposite terminal, so that the BUM message processing is realized, and the problem of ring formation of the BUM message is avoided.

In some embodiments, the load sharing system further comprises:

the first single board and the second single board acquire aggregation group configuration information;

according to the aggregation group configuration information, the first single board associates the uplink forwarding port with the aggregation group port on the client side, and the second single board associates the uplink forwarding port with the aggregation group port to form a sub-shelf aggregation group, where the sub-shelf aggregation group is used for load sharing through the associated aggregation group port.

In the above 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 where the first board is located and the link where the second board is located perform load sharing and corresponding forwarding, so that the first board and the second board forward the packet through load sharing, thereby solving the problem that forwarding can only be performed through one link of the main board and the standby board in the prior art, and thus the bandwidth utilization rate is higher; when the first single board and the second single board determine that the service message is the BUM message, the first single board and the second single board perform corresponding forwarding after limiting the uplink BUM message capability of at least one of the first single board and the second single board according to the set rule, so that the problem of ring formation of the BUM message among the first single board, the second single board and the client side can be avoided, and the forwarding capability of the first single board and the second single board is improved.

In another aspect of the embodiment of the present invention, please refer to fig. 13, which further provides a board, including a load sharing module 21 and a message processing module 23, where the load sharing module 21 is configured to receive a service message; the message processing module 23 is configured to, when it is determined that the service message is a non-BUM message, perform load sharing and corresponding forwarding on a link where the board is located and a link where another board that is a primary/standby board with the board is located.

It should be noted that, the single board may refer to the first single board in any embodiment of the present application, and the other single board, which is a master/slave single board with the single board, refers to the second single board in any embodiment of the present application; the opposite is also true, the single board may also refer to the second single board in any embodiment of the present application, and the other single board that is a primary/standby single board with the single board refers to the first single board in any embodiment of the present application, which is not limited herein.

In some embodiments, the message processing module 23 is further configured to, when determining that the service message is a BUM message, limit an uplink BUM message capability of the board according to a set rule, and perform corresponding forwarding on the board and the other board after the uplink BUM message capability is limited.

In some embodiments, the message processing module 23 is further configured to prohibit an uplink BUM message function of the uplink forwarding port; the message processing module is configured to, when determining that the service message is an uplink BUM message, add a specific tag to the received uplink BUM message and forward the uplink BUM message to the other board, and report the uplink BUM message to the client side at an uplink forwarding port by the other board; or, the message processing module 23 is configured to, when determining that the service message is a downlink BUM message, add a specified label to the received downlink BUM message and then forward the received downlink BUM message, where the other board discards the downlink forwarding BUM message at an uplink forwarding port.

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

In some embodiments, the message processing module 23 is configured to, when determining that the service message is an uplink BUM message, report the uplink BUM message received by the home terminal to the client, add a specific tag to the received uplink BUM message, forward the uplink BUM message to the other board, and discard the received uplink forwarding BUM message of the other board; or, the message processing module is configured to forward the received downlink BUM message to a network side when it is determined that the service message is a downlink BUM message, add an assigned tag to the received downlink BUM message, forward the received downlink BUM message to the other board, and discard the received downlink forwarding BUM message of the other board at an uplink forwarding port.

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

In the implementation of the load sharing method, the single board provided in the foregoing embodiment is only illustrated by dividing the program modules, and in practical applications, the foregoing steps may be distributed by different program modules according to needs, that is, the internal structure of the program for implementing the load sharing method by the single board may be divided into different program modules, so as 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, where the BUM message processing module includes a mark creation vlan unit, a message determination unit, and a BUM message processing unit, where the mark creation vlan unit is configured to create a special mark vlan between the main board and the standby board, and is configured to identify a BUM message transmitted between the main board and the standby board; the message judging unit is used for judging the received message by the main and standby nodes and distinguishing the known unicast message from the BUM message; the BUM message processing unit is configured to close an uplink BUM function of an uplink forwarding port of the standby board, normally forward a downlink BUM message received by the main board, add a vlan tag to the downlink BUM message received by the standby board, forward the downlink BUM message to the main board for forwarding, for the uplink BUM message, the main board directly and normally forwards the uplink BUM message after receiving the uplink BUM message, and normally forward the uplink BUM message after receiving the uplink BUM message, but the uplink forwarding port of the standby board does not forward the uplink BUM message. The message forwarding module comprises 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, wherein the downlink known unicast message forwarding unit is used for forwarding according to a destination MAC address after directly sharing the load of the main link and the standby link; the downlink BUM message forwarding unit is used for directly forwarding 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; after adding a vlan tag to a downlink BUM message received by a standby single board, forwarding the downlink BUM message to a main single board, and normally forwarding the downlink BUM message by other ports, wherein after receiving the message with the vlan tag, the main single board normally forwards the downlink BUM message except not forwarding the downlink BUM message to an uplink forwarding port; the uplink known unicast message forwarding unit is used for forwarding the uplink known unicast message according to a target MAC address after the uplink known unicast message is directly subjected to load sharing through the main link and the standby link; the uplink BUM message forwarding unit is used for the main and standby single boards to directly perform normal forwarding after receiving the uplink BUM message, and the uplink forwarding port of the standby single board does not perform uplink forwarding. The above division of the program modules is also only for illustration.

In addition, the single board and the load sharing method provided by the above embodiments belong to the same concept, and the specific implementation process thereof is detailed in the method embodiments and will not be described herein again.

In another aspect of the embodiments of the present invention, a load sharing apparatus is further provided, where the load sharing apparatus may belong to one or more boards in a network, please refer to fig. 14, the load sharing apparatus includes a processor 201 and a storage medium 202 for storing a computer program capable of running on the processor 201, where when the processor 201 is configured to run the computer program, the steps of the load sharing method provided in any embodiment of the present application are executed. Here, the processor 201 and the storage medium 202 do not refer to a corresponding number of one, but may be one or more. The storage medium 202 may store an operating system and a load sharing apparatus for implementing the load sharing method provided by the embodiment of the present invention, and the processor 201 is configured to improve computing and controlling capabilities and support the operation of the entire server.

In another aspect of the embodiments of the present invention, a storage medium is further provided, for example, a memory including a computer program stored therein, where the computer program is executable by a processor to perform the steps of the load sharing method provided in any embodiment of the present invention. The storage medium can be FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface Memory, optical disk, or CD-ROM; or may be various devices including one or any combination of the above memories.

In order to further understand the implementation process of the load sharing method provided in the embodiment of the present application, the following description is given by way of example with reference to load sharing methods in different scenarios of known unicast message, uplink BUM message, and downlink BUM message transmission, respectively. Referring to fig. 15, taking a known unicast message scenario as an example, the load sharing method includes the following steps:

step S11, the main single board and/or the standby single board receives the known unicast message;

step S12, determining the known unicast message as an uplink message or a downlink message;

when the known downlink unicast message is determined, executing the steps S131 to S133; and executing the steps S141 to S143 when the unicast message is determined to be the uplink known unicast message.

Step S131, when the known downlink unicast message is determined, the main/standby link performs load sharing and then forwards the load shared message to the main/standby single board;

step S132, the main and standby single boards transmit according to the destination MAC address of the known unicast message;

step S133, when one of the main and standby links fails, the service of the failed link is switched to the normal link for forwarding;

step S141, when the known uplink unicast message is determined, the main and standby single boards forward according to the destination MAC address;

step S142, the service of the client side is load-shared by the main link and the standby link;

step S143, when one of the main and standby links fails, the service of the failed link is switched to the normal link for forwarding.

In the above embodiment of the present application, when the active/standby board determines that the service packet is a known unicast packet, the active/standby two links perform load sharing and corresponding forwarding, so that the problem that the network bandwidth cannot be effectively utilized because the packet is forwarded only through one link of the active/standby board in the prior art is solved by the active/standby board forwarding the packet through load sharing, and thus the bandwidth utilization rate is higher.

Before the step S11, the load sharing method further includes a step of acquiring configuration information and forming a cross-subrack aggregation group according to the configuration information. The obtaining of the configuration information and forming the cross-subframe aggregation group according to the configuration information may include: creating an aggregation group port on a customer side device (CE) to realize service load sharing; configuring an aggregation group port on a CE device, wherein a static or manual aggregation group can be configured according to needs; establishing mctag on a first single board and a second single board, wherein the single board A is a main single board, the single board B is a standby single board, uplink forwarding ports C2 of the main single board A and the standby single board B are aggregation group ports related to aggregation group ports of a client side, a port L1 is a single board interconnection port, and a protection mode selects load sharing; the uplink forwarding port C2 on the standby single board forbids the BUM message uploading function; configuring a designated vlan tag between the main single board A and the standby single board B; and establishing a service on the whole network, and adding the related equipment ports of all the single boards into the service.

Referring to fig. 16, in an uplink BUM message scenario as an example, the load sharing method includes the following steps:

step S21, the main veneer and/or the standby veneer receive the uplink BUM message;

step S22, determining the uplink BUM message as received by the main single board or the standby single board;

when the uplink BUM message is received by the main single board, executing step S231; when receiving the uplink BUM message for the standby single board, executing the steps S241-S242;

step S231, the main single board directly and normally forwards the received uplink BUM message;

step S241, the standby single board forbids the reporting ability of the uplink forwarding port to the BUM message, and normally forwards the received uplink BUM message;

step S242, the standby board forwards the received uplink BUM packet with the added tag to the main board, and reports to the client side through the uplink forwarding port of the main board.

In the above embodiment of the present application, when the main board and the standby board determine that the service packet is an uplink BUM packet, the standby board ensures that only one node in the main board and the standby board forwards the uplink BUM packet to the client side by prohibiting the reporting capability of the uplink forwarding port on the BUM packet, so as to prevent the uplink BUM packet from looping, and improve the forwarding capability of the main board and the standby board on the basis of ensuring the bandwidth utilization rate of the main board. It should be noted that, in this embodiment, the uplink BUM message capability of at least one of the first board and the second board is limited according to the setting rule, and for example, the reporting capability of the BUM message of the uplink forwarding port C2 of the standby board is prohibited, and the reporting capability of the BUM message of the uplink forwarding port C2 of the standby board is prohibited, so that when the service load of the uplink BUM message is shared and forwarded, the standby board does not need to distinguish the uplink BUM message received by the main board or the standby board, and the main board can normally forward the uplink BUM message.

Referring to fig. 17, taking a downstream BUM message scenario as an example, the load sharing method includes the following steps:

step S31, the main veneer and/or the standby veneer receive the downlink BUM message;

step S22, determining the downlink BUM message as received by the main veneer or the standby veneer;

when the main single board receives the downlink BUM message, executing the steps S331-S332; when receiving the downlink BUM message for the standby single board, executing steps S341 to S342;

step S331, when the main single board receives the downlink BUM message, the main single board directly and normally forwards the received downlink BUM message;

step S332, the main single board normally forwards the downlink BUM message which is forwarded by the main single board and carries the vlan tag at the ports except the uplink forwarding port C2;

step S341, the standby board normally forwards the received downlink BUM message at a port other than the board interconnection port L1, adds a vlan tag to the downlink BUM message, and forwards the downlink BUM message to the main board through the board interconnection port L1;

step S342, the standby board prohibits the reporting capability of the uplink forwarding port C2 on the BUM message, and discards the received downlink BUM message forwarded by the main board at the uplink forwarding port C2.

In the above embodiment of the present application, when the main board and the standby board determine that the service packet is a downlink BUM packet, the standby board ensures that the downlink BUM packet forwarded to the main board by the standby board cannot be forwarded and sent back to the client side through the uplink forwarding port of the main board by prohibiting the reporting capability of the uplink forwarding port to the BUM packet, so as to prevent the downlink BUM packet from looping, and improve the forwarding capability of the main board and the standby board on the basis of ensuring the bandwidth utilization rate of the main board. It should be noted that, in this embodiment, the uplink BUM message capability of at least one of the first board and the second board is limited according to the setting rule, for example, the reporting capability of the BUM message of the uplink forwarding port C2 of the standby board is prohibited, and the reporting capability of the BUM message of the uplink forwarding port C2 of the standby board is prohibited, so that when performing service load sharing forwarding, the standby board may forward the downlink BUM message to the main board only after adding a designated tag to the downlink BUM message, and the main board discards the downlink BUM message forwarded by the standby board at the uplink forwarding port C2 after identifying the downlink BUM message forwarded by the standby board.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. The scope of the invention is to be determined by the scope of the appended claims.

Claims

1. A method for load sharing, comprising:

the first single board and/or the second single board receives the service message; the first single board and the second single board are main and standby single boards;

and when the service message is determined to be a non-BUM message, carrying out load sharing and corresponding forwarding by the link where the first single board is located and the link where the second single board is located.

2. The method of claim 1, further comprising:

when the service message is determined to be a BUM message, limiting the uplink BUM message capability of at least one of the first single board and the second single board according to a set rule, and correspondingly forwarding the uplink BUM message via the first single board and the second single board after the uplink BUM message capability is limited.

3. The method according to claim 2, wherein when determining that the service packet is a BUM packet, restricting uplink BUM packet capability of at least one of the first board and the second board according to a set rule, and performing corresponding forwarding through the first board and the second board after the uplink BUM packet capability restriction includes:

the second single board forbids the function of the uplink BUM message;

4. The method of claim 3, wherein reporting the received uplink BUM packet from the first board to the client side comprises:

5. The method according to claim 4, wherein the reporting the received uplink BUM packet from the first board to the client side further comprises:

6. The method according to claim 2, wherein when determining that the service packet is a BUM packet, restricting uplink BUM packet capability of at least one of the first board and the second board according to a set rule, and performing corresponding forwarding through the first board and the second board after the uplink BUM packet capability restriction includes:

7. The method of claim 6, wherein the reporting, by the first board and the second board, the uplink BUM packet received by the home terminal to the client side, and discarding the received uplink forwarding BUM packet of the peer terminal comprises:

8. The method according to claim 2, wherein when determining that the service packet is a BUM packet, restricting uplink BUM packet capability of at least one of the first board and the second board according to a set rule, and performing corresponding forwarding through the first board and the second board after the uplink BUM packet capability restriction includes:

the second single board forbids the function of the uplink BUM message;

9. The method according to claim 2, wherein when determining that the service packet is a BUM packet, restricting uplink BUM packet capability of at least one of the first board and the second board according to a set rule, and performing corresponding forwarding through the first board and the second board after the uplink BUM packet capability restriction includes:

10. The method of claim 9, wherein the discarding the received downstream forwarding BUM packet of the peer at the upstream forwarding port comprises:

11. The method according to any one of claims 1 to 10, wherein before the first board and/or the second board receives the service packet, the method includes:

acquiring configuration information of an aggregation group;

and associating the uplink forwarding port of the first single board and the uplink forwarding port of the second single board with the aggregation group port of the client side to form a cross-subrack aggregation group according to the aggregation group configuration information, wherein the cross-subrack aggregation group is used for carrying out load sharing through the associated aggregation group ports.

12. The method according to any one of claims 1 to 10,

13. A load sharing system comprises a first single board and a second single board which are mutually a main single board and a standby single board, and is characterized by comprising:

the first single board and/or the second single board receive a service message;

14. The system of claim 13, further comprising:

15. The system according to claim 14, wherein when determining that the service packet is a BUM packet, restricting an uplink BUM packet capability of at least one of the first board and the second board according to a set rule, and performing corresponding forwarding through the first board and the second board after the uplink BUM packet capability restriction includes:

the second single board forbids the function of the uplink BUM message;

16. The system according to claim 14, wherein when determining that the service packet is a BUM packet, restricting an uplink BUM packet capability of at least one of the first board and the second board according to a set rule, and performing corresponding forwarding through the first board and the second board after the uplink BUM packet capability restriction includes:

the second single board forbids the function of the uplink BUM message;

17. The system of claim 15 or 16, further comprising:

18. The system according to claim 14, wherein when determining that the service packet is a BUM packet, restricting an uplink BUM packet capability of at least one of the first board and the second board according to a set rule, and performing corresponding forwarding through the first board and the second board after the uplink BUM packet capability restriction includes:

when the service message is determined to be an uplink BUM message, the first single board and the second single board report the uplink BUM message received by the local terminal to the client side, and discard the received uplink forwarding BUM message of the opposite terminal; and/or

19. The system of claim 13, comprising:

20. A single board is characterized in that the single board comprises a load sharing module and a message processing module,

the load sharing module is used for receiving a service message;

the message processing module is configured to, when determining that the service message is a non-BUM message, perform load sharing and corresponding forwarding on a link where the board is located and a link where another board that is a primary/standby board with the board is located.

21. The veneer according to claim 20, further comprising:

the message processing module is further configured to, when it is determined that the service message is a BUM message, limit an uplink BUM message capability of the board according to a set rule, and perform corresponding forwarding based on the board and the other board after the uplink BUM message capability limitation.

22. The veneer according to claim 20,

the message processing module is also used for forbidding the uplink BUM message function of the uplink forwarding port;

the message processing module is configured to, when determining that the service message is an uplink BUM message, add a specific tag to the received uplink BUM message and forward the uplink BUM message to the other board, and report the uplink BUM message to the client side at an uplink forwarding port by the other board; or, the message processing module is configured to, when determining that the service message is a downlink BUM message, add a specified label to the received downlink BUM message and then forward the received downlink BUM message, where the other board discards the downlink forwarding BUM message at the uplink forwarding port.

23. The veneer according to claim 22, further comprising:

the message processing module is further configured to start an uplink BUM message function of the uplink forwarding port when a link where the other board is located fails.

24. The veneer according to claim 20,

the message processing module is configured to, when determining that the service message is an uplink BUM message, report the uplink BUM message received by the home terminal to the client side, add an assigned tag to the received uplink BUM message, forward the uplink BUM message to the other board, and discard the received uplink forwarded BUM message of the other board; or the like, or, alternatively,

the message processing module is configured to forward the received downlink BUM message to a network side when it is determined that the service message is a downlink BUM message, forward the received downlink BUM message to the other board after adding an assigned tag to the received downlink BUM message, and discard the received downlink forwarding BUM message of the other board at an uplink forwarding port.

25. The veneer according to any one of claims 20 to 24,

the load sharing module is further configured to obtain aggregation group configuration information, and associate the uplink forwarding port with an aggregation group port on the client side according to the aggregation group configuration information to form a sub-shelf aggregation group.

26. A load sharing device comprising a processor and a memory for storing a computer program operable on the processor; wherein the content of the first and second substances,

the processor is configured to execute the load sharing method according to any one of claims 1 to 12 when running the computer program.

27. A storage medium having stored therein executable instructions which, when executed by a processor, implement the load sharing method of any one of claims 1 to 12.