Edge aggregation port convergence method, device and medium of MLAG device group

Through the RST BPDU message format and negotiation mechanism of the MLAG device group, the problem of slow spanning tree state convergence when the MLAG device group is connected to the edge device is solved, and the rapid convergence of the aggregate port and the rapid recovery of the network are achieved.

CN116708194BActive Publication Date: 2025-08-22INSPUR NETWORK TECH (SHANDONG) CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310855395.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-07-12
Publication Date
2025-08-22
Estimated Expiration
2043-07-12

AI Technical Summary

Technical Problem

When the existing MLAG device group is connected to edge devices, the spanning tree state of the aggregate port converges slowly, causing network congestion and affecting user experience.

Method used

Through the RST BPDU message format in the MLAG device group, port status selection and negotiation reply message reception judgment are performed, message status information is determined, and link status transition is performed based on flag status information to achieve rapid convergence of spanning tree state.

Benefits of technology

The rapid spanning tree convergence of the aggregation port is realized, reducing the flow outage time, avoiding network congestion, and ensuring rapid network recovery.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116708194B_ABST
    Figure CN116708194B_ABST
Patent Text Reader

Abstract

The present invention discloses a method, device, and medium for edge aggregation port convergence in an MLAG device group, belonging to the field of MLAG network topology technology. The method is used to solve the technical problem that when some MLAG device groups are connected to edge devices, the spanning tree state of the aggregation port converges slowly, the outage time is long, and it is easy to cause network congestion, which greatly reduces the user experience. The method includes: using the RST BPDU message format in the MLAG device group, selecting the port state of the aggregation port connected to the edge device to obtain a designated port; determining the reception of the negotiation reply message of the designated port to determine message state information; if the message state information indicates that the message state information has not been received, determining the true or false setting of the flag bit in the designated port to obtain flag bit state information; and according to the flag bit state information, performing a corresponding link state transition on the designated port to achieve rapid convergence of the spanning tree state in the aggregation port.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of MLAG network topology, and in particular to a method, device, and medium for converging edge aggregation ports of an MLAG device group. Background Art

[0002] In current MLAG network topologies, MLAG device groups are primarily used to increase network redundancy, improve device link reliability, and facilitate load balancing. When access layer devices use MLAG groups, they are often connected to edge devices. To prevent loops in the network topology, spanning tree functionality is typically enabled on these devices. However, edge devices, such as servers or standard computers, lack spanning tree functionality. In such cases, it is necessary to configure edge ports on the member interfaces of the connected MLAG device group's aggregation ports to exclude them from spanning tree calculations, thus shortening the convergence time of the entire network topology.

[0003] Existing servers may not have spanning tree functionality, which can cause the spanning tree status of the multiple aggregate ports connected to them to be unstable, slowing convergence across the MLAG network and significantly impacting services. Using command lines to configure edge ports for multiple aggregate ports simultaneously is cumbersome and can easily cause network congestion, further impacting the spanning tree status of the MLAG network topology. Summary of the Invention

[0004] The embodiments of the present application provide an edge aggregation port convergence method, device, and medium for an MLAG device group, which are used to solve the following technical problem: when an existing MLAG device group is connected to an edge device, the spanning tree state of the aggregation port converges slowly, the outage time is long, and it is easy to cause network congestion, which greatly reduces the user experience.

[0005] The embodiments of this application adopt the following technical solutions:

[0006] On the one hand, an embodiment of the present application provides an edge aggregation port convergence method for an MLAG device group, including: selecting the port status of the aggregation port connected to the edge device through the RST BPDU message format in the MLAG device group to obtain a designated port; performing a reception judgment on the negotiation reply message of the designated port to determine message status information; wherein, the message status information includes: received message status information and unreceived message status information; if the message status information is unreceived message status information, performing a true or false setting judgment on the flag bit in the designated port to obtain flag bit status information; according to the flag bit status information, performing a corresponding link state transition on the designated port to achieve rapid convergence of the spanning tree state in the aggregation port.

[0007] In the embodiments of the present application, the aggregation ports connected to edge devices via the MLAG device group no longer need to be configured with edge port commands, allowing the aggregation ports to perform rapid spanning tree convergence. Even if the associated edge devices have spanning tree enabled, they can still participate in normal spanning tree calculations, eliminating network congestion caused by configuring the edge ports to only maintain a forwarding state. This ensures that the aggregation ports have both normal spanning tree calculation functionality and rapid convergence capabilities, ensuring rapid network recovery and reducing outage time.

[0008] In a feasible implementation, the port status of the aggregation port connected to the edge device is selected through the RST BPDU message format in the MLAG device group to obtain a designated port, which specifically includes: opening and activating the RST BPDU message format in the MLAG device group; wherein the RST BPDU message format is a protocol interaction message in the P / A negotiation mechanism; through the full-duplex link in the P / A negotiation mechanism, the edge device and the aggregation port in the MLAG device group are role-elected to determine the designated port based on the MLAG device group and the root port based on the edge device; the designated port is selected for port status to obtain the designated port in the Discarding state.

[0009] In a feasible implementation, a reception determination of a negotiation reply message is performed on the designated port to determine message status information, specifically including: performing a P / A negotiation process on the designated port in the Discarding state; setting the Proposal bit and the Agrement bit in the RST BPDU message format on the designated port after the P / A negotiation process, and synchronously setting the corresponding connected root port to select the Discarding state for all non-edge ports; sending the P / A negotiation reply message to the designated port after the setting process; and determining the reception of the P / A negotiation reply message on the designated port; and determining the message status information based on the reception status of the P / A negotiation reply message.

[0010] In a feasible implementation, after determining the message status information based on the reception status of the P / A negotiation reply message, the method further includes: if the message status information is received message status information, switching the discarding state of the designated port and the discarding state of the root port to a forwarding state; and performing rapid spanning tree convergence based on the P / A negotiation reply message on the designated port and the root port, both in the forwarding state, to achieve flow recovery in the MLAG network.

[0011] In a feasible implementation manner, if the message status information is non-received message status information, then before performing a true or false setting judgment on the flag bit in the designated port and obtaining the flag bit status information, the method further includes: based on the RST BPDU message format in the MLAG device group, identifying the BPDU structure field of the BPDU bridge nesting protocol in the root port; adding a flag bit to the BPDU structure field; wherein the BPDU bridge nesting protocol is used for a protocol loop response between the designated port and the root port.

[0012] In a feasible implementation manner, if the message status information is non-received message status information, the flag bit in the designated port is judged to be true or false to obtain the flag bit status information, specifically including: if the message status information is non-received message status information, based on the BPDU structure field, a reception judgment of the BPDU bridge nesting protocol between the designated port and the root port is performed; if the BPDU bridge nesting protocol is not received, the flag bit in the designated port is set to a False false bit state; if the BPDU bridge nesting protocol has been received, the flag bit in the designated port is set to a True true bit state; wherein, the flag bit status information includes: the False false bit state and the True true bit state.

[0013] In a feasible implementation, based on the flag status information, the designated port is subjected to a corresponding link status transition, specifically including: when the flag bit in the designated port is in the True state, performing P / A negotiation processing on the STP BPDU message format between the designated port and the root port; and determining the link status of the designated port to be the Forwarding Delay forwarding delay state; wherein the STP BPDU message format is used to determine the corresponding network topology structure by transmitting the BPDU bridge nesting protocol between the edge device and the MLAG device group; when the flag bit in the designated port is in the False state, transitioning the link status of the designated port to the Forwarding sending state; performing rapid spanning tree convergence based on the P / A negotiation reply message on the designated port in the Forwarding sending state and the Forwarding Delay forwarding delay state and its corresponding root port, so as to achieve flow recovery of the MLAG network.

[0014] In a feasible implementation manner, the Flags attribute bits in the RST BPDU message format include: TCA bit, Agreement bit, Forwarding bit, Learning bit, Port Role bit, Proposal bit, and TC bit.

[0015] In a second aspect, an embodiment of the present application also provides an edge aggregation port convergence device for an MLAG device group, the device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor so that the at least one processor can execute an edge aggregation port convergence method for an MLAG device group described in any of the above embodiments.

[0016] In a third aspect, an embodiment of the present application further provides a non-volatile computer storage medium, characterized in that the storage medium is a non-volatile computer-readable storage medium, and the non-volatile computer-readable storage medium stores at least one program, each of which includes instructions. When the instructions are executed by a terminal, the terminal executes an edge aggregation port convergence method of an MLAG device group described in any of the above embodiments.

[0017] This application provides a method, device, and medium for edge aggregation port convergence in an MLAG device group. This method allows aggregation ports connected to edge devices via the MLAG device group to rapidly converge to a spanning tree, eliminating the need to configure edge port commands. Even if associated edge devices have spanning tree enabled, they can still participate in normal spanning tree calculations, eliminating network congestion caused by configuring edge ports to only maintain a forwarding state. This ensures that the aggregation ports have both normal spanning tree calculation functionality and rapid convergence, ensuring rapid network recovery and minimizing outages. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments described in the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0019] Figure 1 A flow chart of a method for converging edge aggregation ports of an MLAG device group provided in an embodiment of the present application;

[0020] Figure 2 A schematic diagram of a network topology of an MLAG device group provided in an embodiment of the present application;

[0021] Figure 3 A schematic diagram of a fast convergence state process of an edge port provided in an embodiment of the present application;

[0022] Figure 4A schematic diagram of the structure of an edge aggregation port convergence device of an MLAG device group provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to enable those skilled in the art to better understand the technical solutions in this application, the following will clearly and completely describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0024] The embodiment of the present application provides a method for converging edge aggregation ports of an MLAG device group, such as Figure 1 As shown, the edge aggregation port convergence method of the MLAG device group specifically includes steps S101-S104:

[0025] It should be noted that Figure 2 A schematic diagram of a MLAG device group network topology provided in an embodiment of the present application is shown in FIG. Figure 2 As shown in the figure, Switch1 and Switch2 are both MLAG switching devices at the core layer and can be horizontally virtualized into a single device for redundant backup. Switch3 and Switch4 are both MLAG device groups at the access layer, connecting to downstream server devices (edge ​​devices). They use aggregated ports for load balancing and redundant backup. Port1 and Port4 are both ordinary physical ports, aggregated into aggregate port Agg1, and Port2 and Port3 are aggregated into aggregate port Agg2. Except for Server1 and Server2, all other devices in the network must have the spanning tree function enabled to prevent network loops. Because some server devices may not have the spanning tree function, the spanning tree status of Port1, Port2, Port3, and Port4 connected to them cannot quickly stabilize, slowing the convergence of the entire network and significantly impacting services.

[0026] S101 : Using the RST BPDU message format in the MLAG device group, select the state of the aggregation port connected to the edge device to obtain a designated port.

[0027] Specifically, the RST BPDU message format is enabled and activated in the MLAG device group. The RST BPDU message format is a protocol exchange message in the P / A negotiation mechanism.

[0028] Furthermore, through the full-duplex link in the P / A negotiation mechanism, the edge device and the aggregation port in the MLAG device group are elected for roles, and then the designated port based on the MLAG device group and the root port based on the edge device are determined.

[0029] Furthermore, the designated port is selected for a port state, and a designated port in a Discarding state is obtained.

[0030] In one embodiment, Figure 3 A schematic diagram of a fast convergence state flow of an edge port provided in an embodiment of the present application is shown as follows: Figure 3 As shown in the figure, switches (MLAG devices) with RSTP enabled exchange messages using the RST BPDU format. Compared to STP, which uses two types of messages: Configuration BPDU and TCN BPDU, RSTP uses only the RST BPDU. STP's FLAG tag only uses the TCA and TC bits, while RSTP has redefined the remaining six bits. RSTP's rapid convergence stems from its use of the P / A negotiation mechanism in point-to-point, full-duplex links. This allows designated ports and root ports to enter the forwarding state through a "negotiation process." The P / A negotiation mechanism presupposes three key requirements: a point-to-point, full-duplex link; a designated port in the Discarding state; and the election of the local port as the designated port and the election of the connected peer port as the root port.

[0031] S102: Determine the reception of the negotiation reply message on the designated port and determine message status information, wherein the message status information includes: received message status information and unreceived message status information.

[0032] Specifically, a designated port in the Discarding state undergoes a P / A negotiation. The Proposal and Agreement bits in the RST BPDU format are then set for the designated port after the P / A negotiation. The corresponding root port is also set simultaneously to select the Discarding state for all non-edge ports. The Flags attribute bits in the RST BPDU format include the TCA bit, Agreement bit, Forwarding bit, Learning bit, Port Role bit, Proposal bit, and TC bit.

[0033] Furthermore, the P / A negotiation reply message is sent to the designated port after the setting process, and the designated port is judged to have received the P / A negotiation reply message.

[0034] Furthermore, based on the reception status of the P / A negotiation reply message, message status information is determined.

[0035] If the packet status information indicates received, the designated port and the root port are both switched from the Discarding state to the Forwarding state. The designated port and the root port, both in the Forwarding state, are then used to perform rapid spanning tree convergence based on the P / A negotiation reply message, thereby restoring traffic on the MLAG network.

[0036] In one embodiment, Figure 3 As shown in the figure, when a designated port is in the Discarding state, it sends an RST packet with both the Proposal and Agreement bits in the Flags attribute set to 1. When the connected peer port, which has been elected as the root port, receives this packet, it synchronizes the bits and sets all non-edge ports to the Discarding state. Edge ports and alternate ports are already set to the Agreement bit by default because they do not cause additional loops. After synchronization, the root port on the edge device sends an RST BPDU packet format with the Proposal bit in the Flags attribute set to 0 and the Agreement bit set to 1. The root port then transitions to the Forwarding state. When the designated port in the MLAG group receives this RST BPDU packet format, it identifies it as a response to the Proposal bit and assumes that the peer device is no longer looping. It then quickly transitions its own state to the Forwarding state, fully restoring the link.

[0037] S103: If the message status information is message status information not received, a true or false setting judgment is performed on the flag bit in the designated port to obtain flag bit status information.

[0038] Specifically, based on the RST BPDU message format in the MLAG device group, the BPDU structure field of the BPDU bridge nesting protocol on the root port is identified. A flag bit is added to the BPDU structure field. The BPDU bridge nesting protocol is used to respond to protocol loopbacks between the designated port and the root port.

[0039] Furthermore, if the message status information indicates that the message was not received, a determination regarding the BPDU bridge protocol is performed between the designated port and the root port based on the BPDU structure fields. If the BPDU bridge protocol was not received, the flag bit in the designated port is set to a false state. If the BPDU bridge protocol was received, the flag bit in the designated port is set to a true state. The flag bit status information includes a false state and a true state.

[0040] In one embodiment, Figure 2 As shown in the figure, since the server side (edge ​​device side) does not have the spanning tree function, it will not reply to this P / A negotiation message, causing the P / A negotiation process of Port1, Port2, Port3, and Port4 to fail and become a normal STP process, so it is necessary to wait for two Forwarding Delay (forwarding delay) times. Figure 3 As shown in the figure, in order to shorten the waiting time after the P / A negotiation message fails, a flag bit P can be added to the structure field of the BPDU bridge nesting protocol received by the designated port, such as Port1. If the BPDU bridge nesting protocol is not received, the flag bit P is set to False. On the contrary, if the port can receive the BPDU bridge nesting protocol, it means that it is not an edge port and needs to perform P / A negotiation normally, then the flag bit P is set to True.

[0041] S104 : According to the flag status information, the designated port is subjected to a corresponding link status transition to achieve rapid convergence of the spanning tree status in the aggregation port.

[0042] Specifically, when the flag bit on the designated port is True, a P / A negotiation regarding the STP BPDU message format is performed between the designated port and the root port. The link state of the designated port is then set to ForwardingDelay. The STP BPDU message format is used to determine the corresponding network topology through the BPDU bridge nesting protocol transmitted between the edge device and the MLAG device group. When the flag bit on the designated port is False, the link state of the designated port is changed to Forwarding.

[0043] Furthermore, the designated ports in the Forwarding state and the Forwarding Delay state and their corresponding root ports are subjected to rapid spanning tree convergence based on the P / A negotiation reply message, thereby realizing flow recovery of the MLAG network.

[0044] In one embodiment, Figure 3 as well as Figure 2 As shown in the figure, when the P flag is False and the port is a designated port, it may indicate a P / A negotiation failure. In this case, the port state is directly changed from Discarding to Forwarding, reducing the waiting time after the P / A negotiation failure. If the P flag is True, the normal process is carried out, and the designated port and the root port undergo P / A negotiation using the STP BPDU format. The designated port's link state is also set to two Forwarding Delay states. Ultimately, the MLAG network quickly restores traffic flow and has fast convergence capabilities, ensuring rapid network recovery and reducing traffic interruption time.

[0045] In addition, the embodiment of the present application also provides an edge aggregation port convergence device of an MLAG device group, such as Figure 4 As shown, the edge aggregation port convergence device 400 of the MLAG device group specifically includes:

[0046] At least one processor 401. And a memory 402 in communication with the at least one processor 401. The memory 402 stores instructions that can be executed by the at least one processor 401, so that the at least one processor 401 can execute:

[0047] The RST BPDU message format in the MLAG device group is used to select the port status of the aggregation port connected to the edge device to obtain the designated port.

[0048] Performing a reception determination of a negotiation reply message on a designated port to determine message status information; wherein the message status information includes: received message status information and unreceived message status information;

[0049] If the message status information is the message status information that has not been received, a true or false setting judgment is performed on the flag bit in the designated port to obtain the flag bit status information;

[0050] According to the flag status information, the link status of the designated port is changed accordingly to achieve rapid convergence of the spanning tree status in the aggregation port.

[0051] This application provides a method, device, and medium for edge aggregation port convergence in an MLAG device group. This method allows aggregation ports connected to edge devices via the MLAG device group to rapidly converge to a spanning tree, eliminating the need to configure edge port commands. Even if associated edge devices have spanning tree enabled, they can still participate in normal spanning tree calculations, eliminating network congestion caused by configuring edge ports to only maintain a forwarding state. This ensures that the aggregation ports have both normal spanning tree calculation functionality and rapid convergence, ensuring rapid network recovery and minimizing outages.

[0052] The various embodiments in this application are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the device and non-volatile computer storage medium embodiments are generally similar to the method embodiments, so their descriptions are relatively simple. For relevant parts, refer to the descriptions of the method embodiments.

[0053] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects to their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0054] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0055] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0056] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0057] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0058] The foregoing description describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0059] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the embodiments of the present application may have various modifications and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included within the scope of the claims of the present application.

Claims

1. A method for converging edge aggregation ports of an MLAG device group, characterized in that: The method comprises: The RST BPDU message format in the MLAG device group is used to select the port status of the aggregation port connected to the edge device to obtain the designated port. Performing a reception determination of the negotiation reply message on the designated port to determine message status information; wherein the message status information includes: received message status information and unreceived message status information; If the message status information is message status information that has not been received, performing a true or false setting judgment on the flag bit in the designated port to obtain flag bit status information; According to the flag status information, the designated port is subjected to a corresponding link status transition to achieve rapid convergence of the spanning tree status in the aggregation port.

2. The method for edge aggregation port convergence of an MLAG device group according to claim 1, characterized in that: The RST BPDU message format in the MLAG device group is used to select the port status of the aggregation port connected to the edge device to obtain the designated port. Specifically, the following is performed: Enable and activate the RST BPDU message format in the MLAG device group; wherein the RST BPDU message format is a protocol interaction message in the P / A negotiation mechanism; Performing role election on the edge device and the aggregation ports in the MLAG device group through a full-duplex link in the P / A negotiation mechanism to determine a designated port based on the MLAG device group and a root port based on the edge device; The designated port is selected in a port state to obtain the designated port in a Discarding state.

3. The method for edge aggregation port convergence of an MLAG device group according to claim 1, characterized in that: Determining the reception of the negotiation reply message on the designated port and determining message status information specifically includes: Perform a P / A negotiation on the designated port in the Discarding state; After the P / A negotiation process, the Proposal bit and the Agrement bit in the RST BPDU message format are set for the designated port, and the corresponding root port is set synchronously to select the Discarding state for all non-edge ports. Sending the P / A negotiation reply message to the designated port after the setting process; and performing a reception determination of the P / A negotiation reply message on the designated port; The message status information is determined based on the reception status of the P / A negotiation reply message.

4. The edge aggregation port convergence method of an MLAG device group according to claim 3, characterized in that: After determining the message status information based on the reception status of the P / A negotiation reply message, the method further includes: If the message status information is received message status information, the Discarding state of the designated port and the Discarding state of the root port are switched to the Forwarding state; The designated ports and the root port, both in the forwarding sending state, are subjected to rapid spanning tree convergence based on the P / A negotiation reply message, so as to realize flow recovery of the MLAG network.

5. The method for edge aggregation port convergence of an MLAG device group according to claim 1, characterized in that: If the message status information is message status information that has not been received, performing a true or false setting judgment on a flag bit in the designated port to obtain the flag bit status information, the method further includes: Based on the RST BPDU message format in the MLAG device group, identifying the BPDU structure field of the BPDU bridge nesting protocol in the root port; A flag bit is added to the BPDU structure field; wherein the BPDU bridge nesting protocol is used for protocol loop response between the designated port and the root port.

6. The method for edge aggregation port convergence of an MLAG device group according to claim 5, characterized in that: If the message status information is message status information not received, performing a true or false setting judgment on the flag bit in the designated port to obtain flag bit status information, specifically including: If the message status information is message status information not received, performing a reception judgment on a BPDU bridge nesting protocol between the designated port and the root port based on the BPDU structure field; If the BPDU bridge nesting protocol is not received, the flag bit in the designated port is set to a False state; If the BPDU bridge nesting protocol has been received, the flag bit in the designated port is set to True; The flag bit status information includes: the False bit status and the True bit status.

7. The method for edge aggregation port convergence of an MLAG device group according to claim 1, characterized in that: According to the flag status information, the designated port performs a corresponding link status change, specifically including: When the flag bit in the designated port is in the True state, a P / A negotiation process regarding the STP BPDU message format is performed between the designated port and the root port; and the link state of the designated port is determined to be the ForwardingDelay forwarding delay state; wherein the STP BPDU message format is used to determine the corresponding network topology structure by transmitting the BPDU bridge nesting protocol between the edge device and the MLAG device group; When the flag bit in the designated port is in a False state, changing the link state of the designated port to a Forwarding state; The designated ports in the Forwarding state and the Forwarding Delay state and their corresponding root ports are subjected to rapid spanning tree convergence based on the P / A negotiation reply message, so as to achieve flow recovery of the MLAG network.

8. The method for edge aggregation port convergence of an MLAG device group according to claim 3, characterized in that: The Flags attribute bits in the RST BPDU message format include: TCA bit, Agreement bit, Forwarding bit, Learning bit, Port Role bit, Proposal bit and TC bit.

9. An edge aggregation port convergence device of an MLAG device group, characterized in that: The device comprises: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, so that the at least one processor can execute the edge aggregation port convergence method of an MLAG device group according to any one of claims 1 to 8.

10. A non-volatile computer storage medium, characterized in that The storage medium is a non-volatile computer-readable storage medium, storing at least one program. Each of the programs includes instructions. When executed by a terminal, the instructions enable the terminal to execute the edge aggregation port convergence method of an MLAG device group according to any one of claims 1 to 8.

Citation Information

Patent Citations

  • Network convergence method, network bridges and system

    CN101534211A

  • Ring rapid spanning tree protocol

    US20070008964A1