A method and a controller for generating an expansion configuration

Abstract

Embodiments of the present application disclose a method and a controller for generating an expansion configuration, which are used to improve the expansion efficiency of leaf network elements. Embodiments of the present application provide a method for generating an expansion configuration, including: obtaining the topology of the current network and the access reliability configuration information of the current network; determining the topology of the network to be expanded based on the topology of the current network and the access reliability configuration information of the current network; and obtaining the configuration information of the leaf network elements to be expanded in the network to be expanded and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded based on the topology of the network to be expanded and the configuration information of the network elements in the current network.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a method and a controller for generating expansion configurations. Background Art

[0002] Data centers often need to expand servers to accommodate new virtual machines (VMs). As the servers are expanded, the ports of the leaf subnet elements connected to the servers are insufficient to connect the newly expanded servers. Therefore, the leaf subnet elements also need to be expanded.

[0003] When expanding the leaf subnet elements, since the leaf subnet elements need to be docked with the spine subnet elements to access the expanded leaf subnet elements into the Fabric architecture, it is necessary to configure the expanded leaf subnet elements and the connected spine subnet elements to ensure that the underlay network is connected.

[0004] Currently, in order to expand the leaf subnet elements, usually the network administrator needs to perform manual configuration to expand the leaf subnet elements. This method completely relies on the manual operation of the network administrator to complete, and there are problems such as long time-consuming and easy to make mistakes in expanding the leaf subnet elements, which reduces the expansion efficiency. Summary of the Invention

[0005] Embodiments of this application provide a method and a controller for generating expansion configurations to improve the expansion efficiency of leaf subnet elements.

[0006] To solve the above technical problems, the embodiments of this application provide the following technical solutions:

[0007] In a first aspect, an embodiment of this application provides a method for generating an expansion configuration, including:

[0008] Obtain the topology of the current network and the access reliability configuration information of the current network;

[0009] Determine the topology of the network to be expanded based on the topology of the current network and the access reliability configuration information of the current network;

[0010] Based on the topology of the network to be expanded and the configuration information of the network elements in the current network, obtain the configuration information of the leaf subnet elements to be expanded in the network to be expanded, and the networking configuration information of the spine subnet elements connected to the leaf subnet elements to be expanded.

[0011] In the embodiments of the present application, first, the topology of the current network and the access reliability configuration information of the current network are obtained. Then, based on the topology of the current network and the access reliability configuration information of the current network, the topology of the network to be expanded is determined. Finally, based on the topology of the network to be expanded and the configuration information of the network elements in the current network, the configuration information of the leaf network elements to be expanded in the network to be expanded and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded are obtained. In the embodiments of the present application, by analyzing the topology of the current network, the network elements included in the current network and the connection relationships between the network elements in the current network can be obtained. By analyzing the access reliability configuration information of the current network, the requirements for the access-side reliability configuration of the network elements in the current network can be obtained. After the above analysis, the topology of the network to be expanded can be determined. For example, the topology of the network to be expanded may include the leaf network elements to be expanded and the backbone network elements connected to the leaf network elements to be expanded. Finally, by analyzing the configuration information of the network elements in the current network, the configuration information of the leaf network elements to be expanded and the networking configuration information of the backbone network elements can be obtained. In the embodiments of the present application, manual configuration by network administrators is not required, and the expansion of leaf network elements can be automatically performed, improving the expansion efficiency of leaf network elements.

[0012] In a possible implementation manner, the method further includes:

[0013] Based on the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded, configure the backbone network elements connected to the leaf network elements to be expanded.

[0014] In the above solution, the controller can obtain the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded. The controller configures the backbone network elements according to the networking configuration information of the backbone network elements. For example, in the topology of the current network, the backbone network elements are connected to the current leaf network elements. At this time, the controller configures the backbone network elements using networking configuration information 1. In the topology of the network to be expanded, the backbone network elements also need to be connected to the leaf network elements to be expanded. The controller obtains the networking configuration information 2 of the backbone network elements, and the controller also needs to configure the backbone network elements using networking configuration information 2 so that the backbone network elements can be connected to the leaf network elements to be expanded.

[0015] In a possible implementation manner, the method further includes:

[0016] Send the configuration information of the leaf network elements to be expanded and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded to the configuration execution device, so that the configuration execution device configures the leaf network elements to be expanded according to the configuration information of the leaf network elements to be expanded, and configures the backbone network elements connected to the leaf network elements to be expanded according to the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded.

[0017] In the above solution, the controller can also communicate with the configuration execution device. After the controller obtains the configuration information of the leaf network element to be expanded and the network configuration information of the backbone network element connected to the leaf network element to be expanded, the controller sends the above information to the configuration execution device. Then the configuration execution device can receive the above information from the controller. Next, the configuration execution device configures the leaf network element to be expanded according to the configuration information of the leaf network element to be expanded, so that the leaf network element to be expanded can be connected to the server and the backbone network element. In addition, the configuration execution device can also configure the backbone network element connected to the leaf network element to be expanded according to the network configuration information of the backbone network element connected to the leaf network element to be expanded, and the backbone network element can be connected to the leaf network element to be expanded. In the embodiments of the present application, there are multiple implementation manners for the configuration execution device. For example, the configuration execution device can be integrated with the controller into a control terminal device, or the configuration execution device can also be a device independent of the controller, which is not limited herein.

[0018] In a possible implementation manner, the method further includes:

[0019] Displaying at least one of the following information: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the network configuration information of the backbone network element connected to the leaf network element to be expanded;

[0020] Receiving a modification instruction for at least one of the following information: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the network configuration information of the backbone network element connected to the leaf network element to be expanded;

[0021] According to the modification instruction, re-obtaining at least one of the following information: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the network configuration information of the backbone network element connected to the leaf network element to be expanded.

[0022] In the above solution, after the controller obtains the configuration information of the leaf network element to be expanded in the network to be expanded and the network configuration information of the backbone network element connected to the leaf network element to be expanded, the controller can also display at least one of the following information to the user: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the network configuration information of the backbone network element connected to the leaf network element to be expanded. For example, the controller can display the above information through the user interface (UI) on the display screen.

[0023] After the controller displays the above information to the user, the user can also issue a modification instruction for the above information. For example, the user can modify the topology of the network to be expanded, or the user can modify the configuration information of the leaf network element to be expanded, or the user can also modify the networking configuration information of the backbone network element, or the user can modify multiple pieces of the above information, so as to implement the modification of the expansion plan recommended by the controller according to the user's intention and achieve the expansion of the leaf network element according to the user's needs.

[0024] After the controller receives the modification instruction sent by the user, the controller can determine the information that the user needs to modify through the modification instruction and generate at least one of the following information according to the modification instruction: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the networking configuration information of the backbone network element connected to the leaf network element to be expanded. In the embodiment of the present application, the controller can modify the expansion plan according to the user's modification instruction, so that the modified expansion plan can better meet the user's expansion requirements for the leaf network element. At the same time, it is not necessary for the user to perform the expansion manually. The user only needs to trigger the modification instruction, and the controller can realize the automatic expansion of the leaf network element according to the user's needs, improving the expansion efficiency of the leaf network element.

[0025] Illustrated as follows, in the embodiment of the present application, the user can input an expansion intention to the controller, such as the number of leaf network elements that need to be expanded. Then the controller performs an online expansion plan based on the topology (TOPO) of the current network and outputs the topology of the network to be expanded, the configuration information of the leaf network element to be expanded, and the networking configuration information of the backbone network element. For example, the controller can determine the configuration information of the leaf network element to be expanded, the configuration information of the spine network element, and the link between the leaf network element to be expanded and the spine network element based on the characteristics of the Fabric network. The user can judge whether the expansion plan needs to be modified through the expansion plan presented on the controller. For example, the user can modify the above expansion plan and perform configuration simulation to confirm whether the configuration information of the leaf network element and the networking configuration information of the spine network element after expansion affect the current network. Then the user sends a confirmation instruction to the controller, and the controller can determine the final expansion plan according to the confirmation instruction to realize the user's online expansion and simulation.

[0026] In a possible implementation manner, the topology of the current network includes at least one of the following: the type and model of the network elements in the current network, and the information of the link between the current leaf network element and the backbone network element, where the type of the network elements in the current network includes backbone network elements and leaf network elements.

[0027] In the above solution, the types of network elements in the current network include backbone network elements and leaf network elements. For example, the current network may include one or more backbone network elements and one or more leaf network elements. Among them, one leaf network element needs to be connected to all backbone network elements respectively. At the same time, one backbone network element needs to be connected to all leaf network elements respectively.

[0028] The model number of the network element in the current network refers to the type identifier of the network element in the current network, which can be specifically determined according to the configuration information of the network element.

[0029] For example, the current network may include a current leaf network element, which is connected to the backbone network element, and there is a link between the current leaf network element and the backbone network element. The information of this link can be the port information at both ends of the link.

[0030] In a possible implementation manner, the topology of the network to be expanded includes: the number, type, model number of the leaf network elements to be expanded, and the information of the links between the leaf network elements to be expanded and the backbone network elements. Among them,

[0031] The information of the links between the leaf network elements to be expanded and the backbone network elements includes: the ports on the leaf network elements to be expanded and the ports on the backbone network elements respectively corresponding to the two ends of the links between the leaf network elements to be expanded and the backbone network elements.

[0032] In the above solution, the controller can determine the number of leaf network elements to be expanded, which refers to the number of leaf network elements expanded this time. For example, the value of this number can be default, that is, when the controller needs to expand the current network, two leaf network elements are default expanded each time.

[0033] In a possible implementation manner, the number of leaf network elements to be expanded is determined according to the access reliability configuration information of the current network and the number of servers to be expanded, where the servers to be expanded are used to connect the leaf network elements to be expanded; or,

[0034] The number of leaf network elements to be expanded is determined according to the received expansion instruction, and the expansion instruction is used to indicate the number of leaf network elements to be expanded.

[0035] In the above solution, the controller can also determine the number of leaf network elements to be expanded according to the access reliability configuration information of the current network and the number of servers to be expanded. Among them, the controller can obtain the number of servers to be expanded. The servers to be expanded refer to the servers that need to be added to the current network. The more the number of servers to be expanded, that is, the more leaf network elements need to be added to the current network. The servers to be expanded are used to connect the leaf network elements to be expanded. For example, if the number of servers to be expanded is 3, the controller can determine that the number of leaf network elements to be expanded is also 3. In addition, when determining the number of leaf network elements to be expanded, in addition to obtaining the number of servers to be expanded, the controller also needs to obtain the access reliability configuration information of the current network to determine whether the configuration requirements of the access reliability configuration information of the current network can support the expansion of 3 leaf network elements. If the configuration requirements of the access reliability configuration information of the current network can support the expansion of 3 leaf network elements, the controller can determine that the number of leaf network elements to be expanded is 3 according to the number of servers to be expanded being 3. If the configuration requirements of the access reliability configuration information of the current network can support the expansion of 2 leaf network elements, the controller can determine that 3 leaf network elements cannot be expanded according to the number of servers to be expanded being 3. At this time, the controller determines that the number of leaf network elements to be expanded is 2.

[0036] Alternatively, the controller can also receive an expansion instruction sent by the user. The expansion instruction is used to indicate the number of leaf network elements to be expanded. For example, the user can input the number of leaf network elements to be expanded through the client. The client generates an expansion instruction and sends the expansion instruction to the controller. The controller receives the expansion instruction from the client and determines the number of leaf network elements to be expanded according to the expansion instruction.

[0037] In a possible implementation manner, the type and model of the leaf network element to be expanded are determined according to the type and model of the current leaf network element.

[0038] In the above solution, the controller can obtain the type and model of the current leaf network element in the topology of the current network, and determine the type of the leaf network element to be expanded according to the type of the current leaf network element. For example, the controller determines that the type of the leaf network element to be expanded is the same as the type of the current leaf network element, and the model of the leaf network element to be expanded is the same as the model of the current leaf network element. Another example is that the controller determines that there is a pre-established matching relationship between the type of the leaf network element to be expanded and the type of the current leaf network element, and there is a preset matching relationship between the model of the leaf network element to be expanded and the model of the current leaf network element. The following is an example: If there are 10 current leaf network elements in the topology of the current network, and their types and models are both type 1 and model 1, and there are 3 current leaf network elements with types and models both being type 2 and model 2, then the type and model of the leaf network element to be expanded are type 1 and model 1. It is not limited that the type 2 and model 2 can also be determined as the type and model of the leaf network element to be expanded.

[0039] In a possible implementation, the port on the backbone network element corresponding to the link connecting the leaf network element to be expanded and the backbone network element is an idle port of the backbone network element; and / or,

[0040] The port of the leaf network element to be expanded is determined according to the port of the current leaf network element corresponding to the link connecting the current leaf network element and the backbone network element.

[0041] In the above solution, in the topology of the network to be expanded, the leaf network element to be expanded is connected to the backbone network element through a link. The idle port of the backbone network element can be connected to the port of this link, and the other port of this link is connected to the port of the leaf network element to be expanded. In the embodiments of the present application, the backbone network element has multiple ports, the backbone network element is connected to the leaf network element in the current network, and there are still idle ports on the backbone network element. The idle ports on the backbone network element can be used to connect the leaf network element to be expanded. Therefore, the connection between the leaf network element and the backbone network element can be realized through the idle ports of the backbone network element.

[0042] In addition, the topology of the network to be expanded includes leaf network elements to be expanded. The port through which the leaf network element to be expanded connects to the backbone network element can be determined according to the port of the current leaf network element connected to the backbone network element. For example, if the port 1 of the current leaf network element is connected to the backbone network element through a link, then the port 1 of the leaf network element to be expanded is connected to the backbone network element through a link. Therefore, in the embodiments of the present application, the port of the leaf network element to be expanded can be determined through the port of the current leaf network element. Without limitation, in the embodiments of the present application, the port on the leaf network element to be expanded can be the same as or close to the port on the current leaf network element where the link connecting the current leaf network element to the backbone network element is located. For example, if the port 1 of the current leaf network element is connected to the backbone network element through a link, and when the port 1 of the leaf network element to be expanded is faulty, the port 2 of the leaf network element to be expanded can also be used to connect to the backbone network element through a link, and the port 2 of the leaf network element to be expanded is a port close to the port 1 of the current leaf network element.

[0043] In a possible implementation manner, the configuration information of the leaf network element to be expanded includes: common configuration information and the networking configuration information of the leaf network element to be expanded.

[0044] The common configuration information is the common configuration information of all leaf network elements in the current network.

[0045] In the above solution, the configuration information of the leaf network element to be expanded may include the following two types of information. One is the common configuration information, and the other is the networking configuration information of the leaf network element to be expanded. Among them, the common configuration information is the common configuration information of all leaf network elements in the current network, that is, the common configuration information refers to the configuration information that is the same for all leaf network elements. This common configuration information can also be called the "baseline configuration". In the topology of the network to be expanded, all leaf network elements adopt this common configuration information. For an example illustration of the baseline configuration, please refer to the subsequent embodiments. Since the leaf network element to be expanded is added to the topology of the network to be expanded, and the leaf network element to be expanded can be connected to the backbone network element, it is necessary to obtain the networking configuration information of the leaf network element to be expanded. The networking configuration information of the leaf network element to be expanded refers to the configuration information adopted when the leaf network element is connected to the backbone network element in the network. This networking configuration information can also be called the "configuration resource pool". Therefore, for the leaf network element, the configuration information of the leaf network element may include: the baseline configuration of the leaf network element and the configuration resource pool. Among them, the baseline configuration is the configuration information that exists in all leaf network elements or most leaf network elements (for example, more than half of the leaf network elements), and the configuration resource pool is the respective different configuration information adopted by different leaf network elements when connecting to the backbone network element in the network.

[0046] In a possible implementation manner, the configuration information of the network elements in the current network includes:

[0047] Configuration information for networking the underlying underlay network and the upper overlay network, and Internet Protocol (IP) information for the interconnection of network elements in the current network.

[0048] In the above solution, the current network may include an underlay network and an overlay network. The configuration information of the network elements in the current network may include the configuration information required for networking the underlay network and the overlay network. Additionally, the configuration information of the network elements in the current network may include the IP information for the interconnection of network elements in the current network. The IP information for the interconnection of network elements in the current network may be the IP addresses when network elements are interconnected in the network. In an embodiment of the present application, the controller may determine the configuration information of the leaf network elements to be expanded through the configuration information of the network elements in the current network.

[0049] In a possible implementation manner, the interconnected IP information includes: the port IP addresses at both ends of the link between the leaf network element to be expanded and the backbone network element connected to the leaf network element to be expanded.

[0050] In the above solution, in the topology of the network to be expanded, the leaf network element to be expanded is connected to the backbone network element through a link. This link has two ports, respectively used to connect the leaf network element to be expanded and the backbone network element. The port IP addresses at both ends of this link may be the aforementioned interconnected IP information. In an embodiment of the present application, the configuration information of the network elements may include the port IP addresses at both ends of the link between the leaf network element to be expanded and the backbone network element. Therefore, the leaf network element to be expanded and the backbone network element can be connected through this port IP address.

[0051] In a possible implementation manner, the method further includes:

[0052] When the leaf network element to be expanded has already been connected to the backbone network element, the topology of the network to be expanded is accepted according to preset topology acceptance rules.

[0053] In the above solution, the controller can perform configuration analysis on the topology of the current network. For example, the controller can perform configuration analysis on the entire network of the Fabric. After the configuration analysis, the controller can automatically generate an expansion plan. After generating the expansion plan, the controller can also accept the expansion plan. The specific acceptance items can be flexibly configured. For example, the controller can detect the connectivity between the virtual tunnel end point (VTEP) IPs of the entire network, that is, it can detect whether the three-layer reachability exists between all VTEP IPs in the topology of the network to be expanded. In addition, the controller can also detect whether the topology of the actually expanded network is consistent with the topology of the planned network. The controller reads the topology of the new network to check whether it is consistent with the expansion plan. Among them, the topology of the planned network is the topology of the network obtained in the embodiment of the present application when waiting for expansion. After the new leaf network element goes online, the controller can also collect the topology of the actually expanded network, and perform topology check through the topology of the network to be expanded and the topology of the actually expanded network.

[0054] In a possible implementation manner, the method is executed by a controller.

[0055] In the above solution, the method for generating an expansion configuration can be implemented by a device for generating an expansion configuration. For example, the device for generating an expansion configuration can be used for expanding the data center network architecture. For example, it can automatically expand leaf network elements in the current network. Specifically, the device for generating an expansion configuration can be a controller. The controller analyzes the current topology of the Fabric architecture and the configuration information of the network elements in the current topology. By analyzing the topology and configuration information of the current network, it determines the topology of the network to be expanded, as well as the configuration information of the leaf network elements to be expanded and the configuration information of the backbone network elements in the network to be expanded, so as to realize the automatic expansion of the network. It greatly reduces the workload of network administrators, reduces the error probability of network expansion, and greatly improves the expansion efficiency.

[0056] In a second aspect, an embodiment of the present application further provides a controller, where the controller includes:

[0057] An obtaining module, configured to obtain the topology of the current network and the access reliability configuration information of the current network;

[0058] A processing module, configured to determine the topology of the network to be expanded based on the topology of the current network and the access reliability configuration information of the current network;

[0059] The obtaining module is further configured to obtain the configuration information of the leaf network elements to be expanded in the network to be expanded, and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded, based on the topology of the network to be expanded and the configuration information of the network elements in the current network.

[0060] In a possible implementation, a processing module is configured to configure a backbone network element connected to the leaf network element to be expanded based on the networking configuration information of the backbone network element connected to the leaf network element to be expanded.

[0061] In the above solution, the controller can obtain the networking configuration information of the backbone network element connected to the leaf network element to be expanded. The controller configures the backbone network element according to the networking configuration information of the backbone network element. For example, in the topology of the current network, the backbone network element is connected to the current leaf network element, and the controller uses networking configuration information 1 to configure the backbone network element at this time. In the topology of the network to be expanded, the backbone network element also needs to be connected to the leaf network element to be expanded. The controller obtains the networking configuration information 2 of the backbone network element, and the controller also needs to use the networking configuration information 2 to configure the backbone network element so that the backbone network element can be connected to the leaf network element to be expanded.

[0062] In a possible implementation, a processing module is configured to send the configuration information of the leaf network element to be expanded and the networking configuration information of the backbone network element connected to the leaf network element to be expanded to a configuration execution device, so that the configuration execution device configures the leaf network element to be expanded according to the configuration information of the leaf network element to be expanded, and configures the backbone network element connected to the leaf network element to be expanded according to the networking configuration information of the backbone network element connected to the leaf network element to be expanded.

[0063] In the above solution, the controller can also communicate with the configuration execution device. After the controller obtains the configuration information of the leaf network element to be expanded and the networking configuration information of the backbone network element connected to the leaf network element to be expanded, the controller sends the above information to the configuration execution device. Then the configuration execution device can receive the above information from the controller. Next, the configuration execution device configures the leaf network element to be expanded according to the configuration information of the leaf network element to be expanded, so that the leaf network element to be expanded can be connected to the server and the backbone network element. In addition, the configuration execution device can also configure the backbone network element connected to the leaf network element to be expanded according to the networking configuration information of the backbone network element connected to the leaf network element to be expanded, and the backbone network element can be connected to the leaf network element to be expanded. In the embodiments of the present application, there are multiple implementation manners for the configuration execution device. For example, the configuration execution device can be integrated with the controller into a control terminal device, or the configuration execution device can also be a device independent of the controller, which is not limited herein.

[0064] In a possible implementation, a processing module is configured to display at least one of the following pieces of information: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the networking configuration information of the backbone network element connected to the leaf network element to be expanded; receive a modification instruction for at least one of the following pieces of information: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the networking configuration information of the backbone network element connected to the leaf network element to be expanded; and re-obtain at least one of the following pieces of information according to the modification instruction: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the networking configuration information of the backbone network element connected to the leaf network element to be expanded.

[0065] In the above solution, after the controller obtains the configuration information of the leaf network element to be expanded in the network to be expanded and the networking configuration information of the backbone network element connected to the leaf network element to be expanded, the controller can further display at least one of the following pieces of information to the user: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the networking configuration information of the backbone network element connected to the leaf network element to be expanded. For example, the controller can display the above information through the UI on the display screen.

[0066] After the controller displays the above information to the user, the user can further issue a modification instruction for the above information. For example, the user can modify the topology of the network to be expanded, or the user can modify the configuration information of the leaf network element to be expanded, or the user can also modify the networking configuration information of the backbone network element, or the user can make modifications to the above multiple pieces of information, so as to implement the modification of the expansion plan recommended by the controller according to the user's intention and realize the expansion of the leaf network element according to the user's needs.

[0067] After the controller receives the modification instruction sent by the user, the controller can determine the information that the user needs to modify through the modification instruction, and generate at least one of the following pieces of information according to the modification instruction: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the networking configuration information of the backbone network element connected to the leaf network element to be expanded. In the embodiment of the present application, the controller can modify the expansion plan according to the user's modification instruction, so that the modified expansion plan can better meet the user's expansion requirements for the leaf network element. At the same time, it is not necessary for the user to perform the expansion manually. The controller can realize the automatic expansion of the leaf network element according to the user's needs only by triggering the modification instruction, which improves the expansion efficiency of the leaf network element.

[0068] In a possible implementation, the topology of the current network includes at least one of the following: the types and models of the network elements in the current network, and the information of the links connecting the current leaf network elements to the backbone network elements, where the types of the network elements in the current network include backbone network elements and leaf network elements.

[0069] In the above solution, the types of the network elements in the current network include backbone network elements and leaf network elements. For example, the current network may include one or more backbone network elements, and the current network may include one or more leaf network elements. Among them, one leaf network element needs to be connected to all backbone network elements respectively, and at the same time, one backbone network element needs to be connected to all leaf network elements respectively.

[0070] The model of the network element in the current network refers to the type identifier of the network element in the current network, which can be specifically determined according to the configuration information of the network element.

[0071] For example, the current network may include a current leaf network element, which is connected to the backbone network element, and there is a link between the current leaf network element and the backbone network element. The information of this link may be the port information at both ends of the link.

[0072] In a possible implementation, the topology of the network to be expanded includes: the quantity, type, model of the leaf network elements to be expanded, and the information of the links connecting the leaf network elements to be expanded to the backbone network elements, where

[0073] The information of the links connecting the leaf network elements to be expanded to the backbone network elements includes: the ports on the leaf network elements to be expanded and the ports on the backbone network elements respectively corresponding to both ends of the links connecting the leaf network elements to be expanded to the backbone network elements.

[0074] In the above solution, the controller can determine the quantity of the leaf network elements to be expanded, which refers to the quantity of the leaf network elements expanded this time. For example, the value of this quantity can be default, that is, when the controller needs to expand the current network, it defaults to expand two leaf network elements each time.

[0075] In a possible implementation, the quantity of the leaf network elements to be expanded is determined according to the access reliability configuration information of the current network and the quantity of the servers to be expanded, where the servers to be expanded are used to connect the leaf network elements to be expanded; or,

[0076] The quantity of the leaf network elements to be expanded is determined according to the received expansion instruction, and the expansion instruction is used to indicate the quantity of the leaf network elements to be expanded.

[0077] In the above solution, the controller can also determine the number of leaf network elements to be expanded according to the access reliability configuration information of the current network and the number of servers to be expanded. Among them, the controller can obtain the number of servers to be expanded. The servers to be expanded refer to the servers that need to be added to the current network. The more the number of servers to be expanded, that is, the more leaf network elements need to be added to the current network. The servers to be expanded are used to connect the leaf network elements to be expanded. For example, if the number of servers to be expanded is 3, the controller can determine that the number of leaf network elements to be expanded is also 3. In addition, when determining the number of leaf network elements to be expanded, the controller, in addition to obtaining the number of servers to be expanded, also needs to obtain the access reliability configuration information of the current network to determine whether the configuration requirements of the access reliability configuration information of the current network can support the expansion of 3 leaf network elements. If the configuration requirements of the access reliability configuration information of the current network can support the expansion of 3 leaf network elements, the controller can determine the number of leaf network elements to be expanded as 3 according to the number of servers to be expanded being 3. If the configuration requirements of the access reliability configuration information of the current network can support the expansion of 2 leaf network elements, the controller can determine that 3 leaf network elements cannot be expanded according to the number of servers to be expanded being 3. At this time, the controller determines that the number of leaf network elements to be expanded is 2.

[0078] Alternatively, the controller can also receive an expansion instruction sent by the user. The expansion instruction is used to indicate the number of leaf network elements to be expanded. For example, the user can input the number of leaf network elements to be expanded through the client. The client generates an expansion instruction and sends the expansion instruction to the controller. The controller receives the expansion instruction from the client and determines the number of leaf network elements to be expanded according to the expansion instruction.

[0079] In a possible implementation manner, the type and model of the leaf network elements to be expanded are determined according to the type and model of the current leaf network elements.

[0080] In the above solution, the controller can obtain the type and model of the current leaf network element in the topology of the current network, and determine the type of the leaf network element to be expanded according to the type of the current leaf network element. For example, the controller determines that the type of the leaf network element to be expanded is the same as the type of the current leaf network element, and the model of the leaf network element to be expanded is the same as the model of the current leaf network element. Another example is that the controller determines that there is a pre-established matching relationship between the type of the leaf network element to be expanded and the type of the current leaf network element, and there is a preset matching relationship between the model of the leaf network element to be expanded and the model of the current leaf network element. The following is an example. If there are 10 current leaf network elements in the topology of the current network, and their types and models are both type 1 and model 1, and there are 3 current leaf network elements with types and models both being type 2 and model 2, then the type and model of the leaf network element to be expanded are type 1 and model 1. It is not limited that the type 2 and model 2 can also be determined as the type and model of the leaf network element to be expanded.

[0081] In a possible implementation manner, the port on the backbone network element corresponding to the link connecting the leaf network element to be expanded and the backbone network element is an idle port of the backbone network element; and / or,

[0082] The port of the leaf network element to be expanded is determined according to the port of the current leaf network element corresponding to the link connecting the current leaf network element and the backbone network element.

[0083] In the above solution, in the topology of the network to be expanded, the leaf network element to be expanded is connected to the backbone network element through a link. The idle port of the backbone network element can connect to the port of this link, and the other port of this link connects to the port of the leaf network element to be expanded. In the embodiments of the present application, the backbone network element has multiple ports. The backbone network element is connected to the leaf network element in the current network, and there are still idle ports on the backbone network element. The idle ports on the backbone network element can be used to connect the leaf network element to be expanded. Therefore, the connection between the leaf network element and the backbone network element can be realized through the idle ports of the backbone network element.

[0084] In addition, the topology of the network to be expanded includes leaf network elements to be expanded. The port through which a leaf network element to be expanded connects to the backbone network element can be determined according to the port of the current leaf network element connected to the backbone network element. For example, if the port 1 of the current leaf network element is connected to the backbone network element through a link, then the port 1 of the leaf network element to be expanded is connected to the backbone network element through a link. Therefore, in the embodiments of the present application, the port of the leaf network element to be expanded can be determined through the port of the current leaf network element. Without limitation, in the embodiments of the present application, the port on the leaf network element to be expanded can be the same as or close to the port on the current leaf network element where the link connecting the current leaf network element to the backbone network element is located. For example, if the port 1 of the current leaf network element is connected to the backbone network element through a link, and the port 1 of the leaf network element to be expanded is faulty, the port 2 of the leaf network element to be expanded can also be used to connect to the backbone network element through a link, and the port 2 of the leaf network element to be expanded is a port close to the port 1 of the current leaf network element.

[0085] In a possible implementation manner, the configuration information of the leaf network element to be expanded includes: common configuration information and the networking configuration information of the leaf network element to be expanded.

[0086] The common configuration information is the common configuration information of all leaf network elements in the current network.

[0087] In the above solution, the configuration information of the leaf network element to be expanded may include the following two types of information. One is the common configuration information, and the other is the networking configuration information of the leaf network element to be expanded. Among them, the common configuration information is the common configuration information of all leaf network elements in the current network, that is, the common configuration information refers to the configuration information that is the same for all leaf network elements. This common configuration information can also be called the "baseline configuration". In the topology of the network to be expanded, all leaf network elements adopt this common configuration information. For an example illustration of the baseline configuration, see the subsequent embodiments. Since the leaf network element to be expanded is added to the topology of the network to be expanded, and the leaf network element to be expanded can be connected to the backbone network element, it is necessary to obtain the networking configuration information of the leaf network element to be expanded. The networking configuration information of the leaf network element to be expanded refers to the configuration information adopted when the leaf network element is connected to the backbone network element in the network. This networking configuration information can also be called the "configuration resource pool". Therefore, for a leaf network element, the configuration information of the leaf network element may include: the baseline configuration of the leaf network element and the configuration resource pool. Among them, the baseline configuration is the configuration information that exists in all leaf network elements or most leaf network elements (for example, more than half of the leaf network elements), and the configuration resource pool is the respective different configuration information adopted by different leaf network elements when connecting to the backbone network element in the network.

[0088] In a possible implementation manner, the configuration information of the network elements in the current network includes:

[0089] Configuration information for networking the underlying underlay network and the upper overlay network, and Internet Protocol (IP) information for the interconnection of network elements in the current network.

[0090] In the above solution, the current network may include an underlay network and an overlay network. The configuration information of network elements in the current network may include the configuration information required for networking the underlay network and the overlay network. Additionally, the configuration information of network elements in the current network may include the IP information for the interconnection of network elements in the current network. The IP information for the interconnection of network elements in the current network may be the IP addresses when network elements in the network are interconnected. In the embodiments of the present application, the controller may determine the configuration information of the leaf network elements to be expanded based on the configuration information of network elements in the current network.

[0091] In a possible implementation, the interconnected IP information includes: the port IP addresses at both ends of the link between the leaf network element to be expanded and the backbone network element connected to the leaf network element to be expanded.

[0092] In the above solution, in the topology of the network to be expanded, the leaf network element to be expanded is connected to the backbone network element through a link. This link has two ports, respectively used to connect the leaf network element to be expanded and the backbone network element. The port IP addresses at both ends of this link may be the aforementioned interconnected IP information. In the configuration information of network elements in the embodiments of the present application, it may include the port IP addresses at both ends of the link between the leaf network element to be expanded and the backbone network element. Therefore, the connection between the leaf network element to be expanded and the backbone network element can be achieved through this port IP address.

[0093] In a possible implementation, a processing module is used to, when the leaf network element to be expanded has been connected to the backbone network element, accept the topology of the network to be expanded according to a preset topology acceptance rule.

[0094] In the above solution, the controller can perform configuration analysis on the topology of the current network. For example, the controller can perform configuration analysis on the entire network of the Fabric. After the configuration analysis, the controller can automatically generate a capacity expansion plan. After generating the capacity expansion plan, the controller can also accept the capacity expansion plan, and the specific acceptance items can be flexibly configured. For example, the controller can detect the connectivity between the virtual tunnel endpoint (VTEP) IPs of the entire network, that is, it can detect whether all VTEP IPs in the topology of the network to be expanded are three-layer reachable. In addition, the controller can also detect whether the topology of the actually expanded network is consistent with the topology of the planned network. The controller reads the topology of the new network to check whether it is consistent with the capacity expansion plan. Among them, the topology of the planned network is the topology of the network obtained in the embodiment of the present application when waiting for capacity expansion. After the new leaf network element goes online, the controller can also collect the topology of the actually expanded network, and perform topology check through the topology of the network to be expanded and the topology of the actually expanded network.

[0095] In the second aspect of the present application, the component modules of the controller can also execute the steps described in the foregoing first aspect and various possible implementation manners. For details, see the description of the first aspect and various possible implementation manners above.

[0096] In a third aspect, an embodiment of the present application further provides a controller, which may include entities such as a terminal device or a chip. The controller includes: a processor and a memory; the memory is used to store instructions; the processor is used to execute the instructions in the memory, so that the controller executes the method described in the foregoing first aspect.

[0097] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which instructions are stored. When the instructions run on a computer, the computer is caused to execute the method described in the foregoing first aspect.

[0098] In a fifth aspect, an embodiment of the present application provides a computer program product containing instructions. When the computer program product runs on a computer, the computer is caused to execute the method described in the foregoing first aspect.

[0099] In a sixth aspect, the present application provides a chip system, which includes a processor for supporting the controller to implement the functions involved in the above aspects. For example, the processor is used to send or process the data and / or information involved in the above method. In a possible design, the chip system further includes a memory for storing the necessary program instructions and data of the controller. The chip system can be composed of chips or can include chips and other discrete devices. Description of the Drawings

[0100] Figure 1 Schematic diagram of the process block of a method for generating an expansion configuration provided by an embodiment of the present application;

[0101] Figure 2 Schematic diagram of the architecture of a current network provided by an embodiment of the present application;

[0102] Figure 3 Schematic diagram of the architecture of a network to be expanded provided by an embodiment of the present application;

[0103] Figure 4 Schematic diagram of the process block of a method for generating an expansion configuration provided by an embodiment of the present application;

[0104] Figure 5 Schematic diagram of the process block of a method for generating an expansion configuration provided by an embodiment of the present application;

[0105] Figure 6 Schematic diagram of the process block of a method for generating an expansion configuration provided by an embodiment of the present application;

[0106] Figure 7 Schematic diagram of the process block of a method for generating an expansion configuration provided by an embodiment of the present application;

[0107] Figure 8 Schematic diagram of the architecture of a Fabric network provided by an embodiment of the present application;

[0108] Figure 9 Schematic diagram of a controller for topology configuration analysis provided by an embodiment of the present application;

[0109] Figure 10 Schematic diagram of a controller for generating an expansion plan provided by an embodiment of the present application;

[0110] Figure 11 Schematic diagram of the structure of a controller provided by an embodiment of the present application;

[0111] Figure 12 Schematic diagram of the structure of a controller provided by an embodiment of the present application. Detailed implementation manners

[0112] Embodiments of the present application provide a method and a controller for generating an expansion configuration, which are used to improve the expansion efficiency of leaf network elements.

[0113] The embodiments of the present application will be described below with reference to the accompanying drawings.

[0114] In the description and claims of this application and the above-mentioned drawings, terms such as "first" and "second" are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances, which is only a way of distinguishing objects with the same attributes when describing embodiments of this application. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion, so that a process, method, system, product or device comprising a series of units need not be limited to those units, but may include other units not clearly listed or inherent to these processes, methods, products or devices.

[0115] In an embodiment of this application, a method for generating an expansion configuration is provided, which is used to implement the expansion of the data center network architecture. For example, new leaf network elements can be automatically expanded in the current network. The current network may specifically be a network with a Fabric architecture.

[0116] Illustrated as follows, a network element in a Fabric architecture may include leaf network elements and spine network elements. Among them, the leaf network elements are further divided into server leaf network elements connected to servers, leaf network elements connected to firewalls (FW), service leaf network elements for load balancing (LB), and border leaf network elements connected to external network elements of the Fabric. Among them, since the number of service leaf network elements and border leaf network elements is small, most scenarios of data center network expansion involve the need to expand server leaf network elements. In the subsequent embodiments, the expansion of server leaf network elements is taken as an example for illustration. Among them, expansion refers to adding new leaf network elements to the original Fabric architecture, adding configuration information to the new leaf network elements, and adding networking configuration information to the spine network elements connected to the new leaf network elements.

[0117] The embodiment of the present application further provides a device for generating an expansion configuration. The foregoing method for generating an expansion configuration can be implemented by the device for generating an expansion configuration. For example, the device for generating an expansion configuration can be used for expanding the data center network architecture. For example, it can automatically expand leaf network elements in the current network. Specifically, the device for generating an expansion configuration can be a controller. The controller analyzes the current topology of the Fabric architecture and the configuration information of the network elements in the current topology. By analyzing the topology and configuration information of the current network, it determines the topology of the network to be expanded, as well as the configuration information of the leaf network elements and backbone network elements to be expanded in the network to be expanded, thereby realizing automatic expansion of the network. This greatly reduces the workload of network administrators, reduces the error probability of network expansion, and greatly improves the expansion efficiency.

[0118] The controller provided by the embodiment of the present application can be implemented through software-defined networking (SDN). For example, the controller can specifically be an SDN controller. The SDN controller provided by the embodiment of the present application can get rid of the restrictions of hardware on the network architecture. The SND controller can modify the network just like upgrading and installing software, facilitating more application programs (APPs) to be quickly deployed on the network. Among them, SDN can realize network softwareization and improve network programmability. SDN can implement various functional characteristics better, faster, and more simply than the original network architecture.

[0119] The method for generating an expansion configuration provided by the embodiment of the present application can be applied to the expansion scenario of the data center network, simplifying the expansion processing method for the leaf network elements in the network. As Figure 1 shown, the method for generating an expansion configuration mainly includes the following steps:

[0120] Step 101: Obtain the topology of the current network and the access reliability configuration information of the current network.

[0121] Among them, the current network refers to the data center network before expansion. First, the controller analyzes the current network to obtain the topology of the current network. The topology of the current network may include which network elements are included in the current network and the connection relationships between these network elements. Further, the topology of the current network may also include the two ports of the link connected between the network elements in the current network. In addition, by analyzing the current network, the controller can also obtain the access reliability configuration information of the current network. Among them, the access reliability configuration information refers to the access-side reliability configuration information of the leaf network elements in the current network. For example, the access reliability configuration information may include at least one of the following: single machine, stacking, and cross-device link aggregation. Among them, a single machine means that a server is only connected to one leaf network element, but can be connected to multiple links of this leaf network element, and only provides link-level backup. If this leaf network element fails (goes down), the server cannot access the network. Stacking means that two or more leaf network elements in the current network are virtualized into one leaf network element. If a single device fails, the entire stacking system still remains working, that is, it can provide link-level and device-level backup, and the entire stacking system has only one control plane. Cross-device link aggregation, which can also be called cross-network element link aggregation, means that two or more links on different network elements are virtualized into one link, providing link-level and device-level backup, and the devices maintain independent control planes. It can be understood that for different implementation methods of the access reliability configuration information of the current network, a network expansion method adapted to the access reliability configuration information needs to be adopted. For example, if the access reliability configuration information is stacking, then when expanding the network, two or more leaf network elements need to be expanded in the manner of one virtualized leaf network element.

[0122] Illustrated as follows, the controller can perform configuration analysis through the Fabric topology (TOPO) interface of the controller. By default, the controller can perform configuration analysis on all server leaf network elements, or the user can also specify to the controller to analyze some of the leaf network elements. Through the configuration analysis of the current network, the controller can automatically obtain the topology of the current network and the access reliability configuration information of the current network.

[0123] In some embodiments of the present application, the topology of the current network includes at least one of the following: the type and model of the network elements in the current network, and the information of the link connecting the current leaf network element and the backbone network element. Among them, the types of network elements in the current network include backbone network elements and leaf network elements.

[0124] Specifically, the types of network elements in the current network include backbone network elements and leaf network elements. For example, the current network may include one or more backbone network elements, and the current network may include one or more leaf network elements. Among them, one leaf network element needs to be connected to all backbone network elements respectively. At the same time, one backbone network element needs to be connected to all leaf network elements respectively.

[0125] The model number of the network element in the current network refers to the type identifier of the network element in the current network, which can be specifically determined according to the configuration information of the network element.

[0126] For example, the current network may include the current leaf network element. This current leaf network element is connected to the backbone network element, and there is a link between the current leaf network element and the backbone network element. The information of this link can be the port information at both ends of this link.

[0127] Step 102: Determine the topology of the network to be expanded based on the topology of the current network and the access reliability configuration information of the current network.

[0128] In the embodiments of the present application, after the controller obtains the topology of the current network and the access reliability configuration information of this current network, the controller can automatically perform an expansion plan for the current network according to the configuration requirements of the access reliability configuration information of the current network, so as to obtain the topology of the network to be expanded. Among them, the network to be expanded refers to the preset expanded network obtained by performing an expansion plan on the current network. As Figure 2 and Figure 3 shown, for example, the topology of the current network may include 1 backbone network element (for example, it can be backbone network element a) and 3 leaf network elements. The 3 leaf network elements are respectively leaf network element a, leaf network element b, and leaf network element c. According to the configuration requirements of the access reliability configuration information of the current network, it is determined that leaf network element d can be expanded for this current network, and the to-be-expanded leaf network element d is connected to backbone network element a. Thus, the topology of the network to be expanded can be obtained, including: backbone network element a and 4 leaf network elements. The 4 leaf network elements are respectively leaf network element a, leaf network element b, leaf network element c, and the to-be-expanded leaf network element d. It should be noted that in the embodiments of the present application, by analyzing the topology of the current network and the access reliability configuration information of the current network, the topology of the network to be expanded can be automatically generated. This network to be expanded is obtained by adding the to-be-expanded leaf network element to the current network, and this to-be-expanded leaf network element meets the configuration requirements of the access reliability configuration information of the current network.

[0129] In some embodiments of the present application, the topology of the network to be expanded includes: the number, type, model number of the to-be-expanded leaf network element, and the information of the link between the to-be-expanded leaf network element and the backbone network element. Among them,

[0130] The information of the link connecting the leaf network element to be expanded and the backbone network element includes: the ports on the leaf network element to be expanded and the ports on the backbone network element corresponding to the two ends of the link connecting the leaf network element to be expanded and the backbone network element.

[0131] Specifically, the controller can determine the number of leaf network elements to be expanded, which refers to the number of leaf network elements to be expanded in this expansion. For example, the value of this number can be default. That is, when the controller needs to expand the current network, it defaults to expand two leaf network elements each time.

[0132] In some embodiments of the present application, the number of leaf network elements to be expanded is determined according to the access reliability configuration information of the current network and the number of servers to be expanded, where the servers to be expanded are used to connect the leaf network elements to be expanded; or,

[0133] The number of leaf network elements to be expanded is determined according to the received expansion instruction, and the expansion instruction is used to indicate the number of leaf network elements to be expanded.

[0134] Specifically, the controller can also determine the number of leaf network elements to be expanded according to the access reliability configuration information of the current network and the number of servers to be expanded. Among them, the controller can obtain the number of servers to be expanded. The servers to be expanded refer to the servers that need to be added to the current network. The more the number of servers to be expanded, that is, the more leaf network elements need to be added to the current network. The servers to be expanded are used to connect the leaf network elements to be expanded. For example, if the number of servers to be expanded is 3, the controller can determine that the number of leaf network elements to be expanded is also 3. In addition, when determining the number of leaf network elements to be expanded, in addition to obtaining the number of servers to be expanded, the controller also needs to obtain the access reliability configuration information of the current network to determine whether the configuration requirements of the access reliability configuration information of the current network can support the expansion of 3 leaf network elements. If the configuration requirements of the access reliability configuration information of the current network can support the expansion of 3 leaf network elements, the controller can determine the number of leaf network elements to be expanded as 3 according to the number of servers to be expanded being 3. If the configuration requirements of the access reliability configuration information of the current network can support the expansion of 2 leaf network elements, the controller can determine that it is impossible to expand 3 leaf network elements according to the number of servers to be expanded being 3. At this time, the controller determines that the number of leaf network elements to be expanded is 2.

[0135] Or, the controller can also receive the expansion instruction sent by the user, and the expansion instruction is used to indicate the number of leaf network elements to be expanded. For example, the user can input the number of leaf network elements to be expanded through the client, the client generates an expansion instruction, and sends the expansion instruction to the controller. The controller receives the expansion instruction from the client, and the controller determines the number of leaf network elements to be expanded according to this expansion instruction.

[0136] In some embodiments of the present application, the topology of the network to be expanded may further include the type and model of the leaf network elements to be expanded. Among them, the type of the leaf network element to be expanded is used to indicate that the type of the network element to be expanded is a leaf network element, and the model of the leaf network element to be expanded refers to the type identifier of the leaf network element to be expanded, which can be specifically determined according to the configuration information of the leaf network element.

[0137] In some embodiments of the present application, the topology of the network to be expanded may further include information about the link connecting the leaf network elements to be expanded and the backbone network elements. Among them, in the network to be expanded, the leaf network elements are connected to the backbone network elements, and specifically, a link is used for the connection. The topology of the network to be expanded may further include information about this link. Specifically, the information about the link connecting the leaf network elements to be expanded and the backbone network elements includes: the ports on the leaf network elements to be expanded and the ports on the backbone network elements corresponding to the two ends of the link connecting the leaf network elements to be expanded and the backbone network elements. Among them, a link has two ports at opposite ends. One port of the link is connected to the port of the leaf network element to be expanded, and the other port of the link is connected to the port of the backbone network element. It can be understood that the ports of the link and the ports of the network elements can be distinguished by different port serial numbers.

[0138] In the above embodiments of the present application, the topology of the network to be expanded generated by the controller includes: the number, type, model of the leaf network elements to be expanded, and information about the link connecting the leaf network elements to be expanded and the backbone network elements. Through the above information included in the topology of the network to be expanded, the topology of the network to be expanded can be accurately described, so as to facilitate the expansion of the leaf network elements according to the network to be expanded.

[0139] In some embodiments of the present application, the type and model of the leaf network elements to be expanded are determined according to the type and model of the current leaf network elements.

[0140] Among them, the controller can obtain the type and model of the current leaf network elements in the topology of the current network, and determine the type of the leaf network elements to be expanded according to the type of the current leaf network elements. For example, the controller determines that the type of the leaf network elements to be expanded is the same as the type of the current leaf network elements, and the model of the leaf network elements to be expanded is the same as the model of the current leaf network elements. Another example is that the controller determines that there is a pre-set matching relationship between the type of the leaf network elements to be expanded and the type of the current leaf network elements, and there is a preset matching relationship between the model of the leaf network elements to be expanded and the model of the current leaf network elements. The following is an example for illustration. If there are 10 current leaf network elements in the topology of the current network, and their types and models are both type 1 and model 1, and there are also 3 current leaf network elements with types and models both being type 2 and model 2, then the type and model of the leaf network elements to be expanded are type 1 and model 1. It is not limited that the type 2 and model 2 can also be determined as the type and model of the leaf network elements to be expanded.

[0141] Step 103: Based on the topology of the network to be expanded and the configuration information of the network elements in the current network, obtain the configuration information of the leaf network elements to be expanded in the network to be expanded, and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded.

[0142] Among them, the controller obtains the topology of the network to be expanded, obtains the leaf network elements to be expanded in the network to be expanded according to the topology of the network to be expanded, and the controller can also obtain the configuration information of the network elements in the current network. The configuration information of the network elements in the current network is the configuration information respectively adopted by the network elements included in the topology of the current network. The controller obtains the configuration information of the leaf network elements to be expanded in the network to be expanded based on the topology of the network to be expanded and the configuration information of the network elements in the current network, that is, the controller can obtain the configuration information of the leaf network elements to be expanded. Therefore, the controller can generate an expansion plan according to the configuration information of the leaf network elements to be expanded and recommend it to the user. In addition, the controller can also obtain the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded based on the topology of the network to be expanded and the configuration information of the network elements in the current network. Among them, the backbone network elements are included in the topology of the current network. When the current network needs to be expanded, a network to be expanded can be generated, and the backbone network elements are included in the topology of the network to be expanded. Since the topology of the network to be expanded adds the leaf network elements to be expanded, and the leaf network elements to be expanded need to be connected to the backbone network elements, the networking configuration information of the backbone network elements will also be updated. Therefore, the controller also needs to generate the networking configuration information of the backbone network elements. The networking configuration information of the backbone network elements refers to the configuration information adopted when the backbone network elements and the leaf network elements are connected and networked in the network. In the embodiments of the present application, the topology of the network to be expanded can be automatically generated, and the configuration information of the leaf network elements to be expanded and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded can be obtained. Therefore, manual configuration by network administrators is not required, and the expansion of leaf network elements can be automatically performed, improving the expansion efficiency of leaf network elements.

[0143] In some embodiments of the present application, the configuration information of the network elements in the current network includes:

[0144] The configuration information for networking the underlying network and the overlay network and the Internet Protocol (IP) information for the interconnection of network elements in the current network.

[0145] Among them, the current network may include an underlay network and an overlay network. The configuration information of network elements in the current network may include the configuration information required for networking the underlay network and the overlay network. Additionally, the configuration information of network elements in the current network may include the IP information for the interconnection of network elements in the current network. The IP information for the interconnection of network elements in the current network may be the IP addresses when network elements in the network are interconnected. In the embodiments of this application, the controller may determine the configuration information of the leaf network element to be expanded through the configuration information of network elements in the current network.

[0146] In some embodiments of this application, the interconnected IP information includes: the port IP addresses at both ends of the link between the leaf network element to be expanded and the backbone network element connected to the leaf network element to be expanded.

[0147] Among them, in the topology of the network to be expanded, the leaf network element to be expanded is connected to the backbone network element through a link. This link has two ports, which are respectively used to connect the leaf network element to be expanded and the backbone network element. The port IP addresses at both ends of this link may be the aforementioned interconnected IP information. In the embodiments of this application, the configuration information of network elements may include the port IP addresses at both ends of the link between the leaf network element to be expanded and the backbone network element. Therefore, the leaf network element to be expanded and the backbone network element can be connected through this port IP address.

[0148] Furthermore, in some embodiments of this application, the configuration information of the leaf network element to be expanded includes: common configuration information and the networking configuration information of the leaf network element to be expanded.

[0149] The common configuration information is the common configuration information of all leaf network elements in the current network.

[0150] Specifically, the configuration information of the leaf network element to be expanded can include the following two types of information. One is the common configuration information, and the other is the networking configuration information of the leaf network element to be expanded. Among them, the common configuration information is the common configuration information of all leaf network elements in the current network, that is, the common configuration information refers to the configuration information that is the same for all leaf network elements. This common configuration information can also be called the "baseline configuration". In the topology of the network to be expanded, all leaf network elements adopt this common configuration information. For an illustrative example of the baseline configuration, please refer to the subsequent embodiments. Since the leaf network element to be expanded is added to the topology of the network to be expanded, and the leaf network element to be expanded can be connected to the backbone network element, it is necessary to obtain the networking configuration information of the leaf network element to be expanded. The networking configuration information of the leaf network element to be expanded refers to the configuration information adopted when the leaf network element and the backbone network element are connected to form a network in the network. This networking configuration information can also be called the "configuration resource pool". Therefore, for a leaf network element, the configuration information of the leaf network element can include: the baseline configuration of the leaf network element and the configuration resource pool. Among them, the baseline configuration is the configuration information that exists in all leaf network elements or most leaf network elements (for example, more than half of the leaf network elements), and the configuration resource pool is the respective different configuration information adopted by different leaf network elements when connecting to the backbone network element in the network.

[0151] In some embodiments of the present application, the port on the backbone network element corresponding to the link connecting the leaf network element to be expanded and the backbone network element is the idle port of the backbone network element; and / or,

[0152] The port of the leaf network element to be expanded is determined according to the port of the current leaf network element corresponding to the link connecting the current leaf network element and the backbone network element.

[0153] Among them, in the topology of the network to be expanded, the leaf network element to be expanded and the backbone network element are connected by a link. The idle port of the backbone network element can be connected to the port of the link, and the other port of the link is connected to the port of the leaf network element to be expanded. In the embodiments of the present application, the backbone network element has multiple ports, and the backbone network element is connected to the leaf network elements in the current network. There are also idle ports on the backbone network element. The idle ports on the backbone network element can be used to connect the leaf network element to be expanded. Therefore, the connection between the leaf network element and the backbone network element can be realized through the idle ports of the backbone network element.

[0154] In addition, the topology of the network to be expanded includes leaf network elements to be expanded. The port through which a leaf network element to be expanded connects to a backbone network element can be determined based on the port of the current leaf network element connected to the backbone network element. For example, if port 1 of the current leaf network element is connected to the backbone network element through a link, then port 1 of the leaf network element to be expanded is connected to the backbone network element through a link. Therefore, in the embodiments of the present application, the port of the leaf network element to be expanded can be determined through the port of the current leaf network element. Without limitation, the port on the leaf network element to be expanded in the embodiments of the present application can be the same as or close to the port on the current leaf network element where the link connecting the current leaf network element to the backbone network element is located. For example, if port 1 of the current leaf network element is connected to the backbone network element through a link, and port 1 of the leaf network element to be expanded fails, port 2 of the leaf network element to be expanded can also be used to connect to the backbone network element through a link, and port 2 of the leaf network element to be expanded is a port close to port 1 of the current leaf network element.

[0155] In some embodiments of the present application, after the controller obtains the topology of the network to be expanded, the configuration information of the leaf network elements to be expanded in the network to be expanded, and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded, the controller can also generate an expansion plan and display the expansion plan to the user. For example, the expansion plan generated by the controller in the embodiments of the present application can include the topology of the network to be expanded, the configuration information of the leaf network elements to be expanded, and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded. In the embodiments of the present application, the user can determine the number of leaf network elements that can be expanded this time, the configuration information of the leaf network elements that can be expanded, and the networking configuration information of the backbone network elements connected to the leaf network elements that can be expanded through the expansion plan output by the controller.

[0156] In some embodiments of the present application, as Figure 4 shown, in addition to performing the foregoing steps 101 to 103, the method for generating an expansion configuration provided in the embodiments of the present application may further include the following steps:

[0157] 104. Configure the backbone network elements connected to the leaf network elements to be expanded based on the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded.

[0158] Among them, the controller can obtain the networking configuration information of the backbone network element connected to the leaf network element to be expanded. The controller configures the backbone network element according to the networking configuration information of the backbone network element. For example, in the topology of the current network, the backbone network element is connected to the current leaf network element. At this time, the controller configures the backbone network element with networking configuration information 1. In the topology of the network to be expanded, the backbone network element also needs to be connected to the leaf network element to be expanded. The controller obtains the networking configuration information 2 of the backbone network element, and the controller also needs to configure the backbone network element with networking configuration information 2 so that the backbone network element can be connected to the leaf network element to be expanded.

[0159] In some other embodiments of the present application, such as Figure 5 shown, the method for generating an expansion configuration provided by the embodiments of the present application, in addition to performing the foregoing steps 101 to 103, may further include the following steps:

[0160] 105. Send the configuration information of the leaf network element to be expanded and the networking configuration information of the backbone network element connected to the leaf network element to be expanded to the configuration execution device, so that the configuration execution device configures the leaf network element to be expanded and the backbone network element according to the configuration information of the leaf network element to be expanded, and configures the backbone network element connected to the leaf network element to be expanded according to the networking configuration information of the backbone network element connected to the leaf network element to be expanded.

[0161] Among them, the controller can also communicate with the configuration execution device. After the controller obtains the configuration information of the leaf network element to be expanded and the networking configuration information of the backbone network element connected to the leaf network element to be expanded, it sends the above information to the configuration execution device. Then the configuration execution device can receive the above information from the controller. Next, the configuration execution device configures the leaf network element to be expanded according to the configuration information of the leaf network element to be expanded, so that the leaf network element to be expanded can be connected to the server and the backbone network element. In addition, the configuration execution device can also configure the backbone network element connected to the leaf network element to be expanded according to the networking configuration information of the backbone network element connected to the leaf network element to be expanded, and the backbone network element can be connected to the leaf network element to be expanded. In the embodiments of the present application, there are multiple implementation manners for the configuration execution device. For example, the configuration execution device can be integrated with the controller into a control end device, or the configuration execution device can also be a device independent of the controller, which is not limited herein.

[0162] In some other embodiments of the present application, such as Figure 6 shown, the method for generating an expansion configuration provided by the embodiments of the present application, in addition to performing the foregoing steps 101 to 103, may further include the following steps:

[0163] 106. Display at least one of the following information: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the networking configuration information of the backbone network element connected to the leaf network element to be expanded.

[0164] Among them, after the controller obtains the configuration information of the leaf network element to be expanded in the network to be expanded and the networking configuration information of the backbone network element connected to the leaf network element to be expanded, the controller can also display at least one of the following information to the user: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the networking configuration information of the backbone network element connected to the leaf network element to be expanded. For example, the controller can display the above information through the user interface (UI) on the display screen.

[0165] 107. Receive a modification instruction for at least one of the following information: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the networking configuration information of the backbone network element connected to the leaf network element to be expanded.

[0166] Among them, after the controller displays the above information to the user, the user can also issue a modification instruction for the above information. For example, the user can modify the topology of the network to be expanded, or the user can modify the configuration information of the leaf network element to be expanded, or the user can also modify the networking configuration information of the backbone network element, or the user can modify multiple pieces of the above information, so as to realize modifying the expansion plan recommended by the controller according to the user's intention and achieve the expansion of the leaf network element according to the user's needs.

[0167] 108. According to the modification instruction, re-obtain at least one of the following information: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the networking configuration information of the backbone network element connected to the leaf network element to be expanded.

[0168] Among them, after the controller receives the modification instruction sent by the user, the controller can determine the information that the user needs to modify through the modification instruction, and generate at least one of the following information according to the modification instruction: the topology of the network to be expanded, the configuration information of the leaf network element to be expanded in the network to be expanded, and the networking configuration information of the backbone network element connected to the leaf network element to be expanded. In the embodiments of the present application, the controller can modify the expansion plan according to the user's modification instruction, so that the modified expansion plan can better meet the user's expansion requirements for the leaf network element. At the same time, it does not require the user to manually perform the expansion. The user only needs to trigger the modification instruction, and the controller can realize the automatic expansion of the leaf network element according to the user's needs, improving the expansion efficiency of the leaf network element.

[0169] Illustrated as follows, in the embodiments of the present application, a user may input an intention of expansion to a controller, for example, input the number of leaf network elements to be expanded, and then the controller performs an online expansion plan based on the topology (TOPO) of the current network, and outputs the topology of the network to be expanded, the configuration information of the leaf network elements to be expanded, and the networking configuration information of the backbone network elements. For example, the controller may determine the configuration information of the leaf network elements to be expanded, the configuration information of the spine network elements, and the links between the leaf network elements to be expanded and the spine network elements based on the characteristics of the Fabric network. The user may determine whether the expansion plan needs to be modified based on the expansion plan presented on the controller. For example, the user may modify the above expansion plan and perform configuration simulation to confirm whether the configuration information of the leaf network elements and the networking configuration information of the spine network elements after expansion affect the current network, and then the user sends a confirmation instruction to the controller, and the controller may determine the final expansion plan according to the confirmation instruction, realizing online expansion and simulation of the user.

[0170] In some other embodiments of the present application, as Figure 7 shown, the method for generating an expansion configuration provided by the embodiments of the present application may further include the following steps in addition to performing the foregoing steps 101 to 103:

[0171] 109. When the leaf network elements to be expanded are already connected to the backbone network elements, accept the topology of the network to be expanded according to a preset topology acceptance rule.

[0172] In the embodiments of the present application, the controller may perform configuration analysis on the topology of the current network. For example, the controller may perform configuration analysis on the entire network of the Fabric. After the configuration analysis, the controller may automatically generate an expansion plan. After generating the expansion plan, the controller may also accept the expansion plan. The specific acceptance items may be flexibly configured. For example, the controller may detect the connectivity between the virtual tunnel end point (VTEP) IPs of the entire network, that is, detect whether all the VTEP IPs in the topology of the network to be expanded are three-layer reachable. In addition, the controller may also detect whether the topology of the actually expanded network is consistent with the topology of the planned network. The controller reads the topology of the new network to check whether it is consistent with the expansion plan. Among them, the topology of the planned network is the topology of the network obtained in the embodiments of the present application when waiting for expansion. After the new leaf network elements are online, the controller may also collect the topology of the actually expanded network, and perform topology check through the topology of the network to be expanded and the topology of the actually expanded network.

[0173] As can be seen from the foregoing examples of the embodiments of the present application, in the embodiments of the present application, first, the topology of the current network and the access reliability configuration information of the current network are obtained. Then, based on the topology of the current network and the access reliability configuration information of the current network, the topology of the network to be expanded is determined. Finally, based on the topology of the network to be expanded and the configuration information of the network elements in the current network, the configuration information of the leaf network elements to be expanded in the network to be expanded, and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded are obtained. In the embodiments of the present application, by analyzing the topology of the current network, the network elements included in the current network and the connection relationship between the network elements in the current network can be obtained. By analyzing the access reliability configuration information of the current network, the requirements for the access-side reliability configuration of the network elements in the current network can be obtained. After the above analysis, the topology of the network to be expanded can be determined. For example, the topology of the network to be expanded may include the leaf network elements to be expanded and the backbone network elements connected to the leaf network elements to be expanded. Finally, by analyzing the configuration information of the network elements in the current network, the configuration information of the leaf network elements to be expanded and the networking configuration information of the backbone network elements can be obtained. In the embodiments of the present application, manual configuration by network administrators is not required, and the expansion of leaf network elements can be automatically performed, improving the expansion efficiency of leaf network elements.

[0174] To facilitate a better understanding and implementation of the above solutions of the embodiments of the present application, the following corresponding application scenarios are given for specific illustration.

[0175] In the embodiments of the present application, the controller is specifically an SND controller and the current network is a Fabric network as an example for illustration. As Figure 8 shown, the Fabric network may include two backbone network elements and multiple leaf network elements. Among them, each leaf network element is respectively connected to the backbone network element. For example, there may be various types of leaf network elements. For example, the leaf network element may specifically be a server leaf network element, a service leaf network element, or a border leaf network element. In addition, after expansion according to the embodiments of the present application, the Fabric network also includes a server leaf network element to be expanded, which may also be referred to as a new server leaf network element. The leaf network elements in the embodiments of the present application may also be connected to servers. For example, the server leaf network element is connected to physical servers and virtual servers, the service leaf network element may be connected to a firewall (FW) and a load balance (LB) device, and the border leaf network element is connected to an egress provider edge (PE) router.

[0176] The SDN controller stores the topology information of the current Fabric network. For example, the topology information includes all the leaf network elements and backbone network elements in the current Fabric network. The device roles in a Fabric network include leaf network elements and backbone network elements, where the leaf network elements are further divided into Server leafs connected to servers, service leafs connected to firewall (FW) and load balancer (LB) devices, and border leafs connected to external Fabric devices. Since the number of service leafs and border leafs is small, most scenarios of data center network expansion mainly involve expanding server leafs. Next, the expansion of server leafs will be taken as an example for illustration.

[0177] The application scenarios of the embodiments of this application mainly include: the configuration analysis process for the architecture of the Fabric network, and generating an expansion plan based on the configuration information of the network elements in the current network.

[0178] As Figure 9 shown, the controller starts the topology configuration analysis, which mainly includes the following processes:

[0179] Before starting the topology configuration and running state analysis in the embodiments of this application, first based on the following preset conditions: the controller has established a management channel with the network elements and can read the configuration and state information from the network elements. Here, the network elements refer to backbone network elements and leaf network elements.

[0180] The SDN controller (subsequently referred to as the controller) identifies the roles of the network elements in the topology managed by the controller. The roles are divided into two types: leaf network elements and backbone network elements.

[0181] There are various ways to identify the network element roles. For example, the user displays and specifies the roles of the network elements on the topology interface of the controller. For example, the user marks which virtual network elements are backbone network elements and which are leaf network elements. Another example is that the controller automatically obtains it through topology analysis, provided that all network elements enable the Link Layer Discovery Protocol (LLDP). The role rules are as follows:

[0182] Leaf network element: It only has a link with the backbone network element, there is no link between leaf network elements, and there is a server access link, and the server is connected to the leaf network element.

[0183] Backbone network element: It has a link with the leaf network element.

[0184] In the expansion plan of the embodiments of this application, for one or more leaf network elements already connected to the backbone network element, the configuration information of the expanded leaf network elements is obtained based on the configuration information of these leaf network elements.

[0185] S01. Obtain the configuration information of the leaf nodes.

[0186] Among them, the configuration information of the leaf network elements may include: the type and model of the leaf network elements, the access-side reliability configuration (such as single machine / stacking / cross-device link aggregation), and the ports used to connect to the backbone network elements.

[0187] S02. Obtain the configuration information of the backbone network elements.

[0188] Specifically, the idle ports of the backbone network elements can be obtained, and the border gateway protocol (BGP) route reflector address can be obtained.

[0189] S03. Obtain the network configuration information.

[0190] Specifically, the underlay network protocol and the overlay network protocol can be obtained.

[0191] For example, the underlay network protocol may include: the topology three-layer network protocol (such as open shortest path first (OSPF), intermediate system-to-intermediate system (IS-IS), external border gateway protocol (eBGP)), the interconnected IP addresses of the used backbone network elements and leaf network elements, the used VTEP addresses and VTEP MAC addresses.

[0192] For example, the overlay network protocol includes: the interconnected IP addresses of the used backbone network elements and leaf network elements, the used VTEP addresses and VTEP MAC addresses.

[0193] S04. Obtain the common configuration information of the network elements to be expanded.

[0194] Among them, the common configuration information can also be called the baseline configuration information. For example, it includes: the SDN controller address connected by the network elements, the network time protocol (NTP) server configuration information, the Authentication Authorization Accounting (AAA) server configuration information, and the simple network management protocol (SNMP) server configuration information.

[0195] Next, an example is given for the configuration analysis process of the controller. Configuration analysis is performed on the Fabric TOPO interface of the SDN controller. By default, the SDN controller performs configuration analysis on all server leaf network elements. It should be noted that users can also specify to analyze only some leaf network elements. The purpose of configuration analysis is to automatically obtain the baseline configuration and configuration resource pool of the server leaf network elements. Among them, the baseline configuration is the configuration information that exists in all server leaf network elements or most (more than one-half) of the server leaf network elements.

[0196] First, an example is given for the analysis of the baseline configuration.

[0197] For example, the baseline configuration is for multi-chassis link aggregation group (MLAG) networking, with the value being MLAG. The specific analysis method is as follows:

[0198] 1. Check if there is a dfs-group configuration on the device. For example, the configuration is as follows:

[0199] dfs-group 1

[0200] priority 150

[0201] source ip 19.12.253.11.

[0202] 2. A large number of MLAG configurations are made on the device's downstream ports. For example, the configuration is as follows:

[0203] interface eth-trunk 13

[0204] mode lacp-static

[0205] lacp timeout fast user-defined 9

[0206] dfs-group 1m-lag 13.

[0207] For example, the baseline configuration is for the underlay routing protocol, with the value being OSPF. The analysis method is as follows:

[0208] Check that the routing protocol configuration on the interconnection ports of the leaf and spine is OSPF. The specific code includes:

[0209] leaf:

[0210] ospf 1router-id 10.125.98.3

[0211] stub-router on-startup 720 include-stub / / Configure the stub router to improve the network convergence performance in failure scenarios. When the Server Leaf is the CE12800 series, the on-startup time interval is configured as 3000S. When the Server Leaf is the TOR, the time interval is configured as 720S

[0212] spf-schedule-interval millisecond 50

[0213] lsa-originate-interval intelligent-timer 500 50 100

[0214] lsa-arrival-interval 50 / / Optimize the three-layer architecture and the OSPF convergence time in the case of multiple ECMP between two physical devices

[0215] area 0.0.0.0

[0216] network 10.125.97.20 0.0.0.3

[0217] network 10.125.97.36 0.0.0.3 / / Establish routing neighbors with two Border Leaf devices respectively

[0218] network 10.125.98.3 0.0.0.0

[0219] network 10.125.99.2 0.0.0.0 / / Publish the Loopback address

[0220] #

[0221] interface 40GE1 / 0 / 1

[0222] description "to Border Leaf_1"

[0223] undo portswitch

[0224] ip address 10.125.97.22 255.255.255.252

[0225] ospf network-type p2p / / Configure the network type of the OSPF interface interconnected with the Border Leaf as P2P

[0226] #

[0227] spine:

[0228] ospf 1 router-id 10.125.98.1

[0229] stub-router on-startup 3000 include-stub / / Configure the Stub router to improve the network convergence performance in failure scenarios. When the Border Leaf is the CE12800 series, the on-startup time interval is configured to 3000S. When the Border Leaf is the TOR, the time interval is configured to 720S

[0230] area 0.0.0.0

[0231] network 10.125.97.20 0.0.0.3

[0232] network 10.125.97.24 0.0.0.3

[0233] network 10.125.97.28 0.0.0.3

[0234] network 10.125.97.32 0.0.0.3 / / Establish routing neighbors with 4 Server Leaf devices respectively

[0235] network 10.125.97.56 0.0.0.7 / / Publish the in-band management address of the firewall to establish routing

[0236] network 10.125.98.1 0.0.0.0

[0237] network 10.125.99.1 0.0.0.0 / / Publish the Loopback address

[0238] #

[0239] interface 40GE1 / 0 / 0

[0240] description "to CE6856-1"

[0241] undo portswitch

[0242] ip address 10.125.97.21 255.255.255.252

[0243] ospf network-type p2p / / Configure the connection with the Server Leaf.

[0244] For example, if the baseline configuration is for the management plane and the value is in-band or out-of-band, the analysis method is as follows:

[0245] Check if there is an IP address configured on the Meth0 interface. If there is no configured IP address, it is considered in-band. The specific code used is as follows:

[0246] leaf:

[0247] interface MEth0 / 0 / 0

[0248] shutdown.

[0249] For example, if the baseline configuration is for the SDN controller address and the value is 10.1.2.1, the analysis method is as follows:

[0250] Extract according to the sdn agent configuration of the leaf. The specific code used is as follows:

[0251] sdn agent

[0252] source-ip 10.10.10.10

[0253] controller-ip 10.1.2.1.

[0254] For example, if the baseline configuration is for the NTP server address and the value is 80.3.107.7, the analysis method is as follows:

[0255] Check the NTP server address configured on the device. The specific code used is as follows:

[0256] ntp server disable

[0257] ntp ipv6 server disable

[0258] ntp server source-interface all disable

[0259] ntp ipv6 server source-interface all disable

[0260] ntp unicast-server 80.3.107.7.

[0261] For example, if the baseline configuration is for the iBGP RR address and the values are 10.125.98.1; 10.125.98.2, the analysis method is as follows:

[0262] View the EVPN neighbors configured on the device. The specific code for use is as follows:

[0263] l2vpn-family evpn

[0264] policy vpn-target

[0265] peer 10.125.98.1 enable

[0266] peer 10.125.98.1 advertise irb / / Configure to advertise IRB routes to the BGP EVPN peer

[0267] peer 10.125.98.2 enable

[0268] peer 10.125.98.2 advertise irb.

[0269] Next, an example is given for the analysis of the resource pool configuration.

[0270] The analysis method is shown in Table 1:

[0271]

[0272] After the controller obtains the baseline configuration and the configuration resource pool, all the configurations of the server leaf network elements to be expanded can be generated through the baseline configuration and the configuration resource pool.

[0273] As Figure 10 shown, the controller starts to generate the expansion plan, which mainly includes the following processes:

[0274] S11. Generate the topology of the network to be expanded.

[0275] Among them, the topology of the network to be expanded can include the following: the type and model of the leaf network elements to be expanded, the connection relationship between the expanded leaf network elements and the backbone nodes, and the access reliability configuration information.

[0276] Among them, the type and model of the leaf network elements to be expanded can be specifically extracted from the results of the leaf network element configuration analysis. The connection relationship between the expanded leaf network elements and the backbone nodes can include the ports of the leaf network elements and the idle ports of the backbone network elements. If the access reliability configuration is stacking or cross-device link aggregation, a pair of leaf network elements are generated, and these two network elements are configured through.

[0277] An example is given as follows. The controller obtains the current network topology and the current access reliability configuration information.

[0278] The current network topology may include some or all of the type, model number of the current leaf network element, and information about the links connected to the spine network element. For example, the type of the leaf network element refers to whether the leaf is a switch or a router, the model number of the leaf is the specific model identification of the leaf, and the information about the links connected to the spine network element includes the ports at both ends of the link connecting the current leaf network element and the spine network element on the leaf network element to be expanded and the spine network element.

[0279] The access reliability configuration information refers to the reliability configuration for the server to access the leaf, which may include the stacking method or the cross-network element link aggregation method. Stacking may refer to virtualizing two or more switches into one switch, and cross-network element link aggregation may refer to virtualizing two or more links into one link.

[0280] For example, the controller can obtain the current network topology and access reliability configuration information from the current leaf network element through the configuration management (network configuration protocol, netconf) protocol, or can also obtain the current network topology and access reliability configuration information through the command line or the management information base (MIB).

[0281] The controller determines the network topology to be expanded based on the current network topology and access reliability configuration information.

[0282] The network topology to be expanded includes the number, type, model number of the leaf network element to be expanded, and information about the links connected to the spine network element. The information about the links includes the ports at both ends of the link connecting the leaf network element to be expanded and the backbone network element, respectively, on the leaf network element to be expanded and the spine network element.

[0283] The number of leaf network elements to be expanded can be determined according to the access reliability configuration information and the number of servers to be expanded. The access reliability information may refer to the reliability method for the current server to access the current leaf network element. The following is an example. When the number of servers to be expanded is large, the number of leaf network elements to be expanded will also be large. If n leaf network elements are required in a single-machine scenario, then in the reliability method of two-way stacking or cross-network element link aggregation scenario, 2n leaf network elements are required. In some embodiments, it can also be determined only according to the access reliability configuration information.

[0284] The type and model of the leaf network element to be expanded can be determined according to the type and model of the current leaf network element. For example, if there are currently 10 leaf network elements with the same type 1 and model 1, and another 3 leaf network elements with the same type 2 and model 2, then the type and model of the leaf network element to be expanded are type 1 and model 1. In some cases, type 2 and model 2 can also be determined as the type and model of the leaf network element.

[0285] The port on the spine where the link connected to the spine network element is located needs to be an idle port on the spine network element, and the port on the leaf network element to be expanded should be the same as or close to the port on the current leaf network element where the link connected to the spine network element is located. For example, if the current leaf network element uses a 40G Ethernet interface with a local port number of 1 / 0 / 0 to connect to the spine network element, then the leaf network element to be expanded should also use a 40G Ethernet interface with a local port number of 1 / 0 / 0 to connect to the spine network element.

[0286] S12. Obtain the network configuration information that needs to be added to the backbone network element.

[0287] Among them, the network configuration information that needs to be added to the backbone network element may include: the interconnection configuration between the backbone network element and the leaf network element.

[0288] S13. Generate the configuration information of the leaf network element to be expanded.

[0289] Specifically, the controller can reuse the baseline configuration to generate a new network configuration.

[0290] Illustrated as follows, based on the network topology to be expanded and the configuration information of the network elements in the current network, the controller obtains the configuration information of the leaf to be expanded and the network configuration information of the spine connected to the leaf.

[0291] In some embodiments of the present application, the configuration information of the network elements in the current network includes the configuration information of the current leaf network element and the configuration information of the backbone network element. The configuration information of the leaf to be expanded includes the common configuration of the leaf to be expanded and the network configuration of the leaf to be expanded. The common configuration is generally used for leaf network element management and / or environment-related configurations. In one example, the environment-related configuration includes the addresses of the NTP server, SDN controller, and / or network management in the current environment. The network configuration can be used to make the network elements in the topology IP reachable and the IP addresses between the network segments connected by different network elements reachable. For example, the IP addresses between router 1 and router 2 are reachable, and the IP addresses between network segment 1 connected by router 1 and network segment 2 connected by router 2 are reachable.

[0292] In some embodiments of the present application, the networking configuration information may include the configuration information for underlay and overlay networking and the interconnection IP information.

[0293] The underlay routing protocol configuration includes: a three-layer topology networking protocol, such as OSPF / IS-IS / eBGP, the used VTEP IP address, and the VTEP MAC address.

[0294] The overlay protocol configuration includes: the BGP EVPN route reflector and its client addresses. Among them, the backbone network element can be used as the route reflector, and the leaf network element is the client of the route reflector.

[0295] The interconnection IP information includes the port IP addresses at both ends of the direct connection link between the leaf network element and the spine network element, and these two IP addresses belong to the same network segment.

[0296] Different contents in the networking configuration information can be expressed by the same configuration command, and the parameters of the configuration commands for different contents of the network configuration information are not exactly the same. For example, the underlay routing protocol configuration information of a managed network element may include the network segment IP addresses published by the IGP (Interior Gateway Protocol); the overlay BGPEVPN protocol configuration information of a managed network element may include the peer addresses of the BPG (Border Gateway Protocol) EVPN.

[0297] Next, a specific example is used to illustrate the networking configuration information.

[0298] The networking configuration information 1 is the current networking configuration information, and the networking configuration information 2 is the networking configuration information of the leaf network element to be expanded.

[0299] The networking configuration information 1 includes:

[0300] ospf 1router-id 10.125.98.2

[0301] bfd all-interfaces enable

[0302] bfd all-interfaces min-tx-interval 500min-rx-interval 500detect-multiplier3lsa-arrival-interval intelligent-timer 50 50 50

[0303] area 0.0.0.0

[0304] network 10.125.97.112 0.0.0.3

[0305] network 10.125.97.116 0.0.0.3

[0306] network 10.125.98.2 0.0.0.0

[0307] network 10.125.99.1 0.0.0.0。

[0308] The network configuration information 2 includes:

[0309] ospf 1 router-id 10.125.98.7

[0310] bfd all-interfaces enable

[0311] bfd all-interfaces min-tx-interval 500 min-rx-interval 500 detect-multiplier 3 lsa-arrival-interval intelligent-timer 50 50 50

[0312] area 0.0.0.0

[0313] network 10.125.97.20 0.0.0.3

[0314] network 10.125.97.24 0.0.0.3

[0315] network 10.125.97.28 0.0.0.3。

[0316] Both sets of configuration information include OSPF1, both include bfd all-interfaces enable, bfd all-interfaces min-tx-interval 500 min-rx-interval 500 detect-multiplier 3 lsa-arrival-interval intelligent-timer 50 50 50; the value of area is 0.0.0.0. The values of router-id in these two configuration information are different, indicating that these are two different devices; the routes advertised in these two configuration information are also different, indicating that these two devices can route packets to different network segments.

[0317] S14. Export the expansion plan.

[0318] Among them, the expansion plan exported by the controller may include: the number, type, and model of leaf nodes; the connection relationship between backbone network elements and leaf network elements; and the configuration information of leaf nodes.

[0319] Illustrated as follows, configure the leaf to be expanded and the spine connected to the leaf based on the configuration information of the leaf to be expanded and the network configuration information of the spine connected to the leaf. Based on the configuration, network expansion for the current network can be achieved.

[0320] In the embodiment of the present application, the configuration analysis of the current topology refers to the configuration analysis of the entire network of the Fabric. After the configuration analysis, the controller can automatically generate an expansion plan.

[0321] After generating the expansion plan, it may also include the acceptance process of the expansion plan.

[0322] Specific acceptance items can be flexibly configured. For example, the connectivity detection between VTEP IPs across the network. Another example is topology checking. The controller reads the new topology to check if it is consistent with the expansion plan. Among them, the planned topology is the topology obtained in the embodiment of the present application during network expansion. After the new leaf network element goes online, the actual expanded topology is also collected, and topology checking is performed through the topology to be expanded and the actual expanded topology.

[0323] From the foregoing illustration, it can be seen that the embodiment of the present application provides a method for expanding a data center network according to the user's input intention. Through the analysis of the configuration of network elements in the Fabric network, it recommends the added configuration and networking (the connection between leaf network elements and spine network elements) on the leaf network elements to be expanded and the connected spine network elements. The embodiment of the present application has the characteristic of wide applicability. Because of the configuration analysis process, various different networkings in the data center can be quickly supported. It can not only generate the configuration on the network side of the leaf switch, but also recommend the configuration for the leaf switch to access the server according to the number of servers input by the user. For example, the configurations that can be adopted include link aggregation (Eth-trunk) and MLAG.

[0324] In the embodiment of the present application, an SDN controller is adopted. The controller can analyze the current topology of the Fabric network and the configuration information of network elements in the current network, and then generate a recommended expansion plan. The expansion plan may include: the number of leaf network elements that can be expanded, the configuration information of the expanded leaf network elements, and the spine network elements connected to the leaf network elements. The embodiment of the present application can greatly reduce the workload of network administrators, reduce the probability of errors, and greatly improve the efficiency of network expansion.

[0325] It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that this application is not limited by the described action sequence, because according to this application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0326] To facilitate better implementation of the above solutions of the embodiments of this application, relevant devices for implementing the above solutions are also provided below.

[0327] As Figure 11 shown, an embodiment of this application provides a controller 1100, including:

[0328] An acquisition module 1101, configured to acquire the topology of the current network and the access reliability configuration information of the current network;

[0329] A processing module 1102, configured to determine the topology of the network to be expanded based on the topology of the current network and the access reliability configuration information of the current network;

[0330] The acquisition module 1101 is further configured to acquire the configuration information of the leaf network elements to be expanded in the network to be expanded, and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded, based on the topology of the network to be expanded and the configuration information of the network elements in the current network.

[0331] In some embodiments of this application, the processing module 1102 is further configured to configure the backbone network elements connected to the leaf network elements to be expanded, based on the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded.

[0332] In some embodiments of this application, the processing module 1102 is further configured to send the configuration information of the leaf network elements to be expanded and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded to a configuration execution device, so that the configuration execution device configures the leaf network elements to be expanded according to the configuration information of the leaf network elements to be expanded, and configures the backbone network elements connected to the leaf network elements to be expanded according to the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded.

[0333] In some embodiments of the present application, the processing module 1102 is further configured to display at least one of the following information: the topology of the network to be expanded, the configuration information of the leaf network elements to be expanded in the network to be expanded, and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded; receive modification instructions for at least one of the following information: the topology of the network to be expanded, the configuration information of the leaf network elements to be expanded in the network to be expanded, and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded; and re-obtain at least one of the following information according to the modification instructions: the topology of the network to be expanded, the configuration information of the leaf network elements to be expanded in the network to be expanded, and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded.

[0334] In some embodiments of the present application, the topology of the current network includes at least one of the following: the type and model of the network elements in the current network, and the information of the links connecting the current leaf network elements and the backbone network elements, where the types of the network elements in the current network include backbone network elements and leaf network elements.

[0335] In some embodiments of the present application, the topology of the network to be expanded includes: the number, type, and model of the leaf network elements to be expanded, and the information of the links connecting the leaf network elements to be expanded and the backbone network elements, where

[0336] The information of the links connecting the leaf network elements to be expanded and the backbone network elements includes: the ports on the leaf network elements to be expanded and the ports on the backbone network elements respectively corresponding to the two ends of the links connecting the leaf network elements to be expanded and the backbone network elements.

[0337] In some embodiments of the present application, the number of the leaf network elements to be expanded is determined according to the access reliability configuration information of the current network and the number of servers to be expanded, where the servers to be expanded are used to connect the leaf network elements to be expanded; or,

[0338] The number of the leaf network elements to be expanded is determined according to the received expansion instruction, where the expansion instruction is used to indicate the number of the leaf network elements to be expanded.

[0339] In some embodiments of the present application, the type and model of the leaf network elements to be expanded are determined according to the type and model of the current leaf network elements.

[0340] In some embodiments of the present application, the ports on the backbone network elements corresponding to the links connecting the leaf network elements to be expanded and the backbone network elements are the idle ports of the backbone network elements; and / or,

[0341] The ports of the leaf network element to be expanded are determined according to the ports of the current leaf network element corresponding to the links connecting the current leaf network element to the backbone network element.

[0342] In some embodiments of the present application, the configuration information of the leaf network element to be expanded includes: common configuration information and the networking configuration information of the leaf network element to be expanded.

[0343] The common configuration information is the common configuration information of all leaf network elements in the current network.

[0344] In some embodiments of the present application, the configuration information of the network elements in the current network includes:

[0345] The configuration information for networking the basic underlay network and the upper overlay network and the Internet Protocol (IP) information for the interconnection of network elements in the current network.

[0346] In some embodiments of the present application, the interconnected IP information includes: the port IP addresses at both ends of the link between the leaf network element to be expanded and the backbone network element connected to the leaf network element to be expanded.

[0347] In some embodiments of the present application, the processing module 1102 is further configured to, when the leaf network element to be expanded has been connected to the backbone network element, accept the topology of the network to be expanded according to a preset topology acceptance rule.

[0348] As can be seen from the examples in the foregoing embodiments, in the embodiments of the present application, first, the topology of the current network and the access reliability configuration information of the current network are obtained. Then, based on the topology of the current network and the access reliability configuration information of the current network, the topology of the network to be expanded is determined. Finally, based on the topology of the network to be expanded and the configuration information of the network elements in the current network, the configuration information of the leaf network element to be expanded in the network to be expanded and the networking configuration information of the backbone network element connected to the leaf network element to be expanded are obtained. In the embodiments of the present application, the network elements included in the current network and the connection relationships between the network elements in the current network can be obtained by analyzing the topology of the current network. The requirements for the access-side reliability configuration of the network elements in the current network can be obtained by analyzing the access reliability configuration information of the current network. After the above analysis, the topology of the network to be expanded can be determined. For example, the topology of the network to be expanded may include the leaf network element to be expanded and the backbone network element connected to the leaf network element to be expanded. Finally, by analyzing the configuration information of the network elements in the current network, the configuration information of the leaf network element to be expanded and the networking configuration information of the backbone network element can be obtained. In the embodiments of the present application, manual configuration by the network administrator is not required, and the expansion of the leaf network element can be automatically performed, improving the expansion efficiency of the leaf network element.

[0349] In some embodiments of the present application, the controllers in the above embodiments can all be implemented by a device as shown in Figure 12 .

[0350] The device 1200 includes at least one processor 1201, a communication bus 1202, a memory 1203, and at least one communication interface 1204. The device 1200 can be a general-purpose computer or server or a dedicated computer or server.

[0351] The processor 1201 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the solution of the embodiments of the present application.

[0352] The communication bus 1202 may include a path for transmitting information between the above components.

[0353] The communication interface 1204 can be any transceiver or IP port or bus interface, etc., for communicating with internal or external devices or apparatuses or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0354] The memory 1203 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but not limited thereto. The memory can exist independently and be connected to the processor through a bus. The memory can also be integrated with the processor.

[0355] Among them, the memory 1203 is used to store the application program code for implementing the solutions of the embodiments of the present application, and is controlled by the processor 1201 to execute. The processor 1201 is used to execute the application program code stored in the memory 1203, so as to implement the functions of the encoding end and the decoding end in the embodiments of the application.

[0356] In a specific implementation, as an embodiment, the processor 1201 may include one or more CPUs, such as Figure 12 CPU0 and CPU1 in

[0357] In a specific implementation, as an embodiment, the device 1200 may include multiple processors, such as Figure 12 the processor 1201 and the processor 1208 in

[0358] Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. Here, the processor may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0359] When Figure 12 the device shown is a chip, the function / implementation process of the communication interface 1204 may also be implemented through pins or circuits, etc. The memory is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip.

[0360] It should be noted that for the information interaction, execution process, etc. between the above device modules / units, since it is based on the same concept as the method embodiments of the present application, the technical effects brought by it are the same as those of the method embodiments of the present application. For the specific content, reference may be made to the description in the foregoing method embodiments of the present application, and details are not described herein again.

[0361] The embodiments of the present application further provide a computer storage medium, wherein the computer storage medium stores a program, and the program executes some or all of the steps recorded in the above method embodiments.

[0362] In addition, it should be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, in the drawings of the device embodiments provided in the present application, the connection relationships between modules indicate that they have communication connections, which can be specifically implemented as one or more communication buses or signal lines.

[0363] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by dedicated hardware including application-specific integrated circuits, dedicated CPUs, dedicated memories, dedicated components, etc. Generally, functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structures used to implement the same function can also be various, such as analog circuits, digital circuits or dedicated circuits. However, for the present application, in more cases, software program implementation is a better implementation method. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a readable storage medium, such as a floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk or optical disc of a computer, and includes several instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present application.

[0364] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product.

[0365] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that includes one or more integrated available media. The available medium may be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Claims

1. A method for generating an expansion configuration, characterized in that, The method includes: Obtaining the topology of the current network and the access reliability configuration information of the current network; Determining the topology of the network to be expanded based on the topology of the current network and the access reliability configuration information of the current network; Based on the topology of the network to be expanded and the configuration information of the network elements in the current network, obtaining the configuration information of the leaf network elements to be expanded in the network to be expanded, and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded.

2. The method according to claim 1, wherein The method further includes: Configuring the backbone network elements connected to the leaf network elements to be expanded based on the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded.

3. The method according to claim 1, characterized in that, The method further includes: Sending the configuration information of the leaf network elements to be expanded and the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded to a configuration execution device, so that the configuration execution device configures the leaf network elements to be expanded according to the configuration information of the leaf network elements to be expanded, and configures the backbone network elements connected to the leaf network elements to be expanded according to the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded.

4. The method according to any one of claims 1 to 3, characterized in that The method further includes: Displaying at least one of the following information: the topology of the network to be expanded, the configuration information of the leaf network elements to be expanded in the network to be expanded, the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded; Receiving a modification instruction for at least one of the following information: the topology of the network to be expanded, the configuration information of the leaf network elements to be expanded in the network to be expanded, the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded; According to the modification instruction, re-obtaining at least one of the following information: the topology of the network to be expanded, the configuration information of the leaf network elements to be expanded in the network to be expanded, the networking configuration information of the backbone network elements connected to the leaf network elements to be expanded.

5. The method according to any one of claims 1 to 3, characterized in that The topology of the current network includes at least one of the following: the type, model of the network elements in the current network, the information of the links connecting the current leaf network elements and the backbone network elements, where the types of the network elements in the current network include backbone network elements and leaf network elements.

6. The method according to any one of claims 1 to 3, characterized in that The topology of the network to be expanded includes: the number, type, model of the leaf network elements to be expanded, the information of the links connecting the leaf network elements to be expanded and the backbone network elements, where, The information of the links connecting the leaf network elements to be expanded and the backbone network elements includes: the ports on the leaf network elements to be expanded and the ports on the backbone network elements respectively corresponding to the two ends of the links connecting the leaf network elements to be expanded and the backbone network elements.

7. The method according to claim 6, wherein The number of the leaf network elements to be expanded is determined according to the access reliability configuration information of the current network and the number of servers to be expanded, and the servers to be expanded are used to connect the leaf network elements to be expanded; Or, The number of the leaf network elements to be expanded is determined according to the received expansion instruction, and the expansion instruction is used to indicate the number of the leaf network elements to be expanded.

8. The method according to claim 6, wherein The type and model of the leaf network elements to be expanded are determined according to the type and model of the current leaf network elements.

9. The method according to claim 6, wherein The port on the backbone network element corresponding to the link connecting the leaf network element to be expanded and the backbone network element is an idle port of the backbone network element; and / or, The port of the leaf network element to be expanded is determined according to the port of the current leaf network element corresponding to the link connecting the current leaf network element and the backbone network element.

10. The method according to any one of claims 1 to 3, characterized in that, The configuration information of the leaf network element to be expanded includes: common configuration information and the network configuration information of the leaf network element to be expanded, The common configuration information is the common configuration information of all leaf network elements in the current network.

11. The method according to any one of claims 1 to 3, characterized in that, The configuration information of the network elements in the current network includes: The configuration information for networking the basic underlay network and the upper overlay network and the Internet Protocol (IP) information for the interconnection of network elements in the current network.

12. The method according to claim 11, wherein The interconnected IP information includes: the port IP addresses at both ends of the link between the leaf network element to be expanded and the backbone network element connected to the leaf network element to be expanded.

13. The method according to any one of claims 1 to 3, characterized in that, The method further includes: When the leaf network element to be expanded has been connected to the backbone network element, the topology of the network to be expanded is accepted according to a preset topology acceptance rule.

14. The method according to any one of claims 1 to 3, characterized in that, The method is executed by a controller.

15. A controller, characterized in that, The controller includes: An acquisition module, configured to acquire the topology of the current network and the access reliability configuration information of the current network; A processing module, configured to determine the topology of the network to be expanded based on the topology of the current network and the access reliability configuration information of the current network; The acquisition module is further configured to acquire, based on the topology of the network to be expanded and the configuration information of the network elements in the current network, the configuration information of the leaf network element to be expanded in the network to be expanded, and the network configuration information of the backbone network element connected to the leaf network element to be expanded.

16. A controller, characterized in that, The controller includes: a processor and a memory; the processor and the memory communicate with each other; The memory is used to store instructions; The processor is used to execute the instructions in the memory and execute the method according to any one of claims 1 to 13.

17. A computer-readable storage medium, including instructions, which when running on a computer, cause the computer to execute the method according to any one of claims 1 to 13.

Images