Intelligent topology opening method and device and medium

Abstract

The embodiment of the invention discloses an intelligent topology opening method and device and a medium, belongs to the technical field of computer networks, and solves the problems that a manual network topology planning method is time-consuming and labor-consuming, and network faults are easily introduced due to manual operation errors. Acquiring equipment information, MLAG relation information and an equipment management network IP address network segment; on the basis of the equipment information, acquiring corresponding management IP addresses in the IP address network segment of the equipment management network for the equipment in sequence; based on the equipment information, carrying out equipment arrangement on the canvas; based on the equipment information and the MLAG relation information, generating a topological link for the arranged equipment on the canvas, so as to obtain a planning topology based on the management IP address and the topological link; and comparing the planned topology with the real topology, marking the compared topology difference, and adjusting the planned topology based on the marked topology difference.

Description

Technical Field

[0001] The present application relates to the field of computer network technology, and in particular to an intelligent topology deployment method, device and medium. Background Art

[0002] In today's highly developed information age, data centers, as core facilities for information storage, processing and transmission, are of self-evident importance.

[0003] In the process of deploying a data center network, the network topology determines how data flows between devices and the connections between devices. When planning the topology, you need to consider a variety of factors, including device roles, link connection relationships, bandwidth requirements, and redundancy design.

[0004] However, in actual operation, network topology is usually planned manually. Manually planning network topology is not an easy task. Since data center networks usually contain a large number of devices and complex connection relationships, the planning process is often time-consuming and laborious. Moreover, once the planning is completed, if the connection between devices is wrong, each device and each connection needs to be checked one by one, which brings great trouble to subsequent network debugging and maintenance. It is not only time-consuming and labor-intensive, but also may introduce new faults due to operational errors. Summary of the invention

[0005] The embodiments of the present application provide an intelligent topology deployment method, device and medium, which are used to solve the following technical problems: the method of manually planning the network topology is time-consuming and labor-intensive, and is prone to introduce network failures due to manual operation errors.

[0006] The present application embodiment adopts the following technical solutions:

[0007] The embodiment of the present application provides an intelligent topology startup method, including obtaining device information, MLAG relationship information, and device management network IP address segment; based on the device information, obtaining the corresponding management IP address for each device in the device management network IP address segment in turn; based on the device information, arranging the devices on the canvas; based on the device information and the MLAG relationship information, generating topology links for the arranged devices on the canvas, so as to obtain a planned topology based on the management IP address and the topology link; comparing the planned topology with the actual topology, marking the compared topology differences, and adjusting the planned topology based on the marked topology differences.

[0008] The embodiment of the present application uses the SDN controller software to automatically plan the topology, automatically generate the planned topology map according to the device type and quantity, automatically assign an IP address to each device, and automatically generate links between devices, which greatly saves manpower. At the same time, it can automatically detect the difference between the actual topology and the planned topology, which not only saves the manpower cost of manual verification, but also improves the accuracy of the verification results. It solves the problem of cumbersome topology planning when the network is started, and cumbersome topology verification after the start.

[0009] In one implementation of the present application, based on the device information, a corresponding management IP address is obtained in the IP address segment of the device management network for each device in turn, specifically including: determining the device role corresponding to each device based on the device information; wherein the device role includes at least one of spine, borderleaf and serverleaf; dividing the devices into multiple device sets based on the device role, and sorting the devices in the multiple device sets respectively, and based on the sorting results, obtaining a corresponding management IP address in the IP address segment of the device management network for each device in turn.

[0010] In one implementation of the present application, devices are divided into multiple device sets based on device roles, and the devices in the multiple device sets are sorted respectively. Based on the sorting results, a corresponding management IP address is obtained in the device management network IP address segment for each device in turn, specifically including: performing a first sorting on the multiple device sets to determine the first address acquisition order corresponding to the multiple device sets respectively; determining the device name corresponding to each device respectively, sorting the devices in each device set based on the alphabetical order of the device names, and determining the second address acquisition order corresponding to each device in the device set based on the sorting; based on the first address acquisition order and the second address acquisition order, obtaining the corresponding management IP address in the device management network IP address segment for each device in turn.

[0011] In one implementation of the present application, devices are arranged on a canvas based on device information, specifically including: determining device roles and device quantities corresponding to the device information; and adding different quantities of devices to preset positions of the canvas based on different device roles.

[0012] In one implementation of the present application, different numbers of devices are added to preset positions of the canvas based on different device roles, specifically including: when the device role is spine, the corresponding number of devices are added to the middle preset position of the canvas; when the device role is borderleaf, the corresponding number of devices are added to the upper preset position of the canvas; when the device role is serverleaf, the corresponding number of devices are added to the lower preset position of the canvas.

[0013] In one implementation of the present application, a topological link is generated for the arranged devices on a canvas based on device information and MLAG relationship information, specifically including: based on device roles, device quantity and MLAG relationship, multiple device groups performing MLAG are determined among multiple devices with device roles of borderleaf and serverleaf, and a first connection relationship is determined based on the multiple device groups performing MLAG; a second connection relationship corresponding to a device with a device role of borderleaf and a device role of spine is determined; and a third connection relationship corresponding to a device with a device role of serverleaf and a device role of spine is determined; based on the first connection relationship, the second connection relationship and the third connection relationship, a topological link is generated for the arranged devices on a canvas.

[0014] In one implementation of the present application, based on the first connection relationship, the second connection relationship and the third connection relationship, a topological link is generated for the arranged devices on the canvas, specifically including: based on the first connection relationship, generating a peerlink link and a keepalive link between multiple devices doing MLAG; and based on the second connection relationship, generating a full-mesh link between a device with a borderleaf device role and a spine device role; and based on the third connection relationship, generating a full-mesh link between a device with a serverleaf device role and a spine device role.

[0015] In one implementation of the present application, the planned topology is compared with the actual topology, and the compared topological differences are marked, specifically including: determining the device information and link information corresponding to the real device through the SNMP protocol to generate the real topology; comparing the planned topology with the actual topology; wherein the comparison information includes at least one of the device role, device model, device name, device IP, and link connection relationship; determining the topological differences based on the comparison results, and making different annotations based on the difference types of the topological differences.

[0016] An embodiment of the present application provides an intelligent topology deployment device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: obtain device information, MLAG relationship information, and a device management network IP address segment; based on the device information, obtain a corresponding management IP address for each device in the device management network IP address segment in turn; based on the device information, arrange the devices on a canvas; based on the device information and the MLAG relationship information, generate a topology link for the arranged devices on the canvas to obtain a planned topology based on the management IP address and the topology link; compare the planned topology with the actual topology, mark the compared topology differences, and adjust the planned topology based on the marked topology differences.

[0017] A non-volatile computer storage medium provided in an embodiment of the present application stores computer executable instructions, wherein the computer executable instructions are configured to: obtain device information, MLAG relationship information, and a device management network IP address segment; based on the device information, obtain a corresponding management IP address in the device management network IP address segment for each device in turn; based on the device information, arrange the devices on a canvas; based on the device information and the MLAG relationship information, generate a topology link for the arranged devices on the canvas to obtain a planned topology based on the management IP address and the topology link; compare the planned topology with the actual topology, mark the compared topology differences, and adjust the planned topology based on the marked topology differences.

[0018] At least one of the above technical solutions adopted in the embodiment of the present application can achieve the following beneficial effects: The embodiment of the present application automatically plans the topology through the SDN controller software, automatically generates the planned topology map according to the device type and quantity, automatically assigns an IP address to each device, and automatically generates links between devices, which greatly saves manpower. At the same time, it can automatically detect the difference between the actual topology and the planned topology, which not only saves the manpower cost of manual verification, but also improves the accuracy of the verification results. It solves the problem of cumbersome topology planning when the network is started, and cumbersome topology verification after the start. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor.

[0020] In the figure:

[0021] Figure 1 A flow chart of an intelligent topology deployment method provided in an embodiment of the present application;

[0022] Figure 2 A schematic diagram of a topology structure provided in an embodiment of the present application;

[0023] Figure 3 A schematic diagram of the structure of an intelligent topology deployment device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0024] Embodiments of the present application provide an intelligent topology deployment method, device, and medium.

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

[0026] The technical solution proposed in the embodiment of the present invention is described in detail below with reference to the accompanying drawings.

[0027] Figure 1 A flow chart of an intelligent topology deployment method provided in an embodiment of the present application is shown in FIG. Figure 1 As shown in the figure, the intelligent topology deployment method includes the following steps:

[0028] S101. Obtain device information, MLAG relationship information, and device management network IP address segment.

[0029] In one embodiment of the present application, an SDN (Software Defined Network) controller receives information such as the number, model, role, MLAG (multi-chassis link aggregation group) relationship of devices input by an operator through an SDN controller interface, and receives an IP address segment of a device management network set by the operator through the SDN controller.

[0030] Specifically, the operator inputs the number of devices required in the network through the SDN controller interface. The operator also needs to input the model of each device. The operator specifies the role for each device through the SDN controller interface, and inputs the MLAG relationship information between devices through the SDN controller interface, such as which devices are MLAG pairs and the connection relationship between them. The operator also needs to set the IP address segment of the device management network through the SDN controller interface. The device management network is a dedicated network used to manage devices in the network, and its IP address segment determines the allocation range of the device management IP address.

[0031] S102. Based on the device information, obtain a corresponding management IP address in the device management network IP address segment for each device in turn.

[0032] In one embodiment of the present application, the device role corresponding to each device is determined based on the device information; wherein the device role includes at least one of spine, borderleaf and serverleaf. The devices are divided into multiple device sets based on the device roles, and the devices in the multiple device sets are sorted respectively. Based on the sorting results, the corresponding management IP address is obtained for each device in the device management network IP address segment in turn.

[0033] Specifically, the embodiment of the present application first determines the role corresponding to each device, and after determining the device role, divides the device into multiple sets, each set containing devices with the same role. For example, a set containing all spine role devices (spine switches), a set containing all borderleaf role devices (border leaf switches), and a set containing all serverleaf role devices (server leaf switches) can be created. After the device sets are divided, the devices in each set are sorted. After the sorting is completed, the corresponding management IP address is obtained for each device in the device management network IP address segment based on the sorting order.

[0034] The embodiment of the present application can achieve efficient management and optimization of network devices by determining device roles, dividing device sets, sorting and allocating management IP addresses based on device information, thereby improving network reliability, performance and security, while reducing management costs and maintenance difficulties.

[0035] In one embodiment of the present application, a first sorting is performed on multiple device sets to determine the first address acquisition order corresponding to the multiple device sets. The device names corresponding to each device are determined, and the devices in each device set are sorted based on the alphabetical order of the device names, and the second address acquisition order corresponding to each device in the device set is determined based on the sorting. Based on the first address acquisition order and the second address acquisition order, the corresponding management IP address is obtained for each device in the device management network IP address segment in turn.

[0036] Specifically, the device obtains the device address from the network segment in the order of spine->borderleaf->serverleaf roles. Devices with the same role obtain the corresponding management IP address from the network segment in the alphabetical order of the device name.

[0037] Furthermore, the embodiment of the present application sorts multiple device sets according to a preset sorting basis to determine their first address acquisition order. For example, the embodiment of the present application allocates IP addresses to device sets with higher performance or more important functions.

[0038] Furthermore, in the embodiment of the present application, each device corresponds to a unique device name, and within each device set, the devices are sorted according to the alphabetical order of the device names. According to the sorting result, the order of obtaining the second addresses of the devices in each device set is determined.

[0039] Further, according to the first address acquisition sequence and the second address acquisition sequence, the corresponding management IP address is obtained for each device in the device management network IP address segment in turn. Specifically, according to the first address acquisition sequence, a device set is selected, and within the device set, according to the second address acquisition sequence, an IP address is allocated to each device in the set, and this process is repeated until all devices in the device set are allocated IP addresses.

[0040] The embodiment of the present application performs a first sort on multiple device sets and a second sort based on the device name within each set, thereby ensuring that the allocation of IP addresses meets the requirements of network planning and facilitates subsequent management and maintenance, thereby improving the efficiency and accuracy of network management and reducing the risk of errors.

[0041] S103: Arrange devices on the canvas based on the device information.

[0042] In one embodiment of the present application, the device role and the number of devices corresponding to the device information are determined, and different numbers of devices are added to the preset positions of the canvas based on different device roles.

[0043] Specifically, when the device role is spine, a corresponding number of devices are added to the middle preset position of the canvas. When the device role is borderleaf, a corresponding number of devices are added to the upper preset position of the canvas. When the device role is serverleaf, a corresponding number of devices are added to the lower preset position of the canvas.

[0044] Specifically, the SDN controller automatically arranges the devices on the canvas according to the device roles and quantities, with devices with the borderleaf role arranged in the top row, devices with the spine role arranged in the middle row, and devices with the serverleaf role arranged in the bottom row. Figure 2 A schematic diagram of a planning topology structure provided in an embodiment of the present application is shown in FIG. Figure 2 As shown in the figure, the top layer is the devices with the borderleaf role, including borderleaf 1 and borderleaf 2; the middle layer is the devices with the spine role, including spine 1 and spine2; the bottom layer is the devices with the serverleaf role, including serverleaf 1, serverleaf 2, and up to serverleaf n.

[0045] S104 . Based on the device information and the MLAG relationship information, a topology link is generated for the arranged devices on the canvas, so as to obtain a planned topology based on the management IP address and the topology link.

[0046] In one embodiment of the present application, based on the device role, the number of devices and the MLAG relationship, multiple device groups that perform MLAG are determined among multiple devices with device roles of borderleaf and serverleaf, and a first connection relationship is determined based on the multiple device groups that perform MLAG. A second connection relationship corresponding to a device with a device role of borderleaf and a device with a device role of spine is determined; and a third connection relationship corresponding to a device with a device role of serverleaf and a device with a device role of spine is determined; and a topological link is generated for the arranged devices on a canvas based on the first connection relationship, the second connection relationship and the third connection relationship.

[0047] Specifically, for each role of the device, the MLAG relationship between them is determined, and the devices are grouped according to the MLAG relationship to obtain multiple borderleaf MLAG groups and multiple serverleaf MLAG groups. The devices in each group will share the same MLAG configuration and are usually interconnected through internal links. Within each MLAG group, a first connection relationship between the devices is determined. A second connection relationship between each borderleaf device and the spine device is determined, and a third connection relationship between each serverleaf device and the spine device is determined.

[0048] In one embodiment of the present application, based on the first connection relationship, peerlink links and keepalive links are generated between multiple MLAG devices; and based on the second connection relationship, a full-mesh link is generated between a device with a borderleaf device role and a spine device role; and based on the third connection relationship, a full-mesh link is generated between a device with a serverleaf device role and a spine device role.

[0049] Specifically, within each MLAG group, use lines or arrows to connect device icons to represent peerlinks. Make sure the lines are clear and easy to identify. If keepalive links are different from peerlinks, they can be drawn separately. Typically, keepalive links may be used for monitoring or fault detection, and additional dashed or dotted lines can be added between devices to represent this.

[0050] Furthermore, according to the device roles, the connection relationships between borderleaf and spine devices and between serverleaf and spine devices are determined, and each borderleaf device is automatically connected to all spine devices and each serverleaf device to all spine devices through lines or arrows. Ensure that each device is connected to the required spine device to form a full-mesh network.

[0051] S105: Compare the planned topology with the actual topology, mark the compared topological differences, and adjust the planned topology based on the marked topological differences.

[0052] In one embodiment of the present application, the device information and link information corresponding to the real device are determined through the SNMP protocol to generate the real topology. The planned topology is compared with the real topology; wherein the comparison information includes at least one of the device role, device model, device name, device IP, and link connection relationship. The topological difference is determined based on the comparison result, and different annotations are made based on the difference type of the topological difference.

[0053] Specifically, the SDN controller manages real devices, reads device information and link information through the SNMP protocol, and generates the topology of the real network. The SDN controller compares the planned topology with the real topology. It compares the device role, device model, device name, device IP, link relationship and other factors one by one. The SDN controller displays the differences in the comparison results with different color markers. Different situations such as matching errors, more devices or links in the planned topology than the real topology, and fewer devices or links in the planned topology than the real topology are marked with different colors to facilitate quick identification of differences.

[0054] The embodiment of the present application uses the SDN controller software to automatically plan the topology, automatically generate the planned topology map according to the device type and quantity, automatically assign an IP address to each device, and automatically generate links between devices. Network engineers build the real topology according to the planned topology. After the construction is completed, the SDN controller software manages the real topology and compares it with the planned topology, including device roles, IP addresses, link information, etc., and marks the inconsistencies with different colors to facilitate network engineers to find differences and make adjustments. The embodiment of the present application can greatly save manpower by automatically generating the planned topology. The embodiment of the present application can also automatically detect the difference between the real topology and the planned topology, which can not only save the manpower cost of manual verification, but also make the verification results more accurate.

[0055] Figure 3 The following is a schematic diagram of the structure of an intelligent topology deployment device provided in an embodiment of the present application. Figure 3As shown, the intelligent topology start-up device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: obtain device information, MLAG relationship information, and device management network IP address segment; based on the device information, obtain the corresponding management IP address for each device in the device management network IP address segment in turn; based on the device information, arrange the devices on the canvas; based on the device information and the MLAG relationship information, generate topology links for the arranged devices on the canvas to obtain a planned topology based on the management IP address and the topology links; compare the planned topology with the actual topology, mark the compared topology differences, and adjust the planned topology based on the marked topology differences.

[0056] A non-volatile computer storage medium provided in an embodiment of the present application stores computer executable instructions, wherein the computer executable instructions are configured to: obtain device information, MLAG relationship information, and a device management network IP address segment; based on the device information, obtain a corresponding management IP address in the device management network IP address segment for each device in turn; based on the device information, arrange the devices on a canvas; based on the device information and the MLAG relationship information, generate a topology link for the arranged devices on the canvas to obtain a planned topology based on the management IP address and the topology link; compare the planned topology with the actual topology, mark the compared topology differences, and adjust the planned topology based on the marked topology differences.

[0057] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

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

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

[0060] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0061] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0062] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

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

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

[0065] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the embodiments of the present application may have various changes and variations. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application.

Claims

1. An intelligent topology deployment method, characterized in that: The method comprises: Obtain device information, MLAG relationship information, and device management network IP address segment; Based on the device information, obtaining a corresponding management IP address for each device in the device management network IP address segment in turn; Arrange devices on the canvas based on the device information; Based on the device information and the MLAG relationship information, generating a topology link for the arranged devices on the canvas, so as to obtain a planned topology based on the management IP address and the topology link; The planned topology is compared with the actual topology, topological differences obtained by the comparison are marked, and the planned topology is adjusted based on the marked topological differences.

2. The intelligent topology deployment method according to claim 1, characterized in that: The step of sequentially obtaining a corresponding management IP address for each device in the device management network IP address segment based on the device information specifically includes: Determine the device role corresponding to each of the devices based on the device information; wherein the device role includes at least one of spine, borderleaf and serverleaf; The devices are divided into a plurality of device sets based on the device roles, and the devices in the plurality of device sets are sorted respectively. Based on the sorting results, a corresponding management IP address is obtained in the device management network IP address segment for each device in turn.

3. The intelligent topology deployment method according to claim 2, characterized in that: The device is divided into a plurality of device sets based on the device roles, and the devices in the plurality of device sets are sorted respectively, and based on the sorting results, a corresponding management IP address is obtained for each device in the device management network IP address segment in turn, specifically including: Performing a first sort on the plurality of device sets to determine a first address acquisition order respectively corresponding to the plurality of device sets; Determine a device name corresponding to each of the devices, sort the devices in each of the device sets based on the alphabetical order of the device names, and determine a second address acquisition order corresponding to each of the devices in the device set based on the sorting; Based on the first address acquisition sequence and the second address acquisition sequence, a corresponding management IP address is acquired in the device management network IP address segment for each device in turn.

4. The intelligent topology deployment method according to claim 1, characterized in that: Arranging devices on the canvas based on the device information specifically includes: Determine the device role and device quantity corresponding to the device information; Based on the different roles of the device, different numbers of devices are added to the preset positions of the canvas.

5. The intelligent topology deployment method according to claim 4, characterized in that: Adding different numbers of devices to preset positions of the canvas based on different device roles specifically includes: When the device role is spine, a corresponding number of devices are added to a preset middle position of the canvas; When the device role is borderleaf, a corresponding number of devices are added to a preset position above the canvas; When the device role is serverleaf, a corresponding number of devices are added to a preset position below the canvas.

6. The intelligent topology deployment method according to claim 5, characterized in that: The generating a topology link for the arranged devices on the canvas based on the device information and the MLAG relationship information specifically includes: Based on the device role, the number of devices and the MLAG relationship, a plurality of device groups performing MLAG are determined from a plurality of devices whose device roles are the borderleaf and the serverleaf, and a first connection relationship is determined based on the plurality of device groups performing MLAG; Determine a second connection relationship corresponding to the device whose device role is borderleaf and the device whose device role is spine; and Determine a third connection relationship corresponding to the device whose device role is serverleaf and the device whose device role is spine; Based on the first connection relationship, the second connection relationship, and the third connection relationship, a topological link is generated for the arranged devices on the canvas.

7. The intelligent topology deployment method according to claim 6, characterized in that: The generating a topological link for the arranged devices on the canvas based on the first connection relationship, the second connection relationship, and the third connection relationship specifically includes: Based on the first connection relationship, generating peerlink links and keepalive links between the plurality of devices performing MLAG; and Based on the second connection relationship, generating a full-mesh link between the device whose device role is borderleaf and the device whose device role is spine; and Based on the third connection relationship, a full-mesh link is generated between the device whose device role is serverleaf and the device whose device role is spine.

8. The intelligent topology deployment method according to claim 1, characterized in that: The comparing the planned topology with the actual topology and marking the topological differences obtained by the comparison specifically includes: The device information and link information corresponding to the real device are determined through the SNMP protocol to generate the real topology; Compare the planned topology with the actual topology; wherein the comparison information includes at least one of the device role, device model, device name, device IP, and link connection relationship; The topological differences are determined based on the comparison results, and different annotations are performed based on the difference types of the topological differences.

9. An intelligent topology deployment device, characterized in that: The device comprises a memory for storing computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, the device is triggered to execute the method according to any one of claims 1 to 8.

10. A non-volatile computer storage medium storing computer executable instructions, characterized in that: The computer executable instructions can execute the method according to any one of claims 1 to 8.

Images