LAG linkage protection control method and device

Abstract

The invention relates to the technical field of communication, and discloses an LAG linkage protection control method and device. The method comprises the following steps: when a target member of a home terminal triggers a target event, determining a first target state corresponding to each member of the home terminal from a preset protection state transition table; each member of the home terminal is controlled to be in a corresponding first target state, and the activation state of each member of the home terminal is controlled based on the first target state; and determining a second target state from the protection state transition table according to the request signal of the first target state, controlling each member of the opposite terminal to be in the second target state, and controlling the activation state of each member of the opposite terminal based on the second target state. According to the invention, the technical problems in the prior art that when the actual available bandwidth of the LAG does not meet the use requirement, linkage with upper layer protection deployed at different sites cannot be realized, and the complexity of engineering operation and maintenance is high are solved.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a method and apparatus for LAG linkage protection control. Background Technology

[0002] Currently, LAG (Link Aggregation Group), which follows the international standard 802.1ax, supports link aggregation at different rates. However, in load-sharing mode, if one link in an LAG fails, link congestion can occur. For example, if LAG1 and LAG2 are directly connected and aggregated at 50G, 25G, and 25G, and the customer requires LAG1 and LAG2 to handle 60G of traffic, congestion and packet loss will occur if a single 50G link fails and LAG1 and LAG2 continue to carry the traffic. The 802.1ax standard does not address this scenario.

[0003] In existing technologies, to address the above scenarios, LAG protection typically pre-configures two thresholds: a minimum number of active members and a minimum active bandwidth. Based on the actual active member information of the LAG protection, it is determined whether the LAG meets the bandwidth requirements. If not, the LAG reports an alarm to the upper-layer protection at this station, triggering a rapid switchover of the upper-layer protection. However, this solution has the following two problems:

[0004] 1. Reference Figure 1 , Figure 1 This is a schematic diagram illustrating the deployment of LAG protection at a transit point in existing technology. For example... Figure 1 As shown, when LAG protection is deployed at a cross-site, the upper-layer protection deployed at the source and destination sites cannot obtain alarms reported by LAG across sites. The upper-layer protection cannot switch over quickly and can only rely on control plane protocol convergence, resulting in long packet loss times. That is, this solution is only suitable for scenarios where LAG and upper-layer protection are deployed at the same site, and cannot be linked with upper-layer protection deployed at different sites.

[0005] 2. Reference Figure 2 , Figure 2 This is a schematic diagram illustrating the deployment of LAG protection at the source and destination stations in existing technologies. (Example:) Figure 2 As shown, when LAG protection is deployed at the source and destination stations, and the source and destination stations are configured with BFD (Bidirectional Forwarding Detection) to quickly detect link failures, when LAG does not meet the bandwidth usage requirements but still has active members, BFD message transmission and reception are normal, maintaining normal operation. If a primary / backup path switchover occurs at this time, it will be inconsistent with the existing behavior of triggering protection switchover when the primary path BFD message fails, causing inconvenience to engineering maintenance and increasing the complexity of engineering operation and maintenance. Summary of the Invention

[0006] This invention provides a LAG linkage protection control method and device, which can solve the technical problems in the prior art where the 802.1ax standard supports link aggregation at different rates, but does not describe the scenario where LAG does not meet the minimum activation threshold requirement and needs to be linked with upper-layer protection actions. This leads to the inability to link with upper-layer protection deployed at different sites when the actual available bandwidth of LAG does not meet the usage requirements, as well as the high complexity of engineering operation and maintenance.

[0007] To achieve the above objectives, the present invention provides the following technical solution:

[0008] A method for LAG (Label Aggregator) linkage protection control, wherein members of the LAG communicate via the RFC5880 standard protocol, the method comprising:

[0009] When a target member on this end triggers a target event due to a link failure or by receiving a control command, the first target state corresponding to each member on this end is determined from a preset protection state transition table. The protection state transition table is used to describe the transition relationship between event requests and states. Each state has a corresponding request signal. The target event is an event in which the local end does not meet the minimum activation threshold requirement, an event in which the local end recovers to meet the minimum activation threshold requirement, or an event in which the local end receives a blocking inactivation request signal sent by the peer's LAG.

[0010] Control each member on this end to be in the corresponding first target state and control the activation state of each member on this end based on the first target state;

[0011] Based on the request signal of the first target state, the second target state is determined from the protection state transition table, and each member of the peer end is controlled to be in the second target state. The activation state of each member of the peer end is controlled based on the second target state to realize LAG linkage protection.

[0012] Based on the same inventive concept, this invention also provides an LAG linkage protection control device, wherein members in the LAG communicate via the RFC5880 standard protocol, and the device includes:

[0013] The state determination module is configured to determine the first target state corresponding to each member of the local end from a preset protection state transition table when the target member of the local end triggers a target event due to a link failure or by receiving a control command. The protection state transition table is used to describe the transition relationship between event requests and states. Each state has a corresponding request signal. The target event is either the local end does not meet the minimum activation threshold requirement or the local end recovers to meet the minimum activation threshold requirement.

[0014] The status control module is configured to control each member of the local end to be in the corresponding first target state and control the activation state of each member of the local end based on the first target state; determine the second target state from the protection state transition table according to the request signal of the first target state, and control each member of the peer end to be in the second target state and control the activation state of each member of the peer end based on the second target state, so as to realize LAG linkage protection.

[0015] The technical effects and advantages of this invention are as follows:

[0016] When a target member on this end is deactivated due to a link failure or receiving a control command, causing the local LAG to fail to meet the minimum activation threshold, the system automatically activates all other members on the normal link, deactivating all other members and rendering the entire LAG protection group inactive. Consequently, the LAG group becomes unusable. Then, BFD messages forwarded through the LAG port on the primary path cannot be sent or received normally, indicating a BFD failure on the primary path. This triggers the upper-layer protection to switch to the normal backup path, enabling normal switching of LAG protection and normal switching of the upper-layer protection.

[0017] This invention solves the technical problem in the prior art where, because the 802.1ax standard supports link aggregation at different rates but does not describe the scenario where the LAG does not meet the minimum activation threshold requirement and needs to be linked to the upper-layer protection action, the LAG deployed at the transit site cannot be linked to the upper-layer protection group of the source site for rapid switching when the LAG does not meet the minimum activation threshold requirement, resulting in long packet loss time. This invention improves the performance of service protection switching.

[0018] This solves the technical problem in the existing technology where the BFD state is inconsistent with the business path state when the LAG is deployed at the source and destination stations and does not meet the minimum activation threshold requirement, thus improving the efficiency of engineering operation and maintenance.

[0019] It fills the gap in the 802.1ax standard for LAG minimum activation threshold scenarios and solves the problem that the LAG minimum activation threshold scenario cannot be linked and switched with the upper layer protection when the 802.1ax standard protocol adds support for LAG link aggregation of different rates.

[0020] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures pointed out in the description, claims and drawings. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a schematic diagram of LAG protection deployment at a transit station in the existing technology;

[0023] Figure 2 This is a schematic diagram of LAG protection deployment at the source and destination stations in existing technologies;

[0024] Figure 3 This is a schematic diagram illustrating the principle of deactivating the normal LAG member action mechanism of the present invention;

[0025] Figure 4 A flowchart of the method provided in the embodiments of the present invention;

[0026] Figure 5 A schematic diagram illustrating the BFD protocol message format defined in the RFC 5880 standard;

[0027] Figure 6 This is the LAG protection state machine state transition table corresponding to the local request event under the load mode of this invention;

[0028] Figure 7 This is the LAG protection state machine state transition table corresponding to the peer request event under the load mode of this invention;

[0029] Figure 8 This is a schematic diagram illustrating the effect of deploying the LAG protection of the present invention in a scenario where the upper-level protection is linked due to an SF fault at a transit station.

[0030] Figure 9a This is a schematic diagram of the state transition of the 50G member of LAG1 in the scenario where the LAG at the station is linked to the upper layer protection due to the SF failure.

[0031] Figure 9b This is a schematic diagram of the state transition of the 25G members of LAG1 in the scenario where the LAG at the station is linked to the upper layer protection due to the SF failure.

[0032] Figure 10 This is a schematic diagram of the state transition of each member of LAG1 in the scenario where the LAG recovers from the SF fault and is in the WTR state and is linked to the upper layer protection according to the present invention.

[0033] Figure 11 This is a schematic diagram illustrating the final effect of the present invention in the scenario where the LAG recovers from an SF fault and is in WTR state, triggering the upper-level protection.

[0034] Figure 12a This is a schematic diagram of the state transition of the 50G member of LAG1 in the scenario of LAG recovering from SF fault and WTR timeout in the present invention.

[0035] Figure 12b This is a schematic diagram of the state transition of the 25G members of LAG1 in the scenario of LAG recovering from SF fault and WTR timeout in the present invention.

[0036] Figure 13 This is a schematic diagram illustrating the final effect of the linkage with upper-layer protection scenarios when the LAG recovery of the transit station meets the minimum activation threshold requirement according to the present invention.

[0037] Figure 14 A schematic diagram illustrating the final effect of the scenario where the LAG at the inlet station is linked to the upper-level protection due to an SD fault.

[0038] Figure 15a A schematic diagram of the state transition of the 50G member of LAG1 in the scenario where the LAG at the inception of the station is linked to the upper layer protection due to the SD fault.

[0039] Figure 15b A schematic diagram of the state transition of 25G members of LAG1 in the scenario where LAG at a station is linked to the upper layer protection due to SD failure.

[0040] Figure 16a A schematic diagram of the state transition of the 50G member of LAG2 in the scenario where the LAG at the inception of the station is linked to the upper layer protection due to the SD fault.

[0041] Figure 16b A schematic diagram of the state transition of the 25G members of LAG2 in the scenario where the LAG at the inception of the station is linked to the upper layer protection due to the SD fault.

[0042] Figure 17 A schematic diagram of the state transition of each member of LAG2 in the scenario where LAG recovers from SD fault and is in WTR state to link with upper layer protection.

[0043] Figure 18a A schematic diagram of the state transition of the 50G member of LAG2 in the scenario of LAG recovering from SD fault and WTR timeout triggering upper layer protection.

[0044] Figure 18b A schematic diagram of the state transition of the 25G members of LAG2 in the scenario of LAG recovering from SD fault and WTR timeout triggering upper layer protection.

[0045] Figure 19 This is a schematic diagram illustrating the final effect of the scenario where the LAG at the inception of the invention is locked and inactive due to the issuance of a control command, which is then linked to the upper-level protection.

[0046] Figure 20aA schematic diagram of the state transition of 50G members of LAG1 in a scenario where the LAG is locked and inactive due to the issuance of a control command to link with the upper layer protection.

[0047] Figure 20b A schematic diagram of the state transition of 25G members of LAG1 in a scenario where the LAG is locked and inactive due to the issuance of a control command to link with the upper layer protection.

[0048] Figure 21 This is a functional module diagram of an embodiment of the LAG linkage protection control device of the present invention. Detailed Implementation

[0049] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0050] To address the shortcomings of existing technologies, this invention discloses a LAG linkage protection control method, referring to... Figure 3 , Figure 3 This is a schematic diagram illustrating the principle of deactivating the normal LAG member action mechanism of the present invention. Figure 3 As shown. The primary path of the upper-layer protection has an LAG port, configured with BFD for fast detection of primary link faults. The LAG protection group has three member links with different rates: 50G, 25G, and 25G, defined as follows:

[0051] (A) Minimum activation threshold = Minimum number of active members || Minimum activation bandwidth;

[0052] (B) When (the number of available members on this end < the minimum number of active members) || (the total available bandwidth on this end < the minimum active bandwidth), it is considered that LAG does not meet the minimum active threshold requirement;

[0053] (C) When (the number of available members on this end >= the minimum number of active members) && (the total available bandwidth on this end >= the minimum active bandwidth), it is considered that LAG meets the minimum activation threshold requirement;

[0054] (D) When a LAG member is inactive, it is considered that the LAG member does not carry communication services; when a LAG member is active, it is considered that the LAG member carries communication services.

[0055] Reference Figure 4 , Figure 4 A flowchart of the method provided in the embodiments of the present invention, such as Figure 4 As shown, the method includes:

[0056] Step S10: When a target member of this end triggers a target event due to a link failure or receiving a control command, the first target state corresponding to each member of this end is determined from the preset protection state transition table. The protection state transition table is used to describe the transition relationship between event requests and states. Each state has a corresponding request signal. The target event is an event in which this end does not meet the minimum activation threshold requirement, an event in which this end recovers to meet the minimum activation threshold requirement, or an event in which a blocking inactivation request signal is received from the LAG of the other end.

[0057] In this embodiment, members of the LAG communicate via the RFC 5880 standard protocol. It should be understood that control commands defined by international standards for protection technologies such as G8031 and G8331, such as locking the primary and forced switching, are not applicable to the LAG. This is because the LAG operates in two modes: non-load mode and load mode. In load mode, all members of the LAG have the same role, i.e., there is no primary or backup role. Therefore, descriptions such as locking the primary cannot be applied, and a completely new design is required. Therefore, this embodiment, in order to provide a protection method for the LAG based on 802.1ax supporting minimum activation threshold linkage function in load mode, will design a protection state machine for the LAG supporting minimum activation threshold linkage function in load mode.

[0058] First, the APS request signal and its priority are designed. Specifically, the APS request signal is designed using the 5-bit Diag code in the BFD (Bidirectional Forwarding Detection) protocol message format defined in the RFC5880 standard, resulting in the APS request signal and its priority design table shown in Table 1.

[0059] Table 1

[0060]

[0061]

[0062] The format of Diag diagnostic codes is shown in Table 2.

[0063] Table 2

[0064]

[0065] As shown in Table 1, the request signals can be divided into 10 types according to their sequence numbers. Each request signal in Table 1 contains 4 bits of specific content. The lowest bit (-1) indicates member activation, and 0 indicates member inactivation. The reason is determined by the higher bits. For example, in request signal 1110, the lowest bit is 0, indicating member inactivation, while the higher 3 bits are 111, indicating lock inactivation. It should be noted that 0000 should be avoided in the steady-state, no-request state for easier distinction. The priority of each row of request signals in Table 1 is sorted from high to low. For example, the first row corresponding to APS request signals (request signal 1111) has the highest priority, while the last row corresponding to APS request signals (request signal 0001) has the lowest priority. It should be noted that Table 1 is only a presentation of an example, and the fields in Table 1 can be adjusted according to actual needs.

[0066] As shown in Table 2, the highest bit 3 is used to distinguish whether it is used for APS. In this application, it is always set to 1, which means that bits 4-7 are APS request signals; bits 4-7 are used to fill APS request signals.

[0067] This application adds a Block Inactive request signal 1100 to notify the peer LAG and local LAG members that they are in a Block Inactive state. For example, if a Block Inactive request signal is sent, the 5-bit Diag diagnostic code is 11110, i.e., the APS request signal is 11110; if a Block Inactive request signal is sent, the 5-bit Diag diagnostic code is 11100, i.e., the APS request signal is 11100.

[0068] Reference Figure 5 , Figure 5 A diagram illustrating the BFD protocol message format defined in the RFC 5880 standard. (Example) Figure 5 As shown, the RFC 5880 standard defines the use of values ​​0-8, with values ​​9-31 as reserved values. Preferably, in this application, the 5-bit Diag code uses values ​​16-31 from the reserved values ​​to complete the LAG protection APS request signal design. It should be noted that there are no restrictions on the type of BFD here.

[0069] This application uses the reserved value of the diagnostic code in the BFD control message to transmit the APS request signal, referencing the RFC 5880 standard. The transmission cycle can be as fast as 3*3ms. Compared with the existing technology that uses the reserved field of the LACP (Link Aggregation Control Protocol) message to transmit the APS request signal, referencing the 802.3ad standard, the APS request signal transmission mechanism designed in this application is faster and more efficient. In scenarios where LAG protection requires dual-end linkage switching (such as when the link experiences signal degradation failure), it greatly improves the switching performance.

[0070] Secondly, the State field of the LAG protection state machine under load mode is designed based on the request signal to obtain the State design table as shown in Table 3; it can be understood that each state has a corresponding request signal.

[0071] Table 3 State Design Table

[0072]

[0073] Table 3 introduces two new states, G and J. State G corresponds to Block Inactive, meaning it is not inactive and is abbreviated as Blo Inactive. Its communication service carrying state is Member Inactive, indicating that the LAG member is inactive and not carrying communication services. State J corresponds to Remote Block Inactive, meaning it is not inactive and is abbreviated as RBlo Inactive. Its communication service carrying state is Member Inactive. It should be noted that Table 3 is only a presentation of an example, and the fields in Table 3 can be adjusted according to actual needs.

[0074] Next, the event of the LAG protection state machine under load mode is designed; in this embodiment, the LAG protection state machine event design is preferably divided into two categories: (1) Local Request: event request that occurs in the local LAG; (2) Received far-end request: event request that occurs in the far-end LAG, so as to obtain the local request event table as shown in Table 4 and the far-end request event table as shown in Table 5.

[0075] Table 4 Local Request Event Table

[0076]

[0077] Table 5 Peer Request Event Table

[0078]

[0079] It is understandable that the protection state machine events stored in Tables 4 and 5 represent currently occurring events, and the interpretation principles of each event are similar. The newly added column h in Table 4, corresponding to "Recover form Block," indicates that the local LAG has experienced an event that recovers from not meeting the minimum activation threshold to meeting the minimum activation threshold, and will then jump to the State A state with no request. The newly added column i in Table 4, "Block Inactive," indicates that the local LAG has experienced an event that does not meet the minimum activation threshold, and will then jump to the State G state of "Block Inactive." The newly added column t in Table 5 indicates that the local LAG has received a blocking inactive event request from the remote LAG, and will then jump to the State J state of "Remote Block Inactive." It should be noted that Tables 4 and 5 are only a presentation of an example, and the fields in Tables 4 and 5 can be adjusted according to actual needs.

[0080] Finally, based on the design of LAG request signals and their priorities, the State field of the LAG protection state machine under load mode, and the Event field, the design of the LAG protection state machine state transition table is implemented to obtain, as follows: Figure 6 The LAG protection state machine state transition table corresponding to the local request event shown in the load mode is as follows: Figure 7 The table shown is the LAG protection state machine state transition table corresponding to the peer request event under the load mode; it should be noted that... Figure 6 and Figure 7 In this context, "N / A" indicates that the event will not occur or will be ignored even if it does; "O" indicates that the request is overridden by an existing condition because it has the same or lower priority than an existing request. It should be understood that... Figure 6 and Figure 7 The corresponding LAG protection state machine state transition table constitutes the protection state transition table of this embodiment. That is, the protection state transition table includes the LAG protection state machine state transition table corresponding to the local request event under load mode and the LAG protection state machine state transition table corresponding to the peer request event under load mode. It describes the transition relationship between the event request and the state under load mode.

[0081] In this embodiment, after completing the design of the protection state transition table under load mode, the state switching of members between the local and remote ends can be realized based on the protection state transition table to achieve LAG protection switching control. It should be noted that the target member on the local end refers to the member that has experienced a target event such as signal degradation event, signal failure event, lock activation control command event, lock inactivation control command event, waiting recovery timeout event, manual activation event, or manual inactivation event. It also refers to the member on the local end that has experienced an event that does not meet the minimum activation threshold requirement, an event that recovers from not meeting the minimum activation threshold requirement to meeting the minimum activation threshold requirement, or an event that receives a blocking inactivation request signal sent by the remote LAG.

[0082] Specifically, when a target member on this end triggers a target event due to a link failure or by receiving a control command, the first target state for controlling the state of each member on this end is determined from the state transition table of the LAG protection state machine corresponding to the local request event under load mode based on the target event.

[0083] For example, suppose the target member on this end is currently in state A (NR) and the target event is an event that occurs where the minimum activation threshold requirement is not met, but the minimum activation threshold requirement is met (i.e., the Recover formBlock corresponding to event h). Then, through... Figure 6 It can be determined that when the target member on this end experiences an h event, the priority of the Recover form Block request signal corresponding to the h event is higher than that of the No Request request signal. Therefore, in response to the h event, each member on this end needs to switch from state A to state A, that is, the target member on this end maintains state A unchanged. Therefore, the first target state is state A.

[0084] For example, suppose the target member on this end is currently in state A (NR) and the target event has occurred (i.e., an event that does not meet the minimum activation threshold requirement has occurred, i.e., the BlockInactive corresponding to event i), then by... Figure 6 It can be determined that when the target member on this end experiences an i event, the Block Inactive request signal corresponding to the i event has a higher priority than the No Request request signal. Therefore, in response to the i event, each member on this end needs to switch from state A to state G, that is, the state of the target member on this end needs to be migrated from A to G. Therefore, the first target state is state G.

[0085] For example, suppose the target member on this end is currently in state A (NR) and the target event is the occurrence of a blocking inactive request signal received from the peer's LAG (i.e., the Block Inactive event corresponding to event t), then through... Figure 6It can be determined that when the target member on this side experiences event t, the Block Inactive request signal corresponding to event t has a higher priority than the NoRequest request signal. Therefore, in response to event t, each member on this side needs to switch from state A to state J, that is, the state of each member on this side needs to be migrated from A to J. Therefore, the first target state is state J.

[0086] Step S20: Control each member of the local terminal to be in the corresponding first target state and control the activation state of each member of the local terminal based on the first target state;

[0087] In this embodiment, after determining the first target state corresponding to each member of the local end, the state transition and activation state update of each member of the local end can be controlled based on the first target state. For example, if the first target state is state B, and the service carrying state of state B is Member Active, that is, in the state of carrying communication services, while controlling the state of the target member of the local end to transition from state A to state B, the activation state of each member of the local end needs to be updated to the active state so that the target member of the local end can carry communication services.

[0088] For example, if the first target state is G, and the service carrying state of G is Member Inactive, meaning it is in a state that does not carry communication services, then while controlling the state of the target member on this end to migrate from state A to state G, the active state of each member on this end needs to be updated to inactive so that each member on this end does not carry communication services.

[0089] Step S30: Determine the second target state from the protection state transition table according to the request signal of the first target state, and control each member of the peer end to be in the second target state and control the activation state of each member of the peer end based on the second target state, so as to realize LAG linkage protection.

[0090] In this embodiment, while performing state transitions and activation state control on each member of the local end according to the first target state, a request signal corresponding to the first target state is also sent to the peer end communicating with the local end, so as to obtain information from the peer end through the request signal. Figure 7 In the load mode shown, the second target state is determined in the state transition table of the LAG protection state machine corresponding to the peer request event. The state transition and activation state update of each member of the peer are controlled based on the second target state.

[0091] For example, suppose the first target state is E and the peer target member is currently in state A. Since the request signal corresponding to state E is 1000, the request signal received by the peer target member changes from 0001 in state A to 1000. Furthermore, request signal 1000 has a higher priority than request signal 0001; therefore, the response is to request signal 1000. Through request signal 1000, one can obtain... Figure 7 The system determines that a target member at the other end has experienced an event q, and it needs to switch from state A to state K (i.e., inactive state without request). Therefore, the second target state is state K. Since the service-bearing state of state K is MemberInactive (i.e., not carrying communication services), while controlling the transition of the target member's state from state A to state K, the active state of the target member needs to be updated to inactive. This ensures that the target member does not carry communication services, thus automatically fulfilling the requirement that, under the 802.1ax standard protocol, when the transit LAG does not meet the minimum activation threshold, the transit LAG has no member carrying communication services, causing the primary path BFD to fail and triggering upper-layer protection switching.

[0092] In this embodiment, when a target member on the local end triggers a target event due to a link failure or by receiving a control command, the first target state corresponding to each member on the local end is determined from a preset protection state transition table. The protection state transition table describes the transition relationship between event requests and states. Each state has a corresponding request signal. The target event is either an event where the local end does not meet the minimum activation threshold requirement or an event where the local end recovers to meet the minimum activation threshold requirement. The local end is controlled to be in the corresponding first target state, and the activation state of each member on the local end is controlled based on the first target state. The second target state is determined from the protection state transition table according to the request signal of the first target state, and the peer end is controlled to be in the second target state, and the activation state of each member on the peer end is controlled based on the second target state, so as to realize LAG linkage protection. In this embodiment, when the target member (member 1) on the local end is deactivated due to link failure or receiving a control command, causing the local LAG to fail to meet the minimum activation threshold requirement, the other members (members 2 and 3) with normal links are automatically deactivated, making members 2 and 3 inactive. This results in the entire LAG protection group having no active members, rendering the LAG group unusable. Then, BFD messages forwarded through the LAG port on the primary path cannot be sent or received normally, indicating a BFD failure on the primary path. This triggers upper-layer protection switching to the normal backup path, achieving normal LAG protection switching and enabling normal switching of upper-layer protection. This fills the gap in the 802.1ax standard regarding the minimum activation threshold scenario for LAG and solves the problem of new features in the 802.1ax standard protocol. This invention addresses the issue of LAG (Link Aggregator) failure to coordinate with upper-layer protection in scenarios where the minimum activation threshold is not met, which arises when LAG links are aggregated at different rates. It resolves the technical problem in existing technologies where, although the 802.1ax standard supports link aggregation at different rates, it does not describe scenarios where LAGs do not meet the minimum activation threshold and require coordination with upper-layer protection. This leads to situations where LAGs deployed at intermediate stations cannot quickly coordinate with the source station's upper-layer protection group for switching when the LAG does not meet the minimum activation threshold, resulting in prolonged packet loss. This improves service protection switching performance. Furthermore, it resolves the technical issue in existing technologies where, when LAGs are deployed at source and destination stations and do not meet the minimum activation threshold, the BFD (Browser Decision Function) state is inconsistent with the service path state, thus improving engineering and maintenance efficiency.

[0093] In the face of complex LAG protection failure scenarios, on the one hand, it is necessary to ensure that the normal members of the link can be accurately activated so that the action mechanism for activating normal LAG members can operate normally; on the other hand, it is necessary to ensure that the normal members of the link can be accurately restored so that the existing LAG functions are not affected.

[0094] Furthermore, in one embodiment, when the target member of this end triggers an event that the minimum activation threshold requirement is not met due to a signal failure, the target member of this end is controlled to be in a signal failure state, the other members of this end are controlled to be in a blocked and inactive state, and the activation state of each member of this end is inactive.

[0095] The target member on the other end is controlled to be in a signal failure state, and the other members on the other end are controlled to be in a blocked and inactive state, and the activation state of each member on the other end is inactive.

[0096] In this embodiment, when a communication link in LAG aggregation experiences a complete signal interruption (e.g., the fiber is severed, the optical module at the port is faulty) or a failure in the BFD or LACP protocol, resulting in a port failure, BFD failure, or LACP protocol failure, the communication equipment will consider that the LAG member to have experienced an SF (Signal Fail) failure. An SF failure is detectable by both ends of the fiber optic connection.

[0097] Reference Figure 8 , Figure 8 This is a schematic diagram illustrating the effect of deploying the LAG protection of this invention in a scenario where an SF fault at a substation triggers the upper-level protection. Figure 8 As shown, NE1-NE2-NE3-NE4 is the primary path, and NE1-NE4 is the backup path. NE2 and NE3 are interconnected via optical fibers with speeds of 50G, 25G, and 25G. NE2 deploys LAG1, and NE3 deploys LAG2, each containing 3 members. Communication services are non-equivalently load-sharing among these 3 members. The minimum number of active members configured for LAG1 and LAG2 is 2, and the minimum active bandwidth is 60G.

[0098] Initially, when the 50G link was severed due to fiber optic cable being dug up during construction, communication failures occurred in the 50G link port, BFD protocol messages, and LACP protocol messages. LAG1 and LAG2 both detected the SF failure in the 50G member and migrated it to the SF state, while the 25G member remained in the No Request state.

[0099] Then, LAG1 and LAG2 calculate that the number of available members on their local end is 2, and the total available bandwidth on their local end is 25 + 25 = 50G. Comparing this, the total available bandwidth on their local end is less than the minimum activation bandwidth, failing to meet the minimum activation threshold requirement, thus triggering the "Block Inactive" event (i-event). For the 50G member experiencing an SF failure, the state transition of LAG1 and LAG2 is as follows: Figure 9aAs shown, event c (Signal Fail) has a higher priority than event i (Block Inactive, the local end does not meet the minimum activation threshold requirement). LAG1 and LAG2's 50G members do not respond to event i and remain in the Signal Fail (SF) state. For the 25G members with normal links, the state transitions of LAG1 and LAG2 are as follows: Figure 9b As shown, the i event (Block Inactive) has a higher priority than the No Request event. Therefore, in response to the i event, the 25G members of LAG1 and LAG2 transition from the A state (No Request) to the G state (Block Inactive).

[0100] Ultimately, the 50G members of LAG1 and LAG2 are inactive due to the detection of an SF fault, and the 25G members are automatically deactivated. LAG1 and LAG2 become unusable as a whole. BFD1 and BFD2 messages forwarded by LAG1 and LAG2 are blocked, resulting in BFD1 and BFD2 protocol message communication failures. This triggers upper-layer protection switching to the backup path. At this point, the goal is achieved in a signal failure (SF fault) scenario where the passing LAG does not meet the minimum activation threshold, causing a primary path BFD protocol message communication failure and triggering upper-layer protection switching.

[0101] Furthermore, in one embodiment, when the local target member triggers an event that the local end does not meet the minimum activation threshold requirement due to signal failure recovery, the local target member is controlled to be in a waiting recovery state, the other local members are controlled to be in a blocked inactive state, and the activation state of each local member is inactive.

[0102] The target member on the control end is in a waiting recovery state, the other members on the control end are in a blocked and inactive state, and the activation state of each member on this end is inactive.

[0103] In this embodiment, based on the signal failure of the target member (50G member) on the local end, the 50G link fiber is repaired, and the 50G link port, BFD protocol messages, and LACP protocol messages are all normal. Both LAG1 and LAG2 detect the recovery of the 50G member signal failure. In order to prevent signal jitter and other situations, the 50G members of LAG1 and LAG2 will first enter the WTR (Wait To Restore) state (the industry practice is to wait for 5 minutes). At this time, the 50G member is still unavailable and does not carry traffic, while the 25G member is still in the G state (Block Inactive).

[0104] LAG1 and LAG2 calculate that the number of available members on their local end is 2, and the total available bandwidth on their local end is 25 + 25 = 50G. This does not meet the minimum activation threshold requirement, triggering the "Local End Does Not Meet Minimum Activation Threshold Requirement" event (i-event, Block Inactive). At this time, the state transition of LAG1 and LAG2 is as follows: Figure 10 As shown: For 50G members, when in WTR (Wait To Restore) state, when the i event (Block Inactive event) is triggered, the 50G member does not respond to the i event and maintains the WTR state; for 25G links, when in G state (Block Inactive) state, when the i event is triggered, the 25G member maintains the G state (Block Inactive).

[0105] The effect achieved by 50G members during WTR is as follows Figure 11 As shown, the 50G members of LAG1 and LAG2 are in WTR (Wait To Restore) state, meaning they are inactive. The 25G member remains inactive, and LAG1 and LAG2 as a whole remain unavailable. BFD1 and BFD2 protocol messages forwarded by LAG1 and LAG2 remain blocked. In the event of a BFD1 or BFD2 failure, the upper-layer protection maintains the switchover to the backup path state. At this point, the signal failure (SF) recovery is achieved, and the system is in a WTR scenario. When the transit LAG does not meet the minimum activation threshold, the primary path BFD protocol message communication failure is maintained, and the upper-layer protection is linked to maintain the switchover.

[0106] Furthermore, in one embodiment, when a target member on the local end triggers an event indicating that the local end meets the minimum activation threshold requirement due to being in a waiting recovery state for more than a preset time, the local end members are controlled to be in a no-request state, and the activation state of each member on the local end is active.

[0107] The control ensures that all members on the other end are in a no-request state, while all members on the local end are in an active state.

[0108] In this embodiment, when the 50G members of LAG1 and LAG2 are in a waiting-for-recovery state for more than a preset time, the 50G members transition to the No Request state. LAG1 and LAG2 calculate that the number of available members on their local end is 3, and the total available bandwidth on their local end is 50 + 25 + 25 = 100G, which meets the minimum activation threshold requirement, triggering the local end recovery event (h event, Recover from Block). For the 50G members of LAG1 and LAG2 that have already ended WTR, the state transition is as follows: Figure 12aAs shown, it does not respond to the h event and maintains the no-request state (state A, No Request); for the 25G member whose link is always normal, the state transitions of LAG1 and LAG2 are as follows. Figure 12b As shown, when responding to the h event (Recover from Block), the state transitions from G (BlockInactive) to A (No Request).

[0109] Final effect as Figure 13 As shown, after the SF fault is recovered, the 50G members of LAG1 and LAG2 are reactivated, the 25G link is restored and activated normally, LAG1 and LAG2 become available again, and BFD1 and BFD2 protocol messages forwarded by LAG1 and LAG2 are sent and received normally, which triggers the upper-layer protection to start the back-switching. At this time, the goal of ensuring normal BFD protocol message communication on the primary path and triggering the upper-layer protection back-switching is achieved when the LAG at the station meets the minimum activation threshold requirement under the scenario of SF fault recovery and WTR timeout.

[0110] Furthermore, in one embodiment, when the target member of this end triggers an event that the local end does not meet the minimum activation threshold requirement due to signal degradation failure, the target member of this end is controlled to be in a signal degradation state, the other members of this end are controlled to be in a blocked and inactive state, and the activation state of each member of this end is an inactive state.

[0111] Control the target member on the other end to be in an inactive state without requests, control the other members on the other end to be in a remote blocked inactive state, and set the activation state of each member on the other end to be an inactive state.

[0112] In this embodiment, when a communication link in LAG aggregation experiences a significant decline in signal quality but has not yet completely broken down, the communication equipment continuously monitors key indicators such as bit error rate and optical power for abnormalities. If an abnormality is detected, the LAG member is considered to have experienced a signal degrade (SD) fault. An SD fault may only be detectable by the equipment on the fiber optic connection side.

[0113] The final effect achieved in this embodiment is as follows: Figure 14 As shown. NE1-NE2-NE3-NE4 is the primary path, and NE1-NE4 is the backup path; NE2 and NE3 are interconnected via optical fibers with speeds of 50G, 25G, and 25G. NE2 deploys LAG1, and NE3 deploys LAG2, each containing 3 members. Communication services are non-equivalently load-sharing among these 3 members; the minimum number of active members for configuring LAG1 and LAG2 is 2, and the minimum active bandwidth is 60G.

[0114] Initially, when LAG1 detects an abnormal degradation in the received optical power of the 50G member, it assumes that a signal degrade (SD) fault has occurred and moves it to the signal degraded state (E state, signal Degrade), while the 25G member remains in the initial state (A state, No Request).

[0115] Then, LAG1 calculates that the number of available members on its local end is 2, and the total available bandwidth on its local end is 25 + 25 = 50G, which does not meet the minimum activation threshold requirement, triggering the "Block Inactive" event (i event). For the 50G member of LAG1 in the signal degraded state (E state), the state transition is as follows: Figure 15a As shown, the e-event (signal degrade) has a higher priority than the i-event (block inactive). The 50G member of LAG1 does not respond to the i-event; it maintains the E-state (Signal Degrade) and sends an APS request signal (1000) for signal degrade to the peer. For the 25G member of LAG1 in the no-request state (A-state, No Request), the state transition is as follows... Figure 15b As shown, the i event (Block Inactive) has a higher priority than the No Request event. In response to the i event, the 25G member of LAG1 transitions from the A state (No Request) to the G state (Block Inactive) and sends an APS request signal (1100) for Block Inactive to the peer.

[0116] After LAG2's 50G member receives the APS request signal (1000) indicating signal degradation from the peer, its state transition is as follows: Figure 16a As shown, in response to event q, member 50G of LAG2 transitions from state A to state K (No Request Inactive); after member 25G of LAG2 receives the Block Inactive APS request signal (1100) sent by the peer, its state transition is as follows. Figure 16b As shown, in response to event t, the 25G member of LAG2 is transitioned from state A to state J (Remote Block Inactive).

[0117] Ultimately, the 50G member of LAG1 is inactive due to the detected SD fault, and the 25G member of LAG1 is automatically deactivated; the 50G and 25G members of LAG2 are inactive due to the peer's APS request signal. LAG1 and LAG2 become unavailable, and the BFD1 and BFD2 protocol messages forwarded by LAG1 and LAG2 are blocked, triggering upper-layer protection switching to the backup path. At this point, the goal is achieved: in the SD fault scenario, the transit LAG does not meet the minimum activation threshold requirement, causing a communication failure in the primary path's BFD protocol messages and triggering upper-layer protection switching.

[0118] Furthermore, in one embodiment, when the local target member triggers an event that the local end does not meet the minimum activation threshold requirement due to signal degradation failure recovery, the local target member is controlled to be in a waiting recovery state, and the other local members are in a blocked inactive state.

[0119] Maintain the peer target member in an inactive state without requests, and keep the peer target member's active state in an inactive state;

[0120] Maintain the remaining members on the other end in a remote blocked inactive state, and keep the active state of the remaining members on the other end in an inactive state.

[0121] In this embodiment, based on the signal degradation fault of the target member (50G member) on the local end, LAG1 senses that the optical power of the 50G member's received signal has returned to normal. To prevent optical signal jitter, the 50G member first migrates to the F state (Wait To Restore, WTR state). The industry practice is to wait for 5 minutes. The 25G member is still in the G state (Block Inactive state).

[0122] LAG1 calculates that the number of available members on the local end is 2, and the total available bandwidth on the local end is 25 + 25 = 50G, which does not meet the minimum activation threshold requirement. Therefore, the event "Local end does not meet minimum activation threshold requirement" (i event, Block Inactive) is triggered again. For the 50G member in the F state (Wait To Restore, WTR state), the i event is not responded to, the F state (Wait To Restore, WTR state) is maintained, and an APS request signal of "Wait To Restore" is sent to the peer end. For the 25G member in the G state (Block Inactive state), the G state (Block Inactive state) is maintained, and an APS request signal of "Block Inactive" (1100) is sent to the peer end.

[0123] After receiving the Wait To Restore (APS) request signal from the peer, the 50G member of LAG2 does not respond, and the state transition is as follows: Figure 17 As shown, the K state (No Request Inactive) is maintained; after receiving the Block Inactive APS request signal from the peer, the 25G member of LAG2 does not respond, and the state transition is as follows. Figure 17 As shown, it maintains the J state (Remote Block Inactive).

[0124] During the recovery period, the 50G member of LAG1 remains inactive, and the 25G member of LAG1 remains deactivated. The 50G and 25G members of LAG2 are controlled by the peer's APS request signal and remain inactive. LAG1 and LAG2 as a whole remain unavailable. BFD1 and BFD2 protocol messages forwarded by LAG1 and LAG2 remain blocked. Due to the failure of BFD1 and BFD2 protocol messages, the upper-layer protection maintains the switchover to the backup path. At this point, the goal is achieved in a scenario where signal degradation fault recovery is pending, the transit LAG does not meet the minimum activation threshold requirement, and the primary path BFD protocol message communication failure is maintained, triggering the upper-layer protection switchover.

[0125] Furthermore, in one embodiment, when a target member on the local end triggers an event indicating that the local end has met the minimum activation threshold requirement due to being in a waiting recovery state for more than a preset time, all members on the local end are controlled to be in a no-request state, and the activation state of each member on the local end is active.

[0126] All members on the control side are in a no-request state, and all members on the control side are in an active state.

[0127] In this embodiment, when the 50G member of LAG1 is in the waiting-for-recovery state for more than a preset time, it migrates to the no-request state (state A, No Request). LAG1 calculates that the number of available members on its local end is 3, and the total available bandwidth on its local end is 25+25+50=100G, which meets the minimum activation threshold requirement, triggering the local end recovery event (h event, Recoverfrom Block). At this time, the 50G member of LAG1 does not respond to the h event, maintains the no-request state (state A, No Request), and sends a no-request APS request signal 0001 to the peer end; the 25G member of LAG1 enters the no-request state (state A, No Request) and sends a no-request APS request signal 0001 to the peer end.

[0128] After LAG2's 50G member receives the No Request (APS) request signal 0001 from the peer, the state transition is as follows: Figure 18a As shown, the state transitions from state K (No Request Inactive) to state A (No Request). After receiving the No Request (APS) request signal 0001 from the peer, the 25G member of LAG2 undergoes the following state transition: Figure 18b As shown, the process transitions from state J (Remote Block Inactive) to state A (No Request).

[0129] Final effect as Figure 13 As shown. For the 50G member of LAG1, after the signal degradation fault is recovered, it is reactivated, and the 25G member is normally restored and activated. For LAG2, all members are restored and activated under the control of the peer APS request signal. LAG1 and LAG2 are available again, and the BFD1 and BFD2 protocol messages forwarded by LAG1 and LAG2 are normally transmitted and received. BFD1 and BFD2 communication is normal, which triggers the upper-layer protection to switch back normally. At this time, the scenario of signal degradation fault recovery and waiting for recovery for more than the preset time is achieved. When the passing LAG meets the minimum activation threshold requirement, the BFD protocol message communication of the primary path is normal and the upper-layer protection is switched back in conjunction.

[0130] Furthermore, in one embodiment, when the target member of this end triggers an event that the minimum activation threshold requirement is not met due to receiving a lock-in-deactivation control command, the target member of this end is controlled to be in a locked-in-deactivation state, the other members of this end are controlled to be in a blocked-inactivation state, and the activation state of each member of this end is an inactive state.

[0131] Control the target member on the other end to be in an inactive state without a request, and the active state of the target member on the other end is inactive.

[0132] The control ensures that the remaining members on the other end are in a remote blocked and inactive state, and that the activation state of the remaining members on the other end is inactive.

[0133] In this embodiment, the lock and deactivate control command is an operation and maintenance command that can interfere with the operation of the project. After receiving the lock and deactivate control command, the LAG member will not carry communication services regardless of whether it is normally available. It is usually used during planned maintenance.

[0134] The final effect achieved in this embodiment is as follows: Figure 19As shown. NE1-NE2-NE3-NE4 is the primary path, and NE1-NE4 is the backup path; NE2 and NE3 are interconnected via optical fibers with speeds of 50G, 25G, and 25G. NE2 deploys LAG1, and NE3 deploys LAG2, each containing 3 members. Communication services are non-equivalently load-sharing among these 3 members; the minimum number of active members configured for LAG1 and LAG2 is 2, and the minimum active bandwidth is 60G.

[0135] Initially, 50G members need to replace optical modules or optical fibers. To reduce service disruption, before replacing the physical link, a 50G member lockout control command is issued on NE2. The 50G members of LAG1 are migrated to state C (Lockout of Inactive), while the 25G members of LAG1 remain in state A (No Request).

[0136] Then, LAG1 calculates that the number of available members on its local end is 2, and the total available bandwidth on its local end is 25 + 25 = 50G, which does not meet the minimum activation threshold requirement. This triggers the "Locking Inactive" event (i event). For the 50G member of LAG1 in the C state (Lockout of Inactive), the state transition is as follows: Figure 20a As shown, the C event (Lockout of Inactive event) has a higher priority than the i event (Block Inactive event). The 50G member of LAG1 does not respond to the i event, maintains the C state (Lockout of Inactive), and sends an APS request signal 1110 for Lockout of Inactive to the peer. For the 25G member of LAG1 in the A state (No Request), the state transition is as follows... Figure 20b As shown, in response to the i event, the 25G member of LAG1 is transitioned from the A state (No Request) to the G state (Block Inactive), and an APS request signal 1100 of Block Inactive is sent to the peer.

[0137] After receiving the Lockout of Inactive APS request signal 1110 from the peer, the 50G member of LAG2 transitions to the K state (No Request Inactive state); after receiving the Block Inactive APS request signal 1100 from the peer, the 25G link of LAG2 transitions to the J state (Remote Block Inactive state).

[0138] Ultimately, for LAG1, the 50G member is inactive due to the issuance of a lockout inactivation control command, and the 25G member is automatically deactivated. For LAG2, both the 50G and 25G members are inactive due to the peer's APS request signal, rendering LAG1 and LAG2 unusable. The BFD1 and BFD2 protocol messages forwarded by LAG1 and LAG2 are blocked, causing a communication failure between the BFD1 and BFD2 protocol messages, which in turn triggers upper-layer protection switching to the backup path. At this point, the goal of issuing the lockout inactivation control command is achieved: the transit LAG does not meet the minimum activation threshold requirement, causing the primary path BFD to fail and triggering upper-layer protection switching.

[0139] Furthermore, in one embodiment, when the target member of this end triggers a normal recovery event from blocked inactivity due to receiving a clearing command, all members of this end and all members of the peer end are controlled to be in a no-request state, and the activation state of all members of this end and all members of the peer end is active.

[0140] In this embodiment, based on the event that the target member on the local end does not meet the minimum activation threshold requirement due to receiving a lockout inactive control command, after the 50G member replaces the physical link and manually confirms that the link is normal, NE2 issues a clear control command to the 50G member. The 50G member is released from the lockout inactive state and transitions from state C (Lockout of Inactive) to state A (No Request). The 25G member remains in state G (BlockInactive).

[0141] LAG1 calculates that the number of available members on its local end is 3, and the total available bandwidth on its local end is 25+25+50=100G, which meets the minimum activation threshold requirement. This triggers the event (h event, Recover from Block) that the local end recovers from the minimum activation threshold requirement. At this time, the 50G member of LAG1 does not respond and maintains state A (No Request). The 25G member of LAG1 transitions from state G (BlockInactive) to state A (No Request). Both the 50G and 25G members of LAG1 send a No Request APS request signal 0001 to the peer.

[0142] When LAG2's 50G and 25G members receive the No Request (APS) request signal 0001 from the peer, they both transition to the A state (No Request).

[0143] Final effect as Figure 13 As shown: After receiving the clear command, the 50G member of LAG1 is reactivated, and the 25G member is reactivated normally. For each member of LAG2, responding to the APS request signal sent by the peer, all members are reactivated, and LAG1 and LAG2 become available again. BFD1 and BFD2 protocol messages forwarded by LAG1 and LAG2 are transmitted and received normally, BFD1 and BFD2 communication is normal, and thus the upper-layer protection can be switched back normally. At this point, the goal is achieved that after the inter-site LAG issues the clear control command, the inter-site LAG meets the minimum activation threshold requirement, causing the primary BFD to UP and triggering the upper-layer protection to switch back.

[0144] Based on the same inventive concept, embodiments of the present invention also provide a LAG linkage protection control device. Members in the LAG communicate via the RFC 5880 standard protocol. In one embodiment, referring to... Figure 21 , Figure 21 This is a functional module diagram of an embodiment of the LAG linkage protection control device of the present invention. Figure 21 As shown, the LAG linkage protection control device includes:

[0145] The state determination module 10 is configured to determine the first target state corresponding to each member of the local end from a preset protection state transition table when the target member of the local end triggers a target event due to a link failure or receiving a control command. The protection state transition table is used to describe the transition relationship between event requests and states. Each state has a corresponding request signal. The target event is an event in which the local end does not meet the minimum activation threshold requirement or an event in which the local end recovers to meet the minimum activation threshold requirement.

[0146] The status control module 20 is configured to control each member of the local end to be in the corresponding first target state and control the activation state of each member of the local end based on the first target state; determine the second target state from the protection state transition table according to the request signal of the first target state, and control each member of the peer end to be in the second target state and control the activation state of each member of the peer end based on the second target state, so as to realize LAG linkage protection.

[0147] Furthermore, in one embodiment, when the target member of this end triggers an event that the minimum activation threshold requirement is not met due to a signal failure, the target member of this end is controlled to be in a signal failure state, the other members of this end are controlled to be in a blocked and inactive state, and the activation state of each member of this end is inactive.

[0148] The target member on the other end is controlled to be in a signal failure state, and the other members on the other end are controlled to be in a blocked and inactive state, and the activation state of each member on the other end is inactive.

[0149] Furthermore, in one embodiment, when the local target member triggers an event that the local end does not meet the minimum activation threshold requirement due to signal failure recovery, the local target member is controlled to be in a waiting recovery state, the other local members are controlled to be in a blocked inactive state, and the activation state of each local member is inactive.

[0150] The target member on the control end is in a waiting recovery state, the other members on the control end are in a blocked and inactive state, and the activation state of each member on this end is inactive.

[0151] Furthermore, in one embodiment, when a target member on the local end triggers an event indicating that the local end meets the minimum activation threshold requirement due to being in a waiting recovery state for more than a preset time, the local end members are controlled to be in a no-request state, and the activation state of each member on the local end is active.

[0152] The control ensures that all members on the other end are in a no-request state, while all members on the local end are in an active state.

[0153] Furthermore, in one embodiment, when the target member of this end triggers an event that the local end does not meet the minimum activation threshold requirement due to signal degradation failure, the target member of this end is controlled to be in a signal degradation state, the other members of this end are controlled to be in a blocked and inactive state, and the activation state of each member of this end is an inactive state.

[0154] Control the target member on the other end to be in an inactive state without requests, control the other members on the other end to be in a remote blocked inactive state, and set the activation state of each member on the other end to be an inactive state.

[0155] Furthermore, in one embodiment, when the local target member triggers an event that the local end does not meet the minimum activation threshold requirement due to signal degradation failure recovery, the local target member is controlled to be in a waiting recovery state, and the other local members are in a blocked inactive state.

[0156] Maintain the peer target member in an inactive state without requests, and keep the peer target member's active state in an inactive state;

[0157] Maintain the remaining members on the other end in a remote blocked inactive state, and keep the active state of the remaining members on the other end in an inactive state.

[0158] Furthermore, in one embodiment, when a target member on the local end triggers an event indicating that the local end has met the minimum activation threshold requirement due to being in a waiting recovery state for more than a preset time, all members on the local end are controlled to be in a no-request state, and the activation state of each member on the local end is active.

[0159] All members on the control side are in a no-request state, and all members on the control side are in an active state.

[0160] Furthermore, in one embodiment, when the target member of this end triggers an event that the minimum activation threshold requirement is not met due to receiving a lock-in-deactivation control command, the target member of this end is controlled to be in a locked-in-deactivation state, the other members of this end are controlled to be in a blocked-inactivation state, and the activation state of each member of this end is an inactive state.

[0161] Control the target member on the other end to be in an inactive state without a request, and the active state of the target member on the other end is inactive.

[0162] The control ensures that the remaining members on the other end are in a remote blocked and inactive state, and that the activation state of the remaining members on the other end is inactive.

[0163] Furthermore, in one embodiment, when the target member of this end triggers a normal recovery event from blocked inactivity due to receiving a clearing command, all members of this end and all members of the peer end are controlled to be in a no-request state, and the activation state of all members of this end and all members of the peer end is active.

[0164] The functions of each module in the LAG linkage protection control device correspond to the steps in the LAG linkage protection control method embodiment, and their functions and implementation processes will not be described in detail here.

[0165] Finally, it should be noted that while some processes described in the embodiments of the present invention include multiple operations or steps that appear in a specific order, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of the present invention, or may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.

[0166] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for LAG linkage protection control, characterized in that, Members in the LAG communicate via the RFC 5880 standard protocol, the method comprising: When a target member on this end triggers a target event due to a link failure or by receiving a control command, the first target state corresponding to each member on this end is determined from a preset protection state transition table. The protection state transition table is used to describe the transition relationship between event requests and states. Each state has a corresponding request signal. The target event is an event in which the local end does not meet the minimum activation threshold requirement, an event in which the local end recovers to meet the minimum activation threshold requirement, or an event in which the local end receives a blocking inactivation request signal sent by the peer's LAG. Control each member on this end to be in the corresponding first target state and control the activation state of each member on this end based on the first target state; Based on the request signal of the first target state, the second target state is determined from the protection state transition table, and each member of the peer end is controlled to be in the second target state. The activation state of each member of the peer end is controlled based on the second target state to realize LAG linkage protection.

2. The method according to claim 1, characterized in that, When the target member of this end triggers an event that the minimum activation threshold requirement is not met due to signal failure, the target member of this end is controlled to be in a signal failure state, the other members of this end are controlled to be in a blocked and inactive state, and the activation state of each member of this end is inactive. The target member on the other end is controlled to be in a signal failure state, and the other members on the other end are controlled to be in a blocked and inactive state, and the activation state of each member on the other end is inactive.

3. The method according to claim 1, characterized in that, When the local target member fails to recover due to signal failure, triggering an event that the local end does not meet the minimum activation threshold requirement, the local target member is controlled to be in a waiting recovery state, the other local members are controlled to be in a blocked inactive state, and the activation state of each local member is inactive. The target member on the control end is in a waiting recovery state, the other members on the control end are in a blocked and inactive state, and the activation state of each member on this end is inactive.

4. The method according to claim 3, characterized in that, When a target member on this end triggers an event indicating that the local end meets the minimum activation threshold requirement due to being in a waiting recovery state for more than a preset time, the local end members are controlled to be in a no-request state, and the activation state of each local end member is active. The control ensures that all members on the other end are in a no-request state, while all members on the local end are in an active state.

5. The method according to claim 1, characterized in that, When the target member of this end triggers an event that the minimum activation threshold requirement is not met due to signal degradation fault, the target member of this end is controlled to be in a signal degradation state, the other members of this end are controlled to be in a blocked and inactive state, and the activation state of each member of this end is inactive. Control the target member on the other end to be in an inactive state without requests, control the other members on the other end to be in a remote blocked inactive state, and set the activation state of each member on the other end to be an inactive state.

6. The method according to claim 1, characterized in that, When the local target member fails to recover due to signal degradation, triggering an event that the local end does not meet the minimum activation threshold requirement, the local target member is put into a waiting recovery state, and the other local members are put into a blocked inactive state. Maintain the target member on the other end in an inactive state without requests, and keep the active state of the target member on the other end in an inactive state; maintain the remaining members on the other end in a remote blocked inactive state, and keep the active state of the remaining members on the other end in an inactive state.

7. The method according to claim 1, characterized in that, When a target member on this end triggers an event indicating that the local end meets the minimum activation threshold requirement due to being in a waiting recovery state for more than a preset time, all members on this end are controlled to be in a no-request state, and the activation state of all members on this end is active. All members on the control side are in a no-request state, and all members on the control side are in an active state.

8. The method according to claim 1, characterized in that, When the target member on this end receives a lock and deactivate control command and triggers an event that the minimum activation threshold requirement is not met, the target member on this end is controlled to be in a locked and deactivate state, the other members on this end are controlled to be in a blocked and deactivate state, and the activation state of each member on this end is a deactivate state. Control the target member on the other end to be in an inactive state without a request, and the active state of the target member on the other end is inactive; control the other members on the other end to be in a remotely blocked inactive state, and the active state of the other members on the other end is inactive.

9. The method according to claim 1, characterized in that, When the target member on this end receives a clearing command and triggers the event that the local end recovers from being blocked and inactive, all members on the local end and all members on the peer end are in a no-request state, and the activation state of all members on this end and all members on the peer end is active.

10. A LAG linkage protection control device, characterized in that, Members in the LAG communicate via the RFC 5880 standard protocol, and the device includes: The state determination module is configured to determine the first target state corresponding to each member of the local end from a preset protection state transition table when the target member of the local end triggers a target event due to a link failure or by receiving a control command. The protection state transition table is used to describe the transition relationship between event requests and states. Each state has a corresponding request signal. The target event is either the local end does not meet the minimum activation threshold requirement or the local end recovers to meet the minimum activation threshold requirement. The status control module is configured to control each member of the local end to be in the corresponding first target state and control the activation state of each member of the local end based on the first target state; determine the second target state from the protection state transition table according to the request signal of the first target state, and control each member of the peer end to be in the second target state and control the activation state of each member of the peer end based on the second target state, so as to realize LAG linkage protection.

Images