A method, device and equipment for automatically deploying M-lag group

Abstract

The present invention discloses a method, device and equipment for automatically deploying an M‑lag group. The method comprises: obtaining device information in a networking structure and link relationships between devices, including first access device information and link information; if it is determined according to the first access device information and link information that the first access device is single-homed to an M‑lag system, then determining a Leaf device in the M‑lag system to which the first access device is single-homed to access, and at least one link between the Leaf device and the first access device; configuring a link aggregation interface for the first access device and the Leaf device to create an M‑lag group corresponding to the first access device, and issuing a configuration command to the Leaf device to instruct the traffic received by the Leaf device through the link aggregation interface to be shared and processed by the M‑lag system. The method solves the problem that traffic accessed by a single-homed access device cannot be redundantly backed up and load shared.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method, device and equipment for automatically deploying an M-lag group. Background Art

[0002] Campus SDN (Software-defined Networking) is a new SDN network architecture deployed in campus networks. Figure 1 As shown in the figure, it includes a controller cluster, core layer, aggregation layer, and access layer. The Leaf switch in the aggregation layer is used as an authentication device, responsible for user terminal authentication, policy implementation, and traffic control. The M-lag system is used in the Leaf layer to perform redundant backup and load balancing for user traffic.

[0003] The number of access devices in the campus SDN network is generally in the hundreds or thousands, and each access device needs to be configured with an M-lag group. Currently, the SDN controller only supports manual deployment of M-LAG groups, which is complex to configure. In addition, for the Leaf devices that form the M-lag system through dual-homing of access devices, the controller generally selects the dual-homing link to join the aggregation group. Single-homed access devices cannot access Leaf devices through the M-lag system; access devices must be dual-homed before M-lag groups can be deployed. M-lag groups cannot be deployed for single-homed access devices, and they are still processed by directly connected Leaf devices, resulting in the inability to load balance the access user terminal traffic and there is no redundant backup. Summary of the invention

[0004] Therefore, an embodiment of the present invention provides a method for automatically deploying an M-lag group, the purpose of which is to solve the problem that a single-homed access device cannot be load balanced through the M-lag system in a campus SDN scenario. In order to solve this problem, the following technical solution is disclosed:

[0005] In a first aspect, an embodiment of the present invention provides a method for automatically deploying an M-lag group, which can be applied to a network controller, and the method includes:

[0006] Acquire device information in the networking structure and link relationships between devices, wherein the device information includes first access device information, and the link information includes link information connected to the first access device;

[0007] If it is determined, according to the first access device information and the link information, that the first access device is single-homed to the M-lag system, a Leaf device in the M-lag system that is single-homed to the first access device is determined, and at least one link between the Leaf device and the first access device;

[0008] configuring a link aggregation interface for the first access device and the Leaf device, aggregating the at least one link to the link aggregation interface, so as to create an M-lag group corresponding to the first access device;

[0009] A configuration command is issued to the Leaf device, where the configuration command is used to instruct the traffic received by the Leaf device through the link aggregation interface to be shared and processed by the M-lag system.

[0010] Optionally, in a possible implementation of the first aspect, the acquiring device information in the networking structure and the link relationship between the devices includes:

[0011] The device information of the networking structure is obtained by calling the Simple Network Management Protocol SNMP, wherein the device information includes: device model, device IP address, and interface number; based on the device model, the device IP address, and the interface number in the device information, the link relationship between the devices is obtained through link relationship calculation.

[0012] Optionally, in another possible implementation of the first aspect, determining that the first access device single-homed accesses the M-lag system includes:

[0013] Determine, according to the first access device information and the link information, whether the number of Leaf devices in all neighboring devices of the first access device is 1;

[0014] If yes, determining whether the neighbor Leaf device of the first access device is a device in the M-lag system;

[0015] If yes, it is determined that the first access device single-homedly accesses the M-lag system.

[0016] Optionally, in another possible implementation of the first aspect, the method further includes: if it is determined that the neighbor Leaf device of the first access device is not a device in the M-lag system, determining that the first access device is not single-homed to the M-lag system.

[0017] Optionally, in another possible implementation of the first aspect, after aggregating the at least one link to the link aggregation interface, it also includes: displaying the created M-lag group, the first access device information and the aggregated link aggregation interface information in a preset form.

[0018] In a second aspect, an embodiment of the present invention further discloses a device for automatically deploying an M-lag group, the device comprising:

[0019] An acquisition unit, configured to acquire device information in a networking structure and link relationships between devices, wherein the device information includes first access device information, and the link information includes link information connected to the first access device;

[0020] a determining unit, configured to determine, if it is determined according to the first access device information and the link information that the first access device single-homedly accesses the M-lag system, a Leaf device in the M-lag system to which the first access device single-homedly accesses, and at least one link between the Leaf device and the first access device;

[0021] A configuration unit, configured to configure a link aggregation interface for the first access device and the Leaf device, and aggregate the at least one link to the link aggregation interface to create an M-lag group corresponding to the first access device;

[0022] The sending unit is used to send a configuration command to the Leaf device, where the configuration command is used to instruct the traffic received by the Leaf device through the link aggregation interface to be shared and processed by the M-lag system.

[0023] Optionally, in a possible implementation of the second aspect, the acquisition unit is specifically used to obtain device information of the networking structure by calling SNMP, the device information including: device model, device IP address, interface number; and based on the device model, the device IP address and the interface number in the device information, obtain the link relationship between the devices through link relationship calculation.

[0024] Optionally, in another possible implementation of the second aspect, the determination unit is specifically used to: determine whether the number of Leaf devices among all neighbor devices of the first access device is 1 based on the first access device information and the link information; if so, determine whether the neighbor Leaf device of the first access device is a device in the M-lag system; if so, determine that the first access device is single-homed to the M-lag system.

[0025] In the third aspect, an embodiment of the present invention further discloses an electronic device, comprising a processor and a memory; wherein the memory is coupled to the processor, and computer-readable program instructions are stored on the memory. When the instructions are executed by the processor, the method for automatically deploying the M-lag group as described in the first aspect or any embodiment of the first aspect is implemented.

[0026] In a fourth aspect, an embodiment of the present invention further discloses a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the method for automatically deploying an M-lag group as described in the first aspect or any embodiment of the first aspect is implemented.

[0027] In addition, a computer program product is also provided, including computer program instructions. When the computer program instructions are executed by a processor, the method for automatically deploying an M-lag group as described in the first aspect or any embodiment of the first aspect is implemented.

[0028] The method and apparatus for automatically deploying an M-lag group provided in this embodiment determine whether the current device is single-homed to the M-lag system through access device information and link information, then aggregate the single-homed access device and the Leaf device in the M-lag system, configure the link aggregation interface, and issue a configuration command, thereby creating an M-lag group corresponding to the access device, and the traffic accessed by the link aggregation interface of the M-lag system is load-shared by the M-lag system to the two Leaf devices of the M-lag system for processing and forwarding according to the MAC and IP parity of the terminal device, thereby solving the problem that the traffic accessed by the single-homed access device cannot be redundantly backed up and load-shared.

[0029] In addition, this method detects device information and link relationships through SNMP, and automatically deploys the M-lag group with one click, which simplifies deployment complexity and improves deployment efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0031] Figure 1 A networking diagram of a campus SDN architecture provided by the present invention;

[0032] Figure 2A networking diagram of dual-homing access of access devices to an M-lag system in a campus SDN provided by an embodiment of the present invention;

[0033] Figure 3 A networking diagram of a single-homed access to an M-lag system of an access device in a campus SDN provided by an embodiment of the present invention;

[0034] Figure 4 A flowchart of a method for automatically deploying an M-lag group provided by an embodiment of the present invention;

[0035] Figure 5 A schematic diagram of configuring an M-lag system for a single-homed access device provided by an embodiment of the present invention;

[0036] Figure 6 A flowchart for determining that a first access device is a single-homed access M-lag system provided by an embodiment of the present invention;

[0037] Figure 7 A flowchart of another method for automatically deploying an M-lag group provided by an embodiment of the present invention;

[0038] Figure 8 A structural block diagram of an automatic deployment M-lag group device provided by an embodiment of the present invention;

[0039] Fig. 9 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0040] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present application and to make the above-mentioned purposes, features and advantages of the embodiments of the present application more obvious and understandable, the technical solutions in the embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0041] Before describing the technical solution of the embodiment of the present application, the application scenario of the embodiment of the present application is first described in conjunction with the accompanying drawings. The technical solution of the present application can be applied to the SDN network architecture, such as Figure 1 The figure shows a campus SDN architecture network diagram. In this SDN campus scenario, centralized management of devices and rapid deployment of SDN controllers can be achieved.

[0042] The network layers are: controller cluster, core layer, aggregation layer and access layer. The M-lag system is located in the aggregation layer and is connected to the access device of the next access layer.

[0043] M-lag (Multichassis Link Aggregation Group) provides a cross-device link aggregation technology. M-lag improves the reliability of the link from the single-board level to the device level by performing cross-device link aggregation with the user-side device or server in the same state between two access switches. At the same time, since M-LAG devices can be upgraded separately, the stability of business traffic is guaranteed, making M-lag technology widely used in data center networks.

[0044] Access device or access network element: access device in the campus SDN scenario, which can be classified as an M-lag system consisting of access leaf or dual access leaf.

[0045] The M-lag system contains two M-lag devices (such as device 1 and device 2). In other words, the aggregation groups of these two devices belong to one M-lag group. The two devices perform mutual keepalive detection and are connected by a peer-link link. The peer-link link is a direct aggregation link between the two devices that deploy M-lag. It is used to exchange protocol messages and transmit part of the traffic to ensure the normal operation of M-lag. The M-lag system connects device 1 and device 2 through a peer-link link and performs link aggregation negotiation with the switch in the same state, thereby improving the link reliability from the single-board level to the device level.

[0046] There are two ways for access devices to access the M-lag system. One is dual-homing access, such as Figure 2 As shown in the figure, access device 2 (such as a switch Switch) has links with both devices in the M-lag system (assuming device 1 and device 2). The other is single-homing access, that is, access device 1 is only connected to one device in the M-lag system (such as device 1), such as Figure 3 shown.

[0047] The embodiment of the present invention provides a method for deploying an M-lag group in a single-homed access access device, using an M-lag system unilateral access protocol to ensure that after the single-homed access access device deploys the M-lag group, the traffic can normally access the M-lag system of the Leaf device, thereby achieving load balancing.

[0048] Specifically, see Figure 4 , a method for automatically deploying an M-lag group provided in this embodiment, the method can be applied to a network controller, such as a campus controller (referred to as “controller”) in a controller cluster, etc., and the method includes the following steps:

[0049] Step 101, obtaining device information in a networking structure and link relationships between devices, wherein the device information includes first access device information, and the link information includes link information connected to the first access device.

[0050] Specifically, a possible implementation method is that the controller obtains the device information of the network structure by calling the Simple Network Management Protocol (SNMP), and the device information includes: device model, device IP address, and interface number. For example, the controller calls its internal SNMP module to obtain the topology of the network, including the device information of each device. By calling SNMP, all network devices that support the SNMP protocol can be remotely managed and the device information of these devices can be obtained.

[0051] Then, the link relationship between the devices is obtained through link relationship calculation according to the device model, the device IP address and the interface number in the device information.

[0052] Specifically, the controller can use the M-lag system module, input the device information in the previous step, and calculate the link relationship between the devices, which includes: single-home access devices and their links, dual-home access devices and the link relationship between them, such as Figure 5 As shown, an access device is dual-homed to the M-lag system through link 1 and link 2.

[0053] Further, in step 101, a single-homing access link information table may be generated according to the single-homing access device and link information, and a dual-homing access link information table may be generated according to the dual-homing access device and its link information. This embodiment mainly focuses on the single-homing access link information table.

[0054] Table 1: Single-homed access link information table

[0055]

[0056] For example, Table 1 involves Leaf device 1 and Leaf device 2 in the M-lag group, and also includes the first access device in the single-homed access M-lag group. Therefore, the link information table contains the name, IP address, ID, interface number of Leaf device 1 and Leaf device 2, as well as the device name, device IP address, device ID and interface number of the first access device.

[0057] Step 102: Determine whether the first access device is a single-homed access M-lag system according to the first access device information and the link information.

[0058] Step 103: If yes, that is, it is determined that the first access device is single-homed to the M-lag system, a Leaf device to which the first access device is single-homed in the M-lag system and at least one link between the Leaf device and the first access device are determined.

[0059] Specifically, according to the link information of the first access device, for example, the first access device is connected to Leaf device 1 in the M-lag system, it is determined that the Leaf device that is single-homed to the first access device is "Leaf device 1"; and there are N links between Leaf device 1 and the first access device, and the N links can be connected through N interfaces, where N≥1 and is a positive integer.

[0060] In one example, assuming that N=2, the first link is a link between the first interface of Leaf device 1 and the first interface of the first access device; the second link is a link between the second interface of Leaf device 1 and the second interface of the first access device. After determining that the first access device is a device that is single-homed to the M-lag system, the two links connected between the first access device and Leaf device 1 are determined according to the link information in Table 1.

[0061] Step 104: configure a link aggregation interface for the first access device and the Leaf device, aggregate the at least one link to the link aggregation interface, and create an M-lag group corresponding to the first access device.

[0062] Specifically, a link aggregation interface, such as Bagg1 (Bridge-Aggregation1), is created on Leaf device 1, and the first interface and the second interface of the Leaf device 1 are added to the aggregation interface Bagg1; similarly, a logical aggregation interface Bagg1 is also created on the first access device, and the first interface and the second interface of the first access device are added to the aggregation interface Bagg1, ​​so that the two links appear to be one link connected through the Bagg1 interface. This process is called "link aggregation" or "port aggregation".

[0063] Step 105: Send a configuration command to the Leaf device, where the configuration command is used to instruct the traffic received by the Leaf device through the link aggregation interface to be shared and processed by the M-lag system.

[0064] The controller sends the configuration command "Allow unilateral access to the M-lag system" to the aggregation interface Bagg1 of the two devices, and creates two aggregation interfaces Bagg1 to join an M-lag group. In addition, the configuration command is used to instruct Leaf device 1 that all traffic received through the Bagg1 interface is processed by the load balancing unit in the entire M-lag system to avoid load sharing and traffic forwarding by a single Leaf device. The load balancing unit is connected to the two devices in the M-lag system to coordinate the deployment of M-lag system traffic, forwarding, and redundant backup.

[0065] The method for automatically deploying an M-lag group provided in this embodiment determines whether the current device is single-homed to the M-lag system through access device information and link information, then aggregates the single-homed access device and the Leaf device in the M-lag system, configures the link aggregation interface, and issues a configuration command, thereby creating an M-lag group corresponding to the access device. The traffic accessed by the link aggregation interface of the M-lag system is then load-shared by the M-lag system to the two Leaf devices of the M-lag system for processing and forwarding according to the MAC and IP parity of the terminal device, thereby solving the problem that the traffic accessed by the single-homed access device cannot be redundantly backed up and load-shared.

[0066] In addition, in the campus SDN scenario, this method detects device information and link relationships through SNMP, and automatically deploys the M-lag group with one click, which simplifies the deployment complexity and improves the deployment efficiency.

[0067] Optional, such as Figure 6 As shown, in a specific implementation, the above step 102 specifically includes:

[0068] Step 102-1: According to the first access device information and link information, determine whether the number of Leaf devices in all neighboring devices of the first access device is 1. In other words, determine whether the first access device is single-homed to one Leaf device.

[0069] Specifically, when the controller is networking, it obtains all neighbor devices in the M-lag system in advance, including all Leaf devices and access devices, so as to determine whether the number of all neighbor devices of the first access device is 1. For example, the number of Leaf devices connected to the first access device is determined according to the link information.

[0070] Step 102-2: If yes, further determine whether the neighboring Leaf device of the first access device is a device in the M-lag system.

[0071] One implementation method is that the controller sends a request command to the Leaf device determined in step 102-1. After the Leaf device receives the request command sent by the controller, it feeds back a response to the controller. If the controller receives the response fed back by the Leaf device within a certain period of time, it is determined that the Leaf device is a device in the M-lag system; if no response is received, it is determined that the Leaf device is not a device in the M-lag system.

[0072] Alternatively, another implementation method may be to carry a preset field in the response fed back by the Leaf device, and when the controller detects that the response contains the content of the preset field, it is determined that the Leaf device is a device in the M-lag system; otherwise, it is determined that the Leaf device is not a device in the M-lag system. The content of the preset field can be agreed upon by the controller and the Leaf device during system configuration, and this embodiment does not limit the specific content of the agreement.

[0073] If the result of step 102-1 is "No", that is, there are two or more Leaf devices connected to the first access device, it means that the first access device is not single-homed to the M-lag system, but may be dual-homed to the M-lag system. At this time, end this process and re-acquire other access devices.

[0074] Step 102-3: If the judgment result of step 102-2 is "yes", it is determined that the first access device is single-homed to the M-lag system. At this time, link aggregation is prepared and an M-lag group corresponding to the first access device is created.

[0075] In addition, the method further includes step 102-4.

[0076] Step 102-4: If the neighboring Leaf device of the first access device is not a device in the M-lag system, it is determined that the first access device is not single-homed to the M-lag system, for example, it may be dual-homed to the M-lag system.

[0077] This embodiment determines whether the current first access device is single-homed to the M-lag system through the first access device information and the link information of the device, paving the way for link aggregation and automatic deployment of the M-lag group after subsequent devices are single-homed.

[0078] Optionally, in the above step 104, after aggregating the at least one link to the link aggregation interface, the method further includes: displaying the created M-lag group, the first access device information and the aggregated link aggregation interface information in a preset form.

[0079] For example, the information of the M-lag group, the device information of the first access device and its link information are displayed to the user in a preview table through a web client, so that the user can understand the single-homing deployment result, as well as the traffic monitoring and forwarding after deployment.

[0080] The method provided in this embodiment discovers link information through the controller and converts the single-homed access link (such as Figure 5 When the link 1) device sends the aggregation group, it is configured to access the M-lag system on one side; Figure 5 When configuring the aggregation group for the device of link 2) in the figure, do not add any physical member interface, and configure the aggregation port (such as Bagg1) as an interface for unilateral access to the M-lag system, so as to achieve the deployment of the access device into the M-lag system with single access, and create an M-lag group corresponding to the access device.

[0081] Further, see Figure 7 In one example, the method for automatically deploying an M-lag group includes:

[0082] Step 1: The user triggers the one-click batch deployment of M-lag group tasks through the controller page.

[0083] Step 2: After receiving the user trigger instruction, the controller calls the SNMP protocol module to obtain the topology of the network, such as the device information of each device in the network, the link relationship between devices, etc.

[0084] In addition, it also includes detecting device information of the access device and link information between the access device and the Leaf device. The specific process is the same as step 101 of the aforementioned embodiment, and will not be repeated in this embodiment.

[0085] Step 3: Based on the topology structure, device information and link relationship data in step 2, calculate the link list for deploying the M-lag group.

[0086] Step 4: Preview the link list of the M-lag group that is automatically deployed with one click. For example, through the user's selection operation on the controller, the M-lag group is created in batches with one click, and at least one link of the access device and the Leaf device is aggregated to the newly created link aggregation interface to achieve link aggregation of the two devices. For the specific process, please refer to steps 102 to 104 of the aforementioned embodiment.

[0087] Step 5: The controller sends the M-lag group configuration to the device. For example, it sends configuration commands to the Leaf device and access device to instruct the receiving device to forward traffic through the newly created link aggregation interface.

[0088] Step 6: Output the deployment results to complete the automatic deployment task.

[0089] When the M-lag system protocol message interaction finds that the aggregation groups at both ends have successfully deployed the M-lag group, the protocol consistency check is passed, the M-lag system is activated and the traffic is forwarded normally; at the same time, the traffic sent and received by the single-home access device is forwarded to the Leaf devices that make up the M-lag system through the M-lag group; the load balancing unit in the M-lag system balances the traffic according to the load sharing mode, thereby solving the load sharing problem.

[0090] The method provided in this embodiment deploys an M-lag group for a single-homed access device, and connects the access device to a Leaf device through the M-lag group; and realizes automatic deployment of multiple access devices into an M-lag aggregation group with one click through an automatic deployment method.

[0091] In addition, the present application also discloses an automatic deployment device, such as Figure 8 As shown, the device includes: an acquisition unit 801, a determination unit 802, a configuration unit 803 and a sending unit 804. In addition, the device may also include other more or fewer units / modules, such as a storage unit, etc., which is not limited in this embodiment.

[0092] Among them, the acquisition unit 801 is used to obtain device information in the networking structure and the link relationship between devices, wherein the device information includes first access device information, and the link information includes link information connected to the first access device.

[0093] The determination unit 802 is used to determine, if it is determined based on the first access device information and the link information that the first access device is single-homed to the M-lag system, then the Leaf device in the M-lag system that is single-homed to the first access device, and at least one link between the Leaf device and the first access device.

[0094] The configuration unit 803 is used to configure a link aggregation interface for the first access device and the Leaf device, aggregate the at least one link to the link aggregation interface, and create an M-lag group corresponding to the first access device.

[0095] The sending unit 804 is used to send a configuration command to the Leaf device, where the configuration command is used to instruct the traffic received by the Leaf device through the link aggregation interface to be shared and processed by the M-lag system.

[0096] Optionally, in a specific implementation, the acquisition unit 801 is specifically used to obtain device information of the networking structure by calling SNMP, the device information including: device model, device IP address, interface number; and based on the device model, the device IP address and the interface number in the device information, obtain the link relationship between the devices through link relationship calculation.

[0097] Optionally, in another specific implementation, the determination unit 802 is further used to determine whether the number of Leaf devices among all neighbor devices of the first access device is 1 based on the first access device information and the link information; if so, determine whether the neighbor Leaf device of the first access device is a device in the M-lag system; if so, determine that the first access device is single-homed to the M-lag system.

[0098] Optionally, in another specific implementation, the determination unit 802 is further used to determine that the first access device is not single-homed to the M-lag system if the neighbor Leaf device of the first access device is not a device in the M-lag system.

[0099] In addition, the above device also includes a display unit, which is Figure 8 Not shown in the figure, the display unit is used to display the created M-lag group, the first access device information and the aggregated link aggregation interface information in a preset form.

[0100] Furthermore, the preset format may be a table, a picture or other forms, which is not limited in this embodiment.

[0101] The device provided in this embodiment determines whether the current device is single-homed to the M-lag system through access device information and link information, then aggregates the single-homed access device and the Leaf device in the M-lag system, configures the link aggregation interface, and issues a configuration command, thereby creating an M-lag group corresponding to the access device. The traffic accessed by the link aggregation interface of the M-lag system is then load-shared by the M-lag system according to the MAC and IP parity of the terminal device to the two Leaf devices of the M-lag system for processing and forwarding, thereby solving the problem that the traffic accessed by the single-homed access device cannot be redundantly backed up and load-shared.

[0102] In addition, an embodiment of the present invention further provides an electronic device, such as Fig. 9 As shown, the electronic device may include a processor 110 and a memory 120, wherein the processor 110 and the memory 120 may be connected via a bus or in other ways. Fig. 9In the example, the connection through a bus is taken. In addition, the electronic device further includes at least one interface 130, and the at least one interface 130 may be a communication interface or other interface, which is not limited in this embodiment.

[0103] The processor 110 may be a central processing unit (CPU). The processor 110 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above chips.

[0104] The memory 120, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs, non-transitory computer executable programs and modules, such as program instructions / modules corresponding to the method for automatically deploying the M-lag group in the embodiment of the present invention. The processor 110 executes various functional applications and data processing of the processor by running the non-transitory software programs, instructions and modules stored in the memory 120, that is, the method for automatically deploying the M-lag group in the above method embodiment is implemented.

[0105] The memory 120 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and applications required for at least one function; the data storage area may store data created by the processor 110, etc. In addition, the memory 120 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 120 may optionally include a memory remotely arranged relative to the processor 110, and these remote memories may be connected to the processor 110 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0106] In addition, at least one interface 130 is used for communication between the electronic device and external devices, such as communication with a server, etc. Optionally, at least one interface 130 can also be used to connect external input and output devices, such as a keyboard, a display screen, etc.

[0107] The one or more modules are stored in the memory 120 and when executed by the processor 110, perform the following steps: Figure 4 , Figure 6 to Figure 7The method for automatically deploying M-lag groups in the illustrated embodiment.

[0108] Optionally, the electronic device may be a network controller, or may be any network device in the network, such as a switch, a Leaf device, an access device, etc.

[0109] In addition, this embodiment also provides an automatic deployment system, the structure of which can be as described above. Figure 1 or Figure 5 As shown, the system includes a network controller for implementing the automatic deployment method of the M-lag group in the aforementioned embodiment.

[0110] Furthermore, the system may also include at least one network device such as a Leaf device and an access device, and the structures of these devices may be similar to those of Fig. 9 The structures of the electronic devices shown are the same or different, and this embodiment does not limit this.

[0111] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above-mentioned types of memory.

[0112] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for automatically deploying an M-lag group, characterized in that: The method comprises: Acquire device information in the networking structure, and link relationships between devices, wherein the device information includes first access device information, and the link relationship includes link information connected to the first access device; If it is determined, according to the first access device information and the link information, that the first access device is single-homed to an M-lag system, then determining a Leaf device in the M-lag system to which the first access device is single-homed, and at least one link between the Leaf device and the first access device; configuring a link aggregation interface for the first access device and the Leaf device, aggregating the at least one link to the link aggregation interface, so as to create an M-lag group corresponding to the first access device; A configuration command is issued to the Leaf device, where the configuration command is used to instruct the traffic received by the Leaf device through the link aggregation interface to be shared and processed by the M-lag system.

2. The method according to claim 1, characterized in that The obtaining of device information in the networking structure and link relationships between devices includes: Obtain the device information of the network structure by calling the Simple Network Management Protocol (SNMP), wherein the device information includes: device model, device IP address, and interface number; The link relationship between the devices is obtained by link relationship calculation according to the device model, the device IP address and the interface number in the device information.

3. The method according to claim 1 or 2, characterized in that: Determining that the first access device single-homedly accesses the M-lag system includes: Determine, according to the first access device information and the link information, whether the number of Leaf devices in all neighboring devices of the first access device is 1; If yes, determining whether the neighbor Leaf device of the first access device is a device in the M-lag system; If yes, it is determined that the first access device single-homedly accesses the M-lag system.

4. The method according to claim 3, characterized in that The method further comprises: If the neighbor Leaf device of the first access device is not a device in the M-lag system, it is determined that the first access device is not single-homed to the M-lag system.

5. The method according to claim 1 or 2, characterized in that: After aggregating the at least one link to the link aggregation interface, the method further includes: The created M-lag group, the first access device information and the aggregated link aggregation interface information are displayed in a preset form.

6. A device for automatically deploying an M-lag group, characterized in that: The device comprises: An acquisition unit, configured to acquire device information in a networking structure and a link relationship between devices, wherein the device information includes first access device information, and the link relationship includes link information connected to the first access device; a determining unit, configured to determine, if it is determined according to the first access device information and the link information that the first access device single-homedly accesses the M-lag system, a Leaf device in the M-lag system to which the first access device single-homedly accesses, and at least one link between the Leaf device and the first access device; A configuration unit, configured to configure a link aggregation interface for the first access device and the Leaf device, and aggregate the at least one link to the link aggregation interface to create an M-lag group corresponding to the first access device; The sending unit is used to send a configuration command to the Leaf device, where the configuration command is used to instruct the traffic received by the Leaf device through the link aggregation interface to be shared and processed by the M-lag system.

7. The device according to claim 6, characterized in that The acquisition unit is specifically used to obtain device information of the networking structure by calling SNMP, wherein the device information includes: device model, device IP address, and interface number; and based on the device model, the device IP address, and the interface number in the device information, obtain the link relationship between the devices through link relationship calculation.

8. The device according to claim 6 or 7, characterized in that The determining unit is specifically used for: Determine, according to the first access device information and the link information, whether the number of Leaf devices in all neighboring devices of the first access device is 1; If yes, determining whether the neighbor Leaf device of the first access device is a device in the M-lag system; If yes, it is determined that the first access device single-homedly accesses the M-lag system.

9. An electronic device, characterized in that: comprising a processor and a memory, the memory being coupled to the processor; The memory stores computer-readable program instructions, and when the instructions are executed by the processor, the method for automatically deploying an M-lag group as described in any one of claims 1 to 5 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for automatically deploying an M-lag group as claimed in any one of claims 1 to 5 is implemented.

Images