An intelligent topology opening method, device and medium

Abstract

The embodiment of the application discloses a kind of intelligent topology opening method, equipment and medium, belong to computer network technical field, solve the method of manual planning network topology Time-consuming and labor-consuming, and easy to introduce network failure due to manual operation error Problem.Acquire device information, MLAG relationship information and device management network IP address segment;Based on device information, in turn for each device in device management network IP address segment obtains corresponding management IP address;Based on device information, device arrangement is carried out on canvas;Based on device information and MLAG relationship information, topological link is generated to arranged device on canvas, to obtain planning topology based on management IP address and topological link;Planning topology is compared with real topology, the topological difference compared out is marked, and planning topology is adjusted based on the topological difference marked out.

Description

Technical Field

[0001] This application relates to the field of computer network technology, and in particular to a method, device and medium for intelligent topology setup. Background Technology

[0002] In today's highly information-driven era, the importance of data centers as core facilities for information storage, processing, and transmission is self-evident.

[0003] In the initial setup of a data center network, the network topology determines how data flows between devices and the connections between them. When planning the topology, various factors need to be considered, including device roles, link connections, bandwidth requirements, and redundancy design.

[0004] However, in practice, network topology is usually planned manually. Manually planning a network topology is no easy task. Because data center networks typically contain a large number of devices and complex connections, the planning process is often time-consuming and labor-intensive. Moreover, once the planning is complete, if the connections between devices are incorrect, each device and each connection needs to be checked one by one, which greatly complicates subsequent network debugging and maintenance. This is not only time-consuming and labor-intensive, but may also introduce new faults due to operational errors. Summary of the Invention

[0005] This application provides an intelligent topology planning method, device, and medium to solve the following technical problem: manual network topology planning is time-consuming and laborious, and is prone to network failures due to manual operation errors.

[0006] The embodiments of this application adopt the following technical solutions:

[0007] This application provides a method for intelligent topology deployment. It includes: acquiring device information, MLAG relationship information, and device management network IP address segments; based on the device information, sequentially acquiring the corresponding management IP address for each device from the device management network IP address segments; arranging the devices on a canvas based on the device information; generating topology links for the arranged devices on the canvas based on the device information and MLAG relationship information, thereby obtaining a planned topology based on the management IP addresses and topology links; comparing the planned topology with the actual topology, marking the topology differences found, and adjusting the planned topology based on the marked topology differences.

[0008] This application embodiment uses SDN controller software for automatic topology planning. It automatically generates a planned topology map based on device type and quantity, automatically assigns IP addresses to each device, and automatically generates inter-device links, significantly saving manpower. Simultaneously, it can automatically detect differences between the actual and planned topology, saving not only the labor costs of manual verification but also improving the accuracy of verification results. This solves the problems of cumbersome topology planning during network deployment and cumbersome topology verification after deployment.

[0009] In one implementation of this application, based on device information, each device sequentially obtains its corresponding management IP address from the device management network IP address segment. Specifically, this includes: 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 roles, sorting the devices in the multiple device sets, and based on the sorting results, sequentially obtaining the corresponding management IP address for each device from the device management network IP address segment.

[0010] In one implementation of this application, devices are divided into multiple device sets based on device roles, and the devices in each set are sorted. Based on the sorting results, each device obtains a corresponding management IP address from the device management network IP address segment. Specifically, this includes: performing a first sort on the multiple device sets to determine the first address acquisition order for each set; determining the device name for each device; sorting the devices in each set based on the alphabetical order of the device names; determining a second address acquisition order for each device in each set; and obtaining the corresponding management IP address from the device management network IP address segment for each device based on the first and second address acquisition orders.

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

[0012] In one implementation of this application, different numbers of devices are added to preset positions on the canvas based on different device roles. Specifically, this includes: when the device role is "spine", adding a corresponding number of devices to the middle preset position of the canvas; when the device role is "borderleaf", adding a corresponding number of devices to the upper preset position of the canvas; and when the device role is "serverleaf", adding a corresponding number of devices to the lower preset position of the canvas.

[0013] In one implementation of this application, a topology link is generated on the canvas for the arranged devices based on device information and MLAG relationship information. Specifically, this includes: determining multiple device groups that perform MLAGs from among multiple devices with the device roles of borderleaf and serverleaf based on device roles, number of devices, and MLAG relationships; determining a first connection relationship based on the multiple device groups that perform MLAGs; determining a second connection relationship between devices with the device role of borderleaf and devices with the device role of spine; and determining a third connection relationship between devices with the device role of serverleaf and devices with the device role of spine; and generating a topology link on the canvas for the arranged devices based on the first connection relationship, the second connection relationship, and the third connection relationship.

[0014] In one implementation of this application, a topology link is generated on the canvas for the arranged devices based on a first connection relationship, a second connection relationship, and a third connection relationship. Specifically, this includes: generating peerlink links and keepalive links between multiple MLAG-enabled devices based on the first connection relationship; generating full-mesh links between devices with the role of borderleaf and devices with the role of spine based on the second connection relationship; and generating full-mesh links between devices with the role of serverleaf and devices with the role of spine based on the third connection relationship.

[0015] In one implementation of this application, the planned topology is compared with the actual topology, and the differences in the topology are marked. Specifically, this includes: determining the device information and link information corresponding to the actual device through the SNMP protocol to generate the actual topology; comparing the planned topology with the actual topology; wherein the comparison information includes at least one of the following: device role, device model, device name, device IP, and link connection relationship; determining the topology differences based on the comparison results, and marking them differently based on the type of topology difference.

[0016] This application provides an intelligent topology deployment device, including: 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, which, when executed by the at least one processor, enable the at least one processor to: acquire device information, MLAG relationship information, and device management network IP address segments; based on the device information, sequentially acquire the corresponding management IP address for each device from the device management network IP address segments; arrange the devices on a canvas based on the device information; generate topology links for the arranged devices on the canvas based on the device information and MLAG relationship information, thereby obtaining a planned topology based on the management IP address and the topology links; compare the planned topology with the actual topology, mark the topology differences found in the comparison, and adjust the planned topology based on the marked topology differences.

[0017] This application provides a non-volatile computer storage medium storing computer-executable instructions. The computer-executable instructions are configured to: obtain device information, MLAG relationship information, and device management network IP address segments; based on the device information, sequentially obtain the corresponding management IP address for each device from the device management network IP address segments; arrange the devices on a canvas based on the device information; generate topology links for the arranged devices on the canvas based on the device information and MLAG relationship information, and obtain a planned topology based on the management IP address and topology links; compare the planned topology with the actual topology, mark the topology differences found in the comparison, and adjust the planned topology based on the marked topology differences.

[0018] The above-mentioned technical solutions adopted in this application embodiment can achieve the following beneficial effects: This application embodiment automatically plans the topology through SDN controller software, automatically generates a planned topology map according to the device type and quantity, automatically assigns IP addresses to each device, and automatically generates links between devices, greatly saving manpower. At the same time, it can automatically detect the difference between the actual topology and the planned topology, not only saving the manpower cost of manual verification but also improving the accuracy of the verification results. It solves the problems of cumbersome topology planning during network deployment and cumbersome topology verification after deployment. Attached Figure Description

[0019] 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 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 without creative effort.

[0020] In the picture:

[0021] Figure 1 A flowchart of an intelligent topology setup method provided in this application embodiment;

[0022] Figure 2 This application provides a schematic diagram of a planned topology.

[0023] Figure 3 This is a schematic diagram of the structure of an intelligent topology setup device provided in an embodiment of this application. Detailed Implementation

[0024] This application provides a smart topology setup method, device, and medium.

[0025] 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 with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0026] The technical solutions proposed in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0027] Figure 1 A flowchart of a smart topology setup method provided in this application embodiment is shown below. Figure 1 As shown, the smart topology setup 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 this application, the SDN (Software Defined Network) controller receives information such as the number of devices, models, roles, and MLAG (Multi-Chassis Link Aggregation Group) relationships input by the operator through the SDN controller interface, as well as the device management network IP address segment set by the operator through the SDN controller.

[0030] Specifically, operators input the required number of devices in the network through the SDN controller interface. They also need to input the model number of each device, assign roles to each device through the SDN controller interface, and input MLAG relationship information between devices, such as which devices are MLAG pairs and their connection relationships. Operators also need to configure the IP address range for the device management network through the SDN controller interface. The device management network is a dedicated network used to manage devices within the network, and its IP address range determines the allocation range of device management IP addresses.

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

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

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

[0034] This application's embodiments, through the process of determining device roles, dividing device sets, sorting, and allocating management IP addresses based on device information, can achieve efficient management and optimization of network devices. This improves network reliability, performance, and security while reducing management costs and maintenance complexity.

[0035] In one embodiment of this application, multiple device sets are first sorted to determine a first address acquisition order corresponding to each device set. The device names corresponding to each device are determined, and the devices in each device set are sorted according to the alphabetical order of the device names. Based on this sorting, a second address acquisition order corresponding to each device in the device set is determined. Based on the first and second address acquisition orders, each device sequentially acquires the corresponding management IP address from the device management network IP address segment.

[0036] Specifically, devices obtain their addresses from the network segment in the role order of spine->borderleaf->serverleaf, and devices with the same role obtain their corresponding management IP addresses from the network segment in alphabetical order of their device names.

[0037] Furthermore, in this embodiment of the application, multiple sets of devices are sorted according to a preset sorting criterion to determine their first address acquisition order. For example, this embodiment of the application allocates IP addresses to sets of devices with higher performance or greater importance.

[0038] Furthermore, in this embodiment, each device corresponds to a unique device name, and within each device set, the devices are sorted according to the alphabetical order of their device names. Based on the sorting result, the order in which the second address of the devices in each device set is obtained is determined.

[0039] Furthermore, according to the first address acquisition order and the second address acquisition order, each device sequentially obtains the corresponding management IP address from the device management network IP address segment. Specifically, according to the first address acquisition order, a device set is selected. Within this device set, according to the second address acquisition order, an IP address is assigned to each device in the set. This process is repeated until all devices in all device sets have been assigned IP addresses.

[0040] This application embodiment, by first sorting multiple device sets and then second sorting them based on device names within each set, ensures that the allocation of IP addresses not only meets the requirements of network planning but also 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 device information.

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

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

[0044] Specifically, the SDN controller automatically arranges devices on the canvas according to their roles and quantities. Devices with the borderleaf role are arranged in the top row, devices with the spine role are arranged in the middle row, and devices with the serverleaf role are arranged in the bottom row. Figure 2 A schematic diagram of a planned topology provided in this application embodiment, such as... Figure 2 As shown, the top layer consists of devices with the borderleaf role, including borderleaf 1 and borderleaf 2; the middle layer consists of devices with the spine role, including spine 1 and spine2; and the bottom layer consists of devices with the serverleaf role, including serverleaf 1, serverleaf 2, and so on up to serverleaf n.

[0045] S104. Based on device information and MLAG relationship information, generate topology links for the arranged devices on the canvas to obtain the planned topology based on the management IP address and topology links.

[0046] In one embodiment of this application, based on device roles, device quantity, and MLAG relationships, multiple device groups performing MLAGs are determined from among multiple devices with device roles of borderleaf and serverleaf. A first connection relationship is determined based on these multiple MLAG-performing device groups. A second connection relationship is determined between devices with the device role of borderleaf and devices with the device role of spine; and a third connection relationship is determined between devices with the device role of serverleaf and devices with the device role of spine. Based on the first, second, and third connection relationships, a topology link is generated on the canvas for the arranged devices.

[0047] Specifically, for devices of each role, the MLAG relationships between them are determined. Based on the MLAG relationships, the devices are grouped into multiple borderleaf MLAG groups and multiple serverleaf MLAG groups. Devices within each group will share the same MLAG configuration and are typically interconnected via internal links. Within each MLAG group, the first connection relationships between devices are determined. The second connection relationships between each borderleaf device and the spine device are determined, as well as the third connection relationships between each serverleaf device and the spine device.

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

[0049] Specifically, within each MLAG group, use lines or arrows to connect device icons to represent peerlink links. Ensure the lines are clear and easily identifiable. If keepalive links differ from peerlink links, 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 them.

[0050] Furthermore, based on the device roles, the connection relationships between borderleaf and spine devices, as well as between serverleaf and spine devices, are determined. Each borderleaf device is automatically connected to all spine devices, and each serverleaf device is connected to all spine devices, using lines or arrows. This ensures that each device is connected to the required spine devices, forming a full-mesh network.

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

[0052] In one embodiment of this application, the device information and link information corresponding to the real device are determined using the SNMP protocol to generate a real topology. The planned topology is then compared with the real topology; the comparison information includes at least one of the following: device role, device model, device name, device IP address, and link connection relationship. Based on the comparison results, topology differences are determined, and different labels are applied based on the type of difference.

[0053] Specifically, the SDN controller manages the actual devices, reads device and link information via the SNMP protocol, and generates a realistic network topology. The SDN controller compares the planned topology with the actual topology, comparing factors such as device roles, device models, device names, device IPs, and link relationships. The SDN controller displays differences in the comparison results using different colors. Different colors are used to mark different situations, such as mismatches, more devices or links in the planned topology than in the actual topology, or fewer devices or links in the planned topology than in the actual topology, facilitating quick identification of differences.

[0054] This application embodiment uses SDN controller software for automatic topology planning. It automatically generates a planned topology map based on device type and quantity, automatically assigns IP addresses to each device, and automatically generates inter-device links. Network engineers build the actual topology based on the planned topology. After construction, the SDN controller software incorporates the actual topology and compares it with the planned topology, including device roles, IP addresses, and link information. Inconsistencies are marked with different colors to facilitate network engineers in identifying and adjusting differences. This application embodiment significantly saves manpower by automatically generating the planned topology. Furthermore, it can automatically detect differences between the actual and planned topologies, saving on manual verification costs and ensuring more accurate verification results.

[0055] Figure 3 This is a schematic diagram of the structure of an intelligent topology setup device provided in an embodiment of this application. Figure 3As shown, the intelligent topology deployment 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, which, when executed by the at least one processor, enable the at least one processor to: acquire device information, MLAG relationship information, and device management network IP address segments; based on the device information, sequentially acquire the corresponding management IP address for each device from the device management network IP address segments; arrange the devices on a canvas based on the device information; generate topology links for the arranged devices on the canvas based on the device information and MLAG relationship information, thereby obtaining a planned topology based on the management IP address and the topology links; compare the planned topology with the actual topology, mark the topology differences found in the comparison, and adjust the planned topology based on the marked topology differences.

[0056] This application provides a non-volatile computer storage medium storing computer-executable instructions. The computer-executable instructions are configured to: obtain device information, MLAG relationship information, and device management network IP address segments; based on the device information, sequentially obtain the corresponding management IP address for each device from the device management network IP address segments; arrange the devices on a canvas based on the device information; generate topology links for the arranged devices on the canvas based on the device information and MLAG relationship information, and obtain a planned topology based on the management IP address and topology links; compare the planned topology with the actual topology, mark the topology differences found in the comparison, and adjust the planned topology based on the marked topology differences.

[0057] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0058] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the embodiments of this specification 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.

[0059] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. 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, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0060] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function 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 a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0061] 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.

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

[0063] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0064] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0065] The above descriptions are merely embodiments of this application and are not intended to limit the scope of this application. For those skilled in the art, various modifications and variations can be made to the embodiments of this application. These modifications or substitutions do not cause the essence of the corresponding technical solutions to depart from the spirit and scope of the technical solutions in the embodiments of this application.

Claims

1. A smart topology development method, characterized in that, The method includes: Obtain device information, MLAG relationship information, and device management network IP address range; Based on the device information, the corresponding management IP address is obtained for each device in the device management network IP address segment in sequence; Based on the device information, arrange the devices on the canvas; Based on the device information and the MLAG relationship information, a topology link is generated on the canvas for the arranged devices, so as to obtain the planned topology based on the management IP address and the topology link; The planned topology is compared with the actual topology, the differences in topology are marked, and the planned topology is adjusted based on the marked differences in topology.

2. The intelligent topology setup method according to claim 1, characterized in that, Based on the device information, the step of sequentially obtaining the corresponding management IP address for each device from the device management network IP address segment includes: Based on the device information, the device role corresponding to each device is determined; wherein, the device role includes at least one of spine, borderleaf, and serverleaf; Based on the device roles, the devices are divided into multiple device sets, and the devices in the multiple device sets are sorted. Based on the sorting results, each device obtains the corresponding management IP address in the device management network IP address segment.

3. The intelligent topology setup method according to claim 2, characterized in that, The process of dividing the devices into multiple device sets based on their roles, sorting the devices within each set, and then, based on the sorting results, obtaining the corresponding management IP address for each device from the device management network IP address segment, specifically includes: The multiple sets of devices are sorted in a first order to determine the order in which the first addresses are obtained for each of the multiple sets of devices. The device name corresponding to each of the aforementioned devices is determined. Based on the alphabetical order of the device names, the devices in each of the device sets are sorted. Based on the sorting, the second address acquisition order corresponding to each device in the device set is determined. Based on the first address acquisition order and the second address acquisition order, each device sequentially acquires the corresponding management IP address from the device management network IP address segment.

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

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

6. The intelligent topology setup method according to claim 5, characterized in that, The step of 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 roles, the number of devices, and the MLAG relationship, multiple device groups that perform MLAGs are determined from among the multiple devices whose device roles are borderleaf and serverleaf, and a first connection relationship is determined based on the multiple device groups that perform MLAGs. Determine the second connection relationship between the device role of borderleaf and the device role of spine; and The third connection relationship between the device with the device role of serverleaf and the device with the device role of spine was determined; Based on the first connection relationship, the second connection relationship, and the third connection relationship, a topology link is generated on the canvas for the arranged devices.

7. The intelligent topology setup method according to claim 6, characterized in that, The step of generating a topology 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, peerlink links and keepalive links are generated among the multiple MLAG-performing devices; and Based on the second connection relationship, a full-mesh link is generated between the device with the device role of borderleaf and the device role of spine; and Based on the third connection relationship, a full-mesh link is generated between the device with the device role of serverleaf and the device role of spine.

8. The intelligent topology setup method according to claim 1, characterized in that, The step of comparing the planned topology with the actual topology and marking the differences in the topology found includes: The SNMP protocol is used to determine the device information and link information corresponding to the real devices in order to generate the real topology; The planned topology is compared with the actual topology; the comparison information includes at least one of the following: device role, device model, device name, device IP, and link connection relationship. Topological differences are determined based on the comparison results, and different annotations are applied based on the difference types of the topological differences.

9. A smart topology setup device, characterized in that, The device includes 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 perform the method described in any one of claims 1-8.

10. A non-volatile computer storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are capable of performing the method described in any one of claims 1-8.

Images