Automatic network device configuration

Through the management service, the management service automatically recommends and assigns network device roles and calculates the bucket factor based on the number of network links, the problem of low network configuration management in private cloud environments is solved, and more efficient network orchestration and virtual network creation are achieved.

CN118075130BActive Publication Date: 2024-11-08HEWLETT PACKARD ENTERPRISE DEV LP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410279154.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2023-06-16
Filing Date
2024-03-12
Publication Date
2024-11-08
Estimated Expiration
2044-03-12

AI Technical Summary

Technical Problem

In private cloud environments, it is difficult for prior art to efficiently and automatically configure and manage network devices to support the creation and orchestration of virtual networks, resulting in inefficient network management.

Method used

By automatically recommending and assigning network device roles using management services, calculating bucketing factors based on the number of network links, grouping network devices and applying corresponding configurations to achieve fast and accurate network device role allocation and virtual network creation.

Benefits of technology

It improves the efficiency of network management and orchestration, adapts to network devices with different network links, provides faster and more accurate bucketing methods, and enhances the flexibility and scalability of private cloud environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118075130B_ABST
    Figure CN118075130B_ABST
Patent Text Reader

Abstract

Embodiments of the present disclosure relate to automatic network device configuration. In an example implementation consistent with the features disclosed herein, network devices of a physical network are bucketed based on a statistical analysis of the number of network links of the network devices to achieve automatic configuration. The number of network links of each network device is identified. A bucketing factor of the network device is calculated. The bucketing factor is equal to the sum of the mean and confidence interval values ​​of the number of network links of the network device. A role is recommended for a provisioned network device based on the bucketing factor. The role is assigned to the provisioned network device. Based on the role assigned to the provisioned network device, the network device configuration is applied to the provisioned network device. A virtual network is created on the physical network.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] Overlay networking allows the creation of virtual networks that run on top of the physical network. It implements the abstraction of the underlying network devices, thereby providing flexibility, scalability, and isolation in the network. In overlay networking, virtual networks are created using software-defined networking techniques. Network packets can traverse the physical network, although it looks like they belong to the virtual network.

[0002] In a private cloud environment, overlay networking can be used to support network virtualization and provide network connectivity between cloud components (e.g., virtual machines, containers, etc.). For example, cloud components can be assigned to specific virtual networks so that they can communicate even if they are distributed across different physical host servers or data centers. Virtual networks can be logically segmented and isolated from each other and from the underlying physical network. Virtual networks can be created, modified, or deleted as needed in a private cloud environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Aspects of the present disclosure are best understood from the following detailed description when read with the accompanying figures.

[0004] Figure 1 is a block diagram of a private cloud environment according to some implementations.

[0005] Figure 2 is a block diagram of a physical network according to some implementation.

[0006] Figure 3 is a diagram of a network device provisioning method according to some implementations.

[0007] Figure 4 is a block diagram of a physical network according to some other implementation.

[0008] Figure 5 It is a diagram of a network device orchestration method according to some implementations.

[0009] Corresponding numerals and symbols in the different figures generally refer to corresponding parts unless otherwise indicated.The figures are drawn to clearly illustrate the relevant aspects of the disclosure and are not necessarily drawn to scale. DETAILED DESCRIPTION

[0010] The following disclosure provides many different examples for implementing different features. Specific examples of components and arrangements are described below to simplify the disclosure. Of course, these are merely examples and are not intended to be limiting.

[0011] One component of cloud orchestration is the orchestration of virtual networks using overlay networking. During the orchestration of virtual networks, the underlying physical network is configured before the virtual network is created. For example, network device configurations can be pushed to network devices on the physical network in preparation for the creation of the virtual network.

[0012] A network device such as a switch can be assigned a role based on the role of the network device in the physical network. For example, in a data center (DC) network topology with a leaf-spine architecture, a switch can be a higher-level switch (e.g., a spine switch) or a lower-level switch (e.g., a leaf switch). Similarly, in a campus network topology with a hierarchical architecture, a switch can be a higher-level switch (e.g., a core switch or an aggregator switch) or a lower-level switch (e.g., an access switch). Network device configurations are pushed to network devices based on the roles assigned to them. To assist in cloud orchestration, roles can be automatically recommended for assignment to network devices. The network administrator can then agree or disagree with the recommended roles. If the recommendations are fast and accurate, automatically recommending and assigning roles to network devices can improve the efficiency of network management.

[0013] In an example implementation, roles for network devices of a physical network are recommended based on the number of network links for each of the network devices. A network link is a physical connection between network devices that can be discovered via the Link Layer Discovery Protocol (LLDP). Each network device is bucketed based on the number of links it has to neighboring network devices.

[0014] In particular, the bucketing factor can be calculated via statistical analysis. The bucketing factor is equal to the sum of the mean and confidence interval values ​​of the number of network links for the network device. The network devices can then be grouped by comparing the number of network links with the bucketing factor.

[0015] The network devices in the lower level group may each have a number of network links less than the bucketing factor, while the network devices in the higher level group may each have a number of network links greater than or equal to the bucketing factor. The lower level roles may then be recommended for the network devices in the lower level group, while the higher level roles may be recommended for the network devices in the higher level group. For example, the spine switch role may be recommended for the network devices in the higher level group, while the leaf switch role may be recommended for the network devices in the lower level group. The recommendation may be presented to a network administrator.

[0016] Once the network administrator agrees to the recommendation, the lower-level network device configuration (corresponding to the lower-level role) can be applied to the network devices in the lower-level group, while the higher-level network device configuration (corresponding to the higher-level role) can be applied to the network devices in the higher-level group. Continuing with the previous example, the spine switch configuration can be applied to the network devices in the higher-level group, while the leaf switch configuration can be applied to the network devices in the lower-level group. Bucketing network devices based on statistical analysis of the number of network links for each network device can be faster than other bucketing techniques (e.g., network topology discovery) while still maintaining the desired accuracy. In addition, bucketing network devices based on statistical analysis of the number of network links can be more scalable than other bucketing techniques (e.g., using a predetermined bucketing factor) and can better adapt to networks with network devices with different numbers of network links. Therefore, the efficiency of network management and orchestration can be improved.

[0017] Figure 1 1 is a block diagram of a private cloud environment 100 according to some implementations. The private cloud environment 100 is a system that includes a physical network 102. Overlay networking can be used to orchestrate the private cloud environment 100 such that a virtual network 110 runs on the physical network 102.

[0018] The physical network 102 includes a plurality of network devices 104. The network devices 104 may be controllers, access points, switches, routers, etc. In addition, the physical network 102 includes host servers 106. The host servers 106 may be bare metal machines suitable for hosting cloud components 114 (e.g., virtual machines, containers, etc.). The network devices 104 form a transport network that provides connectivity and routing between the host servers 106. At least some of the network devices 104 and the host servers 106 may be located in a local data center, but the physical network 102 may span multiple locations. The physical network 102 may be a layer 2 network.

[0019] The virtual network 110 is established on the physical network 102 using an encapsulation protocol. The encapsulation protocol encapsulates network traffic within a virtual tunnel 112, which is sent via the network device 104. Example encapsulation protocols include Virtual Extended LAN (VXLAN), Generic Routing Encapsulation (GRE), etc. Encapsulation allows the virtual network 110 to operate as if it is running on a dedicated physical infrastructure, even though the traffic is actually transmitted over the physical network 102. The virtual network 110 can be used in a virtualized environment. In particular, the cloud components 114 hosted by the host server 106 can be connected via the virtual tunnel 112. The virtual network 110 can be a layer 3 network.

[0020] The management service 120 is adapted to manage the private cloud environment 100. In particular, the management service 120 may be used to create or modify a virtual network 110, such as by creating or modifying a virtual tunnel 112. In addition, the management service 120 is used to configure the network devices 104 of the physical network 102, such as by applying a network device configuration to the network device 104 to prepare for the creation of the virtual network 110. The network device 104 may be assigned a role, which represents the role of the network device 104 in the physical network 102. Based on the role assigned to the network device 104, the network device configuration is pushed to the network device 104, which may allow for automation of the private cloud environment 100. As described in more detail subsequently, the role will be automatically recommended by the management service 120 for assignment to the network device 104. Automatically recommending and assigning roles to the network devices 104 may improve the efficiency of network management, and may improve the efficiency of the private cloud environment 100. The role for the network device 104 will be recommended based on the number of network links for each of the network devices 104.

[0021] The management service 120 may include any suitable components. Suitable components include processors, application specific integrated circuits, microcontrollers, memory, etc. The management service 120 may be a physical device, such as a computer. For example, the management service 120 may include a processor 124 and a memory 126. The memory 126 may be a non-transitory computer-readable medium that stores programs for execution by the processor 124. One or more modules within the management service 120 may be partially or fully embodied as software and / or hardware for performing any of the functions described herein. For example, they may be embodied as software that is deployed to a physical device using a suitable containerization technology.

[0022] Management service 120 may be a local service or may be a cloud service. When management service 120 is a local service, it may be part of physical network 102, such as in a local data center. When management service 120 is a cloud service, it may be part of another physical network different from physical network 102. In either implementation, management service 120 is adapted to communicate with network device 104.

[0023] The management service 120 receives commands from the management interface 128 and displays output using the management interface 128. The management interface 128 may be a command line interface, a graphical user interface, a web page interface, etc. The management service 120 processes commands from the management interface 128, validates the commands, and executes logic specified by the commands. In addition, the management service 120 outputs the results of the commands via the management interface 128.

[0024] Figure 21 is a block diagram of a physical network 102 according to some implementations. For clarity of illustration, some features of the physical network 102 are omitted. In particular, only some network devices 104 (e.g., switches) of the physical network 102 are shown. In this implementation, the physical network 102 has a data center (DC) network topology of a leaf-spine architecture, where the network devices 104 include leaf switches 104L and spine switches 104S.

[0025] The leaf switches 104L are lower level switches that are closer to the edge of the physical network 102 than the spine switches 104S. The leaf switches 104L contain access ports that connect to servers, firewalls, load balancers, and edge routers within the physical network 102. For example, the host server 106 (see Figure 1 ) are connected to leaf switches 104L. Each leaf switch 104L has a network link to a spine switch 104S. Some leaf switches 104L at the border 108 of the physical network 102 are border leaf switches. The border leaf switches provide layer 2 or layer 3 external connections to external networks outside the physical network 102. The border leaf switches can perform routing to external routers of the external networks. Although Figure 2 Not shown, a leaf switch 104L may be linked to another leaf switch 104L, such as using a virtual switch extension (VSX) link, to form a leaf switch 104L pair.

[0026] The spine switches 104S are higher-level switches that are farther from the edge of the physical network 102 than the leaf switches 104L. The spine switches 104S connect the leaf switches 104L together to form a leaf-spine structure. Thus, the spine switches 104S act as the backbone of the physical network 102. Each spine switch 104S has a network link to a leaf switch 104L.

[0027] The leaf switch 104L can be the same hardware as the spine switch 104S, but the leaf switch 104L can be programmed in a different way from the spine switch 104S. Because the leaf switch 104L and the spine switch 104S have different roles in the physical network 102, they are programmed using different network device configurations. In particular, each leaf switch 104L is programmed with a lower-level network device configuration that allows them to act as a lower-level switch. In addition, each leaf switch 104S is programmed with a higher-level network device configuration that allows them to act as a higher-level switch. The network device configuration includes hardware settings that specify how the network device 104 should operate. For example, the network device configuration of the switch may include port settings, link aggregation group (LAG) settings, open shortest path first (OSPF) settings, etc. The network device configuration of the leaf switch 104L is different from the network device configuration of the spine switch 104S because the network device configuration of the leaf switch 104L includes hardware settings (e.g., port settings, LAG settings, and / or OSPF settings) that are different from the network device configuration of the spine switch 104S.

[0028] During network management, roles will be automatically recommended for network devices 104 based on the predicted role of the network devices 104. For example, when a network administrator is provisioning a switch (via the management service 120), the management service 120 will predict the role of the switch in the physical network 102, and based on the prediction, automatically recommend a role for assignment to the switch. In this example, the management service 120 predicts whether the provisioned switch will act as a leaf switch 104L or a spine switch 104S, and then recommends a leaf switch role or a spine switch role to the network administrator based on the prediction. Once the network administrator agrees to the role recommendation, the management service 120 pushes the corresponding network device configuration (e.g., a leaf switch configuration or a spine switch configuration) to the switch based on the role. As a result, the switch can begin operating in its desired role (e.g., as a leaf switch 104L or as a spine switch 104S).

[0029] Figure 3 is a diagram of a network device provisioning method 300 according to some implementations. Figure 1-Figure 2 A network device provisioning method 300 is described. The network device provisioning method 300 can be performed by the management service 120 during provisioning of a network device 104, such as a switch.

[0030] In step 302, the management service 120 identifies the number of network links for each of the network devices 104 in the physical network 104. Only network devices 104 (e.g., switches) that have the same device type as the supply network device 104 can be evaluated. The supply network device 104 may (or may not) be one of the network devices 104 being evaluated. A network link of a network device 104 is a connection between a network device 104 and another network device 104. The number of network links for each network device 104 can be discovered via a suitable network discovery protocol, such as the Link Layer Discovery Protocol (LLDP). For example, the management service 120 can poll each network device 104 via LLDP to discover how many network links each network device 104 has to other network devices 104. Figure 2 In the example of FIG. 1 (e.g., the leaf switches 104L are not linked to each other in pairs), there are 2 spine switches 104S and 10 leaf switches 104L. Each leaf switch 104L has 2 network links (e.g., to each of the spine switches 104S). Each spine switch 104s has 10 network links (e.g., to each of the leaf switches 104L). Therefore, the physical network 102 includes 2 network devices 104 with 10 network links and 10 network devices 104 with 2 network links.

[0031] In step 304, the management service 120 calculates the bucketing factor f via statistical analysis of the number of network links for the network device 104. B The dynamic greedy scalable algorithm is used to calculate the bucket factor f B Bucket factor f B is calculated by calculating the confidence interval for the number of network links of network device 104 using equations (1), (2), and (3). In particular, the bucketing factor f B Equal to the average number of network links for network device 104 and confidence interval values The mean value of the network links It is the total number of network links divided by the total number of network devices 104. Confidence interval value is the standard deviation of the square root of the number of network links divided by the total number of network devices 104. The bucketing factor f is calculated dynamically (eg, at runtime) based on the number of network links for the network devices 104. B Can be more accurate than using a hard-coded bucketing factor.

[0032]

[0033]

[0034]

[0035] In equations (1), (2), and (3), is the mean value of the network links, is the confidence interval value, s is the standard deviation of the number of network links (calculated as the sample standard deviation), N is the total number of network devices 104 evaluated, and x i is the number of network links for network device i. In this implementation, the confidence interval value is based on a confidence interval of 68.3%.

[0036] continue Figure 2 , where physical network 102 includes 2 network devices 104 with 10 network links and 10 network devices 104 with 2 network links, the mean is 40 / 12 or approximately 3.333, and the confidence interval value yes or about 0.899. Therefore, the bucketing factor f B It is 3.333+0.899 or approximately 4.232.

[0037] In step 306, the management service 120 recommends a role for the provisioning network device 104 based on the bucketing factor. The role is recommended by predicting the role of the provisioning network device 104 in the physical network 102. The role of the provisioning network device 104 is predicted by comparing the number of network links for the provisioning network device 104 to the bucketing factor. If the number of network links for the provisioning network device 104 is less than the bucketing factor, the role of the provisioning network device 104 is predicted to be a lower-level switch. Figure 2 In the example of , the leaf switch 104L is a lower-level switch. However, if the number of network links for the supply network device 104 is greater than or equal to the bucketing factor, the role of the supply network device 104 is predicted to be a higher-level switch. Figure 2 In the example of FIG. 1 , the spine switch 104S is a higher-level switch. The recommended role is then selected based on the predicted role of the provisioning network device 104. For example, if the provisioning network device 104 is predicted to be a leaf switch 104L, then the leaf switch role is recommended. Similarly, if the provisioning network device 104 is predicted to be a spine switch 104S, then the spine switch role is recommended. The recommended roles can be displayed to a network administrator, such as via the management interface 128.

[0038] Continuing with the previous example, where the bucketing factor is 4.232, if the supply network device 104 has 2 network links, then the supply network device 104 is predicted to be a leaf switch 104L (because 2 is less than 4.232). Therefore, a recommendation for the leaf switch role of the supply network device 104 can be displayed to the network administrator via the management interface 128. However, if the supply network device 104 has 10 network links, then the supply network device 104 is predicted to be a spine switch 104S (because 10 is greater than or equal to 4.232). Therefore, a recommendation for the spine switch role of the supply network device 104 can be displayed to the network administrator via the management interface 128.

[0039] In step 308, the management service 120 assigns the recommended role to the provisioning network device 104 in response to the network administrator agreeing to the recommendation. The input command may be received from the network administrator via the management interface 128. The input command may include an agreement or a disagreement to recommend the role. In response to the input command including an agreement, the recommended role is assigned to the provisioning network device 104, such as by recording the assignment in a memory of the management service 120.

[0040] In step 310, the management service 120 applies the network device configuration to the provisioned network device 104 based on the role assigned to the provisioned network device 104. For example, if the spine switch role is assigned to the provisioned network device 104, the spine switch configuration is applied to the provisioned network device 104. Similarly, if the leaf switch role is assigned to the provisioned network device 104, the leaf switch configuration is applied to the provisioned network device 104. The management service 120 may apply the network device configuration to the provisioned network device 104 by pushing the network device configuration to the provisioned network device 104. When the network device configuration includes hardware settings, pushing the network device configuration to the provisioned network device 104 includes programming the provisioned network device 104 with the hardware settings of the network device configuration.

[0041] In step 312, management service 120 creates virtual network 110 on physical network 102. Virtual network 110 may include virtual tunnel 112 that carries encapsulated traffic sent via network devices 104 including provisioning network device 104. Creating virtual network 110 may include configuring traffic encapsulation for virtual network 110. Thus, cloud components 114 may communicate via provisioning network device 104.

[0042] Figure 41 is a block diagram of a physical network 102 according to some other implementations. For clarity of illustration, some features of the physical network 102 are omitted. In particular, only some network devices 104 (e.g., switches) of the physical network 102 and an external WAN / WLAN switch 104W are shown. In this implementation, the physical network 102 has a campus network topology with a hierarchical architecture, where the network devices 104 include access switches 104A, aggregator switches 104G, and core switches 104C.

[0043] The access switch 104A is a lower-level switch that is closer to the edge of the physical network 102 than the aggregator switch 104G and the core switch 104C. The access switch 104A contains access ports that connect to servers, firewalls, load balancers, and edge routers within the physical network 102. For example, the host server 106 (see Figure 1 ) are connected to the access switch 104A. Each access switch 104A has a network link to the aggregator switch 104G.

[0044] Aggregator switch 104G and core switch 104C are higher-level switches that are farther from the edge of physical network 102 than access switch 104A. Aggregator switch 104G and core switch 104C connect access switch 104A together to form a hierarchical structure. Therefore, aggregator switch 104G and core switch 104C act as the backbone of physical network 102. Core switch 104C is located at the boundary 108 of physical network 102 and provides layer 2 or layer 3 external connection to external network outside physical network 102. Core switch 104C can perform routing to external routers (e.g., WAN / WLAN switch 104W) of external network. Each aggregator switch 104G has a network link to access switch 104A. In addition, core switch 104C is farther from the edge of physical network 102 than aggregator switch 104G. Each core switch 104C has a network link to aggregator switch 104G. Thus, in the hierarchical structure, the access switch 104A is a bottom-level switch, the aggregator switch 104G is a middle-level switch, and the core switch 104C is a top-level switch.

[0045] The access switch 104A can be the same hardware as the aggregator switch 104G and the core switch 104C, but the access switch 104A can be programmed in a different manner from the aggregator switch 104G and the core switch 104C. In addition, the aggregator switch 104G can be programmed in a different manner from the core switch 104C. Because they have different roles in the physical network 102, the access switch 104A, the aggregator switch 104G and / or the core switch 104C are programmed using different network device configurations. In particular, each access switch 104A is programmed with a lower-level network device configuration that allows them to act as a lower-level switch. In addition, the aggregator switch 104G and / or the core switch 104C are programmed with a higher-level network device configuration that allows them to act as a higher-level switch. The network device configuration of the access switch 104A is different from the network device configuration of the aggregation switch 104G and / or the core switch 104C because the network device configuration of the access switch 104A includes different hardware settings (e.g., port settings, LAG settings, and / or OSPF settings) than the network device configuration of the aggregation switch 104G and / or the core switch 104C. In some implementations, the access switch 104A is programmed with a bottom-level device configuration, the aggregator switch 104G is programmed with a middle-level device configuration, and the core switch 104C is programmed with a top-level device configuration.

[0046] The network device 104 can be configured to: Figure 3 104G and core switches 104C). The device provisioning method 300 may not distinguish between the aggregator switch 104G and the core switch 104C during the provisioning of the bucketing of the network devices 104. In addition, the device provisioning method 300 may not distinguish between the access switch 104A and the WAN / WLAN switch 104W.

[0047] exist Figure 4In the example of , there are 4 access switches 104A, 2 aggregator switches 104G, 2 core switches 104C, and 4 WAN / WLAN switches 104W. Each access switch 104A has 2 network links (e.g., to each aggregator switch 104G). Each aggregator switch 104G has 6 network links (e.g., to each access switch 104A and core switch 104C). Each core switch 104C has 6 network links (e.g., to each aggregator switch 104G and WAN / WLAN switch 104W). Each WAN / WLAN switch 104W has 2 network links (e.g., to each core switch 104C). Therefore, the physical network 102 includes 4 network devices 104 with 6 network links and 8 network devices 104 with 2 network links. In this example, the mean of the network links is 40 / 12 or 3.333, and the confidence interval value is or about 0.569. Therefore, the bucketing factor f B is 3.333+0.569 or approximately 3.902. If the provisioning network device 104 has 2 network links, then the provisioning network device 104 is predicted to be an access switch 104A (because 2 is less than 3.902). Therefore, a recommendation for an access switch role for the provisioning network device 104 can be displayed to the network administrator via the management interface 128. However, if the provisioning network device 104 has 6 network links, then the provisioning network device 104 is predicted to be an aggregator switch 104G / core switch 104C (because 6 is greater than or equal to 3.902). Therefore, a recommendation for an aggregation / core switch role for the provisioning network device 104 can be displayed to the network administrator via the management interface 128.

[0048] In this example, the device provisioning method 300 does not distinguish between the aggregator switch 104G and the core switch 104C during bucketing of the network device 104. Therefore, if the provisioned network device 104 is predicted to be a lower-level switch (e.g., access switch 104A), then the access switch role is recommended. However, if the provisioned network device 104 is predicted to be a higher-level switch (e.g., aggregator switch 104G or core switch 104C), then the aggregator switch role or the core switch role may be recommended. Any suitable classification technique may be used to perform the determination of whether the higher-level switch is an aggregator switch 104G or a core switch 104C. For example, the same method as previously described for Figure 3The steps described above may be similar to those described above to evaluate only the higher level switches of the physical network 102. In particular, the grading factors of the higher level switches of the physical network 102 may be calculated using statistical analysis of the number of network links for the higher level switches in a manner similar to how the bucketing factors are calculated. The number of network links for the provisioning network device 104 may then be compared to the grading factors to predict whether the provisioning network device 104 is an aggregator switch 104G or a core switch 104C.

[0049] Figure 5 is a diagram of a method 500 for orchestrating network devices according to some implementations. Figure 1-Figure 4 A network device orchestration method 500 is described. The network device orchestration method 500 can be performed by a management service 120 during orchestration of a plurality of network devices 104, such as switches.

[0050] In step 502, the management service 120 identifies a number of network links for each of the plurality of network devices 104 of the physical network 102. The number of network links may be discovered in a manner similar to that previously described with respect to step 302 of the network device provisioning method 300.

[0051] In step 504, the management service 120 calculates a bucketing factor for the network device 104. The bucketing factor is equal to the sum of the mean and the confidence interval value of the number of network links for the network device 104. The bucketing factor can be calculated in a manner similar to that previously described for step 304 of the network device provisioning method 300.

[0052] In step 506, the management service 120 groups the network devices 104 into one of a lower level group or a higher level group based on a bucketing factor. The number of network links for the network devices 104 in the lower level group is less than the bucketing factor. The number of network links for the network devices 104 in the higher level group is greater than or equal to the bucketing factor. The functions of the network devices 104 are bucketed to predict the role of the network devices 104, wherein the network devices 104 in the lower level group are predicted to have a lower level role (e.g., a leaf switch or an access switch) and the network devices 104 in the higher level group are predicted to have a higher level role (e.g., a spine switch or an aggregation / core switch).

[0053] Then, lower-level roles may be recommended for network devices 104 in lower-level groups, while higher-level roles may be recommended for network devices 104 in higher-level groups. For example, in a data center network topology, a spine switch role may be recommended for network devices in a higher-level group, while a leaf switch role may be recommended for network devices in a lower-level group. Similarly, in a campus network topology, an aggregator / core switch role may be recommended for network devices in a higher-level group, while an access switch role may be recommended for network devices in a lower-level group. The recommendation may be displayed, such as to a network administrator.

[0054] In step S508, the management service 120 applies the lower-level network device configuration and the higher-level network device configuration to the network devices 104 in the lower-level group and the higher-level group, respectively. For example, in a data center network topology, a leaf switch configuration may be applied to the network devices 104 in the lower-level group, while a spine switch configuration may be applied to the network devices 104 in the higher-level group. Similarly, in a campus network topology, an access switch configuration may be applied to the network devices 104 in the lower-level group, while an aggregator / core switch configuration may be applied to the network devices 104 in the higher-level group. The assignment of the network device configuration may be performed in response to receiving the network administrator's consent to the role recommendation. Additional steps may be optionally performed. For example, after applying the lower-level network device configuration and the higher-level network device configuration, the management service 120 may create a virtual network 110 on the physical network 102.

[0055] In an example implementation consistent with features disclosed herein, a system includes: a plurality of network devices; and a management service implemented on a computer, configured to: identify a number of network links for each of the network devices; calculate a bucket factor for the network device, the bucket factor being equal to the sum of a mean value of the number of network links for the network device and a confidence interval value; recommend a role for provisioning the network device based on the bucket factor; assign the role to the provisioning network device; and apply a network device configuration to the provisioning network device based on the role assigned to the provisioning network device.

[0056] In another example implementation of the system, the management service is configured to recommend a role for the provisioned network device by predicting the role of the provisioned network device. In another example implementation of the system, the management service is configured to predict the role of the provisioned network device by comparing the number of network links for the provisioned network device with a bucketing factor, the role being a higher-level switch when the number of network links for the provisioned network device is greater than or equal to the bucketing factor, and the role being a lower-level switch when the number of network links for the provisioned network device is less than the bucketing factor.

[0057] In another example implementation of the system, the network device is part of a physical network, and the management service is further configured to: create a virtual network on the physical network. In another example implementation of the system, the physical network has a leaf-spine architecture. In another example implementation of the system, the physical network has a layered architecture. In another example implementation of the system, the management service and the network device are part of the same physical network.

[0058] In another example implementation of the system, the management service and the network devices are part of different physical networks. In another example implementation of the system, the management service is configured to identify a number of network links for each network device of the network devices via a link layer discovery protocol.

[0059] In an example implementation consistent with features disclosed herein, a computer-implemented method includes: identifying the number of network links for each of a plurality of network devices for a physical network; calculating a bucket factor for the network device, the bucket factor being equal to the sum of a mean of the number of network links for the network device and a confidence interval value; grouping the network devices into one of a lower-level group or a higher-level group based on the bucket factor, the number of network links for the network devices in the lower-level group being less than the bucket factor, and the number of network links for the network devices in the higher-level group being greater than or equal to the bucket factor; and applying a lower-level network device configuration and a higher-level network device configuration to the network devices in the lower-level group and the higher-level group, respectively.

[0060] In another example implementation, the method further includes: creating a virtual network on the physical network after applying the lower-level network device configuration and the higher-level network device configuration. In another example implementation of the method, the lower-level network device configuration is a leaf switch configuration, and the higher-level network device configuration is a spine switch configuration. In another example implementation of the method, the lower-level network device configuration is an access switch configuration, and the higher-level network device configuration is an aggregator / core switch configuration.

[0061] In another example implementation, the method further includes: recommending a lower-level role and a higher-level role for network devices in the lower-level group and the higher-level group, respectively; and receiving consent for the lower-level role and the higher-level role, wherein the lower-level network device configuration and the higher-level network device configuration are applied in response to receiving the consent for the lower-level role and the higher-level role.

[0062] In another example implementation of the method, identifying the number of network links includes discovering the number of network links for each of the network devices via a network discovery protocol. In another example implementation of the method, the network discovery protocol is a link layer discovery protocol.

[0063] In an example implementation consistent with features disclosed herein, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to: identify the number of network links for each of a plurality of network devices for a physical network; calculate a bucket factor for the network device, the bucket factor being equal to the sum of a mean and a confidence interval value for the number of network links for the network device; recommend a role for the provisioned network device by comparing the number of network links for the provisioned network device with the bucket factor; assign the role to the provisioned network device; apply a network device configuration to the provisioned network device based on the role assigned to the provisioned network device; and create a virtual network on the physical network.

[0064] In another example implementation of the non-transitory computer-readable medium, instructions for applying the network device configuration to the provisioned network device are executed in response to the network administrator agreeing to the recommended role. In another example implementation of the non-transitory computer-readable medium, a number of network links for each of the network devices is identified via a link layer discovery protocol. In another example implementation of the non-transitory computer-readable medium, the virtual network transmits encapsulated network traffic over the physical network.

[0065] The foregoing summarizes the features of several examples so that those skilled in the art can better understand the various aspects of the present disclosure. After referring to the specification, various modifications and combinations of the illustrative examples and other examples will be apparent to those skilled in the art. Therefore, the appended claims are intended to cover any such modifications.

Claims

1. A system comprising: Multiple network devices; as well as A management service implemented on a computer, the management service being configured to: identifying a number of network links for each of the network devices; Calculate a bucket factor for the network device, where the bucket factor is equal to the sum of a mean value of the number of network links for the network device and a confidence interval value; recommending a role for provisioning network devices based on the bucketing factor; assigning the role to the provisioning network device; as well as A network device configuration is applied to the provisioning network device based on the role assigned to the provisioning network device. 2 . The system of claim 1 , wherein the management service is configured to recommend the role for the provisioned network device by predicting a role of the provisioned network device.

3. A system according to claim 2, wherein the management service is configured to predict the role of the supply network device by comparing the number of network links for the supply network device with the bucket factor, the role is a higher-level switch when the number of network links for the supply network device is greater than or equal to the bucket factor, and the role is a lower-level switch when the number of network links for the supply network device is less than the bucket factor.

4. The system of claim 1 , wherein the network device is part of a physical network, and the management service is further configured to: A virtual network is created on the physical network.

5. The system of claim 4, wherein the physical network has a spine-and-leaf architecture. The system of claim 4 , wherein the physical network has a layered architecture.

7. The system of claim 1, wherein the management service and the network device are part of the same physical network.

8. The system of claim 1, wherein the management service and the network device are part of different physical networks.

9. The system of claim 1, wherein the management service is configured to identify the number of network links for each of the network devices via a link layer discovery protocol.

10. A computer-implemented method comprising: identifying a number of network links for each of a plurality of network devices of the physical network; Calculate a bucket factor for the network device, where the bucket factor is equal to the sum of a mean value of the number of network links for the network device and a confidence interval value; grouping the network devices into one of a lower level group or a higher level group based on the bucketing factor, the number of network links for the network devices in the lower level group being less than the bucketing factor, and the number of network links for the network devices in the higher level group being greater than or equal to the bucketing factor; as well as A lower level network device configuration and a higher level network device configuration are applied to the network devices in the lower level group and the higher level group, respectively.

11. The method according to claim 10, further comprising: After applying the lower-level network device configuration and the higher-level network device configuration, a virtual network is created on the physical network.

12. The method of claim 10, wherein the lower level network device configuration is a leaf switch configuration and the higher level network device configuration is a spine switch configuration.

13. The method of claim 10, wherein the lower-level network device configuration is an access switch configuration and the higher-level network device configuration is an aggregator / core switch configuration.

14. The method according to claim 10, further comprising: recommending a lower-level role and a higher-level role for the network devices in the lower-level group and the higher-level group, respectively; as well as An agreement to the lower-level role and the higher-level role is received, wherein the lower-level network device configuration and the higher-level network device configuration are applied in response to receiving the agreement to the lower-level role and the higher-level role.

15. The method of claim 10, wherein identifying the number of network links comprises discovering the number of network links for each of the network devices via a network discovery protocol. The method of claim 15 , wherein the network discovery protocol is a link layer discovery protocol.

17. A non-transitory computer readable medium storing instructions that, when executed by a processor, cause the processor to: identifying a number of network links for each of a plurality of network devices of the physical network; Calculating a bucket factor for the network device, where the bucket factor is equal to the sum of a mean value of the number of network links for the network device and a confidence interval value; recommending a role for the provisioned network device by comparing the number of network links for the provisioned network device with the bucketing factor; assigning the role to the provisioning network device; applying a network device configuration to the provisioned network device based on the role assigned to the provisioned network device; as well as A virtual network is created on the physical network.

18. The non-transitory computer readable medium of claim 17, wherein the instructions to apply the network device configuration to the provisioned network device are executed in response to a network administrator agreeing to the recommended role.

19. The non-transitory computer-readable medium of claim 17, wherein the number of network links for each of the network devices is identified via a link layer discovery protocol.

20. The non-transitory computer readable medium of claim 17, wherein the virtual network transmits encapsulated network traffic over the physical network.