Lag protection switching control method and device, equipment and readable storage medium

Abstract

A LAG protection switching control method, device and equipment and readable storage medium, relate to the technical field of communication service protection and switching, and include the following steps: when signal degradation, signal failure, control command issuing and other events occur in the communication process of a LAG member through an 802.3ad standard protocol, the state switching of the local member and the opposite member in different working modes is realized and the active state of the local member and the opposite member is updated through the migration relationship between the event request and the state stored in the pre-designed protection state migration table in the load mode and the protection state migration table in the non-load mode, so as to realize the LAG protection switching corresponding to the signal degradation, signal failure, control command issuing and other events under the 802.3ad standard protocol, and solve the problem of low operation and maintenance efficiency caused by the fact that no operation and maintenance means such as LAG protection control command is defined in the 802.3ad standard.

Description

Technical Field

[0001] This application relates to the field of communication service protection and switching technology, specifically to a LAG protection switching control method, apparatus, device, and readable storage medium. Background Technology

[0002] Currently, signal failure (SF) caused by LACP (Link Aggregation Control Protocol) failure, BFD (Bidirectional Forwarding Detection) failure, or port failure can trigger LAG (Link Aggregation Group) protection switching. However, in engineering maintenance, not only SF problems occur, but also issues such as packet loss and false alarms despite normal links are frequently encountered. Therefore, operators have proposed requirements for triggering LAG protection switching through signal degrade (SD) and issuing control commands. However, the international standard 802.3ad, which LAG follows, does not contain any descriptions of SD, issuing control commands, or triggering LAG switching. In other words, the 802.3ad standard does not define any LAG protection control commands or other maintenance methods, forcing maintenance personnel to seek help from R&D personnel to stabilize LAG services, resulting in low maintenance efficiency.

[0003] It is evident that how to effectively control LAG protection switching in scenarios such as SD and issuing control commands is an urgent problem that needs to be solved. Summary of the Invention

[0004] This application provides a method, apparatus, device, and readable storage medium for LAG protection switching control, which can effectively realize LAG protection switching control in scenarios such as SD card issuance and control command issuance, thereby improving operation and maintenance efficiency.

[0005] In a first aspect, embodiments of this application provide a LAG protection switching control method, wherein members in the LAG communicate via the 802.3ad standard protocol, and the method is applied to a LAG in load mode, comprising the following steps:

[0006] When a target event occurs in the target member of this end, the first target state corresponding to the target event is determined from the preset first protection state transition table. The first protection state transition table is used to describe the transition relationship between the event request and the state under the load mode. Each state has a corresponding request signal. The target event is any one of the following events: signal degradation event, signal failure event, lock activation control command event, lock inactivation control command event, waiting recovery time timeout event, manual activation event, and manual inactivation event.

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

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

[0009] Secondly, embodiments of this application provide an LAG protection switching control device, wherein members in the LAG communicate via the 802.3ad standard protocol, and the device is applied to the LAG in load mode, comprising: a status determination module and a status control module;

[0010] The state determination module is used to determine the first target state corresponding to the target event from a preset first protection state transition table when a target event occurs in the target member of the local end. The first protection state transition table is used to describe the transition relationship between the event request and the state under the load mode. Each state has a corresponding request signal. The target event is any one of the following events: signal degradation event, signal failure event, lock activation control command event, lock inactivation control command event, waiting recovery time timeout event, manual activation event, and manual inactivation event.

[0011] The state control module is used to control the local target member to be in a first target state and to control the activation state of the local target member based on the first target state;

[0012] The state determination module is further configured to determine the second target state from the first protection state transition table based on the request signal of the first target state. The state control module is further configured to control the peer target member to be in the second target state and control the activation state of the peer target member based on the second target state, so as to realize LAG protection switching.

[0013] Thirdly, embodiments of this application provide a LAG protection switching control method, wherein members in the LAG communicate via the 802.3ad standard protocol. The method is applied to a LAG in non-load mode and includes the following steps:

[0014] When a target event occurs in the primary member of this terminal, a third target state corresponding to the target event is determined from the preset second protection state transition table. The second protection state transition table is used to describe the transition relationship between the event request and the state in the non-load mode. Each state has a corresponding request signal. The target event is any one of the following events: signal degradation event, signal failure event, lock activation control command event, lock inactivation control command event, waiting recovery time timeout event, manual activation event, and manual inactivation event.

[0015] Control the primary member of this end to be in the third target state and control the activation state of the target member and the backup member of this end based on the third target state;

[0016] Based on the request signal of the third target state, the fourth target state is determined from the second protection state transition table, and the primary member of the peer end is controlled to be in the fourth target state. The activation state of the primary member and the backup member of the peer end is controlled based on the fourth target state to realize LAG protection switching.

[0017] Fourthly, this application provides an LAG protection switching control device, in which members of the LAG communicate via the 802.3ad standard protocol. The device is applied to the LAG in non-load mode and includes: a status determination module and a status control module.

[0018] The state determination module is used to determine the third target state corresponding to the target event from a preset second protection state transition table when a target event occurs in the local primary member. The second protection state transition table is used to describe the transition relationship between the event request and the state in the non-load mode. Each state has a corresponding request signal. The target event is any one of the following events: signal degradation event, signal failure event, lock activation control command event, lock inactivation control command event, waiting recovery time timeout event, manual activation event, and manual inactivation event.

[0019] The state control module is used to control the local primary member to be in the third target state and to control the activation state of the local target member and the local backup member based on the third target state;

[0020] The state determination module is further configured to determine the fourth target state from the second protection state transition table based on the request signal of the third target state. The state control module is further configured to control the primary member of the peer end to be in the fourth target state and control the activation state of the primary member and the backup member of the peer end based on the fourth target state, so as to realize LAG protection switching.

[0021] Fifthly, embodiments of this application provide an LAG protection switching control device, the LAG protection switching control device including a processor, a memory, and an LAG protection switching control program stored in the memory and executable by the processor, wherein when the LAG protection switching control program is executed by the processor, it implements the steps of the LAG protection switching control method as described above.

[0022] Sixthly, embodiments of this application provide a computer-readable storage medium storing a LAG protection switching control program, wherein when the LAG protection switching control program is executed by a processor, it implements the steps of the LAG protection switching control method as described above.

[0023] The beneficial effects of the technical solutions provided in this application include at least the following:

[0024] When events such as signal degradation, signal failure, or control command issuance occur during communication between LAG members via the 802.3ad standard protocol, the event request and state transition relationship stored in the pre-designed protection state transition table under load mode and the protection state transition table under non-load mode is used to realize the state switching of local and peer members under different working modes and update the activation status of local and peer members. This enables LAG protection switching corresponding to events such as signal degradation, signal failure, and control command issuance under the 802.3ad standard protocol, solving the problem of low operation and maintenance efficiency caused by the lack of LAG protection control commands and other operation and maintenance methods defined in the existing technology. Attached Figure Description

[0025] Figure 1 This is a flowchart illustrating the first embodiment of the LAG protection switching control method of this application;

[0026] Figure 2 This is a schematic representation of the LAG protection state machine state transition corresponding to the local request event under the load mode involved in the embodiments of this application;

[0027] Figure 3 This is a schematic representation of the LAG protection state machine state transition corresponding to the peer request event under the load mode involved in the embodiments of this application;

[0028] Figure 4 This is a schematic diagram illustrating the switching principle of SD faults under load mode in the embodiments of this application;

[0029] Figure 5 This is a schematic diagram illustrating the LAG1 protection state transition corresponding to the SD fault switching scenario under load mode involved in the embodiments of this application.

[0030] Figure 6 This is a schematic diagram illustrating the LAG2 protection state transition corresponding to the SD fault switching scenario under load mode involved in the embodiments of this application.

[0031] Figure 7 This is a schematic diagram illustrating the switching principle of receiving a lock activation control command under load mode in the embodiments of this application;

[0032] Figure 8 This is a schematic diagram illustrating the LAG1 protection state transition when a lock activation control command is received under load mode in the embodiment of this application.

[0033] Figure 9 This is a schematic diagram illustrating the LAG2 protection state transition when a lock activation control command is received under load mode in the embodiment of this application.

[0034] Figure 10 This is a flowchart illustrating the second embodiment of the LAG protection switching control method of this application;

[0035] Figure 11 This is a schematic representation of the LAG protection state machine state transition corresponding to the local request event in the non-load mode involved in the embodiments of this application;

[0036] Figure 12 This is a schematic representation of the LAG protection state machine state transition corresponding to the peer request event in the non-load mode involved in the embodiments of this application;

[0037] Figure 13 This is a schematic diagram illustrating the switching principle of SD faults in non-load mode as described in the embodiments of this application;

[0038] Figure 14 This is a schematic diagram illustrating the LAG1 protection state transition corresponding to the SD fault switching scenario under non-load mode in the embodiments of this application;

[0039] Figure 15 This is a schematic diagram illustrating the LAG2 protection state transition corresponding to the SD fault switching scenario under non-load mode in the embodiments of this application;

[0040] Figure 16 This is a schematic diagram illustrating the switching principle of receiving a lock activation control command in non-load mode in the embodiment of this application.

[0041] Figure 17 This is a schematic diagram illustrating the LAG1 protection state transition when a lock activation control command is received in non-load mode, as described in the embodiments of this application.

[0042] Figure 18This is a schematic diagram illustrating the LAG2 protection state transition when a lock activation control command is received in non-load mode, as described in the embodiments of this application.

[0043] Figure 19 This is a schematic diagram of the hardware structure of the LAG protection switching control device involved in the embodiments of this application. Detailed Implementation

[0044] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0045] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0046] In a first aspect, embodiments of this application provide a method for LAG protection switching control.

[0047] In one embodiment, reference is made to Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the LAG protection switching control method of this application. Members of the LAG communicate via the 802.3ad standard protocol. The method is applied to a LAG in load mode, such as... Figure 1 As shown, the LAG protection switching control method includes:

[0048] Step S10: When a target event occurs in the target member of this end, determine the first target state corresponding to the target event from the preset first protection state transition table. The first protection state transition table is used to describe the transition relationship between the event request and the state under the load mode. Each state has a corresponding request signal. The target event is any one of the following events: signal degradation event, signal failure event, lock activation control command event, lock inactivation control command event, waiting recovery timeout event, manual activation event, and manual inactivation event.

[0049] It should be understood, as an example, that control commands defined by international standards for protection technologies such as G8031 and G8331, such as descriptions of locking the primary function and forced switching, cannot be applied to LAGs. This is because LAGs operate in both non-load and load modes, and in a load-mode LAG, all members have the same role—that is, there is no distinction between primary and backup roles. Therefore, descriptions such as locking the primary function cannot be applied, and a completely new design is required. Thus, this embodiment, in order to provide a protection method for LAGs based on 802.3ad in load mode that supports signal degradation (SD) and control commands, will design a protection state machine for LAGs in load mode that supports SD and control commands.

[0050] First, the LAG request signal and its priority are designed. Specifically, the LAG request signal is designed using the 4-bit reserved field in the LACP (Link Aggregation Control Protocol) message format defined in the 802.3ad standard, resulting in the LAG request signal and its priority as shown in Table 1.

[0051] Table 1 Request Signal and Priority Design Table

[0052]

[0053] The request signals can be divided into 9 types according to their sequence numbers. The second column of the request signals in Table 1 contains 4 bits of specific content. The lowest bit - 1 indicates that the member is active, and 0 indicates that the member is not active. The reason can be seen from the higher bits. For example, the lowest bit of the request signal 1110 corresponding to sequence number 2 is 0, which indicates that the member is not active, while the higher 3 bits are 111, which indicates that the lock is not active. It should be noted that 0000 should be avoided in the steady state without requests to facilitate differentiation. The third and fourth columns of Table 1 are the full English name, abbreviation and Chinese name of each request signal. The fifth column indicates the priority of the request signal, and the smaller the sequence number, the higher the priority. For example, the request signal 1111 corresponding to sequence number 1 has the highest priority, while the request signal 0001 corresponding to sequence number 9 has the lowest priority. The sixth column of Table 1 explains the design considerations for the request signal. For example, the highest priority request signals 1 and 2 can interfere with the operation of the project, while request signals 6 and 7 cannot interfere with the operation of the project. Request signals 3, 4, 5 and 8 and 9 describe the state of the fault scenario and normal scenario in the communication process. 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.

[0054] 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 shown in Table 2; it can be understood that each state has a corresponding request signal.

[0055] Table 2 State Design Table

[0056] State describe Abbreviation A No Request NR Member Active B Lockout of Active LO Active Member Active C Lockout of Inactive LO Inactive Member Inactive D Signal Fail SF Member Inactive E Signal Degrade SD Member Inactive F Wait To Restore WTR Member Inactive G Manual Active Man Active Member Active H Manual Inactive Man Inactive Member Inactive I No Request Inactive NR-Inactive Member Inactive

[0057] In this context, state A, corresponding to "No Request" (NR), indicates no request and its communication service carrying state is "Member Active," meaning the LAG member is active and carrying communication services. State B, corresponding to "Lockout of Active" (LO), indicates lockout active and its communication service carrying state is "Member Active," remaining active regardless of path failure until a "Clear" command is received. State C, corresponding to "Lockout of Inactive" (LOInactive), indicates lockout inactive and its communication service carrying state is "Member Inactive," meaning the LAG member is inactive and not carrying communication services, remaining inactive regardless of path failure until a "Clear" or "Lockout of Active" command is received. State D, corresponding to "Signal Fail" (SF), indicates signal failure and its service carrying state is "Member Inactive," meaning it is not carrying communication services.

[0058] The E state corresponds to Signal Degrade, abbreviated as SD, and its service carrying state is Member Inactive, meaning it is not carrying communication services. The F state corresponds to Wait To Restore, abbreviated as WTR, and its service carrying state is Member Inactive, meaning it is not carrying communication services. The G state corresponds to Manual Active, abbreviated as Man Active, and its communication service carrying state is Member Active, meaning it is carrying communication services. However, if it encounters a higher priority request signal, such as line SF or SD, it will exit this state. The H state corresponds to Manual Inactive, abbreviated as Man Inactive, and its service carrying state is Member Inactive, meaning it is not carrying communication services. The I state corresponds to No Request Inactive, abbreviated as NR-Inactive, and its service carrying state is Member Inactive. Here, Member Inactive means that the local end is normal, that is, there is no path failure at the local end or the local end has not issued control commands, and it is inactive due to the request signal sent by the other end. It should be noted that Table 2 is only a presentation of an example, and the fields in Table 2 can be adjusted according to actual needs.

[0059] 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 of the local LAG; (2) Far-end Request: event request of the remote LAG is received, so as to obtain the local request event table as shown in Table 3 and the far-end request event table as shown in Table 4.

[0060] Table 3 Local Request Event Table

[0061]

[0062] Table 4 Peer Request Event Table

[0063]

[0064] It is understandable that the protection state machine events stored in Tables 3 and 4 represent currently occurring events, and the interpretation principles of each event are similar. For example, column a in Table 3 corresponds to "Lockout of Active," indicating that the local device received a control command to activate the lock, which then jumps to State B, the state of lock activation. Thus, both the State and the Event are displayed as "Lockout of Active." Similarly, column b in Table 3 corresponds to "Lockout of Inactive," indicating that the local device received a control command to deactivate the lock, which then jumps to State C, the state of deactivation. Among these, event d corresponds to "Recover from SF," indicating that the local device recovered from signal failure to alarm-free status; event f corresponds to "Recover from SD," indicating that the local device recovered from signal degradation to alarm-free status; event g corresponds to "WTR timer expires," indicating that the local device experienced a timeout during the recovery wait; and event j corresponds to "Clear," indicating that the local device received a clear control command. It should be noted that Tables 3 and 4 are merely examples, and the fields in Tables 3 and 4 can be adjusted according to actual needs.

[0065] 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 2 The LAG protection state machine state transition table corresponding to the local request event shown in the load mode is as follows: Figure 3 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 2 and Figure 3 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 2 and Figure 3 The corresponding LAG protection state machine state transition table constitutes the first protection state transition table in this embodiment. That is, the first 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.

[0066] In this embodiment, after completing the design of the first protection state transition table under load mode, the state switching of members between the local and peer ends can be realized based on the first protection state transition table to achieve LAG protection switching control. It should be noted that the local target member refers to the member on the local end that has experienced a target event such as a signal degradation event, a signal failure event, a lock activation control command event, a lock inactivation control command event, a recovery timeout event, a manual activation event, or a manual inactivation event. Specifically, when a target member on the local end experiences a target event, the first target state for controlling the state of the local target member is determined from the LAG protection state machine state transition table corresponding to the local request event under load mode, based on the target event. For example, assuming the local target member is currently in state A (NR) and the target event is a signal degradation event (i.e., Signal Degrade corresponding to event e), then... Figure 2 It can be determined that when the target member on this end experiences event e, it needs to switch from state A to state E. That is, the state of the target member on this end needs to be migrated from A to E. Therefore, the first target state is state E.

[0067] Step S20: Control the target member on this end to be in the first target state and control the activation state of the target member on this end based on the first target state.

[0068] As an example, in this embodiment, after determining the first target state, the state transition and activation update of the local target member can be controlled based on the first target state. For example, if the first target state is state E, and the service carrying state of state E is Member Inactive, that is, it is in a state of not carrying communication services, then while controlling the state of the local target member to transition from state A to state E, the activation state of the local target member needs to be updated to inactive so that the local target member does not carry communication services.

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

[0070] In this exemplary embodiment, while performing state transition and activating state control on the local target member according to the first target state, a request signal corresponding to the first target state is also sent to the peer target member communicating with the local target member, so as to obtain information from the peer target member through the request signal. Figure 3The state transition table of the LAG protection state machine corresponding to the peer request event in the load mode shown determines the second target state for controlling the state of the peer target member. Based on the second target state, the state transition and activation state update of the peer target member are controlled, thereby automatically realizing LAG protection switching for different scenario events under the 802.3ad standard protocol.

[0071] 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; therefore, through the request signal 1000, it can be obtained from... Figure 3 The system determines that an event 'o' has occurred in the peer target member, and it needs to switch from state A to state I (i.e., no request, inactive state). Therefore, the second target state is state I. Since the service-carrying state of state I is Member Inactive, meaning it is in a state where it does not carry communication services, while controlling the peer target member's state to transition from state A to state I, the peer target member's active state must be updated to inactive so that the peer target member does not carry communication services.

[0072] As can be seen, this embodiment, based on the 802.3ad standard, extends and proposes LAG support for naming design, request signal type definition, and priority definition for signal degradation and control commands. This allows for the switching of the local and remote members' states and updating their activation states when events such as signal degradation, signal failure, or control command issuance occur during communication between LAG members via the 802.3ad standard protocol. This is achieved by using the migration relationships between event requests and states stored in the pre-designed load mode protection state transition table. This enables LAG protection switching corresponding to events such as signal degradation, signal failure, and control command issuance under the 802.3ad standard protocol, meeting operator requirements and solving the problem of low operational efficiency caused by the lack of defined LAG protection control commands and other operational methods in existing technologies.

[0073] Furthermore, in one embodiment, if the target event is a signal degradation event, the first target state is a signal degradation state and its service bearer state is member inactive, and the second target state is a no-request inactive state and its service bearer state is member inactive.

[0074] Exemplary, see Figure 4As shown, assume network devices NE1 and NE2 are interconnected via four optical fibers, with NE1 deployed on LAG1 and NE2 deployed on LAG2. Each of LAG1 and LAG2 contains four lag members, meaning communication services are load-sharing across these four members, and all four members are currently in state A (i.e., no-request state). When a failover requirement arises in the LAG load pattern due to a signal degradation (SD) fault, i.e., member 1 of LAG1 (the local target member) detects SD, or when member 1 of LAG1 experiences a signal degradation event e (the target event), then according to... Figure 5 As shown, the state of member 1 of LAG1 will be switched from A to E (i.e., signal degradation state, also known as the first target state). Since the service bearer state corresponding to state E is member inactive, it is necessary to control member 1 of LAG1 to be inactive, that is, to deactivate member 1 of LAG1, and the request signal it sends to member 1 of LAG2 (i.e., the peer target member) will change from 0001 to 1000.

[0075] The request signal received by member 1 of LAG2 will change from 0001 to 1000, then according to... Figure 6 As shown, it is necessary to control the State of member 1 of LAG2 to transition from A to I (i.e., no request, inactive state, also known as the second target state). Since the service bearer state corresponding to state I is member inactive, it is necessary to control member 1 of LAG2 to be inactive, which means deactivating member 1 of LAG2, and changing the request signal it sends to member 1 of LAG1 from 0001 to 0010. At this point, member 1 in both LAG1 and LAG2 is in an inactive state, thereby enabling the communication service to be load-balanced among the remaining three members, thus achieving protection switching for SD faults in LAG load mode.

[0076] Furthermore, in one embodiment, if the target event is a lock activation control instruction event, the first target state is a lock activation state and its service bearer state is member activation, and the second target state is a no-request state and its service bearer state is member activation.

[0077] Exemplary, see Figure 7 As shown, assuming NE1 is deployed on LAG1 and NE2 is deployed on LAG2, and the communication service is load-sharing across the four members, when the LACP protocol corresponding to member 1 of LAG1 flickers between normal and fault states, and the possible causes of this flickering are link packet loss or LACP protocol issues, etc., to further investigate the cause of the fault, a lock activation control command will be issued to member 1 of LAG1, i.e., member 1 experiences a lock activation control command event a, then according to... Figure 8As shown, the State of member 1 of LAG1 will be switched from A to B (i.e., locked active state). Since the service bearer state corresponding to state B is member active, it is necessary to keep member 1 of LAG1 active. At this time, member 1 will remain active regardless of whether it encounters SF or SD. At the same time, the request signal sent by member 1 of LAG1 to member 1 of LAG2 will change from 0001 to 1111.

[0078] When member 1 of LAG2 receives a request signal that changes from 0001 to 1111, then according to... Figure 9 As shown, the State of member 1 of LAG2 needs to be controlled to transition from A to A. Since the service bearer state corresponding to state A is member active, member 1 of LAG2 needs to be kept active. Furthermore, regardless of whether SF or SD is encountered, member 1 of LAG2 remains active. At this point, the bidirectional service continues to be load-balanced across the four members. If packet loss occurs, it indicates that the LACP protocol is flickering due to link packet loss; however, if no packet loss occurs, it indicates that the link is normal, and the flickering is caused by the LACP protocol itself, facilitating precise further troubleshooting and effectively improving fault diagnosis efficiency.

[0079] In the scenario of issuing lock activation control commands, in addition to issuing lock activation control commands to member 1 of LAG1, lock activation control commands can also be issued to member 1 of LAG1 and member 1 of LAG2 at the same time, so that the State of member 1 at both ends jumps from A to B, thereby making member 1 at both ends active, and the sending request signals of both ends change from 0001 to 1111. At this time, bidirectional services can continue to be load-sharing on the four members.

[0080] Furthermore, in one embodiment, if the target event is a lock-in-inactivation control instruction event, the first target state is a lock-in-inactivation state and its service bearer state is member inactivation, and the second target state is a no-request inactivation state and its service bearer state is member inactivation.

[0081] As an example, in this embodiment, it is assumed that NE1 is deployed on LAG1, NE2 is deployed on LAG2, and the communication service is load-sharing across the four members. If member 1 encounters a problem requiring replacement of optical modules or optical fibers, in order to reduce service impact, a lockout control command can be issued to member 1 of LAG1, i.e., a lockout event b occurs in member 1 of LAG1. At this time, according to... Figure 2As shown in the LAG protection state machine state transition table corresponding to the local request event, it is necessary to control the State of member 1 of LAG1 to jump from A to C (i.e., lock the inactive state); since the service bearer state corresponding to state C is member inactive, it is necessary to control member 1 of LAG1 to be inactive, and the request signal it sends to member 1 of LAG2 will change from 0001 to 1110.

[0082] At this point, the request signal received by member 1 of LAG2 changes from 0001 to 1110. Therefore, the State of member 1 of LAG2 needs to be controlled to jump from A to I. Since the service bearer state corresponding to state I is member inactive, member 1 of LAG2 also needs to be controlled to be inactive, i.e., member 1 of LAG2 needs to be deactivated, and the request signal it sends to member 1 of LAG1 will change from 0001 to 1110. Afterwards, operations such as replacing optical modules or optical fibers can be performed without affecting communication services. After the operation is completed, if you want to restore the original state, a clear control command is issued to member 1 of LAG1, causing the State of member 1 of LAG1 to jump from C to A, i.e., member 1 of LAG1 is reactivated, and the request signal it sends changes from 1110 to 0001. The request signal received by member 1 of LAG2 then changes back to 0001, and its State also jumps back from I to A, i.e., member 1 of LAG2 is also reactivated.

[0083] In scenarios where a lock inactivation control command is issued, in addition to issuing the lock inactivation control command to member 1 of LAG1, a lock inactivation control command can also be issued to member 1 of both LAG1 and member 1 of LAG2 simultaneously. This causes the State of member 1 at both ends to jump from A to C, thus making member 1 at both ends in an inactive state. At the same time, the send request signals of both ends change from 0001 to 1110. At this time, the normal replacement operation can be completed without affecting the communication service. After the operation is completed, a clear control command is issued. At this time, the State of member 1 at both ends will jump from C back to A, so that member 1 at both ends will be reactivated.

[0084] Furthermore, in one embodiment, if the target event is a signal failure event, the first target state is a signal failure state and its service bearer state is member inactive, and the second target state is a no-request inactive state and its service bearer state is member inactive.

[0085] As an example, in this embodiment, it is assumed that NE1 is deployed on LAG1, NE2 is deployed on LAG2, and the communication service is load-sharing across the four members. If member 1 of LAG1 encounters a fault such as the fiber optic cable being severed during construction, member 1 of LAG1 will detect the fault, i.e., member 1 of LAG1 experiences a signal failure event c. At this time, according to... Figure 2 As shown in the LAG protection state machine state transition table corresponding to the local request event, it is necessary to control the State of member 1 of LAG1 to jump from A to D (i.e., signal failure state). Since the service bearer state corresponding to state D is member inactive, it is necessary to control member 1 of LAG1 to be inactive, and the request signal it sends to member 1 of LAG2 will change from 0001 to 1010.

[0086] At this point, the request signal received by member 1 of LAG2 will change from 0001 to 1010. Therefore, the State of member 1 of LAG2 needs to be controlled to transition from A to I. Since the service bearer state corresponding to state I is member inactive, member 1 of LAG2 also needs to be controlled to be inactive, which means member 1 of LAG2 is deactivated, and the request signal it sends to member 1 of LAG1 will change from 0001 to 1010. Thus, member 1 in both LAG1 and LAG2 is inactive, allowing the communication service to be load-balanced across the remaining three members, thereby achieving protection switching for SF faults in LAG load mode.

[0087] In the SF failure scenario, in addition to member 1 of LAG1 being able to detect the failure, members 1 of both LAG1 and LAG2 may also detect the failure. In this case, the State of members 1 at both ends can be switched from A to D, so that members 1 at both ends are inactive, and other members are responsible for carrying the communication, thereby ensuring normal communication.

[0088] Furthermore, in one embodiment, if the target event is a waiting recovery timeout event, the first target state is waiting for recovery and its service carrying state is member inactive, and the second target state is no request inactive state and its service carrying state is member inactive.

[0089] In this exemplary embodiment, it is assumed that NE1 is deployed on LAG1 and NE2 is deployed on LAG2, and the communication service is load-sharing across the four members. After the cause of the SF fault is identified and the fiber is repaired, member 1 of LAG1 will detect that the SF fault has been recovered. At this time, the State of member 1 of LAG1 will change from D to F (i.e., waiting for recovery), meaning that member 1 of LAG1 enters a waiting-for-recovery state (e.g., waiting continuously for 5 minutes). Since the service bearer state corresponding to state F is member inactive, it is necessary to control member 1 of LAG1 to remain inactive during the waiting-for-recovery state, and the request signal it sends to member 1 of LAG2 will change from 1010 to 0110. The request signal received by member 1 of LAG2 will also change from 1010 to 0110, so it is necessary to control the State of member 1 of LAG2 to change from I to I, meaning that the State of member 1 of LAG2 remains unchanged. Since the service bearer state corresponding to state I is member inactive, it is necessary to control member 1 of LAG2 to continue to remain inactive.

[0090] Once the recovery period ends, the State of member 1 of LAG1 will jump from F back to A, making member 1 of LAG1 active again, and the request signal it sends will change from 0110 back to 0001; while the request signal received by member 1 of LAG2 will change back to 0001, and its State will also jump from I back to A, that is, member 1 of LAG2 will also be active again.

[0091] For the waiting recovery scenario, in addition to member 1 of LAG1 being able to detect that the fault has been recovered, members 1 of both LAG1 and LAG2 may also detect that the fault has been recovered. In this case, the State of members 1 at both ends can be controlled to jump from D to F, that is, members 1 at both ends enter the waiting recovery state, so that members 1 at both ends in the waiting recovery state are inactive. After the waiting recovery time ends, the State of members 1 at both ends is controlled to jump from F to A again, so that members 1 at both ends are reactivated.

[0092] Furthermore, in one embodiment, if the target event is a manually inactive event, the first target state is a manually inactive state and its service carrying state is member inactive, and the second target state is a no-request inactive state and its service carrying state is member inactive.

[0093] In this exemplary embodiment, it is assumed that NE1 is deployed on LAG1, NE2 is deployed on LAG2, and the communication service is load-sharing across the four members. If, during the day, member 1 of LAG1 needs to be deactivated for reasons such as assisting with emergency location, but since daytime is peak communication time, to avoid sudden interruptions and restorations of the link signal, communication must be prioritized, i.e., triggering the normal protection switching and recovery process. At this time, a manual deactivation control command can be issued to member 1 of LAG1, i.e., a manual deactivation event i occurs for member 1 of LAG1. Then, according to... Figure 2 As shown in the LAG protection state machine state transition table corresponding to the local request event, it is necessary to control the State of member 1 of LAG1 to jump from A to H (i.e., manual inactive state). Since the service bearer state corresponding to state H is member inactive, it is necessary to control member 1 of LAG1 to be inactive to assist in emergency location, and the request signal it sends to member 1 of LAG2 will change from 0001 to 0100.

[0094] At this point, the request signal received by member 1 of LAG2 changes from 0001 to 0100. Therefore, it's necessary to control member 1's State to transition from A to I. Since the service bearer state corresponding to state I is member inactive, member 1 of LAG2 also needs to be controlled to be inactive, and its request signal to member 1 of LAG1 will change from 0001 to 0100. After the location is completed, a clear control command can be issued to member 1 of LAG1 to make its State transition from H back to A, thus making member 1 of LAG1 active again, and its request signal to member 1 of LAG2 changes from 0100 to 0001. Meanwhile, the request signal received by member 1 of LAG2 changes back to 0001, and its State also transitions from I back to A, meaning member 1 of LAG2 is also active again.

[0095] In scenarios where a manual deactivation control command is issued, in addition to issuing the command to member 1 of LAG1, a manual deactivation control command can also be issued simultaneously to member 1 of both LAG1 and LAG2. This causes the State of member 1 at both ends to jump from A to H, thus placing member 1 at both ends in an inactive state to assist in emergency location. After location is completed, a clear control command is issued, at which point the State of member 1 at both ends will jump back from H to A, thus reactivating member 1 at both ends.

[0096] Furthermore, in one embodiment, if the target event is a manually activated event, the first target state is a manually activated state and its service carrying state is member activated, and the second target state is a no-request state and its service carrying state is member activated.

[0097] In this exemplary embodiment, it is assumed that NE1 is deployed on LAG1 and NE2 is deployed on LAG2, and the communication service is load-sharing across the four members. After member 1 of LAG1 and member 1 of LAG2 are inactive due to a manual inactivation control command, if the location tracking ends at this point, a manual activation control command can still be issued to member 1 of LAG1, i.e., a manual activation event h occurs for member 1 of LAG1. At this time, according to... Figure 2 As shown in the LAG protection state machine state transition table corresponding to the local request event, the State of member 1 of LAG1 can be controlled to jump from H to G (i.e., manual activation state). Since the service bearer state corresponding to state G is member activation, it is necessary to control member 1 of LAG1 to be reactivated, and the request signal it sends to member 1 of LAG2 will change from 0100 to 0101.

[0098] At this time, the request signal received by member 1 of LAG2 will also change from 0100 to 0101. Therefore, it is necessary to control the state of member 1 of LAG2 to jump from I to A. Since the service bearer state corresponding to state A is member active, it is necessary to control member 1 of LAG2 to be in the active state.

[0099] In scenarios where manual activation control commands are issued, in addition to issuing manual activation control commands to member 1 of LAG1, manual activation control commands can also be issued to member 1 of both LAG1 and member 1 of LAG2 at the same time, so that the State of member 1 at both ends jumps from H to G, thereby making member 1 at both ends re-activated.

[0100] Secondly, embodiments of this application also provide a LAG protection switching control device.

[0101] In one embodiment, members in the LAG communicate via the 802.3ad standard protocol. The LAG protection switching control device is applied to the LAG in load mode. The LAG protection switching control device includes a status determination module and a status control module.

[0102] The state determination module is used to determine the first target state corresponding to the target event from a preset first protection state transition table when a target event occurs in the target member of the local end. The first protection state transition table is used to describe the transition relationship between the event request and the state under the load mode. Each state has a corresponding request signal. The target event is any one of the following events: signal degradation event, signal failure event, lock activation control command event, lock inactivation control command event, waiting recovery time timeout event, manual activation event, and manual inactivation event.

[0103] The state control module is used to control the local target member to be in a first target state and to control the activation state of the local target member based on the first target state;

[0104] The state determination module is further configured to determine the second target state from the first protection state transition table based on the request signal of the first target state. The state control module is further configured to control the peer target member to be in the second target state and control the activation state of the peer target member based on the second target state, so as to realize LAG protection switching.

[0105] Furthermore, in one embodiment, if the target event is a signal degradation event, the first target state is a signal degradation state and its service bearer state is member inactive, and the second target state is a no-request inactive state and its service bearer state is member inactive.

[0106] Furthermore, in one embodiment, if the target event is a signal failure event, the first target state is a signal failure state and its service bearer state is member inactive, and the second target state is a no-request inactive state and its service bearer state is member inactive.

[0107] Furthermore, in one embodiment, if the target event is a lock activation control instruction event, the first target state is a lock activation state and its service bearer state is member activation, and the second target state is a no-request state and its service bearer state is member activation.

[0108] Furthermore, in one embodiment, if the target event is a lock-in-inactivation control instruction event, the first target state is a lock-in-inactivation state and its service bearer state is member inactivation, and the second target state is a no-request inactivation state and its service bearer state is member inactivation.

[0109] Furthermore, in one embodiment, if the target event is a waiting recovery timeout event, the first target state is waiting for recovery and its service carrying state is member inactive, and the second target state is no request inactive state and its service carrying state is member inactive.

[0110] Furthermore, in one embodiment, if the target event is a manually activated event, the first target state is a manually activated state and its service carrying state is member activated, and the second target state is a no-request state and its service carrying state is member activated.

[0111] Furthermore, in one embodiment, if the target event is a manually inactive event, the first target state is a manually inactive state and its service carrying state is member inactive, and the second target state is a no-request inactive state and its service carrying state is member inactive.

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

[0113] Thirdly, this application also provides another LAG protection switching control method.

[0114] In one embodiment, reference is made to Figure 10 , Figure 10 This is a flowchart illustrating the second embodiment of the LAG protection switching control method of this application. Members of the LAG communicate via the 802.3ad standard protocol. The method is applied to the LAG in non-load mode, such as... Figure 10 As shown, the LAG protection switching control method includes:

[0115] Step N10: When a target event occurs in the primary member of this terminal, the third target state corresponding to the target event is determined from the preset second protection state transition table. The second protection state transition table is used to describe the transition relationship between the event request and the state in the non-load mode. Each state has a corresponding request signal. The target event is any one of the following events: signal degradation event, signal failure event, lock activation control command event, lock inactivation control command event, waiting recovery timeout event, manual activation event, and manual inactivation event.

[0116] As an example, in this embodiment, in order to provide a protection method for LAG support of signal degradation (SD) and control commands, etc., under non-load mode based on 802.3ad, a protection state machine for LAG support of SD and control commands, etc., will be designed under non-load mode. It should be understood that LAG under non-load mode has only two members: a primary member and a backup member. Therefore, in this embodiment, Working will be used to represent the primary member and Protection will be used to represent the backup member. Only one member can be active while the other is inactive.

[0117] First, the LAG request signals and their priorities were designed to obtain the LAG request signals and their priorities as shown in Table 1. Second, based on the request signals, the State field of the LAG protection state machine in non-load mode was designed to obtain the State design table shown in Table 5; it can be understood that each state has a corresponding request signal.

[0118] Table 5 State Design Table

[0119]

[0120]

[0121] In this context, state A, corresponding to "No Request" (NR), indicates no request and its communication service carrying state is "Working Actve / Protection Inactive." Specifically, the primary member is active (carrying communication services), while the backup member is inactive (not carrying communication services). State B, corresponding to "Lockout of Active" (LO Active), indicates locked-out activity and its communication service carrying state is "Working Actve / Protection Inactive." Specifically, the primary member is active (carrying communication services), while the backup member is inactive (not carrying communication services). This state remains unchanged regardless of path failure and only exits upon receiving a "Clear" control command. State C, corresponding to "Lockout of Inactive" (LO Inactive), indicates locked-out activity and its communication service carrying state is "Working Inactive / Protection Actve." Specifically, the primary member is inactive, while the backup member is active. This state remains unchanged regardless of path failure and only exits upon receiving a "Clear" or "Lockout of Active" control command.

[0122] The D state corresponds to Working Signal Fail, which is abbreviated as SF-W. Its service carrying state is Working Inactive / Protection Actve, specifically meaning that the primary member is inactive while the backup member is active. The E state corresponds to Protection Signal Fail, which is abbreviated as SF-P. Its service carrying state is Working Actve / Protection Inactive, specifically meaning that the primary member is active while the backup member is inactive. The F state corresponds to Working Signal Degrade, which is abbreviated as SD-W. Its service carrying state is Working Inactive / Protection Actve, specifically meaning that the primary member is inactive while the backup member is active. The G state corresponds to Protection Signal Degrade, which is abbreviated as SD-P. Its service carrying state is Working Actve / Protection Inactive, specifically meaning that the primary member is active while the backup member is inactive.

[0123] The H state, corresponding to Wait To Restore (WTR), indicates waiting for recovery. Its service carrying state is Working Inactive / Protection Active, specifically meaning the primary member is inactive while the backup member is active. The I state, corresponding to Manual Active (Man Active), indicates manual activation. Its communication service carrying state is Working Active / Protection Inactive, specifically meaning the primary member is active while the backup member is inactive. If a higher priority request signal, such as the primary SF or SD, is encountered, this state will exit. The J state, corresponding to Manual Inactive (Man Inactive), indicates manual inactivity. Its service carrying state is Working Inactive / Protection Active, specifically meaning the primary member is inactive while the backup member is active. The K state, corresponding to No Request Inactive (NR-Inactive), indicates no request and inactivity. Its service carrying state is Working Inactive / Protection Active. Actve specifically indicates that both ends are normal, meaning that the local end has not issued control commands or the primary and backup paths are fault-free, and the primary member is inactive and the backup member is active due to a request signal sent by the other end.

[0124] Next, the event of the LAG protection state machine under non-load mode is designed; in this embodiment, it is still preferred to divide the LAG protection state machine event design into two categories: (1) Local Request: event request of the local LAG; (2) Far-end Request: event request of the remote LAG is received, so as to obtain the local request event table as shown in Table 6 and the far-end request event table as shown in Table 7.

[0125] Table 6 Local Request Event Table

[0126]

[0127] Table 7 Peer Request Event Table

[0128]

[0129] It is understandable that the protection state machine events stored in Tables 6 and 7 represent currently occurring events, and the interpretation principles of each event are similar. For example, the Lockout of Active corresponding to column a in Table 6 indicates that the event occurring on this end is that the primary member receives a control command to activate the lock, which will then jump to State B, the state of lock activation. It can be seen that both the State and the Event are displayed as Lockout of Active. Another example is the Lockout of Inactive corresponding to column b in Table 6, which indicates that the event occurring on this end is that the primary member receives a control command to deactivate the lock, which will then jump to State C, the state of deactivation. Among them, the Working Recover from SF corresponding to event d indicates that the event occurring on this end is that the primary member recovers from signal failure to no alarm; the Protection Recover from SF corresponding to event f indicates that the event occurring on this end is that the backup member recovers from signal failure to no alarm; the Working Recover from SD corresponding to event h indicates that the event occurring on this end is that the primary member recovers from signal degradation to no alarm; and the Protection Recover from SD corresponding to event j indicates that the event occurring on this end is that the backup member recovers from signal degradation to no alarm.

[0130] Finally, based on the LAG request signal and its priority, the State field of the LAG protection state machine in non-load mode, and the design of the Event, the design of the LAG protection state machine state transition table is implemented to obtain, as follows: Figure 11 The LAG protection state machine state transition table corresponding to the local request event in non-load mode is shown below. Figure 12 The table shown is the LAG protection state machine state transition table corresponding to the peer request event in non-load mode; it should be noted that... Figure 11 and Figure 12 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 11 and Figure 12 The corresponding LAG protection state machine state transition table constitutes the second protection state transition table in this embodiment. That is, the second protection state transition table includes the LAG protection state machine state transition table corresponding to the local request event in the non-load mode and the LAG protection state machine state transition table corresponding to the peer request event in the non-load mode. It describes the transition relationship between the event request and the state in the non-load mode.

[0131] In this embodiment, after completing the design of the second protection state transition table in non-load mode, the state switching of members between the local and peer ends can be realized based on this second protection state transition table to achieve LAG protection switching control. It should be noted that the local primary member refers to the member on the local end that experiences target events such as signal degradation, signal failure, lock activation control command, lock inactivation control command, recovery timeout, manual activation, or manual inactivation. Specifically, when the local primary member experiences a target event, a third target state for controlling the local member's state is determined from the LAG protection state machine state transition table corresponding to the local request event in non-load mode based on the target event. For example, assuming the local primary member is currently in state A (NR) and the target event is the primary member signal degradation event (i.e., SD on Working corresponding to event g), then... Figure 11 It can be determined that when the local primary member experiences event g, it needs to switch from state A to state F. That is, the state of the local primary member needs to be migrated from A to F. Therefore, the third target state is state F.

[0132] Step N20: Control the primary member of this end to be in the third target state and control the activation state of the target member and the backup member of this end based on the third target state.

[0133] As an example, in this embodiment, after determining the third target state, the state transition and activation update of the local member can be controlled based on this third target state. For example, if the third target state is state F, since the service carrying state of state F is Working Inactive / Protection Active, that is, the primary member does not carry communication services while the backup member does, therefore, while controlling the state of the primary member to transition from state A to state F, the activation state of the primary member needs to be updated to inactive, and the activation state of the backup member needs to be updated to active, so that the primary member does not carry communication services, and the backup member carries the communication services.

[0134] Step N30: ​​Determine the fourth target state from the second protection state transition table based on the request signal of the third target state, and control the primary member of the peer end to be in the fourth target state. Based on the fourth target state, control the activation state of the primary member and the backup member of the peer end to realize LAG protection switching.

[0135] As an example, in this embodiment, while performing state transition and activating state control for the local primary member and local backup member according to the third target state, a request signal corresponding to the third target state is also sent to the peer primary member communicating with the local primary member, so as to obtain information from the peer primary member through this request signal. Figure 12The LAG protection state machine state transition table corresponding to the peer request event in the non-load mode shows that the fourth target state is determined to control the state of the peer primary member. Based on the fourth target state, the state transition of the peer primary member and the activation state of the peer primary member and the peer backup member are updated, thereby automatically realizing LAG protection switching for different scenario events under the 802.3ad standard protocol.

[0136] For example, suppose the third target state is F and the peer primary member is currently in state A. Since the request signal corresponding to state F is 1000, the request signal received by the peer primary member changes from 0001 in state A to 1000; therefore, through the request signal 1000, it can be obtained from... Figure 12 The process determines that the primary member on the other end has experienced event g, and it needs to switch from state A to state K (i.e., inactive state without request). Therefore, the primary member's state needs to transition from A to K, making state K the fourth target state. Since state K's service carrying state is Working Inactive / Protection Active, meaning the primary member is not carrying communication services while the backup member is carrying them, while controlling the primary member's state to transition from A to K, the primary member's active state needs to be updated to inactive, and the backup member's active state needs to be updated to active. This ensures the primary member does not carry communication services, and the backup member carries them instead.

[0137] As can be seen, this embodiment, based on the 802.3ad standard, extends and proposes LAG support for naming design, request signal type definition, and priority definition for signal degradation and control commands. This allows for the switching of the local and remote members' states and updating their activation states when events such as signal degradation, signal failure, or control command issuance occur during communication between LAG members via the 802.3ad standard protocol. This is achieved by using the event request and state transition relationships stored in the pre-designed non-load mode protection state transition table. This enables LAG protection switching corresponding to events such as signal degradation, signal failure, and control command issuance under the 802.3ad standard protocol, meeting operator requirements and solving the problem of low operational efficiency caused by the lack of defined LAG protection control commands and other operational methods in existing technologies.

[0138] Furthermore, in one embodiment, if the target event is a signal degradation event, the third target state is a primary member signal degradation state, and its service carrying state is that the primary member is not activated and the backup member is activated; the fourth target state is a no-request inactive state, and its service carrying state is that the primary member is not activated and the backup member is activated.

[0139] Exemplary, see Figure 13 As shown, assuming network devices NE1 are deployed on LAG1 and NE2 on LAG2, with member 1 being the primary member and member 2 being the backup member, under normal circumstances, communication services only pass through the primary member; when a failover requirement for SD (Signal Degradation) occurs in LAG's non-load mode, i.e., the primary member of LAG1 (i.e., the local primary member) detects SD, that is, the primary member of LAG1 experiences a signal degradation event g (i.e., the target event), then according to... Figure 14 As shown, the State of the primary member of LAG1 will be switched from A to F (i.e., the primary member signal degradation state, also known as the third target state). Since the service bearer state corresponding to state F is that the primary member is not active and the backup member is active, it is necessary to control the primary member of LAG1 to be inactive and the backup member to be active. Then, the request signal sent by the primary member of LAG1 to the primary member of LAG2 (i.e., the peer primary member) will change from 0001 to 1000.

[0140] The request signal received by the primary member of LAG2 will change from 0001 to 1000, then according to... Figure 15 As shown, the State of the primary member of LAG2 needs to be controlled to transition from A to K (i.e., the inactive state without request, also known as the fourth target state). Since the service bearer state corresponding to state K is that the primary member is inactive and the backup member is active, it is necessary to control the primary member of LAG2 to be inactive and the backup member to be active. Therefore, the request signal sent by the primary member of LAG2 to the primary member of LAG1 will change from 0001 to 0010. At this point, the primary members in both LAG1 and LAG2 are inactive, allowing communication services to be transmitted on the backup member, thus achieving protection switching for SD faults in LAG non-load mode.

[0141] Furthermore, in one embodiment, if the target event is a lock activation control command event, the third target state is a lock activation state, in which the primary member is activated and the backup member is not activated, and the fourth target state is a no-request state, in which the primary member is activated and the backup member is not activated.

[0142] Exemplary, see Figure 16As shown, assuming NE1 is deployed on LAG1 and NE2 is deployed on LAG2, with member 1 being the primary member and member 2 being the backup member, under normal circumstances, communication services only use the primary member. When the LACP protocol corresponding to the primary member of LAG1 flickers between normal and fault states, and the possible causes of this flickering are link packet loss or LACP protocol issues, etc., to further investigate the cause of the fault, a lock activation control command will be issued to the primary member of LAG1. That is, when the primary member of LAG1 experiences a lock activation control command event a, then according to... Figure 17 As shown, the State of the primary member of LAG1 will be switched from A to B (i.e., locked active state). Since the service bearer state corresponding to state B is active for the primary member and inactive for the backup member, it is necessary to keep the primary member of LAG1 active while the backup member of LAG1 is inactive. At this time, regardless of whether SF or SD is encountered, the primary member of LAG1 remains active and the backup member remains inactive. At the same time, the request signal sent by the primary member of LAG1 to the primary member of LAG2 will change from 0001 to 1111.

[0143] When the request signal received by the primary member of LAG2 changes from 0001 to 1111, then according to... Figure 18 As shown, the State of the primary member of LAG2 needs to be controlled to transition from A to A. Since the service bearer state corresponding to state A is active for the primary member and inactive for the backup member, the primary member of LAG2 needs to be kept active while the backup member remains inactive. Furthermore, regardless of whether an SF or SD occurs, the primary member of LAG2 remains active while the backup member remains inactive. Thus, bidirectional services continue to be transmitted only on the primary member. If packet loss occurs at this point, it indicates that the LACP protocol is flickering due to link packet loss; however, if no packet loss occurs, it indicates that the link is normal, and the flickering is caused by the LACP protocol itself, facilitating precise further troubleshooting and effectively improving fault diagnosis efficiency.

[0144] In scenarios where lock activation control commands are issued, in addition to issuing lock activation control commands to the primary member of LAG1, lock activation control commands can also be issued to the primary members of both LAG1 and LAG2 simultaneously, so that the State of the primary members at both ends jumps from A to B, thereby making the primary members at both ends active, while the backup members at both ends are inactive, and the send request signals of both ends change from 0001 to 1111. At this time, bidirectional services can also be transmitted only on the primary members.

[0145] Furthermore, in one embodiment, if the target event is a lock-in-inactivation control instruction event, the third target state is a lock-in-inactivation state, and its service carrying state is that the primary member is not activated and the backup member is activated; the fourth target state is a no-request-inactivation state, and its service carrying state is that the primary member is not activated and the backup member is activated.

[0146] In this exemplary embodiment, it is assumed that network devices NE1 are deployed on LAG1 and NE2 on LAG2, with member 1 being the primary member and member 2 being the backup member. Under normal circumstances, communication services only pass through the primary member. If the primary member of LAG1 encounters a problem requiring replacement of an optical module or fiber, to reduce service disruption, a lockout / inactivation control command can be issued to the primary member of LAG1, i.e., a lockout / inactivation event b occurs in the primary member of LAG1. At this time, according to... Figure 11 As shown in the LAG protection state machine state transition table corresponding to the local request event, it is necessary to control the primary member of LAG1 to transition from A to C (i.e., lock in the inactive state). Since the service bearer state corresponding to state C is that the primary member is inactive and the backup member is active, it is necessary to control the primary member of LAG1 to be inactive and the backup member to be active. The request signal sent by the primary member of LAG1 to the primary member of LAG2 will change from 0001 to 1110.

[0147] At this point, the request signal received by the primary member of LAG2 changes from 0001 to 1110. Therefore, the state of the primary member of LAG2 needs to be controlled to transition from A to K. Since the service bearer state corresponding to state K is that the primary member is inactive and the backup member is active, the primary member of LAG2 also needs to be controlled to be inactive, while the backup member of LAG2 is active. The request signal sent by the primary member of LAG2 to the primary member of LAG1 will change from 0001 to 1110. After this, operations such as replacing optical modules or optical fibers can be performed without affecting communication services. Once the operation is complete... After completion, if you want to restore the original state, issue a clear control command to the primary member of LAG1, so that the state of the primary member of LAG1 jumps from C to A, that is, the primary member of LAG1 is reactivated, while the standby member of LAG1 is deactivated again, and its sent request signal changes from 1110 to 0001; while the request signal received by the primary member of LAG2 changes back to 0001, and its state also jumps from K back to A, that is, the primary member of LAG2 is also reactivated, while the standby member of LAG2 is deactivated again.

[0148] In scenarios where a lock / deactivation control command is issued, in addition to issuing the lock / deactivation control command to the primary member of LAG1, the lock / deactivation control command can also be issued simultaneously to the primary members of both LAG1 and LAG2. This causes the State of the primary members at both ends to jump from A to C, thus making the primary members at both ends in an inactive state, while the backup members at both ends are in an active state. Furthermore, the send request signals of both ends change from 0001 to 1110. At this time, a normal replacement operation can be completed without affecting communication services. After the operation is completed, a clear control command is issued. At this time, the State of the primary members at both ends will jump from C back to A, so that the primary members at both ends are in an active state again, while the backup members at both ends are in an inactive state again.

[0149] Furthermore, in one embodiment, if the target event is a signal failure event, the third target state is the primary member signal failure state, and its service carrying state is that the primary member is not activated and the backup member is activated; the fourth target state is the no-request inactive state, and its service carrying state is that the primary member is not activated and the backup member is activated.

[0150] In this exemplary embodiment, it is assumed that network devices NE1 are deployed on LAG1 and NE2 on LAG2, with member 1 being the primary member and member 2 being the backup member. Under normal circumstances, communication services only pass through the primary member. If the primary member of LAG1 encounters a fault such as the fiber optic cable being severed during construction, the primary member of LAG1 will detect the fault, i.e., a signal failure event c occurs in the primary member of LAG1. At this time, according to... Figure 11 As shown in the LAG protection state machine state transition table corresponding to the local request event, it is necessary to control the State of the primary member of LAG1 to jump from A to D (i.e., the primary member signal failure state). Since the service bearer state corresponding to state D is that the primary member is not active and the backup member is active, it is necessary to control the primary member of LAG1 to be inactive and the backup member to be active. The request signal sent by the primary member of LAG1 to the primary member of LAG2 will change from 0001 to 1010.

[0151] At this point, the request signal received by the primary member of LAG2 will change from 0001 to 1010, so the state of the primary member of LAG2 needs to be controlled to jump from A to K. Since the service bearer state corresponding to state K is that the primary member is inactive and the backup member is active, the primary member of LAG2 also needs to be controlled to be inactive and the backup member to be active, and the request signal sent by the primary member of LAG2 to the primary member of LAG1 will change from 0001 to 1010. Thus, the primary members in both LAG1 and LAG2 are in an inactive state, while the backup members in both LAG1 and LAG2 are in an active state, allowing communication services to be transmitted on the backup member, thereby achieving protection switching for SF faults in LAG non-load mode.

[0152] In the case of SF failure, in addition to the primary member of LAG1 being able to detect the failure, the primary members of LAG1 and LAG2 may also detect the failure. In this case, the State of the primary members at both ends can be controlled to jump from A to D, so that the primary members at both ends are inactive and the backup members at both ends are active, so that the backup members are responsible for carrying the communication, thereby ensuring normal communication.

[0153] Furthermore, in one embodiment, if the target event is a waiting recovery timeout event, the third target state is a waiting recovery state, in which the primary member is not activated and the backup member is activated; the fourth target state is a no-request inactive state, in which the primary member is not activated and the backup member is activated.

[0154] In this exemplary embodiment, it is assumed that network devices NE1 are deployed on LAG1 and NE2 are deployed on LAG2, with member 1 being the primary member and member 2 being the backup member. Under normal circumstances, communication services only pass through the primary member. After the cause of the SF fault is identified and the fiber is repaired, the primary member of LAG1 will detect that the SF fault has been recovered. At this time, the state of the primary member of LAG1 will jump from D to H (i.e., waiting for recovery), that is, the primary member of LAG1 enters the waiting for recovery state (e.g., waiting continuously for 5 minutes). Since the service bearer state corresponding to state H is that the primary member is not active and the backup member is active, it is necessary to control the primary member of LAG1 to remain inactive and the backup member to remain active in the waiting for recovery state. The request signal sent by the primary member of LAG1 to the primary member of LAG2 will change from 1010 to 0110. The request signal received by the primary member of LAG2 will also change from 1010 to 0110. Therefore, it is necessary to control the state of the primary member of LAG2 to jump from K to K. That is, the state of the primary member of LAG2 remains unchanged. Since the service bearer state corresponding to state K is that the primary member is not active and the backup member is active, it is necessary to control the primary member of LAG2 to continue to remain inactive, while the backup member of LAG2 continues to remain active.

[0155] Once the recovery period ends, the state of the primary member of LAG1 will jump from H back to A, making the primary member of LAG1 active again and the standby member inactive again. The request signal sent by the primary member of LAG1 will change from 0110 back to 0001. The request signal received by the primary member of LAG2 will change back to 0001, and its state will also jump from K back to A. That is, the primary member of LAG2 will also be active again, and the standby member of LAG2 will be inactive again.

[0156] For the waiting recovery scenario, in addition to the primary member of LAG1 being able to detect that the fault has been recovered, the primary members of both LAG1 and LAG2 may also detect that the fault has been recovered. In this case, the State of the primary members at both ends can be controlled to jump from D to H, that is, the primary members at both ends enter the waiting recovery state, so that the primary members at both ends in the waiting recovery state are inactive, while the standby members at both ends are active. After the waiting recovery time ends, the State of the primary members at both ends is controlled to jump from H to A again, so that the primary members at both ends are active again, while the standby members at both ends are inactive again.

[0157] Furthermore, in one embodiment, if the target event is a manually activated event, the third target state is a manually activated state, in which the primary member is activated and the backup member is not activated; the fourth target state is a no-request state, in which the primary member is activated and the backup member is not activated.

[0158] In this exemplary embodiment, it is assumed that network devices NE1 are deployed on LAG1 and NE2 on LAG2, with member 1 being the primary member and member 2 being the backup member. Under normal circumstances, communication services only pass through the primary member. If, during the day, for reasons such as assisting with emergency location, the primary member of LAG1 needs to be deactivated, but since daytime is peak communication time, to avoid sudden interruptions and restorations of the link signal, communication must be prioritized, triggering the normal protection switching and recovery process. At this time, a manual deactivation control command can be issued to the primary member of LAG1, i.e., a manual deactivation event m occurs for the primary member of LAG1. Then, according to... Figure 11 As shown in the LAG protection state machine state transition table corresponding to the local request event, it is necessary to control the State of primary member 1 of LAG1 to jump from A to J (i.e., manual inactive state). Since the service bearer state corresponding to state J is that the primary member is inactive and the backup member is active, it is necessary to control the primary member of LAG1 to be inactive and the backup member to be active in order to assist in emergency location. The request signal sent by the primary member of LAG1 to the primary member of LAG2 will change from 0001 to 0100.

[0159] At this time, the request signal received by the primary member of LAG2 changes from 0001 to 0100. Therefore, it is necessary to control the state of the primary member of LAG2 to jump from A to K. Since the service bearer state corresponding to state K is that the primary member is not active and the backup member is active, it is necessary to control the primary member of LAG2 to also be in an inactive state, while the backup member of LAG2 is in an active state, and the request signal sent by the primary member of LAG2 to the primary member of LAG1 will change from 0001 to 0100. After the location is completed, a clear control command can be issued to the primary member of LAG1 to make the state of the primary member of LAG1 jump from J back to A. This makes the primary member of LAG1 active again and the standby member inactive again. The request signal sent by the primary member of LAG1 to the primary member of LAG2 changes from 0100 to 0001. The request signal received by the primary member of LAG2 changes back to 0001, and its state also jumps from K back to A. That is, the primary member of LAG2 is also active again, while the standby member of LAG2 is inactive again.

[0160] In scenarios where a manual deactivation control command is issued, in addition to issuing the command to the primary member of LAG1, it can also be issued simultaneously to the primary members of both LAG1 and LAG2. This causes the State of the primary members at both ends to jump from A to J, thus deactivating the primary members at both ends while activating the backup members at both ends to assist in emergency location. After the location is completed, a clear control command is issued. At this time, the State of the primary members at both ends will jump back from J to A, reactivating the primary members at both ends while deactivating the backup members at both ends.

[0161] Furthermore, in one embodiment, if the target event is a manually inactive event, the third target state is a manually inactive state, and its service carrying state is that the primary member is inactive and the backup member is active; the fourth target state is a no-request inactive state, and its service carrying state is that the primary member is inactive and the backup member is active.

[0162] In this exemplary embodiment, it is assumed that network devices NE1 are deployed on LAG1 and NE2 on LAG2, with member 1 being the primary member and member 2 being the backup member. Under normal circumstances, communication services only pass through the primary member. If the primary members of LAG1 and LAG2 are inactive due to a manual inactivation control command, and if the location tracking ends at this point, a manual activation control command can still be issued to the primary member of LAG1, i.e., a manual activation event 1 occurs for the primary member of LAG1. At this time, according to... Figure 11 As shown in the LAG protection state machine state transition table corresponding to the local request event, the State of the primary member z of LAG1 can be controlled to jump from J to I (i.e., manual activation state). Since the service bearer state corresponding to state I is active for the primary member and inactive for the backup member, it is necessary to control the primary member of LAG1 to be activated again and the backup member to be inactive again. The request signal sent by the primary member of LAG1 to the primary member of LAG2 will change from 0100 to 0101.

[0163] At this time, the request signal received by the primary member of LAG2 will also change from 0100 to 0101. Therefore, it is necessary to control the state of the primary member of LAG2 to jump from K to A. Since the service bearer state corresponding to state A is active for the primary member and inactive for the backup member, it is necessary to control the primary member of LAG2 to be active and the backup member to be inactive.

[0164] In scenarios where manual activation control commands are issued, in addition to issuing manual activation control commands to the primary members of LAG1, manual activation control commands can also be issued to the primary members of both LAG1 and LAG2 simultaneously, so that the State of the primary members at both ends jumps from J to I, thereby making the primary members at both ends re-activated, while the backup members at both ends are re-deactivated.

[0165] In summary, this embodiment extends the LACP protocol by combining the features of the 802.3ad standard, realizing the design of control command names, the definition of request signal types and priorities. It also proposes a LAG protection state machine transition table that is compatible with both load and non-load modes. This not only meets the requirements of SD, SF and control commands to trigger LAG protection switching, but also solves the deficiency of the 802.3ad standard in not supporting control commands, and has the potential for standardization.

[0166] Fourthly, this application also provides another LAG protection switching control device.

[0167] In one embodiment, members in the LAG communicate via the 802.3ad standard protocol. The LAG protection switching control device is applied to the LAG in non-load mode. The LAG protection switching control device includes: a status determination module and a status control module.

[0168] The state determination module is used to determine the third target state corresponding to the target event from a preset second protection state transition table when a target event occurs in the local primary member. The second protection state transition table is used to describe the transition relationship between the event request and the state in the non-load mode. Each state has a corresponding request signal. The target event is any one of the following events: signal degradation event, signal failure event, lock activation control command event, lock inactivation control command event, waiting recovery time timeout event, manual activation event, and manual inactivation event.

[0169] The state control module is used to control the local primary member to be in the third target state and to control the activation state of the local target member and the local backup member based on the third target state;

[0170] The state determination module is further configured to determine the fourth target state from the second protection state transition table based on the request signal of the third target state. The state control module is further configured to control the primary member of the peer end to be in the fourth target state and control the activation state of the primary member and the backup member of the peer end based on the fourth target state, so as to realize LAG protection switching.

[0171] Furthermore, in one embodiment, if the target event is a signal degradation event, the third target state is a primary member signal degradation state, and its service carrying state is that the primary member is not activated and the backup member is activated; the fourth target state is a no-request inactive state, and its service carrying state is that the primary member is not activated and the backup member is activated.

[0172] Furthermore, in one embodiment, if the target event is a signal failure event, the third target state is the primary member signal failure state, and its service carrying state is that the primary member is not activated and the backup member is activated; the fourth target state is the no-request inactive state, and its service carrying state is that the primary member is not activated and the backup member is activated.

[0173] Furthermore, in one embodiment, if the target event is a lock activation control command event, the third target state is a lock activation state, in which the primary member is activated and the backup member is not activated, and the fourth target state is a no-request state, in which the primary member is activated and the backup member is not activated.

[0174] Furthermore, in one embodiment, if the target event is a lock-in-inactivation control instruction event, the third target state is a lock-in-inactivation state, and its service carrying state is that the primary member is not activated and the backup member is activated; the fourth target state is a no-request-inactivation state, and its service carrying state is that the primary member is not activated and the backup member is activated.

[0175] Furthermore, in one embodiment, if the target event is a waiting recovery timeout event, the third target state is a waiting recovery state, in which the primary member is not activated and the backup member is activated; the fourth target state is a no-request inactive state, in which the primary member is not activated and the backup member is activated.

[0176] Furthermore, in one embodiment, if the target event is a manually activated event, the third target state is a manually activated state, in which the primary member is activated and the backup member is not activated; the fourth target state is a no-request state, in which the primary member is activated and the backup member is not activated.

[0177] Furthermore, in one embodiment, if the target event is a manually inactive event, the third target state is a manually inactive state, and its service carrying state is that the primary member is inactive and the backup member is active; the fourth target state is a no-request inactive state, and its service carrying state is that the primary member is inactive and the backup member is active.

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

[0179] Fifthly, embodiments of this application provide a LAG protection switching control device, which can be a personal computer (PC), laptop computer, server, or other device with data processing capabilities.

[0180] Reference Figure 19 , Figure 19 This is a schematic diagram of the hardware structure of the LAG protection switching control device involved in the embodiments of this application. In the embodiments of this application, the LAG protection switching control device may include a processor, a memory, a communication interface, and a communication bus.

[0181] The communication bus can be of any type and is used to interconnect the processor, memory, and communication interface.

[0182] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting devices within the LAG protection switching control equipment, as well as interfaces used for interconnecting the LAG protection switching control equipment with other devices (such as other computing devices or user equipment). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user equipment can be displays, keyboards, etc.

[0183] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0184] The processor can be a general-purpose processor, which can call the LAG protection switching control program stored in memory and execute the LAG protection switching control method provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the LAG protection switching control program is called can be referred to in the various embodiments of the LAG protection switching control method of this application, and will not be repeated here.

[0185] Those skilled in the art will understand that Figure 19 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0186] Sixthly, embodiments of this application also provide a computer-readable storage medium.

[0187] The present application has a readable storage medium storing an LAG protection switching control program, wherein when the LAG protection switching control program is executed by a processor, it implements the steps of the LAG protection switching control method as described above.

[0188] The method implemented when the LAG protection switching control program is executed can be referred to in various embodiments of the LAG protection switching control method of this application, and will not be repeated here.

[0189] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0190] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.

[0191] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.

[0192] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0193] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they 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.

[0194] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.

[0195] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A LAG protection switchover control method, characterized by, The members in the LAG communicate through the 802.3ad standard protocol, and the method is applied to the LAG in the load mode and includes the following steps. When a target event occurs in a target member, a first target state corresponding to the target event is determined from a preset first protection state migration table, the first protection state migration table is used to describe the migration relationship between an event request and a state in the load mode, each state has a corresponding request signal, and the target event is any one of a signal degradation event, a signal failure event, a lock activation control instruction event, a lock inactivation control instruction event, a waiting recovery time timeout end event, a manual activation event, and a manual inactivation event. The target member is controlled to be in the first target state, and an activation state of the target member is controlled based on the first target state. A second target state is determined from the first protection state migration table according to a request signal of the first target state, and the target member at the opposite end is controlled to be in the second target state, and an activation state of the target member at the opposite end is controlled based on the second target state, so as to realize LAG protection switching. If the target event is the signal degradation event, the first target state is the signal degradation state and the service bearing state thereof is the member inactivation, and the second target state is the no-request inactivation state and the service bearing state thereof is the member inactivation.

2. The LAG protection switchover control method of claim 1, wherein: If the target event is the signal failure event, the first target state is the signal failure state and the service bearing state thereof is the member inactivation, and the second target state is the no-request inactivation state and the service bearing state thereof is the member inactivation.

3. The LAG protection switching control method of claim 1, wherein: If the target event is the lock activation control instruction event, the first target state is the lock activation state and the service bearing state thereof is the member activation, and the second target state is the no-request state and the service bearing state thereof is the member activation.

4. The LAG protection switching control method of claim 1, wherein: If the target event is the lock inactivation control instruction event, the first target state is the lock inactivation state and the service bearing state thereof is the member inactivation, and the second target state is the no-request inactivation state and the service bearing state thereof is the member inactivation.

5. The LAG protection switching control method of claim 1, wherein: If the target event is the waiting recovery time timeout end event, the first target state is the waiting recovery and the service bearing state thereof is the member inactivation, and the second target state is the no-request inactivation state and the service bearing state thereof is the member inactivation.

6. The LAG protection switching control method of claim 1, wherein: If the target event is the manual activation event, the first target state is the manual activation state and the service bearing state thereof is the member activation, and the second target state is the no-request state and the service bearing state thereof is the member activation.

7. The LAG protection switching control method of claim 1, wherein: If the target event is the manual inactivation event, the first target state is the manual inactivation state and the service bearing state thereof is the member inactivation, and the second target state is the no-request inactivation state and the service bearing state thereof is the member inactivation.

8. A LAG protection switchover control device characterized by comprising: The members in the LAG communicate through the 802.3ad standard protocol, and the device is applied to the LAG in the load mode and includes a state determination module and a state control module. The state determining module is configured to determine a first target state corresponding to the target event from a preset first protection state migration table when a target event occurs in the local target member, the first protection state migration table being configured to describe migration relationships between event requests and states in a load mode, each state having a request signal corresponding thereto, the target event being any one of a signal degradation event, a signal failure event, a lock activation control instruction event, a lock inactivation control instruction event, a waiting recovery time timeout end event, a manual activation event and a manual inactivation event; The state control module is configured to control the local target member to be in the first target state and control activation states of the local target member based on the first target state; The state determining module is further configured to determine a second target state from the first protection state migration table according to the request signal of the first target state, and the state control module is further configured to control the opposite target member to be in the second target state and control activation states of the opposite target member based on the second target state, so as to realize LAG protection switching. If the target event is a signal degradation event, the first target state is a signal degradation state and its service bearing state is member inactivation, and the second target state is a no-request inactivation state and its service bearing state is member inactivation.

9. A LAG protection switchover control method characterized by comprising: The members in the LAG communicate through the 802.3ad standard protocol, and the method is applied to the LAG in a non-load mode and includes the following steps: When a target event occurs in the local primary member, a third target state corresponding to the target event is determined from a preset second protection state migration table, the second protection state migration table being configured to describe migration relationships between event requests and states in a non-load mode, each state having a request signal corresponding thereto, the target event being any one of a signal degradation event, a signal failure event, a lock activation control instruction event, a lock inactivation control instruction event, a waiting recovery time timeout end event, a manual activation event and a manual inactivation event; The state control module is configured to control the local target member to be in the first target state and control activation states of the local target member based on the first target state; The state determining module is further configured to determine a second target state from the first protection state migration table according to the request signal of the first target state, and the state control module is further configured to control the opposite target member to be in the second target state and control activation states of the opposite target member based on the second target state, so as to realize LAG protection switching. If the target event is a signal degradation event, the first target state is a signal degradation state and its service bearing state is member inactivation, and the second target state is a no-request inactivation state and its service bearing state is member inactivation.

10. The LAG protection switchover control method of claim 9, wherein: If the target event is a signal failure event, the third target state is a primary member signal failure state and its service bearing state is primary member inactivation and backup member activation, and the fourth target state is a no-request inactivation state and its service bearing state is primary member inactivation and backup member activation.

11. The LAG protection switchover control method of claim 9, wherein: If the target event is a lock activation control instruction event, the third target state is a lock activation state, the service bearer state of which is a master member activation and a standby member inactivation, and the fourth target state is a no request state, the service bearer state of which is a master member activation and a standby member inactivation.

12. The LAG protection switchover control method of claim 9, wherein: If the target event is a lock inactivation control instruction event, the third target state is a lock inactivation state, the service bearer state of which is a master member inactivation and a standby member activation, and the fourth target state is a no request inactivation state, the service bearer state of which is a master member inactivation and a standby member activation.

13. The LAG protection switchover control method of claim 9, wherein: If the target event is a waiting recovery time timeout end event, the third target state is a waiting recovery state, the service bearer state of which is a master member inactivation and a standby member activation, and the fourth target state is a no request inactivation state, the service bearer state of which is a master member inactivation and a standby member activation.

14. The LAG protection switchover control method of claim 9, wherein: If the target event is a manual activation event, the third target state is a manual activation state, the service bearer state of which is a master member activation and a standby member inactivation, and the fourth target state is a no request state, the service bearer state of which is a master member activation and a standby member inactivation.

15. The LAG protection switchover control method of claim 9, wherein: If the target event is a manual inactivation event, the third target state is a manual inactivation state, the service bearer state of which is a master member inactivation and a standby member activation, and the fourth target state is a no request inactivation state, the service bearer state of which is a master member inactivation and a standby member activation.

16. A LAG protection switchover control device characterized by comprising: The members in the LAG communicate through the 802.3ad standard protocol, and the device is applied to the LAG in a non-load mode and includes a state determining module and a state control module. The state determining module is configured to determine a third target state corresponding to a target event from a preset second protection state migration table when a master member at a local end has the target event, the second protection state migration table is used to describe a migration relationship between an event request and a state in the non-load mode, each state has a request signal corresponding thereto, and the target event is any one of a signal degradation event, a signal failure event, a lock activation control instruction event, a lock inactivation control instruction event, a waiting recovery time timeout end event, a manual activation event, and a manual inactivation event. The state control module is configured to control the master member at the local end to be in the third target state and control activation states of the master member at the local end and a standby member at the local end based on the third target state. The state determining module is further configured to determine a fourth target state from the second protection state migration table according to a request signal of the third target state, and the state control module is further configured to control a master member at a peer end to be in the fourth target state and control activation states of the master member at the peer end and a standby member at the peer end based on the fourth target state, so as to realize LAG protection switching. If the target event is a signal degradation event, the third target state is a primary member signal degradation state, and the service bearer state thereof is a primary member inactivation and a backup member activation, and the fourth target state is a no request inactivation state, and the service bearer state thereof is a primary member inactivation and a backup member activation.

17. A LAG protection switchover control device characterized by comprising: The LAG protection switching control device comprises a processor, a memory, and a LAG protection switching control program stored in the memory and executable by the processor, wherein the LAG protection switching control program, when executed by the processor, implements the steps of the LAG protection switching control method according to any one of claims 1 to 7 and 9 to 15.

18. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a LAG protection switching control program, wherein the LAG protection switching control program, when executed by the processor, implements the steps of the LAG protection switching control method according to any one of claims 1 to 7 and 9 to 15.

Images