Interface configuration method and apparatus

Abstract

The application relates to the technical field of network communication, in particular to an interface configuration method. The method comprises the following steps: creating an M-LAG group, creating a first aggregation interface on a first Leaf, creating a second aggregation interface on a second Leaf, and creating a third aggregation interface on a target Access; adding a downlink port connected with the target Access on the first Leaf to the first aggregation interface, adding a downlink port connected with the target Access on the second Leaf to the second aggregation interface, and adding uplink ports connected with the first Leaf and the second Leaf respectively on the target Access to the third aggregation interface; and adding the first aggregation interface, the second aggregation interface and the third aggregation interface to the M-LAG group, wherein when detecting that a peer end is an aggregation interface and belongs to the same M-LAG group as itself, the first aggregation interface, the second aggregation interface and the third aggregation interface activate a traffic forwarding function of the aggregation interface.

Description

Technical Field

[0001] This application relates to the field of network communication technology, and in particular to an interface configuration method and apparatus. Background Technology

[0002] In a campus network scenario, the networking environment typically consists of three layers: Spine, Leaf, and Access. Spine usually serves as the core layer for data forwarding, Leaf devices serve as the aggregation layer, responsible for wired user authentication and wired / wireless user data forwarding control and policy control, and Access devices serve as the access layer, mainly acting as access devices for directly connected wired users and wireless APs.

[0003] As campus networks grow larger, users have increasingly higher requirements for network stability. Currently, campus networks mainly use M-LAG or stacking to ensure high reliability. Because campus networks are managed in-band, meaning that network management and control information and user network service information are transmitted through the same logical channel, loops often occur during network interface configuration, leading to configuration failures.

[0004] Currently, regarding the connection between two Leaf devices and one Access device, when configuring the M-LAG interface, firstly, an aggregation port is created, and the uplink port on the Access device connected to the Leaf device is added to the aggregation port. Then, the downlink port on one Leaf device connected to the Access device is added to the aggregation port. If the configuration is successful, the downlink port on the other Leaf device connected to the Access device is added to the aggregation port. If the configuration is successful, the configuration is considered successful.

[0005] The current configuration method, while avoiding loops, is complex and inefficient. The configuration of each device is sequential, and if errors such as network management software restarts occur during the configuration process, the configuration must start from the beginning if the last device has not been configured. Summary of the Invention

[0006] This application provides an interface configuration method and apparatus to solve the problems of complex configuration process and low configuration efficiency in the prior art.

[0007] In a first aspect, this application provides an interface configuration method applied to an M-LAG system, the M-LAG system including a first Leaf device and a second Leaf device, a target Access device being physically connected to the first Leaf device and the second Leaf device, the method comprising:

[0008] Create an M-LAG group, create a first aggregation interface on the first Leaf device, create a second aggregation interface on the second Leaf device, and create a third aggregation interface on the target Access device;

[0009] Add the downlink port on the first Leaf device connected to the target Access device to the first aggregation interface; add the downlink port on the second Leaf device connected to the target Access device to the second aggregation interface; add the uplink ports on the target Access device connected to the first Leaf device and the second Leaf device respectively to the third aggregation interface.

[0010] The first aggregation interface, the second aggregation interface, and the third aggregation interface are added to the M-LAG group. When the first aggregation interface, the second aggregation interface, and the third aggregation interface detect that the peer is an aggregation interface and belongs to the same M-LAG group as themselves, the traffic forwarding function of the aggregation interface is activated.

[0011] Optionally, the method further includes:

[0012] The first aggregation interface, the second aggregation interface, and the third aggregation interface are set as aggregation edge interfaces. After being set as aggregation edge interfaces, if the first aggregation interface, the second aggregation interface, and the third aggregation interface detect that the peer is an aggregation interface and belongs to the same M-LAG group as themselves, the traffic forwarding function of the aggregation interface is activated.

[0013] Optionally, when the first aggregation interface detects that the peer is the third aggregation interface based on the Link Aggregation Control Protocol (LACP) and the third aggregation interface belongs to the same M-LAG group as itself, the first aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0014] When the second aggregation interface detects that the peer is the third aggregation interface based on LACP, and the third aggregation interface belongs to the same M-LAG group as itself, the second aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0015] When the third aggregation interface detects that the peer is the first aggregation interface and the second aggregation interface based on LACP, and the first aggregation interface and the second aggregation interface belong to the same M-LAG group as itself, the third aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0016] Secondly, this application provides an interface configuration device for an M-LAG system, the M-LAG system including a first Leaf device and a second Leaf device, a target Access device being physically connected to the first Leaf device and the second Leaf device, the device comprising:

[0017] A creation unit is used to create an M-LAG group, create a first aggregation interface on the first Leaf device, create a second aggregation interface on the second Leaf device, and create a third aggregation interface on the target Access device;

[0018] The first adding unit is used to add the downlink port on the first Leaf device connected to the target Access device to the first aggregation interface, add the downlink port on the second Leaf device connected to the target Access device to the second aggregation interface, and add the uplink ports on the target Access device connected to the first Leaf device and the second Leaf device respectively to the third aggregation interface;

[0019] The second adding unit is used to add the first aggregation interface, the second aggregation interface and the third aggregation interface to the M-LAG group, wherein the first aggregation interface, the second aggregation interface and the third aggregation interface activate the traffic forwarding function of the aggregation interface when they detect that the peer is an aggregation interface and belongs to the same M-LAG group as themselves.

[0020] Optionally, the device further includes:

[0021] The setting unit is used to set the first aggregation interface, the second aggregation interface and the third aggregation interface as aggregation edge interfaces. After the first aggregation interface, the second aggregation interface and the third aggregation interface are set as aggregation edge interfaces, if the peer is detected to be an aggregation interface and belongs to the same M-LAG group as itself, the traffic forwarding function of the aggregation interface is activated.

[0022] Optionally, when the first aggregation interface detects that the peer is the third aggregation interface based on the Link Aggregation Control Protocol (LACP) and the third aggregation interface belongs to the same M-LAG group as itself, the first aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0023] When the second aggregation interface detects that the peer is the third aggregation interface based on LACP, and the third aggregation interface belongs to the same M-LAG group as itself, the second aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0024] When the third aggregation interface detects that the peer is the first aggregation interface and the second aggregation interface based on LACP, and the first aggregation interface and the second aggregation interface belong to the same M-LAG group as itself, the third aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0025] Thirdly, embodiments of this application provide an interface configuration device, which includes:

[0026] Memory, used to store program instructions;

[0027] A processor is configured to invoke program instructions stored in the memory and execute the steps of the method as described in any one of the first aspects above, according to the obtained program instructions.

[0028] Fourthly, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the steps of the method as described in any of the first aspects above.

[0029] In summary, the interface configuration method provided in this application is applied to an M-LAG system, which includes a first Leaf device and a second Leaf device. A target Access device is physically connected to the first Leaf device and the second Leaf device. The method includes: creating an M-LAG group; creating a first aggregation interface on the first Leaf device; creating a second aggregation interface on the second Leaf device; and creating a third aggregation interface on the target Access device; adding the downlink port on the first Leaf device connected to the target Access device to the first aggregation interface; adding the downlink port on the second Leaf device connected to the target Access device to the second aggregation interface; adding the uplink ports on the target Access device connected to the first Leaf device and the second Leaf device to the third aggregation interface; and adding the first aggregation interface, the second aggregation interface, and the third aggregation interface to the M-LAG group. When the first aggregation interface, the second aggregation interface, and the third aggregation interface detect that the peer is an aggregation interface and belongs to the same M-LAG group, the traffic forwarding function of the aggregation interface is activated.

[0030] Using the interface configuration method provided in this application, the gateway software can configure both Leaf devices and Access devices simultaneously. This eliminates the need to configure one device successfully before configuring the other, simplifying the configuration process and improving configuration efficiency. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments of this application or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings of the embodiments of this application.

[0032] Figure 1 A detailed flowchart of an interface configuration method provided in an embodiment of this application;

[0033] Figure 2 This is a schematic diagram illustrating an interface configuration process provided in an embodiment of this application.

[0034] Figure 3 This is a schematic diagram of the structure of an interface configuration device provided in an embodiment of this application;

[0035] Figure 4 This is a schematic diagram of another interface configuration device provided in an embodiment of this application. Detailed Implementation

[0036] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “the,” and “the” as used in this application and claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to any and all possible combinations comprising one or more of the associated listed items.

[0037] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" may also be interpreted as "when," "when," or "in response to a determination."

[0038] For example, see Figure 1 The diagram shown is a detailed flowchart of an interface configuration method provided in an embodiment of this application. This method is applied to an M-LAG system, which includes a first Leaf device and a second Leaf device. A target Access device is physically connected to the first Leaf device and the second Leaf device. The method includes the following steps:

[0039] Step 100: Create an M-LAG group, create a first aggregation interface on the first Leaf device, create a second aggregation interface on the second Leaf device, and create a third aggregation interface on the target Access device.

[0040] In this embodiment, an M-LAG system consisting of two Leaf devices is pre-created using gateway software. Gateway software refers to a software platform that manages network devices, switches, and routers. Then, a virtual M-LAG group is created in the network management software interface, with a virtual first aggregation interface created on the first Leaf device, a virtual second aggregation interface created on the second Leaf device, and a virtual third aggregation interface created on the target Access device physically connected to the first and second Leaf devices.

[0041] For example, Leaf1 and Leaf2 form an M-LAG system. Access device 1 is physically connected to Leaf2 and Leaf2. Specifically, Leaf2's downlink port 1 is physically connected to Access device's uplink port 1, and Leaf2's downlink port 2 is physically connected to Access device's uplink port 2. After creating a virtual M-LAG group through the gateway software, a virtual aggregation interface 1 is created on Leaf2, a virtual aggregation interface 2 is created on Leaf2, and a virtual aggregation interface 3 is created on Access device.

[0042] Step 110: Add the downlink port on the first Leaf device connected to the target Access device to the first aggregation interface; add the downlink port on the second Leaf device connected to the target Access device to the second aggregation interface; add the uplink ports on the target Access device connected to the first Leaf device and the second Leaf device respectively to the third aggregation interface.

[0043] For example, add the downlink port 1 of Leaf device 1 to virtual aggregation interface 1, add the downlink port 2 of Leaf device 1 to virtual aggregation interface 2, and add the uplink port 1 and uplink port 2 of Access device to virtual aggregation interface 3.

[0044] Furthermore, in this embodiment of the application, the above-mentioned interface configuration method may further include the following steps:

[0045] The first aggregation interface, the second aggregation interface, and the third aggregation interface are set as aggregation edge interfaces. After being set as aggregation edge interfaces, if the first aggregation interface, the second aggregation interface, and the third aggregation interface detect that the peer is an aggregation interface and belongs to the same M-LAG group as themselves, the traffic forwarding function of the aggregation interface is activated.

[0046] Specifically, by issuing configuration instructions (e.g., LACP Edge-port) to the first Leaf device, the second Leaf device, and the target Access device, the first aggregation interface created on the first Leaf device, the second aggregation interface created on the second Leaf device, and the third aggregation interface created on the target Access device are configured as aggregated edge interfaces.

[0047] In practical applications, an aggregated interface, after being configured as an aggregated edge interface, is in an inactive state, meaning its own traffic forwarding function is not activated. Its traffic forwarding function will only be activated when it detects that the peer interface is an aggregated interface and belongs to the same aggregation group.

[0048] Step 120: Add the first aggregation interface, the second aggregation interface and the third aggregation interface to the M-LAG group, wherein the first aggregation interface, the second aggregation interface and the third aggregation interface activate the traffic forwarding function of the aggregation interface when they detect that the peer is an aggregation interface and belongs to the same M-LAG group as themselves.

[0049] In this embodiment of the application, when the first aggregation interface detects that the peer is the third aggregation interface based on the Link Aggregation Control Protocol (LACP) and the third aggregation interface belongs to the same M-LAG group as itself, the first aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0050] Similarly, when the second aggregation interface detects that the peer is the third aggregation interface based on LACP, and the third aggregation interface belongs to the same M-LAG group as itself, the second aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0051] Similarly, when the third aggregation interface detects that the peer is the first aggregation interface and the second aggregation interface based on LACP, and the first aggregation interface and the second aggregation interface belong to the same M-LAG group as itself, the third aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0052] For example, by sending configuration commands to Leaf device 1, Leaf device 2 and Access device through gateway software, the aggregation interface 1 created on Leaf device 1, the aggregation interface 2 created on Leaf device 2 and the aggregation interface 3 created on Access device will be added to the same M-LAG group, and each aggregation interface will be configured as an aggregation edge interface.

[0053] Thus, when aggregation interface 1 on Leaf device 1 detects through LACP that the peer is aggregation interface 3, and aggregation interface 3 and aggregation interface 1 belong to the same aggregation group, the connection between aggregation interface 1 and aggregation interface 3 is activated, the configuration of aggregation interface 1 takes effect, and its own traffic forwarding function is activated.

[0054] Similarly, when aggregation interface 2 on Leaf device 2 detects that the peer is aggregation interface 3 through LACP, and aggregation interface 3 and aggregation interface 2 belong to the same aggregation group, the connection between aggregation interface 2 and aggregation interface 3 is activated, the configuration of aggregation interface 2 takes effect, and its own traffic forwarding function is activated.

[0055] When the aggregation interface 3 on the target Access device detects through LACP that the peer is aggregation interface 1 and aggregation interface 2, and aggregation interface 3 belongs to the same aggregation group as aggregation interface 1 and aggregation interface 2, the connection relationship between aggregation interface 3 and aggregation interface 1 is activated, the configuration of aggregation interface 3 takes effect, and its own traffic forwarding function is activated.

[0056] In this embodiment, interface configurations can be sent to Leaf devices and Access devices simultaneously (in parallel). Each Leaf device and Access device configures its own aggregated interface. After each device completes its own aggregated interface configuration, it does not take effect immediately. Instead, it takes effect only when it detects that the other end has also completed its configuration (and the other end belongs to the same aggregate group as itself). That is, all aggregated interfaces take effect at the same time.

[0057] Of course, the above method can also be used to configure the interfaces of each device in the DRNI (Distributed Resilient Network Interconnect) system. In this embodiment, no specific limitations are made.

[0058] The interface configuration process provided in this application embodiment will be described in detail below with reference to specific application scenarios. For example, see [link to relevant documentation]. Figure 2 The diagram shown is a schematic representation of an interface configuration process provided in an embodiment of this application.

[0059] The administrator uses gateway software to create an M-LAG system consisting of Leaf1 and Leaf, with Access devices physically linked to both Leaf1 and Leaf2. Next, a cross-device port aggregation group is created. Simultaneously, DR port configurations are issued to Leaf1 and Leaf2, along with configurations for creating aggregation ports, adding physical interfaces connected to Access devices to the aggregation ports, and setting the created aggregation ports as edge ports. Also, configurations for creating aggregation ports are issued to Access devices, adding physical interfaces connected to Leaf1 and Leaf2 to the aggregation ports, and setting the created aggregation ports as edge ports. Since the aggregation ports created on Leaf and Access are configured as aggregation edge interfaces, each device can associate / activate the aggregation ports according to dynamic protocols.

[0060] For example, see Figure 3 The diagram shown is a structural schematic of an interface configuration device provided in an embodiment of this application. This device is applied to an M-LAG system, which includes a first Leaf device and a second Leaf device. A target Access device is physically connected to the first Leaf device and the second Leaf device. The device includes:

[0061] Creation unit 30 is used to create an M-LAG group, create a first aggregation interface on the first Leaf device, create a second aggregation interface on the second Leaf device, and create a third aggregation interface on the target Access device;

[0062] The first adding unit 31 is used to add the downlink port on the first Leaf device connected to the target Access device to the first aggregation interface, add the downlink port on the second Leaf device connected to the target Access device to the second aggregation interface, and add the uplink ports on the target Access device connected to the first Leaf device and the second Leaf device respectively to the third aggregation interface;

[0063] The second adding unit 32 is used to add the first aggregation interface, the second aggregation interface and the third aggregation interface to the M-LAG group, wherein the first aggregation interface, the second aggregation interface and the third aggregation interface activate the traffic forwarding function of the aggregation interface when they detect that the peer is an aggregation interface and belongs to the same M-LAG group as themselves.

[0064] Optionally, the device further includes:

[0065] The setting unit is used to set the first aggregation interface, the second aggregation interface and the third aggregation interface as aggregation edge interfaces. After the first aggregation interface, the second aggregation interface and the third aggregation interface are set as aggregation edge interfaces, if the peer is detected to be an aggregation interface and belongs to the same M-LAG group as itself, the traffic forwarding function of the aggregation interface is activated.

[0066] Optionally, when the first aggregation interface detects that the peer is the third aggregation interface based on the Link Aggregation Control Protocol (LACP) and the third aggregation interface belongs to the same M-LAG group as itself, the first aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0067] When the second aggregation interface detects that the peer is the third aggregation interface based on LACP, and the third aggregation interface belongs to the same M-LAG group as itself, the second aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0068] When the third aggregation interface detects that the peer is the first aggregation interface and the second aggregation interface based on LACP, and the first aggregation interface and the second aggregation interface belong to the same M-LAG group as itself, the third aggregation interface activates the traffic forwarding function of its own aggregation interface.

[0069] These units can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more digital signal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, when one of these units is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these units can be integrated together to form a system-on-a-chip (SOC).

[0070] Furthermore, regarding the interface configuration device provided in this application embodiment, from a hardware perspective, the hardware architecture diagram of the interface configuration device can be found in [reference needed]. Figure 4 As shown, the interface configuration device may include: a memory 40 and a processor 41.

[0071] The memory 40 is used to store program instructions; the processor 41 calls the program instructions stored in the memory 40 and executes the above method embodiment according to the obtained program instructions. The specific implementation method and technical effect are similar, and will not be described again here.

[0072] Optionally, this application also provides an interface configuration device, including at least one processing element (or chip) for performing the above method embodiments.

[0073] Optionally, this application also provides a program product, such as a computer-readable storage medium storing computer-executable instructions for causing the computer to perform the above-described method embodiments.

[0074] Here, a machine-readable storage medium can be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, etc. For example, a machine-readable storage medium can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drives (such as hard disk drives), solid-state drives, any type of storage disk (such as optical discs, DVDs, etc.), or similar storage media, or combinations thereof.

[0075] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0076] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0077] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0078] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0079] Furthermore, these computer program instructions can also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in the process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0080] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0081] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. An interface configuration method, characterized in that, Applied to an M-LAG system, the M-LAG system including a first Leaf device and a second Leaf device, a target Access device being physically connected to the first Leaf device and the second Leaf device, the method includes: Create an M-LAG group, create a first aggregation interface on the first Leaf device, create a second aggregation interface on the second Leaf device, and create a third aggregation interface on the target Access device; Add the downlink port on the first Leaf device connected to the target Access device to the first aggregation interface; add the downlink port on the second Leaf device connected to the target Access device to the second aggregation interface; add the uplink ports on the target Access device connected to the first Leaf device and the second Leaf device respectively to the third aggregation interface. The first aggregation interface, the second aggregation interface, and the third aggregation interface are added to the M-LAG group. When the first aggregation interface, the second aggregation interface, and the third aggregation interface detect that the peer is an aggregation interface and belongs to the same M-LAG group as themselves, they activate the traffic forwarding function of their own aggregation interfaces.

2. The method as described in claim 1, characterized in that, The method further includes: The first aggregation interface, the second aggregation interface, and the third aggregation interface are set as aggregation edge interfaces. After being set as aggregation edge interfaces, if the first aggregation interface, the second aggregation interface, and the third aggregation interface detect that the peer is an aggregation interface and belongs to the same M-LAG group as themselves, they activate the traffic forwarding function of their own aggregation interface.

3. The method as described in claim 2, characterized in that, When the first aggregation interface detects that the peer is the third aggregation interface based on the Link Aggregation Control Protocol (LACP) and the third aggregation interface belongs to the same M-LAG group as itself, the first aggregation interface activates the traffic forwarding function of its own aggregation interface. When the second aggregation interface detects that the peer is the third aggregation interface based on LACP, and the third aggregation interface belongs to the same M-LAG group as itself, the second aggregation interface activates the traffic forwarding function of its own aggregation interface. When the third aggregation interface detects that the peer is the first aggregation interface and the second aggregation interface based on LACP, and the first aggregation interface and the second aggregation interface belong to the same M-LAG group as itself, the third aggregation interface activates the traffic forwarding function of its own aggregation interface.

4. An interface configuration device, characterized in that, Applied to an M-LAG system, the M-LAG system including a first Leaf device and a second Leaf device, a target Access device physically connected to the first Leaf device and the second Leaf device, the device includes: A creation unit is used to create an M-LAG group, create a first aggregation interface on the first Leaf device, create a second aggregation interface on the second Leaf device, and create a third aggregation interface on the target Access device; The first adding unit is used to add the downlink port on the first Leaf device connected to the target Access device to the first aggregation interface, add the downlink port on the second Leaf device connected to the target Access device to the second aggregation interface, and add the uplink ports on the target Access device connected to the first Leaf device and the second Leaf device respectively to the third aggregation interface; The second adding unit is used to add the first aggregation interface, the second aggregation interface and the third aggregation interface to the M-LAG group, wherein the first aggregation interface, the second aggregation interface and the third aggregation interface activate the traffic forwarding function of their own aggregation interface when they detect that the peer is an aggregation interface and belongs to the same M-LAG group as themselves.

5. The apparatus as described in claim 4, characterized in that, The device further includes: The setting unit is used to set the first aggregation interface, the second aggregation interface and the third aggregation interface as aggregation edge interfaces. After the first aggregation interface, the second aggregation interface and the third aggregation interface are set as aggregation edge interfaces, if they detect that the peer is an aggregation interface and belongs to the same M-LAG group as themselves, they activate the traffic forwarding function of their own aggregation interface.

6. The apparatus as claimed in claim 5, characterized in that, When the first aggregation interface detects that the peer is the third aggregation interface based on the Link Aggregation Control Protocol (LACP) and the third aggregation interface belongs to the same M-LAG group as itself, the first aggregation interface activates the traffic forwarding function of its own aggregation interface. When the second aggregation interface detects that the peer is the third aggregation interface based on LACP, and the third aggregation interface belongs to the same M-LAG group as itself, the second aggregation interface activates the traffic forwarding function of its own aggregation interface. When the third aggregation interface detects that the peer is the first aggregation interface and the second aggregation interface based on LACP, and the first aggregation interface and the second aggregation interface belong to the same M-LAG group as itself, the third aggregation interface activates the traffic forwarding function of its own aggregation interface.

7. An interface configuration device, characterized in that, The interface configuration device includes: Memory, used to store program instructions; A processor is configured to invoke program instructions stored in the memory and execute the steps of the method as described in any one of claims 1-3 according to the obtained program instructions.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing the computer to perform the steps of the method as described in any one of claims 1-3.

Images