Method, device, storage medium and electronic device for cross-device link network management

Abstract

The present application relates to the technical field of network management, and specifically provides a method, apparatus, storage medium and electronic device for cross-device link network management, the method may include: monitoring the uplink in the cross-device link aggregation system, at least updating the uplink table; in the case of failure of all link interfaces in the uplink table, interrupting the downlink so that the network side in the cross-device link aggregation system stops sending traffic to the forwarding device of the uplink; in the case of any link interface in the uplink table returning to normal, restoring the downlink. Some embodiments of the present application can realize the perception of faulty devices, adjust the traffic forwarding method, and improve system stability.

Description

Technical Field

[0001] The present application relates to the technical field of network management, and in particular to a method, apparatus, storage medium and electronic device for cross-device link network management. Background Art

[0002] The traditional M-LAG (Multichassis Link Aggregation Group) network includes multiple forwarding devices and the network side. Currently, when the M-LAG interface of a device in the M-LAG system fails, the network side cannot sense it. At this time, the network side will still send traffic to all M-LAG devices. Finally, the traffic sent by the failed device can only be sent to another device through the peer-link link in the M-LAG system, and finally the traffic is forwarded by another M-LAG device. The internal forwarding process is relatively cumbersome and has high requirements on the bandwidth of the peer-link link, which makes the system less stable.

[0003] Therefore, how to provide a technical solution for a method of cross-device link network management with higher stability has become a technical problem that needs to be solved urgently. Summary of the invention

[0004] The purpose of some embodiments of the present application is to provide a method, apparatus, storage medium and electronic device for cross-device link network management. Through the technical solutions of the embodiments of the present application, when a forwarding device fails, the network side can promptly perceive and adjust the traffic sending strategy, thereby improving the stability of the system and realizing intelligent management of the system.

[0005] In a first aspect, some embodiments of the present application provide a method for cross-device link network management, including: monitoring the uplink in a cross-device link aggregation system, and at least updating the uplink table; in the event that all link interfaces in the uplink table fail, interrupting the downlink so that the network side in the cross-device link aggregation system stops sending traffic to the forwarding device of the uplink; and restoring the downlink in the event that any link interface in the uplink table returns to normal.

[0006] Some embodiments of the present application monitor the uplink and update the uplink table, so that the downlink can be interrupted in time when all link interfaces in the uplink table fail; the downlink can be restored when any link interface is restored. In this way, when any forwarding device fails, the network side can perceive and adjust the traffic sending strategy in time, thereby improving the stability of the system and realizing intelligent management of the system.

[0007] In some embodiments, the monitoring of the uplink in the cross-device link aggregation system and at least updating the uplink table include: obtaining link interface information of a status change in the cross-device link aggregation system; and synchronously updating the uplink table and the downlink table through the link interface information.

[0008] Some embodiments of the present application update the uplink table and the downlink table by acquiring the changed link interface information, so that the network side can perceive the device status in time.

[0009] In some embodiments, the link interface information is deleted port information, wherein the uplink table and the downlink table are synchronously updated through the link interface information, including: searching the uplink table and the downlink table for the port object corresponding to the deleted port information; if the port object belongs to the downlink table and the state of the port object is controlled by the uplink table, restoring the state of the port object to the initial state; otherwise, deleting the port object.

[0010] Some embodiments of the present application can realize intelligent management of the network system by processing the port object according to different situations after finding the port object corresponding to the deleted port information.

[0011] In some embodiments, the link interface information is a target type port, wherein the interruption of the downlink includes: when the target port corresponding to the target type port belongs to the downlink table, but the state of the port object is not controlled by the uplink table, performing the following operations: confirming that the target port is the last faulty port in the uplink table, interrupting all ports in the downlink table, and recording the port state change time and number of changes in the downlink table.

[0012] Some embodiments of the present application can realize intelligent management of the network system by confirming whether the target type port is the last faulty port and recording relevant changes.

[0013] In some embodiments, the link interface information is a target type port, wherein restoring the downlink includes: confirming that the target port is any of the link interfaces in the uplink table that has returned to normal, then starting a timer; based on the timer, controlling all ports in the downlink table to return to a normal state, and recording the port state change time and number of changes in the downlink table.

[0014] Some embodiments of the present application can realize intelligent management of the network system by confirming whether the target port is any link interface that has returned to normal and recording relevant changes.

[0015] In some embodiments, the method further includes: when the target port corresponding to the target type port belongs to the downlink table and the state of the port object is controlled by the uplink table, restoring the target port to a normal state and recording the port state change time and number of changes in the downlink table.

[0016] Some embodiments of the present application can achieve intelligent management of the network system by performing corresponding processing and recording on the actual controlled status and status of the target port.

[0017] In some embodiments, before monitoring the uplink in the cross-device link aggregation system and at least updating the uplink table, the method further includes: creating the uplink table and the downlink table; wherein the uplink table and the downlink table support different interface types.

[0018] Some embodiments of the present application can timely learn the link status by creating an uplink table and a downlink table, so that the network side can perceive the interface status in time, realize intelligent management of the system and improve system stability.

[0019] In the second aspect, some embodiments of the present application provide an apparatus for cross-device link network management, including: a monitoring module, used to monitor the uplink in the cross-device link aggregation system, and at least update the uplink table; an interruption module, used to interrupt the downlink when all link interfaces in the uplink table fail, so that the network side in the cross-device link aggregation system stops sending traffic to the forwarding device of the uplink; a recovery module, used to restore the downlink when any link interface in the uplink table returns to normal.

[0020] In a third aspect, some embodiments of the present application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, can implement the method described in any embodiment of the first aspect.

[0021] In a fourth aspect, some embodiments of the present application provide an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor can implement a method as described in any embodiment of the first aspect when executing the program.

[0022] In a fifth aspect, some embodiments of the present application provide a computer program product, wherein the computer program product comprises a computer program, wherein the computer program, when executed by a processor, can implement the method described in any embodiment of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions of some embodiments of the present application, the drawings required for use in some embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 A schematic diagram of traditional M-LAG network interface fault processing provided for some embodiments of the present application;

[0025] Figure 2 M-LAG network intelligent management architecture diagram provided for some embodiments of the present application;

[0026] Figure 3 One of the flow charts of the method for cross-device link network management provided in some embodiments of the present application;

[0027] Figure 4 A schematic diagram of the internal implementation of interface linkage provided for some embodiments of the present application;

[0028] Figure 5 A second flow chart of a method for cross-device link network management provided for some embodiments of the present application;

[0029] Figure 6 A block diagram of the apparatus composition for cross-device link network management provided in some embodiments of the present application;

[0030] Figure 7 A schematic diagram of an electronic device is provided for some embodiments of the present application. DETAILED DESCRIPTION

[0031] The technical solutions in some embodiments of the present application will be described below in conjunction with the drawings in some embodiments of the present application.

[0032] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0033] In related technologies, such as Figure 1In the current M-LAG network interface fault processing diagram shown, when the M-LAG interface of Device B in the M-LAG system fails, the network side cannot perceive it, and the traffic will still be sent to Device B. At this time, the traffic sent to Device B will be sent to Device A through the peer-link link, and finally the traffic will be forwarded by Device A. It can be seen that the network side in the prior art cannot perceive the device failure in time, and at the same time puts forward higher requirements on the bandwidth of the peer-link link. When the forwarded traffic exceeds the carrying capacity of the peer-link link, it will have an adverse effect on the stability of the system.

[0034] In view of this, some embodiments of the present application provide a method for cross-device link network management, which allows the network side to perceive the device with M-LAG interface failure, and then the network side will directly forward the traffic to the normal M-LAG device, eliminating the relay process between devices in the M-LAG system. In this way, the entire M-LAG network management is more intelligent and the stability of the network is also improved.

[0035] The following is combined with Figure 2 The overall composition structure of the system for cross-device link network management provided by some embodiments of the present application is exemplified.

[0036] like Figure 2 As shown, some embodiments of the present application provide a system for cross-device link network management, and the cross-device link network management system M-LAG system may include: a network side IP network, forwarding devices Device A, Device B and Device C. The network side may send upstream and downstream traffic through the link so that the traffic is sent to the corresponding forwarding device and the network side.

[0037] Specifically, when the downstream M-LAG interface of the M-LAG device fails (for example, Figure 2 When port 1 in the faulty M-LAG fails, the upstream interface connected to the network side can synchronize its status, so that the network side device no longer sends traffic to the device, eliminating the relay process of the peer-link link and reducing its traffic forwarding pressure; at the same time, when the downstream M-LAG faulty interface recovers, the upstream interface also synchronizes its status, thereby restoring the communication between the network side and the M-LAG device. This upstream and downstream link binding process not only makes the entire network more intelligent, but also has the original stability of the peer-link link.

[0038] It should be understood that Figure 2 The number of forwarding devices can be set according to demand, and the embodiments of the present application are not limited to this.

[0039] The following is combined with Figure 2 and attached Figure 3 The implementation process of cross-device link network management provided by some embodiments of the present application is exemplified.

[0040] Please see attached Figure 3 , Figure 3 A flow chart of a method for cross-device link network management provided for some embodiments of the present application.

[0041] In some embodiments of the present application, in the process of intelligently managing the M-LAG system to improve network stability, it is first necessary to create a corresponding interface linkage group to achieve synchronization of interface status. Therefore, in some embodiments of the present application, before executing the method for cross-device link network management, it includes: creating an uplink table and a downlink table; wherein the uplink table and the downlink table support different interface types.

[0042] For example, in some embodiments of the present application, see the attached Figure 4 The provided interface linkage internal implementation diagram. Figure 4 The Debug module in can be used to print debugging information. Create an interface linkage group through the command-line interface (CLI) and the Simple Network Management Protocol (SNMP), and create uplink-list (as a specific example of an uplink table) and downlink-list (as a specific example of a downlink table) in the group. And bind the uplink-list and downlink-list in a linkage group. On the forwarding device Device B in the M-LAG system, the M-LAG interface is the uplink, which is an aggregated link, and the one connected to the network side is the downlink, which is generally a single Ethernet link. For example, Figure 2 As shown in the figure, port 2 on Device A and port 1 on Device B are both M-LAG interfaces. In this case, the faulty M-LAG interface refers to port 1 on Device B. The aggregated links refer to link 1 and link 2, which are aggregated into one link aggregation.

[0043] In addition, uplink-list supports three types of interfaces (for example, multilink, smtlink, eth, and agg), and downlink-list supports only one type of interface (for example, eth and agg). timer is a timer. The interface linkage group can monitor the interface status to notify the interface linkage group module (not shown in the figure) to update the link table and other operations according to relevant information to complete the synchronization of interface information, so that the network side can perceive the device status in time and realize intelligent management of the system.

[0044] The following is an example of the implementation process of cross-device link network management.

[0045] Specifically, the method for cross-device link network management may include:

[0046] S310: Monitor uplinks in the inter-device link aggregation system and at least update an uplink table.

[0047] For example, in some embodiments of the present application, the interface linkage group monitors the changes of the uplink aggregation member interface. The specific monitoring method is to register the port callback function, and the interface linkage group module will be notified immediately when the port status (up / down) changes. When the interface linkage group receives a callback message from the port, it means that the port has changed status, and its changed status will also be reflected in the message. Among them, there are two types of port changes: failure (down) and failure recovery (up). Specifically, the uplink is monitored, and when the M-LAG interface, that is, the aggregation link member interface, changes, the interface linkage module is notified, and the interface change information is synchronously updated to the corresponding uplink-list.

[0048] In some embodiments of the present application, S310 may include: acquiring link interface information of a changed state in the cross-device link aggregation system; and synchronously updating the uplink table and the downlink table through the link interface information.

[0049] For example, in some embodiments of the present application, the interface linkage module receives the above three types of port status change information (as a specific example of link interface information) sent by the interface type eth / LACP / SMLK / MUTLK, and can update the relevant ports in the uplink-list and downlink-list accordingly.

[0050] In some embodiments of the present application, the link interface information is deleted port information, wherein S310 may include: searching the uplink table and the downlink table for the port object corresponding to the deleted port information; if the port object belongs to the downlink table and the state of the port object is controlled by the uplink table, restoring the state of the port object to the initial state; otherwise, deleting the port object.

[0051] For example, in some embodiments of the present application, the corresponding port object to be deleted is found in the uplink-list and downlink-list, and deleted. However, if the port object belongs to the downlink-list and its state is controlled by the uplink-list, its original state is restored through errdisable (as a specific example of the initial state). Specifically, restoring the original state of the port object in the uplink-list refers to the state before it is added to the interface linkage group, which may be up or down.

[0052] S320: When all link interfaces in the uplink table fail, interrupt the downlink so that the network side in the inter-device link aggregation system stops sending traffic to the forwarding device of the uplink.

[0053] For example, in some embodiments of the present application, when all member interfaces (that is, link interfaces) aggregated in the uplink uplink-list fail, the interface linkage module automatically downs (that is, interrupts, or is called a failure) the downlink and records a log. At this time, the network side can sense the device Device B corresponding to the failed M-LAG interface, and the traffic will no longer be forwarded to Device B.

[0054] In some embodiments of the present application, the link interface information is a target type port, and S320 may include: when the target port corresponding to the target type port belongs to the downlink table, but the state of the port object is not controlled by the uplink table, perform the following operations: confirm that the target port is the last faulty port in the uplink table, interrupt all ports in the downlink table, and record the port state change time and number of changes in the downlink table.

[0055] For example, in some embodiments of the present application, when the target port belongs to the downlink-list and its state is not controlled by the uplink-list, the change time and update change number of the corresponding state of the target port can be recorded for the uplink-list. If the target port is the last shut down of the uplink-list (as a specific example of a faulty port), all ports of the downlink-list are shut down through errdisable, and the port state change time and update change number of the downlink-list are recorded.

[0056] S330: When any link interface in the uplink table recovers to normal, recover the downlink.

[0057] For example, in some embodiments of the present application, when only one interface member port (as a specific example of any link interface) in the aggregated link in the uplink uplink-list is restored, the downlink is restored and a log is recorded. Subsequently, the network side can perceive the recovery of the M-LAG device, and the traffic will be forwarded to device B again.

[0058] In some embodiments of the present application, the link interface information is a target type port, and S320 may include: confirming that the target port is any of the link interfaces in the uplink table that has returned to normal, then starting a timer; based on the timer, controlling all ports in the downlink table to return to a normal state, and recording the port state change time and number of changes in the downlink table.

[0059] For example, in some embodiments of the present application, when the target port belongs to the downlink-list and its status is not controlled by the uplink-list, when the first link interface (that is, any link interface) is restored, a timer is created and started to automatically restore the downlink status to up according to the delayed recovery time set by the user. Specifically, if the target port is the first undo shut of the uplink-list (that is, the first link interface), the corresponding timer is started by the recover-time (that is, the delayed recovery time) set by the user, thereby controlling the up of all ports in the downlink-list and recording the port status change time and update change times of the downlink-list.

[0060] The "shut" in the above text refers to "shudown", which indicates a simulated port failure or interruption, while "up" or "undoshutdown" means that the port is restored and can forward traffic, that is, a normal interface or port.

[0061] In some embodiments of the present application, the method for cross-device link network management may also include: when the target port corresponding to the target type port belongs to the downlink table and the state of the port object is controlled by the uplink table, restoring the target port to a normal state and recording the port state change time and number of changes in the downlink table.

[0062] For example, in some embodiments of the present application, for the target port belonging to the downlink-list, only the undo shut controlled by the uplink-list is processed, and the port is up through the errdisable module, and the change time and update change number of its corresponding status are recorded.

[0063] The following is combined with Figure 5 The specific process of cross-device link network management provided by some embodiments of the present application is exemplified.

[0064] Please see attached Figure 5 , Figure 5 A flow chart of a method for cross-device link network management provided for some embodiments of the present application.

[0065] The above process is explained below as an example.

[0066] S510: Create an interface linkage group, which includes an uplink table and a downlink table.

[0067] S520: The interface linkage group monitors the uplink in the inter-device link aggregation system, and synchronizes interface change information in the uplink to the uplink table.

[0068] S530: When the interface linkage group confirms that all link interfaces in the uplink table fail, the downlink is shut down and a log is recorded.

[0069] S540, when the interface linkage group confirms that any link interface in the uplink table has recovered to normal, the downlink is restored and a log is recorded.

[0070] It should be noted that the specific process of S510~S540 can refer to the method embodiment provided above, and in order to avoid repetition, the detailed description is appropriately omitted here.

[0071] Through some of the above embodiments of the present application, it can be known that the present application can allow the network side to perceive the device with M-LAG interface failure, save the relay process between devices in the M-LAG system, and directly forward the traffic to the normal M-LAG device. When the M-LAG faulty device is restored, the network side can also perceive it and re-forward the traffic to all M-LAG devices. Through the above embodiments, the entire M-LAG network management can be made more intelligent while also improving the stability of the network.

[0072] Please refer to Figure 6 , Figure 6 The block diagram of the composition of the apparatus for cross-device link network management provided by some embodiments of the present application is shown. It should be understood that the apparatus for cross-device link network management corresponds to the above method embodiment and can execute each step involved in the above method embodiment. The specific functions of the apparatus for cross-device link network management can be found in the description above. To avoid repetition, the detailed description is appropriately omitted here.

[0073] Figure 6 The device for cross-device link network management includes at least one software function module that can be stored in a memory in the form of software or firmware or solidified in the device for cross-device link network management. The device for cross-device link network management includes: a monitoring module 610, which is used to monitor the uplink in the cross-device link aggregation system and at least update the uplink table; an interruption module 620, which is used to interrupt the downlink when all link interfaces in the uplink table fail, so that the network side in the cross-device link aggregation system stops sending traffic to the forwarding device of the uplink; a recovery module 630, which is used to restore the downlink when any link interface in the uplink table returns to normal.

[0074] In some embodiments of the present application, the monitoring module 610 is used to obtain link interface information of a changed state in the inter-device link aggregation system; and synchronously update the uplink table and the downlink table through the link interface information.

[0075] In some embodiments of the present application, the link interface information is deleted port information, wherein the monitoring module 610 is used to search for the port object corresponding to the deleted port information from the uplink table and the downlink table; if the port object belongs to the downlink table and the state of the port object is controlled by the uplink table, the state of the port object is restored to the initial state; otherwise, the port object is deleted.

[0076] In some embodiments of the present application, the link interface information is a target type port, wherein the interrupt module 620 is used to perform the following operations when the target port corresponding to the target type port belongs to the downlink table but the state of the port object is not controlled by the uplink table: confirm that the target port is the last faulty port in the uplink table, then interrupt all ports in the downlink table, and record the port state change time and number of changes in the downlink table.

[0077] In some embodiments of the present application, the link interface information is a target type port, wherein the recovery module 630 is used to confirm that the target port is any of the link interfaces in the uplink table that has returned to normal, and then start a timer; based on the timer, control all ports in the downlink table to return to a normal state, and record the port state change time and number of changes in the downlink table.

[0078] In some embodiments of the present application, the interrupt module 620 is used to restore the target port to a normal state and record the port state change time and number of changes in the downlink table when the target port corresponding to the target type port belongs to the downlink table and the state of the port object is controlled by the uplink table.

[0079] In some embodiments of the present application, before the monitoring module 610, the apparatus for cross-device link network management also includes a creation module (not shown in the figure) for creating the uplink table and the downlink table; wherein the uplink table and the downlink table support different interface types.

[0080] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the device described above can refer to the corresponding process in the aforementioned method, and will not be described in detail here.

[0081] Some embodiments of the present application further provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, can implement the operations of the method corresponding to any of the above methods provided in the above embodiments.

[0082] Some embodiments of the present application further provide a computer program product, which includes a computer program, wherein when the computer program is executed by a processor, it can implement the operations corresponding to any of the above methods provided in the above embodiments.

[0083] like Figure 7As shown, some embodiments of the present application provide an electronic device 700, which includes: a memory 710, a processor 720, and a computer program stored in the memory 710 and executable on the processor 720, wherein the processor 720 can implement a method as described in any of the above embodiments when reading the program from the memory 710 through a bus 730 and executing the program.

[0084] Processor 720 can process digital signals and can include various computing structures, such as complex instruction set computer structure, reduced instruction set computer structure, or a structure that implements a combination of multiple instruction sets. In some examples, processor 720 can be a microprocessor.

[0085] The memory 710 may be used to store instructions executed by the processor 720 or data related to the execution of instructions. These instructions and / or data may include codes for implementing some or all functions of one or more modules described in the embodiments of the present application. The processor 720 of the disclosed embodiment may be used to execute instructions in the memory 710 to implement the method shown above. The memory 710 includes a dynamic random access memory, a static random access memory, a flash memory, an optical memory, or other memory known to those skilled in the art.

[0086] The above description is only an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0087] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0088] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

Claims

1. A method for cross-device link network management, characterized in that: include: Monitor uplinks in the cross-device link aggregation system and at least update an uplink table; In the event that all link interfaces in the uplink table fail, interrupting the downlink so that the network side in the inter-device link aggregation system stops sending traffic to the forwarding device of the uplink; If any link interface in the uplink table returns to normal, restore the downlink; The monitoring of the uplink in the cross-device link aggregation system and at least updating the uplink table includes: obtaining link interface information of a changed state in the cross-device link aggregation system; synchronously updating the uplink table and the downlink table through the link interface information; The link interface information is deleted port information, wherein the synchronous updating of the uplink table and the downlink table through the link interface information comprises: searching the uplink table and the downlink table for a port object corresponding to the deleted port information; if the port object belongs to the downlink table and the state of the port object is controlled by the uplink table, restoring the state of the port object to an initial state; otherwise, deleting the port object; The link interface information is a target type port, wherein the interruption of the downlink includes: when the target port corresponding to the target type port belongs to the downlink table, but the state of the port object is not controlled by the uplink table, performing the following operations: confirming that the target port is the last faulty port in the uplink table, interrupting all ports in the downlink table, and recording the port state change time and change number in the downlink table; The link interface information is a target type port, wherein the restoring the downlink includes: confirming that the target port is any link interface in the uplink table that has returned to normal, then starting a timer; based on the timer, controlling all ports in the downlink table to return to a normal state, and recording the port state change time and change number in the downlink table; Before monitoring the uplink in the cross-device link aggregation system and at least updating the uplink table, the method further includes: creating the uplink table and the downlink table; wherein the uplink table and the downlink table support different interface types.

2. The method according to claim 1, characterized in that The method further comprises: When the target port corresponding to the target type port belongs to the downlink table and the state of the port object is controlled by the uplink table, the target port is restored to a normal state, and the port state change time and number of changes in the downlink table are recorded.

3. A device for cross-device link network management, characterized in that: The device is used to perform the method according to claim 1, comprising: A monitoring module, used to monitor the uplink in the cross-device link aggregation system, and at least update the uplink table; An interruption module, configured to interrupt a downlink when all link interfaces in the uplink table fail, so that the network side in the inter-device link aggregation system stops sending traffic to the forwarding device of the uplink; The recovery module is used to recover the downlink when any link interface in the uplink table recovers to normal.

4. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program executes the method according to any one of claims 1 to 2 when executed by a processor.

5. An electronic device, characterized in that: The method comprises a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the computer program executes the method according to any one of claims 1 to 2 when being run by the processor.

Images